Monday, 2015-08-17

*** markvoelker has quit IRC00:02
*** sdake_ has joined #openstack-meeting-300:04
*** sdake has quit IRC00:07
*** sdake has joined #openstack-meeting-300:21
*** sdake_ has quit IRC00:23
*** salv-orlando has joined #openstack-meeting-300:25
*** stanzgy has joined #openstack-meeting-300:29
*** salv-orlando has quit IRC00:29
*** shwetaap has quit IRC00:34
*** baoli has joined #openstack-meeting-300:45
*** baoli has quit IRC00:50
*** shwetaap has joined #openstack-meeting-300:50
*** carl_baldwin has joined #openstack-meeting-300:59
*** mestery has joined #openstack-meeting-300:59
*** zhenguo has joined #openstack-meeting-301:23
*** yamahata has joined #openstack-meeting-301:27
*** baoli has joined #openstack-meeting-301:27
*** FallenPegasus has joined #openstack-meeting-301:27
*** baoli has quit IRC01:31
*** FallenPegasus has quit IRC01:32
*** mestery has quit IRC01:36
*** mestery has joined #openstack-meeting-301:36
*** salv-orlando has joined #openstack-meeting-301:37
*** mestery has quit IRC01:37
*** carl_baldwin has quit IRC01:37
*** salv-orlando has quit IRC01:42
*** salv-orlando has joined #openstack-meeting-301:45
*** yamahata has quit IRC01:47
*** salv-orlando has quit IRC01:49
*** zhenguo has quit IRC01:53
*** baoli has joined #openstack-meeting-301:57
*** markvoelker has joined #openstack-meeting-301:58
*** baoli has quit IRC02:02
*** markvoelker has quit IRC02:03
*** banix has quit IRC02:09
*** sankarshan_away is now known as sankarshan02:11
*** yamamoto has joined #openstack-meeting-302:27
*** markvoelker has joined #openstack-meeting-302:31
*** davidmichaelkarr has quit IRC02:57
*** stanzgy has quit IRC03:07
*** FallenPegasus has joined #openstack-meeting-303:16
*** FallenPegasus has quit IRC03:21
*** Piet has joined #openstack-meeting-303:23
*** shwetaap has quit IRC03:29
*** flwang1 has joined #openstack-meeting-303:49
*** flwang has quit IRC03:53
*** VW_ has joined #openstack-meeting-303:53
*** salv-orlando has joined #openstack-meeting-303:54
*** VW_ has quit IRC03:55
*** VW_ has joined #openstack-meeting-303:55
*** VW_ has quit IRC04:00
*** kumar has joined #openstack-meeting-304:00
*** banix has joined #openstack-meeting-304:04
*** stanzgy has joined #openstack-meeting-304:06
*** sahid has joined #openstack-meeting-304:06
*** salv-orlando has quit IRC04:06
*** sahid has quit IRC04:07
*** sahid has joined #openstack-meeting-304:07
*** sahid has quit IRC04:07
*** zz_natorious is now known as natorious04:10
*** openstack has joined #openstack-meeting-304:18
*** ChanServ sets mode: +o openstack04:18
*** yamamoto has quit IRC04:23
*** markvoelker has quit IRC04:31
*** yushiro has joined #openstack-meeting-304:42
*** natorious is now known as zz_natorious04:45
*** irenab has quit IRC04:48
*** baojg has joined #openstack-meeting-304:48
*** geoffarnoldX is now known as geoffarnold04:49
*** geoffarnold is now known as geoffarnoldX04:50
*** yamamoto has joined #openstack-meeting-304:51
*** bpokorny has quit IRC04:56
*** VW_ has joined #openstack-meeting-304:57
*** VW_ has quit IRC04:57
*** VW_ has joined #openstack-meeting-304:58
*** VW_ has quit IRC05:02
*** yushiro has quit IRC05:05
*** FallenPegasus has joined #openstack-meeting-305:05
*** sahid has joined #openstack-meeting-305:07
*** sahid has quit IRC05:09
*** FallenPegasus has quit IRC05:10
*** geoffarnoldX is now known as geoffarnold05:15
*** Poornima has joined #openstack-meeting-305:17
*** FallenPegasus has joined #openstack-meeting-305:20
*** masco has joined #openstack-meeting-305:20
*** ttx has joined #openstack-meeting-305:22
*** banix has quit IRC05:23
*** irenab has joined #openstack-meeting-305:26
*** nkrinner has joined #openstack-meeting-305:27
*** geoffarnold is now known as geoffarnoldX05:27
*** mrunge has joined #openstack-meeting-305:28
*** markvoelker has joined #openstack-meeting-305:32
*** coolsvap|away is now known as coolsvap05:32
*** geoffarnoldX has quit IRC05:32
*** markvoelker has quit IRC05:36
*** salv-orlando has joined #openstack-meeting-305:44
*** FallenPegasus has quit IRC05:45
*** peristeri has joined #openstack-meeting-305:48
*** alexpilotti has quit IRC05:50
*** salv-orlando has quit IRC05:51
*** coolsvap is now known as coolsvap|away05:55
*** kumar has quit IRC06:00
*** lsmola has joined #openstack-meeting-306:12
*** yamamoto has quit IRC06:16
*** Sukhdev has joined #openstack-meeting-306:17
*** yamamoto has joined #openstack-meeting-306:17
*** mickeys has joined #openstack-meeting-306:18
*** salv-orlando has joined #openstack-meeting-306:23
*** mickeys has quit IRC06:25
*** yamamoto has quit IRC06:34
*** yamamoto has joined #openstack-meeting-306:34
*** baojg has quit IRC06:39
*** sdake_ has joined #openstack-meeting-306:44
*** Sukhdev has quit IRC06:47
*** sdake has quit IRC06:47
*** zhenguo has joined #openstack-meeting-306:49
*** peristeri has quit IRC06:53
*** baojg has joined #openstack-meeting-307:03
-openstackstatus- NOTICE: Gerrit is currently under very high load and may be unresponsive. infra are looking into the issue.07:06
*** sdake_ has quit IRC07:08
*** jtomasek has joined #openstack-meeting-307:09
*** jschwarz has joined #openstack-meeting-307:16
*** peristeri has joined #openstack-meeting-307:17
*** zhenguo has quit IRC07:18
*** peristeri has quit IRC07:21
*** peristeri has joined #openstack-meeting-307:21
*** peristeri has quit IRC07:31
*** markvoelker has joined #openstack-meeting-307:33
*** FallenPegasus has joined #openstack-meeting-307:33
*** stanzgy has quit IRC07:34
*** peristeri has joined #openstack-meeting-307:34
*** stanzgy has joined #openstack-meeting-307:35
*** devvesa has joined #openstack-meeting-307:35
*** markvoelker has quit IRC07:37
*** FallenPegasus has quit IRC07:38
*** zhenguo has joined #openstack-meeting-307:39
*** numan has joined #openstack-meeting-307:43
*** stendulker has joined #openstack-meeting-307:55
*** vgridnev has joined #openstack-meeting-307:59
*** zz_ttrifonov is now known as ttrifonov08:03
*** zhenguo has quit IRC08:04
*** devvesa has quit IRC08:14
*** baojg has quit IRC08:23
*** zhenguo has joined #openstack-meeting-308:29
*** matrohon has joined #openstack-meeting-308:34
*** baojg has joined #openstack-meeting-308:39
*** obondarev has joined #openstack-meeting-308:44
*** ttx has quit IRC08:48
*** ttx has joined #openstack-meeting-308:48
*** ttrifonov is now known as zz_ttrifonov08:52
*** zz_ttrifonov is now known as ttrifonov08:53
*** aarefiev has quit IRC08:56
*** tfukushima has joined #openstack-meeting-308:58
*** aarefiev has joined #openstack-meeting-308:59
*** tfukushima has quit IRC09:02
*** tfukushima has joined #openstack-meeting-309:04
*** kbyrne has quit IRC09:12
*** FallenPegasus has joined #openstack-meeting-309:14
*** kbyrne has joined #openstack-meeting-309:17
*** FallenPegasus has quit IRC09:19
*** sankarshan is now known as sankarshan_away09:33
*** markvoelker has joined #openstack-meeting-309:33
*** markvoelker has quit IRC09:38
*** devvesa has joined #openstack-meeting-309:44
*** Guest47951 is now known as d0ugal09:49
*** d0ugal has quit IRC09:49
*** d0ugal has joined #openstack-meeting-309:49
*** tfukushima has quit IRC10:11
*** tfukushima has joined #openstack-meeting-310:12
*** dims has joined #openstack-meeting-310:17
*** pavel_bondar has quit IRC10:19
-openstackstatus- NOTICE: review.openstack.org (aka gerrit) is going down for an emergency restart10:21
*** ChanServ changes topic to "review.openstack.org (aka gerrit) is going down for an emergency restart"10:21
*** baojg has quit IRC10:24
*** ttrifonov is now known as zz_ttrifonov10:25
*** baojg has joined #openstack-meeting-310:25
*** baoli has joined #openstack-meeting-310:28
*** dims has quit IRC10:30
*** dims has joined #openstack-meeting-310:31
*** baoli has quit IRC10:33
*** dims_ has joined #openstack-meeting-310:36
*** yamamoto has quit IRC10:38
*** dims has quit IRC10:38
*** mwagner_lap has quit IRC10:42
*** stanzgy has quit IRC10:42
*** baojg has quit IRC10:48
*** stanzgy has joined #openstack-meeting-310:48
-openstackstatus- NOTICE: Gerrit restart has resolved the issue and systems are back up and functioning10:48
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"10:48
*** dims_ has quit IRC10:50
*** dims has joined #openstack-meeting-310:51
*** stanzgy has quit IRC10:53
*** dims has quit IRC10:59
*** dims has joined #openstack-meeting-311:00
*** FallenPegasus has joined #openstack-meeting-311:03
*** dims has quit IRC11:06
*** qwebirc45728 has joined #openstack-meeting-311:06
*** achippa_ has quit IRC11:07
*** achippa has quit IRC11:07
*** FallenPegasus has quit IRC11:07
*** achippa_ has joined #openstack-meeting-311:07
*** achippa has joined #openstack-meeting-311:07
*** dims has joined #openstack-meeting-311:08
*** qwebirc45728 has quit IRC11:10
*** tfukushima has quit IRC11:10
*** achippa_ has quit IRC11:12
*** achippa has quit IRC11:12
*** dims_ has joined #openstack-meeting-311:12
*** dims has quit IRC11:12
*** dims_ has quit IRC11:17
*** stendulker has quit IRC11:20
*** dims has joined #openstack-meeting-311:22
*** kzaitsev1ws has joined #openstack-meeting-311:26
*** kzaitsev1ws has quit IRC11:26
*** kzaitsev_mb has joined #openstack-meeting-311:27
*** dims has quit IRC11:27
*** dims has joined #openstack-meeting-311:29
*** markvoelker has joined #openstack-meeting-311:34
*** dims_ has joined #openstack-meeting-311:34
*** dims has quit IRC11:35
*** markvoelker has quit IRC11:39
*** dims_ has quit IRC11:39
*** kzaitsev_ws has quit IRC11:40
*** dims has joined #openstack-meeting-311:40
*** kzaitsev_ws has joined #openstack-meeting-311:40
*** yamamoto has joined #openstack-meeting-311:43
*** woodster_ has joined #openstack-meeting-311:46
*** dims has quit IRC11:49
*** dims has joined #openstack-meeting-311:53
*** dims_ has joined #openstack-meeting-311:56
*** dims has quit IRC11:58
*** Poornima has quit IRC11:59
*** dims_ has quit IRC12:04
*** dims has joined #openstack-meeting-312:04
*** yamamoto has quit IRC12:06
*** dims_ has joined #openstack-meeting-312:08
*** dims has quit IRC12:10
*** tfukushima has joined #openstack-meeting-312:11
*** dims has joined #openstack-meeting-312:12
*** dims_ has quit IRC12:14
*** tfukushima has quit IRC12:16
*** dims_ has joined #openstack-meeting-312:18
*** dims has quit IRC12:18
*** dims has joined #openstack-meeting-312:19
*** dims_ has quit IRC12:23
*** dims_ has joined #openstack-meeting-312:26
*** dims has quit IRC12:26
*** tellesnobrega_af has quit IRC12:28
*** dims has joined #openstack-meeting-312:30
*** tellesnobrega has joined #openstack-meeting-312:30
*** dims_ has quit IRC12:31
*** dims has quit IRC12:35
*** dims has joined #openstack-meeting-312:35
*** kzaitsev_mb has quit IRC12:37
*** dims_ has joined #openstack-meeting-312:38
*** kzaitsev_mb has joined #openstack-meeting-312:39
*** dims has quit IRC12:40
*** VW_ has joined #openstack-meeting-312:40
*** baoli has joined #openstack-meeting-312:44
*** kzaitsev_mb has quit IRC12:44
*** ekarlso has quit IRC12:44
*** ekarlso has joined #openstack-meeting-312:44
*** dims has joined #openstack-meeting-312:45
*** dims_ has quit IRC12:45
*** VW_ has quit IRC12:47
*** VW_ has joined #openstack-meeting-312:48
*** baoli has quit IRC12:48
*** FallenPegasus has joined #openstack-meeting-312:52
*** pavel_bondar has joined #openstack-meeting-312:53
*** neelashah has joined #openstack-meeting-312:54
*** dims has quit IRC12:55
*** tfukushima has joined #openstack-meeting-312:56
*** FallenPegasus has quit IRC12:56
*** dims has joined #openstack-meeting-312:58
*** sdake has joined #openstack-meeting-313:00
*** geoffarnold has joined #openstack-meeting-313:01
*** lifeless has quit IRC13:05
*** vdrok_ has joined #openstack-meeting-313:05
*** dims has quit IRC13:06
*** yamamoto has joined #openstack-meeting-313:07
*** jckasper has quit IRC13:09
*** dims has joined #openstack-meeting-313:09
*** kzaitsev_mb has joined #openstack-meeting-313:11
*** yamamoto has quit IRC13:11
*** mrmartin has joined #openstack-meeting-313:12
*** davidmichaelkarr has joined #openstack-meeting-313:12
*** yamamoto has joined #openstack-meeting-313:12
*** dims has quit IRC13:14
*** dims has joined #openstack-meeting-313:14
*** sdake_ has joined #openstack-meeting-313:15
*** sdake has quit IRC13:19
*** sdake_ has quit IRC13:19
*** sankarshan_away is now known as sankarshan13:19
*** dims has quit IRC13:21
*** geoffarnold has quit IRC13:21
*** carl_baldwin has joined #openstack-meeting-313:22
*** leakypipes is now known as jaypipes13:25
*** beagles has quit IRC13:26
*** singlethink has joined #openstack-meeting-313:27
*** dims has joined #openstack-meeting-313:27
*** lifeless has joined #openstack-meeting-313:28
*** absubram has quit IRC13:29
*** julim has joined #openstack-meeting-313:31
*** cbouch has joined #openstack-meeting-313:32
*** markvoelker has joined #openstack-meeting-313:35
*** jpomeroy has joined #openstack-meeting-313:36
*** nate_gone has quit IRC13:36
*** mfranc213 has quit IRC13:36
*** vichoward has quit IRC13:36
*** dims has quit IRC13:36
*** krtaylor has quit IRC13:36
*** markvoelker has quit IRC13:39
*** banix has joined #openstack-meeting-313:41
*** FallenPegasus has joined #openstack-meeting-313:41
*** shwetaap has joined #openstack-meeting-313:41
*** dims has joined #openstack-meeting-313:42
*** baoli has joined #openstack-meeting-313:45
*** FallenPegasus has quit IRC13:45
*** mwagner_lap has joined #openstack-meeting-313:46
*** beagles has joined #openstack-meeting-313:46
*** beagles is now known as Guest7271413:47
*** dims has quit IRC13:48
*** masco has quit IRC13:48
*** sdake has joined #openstack-meeting-313:49
*** shwetaap has quit IRC13:49
*** krtaylor has joined #openstack-meeting-313:49
*** shwetaap has joined #openstack-meeting-313:50
*** baoli has quit IRC13:50
*** Guest72714 has quit IRC13:50
*** dshakhray has joined #openstack-meeting-313:52
*** dims has joined #openstack-meeting-313:54
*** mfranc213 has joined #openstack-meeting-313:56
*** vichoward has joined #openstack-meeting-313:57
*** singleth_ has joined #openstack-meeting-313:58
*** dims has quit IRC13:59
*** cbouch has quit IRC14:00
*** achippa has joined #openstack-meeting-314:01
*** achippa_ has joined #openstack-meeting-314:01
*** singlethink has quit IRC14:01
*** bauwser is now known as bauzas14:03
*** dims has joined #openstack-meeting-314:04
*** achippa_ has quit IRC14:05
*** achippa has quit IRC14:05
*** jckasper has joined #openstack-meeting-314:06
*** lblanchard has joined #openstack-meeting-314:08
*** yamamoto has quit IRC14:09
*** dshakhray has quit IRC14:09
*** cbouch has joined #openstack-meeting-314:10
*** sdake has quit IRC14:10
*** dims has quit IRC14:11
*** wojdev has joined #openstack-meeting-314:11
*** sigmavirus24_awa is now known as sigmavirus2414:15
*** dims has joined #openstack-meeting-314:16
*** irenab has quit IRC14:17
*** sdake has joined #openstack-meeting-314:17
*** dims has quit IRC14:22
*** cbouch has quit IRC14:27
*** pballand has joined #openstack-meeting-314:34
*** numan has quit IRC14:37
*** cbouch has joined #openstack-meeting-314:37
*** achippa has joined #openstack-meeting-314:37
*** achippa_ has joined #openstack-meeting-314:37
*** yamamoto has joined #openstack-meeting-314:39
*** peristeri has quit IRC14:40
*** baojg has joined #openstack-meeting-314:43
*** wojdev has quit IRC14:43
*** alexpilotti_ has joined #openstack-meeting-314:47
*** njohnston has joined #openstack-meeting-314:48
*** achippa has quit IRC14:48
*** achippa_ has quit IRC14:48
*** dims has joined #openstack-meeting-314:48
*** achippa_ has joined #openstack-meeting-314:49
*** achippa has joined #openstack-meeting-314:49
*** markvoelker has joined #openstack-meeting-314:51
*** nkrinner has quit IRC14:53
*** achippa_ has quit IRC14:53
*** achippa has quit IRC14:53
*** irenab has joined #openstack-meeting-314:53
*** yamamoto has quit IRC14:54
*** wojdev has joined #openstack-meeting-314:54
*** bpokorny has joined #openstack-meeting-314:54
*** markvoelker has quit IRC14:55
*** bpokorny has quit IRC14:59
*** smccully has quit IRC14:59
*** smccully has joined #openstack-meeting-315:02
*** krtaylor has quit IRC15:04
*** zz_natorious is now known as natorious15:06
*** carl_baldwin has quit IRC15:08
*** baojg has quit IRC15:09
*** yamahata has joined #openstack-meeting-315:11
*** yamamoto has joined #openstack-meeting-315:13
*** markvoelker has joined #openstack-meeting-315:15
*** krtaylor has joined #openstack-meeting-315:16
*** sbalukoff has quit IRC15:17
*** bpokorny has joined #openstack-meeting-315:18
*** pavel_bondar has quit IRC15:18
*** armax has joined #openstack-meeting-315:20
*** achippa_ has joined #openstack-meeting-315:22
*** achippa has joined #openstack-meeting-315:22
*** e0ne has joined #openstack-meeting-315:27
*** etoews has joined #openstack-meeting-315:32
*** alexpilotti_ is now known as alexpilotti15:35
*** zz_ttrifonov is now known as ttrifonov15:39
*** Sukhdev has joined #openstack-meeting-315:40
*** sahid has joined #openstack-meeting-315:41
*** geoffarnold has joined #openstack-meeting-315:42
*** geoffarnold is now known as geoffarnoldX15:42
*** achippa has quit IRC15:43
*** achippa_ has quit IRC15:43
*** achippa_ has joined #openstack-meeting-315:44
*** achippa has joined #openstack-meeting-315:44
*** lazy_prince has joined #openstack-meeting-315:45
*** geoffarnoldX is now known as geoffarnold15:47
*** achippa_ has quit IRC15:49
*** achippa has quit IRC15:49
*** mestery has joined #openstack-meeting-315:53
*** vgridnev has quit IRC15:54
*** carl_baldwin has joined #openstack-meeting-315:54
*** ttrifonov is now known as zz_ttrifonov15:58
*** mrunge has quit IRC16:02
*** dosaboy_ has joined #openstack-meeting-316:04
*** dosaboy_ has quit IRC16:04
*** dosaboy has quit IRC16:04
*** armax has quit IRC16:05
*** lazy_prince has quit IRC16:06
*** matrohon has quit IRC16:07
*** dosaboy has joined #openstack-meeting-316:09
*** e0ne has quit IRC16:09
*** mrunge has joined #openstack-meeting-316:11
*** david-ly_ is now known as david-lyle16:15
*** claudiub has joined #openstack-meeting-316:17
*** lazy_prince has joined #openstack-meeting-316:18
*** yamamoto has quit IRC16:20
*** Swami has joined #openstack-meeting-316:21
*** stevemar has joined #openstack-meeting-316:24
*** mickeys has joined #openstack-meeting-316:26
*** achippa_ has joined #openstack-meeting-316:30
*** achippa has joined #openstack-meeting-316:30
*** yamahata has quit IRC16:35
*** tqtran-afk has joined #openstack-meeting-316:38
*** tqtran-afk is now known as tqtran16:38
*** tfukushima has quit IRC16:40
*** wojdev has quit IRC16:41
*** tfukushima has joined #openstack-meeting-316:41
*** vgridnev has joined #openstack-meeting-316:44
*** yamamoto has joined #openstack-meeting-316:45
*** devvesa has quit IRC16:46
*** puranamr has joined #openstack-meeting-316:47
*** thiagop has joined #openstack-meeting-316:48
*** yuriyz has joined #openstack-meeting-316:50
*** betherly has joined #openstack-meeting-316:51
*** rameshg87 has joined #openstack-meeting-316:52
*** bharath has joined #openstack-meeting-316:52
*** achippa has quit IRC16:52
*** achippa_ has quit IRC16:52
*** achippa_ has joined #openstack-meeting-316:53
*** achippa has joined #openstack-meeting-316:53
*** natorious is now known as zz_natorious16:54
*** aarefiev_home has joined #openstack-meeting-316:54
*** lucasagomes has joined #openstack-meeting-316:54
*** jschwarz has quit IRC16:55
*** njohnston is now known as nate_gone16:55
*** aarefiev_home is now known as aarefiev2216:55
*** smccully has quit IRC16:56
*** achippa_ has quit IRC16:56
*** achippa has quit IRC16:56
*** smccully has joined #openstack-meeting-316:56
*** achippa has joined #openstack-meeting-316:56
*** achippa_ has joined #openstack-meeting-316:56
*** lazy_prince has quit IRC16:57
*** yamahata has joined #openstack-meeting-316:58
*** rloo has joined #openstack-meeting-316:58
*** saripurigopi has joined #openstack-meeting-316:58
*** liliars_ has joined #openstack-meeting-316:59
* jroll watches the clock16:59
devanandagood morning / afternoon / evening, all16:59
devananda#startmeeting ironic17:00
openstackMeeting started Mon Aug 17 17:00:00 2015 UTC and is due to finish in 60 minutes.  The chair is devananda. 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
*** trown has joined #openstack-meeting-317:00
devananda#chair NobodyCam17:00
openstackCurrent chairs: NobodyCam devananda17:00
jroll\o17:00
thiagopmorning all17:00
betherlyo/ hi!17:00
rameshg87o/17:00
lucasagomeso/17:00
vdrok_morning17:00
yuriyzo/17:00
devanandaas usual, the agenda is in the wiki17:00
mrdao/17:00
trowno/17:00
devananda#link https://wiki.openstack.org/wiki/Meetings/Ironic17:00
saripurigopiO/17:00
devanandaI'll try to keep each topic brief today so we can have plenty of time for open discussion / follow up from the midcycle17:00
rloohi17:00
jlvillalo/17:00
TheJuliao/17:00
NobodyCamo/17:01
mariojv\o17:01
JoshNango/17:01
*** alex_xu has quit IRC17:01
devanandaskipping announcements section since it's empty17:01
NobodyCam:)17:01
devananda#topic subteam status reports17:01
*** openstack changes topic to "subteam status reports (Meeting topic: ironic)"17:01
*** afaranha has joined #openstack-meeting-317:01
devananda#link https://etherpad.openstack.org/p/IronicWhiteBoard17:02
devanandaif you haven't already updated your subteam status, tracked at that ^ link, please do so now17:02
devanandathere was a lot of work / progress on the neutron/ironic integration last week17:03
devanandamany thanks to jroll, Sukhdev, and others for that17:03
jroll:)17:03
jrollit's coming along nicely17:03
NobodyCamand thank you to all who attened the mid-cycle17:03
*** smccully has quit IRC17:03
rloohmm, dtantsur is on PTO. Are we in a hurry to get the ironic-lib stuff done?17:03
*** alex_xu has joined #openstack-meeting-317:03
devanandarloo: yea, we kinda are. it's been blocking other things for a while17:03
*** mrunge has quit IRC17:04
rameshg87rloo: and we have a soft freeze on those files in ironic now17:04
jrollhe's back wednesday17:04
rloodevananda: looks like there are two patches for ironic-lib dvsm testing.17:04
devanandaalso, jroll and I need to catch up with dhellmann soon to sort out releases17:04
jrolldevananda: it's on my calendar to hit him up tomorrow17:04
devanandawe tried last week but there's things in pip/pbr I dont understand17:04
lucasagomesyeah, I think it's most good for a release right?17:05
devanandarloo: thanks17:05
lucasagomesin a code POV17:05
devanandalucasagomes: yea17:05
*** Saripurigopi_ has joined #openstack-meeting-317:05
devanandapshige_, jlvillal: any updates on docs?17:05
rloois anyone familiar with tempest/devstack stuff, to continue Dmitry's patches? (Or we wait til Wed?)17:05
jrolllucasagomes: there's two patches right now to get dsvm running17:06
rameshg87and sfaizan has some patches (ready) for switching ironic to use ironic-lib when it's released17:06
*** zhenguo has quit IRC17:06
* lucasagomes checks the review list17:06
*** yamamoto has quit IRC17:06
*** zhenguo has joined #openstack-meeting-317:06
jrolllucasagomes: https://review.openstack.org/#/c/212491 https://review.openstack.org/#/c/212495/17:06
devanandajroll: release ironic first, then switch to using ironic-lib, ya?17:06
jrolldevananda: yes pls17:06
jlvillaldevananda: Not from me. Was I supposed to do something on docs???17:06
lucasagomesjroll, thanks17:06
*** sambetts has joined #openstack-meeting-317:06
lucasagomesdevananda, ++17:06
*** zhenguo has quit IRC17:07
devanandarameshg87: do you have links to those patches? pls put on the etherpad17:07
*** saripurigopi has quit IRC17:07
rameshg87devananda: ack17:07
* jlvillal trying to remember if he had a TODO item that he forgot about.17:07
jrolldevananda: I expect by EOD tomorrow we'll be ready to release unless we see a major bug we want to fix first17:07
devanandajlvillal: oh, nope. I imagined it :)17:07
* jlvillal Whew!17:07
*** smccully has joined #openstack-meeting-317:07
rloojlvillal: I thought you were going to reorganize our docs?17:08
rloojlvillal: just kidding17:08
mrdalol17:08
* jlvillal recovers from heart-attack.... :P17:08
NobodyCamhehe17:08
devanandamrda: !! you're here :)17:08
devanandajetlag, eh?17:08
mrdadevananda: I'm in SAT this week17:08
devanandaahh17:08
devanandawell, welcome :)17:08
devanandaanything to add to the nova/ironic section of the status report?17:09
mrdathanks - it'll be my last team meeting for a while due to TZ17:09
lucasagomesmrda, :-(17:09
mrdadevananda: Not really, we have some things to do, and jlvillal and I will update later today hopefully17:09
devanandak k17:09
*** mickeyspiegel has joined #openstack-meeting-317:09
mrdadevananda: but I haven't had time to get anything done so far17:09
rloomrda & jlvillal: please remind us if there are nova patches that ought to be reviewed that we want in before liberty deadline whenever that is17:10
*** jpomeroy has quit IRC17:10
mrdarloo: shall do17:10
*** mickeys has quit IRC17:10
rloothx mrda17:10
jlvillaldevananda: On Nova, we have mainly been catching back up as both mrda and I were out on vacation.  There are two patches in the review queue.17:10
jrollrloo: nova is full-on feature freezed for L, bug fixes can land any time AIUI17:11
jlvillalBut if people have patches to go into Nova, please ping mrda or jlvillal (me).  So we can add them to the review queue.17:11
mrdayes please17:11
jlvillalWe usually look for Nova bugs that are tagged as Ironic.  And then look for patches off of those bugs.17:11
devanandagood stuff, everyone - thanks for the updates!17:12
devanandaanything else before we move on? (giving it another minute)17:12
*** achippa has quit IRC17:12
*** achippa_ has quit IRC17:12
rlooso we have OneView in the etherpad, but I don't htink the spec has been approved yet?17:12
*** achippa has joined #openstack-meeting-317:13
*** achippa_ has joined #openstack-meeting-317:13
lucasagomesyeah not yet17:13
lucasagomes#link https://review.openstack.org/#/c/187762/17:13
devanandanope, not yet17:13
sambettshg87 :)17:13
thiagopIn fact, we're waiting for some reviews17:13
thiagopany feedback is appreciated17:13
* lucasagomes adds to his todo for tomorrow17:13
devanandaoh -- actually, one more thing to add to the update list17:13
*** armax has joined #openstack-meeting-317:14
devanandajroll and I (and others) sat down and looked at both the approved and unapproved specs17:14
*** salv-orl_ has joined #openstack-meeting-317:14
devanandacompared to list of things we set out at beginning of the cycle17:14
devanandaand did a major update to the priorities spreadsheet17:14
devananda#link https://docs.google.com/spreadsheets/d/1Hxyfy60hN_Fit0b-plsPzK6yW3ePQC5IfwuzJwltlbo17:14
mrdathanks devananda for the link17:14
devanandasince LP doesn't give us any good way to group bp's by topic, we did that in google ...17:14
lucasagomesoh nice one17:14
* devananda waits for the mythical future when openstack will have a good tool for this17:15
NobodyCamcurrent priorities tab!17:15
rloodevananda: awesome (for updating priorities). Not good wrt all the stuff to do, sigh.17:15
*** carl_baldwin has quit IRC17:15
*** mestery has quit IRC17:15
lucasagomesloads of changes to the driver interfaces O.O17:15
devanandarloo: it's more of a "here are all the things people seem to want to do" + "what major themes emerge" + "what's really important to everyone"17:16
rloodevananda: wrt state machine. should we add some item number about microversioning/client default versions blah blah. or did we decide how to handle enroll?17:16
devanandarloo: let's not discuss that now17:16
*** salv-orlando has quit IRC17:16
thiagopOne more thing about oneview, we're working to put a 3rd party CI to work when the code is merged, even if it runs just periodically due to hardware restrictions17:16
NobodyCamthiagop: awesome!17:17
thiagop30% done17:17
*** achippa_ has quit IRC17:17
*** achippa has quit IRC17:17
devanandaok, going to timebox this lest we run out of time for other things17:17
devanandathanks everyone for the updates!17:17
lucasagomesthiagop, ++ awesome17:17
rloodevananda: don't want to discuss, just think it is high priority and not sure it is captured in the doc17:17
jlvillalthiagop: +1 on awesome :)17:17
devanandarloo: fair point17:17
rloodevananda: i don't think we can release liberty w/o resolving that17:17
devananda#topic scripts that do not fit into our current project repositories17:18
*** openstack changes topic to "scripts that do not fit into our current project repositories (Meeting topic: ironic)"17:18
devanandaNobodyCam: that's you17:18
NobodyCamoh thats me17:18
NobodyCam:)17:18
NobodyCamwe've have a couple of folks purpose utility type scripts, many are driver or vendor specific and17:18
NobodyCamdo not have a good location in the ironic tree. It was suggested that a solution to this would be17:18
NobodyCamto have these scripts in their own repos, and a wiki type page could be created with links pointing17:18
NobodyCamto these repos. I kinda like this as it allows the script creators to maintain them with out having to17:18
NobodyCambogged down by the entire Ironic review process, but they could still be "linked" to the ironic17:18
NobodyCamproject via the wiki page.17:18
NobodyCam(sorry for large paste)17:18
jrollisn't that exactly the method we decided to move forward with in vancouver?17:19
jlvillalI like the idea of separate repo(s) outside of Ironic.17:19
NobodyCamwould like to hear what other folks think about this17:19
devanandajroll: maybe? but we haven't implemented it yet afaik, so it came back up at the midcycle17:19
lucasagomesyeah seems fine to have a separated repo17:19
sambettsI think we decided on a single utils repo in vancouver17:19
lucasagomesI mean "many are drivers", drivers could easily live in our tree17:19
*** BadCub has joined #openstack-meeting-317:20
jrolldevananda: what is there to implement about "make your own repo" and "put a link on our wiki page"17:20
rloo+1 for separate repos. I think in Vancouver there were 2 solutions and no decision.17:20
devanandasambetts: I recall a discussion around having a single "other utils" repo, but there are problems with that17:20
TheJuliaIf I remember correctly, the decision in vancouver was to come back to it, that there was no consensus then17:20
* BadCub is again fashionably late17:20
jrollheh17:20
devanandalike, who approves changes in it? what language is it in? how is it tested?17:20
gabriel-bezerrarloo: +117:20
mrdawould they be curated in anyway?  Or just freeform?  i.e. would there be an owner for each repo as to ensure some sort of consistency?17:20
jlvillallucasagomes: Problem with drivers in our tree is that difficult for people to review hardware/vendor specific code17:20
jrollI'm not seeing this in the etherpad :(17:20
devanandajroll: the only thing for us to do: 1) agree on it 2) document the agreement in a wiki page17:20
jrollright17:20
devanandamrda: no curation17:21
*** sdake_ has joined #openstack-meeting-317:21
lucasagomesjlvillal, well we do it already right?17:21
devanandathe wiki would indicate who, from that vendor (presumably) is the maintainer17:21
sambettsI think we should use the neutron vendor decomp as a case study17:21
mrdas ironic-<vendor>-caveat-emptor as a repo name?17:21
jlvillallucasagomes: Yeah, but is that a good thing or not?  I'm not sure.17:21
lucasagomesjlvillal, many of the vendor stuff can live in a separated library17:21
mrdas/s/so/17:21
NobodyCamin many cases not everyone will be able to test them asfolks may not have the HW to test17:21
devanandaso the communit has a point of contact for issues in, essentially, third-party tools17:21
lucasagomeslike proliantutils17:21
jrolllet's be clear here: this isn't driver code. this is utility scripts etc.17:21
rloowe aren't discussing the home of drivers. just other "stuff", right?17:21
jrollright?17:21
devanandamuch like several drivers have already created their own repos on stackforge or github17:21
TheJuliajroll: correct17:21
jlvillalSorry, for off topic then.17:21
devanandarloo, jroll: correct17:21
jrollpython enroll_hardware_from_acme_cmdb.py etc.17:22
trownhow would this work with "big tent" ie. no more stackforge17:22
devanandaexactly17:22
devanandatrown: so, frankly, I don't like the "no more stackforge" approach17:22
jrollas I said in vancouver, I think this should be completely outside of the ironic program, with the exception of links on our wiki.17:22
devanandajroll: +10017:23
jrollI don't care if your repo is in the openstack ecosystem or not17:23
thiagoppeople that wants can use the 'openstack/' namespace instead of stackforge17:23
jrollmake a repo. put it somewhere.17:23
sambettstrown: you can have independantly released projects under the ironic statium17:23
trowndevananda: me neither...but it seems that is the direction17:23
thiagopit's just not a "official" project17:23
lucasagomesI'm good with separated repos17:23
devanandajroll: so if people put these tools in openstack/ then they will naturally propose that they be listed in openstack/governance/projects.yaml17:23
rameshg87+1 for separate repos and documenting on wiki17:23
mrdajroll: I'm fine with that, but is there an owner? I'm not sure it should be a free for all17:23
devanandaand included in the ironic project17:23
lucasagomespeople can manage their own tools and edit the Ironic wiki to talk about it, no problem17:23
gabriel-bezerrajroll: +117:23
jrolldevananda: right, they should not be included in the ironic tree there.17:24
devanandajroll: right17:24
jlvillalSo is it separate repos under openstack/ or just some repo on github.com?17:24
NobodyCamjroll: devananda: yep that was my thinking too17:24
mrdaI think everyone agrees with not in the ironic tree17:24
*** sdake has quit IRC17:24
sambettsI don't17:24
jrollmrda: I think a free for all is fine17:24
jrollok, here's an example17:24
jrollhttps://github.com/rackerlabs/onmetal-scripts17:24
trown"just some repo on github.com" is problematic as there is no access to the wealth of infra resources then17:25
jrollshould that be in the ironic program? should ironic maintainers be responsible for that repo?17:25
thiagopso, to have a wiki is a consensus?17:25
rlooisn't 'ironic tree' == git repo for 'ironic' code. vs 'ironic program' which includes ipa, inspector, bifrost...17:25
thiagopthe problem is just were to put the code?17:25
NobodyCamexample: https://review.openstack.org/#/c/158577/17:25
sambettsjroll: being under the ironic stadium doesn't mean that the ironic core team is invloved with it at all17:25
devanandathiagop: the problem is "who is responsible fo rmaintaining the code"17:25
jrollrloo: right, sorry17:25
*** mestery has joined #openstack-meeting-317:26
jrollsambetts: it implies that the ironic team is responsible for it17:26
* mrda just doesn't want to allow nefarious updates17:26
devanandasambetts: did we switch from umbrellas to stadiums? :)17:26
jrollsambetts: people will come to the ironic team when they have problems with it17:26
jlvillalHow about allow both repos on github.com and under openstack/  Either is acceptable?17:26
jrolljlvillal++ (just not in the ironic program)17:26
jlvillalJust link to them from the wiki.17:26
jroll+++++17:26
rlooi personally don't care where they put their stuff as long as i'm (ironic program) is not responsible for it17:26
NobodyCam++17:26
TheJulia++17:26
mrda+117:26
devanandajlvillal: that's what NobodyCam proposed at the opening of this topic :)17:26
devanandarloo: exactly17:26
jroll"if you make a repo, we'll link to it"17:26
trownjroll: how does one create a openstack/ repo for an ironic based project that is not under the ironic program?17:27
NobodyCamyep17:27
*** Saripurigopi_ has quit IRC17:27
rloojroll: or 'if you make a repo, you can link to it'17:27
sambettsOur networking-cisco repo lives in the neutron statium but is completely independant, its only there to state its relevance to the project17:27
devanandatrown: one does not17:27
jrolltrown: I have no idea, they should ask infra17:27
mrdatrown: ask infra17:27
thiagoptrown: did that this week17:27
lucasagomesI think it's fair to have separated. Once the project is mature enough it can even be proposed to be part of the ironic umbrella17:27
lucasagomesas others have done already17:27
thiagopjust don't add it to the governance stuff17:27
lucasagomesbut it needs time17:27
TheJuliaHonestly, this may not be a project, it may just be "I have some helper scripts, the community could use them"17:28
devanandawait - thiagop - you created an openstack/* project related to ironic, but that is not intended to be part of the ironic project?17:28
jrollthiagop: oh, that's a good point. infra/tc/whatever doesn't have a problem with that?17:28
trownthiagop: can you point me to the project-config review for that?17:28
thiagopdevananda: yep17:28
gabriel-bezerradevananda: it is openstack/python-oneviewclient17:28
thiagop#link https://review.openstack.org/#/c/211301/17:29
*** armax has quit IRC17:29
devanandaso TheJulia brings us back to the topic at hand -- this isn't about pyhton libraries or UI frameworks or things like that -- it originally came up because the iLO team has some tooling they use, with iLO, to do mass discovery17:29
thiagoptrown: ^17:29
devanandaI dont know if it's even written in python17:29
trownthiagop, thanks17:29
NobodyCam#link https://review.openstack.org/#/c/15857717:29
*** ivar-lazzaro has joined #openstack-meeting-317:29
devanandathiagop, gabriel-bezerra so that clearly should be part of hte ironic project in my opinion (once the spec is approved to implement that driver)17:29
*** ivar-lazzaro has quit IRC17:30
TheJuliaWhich has occured again as other groups have indicated that they have something that is a helper script to do x or y specific task, but don't know what to do to help users who may find the items useful17:30
thiagopdevananda: I know, but once the community hasn't yet agreed on that, I proposed it that way17:30
*** kevinbenton has quit IRC17:30
sambettsdevananda: doesn't that go back to the goverances "Am I OpenStack?" thing? if it can live in openstack/* or not then17:30
TheJuliais an ansible module openstack?17:30
thiagopand it can be a way out to the helper scripts  too17:31
TheJulia(as an example)17:31
devanandaTheJulia: it can be. see OSAD :)17:31
rloodevananda: off topic now, but it would be good to discuss which openstack/python-Xclients will fall under ironic program in the future. i'm concerned that for every vendor, we'll end up with such a client.17:31
*** lsmola has quit IRC17:31
TheJuliadevananda: I knew you were going to respond with that :)17:31
*** ivar-lazzaro has joined #openstack-meeting-317:31
mrdaosad: \o/17:31
*** sdake has joined #openstack-meeting-317:31
devanandarloo: I was just checking projects.yaml and I agree -- it's not currently clear17:31
devanandaproliantutils isn't listed there, but I think it should be17:31
jrollso getting back on topic17:31
*** kevinbenton has joined #openstack-meeting-317:32
jrollthere are clearly things we don't want in the ironic umbrella17:32
rloootoh, if OpenStack wants to rule the world, we can put all opensource code used by openstack under our tent17:32
* devananda sets a timer for 5 more minutes on this topic17:32
jrolland an openstack repo can be made without putting under ironic umbrella17:32
NobodyCamjroll: ++17:32
jrollso I think we should advise vendors to make a repo on openstack or github, doesn't matter17:32
jrolland link to it from a wiki page17:32
thiagopjroll: +117:32
BadCubjroll: +117:33
rameshg87jroll: +117:33
jrollwho wants to write those docs? :)17:33
jroll(or wiki page)17:33
rloojroll: write what docs?17:33
trownjroll: ++, the ability to make a repo under openstack namespace but not under **any** umbrella is news to me17:33
devanandajroll: I think the way things are going, if it's in openstack/* namespace, the TC will want it to be associated with _some_ project team17:33
lucasagomesseems fair... it's basically what was said before "create a repo and link on the wiki" "note you can create a repo under openstack/ if u wish"17:33
devanandatrown: yea, news to me too17:33
rloojroll: the wiki page part is easy.17:33
jrollrloo: the "here's what you should do for tools repos"17:33
jrollrloo: it could be a paragraph on the wiki, rather than docs or whatever17:33
rloojroll: so two wikis: one for instructions on how, one that lists the 3rdparty/whatever stuff.17:34
*** mestery has quit IRC17:34
thiagopdevananda trown I think it was after the depreciation of stackforge namespace17:34
rloojroll: did we agree/vote on this?17:34
BadCubdevananda: if we have folks setup a repo, can they not "associate" to Ironic if the "thing" is meant to be used for Ironic?17:34
jlvillalOr one Wiki with both17:34
jrolldevananda: maybe we should get that clarified, then, but today it's possible17:34
rloojroll: (not the wiki part, the process)17:34
jrollrloo: I made a statement, I'm not seeing disagreement17:34
jroll¯\_(ツ)_/¯17:34
NobodyCamI would also think many vendor type folk already a github repo like the rackerlabs one17:34
sambettsBadCub: +117:34
rloojroll: yeah, but we're in a meeting. don't we have to vote?17:34
*** sdake_ has quit IRC17:35
devanandaBadCub: the question at hand is how to do that association so a) users can find it, but b) the ironic core team isn't expected to maintain vendor tools (which may not even be in python)17:35
devanandajroll: ++ to getting that clarified17:35
NobodyCamand require spicific HW to test17:35
jrollrloo: sure, whatever, voting is fine17:35
jlvillalShould it be in the docs too?  Or the links are only in the Wiki?17:35
thiagopNobodyCam: right17:35
BadCubThose are very good points to get clarified17:35
* devananda doesn't feel the need to vote17:36
lucasagomesjlvillal, I think only wiki is fine17:36
jroll+1 for wiki.17:36
devanandaanyone volunteering to writing this in the wiki?17:36
rameshg87I will17:36
* NobodyCam can take a stab at it17:36
jrollwoo, thanks rameshg8717:36
devanandarameshg87: ty :)17:36
NobodyCamor rameshg8717:36
BadCubrameshg87: +1 :)17:36
thiagoprameshg87: o/\o17:36
NobodyCam:)17:37
NobodyCamThank you all!17:37
* rameshg87 hasn't got this much cheer ever :)17:37
BadCublol17:37
devananda#action rameshg87 to wiki'fy the results of this discussion: vendors can create tool / utility repos without needing to put them under the "ironic" project umbrella, and should link from wiki page17:37
devanandathanks all!17:37
TheJuliathank you!17:37
devananda#topic patches adding copyright headers17:37
*** openstack changes topic to "patches adding copyright headers (Meeting topic: ironic)"17:37
lucasagomeshope this one to be fast...17:37
devanandaI don't see naohiro here, so I'll proxy17:37
jrollcan we just agree to email legal-discuss here17:38
lucasagomesso we have this patch here https://review.openstack.org/212973 adding some copyright lines to their code17:38
devananda#link https://review.openstack.org/21297317:38
lucasagomesIMHO I don't think it matters that much, but we don't have a consensus around it17:38
devanandaI googled a bit, but didn't find it -- but there have been several discussions in -infra about this before17:38
jrollnobody present right now is going to have a definitive answer as to if this is ok. I'm fairly certain those headers aren't enforcable anyway.17:38
devanandalucasagomes: infra does have a policy here17:38
lucasagomesdevananda, not infra, it's legal17:38
lucasagomesalso, AFAIR some projects have decided not to have any copyright lines17:39
devanandathere's a much bigger discussion around CLA / DCO / (C) headers -- some of which was wiki'd here: https://wiki.openstack.org/wiki/OpenStackAndItsCLA17:39
devanandabut then that got caught up in board and TC meetings for a long time, and still isn't resolved17:39
devanandalucasagomes: it's not about legal. the CLA asserts the copyright on submission17:39
NobodyCamat one time we were adding: # Copyright <year> OpenStack Foundation headers17:39
*** Sukhdev has quit IRC17:40
devanandaNobodyCam: you should never have added one of those -- sinc eyou were never, afaik, an employee of the openstaack foundation ....17:40
devanandanor should I ever have17:40
lucasagomesdevananda, right, yeah I know... but many of the code have copyright lines and we keep accepting it17:40
*** Sukhdev has joined #openstack-meeting-317:40
rlooIs the question whether we should allow those Copyright's? We already have code with them.17:40
devanandarloo: no - the question is whether we can allow them to be added after the fact17:40
devanandafujitsu submitted code w/o any (c) header, and it landed, and now they want to "correct" it17:41
lucasagomesyeah can we add it after they are already submitted?17:41
rloodevananda: OH. that is different. No, I don't think so.17:41
mrdaSome companies do demand it, rightly or wrongly, for newly created files.  I think we should allow that, but not allow updates.17:41
devananda#action devananda to follow up with infra and/or legal team on this17:41
BadCubis there a "chance" The foundation will require this copyright in the future, or do they even have the right to require it?17:41
jrollso as I understand it. those copyrights are meaningless. AFAIK we do it because we cargo cult the header.17:41
mrdaIt's all Apache licenced independent of copyright notices - but the copyright notice is a visual indication that it's not public domain code, that it is covered by an explicit licence17:41
jrolldevananda++17:41
devanandathe CLA imputes it on code submission, based on the attribution of the patch author17:41
lucasagomesjroll, ++ yeah they are meanless because we signed the CLA17:41
rloo(or is the definition of 'landed' -- when a release occurs)17:41
devanandaso as far as openstack foundation legal is concerned, they aren't needed.17:42
devanandabut some companies feel otherwise, thus we get them, and mostly don't care17:42
devanandarloo: no, commit accepted17:42
rloodevananda: ok, let's move on then. You've got your action item :)17:42
lucasagomes++17:42
devanandaanyway, time boxing at this point, but wanted everyone to be aware of the discussion and policy17:42
*** carl_baldwin has joined #openstack-meeting-317:42
jroll+1, let's move on17:42
devananda#topic driver name length limit17:42
*** openstack changes topic to "driver name length limit (Meeting topic: ironic)"17:42
lucasagomesanother fast one17:43
devanandathis one has no name on the agenda ...17:43
devananda#link https://review.openstack.org/#/c/209605/17:43
lucasagomesthere's a patch changing the length of the name from 15 to 2517:43
thiagopmine17:43
thiagopbut lucasagomes bringed that to us17:43
jrollis there any reason to continue to limit this artificially? if we proposed 255, what would be the objection?17:43
lucasagomeswhile I think it's fine, do we have any consensus whether 25 is enough for the driver's name ?17:43
lucasagomesimo we can make it longer and have no more problem's with it17:43
mrda25 might be too limited17:43
devanandajroll: the driver name is actually hte python entrypoint name17:44
rloojroll: +1. I see no reason to limit it to 2517:44
devanandais there a limit on python entrypoint names?17:44
jroll+1, let's make it so we never have to deal with this again17:44
thiagopbroght*17:44
jrolldevananda: good question, I doubt it but who knows17:44
jrollprobably 79 :)17:44
betherlyI think 25 is limited but equally think there should be a limit of some kind?17:44
devanandaI don't care about the db field length (as long as it's < 256)17:44
rloolet's limit it to python entrypoint names then!17:44
NobodyCammy only thought here is many folk nay not what to "node-create -d aReallyLongDriverNameGoesHere17:44
* jroll googles about entrypoints17:44
devanandaNobodyCam brings up a good point - usability is also a concern17:45
*** rhagarty__ has joined #openstack-meeting-317:45
mrda255 might be a better choice, just so we don't have to revisit17:45
devanandathis will be displayed in UI, typed on CLI, etc17:45
yuriyzimo reasonable value is 6417:45
rloodevananda: but the names have to be approved by the core-reviewers.17:45
devanandabut I'm fine with the DB no longer imposing an arbitrarily small limit17:45
NobodyCamyuriyz: more than in my option17:45
devanandaand if someone wants to use MyReallyLongdriverNameThatNoOneWillEverType -- well, they can17:45
lucasagomesright17:45
jrollsetuptools doesn't seem to document a max length for entry points17:45
BadCubWould it be sane an reasonable to set it to 100? I think it would be difficult for someone to come up with something longer, unless they are really, really creative17:45
jrollfwiw17:45
NobodyCam++17:46
devanandajroll: cool17:46
thiagopwe could add a recommendation to use short names17:46
betherly+117:46
mrda(assuming they can convince everyone in code review...)17:46
yuriyzok17:46
devanandaBadCub: 100 is even more arbitrary :)17:46
lucasagomesalright, so everyone agrees 25 is too small?17:46
*** rhagarty has quit IRC17:46
devanandalucasagomes: yes17:46
yuriyz+117:46
BadCub+117:46
mrdayup17:46
betherlyYup17:46
NobodyCamyup17:46
rameshg87+1 for 25517:46
jrolllet's just decide on a number now before we bikeshed all over gerrit17:46
devanandaI've heard two suggestions so far: 64 and 25517:46
jrollI like 25517:46
*** rhagarty_ has quit IRC17:46
thiagoplets do a vote?17:46
NobodyCamrameshg87: ya17:46
rloo+1 25517:46
lucasagomeswell 255 then17:47
mrda+1 for 25517:47
lucasagomesno hard limits17:47
*** rhagarty_ has joined #openstack-meeting-317:47
thiagop255 it is17:47
trown+1 for 25517:47
jlvillal+1 for 25517:47
yuriyzok 255 is good17:47
devanandathat's easy17:47
jrollwe can artificially limit in code if we want to make the limit smaller for usability17:47
BadCub+1 for 25517:47
gabriel-bezerraas unlimited as possible17:47
rloounless we find out there's something else that limits it17:47
devananda#agreed use 255 for the driver name field length in the db17:47
lucasagomesrloo, yeah17:47
devananda#undo17:47
openstackRemoving item from minutes: <ircmeeting.items.Agreed object at 0x9c577d0>17:47
betherly+1 jroll17:47
jrollwoo, done17:47
jrollNEXT17:47
lucasagomesthiagop, thanks for the patch :-)17:47
devananda#agreed use 255 for the driver name field length in the db, unless we find out that there is another limit (eg, python entrypoint length)17:47
devananda#topic open discussion17:48
*** openstack changes topic to "open discussion (Meeting topic: ironic)"17:48
thiagoplucasagomes: not at all, will to it later today17:48
lucasagomeswell I put yet another item there for the delete instances at any time in the deployment17:48
lucasagomesdevananda, while I think target_provision_state would be great, I don't see any clear way to actually implement it?17:48
* BadCub wants to thank everyone for making mid-cycle so awesome.17:48
NobodyCam++17:49
mrdaGreat job BadCub!17:49
betherly+117:49
lucasagomesand syntax way, I don't think the flag is all bad. Because the node will actually transit from the target_provision_state it's currently set to transit17:49
betherlyIt was awesome17:49
*** carl_baldwin has quit IRC17:49
betherlyAnd thanks to everyone for making me feel welcome!17:49
lucasagomesand then it will be deleted (and the target_* will mark it as deleted)17:49
BadCubthnx mrda :)17:49
TheJuliaBadCub: Thank you for setting things up17:50
mrdaBadCub: and thank you for putting up with the hills17:50
*** rhagarty__ has quit IRC17:50
BadCubIt was a pleasure! I am glad everyone had a good time. And we got to welcome betherly to the fold :)17:50
devanandalucasagomes: the flag is easy enough to implement inside of ironic, but I have serious concerns about the usaiblity implication for clients17:50
betherlyWoohooooo17:50
jrolllucasagomes: so I think devananda makes a good point, in that it's a third field to look at to determine the state17:50
*** kzaitsev_mb has quit IRC17:50
lucasagomesjroll, devananda right yeah I agree that target_ would be ideal17:51
devanandalucasagomes: ie, anyone building an interface on top of ironic suddenly needs to account for a whole new field (above a certain api version)17:51
rameshg87jroll: determine target state rather17:51
jrollrameshg87: the overall state :)17:51
lucasagomesjust trying to figure how we can actually implement it17:51
*** rhagarty has joined #openstack-meeting-317:51
lucasagomesdue the way our global lock current works17:51
rloowhat if we had a concept like 'queuing events'17:51
devanandarloo: indeed .... :)17:51
lucasagomestarget_provision_state to be a queue?17:51
jrollI brought that up before17:51
jrollit's super complex17:52
NobodyCamwould a que'd delete work for what lucasagomes is looking to acomplish?17:52
rloowell, i wasn't thinking of target_* being a queue. More like a separate field, with target* reflecting the current action.17:52
jrollsee top level comments for patch set 717:52
devanandayea, we spent a lot of time (well, at least I did) thinking about how we would do an event / queue based system intead of our current+target system17:52
rloocuz there are problems with queues, eg depending on what events are queued.17:53
devanandathe API changes for that would be, well, massive17:53
lucasagomesdevananda, right17:53
devanandaas it represents a complete shift in how one interacts with the service17:53
*** dims_ has joined #openstack-meeting-317:53
devanandait's not something we can incrementally add17:53
rameshg87and you never know if the queue will be executed or not17:54
NobodyCamgood poing rameshg8717:54
NobodyCampoint even17:54
devanandarameshg87: in a properly designed event-based system, one does know if the enqueued item is acted upon or times out (because of TTLs and call-backs) ...17:54
lucasagomesdevananda, one way I was thinking is to have instance as a separated resource17:54
devanandarameshg87: split-brain scenarios not withstanding17:55
lucasagomesone can create an instance, and then assign it to the node (instance_uuid)17:55
* mrda sounds the bell for 5 minute warning17:55
devanandawhich is where one gets into RAFT or BASE systems17:55
lucasagomesand on that instance you can mark as delete17:55
devanandaanyway ... :)17:55
NobodyCamTY  mrda17:55
devanandalucasagomes: "instance" as a resource in ironic?17:55
lucasagomesdevananda, yeah... (I know it's already a "thing" in nova too)17:56
devanandacause, well, it's already a resource in Nova. perhaps we just need to change the nova.ironic.virt driver to be able to issue the deletes?17:56
devanandaheh17:56
devananda*re-issue17:56
jrollso devananda and I actually talked about this topic a bit at the midcycle17:56
jrolland about possibly making the state machine transitions work differently based on (provision_state, target_provision_state)17:56
*** dims has quit IRC17:57
jrolland this could make delete a valid transition for (DEPLOYING, ACTIVE)17:57
jrollit might get weird in fsm.py, but that's probably ok17:57
lucasagomesjroll, right, but how to make it not racy17:57
jrollwhere's the race?17:57
rameshg87jroll: and where would we record the new desired transition ?17:57
devanandarameshg87: we'd update target_state17:58
jrollrameshg87: it would change target to DELETED17:58
devanandaie, (DEPLOYING, DELETED) becomes a valid state17:58
lucasagomeshmm17:58
betherlyBefore this meeting ends real quick17:58
devanandaso that when the current task finishes and calls process_event("done")17:58
betherlyWanted to just bring up horizon UI stuff if anyone has heard further on those panels? Otherwise waiting on the UX guys and Piet to be in touch :)17:58
betherlyWill chase on it this week17:58
lucasagomesjroll, I mean, we certainly need to acquire a exclusive lock to do that17:58
devanandathen task_manager notices that the target_state has changed -- and is now DELETED -- and fires off the next step automatically17:59
rloohow would we update target_state if another task has lock on node?17:59
BadCubbetherly: you can follow up with me on that as well.17:59
lucasagomesjroll, when the request comes it will already be locked by another process17:59
betherlyBadCub: thanks I'll message you :)17:59
BadCub:)17:59
lucasagomesso 2 process writing to the node simultaneously17:59
rameshg87I think we should go back to channel and then discuss17:59
lucasagomesI mean same fields17:59
jrolllucasagomes: yeah, the locking is where it gets weird, surely it's possible to deal with it17:59
lucasagomesyeah chanell17:59
jrollcool18:00
lucasagomestimes' up18:00
devanandayep. time's up18:00
jrollthanks all18:00
devanandathanks everyone!18:00
BadCubthanks everyone!18:00
NobodyCamthank you all18:00
mrdaThanks everyone - nice to chat with you in the meeting!18:00
jlvillalThanks!18:00
*** sridhar_ram has joined #openstack-meeting-318:00
*** singlethink has joined #openstack-meeting-318:00
rloolucasagomes: so I think we can handle this if we don't do it via periodic task. if eg a task about to finish whatever it was doing before xsitioning to a new state, checks something else...18:00
devanandasee you all at the same bat time, same bat channel next week!18:00
devananda#endmeeting18:00
NobodyCam:)18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Mon Aug 17 18:00:28 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-08-17-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-08-17-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-08-17-17.00.log.html18:00
*** BadCub has left #openstack-meeting-318:00
*** yuriyz has left #openstack-meeting-318:00
*** aarefiev22 has quit IRC18:01
betherlyThanks guys18:02
betherly*all18:02
*** lucasagomes has left #openstack-meeting-318:02
*** singleth_ has quit IRC18:04
*** s3wong has joined #openstack-meeting-318:05
*** liliars_ has left #openstack-meeting-318:05
*** afaranha has left #openstack-meeting-318:05
*** yamamoto has joined #openstack-meeting-318:06
*** rloo has left #openstack-meeting-318:07
*** tfukushima has quit IRC18:07
*** krtaylor has quit IRC18:08
*** stevemar has quit IRC18:08
*** rameshg87 has quit IRC18:09
*** stevemar has joined #openstack-meeting-318:10
*** bpokorny_ has joined #openstack-meeting-318:11
*** yamamoto has quit IRC18:11
*** bpokorny has quit IRC18:12
*** rhagarty has quit IRC18:13
*** rhagarty_ has quit IRC18:13
*** rhagarty has joined #openstack-meeting-318:13
*** rhagarty_ has joined #openstack-meeting-318:13
*** btully has quit IRC18:18
*** sankarshan is now known as sankarshan_away18:19
*** krtaylor has joined #openstack-meeting-318:21
*** sbalukoff has joined #openstack-meeting-318:21
*** bharath has quit IRC18:24
*** nate_gone is now known as njohnston18:25
*** mickeyspiegel has quit IRC18:26
*** yamahata has quit IRC18:28
*** thiagop has left #openstack-meeting-318:31
*** wojdev has joined #openstack-meeting-318:36
*** MarkAtwood has joined #openstack-meeting-318:36
*** Piet has quit IRC18:40
*** e0ne has joined #openstack-meeting-318:40
*** bharath has joined #openstack-meeting-318:45
*** singleth_ has joined #openstack-meeting-318:45
*** kzaitsev_mb has joined #openstack-meeting-318:46
*** jpomeroy has joined #openstack-meeting-318:48
*** singlethink has quit IRC18:49
*** jpomeroy_ has joined #openstack-meeting-318:50
*** jpomeroy_ has quit IRC18:52
*** krtaylor has quit IRC18:55
*** sahid has quit IRC19:02
*** e0ne has quit IRC19:03
*** kzaitsev_mb has quit IRC19:05
*** geoffarnold has quit IRC19:07
*** krtaylor has joined #openstack-meeting-319:08
*** e0ne has joined #openstack-meeting-319:09
*** geoffarnold has joined #openstack-meeting-319:12
*** armax has joined #openstack-meeting-319:12
*** Rockyg has joined #openstack-meeting-319:13
*** LouisF has joined #openstack-meeting-319:14
*** Sukhdev has quit IRC19:15
*** mrunge has joined #openstack-meeting-319:15
*** vdrok_ has quit IRC19:22
*** achippa_ has joined #openstack-meeting-319:32
*** achippa has joined #openstack-meeting-319:32
*** smccully has quit IRC19:35
*** achippa_ has quit IRC19:36
*** achippa has quit IRC19:36
*** tfukushima has joined #openstack-meeting-319:43
*** e0ne has quit IRC19:45
*** e0ne has joined #openstack-meeting-319:48
*** dims_ has quit IRC19:48
*** dims has joined #openstack-meeting-319:48
*** LouisF has quit IRC19:51
*** mrmartin has quit IRC20:19
*** kzaitsev_mb has joined #openstack-meeting-320:24
*** tfukushima has quit IRC20:27
*** mwagner_lap has quit IRC20:35
*** mickeys has joined #openstack-meeting-320:36
*** mrunge has quit IRC20:36
*** kzaitsev_mb has quit IRC20:38
*** tfukushima has joined #openstack-meeting-320:40
*** Sukhdev has joined #openstack-meeting-320:41
*** VW_ has quit IRC20:48
*** claudiub has quit IRC20:48
*** VW_ has joined #openstack-meeting-320:48
*** Rockyg has quit IRC20:51
*** puranamr has quit IRC20:52
*** trown is now known as trown|outttypeww20:53
*** achippa_ has joined #openstack-meeting-320:57
*** achippa has joined #openstack-meeting-320:57
*** annp has joined #openstack-meeting-320:58
*** exploreshaifali has joined #openstack-meeting-321:00
flaper87#startmeeting Zaqar21:01
openstackMeeting started Mon Aug 17 21:01:07 2015 UTC and is due to finish in 60 minutes.  The chair is flaper87. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: Zaqar)"21:01
openstackThe meeting name has been set to 'zaqar'21:01
*** yamahata has joined #openstack-meeting-321:01
flaper87vkmc: exploreshaifali flwang121:01
vkmcHI21:01
exploreshaifalihi!21:01
flaper87hellooooooooooooooooooooooo21:01
vkmco/21:01
flaper87#topic Roll Call21:01
*** openstack changes topic to "Roll Call (Meeting topic: Zaqar)"21:01
flaper87o/21:01
vkmco/21:01
exploreshaifalio/21:02
flaper87#topic Agenda21:02
*** openstack changes topic to "Agenda (Meeting topic: Zaqar)"21:02
flaper87#link https://wiki.openstack.org/wiki/Meetings/Zaqar#Agenda21:02
flaper87that's our agenda for today21:02
flaper87I believe we don't have pending actions from last week other than reviews21:02
flaper87so, lets get started with our topics for today21:02
flaper87#topic Pending important reviews21:03
*** openstack changes topic to "Pending important reviews (Meeting topic: Zaqar)"21:03
* flaper87 checks gerrit21:03
flaper87#link https://review.openstack.org/#/c/213744/21:03
flaper87recently, auth for ws landed. That patch fixes a deauth bug21:03
*** lblanchard has quit IRC21:03
flaper87#link https://review.openstack.org/#/c/202374/ ( flwang1 )21:03
*** cbouch has quit IRC21:04
flaper87That's email notifications, it still needs to be updated21:04
flwang1o/21:04
flaper87flwang1: morning buddy21:04
flaper87#link https://review.openstack.org/#/c/212828/21:04
vkmcflwang1, morning!21:04
flaper87That one is a new baby but quite important too21:04
flwang1mornings, zaqers :021:04
flaper87That puts us closer to running mongodb+sql21:04
exploreshaifalimorning flwang1 :)21:04
flaper87#link https://review.openstack.org/#/c/195010/21:05
flaper87That's claims for WS21:05
flaper87vkmc has been updating it21:05
flaper87and we kinda have to merge it to complete the ws work21:05
flaper87we still have time so please, lets get to it21:05
flaper87#link https://review.openstack.org/#/c/199824/21:06
vkmcclaims, notifications (therve's) and we are all set for ws I guess21:06
flaper87Set unreliable to False by default21:06
flaper87vkmc: yup, remember we'll discuss notifications+ws tomorrow at 12/13 UTC21:06
vkmcyes :) will be there21:06
flaper87lets see how that goes and if we can merge WS notifications in Liberty21:06
flaper87ok, that's it from the reviews side21:06
flaper87Great work on reviews last week21:07
*** kzaitsev_mb has joined #openstack-meeting-321:07
flaper87Lets keep it up and review the pending patches21:07
flaper87btw21:07
flaper87One note w.r.t reviews21:07
flaper87#link http://lists.openstack.org/pipermail/openstack-dev/2015-August/072191.html21:07
flaper87Ryan Brown has accepted to join the core-reviewers team21:08
vkmcwohoooo21:08
flaper87With full honesty, that sets us one step farther away from having a diverse team21:08
flaper87Nonetheless, I'm very happy about it21:08
flaper87Ryan has provided great reviews and guidance21:09
*** jtomasek has quit IRC21:09
*** amotoki has joined #openstack-meeting-321:09
flaper87please chime in if you've something to share/say21:09
flaper87:D21:09
*** jckasper has quit IRC21:09
exploreshaifaliGreat! yes he answer my questions :P21:09
*** yamamoto has joined #openstack-meeting-321:09
flaper87:D21:09
vkmcryansb is great, I'm really happy to have him in Zaqar21:09
flwang1flaper87: seems all the zaqar core team members should be  redhater, right?21:10
flwang1can you send my CV to your boss?21:10
exploreshaifalihaha21:10
flaper87flwang1: you can just send it to me ;)21:10
vkmclol flwang121:11
flwang1ok, seriously, we need more guys from the other org21:11
flaper87flwang1: yeah, I'm not very proud of that but that's the best we can afford from now until ametts sends back ppl from RAX :P21:11
vkmcwe need more diversity in our team, please bring more Catalyzers flwang1!21:11
flaper87flwang1: or you can put more resources :)21:12
vkmc(I just invented a term to call people from Catalyst)21:12
flwang1flaper87: i will21:12
flaper87Catalystizers is WAY better21:12
*** banix has quit IRC21:12
flaper87just sayin'21:12
vkmchahaha21:12
flaper87flwang1 I'll take your word on that21:12
flaper87:)21:12
vkmcjust repeat it 10 times non-stop21:12
vkmcand tape yourself doing that21:12
flaper87argh, MY HEAD!21:12
vkmcand post it to twitter21:13
vkmcthanks21:13
flwang1flaper87: i will eat my words if you still don't buy a beer for me21:13
flaper87did anyone see my last vine?21:13
flaper87T_T21:13
vkmcnope21:13
* flaper87 keeps embarrasing himself21:13
flaper87ok, don't go there21:13
vkmctoo late21:13
flaper87flwang1 I'll buy you TONS of beers21:13
flaper87with vkmc's credit card21:13
flaper87ok, moving on21:14
flaper87#topic OpenStack Summit (Tokyo)21:14
*** openstack changes topic to "OpenStack Summit (Tokyo) (Meeting topic: Zaqar)"21:14
vkmcflaper87, good luck with that :D haha21:14
flaper87Not much to say there, to be honest. However, we need to start planning sessions.21:14
vkmcyeah21:14
vkmcI have one I have one I have one21:14
flaper87We know what features landed in Liberty and the ones left for Mitaka21:14
flaper87therefore, I'd like us to start brainstorming on specs on what's next in terms of features21:14
flaper87Just like for Liberty, I think we should keep the number of features in Zaqar small and focus on having other projects consuming Zaqar21:15
flaper87In addition to that, I believe we should have sessions for things that have a spec21:15
*** mestery has joined #openstack-meeting-321:15
*** alexpilotti has quit IRC21:16
flaper87Rather than going there and just do basic brainstorming, I'd like us to use that time to clear doubts and move some specs forward21:16
vkmcso, maybe its a good moment to talk about integration with Horizon?21:16
*** alexpilotti has joined #openstack-meeting-321:16
flaper87Although, this needs to be discussed with the next PTL as well21:16
flaper87vkmc: what kind of integration?21:17
*** julim has quit IRC21:17
flaper87vkmc: horizon consiming Zaqar? or having a Zaqar UI on horizon?21:17
vkmcflaper87, Horizon consuming Zaqar21:17
vkmcfor the Zaqar UI... I think that one is not so urgent21:17
flaper87vkmc: exploreshaifali is working on the UI, AFAIR21:18
*** ameybhide has joined #openstack-meeting-321:18
exploreshaifaliyes21:18
*** carl_baldwin has joined #openstack-meeting-321:18
vkmccool21:18
vkmcI didn't know about it21:18
flaper87vkmc: re horizon consuming Zaqar, it'd be really cool21:18
exploreshaifalitoday only I had a littile discussion about same with one Horizon dev21:18
flaper87However, we should also prioritize adoption efforts21:18
*** pballand has quit IRC21:18
flaper87This cycle we focused a lot on Heat and we had tons of help from Heat folks21:18
exploreshaifaliand he asked me to prepare a BP first21:18
vkmcnice21:18
flaper87Next cycle, I think we could focus on either guest-agent or user-facing notifications21:19
flaper87At this point, I'm leaning towards the later since it's definitely a use-case that hasn't been explored enough21:19
flwang1flaper87: any links about the integration with heat? should we invite heat folks to give/join a session?21:19
flaper87flwang1: I think we should give space to other projects this time21:20
*** FallenPegasus has joined #openstack-meeting-321:20
flaper87We've had Heat sessions for 2 summits in a row21:20
flaper87and we've gotten to the point where heat is consuming Zaqar21:20
flaper87now we need to help other projects21:20
flwang1flaper87: ok, cool21:20
flaper87Also, I'd like to see a session on the client21:21
flaper87I hope dynarro will be able to attend and prepare that session21:21
flwang1flaper87: i vote for a GUI of zaqar in horizon and the  integration of horizon21:21
flaper87flwang1: I'd love to have a GUI but that's at the bottom of my interests and what I believe is urgent21:21
exploreshaifaliI think I can prepare spec for zaqar GUI before summit21:22
flaper87unless you folks think otherwise, I'd prefer to stick with that21:22
flaper87exploreshaifali: that should be a horizon spec, though.21:22
exploreshaifaliyeah21:22
flaper87I'd love to attend that session if it is scheduled and approved21:22
*** pballand has joined #openstack-meeting-321:22
exploreshaifaligreat! :)21:23
flwang1flaper87: how about the swift notification middleware?21:23
flaper87flwang1: that's  another exciting use-case, great thinking.21:23
flaper87flwang1: we should also sync with them21:23
flaper87#info sync with notmyname and swift folks about swift consuming zaqar21:24
* flaper87 intentionally summoned notmyname21:24
flwang1s/notmyname/flaper8721:24
flaper87#info sync with folks from horizon to clarify their use-case for Zaqar now that websocket is in place21:24
flaper87ok, anything else?21:25
* notmyname will be happy to talk. is in meeting for a few more minute21:25
flaper87Can we convert the above into action items?21:25
flaper87flwang1 would you like to sync with ppl from swift ?21:26
*** yamamoto has quit IRC21:26
flaper87vkmc: would you like to sync with folks from horizon ?21:26
vkmcflaper87, sure21:26
flaper87I will sync again w/ folks from Sahara since their required feature is implemented21:26
vkmc#action vkmc sync with folks from horizon21:26
flwang1flaper87: yes, and what's the ppl you're talking about?21:26
flaper87#action vkmc to sync with folks from horizon about a possible joint session for zaqar+horizon21:27
vkmcthanks21:27
flaper87#action flwang1 to sync with folks from swift about a possible joint session for zaqar+swift (swift notification middleware)21:27
flaper87#action flwang1 to sync with folks from Sahara about their guest-agent use-case21:27
flaper87damnit21:27
flaper87#undo21:27
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x9a13cd0>21:27
flaper87#action flaper87 to sync with folks from Sahara about their guest-agent use-case21:27
flaper87ooooooooooooooooook21:28
flaper87we can move on now21:28
*** ameybhide has left #openstack-meeting-321:28
flaper87#topic Testing and Focus21:28
*** openstack changes topic to "Testing and Focus (Meeting topic: Zaqar)"21:28
flaper87I believe this cycle has been productive so far. We still don't have a crazy load of users but we've moved forward with steadier steps21:28
*** FallenPegasus has quit IRC21:29
flaper87Now is the time to test what we've done and make sure it's as rock solid as we can expect it to be21:29
flaper87therefore, I'd like to call for a joint testing session21:29
flaper87What day from next week would work for you ?21:29
flaper87I'd like us to dedicate a full-day (or as much as you can from that day) to testing Zaqar21:30
flaper87Single node, multi-node, pre-signed url, websocket, etc21:30
flaper87V2 needs testing-love21:30
flaper87and so on21:30
vkmcsounds good21:30
vkmcThursday/Friday are usually good for me (no meetings those days)21:31
exploreshaifaliyea its exciting21:31
flaper87flwang1: what about you?21:31
flaper87exploreshaifali: what about you?21:31
flaper87Thursday/Friday?21:31
flaper87Shall we do Friday?21:31
exploreshaifaliI am ok with any day21:31
flaper87It'd be like a hackday21:31
flwang1Friday works for me21:31
exploreshaifaliyup Friday will work21:31
flaper87Awesome, Friday next week it is21:31
flwang1flaper87: i'm interested in the performance of notification21:31
exploreshaifali:D21:32
flaper87That should give us enough time to land the remanining patches21:32
flaper87flwang1: yeah, same here. I'll work on a list of tasks for the test-day21:32
flaper87Etherpad, that is.21:32
flwang1flaper87: cool21:32
vkmcI want to check websocket vs wsgi :o21:32
*** FallenPegasus has joined #openstack-meeting-321:33
flaper87awesome21:33
flaper87all that sounds awesome21:33
flaper87ok, I don't have much else on this topic21:33
flaper87I wanted us to find a date and schedule the test-day21:34
flaper87I'll send an email to the mailing list and then a reminder next-week21:34
vkmccool21:34
flaper87anything else?21:34
flaper87I'll take that as a no21:35
flaper87#topic Open Discussion21:35
*** openstack changes topic to "Open Discussion (Meeting topic: Zaqar)"21:35
vkmcI have a few things for Open Discussion21:36
vkmc1. Rally gate21:36
flaper87go21:36
flwang1i have a open question21:36
vkmcit has been failing for a while now21:36
flwang1yep, i saw the rally gate failure recently21:36
vkmcand I couldn't be able to find logs on that21:36
vkmczaqar server seems not to be starting and there are on logs on the screens21:36
flaper87vkmc: yeah, I was going to work on the gate today and then got side-tracked21:36
flwang1vkmc: is there a bug?21:36
flwang1i can work on that21:36
vkmcflwang1, nope, I didn't file a bug21:37
flaper87that said, I think the reason the server is not showing the logs is because of the "fork" code21:37
vkmcoh21:37
flaper87flwang1: how's the policy work going ?21:37
*** FallenPegasus has quit IRC21:37
flwang1flaper87: it works based on my test, and i'm trying to make the unit test pass21:37
flaper87flwang1: cool, I look forward to your patch21:38
flwang1we just need some decorators like this https://review.openstack.org/#/c/209910/1/zaqar/transport/wsgi/v2_0/queues.py21:38
flaper87I'm heads down on fixing bugs now so, lets try to find as many as we can and fix them21:38
flwang1flaper87: i have another topic21:39
flaper87go21:39
flwang1not sure if all of you guys are interested in21:39
flwang1as we're trying to adopt zaqar21:39
flwang1but you know, we're public cloud(though we're small), so we need to charge our customer21:39
flwang1for zaqar, the question is how to charge our customer21:40
flwang1you know, there is no api request statistics components in openstack, like AWS21:40
flaper87flwang1: I'm very interested in that topic21:40
vkmcflwang1, me too21:41
flaper87and I'm sad we couldn't improve our story there during Liberty21:41
flwang1so we're thinking another way to charge user based on message number21:41
flaper87That said, I think we have some options21:41
flaper87These options include emitting things to ceilo or statsd21:41
exploreshaifalimay be by counting/tracking the size and number of messages21:41
flwang1but because AWS and RAX are charging based on API request21:41
flwang1so i'm not sure if it's stupid ideae21:41
vkmcflwang1, AWS SQS/SNS have the same charging schema?21:41
vkmcthan the rest of AWS21:42
flaper87What if we leave that to the cloud provider? What if we limit ourselves to emit as much useful information as we can?21:42
*** zz_natorious is now known as natorious21:42
flwang1First 1 million Amazon SQS Requests per month are free             $0.50 per 1 million Amazon SQS Requests  per month thereafter ($0.00000050 per SQS Request)21:42
flaper87Once the cloud provider has info to reason about, it'll be easy to find compeating plans21:42
flwang1vkmc: ^21:42
flaper87flwang1: requests or messages?21:42
vkmcI see21:42
flaper87What about bulk requests ?21:42
vkmcrequests21:42
flaper87erm, bulk inserts21:43
flwang1request21:43
vkmcA single request can have from 1 to 10 messages, up to a maximum total payload of 256KB.21:43
flwang1api request21:43
flaper87ok21:43
flaper87eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeenteresting21:43
*** achippa_ has quit IRC21:43
*** achippa has quit IRC21:43
flaper87so yeah, I think the best thing we can do is not to start reasoning about what metrics we can emit21:43
flaper87Then ask for feedback to OPs21:43
vkmcyup21:44
flaper87and start emitting a sub-set of those metrics21:44
flwang1flaper87: i was thinking we can create another pipeline plugin like the notifications plugin to count the message numbers for billing21:44
*** achippa has joined #openstack-meeting-321:44
*** achippa_ has joined #openstack-meeting-321:44
flwang1but i'm not sure if that's the correct direction21:44
vkmcwould it make sense to consume Ceilometer for this?21:44
flwang1like i mentioned above, because AWS and RAX didn't go for that21:44
flaper87flwang1: mmh, I think we already have that info in the transport layer but we'll figure that out later21:44
*** pballand has quit IRC21:45
flwang1brb in 5 mins21:45
flaper87vkmc: yup, I'd say ceilo or statsd21:45
vkmcflaper87, never heard of statsd21:45
vkmccool21:45
flaper87I just don't like the idea of working on some specific metrics and say: "This is how you should bill"21:45
vkmcbut we can collect metrics21:45
vkmcand the cloud provider decides21:46
flaper87I'd rather have a set of metrics and say: "This is what you have for billing, you figure it out"21:46
vkmc"ok, I'll charge on no of queues... no of messages... no of requests.."21:46
vkmcyeah21:46
vkmccharge for all the things21:46
flaper87"You've been breathing a lot today, Sir. We'll charge you 0.01 for each breath you took"21:47
vkmchaha21:47
flaper87lets give flwang1 a couple of mins to come back and comment, otherwise, we'll call it21:47
vkmcsure21:47
vkmcin the meantime21:47
vkmcI want to gently remind21:47
vkmc2. docs21:47
vkmcwe don't have docs whatsoever for api v2.021:48
vkmcI'll document websocket, but we also need some love for the other features21:48
vkmcwell, ws is for v1.121:48
flaper87True that, I'll do my part on pre-signed URLs21:48
vkmclet's say, new features21:48
*** achippa_ has quit IRC21:48
*** achippa has quit IRC21:48
vkmc3. client and cli21:49
vkmcwe need to catch up with reviews there as well21:49
vkmcwe have implementations for pools and flavors for the cli, and support for v2 for several endpoints21:49
flaper87yup yup21:49
flaper87I'm hoping we can do a zaqarclient release soon21:49
vkmcyeah me too21:50
flaper87I'd like to work on pre-signed urls first21:50
vkmcdynarro has been working a lot on that21:50
flaper87niiiiiiiiiiiiiiiiiiiiiice21:50
vkmcand we also have some contributions diga and exploreshaifali did21:50
*** VW_ has quit IRC21:50
flaper87+121:51
flaper87ok, lets call it!21:51
*** VW_ has joined #openstack-meeting-321:51
*** banix has joined #openstack-meeting-321:51
vkmcsweet21:51
flaper87flwang1: we can keep talking in #os-zaqar21:51
flaper87THANKS FOLKS!21:51
flaper87great meeting and lets keep it up21:51
flaper87#endmeeting21:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:51
vkmcYEAH :D :D21:51
openstackMeeting ended Mon Aug 17 21:51:32 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:51
vkmcthanks21:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zaqar/2015/zaqar.2015-08-17-21.01.html21:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zaqar/2015/zaqar.2015-08-17-21.01.txt21:51
*** achippa has joined #openstack-meeting-321:51
*** achippa_ has joined #openstack-meeting-321:51
openstackLog:            http://eavesdrop.openstack.org/meetings/zaqar/2015/zaqar.2015-08-17-21.01.log.html21:51
exploreshaifaliThanks everyone!21:51
flaper87vkmc: ^ <321:51
flaper87:D21:51
vkmcflaper87, ^<321:51
vkmc:)21:51
*** exploreshaifali has quit IRC21:56
*** mwagner_lap has joined #openstack-meeting-321:57
*** rhagarty has quit IRC22:00
*** rhagarty_ has quit IRC22:00
*** mestery has quit IRC22:01
*** mestery has joined #openstack-meeting-322:04
*** rhagarty has joined #openstack-meeting-322:04
*** Swami has quit IRC22:04
*** rhagarty_ has joined #openstack-meeting-322:04
*** wojdev has quit IRC22:04
*** smccully has joined #openstack-meeting-322:05
*** njohnston is now known as nate_gone22:07
*** mestery has quit IRC22:09
*** carl_baldwin has quit IRC22:09
*** wojdev has joined #openstack-meeting-322:10
*** sdake_ has joined #openstack-meeting-322:10
*** yamamoto has joined #openstack-meeting-322:11
*** sdake has quit IRC22:13
*** MarkAtwood has quit IRC22:13
*** amotoki has quit IRC22:14
*** alexpilotti has quit IRC22:19
*** Swami has joined #openstack-meeting-322:21
*** vgridnev has quit IRC22:23
*** vgridnev has joined #openstack-meeting-322:23
*** vgridnev has quit IRC22:24
*** neelashah has quit IRC22:24
*** dims_ has joined #openstack-meeting-322:25
*** jpomeroy has quit IRC22:26
*** dims has quit IRC22:28
*** natorious is now known as zz_natorious22:36
*** yamamoto has quit IRC22:37
*** banix has quit IRC22:38
*** carl_baldwin has joined #openstack-meeting-322:39
*** achippa has quit IRC22:39
*** achippa_ has quit IRC22:39
*** ameybhide has joined #openstack-meeting-322:40
*** banix has joined #openstack-meeting-322:40
*** ameybhide has quit IRC22:41
*** e0ne has quit IRC22:41
*** Sukhdev has quit IRC22:41
*** baoli has joined #openstack-meeting-322:45
*** docaedo has quit IRC22:46
*** singleth_ has quit IRC22:47
*** dims_ has quit IRC22:47
*** achippa_ has joined #openstack-meeting-322:47
*** achippa has joined #openstack-meeting-322:47
*** dims has joined #openstack-meeting-322:47
*** baoli has quit IRC22:50
*** markvoelker has quit IRC22:51
*** achippa_ has quit IRC22:51
*** achippa has quit IRC22:51
*** dims has quit IRC22:51
*** kzaitsev_mb has quit IRC22:55
*** jpomeroy has joined #openstack-meeting-322:57
*** mickeys has quit IRC23:00
*** sdake_ is now known as sdake23:01
*** jpomeroy has quit IRC23:07
*** salv-orl_ has quit IRC23:09
*** salv-orlando has joined #openstack-meeting-323:12
*** mestery has joined #openstack-meeting-323:13
*** puranamr has joined #openstack-meeting-323:13
*** VW_ has quit IRC23:14
*** VW_ has joined #openstack-meeting-323:14
*** shwetaap has quit IRC23:16
*** VW_ has quit IRC23:19
*** Sukhdev has joined #openstack-meeting-323:19
*** smccully has quit IRC23:21
*** kzaitsev_mb has joined #openstack-meeting-323:21
*** sdake_ has joined #openstack-meeting-323:23
*** jpomeroy has joined #openstack-meeting-323:25
*** kzaitsev_mb has quit IRC23:26
*** sdake has quit IRC23:26
*** jpomeroy has quit IRC23:29
*** jpomeroy has joined #openstack-meeting-323:30
*** markvoelker has joined #openstack-meeting-323:35
*** salv-orlando has quit IRC23:36
*** yamamoto has joined #openstack-meeting-323:37
*** yamamoto has quit IRC23:42
*** VW_ has joined #openstack-meeting-323:48
*** mickeys has joined #openstack-meeting-323:50
*** armax has quit IRC23:51
*** kzaitsev_mb has joined #openstack-meeting-323:52
*** mestery has quit IRC23:55
*** bharath has quit IRC23:58
*** amotoki has joined #openstack-meeting-323:59

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