Tuesday, 2017-09-05

*** Tom_ has quit IRC00:01
*** yangyapeng has joined #openstack-meeting00:04
*** ykatabam1 has joined #openstack-meeting00:08
*** yangyapeng has quit IRC00:09
*** ykatabam has quit IRC00:09
*** claudiub|2 has quit IRC00:17
*** baojg has quit IRC00:20
*** thorst_afk has joined #openstack-meeting00:24
*** adisky__ has joined #openstack-meeting00:25
*** edmondsw has quit IRC00:26
*** markvoelker has joined #openstack-meeting00:26
*** aeng has quit IRC00:33
*** Manuel_112 has joined #openstack-meeting00:36
*** Manuel_112 has quit IRC00:41
*** bobh has joined #openstack-meeting00:44
*** Manuel_112 has joined #openstack-meeting00:44
*** kiennt has joined #openstack-meeting00:47
*** Manuel_112 has quit IRC00:48
*** zhurong has joined #openstack-meeting00:49
*** bobh has quit IRC00:53
*** wanghao has quit IRC00:54
*** wanghao has joined #openstack-meeting00:55
*** thorst_afk has quit IRC00:55
*** bobh has joined #openstack-meeting00:57
*** liyi has joined #openstack-meeting00:58
*** markvoelker has quit IRC00:59
liyi/JOIN #openstack-meeting01:00
*** caowei has joined #openstack-meeting01:04
*** aeng has joined #openstack-meeting01:06
*** bobh has quit IRC01:08
*** yangyapeng has joined #openstack-meeting01:11
*** ijw has quit IRC01:11
*** ijw has joined #openstack-meeting01:16
*** epico has joined #openstack-meeting01:17
*** david-lyle has joined #openstack-meeting01:20
*** bobh has joined #openstack-meeting01:23
*** bkopilov has quit IRC01:28
*** baoli has joined #openstack-meeting01:30
*** gcb has joined #openstack-meeting01:34
*** thorst_afk has joined #openstack-meeting01:39
*** thorst_afk has quit IRC01:39
*** shu-mutou has joined #openstack-meeting01:46
*** Manuel_112 has joined #openstack-meeting01:47
*** dmacpher has joined #openstack-meeting01:48
*** fzdarsky_ has joined #openstack-meeting01:51
*** Manuel_112 has quit IRC01:51
*** fzdarsky|afk has quit IRC01:55
*** jamesmcarthur has joined #openstack-meeting01:55
*** markvoelker has joined #openstack-meeting01:56
*** ricolin has joined #openstack-meeting02:01
*** kevzha01 has joined #openstack-meeting02:03
*** CAMILA1 has joined #openstack-meeting02:03
*** hongbin has joined #openstack-meeting02:03
CAMILA1HOLA02:03
*** julim has joined #openstack-meeting02:03
CAMILA1HOLAAAAAAAAAAAAAAAAAAAAA02:04
CAMILA1:-[02:04
*** CAMILA1 has left #openstack-meeting02:04
*** liyi has quit IRC02:05
*** gouthamr has quit IRC02:08
*** kevzha01 is now known as kevinz02:12
*** thorst_afk has joined #openstack-meeting02:17
*** thorst_afk has quit IRC02:17
*** hongbin has quit IRC02:18
*** baoli has quit IRC02:24
*** markvoelker has quit IRC02:30
*** Tom has joined #openstack-meeting02:31
*** bobh has quit IRC02:33
Tomhelp02:33
*** caowei has quit IRC02:36
*** bobh has joined #openstack-meeting02:38
*** Manuel_112 has joined #openstack-meeting02:41
*** caowei has joined #openstack-meeting02:41
*** hongbin has joined #openstack-meeting02:45
*** baoli has joined #openstack-meeting02:45
*** Manuel_112 has quit IRC02:45
*** Tom has quit IRC02:46
*** bkopilov has joined #openstack-meeting02:46
*** Tom has joined #openstack-meeting02:48
*** Manuel_112 has joined #openstack-meeting02:51
*** trinaths has joined #openstack-meeting02:53
*** FengShengqin has joined #openstack-meeting02:54
*** Manuel_112 has quit IRC02:56
*** hongbin has quit IRC02:58
*** hongbin has joined #openstack-meeting02:59
*** Tom has quit IRC02:59
*** Tom has joined #openstack-meeting02:59
hongbin#startmeeting zun03:00
openstackMeeting started Tue Sep  5 03:00:07 2017 UTC and is due to finish in 60 minutes.  The chair is hongbin. Information about MeetBot at http://wiki.debian.org/MeetBot.03:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.03:00
*** openstack changes topic to " (Meeting topic: zun)"03:00
openstackThe meeting name has been set to 'zun'03:00
hongbin#link https://wiki.openstack.org/wiki/Zun#Agenda_for_2017-09-05_0300_UTC Today's agenda03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
kevinzo/03:00
FengShengqinfengshengqin03:00
*** Shunli has joined #openstack-meeting03:00
spno/03:01
Shunli0/03:01
hongbinthanks for joining the meeting kevinz FengShengqin spn Shunli03:01
*** lakerzhou has joined #openstack-meeting03:01
hongbinlet's get started03:01
hongbin#topic Announcements03:01
*** openstack changes topic to "Announcements (Meeting topic: zun)"03:01
hongbin1. New BPs for Queens cycle03:02
hongbin#link https://blueprints.launchpad.net/zun/+spec/zun-policy-in-code Register and Document Policy in Code03:02
hongbin#link https://blueprints.launchpad.net/zun/+spec/zun-split-tempest-plugins Split Tempest Plugins into Seperate Repos/Projects03:02
hongbinthese two bps are openstack community goal03:02
hongbinwelcome to pick it if you interest03:02
kiennto/ sorry, i'm late.03:03
hongbinany other announcement from our team members?03:03
hongbinhi kiennt , np, thanks for joining03:03
hongbinok, move forward03:03
hongbin#topic Cinder integration (hongbin)03:03
*** openstack changes topic to "Cinder integration (hongbin) (Meeting topic: zun)"03:03
*** Tom has quit IRC03:04
*** trinaths has left #openstack-meeting03:04
hongbinfor this one, i was working on several patches last week03:04
hongbin#link https://review.openstack.org/#/q/status:open+project:openstack/zun+branch:master+topic:bp/direct-cinder-integration03:04
hongbinthere are a few patches that are ready for review03:05
hongbinthere are a few WIP patches, which is mainly for missing unit tests03:05
hongbini will continue to work on those03:05
hongbinwith all the patches above, the cinder integration feature is ready03:06
hongbinthat is all from me03:06
hongbinany question for this topic?03:06
FengShengqinwe still need prepare cinder volume for container?03:06
kevinzThanks hongbin! This is great feature to zun03:06
hongbinFengShengqin: yes, users need to create a cinder volume in before03:06
*** baoli has quit IRC03:07
hongbinFengShengqin: which is a "cinder create ...." command03:07
hongbinkevinz: welcome03:07
*** lakerzhou1 has joined #openstack-meeting03:07
hongbinany other question?03:08
hongbin#topic Introduce container composition (kevinz)03:08
*** openstack changes topic to "Introduce container composition (kevinz) (Meeting topic: zun)"03:08
hongbin#link https://blueprints.launchpad.net/zun/+spec/introduce-compose03:08
hongbinkevinz: ^^03:08
hongbinkevinz: there?03:09
kevinzHi all, actually I didn't get much time last week due to Arm offsite meeting. I will work on a doc about capsule this week03:09
kevinzhongbin: yeah03:09
hongbinkevinz: :)03:09
hongbinkevinz: get that03:09
kevinzhongbin: And rebase some code to latest commit. Then I think the basic function of capsule will finish03:10
hongbinkevinz: awesome03:10
kevinzhttps://review.openstack.org/480455  and this patch need review03:10
hongbinkevinz: i am looking forward to it, the k8s connector bp will leverage the capsule feature03:10
*** lakerzhou has quit IRC03:11
kevinzhongbin: That's great03:11
hongbincore reviewers, pls help to review this patch03:11
hongbin#link https://review.openstack.org/48045503:11
hongbinthanks kevinz03:11
*** noslzzp has quit IRC03:11
kevinzThat's all from me. Next week I will go to Denvor for PTG03:12
hongbinkevinz: have a good trip03:12
spnkevinz, Have a great trip :)03:12
kevinzhongbin: spn: Thanks!03:12
*** Manuel_112 has joined #openstack-meeting03:12
hongbin#topic Add support for clear container (mkrai)03:12
*** openstack changes topic to "Add support for clear container (mkrai) (Meeting topic: zun)"03:12
hongbinmkrai: hi madhuri, you there?03:12
spnmkrai is not well03:13
spnand she is out03:13
hongbinsorry to hear03:13
spnBut last week she was available for a brief time03:13
spnand we discussed some of the specific of the implementation03:13
spnhttps://etherpad.openstack.org/p/zun-clearcontainers03:13
spnI captured our discussion over there03:13
hongbin#link https://etherpad.openstack.org/p/zun-clearcontainers03:13
*** noslzzp has joined #openstack-meeting03:14
* hongbin is reading the etherpad03:14
lakerzhou1Kevinz, I am going to PTG too. We should meet there.03:15
kevinzlakerzhou1: Wow ,that's great!03:15
kevinzlakerzhou1: hope to meet you there!03:15
*** noslzzp has quit IRC03:16
hongbinspn: the outline in the etherpad looks good to me03:16
hongbinspn: thanks for working on that03:17
spnhongbin, thank you. I trying to add sort of diagram just to clear my mind on how it all works03:17
*** Manuel_112 has quit IRC03:17
*** bobh has quit IRC03:17
spnwe will sit down on implementation specifics this week and add notes over there.03:17
hongbinthanks spn03:18
Shunlispn: so the basic direction is that cc and runc will on different host, right?03:18
*** thorst_afk has joined #openstack-meeting03:18
spnShunli, yes03:18
Shunlithx, ack03:18
spnwhat was your discussion03:18
spnearlier about running zun containers and kvm vms on same machine?03:18
spnzun containers with regular runc engine03:18
hongbinok, i think we should move forward03:19
hongbin#topic NFV use cases (lakerzhou)03:20
*** openstack changes topic to "NFV use cases (lakerzhou) (Meeting topic: zun)"03:20
Shunlino, just to confirm that i understand the etherpad correctly.03:20
hongbin#link https://etherpad.openstack.org/p/zun-nfv-use-cases03:20
hongbinfor this topic, there are a few progress last week03:20
hongbinShunli has uploaded a few patches for the pci support in db/objects03:20
Shunlihttps://review.openstack.org/#/c/500418/03:21
hongbinyes, this is the big patch03:21
Shunliworking on the comments and the ut this week.03:21
hongbinShunli: ack, thanks for working on that03:22
*** ijw has quit IRC03:22
*** jamesmcarthur has quit IRC03:22
hongbinthat is for the pci scheduling support03:22
hongbinin addition, i am working on a few patches in kuryr/kuyr-libnetwork for the sriov support03:23
*** jamesmcarthur has joined #openstack-meeting03:23
*** thorst_afk has quit IRC03:23
hongbin#link https://review.openstack.org/#/c/500420/03:23
hongbin#link https://review.openstack.org/#/c/500436/03:23
Shunlilater maybe will start the pci tracker as the base code need by pci tracker is almost ready.03:23
hongbinyes, what is missing is the pci tracker and scheduler filter03:24
hongbinpci scheduler filter in particular03:24
hongbinafter that, we will look for an integration between zun and kuryr03:25
*** coolsvap has joined #openstack-meeting03:25
Shunlisure03:25
hongbini believe the integration is not hard, zun just needs to populate the neutron port with information about which VF to bind03:25
Shunliit's seems a long way to go. pci feature is too complicate and too much code,:-)03:26
hongbinyes :)03:26
hongbinShunli: i saw you ported a lot of code from nova to zun already03:26
hongbinwhich is great03:27
*** jamesmcarthur has quit IRC03:27
hongbinShunli: thanks for your hard work on this03:27
Shunlinp my pleasure.03:27
hongbinall, any remark on this topic?03:27
lakerzhou1for demo, pci scheduler can be optional if it is too complicated03:28
Shunlilakerzhou1: not just for scheduler, zun need some basic support code for zun need to port from nova.03:29
hongbinyes, it looks a lot of codes are for tracking the pci resources in all nodes03:30
Shunlisuch as the db to store pci device, compute node to collect pci device, etc..03:30
lakerzhou1shunli, yes, understood.03:30
hongbinlakerzhou1: eventually, zun need to pick a VF, and populate the binding:profile in the neutron port03:31
hongbinlakerzhou1: then, kuryr will pick up the port and read information from binding:profile03:31
hongbinlakerzhou1: then, kuryr will know which VF Zun has picked, and bind the interface of the VF03:32
hongbinlakerzhou1: that is how it should work in theory :)03:32
lakerzhou1hongbin, yes, that is correct03:33
*** Manuel_112 has joined #openstack-meeting03:33
hongbinok03:33
*** kiennt_ has joined #openstack-meeting03:33
hongbinall, any other remark on this topic?03:33
hongbin#topic Mutli-host problems (kiennt)03:34
lakerzhou1I have located three physical servers, but it is not easy to get VPN access03:34
*** openstack changes topic to "Mutli-host problems (kiennt) (Meeting topic: zun)"03:34
hongbinlakerzhou1: we can sync with that offline03:34
hongbinkiennt: there?03:35
lakerzhou1hongbin, sure, I will sync up with you tomorrow03:35
kiennt_hi03:35
hongbinlakerzhou1: ack03:35
hongbinkiennt: hey, do you have anything to bring up about this topic?03:36
*** kiennt has quit IRC03:36
kiennt_hongbin: About the gate, the fix with docker cluster store ip fix the prev problem03:36
hongbinkiennt_: ack03:37
kiennt_but, as you know, multi test still failed. I will work on this to figure out what was wrong.03:37
*** FengShengqin has quit IRC03:37
*** Manuel_112 has quit IRC03:38
kiennt_that's all from me, will work on it this week.03:38
hongbinkiennt_: ack03:38
*** kiennt_ is now known as kiennt03:38
*** FengShengqin has joined #openstack-meeting03:38
hongbinkiennt_: thanks for working on that03:38
hongbin#topic Open Discussion03:39
kiennthongbin: my pleasure :)03:39
*** openstack changes topic to "Open Discussion (Meeting topic: zun)"03:39
hongbinall, any topic to bring up for discussion?03:39
kienntnone from me03:39
spnnone from me03:39
hongbinok, all, thanks for joining the meeting, see you next week03:40
hongbin#endmeeting03:40
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"03:40
openstackMeeting ended Tue Sep  5 03:40:47 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:40
*** FengShengqin has left #openstack-meeting03:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-09-05-03.00.html03:40
spnhongbin, bye03:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-09-05-03.00.txt03:40
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-09-05-03.00.log.html03:40
*** kiennt_ has joined #openstack-meeting03:44
*** kiennt has quit IRC03:47
*** links has joined #openstack-meeting03:51
*** sridharg has joined #openstack-meeting03:53
*** tpatil has joined #openstack-meeting03:55
*** lakerzhou1 has quit IRC03:57
*** Manuel_112 has joined #openstack-meeting03:58
*** samP has joined #openstack-meeting03:59
samPHi all for Masakari04:00
tpatilHi04:00
samP#startmeeting masakari04:00
openstackMeeting started Tue Sep  5 04:00:18 2017 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
samPLet's start04:00
samPCan we meet officially on PTG?04:01
Dinesh_BhorHi all04:01
samPI mean, till now, we did meet every summit, and last PTG to discuss about masakari04:01
tpatilsamP: Sure, let's mention date and time in etherpad04:02
*** Manuel_112 has quit IRC04:02
samPtpatil: I will do that, and send a mail to openstack-dev, if some one wants to join04:02
samPHow many of us going to PTG?04:03
tpatilsamP: Ok, Thanks04:03
samPI am going from 9/12 - 9/1404:03
*** ijw has joined #openstack-meeting04:03
*** slaweq has joined #openstack-meeting04:03
tpatilAbhishek and I will be there for the entire week04:03
samPI will be there 9/11 afternoon and will leave 9/15 morning04:03
samPtpatil: great04:04
samPWe can have VoIP or IRC for others who are not at PTG.04:04
samPI will put up those in etherpad04:04
samPOK, next04:05
samP#topic Critical Bugs04:05
*** openstack changes topic to "Critical Bugs (Meeting topic: masakari)"04:05
samPAny bugs need to discuss?04:05
*** hongbin has quit IRC04:05
samP#link https://bugs.launchpad.net/cinder/+bug/171441604:06
openstackLaunchpad bug 1714416 in OpenStack Compute (nova) "Incorrect response returned for invalid Accept header" [Undecided,New]04:06
samP^^ Nova, and Cinder set status to won't fix for this04:06
tpatilyes04:07
*** ijw has quit IRC04:07
tpatilsamP: What's your opinion?04:08
samPI think same goes fro masakari, anyone may re-state it any time.04:08
tpatilsamP: I agree04:08
samPtpatil: thanks04:08
*** slaweq has quit IRC04:08
samPI set it to won't fix04:09
samPLet's move to discussion points04:09
samP#topic Discussion Points04:09
*** openstack changes topic to "Discussion Points (Meeting topic: masakari)"04:09
samP(1) Application for become OpenStack official project04:10
samPI submitted the application,04:10
samP#link https://review.openstack.org/#/c/500118/04:10
samPplease review ^^, and add your comments or questions to review or ML discussion04:11
samP#link http://lists.openstack.org/pipermail/openstack-dev/2017-September/121729.html04:11
tpatilsamP: Ok04:11
samPML discussion ^^04:11
samP(2) Install guide document04:12
samPNeed to review those, however I don't think I can do it before PTG04:12
samPI will do it after PTG, sorry for the delay04:13
samP(3) recovery method customization04:13
*** gcb has quit IRC04:13
samPAny update from Mistral? PTG etherpad set already?04:13
tpatilsamP: Mistral etherpad will be open for changes in this week04:14
samPtpatil: OK, got it.04:14
samP(4) Find hosts without specifying segments04:14
tpatilsamP: we will send an email on the openstack-dev mistral mailing list04:15
samPI think rikimaru is not here to discuss this, and he is working on this AFAIK04:15
samPtpatil: that will be great04:15
samP(5) Queens Work Items04:16
*** kiennt_ is now known as kiennt_AWAY04:16
samPThank you all for classification of the tasks for pike04:16
samPI move "skip" and "incomplete" items to Queens etherpad04:17
samPLet's discuss about those in PTG04:17
samP#link https://etherpad.openstack.org/p/masakari-queens-workitems04:17
samP^^ Etherpad for Queens items04:18
samPI think that's all in Agenda for today's meeting04:18
samP#topic AOB04:18
*** openstack changes topic to "AOB (Meeting topic: masakari)"04:18
*** Manuel_112 has joined #openstack-meeting04:19
*** thorst_afk has joined #openstack-meeting04:19
samPI will send email with etherpad for PTG discussion and PTG tasks for masakari04:19
tpatilsamP: Ok04:20
samPWe have some related discussion with openstac-ha team in PTG04:20
samPI will share those links too04:20
tpatilsamP: Thank you04:20
samPMasakari team might need to attend TC session for explain about masakari and it's community activities04:21
samPIn that case I will let you know by ML04:21
*** psachin has joined #openstack-meeting04:21
tpatilsamP: I will join this session along with you04:21
samPtpatil: Thanks04:21
*** b1airo has joined #openstack-meeting04:22
samPThat's all from my side04:22
*** Manuel_112 has quit IRC04:23
samPAny other topics to discuss?04:23
tpatilsamP: After masakari becomes official project, do we need to take care of any additional things in advance?04:23
samPcode wise? or project wise?04:23
*** thorst_afk has quit IRC04:23
tpatilsamP: Overall04:23
samPI think code wise, not much04:23
tpatilsamP: Ok, and may be project wise , need to adhere to the goals and deadlines, correct?04:24
samPFrom project wise, we need to assign masakari core for tasks such co-project meetings, and TC meetings as such04:25
samPtpatil: correct04:25
*** tbh_ has joined #openstack-meeting04:25
tpatilsamP: Ok, thanks04:25
samPand need to be more careful with release04:25
*** gcb has joined #openstack-meeting04:26
tpatilsamP: Right04:26
samPI think we are pretty much doing everything as same as other official projects do, except release managements and other official project specific this.04:27
samPThere will be no huge changes04:27
*** markvoelker has joined #openstack-meeting04:27
samPs/this/tasks04:27
tpatilsamP: ok04:27
samPany this else to discuss?04:28
tpatilsamP: Nothing from my end04:28
samPtpatil: thanks04:28
Dinesh_Bhorfrom me too04:28
samPDinesh_Bhor: thanks04:28
samPOK then, bit early but we can finish the meeting early..04:29
tpatilsamP: ok04:29
samPIf you have anything to discuss, please use #openstack-masakari on IRC or openstack-dev ML with [masakari] prefix04:29
samPThank you all for attending04:30
samPAh,04:30
samPCan we cancel next we meeting because most of us in PTG?04:30
samPs/we/week04:31
tpatilsamP: Yes, please04:31
samPOK then, There will be no meeting on 9/1204:31
Dinesh_BhorOK04:31
samPInstead of that, we will have meeting at PTG. I will send the details to ML. please check04:32
tpatilsamP: sure04:32
samPOK then. let's finish04:32
samPthank you all04:32
samP#endmeeting04:33
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"04:33
openstackMeeting ended Tue Sep  5 04:33:02 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-09-05-04.00.html04:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-09-05-04.00.txt04:33
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-09-05-04.00.log.html04:33
*** tpatil has quit IRC04:34
*** cartik has joined #openstack-meeting04:37
*** rkmrHonjo has joined #openstack-meeting04:38
*** Manuel_112 has joined #openstack-meeting04:39
*** Manuel_112 has quit IRC04:44
*** marios has joined #openstack-meeting04:44
*** yamahata has joined #openstack-meeting04:48
*** pcaruana has joined #openstack-meeting04:52
*** baoli has joined #openstack-meeting04:54
*** b1airo has quit IRC04:56
*** baoli has quit IRC04:59
*** Manuel_112 has joined #openstack-meeting05:00
*** markvoelker has quit IRC05:00
*** Manuel_112 has quit IRC05:05
*** XueFengLiu has joined #openstack-meeting05:06
*** claudiub|2 has joined #openstack-meeting05:07
*** lpetrut has joined #openstack-meeting05:09
*** thorst_afk has joined #openstack-meeting05:20
*** cartik has quit IRC05:20
*** cartik has joined #openstack-meeting05:21
*** thorst_afk has quit IRC05:24
*** caowei has quit IRC05:26
*** caowei has joined #openstack-meeting05:30
*** Tom has joined #openstack-meeting05:32
*** trinaths has joined #openstack-meeting05:34
*** caowei has quit IRC05:36
*** unicell has joined #openstack-meeting05:39
*** bobmel has quit IRC05:43
*** janki has joined #openstack-meeting05:43
*** lpetrut has quit IRC05:46
*** wanghao has quit IRC05:50
*** wanghao has joined #openstack-meeting05:51
*** samP has left #openstack-meeting05:52
*** Manuel_112 has joined #openstack-meeting05:54
*** markvoelker has joined #openstack-meeting05:58
*** Manuel_112 has quit IRC05:58
*** Manuel_112 has joined #openstack-meeting05:59
*** lpetrut has joined #openstack-meeting05:59
*** wanghao_ has joined #openstack-meeting06:07
*** caowei has joined #openstack-meeting06:07
*** wanghao has quit IRC06:10
*** lpetrut has quit IRC06:18
*** thorst_afk has joined #openstack-meeting06:20
*** thorst_afk has quit IRC06:25
*** lpetrut has joined #openstack-meeting06:26
*** jprovazn has joined #openstack-meeting06:26
*** litao__ has joined #openstack-meeting06:26
*** fzdarsky_ is now known as fzdarsky06:26
*** markvoelker has quit IRC06:31
*** zsli_ has joined #openstack-meeting06:40
*** wanghao has joined #openstack-meeting06:41
*** wanghao_ has quit IRC06:42
*** Shunli has quit IRC06:43
*** rcernin has joined #openstack-meeting06:46
*** unicell has quit IRC06:46
*** lpetrut has quit IRC06:54
*** rkmrHonjo has quit IRC06:56
*** Tom has quit IRC07:03
*** Tom has joined #openstack-meeting07:03
*** Tom_ has joined #openstack-meeting07:05
*** Tom_ has quit IRC07:06
*** Tom_ has joined #openstack-meeting07:06
*** Tom has quit IRC07:08
*** cartik has quit IRC07:09
*** zsli_ has quit IRC07:12
*** tesseract has joined #openstack-meeting07:13
*** cartik has joined #openstack-meeting07:14
*** ykatabam1 has quit IRC07:17
*** thorst_afk has joined #openstack-meeting07:22
*** gcb has quit IRC07:22
*** gcb has joined #openstack-meeting07:22
*** cschwede_ has joined #openstack-meeting07:23
*** trinaths has quit IRC07:24
*** sshank has joined #openstack-meeting07:24
*** thorst_afk has quit IRC07:26
*** slaweq has joined #openstack-meeting07:29
*** cartik has quit IRC07:31
*** treiz has quit IRC07:32
*** treiz has joined #openstack-meeting07:32
*** marios has quit IRC07:34
*** tobiajo has joined #openstack-meeting07:37
*** oidgar has joined #openstack-meeting07:38
*** ralonsoh has joined #openstack-meeting07:41
*** tobiajo has quit IRC07:41
*** sshank has quit IRC07:42
*** tobiajo has joined #openstack-meeting07:44
*** tobiajo has quit IRC07:44
*** tobiajo has joined #openstack-meeting07:46
*** toscalix has joined #openstack-meeting07:55
*** toscalix has quit IRC07:56
*** toscalix_ has joined #openstack-meeting07:56
*** wanghao has quit IRC07:57
*** wanghao has joined #openstack-meeting07:57
*** hwoarang has left #openstack-meeting07:58
*** anilvenkata has joined #openstack-meeting08:01
*** janki is now known as janki|lunch08:02
*** slaweq_ has joined #openstack-meeting08:04
*** Tom_ has quit IRC08:04
*** Tom_ has joined #openstack-meeting08:05
*** Tom____ has joined #openstack-meeting08:06
*** Tom____ has quit IRC08:06
*** Tom____ has joined #openstack-meeting08:07
*** hashar has joined #openstack-meeting08:08
*** slaweq_ has quit IRC08:08
*** Tom_ has quit IRC08:09
*** marios has joined #openstack-meeting08:14
*** marios_ has joined #openstack-meeting08:16
*** thorst_afk has joined #openstack-meeting08:22
*** priteau has joined #openstack-meeting08:24
*** dbecker has joined #openstack-meeting08:25
*** trinaths has joined #openstack-meeting08:25
*** thorst_afk has quit IRC08:27
*** marios_ has quit IRC08:28
*** marios has quit IRC08:28
*** markvoelker has joined #openstack-meeting08:28
*** marios has joined #openstack-meeting08:29
*** rbartal has joined #openstack-meeting08:30
*** alexchadin has joined #openstack-meeting08:30
*** janki|lunch is now known as janki08:34
*** yangyapeng has quit IRC08:34
*** yangyapeng has joined #openstack-meeting08:35
*** caowei_ has joined #openstack-meeting08:37
*** caowei has quit IRC08:37
*** caowei_ is now known as caowei08:37
*** electrofelix has joined #openstack-meeting08:40
*** Tom____ has quit IRC08:50
*** yangyapeng has quit IRC08:52
*** yangyapeng has joined #openstack-meeting08:53
*** e0ne has joined #openstack-meeting08:54
*** e0ne has quit IRC09:00
*** markvoelker has quit IRC09:01
*** amotoki__away is now known as amotoki09:07
*** toscalix_ is now known as toscalix09:07
*** cartik has joined #openstack-meeting09:09
*** sambetts|afk is now known as sambetts09:20
*** e0ne has joined #openstack-meeting09:21
*** thorst_afk has joined #openstack-meeting09:23
*** shu-mutou is now known as shu-mutou-AWAY09:25
*** thorst_afk has quit IRC09:28
*** wanghao has quit IRC09:29
*** wanghao has joined #openstack-meeting09:29
*** wanghao has quit IRC09:29
*** wanghao has joined #openstack-meeting09:30
*** wanghao has quit IRC09:30
*** wanghao has joined #openstack-meeting09:31
*** wanghao has quit IRC09:31
*** wanghao has joined #openstack-meeting09:31
*** wanghao has quit IRC09:32
*** wanghao has joined #openstack-meeting09:32
*** wanghao has quit IRC09:33
*** wanghao has joined #openstack-meeting09:33
*** wanghao has quit IRC09:33
*** wanghao has joined #openstack-meeting09:34
*** wanghao has quit IRC09:34
*** wanghao has joined #openstack-meeting09:35
*** alexchadin has quit IRC09:46
*** alexchadin has joined #openstack-meeting09:47
*** Manuel_112 has quit IRC09:48
*** priteau has quit IRC09:51
*** markvoelker has joined #openstack-meeting09:58
*** yamamoto has quit IRC10:00
*** cartik has quit IRC10:01
*** lpetrut has joined #openstack-meeting10:05
*** Manuel_112 has joined #openstack-meeting10:07
*** Manuel_1_ has joined #openstack-meeting10:08
*** Manuel_112 has quit IRC10:08
*** epico has quit IRC10:14
*** yamamoto has joined #openstack-meeting10:15
*** thorst_afk has joined #openstack-meeting10:24
*** fzdarsky is now known as fzdarsky|lunch10:25
*** thorst_afk has quit IRC10:28
*** kevinz has quit IRC10:29
*** bkopilov has quit IRC10:31
*** markvoelker has quit IRC10:31
*** yamamoto has quit IRC10:37
*** caowei has quit IRC10:41
*** yangyapeng has quit IRC10:43
*** numans has quit IRC10:45
*** lakerzhou1 has joined #openstack-meeting10:48
*** fzdarsky has joined #openstack-meeting10:50
*** lakerzhou1 has quit IRC10:53
*** numans has joined #openstack-meeting10:54
*** jkilpatr has joined #openstack-meeting10:59
*** fzdarsky has quit IRC11:00
*** jkilpatr_ has joined #openstack-meeting11:01
*** yamamoto has joined #openstack-meeting11:02
*** lakerzhou1 has joined #openstack-meeting11:04
*** jkilpatr has quit IRC11:05
*** lakerzhou2 has joined #openstack-meeting11:06
*** lakerzhou1 has quit IRC11:09
*** rossella_s has quit IRC11:12
*** rossella_s has joined #openstack-meeting11:14
*** lakerzhou2 has quit IRC11:15
*** sdague has joined #openstack-meeting11:19
*** ansmith has quit IRC11:23
*** thorst_afk has joined #openstack-meeting11:25
*** tbh_ has quit IRC11:25
*** priteau has joined #openstack-meeting11:26
*** b1airo has joined #openstack-meeting11:28
*** markvoelker has joined #openstack-meeting11:29
*** fried_rice is now known as efried11:29
*** thorst_afk has quit IRC11:33
*** rcernin has quit IRC11:36
*** rcernin has joined #openstack-meeting11:36
*** Manuel_1_ has quit IRC11:37
*** dprince has joined #openstack-meeting11:39
*** julim has quit IRC11:40
*** rossella_s has quit IRC11:42
*** alexchadin has quit IRC11:44
*** alexchadin has joined #openstack-meeting11:44
*** rossella_s has joined #openstack-meeting11:45
*** kiennt_AWAY has quit IRC11:46
*** thorst_afk has joined #openstack-meeting12:00
*** jaypipes has joined #openstack-meeting12:00
*** markvoelker has quit IRC12:01
*** janki has quit IRC12:03
*** laurelm has quit IRC12:07
*** peterstac has quit IRC12:07
*** Manuel_112 has joined #openstack-meeting12:10
*** raildo has joined #openstack-meeting12:11
*** litao__ has quit IRC12:13
*** Manuel_112 has quit IRC12:15
*** markvoelker has joined #openstack-meeting12:16
*** rossella_s has quit IRC12:18
*** edmondsw has joined #openstack-meeting12:21
*** zhurong has quit IRC12:22
*** jamesmcarthur has joined #openstack-meeting12:23
*** edmondsw has quit IRC12:26
*** edmondsw has joined #openstack-meeting12:27
*** yangyapeng has joined #openstack-meeting12:28
*** jamesmcarthur has quit IRC12:28
*** Manuel_112 has joined #openstack-meeting12:31
*** fzdarsky has joined #openstack-meeting12:31
*** edmondsw has quit IRC12:31
*** bobmel has joined #openstack-meeting12:33
*** Manuel_112 has quit IRC12:36
*** bobmel_ has joined #openstack-meeting12:41
*** ansmith has joined #openstack-meeting12:44
*** bobmel__ has joined #openstack-meeting12:44
*** eharney has quit IRC12:45
*** bobmel has quit IRC12:45
*** dmsimard is now known as dmsimard|afk12:47
*** VW has joined #openstack-meeting12:48
*** bobmel_ has quit IRC12:48
*** VW has quit IRC12:48
*** VW has joined #openstack-meeting12:48
*** scottda_ has joined #openstack-meeting12:49
*** oidgar has quit IRC12:50
*** davidsha has joined #openstack-meeting12:51
*** Manuel_112 has joined #openstack-meeting12:52
*** janki has joined #openstack-meeting12:52
*** rossella_s has joined #openstack-meeting12:53
*** juzuluag has joined #openstack-meeting12:53
*** jamesmcarthur has joined #openstack-meeting12:54
*** bobh has joined #openstack-meeting12:54
*** baoli has joined #openstack-meeting12:54
*** baoli has quit IRC12:54
*** pchavva has joined #openstack-meeting12:56
*** Manuel_112 has quit IRC12:56
*** zhurong has joined #openstack-meeting12:56
*** esberglu has joined #openstack-meeting12:57
*** persia has joined #openstack-meeting12:58
*** persia_ has joined #openstack-meeting12:58
*** kylek3h has joined #openstack-meeting12:58
*** edmondsw has joined #openstack-meeting12:58
*** ruijie has joined #openstack-meeting13:00
*** baoli has joined #openstack-meeting13:00
*** rbudden has joined #openstack-meeting13:00
Qiming#startmeeting senlin13:03
openstackMeeting started Tue Sep  5 13:03:00 2017 UTC and is due to finish in 60 minutes.  The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot.13:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:03
*** openstack changes topic to " (Meeting topic: senlin)"13:03
openstackThe meeting name has been set to 'senlin'13:03
*** elynn has joined #openstack-meeting13:04
*** galstrom_zzz is now known as galstrom13:05
*** oidgar has joined #openstack-meeting13:05
*** mriedem has joined #openstack-meeting13:06
Qiminghi, guys, any outstanding issues to discuss today?13:06
ruijie0/13:06
elynnHi Qiming ruijie13:06
*** shaohe_feng has quit IRC13:06
ruijiehi elynn Qiming.13:07
Qimingelynn, long time no see, :)13:07
*** bkopilov has joined #openstack-meeting13:07
elynnI don't have issue to discuss ~ Just to keep in pace with you guys.13:07
elynn..... Some meeting from ONAP are conflict with senlin weekly meeting..13:08
Qimingokay13:08
elynnSometimes I have to choose...13:08
ruijieoh, just proposed patches about revising GC work13:08
Qimingno problem, elynn13:09
*** kevzha01 has joined #openstack-meeting13:09
*** zhurong has quit IRC13:10
elynnI guess ruijie get used to being a PTL now :)13:10
Qimingstarting next week, ruijie will host the weekly meeting?13:11
ruijieokay Qiming:)13:11
Qimingcool13:12
ruijieNoticed next week is Queens Goals Research?13:12
ruijieit's about the PTG or all projects?13:12
elynnWill you attend PTG?13:13
*** Manuel_112 has joined #openstack-meeting13:13
Qimingboth ptg and goals research13:13
*** gouthamr has joined #openstack-meeting13:13
Qimingno funding from my side to attend this PTG13:13
ruijieno, I am not going there :)13:13
*** chenyb4_ has joined #openstack-meeting13:13
*** shaohe_feng has joined #openstack-meeting13:14
*** kevzha01_ has joined #openstack-meeting13:14
*** alexchadin has quit IRC13:14
Qimingnot a cheap trip for people out of US13:14
QimingPTG is against non-americans, ... just my personal feeling13:14
elynnYes, ticket isn't free.13:14
ruijieflight is expensive :)..13:15
*** chenyb4_ has quit IRC13:16
elynnWe could hold some virtual meeting if needed.13:17
*** kevzha01 has quit IRC13:17
Qiminganother patch you may want to review is about the one about lb policy improvement13:17
elynnto discuss the features.13:17
*** julim has joined #openstack-meeting13:17
*** Manuel_112 has quit IRC13:17
Qiming+113:17
ruijiewe can have virtual meetings or we can find a place to have a meeting?13:18
elynnBoth works for me.13:19
elynnXinhui and me might attend the PTG next week, the week after next week is fine.13:19
*** noslzzp has joined #openstack-meeting13:20
Qimingokay13:20
elynnONAP plan to do code freeze next week, it's super busy for us these weeks13:20
Qimingalright13:22
elynnQiming, you mean this patch about lb policy https://review.openstack.org/#/c/500713/ ?13:22
*** toscalix has quit IRC13:22
Qimingyes13:23
Qimingthat is a good starting point at least13:23
ruijiebtw elynn, what do you mean by having virtual meeting? we have other tools besides IRC?13:23
*** tobiajo has quit IRC13:23
*** chenyb4_ has joined #openstack-meeting13:24
elynnruijie, we can find some tools  for virtual meeting, webex , zoom, or skype which support screen sharing.13:24
elynnIn ONAP, we use zoom for weekly meeting, it's a nice tool.13:25
*** lpetrut_ has joined #openstack-meeting13:27
*** b1airo has quit IRC13:28
elynnQiming, it seems they need to adopt existing VIP into LB policy?13:28
Qimingyes13:28
QimingI commented that those LBs should be deleted when the policy is detached13:29
*** lpetrut has quit IRC13:29
elynnSounds like a feature13:30
*** zerick has quit IRC13:31
*** numans has quit IRC13:32
*** bobmel__ has quit IRC13:32
*** zerick has joined #openstack-meeting13:33
*** shaohe_feng has quit IRC13:33
*** Manuel_112 has joined #openstack-meeting13:33
*** shaohe_feng has joined #openstack-meeting13:33
*** bobmel has joined #openstack-meeting13:34
*** juzuluag has quit IRC13:34
*** bobmel has quit IRC13:35
elynnIt's a good start to support this case.13:35
*** bobmel has joined #openstack-meeting13:36
*** eharney has joined #openstack-meeting13:37
*** Manuel_112 has quit IRC13:38
Qimingagree13:38
*** numans has joined #openstack-meeting13:40
*** bobmel has quit IRC13:41
*** bobmel has joined #openstack-meeting13:41
*** artom_ has quit IRC13:41
*** jamesmcarthur has quit IRC13:41
*** jamesmcarthur has joined #openstack-meeting13:42
*** kevzha01__ has joined #openstack-meeting13:43
*** mriedem has quit IRC13:43
*** baoli_ has joined #openstack-meeting13:43
*** mriedem has joined #openstack-meeting13:44
*** baoli has quit IRC13:46
*** kevzha01_ has quit IRC13:46
*** jamesmcarthur has quit IRC13:46
*** marst has joined #openstack-meeting13:50
*** fnaval has joined #openstack-meeting13:50
*** reedip_ has joined #openstack-meeting13:51
Qimingif we don't have more topics to discuss13:51
Qimingwe can end the meeting now13:51
Qiming#endmeeting13:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:52
openstackMeeting ended Tue Sep  5 13:52:19 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-09-05-13.03.html13:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-09-05-13.03.txt13:52
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-09-05-13.03.log.html13:52
*** toscalix has joined #openstack-meeting13:53
*** Manuel_112 has joined #openstack-meeting13:54
*** kevzha01_ has joined #openstack-meeting13:55
*** annp has joined #openstack-meeting13:55
*** ijw has joined #openstack-meeting13:57
*** kevzha01__ has quit IRC13:58
*** Manuel_112 has quit IRC13:59
*** shintaro has joined #openstack-meeting13:59
davidshaHi14:00
*** elynn has quit IRC14:00
reedip_o/14:00
bcafarelhowdy14:00
*** chenyb4_ has left #openstack-meeting14:00
davidsha#startmeeting network_common_flow_classifier14:00
openstackMeeting started Tue Sep  5 14:00:37 2017 UTC and is due to finish in 60 minutes.  The chair is davidsha. 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: network_common_flow_classifier)"14:00
openstackThe meeting name has been set to 'network_common_flow_classifier'14:00
*** dtrainor has joined #openstack-meeting14:00
*** kevzha01_ has quit IRC14:00
davidshaI'll wait 2 minutes for others to join, tmorin said he can't make it today.14:01
reedip_oh ok ..14:01
*** galstrom is now known as galstrom_zzz14:01
davidshaThe Agenda is here if anyone would like to add things to it: https://wiki.openstack.org/wiki/Neutron/CommonClassificationFramework14:01
davidshaOk, we'll start now14:03
davidsha#topic CCF v0 - Update14:03
*** openstack changes topic to "CCF v0 - Update (Meeting topic: network_common_flow_classifier)"14:03
reedip_Checking the Agenda14:03
*** erlon has quit IRC14:03
*** numans has quit IRC14:04
reedip_ok14:04
davidshaSo I've taken over the patches Thaynara has submitted, and breaking them down14:04
davidshahttps://review.openstack.org/#/q/project:openstack/neutron-classifier+status:open14:04
davidshaThere are 4 at the moment, the database migration, the database models and OvOs, the Service Plugin and the Openstack CLI14:05
*** julim_ has joined #openstack-meeting14:05
bcafarelthe service plugin is the "v0 patch" review?14:06
davidshabcafarel: correct14:06
*** oidgar has quit IRC14:06
reedip_need to rename it :)14:07
davidshaI've manager to drop the size of v0 down to ~1000 lines of code, which is an improvement from ~3500 :)14:07
bcafarelyay on that big reviews are a pain to do14:07
reedip_YEP !14:07
*** rlpple has joined #openstack-meeting14:07
davidshareedip_: Well it technically is the V0 API ;P14:07
*** julim has quit IRC14:08
davidshaI do need to fill out the tests a bit more, so it will probably rise to about ~150014:08
reedip_I will look into them tomorrow... I checked the DB patch though14:08
*** hongbin has joined #openstack-meeting14:09
davidshaI saw, thanks for reviewing, If there aren't any questions on this update we can move onto the discussion around the db?14:09
*** numans has joined #openstack-meeting14:10
bcafarelnothing much to say on the other patches, they are still in my review list14:10
*** oidgar has joined #openstack-meeting14:10
davidshabcafarel: kk, thanks for looking!14:10
davidshaOk so moving on14:11
bcafarelthough one (maybe stupid question), the cli plugin will be in the neutron-classifier repo or will it move to python-neutronclient in the "long term"?14:11
davidshabcafarel: For now, we'll keep it in repo, going forward that will probably change.14:11
reedip_bcafarel : it will be in the repo for now14:12
reedip_once it is merged, then it will be moved to neutronclient14:12
reedip_thats what is atleast happeing in tap-as-a-service14:13
bcafarelok thanks14:13
davidshareedip_: That seems like the best way14:13
davidshaOk14:13
*** cloudrancher has quit IRC14:13
davidsha#topic CCF v0 - Database models + Classification fields14:14
*** openstack changes topic to "CCF v0 - Database models + Classification fields (Meeting topic: network_common_flow_classifier)"14:14
davidshaSo there was a lot of discussion here: https://review.openstack.org/#/c/498471/5/neutron_classifier/db/migration/alembic_migrations/versions/pike/expand/4e97d48da530_initial_ccf_database_.py14:14
*** cloudrancher has joined #openstack-meeting14:15
davidshaJust to work from top to bottom, tmorin mentioned ranges14:15
*** Manuel_112 has joined #openstack-meeting14:15
reedip_Line# ?14:15
davidshaline 014:15
reedip_Ohh :P)14:16
davidsha:p14:16
davidshaI was talking to someone about this and we can do 2 things.14:16
davidshatmorin's suggestion of a min_port and a max_port field where we want to specify a range14:17
reedip_ok /14:17
davidshaOr we could have another operator type called "range" allowing AND,OR and RANGE.14:17
reedip_davidsha : how will the RANGE operator work ?14:18
davidshareedip_: Only allow 1 classification type inside the group and the values range from min to max.14:19
*** jchhatbar has joined #openstack-meeting14:19
reedip_davidsha : it would be pretty complicated API , isnt it ???14:20
*** janki has quit IRC14:20
*** Manuel_112 has quit IRC14:20
davidshareedip_: ya, the alternative is sticking the same value into min and max fields if someone isn't using range.14:20
davidshausing a range*14:21
reedip_ok ..I am still trying to imagine it ...14:22
davidshareedip_: The first is what they currently do in security groups I believe14:23
reedip_oh ok , I think I understood with that example14:23
*** SarathMekala has joined #openstack-meeting14:23
*** yamamoto has quit IRC14:24
davidshaFor the second the workflow would be: make tcp_min tcp classification, make tcp_max tcp classification and then create a classification group consuming them and setting the operator to range.14:24
*** beekneemech is now known as bnemec14:25
*** yamamoto has joined #openstack-meeting14:25
reedip_Ok, I think the first idea is easier but we need to identify if we may require the second option in the future?14:26
davidshakk,14:26
*** eharney_ has joined #openstack-meeting14:26
*** eharney has quit IRC14:27
davidshaIs there anything either of you want to pick out in particular from the file to discuss?14:28
bcafareljust generic remark to stick around the same sizes as other neutron tables (address size, ...)14:29
reedip_not from the file as of now ...14:29
reedip_actually yes, Line#4614:29
reedip_the ID14:29
davidshabcafarel: Understood, That will be one of the first this I'll update14:29
davidshareedip_: Correct me if I'm wrong, it's to remove the idea and use the combination of classification_group and classification as it's uniqueness condition correct?14:31
reedip_correct14:31
davidshaidea -> id*14:31
reedip_not the idea, the ID14:31
reedip_hehehe14:31
davidshaO-oh... *undoes last 2 hours of work*14:32
reedip_??14:32
*** galstrom_zzz is now known as galstrom14:32
davidshaSure, is there an example of this somewhere else in the codebase?14:33
davidshareedip_: a bad joke14:33
reedip_davidsha : need to search14:33
davidshakk, I can look later.14:33
bcafarel:)14:33
bcafarelalso https://review.openstack.org/#/c/499571/2/neutron_classifier/db/models.py comment from tmorin is a great suggestion I think14:34
bcafareladding a DB/model sync test could prove useful14:34
*** yamamoto has quit IRC14:35
davidshabcafarel: working on it atm, hopefully I'll have it up soon.14:35
bcafareldavidsha: nice!14:35
*** Manuel_112 has joined #openstack-meeting14:36
davidshaJust a heads up on that patch also, the tests for the Oslo Versioned Objects import all the core neutron objects too.14:36
davidshahttps://review.openstack.org/#/c/499571/2/neutron_classifier/tests/unit/objects/test_objects.py14:37
davidshaline #5914:37
davidshaWhen I was writing the tests I found there were some neutron objects leaking into the test, so I just added them all and test ours with theirs.14:37
*** links has quit IRC14:37
davidshaI don't think it should cause a problem, buts it's something I'll keep an eye on.14:38
reedip_ok14:39
davidshaThe general comments about renaming fields, will we just discuss those in the patch?14:40
davidshaOr removing fields also14:40
*** eharney_ is now known as eharney14:41
*** Manuel_112 has quit IRC14:41
davidshaWill we move on if there isn't anything else?14:42
reedip_there is nothing else to add for now on the DB patch14:42
davidshaok14:42
bcafarelgood for me too14:42
davidsha#topic PTG updates14:42
*** openstack changes topic to "PTG updates (Meeting topic: network_common_flow_classifier)"14:42
*** bobmel has quit IRC14:43
*** annp has quit IRC14:43
davidshaWe covered this last time, but myself and Igor cannot attend, reedip_ you're not attending either are you?14:43
reedip_no , I am not14:44
davidshabcafarel: are you attending?14:44
bcafareldavidsha: another no :(14:44
reedip_Then I guess we can have our normal weekly meeting post PTG. :)14:45
davidshakk, so tmorin is the only one from CCF attending, Yup!14:45
davidshaThe cores were discussing dialing in, so I'll try and keep an eye out for that.14:46
*** jchhatbar_ has joined #openstack-meeting14:46
* bcafarel checks the Denver time zone14:46
davidshaI know it starts at 16:00PM for me.14:47
bcafarelUTC-7 ouch14:47
davidshaSo around now actually14:47
reedip_davidsha : whats your tz14:47
*** marios has quit IRC14:47
davidshaUTC 0, I think I've gotten that wrong...14:48
*** marios has joined #openstack-meeting14:48
reedip_ok, I am +0530 , so I need to keep a jug of coffee14:48
davidshaNo almost 9:00AM in denver now.14:48
davidshareedip_: What time is it over there now?14:48
*** jchhatbar has quit IRC14:49
reedip_201914:49
reedip_hrs14:49
*** jchhatbar_ has quit IRC14:49
davidshaOuch14:49
bcafarelreedip_: I think you'll need something stronger than coffee!14:49
davidshaDon't be afraid to Irish it up ;)14:49
reedip_dont have anything else ... RedBull carshes me out ...14:49
reedip_I will search for Baileys :P14:49
davidshaI think we should move on almost out of time.14:50
reedip_yep14:50
davidsha#topic Call for requirements14:50
*** openstack changes topic to "Call for requirements (Meeting topic: network_common_flow_classifier)"14:50
davidshaI was talking to DragonFlow guys, they seem to want to use neutron classifier to match on neutron resources (ie. TaPaas, LBaas, etc)14:51
reedip_ok ...14:51
reedip_FWaaS team is interested , SridarK , xgerman_ , yushiro would be there in Denver for this14:52
reedip_I wont be there but I will be looking out for this topic :)14:52
davidshaSame, I'll be interested to see what they have for us.14:53
*** oidgar has quit IRC14:54
davidshaI haven't gotten in touch with the author of the security groups RFE, but I'll try for next meeting.14:54
reedip_davidsha : link ?14:55
*** Manuel_112 has joined #openstack-meeting14:57
davidshareedip_: Can't find it and running out of time, it was mentioned in the drivers meetings in early August I believe.14:57
reedip_davidsha : so I look into the logs ( or neutronspecs ? ). I will look into the neutron-specs and the logs , nevermind :)14:57
davidshareedip_: I'll find it for you afte14:58
davidshaIs there anything else before we call time?14:58
reedip_dont worry, I will try and if I dont find, will ask you :)14:58
reedip_nothing from myu sdie14:58
bcafarelgood for me too14:58
davidshaWill we call it then?14:58
*** rlpple has quit IRC14:58
davidshaThanks everyone!14:59
davidsha#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Tue Sep  5 14:59:22 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2017/network_common_flow_classifier.2017-09-05-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2017/network_common_flow_classifier.2017-09-05-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2017/network_common_flow_classifier.2017-09-05-14.00.log.html14:59
*** diablo_rojo has joined #openstack-meeting14:59
*** shintaro has quit IRC15:00
*** rbartal has quit IRC15:01
*** Manuel_112 has quit IRC15:01
*** artom_ has joined #openstack-meeting15:04
*** felipemonteiro has joined #openstack-meeting15:07
*** felipemonteiro_ has joined #openstack-meeting15:09
*** felipemonteiro has quit IRC15:13
*** jamesgu has joined #openstack-meeting15:13
*** Manuel_112 has joined #openstack-meeting15:17
*** SarathMekala has quit IRC15:18
*** oidgar has joined #openstack-meeting15:18
*** lin_yang has joined #openstack-meeting15:18
*** reedip_ is now known as reedip_leaving15:22
*** reedip_leaving has quit IRC15:22
*** Manuel_112 has quit IRC15:22
*** jamesmcarthur has joined #openstack-meeting15:23
*** gmann has quit IRC15:24
*** annegentle has joined #openstack-meeting15:24
*** gmann has joined #openstack-meeting15:24
*** lbragstad has joined #openstack-meeting15:25
*** jamesmcarthur has quit IRC15:27
*** jamesmcarthur has joined #openstack-meeting15:27
*** cleong has joined #openstack-meeting15:28
*** bobmel has joined #openstack-meeting15:29
*** e0ne has quit IRC15:32
*** gyee has joined #openstack-meeting15:32
*** b4rti has quit IRC15:33
*** dtrainor_ has joined #openstack-meeting15:34
*** bobmel has quit IRC15:35
*** yamamoto has joined #openstack-meeting15:35
*** ruijie has quit IRC15:35
*** baoli_ has quit IRC15:37
*** hashar is now known as hasharAway15:38
*** dtrainor has quit IRC15:38
*** baoli has joined #openstack-meeting15:38
*** Manuel_112 has joined #openstack-meeting15:38
*** yamamoto has quit IRC15:43
*** Manuel_112 has quit IRC15:43
*** bobmel has joined #openstack-meeting15:45
*** bobmel has quit IRC15:51
*** artom_ is now known as artom15:53
*** bobmel has joined #openstack-meeting15:54
*** cloudrancher has quit IRC15:54
*** psachin has quit IRC15:55
*** cloudrancher has joined #openstack-meeting15:55
*** jlibosva has joined #openstack-meeting15:57
*** Manuel_112 has joined #openstack-meeting15:59
*** ihrachys has joined #openstack-meeting16:00
ihrachys#startmeeting neutron_ci16:00
openstackMeeting started Tue Sep  5 16:00:47 2017 UTC and is due to finish in 60 minutes.  The chair is ihrachys. 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
ihrachysjlibosva, haleyb o/16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
jlibosvao/16:00
haleybhi16:00
ihrachyswe have some actual juice to discuss today, let's get going16:01
*** bobmel has quit IRC16:01
ihrachysfirst...16:01
ihrachys#topic Actions from prev week16:01
*** openstack changes topic to "Actions from prev week (Meeting topic: neutron_ci)"16:01
ihrachys"jlibosva to tweak gate not to create default subnetpool and enable test_convert_default_subnetpool_to_non_default"16:01
jlibosvaI did investigate the option and it seems the default subnet is created because it's required by auto_allocated_topology tests16:01
*** bobmel has joined #openstack-meeting16:01
jlibosvaas I'm not really familiar with auto allocated topology feature, I'll need to talk to armax to see whether we can create the default subnet before running the auto allocated topology tests and then remove it16:02
ihrachys#action jlibosva to talk to armax about enabling test_convert_default_subnetpool_to_non_default in gate16:03
jlibosvait will require some external locking so auto allocated topology and default subnet tests don't run in parallel16:03
ihrachysI see. I think tests in same class don't run in parallel16:03
ihrachysso you can use that16:03
*** Manuel_112 has quit IRC16:04
jlibosvaaha, you mean to put auto allocated topology and default subnet under the same class16:04
ihrachysyeah. that will give you necessary serialization. I am not sure if it makes sense logically though.16:04
ihrachysI mean, in terms of code quality16:05
*** marst has quit IRC16:05
*** marst has joined #openstack-meeting16:05
ihrachysok let's move on16:06
ihrachysnext item was "anilvenkata to add more control plane checks for migrated router ports tests before ssh'ing"16:06
*** iyamahat has joined #openstack-meeting16:06
ihrachysI believe anilvenkata sent a bunch of fixes for the issues16:06
ihrachyshttps://review.openstack.org/#/c/500384/16:06
ihrachysI believe it will be eventually split16:06
ihrachyscorrect?16:06
jlibosvaalso https://review.openstack.org/#/c/500379 I think is relevant16:07
ihrachysI see. I will have a look at that one too16:07
ihrachysso seems like a good progress, let's make it to completion :)16:07
*** iyamahat has quit IRC16:08
* haleyb will look as well of course16:08
*** iyamahat has joined #openstack-meeting16:08
ihrachysnext was "ihrachys to complete gate-failure cleanup"16:08
ihrachysI did close quite some bugs that haven't showed up16:08
* jlibosva will look too and will be like "hmmm, l3 code ... "16:08
ihrachysI also looked closely through all fullstack bugs and tried to fix/triage some of them16:08
ihrachyswe will discuss specific patches later16:08
ihrachyslet's look at the gate16:09
ihrachys#topic Grafana16:09
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:09
ihrachyshttp://grafana.openstack.org/dashboard/db/neutron-failure-rate16:09
* jlibosva refreshes grafana page16:09
ihrachysI see rally being at 100% a while ago, but that should be fixed now.16:09
ihrachysin master16:09
*** marios has quit IRC16:09
ihrachysI backported the fixes to stable: https://review.openstack.org/#/q/I80c9a155ee2b52558109c764075a58dfabee44d4,n,z16:09
ihrachyswe also have grenade-dvr at 100% right now16:10
*** iyamahat_ has joined #openstack-meeting16:10
ihrachysis it the same failure we were struggling with the last week?16:10
jlibosvawere stable branches also affected by the rally?16:10
ihrachysjlibosva, I would think so, since devstack-gate is branchless16:10
haleybwe have two patches ready for that, got blocked when tox failed, then rally16:10
jlibosvaok16:10
*** iyamahat_ has quit IRC16:11
haleybi'm assuming we're talking the keyerror revert and fix16:11
*** iyamahat_ has joined #openstack-meeting16:11
ihrachyshaleyb, that will be https://review.openstack.org/#/c/499292/ and https://review.openstack.org/#/c/499585/ and https://review.openstack.org/#/c/499725/ ?16:11
jlibosvaI looked at the grenade failure and updated LP bug about what I saw in the logs. I thought that my patch ignoring host in fip object caused back the regression we were fighting with16:11
*** marst_ has joined #openstack-meeting16:11
*** marst has quit IRC16:12
haleybihrachys: yes, thought there were only two but i'll look at those 316:12
jlibosvaalso worth mentioning that I made the grenade dvr job non-voting as we weren't able to merge the rally patch with both jobs failing16:12
ihrachysjlibosva, ok. I think it's a good call in general before we prove it's back to normal16:12
ihrachyswe already wasted ~week of gate16:13
*** numans has quit IRC16:13
haleyboh, I just +2'd that last one, so yes 316:13
ihrachysETOOMANYPATCHES16:13
*** iyamahat has quit IRC16:13
haleybihrachys: and we'll keep working on the server side, then take a deep breath16:13
*** yamahata has quit IRC16:14
jlibosvaI'm confused, I guess we still need to fix the pike branch?16:14
ihrachyswe also have scenario jobs at 100%. what's the latest status there? I believe anilvenkata's fixes should help that in part, but do we have full picture of remaining items?16:14
*** Apoorva has joined #openstack-meeting16:14
ihrachysI also believe dvr keyerror issue was affecting it16:14
jlibosvaI haven't been tracking the failures since the etherpad16:14
ihrachysjlibosva, we probably need to backport all those 3 fixes16:14
ihrachys(revert is effectively already there, so 2)16:14
haleybi though we backported jlibosva's keyerror fix out-of-order16:15
jlibosvayeah, that's why I think it broke the job again16:15
haleybi.e. pike first, then master since we needed it in the "old" grenade16:15
ihrachysjlibosva, ok. I think it's fine to leave the router migration and some other work to proceed and revisit the state after those fixes in.16:15
*** numans has joined #openstack-meeting16:15
jlibosvawe're talking about two topics now :)16:16
ihrachys:)16:16
ihrachysok, let's focus on grenade/dvr16:16
jlibosvaack16:16
*** dtrainor_ has quit IRC16:16
ihrachysmy understanding is, we have 3 fixes: revert + 2 new.16:16
*** dtrainor_ has joined #openstack-meeting16:16
ihrachyswe landed revert in pike because it blocked master revert16:16
ihrachysnow we try to push the revert in master16:16
ihrachyssince the job is non-voting it should go in smoothly despite pike being broken by keyerror16:17
haleybwe also pushed the second (fix keyerror) in pike16:17
jlibosvabut the pike is still broken now as per grafan16:17
ihrachysjlibosva, because we haven't merged all 3 fixes in pike no?16:17
jlibosvaso haleyb do you think it's possible that my fix that went to pike only broke the job again - as it might be causing the same behavior as swami's patch?16:17
ihrachyshaleyb, you pushed? merged you mean?16:17
ihrachysit would be nice to test all patches in one go, both backports and master fixes, with some kind of DNM patch16:18
haleybhttps://review.openstack.org/#/c/500077/ one16:18
ihrachysI *think* gate actually allows depends-on for patches in multiple branches16:18
*** marst has joined #openstack-meeting16:18
ihrachyshaleyb, I see, I wasn't aware of thta16:18
*** marst_ has quit IRC16:19
jlibosvaand I think the 500077 broke the gate again16:19
jlibosvaas per grafana: http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=11&fullscreen16:19
haleybihrachys: it was backwards because once we merged the revert to pike we couldn't land things in master...16:19
jlibosvaif you look at 7 days history, the curve goes up after the patch has been merged16:19
ihrachyshaleyb, ok. comments on what jlibosva suggested? ^16:20
*** Manuel_112 has joined #openstack-meeting16:20
jlibosvaso maybe the only way how to fix it is the server side patch16:20
ihrachysI would be glad if we avoid some reverts/backports before we are sure those don't break anything16:20
jlibosvathe job was still failing on keyerror after the revert on the gate queue16:21
jlibosvain master16:21
ihrachysyes. the original patch was actually trying to fix the keyerror16:21
jlibosvawhich I don't understand why it wasn't hapenning in check queue ...16:21
ihrachysand then broke the gate with duplicate fips16:21
*** dtrainor_ has quit IRC16:21
haleybjlibosva: what was your proposal?  I'm sure it will be great :)16:21
*** dtrainor_ has joined #openstack-meeting16:22
ihrachysso we had keyerror; then we fixed it but regressed with duplicate fips; then we reverted the latter and got keyerrors back; now we try to fix keyerrors.16:22
jlibosvahaleyb: my suggestion is to ask haleyb and swami for help :-p16:22
ihrachyshaha16:22
ihrachyswell this sh*t is definitely on l3 team to solve, so I kinda agree Swami and Brian should be involved ;)16:22
ihrachysit all started with the late feature backport for new dvr mode16:23
*** marst_ has joined #openstack-meeting16:23
haleybyes, we can take the blame for that, armando warned us...16:23
*** marst has quit IRC16:23
*** trinaths has left #openstack-meeting16:23
ihrachysI don't care about blame. I want my precious gate back to normal. :)16:23
jlibosvadon't tell him, he'd be like "I told you"16:23
* haleyb goes to his corner16:24
ihrachysanyway16:24
ihrachys#action haleyb to figure out the way forward for grenade/dvr gate16:24
jlibosvaone thing I don't understand is why the keyerror was happening on the gate queue only - after the revert of swami's patch16:24
ihrachysluck?16:24
ihrachysI think the original keyerror was not breaking 100%?16:24
jlibosvamaybe the reproducer was lower than current issue16:25
*** Manuel_112 has quit IRC16:25
jlibosvaywah16:25
haleybit depends on where the VM was launched from what i remember, so wasn't 100%16:25
jlibosvabut now it is 100%16:25
jlibosvaanyway, let's move on :)16:25
jlibosvamaybe we should revert my patch from pike and not merge it in master16:26
ihrachysI will let haleyb to dig ;) I will stay and watch the house burning.16:26
ihrachysjlibosva, maybe. maybe not. that's why I would love to see some gate proof we have a final resolution.16:27
jlibosvahttps://i.imgur.com/c4jt321.png16:27
*** iyamahat__ has joined #openstack-meeting16:27
*** davidsha has quit IRC16:27
ihrachysjlibosva, that was exactly my reaction when I noticed tox ALL RED failure late Friday16:27
ihrachysI said f* it and turned off irc16:27
jlibosva:D16:27
ihrachysanyway... let's switch topics16:28
*** annegentle has quit IRC16:28
ihrachysso scenario jobs. they fail, but we have router migrations work and keyerror work in the pipeline, so it probably would make sense to revisit the failure rate once those are tackled.16:28
ihrachysso finally, fullstack job16:29
ihrachysthat one was on me to triage16:29
ihrachysand after weeks of procrastination I actually did. yay Ihar.16:29
ihrachysI started https://etherpad.openstack.org/p/queens-neutron-fullstack-failures16:29
jlibosvaI wouldn't call that procrastination but go on :)16:29
ihrachysand I also looked through reported bugs in gate-failure16:29
ihrachysand sent some patches, pulled some people16:30
ihrachysfirst, to skip test_mtu_update for linuxbridge: https://review.openstack.org/#/c/498932/16:30
*** iyamahat_ has quit IRC16:30
ihrachysbecause for lb, we start dhcp agent in a namespace, and so qdhcp- netns is inside this agent namespace16:31
ihrachysand we don't have ip_lib supporting digging devices inside a 2nd order namespace16:31
ihrachyslater we may revisit that16:31
ihrachyssecond is test_ha_router sporadic failure. I sent this: https://review.openstack.org/#/c/500185/16:31
*** marst has joined #openstack-meeting16:31
*** marst_ has quit IRC16:32
ihrachysit basically seems that neutron-server may take some time to schedule both agents to the router, so there is a short window when only a single agent is scheduled16:32
ihrachysand it fails with 2 != 116:32
ihrachysthe patch makes the test wait, like other test cases do16:32
haleyblgtm16:32
ihrachysI actually believe there may be a server side bug here, because ideally it would immediately schedule both16:32
ihrachysand haleyb said he will have a look.16:33
ihrachys;)16:33
anilvenkataihrachys, jlibosva haleyb sorry I was away at that time16:33
ihrachysbut I don't think it's at top priority16:33
anilvenkatafor migration tests I proposed this patch https://review.openstack.org/#/c/500384/16:33
haleybi started looking friday, will continue16:33
ihrachysanilvenkata, np, I think we are good. but an update on how far we are for migration fixes to land would be nice.16:33
anilvenkataconstantly monitoring failures and updating this patch16:33
anilvenkataihrachys, failures have come done16:34
*** iyamahat__ has quit IRC16:34
ihrachysdown?16:34
anilvenkataearlier most of them are failing, now one or two16:34
ihrachysgooooood16:35
jlibosvaanilvenkata: great job! :)16:35
ihrachyswe'll loop in our best troops16:35
ihrachysaka haleyb16:35
anilvenkataI am tracking them and constantly updating the patchset, there are multiple issues(at least reported 4 bugs :) )16:35
ihrachysanilvenkata, keep them coming lol16:35
anilvenkataonce the tests are constantly passing, I will ask for review16:36
anilvenkatathanks ihrachys jlibosva haleyb16:36
ihrachysanilvenkata, ++ you da man16:36
anilvenkatathanks :)16:36
ihrachysok. we were talking about fullstack16:36
anilvenkataok16:37
ihrachysthe last thing I am aware is, some HA tests were failing because ml2 plugin was incorrectly setting dhcp provisioning block on port update while dhcp agent was not aware of any action to do on its side, so port never came to ACTIVE16:37
anilvenkataI also noticed that16:37
ihrachysI digged that, talked to kevinbenton, and it seems like now we have a fix for that: https://review.openstack.org/#/c/500269/16:37
jlibosvadhcp HA or l3 HA?16:37
*** Swami has joined #openstack-meeting16:37
ihrachysjlibosva, l3 ha16:37
ihrachysbut maybe it's not l3 ha specific16:38
anilvenkatal3 ha waiting for dhcp provisioning16:38
ihrachysit's just the fact that fullstack l3ha test case triggered it16:38
jlibosvaso fullstack found yet another real issue?16:38
ihrachysthe fix is now in gate, so we once those three are in, we may expect some better results.16:38
ihrachysjlibosva, how is it news?16:38
ihrachysthat's what it does.16:38
jlibosvagood guy fullstack16:38
ihrachysyeah, he is the cool kid in the hood16:39
ihrachyssadly not everyone realized that yet16:39
ihrachysand that's what I had for grafaan16:39
jlibosvaspeaking about fullstack, I found some time today to do some real work16:39
ihrachysany other interesting artifacts of grafana that I missed?16:40
*** ijw has quit IRC16:40
ihrachysjlibosva, work on isolating ovs?16:40
jlibosvaand did some of the isolation work, I plan to continue with the work this week16:40
anilvenkatakevinbenton, Kevin is awesome in proposing quick fixes like this https://review.openstack.org/#/c/500269/3/neutron/plugins/ml2/plugin.py16:40
jlibosvayeah, it's not just ovs, but simulating better the nodes - it will give us a chance to run two neutron servers16:41
jlibosvaso with haproxy, we could also test active/active server16:41
ihrachysoh, that's very nice.16:41
jlibosvaalso I split the data network into management and data network16:41
anilvenkatathats great16:42
jlibosvaso there are more changes, I need to talk to tmorin as I know bagpipe consumes fullstack16:42
jlibosvaso I don't break their work :)16:42
anilvenkatajlibosva++16:42
ihrachyscool. I love the way we make progress.16:43
ihrachysI assume there is nothing else of interest in grafana16:43
ihrachys#topic Other patches16:43
*** openstack changes topic to "Other patches (Meeting topic: neutron_ci)"16:43
ihrachysI noticed there was a wishlist bug for fullstack asking to kill processes more gracefully (not sigkill but sigterm)16:44
ihrachysI pushed https://review.openstack.org/#/c/499803/ to test whether a mere switch will do16:44
ihrachysso far there is a single run only and it seems successful (as much as fullstack run can be right now)16:45
ihrachysI will monitor and recheck it for a while. I should have some more stats the next time we meet.16:45
ihrachysalso, the fix for functional job with new iptables from RHEL 7.4 can be found here: https://review.openstack.org/#/c/495974/16:46
ihrachysjlibosva already +2d, maybe haleyb can have a look.16:46
*** coolsvap has quit IRC16:46
*** iyamahat has joined #openstack-meeting16:46
haleybi will look16:46
ihrachysany more patches we may need to be aware of?16:47
*** dtrainor_ has quit IRC16:48
ihrachysI guess no16:48
*** toscalix has quit IRC16:48
*** yamahata has joined #openstack-meeting16:49
ihrachys#topic Open discussion16:49
*** openstack changes topic to "Open discussion (Meeting topic: neutron_ci)"16:49
ihrachyswe will have PTG next week16:49
ihrachysso we will cancel the next meeting16:49
ihrachyswe will meet two weeks from now16:49
*** Apoorva has quit IRC16:49
ihrachysanything else to discuss?16:49
jlibosvanot from me16:49
haleybnothing here16:49
*** Apoorva has joined #openstack-meeting16:50
ihrachysok, good, we'll wrap up. keep up the good work.16:50
ihrachysand haleyb, all eyes are on l3 team ;)16:50
ihrachyscheers16:50
jlibosvalol16:50
ihrachys#endmeeting16:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:50
openstackMeeting ended Tue Sep  5 16:50:32 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-09-05-16.00.html16:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-09-05-16.00.txt16:50
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-09-05-16.00.log.html16:50
jlibosvathanks, bye16:50
*** jlibosva has quit IRC16:50
*** Apoorva has quit IRC16:54
*** abalutoiu has joined #openstack-meeting16:57
*** david-lyle has quit IRC16:59
*** erlon has joined #openstack-meeting17:01
*** ralonsoh has quit IRC17:02
*** dtrainor_ has joined #openstack-meeting17:03
*** lpetrut_ has quit IRC17:03
*** eharney_ has joined #openstack-meeting17:04
*** eharney has quit IRC17:05
*** eharney_ is now known as eharney17:05
*** dtrainor_ has quit IRC17:07
*** dtrainor_ has joined #openstack-meeting17:08
*** harlowja has joined #openstack-meeting17:08
*** Apoorva has joined #openstack-meeting17:09
*** bobmel has quit IRC17:11
*** aagate has joined #openstack-meeting17:11
*** aagate has left #openstack-meeting17:12
*** david-lyle has joined #openstack-meeting17:14
*** Manuel_112 has joined #openstack-meeting17:14
*** Manuel_112 has quit IRC17:18
*** dtrainor_ has quit IRC17:20
*** sambetts is now known as sambetts|afk17:22
*** Manuel_112 has joined #openstack-meeting17:23
*** tesseract has quit IRC17:25
*** rcernin has quit IRC17:25
*** numans has quit IRC17:25
*** ijw has joined #openstack-meeting17:27
*** Manuel_112 has quit IRC17:27
*** numans has joined #openstack-meeting17:28
*** david-lyle has quit IRC17:30
*** iyamahat has quit IRC17:32
*** gouthamr has quit IRC17:32
*** oidgar has quit IRC17:34
*** iyamahat has joined #openstack-meeting17:34
*** cloudrancher has quit IRC17:36
*** cloudrancher has joined #openstack-meeting17:37
*** annegentle has joined #openstack-meeting17:37
*** ricolin has quit IRC17:38
*** dmsimard|afk is now known as dmsimard17:38
*** armax has joined #openstack-meeting17:40
*** david-lyle has joined #openstack-meeting17:46
*** jhearns has joined #openstack-meeting17:50
*** jhearns has quit IRC17:50
*** jhearns has joined #openstack-meeting17:51
*** gagehugo has joined #openstack-meeting17:55
*** numans has quit IRC17:56
*** numans has joined #openstack-meeting17:58
*** VW_ has joined #openstack-meeting17:59
*** gouthamr has joined #openstack-meeting17:59
lbragstad#startmeeting keystone18:00
openstackMeeting started Tue Sep  5 18:00:03 2017 UTC and is due to finish in 60 minutes.  The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
lbragstadayoung, breton, cmurphy, dstanek, edmondsw, gagehugo, henrynash, hrybacki, knikolla, lamt, lbragstad, lwanderley, notmorgan, rderose, rodrigods, samueldmq, spilla, aselius, dpar18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: keystone)"18:00
openstackThe meeting name has been set to 'keystone'18:00
hrybackio/18:00
lbragstad#link https://etherpad.openstack.org/p/keystone-weekly-meeting18:00
knikollao/18:00
lbragstadagenda ^18:00
lbragstado/18:00
gagehugoo/18:00
lamto/18:00
edmondswo/18:00
*** baoli has quit IRC18:00
cmurphyo/18:00
*** rderose has joined #openstack-meeting18:00
*** VW_ has quit IRC18:00
*** VW_ has joined #openstack-meeting18:01
*** baoli has joined #openstack-meeting18:01
lbragstad#topic announcements: ptg planning18:01
*** openstack changes topic to "announcements: ptg planning (Meeting topic: keystone)"18:01
lbragstad#link https://etherpad.openstack.org/p/keystone-queens-ptg18:01
lbragstadPTG is next week already, so the schedule is pretty much set at this point18:01
lbragstadi haven't heard of many conflicts18:01
lbragstadwith out proposed sessions anyway18:02
*** VW has quit IRC18:02
lbragstadi'm also still waiting on room information18:02
lbragstadbut i'll up that as soon as possible18:02
hrybackilbragstad: my only issue is I won't be there Monday until ~noon18:02
hrybackiassuming no plane issues. Irma may decide to alter those plans18:02
lbragstadhrybacki: ack18:02
*** Apoorva_ has joined #openstack-meeting18:03
kmallocyeah18:03
kmallocmeeting time or something o/18:03
lbragstadthe etherpads for specific sessions should be good to go18:03
*** unicell has joined #openstack-meeting18:03
edmondswraildo when is your oslo secret protection session going to be?18:03
lbragstadlet me know if you see information missing18:03
lbragstadotherwise - they should be used to prepare for sessions18:04
gagehugoedmondsw https://etherpad.openstack.org/p/oslo-ptg-queens18:04
raildoedmondsw, it will be on Monday in the oslo room, at 1:30-2:10pm18:04
edmondswso that's gonna conflict a bit, at least for me18:05
raildoedmondsw, and we are gonna to have other session, related to the tripleo/k8s discussion about it, after that session in the tripleo room18:05
raildoedmondsw, damn =/18:05
edmondswyou and I should talk sometime before that meeting... IBM has already written code you might use18:06
lbragstadedmondsw: is there anything the keystone schedule can do to mitigate it?18:06
*** Apoorva has quit IRC18:06
edmondswI'm trying to pull together more info on that for you18:06
edmondswlbragstad probably not, because in this case the conflict is us meeting with the VM and Baremetal guys, so it's really their schedule18:06
kmalloci might make it to the 2nd half of monday18:06
raildoedmondsw, I intend to be in the Keystone policy in code session, before that meeting18:06
kmalloci def. am going to miss-policy-in-code18:07
*** numans has quit IRC18:07
kmalloci wont be arriving until around noon on monday18:07
kmallociirc18:07
lbragstadedmondsw: ack - is there a set schedule for that group/sig somewhere?18:07
lbragstadedmondsw: i've just kinda lumped our related topics into a big block to bring to them18:07
edmondswlbragstad I was just looking at what you had put in https://etherpad.openstack.org/p/keystone-queens-ptg18:07
lbragstadand hoping we can discuss them18:07
lbragstadok18:07
lbragstadso - we're on the same page18:07
lbragstadi've reached out to the baremetal/vm sig a couple times but i haven't seen an actual schedule18:08
lbragstad(which kinda makes it tough to schedule the rest of things)18:08
*** ayoung has joined #openstack-meeting18:08
* lbragstad has the feeling he's going to be chasing people down monday and tuesday18:08
edmondswlbragstad if we could firm that up in a way that doesn't conflict with the oslo discussion, that would be great18:08
lbragstadedmondsw: i'll see if i can reach out to johnthetubaguy again18:09
lbragstadi'd be happy to help them schedule it18:09
lbragstadbut i don't know if someone else has already started doing that18:09
lbragstad#action lbragstad to reach out to baremetal/vm sig about firming up their schedule18:10
lbragstadanyone have anything for PTG stuff?18:10
lbragstadmostly just wanted to advertise it18:10
lbragstadwith the etherpads for pre-session reading18:10
lbragstadalrighty - moving on18:11
edmondswyou're giving us homework? ;)18:11
lbragstad#topic project tags character limit18:11
*** openstack changes topic to "project tags character limit (Meeting topic: keystone)"18:11
lbragstadedmondsw: you know it18:11
lbragstadit wouldn't be the PTG without it ;)18:11
edmondswtru dat18:11
lbragstadgagehugo: o/18:11
gagehugoamrith18:11
* kmalloc has an easy answer here....18:12
* kmalloc waits to hear more though18:12
* edmondsw thinks he knows kmalloc's answer...18:12
gagehugoI'd like to avoid having it configurable18:12
kmalloc++18:12
lbragstadme too18:12
amrithhello18:12
kmallocdo not make it configurable18:12
kmalloci would -2 configurable, ftr18:12
gagehugoamrith project tags character limit?18:12
lbragstadamrith: o/18:12
amrithyes18:12
amrithhi lance18:12
lbragstadamrith: you have a use case for a higher limit of tags, right?18:13
amrithkmalloc doesn't want to make it configurable. oK then make the limit large18:13
amrithyes, the idea is to have a hierarchy of tags18:13
kmalloceach tag is stored as a row in the db?18:13
lbragstadkmalloc: yes18:13
kmallocwith a project->many tag relationsiop?18:13
amrithand for that a longer name would be required18:13
kmallocthen 255 varchar is the max i support18:13
lbragstadkmalloc: yeah - it'a many-to-many relationship18:14
kmalloci don't mind if you're anywhere under or equal to 25518:14
kmallocfor the tag name.18:14
gagehugoi'm fine with that18:14
amrithMorgan, I think 255 would be OK to start with; is the db field capped at 255?18:14
lbragstadamrith: so is the concern the *number* of tags or the lenght of a tag?18:14
edmondswhow many levels of hierarchy are we talking here?18:14
amrithkmalloc is Morgan, yes?18:14
kmallocfor DB reasons in MySQL it is18:14
kmallocyeah.18:14
kmallocdon't exceed 255 unless it's really needed... and then we talk about indexes and indexing text fields18:15
kmallocand blobs18:15
amrithedmondsw no idea. 2 or 3 at most, I think18:15
amrith255 sounds fine18:15
kmallocin short, 255 is fine.18:15
amritheven at 5 levels, 255 allows for 50 character names18:15
kmallocamrith: in the db it shouldn't matter18:15
kmallocbecause you're many tags to one project18:16
amrithyes, can we make the default (in code) larger18:16
kmallocyou should store it a relational forms18:16
edmondswI was gonna say we could possibly set a lower limit on tag length, and then support up to 255 for something like "tag:tag:tag"18:16
*** cschwede_ has quit IRC18:16
amrithI assumed we'd have tag.tag.tag.tag.tag18:16
amrithsince the format is tag, value18:16
amrithor tag.tag.tag.tag, value18:16
edmondswsure, I don't care what the delimiter is18:17
* kmalloc would push this to more relational.18:17
amrithas the case may be18:17
amrithkmalloc I agree18:17
kmallocand not tied to text string concat18:17
*** Manuel_112 has joined #openstack-meeting18:17
amrithfine by me, happy if we want to make it relational18:17
kmallocit solves the issue18:17
amrithbut may be overkill18:17
kmallocbut i wont argue too much for /against18:18
amrithkmalloc ditto18:18
edmondswkmalloc assign a UUID per tag, and then each tag can be associated with a parent?18:18
kmallocjust as long as the column(s) in the db are 255 varchar18:18
amrithI won't argue too much against/for :)18:18
kmallocmake sure PKs are auto-inc int18:18
amrithkmalloc +118:18
kmallocand you can use a uuid if you need externally referenceable18:18
kmalloc(just not as PK)18:18
amrithand so long as a user doesn't have to change code to get the whole 25518:18
amrithasking them to change a config is fine, change code is not18:18
kmallocplease do not make this configurable18:19
kmallocat all18:19
gagehugokmalloc I won't heh18:19
lbragstadi'm not seeing how we could actually18:19
amrithfine, let's remove it from the config in that case18:19
lbragstadwe're talking about the length of an attribute in the database18:19
amrithsorry from that file (whatever it was)18:19
lbragstadwhich is defined by schema, right?18:19
gagehugoyeah18:19
kmallocanyway, my requirements are: primary-key is autoinc-int, varchar fields cannot be > 255 (and these need indexes so, please use varchar for the string data)18:20
lbragstadi thought this specific concern was around the actual *number* of tags that could be associated to a project18:20
kmallocif it's relational data18:20
amrithlbragstad there were two18:20
amrithone was to make the overall length greater18:20
kmallocit doesn't matter, unless you want to just say 50 tags. or some such18:20
lbragstadok - i missed the second one then18:20
kmallocmake it high but reasonable18:20
kmallocdon't make it a config option :)18:20
amrithand when I was told that it could be changed, I asked for configurable, and also that max tags be configurable18:20
kmallocstart with it not configurable18:21
kmallocand a high/reasonable max18:21
lbragstadand reasonably right18:21
kmallocif you set one18:21
lbragstadhigh*18:21
gagehugoso 80 -> 25518:21
lbragstadgagehugo: for which one, the database column length or the number of tags a project can have?18:21
* kmalloc has to re-read the state of the code18:21
gagehugolbragstad column length18:22
*** Manuel_112 has quit IRC18:22
kmallocbut it sounds like it is all as i imagine18:22
lbragstadok - sounds like we all agree that the column length should be 255 characters18:22
lbragstaddo we all agree that the number of tags a project should have is 80 and non-configurable?18:23
gagehugolbragstad it's currently 50 tags per project18:23
gagehugowe can up that to 80, idc18:24
lbragstadamrith: does 50 work for you?18:24
amrithlbragstad i think it is more than enough for me18:24
*** pvaneck has joined #openstack-meeting18:24
ayoungPLease make it relational18:24
lbragstadgagehugo: cool - wanna go to 80 so that we're consistent with what nova does?18:24
ayoungand go to 25518:25
gagehugook18:25
ayoungwhy would you limit the number of tags a project can have?18:25
*** Manuel_112 has joined #openstack-meeting18:25
lbragstad#agreed project tag length needs to be increased to 255 characters and be relational18:25
kmallocayoung: to prevent some malicious "add a billion tags to slow things down"18:26
lbragstad#agreed set the number of tags a project can have to 80 to be consistent with nova18:26
ayoungwho owns the tags?18:26
ayoungif I create a tag, do I own it?18:26
gagehugotags is just an attribute of project18:26
ayoungcan only I set it on a project?18:26
kmallocayoung: mostly it's a "set something reasonable and high" where if someonone hits the limit... they did something crazy. set it at 100 or 200, just not "unlimited"18:26
lbragstadcurrently - admins can tag projects18:26
ayounggagehugo, watch out for the word "just"18:26
lbragstadby modifying the project itself18:27
kmallocRBAC "folks may tag projects, RBAC", admin is default18:27
*** numans has joined #openstack-meeting18:27
ayounglbragstad, admins?  We're in 968696 territory with that term...but18:27
kmalloclike i said, be defensive, but not insane18:27
kmallocset the limit at 200 or even 10018:27
*** VW_ has quit IRC18:27
kmallocif we have complaints that is too low, we can adjust18:27
ayoungtags need to be treated as full entities, not just strings in a string table18:27
gagehugoayoung why's that?18:28
ayounggagehugo, IFF they are going to have any non-trivial usage18:28
ayounglets say I have a tag "non-billable"18:28
ayoungnow, it might be find to have a tag table like kmalloc suggests18:29
ayoungbut then you are going to have a shared resource18:29
ayoungi.e.  if I delete a tag, is it garbage collected?18:29
ayoungetc18:29
ayoungjust need to think through the proposal18:29
ayoungis "Admin" and "admin" going to map to the same tag?18:30
ayoungAre we going to make Tags URL safe?18:30
gagehugono, they are case-sensitive18:30
ayoungare they going to allow spaces?18:30
gagehugoyes18:30
*** Manuel_112 has quit IRC18:30
ayoungfull utf-8?18:30
kmallocayoung: yeah should be.18:30
gagehugoyes18:30
gagehugoonly characters not allowed are "," and "/"18:31
gagehugoas per https://specs.openstack.org/openstack/api-wg/guidelines/tags.html18:31
ayoungOK.  Go for it.  Just please provide electric shock therapy for anyone that wants to use them for any security purpose, to include billing18:31
raildolol18:32
gagehugoheh18:32
lbragstad#action gagehugo to implement electric shock therapy in keystone18:32
lbragstadanything else on tags?18:32
lbragstad#topic open discussion18:33
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:33
ayoungWe've got more people beating us up over Read Only Roles18:33
ayoungthats all18:34
lbragstadack - we have nearly an entire day dedicated to it at the ptg18:34
ayoungCool.  The Part of Adam Young will be played by hrybacki18:35
ayoungthey upgraded the actor18:35
lbragstad;)18:36
hrybackihe's not as handsome as the last however18:36
ayounghe played much better infront of the studio audience18:36
* ayoung was an Infantryman18:36
* ayoung ugly18:36
lbragstadis he allowed mic privileges?18:36
ayounglbragstad, he was a Commo SGT in the Army.  He can fix the mike.18:37
hrybackilol18:37
lbragstadperfect18:37
lbragstadalright - unless we have other things to discuss it looks like we can get some time back18:37
knikolla\o/18:38
lbragstadthanks all!18:38
lbragstad#endmeeting18:38
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:38
openstackMeeting ended Tue Sep  5 18:38:21 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-09-05-18.00.html18:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-09-05-18.00.txt18:38
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-09-05-18.00.log.html18:38
*** ijw has quit IRC18:41
*** sridharg has quit IRC18:42
*** gagehugo has left #openstack-meeting18:43
*** ijw has joined #openstack-meeting18:46
*** Apoorva_ has quit IRC18:47
*** Apoorva has joined #openstack-meeting18:47
*** tinwood has quit IRC18:48
*** pcaruana has quit IRC18:49
*** tinwood has joined #openstack-meeting18:49
*** ociuhandu has joined #openstack-meeting18:54
*** ijw has quit IRC18:58
*** thorst_afk has quit IRC18:59
clarkbhello infra team. Ready for the meeting?18:59
cmurphyo/18:59
*** thorst_afk has joined #openstack-meeting18:59
*** dtroyer has quit IRC19:00
jeblairo/19:00
*** rockyg has joined #openstack-meeting19:00
clarkbI expect we'll have a bit of stuff to talk about today so let us go ahead and get started19:00
*** dtroyer has joined #openstack-meeting19:01
clarkb#startmeeting infra19:01
openstackMeeting started Tue Sep  5 19:01:10 2017 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
pabelangero/19:01
ianwo/19:01
fungii guess it's that time again19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
*** lin_yang has quit IRC19:01
clarkb#info The PTG is next week19:02
clarkb#link https://etherpad.openstack.org/p/infra-ptg-queens19:02
clarkb#link https://ttx.re/queens-ptg.html for general PTG info on what to expect19:02
mordredclarkb: I don't believe in PTGs19:02
*** VW has joined #openstack-meeting19:02
clarkbmordred: good news! it is happening either way :)19:03
*** VW has quit IRC19:03
fungithe tooth fairy will be there19:03
clarkbAlso, I compeltely failed at signing our new Queens release key so will remind everyone about that agin now19:03
clarkb#info Queens Cycle signing key ready for attestation19:03
clarkb#link https://sks-keyservers.net/pks/lookup?op=vindex&search=0x4c8b8b5a694f612544b3b4bac52f01a3fbdb9949&fingerprint=on Queens Cycle signing key19:03
*** VW has joined #openstack-meeting19:03
clarkb#link http://docs.openstack.org/infra/system-config/signing.html#attestation attestation process19:03
fungithanks!19:03
fungii mentioned it to the release team in their meeting last week as well19:03
clarkbif you are an infra-root and haven't done that yet, please do that soon as fungi wants to swap keys out after the trailing cycle releases happen19:04
*** ociuhandu_ has joined #openstack-meeting19:04
*** yangyapeng has quit IRC19:04
fungiyeah, basically immediately post-ptg19:04
fungior as soon as i sober up ;)19:04
*** thorst_afk has quit IRC19:04
fungi(just kidding, we have a gerrit maintenance as soon as i get home!)19:04
*** Shrews has joined #openstack-meeting19:04
clarkb#topic Actions from last meeting19:04
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:04
*** ociuhandu has quit IRC19:05
clarkbfungi: I am expecting we still don't have switchport counts? not suprising considering Houston has bigger problems to worry about now19:05
fungii think we can drop that from the perpetual action items and discuss at the ptg how we want to go forward19:05
clarkbfungi: ok that wfm19:05
clarkb#action ianw upgrade mirror-update server and bandersnatch19:06
fungiit don't suppose it's really doing much good to bring it up every meeting19:06
ianwstill pending, didn't want to touch before release19:06
clarkbianw: ^ I expect that can actually happen nowish since most of the release stuff is done tomorrow/thursday19:06
clarkbianw: yup np. I just don't want to forget it and I think we are finally to a point where it is mostly safe to do19:06
ianwyep, will look into19:06
clarkb#action clarkb update infracloud docs to include ssl setup info19:07
clarkbI still need to write ^ that change but am hoping to do that today before the details escape me19:07
clarkb#topic Specs approval19:07
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:07
*** VW has quit IRC19:07
clarkb#link https://review.openstack.org/#/c/492287/19:07
clarkbThis is a cleanup change and all of the dependencies are compelte for it now. Can we open that to voting for those interested in Gerrit and teh Gerrit upgrade? I'll look at getting it in on Thurdsay assuming there aren't items that need addressing19:08
clarkbThat was really the only spec I saw that was ready. Please let me know if I missed any19:09
clarkb#topic Priority Efforts19:09
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:09
fungii'm good with opening that for council vote (thought you had done that last week actually)19:09
clarkb#undo19:10
openstackRemoving item from minutes: #topic Priority Efforts19:10
clarkbfungi: I don't think the dependent changes had merged by the time I looked at the specs again on thursday? I did approve the ssh keys for zuulv3 spec though19:10
clarkb#topic Priority Efforts19:10
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:10
*** thorst_afk has joined #openstack-meeting19:11
clarkbok really quickly before getting into zuulv3. Just wanted to remind everyone that Gerrit upgrade to 2.13 is happening Monday after the PTG19:11
clarkb#link https://etherpad.openstack.org/p/gerrit-2.13.-upgrade-steps19:11
clarkbreviewing ^ would be great if you have time (ha)19:11
clarkb#topic Zuulv319:12
*** openstack changes topic to "Zuulv3 (Meeting topic: infra)"19:12
jeblairhi!  it's less than 1 week before our planned cutover to zuulv319:12
* clarkb hands meeting baton to jeblair19:12
jeblairhere's the list of outstanding items we've been working from: https://etherpad.openstack.org/p/zuulv3-pre-ptg19:12
jeblairgoing down that list...19:13
clarkb#link https://etherpad.openstack.org/p/zuulv3-pre-ptg19:13
jeblairi've been working on the devstack jobs, and i think the devstack-legacy job, which is the job that we'll base the automatically converted devstack jobs on is about ready19:13
jeblairwell, it is ready19:13
fungilgtm19:13
jeblairit's probably going to need slight revision in order to plug into what the migration script outputs19:14
jeblairbut it demonstrates all the mechanical things it needs to do19:14
jeblairit's also actually really close to a framework we can use for *most* automatically converted jobs19:14
jeblairat any rate, i think the next step for that is now waiting on the migration script19:15
jeblairso i'll move part of that to the done section19:15
jeblairthe other part of the devstack work is the zuulv3 native devstack job19:15
*** priteau has quit IRC19:15
*** thorst_afk has quit IRC19:15
jeblairwe're making progress on that -- it's actually really cool to look at -- you can see how things are shaping up for reuse in zuulv3 and how devstack jobs can be understood by mere humans19:16
mordredspeaking of migration script, I'm shifting my attention to migration script today19:16
jeblairthat's here: https://review.openstack.org/50020219:16
mordredjeblair: ++ it's super cool19:16
jeblairmordred: ya, let's talk about migration script in just a min19:16
clarkb#link https://review.openstack.org/#/c/500202/ devstack zuulv3 native job19:17
jeblairre the devstack job -- unfortunately, we've run into an issue possibly related to zuul_console or zuul_stream where we stop getting output after devstack runs wget19:17
Shrewsweird19:17
mordredyah. it's ...19:17
jeblairdigging into that is now at the top of my list (except that some emergency things jumped ahead of it this morning)19:17
mordredone of the weirdest things ever19:17
jeblairso hopefully i'll start looking at it in earnest this afternoon19:18
fungidoes sound very bizarre19:18
*** raildo has quit IRC19:18
jeblairi'm considering it a blocker for 2 reasons -- i still think we need the native devstack job in place before the migration so we actually have something to show and something for folks to build off of19:18
jeblair(otherwise, chaos and anger ensues)19:18
mordredyup19:18
jeblairand also, it may represent a general problem that may appear in other contexts19:18
fungiwell, and people continue to cargo-cult old cruft19:19
jeblair(though i rank that a little unlikely because devstack surpasses everything else with what it does with file handle redirection :)19:19
clarkbdoes it cause the jobs to fail too? or is it just breaking the UI?19:19
mordredyah - the second thing is the most troubling, because it's a very confusing thing to occur that makes no sense19:19
jeblairclarkb: it causes the job to hang19:19
*** VW has joined #openstack-meeting19:19
clarkbgotcha so not something we could attempt to live with if we wanted to19:19
mordredalthough it does get FURTHER than the wget before it hangs19:20
mordredyah19:20
*** Manuel_112 has joined #openstack-meeting19:20
jeblair(ansible proceeds somewhat (unsure how far, for obvious reasons) past the point it stops logging)19:20
mordredit's worth noting that it's not just the remote log streaming that hangs ...19:20
pabelangercould we switch to curl --silent?19:20
fungiwonder if wget security mechanisms are getting overzealous closing extra file descriptors or something19:20
mordredthe local writing of content to the files in /tmp also stops19:20
jeblairpabelanger: if our ci system can't run wget we must hide our faces in paper bags19:20
*** TxGirlGeek has joined #openstack-meeting19:20
fungii have some paper bags19:21
pabelangerjeblair: agree19:21
mordredyah. I would consider not being able to run wget a showstopper - largely becaue whatever breaks wget is gonna break somethign else too19:21
fungicompletely agree19:21
jeblairanyway, i'll start in on that soon and keep folks updated on it19:21
jeblairnext thing on the list is jobs that use special slaves19:21
*** slaweq_ has joined #openstack-meeting19:21
jeblair#link jobs that use special slaves https://etherpad.openstack.org/p/zuulv3-special-jobs19:21
jeblairmordred: ^19:21
mordredso, they don't work (for obvious reasons) but if folks want to see POC jobs using the new devsack base job: https://review.openstack.org/#/c/500365/ is a rewrite of all of shade's dsvm jobs using the new base job19:21
jeblairmordred: (cool thanks!  good to exercise the new api)19:22
mordredI have the majority of these done, including a spectacular stack related to wheel mirrors that you shoudl all enjoy and also run away from screaming19:22
clarkb#link https://etherpad.openstack.org/p/zuulv3-special-jobs subset of zuulv3 cutover prep work, specifically for jobs that run on special nodes19:22
jeblairmordred: that last one means we drop the special builders, right?19:23
mordredyup!19:23
jeblairsweet19:23
pabelangeryay19:23
jeblairmordred: what's still tbd?19:23
mordredthere's still a few hangers on - pabelanger was just asking about next things to work on, so I think I may hand-off the last of that to him while I shit to migration script19:23
* jeblair giggles19:23
*** Manuel_112 has quit IRC19:24
mordredjeblair: I'll update the etherpad after the meeting with a short-list of review links / todo19:24
mordredoh - also - I have two other changes related to not-migration it's worth mentioning19:24
jeblairmordred, pabelanger: thanks!19:24
*** dtrainor has joined #openstack-meeting19:24
mordredthat I need some folks to review19:25
pabelangerexciting19:25
mordredhttps://review.openstack.org/#/c/500320 and https://review.openstack.org/#/c/48971919:25
jeblairoh yeah, if we find time for those, that will be really nice19:25
mordredhttps://review.openstack.org/#/c/500320 is a must-have - or a different impl is - it's a thing we missed in our original tox job - which is upper-constraints handling19:25
jeblairit may actually end up being somewhat migration related, once we start thinking about things like neutron plugin unit tests19:26
mordredlike, we cannot go live without eitherhttps://review.openstack.org/#/c/500320 or an alternate19:26
clarkb#link https://review.openstack.org/#/c/500320 constraints handling in tox jobs19:26
mordredthe thing I want to discuss about it explicitly19:26
mordredis the approach taken of adding openstack/requirements to the required-projects list of the base job19:26
jeblairhrm19:27
*** thorst has joined #openstack-meeting19:27
jeblairwhy can't it be in the base unittest job + base devstack job?19:27
mordredcurrently every job in v2 that runs tox is cloning openstack/requirements itself in the job, so I don't think doing that is any MORE burdensome than the current thing, but it feels weird19:27
mordredjeblair: because unittest is in zuul-jobs19:27
jeblairmordred: it feels like maybe the right thing to do is make openstack-unittest then19:27
mordredand I'll consider it a crying shame if openstack cannot use the tox-py27 job19:27
pabelangertox-py35-constraints has it I think19:28
mordredi'd like to explore every possibility available before we do that19:28
clarkbmordred: one thing to consider is we don't need the entire repo, we just need the single file (not sure if that makes anything easier though)19:28
mordredclarkb: well - we also honestly need to be able to do depends-on with upper-constraints values too19:28
mordredjeblair: can we make a unittest job in project-config that shadows the one in zuul-jobs?19:29
jeblairpabelanger: are you saying tox-py35-constraints is a child job of tox-py35, and tox-py35-constraints has openstack/requirements?19:29
clarkbmordred: ya so some repo manipulation needs to happen19:29
fungican the base tox job archetype grow a mechanism to add -c /some/path/constranits.txt if a file exists at that location, and then all we have to do is add some task to drop the right content there?19:29
mordredyes. tox-py35-constraints is what https://review.openstack.org/#/c/500320 is aiming to remove the need for19:29
mordredfungi: right -so that's what's in that patch19:29
pabelangerjeblair: yes to both19:29
fungithough i guess the set problem means that adding that task still leaves us with a subclass of the tox jobs19:29
jeblairmordred: oh, why do we want to remove it?19:29
mordredlet me back up real quick19:30
jeblairmordred: (or we could take this as something to hash out in #zuul after meeting)19:30
mordredfirst - what the patch does is adds logic to the tox role to look for an upper-constraints file, if given, and if so it will set the environment variable UPPER_CONSTRAINTS_FILE19:30
mordredall of the openstack tox jobs that need/understand UC files respond to that env var19:31
mordredso that part of the logic allows the tox job itself to be used by people who care or don't care about upper-constraints files and for both groups it'll DTRT19:31
mordredthe second part of the equation is getting a file on disk and telling the tox job to look for it19:31
jeblairmordred: i think that part is fine; the thing that rubs me the wrong way is cloning openstack/requirements everywhere; there are *a lot* of jobs that don't need that19:32
mordredthat is the part where the current patch sets a variable and a required-projects19:32
mordredjeblair: indeed19:32
mordredjeblair: we could perhaps justmake it a project-template19:32
mordredjeblair: that adds the repo to required-projects and also sets the variable19:32
mordredso people can use python-jobs-with-constraints perhaps?19:33
pabelangerI think I must have missed something, I thought tox jobs that needed requirements, we'd just create tox-py35-contraints and tox-py27-constraints in openstack-zuul-jobs, everything else could use tox-py27 from zuul-jobs19:33
jeblairi'd love to see if we can make it a proper job19:33
mordredand then for individual job consumption, people can always set the variable and add the repo if they want19:33
jeblaircan we pause for a minute though?19:33
mordredsure19:33
jeblairi'd like to ask whether we want to continue this conversation here, or just note that this is something we need to work out after the meeting?19:33
mordredsure. we can do that19:34
jeblairwe have 5 items after this in the zuul list alone19:34
clarkbya I think we can sort that out after meeting (this is going to be a full meeting)19:34
mordredI just need people to engage on this topic19:34
jeblairlet's resume this immediately after the meeting in #zuul19:34
mordredkk19:34
jeblairnext up: migration script19:34
mordredwe can also talk about the other patch I mentioned then too19:34
*** slaweq_ has quit IRC19:34
jeblairmordred: you mentioned earlier you're going to start working on this19:35
*** slaweq_ has joined #openstack-meeting19:35
jeblairmordred: is this still at one-person stage, or do you need/want anything from other folks?19:35
mordredyes. I'm shifting attention to that today - I think the other special jobs are far enough along, we can grab stragglers at the end if we need to19:35
jeblairs/start/resume/19:35
mordredI think it's one person for the rest of today19:35
mordredand maybe part of tomorrow19:36
jeblaircool, i reckon you'll let us know when there's more stuff to jump on19:36
jeblairnext up: migration docs19:36
mordredbut at that point I'm expecting it'll be to the point where it can be run locally, someone can find a problem with a migration and add a workaround19:36
jeblair#link infra-manual zuulv3 migration docs https://review.openstack.org/50021819:36
jeblairthat change and its parents remove all of the TODO items from the zuulv3 infra manual page19:37
*** priteau has joined #openstack-meeting19:37
jeblairit would be great if folks can review it, and also read the whole thing and identify gaps19:37
jeblairin some form or other, it at least roughly covers most of the things i would want to communicate to folks making the jjb -> zuul transition19:37
jeblairit's not complete documentation, but it should get us on the same page19:37
jeblairi think once we have the migration script, we may want to add things related to that19:38
Shrewsjeblair: i'll review those today19:38
jeblairlike "the migration script output some stuff that looks like this, here's what you should do"19:38
jeblaircan't write that yet19:38
jeblairwe already talked about zuul_console breakage... so next is docs job incorrectly publishing19:39
jeblairwe published the zuulv3 docs over top of the zuulv2 docs19:39
jeblairi think pabelanger just checked in on this before the meeting, and there's a patch that should fix that19:39
jeblairso hopefully this is mostly taken care of already, just needs a review and some republishing19:39
pabelangeryes19:39
jeblairpabelanger: can you take care of making sure that patch gets merged and appropriate jobs re-run to get the right content back in place (and the new version exercised)?19:40
clarkbI'll review this immediately after the meeting too19:41
clarkb(since I started looking at it just before)19:41
pabelangerjeblair: yes, I'll do that after the meeting19:41
*** e0ne has joined #openstack-meeting19:41
jeblaircool thx19:41
jeblairfinally -- zuul-cloner shim; i sent an email out about this and Shrews started working on it19:41
*** priteau has quit IRC19:41
clarkbidea here is just that if you run zuul-cloner it doesn't break on you to easy migration?19:42
clarkb*ease19:42
jeblairclarkb: also it translates the golang-style paths to zuul-cloner style paths19:42
jeblairsrc/git.o.o/openstack/foo -> openstack/foo19:43
jeblairmaybe even supports clonemap files so jobs that rely on that work as-is19:43
Shrewsworking on the clonemap login now19:43
Shrewslogic*19:43
jeblairShrews: w00t thanks!19:43
clarkbnice19:44
jeblairthat's all the things on the list -- anything missing?19:44
jeblair(blockers for migration/cutover)19:44
mordredoh - I noticed a thing, I should add it to the list ...19:44
pabelangernew servers we need for saturday?19:44
jeblairpabelanger: yes!19:44
pabelangereg: nl02.o.o is online, and we should cut over to it asap19:45
*** dtrainor has quit IRC19:45
*** rockyg has quit IRC19:45
jeblairpabelanger: did you spin down those logstash servers?19:45
pabelangernl01.o.o is trusty19:45
*** ijw has joined #openstack-meeting19:45
mordredI noticed this weekend while working on some base job stuff that our configure-mirrors role does not have parity with the current configure-mirror script19:45
jeblairmordred: nice thanks :)19:45
pabelangerjeblair: I just stopped logstash services first, so if we are okay to stop them, we can do that now19:45
pabelangerlogstash-worker016.o. to logstash-worker20.o.o19:46
mordredI think we can likely make a legacy-openstack-configure-mirrors thing in project-config that does a dumb version of a direct translation19:46
jeblairpabelanger: cool, sounds like you, fungi, and clarkb can probably handle that19:46
clarkbmordred: jeblair fwiw the existing script is written such that you execute the same script hat nodepool exectures to load that data up19:46
clarkbfor mirrors19:46
mordredand make it nicer moving forward19:46
fungiyup19:46
*** dtrainor has joined #openstack-meeting19:46
pabelangerkk19:46
mordredclarkb: yup. I think we need to have legacy-openstack-configure-mirrors do that for now19:46
clarkbpabelanger: ya logstash job queue count looks ok so should be fine to turn those servers off/delete them19:47
mordredclarkb: and then we can circle back and talk about how/if to refactor it to be more 'native' later19:47
pabelangerclarkb: ack19:47
jeblairokay, the next event(s) in our schedule are to do trial cutovers this weekend -- saturday and/or sunday evenings.  obviously that will only happen if these blockers are sufficiently resolved by then.19:48
jeblairmaybe let's discuss details on that friday?19:49
fungisounds great19:49
Shrewswfm19:49
pabelanger++19:49
*** esberglu has quit IRC19:50
jeblairclarkb: eot from me19:50
clarkbok19:50
*** esberglu has joined #openstack-meeting19:50
clarkbthere is also a new thread on the mailing list about Zuul UI things19:50
clarkbI've sent a quick reply but definitely don't have enough background on everything going on in Zuul to say much. Would be nice if someone could respodn to that properly19:51
clarkb#topic PTG team dinner19:51
*** openstack changes topic to "PTG team dinner (Meeting topic: infra)"19:51
jeblairclarkb: will do19:51
clarkbTuesday evening looks like the best night for us because it is when we have the most overlap without conflicts. I have't heard objections yet but basically said lets do Tuesday evening at beer garden19:52
jeblair++19:52
pabelangerMmm, garden beer19:52
clarkbIf this doesnt' work please propose alternatives but as of today that is the plan :)19:52
clarkbOnce in Denver I'll send mail/ping people with details on how we are transporting19:53
clarkb#topic Project renames19:53
*** openstack changes topic to "Project renames (Meeting topic: infra)"19:53
*** cloudrancher has quit IRC19:53
clarkb#link https://review.openstack.org/#/c/50076819:53
clarkbwe have one project rename. I don't expect we'll get to taht this week for obvious reasons, or next19:53
clarkbAssuming gerrit upgrade goes well after PTG maybe we can plan a rename for that week or week after? This is mostly a heads up, but lets not worry about it until later19:54
fungii expected it would happen after the gerrit upgrade19:54
*** cloudrancher has joined #openstack-meeting19:54
fungisounds good19:54
clarkbIn theory we'll be knocking out a couple long standing todo items for infra over the next couple weeks so lets focus on doing that first19:54
*** esberglu has quit IRC19:55
clarkb#topic Open Discussion19:55
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:55
clarkbwoo managed a couple minutes leftover for this19:55
fungi#link https://etherpad.openstack.org/p/GoqkPTucMK infra addition to tc's top 5 help wanted19:55
mordred\o/19:55
fungithe tc has suggested we propose something along those lines to help increase visibility with companies looking for effective ways to get more involved19:55
fungiplease hack that up with whatever edits you think it deserves19:55
*** dtrainor has quit IRC19:56
fungibut i'd like to get it pushed up to gerrit in the next day or two19:56
* clarkb makes note to review that19:56
pabelangerfungi: nice, was just talking to some downstream people about how to get move involved upstream19:56
fungii borrowed a little wording from the summary in system-config doc, though with tweaks and most of that is wholly new prose19:56
*** raildo has joined #openstack-meeting19:57
clarkbdoesn't look like there is much else. Thank you everyone19:59
*** priteau has joined #openstack-meeting19:59
clarkb#endmeeting19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:59
openstackMeeting ended Tue Sep  5 19:59:17 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-09-05-19.01.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-09-05-19.01.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-09-05-19.01.log.html19:59
fungithanks clarkb!19:59
*** jprovazn has quit IRC19:59
fungireminder: no tc meeting this week, but there is an upcoming office hour at 01:00 utc in #openstack-tc19:59
*** yangyapeng has joined #openstack-meeting20:01
*** bastafidli_ has joined #openstack-meeting20:01
*** esberglu has joined #openstack-meeting20:03
*** ijw has quit IRC20:05
*** ijw has joined #openstack-meeting20:05
*** esberglu has quit IRC20:07
*** rossella_s has quit IRC20:08
*** rossella_s has joined #openstack-meeting20:09
*** dtrainor has joined #openstack-meeting20:10
*** Swami_ has joined #openstack-meeting20:13
*** Swami_ has quit IRC20:13
*** efried is now known as efried_bbiab20:15
*** abalutoiu has quit IRC20:15
*** julim_ has quit IRC20:15
*** adrianofr has joined #openstack-meeting20:20
*** Manuel_112 has joined #openstack-meeting20:22
*** hasharAway has quit IRC20:23
*** VW has quit IRC20:23
*** dtrainor has quit IRC20:24
*** ijw has quit IRC20:24
*** ijw has joined #openstack-meeting20:24
*** dtrainor has joined #openstack-meeting20:25
*** jkilpatr_ has quit IRC20:25
*** Manuel_112 has quit IRC20:27
*** e0ne has quit IRC20:30
*** VW has joined #openstack-meeting20:30
*** VW has quit IRC20:30
*** VW has joined #openstack-meeting20:31
*** Manuel_112 has joined #openstack-meeting20:31
*** cloudrancher has quit IRC20:32
*** cloudrancher has joined #openstack-meeting20:32
*** marst has quit IRC20:33
*** rossella_s has quit IRC20:34
*** Manuel_112 has quit IRC20:36
*** rderose has quit IRC20:36
*** artom has quit IRC20:36
*** rderose has joined #openstack-meeting20:36
*** edmondsw has quit IRC20:36
*** edmondsw has joined #openstack-meeting20:37
*** rossella_s has joined #openstack-meeting20:37
*** jkilpatr has joined #openstack-meeting20:41
*** edmondsw has quit IRC20:42
*** cleong has quit IRC20:42
*** ansmith has quit IRC20:43
*** rcernin has joined #openstack-meeting20:44
*** dtrainor has quit IRC20:44
*** pchavva has quit IRC20:45
*** dtrainor has joined #openstack-meeting20:46
*** rossella_s has quit IRC20:46
*** rossella_s has joined #openstack-meeting20:48
*** efried_bbiab is now known as efried20:52
*** rossella_s has quit IRC20:54
*** rossella_s has joined #openstack-meeting20:54
*** dtrainor has quit IRC20:56
*** oneswig has joined #openstack-meeting20:56
*** dtrainor has joined #openstack-meeting20:56
*** slaweq_ has quit IRC20:57
*** jamesmcarthur has quit IRC20:57
*** slaweq_ has joined #openstack-meeting20:58
*** jamesmcarthur has joined #openstack-meeting20:58
*** martial has joined #openstack-meeting21:00
oneswig#startmeeting scientific-wg21:00
openstackMeeting started Tue Sep  5 21:00:23 2017 UTC and is due to finish in 60 minutes.  The chair is oneswig. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: scientific-wg)"21:00
openstackThe meeting name has been set to 'scientific_wg'21:00
zioprotohello21:00
hogepodgehi21:00
oneswighello and good evening etc.21:00
rbuddenhello21:00
martialHello all21:00
priteauHello!21:00
oneswig#link agenda for today is https://wiki.openstack.org/wiki/Scientific_working_group#IRC_Meeting_September_5th_201721:01
oneswig#chair martial21:01
openstackCurrent chairs: martial oneswig21:01
*** rderose has quit IRC21:01
oneswigQuite a few topics to cover today, lets get rolling21:02
*** markstur has joined #openstack-meeting21:02
oneswig#topic opportunistic capacity on OpenStack21:02
*** openstack changes topic to "opportunistic capacity on OpenStack (Meeting topic: scientific-wg)"21:02
*** Apoorva_ has joined #openstack-meeting21:02
oneswigBlair was particularly interested in this - should we defer until he's joined?21:02
oneswigLets cover item 2 first21:03
*** jamesmcarthur has quit IRC21:03
oneswig#topic private cloud capacity meter21:03
*** openstack changes topic to "private cloud capacity meter (Meeting topic: scientific-wg)"21:03
*** stevebaker has left #openstack-meeting21:03
oneswigOK so this item was triggered by the discussion on metrics for instance availability a few weeks back21:03
*** noslzzp has quit IRC21:04
*** rossella_s has quit IRC21:04
oneswigAs an example of how new API capabilities can be used, John Garbutt put together a demo21:04
*** eharney has quit IRC21:04
oneswigfor measuring cloud available capacity using (some of) the new Nova placement APIs21:05
*** gouthamr has quit IRC21:05
oneswig#link os-capacity tool https://github.com/johngarbutt/os-capacity21:05
oneswigWorks particularly well for bare metal clouds!21:05
zioprotocool, I just went through the README. I guess you need to run it with Admin credentials right ?21:05
oneswigyes, it's an admin tool, unless your users are especially empowered21:06
*** Apoorva has quit IRC21:06
*** b1airo has joined #openstack-meeting21:06
priteauoneswig: Does it require the placement API?21:06
b1airomorning and sorry for tardiness - bit of a morning meltdown happening with #1 here21:06
*** rossella_s has joined #openstack-meeting21:06
oneswigYes but not the new features introduced by pike - we use it on ocata - but one day will improve to use it with the new features introduced in pike21:07
oneswigHi b1airo21:07
oneswig#chair b1airo21:07
openstackCurrent chairs: b1airo martial oneswig21:07
*** noslzzp has joined #openstack-meeting21:07
oneswigjust on os-capacity21:07
martialwelcome blair21:07
oneswigWhat it helps with is the disconnect between (eg) SLURM queues and cloud about how to handle being full.21:08
oneswigcloud says 'no', slurm says 'join the queue'21:08
oneswigAt least now we have an idea of how much resource we can ask for21:08
oneswigOK - just wanted to offer that up - share and enjoy :-)21:09
*** raildo has quit IRC21:09
oneswigBack to the agenda21:09
oneswig#topic opportunistic cloud capacity21:09
*** openstack changes topic to "opportunistic cloud capacity (Meeting topic: scientific-wg)"21:09
oneswigb1airo: take it away21:09
b1airowanted to take a suevey of what people/deployers are doing to address this use-case today21:10
*** raildo has joined #openstack-meeting21:10
b1airowhat opportunistic capacity i mean something slightly different to the usual "on-demand" associated with cloud-computing21:11
b1airomy experience of "on-demand" in the private/community cloud space is that it really means on-demand until the cloud is full, then again for a little while after each upgrade, but generally it becomes hard to launch e.g. larger flavours actually on-demand21:12
*** harlowja has quit IRC21:13
b1airoi'd like to carve out some compute capacity for groups who have burst / speculative use-cases and are happy to be able to launch e.g. one or two 16 core instances for 24 hours with some basic fairness mechanism arbitrating21:13
b1airothe simplest idea today seems to be:21:14
b1airo1) create a separate AZ for it21:14
*** raildo has quit IRC21:14
b1airo2) create a new project for each existing project that wants access (to control quota)21:14
b1airo3) give that new project access to use the AZ21:15
*** ykatabam has joined #openstack-meeting21:15
*** rockyg has joined #openstack-meeting21:15
b1airo4) run watcher and killer scripts that randomly kill stuff older than X hours21:15
oneswigb1airo: would you have it so that there was some kind of kill-to-fill LRU execution when an instance is requested and the AZ is full?21:16
*** edmondsw has joined #openstack-meeting21:16
zioprotob1airo: watcher and killer scripts, are you considering Openstack Mistral ?21:17
*** ijw has quit IRC21:17
b1airothat'd certainly be ideal oneswig , but implementing that is a nightmare i reckon, would be easier to have external scripts just ensure there is always Y capacity free21:17
b1airoand if no instances older than limit then the zone is full21:18
zioprotob1airo: we have a similar use case where we have to make sure instances run by students are killed everynight at midnight. The use case is different, but we have the same concept of killing resources after a while they are running21:18
*** julim has joined #openstack-meeting21:18
*** thorst has quit IRC21:18
oneswigzioproto: do you use mistral for that, as you suggest?21:19
zioprotooneswig: no we dont21:19
b1airodoes sound similar zioproto, i guess that is for a lab setup?21:20
b1airore. mistral, maybe... is it a good fit?21:20
zioprotoyes, we are using ansible based stuff to delete the instances21:20
zioprotojust because we needed to set this up quickly, and we did not have time to learn another tool just for this task21:21
b1airoanyway, i think this general use case is very common and something that OpenStack really needs to address21:22
priteaub1airo: In our team we call "on-availability" the opposite of "on-demand". One of our projects is combining OpenStack for on-demand and Torque for on-availability, where the compute nodes are moved from one to the other depending on usage. We are hoping to publish results at a conference in 2018. This is quite different from your solution and not relying only on OpenStack though.21:22
b1airoe.g. in the Nectar cloud we have an allocations system with 1,3,6,12 month project lengths and an expiry process. but even with 7 zones of 3-4k cores we still run into this problem21:23
*** StefanPaetowJisc has joined #openstack-meeting21:23
oneswigpriteau: does that mean that torque queues up OpenStack API requests that couldn't be satisfied?21:23
StefanPaetowJiscevening folks. Pardon the tardiness21:23
b1airopriteau, "on-availability" - i like it! have not heard that term in this context before21:23
oneswigHi StefanPaetowJisc21:23
rbuddenpriteau: that’s similar to the limited use cases we’ve had for large scale VMs. We’ve traditionally had the nodes placed in a Slurm reservation, then turned into Nova Computes on demand via bash/ansible/etc.21:23
zioprotob1airo: I am reading as we speak the python code my colleague wrote. The project is decorated with an attribute. Reading the attribute we wrote a custom python code that decides if killing or shutting down the instances on the project.21:23
b1airoo/ StefanPaetowJisc21:24
priteauoneswig: no, they're two separate queues with possibly different groups of users. But behind the scenes they're sharing the same cluster.21:24
rbuddenwhich reminds me, i still owe b1airo an email about this ;)21:24
b1airooh hey rbudden o/21:24
oneswigJohn Garbutt asked me to prompt people interested in preemptible instances (which essentially is the user-centric effect of this concept)21:25
priteaub1airo: Not directly related to the above: the Blazar team will be meeting for the Denver PTG next week and will discuss the idea of the "reaper" service that was proposed in Boston21:25
oneswigIf they could review and comment on https://review.openstack.org/#/c/43864021:25
oneswigIf they haven't done so already.  This will inform discussion at the PTG next week.21:25
*** Manuel_112 has joined #openstack-meeting21:25
martialpriteau +121:26
oneswigSo please take a look if you want a spot instance capability on your cloud21:26
zioproto#link WIP: Backlog spec on preemptible servers https://review.openstack.org/#/c/43864021:26
oneswigzioproto: the very same :-)21:26
zioprotooneswig: yes I just formatted it for the MeetBot21:26
oneswigthanks zioproto21:26
oneswigpriteau: how's the gui for blazar?21:27
priteauoneswig: It's upstream!21:27
priteauhttps://git.openstack.org/cgit/openstack/blazar-dashboard/21:28
oneswignice work21:28
b1aironice21:28
*** jamesmcarthur has joined #openstack-meeting21:28
oneswigWe may want this, sooner rather than later, our ska system is getting very busy21:28
oneswigI'll be in touch priteau...21:29
priteauSounds good21:29
*** Manuel_112 has quit IRC21:30
oneswigOK, anything more to add on opportunistic usage?21:31
b1airoi'm interested to know if people think it is ok to have a different system/api to meet this use-case21:31
martialb1airo: I think that is how some people do it, so I would vote yes21:32
b1airoor whether it should be through Nova API and therefore require some API changes to instance creation, i.e., a richer NoValidHost21:32
*** jamesmcarthur has quit IRC21:32
martialI do like the blazar solution21:33
b1airomartial, the implication if that is the case is we as a community should make an effort to ease and demonstrate that integration for newcomers21:33
b1airothere are really not that many combinations to worry about, e.g., Nova+SLURM and Nova+PBS would probably cover ~80%21:34
priteaurbudden: Do you have a writeup of your Slurm/Nova solution somewhere?21:34
*** Manuel_112 has joined #openstack-meeting21:34
*** Manuel_112 has quit IRC21:34
rbuddenpriteau: I owe and email about this to b1airo, I can include you on it if you’d like ;)21:34
priteauYes please!21:35
martialrbudden: can you add me as well?21:35
rbuddenEverything is just getting back to normal after some vacation and our Bridges upgrades21:35
rbuddenMartial: sure thing21:35
martialthx21:35
b1airothanks rbudden!21:35
rbuddenI’ll warn you it’s nothing super fancy21:35
oneswigb1airo: On the all-openstack side, I think there are liabilities with queuing to get an instance that nova may be wary of, eg, what if I was delayed in creating an instance and then found the resources upon which I depended were gone21:35
zioprotoI dont know if it is related but I did some testing in running 1000 VMs in a single 'openstack server create' command21:35
rbuddenlargely utilizing Availability Zones and metadata tagging of hypervisors and Nova flavors21:35
*** adrianofr has quit IRC21:36
zioprotothe idea is to be able to run that big about of VMs but for a short time21:36
rockygrbudden, you should also consider giving it to the folks who publish superuser blog21:36
oneswigHi rockyg!21:36
rbuddenrockyg: sounds interesting, i can check into that unless someone has a direct contact I can use?21:36
rockygHey!  been lurking21:36
oneswigrbudden: there's a whole chapter on this... in the book... hint...21:37
rockygNicole ???21:37
zioprotowhere is a good start to read about PBS+nova, given that I never used PBS ?21:37
rbuddenoneswig: thanks! i have a copy in front of me on the bookshelf, i’ll check it out!21:37
rbuddenzioproto: I just did a simlar test using Nova/Ironic during our upgrade21:37
*** thorst has joined #openstack-meeting21:37
rbuddenI believe only on the order of 500 nodes in a single instantiation21:38
oneswigrbudden: might be a case study for the second edition?21:38
rbuddenyes, i’ll have notes on this for the book update!21:38
*** ansmith has joined #openstack-meeting21:38
rbuddenmoved to local boot across all nodes and was able to test and verify the Nova scheduler bug fix for this that’s mentioned in the first edition of the book21:38
rockygNicole Martinelli, rbudden21:38
rbuddenrockyg: thx21:38
zioprotorbudden: #link https://cloudblog.switch.ch/2017/08/28/starting-1000-instances-on-switchengines/21:39
rbuddencool, i’ll check out the link21:40
martialzioproto: very nice indeed21:40
oneswigzioproto: you should get your blog onto planet.openstack.org, if it isn't already?21:41
rockyg++ to that.21:42
zioproto#action zioproto check if his blog is already on planet openstack21:42
*** thorst has quit IRC21:42
oneswigOK, move on?21:43
oneswig#topic book update21:43
*** openstack changes topic to "book update (Meeting topic: scientific-wg)"21:43
oneswigThe second edition is taking shape nicely.21:43
oneswigThank you to everyone who has contributed their time and input so far.21:43
oneswigWe have some case studies to fill still21:44
oneswig1) Bare metal infrastructure management case study please, to accompany Bridges and Chameleon21:44
oneswig2) Federation examples to be proposed for the new section, led by Enol21:44
hogepodgeI'm here to remind everyone of the deadline.21:45
rbuddenoneswig: as mentioned in my email to you this morning, i’ll be working on the Bridges update this week.21:45
oneswigThanks rbudden, appreciated21:45
rbuddenI was delaying in hopes to have more time to play with some Neutron integration, but other tasks have unfortuantey had me preoccupied21:46
priteauI have done most of the update of the Chameleon case study this morning, will still provide a few more changes later this week21:46
rbuddenI’m attempting a skip level upgrade from Liberty -> Ocata on our second cluster… I doubt I’ll have it complete before the deadline but if I’ll keep everyone appraised21:47
oneswigExcellent.  What of the federators in this time zone?21:48
oneswig(... obviously busy debugging SAML issues...)21:48
hogepodgeDoes the team feel like it's on track to deliver the update in a few weeks?21:50
StefanPaetowJiscSorry, debugging non-SAML stuff here... feverishly trying to get GSSAPI (Moonshot) done for an HPC-SIG meeting next week :-)21:50
StefanPaetowJiscStill haven't looked at the book spec :-(21:50
oneswighogepodge: I think so, many people have been responsive21:50
oneswigGood luck StefanPaetowJisc, keep us updated!21:50
hogepodgeExcellent. Is there anything I need to take back to the Foundation team?21:50
*** cloudrancher has quit IRC21:51
hogepodgeWe're hoping that the book will have an exciting color image, btw. :-D21:51
martialhogepodge: still the plan, we have to discuss a cut off date for review but we are on track21:51
*** cloudrancher has joined #openstack-meeting21:52
oneswighogepodge: nothing comes to mind for the foundation team right now, thanks21:52
martialcolor :)21:52
oneswighogepodge: how will you decide on a cover?21:52
oneswigBTW - one issue - does anyone have Adobe Illustrator?  We can read the .ai files (they are actually PDFs) but not edit them.21:53
hogepodgeoneswig: the previous book used a research image from one of our community members. If you get an image to us, we can get it to our design team to build out the cover21:53
*** rcernin has quit IRC21:53
oneswigInteresting idea... Can the WG members run a poll do you think?  I'm sure you and the team would pick a good one.21:54
StefanPaetowJiscHmmmm21:54
StefanPaetowJiscI have AI somewhere...21:54
StefanPaetowJiscI have AI CS4.21:55
StefanPaetowJiscIf that helps21:55
b1airopretty sure i can get Adobe suite if required21:55
martialsame as b1airo21:55
oneswigStefanPaetowJisc: it could well.  Can I bear that in mind.  Same to you b1airo21:55
b1airohogepodge, i was wondering about that - we might be able to get something from Monash21:56
oneswigI sense a poll ...21:56
oneswigOK, 1 final topic to squeeze in - can we do it?21:56
b1airoi will talk to my colleague who is very good with this sort of stuff and spends hours making slide decks :-)21:56
StefanPaetowJiscOk, oneswig.21:56
oneswig#topic SWG -> SSIG?21:56
*** openstack changes topic to "SWG -> SSIG? (Meeting topic: scientific-wg)"21:56
oneswigb1airo: what's up?  Do we automatically become a SIG?21:57
*** slaweq_ has quit IRC21:57
zioprotoI will try to let you know about this soon21:57
zioprotoshould be a topic in the UC21:57
martialthat is a conversation that was explained to us at the UC forum session in Boston21:58
zioprotowe skipped a meeting because of bank holiday in the US21:58
martialbut it seemed to Blair and I at the time that it seems so21:58
rockygSo, you get to say yea/nay21:58
martialzioproto, you will keep us updated it seems :)21:58
oneswigAre there material changes to be aware of?21:58
rockygI don't know what happens if you don't pick.21:58
rockygTrying to get more devs involved.21:59
*** numans has quit IRC21:59
zioprotoas far as I understood the biggest change is that there will be a big mailing list with all SIGs21:59
StefanPaetowJiscEWWW22:00
zioprotoand you have to write with your SIG in []22:00
zioprotosimilar to openstack-dev mailing list22:00
b1airosorry i walked away to chase someone to pack there schoolbag o_022:00
b1airo*their22:00
b1airo(back to school for me!)22:00
oneswigIt doesn't sound all that different22:00
priteauIsn't that what we already do?22:00
zioprotooneswig: I would not worry too much22:00
oneswigb1airo: it's been that week here, too22:00
rockygYeah.  Hope is one ml will get more response and cross pollination22:00
b1airozioproto, that is my understanding too22:01
priteauLet's skip the SIG and go straight to STIG ;-)22:01
zioproto#link http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs22:01
oneswigis the major difference the expectation of less work and more interest?22:01
b1airoSpecial Technical Interest Group!22:01
oneswigpriteau: too good....22:01
priteaub1airo: exactly!22:01
*** galstrom is now known as galstrom_zzz22:01
b1airooneswig, i think that is one of the subtler expectations yeah22:01
b1airoWGs were probably thought of originally as more autonomous and goal focused22:02
oneswigAh, we are over time.22:02
zioprotogood night !22:02
oneswigBut to conclude, this is not an issue of concern it seems22:02
oneswigbusiness as usual?22:02
oneswigzioproto: thanks for staying up!22:03
b1airowhereas SIGs are a way to get cliques together, and i think the UC would then like to introduce a few more guidelines to get useful and standardised outputs from those groups22:03
*** bobh has quit IRC22:03
rbuddengotta jet, goodbye everyone!22:03
b1airobye all!22:03
zioprotob1airo: ok ! I take this input for the UC :)22:03
StefanPaetowJiscbye rbudden22:03
oneswigthanks everyone22:03
priteaubye everyone22:03
zioprotoguys it is really late here, I have to leave to sleep, ciao :)22:03
oneswig#endmeeting22:04
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:04
openstackMeeting ended Tue Sep  5 22:04:00 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:04
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-09-05-21.00.html22:04
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-09-05-21.00.txt22:04
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-09-05-21.00.log.html22:04
martialI guess we are done :)22:04
rockygttfn!22:04
*** VW_ has joined #openstack-meeting22:05
*** rockyg has quit IRC22:07
StefanPaetowJiscbye all22:07
*** thorst has joined #openstack-meeting22:07
*** oneswig has quit IRC22:08
*** VW has quit IRC22:08
*** VW_ has quit IRC22:10
*** thorst has quit IRC22:10
*** annegentle has quit IRC22:10
*** annegentle has joined #openstack-meeting22:11
*** b1airo has quit IRC22:13
*** ijw has joined #openstack-meeting22:13
*** priteau has quit IRC22:15
*** annegentle has quit IRC22:16
*** StefanPaetowJi-1 has joined #openstack-meeting22:19
*** StefanPaetowJisc has quit IRC22:19
*** StefanPaetowJi-1 is now known as StefanPaetowJisc22:19
*** ijw has quit IRC22:21
*** dtrainor has quit IRC22:21
*** StefanPaetowJisc has quit IRC22:22
*** felipemonteiro_ has quit IRC22:22
*** dtrainor has joined #openstack-meeting22:23
*** sdague has quit IRC22:26
*** lakerzhou2 has joined #openstack-meeting22:26
*** jamesmcarthur has joined #openstack-meeting22:27
*** Manuel_112 has joined #openstack-meeting22:28
*** baoli has quit IRC22:30
*** Manuel_112 has quit IRC22:33
*** martial has quit IRC22:35
*** Manuel_112 has joined #openstack-meeting22:36
*** numans has joined #openstack-meeting22:39
*** Manuel_112 has quit IRC22:41
*** dprince has quit IRC22:42
*** claudiub|2 has quit IRC22:43
*** numans has quit IRC22:44
*** bastafidli_ has quit IRC22:44
*** jamesmcarthur has quit IRC22:45
*** Apoorva_ has quit IRC22:45
*** Apoorva has joined #openstack-meeting22:46
*** edmondsw has quit IRC22:47
*** edmondsw has joined #openstack-meeting22:48
*** jamesmcarthur has joined #openstack-meeting22:49
*** esberglu has joined #openstack-meeting22:50
*** edmondsw has quit IRC22:52
*** jamesmcarthur has quit IRC22:53
*** jamesmcarthur has joined #openstack-meeting22:53
*** jamesmcarthur has quit IRC22:53
*** jamesmcarthur has joined #openstack-meeting22:54
*** esberglu has quit IRC22:55
*** lakerzhou2 has quit IRC22:56
*** jamesmcarthur has quit IRC22:59
*** ayoung has quit IRC23:01
*** efried is now known as efried_zzz23:07
*** pvaneck has quit IRC23:10
*** thorst has joined #openstack-meeting23:11
*** hongbin has quit IRC23:12
*** thorst has quit IRC23:16
*** gouthamr has joined #openstack-meeting23:17
*** TxGirlGeek has quit IRC23:18
*** hongbin has joined #openstack-meeting23:21
*** thorst has joined #openstack-meeting23:21
*** hongbin has quit IRC23:22
*** sshank has joined #openstack-meeting23:24
*** thorst has quit IRC23:25
*** sshank has quit IRC23:28
*** b1airo has joined #openstack-meeting23:30
*** Manuel_112 has joined #openstack-meeting23:30
*** dimak has quit IRC23:32
*** dimak has joined #openstack-meeting23:34
*** Manuel_112 has quit IRC23:35
*** bobh has joined #openstack-meeting23:37
*** Manuel_112 has joined #openstack-meeting23:39
*** dtrainor has quit IRC23:42
*** markvoelker has quit IRC23:43
*** Manuel_112 has quit IRC23:44
*** dtrainor has joined #openstack-meeting23:45
*** b1airo has quit IRC23:47
*** b1airo has joined #openstack-meeting23:50
*** yuanying has quit IRC23:50
*** yuanying has joined #openstack-meeting23:51
*** artom has joined #openstack-meeting23:56
*** bobh has quit IRC23:57
*** cloudrancher has quit IRC23:58
*** bobh has joined #openstack-meeting23:59
*** cloudrancher has joined #openstack-meeting23:59

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