<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Do most systems have access to a dns system that can be used to check? Maybe that could be one of these plugins.</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Craig J <<a href="mailto:craig.jellick@gmail.com">craig.jellick@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Monday, February 3, 2014 at 1:58 PM<br>
<span style="font-weight:bold">To: </span>Joel Cooklin <<a href="mailto:joel.cooklin@gmail.com">joel.cooklin@gmail.com</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a>" <<a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Openstack] nova unique name generator middleware<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir="ltr">There's currently a check in nova for max length. It's hard coded to 255. Easy low-hanging fruit would be to make that number configurable and add a configurable regex check on the server name.
<div><br>
</div>
<div>The uniqueness check could be trickier: checking the nova db wouldn't be sufficient in many cases as most people need to check some external system(s). Maybe we could put together something pluggable with a nova-db check as an example. Is a wsgi filter
the most appropriate place for such a pluggable validator or should it be deeper, at the same place where the other server name validation occurs?</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, Feb 3, 2014 at 6:46 AM, Joel Cooklin <span dir="ltr">
<<a href="mailto:joel.cooklin@gmail.com" target="_blank">joel.cooklin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">>>Shouldn't "nova list" and some shell script magic do most of this?<br>
<br>
</div>
For our use case this won't work as well since several business units<br>
(tenants) make direct use of the APIs. It's hard to enforce that they<br>
use our wrappers and the like. It would be much more convenient in<br>
our case if we could enforce business logic via a plugin for all<br>
requests regardless of the client being used to access the API.<br>
<div class="HOEnZb">
<div class="h5"><br>
On Sun, Feb 2, 2014 at 11:48 PM, Aryeh Friedman<br>
<<a href="mailto:aryeh.friedman@gmail.com">aryeh.friedman@gmail.com</a>> wrote:<br>
> Shouldn't "nova list" and some shell script magic do most of this? The only<br>
> problem would be to make sure that two people didn't ask for a name at the<br>
> same time<br>
><br>
><br>
> On Mon, Feb 3, 2014 at 1:19 AM, Tim Bell <<a href="mailto:Tim.Bell@cern.ch">Tim.Bell@cern.ch</a>> wrote:<br>
>><br>
>> > -----Original Message-----<br>
>> > From: John Griffith [mailto:<a href="mailto:john.griffith@solidfire.com">john.griffith@solidfire.com</a>]<br>
>> > Sent: 03 February 2014 03:47<br>
>> > To: Joel Cooklin<br>
>> > Cc: <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
>> > Subject: Re: [Openstack] nova unique name generator middleware<br>
>> ><br>
>> > On Sun, Feb 2, 2014 at 7:26 PM, Joel Cooklin <<a href="mailto:joel.cooklin@gmail.com">joel.cooklin@gmail.com</a>><br>
>> > wrote:<br>
>> > > +1 intel use cases. It would be nice to avoid our current custom<br>
>> > > patches.<br>
>> > ><br>
>> > ><br>
>> > > On Sunday, February 2, 2014, Joshua Harlow <<a href="mailto:harlowja@yahoo-inc.com">harlowja@yahoo-inc.com</a>><br>
>> > > wrote:<br>
>> > >><br>
>> > >> +1 yahoo use case(s) would also benefit from not having to patch the<br>
>> > >> +code<br>
>> > >> to achieve similar results.<br>
>> > >><br>
>> > >> Sent from my really tiny device...<br>
>> > >><br>
>> > >> > On Feb 2, 2014, at 12:12 AM, "Tim Bell" <<a href="mailto:Tim.Bell@cern.ch">Tim.Bell@cern.ch</a>> wrote:<br>
>> > >> ><br>
>> > >> > It would be interesting to have a formal exit inside OpenStack nova<br>
>> > >> > at VM creation for this sort of check rather than having to patch<br>
>> > >> > the code.<br>
>> > >> ><br>
>> > >> > Other scenarios that I've seen is where there is a need to enforce<br>
>> > >> > limits as the server name is used for other purposes. Examples are<br>
>> > >> > characters in the server name or maximum length.<br>
>> > >> ><br>
>> > >> > Tim<br>
>> > >> ><br>
>> ...<br>
>> > ><br>
>> > Maybe just an auto-naming option added to nova's existing boot call; use<br>
>> > a prefix and the UUID of the instance would satisfy the<br>
>> > cases people are talking about here and not impact existing users?<br>
>> ><br>
>><br>
>> We have a set of other use cases which are around the use of the server<br>
>> name to get a Kerberos/X.509 identity which imposes other restrictions on<br>
>> the name being chosen (such as maximum length and limited set of<br>
>> characters). The unique name is one scenario but there are others.<br>
>><br>
>> Thus, we could start adding new options such as "max server name length"<br>
>> and "server name character set" or we find a way to do a plugin.<br>
>><br>
>> Tim<br>
>><br>
>> _______________________________________________<br>
>> Mailing list:<br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
>> Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
>> Unsubscribe :<br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
><br>
><br>
><br>
><br>
> --<br>
> Aryeh M. Friedman, Lead Developer, <a href="http://www.PetiteCloud.org" target="_blank">
http://www.PetiteCloud.org</a><br>
<br>
_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>