backport #10744: engine/schema: create default network offering for vpc tier with conserve_mode=1 for fresh installation#10843
Conversation
…erve_mode=1 for fresh installation (apache#10744)
|
@blueorangutan package |
|
@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 13462 |
|
@blueorangutan test |
|
@DaanHoogland a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-13363)
|
|
@blueorangutan test keepEnv |
|
[SF] Trillian test result (tid-13400)
|
|
DB checked after installation. |
…erve_mode=1 for fresh installation (apache#10744) (apache#10843) Co-authored-by: Wei Zhou <weizhou@apache.org>
Description
This PR… backports #10744.
Only new installations of 4.19.x will not have conservemode enabled by default vor VPCs. Upgrades from earlier versions will be alright. In order to make sure conserve mode is enabled for VPC-tiers, either create a clone of the default guestnetwork offering with conservemode enabled or execute the following sql:
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?