Hello everyone. I started working on this blueprint "Implement neutron quota commands" [1] and now there is a patch, that adds quota delete command to python-openstackclient [2] (I will also very appreciate if you will look on it when will have a free time, thanks :)
But some times ago I had discussion in irc about this blueprint and as I understand, the way when we add some new command (for example, quota delete) only for neutron (networking part of quota management in os-client) is not the best way. For example with quota delete, its better to add support of this command for all parts, that quotas management currently implemented in os-client (networking, volume, compute). I think it’s good idea, and the patch mentioned above adds quota delete command for all these parts (networking, volume, compute), but… blueprint exist only for neutron quota commands. So, my main questions is how to deal with tracking of this work? I mean, should I (or someone else) create a bug or spec or rfe or another blueprint with the same proposals (something like "add quota delete command for nova/cinder") and mention it in my patch and in the next patches? [1] https://blueprints.launchpad.net/python-openstackclient/+spec/neutron-client-quota [2] https://review.openstack.org/#/c/376311/ -- Best Regards, Sergey Belous
__________________________________________________________________________ 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