Hi Bryan,

I wish we could claim Congress has most of the data from OpenStack APIs already 
available for policy, but that’s not the case today.

If it were me, I’d start with your use cases, figure out which services and API 
calls you’ll need to support those use cases, and then check if those APIs are 
already available in Congress.

Tim

On Mar 24, 2015, at 1:47 PM, Bryan Sullivan 
<bls...@hotmail.com<mailto:bls...@hotmail.com>> wrote:

Thanks for clarifying, Tim (and Alex for the other response).

Since I have to understand the code anyway going to the drivers for current 
info is reasonable.

Can I derive from your statement "One of Congress’s goals is to make any data 
available via an API call to policy-related" that Congress already exposes (in 
Congress tables) most/all data available through OpenStack component APIs? That 
would save me digging through the OpenStack code as well.

________________________________
From: thinri...@vmware.com<mailto:thinri...@vmware.com>
To: openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>
Date: Tue, 24 Mar 2015 19:57:26 +0000
Subject: Re: [openstack-dev] [Congress] Info on Currently Supported Data Drivers

Hi Bryan,

Inline.

On Mar 24, 2015, at 12:13 PM, Bryan Sullivan 
<bls...@hotmail.com<mailto:bls...@hotmail.com>> wrote:

Hi, I have a question about where to find the complete set of currently 
supported data drivers (with table/row details) for Congress. The info at 
http://congress.readthedocs.org/en/latest/cloudservices.html#drivers<https://urldefense.proofpoint.com/v2/url?u=http-3A__congress.readthedocs.org_en_latest_cloudservices.html-23drivers&d=AwMFAw&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=B6BWd4kFfgOzAREgThxkmTZKy7dDXE2-eBAmL0PBK7s&m=7K6Tq1uqgCY-gmJMedkayeCZgjUEWp7QD_HaJg6pHmY&s=rEUZxD7aLCxwILxm2ugsR4Qr-4JXCdZ_-9BWcvG5F_k&e=>
 seems to cover only Nova and Neutron.  I'm sure that I can pull this info from 
the source at 
https://github.com/stackforge/congress/tree/master/congress/datasources<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_stackforge_congress_tree_master_congress_datasources&d=AwMFAw&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=B6BWd4kFfgOzAREgThxkmTZKy7dDXE2-eBAmL0PBK7s&m=7K6Tq1uqgCY-gmJMedkayeCZgjUEWp7QD_HaJg6pHmY&s=XeNw_NiKGg3HrR5R6oVbN9EVV2RhB3CQ4waMWGvBAHM&e=>
 but I was looking for any documentation on the current state of that code's 
design. The existing blueprints (e.g. at 
https://github.com/stackforge/congress-specs)<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_stackforge_congress-2Dspecs-29&d=AwMFAw&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=B6BWd4kFfgOzAREgThxkmTZKy7dDXE2-eBAmL0PBK7s&m=7K6Tq1uqgCY-gmJMedkayeCZgjUEWp7QD_HaJg6pHmY&s=AjqWychcmYYsMd9oOGytLq3rXOqzhJGLbUTi2OuX2_0&e=>
 do not go into this detail AFAICT.


I’d definitely just do a directory listing on the source code.  Syncing the 
docs is something we do before a major release.  Things are just changing too 
quickly to do anything else.

Also, since I'm looking into how the current supported Congress tables will 
support use cases of the OPNFV Copper project [1], it will be also helpful to 
know where I would look for the set of potential policy-related data items 
inside OpenStack docs/code for the various components. If I find a gap against 
a use case, I would want to be able to specify related patches (e.g. where data 
source driver extensions should get the additional data) so I need to know 
where the data comes from (and what's available) inside OpenStack.


One of Congress’s goals is to make any data available via an API call to 
policy-related.  So anything the API calls of OpenStack returns are reasonable 
candidates for writing policy over.

Tim

[1] 
https://wiki.opnfv.org/copper/use_cases<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_copper_use-5Fcases&d=AwMF-g&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=B6BWd4kFfgOzAREgThxkmTZKy7dDXE2-eBAmL0PBK7s&m=lssF60z2CQNbUwpN7SMHds5C8d33H4qy6lYURJ57ifM&s=SWYETWsuJ04nF3g_lUDlGGi7SlwgIHjobgh9d5zGLA4&e=>

Thanks for your help!
Bryan





__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__________________________________________________________________________ 
OpenStack Development Mailing List (not for usage questions) Unsubscribe: 
openstack-dev-requ...@lists.openstack.org<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to