Re: [openstack-dev] [Congress] data-source renovation

2014-08-04 Thread Alex Yip
Hi all, I favor the first approach because it solves the usability problem of wide tables without limiting Congress' ability to use wide tables, or adding extra complexity. There are legitimate uses for wide tables, so Congress should be able to support them. For example, Congress will need

Re: [openstack-dev] [Congress] data-source renovation

2014-08-01 Thread Rajdeep Dua
Option 2 looks like a better idea keeping in mind the data model consistency with Neutron/Nova. Could we write something similar to a view which becomes a layer on top if this data model? On Wed, Jul 30, 2014 at 3:33 AM, Tim Hinrichs thinri...@vmware.com wrote: Hi all, As I mentioned in a

[openstack-dev] [Congress] data-source renovation

2014-07-29 Thread Tim Hinrichs
Hi all, As I mentioned in a previous IRC, when writing our first few policies I had trouble using the tables we currently use to represent external data sources like Nova/Neutron. The main problem is that wide tables (those with many columns) are hard to use. (a) it is hard to remember