Re: [openstack-dev] [ironic] base node payload for notification

2016-09-29 Thread Tripp, Travis S
On 9/27/16, 8:23 AM, "Jim Rollenhagen" wrote: On Tue, Sep 27, 2016 at 9:57 AM, Loo, Ruby wrote: > Hi Yuriy, > > > > Thanks for bringing this up. I'm good with your list, with the exception of > driver_info and instance_info. I'm on the fence with these two. If we

Re: [openstack-dev] [ironic] base node payload for notification

2016-09-27 Thread Jim Rollenhagen
On Tue, Sep 27, 2016 at 9:57 AM, Loo, Ruby wrote: > Hi Yuriy, > > > > Thanks for bringing this up. I'm good with your list, with the exception of > driver_info and instance_info. I'm on the fence with these two. If we assume > that any secrets will be bleep'd out (configdrives won't be there), is

Re: [openstack-dev] [ironic] base node payload for notification

2016-09-27 Thread Loo, Ruby
Hi Yuriy, Thanks for bringing this up. I'm good with your list, with the exception of driver_info and instance_info. I'm on the fence with these two. If we assume that any secrets will be bleep'd out (configdrives won't be there), is there other information there that might be useful? I'm not t

Re: [openstack-dev] [ironic] base node payload for notification

2016-09-27 Thread Mario Villaplana
After some IRC discussion (http://eavesdrop.openstack.org/irclogs/%23openstack-ironic/%23openstack-ironic.2016-09-27.log.html#t2016-09-27T13:31:42), I'm +1 to this base payload, too. I vote we do this, and we can always update later if operators chime in with additional use cases that should be pu