[BSC#1107545] Migrate subnet pillar name v2.1 -> v3

SUSE / velum

Dashboard for CaaS Platform clusters (v1, v2 and v3)

https://www.suse.com/

Apache License 2.0

54 stars 30 forks source link

[BSC#1107545] Migrate subnet pillar name v2.1 -> v3 #651

Closed bear454 closed 5 years ago

bear454 commented 5 years ago

In v3, the subnet ID is stored in the same Pillar for all public clouds, then arranged into the appropriate pillar structure by InternalApi::V1::PillarsController#cloud_framework_contents

In v2.1, AWS had a different name for the subnet ID (for Azure & GCP, the name is consistent); therefore it is necessary to modify the pillar, if already assigned, in order to prevent losing the customer's entered data.

Backport of https://github.com/kubic-project/velum/pull/650

bear454 commented 5 years ago

Bug 1107545 - migration from v2.1 to v3 will lose AWS subnet id

kiall commented 5 years ago

Ah, @jordimassaguerpla pointed me at the master branch PR - https://github.com/kubic-project/velum/pull/650

jordimassaguerpla commented 5 years ago

Adding the no bugzilla ref label. This is in the commit title. May our regexp not cope with capital BSC?

jordimassaguerpla commented 5 years ago

This is ready to be released

bear454 commented 5 years ago

@MaximilianMeister : please check the updates are properly handling the patch, and if you could point me to some doc where the procedure for that patch is explained, I'd appreciate it.