Re: [openstack-dev] Treating notifications as a contract

2014-10-14 Thread Sandy Walsh
From: Doug Hellmann [d...@doughellmann.com] Tuesday, October 14, 2014 7:19 PM > It might be more appropriate to put it on the cross-project session list: > https://etherpad.openstack.org/p/kilo-crossproject-summit-topics Done ... thanks! ___ OpenStack

Re: [openstack-dev] Treating notifications as a contract

2014-10-14 Thread Doug Hellmann
On Oct 13, 2014, at 5:49 PM, Chris Dent wrote: > On Tue, 7 Oct 2014, Sandy Walsh wrote: > >> Haven't had any time to get anything written down (pressing deadlines >> with StackTach.v3) but open to suggestions. Perhaps we should just add >> something to the olso.messaging etherpad to find time a

Re: [openstack-dev] Treating notifications as a contract

2014-10-13 Thread Chris Dent
On Tue, 7 Oct 2014, Sandy Walsh wrote: Haven't had any time to get anything written down (pressing deadlines with StackTach.v3) but open to suggestions. Perhaps we should just add something to the olso.messaging etherpad to find time at the summit to talk about it? Have you got a link for that

Re: [openstack-dev] Treating notifications as a contract

2014-10-07 Thread Sandy Walsh
> >From: Sandy Walsh [sandy.wa...@rackspace.com] Tuesday, October 07, 2014 6:07 PM > >Haven't had any time to get anything written down (pressing deadlines with >StackTach.v3) but open to suggestions. Perhaps we should just add something to >the olso.messaging etherpad to find time at the summit

Re: [openstack-dev] Treating notifications as a contract

2014-10-07 Thread Sandy Walsh
>From: Chris Dent [chd...@redhat.com] Tuesday, October 07, 2014 12:07 PM > >On Wed, 3 Sep 2014, Sandy Walsh wrote: > >> Good goals. When Producer and Consumer know what to expect, things are >> good ... "I know to find the Instance ID ". When the consumer >> wants to deal with a notification as a

Re: [openstack-dev] Treating notifications as a contract

2014-10-07 Thread Chris Dent
On Wed, 3 Sep 2014, Sandy Walsh wrote: Good goals. When Producer and Consumer know what to expect, things are good ... "I know to find the Instance ID ". When the consumer wants to deal with a notification as a generic object, things get tricky ("find the instance ID in the payload", "What is th

Re: [openstack-dev] Treating notifications as a contract

2014-09-10 Thread Chris Dent
On Wed, 10 Sep 2014, Jay Pipes wrote: There would be an Oslo library that would store the codification of the resource classes and actions, along with the mapping of (resource_class, action, version) to the JSONSchema document describing the payload field. This seems reasonable with two cave

Re: [openstack-dev] Treating notifications as a contract

2014-09-10 Thread Sandy Walsh
> Jay Pipes - Wednesday, September 10, 2014 3:56 PM >On 09/03/2014 11:21 AM, Sandy Walsh wrote: >> On 9/3/2014 11:32 AM, Chris Dent wrote: >>> I took some notes on this a few weeks ago and extracted what seemed >>> to be the two main threads or ideas the were revealed by the >>> conversation that h

Re: [openstack-dev] Treating notifications as a contract

2014-09-10 Thread Jay Pipes
On 09/03/2014 11:21 AM, Sandy Walsh wrote: On 9/3/2014 11:32 AM, Chris Dent wrote: I took some notes on this a few weeks ago and extracted what seemed to be the two main threads or ideas the were revealed by the conversation that happened in this thread: * At the micro level have versione

Re: [openstack-dev] Treating notifications as a contract (CADF)

2014-09-04 Thread Neal, Phil
> On 9/04/2014 Sandy Walsh wrote: > Yesterday, we had a great conversation with Matt Rutkowski from IBM, > one > of the authors of the CADF spec. > > I was having a disconnect on what CADF offers and got it clarified. > > My assumption was CADF was a set of transformation/extraction rules > for >

Re: [openstack-dev] Treating notifications as a contract (CADF)

2014-09-04 Thread Sandy Walsh
Yesterday, we had a great conversation with Matt Rutkowski from IBM, one of the authors of the CADF spec. I was having a disconnect on what CADF offers and got it clarified. My assumption was CADF was a set of transformation/extraction rules for taking data from existing data structures and defin

Re: [openstack-dev] Treating notifications as a contract

2014-09-03 Thread Doug Hellmann
On Sep 3, 2014, at 9:50 AM, Sandy Walsh wrote: > Is there anything slated for the Paris summit around this? > > I just spent nearly a week parsing Nova notifications and the pain of no > schema has overtaken me. > > We're chatting with IBM about CADF and getting down to specifics on their >

Re: [openstack-dev] Treating notifications as a contract

2014-09-03 Thread gordon chung
> > For example: It appears that CADF was designed for this sort of thing and> > > > was considered at some point in the past. It would be useful to know> > > > more of that story if there are any pointers.> >> > My initial reaction is > > that CADF has the stank of enterprisey all over> > it ra

Re: [openstack-dev] Treating notifications as a contract

2014-09-03 Thread Sandy Walsh
On 9/3/2014 11:32 AM, Chris Dent wrote: > On Wed, 3 Sep 2014, Sandy Walsh wrote: > >> We're chatting with IBM about CADF and getting down to specifics on >> their applicability to notifications. Once I get StackTach.v3 into >> production I'm keen to get started on revisiting the notification >> for

Re: [openstack-dev] Treating notifications as a contract

2014-09-03 Thread Chris Dent
On Wed, 3 Sep 2014, Sandy Walsh wrote: Is there anything slated for the Paris summit around this? There are plans to make plans, but that's about all I know. I just spent nearly a week parsing Nova notifications and the pain of no schema has overtaken me. /me passes the ibuprofen We're c

Re: [openstack-dev] Treating notifications as a contract

2014-09-03 Thread Sandy Walsh
Is there anything slated for the Paris summit around this? I just spent nearly a week parsing Nova notifications and the pain of no schema has overtaken me. We're chatting with IBM about CADF and getting down to specifics on their applicability to notifications. Once I get StackTach.v3 into pr