[openstack-dev] [Fuel] Image based provisioning

Mike Scherbakov mscherbakov at mirantis.com
Wed Dec 17 02:03:27 UTC 2014

as part of 6.1 roadmap, we are going to work on patching feature.
There are two types of workflow to consider:
- patch existing environment (already deployed nodes, aka "target" nodes)
- ensure that new nodes, added to the existing and already patched envs,
will install updated packages too.

In case of anakonda/preseed install, we can simply update repo on master
node and run createrepo/etc. What do we do in case of image? Will we need a
separate repo alongside with main one, "updates" repo - and do
post-provisioning "yum update" to fetch all patched packages?

On Tue, Dec 16, 2014 at 11:09 PM, Andrey Danin <adanin at mirantis.com> wrote:
> Adding Mellanox team explicitly.
> Gil, Nurit, Aviram, can you confirm that you tested that feature? It can
> be enabled on every fresh ISO. You just need to enable the Experimental
> mode (please, see the documentation for instructions).
> On Tuesday, December 16, 2014, Dmitry Pyzhov <dpyzhov at mirantis.com> wrote:
>> Guys,
>> we are about to enable image based provisioning in our master by default.
>> I'm trying to figure out requirement for this change. As far as I know, it
>> was not tested on scale lab. Is it true? Have we ever run full system tests
>> cycle with this option?
>> Do we have any other pre-requirements?
> --
> Andrey Danin
> adanin at mirantis.com
> skype: gcon.monolake
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Mike Scherbakov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141217/b5e34cad/attachment.html>

More information about the OpenStack-dev mailing list