Open Stack

Thanks JC. On the Provider API, I found a  better link for Nova APIs that describes all the extensions including the Admin-related ones here: http://api.openstack.org/

One question I had, may be somebody else on the list can clarify: If the Admin API (or Service Provider API) is defined as an extension to the tenant API, does this mean it is optional and there is no requirements for compliant implementations to provide them (since extensions are by definition not core APIs) ?

Youcef

-----Original Message-----
From: JC Martin [mailto:jcmartin at ebaysf.com] 
Sent: Tuesday, September 18, 2012 10:13 AM
To: openstack-dev at lists.openstack.org
Subject: [openstack-dev] [Quantum][LBaaS] 9/18 Meeting summary

During this week's meeting we summarized the discussion topics we wanted to propose during the summit :

Tenant API
	- review of comparison of various implementations
        - Review a proposal for common resource model for tenant api

Provider API
	- discuss the Implementation as either a single endpoint with extensions or a different endpoint.
	  For reference, nova is using both : nova-api expose different endpoints (os-api, metadata, ...)
	  and extensions for admin actions (e.g. http://goo.gl/udpkK)
	- discuss proposed resource model for provider API

Plugin Model
	- Service capabilities versus plugin capabilities versus middleware capabilities
	- Multiple simultaneous plugins (to support multiple LB models)

Capacity Management
	- middleware based
	- plugin based
	- core service

Quantum Integration/dependency
	- should the service be deployable standalone (without Quantum) ?

Additional dependencies/integration
	- keystone
	- horizon


AI : JC to propose a provider Resource Model and REST API, hopefully by next meeting.


Feel free to add if I missed/misrepresented any topic

JC


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev