Tuesday, 2017-11-28

*** ijw has quit IRC00:02
*** salv-orlando has quit IRC00:12
*** salv-orlando has joined #openstack-meeting00:13
*** salv-orlando has quit IRC00:17
*** fnaval has quit IRC00:21
*** ijw has joined #openstack-meeting00:30
*** hongbin has quit IRC00:33
*** sshank has quit IRC00:34
*** jkilpatr has quit IRC00:36
*** fnaval has joined #openstack-meeting00:38
*** absubram has joined #openstack-meeting00:43
*** tovin07_ has joined #openstack-meeting00:44
*** jkilpatr has joined #openstack-meeting00:45
*** Kevin_Zheng has joined #openstack-meeting00:46
*** VW has joined #openstack-meeting00:47
*** jkilpatr has quit IRC00:50
*** zhhuabj has quit IRC00:51
*** zhhuabj_ has quit IRC00:52
*** zhhuabj_ has joined #openstack-meeting00:52
*** dklyle has quit IRC00:54
*** david-lyle has joined #openstack-meeting01:01
*** jkilpatr has joined #openstack-meeting01:03
*** zhhuabj has joined #openstack-meeting01:05
*** zhouyaguo has joined #openstack-meeting01:09
*** jkilpatr has quit IRC01:09
*** jaypipes has quit IRC01:10
*** jkilpatr has joined #openstack-meeting01:11
*** zhouyaguo has quit IRC01:12
*** salv-orlando has joined #openstack-meeting01:14
*** yangyapeng has joined #openstack-meeting01:15
*** yangyapeng has quit IRC01:16
*** yangyapeng has joined #openstack-meeting01:16
*** rbudden has quit IRC01:17
*** salv-orlando has quit IRC01:19
*** armax has quit IRC01:27
*** chyka_ has quit IRC01:29
*** VW has quit IRC01:31
*** aeng has quit IRC01:33
*** jkilpatr has quit IRC01:38
*** absubram has quit IRC01:45
*** esberglu has joined #openstack-meeting01:46
*** sdague has quit IRC01:47
*** mriedem has joined #openstack-meeting01:48
*** rbudden has joined #openstack-meeting01:49
*** aeng has joined #openstack-meeting01:49
*** caowei has joined #openstack-meeting01:49
*** esberglu has quit IRC01:50
*** hughhalf has quit IRC01:51
*** hughhalf has joined #openstack-meeting01:53
*** rbudden has quit IRC02:01
*** ianychoi has quit IRC02:03
*** kevzha01 has joined #openstack-meeting02:03
*** kevzha01 is now known as kevinz02:03
*** dmacpher has joined #openstack-meeting02:05
*** aselius has quit IRC02:08
*** VW has joined #openstack-meeting02:12
*** chyka has joined #openstack-meeting02:13
*** salv-orlando has joined #openstack-meeting02:15
*** zhurong has joined #openstack-meeting02:18
*** chyka has quit IRC02:18
*** salv-orlando has quit IRC02:21
*** Apoorva_ has joined #openstack-meeting02:21
*** yamamoto has joined #openstack-meeting02:22
*** Apoorva has quit IRC02:25
*** Apoorva_ has quit IRC02:25
*** hongbin has joined #openstack-meeting02:27
*** gcb has joined #openstack-meeting02:27
*** esberglu has joined #openstack-meeting02:36
*** esberglu has quit IRC02:36
*** esberglu has joined #openstack-meeting02:37
*** erlon has quit IRC02:41
*** esberglu has quit IRC02:41
*** fzdarsky_ has joined #openstack-meeting02:41
*** fzdarsky|afk has quit IRC02:43
*** iyamahat has quit IRC02:53
*** yamahata has quit IRC02:53
*** gyee_ has quit IRC02:55
*** markstur_ has quit IRC02:55
*** ekcs has quit IRC02:58
*** ijw has quit IRC02:59
hongbin#startmeeting zun03:00
openstackMeeting started Tue Nov 28 03:00:10 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-11-28_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
mkraio/03:01
hongbinhi kevinz mkrai03:01
*** ijw has joined #openstack-meeting03:02
mkraihi hongbin kevinz03:02
hongbinit looks it is three of us today, we could have a short update for each other, then end the meeting shortly03:02
mkraiok03:02
hongbinkevinz: want to go first ?03:02
kevinzhongbin: OK03:02
kevinzLast meeting I referred that add support for run container with create new volume03:03
kevinzThis patch has finished, I will push to review in 5 minutes03:03
hongbinawesome03:03
kevinzAlso, I've checked kuryr-kubernetes03:03
kevinzPlan to refer it first to do the POC of the connector-k8s03:04
hongbinwhy refer kuryr-kubernetes ?03:04
kevinzKuryr-kuberbetes has some same implementation do things as a intermediary03:04
hongbinoh i remembered, you mentioned the watch framework in async03:05
kevinzFor kuryr-k8s, it need to talk with k8s api server and neutron client03:05
kevinzSo for us, it need to talk with k8s api server and zun client03:05
hongbinyes03:05
kevinzSo the framework is the same03:05
hongbini see03:05
hongbinsounds good03:06
hongbinanything else from your side ?03:06
kevinzThe aci-connector-k8s use timer task, I find it is not very good solution for production env03:06
kevinzJust a "demo" I think03:07
hongbinwhat is timer task ?03:07
kevinz aci-connector-k8s will talk with K8s api server every several seconds03:07
hongbinoh i see03:08
kevinzjust like polling03:08
hongbinit is definitely not ideal since we k8s api is watchable03:08
kevinzyes i think so03:08
kevinzSo move to kuryr-k8s framework03:09
*** fnaval has quit IRC03:10
kevinzthat's all from my side03:10
hongbinok, thanks kevinz for the update03:10
hongbinmkrai: want to go next ?03:10
*** kbyrne has quit IRC03:10
mkraiyes sure03:11
mkraiI posted update on my patch on including Clear Container as new runtime03:11
mkrai#link https://review.openstack.org/#/c/499534/03:11
mkraiBut it didn't work03:11
*** kbyrne has joined #openstack-meeting03:11
mkraiI will post another patch today03:12
hongbinneed any help for that ?03:12
hongbinok03:12
mkraiI will try it today and if it doesn't work, will ask for help :)03:12
mkraihongbin: Thank you :)03:12
mkraiThat's all from me03:12
hongbinmkrai: thanks madhuri03:12
hongbinthen, i will give a short update from my side03:13
hongbinlast week, i am cleaning up the sriov patches03:13
hongbinmost of the patches were merged, thanks all for reviewing03:13
hongbinin addition, i am opening a new track for the package manager03:14
hongbinthere is a WIP spec up for review03:14
hongbin#link https://blueprints.launchpad.net/zun/+spec/zun-app-package-manager03:14
mkraiI saw the spec. I will review the spec and post my comment there03:15
*** coolsvap has joined #openstack-meeting03:15
mkraiThis will be a great feature.03:15
hongbinthis feature is targeted for application deployer, and make them easier to deploy zun applicaiton03:15
kevinzDoes the file stored in DB or local directory?03:15
hongbinit is like k8s helm, it could be stored in a github repo03:16
hongbinor it can be local03:16
kevinzsorry, I mean the "helm chart file"03:16
*** salv-orlando has joined #openstack-meeting03:17
hongbini think there are two options: local and github03:17
hongbinwe could maintain a github repository for storing package that is for sharing (like docker hub for docker image)03:17
kevinzOK thanks hongbin03:18
hongbinby default, chart is pulled from github03:18
hongbinhowever, there is another option to upload local 'chart'03:18
hongbini will write down the details in the spec03:18
kevinzI have one more question, I don't like heat :-) Do we support other more friendly deployment tools?03:19
kevinzMaybe a not proper question, haha03:19
mkrai:D03:19
mkraiWe don't use heat now03:19
hongbini am thinking how to answer it :)03:19
mkraiWhere it will be used kevinz  ?03:20
hongbinkevinz: if we don't use heat, any other options available ?03:20
kevinzmkrai: use heat template to deploy the container from the spec03:21
mkraiok you mean container orchestration?03:21
kevinzhongbin: I'm thinking also. I suspect user may don't like to learn more complex heat template03:22
hongbinkevinz: ack03:22
kevinzmkrai: Yeah, deploy server container to realize a function. That need orchestration03:23
*** ijw has quit IRC03:23
*** liyi has joined #openstack-meeting03:23
*** salv-orlando has quit IRC03:23
kevinzmkrai: Just like here in line 89 https://review.openstack.org/#/c/523009/2/specs/zun-package-manager.rst03:24
mkraikevinz: Thanks for the link03:24
mkraiI will have a look03:24
hongbinkevinz: could you leave your comment in the spec, i will think about it03:26
hongbinkevinz: about the heat alternative idea03:26
kevinzhongbin: Sure, I will03:26
kevinzthanks hongbin03:26
hongbinkevinz: thanks03:26
hongbinok, all, thanks for joining hte meeting03:27
hongbinif there is nothing else, i will end the meeting shortly03:27
mkraiThanks everyone03:27
hongbin#endmeeting03:27
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"03:27
openstackMeeting ended Tue Nov 28 03:27:39 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:27
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-11-28-03.00.html03:27
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-11-28-03.00.txt03:27
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-11-28-03.00.log.html03:27
*** fnaval has joined #openstack-meeting03:32
*** ijw has joined #openstack-meeting03:34
*** ricolin has joined #openstack-meeting03:34
*** armax has joined #openstack-meeting03:34
*** fnaval has quit IRC03:37
*** links has joined #openstack-meeting03:39
*** fnaval has joined #openstack-meeting03:40
*** fnaval has quit IRC03:45
*** diga has joined #openstack-meeting03:46
*** diga has left #openstack-meeting03:46
*** fnaval has joined #openstack-meeting03:49
*** yamamoto has quit IRC03:51
*** tpatil has joined #openstack-meeting03:52
*** yamamoto has joined #openstack-meeting03:53
*** yamamoto has quit IRC03:53
*** fnaval has quit IRC03:54
*** yamamoto has joined #openstack-meeting03:54
*** yamamoto has quit IRC03:55
*** tpatil has quit IRC03:56
*** tpatil has joined #openstack-meeting03:58
*** rkmrHonjo has joined #openstack-meeting03:59
tpatilHi04:00
rkmrHonjohi04:00
*** takahara has joined #openstack-meeting04:00
*** samP___ has joined #openstack-meeting04:00
samP___hi all for masakari04:00
tpatilsamP: Ping?04:01
tpatilHi04:01
samP___#startmeeting masakari04:01
openstackMeeting started Tue Nov 28 04:01:05 2017 UTC and is due to finish in 60 minutes.  The chair is samP___. Information about MeetBot at http://wiki.debian.org/MeetBot.04:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:01
*** openstack changes topic to " (Meeting topic: masakari)"04:01
openstackThe meeting name has been set to 'masakari'04:01
samP___Hi all, sorry Im bit late04:01
samP___let's start04:01
samP___I will not be able to attend next 2 meetings, which 12/5 and 12/1204:02
samP___#topic Bugs04:02
*** openstack changes topic to "Bugs (Meeting topic: masakari)"04:02
samP___Any bug to discuss?04:02
rkmrHonjo#link https://review.openstack.org/#/c/486576/04:02
rkmrHonjoThe above patch addresses py35 UT errors. Please review it.04:03
tpatilok04:03
samP___rkmrHonjo: thanks, I will04:03
rkmrHonjotpatil, samP: thanks!04:03
samP___Any other bugs?04:04
samP___if not lets move to discussion. If any, please bring them up in AOB04:04
samP___#topic Discussion04:05
*** openstack changes topic to "Discussion (Meeting topic: masakari)"04:05
samP___(1) Horizon plugin04:05
samP___Any update?04:05
tpatilrkmrHonjo: question: You haven't made any changes to MasakariException, it has message attribute04:05
*** ricolin has quit IRC04:05
*** yamamoto has joined #openstack-meeting04:05
*** ricolin has joined #openstack-meeting04:06
tpatilrkmrHonjo : so any exception inherited from MAsakariException can use message attribute04:06
tpatil#link https://github.com/openstack/masakari/blob/master/masakari/exception.py#L15004:07
samP___tpatil: correct04:08
rkmrHonjotpail: Ah...Ok, I create a new patch and address it.04:08
*** ijw has quit IRC04:08
*** nsingh has joined #openstack-meeting04:08
tpatilrkmrHonjo: Ok, Thanks04:08
rkmrHonjotpatil: thank you for pointing out.04:09
samP___rkmrHonjo: tpatil: thanks04:09
samP___About the Horizon Plughin, I think create project patch will merge soon, once you fix the comments given04:10
samP___#link https://review.openstack.org/#/c/516550/04:10
tpatilsamP: Niraj has uploaded new PS after fixing the review comments04:11
samP___Add #openstack-masakari to access bot is done.04:11
Dinesh_BhorWe just need to answer the question and PTL +1.04:11
nsinghi will submit the patch today after anwer the given question.04:12
samP___Dinesh_Bhor: about pre-existing code? I think answer is NO, right?04:12
Dinesh_BhorsamP___: yes04:12
samP___sure, I will put my +1 to patch04:13
tpatilSo basically, we are starting masakari-dashboard project from scratch04:13
Dinesh_BhorsamP___: We don't have a code in other github repo to be directly forked to masakari-dashboard04:13
samP___tpatil: correct04:13
tpatilnsingh: Please reply to the question04:14
nsinghyes04:14
samP___then the answer is NO and once infra team created the repo, initi with cookiecutter and start working on actual code04:14
tpatilnsingh: Thanks04:14
samP___tpatil: Dinesh_Bhor: nsingh: thank you04:15
samP___I put my +104:16
samP___nsingh: Ping me if you need anything04:16
samP___(2) Install guide document04:16
nsinghsamP__: yes thank you04:16
samP___I checked the docs for Masakari and LGTM. Now waiting with my +204:17
samP___Please check and merge.04:17
samP___Still have one docs to review for masakari-monitors. I will do it soon04:18
tpatilsamP__: Ok04:18
*** salv-orlando has joined #openstack-meeting04:19
samP___(3) recovery method customization04:19
samP___Dinesh_Bhor: thanks for updating spec04:20
Dinesh_BhorI have updated the spec: https://review.openstack.org/#/c/458023/04:20
Dinesh_BhorFix queens spec directory structure: https://review.openstack.org/#/c/522219/04:20
*** fnaval has joined #openstack-meeting04:21
samP___Dinesh_Bhor: thanks. How will continue this spec? you or Abhishek?04:21
samP___s/How/Who04:21
*** chyka has joined #openstack-meeting04:21
tpatilsamP__: Dinesh will takeover this specs and implementation04:21
Dinesh_BhorsamP___: yes04:21
samP___tpatil: Dinesh_Bhor: got it. Thanks.04:22
samP___I will review this.04:22
samP___(4) Find hosts without specifying segments04:22
samP___Sorry for the delay and thanks for update the spec and code04:23
samP___I will review this after recovery method customization spec04:24
rkmrHonjosamP: Thanks.04:24
*** sridharg has joined #openstack-meeting04:24
samP___(5) Queens Work Items04:24
*** kiennt26 has quit IRC04:24
samP___rkmrHonjo: NP04:24
*** dbecker has quit IRC04:25
*** salv-orlando has quit IRC04:25
*** fnaval has quit IRC04:25
samP___Except above discussed, I think no changes/updates in Queens Work Items04:25
*** chyka has quit IRC04:26
samP___(6) Ansible support for Masakari04:26
samP___I brought up this topic since we had some requests from many people04:26
tpatilsamP: We will start understanding how to develop Ansible plugins for installing masakari service04:27
samP___I will share current OSA scripts I use for masakari under my github04:27
tpatilsamP: Thanks, that will definitely help us to understand things quickly04:28
samP___I think we need to add a BP for OSA04:28
*** dmacpher has quit IRC04:29
samP___#link https://blueprints.launchpad.net/openstack-ansible04:29
samP___tpatil: Before proceed we need to discuss with OSA team04:29
*** zhurong has quit IRC04:30
tpatilsamP: ok, but before that we need to understand few things from our side before approaching OSA team04:31
*** gouthamr has quit IRC04:31
samP___tpatil: sure04:31
tpatilsamP: thank you04:32
*** hongbin has quit IRC04:32
samP___Today I had a meeting with OPNFV deployment team04:32
samP___They are planning to include Masakari (pike) into OPNFV F release04:33
samP___One requirement form them was OSA plugin for masakari04:33
tpatilsamP: what is the timeframe of OPNFV F release?04:34
*** fnaval has joined #openstack-meeting04:35
samP___Final dead line is 2nd of May 201804:35
tpatilsamP: Ok, so before that we need to add OSA plugin for Masakari, correct?04:36
samP___sorry, 2nd of March 201804:36
samP___not May04:36
samP___If we can do it in queens release, then OK04:36
samP___I not sure what are deadline for new BP in OSA team04:37
*** psachin has joined #openstack-meeting04:37
*** dbecker has joined #openstack-meeting04:38
tpatilsamP: I will find out this info and after understanding the OSA plugins, I will let you know how much time it would take to develop these plugins04:38
*** m_kazuhiro has joined #openstack-meeting04:38
samP___Even if we can not merge it to queens, working code also would be fine. I need to confirm this with OPNFV team.04:38
samP___tpatil: sure04:39
*** m_kazuhiro has left #openstack-meeting04:39
*** fnaval has quit IRC04:39
samP___(7) BMHA04:39
samP___no update04:39
samP___#topic AOB04:40
*** openstack changes topic to "AOB (Meeting topic: masakari)"04:40
samP___Any other topics?04:40
rkmrHonjoI don't have topics.04:40
tpatilNothing from my end04:41
Dinesh_Bhornothing from my side.04:41
samP___#link https://review.openstack.org/#/c/522711/04:41
samP___I propose ^^ patch to add #openstack-masakari to meetbot and statusbot04:42
*** dmacpher has joined #openstack-meeting04:42
samP___After merge that, we could have this meeting on #openstack-masakari04:42
rkmrHonjogreat!04:43
samP___and all discussions happen in #openstack-masakari will be logged.04:43
Dinesh_BhorsamP___: does this means openstack-masakari channel logs will be recorded?04:43
*** yamamoto has quit IRC04:43
samP___yes04:43
Dinesh_BhorsamP___: ohh great04:43
Dinesh_Bhorthanks04:43
tpatilThat's nice04:43
samP___I asked this when we create this project, however at that time there was no empty slots in meetbot and un-official projects had low priority04:45
samP___I think now, meetbot have 20+ slots lefe.04:45
samP___let's see.04:45
samP___If no other topics, then let's end this meeting early04:46
samP___If you have any other topics to discuss, please use the ML or #openstack-masakari04:46
samP___Thank you all04:46
rkmrHonjothank you.04:46
tpatilThank you04:46
Dinesh_BhorThank you all04:47
samP___#endmeeting04:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"04:47
openstackMeeting ended Tue Nov 28 04:47:13 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-11-28-04.01.html04:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-11-28-04.01.txt04:47
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-11-28-04.01.log.html04:47
*** rkmrHonjo has quit IRC04:47
*** fnaval has joined #openstack-meeting04:47
*** fnaval has quit IRC04:51
*** samP___ has quit IRC04:51
*** yamamoto has joined #openstack-meeting04:54
*** yamamoto has quit IRC04:54
*** yamamoto has joined #openstack-meeting04:54
*** tpatil has quit IRC04:58
*** takahara has quit IRC04:59
*** janki has joined #openstack-meeting05:07
*** claudiub|2 has joined #openstack-meeting05:11
*** m_kazuhiro has joined #openstack-meeting05:14
*** VW has quit IRC05:16
*** caowei has quit IRC05:16
*** markstur has joined #openstack-meeting05:17
*** markstur has quit IRC05:17
*** markstur has joined #openstack-meeting05:17
*** caowei has joined #openstack-meeting05:18
*** salv-orlando has joined #openstack-meeting05:20
*** brault has quit IRC05:21
*** brault has joined #openstack-meeting05:22
*** caowei has quit IRC05:26
*** dmacpher has quit IRC05:26
*** salv-orlando has quit IRC05:27
*** slaweq has joined #openstack-meeting05:31
*** slaweq has quit IRC05:35
*** esberglu has joined #openstack-meeting05:37
*** esberglu has quit IRC05:41
*** dmacpher has joined #openstack-meeting05:43
*** caowei has joined #openstack-meeting05:46
*** m_kazuhiro has quit IRC05:53
*** armax has quit IRC05:58
*** ykatabam has quit IRC06:01
*** armax has joined #openstack-meeting06:01
*** claudiub|2 has quit IRC06:01
*** armax has quit IRC06:02
*** m_kazuhiro has joined #openstack-meeting06:03
*** pcaruana has joined #openstack-meeting06:06
*** pcaruana has quit IRC06:06
*** zhurong has joined #openstack-meeting06:06
*** kiennt26 has joined #openstack-meeting06:10
*** esberglu has joined #openstack-meeting06:15
*** VW has joined #openstack-meeting06:17
*** kiennt26 has quit IRC06:18
*** esberglu has quit IRC06:20
*** VW has quit IRC06:21
*** absubram has joined #openstack-meeting06:22
*** lpetrut has joined #openstack-meeting06:22
*** salv-orlando has joined #openstack-meeting06:22
*** VW has joined #openstack-meeting06:23
*** dmacpher has quit IRC06:26
*** chenying has joined #openstack-meeting06:26
*** VW has quit IRC06:27
*** salv-orlando has quit IRC06:28
*** absubram has quit IRC06:31
*** absubram has joined #openstack-meeting06:37
*** nguyentrihai has quit IRC06:39
*** ykatabam has joined #openstack-meeting06:41
*** bkopilov has joined #openstack-meeting06:42
*** nguyentrihai has joined #openstack-meeting06:45
*** fnaval has joined #openstack-meeting06:48
*** markstur has quit IRC06:49
*** salv-orlando has joined #openstack-meeting06:49
*** ykatabam has quit IRC06:49
*** ykatabam has joined #openstack-meeting06:49
*** salv-orlando has quit IRC06:50
*** salv-orlando has joined #openstack-meeting06:50
*** e0ne has joined #openstack-meeting06:52
*** fnaval has quit IRC06:52
*** aeng has quit IRC06:55
*** msimonin has joined #openstack-meeting06:57
*** hines has joined #openstack-meeting06:59
*** hines has quit IRC07:00
*** mriedem has quit IRC07:00
*** msimonin has quit IRC07:02
*** msimonin has joined #openstack-meeting07:02
*** msimonin has quit IRC07:03
*** msimonin has joined #openstack-meeting07:03
*** msimonin has quit IRC07:04
*** msimonin has joined #openstack-meeting07:04
*** msimonin has quit IRC07:04
*** m_kazuhiro has quit IRC07:04
*** msimonin has joined #openstack-meeting07:05
*** m_kazuhiro has joined #openstack-meeting07:05
*** zhurong has quit IRC07:05
*** msimonin has quit IRC07:05
*** msimonin has joined #openstack-meeting07:05
*** msimonin has quit IRC07:06
*** dmacpher has joined #openstack-meeting07:09
*** marios has joined #openstack-meeting07:09
*** yamahata has joined #openstack-meeting07:11
*** slaweq has joined #openstack-meeting07:17
*** iyamahat has joined #openstack-meeting07:17
*** iyamahat_ has joined #openstack-meeting07:18
*** spectr has joined #openstack-meeting07:18
*** rbartal has joined #openstack-meeting07:19
*** spectr has quit IRC07:21
*** iyamahat has quit IRC07:22
*** oidgar has joined #openstack-meeting07:23
*** slaweq has quit IRC07:25
*** VW has joined #openstack-meeting07:27
*** m_kazuhiro has quit IRC07:28
*** claudiub|2 has joined #openstack-meeting07:28
*** m_kazuhiro has joined #openstack-meeting07:28
*** VW has quit IRC07:31
*** m_kazuhiro has quit IRC07:33
*** makowals has joined #openstack-meeting07:35
*** ykatabam has quit IRC07:39
*** VW has joined #openstack-meeting07:39
*** oidgar has quit IRC07:41
*** VW has quit IRC07:44
*** slaweq has joined #openstack-meeting07:44
*** Alex_Staf has quit IRC07:48
*** msimonin has joined #openstack-meeting07:52
*** rcernin has quit IRC07:53
*** georgk has joined #openstack-meeting07:53
*** rasca has joined #openstack-meeting07:53
*** d0ugal has joined #openstack-meeting07:55
*** m_kazuhiro has joined #openstack-meeting07:57
*** fzdarsky_ is now known as fzdarsky07:57
*** kevzha01_ has joined #openstack-meeting07:58
*** andreas_s has joined #openstack-meeting07:58
*** unicell has joined #openstack-meeting08:00
*** kevinz has quit IRC08:01
*** e0ne has quit IRC08:01
*** kiennt26 has joined #openstack-meeting08:01
*** georgk has quit IRC08:04
*** andreas_s has quit IRC08:08
*** ad_rien_ has joined #openstack-meeting08:15
*** iyamahat_ has quit IRC08:16
*** iyamahat_ has joined #openstack-meeting08:16
*** lpetrut has quit IRC08:18
*** iyamahat has joined #openstack-meeting08:23
*** slaweq_ has joined #openstack-meeting08:24
*** lpetrut has joined #openstack-meeting08:25
*** iyamahat_ has quit IRC08:26
*** pcaruana has joined #openstack-meeting08:28
*** slaweq_ has quit IRC08:29
*** alexchadin has joined #openstack-meeting08:31
*** wewe0901 has joined #openstack-meeting08:45
*** iyamahat has quit IRC08:46
*** iyamahat has joined #openstack-meeting08:46
*** fnaval has joined #openstack-meeting08:48
*** fnaval has quit IRC08:52
*** gmann is now known as gmann_afk08:53
*** ianychoi has joined #openstack-meeting08:53
*** m_kazuhiro has quit IRC08:58
*** priteau has joined #openstack-meeting09:01
*** tovin07_ has quit IRC09:01
*** oidgar has joined #openstack-meeting09:03
*** yamamoto has quit IRC09:04
*** yamamoto has joined #openstack-meeting09:05
*** iyamahat has quit IRC09:09
*** iyamahat has joined #openstack-meeting09:09
*** yamamoto has quit IRC09:11
*** iyamahat has quit IRC09:15
*** iyamahat_ has joined #openstack-meeting09:15
*** oidgar has quit IRC09:18
*** ykatabam has joined #openstack-meeting09:19
*** iyamahat_ has quit IRC09:20
*** zhhuabj_ has quit IRC09:21
*** dbecker has quit IRC09:21
*** zhurong has joined #openstack-meeting09:21
*** dbecker has joined #openstack-meeting09:23
*** absubram has quit IRC09:24
*** zhhuabj_ has joined #openstack-meeting09:32
*** salv-orlando has quit IRC09:33
*** martinkopec has joined #openstack-meeting09:33
*** salv-orlando has joined #openstack-meeting09:33
*** e0ne has joined #openstack-meeting09:36
*** salv-orlando has quit IRC09:38
*** ociuhandu has joined #openstack-meeting09:43
*** lpetrut has quit IRC09:44
*** ociuhandu has quit IRC09:46
*** electrofelix has joined #openstack-meeting09:50
*** Alex_Staf has joined #openstack-meeting09:52
*** VW has joined #openstack-meeting09:53
*** erlon has joined #openstack-meeting09:55
*** rcernin has joined #openstack-meeting09:55
*** chyka has joined #openstack-meeting09:57
*** VW has quit IRC09:57
*** makowals has quit IRC09:57
*** chyka has quit IRC10:02
*** yamahata has quit IRC10:07
*** sambetts|afk is now known as sambetts10:11
*** yamamoto has joined #openstack-meeting10:14
*** zhhuabj_ has quit IRC10:15
*** yamamoto has quit IRC10:19
*** zhurong has quit IRC10:19
*** caowei has quit IRC10:20
*** msimonin has quit IRC10:20
*** msimonin has joined #openstack-meeting10:21
*** msimonin has quit IRC10:21
*** msimonin has joined #openstack-meeting10:21
*** sdague has joined #openstack-meeting10:22
*** msimonin has quit IRC10:22
*** msimonin has joined #openstack-meeting10:22
*** msimonin has quit IRC10:22
*** msimonin has joined #openstack-meeting10:23
*** msimonin has quit IRC10:24
*** zhhuabj_ has joined #openstack-meeting10:27
*** Exhar has quit IRC10:28
*** alexchadin has quit IRC10:28
*** gcb has quit IRC10:28
*** Exhar has joined #openstack-meeting10:30
*** kevzha01 has joined #openstack-meeting10:35
*** lpetrut has joined #openstack-meeting10:35
*** kevzha01_ has quit IRC10:37
*** slaweq_ has joined #openstack-meeting10:37
*** zhhuabj_ has quit IRC10:41
*** kevzha01_ has joined #openstack-meeting10:41
*** slaweq_ has quit IRC10:42
*** kevzha01 has quit IRC10:44
*** haleyb has quit IRC10:45
*** kiennt26 has quit IRC10:45
*** esberglu has joined #openstack-meeting10:46
*** fnaval has joined #openstack-meeting10:49
*** alexchadin has joined #openstack-meeting10:51
*** kevzha01_ has quit IRC10:51
*** esberglu has quit IRC10:51
*** fnaval has quit IRC10:53
*** zhhuabj_ has joined #openstack-meeting10:58
*** salv-orlando has joined #openstack-meeting11:01
*** kevzha01 has joined #openstack-meeting11:01
*** fzdarsky is now known as fzdarsky|lunch11:07
*** jkilpatr has joined #openstack-meeting11:07
*** salv-orlando has quit IRC11:07
*** manikanta_tadi has joined #openstack-meeting11:08
*** salv-orlando has joined #openstack-meeting11:08
*** makowals has joined #openstack-meeting11:12
*** salv-orlando has quit IRC11:13
*** salv-orlando has joined #openstack-meeting11:14
*** makowals has quit IRC11:21
*** makowals has joined #openstack-meeting11:23
*** wewe0901 has quit IRC11:25
*** jkilpatr has quit IRC11:27
*** jkilpatr has joined #openstack-meeting11:38
*** VW has joined #openstack-meeting11:39
*** VW has quit IRC11:44
*** chyka has joined #openstack-meeting11:47
*** mhenkel has quit IRC11:50
*** chyka has quit IRC11:51
*** efried has quit IRC11:54
*** mhenkel has joined #openstack-meeting11:54
*** phil_ has joined #openstack-meeting12:00
*** e0ne has quit IRC12:01
*** bkopilov has quit IRC12:01
*** psachin has quit IRC12:01
*** sapd_ has quit IRC12:03
*** sapd__ has joined #openstack-meeting12:03
*** julim has joined #openstack-meeting12:03
*** d0ugal has quit IRC12:04
*** e0ne has joined #openstack-meeting12:05
*** jkilpatr has quit IRC12:06
*** jkilpatr has joined #openstack-meeting12:07
*** efried has joined #openstack-meeting12:07
*** d0ugal has joined #openstack-meeting12:07
*** raildo has joined #openstack-meeting12:10
*** julim has quit IRC12:11
*** manikanta_tadi has quit IRC12:18
*** yamamoto has joined #openstack-meeting12:18
*** yamamoto has quit IRC12:22
*** esberglu has joined #openstack-meeting12:34
*** rossella_s has quit IRC12:38
*** esberglu has quit IRC12:39
*** rossella_s has joined #openstack-meeting12:41
*** lpetrut has quit IRC12:42
*** rossella_s has quit IRC12:46
*** bobh has joined #openstack-meeting12:46
*** rossella_s has joined #openstack-meeting12:47
*** fzdarsky|lunch is now known as fzdarsky12:55
*** zhurong_phone has joined #openstack-meeting12:55
*** yangyapeng has quit IRC12:56
*** ruijiej has joined #openstack-meeting12:59
ruijiej#startmeeting senlin13:00
openstackMeeting started Tue Nov 28 13:00:04 2017 UTC and is due to finish in 60 minutes.  The chair is ruijiej. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: senlin)"13:00
openstackThe meeting name has been set to 'senlin'13:00
*** georgk has joined #openstack-meeting13:00
*** ricolin has quit IRC13:01
*** liyi has quit IRC13:02
ruijiejhi13:04
*** fouadben has joined #openstack-meeting13:07
*** slaweq_ has joined #openstack-meeting13:10
*** sboyron has joined #openstack-meeting13:10
*** ijw has joined #openstack-meeting13:11
*** dprince has joined #openstack-meeting13:11
*** msimonin has joined #openstack-meeting13:12
*** msimonin1 has joined #openstack-meeting13:13
*** slaweq_ has quit IRC13:14
*** ijw has quit IRC13:15
*** ruijiej has quit IRC13:16
*** msimonin has quit IRC13:16
*** links has quit IRC13:16
*** ruijiej has joined #openstack-meeting13:16
ruijiej#endmeeting13:17
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:17
openstackMeeting ended Tue Nov 28 13:17:46 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:17
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-11-28-13.00.html13:17
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-11-28-13.00.txt13:17
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-11-28-13.00.log.html13:17
*** ruijiej has quit IRC13:18
*** lhx_ has joined #openstack-meeting13:20
*** VW has joined #openstack-meeting13:21
*** pchavva has joined #openstack-meeting13:21
*** edmondsw has joined #openstack-meeting13:22
*** rossella_s has quit IRC13:24
*** VW has quit IRC13:26
*** rossella_s has joined #openstack-meeting13:27
*** pchavva has quit IRC13:27
*** bobh has quit IRC13:27
*** abalutoiu has joined #openstack-meeting13:27
*** bkopilov has joined #openstack-meeting13:28
*** esberglu has joined #openstack-meeting13:29
*** esberglu has quit IRC13:29
*** esberglu has joined #openstack-meeting13:29
*** esberglu has quit IRC13:29
*** dmacpher is now known as dmacpher-afk13:30
*** esberglu has joined #openstack-meeting13:30
*** jaypipes has joined #openstack-meeting13:31
*** yangyapeng has joined #openstack-meeting13:32
*** mriedem has joined #openstack-meeting13:32
*** esberglu has quit IRC13:35
*** yangyapeng has quit IRC13:37
*** egallen has quit IRC13:38
*** pchavva has joined #openstack-meeting13:42
*** HeOS has quit IRC13:43
*** ykatabam has quit IRC13:46
*** VW has joined #openstack-meeting13:47
*** chenybd_ has joined #openstack-meeting13:47
*** rbudden has joined #openstack-meeting13:49
*** salv-orlando has quit IRC13:57
*** haleyb has joined #openstack-meeting13:58
*** esberglu has joined #openstack-meeting14:00
*** shintaro has joined #openstack-meeting14:00
*** yamahata has joined #openstack-meeting14:00
*** mmethot has joined #openstack-meeting14:00
igordchi ccf folks14:04
bcafareligordc: hey14:05
igordcme and davidsha are not yet available to/join start the meeting due to unexpected events... we will be able to in about 5-8 minutes14:06
igordcapologies14:06
*** thorst has joined #openstack-meeting14:06
*** bobh has joined #openstack-meeting14:08
*** davidsha_ has joined #openstack-meeting14:10
*** davidsha has joined #openstack-meeting14:13
*** pcaruana has quit IRC14:13
*** rossella_s has quit IRC14:14
*** davidsha_ has quit IRC14:15
davidsha#startmeeting network_common_flow_classifier14:17
openstackMeeting started Tue Nov 28 14:17:16 2017 UTC and is due to finish in 60 minutes.  The chair is davidsha. Information about MeetBot at http://wiki.debian.org/MeetBot.14:17
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:17
*** openstack changes topic to " (Meeting topic: network_common_flow_classifier)"14:17
openstackThe meeting name has been set to 'network_common_flow_classifier'14:17
davidshaHi, sorry for being late!14:17
*** pcaruana has joined #openstack-meeting14:17
bcafarelhey14:18
*** rossella_s has joined #openstack-meeting14:18
igordchello hello14:18
davidshaI'll go straight to Open Discussion, I haven't any updates on the patches.14:19
davidshaIs that ok?14:19
igordcdavidsha: yes14:20
davidsha#topic Open Discussion14:20
*** openstack changes topic to "Open Discussion (Meeting topic: network_common_flow_classifier)"14:20
davidshabcafarel: would you be interested in taking over chairing this meeting?14:21
bcafarelI had to check the reviews list, I did not even remember what was the patches status :/14:21
*** yamamoto has joined #openstack-meeting14:21
davidshatmorin left a review on the oslo + models patch that needs to be addressed, but I believe I have someone interested in picking up that patch14:22
bcafareloh that would be nice14:22
bcafareldavidsha: no problem chairing the meeting, though for working on ccf itself I have limited bandwith for the next few months14:23
davidshabcafarel: taking over the meeting or someone picking up the patch ;)14:23
bcafarelobviously someone picking up the patch sounds better :)14:23
davidshaThat's fair enough, There were 2 guys interested in development. I believe they are both ramping up on the patches.14:24
davidshaIf you're interested, I might try to organize a google hangout between us to help get the up to speed?14:25
davidshaI just need to find out what time zones they're in.14:26
bcafareldavidsha: sure, though on current code igordc and you are probably the most knowledgeable14:26
bcafarelif you find guys in Australia it will not be easy ;)14:27
davidshaSure, I presume the people who work on CCF are up for challenges anyways ;P14:27
davidshaI'll also add you and tmorin as core reviewers to the neutron-classifier repo.14:28
davidshaI'll try to stay on top of patches and help with reviews while I can,14:28
*** janki has quit IRC14:29
davidshaThats all from me I think, is there anything anyone else would like to bring up?14:30
bcafareldavidsha: ack thanks14:31
*** slaweq has quit IRC14:31
igordcsounds great14:31
bcafarelnot sure if sending a "ccf needs manpower, come and help us" mail to openstack-dev will help for headcount14:31
davidshabcafarel: you'll be in Dublin for the PTG right?14:32
*** slaweq has joined #openstack-meeting14:32
*** alexchadin has quit IRC14:32
bcafareldavidsha: I hope :)14:32
davidshaWell maybe less of a "needs help" and more of a "We invite you to participate in this exciting opportunity..."14:33
davidsha:)14:33
bcafareldavidsha: ok you win you write the mail :)14:33
davidshaDamn!14:33
*** yamamoto has quit IRC14:33
davidshaI'll draft something by the end of this week.14:34
*** eharney has quit IRC14:34
*** ricolin has joined #openstack-meeting14:35
bcafarelhopefully some people in Dublin PTG will show interest too14:35
*** slaweq has quit IRC14:36
davidshabcafarel: Yes, I think we'll need all our patches merged by then before that though, If the other projects can start trying out PoCs then they'll also contribute to extend and maintain the API.14:37
bcafareldavidsha: yeah getting some v0 in before that would be great14:38
davidsha+114:39
davidsha... +2 WF +1..14:39
bcafarel:) not yet I think there are some comments by tmorin first!14:40
*** armax has joined #openstack-meeting14:40
davidshaI'll get in touch with the new guys and ask them to attend the next meeting if possible.14:40
davidshabcafarel: I can add them as notes to the patch for example: "#Note(tmorin) This dict key is mispelled, this needs more unit test coverage"14:41
bcafarelthat's possible indeed14:42
bcafarelanyways as long as we do not flag a v1, big changes can still go in14:43
davidshabcafarel: that was a joke :P14:43
davidshamaybe I should hold off on those core reviewer rights... :P14:43
bcafareldavidsha: why, don't want your last big commit to be so horrible everyone will cross the road when they see you?14:44
*** rossella_s has quit IRC14:44
*** lpetrut has joined #openstack-meeting14:44
davidshabcafarel: It would certainly be a good to make my name in the community :P14:44
bcafarel:)14:45
davidshaI can't be famous so I should just be infamous and all that!14:45
bcafarelhmm ok maybe we will stick to the plan to wait until we have an "acceptable" v014:46
*** rossella_s has joined #openstack-meeting14:47
igordcI think davidsha should pursue a career in hollywood or the music industry instead!14:47
*** VW has quit IRC14:47
davidshaigordc: I have the face of a pit bull chewing a wasp, that could be difficult!14:48
bcafarelthat could be the next trend14:48
davidshaIts all about timing I suppose :)14:49
*** rbowen has joined #openstack-meeting14:50
*** salv-orlando has joined #openstack-meeting14:51
davidshaShould we wrap this up then or shall we speculate further on my future in Hollywood?14:51
*** brault has quit IRC14:51
igordcdavidsha: I was gonna start drafting the manuscript for "the wasp that bit the dog"14:52
bcafarellet's just hope you don't forget us when you are there14:52
bcafareland else we can wrap up I guess (coffee is almost ready)14:52
*** fnaval has joined #openstack-meeting14:53
davidshacool, Look forward to my agent receiving the first draft, and I'll put a reminder in my calender now :P14:53
davidsha#endmeeting14:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:54
openstackMeeting ended Tue Nov 28 14:54:08 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2017/network_common_flow_classifier.2017-11-28-14.17.html14:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2017/network_common_flow_classifier.2017-11-28-14.17.txt14:54
openstackLog:            http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2017/network_common_flow_classifier.2017-11-28-14.17.log.html14:54
bcafarel:)14:54
igordcbye all14:54
davidshasee ye!14:54
*** brault has joined #openstack-meeting14:55
*** sgrasley1 has quit IRC14:55
*** salv-orl_ has joined #openstack-meeting14:56
*** nijaba has quit IRC14:56
*** davidsha has quit IRC14:56
*** shintaro has quit IRC14:57
*** ad_rien_ has quit IRC14:59
*** salv-orlando has quit IRC14:59
*** yamamoto has joined #openstack-meeting15:00
*** awaugama has joined #openstack-meeting15:00
*** ad_rien_ has joined #openstack-meeting15:01
*** hongbin has joined #openstack-meeting15:02
*** rossella_s has quit IRC15:02
*** sgrasley1 has joined #openstack-meeting15:04
*** chenybd_ has quit IRC15:07
*** liusheng has quit IRC15:07
*** marst has joined #openstack-meeting15:10
*** yamamoto has quit IRC15:10
*** zhurong_phone has quit IRC15:15
*** VW has joined #openstack-meeting15:16
*** clayton has quit IRC15:20
*** artom has quit IRC15:21
*** clayton has joined #openstack-meeting15:21
*** coolsvap has quit IRC15:24
*** artom has joined #openstack-meeting15:25
*** d0ugal has quit IRC15:28
*** janki has joined #openstack-meeting15:28
*** sapd__ has quit IRC15:34
*** sapd_ has joined #openstack-meeting15:34
*** msimonin1 has quit IRC15:36
*** msimonin has joined #openstack-meeting15:36
*** HeOS has joined #openstack-meeting15:38
*** slaweq has joined #openstack-meeting15:38
*** d0ugal has joined #openstack-meeting15:42
*** slaweq has quit IRC15:43
*** manjeets_ has joined #openstack-meeting15:43
*** dklyle has joined #openstack-meeting15:43
*** korzen_ has joined #openstack-meeting15:43
*** yamahata__ has joined #openstack-meeting15:44
*** gouthamr has joined #openstack-meeting15:45
*** isq_ has quit IRC15:45
*** slaweq has joined #openstack-meeting15:45
*** manjeets has quit IRC15:45
*** korzen has quit IRC15:45
*** yamamoto has joined #openstack-meeting15:46
*** ijw has joined #openstack-meeting15:46
*** david-lyle has quit IRC15:46
*** slaweq has quit IRC15:50
*** ijw has quit IRC15:50
*** VW_ has joined #openstack-meeting15:51
*** jamesmcarthur has joined #openstack-meeting15:52
*** yamamoto has quit IRC15:52
*** mlavalle has joined #openstack-meeting15:53
*** VW has quit IRC15:54
*** VW has joined #openstack-meeting15:55
*** VW_ has quit IRC15:56
*** markstur has joined #openstack-meeting15:58
*** VW has quit IRC15:59
*** jlibosva has joined #openstack-meeting16:00
*** VW has joined #openstack-meeting16:00
*** ihrachys has joined #openstack-meeting16:01
ihrachys#startmeeting neutron_ci16:01
openstackMeeting started Tue Nov 28 16:01:19 2017 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:01
openstackThe meeting name has been set to 'neutron_ci'16:01
mlavalleo/16:01
jlibosvao/16:01
haleybhi16:01
*** masuberu has joined #openstack-meeting16:01
*** ricolin has quit IRC16:01
*** haint has joined #openstack-meeting16:01
ihrachyshello folks16:01
ihrachys#topic Actions from prev meeting16:01
*** openstack changes topic to "Actions from prev meeting (Meeting topic: neutron_ci)"16:01
*** ricolin has joined #openstack-meeting16:02
ihrachysas usual, we start with actions from last meeting16:02
ihrachysfirst is "jlibosva to figure out why unstable_test didn't work for fullstack scenario case"16:02
ihrachysthough afaiu we figured it out in the meeting16:02
jlibosvawe figured that out in the last meeting itself16:02
jlibosvaright, it was because it failed in setup phase16:02
ihrachysand we decided to leave it as is16:02
mlavalleyes16:02
ihrachys+ your patch that bumped the timeout to wait agents in fullstack16:03
jlibosvaright - https://review.openstack.org/#/c/522872/16:03
ihrachysI mean this one: https://review.openstack.org/#/c/522872/16:03
ihrachysok16:03
ihrachysI guess we could backport it to reduce spurious failures from stable16:03
ihrachysnext was "jlibosva to investigate / report a bug for env deployment failure in fullstack because of port down"16:03
ihrachysand that's basically the fix above16:03
jlibosvacorrect - bug here https://bugs.launchpad.net/neutron/+bug/173435716:04
openstackLaunchpad bug 1734357 in neutron "fullstack: Test runner doesn't wait enough time for env to come up" [High,Fix released] - Assigned to Jakub Libosvar (libosvar)16:04
jlibosvaand I requested the backport to pike right now - https://review.openstack.org/#/c/523453/16:04
ihrachysjlibosva, so you observed up to 3 mins waiting on agents?16:04
jlibosvano, I observed 67 seconds but I wanted to be safe so I tripled the value16:04
jlibosvait's active polling so once env is ready, the waiting loop stopps16:05
jlibosvastops*16:05
ihrachysI see. why is it so slow though? is it because of high parallelism?16:05
*** masber has quit IRC16:05
jlibosvaso the worst case, we wait three minutes only when there is real issue16:05
*** nguyentrihai has quit IRC16:05
ihrachysor would be same in single thread16:05
jlibosvaI didn't investigate that, I saw it took 30 seconds for the ovs-agent to start logging16:05
jlibosvai.e. between test runner spawning process and process actually doing something was a 30 seconds gap16:05
*** lpetrut has quit IRC16:06
*** davidsha has joined #openstack-meeting16:06
*** marios has quit IRC16:06
jlibosvaso it sounds like busy machine. but I haven't checked load and cpu usage stats16:06
*** lpetrut has joined #openstack-meeting16:06
ihrachysok, I guess if it's something serious it will resurface eventually16:07
ihrachysthe job already takes a lot of time. we won't be able to push the boundary indefinitely while adding new cases16:07
ihrachysok, moving on16:07
ihrachys"ihrachys to investigate latest https://bugs.launchpad.net/neutron/+bug/1673531 failures"16:07
openstackLaunchpad bug 1673531 in neutron "fullstack test_controller_timeout_does_not_break_connectivity_sigkill(GRE and l2pop,openflow-native_ovsdb-cli) failure" [High,Confirmed] - Assigned to Ihar Hrachyshka (ihar-hrachyshka)16:07
ihrachysI had a look at logs16:07
*** masuberu has quit IRC16:08
ihrachysso the test case fails on polling port of second fake machine for ACTIVE16:08
*** bzhao has quit IRC16:08
ihrachyshere is the first attempt: http://logs.openstack.org/71/520371/7/check/legacy-neutron-dsvm-fullstack/ad585a2/logs/dsvm-fullstack-logs/TestOvsConnectivitySameNetworkOnOvsBridgeControllerStop.test_controller_timeout_does_not_break_connectivity_sigkill_GRE-and-l2pop,openflow-native_.txt.gz#_2017-11-20_21_59_56_46916:08
*** masuberu has joined #openstack-meeting16:08
ihrachysactually, the attempt is the only one, despite us using wait_until_true16:08
ihrachysand this is because for some reason neutron-server hanged in the middle processing request16:09
ihrachyshere is where the server eventually gives up: http://logs.openstack.org/71/520371/7/check/legacy-neutron-dsvm-fullstack/ad585a2/logs/dsvm-fullstack-logs/TestOvsConnectivitySameNetworkOnOvsBridgeControllerStop.test_controller_timeout_does_not_break_connectivity_sigkill_GRE-and-l2pop,openflow-native_/neutron-server--2017-11-20--21-57-14-411163.txt.gz#_2017-11-20_22_01_03_47516:09
ihrachysprobably triggered by DELETE sent during cleanup of the test case16:09
*** bzhao has joined #openstack-meeting16:09
ihrachysnote that those are two only messages with the req-id in the server log16:09
ihrachysnot sure what to make of it yet16:10
ihrachysusually we have some messages from when the request arrives16:10
ihrachysit could be though that it didn't for some reason16:10
ihrachysand then we see it e.g. repeated in the background / tcp connectivity to server finally recovered but it's too late16:11
jlibosvaso you're saying that wait_until_true doesn't actually poll?16:12
ihrachysjlibosva, maybe it's locked because it waits for reply to its request16:13
ihrachyswe wait for 60 seconds there16:13
ihrachysand after that it bails out16:13
ihrachysand the client apparently also waits 60s+ for reply16:13
ihrachysso we don't ever have a chance to actually retry with new http request16:13
ihrachysif f.e. the previous one is lost somehow by the server16:14
jlibosvaI see16:14
ihrachysalso note that the message in server log is 6s+ after 60s16:14
*** jgu has joined #openstack-meeting16:14
*** eharney has joined #openstack-meeting16:14
*** dtrainor has quit IRC16:14
ihrachysoh and one more thing there16:15
ihrachysthere are two ports there (two fake machines)16:16
ihrachysfirst one is ACTIVE, and here is the message in test log that gives the req-id: http://logs.openstack.org/71/520371/7/check/legacy-neutron-dsvm-fullstack/ad585a2/logs/dsvm-fullstack-logs/TestOvsConnectivitySameNetworkOnOvsBridgeControllerStop.test_controller_timeout_does_not_break_connectivity_sigkill_GRE-and-l2pop,openflow-native_.txt.gz#_2017-11-20_21_59_56_46816:16
*** ad_rien_ has quit IRC16:16
ihrachysbut when you search for the id in server log, you don't have it there at all16:16
*** ad_rien_ has joined #openstack-meeting16:17
ihrachysbut if you try to relate messages, the request is probably this: http://logs.openstack.org/71/520371/7/check/legacy-neutron-dsvm-fullstack/ad585a2/logs/dsvm-fullstack-logs/TestOvsConnectivitySameNetworkOnOvsBridgeControllerStop.test_controller_timeout_does_not_break_connectivity_sigkill_GRE-and-l2pop,openflow-native_/neutron-server--2017-11-20--21-57-14-411163.txt.gz#_2017-11-20_21_59_56_45616:18
ihrachysnote a different id16:18
jlibosvaI also noted http://logs.openstack.org/71/520371/7/check/legacy-neutron-dsvm-fullstack/ad585a2/logs/dsvm-fullstack-logs/TestOvsConnectivitySameNetworkOnOvsBridgeControllerStop.test_controller_timeout_does_not_break_connectivity_sigkill_GRE-and-l2pop,openflow-native_/neutron-server--2017-11-20--21-57-14-411163.txt.gz#_2017-11-20_22_00_00_83816:18
jlibosvawhich is 4 seconds after querying the API16:18
jlibosvaso maybe ovs agent reported something in the meantime16:18
ihrachyshow is it possible that we have different req-id in server and client?16:19
ihrachysis there something in between proxying / overriding headers?16:20
ihrachysanyway... I will dig more16:20
ihrachysI probably should capture what we have alraedy there16:20
ihrachysnext item was "slaweq to investigate / report a bug for test_dscp_marking_packets fullstack failure"16:21
ihrachysI don't see slaweq around16:21
ihrachysbut I see this reported: https://bugs.launchpad.net/neutron/+bug/173364916:21
openstackLaunchpad bug 1733649 in neutron "fullstack neutron.tests.fullstack.test_qos.TestDscpMarkingQoSOvs.test_dscp_marking_packets(openflow-native) failure" [High,Confirmed] - Assigned to Slawek Kaplonski (slaweq)16:21
ihrachysslaweq seems to work on it16:22
jlibosvato the previous - maybe when you don't provide req-id it generates one?16:22
jlibosvaand what we see on server comes from previous call16:22
ihrachysjlibosva, what do you mean? I believe the req-id logged in test case log is generated, yes, but then it is still sent to server16:23
jlibosvaI see curl used:16:23
jlibosvahttp://logs.openstack.org/71/520371/7/check/legacy-neutron-dsvm-fullstack/ad585a2/logs/dsvm-fullstack-logs/TestOvsConnectivitySameNetworkOnOvsBridgeControllerStop.test_controller_timeout_does_not_break_connectivity_sigkill_GRE-and-l2pop,openflow-native_.txt.gz#_2017-11-20_21_59_53_60516:23
jlibosva3 seconds before the neutronclient call with req-d16:23
*** bobh has quit IRC16:24
ihrachysit still says "neutronclient.client" in the message16:24
ihrachysso probably neutronclient uses curl under the hood?16:24
jlibosvano, I think it uses python library16:24
jlibosvaurllib or httplib or something16:25
ihrachysok, I will have a closer look16:25
ihrachysI don't want to take all the time for this issue16:25
ihrachysso let's move on16:25
jlibosvasure16:25
jlibosvasorry16:25
ihrachysthese were all items from previous meeting16:25
ihrachys#topic Grafana16:25
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:25
ihrachyshttp://grafana.openstack.org/dashboard/db/neutron-failure-rate16:25
ihrachysI was actually hopeful that with agent timeout fix the failure rate for fullstack will drop, but seems like it didn't16:26
haleybno rainbows and unicorns :(16:26
ihrachysit's at least not as flat as it was but we have long way to go16:27
ihrachyswe'll look at latest failures later16:27
*** lpetrut has quit IRC16:28
ihrachysin the meantime, I will only note that nothing material changed for fullstack or scenarios.16:28
ihrachysperiodics seem ok too16:28
*** salv-orlando has joined #openstack-meeting16:28
ihrachysso let's dive into specifics16:28
ihrachys#topic Fullstack16:28
*** openstack changes topic to "Fullstack (Meeting topic: neutron_ci)"16:28
*** phil_ has quit IRC16:28
ihrachysfor starter, we have the Kuba's fix to backport; I work on the req-id / port not active issue / slaweq looking at qos dscp failure16:29
ihrachyslet's see if there is anything else that we don't know about in latest logs16:29
*** rbudden has quit IRC16:30
ihrachysI am looking at http://logs.openstack.org/72/522872/1/check/legacy-neutron-dsvm-fullstack/50dfd44/logs/testr_results.html.gz16:30
*** rbudden has joined #openstack-meeting16:30
ihrachysactually, failure rebound for fullstack back to ~90% could be because of dscp qos failure that slaweq suggested in LP is new16:30
*** salv-orl_ has quit IRC16:31
jlibosvais that with the timeout bump patch in?16:31
ihrachysit is results from your patch so yes16:31
*** yamamoto has joined #openstack-meeting16:31
jlibosva:(16:31
jlibosvathe env build fails still16:31
ihrachysas we can see in logs, a log of failures are due to a timeout issue that is similar to what I am looking at16:31
ihrachyswhere it fails on waiting a port to become ACTIVE16:32
jlibosvaoh, wait, no16:32
ihrachysit could be either port genuinely is down, or an issue like mine where server is not responsive16:32
ihrachysalso in this run, test_controller_timeout_does_not_break_connectivity_sigkill failed but with slightly different error16:33
ihrachysneutron.tests.common.machine_fixtures.FakeMachineException: No ICMP reply obtained from IP address 20.0.0.1016:33
ihrachyswhich happens AFTER ports are validated to be ACTIVE16:33
jlibosvashall we mark the test_connectivity tests as unstable with the bug that you're looking at?16:34
jlibosvaand qos with slaweq's bug16:34
ihrachysso it must be a different issue16:34
ihrachysjlibosva, probably. I will post a patch.16:34
ihrachys#action ihrachys to disable connectivity fullstack tests while we look for culprit16:34
ihrachys#action ihrachys to disable dscp qos fullstack test while we look for culprit16:35
ihrachysthere are two more failures that are not falling into the set16:35
ihrachystest_l2_agent_restart with AssertionError: False is not true in     self.assertTrue(all([r.done() for r in restarts]))16:35
ihrachysand test_securitygroup(linuxbridge-iptables) with RuntimeError: Process ['ncat', u'20.0.0.11', '3333', '-w', '20'] hasn't been spawned in 20 seconds16:36
*** yamamoto has quit IRC16:36
jlibosvaI can have a look at the netcat issue, I hope it won't be related to linuxbridge agent :)16:36
ihrachys#action jlibosva to look at test_securitygroup(linuxbridge-iptables) failure in fullstack16:37
ihrachysany candidates to look at test_l2_agent_restart ?16:37
jlibosvaI can also pick that one if nobody wants16:39
ihrachys:)16:39
ihrachyssory jlibosva16:39
ihrachyswe love you :)16:39
jlibosvaI have a feeling it will be related to slow agent starts16:39
ihrachys#action jlibosva to look at test_l2_agent_restart fullstack failure16:40
jlibosvaas I observed it in the env build-up issue16:40
* jlibosva loves being loved16:40
ihrachysthat restart test is afair brutally restarting agents. if it's slow, could hit it in one of restart cycles16:40
ihrachysthough having timeout bumped to 60 sec for each iteration there is maybe not the best path16:41
ihrachysok seems like we have work to do for fullstack16:41
ihrachys#topic Scenarios16:41
*** openstack changes topic to "Scenarios (Meeting topic: neutron_ci)"16:41
ihrachyswe have old bugs16:42
ihrachyshttps://bugs.launchpad.net/neutron/+bug/171730216:42
openstackLaunchpad bug 1717302 in neutron "Tempest floatingip scenario tests failing on DVR Multinode setup with HA" [High,Confirmed]16:42
ihrachysand https://bugs.launchpad.net/neutron/+bug/171971116:42
openstackLaunchpad bug 1719711 in neutron "iptables failed to apply when binding a port with AGENT.debug_iptables_rules enabled" [High,In progress] - Assigned to Dr. Jens Harbott (j-harbott)16:42
*** salv-orlando has quit IRC16:42
ihrachysfor the latter, there seems to be a fix!16:42
ihrachyshere https://review.openstack.org/#/c/523319/16:42
*** salv-orlando has joined #openstack-meeting16:42
*** [HeOS] has joined #openstack-meeting16:42
ihrachyseveryone please review after the meeting :)16:43
ihrachysas for dvr fip issue, mlavalle haleyb no news I believe?16:43
*** lpetrut has joined #openstack-meeting16:43
haleybihrachys: i will need to look, nothing from swami yet16:43
mlavalleihrachys: we haven't heard from swami16:43
*** slaweq has joined #openstack-meeting16:43
mlavallelet's make sure we talk to him this week16:44
mlavalleI think we will have to reassign that issue16:44
ihrachysyeah... maybe he is swamped and we need someone else to have a look instead16:44
mlavalleI'll talk to him16:44
ihrachysright, it's not moving forward. thanks!16:44
*** HeOS has quit IRC16:44
ihrachys#topic Tempest plugin16:45
*** openstack changes topic to "Tempest plugin (Meeting topic: neutron_ci)"16:45
ihrachysso the etherpad is https://etherpad.openstack.org/p/neutron-tempest-plugin-job-move16:45
*** oidgar has joined #openstack-meeting16:45
ihrachysand we have some items there still in progress16:45
*** slaweq_ has joined #openstack-meeting16:45
ihrachysactually quite a lot :)16:45
ihrachysone thing that blocks us is that we still have legacy jobs in master16:45
ihrachysso we can't e.g. remove tempest test classes from neutron tree16:45
ihrachysI believe mlavalle was looking at it16:46
ihrachysmlavalle, any news?16:46
mlavallewell, I am looking at it for stable branches16:46
*** salv-orlando has quit IRC16:46
mlavalleI pushed this https://review.openstack.org/#/c/522931 over the weekend16:46
jlibosvaare we going to migrate stable branches too?16:46
jlibosvaI thought no16:46
jlibosvanot*16:46
ihrachysmlavalle, so your order would be move jobs to stable, then remove from infra?16:46
jlibosvaah, sorry. it's about legacy jobs. ignore me :)16:47
ihrachysjlibosva, projects move their jobs including to stable. I saw others doing it, there is infra request.16:47
mlavalleyes16:47
ihrachysjlibosva, after we move to stable, they are able to clean them up16:47
ihrachysin their repos16:47
mlavalleI can also move master16:47
*** msimonin has quit IRC16:47
mlavalleit's only that I thought someone else was doing ti16:47
jlibosvaI apologize, I thought you meant adopting stable branches for neutron plugin :)16:47
ihrachysmlavalle, I was thinking, we could also have a small patch that makes the legacy jobs executed on stable only while we move jobs?16:47
*** slaweq has quit IRC16:48
ihrachysmlavalle, that would be a simple fix and unblock cleanup in neutron tree16:48
*** rbartal has quit IRC16:48
ihrachysmlavalle, master doesn't need move, it needs removal since we already have new jobs there16:48
mlavalleyeah, that's what I thought16:48
ihrachysmlavalle, I would imagine we could make it with a regex against stable.* for branch for legacy?16:48
mlavalleyeah that sounds right16:49
ihrachysmlavalle, do you want to cover the regex yourself or I should do it?16:50
mlavalleplease take care of that16:50
ihrachysok16:51
ihrachys#action ihrachys to disable legacy jobs for neutron master16:51
mlavalleI will continue with the patch for Pike ^^^^16:51
mlavalleand also another one for Ocata16:51
ihrachysgreat16:51
ihrachysfor ocata you may just backport once done with pike16:51
ihrachysit should work16:51
mlavalleyeap, that's my plan16:52
ihrachysoh so I look at the patch for pike, and I see you move all tempest jobs not just those for tempest plugin?16:52
*** jamesmcarthur has quit IRC16:52
mlavalleI moved all legacy16:52
ihrachysI was under impression you were covering plugin jobs only16:52
ihrachysif not, I don't think anyone is looking at master patch to do the same16:52
mlavalleok, I can do a similar thing for master16:53
ihrachysand for those, it could make sense to start in master16:53
ihrachysyeah16:53
ihrachysthanks!16:53
*** jamesmcarthur has joined #openstack-meeting16:53
ihrachysI also had a small fix to skip new jobs for doc/* changes: https://review.openstack.org/#/c/523244/16:54
ihrachysspotted them executed in a doc-only change in neutron repo16:54
mlavallepushed it in16:55
* ihrachys bows16:55
ihrachysand once legacy jobs are gone in master, we can push https://review.openstack.org/#/c/506672/16:55
*** chyka has joined #openstack-meeting16:56
mlavalleyeah16:56
ihrachysok I think that mostly covers next steps for plugin repo16:56
ihrachys#topic Open discussion16:56
mlavalle++16:56
*** openstack changes topic to "Open discussion (Meeting topic: neutron_ci)"16:56
ihrachysanything to bring up?16:56
ihrachysseems like no! well then you have 3 mins back!16:57
*** VW has quit IRC16:57
ihrachysenjoy!16:57
ihrachys#endmeeting16:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:57
mlavallethanks!16:57
openstackMeeting ended Tue Nov 28 16:57:33 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-11-28-16.01.html16:57
* ihrachys feels generous!16:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-11-28-16.01.txt16:57
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-11-28-16.01.log.html16:57
*** jlibosva has left #openstack-meeting17:00
*** VW has joined #openstack-meeting17:02
*** liusheng has joined #openstack-meeting17:04
*** georgk has quit IRC17:05
*** ijw has joined #openstack-meeting17:09
*** rossella_s has joined #openstack-meeting17:09
*** jamesmcarthur has quit IRC17:11
*** mugsie has joined #openstack-meeting17:13
*** guinm is now known as mguiney17:14
*** lhx_ has quit IRC17:16
*** yamamoto has joined #openstack-meeting17:16
*** mlavalle has left #openstack-meeting17:17
*** sshank has joined #openstack-meeting17:19
*** jamesmcarthur has joined #openstack-meeting17:21
*** yamamoto has quit IRC17:21
*** ekcs has joined #openstack-meeting17:24
*** jamesmcarthur has quit IRC17:25
*** ad_rien_ has quit IRC17:26
*** spilla has joined #openstack-meeting17:26
*** manjeets has joined #openstack-meeting17:31
*** davidsha has quit IRC17:33
*** sshank has quit IRC17:34
*** sshank has joined #openstack-meeting17:34
*** Alex_Staf has quit IRC17:37
*** Apoorva has joined #openstack-meeting17:40
*** ricolin has quit IRC17:40
*** Apoorva has quit IRC17:40
*** Apoorva has joined #openstack-meeting17:41
*** lpetrut has quit IRC17:45
*** jamesmcarthur has joined #openstack-meeting17:45
*** gagehugo has joined #openstack-meeting17:46
*** martinkopec has quit IRC17:46
*** yamahata has quit IRC17:47
*** KwozyMan has joined #openstack-meeting17:50
*** sambetts is now known as sambetts|afk17:50
*** pcaruana has quit IRC17:53
*** thorst has quit IRC17:57
*** thorst has joined #openstack-meeting17:58
lbragstad#startmeeting keystone18:00
openstackMeeting started Tue Nov 28 18:00:09 2017 UTC and is due to finish in 60 minutes.  The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: keystone)"18:00
openstackThe meeting name has been set to 'keystone'18:00
cmurphyo/18:00
lbragstado/18:00
lamto/18:00
raildo\o/18:00
hrybackio/18:00
lbragstadping ayoung, breton, cmurphy, dstanek, edmondsw, gagehugo, henrynash, hrybacki, knikolla, lamt, lbragstad, lwanderley, kmalloc, rderose, rodrigods, samueldmq, spilla, aselius, dpar18:00
gagehugoo/18:00
KwozyMano/18:00
*** unicell has quit IRC18:00
knikollao/18:00
lbragstad#link https://etherpad.openstack.org/p/keystone-weekly-meeting18:00
lbragstadagenda ^18:00
rodrigodso/18:01
lbragstad#topic announcements18:01
*** openstack changes topic to "announcements (Meeting topic: keystone)"18:01
*** yamamoto has joined #openstack-meeting18:01
lbragstad#info gerrit cleanup happened last week and this week18:02
lbragstadif you noticed things get abandon, that's why18:02
lbragstadhopefully the review queue is a bit cleaner18:02
lbragstadwe can always restore things if we decide to pursue them again18:02
*** thorst has quit IRC18:02
lbragstad#info reminder that queens-2 is next week18:02
lbragstadwhich also means that our specification freeze deadline is next week as well18:03
lbragstad#link https://releases.openstack.org/queens/schedule.html18:03
lbragstadwhich leads us into our next topic18:04
lbragstad#topic Specifications18:04
*** openstack changes topic to "Specifications (Meeting topic: keystone)"18:04
lbragstadI figured we could use the meeting time to cruise through some specifications together18:04
lbragstadkind of like an expedited group review18:04
hrybacki+118:05
knikollagood idea18:05
lbragstadfirst up18:05
lbragstad#topic Specifications: Unified Limits18:05
*** openstack changes topic to "Specifications: Unified Limits (Meeting topic: keystone)"18:05
lbragstad#link https://review.openstack.org/#/c/455709/ Limits API18:05
lbragstadfresh patch up from this morning18:05
*** yamamoto has quit IRC18:06
lbragstadwxy_: is going to be picking up all that work and has coordinated some of that with sdague18:06
lbragstadkmalloc: about your comment on the delete semantics of a limit18:08
lbragstad#link https://review.openstack.org/#/c/455709/9/specs/keystone/queens/limits-api.rst,unified18:08
lbragstadis that reason enough to have ID for limits?18:08
lbragstad#link https://review.openstack.org/#/c/455709/9/specs/keystone/queens/limits-api.rst,unified@257 specifically18:08
*** aselius has joined #openstack-meeting18:09
kmalloc*shrug*18:09
kmalloci prefer no ids.18:09
kmallocand just use a path18:09
kmallocthe IDs seem.... weird wedge in there18:09
*** Swami has joined #openstack-meeting18:09
kmallocbut i'd support ids if it makes it that much easier18:10
lbragstadahh18:10
edmondswwhy is region in there? Shouldn't that come from your token?18:10
*** thorst has joined #openstack-meeting18:10
kmallocedmondsw: if you have different limits per region.18:10
edmondswoh, nm... region isn't in token18:10
lbragstadso instead of using a DELETE with a request body, just put everything on the path18:10
kmallocyeah18:10
cmurphywe have ids on pretty much anything, the links thing relies on it18:10
knikolla++ on path18:11
kmalloclbragstad: yeah that is how i'd handle it here. id's feel like a wedge. but again, i'd support either18:11
lbragstadid' support everything on the path *or* an ID instead of having a DELETE with a request body18:11
lbragstadi wouldn't want someone to be able to use this because what they are using to front keystone trims the body from a delete request18:12
kmallocDELETE with a request body is the only option that worries me18:12
edmondswwhy are we forcing folks to set region-specific quotas? What if I want a project-specific but not region-specific quota?18:12
lbragstadper RFC 7231 in your comment18:12
kmallocedmondsw: we should support region-specifc but not require it18:12
kmallocedmondsw: or at least region-specific overrides.18:13
lbragstadalso - that's the registered limit18:13
lbragstadwhich is different than a project limit18:13
*** ad_rien_ has joined #openstack-meeting18:13
lbragstadwhich would limit that projects usage in a specific region if i'm understanding thing correctly18:13
lbragstads/thing/things/18:14
*** thorst has quit IRC18:14
*** dtrainor has joined #openstack-meeting18:17
*** yamamoto has joined #openstack-meeting18:18
*** yamamoto has quit IRC18:18
*** dtrainor has quit IRC18:18
*** dtrainor has joined #openstack-meeting18:18
*** sshank has quit IRC18:18
edmondswI meant default project limits18:19
edmondswi.e. registered limits at the project level instead of the region level18:19
edmondswor better said... registered limits that aren't region-specific18:20
lbragstadservices require a region, right?18:21
kmalloclbragstad: uhm...18:21
kmallocmaybe?18:21
kmalloci think endpoints do18:21
kmallocservices afair do not18:21
lbragstadaha18:21
*** mhayden has left #openstack-meeting18:22
kmallocsince the same service def should be used *everywhere*18:22
kmallocbut... lets be fair, i could be wrong. the catalog is.... wonky sometimes18:22
lbragstadwell - regions are apparently optional for endpoints, too18:23
*** yamahata has joined #openstack-meeting18:23
lbragstad#link https://github.com/openstack/keystone/blob/19451a8e350ecf6c09159438c14f6c7d16190bb8/keystone/catalog/schema.py#L9318:23
cmurphyisn't there always a default region?18:23
lbragstadcmurphy: yeah - that's exactly why i thought it was required18:24
lbragstadbecause i thought that same question18:24
knikollano, the default is no region18:24
lbragstadok - so should reqion be optional for limits?18:24
cmurphyno, i mean if no region is specified there is a default that will be the region for that endpoint18:25
cmurphythe default comes from keystone.conf or something18:25
* cmurphy searches18:25
lbragstad#link https://github.com/openstack/keystone/blob/19451a8e350ecf6c09159438c14f6c7d16190bb8/keystone/catalog/core.py#L18018:25
*** jessegler has joined #openstack-meeting18:25
knikollainteresting, i clearly remember creating endpoints and having them be part of no region :/18:26
knikollaand having to specify region explicitly18:26
*** msimonin has joined #openstack-meeting18:26
lbragstad#link https://github.com/openstack/keystone/blob/19451a8e350ecf6c09159438c14f6c7d16190bb8/keystone/catalog/controllers.py#L19218:27
lbragstadthere is some validation for regions, but i don't see one getting set for endpoints if the request doesn't have it18:27
edmondswhttps://github.com/openstack/keystone/blob/19451a8e350ecf6c09159438c14f6c7d16190bb8/keystone/catalog/core.py#L16518:27
edmondsw^ would allow for None as region_id18:27
cmurphyi might be wrong, it might be just that every deployment tool i've ever used has created one18:27
lbragstadyeah - that could be it, too18:28
cmurphyi'm not seeing anything in conf/ for it18:28
lbragstadto me, i'm not sure it makes sense to require region then if it's possible to have a deployment without a region18:28
knikollahttp://paste.openstack.org/show/627621/18:28
cmurphyokay, i was wrong :)18:29
lbragstadi think we'll need to figure that bit out moving forward with that specific spec18:30
*** sshank has joined #openstack-meeting18:30
lbragstadis everyone ok continuing the unified limit stuff in review until next week?18:31
knikolla+118:31
cmurphyyep18:31
lbragstad#topic Specification: Application Credentials18:31
*** openstack changes topic to "Specification: Application Credentials (Meeting topic: keystone)"18:31
lbragstad#link https://review.openstack.org/#/c/512505/ Application credentials18:31
lbragstadthis one has shaped up pretty good in the last week or two18:32
cmurphyohai18:32
lbragstadcmurphy: you and kmalloc were going through some cases about this last night18:32
*** bobh has joined #openstack-meeting18:32
cmurphyplease do read the whole thing and not just the changes, we merged a lot of inconsistencies the last time around because no one read it all the way through18:32
lbragstadsounded like we just needed to elaborate on the interactions with trusts?18:32
cmurphyoh i forgot to add the bit about blocking trust creation18:33
cmurphyother than that it's good to go18:33
lbragstadare role assignment APIs blocked, too?18:33
cmurphywould be good to get eyes from some of the other stakeholders though18:33
cmurphylbragstad: not in this version, i took out the bits about blocking the whole identity api because my thoughts are that non-admin users can't accidentally delegate those rights anyways18:34
cmurphylbragstad: do you think identity apis should be explicitly blocked?18:34
*** thorst has joined #openstack-meeting18:34
cmurphyanyone else feel strongly about that? ^18:35
lbragstadthat's a good question - i think we'll need to block some of them (like trusts) but maybe not all18:35
lbragstadi suppose role assignment things are admin operations currently18:36
cmurphyi think the main concern is preventing self-cloning credentials but i'm otherwise not sure there's a good reason to block anything else18:36
cmurphyright18:36
*** georgk has joined #openstack-meeting18:36
lbragstadi'll read through the whole thing after this meeting18:37
cmurphycool18:37
lbragstadanyone else have anything to discuss with application credentials that needs to be done here?18:37
*** thorst has quit IRC18:37
*** thorst has joined #openstack-meeting18:38
lbragstad#topic Specification: Policy Goals18:38
*** openstack changes topic to "Specification: Policy Goals (Meeting topic: keystone)"18:38
lbragstad#link https://review.openstack.org/#/c/460344/ Policy goals18:38
lbragstadthese have been floating around for a while and i'm curious if they're still useful enough to merge18:38
lbragstadif not, that's totally fine18:38
cmurphyi think they are18:39
* cmurphy will look18:39
lbragstad#link https://review.openstack.org/#/c/462733/ Roadmap for security18:39
lbragstadfalls into the same category18:39
lbragstadthey are pretty general documents that just lay the introduction for what we need to do to improve u-x in those areas18:39
lbragstadthey do have some overlap with what is in trello18:39
lbragstadbut - i figured that is ok since trello is tracking status of all the moving parts18:40
lbragstadlet me know if you have opinions on what we should do with those18:41
hrybackihave to drop, sorry y'all18:41
lbragstadhrybacki: o/18:41
lbragstad#topic Specification: System Scope18:42
*** openstack changes topic to "Specification: System Scope (Meeting topic: keystone)"18:42
lbragstad#link https://review.openstack.org/#/c/464763/ System roles and system scoping18:42
lbragstadso - that merged ^18:42
lbragstadthanks for all the reviews there18:42
lbragstadI do have patches up for the implementation if anyone wants to start reviewing those18:43
lbragstadi'll get the rest rebased and reproposed by Dec. 8th18:43
lbragstadthen i'll go through and formally abandon the global roles stuff18:43
*** adisky_ has quit IRC18:43
lbragstadsince that will no longer be relevant18:43
lbragstad#topic Specification: Project Tags update18:44
*** openstack changes topic to "Specification: Project Tags update (Meeting topic: keystone)"18:44
lbragstad#link https://review.openstack.org/#/c/508339/ Project tags update18:44
lbragstadi must have put this on the schedule before it merged18:44
lbragstadso - that happened :018:44
lbragstad#topic Open Discussion18:44
*** openstack changes topic to "Open Discussion (Meeting topic: keystone)"18:44
gagehugo\o/18:44
lbragstadfloor is open if folks have things they want to talk about18:44
*** jamesmcarthur has quit IRC18:45
lbragstadcool - looks like we can get some time back before office hours18:46
lbragstadthanks for working through the specs18:46
lbragstadwe should be in good shape by next week!18:46
*** unicell has joined #openstack-meeting18:47
cmurphy\o/18:47
lbragstad#endmeeting18:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:47
openstackMeeting ended Tue Nov 28 18:47:19 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-11-28-18.00.html18:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-11-28-18.00.txt18:47
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-11-28-18.00.log.html18:47
*** dtrainor has quit IRC18:47
*** gagehugo has left #openstack-meeting18:47
*** spilla has left #openstack-meeting18:48
*** tobiash has joined #openstack-meeting18:55
*** dtrainor has joined #openstack-meeting18:59
clarkb#startmeeting infra19:00
openstackMeeting started Tue Nov 28 19:00:32 2017 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: infra)"19:00
openstackThe meeting name has been set to 'infra'19:00
clarkbhello, who is here for the infra meeting?19:00
fricklero/19:00
tobiasho/19:00
ianwo/19:01
clarkb#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:01
clarkbThere are a couple items on the agenda. Jeblair will be joining us late so I think we will do zuulv3 after the general topics list19:02
clarkb#topic Announcements19:02
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:02
clarkbits been a quiet week with the US thanksgiving holiday, I'm not aware of anything that needs announcing19:03
clarkbis there something I've missed?19:03
*** jamesmcarthur has joined #openstack-meeting19:03
fungii guess the venue for the ptg hasn't been officially announced yet19:03
*** Shrews has joined #openstack-meeting19:03
fungiso maybe flag that to announce in next week's meeting if it has been by then19:03
* clarkb scribbles a note19:04
diablo_rojo_phonIt should be announced by this afternoon.19:04
clarkbin that case look to read the openstack-dev mailing list later today for an announcement on the ptg location :)19:04
*** AJaeger has joined #openstack-meeting19:04
AJaegero/19:04
pabelangero/19:04
clarkb#topic Actions from last meeting19:04
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:04
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-11-21-19.01.txt Minutes from last meeting19:05
*** janki has quit IRC19:05
clarkbFungi's action to write the secrets backups doc is complete \o/19:05
*** bobh has quit IRC19:05
fungioh, that was complete last week19:05
fungii think i linked it during the meeting then19:05
clarkbya it ended up in the actions list but now is done so we can keep it out19:06
fungimaybe it hadn't merged yet at that point19:06
clarkbI'm not aware of any specs that need review or otherwise need to be brought up and will skip zuulv3 for now so that jeblair can join us which means straight ot general topics19:06
clarkb#topic General topics19:07
*** openstack changes topic to "General topics (Meeting topic: infra)"19:07
clarkb#topic Zanata 4 upgrade19:07
*** openstack changes topic to "Zanata 4 upgrade (Meeting topic: infra)"19:07
clarkb#link https://review.openstack.org/#/c/506795/ initial change needed for zanata upgrade work19:07
clarkbwe are seeing some of the initial changes come in that will allow us to upgrade from zanata 3 to zanata 4. I think the i18n team would like to see this get done before the string freeze which is late january.19:07
*** jamesmcarthur has quit IRC19:07
*** jessegler has quit IRC19:08
clarkbit would be great if we can help make that possible (code reviews, actually merging code/running upgrades)19:08
jeblairo/19:08
clarkbI did the last one so am fairly familiar with the service, is anyone else interested in learning about the java/wildfly/zanata things? If so let me know and we can work to help get this going with the i18n team19:08
*** msimonin has quit IRC19:09
ianwi have a passing familiarity from the last upgrade, and i think we're in similar tz's, so put me down to help19:09
*** msimonin has joined #openstack-meeting19:09
clarkbianw: awesome thanks19:09
clarkbI expect it will be mostly straightfroward after talking to aeng, no need for a java update or distro upgrade19:09
*** msimonin has quit IRC19:09
*** msimonin has joined #openstack-meeting19:10
fungiunlike, say, the next gerrit upgrade19:10
ianwi'll start by reviewing ^^ :)19:10
pabelangerfungi: +119:10
*** msimonin has quit IRC19:10
*** msimonin has joined #openstack-meeting19:10
*** msimonin has quit IRC19:11
clarkb#topic Priority Efforts19:11
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:11
*** msimonin has joined #openstack-meeting19:11
clarkbjeblair: is here, on to zuul19:11
clarkb#topic Zuul v319:11
*** openstack changes topic to "Zuul v3 (Meeting topic: infra)"19:11
clarkbI wanted to do a quick recap of the zuul cloner venv removal because there were some hiccups with it and want to amke sure we don't forget to do the last cleanups19:12
*** msimonin has quit IRC19:12
*** msimonin has joined #openstack-meeting19:12
clarkbpabelanger: ^ I think the fixes for the pyyaml install have gone in job side, have we remvoed it from the image again?19:12
pabelangerclarkb: we have!19:12
*** msimonin has quit IRC19:13
pabelangerI think we are ready to actually move to https://review.openstack.org/513506/ now, which removes zuul-cloner from base jobs19:13
*** msimonin has joined #openstack-meeting19:13
*** rtjure has joined #openstack-meeting19:13
*** sridharg has quit IRC19:13
*** KwozyMan_ has joined #openstack-meeting19:13
clarkb#link https://review.openstack.org/513506/ remove z-c shim from base job is ready for review now19:13
*** msimonin has quit IRC19:13
pabelangerfor 513506, we'll need to be ready to fix jobs that are broken by it, and re-parent them to legacy-base19:14
clarkbfungi: I think we basically agreed to remove jenkins from the ci group in gerrit last week as well. Did that happen yet?19:14
pabelangeras we expect native zuulv3 jobs 1) not to use zuul-cloner, 2) parent to base19:14
fungiit has not, but i can do it now19:14
pabelangerfungi: +119:15
fungi10 seconds ;)19:15
clarkbworks for me and is an easy revert if we need to19:15
*** KwozyMan has quit IRC19:15
fungiokay, that was more than 10 seconds, but done now19:16
clarkbfrickler: tristanC have a third party CI of zuul-jobs agenda item19:16
fungii had to remember the group name because i forgot i'd linked it from the agenda19:16
clarkbI don't think tristanC is here, but frickler is. Want to fill us in?19:16
fricklerI'm not directly related to the CI19:16
jeblairsomehow i missed that email19:16
fungi#info The retired "Jenkins" account has been removed from the Continuous Integration Tools group in Gerrit now19:16
jeblairbut i've read it now.  and i support the concept in general19:16
fricklerbut I wanted to make sure that tristan gets more feedback on his mail19:17
jeblairthough i was about to send back a reply suggesting that we just use 'recheck' for the recheck command19:17
*** salv-orlando has joined #openstack-meeting19:17
fungi#action fungi send an announcement about the removal of Jenkins from Continuous Integration Tools19:17
fungii'll do that after the meeting19:17
clarkbfungi: thanks19:17
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2017-November/005688.html for details on third party CI for zuul-jobs19:17
jeblairi've long advocated that third-party cis should not have their own recheck command language19:18
*** yamamoto has joined #openstack-meeting19:18
jeblairi don't think it should be a problem for this repo19:18
*** rtjure has quit IRC19:18
clarkbagreed. I think the other considering to make is whether or not we want it to +1, +/-1, -1 or just +0 with logs19:19
clarkb*other consideration19:19
*** oidgar has quit IRC19:20
jeblairi'm happy to try out voting if other folks are19:20
*** claudiub|2 has quit IRC19:20
clarkbI think voting helps get more eyeballs on the problem and not allowing voting makes it easier to ignore the failures. So I am happy to try voting as well19:20
*** dmsimard has joined #openstack-meeting19:21
tobiash++voting19:21
dmsimardhi19:21
dmsimardsorry, forgot to fix calendar event timezone..19:21
fungii have no objection to voting third-party ci systems as long as their feedback is reliable19:21
pabelangeryah, I think we can give voting a try19:21
dmsimardI don't have backlog to get context, but yes, we (RDO/Software Factory) would like to be third party CI against zuul-jobs. I don't know what shape this will take yet.19:22
tobiashthe same applies for me19:22
jeblairdmsimard: current context is software-factory third-party ci: http://lists.openstack.org/pipermail/openstack-infra/2017-November/005688.html19:23
clarkbdmsimard: basically jeblair has asked that we not have any special recheck syntax, just support 'recheck' like upstream zuul. And we seem to be comfortable to try it out in a voting manner (so we'll need to update gerrit ACLs)19:23
jeblairwhich i somehow missed over thankgiving19:23
*** jamesmcarthur has joined #openstack-meeting19:23
dmsimardUltimately, one of the objectives is to leverage TripleO(-ci) jobs, roles, and playbooks from within review.rdoproject.org which is anologous to review.openstack.org, so it will be very important for us to be able to re-use zuul-jobs (and potentially other things, but that's another topic) outside of OpenStack19:23
dmsimardI'd start with non-voting first to get some confidence that we're doing the right thing19:24
jeblairwfm19:24
jeblairthat's the usual approach i believe19:25
fungijust to pile on, i agree wrt standardizing on "recheck" across ci systems. rechecking individual ci systems is moderately dangerous for the same reasons we've resisted requests to recheck individual jobs19:25
clarkbdmsimard: thats fine, just wnted to bring up possible voting early as a lot of projects don't allow it at all and wasn't sure were we stood on that19:25
clarkbso as to avoid surprises later if there were major disagreements :)19:25
*** electrofelix has quit IRC19:25
dmsimardclarkb: well, it's not clear to me yet what these third party jobs will look like yet19:25
dmsimardclarkb: i.e, will it be running base-integration/multinode-integration but just from another zuul for example ?19:26
fungialso, to be clear on the third-party ci situation, we've also said in the past that we'll disable accounts for any ci systems which start reporting on infra team repo changes without prior discussion19:26
dmsimardI feel like there's stuff we'll realize once we get started19:26
tobiashdmsimard: it could be running your most important jobs19:26
mmedvedeI would object to not allowing third-party CIs have their own recheck syntax, sometimes we want to only nudge our third-party CI when there is an obvious problem with it without wasting upstream CI's resources19:27
jeblairmy thought is not to be too prescriptive about what they're doing.  we should have ongoing conversations with third-party ci operators to make sure we're making the most of things, but in general, third-party operators are probably best placed to decide what's important to them and what unique things they can bring to the table.19:27
*** rcarrillocruz has joined #openstack-meeting19:27
* rcarrillocruz waves19:27
fungimmedvede: "zuul enqueue" via the rpc in that case19:27
*** jamesmcarthur has quit IRC19:27
dmsimardtobiash: it depends, what's the purpose or the use case ? I don't think running a tripleo-based job against zuul-jobs is necessarily worthwhile -- we're interested in testing the roles individually19:28
*** yamamoto has quit IRC19:28
mmedvedefungi: I thought we are not encouraged to comment on the same patch twice without an explicit recheck19:28
clarkbdmsimard: but ya sounds like you can go ahead and start trying things out in a non voting capacity, may even want to start in a non reporting manner first. See how that goes then tweak from there19:28
fungimmedvede: that might be a policy some team has put into place, but it's not our policy afaik19:28
jeblairmmedvede: there is nothing about that in https://docs.openstack.org/infra/system-config/third_party.html#requirements19:28
tobiashdmsimard: yes, that probably depends on what's important to you as zuul-jobs user19:28
dmsimardmmedvede, fungi, jeblair: unless mistaken, the recheck keyword is controlled by the third party CI so there's nothing preventing operators from responding to "recheck" and "check myzuulname"19:29
jeblairmmedvede: there is a note in there saying that "recheck" should retrigger all systems.19:29
fungimmedvede: we're specifically talking about third-party ci systems which want to vote on changes to the openstack-infra/zuul-jobs repo (and potentially other deliverables of the infra team in the future)19:29
jeblairdmsimard: nothing except their willingness to abide by the guidelines we've established19:29
pabelangerwait, I thought we said recheck foo was good a while back. I feel like we go back and forth on this every few months19:29
jeblairfungi: indeed, let's not get too far derailed on this :)19:29
dmsimardjeblair: the important part is that they answer to "recheck", right ? if they answer to "check foo" is that an issue ?19:29
jeblairpabelanger: i have never said that.19:29
pabelangerjeblair: other infro-root have, IIRC19:30
jeblairdmsimard: we don't have an established policy on that.  i would like to, in the context of zuul-jobs only, establish a policy that we don't do that and all systems honor recheck.19:30
jeblaironly.19:30
*** priteau has quit IRC19:30
dmsimardjeblair: that's fine, on our end that means setting up a separate pipeline (because we already have a pipeline meant for third party) but that's not expensive19:31
jeblairdmsimard: (or, if it happens to honor something else, just don't mention it)19:31
dmsimardsure19:31
fungidmsimard: "our" in this context being rdo ci?19:32
dmsimardfungi: yeah, RDO's zuul answers to things like "check rdo experimental" (so we don't trigger "check experimental")19:32
dmsimardand possibly other things19:32
*** jamesmcarthur has joined #openstack-meeting19:32
mmedvedejeblair dmsimard : agree recheck should absolutely retrigger all the CI systems. But this does not exclude ability for third-party CIs to also be triggered separately. I would like there to be an official blessed syntax for this. Right now each CI comes up with their own19:33
fungii'm curious why someone would want upstream experimental pipeline results but not rdo's experimental pipeline results. still, that's not crucial to this topic19:33
clarkbya, I think we may be starting to get into another topic entirely19:33
clarkbwe can come back to that if there are no other zuulv3 items or finish them19:33
*** ijw has quit IRC19:33
clarkbI think we may want to talk about the merging of branches though that wasn't on the agenda. Any other zuulv3 items?19:34
dmsimardI have something19:34
fungimmedvede: part of the resistance, historically, is that we feel leaving comments in the code review system is a bad api anyway, and would like to eventually have some other interface fro such tasks19:34
fungiand not tie ourselves to a standard involving arbitrary code review comment strings19:35
*** MrJoshua has joined #openstack-meeting19:35
clarkbdmsimard: what was your zuulv3 item?19:35
dmsimardI'd love at least a first round of reviews on the 'sqlite over http' ara middleware series to 1) always have ara reports regardless of failure/success 2) reduce even further the impact of storage/inode on the log server19:36
dmsimardThe reviews are tagged here: https://review.openstack.org/#/q/topic:ara-sqlite-middleware19:36
dmsimardAnd you can see a practical implementation here --19:36
clarkbdmsimard: does that also depend on getting the ara install updated independent of the zuul install on the zuul executors?19:37
dmsimardWithout the middleware: https://logs.rdoproject.org/33/10433/1/check/rdo-registry-integration/Ze74352b77e17444cace463fc9c994213/ara-database/19:37
dmsimardWith the middleware: http://logs-dev.rdoproject.org/33/10433/1/check/rdo-registry-integration/Ze74352b77e17444cace463fc9c994213/ara-database/19:37
*** sdague has quit IRC19:37
pabelangerSSL cert is bad ^19:37
dmsimardpabelanger: yeah, logs-dev :(19:37
jeblair(i replied to the ml thread with a summary of our discussion on the third-party ci issue)19:37
dmsimardpabelanger: I spun it up without getting proper certs (yet)19:37
dmsimardclarkb: it doesn't depend on the version of ara on the executors, no19:38
clarkbdmsimard: cool, so we can work this independently. I'll make a note to review it19:38
*** links has joined #openstack-meeting19:38
dmsimardclarkb: it doesn't even depend on the version of ara on the logserver (where it would sit like htmlify/os-log_analyzer), it's just a wsgi script that happens to be bundled in ara at the latest version but otherwise can be carried in tree19:39
pabelangerDidn't we have a set of patchs to install it onto our own dev server?19:39
pabelangerlogs-dev.o.o for example19:39
dmsimardthat's the topic I linked earlier, yes: https://review.openstack.org/#/q/topic:ara-sqlite-middleware19:39
pabelangerokay cool19:39
clarkb#link https://review.openstack.org/#/q/topic:ara-sqlite-middleware changes to run ara out of sqlite db using middleware. Will cut down on inode use on the logs server hopefully allowing us to add ara to successful jobs again19:39
pabelangerwill look over here today19:40
dmsimardI have a todo to resolve a conflict between htmlify and ara rewrite rules but it's otherwise at least ready for reviewing19:40
dmsimardI -W one of the patches but it's still worth reviewing :)(19:40
*** qwebirc13003 has joined #openstack-meeting19:40
dmsimardI'll probably go ahead and rebase the stack since it's been a while19:41
dmsimardthat was it for my topic :)19:41
*** qwebirc13003 has left #openstack-meeting19:41
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2017-November/005695.html ml thread on merging feature branches back into master on nodepool and zuul repos and shifting dev work to those branches19:41
clarkbIf you haven't seen it yet and are interested in zuul ^ is probably worth a read19:41
clarkbjeblair: anything you want to add to ^ here?19:42
*** links has quit IRC19:42
jeblairya19:42
jeblairi'd love for someone from the third-party-ci community to jump in on the puppet-openstackci work19:43
*** msimonin has joined #openstack-meeting19:43
jeblairthat is something that should be straightforward to accomplish and doesn't require any zuulv3 knowledge -- the opposite in fact -- it's work to keep zuulv2 working with puppet-openstackci19:43
dmsimardthere's an irc channel where they hang out, worth a try to get their attention19:43
jeblairtrue, though there's a problem if they aren't paying attention here.19:43
clarkbmmedvede may also know individuals that might be interested?19:43
dmsimardthey might not be subscribed to the MLs19:44
AJaegerwe also have project-config-example repo - what should we do with that one? It uses Zuul v2/Jenkins right now19:44
jeblairagain, if they aren't subscribed to openstack-infra it's a problem.  i will send an announcement to third-party-announce to draw attention to my post, however.19:45
mmedvedeclarkb: it has been relatively quiet, lennyb fyi ^^19:45
clarkbjeblair: thanks19:45
*** ssathaye has quit IRC19:45
*** ssathaye has joined #openstack-meeting19:46
fungiAJaeger: good question... i wonder whether it needs branching or can have v2 and v3 content side-by-side19:47
clarkbok any other zuulv3 items before we move on to open discussion?19:47
fungithat's in my opinion part of eth puppet-openstackci work to determine19:48
AJaegerfungi: and somebody would need to update it. Question is whether anybody is using it at all...19:48
jeblairAJaeger, fungi: can likely support side-by-side as we did during our transition.19:48
fungiconvenient19:48
jeblairthough should probably just switch to v3 soon.19:48
mmedvedeclarkb: I'll take a look at puppet-openstackci for zuulv3 branch merge workarounds19:48
*** msimonin1 has joined #openstack-meeting19:48
clarkbmmedvede: thanks19:49
clarkbjeblair: ^ sounds like you may have a volunteer?19:49
jeblair\o/19:49
fungimmedvede: feel free to delegate/distribute the load to any other interested 3rd-party ci ops who show interest too19:49
fungithough hopefully the work involved is relatively minimal19:49
mmedvedethis is my hope :)19:50
jeblair++19:50
fungibut getting some of them to help test it out may make sense19:50
clarkbya I think having third party ci involved just for ^ is worthwhile19:50
clarkbeven if they aren't able to actively review the changes or write them19:50
pabelangermost of the work is going to be moving our zuulv3 stuff from system-config back into puppet-openstackci19:50
*** msimonin has quit IRC19:50
mordredpabelanger: ++19:51
clarkb#topic open discussion19:53
*** openstack changes topic to "open discussion (Meeting topic: infra)"19:53
*** gouthamr_ has joined #openstack-meeting19:53
clarkbAs a general heads up with the firefighting largely behind us I'd like to start organizing the infra TODO list. Basicalyl something that shows new and old infra folk what work is happening and where they can help out if they have spare cycles19:54
*** bobh has joined #openstack-meeting19:54
clarkbYou'll probably see me ask for eyeballs on a storyboard board in the near future19:54
* mordred is back to not being able to login to storyboard, fwiw19:54
clarkbfun19:54
pabelangerI still need to send out ML post about xenial upgrades, I'll try to get that out later today19:54
AJaegerthe Zuul v3 migration issue etherpad has still some items, could we all review it over the next days, please?19:55
clarkbAJaeger: ++19:55
*** gouthamr has quit IRC19:56
mordred++19:56
*** tlaxkit has joined #openstack-meeting19:57
dmsimardon an openfloor note, unbound reviews are up to try and see if this helps with our ongoing DNS resolution failures: https://review.openstack.org/#/q/topic:unbound-ttl19:58
dmsimardshould be good to go in, they're set to not change anything and effectively be no-op so that we can try it selectively in some jobs.19:58
clarkbdmsimard: is that something we might want to try in a limited fashion on the jobs affected by the problem?19:58
dmsimardclarkb: that's exactly the purpose, yes, we're actually not changing the defaults from unbound, but jobs can specify vars for cache-min-ttl and it'll be configured accordingly19:59
clarkbgotcah sounds good19:59
*** bobh has quit IRC19:59
clarkbalright that is all the time we have, find us in #openstack-infra or on the infra mailing list. Thanks everyone20:00
clarkb#endmeeting20:00
pabelangerclarkb: dmsimard: I would also be worth discussion the possible impact to troubleshooting with jobs running different DNS settings. until now, we've tried to keep everything the same across all jobs20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Nov 28 20:00:12 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-11-28-19.00.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-11-28-19.00.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-11-28-19.00.log.html20:00
*** AJaeger has left #openstack-meeting20:00
dmsimardpabelanger: let's follow up in #openstack-infra20:00
*** amodi has joined #openstack-meeting20:01
fungireminder: there is no formal tc meeting this week, but we'll have our second office hour of the week starting in roughly 5 hours (01:00 utc) in the #openstack-tc channel if anyone's interested in participating20:02
*** jamesmcarthur has quit IRC20:03
*** e0ne has quit IRC20:03
*** jamesmcarthur has joined #openstack-meeting20:04
*** sshank has quit IRC20:06
*** oidgar has joined #openstack-meeting20:07
*** bobh has joined #openstack-meeting20:09
*** bobh has quit IRC20:14
*** lpetrut has joined #openstack-meeting20:14
*** eharney has quit IRC20:19
*** bobh has joined #openstack-meeting20:20
*** raildo has quit IRC20:21
*** pcaruana has joined #openstack-meeting20:21
*** markstur has quit IRC20:24
*** bobh has quit IRC20:26
*** iyamahat has joined #openstack-meeting20:26
*** bobh has joined #openstack-meeting20:26
*** esberglu has quit IRC20:27
*** nijaba has joined #openstack-meeting20:28
*** nijaba has quit IRC20:28
*** nijaba has joined #openstack-meeting20:28
*** msimonin has joined #openstack-meeting20:28
*** msimonin1 has quit IRC20:30
*** bobh has quit IRC20:32
*** awaugama has quit IRC20:33
*** KwozyMan_ has quit IRC20:34
*** bobh has joined #openstack-meeting20:38
*** jamesmcarthur has quit IRC20:38
*** jamesmcarthur has joined #openstack-meeting20:40
*** esberglu has joined #openstack-meeting20:40
*** bobh has quit IRC20:43
*** piyanai has joined #openstack-meeting20:48
*** priteau has joined #openstack-meeting20:50
*** edmondsw_ has joined #openstack-meeting20:52
*** bobh has joined #openstack-meeting20:53
*** epei has joined #openstack-meeting20:55
*** edmondsw has quit IRC20:56
*** dprince has quit IRC20:57
*** oneswig has joined #openstack-meeting20:58
*** bobh has quit IRC20:58
oneswig#startmeeting scientific-sig21:00
openstackMeeting started Tue Nov 28 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-sig)"21:00
openstackThe meeting name has been set to 'scientific_sig'21:00
oneswigHellooo21:00
*** leong has joined #openstack-meeting21:00
leongo/21:00
oneswig#link agenda for today https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_November_28th_201721:00
leongI am Leong from Intel21:01
oneswigHi leong, thanks for coming21:01
*** oidgar has quit IRC21:01
*** rajulk has joined #openstack-meeting21:01
*** bobh has joined #openstack-meeting21:01
leongoneswig: will try my best to join more often..:-)21:01
piyanaiHello, This is Piyanai from the MOC21:01
*** Leom has joined #openstack-meeting21:01
oneswigThat'd be great...21:01
piyanaiRajul will also be joining in couple minutes21:01
*** Chris___ has joined #openstack-meeting21:01
oneswigHi piyanai, thanks for joining21:01
*** b1airo has joined #openstack-meeting21:01
*** Chris___ has quit IRC21:01
*** isunil has joined #openstack-meeting21:02
epeiHey, I am Erming from Compute Canada Cloud team21:02
oneswigHi epei, welcome21:02
b1airoMorning21:02
epeioneswig: thanks21:02
oneswigg'day b1airo21:02
oneswig#chair b1airo21:02
openstackCurrent chairs: b1airo oneswig21:02
isunilHello. This is Sunil from Intel.21:03
oneswigHi isunil, thanks for coming21:03
*** thorst has quit IRC21:03
oneswigShall we get started21:03
oneswigb1airo: we are expecting martial today, right?21:03
rajulkHi! this is rajul from MOC21:03
oneswigHello rajulk, thanks for coming21:04
verdurinEvening.21:04
b1airoI think so, should be his TZ21:04
*** Chris___ has joined #openstack-meeting21:04
oneswigHi verdurin21:04
*** diablo_rojo has quit IRC21:04
oneswigok, lets get the show on the road21:04
oneswig#topic ostack-hpc / hpc-cloud-toolkit21:04
*** openstack changes topic to "ostack-hpc / hpc-cloud-toolkit (Meeting topic: scientific-sig)"21:04
*** Chris___ is now known as Chris_MonashUni21:05
oneswigleong: isunil: would you like to describe your project first?21:05
leongok21:05
leongsur21:05
leong#link HPC Cloud Toolkit: https://github.com/hpc-cloud-toolkit/ostack-hpc21:05
leongthis is the hpc cloud toolkit that Intel HPC team is working on the past few monhts21:05
leongwe are now open-sourcing the solution21:05
*** bobh has quit IRC21:06
isunilThis is a recipe to create HPC in a cloud, leveraging OpenHPC21:06
isunilOpenHPC components21:06
oneswigEverything from OpenHPC?21:06
isunilthanks Leong21:06
leongyup.. basiclly integrating OpenHPC with OpenStack (Ironic specifically)21:06
leongcombining the both open-source tooling for HPC community21:06
oneswighow does openstack integrate with beowulf/warewulf - or just replace the infra management components?21:07
isunilwarewulf is not used here.21:07
isunilit is replaced with ironic21:07
leongoneswig: for now, it is mainly the infra managment21:07
oneswigsounds good.21:07
*** msimonin has quit IRC21:07
*** msimonin has joined #openstack-meeting21:07
oneswigCan you describe the process you're using?21:07
leongusing ironic to provision the "hpc-head" and "hpc-compute" node21:07
leongthere are generally 3 phase21:08
*** Alex_Staf has joined #openstack-meeting21:08
*** flanders_ has joined #openstack-meeting21:08
leongphase 1: using disk-image-buider to build the HPC related images21:08
*** msimonin has quit IRC21:08
*** msimonin has joined #openstack-meeting21:08
leongphase 2: using ironic to deploy the physical nodes for HPC Head/Compute21:08
leongphase 3: provision/configure the OpenHPC on the nodes in phase 221:08
*** msimonin has quit IRC21:09
*** trandles has joined #openstack-meeting21:09
oneswigThat's ansible-driven configuration in phase 3?21:09
*** msimonin has joined #openstack-meeting21:09
*** sshank has joined #openstack-meeting21:09
leongthis simplify and make the deployment of HPC cluster easier in the cloud21:09
isunilno ansible so far21:09
leongright now, in phase 3, it is more on a cloud-init script21:09
trandleshi folks...sorry, my calendar didn't update with the time change :(21:09
piyanaiHow tightly does the implementation with Ironic?21:09
*** msimonin has quit IRC21:09
leongansible playbook can be consider for future releases (depending on community needs)21:10
*** msimonin has joined #openstack-meeting21:10
Chris_MonashUniAny global storage associated with the cluster?21:10
*** bobh has joined #openstack-meeting21:10
leongthis is the initial POC/prototype, there is no "global storage" associated with the cluster recipe now21:10
*** msimonin has quit IRC21:10
*** msimonin has joined #openstack-meeting21:10
leongbut we are looking into Lustre21:11
isunilwe are envisioning to have Luster as a service.21:11
b1airoWhat special HPC things is OpenHPC helping us with?21:11
*** msimonin has quit IRC21:11
*** msimonin has joined #openstack-meeting21:11
oneswigleong: We use CephFS and have developed early Manila integration for that.21:11
leongpiyanai: we uses Ironic to provision the baremetal host, depending on your perspective, i would said it is loosely21:11
oneswigisunil: would be interesting to see ansible playbooks for lustre-as-a-service.21:12
*** msimonin has quit IRC21:12
*** msimonin has joined #openstack-meeting21:12
leongoneswig: is CephFS going to be widely adopted by HPC communty?21:12
b1airoleong: too early to say, but it has a lot of interest and traction21:13
leongoneswig: we are wondering if Manila can be integrated with Lustre?21:13
piyanaiGreat, so if I have another “ironic” like software, I should be able to do a plug-and-play replacing Ironic easily…21:13
Chris_MonashUnidoes "lustre-as-a-service" mean building OSS's via nova and provisioning to your provider network, or having an existing luster setup that becomes accessible (driven by Manila)21:13
*** msimonin has quit IRC21:13
isunilOpenHPC brings with all tested,  libraries, integrated components with it. all HPC environment installing HPC libraries on head node and sharing libraries and path with compute node via NFS21:13
oneswigleong: CephFS is not particularly performant in a parallel use case, we are using it a bit like NFS - home directories basically.21:13
leongpiyanai: by theory it is.. however, the recipe now is integrated in an OpenStack environment21:13
*** reed has quit IRC21:14
*** reed has joined #openstack-meeting21:14
Chris_MonashUni@oneswig, isn't home directories the worst place for something like CephFS?21:14
oneswigleong: lustre integration with Manila - could be possible but requires kernel patches for lnet doesn't it?21:14
b1airoisunil: can you describe the testing a little more - that sounds like a good motivation for using it21:14
leongfrom our perspective, we are wondering if that toolkit can be "integrated" in the OpenStack community (for example, creating a HPC project)21:14
oneswigChris_MonashUni: not yet.  It turns out scratch space is worse21:14
oneswigfor us... parallel file opens not good21:15
*** sgrasley1 has quit IRC21:15
*** awaugama has joined #openstack-meeting21:15
*** bobh has quit IRC21:15
priteauleong: Is the system designed to use Ironic to deploy head and compute nodes once by request of an admin, or do you allow HPC users to deploy their own environments regularly?21:15
leongoneswig: might be, not sure yet, we haven't deep dive into that path21:15
oneswigChris_MonashUni: but jewel's CephFS - not good for anything that does fsync (eg, vim) - you've definitely got a point21:16
isunilb1airo: OpenHPC maintains integrated test suites, for every library, application they have21:16
isunilafter provisioning HPC, we run OpenHPC integration test suites to verify all functionality21:17
oneswigleong: isunil: you've mentioned lustre integration, what other plans do you have?21:17
leongpriteau: the toolkit was testing based on a request from admin, this can also allow HPC users to deploy their own21:17
b1airoleong: OpenStack community integration is an interesting idea for sure21:17
*** armax has quit IRC21:17
*** msimonin has joined #openstack-meeting21:17
oneswigleong: just saw your comment up there - aha, elaborate on that?21:17
leongoneswig: OmniPath :-)21:17
*** sgrasley1 has joined #openstack-meeting21:17
b1airopriteau: if I understand correctly then OpenHPC is just a tenant of the cloud, so users of the HPC are necessarily aware of the cloud infrastructure underneath21:18
oneswigIntel Inside, eh? :-)21:18
leongoneswig: you mean the HPC users deployment?21:18
priteaub1airo: you mean "not necessarily aware"?21:18
oneswigthe community part - leong how would that be done?21:19
b1airoYes!21:19
isuniloneswig: OpenHPC is community maintained "A linux foundation"21:19
oneswigisunil: will the ostack-hpc project become part of that?21:19
leongoneswig: the community part.. ok... that's the thing i want to discuss in this Scientific SIG21:19
oneswigleong: you've got ~2 minutes :-)21:20
isuniloneswig: we were hoping for that..21:20
leongi am not sure if this is feasible to create a "HPC project", something like "DBaaS Trove"21:20
*** diablo_rojo has joined #openstack-meeting21:20
leongso eventually this can provide a "HPC catalog" services that based on OpenHPC and OpenStack21:21
b1airoCan't see why not21:21
epeileong: Can we combine step 2 and 3 - Make a comprehensive image that contains what you want to do in #3?21:21
*** gouthamr_ is now known as gouthamr21:21
oneswigleong: ironic, heat and ansible galaxy would be a great toolbag for this21:21
*** pcaruana has quit IRC21:21
leongoneswig: yes21:21
leongepei: we kind of want to split it so that it is more flexible21:22
leongepei: so step 3 potentially can be done with either heat, cloud-init, ansible, etc21:22
epeileong: I see. thanks21:22
oneswigleong: epei: generally there's parameters to configure with here too.21:23
leongwhat do you guys think about the idea of "HPC project"?21:23
epeileong: On the other hand, the head and compute nodes are different.21:23
leongeventually this can add on others like Lustre21:23
rajulkleong: just curoious..waht will this "HPC catalog" offer....template to integrate various openstack serivces for HPC?21:23
oneswigleong: I think it is a good idea but I am not sure if something like Senlin is the way to do it.21:23
piyanaiAny statistic that can be shaerd?21:23
piyanaideployment time for example?21:23
*** bobh has joined #openstack-meeting21:24
piyanaiOr is it still too early for that?21:24
oneswigleong: isunil: have you had any interest from OpenHPC for this work/21:24
leongoneswig: wasn't sure too much on senline21:24
Chris_MonashUnileong: I'd be careful about labeling it as HPC, more like batch scheduler. to achieve the H, you need magic hardware integration21:24
oneswigleong: so an HPC project might not get the mindshare if it was created in that form.  Where to get the best focus on it?21:25
leongChris_MonashUni: you are right, the HPC Project will specifically focusing on hardware integration and HPC software enabling21:25
oneswigChris_MonashUni: very true, totally agree21:25
isuniloneswig: I noticed some interest from OpenHPC community, In past there were one request to OpenHPC to support OpenStack.. they are looking for a recipe to create images and provision...21:25
rajulkChris_MonashUni: +121:25
*** jamesmcarthur has quit IRC21:25
*** jamesmcarthur has joined #openstack-meeting21:26
leongthis is still at an early stage discussion, i am hoping to get more feedback/opinions from the community21:26
oneswigWe create something similar using https://github.com/stackhpc/stackhpc-image-elements/tree/master/elements/openhpc for elements, https://galaxy.ansible.com/stackhpc/cluster-infra/ for heat and https://github.com/SKA-ScienceDataProcessor/p3-appliances for stage 3 - there has to be some common ground21:27
Chris_MonashUniOne nice integration down the line might be application credentials to allow the cluster to access the Openstack users objectstorage21:27
*** edmondsw_ is now known as edmondsw21:27
oneswigChris_MonashUni: ever used barbican for storing cephx keys, monasca credentials etc?21:27
leongChris_MonashUni: +121:27
oneswigSeems to work well for project-level secrets21:27
*** VW has quit IRC21:27
Chris_MonashUnino, I haven't used babrican, but keep meaning to look at it ;-)21:28
*** jamesmcarthur has quit IRC21:28
Chris_MonashUniit does sound appropriate21:28
*** VW has joined #openstack-meeting21:28
oneswigChris_MonashUni: I have an ansible plugin for getting secrets from barbican and setting them as facts21:28
Chris_MonashUnithat sounds fun, care to share?21:28
*** bobh has quit IRC21:29
oneswigChris_MonashUni: try this: https://github.com/SKA-ScienceDataProcessor/p3-appliances/tree/master/ansible/roles/alaska_secrets/library21:29
*** sboyron has quit IRC21:30
oneswigI welcome your PRs to it :-)21:30
*** VW has quit IRC21:30
Chris_MonashUninoice. I might move our team to putting all their stuff in babrican with that ;-)21:30
*** thorst has joined #openstack-meeting21:30
oneswigVault is good but this could be more dynamic21:30
leonganymore questions for the HPC Cloud Toolkit?21:30
*** sboyron has joined #openstack-meeting21:31
oneswigleong: could you make something happen with scientific sig support?21:31
Chris_MonashUni@leong so you spin up a slurmdbd and mysql backend to store accounting info or just throw it away?21:31
leongoneswig: what do you mean "scientific sig support"?21:31
Chris_MonashUnis/so/do/21:31
oneswigChris_MonashUni: trade you a playbook for your slurm backend!21:31
Chris_MonashUnihaha, OK21:32
*** rcernin has quit IRC21:33
oneswigWe should move on - MOC team, you ready?21:33
piyanaiAs ready as can be :)21:33
oneswig#link Slurm at Massachusetts Open Cloud21:33
leongChris_MonashUni: in this POC, it doesn't persist21:33
oneswigTake it away piyanai21:33
piyanaiRajul21:33
piyanaiwould you like to start?21:34
piyanaiWill jump in as needed21:34
rajulkpiyanai: sure21:34
rajulkthe main idea of this poc(as yet ) is to use the underutilized cloud resources for scientific computing21:34
rajulkso this scales an already exisitng slurm cluster over virtual machines as and when resources are avialable21:35
rajulkscaling is driven by Openstack watcher. we added a strategy to look for resource utilization from openstack monasca and then scale the cluster if the utilization is low21:37
piyanaiWe use OpenStack Watcher to monitor the cloud resource, contact/interact with Slurm to provision instances if/when there are tasks on Slurm queue.21:37
b1airoCould Watcher easily have non Monasca data source/s - Monasca still looks extremely heavy21:38
*** bobh has joined #openstack-meeting21:38
piyanaiAs far as I know, yes, it’s still Monasca that gets the most use cases and support in Watcher21:38
piyanaiIn the MOC, we had a lot of scale issues with Celometer, btw.21:39
piyanaiWe are considering moving to Monasca for monitoring21:39
b1airoMonitoring, or metrics?21:39
piyanaiBoth?21:40
oneswigpiyanai: we use Monasca - and use the multi-tenant features for providing performance telemetry to Slurm users.21:40
piyanaiGreat! we should talk.21:40
oneswigCurrently investigating a local deploy of prometheus for the same.21:40
oneswigpiyanai: that'd be great, would be good to share notes.21:41
rajulkoneswig: how's the overhead with monasca21:41
*** pchavva has quit IRC21:42
oneswigIn terms of delay or metrics sampling rate?  Not too sure on either.  We do hate the jvm processes though, they can be real hogs21:42
oneswigWe are currently kolla-ising it - or trying to - which might confine them better21:42
*** openstack has joined #openstack-meeting21:43
*** ChanServ sets mode: +o openstack21:43
rajulkwatcher continuously runs as a background daemon and checks for the job in slum and resource utilization from monasca21:44
*** bobh has quit IRC21:44
*** sdague has joined #openstack-meeting21:44
*** beekhof_the_jit has quit IRC21:44
piyanaiGrow : create instances if there is resource in the cloud. Or if there is already suspended instances21:44
piyanaiShrink : Nova API to suspend instances21:44
*** erlon has quit IRC21:44
oneswigWhat do you do to reconfigure slurm?  Or is it sized to maximum at creation?21:45
*** ad_rien_ has quit IRC21:46
rajulkthe config file contains the max possible nodes in the cluster21:46
b1airoDo you have a configurable high watermark at which point you stop growing and calculate necessary shrink against? I.e so there is always some capacity available21:46
priteaupiyanai: Are you using the Mongo-backed Ceilometer, or Gnocchi?21:46
piyanaiYes, the watermark is set in Watcher21:46
rajulkb1airo21:46
rajulkyes there is a threshold21:47
piyanaiCeilometer -> Gnocchi21:47
piyanaiFor the POC, the threshole is set to 50%21:48
piyanaiWhat we found is that Watcher is very easy to use for this purpose21:48
*** bobh has joined #openstack-meeting21:48
*** amodi has quit IRC21:48
piyanaiIt’s basically boiled down to a few stages ; monitor/analyse/profile/goal/plan/apply21:49
oneswigpiyanai: what needs doing before this can go into production?21:49
verdurinpiyanai: you mentioned in the Sydney talk that you discussed your work at the Slurm User Group meeting21:49
verdurinpiyanai: is the work submitted to SchedMD?21:49
piyanaiverdurin: Rajul is proposing the work to the User Group meeting21:50
priteaupiyanai: Did you solve your scaling issues when switching to Gnocchi?21:50
piyanaiI believe it’s under reviewed21:50
oneswigDid you get the suspended state into Slurm?21:51
piyanaiScaling with Gnocchi -> nope21:51
*** fzdarsky is now known as fzdarsky|afk21:51
rajulkverdurin: this was proposed to the SchedMD....so a whole or some minimal feature might be added to slurm21:51
rajulkoneswig: yes we added a suspend state for poc21:52
oneswigrajulk: but did it go into Slurm's code base?21:52
verdurinrajulk: would be good to hear about progress with them21:52
rajulkoneswig: not yet21:52
priteaupiyanai: That's surprising because the Gnocchi developers often talk about how scalable it is21:52
oneswigrajulk: good luck :-)21:52
b1airoStill depends on the Gnocchi backend I guesss21:53
trandlesSchedMD must be getting tired of hearing about OpenStack integration...I started talking with them last week about upstreaming some plugins...maybe we should have a larger more general discussion21:53
rajulkthanks :)21:53
*** bobh has quit IRC21:53
piyanaipriteau: we might had done something not quite right (doubt it). But every time a new version of OpenStack comes out we had high hope… but ended up with just abandan Ceilometer/Gnocchi21:54
rajulktrandles +121:54
verdurintrandles: yes, success is more likely that way21:54
oneswigIt's interesting to hear a very different use case for Slurm.  Instead of an enclosed cluster, something hybrid, integrating with the wider data centre21:55
*** slaweq_ has quit IRC21:55
piyanaiSlurm = HPC ?21:55
verdurinoneswig: they would be wise to embrace this sort of integration21:55
piyanaiHPC = Slurm - at least that’s my impression from Physics folks around us21:56
*** slaweq has joined #openstack-meeting21:56
oneswigpiyanai: not always I guess, but perhaps hpc mostly = slurm?21:56
*** jamesmcarthur has joined #openstack-meeting21:56
trandlesrajulk: is it ok if I email you and start an implementation discussion?21:56
Chris_MonashUni@piyanai except when Physic = Globus Toolkit ;-)21:56
*** slaweq_ has joined #openstack-meeting21:56
*** thorst has quit IRC21:56
piyanaiOh no, Globus …21:56
trandlesHPC == slurm/torque/openpbs/pbspro/lsf21:56
verdurinrajulk: do you have a link to your source? I couldn't see one in the presentation video21:56
rajulktrandles: sure....reach me on kumar.raju@husky.neu.edu21:57
trandlesrajulk: will do, thx21:57
*** slaweq_ has quit IRC21:57
piyanaiIff Globus would be open source and free…21:57
isunilHas anyone considered PBSPro over SLURM?21:57
*** slaweq_ has joined #openstack-meeting21:57
trandlesisunil: the DoD HPCMP program for one...21:57
rajulkverdurin: have that on a private repo....can modify and share that sometime soon21:58
b1airoWhy bother with a batch scheduler when you can just combine atq and pdsh??21:58
Chris_MonashUni@piyanai, yeah, I know it was sort of a joke, but we still do have physics guys integrate with CERN via globus pipelines (tier 3 processing centres over here)21:58
*** bobh has joined #openstack-meeting21:58
verdurinrajulk: okay, thanks. Please do let us know when it's available.21:58
*** martial_ has joined #openstack-meeting21:59
*** jamesmca_ has joined #openstack-meeting21:59
piyanaiChris_MonashUni: Understood.21:59
Chris_MonashUni@isunil: we moved to slurm (from torque/maui) primarily because the support contract didn't really offer much over what we could get from the interwebs anyway21:59
rajulkverdurin: sure..thanks21:59
Chris_MonashUniPBSPro would be similar, even if Pro offers advantages they may not be large enough to justify the expense22:00
b1airoTime!22:00
oneswigah so it is22:00
*** slaweq has quit IRC22:00
oneswigthanks to our presenters and thanks for joining in.22:00
piyanaiThanks!22:00
isunilChris_MonashUni: reason I was asking, because PBSpro might be working on adding OpenStack.22:00
oneswig#endmeeting22:00
martial_(sigh wrong time again. My bad, sorry)22:00
Chris_MonashUniahh, that makes sense @isunil22:00
*** ijw has joined #openstack-meeting22:01
oneswigmartial_: welcome22:01
isunilthat gives advantage to PBSPro over SLURM.22:01
oneswig:-)22:01
rajulkisunil: +1 may check this out..thanks22:01
trandlessame for me martial_ ... I joined "early" and got lucky :P22:01
oneswigI think the meetbot crashed during the meeting and has failed to close our meeting...22:01
*** rbowen has quit IRC22:02
*** armax has joined #openstack-meeting22:02
Chris_MonashUni@isunil, personally I think the slurm power managment stuff for upping and downing nodes would be a good point to hook openstack integration22:02
verdurinoneswig: you'll never leave22:02
*** leong has quit IRC22:02
oneswigverdurin: We are in IRC's "Hotel California"22:02
Chris_MonashUnibut slurm really only makes decisions based on the queue, and can't look at the state of the cloud22:02
trandlesoneswig: the log stops around the 42 minute mark :(22:02
verdurinChris_MonashUni: yes, that's the sort of approach I've seen so far22:02
verdurinoneswig: thinking more Royston Vasey22:02
oneswigtrandles: did someone say something rude to crash the bot?22:02
*** isunil has quit IRC22:03
* trandles looks at b1airo 22:03
piyanaiChris_MonashUni: I don’t think Physics users care if it’s cloud or bare metal22:03
piyanaiThey know Slurm works22:03
oneswigverdurin: That's a topical observation22:03
*** Shrews has left #openstack-meeting22:03
piyanaiThey have used it - it’s a habbit22:03
*** bobh has quit IRC22:03
*** slaweq_ has quit IRC22:03
Chris_MonashUni@piyanai: I don't think they care either, except in so far as they want them TLB misses to be minimised and their cache hits to be maximised22:04
*** slaweq has joined #openstack-meeting22:04
*** jamesmcarthur has quit IRC22:04
*** slaweq has quit IRC22:04
b1airoBye all - I'm already in my next (physical) meeting22:04
Chris_MonashUniwhich has implications on how the vm is configured on the hypervisor, but only minor ones22:04
trandlespiyanai: I would assume you try not to put MPI jobs on the cloud-hosts nodes22:04
Chris_MonashUnibye @b1airo22:04
piyanaiHave got to go for another meeting now… thanks all … have a great holidays22:04
trandlescheers b1airo22:04
Chris_MonashUnibye all22:04
*** Chris_MonashUni has quit IRC22:04
*** piyanai has left #openstack-meeting22:05
oneswigThanks all22:05
*** trandles has left #openstack-meeting22:05
*** hemna_ has joined #openstack-meeting22:06
*** VW has joined #openstack-meeting22:06
*** ijw has quit IRC22:07
verdurinBye22:08
*** ykatabam has joined #openstack-meeting22:08
*** bobh has joined #openstack-meeting22:09
*** ijw has joined #openstack-meeting22:09
*** georgk has quit IRC22:13
*** slaweq has joined #openstack-meeting22:14
*** bobh has quit IRC22:14
*** ijw has quit IRC22:15
*** sgrasley1 has quit IRC22:15
*** rbudden has quit IRC22:17
*** sgrasley1 has joined #openstack-meeting22:20
*** oneswig has quit IRC22:22
*** rcernin has joined #openstack-meeting22:23
*** priteau has quit IRC22:23
*** jamesmca_ has quit IRC22:25
*** jamesmcarthur has joined #openstack-meeting22:25
*** thorst has joined #openstack-meeting22:27
*** jamesmcarthur has quit IRC22:28
*** sshank has quit IRC22:29
*** sshank has joined #openstack-meeting22:29
*** rbudden has joined #openstack-meeting22:29
*** thorst has quit IRC22:31
*** fouadben has quit IRC22:33
*** jaypipes has quit IRC22:35
*** Alex_Staf has quit IRC22:36
*** awaugama has quit IRC22:36
*** jamesmcarthur has joined #openstack-meeting22:36
*** edmondsw has quit IRC22:36
*** thorst has joined #openstack-meeting22:38
*** jamesmcarthur has quit IRC22:38
*** edmondsw has joined #openstack-meeting22:39
*** bollig has quit IRC22:40
*** bollig has joined #openstack-meeting22:40
*** thorst has quit IRC22:42
*** abalutoiu has quit IRC22:42
*** edmondsw has quit IRC22:43
*** jamesmcarthur has joined #openstack-meeting22:46
*** Leom has quit IRC22:49
*** bobh has joined #openstack-meeting22:50
*** bobh has quit IRC22:55
*** marst has quit IRC22:56
*** sboyron has quit IRC23:00
*** Alex_Staf has joined #openstack-meeting23:01
*** ijw has joined #openstack-meeting23:03
*** zhhuabj_ has quit IRC23:04
*** jamesmcarthur has quit IRC23:05
*** ijw has quit IRC23:08
*** msimonin has quit IRC23:11
*** msimonin has joined #openstack-meeting23:11
*** epei has quit IRC23:11
*** sshank has quit IRC23:13
*** epei has joined #openstack-meeting23:16
*** lbragstad has quit IRC23:17
*** edmondsw has joined #openstack-meeting23:18
*** sshank has joined #openstack-meeting23:18
*** epei has quit IRC23:19
*** epei has joined #openstack-meeting23:19
*** bobh has joined #openstack-meeting23:20
*** epei_ has joined #openstack-meeting23:22
*** edmondsw has quit IRC23:23
*** lbragstad has joined #openstack-meeting23:24
*** epei has quit IRC23:24
*** bobh has quit IRC23:24
*** lpetrut has quit IRC23:25
*** jamesmcarthur has joined #openstack-meeting23:26
*** epei_ has quit IRC23:26
*** flanders_ has quit IRC23:27
*** epei has joined #openstack-meeting23:33
*** bobh has joined #openstack-meeting23:34
*** VW has quit IRC23:35
*** salv-orl_ has joined #openstack-meeting23:37
*** epei has quit IRC23:37
*** bobh has quit IRC23:39
*** fnaval has quit IRC23:40
*** salv-orlando has quit IRC23:40
*** slaweq has quit IRC23:40
*** slaweq has joined #openstack-meeting23:41
*** slaweq has quit IRC23:45
*** thorst has joined #openstack-meeting23:46
*** thorst has quit IRC23:50
*** lbragstad has quit IRC23:56

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