[GitHub] [cloudstack-primate] utchoang commented on issue #99: [WIP] - Recurring Volume Snapshot Custom Action Form
utchoang commented on issue #99: [WIP] - Recurring Volume Snapshot Custom Action Form URL: https://github.com/apache/cloudstack-primate/pull/99#issuecomment-574533221 @rhtyd I resolved the conflict PR. Please review again. Thank you This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd commented on issue #87: Take Volume Snapshot Action
rhtyd commented on issue #87: Take Volume Snapshot Action URL: https://github.com/apache/cloudstack-primate/issues/87#issuecomment-574531621 PR is here https://github.com/apache/cloudstack-primate/pull/109 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd closed issue #87: Take Volume Snapshot Action
rhtyd closed issue #87: Take Volume Snapshot Action URL: https://github.com/apache/cloudstack-primate/issues/87 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd commented on issue #99: [WIP] - Recurring Volume Snapshot Custom Action Form
rhtyd commented on issue #99: [WIP] - Recurring Volume Snapshot Custom Action Form URL: https://github.com/apache/cloudstack-primate/pull/99#issuecomment-574522160 @utchoang there are some conflicts, can you merge latest master and fix the conflicts? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd merged pull request #92: Register Template Action
rhtyd merged pull request #92: Register Template Action URL: https://github.com/apache/cloudstack-primate/pull/92 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] utchoang opened a new pull request #110: [WIP] - Take Volume Snapshot Action
utchoang opened a new pull request #110: [WIP] - Take Volume Snapshot Action URL: https://github.com/apache/cloudstack-primate/pull/110 @rhtyd cc @svenvogel This is my new design of the Take Volume Snapshot Action. Please review and let me know your comments.  This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd commented on issue #109: [WIP] - Take Volume Snapshot Action
rhtyd commented on issue #109: [WIP] - Take Volume Snapshot Action URL: https://github.com/apache/cloudstack-primate/pull/109#issuecomment-574524225 @utchoang kindly create a new branch from origin/master as advised yesterday. That way your PRs won't have changes from other branches/PRs. Kindly fix the merge conflict. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd commented on issue #100: [WIP] - Resource view style/layout improvement
rhtyd commented on issue #100: [WIP] - Resource view style/layout improvement URL: https://github.com/apache/cloudstack-primate/pull/100#issuecomment-574523459 @RitchieVincent the issues have not been addressed yet: 1. The width and label issue is not fixed for all a-progress, for example in zone/cluster:  2. The issue of buttons on the bottom of a nic description block in the instance hardware tab:  This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] utchoang commented on issue #109: [WIP] - Take Volume Snapshot Action
utchoang commented on issue #109: [WIP] - Take Volume Snapshot Action URL: https://github.com/apache/cloudstack-primate/pull/109#issuecomment-574537972 I will close this PR and add a new PR to avoid conflict. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] utchoang closed pull request #109: [WIP] - Take Volume Snapshot Action
utchoang closed pull request #109: [WIP] - Take Volume Snapshot Action URL: https://github.com/apache/cloudstack-primate/pull/109 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd commented on issue #84: [WIP] - Guest network: Many tabs
rhtyd commented on issue #84: [WIP] - Guest network: Many tabs URL: https://github.com/apache/cloudstack-primate/pull/84#issuecomment-574523899 @RitchieVincent no changes seen here, are you working on them at all? If not, please advise. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd merged pull request #104: sort order in list view
rhtyd merged pull request #104: sort order in list view URL: https://github.com/apache/cloudstack-primate/pull/104 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd closed issue #25: Implement list order sorting in List View
rhtyd closed issue #25: Implement list order sorting in List View URL: https://github.com/apache/cloudstack-primate/issues/25 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd commented on issue #62: Custom Upload Action - Template, ISO, volume
rhtyd commented on issue #62: Custom Upload Action - Template, ISO, volume URL: https://github.com/apache/cloudstack-primate/issues/62#issuecomment-574532034 @utchoang will you be able to work on it? Otherwise you may also have a look at: https://github.com/apache/cloudstack-primate/issues/39 (I can explain in detail, as it will a slightly complex task requiring some ldap setup) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Re: CloudStack Kubernetes provider containers on DockerHub
Hi Pierre, Hi Paul, @Paul do you know how we proceed. How we can get the space from Apache and align to the policy? Cheers Sven __ Sven Vogel Teamlead Platform EWERK DIGITAL GmbH Brühl 24, D-04109 Leipzig P +49 341 42649 - 99 F +49 341 42649 - 98 s.vo...@ewerk.com www.ewerk.com Geschäftsführer: Dr. Erik Wende, Hendrik Schubert, Frank Richter Registergericht: Leipzig HRB 9065 Zertifiziert nach: ISO/IEC 27001:2013 DIN EN ISO 9001:2015 DIN ISO/IEC 2-1:2011 EWERK-Blog | LinkedIn | Xing | Twitter | Facebook Auskünfte und Angebote per Mail sind freibleibend und unverbindlich. Disclaimer Privacy: Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die E-Mail (einschließlich etwaiger beigefügter 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 13.01.2020 um 15:06 schrieb Pierre-Luc Dion : > > Hi Paul, > > So we should not use our 2 account but use under apache one instead, > correct? if so, I will remove all owner and projects from the 2 I've > created a while back. they are outdated anyway so better hiding them then > keep old stuff that can cause confusion. > > > On Sun, Jan 12, 2020 at 4:10 PM Sven Vogel wrote: > >> Hi Paul, >> >> I agree! I would do the same If it’s possible. >> >> Cheers >> >> >> __ >> >> Sven Vogel >> Teamlead Platform >> >> EWERK DIGITAL GmbH >> Brühl 24, D-04109 Leipzig >> P +49 341 42649 - 99 >> F +49 341 42649 - 98 >> s.vo...@ewerk.com >> www.ewerk.com >> >> Geschäftsführer: >> Dr. Erik Wende, Hendrik Schubert, Frank Richter >> Registergericht: Leipzig HRB 9065 >> >> Zertifiziert nach: >> ISO/IEC 27001:2013 >> DIN EN ISO 9001:2015 >> DIN ISO/IEC 2-1:2011 >> >> EWERK-Blog | LinkedIn | Xing | Twitter | Facebook >> >> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich. >> >> Disclaimer Privacy: >> Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist >> vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der >> bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, >> Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte >> informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie >> die E-Mail (einschließlich etwaiger beigefügter 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 12.01.2020 um 21:40 schrieb Paul Angus : >>> >>> Hey Guys, >>> >>> Actually I've been meaning to get round to sorting this. We need to >> remove 'our' docker hub account and use the Apache run one >>> https://hub.docker.com/u/apache >>> >>> This came up on the Board mailing list with another project. We'll need >> to align ourselves with the policy also. >>> >>> >>> >>> Kind regards >>> >>> >>> Paul. >>> >>> paul.an...@shapeblue.com >>> www.shapeblue.com >>> Amadeus House, Floral Street, London WC2E 9DPUK >>> @shapeblue >>> >>> >>> >>> >>> -Original Message- >>> From: Sven Vogel >>> Sent: 12 January 2020 14:07 >>> To: dev >>> Cc: Pierre-Luc Dion ; Pierre-Luc Dion < >> pd...@cloudops.com>; Will Stevens ; >> gabrasc...@gmail.com; Wido den Hollander >>> Subject: Re: CloudStack Kubernetes provider containers on DockerHub >>> >>> Hi Guys, >>> >>> Should we also find a ways to put the passwords accessible for all >> committers or PMC like Youtube Account? >>> >>> Make that sense? >>> >>> Cheers >>> >>> Sven >>> >>> >>> __ >>> >>> Sven Vogel >>> Teamlead Platform >>> >>> EWERK DIGITAL GmbH >>> Brühl 24, D-04109 Leipzig >>> P +49 341 42649 - 99 >>> F +49 341 42649 - 98 >>> s.vo...@ewerk.com >>> www.ewerk.com >>> >>> Geschäftsführer: >>> Dr. Erik Wende, Hendrik Schubert, Frank Richter >>> Registergericht: Leipzig HRB 9065 >>> >>> Zertifiziert nach: >>> ISO/IEC 27001:2013 >>> DIN EN ISO 9001:2015 >>> DIN ISO/IEC 2-1:2011 >>> >>> EWERK-Blog | LinkedIn | Xing | Twitter | Facebook >>> >>> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich. >>> >>> Disclaimer Privacy: >>> Der Inhalt dieser E-Mail (einschließlich etwaiger
[GitHub] [cloudstack-primate] utchoang opened a new pull request #109: [WIP] - Take Volume Snapshot Action
utchoang opened a new pull request #109: [WIP] - Take Volume Snapshot Action URL: https://github.com/apache/cloudstack-primate/pull/109 @rhtyd cc @svenvogel This is my new design of the Take Volume Snapshot Action. Please review and let me know your comments. ![Uploading Screenshot_6.jpg…]() This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] PaulAngus commented on issue #87: upgrade: upgrade systemvmtemplate for 4.14
PaulAngus commented on issue #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#issuecomment-574077951 We will have the new systemVM template API and UI. I suggest that we (you) need to get up to speed on how it works ASAP @rhtyd @andrijapanicsb //cc @borisstoyanov @Spaceman1984 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd commented on issue #88: Recurring Volume Snapshot Custom Action Form
rhtyd commented on issue #88: Recurring Volume Snapshot Custom Action Form URL: https://github.com/apache/cloudstack-primate/issues/88#issuecomment-574078656 PR added, closing this. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd closed issue #101: Add Template and ISO Zones tab
rhtyd closed issue #101: Add Template and ISO Zones tab URL: https://github.com/apache/cloudstack-primate/issues/101 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd closed issue #86: Register Template Action
rhtyd closed issue #86: Register Template Action URL: https://github.com/apache/cloudstack-primate/issues/86 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd commented on issue #86: Register Template Action
rhtyd commented on issue #86: Register Template Action URL: https://github.com/apache/cloudstack-primate/issues/86#issuecomment-574078575 PR added, closing this. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd closed issue #88: Recurring Volume Snapshot Custom Action Form
rhtyd closed issue #88: Recurring Volume Snapshot Custom Action Form URL: https://github.com/apache/cloudstack-primate/issues/88 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] utchoang commented on issue #99: [WIP] - Recurring Volume Snapshot Custom Action Form
utchoang commented on issue #99: [WIP] - Recurring Volume Snapshot Custom Action Form URL: https://github.com/apache/cloudstack-primate/pull/99#issuecomment-574078321 @rhtyd I would allow them to be all shown when the form is loaded, but it will affect other input (lag) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366239633 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" + + If local storage paths are found to have a trailing forward slash, + remove it: + + .. parsed-literal:: + + $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + + +.. _ubuntu412: +.. _apt-repo412: Review comment: this has been like this for some time, references, so do indeed needs updating This is an automated message from the Apache Git Service. To respond to the message,
[GitHub] [cloudstack-documentation] andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366240368 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" + + If local storage paths are found to have a trailing forward slash, + remove it: + + .. parsed-literal:: + + $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + + +.. _ubuntu412: +.. _apt-repo412: + +Management Server +- + +Ubuntu +## + +If you are using Ubuntu, follow this procedure to upgrade your packages. If +not, skip to step :ref:`rhel411`. + +.. note:: + **Community Packages:** This section assumes you're using the
[GitHub] [cloudstack-primate] rhtyd commented on issue #92: [WIP] - Register Template Action
rhtyd commented on issue #92: [WIP] - Register Template Action URL: https://github.com/apache/cloudstack-primate/pull/92#issuecomment-574069605 Will review shortly @utchoang This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd commented on issue #99: [WIP] - Recurring Volume Snapshot Custom Action Form
rhtyd commented on issue #99: [WIP] - Recurring Volume Snapshot Custom Action Form URL: https://github.com/apache/cloudstack-primate/pull/99#issuecomment-574072822 @utchoang but it breaks the UX for the user, as in the old UI we would list all the possible select options when the form is loaded. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] RitchieVincent opened a new pull request #104: [WIP] - List order sort buttons
RitchieVincent opened a new pull request #104: [WIP] - List order sort buttons URL: https://github.com/apache/cloudstack-primate/pull/104 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] RitchieVincent commented on issue #100: [WIP] - Resource view style/layout improvement
RitchieVincent commented on issue #100: [WIP] - Resource view style/layout improvement URL: https://github.com/apache/cloudstack-primate/pull/100#issuecomment-574087118 > @RitchieVincent ping - can you address styling issues? Should be all good to go now This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Re: [PRIMATE][SIG] Meeting Notes
14 Jan 2020 meeting notes: Project board: https://github.com/apache/cloudstack-primate/projects/1 Est. total effort left: ~170 hours Progress by number of supported APIs: 80% (95 remaining APIs vs 461 APIs in old UI) High-level changes since last two weeks: * Project dashboard, actions, configuration and actions * Register ISO action * Update offering access and update template permissions form * Zones tab for templates and ISOs * SG: ingress/egress tabs * Guest Network: Egress tab, firewall, pf, vpn, lb tabs (under review) * VPC: create VPN customer gateway, basic list views, tab stubs and navigations * Minor bug fixes and enhancements * Work in progress: https://github.com/apache/cloudstack-primate/pulls Actions and goals for the next two weeks are to continue to work on issues from the project board, work towards manual QA and test-automation. Regards, Rohit Yadav Software Architect, ShapeBlue https://www.shapeblue.com From: Rohit Yadav Sent: Monday, December 16, 2019 20:58 To: dev@cloudstack.apache.org Subject: Re: [PRIMATE][SIG] Meeting Notes 16 Dec 2019 meeting notes: Project board: https://github.com/apache/cloudstack-primate/projects/1 Est. total effort left: ~270 hours Progress by number of supported APIs: ~70% (138 remaining APIs vs 461 APIs in old UI) High-level changes since last two weeks: * Infra/SSL-cert setup form * Domain tree-based list view * Reusable settings component for global settings and scoped settings (in domain, accounts, zones, cluster, primary/secondary storages etc) * IAM: Account certs tab * Compute: VM migration form, assign to account/project form * Minor bug fixes and enhancements * Work in progress: * VM NIC/IP management buttons/views * Backup and recovery UI views and actions Actions and goals for the next two weeks are to continue to work on issues from the project board. Regards, Rohit Yadav Software Architect, ShapeBlue https://www.shapeblue.com From: Rohit Yadav Sent: Monday, December 2, 2019 22:39 To: dev@cloudstack.apache.org Subject: Re: [PRIMATE][SIG] Meeting Notes 2 Dec 2019 meeting notes: Project board: https://github.com/apache/cloudstack-primate/projects/1 Est. total effort left: ~300 hours Progress by number of supported APIs: ~68% (148 remaining APIs vs 461 APIs in old UI) High-level changes since last two weeks: * docker support (wip) + eslint fixes * all related navigation on views * recursive actions/async polling + refresh * reusable details setings for vm & templates * breadcrumb fixes * placement fixes, put actions in card * contextual doc links in views and actions * API remapping framework, most actions work now * infra:summary page, boilerplate code PRs: * Tree-like domain view (in review, Sven/Hoang/EWerk) * Infra/SSL cert setup form (in progress, Rohit/Shapeblue) * VM deployment wizard (in progress, Sven/Florian/EWerk) * Zone deployment (on-hold, Rohit/Shapeblue) Actions and goals for the next two weeks: Gabriel/PCExtreme: to pick a few UI issues from the board, Rohit to suggest easy tasks to start with Sven/EWerk: Continue on the VM deployment and new tasks (project, account views/tabs) Rohit/Shapeblue: write spec/requirements and details on project issues, progress on many of the design/arch issues as well as project board tasks Regards, Rohit Yadav Software Architect, ShapeBlue https://www.shapeblue.com From: Rohit Yadav Sent: Monday, November 18, 2019 18:31 To: dev@cloudstack.apache.org Subject: [PRIMATE][SIG] Meeting Notes 18 Nov 2019 High level: * Attendees - Bobby, Gabriel, Paul, Rohit * High-level project updates discussed: no major changes or significant work in last two weeks * Few bugs fixes and PRs merged in last two weeks * Technical preview project/progress board: https://github.com/apache/cloudstack-primate/projects/1 * Discussed usage of Github packages for docker, maven etc. Actions and agreements: * Gabriel/PCExtreme: exploring a Docker image/setup, Wido has agreed to donate VM/resources for the CI/CD setup for PR (a live env on each PR) - to explore Docker image, CI/env setup and bot-integration on Primate PRs and support for IPv6 in the UI * Bobby/ShapeBlue - manual QA (may commence effort towards end of Dec) * Rohit/ShapeBlue - work stalled on zone deployment, likely to be resumed this week * Paul/ShapeBlue, rest - discuss if having guided tutorials (both videos and articles/docs) may help in driving the interest and traction to development output Discussion for the community - there has not been any significant development output lately, at least in the last 2-4 weeks: * How can we encourage the community to participate and contribute development towards the Primate project? * If we work
[GitHub] [cloudstack-documentation] andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366239968 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" + + If local storage paths are found to have a trailing forward slash, + remove it: + + .. parsed-literal:: + + $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + + +.. _ubuntu412: +.. _apt-repo412: + +Management Server +- + +Ubuntu +## + +If you are using Ubuntu, follow this procedure to upgrade your packages. If +not, skip to step :ref:`rhel411`. + +.. note:: + **Community Packages:** This section assumes you're using the
[GitHub] [cloudstack-primate] rhtyd opened a new issue #105: Dedicate Resource to an Account
rhtyd opened a new issue #105: Dedicate Resource to an Account URL: https://github.com/apache/cloudstack-primate/issues/105 Add forms in zone, pod, cluster, host to: - Form to dedicate that zone/pod/cluster/hod to an account by selecting the domain and the account - List and display either tab or section in details to say whether the resource (zone/pod/cluster/host) is dedicated to an account/domain - If the resource is not dedicated show the dedicate button, otherwise show button to release the dedicated resource For example, in case of a pod:    This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] rhtyd commented on issue #85: [WIP] Backup & Recovery Doc Guide
rhtyd commented on issue #85: [WIP] Backup & Recovery Doc Guide URL: https://github.com/apache/cloudstack-documentation/pull/85#issuecomment-574053364 Thanks @PaulAngus for the screenshots and writeup. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366197757 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" + + If local storage paths are found to have a trailing forward slash, + remove it: + + .. parsed-literal:: + + $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; Review comment: @PaulAngus It's boilerplate from older upgrade rst file, I think we may want to review the whole post-upgrade cases and remove/edit as necessary. This is an automated message from the Apache Git Service. To respond
[GitHub] [cloudstack-documentation] rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366196708 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" + + If local storage paths are found to have a trailing forward slash, + remove it: + + .. parsed-literal:: + + $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + + +.. _ubuntu412: +.. _apt-repo412: + +Management Server +- + +Ubuntu +## + +If you are using Ubuntu, follow this procedure to upgrade your packages. If +not, skip to step :ref:`rhel411`. + +.. note:: + **Community Packages:** This section assumes you're using the community +
[GitHub] [cloudstack-documentation] rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366196639 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" + + If local storage paths are found to have a trailing forward slash, + remove it: + + .. parsed-literal:: + + $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + + +.. _ubuntu412: +.. _apt-repo412: + +Management Server +- + +Ubuntu +## + +If you are using Ubuntu, follow this procedure to upgrade your packages. If +not, skip to step :ref:`rhel411`. + +.. note:: + **Community Packages:** This section assumes you're using the community +
[GitHub] [cloudstack-documentation] rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366197298 ## File path: source/conf.py ## @@ -24,9 +24,9 @@ author = 'Apache CloudStack Project' Review comment: Fixed. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366197197 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" + + If local storage paths are found to have a trailing forward slash, + remove it: + + .. parsed-literal:: + + $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + + +.. _ubuntu412: +.. _apt-repo412: + +Management Server +- + +Ubuntu +## + +If you are using Ubuntu, follow this procedure to upgrade your packages. If +not, skip to step :ref:`rhel411`. + +.. note:: + **Community Packages:** This section assumes you're using the community +
[GitHub] [cloudstack-documentation] rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366197122 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" + + If local storage paths are found to have a trailing forward slash, + remove it: + + .. parsed-literal:: + + $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + + +.. _ubuntu412: +.. _apt-repo412: + +Management Server +- + +Ubuntu +## + +If you are using Ubuntu, follow this procedure to upgrade your packages. If +not, skip to step :ref:`rhel411`. + +.. note:: + **Community Packages:** This section assumes you're using the community +
[GitHub] [cloudstack-documentation] rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366197156 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" + + If local storage paths are found to have a trailing forward slash, + remove it: + + .. parsed-literal:: + + $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + + +.. _ubuntu412: +.. _apt-repo412: Review comment: I'm not sure how they're used, it's been from before I did not change it. Will need review/checking. It's also in the previous 4.11, 4.12 rst files. cc @PaulAngus This is an
[GitHub] [cloudstack-primate] utchoang commented on issue #99: [WIP] - Recurring Volume Snapshot Custom Action Form
utchoang commented on issue #99: [WIP] - Recurring Volume Snapshot Custom Action Form URL: https://github.com/apache/cloudstack-primate/pull/99#issuecomment-574054835 @rhtyd 1. I have merged with the last master. 2. Timezone is not shown in the first place because I only allow it to be shown when the search text is entered. Reference: https://www.antdv.com/components/select. A lot of timezones listed could cause lag when entering other text inputs 3. I will fix and update it on the next commit This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366197175 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" + + If local storage paths are found to have a trailing forward slash, + remove it: + + .. parsed-literal:: + + $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + + +.. _ubuntu412: +.. _apt-repo412: + +Management Server +- + +Ubuntu +## + +If you are using Ubuntu, follow this procedure to upgrade your packages. If +not, skip to step :ref:`rhel411`. + +.. note:: + **Community Packages:** This section assumes you're using the community +
[GitHub] [cloudstack-primate] utchoang edited a comment on issue #99: [WIP] - Recurring Volume Snapshot Custom Action Form
utchoang edited a comment on issue #99: [WIP] - Recurring Volume Snapshot Custom Action Form URL: https://github.com/apache/cloudstack-primate/pull/99#issuecomment-574054835 @rhtyd 1. I have merged with the last master. 2. Timezone is not shown in the first place because I only allow it to be shown when the search text is entered. Reference: https://www.antdv.com/components/select. A lot of timezones listed could cause lag when entering other text inputs 3. I will fix and update it on the next PR of https://github.com/apache/cloudstack-primate/issues/87#issuecomment-573501920 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366197675 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" Review comment: @PaulAngus It's boilerplate from older upgrade rst file, I think we may want to review the whole post-upgrade cases and remove/edit as necessary. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] utchoang commented on issue #92: [WIP] - Register Template Action
utchoang commented on issue #92: [WIP] - Register Template Action URL: https://github.com/apache/cloudstack-primate/pull/92#issuecomment-574055707 @rhtyd I've already tested all. I'm sorry if the message in commit is unclear to you. Please review. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] rhtyd commented on issue #87: upgrade: upgrade systemvmtemplate for 4.14
rhtyd commented on issue #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#issuecomment-574055884 @PaulAngus @andrijapanicsb thanks for the review, the 4.13 upgrade rst file is a copy/paste of the 4.12, which was a copy/paste of 4.11... We've been using the new upgrade path/docs as boilerplate from the upgrade doc of the version before. I think, we probably need to review the post-upgrade docs and make suitable changes. I'm not sure how much of the boilterplate is valid at all now. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd opened a new issue #106: Add pod, cluster, host forms with option to dedicate that resource
rhtyd opened a new issue #106: Add pod, cluster, host forms with option to dedicate that resource URL: https://github.com/apache/cloudstack-primate/issues/106 Create add/create forms for pod, cluster, host with option to dedicate the resource to an account/domain. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #87: upgrade: upgrade systemvmtemplate for 4.14
ACSGitBot commented on issue #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#issuecomment-574104691 Build finished. You can review it at: https://acs-www.shapeblue.com/docs/pr87 Build Log Output: No log errors found to report. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #87: upgrade: upgrade systemvmtemplate for 4.14
ACSGitBot commented on issue #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#issuecomment-574104096 Your request had been received, i'll go and build the documentation and check the output log for errors. This shouldn't take long. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] andrijapanicsb commented on issue #87: upgrade: upgrade systemvmtemplate for 4.14
andrijapanicsb commented on issue #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#issuecomment-574104008 requesting docbuild This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd opened a new issue #107: Add Cluster form
rhtyd opened a new issue #107: Add Cluster form URL: https://github.com/apache/cloudstack-primate/issues/107 Add cluster form. Old UI->Infrastructure->Cluster -> Add. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366269717 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" + + If local storage paths are found to have a trailing forward slash, + remove it: + + .. parsed-literal:: + + $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + + +.. _ubuntu412: +.. _apt-repo412: + +Management Server +- + +Ubuntu +## + +If you are using Ubuntu, follow this procedure to upgrade your packages. If +not, skip to step :ref:`rhel411`. + +.. note:: + **Community Packages:** This section assumes you're using the
[GitHub] [cloudstack-documentation] andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366269484 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" + + If local storage paths are found to have a trailing forward slash, + remove it: + + .. parsed-literal:: + + $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + + +.. _ubuntu412: +.. _apt-repo412: + +Management Server +- + +Ubuntu +## + +If you are using Ubuntu, follow this procedure to upgrade your packages. If +not, skip to step :ref:`rhel411`. + +.. note:: + **Community Packages:** This section assumes you're using the
[GitHub] [cloudstack-documentation] andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366269620 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" + + If local storage paths are found to have a trailing forward slash, + remove it: + + .. parsed-literal:: + + $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + + +.. _ubuntu412: +.. _apt-repo412: + +Management Server +- + +Ubuntu +## + +If you are using Ubuntu, follow this procedure to upgrade your packages. If +not, skip to step :ref:`rhel411`. + +.. note:: + **Community Packages:** This section assumes you're using the
[GitHub] [cloudstack-documentation] andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366269667 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" + + If local storage paths are found to have a trailing forward slash, + remove it: + + .. parsed-literal:: + + $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + + +.. _ubuntu412: +.. _apt-repo412: Review comment: fixed This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment.
[GitHub] [cloudstack-documentation] andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366275485 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" + + If local storage paths are found to have a trailing forward slash, + remove it: + + .. parsed-literal:: + + $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; Review comment: https://github.com/apache/cloudstack/pull/3813 - check and approve This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to
[GitHub] [cloudstack-documentation] andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366275381 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" Review comment: https://github.com/apache/cloudstack/pull/3813 - check and approve This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd closed issue #60: Cluster Actions
rhtyd closed issue #60: Cluster Actions URL: https://github.com/apache/cloudstack-primate/issues/60 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] rhtyd opened a new issue #108: Add Host Form
rhtyd opened a new issue #108: Add Host Form URL: https://github.com/apache/cloudstack-primate/issues/108 Add host form: Old UI-> Infra tab -> Host tab -> Add host button  This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366269884 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" + + If local storage paths are found to have a trailing forward slash, + remove it: + + .. parsed-literal:: + + $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + + +.. _ubuntu412: +.. _apt-repo412: + +Management Server +- + +Ubuntu +## + +If you are using Ubuntu, follow this procedure to upgrade your packages. If +not, skip to step :ref:`rhel411`. + +.. note:: + **Community Packages:** This section assumes you're using the
[GitHub] [cloudstack-documentation] andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14
andrijapanicsb commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#discussion_r366269944 ## File path: source/upgrading/upgrade/upgrade-4.13.rst ## @@ -0,0 +1,360 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information# +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at +http://www.apache.org/licenses/LICENSE-2.0 +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. + +.. |version_to_upgrade| replace:: 4.13.x + +Upgrade Instruction from |version_to_upgrade| += + +This section will guide you from CloudStack |version_to_upgrade| to latest +CloudStack |release|. + +Any steps that are hypervisor-specific will be called out with a note. + +We recommend reading through this section once or twice before beginning +your upgrade procedure, and working through it on a test system before +working on a production system. + +.. note:: +The following upgrade instructions should be performed regardless of +hypervisor type. + +Overview of Upgrade Steps: + + +#. Check any customisations and integrations +#. Upload the |sysvm64-version| System VM template if not already using it. +#. Stop all running management servers +#. Backup CloudStack database (MySQL) +#. Upgrade 1st CloudStack management server +#. Update hypervisors specific dependencies +#. Restart 1st management server +#. Check that your upgraded environment works as expected +#. Upgrade and restart the remaining management servers + + +.. include:: _customisation_warnings.rst + +.. warning:: +If you are not already using the |sysvm64-version| System VM template you will need to +upgrade your System VM template prior to performing the upgrade of the +CloudStack packages. + +.. include:: _sysvm_templates.rst + +Packages repository +--- + +Most users of CloudStack manage the installation and upgrades of +CloudStack with one of Linux's predominant package systems, RPM or +APT. This guide assumes you'll be using RPM and Yum (for Red Hat +Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu). + +Create RPM or Debian packages (as appropriate) and a repository from +the |release| source, or check the Apache CloudStack downloads page at +http://cloudstack.apache.org/downloads.html +for package repositories supplied by community members. You will need +them for :ref:`ubuntu412` or :ref:`rhel412` and :ref:`kvm412` hosts upgrade. + +Instructions for creating packages from the CloudStack source are in the +`CloudStack Installation Guide`_. + +Database Preparation + + +Backup current database + +#. Stop your management server or servers. Run this on all management + server hosts: + + .. parsed-literal:: + + $ sudo service cloudstack-management stop + +#. If you are running a usage server or usage servers, stop those as well: + + .. parsed-literal:: + + $ sudo service cloudstack-usage stop + +#. Make a backup of your MySQL database. If you run into any issues or + need to roll back the upgrade, this will assist in debugging or + restoring your existing environment. You'll be prompted for your + password. + + .. parsed-literal:: + + $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql + $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql + +#. **(KVM Only)** If primary storage of type local storage is in use, the + path for this storage needs to be verified to ensure it passes new + validation. Check local storage by querying the cloud.storage\_pool + table: + + .. parsed-literal:: + + $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" + + If local storage paths are found to have a trailing forward slash, + remove it: + + .. parsed-literal:: + + $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + + +.. _ubuntu412: +.. _apt-repo412: + +Management Server +- + +Ubuntu +## + +If you are using Ubuntu, follow this procedure to upgrade your packages. If +not, skip to step :ref:`rhel411`. + +.. note:: + **Community Packages:** This section assumes you're using the
[GitHub] [cloudstack-documentation] andrijapanicsb commented on issue #87: upgrade: upgrade systemvmtemplate for 4.14
andrijapanicsb commented on issue #87: upgrade: upgrade systemvmtemplate for 4.14 URL: https://github.com/apache/cloudstack-documentation/pull/87#issuecomment-574116323 > We will have the new systemVM template API and UI. I suggest that we (you) need to get up to speed on how it works ASAP @rhtyd @andrijapanicsb //cc @borisstoyanov @Spaceman1984 Looking forward to show This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
