Tuesday, 2016-11-29

*** ykatabam has joined #openstack-meeting00:00
*** ijw has joined #openstack-meeting00:01
*** ianychoi has joined #openstack-meeting00:02
*** bobh_ has joined #openstack-meeting00:03
*** yuanying_ has joined #openstack-meeting00:03
*** ijw has quit IRC00:03
*** ijw has joined #openstack-meeting00:04
*** penick has quit IRC00:04
*** jtomasek has quit IRC00:05
*** galstrom is now known as galstrom_zzz00:05
*** Patifa has quit IRC00:05
*** penick has joined #openstack-meeting00:09
*** fnaval has quit IRC00:10
*** yangyapeng has quit IRC00:12
*** bobmel has joined #openstack-meeting00:16
*** bobmel has quit IRC00:21
*** Swami has joined #openstack-meeting00:21
*** thorst_ has joined #openstack-meeting00:26
*** reedip_ has quit IRC00:27
*** mtanino has quit IRC00:27
*** thorst_ has quit IRC00:27
*** Apoorva has quit IRC00:28
*** rbak has quit IRC00:28
*** SridarK has quit IRC00:29
*** JRobinson__ is now known as JRobinson__afk00:29
*** kylek3h has joined #openstack-meeting00:31
*** gmann has joined #openstack-meeting00:36
*** Julien-zte has joined #openstack-meeting00:43
*** Julien-zte has quit IRC00:44
*** comay_ has quit IRC00:44
*** Julien-zte has joined #openstack-meeting00:45
*** Julien-zte has quit IRC00:45
*** Julien-zte has joined #openstack-meeting00:46
*** shashank_hegde has quit IRC00:46
*** Julien-zte has quit IRC00:51
*** JRobinson__afk is now known as JRobinson__00:52
*** gyee has joined #openstack-meeting00:54
*** gyee has quit IRC00:54
*** stevemar__ has quit IRC00:54
*** guoshan has joined #openstack-meeting00:56
*** Julien-zte has joined #openstack-meeting00:59
*** Apoorva has joined #openstack-meeting01:00
*** guoshan has quit IRC01:01
*** ankur-gupta-f1 has left #openstack-meeting01:03
*** ykatabam has quit IRC01:04
*** piet has quit IRC01:04
*** spzala has joined #openstack-meeting01:05
*** s3wong has quit IRC01:05
*** guoshan has joined #openstack-meeting01:07
*** beagles_biab is now known as beagles01:09
*** tovin07 has joined #openstack-meeting01:10
*** zhurong has joined #openstack-meeting01:11
*** JRobinson__ has quit IRC01:13
*** yangyapeng has joined #openstack-meeting01:15
*** mmotiani_ has joined #openstack-meeting01:17
*** Qiming_ is now known as Qiming01:17
*** donghao has joined #openstack-meeting01:18
*** ykatabam has joined #openstack-meeting01:19
*** shashank_hegde has joined #openstack-meeting01:21
*** jaypipes has quit IRC01:23
*** donghao has quit IRC01:27
*** mmotiani_ has quit IRC01:28
*** Swami has quit IRC01:31
*** gmann has quit IRC01:32
*** askb has quit IRC01:32
*** numans has joined #openstack-meeting01:34
*** thorst_ has joined #openstack-meeting01:35
*** mriedem has joined #openstack-meeting01:38
*** guoshan has quit IRC01:39
*** yamamot__ has joined #openstack-meeting01:41
*** thorst_ has quit IRC01:41
*** yamamot__ has quit IRC01:44
*** askb has joined #openstack-meeting01:44
*** kun_huang has joined #openstack-meeting01:45
*** haleyb_ has joined #openstack-meeting01:46
*** mlavalle has quit IRC01:48
*** elynn has joined #openstack-meeting01:50
*** askb has quit IRC01:52
*** elynn has quit IRC01:55
*** elynn has joined #openstack-meeting01:55
*** shashank_hegde has quit IRC01:56
*** shashank_hegde has joined #openstack-meeting01:57
*** numans has quit IRC02:01
*** bobh_ has quit IRC02:01
*** rfolco_ has joined #openstack-meeting02:03
*** rfolco_ has quit IRC02:03
*** yamamot__ has joined #openstack-meeting02:04
*** paw has quit IRC02:08
*** kaisers_ has joined #openstack-meeting02:08
*** kaisers has quit IRC02:11
*** baoli has joined #openstack-meeting02:11
*** dmacpher has joined #openstack-meeting02:13
*** fnaval has joined #openstack-meeting02:14
*** Apoorva has quit IRC02:16
*** lhx_ has joined #openstack-meeting02:17
*** bobmel has joined #openstack-meeting02:17
*** epico has joined #openstack-meeting02:18
*** shashank_hegde has quit IRC02:20
*** bobmel has quit IRC02:21
*** kun_huang has left #openstack-meeting02:22
*** hongbin has joined #openstack-meeting02:22
*** rajinir has quit IRC02:26
*** reedip has quit IRC02:29
*** reedip has joined #openstack-meeting02:32
*** galstrom_zzz is now known as galstrom02:34
*** numans has joined #openstack-meeting02:35
*** thorst_ has joined #openstack-meeting02:39
*** thorst_ has quit IRC02:40
*** thorst_ has joined #openstack-meeting02:40
*** thorst_ has quit IRC02:41
*** penick has quit IRC02:42
*** paw has joined #openstack-meeting02:45
*** Julien-zte has quit IRC02:45
*** jschwarz has quit IRC02:45
*** zhonghua has quit IRC02:49
*** jschwarz has joined #openstack-meeting02:49
*** enriquetaso has quit IRC02:52
*** Julien-zte has joined #openstack-meeting02:52
*** ijw has quit IRC02:53
*** ijw has joined #openstack-meeting02:53
*** ijw has quit IRC02:53
*** gjayavelu has joined #openstack-meeting02:53
*** lakerzhou has joined #openstack-meeting02:54
*** stevemar__ has joined #openstack-meeting02:55
*** cloud_player has joined #openstack-meeting02:56
*** Namrata has joined #openstack-meeting02:56
*** gjayavelu has quit IRC02:58
*** kevinz has joined #openstack-meeting02:58
*** kevinz has quit IRC02:59
*** kevinz has joined #openstack-meeting02:59
hongbin#startmeeting zun03:00
openstackMeeting started Tue Nov 29 03:00:04 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
*** shubhams has joined #openstack-meeting03:00
hongbin#link https://wiki.openstack.org/wiki/Zun#Agenda_for_2016-11-29_0300_UTC Today's agenda03:00
*** stevemar__ has quit IRC03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
*** yuanying_ has quit IRC03:00
*** spzala has quit IRC03:01
*** sudipto has joined #openstack-meeting03:01
*** sudipto_ has joined #openstack-meeting03:01
*** spzala has joined #openstack-meeting03:01
hongbinThanks for joining hte meeting Namrata kevinz eliqiao shubhams lakerzhou03:02
hongbini knew madhuri cannot come today03:02
hongbinthen, let's start03:02
hongbin#topic Announcements03:02
*** openstack changes topic to "Announcements (Meeting topic: zun)"03:02
hongbinsudipto: hey03:02
hongbin1. Zun is applying to become an official OpenStack project03:02
hongbin#link https://review.openstack.org/#/c/402227/03:02
*** zhangjl has joined #openstack-meeting03:03
hongbini saw most of you have casted a +1 there, which is great :)03:03
hongbinright now, 5 tc has voted for yes03:03
hongbinit looks everything is good so far03:03
hongbinlet's see how this application will go03:03
shubhamshongbin: How many TC votes we need ?03:03
hongbinshubhams: not exactly sure03:04
*** Julien-zte has quit IRC03:04
shubhamshongbin: ok03:04
hongbinshubhams: we need approval from the tc chair03:04
eliqiao5 are over 1/2, right?03:04
hongbinshubhams: the tc chair will approve if there is a consensus among most of hte tc03:04
clarkbeliqiao: no I think tc is 13 total03:04
hongbineliqiao: i remembered there were 13 tc03:05
*** Julien-zte has joined #openstack-meeting03:05
clarkbwe elect 6 and then 7 for 13 total03:05
eliqiaoclarkb: oh, good to know ,thx.03:05
eliqiaohongbin: thx :)03:05
hongbinanything else for the big-tent application ?03:05
hongbinok, move on03:06
hongbin#topic Review Action Items03:06
*** lakerzhou has quit IRC03:06
*** openstack changes topic to "Review Action Items (Meeting topic: zun)"03:06
hongbin#topic Container network (hongbin)03:06
*** openstack changes topic to "Container network (hongbin) (Meeting topic: zun)"03:06
hongbin#link https://blueprints.launchpad.net/zun/+spec/neutron-integration The BP03:06
hongbin#link https://review.openstack.org/#/c/365754/ The proposed spec (merged)03:06
hongbin#link https://review.openstack.org/#/c/396896/ The patch Part 103:06
hongbin#link https://review.openstack.org/#/c/399248/ The patch Part 203:06
*** haleyb__ has joined #openstack-meeting03:06
hongbinright now, all the patches were merged. thanks all for reviews03:06
hongbini will remove this from the meeting agenda next week03:07
hongbinbefore i move forward, any question for the sandbox feature?03:07
hongbin#topic Kubernetes integration (shubhams)03:07
*** openstack changes topic to "Kubernetes integration (shubhams) (Meeting topic: zun)"03:07
hongbin#link https://blueprints.launchpad.net/zun/+spec/k8s-integration03:08
hongbinshubhams: ^^03:08
shubhamsWe created etherpad and put down oour idea there03:08
shubhams#link https://etherpad.openstack.org/p/zun-k8s-integration03:08
*** thorst_ has joined #openstack-meeting03:08
*** spzala has quit IRC03:08
shubhamsThe basic flow is : first we are trying to see if python-k8sclient can be used03:09
shubhamsand in parallel, we will finalize the APIs that we are going to introduce03:09
sudipto_so the k8s integration is about a different set of APIs in zun?03:09
*** haleyb_ has quit IRC03:09
shubhamssudipto_:  yes03:09
hongbinlet's discuss this03:10
*** unicell has quit IRC03:10
shubhamshongbin:  ok03:10
hongbinright now, this is what zun currently support: container, sandbox03:10
*** links has joined #openstack-meeting03:10
*** Julien-zte has quit IRC03:10
*** links has quit IRC03:10
hongbinthis is what k8s currently support: pod, service, replication controller03:10
*** Julien-zte has joined #openstack-meeting03:11
hongbini think the first step is to find a reasonable overlay of the apis between zun and k8s03:11
hongbinhowever, feel free to share your ideas if any03:11
kevinzzun-api will directly talk with k8s-apiserver directly?03:12
sudipto_Also, in this case, what are the additional features that zun would provide or will it just be a passthrough to K8s?03:12
*** huanxuan has joined #openstack-meeting03:12
hongbinkevinz: i think so03:12
hongbinsudipto_: let's cast the inputs to the etherpad03:13
eliqiaocan you tell what's your idear about zun api looks like for k8s intergration?03:13
shubhamskevinz, hongbin : we plan to use python-k8sclient for communication between zun and k8s03:13
hongbinshubhams: i am ok with that03:13
*** Leom has joined #openstack-meeting03:13
hongbinshubhams: python-k8sclient will talk to kube-apiserver03:13
eliqiaothat's will bring another old magnum api problem.03:13
shubhamsIMO, zun should not necessarily provide 1-to-1 mapping with k8s03:13
shubhamswe can have minimum set of commands for now : ex: service, pods at the minimum03:14
eliqiaoI think zun's mission is to unify container API right? (low level could be k8s docker, etc.)03:14
eliqiaoshubhams: but if your low level driver is docker, the operation will be consufsed by serice pods ...03:15
shubhamseliqiao: right, so post k8s we can provide same features for other COEs as well , right?03:15
*** Leom has quit IRC03:15
*** gcb has joined #openstack-meeting03:15
shubhamszun can provide cluster  management apis in unified manner along with container management apis03:16
*** thorst_ has quit IRC03:16
shubhamsWhat are your views on this ?03:17
eliqiaoshubhams: I don't get 'zun can provide cluster management apis'03:17
*** artom has quit IRC03:17
eliqiaoI think Magnum will provide that mission03:17
kevinzzun will do just like "kubectl" do?03:17
*** bobmel has joined #openstack-meeting03:18
eliqiaoIf you konw the history of Magnum, Magnum support k8s/docker at sametime.03:18
shubhamseliqiao: I am thinking in the way service and pod are managed03:18
eliqiaoit has pod/service/rc endpoint and also container endpints03:18
shubhamskevinz: roughly speaking "yes"03:18
eliqiaoso user who using k8s will be confused by 'container'03:18
kevinzshubhams: :D ok03:19
eliqiaozun aimed to provide unified APIs for all COEs.03:19
Qimingunified api for COE is different from unified API for containers ...03:19
*** vishnoianil has quit IRC03:20
shubhamseliqiao: Yes. That's why we do not aim for 1-to-1 mapping with k8s03:20
hongbinQiming: hey, good to see you here03:20
Qimingwatching, thinking03:20
hongbinok, let's discuss one point03:20
hongbinzun do not aim for 1-to-1 mapping with k8s03:20
hongbini agree with this point03:20
hongbinwhat do you think?03:21
eliqiaoQiming: can you detail the differences?03:21
Qimingwhen we are talking about a unified API for COEs, we are aiming at a reference implementation of OCI03:21
hongbinQiming: You mean CNCF?03:22
Qimingwhen we are talking about unified API for containers, we are abstracting away the difference between lxc, docker (minus swarm), rkt, etc.03:22
*** r-mibu has quit IRC03:22
*** yamamo___ has joined #openstack-meeting03:22
*** r-mibu has joined #openstack-meeting03:22
eliqiaoQiming: yes, get it. diferent level.03:22
Qimingwe need a compelling reason for users to adopt zun03:22
*** bobmel has quit IRC03:23
Qimingif I'm a fan of k8s, I really need a reason to switch to zun03:23
*** sharatss has quit IRC03:23
Qimingbtw, I'm not a fan of k8s yet, :D03:24
*** sharatss has joined #openstack-meeting03:24
Qimingthe advantage of zun, as I see it, is it is based on OpenStack, as stated in the big-tent application03:24
Qimingif we can maximize that value, we win03:25
shubhamsWith the ongoing discussion , I get a feel that if we tend to integrate anything using (driver model eg: docker driver , k8s driver etc) then we might not be able to  acheive this goal of uniformity03:25
shubhamsAs we will bounded by the limitation of features provided by respective COEs and runtimes03:25
*** Julien-zte has quit IRC03:25
Qimingif we get ourselves trapped into a k8s compatibility, I'm afraid we are going nowhere03:26
shubhamsQiming: agree03:26
*** yamamot__ has quit IRC03:26
hongbinQiming: +103:26
Qimingthink from users perspective03:26
*** julim has quit IRC03:26
Qimingwhat do they need, what do they value most03:26
*** Julien-zte has joined #openstack-meeting03:26
hongbini think users just want a simple API that is capable to host their applications03:26
QimingI share the same thought with you, hongbin03:27
hongbinthen, the zun API should start with simple and basic functionality03:27
*** r-mibu has quit IRC03:27
sudipto_Are we considering composition of services to be supported via ZUN - with the same set of docker APIs?03:27
hongbinthen, extend to an advanced set of features as we go03:28
sudipto_docker-compose kinda functionality.03:28
*** r-mibu has joined #openstack-meeting03:28
Qimingsounds like something we can leverage heat?03:28
*** aeng has quit IRC03:28
sudipto_I mean getting a container in openstack without real composition supported - i am not sure how useful is that.03:29
*** Julien-zte has quit IRC03:29
sudipto_because we are talking about micro services and that would involve deploying a set of containers, not just one.03:29
sudipto_The reason i brought in the conjecture is because, maybe that would help us define what we want to achieve with K8s...with zun...03:30
*** Julien-zte has joined #openstack-meeting03:30
hongbinhere is what i think: forget about service and replication controller for now03:30
hongbinimplement pod or container or both in zun at the first step03:31
hongbinif we have pod, container is easy (a pod with one container)03:31
*** Julien-zte has quit IRC03:31
*** vishnoianil has joined #openstack-meeting03:31
eliqiaohongbin: hehe ...03:31
sudipto_hongbin, agreed.03:31
hongbinfor docker, we have the sandbox concept now, which makes us easier to implement pod in docker driver03:31
*** Julien-zte has joined #openstack-meeting03:32
*** artom has joined #openstack-meeting03:32
eliqiaohongbin: that's tricky03:32
Qimingmake those things rock solid when we are looking forward to more advanced features and/or use cases03:32
sudipto_My point is - make zun self sufficient first and then move on supporting other COEs if at all.03:32
sudipto_Qiming, +103:32
shubhamshongbin: yep right.. same priorities we have in our etherpad :)03:32
shubhamsQiming: +103:33
hongbinok, all. i proposed all of us to vote on each option in the etherpad03:33
hongbin#link https://etherpad.openstack.org/p/zun-k8s-integration03:33
hongbinthe etherpad should list all the options we have discussed so far03:33
*** trinaths has joined #openstack-meeting03:34
*** artom_ has joined #openstack-meeting03:36
*** artom has quit IRC03:37
*** spzala has joined #openstack-meeting03:37
*** alexpilotti has quit IRC03:40
*** alexpilotti has joined #openstack-meeting03:42
*** julim has joined #openstack-meeting03:42
hongbinok, all03:43
hongbinlet's work on the etherpad as a homework03:43
shubhamshongbin: ok03:43
hongbinis everyone still on the etherpad? or back to here?03:43
hongbinok, move on03:44
hongbin#topic Support interactive mode (kevinz)03:44
*** openstack changes topic to "Support interactive mode (kevinz) (Meeting topic: zun)"03:44
hongbinkevinz: ^^03:44
hongbin#link https://blueprints.launchpad.net/zun/+spec/support-interactive-mode The BP03:45
kevinzHere is the design spec I've updated03:45
hongbin#link https://review.openstack.org/#/c/396841/ The design spec03:45
hongbinkevinz: maybe you could briefly explain what is the updated idea?03:45
hongbinkevinz: because not everyone here has reviewed the updated spec03:46
kevinzOK plan to refer to Kubenetes, zun-cli will first connect to zun-api zun-compute to create container03:47
kevinzdocker daemon will open a tcp port03:48
*** baoli has quit IRC03:48
kevinzzun cli will connect to the zun-api then proxy to the tcp port03:48
kevinzconnect local stdin stderr stdout to this container to realize the interactive03:49
kevinzJust like kubernetes does03:49
*** liuyulong__ is now known as liuyulong03:49
hongbinkevinz: the flow will be: zunclient -> zun-api -> zun-compute -> docker daemon ?03:50
kevinzYeah I think your advice is valuable, change to  zunclient -> zun-api ->docker daemon03:50
hongbini should say: zunclient <-> zun-api <-> zun-compute <-> docker daemon (since the streaming is bidirectional)03:50
hongbinthen zunclient <-> zun-api <-> docker daemon03:51
hongbini like that, because bypassing zun-compute will reduce some overhead03:51
hongbinkevinz: then, the spec looks good to me03:52
kevinzYeah, as first step could we just : zunclient <-> websocket <-> docker-daemon03:52
*** diablo_rojo has joined #openstack-meeting03:52
kevinzzunclient ask zun-api for the websocket link, then connect to port directly without token first step?03:53
hongbinkevinz: i suggest forgetting the token for now03:53
*** ljxiash has joined #openstack-meeting03:53
*** ljxiash has quit IRC03:54
hongbinkevinz: you don't have to implement the authentication at the first iteration03:54
*** ljxiash has joined #openstack-meeting03:54
hongbinkevinz: i think that will be easier for you03:54
kevinzhongbin: OK , that means  ask zun-api for the websocket link, then connect to port directly is fine ?03:54
hongbinkevinz: yes03:54
kevinzhongbin: COOL I will update the spec03:54
hongbinkevinz: after that, you can consider using token / TLS to secure the connection03:55
*** julim has quit IRC03:55
kevinzhongbin: Thanks03:55
hongbinsounds good03:55
hongbinkevinz: thanks for proposing the spec03:55
*** stevemar__ has joined #openstack-meeting03:55
kevinzhongbin: My pleasure03:55
hongbin#topic Open Discussion03:56
*** openstack changes topic to "Open Discussion (Meeting topic: zun)"03:56
hongbinok, if there is nothing else, let's end the meeting a few minutes earlier03:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"03:57
openstackMeeting ended Tue Nov 29 03:57:19 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-11-29-03.00.html03:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-11-29-03.00.txt03:57
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-11-29-03.00.log.html03:57
*** shubhams has quit IRC03:57
*** yuanying has joined #openstack-meeting03:59
*** kevinz has quit IRC04:02
*** Namrata has quit IRC04:05
*** trinaths has quit IRC04:06
*** galstrom is now known as galstrom_zzz04:07
*** ljxiash has quit IRC04:10
*** ljxiash has joined #openstack-meeting04:11
*** stevemar__ has quit IRC04:11
*** thorst_ has joined #openstack-meeting04:14
*** zhurong has quit IRC04:15
*** csomerville has quit IRC04:15
*** csomerville has joined #openstack-meeting04:15
*** ljxiash has quit IRC04:15
*** zhurong has joined #openstack-meeting04:15
*** armax has quit IRC04:16
*** gmann has joined #openstack-meeting04:21
*** jgriffith is now known as jgriffith_away04:21
*** thorst_ has quit IRC04:22
*** hongbin has quit IRC04:24
*** elynn has quit IRC04:32
*** dmorita has quit IRC04:34
*** yamahata has quit IRC04:38
*** masayukig has quit IRC04:40
*** reedip has quit IRC04:42
*** hichihara has joined #openstack-meeting04:42
*** iyamahat has quit IRC04:43
*** masayukig has joined #openstack-meeting04:43
*** numans has quit IRC04:48
*** baoli has joined #openstack-meeting04:49
*** sharatss has quit IRC04:50
*** elynn has joined #openstack-meeting04:57
*** sudipto has quit IRC04:59
*** sudipto_ has quit IRC04:59
*** elynn_ has joined #openstack-meeting05:01
*** ljxiash has joined #openstack-meeting05:01
*** baoli has quit IRC05:01
*** elynn has quit IRC05:02
*** jrist has quit IRC05:03
*** numans has joined #openstack-meeting05:04
*** shashank_hegde has joined #openstack-meeting05:05
*** prateek has joined #openstack-meeting05:05
*** csomerville has quit IRC05:12
*** shashank_hegde has quit IRC05:12
*** gouthamr has joined #openstack-meeting05:12
*** haleyb__ has quit IRC05:12
*** csomerville has joined #openstack-meeting05:14
*** spzala has quit IRC05:15
*** bobmel has joined #openstack-meeting05:19
*** dimtruck is now known as zz_dimtruck05:19
*** thorst_ has joined #openstack-meeting05:20
*** lhx_ has quit IRC05:20
*** bobmel has quit IRC05:23
*** thorst_ has quit IRC05:26
*** donghao has joined #openstack-meeting05:29
*** sudipto has joined #openstack-meeting05:29
*** sudipto_ has joined #openstack-meeting05:29
*** donghao has quit IRC05:33
*** shashank_hegde has joined #openstack-meeting05:35
*** zhangjl has quit IRC05:35
*** gouthamr has quit IRC05:37
*** csomerville has quit IRC05:37
*** aeng has joined #openstack-meeting05:41
*** lhx__ has joined #openstack-meeting05:42
*** gouthamr has joined #openstack-meeting05:46
*** gouthamr has quit IRC05:56
*** Julien-zte has quit IRC05:56
*** Julien-zte has joined #openstack-meeting05:57
*** Julien-zte has quit IRC05:57
*** Julien-zte has joined #openstack-meeting05:58
*** Julien-zte has quit IRC06:01
*** Julien-zte has joined #openstack-meeting06:02
*** huangyunpeng has quit IRC06:04
*** gcb has quit IRC06:08
*** gcb has joined #openstack-meeting06:09
*** haleyb__ has joined #openstack-meeting06:09
*** hichihara has quit IRC06:10
*** yangyapeng has quit IRC06:13
*** yangyapeng has joined #openstack-meeting06:13
*** haleyb__ has quit IRC06:14
*** trinaths has joined #openstack-meeting06:14
*** cloud_player has quit IRC06:15
*** shashank_hegde has quit IRC06:16
*** gcb has quit IRC06:21
*** irenab has joined #openstack-meeting06:24
*** thorst_ has joined #openstack-meeting06:25
*** shashank_hegde has joined #openstack-meeting06:27
*** lpetrut has joined #openstack-meeting06:31
*** anilvenkata has joined #openstack-meeting06:31
*** thorst_ has quit IRC06:32
*** dmorita has joined #openstack-meeting06:34
*** ricolin has joined #openstack-meeting06:35
*** ricolin has quit IRC06:37
*** ricolin has joined #openstack-meeting06:37
*** ricolin has quit IRC06:38
*** ricolin has joined #openstack-meeting06:38
*** dmorita has quit IRC06:39
*** kaminohana has quit IRC06:40
*** gcb has joined #openstack-meeting06:41
*** nadya has joined #openstack-meeting06:41
*** dmacpher has quit IRC06:43
*** Apoorva has joined #openstack-meeting06:43
*** unicell has joined #openstack-meeting06:44
*** Apoorva has quit IRC06:46
*** diablo_rojo has quit IRC06:47
*** aeng has quit IRC06:48
*** ricolin has quit IRC06:48
*** Julien-zte has quit IRC06:48
*** ricolin has joined #openstack-meeting06:49
*** Julien-zte has joined #openstack-meeting06:49
*** Julien-zte has quit IRC06:50
*** Julien-zte has joined #openstack-meeting06:50
*** unicell has quit IRC06:51
*** unicell has joined #openstack-meeting06:52
*** unicell1 has joined #openstack-meeting06:54
*** ijw has joined #openstack-meeting06:56
*** unicell has quit IRC06:56
*** baoli has joined #openstack-meeting06:58
*** ykatabam has quit IRC07:01
*** yamamo___ has quit IRC07:02
*** baoli has quit IRC07:02
*** artom_ has quit IRC07:02
*** Julien-zte has quit IRC07:05
*** Julien-zte has joined #openstack-meeting07:06
*** haleyb__ has joined #openstack-meeting07:10
*** kenji-i_ has quit IRC07:12
*** haleyb__ has quit IRC07:15
*** spzala has joined #openstack-meeting07:16
*** nadya has quit IRC07:17
*** X-dark_ has joined #openstack-meeting07:18
*** nkrinner_afk is now known as nkrinner07:19
*** bobmel has joined #openstack-meeting07:20
*** spzala has quit IRC07:20
*** X-dark has quit IRC07:20
*** X-dark_ is now known as X-dark07:20
*** yuanying has quit IRC07:20
*** llu has quit IRC07:21
*** pcaruana has joined #openstack-meeting07:21
*** sridharg has joined #openstack-meeting07:22
*** anilvenkata is now known as anilvenkata_afk07:22
*** bobmel has quit IRC07:25
*** rasca has joined #openstack-meeting07:26
*** rbartal has joined #openstack-meeting07:26
*** yuanying has joined #openstack-meeting07:26
*** lpetrut has quit IRC07:28
*** makowals has joined #openstack-meeting07:28
*** thorst_ has joined #openstack-meeting07:28
*** iyamahat has joined #openstack-meeting07:29
*** thorst_ has quit IRC07:36
*** korzen has joined #openstack-meeting07:36
*** nadya has joined #openstack-meeting07:37
*** ricolin has quit IRC07:39
*** yamamot__ has joined #openstack-meeting07:39
*** zhurong has quit IRC07:40
*** zhurong has joined #openstack-meeting07:41
*** yamahata has joined #openstack-meeting07:46
*** ykatabam has joined #openstack-meeting07:49
*** andreas_s has joined #openstack-meeting07:51
*** edtubill has joined #openstack-meeting07:58
*** baoli has joined #openstack-meeting07:59
*** Julien-zte has quit IRC08:01
*** Julien-zte has joined #openstack-meeting08:02
*** e0ne has joined #openstack-meeting08:02
*** edtubill has quit IRC08:03
*** gouthamr has joined #openstack-meeting08:03
*** iyamahat has quit IRC08:03
*** baoli has quit IRC08:04
*** kota_ has joined #openstack-meeting08:04
kota_sorry being late08:04
kota_no one?08:05
kota_it looks like eranrom is in the user list.08:05
eranrom#startmeeting storlets08:06
openstackMeeting started Tue Nov 29 08:06:04 2016 UTC and is due to finish in 60 minutes.  The chair is eranrom. Information about MeetBot at http://wiki.debian.org/MeetBot.08:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:06
*** openstack changes topic to " (Meeting topic: storlets)"08:06
openstackThe meeting name has been set to 'storlets'08:06
eranromHi, sorry I am late08:06
kota_hi eranrom :)08:06
eranromTakashi will not be able to join.08:06
eranromSo lets start.08:06
eranrom#topic PTG08:06
*** openstack changes topic to "PTG (Meeting topic: storlets)"08:06
kota_k, takashi looks absent.08:06
eranromThe news from last week are that should we get a room (depending on being official) it will be for all day long Wed-Fri.08:07
*** iyamahat has joined #openstack-meeting08:07
*** matrohon has joined #openstack-meeting08:08
kota_eranrom: !?08:08
*** lezbar has joined #openstack-meeting08:08
eranromTakashi asked if we will get a room will it be for all day long or just periods.08:08
eranromI think his line of thought was: If we have it for all day, perhaps it gives us enough flexibility to meet during Wed-Fri instead of unofficially on Mon-Tue08:09
kota_eranrom: ah, ok. he inclines to keep our room FWIW if we have topics for all.08:10
*** haleyb__ has joined #openstack-meeting08:11
kota_make sense08:11
eranromI guess the question is: Do you think you will not be all caught up with Swift during Wed-Fri?08:12
*** akamyshnikova has quit IRC08:13
*** frasantoro has joined #openstack-meeting08:13
kota_ah does he ask to us?08:13
kota_for the answer, i'm not sure if i can manage the time so flexible.08:14
*** Julien-zte has quit IRC08:14
eranromok, I see. Since Takashi is not here lets continue to discuss next week.08:15
*** Julien-zte has joined #openstack-meeting08:15
*** elynn_ has left #openstack-meeting08:15
*** ayogi has joined #openstack-meeting08:15
kota_thinkin back to the past hackathon, we had a lot of in-flight conversation which is not addressed in official in the whole week so...08:15
*** haleyb__ has quit IRC08:15
kota_eranrom: sure, thanks08:16
eranromkota_: ok.08:16
eranrom#topic: packaging patch08:16
*** openstack changes topic to ": packaging patch (Meeting topic: storlets)"08:16
*** oshidoshi has joined #openstack-meeting08:16
eranromSo the devstack patch was merged, and Takashi is rebasing the packaging patch.08:17
eranromonce rebased, are you ok with merging it?08:17
*** Julien-zte has quit IRC08:17
*** ralonsoh has joined #openstack-meeting08:17
*** lezbar has quit IRC08:17
*** yuanying has quit IRC08:17
kota_eranrom: has takashi addressed the docs for installation already?08:17
*** Julien-zte has joined #openstack-meeting08:17
kota_eranrom: not yet noticed the recent activity for packaging patch.08:18
eranromkota_: ah, good point.08:18
eranromIf the new patch will not have it we can -108:18
*** iyamahat has quit IRC08:19
*** mickeys has quit IRC08:19
*** donghao has joined #openstack-meeting08:19
*** lezbar has joined #openstack-meeting08:19
eranromOnce this is done, I will have few patches before I feel comfortable to get back to the TC.08:20
*** mickeys has joined #openstack-meeting08:20
eranromthat is with getting official.08:20
eranromanything else for today?08:21
kota_not so big one from me08:22
kota_just notify small things08:23
kota_from my company's order, I will be about to improve/testing around multi-in and perhaps multi-out for storlets08:24
*** mickeys has quit IRC08:24
kota_probably the first thing is confirmation for python x multi-in08:24
*** donghao has quit IRC08:25
*** e0ne has quit IRC08:25
kota_and we may need to consider multi-out and something around timeout/open connction (to Swift) timing for long exectution task in storlets08:25
kota_anyway, in my idea, that happens in the new packaging dir structure08:25
kota_that should08:26
kota_so I'm willing to look the patch from takashi again soonly ;-)08:26
eranromkota_: ok. We have discussed the long execution time before. I would LOVE to have this.08:26
eranromkota_: Great! thanks!08:27
eranromplease letme know if I can assist in any way (other than of corse to review)08:27
kota_eranrom: thanks!08:28
*** nkrinner has quit IRC08:28
eranromkota_: anything else for today?08:30
kota_that's all from me today08:30
eranromok, so thanks for joining.08:32
eranromtalk to you later08:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:32
openstackMeeting ended Tue Nov 29 08:32:47 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storlets/2016/storlets.2016-11-29-08.06.html08:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storlets/2016/storlets.2016-11-29-08.06.txt08:32
openstackLog:            http://eavesdrop.openstack.org/meetings/storlets/2016/storlets.2016-11-29-08.06.log.html08:32
*** kota_ has left #openstack-meeting08:33
*** thorst_ has joined #openstack-meeting08:34
*** nkrinner has joined #openstack-meeting08:34
*** alexpilo_ has joined #openstack-meeting08:35
*** woodster_ has quit IRC08:36
*** alexpilotti has quit IRC08:36
*** irenab has quit IRC08:37
*** ijw has quit IRC08:38
*** nkrinner has quit IRC08:38
*** irenab has joined #openstack-meeting08:39
*** alexpilotti has joined #openstack-meeting08:40
*** thorst_ has quit IRC08:41
*** alexpilo_ has quit IRC08:41
*** nadya has quit IRC08:42
*** zhhuabj has quit IRC08:44
*** anilvenkata_afk is now known as anilvenkata08:44
*** phil has joined #openstack-meeting08:46
*** phil is now known as Guest5319508:46
*** alexpilo_ has joined #openstack-meeting08:50
*** shashank_hegde has quit IRC08:50
*** alexpilotti has quit IRC08:51
*** alexpilotti has joined #openstack-meeting08:55
*** alexpilo_ has quit IRC08:55
*** rcernin has joined #openstack-meeting08:56
*** zhhuabj has joined #openstack-meeting08:56
*** aeng has joined #openstack-meeting08:57
*** rossella_s has joined #openstack-meeting08:58
*** shashank_hegde has joined #openstack-meeting08:59
*** shashank_hegde has quit IRC08:59
*** alexpilotti has quit IRC08:59
*** baoli has joined #openstack-meeting09:00
*** kevinz has joined #openstack-meeting09:02
*** toscalix has joined #openstack-meeting09:02
*** ricolin has joined #openstack-meeting09:03
*** baoli has quit IRC09:05
*** alexpilotti has joined #openstack-meeting09:06
*** spzala has joined #openstack-meeting09:10
*** stevemar__ has joined #openstack-meeting09:12
*** haleyb__ has joined #openstack-meeting09:12
*** spzala has quit IRC09:15
*** alexpilotti has quit IRC09:15
*** alexpilotti has joined #openstack-meeting09:16
*** stevemar__ has quit IRC09:16
*** ljxiash has quit IRC09:17
*** haleyb__ has quit IRC09:17
*** yamahata has quit IRC09:18
*** lpetrut has joined #openstack-meeting09:19
*** nadya has joined #openstack-meeting09:19
*** mickeys has joined #openstack-meeting09:20
*** e0ne has joined #openstack-meeting09:24
*** lpetrut has quit IRC09:24
*** mickeys has quit IRC09:25
*** arxcruz has quit IRC09:25
*** Cibo_ has joined #openstack-meeting09:27
*** rossella_s has quit IRC09:31
*** lpetrut has joined #openstack-meeting09:31
*** rossella_s has joined #openstack-meeting09:31
*** tochi has joined #openstack-meeting09:32
*** onovy has quit IRC09:32
*** lin_yang has quit IRC09:33
*** peterlisak has quit IRC09:33
*** mpaolino has joined #openstack-meeting09:35
*** yuval has joined #openstack-meeting09:36
*** tochi has quit IRC09:37
*** mkoderer has joined #openstack-meeting09:37
*** onovy has joined #openstack-meeting09:38
*** peterlisak has joined #openstack-meeting09:38
*** e0ne has quit IRC09:39
*** thorst_ has joined #openstack-meeting09:39
*** sshnaidm is now known as sshnaidm|afk09:39
*** e0ne has joined #openstack-meeting09:40
*** sshnaidm|afk has quit IRC09:40
*** Cibo_ has quit IRC09:40
*** arxcruz has joined #openstack-meeting09:41
*** lpetrut has quit IRC09:41
*** lpetrut has joined #openstack-meeting09:43
*** pnavarro has joined #openstack-meeting09:44
*** lezbar has quit IRC09:44
*** thorst_ has quit IRC09:47
*** lpetrut has quit IRC09:47
*** makowals_ has joined #openstack-meeting09:48
*** lpetrut has joined #openstack-meeting09:49
*** makowals has quit IRC09:51
*** e0ne has quit IRC09:51
*** e0ne has joined #openstack-meeting09:52
*** electrofelix has joined #openstack-meeting09:55
*** fzdarsky|afk has joined #openstack-meeting09:58
*** jschwarz has quit IRC09:59
*** baoli has joined #openstack-meeting10:01
*** zhurong has quit IRC10:05
*** aloga_ has joined #openstack-meeting10:05
*** baoli has quit IRC10:06
*** adiantum has joined #openstack-meeting10:07
*** jschwarz has joined #openstack-meeting10:10
*** reedip has joined #openstack-meeting10:11
*** haleyb__ has joined #openstack-meeting10:13
*** fzdarsky|afk is now known as fzdarsky10:13
*** erlon-airlong has joined #openstack-meeting10:15
*** Julien-zte has quit IRC10:16
*** haleyb__ has quit IRC10:18
*** arxcruz has quit IRC10:19
*** sambetts|afk is now known as sambetts10:19
*** arxcruz has joined #openstack-meeting10:19
*** mickeys has joined #openstack-meeting10:21
*** bobmel has joined #openstack-meeting10:22
*** nadya has quit IRC10:25
*** bobmel has quit IRC10:26
*** mickeys has quit IRC10:27
*** tovin07 has quit IRC10:29
*** apetrich has quit IRC10:29
*** tpsilva has joined #openstack-meeting10:34
*** anilvenkata is now known as anilvenkata_afk10:34
*** egallen has joined #openstack-meeting10:37
*** egallen has quit IRC10:38
*** donghao has joined #openstack-meeting10:38
*** egallen has joined #openstack-meeting10:39
*** e0ne has quit IRC10:40
*** e0ne_ has joined #openstack-meeting10:40
*** xiaofandh12 has joined #openstack-meeting10:43
*** xiaofandh12 has quit IRC10:44
*** epico has quit IRC10:45
*** thorst_ has joined #openstack-meeting10:45
*** donghao has quit IRC10:47
*** acoles_ is now known as acoles10:50
*** nadya has joined #openstack-meeting10:51
*** sshnaidm has joined #openstack-meeting10:51
*** yangyapeng has quit IRC10:51
*** thorst_ has quit IRC10:51
*** yangyapeng has joined #openstack-meeting10:52
*** fnaval_ has joined #openstack-meeting10:52
*** bobmel has joined #openstack-meeting10:54
*** fnaval has quit IRC10:54
*** yangyapeng has quit IRC10:56
*** rfolco has joined #openstack-meeting10:57
*** gouthamr has quit IRC10:58
*** baoli has joined #openstack-meeting11:02
*** sudipto_ has quit IRC11:03
*** sudipto has quit IRC11:03
*** baoli has quit IRC11:07
*** haleyb__ has joined #openstack-meeting11:14
*** martines_ has quit IRC11:16
*** haleyb__ has quit IRC11:19
*** huanxuan has quit IRC11:19
*** mickeys has joined #openstack-meeting11:23
*** anilvenkata_afk is now known as anilvenkata11:25
*** jtomasek has joined #openstack-meeting11:26
*** mickeys has quit IRC11:27
*** martines_ has joined #openstack-meeting11:28
*** ricolin has quit IRC11:29
*** ntpttr has quit IRC11:30
*** ntpttr has joined #openstack-meeting11:31
*** ociuhandu has joined #openstack-meeting11:31
*** sshnaidm has quit IRC11:34
*** sshnaidm has joined #openstack-meeting11:35
*** lpetrut1 has joined #openstack-meeting11:39
*** lpetrut has quit IRC11:41
*** lpetrut1 is now known as lpetrut11:41
*** donghao has joined #openstack-meeting11:45
*** yamamot__ has quit IRC11:46
*** thorst_ has joined #openstack-meeting11:49
*** donghao has quit IRC11:50
*** andymaier has joined #openstack-meeting11:55
*** thorst_ has quit IRC11:57
*** andymaier has quit IRC11:57
*** huanxuan has joined #openstack-meeting12:01
*** rasca has quit IRC12:02
*** baoli has joined #openstack-meeting12:03
*** baoli has quit IRC12:07
*** sridharg has quit IRC12:09
*** rtheis has joined #openstack-meeting12:10
*** yangyapeng has joined #openstack-meeting12:12
*** haleyb__ has joined #openstack-meeting12:15
*** huanxuan has quit IRC12:17
*** haleyb__ has quit IRC12:20
*** guoshan has joined #openstack-meeting12:28
*** guoshan has quit IRC12:29
*** guoshan has joined #openstack-meeting12:29
*** sridharg has joined #openstack-meeting12:33
*** guoshan has quit IRC12:34
*** xionchen_ has joined #openstack-meeting12:41
*** fnaval has joined #openstack-meeting12:42
*** gouthamr has joined #openstack-meeting12:42
*** stevemar__ has joined #openstack-meeting12:44
*** fnaval_ has quit IRC12:45
*** dbecker has joined #openstack-meeting12:49
*** thorst_ has joined #openstack-meeting12:49
*** prateek has quit IRC12:54
*** dprince has joined #openstack-meeting12:54
*** yanyanhu has joined #openstack-meeting12:55
*** gcb has quit IRC12:56
*** lvdongbing has joined #openstack-meeting12:59
*** XueFengLiu has joined #openstack-meeting12:59
yanyanhu#startmeeting senlin13:00
openstackMeeting started Tue Nov 29 13:00:07 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
yanyanhuhi, guys13:00
XueFengLiuhi yanyan13:00
yanyanhuhi, XueFengLiu13:00
lvdongbinghi, all13:00
yanyanhuhi, Qiming13:00
yanyanhulets wait for a while for other attenders13:01
yanyanhuhere is the agenda, https://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Agenda_.282016-11-29_1300_UTC.2913:01
yanyanhuplease feel free to add items13:01
yanyanhuok, lets move on13:02
yanyanhu#topic ocata workitem13:02
*** openstack changes topic to "ocata workitem (Meeting topic: senlin)"13:02
yanyanhuhere is the list13:02
yanyanhu- Improve tempest API test13:03
*** elynn has joined #openstack-meeting13:03
*** weshay_pto is now known as weshay13:03
yanyanhuI think we can consider to start working on it for the versioned request support is almost done13:03
*** baoli has joined #openstack-meeting13:03
*** bobh_ has joined #openstack-meeting13:04
*** lhx__ has quit IRC13:04
*** jaypipes has joined #openstack-meeting13:04
*** jtomasek has quit IRC13:04
yanyanhuthe basic idea is adding the verification of exception message13:04
Qimingwe have removed the performance benchmarking work completely?13:04
yanyanhuto ensure the request handling logic is correct13:04
yanyanhuQiming, I plan to move it back to todo list13:05
yanyanhufor I don't have time to work on it recently...13:05
yanyanhuif anyone want to pick it up, that will be great13:05
QimingI see13:05
*** guoshan has joined #openstack-meeting13:06
yanyanhuthe basement is there, just need efforts to support more profiles and scenarios13:06
yanyanhuok, next one13:06
yanyanhuHA support13:07
*** lixinhui has joined #openstack-meeting13:07
yanyanhuhi, lixinhui13:07
yanyanhuwe just started the topic about HA in seconds :)13:07
yanyanhuany new progress?13:08
lixinhuiin the past week, I submitted the ocativia BP and patch13:08
Qimingnoticed that and your patch13:08
*** baoli has quit IRC13:08
Qiminggood work13:08
lixinhuiMichael has some question about the background13:09
*** lblanchard has joined #openstack-meeting13:09
lixinhuiand I gave some answer13:09
yanyanhuabout using lbaas hm for HA purpose?13:10
lixinhuiif answer can not resolve his questions, may need to discuss that on the weekly meeting of ocativa13:10
*** hai_shi has joined #openstack-meeting13:10
*** hai_shi has quit IRC13:10
lixinhuiyes, I mentioned the use case13:10
*** manikanta_tadi has quit IRC13:11
*** liuyulong_ has joined #openstack-meeting13:11
Qiminghope it won't become next vpnaas13:11
Qimingwhich is dying13:11
lixinhuiyes, it is dying13:11
*** haiwei_ has joined #openstack-meeting13:11
yanyanhupeople do have strong requirement for native lb support13:12
lixinhuianyway, not a big change. hope he can accept13:12
*** mpaolino has quit IRC13:12
yanyanhualthough imho, lbaas is not ready fro production requirement13:12
*** ayogi has quit IRC13:13
yanyanhuso maybe we can give them a simple introduction about our use case13:13
Qimingthey may and may not care13:13
yanyanhuQiming, yes13:13
yanyanhuso we just try our best13:13
Qimingit is not about our use case13:13
Qimingit is their BUG13:14
*** trinaths has left #openstack-meeting13:14
yanyanhuactually this is a contribution for lbaas I feel13:14
Qiminga serious bug, they need to take care of it13:14
yanyanhuno harm for them :)13:14
*** fnaval_ has joined #openstack-meeting13:14
yanyanhuQiming, you mean the incorrect health status of lb member13:14
Qimingif lbaas is maintaining health status for nodes, they should do it right13:14
yanyanhuI mean omitting event for status change13:15
Qimingwe tried help fix it, and they reject the patch, and they "WON'T" fix the bug13:15
yanyanhuI have more strong feeling that our work about event/notification is such important :)13:15
Qimingnow xinhui is trying another workaround, let them send out notifications when node health change13:15
*** apetrich has joined #openstack-meeting13:15
lixinhuiI think it is not reasonable to submit patch into lbaas any more13:15
yanyanhuQiming, yes, have the save feeling for that patch13:16
yanyanhuanyway, it's their decision.13:16
*** fnaval has quit IRC13:16
lixinhuiso we are trying to use ocativia to emit event13:16
lixinhuithen any listener can handle in their own way13:16
Qimingmaybe need a ptl to ptl talk with them13:16
yanyanhulixinhui, yes, that's pretty reasonable13:16
lixinhuino need to care about neutron-lbaas anymore13:16
lixinhuiyes, agree Qiming :)13:17
yanyanhuso neutron-lbaas and ocaticia are two individual projects?13:17
yanyanhuI see13:17
lixinhuineutron-lbaas is dying13:17
yanyanhuI thought they are the same project13:17
*** guoshan has quit IRC13:18
haiwei_there is lbaasv2?13:19
lixinhuiI will keep tracking the patch13:19
lixinhuithat is my part13:19
yanyanhuso maybe we need to have further discussion on this issue13:19
lixinhuiof update13:19
lixinhuiYes, Haiwei_13:19
yanyanhuto see how to move on13:19
lixinhuilbaasv1 has been droped13:19
*** stevemar__ has quit IRC13:19
*** pnavarro has quit IRC13:19
yanyanhuyes, lbaasv2 is now the default enabled api13:20
Qimingneutron ptl is armax13:20
*** stevemar__ has joined #openstack-meeting13:20
lixinhuiMichael Johnson is the octavia PTL13:20
yanyanhuoctavia is part of neutron?13:20
*** julim has joined #openstack-meeting13:20
*** yamamoto has joined #openstack-meeting13:20
yanyanhuor an individual project?13:20
Qimingoctavia has its own core team: https://review.openstack.org/#/admin/groups/370,members13:20
lixinhuithey have the same weekly meeting with neutron13:21
haiwei_lbaas is dying, lbaasv2 is the substitute?13:21
Qimingyes, I think so, haiwei_13:21
*** yamamoto_ has joined #openstack-meeting13:22
yanyanhuwait a minute, lbaasv1 is dying or lbaas project is dying?13:22
elynnOh, I thought lbv2 is dying too13:22
yanyanhuI see13:22
haiwei_thanks goddess , they are not dying both13:22
lixinhuilbaasv1 has been dropped13:22
yanyanhuyes, it is13:22
haiwei_v1 is dead, v2 is dying?13:23
*** andymaier has joined #openstack-meeting13:23
yanyanhuI don't know, I'm listening :)13:23
*** jrist has joined #openstack-meeting13:23
lixinhuiI did not hear anything about v2 is dying13:23
yanyanhusigh, if so, lbaas project is ok13:24
yanyanhujust its v1 api is deprecated which is expected13:24
haiwei_it seems the advanced feature like lbaas , vpn are done by vendors themselves13:24
lixinhuiocativa will replace neutron-lbaas13:24
*** stevemar__ has quit IRC13:24
*** Ruijie_ has joined #openstack-meeting13:25
lixinhuithey are on the path of transforming13:25
*** yamamoto has quit IRC13:25
*** haleyb_ has joined #openstack-meeting13:25
*** mickeys has joined #openstack-meeting13:25
yanyanhureplace? you mean enhancement or completely replacement13:25
yanyanhuso no more haproxy based lb13:25
yanyanhuonly vm based one13:25
lixinhuithat is another reason why we should not submit patch to the dying project13:26
yanyanhuand neutron-lbaas will be renamed to octivia?13:26
*** spzala has joined #openstack-meeting13:26
lixinhuiby default, octavia provide haproxy lb13:26
Qiminghaproxy installed into a VM13:26
lixinhuiand it provide driver for different vendors to plugin13:26
yanyanhuyes, this is what lbaas is doing now13:27
lixinhuiso it is not necessary to have also neutron-lbaas...13:27
yanyanhuso octivia will replace lbaas in bigtent?13:27
*** bobh_ has quit IRC13:28
lixinhuino one ever mention big tent obviously13:28
*** hoangcx has joined #openstack-meeting13:28
yanyanhuanyway, proposing patch to octivia is reasonable13:28
XueFengLiuOctavia is currently the reference backend for Neutron LBaaS. In the near future, Octavia is likely to become the standard OpenStack LBaaS API endpoint.13:28
*** andymaier has quit IRC13:29
yanyanhuI see.13:29
*** ayoung has quit IRC13:29
*** mickeys has quit IRC13:29
Qimingshould we move on? we have been talking about this extraterrestrial project for 30 minutes13:30
elynnSo customers who use lbv1 API will be easy to transfer to use octavia, right?13:30
yanyanhuso we just focusing on communication with octavia team13:30
Qiming20 minutes, sorry13:30
*** spzala has quit IRC13:30
yanyanhusorry, lets discuss this issue offline13:30
yanyanhulets move on now13:30
Qimingping the cores, send emails to mailinglist, we will find out13:30
yanyanhuno document update I think13:31
*** rossella_s has quit IRC13:31
yanyanhuversion request support13:31
yanyanhualmost done13:31
yanyanhuI will finish receiver part this week13:31
*** rossella_s has joined #openstack-meeting13:31
yanyanhuI think XueFengLiu and lvdongbing's work has been done13:31
yanyanhuthen we can anounce the first step is finished13:32
XueFengLiuYes, only action create/delete need to do.13:32
yanyanhuXueFengLiu, thanks13:32
Qimingremove line 20?13:32
yanyanhuQiming, yes13:32
*** lhx__ has joined #openstack-meeting13:33
yanyanhuok, next one, container profile13:33
yanyanhuhi, haiwei_13:33
* Qiming really enjoys pressing the DEL key13:33
haiwei_hi, yanyanhu, I think we need to discuss the image management of containers13:34
yanyanhuhaiwei_, yes, that is an important issue13:34
yanyanhucurrently, we can get image from glance I think?13:34
yanyanhualthough it is not layered13:34
haiwei_I think the next step maybe the image jobs, what do you think Qiming13:34
Qimingwhat do you mean by image jobs?13:35
haiwei_I am think about using Zun yanyanhu13:35
*** huanxuan has joined #openstack-meeting13:35
haiwei_how to give the container an image13:35
Qimingwhen you do glance image-create, you have this:13:36
yanyanhuyes, maybe this is the first choice, at least for now?13:36
Qiming  --container-format <CONTAINER_FORMAT>13:36
Qiming                        Format of the container Valid values: None, ami, ari,13:36
Qiming                        aki, bare, ovf, ova, docker13:36
haiwei_currently we only support downloading the images from the docker lab13:36
haiwei_not the vm's image13:36
Qiming'container-format docker'13:37
Qimingwhat does that mean?13:37
haiwei_this is glance image-create?13:37
XueFengLiuIt is13:37
haiwei_never saw this before13:38
yanyanhumay need more investigation here before making decision :)13:38
haiwei_we usually use bare for container-format13:38
haiwei_ok, will check it13:38
yanyanhuhaiwei_, great, thanks a lot13:38
XueFengLiuthis means we can upload a docker image to glance13:38
Qimingcurrent docker profile relies on docker to parse and download the image13:38
XueFengLiuuse glance-create, I thiknk13:39
yanyanhuQiming, yes, it is now13:39
*** dtrainor has joined #openstack-meeting13:39
Qimingem ... primary use case was for nova-docker I think13:39
lvdongbingthat's the way nova-docker used to work13:39
yanyanhuso maybe an important issue is figuring out how to consume container image stored in glance13:39
Qimingnot sure how useful it is if we let docker(d) to check the image13:39
yanyanhuzun has the same problem I think13:40
Qimingthe assumption is that the controller node has access to either the public hub or a local registry13:40
Qimingit sounds more of the configuration/deployment topic than a senlin programming job ?13:40
*** jtomasek has joined #openstack-meeting13:40
yanyanhuQiming, yes it is13:41
haiwei_if the image is not uploaded to glance, glance will download it from public lib and then support it to other project?13:41
*** rasca has joined #openstack-meeting13:41
yanyanhumaybe this can be a property of container profile?13:42
yanyanhuhaiwei_, not sure about how it works13:42
Qimingif wanted, user (of a public cloud) can create a vm for storing his private docker images, then start a container cluster referencing images stored there?13:42
Qimingdocker determines the registry using tag, ....13:42
yanyanhuQiming, you mean local registry for each container cluster?13:42
*** artom has joined #openstack-meeting13:43
haiwei_why use a vm to store the images?13:43
Qimingjust want to say that is possible13:43
Qimingfor public cloud13:43
*** fguillot has joined #openstack-meeting13:43
yanyanhumaybe we can collect different options and then have a dicussion to see which way is better13:43
Qimingfor private cloud, you can build it somewhere so long the controller node can access its 5000 port13:43
yanyanhuhaiwei_, maybe we can collect all possible options in an etherpad13:44
haiwei_ok, yanyanhu, will create one13:44
yanyanhuand we can leave comments there13:44
yanyanhuhaiwei_, great, thanks :)13:44
yanyanhuok, only 15 minutes left13:44
yanyanhulets move to next topic13:45
yanyanhuhi, Qiming, your turn13:45
*** zhhuabj has quit IRC13:45
*** sudipto has joined #openstack-meeting13:45
*** sudipto_ has joined #openstack-meeting13:45
Qimingokay, almost done13:46
Qimingcommon interface abstracted13:46
Qimingno reviews yet13:46
Qimingmay have to approve it myself13:46
Qimingnext thing would be about the configuration part13:47
Qimingmaking 'database' and 'message' two plugins13:47
Qimingand load them via steverdore13:47
Qimingadd senlin.conf section/options to control when/how to log ...13:48
yanyanhusounds great13:48
yanyanhuabout the message way, so the messages will be published to a public queue?13:48
yanyanhuwhich is accessable for all openstack services13:49
yanyanhuI see13:49
Qimingit is controller plane thing13:49
Qimingirrelevant to zaqar13:49
yanyanhuthis is also what we expect octavia to do :)13:49
yanyanhuQiming, I see13:49
Qimingzaqar is USER-FACING message queue13:49
yanyanhusorry for didn't get time to review the code. Will check it tomorrow13:50
Qimingif you have check the code:13:50
yanyanhuQiming, please feel free to self approve to avoid denpendency issue13:50
Qiming85     def _emit(self, context, event_type, publisher_id, payload):13:50
Qiming 86         notifier = messaging.get_notifier(publisher_id)13:50
Qiming 87         notify = getattr(notifier, self.priority)13:50
Qiming 88         notify(context, event_type, payload)13:50
Qimingthat is all13:50
yanyanhulooks simple13:51
yanyanhuget_notifier is provided by oslo?13:51
yanyanhuI mean the backend logic13:51
yanyanhuI see13:51
Qimingwe have a thin wrapper over it13:51
Qimingalso pretty simple13:52
yanyanhuoh, is there any limit about publishing message to this public queue in control plane?13:52
Qimingdon't think so13:52
Qimingit is the same message service for rpc13:52
yanyanhuI mean if a service publishs too many messages, it could break the queue?13:53
*** fnaval has joined #openstack-meeting13:53
Qimingno experience13:53
yanyanhume neither...13:53
*** zz_dimtruck is now known as dimtruck13:53
Qimingif you have ever checked events collected by ceilometer, you will realize that we are very cautious on this13:54
*** thorst_ has quit IRC13:54
*** sridharg has quit IRC13:54
Qimingif you compare this to the number of RPC calls received by keystone13:54
yanyanhuI know ceilometer gets lots of message from other services13:54
Qimingby neutron13:54
*** thorst_ has joined #openstack-meeting13:54
Qimingthings we are sending are trivial13:54
yanyanhuyes, compared with others13:55
*** bobmel has quit IRC13:55
*** fnaval_ has quit IRC13:55
Qimingalso compare to what nova is sending out: http://git.openstack.org/cgit/openstack/nova/tree/nova/notifications/objects/instance.py#n24613:55
*** bobmel has joined #openstack-meeting13:56
*** ralonsoh_ has joined #openstack-meeting13:56
yanyanhumessage for each status switching for each instance13:56
*** lamt has joined #openstack-meeting13:56
Qimingso I'm not that worried about it13:57
yanyanhuok, seems we don't need to worry about this issue13:57
Qimingin addition, we are making the behavior configurable13:57
*** ralonsoh has quit IRC13:57
*** Qiming has quit IRC13:57
yanyanhuI see13:58
*** haiwei_ has quit IRC13:58
yanyanhuok, these are all workitems on the list13:58
yanyanhuthe time is almost done13:58
yanyanhuany more update?13:58
yanyanhuif not, will end the meeting.13:58
yanyanhuhi, lixinhui, still there?13:59
yanyanhuif it's ok, want to talk with you about the patch for octavia13:59
*** Qiming has joined #openstack-meeting13:59
yanyanhuwe can discuss how to work on it together13:59
yanyanhuto push it move on13:59
yanyanhuok, time is over. Thanks you guys for joining14:00
yanyanhuhave a good night14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Tue Nov 29 14:00:12 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-11-29-13.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-11-29-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-11-29-13.00.log.html14:00
XueFengLiugood night14:00
*** bobmel has quit IRC14:01
*** lezbar has joined #openstack-meeting14:01
*** bobmel has joined #openstack-meeting14:02
*** lvdongbing has quit IRC14:02
*** baoli has joined #openstack-meeting14:03
*** zhhuabj has joined #openstack-meeting14:03
*** yanyanhu has quit IRC14:04
*** xyang1 has joined #openstack-meeting14:06
*** XueFengLiu has quit IRC14:06
*** tobybot11 has joined #openstack-meeting14:07
*** m1dev has joined #openstack-meeting14:08
*** Worry has joined #openstack-meeting14:09
*** elynn has quit IRC14:10
*** donghao has joined #openstack-meeting14:12
*** stevemar__ has joined #openstack-meeting14:17
*** jamesdenton has joined #openstack-meeting14:17
*** zul has quit IRC14:18
*** sballe_ has quit IRC14:18
*** sballe_ has joined #openstack-meeting14:19
*** guoshan has joined #openstack-meeting14:22
*** jamesdenton has quit IRC14:23
*** dmacpher has joined #openstack-meeting14:24
*** dmacpher_ has joined #openstack-meeting14:24
*** Ruijie_ has quit IRC14:24
*** mickeys has joined #openstack-meeting14:26
*** lhx__ is now known as lhx_14:27
*** krtaylor has quit IRC14:28
*** enriquetaso has joined #openstack-meeting14:29
*** fguillot has quit IRC14:29
*** mriedem has quit IRC14:29
*** zul has joined #openstack-meeting14:30
*** mickeys has quit IRC14:30
*** zul has quit IRC14:30
*** jamesdenton has joined #openstack-meeting14:30
*** zul_ has joined #openstack-meeting14:31
*** guoshan has quit IRC14:32
*** kun_huang has joined #openstack-meeting14:36
*** krtaylor has joined #openstack-meeting14:36
*** tobybot11 has quit IRC14:38
*** dasm has quit IRC14:39
*** dmacpher_ has quit IRC14:40
*** liuyulong_ has quit IRC14:42
*** NeverWorry has joined #openstack-meeting14:42
*** Worry has quit IRC14:42
*** xiangxinyong has joined #openstack-meeting14:44
*** irenab has quit IRC14:45
*** ljxiash has joined #openstack-meeting14:46
*** fnaval has quit IRC14:46
*** zhonghua_ has joined #openstack-meeting14:46
*** [HeOS] has quit IRC14:47
*** cleong has joined #openstack-meeting14:47
*** huanxuan has quit IRC14:48
*** leon_wang has joined #openstack-meeting14:48
*** saggi has joined #openstack-meeting14:49
*** mtanino has joined #openstack-meeting14:51
*** zhhuabj has quit IRC14:51
*** liamji has joined #openstack-meeting14:51
*** zhonghua_ has quit IRC14:52
*** NeverWorry has quit IRC14:54
*** zhhuabj has joined #openstack-meeting14:55
*** prateek has joined #openstack-meeting14:56
*** jgregor has joined #openstack-meeting14:57
*** saggi has quit IRC14:57
*** prateek has quit IRC14:57
*** mriedem has joined #openstack-meeting14:57
*** prateek has joined #openstack-meeting14:57
*** dasm has joined #openstack-meeting14:58
*** saggi has joined #openstack-meeting14:58
*** rbak has joined #openstack-meeting15:00
*** dimtruck is now known as zz_dimtruck15:00
saggi#startmeeing karbor15:01
saggi#startmeeting karbor15:01
openstackMeeting started Tue Nov 29 15:01:56 2016 UTC and is due to finish in 60 minutes.  The chair is saggi. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** zul_ is now known as zul15:01
*** openstack changes topic to " (Meeting topic: karbor)"15:01
openstackThe meeting name has been set to 'karbor'15:02
saggiHi everyone15:02
xiangxinyonghi saggi15:02
leon_wangsaggi: hi saggi15:02
*** chenying has joined #openstack-meeting15:02
saggiThere are no agenda items AFAIK15:02
saggibut I think we can discuss the spec for the protection plugin design15:03
saggisince it's a hot matter of contention15:03
yuvalsaggi: yep, I agree15:03
saggi#topic protection plugin spec15:03
*** openstack changes topic to "protection plugin spec (Meeting topic: karbor)"15:03
*** zhonghua_ has joined #openstack-meeting15:03
*** zengchen has joined #openstack-meeting15:04
*** spotz_zzz is now known as spotz15:04
*** spzala has joined #openstack-meeting15:04
*** bobh_ has joined #openstack-meeting15:04
*** acoles is now known as acoles_15:04
*** fnaval has joined #openstack-meeting15:05
saggiThe main issue of contention seems to be complexity.15:05
chenyingMy oppions is that spilt the backup action to several hooks, it too complex for vendors to integrate their solutions.15:05
yuvalFrom what I understand, this seem complex. As a matter of fact, most of the plugin api is optional, and implementing straight-forward plugins should be relatively easy15:05
*** spzala has quit IRC15:06
*** spzala has joined #openstack-meeting15:06
saggiAs the spec says much of the features are optional. There is nothing stopping people from just implementing the main callback15:06
*** spzala has quit IRC15:06
saggiit will cause everything to run in parallel15:06
saggiThe rest of the hooks are for specialized use cases15:06
*** spzala has joined #openstack-meeting15:06
*** spzala has quit IRC15:07
*** oshidoshi has quit IRC15:07
*** spzala has joined #openstack-meeting15:07
*** spzala has quit IRC15:07
saggiThough we already know of use cases where a protection plugin will have to use some of the hooks15:07
*** jgregor_ has joined #openstack-meeting15:07
*** spzala has joined #openstack-meeting15:08
*** spzala has quit IRC15:08
zengchensaggi:at present, there is a scenario that protect service can not support.15:08
*** nadya has quit IRC15:08
saggizengchen: what scenario?15:09
*** spzala has joined #openstack-meeting15:09
*** spzala has quit IRC15:09
zengchensaggi:if user want to protect whole vm with their own plugin which just input id of vm.15:09
*** spzala has joined #openstack-meeting15:09
*** spzala has quit IRC15:10
zengchensaggi:karbor will fetch the volumes attached to the vm to protect together.15:10
*** spzala has joined #openstack-meeting15:10
*** spzala has quit IRC15:10
saggiIn the context of karbor there is no such thing as protecting the whole vm since you don't know what resources are related to the VM. What does make since is being responsible for some of the resources.15:10
zengchensaggi:but user just has one plugin that protect vm15:11
saggiFor example having a plugin for VM and Volumes15:11
*** spzala has joined #openstack-meeting15:11
*** jgregor has quit IRC15:11
*** spzala has quit IRC15:11
saggiThis will work with the paradigm we suggest.15:11
*** hoangcx has quit IRC15:11
*** slaweq_ has quit IRC15:11
saggiThe plugin will register for volume and vm15:12
*** spzala has joined #openstack-meeting15:12
*** spzala has quit IRC15:12
saggiwhen it reaches the prepare stage it will get the sub tree15:12
saggiit will get all the information it needs and prepare information for the main phase15:12
*** slaweq_ has joined #openstack-meeting15:12
*** spzala has joined #openstack-meeting15:12
*** jmckind has joined #openstack-meeting15:13
*** spzala has quit IRC15:13
saggiwhich could just be sending the instruction somwhere else and waiting on the result15:13
chenyingsaggi: Why do you think the plugins don't know the  resources are related to the VM? As I know, several vendor has the solution to protect all vm, only need the id of vm.15:13
saggiThe the plugin could just no-op for volume15:13
*** spzala has joined #openstack-meeting15:13
saggiand have the main just track the main VM task15:13
*** spzala has quit IRC15:13
saggior, if the service gives detailed progress. Show progress related to the resource.15:14
chenyingsaggi: There are some workflow in ther backup software like NBU or simpala, to fetch get related volumes about the protected vm.15:14
*** spzala has joined #openstack-meeting15:14
*** spzala has quit IRC15:14
*** spzala_ has joined #openstack-meeting15:14
*** jaugustine has joined #openstack-meeting15:14
*** spzala_ has quit IRC15:14
*** spzala has joined #openstack-meeting15:15
zengchensaggi:i think your description is karbor's solution. it may be right. but it is not appropirate to integrate the vendor's solution.15:15
*** tommylikehu_ has joined #openstack-meeting15:15
yuvalchenying: if the nbu/simpala karbor plugin registers to protect both VM and Volumes, it can send nbu/simpala the VM, and do nothing for volumes or wait until the VM protect is complete15:15
chenyingIn this scenario, the vendors only need dev a plugins  about the main VM task, don't need dev a plugins about volume.15:16
chenyingyuval I think so15:16
*** saisrikiran has joined #openstack-meeting15:16
saggizengchen: They need to specify that the volumes are taken care of. Since Karbor needs to know that this type is accounted for.15:16
leon_wangchenying: has these vendors provided solutions integrating with VMs now?15:17
*** dasm has quit IRC15:18
saggizengchen: Whatever the vendors protect we need to save information in the checkpoint about the result of the protection.15:18
leon_wangchenying: and is it possible for karbor to seamlessly integrate them?15:18
chenyingleon_wang: simpala plan to integrate the vm protection solution with Karbor,  but I am not when to integrate with karbor.15:19
zengchensaggi:maybe we should think more about how to integrate vendor's solution easily. because that is one of karbor's mission.15:19
*** tonytan4ever has joined #openstack-meeting15:19
leon_wangzengchen: yeah, also reduce our work.15:19
saggizengchen: That is what we are thinking about. What we know is that different vendors protect different things. This is why we need the ProtectionPlugin to specify what it protects and handle status and progress saving per resource.15:21
saggiI don't see a way around this. Let's say that the protection failed because on of the volumes failed. We want to show it to the user. For this we need to know to get information about volumes.15:21
zhonghua_hey, sorry, I am late, but where can I find the agenda for this meeting? so that I can caught up with you.15:21
saggizhonghua_: We are talking about this spec [ https://review.openstack.org/#/c/397156/ ]15:21
zhonghua_saggi: thanks15:22
*** diga has joined #openstack-meeting15:22
leon_wangsaggi:i think it would be better if the vendor can open these interface to karbor.15:22
yuvalI think there are two questions here: 1) does this API fits common vendor use cases 2) is this API easy to understand/use15:23
zengchensaggi:as i said in that patch, yuval's design is very good. can we define simpler interfaces and move the yuval's desgin and resource dependency analysing etc as karbor's default solution?15:23
yuvalsometimes, making the API flexible so it fits common use cases, might make it a bit more complex15:23
*** rasca has quit IRC15:24
yuvalthis is why most hooks are optional, and writing a simple plugin requires only one main hook15:24
saggizengchen: I don't understand what you think is complex. The dependency graph building or the ProtectionPlugin interface.15:24
*** prateek has quit IRC15:24
chenyingleon_wang: some vendor have already open the restAPI about their backupsoftwares, I don't think this is a problow,15:24
leon_wangchenying: got it, thanks15:25
*** nadya has joined #openstack-meeting15:25
zengchensaggi:take Heat as an exmple. it just define two interfaces for resource plugin to create resource. they are 'handle_create', 'check_create_complete'15:25
*** jmckind_ has joined #openstack-meeting15:26
*** rajinir has joined #openstack-meeting15:26
*** mickeys has joined #openstack-meeting15:26
zengchensaggi:as yuval's design, one plugin has 5 interfaces and some are optional.15:26
*** jmckind has quit IRC15:27
*** ljxiash has quit IRC15:27
saggizengchen: 4 hooks15:27
zengchensaggi:yuval's design is good. but IMO, it is one of solution to protect.15:27
saggizengchen: This is because they don't need the prepare phase.15:27
saggiThe prepare phase is the most complex15:27
*** ljxiash has joined #openstack-meeting15:27
saggibut it can wield a lot of benefit15:27
saggifor example15:27
zengchensaggi:i know, it is flexible. it is good.15:28
*** zz_dimtruck is now known as dimtruck15:28
saggiIf you have a VM with 3 volumes. You need to take a snapshot for each and copy the data to 3 different sites.15:28
saggiTaking the snapshots should be done at the same time15:28
saggicopying can be done later15:28
*** mriedem is now known as mriedem_meeting15:29
saggiif we have only one hook "main"15:29
saggiwe put taking the snapshot and copying the data at the same place15:29
saggicopying the data could take a lot of time15:29
*** korzen has quit IRC15:29
saggimeaning that the snapshots might be made at drastically different points in time15:29
zengchensaggi:but for professional preotect software, they just need plugin to send small parameters to it.15:30
saggiSo you should take the snapshot in prepare and then copy in main15:30
saggizengchen: even some professional solutions might not support copying the data off site natively15:30
saggizengchen: and for this solutions they don't need to implement the prepare phase15:31
*** mickeys has quit IRC15:31
saggiThey only need to implement one hook15:31
saggiall hooks are optional15:31
saggiBut we can't only support vendors that have replication and snapshot built in15:32
saggiwe need to also support vendors that only have snapshot15:32
*** jprovazn has joined #openstack-meeting15:32
zengchensaggi:ok, i hold my idea.15:32
yuvalzengchen: what's your idea? do you think we can minimize the amount of hooks? different api?15:33
saggizengchen: Please rephrase that, I don't understand15:33
zengchensaggi:your idea is reasonable. but i still think it is too complex. so i hold my idea.15:34
*** eharney has joined #openstack-meeting15:34
*** slayer has joined #openstack-meeting15:34
saggizengchen: How do you suggest to solve the problem I suggested.15:34
saggiWe need that for the Cinder implementation15:34
saggizengchen: I also don't understand what your idea is. Just only having *main phase* and *complete phase*15:35
*** sshnaidm is now known as sshnaidm|mtg15:35
*** dmorita has joined #openstack-meeting15:36
zengchensaggi:my idea is decribed in the comment.15:36
zengchensaggi:you can see it.15:36
saggizengchen: I saw it. I can't see how it can solve the user case I proposed.15:37
saggiIt will only work for the once case where everything is taken care of by someone else.15:37
zengchensaiig:ok, i will think more about your idea.15:37
*** rasca has joined #openstack-meeting15:38
*** zul has quit IRC15:38
*** zul has joined #openstack-meeting15:38
xiangxinyongI am confused with the relationship between this patch and full vm backup?15:38
saggizengchen: We also have the quiesce use case, where we don't want to hold the VM in quiescent state for as little time as possible.15:39
saggixiangxinyong: full vm backup is the easiest use case to support. It will ignore most of the features.15:39
zengchensaggi:i didn't refuse you and yuval's idea.15:40
*** corey_ has joined #openstack-meeting15:40
*** dmorita has quit IRC15:40
*** ljxiash has quit IRC15:40
saggizengchen: We also want you to agree :)15:40
sagginot just not refuse15:40
zhonghua_why not invite some 3rd vendors to get their comments?15:40
*** cleong has quit IRC15:40
chenyingsaggi: IMO, we also need pay more attention to discuss these interfaces with backup software vendor about different resources portection solution.15:41
*** myoung|bbl is now known as myoung15:41
yuvalzhonghua_: chenying: that sounds like a good idea15:41
zhonghua_yuval: :)15:42
xiangxinyongchenying: As you said, the vendors will only pass the vm id into the plugin to protect whole vm?15:42
zengchensaggi:i just suggest that move your idea as the default solution. then user can develop their plugins by inherited default plugin. or the basic plugin.15:42
*** ricolin has joined #openstack-meeting15:43
chenyingWe need the comments about workflow and plugins interfaces form different vendors.15:43
*** ricolin has quit IRC15:44
chenyingxiangxinyong: As I know, it is.15:44
saggizengchen: The way it's designed you don't need any base code. Any function you need you implement any that you don't you don15:44
yuvalchenying: the workflow is karbor internals. The plugin api is the most important part15:45
*** donghao has quit IRC15:45
zengchensaggi:sorry, not quite understand.15:46
chenyingyuval Yes The plugin api is the most important part. Most of time, it is design for vendors, it is also very important for backup vendors.15:46
zhonghua_yuval: chenying: +115:47
*** fguillot has joined #openstack-meeting15:47
saggizengchen: I'll try and cook up some examples for how to do Full VM backup with this inteface15:47
yuvalchenying: agrees15:48
*** ljxiash has joined #openstack-meeting15:49
zengchensaggi:ok. maybe we should do it first. then return to check.15:49
saggi#topic open discussion15:49
*** openstack changes topic to "open discussion (Meeting topic: karbor)"15:49
*** bnemec has joined #openstack-meeting15:49
saggiAnything else for the last 10 minutes15:49
*** hrybacki is now known as hrybacki|mtg15:50
*** mmotiani_ has joined #openstack-meeting15:50
*** fnaval has quit IRC15:50
yuvalzhonghua_: I've seen some students contributing these days15:51
*** galstrom_zzz is now known as galstrom15:51
yuvalzhonghua_: would you like to share about your activities?15:51
zengcheni have subbit a spec on resolving token's expiration. so hope every guys can review it.15:51
zhonghua_yuval: yeah, sure, but it held by xiangxinyog15:51
*** tommylikehu_ has quit IRC15:51
zhonghua_xiangxinyong: could you please share the communication activities?15:52
chenyingI think we need add more fulltest about different portect flow and use cases. Now the tests in karbor is too simple.15:52
chenyingzengchen: I will.15:53
*** ljxiash has quit IRC15:53
xiangxinyongyuval,saggi: you know our team make a hands-on like the summit in a university under zhonghua's lead15:53
*** pnavarro has joined #openstack-meeting15:53
xiangxinyongand we introduce how to contribute in the openstack and karbor.15:54
yuvalxiangxinyong: sounds great15:54
xiangxinyongand we prepared some blogs for students to operate step by step15:54
*** diga has quit IRC15:55
*** baoli has quit IRC15:55
xiangxinyongThis is the team's blog.http://www.cnblogs.com/openstackteam/15:55
*** fnaval has joined #openstack-meeting15:55
*** baoli has joined #openstack-meeting15:55
zhonghua_xiangxinyong: great jobs15:55
saggigood work!15:56
xiangxinyongzhonghua_: thanks15:56
leon_wangxiangxinyong: Great job!15:56
xiangxinyongIt's our team's work15:56
zengchenxiangxinyong:they are all chinese. are you sure saggi & yuval can understand?15:56
*** tbh has joined #openstack-meeting15:56
chenyingwell done!15:56
saggiwe'll try and use google translate15:56
xiangxinyongbecause the whole team was arrived the university and help the students to do some practice15:57
xiangxinyongbut we need to help the students to raise the experience in OpenStack15:57
*** dkushwaha has joined #openstack-meeting15:58
xiangxinyongzhonghua makes a very good speech about barcelona summit in the university15:58
*** mmotiani_ has quit IRC15:58
*** edtubill has joined #openstack-meeting15:58
saggiOK, I don't know if you guys know but Yuval will be unavailable next week. Feel free to bug me about things.15:58
xiangxinyongand the whole team members helped the students to make pratice15:59
leon_wangxiangxinyong: i think it's a good way to help us perfect our use cases.15:59
xiangxinyongsaggi: sure15:59
saggiAre window is up15:59
*** madorn has quit IRC15:59
saggiwe can continue on #openstack-karbor15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Tue Nov 29 15:59:48 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/karbor/2016/karbor.2016-11-29-15.01.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/karbor/2016/karbor.2016-11-29-15.01.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/karbor/2016/karbor.2016-11-29-15.01.log.html15:59
leon_wangbye everyone15:59
yuvalbye all16:00
*** tung_doan has joined #openstack-meeting16:00
*** yuval has quit IRC16:00
*** chenying has quit IRC16:00
*** mriedem_meeting is now known as mriedem16:00
*** marchetti has joined #openstack-meeting16:00
sripriya#startmeeting tacker16:00
openstackMeeting started Tue Nov 29 16:00:34 2016 UTC and is due to finish in 60 minutes.  The chair is sripriya. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: tacker)"16:00
openstackThe meeting name has been set to 'tacker'16:00
sripriyahi tackers16:00
sripriya#topic Roll Call16:00
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"16:00
*** cathrichardson has joined #openstack-meeting16:01
*** iyamahat has joined #openstack-meeting16:01
*** csomerville has joined #openstack-meeting16:02
*** acoles_ is now known as acoles16:02
*** leon_wang has quit IRC16:02
sridhar_ramhowdy all!16:02
tung_doansridhar_ram: nice to have you back :)16:02
sripriyatbh dkushwaha tung_doan aimeeu hello!16:02
*** neeldhwaj has joined #openstack-meeting16:02
dkushwahahi sridhar_ram good to see you here16:02
*** strigazi_AFK is now known as strigazi16:02
*** diga has joined #openstack-meeting16:02
tbhHi sridhar_ram16:02
sripriyasridhar_ram: very huge welcome back!16:03
*** rcernin has quit IRC16:03
sridhar_ramtung_doan: dkushwaha: tbh: thanks!16:03
dkushwahasridhar_ram, how are you now?16:03
sripriyasridhar_ram: happy to have you back16:03
digasridhar_ram: welcome back!16:03
*** KanagarajM has joined #openstack-meeting16:03
sridhar_ramsripriya: thanks for running the tacker ship, looks you didn't miss a beat...!16:03
sripriyadiga: neeldhwaj hello16:03
sridhar_ramdiga: thanks16:03
*** xiangxinyong has left #openstack-meeting16:04
digasridhar_ram: welcome!16:04
sripriyasridhar_ram: nothing comparable to you :-) you do it best :-)16:04
digasripriya: hi16:04
sripriyasridhar_ram: but thank you16:04
*** spotz is now known as spotz_zzz16:04
sripriyaand thanks to the team!16:04
sridhar_ram^^ yes.. thanks team!16:04
KanagarajMsridhar_ram, hope you are fine now !16:04
sridhar_ramstill catching up, will hang back for this meeting.. please carry on16:05
sridhar_ramKanagarajM: thanks!16:05
sripriyaalright let us get started16:05
sripriya#topic agenda16:05
*** openstack changes topic to "agenda (Meeting topic: tacker)"16:05
*** rbak has quit IRC16:05
sripriya#link https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Nov_28th.2C_201616:05
*** zhonghua_ has quit IRC16:05
sripriyalet us quickly go through the meeting time update and dsvm error, later we can discuss on the specs16:05
*** jdurgin1 has joined #openstack-meeting16:05
sripriya#topic revisit weekly meeting time16:06
*** openstack changes topic to "revisit weekly meeting time (Meeting topic: tacker)"16:06
sripriyasridhar_ram: i know you had suggestion to change the weekly meeting update i guess even before the barcelona summit to gather all developers across TZs16:07
sripriyasridhar_ram: do we need to have a doodle poll for a new weekly meeting time?16:07
sridhar_ramsripriya: yes, particularly with the shifting out of daylight saving...16:07
sridhar_ramsripriya: we can do a doodle poll,16:08
sridhar_ramif we can quickly sample here.. does anyone have major issue if we push this meeting my 1hr?16:08
*** cathrichardson has left #openstack-meeting16:08
sridhar_ram1700 UTC16:09
sripriyasridhar_ram: fine with me16:09
sridhar_ramhow about folks in Asia ?16:09
tung_doansridhar_ram: seems like hard for me :(16:09
*** haleyb__ has joined #openstack-meeting16:09
dkushwahasripriya, 1 hour prior16:09
sridhar_ramtung_doan: ack16:09
tbhsridhar_ram, sripriya I am fine with that16:10
digaFine with me too16:10
sridhar_ramokay, will send a doodle poll out16:11
sridhar_ramfor the record, current 1600UTC / 8AM is not possible for me.16:11
sripriyasridhar_ram: looks like folks are okay except tung_doan and others in asia pacific TZ16:11
*** haleyb_ has quit IRC16:11
tung_doandkushwaha: how are you, bro? :)16:12
sridhar_ramsripriya: anyone else joins from APAC ?16:12
tung_doandkushwaha: how about you, bro? :)16:12
sridhar_ramdkushwaha: are you still in Japan?16:12
sripriyasridhar_ram: i know gongysh is interested to join the meetings16:12
*** ygbo has joined #openstack-meeting16:12
dkushwahasridhar_ram, tung_doan yes, will be back to India in next week16:12
sridhar_ramsripriya: oh yes, we miss him due to the meeting timing16:12
*** rbak has joined #openstack-meeting16:12
sripriyasridhar_ram: and i guess few other folks from NEC16:12
sridhar_ramone option is we can go really early in US pacific.. say, 6:30AM16:13
sridhar_ramor 6AM16:13
sripriyasridhar_ram: :)16:13
sridhar_ramwill send a doodle poll and we can take it from there..16:14
sripriyasridhar_ram: sounds good,16:14
sripriya#action create a doodle poll for new weekly meeting time16:14
sripriyais this the tag sridhar_ram? :)16:14
*** kevinz has quit IRC16:15
sripriyaok cool16:15
sripriyamoving on16:15
sripriya#topic dsvm gate job update16:15
*** openstack changes topic to "dsvm gate job update (Meeting topic: tacker)"16:15
sripriyatung_doan: thanks for actively looking into dsvm job error and actively fixing it16:16
*** haleyb__ has quit IRC16:16
sripriyatung_doan: it will be good to give the team an update on the dsvm error fix16:16
tung_doansripriya: np.. latest patch was fix networking-sfc plugin16:16
tung_doansripriya: the problem now is back to tacker :(16:17
tung_doansripriya: http://logs.openstack.org/79/382479/18/check/gate-tacker-dsvm-functional-ubuntu-xenial-nv/9e5a8c3/logs/devstacklog.txt.gz16:17
*** yamahata has joined #openstack-meeting16:17
sripriyatung_doan: are you referring to OVS_UPDATE variable?16:17
tung_doansripriya: got  the error: http://logs.openstack.org/79/382479/18/check/gate-tacker-dsvm-functional-ubuntu-xenial-nv/9e5a8c3/logs/devstacklog.txt.gz16:18
tung_doansripriya: yes, it made sense now16:18
sridhar_ramspecifically here .. http://logs.openstack.org/79/382479/18/check/gate-tacker-dsvm-functional-ubuntu-xenial-nv/9e5a8c3/logs/devstacklog.txt.gz#_2016-11-29_12_45_00_79616:19
sridhar_ramRegionOne not found16:19
sripriyatung_doan: at least we went past the linux kernel version error and now seeing a new error16:19
sripriyatung_doan: is this consistent?16:19
tung_doansridhar_ram: right. that's my concern16:19
*** eharney has quit IRC16:19
tung_doansrippriya: +116:20
sripriyatung_doan: we will have to look into the logs closely , not sure what is messing the tacker endpoint creations in keystone16:21
tung_doansrippriya: agree16:21
*** rbartal has quit IRC16:22
sripriyatung_doan: a quick look at the logs, i do not see the nfv-orchestration endpoints created16:22
sripriyatung_doan: we can debug it further after the meeting16:22
tung_doansrippriya: ok16:23
sripriyamoving on16:23
sripriya#topic NSD spec16:23
*** openstack changes topic to "NSD spec (Meeting topic: tacker)"16:23
sripriyadkushwaha: i think we are close to merging the NSD spec, there were few comments related to input and output params support for NSD16:24
dkushwahasripriya, yes, currently we have to fix the input handling issues.16:24
*** e0ne_ has quit IRC16:24
tbhsripriya, and I have one more qq on the template part16:24
dkushwahasripriya, we are looking for the way to pass vnf into nsd16:25
*** Swanson has quit IRC16:25
sripriyadkushwaha: okay, i saw sridhar_ram suggesting the nested param template as input file for ns create16:25
sripriyatbh: shoot16:25
*** chrisplo_ has quit IRC16:25
*** mmotiani_ has joined #openstack-meeting16:25
sripriyabobh_: are you around?16:25
tbhsripriya, we have to define the VNF1 in the vnfd for example L# 169 in https://review.openstack.org/#/c/334370/8/samples/tosca-templates/nsd/tosca-nsd.yaml16:26
tbhsripriya, so that part is the new change in VNFD16:26
*** dimtruck is now known as zz_dimtruck16:26
sridhar_ramfolks - i just pushed few comments16:26
* sridhar_ram forgot to click the reply button16:27
sripriyatbh: ack, yes16:27
tbhsridhar_ram, one of your comment regarding creation of VL16:27
sripriyatbh: i know this needs a change in vnfd template too to integrate it into NSD16:27
*** mickeys has joined #openstack-meeting16:27
sripriyatbh: do you have the sample VNFD also?16:27
*** Leo_ has joined #openstack-meeting16:27
sripriyasridhar_ram: will take a look16:28
tbhsripriya, yes we need to refer only existing neutron network there16:28
sridhar_ramtbh: my question is .. do we support any node types in NSD other than VNF16:28
tbhsripriya, http://paste.openstack.org/show/590813/    http://paste.openstack.org/show/590814/16:28
*** zz_dimtruck is now known as dimtruck16:28
tbhsridhar_ram, we can declare VL too16:29
sridhar_ramtbh: okay, can be used to refer to existing networks but not create new networks ?16:29
tbhsridhar_ram, for new networks, my concern is ... we may define the same network in VNFD also, so I think it will be conflicting16:30
dkushwahasridhar_ram, sripriya, tbh  we need to mention CP also nsd template as for ns end point16:30
*** fernnest has quit IRC16:30
bobh_sripriya: sorry I'm late16:30
tbhdkushwaha, that can we can pass as forwarder as per the spec http://docs.oasis-open.org/tosca/tosca-nfv/v1.0/csd03/tosca-nfv-v1.0-csd03.html#_Toc44771473116:31
sridhar_ramtbh: it is okay to not support creating new networks in NSD for now.. it is useful, but we can take it up in follow ons.16:31
sridhar_ramtbh: i was trying to understand the scope of this initial NSD effort16:31
*** mickeys has quit IRC16:31
*** jschwarz has quit IRC16:32
*** armax has joined #openstack-meeting16:32
*** andreas_s has quit IRC16:32
sripriyatbh: i do see the substitution_mappings added to vnfd template16:32
tbhsripriya, yes16:32
sripriyabobh_: no worries, we were just discussing the NSD spec and addressing the comments16:32
sripriyatbh: is the new updated syntax which you pushed earlier?16:33
*** lhx_ has quit IRC16:33
tbhsridhar_ram, currently we are defining APIs for NS and support creation of NS with out creating the forwarding path16:33
sridhar_ramtbh: again, fair enough.. but it will be good to capture these in the spec..16:33
tbhsripriya, this is the new updated syntax, but no major changes except defining new node type in VNFD16:33
sripriyatbh: ack16:35
*** foliveira has joined #openstack-meeting16:35
*** jschwarz has joined #openstack-meeting16:35
dkushwahasripriya, bobh_ do we needs to handle vnfd output in nsd?16:35
tbhsripriya, sridhar_ram sure will update the spec, still looking for the ways to pass input params16:35
sripriyadkushwaha: going back to input param support for nsd, are we going with the nested template as an input for nsd?16:36
*** rasca has quit IRC16:36
sripriyasridhar_ram: does it make sense to give them as separate input files for nsd?16:36
bobh_dkushwaha: If the NSD is deploying a collection of VNFs then it should handle the inputs/outputs of those VNFs as necessary16:36
*** pcaruana has quit IRC16:36
*** Guest53195 has quit IRC16:36
sripriyabobh_: we do not support specifying outputs for VNFD today16:36
dkushwahasripriya, sridhar_ram please check https://review.openstack.org/#/c/334370/8/samples/tosca-templates/nsd/tosca-nsd-param.yaml16:37
sridhar_ramsripriya: I'm leaning towards using a "single" NS param input file16:37
*** dmorita has joined #openstack-meeting16:37
sridhar_ramdkushwaha: looks good to me, inline with what i proposed in my latest comments16:37
sripriyasridhar_ram: okay, it can become a lengthy nested file at some point16:37
*** dmorita has quit IRC16:38
*** dmorita has joined #openstack-meeting16:38
tbhsridhar_ram, why do we need params specified for VDUs specifically?16:38
*** sayalilunkad has quit IRC16:38
sridhar_ramsripriya: understood but it is still better compared to other option16:38
*** KanagarajM has quit IRC16:39
*** mtani____ has joined #openstack-meeting16:39
tbhsridhar_ram, instead we can specify input params per VNF?16:39
sridhar_ramtbh: then we need to worry about VNF <--> param file mapping16:40
sripriyasridhar_ram: tbh: and also the order...16:40
*** unicell1 has quit IRC16:40
*** mtanino has quit IRC16:40
sridhar_ramtbh: .. and there is an extreme case of an NSD with high number of VNFs (like vIMS) where it just becomes painful16:41
tbhsridhar_ram, if we pass params per VNF, we can use the existing API for vnf-create (by passing parameters)16:41
tbhsripriya, can you give an example of maintaining the order?16:42
tbhsripriya, I mean in which cases we have to maintain the order?16:42
sridhar_ramtbh: with a single NS param file we can still use existing vnf-create API... just the NS logic should extract the params related to a specific VNF from the single NS param file16:43
*** unicell has joined #openstack-meeting16:43
sridhar_ramtbh: i've an example in my latest comment in PS1716:43
sridhar_ramtbh: it is similar to dkushwaha above link16:43
*** unicell has quit IRC16:43
sripriyatbh: nsd might have the vnf order in a specific way, but if we are mapping it based on the vnfd name, i'm not sure how we would maintain the order while specifying the template16:43
*** unicell has joined #openstack-meeting16:44
*** kun_huang has quit IRC16:45
sridhar_ramsripriya: indexing off node name would be the way to go.. ns_param[vnf_node_name] dict16:45
*** jamesdenton has quit IRC16:45
*** hrybacki|mtg is now known as hrybacki16:45
sridhar_ramagain see https://review.openstack.org/#/c/334370/8/samples/tosca-templates/nsd/tosca-nsd-param.yaml,unified16:46
bobh_I don't think the params need to be necessarily VNF-specific - you may have NSD params that map to multiple VNF inputs16:46
tbhsridhar_ram, sripriya I was thinking something like this http://paste.openstack.org/show/590855/16:46
sridhar_ramtbh: that would work16:46
sripriyasridhar_ram: tbh: this is vnfd rightt and not vnf16:47
*** sshnaidm|mtg is now known as sshnaidm16:47
sridhar_rambobh_: to support that, we need some sort of an inherited scope16:47
tbhsripriya, name give while onboarding VNFD16:47
sripriyatbh: correct16:48
*** anilvenkata has quit IRC16:48
sridhar_ramsripriya: params comes into play only at runtime.. so ns-create --> vnf-create16:48
bobh_sridhar_ram: Can't the NSD pass parameters into the VNFs using get_input the same way a VNFD does?16:48
sripriyasridhar_ram: yes but we map it based on vnfd names provided in nsd create for vnf creation16:49
*** zengchen has quit IRC16:49
bobh_sridhar_ram: I'm not sure I understand how this is expected to work - to me it is just a collection of VNF references that use the same TOSCA conventions as the VNFDs16:49
sridhar_rambobh_: my understanding is the NSD processing logic wouldn't look / do VNFD processing.. can someone confirm if this assumption is correct ?16:50
*** zengchen has joined #openstack-meeting16:50
tbhsridhar_ram, bobh_ when we run ns-create 1)we validate the nsd16:51
*** jmckind has joined #openstack-meeting16:51
sripriyasridhar_ram: at nsd level, it is just parsing and calling the vnf-create api16:51
sridhar_ramsripriya: ack, that is my understanding..16:51
tbh2)collect the params from param file16:51
tbh3)call vnf-create with those params16:51
dkushwahasridhar_ram, bobh_ vnfd will be onboarded16:51
*** rasca has joined #openstack-meeting16:51
tbh4)complete the ns-creation16:51
sripriyafolks, quick time check, we have 8 mins left16:52
sridhar_ramso param substitution for VNFD will happen in the context of of VNF create within VNFM16:52
*** jmckind_ has quit IRC16:52
*** tommylikehu_ has joined #openstack-meeting16:52
tbhso here we are not giving NSD to heat-translator/heat16:52
sripriyai think we should continue on the tacker channel for this specific topic16:52
*** mtanino has joined #openstack-meeting16:52
sridhar_ramsripriya: sounds good..16:53
sripriyalet us quickly go through the pecan framework spec16:53
sripriya#topic Pecan framework spec16:53
*** openstack changes topic to "Pecan framework spec (Meeting topic: tacker)"16:53
sripriyadiga: ping16:53
digasripriya: Hi16:53
sripriyadiga: did you happen to chat with infra team on creating a new branch?16:53
*** neeldhwaj has quit IRC16:53
*** mtani____ has quit IRC16:53
digasripriya: I am working with infra to create seperate branch for pecan16:53
*** haleyb__ has joined #openstack-meeting16:54
sripriyadiga: also, i do not see the spec describing the design details of the framework and how existing framework is refactored16:54
digasripriya: they have shared some docs, going through those16:54
*** dbecker has quit IRC16:54
digasripriya: yes, will update the patch16:54
*** jamesdenton has joined #openstack-meeting16:54
sridhar_ramdiga: can you please fwd them, i'm curious about branch creation process16:55
digasridhar_ram: sure16:55
sripriyadiga: i believe we should first get the spec completely finished and merged  before we start creating a branch16:55
*** eharney has joined #openstack-meeting16:55
digasripriya: yes16:55
sripriyadiga: until we get a better clarity of how pecan framework will better fit for Tacker, it hard to progress forward16:56
digasripriya: okay16:56
sripriyadiga: i request you to please update the proposed solution and design details16:56
digasripriya: ok16:56
sripriyadiga: i'm thinking we should talk more about the new controllers, extensions, attribute validation and impact on existing plugins16:56
*** tommylikehu_ has quit IRC16:57
sripriyain the spec16:57
sripriyasorry here is the spec link https://review.openstack.org/#/c/368511/ for team to review16:57
sridhar_ram.. in addition to that, it would help if you can give an illustration of how new API can be added and how to write an handler in the spec16:57
digasripriya: yes, I will cover all these point16:57
sripriyasridhar_ram: +116:57
*** Patifa has joined #openstack-meeting16:58
sripriyathanks diga!16:58
digasripriya: welcome!16:58
sripriya#topic open discussion16:58
*** openstack changes topic to "open discussion (Meeting topic: tacker)"16:58
sridhar_ramFolks - here is the doodle poll for the meeting time...16:58
sridhar_ram#link http://doodle.com/poll/ee9p34kfhskd2ucc16:58
sripriyathanks for the link sridhar_ram16:58
sridhar_ramplease set to your local TZ and select all the slots you can possibly attend16:59
sripriyatime is up team16:59
sripriyathanks for joining the meeting16:59
sripriya#endmeeting tacker16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Tue Nov 29 16:59:32 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-11-29-16.00.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-11-29-16.00.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-11-29-16.00.log.html16:59
*** dmorita has quit IRC17:01
*** dmorita has joined #openstack-meeting17:01
*** fernnest has joined #openstack-meeting17:01
*** shashank_hegde has joined #openstack-meeting17:02
*** foliveira has quit IRC17:04
*** xionchen_ has quit IRC17:04
*** baoli has quit IRC17:05
*** dmorita has quit IRC17:07
*** rasca has quit IRC17:07
*** aloga_ has quit IRC17:07
*** haleyb__ has quit IRC17:07
*** Swanson has joined #openstack-meeting17:10
*** baoli has joined #openstack-meeting17:12
*** shashank_hegde has quit IRC17:12
*** frasantoro has quit IRC17:13
*** dmorita has joined #openstack-meeting17:15
*** raildo has quit IRC17:15
*** fernnest has quit IRC17:15
*** dmorita has quit IRC17:16
*** shashank_hegde has joined #openstack-meeting17:16
*** fernnest has joined #openstack-meeting17:16
*** neil_ has joined #openstack-meeting17:16
*** neiljerram has quit IRC17:17
*** liamji has quit IRC17:19
*** honza has quit IRC17:20
*** nadya has quit IRC17:22
*** chrisplo_ has joined #openstack-meeting17:22
*** honza has joined #openstack-meeting17:23
*** dmorita has joined #openstack-meeting17:23
*** honza is now known as Guest2417:23
*** hurricanerix has left #openstack-meeting17:24
*** makowals_ has quit IRC17:25
*** numans has quit IRC17:25
*** matrohon has quit IRC17:26
*** lpetrut has quit IRC17:28
*** Patifa has quit IRC17:28
*** mickeys has joined #openstack-meeting17:28
*** jgregor_ has quit IRC17:29
*** saggi has quit IRC17:29
*** krtaylor has quit IRC17:29
*** jgregor has joined #openstack-meeting17:29
*** slayer has quit IRC17:29
*** zara_the_lemur has joined #openstack-meeting17:31
*** Patifa has joined #openstack-meeting17:31
*** zara_the_lemur is now known as zara_the_lemur__17:31
*** jgregor_ has joined #openstack-meeting17:32
*** mickeys has quit IRC17:32
*** dmorita has quit IRC17:33
*** jgregor has quit IRC17:33
*** cbits has joined #openstack-meeting17:34
*** cody-somerville has joined #openstack-meeting17:35
*** cody-somerville has quit IRC17:35
*** cody-somerville has joined #openstack-meeting17:35
*** Leo_ has quit IRC17:36
*** Leo_ has joined #openstack-meeting17:36
*** dmorita has joined #openstack-meeting17:36
*** jgregor_ has quit IRC17:37
*** ljxiash has joined #openstack-meeting17:37
*** csomerville has quit IRC17:37
*** priteau has joined #openstack-meeting17:38
*** unicell has quit IRC17:38
*** cody-somerville has quit IRC17:39
*** cody-somerville has joined #openstack-meeting17:41
*** cody-somerville has quit IRC17:41
*** cody-somerville has joined #openstack-meeting17:41
*** penick has joined #openstack-meeting17:42
*** ljxiash has quit IRC17:42
*** matrohon has joined #openstack-meeting17:43
*** ygbo has quit IRC17:44
*** comay has joined #openstack-meeting17:44
*** neil_ has quit IRC17:44
*** markvoelker has quit IRC17:45
*** jdurgin1 has quit IRC17:46
*** ayoung has joined #openstack-meeting17:46
*** trandles has joined #openstack-meeting17:47
*** irenab has joined #openstack-meeting17:48
*** edtubill has quit IRC17:48
*** numans has joined #openstack-meeting17:50
*** markvoelker has joined #openstack-meeting17:50
*** dprince has quit IRC17:50
*** dprince has joined #openstack-meeting17:50
*** sshnaidm has quit IRC17:51
*** shashank_hegde has quit IRC17:51
*** numans has quit IRC17:52
*** numans has joined #openstack-meeting17:52
*** toscalix has quit IRC17:53
*** beagles is now known as beagles_brb17:53
*** strigazi is now known as strigazi_AFK17:54
*** iyamahat has quit IRC17:54
*** mickeys has joined #openstack-meeting17:56
*** yamahata has quit IRC17:57
*** henrynash has joined #openstack-meeting17:58
*** gagehugo has joined #openstack-meeting17:58
*** adiantum has quit IRC17:59
*** browne has joined #openstack-meeting17:59
stevemar__#startmeeting keystone18:00
openstackMeeting started Tue Nov 29 18:00:05 2016 UTC and is due to finish in 60 minutes.  The chair is stevemar__. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: keystone)"18:00
openstackThe meeting name has been set to 'keystone'18:00
*** adriant has joined #openstack-meeting18:00
*** neil_ has joined #openstack-meeting18:00
*** unicell has joined #openstack-meeting18:00
henrynashtally-ho, chaps18:00
stevemar__henrynash: chip chip18:00
stevemar__#agenda https://etherpad.openstack.org/p/keystone-weekly-meeting18:00
*** jamielennox has joined #openstack-meeting18:01
stevemar__pokes amakarov, 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, srwilkers, stevemar, topol, StefanPaetowJisc, agrebennikov18:01
rodrigodsstevemar__, why are you stevemar__ and not stevemar?18:01
morgan_rodrigods: he grew a tail18:01
stevemar__rodrigods: cause my bouncer and/or vm are not working18:01
rodrigodsmorgan_, you too18:01
morgan_rodrigods: because i'm lazy after reconfiguring irccloud18:01
morgan_rodrigods: and haven't typed /nick morgan18:02
stevemar__hi cbits, you're new around these parts :)18:02
*** spilla has joined #openstack-meeting18:02
*** rodrigods is now known as rodrigods_18:02
ayoungMy F25 update broke and I am on a different machine...monitoring but bouncing back and forth to try and fix18:02
cbitsYes I am..  Nice to meet you all18:02
stevemar__#topic release status18:02
*** openstack changes topic to "release status (Meeting topic: keystone)"18:02
*** Apoorva has joined #openstack-meeting18:02
rodrigods_ayoung, lol, had the same issue18:02
henrynashhi. cibts, welcome18:02
*** ralonsoh_ has quit IRC18:02
*** chrisplo_ is now known as chrisplo18:02
stevemar__just a reminder that Next milestone is Ocata-2 -- Week of Dec 12-1618:02
lbragstadcbits o/18:02
stevemar__This is also spec freeze week, specs must merge by then18:02
stevemar__such a short release :(18:03
ayoungrodrigods_, did you fix, or still dealing, too?18:03
*** morgan_ is now known as morganfainberg18:03
rodrigods_ayoung, fixed by wiping everything and re installing f2418:03
stevemar__let's try and land all the bps and bugs that touch a lot of things earlier than later18:03
*** morganfainberg is now known as morgan18:04
stevemar__#topic Spec: "Extend user API to support federated attributes"18:04
*** openstack changes topic to "Spec: "Extend user API to support federated attributes" (Meeting topic: keystone)"18:04
stevemar__rderose: ^18:04
rderoseThe problem: I have a federated user and I want to do delegation or make a concrete role assignment, however in order to do that, I need the local user ID.18:04
*** dkushwaha has quit IRC18:04
*** unicell has quit IRC18:05
rderoseAnd there is no way to query Keystone to get the user ID for federated users.18:05
rderoseLikewise, federated users don’t exist in Keystone until after they authenticate.18:05
rderoseProposal: Let's simply extend the user API to support a federated object, allowing operators to:18:05
rderoseQuery users based on federated attributes (unique_id…)18:05
ayoungrderose, so, I don't like the formate:  we should do it likethis:18:05
rderoseCreate federated users by including a federated object18:05
*** ijw has joined #openstack-meeting18:05
*** jgriffith_away is now known as jgriffith18:05
rderoseayoung: what format would you suggest18:05
ayoungidp: "name" : protocols [ ...]18:05
ayoungneed to support multiple idps and multiple protocols18:06
rderoseah, good point18:06
ayoungsomething that reflects that, linked to the same account.18:06
*** haleyb__ has joined #openstack-meeting18:06
*** tonytan4ever has quit IRC18:06
*** jmckind_ has joined #openstack-meeting18:06
ayoungother than that, you are on the right track18:06
rodrigods_don't get it... we fetch the users without having them in the backend?18:06
ayoungrodrigods_, nah18:06
*** rodrigods_ is now known as rodrigods18:06
*** tonytan4ever has joined #openstack-meeting18:07
*** rodrigods has quit IRC18:07
*** rodrigods has joined #openstack-meeting18:07
stevemar__rderose: if i make a post requet to /v3/users with federated bits in my request, it'll only create the entry in the federated_users table?18:07
ayoungrodrigods_, say a user comes in by one Idp/prtotocl, and then later  via a different one...we should see how they link back to their IDP accounts18:07
stevemar__rderose: the querying parts i don't mind18:07
ayoungrderose, does maybe it feel like this should be a separate API?18:07
*** saisrikiran has quit IRC18:07
rderosestevemar__: no, it will create a user in the user table and federated_user table18:07
stevemar__ayoung: a bit yes18:07
*** jmckind has quit IRC18:07
stevemar__rderose: two eh18:07
rderoseayoung: why not utilize the user API?18:08
rodrigodslooks like it should be a different API18:08
stevemar__rderose: why isn't that an issue?18:08
ayoungrderose, its related...but different eentities.18:08
rodrigodsat least... we are exposing how things are implemented underneath18:08
*** saisrikiran has joined #openstack-meeting18:08
lbragstadit does the same thing as a shadow user being created through the federation authentication flow18:08
rodrigodswhich usually is not a good thing18:08
rderosea federated user is a user18:08
ayoungsomething like user/<id>/idps  or something?18:08
rderoselbragstad: ++18:08
*** nadya has joined #openstack-meeting18:08
ayoungOK, for a user show...it probably is OK to have in there as is.18:09
stevemar__lbragstad: thats a better explanation :)18:09
ayoungfor affecting change...lets see what you have...18:09
rodrigodsso the problem is to create role assignments prior the user has even been authenticated?18:09
rderoseayoung: and GET /v3/users/?unique_id={unique_id}18:09
jamielennoxthis seems limiting in any situation where the saem user has more that one login method18:09
lbragstadayoung you mean it's ok to return federated attributes via the identity API?18:09
ayounglbragstad, I'm wavering... don't think it would brek anything18:09
lbragstadi don't think we've tackled the account linking story yet...18:09
rderosejamielennox: this is the opposite of limiting, this is giving operators full control18:10
ayoungOK...what if we said we don;t want it as a POST, but had to be a PUT?18:10
rderosejamielennox: POST /v3/users/{id}/federated18:10
rderose    {18:10
rderose        "federated": {18:10
rderose            "idp_id": "1789d1",18:10
rderose            "protocol_id": saml2,18:10
morganayoung: it shouldn't break anything18:10
rderose            "unique_id": "jdoe",18:10
rderose            "display_name": "James Doe"18:10
rderose        }18:10
rderose    }18:10
jamielennoxbut in which case there is the possibility on multiple federated blocks18:10
ayoungwhat if we used the OS_FEDERATED URL scheme instead?18:10
*** lpetrut has joined #openstack-meeting18:11
stevemar__ayoung: thats what i was thinking,18:11
*** irenab has quit IRC18:11
rderosejamielennox: multiple federated blocks are okay for different IdPs18:11
stevemar__can anyone think of the implications of this?18:11
rodrigodsrderose, so this is to create the user prior they authenticate, right?18:11
lbragstadjamielennox are you proposing that is how we link accounts?18:11
ayoungPUT /v3/OS-FEDERATE/idp/"1789d1",/protocol/saml2,/user_unique_id/"jdoe"   ...18:11
rderoserodrigods: yes18:11
ayoungI know, jdoe not guaranteed to be URL safe18:12
rodrigodsrderose, how can we be sure they will be correctly linked?18:12
*** Patifa has quit IRC18:12
rodrigodsi mean... once the user authenticate, it won't create a different entry18:12
jamielennoxlbragstad: no, but i'm thinking of a situation where we have linked accounts and in which case there are multiple of these per user18:12
ayoungif we  had the user ID, we could do18:12
rderoseayoung stevemar__: we could use OS_FEDERATED, but I just think lets treat federated users like any other users and stop making them special18:12
lbragstadjamielennox right18:13
*** edmondsw has joined #openstack-meeting18:13
jamielennoxalso i'm not sure i see the need for unique_id18:13
ayoungPUT /v3/OS-FEDERATE/idp/1789d1/protocol/saml2,/user_id  with a payload of  "unique_id": "jdoe",18:13
ayoung<rderose>             "display_name": "James Doe"18:13
*** mkoderer has quit IRC18:13
ayoungrderose, yes and no18:13
*** sudipto_ has quit IRC18:13
*** sudipto has quit IRC18:13
*** zul has quit IRC18:13
morganjamielennox: it is because we need the bit from the federated idp to create the mapping18:13
ayoungrderose, I want FEderation to be the dfault way we work with KEystone's identity18:13
rderoserodrigods: no, because they will already be created; once they auth, we'll pull the existing user18:13
*** agrebennikov has joined #openstack-meeting18:13
*** baoli has quit IRC18:13
ayoungI kindof hate the OS-FEDARTION part but that was not my doing ....18:13
rodrigodsrderose, how will you assure this?18:14
ayoungshould be just /idp....18:14
rderosemorgan: with this, we don't need the mapping18:14
rderoseor mapping is optional18:14
henrynashredrose: what do you mean by “pull”, you mean delete?18:14
ayoungmapping needs to be pre-set18:14
*** baoli has joined #openstack-meeting18:14
lbragstadrodrigods i think because we look up the user's federated bits and compare them to what we've already created, right?18:14
stevemar__rderose: yep, i was realizing that :)18:14
rderoserodrigods: shadow users first looks if the user exists and if they don't just pulls that user18:14
jamielennoxmorgan: yea, was looking at the second post block where you already need the id, guess it makes sense from a new user perspective18:14
rderosedoesn't create a new user18:14
ayoungI would liketo point Out that I suggested exactly this kind of API about a year ago....so, yeah, I like it.18:14
stevemar__ayoung: < 1 year ago, in austin :)18:15
*** iyamahat has joined #openstack-meeting18:15
*** diablo_rojo has joined #openstack-meeting18:15
morganstevemar__: lol18:15
stevemar__but yes, pretty much the same thing18:15
ayoungrderose, what you are looking for is something that will pre-create the user, right?18:15
rderosehenrynash: I mean, when a federated user auth, we query for that user. if they exist, we user that user ID and if they don't, we create the user18:15
ayoung2 us case: one user has never visited, 2 link new protocol to existing user?18:15
henrynashrderose: ok, got it18:16
rderoseayoung: essentially allowing operators to do manual provisioning18:16
rderosecreate user and assign role18:16
stevemar__rderose: so hows the workflow for an operator? just create all X users one time?18:16
rderosestevemar__: no, shadow mapping will create users in mass18:16
rderosethis will be for manual provisioning18:16
dstanekrderose: shaddow mapping?18:16
rderoseor even things like get me the local user ID so that I can do delegation18:16
rderosedstanek: Shadow mapping will do the auto provisioning, but I still can’t query for the user ID if I want to do delegation or make a concrete role assignment.18:17
rderosedstanek: I see this going hand-in-hand with shadow mapping. Shadow mapping allows for provisioning in mass. While extending the API, allows for other common operations, such as delegation.18:17
henrynashwhat about a create user taht takes the input expected from the IDP as parameters and then we use the mapper to generat the ID (or maybe that is what you are suggesting)18:17
rodrigodshenrynash, ++18:17
stevemar__okay, so not a total replacment for mapping engine bits18:17
rodrigodshenrynash, that approach looks safer18:17
*** Patifa has joined #openstack-meeting18:18
ayoungrderose, ok, so to link an account to an existing user, you can do that all as a single PUT, where the data is the JSON version of the assertion18:18
lbragstadmore or less another way to solve a similar problem18:18
rderosehenrynash: either way, we will generate the user ID; ideally based on the federated attributes18:18
ayoungand the URL is based on the OS-FEDERATION url scheme.  I'm OK if we drop the OS-FEDDERATION part from there though18:18
dstanekrderose: shadow mapping doesn't create multiple users at at time right? it just extends mapping to provision projects, etc?18:18
ayoungso /v3/idp  is fine18:18
rderoseayoung: cool18:18
lbragstaddstanek right18:18
dstanekrderose: it must be based on the federated attributes18:19
rderosedstanek: ah, right18:19
henrynashrderose: if we do it the way I suggested then we are guarnteed to create the same ID, irrespective of whether it was generate by first auth or by this new api18:19
ayoungsame thing for creating a user:  use a POST, I think, is appropriate there.  Then the controller and the router don't conflict with the existing user controller18:19
rderosedstanek: currently, it's uuid, but yes, it should be18:19
rderosehenrynash: agree18:19
rderoseayoung: ++18:20
ayoungfor reporting information....  are we OK changing the output of the GET user ?18:20
ayoungor should it be a separate API?18:20
lbragstadok - so regardless of how a fedearted use is created, the ID will be the same18:20
stevemar__okay, this topic has eaten enough time, rderose the spec is getting favorable feedback, lets hash out some minor bits there, look for it to get approved18:20
rodrigodsrderose, henrynash ++ that's was my concern18:20
ayoungFrom scratch I think I would be OK with a GET user...but can we be cautious here and start by just providing a new API?18:20
rodrigodsayoung, now that i understand better, i guess it should be the same API18:21
jamielennoxi dont think that makes sense with a shadow user, the shadow user id is not supposed to be reflective of a federated login info, it's just an id18:21
ayoungI can put all those comments in the review.18:21
ayoungrodrigods, related API, but different, just to avoid breaking things18:21
stevemar__ayoung: please do!18:21
*** shashank_hegde has joined #openstack-meeting18:21
*** zul has joined #openstack-meeting18:21
rderoseayoung: we won't be breaking, just extending :)18:21
rderosestevemar__ ++18:21
ayoungrderose, maybe... better safe than sorry18:22
rderoseayoung: :)18:22
stevemar__adriant: you around?18:22
*** jaugustine_ has joined #openstack-meeting18:22
stevemar__#topic Keystone MFA18:22
lbragstad#link https://review.openstack.org/#/c/34342218:22
*** openstack changes topic to "Keystone MFA (Meeting topic: keystone)"18:22
adriantpatch is here: https://review.openstack.org/#/c/343422/18:22
lbragstad^ implementation18:22
adriantThe patch itself is done, looks to have all the right things (docs release notes, etc), just needs people to play with it and test it to see how it works so they can confirm they are happy with it.18:22
adriantThere are some issues around the way I'm doing the testing (I need to test standard password auth without TOTP works), and while that works for now, other random unrelated broken tests may crop up.18:23
stevemar__adriant: that is on my list of things to do soon. FWIW it looks good18:23
lbragstadwas there a specification for this?18:23
adriantThere isn't really too much to say, I just wanted to see if there were any last minute points anyone had I've missed.18:23
dstaneklast time i looked i think it was just about done. adriant i'll look again today.18:23
*** Leo_ has quit IRC18:23
*** crinkle has quit IRC18:23
adriantlbragstad: yes18:23
lbragstadi'm not seeing one linked in the blueprint18:23
*** [HeOS] has joined #openstack-meeting18:24
adriantah, spec came after the blueprint...18:24
stevemar__lbragstad: http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ocata/password-totp-plugin.html18:24
lbragstad#link http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ocata/password-totp-plugin.html18:24
lbragstadalright - updating the blueprint18:24
*** nadya has quit IRC18:24
stevemar__adriant: can we move to your next topic?18:24
adriantyes :)18:24
stevemar__#topic Spec: User Self Management of MFA18:24
adriantas that's the odd one18:24
*** openstack changes topic to "Spec: User Self Management of MFA (Meeting topic: keystone)"18:24
adriantspec here: https://review.openstack.org/#/c/345705/18:24
stevemar__adriant: thanks for getting up early btw18:24
*** shashank_hegde has quit IRC18:25
adriantstevemar__: haha, np18:25
*** henrynash has quit IRC18:25
*** jmckind has joined #openstack-meeting18:25
adriantAfter the passwordtotp patch is merged, Keystone will have MFA support. Problem is, users have no way to make use of it without an admin creating totp creds for them. This spec is about fixing that in a manner that doesn't break things or require a huge rework, but it does add new API features on top of the existing user API (exactly the same way EC2 does).18:25
adriantThere has been some discussion about this, and if this should be a new/extended user api, or we change the credentials API. I argue against the latter as it is harder and can break things.18:25
*** dprince has quit IRC18:25
*** dprince has joined #openstack-meeting18:26
adriantmade notes just in case because it is early ^18:26
adriantSo yes, the last point, new API vs extend the credentials one is a point of contention18:26
adriantwe do need user self management for TOTP, otherwise TOTP is kind of useless as a feature18:26
dstanekadriant: so first question... this can't be done as a policy change?18:26
ayoungadriant, why is admin now required?18:26
stevemar__dstanek: that was my first question in the spec! :)18:27
*** jmckind_ has quit IRC18:27
adriantI've updated the spec itself, it sort of answers those questions.18:27
dstanekstevemar__: don't keep me in suspense. what's the answer!18:27
stevemar__dstanek: hehe, on july 22 -- i forget why18:27
adriantand there is more in the comments themselves18:27
adriantA simple policy change isn't enough18:27
lbragstadadriant because it's per resource?18:28
*** dimtruck is now known as zz_dimtruck18:28
adriantwe've need to add code to the credentials controllers18:28
lbragstadif you consider a credential a single resource in a tenant?18:28
dstanekadriant: what's the limitation?18:28
morgani really wish we could just force the system to require multiple auth plugins18:28
adrianta user owns their own TOTP credentials18:28
morganinstead of needing a new passwordtotp plugin explicitly18:28
ayoungadriant, OK, I like the "type" argument you post there...18:28
lbragstadmorgan ++18:28
*** crinkle has joined #openstack-meeting18:28
ayounglooks like the right approach18:28
morganiirc that was what we discussed when we accepted the totp plugin in the first place18:28
morganbecause... lets be fair, the auth plugins if enabled do not ensure a specific one is used18:29
morganso it becomes an all or nothing deal18:29
morganeveryone must use passwordtotp or you have to inspect the token to know if they did18:29
ayoungmordred, auth plugins should be linked to idp/protocol18:29
adriantmorgan: I agree, and have ideas on that as an approach, but it's hard to enforce. I'll put a spec together for that in future.18:29
ayounger morgan18:29
ayoungauth plugins should be linked to idp/protocol and not be a global list18:30
morganayoung: i disagree, that is too limiting18:30
stevemar__all the code would exist in the credentials layer, just the routes themselves would be /users/user_id first18:30
*** Patifa has quit IRC18:30
stevemar__adriant: ^18:30
ayoungmorgan, everything should er done via the Federation style API, just Keystone is its own IdP18:30
morganayoung: eh. i would be more inclined to say auth-plugins are user-by-user OR idp/protocol18:30
adriantstevemar__: for this spec, pretty much18:30
*** makowals has joined #openstack-meeting18:30
morganayoung: a user should eb able to require mfa not just be limited by what the protocol/idp list is18:31
stevemar__adriant: looks OK to me18:31
*** acoles is now known as acoles_18:31
stevemar__any dissenters?18:31
morganayoung: also... some users in an idp/protocol may not use this18:31
dstanekadriant: i don't quite understand why the policy would be broken based on your description. couldn't we credential format based on type?18:31
morganstevemar__: me18:31
stevemar__morgan: :O18:31
adriantit's the extra routes and serverside generation/activation that make it useful18:31
ayoungmorgabra, wouldnt OTP be another protocol?18:31
mordredwhat if a user does NOT want to use MFA?18:31
morganstevemar__: i do not like adding more plugins for this that is against the original design of the MFA inclusion18:31
mordredlike, you konw, if the user is an API-consuming automation script?18:31
morganstevemar__: this is going down the wrong path.18:31
*** hongbin has joined #openstack-meeting18:31
lbragstadso - throughout the discussion of this spec - we mentioned that there are several things about the existing credential api that prevent us from doing stuff like this18:32
* mordred interjects insanity because he accidentally got pinged18:32
adriantdstanek: it's not just policy, I want to add the generation of TOTP to the serverside18:32
*** jmckind_ has joined #openstack-meeting18:32
*** rossella_s has quit IRC18:32
morganstevemar__: we should be fixing the plugins so we can by user or by idp/protocol enforce required plugins to be used (if enabled)18:32
ayoungHeh...single use tokens!18:32
*** Patifa has joined #openstack-meeting18:32
morganmordred: you're not insane18:32
lbragstadto me, it would be easier to roadmap a way to fix what we have, clean it up, and elaborate on it later than to release yet another credential api and hope we can clean it up later18:32
morganlbragstad: that too18:32
mordredlbragstad: ++18:32
lbragstadthe latter is much harder to do in my opinion18:32
adriantbut we then can't do the serverside generation, or the enable/delete needing a passcode18:33
adriantor at least not easily18:33
dstaneklbragstad: ++ i mentioned redesign in my review. i think we need to have a clear direction instead of bolting on something else18:33
*** yamahata has joined #openstack-meeting18:33
*** allanice001 has joined #openstack-meeting18:33
morgani think the passwordtotp plugin is fundamentally the wrong approach here. we are diving down a bad direction that is now adding more credential apis18:33
*** jmckind has quit IRC18:33
dstanekmorgan: you want to have multiple auth plugins? like password and totp?18:34
morganso i dissent here and say we need to ratchet back and fix the system correctly18:34
morgandstanek: correct18:34
morgandstanek: you can do that now18:34
stevemar__morgan: you volunteering? ;)18:34
morganypou just can't enforce that multiple plugins are needed18:34
adriantmorgan, yes but not by breaking things18:34
ayoungmorgan, can you write up your objectiions?  THink they might be too big for this meeting, and I want to understand them18:34
morganmordred: ^ do I have time for this?18:34
morganmordred: :P18:34
dstanekbut you can't enforce that someone uses 2 of them. that's something we talked about in Austin (i think)18:34
adriantthis new plugin allows password+totp to with via password as normal18:35
morgandstanek: before austin18:35
adriantI'm not using the totp plugin at all, I get the totp passcode from the password itself18:35
morgandstanek: every time MFA has been brought up we said we need to enforce this.18:35
dstanekadriant: i think morgan's point is that we should need another plugin to do that18:35
adriantsticking two auth methods together means ALL the services need a separate totp passcode18:35
lbragstadyeah - i remember that discussion in austin18:35
morganwe shou;dn't need a plugin for password+totp explicitly18:35
ayoungseems like /credentials is kindof like OS-FEDERATION/idp/self/protocol/totp18:35
adriantmorgan, but the base password plugin needs to know to strip the passcode from itself18:36
morganwe should be able to say UserX NEEDS to use both totp and password plugins18:36
morganto auth18:36
adriantotherwise it fails18:36
dstaneka cloud might have 3 auth plugins required and want the user to use any 2. with this implementation that would be a lot of subclassing18:36
chrisplowell maybe user X needs these auth creds for a particular IdP18:36
lbragstadi thought i had a really detailed discussion about this with dolphm at one point... a long time ago18:36
morganbut user Y (service user) only needs password18:36
*** jgregor has joined #openstack-meeting18:37
ayoungshould be on a per domain basis18:37
morganayoung: hell npo18:37
*** e0ne has joined #openstack-meeting18:37
*** slayer has joined #openstack-meeting18:37
morganayoung: how does  rescoping work then?18:37
ayoungmorgan, project-domain?18:37
morganayoung: user or idp/protocol level18:37
adriantthere is nothing stopping us from doing that as well, my whole point with this patch was to allow totp to work with the standard default 'password' auth18:37
morgannot domain by domain18:37
lbragstadwhich boiled down to enforcing authentication factor on specific operations (ie. nova boot doesn't care how i authenticated so long as I used two separate authentication factors, like password and tongue print)18:37
ayoungyou need to use this Auth form to get access to your role assignments on D->P18:37
morganayoung: please no. please please please no.18:38
adriantthe passwordtotp plugin strips the passcode from the password, that's all. Doing that as two plugins wouldn't work easily18:38
ayoungmorgan, my goal is to make the suggestions so wild that we give up on the whole idea all-together18:38
morganadriant: in the body of the auth request you have multiple plugins specified. this works today18:38
ayoungnot really18:38
morganadriant: but we can't say you MUST use both plugins18:39
ayoungyes, that is part of the design18:39
adriantmorgan: yes, but that's not what I wanted with this, that breaks things18:39
dstanekmorgan: adriant was trying to not change the cli/horizon/etc for this18:39
*** jmckind has joined #openstack-meeting18:39
adriantmorgan we can ALSO do that18:39
*** annegentle has joined #openstack-meeting18:39
dstanekadriant: nothing is broken. things would need to be updated18:39
adriantyes, what dstanek said18:39
*** pvaneck has joined #openstack-meeting18:39
morganadriant: except if you are adding a specific plugin you can use any to auth18:39
adriantyes, but updating across multiple projects takes time, and is akin to breaking :P18:39
*** jgriffith is now known as jgriffith_away18:40
morganso you're adding yet-another-auth method and not fixing the issue we said we needed to fix when totp was added18:40
dstaneki think the plugin is reasonable, but not sufficient for the overall mfa needs18:40
*** jmckind_ has quit IRC18:40
adriantmorgan: I think we need both18:40
morgansorry, i'm on a soapbox here because we only accepted totp at all because the next step was fix the system18:40
adriantmorgan: I agree, we need a way to enforce: "these two together"18:40
morgani am against adding another plugin with the nebulous "we'll do this in the future" bit18:40
adriantbut this plugin is meant to work around that in the mean time, and allow a different password+totp auth method18:41
ayoungSo, do we have something actionable for the next week, or are we kicking this out of Ocata?18:41
morganadriant: except it is an all or nothing on the entire cloud18:41
morganadriant: if password is enabled, they can use password... circumventing totp18:41
morganeven with the new plugin18:41
dstanekmorgan: the *only* reason i see this plugin as valuable is that a cloud operator won't have control over the libraries a customer is using and they may have to not use MFA until everything works with it18:41
adriantso don't enable password? this is a replacement for password18:41
dstanekthis plugin makes it *just work*18:41
morganadriant: and then all service users cannot auth18:42
morganadriant: and keystonemiddleware is broken18:42
stevemar__morgan: if you don't have the time to do the work, can you outline what needs to be fixed to adriant ? i'm not even clear how to make multiple auth work18:42
adriantmorgan: this plugin works as a replacement for password auth just fine18:42
morganstevemar__: i can probably do this. let me land the ksa changes.18:42
*** vishnoianil has quit IRC18:42
adriantit does not break password auth without totp18:42
adriantthat was the point of it18:42
dstanekmorgan: service users can still auth... iirc the mfa is only enforced if you have a totp credential18:42
adriantit allows OPTIONAL totp auth with a password18:42
stevemar__morgan: yes, what dstanek said18:43
morganugh. it scans the db on each auth-request to see if you have a totp cred?18:43
morgandouble gross.18:43
adriantit works though18:43
adriantthe totp auth plugin does the exact same thing18:43
ayoungEven password should switch to Federation18:43
morgani'm actually really annoyed that we went down this path18:43
dstanekayoung: ++. here we debate another IdP feature18:43
morganbut i wont block it.18:44
*** dmorita has quit IRC18:44
*** unicell1 has joined #openstack-meeting18:44
morganthe only reason totp was included was because we were going to "fix" the auth mechanisms next18:44
*** dmorita has joined #openstack-meeting18:44
*** dmorita has quit IRC18:44
morganotherwise i would have held on the -2 on totp18:44
*** dmorita has joined #openstack-meeting18:44
stevemar__morgan: can you elaborate how to fix auth in -keystone after?18:44
ayoungdstanek, need a way to do "the keystone database is itself and IdP" and then the rest of this falls in to line18:44
morganstevemar__: yes it is not a hard-to-fix thing. but it requires expanding the api(s).18:45
dstanekcan we fake the password/totp split in the json payload?18:45
dstanekpassword:totp or similar format?18:45
morgandstanek: we could in horizon and the in the cli.18:45
morganheck keystoneauth could do the work for us.18:45
morganthe ksa authplugin could do the magic18:45
morganbut the enforcement on keystone side isnt' there w/o adriant's plugin and changing keystone.conf to only allow the new plugin18:46
*** s3wong has joined #openstack-meeting18:46
stevemar__adriant: stick around -keystone and chat with morgan later?18:46
lbragstadping me, too18:46
adriantthe problem is how do you make MFA optional, but enforce it on users who have it?18:46
dstanekmorgan: ++18:46
morganlike i said, i wont block this. i am lodging my dissent18:46
*** krtaylor has joined #openstack-meeting18:46
adriantstevemar__: yeah I can stick around18:46
morganadriant: i want to fix that part :)18:46
stevemar__okay, 15 minutes-ish left18:47
morganadriant: so we can make it optional/required etc.18:47
stevemar__let's move on18:47
stevemar__jgrassler: here?18:47
jgrasslerstevemar__: Yes18:47
stevemar__#topic Spec: Trust Scope Extensions18:47
*** openstack changes topic to "Spec: Trust Scope Extensions (Meeting topic: keystone)"18:47
stevemar__jgrassler: you're up!18:47
* morgan crawls back under a rock so as not to derail the meeting too much.18:47
jgrasslerThis is the spec review18:47
jgrasslertl;dr on it: I want to add an optional whitelist of capabilities to trusts18:48
jgrasslerIf that whitelist is present for a trust only the listed operations (in terms of oslo.policy targets) are allowed18:48
ayoungyeah, kill that18:49
*** penick has quit IRC18:49
lbragstadjgrassler so - i could create a trust giving you the operation to list vms on a project, but *only* list vms18:49
jgrasslerI'd do the enforcement in oslo.policy since that is where all the information about policy targets (and even concrete objects) is available18:49
ayoungtrusts are not the right abstraction18:49
jgrasslerlbragstad: Exactly, yes18:49
lbragstadjgrassler that was my next question18:49
lbragstadthis would be a cross project spec18:49
*** sshnaidm has joined #openstack-meeting18:49
jgrasslerlbragstad: Yes, it would be18:50
ayoungTHis is unworkable18:50
*** shashank_hegde has joined #openstack-meeting18:50
ayoungPlease read the proposal i have for RBAC in Middleware before you pursue this any further18:50
*** auggy has joined #openstack-meeting18:50
lbragstadayoung link?18:50
ayoungit retreads groud we've been over, and it does not work with the current abstraction18:50
ayounglbragstad, in the etherpad18:50
ayoungafter Taskmnager18:51
lbragstad#link https://review.openstack.org/#/c/391624/18:51
jgrasslerayoung: Where does it break?18:51
ayoungthe short is "there is no way to tell a user wht they need to delegate"18:51
*** Shrews has joined #openstack-meeting18:51
jgrasslerayoung: Ah, you mean they do not know the name of the oslo.policy targets?18:51
ayoungwe have 9 minutes left..too long for this meeting18:52
*** dmorita has quit IRC18:52
ayoungand the role needed for those policy targets18:52
*** tbh has quit IRC18:52
ayoungjgrassler, I had a proposal for operational scoped tokens about a year ago...fell apart on this issue18:52
*** e0ne has quit IRC18:52
*** dmorita has joined #openstack-meeting18:52
*** dmorita has quit IRC18:52
ayoungso... URL patterns18:52
dstanekjgrassler: no a backup_vm target may under the hood use other targets to do its work. what happens there?18:53
ayoungenforce RBAC on18:53
ayounggah..wrong computer18:53
*** dmorita has joined #openstack-meeting18:53
jgrasslerdstanek: Yes, that problem is unsolved, currently :-/18:53
ayoungenforce RBAC on  soemthing like  POST /v2.1/{project_id}/server/{server_id18:53
jgrasslerdstanek: It's the same issue with Barbican secret containers (they consist of multiple secrets)18:54
ayoungjgrassler, so, work with me on the RBAC stuff and we'll get to what you want18:54
*** zz_dimtruck is now known as dimtruck18:54
*** penick has joined #openstack-meeting18:55
jgrasslerayoung: But how do you get the thousands of roles this approach requires for the same granularity in place?18:55
*** saisrikiran has quit IRC18:55
ayoungjgrassler, step by step....18:55
*** electrofelix has quit IRC18:55
*** mmotiani_ has quit IRC18:55
*** saisrikiran has joined #openstack-meeting18:56
*** AJaeger has joined #openstack-meeting18:56
dstanekso in the Z release :-P18:56
stevemar__dstanek: we'll flip over by then18:56
lbragstaddstanek hopefully18:56
ayoungnah, we have something that will work based on all the restrictions18:56
jgrasslerayoung: That one is my main objection to it. It requires a _lot_ of infrastructure to be in place :-/18:56
*** rbak has quit IRC18:56
ayoungplease read through https://review.openstack.org/#/c/391624/18:56
ayoungjgrassler, believe it or not, it is the path of least resistnace18:56
*** rbak has joined #openstack-meeting18:56
jgrasslerayoung: Don't get me wrong, I like your RBAC proposal per se. But not for this purpose. At least not in 2016 :-)18:57
ayoungit is all within code that the Keystone project manages18:57
ayoungjgrassler, what you are proposing is unworkable.  You cannot enforce policy the way you propose without getting changes into every single project18:57
*** baoli has quit IRC18:57
ayoungjust look at how long bug 968696 has been open18:57
openstackbug 968696 in OpenStack Identity (keystone) ""admin"-ness not properly scoped" [High,In progress] https://launchpad.net/bugs/968696 - Assigned to Matthew Edmonds (edmondsw)18:57
jgrasslerayoung: oslo.policy would suffice.18:58
ayoungHey, assignemd to Matt...ah whatever...18:58
ayoungjgrassler, hah18:58
*** mamitchl has joined #openstack-meeting18:58
ayoung"Baby I've been here before I've seen this room and I've walked this floor I worked on this alone before I knew ya"18:58
ayoungjgrassler, lets take it off line18:58
ayoung I will be very happy to work through these things with you18:59
ayoungmeeting is almost over18:59
stevemar__we left a lot on the agenda18:59
stevemar__i'll add it to next weeks18:59
ayoungI want to get the RBAC spec in this release18:59
jgrasslerayoung: Agreed on that. I really don't want to rush through this in half a minute :-)18:59
agrebennikovthank you very much for spending 40 mins on the second topic :(18:59
ayoungplease review18:59
ayoungplease read through https://review.openstack.org/#/c/391624/18:59
stevemar__agrebennikov: happens dude18:59
morganagrebennikov: we can discuss your thing in -keystone after this meeting19:00
morgansince i have the -2 on it.19:00
agrebennikovand we have a customer online))19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Nov 29 19:00:20 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-11-29-18.00.html19:00
*** jmckind_ has joined #openstack-meeting19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-11-29-18.00.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-11-29-18.00.log.html19:00
fungiinfra team, assemble!19:00
*** browne has left #openstack-meeting19:00
morgani want to be sure you're not left hanging here. but we've gone in circles on this.19:00
fungithis week's meeting will likely be short, as there are no proposed general topics19:00
* jesusaur lurks19:01
*** adiantum has joined #openstack-meeting19:01
* jlvillal waits for startmeeting...19:01
fungii get the impression many on the team are suffering from feast holiday hangovers19:01
*** spilla has left #openstack-meeting19:01
*** jmckind has quit IRC19:02
*** Patifa has quit IRC19:03
*** edmondsw has left #openstack-meeting19:03
*** olaph has joined #openstack-meeting19:03
AJaegermorning, jhesketh19:03
fungiwell, let's get this meeting started19:03
fungi#startmeeting infra19:03
openstackMeeting started Tue Nov 29 19:03:56 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:04
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:04
fungi#topic Announcements19:04
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:04
*** haleyb__ has quit IRC19:04
fungii don't have any important announcements this week19:04
fungias always, feel free to hit me up with announcements you want included in future meetings19:04
fungi#topic Actions from last meeting19:04
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:04
*** Patifa has joined #openstack-meeting19:05
*** Patifa has quit IRC19:05
fungi#link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-11-22-19.02.log.html19:05
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x7fbb93c8f550>19:05
fungi#link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-11-22-19.02.html19:05
fungi#action fungi send summit session summary to infra ml19:05
fungii swear it's coming19:06
fungii have more than half of them written up19:06
*** Patifa has joined #openstack-meeting19:06
fungijust need to finish19:06
zara_the_lemur__the wait makes it more exciting!19:06
fungi#topic Specs approval19:06
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:06
fungi#info APPROVED "Gerrit 2.13 Upgrade" spec19:06
fungi#link http://specs.openstack.org/openstack-infra/infra-specs/specs/gerrit-2.13.html Gerrit 2.13 Upgrade19:07
*** jmckind has joined #openstack-meeting19:07
fungithat also got added as a priority effort, since there were no objections19:07
fungithough the post job hasn't finished running for that one yet19:08
fungishould show up in the priority list shortly19:08
fungii haven't approved "Zuul v3: Add section on secrets" yet since i'm unclear on whether clarkb wanted that updated19:08
fungibut we have time to work it out in this meeting19:08
fungi#link https://review.openstack.org/386281 "Zuul v3: Add section on secrets"19:09
*** jmckind_ has quit IRC19:09
zaroi'm sorta stuck on doing gerrit upgrade tasks atm, can discuss later in meeting though.19:09
fungizaro: cool, i'll add that in the priority efforts discussion shortly19:09
clarkbohai sorry got distracted but am here now19:10
clarkbfungi: I responded to your comment in -infra19:10
clarkbasid I was fine with a followup19:10
fungijeblair: follow-up to implement clarkb's requests is cool then? i'll go ahead and approve now19:10
fungithanks clarkb!19:11
*** gagehugo has left #openstack-meeting19:11
fungi#info APPROVED "Zuul v3: Add section on secrets" change19:11
*** baoli has joined #openstack-meeting19:11
*** e0ne has joined #openstack-meeting19:12
fungi#topic Priority Efforts: Gerrit 2.13 Upgrade (zaro)19:12
*** openstack changes topic to "Priority Efforts: Gerrit 2.13 Upgrade (zaro) (Meeting topic: infra)"19:12
*** iyamahat has quit IRC19:12
jeblairfungi: yes, i will implement at least one of those suggestions; i will give the one which is slightly redundant a shot but no promises.  :)19:12
*** raildo has joined #openstack-meeting19:13
zaroi'm sorta stuck on this change, #link https://review.openstack.org/#/c/3867419:13
jeblairthat number doesn't look long enough19:13
*** matrohon has quit IRC19:14
zaroright, it's #link https://review.openstack.org/#/c/38674519:14
fungi#link https://review.openstack.org/386745 Allow zuul launcher and scheduler on the same host19:14
zaroso i'm trying to setup zuul-dev so that we can test new gerrit with a zuul CI In place.19:15
*** skelso has joined #openstack-meeting19:15
zarohad a discussing with nibalizer yesterday about changes to puppet-openstackci to make that work which may cause problems for downstream.19:16
zarowould like to get other people's opinions about this19:16
pabelangermaybe it is just easier to stand up separate dev servers?19:16
*** brault_ has joined #openstack-meeting19:16
pabelangermoving our configs to a single host, is a lot of code churn19:16
clarkbpabelanger: zaro but openstackci is already supposed to support all in one aiui19:17
clarkbso its a bug that should be fixed regardless19:17
fungibut we purposely didn't implement zuul-launcher support in it, i thought19:17
pabelangerclarkb: there is some issues with zuulv25 things19:17
zaroclarkb: fix in openstackci?19:17
nibalizeryah the issue is the decision not to support z2.5 imho19:17
clarkbfungi: is that the only piece that isn't working?19:17
nibalizerputs openstackci in a weird spot19:17
pabelangerwhich, if we land in openstackci, will break system-config19:17
clarkbpabelanger: not sure I follow19:18
pabelangerwe can fix it in openstackci, but will be a lot of chrun19:18
nibalizerbecause previously we said that we'd keep openstackci running what we run19:18
mordredyah. I agree that is awkward19:18
jeblairwe can move it into openstackci.  but i still don't think we should recommend anyone use it.19:18
pabelangerwas a WIP for zuul_launcher in openstackci19:19
fungiaiui, the challenge comes from directly instantiating zuul::launcher in openstack_project but instantiating other puppet classes for zuul through the openstackci module19:19
pabelangerbut was abandoned19:19
*** brault has quit IRC19:19
*** saisrikiran has quit IRC19:20
jeblairso if it will help, let's move it into openstackci.19:21
nibalizerif openstackci can hold launcher stuff, it gets easier to write it I think19:21
nibalizeri do think it will help jeblair19:21
*** lpetrut has quit IRC19:21
nibalizermaybe we leave the default to be jenkins, then we add some flags that turn on a launcher19:21
jeblairyep.  with a comment saying don't do that.  :)19:22
nibalizerand infra uses that on the zuul launchers, and in zaros allinone test node19:22
jeblairdo not press big red button19:22
nibalizerno one ever does that :P19:22
pabelangerI'll be around to help with the move19:23
zaroi'm going to trust that it will help19:23
zarohow would that look on system-config side?  just call into openstackci pieces to setup zuul?19:23
*** ykatabam has quit IRC19:23
nibalizerfor the dev node or for the launchers?19:24
zaroone in prod mode and one in test mode?19:24
zaroI mean how does that seperation work with zuul_dev.pp and zuul_prod.pp?19:24
pabelangerzaro: we should be able to follow same steps for zuul_merger, but using zuul_launcher19:24
*** nadya has joined #openstack-meeting19:25
pabelangerthen add openstackci::zuul_launcher into zuul_dev.pp19:25
*** asselin_ has joined #openstack-meeting19:25
fungii guess some of the confusion is also around how to serialize the needed changes between the different puppet modules19:25
pabelangerif we leave zuul_prod.pp alone for now, that will be less disruption19:26
fungior has that been addressed now?19:26
*** jaugustine_ has quit IRC19:26
*** nadya has quit IRC19:26
nibalizerand we write openstackci:::zuul_launcher so that it can co-exist with openstackci::zuul_scheduler19:26
*** nadya has joined #openstack-meeting19:26
clarkbfungi: I don't think its an issue, if you don't explicitly use openstackci::zuul_lajuncher its a noop19:26
fungigood point19:27
clarkbfungi: which will let our existing code behappy, whcih we can then switch over to use openstackci::zuul_launcher19:27
nibalizeryah i dont expect us having to change zuul_prod.pp at all19:27
fungii guess that directly addresses it anyway19:27
*** oshidoshi has joined #openstack-meeting19:27
*** mmotiani_ has joined #openstack-meeting19:27
*** ijw has quit IRC19:28
nibalizeroh now i see what clark is saying19:28
nibalizerthere should be a change to the launchers puppet, yes, but it shouldn't change the daemon19:28
fungianything else need covering on the gerrit upgrade prep at this point?19:29
fungizaro: are you all squared away on what you need for the puppet end of this?19:30
zarowill pabelanger work on the needed zuul_launcher change?19:30
*** e0ne has quit IRC19:30
zarohis wip change19:30
zaroor abandoned i guess19:30
pabelangerI can help get it landed19:31
pabelangerdon't mind doing it19:31
*** haleyb__ has joined #openstack-meeting19:31
zarocool, thanks!19:31
*** jgregor_ has joined #openstack-meeting19:31
*** oshidoshi has quit IRC19:32
*** penick has quit IRC19:32
fungi#action pabelanger add openstackci::zuul_launcher puppet class19:32
*** e0ne has joined #openstack-meeting19:32
fungithat cover it?19:32
zaroi think so.19:32
fungithanks zaro, pabelanger, nibalizer, clarkb et al!19:33
*** jgregor__ has joined #openstack-meeting19:33
fungi#topic Open discussion19:33
*** fguillot has quit IRC19:33
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:33
fungianybody have anything off-agenda to bring up this week?19:33
pabelangerwe had an outage of ask.o.o over the weekend19:34
fungiahh, yep. so we did19:34
*** penick has joined #openstack-meeting19:34
pabelangerHDD space issue19:34
*** fguillot has joined #openstack-meeting19:34
pabelangerbetween apache and jetty, about 30GB of logs19:34
fungithere's a bigger outstanding issue with ask.o.o... there's an outstanding upgrade to newer askbot19:34
mordredI recommend we stop running out of disk19:34
pabelangerif anybody knows jetty, would love some help how to reduce the log levels for it19:34
*** jgrego___ has joined #openstack-meeting19:34
fungii approved it, didn't work i think because there's some issue with the deployment automation for it, so had to roll it back19:34
*** jgregor has quit IRC19:35
clarkbfungi: for that issue at least we should probably just use vcsrepo19:35
fungii'm not entirely unconvinced the uptick in jetty log volume could be related19:35
clarkbits what we use everywhere else because ~vcsrepo has never worked for us19:35
clarkber !vcsrepo19:35
*** haleyb__ has quit IRC19:36
fungiyeah, i think the commit history in the puppet-askbot repo indicates that the switch from vcsrepo to git provider was an attempt to solve an issue/shortcoming with vcsrepo19:36
fungi#link https://review.openstack.org/235389 Refactor vcsrepo to git resource to resolve refresh trigger issues19:36
*** jgregor_ has quit IRC19:36
fungivcsrepo was retriggering deployment on every run or something19:37
*** nadya has quit IRC19:37
*** jgregor__ has quit IRC19:37
fungitrying to ensure a specific git ref caused it to notify each time the resource was evaluated, if memory served19:37
fungimrmartin may remember more detail19:37
*** vishnoianil has joined #openstack-meeting19:38
*** arxcruz has quit IRC19:38
mrmartinyeah, we had some issues with vcsrepo19:38
fungidiscussing the decision from a year ago to switch from vcsrepo to git resource for puppet-askbot19:38
fungiwhich in turn seems to have the opposite problem of not notifying when the ref changes19:39
mrmartinsome features was missing from git resource as I remember19:39
mrmartinwas / were19:39
*** lin_yang has joined #openstack-meeting19:40
fungiyeah, it appears that ensuring a specific git ref with vcsrepo notifies other resources every time it's evaluated, and ensuring a specific git ref with the git resource fails to notify other resources when the git ref changes19:40
clarkbso vcsrepo triggers things on ever run, current thing doesn't actually update the git repo?19:40
mrmartingive me a min I can check the task history.19:41
mordredclarkb: it updates the git repo but doesn't notify anything else that the git repo changed19:41
mordredclarkb: so actions that trigger when the git repo changes don't fire19:42
fungiyeah, now i don't remember which of those it ended up being19:42
fungii'd have to go back to my post-mortem in the irc logs from when i rolled things back19:42
clarkbah ok so I misunderstood when this was debugged before and thought the git repo didn't update19:42
fungimrmartin: the reason this is coming up though is that we've (suddenly?) started running out of disk space in the last few weeks, and jetty logs look to be what's mostly filling up the filesystem19:43
mordredclarkb: I could also be massively wrong - it's easy to get backwardsed on this19:43
fungithough i don't think anyone has yet looked into why jetty is logging so much lately19:43
jeblairyeah, it looks like nb01 installs nodepool every puppet run19:43
mrmartinwe are using jetty for apache solr19:43
jeblairso vcsrepo appears to do that when you give it a branch at least19:44
fungimrmartin: right, i was wanting to rule out the recent failed and rolled-back upgrade as a cause19:44
mrmartinbut the current solr version seems to be deprecated, but upgrade requires a larger architectural change of solr deployment.19:44
mrmartinvcsrepo had a bug, and that was the reason that we change for this git resource19:45
fungimrmartin: and if the volume of jetty logging isn't indicative of a deeper problem, we probably just need to look into how to scale back on its retention or configure it to compress its logs when it rotates them19:45
jeblairoh wait, i think i may be wrong about that19:45
jeblairi see puppet runs where nodepool was not installed19:45
mrmartinfungi: yeah as a first step, it is a great idea. I don't have access to the ask.o.o site just for the dev one, and it is not reproducing the same issues due to much lower traffic.19:45
jeblairmordred, clarkb, fungi: so it looks like vcsrepo, given a branch, does not install on every pulse.19:46
mrmartinsomeone had time to check what the heck is jetty logging?19:46
fungimrmartin: i can get you some jetty logs after the meeting if you have an opportunity to look at them19:46
mrmartinok, I can check it19:46
*** ljxiash has joined #openstack-meeting19:46
fungii'm pulling some up now19:47
mrmartinmaybe we just simply need to decrease the log level, and add logrotate19:47
pabelangerhow do you do that?19:47
*** lezbar has quit IRC19:47
pabelangerbecause we need to puppet it19:47
fungilots of info lines about things like "org.apache.solr.core.SolrCore  - [core-en] webapp=/solr path=/select/ params={fl=*+score&start=390&q=(vnc)&wt=json&fq=django_ct:(askbot.thread)&rows=10} hits=489 status=0 QTime=0"19:47
fungilooks like maybe performance stats?19:47
*** nadya has joined #openstack-meeting19:48
fungii honestly don't know enough about jetty and solr to be able to say for sure, but the fact that they're pretty much all at info loglevel suggests they're benign anyway19:48
fungiso maybe jetty can be configured to compress when it rotates19:49
pabelangerthink it can19:49
mrmartinyeap, let's try that first, at INFO level it mustn't flood the logs19:49
mrmartinhow quickly it fills up the disk?19:49
ianwwow xml config files are fun19:50
*** nadya has quit IRC19:51
*** adriant has quit IRC19:51
*** ljxiash has quit IRC19:51
fungimrmartin: looking for a graph, just a sec19:51
fungimrmartin: http://cacti.openstack.org/cacti/graph.php?action=view&local_graph_id=2547&rra_id=all19:52
*** jgrego___ has quit IRC19:52
fungi#link http://cacti.openstack.org/cacti/graph.php?action=view&local_graph_id=2547&rra_id=all ask.openstack.org - Used Space - /19:52
mrmartinoh ok, thanks19:52
fungilooks like a few weeks ago it ramped up pretty quickly19:52
bswartzianw hope you're being sarcastic19:52
fungimrmartin: those sawteeth are from where we deleted some older logs manually each time it filled up19:53
*** Leo_ has joined #openstack-meeting19:53
*** ociuhandu has quit IRC19:53
fungimrmartin: and when / gets full and puppet tries to redeploy askbot for whatever reason, it leaves it in a half-installed state and then the service falls offline apparently19:53
fungieach of those incidents was followed by trying to figure out which libraries to manuallt reinstall with pip to get things working again19:54
*** ljxiash has joined #openstack-meeting19:54
pabelangerone day, when we roll DIBs for control plane server, we should have a different mount for /var/logs :)19:55
pabelangerso that doesn't happen19:55
*** jgregor has joined #openstack-meeting19:55
*** jgriffith_away is now known as jgriffith19:56
*** cdent has joined #openstack-meeting19:56
*** slaweq_ has quit IRC19:57
fungiokay, we're coming up on the end of our timeslot. any last-minute items?19:57
*** rfolco has quit IRC19:58
clarkbtranslate-dev still nto working19:58
clarkber on xenial19:58
clarkbwill try to poke at that more later this week19:58
*** ljxiash has quit IRC19:59
clarkbalso puppet + systemd is19:59
clarkbhow to put it nicely19:59
clarkbnot great19:59
* fungi is unsurprised19:59
fungiokay, that's time. thanks everyone!19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:59
openstackMeeting ended Tue Nov 29 19:59:56 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-11-29-19.03.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-11-29-19.03.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-11-29-19.03.log.html20:00
fungitake it away, ttx20:00
ttxwho is around for the TC meeting ?20:00
* edleafe lurks in the back20:00
ttxdhellmann, dims, flaper87, mordred, stevemar: around ?20:00
ttxsdague and thingee are excused20:00
* mtreinish remembers dst this week20:00
lbragstadttx i can step in for keystone stuff if you need anything from keystone this week20:01
*** mamitchl has left #openstack-meeting20:01
*** unicell1 has quit IRC20:01
dimsttx : am here right now may drop off soon to head home20:01
ttxWe have quorum20:01
ttxI suspect flaper87 will join us20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue Nov 29 20:01:39 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: tc)"20:01
openstackThe meeting name has been set to 'tc'20:01
ttxHi everyone!20:01
ttxThanks to dhellmann for chairing last week20:01
ttxOur agenda for today:20:01
dhellmannmy pleasure20:02
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:02
ttx(remember to use #info #idea and #link liberally to make for a more readable summary)20:02
stevemar__mtreinish and i were sippin' lattees in montreal last week20:02
ttx#topic Add project Octavia to OpenStack big-tent (final discussion)20:02
*** openstack changes topic to "Add project Octavia to OpenStack big-tent (final discussion) (Meeting topic: tc)"20:02
*** rockyg has joined #openstack-meeting20:02
ttx#link https://review.openstack.org/31305620:02
EmilienMship it :)20:03
ttxThis was discussed last week, I couldn't spot any strong objection in the logs20:03
ttxFeels like it's mostly reflecting a change that has already happened20:03
stevemar__EmilienM: ++20:03
ttxMy only concern is with the timing: you mention the transition is to be completed in Ocata.20:03
ttxdougwig: ocata-2 is Dec 15, ocata-3 is Jan 27 -- how early do you think you can complete that ?20:03
dhellmannyes, that was my only concern, too20:04
*** rockyg has quit IRC20:04
dhellmannif the transition doesn't happen quickly enough, what portion of octavia is part of "newton" or not?20:04
* mtreinish is still surprised by how short the cycle is :)20:04
ttxdhellmann: I guess given the cycle is short it can be done for ocata-3 ?20:04
*** rockyg has joined #openstack-meeting20:04
* dhellmann checks the release model for octavia20:04
flaper87mtreinish: no kidding20:05
dougwigwe're going to try, but the staffing changes hit us as well. worst case, it finishes in P, and the end user API via neutron is not affected. we currently expect it to be done.20:05
johnsomWe are actively working on the neutron-lbaas/octavia merge, but I think that is a bit independent of the governance change as we are actively managing compatibility via neutron.20:05
dhellmannttx: it's cycle with intermediary, so as long as they have a final release I guess I'm OK with including it in newton20:05
ttxdougwig: in that case you would just publish neutron-lbaas ?20:05
johnthetubaguyI thought octavia already released things last cycle, so worst case it is similar this cycle?20:05
johnthetubaguyjohnsom: +120:05
dougwigttx: aye.20:05
*** ociuhandu has joined #openstack-meeting20:05
*** bobmel has quit IRC20:05
ttxmakes sense to me, thx for the precision20:06
dhellmannok, that sounds fine20:06
ttxOK, no more objections from me, anyone else ?20:06
dougwigi expect both neutron-lbaas and octavia to be required as packages in O, since the former will have the api proxy for backwards compat.20:06
dimsno objections20:06
* flaper87 steals ttx's magic wand and approves Octavia20:06
johnsomdougwig +120:06
ttxshould we get formal approval from armax ?20:06
dhellmannI just realized I said newton when I meant ocata20:07
flaper87ttx: he was active in the review already20:07
ttxsure, but not formal +120:07
dhellmannit seems reasonable to wait for a +1 from armax, but then to let ttx approve as soon as that happens20:08
dhellmannwithout having to go through another meeting review20:08
flaper87works for me20:08
dougwigif you need that, ok. but we have had many conversations with armax, so i'm not worried.20:08
*** galstrom is now known as galstrom_zzz20:08
dhellmannyeah, this is mostly to ensure the record is clear for posterity20:08
fungiyeah, he chimed in on last week's tc discussion as well20:08
ttx#agreed since neutron-lbaas is thorically in neutron currently, waiting for a formal +1 from armax, but ttx is clear to approve as soon as that happens20:08
johnsomYeah, armax is very supportive of this, but I am fine waiting for the rubber stamp.20:08
*** unicell1 has joined #openstack-meeting20:09
fungii can't find thorically in my dictionary20:09
ttxhe might chime in during the meeting20:09
*** allanice001 has quit IRC20:09
*** galstrom_zzz is now known as galstrom20:09
*** bobmel has joined #openstack-meeting20:09
ttxfungi: it involves a hammer20:09
dhellmannfungi : isn't the thoric the middle section of an insect?20:09
* fungi is duly schooled20:09
ttxAlright, let's move on20:10
ttxdougwig, johnsom: consider it almost-done :)20:10
johnsomGrin, thanks!20:10
mordreddhellmann: s/ic/ax/20:10
dhellmannmordred : my joke was not as funny as ttx's20:10
*** gordc has joined #openstack-meeting20:10
ttx#topic Reference doc for new language additions20:10
*** openstack changes topic to "Reference doc for new language additions (Meeting topic: tc)"20:10
ttx#link https://review.openstack.org/39887520:11
ttxflaper87: want to introduce the topic ?20:11
*** cbits has left #openstack-meeting20:11
* dims has to drop off :(20:11
*** olaph has left #openstack-meeting20:11
ttxdims: bye!20:11
stevemar__ttx: great blog a few days ago btw (myth #1 touched on the topic)20:11
flaper87So, I started this by doing a brain dump on my blog and then cleaned the brain dump a bit and wrote it down in the form of a reference document. This is very much a draft that I'd lie us to go over and clean up a bit20:12
flaper87So, the current proposal is a 2-phase process20:12
ttxstevemar__: thx!20:12
flaper87the first phase is to discuss the needs of a new language and why the currently supported languages are not good enough20:12
*** auggy has left #openstack-meeting20:12
flaper87the second phase involves addressing the set of requirements listed in the proposal20:13
*** myoung is now known as myoung|brb20:13
flaper87I intentionally kept the bar high in the proposal because I want us to think about things that new languages should/shouldn't support before OpenStack adopts them20:13
flaper87we can remove and/or add new requirements to the proposal20:13
flaper87there have been some comments on it already from various folks20:13
dhellmannI like the 2 phase structure20:14
ttxmordred: you still have a blogpost queued to recount the javascript experience20:14
flaper87I think one of the main objections is that it's too much work in advance20:14
*** lpetrut has joined #openstack-meeting20:14
ttxdhellmann: yes, I like the idea of making people part of the solution, rather than proactively block progress20:14
*** beagles_brb is now known as beagles20:14
flaper87Now, I also want to mention something that has come up a couple of times20:15
ttxflaper87: we could relax the oslo part -- I don't think a team that is not using some oslo lib would have to front the cost for a lib (or go equivalent) they would not use20:15
flaper87There's a feeling that this proposal is not allowing for people to experiment and that it adds new requirements without having added the language yet. In my opinion, we've experimented with the process already and we did that with python20:16
flaper87sure, different times and a single language but we learnt from that process20:16
johnthetubaguyyeah, I am mostly +1 all the requirements except the oslo libs (we need a way to create such things though)20:16
ttxflaper87: in the past we allowed experiments in feature branches and/or unofficial repos20:16
edleafettx: but if they did implement a common thing that oslo implements, they should make it a lib/whatever to help future work in that language20:16
ttxedleafe: right20:16
flaper87ttx: johnthetubaguy ++ I don't have a good formula to figure out what libs (if any) should be required20:16
johnthetubaguyso, I think if we talk more about the why in the process, many peoples fears will go away20:16
dhellmannI don't think we need to say that all of the oslo libs need to be reproduced, but I do think we need to say that something like config should be done in a way consistent to openstack, not necessarily consistent to the language ecosystem20:17
edleafeflaper87: logging comes to mind as a start...20:17
dtroyerdhellmann: ++20:17
stevemar__dhellmann: i like that20:17
johnthetubaguyflaper87: there is a good point there, its hard to prove you can have a shared lib, if we don't try it... but hey.20:17
edleafedhellmann: yes20:17
ttxdhellmann: yes arguably log/config could be upfront. messaging, maybe first-user20:17
*** slaweq_ has joined #openstack-meeting20:17
ttxsame for oslo.db20:17
morgandhellmann: as long as the understanding is that if the openstack-consistent way can be done without an additonal lib, it should be fine.20:17
dhellmannttx: right20:17
flaper87edleafe: right, so far I think I have logging and config but that's probably subjective20:17
dtroyeralso, the same sort of thinking that got us to olso in the first place should be expected, for things that didn't need an oslo lib in Python but might in naother language20:17
dhellmannmorgan : I'm not sure what that means?20:18
morgandhellmann: some languages don't need the extra mechanisms oslo.config provides to provide an equivalent.20:18
dhellmanndtroyer : ++20:18
edleafeflaper87: true, but requiring that o.vo be implemented is crazy talk20:18
morganricher base (stdlib) style support20:18
flaper87dtroyer: right, that's my thought as well20:18
flaper87edleafe: oh sure20:18
morganthats all.20:18
stevemar__edleafe: yep20:18
ttxand frankly, we had a lot of people complaining that "the TC doesn't want go", and telling those that they can be part of the solution in implementing goslo.config... could turn the table around20:18
dhellmannmorgan : I would be surprised to find another language with an implementation of the things that oslo.config does in a way that is compatible with oslo.config for doc generation, etc. There are a lot of ways to read INI files, but that's only one feature of that library.20:19
EmilienMdhellmann: +1 with config. It's a good start helpful for our operators20:19
flaper87TBH, if it can be proved that stdlib of language X does the same thing without having to add 10 modules to each project, I guess it's fine20:19
flaper87dhellmann: ++20:19
morganflaper87: exactly20:19
morganthat is all i was pointing out20:19
edleafeflaper87: good point20:20
morgandon't force a lib if it is demonstrobly proven to already exist20:20
*** priteau has quit IRC20:20
flaper87the point is, it needs to be proven.20:20
dhellmannI'm not even certain we need to require something like oslo.messaging -- that's a layer I think we might say works differently in different languages20:20
morganflaper87: ++20:20
ttxdhellmann: right20:20
morganoslo.config might have been a bad choice...20:20
*** priteau has joined #openstack-meeting20:20
morganoslo.messaging might have been a better example (as highlighted by dhellmann )20:20
fungiit seems much more like an attempt to avoid a return to the old nova code copies, openstack/common, oslo-incubator...20:20
mordredttx: yes - the javascript blogpost is coming up20:21
edleafedhellmann: in that case, they should demonstrate the reason why messaging isn't applicable20:21
johnthetubaguyright, the bit about being able to create shared libs, as needed, seems way more important20:21
ttxfungi: yes, I'm actually more interested in having the mechanism to share, rather than exact bits of code20:21
ttxwhat johnthetubaguy said20:21
flaper87johnthetubaguy: indeed and I think that's in the current draft already20:21
dhellmannfungi : also to avoid having diverging implementations where different pieces of openstack have different deployment needs based on their language20:21
dhellmannedleafe : we can argue about the bad patterns in oslo.messaging another time :-)20:21
johnthetubaguyflaper87: +1 I love that bit20:21
fungiwe continue to experience it in our python-based projects, so i don't know that we can completely get in front of it with any other language either20:21
ttxAnd I'll only approve it if it's named goslo20:21
edleafedhellmann: :)20:22
stevemar__ttx: not lillehammer?20:22
edleafettx: I read that as 'go slo(w)'20:22
*** slaweq_ has quit IRC20:22
mordredstevemar__: gillehammer20:22
* ttx looks up norwegian cities starting with g20:22
*** bobmel has quit IRC20:23
flaper87so, would people be ok with having a clause on the oslo topic saying that if there are compatible implementations for oslo.config and oslo.log then those don't need to be implemented?20:23
*** baoli has quit IRC20:23
flaper87of course, that needs to be proven and tested, I guess20:23
*** slaweq_ has joined #openstack-meeting20:23
fungiflaper87: yes. take pbr as a (relatively early) example... we have plenty of libraries that share solutions for common problems in python20:23
ttxflaper87: ok, so it looks like you're on a good path here, but as always people will nitpick more when we get to  more details20:23
*** bobmel has joined #openstack-meeting20:23
fungithe common problems in go may not be the same set of problems20:23
dhellmannflaper87 : the part I would want for oslo.log is the config layer that gets the underlying logging machinery to produce output like other openstack services20:23
mordred"how does dependency management and stable branch maint work" and "how do dependencies get mirrored/pre-cached for the gate" are the ones that are going to be harder, to be quite honest20:23
*** baoli has joined #openstack-meeting20:23
johnthetubaguyflaper87: do you think adding more about why in the process would help worry about the concerns about the innovation side of things?20:24
flaper87dhellmann: I can use that as an example for oslo.log in the ref doc20:24
ttxflaper87: did you have further questions that you need answers on before you can produce another draft ?20:24
mordredwriting code is a thing there are tons of people who love to do - so saying "we need some libraries written in $language" is unlikely to get much pushback20:24
dtroyerflaper87: that's why I suggested taking a different perspective and trying to ensure that the externals remain consistent, and getting there informed by what we learned with oslo20:24
flaper87johnthetubaguy: yeah, I'm planning to do that too :D20:24
flaper87ttx: nope, tbh, I'd like to hear from other folks (especially folks that were involved in the previous golang discussions notmyname *hint*)20:24
mordredespeically since the libraries in question have well defined semantics20:24
flaper87other than that, I'm good for now and I've amends to work on20:25
flaper87dtroyer: ++20:25
johnthetubaguyflaper87: cool its that, so you have a prototype, you can save man years using this new language, help me understand the cost of not using python, well here you go, etc20:25
ttxflaper87: if you want specific feedback you might want to reach out more directly20:25
mtreinishjohnthetubaguy: was that a go pun? :)20:25
flaper87ttx: yup, added some of these folks to the review, I'll go in crazy ping mode next20:25
johnthetubaguyheh, it wasn't meant to be20:25
mordredyes. that20:26
*** priteau has quit IRC20:26
ttxbecause unicode ftw20:26
mordredplease god call it that20:26
*** priteau has joined #openstack-meeting20:26
* flaper87 is done, fwiw20:26
ttxflaper87: thx!20:26
ttxmoving on to next topic then20:26
stevemar__thx for leading this flaper8720:27
flaper87my pleasure20:27
ttx#topic Add project Zun to OpenStack big-tent (initial discussion)20:27
*** openstack changes topic to "Add project Zun to OpenStack big-tent (initial discussion) (Meeting topic: tc)"20:27
ttx#link https://review.openstack.org/40222720:27
hongbino/ for zun-related question20:27
ttxhongbin: o/20:27
ttxI'l do a quick intro20:27
ttxAs you may know, Magnum used to have COE-provisioning features and container-lifecycle features20:27
ttxSince those are actually targeting two different use cases, a number of us advocated for separating the two sets20:27
ttxMagnum retained the COE-provisioning abilities, and Zun was formed to host the container-lifecycle abilities20:28
ttxSo this is more of a project split than a new project, in my view20:28
ttxThat said I'm happy that hongbin took the time to completely set up the project and team separately before applying20:28
ttxif anything that makes it even easier to make a call here20:28
*** myoung|brb is now known as myoung20:28
ttxI'll go on record saying I'm still unconvinced this approach has potential, but I'll fight to give them the chance to prove me wrong20:29
ttxComments, objections ?20:29
johnthetubaguysame actually20:29
mtreinishso I did have a question in the review about how they seem to have a nova driver in tree20:29
dhellmannmtreinish , dims : there was a question about a "nova" tree in the zun repo20:29
mtreinishI'm curious if that's just a temp thing or a long term direction20:30
hongbinmtreinish: we have a driver that copied nova-docker code as a starting point20:30
mtreinishbecause I don't think we want to encourage projects to use unstable unsupported interfaces from other projects20:30
fungidims seems to have addressed it half an hour ago20:30
dhellmannyeah, I think from a packaging perspective we'd want that part of the tree renamed to avoid colliding with the regular nova tree20:30
armaxttx: done20:30
hongbinmtreinish: the rational is to avoid duplicate what nova was doing20:30
ttxarmax: great thanks!20:30
johnthetubaguymtreinish: +1, although I wouldn't block on that I guess20:31
*** Patifa has quit IRC20:31
dhellmannno, it's not a blocker, just pointing out some potential issues with packaging and deployment20:31
ttx(dougwig: octavia approved!)20:31
*** Swami has joined #openstack-meeting20:32
mtreinishdhellmann: well it's a bit more than than that to me. It's more that it feels like we're sanctioning doing something the wrong way20:32
*** Patifa has joined #openstack-meeting20:32
mtreinishwhether that's actually the case or not20:32
hongbinok, i will discuss the packaging and deployment issue with the team20:32
hongbinthanks for the feedback20:32
mtreinishbut I agree it's not really a blocker20:32
dougwigttx: ty!20:32
johnthetubaguyhongbin: nova doesn't really support out of tree drivers, because that interface isn't stable, its worth knowing20:33
hongbinjohnthetubaguy: ack20:33
ttxthat makes zun a bit brittle, basically20:33
johnthetubaguyI am curious why the COE is not created by magnum, but thats a separate conversation I guess20:33
*** pvaneck has quit IRC20:33
*** edtubill has joined #openstack-meeting20:34
*** edtubill has quit IRC20:34
mtreinishttx: that's why I brought it up. Because if that's the long term direction to do that it raises some flags20:34
*** pvaneck has joined #openstack-meeting20:34
*** bobh_ has quit IRC20:34
fungiyeah, the docker driver's checkered past should serve as a signpost20:34
ttxmtreinish: good catch20:34
ttxShall we wait until next week to finally approve as usual, or should we fast-track it since it's more of a project split ? (and it has already the required approvals)20:35
ttxI'm fine letting it bake for the week to give others a chance to comment20:35
ttxbut also fine approving it now since there is nothing that forces us to do it in two meetings20:36
fungii'm fine with immediate approval on this one20:36
dhellmannI agree, we can go ahead20:36
fungilooks like we already have rc x10 on this20:36
ttxalright then, let's win some precious minutes and not force hongbin to get up next week at very early hours20:37
ttxhongbin: welcome back!20:37
hongbinthanks all for reviewing the application20:37
hongbinttx: thx!20:37
ttxlet's move on to next topic...20:38
ttx#topic Visions for the TC and OpenStack20:38
*** openstack changes topic to "Visions for the TC and OpenStack (Meeting topic: tc)"20:38
ttxjohnthetubaguy started two documents to work on visions for the TC and OpenStack:20:38
ttxAdd a draft TC vision structure: https://review.openstack.org/40122520:38
ttxAdd a draft OpenStack technical vision: https://review.openstack.org/40122620:38
*** priteau has quit IRC20:38
*** pvaneck has quit IRC20:38
ttxI commented that those are not visions (yet) -- and I'm not convinced Gerrit changes are the best way to get to something we can all review20:38
ttxI would rather collaborate on an etherpad for fast iterations / brainstorming, but I'm fine leaving the choices of weapons to whoever is pushing it :)20:39
*** priteau has joined #openstack-meeting20:39
johnthetubaguyyeah, so I wanted to get something down for us to discuss20:39
*** sambetts is now known as sambetts|afk20:39
johnthetubaguyI guess the first thing, is the TC vision20:39
ttxAlso I would rather not do both in parallel :)20:39
ttxthere is only so many cans of worms you can hold open at the same time20:40
johnthetubaguyyeah +1 that20:40
mordredbah. we can hold SO MANY CANS of worms20:40
dhellmannit's useful to have both to make the scope of each clear, but I agree that it'll be easier to work on them one at a time20:40
johnthetubaguythese patches are really just me thinking out loud20:40
johnthetubaguyyeah, I think the TC vision could include, we should create an OpenStack vision20:40
johnthetubaguybut yeah, the scope is a bit clearer in my head now20:41
johnthetubaguyso the TC vision, do people think we should start with that one?20:41
johnthetubaguyand do people agree that would be useful?20:41
ttxjohnthetubaguy: "we created a vision for openstack", you mean :)20:41
*** allanice001 has joined #openstack-meeting20:41
*** Shrews has left #openstack-meeting20:41
johnthetubaguyttx: true, true20:41
dhellmannjohnthetubaguy : yes, I think it makes sense to start small and focus on a tc vision20:42
johnthetubaguyttx: I added a new patch on the TC one to have more vision-ey bits in it20:42
*** slaweq_ has quit IRC20:42
johnthetubaguyso the personal struggle I have is wanting to point the general direction we are going20:42
ttxjohnthetubaguy: you weren't at the Ann Arbor training iirc ?20:42
johnthetubaguybut I get a vision, with concrete what success lucks like is going to be more useful20:43
johnthetubaguyttx: I wasn't20:43
ttxOne trick is that some of us (who attended this training) now have a coherent vision (ha!) of what a vision looks like, would be great if gothicmindfood could give you an overview20:43
johnthetubaguyI have been pointed at the Ziggman stuff on visions thats public20:43
ttxwould save you time20:43
edleafejohnthetubaguy: haven't had a chance to read them yet, but what is the intended audience for these visions?20:44
dhellmannsome of the rest of what's here could go into the charter (the relationships stuff, for example) -- now that I say it here, I think maybe someone already said that on a review20:44
*** slaweq_ has joined #openstack-meeting20:44
ttxjohnthetubaguy: it's not as if we practiced that skill that much, so you're not really late to the party :)20:44
johnthetubaguydhellmann: yeah, I think some of this probably migrates into an expanded charter20:44
*** dmorita has quit IRC20:44
johnthetubaguyso I would love to see us get a TC vision agreed by the end of the PTG20:45
*** pvaneck has joined #openstack-meeting20:45
johnthetubaguymy focus is really, how do we set oursevles up for success20:45
*** dmorita has joined #openstack-meeting20:45
dhellmannwhat changes do people want to see in the TC or how it operates between now and then?20:46
ttxjohnthetubaguy: I think we could reuse the stewardship WG to make regular progress on this20:46
dhellmannwhere "then" is the end of the time frame laid out here, the end of Queens20:46
*** priteau has quit IRC20:46
johnthetubaguyttx: yes, that makes sense to me20:46
johnthetubaguydhellmann: yeah20:46
*** priteau has joined #openstack-meeting20:46
johnthetubaguyI picked the end of queens, because its in the future, but not too far away20:46
*** allanice001 has quit IRC20:46
dhellmannI think that's a good target20:47
ttxI'm skeptical we can slowly turn the review into the final document though, so I would abandon them and invite interested people to join the SWG meetings / channel20:47
johnthetubaguyttx: yep, thats fine20:47
johnthetubaguyI could get this into a etherpad, and pass it along to the next SWG20:47
ttxthat would be great20:47
fungii agree that should be far faster for initial draft collaboration20:47
fungifinal polish in code review should still be fine20:48
johnthetubaguyyeah, after having drafted this, its totally an etherpad thing20:48
ttxright, I'm pretty sure we'll still nitpick it to death in the end...20:48
johnthetubaguyI was shooting for merging bits, and evolving it in tree, but its totally not that kind of thing20:48
dhellmannyeah, and since we'll have multiples of these it might end up landing as a resolution instead of a top-level document20:49
ttx#info We'll work on the vision for the TC first20:49
johnthetubaguydhellmann: yeah, not a bad idea20:49
ttx#info The vision for the TC may include completing a vision for openstack20:49
*** pvaneck has quit IRC20:49
johnthetubaguythere are probably bits that turn into expanding bits of the charter I guess20:49
*** dmorita has quit IRC20:50
ttx#info We'll grow a base proposal using the Stewardship WG as a vessel20:50
dhellmannyeah, maybe those can come out into their own patches20:50
ttx#action johnthetubaguy to turn the governance reviews into etherpad(s) to discuss in the WG, and encourage people interested to join to attend SWG WG meetings20:50
ttxjohnthetubaguy: did I capture the next steps well ?20:51
johnthetubaguyanyways, wanted to try get *something* moving, so success20:51
dhellmannjohnthetubaguy : ++20:51
johnthetubaguyttx: yeah, I think thats good20:51
*** ekcs has joined #openstack-meeting20:51
johnthetubaguythank you20:51
ttxjohnthetubaguy: cool20:51
*** trandles has quit IRC20:51
*** nadya has joined #openstack-meeting20:51
*** adiantum1 has joined #openstack-meeting20:51
ttxLet's open it up for...20:51
ttx#topic Open discussion20:52
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:52
ttxstevemar: I saw you added the "formal-vote" topic to https://review.openstack.org/401990 ... did you want to discuss it in meeting ?20:52
ttxOr you think we should generally discuss repository removals ?20:52
*** adiantum has quit IRC20:52
*** adiantum1 is now known as adiantum20:52
mtreinishso I had one quick question, when is a good time to start discussing pike goals?20:52
dhellmannI started a mailing list discussion about driver-specific teams. I would appreciate everyone participating in that discussion20:52
dhellmann#link http://lists.openstack.org/pipermail/openstack-dev/2016-November/thread.html#10807420:52
mtreinishI want to revive the tempest plugin goal at some point20:52
ttxmtreinish: I'd say now20:52
*** dimtruck is now known as zz_dimtruck20:52
EmilienMmtreinish: I was about to run it :)20:52
*** trandles has joined #openstack-meeting20:52
EmilienMmtreinish: it's on my list to send it tonight or tomorrow morning20:52
ttxmtreinish: in a future "normal" cycle that would be around summit (middle of the cycle) time20:52
ttxbut there is no summit in the middle of Ocata so now is as good a time as any imho20:53
mtreinishttx: ok cool, I'll work on respinning that patch soon then20:53
ttx#info EmilienM volunteers to drive Pike goals identification20:54
dhellmannthanks, EmilienM!20:54
*** tommylikehu_ has joined #openstack-meeting20:54
stevemar__ttx: sorry, i thought i was being helpful and thought all repo removals needed their topic to be formal vote20:54
ttxNote that we'll have rooms at the pTG available if people want to get together and make quick progress on whatever goal we end up defining20:54
EmilienM#info EmilienM volunteers to also drive OpenStack goals feedback20:54
*** tonytan4ever has quit IRC20:54
ttxstevemar__: if someone objects to a removal during the "lazy consensus week" then i'll raise it for the meeting20:55
ttxotherwise we'll just merge it20:55
stevemar__ttx: rgr that, i'll change the topic then20:55
ttxok, I'll clean up the topic then20:55
ttxstevemar__: done20:55
ttxdhellmann: did you want to point people to the driver-team patches ?20:56
ttxand/or the thread discussion ?20:56
ttxIt's on the agenda for next week meeting20:56
dhellmannttx: they're all linked from the ml thread that I just posted20:56
dhellmann#link http://lists.openstack.org/pipermail/openstack-dev/2016-November/thread.html#10807420:56
dhellmannthere it is again20:56
ttxoh, missed that, great20:56
*** nadya has quit IRC20:56
*** matrohon has joined #openstack-meeting20:57
*** pvaneck has joined #openstack-meeting20:57
ttxok, anything else ?20:57
dhellmannthis is one of those topics where the outcome can have unintended consequences, so please read carefully20:57
*** gordc has left #openstack-meeting20:58
ttxFWIW I'm making progress on making a neutral governance website that holds TC, UC , election docs20:58
*** asselin_ has quit IRC20:58
ttxmaybe board one day, one never knows20:58
fungiyeah, i'm just now looking for the change you linked for me earlier in the infra channel20:58
*** jmlowe has joined #openstack-meeting20:58
*** raildo has quit IRC20:58
*** tommylikehu_ has quit IRC20:58
mtreinishdhellmann: fwiw, I wonder why a vendor would really want tc oversight. Also how is that something we could actually exert any influence over?20:58
mtreinishbut I'll take that to the ml (or wait for next weeks meeting)20:59
ttxfungi: cool, because we now publish to the new directory so the changes do not appear until you flip it20:59
dhellmannmtreinish : the cisco team has already asked for it20:59
*** rocky_g has joined #openstack-meeting20:59
fungittx: the files are getting published to the new /srv/static/tc tree so should be safe to update the vhost now20:59
*** b1airo has joined #openstack-meeting20:59
dhellmannmtreinish : https://review.openstack.org/36370920:59
ttxfungi: ++20:59
mtreinishdhellmann: right, but do they actual have a reason? or is it just they think that's a requirement for marketting or something?20:59
dhellmannmtreinish : does it matter?20:59
ttxmtreinish: discoverability is one, having their contributions count as "openstack" is another21:00
cdentdhellmann: shouldn't it?21:00
*** oneswig has joined #openstack-meeting21:00
dhellmannmtreinish, cdent : I respond to that point in the thread, so I won't repeat myself here.21:00
ttxand... we are off time21:00
fungittx: seems to be https://review.openstack.org/395660 so i'll get it going here in a sec21:00
*** rockyg has quit IRC21:00
ttxlet's continue that discussion on the ML, the reviews and at the meeting next week21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Tue Nov 29 21:00:37 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-11-29-20.01.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-11-29-20.01.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-11-29-20.01.log.html21:00
ttxThanks everyone!21:00
oneswigAnd on that happy note21:01
b1airo#startmeeting scientific-wg21:01
openstackMeeting started Tue Nov 29 21:01:06 2016 UTC and is due to finish in 60 minutes.  The chair is b1airo. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: scientific-wg)"21:01
openstackThe meeting name has been set to 'scientific_wg'21:01
oneswigGreetings all21:01
b1airo#chair oneswig21:01
openstackCurrent chairs: b1airo oneswig21:01
*** diablo_rojo has quit IRC21:01
*** pvaneck has quit IRC21:01
*** designbybeck has joined #openstack-meeting21:01
*** AJaeger has left #openstack-meeting21:01
*** dalvarez has quit IRC21:01
oneswighi all21:01
b1airohow's things?21:02
*** mickeys has quit IRC21:02
*** cdent has left #openstack-meeting21:02
oneswig#link Agenda items https://wiki.openstack.org/wiki/Scientific_working_group#IRC_Meeting_November_29th_201621:02
b1airogood thanksgiving break jmlowe, trandles ?21:02
jmlowegetting back to normal21:02
trandlesyessir, thank you21:02
oneswigAll well here, had the research councils UK cloud workshop today21:02
priteauGood *21:03
trandlesis everyone done with the mad travel schedule for the rest of 2016?21:03
b1airoah cool - did you chair / present something?21:03
jmloweI was home for a day and took the family to my inlaws in TX21:03
oneswigI presented, kind of chaired, but that aspect was fairly minimal21:03
trandleswell attended oneswig ?21:03
b1airotrandles, yes - though i already have 5 o/s trips in my calendar for 201721:03
trandlesouch b1airo21:03
oneswigtrandles: 140-odd I believe - not a sell-out but a good crowd21:03
oneswigb1airo: coming to the UK?21:04
*** martial has joined #openstack-meeting21:04
b1airooneswig, hopefully! but that isn't one of the firm ones yet21:04
*** Patifa has quit IRC21:04
martial(sorry I am late, meeting running over)21:04
oneswigWhat do we need to do to win the Bethwaited account, I wonder...21:04
*** adiantum has quit IRC21:04
oneswigHi Martial21:05
b1airo#chair martial21:05
openstackCurrent chairs: b1airo martial oneswig21:05
b1airohi martial21:05
martialHi Stig, Blair21:05
oneswigTime to tee off?21:05
b1airoyep, want to tell us about your vxlan results?21:05
*** Patifa has joined #openstack-meeting21:05
jmloweI'll poke Bob and see if he's available21:05
oneswigOK, lets do that...21:05
*** adiantum has joined #openstack-meeting21:06
oneswig#topic TCP bandwidth over VXLAN and OVS21:06
*** openstack changes topic to "TCP bandwidth over VXLAN and OVS (Meeting topic: scientific-wg)"21:06
b1airohi rocky_g21:06
oneswigHi rocky_g21:06
*** diablo_rojo has joined #openstack-meeting21:06
*** ijw has joined #openstack-meeting21:06
oneswigSo, this has been a bit of a saga ever since we realised how much our shiny new deployment with its 50G/100G network sucked in this respect21:06
*** fguillot has quit IRC21:07
*** edtubill has joined #openstack-meeting21:07
rocky_gHey!  This meeting time works great for me...I just stay on after the TC21:07
jmloweoneswig: I take it you get near line rate when doing bare metal?21:07
oneswigWe were seeing instance to instance bandwidth around 1.2gbits/s measured using iperf21:07
*** ijw has quit IRC21:07
oneswigjmlowe: bare metal, 1 stream TCP, 46 gbits/s21:07
*** edtubill has quit IRC21:07
jmloweclose enough21:07
*** rbudden has joined #openstack-meeting21:08
oneswigI was satisfied :-)21:08
oneswigHi rbudden21:08
*** ijw has joined #openstack-meeting21:08
*** edtubill has joined #openstack-meeting21:08
rbuddensorry, the time change got me!21:08
jmloweare you sysctl's posted somewhere?21:08
b1airooneswig, 1 stream?! e5-2680v3 ?21:08
b1airowhat window size?21:08
oneswigNot sysctls for that, didn't do any...21:08
b1airojmlowe, +121:08
oneswigI know, I was quite pleased.21:09
b1airothink there might be an element of VW tuning in play?? ;-)21:09
rocky_gYeah, bare metal looks good, but the vm stuff really *sucks*21:09
*** zara_the_lemur__ has left #openstack-meeting21:09
*** dalvarez has joined #openstack-meeting21:09
oneswigAnyway, we got VM-to-VM bandwidth up after much tuning21:09
*** zz_dimtruck is now known as dimtruck21:09
jmlowemy sysctl's https://raw.githubusercontent.com/jetstream-cloud/Jetstream-Salt-States/master/states/10gige.sls21:09
jmloweuse them everywhere21:10
oneswigFirst move was to turn off all those power-saving states and some things Mellanox support recommended disabling21:10
oneswigThat got us to around 2-3 gbits/s21:10
oneswigTried a new kernel after that - 4.7.10 - apparently there is better handling of offloading of encapsulated traffic further upstream21:11
*** gouthamr has quit IRC21:11
oneswigGot us to 11gbits/s21:11
oneswigThen we turned off hyperthreading - all those wimpy cores are fine for production but no good for hero numbers21:11
oneswigThen we were up around 18gbits/s21:12
oneswigThen I did VCPU-to-PCPU core pinning21:12
oneswigthat hit 21 gbits/s21:12
b1airooneswig, so where do Mellanox's shiny graphs (e.g. advertising CX-3 Pro 2+ years ago) come from...?21:12
b1airoahhh! i assumed you were pinning to begin with21:13
oneswigThat's CX-3 - and apparently the driver had a lot of capabilities back-ported to it which don't translate to mlx4 - that backporting process must be redone21:13
oneswigb1airo: no - actually this was a proper nuisance21:13
b1airomeanwhile CX-6 has been announced...21:13
oneswigCertainly the next bit - NUMA passthrough - I had to build a new QEMU-KVM - what you get with CentOS is nobbled21:14
trandlesthe amount of fixes/improvements going into upstream kernels for cx-4 and cx-5 are staggering21:14
jmloweeven the qemu 2.3 from the ev repo?21:14
b1airoha yeah, 1990s21:14
oneswigb1airo: announced for when?21:14
oneswigjmlowe: Does that work for CentOS?  Not sure if it does?21:15
b1airooneswig, same time as HDR presumably21:15
oneswigb1airo: wait a minute, I thought that was announced at SC ... :-)21:15
*** jschwarz has quit IRC21:16
oneswigAnyhow, I built and packaged QEMU-KVM 2.4.1, set isolcpus to give the host OS + OVS 4 cores, and pinned the VM to the NUMA node with the NIC attached to it.21:16
oneswigThat got me to 24.3 gbits/s21:16
b1airoindeed - don't know whether there are even any eng. samples yet though21:16
jmlowethis works just fine for us, has 2.3 in it, now if they could just get a non antique libvirt http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/21:16
*** ajo has quit IRC21:16
oneswigjmlowe: ooh, that's good - thanks, makes my life easier21:17
*** ljxiash has joined #openstack-meeting21:17
*** adiantum1 has joined #openstack-meeting21:17
*** jschwarz has joined #openstack-meeting21:17
martialjmlowe: there was a few posts about this on the ML recently if my memory is correct21:17
*** ajo has joined #openstack-meeting21:17
b1airojmlowe, you're talking about the rhev repos for centos?21:17
jmloweI should read the ml more carefully21:17
jmloweyeah, that's the one21:17
b1airooneswig, something of a saga then21:18
oneswigI had to find an EFI boot ROM RPM from somewhere as well - the package I rebuilt from fedora had a load of broken links in it21:18
b1airoand still only 50% of your bare-metal performance21:18
priteauLooks like they may even have QEMU 2.6 soon: https://cbs.centos.org/koji/buildinfo?buildID=1388421:18
oneswigThat's where I am now - but the joy of it is that a rising tide lifts all boats.21:18
*** apetrich has quit IRC21:18
b1airowhat are mellanox doing to make this right?21:18
oneswigFrom doing this tinkering, I got SR-IOV bandwidth raised from 33gbits/s->42gbits/s and bare metal to 46gbits/s21:19
*** spotz_zzz is now known as spotz21:19
rocky_gAnd have you considered writing this up as a superuser blog?21:19
oneswigrocky_g: that would be fab.  I am writing it up next time I get on a train - tomorrow - will share21:20
jmloweany thoughts as to how much of a difference if any there would be with linuxbridge vs ovs?21:20
*** adiantum has quit IRC21:20
*** adiantum1 is now known as adiantum21:20
oneswigjmlowe: Ah, what a question21:20
jmlowebeing probably the only linxubridge guy here, I had to ask21:21
oneswigI think there would be a positive uplift from ditching OVS, but tripleO has no means to deploy without i21:21
*** ljxiash has quit IRC21:21
oneswigThere was more on this: the kernel capabilities gained in 4.x are being backported by RH to the 7.3 kernel21:22
jmloweI haven't been following triple o, the latest install guides have dropped ovs?  wondering if triple o would follow21:22
oneswigWhich makes the whole process much more attainable.21:22
oneswigjmlowe: I'd need to check, I may be out of date but I hadn't seen that21:23
b1airoso oneswig, had mellanox never looked at vxlan performance with CX-4 ?21:23
*** isunil has joined #openstack-meeting21:23
*** leong has joined #openstack-meeting21:23
oneswigb1airo: who knows?  I'm sure they are busy people :-)21:23
oneswigI can't fault their efforts to get a solution once the issue was clear21:24
b1airoyes, us either - just think their testing leaves something to be desired21:25
*** penick has quit IRC21:25
oneswig#action oneswig to write up a report and share the details on reproducing21:25
oneswigHi leong21:25
*** penick has joined #openstack-meeting21:25
*** Leo_ has quit IRC21:25
oneswigOK next topic?21:25
oneswig#topic telemetry and monitoring - research computing use cases21:26
*** openstack changes topic to "telemetry and monitoring - research computing use cases (Meeting topic: scientific-wg)"21:26
*** krtaylor has quit IRC21:26
*** jschwarz has quit IRC21:26
oneswigOK this is one of our activity areas for this cycle, I wanted to get some WG thoughts down21:26
jmloweI've got two use cases21:27
martialso there was a good conversation on the ML recently21:27
oneswigI think there are specific use cases we like that others don't need21:27
oneswig#link etherpad for brainstorming21:27
oneswig#link https://etherpad.openstack.org/p/scientific-wg-telemetry-and-monitoring21:27
*** jschwarz has joined #openstack-meeting21:27
oneswigmartial: got a link to the mailing list thread?21:28
martialthey mentioned Collectd21:28
martiallet me find it out21:28
oneswigmartial: thanks21:28
*** dmorita has joined #openstack-meeting21:28
leongfor the telemetry and monitoring? are we looking at "enhancing" existing related openstack project to support those features/use-cases of scientific?21:29
oneswigleong: interesting question.  Lots of problems with existing projects21:30
jmloweI've added my 3 current active use cases to the etherpad21:30
oneswigjmlowe: what do you mean by the first?21:30
*** penick has quit IRC21:30
*** e0ne has quit IRC21:31
*** Leo_ has joined #openstack-meeting21:31
*** cdub has quit IRC21:31
martialFYI, we are developing a solution in house for telemetry aggregation21:31
oneswigGreat one b1airo21:32
leongok.. back step a bit.. are we aiming to create a user story in PWG and then perform gap analysis, then decide the best solution from there?21:32
martialI have to find it in the archive, but it was an email: [Openstack-operators] VM monitoring suggestions21:32
jmlowefor every hour there is an event generated in the ceilometer (now new project that I can't remember) database of instance exists with a start and end time up to the next hour, the cpu count, project, user and that can relatively easily be adapted to look like a hpc job and can be fed into existing hpc job reporting systems21:32
oneswigleong: that's a likely path I'd guess.  We already have a federation user story in review21:32
leonggreat oneswig!21:33
*** haleyb__ has joined #openstack-meeting21:33
*** pvaneck has joined #openstack-meeting21:33
leonghaving initial discussion on etherpad is a good start. Moving that discussion towards PWG user story will be able to keep track of the historical viewpoint/discussion on gerrit21:34
*** mickeys has joined #openstack-meeting21:34
martialour solution relies on a python library using psutil and we are also using ganglia21:34
oneswigleong: this is how the other story first took shape21:34
oneswigmartial: got any documentation online for it?21:34
*** penick has joined #openstack-meeting21:35
leongthere are new project evolving, including gnocchi, aodh which might be able to meet the needs.. however, without a formal description of the problem/use-case, it is hard to comment21:35
*** spzala has quit IRC21:35
martialoneswig: giving a link to my team member to the etherpad to describe it21:35
*** spzala has joined #openstack-meeting21:36
*** spzala has quit IRC21:36
jmloweI'm looking at doing something with some civil engineers who have a stream of time series data coming from traffic cameras, they need to have continuous ingestion and aggregation, I'm going to try them with gnocchi and get them off of their 5TB ms sql db21:36
leongit is also worthwhile to mention/document what existing solutions are adopted by existing scientific users in the User Story.21:36
oneswig#link previous user story on federation - please review https://review.openstack.org/#/c/400738/21:36
*** spzala has joined #openstack-meeting21:36
martialjmlowe: I need to get you in touch with a colleague of mine21:36
*** spzala has quit IRC21:37
martialjmlowe: and our Data Science team that does work on traffic camera data :)21:37
b1airojmlowe, o_021:37
oneswigleong: so one relevant shortcoming is I don't believe there is any way to transiently enable high-resolution telemetry - just as an example21:37
*** spzala has joined #openstack-meeting21:37
*** spzala has quit IRC21:37
*** haleyb__ has quit IRC21:37
jmloweI suspect there are a lot of civil engineers grabbing data from their state's DOT and we could probably make a thing that several of them could use21:37
*** spzala has joined #openstack-meeting21:38
*** spzala has quit IRC21:38
*** spzala has joined #openstack-meeting21:38
b1airojmlowe, i think you will be happy with gnochhi - we have it deployed in nectar and seems to work weel21:38
*** spzala has quit IRC21:38
oneswigjmlowe: 5TB of SQL...21:39
jmloweI've been using gnocchi since the 1.x series21:39
*** spzala has joined #openstack-meeting21:39
*** spzala has quit IRC21:39
jmloweeach major release has been an order of magnitude improvement21:39
oneswigWe were using Influx as backend but are stuck now, what does Gnocchi use nowadays?21:39
*** spzala has joined #openstack-meeting21:40
b1airooneswig, stuck why? because they ripped influx out?21:40
jmlowefile, and ceph, and one other21:40
*** spzala has quit IRC21:40
*** noslzzp_ has quit IRC21:40
jmloweif you use ceph make sure you are on the 3.x series21:40
rocky_gfluent maybe?21:40
*** spzala has joined #openstack-meeting21:40
*** noslzzp has joined #openstack-meeting21:40
*** spzala has quit IRC21:40
b1airooneswig, we (well really sorrison) put influx support back and redesigned the driver21:41
*** noslzzp has quit IRC21:41
*** spzala has joined #openstack-meeting21:41
*** spzala has quit IRC21:41
oneswigOthers have said the Ceph backend kind of consumes the ceph - needs its own dedicated cluster - I wonder what rate of time-series metrics is attainable21:42
*** spzala has joined #openstack-meeting21:42
b1aironot sure where the reviews are at - but pretty sure it is all going upstream21:42
*** spzala has quit IRC21:42
jmloweI have very nice things to say about Gordon Chang, one of the gnocchi devs, he's been immensely helpful21:42
oneswigb1airo: that's good, but I don't think we'd pay Influx for the clustered backend21:42
*** Cibo_ has joined #openstack-meeting21:42
*** spzala has joined #openstack-meeting21:42
*** mmotiani_ has quit IRC21:43
*** spzala has quit IRC21:43
*** ajo has quit IRC21:43
b1airodon't need to21:43
b1airoi could get sorrison to join next week and give us the low-down21:43
*** spzala has joined #openstack-meeting21:43
jmlowethe ceph backend in the 1.x series relied too heavily on xattrs which didn't scale, the 2.x series created too many new objects which lead to lock contention and slow ops warnings, the 3.x series has been problem free21:43
*** spzala has quit IRC21:43
oneswigb1airo: which timezone works best for sorrison?21:43
b1airoprobably next week - he rows in the mornings21:44
*** spzala has joined #openstack-meeting21:44
*** spzala has quit IRC21:44
oneswigb1airo: sounds good to me21:44
*** spzala has joined #openstack-meeting21:45
*** spzala has quit IRC21:45
*** jprovazn has quit IRC21:45
b1airooneswig, this might(?) be the tree he's been working on: https://github.com/NeCTAR-RC/gnocchi/tree/nectar/2.221:45
*** spzala has joined #openstack-meeting21:45
*** spzala has quit IRC21:46
*** ajo has joined #openstack-meeting21:46
*** spzala has joined #openstack-meeting21:46
*** e0ne has joined #openstack-meeting21:46
*** spzala has quit IRC21:46
*** e0ne has quit IRC21:47
oneswigWhat do people use for monitoring the health of OpenStack itself?  We have used Monasca, the agent gathers useful data out of the box21:47
*** kaisers_ has quit IRC21:47
*** spzala has joined #openstack-meeting21:47
*** spzala has quit IRC21:47
*** spzala has joined #openstack-meeting21:48
b1airooneswig, how did you find the setup ?21:48
*** spzala has quit IRC21:48
jmlowewe've been using zabbix, because it was there, I'd love to use something better21:48
martialfound the ML thread: http://lists.openstack.org/pipermail/openstack-operators/2016-November/012129.html21:48
leongoneswig: You mean the OpenStack control-plane?21:48
*** spzala has joined #openstack-meeting21:48
leongnagios is one21:48
oneswigMy team mate took quite a few unhappy days on it - Monasca seems to have no concept of a lightweight solution :-)21:48
*** spzala has quit IRC21:48
rbuddenwe use naemon at PSC for most of our monitoring21:48
priteauoneswig: we use Nagios with plugins from https://github.com/cirrax/openstack-nagios-plugins21:49
*** ijw has quit IRC21:49
*** spzala has joined #openstack-meeting21:49
oneswigrbudden: got a link to that?21:49
*** spzala has quit IRC21:49
rbuddenoneswig: http://www.naemon.org21:50
oneswigleong: yes - for example we get historical data of per-service CPU & RAM consumption21:50
rbuddeni believe it’s a fork from Nagios21:50
rocky_ghas anyone looked at the Vitrage project?  I know it's supposed to be root cause analysis, but what does that project use to capture and store their info?21:50
*** spzala has joined #openstack-meeting21:50
*** ijw has joined #openstack-meeting21:50
*** spzala has quit IRC21:50
*** pnavarro has quit IRC21:50
oneswigWasn't Zabbix also an evolution of Nagios?  I sense a bake-off coming21:50
*** annegentle has quit IRC21:50
b1airothe attractive thing about monasca is that it understands openstack - nagios is easy for monitoring process and service state, but what about all the stuff flying around on the MQ21:50
*** spzala has joined #openstack-meeting21:51
trandleswe use LDMS/OVIS   https://ovis.ca.sandia.gov/mediawiki/index.php/Main_Page21:51
oneswigrocky_g: saw the keynote - was blown away - not seen anything since21:51
*** spzala has quit IRC21:51
*** annegentle has joined #openstack-meeting21:51
jmlowehow heavy is heavy when it comes to monasca21:51
*** spzala has joined #openstack-meeting21:51
b1airowe use nagios and ganglia at the host level, elk for api data21:51
*** spzala has quit IRC21:51
oneswigjmlowe: It uses a lot of Apache stack - Kafka, Storm, etc.21:52
*** spzala has joined #openstack-meeting21:52
oneswigGlued together with data-moving services of its own21:52
rocky_gThis is all great info to capture on the etherpad....21:52
*** spzala has quit IRC21:52
*** rtheis has quit IRC21:52
oneswigrocky_g: I'm going to print the whole thing out and put it on my wall :-)21:52
jmlowemust keep from making an ouroboros21:52
martialrocky_g: doing what I can to make that happen :)21:53
*** spzala has joined #openstack-meeting21:53
*** spzala has quit IRC21:53
*** nadya has joined #openstack-meeting21:53
oneswigjmlowe: ouroboros - I have learned something today21:53
*** spzala has joined #openstack-meeting21:54
*** matrohon has quit IRC21:54
*** spzala has quit IRC21:54
oneswigFinal issues to lob in: who monitors OpenStack event notifications, and how?21:54
*** matrohon has joined #openstack-meeting21:54
*** spzala has joined #openstack-meeting21:54
b1airoas in the queues oneswig ?21:54
trandlesoneswig: I've played with it a tiny bit using splunk21:54
*** spzala has quit IRC21:55
oneswigOne aspect of Monasca I quite like is that it hoovers up everything and anything21:55
*** tpsilva has quit IRC21:55
oneswigb1airo: json blobs that get thrown out whenever nova/cinder/etc does anything useful21:55
*** ijw has quit IRC21:55
*** spzala has joined #openstack-meeting21:55
oneswigthose things21:55
*** spzala has quit IRC21:55
*** rodrigods is now known as rodrigods_21:56
*** spzala has joined #openstack-meeting21:56
trandlesoh, I don't touch the json, I was feeding the normal logs to splunk and building searches21:56
*** spzala has quit IRC21:56
oneswigOK, does anyone have infrastructure that triggers alerts based on log messages? - trandles looks like you're up to this21:56
b1airoyeah i was just wondering if you meant notification.error in particular, or everything21:56
rocky_gThere are config options to capture those or not.21:56
*** askb has joined #openstack-meeting21:57
*** spzala has joined #openstack-meeting21:57
trandlesoneswig: exactly21:57
*** spzala has quit IRC21:57
b1airowe have nagios alerts on certain queues21:57
oneswigb1airo: everything - want to reconstruct into timelines (os-profiler?)21:57
b1airojust based on ready message count21:57
*** spzala has joined #openstack-meeting21:57
*** spzala has quit IRC21:57
*** nadya has quit IRC21:58
b1airowe're almost out of time21:58
trandlesour operations folks use zenoss to actually trigger alerts but I've never talked to them about feeding openstack data into it21:58
*** spzala has joined #openstack-meeting21:58
*** spzala has quit IRC21:58
b1airopriteau, we didn't talk about workload traces21:58
b1aironext time?21:59
*** spzala has joined #openstack-meeting21:59
rocky_gNext time...21:59
oneswigpriteau: sounds good to me, fits in well21:59
priteaub1airo: Let's put it on the agenda for next itme21:59
b1airodoes next week's TZ work for you?21:59
*** spzala has quit IRC21:59
b1airoor week after?21:59
priteauI join both meetings :-)21:59
b1airoi thought you did - just a little hungover this morning...21:59
*** spzala has joined #openstack-meeting21:59
b1airo(xmas parties have started already)22:00
*** spzala has quit IRC22:00
b1airothanks all!22:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
oneswigthanks everyone -22:00
openstackMeeting ended Tue Nov 29 22:00:21 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_wg/2016/scientific_wg.2016-11-29-21.01.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_wg/2016/scientific_wg.2016-11-29-21.01.txt22:00
*** dtrainor has quit IRC22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_wg/2016/scientific_wg.2016-11-29-21.01.log.html22:00
oneswiggreat session22:00
martialI see my colleague added content to the Etherpad22:00
*** slayer has quit IRC22:00
martialfeel free to reach out to him with questions22:00
*** spzala has joined #openstack-meeting22:00
*** spzala has quit IRC22:00
martialthanks all22:00
*** leong has quit IRC22:01
*** oneswig has quit IRC22:01
*** spzala has joined #openstack-meeting22:01
*** b1airo has quit IRC22:01
*** spzala has quit IRC22:01
*** julim has quit IRC22:01
*** bobmel has quit IRC22:02
*** spzala has joined #openstack-meeting22:02
*** spzala has quit IRC22:02
*** spzala has joined #openstack-meeting22:03
*** spzala has quit IRC22:03
*** slaweq_ has quit IRC22:03
*** lblanchard has quit IRC22:03
*** spzala has joined #openstack-meeting22:03
*** spzala has quit IRC22:03
*** spzala has joined #openstack-meeting22:04
*** spzala has quit IRC22:04
*** trandles has quit IRC22:04
*** topol has joined #openstack-meeting22:04
*** spzala has joined #openstack-meeting22:05
*** spzala has quit IRC22:05
*** isunil has quit IRC22:05
*** jgregor has quit IRC22:05
*** lpetrut has quit IRC22:05
*** spzala has joined #openstack-meeting22:05
*** spzala has quit IRC22:06
*** hurricanerix has joined #openstack-meeting22:06
*** spzala has joined #openstack-meeting22:06
*** georgem1 has joined #openstack-meeting22:06
*** spzala has quit IRC22:06
*** ykatabam has joined #openstack-meeting22:06
*** spzala has joined #openstack-meeting22:07
*** corey_ has quit IRC22:07
*** spzala has quit IRC22:07
*** jgregor has joined #openstack-meeting22:07
*** priteau has quit IRC22:08
*** spzala has joined #openstack-meeting22:08
*** spzala has quit IRC22:08
*** jtomasek has quit IRC22:08
*** jrist has quit IRC22:08
*** spzala has joined #openstack-meeting22:08
*** spzala has quit IRC22:09
*** spzala has joined #openstack-meeting22:09
*** spzala has quit IRC22:09
*** rocky_g has quit IRC22:10
*** spzala has joined #openstack-meeting22:10
*** spzala has quit IRC22:10
*** spzala has joined #openstack-meeting22:11
*** spzala has quit IRC22:11
*** kaisers has joined #openstack-meeting22:11
*** spzala has joined #openstack-meeting22:11
*** spzala has quit IRC22:12
*** jgregor has quit IRC22:12
*** spzala has joined #openstack-meeting22:12
*** slayer has joined #openstack-meeting22:12
*** spzala has quit IRC22:12
*** spzala has joined #openstack-meeting22:13
*** spzala has quit IRC22:13
*** spzala has joined #openstack-meeting22:14
*** spzala has quit IRC22:14
*** spzala has joined #openstack-meeting22:14
*** spzala has quit IRC22:15
*** penick has quit IRC22:15
*** jamesdenton has quit IRC22:15
*** spzala has joined #openstack-meeting22:15
*** rbudden has quit IRC22:15
*** spzala has quit IRC22:15
*** penick has joined #openstack-meeting22:16
*** spzala has joined #openstack-meeting22:16
*** spzala has quit IRC22:16
*** kaisers has quit IRC22:16
*** topol has quit IRC22:16
*** spzala has joined #openstack-meeting22:17
*** spzala has quit IRC22:17
*** penick has quit IRC22:17
*** kaisers has joined #openstack-meeting22:17
*** penick_ has joined #openstack-meeting22:17
*** spzala has joined #openstack-meeting22:17
*** spzala has quit IRC22:18
*** spzala has joined #openstack-meeting22:18
*** eharney has quit IRC22:18
*** spzala has quit IRC22:18
*** spzala has joined #openstack-meeting22:19
*** spzala has quit IRC22:19
*** topol has joined #openstack-meeting22:19
*** spzala has joined #openstack-meeting22:20
*** spzala has quit IRC22:20
*** spzala has joined #openstack-meeting22:20
*** spzala has quit IRC22:20
*** spzala has joined #openstack-meeting22:21
*** spzala has quit IRC22:21
*** spzala has joined #openstack-meeting22:22
*** spzala has quit IRC22:22
*** matrohon has quit IRC22:22
*** Leo_ has quit IRC22:23
*** spzala has joined #openstack-meeting22:23
*** spzala has quit IRC22:23
*** spzala has joined #openstack-meeting22:24
*** spzala has quit IRC22:24
*** spzala has joined #openstack-meeting22:24
*** spzala has quit IRC22:24
*** spzala has joined #openstack-meeting22:25
*** slayer has quit IRC22:25
*** spzala has quit IRC22:25
*** adiantum has quit IRC22:25
*** jaugustine has quit IRC22:25
*** adiantum has joined #openstack-meeting22:25
*** spzala has joined #openstack-meeting22:26
*** spzala has quit IRC22:26
*** spzala has joined #openstack-meeting22:26
*** spzala has quit IRC22:27
*** spzala has joined #openstack-meeting22:27
*** spzala has quit IRC22:28
*** spzala has joined #openstack-meeting22:28
*** spzala has quit IRC22:28
*** spzala has joined #openstack-meeting22:29
*** spzala has quit IRC22:29
*** spzala has joined #openstack-meeting22:30
*** spzala has quit IRC22:30
*** ljxiash has joined #openstack-meeting22:30
*** spzala has joined #openstack-meeting22:31
*** jgregor has joined #openstack-meeting22:31
*** spzala has quit IRC22:31
*** rcernin has joined #openstack-meeting22:31
*** rfolco has joined #openstack-meeting22:31
*** spzala has joined #openstack-meeting22:31
*** spzala has quit IRC22:32
*** skelso has quit IRC22:32
*** spzala has joined #openstack-meeting22:32
*** georgem1 has quit IRC22:32
*** spzala has quit IRC22:32
*** spzala has joined #openstack-meeting22:33
*** spzala has quit IRC22:33
*** skelso has joined #openstack-meeting22:33
*** spzala has joined #openstack-meeting22:34
*** spzala has quit IRC22:34
*** haleyb__ has joined #openstack-meeting22:34
*** spzala has joined #openstack-meeting22:35
*** spzala has quit IRC22:35
*** dprince has quit IRC22:35
*** spzala has joined #openstack-meeting22:35
*** spzala has quit IRC22:35
*** spzala has joined #openstack-meeting22:36
*** spzala has quit IRC22:36
*** spzala has joined #openstack-meeting22:36
*** spzala has quit IRC22:37
*** spzala has joined #openstack-meeting22:37
*** spzala has quit IRC22:37
*** jmckind has quit IRC22:37
*** spzala has joined #openstack-meeting22:38
*** adiantum1 has joined #openstack-meeting22:38
*** spzala has quit IRC22:38
*** adiantum has quit IRC22:38
*** adiantum1 is now known as adiantum22:38
*** spzala has joined #openstack-meeting22:38
*** spzala has quit IRC22:38
*** spzala has joined #openstack-meeting22:39
*** haleyb__ has quit IRC22:39
*** spzala has quit IRC22:39
*** jschwarz has quit IRC22:39
*** spzala has joined #openstack-meeting22:39
*** spzala has quit IRC22:39
*** ajo has quit IRC22:40
*** jschwarz has joined #openstack-meeting22:40
*** spzala has joined #openstack-meeting22:40
*** spzala has quit IRC22:40
*** spzala has joined #openstack-meeting22:41
*** ajo has joined #openstack-meeting22:41
*** spzala has quit IRC22:41
*** spzala has joined #openstack-meeting22:42
*** spzala has quit IRC22:42
*** spzala has joined #openstack-meeting22:42
*** spzala has quit IRC22:43
*** spzala has joined #openstack-meeting22:43
*** spzala has quit IRC22:43
*** spzala has joined #openstack-meeting22:44
*** spzala has quit IRC22:44
*** spzala has joined #openstack-meeting22:45
*** spzala has quit IRC22:45
*** gyee has joined #openstack-meeting22:45
*** spzala has joined #openstack-meeting22:46
*** spzala has quit IRC22:46
*** spzala has joined #openstack-meeting22:46
*** spzala has quit IRC22:47
*** dmorita has quit IRC22:47
*** designbybeck has quit IRC22:47
*** spzala has joined #openstack-meeting22:47
*** spzala has quit IRC22:47
*** mriedem has quit IRC22:48
*** spzala has joined #openstack-meeting22:48
*** spzala has quit IRC22:48
*** spzala has joined #openstack-meeting22:49
*** spzala has quit IRC22:49
*** xyang1 has quit IRC22:50
*** spzala has joined #openstack-meeting22:50
*** spzala has quit IRC22:50
*** spzala has joined #openstack-meeting22:51
*** spzala has quit IRC22:51
*** ijw has joined #openstack-meeting22:51
*** spzala has joined #openstack-meeting22:51
*** spzala has quit IRC22:51
*** baoli has quit IRC22:52
*** spzala has joined #openstack-meeting22:52
*** spzala has quit IRC22:52
*** thorst_ has quit IRC22:53
*** spzala_ has joined #openstack-meeting22:53
*** tris has quit IRC22:53
*** diga has quit IRC22:53
*** spzala_ has quit IRC22:53
*** jgregor has quit IRC22:54
*** spzala_ has joined #openstack-meeting22:54
*** spzala_ has quit IRC22:54
*** ijw has quit IRC22:54
*** ijw has joined #openstack-meeting22:55
*** spzala_ has joined #openstack-meeting22:55
*** spzala_ has quit IRC22:55
*** spzala has joined #openstack-meeting22:56
*** spzala has quit IRC22:56
*** spzala has joined #openstack-meeting22:56
*** spzala has quit IRC22:56
*** slagle has quit IRC22:57
*** spzala has joined #openstack-meeting22:57
*** dimtruck is now known as zz_dimtruck22:57
*** unicell1 has quit IRC22:57
*** spzala has quit IRC22:57
*** spzala has joined #openstack-meeting22:58
*** spzala has quit IRC22:58
*** spzala has joined #openstack-meeting22:59
*** spzala has quit IRC22:59
*** spzala has joined #openstack-meeting22:59
*** spzala has quit IRC22:59
*** dmorita has joined #openstack-meeting23:00
*** spzala has joined #openstack-meeting23:00
*** spzala_ has joined #openstack-meeting23:00
*** spzala_ has quit IRC23:00
*** dmorita has quit IRC23:00
*** spzala_ has joined #openstack-meeting23:01
*** spzala_ has quit IRC23:01
*** rcernin has quit IRC23:01
*** spzala_ has joined #openstack-meeting23:02
*** spzala_ has quit IRC23:02
*** spzala_ has joined #openstack-meeting23:02
*** spzala has quit IRC23:02
*** dmorita has joined #openstack-meeting23:03
*** spzala_ has quit IRC23:03
*** skelso has quit IRC23:03
*** edtubill has quit IRC23:03
*** spzala has joined #openstack-meeting23:03
*** spzala has quit IRC23:03
*** tris has joined #openstack-meeting23:04
*** rcernin has joined #openstack-meeting23:04
*** rcernin has joined #openstack-meeting23:04
*** spzala has joined #openstack-meeting23:04
*** spzala has quit IRC23:04
*** rfolco has quit IRC23:04
*** spzala has joined #openstack-meeting23:05
*** spzala has quit IRC23:05
*** spzala has joined #openstack-meeting23:06
*** spzala has quit IRC23:06
*** zz_dimtruck is now known as dimtruck23:06
*** spzala has joined #openstack-meeting23:06
*** spzala has quit IRC23:06
*** Leo_ has joined #openstack-meeting23:07
*** spzala has joined #openstack-meeting23:07
*** spzala has quit IRC23:07
*** spzala has joined #openstack-meeting23:08
*** spzala has quit IRC23:08
*** spzala has joined #openstack-meeting23:09
*** spzala has quit IRC23:09
*** spzala has joined #openstack-meeting23:09
*** Leom has joined #openstack-meeting23:09
*** spzala has quit IRC23:09
*** kaminohana has joined #openstack-meeting23:10
*** spzala has joined #openstack-meeting23:10
*** spzala has quit IRC23:10
*** spzala has joined #openstack-meeting23:11
*** spzala has quit IRC23:11
*** Leo_ has quit IRC23:11
*** spzala has joined #openstack-meeting23:12
*** spzala has quit IRC23:12
*** lixinhui has quit IRC23:12
*** spzala has joined #openstack-meeting23:12
*** ijw has quit IRC23:13
*** bobh has joined #openstack-meeting23:13
*** spzala has quit IRC23:13
*** spzala has joined #openstack-meeting23:13
*** spzala has quit IRC23:13
*** spzala has joined #openstack-meeting23:14
*** spzala has quit IRC23:14
*** mriedem has joined #openstack-meeting23:14
*** spzala has joined #openstack-meeting23:15
*** spzala has quit IRC23:15
*** spzala has joined #openstack-meeting23:15
*** spzala has quit IRC23:15
*** yuanying has joined #openstack-meeting23:16
*** spzala has joined #openstack-meeting23:16
*** spzala has quit IRC23:16
*** rodrigods_ is now known as rodrigods23:17
*** galstrom is now known as galstrom_zzz23:17
*** spzala has joined #openstack-meeting23:17
*** spzala has quit IRC23:17
*** dmorita has quit IRC23:17
*** ijw has joined #openstack-meeting23:17
*** spzala has joined #openstack-meeting23:18
*** spzala has quit IRC23:18
*** spzala has joined #openstack-meeting23:18
*** spzala has quit IRC23:19
*** whenry has joined #openstack-meeting23:19
*** spzala has joined #openstack-meeting23:19
*** spzala has quit IRC23:20
*** tommylikehu_ has joined #openstack-meeting23:20
*** spzala has joined #openstack-meeting23:20
*** spzala has quit IRC23:20
*** dmorita has joined #openstack-meeting23:20
*** spzala has joined #openstack-meeting23:21
*** spzala has quit IRC23:21
*** spzala has joined #openstack-meeting23:22
*** spzala has quit IRC23:22
*** ijw has quit IRC23:22
*** stevemar__ has quit IRC23:22
*** spzala has joined #openstack-meeting23:22
*** enriquetaso has quit IRC23:22
*** fnaval has quit IRC23:22
*** spzala has quit IRC23:23
*** stevemar__ has joined #openstack-meeting23:23
*** spzala has joined #openstack-meeting23:23
*** spzala has quit IRC23:23
*** ayoung has quit IRC23:23
*** spzala has joined #openstack-meeting23:24
*** spzala has quit IRC23:24
*** spzala has joined #openstack-meeting23:25
*** spzala has quit IRC23:25
*** unicell has joined #openstack-meeting23:25
*** spzala has joined #openstack-meeting23:25
*** spzala has quit IRC23:25
*** dmorita has quit IRC23:26
*** spzala has joined #openstack-meeting23:26
*** spzala has quit IRC23:26
*** spzala has joined #openstack-meeting23:27
*** spzala has quit IRC23:27
*** stevemar__ has quit IRC23:27
*** spzala has joined #openstack-meeting23:28
*** spzala has quit IRC23:29
*** spzala has joined #openstack-meeting23:29
*** annegentle has quit IRC23:29
*** spzala has quit IRC23:29
*** spzala has joined #openstack-meeting23:30
*** spzala has quit IRC23:30
*** spzala has joined #openstack-meeting23:31
*** spzala has quit IRC23:31
*** spzala has joined #openstack-meeting23:32
*** spzala has quit IRC23:32
*** spzala has joined #openstack-meeting23:32
*** spzala has quit IRC23:32
*** spzala has joined #openstack-meeting23:33
*** annegentle has joined #openstack-meeting23:33
*** spzala has quit IRC23:33
*** spzala has joined #openstack-meeting23:34
*** spzala has quit IRC23:34
*** ljxiash has quit IRC23:34
*** spzala has joined #openstack-meeting23:34
*** spzala has quit IRC23:35
*** haleyb__ has joined #openstack-meeting23:35
*** dmorita has joined #openstack-meeting23:35
*** spzala has joined #openstack-meeting23:35
*** spzala has quit IRC23:35
*** spzala has joined #openstack-meeting23:36
*** spzala has quit IRC23:36
*** spzala has joined #openstack-meeting23:37
*** bobmel has joined #openstack-meeting23:37
*** haleyb__ has quit IRC23:40
*** agrebennikov has quit IRC23:40
*** rcernin has quit IRC23:41
*** bobmel has quit IRC23:42
*** thorst_ has joined #openstack-meeting23:42
*** thorst_ has quit IRC23:46
*** lamt has quit IRC23:46
*** ljxiash has joined #openstack-meeting23:47
*** ljxiash has quit IRC23:47
*** tommylikehu_ has quit IRC23:48
*** ljxiash has joined #openstack-meeting23:52
*** ljxiash has quit IRC23:53
*** nadya has joined #openstack-meeting23:54
*** Swami_ has joined #openstack-meeting23:54
*** spotz is now known as spotz_zzz23:55
*** thorst_ has joined #openstack-meeting23:56
*** Swami has quit IRC23:57
*** thorst_ has quit IRC23:58
*** nadya has quit IRC23:58
*** spotz_zzz is now known as spotz23:59
*** ijw has joined #openstack-meeting23:59

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