Skip to content
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

Create Nova flavors for Octavia #200

Merged
merged 1 commit into from
Nov 20, 2023

Conversation

gthiemonge
Copy link
Contributor

Add support for system-scope Compute client.

Ensure that 2 nova flavors are created:

  • octavia-amphora: 1 vCPU, 1GB RAM, 3GB disk
  • octavia-amphora-4vcpus: 4 vCPU, 4GB RAM, 3GB disk

Flavors in previous releases used non-UUIDs as ID (octavia_65, etc...) and didn't have a clear naming convention (amphora*, octavia*). Don't force the ID of the new flavors, let Nova generates them.

octavia-amphora is the default flavor in Octavia

@openshift-ci openshift-ci bot requested review from gibizer and viroel November 20, 2023 10:22
Copy link
Contributor

openshift-ci bot commented Nov 20, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gthiemonge

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Name: "octavia-amphora",
VCPUs: 1,
RAM: 1024,
Disk: gophercloud.IntToPointer(3),
Copy link
Collaborator

@weinimo weinimo Nov 20, 2023

Choose a reason for hiding this comment

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

As you pointed out in a discussion downsteam already, 3 GB might not be enough. I guess we can leave it like this for now, but it would probably be good to add at least a TODO comment to verify this is enough, or maybe we can make this configurable between a certain range >3.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes, the other solution would be to enable log offloading and disable local disk storage by default, in that case 3GB would be enough

Copy link
Collaborator

@weinimo weinimo left a comment

Choose a reason for hiding this comment

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

lgtm in general

}
r.Log.Info(fmt.Sprintf("Using default flavor \"%s\"", defaultFlavorID))

err = r.generateServiceConfigMaps(ctx, instance, helper, &configMapVars, networkID, defaultFlavorID)
Copy link
Collaborator

Choose a reason for hiding this comment

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

I wonder whether we should create a new struct that contains networkID, defaultFlavorID and potentally more things and use that instead here in order to keep the list of arguments short.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes I can do that

}

isPublic := false
defaultFlavorsCreateOpts := []flavors.CreateOpts{
Copy link
Collaborator

Choose a reason for hiding this comment

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

Even though the name is pretty much self explanatory we should probably add a Description to each flavor as well. The description of the first flavor should mention that this is the default flavor.

Add support for system-scope Compute client.

Ensure that 2 nova flavors are created:
- octavia-amphora: 1 vCPU, 1GB RAM, 3GB disk
- octavia-amphora-4vcpus: 4 vCPU, 4GB RAM, 3GB disk

Flavors in previous releases used non-UUIDs as ID (octavia_65, etc...)
and didn't have a clear naming convention (amphora*, octavia*). Don't
force the ID of the new flavors, let Nova generates them.

octavia-amphora is the default flavor in Octavia
@weinimo
Copy link
Collaborator

weinimo commented Nov 20, 2023

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Nov 20, 2023
@openshift-merge-bot openshift-merge-bot bot merged commit 37c8c91 into openstack-k8s-operators:main Nov 20, 2023
3 checks passed
@gthiemonge gthiemonge deleted the flavor branch June 17, 2024 07:10
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.

2 participants