Description of problem: Presently to support automatic provisioning of PVs from OpenStack cinder volumes, one has to name all VMs created within OpenStack with their hostnames. This doesn't allow semantic naming of VMs. As a user I would like to name my machines in a way that makes it easier to understand what each VM is for. Using hostname doesn't provide necessary meaning to do that. Version-Release number of selected component (if applicable): 3.3
+1, having a meaningful hostname is needed to filter out hosts to be removed.
+1, this issue is bother us for a long time. Here is a similar bug reported about 5 months ago - BZ#1321964.
This is a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1321964 and will be fixed when https://trello.com/c/dyHpMQw9/335-8-as-a-user-i-want-to-the-installer-to-configure-for-the-openstack-cloudprovider-without-having-to-manually-edit-the-node-config is resolved. Not a 3.3 blocker.
Upstream PR: https://github.com/kubernetes/kubernetes/pull/30791
Someone is already working on a more complete solution: https://github.com/kubernetes/kubernetes/pull/31321 That gets us most of the way there. After that, we just need a follow-on commit to start using node.ExternalID instead of node.Name.
Congrats, this was just merged! Is any further code change needed? What OpenShift version do we expect to land the feature into?
There is still more code change needed. This part of the code is changing a lot from release to release of kuberenetes so I need to revisit it to see what more needs to be done. This upstream commit will be in kubernetes 1.6 so it'll either be origin 1.6 (OSE 3.6)
With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers. Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant. This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.