I'm working on an incident system that my company, as an OpenStack operator, will use to support our deployment of OpenStack. Our first features all involve outside tools creating incidents, but It seems like it would be beneficial to define a standard incident API so that core openstack components could send incidents directly. Or at least so that 3rd party tools that work with OpenStack could have an incident API.
I'm assuming an incident system falls outside the OpenStack mission, and I'd expect most operators would want to have their people work incidents via their existing system. So, it seems like defining an implementation independent, OpenStack compatible RESTful API for incidents would be a good thing. I'd expect the API to have adapters for various common incident systems. Note that such an API and adapter set would probably be widely reuseable beyond just Openstack. Does this seem like something that would benefit the community? Is there a way to define just an API as being part of OpenStack, as a way to declare it fit for depending on by OpenStack? This email may include confidential information. If you received it in error, please delete it.
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
