Tuesday, 2018-09-04

*** longkb has joined #openstack-meeting00:21
*** Nel1x has joined #openstack-meeting00:57
*** hongbin has joined #openstack-meeting00:58
*** ykatabam has joined #openstack-meeting01:02
*** SpamapS has joined #openstack-meeting01:17
*** rcernin has quit IRC01:24
*** rcernin has joined #openstack-meeting01:24
*** bzhao__ has joined #openstack-meeting01:27
*** fried_rice is now known as efried01:27
*** apetrich has quit IRC01:28
*** ricolin has joined #openstack-meeting01:30
*** erlon has quit IRC01:31
*** tetsuro has joined #openstack-meeting01:47
*** yamamoto has quit IRC01:50
*** tetsuro has quit IRC01:53
*** yamamoto has joined #openstack-meeting02:11
*** larainema has joined #openstack-meeting02:22
*** erlon has joined #openstack-meeting02:38
*** psachin has joined #openstack-meeting02:41
*** sagara has joined #openstack-meeting03:01
*** arne_wiebalck has quit IRC03:07
*** arne_wiebalck has joined #openstack-meeting03:08
*** Nel1x has quit IRC03:14
*** erlon has quit IRC03:17
*** tpatil has joined #openstack-meeting03:54
*** samP has joined #openstack-meeting04:00
samP#startmeeting masakari04:01
openstackMeeting started Tue Sep  4 04:01:01 2018 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.04:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:01
*** openstack changes topic to " (Meeting topic: masakari)"04:01
openstackThe meeting name has been set to 'masakari'04:01
samPHi all for Masakari04:01
samPsagara: Hi04:01
samPtpatil: Hi04:02
samPlet's start04:02
samP#topic bugs/issues04:02
*** openstack changes topic to "bugs/issues (Meeting topic: masakari)"04:02
samP#link https://review.openstack.org/#/q/topic:bug/1779752+(status:open+OR+status:merged)04:03
tpatilsamP: I have noticed you have approved 3-4 patches. Zuul is failing for one patch, We will fix this issue soon04:03
tpatil#link : https://review.openstack.org/#/c/590735/04:03
tpatilZuul requirements-check job is failing, we will look into this issue04:03
tpatilTo merge these patches, we need another +204:04
*** psachin has quit IRC04:04
tpatilsamara: Can you please review these patches?04:04
samPMy bad, I think we have to put requirement job for non-voting04:04
tpatilsorry, it mean sagara04:04
tpatilI mean sagara04:05
samPAs in here,04:06
samP#link https://review.openstack.org/#/c/588157/3/.zuul.yaml04:06
*** psachin has joined #openstack-meeting04:06
sagaratpatil: OK, I'll check it from now04:06
tpatilsagara: As I'm included in co-author, I'm not approving these patches04:07
sagaratpatil: OK, understood that04:08
samPI think first we have to import zuul jobs as proposed in here,04:10
samP#link https://review.openstack.org/#/c/592980/04:10
samPThen make requirements-check voting to false04:11
tpatilsamP: We will do the needful04:12
samPtpatil: thanks04:12
samP#link https://review.openstack.org/#/c/591557/04:13
samP#link https://review.openstack.org/#/c/562973/04:13
samPBoth LGTM. Thanks.04:14
samPI would like to backport them to rocky.04:14
tpatilsamP: We will do the needful04:14
samPtpatil: thanks04:15
samPAny other patches/bugs to discuss/04:15
samPif any please bring them up anytime.04:16
samPlet't move to next topic04:16
samP#topic PTG04:16
*** openstack changes topic to "PTG (Meeting topic: masakari)"04:16
samP#link https://etherpad.openstack.org/p/masakari-ptg-stein04:16
samPThanks for adding topics04:17
tpatilI have proposed few topics which I would like to see in Stein release04:17
samPtpatil: thanks.04:19
tpatilsamP: Are you planning to merge masakari-monitors functionality in openstack-dev resource agents?04:19
samPI guess we both added functional tests, so I'm gonna remove mine04:19
tpatilfunctional tests for openstacksdk04:20
samPtpatil: ah.. yes. Then that is a different one04:20
tpatiladding  functional tests in masakari and openstacksdk is almost same04:20
tpatilnot openstack-dev resource agents, I mean to say openstack resource agents04:21
samPtpatil: About openstack resource agents, I would like to discuss this topic on PTG04:22
tpatilThe reason to ask this questions is becoz, we are planning to add support in ansible and devstack for masakari-monitors04:23
samPtpatil: In that case, we will use masakari-monitors. With considering current functionality of the masakari monitors,04:24
tpatilWe can have this kind of discussion during PTG04:24
samPopenstack resource agents are not a 100% replacement for masakari monitors04:25
samPI would like to discuss this with aspiers about this on PTG04:25
tpatilsamP: Ok04:26
samPI will try put more details into etherpad before PTG04:27
samPReally sorry, but I only attend on Monday(9/10) and Tuesday(9/11) for PTG04:28
samPAre you will be there on Tuesday for masakari meeting?04:30
tpatilsamP: I think two days are long enough to discuss all topics04:30
samPtpatil: MF, we officially have one day :)04:32
samPHowever, I am available on Monday also, if anyone wants to discuss04:33
samPWe can use free area04:33
*** Bhujay has joined #openstack-meeting04:33
samPThat's all the topics from my side04:34
tpatilNext meeting, in Denver, it will be 10:00 P.M. If required I can join. But I think most of us will be in Denver so we can skip next meeting04:34
samPAh, yes. I think we have already agree to sikp next meeting..04:35
samPLet's skip the next meeting, since all of us in PTG.04:35
samPOr, if anyone needs to discuss any issues, please send the email to openstaci-dev with [masakari]04:36
samPwe can re-consider about the next week meeting04:37
samP#topic AOB04:37
*** openstack changes topic to "AOB (Meeting topic: masakari)"04:37
samPAny other items to discuss/04:37
samPIf not, we can conclude today's meeting.04:38
tpatilNo other topics to be discussed from my end04:39
samPah we have to take, Team Photo on PTG04:39
samPI will put details into etherpad04:39
samPtpatil: Thanks04:40
tpatilLooking forward to see you all in PTG04:40
samPOK then, C U all in PTG04:41
samPsave travel!04:41
samPThank you all for your time.04:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:42
openstackMeeting ended Tue Sep  4 04:42:00 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-09-04-04.01.html04:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-09-04-04.01.txt04:42
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-09-04-04.01.log.html04:42
*** janki has joined #openstack-meeting04:42
*** tpatil has quit IRC04:43
*** samP has left #openstack-meeting04:45
*** ykatabam has quit IRC04:57
*** hongbin has quit IRC04:58
*** ykatabam has joined #openstack-meeting04:59
*** e0ne has joined #openstack-meeting05:13
*** dtroyer has quit IRC05:49
*** mugsie has quit IRC05:49
*** zigo has quit IRC05:49
*** dtroyer has joined #openstack-meeting05:49
*** trinaths has joined #openstack-meeting06:01
*** ykatabam has quit IRC06:02
*** sridharg has joined #openstack-meeting06:07
*** ykatabam has joined #openstack-meeting06:12
*** Bhujay has quit IRC06:16
*** ykatabam has quit IRC06:17
*** ykatabam has joined #openstack-meeting06:18
*** ricolin has quit IRC06:22
*** psachin has quit IRC06:25
*** psachin has joined #openstack-meeting06:30
*** rcernin has quit IRC06:33
*** kopecmartin has joined #openstack-meeting06:33
*** Bhujay has joined #openstack-meeting06:38
*** ykatabam has quit IRC06:43
*** e0ne has quit IRC06:44
*** apetrich has joined #openstack-meeting06:59
*** sridharg has quit IRC07:08
*** alexchadin has joined #openstack-meeting07:33
*** apetrich has quit IRC07:41
*** tssurya has joined #openstack-meeting07:45
*** gibi has joined #openstack-meeting07:45
*** dkushwaha has joined #openstack-meeting07:48
*** joxyuki has joined #openstack-meeting07:58
*** phuoc has joined #openstack-meeting07:59
*** hadai has joined #openstack-meeting08:01
dkushwaha#startmeeting tacker08:02
openstackMeeting started Tue Sep  4 08:02:37 2018 UTC and is due to finish in 60 minutes.  The chair is dkushwaha. 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
dkushwaha#topic Roll Call08:02
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"08:02
dkushwahahi phuoc, joxyuki08:03
*** ykatabam has joined #openstack-meeting08:03
*** Emine has joined #openstack-meeting08:05
dkushwahait seems less team members are available08:05
dkushwahalets wait for couple of minutes08:05
longkbo/ Tacker folks :D08:06
dkushwahahi longkb08:06
dkushwahahi trinaths08:06
dkushwahaok lets start..08:07
dkushwaha#chair phuoc08:07
openstackCurrent chairs: dkushwaha phuoc08:07
dkushwaha#topic Announcements08:07
*** openstack changes topic to "Announcements (Meeting topic: tacker)"08:07
dkushwahaOpenStack rocky release in last week.08:08
dkushwaha#link https://releases.openstack.org/rocky/08:08
longkbo/ nguyenhai93 :D08:08
dkushwahaWe are now in Stein08:08
dkushwahain Rocky, Tacker contributions ranked 37 in review, and 53 in commits08:10
dkushwaha#link http://stackalytics.com/?release=rocky&metric=marks08:10
dkushwaha#topic BPs08:11
*** openstack changes topic to "BPs (Meeting topic: tacker)"08:11
dkushwahaI have started drafting spec for resources force delete feature08:11
trinathsok. can you give the link08:12
dkushwaha#link https://blueprints.launchpad.net/tacker/+spec/force-delete-resources08:12
dkushwahatrinaths, thanks08:12
*** priteau has joined #openstack-meeting08:12
dkushwahain this week i will submit the patch08:12
phuocthat's great :)08:12
longkbdkushwaha: I thinks it would be RFE rather than blueprint08:13
*** apetrich has joined #openstack-meeting08:13
dkushwahalongkb, we need it for all resources(VNF, VNFFG etc..), so I think it will be good to have BP08:14
longkb+1 dkushwaha. Please go ahead :D08:15
dkushwaha#topic python3-first08:15
*** openstack changes topic to "python3-first (Meeting topic: tacker)"08:15
dkushwahawe have multiple patches for python3-first08:16
dkushwaha#link https://review.openstack.org/#/q/topic:python3-first+status:open+(projects:openstack/tacker++OR+project:openstack/python-tackerclient+)08:16
dkushwahaAll these are small patches, Please review it, so that it can be merged soon.08:16
dkushwahaphuoc, joxyuki longkb trinaths ^^08:17
phuocyes, I will look at them08:18
longkb+Infinity phuoc :D08:18
dkushwahaphuoc, Thanks08:18
nguyenhai93I think no problem for those patches08:19
*** alexchadin has quit IRC08:19
dkushwaha#topic BP: reservation-vnf08:20
*** openstack changes topic to "BP: reservation-vnf (Meeting topic: tacker)"08:20
dkushwahajoxyuki, Do you any update on that?08:20
dkushwaha#link https://blueprints.launchpad.net/tacker/+spec/reservation-vnfm08:20
joxyukidkushwaha, yes, but I still work on it.08:21
*** ricolin has joined #openstack-meeting08:21
joxyukiit will be updated in 2 week.08:21
dkushwahajoxyuki, ok.08:21
dkushwahajoxyuki, thanks08:22
dkushwaha#topic Open Discussion08:23
*** openstack changes topic to "Open Discussion (Meeting topic: tacker)"08:23
dkushwahaphuoc, do you have something to talk ?08:23
phuocI have plan to support kuryr-kubernetes in Tacker08:24
dkushwahaphuoc, link please08:24
phuochere it is08:25
dkushwahaphuoc, great08:26
dkushwahaphuoc, ok , I will review it08:26
phuocI will support upgrade Tacker template to newest ETSI TOSCA https://review.openstack.org/#/c/58307408:27
dkushwahaphuoc, you mean with heat-translator and tosca-parser side too?08:28
phuocyes, I think I have some knowledge about them, I hope I can put my effort to do it :)08:29
dkushwahaphuoc, Thnks, This will be very helpful to move forward quickly.08:30
dkushwahatrinaths, nguyenhai93 longkb  anything else08:32
longkbNothing from me :)08:32
nguyenhai93no from me08:32
trinathsnothing from my end. :)08:32
dkushwahaFolks, we have to plan our PTG08:33
dkushwahaPlease put your idea in etherpad for this vPTG08:34
dkushwaha#link https://etherpad.openstack.org/p/Tacker-PTG-Stein08:34
dkushwahaplease lat me me know, when we can schedule.08:34
dkushwahaplease suggest, I will create google poll for that, and will schedule accordingly08:36
*** bhagyashris_ has joined #openstack-meeting08:36
phuocthank dkushwaha  :)08:36
*** e0ne has joined #openstack-meeting08:37
phuochi bhagyashris_08:37
bhagyashris_Hi phuoc08:37
dkushwahais it ok to plan sometime in between 19 to 21 Sep ?08:37
phuocwe are planning Tackerr PTG, https://etherpad.openstack.org/p/Tacker-PTG-Stein08:38
dkushwahahi bhagyashris_08:38
joxyukiok for me08:38
phuocif you have something to talk, you can talk here08:38
phuocor update thatt pad08:38
bhagyashris_dkushwaha: Hi08:39
dkushwahajoxyuki, Thanks08:39
phuocdkushwaha, it's fine for me08:39
bhagyashris_Joxyuki: Hi,08:40
joxyukibhagyasris_, hi08:40
bhagyashris_Thank for this https://etherpad.openstack.org/p/Tacker-PTG-Stein actually I was waiting for this link08:40
dkushwahaphuoc, thanks08:40
nguyenhai93ah, one more thing08:41
nguyenhai93this patch is very long time ago08:41
nguyenhai93it should be handled.08:41
nguyenhai93also, Tacker should move to storyboard08:42
trinathsthe patch still fails.08:42
*** yamamoto has quit IRC08:43
*** d0ugal has quit IRC08:43
dkushwahanguyenhai93, just commented on that08:44
dkushwahanguyenhai93, I tried it on my local env, but it was success there08:44
bhagyashris_i would like to share we can add the link: https://etherpad.openstack.org/p/Tacker-PTG-Stein in https://wiki.openstack.org/wiki/PTG/Stein/Etherpads that will be useful to all not sure how to add08:44
dkushwahaThanks bhagyashris_ I will add it08:45
bhagyashris_ok :)08:46
dkushwaha#action dkushwaha will add PTG etherpad link in  https://wiki.openstack.org/wiki/PTG/Stein/Etherpads08:46
dkushwahanguyenhai93, Ok, I will check that patch again08:47
dkushwaha#action dkushwaha will create google poll for vPTG and share it on mail08:48
dkushwahaThats all from my side.08:49
dkushwahaanything else..08:49
*** psachin has quit IRC08:50
*** tonyb has quit IRC08:50
dkushwahaThanks Folks , closing this meeting08:50
bhagyashris_Just one query where will discussion conduct in the PTG08:50
*** ttsiouts has joined #openstack-meeting08:51
bhagyashris_I mean any room assign for tacker discussion08:51
dkushwahaI will share channel name, like bluejeanse08:51
dkushwahabhagyashris_, ^^08:51
bhagyashris_Thank you :)08:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:51
openstackMeeting ended Tue Sep  4 08:51:53 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2018/tacker.2018-09-04-08.02.html08:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2018/tacker.2018-09-04-08.02.txt08:51
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2018/tacker.2018-09-04-08.02.log.html08:51
*** trinaths has left #openstack-meeting08:54
*** hadai has quit IRC08:55
*** phuoc has left #openstack-meeting08:59
*** joxyuki has left #openstack-meeting08:59
*** d0ugal has joined #openstack-meeting09:03
*** psachin has joined #openstack-meeting09:03
*** ttsiouts has quit IRC09:06
*** ttsiouts has joined #openstack-meeting09:06
*** electrofelix has joined #openstack-meeting09:14
*** yamamoto has joined #openstack-meeting09:19
*** dkushwaha has left #openstack-meeting09:22
*** ykatabam has quit IRC09:40
*** tonyb has joined #openstack-meeting09:53
*** psachin has quit IRC10:06
*** longkb has quit IRC10:06
*** yamamoto has quit IRC10:11
*** yamamoto has joined #openstack-meeting10:11
*** bhagyashris_ has quit IRC10:14
*** yamamoto has quit IRC10:20
*** ttsiouts has quit IRC10:26
*** ykatabam has joined #openstack-meeting10:34
*** yamamoto has joined #openstack-meeting10:44
*** mugsie has joined #openstack-meeting10:46
*** masahito has joined #openstack-meeting10:51
*** masahito has quit IRC10:51
*** masahito has joined #openstack-meeting10:52
*** erlon has joined #openstack-meeting10:58
*** takamatsu has joined #openstack-meeting11:00
*** andreaf has joined #openstack-meeting11:05
*** dangtrinhnt has left #openstack-meeting11:13
*** ttsiouts has joined #openstack-meeting11:23
*** beagles has joined #openstack-meeting11:31
*** alexchadin has joined #openstack-meeting11:34
*** sagara has quit IRC11:37
*** masahito has quit IRC11:40
*** masahito has joined #openstack-meeting11:41
*** jaypipes has joined #openstack-meeting11:44
*** ykatabam has quit IRC11:54
*** sambetts_ has quit IRC11:55
*** dims has joined #openstack-meeting11:56
*** sambetts_ has joined #openstack-meeting11:57
*** ttsiouts has quit IRC12:04
*** ttsiouts has joined #openstack-meeting12:05
*** eharney has joined #openstack-meeting12:06
*** masahito has quit IRC12:07
*** masahito has joined #openstack-meeting12:07
*** ttsiouts_ has joined #openstack-meeting12:07
*** trozet has joined #openstack-meeting12:08
*** ttsiouts_ has quit IRC12:09
*** ttsiouts has quit IRC12:09
*** ttsiouts has joined #openstack-meeting12:10
*** raildo has joined #openstack-meeting12:16
*** tpsilva has joined #openstack-meeting12:18
*** trozet has quit IRC12:29
*** ttsiouts has quit IRC12:32
*** larainema has quit IRC12:37
*** ttsiouts has joined #openstack-meeting12:41
*** jamesmcarthur has joined #openstack-meeting12:46
*** masahito has quit IRC12:48
*** masahito has joined #openstack-meeting12:53
*** mriedem has joined #openstack-meeting12:53
*** r-mibu has joined #openstack-meeting13:01
*** bobh has joined #openstack-meeting13:04
*** jamesmcarthur has quit IRC13:05
*** munimeha1 has joined #openstack-meeting13:06
*** awaugama has joined #openstack-meeting13:06
*** masahito has quit IRC13:08
*** masahito has joined #openstack-meeting13:09
*** masahito has quit IRC13:12
*** masahito has joined #openstack-meeting13:16
*** lbragstad has joined #openstack-meeting13:19
*** masahito has quit IRC13:19
*** masahito has joined #openstack-meeting13:20
*** masahito has quit IRC13:22
*** masahito has joined #openstack-meeting13:22
*** masahito has quit IRC13:26
*** masahito has joined #openstack-meeting13:27
*** annabelleB has joined #openstack-meeting13:42
*** jamesmcarthur has joined #openstack-meeting13:45
*** bdperkin has quit IRC13:47
*** masahito has quit IRC13:47
*** masahito has joined #openstack-meeting13:47
*** masahito has quit IRC13:53
*** bobh_ has joined #openstack-meeting13:54
*** masahito has joined #openstack-meeting13:55
*** masahito has quit IRC13:56
*** aojea has joined #openstack-meeting13:57
*** bobh has quit IRC13:58
*** ttsiouts has quit IRC13:59
*** cmart has joined #openstack-meeting14:02
*** iyamahat has joined #openstack-meeting14:04
*** johnsom has joined #openstack-meeting14:06
*** tidwellr has joined #openstack-meeting14:08
*** ijw has joined #openstack-meeting14:08
*** Bhujay has quit IRC14:17
*** mjturek has joined #openstack-meeting14:19
*** bdperkin has joined #openstack-meeting14:19
*** eharney has quit IRC14:20
*** alexchadin has quit IRC14:22
*** annabelleB has quit IRC14:26
*** alexchadin has joined #openstack-meeting14:26
*** ttsiouts has joined #openstack-meeting14:27
*** zaneb has quit IRC14:29
*** zaneb has joined #openstack-meeting14:29
*** aagate has joined #openstack-meeting14:31
*** annabelleB has joined #openstack-meeting14:31
*** zaneb has quit IRC14:33
*** zbitter has joined #openstack-meeting14:34
*** zbitter has quit IRC14:36
*** jamesmcarthur has quit IRC14:36
*** zaneb has joined #openstack-meeting14:36
*** annabelleB has quit IRC14:42
*** dtrainor has joined #openstack-meeting14:42
*** hongbin has joined #openstack-meeting14:44
*** sridharg has joined #openstack-meeting14:45
*** annabelleB has joined #openstack-meeting14:51
*** dklyle has joined #openstack-meeting14:58
*** jamesmcarthur has joined #openstack-meeting14:59
*** yamamoto has quit IRC15:05
*** yamamoto has joined #openstack-meeting15:05
*** beekneemech is now known as bnemec15:06
*** lamt has joined #openstack-meeting15:07
*** zaneb has quit IRC15:12
*** zbitter has joined #openstack-meeting15:12
*** dklyle has quit IRC15:13
*** dklyle has joined #openstack-meeting15:14
*** zbitter has quit IRC15:14
*** cloudrancher has joined #openstack-meeting15:14
*** zbitter has joined #openstack-meeting15:14
*** zbitter is now known as zaneb15:15
*** cloudrancher has quit IRC15:21
*** cloudrancher has joined #openstack-meeting15:27
*** mjturek has quit IRC15:28
*** armax has joined #openstack-meeting15:31
*** Emine has quit IRC15:31
*** cloudrancher has quit IRC15:34
*** alexchadin has quit IRC15:35
*** alexchadin has joined #openstack-meeting15:36
*** armax has quit IRC15:36
*** alexchadin has quit IRC15:36
*** alexchadin has joined #openstack-meeting15:36
*** alexchadin has quit IRC15:37
*** alexchadin has joined #openstack-meeting15:37
*** alexchadin has quit IRC15:37
*** alexchadin has joined #openstack-meeting15:38
*** alexchadin has quit IRC15:38
*** jamesmcarthur has quit IRC15:43
*** jamesmcarthur has joined #openstack-meeting15:43
*** eharney has joined #openstack-meeting15:45
*** mjturek has joined #openstack-meeting15:48
*** aojea has quit IRC15:52
*** jlvilla-viva is now known as jlvillal15:58
*** yamamoto has quit IRC15:58
*** yamamoto has joined #openstack-meeting15:58
*** mlavalle has joined #openstack-meeting15:59
slaweq_#startmeeting neutron_ci16:00
openstackMeeting started Tue Sep  4 16:00:05 2018 UTC and is due to finish in 60 minutes.  The chair is slaweq_. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
*** annabelleB has quit IRC16:00
slaweq_ok, let's start16:00
slaweq_#topic Actions from previous meetings16:00
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:01
slaweq_mlavalle to check another cases of failing neutron_tempest_plugin.scenario.test_dns_integration.DNSIntegrationTests.test_server_with_fip test16:01
mlavalleI did16:01
mlavalleI checked other ocurrences of this bug16:01
mlavalleI found that not only happend with the DNS integration job16:01
mlavallebut in other jobs as well16:01
mlavallealso found that the evidence points to a problem with Nova16:02
mlavallewhich never rumes the instance16:02
slaweq_did You talk with mriedem about that?16:02
mlavalleit seems to me the compute manager is mixing up the events from Neutron and the virt layer16:02
mlavalleI pinged mriedem ealier today....16:02
mlavallebut he hasn't responded. I assume he is busy and will pong back later16:03
mlavalleI will follow up with him16:03
slaweq_ok, good that You are on it :)16:03
slaweq_thx mlavalle16:03
slaweq_#action mlavalle to talk with mriedem about https://bugs.launchpad.net/neutron/+bug/178800616:03
openstackLaunchpad bug 1788006 in neutron "Tests fail with "Server [UUID] failed to reach ACTIVE status and task state "None" within the required time ([INTEGER] s). Current status: BUILD. Current task state: spawning."" [Critical,Confirmed] - Assigned to Miguel Lavalle (minsel)16:03
slaweq_I added action just to not forget it next time :)16:04
mriedemmlavalle: sorry,16:04
mlavalleyeah, please keep me honest16:04
mriedemforgot to reply16:04
*** annabelleB has joined #openstack-meeting16:04
mriedemi'm creating stories for each project today16:04
slaweq_hi mriedem16:04
mriedemoh sorry thought we were talking about the upgrade-checkers goal :)16:04
slaweq_no, we are talking about https://bugs.launchpad.net/neutron/+bug/178800616:05
openstackLaunchpad bug 1788006 in neutron "Tests fail with "Server [UUID] failed to reach ACTIVE status and task state "None" within the required time ([INTEGER] s). Current status: BUILD. Current task state: spawning."" [Critical,Confirmed] - Assigned to Miguel Lavalle (minsel)16:05
mlavallemriedem: when you have time, please look at https://bugs.launchpad.net/neutron/+bug/178800616:05
mlavallemriedem: we think we need help from a Nova expert16:05
* mriedem throws it on the pile16:05
mlavallemriedem: Thanks :-)16:05
slaweq_thx mriedem16:05
slaweq_ok, so let's move on to next actions now16:06
slaweq_mlavalle to check failing router migration from DVR tests16:06
mlavalleI am working on that one right now16:06
mlavallethe migrations failing are always from HA to {dvr, dvr-ha, legacy}16:07
*** yamahata has quit IRC16:07
mlavalleit seems that when you set the admin_state_up to False in the router....16:07
slaweq_yes, but that's related to other bug I think, see https://bugs.launchpad.net/neutron/+bug/178943416:07
openstackLaunchpad bug 1789434 in neutron "neutron_tempest_plugin.scenario.test_migration.NetworkMigrationFromHA failing 100% times" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)16:07
mlavallethe "device_owner":"network:router_ha_interface" never goes down16:07
mlavalleyeah, that is what I am talking about16:08
*** macza has joined #openstack-meeting16:08
mlavalleI have confirmed that is the case for migration from HA to DVR16:09
mlavalleand from HA to HA-DVR16:09
*** alexchadin has joined #openstack-meeting16:10
mlavalleI expect the same to be happening for HA to legacy (or Coke Classic as I think of it)16:10
mlavalleI intend to contnue debugging16:10
slaweq_but that check if ports are down was introduced by me recently, and it was passing then IIRC16:10
mlavalleit is not passing now16:10
slaweq_so was there any other change recently which could cause such issue?16:10
slaweq_yes, I know it is not passing now :)16:10
mlavalleI was about to ask the same....16:11
mlavallethe ports status remains active all the time16:11
haleybso the port doesn't go down, or the interface in the namespace?  as in two routers have active ha ports16:11
mlavallethe test is checking for the status of the port16:12
slaweq_mlavalle: haleyb: this is patch which adds this: https://review.openstack.org/#/c/589410/16:12
mlavallethat's as far as I've checked so far16:12
slaweq_migration from HA tests were passing then16:12
haleybok, so the port, strange16:13
*** ttsiouts has quit IRC16:13
slaweq_yes, that is really strange16:14
*** ttsiouts has joined #openstack-meeting16:14
mlavallewell, that's what the test checks16:14
mlavallethe status of the port16:14
*** alexchadin has quit IRC16:14
slaweq_yes, I added it to avoid race condition during migration from legacy to ha, described in https://bugs.launchpad.net/neutron/+bug/178558216:15
openstackLaunchpad bug 1785582 in neutron "Connectivity to instance after L3 router migration from Legacy to HA fails" [Medium,Fix released] - Assigned to Slawek Kaplonski (slaweq)16:15
mlavalleI remember and logically it makes sense16:16
slaweq_but if router is set to admin_state_down, its ports should be set to down also, right?16:16
slaweq_but mlavalle You can at least repoduce it manually, right?16:16
mlavalleI haven't tried manually yet. That is my next step16:17
slaweq_or ports status is fine during manual actions?16:17
slaweq_ahh, ok16:17
slaweq_so I will add it as action for You for next week, ok?16:17
mlavalleof course16:17
*** Bhujay has joined #openstack-meeting16:17
mlavalleas I said earlier, keep me honest16:17
slaweq_#action mlavalle continue debugging failing MigrationFromHA tests, bug https://bugs.launchpad.net/neutron/+bug/178943416:18
openstackLaunchpad bug 1789434 in neutron "neutron_tempest_plugin.scenario.test_migration.NetworkMigrationFromHA failing 100% times" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)16:18
slaweq_thx mlavalle16:18
slaweq_slaweq to report a bug about timouts in neutron-tempest-plugin-scenario-linuxbridge16:18
slaweq_that was next one16:18
slaweq_I reported it https://bugs.launchpad.net/neutron/+bug/178957916:19
openstackLaunchpad bug 1788006 in neutron "duplicate for #1789579 Tests fail with "Server [UUID] failed to reach ACTIVE status and task state "None" within the required time ([INTEGER] s). Current status: BUILD. Current task state: spawning."" [Critical,Confirmed] - Assigned to Miguel Lavalle (minsel)16:19
*** ttsiouts has quit IRC16:19
slaweq_but it's in fact duplicate of issue mentioned before https://bugs.launchpad.net/neutron/+bug/178800616:19
openstackLaunchpad bug 1788006 in neutron "Tests fail with "Server [UUID] failed to reach ACTIVE status and task state "None" within the required time ([INTEGER] s). Current status: BUILD. Current task state: spawning."" [Critical,Confirmed] - Assigned to Miguel Lavalle (minsel)16:19
*** ricolin has quit IRC16:19
slaweq_so let's move forward16:19
slaweq_next was16:19
slaweq_mlavalle to ask Mike Bayer about functional db migration tests failures16:19
*** annabelleB has quit IRC16:19
mlavalleI also suspect that some of the failures we are getting in the DVR multinode job are also due to this issue with Nova16:19
mlavalleand the others are due to router migration16:20
mlavalleI conclude that from the results of my queries with Kibana16:20
mlavallenow moving on to Mike Bayer16:20
*** annabelleB has joined #openstack-meeting16:20
mlavalleI was going to ping him16:20
mlavallebut the log that is pointed out in the bug doesn't exist anymore16:21
mlavalleand I don't want to ping him if I don't have data for him to look16:21
slaweq_ok, I will update bug report with fresh log today and will ping You16:21
slaweq_fine for You?16:21
mlavalleso let's keep our eyes open for one of those failures16:22
mlavalleas soon as I have one, I'll ping him16:22
slaweq_ok, sounds good16:22
mlavalleI will also update the bug if I find one16:22
slaweq_if I will have anything new, I will update bug16:22
slaweq_last one from last week was16:22
slaweq_slaweq to mark fullstack security group test as unstable again16:22
slaweq_Done: https://review.openstack.org/59742616:22
slaweq_it's merged recently so fullstack tests should be in better shape now16:23
slaweq_and that was all for actions from previous week16:23
slaweq_let's move to next topic16:23
slaweq_#topic Grafana16:23
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:23
*** gyee has joined #openstack-meeting16:24
slaweq_FYI: patch https://review.openstack.org/#/c/595763/ is merged so in graphs we have now also included jobs which were TIMED_OUT16:25
slaweq_speaking about last week, there was spike around 31.08 on many jobs16:26
slaweq_it was related to some infra bug, fixed in https://review.openstack.org/59152716:26
*** janki has quit IRC16:26
*** janki has joined #openstack-meeting16:27
njohnstonJust to note, I have a change to bump the "older" dashboards versions and to bring them in line with slaweq_'s format: https://review.openstack.org/59716816:28
mlavalleyeah I can see that16:28
slaweq_thx njohnston for working on this :)16:28
mlavalleok, so in principle we shouldn't worry about the spike on 8/3116:28
slaweq_and speaking about other things I think we have one main problem now16:29
slaweq_and it's tempest/scenario jobs issue which we already talked about16:29
mlavallethe nova issue?16:30
mlavalleok, I'll stay on top of it16:30
slaweq_this is basically most common issue I found when I was checking for job results16:30
slaweq_and it is quite paintfull as it happens randomly on many jobs so You need to recheck jobs many times and each time different job fails :/16:31
slaweq_because of that it is also not very visible on graphs IMO16:31
mlavallebut the same underlying problem16:31
slaweq_yes, from what I was checking it looks like that, culprit is the same16:32
slaweq_ok, but let's talk about few other issues which I also found :)16:32
slaweq_#topic Tempest/Scenario16:33
*** openstack changes topic to "Tempest/Scenario (Meeting topic: neutron_ci)"16:33
slaweq_so, except this "main" issue I found few times that same shelve/unshelve test was again failing16:33
slaweq_    * http://logs.openstack.org/71/516371/8/check/neutron-tempest-multinode-full/bb2ae6a/logs/testr_results.html.gz16:33
slaweq_    * http://logs.openstack.org/59/591059/3/check/neutron-tempest-multinode-full/72dbf69/logs/testr_results.html.gz16:33
slaweq_    * http://logs.openstack.org/72/507772/66/check/neutron-tempest-multinode-full/aff626c/logs/testr_results.html.gz16:33
slaweq_I think mlavalle You were checking that in the past, right?16:33
mlavalleyeah I think I was16:34
mlavallehow urgent is it compared to the other two I am working on?16:34
slaweq_not very urgent I think16:34
slaweq_I found those 3 examples in last 50 jobs or something like that16:34
mlavalleok, give me an action item, so I remeber16:34
mlavalleI don't want it to fall through the cracks16:35
mlavalleon the understanding that I'll get it to it after the others16:35
slaweq_do You remember bug report for that maybe?16:35
mlavalleslaweq_: don't worry, I'll find it. for the time being just mention the shelve / unshelve issue in the AI16:36
slaweq_mlavalle: ok16:36
*** kopecmartin has quit IRC16:36
slaweq_#action mlavale to check issue with failing test_attach_volume_shelved_or_offload_server test16:36
mlavallethanks :-)16:37
slaweq_thx mlavalle16:37
slaweq_ok, let's move on16:37
slaweq_I also found one more example of another error: http://logs.openstack.org/96/596896/2/check/tempest-full-py3/95eba41/testr_results.html.gz16:37
slaweq_it was some error during FIP deletion16:37
*** janki has quit IRC16:38
slaweq_but rest api call was done to nova: 500 DELETE
slaweq_and I can't find FIP with such uuid in nova-api logs nor neutron-server logs16:40
slaweq_do You maybe know where this error may be?16:40
*** mjturek has quit IRC16:41
mlavalleso a06bbb30-1914-4467-9e75-6fc70d99427f is not in the neutron server log?16:41
slaweq_and also there is no any ERROR in neutron-server log: http://logs.openstack.org/96/596896/2/check/tempest-full-py3/95eba41/controller/logs/screen-q-svc.txt.gz?level=ERROR16:42
slaweq_which is strange IMO because this error 500 came from somewhere, right?16:42
*** mjturek has joined #openstack-meeting16:42
slaweq_it's only one such failed test but it's interesting for me :)16:42
mlavallemaybe our fips our plunging into a black hole16:43
*** ijw has quit IRC16:44
*** ijw has joined #openstack-meeting16:44
slaweq_in tempest log: http://logs.openstack.org/96/596896/2/check/tempest-full-py3/95eba41/controller/logs/tempest_log.txt16:44
slaweq_it's visible in 3 places16:44
slaweq_once when it's created16:44
slaweq_and then when it's removed16:44
slaweq_with erro 50016:45
* mlavalle looking16:45
mlavalleyeahbut it responded 200 for the POST16:46
mlavalleand the fip doesn't work either16:47
mlavallethe ssh fails16:48
slaweq_because it was not visible anywhere in neutron IMO so it couldn't work, right?16:48
slaweq_maybe that is also culprit of other issues with not working FIP16:49
slaweq_let's keep an eye on it and check if on other examples similar things will pop up16:49
slaweq_next topic16:50
slaweq_#topic Fullstack16:50
*** openstack changes topic to "Fullstack (Meeting topic: neutron_ci)"16:50
mlavalleslaweq_: http://logs.openstack.org/96/596896/2/check/tempest-full-py3/95eba41/controller/logs/screen-q-svc.txt.gz#_Sep_02_23_25_07_98988016:50
mlavallethe fip uuid is in the neutron server log16:51
*** zaneb has quit IRC16:51
slaweq_so I was searching too fast, and not whole log was loaded in browser :)16:51
slaweq_sorry for that16:51
*** zaneb has joined #openstack-meeting16:51
mlavalleI'll let you dig deeper16:52
slaweq_but delete was also fine: http://logs.openstack.org/96/596896/2/check/tempest-full-py3/95eba41/controller/logs/screen-q-svc.txt.gz#_Sep_02_23_25_30_96695216:52
slaweq_I will check those logs once again later16:53
mlavalleright, so it seems the problem is more on the NOva side16:53
slaweq_maybe :)16:53
slaweq_let's back to fullstack for now16:53
slaweq_test_securitygroups test is marked as unstable now so it should be at least in better shape then it was recently16:54
*** tssurya has quit IRC16:54
slaweq_I will continue debugging this issue when I will have some time16:54
slaweq_I think that this is most common issue in fullstack tests and without failing this one, it should be good with other things16:55
slaweq_I have one more question about fullstack16:55
slaweq_what You think about switching fullstack-python35 to be voting?16:55
slaweq_it's following exactly failure rate of py27 job: http://grafana.openstack.org/d/Hj5IHcSmz/neutron-failure-rate?panelId=22&fullscreen&orgId=1&from=now-7d&to=now16:55
njohnstonat this point should I change it to be fullstack-py36 before we commit it?16:56
slaweq_or maybe we should switch neutron-fullstack to be py35 and add neutron-fullstack-python27 in parallel?16:56
slaweq_njohnston: ok, so You want to switch it to py36 and check few more weeks how it will be?16:56
mlavalleI like that paln16:57
njohnstonat least a week, yes16:57
slaweq_that is good idea IMO16:57
mlavallecan we swicth it this week?16:57
*** ekcs has quit IRC16:57
mlavallethat way we get the week of the PTG as testing and if everything goes well, we can pull the trigger in two weeks16:58
njohnstonyes, I will get that change up today16:58
slaweq_great, thx njohnston16:58
slaweq_#action njohnston to switch fullstack-python35 to python36 job16:58
slaweq_ok, lets move quickly to last topic16:58
slaweq_#topic Open discussion16:58
*** openstack changes topic to "Open discussion (Meeting topic: neutron_ci)"16:58
slaweq_FYI: QA team asked me to add list of slowest tests from neutron jobs to https://ethercalc.openstack.org/dorupfz6s9qt - they want to move such tests to slow job16:59
slaweq_Such slow job for neutron is proposed in https://review.openstack.org/#/c/583847/16:59
njohnstonsounds smart16:59
slaweq_I will try to check longest tests in our jobs this week16:59
slaweq_second thing I want to annonce is that I will cancel next week's meeting due to PTG17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Tue Sep  4 17:00:06 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-09-04-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-09-04-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-09-04-16.00.log.html17:00
slaweq_ok, we are out of time :)17:00
slaweq_thx for attending17:00
slaweq_and see You around o/17:00
mlavalleslaweq_: maybe send a message to the ML canceling next week's meeting17:00
slaweq_mlavalle: yes, I will17:00
mlavallenot that hordes of people are going to show up17:00
*** r-mibu has quit IRC17:02
*** mlavalle has left #openstack-meeting17:02
*** _alastor_ has quit IRC17:04
*** njohnston has quit IRC17:12
*** ijw has quit IRC17:13
*** Adri2000 has quit IRC17:16
*** tetsuro has joined #openstack-meeting17:18
*** Adri2000 has joined #openstack-meeting17:19
*** Bhujay has quit IRC17:31
*** njohnston has joined #openstack-meeting17:34
*** ekcs has joined #openstack-meeting17:36
*** annabelleB has quit IRC17:38
*** iyamahat has quit IRC17:41
*** e0ne has quit IRC17:44
*** diablo_rojo has joined #openstack-meeting17:47
*** mjturek has quit IRC17:53
*** mjturek has joined #openstack-meeting17:54
*** mjturek has quit IRC17:54
*** iyamahat has joined #openstack-meeting17:54
*** alexchadin has joined #openstack-meeting17:56
*** iyamahat_ has joined #openstack-meeting17:57
*** electrofelix has quit IRC17:58
*** alexchadin has quit IRC18:00
*** iyamahat has quit IRC18:01
*** njohnston has quit IRC18:10
*** jamesmcarthur has quit IRC18:12
*** zbitter has joined #openstack-meeting18:12
*** zaneb has quit IRC18:12
*** zbitter has quit IRC18:13
*** zbitter has joined #openstack-meeting18:13
*** ijw has joined #openstack-meeting18:14
*** zbitter is now known as zaneb18:14
*** tetsuro has quit IRC18:16
*** tetsuro has joined #openstack-meeting18:16
*** AJaeger has joined #openstack-meeting18:18
*** bswartz has joined #openstack-meeting18:20
*** tetsuro has quit IRC18:20
*** alexchadin has joined #openstack-meeting18:23
*** alexchadin has quit IRC18:27
*** jamesmcarthur has joined #openstack-meeting18:32
*** tetsuro has joined #openstack-meeting18:35
*** jamesmcarthur has quit IRC18:36
*** eharney has quit IRC18:36
*** mjturek has joined #openstack-meeting18:49
*** tetsuro has quit IRC18:53
*** Shrews has joined #openstack-meeting18:59
* fungi peers around19:00
*** clarkb has joined #openstack-meeting19:01
clarkbanyone here for the infra meeting? I apparently need to finish rejoining channels after being kicked from them19:01
clarkb#startmeeting infra19:01
openstackMeeting started Tue Sep  4 19:01:31 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#topic Announcements19:02
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:02
clarkbThe PTG is less than a week a way. I know a good chunk of us will be there. I think we can go ahead and cancel next weeks Infra meeting as a result19:02
clarkbwe'll be in the help room instead19:02
fungiwe'll be in the helproom at that time, i guess (or at lunch)19:03
corvusor both19:03
fungitimezone conversion says we can help lunchishly at that time19:03
corvusi mean, i'm eating lunch now19:04
clarkb#topic Actions from last meeting19:04
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:04
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-08-28-19.01.txt minutes from last meeting19:04
clarkbLast week was actually a fairly "quiet" meeting overall. I think many of us were (and still are) heads down on the bridge.openstack.org migration19:05
clarkbMay as well talk about that then.19:05
clarkb#topic Priority Efforts19:05
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:05
clarkb#topic Update Config Management19:06
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:06
clarkbThe review topic of update-cfg-mgmt and puppet-4 continue to have changes that need review19:06
clarkbcorvus has helped me get a set of changes up to manage clouds.yaml on nodepool nodes and on bridge.openstack.org. They are tested and I think passing tests now so we can probably take the plunge when ready19:07
clarkbthis is a necessary pre step to running the cloud launcher playbook against our clouds again19:07
corvusi'll +3 after lunch^Wmeeting19:07
Shrewsclarkb: i think i saw one fail (timeout)19:07
* diablo_rojo sneaks in late19:07
clarkbShrews: darn ok, will have to take a look then19:07
clarkbOnce those changes are in and happy I'll unwip my change to deploy the cloud launcher playbook on bridge.openstack.org19:08
clarkbat that point we should be in a good spot to add new clouds or cloud regions again (I had to manually run the launcher to set up the new vexxhost region)19:08
clarkbpabelanger: has also proposed a change to run our ansible with mitogen19:08
corvusit looks like we should be able to get the per-project ssh keys feature into zuul soon -- maybe we can land that this week and restart with it.  then it'll be ready for us to experiment with zuul-driven CD at ptg.19:09
corvuspabelanger: are the timings from the test output useful with mitogen, or do you think we need to run it in production to see if it's effective?19:09
clarkb#link https://review.openstack.org/597297/ Adds mitogen to our ansible for hopeful performance improvements19:09
clarkbcorvus: my hunch is we may need to see it in production since I think one of the ways it is helpful is mitigating network latencies19:10
clarkbcorvus: the gains in a small localized test env may be minimal compared to our multicloud control plane19:11
pabelangercorvus: I think we need more hosts to see how it scales.  I can try and look at tests in system-config to see if I can see any differences however19:11
*** jamesmcarthur has joined #openstack-meeting19:11
fungimordred will probably be interested in the pbr entry on mitogen's importer wall of shame too19:11
corvusclarkb: we do have network latencies in the tests...19:11
clarkbcorvus: we do but it si all in the same cloud region isn't it?19:11
corvusclarkb: yes -- much like our control plane19:11
*** mjturek has quit IRC19:11
*** annabelleB has joined #openstack-meeting19:12
clarkbin any case I'm willing to try it in production. I do note that I don't think we can use python3.5 on xenial with mitogen which changes my thoughts on python3 migration for ansible somewhat (assuming we stick with mitogen)19:13
corvusi'm not eager to use mitogen.  i think we have enough work cut out for us as it is, and i've heard mixed reports on its effectiveness.  unless it's like two orders of magnitude better, i'd rather we just focus on the stuff in the spec3.19:14
corvusi'm not going to -2 it or anything, but i'd prefer not to +2 it either, and instead defer it until later.  unless there's some reason we need to incorporate it now.19:14
*** jamesmcarthur has quit IRC19:15
clarkbthats fair, the current cycle is about an hour long which isn't terrible19:15
*** jamesmcarthur_ has joined #openstack-meeting19:15
corvusclarkb: we should (have) increase(ed) the size of bridge and run with more forks19:15
corvusif speed is what we're after, let's start with the basics19:15
corvuswe couldn't even run without ooming before, i don't know why (mitogen or no) we wouldn't run into the same problem this time.19:16
pabelangeryah, this was mostly to see if we could get better performance with current bridge.o.o, but also okay to skip to later19:16
corvusas a staw-man: i'm happy to click the button in the web ui to tell rax to embiggen the existing node19:17
clarkbcorvus: we don't appear to have memory pressure issues on the new bridge (at least with the current number of forks) http://cacti.openstack.org/cacti/graph.php?action=view&local_graph_id=65004&rra_id=all is the cacti info19:17
corvusclarkb: cool.  then we should increase the number of forks until we do :)19:17
clarkbbut that instance is quite small, not opposed to increasing the number of forks and then the ram if we hit the memory limits before the runtime improvements stop19:17
fungii don't think node embiggening is a thing in rax any longer19:18
fungiat least not for pvhvm flavors19:18
corvusfungi: bummer19:19
fungii'm checking now19:19
clarkbnova supports resizing at least19:19
corvuswe *should* be able to launch a new bridge, but i don't know what we don't know about that.19:20
clarkbcorvus: things like clouds.yaml definitely were (and technically still are) managed by hand19:20
*** sridharg has quit IRC19:21
clarkbianw: is the change to make ansible more non root friendly on bridge.o.o still outstanding?19:21
clarkbianw: pabelanger is it worth talking about that here if so? might help reach an agreement?19:21
fungi#link https://support.rackspace.com/how-to/upgrading-resources-for-general-purpose-or-io-optimized-cloud-servers/19:21
fungitl;dr is you can add more disk and you can create a new bigger server19:21
corvusfungi: :(19:22
ianwclarkb: yep19:22
fungioh, there's a thing at the bottom about "auto scale"19:22
clarkbah looks like pabelanger +1'd it to not be a -119:23
fungiwhich seems to have something to do with load balancing19:23
clarkbI guess I just need to rereview it today then19:23
corvusfungi: i guess we could do all that.  but it sounds like for now we can probably increase forks and kick the reprovisioning can down the road.19:23
clarkb#link https://review.openstack.org/#/c/596630/ Change to make ansible on bridge.openstack.org useable as not root user19:23
pabelangerclarkb: yah, other eyes would be good there. Not going to block19:23
corvusansible runs as root; zuul is going to run ansible as root.... is doing this worthwhile?19:24
clarkbcorvus: I'm a fan of it as we often run ansible commands from puppetmaster (and now bridge) as not root19:25
clarkbwe can su every time we want to run it I guess19:25
fungithe idea was for if we're still going to have humans running launch-node.py19:25
corvusclarkb: huh, i always did "sudo ansible" on puppetmaster19:25
fungias the vast majority of the things the launch-node.py script covers doesn't need elevated privileges on the management bastion19:26
clarkbfungi: ya that was where I ran into it first on bridge.openstack.org19:26
clarkbI'm fine either way, forcing root will require some docs updates. Continuing to allow the admin group to run ansible commands requires ianw's change19:27
*** e0ne has joined #openstack-meeting19:27
fungii mean, we were able to run launch-node.py previously by just being in the puppet group, and then later when we switched to using ansible for the cron we made the inventory admin-group-writeable so we still didn't need to sudo launch-node.py19:27
fungiup until a very recent change to get rid of the admin group19:28
corvuswhen i run ansible as corvus on puppetmaster it just hangs.  dunno what it's doing.19:28
clarkbcorvus: it may be generating an inventory for you if you've not done it before19:29
fungiso this was mainly a request to restore that property in a way that doesn't offend anyone's sensibilities (apparently the admin group existing rubs some folks the wrong way)19:29
clarkbI can't remember if it uses the global cache if run as a regularl user or not19:29
ianwhanging usually to me indicates the inventory, and probably that is root only at this point and it's going off doing ... something?19:29
corvusclarkb: that sounds like a fabulous reason to run it as root :)19:29
pabelangerI personally find shared history as root user a little confusing, but not a deal breaker19:30
*** mjturek has joined #openstack-meeting19:30
pabelangerthat was the main bonus I liked about user with sudo19:30
clarkbpabelanger: we can still user + sudo in the current setup fwiw19:31
clarkbpabelanger: the proposed change allows user without sudo.19:31
fungii just personally get especially uneasy when i'm running things as root or via sudo somewhere with as many sensitive contents as the management bastion19:31
corvusansible cron runs as root, zuul will run ansible as root; if we make all the bits necessary to run ansible and launch-node read/writable to all of us -- is there really much of a point to that?19:31
pabelangerRight, that too. would need to check how I did launch-node.py in the past19:31
corvusfungi: i hear that -- everything about the bastion makes me uneasy :)19:32
clarkbya I'm mostly wtih fungi. Many years of only using sudo/root when necesary19:32
corvusbut is the proposed change actually safer?19:32
fungiif the idea is that zuul and/or the ansible cron will take over launching new servers for us, then i'll no longer be uneasy with the fact that i might typo a root-privileged command that needed almost no root access19:32
clarkbcorvus: the ansible commands themselves shouldn't be, but if it helps keep us from just sudoing everything that doesn't immediately work then maybe?19:33
clarkbits mostly a discipline thing and not one we've had problems with ime19:33
corvusi guess what i'm saying is -- the change is really about making all the currently-root-needing things not need root.  and there is nothing else on the server other than the root-needing things.19:33
*** jamesmcarthur_ has quit IRC19:33
*** e0ne has quit IRC19:33
clarkbcorvus: well the ansible stuff only needs root beacuse that is how we've set it up (the invocation side at least)19:34
clarkbbut that is a bigger change to move invocation side off of root to only being root on the remote19:35
fungii'm okay switching to using sudo if that's the plan going forward. we also had a rocky past with things like envvars not getting passed through to those scripts but i guess they're all being put in command-line options now so that shouldn't be as much of an issue19:35
clarkb(and effecitlvey gives you root on the invocation side if you choose so may be a noop)19:35
corvusclarkb: (it still needs to become_true on bridge itself to self-manage, but yes, agreed)19:35
pabelangerwhat is we decided to revert the admin removal change? Then things go back to just working.19:36
clarkbmaybe we can follow up after the meeting with ianw a bit more? we have 24 minutes of meeting allotment left and it would be good to move on to PTG things if we can19:36
fungiseems like the admin group was objectionable because it used to be a standard group on ubuntu and then they deprecated it in more recent releases19:36
ianwhonestly if we're going to do it, i'd rather we have an "ansible" group to avoid confusion over this in the future.  one group, one thing seems logical19:37
fungiand for whatever reason having a group named "admin" is a mistake19:37
fungiyeah, we used the "puppet" group for this in the past19:37
pabelangerright, that was my main suggestion just to rename root to sudo, we'd get the new admin group for bionic.19:37
pabelangeror even us adm19:38
corvusin this particular instance, i'm unconvinced that an admin-like-group system is better.  if someone feels strongly about it and wants to drive that, i'm not opposed.  but it sounds like a time sink with little upside.  especially if, at the end of the day, we're going to end up doing "sudo ansible ..." anyway.19:38
fungii don't want to drag this out. if most of us have no objection to doing it all as root/via sudo i'll adapt19:39
clarkbcorvus: I think the only thing we would want to do is update our docs (for launch node in particular) to reflect that change in process. But otherwise I agree I think we can move forward with forcing use of root19:39
corvusmaybe i just need more convincing :)19:39
clarkbbut ya lets move on so that we can go over ptg things really quickly19:39
clarkband can pick this up again after in #openstack-infra if we want19:39
clarkb#topic General Topics19:39
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:39
clarkbThe PTG is next week19:39
clarkb#link https://etherpad.openstack.org/p/infra-ptg-denver-2018 PTG planning document19:40
clarkbThe PTG runs Monday to Friday. On Monday and Tuesday the infra team is aprt of the helproom at the PTG. I will be there helping people with infra related items as they come up19:40
clarkbif you are attending the PTG and have time Monday and Tuesday please join us19:41
clarkbThen Wednesday and Thursday we will have dedicated infra time in our own room19:41
clarkbFriday is a free day, but the openstack TC is having open meetings in the afternoon that people may be interested in19:41
clarkbI'm open to trying to do some sort of team activity on that day if others are interested (maybe we do breakfast off site so people can get back to the TC meetings)19:42
clarkbthat is the high level overview, should be very similar in format to Dublin with exception of the snow storm19:42
clarkbOh, team bier garten outing. Looking at a schedule of official ptg activities Monday night would be easiest. does that work?19:43
fungiso in other words, _nothing_ like dublin ;)19:43
* fungi remembers the format for dublin was "blizzard"19:44
clarkb#link https://ethercalc.openstack.org/fgry72wu42qw availability for biergarten outing. Monday would be best based on PTG event scheduling. Please let me know if that doesn't work19:44
clarkbI'll go ahead and pencil in Monday now and send details to the infra list later this week if I hear no objections19:44
clarkbThat leaves us with working out an agenda. If you have things you want to work on at the PTG that are not already on the etherpad please add them19:45
clarkbI'm goign to try and categorize and organize them a bit so that when we show up wednesday we can peel them off of the list19:45
corvusi'm arriving on monday, so will join the help-room asap.  bier monday sounds great.  :)19:45
corvusso does tuesday.  and wednesday.  and thursday.19:46
pabelangerI won't be at the PTG this time around, but hope to participate remotely.19:46
clarkbpabelanger: we'll miss you19:46
clarkbpabelanger: re remote participation did you have a specific format in mind (eg a phone call with speakerphone on? or asterisk call from corvus' laptop? or?)19:46
clarkbmight be good to sort that out before we all get on places19:47
corvusyeah, i'm hoping that our work on the config mgmt stuff should mostly be writing a bunch of changes, so remote participation may be effective.19:47
clarkbcorvus: ++19:47
pabelangeryah, if people remember to log into asterisk, that would behelpful, but mostly going to be watching irc19:47
clarkbpabelanger: good to know, I'll try to make a point of treating irc as an extension of the room19:48
pabelangeryah, I'll keep an eye out for etherpad too19:49
clarkbOne thing worth  noting is that I think this is a good opportunity for us to get feedback on the winterscale effort from openstack and some of the newr projects. I hear that airship and starlingx will be there19:49
clarkbinfo on what sort of services various projects feel should be under the generic branding vs their own in particular. Will have to resurrect my etherpad strawman breakdown19:50
clarkbThe helproom may also have a less openstack vibe to it. Unsure at this point but keep that in mind too19:50
clarkbAny other PTG questions, concerns, thoughts?19:51
*** e0ne has joined #openstack-meeting19:52
fungiwe've had some people recently pop up on the ml and in irc wanting to contribute to the team. any idea if we have new infra-curious folks attending?19:52
fungithere always seem to be at least one or two19:53
clarkbfungi: I've not heard of any beyond the non openstack projects at the foundation being there and possibly going to use some of that time to work out infra related things19:53
fungiwould be nice if those projects wanting to use our services also wanted to help maintain them19:54
fungiso maybe!19:54
*** annabelleB has quit IRC19:55
clarkb#topic Open Discussion19:55
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:55
clarkbAlright anything else?19:55
ianwi just got notification on a ticket we have some more linaro resources in their london cloud19:55
ianwwill look into that today.  moving the builder there would probably work out well19:55
ianw#link https://review.openstack.org/#/c/599270/ Switch unmodified readthedocs jobs to warning job19:56
clarkbianw: neat, keep in mind that until clouds.yaml and cloud launcher stuff is automated on bridge.o.o some of the new region bring up is still manual (I manually ran cloud launcher against vexxhost sjc1 for example)19:56
ianwthis adds a warning job for outstanding rtd publishers that aren't actually working.  actually a lot of them are infra projects19:56
ianwif everyone could check their readthedocs login, and anything they own that is an infra project needs to have openstackci user added as an admin19:56
fungireminder that the stein cycle signing key is up for switching into production too19:57
ianwi'm happy to help update the jobs, but can't do that until we have permission19:57
clarkbhuh I don't think I've ever configured rtd for an infra project19:57
ianwclarkb: ++ thanks for reminding me on that19:57
fungi#link https://review.openstack.org/599092 Replace the old Rocky cycle signing key with Stein19:57
* AJaeger would appreciate some regular review on config repos. Especially clarkb and ianw help a lot - but more reactive. Could some of you regularly review, please?19:58
fungithere's a process documentation update and corresponding releases site change under the same topic:artifact-signing19:58
clarkbAJaeger: ++ that is a good reminder. I try when I have downtime to look at the open list in project-config but with everything else going on sometimes that doesn't happen19:58
AJaegerclarkb: if you find over beer some ideas next week on what to do, I would appreciate it (I won't be at PTG but booked tickets for Berlin ;)19:59
clarkbAJaeger: I hear they have beer in berlin too :)20:00
clarkbAnd we are at time.20:00
clarkbTHanks everyone. See you back here in two weeks20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:00
openstackMeeting ended Tue Sep  4 20:00:24 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-09-04-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-09-04-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-09-04-19.01.log.html20:00
fungiclarkb: i heard berlin mostly just has bier instead20:01
*** AJaeger has left #openstack-meeting20:02
*** alexchadin has joined #openstack-meeting20:16
*** ijw has quit IRC20:18
*** jamesmcarthur has joined #openstack-meeting20:21
*** annabelleB has joined #openstack-meeting20:33
*** ijw has joined #openstack-meeting20:41
*** ijw has quit IRC20:48
*** annabelleB has quit IRC20:50
*** ijw has joined #openstack-meeting20:50
*** alexchadin has quit IRC20:51
*** raildo has quit IRC20:51
*** eharney has joined #openstack-meeting20:51
*** annabelleB has joined #openstack-meeting20:52
*** bobh_ has quit IRC21:00
*** iyamahat__ has joined #openstack-meeting21:01
*** bobh has joined #openstack-meeting21:02
*** imacdonn has quit IRC21:02
*** imacdonn has joined #openstack-meeting21:02
*** martial has joined #openstack-meeting21:03
martialFYI skipping the Scientific SIG today21:04
*** iyamahat_ has quit IRC21:04
*** erlon has quit IRC21:05
*** bobh has quit IRC21:07
*** ekcs has quit IRC21:11
*** awaugama has quit IRC21:11
*** e0ne has quit IRC21:13
*** ekcs has joined #openstack-meeting21:18
*** iyamahat__ has quit IRC21:31
*** iyamahat has joined #openstack-meeting21:32
*** ekcs has quit IRC21:34
*** bobh has joined #openstack-meeting21:36
*** ekcs has joined #openstack-meeting21:38
*** ijw has quit IRC21:38
*** Shrews has left #openstack-meeting21:39
*** ijw has joined #openstack-meeting21:40
*** munimeha1 has quit IRC21:47
*** ykatabam has joined #openstack-meeting21:47
*** ijw has quit IRC22:02
*** bobh has quit IRC22:10
*** annabelleB has quit IRC22:15
*** priteau has quit IRC22:21
*** ianychoi has quit IRC22:22
*** aagate has quit IRC22:27
*** erlon has joined #openstack-meeting22:42
*** spartakos has joined #openstack-meeting22:48
*** jamesmcarthur has quit IRC22:50
*** jamesmcarthur has joined #openstack-meeting22:51
*** jamesmcarthur has quit IRC22:52
*** rcernin has joined #openstack-meeting22:55
*** ianychoi has joined #openstack-meeting23:16
*** tpsilva has quit IRC23:18
*** priteau has joined #openstack-meeting23:22
*** aagate has joined #openstack-meeting23:31
*** martial has quit IRC23:32
*** jamesmcarthur has joined #openstack-meeting23:44
*** bobh has joined #openstack-meeting23:44
*** jamesmcarthur has quit IRC23:48
*** bobh has quit IRC23:49
*** mjturek has quit IRC23:58

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