On 13 November 2015 at 11:46, Sean Dague <s...@dague.net> wrote: > On 11/13/2015 01:16 PM, Sean M. Collins wrote: > > On Fri, Nov 13, 2015 at 07:42:12AM EST, Sean Dague wrote: > >> Ok, I top responded with the details of the job, honestly I think it's > >> just a project-config change to get up and running, and then hacking at > >> the bugs that fall out. > > > > Thanks - that was super helpful. > > > > I'm thinking of working on the following on Monday: > > > > 1) capture that somewhere in the upgrade docs we're putting together in > neutron's devref > > > > 2) Adding the stanza to project-config to get grenade running for > > Neutron > > > > 3) Take a look at the patches that Armando linked a couple emails back > > in this thread. > > I don't think that any of the patches listed there are needed. This was > part of the reason I -2ed that direction in the last cycle. It required > a separate special code path for partial upgrade setup which was very > synthetic (and honestly kind of confusing to debug). >
I don't disagree. I didn't meant to imply 'resume the patches', I was only providing the backdrop. > > The new approach means if you did upgrade for the all-in-one case, and > you did multinode setup with worker processes on the subnode, you just > make a config where you do them both at the same time, and you have > partial upgrade. > > -Sean > > -- > Sean Dague > http://dague.net > > __________________________________________________________________________ > 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