<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Nov 16, 2016 at 8:14 PM, Barak Yes, use cloud-init.<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><p dir="ltr">
You can import the image directly as a template and then edit the template to add nics and cloud-init configuration.<br>
(This way you can easily setup multipile preconfigured VMs from it. You don't have to use run-once for cloud-init).</p><span class="gmail-">
<p dir="ltr">> Does the image correspond to the qcow2 one downloadable from <br>
> <a href="http://cloud.centos.org/centos/7/atomic/images/" target="_blank">http://cloud.centos.org/<wbr>centos/7/atomic/images/</a></p>
</span><p dir="ltr">Yes.<span class="gmail-"><br>
><br>
> or does it contain any customization already related for deploying in oVirt itself?</span></p>
<p dir="ltr">No, its the exact same image.</p>
<p dir="ltr">HTH,<br>
Barak Korren.</p>
</blockquote></div><br></div><div class="gmail_extra">Ok,</div><div class="gmail_extra">I imported the atomic image as a template, then I added a nic to it and finally created a VM based on that template.</div><div class="gmail_extra">I specified to use "Cloud-Init/Sysprep" with parameters specified as in this image:</div><div class="gmail_extra"><a href="https://drive.google.com/file/d/0BwoPbcrMv8mvaGF5QWRKSjFJVWM/view?usp=sharing">https://drive.google.com/file/d/0BwoPbcrMv8mvaGF5QWRKSjFJVWM/view?usp=sharing</a><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Some notes:</div><div class="gmail_extra">1) hostname got acquired</div><div class="gmail_extra">2) time zone acquired</div><div class="gmail_extra">3) username and his password got acquired</div><div class="gmail_extra">(btw: he/she has already ability to do "sudo su -", probably embedded in the OS composition itself)</div><div class="gmail_extra">4) The network part is not so clear in my opinion</div><div class="gmail_extra">The line with the "Network" checkbox has an apparently drop down checkbox that is initially empty but shows nothing selecting the arrow</div><div class="gmail_extra">If I understand correctly one should manually write inside? I did so.</div><div class="gmail_extra">Initially I thought about the oVirt network and put "ovirtmgmt", but then I realized that it actually created an ifcfg-ovirmgmt file inside guest.....</div><div class="gmail_extra">So I retested using "eth0" (as in screenshot).</div><div class="gmail_extra">And it got the correct ip/netmask/gw ok, but NOT dns</div><div class="gmail_extra"><div class="gmail_extra"><br></div><div class="gmail_extra">-bash-4.2# cat /etc/sysconfig/network</div><div class="gmail_extra">NETWORKING=yes</div><div class="gmail_extra">NOZEROCONF=yes</div><div class="gmail_extra">-bash-4.2#</div><div><br></div><div><div>-bash-4.2# cat /etc/sysconfig/network-scripts/ifcfg-eth0</div><div>DEVICE=eth0</div><div>BOOTPROTO=static</div><div>ONBOOT=yes</div><div>TYPE=Ethernet</div><div>PERSISTENT_DHCLIENT=yes</div><div>NETMASK=255.255.255.0</div><div>IPADDR=192.168.150.108</div><div>GATEWAY=192.168.150.254</div><div>-bash-4.2#</div></div><div><br></div><div>It has been configured with NetworkManager:</div><div><div>-bash-4.2# systemctl status NetworkManager</div><div>● NetworkManager.service - Network Manager</div><div> Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)</div><div> Active: active (running) since Thu 2016-11-17 12:53:07 CET; 4min 33s ago</div><div> Main PID: 724 (NetworkManager)</div><div> Memory: 16.4M</div><div> CGroup: /system.slice/NetworkManager.service</div><div> └─724 /usr/sbin/NetworkManager --no-daemon</div><div><br></div><div>Nov 17 12:53:53 atomic NetworkManager[724]: <info> NetworkManager state is ...G</div><div>Nov 17 12:53:53 atomic NetworkManager[724]: <info> (eth0): device state cha...]</div><div>Nov 17 12:53:53 atomic NetworkManager[724]: <info> (eth0): device state cha...]</div><div>Nov 17 12:53:53 atomic NetworkManager[724]: <info> (eth0): device state cha...]</div><div>Nov 17 12:53:53 atomic NetworkManager[724]: <info> (eth0): device state cha...]</div><div>Nov 17 12:53:53 atomic NetworkManager[724]: <info> (eth0): device state cha...]</div><div>Nov 17 12:53:53 atomic NetworkManager[724]: <info> NetworkManager state is ...L</div><div>Nov 17 12:53:53 atomic NetworkManager[724]: <info> NetworkManager state is ...L</div><div>Nov 17 12:53:53 atomic NetworkManager[724]: <info> Policy set 'System eth0'....</div><div>Nov 17 12:53:53 atomic NetworkManager[724]: <info> (eth0): Activation: succ....</div><div>Hint: Some lines were ellipsized, use -l to show in full.</div><div>-bash-4.2#</div></div><div><br></div><div>I don't know if fault for DNS is a matter of cloud-init, oVirt or image composition....</div><div><br></div><div>resolv.conf file contains:</div><div><br></div><div><div>-bash-4.2# cat /etc/resolv.conf</div><div># Generated by NetworkManager</div><div>search localdomain</div><div><br></div><div><br></div><div># No nameservers found; try putting DNS servers into your</div><div># ifcfg files in /etc/sysconfig/network-scripts like so:</div><div>#</div><div># DNS1=xxx.xxx.xxx.xxx</div><div># DNS2=xxx.xxx.xxx.xxx</div><div># DOMAIN=<a href="http://lab.foo.com">lab.foo.com</a> <a href="http://bar.foo.com">bar.foo.com</a></div><div>-bash-4.2#</div></div><div><br></div><div>I can do further checks.... the VM is alive</div><div><br></div><div>Cominq back to the network config for cloud-init....</div></div><div class="gmail_extra"><br></div><div class="gmail_extra">The line "Select network above" is in my opinion not so intuitive in its usage</div><div class="gmail_extra"><br></div><div class="gmail_extra">I understood this way</div><div class="gmail_extra"><br></div><div class="gmail_extra">a) you select a Network (eth0) in my case</div><div class="gmail_extra">the first time you explicitly put a name, then when you further add other networks/nics, the dropdown is populated.....</div><div class="gmail_extra"><br></div><div class="gmail_extra">b) when you have a nic selected (eth0 in my case), its configuration is shown in the lines below it</div><div class="gmail_extra">The first time you have to add it with the "+" sign.</div><div class="gmail_extra">When you have more than a nic, every time you select a preconfigured one, you can see its current config in the lines below.....</div><div class="gmail_extra"><br></div><div class="gmail_extra">Not better using multiple nic sections, instead of this dropdown/dynamically changing ones?</div><div class="gmail_extra">The typical user will had 1 interface anyway.</div><div class="gmail_extra">When you accomodate 2-3 sections I doubt ther will be many usacase for more, so that the size of the "New Virtual Machine" window shouldn't suffer too much.</div><div class="gmail_extra"><br></div><div class="gmail_extra">I hope I was able to explain my point of view... ;-)</div><div class="gmail_extra"><br></div><div class="gmail_extra">Gianluca</div></div>