-
Notifications
You must be signed in to change notification settings - Fork 309
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
Please document new VM types #1202
Comments
We've recently increased the NATs VM size, see #1196. The cloud-config examples in https://github.com/cloudfoundry/cf-deployment/tree/main/iaas-support are indeed not up-to date. We'll plan a story to include the new "medium" type. With bosh-bootloader, you should have the "medium" type on all infrastructures. Best Regards, Jochen. |
Sorry, I figured that the infrastructure was immaterial. I'm developing a new CPI for LXD. After not finding the medium VM size, I noticed the release indicating medium was v43, so I just dropped down to the latest of v42. Deployment worked fine, so that was my immediate goal. It will be appreciated once the medium size gets documented. Thanks! |
Examples for cloud-config have been updated, closing this issue. |
What is this issue about?
In your own words, describe the issue.
What steps/actions led to the issue?
I tried to deploy the latest version of CF using the existing documentation (specifically: https://github.com/cloudfoundry/cf-deployment/blob/main/texts/on-cloud-configs.md#vm-types).
Deployment errors because VM type
medium
does not exist.Side note: I like the table setup, for example, that exists for OpenStack -- especially since it suggests the ephemeral disk size. (see: https://github.com/cloudfoundry/cf-deployment/blob/main/iaas-support/openstack/README.md)
The
medium
VM doesn't appear to be in any example cloud-configs either.What version of cf-deployment are you using?
v43.1.0
Please include the
bosh deploy...
command, including all the operations files (plus any experimental operation files you're using):N/A
Please provide output that helps describe the issue:
What IaaS is this issue occurring on?
N/A
Is there anything else unique or special about your setup?
No.
Tag your pair, your PM, and/or team!
It's helpful to tag a few other folks on your team or your team alias in case we need to follow up later.
The text was updated successfully, but these errors were encountered: