openstack team mailing list archive

[Nachi Ueno <ueno.nachi@xxxxxxxxxxxxxxxxxxxx>]

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/CreateServers.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
>