<html>
<head>
</head>
<body class='hmmessage'><div dir='ltr'>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">Thanks for clarifying, Tim (and Alex for the other response).<br><br>Since I have to understand the code anyway going to the drivers for current info is reasonable.<br><br>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.<br><br><div><hr id="stopSpelling">From: thinrichs@vmware.com<br>To: openstack-dev@lists.openstack.org<br>Date: Tue, 24 Mar 2015 19:57:26 +0000<br>Subject: Re: [openstack-dev] [Congress] Info on Currently Supported Data Drivers<br><br>
Hi Bryan,
<div><br>
</div>
<div>Inline.</div>
<div><br>
<div>
<blockquote>
<div>On Mar 24, 2015, at 12:13 PM, Bryan Sullivan <<a href="mailto:blsaws@hotmail.com">blsaws@hotmail.com</a>> wrote:</div>
<br class="ecxApple-interchange-newline">
<div><style>
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}
</style>
<div class="ecxhmmessage">
<div dir="ltr"><span class="ecxmessage">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
</span><span class="ecxmessage"><span class="ecxmessage"><span class="ecxcontent"><a href="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=" class="link" rel="noreferrer" target="_blank">http://congress.readthedocs.org/en/latest/cloudservices.html#drivers</a>
</span></span>seems to cover only Nova and Neutron. </span><span class="ecxmessage">I'm sure that I can pull this info from the source at
<a href="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=" class="link" rel="noreferrer" target="_blank">
https://github.com/stackforge/congress/tree/master/congress/datasources</a> but I was looking for any documentation on the current state of that code's design. The existing blueprints (e.g. at
<a href="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=" target="_blank">
https://github.com/stackforge/congress-specs)</a> do not go into this detail AFAICT.</span><br>
<br>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<blockquote>
<div>
<div class="ecxhmmessage">
<div dir="ltr">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.<br>
<br>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Tim </div>
<br>
<blockquote>
<div>
<div class="ecxhmmessage">
<div dir="ltr">[1] <a href="https://wiki.opnfv.org/copper/use_cases" target="_blank">
https://wiki.opnfv.org/copper/use_cases</a><br>
<br>
Thanks for your help!<br>
Bryan<br>
<br>
<br>
<br>
<span class="ecxEC_Apple-style-span" style="border-collapse:separate;"><span style="font-size:10.0pt;font-family:'Tahoma','sans-serif';color:gray;">
<div><span class="ecxEC_Apple-style-span" style="border-collapse:separate;"><span style="font-size:10.0pt;font-family:'Tahoma','sans-serif';color:gray;"><br>
</span></span></div>
</span><br>
</span></div>
</div>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">
OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div>
</blockquote>
</div>
<br>
</div>
<br>__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</div></div>
</div></body>
</html>