GitHub user rhtyd opened a pull request:

    https://github.com/apache/cloudstack/pull/1983

    [4.10/blocker] Upgrade4920to41000: Migrate systemvmtemplate for 4.10

    - Adds systemvm migration for upgrading to 4.10
    - Remove systemvm migration block for upgrading from 4.5 or below, this
      ensures that pre 4.6 users are not required to seed 4.6 systemvmtemplate
      to upgrade to 4.10, but can directly seed a 4.10 systemvmtemplate
    
    Pinging for review - @karuturi @PaulAngus @abhinandanprateek @DaanHoogland 
@koushik-das @borisstoyanov @wido and others.
    
    Note: for the 4.10 release systemvmtemplates are not available on 
http://cloudstack.apt-get.eu/systemvm yet so I've used URLs from 
packages.shapeblue.com.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shapeblue/cloudstack 
4.10-systemvmtemplate-upgrade-fix

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1983.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1983
    
----
commit 0cec5f57067a43478db37074620727d105467d77
Author: Rohit Yadav <rohit.ya...@shapeblue.com>
Date:   2017-03-03T08:16:45Z

    Upgrade4920to41000: Migrate systemvmtemplate for 4.10
    
    - Adds systemvm migration for upgrading to 4.10
    - Remove systemvm migration block for upgrading from 4.5 or below, this
      ensures that pre 4.6 users are not required to seed 4.6 systemvmtemplate
      to upgrade to 4.10, but can directly seed a 4.10 systemvmtemplate
    
    Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com>

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to