This project looks very interesting and i might give it a go by installing standalone. I have a question though: are there any plans to expose the current output as part of Horizon or any other UI ?
Thx, Dani On Wed, Mar 25, 2015 at 5:15 AM, Zhou, Zhenzan <zhenzan.z...@intel.com> wrote: > Just found it has been supported, e.g. > > > > openstack congress driver schema show ceilometer > > > > So here is the way to check data source drivers: > > > > For supported data source drivers: > > 1. openstack congress driver list > > 2. openstack congress driver schema show <ds-name> > > > > For enabled data source drivers: > > 1. openstack congress datasource list > > 2. openstack congress datasource schema show <ds-name> > > > > BR > > Zhou Zhenzan > > > > *From:* Zhou, Zhenzan [mailto:zhenzan.z...@intel.com] > *Sent:* Wednesday, March 25, 2015 12:24 PM > > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [Congress] Info on Currently Supported > Data Drivers > > > > Hi, > > > > The ‘driver list’ sub command could provide supported data source drivers, > but we cannot show its schema if it’s NOT LOADED. So we still have to check > the code for the schema. My point is that we could support show schemas for > any supported data source drivers, even it’s not loaded. > > > > zhenzan@zhenzan-openstack:~$ openstack congress driver list > > > +----------------+--------------------------------------------------------------------------+ > > | id | > description | > > > +----------------+--------------------------------------------------------------------------+ > > | ceilometer | Datasource driver that interfaces with > ceilometer. | > > | plexxi | Datasource driver that interfaces with > PlexxiCore. | > > | swift | Datasource driver that interfaces with > swift. | > > | neutronv2 | Datasource driver that interfaces with OpenStack > Networking aka Neutron. | > > | nova | Datasource driver that interfaces with OpenStack > Compute aka nova. | > > | murano | Datasource driver that interfaces with > murano | > > | keystone | Datasource driver that interfaces with > keystone. | > > | cloudfoundryv2 | Datasource driver that interfaces with > cloudfoundry | > > | ironic | Datasource driver that interfaces with OpenStack bare > metal aka ironic. | > > | cinder | Datasource driver that interfaces with OpenStack > cinder. | > > | vcenter | Datasource driver that interfaces with > vcenter | > > | glancev2 | Datasource driver that interfaces with OpenStack Images > aka Glance. | > > > +----------------+--------------------------------------------------------------------------+ > > zhenzan@zhenzan-openstack:~$ openstack congress datasource schema show > ceilometer > > ERROR: openstack Resource ceilometer not found (HTTP 404) > > > > > > BR > > Zhou Zhenzan > > *From:* Pierre-Emmanuel Ettori [mailto:pe.ett...@gmail.com > <pe.ett...@gmail.com>] > *Sent:* Wednesday, March 25, 2015 11:54 AM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [Congress] Info on Currently Supported > Data Drivers > > > > Hi Zhenzan, > Actually I believe the command that Tim is looking for is: > > openstack congress datasource list > > Please let us know if you are running into any issue. > > Thanks > Pierre > > > > On Tue, Mar 24, 2015 at 8:39 PM Tim Hinrichs <thinri...@vmware.com> wrote: > > Hi Zhenzan, > > > > I don't have the CLI in front of me, but check out the 'driver' commands. > The command you're looking for is something like the following. > > > > $ openstack congress driver list > > > > Tim > > > ------------------------------ > > *From:* Zhou, Zhenzan <zhenzan.z...@intel.com> > *Sent:* Tuesday, March 24, 2015 7:39 PM > > > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [Congress] Info on Currently Supported > Data Drivers > > Hi, > > > > To check LOADED(or ENABLED) data source drivers for a running system, you > can use congress cli. Maybe we could add a command to list SUPPORTED data > source drivers? > > > > zhenzan@zhenzan-openstack:~$ openstack congress datasource list > > > +--------------------------------------+-----------+---------+------+-----------------------------------------------------------------------------------------------------------------------------+ > > | id | name | enabled | type | > config > | > > > +--------------------------------------+-----------+---------+------+-----------------------------------------------------------------------------------------------------------------------------+ > > | 20a33403-e8d0-440a-b36f-0383bfcfd06f | cinder | True | None | > {u'username': u'admin', u'tenant_name': u'admin', u'password': u'<hidden>', > u'auth_url': u'http://10.239.47.118:5000/v2.0'} | > > | 7326d165-9e03-4b9c-acf8-b94a7f0a013f | ironic | True | None | > {u'username': u'admin', u'tenant_name': u'admin', u'password': u'<hidden>', > u'auth_url': u'http://10.239.47.118:5000/v2.0'} | > > | 80587cf8-ffbc-4c9a-b452-f884427b8cac | keystone | True | None | > {u'username': u'admin', u'tenant_name': u'admin', u'password': u'<hidden>', > u'auth_url': u'http://10.239.47.118:5000/v2.0'} | > > | 9a85d0f9-c869-41fe-b6d0-b784c1e84169 | nova | True | None | > {u'username': u'admin', u'tenant_name': u'admin', u'password': u'<hidden>', > u'auth_url': u'http://10.239.47.118:5000/v2.0'} | > > | df715798-7aa9-4fdc-8bfd-f37718bd4691 | neutronv2 | True | None | > {u'username': u'admin', u'tenant_name': u'admin', u'password': u'<hidden>', > u'auth_url': u'http://10.239.47.118:5000/v2.0'} | > > | e819b6c4-3744-4c45-9623-ad26ead15485 | glancev2 | True | None | > {u'username': u'admin', u'tenant_name': u'admin', u'password': u'<hidden>', > u'auth_url': u'http://10.239.47.118:5000/v2.0'} | > > > +--------------------------------------+-----------+---------+------+-----------------------------------------------------------------------------------------------------------------------------+ > > > > zhenzan@zhenzan-openstack:~$ openstack congress datasource schema show > cinder > > +-----------+----------------------------------------------------+ > > | table | columns | > > +-----------+----------------------------------------------------+ > > | services | {'name': 'status', 'description': 'None'}, | > > | | {'name': 'binary', 'description': 'None'}, | > > | | {'name': 'zone', 'description': 'None'}, | > > | | {'name': 'state', 'description': 'None'}, | > > | | {'name': 'updated_at', 'description': 'None'}, | > > | | {'name': 'host', 'description': 'None'}, | > > | | {'name': 'disabled_reason', 'description': 'None'} | > > | | | > > | snapshots | {'name': 'status', 'description': 'None'}, | > > | | {'name': 'created_at', 'description': 'None'}, | > > | | {'name': 'volume_id', 'description': 'None'}, | > > | | {'name': 'size', 'description': 'None'}, | > > | | {'name': 'id', 'description': 'None'}, | > > | | {'name': 'name', 'description': 'None'} | > > | | | > > | volumes | {'name': 'id', 'description': 'None'}, | > > | | {'name': 'size', 'description': 'None'}, | > > | | {'name': 'user_id', 'description': 'None'}, | > > | | {'name': 'status', 'description': 'None'}, | > > | | {'name': 'description', 'description': 'None'}, | > > | | {'name': 'name', 'description': 'None'}, | > > | | {'name': 'bootable', 'description': 'None'}, | > > | | {'name': 'created_at', 'description': 'None'}, | > > | | {'name': 'volume_type', 'description': 'None'} | > > | | | > > +-----------+----------------------------------------------------+ > > > > > > BR > > Zhou Zhenzan > > > > *From:* Tim Hinrichs [mailto:thinri...@vmware.com] > *Sent:* Wednesday, March 25, 2015 6:07 AM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [Congress] Info on Currently Supported > Data Drivers > > > > 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> 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 > To: 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> 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?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 > > __________________________________________________________________________ > 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 > > > > __________________________________________________________________________ > 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 > > > __________________________________________________________________________ > 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 > >
__________________________________________________________________________ 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
