[GitHub] cloudstack issue #1951: CLOUDSTACK-9792: Add upgrade path for 4.9.3.0

Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1951 Ping @karuturi --- 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

[GitHub] cloudstack issue #1951: CLOUDSTACK-9792: Add upgrade path for 4.9.3.0

Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1951 ping @karuturi let's merge this? --- 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

[GitHub] cloudstack issue #1951: CLOUDSTACK-9792: Add upgrade path for 4.9.3.0

Github user syed commented on the issue: https://github.com/apache/cloudstack/pull/1951 Thanks @rhtyd for confirming. LGTM :+1: --- 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 e

[GitHub] cloudstack issue #1951: CLOUDSTACK-9792: Add upgrade path for 4.9.3.0

Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1951 @syed yes there is no problem I see, with `INSERT IGNORE` we can have this db change in both paths resulting in same final state. --- If your project is set up for it, you can reply to this email

[GitHub] cloudstack issue #1951: CLOUDSTACK-9792: Add upgrade path for 4.9.3.0

Github user syed commented on the issue: https://github.com/apache/cloudstack/pull/1951 @rhtyd If I understand correctly if we add the DB changes in 4.9.2->4.9.3 then after forward merging, upgrade from 4.9.2->4.10.0 should not have any problems with idempotency correct? --- If you

[GitHub] cloudstack issue #1951: CLOUDSTACK-9792: Add upgrade path for 4.9.3.0

Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1951 @koushik-das there is plan for 4.9.3, though the db schema change to insert/update the hypervisor capability need to go into 4.10.0 either with this PR carefully fwd-merged (which I can help with)

[GitHub] cloudstack issue #1951: CLOUDSTACK-9792: Add upgrade path for 4.9.3.0

Github user koushik-das commented on the issue: https://github.com/apache/cloudstack/pull/1951 I already see schema-4920to41000.sql and the corresponding cleanup file in master. So how will this fit in the overall scheme? Is there any plans for 4.9.3? --- If your project is set up f

[GitHub] cloudstack issue #1951: CLOUDSTACK-9792: Add upgrade path for 4.9.3.0

Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1951 Requesting for review - @DaanHoogland @abhinandanprateek @karuturi @koushik-das @syed --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as we

[GitHub] cloudstack issue #1951: CLOUDSTACK-9792: Add upgrade path for 4.9.3.0

Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1951 Thanks @borisstoyanov @karuturi ping --- 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

[GitHub] cloudstack issue #1951: CLOUDSTACK-9792: Add upgrade path for 4.9.3.0

Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/1951 Just want to confirm it fresh installs and upgrades the DB to 4.9.3. will cancel the run after as I'm planning to do an upgrade scenario as well. Thanks @rhtyd --- If your project i

[GitHub] cloudstack issue #1951: CLOUDSTACK-9792: Add upgrade path for 4.9.3.0

Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1951 @borisstoyanov an explicit integration test is not necessary if Travis passes, since all changes are around db upgrade/version. --- If your project is set up for it, you can reply to this email a

[GitHub] cloudstack issue #1951: CLOUDSTACK-9792: Add upgrade path for 4.9.3.0

Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1951 @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests --- If your project is set up for it, you can reply to this email and have your

[GitHub] cloudstack issue #1951: CLOUDSTACK-9792: Add upgrade path for 4.9.3.0

Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/1951 @blueorangutan test --- 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 w

[GitHub] cloudstack issue #1951: CLOUDSTACK-9792: Add upgrade path for 4.9.3.0

Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1951 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-504 --- 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 d

[GitHub] cloudstack issue #1951: CLOUDSTACK-9792: Add upgrade path for 4.9.3.0

Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1951 @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. --- If your project is set up for it, you can reply to this email and have your re

[GitHub] cloudstack issue #1951: CLOUDSTACK-9792: Add upgrade path for 4.9.3.0

Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/1951 @blueorangutan package --- 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 an