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

BOSH group name is often too long to generate an availability set name automatically from #209

Closed
dsboulder opened this issue Sep 22, 2016 · 3 comments
Labels

Comments

@dsboulder
Copy link
Member

An Avail Set name can only be 80 characters, but BOSH generates a group: field automatically that can exceed this limit easily. For example, a compilation VM has the following automatic name:
bosh_director_name-deployment_name-compilation-RANDOM_GUID_FROM_BOSH. Since BOSH inserts a GUID, the deployment name and director name have to be fairly short or things break.

My proposed solution would be to make the AvailSet name be az-MD5-of-bosh-provided-group, if the name is longer than azure allows. What do you think?

@dsboulder
Copy link
Member Author

For background: BOSH recently introduced this group: field in the env hash. Dmitriy wanted the name to be as unique as possible, so he concatenates the DirectorName + DeploymentName + JobName. Sadly this can be quite long, especially with automatically generated compilation VM names, so I'm hoping the CPI can handle the occasional long group name.

@AbelHu
Copy link
Contributor

AbelHu commented Sep 22, 2016

@dsboulder @cppforlife On Azure the length of the availability set name must be between 1 and 80 characters. env.bosh.group which is generated by BOSH director may be too long. CPI will truncate the name to the following format az-MD5-[LAST-40-CHARACTERS-OF-GROUP] if the length of env.bosh.group is greater than 80.

@AbelHu AbelHu added Done and removed in-progress labels Sep 22, 2016
@AbelHu
Copy link
Contributor

AbelHu commented Sep 22, 2016

Fix it in this commit

@AbelHu AbelHu closed this as completed Sep 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants