[CLOUDSTACK-10302] Create database path upgrade from 4.11.0.0 to 4.12.0.0

[rafaelweingartner]

No description provided.

[yadvr]

LGTM, standard boilerplate.
Should we also create one for 4.11.1.0; the upgrade path could be like this: 4.11.0.0->4.11.1.0->4.12.0.0 ?

[yadvr]

@blueorangutan package

[blueorangutan]

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

[yadvr]

@rafaelweingartner another comment - should this have a JIRA id, or just a general thought for several administrative-ish work should we have either a catchall jira ticket or decide to have no ticket for such tasks at all?

[rafaelweingartner]

@rhtyd I have no arguments against or pro Jira tickets for this specific case. I can create one to use here if we decided to do so.
To create the other upgrade path, I believe a different PR would be better, what do you think?

[blueorangutan]

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1727

[borisstoyanov]

LGTM

[wido]

LGTM

[DaanHoogland]

let's not have jira tickets if we don't need them.
@blueorangutan test

[blueorangutan]

@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[rafaelweingartner]

@DaanHoogland I agree, but this topic needs to be discussed out of Github in our mailing list. There is also another PR of mine that I only created because someone asked me .

[blueorangutan]

Trillian test result (tid-2286)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 27115 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2463-t2286-kvm-centos7.zip
Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py
Smoke tests completed. 67 look OK, 0 have error(s)
Only failed tests results shown below:

Test	Result	Time (s)	Test File