Wednesday, 2017-01-11

*** rbak has quit IRC00:08
*** harlowja has quit IRC00:09
*** yangyapeng has quit IRC00:09
*** imcsk8 has quit IRC00:09
*** imcsk8 has joined #openstack-meeting00:09
*** pasquier-s has quit IRC00:11
*** xiaohhui has quit IRC00:11
*** ogelbukh has quit IRC00:11
*** xiaohhui has joined #openstack-meeting00:11
*** baoli has quit IRC00:12
*** zaro has quit IRC00:12
*** efried has joined #openstack-meeting00:12
*** simonmcc has quit IRC00:12
*** macsz has quit IRC00:12
*** zerick has quit IRC00:12
*** markvoelker has quit IRC00:12
*** dewanee has quit IRC00:12
*** ttrifonov has quit IRC00:12
*** vdrok has quit IRC00:12
*** NikitaKonovalov has quit IRC00:12
*** haukebruno has quit IRC00:12
*** zaro has joined #openstack-meeting00:12
*** rpodolyaka has quit IRC00:12
*** johnsom has quit IRC00:12
*** macsz has joined #openstack-meeting00:12
*** HenryG has quit IRC00:12
*** aeng has quit IRC00:12
*** med_ has quit IRC00:12
*** hughhalf has quit IRC00:12
*** afazekas has quit IRC00:12
*** dewanee has joined #openstack-meeting00:12
*** cdub has quit IRC00:12
*** markvoelker has joined #openstack-meeting00:12
*** ogelbukh has joined #openstack-meeting00:13
*** pkoniszewski has quit IRC00:13
*** rbudden has quit IRC00:13
*** zerick has joined #openstack-meeting00:13
*** ildikov has quit IRC00:13
*** lcastell has quit IRC00:13
*** darvon has quit IRC00:13
*** haukebruno has joined #openstack-meeting00:13
*** NikitaKonovalov has joined #openstack-meeting00:14
*** VW_ has joined #openstack-meeting00:14
*** jroll has quit IRC00:14
*** darvon has joined #openstack-meeting00:14
*** bobmel has joined #openstack-meeting00:14
*** hongbin has quit IRC00:15
*** HenryG has joined #openstack-meeting00:15
*** pkoniszewski has joined #openstack-meeting00:16
*** kenji-i has quit IRC00:16
*** med_ has joined #openstack-meeting00:16
*** lcastell has joined #openstack-meeting00:17
*** VW has quit IRC00:17
*** med_ is now known as Guest4752000:17
*** hughhalf has joined #openstack-meeting00:17
*** afazekas has joined #openstack-meeting00:17
*** ttrifonov has joined #openstack-meeting00:18
*** VW_ has quit IRC00:18
*** simonmcc has joined #openstack-meeting00:18
*** Guest47520 is now known as medberry00:19
*** medberry has quit IRC00:19
*** medberry has joined #openstack-meeting00:19
*** fnaval has quit IRC00:19
*** bobmel has quit IRC00:19
*** rpodolyaka has joined #openstack-meeting00:20
*** ildikov has joined #openstack-meeting00:21
*** jroll has joined #openstack-meeting00:21
*** aeng has joined #openstack-meeting00:21
*** pasquier-s has joined #openstack-meeting00:22
*** vdrok has joined #openstack-meeting00:22
*** johnsom has joined #openstack-meeting00:22
*** pasquier-s has quit IRC00:25
*** pasquier-s has joined #openstack-meeting00:25
*** vdrok has quit IRC00:25
*** vdrok has joined #openstack-meeting00:25
*** johnsom has quit IRC00:25
*** johnsom has joined #openstack-meeting00:25
*** thorst has joined #openstack-meeting00:25
*** harlowja has joined #openstack-meeting00:25
*** chenying has quit IRC00:29
*** chenying has joined #openstack-meeting00:29
*** ekcs has quit IRC00:30
*** Dmitrii-Sh has quit IRC00:32
*** chyka has quit IRC00:33
*** aslezil has quit IRC00:34
*** sdake has quit IRC00:34
*** mriedem has joined #openstack-meeting00:35
*** bobmel has joined #openstack-meeting00:35
*** woodster_ has quit IRC00:35
*** mriedem1 has joined #openstack-meeting00:38
*** bobmel has quit IRC00:40
*** Julien-zte has joined #openstack-meeting00:40
*** thorst has quit IRC00:42
*** mriedem has quit IRC00:42
*** thorst has joined #openstack-meeting00:42
*** joehuang has joined #openstack-meeting00:43
*** jaypipes has quit IRC00:44
*** thorst has quit IRC00:46
*** bobmel has joined #openstack-meeting00:56
*** oomichi has quit IRC00:58
*** VW has joined #openstack-meeting00:58
*** mriedem1 has quit IRC00:58
*** oomichi has joined #openstack-meeting01:00
*** bobmel has quit IRC01:00
*** VW has quit IRC01:03
*** thorst has joined #openstack-meeting01:11
*** diablo_rojo has quit IRC01:14
*** thorst has quit IRC01:16
*** mestery has left #openstack-meeting01:16
*** bobmel has joined #openstack-meeting01:17
*** yangyapeng has joined #openstack-meeting01:18
*** ansmith has joined #openstack-meeting01:19
*** epico has joined #openstack-meeting01:19
*** bobmel has quit IRC01:21
*** huanxuan has joined #openstack-meeting01:22
*** zz_dimtruck is now known as dimtruck01:22
*** kevinz has joined #openstack-meeting01:28
*** aweeks has joined #openstack-meeting01:32
*** xgerman has joined #openstack-meeting01:32
*** lhx__ has joined #openstack-meeting01:33
*** beekhof_mb has joined #openstack-meeting01:34
*** briancurtin has joined #openstack-meeting01:35
*** bobmel has joined #openstack-meeting01:38
*** bobmel has quit IRC01:42
*** diablo_rojo has joined #openstack-meeting01:42
*** markvoelker has quit IRC01:43
*** markvoelker has joined #openstack-meeting01:44
*** yamamoto_ has joined #openstack-meeting01:47
*** pvaneck has quit IRC01:48
*** markvoelker has quit IRC01:49
*** Wenzhi has joined #openstack-meeting01:50
*** nadya has joined #openstack-meeting01:51
*** cdelatte has quit IRC01:54
*** nadya has quit IRC01:55
*** dmorita has quit IRC01:57
*** kvmahesh has joined #openstack-meeting01:58
*** dmorita has joined #openstack-meeting01:58
*** bobmel has joined #openstack-meeting01:59
*** gyee has quit IRC02:00
*** unicell has quit IRC02:01
*** thorst has joined #openstack-meeting02:02
*** thorst has quit IRC02:02
*** efried has quit IRC02:03
*** bobmel has quit IRC02:03
*** kvmahesh has quit IRC02:04
*** diablo_rojo has quit IRC02:06
*** sacharya has quit IRC02:07
*** s3wong has quit IRC02:08
*** ansmith has quit IRC02:11
*** efried has joined #openstack-meeting02:13
*** dimtruck is now known as zz_dimtruck02:15
*** dmorita has quit IRC02:18
*** bobmel has joined #openstack-meeting02:19
*** bobmel has quit IRC02:24
*** VW has joined #openstack-meeting02:26
*** dmorita has joined #openstack-meeting02:27
*** VW has quit IRC02:30
*** VW has joined #openstack-meeting02:31
*** spzala has quit IRC02:52
*** rreimberg has quit IRC02:54
*** hongbin has joined #openstack-meeting02:55
*** bobmel has joined #openstack-meeting03:01
*** sacharya has joined #openstack-meeting03:02
*** bobmel has quit IRC03:06
*** dmorita has quit IRC03:06
*** sacharya has quit IRC03:07
*** zz_dimtruck is now known as dimtruck03:11
*** iyamahat has quit IRC03:13
*** yamahata has quit IRC03:14
*** julim has quit IRC03:16
*** absubram has quit IRC03:18
*** thorst has joined #openstack-meeting03:20
*** thorst has quit IRC03:20
*** gouthamr has quit IRC03:21
*** amotoki has quit IRC03:21
*** absubram has joined #openstack-meeting03:25
*** diablo_rojo has joined #openstack-meeting03:27
*** amotoki has joined #openstack-meeting03:29
*** absubram has quit IRC03:31
*** dmorita has joined #openstack-meeting03:32
*** salv-orl_ has quit IRC03:32
*** salv-orlando has joined #openstack-meeting03:32
*** amotoki has quit IRC03:33
*** dmorita has quit IRC03:36
*** markvoelker has joined #openstack-meeting03:36
*** yamamoto_ has quit IRC03:43
*** bobmel has joined #openstack-meeting03:43
*** kbyrne has quit IRC03:45
*** spzala has joined #openstack-meeting03:47
*** links has joined #openstack-meeting03:47
*** gongysh has joined #openstack-meeting03:47
*** bobmel has quit IRC03:47
*** kbyrne has joined #openstack-meeting03:48
*** jrobinson is now known as jrobinson-afk03:48
*** Wenzhi has quit IRC03:50
*** dmorita has joined #openstack-meeting03:50
*** nadya has joined #openstack-meeting03:51
*** lhx__ has quit IRC03:52
*** r-mibu has quit IRC03:52
*** iyamahat has joined #openstack-meeting03:52
*** jrobinson-afk has quit IRC03:52
*** r-mibu has joined #openstack-meeting03:52
*** ayoung has quit IRC03:53
*** sdake has joined #openstack-meeting03:54
*** dmorita has quit IRC03:54
*** jrobinson has joined #openstack-meeting03:55
*** nadya has quit IRC03:56
*** jrobinson is now known as jrobinson-afk03:56
*** sdake has quit IRC04:00
*** iyamahat_ has joined #openstack-meeting04:00
*** sdake has joined #openstack-meeting04:01
*** iyamahat has quit IRC04:01
*** lhx__ has joined #openstack-meeting04:03
*** bobmel has joined #openstack-meeting04:04
*** martines_ has quit IRC04:04
*** rbudden has joined #openstack-meeting04:05
*** yangyapeng has quit IRC04:05
*** janki has joined #openstack-meeting04:08
*** bobmel has quit IRC04:08
*** sacharya has joined #openstack-meeting04:15
*** yamahata has joined #openstack-meeting04:15
*** VW has quit IRC04:17
*** padkrish has joined #openstack-meeting04:17
*** martines_ has joined #openstack-meeting04:17
*** sdake has quit IRC04:18
*** padkrish has quit IRC04:18
*** padkrish has joined #openstack-meeting04:18
*** spzala has quit IRC04:19
*** padkrish has quit IRC04:19
*** sacharya has quit IRC04:20
*** salv-orl_ has joined #openstack-meeting04:23
*** bobmel has joined #openstack-meeting04:25
*** salv-orlando has quit IRC04:26
*** Wenzhi has joined #openstack-meeting04:26
*** bobmel has quit IRC04:29
*** jrobinson-afk is now known as jrobinson04:29
*** iyamahat_ has quit IRC04:32
*** sudipto_ has joined #openstack-meeting04:32
*** sudipto has joined #openstack-meeting04:32
*** AlanClark has quit IRC04:32
*** sheel has joined #openstack-meeting04:34
*** ijw has quit IRC04:34
*** VW has joined #openstack-meeting04:36
*** cody-somerville has joined #openstack-meeting04:43
*** cody-somerville has quit IRC04:43
*** cody-somerville has joined #openstack-meeting04:43
*** csomerville has quit IRC04:43
*** bobmel has joined #openstack-meeting04:46
*** yamamoto_ has joined #openstack-meeting04:46
*** bobmel has quit IRC04:50
*** nadya has joined #openstack-meeting04:52
*** yangyapeng has joined #openstack-meeting04:52
*** absubram has joined #openstack-meeting04:55
*** nadya has quit IRC04:56
*** aslezil_ has joined #openstack-meeting04:58
*** absubram_ has joined #openstack-meeting04:59
*** absubram has quit IRC04:59
*** absubram_ is now known as absubram04:59
*** bobmel has joined #openstack-meeting05:07
*** sdake has joined #openstack-meeting05:07
*** thorst has joined #openstack-meeting05:09
*** dkushwaha has joined #openstack-meeting05:11
*** bobmel has quit IRC05:11
*** adisky_ has joined #openstack-meeting05:11
*** askb has quit IRC05:12
*** askb has joined #openstack-meeting05:12
*** gcb has quit IRC05:13
*** lhx__ has quit IRC05:13
*** thorst has quit IRC05:14
*** Yanxingan has joined #openstack-meeting05:15
*** Cibo has quit IRC05:15
*** sudipto_ has quit IRC05:17
*** sudipto has quit IRC05:17
*** hongbin has quit IRC05:18
*** rbudden has quit IRC05:19
*** yonglihe has quit IRC05:27
*** bobmel has joined #openstack-meeting05:28
*** ayogi has joined #openstack-meeting05:28
*** Cibo has joined #openstack-meeting05:28
*** Yanxingan has quit IRC05:29
*** Yanxing_an has joined #openstack-meeting05:29
*** xuhaiwei_ has joined #openstack-meeting05:30
sridhar_ram#startmeeting tacker05:30
openstackMeeting started Wed Jan 11 05:30:49 2017 UTC and is due to finish in 60 minutes.  The chair is sridhar_ram. Information about MeetBot at
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
sridhar_ram#topic Roll Call05:30
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"05:30
*** diga has joined #openstack-meeting05:31
sridhar_ramwho is here for tacker meeting?05:31
sridhar_ramhowdy all!05:32
sridhar_ramlet's give a min before we start05:32
*** bobmel has quit IRC05:32
*** nadya has joined #openstack-meeting05:32
sridhar_ramalright, let's start05:33
*** VW has quit IRC05:33
sridhar_ram#topic Ocata Implementation Status05:33
*** openstack changes topic to "Ocata Implementation Status (Meeting topic: tacker)"05:33
sridhar_ram#topic NSD05:33
*** openstack changes topic to "NSD (Meeting topic: tacker)"05:33
sridhar_ramthis is the highest priority05:34
sridhar_ramdkushwaha: any blocking issues?05:34
sridhar_ramdkushwaha: what is pending to finish for NSD ?05:34
*** nadya has quit IRC05:34
dkushwahasridhar_ram, not blocking, I am going through FT/UT parts now05:35
sridhar_ramdkushwaha: okay, i just finished reviewing from my side..05:35
*** ykatabam has quit IRC05:36
sridhar_ramdkushwaha: which other core member reviewing NSD ?05:36
dkushwahasridhar_ram, we got gongesh comments only before05:37
sridhar_ramdkushwaha: okay, remind gongysh .. we can be the 2nd reviewer05:37
dkushwahasridhar_ram, yes sure05:37
jankio/, sorry late05:37
dkushwahasridhar_ram, it would be more batter, if more members can review it05:38
sridhar_ramdkushwaha: once review comments are taken care, we can start merging NSD soon..05:38
sridhar_ramdkushwaha: actively ping diff core team members..05:38
dkushwahasridhar_ram, yes, sure05:38
sridhar_ramdkushwaha: thanks05:39
sridhar_ram#topic VNF inline template05:39
*** openstack changes topic to "VNF inline template (Meeting topic: tacker)"05:39
sridhar_ramjanki: where do we stand on this?05:39
jankisridhar_ram, cleint and server patchs are submitted for review05:40
dkushwahasridhar_ram, other than taker members, I also asked Mistral core, and also got comments frm his side.05:40
jankigongysh has few comments on client side which conflict with what is mentioned in the spec. Need your thoughts on that too05:40
sridhar_ramjanki: we need to get the client / API part settled down soon... so focus on getting client patch
sridhar_ramgongysh is not here05:41
*** aslezil_ has quit IRC05:41
sridhar_ramjanki: do you mind briefly desc the issue ?05:41
jankisridhar_ram, waiting for your opinion on the comments in client patch05:41
jankisridhar_ram, sure. what he is proposing is to use --with-vnf-template option to show inline vnfds instaed of --all option05:42
*** sudipto_ has joined #openstack-meeting05:42
*** sudipto has joined #openstack-meeting05:42
jankithe spec says using --all. Not sure what to use05:42
*** tbh has joined #openstack-meeting05:43
sridhar_ramthis for vnfd-list cmd / api ?05:43
tbhsorry for the late05:43
jankisridhar_ram, yes. for vnfd-list --all or vnfd-list --with-vnf-template05:43
sridhar_ramtbh: hi!05:43
tbhsridhar_ram, hi05:43
jankisridhar_ram, second, we talked about allowing user to enter both vnfd-id and vnfd-template with vnfd-template being precedent. His comment says to make vnfd-id and vnfd-template mutually exclusive. this again conflicts with what is mentioned in spec05:44
sridhar_ramjanki: this one is easy, if we can make it mutually exclusive that is alway better05:45
jankisridhar_ram, ok. will make changes accordingly05:45
*** xuan0802 has joined #openstack-meeting05:45
sridhar_ramjanki: we can edit the spec once the code merge, we usually don't do that.. but at times it is okay as an exception05:45
sridhar_rambut cli doc will take care of the documentation05:46
jankisridhar_ram, that solves my concern then :)05:46
sridhar_ramjanki: let's do the right thing :)05:46
jankisridhar_ram, doc on client side too? or just the ref doc?05:46
sridhar_ramjanki: cli doc is autogenerated .. see
*** KanagarajM has joined #openstack-meeting05:47
jankisridhar_ram, will have a look.05:47
sridhar_ramregarding --with-vnf-template, i think gongysh comment is not to use "--all"05:47
jankisridhar_ram, yes. he is suggesting to not use "--all" because it is used by opensatck client05:48
*** bobmel has joined #openstack-meeting05:49
*** ntpttr has quit IRC05:49
sridhar_rami personally don't like --with-vnf-template, i think we need a filter flag to indicate "inline"05:49
*** ntpttr_ has joined #openstack-meeting05:49
sridhar_ramwe can take it up in the gerrit review05:49
sridhar_ramjanki: another qq, will tacker vnfd-show <uuid> of an inline template work fine?05:49
jankisridhar_ram, any variable used will be a filter flag.05:50
jankisridhar_ram, yes. it should/will show. let me still check it on my system and get back on that05:50
sridhar_ramjanki: np05:50
*** diablo_rojo has quit IRC05:50
jankisridhar_ram, I also need your opinion on the change
jankiin this particular file.05:51
jankiso when vnfd-id is not specified and vnf-template is specified, vnfd-id will be None. THe above change bypasses validating UUID05:51
sridhar_ramjanki: i can look into it.. but i'm sure there are better qualified cores & member can provide some opinion as well :)05:51
jankiI have specified default vnfd-id to be None05:52
jankisridhar_ram, yes ofcourse, everyone can have a look.05:52
*** s3wong has joined #openstack-meeting05:52
sridhar_ramtbh: sripriya: KanagarajM: please review this code.. it is fairly lightweight change..05:52
s3wongsorry --- just got home05:53
sridhar_ramjanki: on your side, please take care of the merge conflicts05:53
sridhar_rams3wong: howdy!05:53
sridhar_ramlet's move to the next item05:53
KanagarajMsridhar_ram, sure.05:53
sridhar_ramKanagarajM: thanks!05:53
jankisridhar_ram, yes. I am waiting for few more review comments to make changes from my side05:53
*** bobmel has quit IRC05:53
sridhar_ram#topic VNFC05:53
*** openstack changes topic to "VNFC (Meeting topic: tacker)"05:53
sridhar_ramtbh: i left some comments in your patchset..05:54
KanagarajMsridhar_ram, should we schedule the corresponding bp for o3 on inline template ?05:54
*** gongysh has quit IRC05:54
sridhar_ramKanagarajM: yes, is marked for o305:55
tbhsridhar_ram, I have seen the comments,05:55
sridhar_ramKanagarajM: pretty much all BPs are now pointing to o3 :)05:55
tbhsridhar_ram, but I have added abstract driver as just a placeholder for future drivers05:56
KanagarajMsridhar_ram, yeah :)05:56
sridhar_ramtbh: the summary is - can we make HOT SoftwareConfig has a inherent feature off openstack vim infra driver .. without any need to specify a vnfc-driver05:56
tbhsridhar_ram, can I just keep it in the code, but remove "vnfc_driver" for now?05:57
sridhar_ramtbh: tbh: not a good idea to leave dead code in the tree05:57
sridhar_ramtbh: better to remove and reintroduce as needed...05:57
tbhsridhar_ram, ok05:58
*** Wenzhi has quit IRC05:58
sridhar_ramtbh: again, given this is a server side change we have some time... NSD is higher priority, fyi :)05:58
sridhar_ramtbh: next, how to do gate tests for this feature?05:58
sridhar_ramtbh: you need a special fedora image with heat agent ?05:59
tbhsridhar_ram, yes, we need fedora image to be uploaded in glance05:59
sridhar_ramKanagarajM: do you know how heat does gate tests for SoftwareConfig ?06:00
sridhar_ramKanagarajM: any special image used ?06:00
*** Wenzhi has joined #openstack-meeting06:00
*** lhx__ has joined #openstack-meeting06:01
sridhar_ramtbh: there is a tool called diskimage builder ..
sridhar_ramtbh: you can reach out to infra team on how to leverage this / other options to host a custom image for gate tests06:02
tbhsridhar_ram, sure, will do that06:02
sridhar_ramtbh: ping KanagarajM offline as they should have solved this problem in heat06:03
KanagarajMsridhar_ram, i will have a look06:03
sridhar_ramKanagarajM: oh, thanks!06:03
tbhsridhar_ram, ure06:04
sridhar_rammoving on06:04
*** nkrinner_afk is now known as nkrinner06:04
sridhar_ram#topic Tacker-Senlin integration06:04
*** openstack changes topic to "Tacker-Senlin integration (Meeting topic: tacker)"06:04
*** gcb has joined #openstack-meeting06:04
xuhaiwei_hi, I am working on this sridhar_ram06:05
sridhar_ramxuhaiwei_: KanagarajM: what is the latest in wrapping up the spec ?06:05
xuhaiwei_the spec is reviewed by core members, I still have some comments need to feed back06:05
xuhaiwei_I will modify the spec according to KanagarajM's comment06:06
sridhar_ramxuhaiwei_: looks selective vdu support in senlin based scaling is the only outstanding this06:06
*** bkopilov has joined #openstack-meeting06:06
KanagarajMsridhar_ram, i tried to ask some more details and i think xuhaiwei_ is working on it06:07
KanagarajMxuhaiwei_, :) thanks.06:07
sridhar_ramKanagarajM: xuhaiwei_: sounds good06:07
*** unicell has joined #openstack-meeting06:07
sridhar_ramxuhaiwei_: anything else you want to bring it up on this topic ?06:07
xuhaiwei_sridhar_ram, KanagarajM, just not sure what is selective vdu support means06:07
*** nadya has joined #openstack-meeting06:07
KanagarajMxuhaiwei_, it helps user to scale give set of VDUs 1 and 2 from the all VUDs VDU 1,2,3... say for example.06:08
sridhar_ramxuhaiwei_: currently all VDUs in the VNF gets scaled out / in .. 'selective VDU' is about scaling a subset of VDUs06:08
*** bobmel has joined #openstack-meeting06:09
xuhaiwei_sridhar_ram, KanagarajM, thanks for explaining, I will answer it in the spec06:10
sridhar_ramxuhaiwei_: sounds good..06:10
sridhar_rammoving to the next topic06:10
KanagarajMxuhaiwei_, yrw.06:10
sridhar_ram#topic tosca-parser / heat-translator 0.7.006:10
*** lpetrut has joined #openstack-meeting06:10
*** openstack changes topic to "tosca-parser / heat-translator 0.7.0 (Meeting topic: tacker)"06:10
*** nadya has quit IRC06:11
KanagarajMsridhar_ram, i am closly following up with sahdev (HT ptl) and seems with current version, we can't support selective vdu, for which we are looking for HT.06:11
sridhar_ramKanagarajM: thanks.. it was not clear whether this version would solve the problem..06:12
KanagarajMsridhar_ram, and sahdev assured to provide a reuired support in ocata so that tacker can provide support for selective vdu. but 0.7.0 does not have support06:12
sridhar_ramKanagarajM: okay, it will be tight.. let's see06:13
*** dims has quit IRC06:13
tbhsridhar_ram, and we latest tosca-parser to have NSD support06:13
KanagarajMsridhar_ram, i have made it a high priority. hope we could make it. :)06:13
sridhar_ramKanagarajM: thanks for following it up..06:13
sridhar_ramtbh: yep, that's great06:13
*** bobmel has quit IRC06:14
*** unicell has quit IRC06:14
sridhar_ramtbh: glad to have this nice cross-project collaboration between these two projects06:14
*** unicell has joined #openstack-meeting06:14
sridhar_ramnext topic..06:14
tbhsridhar_ram, yeah06:14
sridhar_ram#topic API Framework06:14
*** openstack changes topic to "API Framework (Meeting topic: tacker)"06:14
sridhar_ramdiga: glad to see the spec is iterating nicely06:15
digasridhar_ram: :) Thanks06:15
sridhar_ramdiga: can you give an update?06:15
digasridhar_ram: yes06:15
digasridhar_ram: I think almost all the queries are answered in case of API framework selection & features support using new API framework06:15
*** sacharya has joined #openstack-meeting06:16
KanagarajMtbh, tacker requirements.txt has heat-translator>=0.4.0, you may need to set to right version based on your above comment.
digasridhar_ram: According to my study in API framework so far, we can start the work on falcon framework06:16
sridhar_ramKanagarajM: good catch, post-NSD the version need to be bumped to 0.7.006:17
digaI had discussion with some community folks & infra team also, people suggests falcon over flask because falcon is 8x faster than flask06:17
*** ijw has joined #openstack-meeting06:18
digasridhar_ram: It is developed for cloud API only.06:18
sridhar_ramdiga: okay, for http-server, have you seen any other project using gunicorn ?06:18
* sridhar_ram means any other openstack projects06:18
digasridhar_ram: in OpenSTack, most of the people uses, HTTP WSGI server like zaqar etc06:19
*** dfflanders has quit IRC06:19
sridhar_ramdiga: that is for falcon, i was curious about gunicorn..06:20
digasridhar_ram: ok06:20
sridhar_ramdiga: codesearch doesn't get much hits..
*** sacharya has quit IRC06:20
sridhar_ramdiga: please investigate this portion (http-server to frontend falcon)06:20
digasridhar_ram: okay06:21
*** gongysh has joined #openstack-meeting06:21
sridhar_ramdiga: i'm specifically interested to know what zaqar is using to frontend falcon06:21
digasridhar_ram: okay06:21
sridhar_ramKanagarajM: btw, i agree w/ diga we should take up swagger work as a separate follow on06:22
digasridhar_ram: will talk to zaqar team06:22
sridhar_ramKanagarajM: api framework is a *huge* effort06:22
*** ijw has quit IRC06:22
KanagarajMsridhar_ram, ok06:23
sridhar_ramdiga: another question, I'm assuming post falcon we need to work on API microversion support (this is a openstack wide goal)06:23
digasridhar_ram: just one question, are we using same tacker API server for tacker UI Now ?06:23
sridhar_ramdiga: something to keep in mind as you are exploring06:23
sridhar_ramdiga: yes, UI uses tackerclient library with uses the tacker API server06:24
digasridhar_ram: yes, current spec is written based on those efforts06:24
sridhar_ramdiga: wonderful work so far!06:24
KanagarajMdiga, i see, that monasca api also uses falcon and its one of the highly scalable service. so falcon would be a right choice as you discovered. thanks.06:24
digaKanagarajM: :) YEs06:25
digasridhar_ram: Thanks :)06:25
sridhar_ramdiga: anything else?06:25
sridhar_ram.. on this topic ?06:25
*** pcaruana has joined #openstack-meeting06:25
digasridhar_ram: then in this case, we can go with HTTP for API server like zaqar & monasca using now06:25
*** efried has quit IRC06:26
sridhar_ramdiga: yes, adoption  is definitely a key factgor06:26
sridhar_ramalright almost out of time06:26
KanagarajMdiga, i think you could start the impl in parallel, by that time we could merge the spec.06:26
sridhar_ramKanagarajM: +106:26
digasridhar_ram: I will discuss on thi topic with zaqar & monasca team today.06:26
sridhar_ramdiga: sounds good06:26
digaKanagarajM: sridhar_ram : Sure06:27
sridhar_ram#topic Open Discussion06:27
*** openstack changes topic to "Open Discussion (Meeting topic: tacker)"06:27
Yanxing_anI have a few questions06:27
sridhar_ramJust 13 calendar days left until feature freeze / client library release06:27
Yanxing_anvnffg does not support EVENT , is it in plan?06:27
sridhar_ramplease get the reviews going06:27
digasridhar_ram: are we planning mid-cycle meetup in Feb ?06:28
sridhar_ramYanxing_an: good catch, those two feature landed in parallel .. it should've been fixed in Ocata06:28
gongyshYanxing_an,  there is no design to not use event. so you can fix it if you have time.06:28
sridhar_ramYanxing_an: I think we still have room to do it ..06:29
sridhar_ramYanxing_an: btw, welcome to the project! thanks for the reviews06:29
sridhar_ramFolks - we are out of time06:29
Yanxing_anok, i will to fix it06:29
Yanxing_antackerclient not support vnf-trigger command, is it need to add?06:29
sridhar_ramYanxing_an: let's take it offline in the #tacker channel06:30
sridhar_rambye everyone06:30
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"06:30
openstackMeeting ended Wed Jan 11 06:30:28 2017 UTC.  Information about MeetBot at . (v 0.1.4)06:30
openstackMinutes (text):
*** bobmel has joined #openstack-meeting06:30
*** s3wong has quit IRC06:30
*** KanagarajM has left #openstack-meeting06:31
*** xuan0802 has quit IRC06:32
*** joehuang has quit IRC06:32
*** sridharg has joined #openstack-meeting06:32
*** bobmel has quit IRC06:35
*** sheel has quit IRC06:37
*** efried has joined #openstack-meeting06:38
*** gongysh has quit IRC06:39
*** lpetrut has quit IRC06:43
*** sdake has quit IRC06:45
*** dkushwaha has left #openstack-meeting06:50
*** bobmel has joined #openstack-meeting06:51
*** ijw has joined #openstack-meeting06:54
*** bobmel has quit IRC06:56
*** adiantum has joined #openstack-meeting06:58
*** csomerville has joined #openstack-meeting06:59
*** lpetrut has joined #openstack-meeting07:00
*** cody-somerville has quit IRC07:02
*** adiantum has quit IRC07:08
*** adiantum1 has joined #openstack-meeting07:08
*** lpetrut has quit IRC07:08
*** tesseract has joined #openstack-meeting07:08
*** unicell has quit IRC07:10
*** unicell has joined #openstack-meeting07:10
*** adiantum1 is now known as adiantum07:10
*** nadya has joined #openstack-meeting07:11
*** bobmel has joined #openstack-meeting07:12
*** tbh has quit IRC07:13
*** bobmel has quit IRC07:17
*** lpetrut has joined #openstack-meeting07:17
*** xuhaiwei_ has quit IRC07:19
*** anilvenkata has joined #openstack-meeting07:20
*** andreas_s has joined #openstack-meeting07:21
*** makowals has joined #openstack-meeting07:21
*** korzen has joined #openstack-meeting07:23
*** dimtruck is now known as zz_dimtruck07:24
*** tiantian has joined #openstack-meeting07:26
*** amotoki has joined #openstack-meeting07:28
*** kjorgens_ has joined #openstack-meeting07:30
*** lpetrut has quit IRC07:33
*** kjorgensen has quit IRC07:33
*** kjorgens_ has quit IRC07:33
*** bobmel has joined #openstack-meeting07:33
*** kaisers1 has quit IRC07:33
*** rasca has joined #openstack-meeting07:35
*** hwoarang has quit IRC07:35
*** qwebirc99292 has joined #openstack-meeting07:36
*** bobmel has quit IRC07:38
*** kevinz has quit IRC07:40
*** kevinz has joined #openstack-meeting07:41
*** hwoarang has joined #openstack-meeting07:43
*** rbartal has joined #openstack-meeting07:44
*** ramishra has joined #openstack-meeting07:44
*** qwebirc99292 has quit IRC07:45
*** jrobinson has quit IRC07:46
*** ricolin has joined #openstack-meeting07:47
*** ralonsoh has joined #openstack-meeting07:48
*** zhihui has joined #openstack-meeting07:48
*** astarove has quit IRC07:49
*** kaisers has joined #openstack-meeting07:50
*** kaisers1 has joined #openstack-meeting07:50
*** yonglihe has joined #openstack-meeting07:50
*** ramishra has quit IRC07:52
*** KanagarajM has joined #openstack-meeting07:52
*** adiantum has quit IRC07:53
*** adiantum1 has joined #openstack-meeting07:53
*** ramishra has joined #openstack-meeting07:54
*** bkopilov has quit IRC07:55
*** hogepodge has quit IRC07:56
*** adiantum1 is now known as adiantum07:56
*** prazumovsky has joined #openstack-meeting07:56
ramishra#startmeeting heat08:00
openstackMeeting started Wed Jan 11 08:00:21 2017 UTC and is due to finish in 60 minutes.  The chair is ramishra. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: heat)"08:00
openstackThe meeting name has been set to 'heat'08:00
ramishra#topic roll call08:00
*** openstack changes topic to "roll call (Meeting topic: heat)"08:00
*** sacharya has joined #openstack-meeting08:00
*** therve has joined #openstack-meeting08:01
ramishraok, we've some attendance today:)08:02
*** iyamahat has joined #openstack-meeting08:02
ramishra#topic adding items to agenda08:02
*** openstack changes topic to "adding items to agenda (Meeting topic: heat)"08:02
ramishraI only have 2 topics.08:03
ramishra#topic ocata-3 status08:03
*** openstack changes topic to "ocata-3 status (Meeting topic: heat)"08:03
ramishraDoes not look very good, with one week left excluding this week;)08:04
therveYeah a good chunk of bugs08:05
*** sheeprine has quit IRC08:05
ramishraKanagarajM: what about
KanagarajMramishra, i will move to next cycle08:05
*** yamahata has quit IRC08:05
*** sacharya has quit IRC08:06
therveI don't think we have any critical bugs though08:06
*** ricolin has quit IRC08:06
*** ricolin has joined #openstack-meeting08:06
ramishratherve: no, I've not noticed any.08:06
ramishraI would request the owners to be realistic and move bugs/bps to next release.08:07
ramishraOtherwise I'll do it at the end;)08:07
thervetiantian, Are you working on ?08:08
openstackLaunchpad bug 1649900 in heat "Can't use conditions with depends_on" [Undecided,New] - Assigned to huangtianhua (huangtianhua)08:08
skraynevramishra: I think that it's the best option :)08:08
therveI might try to have a go otherwise08:08
tiantiantherve, sorry, no08:08
therveOK thanks08:08
*** iyamahat has quit IRC08:09
ramishratherve: do you know about bug 163730408:09
openstackbug 1637304 in heat "Zaqar queue can be inadvertently deleted" [Low,Triaged] - Assigned to Jason Dunsmore (jasondunsmore)08:09
ramishracan this be closed?08:09
therveramishra, Yeah I think so08:09
*** sheeprine has joined #openstack-meeting08:09
ramishratherve: ok, thanks!08:09
tiantiantherve, maybe I will look into it next week:)08:09
thervetiantian, Sure, don't hesitate to steal it back if I don't have a patch08:10
tiantiantherve, ok08:11
therve is an interesting one for people that care about lbaas08:13
openstackLaunchpad bug 1655303 in heat " OS::Neutron::LBaaS::Pool is missing the loadbalancer property" [Wishlist,New]08:13
therveIt may not be super hard08:13
*** edtubill has quit IRC08:13
*** strigazi_AFK is now known as strigazi08:13
therveramishra, I haven't checked, but could we include heat-agents in the ocata-3 release?08:14
therveI think the idea would be to follow heat release cycle if possible08:14
*** yuval_ has joined #openstack-meeting08:14
*** yuval_ is now known as yuval08:15
*** ramishra has quit IRC08:15
*** Cibo_ has joined #openstack-meeting08:16
*** amotoki has quit IRC08:16
*** ramishra has joined #openstack-meeting08:17
ramishrasorry was disconncted.08:17
*** Dmitrii-Sh has joined #openstack-meeting08:17
ramishraAre we sill on the same topic?08:18
tiantianyes :)08:18
*** Wenzhi has quit IRC08:18
ramishraok, sorry again.08:18
ramishrashould we move on?08:18
ramishrabefore disconnected as I was asking about bug 164326808:19
openstackbug 1643268 in OpenStack Compute (nova) "test_cancel_update_server_with_port failing intermittently" [Undecided,Incomplete]
*** lhx__ has quit IRC08:19
*** gcb has quit IRC08:19
*** Wenzhi has joined #openstack-meeting08:20
ramishraWe've disabled that test for the time being, anyone willing to look at it?08:20
ramishraok, it seems no one:)08:21
ramishramoving on..08:21
ramishra#topic props data de-duplication08:21
*** openstack changes topic to "props data de-duplication (Meeting topic: heat)"08:21
*** sudipto has quit IRC08:21
ramishra#link #link
*** salv-orl_ has quit IRC08:21
ramishrathe proposal is to land these patches and postpone rolling update tag claim for the next release.08:22
ramishraAnyone has any concerns. I did not see many respond to the ML thread.08:22
*** sudipto_ has quit IRC08:23
therveYeah not really08:23
*** sudipto has joined #openstack-meeting08:23
*** sudipto_ has joined #openstack-meeting08:23
therveIt's not great, but alternatives are worse :)08:24
*** Wenzhi has quit IRC08:24
ramishrayeah, I agree.08:24
ramishraBut we need to handle similar kind of db changes in the future.08:24
*** lpetrut has joined #openstack-meeting08:24
skraynevramishra: I supose, that silence means agreement :)08:25
*** Wenzhi has joined #openstack-meeting08:25
ramishraskraynev: yeah, but I understood that but wanted to be doubly sure that we all agree.08:25
ramishraok, that's all from my side.08:26
ramishra#topic open discussion08:26
*** openstack changes topic to "open discussion (Meeting topic: heat)"08:26
therveramishra, I haven't checked, but could we include heat-agents in the ocata-3 release?08:27
therveI think the idea would be to follow heat release cycle if possible08:27
therve(I think you missed that)08:27
ramishratherve: I'll check that.08:28
therveCool thanks08:28
ramishratherve: on the galnce v2 thing..08:28
ramishraI don't understand the relucatance to provide copy-from with v2 api?08:29
ramishraIf that's available we don't have to go the path of not supporting it the resource.08:29
therveI don't know about it. It doesn't look like it's there yet?08:30
*** lyarwood is now known as lyarwood_08:30
ramishrayeah, it's not there in v2. but available with v1.08:30
therve"There used to be copy-from too (which may or may not come back)."08:30
therveI don't want to think about it too much honestly08:31
tiantianglance v2 supports --file and --location (disabled by default)08:31
ramishraI understand the risk with locations. But not sure why copy-from was removed.08:31
therveIt's somewhat the same issue TBH08:31
*** lhx__ has joined #openstack-meeting08:31
therveWhat did you think about the heat client idea?08:31
ramishratherve: how? it's just one time thing. Making locations visible can be issue.08:32
therveramishra, Still that requires the backend to access some unknown data08:32
ramishraAlso location was treated as a store, but with copy-from, it copies the data from the external location to the default store.08:32
ramishraIf it's issue with glance then it's issue with heat too.08:33
*** gcb has joined #openstack-meeting08:33
tiantianyes, agree08:33
ramishratherve: yeah, I'm fine if we want to add it to heatclient.08:34
ramishraWe do that for templates, I think.08:34
ricolinI think the clint sounds better place to do08:34
thervericolin ?08:35
*** bobmel has joined #openstack-meeting08:35
ramishratherve: s/clint/client08:36
ricolintherve: Just agree with we add it to heatclient:)08:36
therveOK :)08:36
ricolinbad choice of words...08:37
ramishraok, anything else?08:37
therveNot from me08:37
ricolindeprecate non convergence?08:38
ramishraricolin: I'm not sure if we would like to do it so soon.08:38
ramishraMay be in pike?08:38
therveWe haven't made any progress on memory consumption AFAIK08:39
*** phil has joined #openstack-meeting08:39
therveIt's a pretty important issue to look at08:39
*** phil is now known as Guest496308:39
*** gcb has quit IRC08:40
ricolintherve: I think if tripleO's find with current improvement, we might want to start the deprecation process08:40
ricolinramishra: Pike sounds great08:40
*** bobmel has quit IRC08:40
thervericolin, Right. They are not right now.08:40
*** ricolin_ has joined #openstack-meeting08:41
*** yuval has quit IRC08:42
ramishraPlease spend sometime reviewing the patches in the queue.08:42
ramishraok, should we move back to heat?08:42
ricolin_My network breaks...08:42
ricolin_ramishra: going 108:42
ramishra#endmeeting heat08:43
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"08:43
openstackMeeting ended Wed Jan 11 08:43:07 2017 UTC.  Information about MeetBot at . (v 0.1.4)08:43
openstackMinutes (text):
*** KanagarajM has left #openstack-meeting08:43
*** therve has left #openstack-meeting08:44
*** mgoddard has joined #openstack-meeting08:45
*** ricolin has quit IRC08:45
*** Wenzhi has quit IRC08:45
*** ricolin_ has quit IRC08:50
*** bkopilov has joined #openstack-meeting08:51
*** ijw has quit IRC08:52
*** bobmel has joined #openstack-meeting08:57
*** cartik has joined #openstack-meeting08:59
*** sridhargaddam has joined #openstack-meeting08:59
*** rossella_ has joined #openstack-meeting08:59
*** sridharg has quit IRC08:59
*** ykatabam has joined #openstack-meeting09:00
*** bobmel has quit IRC09:01
*** mgoddard has quit IRC09:01
*** ricolin_ has joined #openstack-meeting09:02
*** mickeys has quit IRC09:03
*** jprovazn has joined #openstack-meeting09:07
*** sambetts|afk is now known as sambetts09:17
*** radez has quit IRC09:17
*** amotoki has joined #openstack-meeting09:22
*** toscalix has joined #openstack-meeting09:23
*** matrohon has joined #openstack-meeting09:25
*** makowals_ has joined #openstack-meeting09:26
*** makowals has quit IRC09:28
*** Wenzhi has joined #openstack-meeting09:30
*** Julien-zte has quit IRC09:34
*** Wenzhi has quit IRC09:35
*** saju_m has joined #openstack-meeting09:35
*** ntpttr_ has quit IRC09:41
*** ntpttr has joined #openstack-meeting09:42
*** mgoddard has joined #openstack-meeting09:43
*** kjorgensen has joined #openstack-meeting09:45
*** nadya has quit IRC09:45
*** Wenzhi has joined #openstack-meeting09:48
*** kjorgensen has quit IRC09:49
*** cartik has quit IRC09:50
*** Wenzhi has quit IRC09:52
*** ijw has joined #openstack-meeting09:52
*** xiaofandh12 has joined #openstack-meeting09:55
*** donghao has quit IRC09:57
*** ijw has quit IRC09:57
*** yuval has joined #openstack-meeting09:58
*** sridharg has joined #openstack-meeting09:59
*** bobmel has joined #openstack-meeting09:59
*** ijw has joined #openstack-meeting10:00
*** ygbo has joined #openstack-meeting10:01
*** zhihui has quit IRC10:01
*** lyarwood_ is now known as lyarwood10:02
*** sridhargaddam has quit IRC10:02
*** e0ne has joined #openstack-meeting10:02
*** epico has quit IRC10:03
*** prazumovsky has quit IRC10:03
*** lyarwood is now known as lyarwood_10:03
*** mickeys has joined #openstack-meeting10:04
*** bobmel has quit IRC10:04
*** nadya has joined #openstack-meeting10:05
*** ijw has quit IRC10:05
*** ayogi has quit IRC10:05
*** ayogi has joined #openstack-meeting10:07
*** mickeys has quit IRC10:08
*** acoles_ is now known as acoles10:14
*** yangyapeng has quit IRC10:17
*** sambetts is now known as sambetts|afk10:20
*** bobmel has joined #openstack-meeting10:20
*** nadya has quit IRC10:22
*** kjorgensen has joined #openstack-meeting10:24
*** bobmel has quit IRC10:25
*** hashar has joined #openstack-meeting10:26
*** kevinz has quit IRC10:27
*** megm has quit IRC10:27
*** alexpilotti has quit IRC10:27
*** zhihui has joined #openstack-meeting10:27
*** kjorgensen has quit IRC10:27
*** kjorgens_ has joined #openstack-meeting10:27
*** alexpilotti has joined #openstack-meeting10:28
*** megm has joined #openstack-meeting10:29
*** kjorgens_ has quit IRC10:32
*** rfolco has joined #openstack-meeting10:32
*** tbh has joined #openstack-meeting10:38
*** claudiub has joined #openstack-meeting10:38
*** HeOS has joined #openstack-meeting10:38
*** claudiub|2 has quit IRC10:41
*** bobmel has joined #openstack-meeting10:41
*** electrofelix has joined #openstack-meeting10:41
*** bobmel has quit IRC10:46
*** zhurong has joined #openstack-meeting10:46
*** aarefiev has joined #openstack-meeting10:47
*** aarefiev_afk has quit IRC10:50
*** nadya has joined #openstack-meeting10:50
*** Yanxing_an has quit IRC10:51
*** adiantum has quit IRC10:54
*** yamamoto_ has quit IRC10:59
*** gcb has joined #openstack-meeting11:00
*** ijw has joined #openstack-meeting11:02
*** bobmel has joined #openstack-meeting11:02
*** sacharya has joined #openstack-meeting11:02
*** nadya has quit IRC11:03
*** ricolin_ has quit IRC11:06
*** bobmel has quit IRC11:06
*** ijw has quit IRC11:07
*** sacharya has quit IRC11:07
*** matrohon has quit IRC11:09
*** yamamoto has joined #openstack-meeting11:12
*** adiantum has joined #openstack-meeting11:12
*** sudipto has quit IRC11:15
*** sudipto_ has quit IRC11:15
*** sdague has joined #openstack-meeting11:15
*** yamamoto has quit IRC11:17
*** bobmel has joined #openstack-meeting11:23
*** mgoddard has quit IRC11:26
*** mgoddard has joined #openstack-meeting11:26
*** yangyapeng has joined #openstack-meeting11:33
*** zhurong has quit IRC11:35
*** mgoddard has quit IRC11:35
*** mgoddard has joined #openstack-meeting11:38
*** bobmel_ has joined #openstack-meeting11:39
*** dims has joined #openstack-meeting11:39
*** JoseMello has joined #openstack-meeting11:40
*** bobmel has quit IRC11:41
*** askb has quit IRC11:43
*** jkilpatr has quit IRC11:48
*** nadya has joined #openstack-meeting11:50
*** tiantian has quit IRC11:50
*** tiantian has joined #openstack-meeting11:51
*** ociuhandu has joined #openstack-meeting11:52
*** Julien-zte has joined #openstack-meeting11:53
*** Guest4963 is now known as preisner11:53
*** claudiub|2 has joined #openstack-meeting11:54
*** tommylikehu_ has joined #openstack-meeting11:57
*** claudiub has quit IRC11:57
*** kjorgensen has joined #openstack-meeting11:57
*** huanxuan has quit IRC11:58
*** zhihui has quit IRC11:58
*** zhihui has joined #openstack-meeting11:59
*** arxcruz has quit IRC12:01
*** fanyishi has joined #openstack-meeting12:01
*** kjorgensen has quit IRC12:02
*** mpaolino has joined #openstack-meeting12:03
*** yuvalb has joined #openstack-meeting12:03
*** sankarshan_away is now known as sankarshan12:05
*** kevinz has joined #openstack-meeting12:06
*** jkilpatr has joined #openstack-meeting12:09
*** rtheis has joined #openstack-meeting12:09
*** sambetts|afk is now known as sambetts12:09
*** ayoung has joined #openstack-meeting12:14
*** amotoki has quit IRC12:14
*** yuval has quit IRC12:15
*** jkilpatr has quit IRC12:16
*** adiantum has quit IRC12:16
*** arxcruz has joined #openstack-meeting12:19
*** nick-ma_ has quit IRC12:22
*** amotoki has joined #openstack-meeting12:26
*** makowals_ has quit IRC12:26
*** makowals has joined #openstack-meeting12:26
*** Julien-zte has quit IRC12:29
*** jkilpatr has joined #openstack-meeting12:29
*** kevinz has quit IRC12:31
*** radez has joined #openstack-meeting12:32
*** kevinz has joined #openstack-meeting12:32
*** Wenzhi has joined #openstack-meeting12:32
*** tommylikehu_ has quit IRC12:33
*** raildo has joined #openstack-meeting12:35
*** janki has quit IRC12:35
*** Wenzhi has quit IRC12:37
*** janki has joined #openstack-meeting12:37
*** Julien-zte has joined #openstack-meeting12:40
*** thorst has joined #openstack-meeting12:41
*** fzdarsky has joined #openstack-meeting12:42
*** ayogi has quit IRC12:43
*** gcb has quit IRC12:45
*** Wenzhi has joined #openstack-meeting12:47
*** liuyulong_ has joined #openstack-meeting12:48
*** kevinz has quit IRC12:49
*** kevinz has joined #openstack-meeting12:50
*** amotoki has quit IRC12:50
*** tbh has quit IRC12:51
*** Wenzhi has quit IRC12:51
*** liuyulong has quit IRC12:51
*** claudiub has joined #openstack-meeting12:51
*** Jun-Sik has joined #openstack-meeting12:53
*** ttrifonov has quit IRC12:53
*** fanyishi has quit IRC12:54
*** claudiub|2 has quit IRC12:54
*** fanyishi has joined #openstack-meeting12:54
*** dongfeng has joined #openstack-meeting12:55
*** sudipto has joined #openstack-meeting12:56
*** sudipto_ has joined #openstack-meeting12:56
*** Yipei has joined #openstack-meeting12:57
*** yinxiulin has joined #openstack-meeting12:58
*** tommylikehu_ has joined #openstack-meeting12:59
*** tommylikehu_ has quit IRC12:59
*** tommylikehu_ has joined #openstack-meeting12:59
*** amotoki has joined #openstack-meeting13:00
*** WuCheng has joined #openstack-meeting13:00
*** RongHui11 has joined #openstack-meeting13:00
*** joehuang has joined #openstack-meeting13:00
*** ttrifonov has joined #openstack-meeting13:01
*** rfolco has quit IRC13:01
zhiyuan hi13:01
joehuang#startmeeting tricircle13:01
openstackMeeting started Wed Jan 11 13:01:54 2017 UTC and is due to finish in 60 minutes.  The chair is joehuang. Information about MeetBot at
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
joehuang#topic rollcall13:02
*** openstack changes topic to "rollcall (Meeting topic: tricircle)"13:02
joehuang#info joehuang13:02
zhiyuan#info zhiyuan13:02
RongHui11#info ronghui13:02
dongfeng#info dongfeng13:02
yinxiulin#info xiulin13:02
*** amotoki has quit IRC13:02
fanyishi#info fanyishi13:02
Yipei#info Yipei13:02
WuCheng#info WuCheng13:02
*** sacharya has joined #openstack-meeting13:03
joehuang#topic Ocata release preparation13:04
*** openstack changes topic to "Ocata release preparation (Meeting topic: tricircle)"13:04
joehuanghello, as planned, Ocata branch will be created on Jan.2413:04
*** dprince has joined #openstack-meeting13:04
joehuangIs there any challenge for your patches to be merged13:04
RongHui11not for tricircle but for trio2o13:05
zhiyuanthe implementation of xjob enhancement can be submitted tomorrow13:05
*** longxiongqiu has joined #openstack-meeting13:05
*** amotoki has joined #openstack-meeting13:05
*** adiantum has joined #openstack-meeting13:05
zhiyuanshare_vxlan is hard to catch the deadline13:05
joehuangthank you zhiyuan, the reliability is very important feature to be merged13:06
*** yamamoto has joined #openstack-meeting13:06
joehuangto Ronghui, Trio2o will not follow the schedule13:06
joehuangand no release plan for trio2o yet13:06
*** lijinghong has joined #openstack-meeting13:07
RongHui11 is hard to merge  and want some help13:07
*** sacharya has quit IRC13:08
*** lhx__ has quit IRC13:08
*** tovin07_ has joined #openstack-meeting13:09
*** matrohon has joined #openstack-meeting13:09
joehuangyes, if you want to make trio2o pass the gate test, the should be enhanced. I'll try to find time to help you13:11
joehuangany other chanllenge?13:11
zhiyuani think the tempest plugin also needs modification13:11
joehuangfor tricircle features13:11
RongHui11thank you so much :)13:11
*** qwebirc50747 has joined #openstack-meeting13:11
qwebirc50747hi there. were can I found the channel of the taas meeting?13:11
joehuangsorry, don't know13:12
joehuangyou may search taas meeting from google13:12
*** liukun has joined #openstack-meeting13:13
*** hejiawei has joined #openstack-meeting13:13
qwebirc50747I did. But I only able to find
qwebirc50747no specific channel13:14
joehuangplease review the patches for devstack for tricircle too, I have several patches in queue13:14
zhiyuanok, will review tomorrw13:14
joehuangto qwebirc50747, sorry, no idea13:15
*** tovin07_ is now known as tovin0713:15
joehuangfor vxlan networking, I think we need to plan a release after Ocata release,13:15
zhiyuanhi, you can get the info in this page :
joehuangso we can work hard for vxlan networking in the master branch at the same time13:16
joehuang#topic shadow_agent for VxLAN L2 networking/L3 DVR issue13:16
*** openstack changes topic to "shadow_agent for VxLAN L2 networking/L3 DVR issue (Meeting topic: tricircle)"13:16
joehuanghello, zhiyuan, do you have some progress to share on this feature13:17
RongHui11for the tricircle ,1)  i will try to clean remaining code of nova and cinder 2) the patch for remove codes got +2.  3) After the Qos spec patch merge, will submit the related codes ASAP13:17
*** ansmith_ has joined #openstack-meeting13:17
joehuangto Ronghui, thanks, great helpful13:17
zhiyuanyes, for external network, we can also use shadow agent/port to sync the tunnel information, creation of gateway port will also trigger l2 pop13:18
zhiyuanso we just create shadow port for gateway port in each pod13:19
zhiyuanshadow mac not tested yet13:19
zhiyuanshadow mac for DVR not tested yet13:19
joehuangthat means shade_agent will work for for L2/L3 networking via VxLAN13:19
*** electrocucarach has joined #openstack-meeting13:20
joehuangit's not so urgent13:20
joehuangwe can begin to work on the spec and code based on this idea13:20
joehuangshadow mac for DVR, I think it should be ok too13:21
zhiyuanyes, but i also find that l3 ha can not work properly with l2 pop, not sure if it's a bug or there's something wrong with my environment13:21
zhiyuanwith l2 pop, the tunnel between compute host and network host is not created, but if i turn off l2 pop, the tunnel can be created13:22
*** ramishra has left #openstack-meeting13:23
*** qwebirc50747 has quit IRC13:23
joehuangfurther investigation could be done in parallel, this is quite strange. maybe L3HA only work for centralized router, not for DVR?13:23
zhiyuanbut in my test, the router i created is centrailized, not DVR router13:23
joehuanghow about DVR router for L3HA?13:24
joehuangcentralized mode is called "legacy"13:24
zhiyuanthe combination of DVR and HA not tested yet13:24
zhiyuani think DVR is one kind of HA13:25
*** kjorgensen has joined #openstack-meeting13:25
joehuangit seems HA is for DVR13:26
*** kjorgensen has quit IRC13:26
*** kjorgensen has joined #openstack-meeting13:26
*** kjorgensen has quit IRC13:27
*** efried has quit IRC13:27
*** kjorgensen has joined #openstack-meeting13:28
joehuang#info shade_agent works for L3 networking (vxlan as bridge network) too13:28
zhiyuanboth of them are implemented in Juno, i think they can work separately13:28
*** amotoki has quit IRC13:28
*** kjorgensen has quit IRC13:28
joehuang#info L3HA has some issue with L2pop, need more investigation, but not so urgent13:29
*** kjorgensen has joined #openstack-meeting13:29
joehuang#topic shared_vlan confusion when creating vlan network in some specified region13:29
*** openstack changes topic to "shared_vlan confusion when creating vlan network in some specified region (Meeting topic: tricircle)"13:29
joehuanghello, I am writing the user guide for different scenario13:30
joehuangand I found one issue for shared_vlan concept13:30
joehuangif we want to create a network which only resides in one region and the network type is vlan13:31
joehuangthen we have to specify the physical network type as shared_vlan13:31
joehuangotherwise no other way to create a vlan network in local Neutron13:32
joehuangby default, the local network in central Neutron means the network type is decided by local neutron13:32
joehuangit could be vlan, vxlan or gre or else, it's undetermined13:32
joehuangbut shared_vlan, the concept is to create a network spanning into multiple openstack13:33
*** kjorgensen has quit IRC13:33
joehuangwith same vlan segment13:33
joehuangthis afternoon13:34
joehuangI discussed with zhiyuan13:34
joehuangabout it13:34
joehuangone idea is just use vlan as the physical network type, and using availability_zone_hints to limit where the network will reside13:35
*** mpaolino has quit IRC13:35
joehuangfor example, network( physical network type = vlan, az_hint=az1,az2) means the network could be presented in az1 and az213:36
joehuangif only one az is specified, then the network will be limited to one openstack, for example network( physical network type = vlan, az_hint=az1)13:37
joehuangif no az_hint is specified, then means the network could be spread into any openstack13:37
*** mgoddard has quit IRC13:38
RongHui11no matter the network spread in which az and the physical network type need to be vlan?13:38
joehuangif you create a vlan network13:39
*** amotoki has joined #openstack-meeting13:39
*** aloga has quit IRC13:39
joehuangthe physical network type is not must to be vlan, it could be vxlan too, but currently only shared_vlan supported13:39
*** sdake has joined #openstack-meeting13:39
joehuangthis idea is already described in the spec:
RongHui11got it13:40
joehuangin this section: A Cross Pod L2 Networking Creation13:40
*** rbak has joined #openstack-meeting13:42
joehuanghow do you think about to update the shared_vlan to vlan, just use az_hint to limit the scope of the network ?13:43
*** sdake_ has joined #openstack-meeting13:43
zhiyuani think it's fine, two questions (1) do we need to keep local network type (2) how about vxlan network type since shared_vxlan is not supported yet13:44
RongHui11same question for (2)13:45
*** lhx__ has joined #openstack-meeting13:45
*** annegentle has joined #openstack-meeting13:45
*** sdake has quit IRC13:46
joehuang1) for local network, we can keep it there for the case where no parameter will be specified creating a network13:46
joehuang2) for shared_vxlan, I think we can deal with it as vlan network13:47
*** WuCheng_ has joined #openstack-meeting13:47
joehuangjust use vxlan for shared_vxlan13:47
zhiyuanthen how about user creates a vxlan network with more than one az in az_hint?13:48
*** rbak has quit IRC13:48
joehuangthen this vxlan network could be spread into these azs13:49
zhiyuani know, but currently cross pod vxlan network is not supported13:49
joehuangjust raise exception, not supported yet13:50
joehuangno need13:50
joehuangone second13:50
*** WuCheng has quit IRC13:51
joehuangin some scenario, for example SDN controller13:51
joehuangthey can talk with each other via BGP13:51
joehuangfor just create vxlan network at the bottom region as usual,13:51
joehuangwe need to add one indicator13:52
joehuangif it's by L2pop, shadow_agent, it's not supported13:52
joehuangif it's done by SDN controller, then it's ok, just like what vlan has done13:53
zhiyuandiscuss this in our release notes?13:53
*** neiljerram has joined #openstack-meeting13:53
*** aloga has joined #openstack-meeting13:54
joehuangshared_vlan needs to be updated ASAP, before Jan 2413:54
joehuangwho can help this?13:54
*** julim has joined #openstack-meeting13:55
yinxiulini will do it ASSP13:56
*** david-lyle has quit IRC13:56
joehuangok, thank you xiulin13:56
joehuang#action network type "shared_vlan" should be simplified to vlan13:57
yinxiulinyou are welcome13:57
joehuang#topic open discussion13:57
*** openstack changes topic to "open discussion (Meeting topic: tricircle)"13:57
joehuangany other topic13:57
*** lblanchard has joined #openstack-meeting13:58
joehuangok, thank you very much13:58
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"13:58
openstackMeeting ended Wed Jan 11 13:58:44 2017 UTC.  Information about MeetBot at . (v 0.1.4)13:58
openstackMinutes (text):
*** crinkle_ has quit IRC13:59
*** tongli has joined #openstack-meeting13:59
*** amotoki has quit IRC13:59
*** david-lyle has joined #openstack-meeting13:59
*** crinkle_ has joined #openstack-meeting13:59
*** WuCheng_ has quit IRC13:59
*** dongfeng has quit IRC13:59
*** baoli has joined #openstack-meeting13:59
*** joehuang has quit IRC13:59
*** baoli has quit IRC14:00
*** fanyishi has quit IRC14:00
*** Jun-Sik has quit IRC14:00
*** RongHui11 has quit IRC14:00
*** Yipei has quit IRC14:00
*** baoli has joined #openstack-meeting14:00
*** lijinghong has quit IRC14:01
*** lamt has joined #openstack-meeting14:01
*** yamamoto has quit IRC14:01
*** yamamoto has joined #openstack-meeting14:02
*** links has quit IRC14:02
*** ayoung has quit IRC14:03
*** kylek3h has quit IRC14:03
*** mriedem has joined #openstack-meeting14:03
*** kaisers_ has joined #openstack-meeting14:04
*** jprovazn has quit IRC14:06
*** diga has quit IRC14:06
*** bobmel_ has quit IRC14:06
*** yamamoto has quit IRC14:07
*** jprovazn has joined #openstack-meeting14:07
*** dmorita has joined #openstack-meeting14:08
*** hejiawei has quit IRC14:08
*** ntpttr has quit IRC14:09
*** yinxiulin has quit IRC14:10
*** preisner has quit IRC14:11
*** claudiub|2 has joined #openstack-meeting14:12
*** ntpttr has joined #openstack-meeting14:13
*** dmorita has quit IRC14:13
*** electrocucarach is now known as electrocucaracha14:13
*** claudiub has quit IRC14:16
*** david-lyle has quit IRC14:16
*** fguillot has joined #openstack-meeting14:17
*** cdub has joined #openstack-meeting14:17
*** annegentle has quit IRC14:18
*** claudiub has joined #openstack-meeting14:20
*** sdake has joined #openstack-meeting14:20
*** Swami has joined #openstack-meeting14:21
*** zz_dimtruck is now known as dimtruck14:22
*** electrocucaracha has left #openstack-meeting14:22
*** claudiub|2 has quit IRC14:23
*** sdake_ has quit IRC14:23
*** VW has joined #openstack-meeting14:24
*** yamamoto has joined #openstack-meeting14:30
*** VW_ has joined #openstack-meeting14:31
*** VW has quit IRC14:31
*** ioden has joined #openstack-meeting14:31
*** kevinz has quit IRC14:31
*** longxiongqiu has quit IRC14:32
*** jgrassler has joined #openstack-meeting14:34
*** yamamoto has quit IRC14:34
*** yamamoto has joined #openstack-meeting14:35
*** mgoddard has joined #openstack-meeting14:36
*** adiantum1 has joined #openstack-meeting14:37
*** adiantum has quit IRC14:39
*** adiantum1 is now known as adiantum14:39
*** amotoki has joined #openstack-meeting14:39
*** Chengli has joined #openstack-meeting14:40
*** lamt has quit IRC14:40
*** yamamoto has quit IRC14:40
*** korzen has quit IRC14:40
*** yamamoto has joined #openstack-meeting14:43
*** jonesn has joined #openstack-meeting14:44
*** makowals has quit IRC14:45
*** longxiongqiu has joined #openstack-meeting14:46
*** bobmel has joined #openstack-meeting14:48
*** dimtruck is now known as zz_dimtruck14:49
*** tongli has quit IRC14:49
*** yamamoto has quit IRC14:49
*** sdake_ has joined #openstack-meeting14:51
*** cleong has joined #openstack-meeting14:51
*** cloudm2 has joined #openstack-meeting14:51
*** gouthamr has joined #openstack-meeting14:52
*** VW_ has quit IRC14:52
*** VW has joined #openstack-meeting14:53
*** liukun has quit IRC14:53
*** bobmel has quit IRC14:54
*** sdake has quit IRC14:54
*** makowals has joined #openstack-meeting14:56
*** chenying has quit IRC14:58
*** ljxiash has joined #openstack-meeting14:58
*** bobmel has joined #openstack-meeting14:59
*** rbak has joined #openstack-meeting15:00
*** galstrom_zzz is now known as galstrom15:02
*** bobh has joined #openstack-meeting15:02
*** designbybeck has joined #openstack-meeting15:04
*** efried has joined #openstack-meeting15:04
*** sacharya has joined #openstack-meeting15:04
*** lhx__ has quit IRC15:04
*** iyamahat has joined #openstack-meeting15:04
*** hongbin has joined #openstack-meeting15:06
*** spzala has joined #openstack-meeting15:06
*** spzala has quit IRC15:06
*** spzala has joined #openstack-meeting15:06
*** sacharya has quit IRC15:08
*** bobmel_ has joined #openstack-meeting15:08
*** nkrinner is now known as nkrinner_afk15:09
*** bobmel has quit IRC15:10
*** adrianofr_ has joined #openstack-meeting15:12
*** janki has quit IRC15:12
*** claudiub|2 has joined #openstack-meeting15:12
*** caboucha has joined #openstack-meeting15:12
*** tommylikehu_ has left #openstack-meeting15:13
*** edtubill has joined #openstack-meeting15:14
*** Julien-zte has quit IRC15:15
*** pradk has joined #openstack-meeting15:15
*** claudiub has quit IRC15:16
*** david-lyle has joined #openstack-meeting15:17
*** kylek3h has joined #openstack-meeting15:17
*** rbudden has joined #openstack-meeting15:19
*** galstrom is now known as galstrom_zzz15:19
*** zz_dimtruck is now known as dimtruck15:21
*** hogepodge has joined #openstack-meeting15:21
*** david-lyle has quit IRC15:21
*** sdake_ has quit IRC15:22
*** yamahata has joined #openstack-meeting15:22
*** sdake has joined #openstack-meeting15:22
*** nklenke has joined #openstack-meeting15:25
*** sacharya has joined #openstack-meeting15:25
*** raj_singh_ has joined #openstack-meeting15:26
*** spotz_zzz is now known as spotz15:27
*** ljxiash has quit IRC15:27
*** donghao has joined #openstack-meeting15:28
*** bobmel has joined #openstack-meeting15:28
*** markvoelker has quit IRC15:28
*** baoli has quit IRC15:28
*** jaugustine has joined #openstack-meeting15:29
*** markvoelker has joined #openstack-meeting15:29
*** xiaofandh12 has quit IRC15:30
*** bobmel_ has quit IRC15:31
*** sridharg has quit IRC15:31
*** longxiongqiu has quit IRC15:32
*** ayoung has joined #openstack-meeting15:32
*** fnaval has joined #openstack-meeting15:32
*** nklenke_ has joined #openstack-meeting15:33
*** markvoelker has quit IRC15:35
*** ayoung has quit IRC15:38
*** sankarshan is now known as sankarshan_away15:38
*** diablo_rojo_phon has joined #openstack-meeting15:38
*** adiantum has quit IRC15:40
*** galstrom_zzz is now known as galstrom15:41
*** galstrom is now known as galstrom_zzz15:41
*** spzala has quit IRC15:44
*** spzala has joined #openstack-meeting15:44
*** spzala has quit IRC15:45
*** TxGirlGeek has joined #openstack-meeting15:45
*** spzala has joined #openstack-meeting15:45
*** Leo_ has joined #openstack-meeting15:45
*** Swami_ has joined #openstack-meeting15:47
*** lhx__ has joined #openstack-meeting15:48
*** guyr-infinidat has joined #openstack-meeting15:49
*** wiggin15 has joined #openstack-meeting15:49
*** Swami has quit IRC15:49
*** Sukhdev has joined #openstack-meeting15:50
*** ayoung has joined #openstack-meeting15:50
*** yamamoto has joined #openstack-meeting15:50
*** wxy| has joined #openstack-meeting15:50
*** saju_m has quit IRC15:51
*** aslezil_ has joined #openstack-meeting15:51
*** tommylikehu_ has joined #openstack-meeting15:52
*** shintaro has joined #openstack-meeting15:52
*** armax has joined #openstack-meeting15:52
*** duartea__ has quit IRC15:53
*** diablo_rojo has joined #openstack-meeting15:53
*** tommylikehu_ has quit IRC15:55
*** xyang1 has joined #openstack-meeting15:56
*** markvoelker has joined #openstack-meeting15:57
*** claudiub has joined #openstack-meeting15:59
smcginnis#startmeeting Cinder16:00
openstackMeeting started Wed Jan 11 16:00:04 2017 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at
smcginnisping dulek duncant eharney geguileo winston-d e0ne jungleboyj jgriffith thingee smcginnis hemna xyang1 tbarron scottda erlon rhedlind jbernard _alastor_ bluex patrickeast dongwenjuan JaniceLee cFouts Thelo vivekd adrianofr mtanino yuriy_n17 karlamrhein diablo_rojo jay.xu jgregor baumann rajinir wilson-l reduxio wanghao thrawn01 chris_morrell stevemar watanabe.isao,tommylikehu mdovgal ildikov16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: Cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
smcginniswxy viks ketonne16:00
smcginnis#topic Announcements16:00
*** openstack changes topic to "Announcements (Meeting topic: Cinder)"16:00
*** shintaro has quit IRC16:00
smcginnis#link Review focus16:00
smcginnisPTG is coming up!16:00
smcginnis#info Need to register for the PTG if you have not already done so.16:00
smcginnis#link PTG info and registration16:00
smcginnis#link PTG Hotel reservations16:01
diablo_rojoHello :)16:01
smcginnisJust wanted to note for everyone that registering for the PTG hotel through the link helps.16:01
smcginnisAs part of holding the event there, there is some obligation to fill some of the rooms.16:01
smcginnisAnd there's free breakfast!16:01
diablo_rojoYes please make sure you book through our reserved hotels :)16:02
*** jungleboyj has joined #openstack-meeting16:02
smcginnis#info Need to start planning for the PTG16:02
diablo_rojoYay breakfast!16:02
*** claudiub|2 has quit IRC16:02
smcginnis#link PTG topic planning etherpad16:02
*** bobmel_ has joined #openstack-meeting16:02
jungleboyjBreakfast?  Did I miss something?16:02
smcginnisBreakfast? :)16:02
*** yamamoto has quit IRC16:02
jungleboyjsmcginnis: True story.16:02
*** bobmel has quit IRC16:02
*** bobmel_ has quit IRC16:03
smcginnis#info Summit call for presentations is open16:03
*** lamt has joined #openstack-meeting16:03
smcginnisLet's get some good storage sessions for the Summit.16:03
smcginnis#link Summit CFP16:03
*** bobmel has joined #openstack-meeting16:03
smcginnisIf you have ideas for anything you would like to talk about that would be beneficial, please submit a proposal.16:03
smcginnisIt may or may not make it, but it definitely won't if you don't submit it. ;)16:04
*** lhx__ has quit IRC16:04
jgriffithsmcginnis I would like to discuss climate change16:04
smcginnisAnd this one might actually be its own topic, but just to make sure driver maintainers know, we would like CG support migrated to generic groups by P-1 if possible.16:05
smcginnisjgriffith: How Cinder is destroying the climate!16:05
jungleboyjjgriffith: You can do that after you solve the problem.16:05
smcginnisjgriffith: Good chance of getting in. ;)16:05
jgriffithsmcginnis yes!  It's all our fault16:05
xyang1just want to make sure driver maintainers see the email about migrating CGs to groups16:05
*** viks has joined #openstack-meeting16:05
smcginnisAnd vendors. :D16:05
smcginnis#link Migrate CGs to Generic Volume Groups update16:05
smcginnis#topic New Cinder Attach/Detach API16:06
*** openstack changes topic to "New Cinder Attach/Detach API (Meeting topic: Cinder)"16:06
smcginnisildikov and jgriffith: All yours.16:06
ildikovsmcginnis: tnx :)16:06
*** ijw has joined #openstack-meeting16:06
ildikovso the topic is not new I think most of you already know that new Attach/Detach API is on it's way b jgriffith16:06
ildikovwe desperately need code review and attention from the team at this point16:07
ildikovCinder patch: #link
ildikovclient patch: #link
jgriffithand I'm working on updating the client patch this morning16:07
jgriffithit's out of date with some of the changes just FYI16:07
smcginnisNot sure the bot picks it up inless it starts with the #16:07
smcginnis#link Cinder patch16:07
smcginnis#link Client patch16:08
* dulek signs in for cinder patch.16:08
smcginnisjgriffith: The service side is up to date though, correct? Or changes coming on that.16:08
*** anilvenkata has quit IRC16:08
ildikovif there's any questions regarding to this that we should discuss here, please  let us know16:08
ildikovwe also started to investigate to enable Cinder v3 in Nova, scottda has a patch up for it16:09
*** Swanson has joined #openstack-meeting16:09
*** salv-orlando has joined #openstack-meeting16:09
*** bobmel has quit IRC16:09
ildikovthat's hitting EndpointNotFound error for seemingly no good reason16:09
scottdaYeah, I'm not sure mriedem was on board with making that the default for Nova yet...16:09
scottdanor am I sure we are ready. We need it running in some Nova jobs first.16:10
mriedemcinder v3?16:10
mriedemnot without the damn thing actually working :)16:10
smcginnismriedem: You're so picky.16:10
*** bobmel has joined #openstack-meeting16:10
scottdaYOu are picky16:10
ildikovscottda: just at least investigating why the config option does not work as expected16:10
mriedemi'd like to enable cinder v3 in the placement job for nova, where our other bleeding edge stuff goes16:10
*** Chengli has left #openstack-meeting16:10
hemnait's the openstack way.16:10
hemnause it before it works.16:10
jungleboyjmriedem: Details, details!16:10
mriedemthe problem is passing a config through from the project-config to devstack-gate to devstack to configure nova,16:11
smcginnisYeah, working out the issues and making sure it _can_ work is a good first step.16:11
scottdaOK, well it's getting starved out in my queue...I haven't even looked lately16:11
mriedemwhen we don't have post-config working yet for that plumbing16:11
*** ijw has quit IRC16:11
smcginnisThen by Pike we will have had v3 out for 2 releases and it should be safer considering it for the default.16:11
ildikovsmcginnis: the service side patch has a few comments, but I would still encourage everyone to look into it earlier rather than later16:11
scottdaI've gotten it to work manually, so it's a config/infra thing I believe16:11
mriedemwell, ^ infra job plumbing is the 2nd issue16:11
mriedemmaking it work is the first16:11
*** jessegler has joined #openstack-meeting16:11
smcginnisildikov: +116:11
ildikovsmcginnis: BTW, what is the deadline to get this landed?16:12
ildikovsmcginnis: in Ocata I mean :)16:12
*** annegentle has joined #openstack-meeting16:13
*** rbartal has quit IRC16:13
smcginnisildikov: I think if we aren't extrememly close by O-3, we better wait until Pike.16:13
smcginnisildikov: Ideally before O-3.16:13
ildikovdulek: tnx for signing in :)16:13
smcginnisildikov: But jgriffith likes to land large features at code freeze, so we'll see. :P16:13
*** Rockyg has joined #openstack-meeting16:13
* jgriffith looks away16:14
* jungleboyj remembers jgriffith scolding me for that in the past. ;-)16:14
ildikovsmcginnis: LOL, if it's shoehorned in Ocata still I think I'm fine :)16:14
bswartzdo as I say not as I do!16:14
jgriffithWe can wait til Pike, no worries16:14
smcginnisSo everyone please review the patches if you can.16:14
jungleboyjbswartz: :-)16:14
jgriffithTBF the patches have been up for 4 months now16:14
*** tovin07 has quit IRC16:15
smcginnisjgriffith: Yeah, we can. Would be great if we can get it in O though so there's a chance Nova may use it in P.16:15
ildikovsmcginnis: would make it better to move forward with the Nova parts to have the initials in Cinder as soon as we can16:15
scottdayeah, I think we merge things late because we review and test late...16:15
smcginnisildikov: Totally agree.16:15
jungleboyjildikov: ++16:15
smcginnisscottda: That's a fair statement too.16:15
ildikovsmcginnis: :)16:15
jungleboyjThis is one of those things that will just drag out forever.16:15
*** winston-1 has joined #openstack-meeting16:15
smcginnisjungleboyj: Shsuh16:15
*** shintaro has joined #openstack-meeting16:15
jgriffithSo what's strange about all this is this is what I thought the glorious almighty micro-versioning madness was supposed to buy us16:16
ildikovsmcginnis: +1 :)16:16
smcginnisjgriffith: Rebases?16:16
jgriffithsmcginnis haha!  Well it's certainly GREAT for that16:16
scottdamicroversion just lets you add the new API, and NOva can see it's there and use it.16:16
*** bkopilov has quit IRC16:16
*** matrohon_ has joined #openstack-meeting16:16
jungleboyjsmcginnis: Shsuh?16:16
smcginnisjungleboyj: sdjalksdghvailuga16:16
jungleboyjsmcginnis: a;dsfjadslfjal;sdjfa;ldsfkja16:16
jgriffithscottda we're not doing anything differently than we ever have :(16:17
jgriffithwe're just making it *harder*16:17
jgriffithand it's madness that we've added 23 versions to the API in the last 4 months16:17
scottdaWell, it's really just semver...16:17
mdovgaljungleboyj, is it elfin language? :)16:17
scottdaAdd a new api, bump the minor version.16:17
smcginnisjgriffith: This is part of the reason I would prefer to batch changes and only bump on release. We're just constantly stepping on each other's toes.16:18
jgriffithusability is going to suck16:18
jgriffithsmcginnis YES PLEASE!!!!16:18
smcginnisThen you would know O is 3.12, P is 3.13, etc.16:18
jungleboyjmdovgal: Must be.16:18
e0ne  smcginnis: +116:18
diablo_rojosmcginnis, +116:18
jgriffithsmcginnis I'd even take it further... have an 'N' release every each release16:18
scottdaAs long as you don't deploy from Master...16:18
ildikovsmcginnis: that would be a good compromise I think, had the same thought a while back16:18
hemnathe current model makes sense if you are using master for deployment though.16:18
winston-1smcginnis: +116:18
jgriffithsmcginnis ie when we open Pike we bump the number to V416:19
e0nehemna: good point16:19
*** matrohon has quit IRC16:19
jgriffitheverything new goes in V416:19
scottdaWe support deploying from master..but if we want to stop that, OK.16:19
jgriffithwhen we open Q we go to V516:19
hemnaotherwise you'd have lots of changes going into the API during the release cycle and no version change.  :(16:19
jgriffithscottda you can still deploy from master that way16:19
jungleboyjjgriffith: Isn't that what we used to do ... Oh you mean always bump it with the release.16:19
smcginnisscottda: I still would like to see justification why we absolutely need to support CD. Our contract should just be on official release boundaries, as far as I'm concerned.16:19
jgriffithscottda and sorry, but that whole thing is a farce anyway16:19
jgriffithpeople can barely deploy from release without heroic efforts from distros16:20
scottdaI don't care one way or another. It's just he model that exists.16:20
jgriffithscottda I know.. and it's also being pushed by the cross-project thing16:20
jgriffithbut I think it sucks16:20
scottdaAnd Cinder can go it's own way, but the rest of openstack thinks differently...16:20
jgriffithand I'm not afraid to voice my opinion16:20
smcginnisIs it actually stated somewhere in writing that we must support continuous deployment?16:20
hemnaalso, if you don't bump the micro version on the API change, then we are back to basically the old model, which was also broken.16:20
hemnableh, whatevs16:20
scottdaYeah, we've had releases of the client that have features that might or might not be in the do you know?16:21
jgriffithhemna I've never understood what exactly was *broken*16:21
*** neiljerram has quit IRC16:21
*** jaypipes has joined #openstack-meeting16:21
smcginnishemna: I'm fine having a bunch of API changes in one microversion. You just need to know what given release corresponds to what microversion for the feature you want.16:21
jgriffithother than lack of process and documentation16:21
jgriffithsmcginnis +116:21
hemnasmcginnis, who coordinates doing the version bump in 5 different people doing patches?16:22
jgriffithI suppose this is a PTG discussion16:22
hemnathis will be a nightmare IMHO.16:22
jgriffithand will have significant ramifications from the overlords in other OS projects16:22
smcginnishemna: You just do it once when the new cycle starts, then you wait and do it again when the next one does.16:22
jgriffithhemna why?16:22
* jungleboyj loves how the PTG agendas develop before a meeting. :-)16:22
hemnayou bump the version with no real changes at the start of the cycle?16:22
*** salv-orl_ has joined #openstack-meeting16:22
smcginnisAnd in the mean time, if you specify a microversion and the api is not there - stop running off of master.16:23
hemnamakes absolutely no sense to me.16:23
jgriffithhemna IMHO what we're doing now is a nightmare, and the VERY FEW customers I have that are newer than Kilo at this point have been asking how the hell the versiioning stuff works16:23
smcginnishemna: You will have changes in the cycle though.16:23
smcginnisAnd until the cycle is released, who cares?16:23
jungleboyjhemna:  Why?  Concerned that there will be no changes for the new version?16:23
jgriffithhemna yep, because it's a new release of the prject/software16:23
scottdaSo, people might not like semver, but it's a bit of a standard. Breaking changes, you up the major version. non-breaking change you up the minor version16:23
jungleboyjI guess that could happen, but unlikely.16:23
jgriffithhemna god forbid we version our software16:23
hemnaok if you say so.  it makes no sense to me.  uber complicated that nobody will understand.16:24
smcginnisSeems much less complicated, but I guess that's just me.16:24
jungleboyjIsn't what we do more complicated.16:24
hemnaanyway, I'll shut up since I'm in the minority.16:24
jgriffithhemna fair enough16:24
hemnanever mind.16:24
jungleboyjYou have to specify a special version to get a function?16:24
smcginnisjungleboyj: A microversion.16:24
jungleboyjsmcginnis: I hear you.16:24
jgriffithhemna different perspectives I guess, I see the micro madness as uber complex and confusing and the alternate super easy :)16:24
smcginnisjungleboyj: Right now it is for each and every API change.16:25
hemnahow is versioning each API change complicated?   I seriously don't get that.16:25
hemnayou changed something, it's a new version.16:25
jungleboyjsmcginnis: I know, that is confusing to me.  :-)16:25
jgriffithhemna have you tried using it?16:25
hemnanow we'll have random versions for something that never happened or didn't change anything, just because....16:25
*** salv-orlando has quit IRC16:25
scottdaIt'd be nice to know what users think...16:25
smcginnishemna: I doubt we would have a release with no API changes.16:25
hemnasmcginnis, you just suggested changing the API version at the start of a release.16:26
smcginnishemna: But fair enough, then we bump the microversion with the first patch that actually does change it.16:26
jgriffithhemna oh.. that explains the confusion sorry16:26
DuncanTjgriffith: I have tried using it. Literally the only thing I find a problem is there's no 'just use the max version' for show commands where I want to see everything that the server can tell me16:26
smcginnishemna: Because I know we never have a release without an API change.16:26
hemnaI have to bail to take my kid to school.  l8rs16:26
jgriffithhemna we should chat later and I'll try and explain what I meant.  I don't think it's what your envisioning16:26
jungleboyjsmcginnis: That could work.16:26
smcginnisIt's a DuncanT!16:26
bswartzDuncanT: that's by design16:26
jgriffithDuncanT yeah.. but you're "Duncan" :)16:26
smcginnisOK, I think we've gone down a rabbit hole. Let's get back to the agenda.16:27
smcginnis#topic Manual Testing for Ocata release16:27
*** openstack changes topic to "Manual Testing for Ocata release (Meeting topic: Cinder)"16:27
DuncanTjgriffith: I think batching during a release can work just as well iif you abandon the idea that you can deploy from trunk and have a sane system16:27
jgriffithsorry.. that was completely my fault16:27
jungleboyjA DuncanT is good to see!16:27
smcginnisscottda: Save us please! :)16:27
jungleboyjIt is good luck.16:27
DuncanTjgriffith: I just fail to understand why 1 version bump per release is easier to understand16:27
scottdaThere's a page for things that need testing before the release ^^^^16:27
DuncanTjungleboyj: I may be vanishing for good from cinder soon :-( We'll see16:28
scottdaWe discovered in Newton that we have an ad hoc way of testing things that lack Tempest tests...16:28
*** bkopilov has joined #openstack-meeting16:28
scottdai.e Just hope that someone tests them.16:28
* jungleboyj doesn't want to hear that!16:28
smcginnisscottda: :)16:28
scottdaGeneric groups, upgrades, DB migrations, AA/HA,...these need to be tested, and others.16:28
scottdaSome folks are already doing this, either because they own the feature, or care , or whaever16:29
smcginnisI think good old fashioned exploratory testing can find a lot of things.16:29
scottdaSo, please add thing to the etherpad as needed, and sign up if you are testing.16:29
*** TxGirlGeek has quit IRC16:29
* e0ne is worried how many manual tests we have to run before the each release16:29
scottdaThat will at least help us identify gaps.16:29
scottdae0ne: Yeah, getting automated tests is a separate issue...16:29
scottdae0ne: That is the ideal. But in reality, this is our situation.16:30
smcginnise0ne: Probably not a full suite for every release. I think it just helps from time to time to actually try everything out in a given functional area and make sure it's sane.16:30
scottdaAnd I think in the past, things have been missed.16:30
smcginnisWe've had plenty of cases where tests pass just fine, but the logic of the thing is completely broken.16:30
e0newhy we didn't care about functional and integration tests during feature development?16:31
*** galstrom_zzz is now known as galstrom16:31
scottdaYeah, this is just a way to track what should be tested, and what is tested.16:31
scottdae0ne: I'm 100% for a better way to ensure adding tests with the feature.16:31
scottdaBut, we still have today's reality. Do we want to release with noone testing this stuff?16:31
e0nescottda: IMO, it should be one of our priorities for Pike16:32
DuncanTscottda: Just -2 everything until current test coverage is 100% :-)16:32
smcginnisTesting and stabilization was supposed to be a priority for Ocata. So I'd love to see at least some of it done now.16:32
smcginnisDuncanT: Hah, full stop on everything. ;)16:32
scottdaOK, well I'm just wanting to point people to the etherpad. Things need testing, and it's nice to know if someone is testing. That's all.16:33
DuncanTsmcginnis: Kill or cure16:33
smcginnisThanks scottda16:33
smcginnis#topic Status of DRBD16:33
*** shintaro has quit IRC16:33
*** openstack changes topic to "Status of DRBD (Meeting topic: Cinder)"16:33
jungleboyjscottda: Good effort to start.  Thanks!16:33
smcginnisscottda: Still you. :)16:33
scottdaON the ML it was pointed out that drbdmanage isn't GPL'd any more.16:34
scottdaNeeds some explicit user agreement.16:34
scottdaDo we even care about DRBD?16:34
scottdaThe tests fail 100% of the time.16:34
smcginnisLinbit does.16:34
smcginnisAnd I did hear from them that they were going to try to address the concerns.16:34
e0nelet's make it unsupported16:34
smcginnisBut I have not seen any progress there.16:34
scottdaWell, someone needs to get the tests to pass, for one thing, or they are just noise16:34
*** mickeys has joined #openstack-meeting16:35
e0neor get CI working16:35
smcginnisSo I think at this point we should remove the test and mark it unsupported.16:35
scottdaSo, prior to the GPL issue, the tests are broken.16:35
scottdasmcginnis: +116:35
smcginnisInfra should only be running tests for 100% compliant open drivers.16:35
*** mmalik4 has joined #openstack-meeting16:35
DuncanTFor sure they should be running their own CI now16:35
*** neiljerram has joined #openstack-meeting16:36
e0nesmcginnis: +116:36
smcginnisOK, I can put up patches later to remove the job and mark it unsupported.16:36
smcginnisUnless someone else wants to grab that.16:36
DuncanTThe mix of licenses we have make providing a cinder distribution that 'just works' for all supported drivers not legally possible, but I've no longer got any skin in that game and the discussion was going round in circles16:36
smcginnisDuncanT: I think that's going to be another one of those long drawn out discussions.16:37
smcginnisOK, I'll put that on my todo list for today.16:37
smcginnisAny other thoughts or opinions before I move on?16:38
smcginnisOK, thanks again scottda16:38
smcginnis#topic Adding Bandit as a non-voting gate16:38
*** openstack changes topic to "Adding Bandit as a non-voting gate (Meeting topic: Cinder)"16:38
smcginnisrarora: You around?16:38
*** andreas_s has quit IRC16:39
rarorawe had brought this up a few weeks ago and the consensus was to look more into cleaning up the results so there are fewer false positives and see how keystone likes having it in their gate16:39
smcginnisrarora: So I'll admit it's been awhile since I ran it, but last time I ran bandit there were pages of warnings and errors...16:39
e0nerarora: did we fix a lot of false positive errors?16:39
smcginnisAnd not one of them was valid.16:39
*** mickeys has quit IRC16:40
raroraSo with filtering for medium severity and confidence, if I remember correctly there are roughly 100 bugs that bandit is coming up with16:40
*** reedip_outofmemo has joined #openstack-meeting16:40
rarorafor the entirety of the project16:40
rarorawhich imo isn't too bad16:41
raroraand then there are some common things that can be nosec'd so overall I think that it would be a good idea still to add this as a non-voting gate16:41
smcginnisrarora: Any idea if any were legitimate though? 100 bugs of noise actually seems very bad to me.16:41
smcginnisrarora: Don't get me wrong, I like the project and see its value.16:42
DuncanTrarora: I think the nosec patch needs to happen before it goes in the gate or it just becomes yet another thing in the gate we ignore, which we've already got lots of16:42
smcginnisDuncanT: +116:42
e0neDuncanT: +216:42
smcginnisI agree, clean up first, then look at making it a regular job.16:43
raroraI do see what you are saying. Is the nosec patch so that we can ignore things using the config rather than commenting a nosec?16:43
smcginnisrarora: IIRC, does it just need a #nosec tag in the code like we do now for #noqua for pep8 things?16:43
jonesnwhat I looked at was a #nosec in the code.16:44
DuncanTrarora: Whichever is gets us a sane & informative result set from bandit gate16:44
DuncanTrarora: Adding 100 #nosec might be ugly though.... disabling some of the nosier tests would probably be better16:44
smcginnisI think sorting through maybe a dozen false alarms is OK. Sorting through 100+ false alarms just ends up being noise and getting ignored.16:45
rarorayes, disabling lib xml and things like binding to all interfaces should help out16:45
raroraalso not sure what people's positions are on things like disabling warnings for md5 hashing becuase if the hash is not used for security purposes it's a non-issue and that is usually the case16:46
smcginnisrarora: I think all of those I looked at last time were not used for security purposes.16:46
DuncanTrarora: Better to disable too much initially and get a clean gate run16:46
DuncanTrarora: As we #nosec or fix the code, we can enable more tests16:47
*** neiljerram has quit IRC16:47
smcginnisDuncanT: That might be the better approach. Otherwise we're not very likely to get to the passing state.16:47
DuncanTrarora: A gate test that always gives even 1 false positive is nearly useless in practice16:47
raroraDuncanT: Well the point of this, even if it nearly always would give false positives, is that it would help with people not committing new code with security issues16:48
*** bobmel_ has joined #openstack-meeting16:48
jonesnDo you think bandit could ever be configured to a point where we are guaranteed no false positives?16:48
raroraNo I do not16:48
smcginnisrarora: They're not likely to notice that they are adding new issues if the test always fails anyway though.16:48
rarorasmcginnis: fair point16:49
DuncanTrarora: I'm saying disable nearly everything if needed, and turn each test on in a patch with the relevant #nosec to keep a clean pass16:49
DuncanTrarora: Better that than another gate test that nobody reads because there are always warnings16:49
jesseglerMakes sense to me16:49
xyang1DuncanT: what about making it non-voting first?16:50
smcginnisIt will probably always have to be non-voting.16:51
*** bobmel has quit IRC16:51
smcginnisOK, we have one more topic and <9 minutes left. I think for now, our preference would be to clean up the false error reporting, then we can look at adding it as a regular non-voting job.16:51
raroraDuncanT: I see where you are coming from but at the same time, I feel like if it gets ignored by most people oh well, it's non-voting and isn't that resource intenseive and it at least gives people an easy way to take a look if they want to.16:51
rarorasmcginnis: okay, no problem :)16:52
rarorajust glad we got to talk about it16:52
smcginnisWe just have too many non-voting jobs that are ignored when they fail.16:52
smcginnisIt decreases the value of the Jenkins results.16:52
smcginnisrarora: Yes, thank you for discussing it. I think anything we can do to increase security awareness is a good thing.16:52
diablo_rojo8 min left as a heads up16:53
smcginnisOK, I'll move on. Thanks rarora16:53
smcginnis#topic Avoid merging Tempest tests that break Cinder CI16:53
*** openstack changes topic to "Avoid merging Tempest tests that break Cinder CI (Meeting topic: Cinder)"16:53
smcginnisscottda: You again16:53
SwansonIf it is non voting I traditionally assume a fail is half expected and don't look.16:53
scottdaThat tempest test for snapshot_manage merged, and broke a bunch of CIs16:53
scottdaI don't recognize a single Cinder reviewer.16:53
scottdaSeems kinda broken to merge that in the first place, IMO16:54
scottdaBTW, revert patch up is:
smcginnisscottda: Totally16:54
scottdaNot sure what to do. Maybe this will urge caution from Tempest reviewers.16:54
smcginnisThis might be the better answer than just reverting it:16:54
scottdaJust seems kinda bad.16:54
smcginnis#link Manage feature flag16:54
smcginnisBut I agree that shouldn't have landed in the first place.16:55
smcginnisGood to have the test coverage. But I think even for the drivers that do support manage/unmanage, some require different identifiers and things.16:55
scottdaOK. Didn't know how many CIs were broken, or whom was affected by this.16:56
smcginnisSo not sure how useful that test actually is.16:56
smcginnisscottda: I was affected.16:56
smcginnisscottda: But the interesting thing is one of our drivers does support the feature, so the failure was expected.16:56
DuncanTscottda: It passed for LVM though, right?16:56
jungleboyjSad that the CI's caught the problem and no one noticed.16:56
smcginnisBut our other storage does support it and failed for other reasons.16:56
scottdaJust woke up to the issue, and thought I'd bring it up. Maybe Tempest team will ping us next time for a review or opinion.16:56
smcginnisjungleboyj: Problem is for tempest, I think only LVM is run to validate those patches.16:57
*** acoles is now known as acoles_16:57
*** wiggin15 has quit IRC16:57
jungleboyjsmcginnis: Oh ... :-(16:57
smcginnisOh, and ceph, which was the only thing specifically called out to skip the test.16:57
scottdaDuncanT: I reckon it passed for LVM, but that is not enough. Not sure if there's a process to prevent this, or just "raise awareness".16:58
smcginnisRaise awareness is probably all we can hope for at this point.16:58
smcginnis2 minutes16:58
scottdaOK, that's it for this.16:58
smcginnis#topic Open discussion16:58
*** openstack changes topic to "Open discussion (Meeting topic: Cinder)"16:58
jungleboyjBegs better coordination with the tempest team though.16:58
smcginnisAny quick last minute (literally) things?16:58
jungleboyjAny idea what the p-1 date will be?16:59
*** neiljerram has joined #openstack-meeting16:59
jungleboyjSwanson: P-116:59
smcginnisNot up yet:
smcginnisI think I guesstimated somewhere when that would be. I'll see if I can find that.16:59
jungleboyjsmcginnis: Right.  Guessing that will be early May ?16:59
dulekjungleboyj: There's probably a review going in openstack/releases?16:59
smcginnisdulek: Oh right, there is actually.17:00
smcginnisThat's time. Thanks everyone.17:00
jungleboyjsmcginnis: Ok, good enough.17:00
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"17:00
openstackMeeting ended Wed Jan 11 17:00:16 2017 UTC.  Information about MeetBot at . (v 0.1.4)17:00
openstackMinutes (text):
*** viks has left #openstack-meeting17:00
*** nadya has quit IRC17:01
*** mickeys has joined #openstack-meeting17:01
*** xyang1 has quit IRC17:02
*** jonesn has left #openstack-meeting17:03
*** cloudm2 has quit IRC17:03
*** winston-1 has left #openstack-meeting17:03
*** matrohon_ has quit IRC17:03
*** Leo_ has quit IRC17:05
*** e0ne has quit IRC17:06
*** Leo_ has joined #openstack-meeting17:06
*** Sukhdev has quit IRC17:08
*** ijw has joined #openstack-meeting17:08
*** wxy| has quit IRC17:09
*** ygbo has quit IRC17:10
*** briancurtin has quit IRC17:11
*** ijw has quit IRC17:12
*** jaypipes has quit IRC17:12
*** pcaruana has quit IRC17:12
*** nadya has joined #openstack-meeting17:14
*** Swami_ has quit IRC17:14
*** krenczewski has joined #openstack-meeting17:17
*** tesseract has quit IRC17:20
*** sdake_ has joined #openstack-meeting17:22
*** bobmel_ has quit IRC17:22
*** unicell has quit IRC17:23
*** nadya has quit IRC17:24
*** bobmel has joined #openstack-meeting17:24
*** iyamahat has quit IRC17:25
*** sdake has quit IRC17:25
*** yamahata has quit IRC17:25
*** kjorgensen has joined #openstack-meeting17:25
*** bobmel has quit IRC17:27
*** jessegler has quit IRC17:27
*** bobmel has joined #openstack-meeting17:27
*** bobmel has quit IRC17:28
*** strigazi is now known as strigazi_AFK17:29
*** bobmel has joined #openstack-meeting17:31
*** baoli has joined #openstack-meeting17:36
*** lpetrut has quit IRC17:38
*** wiggin15 has joined #openstack-meeting17:39
*** wiggin15 has quit IRC17:39
*** hashar has quit IRC17:41
*** dmorita has joined #openstack-meeting17:42
*** eharney has joined #openstack-meeting17:44
*** jaugustine has quit IRC17:45
*** dmorita has quit IRC17:47
*** dmorita has joined #openstack-meeting17:49
*** nadya has joined #openstack-meeting17:50
*** caboucha has quit IRC17:50
*** sudipto has quit IRC17:50
*** sudipto_ has quit IRC17:50
*** jaypipes has joined #openstack-meeting17:52
*** rossella_ has quit IRC17:52
*** iyamahat has joined #openstack-meeting17:53
*** aarefiev is now known as aarefiev_afk17:54
*** georgk has joined #openstack-meeting17:54
*** yamahata has joined #openstack-meeting17:54
*** Swami has joined #openstack-meeting17:54
*** Cibo_ has quit IRC17:58
*** bh526r has joined #openstack-meeting17:58
*** vipuls has joined #openstack-meeting17:58
bh526r#startmeeting gluon18:00
openstackMeeting started Wed Jan 11 18:00:18 2017 UTC and is due to finish in 60 minutes.  The chair is bh526r. Information about MeetBot at
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
bh526r#topic Roll Call18:00
*** openstack changes topic to "Roll Call (Meeting topic: gluon)"18:00
bh526rHi Paul18:00
bh526r#info Bin Hu18:00
*** nadya has quit IRC18:01
tomhambleton#info Tom Hambleton18:01
kamal___#info kamal hussain18:01
pcarver#info Paul Carver18:01
*** ociuhandu has quit IRC18:01
georgk#info Georg Kunz18:01
krenczewski#info Kamil Renczewski18:02
bh526r#topic Admin Update18:02
*** openstack changes topic to "Admin Update (Meeting topic: gluon)"18:02
jinliHi everyone18:02
jinli#info JinLi18:02
bh526rBecause we won't have room in PTG Atlanta, it is impractical to gather there18:02
*** ralonsoh has quit IRC18:03
bh526rBut we also need a f2f as the last sprint before Ocata release.18:03
bh526rI propose to have a Gluon F2F in Bay Area in the week of Feb 6-1018:03
bh526rDoes anyone have any preference over those dates?18:04
*** galstrom is now known as galstrom_zzz18:04
tomhambletonI have an issue with Feb. 8. How about Feb. 6-7?18:04
bh526rThat is good to me. Does Feb 6-7 work for everyone?18:05
*** toscalix has quit IRC18:05
jinliI am ok18:05
pcarverWhat's the agenda? I'm on the east coast and not sure whether it's worthwhile to travel to bay area18:05
bh526rfinish last minutes coding and testing18:06
*** ijw has joined #openstack-meeting18:08
*** bobmel_ has joined #openstack-meeting18:08
bh526r#info Because it is impractical to have a Gluon group meeting in PTG Atlanta due to logistics issue as we discussed last week (Jan 4)18:08
diablo_rojo_phonThere will be apace for impromptu meetings at the PTG if you're interested in getting together.18:09
*** hurricanerix has joined #openstack-meeting18:09
bh526r#info in order to complete coding and testing before Ocata release in the week of Feb 20-24, all agreed to have a Gluon F2F in Bay Area in the week of Feb 6-10.18:10
*** galstrom_zzz is now known as galstrom18:10
*** reedip_outofmemo has quit IRC18:11
bh526r#info the goal is to complete any last-minute coding and testing18:11
bh526r#info The dates are Feb 6 and Feb 7 considering the availability of core developers18:12
*** bobmel has quit IRC18:12
*** bobh has quit IRC18:12
bh526rI see, thank you diablo_rojo_phon.18:12
ildikovbh526r: would you need a room for all 5 days?18:12
*** tonytan4ever has joined #openstack-meeting18:12
ildikovbh526r: or you could list the days you would like to gather?18:13
*** ijw has quit IRC18:13
*** claudiub|2 has joined #openstack-meeting18:15
*** david-lyle has joined #openstack-meeting18:15
*** david-lyle has quit IRC18:16
*** david-lyle has joined #openstack-meeting18:16
ildikovbh526r: we might have a small room available, but would need to know which days to check for you to ensure we don't have collisions18:16
*** rasca has quit IRC18:17
*** unicell has joined #openstack-meeting18:17
bh526rI see, thank you Ildiko. Let me communicate with some other core members, because not every core member is on the IRC yet.18:18
*** claudiub has quit IRC18:19
*** sambetts is now known as sambetts|afk18:19
bh526rThe goal of F2F in Bay Area is to complete coding and testing before Feb 20.18:20
*** jaugustine has joined #openstack-meeting18:20
ildikovbh526r: it would be great if you can gather on the PTG18:20
ildikovbh526r: or the PTG as well so that you can interact with the relevant project teams too and socialize the project further18:21
ildikovbh526r: please ping me if you have more info and we can look into the options then18:21
bh526rsounds good, and thank you Ildiko18:22
*** Leo_ has quit IRC18:22
ildikovbh526r: sure, np18:23
bh526r#topic Gluon Tasks18:25
*** openstack changes topic to "Gluon Tasks (Meeting topic: gluon)"18:25
bh526r#info above links are for informational purpose18:26
bh526r#info to understand where we are, and rest of work before release18:26
bh526r#topic Status Update18:26
*** openstack changes topic to "Status Update (Meeting topic: gluon)"18:26
*** reedip_outofmemo has joined #openstack-meeting18:27
bh526r#info 1. Authentication and Access Control18:27
bh526rKamal, further update?18:27
kamal___no I don't have any updates. Hoping to send a review this week18:28
*** awiedlea has joined #openstack-meeting18:28
bh526r#info Kamal is working on another patch, and will send for review this week18:28
*** awiedlea has quit IRC18:28
bh526r#info 2. OpenContrail's Mechanism Driver18:28
bh526r#info Kamil submitted another patchset on Jan 1018:29
bh526r#info with updated repo of Mechanism Driver, and updated readme18:29
*** rbak has quit IRC18:29
*** ianychoi has quit IRC18:30
krenczewskiI am not sure if pushing install script to gluon repo is good idea18:30
bh526r#info There were several comments on the patch18:30
krenczewskiIf I understood your e-mail correctly18:30
bh526rI see. How big size is the script?18:30
krenczewskiThis would lead to maintain the same script in two separate rpositories18:30
krenczewskiNot big but it would be annoying and error prone18:31
*** lpetrut has joined #openstack-meeting18:31
bh526rGot you. The script is already in another repo18:31
bh526rPerhaps you only need to update readme, and with instruction and pointer to get the script18:31
*** TxGirlGeek has joined #openstack-meeting18:32
*** amotoki has quit IRC18:32
krenczewskiI think that pointing to repository is enough18:32
krenczewskiThere are installation instructions18:33
bh526rWill the script then install the Mechanism Driver?18:33
krenczewskiwhat do you think?18:33
bh526rThen that's good. It seems a clean way18:33
krenczewskiOk, great18:33
*** guyr-infinidat has quit IRC18:34
krenczewskiAnd once I got some help from Ian I create Fuel and Apex installer options18:34
bh526r#info Kamil has written a script to install Contrail Mechanism Driver based on comments within the patch18:34
bh526rGreat, thank you Kamil18:34
krenczewskiand add Devstack installation option18:34
*** nadya has joined #openstack-meeting18:35
bh526r#info Kamil will update the readme with the pointer to script and installation instruction18:35
*** mgoddard has quit IRC18:35
bh526r#info Those seem sufficient for manual installation18:36
*** ntpttr has quit IRC18:36
*** absubram has quit IRC18:36
bh526r#info After that, Kamil will work with Ian, Georg etc. for options of being installed by installers, such as Devstack, Apex, Fuel etc.18:36
bh526r#info in order to support the effort of integration and installation in OPNFV18:37
bh526rGreat work, thank you Kamil18:37
bh526r#info 3. Testing18:37
georgkbh526r: sorry, I need to leave now18:38
*** rossella_ has joined #openstack-meeting18:38
bh526rSure, no problem. Georg18:38
georgkbh526r: if there is anything for me to so, drop me an email18:38
bh526rHave a good night18:38
georgkthank you, bye18:38
bh526rSure, thank you Georg18:38
*** guyr-infinidat has joined #openstack-meeting18:39
bh526r#info Jin's patches 405689 and 418177 were approved and merged on Jan 1018:39
*** absubram has joined #openstack-meeting18:39
*** adisky_ has quit IRC18:39
*** aslezil_ has quit IRC18:39
bh526r#info 4. Shim Layer for Open Daylight18:39
*** electrofelix has quit IRC18:39
*** ntpttr has joined #openstack-meeting18:40
bh526r#info Patch 407388 and 413011 have been comprehensively reviewed, commented and updated in the past a few weeks18:40
bh526r#info 413011 was finally approved and merged on Jan 1018:40
*** raj_singh_ has quit IRC18:41
bh526r#info 407388 was abandoned accordingly18:41
bh526r#info 5. Gluon API Specification18:41
*** kjorgensen has quit IRC18:42
bh526r#info Patch 411918 has been comprehensively reviewed, commented and updated in the past a few weeks18:42
*** s3wong has joined #openstack-meeting18:42
bh526r#info It was approved and merged on Jan 1018:42
*** georgk has quit IRC18:42
bh526r#info Tom is working on revising the code for the updated API spec18:42
bh526r#info 6. Devstack Integration18:43
*** guyr-infinidat has quit IRC18:43
bh526r#info It is still work in progress18:43
*** kjorgensen has joined #openstack-meeting18:43
*** rbak has joined #openstack-meeting18:43
bh526r#info 7. Add Entry Points to our Neutron Plugin18:43
bh526r#info The patch 404390 was merged on Jan 1018:44
bh526r#info 8. Nova enhancement18:44
*** ociuhandu has joined #openstack-meeting18:45
bh526r#info As we reviewed and discussed last week, Ian has updated the patchset (#4) on Jan 1018:46
bh526r#info Ian continues to work with Nova team on it.18:46
bh526rAny question or other update?18:47
bh526r#topic AOB18:48
*** openstack changes topic to "AOB (Meeting topic: gluon)"18:48
bh526ranything else to discuss?18:49
bh526rIf nothing else to discuss, we can adjourn the meeting18:50
bh526r#info Meeting adjourned18:50
bh526rThank you everyone and bye all18:50
tomhambletonBye all18:50
jinliBye everyont18:50
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"18:50
openstackMeeting ended Wed Jan 11 18:50:40 2017 UTC.  Information about MeetBot at . (v 0.1.4)18:50
openstackMinutes (text):
*** Rockyg has quit IRC18:51
*** bh526r has quit IRC18:55
*** lpetrut has quit IRC18:55
*** abalutoiu has joined #openstack-meeting18:58
*** rhochmuth has joined #openstack-meeting18:58
*** csomerville has quit IRC18:58
*** zara_the_lemur__ has joined #openstack-meeting18:58
*** csomerville has joined #openstack-meeting18:58
*** aslezil_ has joined #openstack-meeting18:58
*** krenczewski has quit IRC18:59
*** dmorita has quit IRC18:59
SotKanyone here for the storyboard meeting?19:00
funginobody here but us chickens19:00
rhochmuthi am from the monasca team19:00
*** ekcs has joined #openstack-meeting19:00
SotK#startmeeting storyboard19:00
openstackMeeting started Wed Jan 11 19:00:55 2017 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: storyboard)"19:00
openstackThe meeting name has been set to 'storyboard'19:01
diablo_rojoHello :)19:01
diablo_rojoThanks for coming rhochmuth :)19:01
SotK#link Agenda (that is semi-updated)19:01
rhochmuththanks for inviting me19:01
*** Leo_ has joined #openstack-meeting19:01
SotKwelcome folks!19:01
SotKI don't think we have any announcements or urgent items today19:02
*** reedip_outofmemo has quit IRC19:02
SotK#topic In Progress Work19:02
*** openstack changes topic to "In Progress Work (Meeting topic: storyboard)"19:02
*** mtanino has joined #openstack-meeting19:02
*** Wenzhi has joined #openstack-meeting19:03
zara_the_lemur__I've finally sent a patch to get rid of our placeholder operator deployment docs19:04
* SotK hasn't managed to get much done in this last week19:04
diablo_rojozara_the_lemur__, nice :)19:04
zara_the_lemur__I'd rather a really nice operator guide, but the current thing was worse than nothing19:04
zara_the_lemur__since it made a user think there was a guide, then they'd click it and get 'guide todo'19:04
*** VW has quit IRC19:04
zara_the_lemur__story for that more generally is:!/story/200053519:05
zara_the_lemur__patch is:19:05
* SotK is still vaguely conflicted about it19:06
zara_the_lemur__fair enough19:06
diablo_rojoSotK, conflicted why?19:06
zara_the_lemur__(I partly sent it to prompt discussion on it and maybe someone would take on the task of making a better ops guide)19:07
SotKI worry that we will remove it and then never get round to putting a proper one there19:07
*** spzala has quit IRC19:07
SotKbut then the counter argument is that we are equally likely to have the misleading stub there and never get round to putting a proper one there19:07
*** spzala has joined #openstack-meeting19:07
zara_the_lemur__yeah, that was my reason for leaving the stub up so long19:07
diablo_rojoHa ha fair enough19:07
zara_the_lemur__and I didn't get round to it19:07
*** Wenzhi has quit IRC19:08
zara_the_lemur__is anyone here atm able or interested to make a better ops guide?19:08
zara_the_lemur__*able to or interested in19:08
* zara_the_lemur__ gives up on fixing that sentence19:08
persiaFolk who are current operators would be the most exciting of volunteers19:09
diablo_rojozara_the_lemur__, maybe we could work on that in conjunction with a summit talk for storyboard?19:09
diablo_rojoUnless someone else wants it :)19:09
*** briancurtin has joined #openstack-meeting19:09
zara_the_lemur__diablo_rojo: my trouble atm is setting up a good environment for the deployment19:09
diablo_rojozara_the_lemur__, Ah, fair enough.19:10
* SotK is not seeing many volunteers, so I guess I will think more and become unconflicted :)19:11
*** spzala has quit IRC19:12
zara_the_lemur__also awaits reviews19:12
* SotK will will review after this meeting19:12
zara_the_lemur__either of the 'fix the logic a bit first' kind or the 'merge this' kind, not sure if people are waiting for me there19:12
diablo_rojoI will review too. I need to get in on all that fun :)19:12
SotKAnything else in progress that needs attention brought to it?19:13
zara_the_lemur__my misc install instructions fixes are still awaiting further +1s19:14
*** jkilpatr has quit IRC19:14
zara_the_lemur__I apparently sent a bunch of install instruction things this week19:14
* SotK cannot offer extra +1s19:14
*** dmorita has joined #openstack-meeting19:14
zara_the_lemur__oh, and AJaeger's docs change:19:15
*** rossella_ has quit IRC19:15
zara_the_lemur__that's one I've reviewed, awaiting more eyes19:15
* diablo_rojo opened a bunch of tabs19:16
zara_the_lemur__brb plugging in computer19:16
zara_the_lemur__nothing else to note there19:16
* SotK merges AJaeger's patch19:16
SotKok, lets move on19:17
SotK#topic Migration scripts19:17
*** openstack changes topic to "Migration scripts (Meeting topic: storyboard)"19:17
SotKI believe that it is a good time to see if our LP migration scripts still work?19:17
diablo_rojoSo, do we know the last time they were used for sure?19:18
*** rlpple has joined #openstack-meeting19:18
*** rlpple has quit IRC19:18
SotKI think they were used when craige was investigating phabricator stuff19:18
*** rlpple has joined #openstack-meeting19:18
SotKso probably late 2015/early 201619:19
*** dmorita has quit IRC19:19
diablo_rojoNot so bad then19:19
*** rossella_ has joined #openstack-meeting19:19
diablo_rojoSo, we need to test those to see what all breaks so we can hopefully get Monasca rolling on moving over.19:20
zara_the_lemur__if it's any help, they were used to import infra stories to storyboard before that; some unusual characters weren't converted properly19:20
SotKthat is help, we need to fix that bug19:20
diablo_rojounusual characters?19:21
zara_the_lemur__it's something we should test on a small scale first, hang on, will find the story19:21
* zara_the_lemur__ remembers it because she went through removing the oddness so GETs worked properly19:21
SotKterminal colour codes and stuff iirc19:21
* zara_the_lemur__ finds!/story/29219:22
diablo_rojoInteresting. Okay well if its just a few things to get cleaned up that shouldn't be bad. Does anyone have something we could test it on?19:22
zara_the_lemur__I would imagine would be a good place?19:23
SotKI suggest we try importing a real LP project into storyboard-dev19:23
persiaThere were a few classes of characters that were not converted properly.  These at least included A) ANSI control codes, B) some multibyte characters (but not all multibyte characters, strangely), and C) some cases where different sorts of markup seemed to be overly escaped.19:23
diablo_rojoSotK, so we could hypothetically just try it with Monasca to storyboard-dev and so long as it all looks happy then we can move forward with the real migration?19:25
persiaSpecifically related to Monasca: what is the post-migration plan for things like ?19:25
openstackLaunchpad bug 1368661 in Glance Client "Unit tests sometimes fail because of stale pyc files" [Undecided,In progress] - Assigned to Shu Muto (shu-mutou)19:25
SotKit strikes me we will also need to decide how to encode the priorities opf of tasks from LP19:25
SotKdiablo_rojo: yes, I reckon so19:26
persiarhochmuth: How do you think the monasca team will want to encode priorities in the future?19:26
diablo_rojopersia, good question :)19:26
rhochmuthi'm not sure19:26
*** dmorita has joined #openstack-meeting19:26
rhochmuthare you referring to high, undecided, …19:27
rhochmuthfor example, the priority to resolve a bug or implment a feature19:27
persiaThere are two different common ways of expressing priority in Storyboard, used today.  One is to use tags (e.g. "high-priority").  The other is to use worklists (gather the most important into a worklist, with developers expected to pull their next activity from that worklist).19:27
persiaYes.  LP has a "Priority" field, with Critical, High, Medium, Low, Undecided.  Storyboard doesn't have that field.19:28
rhochmuthi think the tags would be the best approach19:28
rhochmuthfor bugs19:28
rhochmuththe worklists i see being more useful for tasks associated with a new feature or blueprint19:29
rhochmuthSo, I think the Priority field would be useful19:29
rhochmuthwithout that we can't order bugs for resolution19:29
persiaSpecifically for the migration, do you think it makes sense to create tags as part of migration?19:29
*** jkilpatr has joined #openstack-meeting19:30
persiaOr do you think it makes sense to populate a worklist in Priority order.19:30
rhochmuthi see, i think tags make sense19:30
fungialso, with automatic worklists based on story tags, you can sort of emulate the old bug importance implementation in lp19:30
persiaAh, good point19:30
*** pvaneck has joined #openstack-meeting19:30
rhochmuthwell, now i might want to change my mind since you put it that way19:31
fungiyou can have an automatic worklist for high-importance bugs, and tag them with monasca-bug-high or something19:31
rhochmuthso, if you can create worklists by based on tags, that sounds like what we woudl want19:31
rhochmuthsounds like it would work well19:31
persiarhochmuth: Note that automatic worklists aren't editable directly, so if you go that way, and you want to change a priority, you'd go to the individual story, and change the tag.19:32
*** s3wong has quit IRC19:32
* SotK returns and complains about internet trouble19:32
fungiand then their tasks would automatically appear in some "monasca's high importance bugs" worklist19:32
*** amotoki has joined #openstack-meeting19:32
* SotK would also recommend some kind of worklist approach19:32
persiaBut I think that's the easiest to implement in a migration script, especially tags with names like project-importance (e.g. monasca-high)19:33
rhochmuthi think that flow would work19:33
persiaAnd if a team wants to change later, it's not that hard to create a manual worklist with the most important things on the top.19:33
rhochmuthso, within a project, you have several worklists19:33
rhochmuthone list for high, another for medium, ...19:34
persiaWhereas, I think if the migration script goes straight to worklists, it's hard for teams to migrate to something using tags.19:34
SotKpersia: I concur19:34
fungirhochmuth: worklists aren't tied to projects. anyone can create one19:34
rhochmuthand then the bugs are tagged and automatically put into a worklist19:34
persiarhochmuth: And if you need to add cross-project things to the worklist, you can use the same tag, even on another project.19:34
zara_the_lemur__bear in mind that you can filter a tag by project and name, so there's no need to use something like 'monasca-high' if you filtered by 'monasca' and 'high-priority'19:34
SotKthough, I'm not sure the project name would be needed, you could just have the worklist contain tasks in the Monasca project in stories with the relevant tag19:34
fungizara_the_lemur__: great point19:35
rhochmuthi think i understand19:35
persiazara_the_lemur__: That makes it hard to emulate something like , where different projects have different priorities for the same story.19:35
openstackLaunchpad bug 1368661 in Glance Client "Unit tests sometimes fail because of stale pyc files" [Undecided,In progress] - Assigned to Shu Muto (shu-mutou)19:35
persiaErr, different importance.19:35
fungialso true19:35
SotKhm, good point19:35
rhochmuthwell, i'm not sure that case where there are different priorities is as important19:36
rhochmuthseems like an outlier19:36
persiaI think that long-term, if people like to use tags for importance, some common tags may come into use, but for the migration script, I think we want to preserve as much information from LP as possible.19:36
SotKseems sensible to me19:37
zara_the_lemur__makes sense19:37
*** krtaylor has quit IRC19:37
*** VW has joined #openstack-meeting19:37
zara_the_lemur__(also, that reminds me, I believe we need task-tag filtering in the webclient)19:38
persiarhochmuth: I've worked on a number of differnt projects that use LP (both inside and outside openstack), and find it fairly normal that different projects have different priorities for the same issue (depending on what else needs doing, whether there are deadlines, etc.)19:38
rhochmuthgot it, a lot of learnings for me19:38
rhochmuththx persia19:38
SotKso to summarise, we need to fix the priority handling in the migration script to use tags, and we need to fix the encoding bug19:39
SotKand we will then run a test import against storyboard-dev19:39
persiaSotK: Yes, but I have another issue to raise :)19:40
SotKpersia: go on19:40
fungilonger term having fine-grained ordering in team-specific and personal worklists may provide a more usable model, though i expect it will take a while for our community to acclimate since it is a fairly significant paradigm shift19:40
persiaIf there is not a "flag day", where all the projects migrate, what is the right thing to do with LP bugs that affect multiple projects, where one of those projects is migrating, and another project is not migrating?19:40
persiafungi: +119:40
SotKah, like the one you linked19:41
fungipersia: if there are only a handful, those bugs will diverge, but comments in lp that are missing from sb will get added at reimport later19:41
* persia spent the beginning of the meeting poring through Monasca bugs to find an example like that19:41
persiafungi: And comments in sb will never be in LP?19:41
fungiprojects with lots of shared bugs, we've recommended waitibng for a big-bang import19:42
fungimonasca has stated that they feel the number of cross-project bugs involving their project are minimal enough to accept that bit of pain19:42
persiaMy concern with that is that it might impact cross-project coordination, but I suppose if individual projects are willing to take on the extra load of watching both places while waiting for the big bang, that choice should be available.19:42
persiaAnd that implementation is easy enough that it shouldn't complicate things too much (other than a little extra work for early migration teams)19:43
fungiand yeah, any additional cross-project pain might help increase momentum/adoption ;)19:43
diablo_rojoHa ha ha a silver lining19:43
*** fguillot has quit IRC19:43
persiaIn that case, I'm happy with SotK's earlier summary, unless rhochmuth is surprised and worried about the extra cross-project effort.19:44
rhochmuthpersia: i made an assumption we didn't have too many cross-project issues19:44
persiarhochmuth: You don't, based on looking at about 40% of your bugs :)19:44
rhochmuthi don't think the monasca team is worried about it then19:45
*** salv-orl_ has quit IRC19:45
*** akuznetsov has joined #openstack-meeting19:45
SotKthanks rhochmuth and the monasca team :)19:47
rhochmuththat you storyboard team19:47
rhochmuthis there anything you need me to do19:47
rhochmuthor any help with19:47
diablo_rojoSotK, ?19:48
*** akuznetsov has quit IRC19:49
diablo_rojoMore internet issues I expect..19:49
* SotK can't think of anything immediately off the top of his head except "feel free to help out with reviews and code and stuff if you like/have the time"19:49
zara_the_lemur__yeah, I'm not aware of anything migration-specific19:50
zara_the_lemur__though we'll let you know if we think of anything19:50
rhochmuthok, sounds good19:50
rhochmuthwill look for revews19:50
fungirhochmuth: once the import script is tested/working, we'll want to schedule a window to import your stories in production and turn off lp bug tracking (and you'll probably want to coordinate some documentation updates and announcements about that for the same time)19:50
rhochmuthgot it19:51
rhochmuththanks fungi19:51
zara_the_lemur__if you have any more questions, feel free to ask as they come up! :)19:51
rhochmuthdo you have a time-frame?19:51
fungithere's one other annoyance we've noticed, which is that disabling bug reporting in lp doesn't make existing bugs immutable, it only prevents opening new bugs... so people may still update old lp bugs from time to time if they didn't "get the memo"19:51
*** hashar has joined #openstack-meeting19:52
rhochmuthok, so we'll have to watch for that19:52
persiaIn other contexts, I've seen teams set all open bugs in LP to invalid with a comment pointing to the new tracker.19:52
rhochmuthbut, it sounds reasonable that we'll be able to track that19:52
rhochmuthpersia: that sounds like a good idea19:52
persiaThis isn't the most friendly transition, but it has been used in the past by teams migrating from LP to other (non-SB) things.19:52
fungipersia: yep, that may be a good tack to take, though could be messy for the handful of shared bugs19:53
diablo_rojoEasy enough to do for all the non shared bugs though I would think19:53
persiafungi: Also popular bugs with many subscribers.  The debate over whether some project should use LP or not can overflow into unrelated issues, and people can become unhappy about bug subscriptions.19:53
fungiyeah, the lp api, even with its warts, is pretty easy to use for something like that19:53
persiadiablo_rojo: Yep.19:54
fungioh, though bugs with many subscribers have a tendency to run into internal lp timeouts when trying to update them19:54
persia#launchpad can often help with those special cases.19:54
fungiso there could be a few that end up not getting updated with the pointer, but that's better than nothing19:54
fungiyeah, also sometimes the smtp api will work for those where the http api and webui don't19:55
SotKcertainly sounds like a good idea to me19:56
SotKcan anyone think of anything else to discuss about this right now?19:56
*** CarolBarrett has joined #openstack-meeting19:57
SotKthen I guess we'll have open discussion for a couple of minutes19:57
SotK#topic Open Discussion19:57
*** openstack changes topic to "Open Discussion (Meeting topic: storyboard)"19:57
*** ekhugen_alt has joined #openstack-meeting19:58
*** VW has quit IRC19:58
diablo_rojoGot the second blog post basically done so we can post that whenever. Decision on what we are changing the domain to?19:58
*** morgan_ is now known as morgan19:58
SotKmy favourite one in the etherpad is unavailable :(19:59
SotKwe can continue this discussion in #storyboard though, since we should probably pick something and are out of time19:59
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"20:00
diablo_rojoFair enough :)20:00
openstackMeeting ended Wed Jan 11 20:00:02 2017 UTC.  Information about MeetBot at . (v 0.1.4)20:00
SotKthanks folks :)20:00
openstackMinutes (text):
ekhugen_alt#startmeeting wos-mentoring20:00
openstackMeeting started Wed Jan 11 20:00:37 2017 UTC and is due to finish in 60 minutes.  The chair is ekhugen_alt. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: wos-mentoring)"20:00
openstackThe meeting name has been set to 'wos_mentoring'20:00
*** VW has joined #openstack-meeting20:01
ekhugen_althi, who's here for the women of openstack mentoring meeting?20:01
CarolBarrettHi Emily20:01
CarolBarrettHappy New Year!20:01
ekhugen_altHi CarolBarrett!20:01
ekhugen_altThanks! Happy New Year to you too!20:01
ekhugen_altI know Megan sent me a note she couldn't be here20:02
diablo_rojoHello :)20:03
ekhugen_altHi Kendall!20:03
ekhugen_altoh CarolBarrett was Nicole from Intel going to come?  She sent me an email about getting an invite20:03
CarolBarrettekhugen_alt: Good question, I'll ping her!20:03
CarolBarrettshe's on her way20:04
spotzI'm here in a normal distractedly way if needed:)20:05
ekhugen_altHi Amy!20:05
* ekhugen_alt wishes everyone a Happy New Year and hopes their holidays were nice20:05
diablo_rojospotz, you and me both :)20:05
*** ayoung has quit IRC20:06
ekhugen_alt#topic matches20:06
spotzHappy New Years all20:06
*** openstack changes topic to "matches (Meeting topic: wos-mentoring)"20:06
ekhugen_altso first topic is matches (I think we can catch Nicole up when she comes)20:06
ekhugen_altright now according to spreadsheet we have 10 mentor/mentee pairs
*** sdake_ is now known as sdake20:07
*** nadya has quit IRC20:07
ekhugen_altwhich is I think half of all people signed up are currently matched (it sounds kind of low when I say 10 pairs for some reason20:08
ekhugen_altwe were going to check in with them after 1 month (it's been slightly more than that)20:08
ekhugen_altany suggestions on what the checkup note should say?20:08
*** Nicole_ has joined #openstack-meeting20:09
* ekhugen_alt waves hi to Nicole_20:10
Nicole_hi there!20:10
CarolBarrettHi Nicole_20:10
diablo_rojoIf they feel like they are a good fit mentor/mentee wise? What is the best bit of advice they have gotten so far? How often do they connect?20:11
CarolBarrettekhugen_alt: Can we adapt what we wrote for the previous checkin email?20:11
diablo_rojoI'd keep it pretty short20:11
spotzekhugen_alt: I know Shilla and I are going to try to start next week. But maybe just mention breaks are over?20:11
ekhugen_altyeah, I guess the question is kind of, should we try to get some information out of this note, or just treat it as a reminder/is the mentoring relationship still breathing note?20:13
*** e0ne has joined #openstack-meeting20:14
spotzI'd go with still breathing. At least with the timing of my match we didn't have a chance to do anything before breaks20:14
diablo_rojoekhugen_alt, ha ha good question. I suppose info gathering isn't really necessary.20:14
diablo_rojoStill breathing sounds good to me.20:15
*** spzala_ has joined #openstack-meeting20:15
ekhugen_altand CarolBarrett I think the only previous checkup note we did was when we sent out the survey, for the first round of matches20:15
CarolBarrettekhugen_alt: It might be good to see if anyone of the Matches are interested in participating in a session in Boston to talk about their experience20:15
Nicole_perhaps see if the mentor/mentee relationships are still breathing, although it'd be nice to build these out into a collage of mini-stories in the long term.20:16
Nicole_emily, carol -- love your idea!20:17
Nicole_about considering some of these as stories/sessions in boston.20:17
ekhugen_altso I think a Happy New Year, we're just checking in on you to see how your mentoring relationship is going/if you have any questions.  Also we're trying to get a panel session together for the Boston summit, reply if you're interested20:17
ekhugen_alttype of note?20:17
Nicole_double yes.20:18
spotzekhugen_alt: Sounds good, only issue might be that call for presentations are out. Might need to get that in before you might get responses20:18
Nicole_i'm writing a session submission for another diversity-related session. i'd be happy to write one for a mentor-related session.20:19
ekhugen_altspotz: are you suggesting delaying asking about this until we're sure the presentation is accepted?20:19
Nicole_have we done something like this before?20:19
spotznope opposite:)20:19
ekhugen_altI think actually Anne mccormick put a note out to the listserv looking for people20:19
spotzekhugen_alt: Apply now because you may not hear back in time20:19
ekhugen_altso she's putting the session together, I believe20:20
Nicole_ah, ok20:20
*** spzala_ has quit IRC20:20
CarolBarrettYup - Anne McCormick is leading this.20:21
Nicole_sounds great20:21
*** spzala has joined #openstack-meeting20:21
ekhugen_altso maybe instead of "reply if you're interested" "reply to Anne <email> if you're interested"?20:21
CarolBarrettIf we do that we should check with her first. If we ask for responses to our email, then we can pass the contacts to Anne. 6 of one; half-dozen of another...20:23
ekhugen_altI can send her an email and ask her preference20:23
*** rlpple has quit IRC20:23
*** jaugustine has quit IRC20:23
ekhugen_altanything else for the follow up emails?  or matches in general?20:24
*** cody-somerville has joined #openstack-meeting20:24
*** cody-somerville has quit IRC20:24
*** cody-somerville has joined #openstack-meeting20:24
*** jkilpatr has quit IRC20:24
*** jaugustine has joined #openstack-meeting20:24
diablo_rojoDOnt think so :)20:24
ekhugen_altokay #topic openstack project20:25
ekhugen_altI don't have much to report here, I put it on the agenda to shame myself into action20:25
ekhugen_altI think last year I left it as I was partway through the project creator's guide and needed something from the infra team20:25
ekhugen_altI think they might've added me to the projects (so I can start adding others) but I need to go back and check that20:26
*** jaugustine_ has joined #openstack-meeting20:26
*** jaugustine has quit IRC20:26
ekhugen_alt<- bad emily20:26
*** csomerville has quit IRC20:26
ekhugen_altany questions or comments on this?20:27
spotznot I20:27
ekhugen_alt#topic Boston planning20:28
*** openstack changes topic to "Boston planning (Meeting topic: wos-mentoring)"20:28
ekhugen_altanyone have any updates on Boston planning for a speed mentoring session?20:28
Nicole_intel is sponsoring the speed mentoring session in boston20:29
ekhugen_altyay! thank you!20:29
*** jkilpatr has joined #openstack-meeting20:29
Nicole_i'm exited about it!20:29
Nicole_i'd like to get team input as we plan for it.20:29
Nicole_what worked/what didn't work.20:30
ekhugen_altNicole_ +120:30
spotzIt's moving to a lunch right?20:30
*** sshnaidm is now known as sshnaidm|bbl20:30
ekhugen_altis it going to be a breakfast session again, or is there the chance to switch to later in the day?20:31
Nicole_am checking on that.20:31
Nicole_would like to move it later in the day, if we can.20:31
CarolBarrettekhugen_alt: Did we capture improvements for the next round in Barcelona?20:31
* ekhugen_alt looks back through chatlogs20:31
CarolBarrettI know they were looking at Lunch, but I haven't seen that confirmed by anyone from the Foundation yet20:31
Nicole_am checking on the time in parallel.20:32
CarolBarrettekhugen_alt: I thought we had an etherpad...? but I could be imagining things20:32
*** bobh has joined #openstack-meeting20:32
spotzI'm gonna end up with Breakfast and Learns:)20:32
*** bobh has quit IRC20:32
ekhugen_altcarolbarrett we did, I don't think we had much in there (no mentors replied in it)
Nicole_from memory, i can remember 2 of the highlights, but am trying to think of areas for improvement.20:34
ekhugen_altoh here, I think we had some suggestions at this wos meeting
spotzI wasn't there, only feedback I really heard was that one of the mentors wasn't prepared but that's kind of vague20:34
Nicole_at this point, i've confirmed that it's still during breakfast.20:34
*** nklenke has quit IRC20:35
*** sdake has quit IRC20:35
ekhugen_altso I think we liked the idea of having separate career and technical mentoring20:36
diablo_rojoekhugen_alt, +120:36
ekhugen_altbut we wanted to have like ushers to seat mentors and mentees20:36
CarolBarrettI think a couple of things we talked about changing for next time are: Having the greeters usher people to seats to get the table distribution we want20:36
ekhugen_altcarolbarrett +120:36
CarolBarrettAlso, having  a sign that indicates which tables are for Technical and which are for Career mentoring20:37
*** sdake has joined #openstack-meeting20:37
CarolBarrettThere's a comment in one of the other etherpads about having 2 mentors per table - might be a good idea, esp if we seat ~8 people at a table...20:37
*** krtaylor has joined #openstack-meeting20:37
ekhugen_altDid people like having 2 mentors per table?  I thought that people actually didn't like that20:38
ekhugen_altbecause one mentor would tend to talk more than the other20:38
CarolBarrettIt seems like we have a challenge getting both our mentors and mentees there on time - if this moves to lunch that might solve the early morning part of this issue, but could introduce others (like people getting from Point A to Point B)20:38
diablo_rojoI think it depended on the table and pair of mentors- some talked more than others.20:38
diablo_rojoThat was my take anyway.20:39
CarolBarrettekhugen_alt: You may be right. I don't have any 1st hand feedback on this20:39
ekhugen_altI'm just going by what's in that etherpad from Nov. 1420:39
*** askb has joined #openstack-meeting20:39
Nicole_in looking at the etherpad from the wos 11/14 meeting, it looks like timing comes up quite a bit.20:39
Nicole_both, timing of the wos/diversity/mentor sessions overall (sequence of sessions), and the specific time of the mentor session.20:40
ekhugen_altyes, it was a real issue at both events that people did not come even remotely on time20:40
ekhugen_altI wish I had a better solution for that20:41
Nicole_the boston prospectus & schedule hasn't been printed yet. we may still have time to influence the timing of sessions overall, and the time of the mentor session specifically.20:41
*** sdake has quit IRC20:41
CarolBarrettI find it hard to imagine they will move both the Speed Mentoring and WOO Networking Session to lunch20:42
ekhugen_altI think we only ended up with 2 15 minute sessions at Barcelona, because of how late we started20:42
diablo_rojoWhat is the normal time block we have to work with?20:42
spotzFrom doing the lunch and learns we still have stragglers, you also have an issue of folks not there for the session just in the room for lunch20:42
Nicole_i think the time block was 50 min.20:42
ekhugen_altdiablo_rojo well the past two times we got like 7:30-8:4520:42
*** nklenke_ has quit IRC20:42
spotzyeah have to be over by 8:45 so people can get to keynotes20:43
*** e0ne has quit IRC20:43
diablo_rojoMaybe we just start rotations sooner and as stragglers come it we can catch them at the door with the lowdown rather than waiting for more people20:43
diablo_rojoIF we wait too long we dont get as many rotations in20:43
ekhugen_altright, but then we also don't have many people to start the first rotation20:44
*** asselin_ has joined #openstack-meeting20:44
ekhugen_altcrazy idea, but what if we threw out the idea of rotations?20:44
spotzSo just 1 mentor per table and folks stay put?20:44
spotzdefinitely helps with the rotation chaos20:45
ekhugen_altright, but then maybe we could have a list of questions to go through and call time on each question20:45
ekhugen_altto help make sure it moves along and doesn't get caught up in one person talking the whole time?  Maybe that makes it not really speed mentoring20:45
*** asselin has quit IRC20:46
Nicole_timing was 7:30-8:35 am in barcelona. but it didn't feel like it was that long, given the issues that folks have already mentioned above.20:46
diablo_rojoRotating mentors instead of mentees helps clear up the chaos20:46
diablo_rojosome of it anyway20:46
Nicole_agree with the idea of 1 mentor per table, based on the earlier feedback20:46
Nicole_i think we need clearer delineation of technical vs career tables20:47
*** adiantum has joined #openstack-meeting20:48
CarolBarrettNicole_: +120:48
ekhugen_altNicole_ +120:48
diablo_rojoNicole_, +120:48
spotzwhat about asking for questions in advance?20:48
diablo_rojoDiscussion questions in advance is a good idea too.20:48
Nicole_maybe there's a way to ask them what their top 3 questions are at the time that they register?20:49
spotzThat way if someone asks something really good it can be asked at all the related tables20:49
ekhugen_altooh, that's a good idea20:49
diablo_rojoNicole_, +120:49
*** sdake has joined #openstack-meeting20:49
Nicole_this will also tell us how many are interested in which track (e.g. technical vs career)20:49
Nicole_we'll also be able to see what interests are, and if they're in the same areas, different areas, etc.20:50
*** bkeller` has joined #openstack-meeting20:50
Nicole_what's the consensus on time of day? breakfast? lunch? evening?20:51
Nicole_and the consensus on sequencing of the networking session & mentor session?20:51
ekhugen_altI like evening, personally20:51
diablo_rojoWhile I hate waking up early, I have the least conflicts before the keynotes.20:52
*** m_kazuhiro has joined #openstack-meeting20:52
CarolBarrettI agree with Evening...esp now that there are fewer evening parties20:52
Nicole_am thinking the sponsors of the mentor & networking sessions can work together with the foundation to see if we can influence the time of day.20:52
spotzevening will get you the most turn out potentially or at least the most sign ups20:52
*** joeljwright has joined #openstack-meeting20:53
ekhugen_altI don't have a strong feeling on the sequencing?20:53
diablo_rojoIf you decide evening  would be better I can talk to the people who will be doing the scheduling at the foundation for the Summit/Forum.20:53
CarolBarrettNo request on sequencing either20:53
ekhugen_altinstead of truly evening, maybe last session of the day could be a compromise? although then we're competing with other sessions potentially20:55
*** xyang1 has joined #openstack-meeting20:55
*** jrichli has joined #openstack-meeting20:56
CarolBarrettThat could work20:56
ekhugen_altokay we only have 4 minutes left, do we have any thing else we want to be sure to discuss today?20:56
Nicole_from the feedback at the 11/14 wos meeting, it looks like there's some input to host a meetup or the networking session prior to the mentor session so that folks have an intro to wos20:56
Nicole_does someone have the action item to work with the foundation on timing? it would be great to close on that before we close this meeting.20:58
ekhugen_altNicole_ by timing do you mean breakfast/lunch/evening?  or the sequencing?20:58
Nicole_breakfast/lunch/evening ... that seems to be the priority20:58
ekhugen_altit sounds like most people like evening, and diablo_rojo offered to talk with the schedulers?20:59
*** milkman__ has joined #openstack-meeting20:59
ekhugen_altwe can continue talking on openstack-women20:59
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"20:59
openstackMeeting ended Wed Jan 11 20:59:50 2017 UTC.  Information about MeetBot at . (v 0.1.4)20:59
openstackMinutes (text):
*** sgundur_ has joined #openstack-meeting20:59
*** pdardeau has joined #openstack-meeting21:00
*** acoles_ is now known as acoles21:00
notmynameswift team meeting time21:00
notmyname#start meeting swift21:00
notmyname#startmeeting swift21:00
openstackMeeting started Wed Jan 11 21:00:15 2017 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at
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
*** kota_ has joined #openstack-meeting21:00
*** tonytan4ever has quit IRC21:00
*** timburke has joined #openstack-meeting21:00
*** ekhugen_alt has left #openstack-meeting21:01
*** tonytan4ever has joined #openstack-meeting21:01
notmynamewelcome everyone21:01
notmynameagenda for this week is at21:01
*** lyarwood_ is now known as lyarwood21:02
notmynameand because of timezones, I'd like to start at the bottom with cschwede21:02
*** CarolBarrett has quit IRC21:02
notmynamecschwede: what's up with part power increase? I'm looking forward to that!21:02
*** raildo has quit IRC21:02
cschwedenotmyname: thx! well, i just wanted to check if there are any questions regarding the patch, if i could help reviewers getting this forward21:02
*** milkman__ is now known as cutforth21:03
notmynamelooks like in the past both mattoliverau and pdardeau have commented on it21:03
notmynamecschwede: but you're currently blocked needing reviews on it, right?21:03
timburkehey, that was another one i wanted to look at from the "Needs Final Approval" category on
pdardeaui'll review again21:04
mattoliverauI'm mostly back in the swing after my vacation, so I'll have another play with it :)21:04
cschwedeyes, and I hopefully adressed all comments from Matt and Paul21:04
notmynamepdardeau: mattoliverau: thanks!21:04
cschwedePete already added his +2 to that patch21:04
cschwedeso ping me if you have time for review and questions on that patch - would be great!21:05
mattoliveraucschwede: well pdardeau and I will find some time :)21:05
*** rossella_ has quit IRC21:05
cschwedemattoliverau, pdardeau: thx a lot!21:05
notmynameok, back up to the top of the list21:05
notmyname and
openstackLaunchpad bug 1651530 in OpenStack Object Storage (swift) "suffix hash invalidation may be lost" [Critical,New]21:06
notmynameacoles: clayg: what's the status here?21:06
*** Nicole_ has quit IRC21:06
notmynameI see clayg had pushed some review comments, but also a bunch of other related patches?21:07
acolesnotmyname: I saw clayg did a great review21:07
*** dimtruck is now known as zz_dimtruck21:07
*** adiantum has quit IRC21:08
acolesnotmyname: yes, I saw those but not had time today to follow up21:08
*** adiantum1 has joined #openstack-meeting21:08
notmynameoh hi!21:08
cschwedeso that's a race condition?21:08
acolesI think maybe he broke it up into several patches21:08
* clayg busts over some boxes for acoles21:08
*** ykatabam has quit IRC21:08
claygacoles: oh yeah... i was feeling really bad about that last night21:08
notmynameclayg: so that's the relation of and the patches you pushed up?21:08
claygdoes anyone know Pavel?  Can I tell him ... idk something ... that i'm not a jerk on purpose?21:09
acolesI already told him :P21:09
claygso... three days in I *think* - I *think* I understand patch
acolesclayg: you were faster than me21:09
claygI spit it up into smaller patches that I do understant21:09
*** fzdarsky has quit IRC21:09
*** rbak has quit IRC21:10
claygso... what to do?  acoles has a +2 on patch 40204321:10
notmynameah ok21:10
*** adiantum1 is now known as adiantum21:10
claygI'm like... I can *almost* think - i'm scared... but I keep with it and believe in myself21:10
claygI might be able to +A it without ruining everyone's clusters21:10
acolesapart from now needing to re-review them, I see the merit in splitting up, there were definitely several issues being addressed, and as someone pointed out the commit message "optimize.." hides fact that there is a bug fix21:10
notmynameclayg: you cplit it into 4 patches right?
claygor rather I'm not sure if doing that should constitute negligence - since we *obviousl* should not fix three unrelated things in a critcal bug fix21:11
*** jprovazn has quit IRC21:11
cschwedeso Pavel is not around? onovy maybe?21:11
acolesI feel bad that I did not push back more on the multiple-fixes-in-a-patch, I guess that's the beauty of fresh eyes21:12
cschwedeonovy: hello :) so clayg and acoles are just discussing Pavel's patch ^^21:12
* onovy is fine with spliting21:12
claygacoles: you see Closes-Bug and it says CRITICAL it's really hard to say "no"21:13
cschwedesplitting sounds good to me too21:13
acolesclayg: are your patches in a chain, if I pull one will I see the same end result?21:13
*** mmalik4 has quit IRC21:13
onovyand pavel is on vacation (family reason, new baby)21:13
clayghonestly tho - i'm more pissed about the double rehash optimization than the teeny little race on new parts21:13
claygi mean... both should be fixed obviously :P21:13
claygbut I have this deep burning hate for with REPLICATE requests21:14
claygdid we netsplit?21:14
onovyno, i'm here21:14
claygacoles: no my patches are *not* in a chain21:14
notmynameno, just quiet :-)21:14
acolesclayg: k21:14
claygthe changes were all orthogonal and I didn't want review of one to hold up any other21:15
claygif you're super into eliminating the write iop on noop replicate reqeusts - go review that one21:15
claygif you don't like the race with invalidate of a part while doing the initial rehash to create the hashes.pkl - go review that one21:15
onovyshould Pavel review that three patches too, right?21:15
claygif you think doing rehash of every suffix twice every replicate call is a bad idea - go review that one21:16
claygonovy: that would be super helpful21:16
notmynameseems that on one hand we've got a complex patch that closes an important issue and does a few other nice things too, and already has one +2. on the other, we've got a few unlrelated patches that each do only one thing, but they're all unreviewed21:16
mattoliverauclayg: I've been playing with that patch. So I'll continue to review it (noop one)21:16
onovyclayg: i will ask him tomorrow21:16
acolesonovy: let him enjoy his new baby! I'll take a look over them, but he may want to before they merge21:16
claygnotmyname: that's a great description of the situation!21:17
claygnotmyname: but please understand - i wasn't trying to make extra work - or even get on a high horse about splitting them up21:17
onovyacoles: he is working from home. sometimes :)21:17
claygnotmyname: if you look at my review I'm all like "why the ^%&* is this gross code here?" and it's not till you understand all the things going on that you can sort to understand the motivations and reasons for all the changes21:18
claygand I think...21:18
notmynameok, so the risk of sticking with the first is that we might land broken code. the benefit is that it might land sooner. the risk of the second method is one or more just languish for a long time, and the important one(s) will take longer anyway for rereviews21:18
claygwell acctually I still don't unerstand the fix for the new part race21:18
claygI ended up with a totally different solution to make the tests pass21:18
notmynameclayg: what do you want to do? stick with the new patches or just use your work there to understand the first one?21:19
claygnotmyname: "might land sooner" - if Pavel is not intested in collaborating on the split up changes to fix these issues independently I think I would prefer not to side step his amazing efforts in the combined patch21:20
notmynameacoles: what do you want to do? rereview or land the one you've already +2;;d21:20
*** diablo_rojo_phon has quit IRC21:20
*** rbak has joined #openstack-meeting21:20
claygnotmyname: that would leave me trying to +A the existing combined patch - which so far I don't have a sufficient behavioral deficiency to -121:21
clayg... but I don't understand it yet either21:21
acolesnotmyname: I think my +2 came with caveat that I had some hand in the patch, so ideally we'd have two more +2's on something critical21:21
clayg... trying21:21
claygacoles: can you maybe explain to me after the meeting how it managed to fix invalidate_hashes dropping suffix invalidation on the floor when the hashes.pkl doesn't exist without changing invalidate_hashes?21:22
onovyjust my two cents: if we can wait a bit, Pavel can take a look into 3 splitted/clayg's patches21:22
acolesclayg: are your patches a decomposition of the original or wildly different?21:22
claygI think that's he only piece I really still don't understand21:22
notmynameok. I'm not leaning too strongly one way or the other, but if we need a decision made, I'd vote for the splits21:22
claygthe rest is style nits that I think I can fix in a follow up21:22
onovyclayg: Pavel should explain it to you :)21:22
claygacoles: the tests transfer - the solutions are ment to be "more obviously correct"21:22
claygno wildly different21:22
kota_notmyname: +121:23
acolesclayg: I can try explain but I'll need to reload it first.21:23
notmynameonovy: aside from the cosmic injustice of knowing there's a bug and having a patch unmerged that seems to fix it, no, there is no particular rush21:23
claygexcept for the race - i still don't understand pavel's fix for the race - I think my fix is obviously correct and I stole your tests21:23
kota_I'm moving to review the original combined to the splitted 4.21:23
clayg*obviously correct* modulo whatever could be claned up pending review (e.g. the weird mkdirs call under directory lock?  wtf?  cc kota)21:23
onovynotmyname: yep. critical bug (data loss) was already fixed. this should be well tested21:24
onovydon't added another regression here (again :)21:24
notmynamekota_: I don't follow what you mean by "review the original combined to the split 4"21:24
claygonovy: if Pavel could do that it would be *very* helpful!  what's his handle?  does he lurk?21:24
mattoliveraunotmyname: I think kota_ means he's faviouring the combined.21:25
mattoliverauI'm not sure myself.21:25
*** salv-orlando has joined #openstack-meeting21:25
kota_notmyname: ah, i like the second method to review clayg's patches, i mean and I has started to review them.21:25
mattoliveraupersonaly I like them split up, only because they're more targeted and easier for my head to get around (eventually). But that might just be my brain being slow.21:25
claygacoles: well could you read the commit message and glance at the diff in
onovyclayg: you mean just now? it's 10pm here, so i think he is sleeping :)21:25
*** jmckind has joined #openstack-meeting21:25
notmynameok, let's do that. it's decided. we'll get Pavel's view on the split patches, acoles will (may?) rereview, clayg will continue to own the split patches, kota_ et al will review21:26
onovynotmyname: +121:26
notmynameeveryone agree?21:26
claygacoles: you filed the bug - so you should at least be able to reload the failure quickly - and I think my diff is small/obvious enough that you might either agree "yeah that's the fix" or "oh, now I remember what the other change did!"21:26
onovyi will send note to Pavel21:26
notmynameonovy: thanks. but remind him that babies come before code ;-)21:26
claygonovy: if at any point Pavel wants to restore his authorship of the four spit patches - I really only consider that I have split his work on his behalf21:27
claygi am but a humble servent and beg forgiveness for my hubris21:27
notmynameclayg: you can `git commit --ammend --author="foo bar <foo@bar>"` to change the commit21:27
*** zz_dimtruck is now known as dimtruck21:27
claygoh goodness the poor bloke is replicating!?21:27
notmynameok, moving on!21:28
notmynamekota_: any progress on global ec this week?21:28
onovyclayg: Co-Author: Pavel Kvasnička <> // so i'm fine with authorship21:28
kota_notmyname: unfortunately nothing except i rebased it onto the newest master21:28
onovyclayg: but yep. if it's just split, you can --amend author and push it yourself :)21:29
kota_notmyname: i really want volunteer for reviews.21:29
onovymove on, sry21:29
notmynamespecifically for
kota_yes, that one.21:29
notmynameEC fragment duplication. can anyone volunteer to review this patch, please?21:30
claygI obviously should step up - i have it loaded in my brain form... Austin?21:30
claygno... San Antonio21:30
notmynametimburke: will you have a chance?21:30
claygI remember looking at it in the hotel lobby21:30
timburkei was just thinking about that. sure21:30
notmynametimburke: awesome, thanks21:30
kota_clayg: yeah, that review was helpful to progress, thx.21:31
claygI have bandwidth this week (and into early next) for reviews - i'd like to spend it there for sure.21:31
notmynameclayg: cool, thanks21:31
notmynamejrichli: symlink progress from this week. what's up?21:31
jrichlithanks for all the great feedback on the api patch.21:32
jrichlii am squashing it into the implementation patch now.21:32
notmynameah, cool21:32
notmynameand you've mapped that into a trello board right?
notmynameeither you or tdasilva did21:32
jrichliyes, tdasilva created cards for outstanding issues21:33
claygwtg tdasilva!21:33
notmynamethankd tdasilva21:33
tdasilvajust copy and paste from clayg's awesome comments ;)21:33
*** lpetrut has joined #openstack-meeting21:33
notmynameif anyone wants access to that board, please ping me on irc with your trello username and i'll add you21:34
notmynameaccess == write access. IIRC it's public read21:34
notmynamejrichli: acoles: how was the keymaster v2 call last week? anything to report from that?21:34
kota_notmyname: thanks for adding me ;-)21:35
kota_notmyname: and i think m_kazuhiro may want to join?21:35
kota_m_kazuhiro: ?21:35
claygtdasilva: I told you that was a roast right?  I just trying to keep notes from torgomatic timburke and notmyname !21:35
m_kazuhirokota_: yes. I want to join.21:35
acolesnotmyname: call was good, thanks tdasilva for hosting21:36
jrichlinotmyname: it went well.  acoles created an etherpad and recorded the results.21:36
notmynameany summary?21:36
acolesand for the keen there is a link at bottom for call replay courtesy of tdasilva21:37
notmynameor what's next?21:37
acolessummary each keymaster impl loads key from one source. keep it simple.21:37
jrichliis mathiasb here?21:37
mathiasbnotmyname: I tried to address the comments from the call and on gerrit, new version is available for review21:38
*** rtheis has quit IRC21:38
*** lpetrut has quit IRC21:38
notmynamemathiasb: what's the link to the patch?21:38
notmynamemathiasb: great, thanks. so the current status is needing reviews? or are you expecting more dev work first?21:39
mathiasbit is ready for reviews21:39
notmynameok, great21:39
notmynamebkeller`: any progress on notifications this week?21:39
notmynameany updates from last week?21:39
bkeller`not really21:40
notmynametdasilva: what's the status of pyeclib/libec merge? any progress for merging and keeing history?21:40
*** abalutoiu has quit IRC21:41
*** zara_the_lemur__ has left #openstack-meeting21:41
notmynametdasilva: ? (you're talking in -swift) ;-)21:42
tdasilvanotmyname: no progress on that this week21:42
notmynameok :-)21:42
claygnotmyname: IIRC onovy told us to keep them seperate and pyeclib should support old versions of liberasurecode and I sorta had a conniption21:42
notmynametdasilva: anything we can do to help?21:42
tdasilvanotmyname: i just need to ping infra again21:42
notmynameclayg: yes, I remember that :-)21:42
claygonovy: sorry about that :\21:42
onovyi don't have problem with merging, if there will be correctly working build scripts for both21:43
onovyand i can than build two package, so same as now21:43
tdasilvaonovy: i created this repo:
onovyi will "lock" version between this two packages, so same version will be installed21:44
notmynameonovy: that makes sense. one code repo, two deliverables21:44
onovytdasilva: i will take a look21:44
tdasilvabased on the talks i had with infra folks, that's how i understood it should look like at the end21:44
onovytdasilva: why not just put two dirs inside one repo and have that projects "directory separated"?21:45
tdasilvaonovy: it has to do with the gate jobs and where they look for certain files21:45
onovyah, right21:45
tdasilvamy initial plan was sort of what you described21:45
onovythat's strange21:46
onovyyou can use one build system for one language only21:46
notmynamejoeljwright: how's the pre/post -amble patch going?21:47
joeljwrightI'm still working on the comments from timburke/jrichlie21:47
notmynamejoeljwright: ok21:47
joeljwrightI have one qn for general consumption21:47
joeljwrightwould anyone mind reducing min seg size to 0 bytes?21:47
onovytdasilva: if i understand correctly: make will build liberasurecode only, and python python-pyeclib only, right?21:48
*** sshnaidm|bbl is now known as sshnaidm21:48
claygtdasilva: but that's just merging the repo's right?  it's not really making the changes in pyeclib that turn it into a true python-liberasurecode - the c code still does a dynmic reference to whatever .so you have in the LDPATH or whatever?  you can publish a python-liberasurecode wheel to pypi and have it installed with pip?21:48
tdasilvaonovy: right21:48
notmynamejoeljwright: yeah, timburke asked me about that21:48
onovytdasilva: that's really confusing to have it in one directory :/21:49
*** cleong has quit IRC21:49
notmynameI think that if we actually write down the zero-byte chunk and jsut optimize out the read, I'm ok with that (IIRC our discussion)21:49
onovyjust because "gates want it this way"21:49
joeljwrightnotmyname, excellent21:49
joeljwrightthat's what I've been working on21:49
jrichlijoeljwright: I would expect torgomatic might an opinion.  it'd be good to get his 2 cents21:49
tdasilvaclayg: right, have not attempted to change any behavior yet, thought it could be done on a follow-up change?21:49
onovyclayg: i still need dynamic reference :]21:49
timburkenotmyname: joeljwright: that still gets a little weird as you can't necessarily COPY an slo you can GET21:49
claygonovy: lol - "why do it wrong just cause gates want it that way" - you are one of us21:50
notmynamejoeljwright: I'm also pretty sure that others are likely to have a different opinion. ;-)21:50
joeljwrightwell, I can only propose it21:50
onovyclayg: :] maybe we can create some kind of workaround?21:50
onovyput it into subdirectory, but add makefile + into root21:50
joeljwrightI'm aiming to have something for comments by Friday21:50
notmynamejoeljwright: great21:50
onovymake just width 'cd ... ; make'21:50
onovyand something similar for setup.py21:50
claygonovy: why do you want it dynamic?  I thougth you *just* said you have to lock the packages together?21:51
onovyclayg: yep. because i will lock packages together i don't want to have same ELF inside two packages21:51
*** tonytan4ever has quit IRC21:51
onovystatical linked inside python_c and inside liberasurecode for "C users"21:51
*** chrisplo_ has left #openstack-meeting21:52
claygwhich is my whole beef - I *want* all of the ec code tightly coupled - I can only barely stand swift "supporting" multiple versions of pyeclib because we build libec from source and bump pyeclib in our requirements like we own the whole damn thing21:52
notmynameI want to mention one last thing before we're completely out of time. the TC approved this week. it's a process for getting not-python into openstack code repos21:52
claygdrives me nuts that pyeclib and liberasure code don't even *try* to say they're tightly coupled21:52
timburkeoh! joeljwright! you might have some insight into how best to record the fact that an object is a symlink in the container db :-) i was suggesting stuff it in the etag (or at least, the etag that gets sent to the container server)21:52
onovyclayg: right. package lock will tightly couple it21:52
onovy*package version lock21:53
claygonovy: what is the benifit of the project "supporting" loose coupling - and then requiring packagers to implement tight coupling?21:53
joeljwrighttimburke: I'd need to think about that one!21:53
mattoliverautimburke: shouldn't you prepend an 'l' to it or something :P21:53
onovyclayg: benefit is simple. we don't want to have same binary inside two packages21:53
notmyname(all agenda items have been brought up, but I don't want to cut off the packaging discussion before our time is up)21:53
onovydeduplication :]21:53
onovynotmyname: clayg: let's continue in -swift?21:54
*** krtaylor has quit IRC21:54
timburkejoeljwright: for some reason i had it in my head that you'd done similar things...21:54
*** thorst has quit IRC21:54
*** ykatabam has joined #openstack-meeting21:55
joeljwrightI have abused the content type in middlewares, but nothing I'd suggest in public :)21:55
notmynamejoeljwright: to echo timburke, yeah you're name came up when we were talking about how to (if to) expose symlinks in listings. we'd love your input21:55
notmynameok, I think that's it21:56
notmynamethanks, everyone, for coming and participating. thank you for working on swift21:56
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"21:56
openstackMeeting ended Wed Jan 11 21:56:23 2017 UTC.  Information about MeetBot at . (v 0.1.4)21:56
openstackMinutes (text):
*** sgundur_ has left #openstack-meeting21:56
*** pdardeau has left #openstack-meeting21:56
*** timburke has left #openstack-meeting21:56
*** thorst has joined #openstack-meeting21:57
*** ijw has joined #openstack-meeting21:57
*** VW has quit IRC21:59
*** m_kazuhiro has left #openstack-meeting21:59
*** ansmith_ has quit IRC21:59
*** jrichli has left #openstack-meeting22:01
*** thorst has quit IRC22:02
*** fzdarsky has joined #openstack-meeting22:02
*** cutforth has quit IRC22:03
*** sdake has quit IRC22:03
*** sdake has joined #openstack-meeting22:04
*** kota_ has left #openstack-meeting22:07
*** fzdarsky has quit IRC22:08
*** spzala has quit IRC22:09
*** VW has joined #openstack-meeting22:11
*** lblanchard has quit IRC22:13
*** adiantum has quit IRC22:13
*** ayoung has joined #openstack-meeting22:13
*** spzala has joined #openstack-meeting22:16
*** sdake has quit IRC22:16
*** jaypipes has quit IRC22:16
*** spzala has quit IRC22:20
*** fzdarsky has joined #openstack-meeting22:21
*** salv-orl_ has joined #openstack-meeting22:22
*** sshnaidm is now known as sshnaidm|away22:23
*** s3wong has joined #openstack-meeting22:24
*** salv-orlando has quit IRC22:26
*** reed_ has joined #openstack-meeting22:26
*** reed_ has quit IRC22:26
*** tiantian has quit IRC22:28
*** tiantian has joined #openstack-meeting22:28
*** spzala has joined #openstack-meeting22:28
*** spzala has quit IRC22:28
*** markvoelker has quit IRC22:29
*** baoli has quit IRC22:30
*** bkeller` has quit IRC22:32
*** markvoelker has joined #openstack-meeting22:32
*** annegentle has quit IRC22:33
*** edtubill has quit IRC22:34
*** markvoelker has quit IRC22:34
*** markvoelker has joined #openstack-meeting22:34
*** markvoelker_ has joined #openstack-meeting22:39
*** markvoelker has quit IRC22:39
*** VW has quit IRC22:39
*** kberger has joined #openstack-meeting22:41
*** VW has joined #openstack-meeting22:44
*** designbybeck has quit IRC22:45
*** jmckind has quit IRC22:46
*** jkilpatr has quit IRC22:47
*** hashar has quit IRC22:49
*** julim has quit IRC22:49
*** acoles is now known as acoles_22:49
*** ayoung has quit IRC22:51
*** jmckind has joined #openstack-meeting22:53
*** georgk has joined #openstack-meeting22:55
*** Swami has quit IRC22:56
*** cdub has quit IRC22:57
*** VW has quit IRC22:58
*** tommylikehu_ has joined #openstack-meeting22:58
*** joeljwright has quit IRC22:59
*** Leo_ has quit IRC22:59
*** spzala has joined #openstack-meeting23:01
*** krtaylor has joined #openstack-meeting23:02
*** bobmel_ has quit IRC23:02
*** jmckind has quit IRC23:03
*** ChanServ changes topic to "OpenStack Meetings ||"23:04
*** tommylikehu_ has quit IRC23:07
*** fzdarsky is now known as fzdarsky|afk23:07
*** fnaval has quit IRC23:09
*** efried has quit IRC23:09
*** spzala has quit IRC23:09
*** spzala has joined #openstack-meeting23:09
*** lamt has quit IRC23:11
*** fzdarsky|afk has quit IRC23:12
*** VW has joined #openstack-meeting23:16
*** claudiub|2 has quit IRC23:16
*** spzala has quit IRC23:18
*** cdub has joined #openstack-meeting23:18
*** VW has quit IRC23:20
*** sdake has joined #openstack-meeting23:21
*** JRobinson__ has joined #openstack-meeting23:22
*** JRobinson__ has quit IRC23:23
*** JRobinson__ has joined #openstack-meeting23:26
*** JRobinson__ is now known as jrobinson23:27
*** jrobinson has quit IRC23:29
*** galstrom is now known as galstrom_zzz23:30
*** jaypipes has joined #openstack-meeting23:30
*** sdake_ has joined #openstack-meeting23:30
*** sdake has quit IRC23:31
*** markvoelker_ has quit IRC23:32
*** JoseMello has quit IRC23:35
*** VW has joined #openstack-meeting23:35
*** adiantum has joined #openstack-meeting23:36
*** edtubill has joined #openstack-meeting23:36
*** cdub has quit IRC23:37
*** jrobinson has joined #openstack-meeting23:37
*** sdake has joined #openstack-meeting23:37
*** pradk has quit IRC23:38
*** sdake_ has quit IRC23:38
*** rbudden has quit IRC23:40
*** VW has quit IRC23:40
*** markvoelker has joined #openstack-meeting23:40
*** edtubill has quit IRC23:40
*** dimtruck is now known as zz_dimtruck23:47
*** thorst_ has joined #openstack-meeting23:48
*** salv-orl_ has quit IRC23:52
*** thorst_ has quit IRC23:53
*** rhochmuth has quit IRC23:54
*** sdake_ has joined #openstack-meeting23:54
*** xyang1 has quit IRC23:55
*** ramineni_ has joined #openstack-meeting23:55
*** sdake has quit IRC23:56
*** masahito has joined #openstack-meeting23:58
*** pvaneck has quit IRC23:58
*** pvaneck has joined #openstack-meeting23:58
*** rbak has quit IRC23:59
ekcstime for congress meeting. ramineni_ masahito aimeeu23:59
ekcs#startmeeting congressteammeeting23:59
openstackMeeting started Wed Jan 11 23:59:55 2017 UTC and is due to finish in 60 minutes.  The chair is ekcs. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.23:59
*** openstack changes topic to " (Meeting topic: congressteammeeting)"23:59
openstackThe meeting name has been set to 'congressteammeeting'23:59

Generated by 2.14.0 by Marius Gedminas - find it at!