Feature Request: Option to Select Specific Nutanix Storage Container for VM Creation in IPI Installation

[cragr]

Version

$ openshift-install version
openshift-install 4.14.9
built from commit dfafb5ca972a6ed4677257aebfe4f284ac020830
release image quay.io/openshift-release-dev/ocp-release@sha256:f5eaf0248779a0478cfd83f055d56dc7d755937800a68ad55f6047c503977c44
release architecture amd64

Platform: nutanix

What happened?

When using the IPI method to deploy OpenShift on the Nutanix platform, the virtual machines are automatically created in the default Nutanix Storage Container, named 'SelfServiceContainer'

What you expected to happen?

I expected an optional configuration parameter in the install-config.yaml file that would allow the IPI installation to store the virtual machines in a custom storageContainer.

How to reproduce it (as minimally and precisely as possible)?

Create the installation configuration file

$ ./openshift-install create install-config --dir <installation_directory> 

Try modifying the install-config.yaml to specify the storage container location on the Nutanix platform where the VMs will be deployed.

platform:
  nutanix:
    apiVIP: 10.40.142.7 
    ingressVIP: 10.40.142.8 
    prismCentral:
      endpoint:
        address: your.prismcentral.domainname 
        port: 9440 
      password: <password> 
      username: <username> 
    prismElements:
    - endpoint:
        address: your.prismelement.domainname
        port: 9440
      uuid: 0005b0f1-8f43-a0f2-02b7-3cecef193712
    subnetUUIDs:
    - c7938dc6-7659-453e-a688-e26020c68e43
    clusterOSImage: http://example.com/images/rhcos-47.83.202103221318-0-nutanix.x86_64.qcow2 

Anything else we need to know?

The option to specify the storageContainer in the install-config.yaml is not listed in the official documentation Additional Nutanix configuration parameters

References

• Red Hat OpenShift Container Platform Installer Provisioned Installation on Nutanix AOS (AHV)
• Red Hat OpenShift on Nutanix
• Cloud Native: AOS 6.5 with Red Hat OpenShift Design

[ddcdk]

+1

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[cragr]

/remove-lifecycle stale

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[andrescolodrero]

/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.