Add toggle to disable humam readable for Openstack

[shinji62]

Add ops-files to desactivate humam readabl for Openstack.

This is actually needed when using openstack as cloud-provider in Kubernetes (ala Kubo).

[cfdreddbot]

Hey shinji62!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA.

[shinji62]

@cppforlife

[jhiemer]

@shinji62 wouldn't it be better to ask the OpenStack CPI team to change then separator between the name and the id into something like "-", which would keep the human readable names and also be allowed in context of DNS?

(facing the same problem as you currently).

[shinji62]

@jhiemer This is not only kubo related. So if people would like to desactivate this behavior. this PR will help

[jhiemer]

@shinji62 I am aware of that. But then it will be a much bigger problem with other deployments also relying on DNS in future, or?

[shinji62]

Agree, but again this is just to desactivate it.

[dpb587-pivotal]

🔗 Some related Slack discussion about this...

• cloudfoundry#bosh
• cloudfoundry#bosh

Original error message...

Unable to register node "worker/925f11f3-80af-4844-a00e-f0af521779d1" with API server: Node "worker/925f11f3-80af-4844-a00e-f0af521779d1" is invalid: metadata.name: Invalid value: "worker/925f11f3-80af-4844-a00e-f0af521779d1": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is 'a-z0-9?(.a-z0-9?)*')

[shinji62]

@dpb587-pivotal Please see https://cloudfoundry.slack.com/archives/C0SBBBJSZ/p1514918952000286

Could be good to have this merged.