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: [email protected] To: [email protected] 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 <[email protected]> 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 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 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) 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 Thanks for your help! Bryan __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
