Thanks to visit codestin.com
Credit goes to github.com

Skip to content

engine/schema: create default network offering for vpc tier with conserve_mode=1 for fresh installation #10744

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 9, 2025

Conversation

weizhouapache
Copy link
Member

Description

with #8309, he default vpc offering of upgraded environments have been updated to conserve_mode=1.
but for fresh installation, the default vpc offering still has conserve_mode=0.

This PR fixes it.

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)
  • build/CI
  • test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

Bug Severity

  • BLOCKER
  • Critical
  • Major
  • Minor
  • Trivial

Screenshots (if appropriate):

How Has This Been Tested?

How did you try to break this feature and the system with this change?

@weizhouapache weizhouapache changed the title engine/schema: Re-apply #8309: VPC: update default network offering for vpc tier to conserve_mode=1 engine/schema: create default network offering for vpc tier with conserve_mode=1 for fresh installation Apr 17, 2025
@weizhouapache weizhouapache force-pushed the 4.20-vpc-conserve-mode branch from 702472b to 53a1c88 Compare April 17, 2025 08:07
Copy link

codecov bot commented Apr 17, 2025

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 16.01%. Comparing base (207a2c1) to head (53a1c88).
Report is 54 commits behind head on 4.20.

Files with missing lines Patch % Lines
...tack/engine/orchestration/NetworkOrchestrator.java 0.00% 1 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##               4.20   #10744      +/-   ##
============================================
- Coverage     16.02%   16.01%   -0.01%     
+ Complexity    13124    13120       -4     
============================================
  Files          5652     5652              
  Lines        495921   495921              
  Branches      60053    60053              
============================================
- Hits          79463    79445      -18     
- Misses       407593   407612      +19     
+ Partials       8865     8864       -1     
Flag Coverage Δ
uitests 4.00% <ø> (ø)
unittests 16.86% <0.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@DaanHoogland DaanHoogland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

clgtm

@weizhouapache weizhouapache marked this pull request as ready for review April 17, 2025 13:23
@weizhouapache
Copy link
Member Author

@blueorangutan package

@blueorangutan
Copy link

@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.

@blueorangutan
Copy link

Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 13095

@DaanHoogland
Copy link
Contributor

@blueorangutan test

@blueorangutan
Copy link

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

@blueorangutan
Copy link

[SF] Trillian Build Failed (tid-13043)

@blueorangutan
Copy link

[SF] Trillian test result (tid-13051)
Environment: kvm-ol8 (x2), Advanced Networking with Mgmt server ol8
Total time taken: 57759 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr10744-t13051-kvm-ol8.zip
Smoke tests completed. 141 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test Result Time (s) Test File

Copy link
Contributor

@harikrishna-patnala harikrishna-patnala left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@blueorangutan
Copy link

[SF] Trillian Build Failed (tid-13105)

@rohityadavcloud rohityadavcloud added this to the 4.20.1 milestone May 9, 2025
@rohityadavcloud
Copy link
Member

rohityadavcloud commented May 9, 2025

Is this good to merge @weizhouapache @Pearl1594 @DaanHoogland ?

@DaanHoogland
Copy link
Contributor

@Pearl1594 , do you want more testing on this?

Copy link
Contributor

@Pearl1594 Pearl1594 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

code LGTM. But I wonder if this should go into 4.19

@weizhouapache
Copy link
Member Author

code LGTM. But I wonder if this should go into 4.19

@Pearl1594
I can create another PR for 4.19, if you think it is needed

(for DB issue fixed in both 4.19.3 and 4.20.1, we need to create two separated PRs)

@Pearl1594
Copy link
Contributor

I think it would be good to have in 4.19 as well .. but this is good to merge

@Pearl1594 Pearl1594 merged commit 7e2aa0e into apache:4.20 May 9, 2025
25 of 26 checks passed
@@ -595,7 +595,7 @@ public void doInTransactionWithoutResult(final TransactionStatus status) {
if (_networkOfferingDao.findByUniqueName(NetworkOffering.DefaultIsolatedNetworkOfferingForVpcNetworks) == null) {
offering = _configMgr.createNetworkOffering(NetworkOffering.DefaultIsolatedNetworkOfferingForVpcNetworks,
"Offering for Isolated VPC networks with Source Nat service enabled", TrafficType.Guest, null, false, Availability.Optional, null,
defaultVPCOffProviders, true, Network.GuestType.Isolated, false, null, false, null, false, false, null, false, null, true, true, false, false, null, null, null,true, null, null, false);
defaultVPCOffProviders, true, Network.GuestType.Isolated, false, null, true, null, false, false, null, false, null, true, true, false, false, null, null, null,true, null, null, false);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so only this needs backporting to 4.19?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this part, and also the SQL to 4.19.2->4.19.3 upgrade schema

@DaanHoogland DaanHoogland deleted the 4.20-vpc-conserve-mode branch May 9, 2025 09:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants