[openstack-dev] [all] how to send messages (and events) to our users

Hi all For quite some time we (Heat team) have wanted to be able to send messages to our users (by user I do not mean the Operator, but the User that is interacting with the client). What do I mean by "user messages", and how do they differ from our current log messages and notifications? - Our c

Re: [openstack-dev] [all] how to send messages (and events) to our users

On 04/06/2015 08:55 PM, Angus Salkeld wrote: Hi all For quite some time we (Heat team) have wanted to be able to send messages to our users (by user I do not mean the Operator, but the User that is interacting with the client). What do I mean by "user messages", and how do they differ from our

Re: [openstack-dev] [all] how to send messages (and events) to our users

On Tue, Apr 7, 2015 at 1:53 PM, Chris Friesen wrote: > On 04/06/2015 08:55 PM, Angus Salkeld wrote: > >> Hi all >> >> For quite some time we (Heat team) have wanted to be able to send >> messages to our >> users (by user I do not mean the Operator, but the User that is >> interacting with >> the

Re: [openstack-dev] [all] how to send messages (and events) to our users

On 04/06/2015 10:08 PM, Angus Salkeld wrote: On Tue, Apr 7, 2015 at 1:53 PM, Chris Friesen mailto:chris.frie...@windriver.com>> wrote: On 04/06/2015 08:55 PM, Angus Salkeld wrote: Hi all For quite some time we (Heat team) have wanted to be able to send messages to o

Re: [openstack-dev] [all] how to send messages (and events) to our users

possible to take in non-json log messages and build an indexer around that if needed. cheers, gord Date: Tue, 7 Apr 2015 12:55:37 +1000 From: asalk...@mirantis.com To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [all] how to send messages (and events) to our users Hi all For qui

Re: [openstack-dev] [all] how to send messages (and events) to our users

On 04/07/2015 10:10 AM, gordon chung wrote: > >> - Specific user oriented log messages (distinct from our normal > operator logs) >> - Deprecation messages (if they are using old resource > properties/template features) >> - Progress and resource state changes (an application doesn't want to > pol

Re: [openstack-dev] [all] how to send messages (and events) to our users

. ? From: Angus Salkeld Sent: Monday, April 6, 2015 11:55 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [all] how to send messages (and events) to our users Hi all For quite some time we (Heat team) have wanted to be

Re: [openstack-dev] [all] how to send messages (and events) to our users

> This could be extended to richer JSON events that include the stack, > resources affected in the update, stats like "num-deleted-resources" or > "num-replaced-resources", autoscaling actions, and info about stack errors. > > Is there a way for users as-is to view those raw notifications, not just

Re: [openstack-dev] [all] how to send messages (and events) to our users

>Tooling in general seems to be moving towards richer event data as well. >The logging tools (Loggly/Logstash/PaperTrail/zillions of others) are >intended to take your unstructured logs and turn them into events, so >why not have Heat output structured events that we can present to the >user with

Re: [openstack-dev] [all] how to send messages (and events) to our users

On 04/07/2015 11:34 AM, Sandy Walsh wrote: log({'message':"The %(foo)s did %(thing)s", 'foo':'x', 'thing':'action'}) I pity the foo that did that thing. -jay __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [all] how to send messages (and events) to our users

On 04/07/2015 02:34 PM, Sandy Walsh wrote: > >> Tooling in general seems to be moving towards richer event data as well. >> The logging tools (Loggly/Logstash/PaperTrail/zillions of others) are >> intended to take your unstructured logs and turn them into events, so >> why not have Heat output str

Re: [openstack-dev] [all] how to send messages (and events) to our users

> Yeah, I'd really like to have a schema for Heat events so we can have a > single event stream and repackage events for different consumption goals > (metrics, notifications, programmatic interaction, etc). Keystone and parts of Ceilometer use the CADF schema to build notification messages[1].

Re: [openstack-dev] [all] how to send messages (and events) to our users

On 07/04/15 12:55 +1000, Angus Salkeld wrote: Hi all For quite some time we (Heat team) have wanted to be able to send messages to our users (by user I do not mean the Operator, but the User that is interacting with the client). What do I mean by "user messages", and how do they differ from our

Re: [openstack-dev] [all] how to send messages (and events) to our users

>From: Ryan Brown >Sent: Wednesday, April 8, 2015 9:42 AM > >> The trend in the monitoring space seems to be: >> >> 1. Alarms are issued from Metrics as Events. >> (events can issue alarms too, but conventional alarming is metric based) >> 2. Multiple events are analyzed to produce Metrics (st

Re: [openstack-dev] [all] how to send messages (and events) to our users

Excerpts from Angus Salkeld's message of 2015-04-06 19:55:37 -0700: > Hi all > > For quite some time we (Heat team) have wanted to be able to send messages > to our > users (by user I do not mean the Operator, but the User that is interacting > with the client). > > What do I mean by "user messag

Re: [openstack-dev] [all] how to send messages (and events) to our users

>From: Clint Byrum >Sent: Wednesday, April 8, 2015 1:15 PM > >There's this: > >https://wiki.openstack.org/wiki/Cue Hmm, that looks interesting. Will read. >I also want to point out that what I'd actually rather see is that all >of the services provide fun

Re: [openstack-dev] [all] how to send messages (and events) to our users

>From a security point, it certainly scares the hell out of me On 7 April 2015 at 08:45, Chris Friesen wrote: > On 04/06/2015 10:08 PM, Angus Salkeld wrote: > >> On Tue, Apr 7, 2015 at 1:53 PM, Chris Friesen < >> chris.frie...@windriver.com >> > wrote: >> >>

Re: [openstack-dev] [all] how to send messages (and events) to our users

On Wed, 8 Apr 2015, Sandy Walsh wrote: Yes. It would be so good to pull apart the state-machine that is Nova and just emit completed actions via notifications. Then, have something like TaskFlow externalize the orchestration. Do away with RPC-over-AMQP. YES! I've got notes going back to my fir

Re: [openstack-dev] [all] how to send messages (and events) to our users

uncan Thomas Sent: Wednesday, April 8, 2015 2:03 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [all] how to send messages (and events) to our users >From a security point, it certainly scares the hell out of me On 7 April 2015 at 08:45, Chris

Re: [openstack-dev] [all] how to send messages (and events) to our users

On 08/04/15 16:38 +, Sandy Walsh wrote: From: Clint Byrum Sent: Wednesday, April 8, 2015 1:15 PM There's this: https://wiki.openstack.org/wiki/Cue Hmm, that looks interesting. Will read. I also want to point out that what I'd actually rather se

Re: [openstack-dev] [all] how to send messages (and events) to our users

On 8 April 2015 at 20:34, Chris Dent wrote: > On Wed, 8 Apr 2015, Sandy Walsh wrote: > > Yes. It would be so good to pull apart the state-machine that is Nova and >> just emit completed actions via notifications. Then, have something like >> TaskFlow externalize the orchestration. Do away with R

Re: [openstack-dev] [all] how to send messages (and events) to our users

ons)" mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [all] how to send messages (and events) to our users On Fri, Apr 10, 2015 at 2:24 AM, Sandy Walsh mailto:sandy.wa...@rackspace.com>> wrote: >From: Angus Salkeld mailto:asalk...@mirantis.co

Re: [openstack-dev] [all] how to send messages (and events) to our users

On 08/04/15 20:23 -0700, Joshua Harlow wrote: Hope this helps: 'Let's do away with' == 'remove it/no longer use it' vs 'let's use RPC-over-AMQP' which means continue using it/use it more. a-ha... That explains it. My, obviously, non-native english translation failed to parse that. Thanks for

Re: [openstack-dev] [all] how to send messages (and events) to our users

On 08/04/15 15:35 -0700, Min Pae wrote: Uh sorry to nitpick, I think he said “let’s do away with” not “let’s use” RPC-over-AMQP How is that different? I honestly don't see the difference but I'm surre I'm missing something in my translation. On Wed, Apr 8, 2015 at 10:56 AM, Flavio Percoco w

Re: [openstack-dev] [all] how to send messages (and events) to our users

Sandy Walsh wrote: From: Clint Byrum Sent: Wednesday, April 8, 2015 1:15 PM There's this: https://wiki.openstack.org/wiki/Cue Hmm, that looks interesting. Will read. I also want to point out that what I'd actually rather see is that all of the servi

Re: [openstack-dev] [all] how to send messages (and events) to our users

Hope this helps: 'Let's do away with' == 'remove it/no longer use it' vs 'let's use RPC-over-AMQP' which means continue using it/use it more. Flavio Percoco wrote: On 08/04/15 15:35 -0700, Min Pae wrote: Uh sorry to nitpick, I think he said “let’s do away with” not “let’s use” RPC-over-AMQP

Re: [openstack-dev] [all] how to send messages (and events) to our users

Uh sorry to nitpick, I think he said “let’s do away with” not “let’s use” RPC-over-AMQP On Wed, Apr 8, 2015 at 10:56 AM, Flavio Percoco wrote: > On 08/04/15 16:38 +, Sandy Walsh wrote: > >> >> >>> From: Clint Byrum >>> Sent: Wednesday, April 8, 2015

Re: [openstack-dev] [all] how to send messages (and events) to our users

On Wed, Apr 8, 2015 at 4:45 PM, Min Pae wrote: > > >> "an under-the-clould service" ? - That is not what I am after here. >> >> I think the thread went off on a tangent and this point got lost. A user > facing notification system absolutely should be a web centric protocol, as > I imagine one of

Re: [openstack-dev] [all] how to send messages (and events) to our users

: "OpenStack Development Mailing List (not for usage questions)" Date: Wednesday, April 8, 2015 at 5:18 PM To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [all] how to send messages (and events) to our users > > > O

Re: [openstack-dev] [all] how to send messages (and events) to our users

ck Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Date: Wednesday, April 8, 2015 at 5:18 PM > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > > Subject: Re: [o

Re: [openstack-dev] [all] how to send messages (and events) to our users

On 06/04/15 22:55, Angus Salkeld wrote: Hi all For quite some time we (Heat team) have wanted to be able to send messages to our users (by user I do not mean the Operator, but the User that is interacting with the client). What do I mean by "user messages", and how do they differ from our curre

Re: [openstack-dev] [all] how to send messages (and events) to our users

> > "an under-the-clould service" ? - That is not what I am after here. > > I think the thread went off on a tangent and this point got lost. A user facing notification system absolutely should be a web centric protocol, as I imagine one of the big consumers of such a system will be monitoring das

Re: [openstack-dev] [all] how to send messages (and events) to our users

>From: Angus Salkeld >Sent: Wednesday, April 8, 2015 8:24 PM >To: OpenStack Development Mailing List (not for usage questions) >Subject: Re: [openstack-dev] [all] how to send messages (and events) to our >users > > >I also want to point out that what I'd actually r

Re: [openstack-dev] [all] how to send messages (and events) to our users

On Thu, Apr 9, 2015 at 2:15 AM, Clint Byrum wrote: > Excerpts from Angus Salkeld's message of 2015-04-06 19:55:37 -0700: > > Hi all > > > > For quite some time we (Heat team) have wanted to be able to send > messages > > to our > > users (by user I do not mean the Operator, but the User that is >

Re: [openstack-dev] [all] how to send messages (and events) to our users

+1 for using taskflow to implement workflows… workflow reliability is a non-trivial problem that is best solved in one place imho I have doubts as to whether AMQP is the right protocol for notifications. Web service interfaces, thus far, being the “standard” interface for interacting with Opensta