incubator-deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mohammed Morsi <>
Subject Re: 'Name' usage in deltacloud drivers
Date Wed, 15 Dec 2010 18:18:47 GMT
  On 12/14/2010 02:01 PM, Ian Main wrote:
> On Tue, 2010-12-14 at 10:32 -0800, David Lutterkort wrote:
>> On Mon, 2010-12-06 at 20:10 -0800, Ian Main wrote:
>>> Either way we are going to require changes to the API.  Probably the
>>> easiest is to just support a notion of the maximum instance name
>>> length for a given provider.
>> How would the following work for you:
>>    <link rel="instances" href="...">
>>      <feature name="user-name">
>>        <constraint name="length" value="20"/>
>>        <constraint name="pattern" value="[crazy regexp in some yet-to-be-specified
>>      </feature>
>>    </link>
>> In other words, we tell the client (a) that the cloud supports
>> user-supplied names for instances (b) what the maximum length is and (c)
>> the regexp pattern that the name must match (or would it more be more
>> helpful to indicate that through words like 'hostname' or 'alphanum' ?)
> Yeah I'd be inclined to think 'hostname' or 'alphanum' would be better.
> The client here is written in C++ so to apply the regexp I'd have to
> drag in another library into condor and do the match to ensure
> conformity.  Even then I'm not sure how you'd use that information
> (match/no match) to modify the name to conform.  It would probably be
> better just to say "if alphanum then sanitize_alphanum()".

Would it be smart to automaticallly sanetize the names without 
consulting the user first? What if they go to start several instances 
all with the same name except for one character which is invalid and 
automatically removed?


View raw message