So, a plan. My idea about this backport is to:
1. We write Mitaka code deploying Liberty, just liberty (remove deploy_liberty nonsense from patchset above) 2. We mark this code as Kolla 1.1.0 effectively deprecating what we call liberty today 3. Most of bugs found in master/stable-mitaka will also be relevant to liberty so brace for backports of bugfixes So what I am going to do: 1. Make patchset above deploy Liberty (only liberty) for source builds 2. After mitaka will be cut off, we do code copying What I need from you guys: 1. Someone help me figure out centos binary as it doesn't really use sources from build-conf 2. Someone help me to check out if release of mariadb, rabbitmq and other infra changed anything that will break Liberty, I highly doubt it, but if you guys know about anything, shout out please. 3. Testing testing testing Thoughts? Michal On 30 March 2016 at 13:30, Michał Jastrzębski <inc...@gmail.com> wrote: > 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 <rhall...@redhat.com> wrote: >> Agreed this needs to happen +1, >> >> ----- Original Message ----- >> From: "Jeff Peeler" <jpee...@redhat.com> >> To: "OpenStack Development Mailing List (not for usage questions)" >> <openstack-dev@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) <std...@cisco.com> >> wrote: >>> >>> >>> From: Jeffrey Zhang <zhang.lei....@gmail.com> >>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" >>> <openstack-dev@lists.openstack.org> >>> Date: Wednesday, March 30, 2016 at 12:29 AM >>> To: "OpenStack Development Mailing List (not for usage questions)" >>> <openstack-dev@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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
