Tuesday, 2017-02-14

*** ykatabam1 has joined #openstack-meeting00:00
*** ykatabam has quit IRC00:00
*** jamesdenton has joined #openstack-meeting00:02
*** lamt has quit IRC00:03
*** jamesdenton has quit IRC00:06
*** jamesdenton has joined #openstack-meeting00:08
*** Swami has quit IRC00:08
*** Swami has joined #openstack-meeting00:08
*** Swami_ has joined #openstack-meeting00:08
*** sdague has quit IRC00:09
*** yangyapeng has quit IRC00:10
*** sdake_ has joined #openstack-meeting00:11
*** aeng has joined #openstack-meeting00:12
*** sdake has quit IRC00:12
*** jamesdenton has quit IRC00:12
*** spzala has joined #openstack-meeting00:13
*** ihrachys has joined #openstack-meeting00:14
*** markvoelker has quit IRC00:16
*** hongbin has quit IRC00:17
*** markvoelker has joined #openstack-meeting00:17
*** ihrachys has quit IRC00:19
*** yuvalb has quit IRC00:22
*** yuvalb has joined #openstack-meeting00:22
*** dmorita has joined #openstack-meeting00:26
*** thorst_ has quit IRC00:30
*** thorst_ has joined #openstack-meeting00:30
*** baoli has quit IRC00:30
*** emagana has quit IRC00:30
*** thorst_ has quit IRC00:31
*** Julien-zte has joined #openstack-meeting00:31
*** VW has quit IRC00:32
*** diablo_rojo has quit IRC00:36
*** Swami__ has joined #openstack-meeting00:40
*** Swami has quit IRC00:40
*** Swami has joined #openstack-meeting00:41
*** ihrachys has joined #openstack-meeting00:41
*** dmorita has quit IRC00:42
*** Swami_ has quit IRC00:43
*** VW has joined #openstack-meeting00:44
*** VW has quit IRC00:46
*** dmorita has joined #openstack-meeting00:47
*** ihrachys has quit IRC00:48
*** ricolin has joined #openstack-meeting00:48
*** kylek3h has joined #openstack-meeting00:48
*** iceyao has joined #openstack-meeting00:49
*** Leom has quit IRC00:49
*** liangy has quit IRC00:51
*** jamesdenton has joined #openstack-meeting00:51
*** dmorita has quit IRC00:54
*** ykatabam has joined #openstack-meeting01:00
*** gcb has quit IRC01:03
*** ykatabam1 has quit IRC01:03
*** jamesdenton has quit IRC01:03
*** Julien-zte has quit IRC01:06
*** askb has quit IRC01:12
*** Julien-zte has joined #openstack-meeting01:12
*** claudiub|2 has quit IRC01:13
*** thorst_ has joined #openstack-meeting01:17
*** thorst_ has quit IRC01:17
*** askb has joined #openstack-meeting01:18
*** guoshan has joined #openstack-meeting01:18
*** yangyapeng has joined #openstack-meeting01:19
*** Apoorva has quit IRC01:19
*** Apoorva has joined #openstack-meeting01:20
*** huanxuan has joined #openstack-meeting01:23
*** kylek3h has quit IRC01:23
*** guoshan has quit IRC01:23
*** guoshan has joined #openstack-meeting01:23
*** diga has joined #openstack-meeting01:24
*** kevinz has joined #openstack-meeting01:29
*** pvaneck_ has quit IRC01:35
*** unicell has quit IRC01:38
*** toscalix has joined #openstack-meeting01:42
*** gongysh has joined #openstack-meeting01:49
*** guoshan has quit IRC01:52
*** guoshan has joined #openstack-meeting01:53
*** dtrainor has joined #openstack-meeting01:53
*** jrist has quit IRC01:58
*** cdelatte has quit IRC01:59
*** Apoorva has quit IRC02:00
*** thorst_ has joined #openstack-meeting02:02
*** dongfeng2 has joined #openstack-meeting02:06
*** lhx__ has joined #openstack-meeting02:07
*** dongfeng3 has joined #openstack-meeting02:08
*** sdake_ is now known as sdake02:09
*** shu-mutou-AWAY is now known as shu-mutou02:10
*** jrist has joined #openstack-meeting02:11
*** dongfeng2 has quit IRC02:12
*** dmorita has joined #openstack-meeting02:14
*** eharney has joined #openstack-meeting02:16
*** sdake has quit IRC02:17
*** sdake has joined #openstack-meeting02:19
*** gcb has joined #openstack-meeting02:20
*** dmorita has quit IRC02:21
*** esberglu has joined #openstack-meeting02:21
*** dongfeng3 has quit IRC02:22
*** tfukushima has joined #openstack-meeting02:23
*** tfukushima has quit IRC02:23
*** esberglu has quit IRC02:26
*** thorst_ has quit IRC02:29
*** japestinho has joined #openstack-meeting02:30
*** dmacpher has joined #openstack-meeting02:34
*** julim has quit IRC02:41
*** VW has joined #openstack-meeting02:43
*** dbecker has joined #openstack-meeting02:44
*** epico has joined #openstack-meeting02:46
*** VW has quit IRC02:48
*** sudipto has joined #openstack-meeting02:48
*** sudipto_ has joined #openstack-meeting02:48
*** Julien-z_ has joined #openstack-meeting02:48
*** dbecker has quit IRC02:49
*** lakerzhou has joined #openstack-meeting02:49
*** Julien-zte has quit IRC02:50
*** dtrainor has quit IRC02:51
*** Namrata has joined #openstack-meeting02:52
*** cloud_player has joined #openstack-meeting02:54
*** hongbin has joined #openstack-meeting02:56
*** shubhams has joined #openstack-meeting02:59
*** takahara has joined #openstack-meeting03:00
hongbin#startmeeting zun03:00
openstackMeeting started Tue Feb 14 03:00:07 2017 UTC and is due to finish in 60 minutes.  The chair is hongbin. Information about MeetBot at http://wiki.debian.org/MeetBot.03:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.03:00
*** openstack changes topic to " (Meeting topic: zun)"03:00
openstackThe meeting name has been set to 'zun'03:00
hongbin#link https://wiki.openstack.org/wiki/Zun#Agenda_for_2017-02-14_0300_UTC Today's agenda03:00
*** pksingh has joined #openstack-meeting03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
pksinghhello03:00
shubhamsShubham03:00
sudiptoo/03:00
lakerzhoulakerzhou03:00
NamrataNamrata03:00
mkraiMadhuri Kumari03:00
kevinzkevinz03:00
hongbinthanks for joining the meeting pksingh shubhams sudipto lakerzhou Namrata mkrai kevinz03:00
hongbin#topic Announcements03:01
*** openstack changes topic to "Announcements (Meeting topic: zun)"03:01
hongbin1. Select a mascot representing Zun03:01
hongbin#link https://www.openstack.org/project-mascots/03:01
*** s3wong has quit IRC03:01
hongbini was received an email from openstack foundation to ask the zun team to select a logo03:01
hongbinbasically, we select a animal or an item, someone will make a logo for zun team03:02
mkraiWhat is the meaning of zun ?03:02
mkraiI forgot03:02
hongbinzun is a container03:02
*** eliqiao has joined #openstack-meeting03:02
mkraiThat is a chinese word, right?03:02
sudiptoI guess that means a container?03:02
hongbinit seems to be an old chinese world03:03
hongbinyes03:03
hongbin#link https://en.wikipedia.org/wiki/Zun03:03
mkraihongbin By when we have to reply?03:03
eliqiaohi03:03
*** Julien-z_ has quit IRC03:03
hongbinmkrai: i guess one week or two03:03
hongbinhi eliqiao03:03
hongbinok, any idea?03:04
hongbinor want to discuss it offline?03:04
shubhamshongbin: any specific theme for this that we have to follow?03:04
mkraiNeed to think03:04
* eliqiao lurk03:04
hongbinshubhams: i don't think there is any specific theme03:04
hongbinok, let me send an email for that03:04
*** Wenzhi has joined #openstack-meeting03:05
hongbin#action hongbin send a ML to discuss the team mascot03:05
hongbinok, next one03:05
hongbin#topic Review Action Items03:05
*** openstack changes topic to "Review Action Items (Meeting topic: zun)"03:05
*** ihrachys has joined #openstack-meeting03:05
hongbin1. eliqiao_ create a bug for polling issue (DONE)03:05
hongbin#link https://bugs.launchpad.net/zun/+bug/166241503:05
openstackLaunchpad bug 1662415 in Zun "Improve sandbox creation polling" [Medium,Triaged]03:05
hongbinthanks eliqiao for creating the bug03:05
Qimingmaybe a barrel, :)03:06
Qiminghttps://en.wikipedia.org/wiki/Barrel03:06
*** Wenzhi has quit IRC03:06
hongbini guess anyone can assign it to himself/herself if he/she want03:06
hongbinQiming: hey03:06
Qimingo/03:06
hongbininteresting03:06
kevinzCool03:06
hongbin#topic Cinder integration (diga)03:06
*** openstack changes topic to "Cinder integration (diga) (Meeting topic: zun)"03:06
hongbin#link https://blueprints.launchpad.net/zun/+spec/cinder-zun-integration The BP03:06
hongbin#link https://review.openstack.org/#/c/417747/ The design spec03:06
hongbindiga told me he won't be able to come today03:07
hongbinhe said he was working on this bp03:07
hongbinhe will submit the patches by thursday03:07
hongbinthat is all03:07
hongbinany comment ?03:07
*** sshnaidm|off has quit IRC03:07
hongbinok, next one03:08
hongbin#topic Kuryr integration (hongbin)03:08
*** openstack changes topic to "Kuryr integration (hongbin) (Meeting topic: zun)"03:08
hongbin#link https://blueprints.launchpad.net/zun/+spec/kuryr-integration The BP03:08
hongbinthe spec is up for review for about one week or two03:08
*** sshnaidm|off has joined #openstack-meeting03:08
hongbin#link https://review.openstack.org/#/c/425883/03:09
sudiptohongbin, i reviewed it yesterday. Had a few concerns...03:09
hongbinseveral people have provided feedback, and hte spec was revisioned a few times03:09
hongbinsudipto: ack, will address your comments later03:09
sudiptohongbin, sure.03:09
hongbini would ask everyone to review the spec again if you have a chance03:10
pksinghwill review it today03:10
hongbinit seems it is close to merge soon03:10
mkraiI will review03:10
hongbinthanks03:10
hongbinok, next one03:10
hongbin#topic Support interactive mode (kevinz)03:10
*** openstack changes topic to "Support interactive mode (kevinz) (Meeting topic: zun)"03:10
hongbin#link https://blueprints.launchpad.net/zun/+spec/support-interactive-mode The BP03:10
hongbin#link https://review.openstack.org/#/c/396841/ The design spec03:11
hongbinkevinz: ^^03:11
kevinzHi hongbin, https://review.openstack.org/#/c/417681/  this patch has been merged03:11
kevinzI will add some test cases here and investigate the security problem03:12
hongbinkevinz: ack03:12
hongbinkevinz: i tried the attach command, it works very well03:13
*** spzala has quit IRC03:13
hongbinkevinz: i think the next step is to implement a run command that does attach automatically, like docker run -it03:13
kevinzhongbin: Yeah Thanks , I will do it03:14
hongbinkevinz: also, it seems the container will die after a attach and deattach03:14
*** toscalix has quit IRC03:14
hongbinkevinz: it seems there is a way to keep the container alive after a de-attach03:14
hongbinkevinz: those are good to support03:15
kevinzOK I will find out the reason.03:15
*** yamahata has quit IRC03:15
hongbinkevinz: yes, those are minor tweaks to follow up03:15
hongbinkevinz: however, the work is amazing03:15
hongbinkevinz: thanks for the great work, i knew it is not easy03:16
*** iyamahat has quit IRC03:16
hongbinkevinz: but you make it !03:16
kevinzhongbin: My pleasure03:16
*** esberglu has joined #openstack-meeting03:16
hongbinthat is all from me03:16
kevinzThanks for your comments on that patch03:16
hongbinall, any comment for kevinz ?03:16
hongbinnp03:17
pksinghreally great work !!03:17
*** dmorita has joined #openstack-meeting03:17
hongbinkevinz: i guess you can close the bp ?03:17
kevinzThanks for pksingh, your valuable advice for this bp03:17
*** yangyapeng has quit IRC03:18
pksinghnp03:18
kevinzhongbin:OK I will close it after add zun run03:18
hongbinkevinz: ack03:18
hongbinok, advance topic03:18
hongbin#topic Introduce host capabilities and cpusets03:19
*** openstack changes topic to "Introduce host capabilities and cpusets (Meeting topic: zun)"03:19
hongbin#link https://review.openstack.org/#/c/427007/ The spec03:19
hongbinsudipto: lakerzhou ^^03:19
lakerzhouI had minor comments about the NUMA support03:19
*** ihrachys_ has joined #openstack-meeting03:19
sudiptoI seemed to have replied to them.03:20
*** yangyapeng has joined #openstack-meeting03:20
*** esberglu has quit IRC03:20
lakerzhouI think it should be addressed in another feature. The current design cover one use case. It can be extended later it is necessary.03:21
*** gouthamr has quit IRC03:21
sudiptoDo you any more concerns for now lakerzhou or can we take the comments during the code reviews?03:21
lakerzhouno I don't have concerns.03:21
hongbinyes, i agree that the current design is well covered for one use case03:21
sudiptoYou're more than welcome to review the patches :)03:22
hongbinwe can always improve it later03:22
eliqiaohongbin: about host capabilities, I think we could support cache allocation later.03:22
*** ihrachys has quit IRC03:22
lakerzhousudipto, I certainly well, thanks for the great work :)03:22
sudiptoyeah, thought of that.03:22
hongbineliqiao: could you elaborate?03:22
hongbineliqiao: perhaps sudipto can comment on your question03:23
*** ihrachys_ has quit IRC03:24
sudiptohongbin, this is something that eliqiao is driving in nova: https://blueprints.launchpad.net/nova/+spec/cat-support (i am guessing this is what it is?)03:24
eliqiaosudipto: yes.03:25
*** fnaval has joined #openstack-meeting03:25
hongbini see03:25
hongbinit looks like a good to have03:25
eliqiaosudipto: That's for VM support in nova, though libvirt.03:25
sudiptoeliqiao, but i think the l3-cache would apply to containers too...03:26
eliqiaohongbin: for container support, we could leverage other software, like intel-cat-cmt ..03:26
*** dmorita has quit IRC03:26
sudiptois it supported by all the servers of intel?03:26
eliqiaosudipto: yes, only on xeon cpu.03:26
sudiptoin order to support this, we would have to do quite a bit of plumbing in the zun code, since we don't have libvirt to our helm03:27
sudiptobut yeah we could look at this maybe in the second iteration once we have all the pieces in?03:27
eliqiaosudipto: right, I will talk with my colleage for zun support.03:27
eliqiaothey are working on an agent which will provide cache monitor/allocation.03:28
eliqiaolater we can integrate it to zun.03:28
hongbineliqiao: ack03:28
*** jrobinson is now known as jrobinson-afk03:28
hongbineliqiao: feel free to create a bp/spec if you want to lead this work03:29
eliqiaoI will find my time to review host-capabilities in zun and to see if we can support cat in zun03:29
eliqiaohongbin: okay. thx.03:29
*** thorst_ has joined #openstack-meeting03:29
*** thorst_ has quit IRC03:30
hongbinok, any other comment?03:30
sudiptohongbin, should we merge the spec, if everyone is on the same page?03:30
hongbinsudipto: i am ok with that (already gave +2)03:31
hongbinit seems lakerzhou also agreed to merge it03:31
pksinghi agree too03:31
hongbini think it is ready to go03:31
lakerzhouHongbin, I agree03:32
hongbinok03:33
hongbinsudipto: any other comment you want to make?03:33
sudiptohongbin, just would like to thank people who took the time out to review the spec. :)03:33
hongbin:)03:33
hongbinthanks sudipto for this work03:34
*** fnaval_ has joined #openstack-meeting03:34
hongbinok, next topic03:34
hongbin#topic Update image API to support multi-compute scenario (Wenzhi)03:34
*** openstack changes topic to "Update image API to support multi-compute scenario (Wenzhi) (Meeting topic: zun)"03:34
hongbin#link https://review.openstack.org/#/c/432857/03:34
*** diga has quit IRC03:34
hongbinit looks wenzhi is not here03:35
hongbinhowever, he proposed an interesting patch03:35
hongbini have reviewed his patch, perhaps, i can explain it a bit03:35
hongbinwhat he proposed is an API to schedule a container03:35
hongbinthis api basically write down the host to the container object in db03:36
hongbinthen, the image api can select host based on the 'host' field in the container object03:36
sudiptohongbin, i went through the patch, thought i saw jenkins fail on that yesterday.03:37
*** fnaval has quit IRC03:37
hongbinsudipto: it seems he uploaded another patchset, perhaps, it fixed the jenkins03:37
sudiptohongbin, sure.03:38
hongbini wanted to discuss the idea here, but it seems it is better to leave it offline03:38
hongbinthen, everyone has a chance to review it03:38
mkraiYes I will review it and post my comments on the patch03:39
hongbinmkrai: ack03:39
hongbinok, then let's enter open discussion03:39
hongbin#topic Open Discussion03:39
*** openstack changes topic to "Open Discussion (Meeting topic: zun)"03:39
hongbinanyone has a topic to bring up?03:39
mkraiYes I have one03:40
hongbinmkrai: go ahead03:40
mkrai#link https://review.openstack.org/#/c/431442/03:40
mkraithis is support to add image-search API in zunclient03:40
mkraiBut seems the response object for image drivers, glance and docker are completely different03:40
mkraiSo we need to think of some common response object for the same03:41
hongbinyes, possibly, we need to define an object for image03:41
mkraidocker search returns 'stars', 'official' etc which glance doesn't have03:41
*** armax has quit IRC03:42
hongbinmkrai: one way to handle that is to define a metadata field03:42
mkraihongbin: that includes driver specific fields?03:42
hongbinmkrai: possibly03:43
hongbinmkrai: another way to handle that is to simply hide those fields03:43
mkraihongbin: Do you think just the name and driver would be enough?03:43
mkraiwith metadata field03:44
hongbinmkrai: personally, i would like to see more fields that are common for both docker and glance03:44
hongbini.e. size, location, etc.03:44
*** ihrachys has joined #openstack-meeting03:45
mkraihongbin: docker search don't show size and all03:45
sudiptolocation is important IMHO03:45
mkraionly common field is 'name' I guess03:45
sudiptoIIUC, that should tell you if it's a public registry or a private one.03:45
mkraiNAME                  DESCRIPTION                                    STARS OFFICIAL  AUTOMATED03:46
mkraiThese are the fields for docker03:46
hongbini see03:46
sudiptobut i thought there was debate around that in glance, whether the location should be admin only.03:46
hongbinsudipto: ack03:46
hongbinmkrai: then, i am ok to start with name and driver03:47
mkraiI will try to create a common response object and post it on review link03:47
mkraiYou all can post your suggestion on that03:47
mkraihongbin: ack03:48
hongbinthanks mkrai03:48
mkraihongbin: sudipto Thanks03:48
*** dimtruck is now known as zz_dimtruck03:48
Namratahongbin:I am working on container resource.the patch is ready I am testing it.03:48
mkraiThat's all from my side.03:48
Namratawill upload it today03:49
hongbinNamrata: awesome03:49
*** yamahata has joined #openstack-meeting03:49
hongbinNamrata: did the heat team give you enough comment for this feature?03:50
*** yangyapeng has quit IRC03:50
Namratai havent joined the team meeting03:50
Namratai will do this week and ask for reviewing the patches03:51
hongbinNamrata: that is fine, i will help you to ping them03:51
Namratasure .thanks hongbin03:51
*** yangyapeng has joined #openstack-meeting03:51
*** vishnoianil has quit IRC03:52
hongbinthanks Namrata for working on this feature in heat03:52
Namratahongbin:thanks for sugesting the same03:52
hongbinok, it seems there is no more topic to bring up03:53
*** baoli has joined #openstack-meeting03:53
hongbinthen, i will end the meeting a bit earlier, all , thanks for joining the meeting03:53
hongbin#endmeeting03:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"03:53
openstackMeeting ended Tue Feb 14 03:53:45 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-02-14-03.00.html03:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-02-14-03.00.txt03:53
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-02-14-03.00.log.html03:53
*** guoshan has quit IRC03:54
*** shubhams has left #openstack-meeting03:55
*** pksingh has quit IRC03:56
*** david-lyle_ has joined #openstack-meeting03:56
*** lakerzhou has quit IRC03:56
*** abhishekk has joined #openstack-meeting03:56
*** Namrata has quit IRC03:57
*** david-lyle has quit IRC03:58
*** tpatil has joined #openstack-meeting03:59
*** takashi has joined #openstack-meeting03:59
*** links has joined #openstack-meeting03:59
*** Dinesh_Bhor has joined #openstack-meeting04:00
*** sagara has joined #openstack-meeting04:00
samPhi o/04:00
tpatilHi04:01
Dinesh_BhorHi all04:01
sagarasamP: hi04:01
samP#startmeeting masakari04:01
openstackMeeting started Tue Feb 14 04:01:10 2017 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.04:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:01
*** openstack changes topic to " (Meeting topic: masakari)"04:01
openstackThe meeting name has been set to 'masakari'04:01
samPhi all..04:01
*** rkmrHonjo has joined #openstack-meeting04:01
abhishekk\o04:01
rkmrHonjoHi04:01
samP#topic Bugs04:01
*** openstack changes topic to "Bugs (Meeting topic: masakari)"04:01
takashio/04:01
samPrkmrHonjo has reported 2 bugs.04:02
samPrkmrHonjo: could you please explain them?04:02
rkmrHonjoOK.04:02
tpatil# link : https://bugs.launchpad.net/masakari/+bug/166351304:02
openstackLaunchpad bug 1663513 in masakari "Masakari failed to rescue PAUSED instances" [Undecided,New]04:02
tpatil# link : https://bugs.launchpad.net/masakari/+bug/166351304:03
rkmrHonjotpatil: thanks.04:03
rkmrHonjoIn this report, I found that masakari can't rescue PAUSED instance.04:03
takashirkmrHonjo: you mean, the instance paused by users, right?04:04
rkmrHonjoYes. Masakari try to call stop API to paused instance, but the return code of API is "409".04:05
*** aeng has quit IRC04:05
tpatilrkmrHonjo: when user pause instance, what libvirt event is sent in the notification?04:05
*** baoli has quit IRC04:06
takashirkmrHonjo: I'd like to confirm which version you are using for your testing04:06
takashirkmrHonjo: Does it include this change? https://review.openstack.org/#/c/430121/04:06
rkmrHonjotpatil: Please wait, I check it.04:06
rkmrHonjos/tpatil/takashi/g04:07
takashiI think that tpatil is thinking about the smme thing as me...04:07
tpatiltakashi: yes04:07
*** Swami_ has joined #openstack-meeting04:08
*** Swami has quit IRC04:08
*** dmorita has joined #openstack-meeting04:08
rkmrHonjotpatil: Reproduce procedure is... 1. Pause instance. 2. Kill the instance process after paused. This is a simulation of instance failure.04:08
abhishekkIMO if we do this, then user will never be able to pause the instance04:08
*** Swami__ has quit IRC04:08
*** Swami has joined #openstack-meeting04:09
takashirkmrHonjo: so you are trying the case when some process failure happens 'after' user pauses their instance.04:09
takashis/some process/qemu process/g04:09
rkmrHonjotakashi: Yes.04:09
rkmrHonjoPausing is not trigger. Paused instance failure is the trigger of this bug.04:10
rkmrHonjoSo https://review.openstack.org/#/c/430121/ doesn't resolve this issue.04:11
takashirkmrHonjo: ok. so let's back to tpatil's question. What kind of notification does masakari monitor send for that situation?04:12
takashiLIFECYCLE STOPPED_FAILED?04:12
*** fzdarsky|afk has joined #openstack-meeting04:12
takashijust for my confirmation04:12
rkmrHonjotakashi: Ah...Please wait.04:12
*** dmorita has quit IRC04:12
abhishekkinshort wheneve masakari-engine receives notification, we need to reset it to error state?04:13
abhishekkwe are setting instance to error sstate if it is i resize (IMO this is for host failure)04:14
abhishekks/i/in04:14
rkmrHonjotakashi: STOPPED_FAILED, yes.04:15
takashirkmrHonjo: thx04:15
takashiabhishekk: your are talking about this? https://github.com/openstack/masakari/blob/master/masakari/engine/drivers/taskflow/instance_failure.py#L60-L6204:16
abhishekktakashi: yes04:16
takashithe one for host failure https://github.com/openstack/masakari/blob/master/masakari/engine/drivers/taskflow/host_failure.py#L95-L10204:16
tpatilIf user has paused instance, does libvirt generated STOPPED_FAILED event?04:17
abhishekkIMO this way for each vm_state except (shelved_offloaded) we can trigger this failure, am I right?04:17
takashitpatil: STOPPED_FAILED is not caused just for pausing instance04:18
takashitpatil: even after we pause instance, qemu process for the paused instance remains on compute node, and ...04:19
rkmrHonjoabhishekk, takashi: Maybe yes. I'm checking other statuses now. PAUSED is one of the examples.04:19
samPPased by the user right? Notification sent by the process monitor?04:19
takashitpatil: if we get some failure for the qemu process, we get notification with STOPPED_FAILED04:19
rkmrHonjosamP: Instance monitor sent notification. Because this is a instance failure.04:20
abhishekkHe is talking if instance is paused and after oausing if it fails (killing qemu process) then04:20
abhishekks/ousing/pausing04:20
tpatiltakashi: and in this case, you are simulating to kill the qemu process and then it send STOPPED_FAILED event, correct?04:20
takashitpatil: right04:22
*** sdake has quit IRC04:22
*** anilvenkata has joined #openstack-meeting04:22
takashiso the point here is, we can get STOPPED_FAILED event for active instance and poused instance, because for both cases qemu process remains and send that notification when the qemu process dies for some reasons04:23
tpatilmasakari-engine doesn't have enough information to take all these smart decision as it's unaware of what's going on the compute node.04:23
takashilike OOM-killer04:23
takashis/send/masakari-monitor sends/04:24
rkmrHonjotakashi: You're right. thanks.04:24
tpatilrkmrHonjo: Do you think calling reset-state api, stop and start will solve this problem?04:25
rkmrHonjotpatil:Yes.04:25
takashiIf we can assume that STOPPED_FAILED is raised only when qemu process dies unexpectedly, it makes sense to me to reset the instance state to error for any cases04:26
tpatilbefore calling reset-state, engine can check the vm state/task status and accordingly make some decisions and call reset-state api before calling stop and start apis.04:26
*** ayogi has joined #openstack-meeting04:27
takashitpatil: that is what we are doing for resizing, right?04:27
tpatilcorrect04:27
samPIMO, if it is a user paused instance, in this case we change the state to paused -> active/stop04:27
samPis acceptable?04:27
samPis it acceptable?04:27
rkmrHonjosamP: Yeah. I agree with tpatil's opinion.04:28
*** ihrachys has quit IRC04:28
tpatilrkmrHonjo: Let me confirm the problem again. user pauses instance, before it's paused gracefully qemu process dies and it generate STOPPED_FAILED event and send an notification to masakari. Masakari check the vm/task state and call reset-state api before calling stop and start apis.04:30
tpatilso finally user will see the instance in active status and NOT in paused state.04:30
*** thorst_ has joined #openstack-meeting04:30
tpatilprovided qemu process is up again on the compute node.04:31
tpatilrkmrHonjo: Please describe the reproduction steps on the LP bug in detail04:32
samPtpatil: thanks, this method looks good to me04:32
rkmrHonjotpatil: OK, I describe the steps.04:32
samPtpatil: so, user can paused it again04:33
*** adisky_ has joined #openstack-meeting04:33
samP#action rkmrHonjo add reproduction steps on the LP bug #1663513 in detai04:34
openstackLaunchpad bug 1663513 in masakari "Masakari failed to rescue PAUSED instances" [Undecided,New] https://launchpad.net/bugs/166351304:34
*** ihrachys has joined #openstack-meeting04:34
rkmrHonjotpatil, samP: I agree with your opinion.04:34
*** hongbin has quit IRC04:34
tpatilsamP: Ok04:34
samPOK then, lets discuss details on the LP or gerrit for this04:35
takashi+104:35
sagara+104:35
rkmrHonjo+104:35
samPNext bug,04:35
samP#link https://bugs.launchpad.net/masakari/+bug/166418304:35
openstackLaunchpad bug 1664183 in masakari "Failed to update a status of hosts." [Undecided,New]04:35
*** thorst_ has quit IRC04:35
rkmrHonjoOK. This report says... Masakari user can't update status of host-foo if there are "error" notifications in host-bar. (host-foo and bar belong to same segment.)04:36
rkmrHonjoIs this correct?04:36
tpatilyou can only update on_maintenance and reserved properties of hosts04:36
tpatilthere is no status field for host04:37
Dinesh_Bhorhost doesn't have any property like status04:37
rkmrHonjoAh, sorry, "status" means on_maintenance.04:37
rkmrHonjoI fix LP after that.04:37
takashiif the error is temporal one, it will be resolved by periodic task. Is it right?04:38
takashiIn my understanding, if the fail over segment has notifications only in finished or failed status, we can update the hosts in it04:38
samPtakashi: same understanding04:39
tpatiltakashi: correct04:39
takashiand periodic task should pick up notifications in error, and change it to finished or failed04:39
samPso, we have to wait for periodic task to clear it04:39
tpatilthe notification is error status will be processed by the periodic tasks04:40
takashi#link https://review.openstack.org/#/c/431335/04:40
takashithis one04:40
tpatil#link :https://review.openstack.org/#/c/427072/04:41
*** donghao has joined #openstack-meeting04:42
takashisorry, I pasted wrong url...04:42
takashi:-(04:42
tpatilafter processing notification in error status, it will change the status either to finished or failed. After that, you should be able to change the on_maintenance flag04:42
rkmrHonjoAll: Thank you for explaining.In conclusion, this is correct as Masakari specs, right?04:43
*** Kevin_Zheng has quit IRC04:43
tpatilrkmrHonjo: yes04:43
*** jrobinson-afk is now known as jrobinson04:43
samPrkmrHonjo: yes, if there is error notifications in the segment, you have to wait till periodic task clear the state of the notifications04:44
rkmrHonjosamP, tpatil:OK. I fix describe and change status to "invalid" after that.04:44
samPrkmrHonjo: thanks04:44
samPis there any other bugs to discuss?04:45
tpatilrkmrHonjo: the default interval of periodic task is 120 seconds04:45
takashisamP: I think tpatil listed up some bugs in high priority etherpad04:46
*** donghao has quit IRC04:46
takashiso can we move to the topic?04:46
samPtakashi: yep..04:46
samPthat is the next topic04:46
samP#topic High priority items for Ocata04:46
*** openstack changes topic to "High priority items for Ocata (Meeting topic: masakari)"04:46
samPlest discuss about tpatil's list04:47
samP#link https://etherpad.openstack.org/p/ocata-priorities-masakari04:47
samPI added the items for python-masakariclinet and masakari-monitors.04:48
tpatilAdd periodic tasks to process notifications in error/new states04:48
tpatil# link : https://review.openstack.org/#/c/431335/04:49
tpatilabove patch is pending for review04:49
*** sudipto_ has quit IRC04:50
*** sudipto has quit IRC04:50
*** adiantum1 has joined #openstack-meeting04:50
samPtpatil: I will review it04:50
tpatil2. Implement reserve host recovery methods04:50
tpatil#link : https://review.openstack.org/#/c/432314/04:50
tpatilI have review this patch and voted -104:51
tpatilDinesh will address these review comments04:51
Dinesh_Bhor^^ I will address them today04:51
samPtpatil: Dinesh_Bhor thanks04:51
takashiwill review the patch, and also its spec04:52
*** adiantum has quit IRC04:53
*** adiantum1 is now known as adiantum04:53
*** Julien-zte has joined #openstack-meeting04:53
tpatilRelease notes build is failing04:54
tpatilIt requires major changes04:54
*** guoshan has joined #openstack-meeting04:55
rkmrHonjotpatil: major changes?04:55
samPtpatil: What changes are you proposing?04:55
*** aeng has joined #openstack-meeting04:55
tpatilafter you build the release notes using to command, it should show Newton Release Notes and Current Series Release Notes04:55
tpatils/to/tox04:55
tpatilcurrently, it's not showing Newton Release notes at all.04:56
takashifyi: http://docs.openstack.org/releasenotes/nova/unreleased.html04:57
tpatilAlso ,the release note formatting is incorrect at few other places which we are planning to fix in the same LP bug04:57
takashiin this release note, we can find newton release note in the page also as current seriese04:58
*** yuanying has quit IRC04:58
*** yuanying has joined #openstack-meeting04:58
samPtpatil: takashi: got it.04:58
samPtpatil: are you addressing this on same LP bug?04:58
tpatilsamP: yes04:59
*** guoshan has quit IRC04:59
samPtpatil: OK, thanks. Me too take look into this, sice masakari-monitors,and python-masakariclient need the same fix05:00
sagarawe have no time, do we need to change the room?05:00
samPnop05:00
samPOK, lets finish the discussion here and move to #opesntack-masakari05:00
*** esberglu has joined #openstack-meeting05:01
samPthank you all..05:01
tpatilThanks05:02
samPlets finish, please use #opesntack-masakari or ML for further discussion05:02
samP#endmeeting05:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:02
openstackMeeting ended Tue Feb 14 05:02:30 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-02-14-04.01.html05:02
*** zul has quit IRC05:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-02-14-04.01.txt05:02
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-02-14-04.01.log.html05:02
*** tpatil has quit IRC05:02
*** vishnoianil has joined #openstack-meeting05:04
*** sagara has left #openstack-meeting05:04
*** esberglu has quit IRC05:05
*** VW has joined #openstack-meeting05:10
*** VW has quit IRC05:11
*** VW has joined #openstack-meeting05:11
*** unicell has joined #openstack-meeting05:13
*** unicell has quit IRC05:14
*** nadya has joined #openstack-meeting05:16
*** nadya has quit IRC05:17
*** unicell has joined #openstack-meeting05:18
*** zhiyuan has quit IRC05:19
*** gcb has quit IRC05:20
*** gcb has joined #openstack-meeting05:20
*** VW has quit IRC05:22
*** zul has joined #openstack-meeting05:24
*** fnaval has joined #openstack-meeting05:25
*** sudipto_ has joined #openstack-meeting05:26
*** sudipto has joined #openstack-meeting05:26
*** fnaval_ has quit IRC05:28
*** ihrachys_ has joined #openstack-meeting05:28
*** ihrachys has quit IRC05:29
*** vishnoianil has quit IRC05:32
*** vishnoianil has joined #openstack-meeting05:34
*** unicell1 has joined #openstack-meeting05:40
*** unicell has quit IRC05:41
*** links has quit IRC05:55
*** guoshan has joined #openstack-meeting05:55
*** sandanar has joined #openstack-meeting05:56
*** guoshan has quit IRC06:00
*** lpetrut has joined #openstack-meeting06:00
*** emagana has joined #openstack-meeting06:08
*** emagana has quit IRC06:09
*** emagana has joined #openstack-meeting06:09
*** links has joined #openstack-meeting06:12
*** salv-orlando has joined #openstack-meeting06:12
*** jtomasek has quit IRC06:12
*** ijw has quit IRC06:13
*** guoshan has joined #openstack-meeting06:26
*** sudipto_ has quit IRC06:26
*** sudipto has quit IRC06:26
*** ihrachys has joined #openstack-meeting06:28
*** ihrachys_ has quit IRC06:30
*** thorst_ has joined #openstack-meeting06:32
*** padkrish has joined #openstack-meeting06:32
*** jrobinson has quit IRC06:38
*** padkrish has quit IRC06:42
*** Hosam has joined #openstack-meeting06:43
*** thorst_ has quit IRC06:45
*** links has quit IRC06:48
*** esberglu has joined #openstack-meeting06:50
*** lhx__ has quit IRC06:51
*** rcernin has joined #openstack-meeting06:54
*** esberglu has quit IRC06:55
*** nkrinner_afk is now known as nkrinner06:56
*** sudipto has joined #openstack-meeting06:56
*** sudipto_ has joined #openstack-meeting06:56
*** dmacpher has quit IRC06:59
*** ykatabam has quit IRC06:59
*** salv-orl_ has joined #openstack-meeting07:00
*** LaochMumhain has joined #openstack-meeting07:00
*** LaochMumhain has quit IRC07:00
*** sridharg has joined #openstack-meeting07:01
*** iyamahat has joined #openstack-meeting07:02
*** links has joined #openstack-meeting07:02
*** salv-orlando has quit IRC07:03
*** andreas_s has joined #openstack-meeting07:03
*** lpetrut has quit IRC07:08
*** artom has quit IRC07:11
*** ihrachys_ has joined #openstack-meeting07:11
*** ihrachys has quit IRC07:13
*** lpetrut has joined #openstack-meeting07:14
*** takashi has quit IRC07:14
*** ihrachys has joined #openstack-meeting07:14
*** tesseract has joined #openstack-meeting07:15
*** ihrachys_ has quit IRC07:17
*** artom has joined #openstack-meeting07:18
*** ihrachys has quit IRC07:20
*** claudiub|2 has joined #openstack-meeting07:20
*** ihrachys has joined #openstack-meeting07:23
*** bkopilov has quit IRC07:26
*** lpetrut has quit IRC07:27
*** bkopilov_ has quit IRC07:27
*** rasca has joined #openstack-meeting07:28
*** cody-somerville has joined #openstack-meeting07:32
*** csomerville has quit IRC07:32
*** Douhet has quit IRC07:33
*** Douhet has joined #openstack-meeting07:34
*** takahara has quit IRC07:35
*** adiantum has quit IRC07:36
*** adiantum1 has joined #openstack-meeting07:36
*** ekuris__ has joined #openstack-meeting07:37
*** VW has joined #openstack-meeting07:38
*** adiantum1 is now known as adiantum07:38
*** guoshan_ has joined #openstack-meeting07:39
*** Hosam_ has joined #openstack-meeting07:40
*** Hosam has quit IRC07:40
*** rasca has quit IRC07:41
*** lhx__ has joined #openstack-meeting07:41
*** guoshan has quit IRC07:41
*** jprovazn has joined #openstack-meeting07:43
*** emagana has quit IRC07:46
*** yamamoto has quit IRC07:47
*** nijaba has quit IRC07:49
*** zul has quit IRC07:50
*** ltomasbo|away is now known as ltomasbo07:50
*** links has quit IRC07:50
*** nijaba has joined #openstack-meeting07:52
*** nijaba has quit IRC07:52
*** nijaba has joined #openstack-meeting07:52
*** links has joined #openstack-meeting07:52
*** hsushil10 has joined #openstack-meeting07:55
*** eranrom has joined #openstack-meeting07:55
*** nadya has joined #openstack-meeting07:56
*** crinkle is now known as cmurphy07:57
eranrom#startmeeting storlets08:00
openstackMeeting started Tue Feb 14 08:00:40 2017 UTC and is due to finish in 60 minutes.  The chair is eranrom. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: storlets)"08:00
openstackThe meeting name has been set to 'storlets'08:00
*** akihito has joined #openstack-meeting08:00
eranromHi08:00
eranromakihito: Hi08:00
akihitohi08:01
*** takashi has joined #openstack-meeting08:01
eranromtakashi: hi08:01
takashieranrom: hi08:01
eranromI do not have anything special for today.08:02
takashiIs kota_ already here? I heard that he should be late for some minutes08:02
eranromtakashi: no, lets wait, I wanted to ask him something...08:03
takashieranrom: ok08:03
takashinot so big topics from my side. just would like to ask some reviews about high-priority items08:03
takashieranrom: Can I ask one thing before kota_ comes?08:04
eranromtakashi: sure, please do08:04
*** VW has quit IRC08:04
takashiabout container id problems: https://review.openstack.org/#/c/425054/08:04
*** kota_ has joined #openstack-meeting08:04
kota_hello08:05
eranromkota_: hi08:05
kota_sorry for delay08:05
takashikota_: hi08:05
*** Dinesh_Bhor has left #openstack-meeting08:05
eranromtakashi: right, I said I will try your fix, did not get to it. Will try today08:05
akihitohi08:05
takashieranrom: Do you have any update about using whole id as a scope in container?08:05
eranromtakashi: sorry not yet. Will try today08:05
kota_what's going on?08:06
takashieranrom: OK. I'll leave my +2 later on the patch, so if you find any difficulty let's land your fix first08:06
eranromtakashi: thanks!08:06
takashikota_: just talking about container id fixes08:06
eranromkota_: good thanks08:06
kota_it looks like you all get an answer ;-)08:06
takashihttps://review.openstack.org/#/c/425054/08:06
kota_great08:06
takashi:-)08:06
eranromAs I have mentioned I do not have anything special.08:06
eranromkota_: I wanted to ask you if you know when stable/ocata is planned for Swift08:07
kota_AFAIK, soon08:07
kota_maybe wed or thu on notmyname08:07
eranromok, thanks.08:08
kota_I saw some notice on the release this morning at irc openstack-swift channel08:08
*** makowals has quit IRC08:08
eranromkota_: ok, will have a look08:08
eranromOther than that, some of us are meeting next week. Yey.08:09
eranromplease see if there is anything to add here: https://etherpad.openstack.org/p/storlets-pike-design-summit08:09
kota_k08:09
akihitoI put topic of agent logging to etherpad.08:09
kota_akihito: good08:09
*** makowals has joined #openstack-meeting08:09
eranromakihito: saw it. its a good point.08:09
akihitoI would like to discuss this topic in PTG.08:10
akihitoThank you!08:10
eranromakihito: yep.08:10
*** sshnaidm|off is now known as sshnaidm08:10
eranromits a good subject08:10
*** pcaruana has joined #openstack-meeting08:11
kota_though i didn't add the topic to meeting agenda today, can i put a question here?08:11
eranromkota_: please do08:11
kota_ok08:11
takashikota_: sure08:11
kota_thanks08:11
kota_so... I had a problem with my AWS vm with s2aio08:12
kota_I didn't dig why/what happens yet so i'm going to describe what I got in the environment08:12
kota_here08:12
kota_at first, I made a s2aio environment with clean ubuntu 16.04 vm via ./s2aio.sh08:13
kota_strictly speaking ./s2aio.sh dev host08:13
*** adiantum has quit IRC08:13
kota_it worked as expected all environment got ready to use, yey08:13
kota_however08:13
*** ihrachys has quit IRC08:13
kota_once I did suspend the vm08:13
kota_and re-launch it, the environment didn't work anymore08:14
kota_do you have any ideas on that?08:14
eranromkota_: I am afraid this is a known issue. and to the best of my knowledge it has to do with Swift using a loopback device over a local file08:14
kota_with my quick view, the keystone process was being missing08:14
eranromright. also keystone and swift are not necessarily getting up08:15
kota_eranrom: yeah, I tried to ./s2aio.sh swift stop/start with your patch08:15
takashikota_: does your vm itself run?08:15
kota_eranrom: but nothing resolved08:15
kota_takashi: sure08:15
takashikota_: ok08:15
kota_and one more issue on that08:15
eranromdid you do the stop before the vm was suspended?08:15
kota_when i tried to re-install via ./s2aio.sh dev host08:16
*** ekuris__ has quit IRC08:16
kota_we cannot do that maybe due to that we need something like unstack.sh?08:16
eranromkota_: that is right.08:16
kota_so I have to build brand-new environment with clean vm with cry a lot :/08:16
eranromwell, you can try and do:08:17
kota_eranrom: I didin't call stop before suspend08:17
eranromunstack.sh08:17
kota_ah08:17
eranromthen run s2aio.sh again08:17
eranromand in following 'suspends' stop before you suspend08:17
kota_and I found a behavior which may be problem08:17
eranromit is a problem :-)08:18
kota_in the suspend, aws vm seems to delete /tmp files08:18
eranromoh, I see.08:18
kota_and ./s2aio.sh looks like to prepare a lot of files in the dir.08:18
kota_ok, what I can try is unstack.sh and then ./s2aio.sh again08:19
eranromkota_: yes.08:19
kota_I'm not sure I had tried that.08:19
eranromIf this does not help lets discuss in IRC08:19
eranromI should mention the following:08:19
*** ihrachys has joined #openstack-meeting08:20
eranrom1. There is a new patch that "port" all s2aio to devstack (no ansible)08:20
*** sagara has joined #openstack-meeting08:20
*** r-mibu has quit IRC08:20
*** masahito has joined #openstack-meeting08:20
eranrom2. This patch also does not use /tmp anymore08:20
*** iyamahat has quit IRC08:20
kota_oh, nice08:20
*** knangia has quit IRC08:20
*** masahito has quit IRC08:21
eranrom3. This patch supports install, stop, start08:21
*** masahito has joined #openstack-meeting08:21
eranrom4. install is equivalent to stack.sh08:21
takashimakes much sense08:21
eranrom5. start and stop merely start and stop Swift and Keystone. There used to be a devstack equivalent but its deprecated08:22
*** lhx__ has quit IRC08:22
eranrom6. I will add uninstall which will be the equivalent to unstack08:22
eranromThis is the patch:08:22
eranromhttps://review.openstack.org/#/c/429636/08:22
eranromand there is a PTG topiv on that :-)08:23
eranromtopic08:23
eranromtakashi: I know you are very busy with a new project, but will be gratefull if you can comment in the discussion topics in the Etherpad.08:23
kota_sounds what I was looking for ;-)08:23
eranromkota_: hopefully :-)08:24
*** lhx__ has joined #openstack-meeting08:24
kota_eranrom: I'd like to try the patch anyway to aviod newly clean install at AWS for each time :,<08:24
eranromkota_: It does require quite a review though. Also, it depends on another patch that takes all code out of the container image08:24
*** yamamoto has joined #openstack-meeting08:24
kota_eranrom: gotcha08:25
eranromkota_: you are still welcome to use it.08:25
*** ihrachys has quit IRC08:25
*** r-mibu has joined #openstack-meeting08:25
eranromanything else?08:27
*** matrohon has joined #openstack-meeting08:27
eranromthat is anything else for now?08:27
kota_that's all to me.08:27
*** ihrachys has joined #openstack-meeting08:27
takashinothing else from my side08:27
akihitonothing08:27
kota_have a nice trip you all08:28
kota_except takashi? sorry :/08:28
takashihave a nice trip and have a nice and exciting week08:28
eranromThanks!08:28
takashiI'm looking forward to hear your great discussions!08:28
akihitoThank you08:28
takashikota_: np :-)08:28
eranromtakashi: thanks!08:28
*** rasca has joined #openstack-meeting08:29
eranromThank you all for joining.08:29
eranrom#endmeeting08:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:29
openstackMeeting ended Tue Feb 14 08:29:19 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storlets/2017/storlets.2017-02-14-08.00.html08:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storlets/2017/storlets.2017-02-14-08.00.txt08:29
*** kota_ has left #openstack-meeting08:29
openstackLog:            http://eavesdrop.openstack.org/meetings/storlets/2017/storlets.2017-02-14-08.00.log.html08:29
*** ekuris__ has joined #openstack-meeting08:30
*** akihito has quit IRC08:31
*** rwsu has joined #openstack-meeting08:31
*** ociuhandu has joined #openstack-meeting08:36
*** ralonsoh has joined #openstack-meeting08:36
*** zhonghua has quit IRC08:38
*** esberglu has joined #openstack-meeting08:40
*** ociuhandu has quit IRC08:40
*** pnavarro has joined #openstack-meeting08:41
*** zhonghua has joined #openstack-meeting08:41
*** ociuhandu has joined #openstack-meeting08:42
*** esberglu has quit IRC08:44
*** rossella_s has joined #openstack-meeting08:46
*** strigazi_AFK is now known as strigazi08:46
*** ociuhandu has quit IRC08:47
*** priteau has joined #openstack-meeting08:48
*** yamahata has quit IRC08:48
*** huanxuan has quit IRC08:50
*** Swami has quit IRC08:53
*** Swami_ has quit IRC08:53
*** zhangshuai has joined #openstack-meeting08:54
*** zul has joined #openstack-meeting08:54
*** ociuhandu has joined #openstack-meeting08:57
*** egallen has joined #openstack-meeting08:58
*** phil__ has joined #openstack-meeting09:00
saggi#startmeeting karbor09:01
openstackMeeting started Tue Feb 14 09:01:55 2017 UTC and is due to finish in 60 minutes.  The chair is saggi. Information about MeetBot at http://wiki.debian.org/MeetBot.09:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:01
*** edisonxiang has joined #openstack-meeting09:01
*** openstack changes topic to " (Meeting topic: karbor)"09:01
openstackThe meeting name has been set to 'karbor'09:02
*** masahito has left #openstack-meeting09:02
saggiHi everyone09:02
edisonxiangHey09:02
zhonghuahi09:02
chenyinghi09:02
*** ociuhandu has quit IRC09:02
saggiyuval should join soon09:03
yuvalbHey (using irc on phone)09:03
*** chenhuayi has joined #openstack-meeting09:03
saggiThere is nothing on the agenda09:03
saggibut it's the tail end of the O cycle09:03
saggi#topic finishing Ocata09:03
*** openstack changes topic to "finishing Ocata (Meeting topic: karbor)"09:04
zhangshuaihi saggi, yuval09:04
*** xinyanzhang has joined #openstack-meeting09:04
zhangshuaihi saggi, yuvalb09:04
saggihi09:04
yuvalbhey09:05
chenyingThere are some bug fixes, need think about marging back to ocata branch of karbor.09:05
saggichenying, like what?09:05
zhangshuaiI'm checking some of dashboard's Bug09:06
chenyinghttps://review.openstack.org/#/c/433428/ https://review.openstack.org/#/c/433015/ about dashboard.09:06
chenyingwu also work on the bug fixes about the python-karborclient.09:06
*** cloud_player has quit IRC09:07
yuvalbchenying: new found bugs?09:08
chenyingyuvalb is working on a bug about the authentication when the service is starting.09:08
chenyingyuval Yes I found a bug about heat client creation. I am fixing it .09:09
yuvalbwe have the release next week09:10
*** electrofelix has joined #openstack-meeting09:10
chenying<yuvalb> The bug that wu found is about the help or description of karbor cmd.09:10
yuvalbsaggi has to go and I'm on phone, so let's make this quick09:11
*** shintaro has joined #openstack-meeting09:11
yuvalbocata is next week09:11
yuvalbcritical bug fixes will be merged09:12
chenyingOK we will submit the fix patch ASAP.09:12
zhangshuaihttp://xxx.xxx.xxx.xxx/identity is not works in restoring.  and http://xxx.xxx.xxx.xxx:35357/v3 is ok09:12
yuvalbdo not send patches to stable/ocata until the patch is merged in master09:12
yuvalbchenying, we spoke about that yesterday09:13
*** jtomasek has joined #openstack-meeting09:13
yuvalbzhangshuai: that depends on the keystone deployment09:13
yuvalbuwsgi vs mod_wsgi09:13
yuvalbsee keystone in devstack09:14
*** ddeja has left #openstack-meeting09:14
chenyingyuval I use the git cherry-pick -x send the merged patch to stable/ocata.09:14
yuvalbanyway, devstack shouldn't really be used for production deployment09:14
yuvalbchenying: but only after the patch to master was fully merged09:15
chenyingyuvalb No problem09:15
yuvalbgreat09:16
zhangshuaiGot it , yuvalb09:16
yuvalbanything else?09:16
*** e0ne has joined #openstack-meeting09:17
chenyingyuval Do you have any time  to review patches today? Some comments have been adressed.09:17
yuvalbI will barely have time for reviews today09:17
*** ihrachys has quit IRC09:18
*** hsushil10 has quit IRC09:18
chenying: (09:19
yuvalbanything else?09:19
chenyingIf you are free, you can see the patches that you have give comments. If they are ok, I hope that they can be merged today.09:20
yuvalbAs said, I will barley have time today09:20
chenyingOK I know.09:21
yuvalbbarely*09:21
*** amotoki has joined #openstack-meeting09:21
yuvalbright09:21
yuvalbthanks for coming09:21
yuvalb#endmeeting09:22
*** aarefiev_afk is now known as aarefiev09:22
saggi#endmeeting09:24
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:24
openstackMeeting ended Tue Feb 14 09:24:03 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:24
openstackMinutes:        http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-02-14-09.01.html09:24
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-02-14-09.01.txt09:24
openstackLog:            http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-02-14-09.01.log.html09:24
*** adiantum has joined #openstack-meeting09:25
*** sagara has quit IRC09:26
*** bkopilov has joined #openstack-meeting09:26
*** bkopilov_ has joined #openstack-meeting09:27
*** yamamoto has quit IRC09:31
*** lpetrut has joined #openstack-meeting09:31
*** gongysh has quit IRC09:32
*** gongysh has joined #openstack-meeting09:34
*** zhhuabj has quit IRC09:34
*** sheeprine has quit IRC09:39
*** sheeprine has joined #openstack-meeting09:41
*** dmorita has joined #openstack-meeting09:41
*** Julien-zte has quit IRC09:43
*** zhhuabj has joined #openstack-meeting09:47
*** Alex_Staf has joined #openstack-meeting09:52
*** kevinz has quit IRC09:53
*** hashar has joined #openstack-meeting09:54
*** dmorita has quit IRC09:54
*** tesseract-RH has joined #openstack-meeting09:56
*** emagana has joined #openstack-meeting09:58
*** iceyao has quit IRC09:59
*** ykatabam has joined #openstack-meeting09:59
*** yangyapeng has quit IRC09:59
*** nadya has quit IRC10:00
*** epico has quit IRC10:01
*** ricolin has quit IRC10:02
*** emagana has quit IRC10:03
*** shintaro has quit IRC10:03
*** apetrich has quit IRC10:04
*** tesseract has quit IRC10:04
*** donghao has joined #openstack-meeting10:05
*** yamamoto has joined #openstack-meeting10:05
*** apetrich has joined #openstack-meeting10:06
*** mickeys has quit IRC10:09
*** dmorita has joined #openstack-meeting10:10
*** donghao has quit IRC10:11
*** ricolin has joined #openstack-meeting10:11
*** sambetts|afk is now known as sambetts10:12
*** yamamoto has quit IRC10:12
*** epico has joined #openstack-meeting10:13
*** guoshan_ has quit IRC10:14
*** dmorita has quit IRC10:14
*** ociuhandu has joined #openstack-meeting10:16
*** ociuhandu has quit IRC10:21
*** ociuhandu has joined #openstack-meeting10:24
*** esberglu has joined #openstack-meeting10:27
*** chenhuayi has quit IRC10:27
*** ekuris__ has quit IRC10:27
*** esberglu has quit IRC10:32
*** sdake has joined #openstack-meeting10:34
*** sdake_ has joined #openstack-meeting10:37
*** sdake__ has joined #openstack-meeting10:39
*** sdake has quit IRC10:39
*** gongysh has quit IRC10:39
*** spotz is now known as spotz_zzz10:40
*** ociuhandu has quit IRC10:40
*** rkmrHonjo has quit IRC10:41
*** ekuris__ has joined #openstack-meeting10:42
*** sdake_ has quit IRC10:42
*** thorst_ has joined #openstack-meeting10:42
*** abalutoiu has joined #openstack-meeting10:43
*** thorst_ has quit IRC10:47
*** nadya has joined #openstack-meeting10:49
*** lhx__ has quit IRC10:50
*** sdake has joined #openstack-meeting10:51
*** rossella_s has quit IRC10:53
*** rossella_s has joined #openstack-meeting10:53
*** sdake__ has quit IRC10:53
*** ociuhandu has joined #openstack-meeting10:56
*** epico has quit IRC11:00
*** yamamoto has joined #openstack-meeting11:04
*** yamamoto has quit IRC11:04
*** rfolco has joined #openstack-meeting11:05
*** yamamoto has joined #openstack-meeting11:05
*** yamamoto has quit IRC11:07
*** mickeys has joined #openstack-meeting11:10
*** matrohon has quit IRC11:10
*** kaisers has quit IRC11:11
*** dmorita has joined #openstack-meeting11:12
*** mickeys has quit IRC11:14
*** dmorita has quit IRC11:17
*** sdague has joined #openstack-meeting11:18
*** ricolin has quit IRC11:18
*** Cibo has quit IRC11:18
*** kaisers has joined #openstack-meeting11:20
*** jrist has quit IRC11:27
*** Cibo has joined #openstack-meeting11:30
*** jkilpatr has quit IRC11:36
*** dmorita has joined #openstack-meeting11:39
*** jrist has joined #openstack-meeting11:40
*** gongysh has joined #openstack-meeting11:46
*** xiaohhui has quit IRC11:50
*** spotz_zzz is now known as spotz11:51
*** sudipto has quit IRC11:52
*** sudipto_ has quit IRC11:52
*** Hosam has joined #openstack-meeting11:52
*** Hosam_ has quit IRC11:55
*** donghao has joined #openstack-meeting11:56
*** Kevin_Zheng_ has joined #openstack-meeting11:58
*** sshnaidm has quit IRC11:59
*** donghao has quit IRC12:00
*** tommylikehu_ has joined #openstack-meeting12:00
*** dbecker has joined #openstack-meeting12:02
*** amotoki has quit IRC12:02
*** ataraday_ has joined #openstack-meeting12:04
*** sshnaidm has joined #openstack-meeting12:06
*** jkilpatr has joined #openstack-meeting12:07
*** yamamoto has joined #openstack-meeting12:08
*** askb has quit IRC12:09
*** mickeys has joined #openstack-meeting12:11
*** larainema has quit IRC12:12
*** dbecker has quit IRC12:12
*** yamamoto has quit IRC12:14
*** armstrong has joined #openstack-meeting12:14
*** mickeys has quit IRC12:15
*** liuyulong_ has joined #openstack-meeting12:15
*** yamamoto has joined #openstack-meeting12:17
*** liuyulong has quit IRC12:18
*** hashar is now known as hasharLunch12:22
*** liuyulong__ has joined #openstack-meeting12:24
*** liuyulong_ has quit IRC12:28
*** dbecker has joined #openstack-meeting12:29
*** matrohon has joined #openstack-meeting12:30
*** toscalix has joined #openstack-meeting12:31
*** Hosam_ has joined #openstack-meeting12:33
*** matrohon has quit IRC12:36
*** yangyapeng has joined #openstack-meeting12:36
*** Hosam has quit IRC12:37
*** sdake_ has joined #openstack-meeting12:41
*** Julien-zte has joined #openstack-meeting12:42
*** bkopilov has quit IRC12:43
*** bkopilov_ has quit IRC12:43
*** sdake has quit IRC12:43
*** thorst_ has joined #openstack-meeting12:45
*** larainema has joined #openstack-meeting12:54
*** jaypipes has joined #openstack-meeting12:54
*** yanyanhu has joined #openstack-meeting12:55
*** matrohon has joined #openstack-meeting12:59
*** salv-orlando has joined #openstack-meeting13:00
yanyanhu#startmeeting senlin13:00
openstackMeeting started Tue Feb 14 13:00:35 2017 UTC and is due to finish in 60 minutes.  The chair is yanyanhu. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: senlin)"13:00
openstackThe meeting name has been set to 'senlin'13:00
yanyanhuhello everyone13:00
*** elynn has joined #openstack-meeting13:01
elynnHi13:01
yanyanhuhi, elynn13:01
Qiminghello13:01
yanyanhuhi, Qiming13:01
yanyanhugood evening, I guess somebody may leave for valentine's day :)13:02
yanyanhulets wait for minutes for other attenders13:03
*** salv-orl_ has quit IRC13:03
yanyanhuok, lets get started13:04
yanyanhuhttps://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Agenda_.282017-02-14_1300_UTC.2913:05
yanyanhuhere is the agenda, please feel free to add items13:05
yanyanhu#topic ocata work items13:05
*** openstack changes topic to "ocata work items (Meeting topic: senlin)"13:05
yanyanhu"Feature Rich" Nova Server13:05
elynnIt's ongoing13:06
yanyanhuhi, elynn, I noticed basic support has been done13:06
yanyanhuyes13:06
*** hasharLunch is now known as hashar13:06
elynnThree patches merged.13:06
yanyanhunice13:06
elynnNow it support to create ports with security_groups and floating_ip13:06
yanyanhuok13:06
yanyanhuso what is the next step?13:06
elynnThere're two patches are under reviewing13:06
elynnOne is to support jinja2 in user_data13:07
elynnI think that is also important one.13:07
yanyanhuok13:07
*** XueFengLiu has joined #openstack-meeting13:07
yanyanhuI guess those ones have been enough to support VDU case xinhui described before?13:07
elynnAnother one is to handle network update13:08
elynnNot without the jinja2 patch yanyanhu13:08
yanyanhuthat is for support vdu node update, right13:08
*** zhonghua has quit IRC13:08
yanyanhufor deployment, I guess it is enough?13:08
yanyanhuelynn, I see13:08
Qimingthe network update logic is a mess13:09
*** zhonghua has joined #openstack-meeting13:09
elynnAnd Bran from vmware are testing and migrating their existing templates to  use senlin vdu profile13:09
Qimingjust spent some time reading the code13:09
elynnQiming, Why do you say so?13:09
QimingI have previously spent a whole week to refactor the code to covery all possible paths and possbilities13:09
elynnIt's not easy to handle network update actually...13:09
Qimingso I know how tricky it is to get things right13:10
yanyanhuyes, network update is not easy for we need to control the sequence of network resource operations carefully13:10
*** jmckind has joined #openstack-meeting13:10
QimingI said it is a mess because there are some new inline functions introduced, that does nothing at all13:11
Qimingit is not easy, that part I agree13:11
*** mickeys has joined #openstack-meeting13:11
*** tommylikehu_ has quit IRC13:11
*** tommylikehu_ has joined #openstack-meeting13:12
elynnYou mean I should expand inline functions in _update_network function?13:12
elynnQiming13:12
Qimingyou don't need the _get_network call at all, for example13:12
Qimingit has been well encapsulated in the sdk exception annotator13:13
*** amotoki has joined #openstack-meeting13:13
Qimingit involves a lot of unnecessary DB transactions which can be safely combined13:14
*** khappone has joined #openstack-meeting13:14
*** baoli has joined #openstack-meeting13:15
yanyanhuI guess we can define some util functions if those logics are generic enough to reuse, otherwise, we can just define local function in VDU server module13:15
elynnyes13:15
Qimingline 1127 to 1154 is now made an inline function, that is making writing test cases for it very difficult13:15
elynnI can refactor that.13:15
Qimingthe logic is already very complicated ...13:15
*** mickeys has quit IRC13:16
yanyanhuQiming, +1, inline function is very difficult to test...13:16
QimingI was never successful when trying to write an elegant unit test for inline functions13:16
elynnYou mean move that logic out? Qiming13:16
Qimingit is bad programming style, thus should be fixed13:17
elynnokay, I could do that.13:17
*** dbecker has quit IRC13:17
Qimingin previous work, I tried very hard to save code lines for validation13:18
Qimingthat is the reason I introduced 'reason' parameter to _validate_network13:18
elynnI saw that logic Qiming13:19
Qimingin this revised version, I need more time to understand how the logic flows and every corner cases covered13:19
elynnAfter refactoring, 'reason' parameter is used only for a limit part.13:19
yanyanhuso, elynn, please keeping refactoring the code, thanks a lot :)13:20
elynnI can show you the logic behind this patch :)13:20
yanyanhu:)13:20
Qimingokay, if possible, keep function complexity below 2013:20
Qimingkeep function lines below 10013:20
*** davidsha has joined #openstack-meeting13:21
Qimingthat is a high bar13:21
elynnI can try...13:21
*** annp has joined #openstack-meeting13:21
Qimingbut for maintainability's sake, it is no less important than functional correctness13:21
Qimingif you find some logics requently called, you may want to move them into the corresponding driver13:22
Qimingthat's all from me13:23
elynnokay, I will keep in mind :)13:23
Qimingmany thanks13:23
yanyanhugreat, lets move on13:23
yanyanhunext one, Engine Improvement13:24
yanyanhuxuefeng is not here I think13:24
XueFengLiuhi13:24
XueFengLiuyanyan13:24
XueFengLiu:)13:24
yanyanhuhi :)13:24
yanyanhuI throught you are not here13:24
*** mtanino has quit IRC13:24
XueFengLiuCome back13:25
XueFengLiuAbout action improvement13:25
*** abhishekk has left #openstack-meeting13:25
XueFengLiuWill split the patch13:25
yanyanhuyes13:26
XueFengLiuThen you guys help to review13:26
*** sudipto_ has joined #openstack-meeting13:26
*** sudipto has joined #openstack-meeting13:26
yanyanhuwe can split the logic at DB API layer and upper layer13:26
yanyanhuXueFengLiu, thanks a lot13:26
XueFengLiumy pleasure13:27
yanyanhuand please keep working on this as well :)13:27
yanyanhuhttps://review.openstack.org/#/c/424073/13:27
XueFengLiuWill do this tomorrow13:27
yanyanhuthanks13:27
XueFengLiuYes13:28
yanyanhuok, lets move on13:28
yanyanhuHealth Management13:28
XueFengLiuOk13:28
Qimingso yanyan's patch won't be revived?13:28
yanyanhuQiming, you mean the one about action purging?13:28
Qimingyes13:28
Qiming32933813:28
yanyanhusorry haven't resumed it...13:28
*** links has quit IRC13:28
yanyanhuI guess there won't be difficult to restore it13:29
XueFengLiuhttps://review.openstack.org/#/c/431401/13:29
QimingI think 431401 is doing the same thing, right?13:29
yanyanhudifficulty13:29
XueFengLiuThis one13:29
XueFengLiuYes13:29
Qimingokay, then 329338 can be abandoned forever?13:29
XueFengLiuWith recent code13:29
XueFengLiuHaHa13:30
Qimingthat is confusing13:30
yanyanhuQiming, I guess my patch is more generic solution for action purging13:30
yanyanhuoh, you mean this one13:30
yanyanhuhttps://review.openstack.org/#/c/431401/13:30
yanyanhuI guess I can abandon mine13:30
Qimingxuefeng didnt continue your patch13:30
yanyanhuand lets keep working on 43140113:30
Qimingseems to me he started a new one13:31
XueFengLiuThe same one13:31
yanyanhuit's ok13:31
Qimingokay, let's forget 329338 then13:31
yanyanhuyes13:31
yanyanhuI will abandon 32933813:31
XueFengLiuTwo patches about action13:31
Qimingreassign this to XueFeng now13:31
*** annp has quit IRC13:31
XueFengLiuThe first is about cluster check action13:32
*** ekuris__ has quit IRC13:32
XueFengLiuAnd https://review.openstack.org/#/c/431401/  is the same with yanyan's13:32
Qiminggot it13:32
Qimingwe can move on then13:32
yanyanhuso please keep working on it13:32
XueFengLiuTo delete all actions when we delete a cluster/node13:32
XueFengLiuOK13:33
yanyanhunice, lets move on13:33
yanyanhudocument13:33
yanyanhuQiming worked hard on document I think13:33
Qimingneed eyes on review13:33
yanyanhuand the one for lb policy has been done13:33
QimingI want all policy types documented before final RC13:34
yanyanhuyes, please help to review them, thanks a lot13:34
XueFengLiuYes, it's a hard work13:34
Qimingthen during the last week, we'll focus only on critical bugs13:34
*** kylek3h has joined #openstack-meeting13:34
yanyanhusounds great13:34
*** kylek3h has quit IRC13:34
yanyanhuok, next one13:35
yanyanhuSenlinclient13:35
Qimingfrom release time's point of view, all RCs are just practices for the final release13:35
yanyanhuyep :)13:35
*** kylek3h has joined #openstack-meeting13:35
Qimingthe ultimate goal is to make the final release stable13:35
QimingI'll try get the 3 other policy types documented in the next two days13:36
yanyanhuhi, XueFengLiu, so the functional test for client has not been started?13:36
yanyanhuQiming, thank you so much, will help to review13:36
*** Cibo_ has quit IRC13:36
XueFengLiuYanyan, sorroy not time to do now13:36
yanyanhuno problem13:36
Qimingyanyanhu, I think we need your expertise in setting up the gate job13:36
yanyanhuyes, I think I will try to spend some time on it13:37
yanyanhuto set up the gate job13:37
yanyanhuand then XueFengLiu can keep working on the test case13:37
XueFengLiuNo problem13:37
yanyanhuwill start this work in this week13:37
XueFengLiu:)13:37
Qimingwould be greate13:38
yanyanhu:)13:38
yanyanhuok next one13:38
Qimingwrting test case can be split across the team13:38
yanyanhuprofile13:38
yanyanhuQiming, yes, that can be done in parallel13:38
yanyanhuhaiwei is not here?13:38
XueFengLiuYes13:38
yanyanhuok, lets skip it. Although that is one of the most important TODO for us in next cycle13:39
Qiminganother two patches need your review13:39
Qimingthey are about support status at client side13:39
yanyanhuQiming, yes, saw them, will check them tomorrow13:39
*** iceyao has joined #openstack-meeting13:39
Qiming$ senlin policy-type-list13:39
QimingWARNING (shell) "senlin policy-type-list" is deprecated and will be removed by Apr 2017, please use "openstack cluster policy type list" instead.13:39
Qiming+--------------------------------+---------+----------------------------+13:39
Qiming| name                           | version | support_status             |13:39
Qiming+--------------------------------+---------+----------------------------+13:39
Qiming| senlin.policy.affinity         | 1.0     | SUPPORTED since 2016.10    |13:39
Qiming| senlin.policy.batch            | 1.0     | EXPERIMENTAL since 2017.02 |13:39
Qiming| senlin.policy.deletion         | 1.0     | SUPPORTED since 2016.04    |13:39
Qiming| senlin.policy.health           | 1.0     | EXPERIMENTAL since 2017.02 |13:39
Qiming| senlin.policy.loadbalance      | 1.0     | SUPPORTED since 2016.04    |13:40
Qiming| senlin.policy.region_placement | 1.0     | EXPERIMENTAL since 2016.04 |13:40
Qiming|                                |         | SUPPORTED since 2016.10    |13:40
yanyanhulooks nice13:40
Qiming| senlin.policy.zone_placement   | 1.0     | EXPERIMENTAL since 2016.04 |13:40
Qiming|                                |         | SUPPORTED since 2016.10    |13:40
Qiming+--------------------------------+---------+----------------------------+13:40
Qimingthis is the output13:40
yanyanhusorry, I broke the line :)13:40
yanyanhuthis looks great13:40
Qimingyou broke nothing at my side13:40
yanyanhu:P13:40
Qimingit is all caused by connection delay13:41
yanyanhuyes13:41
*** gouthamr has joined #openstack-meeting13:41
yanyanhuXueFengLiu, elynn, please help to review them as well if you guys have time :)13:41
yanyanhuok, those are all items in the list13:42
XueFengLiuOK13:42
yanyanhu#topic Ocata RC3 for senlin and final release for senlin-dashboard13:42
*** openstack changes topic to "Ocata RC3 for senlin and final release for senlin-dashboard (Meeting topic: senlin)"13:42
elynnwill13:42
yanyanhuso this week will be the time for senlin rc3 and final release for senlin-dashboard13:42
yanyanhuplan to cut the release by this Tuesday13:42
Qimingcome on13:43
elynntoday is tuesday13:43
Qimingtoday is Tuesday13:43
yanyanhuso if there is any critical fix, please push it13:43
yanyanhusorry...13:43
yanyanhumisclicking13:43
yanyanhuThursday13:43
yanyanhuate too much chocolate13:43
elynn:)13:44
Qimingbad for your brain, boy13:44
yanyanhuok, so open discussion now13:44
yanyanhuQiming, agree...13:44
yanyanhu#topic open discussion13:44
*** openstack changes topic to "open discussion (Meeting topic: senlin)"13:45
QimingI'm really curious about the mistral workflow progress13:45
yanyanhuany more want to discuss?13:45
yanyanhuoh, btw, our final mascot has been ready13:45
*** yamamoto has quit IRC13:45
elynno?13:45
Qimingbut ... I think the girl may be dating ...13:45
yanyanhuQiming, I think xinhui will talk with mistral guys in PTG13:45
yanyanhuhope she can bring back more news13:45
Qiminghttps://www.dropbox.com/sh/b8kpj5k29eaf65t/AADoIo9VUz14A81c--UTRtLNa?dl=013:46
yanyanhuWoW13:46
yanyanhugood for her :P13:46
yanyanhuelynn, will forward you guys the mail about Mascot13:46
yanyanhuit's cool13:46
Qimingthe link I pasted above13:46
elynnWhat's that?13:46
Qimingthat is the mascot for Senlin13:47
elynnAn unknown webside13:47
Qimingthe final version13:47
yanyanhusigh,I can't open that link...13:47
yanyanhuat home13:47
Qimingneed proxy I think13:47
yanyanhuyes13:47
yanyanhuseems so13:47
*** lamt has joined #openstack-meeting13:47
Qimingcan you access https://snag.gy/ ?13:47
elynnThat is the final version?13:48
*** ekuris__ has joined #openstack-meeting13:48
yanyanhuelynn, think so13:48
yanyanhuQiming, yes13:48
yanyanhuthat is accessible13:48
elynnLooks sweet, looks like tree family.13:48
Qimingokay, I'm pasting to that site13:48
yanyanhuhaha13:48
Qimingthe link will be ..13:49
Qiming..13:49
Qiming(uploading )13:49
Qiming..13:49
*** janzian has joined #openstack-meeting13:49
Qiming..13:49
Qiminghttps://snag.gy/ZUNIkV.jpg13:49
yanyanhusaw it, haha13:49
XueFengLiuhaha13:50
Qimingso many .... trees13:50
Qiming:D13:50
yanyanhuthanks a lot for the effort of Heidi and her team13:50
*** Hosam_ has quit IRC13:50
elynnWhere will we put that logo?13:51
Qiminganywhere13:51
Qimingwhen you need to tell a story about it13:51
*** jlibosva has joined #openstack-meeting13:51
*** mlavalle has joined #openstack-meeting13:51
yanyanhuyou can print it on your T-shirt13:51
yanyanhu:)13:51
elynnThat's a good idea :D13:51
XueFengLiuFor example senlin wiki13:52
Qimingright, right13:52
QimingI should have done that13:52
*** sudipto has quit IRC13:52
*** sudipto_ has quit IRC13:52
Qimingnoted, as a work item in etherpad13:52
yanyanhuthanks :)13:53
yanyanhuok, so that's all topics for today13:53
yanyanhuany more for discussion?13:53
Qimingno from me13:53
elynnnope13:54
yanyanhuok, thanks all you guys for joining13:54
XueFengLiuIn wiki we'd better add two things:1.tell peoplesome link need vpn  2.add some Frequently Asked Questions13:54
yanyanhuXueFengLiu, +1, FAQ is important13:54
XueFengLiu:)13:54
Qimingadded to etherpad13:55
yanyanhuthanks, Qiming13:55
XueFengLiuNo need much ,just several FAQ13:55
*** haleyb_ has joined #openstack-meeting13:55
*** yamamoto has joined #openstack-meeting13:55
yanyanhuok, so happy valentine's day to you all and have a good night:)13:56
Qimingu 213:56
XueFengLiugood night, all:)13:56
Qimingbye13:56
yanyanhubye13:56
elynngood night13:56
yanyanhu#endmeeting13:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:56
openstackMeeting ended Tue Feb 14 13:56:48 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-02-14-13.00.html13:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-02-14-13.00.txt13:56
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-02-14-13.00.log.html13:56
*** yanyanhu has quit IRC13:57
*** phil__ has quit IRC13:57
*** elynn has left #openstack-meeting13:57
*** julim has joined #openstack-meeting13:57
*** fguillot has joined #openstack-meeting13:58
*** john-davidge has joined #openstack-meeting13:59
*** ihrachys has joined #openstack-meeting13:59
jlibosva#startmeeting networking14:00
openstackMeeting started Tue Feb 14 14:00:00 2017 UTC and is due to finish in 60 minutes.  The chair is jlibosva. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
jlibosvaHello friends! o/14:00
ataraday_hi14:00
dasanindHi14:00
*** reedip_ has joined #openstack-meeting14:00
*** esberglu has joined #openstack-meeting14:00
mlavalleo/14:00
*** rajivk__ has joined #openstack-meeting14:00
*** tovin07 has joined #openstack-meeting14:00
jlibosva#topic Announcements14:00
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:00
haleyb_hi14:00
reedip_O/14:00
john-davidgeo/14:00
*** yamamoto has quit IRC14:00
rajivk__o/14:00
*** eharney has quit IRC14:00
jlibosvaThe PTG is next week - http://lists.openstack.org/pipermail/openstack-dev/2017-January/110040.html14:00
*** trevormc has joined #openstack-meeting14:00
*** hichihara has joined #openstack-meeting14:00
trevormco/14:00
jlibosvaWe already have quite an attendance :)14:00
*** annp has joined #openstack-meeting14:01
jlibosvaIdeas/topics to discuss are put here: https://etherpad.openstack.org/p/neutron-ptg-pike14:01
ihrachyso/14:01
hichiharao/14:01
annpo/14:01
jlibosvaI assume it's gonna we walked through soon and somehow organized14:01
*** korzen has joined #openstack-meeting14:01
kevinbentonhi14:01
jlibosvaPike specs are now open https://review.openstack.org/#/c/429855/14:01
ajoo/14:01
ihrachysyeah. note there is a -final version: https://etherpad.openstack.org/p/neutron-ptg-pike-final14:01
andreas_shi14:02
jlibosvaihrachys: ah, thanks. I didn't know about that one14:02
ihrachysthough it's not final, I believe kevinbenton was going to scrap it once more14:02
kevinbentonyeah, i want to go over one last time to assign some chairs with ihrachys and armax14:02
amotokioh, i haven't added me....14:02
kevinbentonbut i think the topics are pretty finalized14:02
*** takashi has quit IRC14:03
kevinbentoni need to see what new stuff has hit https://etherpad.openstack.org/p/neutron-ptg-pike14:03
kevinbentonover the weekend14:03
jlibosvakevinbenton: since you're here, do you want to lead? :)14:04
*** jprovazn has quit IRC14:04
kevinbentonno14:05
jlibosvaok14:05
*** hoangcx has joined #openstack-meeting14:05
kevinbenton:)14:05
jlibosvaSo about the Pike specs open - please if you have any proposals that didn't make it to Ocata, you'll need to rebase/re-propose for Pike.14:05
jlibosvaWe have a sort of a new Neutron CI meeting regularly on Tuesdays at 4pm UTC.14:06
jlibosvaThat's in 2 hours. I encourage everyone interested in gate stability to join.14:06
*** donghao has joined #openstack-meeting14:06
dasmlate allo allo14:07
dasm\14:07
jlibosvaAbout Ocata - we have an assessment https://review.openstack.org/#/c/425990/14:07
*** XueFengLiu has quit IRC14:07
jlibosvaif you are a feature owner, please have a look14:07
*** knangia has joined #openstack-meeting14:07
*** mriedem_afk is now known as mriedem14:08
ihrachysand comment14:08
jlibosvaOcata is planned to be coordinated release on Feb 22nd14:08
*** hoangcx_ has joined #openstack-meeting14:08
*** toscalix has quit IRC14:08
jlibosvaThat's all I had to announce. Anybody else wants to announce anything?14:08
jlibosvaok, moving on14:09
jlibosva#topic Blueprints14:09
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:09
*** hoangcx has quit IRC14:09
jlibosvaAs I said, Pike specs are now open so please rebase to Pike proposals that didn't make it to Ocata14:10
*** sridharg has quit IRC14:10
jlibosvaFor Ocata, I believe only very-very-critical things can be set - https://launchpad.net/neutron/+milestone/ocata-rc214:11
*** ayogi has quit IRC14:11
jlibosvaihrachys: korzen I see no patches for ovo in the wiki, do you want a dedicated topic?14:12
ataraday_Some changes for enginefacade switch will be glad to get reviews - https://review.openstack.org/#/c/402750/  and https://review.openstack.org/#/c/404715/14:12
ihrachysI will only mention that korzen and electrocucaracha started working on online migration mechanism in neutron-db-manage, and they have a WIP: https://review.openstack.org/43249414:13
ihrachysit's not ready right now, and there is some design work to do, but that's a topic that will require some oversight from the whole team later, so a heads up14:13
*** dtrainor has joined #openstack-meeting14:13
ihrachysother than that, I don't think there is much to bring up right now14:14
jlibosvaihrachys: ok, thanks for heads up14:14
*** electrocucaracha has joined #openstack-meeting14:14
jlibosvaataraday_: thanks for bringing this up, I see one already has +2 :)14:15
jlibosvaanybody else has some links that need attention?14:16
*** lamt has quit IRC14:16
*** kristian__ has joined #openstack-meeting14:16
jlibosva#info enginefacade patches: https://review.openstack.org/#/c/402750/ https://review.openstack.org/#/c/404715/14:16
*** haleyb_ has quit IRC14:16
jlibosva#info online migration mechanism WIP patch https://review.openstack.org/#/c/432494/14:16
*** haleyb_ has joined #openstack-meeting14:17
jlibosvaI think we can move on14:17
jlibosva#topic Bugs and gate failures14:17
*** openstack changes topic to "Bugs and gate failures (Meeting topic: networking)"14:17
electrocucarachajlibosva: I have one14:18
*** bobmel has joined #openstack-meeting14:18
electrocucaracha:S14:18
jlibosvaelectrocucaracha: for blueprints?14:18
jlibosvaelectrocucaracha: or bugs?14:18
electrocucarachawell, it was related with the code coverage14:18
electrocucarachaany comment is welcome https://review.openstack.org/#/c/432432/14:19
*** donghao has quit IRC14:19
jlibosvaelectrocucaracha: ok, thanks14:19
*** sridharg has joined #openstack-meeting14:19
jlibosvaI think that belongs here to gate14:20
*** trevormc has quit IRC14:20
jlibosvaI'd also like to remind here again the Neutron CI meeting, which will be in 1.66 hours: https://wiki.openstack.org/wiki/Meetings/NeutronCI14:20
*** donghao has joined #openstack-meeting14:20
jlibosvaI was the bug deputy for the last week14:21
jlibosvaNothing major has been reported last week, was pretty calm14:21
jlibosvaweird for a week so close to release :)14:21
ihrachysno one tests rc :P14:21
*** zz_dimtruck is now known as dimtruck14:22
jlibosvaarmax is the bug deputy for this week, so we're in good hands14:22
*** jamesdenton has joined #openstack-meeting14:22
jlibosvaanybody wants to raise any bug here?14:23
*** bkopilov has joined #openstack-meeting14:24
jlibosvano? so we can move to the next topic14:24
*** bkopilov_ has joined #openstack-meeting14:24
jlibosva#topic Docs14:24
*** openstack changes topic to "Docs (Meeting topic: networking)"14:24
*** boden has joined #openstack-meeting14:24
john-davidgejlibosva: Hi!14:25
jlibosvaI saw john-davidge waving at the beginning of this meeting :) Do you want to give any updates about docs?14:25
* jlibosva is too slow14:25
ihrachyshm do we have deputies for next weeks? just sayin14:25
john-davidgewanna go back to bugs for a deputy?14:25
jlibosvaihrachys: hmm, good point. I forgot about PTG14:25
jlibosva#undo14:25
openstackRemoving item from minutes: #topic Docs14:25
jlibosvaany volunteer for keeping an eye on bugs during PTG? :)14:26
ihrachyspreferrably someone not on ptg14:27
electrocucarachaI can14:28
jlibosvaelectrocucaracha: thanks!14:28
dasmelectrocucaracha: phew! thanks14:28
electrocucarachaI mean, I won't go so I can do it14:28
*** toscalix has joined #openstack-meeting14:28
mlavallethanks electrocucaracha!14:28
ihrachysyay electrocucaracha14:28
mlavallewe'll miss you in Atlante, though14:28
jlibosvaindeed14:28
amotokiwe all hope not many bugs will be filed in the release week :)14:28
dasmmlavalle: i won't miss electrocucaracha in AtlantE ;)14:29
*** links has joined #openstack-meeting14:29
electrocucarachathat will be boring amotoki14:29
jlibosvaI think we can get back to docs :)14:29
jlibosva#topic Docs14:29
*** openstack changes topic to "Docs (Meeting topic: networking)"14:29
jlibosvajohn-davidge: hi again :)14:29
john-davidgeOk, so recently we've been landing lots of patches related to #link https://bugs.launchpad.net/openstack-manuals/+bug/165637814:30
openstackLaunchpad bug 1656378 in openstack-manuals "Networking Guide uses RFC1918 IPv4 ranges instead of RFC5737" [High,In progress] - Assigned to John Davidge (john-davidge)14:30
john-davidgeAnybody is welcome to pick up a related patch if they have some free time14:30
john-davidgeAlso, there will be an openstack-manuals/neutron corss project session at the PTG sometime on monday or tuesday14:31
john-davidgeParticularly to discuss a re-organisation of the networking guide and encourage contributions14:31
john-davidgeThat's it from me14:32
amotokiyou can check the networking guide for newton release at http://docs.openstack.org/draft/draft-index.html14:32
john-davidgeamotoki: Thanks :)14:32
jlibosvajohn-davidge: thanks for updates14:32
amotokiIf you find points to be changed or added, let's file a bug and hopefully propose a patch14:32
*** diga has joined #openstack-meeting14:33
jlibosvayep, thanks amotoki14:34
john-davidgeYes, final version will be cut just before the PTG14:34
amotokijohn-davidge: did the docs team change the timing of branch cut?14:34
amotokiIIRC previously the branch was cut after several weeks after the release14:35
john-davidgeamotoki: Not that I'm aware of, that's what I last heard from asettle14:35
john-davidgeWill double check with her14:35
amotokijohn-davidge: okay, let's ask her14:35
jlibosvaanything else related to docs?14:36
*** rbak has joined #openstack-meeting14:36
john-davidgenot from me14:36
amotokime to14:36
amotokitoo14:36
jlibosvajohn-davidge: amotoki ok, thank you for all updates :)14:36
jlibosva#topic Transition to OSC14:36
*** openstack changes topic to "Transition to OSC (Meeting topic: networking)"14:36
jlibosvaamotoki: do you want "the mic"?14:36
amotokii have no specific update this week14:37
amotokiI plan to discuss the remaining transition plan in Atlanta with OSC team14:37
jlibosvaamotoki: is neutron client gonna be released the same time with all other projects?14:37
amotokijlibosva: could you elaborate more?14:38
jlibosvaamotoki: I mean if the releases are synced14:38
dasmjlibosva: afaik neutron cli is already released14:38
dasmjlibosva: cli releases were 2 (or maybe 3) weeks ag14:38
dasmo14:38
jlibosvadasm: aah, ok. thanks14:39
amotokiin Ocata, we didn't release neutronclient in the middle of releases.14:39
amotokiI agree it is not good.14:39
amotokias dasm said we released neutron client for Ocata release14:39
jlibosvaamotoki: ok, thanks. I must have missed that14:40
*** mickeys has joined #openstack-meeting14:40
amotokithat's all from me today14:40
*** haleyb_ has quit IRC14:40
jlibosvaok, moving on14:40
dasmbut, worth to mention, neutron cli is rleeased as 6.1 and marked as deprecated14:40
dasm*released14:40
*** FengShengqin1 has joined #openstack-meeting14:40
*** yamamoto has joined #openstack-meeting14:40
*** TheJulia has quit IRC14:41
jlibosvadasm: good, thanks for info14:41
jlibosva#topic Neutron-lib and planned neutron refactoring14:42
*** openstack changes topic to "Neutron-lib and planned neutron refactoring (Meeting topic: networking)"14:42
jlibosvaboden: hi, are you around?14:42
*** kevinz has joined #openstack-meeting14:42
*** larainema has quit IRC14:42
*** patrickeast has quit IRC14:42
*** scottda has quit IRC14:42
*** lamt has joined #openstack-meeting14:43
*** persia_ has quit IRC14:43
*** dolphm has quit IRC14:43
*** RuiChen has quit IRC14:43
*** fmccrthy has quit IRC14:43
*** ashtokolov has quit IRC14:43
*** JayF has quit IRC14:43
*** ALUVial has quit IRC14:43
*** mfranc213 has quit IRC14:43
jlibosvait seems like he is not14:43
mlavallemaybe too early for him14:43
*** Kevin_Zheng_ has quit IRC14:43
jlibosvayeah though he usually shows up14:43
jlibosva#topic Open discussion14:44
*** openstack changes topic to "Open discussion (Meeting topic: networking)"14:44
*** larainema has joined #openstack-meeting14:44
jlibosvathere are no new items to on demand agenda14:44
*** mickeys has quit IRC14:44
*** patrickeast has joined #openstack-meeting14:44
jlibosvaso if anybody wants to discuss anything here, now is the chance14:44
jlibosvawe have 15 mins left, so we have plenty of time14:44
bodenjlibosva: sorry I was away for a min14:44
jlibosvaboden: I knew you are around :)14:45
*** rsFF- has quit IRC14:45
jlibosva#undo14:45
openstackRemoving item from minutes: #topic Open discussion14:45
jlibosvaboden: do you want to give any updates :)14:45
*** yamamoto has quit IRC14:45
*** ALUVial has joined #openstack-meeting14:45
*** RuiChen has joined #openstack-meeting14:45
bodenMuch of the same as last week in neutron-lib. As armax mentioned last week we can likely start landing more lib patches this week and into next so I would encourge folks to take a peek at the reviews out there14:46
*** dimtruck is now known as zz_dimtruck14:46
*** zz_dimtruck is now known as dimtruck14:46
*** dmorita has quit IRC14:46
*** TheJulia has joined #openstack-meeting14:46
jlibosva#link https://review.openstack.org/#/q/project:openstack/neutron-lib+status:open14:46
*** bkopilov_ has quit IRC14:47
bodenI think we have 1 active neutron-lib impact patch.. give me 1 sec14:47
*** bkopilov has quit IRC14:47
*** Kevin_Zheng_ has joined #openstack-meeting14:47
*** ashtokolov has joined #openstack-meeting14:47
*** kristian__ has quit IRC14:47
*** fmccrthy has joined #openstack-meeting14:47
*** rsFF has joined #openstack-meeting14:48
*** dolphm has joined #openstack-meeting14:48
*** scottda has joined #openstack-meeting14:49
bodenThe 2 lib impact patches are listed on the neutron meeting wiki; although the patches need to be refreshed once merged they will impact consumers of the relevant functionality14:49
boden#link https://review.openstack.org/#/c/421562/  uses the providernet API definition from lib14:50
*** mfranc213 has joined #openstack-meeting14:50
*** sandanar has quit IRC14:50
boden#link https://review.openstack.org/#/c/422210/ uses the portbindings api def from neutron-lib14:50
*** rajivk__ has quit IRC14:50
jlibosva#link https://review.openstack.org/#/c/421562/ uses the providernet API definition from lib14:51
jlibosvaoh, the bot doesn't say anything? ok14:51
bodenfor more details, please see the neutron-lib section of the meeting wiki14:51
*** fnaval has quit IRC14:51
bodenand lastely, please don’t forget to add any relevant neutron-lib topics to the PTG etherpad14:51
bodenthat’s it from me14:51
*** ykatabam has quit IRC14:52
jlibosvaboden: ok, thanks14:52
*** eharney has joined #openstack-meeting14:52
jlibosva#topic Open discussion14:52
*** openstack changes topic to "Open discussion (Meeting topic: networking)"14:52
jlibosvawe have 8 minutes left14:52
ataraday_I've sent an email for openstack-dev about "Alternative approaches for L3 HA" and I'll happy to get some comments there :)14:52
*** briancline has quit IRC14:52
*** briancline has joined #openstack-meeting14:52
jlibosva#link http://lists.openstack.org/pipermail/openstack-dev/2017-February/111953.html14:53
*** rossella_s has quit IRC14:53
jlibosvaataraday_: thanks :) I put a link here14:53
ataraday_jlibosva, thanks :)14:53
*** rossella_s has joined #openstack-meeting14:53
*** ekuris__ has quit IRC14:53
jlibosvaataraday_: do you want to discuss it here? or ML is doing fine?14:53
ataraday_ML fine :)14:53
jlibosvacool14:54
*** ekuris__ has joined #openstack-meeting14:54
ataraday_just to bring some attention to it :)14:54
jlibosvaI'm sure people will read14:55
jlibosvaanybody else has anything to mention here? we have 5 minutes14:55
*** dimtruck is now known as zz_dimtruck14:55
amotokiI think we will skip the meeting next week14:56
jlibosvaI would just like mention here again that there is a Neutron CI meeting in an hour :) at this channel, please show up if you're interested in gate stability14:56
*** persia_ has joined #openstack-meeting14:56
jlibosvaamotoki: yeah, good point.14:56
ihrachysjlibosva: you go extra mile to advertise it, thanks :)))14:56
jlibosvakevinbenton: are you still here? I guess next week there won't be a meeting, right?14:56
*** shintaro has joined #openstack-meeting14:56
hichiharanext next meeting?14:56
kevinbentonjlibosva: yeah, i assume no meeting next week14:56
jlibosvakevinbenton: you assume? you're the boss now, you must be sure :)14:57
ihrachysfor the record, next is 28th then14:57
mlavallemaybe a message to the ML will be helpful14:57
kevinbentonjlibosva: yeah, no meeting14:57
*** vishnoianil has quit IRC14:57
jlibosva:]14:57
kevinbentonjlibosva: it would be too soon to provide feedback from PTG14:57
*** yamamoto has joined #openstack-meeting14:57
*** yamamoto has quit IRC14:57
jlibosvavery first hours of ptg vertical track, not bad maybe14:57
*** JayF has joined #openstack-meeting14:58
jlibosvaor horizontal maybe14:58
amotokikevinbenton: jlibosva: are you talking about the meeting of the week Feb 28th?14:58
*** Leo_ has joined #openstack-meeting14:58
jlibosvaamotoki: yeah, the next meeting will be 28th14:58
ihrachysyeah, it's confusing how kevinbenton mentioned feedback14:59
ihrachysunless it was a joke, that I struggle to distinguish that early14:59
kevinbentonihrachys: i was thinking if we had some sessions done already14:59
kevinbentonihrachys: we could provide some info for remote folks14:59
ihrachysit will be just a start, and only cross project14:59
jlibosvaah, I got it as a joke14:59
amotoki:)14:59
ihrachysso indeed next 28th I assume then14:59
jlibosvaok, we're out of time15:00
*** Akis_ has joined #openstack-meeting15:00
jlibosvathanks for showing up :)15:00
dasmo/15:00
jlibosva#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
mlavalleo/15:00
openstackMeeting ended Tue Feb 14 15:00:09 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2017/networking.2017-02-14-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2017/networking.2017-02-14-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2017/networking.2017-02-14-14.00.log.html15:00
dasanindThanks15:00
*** john-davidge has left #openstack-meeting15:00
sindhuthanks15:00
*** electrocucaracha has left #openstack-meeting15:00
ralonsohhello15:00
*** hichihara has quit IRC15:00
ralonsoh#startmeeting neutron_qos15:00
openstackMeeting started Tue Feb 14 15:00:57 2017 UTC and is due to finish in 60 minutes.  The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_qos)"15:01
openstackThe meeting name has been set to 'neutron_qos'15:01
*** med_` is now known as medberry15:01
*** medberry has quit IRC15:01
*** medberry has joined #openstack-meeting15:01
*** anilvenkata has quit IRC15:01
davidshaHi15:01
ralonsohHappy Valentines day15:01
davidshaStop you'll make me blush ~15:01
*** medberry is now known as med_15:01
ralonsohslaweq won't attend today15:01
davidshakk15:01
ralonsohhe will review the logs15:01
ralonsohajo?15:01
ralonsohreedip?15:01
*** haleyb_ has joined #openstack-meeting15:02
ralonsohlet's wait one minute15:02
davidshacan we remove that last interaction? he doesn't need to see that....15:02
*** dmorita has joined #openstack-meeting15:02
davidshakk15:02
ajohey sorry ralonsoh , I'm back15:02
*** hoangcx_ has quit IRC15:03
ralonsohnp15:03
davidshaHi15:03
ralonsohlet's start15:03
ralonsoh#topic RFEs15:03
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:03
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/165708915:03
openstackLaunchpad bug 1657089 in neutron "[RFE]Add bandwidth_limit to vip" [Undecided,New]15:03
ajoI need to leave around half past the hour, but I'll be around 'till then15:03
ralonsohno problem15:03
*** Akis__ has quit IRC15:03
ralonsohok, I'll take a look to this RFE15:03
*** anilvenkata has joined #openstack-meeting15:04
ralonsohBut I'll ask for more information15:04
ajowell15:04
ajoabout that one15:04
ajowe need something that fits the current model15:04
ajolike assigning policies to routers, etc15:04
ralonsohthat's right15:04
*** janzian has left #openstack-meeting15:04
ralonsohwe have tu bugs related15:04
ralonsohmybe15:04
reedip_Hi15:04
ajowe could explore the posibilities of that15:05
ajoor assigning policies to vips15:05
ajoyes15:05
ajothere's a related bug right15:05
ralonsohone sec15:05
ralonsoh#link https://review.openstack.org/#/c/425218/15:05
ralonsohAnd15:05
ralonsoh#link https://review.openstack.org/#/c/428304/15:05
ralonsohIf you can take a look at those ones15:06
ralonsohperfect15:06
*** dmorita has quit IRC15:06
*** VW has joined #openstack-meeting15:06
* ajo looks15:06
*** jlibosva has left #openstack-meeting15:07
ralonsohmaybe we can talk about this bug in etherpad15:07
ajoabout the default one,15:07
*** fnaval has joined #openstack-meeting15:08
ajomakes sense, but I would like something that would allow administrators to stick policies to projects15:08
ajonot only projects to themselves,15:08
ajobut the admin15:08
ajothat makes a lot of sense for bandwidth allocation, etc15:09
ajobut that'd require another API rest call to create those kind of associations15:09
ajothe same thing would be useful for self-tenant assignment15:09
ajofor example15:09
ajoneutron qos-default-policy bandwidth-limit-10M15:09
ajoor, as admin15:09
ajoneutron qos-default-policy bandwidth-limit-10M --to-tenant <uuid_of_tenant>. (or project)15:09
ralonsohok15:10
ajothe "default" flag is more limited15:10
ralonsohthis will be another patch15:10
ralonsohok15:10
ralonsohI'll change the implementation15:10
ajothanks for taking on this ralonsoh15:10
ralonsohnp15:10
ralonsohnext one15:10
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/163479815:10
openstackLaunchpad bug 1634798 in neutron "[RFE] Qos DSCP to vlan priority mapping" [Wishlist,Confirmed]15:10
ajoI suspect slaweq would agree, knowing their use cases at OVH15:10
ralonsohyes, I think so15:11
*** martines has quit IRC15:11
ralonsohDo you think this rfe is feasible?15:11
ralonsohdavidsha?15:12
ajoIt's probably feasible, but I believe we have things with higher priority right now15:12
ralonsohok15:12
*** annp has quit IRC15:12
ralonsohso let's keep it in the backlog15:12
ralonsohnext one15:12
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/150562715:12
openstackLaunchpad bug 1505627 in neutron "[RFE] QoS Explicit Congestion Notification (ECN) Support" [Wishlist,Incomplete] - Assigned to Reedip (reedip-banerjee)15:12
davidshaI agress with ajo15:12
ralonsohreedip?15:12
reedip_M driving, can we take.this later if possible?15:13
davidshaagree*15:13
ajoreedip any update on the questions of the etherpad?15:13
ajoack15:13
ralonsohok15:13
ralonsohnext one15:13
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/163922015:13
openstackLaunchpad bug 1639220 in neutron "[RFE] Introduce Network QoS policy "is_default" behaviour" [Low,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:13
reedip_ajo: none afternthe last meeting, will look at it today15:13
ralonsohok, that's mine15:13
*** Leo_ has quit IRC15:13
ralonsohand we have already talk about this one15:14
ralonsohno more rfe's15:14
mlavalleI have a question15:14
ralonsohany other comment?15:14
*** Leo_ has joined #openstack-meeting15:14
ralonsohplease15:14
*** liangy has joined #openstack-meeting15:14
mlavalleare we going to implement https://review.openstack.org/#/c/396297/ during Pike?15:14
*** yamahata has joined #openstack-meeting15:15
ralonsohoh yes! I don't know why I didn't appear in the query...15:15
*** bkopilov has joined #openstack-meeting15:15
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/157898915:15
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:15
*** bkopilov_ has joined #openstack-meeting15:15
*** hongbin has joined #openstack-meeting15:16
ralonsohI made a POC: https://review.openstack.org/#/c/401254/15:16
*** haleyb_ has quit IRC15:16
ralonsohreading the BW15:16
ralonsohare we going to talk about this RFE in the PTG?15:17
ralonsohthere are several parts involved15:17
ajoWe have no oficial timeslot, but we can, of course make a small table :)15:17
ralonsohthat will be perfect15:17
ajoyes :)15:17
mlavalleIn the spec I volunteered to implement the placement api interaction pieces15:17
mlavalleso I want to make sure we are moving ahead with this because I want to honot my commitments15:18
*** iyamahat has joined #openstack-meeting15:18
mlavallehonor^^^15:18
ajoralonsoh reading the commit message: you don't need to count down the bandwidth15:18
*** priteau has quit IRC15:18
ajothat's handled by nova when doing allocations, etc.15:18
ajoit can be nice for informative reasons, I guess, but we don't need to use it15:19
ajoI mean, we don't need to update nova when there's more "min bw" used. Nova will be aware, and will have the bandwidth counted down15:19
*** iceyao has quit IRC15:19
*** emagana has joined #openstack-meeting15:19
ralonsohok, buy I have some concerns about this15:19
ralonsohplease, make an small review and I'll reply15:19
ajoack15:20
ralonsohthanks!15:20
ralonsohmlavalle: will you assist to the PTG?15:20
mlavalleralonsoh: yeah I'll be there15:21
ralonsohperfect, so during the PTG we'll talk about this rfe15:21
ralonsohlet's move to bugs15:21
ralonsoh#topic Bugs15:21
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:21
ralonsohhttps://bugs.launchpad.net/neutron/+bug/166390815:22
openstackLaunchpad bug 1663908 in neutron "Qos rules not cleaned by L2 agent" [Undecided,New]15:22
ralonsohI need to reproduce this bug to be sure15:22
ralonsohI can take this one15:22
davidshaYou have a lot on your plate I can take it.15:22
ralonsohperfect, we'll share the work load15:23
ralonsohnext one15:23
ralonsohhttps://bugs.launchpad.net/neutron/+bug/166210915:23
openstackLaunchpad bug 1662109 in neutron "tempest scenario test_qos fails intermittently" [High,In progress] - Assigned to Miguel Angel Ajo (mangelajo)15:23
ralonsohajo ?15:23
ajoOh, we merged one patch regarding that15:23
ajolet me check what's the status15:23
ralonsohperfect!15:23
ajooh, it didn't merge due to gate unstability15:24
ralonsohok, but the patch is there15:24
ralonsohnext one15:25
ralonsohhttps://bugs.launchpad.net/neutron/+bug/165931215:25
openstackLaunchpad bug 1659312 in neutron "Enforce QoS policies applied on router interfaces" [Wishlist,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:25
ralonsohI'll ping kevinbenton to review this one15:25
ralonsohhe kindly ask me to open this one15:25
ralonsohand this one (related)15:26
ralonsohhttps://bugs.launchpad.net/neutron/+bug/165926515:26
openstackLaunchpad bug 1659265 in neutron "Network level QoS policies should apply to network:router_gateway" [Wishlist,In progress] - Assigned to Maxime (maxime-guyot-p)15:26
*** adiantum1 has joined #openstack-meeting15:26
ralonsohI you have time, reviews will be welcome15:26
*** mtanino has joined #openstack-meeting15:26
*** annegentle has joined #openstack-meeting15:26
ralonsohnext one15:26
ralonsohhttps://bugs.launchpad.net/neutron/+bug/165738115:26
openstackLaunchpad bug 1657381 in neutron "QoS drivers need to implement a precommit for the actions" [Medium,Incomplete]15:26
*** zz_dimtruck is now known as dimtruck15:27
ralonsohajo ?15:27
ralonsohyou stopped this patch15:27
ajoI was waiting on answer to my quetions15:27
ajosuddenly I realized that if we don't allow anyone to stop the transaction due to an error in the driver15:27
ajoit becomes pointless15:27
ralonsohyes, I see15:28
ajobecause 1) drivers can't stop the transaction because they don't support a rule15:28
*** emagana has quit IRC15:28
*** gongysh has quit IRC15:28
ajo2) if the backend had an issue it should be logged and retried later15:28
*** armax has joined #openstack-meeting15:28
*** adiantum has quit IRC15:28
*** adiantum1 is now known as adiantum15:28
ajoat worst, the normal action of the driver can be used to throw such excetion15:28
*** ekuris__ has quit IRC15:28
ajoexception15:28
ralonsohas you said, it becomes pointless15:28
ajoso15:28
ajoI asked on patch for more details on the need of such precommit action15:29
ralonsohok, so no action for now until feedback15:29
*** boden has left #openstack-meeting15:29
ralonsohnext one15:29
ralonsohhttps://bugs.launchpad.net/neutron/+bug/164951715:29
openstackLaunchpad bug 1649517 in neutron "qos policy attached to network, qos_policy_id is reflecting on neutron net-show , but not on the port with neutron port-show" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq)15:29
*** donghao has quit IRC15:29
ralonsohI'll ping slaweq a bit latter about this bug15:29
ralonsohit seems to be stopped15:30
ajoI have to leave for now, thanks ralonsoh for driving the meeting, I'll read the logs later15:30
ralonsohno problem15:30
ralonsohsee you later15:30
ralonsohnext one15:31
ralonsohhttps://bugs.launchpad.net/neutron/+bug/164950315:31
openstackLaunchpad bug 1649503 in neutron "Mechanism driver can't be notified with updated network" [High,In progress] - Assigned to Hong Hui Xiao (xiaohhui)15:31
ralonsohI'll ping Hong for feedback, beause seems to be stopped too15:31
*** mriedem1 has joined #openstack-meeting15:31
*** nadya has quit IRC15:32
ralonsohok, no more bugs in the agenda15:32
*** tommylikehu_ has quit IRC15:32
*** diablo_rojo has joined #openstack-meeting15:32
ralonsohanyone has any other bug?15:32
ralonsohok15:32
ralonsoh#topic Other Changes15:32
*** openstack changes topic to "Other Changes (Meeting topic: neutron_qos)"15:32
ralonsohnothing in the agenda15:33
*** mriedem has quit IRC15:33
ralonsohlast topic15:33
ralonsoh#topic Open Discussion15:33
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:33
ralonsohnext week PTG15:34
ralonsohI hope will have time enough to finish all open topics15:34
*** dmorita has joined #openstack-meeting15:34
*** donghao has joined #openstack-meeting15:34
ralonsohdavidsha, mlavalle: anything else?15:35
*** mriedem1 is now known as mriedem15:35
davidsha+1, I'd like to discuss the flow manager and neutron-classifier at it.15:35
ralonsohyes, sure!15:35
*** dtrainor_ has joined #openstack-meeting15:36
ralonsohde you have a POC of the classifier?15:36
ralonsohwith OVS15:36
*** dtrainor has quit IRC15:37
davidshaI'm working on writing a service plugin for neutron-classifier at the moment, I'm hoping to have something to show and get opinions on by next week.15:37
ralonsohthat's perfect15:37
*** funzo has joined #openstack-meeting15:37
*** toscalix has quit IRC15:37
ralonsohok, let's end the meeting15:37
ralonsohthank you all!15:37
davidshaThanks!15:37
ralonsoh#endmeeting15:38
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:38
openstackMeeting ended Tue Feb 14 15:38:03 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-02-14-15.00.html15:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-02-14-15.00.txt15:38
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-02-14-15.00.log.html15:38
*** donghao has quit IRC15:39
*** dmorita has quit IRC15:39
*** unicell has joined #openstack-meeting15:41
*** unicell1 has quit IRC15:41
*** liangy has quit IRC15:42
*** zhhuabj has quit IRC15:42
*** dtrainor_ has quit IRC15:42
*** matrohon has quit IRC15:44
*** anilvenkata has quit IRC15:45
*** caboucha has joined #openstack-meeting15:45
*** zhhuabj has joined #openstack-meeting15:46
*** liangy has joined #openstack-meeting15:47
*** links has quit IRC15:47
*** reedip_1 has joined #openstack-meeting15:49
*** dtrainor has joined #openstack-meeting15:49
*** dmorita has joined #openstack-meeting15:50
*** hieulq_ has joined #openstack-meeting15:52
*** jlibosva has joined #openstack-meeting15:54
*** dmorita has quit IRC15:54
*** zhhuabj has quit IRC15:55
*** kevinz has quit IRC15:55
*** kristian__ has joined #openstack-meeting15:56
*** boden has joined #openstack-meeting15:56
*** jdurgin1 has joined #openstack-meeting15:56
*** mriedem has quit IRC15:57
*** yamamoto has joined #openstack-meeting15:58
*** matrohon has joined #openstack-meeting15:58
*** jtomasek has quit IRC15:59
*** korzen has quit IRC15:59
*** shintaro has quit IRC15:59
*** ataraday_ has quit IRC15:59
*** ataraday_ has joined #openstack-meeting15:59
*** mriedem has joined #openstack-meeting15:59
*** trevormc has joined #openstack-meeting16:00
ihrachys#startmeeting neutron_ci16:01
openstackMeeting started Tue Feb 14 16:01:16 2017 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:01
openstackThe meeting name has been set to 'neutron_ci'16:01
ihrachyshello everyone :)16:01
jlibosvao/16:01
manjeetshi16:01
kevinbentonhi16:01
reedip_1o/16:01
dasmo/16:02
ihrachys#link https://wiki.openstack.org/wiki/Meetings/NeutronCI Agenda16:02
ihrachys(or lack of it, I need to write up some stub topics)16:02
ihrachyslet's start with action items from the previous meeting16:02
ihrachys#topic Action items from previous meeting16:02
*** openstack changes topic to "Action items from previous meeting (Meeting topic: neutron_ci)"16:02
ihrachys"ihrachys to follow up with armax on periodic functional job not showing up in grafana"16:03
ihrachysso indeed the periodic functional does not show up in http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=7&fullscreen16:03
ihrachysBUT16:03
*** zhhuabj has joined #openstack-meeting16:03
ihrachyswe can see runs in http://logs.openstack.org/periodic/periodic-neutron-dsvm-functional-ubuntu-xenial/16:03
*** ricardo2 has joined #openstack-meeting16:03
*** erlon has joined #openstack-meeting16:03
ihrachysand armax suggested that it does not show up because of a glitch in grafana that makes it impossible to draw a trend while results are identical16:04
ihrachysso we believe that till it fails, it won't be in the grafana16:04
jlibosvait's also on openstack-health http://status.openstack.org/openstack-health/#/job/periodic-neutron-dsvm-functional-ubuntu-xenial16:04
ihrachysthat's actually interesting that it hasn't failed in 15 runs16:04
ihrachysjlibosva: oh thanks for the link!16:05
*** yamamoto has quit IRC16:05
ihrachyswe saw failure rate in check queue at 30% to 40% before, so even though today it's 10%, the chance of not hitting it once in 15 runs in the past is quite low16:05
ihrachysso either we are lucky, or there is some other thing in play (maybe we allocate different VMs for periodic?)16:06
ihrachysso far, we are going to monitor, and maybe in a week we will have a failure; if not, we will look closer at job definitions.16:06
ihrachysok next action was: "ihrachys to look at e-r bot for openstack-neutron channel"16:07
ihrachysthat's actually something to decide first if we even want it16:07
ihrachysI noticed some other projects like nova or glance have a irc bot that reports into their channels on captured classified failures16:07
ihrachysI was thinking, it may help to give us some better understanding of what hits our gates16:08
kevinbentoni vote +1 for that16:08
ihrachysso far I proposed a patch that enables the bot at https://review.openstack.org/#/c/433735/16:08
*** unicell has quit IRC16:08
*** donghao has joined #openstack-meeting16:08
jlibosva+1 from me too. If it will become annoying or un-useful, we can disable it anytime16:08
ihrachysI guess we can enable it and see how it goes; if it spams too much, we tweak or disable it later16:08
manjeets+116:08
ihrachysok and I see mtreinish comment that it's wrong place to do it; I will update the right one after the meeting16:09
ihrachysas long as we agree on the direction, which I believe we do :)16:09
*** nkrinner is now known as nkrinner_afk16:09
dasmihrachys: how does it look on channel? irc bot shows url? do you have example of that?16:09
dasmi'm ok with enabling it, just asking to know what'll be changed16:10
kevinbentonevery 2 seconds it will report if we have any failures :)16:11
*** rcernin has quit IRC16:11
dasmkevinbenton: ++ :)16:11
ihrachyslike in http://eavesdrop.openstack.org/irclogs/%23openstack-qa/%23openstack-qa.2017-01-16.log.html#t2017-01-16T03:12:5416:11
ihrachysthough if it knows the error, it will report the bug and all16:12
dasmihrachys: ack16:12
*** donghao has quit IRC16:12
ihrachysok, that's an example of bug recognized: http://eavesdrop.openstack.org/irclogs/%23openstack-qa/%23openstack-qa.2017-01-08.log.html#t2017-01-08T00:13:5316:12
ihrachysI guess we won't know if it's useful until we try16:13
*** nkrinner_afk is now known as nkrinner16:13
manjeetsi have a question what if patch is culprit over the failure of job will it still report ?16:13
dasmihrachys: btw "recognized bugs". if i recall correctly, we have to manually categorize recognized bugs. is it true?16:13
manjeetsor there is a way to filter out16:13
ihrachysmanjeets: it probably reports on gate jobs only16:13
ihrachysthat would be my expectation16:13
dasmi think, electrocucaracha did something like that for couple bugs16:13
mtreinishihrachys: do you want to have it report uncategorized failures too? Your patch didn't have that16:13
ihrachysmtreinish: yeah, could be; I haven't spent much time thinking on it yet, just sent a strawman to have it for discussion16:14
*** adiantum has quit IRC16:14
ihrachysmtreinish: while we have you here, could you confirm it monitors gate queue only?16:14
mtreinishthe irc reporting?16:15
*** galstrom_zzz is now known as galstrom16:15
ihrachysyea16:15
ihrachysotherwise it would spam with irrelevant messages16:15
mtreinishyeah it doesn't report to irc for check iirc16:15
*** nkrinner is now known as nkrinner_afk16:16
mtreinishbut it's been a while since I looked at the code/config16:16
ihrachysthat makes sense16:16
ihrachysmtreinish: is the bot useful for qa team?16:16
ihrachysdo you find it helps, or just spams with low actual profit?16:17
*** shintaro has joined #openstack-meeting16:17
mtreinishso in the past it was quite useful, especially when we first started e-r16:17
mtreinishbut nowadays I don't think many people pay attention to it16:18
mtreinishif you've got people who are willing to stay on top of it I think it'll be useful16:18
ihrachysaye; we were looking for ways to direct attention to elastic-recheck tooling lately, and I am hopeful it will give proper signals16:18
ihrachysok next action item was: "manjeets to produce a gerrit dashboard for gate and functional failures"16:19
manjeetshttps://github.com/manjeetbhatia/neutron_stuff/blob/master/create_gate_failure_dash.py16:19
manjeetsthis can be used to create fresh one all the time16:19
*** amotoki has quit IRC16:19
ihrachysmanjeets: do you have link to the resulting dashboard handy?16:19
*** fzdarsky|afk is now known as fzdarsky16:19
ihrachysuse url shortener please16:19
manjeetshttps://github.com/manjeetbhatia/neutron_stuff/blob/master/README.md16:20
manjeetsihrachys, ok yes there is only one patch from 14 tickets in progress atm16:20
*** tovin07 has quit IRC16:20
manjeetswhich it captured16:20
jlibosvamanjeets++16:21
ihrachysis it because the dashboard doesn't capture some, or that's indeed all we have?16:21
jlibosvagood stuff16:21
kevinbentonmtreinish: can we alter the bot to direct messages at whoever is currently talking in the channel? :)16:21
manjeetsI manually checked some of them are abandoned16:21
manjeetsonly one patch is open ihrachys16:21
mtreinishkevinbenton: heh, it wouldn't be that hard. All the info is there to add that "feature" :)16:22
reedip_1manjeets +116:22
ihrachyskevinbenton: haha. we should also make it customize the message depending on the rate of failure reports. sometimes it asks politely, sometimes 'everyone just shut up and fix the damned gate'16:22
dasmkevinbenton: are you planning to silence irc channel? :)16:22
*** number80 has quit IRC16:23
ihrachysmanjeets: thanks a lot for the work. do you plan to contribute the script to some official repo? like we did for milestone target dashboard.16:23
manjeetsihrachys, some stuff is hardcoded I'll send this script to neutron/tools once i fix those16:24
*** shintaro has quit IRC16:24
ihrachysaye. we then can hook it into infra so that it shows up at http://status.openstack.org/reviews/16:24
ihrachys#action manjeets to polish the dashboard script and propose it for neutron/tools/16:25
manjeetsyes we can do that16:25
*** baoli has quit IRC16:25
ihrachysok next item is "jlibosva to follow up on scenario failures"16:25
*** shintaro has joined #openstack-meeting16:25
ihrachysjlibosva: your stage. how does scenario job feel today?16:25
jlibosvaunfortunately no fixes were merged16:26
jlibosvawe have one for qos that's been failing a lot16:26
* jlibosva looks for link16:26
*** shintaro has quit IRC16:26
*** david-lyle has joined #openstack-meeting16:26
jlibosvahttps://review.openstack.org/#/c/430309/ - it's already approved but failing on gate16:26
*** ricardo2 has quit IRC16:26
jlibosvaanother patch is to increase debugability - https://review.openstack.org/#/c/427312/ - there is a sporadic failure where tempest is unable to ssh to the instance16:27
jlibosvaI suspect that that's due to slow hypervisors, I compared locally boottime of my machine and the one on gate and gate is ~14x slower16:28
jlibosvagiven that it runs with ubuntu that starts a lot of services, our tempest conf might just have insufficient timeout16:28
jlibosvabut it's hard to tell without getting instance boot console output16:28
ihrachysyeah, overall I noticed job timeouts in gate lately, but we will cover it a bit later16:29
jlibosvaI think those are two major issues, I haven't seen anything else16:29
*** david-lyle_ has quit IRC16:29
jlibosvaihrachys: yeah, that made me just think that maybe some infra changed. But that's for a separate discussion16:29
*** vi01et03 has joined #openstack-meeting16:29
ihrachysjlibosva: generally speaking, what's the strategy for scenario job assuming we solve the remaining stability issues? do we have a plan to make it vote?16:29
jlibosvaihrachys: no formal plan but I'd like to make it voting once it reaches some reasonable failure rate16:29
*** matrohon has quit IRC16:30
mlavallejlibosva: what's reasonable?16:30
jlibosvawe'll see after we get those two patches in and eventually increase timeout (which are already 2 times higher than with cirros IIRC)16:30
jlibosvamlavalle: optimistic guess - 10-15%16:30
*** bobh has joined #openstack-meeting16:31
clarkbjlibosva: qemu is slow yes16:31
clarkbthats normal and expected16:31
clarkb(and why cirros is used most places)16:31
jlibosvacurrently we have BUILD_TIMEOUT=392 for Ubuntu16:32
ihrachysjlibosva: if we have mutiple tests running in parallel starting instances on low memory machines, then maybe reduce number of test workers? that should give better per-test timing?16:32
*** number80 has joined #openstack-meeting16:32
*** guyr-infinidat has joined #openstack-meeting16:33
jlibosvaihrachys: that's a good idea. Given that amount of tests is very low. I'll try to send a patch for that16:33
ihrachys#action jlibosva to try reducing parallelization for scenario tests16:33
jlibosvaat least to get some additional info whether that helps16:33
ihrachyswe gotta have a plan to make it vote, otherwise it will be another fullstack job that we break once in a while16:34
ihrachysit also makes sense to plan for what we do with two flavors of the job we have - ovs and linuxbridge; but that's probably a discussion for another venue. ptg?16:35
ihrachysok, last action item was "ihrachys to read about how swappiness is supposed to work, and why it doesn't in gate"16:35
ihrachysI haven't found much; the only thing I noticed is that we use =30 in devstack while default is claimed to be 60 by several sources. my understanding is that we set it to =10 before just because some kernels were completely disabling it (=0)16:36
*** dmorita has joined #openstack-meeting16:36
ihrachysthat being said, the previous attempt to raise from =10 to =30 didn't help too much, we still hit oom-killer with swap free16:36
*** jprovazn has joined #openstack-meeting16:37
*** Akis_ has quit IRC16:37
*** Julien-zte has quit IRC16:37
*** ygbo has joined #openstack-meeting16:37
ihrachysso another thing that came to my mind is that a process (mysqld, qemu?) could block memory from swapping (there is a syscall for that)16:37
*** Julien-zte has joined #openstack-meeting16:37
ihrachysand afaik we lack info on those memory segments in current logs collected16:37
ihrachysso I am going to look at how we could dump that16:37
*** Julien-zte has quit IRC16:37
dasmihrachys: do you maybe have any links about swappiness to share?16:38
*** Julien-zte has joined #openstack-meeting16:38
ihrachys#action ihrachys to look at getting more info from kernel about ram-locked memory segments16:38
ihrachysdasm: there are some you can find by mere googling. afaik there is no official doc, just blog posts and stackoverflow and such16:38
*** Julien-zte has quit IRC16:38
dasmihrachys: ack16:38
*** Julien-zte has joined #openstack-meeting16:39
ihrachysok and we are done with action items, woohoo16:39
clarkbihrachys: yes mlock and friends. Also apparently kernel allocations aren't swappable16:39
*** Julien-zte has quit IRC16:39
*** Julien-zte has joined #openstack-meeting16:40
*** Julien-zte has quit IRC16:40
ihrachysnow, let's discuss current gate issues as we know them16:40
*** zhangshuai has quit IRC16:40
ihrachys#topic Gate issues16:40
*** openstack changes topic to "Gate issues (Meeting topic: neutron_ci)"16:40
*** dmorita has quit IRC16:40
*** Julien-zte has joined #openstack-meeting16:41
*** Julien-zte has quit IRC16:41
ihrachys#link https://goo.gl/8vigPl Open bugs16:41
ihrachysthe bug that was the most affecting in the past is at the top of the list16:41
ihrachys#link https://bugs.launchpad.net/neutron/+bug/1627106 ovsdb native timeouts16:42
openstackLaunchpad bug 1627106 in neutron "TimeoutException while executing tests adding bridge using OVSDB native" [Critical,In progress] - Assigned to Miguel Angel Ajo (mangelajo)16:42
*** electrocucaracha has joined #openstack-meeting16:42
ihrachysotherwiseguy: kevinbenton: what's the latest status there? I see the patch was in gate but now bumped off?16:42
jlibosvaotherwiseguy has a related patch for it pushed recently16:42
jlibosvahttps://review.openstack.org/#/c/429095/16:42
ihrachysyeah that's the patch I meant16:43
otherwiseguyihrachys, It looked like another patch started using a function that I hadn't updated because we didn't use it.16:43
*** ashcrack has joined #openstack-meeting16:43
otherwiseguyNew update modifies that function to get rid of the verify() call where we can. Can't remove it when calling "add" on a map column, but don't think we do that.16:43
ihrachysotherwiseguy: ok, other than that, do we have stability issues with that? I think that's what resulted in bumping off the gate in the past.16:44
*** whenry has joined #openstack-meeting16:44
*** diga has quit IRC16:44
*** akiskourtis has joined #openstack-meeting16:44
otherwiseguyihrachys, I can only say "we'll see". Does "Bumped off the gate mean setting it WIP" or does it require something else?16:45
ihrachyswell I don't think it's necessarily WIP, but I assume armax wanted to collect more stats on its success.16:45
*** Akis_ has joined #openstack-meeting16:45
otherwiseguyBecause I set it WIP to add the change I just mentioned.16:45
ihrachysafaik the bump was triggered by general gate instability, so we don't really know if it's because of this patch16:45
otherwiseguyNot necessarily because of any stability.16:46
ihrachysotherwiseguy: ok, I guess then we just wait for the new version, recheck a bunch of times again, and see if we can get it in16:46
otherwiseguyissues16:46
ihrachysotherwiseguy: thanks for working on it16:46
otherwiseguyBut if things magically got better after removing it from the gate, then that would scare me a bit.16:47
*** nadya has joined #openstack-meeting16:47
ihrachysotherwiseguy: no, it's not that, it's just armax was not sure if it helps if we need to recheck so much16:47
ihrachysto pass it in16:47
ihrachysI believe it's just a matter of caution, we don't want to introduce another vector of instability16:48
otherwiseguyWe didn't need to recheck it so much, I was just rechecking a bunch to see if there were any timeout errors.16:48
otherwiseguyThere were failures occasionally, but none I could definitely match to the patch.16:48
*** FengShengqin1 has quit IRC16:48
*** FengShengqin1 has joined #openstack-meeting16:48
*** rcernin has joined #openstack-meeting16:49
ihrachysok, let's move on. another issue that affects our gates lately is tempest job timeouts due to slow machine run.16:49
*** akiskourtis has quit IRC16:49
*** jmckind has quit IRC16:49
ihrachysthat one is a bit tricky, and doesn't really seem neutron specific16:49
ihrachysI started discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-February/111923.html16:49
ihrachysbut tl;dr is it seems sometimes machines we run tests on are very slow16:50
ihrachyslike 2-3 times slower than usual16:50
ihrachyswhich makes zuul abrupt runs in the middle16:50
ihrachysafter 2h16:50
ihrachysso there is a bit of discussion inside the thread, you may want to have a look16:50
ihrachysI don't think at this point we know the next steps to take on that one16:50
mlavalledo you mean zuul abruptly ends the runs?16:50
ihrachysit's also of concern that timeouts were not happening as often before16:50
ihrachysmlavalle: well it's devstack itself I believe, it sets some timeout traps and kill tempest16:51
mlavalleyeah, I see that quite often in patchses I review. Just making sure we were talking about the same thing :-)16:52
dasmare we still seeing timeouts? i've seen infra info about storage problems (which i believe should be fixed already).16:52
dasmmaybe both are unrelated16:52
clarkbdasm: that should be unrelated16:52
dasmclarkb: ack16:52
clarkbdasm: storage problems affected centos7 package installs as we had a bad centos7 mirror index16:52
ihrachysI was thinking that timeouts are happening lately, and we touched swappiness lately too [also number of rpc workers but armax claims it could affect test times], so I was thinking, maybe we somehow pushed the failing jobs to the edge some more so as to trigger timeouts on slower machines.16:52
clarkb(but that should fail fast)16:52
*** liangy has quit IRC16:52
dasmihrachys: are you suggesting reverting swappiness and verifying timeouts?16:53
*** jmckind has joined #openstack-meeting16:54
dasms/verifying/checking16:54
ihrachysI don't suggest touching anything just yet, I am just thinking aloud of what could make those timeouts triggered16:54
ihrachysnote it can be as well external to openstack, but we can't help that, so it's better to focus for what we can do16:54
*** rossella_s has quit IRC16:55
ihrachysdasm: also note that it's not like all jobs timeout; most of them pass successfully, and in time that is a lot lower than 2h16:55
ihrachysgood runs are usually ~1h 10-20 mins16:55
ihrachyssometimes even less than an hour16:55
*** michael_bredel has joined #openstack-meeting16:55
ihrachysso I suspect machines in different clouds are not uniform16:55
dasmhmm.. maybe correlation between infrastructure? we should probably look at this16:56
dasmi can try to verify if it's somehow related and if we're seeing timeouts just for specific clouds16:56
*** Alex_Staf has quit IRC16:56
ihrachysit may be just that for those slow machines we have, we may have gotten the time pushed a bit beyond the limit16:56
ihrachysof note, there does not seem to be correlation with cloud used, or project.16:56
dasmhmm16:57
ihrachysI am gonna dump cpu flags in devstack to see if there is a difference between what's available for the machines16:57
ihrachys#action ihrachys to dump cpu flags in devstack gate16:57
ihrachysapart from that, I am out of ideas on next steps; if someone has, please speak up in the email thread.16:58
ihrachysoh 2 mins left; and before we complete the meeting, I want to mention several patches we landed lately.16:58
ihrachysone is removing requests dependency that somewhat reduces memory usage for l3 agent: https://review.openstack.org/#/c/432367/16:58
ihrachysthen we also enabled dstat service in functional gate: https://review.openstack.org/427358 so now next time we spot a timeout in ovsdb native we can check the load of the system at that point.16:59
ihrachysI don't expect it to give a definite answer, but who knows, at least there is chance16:59
ihrachysthere is also a patch up for review to fix cleanup for floating ips in some api tests: https://review.openstack.org/43271317:00
jlibosvaI have a patch for fullstack -17:00
ihrachysok we are at the top of the hour17:00
jlibosvaI wanted to raise here17:00
*** sdake has joined #openstack-meeting17:00
ihrachysjlibosva: shoot quick17:00
jlibosvahttps://review.openstack.org/#/c/433157/17:00
*** jkilpatr_ has joined #openstack-meeting17:00
jlibosvadidn't report a bug as I was hitting it locally17:00
ihrachysack. let's follow up in the project channel17:01
jlibosvaand was lazy to search logstash :) but I can do that if it's eneded17:01
ihrachysthanks everyone17:01
jlibosvathanks!17:01
dasmo/17:01
ihrachys#endmeeting17:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:01
manjeetsthanks17:01
openstackMeeting ended Tue Feb 14 17:01:13 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-02-14-16.01.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-02-14-16.01.txt17:01
mlavalleo/17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-02-14-16.01.log.html17:01
igordcard#startmeeting network_common_flow_classifier17:01
openstackMeeting started Tue Feb 14 17:01:22 2017 UTC and is due to finish in 60 minutes.  The chair is igordcard. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: network_common_flow_classifier)"17:01
*** electrocucaracha has left #openstack-meeting17:01
openstackThe meeting name has been set to 'network_common_flow_classifier'17:01
*** mlavalle has left #openstack-meeting17:01
*** trevormc has left #openstack-meeting17:01
*** manjeets has left #openstack-meeting17:01
igordcardhi davidsha, all17:01
*** jlibosva has left #openstack-meeting17:01
*** sdake_ has quit IRC17:02
davidshaHi17:02
igordcardlet's go straight into the agenda17:02
igordcard#link https://wiki.openstack.org/wiki/Neutron/CommonFlowClassifier#Discussion_Topic_14_February_201717:02
igordcard#topic Approach A - PoC status17:02
*** openstack changes topic to "Approach A - PoC status (Meeting topic: network_common_flow_classifier)"17:02
*** michael_bredel has quit IRC17:02
*** jkilpatr has quit IRC17:02
*** michael_bredel has joined #openstack-meeting17:03
igordcarddavidsha you've been working on an initial PoC for the ccf17:03
igordcarddavidsha: what's the status?17:03
davidshaYa, at the moment I've the service plugin working and I'm working on the resources and database models,17:04
igordcarddavidsha: is the service plugin exposing an API?17:05
davidshaI've defined a resource for ipv4, ipv6, ethernet, tcp, udp and neutron ports/subnets and networks17:05
*** sdake has quit IRC17:05
davidshaigordcard: yes, to the previously mentioned resources17:05
*** hieulq_ has quit IRC17:05
davidshaAt the moment I'm only testing on ipv4 though.17:05
igordcardgreat, those are a nice set of classification types to start with17:05
*** ygbo has quit IRC17:05
*** andreas_s has quit IRC17:05
igordcardfor the neutron resources, is that a single type or three different types?17:06
davidshaA single type17:06
davidshabut you can specify source and destination too17:06
igordcardcool17:07
igordcardare you publishing the "initial commit" before the ptg?17:07
*** dmorita has joined #openstack-meeting17:08
*** sdake has joined #openstack-meeting17:08
davidshaI'm hoping to17:08
*** boden has left #openstack-meeting17:08
igordcarddavidsha: alright17:08
*** martines has joined #openstack-meeting17:08
davidshaI should for just IPV4, It would need more time for the classification groupings and other classifications that had been discussed.17:09
igordcardare you looking at any neutron project to demo the consumption of classification resources from the ccf?17:09
*** sridharg has quit IRC17:09
igordcarddavidsha: sounds good.. I would say a subset of IPv4 attributes is enough for this first PoC17:10
davidshaYes, I was looking to try and use QoS dscp17:10
davidshakk17:10
igordcardgreat17:11
*** VW has quit IRC17:11
igordcardI will work on the spec this week17:11
*** VW has joined #openstack-meeting17:11
igordcard#link https://review.openstack.org/#/c/333993/10/specs/ocata/common-classifier.rst17:11
davidshaack17:11
*** aarefiev is now known as aarefiev_afk17:12
igordcardplanning to trim it and stick to approach A (the one used in the PoC we are discussing)17:12
*** dmorita has quit IRC17:12
davidsha+117:12
igordcardwill also add your name to the assignees list17:12
davidsha:D17:13
*** donghao has joined #openstack-meeting17:13
*** rossella_s has joined #openstack-meeting17:13
igordcardand looking forward to exchange some information after the new patchset, to further align the spec with the PoC's technical details17:13
davidsha+1, I'd have liked to break it into smaller patches but it all makes the service plugin.17:14
igordcardI should continue to stay very busy with the sfc encapsulation work, but will find time to update and align the spec17:14
davidshaeach patch would not provide anything without the others.17:15
davidshaack17:15
igordcarddavidsha: could you maybe split the db resources and methods from the plugin's methods (just replace them with stubs at the most)?17:15
davidshaigordcard: True, the database migrations don't necessarily have to be in the service plugin patch.17:16
igordcardanyway, it's not like having smaller patches will make it easier to debug a regression or something like that17:16
davidshatrue17:17
igordcardas this is a whole new thing17:17
*** e0ne has quit IRC17:17
igordcardalright, this is all about the PoC for now17:18
igordcardmoving on...17:18
*** donghao has quit IRC17:18
igordcard#topic PTG information17:18
*** openstack changes topic to "PTG information (Meeting topic: network_common_flow_classifier)"17:18
igordcardmyself, you, and sean-k-mooney are going to the PTG17:19
davidshayup17:19
igordcardwe all have context about the CCF and area hoping to give the community more information and discuss at the PTG17:19
igordcardand are *17:19
igordcardI've added the topic to the etherpad17:20
igordcard#topic https://etherpad.openstack.org/p/neutron-ptg-pike17:20
*** openstack changes topic to "https://etherpad.openstack.org/p/neutron-ptg-pike (Meeting topic: network_common_flow_classifier)"17:20
davidshakk17:20
igordcardoops17:20
*** iyamahat has quit IRC17:20
davidshathere is an undo action ;P17:20
igordcarddavidsha: yeah but I wonder if it's in general about the previous line.. or the previous topic17:21
igordcardlet's try17:21
igordcard#undo17:21
openstackRemoving item from minutes: #topic https://etherpad.openstack.org/p/neutron-ptg-pike17:21
igordcardoh cool17:21
davidshaLol17:21
*** diablo_rojo_phon has joined #openstack-meeting17:22
davidshaIt's the last action the bot took.17:22
*** ihrachys has quit IRC17:22
*** yamahata has quit IRC17:22
igordcardI'm looking at the live log but it's not being very helpful17:22
igordcardanyway, back to the point17:22
igordcardI've added the CCF topic to the neutron pike ptg etherpad17:23
igordcard#link https://etherpad.openstack.org/p/neutron-ptg-pike17:23
igordcardwhen the PoC is published I'll add the link to it too (to the etherpad ccf bullet)17:23
davidshakk17:23
igordcardanything else about the PTG?17:24
davidshaNo, I'm good.17:24
igordcardalright, moving on...17:24
igordcard#topic Open discussion17:24
*** openstack changes topic to "Open discussion (Meeting topic: network_common_flow_classifier)"17:24
igordcardanything else we need to discuss?17:24
igordcardI'm good too17:26
igordcardalright davidsha, have a nice evening17:26
davidshaigordcard: you too.17:26
*** FengShengqin1 has quit IRC17:26
igordcard#endmeeting17:26
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:26
openstackMeeting ended Tue Feb 14 17:26:33 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:26
openstackMinutes:        http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2017/network_common_flow_classifier.2017-02-14-17.01.html17:26
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2017/network_common_flow_classifier.2017-02-14-17.01.txt17:26
openstackLog:            http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2017/network_common_flow_classifier.2017-02-14-17.01.log.html17:26
*** jdurgin1 has quit IRC17:26
*** caboucha has quit IRC17:26
*** sudipto has joined #openstack-meeting17:28
*** sudipto_ has joined #openstack-meeting17:28
*** ociuhandu has quit IRC17:29
*** davidsha has quit IRC17:30
*** pcaruana has quit IRC17:31
*** nadya has quit IRC17:33
*** ihrachys has joined #openstack-meeting17:33
*** lpetrut has quit IRC17:35
*** Swami has joined #openstack-meeting17:35
*** rasca has quit IRC17:37
*** Apoorva has joined #openstack-meeting17:38
*** lamt has quit IRC17:40
*** iyamahat has joined #openstack-meeting17:46
*** rajinir_ has joined #openstack-meeting17:46
*** spilla has joined #openstack-meeting17:50
*** myoung has quit IRC17:51
*** gagehugo has joined #openstack-meeting17:52
*** dmorita has joined #openstack-meeting17:53
*** unicell has joined #openstack-meeting17:53
*** mickeys has joined #openstack-meeting17:55
*** reedip_1 has quit IRC17:55
*** dbecker has joined #openstack-meeting17:57
*** ralonsoh has quit IRC17:57
*** nadya has joined #openstack-meeting17:58
*** hashar has quit IRC17:59
*** browne has joined #openstack-meeting17:59
lbragstad#startmeeting keystone18:00
openstackMeeting started Tue Feb 14 18:00:23 2017 UTC and is due to finish in 60 minutes.  The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: keystone)"18:00
openstackThe meeting name has been set to 'keystone'18:00
lbragstadping agrebennikov, amakarov, annakoppad, antwash, ayoung, bknudson, breton, browne, chrisplo, crinkle, davechen, dolphm, dstanek, edmondsw, edtubill, gagehugo, henrynash, hrybacki, jamielennox, jaugustine, jgrassler, knikolla, lamt, lbragstad, kbaikov, ktychkova, morgan, nishaYadav, nkinder, notmorgan, portdirect raildo, ravelar, rderose, rodrigods, roxanaghe, samueldmq, SamYaple, shaleh, spilla, srwilkers,18:00
lbragstad StefanPaetowJisc, stevemar, topol18:00
bknudsonhi18:00
browneo/18:00
lbragstadbknudson o/18:00
rderoseo/18:00
spillao/18:00
*** jaugustine has joined #openstack-meeting18:00
dstaneko/18:00
knikollao/18:00
cmurphyo/18:00
raildoo/18:00
jaugustineo/18:00
*** mickeys has quit IRC18:01
*** jkilpatr has joined #openstack-meeting18:01
*** jkilpatr_ has quit IRC18:01
*** guyr-infinidat has quit IRC18:01
lbragstad#link agenda https://etherpad.openstack.org/p/keystone-weekly-meeting18:01
gagehugoo/18:02
lbragstadwe have a pretty light agenda today, so we'll give it a minute or two for others to show up18:02
stevemaro/18:02
* stevemar grabs popcorn18:02
lbragstadstevemar aren't you suppose to be on vacation?18:03
*** vi01et03 has quit IRC18:03
lbragstadstevemar or sleeping?18:03
*** ankur-gupta-f4 has joined #openstack-meeting18:03
stevemarlbragstad: management said no to my sleeping request18:03
lbragstadstevemar sounds like you need to talk to HR ;)18:03
*** chris_morrell has joined #openstack-meeting18:03
*** michael_bredel has quit IRC18:03
knikollastevemar: should have phrased it as "productive thinking with my eyes closed"18:04
*** guyr-infinidat has joined #openstack-meeting18:04
lbragstadknikolla i do that *all* the time18:04
dstanek"i demand mid-day naps"18:04
lbragstad#topic Meeting time18:04
*** openstack changes topic to "Meeting time (Meeting topic: keystone)"18:04
lbragstadalright - does this time still work for everyone?18:04
*** nadya has quit IRC18:04
gagehugoyup18:05
stevemarworks for me18:05
dstanekyep18:05
lbragstadI don't think we've ever changed the time of this meeting since I've been on the project, but wanted to ask since i know we have new folks18:05
lbragstadI'm good with it18:05
*** ashcrack has quit IRC18:05
bknudsonworks for me18:05
knikollaworks for me18:05
lbragstadthis is the response I was planning for :)18:05
*** krtaylor has quit IRC18:05
*** dbecker has quit IRC18:05
cmurphyif the meeting time didn't work for someone wouldn't it be unlikely they'd be here to mention that?18:06
lbragstadcmurphy more than likely - yes18:06
*** yamahata has joined #openstack-meeting18:06
dolphm+1 for confirmation bias18:06
lbragstadcmurphy would a mailing list post be more appropriate?18:06
gagehugolbragstad that would probably be a good idea18:07
ayoungheyo18:07
lbragstad#action lbragstad to send a note to the mailing list to see if meeting time still works for everyone (even those not in the meeting)18:07
lbragstad#topic Cross project liaisons18:08
*** openstack changes topic to "Cross project liaisons (Meeting topic: keystone)"18:08
lbragstad#link https://wiki.openstack.org/wiki/CrossProjectLiaisons18:08
dstaneki'd like to give up my QA spot to let someone else get in there - maybe a non-core would be interested?18:08
lbragstadif anyone else would like to sit out a release, now is the time to shuffle those seats18:08
knikolladstanek: there's a requirement to be core i think18:09
lbragstadknikolla nope -18:09
lbragstad"The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL."18:09
topolo/18:09
dstaneklbragstad: ++18:09
dstanekplus it helps people get more involved that may want to be core18:09
lbragstadso if anyone here wants to be a CPL, please speak up :)18:09
lbragstaddstanek ++ exactly18:10
*** armstrong has quit IRC18:10
lbragstadbeing a CPL is a great way to get more involved, especially with other projects18:10
*** guyr-infinidat has quit IRC18:10
knikollaThe liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.18:10
knikollafrom the wiki ^^18:10
knikollathe QA section of CPL18:10
*** FengShengqin1 has joined #openstack-meeting18:10
lbragstadhmm - it'd take *should* with a grain of salt18:11
*** kristian__ has quit IRC18:11
topolsounds like PTL discretion to me :-)18:11
lbragstadI'd personally rather have a contributor that is willing to spend time on the responsibilities of the CPL versus a core reviewer who is already spread to thin and can't dedicate the time18:11
dstaneki don't know why they'd have separate rules18:11
dstanekif someone wants to step up i'm sure they have the backing of the PTL and several cores18:12
topollbragstad +++18:12
*** sambetts is now known as sambetts|afk18:12
lbragstadknikolla would you be interested taking over the QA CPL role from dstanek ?18:12
knikollalbragstad: i'd be interested, though i can't give a definitive answer now18:13
lbragstadknikolla that's fine18:13
ayoungrodrigods, let me volunteer you for that18:13
lbragstadknikolla I'll follow up with the maintainers of that page and see if that's a hard requirement (even though it doesn't sound like it is)18:13
*** neiljerram has quit IRC18:13
lbragstad#action lbragstad to follow up about requirement of core for CPL roles18:14
topoltypicaly when something says should its not set in stone and discretion is allowed18:14
lbragstadanyone else interested in stepping up for down for a CPL role?18:14
lbragstadtopol ++18:14
lbragstadtopol I would imagine it's ultimately up to the project18:14
topolI agree18:14
ayounglbragstad, rodrigods is full time QA.  He'd be the obvious choice for the QA liason18:15
knikollaayoung: ++18:15
lbragstadrodrigods thoughts?18:15
lbragstadrodrigods do you accept this voluntrolling?18:15
*** dmorita has quit IRC18:15
ayoungsilence == consent18:15
knikollalol18:15
raildohaha ++ for rodrigods18:16
lbragstadI won't push anyone into it just yet, but I will make a note to follow up with folks so that we can keep the position filled18:16
ayounglets get a confirmation from him later...18:16
knikollaagreed18:16
lbragstadmoving on18:16
lbragstad#topic Pike PTG Planning and Agenda18:16
*** openstack changes topic to "Pike PTG Planning and Agenda (Meeting topic: keystone)"18:16
lbragstad#link https://etherpad.openstack.org/p/keystone-pike-ptg18:16
lbragstadrough outline of our agenda is at the bottom, along with some basic information about the format18:16
*** tonytan4ever has joined #openstack-meeting18:17
lbragstadI'm working on the schedule now - so if anyone notices a conflict somewhere, please let me know as soon as possible18:17
lbragstadalso - if anyone has a last minute topic, let me know18:17
lbragstadI think we are just going to have a single room for 3 days18:18
lbragstad(wednesday through friday)18:18
*** dbecker has joined #openstack-meeting18:18
lbragstadit will be available from 9 - 5 (6 if we need it)18:18
lbragstadI am going to try and fit the time blocks to the topic, so that we don't feel cramped for time if we have a large topic to work through18:19
lbragstadlike-wise for smaller topics18:19
lbragstadmy plan is to have this fleshed out by thursday18:19
bknudsonlots to go through in 3 days18:19
lbragstadbknudson yes, thereis18:19
lbragstadif there is anything major that we need to work around, scheduling-wise, I'll need to know within the next day or two18:20
lbragstadby friday i expect to have a pretty solid schedule laid out18:20
samueldmqlbragstad: nice single room is good18:20
lbragstad(along with etherpads for dedicated topics - complete with background information)18:20
lbragstad++18:21
lbragstadif we need to meet up with any other projects wednesday through friday - we will have to start scheduling that18:21
lbragstada lot of other projects are working through their schedules now, too18:21
lbragstadlast bits about the PTG sessions18:22
lbragstadI'd like to see if we can stick to the Champion/Moderator/Scribe model throughout the PTG18:22
lbragstadI put definitions for each of those roles in the etherpad (in the agenda section)18:22
samueldmqlbragstad: cool, we will have a meeting for policy , correct ?18:22
samueldmqyou hav emore info on that ?18:22
lbragstadsamueldmq we do - and it will be coordinated with the nova + cinder teams18:22
*** nadya has joined #openstack-meeting18:23
lbragstadI have that blocked off for thursday afternoon18:23
lbragstadafter lunch18:23
lbragstadfor now - that's really the only topic we have set with any sort of precedence, since we rely on schedules from other projects18:24
lbragstad(nova is going to be meeting with cinder thursday morning and ironic on wednesday afternoon)18:24
samueldmqcool18:25
lbragstaddoes everyone know what times they plan on getting in and leaving?18:25
lbragstadI'll be there Wednesday morning and staying until late friday night18:26
gagehugotue afternoon - friday night18:26
rderoseyeah, Tues 4 PM, leaving Fri night18:26
*** tesseract-RH has quit IRC18:26
lbragstadwe typically have a lot of folks heading home on friday afternoon - so I have the hackathon tentatively set for that day18:26
samueldmqsun-sat18:26
topolIm Sunday thru Friday. Got Interop stuff Monday-Tuesday18:27
lbragstadif we need more room for topics, we can bump into the hackathon time18:27
knikollaTues 8pm, Sat morning18:27
dstaneksometime on tuesday and sometime on friday -- my departures are a little variable though18:27
knikollawill miss happy hour :(18:27
bknudsonI'm also there Sun - Fri since oslo is mon-tue18:27
*** ijw has joined #openstack-meeting18:27
lbragstadcool18:27
lbragstadI expect  for things to come up throughout the week - so if find potential hackathon ideas we can add them later18:28
* topol trying to remember all my favorite restaurants. I lived in ATL 9 years18:29
lbragstadotherwise we can keep that as a breakout session, too18:29
lbragstadtopol oh - i'm one step ahead of you :)18:29
*** ltomasbo is now known as ltomasbo|away18:29
lbragstadtopol feel free to amend my list on line 132 #link https://etherpad.openstack.org/p/keystone-pike-ptg18:29
*** e0ne has joined #openstack-meeting18:29
lbragstadthose ^ were a few places we went to the last time we had a summit in ATL18:29
*** eharney has quit IRC18:30
lbragstadI threw them there in case we needed ideas for supper any of those nights18:30
samueldmqlbragstad: ++ nice18:30
topolAhhh, let me expand your horizons with some real local favorites18:30
lbragstadtopol ++18:30
samueldmqhehehe18:31
samueldmqtopol: ++18:31
*** dmorita has joined #openstack-meeting18:31
lbragstadalright - anyone else have questions about the PTG?18:31
lbragstad#topic Open discussion18:32
*** openstack changes topic to "Open discussion (Meeting topic: keystone)"18:32
bknudsonwaffle house18:32
lbragstadbknudson -218:32
brownehaha18:32
lbragstadI went there last time18:32
*** eharney has joined #openstack-meeting18:33
*** sudipto_ has quit IRC18:33
*** sudipto has quit IRC18:33
* jaugustine waiting intensely waiting for gmaps link to Panchos18:34
*** bobh has quit IRC18:34
gagehugoMonster Margarita huh18:35
*** sudipto has joined #openstack-meeting18:35
*** sudipto_ has joined #openstack-meeting18:35
*** sudipto_ has quit IRC18:35
*** sudipto has quit IRC18:35
*** dmorita has quit IRC18:35
samueldmqgagehugo: is that a huge margerita pizza ?18:38
gagehugosamueldmq I have no idea, but it sounds interesting18:39
gagehugoI assume it's just a very big margerita18:40
*** eharney has quit IRC18:40
samueldmq+18:40
samueldmq++18:40
*** DuncanT has quit IRC18:41
*** e0ne has quit IRC18:42
lbragstadi think my client dropped, did the meeting actually end?18:45
*** ianychoi_ has joined #openstack-meeting18:46
clarkblooks like still open discussion18:46
lbragstadthanks for coming and a reminder that next week we probably won't have a meeting due to travel18:46
lbragstadthanks clarkb18:46
*** lamt has joined #openstack-meeting18:46
lbragstad(not sure what happened there)18:46
lbragstad#endmeeting18:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:46
openstackMeeting ended Tue Feb 14 18:46:43 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-02-14-18.00.html18:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-02-14-18.00.txt18:46
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-02-14-18.00.log.html18:46
*** browne has left #openstack-meeting18:47
lbragstadthere we go - I actually attempted to end the meeting 10 minutes ago, but my connection blipped18:47
*** ianychoi has quit IRC18:48
*** gagehugo has left #openstack-meeting18:51
*** myoung has joined #openstack-meeting18:53
*** eharney has joined #openstack-meeting18:53
*** s3wong has joined #openstack-meeting18:55
*** krtaylor has joined #openstack-meeting18:56
*** abalutoiu has quit IRC18:58
*** baoli has joined #openstack-meeting18:58
*** e0ne has joined #openstack-meeting18:59
fungiinfra team, culminate!19:00
fungithis week we have topics proposed by jeblair, fungi and ianw19:00
*** ihrachys has quit IRC19:00
* clarkb materializes19:00
*** pvaneck has joined #openstack-meeting19:00
*** ihrachys has joined #openstack-meeting19:00
bkeroo/19:00
*** olaph has joined #openstack-meeting19:00
jeblairyay!  i wonder what my topic is19:00
ianwo/19:00
olaphyo19:00
fungijeblair: i carried over your topic from last week in case you had more followup19:01
jeblairi hope it's a good one19:01
fungiyou can make it as brief as you like ;)19:01
*** salv-orl_ has joined #openstack-meeting19:01
jeblairfungi: i did that in the zuul meeting too!  totally on purpose!  :)19:01
jeblairbut yeah, a couple mins would be good19:01
*** chris_morrell has quit IRC19:02
zaroo/19:02
pabelangerhi19:02
*** donghao has joined #openstack-meeting19:03
fungi#startmeeting infra19:03
openstackMeeting started Tue Feb 14 19:03:49 2017 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
*** openstack changes topic to " (Meeting topic: infra)"19:03
openstackThe meeting name has been set to 'infra'19:03
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:03
*** salv-orlando has quit IRC19:03
fungi#topic Announcements19:04
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:04
mordredo/19:04
fungi#info Final version of the foundation's logo work for the Infra team is now available19:04
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2017-February/005151.html Foundation mascot and logo treatments for Infra team (final version)19:04
fungiclarkb also mentioned to me that if you're going to do something with those, avoid the jpegs. the png versions are devoid of terrible jpeg artifacting19:04
fungi(and there are also vector versions as well)19:05
*** ashcrack has joined #openstack-meeting19:05
fungias always, feel free to hit me up with announcements you want included in future meetings19:05
*** dbecker has quit IRC19:05
fungi#topic Actions from last meeting19:05
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:05
fungi#link http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-02-07-19.04.html Minutes from last meeting19:05
*** chenying has quit IRC19:05
fungiShrews propose a change adding yourself to modules/openstack_project/manifests/users*.pp in system-config19:05
fungi#link https://review.openstack.org/430421 Add David Shrewsbury to users/infra-root19:05
fungithat's been approved!19:05
*** chenying has joined #openstack-meeting19:05
*** lpetrut has joined #openstack-meeting19:05
fungiShrews is not in here though19:06
fungi#topic Specs approval19:06
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:06
*** BobH has joined #openstack-meeting19:06
fungiwe don't seem to have anything new up this week19:06
fungi#topic Priority Efforts19:06
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:06
*** Shrews has joined #openstack-meeting19:06
funginothing called out specifically here, though there are some zuul/nodepool topics coming up later in the meeting19:07
fungi#topic Zuul related PTG prep (jeblair)19:07
*** openstack changes topic to "Zuul related PTG prep (jeblair) (Meeting topic: infra)"19:07
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2017-February/005131.html Zuul info for PTG19:07
* Shrews throws a delayed wave o/19:07
*** Patifa has joined #openstack-meeting19:07
fungithat's an awfully good thread (though i'll admit i haven't finished digesting it yet)19:07
*** donghao has quit IRC19:07
jeblairif folks could read that before arriving at the ptg, that would be great19:07
jeblairwe will at least have a common vocabulary to discuss things :)19:08
jeblairwe have also been working on the list here19:08
jeblair#link https://etherpad.openstack.org/p/pike-ptg-zuul19:08
fungijust to reiterate, as zuul v3 and its related effects are probably the largest undertaking we've worked on as a team in recent years, expect it to be the primary source of activities for us at the ptg19:09
Shrewsgosh. i hope it works then  :)19:09
jeblairwe're making good progress on that so i think we'll be able to accomplish something.  :)19:09
fungiwe will make time/space for collaboration on other things, but zuul/nodepool work will likely demand the main room a lot of the time19:10
*** baoli has quit IRC19:10
*** kaisers has quit IRC19:10
*** gouthamr has quit IRC19:10
jeblairfungi: i think that about covers it19:11
fungithanks jeblair, looking forward to it!19:11
fungi#topic Devstack trusty & nodepool (ianw)19:11
*** openstack changes topic to "Devstack trusty & nodepool (ianw) (Meeting topic: infra)"19:11
fungi#link https://review.openstack.org/433218 Remove distro support based on new libvirt minimum19:11
BobHis there a rough schedule on how much time we'll spend together each day? For those of us that may things going on in the evenings.19:11
*** sshnaidm is now known as sshnaidm|afk19:11
ianwjust to sync up on this, mostly for dib purposes ...19:11
fungiBobH: we've got a general ptg planning topic coming up later in the meeting too, we can get into it there19:11
ianwso all our nodepool dsvm testing is xenial right?  even though the builders are actually trusty?19:11
*** e0ne has quit IRC19:12
pabelangerthat sounds right19:12
ianwi presume that as we bring zuulv3 online, we'll be using xenial underneath?19:12
fungiianw: i think that's pretty temporary. we all agreed, i think, that we want to rebuild them on xenial shortly19:12
*** armax has quit IRC19:12
clarkbyes the risk was also thought to be minimal since for non dib things its all python and rest apis19:13
fungii expect that it'll be xenial (or at least not trusty) by the time we go into production19:13
*** baoli has joined #openstack-meeting19:13
clarkb*all python 2.719:13
jeblairwe could probably start replacing the nb hosts now if we wanted?19:14
pabelanger++19:14
clarkbjeblair: yup and we could add them then delete old ones19:14
ianwthat might not be a bad idea to shake out issues early19:14
fungiyeah, i think we had briefly discussed deploying them initially on xenial but opted to do trusty first and then rolling replace with xenial soon after19:14
jeblairmaybe we could start that after the ptg....19:14
ianwand i could reduce trusty testing on dib too19:14
fungishortly post-ptg wfm19:15
Shrewsafter the PTG sounds sane19:15
*** spilla has left #openstack-meeting19:15
ianwok, i'll be happy to help out with that19:15
fungi#agreed Soon after the PTG we should start replacing the 14.04-based nodepool builder instances with 16.0419:15
ianwthat was all, just wanted to sync up on the deprecation, thanks19:16
fungithanks ianw! good to point out the implications of libvirt minimums there19:16
fungione (less savory) option would also be to test nodepool against stable/ocata until we can switch to master nova's expectations19:17
fungibut i doubt it will come to that19:17
clarkbfungi: we test on xenail though19:17
clarkbso we meet nova's expectations19:17
fungioh, fair enough19:17
clarkb(this was part of the argument for running on xenial, it would be harder to keep all that stuff working then a simpleish python2.7 process)19:17
*** dmorita has joined #openstack-meeting19:17
fungii meant if we wanted to test accurately for production, but yeah19:18
ianwyeah, we are on xenial.  we still run dib functional tests on trusty19:18
clarkbthen we would over time get there on the daemon side19:18
fungiyep, seems fine to me19:18
jeblairto be fair, we don't actually care that nodepool works with nova master, we care that it works with clouds we use.  devstack/nova master is a proxy for that.  :)19:18
fungi(and possibly a poor one, but at least an optimistic assumption!)19:19
clarkbindeed19:19
jeblairbut yeah, the only sane thing for us to do i think is to continue testing master, so i'm glad we're doing that.19:19
fungianything else here before we forge on in the agenda?19:20
ianwnope19:20
fungi#topic Redirect developer and docs from HTTP to HTTPS (fungi)19:20
*** openstack changes topic to "Redirect developer and docs from HTTP to HTTPS (fungi) (Meeting topic: infra)"19:20
fungi#link https://review.openstack.org/432334 Redirect developer and docs from HTTP to HTTPS19:20
fungijust a quick note that the docs team reached consensus on only serving via https going forward and redirecting all http to https19:21
bkeroYay19:21
*** salv-orl_ has quit IRC19:21
fungithat change has a couple of +2s so i'm planning to approve it shortly following the meeting unless there are any objections19:21
ianwcool, that seemed fine, but i figured we should merge it when people were around19:21
clarkbwoo19:21
*** salv-orlando has joined #openstack-meeting19:21
*** dmorita has quit IRC19:22
fungii'll be around a good chunk of the evening, but wanted to make sure everyone in subsequent timezones was also aware (and knew what to revert if needed)19:22
jeblair++19:22
mordred\o/19:22
fungiany questions/concerns on this before we move on?19:22
jeblairi like the speed and efficiency with which consensus was reached.  :)19:23
fungiyes, AJaeger is good at squeezing answers out of people ;)19:23
*** salv-orlando has quit IRC19:24
fungi#topic Release bindep 2.2.0 (fungi)19:24
*** openstack changes topic to "Release bindep 2.2.0 (fungi) (Meeting topic: infra)"19:24
fungi#link http://git.openstack.org/cgit/openstack-infra/bindep/log/ Recent bindep commits19:24
*** emagana has joined #openstack-meeting19:24
fungiwe've had a number of requests to get a new bindep in circulation, particularly for the rhel support change19:25
fungithere is one outstanding change for bindep with no negative reviews we could wedge into this before tagging too, if anyone's interested in looking over it19:25
fungi#link https://review.openstack.org/428394 Extract file finding and processing to functions19:26
clarkbI know ihrachys said https://review.openstack.org/#/c/381979/ was important and asked for reviews on the mailing list, so I reviewed and it hasn't gotten a response19:26
fungiyeah, i was waiting for him to resurrect that one before looking at it again19:27
fungiso am not expecting it to make this release19:27
fungifrom the already merged changes since 2.1.0 i think this needs to be 2.2.0 (new features, but no backward-incompatibilities)19:27
fungianyone disagree?19:27
clarkbnope19:28
fungiis this too risky at this point in the release cycle? (it's not in global requirements and isn't a dependency of anything, but does get used in lots of jobs)19:28
fungii feel like our existing functional testing is pretty thorough at least19:28
fungialong with significant unit test coverage19:29
clarkbthats a good point, because it isn't constraints managed it isn't super simple to avoid a broken release19:29
fungittx: as release ptl now, you might have some input there19:29
clarkbbut it probably isn't too hard to modify our bindep job macro to install previous version if necessary19:29
fungiyeah, i do think we have some easy and quick ways to solve any unintended breakage, including just quickly patching and tagging another release (because of no requirements sync baggage), or rolling back nodepool images19:30
pabelangerany downside to adding it to constraints?19:30
*** emagana has quit IRC19:31
fungiwhat would be the up-side? it's not a dependency of anything19:31
fungiand we run it from a pre-built virtualenv baked into our images19:31
pabelangertrue, was just asking19:31
jeblairyeah, i think it's used too early in the process for constraints to help19:31
fungiright, putting upper-constraints.txt wouldn't do anything afaik19:32
fungier, putting it in19:32
fungiokay, i'll double-check with the release team just to be sure they're aware (and let them know that we don't expect any impact)19:32
fungiotherwise planning to move forward with tagging 2.2.0 in the next day or so19:33
clarkbright bindep has to run before pip with constraints does in order to get system deps in place19:33
fungi#info Expect bindep 2.2.0 in the next 24-48 hours unless there is strong objection from the Release Management team19:34
fungi#topic General PTG planning (fungi)19:34
*** openstack changes topic to "General PTG planning (fungi) (Meeting topic: infra)"19:34
fungi#link https://etherpad.openstack.org/p/infra-ptg-pike Infra Pike PTG planning pad19:34
fungiBobH: can you repeat your question from earlier, if you're still around?19:34
clarkbre General PTG Planning I wanted to get the test failure debugging session onto the project room schedule19:35
BobHsure, do we have an idea on how much time we'll spend together during the day to allow for time in the evening for other activities19:35
clarkbandreaf: if you are around you might have input on ^ too19:35
clarkbI was wondering what people thought about when would be most effective, during the first two days of ptg or last 3 days? or maybe do it twice once for each group?19:36
fungiBobH: great question. i'm looking now to see if we have specific hours for start/finish published for teh conference space19:36
BobHI couldn't find anything other than it was up to the respective teams19:37
ttxfungi: reading19:37
*** abalutoiu has joined #openstack-meeting19:37
jeblairthe ethercalc make it look like 9-519:37
clarkbjeblair: 5:3019:37
clarkbI think the 5 block runs until 5:3019:37
ttxrooms will stay open until 6pm19:37
ttxNormal hours are 9-519:38
jeblairclarkb: indeed19:38
fungithanks jeblair/clarkb/ttx19:38
ttxbut overtime is ok19:38
fungii feel like 9-5 is plenty. don't want to burn everyone out19:38
ttxre: release management I'd rather keep things safe until next Wednesday19:38
ttxslushy slush19:39
clarkb9-5 sounds good to me19:39
ttxespecially for things that are a bit special19:39
BobHworks for me.19:39
*** ihrachys has quit IRC19:39
fungittx: mmm, okay i can put off the new bindep until after release day19:39
fungii keep forgetting it's next wednesday already19:39
*** rosmaita has joined #openstack-meeting19:39
fungia week from tomorrow19:40
jeblairhow important are the rhel support updates?  are they blocking any (release related) work?19:40
*** raildo has quit IRC19:40
clarkbre joint infra/qa session on debugging test failures. Seems like we currently pull more people from cross project work into that so possibly valuable to do it during first two days. But also valuable to do it during last 3 days to hopefully make more of the projects self sufficient in debugging things19:40
fungijeblair: there shouldn't be any release dependency on bindep since it's intended for developers setting up development environments19:40
*** ihrachys has joined #openstack-meeting19:41
fungiand for some convenient automation in our ci19:41
jeblairfungi: poorly phrased question -- i mean are they blocking any openstack developer's ability to complete the release of their project?19:41
funginot to my knowledge, no19:41
jeblaircool19:41
*** salv-orlando has joined #openstack-meeting19:41
clarkbif no one else has opinions on that session schedulign I will probably just pencil it in twice for the two groupings of days19:42
jeblairclarkb: i wonder how many vertical devs will be around the first 2 days...?19:42
fungiclarkb: yeah, if we only have one joint debugging session it likely needs to be monday/tuesday because harder for the various services teams to work out a time they can have representatives available19:43
jeblairclarkb: yeah, both as an experiment sounds like a good idea19:43
fungioh, great point jeblair19:43
clarkbya thinking we want to reach both groups and having it during each chunk of time might be best way to do that19:43
jeblairfungi: if we had to (guess and) pick 1, i would probably actually pick last 3 days...19:43
fungii somehow ignored that some of the services teams might not have anyone show up until wednesday19:43
clarkbalso thinking half an hour might not be enough and should go for an hour?19:44
jeblairfungi: i agree with your point about difficulty in scheduling though.19:44
clarkbthere I penciled in two hours19:45
*** claudiub|2 is now known as claudiub19:45
clarkbandreaf: if you can provide feedback on those selections that would be great19:45
*** neiljerram has joined #openstack-meeting19:45
pabelangerhttps://ethercalc.openstack.org/Pike-PTG-Discussion-Rooms is the URL in question, too me a while to find it19:45
jeblairclarkb: i watched you pencil them in!  ++19:45
fungiclarkb: i agree that's safest. is there a rough set of examples you expect to work from?19:45
*** Akis__ has joined #openstack-meeting19:46
clarkbfungi: I was planning on digging through recent ones19:46
clarkbprobably fridayish19:46
clarkbso the kolla jinja2 failure19:46
fungittx: is there a reason not to link that spreadsheet in https://wiki.openstack.org/wiki/PTG/Pike/Etherpads (or is it there and i'm not seeing it)>19:46
fungi?19:46
clarkbsome of the OOM fails19:46
clarkbthe libvirt crashes with nested virt19:46
*** rfolco has quit IRC19:47
fungiyeah, i guess the odds of unsolved gate failures more or less evaporating before then is slim19:47
fungiand if they do, we should spend those slots celebrating? ;)19:47
*** toscalix has joined #openstack-meeting19:48
clarkbbut want to focus on general debugging too19:48
*** matrohon has joined #openstack-meeting19:48
clarkband reading logs etc19:48
*** akiskourtis has joined #openstack-meeting19:48
fungiseems like all of that is covered pretty thoroughly if you just dive into example failures anyway19:48
clarkbsince a large amount ofissues that get run by us seem to be from people just lost in the maze of openstack19:48
pabelanger++19:48
fungibut yes, big thumbs-up to trying to reduce the general confusion over where and how stuff gets logged19:49
*** Akis_ has quit IRC19:49
ttxfungi: no reason, please fix19:50
fungittx: thanks, will do momentarily19:50
*** toscalix has quit IRC19:51
*** Akis__ has quit IRC19:51
mtreinishclarkb: we could just pick something from the uncategorized failure page and dig into19:52
mtreinishit19:52
fungiskimming through our planning pad (and ignoring the stuff i pasted in there as conversation starters), it looks like we have interest in hacking on the next generation of zuul/nodepool (obviously), storyboard stuff (especially promotion and migration tooling), the debugging sessions clarkb has been discussing, maybe some work on firehose, manage-projects stuff (if there's any left to do by then),19:53
fungixenial control-plane migrations and discussing moving some of our control plan to different service providers, and the devstack-gate support for local.conf19:53
clarkbmtreinish: ++ I like that19:53
clarkbdo we have our room assignment so that can be put in etherpad too ? (though there will be maps and plenty of signs aiui so maybe not necessary)19:54
ttxthere will be maps19:55
ttxthere are always maps19:55
ttxreading the maps is important.19:55
fungias stated previously i'm trying to avoid over-structuring this since it's the first ptg and we want to see how things might emerge organically, but one idea i've been toying with is to have at least one volunteer for each of the topics we wind up working on to take notes they can feed me with urls to outcomes (documentation of decisions reached, features implemented, results of demos/testing,19:55
fungiwhatever) so i can more easily produce a summary without missing bits for topics in which i wasn't personally involved19:55
* jeblair wonders what ttx has hidden in the maps19:56
*** gordc has joined #openstack-meeting19:56
*** nadya has quit IRC19:57
pabelangerfungi: seems like a good approach19:57
fungiso between now and monday, be thinking about if there are things you plan to be around for all of where you wouldn't mind keeping track of what's going on for posterity (you don't need to be leading the work, just paying attention and making some notes is enough)19:57
*** kristian__ has joined #openstack-meeting19:58
clarkbalso someone noted there would be an atlanta guide for eateries?19:58
mordredjeblair: special prizes19:58
fungiwe can break some of the more involved topics out into their own tracking pads too and link them from our main etherpad to keep stuff under control19:58
clarkbonce I find that I will try to respond to ml thread about dinner options19:58
fungii still liked the trader vic's suggestion, but i'm probably just biased by the recommended attire19:59
clarkbPitty Pat's Porch looks very atlanta and is downtown. I'm good with Trader Vic's and we all dress appropriately :)19:59
clarkbthey have mai tais too19:59
ttxI may have to borrow an adequate shirt19:59
fungithey would have you believe they're the home of the original mai tai20:00
fungioh, we're out of time20:00
fungithanks everybody!20:00
fungi#endmeeting20:00
bkeroThanks o/20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Feb 14 20:00:34 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-02-14-19.03.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-02-14-19.03.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-02-14-19.03.log.html20:00
*** Shrews has left #openstack-meeting20:00
ttxohai20:00
stevemaro/20:00
sdagueo/20:00
lbragstado/20:00
fungitc-ishness ensues20:00
dtroyero/20:01
flaper87o/20:01
ttxdhellmann, dims, EmilienM, mordred, mtreinish, thingee: around ?20:01
mtreinisho/20:01
ttxjohnthetubaguy is Valentining20:01
mordredttx: I guess so20:01
dhellmanno/20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue Feb 14 20:01:23 2017 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: tc)"20:01
openstackThe meeting name has been set to 'tc'20:01
* edleafe pulls up a chair20:01
flaper87I just want to say you guys are the worst valentine's date I've ever had.20:01
flaper87no offense, though20:01
flaper87:D20:01
* mordred slyly puts his arm around flaper87's shoulder20:01
ttxflaper87: I think I had other TC meetings on Valentine's day Tuesday, so maybe not20:01
* dhellmann sprinkles rose petals at flaper87's feet20:02
ttxOur agenda for today is at:20:02
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:02
*** bastafidli has joined #openstack-meeting20:02
ttx#topic Update projects.yaml with results of the PTL elections20:02
flaper87LOL20:02
*** openstack changes topic to "Update projects.yaml with results of the PTL elections (Meeting topic: tc)"20:02
* flaper87 stfu20:02
ttx#link https://review.openstack.org/43048120:02
*** kristian__ has quit IRC20:02
ttxLooks like I can approve this now unless someone screams20:02
stevemarttx: go for it20:02
ttxdone20:02
* stevemar is happy to be off that list hehe20:02
*** gouthamr has joined #openstack-meeting20:03
ttxstevemar: offciially relieved from that particular duty20:03
ttx#topic PTG organization20:03
*** openstack changes topic to "PTG organization (Meeting topic: tc)"20:03
mugsiestevemar: +1 :)20:03
ttxSo we have the PTG coming next week, was wondering if you had questions20:03
* mordred hands stevemar a pie20:03
ttxRandom bits of information:20:03
stevemarmordred: better be apple20:03
ttxWe'll be communicating / synchronizing via #openstack-ptg, so join that20:03
ttxAnd we have a number of reservable rooms for inter-project discussions which you can book via20:03
EmilienMo/20:03
ttx#link https://ethercalc.openstack.org/Pike-PTG-Discussion-Rooms20:03
ttxWe'll do 9am - 5pm every day (although the rooms will stay accessible until 6pm)20:03
ttxLunch will be served between noon and 1:30pm20:04
ttxit's ok to cut it short20:04
ttxThere will be a happy hour on Tuesday 5-7pm, and a feedback fishbowl session at 5pm on Thursday20:04
*** dmorita has joined #openstack-meeting20:04
ttxOtherwise you should self-organize20:04
ttxWe should have some email today(?) with pointers to group-friendly restaurants in the area20:04
ttxin case you want to set up dinners20:05
stevemarlbragstad: ^20:05
flaper87sounds fantastic20:05
ttxOther questions ?20:05
EmilienM5pm? I scheduled sessions until 620:05
ttxEmilienM: it's fine20:05
flaper87EmilienM: rooms available till 620:05
EmilienMwe don't want to miss parties though :-P20:05
ttxThe bar should not be empty yet20:05
flaper87EmilienM: then stop working20:05
flaper87:P20:05
stevemarlol20:05
fungiis there a separate lunch location, and if so then is it still allowed to bring lunch back to the team rooms instead?20:06
ttxEmilienM: it's on Tuesday, your sessions for TripleO start on Wed ?20:06
EmilienMttx: right20:06
EmilienMI'll make sure flaper87 doesn't go at bar before20:06
ttxfungi: no idea20:06
ttxprobably ok20:06
* fungi will "wing it"20:06
edleafeEmilienM: move your last session to the bar20:06
ttxedleafe: that's the spirit20:06
ttxok, feel free to hit me or diablo_rojo if you have questions, we'll do our best to extract knowledge from the events team and answer20:07
fungiapparently there's a bar in the same hotel, so easy to move any session you like to it probably ;)20:07
EmilienMwe'll be releasing final ocata in our case, we'll need strong drinks20:07
EmilienMttx: thanks of all the infos!20:07
ttx#topic Document current base services20:08
*** openstack changes topic to "Document current base services (Meeting topic: tc)"20:08
ttx#link https://review.openstack.org/43096520:08
*** nadya has joined #openstack-meeting20:08
ttxThis is introducing the concept of "base services"20:08
ttxwhich are things that OpenStack projects can reasonably assume will be present in any OpenStack installation and may therefore freely leverage the features of20:08
ttxIt's not really a new concept, but we never actually listed the things that are OK to assume will be present20:08
ttxCurrently: a database, a message queue and Keystone20:08
ttxwhich kind of made it harder for us from having discussions on how to grow or limit that set20:09
*** dmorita has quit IRC20:09
ttxSo I think this will really help us, by providing a base framework for future necessary debates20:09
ttx(debates like ending the postgres support, or adding a DLM, or being able to assume Barbican will be present)20:09
ttxQuestions, comments ?20:09
mtreinishttx: well this doesn't really effect the postgres discussion. You said an oslo.db compatible db in there20:10
mtreinishpostgres fits that20:10
flaper87I just had one comment on it but not a blocker for sure20:10
ttxmtreinish: it doesn't affect indeed, describves status quo20:10
ttxflaper87: yeah, we can rename after the merge if necessary20:10
ttxfeels like we have enough votes to pass it, then we'll evolve from there20:11
stevemari think the wording is loose enough around the DB that if we can approve that aside from the postgres discussion20:11
flaper87ttx: yup, voted20:11
flaper87ttx: I can do the follow-up one if you want, since I brought it up20:11
* dims_ many apologies for showing up tardy20:11
ttxok approved20:11
fungithe intent seems to be (with databases for example) that you only rely on features of the rdbms exposed through oslo.db, which at least allows us to tune for a common featureset between multiple backends20:12
ttxflaper87: sure -- dtroyer's proposed title sounds good20:12
ttxfungi: yes. If we want to not support postgres anymore, we can eiether block it at oslo.db level or replace that oslo.db statement by something stronger20:12
fungithough the way it's written, i could see people interpreting it such that you can depend on the advanced features of a single database which happens to be a supported oslo.db backend, even if you're not using oslo.db to leverage it (and so may use features not provided by oslo.db)20:13
ttxWe'll get back to that later in the meeting when we cover postgresql20:13
fungiwfm20:13
ttxIt's a living doc so feel free to propose updates :)20:13
ttxI think it accurately describes the current situation20:14
ttx#topic Glance: Changing response status code. What's the best path forward?20:14
*** openstack changes topic to "Glance: Changing response status code. What's the best path forward? (Meeting topic: tc)"20:14
dims_agree20:14
dtroyer++20:14
ttx#link https://review.openstack.org/#/c/420038/20:14
ttx#link https://review.openstack.org/#/c/425487/20:14
ttxflaper87, rosmaita: o/20:14
*** bobh_ has joined #openstack-meeting20:14
flaper87o/20:14
rosmaitao/20:14
flaper87So, I've been talking with rosmaita about this and digging into the topic20:14
flaper87I'll let rosmaita do all the talking, though20:14
rosmaitaok20:14
rosmaitaGlance has proposed to fix a bug, an API call that returns a 200 whereas a 204 (No Content) is more appropriate, by changing the software to return the correct code.  Ordinarily, this would be a questionable move, but we've argued that in this particular case because the documents have always stated this call returns a 204 and all the other related calls in fact return 204s. However, representatives of the QA team saw the change, and did not li20:15
rosmaitaThe Glance team consulted the API-WG Guidelines which state that this kind of thing is generally not acceptable, but the details of this case seemed to make it an exception.  So the Glance team met with the API-WG to see what they thought, and they agreed this was a legitimate exception. Unfortunately, the QA team merged a tempest test that covers this call and expects a 200 in the response, before the discussion was resolved, and now we can't20:15
rosmaitaWe're bringing this up at the TC because we'd like a solution to this particular situation and we feel the need of a non biased body to provide guidance. This issue is also related to the  ongoing discussion about the proposed api-compatability tag20:15
* rosmaita takes a deep breath20:15
flaper87rosmaita: I think your IRC client cut some of the pastes :P20:15
rosmaitashoot, i'm using irssi, but looks ok to me20:16
edleafeWearing my API-WG hat, we felt that it was indeed a reasonable change20:16
dhellmannis that tempest test part of what's used for defcore?20:17
ttxdid not li..20:17
ttxke it ?20:17
mordredI believe making the changes, in this case, are improvements to the user20:17
rosmaitadon't think so, it's metadefs20:17
dhellmannok, good20:17
edleafeThe return code doesn't change the meaning. 200->204 is not the same as, say, 400-40420:17
flaper87Based on how the discussions on this topic have evolved and the parties involved, I think I'd be good with this change happening. The API-WG was part of the discussion and it's not part of defcore20:17
dhellmannI'm curious to understand why the QA team thought adding that test on their own was appropriate.20:17
rosmaitawell, they were expanding test coverage of glance to metadefs20:18
rosmaitaactually, they reported the bug20:18
fungiare the tempest reviewers objecting to a change that will accept either of 200 or 204 for that call?20:18
dhellmannOK, but this change was in progress, right?20:18
rosmaitadhellmann: yes20:18
dhellmannI guess I'm trying to understand how this turned into a blocking situation instead of an opportunity for a conversation.20:18
rosmaitafungi: https://review.openstack.org/#/c/432611/20:18
mordredsounds to me like the process is working ... the QA team found a bug where the code didn't do what the docs say it should and the dev team fixed it20:19
rosmaitayes, the disagreement is on how the fix should go20:19
dhellmannAnd why it had to come to the TC for a decision. Not that asking us to make one is wrong, just we'd like I think to avoid having to do that when possible.20:19
mtreinishfungi: normally that's not how things like this are handled. But they can be in edge cases20:19
mtreinishtempest likes the api to work the same on all releases20:19
mordredso does mordred20:19
edleafedhellmann: Glance did come to the API-WG for a discussion, but our conclusions didn't seem to sway QA20:20
*** raildo has joined #openstack-meeting20:20
fungimtreinish: yeah, looks like oomichi has objected to 432611 on the grounds that tempest is used for defcore (though sounds like the test in question actually isn't)20:20
dhellmannit sounds like the argument for changing the response code is the new value is more accurate and more consistent, and the argument for not changing it is that we don't change response codes?20:20
mordred_but_ - also sometimes we find things that are just bugs - and low-impact bugs too20:20
flaper87dhellmann: I think the current issue is that the discussion has hit a deadlock20:20
*** ijw has quit IRC20:20
*** dbecker has joined #openstack-meeting20:20
*** akiskourtis has quit IRC20:20
mtreinishmostly the issue here stems from a lot of precedence that changes like this need to be handled in a way that things don't change between releases without a versioning mechanism of some sort20:20
edleafeflaper87: bingo20:20
ttxand escalation was the only solution20:20
dhellmannflaper87 : right, and I would like to know why we have two teams deadlocked20:20
*** akiskourtis has joined #openstack-meeting20:20
*** salv-orlando has quit IRC20:20
*** nadya has quit IRC20:21
dhellmannwe can deal with the immediate issue of deciding how to proceed, but we should also deal with the issue of getting deadlocked in the first place20:21
ttxdhellmann: I suspect one of the dimensions of this issue is that the tempest tests live in tempest in that case20:21
edleafedhellmann: one reason is that the API-WG is simply advisory, whereas the TC has a little more power to resolve such issues20:21
mordredI mean - I think the urge to be conservative here is a good one, and I honestly would not mind the process for things like this be to get a TC greenlight - just so that we don't slippery slope back into the world of making brekaing changes across releases20:21
ttxi.e. the QA team has authority on one part of the fix and Glance on the other20:21
mtreinishfungi: I think oomichi is referring to the nature of tempest being used against any cloud and using defcore as an example20:21
*** sdake has quit IRC20:22
mtreinishbut I could be wrong20:22
dims_guess folks who are relying on current behavior will break. folks who read the docs will just scratch their heads. so we lean towards the not-breaking-people direction?20:22
ttxso if they don't agree on the fix and nobody yields... escalation is the right process20:22
fungii would have hoped to see rosmaita follow up to the -1 on 432611 with appropriate counterarguments rather than just assuming the opinion of any reviewer is immutable, but maybe there was other subsequent discussion which isn't reflected in that review?20:22
*** sdake has joined #openstack-meeting20:22
ttxthe only way to avoid that in the future is to put all tempest tests in project-specific repo but we rules the other way recently20:22
mordreddims_: they'll break in theory. in practice, the chances someone has code that is explicitly checking for 200 vs 204 and making different actions based on it is none20:22
edleafeIn case anyone wants my POV on this: https://blog.leafe.com/api-longevity/20:22
ttxruled*20:22
dhellmannttx: only for defcore tests20:22
flaper87fungi: I think that's the cae, although probably not ideal20:23
ttxdhellmann: apparently for that one as well20:23
mordredbecause theonly different action you'd make from 200 to 204 is to not look at the payload - but there is no payload anyway,so there is literally no legitimate consumption difference20:23
dhellmannthat policy only applies to tests intended for use by defcore20:23
dhellmannwell, my point is the test could just be moved20:23
rosmaitafungi: see the other patches ttx linked for the arguments about this20:23
dhellmannthough that doesn't solve the collaboration problem20:23
*** jprovazn has quit IRC20:23
mtreinishmordred: well unless you have a poorly written client that assumes a specific response code to measure success20:23
edleafedhellmann: you are correct in pointing out that there are two problems here20:23
mtreinishmordred: in the past we've asserted that's a thing we've cared about20:24
dhellmannmordred: do we anticipate someone looking at the specific error code at all?20:24
sdaguemordred: yeh, I think it's mostly the difference of opinion of "is not really broken, why fix this"20:24
sdaguedhellmann: people do stuff all the time where they just == KNOWN_GOOD_THING20:24
flaper87mordred: ++20:24
ttxso yes, (1) how do we solve that disagreement and (2) how do we avoid similar situations in the future20:25
mordredyah. it's a jugement call. I'm saying I come down fairly strongly  on "just fix the bug" - because someone who wrote a client that is _specifically_ coding against the 200 and not the 204 coded to a specific success code that is in contradiction to the api docs so holy crap what were they doing?20:25
sdagueright, we've got 2 camps here. QA) don't change things unless it's really hurting people.20:25
dtroyeralso, KNOWN_GOOD_THING is often defined by what it does, not what the docs say20:25
dhellmannmordred : they were coding against how a cloud they use actually works?20:25
sdagueGlance) lets make this more compliant20:25
fungirosmaita: yeah, skimmed and it looks like the pushback from oomichi was that there should be thorough discussion before changing that behavior. now that it's been discussed is he still unwilling to budge?20:25
dims_right dtroyer20:25
*** knangia has quit IRC20:25
sdagueand seems like the TC call is really where we want that slider to be20:26
*** knangia has joined #openstack-meeting20:26
mugsieI do know if i was writing a client for something, and the docs disagreed with the actual response, I would just throw my hands up, and code it to what worked20:26
rosmaitafungi: yes, but as you can see, both sides of this have support20:26
ttxsdague: and I think it's appropriate for the TC to make that call, tbh20:26
dhellmannmugsie : right20:26
mordredmugsie: right. but this is a different _success_ code - coding against a specific code is crazy in teh first place20:26
sdaguebecause I think that after the recommendation, the teams will most likely run with it20:26
*** knangia has quit IRC20:26
edleafemugsie: but I wouldn't be shocked if later the behavior changed to match the docs - especially when it is consistent with everything else20:26
bastafidlican there be intermitent fix when documentation gets adjusted to highlight both behabiours (200 and 204) and then queue real fix for later release?20:26
mordredthe _only_ reason I could _possibly_ think of to check the specific 200 vs. 204 is if you were coding to a spec - in which case you would have been wrong20:27
*** knangia has joined #openstack-meeting20:27
mugsiemordred: sure - but in some APIs different succes codes mean different things20:27
rosmaitamugsie: what edleafe said20:27
mordredotherwise you'll be coding to 2xx20:27
mugsieone is "its done" anther is "come back and check"20:27
mugsiein the 204 case its not as clear cut20:27
stevemarmordred: IIRC thats what triggered the keystone patch to change things from 200 -> 20420:27
mordredright - but this is "it's done" and "it's done and I don't have a payload"20:27
dhellmannmordred: I'm not sure we have previously applied any expectation that users will be rational when we limit changes of this nature. :-)20:27
mordreddhellmann: :)20:27
sdaguedhellmann: yeh, that's really the crux20:28
dtroyerthis is probably the closest we will come to this sort of exception being mostly harmless20:28
mordreddtroyer: ++20:28
stevemardtroyer: true20:28
sdagueso... just to be warned20:28
dtroyerI really don't think we are in danger of setting precedent we will eventually regret here20:28
mordredme either20:28
edleafemugsie: if I saw docs = 204 and behavior = 200, I'd code 200 <= response < 300 and be done with it. :)20:28
ttxOK, let's make some progress here -- (1) which approach would you rather take, Glance or QA ? And (2) how would you avoid such disagreement in the future ?20:28
flaper87fwiw, in this case, I'd prefer to take the API-WG's advice and go with it20:28
mordrededleafe: ++20:28
sdaguethere have been individuals across multiple projects wanting to change up all the success codes to match the api-wg recommendations20:28
mordredttx: I explicitly do not want this to be about a general response20:28
sdaguebecause probably about 30% of succes is wrong20:29
dhellmannttx: to be clear, it's a choice between correcting the docs and between changing the code?20:29
sdagueby strict http standards20:29
mordredthis is a very specific case with a very specific set of tradeoffs20:29
mtreinishdtroyer: there is a simple middle ground here just version the api. So it matches the docs moving forward but maintains backwards compat for older clients20:29
flaper87dhellmann: yes20:29
mordredthat I think rosmaita has done a great job of enumerating20:29
dtroyersdague: sure, and much of that will cause much more heartburn… are the docs wrong (different) in those cases too?20:29
fungidhellmann: or between changing the documented behavior and correcting the code ;)20:29
sdagueso, if this slider moves, that all comes into play20:29
mtreinishwhich is what I always recommend for an api change20:29
mordredwe absolutely do not need to make any larger decisions on policies20:29
dhellmannfungi : yes20:29
ttxmordred: so you would explicitly not provide an answer for (2) (how to avoid such disagreement in the future)20:29
mordredttx: yes. very much so20:30
ttxand rule case by case20:30
sdaguedtroyer: where the docs have been wrong on the nova side, we've been just fixing the docs20:30
dtroyermtreinish: assuming clients ever actually pay attention to API versions… it's more of a "notice a break" and reactively deal with it situation20:30
mordredthis is not a precedent-needing problem20:30
mugsiebut, now the docs will be wrong for one release, and right for one - where as if the docs are fixed, they are right for all versions20:30
mordredyes20:30
ttxmordred: wfm20:30
dtroyersdague: perfectly good option too20:30
edleafettx: I understood 2) to mean "why don't teams cooperate"?20:30
fungii like flaper87's position. we have the api working group for a reason, and the glance team did consult with them to get an answer. i see no reason to disagree with them on api-behavior-specific topics20:30
mtreinishdtroyer: right, by versioning it you don't break anyone20:30
mtreinishmugsie: right, I view this as more a doc bug then anything20:31
edleafemtreinish: now if only Glance supported microversions... :)20:31
mordredversioning just shifts the complexity to a different place20:31
mordredfor this20:31
ttxfungi: ++20:31
stevemarmordred: yeah20:31
flaper87fungi: ++20:31
smcginnismordred: +120:31
mugsiemordred: ++20:31
dtroyerversioning needs to be done, but I don't think this is a zero-sum situation20:31
dhellmannfungi : ++20:31
mtreinishedleafe: right, this issue has come up before with glance more than once in the past few weeks, and it's why I proposed that tag20:32
fungialso, the tc contradicting the api working group on a topic like this feels like a vote of "no confidence" in them20:32
dtroyerfix the friggin bug, and get up to date with versioning…we really need both20:32
edleafedtroyer: +120:32
mordreddtroyer: totes. versioning needs to be done. but punting to versioning for this one I think is overkill20:32
ttxOK, it feels like there is a majority agreeing to take Glance's side on this one ? And no majority to make that a precedent20:32
*** lpetrut has quit IRC20:32
* ttx prepares a #startvote20:32
flaper87ttx: you may want to have an actual IRC vote, just for logging purposes20:32
mordredttx: if there is any precedent, it's that the teams all acted appropriately20:32
dims_i can go with that ttx20:32
flaper87ttx: that20:32
flaper87:D20:32
mordredttx: glance talked to the API-WG - the QA team was appropriately conservative20:32
dims_++ mordred20:33
rosmaitamordred: ++20:33
dtroyermordred: ++20:33
mordredif the same situation arises again and all of the teams follow this pattern I don't think it'll be bad for openstack20:33
mtreinishmordred: no versioning should have been done for the other breaking change glance made a few weeks ago where they completely changed the membership api20:33
sdagueso, I don't actually understand how you can reject the precident though20:33
edleafemordred: good summary20:33
fungii definitely don't see this as setting any precedent for anything other than agreeing with the api-wg on their assessment of effectively non-impactful minor changes20:33
ttx#startvote Should that conflict be solved by taking Glance's or QA's approach? Glance, QA, abstain20:33
openstackBegin voting on: Should that conflict be solved by taking Glance's or QA's approach? Valid vote options are Glance, QA, abstain.20:33
openstackVote using '#vote OPTION'. Only your last vote counts.20:33
mordredfungi: ++20:33
flaper87#vote Glance20:33
mordred#vote Glance20:33
dhellmann#vote Glance20:33
fungi#vote Glance20:33
mtreinish#vote QA20:34
dtroyer#vote Glance20:34
EmilienM#vote Glance20:34
sdague#vote abstain20:34
ttx#vote abstain20:34
dims_#vote Glance20:34
*** lamt has quit IRC20:34
ttx(would rather come up with a precedent but understand why its not necessarily desirable here)20:34
sdaguettx: you can't not though20:35
dtroyersdague: sure, the precedent includes the amount of (non)breakage potential too20:35
ttxok, 30 more seconds20:35
sdaguedtroyer: that's fine, like I said a rather large amount of success codes are non HTTP pure20:35
* mugsie will bet this *will* be used as an example of a change that was allowed in the future20:36
dtroyersdague: right.  and a large number of thouse would be painful, so any precedent doesn't apply20:36
sdaguewe've had specs in Nova to go clean those up, which we've kept pushing back on because it's a lot of churn for not much clear value20:36
ttx#endvote20:36
openstackVoted on "Should that conflict be solved by taking Glance's or QA's approach?" Results are20:36
openstackQA (1): mtreinish20:36
openstackGlance (7): dims_, fungi, mordred, dhellmann, dtroyer, flaper87, EmilienM20:36
openstackabstain (2): ttx, sdague20:36
*** lamt has joined #openstack-meeting20:36
ttxmugsie: doesn't prevent anyone from re-raising it to TC20:36
sdaguettx: it doesn't20:36
sdaguebut it won't be20:36
fungiit sets a precedent that backward compatibility rules are open to interpretation in some cases20:37
sdagueit's fine that was the decision, but please don't pretend teams won't self censor on it20:37
mtreinishfungi: which I think is a step in the wrong direction20:37
mordredand that the API-WG should be consulted when they are open to interp as well20:37
mtreinishfungi: the apis change enough as it is20:37
ttx#info <mordred> ttx: glance talked to the API-WG - the QA team was appropriately conservative20:38
ttxok, next topic20:38
*** csomerville has joined #openstack-meeting20:38
ttx#topic Deprecate postgresql in OpenStack20:38
*** openstack changes topic to "Deprecate postgresql in OpenStack (Meeting topic: tc)"20:38
ttx#link https://review.openstack.org/42788020:38
ttxOn this one I was wondering if we can really use that 8% figure to say that "the ecosystem has settled on MySQL as the backend"20:38
ttxthat user survey metric is a bit weird, since 24% say they use MongoDB20:38
sdaguettx: because of ceilometer, right?20:39
flaper87ttx: telemetry?20:39
fungiand also of that 8% only half were apparently describing production environments?20:39
ttxAlso Xen/Xenserver represents 6% of Nova deployments... has the ecosystem settled on KVM ?20:39
ttxsdague: 24% of deployments using ceilometer ?20:39
* ttx looks20:39
fungii'm more concerned that we have fairly major distributions (suse and huawei) deploying with postgresql by default instead of mysql20:40
ttxit feels like the backlash is not coming from a vocal minority as much as I expected it20:40
fungiand curious to know what impact this would have on them20:40
*** emagana has joined #openstack-meeting20:40
dtroyerfungi: I'm curious what they've seen when there has been so little testing as it is on pg20:41
ttxsdague: you're right, probably comes from Ceilometer 60%20:41
*** armax has joined #openstack-meeting20:41
*** rfolco has joined #openstack-meeting20:41
mtreinishdtroyer: yeah, I'm curious about that too20:41
EmilienMin TripleO, we use MongoDB with Zaqar messaging20:41
sdaguefungi: yeh, it seems like products by suse, huawei, and windriver are based on pg, but I've never seen an organic instance in the operator community based on that20:41
edleafeWhile not an API, this also seems like a breaking change20:41
*** cody-somerville has quit IRC20:41
*** rfolco has quit IRC20:41
gordcdtroyer: tbh, there isn't much breakage. the rare times we notice issues, we'll just patch it upstream.20:41
ttxdoes anyone know what CERN is using ? Tim sounded like he would rather keep pg20:42
dims_fungi : we will need some time to find the dev teams in there and ask them20:42
dtroyergordc: how hard is it to identify that as a DB issue?  or are you good enough at it by now to see it quickly?20:42
sdaguettx: galera I was pretty sure20:42
EmilienMttx: mysql AFIK20:42
fungisdague: ftr, i understand there is a very large telco in europe basing their public cloud on huawei's distribution at least (they said as much in either a keynote or a board meeting, maybe both)20:42
ttxanyway, I think that shouldn't block our decision -- but I think it calls for a deprecation period20:42
edleafeIt's interesting that patching issues like this are acceptable, but patching a minor API success code change causes so much concern20:42
mordredfungi: yes. I have an account on it20:42
gordcdtroyer: i don't actually manage the product stuff so i can't give you accurate details on how quickly it gets identified20:43
ttxat the very minimum20:43
dtroyerI think the step of deprecating pg is necessary to either move forward with officially unsupporting it or to rally (again) the support required to properly maintain it20:43
gordcdtroyer: we're not tracking master so we really only notice things when we start pulling in update for next version20:43
ttxi.e. we would not intentionally scrap pg-compatibilty code until +1year20:43
sdaguettx: but we should definitely ensure it's not really in docs and the like20:43
mordredyah. I don't think removal without a full and conservative deprecation cycle is an option20:44
sdaguebecause right now there is implied support from upstream20:44
dtroyergordc: ok, so given the lag from master to distro, the removal of most pg jobs early in Ocata(-ish) only now gets to you?20:44
ttxsdague: well, if the other is "deprecated" it should not look good in docs indeed20:44
gordcdtroyer: we had pgsql test in ceilometer gate and we were noticed a pg break every 8 months or so... majority the db stuff we do in openstack is really generic.20:44
*** funzo has left #openstack-meeting20:44
dtroyergordc: ok, thx20:45
mugsiedtroyer: I would not assume that it would even on the radar of some distros yet20:45
ttxsdague: I agree the mismatch between support upstream and usage is distro is a bit weird20:45
dhellmannis the problem with supporting it the lack of folks to fix breaks, or is there a pressing technical need for something only available in mysql?20:45
gordcdtroyer: i can't recall how many issues reached downstream. when i asked, they gave me 3 examples of them patching upstream to fix pgsql20:45
edleafedhellmann: the former20:45
dhellmannedleafe : ok, because I've heard both arguments20:45
mordrededleafe: I'd say both actually20:45
mordredI think the reason I'm advocating for us to consider this is so that we can consider _not_ doing really generic database stuff20:45
dhellmannmordred : "pressing"?20:46
ttxTheoretical: if someone shows up and fixes PG support and works in QA team to support it, would we reverse the decision ?20:46
mordrednothing is pressing20:46
mordredopenstack has worked for years20:46
*** krtaylor has quit IRC20:46
sdaguedhellmann: from my point of view the problem is the extra overhead of "oh, we'd like to do utf8 right on these fields"20:46
dhellmannright, ttx phrased my question more directly20:46
sdague"oh, wth does pg do there? do we have to care?"20:46
sdaguefeature dies20:46
mordredyup20:46
mordredsdague: ++20:46
mordredthere's a ton of db improvement that dies on the vine20:46
dhellmannI am surprised that unicode is even something we have to deal with. Doesn't sqlalchemy do that?20:46
dtroyerttx: we've seen that for short periods before, how do we gauge long-term commitment?20:46
edleafemordred: the impetus was lack of support. Once we consider dropping it, then the possibilities of MySQL-centric stuff start to bloom20:47
sdaguedhellmann: no20:47
dhellmannffs20:47
mordreddtroyer: unicode is execptionally difficult to get right20:47
mordredgah20:47
*** ijw has joined #openstack-meeting20:47
mordreddhellmann: ^^ sorry20:47
*** armax_ has joined #openstack-meeting20:47
*** armax has quit IRC20:47
*** armax_ is now known as armax20:47
sdaguethe db engine is really important20:47
sdagueespecially if you are trying to index things for search20:47
ttxhappens that databses are hard to abstract after all20:47
mordred++20:47
sdaguethere is this assumption that sqla and oslo.db abstract the db20:47
sdaguethey do not20:47
bastafidliedleafe: ++20:47
sdaguethey provide some convenience functions20:48
gordci mention this on patch... but breaking something that works for some hypothetical improvements is kinda sketchy.20:48
sdagueand if you write some thing in ormish ways, some common 80% cases are made to look the same20:48
*** lamt has quit IRC20:48
ttxgordc: devil's advocate: in openstack we say that what's not tested is broken20:48
dhellmanngordc : I'm hearing a very specific improvement in non-ascii text support20:48
ttxI'm more concerned about the lack of testing or resources to work on it20:49
gordcttx: fair enough.20:49
fungigordc: would you object to proposed model/schema changes that improved performance in mysql but worsened performance in postgresql (or vice versa)?20:49
EmilienMttx: right, it seems like a very few (1 or 2) people actually maintain it20:49
*** chris_morrell has joined #openstack-meeting20:49
dhellmannttx: the question in my mind is whether we phrase the deprecation as reversible if support shows up, or if we say it's settled once and for all20:49
gordcfungi: nope. i think that'd be good.20:50
ttxgordc: I'm saying "devil's advocate" because my personal preference on this is that we should find a way to make it work20:50
fungijust curious whether we need some actual examples of beneficial changes we've avoided/abandoned because they'll impair one specific backend20:50
dims_how much deprecation period are we looking at?20:50
*** Patifa has quit IRC20:50
gordcttx: i'd prefer a periodic check to see actually validate pgsql is unmaintained20:50
stevemarthis is a *very* liberal use of our deprecation policy :\20:51
ttxdhellmann: well... deprecation will not actively break, it's more of a statement that we'll start actively breaking pG by removing code or adding MySQl-specific stuff by one year20:51
dtroyerfungi: I would think that would help some decision makers somewhere know (and work on their upstream mgmt)  if they want to fund support20:51
gordcor if it's just  working and nothing pgsql is being done.20:51
*** dmorita has joined #openstack-meeting20:51
ttxso it's easily reversed if we can be convinced20:51
ttxbut as dtroyer said, would take a lot to convince it's strategic involvement and not purely tactical20:51
dhellmannttx: right, but if someone comes along offering to do support and their work is going to be turned away because we don't want that work, we should just say that up front20:51
sdaguemy concern about all of this, is the same bind we get into with "this does't work" "oh we need people to support it"20:51
mordredttx: I think that's a great way to phrase it - it would also give folks a time to work up things like what fungi is talking about20:51
sdaguebecause it's not really true, we need maintainers20:51
sdaguepeople that are proactively on top of things20:52
dtroyersdague: ++20:52
*** kristian__ has joined #openstack-meeting20:52
mtreinishsdague: ++20:52
sdaguebecause, what happens with just the "raise hands to support" is someone else already burdened in the community has to own the maintenance20:52
dtroyerand this is one way to let our contributing companie know where they need to pay attention20:52
smcginnisOne concern would be if pg goes away, we add some mysql specific functionality, then someone shows up and wants to maintain and add back in pg support.20:52
ttxsdague: yes as I said it would take a lot to convince us that PG is actually maintained20:52
*** kristian__ has quit IRC20:52
smcginnisIt will be much more difficult then.20:52
sdaguesmcginnis: it will be20:52
*** kristian__ has joined #openstack-meeting20:52
sdaguebecause we decided not to burden existing contributors with it20:53
*** donghao has joined #openstack-meeting20:53
sdagueso that they could focus on more important things for users20:53
sdagueit's all trade offs20:53
ttxsmcginnis: will be too late by then20:53
smcginnissdague: Yep, fair point. Just pointing that out with talk of keeping the door open for it.20:53
fungii'm also curious what "deprecation" would look like. should we rip out any postgresql deployment examples in master branches of install documentation at the start of the deprecation period, or at the end of it?20:53
dhellmannsmcginnis : right, that's another reason for us being clear if what we're really saying is that we are going to drop pg and not accept maintenance work20:53
ttxsmcginnis: we can only reverse that decision during the deprecation period, while we don't touch anything20:53
EmilienMsmcginnis: I second you. Also some companies might need to fork some projects to maintain pg support ... which wouldn't be cool either.20:53
smcginnisdhellmann: +120:53
sdagueand, it's fine to say that our resources should be spent on a db that is rarely used20:53
gordcjust curious, but how are we certain it's not maintained?20:53
dhellmanngordc : because people were not showing up to deal with breaks in the gate?20:54
dhellmannand that led to teams dropping the postgresql jobs from their gate20:54
dtroyerI think deprecation here means a) documenting the current state (untested), and b) waiting a period, sya a year, for the situation to change, and c) re-evaluating at the end of that period before allowing mysql-specific bits20:54
ttxand now it's probably broken but noone knows20:54
gordcdhellmann: i see. i didn't realise there were more. the pgsql we found was patched within 12 hours20:54
mordredyah - postgres has _consistently_ been ignored for YEARS20:54
mordredthis isn't like a recent thing20:54
mugsiefrom our projects perspective, every now and again, someone comes in to fix pg, gets a gate and leaves.20:54
dhellmanngordc : at this point only the telemetry team was gating, iiuc20:54
sdagueyeh, pretty clear the fact that we dropped pg from the gate an no one was there building alternative testing around it, means it's not maintained20:54
mordredmugsie: ++20:55
mugsiethen 6 months later something breaks, and we just drop the gate20:55
edleafemordred: so it's been deprecated, but we're now just owning up to it?20:55
gordcdhellmann: neutron i mentinoed they have periodic postgresql20:55
mordrededleafe: the openstack community has literallky never actually cared about postgres20:55
ttxok, I think we made progress. Let's discuss this F2F next week and I think we'll be able to make a call for Pike20:55
dhellmanngordc : a periodic job is not a gate job, though, right?20:55
*** dmorita has quit IRC20:55
mugsieand a periodic job is only as good as the people watching the results20:55
edleafemordred: it seems that enough people cared to create the tests in the first place20:56
sdagueand, more importantly, no one is getting ahead of things20:56
ttxsdague: ++20:56
edleafemordred: once they left, no one picked up the slack20:56
sdaguejust having a test job isn't maintaining anything20:56
ttxIt's reactive rather than proactive20:56
gordcdhellmann: right. i forgot what question was... if it's being gated on? it's not. :)20:56
mordrededleafe: that's how I define "community doesn't care"20:56
dhellmanngordc : right20:56
gordci'm just wondering if it's actually broken. :)20:56
*** reedip_1 has joined #openstack-meeting20:56
edleafemordred: and that's how I define effectively deprecated20:56
mordrededleafe: a random human helicoptering in to do work once and then going away does not equate to overall care and feeding20:56
mugsiewe (designate) actually do have a voting pg gate job right now20:56
mordrededleafe: totes20:56
mtreinishgordc: I don't see any periodic jobs with postgres in the name: http://status.openstack.org/openstack-health/#/?groupKey=build_name&searchProject=postgres20:56
mordrededleafe: oh - sorry - yes, I agree with you - I was just trying to agree more strongly20:56
edleafemordred: :)20:57
ttx#topic Open discussion20:57
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:57
gordcmtreinish: just going by what neutron said.20:57
ttxQuick couple of topics20:57
ttxWe'll skip the TC meeting next week due to PTG20:57
edleafeYeah, I'm just saying let's be honest about it20:57
*** mickeys has joined #openstack-meeting20:57
ttxand amrith raised the issue of the "OpenStack Clean" bot posting comments on unworthy changes20:57
ttx#link http://lists.openstack.org/pipermail/openstack-tc/2017-February/001333.html20:57
ttxWhile I generally agree with what it says, it feels like a slippery slope to have anonymous bots trolling on reviews20:57
*** donghao has quit IRC20:57
ttxAny opinion on that one ?20:57
mugsiettx: I think the account has been disabled20:57
gordcmtreinish: we dropped ours recently.20:57
dhellmannyes, that doesn't seem like the right answer there and I agree with disabling the bot20:57
ttxyes, but in a legal vacuum -- should we have a nobot policy ?20:58
ttxor only vetted bots ?20:58
EmilienMthe comments are really useless but don't hurt anyone though I agree with disabling the bot.20:58
mugsievetted only seems resonable20:58
dims_only infra approved bots20:58
*** reedip_1 has quit IRC20:58
ttxdims_: sounds good20:58
EmilienMdims_: yes, +120:58
mtreinishgordc: that link is going back a month20:58
mtreinishgordc: you can change the period20:58
dhellmannvetting bots that post seems like a reasonable standard20:58
dtroyersimilar to the 3rd party CI requirements?20:58
ttx#agreed Only infra-approved bots are allowed on Gerrit20:58
mtreinishttx: are we sure that's a bot? It's review here seems like a human: https://review.openstack.org/#/c/430164/20:58
ttxmtreinish: it's a human that repeats itself very often then20:59
notmynamehow is that done? sounds like a "Real Name" policy20:59
dhellmannmtreinish : maybe it was a bulk update20:59
* fungi isn't sure he wants the infra team burdened with vetting every single automated system which comments on reviews... there are hundreds already20:59
sdaguealso, bots aren't supposed to vote in CR20:59
ttxnotmyname: Turing test ?20:59
sdaguebots are only supposed to vote in V20:59
mugsienotmyname: we kind of have that with the CLA20:59
dhellmannfungi : ++20:59
smcginnisstackalytics ranking improvement bot?21:00
ttxnotmyname: if the bot can convince us it's human, it's probably good enough21:00
edleafesmcginnis: ha!21:00
fungimugsie: no idea how the cla has anything to do with code review comments though21:00
ttxand we are out of time...21:00
EmilienMttx: thx for chairing!21:00
ttxSee you all next week ?21:00
EmilienMo/21:00
ttxor almost all21:00
edleafeSee you in Atlanta!21:00
rosmaitathanks everyone!21:00
*** gordc has left #openstack-meeting21:00
ttx#endmeeting21:01
dhellmannsee you in Atlanta!21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Tue Feb 14 21:01:00 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-02-14-20.01.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-02-14-20.01.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-02-14-20.01.log.html21:01
*** mickeys has quit IRC21:01
mordrednotmyname: it's done not by active policing in any automated fashion - but by referring to it as an agreement when a misbehaving bot surfaces21:02
mordrednotmyname: kind of lke a "don't be a jerk" policy - you can't actually _implement_ it on an ongoing basis - but you can refer to it when someone does something that upsets a large number of people21:02
dims_++ mordred21:03
bswartzoh man if we have a "don't be a jerk" policy it won't just be bots that are affected...21:03
mordredbswartz: :)21:03
mordredbswartz: we _do_ have a don't be a jerk policy21:03
*** Patifa has joined #openstack-meeting21:03
dims_bswartz : :)21:03
mordredhttps://www.openstack.org/legal/community-code-of-conduct/21:04
mordredit's worded with way more words than "don't be a jerk" - but that's what it boils down to21:04
*** olaph has left #openstack-meeting21:04
bswartzgood to know21:04
bswartzthat link may come in handy in some discussions21:05
*** eharney has quit IRC21:06
*** donghao has joined #openstack-meeting21:08
*** kristian__ has quit IRC21:09
*** Patifa has quit IRC21:10
*** BobH has quit IRC21:12
*** HOS has quit IRC21:12
*** astarove has quit IRC21:12
*** itamaro has quit IRC21:12
*** shu-mutou has quit IRC21:12
*** donghao has quit IRC21:12
*** BobH has joined #openstack-meeting21:13
*** HOS has joined #openstack-meeting21:13
*** astarove has joined #openstack-meeting21:13
*** itamaro has joined #openstack-meeting21:13
*** shu-mutou has joined #openstack-meeting21:13
*** Patifa has joined #openstack-meeting21:15
*** BobH has quit IRC21:15
*** HOS has quit IRC21:15
*** astarove has quit IRC21:15
*** itamaro has quit IRC21:15
*** shu-mutou has quit IRC21:15
*** BobH has joined #openstack-meeting21:16
*** HOS has joined #openstack-meeting21:16
*** astarove has joined #openstack-meeting21:16
*** itamaro has joined #openstack-meeting21:16
*** shu-mutou has joined #openstack-meeting21:16
*** Patifa has quit IRC21:16
*** bastafidli has quit IRC21:19
*** jkilpatr has quit IRC21:20
*** diablo_rojo_phon has quit IRC21:20
*** eharney has joined #openstack-meeting21:20
*** bobmel has quit IRC21:22
*** julim has quit IRC21:23
*** jamesdenton has quit IRC21:25
*** krtaylor has joined #openstack-meeting21:27
*** jrobinson has joined #openstack-meeting21:28
*** raildo has quit IRC21:30
*** galstrom is now known as galstrom_zzz21:31
*** dmorita has joined #openstack-meeting21:32
*** askb has joined #openstack-meeting21:32
*** galstrom_zzz is now known as galstrom21:33
*** lamt has joined #openstack-meeting21:34
*** bastafidli has joined #openstack-meeting21:36
*** dmorita has quit IRC21:36
*** baoli has quit IRC21:43
*** baoli has joined #openstack-meeting21:44
*** rcernin has quit IRC21:44
*** dmorita has joined #openstack-meeting21:46
*** ashcrack has quit IRC21:50
*** pnavarro has quit IRC21:50
*** salv-orlando has joined #openstack-meeting21:51
*** dmorita has quit IRC21:53
*** fguillot has quit IRC21:58
*** FengShengqin1 has quit IRC21:59
*** jmckind has quit IRC22:02
*** FengShengqin1 has joined #openstack-meeting22:02
*** matrohon has quit IRC22:03
*** jkilpatr has joined #openstack-meeting22:03
*** ihrachys_ has joined #openstack-meeting22:03
*** sdake has quit IRC22:04
*** ykatabam has joined #openstack-meeting22:05
*** ihrachy__ has joined #openstack-meeting22:05
*** ihrachys_ has quit IRC22:05
*** sshnaidm|afk is now known as sshnaidm22:06
*** ihrachys has quit IRC22:06
*** lamt has quit IRC22:06
*** dimtruck is now known as zz_dimtruck22:06
*** jaugustine has quit IRC22:07
*** Patifa has joined #openstack-meeting22:08
*** dmorita has joined #openstack-meeting22:09
*** tonytan4ever has quit IRC22:10
*** lamt has joined #openstack-meeting22:11
*** yamamoto has joined #openstack-meeting22:12
*** dmorita has quit IRC22:13
*** thorst_ has quit IRC22:15
*** Sukhdev has joined #openstack-meeting22:21
*** lamt has quit IRC22:21
*** thorst_ has joined #openstack-meeting22:24
*** lamt has joined #openstack-meeting22:24
*** dmorita has joined #openstack-meeting22:25
*** krtaylor has quit IRC22:26
*** bastafidli has quit IRC22:27
*** thorst_ has quit IRC22:28
*** sdake has joined #openstack-meeting22:28
*** bastafidli has joined #openstack-meeting22:29
*** dbecker has quit IRC22:30
*** FengShengqin1 has quit IRC22:30
*** sdake has quit IRC22:30
*** ihrachy__ has quit IRC22:30
*** ihrachys has joined #openstack-meeting22:31
*** sdake has joined #openstack-meeting22:31
*** zz_dimtruck is now known as dimtruck22:33
*** ihrachys_ has joined #openstack-meeting22:33
*** luzC- has joined #openstack-meeting22:34
*** imcsk8_ has joined #openstack-meeting22:34
*** waj334_ has joined #openstack-meeting22:34
*** jamesmcarthur_ has joined #openstack-meeting22:34
*** alexpilo_ has joined #openstack-meeting22:34
*** izaakk_ has joined #openstack-meeting22:35
*** xek_ has joined #openstack-meeting22:35
*** gouthamr has quit IRC22:35
*** bryan_att_ has joined #openstack-meeting22:35
*** dasanind_ has joined #openstack-meeting22:36
*** ianw has quit IRC22:36
*** sdake_ has joined #openstack-meeting22:36
*** beekneemech has joined #openstack-meeting22:36
*** BobH has quit IRC22:36
*** cebruns__ has joined #openstack-meeting22:37
*** annegentle has quit IRC22:37
*** doffm has joined #openstack-meeting22:37
*** Adri2000_ has joined #openstack-meeting22:37
*** egon_ has joined #openstack-meeting22:38
*** tonyb_ has joined #openstack-meeting22:38
*** rmcadams_ has joined #openstack-meeting22:39
*** gus_ has joined #openstack-meeting22:39
*** annegentle has joined #openstack-meeting22:40
*** kozhukalov_ has joined #openstack-meeting22:40
*** eharney has quit IRC22:40
*** ihrachys_ has quit IRC22:40
*** dgonzalez_ has joined #openstack-meeting22:40
*** jraim_ has joined #openstack-meeting22:40
*** dlundquist_ has joined #openstack-meeting22:40
*** sballe__ has joined #openstack-meeting22:40
*** ameade_ has joined #openstack-meeting22:41
*** dims has joined #openstack-meeting22:41
*** terryw has joined #openstack-meeting22:41
*** HenryG_ has joined #openstack-meeting22:41
*** laurelm_ has joined #openstack-meeting22:41
*** mtreinish_ has joined #openstack-meeting22:41
*** sdake__ has joined #openstack-meeting22:41
*** yantarou_ has joined #openstack-meeting22:41
*** saggi- has joined #openstack-meeting22:41
*** dansmith_ has joined #openstack-meeting22:41
*** mkoderer___ has joined #openstack-meeting22:41
*** mriedem has quit IRC22:41
*** Swami has quit IRC22:41
*** sdake has quit IRC22:42
*** ihrachys has quit IRC22:42
*** jkilpatr has quit IRC22:42
*** pvaneck has quit IRC22:42
*** martines has quit IRC22:42
*** sshnaidm has quit IRC22:42
*** rmcadams has quit IRC22:42
*** ayoung has quit IRC22:42
*** bnemec has quit IRC22:42
*** dims_ has quit IRC22:42
*** HenryG has quit IRC22:42
*** doffm_ has quit IRC22:42
*** ircuser-1 has quit IRC22:42
*** mtreinish has quit IRC22:42
*** xek has quit IRC22:42
*** efried has quit IRC22:42
*** saggi has quit IRC22:42
*** alexpilotti has quit IRC22:42
*** cebruns_ has quit IRC22:42
*** egon has quit IRC22:42
*** dgonzalez has quit IRC22:42
*** lennyb has quit IRC22:42
*** imcsk8 has quit IRC22:42
*** dasanind has quit IRC22:42
*** jamesmcarthur has quit IRC22:42
*** izaakk has quit IRC22:42
*** dlundquist has quit IRC22:42
*** waj334 has quit IRC22:42
*** sballe_ has quit IRC22:42
*** kozhukalov has quit IRC22:42
*** ameade has quit IRC22:42
*** jraim has quit IRC22:42
*** laurelm has quit IRC22:42
*** dansmith has quit IRC22:42
*** luzC has quit IRC22:42
*** stevemar has quit IRC22:42
*** sankarshan has quit IRC22:42
*** yantarou has quit IRC22:42
*** gus has quit IRC22:42
*** Adri2000 has quit IRC22:42
*** karthikp_ has quit IRC22:42
*** mkoderer__ has quit IRC22:42
*** tonyb has quit IRC22:42
*** bryan_att has quit IRC22:42
*** otherwiseguy has quit IRC22:42
*** greghaynes has quit IRC22:42
*** haleyb has quit IRC22:42
*** sshank has quit IRC22:42
*** vkramskikh has quit IRC22:42
*** fungi has quit IRC22:42
*** darvon has quit IRC22:42
*** dgonzalez_ is now known as dgonzalez22:42
*** yantarou_ is now known as yantarou22:42
*** luzC- is now known as luzC22:42
*** mtreinish_ is now known as mtreinish22:42
*** dansmith_ is now known as dansmith22:42
*** laurelm_ is now known as laurelm22:42
*** sankarshan has joined #openstack-meeting22:43
*** waj334_ is now known as waj33422:43
*** jamesmcarthur_ is now known as jamesmcarthur22:43
*** stevemar has joined #openstack-meeting22:43
*** izaakk_ is now known as izaakk22:43
*** bastafidli has quit IRC22:43
*** darvon has joined #openstack-meeting22:44
*** kozhukalov_ is now known as kozhukalov22:44
*** dlundquist_ is now known as dlundquist22:44
*** bryan_att_ is now known as bryan_att22:44
*** sdake_ has quit IRC22:44
*** jraim_ is now known as jraim22:45
*** sballe__ is now known as sballe_22:45
*** karthikp_ has joined #openstack-meeting22:45
*** dasanind_ is now known as dasanind22:45
*** rmcadams_ is now known as rmcadams22:45
*** dlundquist has quit IRC22:46
*** annegentle has quit IRC22:46
*** Adri2000_ has quit IRC22:46
*** xek_ has quit IRC22:46
*** luzC has quit IRC22:46
*** baoli has quit IRC22:46
*** ijw has quit IRC22:46
*** Leo_ has quit IRC22:46
*** fmccrthy has quit IRC22:46
*** TheJulia has quit IRC22:46
*** larainema has quit IRC22:46
*** jaypipes has quit IRC22:46
*** edleafe has quit IRC22:46
*** arxcruz has quit IRC22:46
*** zigo has quit IRC22:46
*** fernnest has quit IRC22:46
*** afazekas has quit IRC22:46
*** ajo has quit IRC22:46
*** morgan has quit IRC22:46
*** zxiiro has quit IRC22:46
*** amitry has quit IRC22:46
*** nonameentername has quit IRC22:46
*** med_ has quit IRC22:46
*** castulo has quit IRC22:46
*** andreaf has quit IRC22:46
*** devananda has quit IRC22:46
*** lyarwood has quit IRC22:46
*** galstrom has quit IRC22:46
*** clayton has quit IRC22:46
*** swifterdarrell has quit IRC22:46
*** irenab has quit IRC22:46
*** sam64 has quit IRC22:46
*** mugsie_ has quit IRC22:46
*** tris has quit IRC22:46
*** dalvarez has quit IRC22:46
*** mmotiani has quit IRC22:46
*** joanna has quit IRC22:46
*** darrenc has quit IRC22:46
*** homerp has quit IRC22:46
*** mrhillsman has quit IRC22:46
*** mattoliverau has quit IRC22:46
*** ChrisPriceAB has quit IRC22:46
*** sweston has quit IRC22:46
*** vipuls has quit IRC22:46
*** margaret has quit IRC22:46
*** dpyzhov has quit IRC22:46
*** smurke- has quit IRC22:46
*** marios has quit IRC22:46
*** jianghuaw has quit IRC22:46
*** pcarver has quit IRC22:46
*** rderose has quit IRC22:46
*** njohnston has quit IRC22:46
*** mugsie_ has joined #openstack-meeting22:46
*** tonyb_ is now known as tonyb22:46
*** afazekas has joined #openstack-meeting22:46
*** njohnston has joined #openstack-meeting22:46
*** irenab has joined #openstack-meeting22:46
*** lyarwood has joined #openstack-meeting22:46
*** med_ has joined #openstack-meeting22:46
*** galstrom has joined #openstack-meeting22:47
*** jaypipes has joined #openstack-meeting22:47
*** devananda has joined #openstack-meeting22:47
*** homerp has joined #openstack-meeting22:47
*** swifterdarrell has joined #openstack-meeting22:47
*** med_ is now known as Guest390422:47
*** luzC has joined #openstack-meeting22:47
*** edleafe has joined #openstack-meeting22:47
*** castulo has joined #openstack-meeting22:48
*** mrhillsman has joined #openstack-meeting22:48
*** pvaneck has joined #openstack-meeting22:48
*** greghaynes has joined #openstack-meeting22:49
*** fungi has joined #openstack-meeting22:49
*** ircuser-1 has joined #openstack-meeting22:49
*** lennyb has joined #openstack-meeting22:50
*** ameade_ is now known as ameade22:50
*** sshnaidm has joined #openstack-meeting22:50
*** martines has joined #openstack-meeting22:51
*** jkilpatr has joined #openstack-meeting22:51
*** ayoung has joined #openstack-meeting22:51
*** efried has joined #openstack-meeting22:51
*** ChrisPriceAB has joined #openstack-meeting22:52
*** haleyb has joined #openstack-meeting22:52
*** jianghuaw has joined #openstack-meeting22:52
*** baoli has joined #openstack-meeting22:52
*** zigo has joined #openstack-meeting22:52
*** xek_ has joined #openstack-meeting22:52
*** ijw has joined #openstack-meeting22:52
*** Leo_ has joined #openstack-meeting22:52
*** arxcruz has joined #openstack-meeting22:52
*** ajo has joined #openstack-meeting22:52
*** nonameentername has joined #openstack-meeting22:52
*** andreaf has joined #openstack-meeting22:52
*** clayton has joined #openstack-meeting22:52
*** sam64 has joined #openstack-meeting22:52
*** tris has joined #openstack-meeting22:52
*** dalvarez has joined #openstack-meeting22:52
*** darrenc has joined #openstack-meeting22:52
*** mattoliverau has joined #openstack-meeting22:52
*** vipuls has joined #openstack-meeting22:52
*** smurke- has joined #openstack-meeting22:52
*** marios has joined #openstack-meeting22:52
*** pcarver has joined #openstack-meeting22:52
*** rderose has joined #openstack-meeting22:52
*** sweston has joined #openstack-meeting22:53
*** zigo is now known as Guest2705722:54
*** esberglu has quit IRC22:54
*** larainema has joined #openstack-meeting22:54
*** esberglu has joined #openstack-meeting22:54
*** margaret has joined #openstack-meeting22:55
*** dpyzhov has joined #openstack-meeting22:56
*** annegentle has joined #openstack-meeting22:56
*** fmccrthy has joined #openstack-meeting22:57
*** zxiiro has joined #openstack-meeting22:57
*** TheJulia has joined #openstack-meeting22:57
*** esberglu has quit IRC22:58
*** amitry has joined #openstack-meeting22:59
*** dlundquist has joined #openstack-meeting23:00
*** dmorita has quit IRC23:00
*** Adri2000 has joined #openstack-meeting23:01
*** dmorita has joined #openstack-meeting23:03
*** iyamahat has quit IRC23:04
*** gyee has joined #openstack-meeting23:06
*** ianychoi_ is now known as ianychoi23:06
*** knangia has quit IRC23:07
*** esberglu has joined #openstack-meeting23:07
*** knangia has joined #openstack-meeting23:07
*** baoli has quit IRC23:08
*** tommylikehu_ has joined #openstack-meeting23:08
*** ijw has quit IRC23:08
*** diablo_rojo has quit IRC23:09
*** mickeys has joined #openstack-meeting23:09
*** rbak has quit IRC23:09
*** esberglu has quit IRC23:11
*** mickeys has quit IRC23:13
*** galstrom is now known as galstrom_zzz23:13
*** cloudrancher has joined #openstack-meeting23:14
*** cloudrancher has quit IRC23:14
*** cloudrancher has joined #openstack-meeting23:14
*** joanna has joined #openstack-meeting23:15
*** tommylikehu_ has quit IRC23:16
*** morgan_ has joined #openstack-meeting23:16
*** thorst_ has joined #openstack-meeting23:19
*** thorst_ has quit IRC23:20
*** claudiub has quit IRC23:20
*** egon_ is now known as egon23:21
*** jaypipes has quit IRC23:22
*** VW_ has joined #openstack-meeting23:22
*** sdague has quit IRC23:22
*** Julien-zte has joined #openstack-meeting23:23
*** kenji-i has joined #openstack-meeting23:25
*** VW has quit IRC23:25
*** VW_ has quit IRC23:26
*** chris_morrell has quit IRC23:27
*** tommylikehu_ has joined #openstack-meeting23:27
*** Julien-zte has quit IRC23:28
*** tommylikehu_ has quit IRC23:31
*** bobmel has joined #openstack-meeting23:34
*** bobh_ has quit IRC23:36
*** dimtruck is now known as zz_dimtruck23:38
*** bobmel has quit IRC23:39
*** zz_dimtruck is now known as dimtruck23:39
*** ianw has joined #openstack-meeting23:41
*** sshnaidm has quit IRC23:41
*** dmorita has quit IRC23:44
*** Swami has joined #openstack-meeting23:46
*** dmorita has joined #openstack-meeting23:46
*** Swami_ has joined #openstack-meeting23:46
*** dmorita has quit IRC23:47
*** sshnaidm has joined #openstack-meeting23:47
*** salv-orlando has quit IRC23:47
*** sshnaidm is now known as sshnaidm|off23:48
*** gouthamr has joined #openstack-meeting23:51
*** Patifa has quit IRC23:51
*** sdake__ is now known as sdake23:52
*** mriedem has joined #openstack-meeting23:53
*** Leo_ has quit IRC23:55
*** dmorita has joined #openstack-meeting23:58
*** reedip_1 has joined #openstack-meeting23:59

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