I'm skeptical, because usually ticket creation has to be a two way
interaction because the entity asking for the ticket has to know that it
succeeded end to end and should receive a URI back so that they can
record it.
There should be a well defined API that forms the boundary between
OpenStack specific code and backend integration code. You could use a
push API, but you'd have to listen to it with a client that was aware of
OpenStack semantics. There's no reason an incident service would want to
maintain that and you wouldn't want them too, either.
On 09/07/2011 07:02 AM, George Reese wrote:
This should fall under the more general push notifications API.
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
