openstack team mailing list archive

[Daryl Walleck <daryl.walleck@xxxxxxxxxxxxx>]

Hi Gabe,

I think what Nachi is saying is that these parameters can be taken in a create request, but are not documented (I say this also because I've seen this in novaclient as well). I know they're not required, but I'm curious what their purpose is.

Daryl
 
On Dec 2, 2011, at 12:16 PM, Gabe Westmaas wrote:

> Hi Nachi,
> 
> The reason for excluding those from being required in the create response
> is to allow us to make those creates as asynchronous as possible.
> 
> Gabe
> 
> On 12/2/11 12:01 PM, "Nachi Ueno" <ueno.nachi@xxxxxxxxxxxxxxxxxxxx> wrote:
> 
>> Hi Brian
>> 
>> Thank you for your response.
>> How about params which is missing in docs?
>> 
>> accessIPv4
>> accessIPv6
>> adminPass
>> config_drive
>> security_groups
>> networks
>> blob
>> keyname
>> availability_zone
>> reservation_id
>> min_count
>> max_count
>> 2011/12/1 Brian Waldon <brian.waldon@xxxxxxxxxxxxx>:
>>> Our consoles resource is not a part of the 1.1 (2.0) API. You are right
>>> in thinking it should be in the contrib directory. Additionally, it
>>> needs to be modified to act as an extension.
>>> 
>>> Our current level of documentation of extensions is extremely lacking,
>>> so hopefully before Essex we can do a much better job.
>>> 
>>> Brian Waldon
>>> 
>>> 
>>> On Dec 1, 2011, at 1:37 PM, Nachi Ueno wrote:
>>> 
>>>> Hi Nova-cores
>>>> 
>>>> Is the Console function in OS API 1.1 specs?
>>>> (See https://bugs.launchpad.net/nova/+bug/898266)
>>>> 
>>>> The implementation is not in contrib directory, so it didn't looks an
>>>> extension.
>>>> But as 898266 mentioned, it is not described in API docs.
>>>> 
>>>> And also, I checked API spces from code. (I know this is reverse way.
>>>> :))
>>>> 
>>>> There are another example,
>>>> Create server could get,
>>>> 
>>>> name (*)
>>>> imageRef (*)
>>>> flavorRef (*)
>>>> accessIPv4
>>>> accessIPv6
>>>> adminPass
>>>> config_drive
>>>> security_groups
>>>> networks
>>>> blob
>>>> keyname
>>>> availability_zone
>>>> reservation_id
>>>> min_count
>>>> max_count
>>>> metadata (*)
>>>> personality (*)
>>>> 
>>>> And only * one is documented on API.
>>>> 
>>>> http://docs.openstack.org/api/openstack-compute/1.1/content/CreateServer
>>>> s.html
>>>> 
>>>> Doc-Team can not decide specs, so I suppose Nova-core are responsible
>>>> to define these specs.
>>>> 
>>>> Cheers
>>>> Nachi
>>>> 
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp
>>> 
>> 
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp