Wednesday, 2017-01-04

*** spzala has quit IRC00:02
*** spzala has joined #openstack-meeting00:02
*** sdake has quit IRC00:04
*** baoli has quit IRC00:05
*** dimtruck is now known as zz_dimtruck00:08
*** kjorgensen has joined #openstack-meeting00:13
*** salv-orlando has quit IRC00:14
*** zz_dimtruck is now known as dimtruck00:15
*** bobh has joined #openstack-meeting00:16
*** yamamoto has joined #openstack-meeting00:17
*** AlanClark has quit IRC00:19
*** bobh has quit IRC00:19
*** fnaval has joined #openstack-meeting00:20
*** saisrikiran has joined #openstack-meeting00:21
*** jaugustine has quit IRC00:26
*** jaugustine has joined #openstack-meeting00:26
*** jaugustine has quit IRC00:30
*** Julien-zte has joined #openstack-meeting00:30
*** Swami has quit IRC00:32
*** hongbin has quit IRC00:32
*** saisrikiran has quit IRC00:35
*** jrobinson has quit IRC00:36
*** fnaval has quit IRC00:38
*** jrobinson has joined #openstack-meeting00:38
*** fnaval has joined #openstack-meeting00:39
*** dimtruck is now known as zz_dimtruck00:44
*** guoshan has joined #openstack-meeting00:45
*** claudiub|2 has quit IRC00:48
*** kjorgensen has quit IRC00:49
*** guoshan has quit IRC00:50
*** fnaval has quit IRC00:51
*** fnaval has joined #openstack-meeting00:52
*** ayoung has quit IRC00:53
*** jrobinson has quit IRC00:53
*** jrobinson has joined #openstack-meeting00:54
*** thorst has joined #openstack-meeting00:55
*** thorst has quit IRC00:58
*** ijw has quit IRC01:01
*** diablo_rojo has quit IRC01:02
*** Fdaisuke_ has joined #openstack-meeting01:04
*** liusheng has joined #openstack-meeting01:04
*** yamamoto has quit IRC01:04
*** Fdaisuke has quit IRC01:05
*** fnaval has quit IRC01:07
*** huanxuan has joined #openstack-meeting01:14
*** salv-orlando has joined #openstack-meeting01:15
*** salv-orlando has quit IRC01:20
*** ijw has joined #openstack-meeting01:22
*** unicell has joined #openstack-meeting01:24
*** ijw has quit IRC01:27
*** rfolco_ has joined #openstack-meeting01:28
*** rfolco_ has quit IRC01:28
*** eliqiao has quit IRC01:29
*** claudiub|2 has joined #openstack-meeting01:29
*** kevinz has joined #openstack-meeting01:30
*** yangyapeng has joined #openstack-meeting01:30
*** rfolco_ has joined #openstack-meeting01:31
*** rfolco_ has quit IRC01:31
*** eliqiao has joined #openstack-meeting01:33
*** sdake has joined #openstack-meeting01:33
*** guoshan has joined #openstack-meeting01:37
*** X-dark_ has joined #openstack-meeting01:37
*** X-dark has quit IRC01:38
*** X-dark_ is now known as X-dark01:38
*** ijw has joined #openstack-meeting01:43
*** rfolco_ has joined #openstack-meeting01:46
*** rfolco_ has quit IRC01:46
*** jrobinson has quit IRC01:46
*** jrobinson has joined #openstack-meeting01:48
*** kjorgensen has joined #openstack-meeting01:49
*** ijw has quit IRC01:50
*** sdake_ has joined #openstack-meeting01:50
*** ijw has joined #openstack-meeting01:52
*** sdake has quit IRC01:52
*** kjorgensen has quit IRC01:54
*** thorst has joined #openstack-meeting01:54
*** jrobinson has quit IRC01:54
*** rfolco_ has joined #openstack-meeting01:56
*** rfolco_ has quit IRC01:56
*** ijw has quit IRC01:57
*** claudiub|2 has quit IRC01:59
*** bobh_ has joined #openstack-meeting01:59
*** yamamoto has joined #openstack-meeting02:02
*** gongysh has joined #openstack-meeting02:03
*** ijw has joined #openstack-meeting02:05
*** ianw is now known as ianw_pto02:07
*** ijw has quit IRC02:11
*** epico has joined #openstack-meeting02:11
*** zz_dimtruck is now known as dimtruck02:12
*** guoshan has quit IRC02:12
*** lhx__ has joined #openstack-meeting02:16
*** salv-orlando has joined #openstack-meeting02:16
*** rbudden has joined #openstack-meeting02:17
*** unicell has quit IRC02:19
*** ljxiash has joined #openstack-meeting02:20
*** ljxiash has quit IRC02:20
*** ljxiash has joined #openstack-meeting02:21
*** thorst has quit IRC02:21
*** salv-orlando has quit IRC02:21
*** thorst has joined #openstack-meeting02:21
*** thorst has quit IRC02:25
*** VW has joined #openstack-meeting02:26
*** sdake_ has quit IRC02:29
*** VW has quit IRC02:30
*** mickeys has quit IRC02:31
*** _Fdaisuke_ has joined #openstack-meeting02:39
*** mickeys has joined #openstack-meeting02:39
*** Fdaisuke_ has quit IRC02:42
*** s3wong has quit IRC02:45
*** thorst has joined #openstack-meeting02:47
*** sdake has joined #openstack-meeting02:48
*** cloud_player has quit IRC02:49
*** cloud_player has joined #openstack-meeting02:49
*** yinwei_computer has joined #openstack-meeting02:49
*** thorst has quit IRC02:49
*** jrobinson has joined #openstack-meeting02:55
*** jrobinson is now known as jrobinson-afk02:58
*** lhx__ has quit IRC03:00
*** ljxiash has quit IRC03:06
*** ljxiash has joined #openstack-meeting03:06
*** ljxiash has quit IRC03:11
*** guoshan has joined #openstack-meeting03:16
*** hongbin has joined #openstack-meeting03:17
*** mriedem has quit IRC03:22
*** lhx__ has joined #openstack-meeting03:23
*** jrobinson-afk is now known as jrobinson-03:28
*** epico has quit IRC03:29
*** nklenke has quit IRC03:33
*** thorst has joined #openstack-meeting03:35
*** prateek has quit IRC03:36
*** prateek has joined #openstack-meeting03:36
*** thorst has quit IRC03:36
*** prateek has quit IRC03:45
*** sudipto has joined #openstack-meeting03:45
*** sudipto_ has joined #openstack-meeting03:45
*** r-mibu has quit IRC03:47
*** r-mibu has joined #openstack-meeting03:47
*** nklenke has joined #openstack-meeting03:48
*** epico has joined #openstack-meeting03:52
*** links has joined #openstack-meeting03:56
*** lhx__ has quit IRC03:58
*** dimtruck is now known as zz_dimtruck04:00
*** lhx__ has joined #openstack-meeting04:01
*** yinwei_computer has left #openstack-meeting04:01
*** ijw has joined #openstack-meeting04:01
*** zhonghua has quit IRC04:02
*** guoshan has quit IRC04:02
*** zhonghua has joined #openstack-meeting04:02
*** bobh_ has quit IRC04:02
*** zz_dimtruck is now known as dimtruck04:04
*** bobh has joined #openstack-meeting04:06
*** baoli has joined #openstack-meeting04:10
*** bobh has quit IRC04:11
*** baoli has quit IRC04:15
*** spzala has quit IRC04:16
*** salv-orlando has joined #openstack-meeting04:17
*** ljxiash has joined #openstack-meeting04:19
*** salv-orlando has quit IRC04:21
*** hongbin has quit IRC04:22
*** sudipto_ has quit IRC04:27
*** sudipto has quit IRC04:27
*** bkopilov has quit IRC04:28
*** kjorgens_ has joined #openstack-meeting04:29
*** thorst has joined #openstack-meeting04:37
*** guoshan has joined #openstack-meeting04:38
*** bkopilov has joined #openstack-meeting04:40
*** thorst has quit IRC04:41
*** guoshan has quit IRC04:43
*** cartik has joined #openstack-meeting04:50
*** adisky_ has joined #openstack-meeting04:52
*** janki has joined #openstack-meeting04:52
*** aeng has quit IRC04:53
*** kjorgens_ has quit IRC04:55
*** kjorgensen has joined #openstack-meeting04:55
*** aeng has joined #openstack-meeting04:56
*** VW has joined #openstack-meeting05:00
*** unicell has joined #openstack-meeting05:01
*** kjorgens_ has joined #openstack-meeting05:02
*** ayogi has joined #openstack-meeting05:04
*** kjorgensen has quit IRC05:05
*** reedip has joined #openstack-meeting05:05
*** sudipto has joined #openstack-meeting05:08
*** sudipto_ has joined #openstack-meeting05:08
*** kjorgens_ has quit IRC05:09
*** martines_ has quit IRC05:14
*** lhx__ has quit IRC05:19
*** kjorgensen has joined #openstack-meeting05:21
*** ijw has quit IRC05:25
*** kjorgens_ has joined #openstack-meeting05:25
*** martines_ has joined #openstack-meeting05:27
*** kjorgensen has quit IRC05:29
*** tung_doan has joined #openstack-meeting05:29
*** KanagarajM has joined #openstack-meeting05:30
sridhar_ram#startmeeting tacker05:30
openstackMeeting started Wed Jan  4 05:30:47 2017 UTC and is due to finish in 60 minutes.  The chair is sridhar_ram. Information about MeetBot at http://wiki.debian.org/MeetBot.05:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:30
*** openstack changes topic to " (Meeting topic: tacker)"05:30
openstackThe meeting name has been set to 'tacker'05:30
*** X-dark has quit IRC05:30
gongyshhi05:30
KanagarajMhi05:30
sridhar_ram#topic Roll Call05:30
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"05:30
gongyshme here05:31
jankio/05:31
sridhar_ramgongysh: KanagarajM: janki: hi there!05:31
tung_doanhi all05:31
jankiHi sridhar_ram, all05:31
gongyshhi05:31
*** tbh has joined #openstack-meeting05:31
KanagarajMhi05:31
*** Yan has joined #openstack-meeting05:32
sridhar_ramHappy new year team!05:32
tbhhi05:32
sridhar_ramlet's start ..05:32
sridhar_ram#chair gongysh tbh KanagarajM05:32
openstackCurrent chairs: KanagarajM gongysh sridhar_ram tbh05:32
sridhar_ram#topic Agenda05:32
*** openstack changes topic to "Agenda (Meeting topic: tacker)"05:32
sridhar_ram#link https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Jan_4th.2C_201605:32
sridhar_ram#topic Announcements05:33
*** openstack changes topic to "Announcements (Meeting topic: tacker)"05:33
*** mkrai has quit IRC05:34
sridhar_ramnothing specific from my side, except the usual reminder of Ocata deadline coming up fast05:34
sridhar_ram#topic Ocata Blueprint Status05:34
*** openstack changes topic to "Ocata Blueprint Status (Meeting topic: tacker)"05:34
sridhar_ram#topic NSD spec05:34
*** openstack changes topic to "NSD spec (Meeting topic: tacker)"05:34
sridhar_ramtbh: dkushawa: can you please provide an update ?05:34
* sridhar_ram realizes the topic should be NSD implementation status05:35
tbhsridhar_ram, pushed most of the functionality, the remaining items in the todo list are UTs/FTs05:35
gongyshtbh, do we have a guide for testing?05:36
sridhar_ramtbh: that's wonderful !05:36
tbhI just recorded a quick video of nsd https://www.dropbox.com/s/isu0fs1ebutg9gh/nsd.mp4?dl=0(not sure that is correct format to share)05:36
tbhgongysh, ^^05:36
gongyshtbh,  cool, we should have a rst in our doc dir, I think.05:37
tbhgongysh, yes05:37
*** gouthamr has joined #openstack-meeting05:37
sridhar_ramgongysh: agree...05:38
sridhar_ramlet's take 3 mins to quickly look at tbh's video05:39
gongyshtbh, the video is cool05:42
sridhar_ramfolks - please share your comments05:42
tbhsome optimizations are needed as it involves building dict and yaml. so I think it will be covered mostly in reviews :)05:42
sridhar_ramtbh: the demo is cool05:42
sridhar_ramtbh: do we need those import line (for VNF1 and VNF2) in nsd.yaml ?05:43
*** csomerville has quit IRC05:43
tbhsridhar_ram, gongysh thanks05:43
tbhsridhar_ram, yes as per TOSCA nfv profile syntax05:43
*** cody-somerville has joined #openstack-meeting05:43
*** cody-somerville has quit IRC05:43
*** cody-somerville has joined #openstack-meeting05:43
KanagarajMtbh, nice demo !05:44
*** prateek has joined #openstack-meeting05:44
sridhar_ramtbh: sounds good, glad we made VNFD name unique05:44
jankitbh: good one05:44
KanagarajMsridhar_ram, tbh , i think import part is not required for tacker defintions05:44
tbhsridhar_ram, absolutely, that helped a lot in this patch05:44
sridhar_ramtbh: all this using mistral behind the scenes ?05:45
KanagarajMas its already taken care in tacker while invoking the HT05:45
tbhsridhar_ram, yes, mistral occupied most of the time05:45
tbhKanagarajM, we aren't invoking HT directly from nsd perspective05:46
tbhnsd -> mistral -> tacker -> VNF05:46
gongyshtbh, I need a guide to test,  do we have one somewhere?05:46
KanagarajMtbh, oh ! yes. I remember05:46
*** s3wong has joined #openstack-meeting05:46
s3wongsorry, late05:47
tbhgongysh, I will push the rst by EOD05:47
gongyshtbh, thanks, looking forward to it.05:47
*** ricolin has joined #openstack-meeting05:47
*** kristian__ has joined #openstack-meeting05:47
KanagarajMsridhar_ram, tbh, so now, we could make NDS and VNFD all follow the same process in terms of importing the tacker definitions. is it ok ?05:47
sridhar_ramKanagarajM: i think you've this  HT bug https://bugs.launchpad.net/heat-translator/+bug/1652928 in mind05:48
openstackLaunchpad bug 1652928 in Heat Translator "Fails to translate the derived polices" [High,New] - Assigned to Sahdev Zala (spzala)05:48
KanagarajMsridhar_ram, yes :)05:48
sridhar_ramtbh: while we don't use HT, we still use tosca-parser for NSD and tosca imports still play a role there. correct ?05:48
sridhar_rams3wong: hi there05:49
tbhsridhar_ram, right05:49
tbhKanagarajM, I didn't get you05:49
sridhar_ramKanagarajM: now, i don't understand how can we get to follow the same process .. they already follow the same pattern05:50
sridhar_ramKanagarajM: we remove tacker custom types from the ToscaTemplate and pass a "sanitized" tree to HT05:50
KanagarajMsridhar_ram, in case of VNFD, tacker takes the resposibility of importing the tacker defined tosca defitions, while for NSD user should include in TOSCA05:50
*** dkushwaha has joined #openstack-meeting05:51
dkushwahao/05:51
dkushwahasorry I am late05:51
sridhar_ramKanagarajM: that where i was kind of questioning tbh .. why we need an import. But now I understand it make sense to have them05:51
KanagarajMsridhar_ram, you mean, will include imports in TOSCA before passign to HT05:52
sridhar_ramKanagarajM: without those import the "VNF1" type few lines further down won't parse05:52
*** kristian__ has quit IRC05:52
tbhsridhar_ram, you are right05:52
Yano/05:53
tbhsridhar_ram, and these VNF1 has to be defined in VNFD1.yaml05:53
sridhar_ramKanagarajM: for VNFD the imports are custom variations on top of TOSCA_nfv_definitions in tosca-parser, so those custom types needs to be stripped before sending to HT. HT won't know an tacker custom types05:53
KanagarajMsridhar_ram, tbh, for VNFD, HT passes the parsing without explicitily menting the import statements in VNFD05:53
sridhar_ramtbh: hmm.. you mean there should be a VNFD1 in the tacker vnfd catalog?05:54
tbhsridhar_ram, KanagarajM like this http://paste.openstack.org/show/593839/05:54
tbhsridhar_ram, yes05:54
sridhar_ramtbh: so, it is not really a "file" per se ?05:55
sridhar_ramtbh: we can take the rest in the code review05:55
*** VW has quit IRC05:55
sridhar_ramoverall .. happy w/ the progress you and dkushwaha has made!05:55
sridhar_ramgood job05:55
KanagarajMi think we should not bother user to include the tacker defined types in VNFD or NSD, because tacker  should take care of it05:55
*** mkrai has joined #openstack-meeting05:55
tbhsridhar_ram, we thought of having VNFD name in NSD instead of VNFD path05:55
KanagarajMsridhar_ram, ^^ Tacker takes the control on the TOSCA definitions supported by it05:56
KanagarajMtbh, s3wong , sridhar_ram  but does HT  expecting to have import in place,05:57
gongyshKanagarajM, I think we should provide users to extend the TOSCA definition in the future.05:57
tbhKanagarajM, HT when invokes TP, it expects imports05:57
sridhar_ramKanagarajM: we can consider automating all the VNF type "references" to automatically lookup in the tacker catalog .. that is more a convenience (reducing few lines in NSD) than anything else05:57
*** ykatabam has quit IRC05:58
KanagarajMgongysh, not sure !05:59
sridhar_ramKanagarajM: anyways, leave that comment in the gerrit .. we can let tbh and dkushwaha evaluation it05:59
KanagarajMsridhar_ram, yes +105:59
sridhar_ramto me it is not a deal breaker05:59
KanagarajMsridhar_ram, yes, i would like tbh, s3wong would take a look on that defect05:59
sridhar_ramlet's get the NS client changes in ASAP05:59
s3wongKanagarajM: sure06:00
KanagarajMs3wong, thanks06:00
*** kristian__ has joined #openstack-meeting06:00
sridhar_ramanything else on NSD?06:00
*** kristian__ has quit IRC06:00
sridhar_rammoving on..06:01
tbhhad few issues in horizon part06:01
tbhbut keeping it in the last part for now06:02
sridhar_ramthere was an issue on VNFD catalog page which gongysh just pushed a patch (thanks gongysh!)06:02
sridhar_ramtbh: sure, make sense..06:02
sridhar_ramKanagarajM: since we are in the topic, do you want to discuss https://bugs.launchpad.net/heat-translator/+bug/1652928 here ?06:03
openstackLaunchpad bug 1652928 in Heat Translator "Fails to translate the derived polices" [High,New] - Assigned to Sahdev Zala (spzala)06:03
gongyshsridhar_ram, it bothered me a few days.06:03
sridhar_ramgongysh: i finally hit the same problem today after a restack06:03
KanagarajMsridhar_ram, yes06:04
sridhar_ram#topic HT failure due to tacker imports06:04
*** openstack changes topic to "HT failure due to tacker imports (Meeting topic: tacker)"06:04
sridhar_rammy understanding is there is a new release of HT (and TP?) pending release any moment and that is failing tacker sanity tests ?06:05
KanagarajMs3wong, we are waiting for this bug to get dfixed sooner for scaling seletive vdu06:05
KanagarajMselective vdu scaling *06:05
KanagarajMs3wong, sahdev is looking into already. and kindly help further on it06:05
*** jrobinson- is now known as jrobinson06:06
sridhar_ramKanagarajM: from the bug notes, this sounds like a HT regression.06:06
*** gouthamr has quit IRC06:06
s3wongKanagarajM, sridhar_ram: seems like bobh's area --- looking at his comment on the bug now06:06
sridhar_rams3wong: agree06:06
*** diga has joined #openstack-meeting06:07
digao/06:07
digasorry got late06:07
sridhar_rambobh: are you here?06:07
KanagarajMs3wong, sure.06:07
sridhar_ramdiga: hi !06:07
KanagarajMsridhar_ram, yes06:07
sridhar_ramKanagarajM: okay, spzala is probably not online now06:07
s3wongsridhar_ram: probably a little late for bobh06:07
KanagarajMsridhar_ram, seems !06:08
sridhar_ramKanagarajM: what is the specific error you get? unknown node type?06:08
*** dimtruck is now known as zz_dimtruck06:08
*** lhx__ has joined #openstack-meeting06:09
KanagarajMsridhar_ram, no. It is not returning the scaling yaml (provider template to be generated by HT as part policy->targets)06:09
gongyshtung_doan, do you run into this bug?06:10
KanagarajMto produced the bug, you need to use the master copy of the HT06:10
sridhar_ramKanagarajM: Hmm... HT should honor any derived types and parse properly06:10
KanagarajMsridhar_ram, +106:11
sridhar_ramKanagarajM: it will be good if we can narrow down to a specific HT patchset that broke this06:11
s3wongKanagarajM: in that case, seems like there has been changes on master HT which caused this prpblem06:12
s3wongproblem06:12
sridhar_ramKanagarajM: obviously something post HT 0.7.0 release.. anyways spzala is looking into this06:12
sridhar_ramlet's give him sometime06:12
KanagarajMsridhar_ram, its a new feature added in HT, but it broken the back-ward comaptibility06:12
sridhar_rami'll follow up him tomorrow US time06:13
KanagarajMsridhar_ram, sure. thanks06:13
sridhar_ramKanagarajM: yeah, seems like06:13
s3wongKanagarajM: so the breakage is between heat-translator and latest HT?06:13
sridhar_ramlike i mentioned, any incomp issue w/ tosca-parser or HT is a pain, need to be on the top of it06:13
sridhar_rams3wong: yes06:14
tung_doangongysh: no.. seems like it's the new bug06:14
KanagarajMs3wong, yes i guess so, as tacker didn't face the issue in neuton06:14
sridhar_ramalright, let's circle back after the resp from spzala06:15
sridhar_rammoving on..06:15
sridhar_ram#topic Ocata Client Release06:15
*** openstack changes topic to "Ocata Client Release (Meeting topic: tacker)"06:15
*** kenji-i has joined #openstack-meeting06:16
sridhar_ramIn preparation for Ocata Final Client release on Jan 23rd (see https://releases.openstack.org/ocata/schedule.html)06:16
sridhar_ram.. we need to get all client changes in ASAP06:16
sridhar_ramcores: please prioritize the tackerclient patchsets in your review queue06:17
sridhar_ramonce NSD client merges i plan to release an "interim" tackerclient06:18
gongyshsridhar_ram, got it06:18
sridhar_ramthis will help to pass dsvm gate tests for the NSD server sider patchset06:18
sridhar_ramgongysh: thanks!06:18
sridhar_ramapart from NSD and VNFFGD param support, are there any other feature pending tackerclient changes for Ocata ?06:19
jankisridhar_ram, inline template?06:19
jankiI have pushed the client patch06:19
sridhar_ramjanki: yes, thanks for reminding..06:20
sridhar_ramjanki: do you've a link?06:20
jankisridhar_ram, https://review.openstack.org/#/c/414602/ - client patch06:20
sridhar_ramjanki: thanks06:20
jankiI have 1 query sort of too for this feature, sridhar_ram06:21
sridhar_ramfyi, here is the NSD client patchset .. https://review.openstack.org/41218806:21
KanagarajMsridhar_ram, i just +206:21
KanagarajMsridhar_ram, waiting for main feature to land06:21
sridhar_ramKanagarajM: thanks!06:21
*** guoshan has joined #openstack-meeting06:22
*** amotoki has joined #openstack-meeting06:22
sridhar_ramjanki: let's move to open discussions06:22
sridhar_ramanything else on tackerclient ?06:22
gongyshKanagarajM, why wait for main feature to land. I think main feature is waiting for it.06:22
sridhar_ramgongysh: +106:22
KanagarajMgongysh, i mean NSD feature support in Tacker06:23
KanagarajMsridhar_ram, gongysh am i missing something :(06:23
gongyshKanagarajM, Kind of. the codes in client and server sometimes depend on each other.06:23
s3wongKanagarajM: yeah, I thought we are releasing client first --- so assuming NSD landing in Ocata is going to happen, we can merge the client changes now...06:24
tbhKanagarajM, to pass dsvm gate tests for NSD patches in Tacker we need client patch to be merged06:24
gongyshKanagarajM, server code needs it to have functional tests.06:24
sridhar_ramKanagarajM: typically client changes goes in first w/o server, we make a client release and server will use to pass dsvm gate06:24
KanagarajMyeah, only functional test will be pending i agree06:24
sridhar_ramKanagarajM: exactly106:24
gongyshKanagarajM, yes.06:24
sridhar_ram#topic Open Discussion06:25
*** openstack changes topic to "Open Discussion (Meeting topic: tacker)"06:25
sridhar_ramjanki: what is your question ?06:25
gongyshsridhar_ram, KanagarajM , I think we can let client merge.06:25
sridhar_ramdiga: thanks for taking fwd the api-framework using falcon!06:25
sridhar_ramgongysh: agree06:25
jankisridhar_ram, I am thinking in inline template, while deleting vnf the corresponding vnfd should also be deleted06:25
digasridhar_ram: yep06:25
KanagarajMgongysh, sridhar_ram i think if we +A, gerrit does not allow as there is a depends-on tag in commit message06:25
jankithis point is mentioned in the spec06:25
sridhar_ramjanki: make sense to me06:26
digasridhar_ram: can we go ahead & create feature/branch for falcon-api-framework06:26
* sridhar_ram notes 4 mins left06:26
KanagarajMsridhar_ram, gongysh so we need to remove depends-on tag from commit message !06:26
gongyshKanagarajM,  yes.06:26
digasridhar_ram: I will address your comments by today EOD after discussion with monasca team06:26
jankisridhar_ram, should I code it even without being mentioned in spec?06:26
sridhar_ramdiga: let's take up api-framework discussion next week06:26
digasridhar_ram: okay06:26
tbhKanagarajM, I will update the commit message06:27
jankisridhar_ram, and also to delete vnfd if vnf is in error state. not sure how valid this would be06:27
gongyshsridhar_ram, what happened to odl sfc?06:27
*** apetrich has joined #openstack-meeting06:27
KanagarajMtbh, sure. thanks.06:27
sridhar_ramjanki: it is fine unless it is  against what is mentioned in the spec..06:28
jankisridhar_ram, it is not against the spec. infact the point is not mentioned. so will add it06:29
tbhupdated the commit message for client patch https://review.openstack.org/#/c/412188/06:29
sridhar_ramgongysh: that is a bigger topic, another time06:29
jankisridhar_ram, how about deleting vnfd if vnf is in error state?06:29
sridhar_ramjanki: let's take it offline06:29
sridhar_ramtimes up folks06:29
sridhar_ramthanks for joining06:29
s3wongbye06:30
Yanbye06:30
sridhar_ram#endmeeting06:30
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"06:30
openstackMeeting ended Wed Jan  4 06:30:07 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2017/tacker.2017-01-04-05.30.html06:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2017/tacker.2017-01-04-05.30.txt06:30
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2017/tacker.2017-01-04-05.30.log.html06:30
*** KanagarajM has left #openstack-meeting06:30
*** sridharg has joined #openstack-meeting06:31
*** RuiChen has joined #openstack-meeting06:34
*** claudiub|2 has joined #openstack-meeting06:35
*** Kevin_Zheng has joined #openstack-meeting06:35
*** lpetrut has joined #openstack-meeting06:36
*** thorst has joined #openstack-meeting06:38
*** kjorgens_ has quit IRC06:40
*** dkushwaha has left #openstack-meeting06:40
*** thorst has quit IRC06:42
*** salv-orlando has joined #openstack-meeting06:43
*** usman has joined #openstack-meeting06:46
*** korzen has joined #openstack-meeting06:51
*** zz_dimtruck is now known as dimtruck06:51
*** pcaruana has joined #openstack-meeting06:51
*** bkopilov has quit IRC06:52
*** nadya has joined #openstack-meeting06:53
*** e0ne has joined #openstack-meeting06:54
*** nadya has quit IRC06:54
*** dimtruck is now known as zz_dimtruck06:57
*** jrobinson has quit IRC06:59
*** nkrinner_afk has quit IRC06:59
*** nkrinner has joined #openstack-meeting06:59
*** Yan has left #openstack-meeting07:09
*** tung_doan has left #openstack-meeting07:13
*** rcernin has joined #openstack-meeting07:15
*** X-dark has joined #openstack-meeting07:17
*** e0ne has quit IRC07:17
*** tesseract has joined #openstack-meeting07:18
*** ykatabam has joined #openstack-meeting07:18
*** rasca has joined #openstack-meeting07:21
*** rbudden has quit IRC07:21
*** lpetrut has quit IRC07:27
*** mickeys has quit IRC07:33
*** bkopilov has joined #openstack-meeting07:33
*** kristian__ has joined #openstack-meeting07:37
*** salv-orlando has quit IRC07:39
*** YanXingan has joined #openstack-meeting07:39
*** kristian__ has quit IRC07:39
*** kristian__ has joined #openstack-meeting07:39
*** Cibo_ has joined #openstack-meeting07:42
*** kristian__ has quit IRC07:42
*** s3wong has quit IRC07:52
*** VW has joined #openstack-meeting07:55
*** gongysh_ has joined #openstack-meeting07:59
*** cartik has quit IRC07:59
*** matrohon has joined #openstack-meeting07:59
*** VW has quit IRC08:00
*** gongysh has quit IRC08:00
*** apetrich has quit IRC08:12
*** jchhatbar has joined #openstack-meeting08:17
*** janki has quit IRC08:19
*** nadya has joined #openstack-meeting08:30
*** lhx__ has quit IRC08:31
*** leon_wang has quit IRC08:32
*** mickeys has joined #openstack-meeting08:33
*** nadya has quit IRC08:34
*** gongysh_ has quit IRC08:37
*** yuval has joined #openstack-meeting08:38
*** thorst has joined #openstack-meeting08:39
*** mickeys has quit IRC08:39
*** lhx__ has joined #openstack-meeting08:40
*** rasca has quit IRC08:41
*** thorst has quit IRC08:43
*** anilvenkata has joined #openstack-meeting08:45
*** rasca has joined #openstack-meeting08:49
*** usman has left #openstack-meeting08:49
*** salv-orlando has joined #openstack-meeting08:49
*** priteau has joined #openstack-meeting08:49
*** kristian__ has joined #openstack-meeting08:50
*** gongysh has joined #openstack-meeting08:51
*** kjorgensen has joined #openstack-meeting08:52
*** rasca has quit IRC08:53
*** cartik has joined #openstack-meeting08:53
*** korzen has quit IRC08:54
*** korzen has joined #openstack-meeting08:56
*** kjorgensen has quit IRC08:57
*** rasca has joined #openstack-meeting09:00
*** korzen has quit IRC09:00
*** iyamahat has joined #openstack-meeting09:01
*** toscalix has joined #openstack-meeting09:01
*** korzen has joined #openstack-meeting09:02
*** Cibo_ has quit IRC09:03
*** ricolin has quit IRC09:03
*** StefanPaetowJisc has joined #openstack-meeting09:03
*** iyamahat has quit IRC09:04
*** dbecker has joined #openstack-meeting09:05
*** acoles_ is now known as acoles09:12
*** ricolin has joined #openstack-meeting09:13
*** fzdarsky has joined #openstack-meeting09:14
*** rasca has quit IRC09:15
*** rasca has joined #openstack-meeting09:16
*** hashar has joined #openstack-meeting09:19
*** lpetrut has joined #openstack-meeting09:21
*** tbh has quit IRC09:23
*** tinwood has quit IRC09:27
*** YanXingan has left #openstack-meeting09:30
*** acoles is now known as acoles_09:31
*** acoles_ is now known as acoles09:34
*** mickeys has joined #openstack-meeting09:36
*** mickeys has quit IRC09:41
*** hurricanerix has quit IRC09:41
*** hurricanerix has joined #openstack-meeting09:43
*** tinwood has joined #openstack-meeting09:47
*** jchhatbar_ has joined #openstack-meeting09:50
*** Julien-zte has quit IRC09:53
*** jchhatbar has quit IRC09:53
*** salv-orl_ has joined #openstack-meeting09:53
*** kristian__ has quit IRC09:54
*** salv-orlando has quit IRC09:56
*** kristian__ has joined #openstack-meeting09:56
*** sudipto has quit IRC10:08
*** sudipto_ has quit IRC10:08
*** guoshan has quit IRC10:13
*** ljxiash has quit IRC10:16
*** ljxiash has joined #openstack-meeting10:16
*** StefanPaetowJisc has left #openstack-meeting10:17
*** anilvenkata has quit IRC10:17
*** ljxiash has quit IRC10:18
*** ljxiash has joined #openstack-meeting10:18
*** e0ne has joined #openstack-meeting10:22
*** kevinz has quit IRC10:23
*** zhurong has joined #openstack-meeting10:26
*** anilvenkata has joined #openstack-meeting10:29
*** ociuhandu has quit IRC10:31
*** apetrich has joined #openstack-meeting10:32
*** armax has joined #openstack-meeting10:36
*** mickeys has joined #openstack-meeting10:37
*** thorst has joined #openstack-meeting10:39
*** lhx__ has quit IRC10:39
*** mickeys has quit IRC10:41
*** yamahata has quit IRC10:42
*** thorst has quit IRC10:44
*** yamamoto has quit IRC10:47
*** rcarrillocruz has quit IRC10:49
*** links has quit IRC10:57
*** epico has quit IRC11:00
*** huanxuan has quit IRC11:03
*** lhx__ has joined #openstack-meeting11:03
*** sdague has joined #openstack-meeting11:04
*** sambetts|afk is now known as sambetts11:04
*** salv-orl_ has quit IRC11:05
*** matrohon has quit IRC11:09
*** zhurong has quit IRC11:19
*** dfflanders has quit IRC11:19
*** ayoung has joined #openstack-meeting11:20
*** ljxiash has quit IRC11:20
*** korzen has quit IRC11:20
*** tiantian has joined #openstack-meeting11:20
*** links has joined #openstack-meeting11:21
*** gongysh has quit IRC11:21
*** askb has quit IRC11:23
*** rfolco has joined #openstack-meeting11:25
*** yangyapeng has quit IRC11:26
*** salv-orlando has joined #openstack-meeting11:28
*** fanyishi has joined #openstack-meeting11:31
*** fanyishi has quit IRC11:31
*** anilvenkata has quit IRC11:32
*** claudiub|2 has quit IRC11:36
*** mickeys has joined #openstack-meeting11:38
*** yamamoto has joined #openstack-meeting11:40
*** mickeys has quit IRC11:42
*** ljxiash has joined #openstack-meeting11:46
*** yamamoto has quit IRC11:46
*** anilvenkata has joined #openstack-meeting11:46
*** yamamoto has joined #openstack-meeting11:47
*** sdake has quit IRC11:49
*** huanxuan has joined #openstack-meeting11:50
*** ljxiash has quit IRC11:50
*** sshnaidm|afk is now known as sshnaidm11:51
*** yamamoto has quit IRC11:51
*** diga has quit IRC11:55
*** liusheng has quit IRC12:01
*** sankarshan_away is now known as sankarshan12:03
*** claudiub|2 has joined #openstack-meeting12:04
*** neiljerram has joined #openstack-meeting12:07
*** yamamoto has joined #openstack-meeting12:17
*** ljxiash has joined #openstack-meeting12:19
*** jkilpatr has joined #openstack-meeting12:20
*** rtheis has joined #openstack-meeting12:26
*** kristian__ has quit IRC12:26
*** ricolin has quit IRC12:29
*** liusheng has joined #openstack-meeting12:29
*** cartik has quit IRC12:30
*** cdelatte has joined #openstack-meeting12:30
*** rtheis_ has joined #openstack-meeting12:30
*** rtheis has quit IRC12:33
*** sudipto_ has joined #openstack-meeting12:33
*** sudipto has joined #openstack-meeting12:33
*** mickeys has joined #openstack-meeting12:39
*** rtheis has joined #openstack-meeting12:40
*** thorst has joined #openstack-meeting12:41
*** jaypipes has joined #openstack-meeting12:42
*** rtheis_ has quit IRC12:42
*** yamamoto has quit IRC12:42
*** liuzyu has joined #openstack-meeting12:42
*** Administrator has joined #openstack-meeting12:42
*** Administrator is now known as Guest3023412:43
*** mickeys has quit IRC12:43
*** lhx__ has quit IRC12:47
*** yangyapeng has joined #openstack-meeting12:49
*** dongfeng has joined #openstack-meeting12:51
*** JunSik has joined #openstack-meeting12:52
*** Yipei has joined #openstack-meeting12:54
*** fanyishi has joined #openstack-meeting12:55
*** yinxiulin has joined #openstack-meeting12:56
*** salv-orlando has quit IRC12:56
*** zhurong has joined #openstack-meeting12:56
*** weshay is now known as weshay_doctor12:58
*** joehuang has joined #openstack-meeting12:58
*** WuCheng has joined #openstack-meeting12:58
*** matrohon has joined #openstack-meeting12:59
joehuanghello13:01
joehuang#startmeeting tricircle13:01
openstackMeeting started Wed Jan  4 13:01:32 2017 UTC and is due to finish in 60 minutes.  The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: tricircle)"13:01
openstackThe meeting name has been set to 'tricircle'13:01
yinxiulinhello13:01
joehuang#topic rollcall13:01
*** openstack changes topic to "rollcall (Meeting topic: tricircle)"13:01
joehuang#info joehuang13:02
zhiyuan#info zhiyuan13:02
Yipei#info Yipei13:02
dongfeng#info dongfeng13:02
yinxiulin#info xiulin13:02
WuCheng#WuCheng13:02
WuCheng#info WuCheng13:02
JunSik#info JunSik13:03
joehuang#topic shadow_agent for VxLAN L2 networking/L3 DVR issue13:03
*** openstack changes topic to "shadow_agent for VxLAN L2 networking/L3 DVR issue (Meeting topic: tricircle)"13:03
joehuanghello, zhiyuan, how about the PoC progress of shadow agent13:04
joehuangany challenges found?13:04
zhiyuani have finished the PoC test and yes, the shadow agent/port solution works. some works left before the submission, i need to add a new type driver for shared_vxlan, and also handle resource clearing13:05
*** RongHui11 has joined #openstack-meeting13:06
joehuangso you can prepare a spec for review13:06
RongHui11hello13:06
joehuanghello, ronghui13:06
RongHui11sorry for late13:06
*** nadya has joined #openstack-meeting13:06
joehuangit's fine :)13:06
zhiyuanafter creating VMs in two pods in the same network, the vxlan tunnels are creating in both pods and thus the two VMs are connected13:06
*** bobmel has joined #openstack-meeting13:06
zhiyuanyes, will start to write the spec13:07
joehuangawsome!13:07
*** salv-orlando has joined #openstack-meeting13:07
*** bobh has joined #openstack-meeting13:07
joehuanglooking forward for the spec13:07
zhiyuan:)13:08
joehuanghow about L3 bridge network using VxLAN13:08
*** nadya has quit IRC13:08
zhiyuanoh, this part not tested yet13:09
zhiyuanthen i test the vxlan network for l3 first?13:10
joehuangit's the key whether we can get the vtep for external gateway port13:10
zhiyuanwe can collect this in central plugin, but need to figure out how to trigger l2 pop13:11
*** bobmel has quit IRC13:11
zhiyuanexternal gateway port is not VM port13:12
joehuangfor L3 networking, although we can use vlan, but the number is limited, so it's better to use vxlan as the bridge network, no matter for which kind of local network13:12
joehuangcorrect, it's not VM port, the device owner is different13:13
zhiyuanmaybe we can also create shadow port and shadow agent for gateway port, need further investigation13:13
joehuangsince currently no vxlan external network has been used yet, so maybe some chanllenge13:15
*** yamamoto has joined #openstack-meeting13:16
*** sdake has joined #openstack-meeting13:16
*** lhx__ has joined #openstack-meeting13:18
joehuang#action investigate whether shadow agent/port can help L3 networking on VxLAN bridge network13:18
joehuanggood, next topic13:18
joehuangone second13:18
joehuangother question on shadow agent/port?13:19
joehuang#topic db migration version13:20
*** openstack changes topic to "db migration version (Meeting topic: tricircle)"13:20
joehuanghello yipei, how about the db migrate_version13:20
Yipeialready finish it and tested in my environment13:20
*** korzen has joined #openstack-meeting13:21
*** ayogi has quit IRC13:21
joehuangcool13:21
Yipeiit works, but still have some small problems in code, i will improve it13:21
Yipeii just imitate the code in kingbird13:22
joehuang#link https://review.openstack.org/41653413:22
Yipeistill need to do some research on code13:22
*** bobh has quit IRC13:23
joehuangtricircle has no tricircle-engine13:23
Yipeii still do not understand some details in code13:23
Yipeiyes13:23
Yipeii also discover the problem13:23
Yipeineed to go on improving the code13:24
joehuangyou can use configuration file api.conf13:24
joehuangbut I don't know why configuration file is needed for db-sync13:25
Yipeiconfiguration file?13:27
*** tongli has joined #openstack-meeting13:28
joehuangline 65 default_config_files13:28
Yipeii also do not know why, i will figure out13:28
*** yamamoto has quit IRC13:28
joehuangok, please jump to the source code oslo_config to find out the cfg.CONF initiailization13:30
joehuangany question?13:30
Yipeino13:31
joehuang#open discussion13:31
RongHui11no13:31
joehuang#topic open discussion13:32
*** openstack changes topic to "open discussion (Meeting topic: tricircle)"13:32
joehuanghow about the qos feature?13:33
*** lamt has joined #openstack-meeting13:33
joehuangis xiongqiu online?13:34
*** jungleboyj has quit IRC13:34
Yipeifor lbaas, i tested lbaas with Octavia in tricircle13:34
Yipeii find some problems13:35
joehuangwhat's found13:35
joehuangwhat did you find?13:36
Yipeifirstly, for the functions of tricircle, the command "neutron --os-region-name=CentralRegion net-create net1" fails13:36
Yipeithe error is as follows. Region CentralRegion is not a valid region name for cloud envvars. Valid choices are RegionOne. Please note that region names are case sensitive.13:36
zhiyuanoh, that's an old issue13:36
*** longxiongqiu has joined #openstack-meeting13:36
joehuangyou need to unset the environment variables13:37
zhiyuanjust run "unset OS_REGION_NAME"13:37
Yipeineutron --os-region-name=RegionOne net-create net1, it works13:37
joehuangyes13:37
*** X-dark has quit IRC13:37
Yipeiit tried13:37
YipeiInternalServerError: Request Failed: internal server error while processing your request.13:38
YipeiFile "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 365, in post13:38
joehuanghave you added the pod? and all pods exists13:38
*** tommylikehu_ has joined #openstack-meeting13:39
Yipeiyes, all the pods are added13:39
joehuangone region or two region13:39
*** mickeys has joined #openstack-meeting13:39
Yipeitwo region13:39
zhiyuanthen need to dig into the log file to see why13:40
*** darvon has quit IRC13:40
joehuangdid the second region register to the keystone13:40
*** yuval has quit IRC13:41
*** prateek has quit IRC13:41
longxiongqiuHello, joe. Sorry for lating, i am recently writing a paper for a conference in order to graduate, the conference dead time is near. i will give the completed code to jiawei for testing and upload it.13:41
*** nklenke has quit IRC13:41
joehuangto xiongqiu, how about the spec?13:41
RongHui11i will finish the spec13:41
Yipeito joehuang, yes13:42
Yipeii will check logs to find the error13:42
joehuangso openstack --os-region-name=RegionOne endpoint list works?13:42
joehuangyes, please.13:42
joehuangOther topics?13:43
*** wxy| has joined #openstack-meeting13:43
Yipeito joehuang, it works13:43
Yipeialso13:43
*** darvon has joined #openstack-meeting13:43
Yipeiif i create a net successfully, will neutron create corresponding ports?13:44
*** mickeys has quit IRC13:44
joehuangno13:44
*** efried has quit IRC13:44
Yipeiok, i see13:44
joehuangonly if you boot a VM in Nova, or explicitly create a port13:44
*** HeleneCoullon has joined #openstack-meeting13:44
Yipeihow about dhcp_port?13:45
Yipeiwill it also created when booting a VM?13:45
zhiyuandhcp port is created when you create the subnet13:45
joehuangnot network13:45
Yipeino, i create a subnet, but there is no dhcp_port13:46
joehuangand if enable_dhcp is true when creating subnet13:46
*** nklenke has joined #openstack-meeting13:46
zhiyuanyou mean no dhcp port in local neutron?13:46
Yipeiyes, at first, i tried to install tricircle and octavia together with devstack13:47
*** nadya has joined #openstack-meeting13:47
*** reedip_ has joined #openstack-meeting13:47
Yipeioctavia will create a subnet, but it fails since there is no dhcp_port13:47
Yipeii tried to install octavia manually13:48
*** dprince has joined #openstack-meeting13:48
Yipeiafter create a subnet, still no dhcp_port13:48
joehuangoctavia will send command to regionone, I think. Unless you install ocatavia in central region13:48
*** korzen has quit IRC13:48
*** korzen has joined #openstack-meeting13:48
joehuangneed to figure out which region ocatavia belongs to, and where the request it issued to13:49
Yipeii see13:49
joehuangby default, only tricircle api/xjob and central neutron server in central region in devstack installation13:50
joehuangso ocatavia by default will be installed in regionone13:50
zhiyuanyes, if lb talks to local neutron, it can create the subnet, but dhcp agent will fail to create the dhcp port because the ip is not allocated in central neutron13:51
Yipeioh, i see13:51
joehuangyes, the local neutron has been configured with tricircle local plugin, the dhcp port behavior is different the default13:53
Yipeiso i will check logs and try to create nets and subnets first, then install octavia manually. And go on testing13:53
joehuangok, to ronghui, look forward to the spec of qos13:53
zhiyuani think you can just configure LB to talk to central neutron13:54
zhiyuanOR we need LB to talk to local neutron?13:54
joehuangyou can register ocatavia in central region, manually register13:54
*** WuCheng has quit IRC13:54
joehuangremove the old endpoint which resides in the regionone13:54
*** ljxiash has quit IRC13:55
*** sridharg has quit IRC13:55
joehuangyes, zhiyuan's proposal may also work13:55
joehuangneed to find the neutron url configuration in ocatavia13:55
joehuangand change it, reboot ocatvia service13:56
joehuangbut one second13:56
joehuangI am afraid it'll fail13:56
joehuangbecause ocatavia now will boot LB service via Nova13:57
joehuangI am not sure whether ocatavia can work with different region services, nova/glance in regionone, neutron in centralregion13:58
zhiyuanif LB does need to talk to local neutron, then we need to create the network and subnet in central neutron first13:58
joehuangI suggest Yipei to study that in detail13:59
joehuangtime is up13:59
Yipeiok13:59
zhiyuanand pass the subnet ID in central neutron to LB, when LB tries to query the subnet, the subnet will be created in local plugin13:59
joehuangthank you for attending the meeting13:59
joehuang#endmeeting13:59
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"13:59
openstackMeeting ended Wed Jan  4 13:59:57 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tricircle/2017/tricircle.2017-01-04-13.01.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tricircle/2017/tricircle.2017-01-04-13.01.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tricircle/2017/tricircle.2017-01-04-13.01.log.html14:00
zhiyuanbye14:00
RongHui11bye14:00
joehuangbye14:00
dongfengbye14:00
JunSikbye14:00
Yipeibye14:00
*** Nakato has quit IRC14:00
*** Nakato has joined #openstack-meeting14:00
*** JunSik has quit IRC14:00
*** Yipei has quit IRC14:02
*** fanyishi has quit IRC14:03
*** tommylikehu_ has quit IRC14:04
*** joehuang has quit IRC14:05
*** sankarshan is now known as sankarshan_away14:05
*** reedip_outofmemo has joined #openstack-meeting14:06
*** yinxiulin has quit IRC14:09
*** baoli has joined #openstack-meeting14:09
*** pradk has quit IRC14:09
*** baoli has quit IRC14:09
*** eharney has joined #openstack-meeting14:10
*** baoli has joined #openstack-meeting14:10
*** bvandenh has joined #openstack-meeting14:10
*** tommylikehu_ has joined #openstack-meeting14:12
*** julim has joined #openstack-meeting14:12
*** zul has quit IRC14:14
*** zul has joined #openstack-meeting14:15
*** longxiongqiu has quit IRC14:17
*** salv-orlando has quit IRC14:17
*** salv-orlando has joined #openstack-meeting14:17
*** jamesdenton has joined #openstack-meeting14:19
*** hwoarang has quit IRC14:19
*** priteau has quit IRC14:19
*** hwoarang has joined #openstack-meeting14:20
*** kevinz has joined #openstack-meeting14:20
*** designbybeck has joined #openstack-meeting14:21
*** lblanchard has joined #openstack-meeting14:23
*** weshay_doctor is now known as weshay14:23
*** X-dark has joined #openstack-meeting14:25
*** ykatabam has quit IRC14:26
*** salv-orlando has quit IRC14:27
*** fguillot has joined #openstack-meeting14:27
*** rbartal has quit IRC14:32
*** bzhao_ has joined #openstack-meeting14:34
*** rbartal has joined #openstack-meeting14:35
*** kevinz has quit IRC14:36
*** kevinz has joined #openstack-meeting14:36
*** efried has joined #openstack-meeting14:40
*** mickeys has joined #openstack-meeting14:40
*** tommylikehu_ has quit IRC14:40
*** tommylikehu_ has joined #openstack-meeting14:41
*** ykatabam has joined #openstack-meeting14:41
*** ykatabam has quit IRC14:42
*** mickeys has quit IRC14:45
*** VW has joined #openstack-meeting14:45
*** cleong has joined #openstack-meeting14:46
*** jungleboyj has joined #openstack-meeting14:46
*** arxcruz has quit IRC14:47
*** kevinz has quit IRC14:47
*** kevinz has joined #openstack-meeting14:47
*** VW has quit IRC14:48
*** VW has joined #openstack-meeting14:48
*** bogdando has quit IRC14:50
*** kgiusti has joined #openstack-meeting14:50
*** Guest30234 has quit IRC14:51
*** baoli has quit IRC14:52
*** ansmith has joined #openstack-meeting14:52
*** liuzyu has quit IRC14:55
*** arxcruz has joined #openstack-meeting14:56
*** rbak has joined #openstack-meeting14:56
*** baoli has joined #openstack-meeting14:58
*** bogdando has joined #openstack-meeting14:58
*** fnaval has joined #openstack-meeting14:59
*** ricolin has joined #openstack-meeting14:59
*** paw has quit IRC14:59
*** msimonin has joined #openstack-meeting14:59
*** ad_rien__ has joined #openstack-meeting14:59
*** bobh_ has joined #openstack-meeting14:59
*** links has quit IRC14:59
*** ad_rien__ has quit IRC15:00
*** ntpttr__ has joined #openstack-meeting15:00
*** ad_rien_ has joined #openstack-meeting15:00
msimoninad_rien shoud come quickly15:00
msimoninshould*15:00
ad_rien_#startmeeting massively_distributed_clouds15:00
openstackMeeting started Wed Jan  4 15:00:36 2017 UTC and is due to finish in 60 minutes.  The chair is ad_rien_. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: massively_distributed_clouds)"15:00
openstackThe meeting name has been set to 'massively_distributed_clouds'15:00
ad_rien_#chair ad_rien_15:00
openstackCurrent chairs: ad_rien_15:00
msimonino/15:00
*** xyang1 has joined #openstack-meeting15:00
serverascodehi15:00
ad_rien_agenda15:00
ad_rien_#link https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 line 1515:01
ansmitho/15:01
*** ntpttr__ has quit IRC15:01
ad_rien_Hi folks15:01
*** ntpttr__ has joined #openstack-meeting15:01
ad_rien_To start, I wish you all the best for 2017 ;)15:01
*** foliveira has joined #openstack-meeting15:01
msimoninthanks ad_rien_ :)15:02
*** ntpttr__ has quit IRC15:02
denaitre_o/15:02
ad_rien_#topic previous meeting action items15:02
*** openstack changes topic to "previous meeting action items (Meeting topic: massively_distributed_clouds)"15:02
*** ntpttr__ has joined #openstack-meeting15:02
*** rcherrueau has joined #openstack-meeting15:02
HeleneCoullono/15:03
ad_rien_So regarding the last minute I cannot chair it unfortunately but I saw that you made few comments regarding the first slides we proposed15:03
ad_rien_Hi HeleneCoullon denaitre_15:03
*** Menthos has joined #openstack-meeting15:03
*** hongbin has joined #openstack-meeting15:03
ad_rien_I updated the slides in order to take into account the comments you made15:03
*** pradk has joined #openstack-meeting15:04
ad_rien_ansmith:  I saw that you proposed to clarify the AMQP bricks in order to make a distinction between RabbitMQ/QPID/ZeroMq…15:04
ad_rien_I just copied/pasted the slide and added a comment to ask you to update the figure according to the QPID bricks15:05
ansmithad_rein_: yes, the conversation was to have oslo.messaging be the service at the block level15:05
*** mriedem has joined #openstack-meeting15:05
ansmithand then show relationship to backend(s) at next level down15:05
ad_rien_#link https://docs.google.com/presentation/d/1jJFZejZqgYDxu5FX4K8g3I5zQ87afnjYI4VSRSuCQ6U/edit#slide=id.p15:05
*** baoli has quit IRC15:05
ad_rien_so if you go on the slides15:05
ad_rien_and you give a look at slides 2 and 3, you will see the comment.15:06
ad_rien_May I ask you to update Slide 3 for QPID15:06
ad_rien_?15:06
*** zhurong has quit IRC15:06
*** jungleboyj has quit IRC15:06
ansmithI will take the action to update the slide15:07
ad_rien_ok great15:07
ansmithad_rien_: are you ok if I introduce oslo.messaging client/server blocks?15:08
ad_rien_#action update slides for QPid and RabbitMQ15:08
*** VW has quit IRC15:08
ansmithand then show relation to rabbit/amqp/zmq backends?15:08
ad_rien_ansmith:  yes please feel free to propose a new slide15:08
*** Leom has joined #openstack-meeting15:08
*** baoli has joined #openstack-meeting15:08
ansmithad_rien_: perfect15:08
ad_rien_you folks from redhat are probably the best one to propose such a vision15:08
*** VW has joined #openstack-meeting15:09
ad_rien_ok15:09
*** corey_ has joined #openstack-meeting15:09
*** corey_ is now known as Guest4114715:09
*** ad_rien_1 has joined #openstack-meeting15:10
ad_rien_1or does anyone wants to add something on the current deployment scenarios we identified15:10
*** witek has joined #openstack-meeting15:10
ad_rien_1(sorry I'm facing network issues)15:10
*** GordonTX has joined #openstack-meeting15:10
ad_rien_1so the next topic is to try to identify the pros/cons on the different scenarios15:11
ad_rien_1Joe Huang added  a comment in that direction this morning15:11
*** jungleboyj has joined #openstack-meeting15:11
ad_rien_1#topic Identify pros/cons of the different approaches15:11
*** cleong has quit IRC15:11
*** wxy|_ has joined #openstack-meeting15:11
*** zz_dimtruck is now known as dimtruck15:12
*** yangyape_ has joined #openstack-meeting15:12
ad_rien_1So apart from the SPOF (single point of failure) of the current approach, do you see some issues ?15:12
*** armax_ has joined #openstack-meeting15:12
ad_rien_1From Inria, we are going to conduct performance experiments to identify network constraints in terms of latency/bandwidth15:13
*** VW has quit IRC15:13
*** wxy| has quit IRC15:13
*** yangyapeng has quit IRC15:13
*** armax has quit IRC15:13
*** armax_ is now known as armax15:13
ad_rien_1for example in Scenario 1 (the simplest one)15:13
*** VW has joined #openstack-meeting15:13
*** ad_rien_ has quit IRC15:13
ad_rien_1We would like to identify to what extent it is relevant from the network WAN constraint viewpoint.15:13
ad_rien_1That is, we would like to see whether the network can be a strong constraint that can prevent such a deployment15:14
ad_rien_1maybe latency issues, ....15:14
*** tongli has quit IRC15:14
ad_rien_1between nova-computes and services that are deployed on site 015:15
*** edtubill has joined #openstack-meeting15:15
*** kevinz has quit IRC15:15
msimoninLike trying to  find what are the minimum bandwidth and latency requirements to operate compute nodes far from core services ?15:15
ad_rien_1Exactly msimonin15:15
ad_rien_1It would be great to identify other experiments we can do to identify weaknesses or confirm advantages15:16
*** spzala has joined #openstack-meeting15:16
ad_rien_1so folks any idea?  ansmith? serverascode?15:16
*** stevejims has joined #openstack-meeting15:16
serverascodenothing from me, just lurking for now :)15:17
*** stevejims has left #openstack-meeting15:17
msimonin:)15:17
ansmithad_rien_1: quick question on scenario 1, is nova-compute to services via L2 or L3?15:17
ansmithe.g. any assumptions about openstack config15:17
ad_rien_1L3 I would say15:17
ad_rien_1since you go through the WAN15:18
msimoninI guess we'll first experiment using the same L2 segment and try to figure out how to go through L315:18
ad_rien_1msimonin:  can you elaborate please ?15:19
msimoninFrom the experimentation we'll first go on the same L2 segment with network constraints and then got over L3 in the next iteration15:20
msimoninjust suggesting :)15:20
ad_rien_1ok thanks15:20
msimoninansmith: is there any known deployment over L3 ?15:20
ad_rien_1Ok I took some notes on our pad15:20
ansmithad_rien_l: some stretch site models extend the l2, with l3, there may be more configuration to consider of openstack services15:21
ansmithad_rien_l: I don't have direct experience there15:21
ad_rien_1ansmith:  I tried to write down this in the pad15:22
ad_rien_1line 3515:22
msimoninansmith:  what services do you have in mind ?15:22
*** ijw has joined #openstack-meeting15:23
ansmithmsimonin: thinking more generally that if there is an "internal mgmt" subnet, that the openstack api and messaging services likely reside on it15:23
*** rbartal has quit IRC15:24
ansmithmsimonin: so if WAN is l2, everything should just "work"15:24
msimoninansmith: sure :)15:24
ad_rien_1so we have an action that is to identify lack of functionality according to the different scenario15:24
*** huanxuan_ has joined #openstack-meeting15:25
msimoninI guess here some feedback/experience from telecom network would be beneficial15:25
ad_rien_1How can we do that ?15:25
msimoninNobody from orange here ? : )15:25
*** Akis_ has quit IRC15:25
ad_rien_1I mean we can at Inria take one or two scenarios and try to identify functional limitations (before performing performance experiments) but we need some helps for other scenarios15:26
ad_rien_1That is the first possibility15:26
ad_rien_1The second is to try to prioritize the different scenarios and start by focusing on the most important/representative/relevant one ?15:26
ad_rien_1serverascode:  AFAIK, we did not finalize our choice in the telecom WG?15:26
ad_rien_1did you ?15:27
serverascodein terms of distributed clouds? no don't think we finalized anything15:27
ad_rien_1#action Identify functional needs/limitations for each scenario15:27
*** huanxuan has quit IRC15:27
ad_rien_1I mean in terms of what can be the minimal NFV deployment15:27
ad_rien_1?15:27
msimoninyes15:28
ad_rien_1By merging our effort we can probably progress faster15:28
*** claudiub has joined #openstack-meeting15:28
serverascodeah ok, no we haven't finalized anything, just agreed to start working on a document to define it15:28
ad_rien_1ok15:28
serverascodein terms of a "generic NFV platform based on OpenStack"15:28
ad_rien_1yepp15:28
*** ijw has quit IRC15:29
*** frickler has quit IRC15:29
*** Guest66666 has quit IRC15:29
ad_rien_1We met some folks form create-net during the cloudcom conference in december15:29
*** frickler has joined #openstack-meeting15:29
*** Guest66666 has joined #openstack-meeting15:29
ad_rien_1the guys investigate the scenario 1 (i.e. slide 0) in a context of edge computing15:29
*** absubram has joined #openstack-meeting15:30
ad_rien_1(i.e. they have a large cloud and few remote compute nodes).15:30
ad_rien_1For the moment, they only performed paper works15:30
ad_rien_1and told us that they are interested by following our progress. I hope they will join us. but once again, if we can combine our effort, it would be valuable for all of us15:30
ad_rien_1for Fog/Edge scenario 1 looks to be the simplest15:31
*** claudiub|2 has quit IRC15:31
ad_rien_1I do not know whether it makes sense for NFV operators15:31
*** baoli has quit IRC15:31
ad_rien_1ok so getting back to my initial question: how can we move forward. Can we sort the different scenarios?15:33
ad_rien_1and focus on the most important one?15:33
*** bvandenh has quit IRC15:33
ad_rien_1#action prioritize the different scenarios15:33
msimoninif some people are interested in scenario 1 we should start by this one15:34
ad_rien_1+115:34
msimonin=> compute far from core services15:34
*** paw has joined #openstack-meeting15:34
*** rbartal has joined #openstack-meeting15:34
ad_rien_1this will also enable the evaluation of other messaging solutions15:35
*** spotz_zzz is now known as spotz_15:35
ad_rien_1so let's focus on this first scenario. Is it ok for everyone?15:35
ansmith+115:35
ad_rien_1#info everyone agrees to start with scenario 115:36
kgiusti+115:36
msimonin:)15:36
ad_rien_1so let's move to the next topic15:37
*** jprovazn has joined #openstack-meeting15:37
ad_rien_1#topic ENOS status15:37
msimoninyeah !15:37
msimoninso15:37
ad_rien_1msimonin:  can you please briefly introduce what is ENOS and how it can be helpful to investigate the different scenarios ?15:37
ad_rien_1I give you 3 minutes :)15:37
msimoninthanks :)15:38
msimonin#link https://github.com/beyondtheclouds/enos15:38
msimoninwe've build a tool to evaluate openstack in various connfiguration and topology15:38
msimoninthere is a white paper somewhere15:38
msimoninlet me find the link15:38
*** Sukhdev has joined #openstack-meeting15:39
*** zhipengh has joined #openstack-meeting15:39
* msimonin searching :)15:39
msimonin#link https://hal.inria.fr/hal-01415522v215:39
msimoninfound it :)15:40
msimoninso we already made some scalability tests15:40
msimoninpresented at Barcelona15:40
msimoninand we plan to extend to support multiregion deployment as well as15:40
msimoninnetwork constraints enforcement15:40
*** zhipengh has left #openstack-meeting15:41
*** mickeys has joined #openstack-meeting15:41
msimoninso basically we'll be able to evaluate the different scenarios15:41
msimonin(hopefully :) )15:41
*** X-dark has quit IRC15:41
msimoninI think that's all for the overview ad_rien_1 :)15:41
ad_rien_1thanks15:41
ad_rien_1Just to complete, Scenario 1 can be evaluated, Scenario 2 is cells (for the moment we do not consider it as the cell v2 refactoring is under heavy development) and finally,  Scenarios 3 can be  evaluated. 15:42
ad_rien_1is it correct?15:42
msimoninyes15:42
ad_rien_1thanks15:42
ad_rien_1so the next step regarding ENOS is to investigate how we can deploy other messaging solutions such as QPiD15:43
*** rbak_ has joined #openstack-meeting15:43
*** salv-orlando has joined #openstack-meeting15:43
ad_rien_1ansmith:  kgiusti: are there ansible playbooks to deploy QPID ?15:43
*** huanxuan has joined #openstack-meeting15:43
ad_rien_1(actually ENOS is leveraging kolla and ansible)15:43
ansmithad_rien_l, msimonin: there is puppet module but ansible shouldnt take too much15:44
*** huanxuan_ has quit IRC15:44
msimonincould you link the puppet module ?15:44
*** jaugustine has joined #openstack-meeting15:45
ad_rien_1or even better, if you can provide some ansible playbooks if doing the port is not too time consuming ;) ?15:45
*** mickeys has quit IRC15:45
ansmithpuppet module reference in etherpad15:45
*** reedip_ has quit IRC15:45
msimoninansmith: ack15:45
ansmithad_rien_l: will assess ansible effort15:46
ad_rien_1thanks15:46
*** rbak has quit IRC15:46
ad_rien_1#action ansmith will give a look to ansible playbooks for QPID15:47
ad_rien_1is there any question regarding ENOS?15:47
*** salv-orlando has quit IRC15:48
ad_rien_1ok so let's move to the next topic15:48
ad_rien_1#topic expected capabilities for Massively distributed/Fog/Edge clouds15:48
ad_rien_1as I mentioned I was not chairing the last meeting15:48
msimoninLast time we started to discuss migration with someone from orange15:49
ad_rien_1so based on the logs it looks like this point was not sufficiently discussed15:49
ad_rien_1ok15:49
* ad_rien_1 is looking for the logs. 15:49
msimoninbut he seems not here today15:49
ad_rien_1#action do not forget to discuss about migration between remote sites with Orange folks15:50
ad_rien_1Can eveyone access the pad: https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 ?15:52
ad_rien_1#link https://etherpad.openstack.org/p/massively_distributed_ircmeetings_201715:52
ad_rien_1I just copied/pasted few ideas we have at Inria regarding this topic.15:52
ad_rien_1can you go through the notes and put +1 if you believe it makes sense.15:52
*** saisrikiran has joined #openstack-meeting15:54
ad_rien_1We have 5 minutes before ending the meeting?15:54
ad_rien_1any comments on the expected capabilities?15:54
ad_rien_1it seems not so I propose to switch to the last topic.15:55
*** caboucha has joined #openstack-meeting15:55
ad_rien_1and we will come back on this point later.15:55
ad_rien_1#topic Open Discussion15:55
ad_rien_1So from my side, just two remarks (already written in the pad)15:55
ad_rien_11./ We talked about folks from RedHat that are investigating Fog/Edge computing challenges.15:56
ad_rien_1ansmith:  kgiusti any chance to talk with them during one of our meetings?15:56
ad_rien_1I think it would be really great to exchange our point of views.15:56
*** viks has joined #openstack-meeting15:56
ansmithad_rien_l: I reached out to them prior to break and they were very interested, I will follow up15:57
*** sheel has quit IRC15:57
ad_rien_1#action ansmith will check whether other folks from redhat can participate to the WG.15:57
*** akuznetsov has joined #openstack-meeting15:57
ad_rien_1thanks ansmith15:57
ad_rien_1we can discuss my second point later15:57
ad_rien_1we have just two more minutes.15:58
ad_rien_1So I prefer to leave the floor to you guys15:58
*** zengchen has quit IRC15:58
ad_rien_1anything from your side ?15:58
serverascodenohting from me15:58
*** zengchen has joined #openstack-meeting15:58
ad_rien_1ok thanks for attending the meetinhg15:58
ad_rien_1talk to you in two weeks.15:59
ad_rien_1bye15:59
serverascodethanks!15:59
ad_rien_1#endmeeting15:59
ansmiththanks15:59
*** ad_rien_1 is now known as ad_rien_15:59
ad_rien_#endmeeting15:59
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"15:59
openstackMeeting ended Wed Jan  4 15:59:47 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/massively_distributed_clouds/2017/massively_distributed_clouds.2017-01-04-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/massively_distributed_clouds/2017/massively_distributed_clouds.2017-01-04-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/massively_distributed_clouds/2017/massively_distributed_clouds.2017-01-04-15.00.log.html15:59
*** sudipto has quit IRC16:00
*** sudipto_ has quit IRC16:00
*** msimonin has quit IRC16:00
*** TxGirlGeek has joined #openstack-meeting16:00
*** kgiusti has left #openstack-meeting16:00
*** mdovgal has joined #openstack-meeting16:00
*** tbarron has joined #openstack-meeting16:00
*** yamahata has joined #openstack-meeting16:01
*** witek has quit IRC16:01
*** diablo_rojo_phon has joined #openstack-meeting16:01
tommylikehu_happy new year :) but where is the host16:01
*** shamail has joined #openstack-meeting16:02
jungleboyjtommylikehu_: Happy New Year.16:02
smcginnis#startmeeting Cinder16:02
openstackMeeting started Wed Jan  4 16:02:18 2017 UTC and is due to finish in 60 minutes.  The chair is smcginnis. 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: Cinder)"16:02
openstackThe meeting name has been set to 'cinder'16:02
jungleboyjThere is the man!16:02
scottdahi16:02
vikshi all16:02
eharneyhi16:02
tommylikehu_hi all16:02
smcginnisSorry, I need a door on my cubicle. :)16:02
e0nehi16:02
*** cleong has joined #openstack-meeting16:02
smcginnisOr just work from home on Wednesdays...16:02
e0ne#link https://wiki.openstack.org/wiki/CinderMeetings#Next_meeting16:02
duleko/16:03
mdovgalhi16:03
diablo_rojo_phonHello :)16:03
jungleboyjsmcginnis: Working from home is the way to go.16:03
smcginnise0ne: Doesn't do much good to capture that in the logs since it's changed every week. :)16:03
rarorahi16:03
*** Guest41147 has quit IRC16:03
smcginnisjungleboyj: Especially when you have a ridiculously large monitor, right?16:03
xyang1hi16:03
jungleboyjsmcginnis: ;-)16:03
smcginnis#topic Announcements16:03
tommylikehu_maybe two16:03
*** openstack changes topic to "Announcements (Meeting topic: Cinder)"16:03
smcginnis#link https://etherpad.openstack.org/p/cinder-spec-review-tracking Review focus16:03
tbarronhi16:04
smcginnisI believe scottda has done more testing of the A/A patches. Would be nice to get those through.16:04
scottdayeah, I crashed by Devstack and need to restest.16:04
smcginnis#info Need to register for the PTG if you have not already done so16:04
scottdahopefully not caused by AA/HA :)16:04
smcginnis#link http://www.openstack.org/ptg PTG info and registration16:04
smcginnisscottda: Hah16:05
smcginnisPlease get registered for the PTG if you can.16:05
*** rcherrueau has quit IRC16:05
smcginnisWe need participation to make this useful.16:05
tommylikehu_smcginnis: wish so16:05
wxy|_hi16:05
smcginnistommylikehu_: Long trip for you. :)16:05
diablo_rojo_phonFinally getting to a good number of cinder folks.16:05
*** Menthos has left #openstack-meeting16:05
smcginnistommylikehu_: Would be great if you could make it though.16:05
smcginnisdiablo_rojo_phon: Oh good, do you know the numbers off hand?16:05
dulekgeguileo: How's rebasing of A/A stuff? You need any help there?16:05
tommylikehu_smcginnis:  thanks, I would like to have a try16:06
smcginnis#info Summit call for presentations is open16:06
smcginnis#link https://www.openstack.org/summit/boston-2017/call-for-presentations/ Summit CFP16:06
smcginnisIf you have any ideas for Summit topics, please submit them.16:07
smcginnis#info Need to start planning for the PTG16:07
smcginnis#link https://etherpad.openstack.org/p/ATL-cinder-ptg-planning PTG topic planning16:07
scottdasmcginnis: I put a placeholder in there for cinder-nova meeting...16:07
diablo_rojo_phonsmcginnis: not offhand but I can check the spreadsheet later and let you know.16:07
scottdasmcginnis: NOt sure about when that needs to happen, how to get a big room, etc16:08
tommylikehu_erlon here?16:08
scottdaI think there's some cross-project designated day or something?16:08
*** corey_ has joined #openstack-meeting16:08
diablo_rojo_phonscottda: no designated day.16:09
*** corey_ is now known as Guest4830916:09
* patrickeast sneaks in late16:09
*** cleong has quit IRC16:09
smcginnisscottda: From what I understand, there will be some space for ad hoc groups.16:09
scottdadiablo_rojo_phon: ok, cool. What about a big room?16:09
*** rcernin has quit IRC16:09
smcginnisscottda: We will have our dedicated rooms Wed-Fri16:09
dulekscottda: http://lists.openstack.org/pipermail/openstack-dev/2017-January/109608.html16:09
scottdasmcginnis: Well, we might have a smaller cinder-nova api meeting, That might work.16:09
smcginnisSo any and all PTG ideas, please add to that etherpad. We'll sort it out once we get closer.16:09
dulekscottda: here's ttx answer on that.16:10
scottdanot sure about how many from both teams are interested.16:10
*** saisrikiran has quit IRC16:10
diablo_rojo_phonscottda: yeah the rooms are kind of going to be scaled like how they were for the design summits.16:10
smcginnisscottda: Yeah, probably a small enough group that actually cares.16:10
dulekSmall announcement from me - since today Cinder's listed here: https://governance.openstack.org/tc/reference/tags/assert_supports-rolling-upgrade.html :)16:10
smcginnisdulek: +1 Nice to see that.16:10
*** nkrinner is now known as nkrinner_afk16:11
scottdadulek: thx16:11
smcginnis#topic APIs for encryption types16:11
*** openstack changes topic to "APIs for encryption types (Meeting topic: Cinder)"16:11
smcginnisNot sure who added this one, no nick listed16:11
scottdamaybe Steve Martinelli?16:11
smcginnisstevemar: Was this from you? ^^16:12
smcginnis#link https://bugs.launchpad.net/cinder/+bug/156204316:12
openstackLaunchpad bug 1562043 in Cinder "[api-ref]API doc reference missing "volume type encryption create"" [Medium,In progress] - Assigned to wangxiyuan (wangxiyuan)16:12
stevemaro/16:12
stevemaroh yeah16:12
stevemarthat was me, a while ago16:12
stevemari was trying to find them and got frustrated that they are not there16:12
smcginnisBeen two weeks, so it's hard to remember some times? :)16:12
stevemarthe bugs been opened for several months now16:12
smcginnisstevemar: Ah, we're just missing the api-ref?16:12
*** akuznetsov has quit IRC16:12
* jungleboyj hands stevemar a coffee16:13
eharneylooks like we just need to review https://review.openstack.org/#/c/415320/ ?16:13
stevemarsmcginnis: yes, i was looking here: http://developer.openstack.org/api-ref/block-storage/v2/index.html16:13
scottda#link https://review.openstack.org/#/c/415320/16:13
smcginnistabbed16:13
*** msimonin has joined #openstack-meeting16:13
smcginnisstevemar: Unfortunately, there's probably a lot more than that missing.16:13
stevemarsmcginnis: that makes me sad :(16:13
smcginnisWe added in-tree api-ref last release, but one person was doing it and they've moved on to another job.16:13
stevemarsmcginnis: do a sprint :P16:14
smcginnisstevemar: Yeah... on the list of things that need attention.16:14
wxy|_So is there any work list for Api ref?16:14
smcginniswxy|_: Not that I have or have seen.16:14
smcginniswxy|_: If that's something you are interested in, feel free to start an etherpad or something if you think it would help.16:14
smcginnisAny attention to the api-ref would be beneficial.16:14
*** rbartal has quit IRC16:15
stevemarits unfair to expect users to know internals of cinder to use an API, gotta doc it!16:15
smcginnisI think nova had some tool or something they were using to track progress on their api-ref work. Not sure though.16:15
smcginnisstevemar: Yes, definitely.16:15
stevemar(also the help and docstrings in cinderclient aren't much more helpful)16:15
*** HeleneCoullon has left #openstack-meeting16:15
smcginnisI think there are a few Cinder bugs filed for api-ref work that needs to be done. So if that interests anyone, they're out there.16:16
scottdastevemar: Thanks for keeping us on our toes.16:16
stevemarscottda: np :)16:16
smcginnisstevemar: Keeping us in line! :)16:16
jungleboyjsmcginnis: Is there a tag for that?16:16
scottdaI think it's [api-ref]16:16
smcginnisjungleboyj: mmmmm, maybe? :)16:16
smcginnisThat's in the title, but not sure if a tag has been set, at least on all of them.16:16
stevemarwe had the same issue in keystone (when we moved our APIs in-tree), we did a 2 day sprint near the end of the cycle, it worked really well16:16
smcginnisWill try to make sure it is next time I do a pass through them.16:17
*** msimonin1 has joined #openstack-meeting16:17
*** msimonin has quit IRC16:17
*** winston-d has joined #openstack-meeting16:17
stevemarit was all doc'ed here: https://etherpad.openstack.org/p/keystone-api-sprint16:17
jungleboyj:-)  Sounds like a good idea.16:17
smcginnisstevemar: Good tip. That sounds like something good to do closer to the end of a cycle.16:17
smcginnisstevemar: Nice, thanks!16:17
stevemaranyway, i'll step off my soapbox now16:17
jungleboyjstevemar: Are you becoming a Cinder guy?16:18
smcginnisstevemar: While you're up, want to do a quick mention for the driver maintainers?16:18
smcginnisjungleboyj: We're forcing him to be by not having good docs. ;)16:18
jungleboyjsmcginnis: Ah, so that is our hidden agenda.  Cool.16:18
stevemaroh sure16:19
smcginnisWe're sneaky like that.16:19
stevemarso, i had another ask16:19
*** pabelanger has quit IRC16:19
*** pabelanger has joined #openstack-meeting16:19
stevemarthe TC is doing some work around drivers, smcginnis has been keeping up to date on it16:20
*** sdague_ has joined #openstack-meeting16:20
stevemari can't find the ML post atm...16:20
*** huanxuan_ has joined #openstack-meeting16:20
stevemarbut is anyone interested in helping us out here? we're looking to talk to a few cinder driver maintainers16:20
*** kjorgensen has joined #openstack-meeting16:21
stevemarthe TC wants to make sure we're asking the right questions and proposing solutions that'll help driver maintainers16:21
smcginnisMight be this one: http://lists.openstack.org/pipermail/openstack-dev/2016-December/108410.html16:21
stevemarthanks smcginnis!16:21
jungleboyjstevemar: I will put the call out to our internal driver maintainers.16:22
jungleboyjHave them contact you?16:22
*** ntpttr__ has quit IRC16:22
stevemarjungleboyj: just shoot me their email and name16:22
jungleboyjstevemar: Can do buddy.16:22
*** msimonin1 has quit IRC16:22
stevemardo driver maintainers normally not attend the meeting?16:22
*** kjorgens_ has joined #openstack-meeting16:22
*** ijw has joined #openstack-meeting16:22
tommylikehu_yes maybe16:23
*** huanxuan has quit IRC16:23
smcginnisstevemar: Many do, but some companies have a different set of driver maintainers.16:23
scottdastevemar: Attendance is a bit light today...16:23
jungleboyjstevemar: Some do, but for IBM most of them are Asia, so not a good time.16:23
stevemarah16:23
stevemarvarious reasons16:23
*** nadya has quit IRC16:23
stevemarcool16:23
smcginnis#action Driver maintainers contact stevemar to get involved in driver team discussion16:23
stevemarany suggestions for names i can poke? from the esteemed core team? :)16:23
smcginnisstevemar: Hopefully the mention in here will get read in the meeting logs and get some activity16:24
xyang1stevemar: I'd be interested in talking to you about this, do you need my email?16:24
*** msimonin has joined #openstack-meeting16:24
tommylikehu_stevemar: maybe you can leave your email here16:24
*** neiljerram has quit IRC16:24
tommylikehu_the guys could check this log and contact you later16:24
stevemarsure, folks can reach me at s.martinelli@gmail.com or send me a PM16:24
tommylikehu_stevemar: thanks16:25
stevemarneutron has a "lieutenant" list of drivers: http://docs.openstack.org/developer/neutron/policies/neutron-teams.html#core-review-hierarchy16:25
smcginnisstevemar: Now the spam bots have you. ;)16:25
*** neiljerram has joined #openstack-meeting16:25
stevemar(if you scroll down a bit)16:25
tommylikehu_lol16:25
*** kjorgensen has quit IRC16:26
stevemarok, now i'm really done :P16:26
smcginnisstevemar: Thanks!16:26
smcginnis#topic Reset-status for all resources with single command in Cinder-client and OSC16:26
*** openstack changes topic to "Reset-status for all resources with single command in Cinder-client and OSC (Meeting topic: Cinder)"16:26
tommylikehu_great, I add this topic for eharney16:26
smcginniseharney and tommylikehu_: Take er away16:26
tommylikehu_eharney: here?16:26
eharneyyep16:26
*** guoshan has joined #openstack-meeting16:27
tommylikehu_I think the idea comes from eharney16:27
smcginnis#link https://review.openstack.org/#/c/413156/ Proposed approach16:27
*** ijw has quit IRC16:27
tommylikehu_and  it's about reset different resource's status with single command16:28
smcginnisSo the idea is rather than adding reset commands for everything, just have one general command that can be pointed at whatever needs to be reset?16:28
eharneyfor context, the start here is that i voted against adding group-reset-state and group-snapshot-reset-state to the cinder CLI16:28
eharneyfor a couple of reasons16:28
tommylikehu_smcginnis:  right16:28
eharney1) we don't need a CLI full of X reset-state commands, one for every resource, IMO, because it's a lot of clutter16:29
eharney2) copying the way we do reset-state now is not a good plan because what we do now is not really a great design16:29
e0neeharney: I like this idea16:29
eharneyand i'd rather fix it rather than propagate it further16:29
scottda(we've 3 *reset* commands now, and are proposing adding 2 more)16:29
scottdaeharney: +116:29
tommylikehu_scottda: yeah16:29
*** unicell has quit IRC16:29
eharneyif we move to a new command, we can smoothly fix the other issues with the current scheme16:30
eharneysuch as the fact that it defaults to "available" which IMO is rarely a safe choice16:30
bswartzwhat's the downside of collapsing it all down to 1 command?16:30
*** tonytan4ever has joined #openstack-meeting16:30
tommylikehu_bswartz: it could be ugly maybe16:30
scottdaOr it could be beautiful16:30
scottda:)16:30
eharneybswartz: the only argument really presented against it so far was kind of "we do it in one command in osc, but in cinder CLI we already do this, so let's keep doing it the current way"16:31
tommylikehu_sorry maybe different from others16:31
eharneywhich IMO is not really much of an argument16:31
jungleboyjeharney: I think that makes sense.  Not add additional commands and set things up so that it is easier to fix in the future.16:31
bswartzI lean in favor of this16:31
smcginniseharney: I haven't looked at that patch, but is that working? Or needs more work?16:31
scottdaIt's going to need a spec. What will the API look like? Will we have a ResetManager?16:32
xyang1eharney: can you get it done in Ocata?16:32
eharneysmcginnis: it works for volume and snap16:32
tommylikehu_we are gathering more response and then take the steps16:32
*** guoshan has quit IRC16:32
scottdaOr maybe no spec? What do people think?16:32
smcginniseharney: So it would just need a little more work to add other object support? Seems worth spending a little more time on.16:32
eharneyi'm also concerned about whether we are relying on reset-state too much in general rather than making things work in a way where it isn't needed so often16:33
eharneysmcginnis: right16:33
winston-dfor the case to reset a volume that is 'in-use' to 'available' (or the other way around), we need reset-state API to be able to deal with not just 'status' field.16:33
dulekwinston-d: Yup, same with migration status.16:33
smcginnisscottda: Good question. I'm kind of on the fence on a spec. Could be useful to document what's being done, but could also be overkill.16:33
jungleboyjeharney: Madness!16:33
scottdaWell, this is ultimately about an admin API to change the DB....16:33
smcginniswinston-d: Good point. Maybe a spec is needed to flesh out some of these details.16:33
eharneyi don't mind writing specs if people agree on the general direction16:34
tommylikehu_Only the clients are involovd in this?16:34
scottdaI agree with eharney that ideally we would fix thing to prevent bad state, but that's been a bit hard.16:34
smcginniseharney: I tentatively agree with the general direction. :)16:35
scottdaWe got pushback from nova for this 2 years ago, and we're still trying to fix the api...16:35
eharneyscottda: well, we keep not doing things we could be doing to avoid it.  like using async error messages rather than the pattern of "leave the object in error_X and ask the admin to reset it"16:35
winston-ddulek: yeah, so basically it shouls support almost every status-like filed for different resources.16:35
winston-dDesigning such a able can be challenging.16:36
scottdaI think it's better to design it right, and take our time.16:36
eharneyreset-state already deals with attach status, it can be made to deal w/ migration status too16:36
smcginnisscottda: That;s crazy talk.16:36
scottdaIf we start the spec now, we can beat on it at PTG and have something in Pike16:37
smcginnisGood call.16:37
tommylikehu_scottda:  sounds great16:37
jungleboyjMy two cents are that we need to eventually get the problems that lead to the need for these resolved.16:37
winston-d+116:37
jungleboyjIn the short term though, getting a good solution for reset-state is desirable.16:37
smcginnisjungleboyj: +116:37
*** jchhatbar_ has quit IRC16:37
scottdaYeah, but sh*&t happens, and we'll always need a tool.16:37
jungleboyjscottda: Exactly.16:38
winston-dscottda: SQL16:38
smcginnisI don't know if we can ever get rid of the root causes, but worth making things more robust.16:38
winston-d:)16:38
smcginniswinston-d: ;)16:38
jungleboyjscottda: So lets make the tool decent.  :-)16:38
eharneywe can certainly stop adding new root causes16:38
jungleboyjsmcginnis: +116:38
jungleboyjeharney: Madness again!16:38
tommylikehu_eharney: :)16:38
eharneyi -1'd a spec this morning on revert to snapshot because it wanted to add a new state of "error_reverting"... this is the design trap we tend to go toward by default16:38
tommylikehu_eharney: I gonna check this16:39
smcginnisIf things get to the point where it's rare enough, SQL is probably OK. But until then, I think having a decent tool to help admins with this is worth it.16:39
scottdaNot every admin can access the DB directly with SQL16:39
eharneySQL isn't good enough because then people will break things like resetting the volume status and not the attachment status16:39
scottdaAccessing production DB is generally bad...16:39
jungleboyjscottda: +116:40
smcginnisYeah, only if it's a very, very rare occurence. If that's ever possible.16:40
scottdaAnd I have done it countless times :)16:40
scottdacause sh*!t breaks.16:40
winston-dyeah, and schema change is nightmare for SQL based tool16:40
smcginniseharney: So spec then?16:41
eharneysmcginnis: i guess, i'll start with the proposed CLI ideas and see what else ends up in there16:41
scottdaspec +116:41
smcginniseharney: Thanks. Might be good to add to here too: https://etherpad.openstack.org/p/ATL-cinder-ptg-planning16:41
smcginniseharney: Would be nice to have a high bandwidth discussion on things.16:41
eharneysure16:42
tommylikehu_smcginnis, eharney thanks16:42
smcginniseharney, tommylikehu_: Thanks! Anything else on this topic?16:42
smcginnis#topic Open Discussion16:43
*** openstack changes topic to "Open Discussion (Meeting topic: Cinder)"16:43
smcginnisAnything else?16:43
smcginnisDid we get a netsplit or something?16:43
tommylikehu_no16:43
* jungleboyj waves16:43
scottdano16:43
smcginnis:)16:44
winston-dstill here16:44
*** sdake has quit IRC16:44
eharneyhttps://review.openstack.org/#/c/337814/ would really like some more reviews16:44
smcginnistabbed16:44
smcginnisOh, another reminder, non-client lib deadline is in two weeks.16:44
tommylikehu_O-316:45
smcginnisSo if you are working on anything in os-brick, or have anything you know we need to get through, nows the time to push that.16:45
*** mickeys_ has joined #openstack-meeting16:45
smcginnistommylikehu_: non-client library freeze is before o-316:45
tommylikehu_smcginnis: ok~16:45
smcginnistommylikehu_: Gives a little time to make sure there are dependency issues before the bigger freeze.16:45
smcginnis#link https://releases.openstack.org/ocata/schedule.html Ocata schedule16:46
eharneywe landed some os-brick stable/newton fixes.  i/we need to cycle through those again and see about doing a release there, i suppose16:46
smcginniseharney: Or can we just raise Newton upper constraints to use the newer lib?16:46
smcginnisI don't think we could do that with Mitaka since we added privsep, but I think we should be able to now.16:46
smcginnisThough probably doesn't hurt to just do a stable release.16:47
eharneysmcginnis: well we already merged them into stable, might as well cut a release16:47
smcginniseharney: True16:47
tommylikehu_smcginnis:  any reminder about the drivers's deprecation strategy16:47
eharneyfor those people who actually "use" this code that i'm always hearing about :)16:47
smcginniseharney: :)16:47
smcginnistommylikehu_: Good point.16:47
smcginnisThere are a few remaining patches marking drivers as unsupported.16:47
smcginnisAnd a few went through already.16:48
scottdaYeah, looks like a lot of driver unsupported patches that just need +A16:48
smcginnisIf we get CI stable on those before RC1, I think we can revert those.16:48
tommylikehu_smcginnis:  great16:48
smcginnisOtherwise, some queued up for removal in Pike.16:48
smcginnisIf it comes to that.16:48
smcginnishttps://review.openstack.org/#/q/status:open+project:openstack/cinder+branch:master+topic:ci_unsupported16:48
smcginnisOpen reviews ^^16:48
eharneyany thoughts on NFS snapshots?  i still owe erlon some testing there but it hasn't seen any other review lately16:49
smcginniseharney: I've kind of been waiting for that to shake out. If it's ready, I would like to get that pushed through.16:49
*** lhx__ has quit IRC16:49
smcginnisThe one question I had there is any impact with drivers that build on top of the NFS driver.16:49
*** huanxuan_ has quit IRC16:50
eharneyi don't know of anything really worrying there, but it's been a while since i've looked at it really closely16:51
jungleboyjeharney: *Sigh* I have been wanting to play with those but been in turmoil lately.  :-)16:52
smcginniseharney: I'm sure we'll find out eventually. Really won't be in any worse shape than we are now, so I don't think anything needs to be held back by it.16:52
jungleboyjI will see if I can play with the latest patches.16:52
eharneyjungleboyj: cool16:52
jungleboyjsmcginnis: +216:52
*** ad_rien_ has quit IRC16:52
vikshi, minor topic, can this be merged now https://review.openstack.org/#/c/378105/? Sry to bring it again. Trying to save one more merge conflict16:52
smcginnisviks: I'll take a look later. Got it open in a tab now. Hopefully should be good now.16:53
vikscorrect link is https://review.openstack.org/#/c/378105/16:53
viksthanks16:53
smcginnisOK, anything else for the meeting?16:53
smcginnisOK, thanks everyone!16:54
jungleboyjThanks smcginnis !16:54
smcginnis#endmeeting16:54
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"16:54
openstackMeeting ended Wed Jan  4 16:54:34 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2017/cinder.2017-01-04-16.02.html16:54
viksbye all16:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2017/cinder.2017-01-04-16.02.txt16:54
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2017/cinder.2017-01-04-16.02.log.html16:54
jungleboyjAsta la vista baby!16:54
smcginnis:)16:54
winston-dbye16:56
*** X-dark has joined #openstack-meeting16:56
jungleboyjBye.16:56
*** ijw has joined #openstack-meeting16:56
*** winston-d has left #openstack-meeting16:57
*** tommylikehu_ has quit IRC16:57
*** tbarron has left #openstack-meeting16:59
*** viks has quit IRC17:01
*** qpqp has joined #openstack-meeting17:02
*** salv-orlando has joined #openstack-meeting17:04
*** bzhao_ has quit IRC17:04
*** hashar has quit IRC17:05
*** ijw has quit IRC17:06
*** sdake has joined #openstack-meeting17:08
*** ricolin has quit IRC17:08
*** jaugustine has quit IRC17:10
*** VW has quit IRC17:10
*** VW has joined #openstack-meeting17:11
*** sdake has quit IRC17:13
*** paw has quit IRC17:14
*** JoseMello has joined #openstack-meeting17:14
*** wxy|_ has quit IRC17:14
*** ijw has joined #openstack-meeting17:15
*** paw has joined #openstack-meeting17:16
*** VW has quit IRC17:16
*** shamail has quit IRC17:16
*** msimonin has quit IRC17:17
*** msimonin has joined #openstack-meeting17:17
*** msimonin has quit IRC17:17
*** msimonin has joined #openstack-meeting17:18
*** msimonin has quit IRC17:18
*** msimonin has joined #openstack-meeting17:18
*** msimonin has quit IRC17:18
*** msimonin has joined #openstack-meeting17:18
*** tesseract has quit IRC17:21
*** VW has joined #openstack-meeting17:22
*** msimonin has quit IRC17:22
*** ijw has quit IRC17:23
*** 09SAAA525 has joined #openstack-meeting17:25
*** msimonin has joined #openstack-meeting17:25
*** rasca has quit IRC17:28
*** sdague_ has quit IRC17:30
*** e0ne has quit IRC17:31
*** matrohon has quit IRC17:31
*** ad_rien_ has joined #openstack-meeting17:32
*** 09SAAA525 has quit IRC17:33
*** reedip_outofmemo has quit IRC17:33
*** lpetrut has quit IRC17:34
*** weshay is now known as weshay_lunch17:35
*** Swami has joined #openstack-meeting17:39
*** sdague has quit IRC17:39
*** Guest48309 has quit IRC17:40
*** cleong has joined #openstack-meeting17:40
*** paw has quit IRC17:41
*** ntpttr__ has joined #openstack-meeting17:42
*** ijw has joined #openstack-meeting17:44
*** baoli has joined #openstack-meeting17:45
*** ijw has quit IRC17:45
*** msimonin has quit IRC17:46
*** Leom has quit IRC17:47
*** paw has joined #openstack-meeting17:48
*** VW_ has joined #openstack-meeting17:48
*** VW_ has quit IRC17:49
*** VW_ has joined #openstack-meeting17:49
*** VW has quit IRC17:51
*** ad_rien_ has quit IRC17:51
*** yamahata has quit IRC17:54
*** designbybeck has quit IRC17:54
*** alraddarla_ has joined #openstack-meeting17:56
*** nadya has joined #openstack-meeting17:57
*** kjorgens_ has quit IRC17:57
*** bh526r has joined #openstack-meeting17:58
bh526r#startmeeting gluon18:00
openstackMeeting started Wed Jan  4 18:00:07 2017 UTC and is due to finish in 60 minutes.  The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: gluon)"18:00
openstackThe meeting name has been set to 'gluon'18:00
pcarverhello18:00
bh526r#topic Roll Call18:00
*** openstack changes topic to "Roll Call (Meeting topic: gluon)"18:00
bh526rHi Paul, happy new year18:00
bh526r#info Bin Hu18:00
pcarversame to you18:00
pcarver#info Paul Carver18:00
bh526rlooks like only you and I now18:01
*** Sukhdev has quit IRC18:01
*** Uri_ has joined #openstack-meeting18:01
pcarveryup, maybe so18:02
alraddarla_#info Darla Ahlert18:02
*** Sukhdev has joined #openstack-meeting18:02
alraddarla_I'm here too :)18:02
bh526rHi Darla, happy new year18:02
pcarverhi Darla18:02
alraddarla_hello! Happy new year!18:02
kamal___#info Kamal Hussain18:02
kamal___happy new year all!18:02
bh526rHi Kamal, happy new year18:02
kamal___thanks18:03
jinliHappy New Year !18:03
jinli#info JinLi18:03
bh526rHappy new year Jin18:03
*** bobmel has joined #openstack-meeting18:04
bh526r#topic Admin Update18:04
*** openstack changes topic to "Admin Update (Meeting topic: gluon)"18:04
bh526rLooks like many groups are planning PTG meeting in the end of February18:05
bh526rI communicated with Thierry from Foundation regarding those logistics in PTG, especially room assignment18:05
bh526rThe situation is that the PTG is organized around team rooms rather than around individual sessions.18:06
*** rob_tao has joined #openstack-meeting18:06
*** fzdarsky is now known as fzdarsky|afk18:06
*** dprince has quit IRC18:06
bh526rFoundation will publish an event map, rather than an event schedule.18:06
*** tonytan4ever has quit IRC18:07
bh526rBecause Foundation offers full rooms to teams (for multiple days), only official projects can get a full room assigned at the PTG.18:07
*** tonytan4ever has joined #openstack-meeting18:07
bh526rRegarding unofficial projects like us, there are lots of hallway / lunch space that can be reused for discussions around other projects or not-yet-official initiatives.18:08
tomhambleton#info Tom Hambleton18:08
bh526rSo they won't appear as a "room" on the event maps.18:08
bh526rIn a word, unofficial projects won't get a room in PTG. If we want to meet in PTG, we only can reuse hallway/lunch space18:09
bh526rSo that's the information I got so far for PTG18:10
bh526r#info Many groups are planning PTG meeting in the end of February18:11
bh526r#info Bin communicated with Thierry from Foundation regarding those logistics in PTG, especially room assignment18:11
Uri_sorry for the ignorance, PTG???18:11
*** iyamahat has joined #openstack-meeting18:11
bh526rProject Team Gathering18:12
*** nadya has quit IRC18:12
pcarverhttps://www.openstack.org/ptg/18:12
bh526rIt used to be design summit. Now it is a separate event PTG.18:12
*** jaugustine has joined #openstack-meeting18:12
Uri_thx18:12
bh526r#info The situation is that the PTG is organized around team rooms rather than around individual sessions.18:12
bh526r#info Foundation will publish an event map, rather than an event schedule.18:12
bh526r#info Because Foundation offers full rooms to teams (for multiple days), only official projects can get a full room assigned at the PTG.18:13
bh526r#info Regarding unofficial projects like us, there are lots of hallway / lunch space that can be reused for discussions around other projects or not-yet-official initiatives.18:13
*** efried has quit IRC18:13
bh526r#info In a word, unofficial projects won't get a room in PTG. If we want to meet in PTG, we only can reuse hallway/lunch space18:13
alraddarla_Is anyone planning on going to PTG?18:14
*** tonytan4ever has quit IRC18:14
bh526rLet us think about the strategy to best use PTG18:14
*** tonytan4ever has joined #openstack-meeting18:15
bh526rIan is working on those Gluon patches in Nova, and potentially in Neutron18:15
pcarverI'm planning to put in a travel request to go to the PTG. No idea yet on whether it's likely to be approved.18:15
bh526rSo he needs to go to PTG. But let me communicate with him to make sure he is going to.18:16
bh526rIan's presence is critical, in my view18:16
bh526rso that he can work with Nova and Neutron team there to get our patch/BP move forward18:17
*** jaugustine has quit IRC18:17
bh526rBecause we won't have a room there, only hallway/lunch space ca be reused, it may not be practical to have a formal Gluon team meeting there.18:18
*** weshay_lunch is now known as weshay18:18
rob_taoI wonder if Gluon guys or others can just sit in the room of an official project, for example, Nova? If yes it would be helpful if some of us are there imho18:18
*** ntpttr__ has quit IRC18:18
bh526rThat's an unfortunate reality18:18
bh526rThat's right. Instead of Gluon team meeting, our critical mass, such as Ian, need to be in Nova and Neutron's room to work on our topics with Nova and Neutron.18:19
*** toscalix has quit IRC18:19
*** dprince has joined #openstack-meeting18:20
*** VW_ has quit IRC18:20
*** Leom has joined #openstack-meeting18:20
bh526rSo whoever plans to go to PTG, that's the major goal.18:20
*** lblanchard has quit IRC18:21
*** iyamahat has quit IRC18:21
*** VW has joined #openstack-meeting18:22
bh526r#info So everyone is encouraged to think about the best way of working in PTG, and either plan to go to PTG and work with Nova and Neutron on Gluon topics, or stay in back office to get our work done.18:22
*** VW has joined #openstack-meeting18:23
*** GordonTX has quit IRC18:23
bh526r#info Bin will take an action to communicate with Ian and convince him to go.18:23
bh526rany other thoughts?18:24
*** gagehugo has joined #openstack-meeting18:25
pcarverIf my travel request is approved I expect to spend time working with the Neutron team on sub-projects, but would also join in any Gluon discussions that happen to take place ad hoc18:25
bh526rThat's great Paul. Thank you18:26
*** iyamahat has joined #openstack-meeting18:26
pcarverIt's probably not worth travelling for anyone who is strictly working on Gluon and isn't following activies ongoing in one or more of the official OpenStack projects.18:26
*** Uri_ has quit IRC18:27
bh526rI didn't send travel request for PTG, because under this situation, my presence there may not make a significant difference. So I would rather save some money. But Ian is critical.18:28
*** lblanchard has joined #openstack-meeting18:28
bh526rok, let's move on to other topics18:29
*** lpetrut has joined #openstack-meeting18:29
bh526r#topic Gluon Tasks18:29
*** openstack changes topic to "Gluon Tasks (Meeting topic: gluon)"18:29
*** jaugustine has joined #openstack-meeting18:29
bh526rroutine record here18:29
bh526r#Info Ocata Tasks18:30
bh526r#link https://wiki.openstack.org/wiki/Gluon/Tasks-Ocata18:30
*** nadya has joined #openstack-meeting18:30
bh526r#link https://etherpad.openstack.org/p/ocata-gluon-work-plan18:30
bh526r#link https://etherpad.openstack.org/p/ocata-nova-neutron-session18:30
*** acoles is now known as acoles_18:31
bh526r#topic Status Update18:31
*** openstack changes topic to "Status Update (Meeting topic: gluon)"18:31
bh526r#info 1. Authentication and Access Control18:32
bh526r#link https://review.openstack.org/#/c/411000/18:32
*** yamahata has joined #openstack-meeting18:32
bh526r#info Patch 411000 was merged after our last discussion on Dec 2118:32
bh526r#info 2. OpenContrail's Mechanism Driver18:33
bh526r#link https://review.openstack.org/#/c/402071/18:33
bh526r#info Pending on Juniper's new repo, and then update of instruction18:33
bh526r#info 3. Testing18:34
bh526r#link https://review.openstack.org/#/c/405689/18:34
kamal___I am also working on more changes for the access control18:34
bh526r#info Kamal is also working on fine tuning and polishing etc. more changes of access control18:34
bh526r#info 405689 Jenkins failed. Georg and Darla had comments18:35
jinliI am still working on that one18:35
bh526r#info Jin is continuing working on it18:36
bh526r#info 4. Shim Layer for Open Daylight18:36
bh526r#link https://review.openstack.org/#/c/413011/18:36
*** sdake has joined #openstack-meeting18:36
tomhambletonI am still reviewing it.  I have a few issues with it but overall it looks good18:37
bh526r#info We discussed it on Dec 21. It looks good. The pending action is how to handle a prior patch 40738818:37
bh526r#info We generally agreed that 407388 should be abandoned on Dec 2118:38
*** unicell has joined #openstack-meeting18:38
*** Leom_ has joined #openstack-meeting18:39
bh526r#info Because Georg and Niko are still on vacation, we can wait for them to come back then formally abandon 407388.18:39
bh526r#info Meanwhile, Tom will continue to review 413011.18:39
*** ijw has joined #openstack-meeting18:39
bh526r#info All are also encouraged to continue to review 413011, and post comments there18:40
*** spzala has quit IRC18:40
bh526r#info 5. Gluon API Specification18:41
*** kjorgensen has joined #openstack-meeting18:41
bh526r#link https://review.openstack.org/#/c/411918/18:41
*** spzala has joined #openstack-meeting18:41
bh526r#info Tom has done a great job, and also addressed many comments18:41
*** Leom has quit IRC18:42
tomhambletonI am getting some good feedback on this spec.  Hopefully we can get this approved in a week or so18:42
bh526rPaul - you also just posted some comments before the meeting18:42
bh526rPerhaps you can share some here with Tom too?18:42
pcarversure, I just had a few questions on things that weren't completely clear18:43
*** Leom_ has quit IRC18:43
pcarverI think it looks good overall18:43
*** spzala has quit IRC18:44
*** spzala has joined #openstack-meeting18:44
pcarverI think a few more examples would be helpful to clarify some of the bits that weren't entirely clear.18:44
*** ijw has quit IRC18:44
tomhambletonWill do,  I will process all of your comments18:44
bh526rGreat, thank you both Paul and Tom18:44
bh526r#info 5. Bug Fixes18:45
bh526r#link https://review.openstack.org/#/c/413307/18:45
pcarverI'm planning to attempt to describe the current networking-sfc API and the Contrail SFC API in YAML18:45
bh526r#info this was approved and merged after our last meeting on Dec 2118:45
*** yamahata has quit IRC18:46
bh526rThat is awesome, Paul.18:46
bh526r#info 7. Devstack Integration (Work in Progress)18:47
*** yamahata has joined #openstack-meeting18:47
bh526r#link https://review.openstack.org/#/c/404069/18:47
bh526r#info Ian is still working on it18:47
*** sk1pp has joined #openstack-meeting18:47
bh526r#info 8. Add Entry Points to our Neutron Plugin (Work in Progress)18:47
bh526r#link https://review.openstack.org/#/c/404390/18:48
bh526r#info Ian is still working on it18:48
*** galstrom_zzz is now known as galstrom18:48
bh526r#info 9. Nova Enhancement (Work in Progress)18:48
bh526r#info This is what Ian is working with John in Nova team18:48
*** jaugustine has quit IRC18:48
bh526r#link https://review.openstack.org/#/c/390513/18:49
*** jaugustine has joined #openstack-meeting18:49
bh526r#info Most recent comments were on Dec 1318:49
bh526r#info On Jan 3, Nova PTL Matt suggested "This has to be moved to the nova/specs/pike/approved directory as ocata is closed for new specs."18:50
bh526r#info So Ian will take action to continue it in Pike cycle.18:51
bh526r#topic AOB18:51
*** openstack changes topic to "AOB (Meeting topic: gluon)"18:51
bh526rThat's all of the update. Anything else to discuss?18:52
*** pcaruana has quit IRC18:52
*** s3wong has joined #openstack-meeting18:52
rob_taoI would like to take this opportunity to bring up the multi-site setup for lab/future demo we talked about.  One Question I have for your guys: what should be used for the underlay encapsulation(GRE/MPLS/or...) between sites? Can we determine one only?18:52
*** sdague has joined #openstack-meeting18:52
*** kjorgens_ has joined #openstack-meeting18:52
*** jaugustine has quit IRC18:53
tomhambletonMPLSoGRE18:53
tomhambletonThat is what we did before18:54
*** sdake has quit IRC18:54
rob_taoWill it be used by all? ideally it is the case18:54
*** vishnoianil has quit IRC18:55
rob_taoAnything on the Gluon lab status?18:55
bh526rWe can ask Georg once he is back from vacation next week18:55
*** zara_the_lemur__ has joined #openstack-meeting18:56
rob_taook then. thanks to all18:56
bh526ranything else?18:56
bh526rThank you Robert18:56
*** kjorgensen has quit IRC18:56
bh526rIf nothing else, let's adjourn the meeting18:57
bh526r#info Meeting adjourned18:57
bh526r#endmeeting18:57
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"18:57
tomhambletonBye all!18:57
openstackMeeting ended Wed Jan  4 18:57:23 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gluon/2017/gluon.2017-01-04-18.00.html18:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gluon/2017/gluon.2017-01-04-18.00.txt18:57
openstackLog:            http://eavesdrop.openstack.org/meetings/gluon/2017/gluon.2017-01-04-18.00.log.html18:57
bh526rThank you everyone and bye all18:57
*** alraddarla_ has left #openstack-meeting18:58
kamal___bye all18:59
*** anilvenkata has quit IRC18:59
zara_the_lemur__anybody around for the... *drumroll* ... storyboard meeting?19:00
*** spzala has quit IRC19:01
zara_the_lemur__SotK is unwell today, hope he feels better soon19:01
betherlyo/19:01
betherlyHallo!19:01
zara_the_lemur__hi, betherly!19:01
zara_the_lemur__okay, we'll start, then!19:02
zara_the_lemur__#startmeeting storyboard19:02
openstackMeeting started Wed Jan  4 19:02:08 2017 UTC and is due to finish in 60 minutes.  The chair is zara_the_lemur__. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: storyboard)"19:02
openstackThe meeting name has been set to 'storyboard'19:02
zara_the_lemur__#topic Announcements19:02
*** openstack changes topic to "Announcements (Meeting topic: storyboard)"19:02
zara_the_lemur__I have nothing listed19:02
zara_the_lemur__HOWEVER19:02
zara_the_lemur__SotK's patch to list teams that can access private stories has finally gone in!19:03
zara_the_lemur__so this means that you no longer need to list who can view a private story user-by-user19:03
*** rbudden has joined #openstack-meeting19:03
diablo_rojo_phonHello :)19:03
zara_the_lemur__but can make a team once, and then give that team access wherever19:03
zara_the_lemur__hi, diablo_rojo_phon!19:03
zara_the_lemur__It's been in-progress for forever so I decided it was worthy of an announcement19:04
zara_the_lemur__#topic urgent items19:04
*** openstack changes topic to "urgent items (Meeting topic: storyboard)"19:04
zara_the_lemur__Nothing I'm aware of19:04
zara_the_lemur__we're ticking along19:04
zara_the_lemur__#topic #In-progress work19:04
*** openstack changes topic to "#In-progress work (Meeting topic: storyboard)"19:04
zara_the_lemur__for some reason I'm putting hashes everywhere...19:05
fungiSotK: thanks for group visibility for private stories! that will be a huge help to the vmt19:05
*** sambetts is now known as sambetts|afk19:05
zara_the_lemur__+119:05
zara_the_lemur__I've tested it, but it'll be good for people to try it out on things that aren't super-critical first, in case we've missed anything19:06
betherlyBrill!19:06
zara_the_lemur__:)19:06
zara_the_lemur__in other news... in a fit of desperation, I rechecked jeblair's patch to put tags in the task filter19:07
zara_the_lemur__(So that we can filter tasks by story tag)19:07
zara_the_lemur__and apparently it just needed a recheck19:07
zara_the_lemur__well, a fourth recheck19:07
zara_the_lemur__so that has fiiiiinally been merged, after probably-more-than-a-month-I-don't-even-want-to-look19:07
zara_the_lemur__(that's in the api)19:08
fungioh nice19:08
fungiso now we can filter tasks by story tag?19:08
* zara_the_lemur__ goes to find patch19:08
*** bh526r has quit IRC19:09
zara_the_lemur__#link https://review.openstack.org/#/c/404978/19:09
zara_the_lemur__so yeah, for worklists19:10
*** sdague_ has joined #openstack-meeting19:10
zara_the_lemur__so hopefully we'll need fewer workaround scripts for boards as time goes on.19:11
*** jprovazn has quit IRC19:11
zara_the_lemur__other in-progress things...19:11
*** jaugustine has joined #openstack-meeting19:11
zara_the_lemur__I made yet another fresh StoryBoard install this weekend, so have updated some of the install docs19:11
zara_the_lemur__nothing very exciting there19:11
zara_the_lemur__#link https://review.openstack.org/#/c/415996/19:12
zara_the_lemur__#link https://review.openstack.org/#/c/415942/19:12
*** rob_tao has quit IRC19:13
zara_the_lemur__and have submitted a 'fix' for a private stories bug; 'fix' in quotes since it fixes the problem but the logic isn't what we should really be doing19:13
zara_the_lemur__#link https://review.openstack.org/#/c/416070/19:13
zara_the_lemur__well, it's better than what was there before as far as I could tell, anyway19:13
*** e0ne has joined #openstack-meeting19:13
zara_the_lemur__so those are some patches awaiting reviews19:13
zara_the_lemur__we also have some general maintenance patches awaiting review19:14
zara_the_lemur__#link https://review.openstack.org/#/c/415493/19:14
zara_the_lemur__#link https://review.openstack.org/#/c/415494/19:14
zara_the_lemur__aaaand we are still using login.launchpad.net instead of login.ubuntu.com but I don't know how to even start changing the database for that.19:15
*** gagehugo has left #openstack-meeting19:15
*** ijw has joined #openstack-meeting19:15
fungion 416070, i wonder why not just always make stories visible to the creator? it's not like hiding a story from its creator serves to create any additional security/secrecy (except maybe hiding later comments from them, not sure what the use case is though)19:15
*** sdake has joined #openstack-meeting19:15
*** sdake has quit IRC19:16
fungion the login.ubuntu.com front, it's just a db query we'll need to run (probably an etl script like the one mordred wrote for gerrit)19:16
persiaA potential use case is to hide later comments/updates in the event that a story is private to a company, and the creator changes employment.19:16
fungiso instead of always making it visible to the creator in perpetuity, just make it visible to teh creator by default unless they're removed?19:17
persiaI believe that is already in place.19:17
zara_the_lemur__yeah, that's the idea (and that is our current default)19:17
clarkboh hey this is topical on the internet now19:17
zara_the_lemur__(the problem atm is that it's possible to remove *everyone* from a story :D)19:18
clarkbsome ham radio software company used such features in whatever ticketing system they were using to remove evidence of being mean to their customers19:18
fungizara_the_lemur__: aha, got it. so the "fix" is to prevent them from removing themselves without having at least one other user able to view it19:18
zara_the_lemur__yeah19:18
clarkband then the Internet found out and got mad19:18
zara_the_lemur__that sounds interesting19:19
persiaclarkb: The internet will always find out, but from the perspective of most product managers, having that take three months can be a critical difference between being willing to use a common tracking system, and maintaining an internal JIRA (or whatever).19:19
clarkbpersia: oh sure its not the tracking systems fault19:19
clarkbits just an interesting story of the past couple weeks directly related to such features19:20
zara_the_lemur__(think I found the article, will read)19:20
fungialso this same sort of thing crops up all the time with web forums where the company maintaining it decides to hide things they find embarrassing19:20
jeblairour ticketing system has a 3-month fire rating!19:20
fungiand then stuff leaks and... yeah19:20
fungiit's more of a policy question than a feature question19:21
zara_the_lemur__yeah, down the line it's worth considering who can make stories private19:21
persiaFrom a feature perspective, I think it is useful to be able to embargo things to arbitrary groups.  From a policy perspective, I think that people collaborating in a large public open-source project would do well not to behave in ways that could cause later leaks to be embarassing.19:21
*** X-dark_ has joined #openstack-meeting19:22
fungimy sentiments as well19:22
*** jaugustine has quit IRC19:22
fungianyway, it's feature parity with lp's private bug handling and we're not seeing widespread issues there, so i'm not concerned really19:22
persiaThere's still the odd corner case where one can set the permissions of a story to only be readable by a group that contains no members, just in case people are poking the corners of this.19:22
*** jaugustine has joined #openstack-meeting19:23
zara_the_lemur__(right, and for now I'm fairly confident that if a company starts trying to hide things that were previously public all over storyboard, to hide bad behaviour, infra can say 'erm what?' and revert it.)19:23
fungipersia: though in that corner case, someone can still readd users to the group in question, the story is not completely unreachable19:23
persiazara_the_lemur__: Do SB admins have access to private stories, or only DB admins?19:23
*** X-dark has quit IRC19:24
*** X-dark_ is now known as X-dark19:24
zara_the_lemur__DB admins19:24
*** matrohon has joined #openstack-meeting19:24
persiafungi: Ah, thanks for pointing out that.  It makes me less worried about the current state :)19:24
*** ijw has quit IRC19:24
fungi(unless i'm misunderstanding the privacy/data model)19:24
persiaI think you understand correctly19:24
*** ad_rien_ has joined #openstack-meeting19:25
fungii still haven't had time to play around with how user groups are managed19:25
zara_the_lemur__(SB admins can add/remove people to/from teams; DB admins can see anything in StoryBoard as far as I'm aware)19:25
zara_the_lemur__it'd be good to get more eyes on it19:25
*** diablo_rojo has joined #openstack-meeting19:25
*** spotz_ is now known as spotz_zzz19:25
fungiyeah, db admins are always going to have access to everything (at least everything stored persistently in the db)19:26
zara_the_lemur__yep19:27
zara_the_lemur__so with the model atm, theoretically a sb admin could add themselves to a team and by that method gain access to things they can't see by default19:27
*** e0ne has quit IRC19:27
*** jaugustine has quit IRC19:28
zara_the_lemur__I don't yet know whether that's an issue, since I don't know how sb admins would be decided; if they're a subset of db admins then it's fine19:28
fungiwhich is also true of lp, so again not concerned with that design choice19:28
zara_the_lemur__cool19:28
persiaGenerally speaking, if one can't trust the DB admins or the SB admins ,they probably shouldn't be using that SB instance.19:28
*** ijw has joined #openstack-meeting19:28
*** e0ne has joined #openstack-meeting19:29
fungiin lp in fact, you basically have project-specific admins and group-specific admins. so it boils down to trusting people in the groups to which you're delegating access anyway19:29
fungithough i'm sure lp also has server-wide admins who can do those things, i'm just not one19:29
*** sdake has joined #openstack-meeting19:30
persiaMy understanding is that there are several classes of wider LP admin permissions, but that becomes an implementation detail.19:30
zara_the_lemur__great, if you're confident that it has feature-parity then that should be fine19:30
*** dprince has quit IRC19:30
fungito reduce burden on the sb admins, it may make sense in the future to extend the group schema to incorporate group-specific admins or the ability for groups to self-manage their memberships19:31
*** ad_rien_ has quit IRC19:31
fungibut that doesn't strike me as a blocker19:31
*** dprince has joined #openstack-meeting19:31
*** galstrom is now known as galstrom_zzz19:32
*** spzala has joined #openstack-meeting19:32
zara_the_lemur__+119:32
*** galstrom_zzz is now known as galstrom19:32
zara_the_lemur__plus, you have permissions for teams, who's on the list of admins who can assign members of groups admin permissions over the groups19:33
zara_the_lemur__*plus if you have19:33
*** galstrom is now known as galstrom_zzz19:33
zara_the_lemur__could get a bit infinite-regress-y19:33
jeblairself-management has worked out really well in gerrit (it's optional -- a group has an owner, which is another group.  that could be an admin group if you want top-down management, or it could be the group itself if you want self-management)19:34
jeblairzara_the_lemur__: that sounds adaptable to what you said -- maybe if you can acl management of a group to itself...19:34
persiaThat seems a reasonable model, assuming the users don't make long nested loops.19:34
persiaIs there a story about that already?19:35
*** spzala_ has joined #openstack-meeting19:35
zara_the_lemur__ah, so teams within teams?19:35
*** bnemec has quit IRC19:35
zara_the_lemur__I suspect there isn't a story yet19:35
zara_the_lemur__I think it's come up on irc before, vague memories of discussing it19:35
zara_the_lemur__very vague, possibly imaginary19:35
fungizara_the_lemur__: not so much teams within teams as teams controlled by a team (which could be itself in some circumstances)19:36
*** ttx has quit IRC19:36
*** pabelanger has quit IRC19:36
*** SotK has quit IRC19:36
*** sshnaidm has quit IRC19:36
*** radez has quit IRC19:36
*** aignatov has quit IRC19:36
*** mrmartin has quit IRC19:36
*** sindhude has quit IRC19:36
*** kevinbenton has quit IRC19:36
*** raginbajin has quit IRC19:36
*** onovy has quit IRC19:36
*** jschwarz has quit IRC19:36
*** manjeets has quit IRC19:36
*** Douhet has quit IRC19:36
*** mfranc213 has quit IRC19:36
*** lifeless has quit IRC19:36
*** cburgess has quit IRC19:36
*** rmk has quit IRC19:36
*** vgadiraj has quit IRC19:36
*** Zara has quit IRC19:36
*** rodrigods has quit IRC19:36
*** karthikp- has quit IRC19:36
*** tris has quit IRC19:36
*** cebruns_ has quit IRC19:36
*** raj_singh has quit IRC19:36
*** doffm has quit IRC19:36
*** d34dh0r53 has quit IRC19:36
*** yarkot has quit IRC19:36
*** cFouts has quit IRC19:36
*** sneti has quit IRC19:36
*** pshige_________ has quit IRC19:36
*** finchd has quit IRC19:36
*** eglute has quit IRC19:36
*** mikal has quit IRC19:36
*** jamespd has quit IRC19:36
*** nonameentername has quit IRC19:36
*** clarkb has quit IRC19:36
*** mrda has quit IRC19:36
*** bnemec has joined #openstack-meeting19:36
*** doffm has joined #openstack-meeting19:36
*** mikal has joined #openstack-meeting19:36
*** sk1pp has left #openstack-meeting19:36
*** eglute has joined #openstack-meeting19:36
*** SotK has joined #openstack-meeting19:36
*** radez has joined #openstack-meeting19:36
*** jschwarz has joined #openstack-meeting19:36
*** jamespd has joined #openstack-meeting19:36
*** Zara has joined #openstack-meeting19:36
persiaI read teams-within-teams is separate from team-owner-is-a-team(can be self).19:36
*** mfranc213 has joined #openstack-meeting19:36
*** pabelanger has joined #openstack-meeting19:36
*** clarkb has joined #openstack-meeting19:36
*** rodrigods has joined #openstack-meeting19:36
*** _nonameentername has joined #openstack-meeting19:36
*** rmk has joined #openstack-meeting19:36
*** d34dh0r53 has joined #openstack-meeting19:36
*** mrda has joined #openstack-meeting19:36
*** spzala has quit IRC19:36
*** pshige_________ has joined #openstack-meeting19:36
*** cburgess has joined #openstack-meeting19:36
*** lifeless has joined #openstack-meeting19:36
*** tris- has joined #openstack-meeting19:36
*** aignatov has joined #openstack-meeting19:36
*** ttx has joined #openstack-meeting19:36
*** gnarld_ has joined #openstack-meeting19:36
*** rmk has quit IRC19:36
*** rmk has joined #openstack-meeting19:36
*** mrmartin has joined #openstack-meeting19:36
*** karthikp_ has joined #openstack-meeting19:37
*** kevinbenton has joined #openstack-meeting19:37
*** cebruns_ has joined #openstack-meeting19:37
*** Douhet has joined #openstack-meeting19:37
*** gnarld_ is now known as cFouts19:37
*** sshnaidm has joined #openstack-meeting19:37
fungigerrit does also have teams-within-teams (you can specify a team to include other teams as members), and yes gerrit seems to have loop detection built in to handle that19:37
*** zxiiro has quit IRC19:37
fungiwe have lots of examples of group inclusion loops in gerrit already, and there is even a recursive membership query in its api which dtrt with those loops19:37
*** tris- is now known as tris19:37
*** fitoduarte has joined #openstack-meeting19:38
*** raginbajin has joined #openstack-meeting19:38
zara_the_lemur__I might be phrasing it badly, the only model I currently have for this would be something like linux user groups, so that membership of one group could depend on membership of another group (so a group acts like a subset of another group, but it's not the groups that are nested, but the membership status, if that makes sense)19:38
*** korzen has quit IRC19:38
zara_the_lemur__anyway, cool, there are ideas around it and people can see ways of doing things if we need it; I think that's promising :)19:39
*** finchd has joined #openstack-meeting19:39
*** galstrom_zzz is now known as galstrom19:39
*** zxiiro has joined #openstack-meeting19:39
*** yarkot has joined #openstack-meeting19:39
persiazara_the_lemur__: That matches my understanding (ignoring that I don't see linux groups that way), that for a given user, they are a member of  group directly, or they are a member of a group indirectly (because a group in which they are a member is a member of the indirect group)19:39
*** sindhude has joined #openstack-meeting19:40
zara_the_lemur__heh, that sounds different to mine but this meeting probably isn't the best time to work out if we're picturing the same thing or not; we should probably continue it later :)19:41
zara_the_lemur__we only have about 20 mins left so probably best to move onto open discussion19:41
* fungi apologizes for the tangent19:41
zara_the_lemur__#topic open discussion19:41
*** openstack changes topic to "open discussion (Meeting topic: storyboard)"19:41
zara_the_lemur__Now everyone can go on tangents and I won't have a vague sense of guilt :)19:42
zara_the_lemur__also, goodness, I said 'probably' a lot there19:42
diablo_rojoprobably is a good word19:43
zara_the_lemur__:)19:43
fungii probably agree, probably is probably a good word19:43
*** raj_singh has joined #openstack-meeting19:44
*** manjeets has joined #openstack-meeting19:44
*** paw has quit IRC19:44
zara_the_lemur__on that note, I will probably try to get PTG attendance sorted out this week19:44
fungiso i guess if we're short on other open discussion topics... gerrit's documentation has a bit to say about its group management which may be worth skimming19:45
fungi#link https://gerrit-review.googlesource.com/Documentation/access-control.html#_account_groups19:45
zara_the_lemur__cool, thanks19:46
fungiit's pretty terse, but does a good job of explaining their model19:47
zara_the_lemur__yeah, at a glance it looks clear19:49
*** jaugustine has joined #openstack-meeting19:49
*** vishnoianil has joined #openstack-meeting19:49
*** dprince has quit IRC19:50
*** dprince has joined #openstack-meeting19:50
*** corey_ has joined #openstack-meeting19:50
*** VW_ has joined #openstack-meeting19:51
*** corey_ is now known as Guest374519:51
*** ayoung is now known as ayoung-afk19:52
zara_the_lemur__anyone with any other topics?19:52
zara_the_lemur__we have 8 mins19:52
*** VW_ has quit IRC19:52
fungii've got nothing else, other than a huge thank-you to everyone who works on storyboard19:52
*** VW_ has joined #openstack-meeting19:52
fungiyou're building amazing stuff19:52
*** cleong has quit IRC19:53
zara_the_lemur__:D well, in turn I send a huge thank-you to everyone who works on the openstack infra!19:53
*** rfolco has quit IRC19:53
*** VW has quit IRC19:54
zara_the_lemur__it's nice working on a project where review etc is so straightforward19:54
zara_the_lemur__and, of course, the CI :)19:55
*** spotz_zzz is now known as spotz_19:56
*** VW_ has quit IRC19:56
zara_the_lemur__we have 4 mins left for everyone to compliment each other if they want19:56
zara_the_lemur__3 mins now19:57
jeblairzara_the_lemur__: that's some first class counting down!19:57
zara_the_lemur__:D19:57
zara_the_lemur__you have some excellent hats!19:58
*** gouthamr has joined #openstack-meeting19:58
zara_the_lemur__YOU ARE ALL FANTASTIC19:59
zara_the_lemur__#endmeeting19:59
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"20:00
openstackMeeting ended Wed Jan  4 19:59:58 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2017/storyboard.2017-01-04-19.02.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2017/storyboard.2017-01-04-19.02.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2017/storyboard.2017-01-04-19.02.log.html20:00
*** efried has joined #openstack-meeting20:00
*** Leom has joined #openstack-meeting20:00
*** _alastor1 is now known as _alastor_20:01
*** efried has quit IRC20:02
*** efried has joined #openstack-meeting20:02
*** efried has left #openstack-meeting20:03
*** bvandenh has joined #openstack-meeting20:04
*** dongfeng has quit IRC20:04
*** Leom_ has joined #openstack-meeting20:06
*** VW has joined #openstack-meeting20:07
*** Leom has quit IRC20:07
*** efried has joined #openstack-meeting20:08
*** beagles is now known as beagles_biab20:08
*** salv-orlando has quit IRC20:08
*** efried has quit IRC20:09
*** weshay is now known as weshay_brb20:10
*** Sukhdev has quit IRC20:11
*** liangy has joined #openstack-meeting20:12
*** efried has joined #openstack-meeting20:16
*** efried has quit IRC20:17
*** bvandenh has quit IRC20:19
*** dongfeng has joined #openstack-meeting20:21
*** weshay_brb is now known as weshay20:26
*** VW has quit IRC20:26
*** VW has joined #openstack-meeting20:27
*** rtheis has quit IRC20:28
*** spotz_ is now known as spotz_zzz20:32
*** Guest3745 is now known as cleong20:33
*** spotz_zzz is now known as spotz_20:33
*** caboucha has quit IRC20:34
*** tonytan4ever has quit IRC20:35
*** tonytan4ever has joined #openstack-meeting20:36
*** efried has joined #openstack-meeting20:37
*** efried has quit IRC20:37
*** mickeys_ has quit IRC20:39
*** d0ugal has quit IRC20:39
*** lamt has quit IRC20:39
*** sdake has quit IRC20:40
*** spzala_ has quit IRC20:42
*** cutforth has joined #openstack-meeting20:45
*** torgomatic has joined #openstack-meeting20:45
*** paw has joined #openstack-meeting20:46
*** ijw has quit IRC20:49
*** JoseMello has quit IRC20:55
*** d0ugal has joined #openstack-meeting20:55
*** CarolBarrett has joined #openstack-meeting20:57
*** acoles_ is now known as acoles20:57
*** mmotiani1 has joined #openstack-meeting20:58
*** sgundur_ has joined #openstack-meeting20:58
*** pdardeau has joined #openstack-meeting20:59
*** kota_ has joined #openstack-meeting20:59
notmynameswift team meeting time21:00
notmyname#startmeeting swift21:00
openstackMeeting started Wed Jan  4 21:00:07 2017 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: swift)"21:00
openstackThe meeting name has been set to 'swift'21:00
notmynamewho's here for the swift team meeting?21:00
*** jrichli has joined #openstack-meeting21:00
kota_hi21:00
pdardeauhi21:00
bkeller`o/21:00
sgundur_hi21:00
jrichlihello21:00
mmotiani1Hi21:00
*** nadeem has joined #openstack-meeting21:01
notmynamehmm... kinda light today :-)21:01
notmynamebut to the faithful, welcome ;-)21:01
nadeemo/21:01
notmynamethis week I was hoping to catch up on what's going on, now that we're all back from holidays21:02
acoleshi, sorry for being late21:02
*** jaugustine has quit IRC21:02
notmynamebut first, I wanted to call out donagh in the meeting and thank him for working on swift. he's moving on to other projects at HPE and will no longer be working on swift https://review.openstack.org/#/c/416577/21:03
notmynameso if/when you see him around, tell him thanks and wish him well :-)21:03
*** caiobrentano has joined #openstack-meeting21:04
notmynameok, so let's talk about what's going on21:04
*** rtheis has joined #openstack-meeting21:04
*** rtheis has quit IRC21:04
notmynameI'll admit I haven't completely caught up on patches since being off, so if I'm missing something that comes up, please remind me :-)21:04
cutfortho/21:04
tdasilvahi21:05
*** spzala has joined #openstack-meeting21:06
notmynamein our last meeting, I put forth a list of stuff that's being worked on that are big (either in impact or in effort)21:06
notmynamegolang object server, global ec, composite rings, policy migration, policy auto tiering, sync to elasticsearch, container sharding, symlinks, increase part power, container sharding21:06
notmynameand I know there are other things going on too21:06
*** ykatabam has joined #openstack-meeting21:08
notmynamehere's what I'm working on personally, related to upstream work. I'm getting ready for a conference in two weeks (talk prep) and I'm working on an improved all-in-one environment that shoudl be really easy to consume21:08
notmynamei hope to be done with that relatively soon, and it will be a public tool21:08
notmynameso what are you working on? who's first?21:08
notmyname...or second, rather21:09
*** adisky_ has quit IRC21:09
*** ad_rien_ has joined #openstack-meeting21:09
notmynamekota_: what's going on with you and in the NTT world?21:09
kota_notmyname: ok, so you know, global ec is my first priority21:10
*** saisrikiran has joined #openstack-meeting21:10
notmynamecool. I'm excited about that :-)21:10
kota_notmyname: and still waiting reviews21:10
notmynamehow's progress?21:10
notmynameok, blocked by reviews21:10
kota_not so much recently21:10
kota_yes21:10
notmynameok21:10
*** dimtruck is now known as zz_dimtruck21:10
kota_and the good news in the end of the last year21:10
kota_is21:10
kota_storlets has been openstack official21:11
kota_related project to swift21:11
jrichlinice21:11
*** mrmartin has quit IRC21:11
kota_and i has been working on some stuff on that21:11
notmynamecool21:11
acolescongrats to storlets team21:11
kota_the most impressive work has been writing jupyter/ipython extension21:11
kota_https://review.openstack.org/#/c/414883/21:11
kota_thanks all21:12
*** cleong has quit IRC21:12
*** ayoung-afk is now known as ayoung21:12
kota_now i'm thinking of sort of that could be used for swift too.21:12
notmynamefun21:12
*** mickeys has joined #openstack-meeting21:12
notmynamepdardeau: you're next. what's up?21:13
kota_e.g. %%swift-upload container object -> upload ipython cell to swift21:13
pdardeaummotiani1: and i are working on swift benchmarking21:13
pdardeauramping up to 20 storage nodes with 8 HDD each21:13
mmotiani1+121:14
notmynamenice21:14
notmynameanything upstream you're needing for that?21:14
pdardeaunot at the moment21:14
notmynameok21:14
notmynamebkeller`: what's up with you? frozen in chicago?21:15
acolespdardeau: did you ever meet Mark Seger (in Bristol maybe?) - he has some nice tools for benchmarking/analysis21:15
* notmyname always imagines chicago as very very cold21:15
bkeller`it's 10F here today21:15
bkeller`nothing new for notifications yet though21:15
pdardeauacoles: yes, i did! thanks for reminding me. i'll look around to see what he has21:15
acolespdardeau: email me if you want to connect with him, he doesn't hang out in irc21:16
pdardeauacoles: thx21:16
notmynamebkeller`: ok. what do you need from upstream?21:16
*** askb has joined #openstack-meeting21:16
bkeller`nothing yet that i know of21:17
notmynameok21:17
notmynamejrichli: you're next21:17
jrichlitdasilva, timburke, and I have done some work on symlinks recently21:17
jrichlistill more to do for sure21:17
*** e0ne has quit IRC21:17
jrichlitimburke left a lot of good feedback21:18
notmynamecool21:18
jrichlii uploaded a patch for api-ref docs - could use some feedback there21:18
notmynameok. link?21:18
jrichlihttps://review.openstack.org/#/c/41594321:18
*** galstrom is now known as galstrom_zzz21:18
jrichliclayg had mentioned it would be good for us to focus on hammering the api out before we go through perfecting the impl21:19
notmynameyeah, I can see wisdom in that21:19
*** spzala has quit IRC21:19
jrichliand you all have prob seen in channel we are planning to have a conference call about keymaster v2 soon21:20
acolesjrichli: do we have a time yet?21:20
notmynamegreat21:20
jrichlii guess tomorrow at 14:00 UTC - although, i still have a lot to go over for myself.  but i dont want to hold it up.21:20
*** julim has quit IRC21:20
notmynameI'll look forward to hearing what you talk about21:21
jrichlii haven't created an invite yet.  will today.  let me know if you are interested - i already know about tdasilva, mahatic, acoles21:21
jrichliwell, i call it that, but its about mathiasb current patch - oh, and he will be on the list of course :-)21:22
notmyname#info review https://review.openstack.org/#/c/415943 for symlink API21:22
*** zara_the_lemur__ has left #openstack-meeting21:22
acolesspecifically I want to suggest that future keymasters *only* keep config in a separate file (not in proxy-server.conf), and have others tell me I am wrong21:22
jrichlihttps://review.openstack.org/364878/21:23
notmyname#info if interested, talk to jrichli about an invite to the conference call about keymaster v2 happening this week21:23
*** salv-orlando has joined #openstack-meeting21:23
notmynamejrichli: anything else?21:24
*** thiago has joined #openstack-meeting21:24
jrichlithat's all i have been up to lately21:24
*** tdasilva has quit IRC21:24
*** thiago is now known as Guest5933021:24
notmynamesgundur_: you're up. what are you working on this week?21:24
*** Guest59330 is now known as tdasilva21:25
*** timburke has joined #openstack-meeting21:25
*** timburke has left #openstack-meeting21:25
sgundur_notmyname : Happy new year21:25
sgundur_was on vacation , got back this week21:26
sgundur_been learning about EC from Nadeem21:26
notmynamehint: "mark all as read" is a *great* way to deal with email ;-)21:26
sgundur_lol21:26
notmynamecool on the EC learning21:26
sgundur_I am inclined to do some meaningful reviews on EC and hopefully more in furture in EC work21:27
*** jaypipes has quit IRC21:27
notmynamesgundur_: great. it would be helpful for you to look at kota_'s global EC patches. both to learn and for getting that landed21:27
notmynamesgundur_: nadeem: anything else you need from the rest of the community?21:28
sgundur_yes, that's what I was thinking looking at Kota's update earlier21:28
notmynamewonderful. thanks21:28
*** joeljwright has joined #openstack-meeting21:28
kota_sgundur_: thanks ;-)21:28
*** mrmartin has joined #openstack-meeting21:28
joeljwrightSorry I'm late! :S21:28
*** sdake has joined #openstack-meeting21:28
notmynamejoeljwright: no worries. welcome21:29
notmynameacoles: your turn. what's going on?21:29
*** ijw has joined #openstack-meeting21:29
*** timburke has joined #openstack-meeting21:30
acolesnotmyname: before the break I was working with Pavel on this patch https://review.openstack.org/402043 which needs to land21:30
acolesfixes regression in replication suffix hashing21:30
notmynameah, yes. thanks for the reminder. that's a big deal21:31
acolesyes.21:31
notmyname#info please review https://review.openstack.org/#/c/402043/ to close a high priority bug21:31
acoles^^ please go to a quiet place and think hard about whether we now have it right21:32
acolesnotmyname: now getting up to speed on the keymaster/barbican patch again.21:32
notmynamecool21:32
notmynameacoles: anything else you need from upstream?21:32
acolesand found an ssync bug in the process :/ which I'll probably try to fix21:32
notmynameyay21:32
notmyname(sarcastically for the bug. seriously for the fix)21:33
acolesnotmyname: not feeling any need at the moment21:33
notmynameok21:33
* acoles is grieving for donagh21:33
notmyname+121:33
*** VW has quit IRC21:33
jrichli+121:33
joeljwright:(21:33
kota_:(21:34
notmynamecutforth: anything from you? are you working on anything related to upstream swift this week?21:34
acolesI will still pester him!21:34
notmynametdasilva: your turn. what's new with you in the new year?21:35
tdasilvahello! just before the break i was working on the libec/pyeclib merger21:36
notmynameoh right!21:36
tdasilvaI thought of two options, one was to copy files from pyeclib into libec repo and send gerrit patch21:36
tdasilvathe other was to work with infra to merge the repos, so that way we could keep history of changes21:37
notmynamewhich way are you leaning so far?21:37
tdasilvaI took a stab at creating a throw away repo but still need to get feedback from infra team21:37
notmynameok. I'd prefer to keep the history, if possible. thanks for working on that21:37
tdasilvayeah, i'd like that too, will continue trying to work with the infra team, let's see...21:38
notmynamecool21:38
notmynameanything you need from the rest of the community yet?21:38
tdasilvaover the break timburke left comments on symlink patch, so i started going through those21:38
notmynameok21:38
tdasilvaand jrichli send the api-ref patch which I still need to look over21:38
tdasilvahoping to send an update to symlink patch soon21:39
notmynamethanks21:39
cutforthnothing from me, thank you for asking21:39
tdasilvai think that's it. jrichli if you need video conf. call for tomorrow's meeting i can help21:40
jrichlitdasilva: ok, cool.  thx21:40
notmynametimburke: your turn. what's up?21:40
timburkemostly looking at swift3 stuff21:40
*** tdasilva- has joined #openstack-meeting21:40
notmynameok. anything blocking that you need help with?21:41
timburkecan we clone kota_?21:41
timburke:P21:41
notmynameheh21:41
kota_so my slow review blocks them, i know :/21:42
timburkewell, i *could* just merge them, but then i'd feel dirty21:42
*** zz_dimtruck is now known as dimtruck21:42
notmynamejoeljwright: I think you're the last nick I saw come in. your turn. what's going on with you, related to swift team work?21:43
joeljwrightI got some good feedback on the SLO preamble/postamble stuff21:43
joeljwrightneed to talk to timburke about his comments21:44
notmynamegreat21:44
joeljwrightalso, the removing slo segments patch for the client21:44
notmynameah, nice21:44
notmynameis that up yet and I'm forgetting about it, or is it goign to be proposed?21:44
joeljwrightwhich one?21:45
notmynameremoving slo segments21:45
joeljwrightthe SLO segment removal patch had issues21:45
timburkeugh, that reminds me that i need to think more about https://review.openstack.org/#/c/310075/ ...21:45
joeljwrightI'd like it fixed too, so that will be a chat with timburke21:45
notmynameok21:45
timburkeoh! "removal" -> "expiration"21:45
notmynameanything else from anyone? did I skip anyone or did anyone remember something else? anything else to bring up?21:46
joeljwrightsorry - it's been a fun christmas21:46
joeljwrightI also have a machine set up to test container sharding, but no progress yet21:46
*** nadya has quit IRC21:46
notmynamejoeljwright: nice21:46
joeljwrightwill probably bug mattoliverau as soon as I have something21:46
nadeemWas on vacation for last few weeks. I will working on trimming feature/hummingbird branch to isolate golang replicator21:46
pdardeauany updates on anything golang related?21:47
timburkenice! i've been wanting to look at that but haven't gotten around to it21:47
notmynamenadeem: cool. please continue to talk with clayg about that too :-)21:47
*** saisrikiran has quit IRC21:47
nadeemsure will do :)21:47
notmynamethanks21:47
joeljwrighttimburke: you got a few mins after the meeting?21:48
timburkeyeah, definitely21:48
notmynameso in summary, https://review.openstack.org/#/c/402043/ needs some serious review to close a bug, https://review.openstack.org/#/c/415943 is a proposal for symlink API, and talk to jrichli if you're interested in the new keymaster call tomorrow21:48
notmynameif there's nothing else....21:49
notmynamethanks, again, for all your work on swift21:49
notmyname#endmeeting21:49
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"21:49
openstackMeeting ended Wed Jan  4 21:49:43 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2017/swift.2017-01-04-21.00.html21:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2017/swift.2017-01-04-21.00.txt21:49
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2017/swift.2017-01-04-21.00.log.html21:49
*** pdardeau has left #openstack-meeting21:49
*** sgundur_ has left #openstack-meeting21:50
*** lamt has joined #openstack-meeting21:50
*** timburke has left #openstack-meeting21:50
*** mmotiani1 has quit IRC21:50
*** jrichli has left #openstack-meeting21:50
*** joeljwright has left #openstack-meeting21:51
*** dbecker has quit IRC21:53
*** jamesdenton has quit IRC21:53
*** salv-orl_ has joined #openstack-meeting21:54
*** eharney has quit IRC21:54
*** TxGirlGeek has quit IRC21:55
*** spotz_ is now known as spotz__21:56
*** spotz__ is now known as spotz_21:56
*** TxGirlGeek has joined #openstack-meeting21:56
*** salv-orlando has quit IRC21:56
*** thorst has quit IRC21:58
*** matrohon has quit IRC21:58
*** thorst has joined #openstack-meeting22:00
*** TxGirlGeek has quit IRC22:01
*** ansmith has quit IRC22:01
*** TxGirlGeek has joined #openstack-meeting22:02
*** iyamahat has quit IRC22:03
*** iyamahat has joined #openstack-meeting22:03
*** VW has joined #openstack-meeting22:03
*** fguillot has quit IRC22:03
*** TxGirlGeek has quit IRC22:03
*** TxGirlGeek has joined #openstack-meeting22:05
*** thorst has quit IRC22:05
*** TxGirlGeek has quit IRC22:06
*** VW has quit IRC22:06
*** TxGirlGeek has joined #openstack-meeting22:06
*** VW has joined #openstack-meeting22:06
*** edtubill has quit IRC22:06
*** acoles is now known as acoles_22:07
*** lbeliveau has joined #openstack-meeting22:08
*** dprince has quit IRC22:09
*** TxGirlGeek has quit IRC22:09
*** TxGirlGeek has joined #openstack-meeting22:09
*** TxGirlGeek has quit IRC22:11
*** TxGirlGeek has joined #openstack-meeting22:11
*** lblanchard has quit IRC22:13
*** guoshan has joined #openstack-meeting22:14
*** TxGirlGeek has quit IRC22:16
*** TxGirlGeek has joined #openstack-meeting22:16
*** thorst has joined #openstack-meeting22:18
*** rbudden has quit IRC22:18
*** guoshan has quit IRC22:19
*** thorst has quit IRC22:21
*** fzdarsky|afk has quit IRC22:22
*** thorst has joined #openstack-meeting22:22
*** TxGirlGeek has quit IRC22:23
*** ad_rien_ has quit IRC22:24
*** jkilpatr has quit IRC22:25
*** jrobinson has joined #openstack-meeting22:25
*** onovy has joined #openstack-meeting22:26
*** CarolBarrett has quit IRC22:29
*** baoli has quit IRC22:29
*** TxGirlGeek has joined #openstack-meeting22:30
*** baoli has joined #openstack-meeting22:30
*** kota_ has left #openstack-meeting22:30
*** baoli has quit IRC22:33
*** baoli has joined #openstack-meeting22:36
*** gouthamr has quit IRC22:36
*** masayukig has quit IRC22:38
*** masayukig has joined #openstack-meeting22:38
*** rbak_ has quit IRC22:38
*** thorst has quit IRC22:39
*** VW has quit IRC22:40
*** baoli has quit IRC22:40
*** VW has joined #openstack-meeting22:44
*** bobh_ has quit IRC22:45
*** nadya has joined #openstack-meeting22:47
*** cutforth has quit IRC22:49
*** diablo_rojo_phon has quit IRC22:50
*** tonytan4ever has quit IRC22:50
*** VW has quit IRC22:51
*** VW has joined #openstack-meeting22:51
*** dfflanders has joined #openstack-meeting22:52
*** nadya has quit IRC22:52
*** openstack has joined #openstack-meeting22:53
*** ChanServ sets mode: +o openstack22:53
*** rbak has joined #openstack-meeting22:54
*** VW_ has joined #openstack-meeting22:54
*** VW has quit IRC22:57
*** VW_ has quit IRC22:58
*** TxGirlGeek has quit IRC22:59
*** amotoki has quit IRC23:00
*** amotoki has joined #openstack-meeting23:02
*** rbudden has joined #openstack-meeting23:03
*** jaugustine has joined #openstack-meeting23:04
*** armax has quit IRC23:04
*** lpetrut has quit IRC23:04
*** ijw has quit IRC23:05
*** armax has joined #openstack-meeting23:05
*** xyang1 has quit IRC23:05
*** armax has quit IRC23:06
*** sdake has quit IRC23:09
*** jaugustine has quit IRC23:10
*** VW has joined #openstack-meeting23:14
*** spzala has joined #openstack-meeting23:17
*** saggi has quit IRC23:17
*** VW has quit IRC23:18
*** saggi has joined #openstack-meeting23:19
*** yamahata has quit IRC23:19
*** salv-orl_ has quit IRC23:20
*** jungleboyj has quit IRC23:23
*** cdelatte has quit IRC23:23
*** sdake has joined #openstack-meeting23:24
*** sdake has quit IRC23:26
*** yamahata has joined #openstack-meeting23:26
*** amotoki has quit IRC23:26
*** gongysh has joined #openstack-meeting23:28
*** sdake has joined #openstack-meeting23:29
*** spotz_ is now known as spotz_zzz23:30
*** amotoki has joined #openstack-meeting23:31
*** iyamahat_ has joined #openstack-meeting23:34
*** iyamahat has quit IRC23:34
*** pradk has quit IRC23:34
*** thorst_ has joined #openstack-meeting23:35
*** gouthamr has joined #openstack-meeting23:39
*** spzala has quit IRC23:42
*** spzala has joined #openstack-meeting23:45
*** myoung is now known as myoung|afk23:46
*** lamt has quit IRC23:48
*** gouthamr has quit IRC23:48
*** gouthamr has joined #openstack-meeting23:53
*** lbeliveau has quit IRC23:54
*** ijw has joined #openstack-meeting23:55
*** ansmith has joined #openstack-meeting23:55
*** iyamahat has joined #openstack-meeting23:57
*** iyamahat_ has quit IRC23:57
*** ekcs has joined #openstack-meeting23:57
*** masahito has joined #openstack-meeting23:58
ekcstime for congress meeting. masahito thinrichs ramineni aimeeu23:59

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