Hi folks >Anne Sorry,I remember now. I got extension docs from you.
2011/12/2 Brian Waldon <brian.wal...@rackspace.com>: > accessIPv4 and accessIPv6 are both core instance attributes. The rest are all > attributes owned by existing extensions. Keep in mind that the spec doesn't > require all attributes to be returned in a POST response. I got it. So accessIPv4 and accessIPv6 is in core. The rest are extension. > Chris - I don't think config_drive is documented as an extension. This bug is > still not fixed: https://bugs.launchpad.net/nova/+bug/833331 > > Waldon > > On Dec 2, 2011, at 1:13 PM, Christopher MacGown wrote: > >> Hi Nachi, >> >> At least for config_drive, it has been documented as an extension. >> >> - chris >> >> On Dec 2, 2011, at 10:07, Nachi Ueno <ueno.na...@nttdata-agilenet.com> 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.wal...@rackspace.com>: >>>> 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@lists.launchpad.net >>>>> Unsubscribe : https://launchpad.net/~openstack >>>>> More help : https://help.launchpad.net/ListHelp >>>> >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~openstack >>> Post to : openstack@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~openstack >>> More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
