[openstack-dev] Consolidation for Manager and Resource classes
Has anyone looked into doing a effort in consolidating the different implementations of these classes ? Doing a short walk-through I see: Manager * Has a typical kind of API (server, lb, network, subnet) which it interacts with and returns instances of a result as a Resource Resource * Represents a instance of a object. # Nova https://github.com/openstack/python-novaclient/ https://github.com/openstack/python-novaclient/blob/master/novaclient/base.py # Neutron https://github.com/openstack/python-neutronclient N/A? # Glance https://github.com/openstack/python-glanceclient https://github.com/openstack/python-glanceclient/blob/master/glanceclient/common/base.py # Keystone https://github.com/openstack/python-keystoneclient/ https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/base.py # Cinder https://github.com/openstack/python-cinderclient/ https://github.com/openstack/python-cinderclient/blob/master/cinderclient/base.py # Ceilometer https://github.com/openstack/python-ceilometerclient/ https://github.com/openstack/python-ceilometerclient/blob/master/ceilometerclient/common/base.py # Heat https://github.com/openstack/python-heatclient https://github.com/openstack/python-heatclient/blob/master/heatclient/common/base.py # Ironic https://github.com/openstack/python-ironicclient https://github.com/openstack/python-ironicclient/blob/master/ironicclient/common/base.py # Tuskar https://github.com/openstack/python-tuskarclient https://github.com/openstack/python-tuskarclient/blob/master/tuskarclient/common/base.py # Trove https://github.com/openstack/python-troveclient https://github.com/openstack/python-troveclient/blob/master/troveclient/base.py # Marconi https://github.com/openstack/python-marconiclient N/A? # Savanna https://github.com/openstack/python-savannaclient https://github.com/openstack/python-savannaclient/blob/master/savannaclient/api/base.py # Manila https://github.com/stackforge/python-manilaclient https://github.com/stackforge/python-manilaclient/blob/master/manilaclient/base.py They are all doing the same thing, so why not put them into a common place? Endre ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Consolidation for Manager and Resource classes
+1 to consolidate. They are all doing the same thing, so why not put them into a common place? *almost* the same thing, there's some small differences, one e.g is that Ironic use PATH for the update instead of PUT. Cheers, Lucas ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Consolidation for Manager and Resource classes
I can see though that there is a apiclient thing in oslo-incubator, would it be an idea to name this oslo.client instead of having to copy this in like other oslo stuff? Endre 2013/10/16 Lucas Alvares Gomes lucasago...@gmail.com +1 to consolidate. They are all doing the same thing, so why not put them into a common place? *almost* the same thing, there's some small differences, one e.g is that Ironic use PATH for the update instead of PUT. Cheers, Lucas ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev