Open Stack

> -----Original Message-----
> From: John Griffith [mailto:john.griffith at solidfire.com]
> Sent: 03 February 2014 03:47
> To: Joel Cooklin
> Cc: openstack at lists.openstack.org
> Subject: Re: [Openstack] nova unique name generator middleware
> 
> On Sun, Feb 2, 2014 at 7:26 PM, Joel Cooklin <joel.cooklin at gmail.com> wrote:
> > +1 intel use cases.  It would be nice to avoid our current custom patches.
> >
> >
> > On Sunday, February 2, 2014, Joshua Harlow <harlowja at yahoo-inc.com> wrote:
> >>
> >> +1 yahoo use case(s) would also benefit from not having to patch the
> >> +code
> >> to achieve similar results.
> >>
> >> Sent from my really tiny device...
> >>
> >> > On Feb 2, 2014, at 12:12 AM, "Tim Bell" <Tim.Bell at cern.ch> wrote:
> >> >
> >> > It would be interesting to have a formal exit inside OpenStack nova
> >> > at VM creation for this sort of check rather than having to patch the code.
> >> >
> >> > Other scenarios that I've seen is where there is a need to enforce
> >> > limits as the server name is used for other purposes. Examples are
> >> > characters in the server name or maximum length.
> >> >
> >> > Tim
> >> >
...
> >
> Maybe just an auto-naming option added to nova's existing boot call; use a prefix and the UUID of the instance would satisfy the
> cases people are talking about here and not impact existing users?
> 

We have a set of other use cases which are around the use of the server name to get a Kerberos/X.509 identity which imposes other restrictions on the name being chosen (such as maximum length and limited set of characters). The unique name is one scenario but there are others.

Thus, we could start adding new options such as "max server name length" and "server name character set" or we find a way to do a plugin.

Tim