Hi guys, @Sergii, it looks like you misunderstood something. `node-uuid` is not a general use case. It's only about conflicting nodes, and I'm sure everyone's going to change such a hostname in order to avoid confusion.
@Andrew, a) Database refuses hostnames that break unique constraint, sot it'll work out-of-box. b) I like this idea. I think refusing `node-id` where `id` is not actually a node id is good idea. It solves our problem. Thanks, Igor On Wed, Jul 22, 2015 at 8:21 AM, Sergii Golovatiuk <sgolovat...@mirantis.com> wrote: > node-uuid is very terrible from UX perspective of view. Ask support people > if they are comfortable to ssh such nodes or telling the name in phone > conversation with customer. If we cannot validate FQDN of hostname I would > slip this feature to next release where we can pay more attention to > details. > > -- > Best regards, > Sergii Golovatiuk, > Skype #golserge > IRC #holser > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
