Open Stack

Until we are sure IBP solves operation phase where we need to deliver
updated packages so client will be able to provision new machines with
these fixed packages, I would leave backward compatibility with normal
provision. ... Just in case.



--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser

On Mon, Jan 26, 2015 at 4:56 PM, Vladimir Kozhukalov <
vkozhukalov at mirantis.com> wrote:

> My suggestion is to make IBP the only option available for all upcoming
> OpenStack releases which are defined in openstack.yaml. It is to be
> possible to install OS using kickstart for all currently available
> OpenStack releases.
>
> Vladimir Kozhukalov
>
> On Mon, Jan 26, 2015 at 6:22 PM, Igor Kalnitsky <ikalnitsky at mirantis.com>
> wrote:
>
>> Just want to be sure I understand you correctly: do you propose to
>> FORBID kickstart/preseed installation way in upcoming release at all?
>>
>> On Mon, Jan 26, 2015 at 3:59 PM, Vladimir Kozhukalov
>> <vkozhukalov at mirantis.com> wrote:
>> > Subject is changed.
>> >
>> > Vladimir Kozhukalov
>> >
>> > On Mon, Jan 26, 2015 at 4:55 PM, Vladimir Kozhukalov
>> > <vkozhukalov at mirantis.com> wrote:
>> >>
>> >> Dear Fuelers,
>> >>
>> >> As you might know we need it to be possible to install several
>> versions of
>> >> a particular OS (Ubuntu and Centos) by 6.1  As far as having different
>> OS
>> >> versions also means having different sets of packages and some of  the
>> >> packages are installed and configured during provisioning stage, we
>> need to
>> >> have a kind of kickstart/preseed version mechanism.
>> >>
>> >> Cobbler is exactly such a mechanism. It allows us to have several
>> Distros
>> >> (installer images) and profiles (kickstart/preseed files). But
>> >> unfortunately, for some reasons we have not been using those Cobbler's
>> >> capabilities since the beginning of Fuel and it doesn't seem to be
>> easily
>> >> introduced into Nailgun to deal with the whole Cobbler life cycle.
>> >>
>> >> Anyway, we are moving towards IBP (image based provisioning) and we
>> >> already have different images connected to different OpenStack releases
>> >> (openstack.yaml) and everything else which is necessary for initial
>> node
>> >> configuration is serialized inside provision data (including profile
>> name
>> >> like 'ubuntu_1204' or 'ubuntu_1404') and we are able to choose
>> cloud-init
>> >> template by this profile name.
>> >>
>> >> And taking into account what it is written above, the suggestion is to
>> >> completely avoid using kickstart/preseed based way of OS provisioning
>> by 6.1
>> >> for all new releases allowing ONLY old ones to use this way.
>> >>
>> >> Any opinions about that stuff are welcome.
>> >>
>> >> Vladimir Kozhukalov
>> >
>> >
>> >
>> >
>> __________________________________________________________________________
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150126/5185118a/attachment.html>