On 10/13/2015 12:57 PM, Emilien Macchi wrote:
On 10/08/2015 07:38 AM, Vladimir Kuklin wrote:
[...]
* Proposed solution
Introduce a library of exception handling methods which should be the
same for all puppet openstack providers as these exceptions seem to be
generic. Then, for each of the providers we can introduce
provider-specific libraries that will inherit from this one.
Our mos-puppet team could add this into their backlog and could work on
that in upstream or downstream and propose it upstream.
What do you think on that, puppet folks?
This is excellent feedback from how modules work in Fuel and I'm sure
you're not alone, everybody deploying OpenStack with Puppet is hitting
these issues.
You might want to refactor [1] and manage more use-cases.
If you plan to work on it, I would suggest to use our upstream backlog
[2] so we can involve the whole group in that work.
[1]
https://github.com/openstack/puppet-openstacklib/blob/master/lib/puppet/provider/openstack.rb
[2] https://trello.com/b/4X3zxWRZ/on-going-effort
If the issue is that openstackclient output is hard to parse, we should
tell openstackclient to output JSON -
https://bugs.launchpad.net/puppet-openstacklib/+bug/1479387
Thanks for taking care of that,
__________________________________________________________________________
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
