Monday, 2016-05-16

*** ddieterly[away] is now known as ddieterly00:01
*** alexpilotti has joined #openstack-meeting-300:11
*** alexpilotti has quit IRC00:12
*** amotoki has joined #openstack-meeting-300:17
*** kzaitsev_mb has quit IRC00:18
*** Sukhdev has joined #openstack-meeting-300:19
*** zz_dimtruck is now known as dimtruck00:20
*** scottda has quit IRC00:25
*** obondarev has quit IRC00:29
*** obondarev has joined #openstack-meeting-300:30
*** toddjohn_ has joined #openstack-meeting-300:45
*** hoangcx has joined #openstack-meeting-300:47
*** hoangcx has left #openstack-meeting-300:47
*** toddjohn_ has quit IRC00:50
*** amotoki has quit IRC00:59
*** zhurong has joined #openstack-meeting-301:03
*** kzaitsev_mb has joined #openstack-meeting-301:18
*** amotoki has joined #openstack-meeting-301:21
*** kzaitsev_mb has quit IRC01:24
*** bswartz has quit IRC01:28
*** zhenguo_ has joined #openstack-meeting-301:31
*** salv-orlando has joined #openstack-meeting-301:43
*** maishsk has quit IRC01:47
*** sdague has quit IRC01:47
*** amotoki has quit IRC01:47
*** salv-orlando has quit IRC01:51
*** ddieterly is now known as ddieterly[away]02:02
*** mbound has joined #openstack-meeting-302:09
*** amotoki has joined #openstack-meeting-302:10
*** mbound has quit IRC02:14
*** nelsnels_ has joined #openstack-meeting-302:19
*** nelsnelson has quit IRC02:19
*** kzaitsev_mb has joined #openstack-meeting-302:20
*** kzaitsev_mb has quit IRC02:25
*** bswartz has joined #openstack-meeting-302:33
*** ccamacho has quit IRC02:43
*** ccamacho has joined #openstack-meeting-302:45
*** toddjohn_ has joined #openstack-meeting-302:47
*** toddjohn_ has quit IRC02:52
*** yamamot__ has joined #openstack-meeting-302:54
*** bpokorny has joined #openstack-meeting-302:59
*** ddieterly[away] has quit IRC03:02
*** dimtruck is now known as zz_dimtruck03:04
*** zz_dimtruck is now known as dimtruck03:04
*** reedip__ has joined #openstack-meeting-303:08
*** coolsvap has joined #openstack-meeting-303:11
*** dimtruck is now known as zz_dimtruck03:13
*** coolsvap has quit IRC03:15
*** yamamot__ has quit IRC03:19
*** kzaitsev_mb has joined #openstack-meeting-303:21
*** kzaitsev_mb has quit IRC03:26
*** baoli has joined #openstack-meeting-303:26
*** bpokorny has quit IRC03:26
*** baoli has quit IRC03:30
*** coolsvap has joined #openstack-meeting-303:32
*** pgadiya has joined #openstack-meeting-304:11
*** amotoki has quit IRC04:15
*** amotoki has joined #openstack-meeting-304:16
*** kzaitsev_mb has joined #openstack-meeting-304:22
*** yamamot__ has joined #openstack-meeting-304:22
*** kzaitsev_mb has quit IRC04:27
*** Poornima has joined #openstack-meeting-304:30
*** irenab has quit IRC04:33
*** salv-orlando has joined #openstack-meeting-304:36
*** sverma has joined #openstack-meeting-304:43
*** salv-orlando has quit IRC04:45
*** toddjohn_ has joined #openstack-meeting-304:48
*** toddjohn_ has quit IRC04:53
*** mtanino has quit IRC04:58
*** lpetrut has joined #openstack-meeting-305:20
*** zhurong has quit IRC05:31
*** zhurong has joined #openstack-meeting-305:32
*** irenab has joined #openstack-meeting-305:34
*** amotoki_ has joined #openstack-meeting-305:53
*** amotoki has quit IRC05:54
*** reedip__ has quit IRC06:00
*** muawiakhan has joined #openstack-meeting-306:01
*** salv-orlando has joined #openstack-meeting-306:02
*** salv-orlando has quit IRC06:08
*** lpetrut has quit IRC06:20
*** kzaitsev_mb has joined #openstack-meeting-306:23
*** salv-orlando has joined #openstack-meeting-306:25
*** reedip__ has joined #openstack-meeting-306:26
*** anilvenkata has joined #openstack-meeting-306:28
*** kzaitsev_mb has quit IRC06:28
*** tfukushima has joined #openstack-meeting-306:41
*** toddjohn_ has joined #openstack-meeting-306:50
*** toddjohn_ has quit IRC06:54
*** amotoki_ is now known as amotoki06:58
*** Sukhdev has quit IRC07:00
*** dedery has joined #openstack-meeting-307:17
*** kzaitsev_mb has joined #openstack-meeting-307:24
*** jtomasek has joined #openstack-meeting-307:26
*** kzaitsev_mb has quit IRC07:29
*** jschwarz has joined #openstack-meeting-307:31
*** mickeys_ has joined #openstack-meeting-307:32
*** ihrachys has joined #openstack-meeting-307:32
*** lpetrut has joined #openstack-meeting-307:32
*** jlanoux has joined #openstack-meeting-307:34
*** stendulker has joined #openstack-meeting-307:36
*** aarefiev has quit IRC07:43
*** mickeys_ has quit IRC07:44
*** mickeys has joined #openstack-meeting-307:45
*** mickeys has quit IRC07:49
*** numans has joined #openstack-meeting-307:51
*** toddjohn_ has joined #openstack-meeting-307:51
*** pavel_bondar has joined #openstack-meeting-307:56
*** toddjohn_ has quit IRC07:56
*** lpetrut has quit IRC08:01
*** amotoki has quit IRC08:03
*** mbound has joined #openstack-meeting-308:09
*** amotoki has joined #openstack-meeting-308:11
*** salv-orlando has quit IRC08:11
*** zhurong has quit IRC08:12
*** zhurong has joined #openstack-meeting-308:12
*** mbound has quit IRC08:14
*** markvoelker has joined #openstack-meeting-308:15
*** zhurong has quit IRC08:16
*** zhurong has joined #openstack-meeting-308:17
*** markvoelker has quit IRC08:23
*** markvoelker has joined #openstack-meeting-308:24
*** kzaitsev_mb has joined #openstack-meeting-308:25
*** dosaboy has quit IRC08:26
*** amotoki has quit IRC08:27
*** kzaitsev_mb has quit IRC08:30
*** dosaboy has joined #openstack-meeting-308:36
*** kzaitsev_mb has joined #openstack-meeting-308:36
*** Poornima has quit IRC08:37
*** amotoki has joined #openstack-meeting-308:46
*** Poornima has joined #openstack-meeting-308:47
*** toddjohn_ has joined #openstack-meeting-308:52
*** mdbooth_ is now known as mdbooth08:56
*** toddjohn_ has quit IRC08:57
*** kzaitsev_mb has quit IRC08:59
*** neiljerram has joined #openstack-meeting-309:01
*** kzaitsev_mb has joined #openstack-meeting-309:03
*** sambetts|afk is now known as sambetts09:07
*** kzaitsev_mb has quit IRC09:09
*** amotoki has quit IRC09:10
*** neiljerram has quit IRC09:17
*** neiljerram has joined #openstack-meeting-309:22
*** ihrachys has quit IRC09:24
*** lpetrut has joined #openstack-meeting-309:27
*** ihrachys has joined #openstack-meeting-309:28
*** lpetrut1 has joined #openstack-meeting-309:33
*** lpetrut has quit IRC09:34
*** lpetrut1 is now known as lpetrut09:34
*** luis_ has joined #openstack-meeting-310:00
*** kzaitsev_mb has joined #openstack-meeting-310:08
*** zhurong has quit IRC10:09
*** amotoki has joined #openstack-meeting-310:14
*** sdague has joined #openstack-meeting-310:18
*** yamamot__ has quit IRC10:19
*** tfukushima has quit IRC10:22
*** tfukushima has joined #openstack-meeting-310:24
*** salv-orlando has joined #openstack-meeting-310:34
*** salv-orlando has quit IRC10:39
*** salv-orlando has joined #openstack-meeting-310:48
*** anilvenkata has quit IRC10:53
*** toddjohn_ has joined #openstack-meeting-310:53
*** toddjohn_ has quit IRC10:58
*** markvoelker has quit IRC11:06
*** stendulker has quit IRC11:08
*** krtaylor has quit IRC11:10
*** _fortis has quit IRC11:13
*** jtomasek_ has joined #openstack-meeting-311:14
*** yamamoto_ has joined #openstack-meeting-311:18
*** krtaylor has joined #openstack-meeting-311:24
*** numans has quit IRC11:25
*** rtheis has joined #openstack-meeting-311:25
*** salv-orlando has quit IRC11:27
*** dedery has quit IRC11:33
*** salv-orlando has joined #openstack-meeting-311:35
*** zhurong has joined #openstack-meeting-311:36
*** amotoki has quit IRC11:36
*** jtomasek_ has quit IRC11:38
*** anilvenkata has joined #openstack-meeting-311:41
*** kzaitsev_mb has quit IRC11:50
*** amotoki has joined #openstack-meeting-311:52
*** sdake has joined #openstack-meeting-311:55
*** mtanino has joined #openstack-meeting-311:57
*** jschwarz has quit IRC12:01
*** luis_ has quit IRC12:01
*** sergio_nubeliu has joined #openstack-meeting-312:05
*** zhurong has quit IRC12:07
*** amotoki has quit IRC12:08
*** markvoelker has joined #openstack-meeting-312:08
*** numans has joined #openstack-meeting-312:09
*** kzaitsev_mb has joined #openstack-meeting-312:10
*** jtomasek_ has joined #openstack-meeting-312:10
*** sdake has quit IRC12:10
*** amotoki has joined #openstack-meeting-312:10
*** markvoelker has quit IRC12:13
*** jschwarz has joined #openstack-meeting-312:16
*** amotoki has quit IRC12:17
*** coolsvap has quit IRC12:22
*** coolsvap has joined #openstack-meeting-312:22
*** toddjohn_ has joined #openstack-meeting-312:23
*** jschwarz_ has joined #openstack-meeting-312:26
*** yamamoto_ has quit IRC12:27
*** iurygregory has joined #openstack-meeting-312:29
*** yamamoto_ has joined #openstack-meeting-312:29
*** jschwarz has quit IRC12:30
*** dedery has joined #openstack-meeting-312:31
*** coolsvap has quit IRC12:33
*** pgadiya has quit IRC12:37
*** kzaitsev_mb has quit IRC12:38
*** julim has joined #openstack-meeting-312:40
*** yamamoto_ has quit IRC12:40
*** kzaitsev_mb has joined #openstack-meeting-312:42
*** Poornima has quit IRC12:42
*** scottda has joined #openstack-meeting-312:45
*** yamamoto_ has joined #openstack-meeting-312:46
*** dedery has quit IRC12:46
*** yamamoto_ has quit IRC12:47
*** pgadiya has joined #openstack-meeting-312:49
*** yamamoto has joined #openstack-meeting-312:50
*** toddjohn_ has quit IRC12:53
*** yamamoto has quit IRC12:58
*** yamamoto has joined #openstack-meeting-312:59
*** markvoelker has joined #openstack-meeting-313:00
*** alexpilotti has joined #openstack-meeting-313:02
*** ddieterly has joined #openstack-meeting-313:02
*** egallen has joined #openstack-meeting-313:03
*** pgadiya has quit IRC13:04
*** markvoelker has quit IRC13:04
*** markvoelker has joined #openstack-meeting-313:04
*** mtanino has quit IRC13:08
*** sverma has quit IRC13:09
*** baoli has joined #openstack-meeting-313:09
*** lblanchard has joined #openstack-meeting-313:14
*** irenab has quit IRC13:18
*** jlanoux_ has joined #openstack-meeting-313:20
*** sverma has joined #openstack-meeting-313:21
*** reedip__ has quit IRC13:23
*** jlanoux has quit IRC13:23
*** ddieterly has quit IRC13:23
*** zz_dimtruck is now known as dimtruck13:27
*** ddieterly has joined #openstack-meeting-313:28
*** markvoelker has quit IRC13:28
*** alexpilo_ has joined #openstack-meeting-313:29
*** muawiakhan has quit IRC13:29
*** alexpil__ has joined #openstack-meeting-313:30
*** ddieterly has quit IRC13:31
*** alexpilotti has quit IRC13:31
*** pgadiya has joined #openstack-meeting-313:32
*** pgadiya has quit IRC13:34
*** alexpilo_ has quit IRC13:34
*** toddjohn_ has joined #openstack-meeting-313:34
*** tonytan4ever has joined #openstack-meeting-313:35
*** sverma has quit IRC13:39
*** yamamoto has quit IRC13:49
*** spzala has joined #openstack-meeting-313:50
*** dimtruck is now known as zz_dimtruck13:52
*** banix has joined #openstack-meeting-313:54
*** mtanino has joined #openstack-meeting-313:54
*** rbak has joined #openstack-meeting-313:54
*** sverma has joined #openstack-meeting-313:56
*** yamamoto has joined #openstack-meeting-314:02
*** coolsvap has joined #openstack-meeting-314:03
*** sigmavirus24_awa is now known as sigmavirus2414:04
*** vhoward has joined #openstack-meeting-314:07
*** sdake has joined #openstack-meeting-314:08
*** doug-fish has joined #openstack-meeting-314:08
*** xiaohhui has quit IRC14:09
*** zz_dimtruck is now known as dimtruck14:10
*** yamamoto has quit IRC14:11
*** MeganR has quit IRC14:12
*** ddieterly has joined #openstack-meeting-314:12
*** alexpil__ has quit IRC14:13
*** anilvenkata has quit IRC14:16
*** xiaohhui has joined #openstack-meeting-314:22
*** sverma has quit IRC14:23
*** xiaohhui has quit IRC14:23
*** yamamoto has joined #openstack-meeting-314:24
*** haleyb has quit IRC14:24
*** markvoelker has joined #openstack-meeting-314:25
*** galstrom_zzz is now known as galstrom14:26
*** markvoelker has quit IRC14:30
*** yamamoto has quit IRC14:32
*** yamamoto has joined #openstack-meeting-314:34
*** sverma has joined #openstack-meeting-314:36
*** sarob has joined #openstack-meeting-314:36
*** irenab has joined #openstack-meeting-314:42
*** irenab has quit IRC14:43
*** emagana has joined #openstack-meeting-314:48
*** salv-orlando has quit IRC14:49
*** amotoki has joined #openstack-meeting-314:49
*** jlanoux_ has quit IRC14:50
*** salv-orlando has joined #openstack-meeting-314:50
*** toddjohn_ has quit IRC14:53
*** sverma has quit IRC14:53
*** sverma has joined #openstack-meeting-314:55
*** superdan is now known as dansmith14:56
*** vsaienko1 has joined #openstack-meeting-314:59
*** armax has joined #openstack-meeting-314:59
*** julim has quit IRC15:01
*** haleyb has joined #openstack-meeting-315:02
*** julim has joined #openstack-meeting-315:03
*** sneti has quit IRC15:04
*** tonytan4ever has quit IRC15:04
*** sneti has joined #openstack-meeting-315:09
*** toddjohn_ has joined #openstack-meeting-315:14
*** rossella_s has joined #openstack-meeting-315:14
*** maishsk has joined #openstack-meeting-315:18
*** jlanoux has joined #openstack-meeting-315:21
*** toddjohn_ has quit IRC15:24
*** yamahata has joined #openstack-meeting-315:25
*** toddjohn_ has joined #openstack-meeting-315:25
*** toddjoh__ has joined #openstack-meeting-315:26
*** toddjo___ has joined #openstack-meeting-315:28
*** amotoki has quit IRC15:28
*** sverma has quit IRC15:28
*** toddjohn_ has quit IRC15:29
*** doug-fish has quit IRC15:30
*** rstarmer has joined #openstack-meeting-315:30
*** toddjoh__ has quit IRC15:31
*** toddjo___ has quit IRC15:32
*** rstarmer has quit IRC15:35
*** egallen has quit IRC15:37
*** jschwarz_ has quit IRC15:37
*** kmartin has joined #openstack-meeting-315:38
*** maishsk has quit IRC15:42
*** maishsk_ has joined #openstack-meeting-315:42
*** bpokorny has joined #openstack-meeting-315:46
*** Sukhdev has joined #openstack-meeting-315:48
*** MeganR has joined #openstack-meeting-315:51
*** _sarob has joined #openstack-meeting-315:53
*** hshiina has joined #openstack-meeting-315:55
*** sarob has quit IRC15:56
*** vishwanathj has joined #openstack-meeting-315:56
*** muawiakhan has joined #openstack-meeting-316:01
sc`#startmeeting openstack_chef16:02
openstackMeeting started Mon May 16 16:02:07 2016 UTC and is due to finish in 60 minutes.  The chair is sc`. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: openstack_chef)"16:02
openstackThe meeting name has been set to 'openstack_chef'16:02
*** toddjohn_ has joined #openstack-meeting-316:02
*** milan has joined #openstack-meeting-316:02
sc`o/16:02
milano/16:02
*** toddjohn_ has quit IRC16:03
*** toddjohn_ has joined #openstack-meeting-316:03
*** julim has quit IRC16:04
sc`will give about 10 minutes for people to join16:05
*** muawiakhan has quit IRC16:06
*** julim has joined #openstack-meeting-316:06
*** pas-ha has joined #openstack-meeting-316:06
*** egallen has joined #openstack-meeting-316:08
*** toddjohn_ has quit IRC16:08
*** pas-ha has left #openstack-meeting-316:09
*** Swami has joined #openstack-meeting-316:11
*** toddjohn_ has joined #openstack-meeting-316:12
*** salv-orl_ has joined #openstack-meeting-316:15
*** tiendc has joined #openstack-meeting-316:16
sc`didn't think anyone would be around. going to call it16:16
*** toddjohn_ has quit IRC16:16
sc`#endmeeting16:17
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:17
openstackMeeting ended Mon May 16 16:17:01 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:17
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_chef/2016/openstack_chef.2016-05-16-16.02.html16:17
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_chef/2016/openstack_chef.2016-05-16-16.02.txt16:17
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_chef/2016/openstack_chef.2016-05-16-16.02.log.html16:17
*** toddjohn_ has joined #openstack-meeting-316:17
*** salv-orlando has quit IRC16:18
*** toddjohn_ has quit IRC16:21
*** julim has quit IRC16:23
*** lpetrut has quit IRC16:27
*** _sarob has quit IRC16:28
*** julim has joined #openstack-meeting-316:34
*** yuriyz|2 has joined #openstack-meeting-316:38
*** rossella_s has quit IRC16:41
*** kzaitsev_mb has quit IRC16:42
*** lucasagomes has joined #openstack-meeting-316:46
*** revon has joined #openstack-meeting-316:47
*** lekha is now known as lekha-away16:48
*** jlanoux has quit IRC16:49
*** dtantsur has joined #openstack-meeting-316:49
*** blakec has joined #openstack-meeting-316:54
*** ivar-lazzaro has joined #openstack-meeting-316:55
*** pas-ha has joined #openstack-meeting-316:55
*** rama_y has joined #openstack-meeting-316:56
*** rloo has joined #openstack-meeting-316:57
*** mgould has joined #openstack-meeting-316:58
*** ihrachys has quit IRC16:58
*** mat128 has joined #openstack-meeting-316:59
*** mariojv has joined #openstack-meeting-316:59
jroll#startmeeting ironic17:00
openstackMeeting started Mon May 16 17:00:09 2016 UTC and is due to finish in 60 minutes.  The chair is jroll. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: ironic)"17:00
openstackThe meeting name has been set to 'ironic'17:00
jrollhai everyone17:00
mariojvo/17:00
jlvillalo/17:00
mat128o/17:00
rama_yo/17:00
NobodyCam0/17:00
NobodyCam:p17:00
*** sivaramakrishna has joined #openstack-meeting-317:00
yuriyz|2o/17:00
vdroko/17:00
rlooo/17:00
devanandao/17:00
mgouldo/717:00
jroll#chair devananda NobodyCam17:00
openstackCurrent chairs: NobodyCam devananda jroll17:00
jroll#topic announcements and reminders17:00
*** openstack changes topic to "announcements and reminders (Meeting topic: ironic)"17:01
dtantsuro/17:01
blakeco/17:01
lucasagomeso/17:01
jrollso, people have been chugging along on grenade work17:01
jrollit seems to be going well, lots of fun there17:01
vsaienko1o/17:01
NobodyCamgreat work every one!17:01
jrollI also have a chain of patches up for all the deprecated stuff we need to drop, if people want to get that done https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:deprecations17:02
milano/17:02
*** wajdi has joined #openstack-meeting-317:02
sambettso/17:03
jrolllast, looks like the virtual vs physical midcycle doodle is overwhelmingly in support of virtual: http://doodle.com/poll/4vm5ea28t3qyn7bp17:03
*** iyamahat has joined #openstack-meeting-317:03
krtayloro/17:03
jrollI'll send out a more official email about that later[17:03
jrollany other announcements or reminders?17:03
*** thiagop has joined #openstack-meeting-317:03
rloojroll: which means it will be virtual?17:04
jrollrloo: yes17:04
rloojroll: thx. I wanted that yes recorded :D17:04
lucasagomesheh17:04
jrollhah17:04
rloopossible date will be another poll?17:05
jrollmaybe!17:05
rloo:)17:06
jroll#topic subteam status updates17:06
*** openstack changes topic to "subteam status updates (Meeting topic: ironic)"17:06
jrollas always:17:06
jroll#link https://etherpad.openstack.org/p/IronicWhiteBoard17:06
pas-hao/17:06
jrollstarts at line 80 this week17:06
rloodtantsur: wrt spring bug clean up, would it be good for folks to help you. maybe *after* the grenade effort?17:08
jroll++17:08
*** doug-fish has joined #openstack-meeting-317:08
jlvillaljroll: Back-tracking. On the virtual midcycle, are there date-ranges when think it will happen? Can I assume that will be in the follow-up email :)17:09
jrolljlvillal: I haven't thought much about it, sorry17:09
* jlvillal would vote for not conflicting with Nova mid-cycle. Especially since he is on vacation that week :)17:09
jrolljlvillal: it won't, I'll be busy at nova midcycle that week :P17:09
dtantsurrloo, yeah17:10
*** doug-fis_ has joined #openstack-meeting-317:10
*** toddjohn_ has joined #openstack-meeting-317:10
*** toddjohn_ has quit IRC17:10
*** toddjohn_ has joined #openstack-meeting-317:11
jrollanything else on subteam updates?17:11
rloolots of great work done on grenade and gate stuff. i hope you have been chugging beer too.17:11
*** coolsvap has quit IRC17:11
*** Sukhdev has quit IRC17:11
sivaramakrishnavsaienko1: there?17:11
*** doug-fi__ has joined #openstack-meeting-317:12
vsaienko1sivaramakrishna yes17:12
sivaramakrishnaI've rebased the devstack related patches https://review.openstack.org/#/c/256364/ etc17:12
*** david-lyle_ has quit IRC17:12
jrollcan this be taken outside of the meeting? :)17:13
jroll(unless it's a topic for the group17:13
jroll)17:13
jlvillal+117:13
sivaramakrishnasure, jroll17:13
jrollthanks17:13
*** doug-fish has quit IRC17:13
jrollmoving on17:13
*** david-lyle has joined #openstack-meeting-317:13
jroll#topic Active Node Creation/adopt17:13
*** openstack changes topic to "Active Node Creation/adopt (Meeting topic: ironic)"17:13
jroll#link https://review.openstack.org/#/c/27576617:13
* jroll hands rloo the mic17:13
*** doug-fis_ has quit IRC17:14
rlooso i just want to know if we want to have adopt be changed to deploy17:14
rlooif the microversion is older17:14
rloohttps://review.openstack.org/#/c/275766/17/ironic/api/controllers/v1/node.py17:14
rlooline 13317:14
*** qwebirc84709 has joined #openstack-meeting-317:15
rloothere are a few +2 for that patch17:15
rlooi don't think there should be.17:15
devanandarloo: that seems to me to be a good shim for backwards compatibility, eg. with Nova17:15
jrollyeah, I don't recall a group chat about this17:15
devanandarloo: could you explain what risk or negative impact you think it will have?17:15
mat128rloo: I vaguely remember an against against: old API microversion cannot act on "adopt" the same way we can act on "deploy"17:15
jlvillalWhat would it report then? I assume this is just to report the state to an old client.17:15
rloodevananda: well, we don't do anything for eg inspector17:15
NobodyCamI see the point, but I personally don't see a issue with it17:15
devanandajlvillal: that is my understanding as well17:16
rloowe aren't consistent with it. and does it make sense that 'adopt' is 'deploy'?17:16
devanandamake a node in the ADOPTING transition appear to older clients in a way that they understand it17:16
dtantsurjlvillal, the truth like we always do?17:16
*** doug-fi__ has quit IRC17:16
jrollso julia said: "I think we shouldn't be exposing new node states to older clients, and that is represented in the specification, that we conceal to older clients. IMO, it is a breaking change because the state is leveraged for programatic decisions by API clients."17:16
NobodyCamdevananda: jlvillal: that is my understanding too17:16
dtantsurdevananda, the clients have to be ready for unknown states. otherwise any additions breaks them17:16
rloowhat about 'clean'. what should we do there?17:16
jrollif "the state is leveraged for programatic decisions by API clients", we shouldn't lie about the state17:17
dtantsure.g. you can't replace ENROLL with anything. Nor CLEANING.17:17
devanandarloo: inspecting isn't a state within the AVAILABLE->ACTIVE->AVAILABLE cycle, ie, that Nova cares about17:17
dtantsurdevananda, neither is ADOPTING, it does not start with AVAILABLE17:17
rlooi don't want to focus on nova specifically. just want to know how we want to handle this and all states we've added17:17
jrollfwiw, this won't break nova17:17
rloodevananda: are you saying that this is actually needed for nova?17:18
jrollnova only cares if a thing is available or not17:18
jrollhttps://github.com/openstack/nova/blob/master/nova/virt/ironic/driver.py#L17917:18
dtantsuryeah, I don't get the nova argument here too. we introduce new states constantly, it never broke them17:18
* jlvillal wonders if we should have an "UNKNOWN" state to report to older clients? 17:18
jrollthere *is* this: https://github.com/openstack/nova/blob/master/nova/virt/ironic/driver.py#L7217:18
jlvillalYou don't know about this state, go away...17:18
jrollbut you can't unprovision from adopting or deploying, so it's irrelevant17:18
*** yamamoto has quit IRC17:18
rlooso I understand what julia meant wrt not showing new states etc. but the truth is that we haven't been hiding new states. so why start now. or do we want to hide new states?17:18
devanandajroll: right17:18
jrollapparently you can from deploying? wat?17:18
*** yamamoto has joined #openstack-meeting-317:18
dtantsurjlvillal, how will it help anyone?17:18
*** yamamoto has quit IRC17:19
dtantsurexcept for our love to microversion everything?17:19
jrollwhich shows me even more we shouldn't pretend this is deploying17:19
rlooadopting is NOT deploying17:19
lucasagomesI'm a bit out of context (I haven't reviewed the patch) but I tend to agree with rloo re inconsistencies17:19
lucasagomessince it hasn't been the case for other states17:20
jrollso I agree with rloo here, and have commented as such on the patch17:20
jrollif someone can convince me this is necessary for some reason, I'm happy to listen17:20
jlvillalDoes that also imply that clients should not break if they see a state they don't know about?17:20
mat128jlvillal: thought that was already the case17:20
jlvillalIt makes sense to me to have it that way.17:21
*** tonytan4ever has joined #openstack-meeting-317:21
devanandajroll: an older client can not reasonably act on a node in a state that didn't exist in the version which that client was designed for17:21
*** yamamoto has joined #openstack-meeting-317:21
jrolldevananda: do we assert that an older client should be able to reasonably act on a node that is in the ADOPTING state?17:21
mat128devananda: how did we introduce inspecting?17:22
jrolldevananda: especially when we lie about that state?17:22
dtantsurmat128, and enroll. and cleaning (actually cleaning was a troublesome one, it did break nova iirc)17:22
devanandajroll: fair point. nope.17:22
jroll:)17:22
jrollif we lie about the state, bad decisions will be made17:22
*** sivaramakrishna has quit IRC17:23
*** trusted has joined #openstack-meeting-317:24
NobodyCamwould it be better to  obj.provision_state = ir_states.AVAILABLE17:24
jrollso does anyone still agree that we should munge this state in the api response?17:24
dtantsurNobodyCam, oh no, nova will try to use it17:24
jrollNobodyCam: huh?17:24
jrollyeah that17:24
devanandajroll: and if we return the state to older clients, are we certain they'll ignore it?17:24
NobodyCamgah ... Active!!!17:24
NobodyCam:p17:24
lucasagomesNobodyCam, I think no, cause then the client could potentially act against AVAIALBLE17:24
mat128NobodyCam: ACTIVE would be closer to the truth, considering a node will transition into active when it's done17:24
mat128but still lying17:24
*** coolsvap has joined #openstack-meeting-317:25
lucasagomesbut since it's not really AVAILABLE, things can happen (bad ones)17:25
dtantsurNobodyCam, we do support a couple of actions on ACTIVE, which we can't support on ADOPTING17:25
rlooNobodyCam: active won't work either, cuz it is adopting. after adopting, if it succeeds, it will be active.17:25
*** dims_ has joined #openstack-meeting-317:25
devanandamat128: I believe that's the point of the current patch. returning DEPLOYING because the node will transition to ACTIVE when adoption finishes17:25
jrolldevananda: ignore it in terms of... not do something with it or?17:25
devanandajroll: right17:25
jrolldevananda: I mean, I would hope so, but I can't speak for code I don't know17:25
NobodyCamAVAILABLE was bad typing ... ACTIVE was what I was thinking17:25
devanandajroll: as opposed to, say, tyring to do things it can't do (which, you have a valid point, would also happen if we return DEPLOYING and the client tries to DELETE)17:26
mat128NobodyCam: ACTIVE should have instance_uuid, this one wont17:26
vdrokif we want to substitute, deploying is the best fit I think, actions are the same. but it seems we don't17:26
jrolldevananda: "if state is something I've never coded for, do something destructive" sounds crazy, if someone writes that code that's their own gun pointed at their feet imo17:26
lucasagomesmat128, not necessarily if used in stand-alone mode17:26
*** dims has quit IRC17:26
mat128lucasagomes: true..17:26
dtantsurACTIVE is a stable state, I don't think we should consider it..17:27
lucasagomesmat128, but ACTIVE does allow user to delete the instance (which can turn out bad)17:27
devanandajroll: I've seen code assume things like "if state in LIST_OF_STATES: do this; else: do that;"17:27
lucasagomesyeah I think the best fit is actually DEPLOYING, but not sure it's _required_17:27
devanandajroll: so it is code like that I am concerned about17:27
mat128lucasagomes: what happens if we just return ADOPTING? Can we confirm it won't break a node-list on older client?17:27
vdrokand btw, nova won't manage adopted nodes right?17:27
jrolldevananda: yeah, but 'that' being something destructive? idk17:27
devanandalucasagomes: fwiw, ADOPTING does not allow delete17:27
devanandahttps://review.openstack.org/#/c/275766/17/ironic/common/states.py17:27
rloolook, we have a lot of new states since 'adopting' (sorry) the new state machine: http://docs-draft.openstack.org/66/275766/17/check/gate-ironic-docs/52915ef//doc/build/html/_images/states.svg17:28
*** ddieterly is now known as ddieterly[away]17:28
dtantsurdevananda, then here's the question: are we ready to do it every time now? even when we don't have a good candidate? like imagine we would have to introduce ENROLL.17:28
lucasagomesdevananda, yup yeah that's reinforce the idea of not using ACTIVE to mask it17:28
rloowe do not (yet) handle masking new states from older versions.17:28
lucasagomesmat128, we can totally test that, it should not off the top of my head17:28
dtantsur(apparently we broken all that people when we did it already, so now they're ready :D )17:28
devanandadtantsur: yea, we've had similar discussions (and difficulties) every time we've introduced new states17:28
* jroll pulls the pin and asks "is our state machine part of our api contract?"17:29
devanandajroll: yes17:29
rlooit seems like we introduced microversions when we introduced enroll. the versioning was meant to handle these new states.17:29
*** piet has joined #openstack-meeting-317:29
dtantsurrloo, we introduced microversions on NOSTATE->AVAILABLE change17:29
dtantsurwhich was breaking for nearly everyone starting with Nova17:29
devanandajroll: the list of "verbs" that an API accepts is part of that contract17:30
jlvillalhmmm NOSTATE...17:30
dtantsurit's unclear to me whether introducing ADOPTING breaks anyone, who already recovered from ENROLL and CLEANING17:30
*** coolsvap_ has joined #openstack-meeting-317:30
jrolldevananda: yes, but that isn't strictly the state machine17:30
rloo++ dtantsur17:30
devanandajroll: it is how one interacts with the state machine17:30
dtantsurbut NOSTATE is different, it IS a synonym for AVAILABLE17:30
jrolldevananda: I'm asking e.g. is the list of possible states part of the api contract?17:30
mgouldISTM the real problem is that we have no way of saying "your client must be at least this recent to talk to me"17:30
jrolldevananda: are transient states part of the contract?17:31
jrolletc17:31
mat128state machine changed when new nodes started in "enroll" instead of "available"17:31
devanandajroll: ok. that's slightly different than the acceptable verbs, but I also believe that's part of the contract17:31
devanandajroll: think of a programming API. if a function introduces a different return code, is that a change in the contract?17:31
jlvillalI said this before, but can the contract also be if you see a state you don't know about don't crash and don't try to do things on that node.17:31
rlooit seems to me that if someone does something to ironic using version X, we shouldn't have to guarantee that everything will work loverly if they then use version X-i.17:32
mat128rloo: but staying on version X and not hiding ADOPT means I will see ADOPT at some point17:32
mat128just because Ironic was upgraded, but api version stayed the same17:32
*** doug-fish has joined #openstack-meeting-317:32
jrolldevananda: well, it depends, right? do the docs for that function say "returns an integer" or "returns an integer, one of [0, 1, 2, 3]"17:33
rloomat128: i mean microversion. you mean v1/v2 of the URL?17:33
dtantsurmat128, meaning someone in your cloud started using X+i and new features...17:33
devanandajroll: indeed17:33
*** dedery has joined #openstack-meeting-317:33
* mgould thinks we're doing this backwards17:33
mgouldclient sets the API version, server tries to handle it17:34
mgouldit should be the server that sets the version, and the client that has to adjust17:34
*** coolsvap has quit IRC17:34
jrolldevananda: and here is our doc on the Node object in an api response http://docs.openstack.org/developer/ironic/webapi/v1.html#ironic.api.controllers.v1.node.Node.provision_state17:34
dtantsurmgould, well, that's not the intention of API versioning in our case :)17:34
jrolldevananda: which is "Represent the current (not transition) provision state of the node"17:34
rloomgould: that won't work; it'd really break clients.17:34
mat128why not hide anything that doesnt exist for a microversion under an "UNKNOWN" state?17:34
devanandamgould: we have a mechanism in place for the server to indicate the minimum version the client must support to interact with it17:34
dtantsurmat128, how is it different? people start seeing UNKNOWN nodes at random stages of their lifecycle17:35
devanandamgould: are you suggesting that we should raise that minimum version?17:35
*** yamamoto has quit IRC17:35
mgoulddevananda, yes17:35
dtantsurhmmmmmm17:35
devanandathat's interesting17:35
mat128dtantsur: yes, but at least it keeps working. If we require a new-enough client, that means I can't even upgrade Ironic17:35
*** coolsvap_ is now known as coolsvap17:35
mgouldbut IIRC the last time we had this discussion we concluded that we could never ever raise it17:35
mat128dtantsur: If you want to know what the UNKNOWN means, you can always use a newer API version17:35
dtantsurmat128, we don't require anything. you just should not make assumptions about things we explicitly don't guarantee. like that we'll never add more states.17:36
mgouldbecause by definition that would break clients17:36
devanandawe could, in a response that includes nodes with ADOPTING state, include the X-OpenStack-ironic-API-Min-Version: 1.xx header17:36
devanandajust for that response17:36
pas-hanever ever is too heavy brick to carry17:36
jroll...17:36
mgouldpas-ha, exactly17:36
jrolldevananda: pls no17:36
rlooi think raising the minimum version is a different discussion. unless you thinkwe should raise it whenever we have something that isn't 'backwards compatible'17:36
devanandaI haven't thought this through yet - just tossing the idea out17:36
mgouldrloo, YES! :-)17:36
dtantsurdevananda, I already imaging getting bugzillas like "ironicclient crashes on my deployment"...17:36
dtantsurI mean, I like your idea, but only in an ideal world :)17:36
devanandajroll: I don't mean "raise it all the time" - just raise it for the response that includes incompatible things17:36
*** hshiina has left #openstack-meeting-317:36
devanandadtantsur: hehe17:37
jrollrloo: mgould: that completely defeats the purpose of versioning at all17:37
rloomgould: that is totally against the idea behind microversions17:37
jrollyeah17:37
jrollmight as well just not version17:37
* dtantsur feels like the discussion goes a bit too far17:37
* lucasagomes feels the same17:37
jrolldevananda: right, I think a minimum that changes based on the endpoint or response is HOLY COW17:37
rloojroll: right, and i have to say, i like that idea. not versioning and not caring about breaking people's stuff.17:37
devanandaso, I believe this is actually exactly what version negotiation is for17:37
devanandarather than the client to behave unexpectedly when it gets a result it does'nt understand17:37
dtantsurrloo++17:38
mgouldjroll, oh right, I don't like the idea of min-version being a function of endpoint either17:38
devanandait would fail early with a message such as "unable to talk to this endpoint, required version XX"17:38
*** doug-fish has quit IRC17:38
*** trusted has quit IRC17:38
devanandaalso, yea, we're pretty far off track now ...17:38
jrollreal talk: do we expect a deployment that is using this feature to ever use a version lower than the one that introduces this feature?17:38
dtantsurI hope not, but I'm afraid yes17:39
vdrokcan we just state somewhere - don't do anything with a node in a state you don't know about? Is it enough?17:39
*** trusted has joined #openstack-meeting-317:39
sambettswouldn't that lead to the client failing transiently? e.g. if I did a node-list it would work sometimes but not others17:39
NobodyCamdtantsur: ++17:39
dtantsure.g. imagine people using 3rd party tooling for Ironic17:39
jrollgreat :|17:39
jrollok, so this comes down to two sides:17:39
devanandajroll: absolutely17:39
jroll1) lie about the actual state of the node17:39
jroll2) pass an unknown state to clients17:39
mgouldjroll: 1.1) lie in different ways about the actual state of the node to different clients17:40
mat128we have 3rd party tooling for Ironic here, and from checking: it wont crash for an unknown state (thankfully), but if we raise min-version is breaks :(17:40
rloo3) return the actual state17:40
jrollrloo: 2 == 317:40
dtantsurI think 3==217:40
lucasagomesrloo, I think that's 217:40
lucasagomesyeah17:40
rloooh, sorry.17:40
jlvillalI vote for 2   https://en.wikipedia.org/wiki/Robustness_principle17:40
wajdireport the correct state, but indicate to the client that the version does not allow for manipulating that state?17:40
jroll2) pass a new unknown state to clients17:40
jlvillalAs in the clients should be robust in accepting unknown states.17:40
* rloo thought 2 was a new "unknown" state.17:41
mat128"UNKNOWN" or actual state should be no different if clients are coded correctly17:41
jroll2) pass a new unknown state (adopting) to clients17:41
jroll:)17:41
mat128I'm afraid they might not, so "UNKNOWN" might help us in the future17:41
rloo2) is consistent with what we are doing currently17:41
vdrokwajdi: but then older clients won't understand this indication? :)17:41
*** dedery has quit IRC17:42
dtantsurmat128, if they care about adopting UNKNOWN, they might as well care about avoiding hardcoding the whole list of states17:42
jrolldo we need some sort of formal meeting/ML vote on this, or can we be adults and handle it in gerrit?17:42
jroll(and is there more to discuss?)17:42
thiagopjroll: I think you shoud do a "vote" to clarify options due to the confusion in 217:42
rloowhy can't we vote now?17:42
mat128dtantsur: thats why I said "if they are coded properly", fwiw the only 3rd party client I know of would accept either17:42
jlvillalDoes: pass a new unknown state to clients in this particular case mean "ADOPTING".  Assuming it doesn't mean a state "UNKNOWN"17:42
devanandajroll: fwiw, after discussing this, I agree with (2)17:43
lucasagomesI think 2 is consistent to what've done in the past. Plus, adopting is a rare (for lack of better word) state? Since it's used to migrate existing workloads to ironic and should not happen often17:43
NobodyCamjust pointing out that the author is not here for this.17:43
rlooNobodyCam: the author was fine with a vote on it. see her comments.17:43
devanandaI had thought that (1) would allow it to be compatible with existing clients (eg, Nova), but it clearly won't be17:44
devanandalucasagomes: in some environments, it may not be all that rare17:44
rlooNobodyCam: line 136, https://review.openstack.org/#/c/275766/12/ironic/api/controllers/v1/node.py17:44
lucasagomesdevananda, fair, but it's like a operator driving action. It's not like CLEANING which is actually part of the "main loop"17:44
devanandalucasagomes: true17:45
dtantsurdevananda, out of curiosity: do you envision using both Nova and ADOPT in one deployment? ADOPT does not play with nova at all, right?17:45
jrollokay are folks ready to vote on this then?17:45
dtantsur(feel free to answer in channel)17:45
devanandadtantsur: absolutely17:45
devanandaimagine a phased migration of a very large existing bare metal deployment -- as existing DCs are connected to the nova+ironic management layer ,they get "adopted"17:45
mariojvready to vote17:45
jroll#startvote should we (1) change the provision_state in the api response to deploying or (2) return the actual (adopting) provision_state in the api response? 1, 217:46
openstackBegin voting on: should we (1) change the provision_state in the api response to deploying or (2) return the actual (adopting) provision_state in the api response? Valid vote options are 1, 2.17:46
openstackVote using '#vote OPTION'. Only your last vote counts.17:46
mat128devananda: then there's the issue of "how do I get instances without deploying anything?" :)17:46
devanandajroll: ++17:46
jroll#vote 217:46
dtantsur#vote 217:46
lucasagomes#vote 217:46
mariojv#vote 217:46
jlvillal#vote 217:46
mgould#vote 217:46
mat128#vote 217:46
devananda#vote 217:46
NobodyCam#vote 217:46
vdrok#vote 217:46
thiagop#vote 217:46
sambetts#vote 217:46
wajdi#vote 217:46
devanandamat128: you mean eg. boot from volume?17:46
jrolland somehow we're still talking about this? :)17:47
rloo#vote 217:47
mat128devananda: like I have a thousand machines to "import" into the OpenStack world, they come from an old world system17:47
* jroll gives it another 2 minutes or so17:47
mat128I want instances and nodes, but must not touch power state or data17:47
devanandajroll: good job getting everyone to a concensus :)17:47
jrollheh17:47
mat128devananda: This bp helps me getting the nodes in, but instances are something else that has to be taken care of17:47
devanandamat128: ah - I see. you mean how to create the corresponding Nova instances?17:48
rloomat128: yes, it doesn't address how to hook it in with nova.17:48
mat128devananda: exactly17:48
jrollmat128: insert into instances ...; "D17:48
mat128rloo: yup, that's future work17:48
jrolls/"D/:D17:48
mat128Haha17:48
devanandajroll: :)17:48
mat128we were aiming more for nova boot with nodes on the fake driver, but whatever works17:48
mat128you have to deal with Neutron and stuff17:48
mat128#offtopic17:48
mat128next?17:48
jrollya17:49
jroll#endvote17:49
openstackVoted on "should we (1) change the provision_state in the api response to deploying or (2) return the actual (adopting) provision_state in the api response?" Results are17:49
openstack2 (14): lucasagomes, devananda, rloo, jlvillal, mariojv, mgould, mat128, dtantsur, jroll, NobodyCam, wajdi, sambetts, vdrok, thiagop17:49
jrollnow17:49
jrollplease go apply those votes in gerrit :)17:49
*** Ravikiran_K has joined #openstack-meeting-317:49
jroll#topic open discussion17:49
*** openstack changes topic to "open discussion (Meeting topic: ironic)"17:49
* jroll welcomes people to throw random dates at him for midcycle-ing17:49
jrollthe week of june 27 and july 18 are out17:50
lucasagomesjroll, I would end of june ?17:50
lucasagomesI will, *17:50
rloojroll: would it be useful before or after nova or doesn't matter?17:50
jrollrloo: not sure it matters17:50
lucasagomesjroll, btw, how many days? 3 days?17:50
dtantsurI'm out July 22-2917:50
thiagoprloo: good question17:50
jrollfwiw, I'd like to do it earlier and maybe have a second one late in the cycle :)17:51
jrolllucasagomes: yeah, I think 3 days works17:51
*** s3wong has joined #openstack-meeting-317:51
jrollbut whatever y'all think is good17:51
jlvillalJune looks good for me. and early July.17:51
vdroksame for me17:51
mariojv++ end of june17:51
jrollbtw, here's newton schedule http://releases.openstack.org/newton/schedule.html17:51
lucasagomes27-29 June17:51
jrolllucasagomes: I won't be around that week :/17:52
rloodidn't jroll mention that the week of june 27 is out?17:52
jlvillalAnd I like the idea of trying to get in two of them. One soon and one later.17:52
rloois june 20 too soon?17:52
jrollI guess we could do it that week, you all don't need me there :)17:52
lucasagomesjroll, right, 20-22 maybe?17:52
jrollyeah I'm good with the week of the 20th17:52
vdrokand when is nova's midcycle?17:52
jlvillalMaybe only two days for 2nd one.  Third day was sort of quiet last time.17:52
mariojv20th wfm too17:52
NobodyCamI'll be out 21st as its my birthday17:52
jrollvdrok: july 19-2117:52
rloojuly 11?17:53
mariojvmaybe a doodle would be good for this17:53
NobodyCam7/11 wfm17:53
*** doug-fish has joined #openstack-meeting-317:53
mat128mariojv: +1 for doodle17:53
jrollyeah, planning on a doodle17:53
jrolljust wanted to hear initial ideas17:53
rlooi think those two weeks are the candidates. june 20 & july 11. cuz i said so :D17:54
vdrokjroll: just wondering as there is this generic resource pools, we might want to sync on this somehow with nova?17:54
*** baoli has quit IRC17:54
rloovdrok: ++. but jroll will be at nova mid-cycle.17:54
jrollvdrok: totally, I'll try to get jaypipes at our midcycle, I'll also be at nova's17:54
vdrokcool, thanks :)17:55
*** baoli has joined #openstack-meeting-317:55
rlooit might almost be worth having a separate meeting *just* to discuss resource pools/etc.17:55
jrollyeah17:55
rloolike soon. in next 2 weeks or so. cuz i am guessing we will procrastinate and not look/think about it until we have to.17:56
jrollyeah17:56
rlooerr. I mean, like after we get grenade working.17:56
jrollto be clear I don't think there's even the nova spec up for that17:56
vdrokjroll: there is17:56
jrollbut we should figure it out and get started on the ironic side17:56
rlooyou mean jay pipe's spec? there is.17:56
jrollkinda, it's wip17:57
jrollhttps://review.openstack.org/#/c/312696/17:57
jrolloh, y'all are already reviewing, good17:57
rlooyeah, that one.17:57
vdrokalso this one, knid of related - https://review.openstack.org/#/c/300176/17:58
rloovdrok: OH. I wondered if generic resource pools was already a thing or not.17:58
NobodyCam*two minutes left*17:58
*** doug-fish has quit IRC17:58
jrollyeah, that's the earlier step in the chain17:58
vdrokrloo: not yet :)17:58
*** flwang1 has joined #openstack-meeting-317:58
rloovdrok: i didn't see anything in the first spec that mentions the second spec.17:59
rloothis ain't going to be done in Newton.17:59
*** s3wong has quit IRC17:59
*** doug-fish has joined #openstack-meeting-317:59
vdrokrloo: there is only a name of bp somewhere in the spec itself17:59
jrollprobably not, but if we can all agree on the path, we can get whatever we need done on the ironic side17:59
*** Eva-i has joined #openstack-meeting-317:59
rloojroll: exactly.18:00
*** baoli has quit IRC18:00
vdrokwe can do search api anyway18:00
rlooyup, i think search and claims API can still be done.18:00
jrollwell, it's unclear if we need a search api18:00
flwang1hi guys18:00
jrolloh, out of time18:00
rloosearch API is useful regardless, don't you htink?18:00
Eva-ihello18:00
jrollflwang1: we'll be in #openstack-ironic if you're looking for us18:00
jlvillaltime!18:00
rlooalthough maybe not a high priority any more.18:00
jroll#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Mon May 16 18:00:47 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2016/ironic.2016-05-16-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2016/ironic.2016-05-16-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2016/ironic.2016-05-16-17.00.log.html18:00
*** dtantsur has left #openstack-meeting-318:01
mariojvhave a good day all18:01
jrollflwang1: if you're here for another meeting, sorry for running late on this one :)18:01
*** mariojv has left #openstack-meeting-318:01
*** pas-ha has left #openstack-meeting-318:01
flwang1jroll: no worries18:01
*** yuriyz|2 has left #openstack-meeting-318:01
*** blakec has left #openstack-meeting-318:01
*** wajdi has left #openstack-meeting-318:01
*** thiagop has left #openstack-meeting-318:01
flwang1#startmeeting zaqar18:01
openstackMeeting started Mon May 16 18:01:40 2016 UTC and is due to finish in 60 minutes.  The chair is flwang1. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: zaqar)"18:01
Eva-iflwang1: vkmc: flaper87: hello18:01
openstackThe meeting name has been set to 'zaqar'18:01
vkmco/18:01
vkmchey18:01
*** mat128 has left #openstack-meeting-318:01
*** s3wong has joined #openstack-meeting-318:01
flwang1#topic roll call18:01
*** openstack changes topic to "roll call (Meeting topic: zaqar)"18:02
flwang1o/18:02
*** lucasagomes has left #openstack-meeting-318:02
Eva-io/18:02
flwang1seems we will miss flaper87 and ryansb18:02
vkmco/18:02
*** rloo has left #openstack-meeting-318:03
*** numans has quit IRC18:03
Eva-iyes18:03
*** trusted has quit IRC18:03
flwang1so like i mentioned, today's agenda will be simple18:03
flwang1some important patch to review and the assignments for newton18:04
flwang1#topic code review18:04
*** openstack changes topic to "code review (Meeting topic: zaqar)"18:04
*** baoli has joined #openstack-meeting-318:05
Eva-iI think this patch is important: https://review.openstack.org/#/c/294368/. But I haven't reviewed it yet.18:05
flwang1i think Eva-i's patch for subscription's age are ready to go18:05
flwang1Eva-i: yep, thanks for raising it. blame me.18:06
Eva-iyeah, these patches: https://review.openstack.org/#/c/288907/ https://review.openstack.org/#/c/288908/18:06
Eva-iflwang1: no, you blame me18:06
flwang1we need to get the client patch in, asap18:06
flwang1in N-1 and after that, i will release a new version for our client18:06
*** julim has quit IRC18:07
Eva-ioki =/18:07
*** julim has joined #openstack-meeting-318:08
flwang1and my tempest patch, though it's redis gate is still strugling https://review.openstack.org/30247918:09
flwang1i guess our sqlalchemy code is not thread safe18:09
flwang1and Eva-i's redis claim fix https://review.openstack.org/#/c/314273/18:10
*** mgould has quit IRC18:10
Eva-iyes, I would like it18:11
flwang1i know after the summit, many peoples are not in the good status to coding/reviewing, but let's rock on since now :)18:11
flwang1s/to/for18:11
Eva-iyes =)18:12
flwang1ok, anything else we need to talk for code review?18:12
Eva-iflwang1: I think no18:13
*** toddjohn_ has quit IRC18:13
flwang1Eva-i: ?18:13
Eva-ilet's discuss assignments18:13
Eva-iflwang1: I asked your question18:13
flwang1#topic newton assignments18:14
*** openstack changes topic to "newton assignments (Meeting topic: zaqar)"18:14
*** sambetts is now known as sambetts|afk18:15
*** toddjohn_ has joined #openstack-meeting-318:15
*** doug-fis_ has joined #openstack-meeting-318:15
flwang1we still have a lot of things to do given our team size18:15
Eva-iSo I assigned to myself "install guide" and "lazy queues in subscriptions". If everything will go smooth and fast, I'll take "improved notifications".18:15
*** toddjohn_ has quit IRC18:16
*** toddjohn_ has joined #openstack-meeting-318:16
*** numans has joined #openstack-meeting-318:16
*** dedery has joined #openstack-meeting-318:16
*** Ravikiran_K has quit IRC18:16
Eva-iI haven't taken much tasks, because I think I should start getting job.18:16
flwang1Eva-i: ok, pls remind me, do we have a spec for lazy queue for subscription?18:16
Eva-iflwang1: yes, we have18:17
flwang1Eva-i: i think i have merged it, right?18:17
Eva-iflwang1: let's see18:17
*** doug-fish has quit IRC18:18
flwang1oh, it's merged18:18
flwang1awesome18:18
Eva-ioh, oki18:18
vkmcdo we have all the bps registered for newton?18:18
flwang1Eva-i: let's get it done in N-118:18
Eva-iflwang1: yes, I remember18:18
flwang1vkmc: not yet18:18
vkmcI know that some features were discussed in previous meetings, but it would be nice to get all of them in a single place18:18
Eva-iflwang1: can you approve then blueprint? https://blueprints.launchpad.net/zaqar/+spec/lazy-queues-in-subscriptions18:19
flwang1vkmc: i think only the notifitication format improvement hasn't been registered18:19
*** jtomasek has quit IRC18:19
flwang1Eva-i: done :)18:20
Eva-ivkmc: I think here are all tasks https://etherpad.openstack.org/p/newton-zaqar-assignment18:20
vkmck k18:20
Eva-iflwang1: thanks18:20
vkmcthanks Eva-i18:20
*** doug-fis_ has quit IRC18:21
flwang1#link  https://etherpad.openstack.org/p/newton-zaqar-assignment18:21
*** doug-fish has joined #openstack-meeting-318:21
flwang1vkmc: except the sqlalchemy migration, anything else you would like to take?18:21
vkmcflwang1, looking on the list right now, I'll let you guys know offline18:22
Eva-iI think I need some help with install guide, it's almost ready, just one little problem blocks me18:22
Eva-iflwang1: can we discuss the problem in Zaqar chat later?18:23
flwang1vkmc: ok, cool18:23
flwang1Eva-i: sure18:23
vkmcthanks18:23
flwang1i think i will work on the api ref doc and the dead letter queue18:24
flwang1and walk around as a waiter18:24
*** yamamoto has joined #openstack-meeting-318:24
flwang1or fireman18:24
Eva-ioh18:25
Eva-iokay18:26
*** doug-fish has quit IRC18:26
*** yamahata has quit IRC18:26
flwang1and except those big tasks, we still have some small work to do18:27
flwang1like fix the rally gate job18:27
flwang1fix the tempest gate job18:27
flwang1improve our log18:27
*** yamahata has joined #openstack-meeting-318:27
flwang1improve our tests of py318:27
*** ddieterly[away] has quit IRC18:28
Eva-iyes, I'm not sure though I'll be able to spend much time of them18:29
Eva-i*for them18:29
flwang1and another big job is support any potential user who would like to deploy zaqar in prod18:29
flwang1and more integration with other projects18:30
vkmcyeah18:30
vkmcI'm aware that tripleo and heat are the ones using Zaqar atm18:30
flwang1in Newton, i would like to see the integration with senlin18:30
vkmcbut we had integration with Sahara, Senlin and Horizon pending18:30
vkmcdifferent use cases18:30
flwang1vkmc: ceilometer(aodh) has integrated with zaqar in Mitaka18:30
vkmcnice18:30
flwang1horizon's integration depends on the integration with searchlight18:31
Eva-iYes, integration is important. It's something that makes Zaqar more popular.18:31
flwang1#link bp of searchlight https://review.openstack.org/#/c/246220/18:31
*** pvaneck has joined #openstack-meeting-318:33
*** Sukhdev has joined #openstack-meeting-318:33
*** muawiakhan has joined #openstack-meeting-318:33
flwang1so actually, we have tons of things to do18:33
flwang1but our team is still very small18:33
flwang1so another job is broadcasting the signal: zaqar is interesting, we need more people18:34
Eva-izaqar needs funny youtube vids18:35
*** ddieterly has joined #openstack-meeting-318:35
flwang1personally, i think the future of Openstack will need more upper layer service to build a good eco system(like aws), and zaqar is one of the critical parts18:35
*** coolsvap is now known as coolsvap|zzzzzzz18:36
flwang1Eva-i: yep, and we need some sample code, video, docs18:36
*** pfreund has left #openstack-meeting-318:36
flwang1ok, given we're missing peoples in this meeting18:38
flwang1so we may need to discuss those tasks' assignments  later/offline18:38
Eva-ioki18:39
flwang1#topic open discussion18:39
*** openstack changes topic to "open discussion (Meeting topic: zaqar)"18:39
flwang1anything else we can discuss?18:39
Eva-ino, I think18:39
*** lpetrut has joined #openstack-meeting-318:40
flwang1vkmc: any comments?18:41
flwang1ok18:42
flwang1Eva-i: thank you for joining18:42
vkmcnothing from me18:42
flwang1#endmeeting18:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:42
openstackMeeting ended Mon May 16 18:42:37 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zaqar/2016/zaqar.2016-05-16-18.01.html18:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zaqar/2016/zaqar.2016-05-16-18.01.txt18:42
openstackLog:            http://eavesdrop.openstack.org/meetings/zaqar/2016/zaqar.2016-05-16-18.01.log.html18:42
vkmco18:42
vkmco/18:42
vkmcthx18:42
*** kzaitsev_mb has joined #openstack-meeting-318:42
*** toddjohn_ has quit IRC18:43
*** tfukushima has quit IRC18:43
*** toddjohn_ has joined #openstack-meeting-318:43
*** tiendc has quit IRC18:44
*** krtaylor has quit IRC18:44
*** egallen has quit IRC18:49
*** muawiakhan has quit IRC18:50
*** numans has quit IRC18:56
*** banix has quit IRC18:58
*** baoli has quit IRC18:59
*** doug-fis_ has joined #openstack-meeting-319:00
*** doug-fis_ has quit IRC19:02
*** woodster_ has joined #openstack-meeting-319:03
*** sarob has joined #openstack-meeting-319:04
*** Swami has quit IRC19:04
*** mickeys has joined #openstack-meeting-319:05
*** Swami has joined #openstack-meeting-319:06
*** salv-orl_ has quit IRC19:07
*** Swami has quit IRC19:14
*** lpetrut has quit IRC19:24
*** tonytan4ever has quit IRC19:27
*** mickeys has quit IRC19:29
*** mickeys has joined #openstack-meeting-319:29
*** mickeys has quit IRC19:33
*** baoli has joined #openstack-meeting-319:45
*** doug-fish has joined #openstack-meeting-319:46
*** baoli has quit IRC19:46
*** baoli has joined #openstack-meeting-319:47
*** yamahata has quit IRC19:48
*** iyamahat has quit IRC19:49
*** dedery has quit IRC19:50
*** toddjohn_ has quit IRC19:51
*** dedery has joined #openstack-meeting-319:52
*** toddjohn_ has joined #openstack-meeting-319:53
*** dedery has quit IRC19:53
*** tonytan4ever has joined #openstack-meeting-319:53
*** mbound has joined #openstack-meeting-319:54
*** toddjoh__ has joined #openstack-meeting-319:56
*** toddjohn_ has quit IRC19:57
*** toddjoh__ has quit IRC19:57
*** toddjohn_ has joined #openstack-meeting-319:58
*** doug-fis_ has joined #openstack-meeting-320:00
*** doug-fi__ has joined #openstack-meeting-320:01
*** Swami has joined #openstack-meeting-320:01
*** doug-f___ has joined #openstack-meeting-320:02
*** flwang1 has quit IRC20:04
*** doug-fish has quit IRC20:04
*** doug-fis_ has quit IRC20:05
*** doug-fi__ has quit IRC20:05
*** sarob has quit IRC20:07
*** baoli has quit IRC20:07
*** baoli has joined #openstack-meeting-320:08
*** _sarob has joined #openstack-meeting-320:08
*** iyamahat has joined #openstack-meeting-320:08
*** krtaylor has joined #openstack-meeting-320:08
*** baoli has quit IRC20:09
*** baoli has joined #openstack-meeting-320:09
*** piet has quit IRC20:10
*** Sukhdev has quit IRC20:10
*** toddjohn_ has quit IRC20:11
*** yamahata has joined #openstack-meeting-320:12
*** toddjohn_ has joined #openstack-meeting-320:12
*** rama_y has quit IRC20:12
*** toddjohn_ has quit IRC20:16
*** salv-orlando has joined #openstack-meeting-320:17
*** rama_y has joined #openstack-meeting-320:19
*** toddjohn_ has joined #openstack-meeting-320:20
*** toddjohn_ has quit IRC20:22
*** stanzgy has joined #openstack-meeting-320:23
*** qwebirc84709 has quit IRC20:28
*** doug-f___ has quit IRC20:29
*** baoli has quit IRC20:29
*** igorn has quit IRC20:30
*** iurygregory has quit IRC20:30
*** gabriel-bezerra has quit IRC20:30
*** stanzgy has quit IRC20:30
*** doug-fish has joined #openstack-meeting-320:31
*** krtaylor has quit IRC20:32
*** gabriel-bezerra has joined #openstack-meeting-320:32
*** iurygregory has joined #openstack-meeting-320:34
*** igorn has joined #openstack-meeting-320:35
*** sdake has quit IRC20:37
*** sdake has joined #openstack-meeting-320:37
*** gabriel-bezerra has quit IRC20:40
*** gabriel-bezerra has joined #openstack-meeting-320:41
*** tonytan4ever has quit IRC20:47
*** tonytan4ever has joined #openstack-meeting-320:47
*** bpokorny_ has joined #openstack-meeting-320:48
*** bpokorny_ has quit IRC20:49
*** bpokorny_ has joined #openstack-meeting-320:49
*** CIA has quit IRC20:51
*** doug-fis_ has joined #openstack-meeting-320:51
*** _sarob has quit IRC20:52
*** bpokorny has quit IRC20:52
*** ddieterly is now known as ddieterly[away]20:52
*** sarob has joined #openstack-meeting-320:53
*** doug-fish has quit IRC20:54
*** baoli has joined #openstack-meeting-320:55
*** julim has quit IRC20:55
*** hichihara has joined #openstack-meeting-320:56
*** rtheis has quit IRC20:59
*** mickeys_ has joined #openstack-meeting-320:59
*** ddieterly[away] is now known as ddieterly20:59
*** Sukhdev has joined #openstack-meeting-321:01
*** vhoward has quit IRC21:08
*** lblanchard has quit IRC21:15
*** doug-fis_ has quit IRC21:17
*** doug-fish has joined #openstack-meeting-321:18
*** doug-fish has quit IRC21:22
*** qwebirc85867 has joined #openstack-meeting-321:22
*** doug-fish has joined #openstack-meeting-321:25
*** mickeys_ has quit IRC21:26
*** doug-fish has quit IRC21:26
*** doug-fish has joined #openstack-meeting-321:27
*** bpokorny_ has quit IRC21:30
*** bpokorny has joined #openstack-meeting-321:31
*** doug-fish has quit IRC21:32
*** doug-fish has joined #openstack-meeting-321:33
*** dimtruck is now known as zz_dimtruck21:35
*** doug-fish has quit IRC21:37
*** doug-fish has joined #openstack-meeting-321:38
*** doug-fish has quit IRC21:38
*** flwang1 has joined #openstack-meeting-321:38
*** doug-fish has joined #openstack-meeting-321:38
*** ivar-laz_ has joined #openstack-meeting-321:45
*** spzala has quit IRC21:46
*** toddjohn_ has joined #openstack-meeting-321:46
*** toddjohn_ has quit IRC21:47
*** neiljerram has quit IRC21:47
*** toddjohn_ has joined #openstack-meeting-321:47
*** ivar-lazzaro has quit IRC21:48
*** galstrom is now known as galstrom_zzz21:51
*** toddjohn_ has quit IRC21:52
*** flwang1 has quit IRC21:55
*** markvoelker has joined #openstack-meeting-321:57
*** markvoelker has quit IRC22:01
*** tonytan4ever has quit IRC22:01
*** markvoelker has joined #openstack-meeting-322:01
*** MeganR has quit IRC22:03
*** toddjohn_ has joined #openstack-meeting-322:06
*** toddjohn_ has quit IRC22:07
*** doug-fish has quit IRC22:07
*** toddjohn_ has joined #openstack-meeting-322:08
*** sigmavirus24 is now known as sigmavirus24_awa22:09
*** mickeys has joined #openstack-meeting-322:09
*** Eva-i has quit IRC22:10
*** flwang1 has joined #openstack-meeting-322:11
*** toddjohn_ has quit IRC22:12
*** toddjohn_ has joined #openstack-meeting-322:13
*** doug-fis_ has joined #openstack-meeting-322:13
*** salv-orl_ has joined #openstack-meeting-322:14
*** doug-fi__ has joined #openstack-meeting-322:16
*** hichihara has quit IRC22:17
*** salv-orlando has quit IRC22:18
*** doug-fis_ has quit IRC22:18
*** toddjohn_ has quit IRC22:18
*** Sukhdev has quit IRC22:20
*** Sukhdev has joined #openstack-meeting-322:21
*** doug-fi__ has quit IRC22:21
*** ivar-laz_ has quit IRC22:32
*** ivar-lazzaro has joined #openstack-meeting-322:33
*** piet has joined #openstack-meeting-322:36
*** doug-fish has joined #openstack-meeting-322:40
*** mickeys has quit IRC22:43
*** doug-fish has quit IRC22:44
*** rbak has quit IRC22:48
*** piet has quit IRC22:50
*** sdague has quit IRC22:50
*** piet has joined #openstack-meeting-322:52
*** emagana has quit IRC22:52
*** qwebirc85867 has quit IRC22:53
*** zz_dimtruck is now known as dimtruck22:54
*** OmarB has joined #openstack-meeting-322:57
*** emagana has joined #openstack-meeting-323:00
*** Sukhdev has quit IRC23:01
*** OmarB has quit IRC23:01
*** doug-fish has joined #openstack-meeting-323:02
*** emagana has quit IRC23:02
*** emagana has joined #openstack-meeting-323:02
*** mickeys has joined #openstack-meeting-323:03
*** dimtruck is now known as zz_dimtruck23:05
*** zz_dimtruck is now known as dimtruck23:05
*** ddieterly has quit IRC23:06
*** markvoelker has quit IRC23:06
*** piet has quit IRC23:07
*** kenji-i has joined #openstack-meeting-323:12
*** mbound has quit IRC23:14
*** dimtruck is now known as zz_dimtruck23:14
*** sarob has quit IRC23:32
*** zz_dimtruck is now known as dimtruck23:33
*** emagana has quit IRC23:34
*** toddjohn_ has joined #openstack-meeting-323:36
*** Sukhdev has joined #openstack-meeting-323:38
*** toddjohn_ has quit IRC23:41
*** emagana has joined #openstack-meeting-323:46
*** Swami has quit IRC23:47
*** emagana has quit IRC23:50
*** mickeys has quit IRC23:51
*** mickeys has joined #openstack-meeting-323:52
*** mickeys has quit IRC23:52
*** mickeys has joined #openstack-meeting-323:53
*** pvaneck has quit IRC23:54
*** revon has quit IRC23:59

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!