Re: [VOTE] 4.11.3.0 RC1
Gregor, can you confirm if you followed the steps exactly in regards to template flags and more importantly the actual name - I believe in the code, during upgrading, it will search for specific template name (i.e. systemvm-vmware-4.11.3) and update it's DB values so it becomes a "SYSTEM" instead of "USER" type that it was initially. Andrija On Wed, 12 Jun 2019 at 16:46, Riepl, Gregor (SWISS TXT) < gregor.ri...@swisstxt.ch> wrote: > Hi Paul, > > > The release notes are still work-in-progress, but the systemvm > > template upgrade section has been updated. You may refer the > > following for systemvm template upgrade testing: > > > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/index.html > > Thanks! > > We're doing our own tests right now, but ran into problems when > updating the system VMs. > > For one, after registering the new VMware systemvm template, it is > shown as a "USER" template. I'm not sure if this is correct. Is there > an additional step to ensure it is considered a "SYSTEM" template? > I believe this is important so the SSVM and Console Proxy get upgraded. > > Secondly, the upgrade instructions do not mention updating > minreq.sysvmtemplate.version > and > router.template. > to the > version/name of the new template. > > Without this step, routers won't be upgraded to the new template. > IMHO, it should be mentioned in all upgrade instructions. > > Should I prepare a PR against the documentation? > > Best regards, > Gregor > -- Andrija Panić
Re: [VOTE] 4.11.3.0 RC1
Hi Paul, > The release notes are still work-in-progress, but the systemvm > template upgrade section has been updated. You may refer the > following for systemvm template upgrade testing: > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/index.html Thanks! We're doing our own tests right now, but ran into problems when updating the system VMs. For one, after registering the new VMware systemvm template, it is shown as a "USER" template. I'm not sure if this is correct. Is there an additional step to ensure it is considered a "SYSTEM" template? I believe this is important so the SSVM and Console Proxy get upgraded. Secondly, the upgrade instructions do not mention updating minreq.sysvmtemplate.version and router.template. to the version/name of the new template. Without this step, routers won't be upgraded to the new template. IMHO, it should be mentioned in all upgrade instructions. Should I prepare a PR against the documentation? Best regards, Gregor
Re: 4.13 Heads up
Sounds like a plan! Wido On 6/10/19 5:19 PM, Paul Angus wrote: > In order to keep up the momentum on the release cadence, some of us are now > planning to get 4.13 moving > > > > We've come up with a plan which I hope everyone will find acceptable (see > below). > > > > > > == 4.13.0.0: (next LTS release) > == > > > > * 1-5 July 2019: Freeze master and stabilize > * 8-12 July 2019: After ~100% smoketest pass and only accept blocker > fixes, cut RC1 > * 14 July - 5 Aug 2019: Release 4.13.0.0 (next LTS) > * Milestone: https://github.com/apache/cloudstack/milestone/8 > > > > Cheers > > > > Paul Angus > > > > > > > > > > > > > paul.an...@shapeblue.com > www.shapeblue.com > Amadeus House, Floral Street, London WC2E 9DPUK > @shapeblue > > >
