Tuesday, 2018-05-08

*** mjturek has quit IRC00:00
*** rpioso is now known as rpioso|afk00:07
*** hemna_ has quit IRC00:08
*** longkb has joined #openstack-meeting00:23
*** Bonjourm8 has quit IRC00:23
*** Dinesh_Bhor has joined #openstack-meeting00:30
*** julim has quit IRC00:34
*** cloudrancher has joined #openstack-meeting00:35
*** felipemonteiro__ has joined #openstack-meeting00:39
*** Nel1x has quit IRC00:48
*** longkb1 has joined #openstack-meeting00:53
*** diman has joined #openstack-meeting00:54
*** longkb has quit IRC00:55
*** diman has quit IRC00:58
*** Nel1x has joined #openstack-meeting01:03
*** longkb1 has quit IRC01:13
*** kaisers_ has joined #openstack-meeting01:13
*** longkb has joined #openstack-meeting01:13
*** kaisers has quit IRC01:16
*** cloudrancher has quit IRC01:19
*** Nel1x has quit IRC01:20
*** jesusaur has quit IRC01:22
*** jesusaur has joined #openstack-meeting01:24
*** Bonjourm8 has joined #openstack-meeting01:31
*** Nel1x has joined #openstack-meeting01:34
*** felipemonteiro__ has quit IRC01:35
*** bkopilov_ has quit IRC01:35
*** bkopilov__ has quit IRC01:35
*** sapd has joined #openstack-meeting01:40
*** lkwan_ has joined #openstack-meeting01:52
*** carl_baldwin_ has quit IRC01:55
*** hongbin has joined #openstack-meeting02:02
*** markstur_ has quit IRC02:09
*** Bonjourm8 has quit IRC02:11
*** psachin` has joined #openstack-meeting02:12
*** longkb1 has joined #openstack-meeting02:14
*** longkb has quit IRC02:17
*** yamamoto has joined #openstack-meeting02:17
*** yamamoto has quit IRC02:22
*** ricolin has joined #openstack-meeting02:22
*** brault has joined #openstack-meeting02:31
*** shu-mutow-AWAY is now known as shu-mutow02:35
*** brault has quit IRC02:36
*** hongbin_ has joined #openstack-meeting02:37
*** lkwan__ has joined #openstack-meeting02:37
*** longkb has joined #openstack-meeting02:38
*** longkb1 has quit IRC02:39
*** felipemonteiro__ has joined #openstack-meeting02:39
*** hongbin has quit IRC02:40
*** kevzha01 has joined #openstack-meeting02:44
*** kevzha01__ has quit IRC02:46
*** esberglu has joined #openstack-meeting02:48
*** esberglu has quit IRC02:48
*** liyi has joined #openstack-meeting02:48
*** bkopilov_ has joined #openstack-meeting02:55
*** bkopilov__ has joined #openstack-meeting02:56
*** felipemonteiro__ has quit IRC02:58
*** VW has joined #openstack-meeting02:58
*** kevzha01 is now known as kevinz03:00
*** yamamoto has joined #openstack-meeting03:04
*** zhhuabj has quit IRC03:05
*** hoangcx has joined #openstack-meeting03:05
*** gcb has joined #openstack-meeting03:08
*** hemna_ has joined #openstack-meeting03:14
*** zhhuabj has joined #openstack-meeting03:18
*** epico has joined #openstack-meeting03:21
*** yamamoto has quit IRC03:31
*** VW has quit IRC03:32
*** VW has joined #openstack-meeting03:32
*** VW has quit IRC03:37
*** niraj_singh has joined #openstack-meeting03:43
*** epico has quit IRC03:43
*** lpetrut has joined #openstack-meeting03:43
*** sridharg has joined #openstack-meeting03:48
*** sapd has quit IRC03:48
*** gyee has quit IRC03:48
*** janki has joined #openstack-meeting03:50
*** cloudrancher has joined #openstack-meeting03:52
*** markstur has joined #openstack-meeting03:54
*** hongbin_ has quit IRC03:55
*** tpatil has joined #openstack-meeting03:57
*** cloudrancher has quit IRC03:57
*** sagara has joined #openstack-meeting03:59
*** markstur has quit IRC03:59
samPHi all for masakari04:00
samP#startmeeting masakari04:00
openstackMeeting started Tue May  8 04:00:39 2018 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.04:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:00
*** openstack changes topic to " (Meeting topic: masakari)"04:00
openstackThe meeting name has been set to 'masakari'04:00
samPHi all..04:00
*** longkb has quit IRC04:01
*** hoangcx has quit IRC04:01
samPLet's start04:01
samP#topic High priority items04:01
*** openstack changes topic to "High priority items (Meeting topic: masakari)"04:01
*** longkb has joined #openstack-meeting04:01
samP(1) Change the meeting time04:01
*** hoangcx has joined #openstack-meeting04:01
lkwan__It will be nice if the meeting can be started 1 hour earlier?04:02
samPwe had a mail discussion to change the meeting time to 03:00 UTC.04:02
samPlkwan__: I am OK with that, much earlier also possible04:02
lkwan__03:00 UTC is fine04:03
samPseems like most of us are OK with 03:00UTC which is 12:00 JST04:04
samPI will propose the patch for this, and you still may put your comment that04:04
*** epico has joined #openstack-meeting04:04
samPAny High priority items?04:05
samPOtherwise, let's go to BUG/Patches discussion04:05
lkwan__status of openstacksdk?04:05
samPlkwan__: let's talk about that in next topic04:05
samP#topic Critical Bugs and Patches04:06
*** openstack changes topic to "Critical Bugs and Patches (Meeting topic: masakari)"04:06
samPOK, openstacksdk released new version..04:06
tpatil0.13.0 is released04:06
samPwhich will fix most of our problems04:06
lkwan__is the type we are waiting for is there?04:07
tpatilWe will need to update patch https://review.openstack.org/#/c/546492/14/requirements.txt to use the new version04:07
patchbotpatch 546492 - masakari-monitors - [WIP] Update for upcoming openstacksdk changes to ...04:07
tpatilBut IMO, we need 0.130.0 for both  lower constraints and regular test jobs04:08
samPcurrent lower is openstacksdk===0.11.204:09
tpatillower constraints jobs : https://review.openstack.org/#/c/555823/, should also use 0.13.004:09
patchbotpatch 555823 - masakari-monitors - add lower-constraints job04:09
samPtpatil: humm.. #555823 this should update04:11
*** fnaval has quit IRC04:11
samPI will discuss this with rkhonjo/takahara about #54649204:12
tpatilsamP: OK04:12
Dinesh_BhorI think openstack BOT job will propose the patch for bumping openstacksdk version in masakari-monitors if its not already proposed then04:13
tpatilDinesh_Bhor: it will not becoz openstacksdk is not included in requirements.txt of masakari-monitors04:13
samPDinesh_Bhor: really? does it update to latest version?04:14
samPtpatil: same understanding here04:14
Dinesh_Bhortpatil: ohh04:14
tpatilopenstacksdk library is added in above patch 54649204:14
patchbothttps://review.openstack.org/#/c/546492/ - masakari-monitors - [WIP] Update for upcoming openstacksdk changes to ...04:14
Dinesh_BhorYes, correct. Then we need to update it manually.04:14
samPDinesh_Bhor: tpatil: thanks04:14
lkwan__how about this... https://review.openstack.org/#/c/536668/04:15
patchbotpatch 536668 - masakari-monitors - Change masakari service-type from 'ha' to 'instanc...04:15
*** lpetrut has quit IRC04:15
Dinesh_Bhorlkwan__: I will confirm about this once we have newer openstacksdk in masakari-monitors04:16
samPlkwan__: I agree with tpatil's comment on this..04:16
lkwan__Just want to make it clear... will the new sdk fix this https://bugs.launchpad.net/python-masakariclient/+bug/175604704:17
openstackLaunchpad bug 1756047 in python-masakariclient "masakari command failed due to os-service-type1.2.0" [Critical,Confirmed]04:17
samPLet's fix #546492 and see whether we still need 53666804:17
*** gyee has joined #openstack-meeting04:17
tpatillkwan__: Yes, it will fix this issue though I haven't yet tested it by myself04:18
samPOK then, let's review and merge #546492 asap, then we can confirm does it fix bug/1756047.04:20
samPI will update #546492 after this meeting.04:20
tpatilsamP: Ok, Thanks04:21
samPI would like to fix this sdk issue assp and release a new version of masakariclient04:21
samPAny other bugs or patches to discuss?04:22
lkwan__same one.. it will be nice if some of us can review https://review.openstack.org/#/c/534958/04:22
patchbotpatch 534958 - masakari-monitors - Introspective Instance Monitoring through QEMU Gue...04:22
lkwan__Ken and Greg are waiting for some replies the status04:23
lkwan__and I communicated that mid May is the target date.04:23
lkwan__is the date still ok?04:23
*** gyee has quit IRC04:24
samPlkwan__: sure, I will put my comments today.04:24
tpatilsamP: First we will need to merge the specs : https://review.openstack.org/#/c/469070/04:24
patchbotpatch 469070 - masakari-specs - Introspective instance monitoring.04:24
lkwan__thanks, I will be on irc tomorrow and follow up as much as possible.04:24
samPtpatil: correct04:25
tpatillkwan__: I have started reviewing the implementation04:25
tpatillkwan__: I have one request, is it possible to split this single patch?04:26
samPlkwan__: thanks for spec update. I will take a one last look and approve it.04:26
samPDinesh_Bhor: thanks for spc fix04:27
lkwan__taptil, any suggestion how to split?04:27
lkwan__the main part is qemu_utils.py04:27
lkwan__it is not that big and I will try to be irc tomorrow to answer questions if this help.04:30
tpatilMaybe you can split it into 3 patches, #1: basic service related code including config options, #2: monitoring instances, #3: sending notifications04:30
samPlkwan__: that's really helpful. thanks04:32
lkwan__taptil, I will put comments on the README. For the 3 parts you mentioned... so that you can read it easier.04:33
*** anilvenkata has joined #openstack-meeting04:34
samPI will put my comment on current patch. As tpatil suggest it is easy to review if you split this patch, however let see how it goes.04:35
tpatillkwan__: I will appreciate if you can split the patches but if you don't have time, I'm ok to review this single patch, the only concern is it will take lot of time for review.04:35
samPlkwan__: Just one question, have you already test this?04:36
lkwan__many times04:36
lkwan__and very stable04:36
samPlkwan__: great..thanks04:36
lkwan__the notification is very simple04:36
lkwan__but it is within the same file, then why it is very hard to split it out04:37
lkwan__just one function for notification04:37
tpatilAre you filtering instances based on metadata as mentioned in specs?04:37
lkwan__we only listen to those with qemu04:38
*** links has joined #openstack-meeting04:38
lkwan__and filter them out04:38
tpatilI couldn't find it in the code, I will take a closer look later.04:39
lkwan___hasQemuGuestAgent function04:40
lkwan__on qemu_utils.py04:40
lkwan__based on whether this is a sock or not04:40
tpatilOk, Thanks04:42
samPlkwan__: tpatil: thanks04:42
samPlkwan__: we might contact you for more details, on IRC or dev-ml04:43
lkwan__yes... will be on IRC to answer questions.04:43
samPlkwan__: thanks.04:44
lkwan__if I am taking a break.. for the time difference... I will indicate as well04:44
samPlkwan__: sure.. thanks04:44
lkwan__thanks samP , tpatil,  Dinesh and others.04:45
samPAny other bugs/patches to discuss?04:45
samPlkwan__: NP04:45
samPIf any bring the at the end of this meeting..04:45
samP#topic Discussion points04:46
*** openstack changes topic to "Discussion points (Meeting topic: masakari)"04:46
samP(1) Horizon Plugin04:46
*** epico has quit IRC04:46
samPSice sdk is fixed, we can move on with this, right?04:46
samPAh, need it on requirements?04:47
samPniraj_singh: OK, understand. Let's fix python client first..04:48
samP(2) recovery method customization04:48
niraj_singhyes. i waiting for that.04:48
niraj_singhi/i am04:49
*** kaisers_ has quit IRC04:49
tpatilsamP: We are planning to use openstacksdk instead of masakariclient04:49
tpatilNeed to fix ray review comment given on patch : https://review.openstack.org/#/c/543870/4/requirements.txt04:49
patchbotpatch 543870 - masakari-dashboard - Add segment panel04:49
tpatilsamP: recovery method customization, working on specs04:50
samPtpatil: ah...yes. thanks.. we don't need to use masakariclient04:50
samPthen can we bump the sdk version for dashboard and check?04:51
samPtpatil: thanks for working on recovery method customization spec04:51
tpatilsamP: Yes, it's working with the new sdk version. niraj_singh will do the needful and upload patches for review04:52
samPtpatil: niraj_singh: thanks. I will review once updated the patch.04:53
*** claudiub has joined #openstack-meeting04:53
niraj_singhyes, i will do this today.04:53
samPniraj_singh: thanks04:53
samP(3) Ansible support for Masakari04:53
niraj_singhRepo created for masakari ansible plugin04:53
niraj_singh https://github.com/openstack/openstack-ansible-os_masakari/04:53
samPgreat !!04:54
samPniraj_singh: Thanks04:54
niraj_singh"masakari-monitors" and "pacemaker and corosync" services are installed in my env. Not tested yet.04:54
niraj_singhCurrentlly working on the tests for the first commit https://review.openstack.org/#/c/566538/04:55
patchbotpatch 566538 - openstack-ansible-os_masakari - Add Maskari base jobs04:55
niraj_singhIt include masakari-appi and masakari-engine04:55
lkwan__will that be including the client ?04:55
tpatilsamP: we will contact cluster labs community to find out how to install pacemaker and corosync04:55
samPniraj_singh: got it. Do you find any useful Ansible role for pacemaker and coro?04:56
samPtpatil: niraj_singh: got it.04:56
tpatillkwan__: you mean python-masakariclient04:56
niraj_singhyes. https://github.com/mrlesmithjr/ansible-pacemaker04:56
tpatillkwan__: Yes, it will be installed automatically as it's a dependency in masakari-monitor04:57
niraj_singhsamP: we can use this for now.04:57
samPniraj_singh: great.. looks like some thing nice..04:57
niraj_singhsamP: thanks04:57
samPniraj_singh: np04:58
lkwan__my understanding is that masakari can be used not only limited to openstack but other cluster?04:58
samPGreat... anything else?04:58
samPlkwan__: ??04:58
lkwan__np, next time04:58
samPwe only have 2mins left04:58
lkwan__nothing else.04:59
*** Zames_ has joined #openstack-meeting04:59
samPlkwan__: please mail or discuss next time or discuss it on #openstack-masakari04:59
samPlkwan__: sorry04:59
samPLet's finish today's meeting.04:59
samPThank you everyone05:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"05:00
openstackMeeting ended Tue May  8 05:00:07 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-05-08-04.00.html05:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-05-08-04.00.txt05:00
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-05-08-04.00.log.html05:00
*** Dinesh__Bhor has joined #openstack-meeting05:01
*** Dinesh_Bhor has quit IRC05:02
*** Zames_ has quit IRC05:02
*** lkwan__ has quit IRC05:03
*** lkwan_ has quit IRC05:04
*** sagara has quit IRC05:04
*** yamamoto has joined #openstack-meeting05:06
*** epico has joined #openstack-meeting05:09
*** lpetrut has joined #openstack-meeting05:13
*** jesusaur has quit IRC05:14
*** hemna_ has quit IRC05:15
*** e0ne has joined #openstack-meeting05:18
*** jesusaur has joined #openstack-meeting05:19
*** kaisers has joined #openstack-meeting05:22
*** tpatil has quit IRC05:22
*** radeks has joined #openstack-meeting05:24
*** lpetrut has quit IRC05:24
*** kaisers has quit IRC05:27
*** Nel1x has quit IRC05:27
*** e0ne has quit IRC05:29
*** aeng has quit IRC05:32
*** trinaths has joined #openstack-meeting05:40
*** markstur has joined #openstack-meeting05:42
*** markstur has quit IRC05:48
*** marios has joined #openstack-meeting05:51
*** dmacpher has quit IRC05:52
*** kaisers1 has quit IRC05:54
*** dmacpher has joined #openstack-meeting05:55
*** kaisers has joined #openstack-meeting05:57
*** markvoelker has quit IRC06:01
*** pcaruana has joined #openstack-meeting06:01
*** tssurya has joined #openstack-meeting06:03
*** rbartal has joined #openstack-meeting06:07
*** lpetrut has joined #openstack-meeting06:10
*** kaisers1 has joined #openstack-meeting06:11
*** Dinesh__Bhor has quit IRC06:14
*** dineshbhor__ has joined #openstack-meeting06:14
*** dineshbhor__ has quit IRC06:15
*** liuzz_ has joined #openstack-meeting06:29
*** liuzz has quit IRC06:29
*** brault has joined #openstack-meeting06:32
*** rajinir has quit IRC06:35
*** brault has quit IRC06:36
*** andreas_s has joined #openstack-meeting06:37
*** alexchadin has joined #openstack-meeting06:39
*** jesusaur has quit IRC06:45
*** kaisers1 has quit IRC06:45
*** jesusaur has joined #openstack-meeting06:46
*** vabada has joined #openstack-meeting06:47
*** dmacpher has quit IRC06:56
*** rasca has quit IRC06:56
*** radeks_ has joined #openstack-meeting07:01
*** zhhuabj has quit IRC07:01
*** dangtrinhnt has joined #openstack-meeting07:01
*** markvoelker has joined #openstack-meeting07:01
*** mardim has joined #openstack-meeting07:02
*** brault has joined #openstack-meeting07:02
*** rasca has joined #openstack-meeting07:04
*** brault has quit IRC07:04
*** brault has joined #openstack-meeting07:04
*** alexchad_ has joined #openstack-meeting07:08
*** rcernin has quit IRC07:08
*** alexchadin has quit IRC07:10
*** sapd has joined #openstack-meeting07:11
*** zhhuabj has joined #openstack-meeting07:13
*** trinaths has quit IRC07:15
*** zhhuabj has quit IRC07:16
*** claudiub|2 has joined #openstack-meeting07:19
*** kaisers1 has joined #openstack-meeting07:22
*** claudiub has quit IRC07:22
*** epico has quit IRC07:27
*** armax has quit IRC07:30
*** diman has joined #openstack-meeting07:32
*** rwsu has quit IRC07:32
*** keiko has joined #openstack-meeting07:35
*** markvoelker has quit IRC07:36
*** keiko has quit IRC07:40
*** gcb has quit IRC07:41
*** nmagnezi has quit IRC07:46
*** nmagnezi has joined #openstack-meeting07:47
*** alexchad_ has quit IRC07:48
*** zhhuabj has joined #openstack-meeting07:50
*** mhoungbo1 has quit IRC07:51
*** dmacpher has joined #openstack-meeting07:53
*** zhhuabj has quit IRC07:55
*** yamamoto has quit IRC07:56
*** zhhuabj has joined #openstack-meeting07:58
*** phuoc_ has joined #openstack-meeting07:58
*** gongysh has joined #openstack-meeting08:02
gongysh#startmeeting tacker08:02
openstackMeeting started Tue May  8 08:02:15 2018 UTC and is due to finish in 60 minutes.  The chair is gongysh. Information about MeetBot at http://wiki.debian.org/MeetBot.08:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:02
*** openstack changes topic to " (Meeting topic: tacker)"08:02
openstackThe meeting name has been set to 'tacker'08:02
*** rwsu has joined #openstack-meeting08:02
gongysh#topic roll call08:02
*** openstack changes topic to "roll call (Meeting topic: tacker)"08:02
phuoc_hi gongysh08:03
gongyshphuoc_ hi08:03
*** yamamoto has joined #openstack-meeting08:03
*** keiko_ has joined #openstack-meeting08:04
*** egonzalez has joined #openstack-meeting08:05
gongysh#topic bp08:05
*** openstack changes topic to "bp (Meeting topic: tacker)"08:05
gongyshphuoc_ hi08:05
*** lpetrut has quit IRC08:05
gongyshdo you have update for your bp?08:05
*** zhhuabj has quit IRC08:06
phuoc_gongysh, I have some code for it08:06
*** dkushwaha has joined #openstack-meeting08:06
gongyshphuoc_, need any help from review?08:06
phuoc_So, I can create VNFFG between VM and container VNFs08:06
phuoc_use kuryr-kubernetes08:06
gongyshdkushwaha, hi08:06
*** Dinesh_Bhor has joined #openstack-meeting08:06
mardim#info Dimitrios Markou08:06
gongyshphuoc_, if you can put out testing method along with your patch, it will help lots.08:07
phuoc_so, I will record it, and send demo to you guys08:07
mardimgongysh, Can I start the update about the demo because I have a conflicting meeting in half an hour08:07
gongyshmardim, ok08:07
phuoc_mardim, sure ^^08:08
gongysh#topic demo of sfc in vancuvour08:08
*** openstack changes topic to "demo of sfc in vancuvour (Meeting topic: tacker)"08:08
mardimSo I have a video about the demo08:08
gongyshmardim, please.08:08
gongyshmardim, i have some updates and comments on demo ppt08:08
mardimBut today I realised08:08
mardimthat libvirt shutted off my devstack Vm08:08
mardimand right now nothing works08:08
mardimI will try to fix that but if I will not make it08:09
mardimwe will have the video08:09
mardimso I think we are coo08:09
mardimI hope gongysh like the video08:09
mardimAlso I ve updated the slides08:09
mardimfor the presentation08:09
mardimplease gongysh review it08:09
gongyshmardim, the is no audio for the video.08:09
mardimYes I know08:10
gongyshthe -> there08:10
mardimbeacuse I wanted to present it to the summit08:10
mardimAnd I do not wanted audio08:10
mardimSo I can do the live talk08:10
gongyshmardim, I have some comments on the google slides.08:10
gongyshyou can have a look at them.08:10
mardimgongysh, ok08:10
mardimyou can add or remove whatever you want on the slides08:11
mardimgongysh, ^08:11
gongyshone point I give is the github site for the demo scripts.08:11
gongyshso that the audience can practice it offline after the topic.08:11
mardimlet me check08:12
gongysh#link https://drive.google.com/open?id=1Hoq-QT9W-g68K1I87xH1Bu_ft382uOfe08:12
gongysh#link https://docs.google.com/presentation/d/1oxJeymXFlWhmeVRKEV2cDXWxpADhmw7lt_W8pDVDpOs/edit?usp=sharing08:12
*** YanXing_an has joined #openstack-meeting08:13
gongyshmardim, I hope you limited the edit privilege on the slides. :)08:13
gongyshguys, these two links are information about tacker sfc topic at vancouver summit.08:13
mardimthe link I send you is an edit link08:13
mardimnot a readonly08:14
gongyshanyone can comment on it.08:14
mardimIs it ok to just show the video08:14
mardimif I do not manage to recreate the hands on demo ?08:14
mardimbecause now is in a bad shpae08:14
gongyshmardim, thanks for the efforts to prepare the slides.08:15
gongyshmardim, the video is the last resort.08:15
gongyshok, lets back to bp topic08:16
gongysh#topic bp08:16
*** openstack changes topic to "bp (Meeting topic: tacker)"08:16
mardimThanks a lot08:16
gongyshmardim, thanks08:16
gongyshdangtrinhnt, hi08:16
dangtrinhntgongysh hi08:16
gongyshdo you have some thing to talk about your bp?08:17
dangtrinhntNothing finish yest. I'm still rushing with the studio08:17
gongyshdangtrinhnt, ok08:18
nguyenhai_Hi, about VNF monitoring using Mistral, I don't have any update too08:18
*** zhhuabj has joined #openstack-meeting08:18
dangtrinhntgongysh, mardim, Can I comment to the slides?08:18
gongyshnguyenhai_, you are still stuck with conductor to access the vim credentials:08:19
mardimYes of course08:19
dkushwahanguyenhai_, i think action part is still in wip08:19
gongyshdangtrinhnt, sure08:19
gongyshnguyenhai_, you are still stuck with conductor to access the vim credentials?08:19
nguyenhai_yes, I am08:19
gongyshYanXing_an, hi08:19
nguyenhai_anyone is expert in the vim credentials can help?08:20
gongyshdo we have a way for admin to access the vim credentials stored in barbican?08:20
gongyshconductor have to access the vim credentials.08:20
*** diman has quit IRC08:20
patchbotpatch 486924 - tacker - Implement VNF monitoring using Mistral08:20
YanXing_angongysh, maybe we need modify the Policy08:21
nguyenhai_oslo_messaging.set_transport_defaults(control_exchange='tacker') cannot transport all settings of server to conductor08:21
gongyshnguyenhai_, there are two problems here: one is how the conductor get the keystone settings of the tacker conf, second is how the conductor can get the vim credentials.08:23
*** dbecker has joined #openstack-meeting08:24
gongyshfor the first one, I think we can add keystone config options registry into the conductor codes.08:27
gongyshfor the second, do you have any idea?08:27
gongyshcan we allow someone to access the vim credentials stored in barbican?08:28
gongyshhow can we make change to barbican setting?08:28
*** Li_Jiale has joined #openstack-meeting08:29
YanXing_ani will look into it08:29
gongyshmardim, can you write the env setup script for the demo?08:29
gongyshI want to find some time to set up the env.08:30
gongyshYanXing_an, ok. thanks08:30
gongyshkeiko_, hi08:30
gongyshany update?08:30
nguyenhai_thanks YanXing_an08:30
keiko_just now on going for vnfm-reservation.08:31
gongyshkeiko_, ok08:31
mardimgongysh, what do you mean ?08:31
*** diman has joined #openstack-meeting08:31
mardimgongysh, what is the env_setup script ?08:31
gongyshmardim, I mean the demo env setup script.08:31
gongyshhad better step by step guide.08:32
mardimI will try to find some spare time to write a step by step guide08:32
mardimif this is what do you mean08:33
phuoc_mardim, I think you can provide some file, such as local.conf, vnffgd.yaml08:33
mardimI have the local.conf and the vnffgd files08:33
mardimI can provide them in a github repo08:33
phuoc_that's great08:33
mardimbut I do not have the time right now to write any script or a guide08:33
gongyshthe openwrt and scruxxx settings08:33
mardimso I cannot promise08:33
*** markvoelker has joined #openstack-meeting08:33
mardimwhat is scruxxxx08:34
dangtrinhntgongysh, The answer is yes. nguyenhai_: this workflow may help: https://docs.openstack.org/tacker/latest/contributor/encrypt_vim_auth_with_barbican.html#overview08:34
nguyenhai_I will look at it08:34
mardimgongysh, I can provide links08:35
mardimthat I used for the configuration08:35
YanXing_angongysh, nguyenhai, what's the use case that conductor access the vim credentials?  monitor the vim at high level?08:35
*** diman has quit IRC08:36
dangtrinhntmardim, I can help writing the script and guide.08:36
mardimdangtrinhnt, thanks08:36
mardimyou can start writing it08:36
dangtrinhntJust need your configuration file/link.08:36
mardimand I can review and help with additional info08:36
dangtrinhntok cool.08:36
gongyshYanXing_an, our policy action is run in tacker conductor, which is oslo message rpc target from mistral monitor tasks.08:36
mardimdangtrinhnt, ok I will send you some links after the meeting08:37
mardimthanks !!08:37
dangtrinhntNo problem. Cool.08:37
gongyshYanXing_an,  you can review the https://review.openstack.org/#/c/486924/ and get the idea.08:38
patchbotpatch 486924 - tacker - Implement VNF monitoring using Mistral08:38
*** nsingh has joined #openstack-meeting08:38
gongyshdangtrinhnt,  thanks08:38
*** arnewiebalck_ has joined #openstack-meeting08:38
gongyshdangtrinhnt, after that, please send me the github url.08:39
*** claudiub has joined #openstack-meeting08:39
*** _mmethot_ has joined #openstack-meeting08:39
gongyshmardim, for the topic, I want you to show us how the odl does the sfc.08:39
gongyshjust like the comment at the google doc.08:39
dangtrinhntgongysh, ok.08:39
*** arnewiebalck has quit IRC08:39
*** arnewiebalck_ is now known as arnewiebalck08:39
*** yamamoto_ has joined #openstack-meeting08:40
mardimI can update the slides about odl sfc08:40
gongyshmardim, thanks08:40
YanXing_angongysh, if we have only ping action for vim, it's no need to get the vim auth from barbican.08:40
mardimgongysh, no pro08:40
*** e0ne has joined #openstack-meeting08:40
*** mmethot_ has quit IRC08:40
*** aspiers has quit IRC08:40
*** zigo_ has quit IRC08:40
*** rasca has quit IRC08:41
*** ssbarnea_ has joined #openstack-meeting08:41
*** yamamoto has quit IRC08:41
*** niraj_singh has quit IRC08:41
*** claudiub|2 has quit IRC08:41
*** rasca has joined #openstack-meeting08:42
gongyshYanXing_an, we need to run policy action, such as respawn or scale the vnf from conductor08:42
nguyenhai_YanXing_an, we need vim auth for respawn the VNF08:42
YanXing_anok, i see08:42
gongysh#topic open discussion08:43
*** openstack changes topic to "open discussion (Meeting topic: tacker)"08:43
gongyshanything else?08:43
YanXing_anaguyenhai, it's a good change08:43
*** alexchadin has joined #openstack-meeting08:44
phuoc_Can you guys review it, https://review.openstack.org/#/c/54810908:44
patchbotpatch 548109 - tacker - Support exposing Kubernetes service using Loadbala...08:44
*** zigo has joined #openstack-meeting08:45
dangtrinhntgongysh, I don't see docker image for tacker-horizon in kolla08:45
gongyshdangtrinhnt, there is no independent tacker-horizon stuff08:45
gongyshtacker horizon is a plugin in horizon image.08:45
gongyshphuoc_, I am not sure I know the purpose of that patch. is it a part of your bp?08:46
phuoc_gongysh, yes08:46
phuoc_It will prepare devstack environment for my next patch set08:47
gongyshyou can mark it as a part of you bp at git commit msg.08:47
gongyshand add implements: bp xxxx08:47
dangtrinhntgongysh, that patch also fix an incompatibility issue with kuryr-k8s08:47
phuoc_gongysh sure, I will do it08:47
nguyenhai_I reported a bug: https://bugs.launchpad.net/tacker/+bug/176838608:48
openstackLaunchpad bug 1768386 in tacker "Cannot add OpenWRT image while installing by devstack" [Medium,New]08:48
gongyshdkushwaha, hi08:48
nguyenhai_Devstack installation cannot add OpenWRT image by default.08:48
nguyenhai_Can anyone confirm the function tacker_check_and_download_images work or not?08:48
dkushwahagongysh, hi08:48
gongyshdkushwaha, anything to talk?08:48
dkushwahagongysh, not now, i am just drafting ppt for project update08:49
gongyshdkushwaha, great.08:49
gongysh thanks08:49
gongyshdo you have project update template?08:49
gongyshI got the template email from community08:50
*** epico has joined #openstack-meeting08:50
dkushwahagongysh, oh, i am preparing own . https://docs.google.com/presentation/d/1cJQ6MVvCVLFVJM1RCkk9w-22St1xEDoOqpntpQdK-uI/edit#slide=id.g3379f772a0_0_12208:50
dkushwahagongysh,  please share that template, i will update accordingly08:51
gongyshdkushwaha, sure08:51
gongysh#link tacker update slides https://docs.google.com/presentation/d/1cJQ6MVvCVLFVJM1RCkk9w-22St1xEDoOqpntpQdK-uI/edit#slide=id.g3379f772a0_0_12208:51
gongyshdkushwaha, can you send me your email address again here?08:52
gongyshs/send/show/  me08:53
*** aspiers has joined #openstack-meeting08:53
*** nmagnezi_ has joined #openstack-meeting08:53
*** nmagnezi has quit IRC08:54
phuoc_gongysh, Can you share the template to me?08:54
phuoc_my email is: phuoc.hc@dcn.ssu.ac.kr08:54
phuoc_thank you08:54
*** hoangcx has quit IRC08:55
gongyshphuoc_, dkushwaha , email is on the way.08:55
*** vabada has quit IRC08:55
dkushwahagongysh, Thanks08:55
*** vabada has joined #openstack-meeting08:55
gongyshphuoc_, we can share the k8s feature on project update topic.08:56
gongysheven with a small demo.08:56
*** mattia has joined #openstack-meeting08:56
*** yamamoto_ has quit IRC08:56
phuoc_gongysh, sure08:56
phuoc_I will do it08:57
gongyshphuoc_, please help update the https://docs.google.com/presentation/d/1cJQ6MVvCVLFVJM1RCkk9w-22St1xEDoOqpntpQdK-uI/edit#slide=id.g3379f772a0_0_12208:57
*** d0ugal__ has quit IRC08:57
*** Zames_ has joined #openstack-meeting08:58
*** d0ugal has joined #openstack-meeting08:58
gongyshphuoc_, dkushwaha ,https://www.openstack.org/summit/vancouver-2018/summit-schedule/global-search?t=Onboarding08:58
gongyshwe also have a project onboarding topic08:58
gongyshI hope you guys can help to do it too.08:59
gongyshdangtrinhnt, hi08:59
*** YanXing_an has quit IRC08:59
dangtrinhntgongysh hi08:59
gongyshcan you help to prepare the ppt for onboarding sesstion?09:00
dkushwahagongysh, sure, do we need some saparate ppt for that too?09:00
gongyshlets to tacker channel.09:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:00
openstackMeeting ended Tue May  8 09:00:17 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2018/tacker.2018-05-08-08.02.html09:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2018/tacker.2018-05-08-08.02.txt09:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2018/tacker.2018-05-08-08.02.log.html09:00
*** kevinz has quit IRC09:00
*** keiko_ has quit IRC09:00
*** hoangcx has joined #openstack-meeting09:02
*** Zames_ has quit IRC09:02
*** lpetrut has joined #openstack-meeting09:03
*** markvoelker has quit IRC09:07
*** yamamoto has joined #openstack-meeting09:08
*** lpetrut has quit IRC09:14
*** fnaval has joined #openstack-meeting09:16
*** claudiub|2 has joined #openstack-meeting09:19
*** fnaval has quit IRC09:20
*** gongysh has quit IRC09:21
*** sambetts|afk is now known as sambetts09:22
*** claudiub has quit IRC09:22
*** mhoungbo1 has joined #openstack-meeting09:25
*** mhoungbo1_ has joined #openstack-meeting09:31
*** Zames_ has joined #openstack-meeting09:33
*** mhoungbo1 has quit IRC09:33
*** Dinesh_Bhor has quit IRC09:33
*** mhoungbo1_ has quit IRC09:34
*** Zames_ has quit IRC09:35
*** shu-mutow is now known as shu-mutow-AWAY09:39
*** bkopilov__ has quit IRC09:39
*** bkopilov_ has quit IRC09:39
*** diman_ has joined #openstack-meeting09:40
*** zhhuabj has quit IRC09:41
*** mhoungbo1 has joined #openstack-meeting09:42
*** gongysh has joined #openstack-meeting09:44
*** vabada has quit IRC09:46
*** diman_ has quit IRC09:46
*** vabada has joined #openstack-meeting09:46
*** diman_ has joined #openstack-meeting09:50
*** zhhuabj has joined #openstack-meeting09:53
*** diman_ has quit IRC09:55
*** Zames_ has joined #openstack-meeting09:56
*** Zames_ has quit IRC09:57
*** Zames_ has joined #openstack-meeting10:02
*** Li_Jiale has quit IRC10:03
*** markvoelker has joined #openstack-meeting10:04
*** Zames_ has quit IRC10:04
*** alexchadin has quit IRC10:09
*** dkushwaha has left #openstack-meeting10:14
*** yamamoto has quit IRC10:15
*** caowei has quit IRC10:20
*** yamamoto has joined #openstack-meeting10:20
*** liyi has quit IRC10:21
*** kaisers has quit IRC10:30
*** rcernin has joined #openstack-meeting10:35
*** markvoelker has quit IRC10:38
*** zhhuabj has quit IRC10:41
*** mhoungbo1 has quit IRC10:44
*** yamamoto has quit IRC10:48
*** ykatabam has quit IRC10:49
*** zhhuabj has joined #openstack-meeting10:53
*** ykatabam has joined #openstack-meeting10:53
*** alexchadin has joined #openstack-meeting10:55
*** gongysh has quit IRC11:06
*** diman_ has joined #openstack-meeting11:07
*** mhoungbo1 has joined #openstack-meeting11:07
*** mhoungbo1 has quit IRC11:10
*** longkb has quit IRC11:10
*** diman_ has quit IRC11:16
*** mhoungbo1 has joined #openstack-meeting11:19
*** claudiub has joined #openstack-meeting11:28
*** diman has joined #openstack-meeting11:30
*** phuoc_ has left #openstack-meeting11:31
*** claudiub|2 has quit IRC11:31
*** mhoungbo1 has quit IRC11:33
*** mhoungbo1 has joined #openstack-meeting11:34
*** markvoelker has joined #openstack-meeting11:34
*** mhoungbo1 has quit IRC11:35
*** diman has quit IRC11:35
*** zhangchi has joined #openstack-meeting11:36
*** yamamoto has joined #openstack-meeting11:37
*** liyi has joined #openstack-meeting11:39
*** mhoungbo1 has joined #openstack-meeting11:43
*** zhangchi has quit IRC11:52
*** rubasov has joined #openstack-meeting11:53
*** pchavva has joined #openstack-meeting11:55
*** sridharg has quit IRC11:56
*** sridharg has joined #openstack-meeting11:57
*** andreas_s has quit IRC12:01
*** rbartal has quit IRC12:01
*** andreas_s_ has joined #openstack-meeting12:02
*** andreas_s_ has quit IRC12:02
*** andreas_s_ has joined #openstack-meeting12:02
*** raildo has joined #openstack-meeting12:03
*** rbartal has joined #openstack-meeting12:04
*** mriedem has joined #openstack-meeting12:05
*** markvoelker has quit IRC12:08
*** edmondsw has joined #openstack-meeting12:08
*** zhangchi has joined #openstack-meeting12:09
*** diman has joined #openstack-meeting12:10
*** andreas_s_ has quit IRC12:12
*** andreas_s has joined #openstack-meeting12:13
*** andreas_s has quit IRC12:14
*** markvoelker has joined #openstack-meeting12:15
*** andreas_s_ has joined #openstack-meeting12:15
*** andreas_s_ has quit IRC12:15
*** andreas_s_ has joined #openstack-meeting12:16
*** diman has quit IRC12:16
*** liyi has quit IRC12:20
*** rbudden has joined #openstack-meeting12:23
*** bkopilov_ has joined #openstack-meeting12:25
*** kaisers has joined #openstack-meeting12:27
*** bkopilov__ has joined #openstack-meeting12:27
*** alexchadin has quit IRC12:31
*** kaisers has quit IRC12:32
*** zhangchi has quit IRC12:33
*** alexchadin has joined #openstack-meeting12:33
*** zhangchi has joined #openstack-meeting12:33
*** claudiub has quit IRC12:34
*** fabian_ has joined #openstack-meeting12:40
*** fabian_ is now known as chenyb412:40
*** mhoungbo1 has quit IRC12:49
*** arxcruz has quit IRC12:50
*** arxcruz has joined #openstack-meeting12:57
*** arxcruz has quit IRC13:00
*** arxcruz has joined #openstack-meeting13:01
*** brault has quit IRC13:04
*** diman has joined #openstack-meeting13:07
*** claudiub has joined #openstack-meeting13:09
*** diman has quit IRC13:13
*** yamamoto has quit IRC13:16
*** yamamoto has joined #openstack-meeting13:16
*** dklyle has quit IRC13:19
*** zhhuabj has quit IRC13:23
*** zhangchi has quit IRC13:24
*** mjturek has joined #openstack-meeting13:25
*** nsingh has left #openstack-meeting13:25
*** eharney has joined #openstack-meeting13:25
*** smcginnis[m] has joined #openstack-meeting13:28
*** claudiub has quit IRC13:28
*** felipemonteiro__ has joined #openstack-meeting13:28
*** gongysh has joined #openstack-meeting13:28
*** hoangcx_ has joined #openstack-meeting13:28
*** dustins has joined #openstack-meeting13:30
*** felipemonteiro_ has joined #openstack-meeting13:36
*** jamesmcarthur has joined #openstack-meeting13:36
*** VW has joined #openstack-meeting13:37
*** felipemonteiro__ has quit IRC13:39
*** Bonjourm8 has joined #openstack-meeting13:41
*** ssbarnea_ has quit IRC13:42
*** zhhuabj has joined #openstack-meeting13:42
*** Bonjourm8 has quit IRC13:42
*** anilvenkata has quit IRC13:45
*** amotoki has quit IRC13:51
*** hoangcx has quit IRC13:52
*** janzian has joined #openstack-meeting13:52
*** mlavalle has joined #openstack-meeting13:54
*** hoangcx_ is now known as hoangcx13:54
*** njohnsto_ has joined #openstack-meeting13:57
*** epico has quit IRC13:58
*** hongbin has joined #openstack-meeting13:59
*** diman has joined #openstack-meeting13:59
mlavalle#startmeeting networking14:00
openstackMeeting started Tue May  8 14:00:28 2018 UTC and is due to finish in 60 minutes.  The chair is mlavalle. 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
*** njohnsto_ has quit IRC14:00
mlavalleHi there!14:00
*** awaugama has joined #openstack-meeting14:00
*** esberglu has joined #openstack-meeting14:00
*** ihar has joined #openstack-meeting14:01
*** awaugama has quit IRC14:01
*** awaugama has joined #openstack-meeting14:01
*** shintaro has joined #openstack-meeting14:01
mlavalleUpdated agenda for today is here:14:01
mlavalle#link https://wiki.openstack.org/wiki/Network/Meetings14:01
mlavalleLet's get going:14:02
*** lajoskatona_ has joined #openstack-meeting14:02
mlavalle#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:02
mlavalleReminder that we are going about a month away from our next milestone, Rocky-2: June 4th to 8th14:03
*** kosamara has quit IRC14:03
*** ricolin_ has joined #openstack-meeting14:03
*** rossella_s has quit IRC14:03
*** rubasov has quit IRC14:03
*** alexchadin has quit IRC14:03
mlavalleLast week we mentioned that we are looking for a Neutron liaison with the QA team14:03
*** rubasov has joined #openstack-meeting14:04
mlavalleand slaweq has stepped up to the plate14:04
*** lajoskatona_ has quit IRC14:05
*** lajoskatona_ has joined #openstack-meeting14:05
*** jamesmcarthur has quit IRC14:05
*** lbragstad has quit IRC14:05
mlavalleslaweq: We can let andreaf know that now you have this role14:05
*** jamesmcarthur has joined #openstack-meeting14:05
*** rossella_s has joined #openstack-meeting14:05
*** mriedem has quit IRC14:05
*** lbragstad has joined #openstack-meeting14:05
mlavalleand I will update the liaisons page also14:05
*** e0ne_ has joined #openstack-meeting14:05
*** e0ne has quit IRC14:05
*** tris- has quit IRC14:06
andreafslaweq great, thank you! gmann should know about that too :)14:06
mlavalleThe Vancouver summit is less than 2 weeks away14:06
*** tris has joined #openstack-meeting14:06
*** ricolin has quit IRC14:06
slaweqI hope I will handle this role well :)14:06
mlavallecome on, we all know you will do GREAT!14:07
*** annp has joined #openstack-meeting14:07
mlavalleNeutron related Forum sessions in Vancouver are listed in the meeting's wiki page14:07
*** psachin` has quit IRC14:07
*** zhhuabj has quit IRC14:08
slaweqthx mlavalle :)14:08
mlavalleand finally, if you are attending the summit, please register your name here and let us know if you will join our team dinner on Tuesday evening:14:09
mlavalle#link https://etherpad.openstack.org/p/YVR-neutron-atendees14:09
mlavalleany other announcements we should bring up to the team?14:10
*** chenyb4 has quit IRC14:10
mlavalleok, let's move on14:11
mlavalle#topic Blueprints14:11
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:11
mlavalleThe blueprints that we are targeting for R-2 are these:14:11
mlavalle#link https://launchpad.net/neutron/+milestone/rocky-214:12
mlavalleDoes anyone has a blueprint to discuss?14:12
mlavalleI have a few things to say regarding blueprints14:13
mlavalleFirst of all, extending the logging framewokr to FWaaS14:14
mlavalleThere are a few patches under review:14:14
mlavalle#link https://review.openstack.org/#/q/topic:bug/172072714:14
mlavallePlease take a look if you have bandwidth available14:14
*** diman has quit IRC14:14
*** bobh has joined #openstack-meeting14:15
mlavalleParticularly, take a look at the spec: https://review.openstack.org/#/c/509725/14:15
patchbotpatch 509725 - neutron-specs - (Operator-only) Extend logging framework for FWaaS v214:15
annpmlavalle +114:15
njohnstonI think the spec is looking pretty good14:15
mlavallehoangcx ping me yesterday for something else but took advantage of the conversation to draw my attention to that spec. I will review it soon14:16
mlavallenjohnston: if you have a chance, please leave your opinion, feedback there :-)14:16
annpnjohnston: yes. I think the spec is good now14:16
*** yamamoto has quit IRC14:16
hoangcxmlavalle: Almost fwaas team members was OK with that. Just waiting for your final round :)14:17
mlavalleRegarding https://blueprints.launchpad.net/neutron/+spec/live-migration-portbinding14:18
mlavalleI have been busily working on this blueprint the past two weeks14:18
mlavallemaking excellent progress. I have a series of 5 patches that I will push soon14:18
mlavallethat finish the implementation14:19
annpmlavalle +114:19
mlavalleI am dividing this up in smaller chunks, so it is easier t review14:19
*** yamamoto has joined #openstack-meeting14:19
ihardoes it make sense to review now or better wait for push?14:20
*** zhhuabj has joined #openstack-meeting14:20
mlavalleihar: wait for me for the next push, please14:20
iharhappy to14:20
mlavalleFinally, I want to highlight https://blueprints.launchpad.net/neutron/+spec/strict-minimum-bandwidth-support14:21
mlavallerubasov has been making great progress with the spec: https://review.openstack.org/#/c/508149/14:22
patchbotpatch 508149 - neutron-specs - QoS minimum bandwidth allocation in Placement API14:22
*** mriedem has joined #openstack-meeting14:22
mlavallein my opinion, it is getting in good shape14:23
*** reedip_ has joined #openstack-meeting14:23
mlavalleI have one point of contention that I think we can fix this week14:23
rubasovyep, let's discuss that point on the next qos meeting14:24
mlavalleThe Nova side spec is also in good shape: https://review.openstack.org/#/c/502306/14:24
patchbotpatch 502306 - nova-specs - Network bandwidth resource provider14:24
gibithe nova spec has one nova internal data modelling question14:25
*** cloudrancher has joined #openstack-meeting14:25
gibiI'm aiming to get that resolved this week14:25
mlavalleFinally, finally, I want to remind the team about the OVO backlog:14:25
mlavalle#link https://docs.google.com/spreadsheets/d/1Mz7V40GSdcUH_aBoNWjsFaNRp4wf-duz1GFWligiNXc/edit#gid=105178884814:25
mlavallePlease take a look and see if there are work items you are interested in helping with14:26
mlavalleihar made great progress last week merging a few things that were blocking progress there14:27
mlavalleanything else on blueprints?14:27
*** kaisers has joined #openstack-meeting14:28
mlavalleok, let's move on14:28
mlavalle#topic Community Goals14:28
*** openstack changes topic to "Community Goals (Meeting topic: networking)"14:28
mlavalleI knew it! annp has an update :-)14:29
reedip_hi :)14:29
annpregards to deploy neutron-api under wsgi14:29
annpThanks Slawek and Gary for reviewing on https://review.openstack.org/#/c/555608/.14:29
patchbotpatch 555608 - neutron - Allow neutron-api load config from WSGI process14:29
annpCurrently I’m trying to fix race condition between neutron-rpc and neutron-api, which are pointed by Slaweq at https://review.openstack.org/#/c/473718/. Thanks a lot Slawek :)14:29
patchbotpatch 473718 - openstack-dev/devstack - [WIP]: WSGI Neutron integration14:29
*** mhoungbo1 has joined #openstack-meeting14:30
*** egonzalez has quit IRC14:30
slaweqannp: You welcome :)14:30
annpthere is no much progress compare with last meeting. But I think it will good in Rocky-214:30
annpmlavalle, that's all from me.14:31
mlavalleannp: thanks for the update14:31
annpmlavalle, Thanks. :) please go ahead14:32
*** kaisers has quit IRC14:32
mlavalleAs for pythn3.5 support, we have this etherpad:14:33
mlavalle#link https://etherpad.openstack.org/p/py3-neutron-pike14:33
*** Nil_ has joined #openstack-meeting14:33
mlavallewe probably need a formal owner for this goal, so if you have time, please volunteer14:34
*** zhhuabj has quit IRC14:34
mlavalleanything else on community goals?14:34
*** fnaval has joined #openstack-meeting14:35
mlavalleok, let's move on14:35
mlavalle#topic Bugs14:35
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:35
mlavalleOur deputy last week was hongbin14:35
mlavalleThis is the update he sent yesterday:14:36
*** egonzalez has joined #openstack-meeting14:36
mlavalle#link http://lists.openstack.org/pipermail/openstack-dev/2018-May/130245.html14:36
hongbinthere are 6 bugs opening last week14:36
hongbini want to bring this one up as it might have security impact: https://bugs.launchpad.net/neutron/+bug/176781114:37
openstackLaunchpad bug 1767811 in neutron "[DVR] br-int in compute node will send unknown unicast to sg-xxx" [Medium,Confirmed] - Assigned to Hong Hui Xiao (xiaohhui)14:37
mlavallehe seems to be working on it14:38
mlavallethe RFE that you point out is already in my radar screen14:39
mlavalleand haleyb has been commenting it14:39
haleybyes, mac re-generation14:40
mlavalleanything else you want to highlight, hongbin ?14:40
hongbinmlavalle: nothing else from me14:40
mlavallethanks for the thorough report14:40
hongbinmy pleasure :)14:40
mlavalleThis week our deputy is hichihara14:40
mlavalleI don't see him on line, but I'll ping him tonight to make sure he is aware14:41
*** rbudden has quit IRC14:41
mlavalle#topic Docs14:41
*** openstack changes topic to "Docs (Meeting topic: networking)"14:41
mlavalleboden is away on vacation this week and next14:42
mlavalleDoes anyone have anything about this topic?14:42
*** dklyle has joined #openstack-meeting14:42
mlavalle#topic neutron-lib14:42
*** openstack changes topic to "neutron-lib (Meeting topic: networking)"14:42
mlavalleSame observation about boden being away14:43
mlavalleAnyone wants to discuss anything on neutron-lib?14:43
mlavalle#topic CLI / SDK14:44
*** openstack changes topic to "CLI / SDK (Meeting topic: networking)"14:44
mlavallemhhh, I don't see amotoki on line either14:44
mlavalleanyone has anything to say on this topic?14:44
mlavalle#topic On demand agenda14:45
*** openstack changes topic to "On demand agenda (Meeting topic: networking)"14:45
mlavalleI added a point to this topic14:45
mlavalleThere is an intriguing ML thread about GraphQL and a pilot that is going to be done with the Neutron API14:46
mlavalleI still have to fully understand what this is and the plan14:46
mlavalleThere is going to be a meeting on this in Vancouver. so if you are around, I encourage folks to check it out and see what it means14:47
mlavalleThe thread is here:  http://lists.openstack.org/pipermail/openstack-dev/2018-May/130100.html14:47
*** rcernin has quit IRC14:47
mlavalleand with that, I return ~12 minutes to your agendas14:47
mlavalleThanks for attending14:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:48
openstackMeeting ended Tue May  8 14:48:09 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-05-08-14.00.html14:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-05-08-14.00.txt14:48
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-05-08-14.00.log.html14:48
slaweqthx for 12 minutes :)14:48
*** reedip_ has quit IRC14:48
slaweqsee You on next meeting14:48
*** rajinir has joined #openstack-meeting14:49
*** diman has joined #openstack-meeting14:49
*** armax has joined #openstack-meeting14:50
*** hemna_ has joined #openstack-meeting14:55
*** rbudden has joined #openstack-meeting14:55
*** hoangcx has quit IRC14:57
*** gongysh has quit IRC14:59
*** shintaro has quit IRC14:59
slaweq#startmeeting neutron_qos15:00
openstackMeeting started Tue May  8 15:00:08 2018 UTC and is due to finish in 60 minutes.  The chair is slaweq. 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:00
openstackThe meeting name has been set to 'neutron_qos'15:00
slaweqok, let's start15:01
*** wxy| has joined #openstack-meeting15:01
slaweq#topic RFEs15:01
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:01
slaweq#link https://bugs.launchpad.net/neutron/+bug/172757815:01
openstackLaunchpad bug 1727578 in neutron "[RFE]Support apply qos policy in VPN service" [Wishlist,Triaged]15:01
slaweqjust FYI: specs for this one is merged already15:01
slaweqI hope zhaobo6 will start working on implementation now15:02
mlavalleI know he is working on it15:02
slaweqsuper :)15:02
mlavalleit is actually in his goals15:02
slaweqis he from Your company?15:02
slaweqsuper - so we have good info about that :)15:03
slaweqnext one on list is:15:03
slaweq#link https://bugs.launchpad.net/neutron/+bug/156096315:03
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress]15:03
slaweqI have some idea how maybe it could be done but I didn't even test PoC if that will works actually15:03
slaweqI think about some marking of packets like (MARK in iptables) when packet is going out from tap interface and then match such marks on physical interface to proper class15:04
slaweqbut as I said I even check any PoC if that could makes sense even15:05
*** egonzalez has quit IRC15:05
slaweqdo You think that such solution might work maybe?15:05
mlavalleworth giving it a try15:05
*** reedip_ has joined #openstack-meeting15:05
mlavalledid the paper I sent help?15:05
slaweqyes, I read it15:06
*** markstur has joined #openstack-meeting15:06
slaweqand it is quite helpful15:06
slaweqthx mlavalle for it15:06
slaweqhi reedip_15:06
rubasovI have a faint memory of somebody claiming iptables CLASSIFY more efficient than MARK15:06
njohnstonhi reedip_!15:07
slaweqrubasov: thx for the tip15:07
slaweqI will try to explore it15:07
slaweqalso there is the case with openflow rules and without iptables so this should be somehow covered also :)15:08
*** links has quit IRC15:08
*** diman has quit IRC15:08
slaweqI really want to make some PoC for it soon15:09
slaweqok, moving to the next one15:09
slaweq#link https://bugs.launchpad.net/neutron/+bug/156096315:09
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress]15:09
slaweqAFAIK rubasov and mlavalle wanted to discuss something about that one today15:10
slaweqso go on :)15:10
rubasovlet me shortly summarize the question15:10
rubasovwe have two options15:11
rubasovoption 1: one qos policy rule (mimimum_bw as today) extended with two boolean parameters: enforce_data_plane, enforce_placement15:11
rubasovoption 1: two qos policy rules for data plane and placement15:12
rubasovI mean option 2 :-)15:12
*** manjeet has joined #openstack-meeting15:12
mlavallethe point that I don't get is why we need to separate dta plane enforcement and placement enforcement15:12
rubasovoption 1 is clearly better API design and better user experience (for the admin at least)15:12
rubasovbut I'm not sure about how it works with rule validation15:13
*** manjeet is now known as manjeets_wfh15:13
slaweqI have same question as mlavalle15:13
mlavalleif a port has a policy with a minimum bandwidth rule, it should be enforced in the data plane and for placament purposes also15:14
rubasovmlavalle, slaweq: since placement enforcement is agnostic of drivers we may have users wanting placement enforcement but not yet having data plane enforcement15:14
*** spilla has joined #openstack-meeting15:15
mlavallebut shouldn't those users be aware of what is available?15:15
mlavalleand request what is available15:15
rubasovalso (at least during upgrade) the current behavior is enforce_data_plane=True but enforce_placement=False15:15
*** spilla has left #openstack-meeting15:16
rubasovmlavalle: er, I'm not sure I understand your last question15:16
slaweqwhat about validating this rule type for all backends and document properly that it is supported by X, Y, Z backends and if You are using different one then min bandwidth will be only enforcement by placement15:17
slaweqwithout additional switch in API15:18
mlavalleThe way I see it, having a minimum bandwidth rule in a port means that it should be enforced in all the components that are necessary in the OpenStack system to make it effective15:18
mlavallewe shouldn't separate data plane and placement15:18
rubasovbut the system will actually work different in different openstack versions, shouldn't that be shown in the API?15:19
slaweqyes, but (at least for now) we don't have a way to enforce it on data plane yet15:19
slaweqbut for some private clouds it might be useful to use it only with "guarantee" on placement level15:19
mlavalleso, if I can create a minimum bandwidth rule, that is the API telling me it is possible15:20
slaweqrubasov: is that what You want to achieve?15:20
rubasovslaweq: yes15:20
slaweqok, so I at least understand it properly :)15:21
mlavallethe fact that I can create and assign a minimum bandwidth rule to a port should be the necessary condition for that rule to be enforced accross all the OpenStack componentts necessary to make it effective15:21
gibikeeping a single rule and enforcing that placement allocation is mandatory makes the upgrade harder. This will force us to create allocations for bound ports in placement during upgrade. However it is the same upgrade that will install the code that will report bandwidth inventory.15:21
gibifeels like a chicken and egg problem15:21
mlavalleso let's solve a migration problem15:22
rubasovmlavalle: for example what about direction ingress?15:22
mlavallebut let's not create artificial concepts in the API15:22
rubasovas soon as we'll have placement enforcement that will work for that direction (both directions in fact) for all drivers but we may not have data plane enforcement for all drivers at that point15:23
*** YanXing_an has joined #openstack-meeting15:23
slaweqyes, and IMHO that should be properly documented that users would be aware of whatis guaranteed and what is best effort only15:24
*** reedip_ is now known as reedip_ooo15:24
*** reedip_ooo has quit IRC15:24
mlavalleyes, isn't this a documentation issue?15:25
*** andreas_s_ has quit IRC15:25
*** andreas_s has joined #openstack-meeting15:26
*** annp has quit IRC15:26
rubasovbut that documentation could not be global, it would depend on which drivers are loaded, right? so each deployer would have to document this again for each deployment15:26
slaweqrubasov: but I was thinking about something like:15:27
mlavallewe can give them the rules: if you have such and such drivers, you minimum bandwidth rules will be enforced15:28
slaweqmin bw limit is supported by ovs, sr-iov backends so if You use those backends, Your min bw will be guarantee15:28
*** diman has joined #openstack-meeting15:28
* mlavalle tried to say the same thing as slaweq15:28
slaweqif You use other backend, like linuxbridge, bw limit is only enforcement by placement and is not guarantee15:28
*** manjeets_ has joined #openstack-meeting15:28
slaweqwhat You think about something like that?15:29
*** manjeets_ has quit IRC15:29
*** manjeets_ has joined #openstack-meeting15:29
rubasovthat's pretty much what we had in patch set 615:30
patchbotpatch 508149 - neutron-specs - QoS minimum bandwidth allocation in Placement API15:30
*** felipemonteiro has joined #openstack-meeting15:30
rubasovI'm trying to remember why we moved away from it (if there was a proper reason, I'm not sure)15:30
*** felipemonteiro__ has joined #openstack-meeting15:31
mlavalleI am happy with that15:31
*** manjeets_wfh has quit IRC15:31
mlavallebecause what is stated there is a "temporary" situation15:31
mlavallethat we can change as we add support for more drivers15:31
slaweqat least it should be temporary and we should add support for ovs and lb backends for it :)15:32
mlavallein contrast, adding stuff to the API creates long term, permamnet situations15:32
mlavallethat are difficult to change in the future15:32
*** felipemonteiro_ has quit IRC15:32
*** manjeets_ is now known as manjeets_wfh15:33
slaweqmlavalle: in our case API changes are almost impossible to change :)15:33
mlavalleAPIs create commitments15:33
*** njohnston is now known as njohnston_afk15:34
rubasovI'm just a bit afraid of the user being confused when asking for the same thing in the API and getting many different things depending on OpenStack version and/or backend drivers (both being things the end user should not know about)15:34
*** felipemonteiro has quit IRC15:35
*** andreas_s has quit IRC15:35
mlavalleIn that sense, we have an undesirable situation given how fast the community can add minimum bandwidth support to different drivers15:35
rubasovbut I can let that fear go if you prefer to handle this kind of support matrix by documentation15:35
slaweqI would prefer docs way for that15:35
mlavallebut that undesirable situation is temporary, as we add support for more drivers15:36
slaweqbut I think that it's mlavalle and drivers team choice :)15:36
mlavalleand we can mitigate it with proper documentation15:36
rubasovI accept that choice15:37
gibican we get back to the upgrade issue?15:37
mlavallein fact, we use that matrix approach already in the QoS documentation, IIRC15:37
gibiassume there is a bound SRIOV port with minimum bandwidth rule today. that is enforced on the data plane15:37
gibinow the deployer upgrades neutron and nova to the version that support placement bandwidth rule and that r15:38
*** diman has quit IRC15:38
gibirequires the port to have bandwidth allocation in placement15:38
gibiduring upgrade we cannot make that allocation, as no bandwidht inventory will be in place15:39
slaweqmlavalle: we have such matrix here: https://docs.openstack.org/neutron/latest/contributor/internals/quality_of_service.html#agent-backends15:39
rubasovslaweq: yep, I was thinking of the same15:39
gibiso after such upgade we will have an inconsistent resource allocation situation in placement15:39
*** andreas_s has joined #openstack-meeting15:40
gibiwhich means any new boot with QoS bandwidth aware port will result in a not enforced resource limit15:40
mlavallecan't we include in the upgrade process a script that cretes the bandwidth inventories15:40
gibimlavalle: that inventory is agent dependent15:40
gibimlavalle: so I'm not sure15:41
gibimoreover there are two cases15:41
mlavalleif a host is running agents with minimum bandwidth supppirt15:41
mlavallethe script will create the RPs necessary15:42
gibimlavalle: so that script will duplicate the work of the given agent (ovs, sriov, etc)15:42
mlavallewe can get that data in the controller from the agents heartbeats15:42
mlavalleonly during the upgrades15:42
gibimlavalle: but that would require an upgraded and running agent15:43
gibimlavalle: and an upgraded and running controller that understands the new heartbeat sturcture15:44
slaweqgibi: such script would need to duplicate only sriov agent's work as only this backend supports now min bandwidth15:44
gibislaweq: good point15:44
gibislaweq: that help15:44
gibistill there are two cases15:44
*** annp has joined #openstack-meeting15:44
gibii) we can do an in place allocation for the bound port15:44
gibiii) we cannot as there is not enough bandwidth on that host15:44
rubasovI think (ii) is the really hard one15:45
gibi#ii) would require a livemigration to resolve15:45
mlavalleyeah, and the admin should be aware of it15:45
mlavalleand take necessary actions15:45
mlavallehowever unpleasant the upgrade process might be, it will happen once15:46
gibimlavalle: either we fail the upgrade or implement a pre-flight check for such situation15:46
mlavallebut that is preferable to add things to the API that we will never be able to remove15:46
mlavalleand that will create an unpleasant experience to users and admins for a loooong time15:47
gibimlavalle: you statement about API commitment make sense to me. I'm just pretty afraid about the unplesantness of this upgrade15:48
mlavalleme too, but it is only once per deployment15:48
gibimlavalle: maybe when we will have some PoC code where I can play with the upgrade that would help removing some of the fear15:48
mlavallelet's focus on making mitigating that unplestaness as much as we can15:48
* mlavalle not sure that word exists15:49
rubasovIMHO even if gibi's upgrade concerns are valid (not 100% sure myself at the moment) we can get back to this if and when the upgrade proves to be too painful in a lab setting (but before removing the experimental flag from the overall feature)15:50
gibirubasov: I can live with that15:50
mlavalleyeah, let's move ahead with the spec assuming documentation15:50
mlavallewill help us address the migration problem15:50
mlavallewe all understand that there are trade offs15:51
mlavalleand let's not over commit to an API design that is not ideal15:51
slaweqI agree, let's make something first and then deal with upgrades problem :)15:51
rubasovI'll update the spec accordingly tomorrow15:52
mlavallerubasov, gibi, lajoskatona_: I want to commend your great work over the past few weeks on this topic15:52
mlavalleyou guys are the best !15:52
gibimlavalle: thanks15:52
rubasovmlavalle, slaweq: thank you for all the help15:53
*** andreas_s has quit IRC15:53
mlavalleok, slaweq I think we can move on15:54
slaweqok, I think we can quickly move to next topic now :)15:54
slaweqor wait15:54
slaweqthere is also15:54
slaweq#link https://bugs.launchpad.net/neutron/+bug/150562715:54
openstackLaunchpad bug 1505627 in neutron "[RFE] QoS Explicit Congestion Notification (ECN) Support" [Wishlist,Triaged] - Assigned to Reedip (reedip-banerjee)15:54
slaweqwhich is mark as postponed15:54
slaweqbut specs is waiting for review: https://review.openstack.org/#/c/445762/15:55
patchbotpatch 445762 - neutron-specs - Spec for Explicit Congestion Notification15:55
* mlavalle has that spec in his bakclog of reviews15:55
slaweqso please add it to Your queue maybe :)15:55
slaweqthx mlavalle15:55
slaweqok, so next topic15:55
slaweq#topic Bugs15:55
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:55
slaweqI'm now aware about any new bug related to QoS15:55
slaweqso just short sum up15:56
slaweq#link https://bugs.launchpad.net/neutron/+bug/175831615:56
openstackLaunchpad bug 1758316 in neutron "Floating IP QoS don't work in DVR router" [High,In progress] - Assigned to LIU Yulong (dragon889)15:56
slaweqpatch for that is in gate probably: https://review.openstack.org/#/c/558724/15:56
patchbotpatch 558724 - neutron - [L3][QoS] Cover mixed dvr_snat and compute node dv...15:56
slaweqso it might be consiedered as fixed IMO :)15:56
slaweqno, there is -2 from zuul :/15:56
slaweqso we will have to recheck it15:56
* mlavalle who is weizj, he is been reviewing a lot of patches15:57
slaweqmlavalle: I don't know15:57
slaweqbut I also saw a lot of reviews from him recently15:57
mlavallewell, it is good to have one more reviewer15:57
slaweqtwo more bugs (very old):15:58
slaweq#link https://bugs.launchpad.net/neutron/+bug/163918615:58
openstackLaunchpad bug 1639186 in neutron "qos max bandwidth rules not working for neutron trunk ports" [Low,Confirmed]15:58
slaweq#link https://bugs.launchpad.net/neutron/+bug/173285215:58
openstackLaunchpad bug 1732852 in neutron "neutron don't support Router gateway rate limit " [Low,In progress]15:58
slaweqthere is no any update about them15:58
*** e0ne_ has quit IRC15:58
slaweqit's just short reminder - maybe someone want's to hug them :)15:58
*** lajoskatona_ has quit IRC15:59
slaweqok, I think that we are almost out of time now16:00
slaweqso thanks guys16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:00
openstackMeeting ended Tue May  8 16:00:35 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
slaweqsee Yoy16:00
mlavalleThank you all for the great discussion16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-05-08-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-05-08-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-05-08-15.00.log.html16:00
rubasovthank you16:00
*** edmondsw has quit IRC16:00
slaweq#startmeeting neutron_ci16:01
openstackMeeting started Tue May  8 16:01:21 2018 UTC and is due to finish in 60 minutes.  The chair is slaweq. 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
slaweqwelcome on CI meeting :)16:01
*** edmondsw has joined #openstack-meeting16:01
mlavallethe last one of my morning :-)16:01
* slaweq have busy, meetings day :)16:01
*** janki has quit IRC16:01
slaweqmlavalle: same for me but last of my afternoon16:02
slaweqhi ihar16:02
iharoh you guys stay fir 3h? insane16:02
slaweqhaleyb will join?16:02
slaweqihar: yes16:02
slaweqI just finished QoS meeting and started this one16:02
* haleyb takes an hour off for offline meetings :(16:02
slaweqone by one :)16:02
slaweqok, lets start16:03
slaweq#topic Actions from previous meetings16:03
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:03
slaweqlast week there was no meeting so let's check actions from 2 weeks16:03
slaweq* slaweq will check failed SG fullstack test16:03
slaweqI reported bug https://bugs.launchpad.net/neutron/+bug/176782916:03
openstackLaunchpad bug 1767829 in neutron "Fullstack test_securitygroup.TestSecurityGroupsSameNetwork fails often after SG rule delete" [High,Confirmed] - Assigned to Slawek Kaplonski (slaweq)16:03
slaweqI tried to reproduce it with some DNM patch with additional logs but I couldn't16:04
slaweqI suppose that it is some race condition in conntrack manager module16:04
*** gyee has joined #openstack-meeting16:04
haleybslaweq: i hope not :(  but i will also try, and do some manual testing, since it's blocking that other patch16:04
slaweqhaleyb got similar error on one of his patches I think and there it was reproducible 100% of times16:04
slaweqok, so haleyb You will check that on Your patch, right?16:06
*** rmascena has joined #openstack-meeting16:06
haleybslaweq: yes, and i had tweaked the patch with what looked like a fix, but it still failed, so i'll continue16:06
*** marios has quit IRC16:06
*** cloudrancher has quit IRC16:06
slaweqok, thx16:06
slaweq#action haleyb will debug failing security groups fullstack test: https://bugs.launchpad.net/neutron/+bug/176782916:07
openstackLaunchpad bug 1767829 in neutron "Fullstack test_securitygroup.TestSecurityGroupsSameNetwork fails often after SG rule delete" [High,Confirmed] - Assigned to Slawek Kaplonski (slaweq)16:07
slaweqnext one is16:07
slaweq* slaweq will report bug about failing trunk tests in dvr multinode scenario16:07
slaweqBug report is here: https://bugs.launchpad.net/neutron/+bug/176670116:07
openstackLaunchpad bug 1766701 in neutron "Trunk Tests are failing often in dvr-multinode scenario job" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)16:07
slaweqI see that mlavalle is assigned to it16:08
slaweqdid You find something maybe?16:08
*** raildo has quit IRC16:08
mlavalleno, I haven't made progress on this one16:08
*** YanXing_an has quit IRC16:08
mlavalleI will work on it this week16:09
slaweq#action mlavalle will check why trunk tests are failing in dvr multinode scenario16:09
slaweqok, next one16:10
slaweq* jlibosva will mark trunk scenario tests as unstable for now16:10
slaweqhe did: https://review.openstack.org/#/c/564026/16:10
mlavalleI think he did16:10
patchbotpatch 564026 - neutron-tempest-plugin - Mark trunk tests as unstable (MERGED)16:10
slaweqso mlavalle, be aware that those tests will now not fail in new jobs16:10
slaweqif You will look for failures, You need to look for skipped tests :)16:10
slaweqnext one was:16:11
slaweq* slaweq to check rally timeouts and report a bug about that16:11
slaweqI reported a bug: https://bugs.launchpad.net/neutron/+bug/176670316:11
openstackLaunchpad bug 1766703 in neutron "Rally tests job is reaching job timeout often" [High,Confirmed] - Assigned to Slawek Kaplonski (slaweq)16:11
slaweqand I did some initial checks of logs16:11
slaweqthere are some comments in bug report16:11
*** manjeets_ has joined #openstack-meeting16:12
slaweqbasically it don't looks like we are very close to the limit on good runs16:12
*** cloudrancher has joined #openstack-meeting16:12
slaweqand also in neutron server logs I found that API calls on such bad runs are really slow, e.g. http://logs.openstack.org/24/558724/11/check/neutron-rally-neutron/d891678/logs/screen-q-svc.txt.gz?level=INFO#_Apr_24_04_23_23_63263116:14
slaweqalso there is a lot of errors in this log file: http://logs.openstack.org/24/558724/11/check/neutron-rally-neutron/d891678/logs/screen-q-svc.txt.gz?level=INFO#_Apr_24_04_14_59_00394916:14
slaweqI don't think that this is culprit of slow responses because same errors are in logs of "good" runs16:15
slaweqbut are You aware of such errors?16:15
*** manjeets_wfh has quit IRC16:15
slaweqihar: especially You as it looks to be related to db :)16:15
*** andreas_s has joined #openstack-meeting16:16
iharI think savepoint deadlocks are common, as you said already16:16
iharI have no idea why tho16:16
slaweqok, just asking, thx for checking16:17
iharone reason for slow db could be limit on connections in oslo.db16:17
iharand/or wsgi16:17
iharneutron-server may just queue requests16:17
slaweqihar: thx for tips, I will try to investigate this slow responses more during the week16:17
*** harlowja has joined #openstack-meeting16:17
iharbut I dunno, depends on whether we see slowdowns in the middle of handlers or it just takes a long time to see first messages of a request16:18
*** ricolin_ has quit IRC16:18
slaweqproblem is that if it reach this timeout then there is no those fancy rally graphs and tables to check everything16:19
slaweqso it's not easy to compare with "good" runs16:19
slaweq#action slaweq will continue debugging slow rally tests issue16:19
slaweqI think we can move on to the next one16:20
slaweq* slaweq will report a bug and talk with Federico about issue with neutron-dynamic-routing-dsvm-tempest-with-ryu-master-scenario-ipv416:20
slaweqBug report: https://bugs.launchpad.net/neutron/+bug/176670216:20
openstackLaunchpad bug 1766702 in neutron "Periodic job * neutron-dynamic-routing-dsvm-tempest-with-ryu-master-scenario-ipv4 fails" [High,Confirmed] - Assigned to Slawek Kaplonski (slaweq)16:20
slaweqdalvarez found that there was also another problem caused by Federico's patch16:20
slaweqI already proposed patch to fix what dalvarez found16:21
slaweqand I'm working on fix neutron-dynamic-routing tests16:21
*** arnewiebalck has quit IRC16:21
slaweqproblem here is that now tests can't create two subnets with same cidr16:21
*** yamamoto has quit IRC16:21
*** cloudrancher has quit IRC16:22
slaweqand neutron-dynamic-routing in scenario tests creates subnetpool and then subnet "per test" but always uses same cidrs16:22
slaweqso first test passed but in second subnet is not created as cidr is already in use16:22
slaweqhaleyb posted some patch to check it but it wasn't fix for this issue16:23
slaweqso I will continue this work also16:23
slaweq#action slaweq to fix neutron-dynamic-routing scenario tests bug16:23
slaweqok, that's all from my list16:24
slaweqdo You have anything to add?16:24
*** andreas_s has quit IRC16:25
slaweqok, so let's move on to next topic16:25
*** andreas_s has joined #openstack-meeting16:25
slaweq#topic Grafana16:25
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:25
slaweqMany tests on high failure rate yesterday and today, but it might be related to some issue with devstack legacy jobs, see: http://eavesdrop.openstack.org/irclogs/%23openstack-infra/latest.log.html#t2018-05-08T07:10:0216:27
*** manjeets_ has quit IRC16:28
*** radeks_ has quit IRC16:28
*** kaisers has joined #openstack-meeting16:29
*** erlon has quit IRC16:29
slaweqexcept that I think that it's quite "normal" for most tests16:30
slaweqdo You see anything worrying?16:30
slaweqok, I guess we can move to next topics16:32
mlavallehas the devstack issue benn solved?16:32
slaweqyes, I frickler told me today it should be solved last night16:33
slaweqso recheck of Your patch should works fine :)16:33
slaweqmoving on16:33
slaweq#topic Scenarios16:33
*** openstack changes topic to "Scenarios (Meeting topic: neutron_ci)"16:33
*** kaisers has quit IRC16:33
slaweqI see that dvr-multinode job is now at about 20 to 40% still16:34
slaweqeven after marking trunk tests and dvr migration tests as unstable16:34
slaweqlet's check some example failures then :)16:35
haleybslaweq: Kernel panic - not syncing:16:36
haleybhah, that's not neutron!16:37
slaweqhaleyb: :)16:37
slaweqI just copied failure result without changing the reason16:37
slaweqI'm looking for some other examples still16:37
*** rossella_s has quit IRC16:38
slaweqbut this should be already marked as unstable, right haleyb?16:38
haleybthis one or the last one?16:38
*** andreas_s has quit IRC16:38
slaweqlast one16:39
slaweqin first one, if it was kernel panic than it's "fine" for us :)16:39
*** yamamoto has joined #openstack-meeting16:39
mlavallenot our problem16:39
haleybi'm not sure the migration tests are marked unstable16:40
slaweqmlavalle: I think we have enough of our problems still ;)16:40
mlavallewe do16:40
*** rossella_s has joined #openstack-meeting16:40
haleybboth those failed metadata16:40
slaweqhaleyb: I though that You did it few weeks ago16:40
*** manjeet has joined #openstack-meeting16:40
patchbotpatch 561322 - neutron-tempest-plugin - Mark DVR/HA migration tests unstable (MERGED)16:41
haleybyes, it should have covered them16:42
*** manjeets_ has joined #openstack-meeting16:42
slaweqso maybe it was some old patch then16:42
slaweqbut we know this issue already so I think we don't need to talk about it now16:43
slaweqthx for check haleyb :)16:43
slaweqin the meantime I found one more failed run:16:43
slaweqand here it was global job timeout reached16:43
*** manjeet has quit IRC16:45
*** diman has joined #openstack-meeting16:45
slaweqlooks that most tests took about 10 minutes16:46
slaweqI think that if such issue will repeat more we will have to investigate what is slowing down those tests16:48
slaweqdo You agree? :)16:48
haleybyes, agreed16:48
*** dklyle has quit IRC16:48
*** EmilienM is now known as EmilienM_PTO16:49
*** ssbarnea_ has joined #openstack-meeting16:49
slaweqok, thx haleyb :)16:49
slaweqI didn't found different issues for this job from last few days16:49
slaweqaccording to other scenario jobs16:49
*** sshank has joined #openstack-meeting16:49
slaweqI want to remind You that since some time we have voting 2 jobs:16:50
*** diman has quit IRC16:50
slaweqboth are IMHO quite stable according to graphana16:50
slaweqand I would like to ask if we can consider to make them gating also16:50
* mlavalle looking at grafana16:50
slaweqwhat do You think?16:51
mlavalleyes, let's give it a try16:51
slaweqthx mlavalle for blessing :)16:52
slaweqshould I send patch or You want to do it?16:52
mlavalleplease send it16:54
slaweqok, I will16:54
slaweq#action slaweq to make 2 scenario jobs gating16:54
slaweqI don't have anything else according to any of job types for today16:55
slaweqdo You want to talk about something else?16:55
slaweqif not we can finish few minutes before the time :)16:55
mlavalleI don't have anything else16:55
slaweqok, so enjoy Your free time then ;)16:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:56
openstackMeeting ended Tue May  8 16:56:55 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-05-08-16.01.html16:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-05-08-16.01.txt16:56
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-05-08-16.01.log.html16:57
slaweqthanks for attending16:57
mlavallethanks slaweq, haleyb, ihar16:57
*** jessegler has joined #openstack-meeting16:57
*** rbartal has quit IRC16:59
*** zhhuabj has joined #openstack-meeting17:00
*** wxy| has quit IRC17:02
*** sambetts is now known as sambetts|afk17:02
*** jamesmcarthur has quit IRC17:04
*** dklyle has joined #openstack-meeting17:04
*** jamesmcarthur has joined #openstack-meeting17:05
*** jamesmcarthur has quit IRC17:09
*** e0ne has joined #openstack-meeting17:10
*** yamamoto has quit IRC17:10
*** e0ne has quit IRC17:12
*** gyee has quit IRC17:17
*** kaisers has joined #openstack-meeting17:22
*** ayoung is now known as ayoung-dentist17:25
*** slaweq has quit IRC17:25
*** slaweq has joined #openstack-meeting17:26
*** harlowja has quit IRC17:31
*** slaweq has quit IRC17:31
*** annp has quit IRC17:32
*** e0ne has joined #openstack-meeting17:32
*** julim has joined #openstack-meeting17:33
*** julim has quit IRC17:33
*** dklyle has quit IRC17:37
*** slaweq has joined #openstack-meeting17:41
*** julim has joined #openstack-meeting17:42
*** ekcs has joined #openstack-meeting17:42
*** slaweq has quit IRC17:45
*** tssurya has quit IRC17:50
*** tobiash has joined #openstack-meeting17:50
*** mjturek has quit IRC17:50
*** jlvillal is now known as jlvacation17:51
*** arnewiebalck_ has joined #openstack-meeting17:56
*** anteaya has joined #openstack-meeting17:59
*** ssbarnea_ has quit IRC17:59
*** mhoungbo1 has quit IRC18:02
*** rossella_s has quit IRC18:05
*** VW_ has joined #openstack-meeting18:07
*** VW_ has quit IRC18:08
*** VW_ has joined #openstack-meeting18:08
*** felipemonteiro__ has quit IRC18:10
*** felipemonteiro__ has joined #openstack-meeting18:10
*** VW has quit IRC18:10
*** yamamoto has joined #openstack-meeting18:11
*** radeks_ has joined #openstack-meeting18:11
*** gyee has joined #openstack-meeting18:19
*** Bonjourm8 has joined #openstack-meeting18:20
*** yamamoto has quit IRC18:21
*** erlon has joined #openstack-meeting18:22
*** harlowja has joined #openstack-meeting18:25
*** vabada2 has joined #openstack-meeting18:26
*** vabada has quit IRC18:27
*** erlon has quit IRC18:28
*** sridharg has quit IRC18:29
*** strigazi has quit IRC18:30
*** strigazi has joined #openstack-meeting18:31
*** jessegler has quit IRC18:31
*** psachin` has joined #openstack-meeting18:33
*** rossella_s has joined #openstack-meeting18:37
*** e0ne has quit IRC18:38
*** ssbarnea_ has joined #openstack-meeting18:38
*** pchavva has quit IRC18:39
*** Swami has joined #openstack-meeting18:39
*** tssurya has joined #openstack-meeting18:42
*** kaisers has quit IRC18:42
*** kaisers has joined #openstack-meeting18:42
*** VW_ has quit IRC18:43
*** VW has joined #openstack-meeting18:44
*** Swami has quit IRC18:45
*** Shrews has joined #openstack-meeting18:50
*** Bonjourm8 has quit IRC18:52
corvusoh hey19:00
clarkb#startmeeting infra19:01
openstackMeeting started Tue May  8 19:01:13 2018 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
clarkb#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
clarkbSummit/OpenDev is in just under two weeks19:01
clarkbIf you are attending don't forget to do whatever prep you need :)19:02
* corvus frets19:02
*** e0ne has joined #openstack-meeting19:02
* fungi is so behind19:02
clarkbwe need a support group19:02
clarkbI was silly and decided to take a mini vacation next week for my birthday. Which further cuts into my available time (but I'm excited to go fishing and sit on the (cold) oregon beach)19:03
fungisounds marvellous19:03
clarkbDue to ^ we'll need an infra meeting chair volunteer19:03
anteayahappy birthday19:03
clarkband I figure we'll cancel the May 22 meeting as many of us will be at the summit19:03
clarkbLet me know if interested in chairing on the 15th19:04
* fungi hopes that's cmurphy volunteering to chair next week's meeting ;)19:04
clarkbfungi: I totally read it that way too :P19:04
mordredthat's how I read it19:04
* cmurphy runs19:04
*** julim has quit IRC19:04
clarkbanything else need to be announced?19:05
*** VW_ has joined #openstack-meeting19:05
fungii don't seem to have any conflicts for the 15th so _can_ chair, but totally wouldn't want to take that pleasure away from anyone who wants to volunteer. i've chaired plenty of these already19:05
*** VW_ has quit IRC19:05
anteayaI think cmurphy should take a turn19:05
*** VW_ has joined #openstack-meeting19:05
clarkbI think cmurphy might also be semi afk too so won't push too hard on that :)19:05
anteayaah okay19:06
anteayaanother time then19:06
cmurphyyeah i am in and out for the next couple weeks19:06
clarkb#topic Actions from last meeting19:06
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:06
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-05-01-19.01.txt minutes from last meeting19:06
clarkbThere wasn't a specific #action recorded but more of a collective please go review our three config management future specs. Seems like there were comments on the whole set so I think people were reading them19:06
clarkbBefore we dig into that subject19:07
clarkb#topic Specs approval19:07
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:07
clarkb#link https://review.openstack.org/349831 Survey tool spec19:07
patchbotpatch 349831 - openstack-infra/infra-specs - Add survey spec19:07
clarkbanteaya: has indicated that ^ should be ready for review. tl;dr is lets run a limesurvey to host the surveys that various groups want to run around openstack19:07
clarkbfungi: I think you've been helping out there are you happy for that to be up for approval this week as well?19:08
*** VW has quit IRC19:08
*** jamesmcarthur has joined #openstack-meeting19:08
fungiyeah, i think i've already registered a rollcall +1 on it19:08
clarkbyup I see that now19:08
anteayaand yes he has been helping out a lot19:08
*** ChanServ sets mode: +b *!*@ec2-52-37-21-161.us-west-2.compute.amazonaws.com19:08
*** patchbot was kicked by ChanServ (Banned: Please operate bots in common openstack channels through official project infrastructure)19:08
fungithe biggest unknown was the self-service signup to create surveys19:08
anteayafor which I'm very grateful19:09
clarkbif the infra council voters could look over that spec this week it would be appreciated. I'll make a not to look at it probably late on thursday as far as approving it goes19:09
clarkb*make a note19:09
fungibut digging into configuration now that we have a demo/prototype up, it looks like it should be able to handle webserver auth so we have a good chance of getting apache mod_auth_openid working19:09
*** dklyle has joined #openstack-meeting19:09
fungii'm hoping to give that a shot tomorrow now that i've found all the commented configuration defaults for limesurvey19:10
anteayathank you19:10
fungialso it does support pluggable authentication, so we could roll our own if someone gets ambitious19:10
* anteaya ladles on more gratitude19:10
*** Swami has joined #openstack-meeting19:10
*** Swami_ has joined #openstack-meeting19:10
mordredanteaya: I read that as gravy19:11
anteayamordred, when did you last eat?19:11
anteayamight you be hungry?19:11
fungiyeah, now i want to go find food after this meeting19:11
mordredanteaya: about 15 minutes ago ... but gravy is always good19:11
fungigood gravy19:11
clarkb#topic Priority efforts19:11
*** openstack changes topic to "Priority efforts (Meeting topic: infra)"19:11
* clarkb takes gravy as the cue we are ready for next topic :)19:11
anteayaclarkb, good pickup19:12
fungiall topics are now gravy19:12
clarkbwe'll start with storyboard. Looks like migrations continue. Heat is done and loci is in the queue?19:12
fungiyeah, heat was a massive import19:12
fungi>5k bugs19:12
fungier, >4k bugs19:12
fungistill a lot19:12
fungitook in the neighborhood of 12-14 hours to import, i think19:13
fungiloci should be quick by comparison19:13
diablo_rojoPoked at the next tripleo squad again too- trying to get them on the schedule of migrations19:13
anteayamany things will be quick by comparison19:13
anteayamy flight to vancouver will be quick by comparison19:14
diablo_rojomordred, nothing compared to what neutron and nova will be (I tried to do a test of the neutron one and it ran for a week before I stopped it)19:14
fungithe model there is sort of weird though. i'm not entirely convinced it will make sense for them to import all tripleo bugs into tripleo-ci but start by only importing the ones tagged as security and then import the others into the same project later19:14
*** VW_ has quit IRC19:15
fungier, into tripleo-common19:15
funginot tripleo-ci19:15
diablo_rojofungi, agreed19:15
diablo_rojoI think making a repo for them would make more sense19:15
fungiany bugs which are already in lp and then after the import they add the security tag... do those need to get closed and reopened in storyboard? no idea19:15
*** jamesmcarthur has quit IRC19:16
diablo_rojoIts definitely messy.19:16
fungithe tripleo leadership have expressed concerns that having storyboard tasks tied to repositories isn't compatible with their workflow and they'd rather just have all tasks be for their team19:16
diablo_rojoThen they should all go at once rather than squad by squad19:17
*** sshank has quit IRC19:17
diablo_rojoprobably should at least19:17
clarkbfungi: that is how they operate in lp I guess?19:17
*** rpioso|afk is now known as rpioso19:17
*** jamesmcarthur has joined #openstack-meeting19:18
fungiyeah, there is a "tripleo" project in lp and then they add bug tags to indicate which subteams are working on what bugs, seems like19:18
fungiso anyway, the closest we have under our current model (there is no "tripleo" repo) is to migrate their bugs to have tasks for the tripleo-common repo19:19
fungibut as diablo_rojo notes, their desire to migrate subteam at a time makes this extra weird19:19
mordredthat seems weird to me as well - and something that seems pretty rife for confusion and stress while it's happening19:20
clarkbis that something we should try to have a more direct conversation with the tripleo team about?19:20
clarkb(thinking with summit coming up that may be an opportunity there)19:21
*** VW has joined #openstack-meeting19:21
fungiwhile that would probably be useful, i think i'm booked solid by this point19:21
diablo_rojoWe can add it to the agenda for the storyboard forum session monday19:22
clarkbya I feel that way too19:22
fungiunless we can somehow have that conversation while i'm asleep19:22
diablo_rojoif they can make it19:22
clarkbfungi: or corner mwhahaha and EmilienM_PTO in a bar on tuesday19:22
fungii predict i'll be having many conversations while asleep by the last day19:22
* mwhahaha disagrees with the confusion part but whatever19:22
mordredfungi: we're allowed to sleep at the summit?19:23
clarkbmordred: you aren't19:23
mwhahahai won't be at summit, but i'd be happy to have a chat about it sooner, as we need to figure out the migration to storyboard anyway19:23
diablo_rojomwhahaha, would you be able to make it to the Storyboard session Monday?19:23
mwhahahatl;dr, we probably should just mass cutover sooner but i need to sent a note to th eml this week19:23
mwhahahathis subteam move probably isn't working out19:24
*** e0ne has quit IRC19:24
clarkbcool sounds like we should be able to sort something out then19:24
clarkb(both parties are motivated etc)19:25
diablo_rojomwhahaha, it worked for a few of the squads, but yeah its probably time if we can swing it with your conributors19:25
mwhahahait's not really working cause it's confusing everyone on where to create and there's no fix except duplicating work19:26
*** david-lyle has joined #openstack-meeting19:27
fungithat's the sort of confusion i was concerned partial migration would cause19:27
clarkbalright are we ready to move on to the next topic?19:29
clarkb#topic Modern Config Management19:29
*** openstack changes topic to "Modern Config Management (Meeting topic: infra)"19:29
clarkb#link https://review.openstack.org/449933 Puppet 4 Infra19:29
clarkb#link https://review.openstack.org/469983 Ansible Infra19:29
clarkb#link https://review.openstack.org/565550 Containerized infra19:29
clarkbNow that we've had a chance to read these through and consider them, what are our thoughts/impressiosn?19:30
mordredpabelanger pointed out that ansible and container potentially share a common base19:30
*** psachin` has quit IRC19:30
clarkbthat is the setup email and users and install docker portion right?19:31
mordredso if we like either of the two of them, it might be worth splitting out an ansible-base spec to describe that portion19:31
mordredclarkb: yah19:31
corvusyeah, and to some extent, we may end up with some hosts where we have some ansible and no containers (eg, afs servers).  it may really be a matter of degree?19:31
mordredand how to deal with hiera/secrets19:31
mordredcorvus: ++19:31
*** dbecker has quit IRC19:31
pabelangerI am however, liking puppet-4 (I guess 5 because of bionic) as it might be less work19:31
corvusi'm leaning toward the container approach, mostly because it completely decouples us from operating system dependencies19:32
clarkbmy initial impression was that puppet 4 and then 5 feel like less upfront work. Like we can probably get to 4 in a week or two. But then persistent issues like bionic not having puppet 5 packages and the weird renaming of silly things and distros undoing that seems like pain I'd like to avoid19:32
mordredI would prefer either ansible or container specs (or some combo of the two) - but obvs sinceI wrote it I prefer the container one19:32
cmurphyi'm trying to verify whether puppet 4 will be supported on bionic, i think it will be19:32
mordredcorvus: ++ - that's my main motivation from it - that and it shifts some burden to the ci system19:33
mordredwhich, it turns out, we hae a good one of19:33
clarkband ya I think containerizing applications gives us some new features that will be useful over time that both puppet and ansible largely lack as we'd use them otherwise19:33
pabelangerIf I replace containers with the word packaging, I think I'm okay with them :)  mordred did a good job outlining some use cases I was having trouble seeing19:34
clarkb(whereas puppet and ansible are roughly equivalent in "power"/utility, puppet even has thair own remote ssh tool now (its literally just ansible written in ruby for puppet))19:34
anteayaI'd just like to see whatever the decision is well publicized so that in 2 months when someone says, hey you should all do [thing] someone can point to a url19:34
fungiit's still not clear to me that ditching puppet for $next_thing necessarily fixes the need to periodically update our configuration nor the odds of backward-incompatible changes to file paths over time19:34
mordredpabelanger: \o/ (and yea, that's how I've been thinking of them)19:34
corvuswith puppet, we have to have a working version of puppet on every host, and if that version is different (it often is) things get complicated.  with ansible, we only need a working version of ansible on one host (the controller).  and with containers, because so many of our services are things we run from source, we can drop a lot of the work we're doing to deploy those via a config management19:34
fungiokay, that i find compelling19:35
clarkbcorvus: aiui you can do that with puppet now, though that might require first getting to puppet 5?19:35
clarkbcorvus: they literally implemented ansible remote execution in ruby for puppet resources19:35
fungier, by "that" i mean the ability to not need to install a client/agent on all our various systems19:36
fungiso does actually solve the consistency issue19:36
corvusclarkb: it's a good model19:36
clarkbcorvus: yup, I think ansible sort of proved that point to puppet :)19:36
ianwas i mentioned in my comments, just because the containers are there, still most of the configuration is/can be in puppet?  i mean it's not a thrilling idea to translate huge blobs of erb config templates into jinja just because19:36
corvusthe containers idea further minimizes the ansible we will end up with.19:36
mordredianw: the containers plan ends up with puppet going completely away19:37
mordredianw: and using ansible to template out config files19:37
ianwends up with ... but it's not like we need to have a flag day switch?19:37
pabelangeryah, as I understand it, we'd write the container as Dockerfile, then use ansible to template and bind-mount a config into it19:37
mordred(I agre that translating erb to jinja sounds like unfun)19:37
fungiand to make determinations on what package renames happen between distro versions?19:37
mordredianw: right. we don' tneed to flag day19:37
corvusmordred, ianw: one server at a time, i'd reckon19:38
clarkbya I think any transition to using more ansible would invole puppet_run_all running less "all"19:38
clarkband things being converted being more ansibly19:38
clarkbeventuall all will be an empty set19:38
corvus(i... actually think translating erb to jinja2 sounds fun)19:38
* mordred assigns corvus the erb to jinja2 tasks19:38
corvusbut i can at least agree it's busy work, and it is a cost that we should allocate to the ansible options :)19:38
clarkbI also think in that scenario we'd likely want to continue to keep pupept on enough life support that it is viable until we are off it. Which likely means puppet 4 is still something we'd do? maybe just with less rigorous testing of each application deployment?19:39
pabelangerthe part I didn't fully understand, are we moving away from puppetmaster.o.o to say zuul post pipelines? Or new bastion host?19:39
clarkbpabelanger: I think beacuse puppet remains until we are off of it the initial transition would require a bastion host remains19:40
clarkbthen a future spec could have us switch to zuul directly driving the deployment19:40
mordredpabelanger: I was thinking we keep puppetmaster for now - but we could certainly start triggering some playbooks on it as a static host in a post pipeline19:40
clarkb(basically thats out of scope I think)19:40
mordredclarkb: ++19:40
*** slaweq has joined #openstack-meeting19:41
pabelangerokay, keep in mind, we do need to rebuild that server (since it is trusty)19:41
cmurphyi think moving to puppet 4 is little enough work that we can keep going with it without rejecting future plans19:41
pabelanger(but maybe just inplace upgrade)19:41
corvuspabelanger: yeah, maybe we just punt for 8 months and if it's still important, do an in-place upgrade19:41
corvus(we have a year of trusty remaining)19:42
mordredcmurphy: yah - and puppet needs to stick around for a while anyway for transition purposes19:42
clarkbcmurphy: mordred exactly19:42
*** awaugama has quit IRC19:42
mordredthere's a little handwavey in the container spec about hiera/secrets and inventory that I think we should likely do some POCs of options19:43
fungiso it's feeling like we have a little of all three specs we could consider in tandem?19:44
ianwcmurphy: ++ i still see having puppet4 in the mix as useful over the medium term19:44
fungicontinue with puppet 4 uplift, get ansiblification working, possibly tack on containerization?19:44
clarkbfungi: ya I get the sense what we'll acutally end up with is life support puppet4 short/medium term, transition to ansible base + container application "packaging" longer term, eventually having zuul do deployments (but this last bit should be its own spec)19:45
pabelangerfungi: yah, that order seems right. We'll need ansible in place before containers19:45
corvusfungi: yes, though i'd like us to disambiguate that to remove the 'possibly' :)19:45
*** slaweq has quit IRC19:45
mordredclarkb: ++19:45
clarkbhaving typed that does anyone here think that is a terrible idea just as their initial reaction?19:45
fungisure, having a roadmap is good19:45
mordrednope. I think it's good ... a few pending details notwithstanding19:46
pabelangeryah, I'm willing to try19:46
fungii'm not opposed to just sticking with puppet (i know it, even if it's changing), though i need to get more familiar with ansible/jinja anyway given zuul's use of it...19:46
corvusshould we make a new spec which lays out all 3 things in a single document, or revise the specs to build on each other?19:46
clarkbcorvus: I kinda think one doc will be best for people's understadning if not directly invovled day to day19:47
clarkbmaybe as a next step I should through my summary out to the infra lst today, and if no one objects we can start on making that the future spec?19:47
* mordred can take a stab at that ... programming is harder than text writing right now19:47
clarkbI guess nothing prevents starting to work on that now either if mordred wants to do word typing instead of programming typing19:47
mordredreaching for the special keys is the thing that blows the most19:47
fungiyeah, i can git behind the short-term puppet 4 and medium-term migrate to ansible (if that's what the others who have time to spend on this are interested in doing), but i'm not yet sold on the longer-term containers piece (no offense, mordred)19:48
fungier, get behind19:48
* fungi sighs at finger memory19:48
corvusfungi: i do that all the time19:48
*** diman has joined #openstack-meeting19:48
pabelanger+1 to migration idea19:48
mordredfungi: none taken! having been skeptical myself for a long time I both appreciate and likely agree with at least some if not most of your concerns19:48
clarkbok sounds like we have a plan to make a plan :)19:49
clarkbI'll send that out after lunch then19:49
clarkbbefore we run out of time there is a related topic from pabelanger we should at least touch on19:49
fungii liked planning the plan to make a plan19:49
clarkb#topic General Topics19:49
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:49
clarkbpabelanger brings up a second round of xenial upgrades19:49
clarkbgiven the above soft decision do we think we should continue to push towards xenial?19:49
fungismarcet was asking just today about upgrading openstackid-dev and openstackid.org to xenial so that openstackid can take advantage of newer laravel which needs newer php19:50
corvusfungi: let me know what i can do to convince you -- i'm keen on it not only because it will reduce our deploy-in-config-management footprint, but i think it's coming at an opportune time when we're also at risk of fallout from pip10 and the like, where we might have to be looking at changing our deployment-from-source strategy anyway19:50
corvus[sorry for the topic leak]19:50
pabelangeryah, we have 1 year left on trusty and some long lived servers still to do. At this point, I think it is mostly about scheduling outages19:50
clarkbmy initial thought is since short/medium term we'd be puppet 4ing anyways (likely) that getting to xenial helps us avoid having another factor in the migration process. Basically get it out of the way then migrate applications based on the application not hosting platform19:50
corvus[also, wow, turns out that was actually still relevant to this topic]19:51
clarkbcorvus: :)19:51
clarkbalso getting to systemd across the baord just makes toehr stuff easier19:51
clarkbnot because its systemd but because its consistent19:51
fungiyeah, i wouldn't want the fact that we decide to do do something different in general which we're not quite ready to start implementing yet hold back server upgrades we need19:51
clarkb(don't panic systemd haters :) )19:52
mordredclarkb: agree19:52
corvusi imagine we don't want to touch openstackid for the next 3 weeks anyway?19:52
clarkbcorvus: ++19:52
fungicorvus: that would be a great question for smarcet &co19:52
pabelangeryah, https://ethercalc.openstack.org/osiuhjzjq336 is the propose week for sprints19:52
pabelangerwhich is after summit19:52
pabelangerr-11, r-10, r-0919:53
fungii sure hope they're not wanting to switch platforms for it right before the summit, right19:53
clarkb#link https://ethercalc.openstack.org/osiuhjzjq336 help select a week for a xenial upgrade sprint19:53
*** diman has quit IRC19:53
pabelangerand https://etherpad.openstack.org/p/infra-sprint-xenial-upgrades-part2 has a list of servers we still need to migrate19:53
clarkb#link https://etherpad.openstack.org/p/infra-sprint-xenial-upgrades-part2 servers that still need to migrate to xenial19:53
clarkbif interesting in helping out please indicate your availability19:54
clarkbI do think it would be wortwhile and helpful19:55
pabelangerit was also a great learning experience for new infra-root19:55
clarkbalright we have 5 minutes left I'll open the floor to anything else19:55
clarkb#topic Open Discussion19:55
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:55
clarkbI heard a rumor of zuul stickers so keep space for those :P19:56
clarkbI also still have more infra ant stickers if you want them19:56
pabelangerclarkb: sounds like team dinner is monday night?19:57
clarkboh right I proposed monday night at a brewpub near to the convention center. I think we can swing that without going through too much official paper pushing19:57
clarkb(I don't want to pay a deposit on a room then sort out paying with a single card)19:57
anteayaclarkb, good call19:57
fungisounds good to me19:58
clarkbthe proposed location seems quite large, has pool tables and brew their own beer. Food wise they have vegetarian options and gluten free looks like but not vegan or at least nothign screams vegan19:58
clarkbif for some reason you don't like this option I'm totally open to alternatives I'll just be asking that you do some of the leg work too :)19:59
clarkblet me know19:59
*** markstur has quit IRC19:59
fungii'm up for losing a few rounds of pool19:59
clarkband we are at time. Thanks everyone20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:00
openstackMeeting ended Tue May  8 20:00:08 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-05-08-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-05-08-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-05-08-19.01.log.html20:00
*** munimeha has joined #openstack-meeting20:00
*** julim has joined #openstack-meeting20:01
*** radeks__ has joined #openstack-meeting20:04
*** radeks_ has quit IRC20:05
*** radeks has quit IRC20:06
*** esberglu has quit IRC20:07
*** markstur has joined #openstack-meeting20:11
*** rmascena has quit IRC20:12
*** jamesmca_ has joined #openstack-meeting20:15
*** jamesmca_ has quit IRC20:17
*** jamesmcarthur has quit IRC20:18
*** jamesmcarthur has joined #openstack-meeting20:18
*** jamesmcarthur has quit IRC20:18
*** esberglu has joined #openstack-meeting20:19
*** e0ne has joined #openstack-meeting20:20
*** pcaruana has quit IRC20:21
*** julim has quit IRC20:24
*** dklyle has quit IRC20:32
*** edmondsw has quit IRC20:33
*** jamesmcarthur has joined #openstack-meeting20:37
*** hemna_ has quit IRC20:41
*** e0ne has quit IRC20:45
*** ttsiouts_ has joined #openstack-meeting20:46
*** diman has joined #openstack-meeting20:49
*** slaweq has joined #openstack-meeting20:49
*** andreas_s has joined #openstack-meeting20:52
*** radeks__ has quit IRC20:53
*** arnewiebalck_ has quit IRC20:54
*** diman has quit IRC20:54
*** ykatabam has quit IRC20:57
*** ayoung-dentist is now known as ayoung20:57
*** andreas_s has quit IRC20:57
*** tssurya has quit IRC20:59
*** dustins has quit IRC21:09
*** jamesmcarthur has quit IRC21:09
*** diman has joined #openstack-meeting21:12
*** hemna_ has joined #openstack-meeting21:13
*** felipemonteiro_ has joined #openstack-meeting21:13
*** bobh has quit IRC21:13
*** ianychoi has quit IRC21:15
*** felipemonteiro__ has quit IRC21:17
*** diman has quit IRC21:17
*** rbudden has quit IRC21:19
*** david-lyle has quit IRC21:23
*** VW_ has joined #openstack-meeting21:31
*** VW has quit IRC21:35
*** VW_ has quit IRC21:36
*** felipemonteiro__ has joined #openstack-meeting21:38
*** felipemonteiro_ has quit IRC21:38
*** markvoelker_ has joined #openstack-meeting21:41
*** markvoelker has quit IRC21:42
*** ttsiouts_ has quit IRC21:48
*** diman has joined #openstack-meeting21:53
*** manjeets_ has quit IRC21:53
*** diman has quit IRC21:57
*** bobh has joined #openstack-meeting21:58
*** ykatabam has joined #openstack-meeting22:02
*** esberglu has quit IRC22:12
*** rwsu has quit IRC22:13
*** jamesmcarthur has joined #openstack-meeting22:18
*** mlavalle has left #openstack-meeting22:22
*** jamesmcarthur has quit IRC22:22
*** rcernin has joined #openstack-meeting22:25
*** felipemonteiro_ has joined #openstack-meeting22:34
*** zhhuabj has quit IRC22:36
*** felipemonteiro__ has quit IRC22:37
*** julim has joined #openstack-meeting22:38
*** diman has joined #openstack-meeting22:47
*** hongbin has quit IRC22:48
*** diman has quit IRC22:51
*** julim has quit IRC22:52
*** julim has joined #openstack-meeting22:53
*** slaweq has quit IRC22:57
*** tpsilva has quit IRC22:58
*** felipemonteiro__ has joined #openstack-meeting23:04
*** felipemonteiro_ has quit IRC23:04
*** dmacpher has quit IRC23:11
*** ssbarnea_ has quit IRC23:13
*** felipemonteiro__ has quit IRC23:14
*** julim has quit IRC23:18
*** julim has joined #openstack-meeting23:28
*** munimeha has quit IRC23:30
*** janzian has quit IRC23:31
*** bkopilov_ has quit IRC23:31
*** bkopilov__ has quit IRC23:32
*** abalutoiu_ has quit IRC23:41
*** bkopilov__ has joined #openstack-meeting23:44
*** bkopilov_ has joined #openstack-meeting23:44
*** ykatabam has quit IRC23:47
*** ykatabam has joined #openstack-meeting23:48
*** bkopilov__ has quit IRC23:52
*** bkopilov_ has quit IRC23:52

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