Open Stack

Thank you for your advice.

In our production environment, is using the RPM by puppet to deploy based
environment.But there are still a few projects due to the deployment cost
is higher, so choose the snapshot.Actually it's more like image of a
disguised form.

2016-11-22 20:39 GMT+08:00 Saverio Proto <zioproto at gmail.com>:

> Hello,
>
> snapshot are meant to be backups.
> I would not install software on a machine, and then use the snapshot
> as a glance image to start many new instances.
>
> you could just create machines with a clean glance image and install
> the necessary software with ansible/puppet
>
> if the installation time at boot is too long, you could create glance
> images with the software you need with the diskimage-builder creating
> a new dib.
>
> Look at this example of a ubuntu glance image with zeppelin and spark
> preinstalled:
> https://github.com/switch-ch/diskimage-builder/tree/
> SWITCHengines/elements/zeppelin
>
> Saverio
>
>
> 2016-11-22 7:44 GMT+01:00 Jack Gao <jack.gao.ch at gmail.com>:
> > Hi everyone，
> >
> > I am using a virtual machine to create a snapshot, and then use this
> > snapshot to create other virtual machines.Will encounter residual data
> > didn't clean the problem, this will lead to network card information is
> > inaccurate, puppet certificate conflict etc.
> >
> > The current practice is to use the sys-virtprep tools manual cleaning,
> > within the opesntack system, whether to have a better solution?
> >
> > Regards.
> >
> > _______________________________________________
> > OpenStack-operators mailing list
> > OpenStack-operators at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20161123/fa52a5c2/attachment.html>