-
Notifications
You must be signed in to change notification settings - Fork 34
Add boot-from-volume support to server controller #634
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| # Example of creating a server that boots from a Cinder volume instead of an image. | ||
| # This is the boot-from-volume (BFV) pattern. | ||
| # | ||
| # Prerequisites: | ||
| # - A bootable volume created from an image (see openstack_v1alpha1_volume_bootable.yaml) | ||
| # - Network, subnet, and port resources | ||
| # - A flavor | ||
| --- | ||
| apiVersion: openstack.k-orc.cloud/v1alpha1 | ||
| kind: Server | ||
| metadata: | ||
| name: server-boot-from-volume-sample | ||
| spec: | ||
| cloudCredentialsRef: | ||
| cloudName: openstack | ||
| secretName: openstack-clouds | ||
| managementPolicy: managed | ||
| resource: | ||
| # Note: No imageRef - booting from volume instead | ||
| bootVolume: | ||
| volumeRef: bootable-volume-sample | ||
| flavorRef: server-sample | ||
| ports: | ||
| - portRef: server-sample | ||
| availabilityZone: nova |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| --- | ||
| apiVersion: kustomize.config.k8s.io/v1beta1 | ||
| kind: Kustomization | ||
| resources: | ||
| - volume.yaml | ||
| - server.yaml |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| --- | ||
| # Server that boots from a volume instead of an image | ||
| apiVersion: openstack.k-orc.cloud/v1alpha1 | ||
| kind: Server | ||
| metadata: | ||
| name: server | ||
| spec: | ||
| cloudCredentialsRef: | ||
| cloudName: openstack | ||
| secretName: cloud-config | ||
| managementPolicy: managed | ||
| resource: | ||
| # No imageRef - booting from volume | ||
| bootVolume: | ||
| volumeRef: boot-volume | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I believe we're missing a few refs in
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @mandre should I add them in this patch or should we have a dedicated PR for that as it seems many references are missing?
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Preferably in a different patch. |
||
| flavorRef: flavor | ||
| ports: | ||
| - portRef: port | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| --- | ||
| # Bootable volume created from the cirros image | ||
| apiVersion: openstack.k-orc.cloud/v1alpha1 | ||
| kind: Volume | ||
| metadata: | ||
| name: boot-volume | ||
| spec: | ||
| cloudCredentialsRef: | ||
| cloudName: openstack | ||
| secretName: cloud-config | ||
| managementPolicy: managed | ||
| resource: | ||
| size: 1 | ||
| imageRef: cirros |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because of this change, we'll have to cut a new major release since it's not backward compatible. This settles the discussion in #632.