[openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch

Michał Jastrzębski inc007 at gmail.com
Wed Mar 30 18:30:42 UTC 2016


So I made this:
https://review.openstack.org/#/c/299563/

I'm not super fond of reverting commits from the middle of release,
because this will make a lot of mess. I'd rather re-implement keystone
bootstrap logic and make it conditional as it is not that complicated.

On 30 March 2016 at 12:37, Ryan Hallisey <rhallise at redhat.com> wrote:
> Agreed this needs to happen +1,
>
> ----- Original Message -----
> From: "Jeff Peeler" <jpeeler at redhat.com>
> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
> Sent: Wednesday, March 30, 2016 1:22:31 PM
> Subject: Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch
>
> On Wed, Mar 30, 2016 at 3:52 AM, Steven Dake (stdake) <stdake at cisco.com> wrote:
>>
>>
>> From: Jeffrey Zhang <zhang.lei.fly at gmail.com>
>> Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>> <openstack-dev at lists.openstack.org>
>> Date: Wednesday, March 30, 2016 at 12:29 AM
>> To: "OpenStack Development Mailing List (not for usage questions)"
>> <openstack-dev at lists.openstack.org>
>> Subject: Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty
>> within the Liberty branch
>>
>> +1
>>
>> A lot of changes has been make in Mitaka. Backport is difficult.
>>
>> But using Mitaka deploy Liberty also has *much works*. For example,
>> revert config file change which deprecated in Mitaka and Liberty support.
>>
>> A important one is the `keystone-manage bootstrap` command to create the
>> keystone admin account. This is adderecently and only exist in the Mitaka
>> branch. So when using this method, we should revert some commit and use
>> the old way method.
>>
>>
>> Agreed.
>
> I'm sure there will be some checking and such once all the code has
> been shuffled around, but I think doing this work is better than
> abandoning a branch. So +1 to proposal.
>
> __________________________________________________________________________
> 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



More information about the OpenStack-dev mailing list