Thanks Tim, we actually have the max length constraint as well (imposed
because of Active Directory integration). We've gone back and forth about
adding validation or generating names. We've chosen name generation for the
time being because we felt that that would be better for the user than
reject
Hi Craig,
in reality is what we are doing...
to fail early we have some checks at API level. In the case of VM hostname
uniqueness we check first if it exists already on DNS (the network is shared
between between all the lab).
Then we have some hooks in the nova network driver to interact with o
My understanding of the gen name is that it will be unique across your
openstack
Remo
Inviato da iPhone ()
Il giorno Feb 1, 2014, alle ore 17:32, Aryeh Friedman
ha scritto:
>>
>> Aryeh, to your point, OpenStack effectively _is_, the provisioning system.
>> Our current use case is providi
>
>
> Aryeh, to your point, OpenStack effectively _is_, the provisioning system.
> Our current use case is providing engineers with a self service portal for
> spinning up VMs on which they can do development work. So, the workflow is
> user -> UI -> nova API. But when a VM is spun up, we still wan
Thanks Belmiro. I think long term we may end up doing something similar.
Though our network infrastructure is fairly complex, so it would be more
like a call to a network API (maybe just a DNS check?) rather than querying
a DB directly.
Aryeh, to your point, OpenStack effectively _is_, the provisi
-- Forwarded message --
From: Aryeh Friedman
Date: Sat, Feb 1, 2014 at 5:09 PM
Subject: Re: [Openstack] nova unique name generator middleware
To: Belmiro Moreira
Since I am relatively new to the guts of OpenStack this might be an off
base suggestion but why is this even OpenStac
