> On 02 Dec 2015, at 08:43, Gianluca Cecchi <gianluca.cec...@gmail.com> wrote: > > On Wed, Dec 2, 2015 at 8:18 AM, Shahar Havivi <shah...@redhat.com > <mailto:shah...@redhat.com>> wrote: > On 01.12.15 17 <tel:01.12.15%2017>:26, Gianluca Cecchi wrote: > > > > OK, I'm trying using classic network instead of NetworkManager. > > But right before running the "make template" action, do I have to run any > > of "sys-unconfig" and/or "virt-sysprep" tools? > No you don't need to run this tools. > > OK. Understood.
you don’t have to, but you’ll get a better, cleaner, template if you’ve been using the original image before (added accounts, installed stuff…things people usually do when preparing a template:) we’re looking into integrating it into UI, as it is quite easy to omit a thing or two when sealing it manually It may make sense to use it for initialization during deployment as well as a replacement of cloud-init not requiring you to initialize it by running it. You would have to do it yourself, making sure the image is not in use while the operation is ongoing. I think it would also be nice to completely integrate it into “create VM from Template” flow. You would have a ready-to-go VMs customized at the time of creation already, instead of relying on runtime cloud-init Thanks, michal > > > > > > It remains open the question about how to properly seal a RHEL 7 / CentOS 7 > What do you mean by sealing? > > > I mean what are the correct modifications t apply to the OS, before makeing > it a template and then create a VM from that template using cloud-init. > For example: > a NetworkManager enabled configuration for ifcfg-eth0 file is somethng like > that on RH EL 7: > > TYPE=Ethernet > BOOTPROTO=none > DEFROUTE=yes > IPV4_FAILURE_FATAL=no > IPV6INIT=no > IPV6_AUTOCONF=yes > IPV6_DEFROUTE=yes > IPV6_PEERDNS=yes > IPV6_PEERROUTES=yes > IPV6_FAILURE_FATAL=no > NAME=eth0 > UUID=5a656c34-e4ba-44a1-8079-d2c797e6a8f4 > DEVICE=eth0 > ONBOOT=yes > IPADDR=10.4.4.29 > PREFIX=24 > GATEWAY=10.4.4.250 > DNS1=10.4.1.11 > DNS2=10.4.1.12 > DOMAIN="mysearchdomain1.com <http://mysearchdomain1.com/> mysearchdomain2.com > <http://mysearchdomain2.com/>" > > While an old style (managed by classic "network" service) entry sholud be > something like: > > DEVICE=eth0 > TYPE=Ethernet > BOOTPROTO=static > ONBOOT=yes > IPADDR=10.4.4.29 > PREFIX=24 > GATEWAY=10.4.4.250 > > Do I have to make any modification in both case to ifcfg-eth0 just before > making template or should I leave the original VM values inside? > Does cloud-init provided by oVirt with the values I put inside the GUI during > VM creation replace files using something like "sed" command or does it run > any network-config operating system commands? > Gianluca > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users