Tuesday, 2016-12-20

*** donghao has quit IRC00:01
*** mmalik4 has quit IRC00:01
*** fnaval_ has quit IRC00:01
*** thorst has quit IRC00:05
*** cody-somerville has joined #openstack-meeting00:13
*** aeng has quit IRC00:14
*** VW has quit IRC00:15
*** aeng has joined #openstack-meeting00:19
*** Leom has quit IRC00:21
*** cody-somerville has quit IRC00:22
*** cody-somerville has joined #openstack-meeting00:22
*** cody-somerville has quit IRC00:22
*** cody-somerville has joined #openstack-meeting00:22
*** juzuluag has joined #openstack-meeting00:24
*** guoshan has joined #openstack-meeting00:27
*** Julien-zte has joined #openstack-meeting00:35
*** claudiub has quit IRC00:38
*** hongbin has quit IRC00:41
*** Wenzhi has joined #openstack-meeting00:45
*** aeng has quit IRC00:49
*** lamt has joined #openstack-meeting00:53
*** cody-somerville has quit IRC00:54
*** dimtruck is now known as zz_dimtruck00:55
*** emagana has quit IRC00:56
*** amotoki has joined #openstack-meeting00:56
*** sdake has joined #openstack-meeting00:56
*** kevinz has joined #openstack-meeting00:56
*** emagana has joined #openstack-meeting00:57
*** emagana has quit IRC01:02
*** thorst has joined #openstack-meeting01:03
*** huanxuan has joined #openstack-meeting01:05
*** guoshan has quit IRC01:05
*** sdake_ has joined #openstack-meeting01:09
*** thorst has quit IRC01:10
*** amotoki has quit IRC01:11
*** sdake has quit IRC01:11
*** weshay_relocatin is now known as weshay01:12
*** amotoki has joined #openstack-meeting01:12
*** aeng has joined #openstack-meeting01:13
*** cody-somerville has joined #openstack-meeting01:15
*** cody-somerville has quit IRC01:15
*** cody-somerville has joined #openstack-meeting01:15
*** zz_dimtruck is now known as dimtruck01:16
*** unicell has quit IRC01:18
*** longxiongqiu has joined #openstack-meeting01:20
*** juzuluag has quit IRC01:26
*** guoshan has joined #openstack-meeting01:26
*** amotoki has quit IRC01:28
*** amotoki has joined #openstack-meeting01:30
*** cody-somerville has quit IRC01:32
*** gongysh has joined #openstack-meeting01:33
*** zhhuabj has quit IRC01:34
*** longxiongqiu has quit IRC01:37
*** cody-somerville has joined #openstack-meeting01:37
*** cody-somerville has quit IRC01:37
*** cody-somerville has joined #openstack-meeting01:37
*** yamamot__ has joined #openstack-meeting01:39
*** baoli has joined #openstack-meeting01:40
*** fnaval has joined #openstack-meeting01:41
*** longxiongqiu has joined #openstack-meeting01:41
*** dmacpher has quit IRC01:43
*** baoli has quit IRC01:45
*** lhx_ has joined #openstack-meeting01:46
*** zhhuabj has joined #openstack-meeting01:47
*** longxion_ has joined #openstack-meeting01:51
*** cody-somerville has quit IRC01:53
*** longxiongqiu has quit IRC01:55
*** cody-somerville has joined #openstack-meeting01:57
*** mickeys has quit IRC01:57
*** Sukhdev has quit IRC01:59
*** neiljerram has quit IRC02:00
*** sdake_ has quit IRC02:00
*** thorst has joined #openstack-meeting02:07
*** gouthamr has quit IRC02:10
*** thorst has quit IRC02:14
*** thorst has joined #openstack-meeting02:15
*** asselin_ has joined #openstack-meeting02:19
*** thorst has quit IRC02:19
*** kjorgensen has quit IRC02:19
*** asselin__ has joined #openstack-meeting02:20
*** kjorgensen has joined #openstack-meeting02:20
*** asselin has quit IRC02:20
*** asselin_ has quit IRC02:23
*** longxiongqiu has joined #openstack-meeting02:24
*** kjorgens_ has joined #openstack-meeting02:24
*** kjorgensen has quit IRC02:25
*** longxion_ has quit IRC02:25
*** kjorgens_ has quit IRC02:29
*** kjorgensen has joined #openstack-meeting02:29
*** gcb has quit IRC02:30
*** kjorgensen has quit IRC02:33
*** mriedem has quit IRC02:33
*** prameswar has joined #openstack-meeting02:35
*** zhhuabj has quit IRC02:46
*** mkrai_ has joined #openstack-meeting02:47
*** vi01et has quit IRC02:48
*** s3wong has quit IRC02:49
*** gcb has joined #openstack-meeting02:50
*** hongbin has joined #openstack-meeting02:53
*** cloud_player has joined #openstack-meeting02:56
*** Namrata has joined #openstack-meeting02:57
*** prameswar has left #openstack-meeting02:57
*** prameswar has joined #openstack-meeting02:57
*** mickeys has joined #openstack-meeting02:59
*** gongysh has quit IRC03:00
hongbin#startmeeting zun03:00
openstackMeeting started Tue Dec 20 03:00:14 2016 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_2016-12-20_0300_UTC Today's agenda03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
mkrai_Madhuri Kumari03:00
NamrataNamrata03:00
kevinzkevinz03:00
*** pksingh has joined #openstack-meeting03:00
*** zhangjl has joined #openstack-meeting03:00
pksinghpksingh03:01
*** bobh has joined #openstack-meeting03:01
hongbinthanks for joining the meeting mkrai_ Namrata kevinz pksingh03:01
*** iyamahat has quit IRC03:01
hongbinlet's get started03:01
hongbin#topic Announcements03:02
*** openstack changes topic to "Announcements (Meeting topic: zun)"03:02
hongbini have no announcement03:02
hongbinanyone else has any announcement?03:02
hongbin#topic Review Action Items03:02
*** openstack changes topic to "Review Action Items (Meeting topic: zun)"03:02
hongbin1. hongbin split the k8s bp into two (DONE)03:02
hongbin#link https://blueprints.launchpad.net/zun/+spec/introduce-pod The Pod BP03:02
hongbin#link https://blueprints.launchpad.net/zun/+spec/k8s-integration The k8s BP03:02
hongbinThe pod bp needs an owner03:03
hongbinif anyone interest in the work, feel free to take it03:03
hongbin2. hongbin raise a ML with API WG to discuss the consolidate of actions into single URL (DONE)03:03
hongbin#link http://lists.openstack.org/pipermail/openstack-dev/2016-December/109136.html03:03
pksinghcurrently implementing api bp, i can teke that if any body helps me03:03
*** mickeys has quit IRC03:03
*** lakerzhou has joined #openstack-meeting03:04
*** fnaval has quit IRC03:04
hongbinpksingh: sure, i can help you a bit03:04
pksinghhongbin: ok :)03:04
hongbinpksingh: feel free to assign it to yourself03:04
hongbinok, back to the ML discussion03:05
hongbinthere are two replies on the ML03:05
hongbinfirst reply: http://lists.openstack.org/pipermail/openstack-dev/2016-December/109178.html03:05
mkrai_First reply seems out of context to me03:05
hongbinchris dent seems to suggest to consolidate multiple urls03:06
mkrai_I didn't get the response clearly may be03:06
mkrai_hongbin: Can you please explain what option he proposed?03:06
hongbinmkrai_: i am also not sure exactly what he mean03:06
*** yamahata has quit IRC03:06
hongbinmkrai_: by looking at the urls, i guess he suggested to consolidate multiple urls03:07
hongbinhowever, the second reply is the meat03:07
hongbin#link http://lists.openstack.org/pipermail/openstack-dev/2016-December/109208.html03:07
mkrai_Yes Alex's response is clear03:07
hongbinalex xu is a nova core, he pointed out the problems of having multple urls03:07
hongbinpersonally, i agree with him03:08
mkrai_hongbin: I think he has pointed out problems with single API03:08
hongbinmkrai_: yes03:08
mkrai_Ok03:08
*** zhhuabj has joined #openstack-meeting03:09
*** dmacpher has joined #openstack-meeting03:09
hongbinthen, we could leave it as multiple url as is03:09
hongbin(if there is no further objection)03:09
hongbinQiming: ping03:09
mkrai_I am ok with it03:09
pksinghme to03:09
hongbinok03:09
hongbinthen, move on03:10
hongbin#topic Introduce pod03:10
*** openstack changes topic to "Introduce pod (Meeting topic: zun)"03:10
hongbin#link https://blueprints.launchpad.net/zun/+spec/introduce-pod The BP03:10
hongbinlet's skip this one for now, since pksingh just took it03:10
Qimingpo03:10
hongbinQiming: hey03:10
hongbinQiming: we are discussing the multiple action urls03:10
Qimingyes03:11
*** sharatss has quit IRC03:11
hongbinQiming: based on the replies in the ML, it seems there are several problems of this design in nova03:11
*** sharatss has joined #openstack-meeting03:11
Qiminglooking03:11
hongbinQiming: so it seems people lean on the multiple urls options03:11
hongbinQiming: we can get back to it at open discussion if you like03:12
Qimingokay03:12
hongbin#topic Support multi-host deployment (hongbin)03:12
*** openstack changes topic to "Support multi-host deployment (hongbin) (Meeting topic: zun)"03:12
hongbin#link https://blueprints.launchpad.net/zun/+spec/support-multiple-hosts The BP03:12
hongbini am going to start this one next week03:12
hongbinthe idea is to support deploying multiple zun-compute to hosts (right now, we deploy everyone in a single host)03:13
mkrai_cool this will be good to have03:13
hongbinyes03:13
hongbini will work on that, and report the status at the next meeting03:13
hongbinnext one03:13
hongbin#topic Support interactive mode (kevinz)03:13
*** openstack changes topic to "Support interactive mode (kevinz) (Meeting topic: zun)"03:13
hongbin#link https://blueprints.launchpad.net/zun/+spec/support-interactive-mode The BP03:13
hongbin#link https://review.openstack.org/#/c/396841/ The design spec03:13
hongbinkevinz: ^^03:13
kevinzhttps://github.com/kevin-zhaoshuai/container-interactive-client03:14
kevinzLast week I have finished a demo for this03:14
*** thorst has joined #openstack-meeting03:14
hongbincoll03:14
hongbincool03:14
*** thorst has quit IRC03:14
kevinzNow the status is we can use the websocket link to do interactive mode to container03:14
hongbin#link https://github.com/kevin-zhaoshuai/container-interactive-client03:15
*** diga has joined #openstack-meeting03:15
kevinzStill two issues I need to fix. One is python packages websocket-client , Websocket-client will need to modify some code when dealing with escape code.03:15
kevinzThe other is add support to container tty session resize according to current user03:16
hongbincould you elaborate what is tty session resize?03:16
kevinzOfcourse03:17
digahttps://www.irccloud.com/pastebin/Nujli3wo03:18
kevinzdocker will generated a tty session inside the container,I will find a link03:18
digao/03:18
kevinzhttps://docs.docker.com/engine/reference/api/docker_remote_api_v1.21/#/resize-a-container-tty03:18
hongbindiga: thanks for joining03:18
*** yangyapeng has joined #openstack-meeting03:19
*** mriedem has joined #openstack-meeting03:19
*** sdake has joined #openstack-meeting03:19
digahongbin: welcome03:19
kevinzwhen we connect to the container, user will get a fixable size tty session03:19
hongbinkevinz: i see03:19
*** sdake has quit IRC03:19
*** vishnoianil has joined #openstack-meeting03:20
*** sdake has joined #openstack-meeting03:20
kevinzwe can change it according to users' terminal size.03:20
hongbini see03:20
hongbinkevinz: sounds you have a good progress on this one03:20
hongbinkevinz: do you need any help from our team member regarding to this bp?03:21
kevinzhongbin: Thanks~ If I need I will ask wenzhi for some help :D03:22
hongbinanyway, feel free to ping any of us in irc if you need help03:22
hongbinok03:22
kevinzWhen integrate with zun and clis03:22
hongbingreat03:22
hongbinnext one03:22
*** mickeys has joined #openstack-meeting03:22
hongbin#topic Make Zunclient an OpenStackClient plugin (Namrata)03:23
*** openstack changes topic to "Make Zunclient an OpenStackClient plugin (Namrata) (Meeting topic: zun)"03:23
hongbin#link https://blueprints.launchpad.net/zun/+spec/zun-osc-plugin03:23
hongbinNamrata: ^^03:23
Namratahey03:23
NamrataHave uploaded the initial commit for opensack client support in python - zunclient and it is merged03:23
NamrataI have uploaded OSC plugin fo command show but there is a name conflict03:23
Namrataso can we discuss what command name should be there03:23
*** vishnoianil has quit IRC03:24
hongbinNamrata: i think you can forget about the name conflict for now03:24
hongbinNamrata: it is a bigger problem we need to deal with :)03:25
Namrataso how would it work with swift ?03:25
hongbinfor others, we are talking about the keywork "container" was taken in openstackclient by swift03:25
stevemarthere is a non-voting job you can add to your client to pick up these conflicts when they are proposed, see: http://docs.openstack.org/developer/python-openstackclient/plugins.html#checklist-for-adding-new-openstack-plugins03:25
*** JRobinson__ is now known as JRobinson__afk03:25
*** pksingh_ has joined #openstack-meeting03:26
hongbinstevemar: ack03:26
hongbinstevemar: is there any way to allow the same keyword (i.e. container) can be taken by multiple project?03:27
hongbin#link http://docs.openstack.org/developer/python-openstackclient/plugins.html#checklist-for-adding-new-openstack-plugins03:27
Namratastevemar:thanks03:27
hongbinstevemar: e.g. a namespace ?03:27
stevemarhongbin: unfortunately not03:27
hongbinstevemar: is that a reasonable feature that can be requested for osc?03:27
stevemarcontainer is tricky... in swift it's a container / bucket for objects03:27
hongbinyes it is03:28
stevemarhongbin: we've had discussions on the mailing list before about namespacing comands03:28
hongbini guess what we wanted is a feature to shadow swift container when users are using zun03:28
mkrai_barbican also have container concept03:28
stevemarmkrai_: i think they are calling it "secret container"03:28
*** pksingh has quit IRC03:28
stevemarhttps://github.com/openstack/python-barbicanclient/blob/master/setup.cfg#L45-L4803:29
mkrai_stevemar: Yes I saw that03:29
stevemarhongbin: Namrata i suggest a note to the mailing list, so dtroyer can give guidance03:29
digahongbin: may be we can initiate conversation with swift team on this ?03:29
mkrai_hongbin: There is high possibility that users can use both in future03:29
hongbinstevemar: ack03:30
stevemarthe swift team doesn't own the OSC commands03:30
hongbin#action hongbin start a ML to osc team to discus the name collision issue03:30
stevemarthe OSC team (myself + dtroyer + a few others) owns the commands used in osc03:30
stevemar(we deeply regret calling the swift container just "container")03:31
mkrai_I suggest to have "object container"03:31
hongbinyes, imho, every commands should prefix with a project name (i.e. compute, network , ...)03:31
mkrai_But this suggestion would be too early03:31
hongbinthat is how aws cli works ....03:32
mkrai_+1 hongbin03:32
pksingh_+103:32
hongbinanyway03:32
stevemarheres an old reference: http://lists.openstack.org/pipermail/openstack-dev/2015-October/076354.html03:32
hongbin#link http://lists.openstack.org/pipermail/openstack-dev/2015-October/076354.html03:32
stevemarhongbin: right, just don't use the project "code name", so don't call it "openstack zun container show" :)03:33
*** huanxuan has quit IRC03:33
stevemarcongress did that, and it's ugly03:33
*** amotoki has quit IRC03:33
hongbinstevemar: yes, that could be an alternative03:33
stevemarwe could rename the OSC command, but we would need to deprecate it first :\03:34
stevemarwhen will zunclient be released?03:34
hongbinpossibly a few months after03:34
stevemarOK, we can discuss this in the ML, i'll respond there03:35
stevemardon't want to take up more time in the meeting03:35
hongbinstevemar: thanks for your response and suggestion here :)03:35
Namratastevemar:thanks03:35
stevemarnp03:36
hongbinNamrata: my advice for you is don't worry the namespace problem for now03:36
hongbinNamrata: i will help you to deal with that03:36
hongbinNamrata: just add commands as you did before03:36
Namratathanks hongbin03:36
hongbinNamrata: np03:36
Namrataokay i will add03:37
Namratahttps://etherpad.openstack.org/p/zunclient_openstack-client-cli03:37
Namratathese are the osc commmands i will further work on03:37
hongbinNamrata: lgtm03:38
pksingh_Namrata: +103:38
Namratathanks hongbin pksingh_03:38
hongbinok, move on03:38
hongbin#topic Open Discussion03:38
*** openstack changes topic to "Open Discussion (Meeting topic: zun)"03:38
hongbinanyone has a topic to bring up here?03:39
hongbinQiming: want to discuss the action urls?03:39
hongbinok, if there is no topic, let's end the meeting earlier03:40
mkrai_Qiming: has replied to email03:40
pksingh_hongbin: can we look into https://blueprints.launchpad.net/zun/+spec/auto-select-nova-flavor03:40
hongbinpksingh_: sure03:41
hongbinpksingh_: go ahead03:41
pksingh_how will we finding the exact memory requirement?03:41
pksingh_means exact flavour size mey not  be there right?03:41
pksingh_wouldn't that be waste of resource03:42
pksingh_make sense?03:43
hongbinyes, this is a good point03:43
stevemaroh, just one more comment on the CLI (now that I see the etherpad) -- the trove team actually made a spec added for it: https://review.openstack.org/#/c/391871/ and asked me + dtroyer to review. They've found it helpful so far :)03:43
hongbinpksingh_: do you have an alternative proposal?03:43
pksingh_hongbin: i dont have now,03:43
*** abhishekk has joined #openstack-meeting03:44
hongbinstevemar: ack03:44
pksingh_if we go through nova then i think this is the only possible solution03:44
hongbin#link  https://review.openstack.org/#/c/391871/03:44
*** dmorita has quit IRC03:44
hongbinpksingh_: another option is cerating a new flag (i.e. --extra-opts nova.flavor=m1.small)03:45
pksingh_hongbin: from cli?03:45
hongbinpksingh_: yes03:45
hongbinpksingh_: and rest api as well03:45
hongbinpksingh_: however, we need to deal with the case that if this flag is not specified03:46
pksingh_hongbin: i was thinking sandbox should not be exposed to users, they should just know about containers03:46
hongbinsure, that is a valid point03:46
mkrai_+1 pksingh_03:47
hongbinthen, we need to auto-select the sandbox flavor for users somehow03:47
pksingh_hongbin: okay lets go with bestfit falvour for time being03:47
mkrai_And the logic should reside in zun03:47
hongbinpksingh_: wfm03:47
pksingh_later we can refine03:47
hongbinok03:48
prameswarhi hongbin , you added one bug #link https://bugs.launchpad.net/zun/+bug/1650979 that is related to pulling large image i also tested. it is not ending it keep on showing pulling_image. so you suggested 3 point. anyone want to suggest which is best way to solve that problem?03:48
openstackLaunchpad bug 1650979 in Zun "Zun run failed when pulling a large image" [Medium,Triaged]03:48
pksingh_ok thats all from me03:48
mkrai_pksingh_: the extra ram can be used by nova to host new sandboxes03:48
hongbinprameswar: sure, we could discuss that here03:49
pksingh_mkrai_: sure, we will discuss that, once i propose the bp spec03:49
mkrai_pksingh_: Sure03:49
hongbin#link https://bugs.launchpad.net/zun/+bug/165097903:49
openstackLaunchpad bug 1650979 in Zun "Zun run failed when pulling a large image" [Medium,Triaged]03:49
mkrai_prameswar: I feel make it "cast"03:49
pksingh_prameswar: for timebeing i am in favour of cast03:49
*** VW has joined #openstack-meeting03:49
hongbinlet's pause a few seconds for everyone to review the bug03:49
hongbinok, sound like we already has a choice03:50
digahongbin: is there anyone working on storage support if not, I will start on03:50
prameswari also think so03:50
hongbindiga: sure03:50
digahongbin:  will talk about it on zun channel03:51
hongbinprameswar: ok, sounds like you are good to go?03:51
digaAfter the meeting03:51
prameswaryes :)03:51
*** Namrata_ has joined #openstack-meeting03:51
hongbinprameswar: great03:51
hongbindiga: you wanted to work on this one? https://blueprints.launchpad.net/zun/+spec/cinder-zun-integration03:51
hongbindiga: ok, ping me at zun channel about that03:52
*** Dinesh_Bhor has joined #openstack-meeting03:52
hongbinany other topic?03:52
*** Namrata has quit IRC03:52
*** subh has joined #openstack-meeting03:52
hongbinall, thanks for joining the meeting. a reminder, there will be no meeting next week. have a happy holiday03:53
hongbin#endmeeting03:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"03:53
openstackMeeting ended Tue Dec 20 03:53:24 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-12-20-03.00.html03:53
pksingh_same to u03:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-12-20-03.00.txt03:53
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-12-20-03.00.log.html03:53
mkrai_Happy holidays everyone!03:53
*** zhangjl has left #openstack-meeting03:53
*** mkrai_ has quit IRC03:54
*** yangyapeng has quit IRC03:54
*** samP has joined #openstack-meeting03:56
digaSure hongbin03:56
*** zhhuabj has quit IRC03:56
*** zhhuabj has joined #openstack-meeting03:57
*** sdake_ has joined #openstack-meeting03:58
*** rkmrhj has joined #openstack-meeting03:58
*** sdake has quit IRC03:59
samPhi o/04:00
samPare we good to start masakari meeting?04:00
rkmrhjNo problem.04:00
samPok then04:00
samP#startmeeting masakari04:01
openstackMeeting started Tue Dec 20 04:01:00 2016 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.04:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:01
*** openstack changes topic to " (Meeting topic: masakari)"04:01
openstackThe meeting name has been set to 'masakari'04:01
samPhi all04:01
*** yangyapeng has joined #openstack-meeting04:01
abhishekko/04:01
Dinesh_BhorsamP: hi04:01
abhishekkhi04:01
rkmrhjhi04:01
samP#topic Critical bugs04:01
*** openstack changes topic to "Critical bugs (Meeting topic: masakari)"04:01
samPany bus to discuss?04:01
samPsorry, bugs04:02
*** lakerzhou has quit IRC04:02
*** JRobinson__afk is now known as JRobinson__04:02
samPif no then, we can jump in to next topic04:02
samPif you have any, then we can discuss them later in this meeting04:03
samP#topic Discussion points04:03
*** openstack changes topic to "Discussion points (Meeting topic: masakari)"04:03
samPFirst, pypi packaging04:04
samPwhen we create the repo, I didn't add pypi jobs. so, there are no pypi packages for masakari04:04
samPToday I manually add v2.0.1 to pypi04:05
*** dmorita has joined #openstack-meeting04:05
samP#link https://pypi.python.org/pypi/masakari/2.0.1.dev1904:05
samPI can do same for masakari-monitors and python-masakari-client04:06
*** pksingh_ has quit IRC04:06
*** tpatil_ has joined #openstack-meeting04:06
rkmrhjsamP: Please do it.04:06
samPI think we should add pypi jobs for gate to automatically update the pypi04:06
tpatil_Hi04:07
samPhi04:07
tpatil_Having problem connecting from my mac, so connected from windows04:07
*** amotoki has joined #openstack-meeting04:07
samPtpatil_: ok, no problem. you are live now..04:08
tpatil_Yes ,finally04:08
samPwe are discussing about adding pypi packages for masakari/monitors/client04:08
*** VW has quit IRC04:09
tpatil_ok04:09
*** cody-somerville has quit IRC04:09
samPI will update the project config for add pypi jobs for masakari/monitors/client.04:09
samPhowever, monitors would be bit tricky.04:10
*** dmorita has quit IRC04:10
samPrkmrhj: how are we doing with adding setup script for shell scripts in monitors?04:10
*** rkmrhj_ has joined #openstack-meeting04:10
*** sdake has joined #openstack-meeting04:11
*** sdake_ has quit IRC04:11
samPanyway, I will work with masakari and client first.04:12
samP#action samP add pypi jobs to project config of masakari and client and monitors04:12
*** rkmrhj has quit IRC04:13
rkmrhj_samP: Thanks.04:13
samPnext, I would like to discuss about documentation04:13
samPThe reason is, some ppl are start to try masakari and Im flooded with emils04:14
tpatil_what kind of documentation are you expecting to start with?04:15
tpatil_apis?04:15
*** rkmrhj has joined #openstack-meeting04:15
*** yamahata has joined #openstack-meeting04:15
samPIn first step, how to install and then APIs04:15
samPI think we do have japanese doc for how to install and configure04:16
tpatil_please forward all Japanese documentation to us and we will try to translate in English.04:17
abhishekksamP: https://github.com/openstack/masakari/tree/master/devstack, here it is mentioned how you can install masakari04:17
*** rkmrhj_ has quit IRC04:17
samPabhishekk: thanks04:18
samPabhishekk: we need to document this from how setup from the start, start with creating pacemaker cluster for compute nodes04:19
*** prateek has joined #openstack-meeting04:19
abhishekksamP: ok, got it04:19
*** thorst has joined #openstack-meeting04:19
samPtpatil_: I will try to translate this to some level. could you please brush it up?04:20
tpatil_samP: Sure04:20
samPand the next question is, where we can host this?04:20
*** sudipto has joined #openstack-meeting04:20
*** sudipto_ has joined #openstack-meeting04:20
samPsince we can not use openstack.doc, one option is to use http://pythonhosted.org/masakari04:21
*** huanxuan has joined #openstack-meeting04:21
samPor we can host it in git with masakari source04:21
tpatil_samP: I think git is fine to start with04:22
samPtpatil_: sure, then I will push the initial draft04:23
*** subh has quit IRC04:23
rkmrhjDoes the document contains installing steps of masakari-monitors?04:23
*** sdake_ has joined #openstack-meeting04:24
samPrkmrhj: good question, I am thinking to put them all in one document.04:25
tpatil_In general, it should include all services needed to run masakari in multi node environment.04:25
samPrkmrhj: any suggestions?04:25
samPtpatil_: sure04:26
*** mickeys has quit IRC04:26
rkmrhjsampP: Sorry, no suggestions. I planned to write installing steps of masakari-monitors after implementing blueprints. But my plan doesn't contain masakari.04:26
samPabhishekk: thanks for the BP..04:26
abhishekksamP: WC04:27
*** sdake has quit IRC04:27
samPrkmrhj: That would be fine. I will write the basic steps to install them. you can update it.04:28
*** thorst has quit IRC04:28
rkmrhjsamP: OK, sure.04:29
samP#action samP add "how to install masakari" docs04:29
samPOK, I will add them soon04:29
samPnext topic is sepc repo04:29
samP#link https://review.openstack.org/#/c/412376/04:29
samPits under review now, hopefully we will get it soon. Then I will cookiecut it and will be ready to go.04:31
*** prameswar has left #openstack-meeting04:31
tpatil_After this patch is merged, we will start pushing specs for all action items in last meeting04:31
tpatil_all action items discussed in last meeting04:31
samPtpatil_: user, but wait for cookicut.04:31
*** diablo_rojo has joined #openstack-meeting04:31
samPtpatil_: not "user", sure04:32
*** unicell has joined #openstack-meeting04:32
tpatil_you mean once this project is available in github, correct?04:32
*** hongbin has quit IRC04:33
samPtpatil_: after it available in github, first patch would be the cookicut, which make the structure for the repo04:33
tpatil_samP: Ok, I got it04:34
samPtpatil_: I will puch this patch wright after repo available on github04:35
tpatil_ok04:35
samPOK then, that was all the items I added to agenda. Any thing else to discuss?04:36
tpatil_Nothing from my side for now04:37
abhishekksamP: Please check the blueprint, once it is approved we ill submit patches against it04:37
samPtpatil_: thanks04:37
samPabhishekk: sure, thank you04:37
abhishekkthanks04:37
samP#topic AOB04:38
*** openstack changes topic to "AOB (Meeting topic: masakari)"04:38
rkmrhjbye04:38
samPwait04:38
rkmrhjoh, sorry.04:38
samPI am gonna take early vac from 12/2604:38
tpatil_Ok, are you available for the next meeting?04:39
samPso, not gonna be able to host next IRC till 1/1004:40
tpatil_Ok04:40
rkmrhjSure.04:41
samPbecause its new year, I think most of us are not available on 1/304:41
*** subh has joined #openstack-meeting04:41
tpatil_Let's keep in touch for important matter on mailing list till then04:42
samPany volunteer to host the meeting on 12/27? or we can skip 12/27 and 1/304:42
*** sudipto has quit IRC04:42
*** sudipto_ has quit IRC04:42
samPtpatil_: sure04:43
tpatil_IMO, we can skip meeting on 12/27 and 1/3 and as said above we can use mailing list to discuss on important agenda04:44
rkmrhjI agree to skip 12/27 and 1/3.04:44
samPOK, lets skip the IRC for 12/27 and 1/3, however post to ML for any important matters.04:44
samPtpatil_: rkmrhj thanks04:45
samPIs there any other things to discuss?04:45
*** guoshan has quit IRC04:46
samPif no then, lest finish... thank you all04:46
rkmrhjNot discuss, but I have a request. Please review https://review.openstack.org/#/c/397064/04:46
tpatil_rkmrhj: I will check this patch soon04:47
samP#action Review https://review.openstack.org/#/c/39706404:47
rkmrhjtpatil_: Thanks a lot!04:47
samPrkmrhj: me too will check04:47
rkmrhjsamP: tanks, too.04:48
samPok then, bye all "Merry Christmas And Happy New Year"04:48
rkmrhjNG: tanks Correct: thanks04:48
Dinesh_BhorsamP: same to you, thanks to all04:49
tpatil_Happy New year to everyone in advance04:49
samP#endmeeting04:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"04:49
openstackMeeting ended Tue Dec 20 04:49:52 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2016/masakari.2016-12-20-04.01.html04:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2016/masakari.2016-12-20-04.01.txt04:49
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2016/masakari.2016-12-20-04.01.log.html04:49
*** tpatil_ has quit IRC04:50
rkmrhjbye04:50
*** rkmrhj has left #openstack-meeting04:50
samPthank you all and bye04:50
*** Namrata_ has quit IRC04:51
*** links has joined #openstack-meeting04:52
*** amotoki has quit IRC04:58
*** amotoki has joined #openstack-meeting05:03
*** sdake has joined #openstack-meeting05:05
*** sdake has quit IRC05:08
*** sdake_ has quit IRC05:08
*** sharatss has left #openstack-meeting05:10
*** amotoki has quit IRC05:14
*** mickeys has joined #openstack-meeting05:16
*** Sukhdev has joined #openstack-meeting05:22
*** thorst has joined #openstack-meeting05:25
*** thorst has quit IRC05:33
*** subh has quit IRC05:35
*** bobh has quit IRC05:40
*** kjorgensen has joined #openstack-meeting05:44
*** guoshan has joined #openstack-meeting05:46
*** dimtruck is now known as zz_dimtruck05:48
*** kjorgensen has quit IRC05:48
*** amotoki has joined #openstack-meeting05:50
*** guoshan has quit IRC05:51
*** nadya has joined #openstack-meeting05:52
*** Sukhdev has quit IRC05:52
*** bobh has joined #openstack-meeting05:57
*** yangyape_ has joined #openstack-meeting05:58
*** armax has quit IRC05:59
*** yangyapeng has quit IRC05:59
*** janki has joined #openstack-meeting06:08
*** emagana has joined #openstack-meeting06:08
*** sridharg has joined #openstack-meeting06:08
*** JRobinson__ has quit IRC06:12
*** emagana has quit IRC06:12
*** guoshan has joined #openstack-meeting06:15
*** subh has joined #openstack-meeting06:17
*** kylek3h_ has quit IRC06:20
*** amotoki has quit IRC06:21
*** nadya has quit IRC06:21
*** kylek3h_ has joined #openstack-meeting06:22
*** cody-somerville has joined #openstack-meeting06:25
*** cody-somerville has quit IRC06:25
*** cody-somerville has joined #openstack-meeting06:25
*** iyamahat has joined #openstack-meeting06:25
*** claudiub has joined #openstack-meeting06:26
*** jchhatbar has joined #openstack-meeting06:27
*** amotoki has joined #openstack-meeting06:27
*** nadya has joined #openstack-meeting06:29
*** rbartal has joined #openstack-meeting06:29
*** janki has quit IRC06:29
*** thorst has joined #openstack-meeting06:30
*** anilvenkata has joined #openstack-meeting06:32
*** iyamahat has quit IRC06:32
*** fzdarsky has joined #openstack-meeting06:33
*** lpetrut has joined #openstack-meeting06:37
*** thorst has quit IRC06:38
*** diablo_rojo has quit IRC06:41
*** samP has left #openstack-meeting06:44
*** dmorita has joined #openstack-meeting06:45
*** ykatabam has quit IRC06:49
*** dmorita has quit IRC06:49
*** fzdarsky has quit IRC06:51
*** ayogi has joined #openstack-meeting06:53
*** unicell has quit IRC06:55
*** unicell has joined #openstack-meeting06:56
*** kylek3h_ has quit IRC06:57
*** rcernin has quit IRC06:59
*** kaminohana has quit IRC07:00
*** abhishekk has left #openstack-meeting07:01
*** yangyape_ has quit IRC07:06
*** yangyapeng has joined #openstack-meeting07:09
*** cody-somerville has quit IRC07:10
*** Dinesh_Bhor has left #openstack-meeting07:11
*** tesseract has joined #openstack-meeting07:11
*** tesseract is now known as Guest1497207:11
*** rcernin has joined #openstack-meeting07:11
*** unicell1 has joined #openstack-meeting07:13
*** unicell has quit IRC07:15
*** ykatabam has joined #openstack-meeting07:15
*** longxiongqiu has quit IRC07:16
*** longxiongqiu has joined #openstack-meeting07:16
*** rbudden has quit IRC07:21
*** longxion_ has joined #openstack-meeting07:21
*** longxiongqiu has quit IRC07:23
*** Ravikiran_K has joined #openstack-meeting07:23
*** rcernin has quit IRC07:26
*** kylek3h_ has joined #openstack-meeting07:30
*** zhhuabj has quit IRC07:30
*** amotoki has quit IRC07:31
*** lpetrut has quit IRC07:32
*** yuval has joined #openstack-meeting07:34
*** diga has quit IRC07:34
*** thorst has joined #openstack-meeting07:35
*** yangyape_ has joined #openstack-meeting07:35
*** yangyape_ has quit IRC07:36
*** yangyapeng has quit IRC07:39
*** rcernin has joined #openstack-meeting07:43
*** andreas_s has joined #openstack-meeting07:43
*** thorst has quit IRC07:43
*** Ravikiran_K has quit IRC07:44
*** yangyapeng has joined #openstack-meeting07:44
*** rasca has joined #openstack-meeting07:45
*** manikanta_tadi has quit IRC07:51
*** eranrom has joined #openstack-meeting07:57
*** adiantum has joined #openstack-meeting07:57
*** irenab has quit IRC07:59
eranrom#startmeeting storlets08:00
openstackMeeting started Tue Dec 20 08:00:08 2016 UTC and is due to finish in 60 minutes.  The chair is eranrom. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: storlets)"08:00
openstackThe meeting name has been set to 'storlets'08:00
eranromHi08:00
eranromagenda is here: https://wiki.openstack.org/wiki/Meetings/Storlets08:00
*** kota_ has joined #openstack-meeting08:01
kota_hello08:01
eranromHi Kota08:01
kota_hi eranrom08:01
eranromhere is the agenda: https://wiki.openstack.org/wiki/Meetings/Storlets08:02
kota_thx08:02
eranromDo you know if Takashi plans on joining?08:02
*** cdub has quit IRC08:02
*** manikanta_tadi has joined #openstack-meeting08:03
kota_idk but i heared takashi has been tied up to a trouble shoorting recently.08:03
*** akihito has joined #openstack-meeting08:03
kota_so it may be difficult to attend unfortunately08:03
eranromHi Akihito.08:03
eranromkota_: with a cient?08:03
akihitoHi !08:04
eranromclient08:04
kota_eranrom: yeah, I cannot say anything in detail though :/08:04
eranromok, lets start then08:04
eranrom#topic Big-Tent08:04
*** openstack changes topic to "Big-Tent (Meeting topic: storlets)"08:04
*** sshnaidm|afk is now known as sshnaidm08:04
eranromSo we are on the agenda today/tomorrow08:05
eranromAny comments on the summary in the Etherpad?08:05
eranromhttps://etherpad.openstack.org/p/storlets-big-tent08:05
kota_looking08:06
akihitoI confirm it.08:06
eranromThanks!08:06
eranromakihito: thanks!08:06
kota_the summary looks great, we've been progressed08:07
eranromyeah, a lot of work from you guys actually :-)08:08
kota_:-)08:09
eranromnext topic?08:09
kota_sure08:09
akihitook.08:09
*** adiantum has quit IRC08:10
*** huanxuan has quit IRC08:10
eranrom#topic Patches review prioritisation08:10
*** openstack changes topic to "Patches review prioritisation (Meeting topic: storlets)"08:10
*** akihito has quit IRC08:11
eranromhttps://review.openstack.org/#/q/project:openstack/storlets+status:open08:11
*** adiantum has joined #openstack-meeting08:11
*** akihito has joined #openstack-meeting08:11
eranromakihito: https://review.openstack.org/#/q/project:openstack/storlets+status:open08:11
eranromI basically need an input from you. What is most important from your P.O.V.08:12
*** yamamot__ has quit IRC08:12
eranromFrom my side there is one important patch which is: https://review.openstack.org/#/c/395152/08:13
eranromI just notices that it needs merge conflict. So naturally, only after I merge...08:13
kota_nice, https://review.openstack.org/#/c/394343/ has been merged08:13
akihitook. wait a minute...08:13
eranromkota_: Takashi merged it few mins before the meeting :-)08:14
eranromSo I thought he will join.08:14
kota_eranrom: i didn't notice that :D08:14
kota_gotcha08:15
*** frasantoro has joined #openstack-meeting08:16
akihitoI think that high Priority topics are https://review.openstack.org/#/c/410244/ and https://review.openstack.org/#/c/400057/08:16
akihitobut, https://review.openstack.org/#/c/400057/ is WIP...08:17
eranromakihito: ok, thanks. Suggestion (I learned this from Takashi)08:18
eranromPut WIP in the commit message and once you remove it, I know its time to review.08:18
*** pcaruana has joined #openstack-meeting08:19
kota_it would be helpful to know the status, exactly08:19
akihitoI understood.08:19
eranromIn the meantime I will look at https://review.openstack.org/#/c/395152/08:19
eranromseems like it needs a merge as well.08:19
kota_it looks, takashi is still working for https://review.openstack.org/#/c/400057/08:19
*** ricolin has joined #openstack-meeting08:19
kota_looking at the last comment from takashi, a comment says "It seems more safe to me, even if child processes are automatically killed when its parent process is killed. will fix, thanks!"08:20
kota_i'm looking at the last sentence, "will fix"08:20
kota_akihito: on the other priority patch https://review.openstack.org/#/c/400057/08:21
eranromkota_: ok gotcha. I beleive you are referring to https://review.openstack.org/#/c/410244/08:21
kota_akihito: it looks like it needs more work to resolve gate failure?08:22
kota_akihito: or issues not related to your change?08:22
kota_eranrom yeah08:22
kota_eranrom: sorry, my miss link08:23
eranromkota_: np :-)08:23
akihitohmm. I still do not understand all the details of the failure. I don't think it is a big problem.08:24
akihitoI think that I can fix it.08:24
kota_akihito: ok08:25
kota_akihito: if you need help, please feel free to ask us. probably we can work to deletct the problem08:25
*** huanxuan has joined #openstack-meeting08:25
akihitoThank you. If there is a problem ,ask you a question.08:26
*** jchhatbar is now known as janki08:27
eranromok, summarising:08:27
eranrom1. eranrom to rebase the start/stop patch and ask for review08:27
eranrom2. akihito to place WIP on the func tests patch will its ready08:27
eranrom3. eranrom to wait for Takashi to finalyze the timeout patch08:28
eranromanything esle?08:28
kota_4. I should ask takashi to merge https://review.openstack.org/#/c/409003/08:28
kota_that's all from me08:28
eranromkota_: ok, thanks!08:29
*** Wenzhi has quit IRC08:29
eranromnext topic?08:29
kota_yes08:29
akihitoyeh.08:29
*** Wenzhi has joined #openstack-meeting08:29
eranrom#topic PTG08:29
*** openstack changes topic to "PTG (Meeting topic: storlets)"08:29
eranromDepending on the results of the TC meeting we will know if we will have space.08:30
kota_ok08:30
*** ^Gal^ has joined #openstack-meeting08:30
*** llu has joined #openstack-meeting08:31
eranromI guess its too early to discuss the agenda, but I have created a roadmap wiki page you may start to look at:08:32
eranromhttps://wiki.openstack.org/wiki/Storlets/Roadmap08:32
*** nmagnezi has joined #openstack-meeting08:32
eranromand of-corse edit08:32
kota_nice08:33
akihitowow! you are great!08:33
*** amotoki has joined #openstack-meeting08:33
*** dmacpher has quit IRC08:33
eranromThank you.  Do feel free to add / change / comment.08:34
*** Wenzhi has quit IRC08:34
*** shu-mutou has joined #openstack-meeting08:34
eranromanything else on PTG?08:35
kota_non for now.08:35
akihitothat's all08:35
akihitofor me.08:36
eranromok, anything else for today?08:36
*** rcernin has quit IRC08:36
kota_nothing08:37
akihitoI don't have topic.08:37
eranromok, so thanks for joining.08:37
eranromRegards to Takashi if you talk to him.08:37
kota_thanks a lot eranrom08:37
kota_a08:37
kota_wait08:37
kota_wait wait wait08:37
eranromwaiting.08:37
kota_an important topic08:37
kota_when the next meeting happens08:37
*** subh has quit IRC08:37
kota_AFAIK, swift will skip  2 weeks for irc meeting due to christmas and new year08:38
eranromoh right.08:38
akihitook. next 1/10?08:38
kota_sounds ok to me. or 1/3 if eranrom perefers08:39
kota_ah08:39
kota_Jan 3rd08:39
akihitook.08:39
eranromI am good with both.08:39
kota_akihito: the expression is used in Japan08:39
eranromDo you have a holiday in Japan?08:40
akihitosorry.. I don't know..08:40
kota_3 days before/after new year.08:40
eranromok.08:40
akihitook!08:40
*** thorst has joined #openstack-meeting08:40
eranromI will send a mail that we skip next week and meet again on Jan 3rd08:40
eranromIf you want to change just reply.08:41
kota_that's basic holidays and someone take extra day offs around.08:41
kota_ok08:41
kota_sounds fine.08:41
eranromkota_: Thanks for bringing this up!08:41
eranromok, so once again thanks for joining, and talk to you later :-)08:41
kota_yeah! hope everyone have good vacations08:42
*** priteau has joined #openstack-meeting08:42
akihitothank you.08:42
eranromyep good vacation all!08:42
eranrom#endmeeting08:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:43
openstackMeeting ended Tue Dec 20 08:43:03 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storlets/2016/storlets.2016-12-20-08.00.html08:43
*** yamamoto has joined #openstack-meeting08:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storlets/2016/storlets.2016-12-20-08.00.txt08:43
openstackLog:            http://eavesdrop.openstack.org/meetings/storlets/2016/storlets.2016-12-20-08.00.log.html08:43
*** yamamoto has quit IRC08:47
*** thorst has quit IRC08:48
*** kota_ has left #openstack-meeting08:48
*** mickeys has quit IRC08:50
*** emagana has joined #openstack-meeting08:51
*** yangyape_ has joined #openstack-meeting08:51
*** phil has joined #openstack-meeting08:52
*** phil is now known as Guest8493408:52
*** yangyapeng has quit IRC08:54
*** subh has joined #openstack-meeting08:54
*** emagana has quit IRC08:56
*** dbecker has joined #openstack-meeting08:56
*** leon_wang has joined #openstack-meeting08:57
*** rossella_s has joined #openstack-meeting08:57
*** yamamoto has joined #openstack-meeting08:58
*** akihito has quit IRC08:58
*** rcernin has joined #openstack-meeting08:58
*** Guest84934 has quit IRC09:00
yuval#startmeeting karbor09:00
openstackMeeting started Tue Dec 20 09:00:45 2016 UTC and is due to finish in 60 minutes.  The chair is yuval. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: karbor)"09:00
openstackThe meeting name has been set to 'karbor'09:00
*** chenying has joined #openstack-meeting09:01
yuvalHello everybody, and welcome to Karbor's weekly meeting09:01
*** edisonxiang has joined #openstack-meeting09:01
chenyinghi09:01
edisonxianghi09:01
leon_wanghi09:01
*** zengchen has joined #openstack-meeting09:01
yuvalsaggi will not be here today09:01
yuvalzhonghua: here?09:02
zhonghuahi09:02
chenyingyinwei said that she will come later.09:02
yuvalzengchen: zhangshuai: ?09:02
zengchenyuval:i am here.09:02
zengchenyuval:how are you.09:02
yuvalzengchen: fine, thanks :)09:02
yuvalalright09:03
yuval#topic Make fullstack tests voting09:03
*** lpetrut has joined #openstack-meeting09:03
*** openstack changes topic to "Make fullstack tests voting (Meeting topic: karbor)"09:03
yuvalOver the last 2 weeks we had 3 bugs affecting our fullstack tests09:03
yuval1) xenial virtualenv issue 2) gitattributes issue 3) devstack+heat issue09:04
chenyingyou mean that change the voting status of fullstack tests?09:04
yuvalthe gate was out for a long time, and we had to merge patches without taking into account the fullstack gate09:04
yuvalso I was thinking about making the gate voting09:05
yuvalwhat is your opinion?09:05
*** kevinz has quit IRC09:05
*** kevinz has joined #openstack-meeting09:05
chenying+109:06
edisonxiang+109:06
zengchenyuval:but, fullstack can find some error even if all the unit test pass.09:06
yuvalthe only downside, is that if we run into issues like those we had last week, we will not be able to merge patches09:06
chenyingbut now the plugins have not been refactored, some fullstack test have not been run.09:06
yuvalthe other option is leave the gate non-voting, but consider it as mandatory - cores shouldn't merge patches when gate fails09:07
yuvalchenying: only 1 test is being skipped09:07
chenyingyuval: ok09:07
yuvalzengchen: I don't understand your point09:08
zengchenyuval:I agree with you.09:09
*** lpetrut has quit IRC09:09
*** lpetrut has joined #openstack-meeting09:09
yuvalright, next topic09:09
zengchenyuval:but if the issue happened like last week. then how do we do?09:10
yuvalzengchen: fix the gates09:10
chenyingThe fullstack or tempest tests in other projects seam  that is not voting status.09:10
zengchenyuval:+109:10
yuvalchenying: yes, the fullstack/tempest gates seem to be more fragile09:11
*** zhhuabj has joined #openstack-meeting09:11
*** yinwei_computer has joined #openstack-meeting09:12
yuvaluntil we make it voting, or if we decide to leave it as is - please do not merge patches with failing fullstack09:12
yinwei_computerhello, I'm on line now09:13
*** claudiub has quit IRC09:13
yuval#topic Adjust protection plugins09:13
*** openstack changes topic to "Adjust protection plugins (Meeting topic: karbor)"09:13
yuvalwe currently have the following protection plugins to adjust to the protection plugin api:09:13
yuvalcinder backup, image to bank, server to bank09:14
yuvaland write the new network topology to bank plugin09:14
yuvalI've almost finished the cinder backup protection plugin, and upload it as soon as it is complete09:15
yinwei_computerso what's the target of the adjustment?09:15
yuvalyinwei_computer: https://review.openstack.org/348163 was merged09:15
zhonghuayuval: great job09:16
yinwei_computerok, got it09:16
yinwei_computerso every protection plugin should align with the new mechanism09:16
yuvalyinwei_computer: yup09:16
*** e0ne has joined #openstack-meeting09:17
chenying Adjust protection plugins, The vendors also hope that the interface exposed should be simple enough. Do we real need expose all the hooks to them to develop plugins? Can we keep some hooks in the base plugins? Most of time, the vendor only care the mian hook of operation.09:17
yuvalchenying: all the hooks are optional, including the main09:18
yuvalchenying: vendors can simply implement the main hook alone09:18
yinwei_computerI heard that some providers have already developed plugins based on original interfaces.  Will there be an adapter base class to keep their plugins unchanged? @yuval09:18
chenyingyinwei_computer: +109:18
yuvalyinwei_computer: besides the api, there is another change - hooks are synchronous. each hook needs not only to start the work (i.e cinder_client.backups.create ...) but also poll and verify it is complete09:19
*** hashar has joined #openstack-meeting09:19
yinwei_computerso by default, the protection would be serialized instead of on parallel previously?09:19
yuvalyinwei_computer: it will be parallel, in relation to the number of greenthreads in the taskflow executor09:20
*** dmacpher has joined #openstack-meeting09:20
*** amotoki has quit IRC09:21
yinwei_computer@yuval I see.  do you think the adapter solution is feasible?09:21
yuvalyinwei_computer: previously, all work began in the same moment, with no order between different types of resources09:21
yuvalyinwei_computer: it is, but it might require some adaptions on the protection plugin's part09:21
yinwei_computerthe adapter itself will do the adpations work, and thus those existed provider plugins could keep unchanged.09:22
yuvalyinwei_computer: might be possible, but we should consider marking that interface as deprecated09:23
chenyingThe creat_backup/delete_backup/restore_backup these interfaces seam more reasonable and suitable for vendors to understand the logic of plugins. We can consider adding the adapter module in base class.09:23
yinwei_computerif they prefer better control of protection dependencies, they could choose to develop new plugins.  But if not, they could keep it the same.09:23
*** r-mibu has joined #openstack-meeting09:24
yuvalyinwei_computer: chenying: again, the problem is not in the api, but the sync/async nature of the protection plugins09:24
yinwei_computeryuval: agree. so your concern is the effort to maintain two series of interfaces in our code, right?09:25
*** zhhuabj has quit IRC09:25
yuvalyinwei_computer: yes09:26
yinwei_computerchenying: what do you think? maintain two series of interfaces, and we need map the old one into the new model.09:27
yinwei_computerIt seems to me like the compatible issue.09:27
*** zhhuabj has joined #openstack-meeting09:28
chenying maintain two series of interfaces sounds not a good idea.09:28
yinwei_computeror we will support incoming  providers with the simplified interfaces as well?09:28
*** ricolin has quit IRC09:30
chenyingor we will support incoming  providers with the simplified interfaces as well?  I don't understand.09:31
yinwei_computeroption 1: only provide adapter to those old provider plugins;09:31
yinwei_computeroption2: for incoming new provider plugins, we also provider two interfaces: simplified one and full one.09:32
*** amotoki has joined #openstack-meeting09:33
chenyingyuval: what's your opinion?09:33
yuvalHow many vendors we have right now who already wrote protection plugins? I know only about EISOO09:33
*** adiantum has quit IRC09:33
*** nadya has quit IRC09:35
chenyingThe commvalt is developint the plugins base on the old interfaces.09:35
*** amotoki has quit IRC09:35
yuvalchenying: let's start with working with the vendors and try to migrate into the current api09:36
*** matrohon has joined #openstack-meeting09:36
yuvalchenying: shouldn't be that hard, and they can consult with us09:36
yinwei_computeryuval: currently we heard the voice that vendors prefer simplified version interfaces :(09:37
*** adiantum has joined #openstack-meeting09:37
chenyingyinwei_computer: +109:37
yinwei_computerthey prefer an idiot way if they don't have a dependency organization requirement09:37
yuvalI'll send the cinder backup protection plugin, maybe it will be clearer that is shouldn't be much effort to migrate09:38
yinwei_computerI guess the adapter is not an independent interface series, but a reference implementation, like cinder lvm driver.09:39
yinwei_computerok09:39
chenyingok good idea.09:39
yuval#topic Ocata bugs and schedule09:39
*** openstack changes topic to "Ocata bugs and schedule (Meeting topic: karbor)"09:39
yuvalOcata MS2 was last week09:40
yuvalyou can view Ocata schedule here: https://releases.openstack.org/ocata/schedule.html09:40
yuvalJanuary 23-27 is MS309:40
*** phil_ has joined #openstack-meeting09:41
yuvalwe still have unresolved bugs, and worse - unassigned bugs here: https://launchpad.net/karbor/+milestone/ocata09:41
*** phil_ is now known as Guest4517409:41
yuvalಥ_ಥ09:42
*** lpetrut1 has joined #openstack-meeting09:43
chenyingI don't think all the tasks in bug list must be solved in Ocata. If it is a real a problow/error, we need fix it. If it is a optimized task, we can do it later version.09:43
yuvalzengchen: edisonxiang: chenying: yinwei_computer: zhonghua: please assign bugs to yourselves if you think you can handle them soon09:43
*** lpetrut has quit IRC09:43
*** lpetrut1 is now known as lpetrut09:43
yuvalchenying: if you think something can be deferred to pike, can you comment in the bug and/or mark it?09:43
*** shu-mutou is now known as shu-mutou-AWAY09:44
zengchenyinwei_computer:https://bugs.launchpad.net/karbor/+bug/1577698. look at my comment. I think it is resolved now.09:44
openstackLaunchpad bug 1577698 in Karbor "set per request one client for sync protection status" [High,Triaged]09:44
edisonxiangyuval:)09:44
chenyingyuval: OK09:44
*** sridharg has quit IRC09:44
yuvalI see some bugs assigned to Wang Hui and Chen Huayi, which are not very active, I believe09:45
*** thorst has joined #openstack-meeting09:45
*** sridharg has joined #openstack-meeting09:46
yuval#topic Open Discussion09:46
*** openstack changes topic to "Open Discussion (Meeting topic: karbor)"09:46
*** ktychkova_ has joined #openstack-meeting09:46
yuvalanything else? :)09:46
*** ktychkova has quit IRC09:47
yuvalalright, thank you all!09:48
yuvalmay the force be with you09:48
*** lpetrut has quit IRC09:48
yuval#endmeeting09:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:48
openstackMeeting ended Tue Dec 20 09:48:41 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/karbor/2016/karbor.2016-12-20-09.00.html09:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/karbor/2016/karbor.2016-12-20-09.00.txt09:48
openstackLog:            http://eavesdrop.openstack.org/meetings/karbor/2016/karbor.2016-12-20-09.00.log.html09:48
*** zhhuabj has quit IRC09:50
*** mickeys has joined #openstack-meeting09:51
*** Ravikiran_K has joined #openstack-meeting09:53
*** sudipto_ has joined #openstack-meeting09:53
*** sudipto has joined #openstack-meeting09:53
*** thorst has quit IRC09:54
*** lpetrut has joined #openstack-meeting09:56
*** kevinz has quit IRC09:56
*** mickeys has quit IRC09:57
*** nadya has joined #openstack-meeting09:58
*** ktychkova_ has quit IRC10:02
*** yamamoto has quit IRC10:02
*** ktychkova has joined #openstack-meeting10:02
*** lhx_ has quit IRC10:04
*** lhx_ has joined #openstack-meeting10:09
*** GB21 has joined #openstack-meeting10:11
*** rossella_s has quit IRC10:11
*** rossella_s has joined #openstack-meeting10:12
*** irenab has joined #openstack-meeting10:15
*** Julien-zte has quit IRC10:16
*** ociuhandu has quit IRC10:17
*** bkopilov_ has quit IRC10:17
*** yangyape_ has quit IRC10:21
*** adiantum has quit IRC10:21
*** adiantum has joined #openstack-meeting10:21
*** sudipto has quit IRC10:21
*** sudipto_ has quit IRC10:21
*** armax has joined #openstack-meeting10:22
*** guoshan has quit IRC10:24
*** Julien-zte has joined #openstack-meeting10:25
*** Julien-zte has quit IRC10:25
*** adiantum has quit IRC10:25
*** Julien-zte has joined #openstack-meeting10:26
*** Julien-zte has quit IRC10:27
*** Julien-zte has joined #openstack-meeting10:28
*** Julien-zte has quit IRC10:31
*** Julien-zte has joined #openstack-meeting10:32
*** longxion_ has quit IRC10:32
*** longxiongqiu has joined #openstack-meeting10:33
*** claudiub has joined #openstack-meeting10:34
*** Julien-zte has quit IRC10:35
*** Julien-zte has joined #openstack-meeting10:35
*** Julien-zte has joined #openstack-meeting10:36
*** armax has quit IRC10:38
*** GB21 has quit IRC10:40
*** yamahata has quit IRC10:44
*** dmorita has joined #openstack-meeting10:45
*** jklare has quit IRC10:48
*** e0ne has quit IRC10:49
*** e0ne has joined #openstack-meeting10:49
*** dmorita has quit IRC10:50
*** thorst has joined #openstack-meeting10:50
*** mickeys has joined #openstack-meeting10:53
*** Ravikiran_K has quit IRC10:56
*** thorst has quit IRC10:58
*** mickeys has quit IRC10:58
*** gcb has quit IRC10:59
*** yamamoto has joined #openstack-meeting10:59
*** amotoki has joined #openstack-meeting10:59
*** emagana has joined #openstack-meeting11:03
*** astarove has quit IRC11:06
*** emagana has quit IRC11:07
*** GB21 has joined #openstack-meeting11:07
*** acoles_ is now known as acoles11:07
*** yamamoto has quit IRC11:08
*** amotoki has quit IRC11:10
*** longxion_ has joined #openstack-meeting11:13
*** longxiongqiu has quit IRC11:13
*** sdague has joined #openstack-meeting11:20
*** matrohon has quit IRC11:20
*** neiljerram has joined #openstack-meeting11:20
*** guoshan has joined #openstack-meeting11:25
*** guoshan has quit IRC11:29
*** ntpttr has quit IRC11:30
*** adiantum has joined #openstack-meeting11:30
*** ntpttr has joined #openstack-meeting11:34
*** amotoki has joined #openstack-meeting11:40
*** ociuhandu has joined #openstack-meeting11:53
*** mickeys has joined #openstack-meeting11:54
*** prateek has quit IRC11:55
*** thorst has joined #openstack-meeting11:55
*** rtheis has joined #openstack-meeting11:57
*** leon_wang has left #openstack-meeting11:57
*** mickeys has quit IRC11:58
*** subh has quit IRC12:00
*** electrofelix has joined #openstack-meeting12:01
*** thorst has quit IRC12:04
*** Ravikiran_K has joined #openstack-meeting12:06
*** yamamoto has joined #openstack-meeting12:09
*** GB21 has quit IRC12:09
*** yamamoto has quit IRC12:18
*** kjorgensen has joined #openstack-meeting12:19
*** amotoki has quit IRC12:20
*** subh has joined #openstack-meeting12:24
*** kjorgensen has quit IRC12:24
*** subh has quit IRC12:25
*** guoshan has joined #openstack-meeting12:26
*** GB21 has joined #openstack-meeting12:27
*** Julien-zte has quit IRC12:27
*** sdake has joined #openstack-meeting12:28
*** yamamoto has joined #openstack-meeting12:28
*** guoshan has quit IRC12:30
*** dprince has joined #openstack-meeting12:35
*** thorst has joined #openstack-meeting12:38
*** GB21 has quit IRC12:38
*** amotoki has joined #openstack-meeting12:40
*** amotoki has quit IRC12:40
*** amotoki has joined #openstack-meeting12:41
*** ociuhandu has quit IRC12:43
*** ociuhandu has joined #openstack-meeting12:43
*** sshnaidm is now known as sshnaidm|lnch12:47
*** ociuhandu has quit IRC12:48
*** GB21 has joined #openstack-meeting12:50
*** ociuhandu has joined #openstack-meeting12:54
*** mickeys has joined #openstack-meeting12:55
*** gouthamr has joined #openstack-meeting12:55
*** matrohon has joined #openstack-meeting12:56
*** yanyanhu has joined #openstack-meeting12:57
*** mickeys has quit IRC12:59
*** ociuhandu has quit IRC12:59
yanyanhu#startmeeting senlin13:00
openstackMeeting started Tue Dec 20 13:00:12 2016 UTC and is due to finish in 60 minutes.  The chair is yanyanhu. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: senlin)"13:00
openstackThe meeting name has been set to 'senlin'13:00
*** yangyapeng has joined #openstack-meeting13:00
yanyanhuhello13:00
Qiminghi13:00
*** elynn has joined #openstack-meeting13:00
*** zhouzhengxi has joined #openstack-meeting13:01
yanyanhuhi, Qiming13:01
yanyanhuhi, elynn13:01
elynnhi yanyanhu13:01
zhouzhengxiHi yanyanhu.13:01
*** Ruijie_ has joined #openstack-meeting13:01
yanyanhuhi, zhouzhengxi, you're using your full name :)13:01
*** pcaruana has quit IRC13:01
zhouzhengxiHi elynn.13:01
yanyanhuhi, Ruijie_13:01
Ruijie_hi, yanyanhu13:01
*** hoangcx has joined #openstack-meeting13:02
yanyanhulets wait for a while for other attenders13:02
yanyanhuand here is the agenda: https://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Agenda_.282016-12-20_1300_UTC.2913:02
yanyanhuplease feel free to add items13:02
*** lhx_ has quit IRC13:02
yanyanhuok, lets start13:02
yanyanhuhttps://etherpad.openstack.org/p/senlin-ocata-workitems13:03
yanyanhu#topic ocata workitems13:03
*** openstack changes topic to "ocata workitems (Meeting topic: senlin)"13:03
yanyanhuTesting13:03
yanyanhuhaven't work on it13:03
yanyanhuand about rally plugin, Ruijie_ has added the support for cluster scaling13:03
yanyanhunext one13:04
yanyanhuhealth management13:04
yanyanhuxinhui is not here I guess13:04
yanyanhunoticed octavia team have left more comments on xinhui's patch13:05
Qimingone of the workitems is about adding mistral support13:05
yanyanhuah, right13:05
yanyanhuQiming is now working on it13:05
Qimingyup, those are all reasonable comments13:05
yanyanhuabout supporting mistral workflow in senlin13:05
*** zhouzhengxi is now known as zzxwill13:06
yanyanhuthe purpose is leveraging mistral's ability to drive the workflow of failure recovery13:06
zzxwillChanged to my gerrit username. Thanks, yanyanhu.13:06
yanyanhuQiming, is that right?13:06
yanyanhu:)13:06
*** pcaruana has joined #openstack-meeting13:06
yanyanhuzzxwill, :)13:06
Qimingyes, sort of an amendament13:07
Qimingthere are always work we cannot model, for recovery13:07
*** huanxuan has quit IRC13:07
Qimingwe can leave them as user provided hooks13:07
yanyanhuyep13:07
Qimingusers can hook their own workflow, workbook to the recovery process13:07
yanyanhufor users are the only people can decide how to make the recovery in some cases13:08
Qimingthis is the patch: https://review.openstack.org/#/c/412389/13:08
yanyanhuyea, the API version problem13:08
Qimingonce mistral is returning a "discoverable" version, we can identify it in openstacksdk13:09
Qimingthen we add resources into sdk13:09
yanyanhugreat13:09
Qimingand finally, we know how to retrieve and trigger a workflow13:09
*** ociuhandu has joined #openstack-meeting13:09
*** nadya has quit IRC13:09
*** mjturek has joined #openstack-meeting13:09
yanyanhuhow about the current mistral support in sdk?13:10
Qimingnothing yet13:10
yanyanhuneed big effort to complete it?13:10
yanyanhuI see...13:10
Qimingonly a base committed: https://review.openstack.org/#/c/412079/13:10
*** jchhatbar has joined #openstack-meeting13:10
yanyanhumaybe we can start from those basic and necessary ones13:11
Qimingit won't be big I think13:11
yanyanhuok13:11
Qimingfor example, I have completed the whole bare-metal support in about one day: https://review.openstack.org/#/q/project:openstack/python-openstacksdk+message:bare-metal13:12
yanyanhuWoW13:12
Qimingchecked mistral resource types, it is not big13:12
yanyanhuQiming, you're a real superman :P13:12
*** mjturek has quit IRC13:13
yanyanhuthanks a lot for the effort13:13
Qimingone thing I'm not quite sure is whether the API doc for mistral is latest: http://docs.openstack.org/developer/mistral/developer/webapi/v2.html13:13
*** lxinhui has joined #openstack-meeting13:13
*** janki has quit IRC13:13
Qimingneed to double confirm13:13
yanyanhuyes... those API docs are almost the only reference for us...13:14
*** ociuhandu has quit IRC13:14
yanyanhubesides the source code13:14
*** lamt has quit IRC13:14
Qimingem, maybe I was too optimistic, those resources do have a lot of attributes ...13:14
yanyanhuanyway, hope there won't be much difficult13:14
yanyanhuhope their API document is accurate :)13:15
*** Wenzhi has joined #openstack-meeting13:15
Qimingme too13:15
*** sshnaidm|lnch is now known as sshnaidm13:15
yanyanhuoh, I have added this sub workitem to HA section13:15
yanyanhufor further tracking13:15
yanyanhuand will contact xinhui for that patch to octavia13:16
lxinhuihi, yanyanhu13:16
yanyanhuhi, lxinhui :)13:16
lxinhuihave micheal accepted the BP?13:16
yanyanhunice to see you13:16
yanyanhulxinhui, not yet13:16
lxinhuisorry for the late13:16
yanyanhuand their left more comments on that patch13:16
yanyanhulxinhui, no problem13:16
lxinhuilast week, I traveled to Shenzhen for Open-O meetup13:17
yanyanhuI guess they still have some questions about that change13:17
lxinhuiand saw many old friends there13:17
yanyanhufor NFV :)13:17
yanyanhunice13:17
lxinhuithat does not make sense13:17
lxinhuisince BP represents the requriements only13:17
lxinhuiwhich should be speparated with implement13:18
lxinhuiif he has questions about the change13:18
yanyanhulink to the patch: https://review.openstack.org/#/c/402296/13:18
lxinhuiwhy not accpet the BP then leave comments on the change13:18
yanyanhulxinhui, I guess they may want to understand more detail about the change13:19
yanyanhuanyway, BP is the basement13:19
lxinhuiis German one of the core members?13:19
yanyanhulxinhui, not sure13:20
lxinhuithat is what I am discussing13:20
*** annp has joined #openstack-meeting13:20
Qimingtheir suggestions to make notifications configurable is reasonable13:20
lxinhuino matter reasonable or not13:20
yanyanhulxinhui, maybe you can leave some reply on the patch and ask for them for further review on that bp13:20
lxinhuimicheal need approve the BP firstly13:20
lxinhuias his own comment13:21
lxinhuileave it till the BP approved13:21
yanyanhuhave got response from michael and he said they will spend more time to understand it13:21
lxinhuino need to understand the chnage13:21
lxinhuijust echo back to us if he accept the requrirment or not13:21
lxinhui...13:21
lxinhuior lese, I update new patch means nothting13:22
*** lhx_ has joined #openstack-meeting13:23
*** jaypipes has joined #openstack-meeting13:23
*** yanyan has joined #openstack-meeting13:23
yanyansorry, just dropped13:24
Qimingyes, need some clarification on the review13:24
lxinhuiAll of us should go to Alanta13:24
*** ociuhandu has joined #openstack-meeting13:24
lxinhuifor the middle cycle13:24
lxinhuiand f2f coding there :)13:25
yanyanlxinhui, that is diffult for us :( although we really hope so13:25
Qimingor else we will get blocked13:25
yanyandifficult13:25
* Qiming not a strong believer of f2f coding13:25
yanyananyway, having more discussion on that BP is urgent13:26
yanyanwe have only 1 month left for Ocata13:26
yanyanless than 1 month13:26
*** rbowen has quit IRC13:26
lxinhuiYes13:26
Qimingjust leave a comment on that patch13:26
lxinhuianother thing I am trying to get time to do is integrate mistral with Senlin13:26
*** rbowen has joined #openstack-meeting13:26
*** yanyanhu has quit IRC13:26
*** guoshan has joined #openstack-meeting13:26
Qimingwhether we should wait for the BP to be approved before submitting another patchset13:26
yanyanlxinhui, Qiming is working on it too :)13:26
lxinhuiha13:27
lxinhuiI will work with him toegtehr13:27
lxinhuior qiming can handle it13:27
lxinhuiI will do something else13:27
lxinhuisince he is much more familar about SDK13:27
yanyanI think you two can have some discussion to see whether there are some gaps between what we need and what they have13:28
lxinhuiyes13:28
yanyanQiming is now working on sdk support and also need some fixes on mistral itself13:28
lxinhuiyes13:28
yanyanlxinhui, maybe you can consider more from senlin's pespective13:28
*** sudipto_ has joined #openstack-meeting13:28
*** sudipto has joined #openstack-meeting13:28
lxinhuiwe have has a short discussion in the weekend13:28
lxinhuiha13:29
yanyanyes?13:29
Qiminghttps://review.openstack.org/#/c/412389/13:29
lxinhuiabout what you just mentined13:29
Qimingpatch for fixing the version problem13:29
*** adiantum has quit IRC13:29
lxinhuicoo13:30
lxinhuil13:30
lxinhuiThen I can learn that in the vacation13:30
lxinhuiand see what I can help there13:30
yanyanlxinhui, btw, German is not the core reviewer of octavia, but he does contribute a lot to it13:30
yanyanso he should be very familiar with it13:31
*** guoshan has quit IRC13:31
QimingI'd suggest we focus on getting things landed, instead of the people behind it13:31
yanyanQiming, agree totally13:32
yanyanso maybe just reply to the questions13:32
yanyanand have more discussion on the proposal13:32
yanyantry to involve related people13:32
yanyanand see their feedback13:33
*** jaypipes has quit IRC13:33
yanyanif we do all those things but can get it, that won't be our fault13:33
yanyans/can/can't13:33
Qimingleave a comment there13:33
Qimingasking for suggestions13:33
*** huanxuan has joined #openstack-meeting13:34
Qimingshould we wait for bp approval before submitting another patchset?13:34
yanyanthanks Qiming13:34
lxinhuiQiming, That is what I mean by help13:35
lxinhuiyou are the god can do everything13:35
yanyanwe can add octavia's core reviewers to reviewer list13:35
lxinhuiI will see anything can do to help landing13:35
*** pradk has joined #openstack-meeting13:35
*** pradk has quit IRC13:35
lxinhuiWhat comments13:35
yanyangreat, thanks a lot13:35
lxinhuiabout13:35
Qimingcool13:35
lxinhuioctavia?13:36
Qimingyes13:36
lxinhuiwhere is your comments13:36
lxinhuior13:36
lxinhuimistral13:36
Qiming"whether we should wait for the BP to be approved before submitting another patchset"13:36
lxinhuican not see it13:37
lxinhuimaybe metwork problem13:37
yanyancould be gerrit's problem13:37
Qimingnever mind13:37
yanyananyway, hope there can be more progress13:37
yanyanok, so lets move on?13:37
lxinhuiyes, please13:37
yanyandocument, no progress?13:37
yanyanversioned request13:38
*** ociuhandu has quit IRC13:38
yanyansupport for credential_get, get_revision are still unfinished13:38
yanyanwill work on them soon13:38
yanyanall others have been done I think13:38
*** ociuhandu has joined #openstack-meeting13:38
yanyancontainer profile13:39
yanyanQiming's patches have been merged13:39
yanyantwo patches to support dependency between node and profile13:39
yanyanevent/notification13:39
Qimingthere are some more patches about validation13:39
yanyanyes13:40
Qimingblocked now by gate problem13:40
*** pradk has joined #openstack-meeting13:40
yanyanyes, have a topic about this13:40
yanyanreally a headache13:40
yanyanok, lets finish the discussion on workitems first13:40
yanyanconfiguration options for event/notification have been added13:40
yanyanso all basic support has been done I guess? Qiming13:41
yanyanfor event/notification13:41
Qimingyes13:41
Qimingneed to add some documents13:41
yanyanQiming, great13:42
yanyanok, last one13:42
yanyanNFV support/Baremetal cluster13:43
yanyanQiming, do we need further sync with tosca team?13:44
Qimingyes, we'd better do that13:44
yanyanQiming, ok, since the bp for tacker is almost ready(I think), maybe need talk with tosca team for some detail13:45
lxinhuiI think there already have been a disucssion in their weekly meeting13:45
yanyanto support translation between senlin resource and tosca resource13:45
lxinhuiright?13:45
lxinhuihow about that time13:45
Qimingyes, ideally, tosca templates can be translated to senlin profile/policy specs directly13:46
yanyanyes13:46
Qimingbut this will become useless if tacker insists that they will orchestrate things using heat13:46
lxinhui...13:47
yanyanQiming, if they insist, it'ok I think13:47
Qimingyes13:47
Qimingbut some day, they will realize ...13:47
lxinhuiwhy they still insist on the integration13:47
lxinhuiwith heat13:47
lxinhuiinstead of senlin13:47
yanyanjust they wont get benefit from some useful features senlin provide13:47
Qimingit gives them a single dependency13:47
Qimingit makes things a lot simpler13:48
yanyanyes13:48
lxinhuiall the functions they need can be done by Senlin?13:48
yanyanthat's why they reply on heat to deploy everything13:48
Qimingcluster management can and should be done via senlin13:48
yanyanQiming, yes, it is13:49
yanyanjust senlin cluster could be created through heat as well13:49
yanyanas a heat resource13:49
lxinhuiwhat other functions make them dependent on heat>13:49
lxinhui?13:49
lxinhuibesides this13:49
Qimingcombination of things13:49
yanyanlxinhui, network, storage, etc.13:49
lxinhui...13:50
lxinhuionce we discussed this13:50
lxinhuiright when Qiming mention the resource pool management13:50
Qimingthey don't get my metaphor: heat provides you a struct, while senlin provides you an array13:50
*** ociuhandu has quit IRC13:50
lxinhuithey do not need maybe13:50
lxinhuior identify the importance13:50
Qimingthey will first try model everything as a struct, that is fine13:50
Qimingjust a little worried about their future changes, .... maybe I'm worrying too much13:51
lxinhuicould you give me an example of "model everything as a struc"13:51
yanyanQiming, anyway. senlin will be the backend service to manage cluster resource13:51
Qiming....13:51
yanyanthat will be helpful for them13:51
Qimingevery resource combined into a template, deployed as a stack13:52
lxinhui...13:52
Qimingthat is a struct, lxinhui, right?13:52
lxinhui.....13:52
*** hichihara has joined #openstack-meeting13:52
lxinhuianyway13:52
*** longxion_ has quit IRC13:52
lxinhuiI agree to extend Senlin for more network/storage13:52
lxinhuifunctions13:52
Qimingoperating a cluster thru heat is doable, but you are losing all the operations we have worked hard to provide13:52
lxinhuias a real resource manager13:53
Qimingactually we can13:53
lxinhuibut not today13:53
*** Julien-zte has joined #openstack-meeting13:53
Qimingit is not about things we CAN do, it is really about things we SHOULD do or NOT13:53
yanyanQiming, yes, that's the point13:54
lxinhuithen you can not claim senlin as a resource manager13:54
Qiminge.g. we can invoke libvirt directly, bypassing nova13:54
lxinhuias a resource manager13:54
lxinhuiyou need consider different kinds of reosurces13:54
Qimingso that we can manage physical hosts, and do VM placement13:54
Qiming:D13:54
lxinhuiyou need to think how to control them13:54
lxinhuireserve13:54
lxinhuiand so on13:55
lxinhuior it just a toy13:55
Qimingso far I still believe we should focus on getting cluster management done13:55
lxinhuito let audience to know13:55
lxinhuithat is good to use it for clusteting management13:55
lxinhuisince13:55
yanyankinda agree with Qiming, lets just well play our role as clusering service in current stage  :)13:56
lxinhuiclustering should not be only a group of somethin,,13:56
*** mickeys has joined #openstack-meeting13:56
Qimingthinking from users perspective13:56
lxinhuibut also managemet functions related to it13:56
lxinhuiI am a user13:56
Qimingwe can somehow extend the nova server profile13:56
lxinhui:)13:56
*** ihrachys has joined #openstack-meeting13:56
*** cleong has joined #openstack-meeting13:57
Qimingto add more useful features regarding storage and network13:57
lxinhuiyes13:57
lxinhuireason why every company want hire nove dev13:57
yanyanok, 2 minutes left, guys :)13:57
Qimingwe don't have to get ourselves limited/constrained by the abstractions provided by a single service (e.g. nova)13:57
lxinhuibecause it is indepensible13:58
Qimingif users need a nova server with a floating IP13:58
lxinhuiI am trying to think the way to make senlin indepensible13:58
Qimingwe should add add a floating IP property to nova server profile13:58
lxinhuiinstead of some toolkit nice to have13:58
*** jlibosva has joined #openstack-meeting13:59
Qiming... openstack is not indispensible ...13:59
lxinhuimore than that13:59
*** jungleboyj has joined #openstack-meeting13:59
lxinhuiprecondition is openstack is alreay chosed13:59
*** GB21 has quit IRC13:59
lxinhuithen senlin should be chosed13:59
QimingI agree13:59
elynnMaybe at least make it indispensable at NFV world13:59
Qiming:D13:59
lxinhuithat is what I mean13:59
lxinhuiagree elynn13:59
yanyanhi, since time is almost over, lets move back to senlin channel for further discussion?13:59
*** GB21 has joined #openstack-meeting14:00
*** korzen has joined #openstack-meeting14:00
*** sudipto_ has quit IRC14:00
*** sudipto has quit IRC14:00
*** john-davidge has joined #openstack-meeting14:00
yanyanthanks all you guys for joining, lets move back the senlin channel14:00
yanyan#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
Qimingpeople still prefer joining big, famous projects, :)14:00
openstackMeeting ended Tue Dec 20 14:00:31 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-12-20-13.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-12-20-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-12-20-13.00.log.html14:00
*** mickeys has quit IRC14:00
jlibosvaHello friends of Neutron :)14:00
jlibosvaLet's get started14:01
john-davidgeHi14:01
*** Ruijie_ has left #openstack-meeting14:01
jlibosva#startmeeting networking14:01
openstackMeeting started Tue Dec 20 14:01:08 2016 UTC and is due to finish in 60 minutes.  The chair is jlibosva. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
bzhaohello14:01
*** openstack changes topic to " (Meeting topic: networking)"14:01
openstackThe meeting name has been set to 'networking'14:01
amotokihi14:01
hichiharahi14:01
hoangcxHi14:01
ihrachyso/14:01
bcafarelhello14:01
*** Ruijie_ has joined #openstack-meeting14:01
jlibosva#topic Announcements14:01
korzenhello14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
dasanindHi14:01
annphi14:01
jlibosvaWe have a new mechanism for branch management14:01
jlibosva#link http://lists.openstack.org/pipermail/openstack-dev/2016-December/108923.html14:01
jlibosvaPlease have a look14:01
*** rbudden has joined #openstack-meeting14:02
jlibosvaIt basically means we'll be able to create new feature or stable branches by sending patches to gerrit14:02
jlibosvaPretty cool14:02
ihrachysyay, we asked for it for cycles14:02
amotoki+10014:02
jlibosvaThere is a proposal to introduce nova-compute-api14:02
jlibosva#link https://review.openstack.org/#/c/411527/114:02
jlibosvaIt can be relevant to us in the meaning of how we interact with nova when plugging a new port14:03
jlibosvaNext announcement14:03
jlibosvaNew dates for PTL nominations and elections for Pike are now on review14:03
jlibosva#link https://review.openstack.org/#/c/404275/14:03
*** trevormc has joined #openstack-meeting14:04
trevormco/14:04
jlibosvaThere is also a discussion about new goal for Pike about supporting Python 3.514:04
dasmjlibosva: are you suggesting to dethrone armax? :)14:04
jlibosvadasm: no! Just setting dates in which we're gonna support armax to run for PTL for another cycle :-P14:05
dasm\o/14:05
ihrachyshehe14:05
bzhao:)14:05
ihrachysjlibosva: re python3, are you going to take care of it? ;)14:05
jlibosva#link https://review.openstack.org/#/c/349069/714:05
jlibosvaPython3 link ^^14:05
ihrachysI think we may need to set up another job for py3 neutron mode14:06
*** fguillot has joined #openstack-meeting14:06
dasmah right.. i thought we have it already, but it's just for unittests.14:06
jlibosvamaybe, that's planned for Pike though :)14:06
jlibosvaright, we do run unittests but they don't guarantee you can run your cloud on Py3 :)14:06
ajolate o/14:07
*** lblanchard has joined #openstack-meeting14:07
ihrachysyeah, but since it may take some time, I would suggest our testing lieutenant to start poking it already14:07
jlibosvaihrachys: ok, I'll poke him :)14:07
dasmheh14:07
dasm*hehe14:07
ihrachysjlibosva: him?? :)14:07
jlibosvaNext good news announcement14:07
jlibosvaOur Neutron team is growing, we have new members in go-to contacts for certain areas14:08
*** mtanino has quit IRC14:08
jlibosvaSpecifically abhiraut is a new contact for clients14:08
jlibosvamlavalle is now L3 lieuteant14:08
*** askb has quit IRC14:08
jlibosvaAnd for services we have tidwellr and njohnston14:08
jlibosvaCongratulations to all and keep up with the good work :)14:08
ihrachysnice to see the team regaining for late drop-offs14:09
jlibosvaYou can see updated list of contacts here:14:09
*** boden has joined #openstack-meeting14:09
rossella_scongratulations!14:09
jlibosvahttps://github.com/openstack/neutron/blob/master/doc/source/policies/neutron-teams.rst#core-review-hierarchy14:09
bzhaoawesome14:09
trevormchaleyb was also added tl L314:09
trevormcto L3* right?14:09
ajocongratulations :)14:10
jlibosvatrevormc: oh, right! Thanks14:10
trevormcdidnt want to leave anyone out, congrats to all14:10
*** nadya has joined #openstack-meeting14:10
jlibosvaso also congratulations haleyb-away14:10
annpcongratulations :)14:10
*** sdake_ has joined #openstack-meeting14:10
jlibosvaThe last announcement is that we're out of Ocata-2 milestone14:11
jlibosvaWhich means we should now focus on o-3 bugs and features14:11
jlibosvaThe list of o-3 seems empty so far but I'd expect it's gonna be filled soon14:11
*** sdake has quit IRC14:12
jlibosvaanybody wants to announce anything?14:12
jlibosva#topic Blueprints14:12
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:12
*** electrocucaracha has joined #openstack-meeting14:12
*** lamt has joined #openstack-meeting14:13
*** egallen has joined #openstack-meeting14:13
jlibosvaThere are some blueprints tagged for o-214:13
jlibosvawhich weren't finished, I assume they are gonna be flipped to o-314:13
jlibosvahttps://launchpad.net/neutron/+milestone/ocata-214:13
jlibosvaIs there anybody who gets his BP work blocked by anything or any important patches that lack reviews?14:14
hoangcxSecurity Group Logging is ready to go and really need to get more attention from cores.14:14
hoangcx#link https://review.openstack.org/#/c/203509/14:15
jlibosvahoangcx: thanks for raising this14:15
hoangcxThanks rossella_s for helping the work as approver14:15
bodenAlso the diagnostics spec is ready for some core reviews; it’s currently a bit rough, but once we can get some direction from cores I’ll solidify it..  https://review.openstack.org/#/c/308973/14:15
*** Wenzhi has quit IRC14:16
*** nadya has quit IRC14:16
jlibosvahttps://review.openstack.org/#/c/308973/14:16
jlibosva^ fixed link for diagnostics :)14:16
ihrachysrossella_s: how close are we for logging spec to merge?14:16
jlibosvathanks boden14:16
rossella_shoangcx, my pleasure14:16
amotokihoangcx: I was requested to review it from yushiro and will check the spec in a couple of days.14:16
*** Wenzhi has joined #openstack-meeting14:16
*** rasca has quit IRC14:16
ihrachysamotoki: hey! nice to see you back!14:17
hoangcxamotoki, Thanks a lot :-)14:17
amotokiI will check it from the API perspective.14:17
rossella_sihrachys, from my point of view it's ok but I would like to get more eyes on it14:17
rossella_samotoki, welcome back14:17
ihrachysrossella_s: I believe your +2 would help to get that attention :)14:17
amotokithanks. sorry for my absense.14:17
korzenhow about port binding for Live Migration? https://review.openstack.org/40429314:18
rossella_sihrachys, technically I am not a driver...don't think I am allowed to +214:18
*** rasca has joined #openstack-meeting14:18
ihrachysrossella_s: any core is allowed to +2, you just can't merge14:18
korzenis port binding for LM going to happen in Ocata?14:18
rossella_sihrachys, cool14:18
ihrachysrossella_s: and since you are an approver for the feature, it only makes sense for you to assess it for merge14:18
*** baoli has joined #openstack-meeting14:18
hoangcxihrachys, Oh, Thanks for clarifying the point14:19
amotokikorzen: what does LM mean?14:19
rossella_sihrachys, great, will do then14:19
hichiharaI'm watching the spec as well. I also wait rossella_s's +2 :)14:19
*** baoli has quit IRC14:19
ihrachysamotoki: live migration14:19
*** VW has joined #openstack-meeting14:19
jlibosvakorzen: is this the spec https://review.openstack.org/#/c/309416/ ?14:19
rossella_ssorry for my misunderstanding14:19
amotokiI see. a lot of abbreviation14:19
*** baoli has joined #openstack-meeting14:19
*** Ruijie__ has joined #openstack-meeting14:20
korzenjlibosva, ye14:20
dasanindkorzen: we have made some good progress for live migration14:20
*** tuhv has joined #openstack-meeting14:20
*** tuhv has quit IRC14:20
jlibosvaso that needs to go in first before code patches get in14:20
korzenand we have only 4 weeks14:21
*** tuhv has joined #openstack-meeting14:21
*** Wenzhi has quit IRC14:21
korzenwe should think of online data migration for that one14:21
ihrachysI think it's a classic case of no owner/approver14:21
ihrachysfor blueprints, we have a person to help with landing14:22
ihrachysfor bare RFEs we don't14:22
jlibosvaWould creating a blueprint help with prioritizing the work?14:22
jlibosvaoh, there is an rfe, sorry14:22
dasanindkorzen: here is the WIP patch for live migration https://review.openstack.org/#/c/404293/14:22
ihrachysjlibosva: I think that's worth exploring, at least raising the flag to armax about it14:22
*** Ruijie_ has quit IRC14:22
*** prateek has joined #openstack-meeting14:23
jlibosva#action jlibosva to talk with armax about prioritizing live migration14:23
*** pcaruana has quit IRC14:23
jlibosvaany other blueprints that lack attention?14:23
*** yanyan has quit IRC14:23
ihrachysI will use a separate slot for OVO stuff14:24
*** longxiongqiu has joined #openstack-meeting14:24
jlibosvaihrachys: I was just about to ask about it as there are no patches linked on wiki14:24
jlibosva#topic OVO/no API downtime14:24
*** openstack changes topic to "OVO/no API downtime (Meeting topic: networking)"14:24
jlibosvaihrachys: lead the show14:24
ihrachysok, sec14:24
*** salv-orlando has joined #openstack-meeting14:24
ihrachysthere was some progress done on OVO from the prev Monday14:25
*** ayogi has quit IRC14:25
ihrachysthanks for all reviewers who stepped in!14:25
ihrachysthere are some more patches in the queue that would benefit from some core reviewer attention14:25
*** lxinhui has quit IRC14:25
ihrachys1. switching flavour service plugin to OVOs: https://review.openstack.org/#/c/306685/14:25
*** jamesdenton has joined #openstack-meeting14:25
ihrachys2. there are also several patches in the queue for ml2 type drivers that depend on https://review.openstack.org/#/c/398873/ going in14:26
jlibosva#link https://review.openstack.org/#/c/306685/14:26
jlibosva#link https://review.openstack.org/#/c/398873/14:26
ihrachysI see ataraday just respinned it so it's probably good to go14:26
ihrachysI will review the patch after the meeting, and I hope someone else does it too14:26
ihrachysI think the patch was advertised as breaking on ML and during prev team meetings, so it should be fine14:27
ihrachyswe of course will check stadium grafana boards before pulling the lever14:27
*** guoshan has joined #openstack-meeting14:27
ihrachysI think that's mostly it for broader team, we will spin a bit more internally before asking for more attention14:27
jlibosvathanks ihrachys14:27
ihrachyspassing the show back14:27
jlibosva#topic Bugs and gate failures14:28
*** openstack changes topic to "Bugs and gate failures (Meeting topic: networking)"14:28
jlibosvaBug deputy for the last week was mlavalle14:28
jlibosvaBut I see he's not connected14:28
*** Ruijie__ has quit IRC14:28
ihrachysyeah. I think we had that ask to send email reports if not present during irc meeting14:28
*** Ruijie__ has joined #openstack-meeting14:28
ihrachyswas it ever documented?14:28
jlibosvaI don't think that's documented14:29
ihrachysok I can check it and propose a patch if not14:29
*** dmorita has joined #openstack-meeting14:29
jlibosva#action ihrachys to check bug deputy policy and whether it's advised to send email if not attending weekly irc meeting14:30
jlibosvathanks ihrachys for checking14:30
jlibosvawe have john-davidge bug deputy this week14:30
john-davidgejlibosva: Hi14:31
jlibosvaand we already have set a bug deputy for the next week - our mighty PTL armax will serve over Christmas14:31
jlibosvajohn-davidge: hi :)14:31
john-davidgejlibosva: Pretty quiet so far this week :)14:31
jlibosvajust updating about bug deputy role14:31
*** guoshan has quit IRC14:31
jlibosvajohn-davidge: good :) maybe people are already taking time off for Christmas14:32
*** links has quit IRC14:32
ihrachysjohn-davidge: if you think it's quiet, swap chairs with armax!14:32
ihrachysthat will surely be quiet ;)14:32
jlibosvaI checked open launchpad bugs for gate-failures and most of them are fixed by now14:32
jlibosvaWe have gate failure open to dvr https://bugs.launchpad.net/neutron/+bug/1649867 though that doesn't have any assignee14:32
openstackLaunchpad bug 1649867 in tempest "Gate tempest dsvm neutron dvr test fails" [Undecided,Incomplete]14:32
*** zzxwill has quit IRC14:32
jlibosvaas per comments it might be issue related to some other existing bug14:33
jlibosvaany volunteers to look at this one?14:33
ihrachysit's a dup14:33
ihrachysbug in libvirtd14:33
ihrachyssince xenial switch, the hypervisor is in xenial14:33
ihrachyssorry, in denial14:33
ihrachys:)14:33
jlibosvaihrachys: do we have a bug # for it?14:34
*** dmorita has quit IRC14:34
ihrachysbug 164677914:34
openstackbug 1646779 in tempest "libvirt killed by kernel on general protection or stack segment traps" [Undecided,Incomplete] https://launchpad.net/bugs/164677914:34
ihrachyswe landed an elastic-recheck query for that lately: https://review.openstack.org/40627814:34
ihrachysthat should capture all new failures14:34
ihrachysif not, consider tweaking the query14:34
jlibosvaihrachys: good stuff, thanks14:35
jlibosvaanybody noticed any other failures or bugs worth highlighting?14:35
ihrachysI have small thing14:36
ihrachysnot a breakage, yet, but gate related14:36
ihrachyswe have those scenario jobs in experimental queue14:36
ihrachysboth dvr as well as non dvr14:36
ihrachysit turned out that our gate hook always enables dvr tests even for non-dvr setups14:37
ihrachyswhich breaks those jobs if we land DVR scenarios14:37
*** pcaruana has joined #openstack-meeting14:37
ihrachysso I was working lately on tweaking our gate hook to enable the tests only when DVR is configured for the job14:37
*** priteau has quit IRC14:37
ihrachysthe result is https://review.openstack.org/#/q/status:open++branch:master+topic:dvr-scenario and I am happy to see reviews14:37
ihrachysEOM14:38
jlibosvaihrachys: thanks for update14:38
jlibosva#link https://review.openstack.org/#/q/status:open++branch:master+topic:dvr-scenario14:38
jlibosvaI'll also have a look after meeting14:38
ihrachysthanks14:38
*** clayton has quit IRC14:38
jlibosva#topic Docs14:39
*** openstack changes topic to "Docs (Meeting topic: networking)"14:39
*** VW has quit IRC14:39
jlibosvaI don't see Sam-I-Am around14:39
dasmjlibosva: afair, john-davidge is docs liaison14:39
ihrachysI think someone was to take it over from him?14:39
ihrachysright, john-davidge!14:39
jlibosvaaaah14:39
jlibosvajohn-davidge: hi again :)14:39
*** VW has joined #openstack-meeting14:39
john-davidgejlibosva: Hello again :)14:39
jlibosvajohn-davidge: do you want to give any updates about docs?14:40
*** clayton has joined #openstack-meeting14:40
john-davidgejlibosva: A couple of patches to highlight for reviews:14:40
*** ataraday_ has joined #openstack-meeting14:40
john-davidge#link https://review.openstack.org/#/c/411463/14:40
amotokishortcut for networking guide reviews:14:41
amotoki#link https://review.openstack.org/#/q/status:open+project:openstack/openstack-manuals+path:%255Edoc/networking-guide/.*14:41
*** jungleboyj has quit IRC14:41
john-davidgeAnd if anyone has a working auto-allocation-enabled environment I'd appreciate a thumbs up/down on this one: https://review.openstack.org/#/c/410493/14:41
john-davidgeHaven't had much luck getting a dev env working for that myself14:42
john-davidgeThat's it from me. The transition to OSC commands continues at a good pace.14:43
john-davidgeThanks ankur-gupta-f!14:43
jlibosvajohn-davidge: thanks for update :)14:43
*** eharney has quit IRC14:43
jlibosvasince you mentioned it14:44
jlibosva#topic Transition to OSC14:44
*** openstack changes topic to "Transition to OSC (Meeting topic: networking)"14:44
jlibosvajohn-davidge: is there anything to update beside it continues at a good pace? :)14:44
*** bobmel_ has joined #openstack-meeting14:45
john-davidgejlibosva: Aha, I'll defer to amotoki on that14:45
amotokihehe14:45
jlibosvaamotoki: hello :)14:45
amotokiI haven't grabbed the status on OSC transition while I was absent...14:46
*** ykatabam has quit IRC14:46
amotokibut I am checking the status this week and will report before the next meeting.14:46
ihrachysI think john-davidge mentioned docs transition to providing examples with OSC instead of neutronclient CLI14:46
ihrachysnot transition itself14:46
jlibosvaamotoki: ok, thanks. And welcome back, it's good to have you :)14:46
amotokiihrachys: that's true, but checking documents is one of the works of OSC transition.14:47
amotokiit helps us identify the gap.14:47
*** jmckind has joined #openstack-meeting14:47
*** tuhv has quit IRC14:47
*** ociuhandu has joined #openstack-meeting14:47
jlibosva#topic Neutron-lib and planned neutron refactoring14:48
*** openstack changes topic to "Neutron-lib and planned neutron refactoring (Meeting topic: networking)"14:48
jlibosvaHenryG: are you around?14:48
*** bobmel has quit IRC14:48
HenryGI am14:48
*** Guest67717 is now known as med_14:48
ihrachyslol14:48
*** med_ has quit IRC14:48
*** med_ has joined #openstack-meeting14:48
ihrachysneutron is not going to let you off, never14:48
*** donghao has joined #openstack-meeting14:49
HenryGI know o_O14:49
bodenI can add a few neutron-lib details if HenryG doesn’t have any14:49
jlibosvaboden: that would be good :)14:49
HenryGI will defer to boden14:49
*** GB21 has quit IRC14:49
jlibosvaHenryG: sorry for pinging :D14:49
*** Ruijie_ has joined #openstack-meeting14:50
bodenwe recently had some neutron-lib hacking check patches land. There’s still some related work in progress but I’d encourage folks to have a look at:14:50
boden#link https://github.com/openstack/neutron-lib/blob/master/doc/source/usage.rst14:50
*** Ruijie__ has quit IRC14:50
bodena number of the patches for review now are related to api-def for subprojects and for neutron extensions14:50
*** longxiongqiu has quit IRC14:50
bodenI’ve noticed a few core reviewers on neutron-lib patches, but would encourage other cores to try and find a little time to review the lib patches14:51
ihrachysboden: dasm: what's the release plan for those bits we landed already?14:51
amotokiboden: that's my fault. I am taking some of them over and rebasing for reviews.14:51
*** fnaval has joined #openstack-meeting14:51
dasmihrachys: neutron-lib is planned to be released after xmas14:51
dasmihrachys: prob 1st, 2nd week of Jan14:51
*** sshnaidm is now known as sshnaidm|afk14:52
ihrachysok I hope it will not take till o-3 and we will have some more time till final Ocata release14:52
ihrachysso that we have time to fix any issues we unveil with adoption of new bits14:52
*** flip214 has quit IRC14:52
dasmin that case, we should double confirm with armax, who decided about deferring it till next year.14:52
dasmbut i believe we will have enough time to verify it before o314:53
bodendasm: we actually did discuss with armax the other day..> I can tryh to find the IRC log14:53
ihrachysno, I think it's correct to defer to after xmas14:53
ihrachysjust hopefully not to after o3 :)14:53
dasmboden: afair, reedip was also involved in this. and armax decided it should be after xmas14:53
* dasm looking through logs for details14:54
bodendasm: that’s what I remember too14:54
*** shintaro has joined #openstack-meeting14:54
amotokiJan 16-20 is the week of lib freeze and it sounds a good idea to release neutron-lib in 1st or 2nd week of Jan.14:54
bodensearch for ‘release of neutron-lib’ in #link http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2016-12-15.log.html14:55
bodenfor a discussion of release dates for neutron-lib14:55
*** zz_dimtruck is now known as dimtruck14:55
dasmboden: http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2016-12-15.log.html#t2016-12-15T21:48:0014:55
*** fzdarsky has joined #openstack-meeting14:55
ihrachysack. 5 mins!14:55
dasmamotoki: ack14:56
ataraday_Hi, everyone! sorry, for being very late... Can I ask for some attention for this refactoring change https://review.openstack.org/#/c/398873/? This refactor is need for refactor of segments db. Which is needed for new engine facade14:56
jlibosvagood to have this cleared :) Any other updates about lib?14:56
bodenI don’t have any other lib updates myself14:56
*** mickeys has joined #openstack-meeting14:56
jlibosvaboden: thanks14:56
jlibosva#topic Open discussion14:56
*** openstack changes topic to "Open discussion (Meeting topic: networking)"14:57
ihrachysataraday_: yeah, I mentioned that before. I will review14:57
bodenataraday_ I’ll try to make a pass through the libimpact patches today14:57
ataraday_ihrachys, boden Thanks!14:57
*** mlavalle has joined #openstack-meeting14:57
jlibosvaThe on demand agenda is empty14:57
jlibosvaanybody has any topic he'd like to discuss?14:57
jlibosvawe have 2 minutes :)14:57
ihrachysthen we can use 3 mins for coffee woot14:57
jlibosvaor we can sing chorals14:58
dasmenjoy xmas time folks!14:58
dasmbtw. any updates on next meetings?14:58
dasmive seen, ihrachys sent message that upgrades one is cancelled14:58
amotokiI think everyone is having coffee or some during the meeting :)14:58
ihrachysthat's prolly armax to ask14:58
ihrachysbut I don't expect one in next week ;)14:58
jlibosvaI would expect next meeting to be cancelled. I guess armax will send an email :)14:58
mlavalledanm, did I miss the meeting?14:59
jlibosvamlavalle: nope, you still have a minute14:59
ihrachyshaha14:59
john-davidgemlavalle: now 30 seconds :)14:59
ihrachysand counting14:59
mlavallesorry, I thought it was now14:59
dasmmlavalle: yes. we tried to praise you, but because you've missed it... you don't get anything14:59
*** korzen has quit IRC14:59
john-davidgeHappy holidays everyone!14:59
mlavalleas far as bugs, it was relatevile quiet14:59
jlibosvaok, thanks folks for showing up :) Enjoy Christmas14:59
*** thorst has quit IRC14:59
hichiharabye14:59
bzhaobye, happy christmas14:59
trevormcthanks15:00
dasmthanks all15:00
*** boden has left #openstack-meeting15:00
electrocucarachathanks15:00
jlibosvamlavalle: thanks for update! :)15:00
jlibosva#stopmeeting15:00
dasanindHappy holidays thank you15:00
hoangcxthanks15:00
annpHappy Xmas, bye15:00
dasmjlibosva: wrong command :)15:00
amotokijlibosva: endmeeting instead15:00
jlibosva#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Tue Dec 20 15:00:24 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-12-20-14.01.html15:00
dasm\o/15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-12-20-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-12-20-14.01.log.html15:00
*** mcunietti has joined #openstack-meeting15:00
jlibosvadasm: amotoki thanks :D15:00
amotoki:)15:00
*** electrocucaracha has left #openstack-meeting15:00
*** Ruijie_ has quit IRC15:00
*** hichihara has quit IRC15:01
*** bobh has quit IRC15:01
*** john-davidge has left #openstack-meeting15:01
*** mickeys has quit IRC15:01
*** hoangcx has quit IRC15:02
*** eharney has joined #openstack-meeting15:04
*** annp has quit IRC15:05
*** dimtruck is now known as zz_dimtruck15:05
*** thorst has joined #openstack-meeting15:06
*** rbartal has quit IRC15:07
*** acoles is now known as acoles_15:08
*** raildo has joined #openstack-meeting15:09
*** longxiongqiu has joined #openstack-meeting15:11
*** eharney has quit IRC15:12
*** fzdarsky_ has joined #openstack-meeting15:13
*** matrohon has quit IRC15:14
*** tlaxkit has joined #openstack-meeting15:14
*** acoles_ is now known as acoles15:15
*** longxiongqiu has quit IRC15:15
*** jaugustine has joined #openstack-meeting15:17
*** Drankis has joined #openstack-meeting15:21
*** zhouzhengxi has joined #openstack-meeting15:23
*** nmagnezi_ has joined #openstack-meeting15:24
*** nmagnezi has quit IRC15:25
*** sshnaidm|afk is now known as sshnaidm15:27
*** armax has joined #openstack-meeting15:27
*** nadya has joined #openstack-meeting15:27
*** guoshan has joined #openstack-meeting15:28
*** nadya has quit IRC15:28
*** tlaxkit has quit IRC15:29
*** ayoung has quit IRC15:30
*** ayoung has joined #openstack-meeting15:30
*** mcunietti has left #openstack-meeting15:31
*** dprince has quit IRC15:31
*** guoshan has quit IRC15:32
*** mtanino has joined #openstack-meeting15:32
*** nklenke has joined #openstack-meeting15:33
*** ayoung has quit IRC15:34
*** ayoung has joined #openstack-meeting15:34
*** eharney has joined #openstack-meeting15:34
*** huanxuan has quit IRC15:35
*** neiljerram has quit IRC15:35
*** nadya has joined #openstack-meeting15:38
*** nadya has quit IRC15:42
*** emagana has joined #openstack-meeting15:43
*** julim has quit IRC15:44
*** caboucha has joined #openstack-meeting15:45
*** rbartal has joined #openstack-meeting15:48
*** harlowja has joined #openstack-meeting15:49
*** shintaro has quit IRC15:52
*** shintaro has joined #openstack-meeting15:54
*** shintaro has quit IRC15:55
*** tommylikehu_ has quit IRC15:56
*** mickeys has joined #openstack-meeting15:57
*** iyamahat has joined #openstack-meeting15:58
*** jchhatbar has quit IRC15:58
*** jungleboyj has joined #openstack-meeting15:58
*** zhouzhengxi has quit IRC15:58
*** yuval has quit IRC16:00
*** hongbin has joined #openstack-meeting16:01
*** tuan_luong has joined #openstack-meeting16:01
*** markvoelker_ has joined #openstack-meeting16:01
*** diablo_rojo has joined #openstack-meeting16:02
*** mickeys has quit IRC16:02
*** markvoelker has quit IRC16:03
*** baoli has quit IRC16:03
*** markvoelker has joined #openstack-meeting16:04
*** prateek_ has joined #openstack-meeting16:05
*** baoli has joined #openstack-meeting16:06
*** markvoelker_ has quit IRC16:07
*** prateek has quit IRC16:08
*** bkopilov has quit IRC16:09
*** anilvenkata has quit IRC16:14
*** saisrikiran has joined #openstack-meeting16:15
*** diga has joined #openstack-meeting16:16
*** bkopilov has joined #openstack-meeting16:20
*** clayton has quit IRC16:21
*** vishnoianil has joined #openstack-meeting16:22
*** clayton has joined #openstack-meeting16:22
*** bobh has joined #openstack-meeting16:23
*** nmagnezi_ is now known as nmagnezi16:23
*** nadya has joined #openstack-meeting16:24
*** tommylikehu_ has joined #openstack-meeting16:24
*** tuan_luong has quit IRC16:26
*** prateek_ has quit IRC16:27
*** prateek has joined #openstack-meeting16:27
*** baoli has quit IRC16:28
*** guoshan has joined #openstack-meeting16:29
*** nmagnezi has quit IRC16:29
*** thorst has quit IRC16:31
*** thorst has joined #openstack-meeting16:31
*** cody-somerville has joined #openstack-meeting16:32
*** cody-somerville has quit IRC16:32
*** cody-somerville has joined #openstack-meeting16:32
*** saisrikiran has quit IRC16:33
*** ^Gal^ has quit IRC16:33
*** ^Gal^_ has joined #openstack-meeting16:33
*** ^Gal^_ is now known as ^Gal^16:33
*** guoshan has quit IRC16:33
*** andreas_s has quit IRC16:33
*** bobh has quit IRC16:34
*** TxGirlGeek has joined #openstack-meeting16:35
*** trevormc has quit IRC16:39
*** thorst has quit IRC16:40
*** ^Gal^ has quit IRC16:42
*** harlowja has quit IRC16:42
*** reedip_ has joined #openstack-meeting16:43
*** sridharg has quit IRC16:50
*** Julien-zte has quit IRC16:51
*** Julien-zte has joined #openstack-meeting16:51
*** Julien-zte has quit IRC16:51
*** rtheis has quit IRC16:54
*** igordcard has joined #openstack-meeting16:56
*** zz_dimtruck is now known as dimtruck16:56
*** igordcard has quit IRC16:56
*** mickeys has joined #openstack-meeting16:58
*** igordcard has joined #openstack-meeting16:58
*** igordcard has quit IRC16:58
*** igordcard has joined #openstack-meeting16:59
*** igordcard has quit IRC16:59
*** igordcard has joined #openstack-meeting17:00
*** igordcard has quit IRC17:01
*** comay has quit IRC17:01
*** bkopilov_ has joined #openstack-meeting17:01
*** kjorgensen has joined #openstack-meeting17:02
*** igordcard has joined #openstack-meeting17:02
*** bkopilov has quit IRC17:02
*** mickeys has quit IRC17:02
*** Guest14972 has quit IRC17:03
*** julim has joined #openstack-meeting17:04
*** dimtruck is now known as zz_dimtruck17:06
*** e0ne has quit IRC17:08
*** Guest45174 has quit IRC17:14
*** rtheis has joined #openstack-meeting17:16
*** eharney has quit IRC17:17
*** eharney has joined #openstack-meeting17:18
*** lpetrut has quit IRC17:18
*** rtheis has quit IRC17:19
*** frasantoro has quit IRC17:20
*** galstrom_zzz is now known as galstrom17:20
*** Ravikiran_K has quit IRC17:21
*** prateek has quit IRC17:21
*** neiljerram has joined #openstack-meeting17:21
*** yamahata has joined #openstack-meeting17:23
*** eharney has quit IRC17:24
*** bobh has joined #openstack-meeting17:25
*** hurricanerix has joined #openstack-meeting17:27
*** aloga has quit IRC17:28
*** aloga has joined #openstack-meeting17:28
*** guoshan has joined #openstack-meeting17:29
*** lhx_ has quit IRC17:30
*** reedip_ has quit IRC17:31
*** saisrikiran has joined #openstack-meeting17:31
*** baoli has joined #openstack-meeting17:33
*** annakoppad has joined #openstack-meeting17:33
*** prateek has joined #openstack-meeting17:34
*** guoshan has quit IRC17:34
*** prateek_ has joined #openstack-meeting17:36
*** prateek_ has quit IRC17:37
*** thorst has joined #openstack-meeting17:37
*** prateek_ has joined #openstack-meeting17:37
*** eharney has joined #openstack-meeting17:38
*** prateek has quit IRC17:39
*** csomerville has joined #openstack-meeting17:39
*** cody-somerville has quit IRC17:42
*** dmorita has joined #openstack-meeting17:44
*** neiljerram has quit IRC17:44
*** ihrachys has quit IRC17:45
*** thorst has quit IRC17:45
*** dprince has joined #openstack-meeting17:46
*** mickeys has joined #openstack-meeting17:47
*** emagana has quit IRC17:48
*** nadya_ has joined #openstack-meeting17:49
*** bobh has quit IRC17:49
*** emagana has joined #openstack-meeting17:51
*** nishaYadav has joined #openstack-meeting17:51
*** nadya has quit IRC17:53
*** harlowja has joined #openstack-meeting17:53
*** lpetrut has joined #openstack-meeting17:54
*** neiljerram has joined #openstack-meeting17:57
*** fzdarsky has quit IRC17:57
*** fzdarsky_ has quit IRC17:57
*** pcaruana has quit IRC17:59
*** bobh has joined #openstack-meeting17:59
*** yamamoto has quit IRC17:59
*** abalutoiu has joined #openstack-meeting17:59
*** yamahata has quit IRC17:59
* breton yawns18:00
*** iyamahat has quit IRC18:00
samueldmqagrebennikov, amakarov, annakoppad, ayoung, bknudson, breton, browne, chrisplo, crinkle, davechen, dolphm, dstanek, edmondsw, edtubill, gagehugo, gyee, henrynash, hrybacki, jamielennox, jaugustine, jgrassler, knikolla, lbragstad, kbaikov, ktychkova, morgan, nisha, nkinder, notmorgan, raildo, ravelar, rderose, rodrigods, roxanaghe, samueldmq, shaleh, spilla,18:00
samueldmqsrwilkers, StefanPaetowJisc, stevemar, topol18:00
rodrigodso/18:00
ayoungOyez18:00
samueldmqhi all18:00
crinkleo/18:00
lbragstado/18:00
rodrigodshuge list :)18:00
*** ravelar has joined #openstack-meeting18:00
*** jamesdenton has quit IRC18:00
*** lpetrut has quit IRC18:00
*** saisrikiran has quit IRC18:00
stevemaro/18:00
samueldmqyeah, it's getting bigger, which is good18:00
dstaneko/18:00
jaugustineo/18:00
stevemaruntil we prune the list again :)18:00
samueldmq#startmeeting keystone18:01
openstackMeeting started Tue Dec 20 18:01:02 2016 UTC and is due to finish in 60 minutes.  The chair is samueldmq. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
morganstevemar: ++18:01
*** openstack changes topic to " (Meeting topic: keystone)"18:01
openstackThe meeting name has been set to 'keystone'18:01
knikollao/18:01
samueldmqhi all, hope you're all doing well18:01
*** gagehugo has joined #openstack-meeting18:01
samueldmqwe've got a small agenda today18:01
samueldmqso if you ahve something to discuss, please update the etherpad18:01
samueldmqthe agenda is at:18:01
samueldmq#link https://etherpad.openstack.org/p/keystone-weekly-meeting18:01
*** acoles is now known as acoles_18:01
*** unicell1 has quit IRC18:01
samueldmq#topic announcements18:01
*** openstack changes topic to "announcements (Meeting topic: keystone)"18:01
samueldmqstevemar: o/18:02
rderoseo/18:02
stevemaroh hey18:02
stevemarthanks for running the meeting samueldmq!18:02
morganstevemar: lol18:02
stevemartheres more!18:02
samueldmqstevemar: my pleasure18:02
stevemarwe're a few weeks away from ocata-3 being cut18:02
stevemarhttps://releases.openstack.org/ocata/schedule.html18:02
*** rbartal has quit IRC18:03
samueldmq#link https://releases.openstack.org/ocata/schedule.html18:03
stevemarocata-3 is being cut on Jan 23-2718:03
morganstevemar: i'm going to try and get the MFA stuff done, but holidays may mean it slips18:03
*** yamamoto has joined #openstack-meeting18:03
gagehugoo/18:03
morganstevemar: but that was expected with the short cycle.18:03
stevemarI don't know what the holiday schedules look like for everyone, but i figured I'd remind everyone of the priorities: https://docs.google.com/spreadsheets/d/156q820cXcEc8Y9YWQgoc_hyOm3AZ2jtMQM3zdDhwGFU/edit?usp=sharing18:03
*** longxiongqiu has joined #openstack-meeting18:03
stevemarcommunication will be slow and infrequent18:04
stevemarif you need me, shoot me an email to my gmail address18:04
stevemarotherwise, thanks everyone who has reviewed or commited a patch this cycle!18:04
stevemari'll be canceling next meeting18:04
stevemarand taking this thursday/friday off18:04
stevemarso merry christmas and happy holidays :)18:04
stevemarthanks keystoners :)18:05
samueldmq\o/18:05
stevemarand happy new year too!18:05
samueldmqthanks all, this has been a great year for keystone18:05
lbragstadstevemar ++18:05
samueldmqstevemar: thanks for being a great leader18:05
rodrigodsthanks!18:05
stevemarnext meeting till be on 01/03 (or whatever the numeber is, that week)18:05
gagehugothanks!18:05
knikollahappy holidays!18:05
*** dmacpher_ has joined #openstack-meeting18:06
* stevemar hands the baton back to samueldmq18:06
samueldmqstevemar: thanks18:06
samueldmq#topic open discussion18:06
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:06
*** parora has joined #openstack-meeting18:06
samueldmqdoes anybody have anything to discuss?18:06
lbragstadjust a reminder that we will be having our policy meeting tomorrow - but it will probably be cancelled next week18:07
samueldmqI am particularly concerned about the features which have been approved but not started, in that doc stevemar shared18:07
lbragstadI'll be sure to send a note to the mailing list, but wanted to post an update here, too18:07
stevemarthe keystone-horizon meeting is canceled 2 weeks in a row, lands on a thursday18:07
samueldmqlbragstad: nice. what time ?18:07
samueldmqlbragstad: just to document it here too.18:07
*** yamamoto has quit IRC18:07
*** thorst has joined #openstack-meeting18:08
lbragstad1600 UTC18:08
lbragstadhttp://eavesdrop.openstack.org/#Keystone_Policy_Meeting18:08
*** longxiongqiu has quit IRC18:08
samueldmqlbragstad: nice, thanks18:08
lbragstadyep!18:08
stevemaranyone have a review request?18:08
rderosehttps://review.openstack.org/#/c/399684/18:09
rderose:)18:09
rodrigodsyeah :)18:09
rodrigodshttps://review.openstack.org/#/c/324769/18:09
samueldmqalso, there are plenty of not started bugs in that priorities etherpad. just in the case someone want to pick one up :-)18:09
stevemarrderose: added18:09
*** prateek_ has quit IRC18:10
rodrigodsalthough samueldmq and lbragstad reviewed it18:10
rodrigods:)18:10
stevemarrodrigods: "u'Conflict occurred attempting to store identity_provider - Duplicate entry: testshib"18:10
stevemar:P18:10
rodrigodsstevebaker, yep18:10
rodrigodssee related bug18:10
stevemarsamueldmq: yeah, I'm hoping to fix the LDAP ones over the break18:10
stevemarand KSC ones18:10
rodrigodsit will never pass, because the cleanup is broken due the bug18:10
*** jlibosva has quit IRC18:11
samueldmqstevemar: nice18:11
rodrigodsan option is to add the "wip" decorator18:11
samueldmqrodrigods: what is that bug and what does it take to fix it ?18:11
*** rossella_s has quit IRC18:11
samueldmqrodrigods: https://bugs.launchpad.net/keystone/+bug/1642692 ?18:12
openstackLaunchpad bug 1642692 in OpenStack Identity (keystone) "Protocol can't be deleted after federated_user is created" [Medium,Triaged] - Assigned to Ron De Rose (ronald-de-rose)18:12
*** salv-orlando has quit IRC18:12
*** lpetrut has joined #openstack-meeting18:12
*** rossella_s has joined #openstack-meeting18:12
stevemarmaybe someone wants to organize a bug smash in the new year ? :)18:12
nishaYadavsamueldmq, can you please send a link of the not started bugs you are stating above ^ ?18:12
stevemarif everyone fixes one or two bugs we'd make a lot of headway18:12
samueldmqstevemar: I can organize it, just need to know when it would work for ppl18:13
lbragstadstevemar dstanek and I have talked about resurrecting the friday bug days18:13
samueldmqstevemar: agreed18:13
*** zz_dimtruck is now known as dimtruck18:13
samueldmqlbragstad: that'd be great!18:13
knikollaI'd be happy if there was something regular and structured18:13
stevemarlbragstad: you thinking all day friday?18:13
samueldmqnishaYadav: see the priorities at https://docs.google.com/spreadsheets/d/156q820cXcEc8Y9YWQgoc_hyOm3AZ2jtMQM3zdDhwGFU/edit#gid=018:13
stevemar9am - 5pm sort of deal?18:13
lbragstadstevemar that's what it was before18:13
stevemaryeah, lets start those up again18:13
rodrigods++18:13
samueldmqnishaYadav: there is a section with bugs to be addressed in Ocata18:13
rodrigodsgood idea18:14
lbragstadbut most folks would conttribute an hour or two18:14
stevemarlbragstad: i'll stick around all day :P18:14
*** hashar has quit IRC18:14
lbragstadfrom our experience - it the issue wasn't finding things to work on18:14
lbragstador bugs to fix,18:14
nishaYadavsamueldmq, sure I will check that, thanks18:14
knikollaI should be able to request the whole friday for keystone, already complained to manager I don't contribute as much as I wanted.18:14
lbragstadthe hang up usually ends up being reviews that close bugs18:14
knikollabut having it a regular occurence makes it easier.18:14
samueldmqknikolla: nice, hopefully it'll work out18:15
dstanekthe full friday was nice. the biggest issue we had is that as time went on there was less and less of us18:15
lbragstadi can take an action item to get that rolling again with dstanek if people want that format18:15
stevemarknikolla: i'm sure lbragstad or dstanek will whip up an email to the mailing list that you can send to your manager18:15
lbragstaddstanek ++ especially across time zones18:15
stevemardstanek: that's somewhat expected, sorry west coast people18:16
knikolladstanek: lets put a threshold on the number of people, and if it drops below that, revise18:16
samueldmq#action lbragstad and dstanek to get bug smashes on Fridays rolling again18:16
lbragstadknikolla do you need it phrased a certain way in order to get approval?18:16
dstaneki mean just in general. by the last official one i may have been the only one participating18:16
stevemardstanek: did you remind people that you were running them?18:16
dstanekwe need to try to keep people engaged more, but i don't know how18:16
lbragstadknikolla something along the lines of "subject: knikolla must fix all the bugs every Friday in keystone"18:17
knikollastevemar, lbragstad: not really, Its a pretty informal workplace (as academia usually is). but since i work with a lot of students, and they rotate every semester, i never get to delegate as much as i want.18:17
dstanekstevemar: yep, we announced it, had people updating the etherpad, but it still lost steam18:17
samueldmqlbragstad: dstanek: having a hangouts set up can be useful too, so people can just talk in there when needed18:17
samueldmqI remember lbragstad did that once18:17
knikollaso even if my manager says, yes, if I need to get stuff done, and nobody can do it besides me, approval doesn't help much.18:17
stevemardstanek: hmm, okay, let's try it again and see what happens, we need new data18:17
gagehugo++ hangouts18:17
dstaneksamueldmq: initially we did. but nobody wanted to do that18:17
stevemardstanek: timing is always an issue18:17
stevemar++ hangouts18:18
dstanekit's too hard to work in a hang out. even worse that having a noisy cube18:18
stevemarwho wasn't OK with hangouts?18:18
rodrigodsmaybe it should be something to happen on fridays18:18
lbragstadthe only thing that stinks about hangouts is the attendance cap18:18
morganstevemar: what was trhe reson for hangouts?18:18
rodrigodsbut if we have quorum?18:18
lbragstad(we hit that with the policy meeting)18:18
* morgan reads backscroll18:18
knikollais there something that doesn't cap like hangouts?18:18
ayounghangouts was problematic for policy meeting18:18
stevemarhaha, if we have that many people participating in the bug smash, i'd be happy!18:19
lbragstadwell - to be fair, I don't pay for google services, so the unpaid version does have a cap18:19
stevemari can't imagine it'll be more than 1018:19
dstaneki'll be happy to send out an email about Friday bug days, but i don't want to sit in a hangout. i would do it on demand though18:19
morganalso, remember that anything said in hangouts needs to be replayed to open development practices (irc, etc) if it is used for anything beyond adhoc problem soliving18:19
gagehugoI like discord for voice/text chatting, no video though18:19
lbragstaddstanek was telling me that the paid version has a higher cap18:19
morgandecisions should not be bade on them18:19
morganmade*18:19
stevemarmorgan: it'll be for problem solving18:19
samueldmqstevemar: ++18:20
dstaneklbragstad: not much higher iirc18:20
morganstevemar: just make sure folks are clear on that18:20
knikollahmmm, can we have multiple hangout rooms?18:20
knikollalike one for ldap18:20
lbragstadwe could use something like mumble18:20
knikollaone for federation18:20
knikollaone for general bugs18:20
dstanekknikolla: no, that would be terrible18:20
stevemarany decision made will be will be noted in commit messages and bug reports18:20
knikollatrue18:20
morganftr, i dislike hangouts in general for a "standing" thing18:20
dstaneki think hangouts should be on demand and can be coordinated in the room18:20
stevemarlet's just try a single hangout for now, if we run into issues, we'll handle them as we go18:20
morganstanding hangouts is bad18:20
morgando an on-demand one18:20
morganif needed18:20
bretonhttps://meet.jit.si/18:21
dstanekthe last thing i want to do is hack code or try to review with 12 people staring at me18:21
samueldmqstevemar: ++18:21
stevemarthe hangout worked *really* well for the API sprint18:21
morganif you need to communicate problem solve, spin up a hangout18:21
bretonno google account required and is FOSS18:21
samueldmqlet's just start it, we can improve/change tools as needed18:21
lbragstadmorgan ++18:21
morgandon't make a standing one for the day18:21
stevemardstanek: but i'm watching you code right now18:21
*** Swami has joined #openstack-meeting18:21
knikollaone of the postdocs that works with us, swears by talky.io18:21
morganstevemar: twitch programs openstack18:21
dstanekstevemar: i know the NSA is!18:21
stevemari'll let whoever organizes this make the call, but i think a single hangout is fine for now18:22
*** csomerville has quit IRC18:22
morgananyway. like i said. don't make a standing hangout for this. spin up the hangout dynamically for specific solving18:22
stevemarit worked for the API ref sprint18:22
samueldmqstevemar: agreed18:22
stevemarI get lonely during the day and want to talk to people18:23
samueldmqstevemar: same here, I don't even have an office near me D:18:23
stevemarlbragstad: you've got the TODO correct?18:23
lbragstadstevemar i do - samueldmq made an action18:24
samueldmqstevemar: I've added an #action a few lines above18:24
samueldmqyep18:24
stevemarawesomeo18:24
samueldmqdoes anybody else have something else to discuss ?18:24
stevemaroh, one thing I wanted to remind people about18:24
stevemarhttps://www.openstack.org/ptg/18:24
stevemarPTG, register for it soon (I have to do that...)18:24
lbragstadstevemar when do you want the first Friday bug day to be?18:25
dstaneki'm surprised that it didn't sell out already18:25
stevemardstanek: I'm waiting til mid-january18:25
lbragstadstevemar Friday, January 6th?18:25
stevemarlbragstad: sure, fine w/ me18:25
dstanek220 tickets remaining18:25
lbragstaddstanek does that work for you?18:25
stevemardstanek: I don't want to do two expense reports18:25
dstaneklbragstad: yep, works for me18:26
lbragstaddstanek sweet - thanks18:26
*** parora has quit IRC18:26
lbragstadstevemar doing more than one expense report at a time is borderline manager-like18:26
dstanekstevemar: just keep an eye on that number18:26
*** prateek has joined #openstack-meeting18:26
stevemardstanek: ++, if someone notices that number dipping, give the rest of the team a shout18:27
stevemari have to wait til travel req is approved, and that doesn't happen til new year18:27
stevemari imagine a lot of people are in the same boat18:27
dstanek#link https://www.eventbrite.com/e/project-teams-gathering-tickets-27549298694#tickets18:27
stevemarkeystone is having their mid-cycle W-F apparently18:28
knikollaAre you guys coming just for W-F or earlier?18:28
stevemarMonday and Tuesday is all the horizontal projects18:28
samueldmqanything else ?18:28
stevemarknikolla: whole week!18:28
lbragstadi'm still unsure if I'll be there the whole week18:28
*** unicell has joined #openstack-meeting18:29
knikollaI'm not sure either18:29
samueldmqsorry my message got delayed18:29
lbragstadunless dstanek has heard something I haven't18:29
samueldmq I am trying to be the whole week18:29
*** rcernin has quit IRC18:29
*** guoshan has joined #openstack-meeting18:30
stevemari'm done with topics :)18:31
dstaneklbragstad: no idea, i'm assuming that i'll get there on Tuesday though18:31
dstaneksounds like beer:30 then18:31
*** DavidPurcell has joined #openstack-meeting18:31
samueldmqyeah18:31
samueldmqthanks everyone for coming18:31
lbragstadthanks all18:31
knikollaA unified midcycle is nice though, I had to fly to the nova one in the last cycle :/ In Hillsboro18:31
stevemarthanks for chairing18:31
stevemarsamueldmq: ^18:31
*** iyamahat has joined #openstack-meeting18:31
samueldmqenjoy holidays, Merry Christmas and Happy New Year18:31
stevemarhappy holidays all!!!!!18:32
samueldmqstevemar: anytime, thanks18:32
samueldmq#endmeeting18:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:32
openstackMeeting ended Tue Dec 20 18:32:17 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-12-20-18.01.html18:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-12-20-18.01.txt18:32
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-12-20-18.01.log.html18:32
*** ataraday_ has quit IRC18:32
*** gagehugo has left #openstack-meeting18:32
*** annakoppad has quit IRC18:32
*** asselin has joined #openstack-meeting18:32
samueldmqfungi: we've released the room early today :)18:33
*** asselin__ has quit IRC18:33
fungithanks samueldmq!18:34
fungithough infra has a light agenda today anyway18:34
*** nishaYadav has quit IRC18:34
samueldmqfungi: thanks, same here, and we won't have meeting next week18:34
funginor will we18:34
*** Drankis has quit IRC18:35
*** guoshan has quit IRC18:35
fungii think pretty much everyone has cancelled at least meetings the first half of next week18:35
samueldmq++18:35
*** dmacpher_ has quit IRC18:38
*** ociuhandu has quit IRC18:39
*** bobh has quit IRC18:39
*** bobh has joined #openstack-meeting18:41
*** yamahata has joined #openstack-meeting18:41
*** pvaneck has joined #openstack-meeting18:43
*** s3wong has joined #openstack-meeting18:54
*** rasca has quit IRC18:55
*** Shrews has joined #openstack-meeting18:57
*** mamitchl has joined #openstack-meeting18:57
*** zara_the_lemur__ has joined #openstack-meeting18:57
*** nadya_ has quit IRC18:57
*** AJaeger has joined #openstack-meeting18:58
*** fnaval has quit IRC18:59
fungiinfra team, meet if you dare!19:00
fungithis week we have topics proposed by clarkb and yours truly19:00
clarkbhello19:00
AJaegeroh, what existing things await us, dear master?19:00
* zara_the_lemur__ lurks19:00
*** fnaval has joined #openstack-meeting19:00
ianwgood morning19:00
*** fnaval has quit IRC19:00
pabelangero/19:01
DavidPurcello/19:01
*** fnaval has joined #openstack-meeting19:01
jheskethMorning19:01
mmedvedeo/19:01
*** elynn has quit IRC19:01
*** dmorita has quit IRC19:02
jeblairhi!19:02
*** elynn has joined #openstack-meeting19:02
fungi#startmeeting infra19:03
openstackMeeting started Tue Dec 20 19:03:12 2016 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
*** openstack changes topic to " (Meeting topic: infra)"19:03
openstackThe meeting name has been set to 'infra'19:03
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:03
fungi#topic Announcements19:03
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:03
fungi#info The OpenStack Infra team will not meet on Tuesday, December 27, 2016; our next meeting will occur on Tuesday, January 3, 2017 at 19:00 UTC in the #openstack-meeting channel as usual.19:03
fungi(as decided in last week's meeting)19:03
fungias always, feel free to hit me up with announcements you want included in future meetings19:03
fungi#topic Actions from last meeting19:04
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:04
fungi#link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-12-13-19.03.html previous meeting minutes19:04
fungipabelanger add openstackci::zuul_launcher puppet class19:04
pabelangerYes!19:04
fungihow did you get on?19:04
pabelangerI have started working on this locally19:04
asselino/19:04
pabelangerjust doing a few tests before pushing it up19:04
pabelangerbut, looks to be straightforward19:04
pabelangerwill be ready for reviews on thursday19:04
fungiokay, cool. maybe we can mark it off by the time we meet again in a couple weeks19:05
pabelanger++19:05
*** diablo_rojo has quit IRC19:05
*** yamamoto has joined #openstack-meeting19:05
fungii likely won't be doing much in the way of reviews on thursday, but give me a heads up and i'll try to look when i'm online19:05
pabelangersure19:05
fungithanks for working on that!19:05
fungi#topic Specs approval19:05
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:05
fungi#info APPROVED "Zuul v3: update with Ansible role information"19:06
fungi#link https://review.openstack.org/381329 "Zuul v3: update with Ansible role information" spec update19:06
*** dmorita has joined #openstack-meeting19:06
fungialso i finally marked the artifact signing spec as implemented19:06
*** AlanClark has joined #openstack-meeting19:06
jlvillalo/19:06
fungi#link https://review.openstack.org/409906 "Artifact signing is now implemented" change19:06
fungi#link http://lists.openstack.org/pipermail/openstack-dev/2016-December/109111.html "Signing Keys for Ocata Release" announcement19:07
*** electrofelix has quit IRC19:07
fungidoesn't look like we have any new specs going up for a vote this week19:07
fungi#topic Priority Efforts19:07
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:08
*** Swami has quit IRC19:08
funginothing is called out on the agenda, but our next discussion topic covers something we may want to consider as an addition19:08
fungi#topic Cross-project goal to support Python 3.5 in Pike (fungi)19:08
*** openstack changes topic to "Cross-project goal to support Python 3.5 in Pike (fungi) (Meeting topic: infra)"19:08
*** skelso has joined #openstack-meeting19:08
fungi#link https://review.openstack.org/349069 proposed cross-project goal to support Python 3.5 in Pike19:08
*** Swami has joined #openstack-meeting19:09
fungithe latest patchset for that proposed pike goal mentions infra19:09
AJaegerwe have quite a few repos without python35 jobs19:09
* AJaeger hasn't done any detailed analysis19:09
fungiwe do have rather a lot of python-based tooling, at least some of which is probably not tested at all for py3k compliance, and certainly most of it is not regularly running all its tests under 3.519:09
*** bobh has quit IRC19:09
fungii haven't responded positively to the goal wearing my infra ptl hat yet, since i wanted to bring it up with the team first and figure out if we think it's feasible by the end of pike19:10
jeblairfungi: i don't think we belong in there19:10
fungii can certainly make that case, given sufficient explanation19:11
jeblairi imagine that this sort of goal is to make openstack itself more operationally consistent19:11
fungiexemption along the same lines as the licensing argument?19:12
*** Sukhdev has joined #openstack-meeting19:12
jeblairfungi: indeed, and even language -- i mean, our java code isn't going to be py3 any time soon19:12
*** yamamoto has quit IRC19:13
fungiwell, sure, this is primarily about making sure we don't get caught without a solution when python 2.7 reaches end of life19:13
jeblairi'm not disputing its importance, merely the need to synchronize with openstack itself on tihs19:13
*** diga has quit IRC19:14
clarkbits probably not a bad idea to start thinking about it though?19:15
*** galstrom is now known as galstrom_zzz19:15
jeblairoh, we've been thinking about it, and indeed doing a lot of work19:15
fungiyeah, so for infra projects we generally don't use coordinated global requirement synchronization, have projects under other (even apache-incompatible) free licenses, have projects in languages not officially sanctioned by the tc for openstack deliverables19:15
*** nadya has joined #openstack-meeting19:15
*** rbudden_ has joined #openstack-meeting19:15
jeblairbut we've also been deferring some of it because we know that the initial cut of zuulv3 is more urgent19:16
DavidPurcellMight also want to update the creator's guide templates to include or require 3.5 http://docs.openstack.org/infra/manual/creators.html#configure-zuul-to-run-jobs19:16
*** rbudden has quit IRC19:16
*** rbudden_ is now known as rbudden19:16
*** diablo_rojo has joined #openstack-meeting19:16
clarkbone thing we could do is require any new code to be python319:16
jeblairno we can't19:16
clarkblike possible new bug organizing report dashboard19:16
clarkbjeblair: why not?19:17
jeblairoh like that19:17
fungiDavidPurcell: yep, agreed, in fact we've already started including gate-{name}-python35 in the python-jobs job-template in jjb and have talked about adding it to the python-jobs project-template in zuul's config19:17
AJaegerDavidPurcell: I just updated that page, wonder why it's not up yet...19:17
jeblairi thought you meant new patches19:17
clarkbsorry not new patches, new project repos/code bases19:17
jeblairclarkb: possibly. i mean, we should at least try.  :)19:17
fungiso i guess there's a couple of major axes to this problem from our (infra's) perspective19:18
* AJaeger investigates why infra-manual publishing fails19:18
clarkbwe could also likely port our jobs that check things about our repos to python3 easily as that should be self testing maybe19:18
DavidPurcellAJaeger: It is now...  That was quick.19:18
fungifirst is whether _our_ tools need to all support python 3 asap, and it sounds like that's maybe a harder sell19:18
AJaegerDavidPurcell: ;)19:18
fungithe other is whether our ci supports and workflow documentation encourages python 3 support in other projects19:19
fungiwhich i think we've already mostly met?19:19
clarkbyes, I don't think anything prevents our users from running python319:19
AJaegerwe should double check the documents19:19
fungicertainly implying that it's acceptable for completely new python projects to start out without python 3 support is something we should avoid19:20
jeblairfungi: there's a reference to an un-logged #openstack-python3 channel in there19:22
fungia rough count says we have somewhere around 40 infra repos with a setup.py in them, and even auditing those for py3k compliance before the end of the pike cycle strikes me as a tall order19:22
* AJaeger just did https://review.openstack.org/413211 to promote python35-jobs a bit19:22
fungijeblair: oh, fun19:22
*** ociuhandu has joined #openstack-meeting19:22
jeblairfungi: which violates the tc irc channel policy: https://governance.openstack.org/tc/reference/irc.html19:23
pabelangerokay, that took me way to long to find Infrastructure in that review19:23
*** whenry has joined #openstack-meeting19:24
AJaegerbefore we enforce it, we need to extend meetbot setup to handle all channels...19:24
pabelangerAgreed, that is going to be a fair amount of work for us I think.19:24
pabelangerwith zuulv3 effort19:24
fungijeblair: agreed, i've asked dhellmann and haypo in that channel whether there's a change to add logging for it19:24
fungidhellmann thinks it's an oversight we should correct19:25
clarkbright I think a good place to start is where it is easy19:25
clarkbrequire new code bases be python3, update simple scripts that are already self testing, and so on19:25
jeblairthere are some significant py3 challenges with gear that need to be resolved before systems that use it can/should switch to py319:25
jeblairthis is one of the things we have deferred so that we can make progress on the basics in zuulv319:25
jeblairi think they are solvable, but they are going to take some real care and thought, and should not be rushed19:26
AJaegerat least all infra repos that have python35 set up , have it as voting ;)19:26
fungijeblair: yeah, i think the fact that we don't use global requirements and the py3k goal hinges on making sure the global requirements list of deps support it is a good indication of the situation we're in there19:26
*** russellb has quit IRC19:28
*** russellb has joined #openstack-meeting19:28
jeblairfungi: yeah, and i like the idea of the goals, and i like this one.  i don't want us to be a distraction for it.19:28
fungi#agreed The Infra team is actively working toward Python 3 support across its tooling, but has far more diverse requirements from the general body of OpenStack services and libraries and so does not expect to complete that effort by the end of the Pike development cycle; however making sure our CI automation supports the Python 3 testing needs of other projects is a very high priority (and already19:29
fungibasically solved).19:29
fungihrm, that was too long19:29
*** thorst has quit IRC19:29
fungi#undo19:29
openstackRemoving item from minutes: <ircmeeting.items.Agreed object at 0x7fc5685a3d10>19:29
*** gouthamr has quit IRC19:29
fungi#agreed The Infra team is actively working toward Python 3 support across its tooling, but has far more diverse requirements from the general body of OpenStack services and libraries and so does not expect to complete that effort by the end of the Pike development cycle.19:29
* jlvillal notices another thing to to add a __str__ method to19:29
*** thorst has joined #openstack-meeting19:29
fungi#agreed Making sure our CI automation supports the Python 3 testing needs of other projects is a very high priority (and already basically solved).19:30
*** olaph has joined #openstack-meeting19:30
fungieveryone comfortable with those two stated agreements?19:30
AJaegeryes19:30
clarkbyup19:30
jeblair++19:30
pabelanger++19:31
jheskethYep19:31
*** guoshan has joined #openstack-meeting19:31
fungithanks! this was very helpful19:31
jeblairfungi: thank you for interfacing!19:31
fungianybody else have anything they want to say on the python 3 goal front before i yield teh floor to clarkb's topic?19:32
fungi#topic Switch review.o.o openid to login.ubuntu.com (clarkb)19:32
*** openstack changes topic to "Switch review.o.o openid to login.ubuntu.com (clarkb) (Meeting topic: infra)"19:32
fungiwe were originally talking about doing this late last week or early this week i guess19:33
clarkbya basically we should be thinking about this so lp doesn't berak us again as supposedly we are using the wrong url19:33
clarkb(we should also be thinking about storyboard and wiki)19:33
zara_the_lemur__yeah, I've +1'd a patch for storyboard19:33
jeblair'wrong' but not 'deprecated' :)19:33
zara_the_lemur__I can't merge it19:33
zara_the_lemur__since it's in the system config repo19:34
clarkbzara_the_lemur__: ya and the tricky part is we have to update the config, and db at roughly the same time19:34
clarkbgerrit is a bit easier because we can update db while it is running as gerrit allows for more than one openid19:34
fungiright, with gerrit we can basically just leave the "old" openid urls in the db forever19:35
clarkbfor gerrit I think our rough plan should be 1) update db 2) merge config change 3) restart gerrit when config is applied.19:35
*** harlowja has quit IRC19:35
*** guoshan has quit IRC19:35
clarkband then question si do we want to schedule a more formal downtime, get everything done ahead of time so that when GC problems occur we do restart then or something else?19:35
jeblairclarkb: that's still a little racy if people make new accounts during then19:36
fungithe tricksy timing for gerritses comes down to minimizing the window between the db additions and the config change, since new accounts created between them could end up broken/duplicated19:36
fungier, what jeblair just said19:36
jeblairfungi:  :)19:36
clarkbjeblair: oh good point19:36
clarkbso maybe is best to stop gerrit, update db, update config, start gerrit19:37
jeblairclarkb: so we may want a second 'update the db' change to catch any new accounts; or maybe we just want to take a brief outage and do the db update and config change while offline19:37
*** prateek has quit IRC19:37
fungiit's not as if gerrit's under heavy use this time of year19:37
*** thorst has quit IRC19:38
*** sdake has joined #openstack-meeting19:39
clarkbjeblair: problem with catch new accounts is they won't work in the interim19:39
clarkbactually maybe they will I think monty mentioned he tested the old and new things accept the old and new urls both19:39
jeblairyeah, i lean toward the outage idea19:39
fungirather, they'll get duplicated19:39
clarkbbut outage will be safer19:39
fungii did test that the lp api calls used in jeepyb support user lookups via openid interchangeably with both19:40
fungiso we can patch those any time we like19:40
*** jamesdenton has joined #openstack-meeting19:41
clarkbare people around tomorrow?19:41
jeblairyep19:41
*** sdake_ has quit IRC19:41
fungii am not around tomorrow, but if other people are and want to work on it then please feel free to do so19:41
fungii'll be driving a good chunk of the day19:41
clarkbmordred: did the review-dev change, any chance you will be around tomorrow and we can do the prod server?19:42
clarkbI will be around19:42
* jhesketh isn't but can be if needed19:42
clarkbjeblair: we could do it if you are willing to19:42
mordredclarkb: yah19:42
jeblairclarkb: wfm19:43
clarkbgreat what time works tomorrow? say 1800UTC?19:43
*** Leo_ has joined #openstack-meeting19:43
mordredclarkb: I'm free all day19:43
clarkbok I should be awake by 1800UTC but will ping mordred and we can get it done19:43
*** weshay is now known as weshay_relocate19:44
*** neiljerram has quit IRC19:44
jeblair1800 is good for me19:44
clarkbI will also likely poke at storyboard-dev at some point tomorrow as well19:44
clarkbsounds good. Thats mostly what I wanted out of this topic. How do we want to go about it and when and those have both been answered19:45
zara_the_lemur__:)19:46
fungii'm already comfortable this should be pretty straightforward. the main trick which mordred already solved is the etl to add/replace rows keeping some substring constant while altering another substring19:47
pabelangerI won't be around much tomorrow to help, a heads up19:47
fungihappy to just find out the next time i get to the internet that it's done and behind us ;)19:48
mordred\o/19:48
*** gordc has joined #openstack-meeting19:49
fungiokay, anything else need hashing out for the openid url replacement?19:50
ianwnot that i have any great insights into it, but i will be around .au time if everything goes cray cray and you want to go to bed :)19:50
*** gouthamr has joined #openstack-meeting19:50
fungithanks, everyone who's working on updating this19:50
fungi#topic Open discussion19:50
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:50
jlvillalI notice on #openstack-meeting-5 that 'openstack' is not an operator. Which seems incorrect.19:51
clarkbI think that got traced back to the accessbot not having its nick set properly?19:51
clarkbI know I +2'd the change to fix that19:51
fungijlvillal: i believe it gets topic modifying permission anyway so shouldn't bother19:51
*** jamesdenton has quit IRC19:51
fungis/bother/matter/19:51
fungimaybe we do that through chanops?19:52
fungii thought we just added the specific mode for topic19:52
jlvillalI just did a 'testing' meeting there and the topic stays the same19:52
jlvillalAnd doing the #topic command didn't seem to do anything19:53
fungioh, meetbots get +O so are auto-opped19:53
fungibut that only takes effect on /join i think19:53
*** sdake_ has joined #openstack-meeting19:53
*** abalutoiu has quit IRC19:53
fungiso probably needs a restart or might be able to just /kick and let it rejoin?19:54
fungior else it'll take effect the next time a change merges to its own configuration19:54
clarkband make sure it is setting its nick properly now19:54
clarkber I guess if it has the proper access in that channel that that did work /me checks19:55
jeblairit's not on the access list for that channel19:55
jeblairso accessbot is broken or its config is broken or has not run19:55
*** sdake has quit IRC19:56
*** skelso has quit IRC19:56
*** jamesdenton has joined #openstack-meeting19:57
clarkbhttps://review.openstack.org/#/c/410975/ did merge so possibly we just have to restart the accessbot?19:58
fungioh, as mentioned i'm not around much tomorrow. i'll be mostly spotty with my online activity for the coming week, but should be around again normally from the 29th onward19:58
*** DavidPurcell has quit IRC19:58
*** kota_ has joined #openstack-meeting19:59
clarkband change your freenode password19:59
dimshappy holidays everyone!19:59
*** rossella_s has quit IRC19:59
fungithanks dims19:59
fungiaaaaand we're out of time--thanks everyone!20:00
fungi#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Dec 20 20:00:06 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-12-20-19.03.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-12-20-19.03.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-12-20-19.03.log.html20:00
ttxo/20:00
*** Shrews has left #openstack-meeting20:00
stevemaro/20:00
dimso/20:00
* fungi isn't disappearing20:00
dtroyero/20:00
dims:)20:00
ttxdhellmann, EmilienM, flaper87, johnthetubaguy, mordred, mtreinish, sdague, thingee: around ?20:00
mtreinisho/20:00
EmilienMo/20:00
* thingee is finally present with a baby strapped to him20:00
flaper87o/20:00
flaper87thingee: welcome back20:00
mordredo/20:00
johnthetubaguyo/20:00
dimsyay thingee20:00
ttx#startmeeting tc20:00
openstackMeeting started Tue Dec 20 20:00:59 2016 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
* smcginnis lurks in the corner20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: tc)"20:01
dhellmanno/20:01
openstackThe meeting name has been set to 'tc'20:01
ttxHi everyone!20:01
ttxBusy agenda for today, so let's try to go quick.20:01
kota_hello20:01
*** mamitchl has left #openstack-meeting20:01
ttxLots of things that would be great to finalize before the new year20:01
mordredthingee: I have many fewer babies strapped to me than you do I believe20:01
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:01
ttx(remember to use #info #idea and #link liberally to make for a more readable summary)20:01
jroll\o20:01
sdagueo/20:01
ttx#topic Storlets to become official - Proposed governance change20:01
*** openstack changes topic to "Storlets to become official - Proposed governance change (Meeting topic: tc)"20:01
stevemarthingee: i wouldn't let the baby type20:01
ttx#link https://review.openstack.org/35369320:01
ttxThis was originally proposed in August20:01
flaper87eranrom: around ?20:02
ttxback then we deferred it so that a number of requirements could be implemented20:02
eranromHi20:02
ttxProgress was made there and tracked at:20:02
ttx#link https://etherpad.openstack.org/p/storlets-big-tent20:02
ttxI feel like this is going in the right direction and is close enough now...20:02
thingeegood progress!20:02
ttxThoughts ?20:02
flaper87yeah, FWIW, I've been working with the storlets team since August and guiding them through the process20:02
ttxI appreciated that Eran did wait until significant progress was made before reapplying20:03
flaper87the team was receptive and they addressed the concerns as they came20:03
stevemarsounds like great progress, just a few things left to do20:03
* sigmavirus sneaks in and sits in the back20:03
johnthetubaguylast week was the date for membership freeze, I guess thats not a hard rule?20:03
ttxIf we want Storlets in Ocata and at the Atlanta PTG this is a bit of a deadline20:03
*** DavidPurcell has joined #openstack-meeting20:03
*** olaph has left #openstack-meeting20:03
ttx(if approved today we can still include it I think)20:04
thingeefine with making an exception20:04
flaper87One of the questions is whether the current concerns are critical or not20:04
dhellmannmaybe we should focus on the application, and figure out the deadline question if we decide to go ahead20:04
flaper87EmilienM: ^20:04
jrolllooks like great progress, I'd think it's pretty clear at this point they are one of us20:04
stevemarlooks like it's just py35 and test stuff left -- and given storlets track record, i think they'll get it done20:04
dhellmannflaper87 : what's the story with java testing? are we able to support that now?20:05
thingeestevemar ++20:05
johnthetubaguyjroll +120:05
EmilienMflaper87: no blocker on my side. My questions were answered correctly20:05
dimsagree stevemar20:05
dtroyerAre we going to require a CTI or anything like that for the Java bits?20:05
jrollstevemar: +1, and those aren't things we require today20:05
dimscast my +120:05
dhellmanndtroyer : good question20:05
EmilienMjroll: +120:06
flaper87dhellmann: afaik, it's a work in progress20:06
flaper87eranrom: you might want to chime in a bit more on the java side of things20:06
jrollthey've moved to openjdk, at least20:07
eranromCTI==Continous Test Integration?20:07
fungiconsistent testing interface20:07
dhellmannttx: do we have a position on java? there's some precedent with monasca20:07
flaper87jroll: yes20:07
dtroyerI'm not thrilled with the inconsistency we have WRT languages here...20:07
dhellmanndtroyer : ++20:07
eranromif so then while we are lacking unit tests we do have functional tests in place20:07
ttxwell, I think this falls into the integration point rule20:07
ttxlike a java sdk20:07
eranromSo the java code is being regularly tested20:07
fungi#link https://governance.openstack.org/tc/reference/project-testing-interface.html20:07
dhellmanneranrom : we don't have a CTI documented for java: https://governance.openstack.org/tc/reference/project-testing-interface.html20:07
fungieranrom: ^20:07
ttxit's not a service in java, it's a workload environment20:08
ttxso while it would be great to properly test it, I don't think we need a CTI20:08
flaper87yeah, fwiw, the java code is not on the service side20:08
ttxsince that would be pretty unique20:08
*** caboucha_ has joined #openstack-meeting20:08
jrollright, similar to how trove runs mysql, right?20:08
*** caboucha has quit IRC20:08
EmilienMttx: right20:08
ttxjroll: yes20:08
kota_ttx: true and as eranrom said, we have a few functional for java app in workload20:08
fungiright, i think the question is whether the java-based payloads need to get tc approval as a "supported" language and have cti addition and whatnot. i thought we'd determined previously they did not20:08
ttxmore like a service VM20:08
kota_s/we/storlets/20:08
jrollttx: yes, that's the words I wanted :)20:09
johnthetubaguyjroll +120:09
flaper87fungi: otoh, I'd say no but I haven't dug too much into that thought20:09
ttxdhellmann: but yes, we migt want to clarify that distinction to explain why it's OK here20:09
thingeettx ++20:09
johnthetubaguyfor the folks storlets are aiming at, they do everything in Java, so it would be odd to require those folks to learn python20:10
dhellmannttx: someone else may need to do that, because I don't see the distinction myself. It's not a *service* but it's running on the server and defines an API, so I would think we would want some form of test for it.20:10
dtroyerwe cared enough about which SDK was used, that was only due to redistribution concerns then?20:10
ttxthe "service" is really swift here. Storlets is glue code to run payloads, and the Java payloads use a Java runtime shim20:10
mtreinishdtroyer: yeah, that was my understanding for the openjdk bit20:10
dhellmanndtroyer : yeah, we can't test with the oracle jdk in the gate, IIUC20:10
ttxdtroyer: yes20:10
fungiso the only "java" produced by the storlets team is example code, it sounds like20:11
*** askb has joined #openstack-meeting20:11
ttxfungi: last time I looked there was some glue code to expose environment bits20:11
flaper87ttx: indeed, I don't think that's changed20:11
dtroyerplus a tiny bit of C20:11
fungioh, got it. so a minimal shim in java20:11
jrolldon't get me wrong, I'd love to see the storlets team define the java CTI and run unittests on the libraries it exposes, but I don't believe it's a blocker here20:11
*** nadya has quit IRC20:12
*** clenimar has quit IRC20:12
ttxjroll++20:12
ttxWe have enough to approve this20:12
dhellmannif we ignore the CTI question, are there actually tests for the java shim?20:12
dhellmannttx: I would like to get this clarified before we move on20:12
eranromdhellmann: functional tests20:12
jrolldhellmann: they run functional tests with a java workload20:12
ttxI'll let eran20:12
ttxanswer20:12
mtreinishdhellmann: from the quick scan I just did, they test it indirectly via functional tests. But no direct unittesting or anything like that20:12
johnthetubaguymtreinish: thats what I am seeing20:13
dhellmannand those functional tests run in a gate job somehow?20:13
eranromyes20:13
dhellmannok, then I'm satisified20:13
EmilienM(using ansible)20:13
EmilienM(and plan to use devstack iiuc)20:13
dhellmannthanks, eranrom20:13
ttxit's not the end of the integration journey anyway, more like a milestone20:13
dhellmannas long as the stuff is actually being tested, we can discuss a java CTI separately20:13
dhellmannsince they're functional tests, that may not apply here20:14
ttxok, any other objection before I approve ?20:14
mordredalso, between storlets, monasca and the infra projects that are in java, I think we've got a good corpus to define a java CTI should we decide that's a good idea20:14
dhellmann++20:14
ttxok, approving20:14
dtroyermordred: I think ti is a good idea, not blocking here20:14
mordred++20:14
dims++ mordred dtroyer20:15
ttxeranrom: welcome!20:15
eranrommordred: sounds like a good topic for one of the cross project deiscussions20:15
mordrederanrom: totally agree20:15
eranromttx and all: Thanks very much.20:15
jrollmordred: ++20:15
fungibrowsing the storlets src/ subtree, there's a nontrivial quantity of java under there20:15
thingeeeranrom congrats and good work20:15
ttxthansk flaper87 for following up and mentoring them20:15
eranromthingee: Thanks!20:15
fungii'm surprised it doesn't have unit tests20:15
kota_thanks all (i'm working for storlets)!20:15
flaper87my pleasure20:15
ttx#topic Reference doc for new language additions20:15
*** openstack changes topic to "Reference doc for new language additions (Meeting topic: tc)"20:15
eranromflaper87: Thanks for working with us on this.20:15
* EmilienM thinks flaper87 has superpowers20:15
dtroyerI think we should encourage them to work in that direction (unit testin gthe JAva)20:16
mtreinishfungi: http://paste.openstack.org/show/592955/20:16
dims++ dtroyer20:16
flaper87o/20:16
ttx#link https://review.openstack.org/39887520:16
ttxI like the general principles laid out here (the two-step dance)20:16
flaper87so, I've addressed some of the comments and I replied to the latest comments from dhellmann ttx and dtroyer20:16
flaper87thanks a bunch for commenting on it20:16
flaper87I'm good with amending the current proposal and, at this point, wait till next year to approve it20:17
ttxI see it as a living document and the current version is probably good enough as an initial doc20:17
dtroyerI think it is pretty good shape20:17
flaper87there's no rush and I'd rather give some extra time to chime in on this20:17
dtroyerttx: ++20:17
ttx(if we wanted to approve the initial version now)20:17
ttxflaper87: I'm fine with doing one more iteration, too20:17
ttxflaper87: ok, so do you have anything specific to discuss today ?20:17
flaper87however, if people feel this can go in now and amends can be done in follow-up patches, I can do that too20:17
jrollprobably want to drop that note at line 24 before publishing, yeah?20:17
dhellmannThe requirements management is one of the bigger issues, so I'd like to get that written down before teams start using this process. That could still happen as a follow-up, I guess.20:18
fungii expect we're going to end up with subsequent changes to this document before any new language makes it through the gauntlet regardless20:18
flaper87ttx: not really, I've reached out to more people on IRC and there doesn't seem to be strong opposition to this proposal20:18
ttxwe don't have any urgency in approvign that now rather than next meeting tbh20:18
flaper87yup20:18
dimsagree ttx flaper8720:18
thingeegood work flaper8720:18
flaper87I'll be out next week and the one after next week so, we can postpone this till next year :)20:18
flaper87thingee: danke :D20:19
ttxok, then unless there are questions we can move on to the next topic so that we have enough time to cover everything20:19
flaper87by all means, if there are more questions/concerns, this is the time.20:19
flaper87but don't ruin my new years celebration20:19
ttx#info one more iteration, final approval expected at next meeting20:19
dtroyerthanks flaper8720:19
flaper87dtroyer: my pleasure20:19
*** raildo has quit IRC20:20
ttxok then, moving on20:20
ttx#topic Amend reference/PTI with supported distros20:20
*** openstack changes topic to "Amend reference/PTI with supported distros (Meeting topic: tc)"20:20
ttx#link https://review.openstack.org/40294020:20
EmilienMo/20:20
ttxWe presented this one a couple weeks ago and there were objections due to regular job failures on CentOS20:20
ttxEmilienM: floor is yours20:20
EmilienMwell, if you have some questions or concerns about this proposal, please go ahead20:21
mtreinishttx: was there any change on that?20:21
fungiit's sounded like there's some confusion over what's currently actually tested, and what needs to be tested, to move forward20:21
sdagueihar and ianw seem to have been watching more closely and think it's probably ok for single node20:21
*** kota_ has left #openstack-meeting20:21
EmilienMttx: I don't have anything to add now, I think I addressed comments in the proposal20:21
sdagueat least from comments in the review20:21
fungithe outstanding concern seemed to me to be over what features/tests are currently didabled to get those basic devstack-gate jobs passing20:22
mtreinishfungi: there is still the disparity between what's tested. But the way the proposal is worded that's not necessarily a blocker20:22
fungis/didabled/disabled20:22
sdagueI feel like the proof is probably going to come in the pudding. We've disabled voting on those jobs before when it was blocking unrelated work from moving forward20:22
ttxyeah, I think the proposal is sufficiently weakly-worded to be aspirational20:22
fungiso the question remains, what happens if we need to disable those jobs again once this resolution passes?20:23
mtreinishtbh, I'd rather see things being run everywhere before we merge this20:23
ttxbut on those issues I like to trust our QA people judgment20:23
fungiis approving 402940 the turning point where if the job breaks we tell people to suck it up and work on fixing the job or whatever broke it because we're not going to turn it off any longer?20:24
sdagueso I'm fine with this being aspirational, and realize that realities mean we're not going to shut down the ship if there is a centos issue we can't get resolved in a timely manner.20:24
EmilienMfungi: we can't force folks to keep the job voting, if it's blocking something. But we can assume good faith on the desire to test both platforms20:24
EmilienMfungi: I don't think that's the idea behind this proposal, at least not from my side20:25
fungii guess as long as it leaves us with the same flexibility/options we have now, i'm not opposed20:25
fungiwhich seems to be the case20:25
ttxWe have a majority now. mtreinish would rather see things being run everywhere first. Any other objection ?20:26
sdagueso my feeling is always that test jobs are information to help humans make better decisions. As such, they should always be treated in an advisory capacity, and turned off when they are doing more harm than good20:26
dims++ sdague20:26
sdaguewhich is true of anything that currently votes20:26
EmilienMsdague: yes, I do agree.20:26
fungisgtm20:26
sdagueand this would be in the same capacity20:26
dhellmannI would hope we would prefer fixing jobs over turning them off, but I agree with the general idea that sometimes expediency calls for turning them off20:26
ttxAlright, it feels like we have support for this to be merged now20:27
sdaguedhellmann: or, you know, you pull the car over and change to a spare tire, and keep going, instead of sitting on the side of the road out of priciple20:27
EmilienMdhellmann: me too, though it's a matter of resources available to work on $topic. I would expect them growing if we recognize this platform as "official" in our testing20:27
* dtroyer has to fix a flat after the meeting… thanks for the reminder sdague20:28
sdague:)20:28
dhellmannsdague : fix the tire instead of just removing it and trying to drive on 3?20:28
* ttx approves20:28
ttxand moves on20:28
EmilienMttx: thanks20:28
ttx#topic Driver teams: establish new "driver team" concept20:28
dhellmannthanks, EmilienM20:28
*** openstack changes topic to "Driver teams: establish new "driver team" concept (Meeting topic: tc)"20:28
ttxAs promised last week I pushed the "amended grey" option back to the -dev list for community comments20:28
*** saisrikiran has joined #openstack-meeting20:28
ttx#link https://review.openstack.org/40382920:28
mordredsdague: just drive on the flat20:28
ttxThere were a number of public objections, but not for the same reasons. Let me summarize them20:28
ttxjaypipes basically thinks we should not have vendor teams in OpenStack, prefers the soft black option20:29
*** haleyb-away has quit IRC20:29
ttx#link https://review.openstack.org/#/c/403836/20:29
ttxIt is, I think, the crux of the issue: is allowing driver teams more destructive than not allowing them ?20:29
ttxJay Faulkner and Bob Melander advocate for a more weakly-worded clause around drivers extending APIs20:29
ttxI proposed an alternate wording in the comments, that would cover the Ironic case20:29
ttxjaypipes objects to softening the language around drivers extending APIs, but frankly I think that's a larger discussion (about interoperability and strict APIs) not really tied to driver teams in particular20:29
ttxas it affects all drivers, in-tree or out-tree.20:30
mordredI agree with anyone saying we should be stricter about APIs, fwiw20:30
ttxNext, cdent and John Davidge object to "strongly preferring" in-tree drivers20:30
ttxWhich is also a good point. Drivers are using plug-in points, so why maintain some of them in-tree in the same code repository ?20:30
ttxMy take on it is that you should either have all drivers out of tree, or you should strongly prefer in-tree. But having some in-tree and some out-tree with an arbitrary boundary is not really awesome.20:30
smcginnisttx: +120:30
dhellmannbecause quite a lot of our driver APIs are not well defined20:30
mordred++20:30
ttxJohn Davidge also objects to the obfuscation of brands in team names, making lives of users more miserable20:30
ttxI think this concern comes from the lack of proper driver catalogs -- people should not go through the official OpenStack team list to find their drivers20:31
dtroyerI think in-tree reference drivers (like LVM in the cinder case) are good to maintain20:31
mordredttx: can you give an example?20:31
ttxif only because they won't find in-tree drivers in there20:31
mtreinishttx: at least for ironic api thing I didn't see an issue with the current wording. It's not modifying the api, just using a free form vendor endpoint that ironic exposes20:31
dtroyerwould support moving the rest20:31
sdagueit's not just our driver APIs being not well defined20:31
ttxSo in parallel with this we should invest in making the driver section of the OpenStack marketplace actually usable20:31
ttxAnd probably make sure that project docs reference drivers too.20:31
sdaguemany people complain that it is hard to get things into openstack20:31
ttxAndreas Scheuring and jaypipes wondered how that obfuscation might work in practice20:31
sdagueif you have to coordinate feature adds across multiple git repos thaat gets so much harder20:32
ttxbut I think we have a good example case with the "Winstackers" team, and we have a history of creative naming20:32
*** guoshan has joined #openstack-meeting20:32
*** weshay_relocate is now known as weshay20:32
ttxOK, so let's take those one by one. First the proposed modifications to grey:20:32
ttx* Softening the language around drivers extending API. Good idea, bad idea ?20:32
mtreinishttx: bad idea20:32
mordredbad idea20:32
dhellmannI should also point out that the text doesn't say "in tree" but "in the consuming projects" by which I meant in a repo owned by that project team20:32
flaper87yeah, I'd prefer not to soften the language20:32
fungikeeping in mind that it sounds like most neutron drivers today "extend" the neutron api in at least some ways20:33
ttxshould we go after Ironic for having such a capability in their drivers ?20:33
dhellmannthe bit after the comma comes after the comment, so it's not as clear20:33
dims+1 to not soften the language20:33
mordredfungi: don't even get me started on that20:33
mtreinishfungi: yep...20:33
fungi(of course, maybe that provides a lot of examples for why it's a bad idea?)20:33
*** thorst has joined #openstack-meeting20:33
sdagueneutron drivers already do this, it has caused substantial pain20:33
EmilienMbad idea, I agree20:33
jrollttx: oh, that would be fun :)20:33
sdaguettx: bad idea20:33
*** thorst has quit IRC20:33
dtroyer++20:33
bswartzsorry I only read this proposal just now and I'm late to the party, but out of tree drivers are terrible because they practically ensure that the interfaces can never evolve20:33
bswartzI strongly prefer in-tree drivers20:33
ttxgreat segway20:34
ttx* "Strongly encouraging" in-tree drivers. Good idea, bad idea ?20:34
dhellmannttx: I thought ironic used that API extension point for evolving new APIs20:34
sdaguettx: good idea20:34
EmilienM+120:34
flaper87ttx: +120:34
stevemarso cinder wants in-tree and neutron wants out-of-tree :)20:34
dhellmannttx: it's not actually "in-tree" though, see my earlier comment20:34
dimsgood idea20:34
bswartzmanila wants in-tree as well20:34
* ttx reads20:34
stevemarjroll: what about ironic?20:34
mtreinishstevemar: iiuc neutron is the only thing this really effects in practice20:34
mordredI agree more with what ttx said on this earlier - "My take on it is that you should either have all drivers out of tree, or you should strongly prefer in-tree. But having some in-tree and some out-tree with an arbitrary boundary is not really awesome"20:34
jrolldhellmann: we do use that API for that, and I'm happy to have that conversation, but I'd love to keep on this topic and talk about that later20:34
stevemarmtreinish: agreed20:35
mtreinishbecause the other projects don't support out of tree drivers20:35
dhellmannit says "in the consuming projects and managed by the same contributors in a collaborative fashion, *whether by including drivers "in tree" or by placing them in separate repositories owned by the same team"20:35
mordredI do not agree with the objections to out of tree drivers20:35
dhellmannttx: ^^20:35
mordredin fact20:35
jrollironic prefers in-tree drivers, but has CI requirements for those, and allows out-of-tree drivers for drivers that do not have CI20:35
ttxdhellmann: oh right20:35
dhellmannit's about repo ownership20:35
mordredI tihnk we should strongly encourage driver APIs to be treated like apis so that people who want out of tree drivers can without being screwed20:35
ttxdhellmann: got it20:35
fungimy take on it is that there are always going to be some out-of-tree drivers because they're developed by third parties, possibly even outside the community entirely20:35
mordredfungi: ++20:35
ttxyeah, then I'm not convinced by that objection20:35
jrollironic also tries to keep the driver API stable, but doesn't make promises (though we'd love to get there)20:35
ttx* Brand obfuscation in team names. Good idea, bad idea ?20:36
dhellmannright, the point of this phrase is we want to encourage teams to do things in a way that makes it less painful, not more20:36
fungias to whether or not we encourage that, or consider such drivers in need of "official recognition" by the tc, i'm unsure20:36
dhellmannand to encourage collaboration, not more driver teams20:36
jrollfungi: except in projects like nova that actively write code to disallow loading out-of-tree drivers :)20:36
*** e0ne has joined #openstack-meeting20:36
mordredttx: I thnk brand obfuscation is a tricky subject20:36
bswartzmordred: forget about screwing driver developers -- it's the driver developers that are screwing the projects (in some cases)20:36
*** lpetrut has quit IRC20:36
jrollfungi: (but then people will just patch the tree, etc, you can't win)20:36
smcginnisjroll: Same for Cinder re: "tried to keep the driver API stable, but doesn't make promises"20:36
fungijroll: which can be "solved" by also distributing a nova fork, probably happens20:36
jrollyep20:36
fungiright, thath20:36
*** Leo_ has quit IRC20:36
sdaguejroll: there is still a hook for loading out of tree drivers20:37
*** guoshan has quit IRC20:37
ttxmordred: I added it after dsicussing with fungi ways to avoid to turn the project team list into a walking billboard20:37
sdaguewe do tell people it's not officially supported and they should be working in the community instead20:37
*** lpetrut has joined #openstack-meeting20:37
mordredttx: for instance, it's entirely possible the nova-docker driver could hit legal issues with docker inc's move to make 'docker' all about the company and we could run in to a situation where a team who cared aout that would not be able to legally call themselves the docker team20:37
jrollsdague: I'm skeptical, would love to see that after the meeting20:37
fungiin short, any time we give companies a place to list themselves, everyone wants to avoid being outdone by their competitors and looks for a way to get added to the list20:37
dtroyerI like the team name vs repo name distinction, didn't catch that the first time through20:37
ttxdtroyer: ++20:38
sdaguemordred: the nova docker driver that is abandoned?20:38
dhellmannfungi : will we also forbid the use of trademarks in the team mission descriptions?20:38
mordredsdague: irrelevant for the purposes of example of why naming a driver team after a thing that is trademarked can be problematic20:38
ttxI guess it's easy to change our stance on the brand obfuscation thing. Team renames are cheap20:38
mtreinishsdague: there is a clone of it in the zun repo. It'll never die :)20:38
ttxI'm willing to give it a try though20:38
fungimordred: i'm honestly less concerned about legal ramifications of trademarks appearing in team names. that concern possibly also applies to deliverable/repo names which we aren't proposing any restrictions on20:39
mordredI just don't think we know enough to make a hard rule on that20:39
ttxfor reasons outlined by fungi20:39
jrollfungi: so reading your comments, you'd be okay with a 'bar' team that has a neutron-foo driver, to support foo branded switches, but not okay with a foo team doing that, correct?20:39
jrollor ttx ^20:39
ttxjroll: yes20:39
jrollok, thanks20:39
fungijroll: basically, yes. a lot of that is because we have one place we list all team names, but we don't list the deliverables for all projects in one place (except in structured data files where the proposal intermixes them with normal teams)20:40
* jroll doesn't have a strong opinion, then20:40
dhellmannit will be interesting to see what effect, if any, the obfuscation rule has20:40
ttxjroll: think Winstackers doing a nova-hyperv repo20:40
jrollttx: good example, thanks20:40
ttxdhellmann: as I said we can easily come back on that one20:40
dhellmannyeah20:40
ttxOK, so that leaves us with the crux described above. Do we want vendor-led driver teams or not20:40
ttxIf we do, I would argue that grey is now looking like a reasonable compromise. If we don't, we should pick soft black20:40
dims+1 to no trademarks in the team/deliverable/repo names for vendor led teams20:41
*** Leom has joined #openstack-meeting20:41
mordredI think they are valuable, although I totally understand the concerns with their existence20:41
fungiso far the only official teams we have with trademarked terms in their names are also the names of free software projects which just happen to be trademarked, which i find less objectionable20:41
* dims remembers java.apache.org -> jakarta.apache.org20:41
ttxjaypipes makes a good case that it could be harmful. it's just difficult to judge which option is actually the most destructive20:41
dtroyerI can live with vendor-led teams as a fallback, still like the idea that they should be considered that and not a frist choice20:41
mordreddtroyer: ++20:41
dhellmannright, dtroyer, I think given that we're not going to just accept all teams, that they have to go through the consuming project first, it will be manageable.20:41
dimsdtroyer : yep20:41
fungiworth noting, the grey option is still my third choice. but the proposal is one i could support if there is sufficient backing from the rest of the tc20:42
ttxTo me the question is, are we going to get more core contributions by having them in, or by keeping them out20:42
ttx(by core I mean contributions to the consuming service)20:43
dtroyergiven the (perception at least) of the current corporate climate, we're going to see a lot of minimal amount of effort stuff I am afraid20:43
stevemardtroyer: good point20:43
flaper87I'm leaning towards in. I don't think keeping them out is not really going to help with getting more contributions, I think20:43
dhellmannI suppose if we say no to the teams, we just wouldn't see their efforts at all.20:44
mordredI don't think core contributions is the only thing that's relevant - I think empowering our consumers to use the hardware items they want to use is also important, and sometimes that may involve empowering the vendor of that thing to maintain something nobody else cares about20:44
ttxanother way to put it would be... will we get enough extra core contributions to justify compromising on our open collaboration principles20:44
mordredeven if we don't like that vendor20:44
dhellmannmordred : yes, good point20:44
dimsmy opinion, driver team option is a safety valve to keep folks in. so +120:44
jrollidk. with the cisco team as a specific example, sambetts is an ironic core, that team cares about cisco stuff working in the entire openstack ecosystem, not just their neutron driver20:44
smcginnismordred: +120:44
fungii mostly just want to make sure that companies coming to us trying to get their "driver team" listed to raise their visibility have somewhere "better" we can direct them (e.g., driver marketplace on www.o.o)20:44
mordredfungi: +20:44
mordredfungi: ++20:44
jrollsam is a heavy driver (heh) of a lot of ironic's networking work20:44
mordredjroll: yes. that is the healthy way to do things and what we should _always_ prefer20:45
*** sdake has joined #openstack-meeting20:45
dhellmannjroll : I think it speaks highly that they asked to be an official team under the existing rules.20:45
sdagueright, if the source code lives in gerrit, it means that users are empowered even if their vendor abandons the effort down the road. There is a collaboration space20:45
dtroyerwhat I do like about the driver teams is that ensures that the cose as it stands is available for customers should the vendor disappear.  it isn't sufficient, but better than it being buried and possibly disappeared on github in that case20:45
dtroyers/cose/code/20:45
mordreddtroyer: ++20:45
jroll(I can't speak for other vendor teams, of course)20:45
sdagueand it's part of the workflow that lets someone understand how to work on common code20:45
mordredalso - a vendor who wants a driver team to be official is saying that they'd LIKE non-company people - they may just not have any20:45
fungidtroyer: the irony there is that if the vendor abandons that repo and some other unrelated team takes it over, they could probably qualify as an official team under our existing rules ;)20:45
jrollI like this grey option in that the TC will prefer to try to get the team to work with the project they plug into first, and being a separate team as a fallback20:46
mordredif a company wants to do out of tree drivers just with themselves, the overhead to doing things 'officially' is silly for them to carry20:46
ttxTo avoid the "contributes only to their driver team and consider it's contributing enough to openstack as a result" -- we could list driver teams ina subcategory in stackalytics20:46
jrollallows folks on both sides to document why it doesn't fit20:46
sdaguebecause, our workflow is different enough from what's considered norms today, that any additional ways to get there are good20:46
dtroyerfungi: I would hope in that case moving back into the project team oversight is what happens20:46
flaper87jroll: indeed20:46
johnthetubaguyit feels like we should welcome them into the community to learn form each other on how to be successful at doing this thing, I don't want to exclude them, it hurts our users wanting to use their things if they do it badly20:46
fungidtroyer: if the consuming project team would allow it, but some do not want that added responsibility20:46
dhellmannjohnthetubaguy : ++20:46
ttxok, I feel a group leaning toward "in"20:47
* dhellmann is happy to see others making the same arguments that led to starting this whole mess20:47
mordredjohnthetubaguy: ++20:47
ttxI can live by both outcomes at this point (grey or softblack)20:47
jrolldhellmann: :)20:47
johnthetubaguyat least its explicitly messy20:47
johnthetubaguy(now)20:47
ttxany other advocate for "out" ?20:47
mtreinishwhat I'm still struggling with is what "in" actually means here, and the benefits it provides a driver team20:48
*** whenry has quit IRC20:48
ttx(Because if I read your previous answers I should actually not modify grey)20:48
mtreinishlike the infra workflow was always available to them as was hosting a repo in openstack/20:48
ttxmtreinish: they become an official openstack project team, with controlled /limited scope20:48
dimsmtreinish : access to horizontal teams20:48
ttxmtreinish: vote for TC20:48
*** sdake_ has quit IRC20:48
jrollmtreinish: docs.openstack.org access is the main thing people want, from what I've heard20:48
ttxPTG space20:48
stevemarthanks for asking mtreinish20:49
mtreinishso docs.o.o, a tc vote, and ptg access?20:49
dhellmannmtreinish : they're asking to be "in". We don't currently say there must be a benefit to any other teams asking to join.20:49
stevemarjroll: the part of docs.o.o? the developer docs? or guides?20:49
jrollATC/PTG, folks are happy to have, but don't care as much, afaict20:49
thingeejroll +1 heard that from neutron folks20:49
jrollstevemar: being able to publish anything anywhere on that site (primarily dev docs, but now install guide plugins etc)20:49
mordredI think these are people who have banked a bunch on openstack, and they want us to consider them one of us20:49
* stevemar nods20:49
mtreinishdhellmann: well in this case it matters because we're defining a new subset of projects that is different20:49
thingeestevemar vendors want to be able to document setting up an environment with their drivers.20:50
*** thorst has joined #openstack-meeting20:50
stevemarthingee: that sounds perfectly reasonable20:50
dhellmannmtreinish : why does that make it matter? are you worried we're giving up too much somehow?20:50
*** Sukhdev has quit IRC20:50
thingeeI agree. current rules disallow neutron drivers today though20:50
ttxIf you made your decision can you cast your +1 for either proposal ? Just so that we know where we stand20:50
ttxLooks like overwhelming support for grey as it stands20:51
fungione remaining concern i have with the grey option is that it may imply, to teams who end up developing drivers without skewed employer affiliation using publicly available specifications and/or reverse-engineering, that they're supposed to apply as a driver team and don't realize they could be full-fledged project teams20:51
ttxI'm fine approving it now since we covered all the objections that were raised and decided to bypass them20:51
mtreinishdhellmann: I am concerned about that because these teams are very specifically about a single product. The level playing field thing is there for a reason20:51
dhellmannfungi : we can guide them when they apply for status20:51
dimsagree dhellmann20:52
fungidhellmann: yes, i hope we'll be aware enough to do so20:52
ttxyes we need to accompany those, and probably write a bunch for the project team guide20:52
dhellmannmtreinish : are you concerned about what the teams get, or what we get? I don't see how the single product question is related to your earlier question.20:52
mordredmtreinish: yah - I do not think we should allow single-vendor services20:52
dhellmannI also don't think we should keep driver teams if they do not accept valid contributions from outside the vendor.20:52
thingeemordred mtreinish ++20:53
mordreddhellmann: ++20:53
mordreddhellmann: we should maybe encode that20:53
mtreinishdhellmann: I'm trying to weigh what the community gets vs what the vendor gets20:53
dhellmannperhaps, I had trouble coming up with wording20:53
ttxok, should we approve this now or discuss it one more time20:53
mordreddhellmann: fair20:53
ttxbecause I have stuff to discuss in open discussion20:53
dhellmannmtreinish : so you're worried that vendors will ask to live under our rules and somehow hoodwink us into giving them more benefit than we get?20:53
jrolldhellmann: I feel like the outside contributions thing is part of "open development"20:53
*** gordc has left #openstack-meeting20:53
dhellmannttx: ok20:54
dhellmannjroll : yep20:54
fungii'm okay pressing forward. while grey is not my preference, my concerns are addressed sufficiently by it20:54
flaper87I'm ok with the proposal as it is20:54
stevemarttx: is today the cutoff for driver teams getting ptg space?20:54
dimsy, already has my +120:54
EmilienMsame20:54
ttxstevemar: not really. But some teams have been patiently waiting that we get our house in order20:54
*** thorst has quit IRC20:55
ttxmtreinish: ?20:55
ttxcan you live by it ?20:55
stevemargotcha20:55
mtreinishttx: I'd be fine with it. But I still have concerns20:55
* fungi still finds those leadership training catchphrases mildly creepy20:55
ttxconcerns that we can address in subsequent changes ?20:56
mtreinishI'm not sure, I think it's a more fundamental question about why20:56
flaper87ttx: perhaps we should postpone it till next year with the language one20:56
ttxok, let's not rush it20:56
thingeeyes, four mins left too20:56
ttx#topic Open discussion20:56
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:56
ttx* Joint TC/Board meeting20:56
ttxI had an exchange with Alan and we agreed that tacking a half-day at the start or the end of a long PTG week wasn't likely to deliver the desired results20:57
mtreinishlike I think the rules outlined make sense, I'm just worried about the implications of it20:57
ttxThey are now looking into a specific 1-day or 2-day workshop to make progress on the "OpenStack futures" discussion20:57
ttxWhich might be tied to a future ops meetup or OpenStack Day or leadership training to make the trip worthwhile20:57
ttxLong story short, won't happen on Sunday or Friday of the PTG, so you can book your flights20:57
dimsgreat thanks ttx20:57
*** e0ne has quit IRC20:57
ttx(I'll likely arrive Saturday afternoon, so I'm happy to see people on Sunday)20:57
persiaTying it to something is very appealing for those of us who wish to observe.20:57
ttx* Election officials for Pike PTL elections20:57
ttxWe have volunteers to be "officials": tristanC & diablo_rojo20:58
ttx(They said they would not run for PTL election)20:58
jrollpersia: ++20:58
ttxIf you don't have objections, I propose we let them start organizing since we don't have that much time left20:58
dhellmannttx: ++20:58
dtroyer++20:58
ttx* Skipping next two meetings20:58
fungithanks for volunteering, tristanC and diablo_rojo!20:58
ttxDec 27 is likely to be lightly-attended20:58
dims++ ttx20:58
EmilienMttx: no objection20:58
ttxJan 3... we could have a meeting then, especially since we now have a bit of a backlog20:58
ttxyou tell me20:58
johnthetubaguy++ for both of those20:58
dims+1 to skip20:58
*** neiljerram has joined #openstack-meeting20:58
mtreinish+120:58
dtroyer+1 on Jan 3 next meeting20:58
dhellmann+1 to skip the 27th and meet on Jan 320:59
dims+1 to Jan 320:59
johnthetubaguyyeah, 3rd seems fine for me20:59
fungii'll need excusing from any meeting on the 27th but am available for the 3rd20:59
flaper87I'll be out on Jan 3, likely20:59
EmilienMwait, I thought we would meet and celebrate together20:59
EmilienMoh well, +1 then :-)20:59
ttxlet's close the driver-team stuff on Jan 3rd ?20:59
thingee+1 to skip 27th, next meeting jan 320:59
ttxmtreinish: you'll be around ?20:59
mtreinishon jan 3rd?20:59
mtreinishyeah20:59
ttxok20:59
sdague+1 for skip 27th20:59
ttx#agreed skip the 27th and meet on Jan 320:59
ttxAnything else, anyone ?21:00
ttxwith 0 seconds left ?21:00
jrollhe says at the buzzer :)21:00
ttx#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Tue Dec 20 21:00:21 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
stevemari think were good21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-12-20-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-12-20-20.00.txt21:00
sdagueenjoy the holidays folks21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-12-20-20.00.log.html21:00
ttxand happy new year!21:00
EmilienMthanks ttx for chairing!21:00
*** AJaeger has left #openstack-meeting21:00
EmilienMsdague: ++21:00
jrollthanks ttx, see y'all next year21:00
stevemarhappy holidays all21:00
thingeehappy holidays!21:00
johnthetubaguyhave a good one all!21:00
*** ayoung has quit IRC21:01
*** ayoung has joined #openstack-meeting21:01
*** dmorita has quit IRC21:04
*** DavidPurcell has left #openstack-meeting21:05
*** ykatabam has joined #openstack-meeting21:06
*** gouthamr has quit IRC21:09
*** lpetrut has quit IRC21:11
*** nadya has joined #openstack-meeting21:12
*** mtanino has quit IRC21:13
*** nadya has quit IRC21:16
*** saisrikiran has quit IRC21:18
*** dmorita has joined #openstack-meeting21:19
*** cody-somerville has joined #openstack-meeting21:19
*** dmorita has quit IRC21:20
*** irenab_ has joined #openstack-meeting21:21
*** irenab has quit IRC21:21
*** irenab_ is now known as irenab21:21
*** zara_the_lemur__ has left #openstack-meeting21:22
*** mrda is now known as michaeld21:22
*** thorst has joined #openstack-meeting21:23
*** michaeld is now known as mrda21:24
*** julim has quit IRC21:28
*** thorst_ has joined #openstack-meeting21:30
*** thorst has quit IRC21:31
*** guoshan has joined #openstack-meeting21:32
*** weshay is now known as weshay_afk21:33
*** sdake_ has joined #openstack-meeting21:34
*** thorst_ has quit IRC21:35
*** sdake has quit IRC21:35
*** guoshan has quit IRC21:37
*** sdake has joined #openstack-meeting21:39
*** dmorita has joined #openstack-meeting21:39
*** eranrom has quit IRC21:42
*** sdake_ has quit IRC21:42
*** fnaval has quit IRC21:43
*** jungleboyj has quit IRC21:43
*** AlanClark has quit IRC21:45
*** Leom has quit IRC21:45
*** fnaval has joined #openstack-meeting21:45
*** fnaval has quit IRC21:46
*** fnaval has joined #openstack-meeting21:46
*** fnaval has quit IRC21:47
*** dprince has quit IRC21:48
*** fnaval has joined #openstack-meeting21:48
*** coolsvap has quit IRC21:49
*** fnaval_ has joined #openstack-meeting21:50
*** fnaval__ has joined #openstack-meeting21:51
*** Leom has joined #openstack-meeting21:53
*** fnaval___ has joined #openstack-meeting21:53
*** fnaval has quit IRC21:53
*** fnaval has joined #openstack-meeting21:55
*** fnaval_ has quit IRC21:56
*** AlanClark has joined #openstack-meeting21:56
*** fnaval_ has joined #openstack-meeting21:57
*** fnaval__ has quit IRC21:57
*** fnaval__ has joined #openstack-meeting21:58
*** fnaval___ has quit IRC21:58
*** fnaval has quit IRC22:00
*** fnaval has joined #openstack-meeting22:00
*** fnaval___ has joined #openstack-meeting22:01
*** fnaval_ has quit IRC22:02
*** caboucha_ has quit IRC22:02
*** fnaval_ has joined #openstack-meeting22:03
*** lblanchard has quit IRC22:04
*** cleong has quit IRC22:04
*** fnaval__ has quit IRC22:04
*** fnaval has quit IRC22:05
*** fnaval has joined #openstack-meeting22:05
*** fnaval__ has joined #openstack-meeting22:07
*** fnaval___ has quit IRC22:07
*** fnaval___ has joined #openstack-meeting22:08
*** fnaval_ has quit IRC22:09
*** fnaval_ has joined #openstack-meeting22:10
*** fnaval has quit IRC22:10
*** Sukhdev has joined #openstack-meeting22:10
*** fnaval__ has quit IRC22:12
*** gouthamr has joined #openstack-meeting22:14
*** thorst has joined #openstack-meeting22:14
*** fnaval___ has quit IRC22:14
*** thorst has quit IRC22:16
*** armax has quit IRC22:16
*** thorst has joined #openstack-meeting22:16
*** eharney has quit IRC22:21
*** mtanino has joined #openstack-meeting22:21
*** jmckind has quit IRC22:22
*** s3wong_ has joined #openstack-meeting22:22
*** Leom has quit IRC22:23
*** abalutoiu has joined #openstack-meeting22:24
*** thorst has quit IRC22:25
*** s3wong has quit IRC22:25
*** jamesdenton has quit IRC22:26
*** saisrikiran has joined #openstack-meeting22:28
*** mtanino has quit IRC22:29
*** diablo_rojo has quit IRC22:30
*** guoshan has joined #openstack-meeting22:33
*** saisrikiran has quit IRC22:35
*** Sukhdev has quit IRC22:36
*** guoshan has quit IRC22:38
*** Sukhdev has joined #openstack-meeting22:38
*** nadya has joined #openstack-meeting22:45
*** TxGirlGeek has quit IRC22:47
*** galstrom_zzz is now known as galstrom22:49
*** nadya has quit IRC22:50
*** Swami has quit IRC22:59
*** galstrom is now known as galstrom_zzz22:59
*** AlanClark has quit IRC23:00
*** salv-orlando has joined #openstack-meeting23:06
*** tommylikehu_ has quit IRC23:07
*** sdague has quit IRC23:08
*** TxGirlGeek has joined #openstack-meeting23:10
*** rbudden has quit IRC23:16
*** claudiub has quit IRC23:18
*** fguillot has quit IRC23:20
*** thorst has joined #openstack-meeting23:22
*** ociuhandu has quit IRC23:24
*** Sukhdev_ has joined #openstack-meeting23:25
*** Sukhdev has quit IRC23:27
*** ociuhandu has joined #openstack-meeting23:28
*** pradk has quit IRC23:29
*** thorst has quit IRC23:30
*** Leom has joined #openstack-meeting23:31
*** mtanino has joined #openstack-meeting23:34
*** guoshan has joined #openstack-meeting23:34
*** galstrom_zzz is now known as galstrom23:38
*** askb has quit IRC23:38
*** guoshan has quit IRC23:39
*** salv-orlando has quit IRC23:40
*** thorst has joined #openstack-meeting23:41
*** skelso has joined #openstack-meeting23:41
*** thorst has quit IRC23:41
*** thorst has joined #openstack-meeting23:41
*** kaminohana has joined #openstack-meeting23:42
*** cebruns has quit IRC23:44
*** mlavalle has quit IRC23:44
*** baoli has quit IRC23:45
*** JRobinson__ has joined #openstack-meeting23:45
*** lamt has quit IRC23:45
*** lamt has joined #openstack-meeting23:46
*** thorst has quit IRC23:46
*** Leom has quit IRC23:46
*** lamt has quit IRC23:51
*** cebruns has joined #openstack-meeting23:51
*** thorst has joined #openstack-meeting23:52
*** thorst has quit IRC23:52
*** thorst has joined #openstack-meeting23:52
*** dimtruck is now known as zz_dimtruck23:52
*** cebruns has quit IRC23:59

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