Re: [VOTE] 4.11.3.0 RC1
+1 (binding) KVM, CentOS7, local storage. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Milamber" > To: "dev" > Sent: Wednesday, 19 June, 2019 22:35:50 > Subject: Re: [VOTE] 4.11.3.0 RC1 > Hello, > > +1 (binding) > > > Tested on KVM + NFS installation > > > Milamber > > On 11/06/2019 10:57, Paul Angus wrote: >> Hi All, >> >> I've created a 4.11.3.0 release (RC1), with the following artefacts up for >> testing and a vote: >> >> >> Git Branch and Commit SH: >> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.11.3.0-RC20190610T1615 >> Commit: 51124b7b35f47089b2e51a93b2094ea93dd15302 >> >> Source release (checksums and signatures are available at the same >> location): >> https://dist.apache.org/repos/dist/dev/cloudstack/4.11.3.0/ >> >> PGP release keys (signed using 51EE0BC8): >> https://dist.apache.org/repos/dist/release/cloudstack/KEYS >> >> The vote will be open until end of 16 June 2019. >> >> For sanity in tallying the vote, can PMC members please be sure to indicate >> "(binding)" with their vote? >> >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >> >> Additional information: >> >> For users' convenience, I've built packages from >> 51124b7b35f47089b2e51a93b2094ea93dd15302 and published RC1 repository here: >> http://packages.shapeblue.com/testing/41130rc1/ >> >> 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 >> >> 4.11.3.0 systemvm templates are available from here: >> http://packages.shapeblue.com/testing/systemvm/41130rc1/ >> >> >> >> PRs in 4.11.3.0: >> +==+ >> >> +-+--++ >> | Version | Github | Description >> | | >> +=+==++ >> | 4.11.3.0| `#3381`_ | schema: add 4.11.2 to 4.11.3 >> | systemvmtemplate upgrade path | >> +-+--++ >> | 4.11.3.0| `#3075`_ | KVM: Prevent regenerating keystore on >> | provisionCertificate | >> | | | API >> | >> +-+--++ >> | 4.11.3.0| `#3373`_ | router: support multi-homed VMs in VPC >> | | >> +-+--++ >> | 4.11.3.0| `#3366`_ | Fix rule duplication with static NAT >> rules >> | | >> +-+--++ >> | 4.11.3.0| `#3194`_ | Suspending a VM before snapshot >> deletion >> | (see PR #3193)| >> +-+--++ >> | 4.11.3.0| `#3370`_ | ssvm: apply MTU value on >> storage/management >> | nic if | >> | | | available >> | >> +-+--++ >> | 4.11.3.0| `#2995`_ | KVM: Improvements on upload direct >> download >> | certificates | >> +-+--++ >> | 4.11.3.0| `#3351`_ | Have persistent DHCP leases file on >> VRs and >> | cleanup| >> | | | /etc/hosts on VM deletion >> | >> +-+--++ >> | 4.11.3.0| `#3310`_ | Fix removing static NAT rules with >> Juniper >> | SRX | >> +-+--++ >> | 4.11.3.0
Re: [VOTE] 4.11.3.0 RC1
Hello, +1 (binding) Tested on KVM + NFS installation Milamber On 11/06/2019 10:57, Paul Angus wrote: Hi All, I've created a 4.11.3.0 release (RC1), with the following artefacts up for testing and a vote: Git Branch and Commit SH: https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.11.3.0-RC20190610T1615 Commit: 51124b7b35f47089b2e51a93b2094ea93dd15302 Source release (checksums and signatures are available at the same location): https://dist.apache.org/repos/dist/dev/cloudstack/4.11.3.0/ PGP release keys (signed using 51EE0BC8): https://dist.apache.org/repos/dist/release/cloudstack/KEYS The vote will be open until end of 16 June 2019. For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote? [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Additional information: For users' convenience, I've built packages from 51124b7b35f47089b2e51a93b2094ea93dd15302 and published RC1 repository here: http://packages.shapeblue.com/testing/41130rc1/ 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 4.11.3.0 systemvm templates are available from here: http://packages.shapeblue.com/testing/systemvm/41130rc1/ PRs in 4.11.3.0: +==+ +-+--++ | Version | Github | Description | +=+==++ | 4.11.3.0| `#3381`_ | schema: add 4.11.2 to 4.11.3 systemvmtemplate upgrade path | +-+--++ | 4.11.3.0| `#3075`_ | KVM: Prevent regenerating keystore on provisionCertificate | | | | API | +-+--++ | 4.11.3.0| `#3373`_ | router: support multi-homed VMs in VPC | +-+--++ | 4.11.3.0| `#3366`_ | Fix rule duplication with static NAT rules | +-+--++ | 4.11.3.0| `#3194`_ | Suspending a VM before snapshot deletion (see PR #3193)| +-+--++ | 4.11.3.0| `#3370`_ | ssvm: apply MTU value on storage/management nic if | | | | available | +-+--++ | 4.11.3.0| `#2995`_ | KVM: Improvements on upload direct download certificates | +-+--++ | 4.11.3.0| `#3351`_ | Have persistent DHCP leases file on VRs and cleanup| | | | /etc/hosts on VM deletion | +-+--++ | 4.11.3.0| `#3310`_ | Fix removing static NAT rules with Juniper SRX | +-+--++ | 4.11.3.0| `#3361`_ | Fix 4.11 VR Issues with Multiple Public Subnets| +-+--++ | 4.11.3.0| `#3206`_ | server: allow dedicate ip range to a domain if ips are | | | | used by an account in the domain | +-+--++ | 4.11.3.0| `#3205`_ | server: update dhcp configurations in vrs while update | | | | default nic of running vms | +-+--++ | 4.11.3.0| `#3362`_ | vmware: fix potential NPE when memory hotplug capability | | | | is checked | +-+--++ |
Re: [VOTE] 4.11.3.0 RC1
Hi Wei, the workaround is only necessary when kernel security patch cannot be applied and afterwards the host cannot be rebooted. For 4.11.3.0 rc1, the new systemvmtemplate has the latest kernel security patch. Regards. Regards, Rohit Yadav From: Wei ZHOU Sent: Wednesday, June 19, 2019 12:02:46 AM To: dev@cloudstack.apache.org Subject: Re: [VOTE] 4.11.3.0 RC1 Hi Rohit, Do we need to change default iptable tables for cpvm and ssvm ? # iptables -I INPUT -p tcp --tcp-flags SYN SYN -m tcpmss --mss 1:500 -j DROP # ip6tables -I INPUT -p tcp --tcp-flags SYN SYN -m tcpmss --mss 1:500 -j DROP (see https://access.redhat.com/security/vulnerabilities/tcpsack) -Wei Rohit Yadav 于2019年6月18日周二 上午11:57写道： > All, > > > Due to recently disclosed and fixed tcp/SACK vulnerability and other > security issues (refer https://www.debian.org/security/2019/dsa-4465), > I've rebuilt and synced new 4.11.3.0 systemvmtemplates which has linux > 4.9.168-1+deb9u3 (2019-06-16): > > > http://download.cloudstack.org/systemvm/testing/4.11.3-rc > > http://packages.shapeblue.com/testing/systemvm/41130rc1 > > > Kindly continue testing 4.11.3.0 RC1 using above systemvmtemplates. Thanks. > > > Build log for reference: > http://download.cloudstack.org/systemvm/testing/4.11.3-rc/build.log > > > Regards, > > Rohit Yadav > > Software Architect, ShapeBlue > > https://www.shapeblue.com > > > From: Riepl, Gregor (SWISS TXT) > Sent: Friday, June 14, 2019 7:45:58 PM > To: dev@cloudstack.apache.org; us...@cloudstack.apache.org > Subject: Re: [VOTE] 4.11.3.0 RC1 > > +1 > > Based on: > - Packages from http://packages.shapeblue.com/testing/41130rc1/ and > http://packages.shapeblue.com/testing/systemvm/41130rc1/ > - Upgrade of our test cloud from 4.11.2 to 4.11.3 worked without problems > (aside from the mentioned template issue) > - Our internal smoke test stack ran successfully > > The only thing I'm a bit unhappy about is the backported ostype API fix: > https://github.com/apache/cloudstack/pull/3066 > Since this is a breaking API change, I don't think it should be included > in a minor release, even if it fixes an API bug. > It triggers an error in Packer, which we use to create templates. > However, a fix was already commited and will be in the next Packer > release, so I'm ok'ing it: https://github.com/hashicorp/packer/pull/7694 > > rohit.ya...@shapeblue.com > www.shapeblue.com<http://www.shapeblue.com> > Amadeus House, Floral Street, London WC2E 9DPUK > @shapeblue > > > > rohit.ya...@shapeblue.com www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue
Re: [VOTE] 4.11.3.0 RC1
Hi Wei, Sounds good. Maybe we should add the fist option to ssvm and csvm too. Option #1 Disable selective acknowledgments system wide for all newly established TCP connections. # echo 0 > /proc/sys/net/ipv4/tcp_sack or # sysctl -w net.ipv4.tcp_sack=0 ... Sven Von meinem iPhone gesendet __ Sven Vogel Teamlead Platform EWERK RZ GmbH Bruhl 24, D-04109 Leipzig P +49 341 42649 - 11 F +49 341 42649 - 18 s.vo...@ewerk.com www.ewerk.com Geschaftsfuhrer: Dr. Erik Wende, Hendrik Schubert, Frank Richter Registergericht: Leipzig HRB 17023 Zertifiziert nach: ISO/IEC 27001:2013 DIN EN ISO 9001:2015 DIN ISO/IEC 2-1:2011 EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<https://www.linkedin.com/company/ewerk-group> | Xing<https://www.xing.com/company/ewerk> | Twitter<https://twitter.com/EWERK_Group> | Facebook<https://de-de.facebook.com/EWERK.IT/> Auskunfte und Angebote per Mail sind freibleibend und unverbindlich. Disclaimer Privacy: Der Inhalt dieser E-Mail (einschlieslich etwaiger beigefugter Dateien) ist vertraulich und nur fur den Empfanger bestimmt. Sollten Sie nicht der bestimmungsgemase Empfanger sein, ist Ihnen jegliche Offenlegung, Vervielfaltigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte informieren Sie in diesem Fall unverzuglich den Absender und loschen Sie die E-Mail (einschlieslich etwaiger beigefugter Dateien) von Ihrem System. Vielen Dank. The contents of this e-mail (including any attachments) are confidential and may be legally privileged. If you are not the intended recipient of this e-mail, any disclosure, copying, distribution or use of its contents is strictly prohibited, and you should please notify the sender immediately and then delete it (including any attachments) from your system. Thank you. Am 18.06.2019 um 20:33 schrieb Wei ZHOU mailto:ustcweiz...@gmail.com>>: Hi Rohit, Do we need to change default iptable tables for cpvm and ssvm ? # iptables -I INPUT -p tcp --tcp-flags SYN SYN -m tcpmss --mss 1:500 -j DROP # ip6tables -I INPUT -p tcp --tcp-flags SYN SYN -m tcpmss --mss 1:500 -j DROP (see https://access.redhat.com/security/vulnerabilities/tcpsack) -Wei Rohit Yadav mailto:rohit.ya...@shapeblue.com>> 于2019年6月18日周二 上午11:57写道： All, Due to recently disclosed and fixed tcp/SACK vulnerability and other security issues (refer https://www.debian.org/security/2019/dsa-4465), I've rebuilt and synced new 4.11.3.0 systemvmtemplates which has linux 4.9.168-1+deb9u3 (2019-06-16): http://download.cloudstack.org/systemvm/testing/4.11.3-rc http://packages.shapeblue.com/testing/systemvm/41130rc1 Kindly continue testing 4.11.3.0 RC1 using above systemvmtemplates. Thanks. Build log for reference: http://download.cloudstack.org/systemvm/testing/4.11.3-rc/build.log Regards, Rohit Yadav Software Architect, ShapeBlue https://www.shapeblue.com From: Riepl, Gregor (SWISS TXT) mailto:gregor.ri...@swisstxt.ch>> Sent: Friday, June 14, 2019 7:45:58 PM To: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>; us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org> Subject: Re: [VOTE] 4.11.3.0 RC1 +1 Based on: - Packages from http://packages.shapeblue.com/testing/41130rc1/ and http://packages.shapeblue.com/testing/systemvm/41130rc1/ - Upgrade of our test cloud from 4.11.2 to 4.11.3 worked without problems (aside from the mentioned template issue) - Our internal smoke test stack ran successfully The only thing I'm a bit unhappy about is the backported ostype API fix: https://github.com/apache/cloudstack/pull/3066 Since this is a breaking API change, I don't think it should be included in a minor release, even if it fixes an API bug. It triggers an error in Packer, which we use to create templates. However, a fix was already commited and will be in the next Packer release, so I'm ok'ing it: https://github.com/hashicorp/packer/pull/7694 rohit.ya...@shapeblue.com<mailto:rohit.ya...@shapeblue.com> www.shapeblue.com<http://www.shapeblue.com> Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue
Re: [VOTE] 4.11.3.0 RC1
Hi Rohit, Do we need to change default iptable tables for cpvm and ssvm ? # iptables -I INPUT -p tcp --tcp-flags SYN SYN -m tcpmss --mss 1:500 -j DROP # ip6tables -I INPUT -p tcp --tcp-flags SYN SYN -m tcpmss --mss 1:500 -j DROP (see https://access.redhat.com/security/vulnerabilities/tcpsack) -Wei Rohit Yadav 于2019年6月18日周二 上午11:57写道： > All, > > > Due to recently disclosed and fixed tcp/SACK vulnerability and other > security issues (refer https://www.debian.org/security/2019/dsa-4465), > I've rebuilt and synced new 4.11.3.0 systemvmtemplates which has linux > 4.9.168-1+deb9u3 (2019-06-16): > > > http://download.cloudstack.org/systemvm/testing/4.11.3-rc > > http://packages.shapeblue.com/testing/systemvm/41130rc1 > > > Kindly continue testing 4.11.3.0 RC1 using above systemvmtemplates. Thanks. > > > Build log for reference: > http://download.cloudstack.org/systemvm/testing/4.11.3-rc/build.log > > > Regards, > > Rohit Yadav > > Software Architect, ShapeBlue > > https://www.shapeblue.com > > > From: Riepl, Gregor (SWISS TXT) > Sent: Friday, June 14, 2019 7:45:58 PM > To: dev@cloudstack.apache.org; us...@cloudstack.apache.org > Subject: Re: [VOTE] 4.11.3.0 RC1 > > +1 > > Based on: > - Packages from http://packages.shapeblue.com/testing/41130rc1/ and > http://packages.shapeblue.com/testing/systemvm/41130rc1/ > - Upgrade of our test cloud from 4.11.2 to 4.11.3 worked without problems > (aside from the mentioned template issue) > - Our internal smoke test stack ran successfully > > The only thing I'm a bit unhappy about is the backported ostype API fix: > https://github.com/apache/cloudstack/pull/3066 > Since this is a breaking API change, I don't think it should be included > in a minor release, even if it fixes an API bug. > It triggers an error in Packer, which we use to create templates. > However, a fix was already commited and will be in the next Packer > release, so I'm ok'ing it: https://github.com/hashicorp/packer/pull/7694 > > rohit.ya...@shapeblue.com > www.shapeblue.com > Amadeus House, Floral Street, London WC2E 9DPUK > @shapeblue > > > >
Re: [VOTE] 4.11.3.0 RC1
All, Due to recently disclosed and fixed tcp/SACK vulnerability and other security issues (refer https://www.debian.org/security/2019/dsa-4465), I've rebuilt and synced new 4.11.3.0 systemvmtemplates which has linux 4.9.168-1+deb9u3 (2019-06-16): http://download.cloudstack.org/systemvm/testing/4.11.3-rc http://packages.shapeblue.com/testing/systemvm/41130rc1 Kindly continue testing 4.11.3.0 RC1 using above systemvmtemplates. Thanks. Build log for reference: http://download.cloudstack.org/systemvm/testing/4.11.3-rc/build.log Regards, Rohit Yadav Software Architect, ShapeBlue https://www.shapeblue.com From: Riepl, Gregor (SWISS TXT) Sent: Friday, June 14, 2019 7:45:58 PM To: dev@cloudstack.apache.org; us...@cloudstack.apache.org Subject: Re: [VOTE] 4.11.3.0 RC1 +1 Based on: - Packages from http://packages.shapeblue.com/testing/41130rc1/ and http://packages.shapeblue.com/testing/systemvm/41130rc1/ - Upgrade of our test cloud from 4.11.2 to 4.11.3 worked without problems (aside from the mentioned template issue) - Our internal smoke test stack ran successfully The only thing I'm a bit unhappy about is the backported ostype API fix: https://github.com/apache/cloudstack/pull/3066 Since this is a breaking API change, I don't think it should be included in a minor release, even if it fixes an API bug. It triggers an error in Packer, which we use to create templates. However, a fix was already commited and will be in the next Packer release, so I'm ok'ing it: https://github.com/hashicorp/packer/pull/7694 rohit.ya...@shapeblue.com www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue
Re: [VOTE] 4.11.3.0 RC1
+1 Based on: - Packages from http://packages.shapeblue.com/testing/41130rc1/ and http://packages.shapeblue.com/testing/systemvm/41130rc1/ - Upgrade of our test cloud from 4.11.2 to 4.11.3 worked without problems (aside from the mentioned template issue) - Our internal smoke test stack ran successfully The only thing I'm a bit unhappy about is the backported ostype API fix: https://github.com/apache/cloudstack/pull/3066 Since this is a breaking API change, I don't think it should be included in a minor release, even if it fixes an API bug. It triggers an error in Packer, which we use to create templates. However, a fix was already commited and will be in the next Packer release, so I'm ok'ing it: https://github.com/hashicorp/packer/pull/7694
Re: [VOTE] 4.11.3.0 RC1
So, I think it's ok to leave this issue aside. I have a suspicion why the templates don't get upgraded, but since we know how to fix them manually, it's not release critical. We'll open a ticket later. From: Rohit Yadav Sent: 13 June 2019 12:49:40 To: dev; us...@cloudstack.apache.org Subject: Re: [VOTE] 4.11.3.0 RC1 Gregor, Please follow the following guide, but use the systemvmtemplate URL from the mirror shared on this thread and register the template with the name as "systemvm--4.11.3" before upgrading to 4.11.3.0-rc1: http://docs.cloudstack.apache.org/en/4.11.2.0/upgrading/upgrade/upgrade-4.11.html Regards, Rohit Yadav Software Architect, ShapeBlue https://www.shapeblue.com From: Andrija Panic Sent: Thursday, June 13, 2019 2:45:50 AM To: dev Cc: us...@cloudstack.apache.org Subject: 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ć rohit.ya...@shapeblue.com www.shapeblue.com<http://www.shapeblue.com> Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue
Re: [VOTE] 4.11.3.0 RC1
Gregor, Please follow the following guide, but use the systemvmtemplate URL from the mirror shared on this thread and register the template with the name as "systemvm--4.11.3" before upgrading to 4.11.3.0-rc1: http://docs.cloudstack.apache.org/en/4.11.2.0/upgrading/upgrade/upgrade-4.11.html Regards, Rohit Yadav Software Architect, ShapeBlue https://www.shapeblue.com From: Andrija Panic Sent: Thursday, June 13, 2019 2:45:50 AM To: dev Cc: us...@cloudstack.apache.org Subject: 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ć rohit.ya...@shapeblue.com www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue
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: [VOTE] 4.11.3.0 RC1
+1 (binding) Based on; > gpg --verify apache-cloudstack-4.11.3.0-src.tar.bz2.asc gpg: assuming signed data in 'apache-cloudstack-4.11.3.0-src.tar.bz2' gpg: Signature made Mon 10 Jun 2019 08:45:16 PM IST gpg:using RSA key 8B309F7251EE0BC8 gpg: Good signature from "Paul Angus (apache) " Primary key fingerprint: 70F0 17ED 6DB6 7AC9 2681 66C1 8B30 9F72 51EE 0BC8 Smoketest ~100% pass on kvm, xenserver, vmware, and simulator/Travis: https://github.com/apache/cloudstack/pull/3376 https://github.com/apache/cloudstack/pull/3381 4.11.3 systemvmtemplates location verified, OK; http://download.cloudstack.org/systemvm/testing/4.11.3-rc/ http://packages.shapeblue.com/testing/systemvm/41130rc1/ (templates syncing now) Regards, Rohit Yadav Software Architect, ShapeBlue https://www.shapeblue.com From: Paul Angus Sent: Tuesday, June 11, 2019 3:27:29 PM To: dev@cloudstack.apache.org; us...@cloudstack.apache.org Subject: [VOTE] 4.11.3.0 RC1 Hi All, I've created a 4.11.3.0 release (RC1), with the following artefacts up for testing and a vote: Git Branch and Commit SH: https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.11.3.0-RC20190610T1615 Commit: 51124b7b35f47089b2e51a93b2094ea93dd15302 Source release (checksums and signatures are available at the same location): https://dist.apache.org/repos/dist/dev/cloudstack/4.11.3.0/ PGP release keys (signed using 51EE0BC8): https://dist.apache.org/repos/dist/release/cloudstack/KEYS The vote will be open until end of 16 June 2019. For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote? [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Additional information: For users' convenience, I've built packages from 51124b7b35f47089b2e51a93b2094ea93dd15302 and published RC1 repository here: http://packages.shapeblue.com/testing/41130rc1/ 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 4.11.3.0 systemvm templates are available from here: http://packages.shapeblue.com/testing/systemvm/41130rc1/ PRs in 4.11.3.0: +==+ +-+--++ | Version | Github | Description | +=+==++ | 4.11.3.0| `#3381`_ | schema: add 4.11.2 to 4.11.3 systemvmtemplate upgrade path | +-+--++ | 4.11.3.0| `#3075`_ | KVM: Prevent regenerating keystore on provisionCertificate | | | | API | +-+--++ | 4.11.3.0| `#3373`_ | router: support multi-homed VMs in VPC | +-+--++ | 4.11.3.0| `#3366`_ | Fix rule duplication with static NAT rules | +-+--++ | 4.11.3.0| `#3194`_ | Suspending a VM before snapshot deletion (see PR #3193)| +-+--++ | 4.11.3.0| `#3370`_ | ssvm: apply MTU value on storage/management nic if | | | | available | +-+--++ | 4.11.3.0| `#2995`_ | KVM: Improvements on upload direct download certificates | +-+--++ | 4.11.3.0| `#3351`_ | Have persistent DHCP leases file on VRs and cleanup| | | | /etc/hosts on VM deletion | +-+--++ | 4.11.3.0| `#3310`_ | Fix removing static NAT rules with Juniper SRX | +-+--++ | 4.11.3.0| `#3361`_ | Fix 4.11 VR Issues with Multiple Public Subnets| +-+--++ | 4.11.3.0
