[GitHub] [cloudstack-documentation] DaanHoogland commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14

[GitBox]

DaanHoogland commented on a change in pull request #87: upgrade: upgrade 
systemvmtemplate for 4.14
URL: 
https://github.com/apache/cloudstack-documentation/pull/87#discussion_r373344197
 
 

 ##
 File path: source/conf.py
 ##
 @@ -20,13 +20,13 @@
 # -- Project information -
 
 project = 'Apache CloudStack'
-copyright = '2018, Apache Foundation'
+copyright = '2020, Apache Foundation'
 
 Review comment:
   didn't think of it like that, but you are right @GabrielBrascher and i think 
we should claim further back than 2018. we cstill have the older docs hosted so 
we can still check and add it here


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 edited a comment on issue #7: [WIP] Feature/vm wizard

[GitBox]

utchoang edited a comment on issue #7: [WIP] Feature/vm wizard
URL: https://github.com/apache/cloudstack-primate/pull/7#issuecomment-580535882
 
 
   @iceteabottle Thank you so much. 
   @svenvogel I will start working on it after @rhtyd finishes merging this PR.


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 #7: [WIP] Feature/vm wizard

[GitBox]

utchoang commented on issue #7: [WIP] Feature/vm wizard
URL: https://github.com/apache/cloudstack-primate/pull/7#issuecomment-580535882
 
 
   @iceteabottle thank you so much. 
   @svenvogel I will start working on it after @rhtyd finishes merging this PR


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 edited a comment on issue #7: [WIP] Feature/vm wizard

[GitBox]

utchoang edited a comment on issue #7: [WIP] Feature/vm wizard
URL: https://github.com/apache/cloudstack-primate/pull/7#issuecomment-580535882
 
 
   @iceteabottle Thank you so much. 
   @svenvogel I will start working on it after @rhtyd finishes merging this PR


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] GabrielBrascher commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14

[GitBox]

GabrielBrascher commented on a change in pull request #87: upgrade: upgrade 
systemvmtemplate for 4.14
URL: 
https://github.com/apache/cloudstack-documentation/pull/87#discussion_r373274024
 
 

 ##
 File path: source/conf.py
 ##
 @@ -20,13 +20,13 @@
 # -- Project information -
 
 project = 'Apache CloudStack'
-copyright = '2018, Apache Foundation'
+copyright = '2020, Apache Foundation'
 
 Review comment:
   I am totally OK with the 2020 copyright, but I would like to raise a point 
of view regarding the use of copyright.
   
   Sometimes I ask myself if we should update the copyright date, as the date 
establishes how far back the claim was made. At least I think this is the 
meaning :slightly_smiling_face:.
   
   If that is right, this would mean that when the date is updated, one is no 
longer claiming the copyright for the original date. One choice would be to 
have something as `Copyright © 2018-2019`.
   
   An example can be seen at http://httpd.apache.org/ were it is claimed from 
the original date to the latest update `Copyright © 1997-2020 The Apache 
Software Foundation.`


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: [PROPOSE] RM for 4.14

[Andrija Panic]

Hi all,

with regards to the freeze date, it seems that we'll have to push it back a
bit, again.

I have not had time to do much myself (will rejoin the effort starting from
Monday), but I can see that we have reduced total number of Milestone items
(for both 4.14 and 4.13.1) by 1/3 (we went from ~60 to ~40) - this leaves
us with roughly another **2 weeks** to finish off the remaining milestone
items. Next time I might propose a very "pessimistic" dates, instead of
overly optimistic (that original dates I proposed seem to be), to avoid
postponing the release by this amount of time.

I hope that everyone finds this OK - at the end of the day, WHAT we release
it what's going to be remembered, not WHEN we released it.
As usual, I will follow up here once we are close to the freeze date.

If anyone has any concerns, please let me know.

Thanks,
Andrija


On Wed, 22 Jan 2020 at 15:18, Boris Stoyanov 
wrote:

> +1, I'd really love to see some of the PRs with the 4.14 milestone in but
> I need more time to test them.
>
> Bobby.
>
> On 22.01.20, 13:22, "Andrija Panic"  wrote:
>
> Hi all,
>
> I’d like to push back the freeze date for at least a week vs. what's
> previously proposed since I’ve been contacted by a few people who have
> some
> PRs they like to get closed off.  If of any interest, I’m away
> 27th-31th
> January (but will check emails occasionally).
>
> I'll follow-up here on the freeze date.
>
> Thanks,
> Andrija
>
>
>
> boris.stoya...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
> On Fri, 20 Dec 2019 at 16:30, Andrija Panic 
> wrote:
>
> > Hi guys
> >
> > Sven,
> > read the original email pls (last part of it) - we will need to fix
> some
> > bugs, test other people fixes as applicable, etc - "usual" day to dev
> > stuff.
> >
> > Gabriel,
> >
> > thx for the help (in advance! ), let's aim to improve the page
> during this
> > release, I'll surely raise this if/when I see a problem (considering
> this
> > is my first time but I will also have help from other experienced
> guys as
> > already explained).
> >
> > As for the LTS discussion, I would add that there is an "awful" lot
> of new
> > stuff planned for this releases, making it a more suitable candidate
> for
> > LTS then for non-LTS, if that makes sense.
> >
> > Anyway, looking forward working with all you guys on this one!
> >
> > Best,
> > Andrija
> >
> >
> >
> > On Fri, 20 Dec 2019, 12:24 Sven Vogel,  wrote:
> >
> >> @Paul @Gabriel
> >>
> >>
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+Procedure
> >>
> >>
> >> This seems the link for the release process. I read them. how is it
> >> possible to engage in this process? I don’t know. Is it useful. I
> would
> >> come more into and learn it.
> >>
> >>
> >>
> >>
> >> Von meinem iPhone gesendet
> >>
> >>
> >> __
> >>
> >> 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
> >>
> >> Support:
> >> +49 341 42649 555
> >>
> >> Zertifiziert nach:
> >> ISO/IEC 27001:2013
> >> DIN EN ISO 9001:2015
> >> DIN ISO/IEC 2-1:2011
> >>
> >> ISAE 3402 Typ II Assessed
> >>
> >> EWERK-Blog | LinkedIn<
> >> https://www.linkedin.com/company/ewerk-group> | Xing<
> >> https://www.xing.com/company/ewerk> | Twitter<
> >> https://twitter.com/EWERK_Group> | Facebook<
> >> https://de-de.facebook.com/EWERK.IT/>
> >>
> >> Mit Handelsregistereintragung vom 09.07.2019 ist die EWERK RZ GmbH
> auf
> >> die EWERK IT GmbH verschmolzen und firmiert nun gemeinsam unter dem
> Namen:
> >> EWERK DIGITAL GmbH, für weitere Informationen klicken Sie hier<
> >> https://www.ewerk.com/ewerkdigital>.
> >>
> >> 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 

[GitHub] [cloudstack-primate] iceteabottle commented on issue #7: [WIP] Feature/vm wizard

[GitBox]

iceteabottle commented on issue #7: [WIP] Feature/vm wizard
URL: https://github.com/apache/cloudstack-primate/pull/7#issuecomment-580286303
 
 
   > @utchoang can you resume here please?
   
   @utchoang please see my checklist 
https://github.com/apache/cloudstack-primate/pull/7#issue-333054299
   
   @rhtyd please merge this PR so @utchoang can finish this feature.
   
   Thanks for the cooperation in this project. I'm sorry that I have to 
discontinue my work here.


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] svenvogel commented on issue #7: [WIP] Feature/vm wizard

[GitBox]

svenvogel commented on issue #7: [WIP] Feature/vm wizard
URL: https://github.com/apache/cloudstack-primate/pull/7#issuecomment-580283807
 
 
   @utchoang can you resume here please?


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] iceteabottle commented on issue #7: [WIP] Feature/vm wizard

[GitBox]

iceteabottle commented on issue #7: [WIP] Feature/vm wizard
URL: https://github.com/apache/cloudstack-primate/pull/7#issuecomment-580279528
 
 
   Add SSH keypair selection.
   
   ![Bildschirmfoto 2020-01-30 um 15 30 
03](https://user-images.githubusercontent.com/13260952/73458354-6c928e00-4375-11ea-83a9-f0c127e10eef.png)
   


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 #123: [WIP] - Add pod form

[GitBox]

rhtyd commented on issue #123: [WIP] - Add pod form
URL: 
https://github.com/apache/cloudstack-primate/pull/123#issuecomment-580214508
 
 
   @RitchieVincent can you check and fix the popover issues, use placeholder 
for api description instead?


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 #122: [WIP] - Add host form

[GitBox]

rhtyd commented on issue #122: [WIP] - Add host form
URL: 
https://github.com/apache/cloudstack-primate/pull/122#issuecomment-580214558
 
 
   @RitchieVincent can you check and fix the popover issues, use placeholder 
for api description instead?


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 #114: [WIP] - Cluster form

[GitBox]

rhtyd commented on issue #114: [WIP] - Cluster form
URL: 
https://github.com/apache/cloudstack-primate/pull/114#issuecomment-580214530
 
 
   @RitchieVincent can you check and fix the popover issues, use placeholder 
for api description instead?


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

[GitBox]

ACSGitBot commented on issue #87: upgrade: upgrade systemvmtemplate for 4.14
URL: 
https://github.com/apache/cloudstack-documentation/pull/87#issuecomment-580149885
 
 
   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

[GitBox]

ACSGitBot commented on issue #87: upgrade: upgrade systemvmtemplate for 4.14
URL: 
https://github.com/apache/cloudstack-documentation/pull/87#issuecomment-580149247
 
 
   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] rhtyd commented on issue #87: upgrade: upgrade systemvmtemplate for 4.14

[GitBox]

rhtyd commented on issue #87: upgrade: upgrade systemvmtemplate for 4.14
URL: 
https://github.com/apache/cloudstack-documentation/pull/87#issuecomment-580149205
 
 
   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-documentation] rhtyd commented on a change in pull request #87: upgrade: upgrade systemvmtemplate for 4.14

[GitBox]

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_r372814521
 
 

 ##
 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:`ubuntu413` or :ref:`rhel413` and :ref:`kvm413` 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/"';
+
+
+.. _ubuntu413:
+.. _apt-repo413:
+
+Management Server
+-
+
+Ubuntu
+##
+
+If you are using Ubuntu, follow this procedure to upgrade your packages. If
+not, skip to step :ref:`rhel413`.
+
+.. 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

[GitBox]

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_r372811540
 
 

 ##
 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:`ubuntu413` or :ref:`rhel413` and :ref:`kvm413` 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/"';
+
+
+.. _ubuntu413:
+.. _apt-repo413:
+
+Management Server
+-
+
+Ubuntu
+##
+
+If you are using Ubuntu, follow this procedure to upgrade your packages. If
+not, skip to step :ref:`rhel413`.
+
+.. 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

[GitBox]

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_r372809835
 
 

 ##
 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:`ubuntu413` or :ref:`rhel413` and :ref:`kvm413` 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/"';
+
+
+.. _ubuntu413:
+.. _apt-repo413:
+
+Management Server
+-
+
+Ubuntu
+##
+
+If you are using Ubuntu, follow this procedure to upgrade your packages. If
+not, skip to step :ref:`rhel413`.
+
+.. 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

[GitBox]

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_r372808871
 
 

 ##
 File path: source/upgrading/upgrade/_sysvm_templates.rst
 ##
 @@ -74,7 +72,7 @@ Update System-VM templates
|||
|| Format: QCOW2  |
|||
-   || OS Type: Debian GNU/Linux 7.0 (64-bit) (or the |
+   || OS Type: Debian GNU/Linux 9.0 (64-bit) (or the |
 
 Review comment:
   Changed back to 7.0


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

[GitBox]

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_r372808734
 
 

 ##
 File path: source/upgrading/upgrade/_sysvm_templates.rst
 ##
 @@ -48,9 +48,7 @@ Update System-VM templates
|||
|| Format: VHD|
|||
-   || OS Type: Debian GNU/Linux 7.0 (64-bit) (or the |
-   || highest Debian release number available in the |
-   || dropdown)  |
+   || OS Type: Other Linux 64-bit|
|||
|| Extractable: no|
|||
 
 Review comment:
   not needed, fixed the template OS type name.


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

[GitBox]

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_r372808503
 
 

 ##
 File path: source/upgrading/upgrade/_sysvm_templates.rst
 ##
 @@ -48,9 +48,7 @@ Update System-VM templates
|||
|| Format: VHD|
|||
-   || OS Type: Debian GNU/Linux 7.0 (64-bit) (or the |
-   || highest Debian release number available in the |
-   || dropdown)  |
+   || OS Type: Other Linux 64-bit|
 
 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

[GitBox]

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_r372806774
 
 

 ##
 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:
   Since PR was merged, I'll remove the workaround ref from the release notes.


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