Tuesday, 2016-11-08

*** baoli has quit IRC00:01
*** gouthamr has joined #openstack-meeting00:02
*** tpsilva has quit IRC00:04
*** ijw has quit IRC00:05
*** gibi has quit IRC00:06
*** askb has joined #openstack-meeting00:06
*** ijw has joined #openstack-meeting00:07
*** cdub has joined #openstack-meeting00:08
*** Viswanath has joined #openstack-meeting00:10
*** draynium has joined #openstack-meeting00:12
*** takashin has joined #openstack-meeting00:13
*** gibi has joined #openstack-meeting00:13
*** thorst_ has quit IRC00:14
*** rfolco has quit IRC00:14
*** thorst_ has joined #openstack-meeting00:15
*** Viswanath has quit IRC00:16
*** bobh has joined #openstack-meeting00:17
*** imcsk8 has joined #openstack-meeting00:18
*** thorst_ has quit IRC00:19
*** Patifa has quit IRC00:19
*** takashin has quit IRC00:19
*** Leom has quit IRC00:22
*** mickeys has joined #openstack-meeting00:24
*** Patifa has joined #openstack-meeting00:25
*** lhx_ has joined #openstack-meeting00:26
*** gibi has quit IRC00:28
*** uxdanielle has quit IRC00:30
*** Patifa has quit IRC00:32
*** thorst_ has joined #openstack-meeting00:34
*** thorst_ has quit IRC00:34
*** thorst_ has joined #openstack-meeting00:35
*** numans has quit IRC00:38
*** markvoelker has quit IRC00:39
*** thorst_ has quit IRC00:43
*** rossella_s has joined #openstack-meeting00:44
*** baoli has joined #openstack-meeting00:44
*** Julien-zte has joined #openstack-meeting00:46
*** banix has joined #openstack-meeting00:49
*** baoli has quit IRC00:51
*** mickeys has quit IRC00:52
*** woodster_ has quit IRC00:55
*** gibi has joined #openstack-meeting01:01
*** zhhuabj_ has quit IRC01:04
*** baoli has joined #openstack-meeting01:06
*** bobh has quit IRC01:08
*** ijw has quit IRC01:08
*** jamesdenton has joined #openstack-meeting01:08
*** lhx_ has quit IRC01:09
*** Wenzhi has joined #openstack-meeting01:12
*** baoli has quit IRC01:13
*** rfolco has joined #openstack-meeting01:14
*** rfolco has quit IRC01:14
*** syjulian has quit IRC01:15
*** ober37 has quit IRC01:16
*** zhhuabj_ has joined #openstack-meeting01:16
*** ober37 has joined #openstack-meeting01:17
*** syjulian has joined #openstack-meeting01:18
*** unicell has quit IRC01:19
*** ayoung has joined #openstack-meeting01:20
*** unicell has joined #openstack-meeting01:21
*** Sukhdev has quit IRC01:25
*** iyamahat has quit IRC01:26
*** baoli has joined #openstack-meeting01:27
*** oomichi has quit IRC01:28
*** oomichi has joined #openstack-meeting01:29
*** zhurong has joined #openstack-meeting01:30
*** jamesdenton has quit IRC01:33
*** Apoorva has quit IRC01:33
*** Daisy has joined #openstack-meeting01:34
*** thorst_ has joined #openstack-meeting01:37
*** ijw has joined #openstack-meeting01:37
*** camunoz has quit IRC01:37
*** takashin has joined #openstack-meeting01:38
*** markvoelker has joined #openstack-meeting01:40
*** banix has quit IRC01:42
*** tiantian has quit IRC01:43
*** tiantian has joined #openstack-meeting01:43
*** markvoelker has quit IRC01:45
*** takashin has quit IRC01:45
*** Daisy has quit IRC01:45
*** banix has joined #openstack-meeting01:46
*** bobh has joined #openstack-meeting01:47
*** dmacpher has quit IRC01:47
*** oomichi has quit IRC01:54
*** oomichi has joined #openstack-meeting01:55
*** zhhuabj_ has quit IRC01:59
*** ayoung has quit IRC02:02
*** maeker_ has joined #openstack-meeting02:03
*** gcb has joined #openstack-meeting02:04
*** maeker_ has quit IRC02:05
*** maeker has quit IRC02:05
*** maeker has joined #openstack-meeting02:06
*** comay_ has quit IRC02:09
*** chandrav has joined #openstack-meeting02:11
*** bobh has quit IRC02:13
*** fzdarsky|afk has quit IRC02:13
*** elynn has joined #openstack-meeting02:15
*** zhhuabj_ has joined #openstack-meeting02:16
*** banix has quit IRC02:18
*** baoli has quit IRC02:18
*** Daisy has joined #openstack-meeting02:19
*** shu-mutou has joined #openstack-meeting02:20
*** elynn has quit IRC02:20
*** elynn has joined #openstack-meeting02:20
*** fnaval has quit IRC02:21
*** ykatabam has joined #openstack-meeting02:24
*** hongbin has joined #openstack-meeting02:24
*** baoli has joined #openstack-meeting02:24
*** thorst_ has quit IRC02:25
*** thorst_ has joined #openstack-meeting02:25
*** lhx_ has joined #openstack-meeting02:28
*** cody-somerville has joined #openstack-meeting02:28
*** cody-somerville has quit IRC02:28
*** cody-somerville has joined #openstack-meeting02:28
*** chandrav has quit IRC02:29
*** armax has quit IRC02:30
*** chandrav has joined #openstack-meeting02:31
*** thorst_ has quit IRC02:34
*** Daisy has quit IRC02:35
*** chandrav has quit IRC02:36
*** Daisy has joined #openstack-meeting02:36
*** yamamoto_ has joined #openstack-meeting02:36
*** epico has joined #openstack-meeting02:39
*** galstrom_zzz is now known as galstrom02:39
*** yanyanhu has joined #openstack-meeting02:39
*** ijw has quit IRC02:42
*** maeker_ has joined #openstack-meeting02:43
*** maeker has quit IRC02:43
*** imcsk8 has quit IRC02:44
*** imcsk8 has joined #openstack-meeting02:45
*** baoli has quit IRC02:47
*** baoli has joined #openstack-meeting02:48
*** mkrai has joined #openstack-meeting02:49
*** banix has joined #openstack-meeting02:50
*** yamahata has joined #openstack-meeting02:50
*** baoli has quit IRC02:50
*** shubhams has joined #openstack-meeting02:51
*** s3wong has quit IRC02:51
*** krtaylor has joined #openstack-meeting02:53
*** pksingh has joined #openstack-meeting02:54
*** pksingh has quit IRC02:55
*** dmacpher has joined #openstack-meeting02:56
*** chuckC_ has joined #openstack-meeting02:58
*** pksingh has joined #openstack-meeting02:58
*** galstrom is now known as galstrom_zzz02:58
*** baoli has joined #openstack-meeting02:59
hongbin#startmeeting zun02:59
openstackMeeting started Tue Nov  8 02:59:56 2016 UTC and is due to finish in 60 minutes.  The chair is hongbin. Information about MeetBot at http://wiki.debian.org/MeetBot.02:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.02:59
*** openstack changes topic to " (Meeting topic: zun)"02:59
openstackThe meeting name has been set to 'zun'03:00
hongbin#link https://wiki.openstack.org/wiki/Zun#Agenda_for_2016-11-08_0300_UTC Today's agenda03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
shubhamsshubhams03:00
mkraiMadhuri Kumari03:00
kevinzkevinz03:00
pksinghPradeep Singh03:00
WenzhiWenzhi03:00
*** chuckC_ has quit IRC03:00
flwango/03:00
yanyanhuhi03:00
hongbinThanks for joining the meeting shubhams mkrai kevinz pksingh Wenzhi flwang yanyanhu03:01
hongbin#topic Announcements03:01
*** openstack changes topic to "Announcements (Meeting topic: zun)"03:01
hongbin1. Welcome Shubham to join the core team03:01
hongbin#link http://lists.openstack.org/pipermail/openstack-dev/2016-November/106750.html03:01
pksinghcongrate shubhams03:01
*** iyamahat has joined #openstack-meeting03:01
Wenzhiwelcome03:01
mkraiCongratulation shubhams :)03:01
kevinzcongratulations03:01
mkraiWelcome to the team!03:01
hongbinshubhams: welcome. thanks for your contribution to Zun03:01
shubhamsThanks hongbin pksingh mkrai kevinz :)03:01
shu-mutouwelcome!03:02
hongbin2. Plan to be an official OpenStack project03:02
hongbinA requirement of joining OpenStack is to have an elected PTL, so I will find someone to hold a PTL election.03:02
mkraiI have been waiting for this :)03:02
hongbinyes03:02
Wenzhime too :)03:02
pksingh:)03:02
kevinz:)03:02
hongbinafter a ptl is elected, i will apply to be official03:02
hongbinhopefully, everything is fine03:03
hongbin3. OpenStack Barcelona Summit recap03:03
hongbin* We had a Zun presentation in the main summit.03:03
hongbin#link http://www.slideshare.net/hongbin034/zun-presentation-openstack-barcelona-summit The slide03:03
hongbin#link The video: https://www.youtube.com/watch?v=Go8_G3iLyl4 The video03:03
pksinghhongbin: i watched the video, it is greate :)03:03
hongbinpksingh: i was a bit nervous at that time03:03
hongbin:)03:03
yanyanhucool03:03
hongbinhope everything is clear03:04
*** thorst_ has joined #openstack-meeting03:04
kevinzwell done03:04
pksinghyup03:04
hongbin* We had a Zun session at design summit03:04
hongbin#link https://etherpad.openstack.org/p/ocata-zun-worksession The etherpad03:04
shubhamsYes it was a nice session03:04
hongbin* The general public showed high interests in our project03:04
hongbin#link http://www.internetnews.com/blog/skerner/openstack-zun-debuts-new-approach-to-cloud-containers.html An article about Zun03:04
hongbin* Feedback/Wishlist03:04
*** armax has joined #openstack-meeting03:04
hongbin1. Strong isolation between containers from different tenants03:04
*** unicell has quit IRC03:04
hongbin2. Kubernetes integration03:05
hongbinThese are the main features that I heard several times03:05
hongbinWill discuss it later in the agenda03:05
hongbin#topic Review Action Items03:05
*** openstack changes topic to "Review Action Items (Meeting topic: zun)"03:05
hongbinDiscuss with hongbin on features list for release o (In Progress)03:05
hongbinLet's discuss this03:05
*** iyamahat_ has joined #openstack-meeting03:06
hongbin#topic Plan features for Ocata release03:06
*** openstack changes topic to "Plan features for Ocata release (Meeting topic: zun)"03:06
hongbin#link https://etherpad.openstack.org/p/zun-ocata-planning The etherpad03:06
hongbinWe can either brainstorm ocata features here or work on the etherpad03:06
hongbinWhat features you want?03:06
*** dmacpher has quit IRC03:07
shubhamsI think on etherpad we can put our votes for each feature and then decide . What do you say ?03:07
pksinghetherpad +103:07
flwangi would say just focus on the current list03:07
*** iyamahat has quit IRC03:07
flwangvote is a good idea here03:07
hongbinshubhams: for sure, but let's wait for everything to have a input first03:07
hongbinok, do anyone want to add to the list at the last monent?03:08
pksinghI think first we should focus on docker runtime, and support all operations03:08
eliqiaohi , I am late03:08
hongbinpksingh: ack03:08
hongbineliqiao: we are working on the etherpad https://etherpad.openstack.org/p/zun-ocata-planning03:09
eliqiaohongbin: thx03:09
hongbinok, then let's vote03:09
mkraiPlease add any feature which you feel is left03:11
*** spotz is now known as spotz_zzz03:11
hongbinSo far, it looks k8s integration and functional tests have a lot of votes03:11
Qimingem, what does this mean -- "Kubernetes integration"?03:11
mkraiYes hongbin03:11
Qiminghaving zun acting as a proxy to kubernetes?03:11
hongbinQiming: sort-of03:12
*** thorst_ has quit IRC03:12
hongbinQiming: right now, we have docker + nova as the first driver03:12
hongbinQiming: I think k8s can be the second driver03:12
hongbinQiming: you have a concern?03:13
Qiming... they are different layer things, container engine and container orchestrator03:13
Qimingmy concern ^03:13
hongbinQiming: In the summit, people said we considered nova as a COE :)03:13
Qimingif nova can be a COE, there won't be zun03:14
hongbinQiming: Zun is driving nova as a COE (that is what I mean)03:14
QimingIMO, nova is not suitable for orchestration, and zun is the orchestrator03:14
hongbinQiming: ok, we could discuss that03:15
Qimingthen zun is about a unified COE abstraction, right?03:15
*** klkumar has joined #openstack-meeting03:15
hongbinQiming: yes, that is my understanding03:15
Qimingthanks, just for clarification, sorry for interrupt03:15
hongbinQiming: let me know if you have any concern03:16
hongbinHowever, we could discuss this offline03:16
*** armax has quit IRC03:16
hongbinOK, let's move on03:16
hongbin#topic Support interactive mode (adisky)03:17
*** openstack changes topic to "Support interactive mode (adisky) (Meeting topic: zun)"03:17
hongbin#link https://blueprints.launchpad.net/zun/+spec/support-interactive-mode The BP03:17
kevinzI've done some investigation , will use dockerpty to realize this.03:17
kevinzhttps://github.com/d11wtq/dockerpty03:17
pksinghhongbin: i would like to work on this03:17
kevinzCould I re use this library? Or copy its code to Zun.03:17
kevinzI will write a spec before next team meeting.03:17
pksinghif noone is working03:17
hongbinit looks kevinz also wanted to work on this :)03:18
hongbinpksingh vs kevinz03:18
*** tovin07 has joined #openstack-meeting03:18
hongbinpksingh: it looks the BP has been assigned to kevinz03:18
pksinghok will help kevinz in reviews :)03:19
hongbinkevinz: sure, looking forward to the spec03:19
kevinzpksingh: :-) Thanks~03:19
kevinzhongbin: OK03:19
hongbinyou two can pair up to work on this if you want03:19
shubhamskevinz: I  checked github repo of dockerpty and bit worried as last commit on this was in Feb. I am afraid if this repo is maintained well03:19
pksinghkevinz can we work on this?03:20
kevinzshubhams: Yeah I also concerned about that. So maybe we can re realize this in Zun03:20
hongbinok, let's move on03:21
hongbin#topic Container image store (mkrai)03:21
shubhamskevinz: ok03:21
*** openstack changes topic to "Container image store (mkrai) (Meeting topic: zun)"03:21
hongbin#link https://blueprints.launchpad.net/zun/+spec/glance-integration The BP03:21
hongbin#link https://review.openstack.org/#/c/383678/ Madhuri's patch03:21
hongbin#link https://review.openstack.org/#/c/380298/ Shubham's patch03:21
kevinzpksingh Thanks~03:21
mkraihongbin: the base patches were merged.03:21
hongbinmkrai: any other patches you plan to submit?03:22
mkraiI guess few more patches are required which are just needed for finishing off03:22
shubhamshongbin: mkrai , I will start working on python-magnumclient for image api03:22
mkraiYes one03:22
mkraiThat is to store images in glance when we pull it from docker03:22
hongbinshubhams: ack03:22
mkraiAnd then we can close this bp03:22
hongbingreat03:23
flwangmkrai: store the un-layered image in glance?03:23
mkraiOne question03:23
hongbinflwang: yes, it is a tarball03:23
flwangok, got it03:23
mkraiflwang: Yes. Do we want to support layering in glance also?03:23
flwangmkrai: no, since it's basically impossible :D03:23
mkraiThe same way nova-docker does it03:23
*** baoli_ has joined #openstack-meeting03:24
flwangi will take a look the patch this week03:24
flwangputting my glance hat03:24
hongbinflwang: i like your hat :)03:24
mkraihongbin: What do you think about it?03:25
hongbinmkrai: i agree with flwang that it is hard to work on layering image at this stage03:25
mkraiOk so I will leave that03:25
hongbinmkrai: it requires a lot of work, maybe a new project03:25
*** yamamoto_ has quit IRC03:25
hongbinyes, it might be a priority in the future, but i don't think it is now03:26
mkraiI meant storing new tarball of changed image which the nova-docker way03:26
*** baoli has quit IRC03:26
flwangmkrai: that's alright03:26
mkraiI think we can leave it for now as Glare aims to do it03:26
flwangonething we need to do is03:26
flwangusing tags or image custom properties to tag the image clearly03:27
flwangGlare is good, but don't expect much at this stage03:27
flwangat the lay off of Mirantis03:27
mkraiOhh I didn't know about this03:28
flwangI don't think there are people working on that, unless current Glare cores still want to maintain that after got a new job03:28
hongbinmarantis is laying off people, this is a hot discussion in the summit03:28
hongbinok, let's move on03:29
hongbin#topic Container network (hongbin)03:29
*** openstack changes topic to "Container network (hongbin) (Meeting topic: zun)"03:29
flwangpls take it as rumor03:29
*** thorst_ has joined #openstack-meeting03:29
flwang;D03:29
hongbin#link https://blueprints.launchpad.net/zun/+spec/neutron-integration The BP03:29
hongbin#link https://review.openstack.org/#/c/365754/ The proposed spec (merged)03:29
hongbin#link https://review.openstack.org/#/c/380646/ The patch03:29
hongbini tried to resolved all the conflicts in the patch and addresses most of hte comments03:29
hongbini think it is ready for another round of reviews now03:30
hongbin(remind: this is a large patch)03:30
mkraiYes I will revisit the patch03:30
hongbinmkrai: thx03:30
*** thorst_ has quit IRC03:30
hongbinok, then move to open discussion03:30
hongbin#topic Open Discussion03:30
*** openstack changes topic to "Open Discussion (Meeting topic: zun)"03:30
hongbin1. Multi-tenancy isolation between containers in the same host03:31
hongbinThis is the top wishlist in the summit according to the feedback03:31
mkraihongbin: I am not sure whether it will be feasible or not. But how about adding namespaces concept?03:32
hongbinmkrai: right now, we can hide containers from other tenants03:32
hongbinmkrai: which is basically a namespace03:32
mkraiK8s also has similar concept of namepsace03:32
hongbinmkrai: yes, consider openstack tenant is similar as k8s namespace03:33
pksinghthats i think just for hinding resources from ane and other03:33
mkraiYes03:33
yanyanhumaybe they are different I think. Currently, namespace only controls the visibility of resources while multi-tenancy is more about isolation?03:33
yuanyingHow host file systems is hidden by zun?03:33
hongbinyanyanhu: yes, i should say openstack tenant is a stronger than namespace03:34
yanyanhuyes03:34
hongbinyuanying: zun didn't expose the -v flag, so it is impossible to use docker run -v to mount host file system03:34
yuanyinghongbin: I got it03:35
hongbinhowever, the issue is: if there are two containers from two tenants scheduled to the same host, how to do isolation03:35
hongbinthis is the concern from people03:35
hongbinthere are several ways to solve it03:36
*** yamamoto_ has joined #openstack-meeting03:36
hongbin1. using vm as isolators03:36
hongbin2. use secure container (i.e. hyper, clear container)03:36
hongbinanything else?03:36
Qimingwait for kernel improvement03:36
hongbinQiming: :)03:36
*** dmorita has quit IRC03:36
yanyanhuor isolating containers by running them on different physical hosts?03:37
*** ayoung has joined #openstack-meeting03:37
hongbinyanyanhu: yes, that is also an option03:37
yanyanhualthough the isolation granularity could be too coarse...03:37
mkraiI may lead to waste of resource yanyanhu03:37
yanyanhumkrai, yes, that is a big concern03:37
mkraiI think #option 2 is better03:37
hongbinsilent....03:38
flwangif we  go for #2, does that mean docker is not welcome at this case?03:39
yanyanhufor option2, it depends on whether users buy in your idea: is "secure" container really secure?03:39
yanyanhu:)03:39
yanyanhuflwang, +103:39
pksinghflwang: +103:39
yanyanhuif it is 'really' secure, it is 'container' ?03:39
hongbinyanyanhu: it is actually a vm :)03:39
Qimingyes, it is Container NG03:39
yanyanhuyep03:39
flwanglet me ask in another way03:39
mkraione container per vm03:40
flwangwhy we don't like VM03:40
*** adisky has joined #openstack-meeting03:40
flwangjust because we're working on container?03:40
hongbinyanyanhu: however, it use the vm to run container image, so it is sort of a *container*03:40
QimingVM kills almost every benefit you get from a container, :D03:40
flwangwithout VM, we have not much relationship with OpenStack, IMHO03:40
Qimingflwang, true, that is why they don't care about us03:40
flwangQiming: hah03:40
hongbinflwang: the key of secure container is that it has optimized for the boot time03:41
hongbinflwang: so compared to vm, secure container boot faster03:41
hongbinflwang: that is the whole point03:41
flwanghongbin: but03:41
*** armax has joined #openstack-meeting03:41
*** markvoelker has joined #openstack-meeting03:41
mkraiFor clear container I know the container boots up really fast. I have used  it03:41
*** camunoz has joined #openstack-meeting03:41
flwangfor that case, we will basically give up docker, right?03:41
mkraiflwang: We can use the same docker cli to run clear containers03:42
flwangor we support docker, but if you want more secure, go for clear container ?03:42
hongbinflwang: yes, i think so. or i should say, for that case, secure container is an alternative to docker03:42
mkraiYes flwang03:42
flwangok, fair enough03:42
mkrai#link https://lwn.net/Articles/644675/03:43
mkraiMay be this article will help to understand03:43
hongbinflwang: you don't like secure container? or you have any concern?03:43
yanyanhumkrai, nice, will read it03:43
hongbini think we can try secure container, as an experiential driver (i am not sure if it will work)03:45
mkrai+1 hongbin03:45
hongbinany concern for this?03:45
pksingh+1 hongbin03:45
flwanghongbin: i'm happy with secure container03:45
shubhams+1 for secure container trial03:46
hongbinflwang: i just want to know if you see any pitfall for this approach03:46
flwangi just don't want to miss any case which may let some potential user go away03:46
*** markvoelker has quit IRC03:46
hongbinok, if there is no objection, i will create a bp for this03:46
hongbin#action hongbin create a bp for adding support for secure container03:47
adisky+1 hongbin03:47
hongbinAnything else to discuss from our team members?03:47
mkraik8s integration?03:48
hongbinmkrai: sure , we can discuss that03:48
mkraiDo we want to integrate with Magnum for this?03:48
pksinghhongbin: can we have anything like imagepullpolicy like k8 has?03:48
hongbinmkrai: that doesn't mean integrate with magnum03:49
mkraiImplement the k8s APIs in Zun?03:49
hongbinpksingh: i am not familiar with image pulling policy, but we can investigate it later03:49
hongbinmkrai: simply speaking, implement zun api by using k8s03:49
pksinghhongbin: ok03:50
hongbinhere is the long version03:50
hongbinthis is a features that has been mentioned by different people in the summit03:50
mkraiOk got it03:50
hongbinthe people don't like to use magnum to boot k8s, because they already has a k8s that is statically there03:50
hongbinhowever, they want zun to interact with an existing k8s (whether it is provisioned by magnum or not)03:51
mkraiMagnum integration can be later part03:51
mkraiBut it is not needed now03:51
hongbinyes, it should be optional as well03:52
mkraiWe can use our python-k8sclient :)03:52
*** diga has joined #openstack-meeting03:52
pksinghmkrai: why zun will integrate with magnum?03:52
hongbinyes, we definitely can03:52
mkraipksingh: To provision host running k8s03:52
mkraipksingh: But that is optional03:53
pksinghmkrai: do we need that vai zun?03:53
mkraipksingh: Either the operators can have their own existing k8s cluster03:53
mkraipksingh: May be in future but not sure now03:54
*** ayoung has quit IRC03:54
hongbinok, any other comment about the k8s integration?03:55
hongbinmaybe i should create a bp for that as well?03:55
mkraiyes03:55
pksinghhongbin: i think bp already exists?03:56
hongbinpksingh: really? let's me check03:56
mkraihongbin: I will test python-k8sclient this week03:56
*** Rockyg has quit IRC03:56
mkraiNot sure whether it is still working or not03:56
*** ayoung has joined #openstack-meeting03:56
hongbinpksingh: no, i couldn't find any bp about k8s integration03:57
pksinghhongbin: its different, https://blueprints.launchpad.net/zun/+spec/k8s-compatible-api03:57
hongbinpksingh: yes, this one is just a brainstormed idea03:57
hongbin#action hongbin create a bp for k8s integration03:57
pksinghhongbin: there is https://blueprints.launchpad.net/zun/+spec/coe-integration03:58
hongbincoe is a bit too general, but yes, we could link to this bp as well03:59
*** rossella_s has quit IRC03:59
hongbinok, it looks time is up03:59
mkraiThanks all!03:59
hongbinall, thanks for joining the meeting03:59
hongbin#endmeeting04:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"04:00
openstackMeeting ended Tue Nov  8 04:00:03 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-11-08-02.59.html04:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-11-08-02.59.txt04:00
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-11-08-02.59.log.html04:00
*** links has joined #openstack-meeting04:00
*** pksingh has quit IRC04:00
*** shubhams has left #openstack-meeting04:00
*** banix has quit IRC04:02
*** noslzzp has quit IRC04:02
*** noslzzp has joined #openstack-meeting04:03
*** chandrav has joined #openstack-meeting04:05
*** spzala has quit IRC04:05
*** ayoung has quit IRC04:06
*** chandrav has quit IRC04:07
*** baoli_ has quit IRC04:11
*** fzdarsky|afk has joined #openstack-meeting04:11
*** galstrom_zzz is now known as galstrom04:11
*** sudipto_ has joined #openstack-meeting04:17
*** sudipto has joined #openstack-meeting04:17
*** mkrai has quit IRC04:20
*** sudipto has quit IRC04:21
*** sudipto_ has quit IRC04:21
*** yamamoto_ has quit IRC04:25
*** kenji-i has quit IRC04:28
*** markstur_ has quit IRC04:30
*** thorst_ has joined #openstack-meeting04:31
*** armax has quit IRC04:32
*** hongbin has quit IRC04:32
*** galstrom is now known as galstrom_zzz04:34
*** liamji has joined #openstack-meeting04:34
*** dmacpher has joined #openstack-meeting04:34
*** Daisy has quit IRC04:35
*** Daisy has joined #openstack-meeting04:35
*** dmorita has joined #openstack-meeting04:37
*** Sukhdev has joined #openstack-meeting04:37
*** thorst_ has quit IRC04:39
*** Daisy has quit IRC04:40
*** dmorita has quit IRC04:41
*** aohuanxuan has joined #openstack-meeting04:43
*** gouthamr has quit IRC04:50
*** gongysh has joined #openstack-meeting04:54
*** Daisy has joined #openstack-meeting04:57
*** sudipto has joined #openstack-meeting04:59
*** sudipto_ has joined #openstack-meeting05:00
*** llu has quit IRC05:01
*** Daisy has quit IRC05:02
*** Daisy has joined #openstack-meeting05:03
*** ianychoi has joined #openstack-meeting05:03
*** gongysh has quit IRC05:05
*** yamamoto_ has joined #openstack-meeting05:06
*** yamamoto_ has quit IRC05:06
*** yamamoto_ has joined #openstack-meeting05:07
*** maeker_ has quit IRC05:10
*** maeker has joined #openstack-meeting05:10
*** yanyanhu has left #openstack-meeting05:14
*** markstur has joined #openstack-meeting05:14
*** cdub has quit IRC05:16
*** cdub has joined #openstack-meeting05:16
*** odyssey4me has quit IRC05:17
*** benj_ has quit IRC05:17
*** unicell has joined #openstack-meeting05:17
*** odyssey4me has joined #openstack-meeting05:18
*** benj_ has joined #openstack-meeting05:18
*** notmyname has quit IRC05:19
*** sc68cal has quit IRC05:19
*** Julien-zte has quit IRC05:19
*** sc68cal has joined #openstack-meeting05:19
*** notmyname has joined #openstack-meeting05:20
*** aohuanxuan has quit IRC05:21
*** gmann has quit IRC05:25
*** markstur has quit IRC05:26
*** sridharg has joined #openstack-meeting05:31
*** shintaro has joined #openstack-meeting05:32
*** anilvenkata has joined #openstack-meeting05:33
*** shintaro has quit IRC05:34
*** thorst_ has joined #openstack-meeting05:37
*** numans has joined #openstack-meeting05:42
*** claudiub has joined #openstack-meeting05:42
*** maeker has quit IRC05:44
*** markstur_ has joined #openstack-meeting05:44
*** thorst_ has quit IRC05:45
*** irenab has joined #openstack-meeting05:51
*** rcernin has joined #openstack-meeting05:54
*** takashin_ has joined #openstack-meeting05:55
*** takashin_ has quit IRC05:55
*** Fdaisuke has quit IRC05:56
*** GB21 has joined #openstack-meeting06:01
*** cdub has quit IRC06:02
*** camunoz has quit IRC06:05
*** spzala has joined #openstack-meeting06:06
*** spzala has quit IRC06:10
*** mickeys has joined #openstack-meeting06:12
*** cody-somerville has quit IRC06:13
*** markstur_ has quit IRC06:13
*** cody-somerville has joined #openstack-meeting06:14
*** cody-somerville has quit IRC06:14
*** cody-somerville has joined #openstack-meeting06:14
*** Sukhdev has quit IRC06:18
*** unicell has quit IRC06:21
*** TommyLikeHu__ has quit IRC06:23
*** sandanar has joined #openstack-meeting06:23
*** TommyLikeHu has joined #openstack-meeting06:25
*** unicell has joined #openstack-meeting06:27
*** trinaths-nxp has joined #openstack-meeting06:33
*** kaminohana has quit IRC06:35
*** lpetrut has joined #openstack-meeting06:35
*** dimtruck is now known as zz_dimtruck06:36
*** thorst_ has joined #openstack-meeting06:42
*** markvoelker has joined #openstack-meeting06:43
*** unicell has quit IRC06:43
*** cody-somerville has quit IRC06:44
*** mkoderer has joined #openstack-meeting06:44
*** unicell has joined #openstack-meeting06:46
*** acabot has quit IRC06:47
*** unicell has quit IRC06:47
*** unicell1 has joined #openstack-meeting06:47
*** markvoelker has quit IRC06:47
*** ykatabam has quit IRC06:50
*** thorst_ has quit IRC06:50
*** belmoreira has joined #openstack-meeting06:50
*** pcaruana has joined #openstack-meeting06:53
*** unicell1 has quit IRC06:54
*** unicell has joined #openstack-meeting06:55
*** iyamahat_ has quit IRC06:55
*** Ravikiran_K has joined #openstack-meeting06:56
*** unicell1 has joined #openstack-meeting07:01
*** unicell has quit IRC07:01
*** tesseract has joined #openstack-meeting07:03
*** tesseract is now known as Guest657007:03
*** david-lyle has quit IRC07:03
*** yuval has joined #openstack-meeting07:06
*** cody-somerville has joined #openstack-meeting07:10
*** cody-somerville has quit IRC07:10
*** cody-somerville has joined #openstack-meeting07:10
*** HeOS has quit IRC07:11
*** csomerville has joined #openstack-meeting07:12
*** csomerville has quit IRC07:14
*** csomerville has joined #openstack-meeting07:15
*** cody-somerville has quit IRC07:16
*** sudipto has quit IRC07:16
*** sudipto_ has quit IRC07:16
*** yamahata has quit IRC07:18
*** cody-somerville has joined #openstack-meeting07:19
*** cody-somerville has quit IRC07:19
*** cody-somerville has joined #openstack-meeting07:19
*** mickeys has quit IRC07:21
*** csomerville has quit IRC07:22
*** ebalduf has quit IRC07:23
*** andreas_s has joined #openstack-meeting07:24
*** singhj has joined #openstack-meeting07:24
*** Naeil has joined #openstack-meeting07:24
*** dmacpher has quit IRC07:28
*** yamahata has joined #openstack-meeting07:33
*** aloga_ has joined #openstack-meeting07:37
*** csomerville has joined #openstack-meeting07:45
*** singhj has quit IRC07:45
*** lpetrut has quit IRC07:46
*** jprovazn has joined #openstack-meeting07:47
*** thorst_ has joined #openstack-meeting07:47
*** cody-somerville has quit IRC07:48
*** lpetrut has joined #openstack-meeting07:52
*** numans has quit IRC07:53
*** thorst_ has quit IRC07:55
*** takashi has joined #openstack-meeting07:56
*** HeOS has joined #openstack-meeting07:58
eranrom#startmeeting storlets07:59
openstackMeeting started Tue Nov  8 07:59:54 2016 UTC and is due to finish in 60 minutes.  The chair is eranrom. Information about MeetBot at http://wiki.debian.org/MeetBot.07:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:59
*** openstack changes topic to " (Meeting topic: storlets)"07:59
openstackThe meeting name has been set to 'storlets'07:59
eranromHi08:00
*** akihito has joined #openstack-meeting08:00
takashio/08:00
eranromtakashi: Hi!08:00
*** elynn has left #openstack-meeting08:00
*** yanyanhu has joined #openstack-meeting08:00
eranromagenda is here: https://wiki.openstack.org/wiki/Meetings/Storlets08:01
eranromany other topics?08:01
*** mickeys has joined #openstack-meeting08:01
takashieranrom: thanks for updating. no other things from my side08:01
eranromok. Does the order seem right?08:02
*** mickeys has quit IRC08:02
*** lhx_ has quit IRC08:02
eranromI mean as a merge order08:03
takashieranrom: you are talking about the order of big tent works?08:03
eranromyes08:03
takashieranrom: basically seems corrent for me. Maybe we don't have paricular order about 2 and 3, packaging work and keystone v3 work08:04
eranromright. I guess it does not matter.08:04
*** janki has joined #openstack-meeting08:04
takashieranrom: +108:04
takashiakihito: around?08:05
eranromI take it that 370332 is ready for a review. Is it also ready to be merged?08:05
takashieranrom: no. I still need to rebase that on your devstack change, to get rid of permission problem08:05
eranromtakashi: ok, thanks!08:06
takashieranrom: I submitted independent patch 393767 to just test that packaging work works on your devstack patch08:06
*** kota_ has joined #openstack-meeting08:06
akihitohi08:06
eranromakihito: Hi!08:06
*** tris has quit IRC08:06
takashieranrom: but I currently find timeout issues caused by very slow speed to storlets directory using copy module in ansible08:07
*** numans has joined #openstack-meeting08:07
* kota_ is in slow response mode, probably it's read only because of another meeting in paralel08:07
takashieranrom: and need to address that. Maybe I need to tar and untar the directory for copying08:07
takashikota_: np :-)08:08
eranromkota_: Hi!08:08
eranromtakashi: Just curious, in which partof the installation this happens?08:08
takashieranrom: When installing storlets code, ansible copies storlets directory to remote host before executing setup.py08:09
eranromtakashi: Does it happen at the gate or locally?08:10
takashieranrom: yes08:10
takashieven if the target host is localhost, I find performance issue about copy modules08:10
eranromtakashi: interesting.08:11
eranromThis actually brings me to the next topic: Will we need the ansible scripts once porting to devstack?08:11
*** matrohon has joined #openstack-meeting08:12
*** gcb has quit IRC08:13
takashieranrom: I think it is better to make them independent from our repo, but we shouldn't do that in this cycle, considering required time.08:13
*** hashar has joined #openstack-meeting08:13
eranromtakashi: agree! Once we are in (the tent) we can add repos. We could add an ansible repo for storlets deployment08:14
takashieranrom: yes08:14
eranromok. Anything else for today?08:14
takashiAfter solving copy speed problem, and confirming that my package patch can work on your devstack patch, I'll abandon my temporal patch 393767, and rebase my previous patch 370332, to make it in the final shape08:15
eranromtakashi: ok, In the mean time I will have a deeper look at 37033208:16
takashieranrom: Fortunately I didn't need so much change when rebasing, so you can see patch 370332 as a starting point08:17
*** Daisy_ has joined #openstack-meeting08:17
eranromtakashi: ok. good!08:17
takashithat's all from my side today, about packaging work. I started to read your devstack patch, but still need some time to finish reviewing it.08:18
*** trinaths-nxp has quit IRC08:18
eranromtakashi: ok, thanks08:18
*** lpetrut has quit IRC08:18
eranromSo unless there is nothing else we get back 40 minutes :-)08:19
eranromakihito: anything from your side?08:19
akihitoI modify python-support. but I don't finish...08:20
eranromakihito: ok. I started looking at the fds patch, but only half way through.08:20
*** Daisy has quit IRC08:20
akihitoplease review after finish work.08:20
*** ralonsoh has joined #openstack-meeting08:20
eranromakihito: ok08:21
*** yanyanhu has left #openstack-meeting08:21
takashieranrom: maybe we need some feedback from you about some points.  ex. there are some command types we do not understand totally.08:21
takashi(about the fd validation passed to datagram, about which curretly akihito is working08:22
eranromtakashi: sure. Do you want to bring it up now?08:22
takashieranrom: not now. maybe after akihito finishes his current work08:23
eranromtakashi: ok. sure08:23
*** trinaths-nxp has joined #openstack-meeting08:23
eranromallright, so thanks for joining!08:24
takashieranrom: I'll also have a look about yor testr patch and keystone v3 patch08:24
eranromtakashi: thanks! saw your testr comments, and will be working on the,08:24
eranromthem08:24
*** csomerville has quit IRC08:24
*** gcb has joined #openstack-meeting08:25
takashieranrom: thanks08:25
takashieranrom: maybe with these patches we address all homework for big tent joining, execpt for copy right header, right?08:25
takashithese patches = devstack, packaging, testr and keystonev308:25
eranromtakashi: I believe so, I will confirm that with the etherpad page. Also, I will take care of the headers as step 608:26
takashierarnom: thanks!08:26
eranromand if this is all. I will turn to flaper87 to have a look08:27
eranromand then get back to the tc08:27
takashieranrom: makes sense08:27
*** csomerville has joined #openstack-meeting08:28
eranromok. so thanks again for joining!08:28
takashieranrom: thank you. have a nice day!08:28
akihitothank you!08:28
eranrom#endmeeting08:28
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:28
openstackMeeting ended Tue Nov  8 08:28:53 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storlets/2016/storlets.2016-11-08-07.59.html08:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storlets/2016/storlets.2016-11-08-07.59.txt08:28
openstackLog:            http://eavesdrop.openstack.org/meetings/storlets/2016/storlets.2016-11-08-07.59.log.html08:28
*** links has quit IRC08:29
*** kota_ has left #openstack-meeting08:29
*** tovin07_ has joined #openstack-meeting08:31
*** frasantoro has joined #openstack-meeting08:32
*** tris has joined #openstack-meeting08:38
*** fzdarsky|afk is now known as fzdarsky08:38
*** toscalix has joined #openstack-meeting08:42
*** phil has joined #openstack-meeting08:43
*** markvoelker has joined #openstack-meeting08:43
*** Wenzhi has quit IRC08:44
*** phil is now known as Guest7633908:44
*** links has joined #openstack-meeting08:44
*** markvoelker has quit IRC08:48
*** Daisy_ has quit IRC08:49
*** rbartal has joined #openstack-meeting08:49
*** zhangshuai has joined #openstack-meeting08:51
*** leon_wang has joined #openstack-meeting08:52
*** rasca has joined #openstack-meeting08:53
*** thorst_ has joined #openstack-meeting08:54
*** sudipto has joined #openstack-meeting08:54
*** sudipto_ has joined #openstack-meeting08:54
*** Daisy has joined #openstack-meeting08:55
*** thorst_ has quit IRC08:59
*** oshidoshi has joined #openstack-meeting08:59
*** Daisy has quit IRC09:00
*** Daisy has joined #openstack-meeting09:00
*** shu-mutou is now known as shu-mutou-AWAY09:02
*** saggi has joined #openstack-meeting09:02
saggi#startmeeting09:02
openstacksaggi: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'09:02
saggi#startmeeting karbor09:02
openstackMeeting started Tue Nov  8 09:02:41 2016 UTC and is due to finish in 60 minutes.  The chair is saggi. Information about MeetBot at http://wiki.debian.org/MeetBot.09:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:02
*** openstack changes topic to " (Meeting topic: karbor)"09:02
saggiHi everyone09:02
openstackThe meeting name has been set to 'karbor'09:02
*** zengchen has joined #openstack-meeting09:02
*** numans has quit IRC09:02
leon_wanghi09:02
xiangxinyonghello09:02
*** mickeys has joined #openstack-meeting09:03
zengchenhello guys.09:03
saggiSorry for being a bit late, was busy looking at patches09:03
yuvalhey09:03
saggiSpeaking on patches....09:04
saggi#topic The way to stability09:04
*** openstack changes topic to "The way to stability (Meeting topic: karbor)"09:04
saggiI spent the last couple of days triaging all the bugs on launchpad09:04
saggiThat means setting priorities and deciding what should get in Ocata.09:05
saggiPatch sets that relate to bugs should get a much higher priority in review than other patches.09:05
saggiAlso, fixing bugs is of higher priority than cleanups.09:06
*** spzala has joined #openstack-meeting09:06
saggiFurther more, please open bugs on things that you know are broken. I will triage bugs every morning so we know what we need to do.09:06
*** mickeys has quit IRC09:07
xiangxinyongok09:08
saggiCurrently what is being stable means is only in our heads. It's better that we have a list of things we need to fix.09:08
*** nmagnezi has joined #openstack-meeting09:09
xiangxinyongdo we need to mark them in the lauchpad?09:09
saggiPlease make sure to make the bug reports detailed and easy to understand even out of context since someone else might fix the problem you found09:10
*** links has quit IRC09:10
saggixiangxinyong: It should be automatic09:10
leon_wangok09:10
saggiIf you set the proper headers in gerrit09:10
saggihttps://wiki.openstack.org/wiki/GitCommitMessages09:10
*** spzala has quit IRC09:11
yuvalbtw, chenying and zhonghua-lee here too?09:11
*** epico has quit IRC09:12
*** yangyapeng has joined #openstack-meeting09:12
xiangxinyongthey are not available09:12
saggiJust to sum up. If you see a problem and you can't send a patch immediately, open a bug. Otherwise things fall through the cracks.09:12
saggiI will send an email to the mailing list and CC chenying and zhonghua-lee about it09:13
xiangxinyongsaggi:great09:13
xiangxinyongdo you mean every patch needs a bug or bp?09:14
yuvalwe have some bugs with inactive assignee, I think09:14
saggixiangxinyong: It will get higher priority review from me and yuval. Also if a bug exists for the problem you are fixing you will need to set the bug in the commit message.09:15
xiangxinyongsaggi: agree09:15
xiangxinyongthe Standard commit message is important09:16
leon_wangxiangxinyong:couldn't agree more.09:17
*** LiChunyu has joined #openstack-meeting09:17
xiangxinyong:)09:17
leon_wangoften be confused with the patch which doesn't contain any commit message :(09:18
saggiNeedless to say, working on fixing bugs is top priority.09:18
zengchentotally agree.09:19
saggi#topic Adding Karbor into Kolla and implementing container deployment (xiangxinyong)09:19
*** openstack changes topic to "Adding Karbor into Kolla and implementing container deployment (xiangxinyong) (Meeting topic: karbor)"09:19
xiangxinyongwe discuss the feature with kolla team members. zhanglei and caiwei09:20
saggixiangxinyong: This relates to ease of installation so we might fit in the the O cycle. But I wonder what we need to change code wise for this to work.09:21
zhangshuaizhanglei and caowei09:21
xiangxinyongzhangshuai: are you around?09:21
xiangxinyongzhangshuai is working on it09:22
zhangshuaisaggi:no09:22
xiangxinyongI guess we only need to give the installation documents to kolla team09:22
saggixiangxinyong: can they convert the devstack scripts?09:23
*** epico has joined #openstack-meeting09:23
zhangshuaithey make it as a docker image09:23
zhangshuaixiangxinyong:you are right.09:23
yuvalI believe working on OpenStack Ansible deployment first could help09:23
*** links has joined #openstack-meeting09:23
*** Daisy has quit IRC09:24
xiangxinyongyeah. caowei from 99cloud is an expert09:24
saggizaneb: What is the the delta between kolla and openstack-ansible09:24
*** strigazi_AFK is now known as strigazi09:25
xiangxinyongbut unfortunately caowei is not here today.09:25
xiangxinyongIt is easy for him to submit a patch in kolla to do this work09:26
*** Daisy has joined #openstack-meeting09:27
xiangxinyongit is very well for karbor and kolla09:27
saggiWhat will the patch do is it a Dockerfile?09:27
xiangxinyongsaggi: not sure. but zhangshuai and caowei are working on it.09:28
zhangshuailike https://review.openstack.org/#/c/37490809:28
*** ddeja has left #openstack-meeting09:29
xiangxinyongzhangshuai: thanks09:29
*** huanxuan has joined #openstack-meeting09:29
*** saggi has left #openstack-meeting09:29
*** saggi has joined #openstack-meeting09:29
zhangshuai:)09:29
leon_wangzhuangshuai:great09:30
saggizhangshuai, xiangxinyong: Great, Please put me as a reviewer for any patches for Karbor in Kolla.09:30
yuvalme too please09:30
xiangxinyong:) no problem.09:30
zhangshuaisaggi,yuval: ok,  thank you.09:31
saggi#topic Karbor integrated with Freezer Plan (xiangxinyong)09:31
xiangxinyongwe could keep touch with kolla's guys09:31
*** openstack changes topic to "Karbor integrated with Freezer Plan (xiangxinyong) (Meeting topic: karbor)"09:31
saggixiangxinyong: sure09:31
xiangxinyongyangyapeng: are you around?09:31
yangyapengxiangxinyong: yeah09:32
xiangxinyongwelcome to join this meeting09:32
xiangxinyongyangyapeng from 99cloud is the freezer's core member09:32
yangyapeng:)09:32
xiangxinyonghe is very kind09:32
leon_wanghi yapeng09:33
*** trinaths-nxp has left #openstack-meeting09:33
saggihi yangyapeng09:33
yuvalhey yangyapeng09:33
yangyapenghello  guys :)09:33
saggiI have my ideas on how to integrate but I'd much rather hear what yangyapeng has to suggest.09:33
xiangxinyongsaggi: do we have some plans to integrate with freezer.?09:33
saggiYes09:34
saggiIt depends on freezer plugins09:34
yangyapengwhether it have a  details  in etherpad09:35
* saggi is looking for the freezer etherpad09:35
xiangxinyongsaggi: may we develop a freezer plugin to connect freezer?09:35
saggiyangyapeng: can't find the etherpads from BCN : https://wiki.openstack.org/wiki/Design_Summit/Ocata/Etherpads09:35
*** zhhuabj_ has quit IRC09:36
yuvalhttps://etherpad.openstack.org/p/freezer_other_roadmap_ocata09:36
yuvalhttps://etherpad.openstack.org/p/freezer_new_archi09:36
*** adiantum has joined #openstack-meeting09:36
saggiThe last one09:36
saggiSo if we look at what we need from freezer. It's guest cooperation.09:37
*** dmorita has joined #openstack-meeting09:38
*** lhx_ has joined #openstack-meeting09:38
saggiFile level backups don't really make much since for the Karbor story. So what we want to do is invoke freezer and have it tell the applications to prepare for backup.09:38
saggiThan we create the backup the usual Karbor way.09:39
*** zhonghua has joined #openstack-meeting09:39
saggiThe main question is if we can pass configuration about plugins in the API call itself.09:40
saggiInstead of creating plans in freezer09:40
*** Daisy has quit IRC09:40
*** Daisy has joined #openstack-meeting09:40
saggiyangyapeng ^^09:41
*** aloga_ has quit IRC09:41
*** chenying2016 has joined #openstack-meeting09:41
xiangxinyongsaggi: I guess creating plans in freezer is not good09:41
chenying2016hi09:41
chenying2016I am09:41
*** LiChunyu has quit IRC09:41
xiangxinyong:)09:41
saggixiangxinyong: We would like to user freezer as a stateless entity09:41
chenying2016I am late09:41
saggichenying2016: :)09:42
*** yangyapeng has quit IRC09:42
xiangxinyongsaggi: agree with you09:42
xiangxinyongsaggi: it seems like we need to do more commuications with freezer team09:42
saggiyangyapeng left09:42
*** dmorita has quit IRC09:43
*** ociuhandu has joined #openstack-meeting09:43
saggixiangxinyong: You are right. I will add an item to their weekly meeting this week to talk about statelessness.09:43
xiangxinyong^^09:43
xiangxinyongyeah. yangyapeng and Pierre-Arthur Mathieu could help us.09:44
zengchensaggi: we can simply use freezer to do what it does. just invoke its api. but the question is the configuration of freezer agent is a little complex.09:44
xiangxinyongsaggi: thank you.09:44
saggizengchen: What configuration09:44
chenying2016install09:44
chenying2016freezer09:44
saggiYes, maybe we can also get them to have an agentless option.09:45
saggiWe'll see09:45
zengchensaggi:you can see there are a little more configurations for the freezer agent. the user should know how to use them.09:46
saggichenying2016: In any case, freezer is not a mandatory requirement for karbor. We will only use it for application level consistency.09:46
zengchensaggi:i had writed a plugin of freezer.09:47
xiangxinyongzengchen: great09:47
*** ociuhandu has quit IRC09:47
yuvalthis plugin architecture is not yet merged, right?09:48
zengchensaggi:hope to see your detailf of solution.09:48
saggi#action talk to Freezer team about using freezer as a stateless entity preferably without setting up schedulers.09:48
*** zhhuabj_ has joined #openstack-meeting09:48
xiangxinyongsaggi: thanks09:48
zengchenyuval:you asked me?09:49
yuvalas a general question09:49
saggiyuval: IIRC it's in their roadmap for this cycle09:50
saggiBut I'm not sure.09:50
yuvalsaggi: thumbs up emoji09:50
saggi#topic open discussion09:50
*** openstack changes topic to "open discussion (Meeting topic: karbor)"09:50
saggiAnything else?09:50
*** pcaruana has quit IRC09:51
zengcheni have came across a question09:51
chenyingI hope the patches about the operationengine could be merged,\.09:52
saggizengchen: ...09:53
saggichenying. I'll try and do it today09:53
zengchenabout this patch (https://review.openstack.org/#/c/384062/). the unit test can pass if i use 'ostestr' to run, if it failed when i use 'tox - e py27'09:53
chenyingThe operationengine servcie could not work because of this patches.09:53
*** zhonghua has quit IRC09:54
saggizengchen: You are asking why it fails?09:54
chenyingzengchen have a problom about tox -e to run unit test.09:54
zengchenthe reason is the 'mock' can not work when the run unit test with 'tox'09:54
*** Daisy has quit IRC09:54
saggizengchen: It fails all version of python09:54
zengchensaggi:i just want to ask who know the difference between the 'ostestr' and 'tox'. I think if the 'ostestr' can work, the 'tox' can work too.09:55
saggiIt might be something in the configuration. I will have to look at it more closely to see what the problem is.09:56
zengchensaggi:yes, both py27 and py34 failed.09:56
*** ociuhandu has joined #openstack-meeting09:56
zengchensaggi:thanks. I have spent a lot of time on it. but i failed to fix it.09:57
saggizengchen: I'll try and squeeze it in my schedule.09:57
saggiAnything else?09:57
*** thorst_ has joined #openstack-meeting09:57
zengchensaggi:thanks very much.09:58
*** aloga_ has joined #openstack-meeting09:58
*** zhurong has quit IRC09:58
saggiI would like to just to thank xiangxinyong for his great suggestions for topics for this meeting. And in general trying to get Kolla and Freezer's cooperation.09:58
yuvalxiangxinyong: great job!09:59
saggiGood day everyone09:59
zengchenbye bye.09:59
saggi#endmeeting09:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:59
openstackMeeting ended Tue Nov  8 09:59:22 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/karbor/2016/karbor.2016-11-08-09.02.html09:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/karbor/2016/karbor.2016-11-08-09.02.txt09:59
openstackLog:            http://eavesdrop.openstack.org/meetings/karbor/2016/karbor.2016-11-08-09.02.log.html09:59
*** electrofelix has joined #openstack-meeting09:59
leon_wangbye09:59
*** neiljerram has joined #openstack-meeting10:00
xiangxinyongsaggi,yuval: you are welcome10:00
xiangxinyonggood bye10:00
*** klkumar has quit IRC10:00
*** ociuhandu has quit IRC10:01
*** sambetts|afk is now known as sambetts10:01
*** tovin07_ has quit IRC10:03
*** leon_wang has left #openstack-meeting10:03
*** mickeys has joined #openstack-meeting10:04
*** thorst_ has quit IRC10:05
*** klkumar has joined #openstack-meeting10:05
*** zhangshuai has left #openstack-meeting10:05
*** mickeys has quit IRC10:10
*** chenying2016 has quit IRC10:12
*** askb has quit IRC10:16
*** epico has quit IRC10:17
*** sudipto_ has quit IRC10:19
*** sudipto_ has joined #openstack-meeting10:19
*** notmyname has quit IRC10:20
*** lpetrut has joined #openstack-meeting10:27
*** notmyname has joined #openstack-meeting10:29
*** tpsilva has joined #openstack-meeting10:31
*** sshnaidm|away is now known as sshnaidm10:32
*** lpetrut1 has joined #openstack-meeting10:32
*** asselin_ has quit IRC10:33
*** lpetrut has quit IRC10:33
*** lpetrut1 is now known as lpetrut10:33
*** bobmel has quit IRC10:37
*** bobmel has joined #openstack-meeting10:38
*** numans has joined #openstack-meeting10:40
*** asselin has joined #openstack-meeting10:46
*** acoles_ is now known as acoles10:46
*** donghao has joined #openstack-meeting10:48
*** Daisy has joined #openstack-meeting10:48
*** Daisy has quit IRC10:52
*** rvasilets___ has joined #openstack-meeting10:53
*** Ravikiran_K has quit IRC10:56
*** rfolco has joined #openstack-meeting10:57
*** thorst_ has joined #openstack-meeting11:03
*** Naeil has quit IRC11:04
*** thorst_ has quit IRC11:09
*** zhhuabj_ has quit IRC11:12
*** asselin has quit IRC11:13
*** zhhuabj_ has joined #openstack-meeting11:13
*** aloga_ has quit IRC11:17
*** Kevin_Zheng has quit IRC11:18
*** fzdarsky is now known as fzdarsky|lunch11:21
*** dprince has joined #openstack-meeting11:24
*** klkumar has quit IRC11:28
*** yangyapeng has joined #openstack-meeting11:29
*** ntpttr has quit IRC11:30
*** ntpttr has joined #openstack-meeting11:31
*** chenhb has quit IRC11:31
*** stn1 has joined #openstack-meeting11:32
*** dfflanders has quit IRC11:33
*** yangyapeng has joined #openstack-meeting11:34
*** stn1 has quit IRC11:34
*** chenhb has joined #openstack-meeting11:34
*** oshidoshi has quit IRC11:36
*** oshidoshi1 has joined #openstack-meeting11:36
*** rtheis has joined #openstack-meeting11:40
*** oshidoshi1 has quit IRC11:42
*** sudipto has quit IRC11:45
*** sudipto_ has quit IRC11:45
*** liamji has quit IRC11:48
*** brucetan has joined #openstack-meeting11:54
*** spotz_zzz is now known as spotz11:57
*** spotz is now known as spotz_zzz11:59
*** hashar has quit IRC12:03
*** zhurong has joined #openstack-meeting12:05
*** Naeil has joined #openstack-meeting12:07
*** hoangcx has joined #openstack-meeting12:08
*** banix has joined #openstack-meeting12:08
*** hoangcx has quit IRC12:11
*** zhurong has quit IRC12:13
*** cdub has joined #openstack-meeting12:15
*** takashi has left #openstack-meeting12:16
*** hashar has joined #openstack-meeting12:20
*** zhurong has joined #openstack-meeting12:21
*** aloga_ has joined #openstack-meeting12:21
*** aloga_ has joined #openstack-meeting12:21
*** oshidoshi has joined #openstack-meeting12:22
*** aloga_ has quit IRC12:23
*** aloga_ has joined #openstack-meeting12:23
*** rodrigods has quit IRC12:25
*** rodrigods has joined #openstack-meeting12:26
*** yamamoto_ has quit IRC12:26
*** dmacpher has joined #openstack-meeting12:26
*** banix has quit IRC12:28
*** e0ne has joined #openstack-meeting12:36
*** david-lyle has joined #openstack-meeting12:37
*** rossella_s has joined #openstack-meeting12:37
*** zhurong has quit IRC12:38
*** GB21 has quit IRC12:38
*** yanyanhu has joined #openstack-meeting12:40
*** mkoderer has quit IRC12:42
*** zhurong has joined #openstack-meeting12:43
*** markvoelker has joined #openstack-meeting12:45
*** ishafran has joined #openstack-meeting12:47
*** lvdongbing has joined #openstack-meeting12:49
*** markvoelker has quit IRC12:50
*** Ruijie has joined #openstack-meeting12:50
*** lhx_ has quit IRC12:50
*** thorst_ has joined #openstack-meeting12:50
*** Hosam has joined #openstack-meeting12:52
*** fzdarsky|lunch is now known as fzdarsky12:52
*** astarove_ has quit IRC12:55
*** zz_dimtruck is now known as dimtruck12:56
*** akihito has quit IRC12:56
*** e0ne has quit IRC12:56
*** aloga_ has quit IRC12:58
yanyanhu#startmeeting senlin13:00
openstackMeeting started Tue Nov  8 13:00:03 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
yanyanhuhello13:00
Ruijieevening :)13:00
yanyanhuhi, Ruijie, evening :)13:00
lvdongbinghi, yanyan, ruijie13:01
*** trown|outtypewww is now known as trown13:01
Qiminghi13:01
yanyanhuhhi, lvdongbing, Qiming13:01
yanyanhulets wait for a while for other attenders13:01
yanyanhuhttps://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Agenda_.282016-11-01_1300_UTC.2913:01
*** lixinhui_ has joined #openstack-meeting13:01
yanyanhuhere is the agenda, please feel free to add items you want to discuss13:02
*** elynn has joined #openstack-meeting13:02
yanyanhuhi, lixinhui_13:02
elynnhi13:02
lixinhui_hi, yanyanhu13:02
yanyanhuhi, elynn13:02
lixinhui_hi elynn13:02
yanyanhuok, lets move on13:02
Hosamhi everybody13:02
yanyanhu#topic ocata work items13:02
*** openstack changes topic to "ocata work items (Meeting topic: senlin)"13:02
*** XueFeng has joined #openstack-meeting13:02
*** sudipto_ has joined #openstack-meeting13:02
*** sudipto has joined #openstack-meeting13:03
yanyanhuhttps://etherpad.openstack.org/p/senlin-ocata-workitems13:03
*** hoangcx has joined #openstack-meeting13:03
yanyanhuocata workitems13:03
yanyanhuhi, XueFeng13:03
XueFenghi,all13:03
lixinhui_hi13:03
yanyanhuok, lets first go through the item list13:03
yanyanhuperformance test, still no progress, didn't get time to work on it recently13:03
*** oferby has joined #openstack-meeting13:03
yanyanhuHA13:04
yanyanhuhi, Qiming, lixinhui_, any update about it?13:04
lixinhui_I tried mistral13:04
lixinhui_with basic flow13:04
yanyanhunice13:04
lixinhui_and still can not quiet underdtand its definition about flow switch13:05
lixinhui_will investigate more there13:05
*** pradk has joined #openstack-meeting13:05
yanyanhuok13:05
yanyanhuthanks for the effort on this13:05
lixinhui_and I am not sure if we will put the actions into senlin or mistral itself13:05
lixinhui_by "actions", I mean mistral flow actions13:05
yanyanhuyou mean?13:06
Qimingit is a question of engine-centric HA solution or workflow-centric HA solution, I guess13:06
yanyanhuusing senlin to drive the workflow or using mistral to drive it?13:06
lixinhui_if put inside senlin, that means senlin will maitain the flow for recovers or some cluster management purpose13:06
lixinhui_if put them inside mistral13:06
*** spzala has joined #openstack-meeting13:06
*** diablo_rojo_phon has joined #openstack-meeting13:07
lixinhui_then users need to maintain there13:07
yanyanhuok, so any pro or con for these two choices?13:07
*** toscalix_ has joined #openstack-meeting13:07
yanyanhulike a template?13:07
lixinhui_if we wanna leverage mistral flow as recover of senlin13:07
lixinhui_seems we should maintain them13:08
lixinhui_yes13:08
yanyanhuI see13:08
lixinhui_I assume the flow template should be put together with the actions together13:08
*** Hosam has quit IRC13:08
lixinhui_and openstacksdk does not support mistral today13:08
Qimingit is like the design choice we were facing when modeling ceilometer alarms13:08
*** hoangcx has quit IRC13:08
*** rossella_s has quit IRC13:09
yanyanhuQiming, have the same feeling13:09
lixinhui_so we should leave them inside mistral13:09
yanyanhuif so, maybe maintaining the workflow in mistral is better choice, for it is the service for 'workflow' management :)13:09
Qimingit seems reasonable to manage those workflows in senlin, however it doesn't make a lot senses13:10
lixinhui_ok13:10
*** miaohb has joined #openstack-meeting13:10
Qimingif possible, maybe we can have a /contrib directory and get the worflow abstracted there13:10
yanyanhugood idea13:11
yanyanhuas examples for users13:11
*** spzala has quit IRC13:11
elynncontrib +113:11
lixinhui_:)13:11
Qimingthen we discuss whether we want to keep just a reference to the mistral work flow or we keep the whole workflow definition13:11
lixinhui_what is the reference idea?13:11
Qimingmaking decision without checking the code would be difference13:12
lixinhui_I think they are python files and yaml...13:12
yanyanhumake senses. With that, we can better tell whether holding those workflows inside senlin makes sense13:12
Qiminguser create a workflow in mistral, we reference it and trigger it when evaluating the health policy13:12
lixinhui_for example13:12
Qimingif needed, we can provide inputs and grab outputs from those workflows13:13
lixinhui_how for users to know how many flows they can choose13:13
lixinhui_yes13:13
lixinhui_Qiming13:13
lixinhui_that is what we may need do13:13
lixinhui_I mean13:13
lixinhui_to grab recover related flows and list them in senlin13:14
Qimingif we provide those choices to users thru senlin, senlin becomes a proxy of mistral, it buys user nothing other than overhead13:14
lixinhui_not really13:14
*** markvoelker has joined #openstack-meeting13:14
Qimingthe workflow is supposed to be created by the same user13:14
*** hoangcx has joined #openstack-meeting13:14
*** hoangcx has quit IRC13:14
lixinhui_please think from the perspective that senlin acts as cluster manager13:14
lixinhui_user will wanna to know what kinds of choice we provide for the cluster recover13:14
Qimingjust a quick thought, there are many other alternatives13:15
lixinhui_and do not wanna to jump out and use other tools13:15
Qimingif a workflow-centric solution makes more sense, I'm fine with it13:15
Qimingit means we don't need to provide any additional support to this13:15
Qimingby we, I mean senlin engine13:15
Qimingusing openstack is about using a collection of tools13:16
Qimingall those tools are exposed thru horizon (the single web UI) or the openstackclient (the sole command line interface)13:16
Qimingyou cannot say you are jumping from one tool to another13:17
lixinhui_if we wanna sell it, the story may be need more useful experience13:17
lixinhui_anyway13:17
*** maeca1 has joined #openstack-meeting13:17
yanyanhulixinhui_, +113:17
yanyanhuI think we need more investigation result to help us to make the decision13:17
*** adreznec has quit IRC13:17
lixinhui_yes13:17
*** Hosam has joined #openstack-meeting13:17
lixinhui_yanyanhu13:17
*** haiwei_ has joined #openstack-meeting13:17
Qimingusers don't care it is mistral or senlin or whatever13:17
lixinhui_that is the reason why they wanna good entry point13:18
lixinhui_:)13:18
Qimingthe community is not there yet, but I think that is the right direction13:18
lixinhui_I will investigate more then return here for more discussion13:18
yanyanhugreat13:18
lixinhui_agree, Qiming13:18
*** Liuqing has joined #openstack-meeting13:18
yanyanhuwill wait for it, then lets have further discussion on it13:19
lixinhui_:)13:19
*** Liuqing has quit IRC13:19
yanyanhuok, lets move on?13:19
lixinhui_yes, please13:19
*** miaohb has quit IRC13:19
yanyanhuDocument, no new work here?13:20
*** miaohb has joined #openstack-meeting13:20
*** adreznec has joined #openstack-meeting13:20
yanyanhuversioned request13:20
*** Liuqing has joined #openstack-meeting13:20
yanyanhuit is in good progress I think13:20
*** toscalix__ has joined #openstack-meeting13:20
yanyanhucluster support has been done by Qiming I think13:20
yanyanhuand node support has been done as well13:20
yanyanhuI'm now working on receiver, Ruijie is working on policy and lvdongbing is working on profile?13:21
*** lamt has joined #openstack-meeting13:21
Qimingclaim: I'm moving away from that work now13:21
yanyanhujust noticed lvdongbing proposed the patch for versioned request support for profile :)13:21
Qimingguys pls feel free to pick up any other resources/apis to work13:21
yanyanhuQiming, thanks a lot for that concrete basement u built for this job :)13:21
yanyanhusure13:21
XueFengOK13:21
yanyanhuhope we can finish it soon since that's the prerequisite of other refactoring/new features13:22
Qiminglooking forward, I'm hoping we can rework the common.schema module, use versioned object to define profiles and policies13:22
*** julim has joined #openstack-meeting13:22
Qimingthen we get free versioning support13:23
yanyanhuQiming, yes, that should be managed using versioned obj as well13:23
Qimingand we unify all those schemas under json schema13:23
yanyanhuyep13:23
*** toscalix_ has quit IRC13:24
yanyanhuBTW, guys, plz add an item into etherpad with your name followed before starting work on support for some resources13:24
yanyanhuit will be helpful to avoid conflict and duplicated effort13:24
*** kylek3h has joined #openstack-meeting13:24
yanyanhuok, next one13:25
yanyanhucontainer profile13:25
yanyanhuhi, haiwei_13:25
yanyanhuany new progress?13:25
Qimingseems patch 368539 will never make its way in13:25
yanyanhuhttps://review.openstack.org/#/c/368539/13:26
yanyanhuthis one13:26
Qimingat the same time, https://review.openstack.org/#/c/394896/ is coming in to remove the dependency13:26
Qimingwe discussed about this on at Barcelona13:26
haiwei_yanyanhu, just made a patch to remove container node infor from cluster dependents as we discussed in the summit13:26
yanyanhuhaiwei_, ok13:26
*** ljxiash has joined #openstack-meeting13:26
Qimingthe correct dependency is: cluster <-------- profile <--------- container cluster/node13:27
*** aloga_ has joined #openstack-meeting13:27
Qimingthe second dependency is already enforced, but the first one is not yet13:27
haiwei_yes, I am doing it that way13:28
Qimingwe can still delete a cluster even if it is referenced by a (container) profile13:28
*** kylek3h has quit IRC13:28
haiwei_patch 368539 will be modified or abandon13:28
Qimingokay13:28
Qimingwe can reuse the same db schema13:28
yanyanhugreat13:29
*** david-lyle has quit IRC13:29
XueFengWill read and study this13:30
Qimingjust that cluster1.dependents['profile'] == a_container_profile now13:30
yanyanhuI see13:30
Qimingthat dependency is created when the container profile is created13:30
*** miaohb has quit IRC13:30
Qimingcluster1.dependents can still contain other dependencies later ...13:31
haiwei_you mean we should input container profile type into 'dependents' of cluster? qiming13:31
Qimingprofile id13:31
haiwei_ok13:31
Qimingwhen no profile object is created, the dependency doesn't exists13:31
*** yamamoto has joined #openstack-meeting13:32
*** yamamoto has quit IRC13:32
yanyanhucool, will help to review the patch as well13:32
*** yamamoto has joined #openstack-meeting13:32
haiwei_I will do this soon13:32
yanyanhuhaiwei_, thanks :)13:32
yanyanhuok, next one?13:32
*** links has quit IRC13:33
yanyanhuzaqar message receiver13:33
*** liamji has joined #openstack-meeting13:33
yanyanhuafter sdk 0.9.9 was released, everything is ready now13:33
yanyanhuand the integration test for message receiver works as well13:33
yanyanhu(although it is broken now for zaqar-ui installation problem at gate side...)13:33
yanyanhubut that is not our fault13:34
Qimingcool13:34
yanyanhuwill propose patch to project-config to fix it13:34
Qimingso the zaqar receiver item can be completely removed from etherpad?13:34
yanyanhuQiming, yes, I think so13:34
yanyanhuwill remove it13:34
yanyanhumaybe some more works will be done in future, but the basic workflow is ok now13:35
Qimingalready removed, \o/, I like the feeling of deleting things13:35
yanyanhuthanks :)13:35
yanyanhuhah13:35
*** toscalix__ is now known as toscalix_13:35
yanyanhuok, next one13:35
yanyanhuevent/notification13:35
yanyanhuQiming, your turn?13:35
Qimingokay, just added link to blueprint13:36
Qimingwhich needs review and approval13:36
yanyanhugreat13:36
Qimingand drafted a spec today, eyes needed for review13:36
yanyanhusure13:36
yanyanhuguys, please help to take a look at it and leave your comments :)13:37
*** zhurong has quit IRC13:37
lvdongbingok :)13:37
Qimingwould rather not waste time in meeting to go through the idea13:37
Qimingit all in the wine13:37
yanyanhuQiming, sure, will discuss it offline13:37
yanyanhu:)13:37
elynngreat13:37
yanyanhuok, next one. batch policy13:37
yanyanhuI think it has been done by Ruijie ?13:37
Ruijieno really yanyanhu13:38
yanyanhuok13:38
Ruijieit just support cluster delete and update13:38
Ruijiewant to add support to more actions13:38
yanyanhuRuijie, nice13:38
yanyanhuso lets leave it there13:38
Ruijieokay, will resume it after versioned resource support13:39
*** xyang1 has joined #openstack-meeting13:39
yanyanhuRuijie, great, and thanks for the hands on versioned req :)13:39
yanyanhuand also lvdongbing as well13:39
yanyanhuok, nextone13:39
yanyanhuNFV support/baremetal cluster13:39
yanyanhuI guess this job has not been started yet?13:40
yanyanhuwe just got some requirement for it in summit13:40
Qimingtacker side, haiwe has proposed a spec for review13:40
yanyanhuQiming, so some guys from huawei have plan to work on it?13:40
Qimingyes, haven't seen any activity yet13:41
yanyanhuQiming, yes, saw those update on spec at tacker side13:41
yanyanhuQiming, I see13:41
Qimingit is meghaa..f.a.swar ?13:41
yanyanhu:P13:41
Qimingcannot spell that project name13:41
Qimingsorry13:41
yanyanhudifficult to spell13:41
elynn...13:41
*** lhx_ has joined #openstack-meeting13:42
yanyanhuok, lets focus on the spec proposal to tacker now13:42
Qimingmeghdwar13:42
haiwei_what is that?13:42
Qiminghttps://wiki.openstack.org/wiki/Meghdwar13:43
elynnI'm also curious what is that ...13:43
Qiming edge cloud gateway13:43
yanyanhuwill read that wiki as well...13:44
elynnStill has no idea...13:44
yanyanhu:)13:44
yanyanhubecause we are lack of knowledge about NFV I think13:44
yanyanhuanyway, hope there will be more progress on it in future13:45
yanyanhuok, those are all work items in the etherpad13:45
Qimingthat wiki contains a lot info13:45
*** lblanchard has joined #openstack-meeting13:45
yanyanhuyep13:45
Qimingincluding a paste of irc log ...13:46
XueFengWill research it13:46
*** eharney has joined #openstack-meeting13:46
yanyanhumaybe it is a good start point to understand the entire background13:46
yanyanhume too :)13:46
yanyanhuoh, elynn, XueFeng, you guys are working on lock recently?13:46
*** hoangcx has joined #openstack-meeting13:46
*** rbowen has quit IRC13:46
elynnI will try to add db api13:46
yanyanhuelynn, ok13:47
yanyanhuthen we can enhance the lock cleaning logic13:47
XueFengNeed reconsider my patch13:47
yanyanhuXueFeng, I think that will be helpful to address those lock issues we met :)13:47
Qimingelynn, that db api can be called when a service is started ...13:47
yanyanhuXueFeng, thanks a lot for bring this issue up13:47
yanyanhuwe do need more thinking on it13:47
*** hoangcx has quit IRC13:48
elynnQiming: yes, then will add more codes :)13:48
*** hoangcx has joined #openstack-meeting13:48
yanyanhuelynn, great. will help to review the patch13:48
Qimingelynn, I mean here: http://git.openstack.org/cgit/openstack/senlin/tree/senlin/engine/service.py#n20313:48
elynnNot sure doing cleanse on engine start is ok or not .13:49
Qimingline 21213:49
elynnMight bring race codition.13:49
*** mriedem has joined #openstack-meeting13:49
elynnSince normally we will start multi workers.13:49
Qimingthings are still ramping up, it is a good chance to clean the room before moving in13:49
elynnAnd each worker will do this.13:50
*** ataraday has joined #openstack-meeting13:50
yanyanhudo we need extra lock here?13:50
*** baoli has joined #openstack-meeting13:50
yanyanhufor avoid this race condition?13:50
QimingI don't think each worker will do this13:50
Qimingat least we can do it before we start the RPC server13:51
elynnyes, might, but need more discuss about it.13:51
*** spzala has joined #openstack-meeting13:51
yanyanhuok13:51
Qimingok13:51
yanyanhumaybe after the patch is proposed, we can have further discussion based on it13:51
*** baoli_ has joined #openstack-meeting13:52
yanyanhuok, open discussion13:52
yanyanhu#topic open discussion13:52
*** openstack changes topic to "open discussion (Meeting topic: senlin)"13:52
yanyanhuany more topics you guys want to talk about?13:52
*** zhhuabj_ has quit IRC13:53
yanyanhuif no, maybe we can finish the meeting a little earlier13:53
Qimingone thing13:53
QimingI checked the RDO packaging thing13:53
Qimingit seems https://review.rdoproject.org/ has all of it13:54
*** tongli has joined #openstack-meeting13:54
Qimingstill no clue how to start it if we want to push senlin into RDO13:54
yanyanhuso this is a gerrit maintained by rdo team?13:55
Qimingyes13:55
Qimingseems so13:55
yanyanhuand we need to propose patch to it if we want to add senlin to it, e.g.13:55
Qimingthere is a #rdo channel, where we can ask questions13:55
yanyanhuI see13:55
yanyanhuok13:55
yanyanhuI checked the latest release of rdo(Newton), senlin is still not there13:56
*** baoli has quit IRC13:56
Qimingit is not replicated into rdo repo13:56
*** haiwei_ has quit IRC13:56
yanyanhuyes13:56
Qimingsome people got to propose it and promise to maintain it13:56
yanyanhuI see13:57
yanyanhuthat is reasonable13:57
yanyanhulike each package in debian has its maintainer13:57
*** janki has quit IRC13:57
Qimingjust some info collected recently13:58
yanyanhuok, maybe lets keep paying some attention on it13:58
Qimingwe will need to learn more when we get the request13:58
*** lindycoder has joined #openstack-meeting13:58
yanyanhuyes13:58
*** elynn has quit IRC13:59
Qimingwould be good we have a focal from core team to keep an eye on this13:59
*** janzian has joined #openstack-meeting13:59
Qimingno more from me13:59
*** ihrachys has joined #openstack-meeting13:59
yanyanhugreat, thanks for all those info, Qiming13:59
yanyanhuwill keep looking at it14:00
yanyanhutime is over14:00
yanyanhuthanks for joining the meeting14:00
yanyanhulets move back to senlin channel14:00
yanyanhu#endmeeting14:00
*** electrocucaracha has joined #openstack-meeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Tue Nov  8 14:00:17 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-08-13.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-11-08-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-11-08-13.00.log.html14:00
*** shintaro has joined #openstack-meeting14:00
*** donghao has quit IRC14:00
dasmo/14:00
*** XueFeng has quit IRC14:00
electrocucarachao/14:01
ihrachys#startmeeting networking14:01
openstackMeeting started Tue Nov  8 14:01:05 2016 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: networking)"14:01
asingh_ Hi14:01
openstackThe meeting name has been set to 'networking'14:01
*** rbowen has joined #openstack-meeting14:01
johnsomo/14:01
dasanind_Hi14:01
andreas_shola14:01
*** yanyanhu has quit IRC14:01
*** pc_m has joined #openstack-meeting14:01
* ihrachys gives a minute for everyone to wake up :)14:01
*** Ruijie has quit IRC14:01
ajoo/ :)14:01
hoangcxHi14:01
ralonsohhi14:01
bcafarelhello14:01
pc_mo/14:02
*** boden has joined #openstack-meeting14:02
ltomasbohi14:02
*** amuller has joined #openstack-meeting14:02
lindycoderhi14:02
ihrachysok let's run it thru14:02
ihrachysit will be packed today...14:02
ihrachys#link https://wiki.openstack.org/wiki/Network/Meetings14:02
*** ebalduf has joined #openstack-meeting14:02
ihrachysan attentive reader may notice that the layout of the wiki page, as well as topics covered is changed from the last time we had the meeting; that's all armando's fault :)14:03
ihrachyssome topics went away (keystonev3)14:03
ihrachyssome transformed (neutron-lib now includes announcements about breaking changes in review)14:03
*** dalvarezs has joined #openstack-meeting14:03
blogano/14:03
ihrachysand some were added for greater visibility (there is now an explicit no-api-downtime-upgrades subsection in blueprints section)14:04
ihrachysArmando believes the layout will better reflect the priorities of the team for Ocata and will help us focus on what matters14:04
*** lvdongbing has quit IRC14:04
*** john-davidge has joined #openstack-meeting14:04
ihrachys#topic Announcements14:04
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:04
ihrachys1. neutron-lib 1.0.0 is released yay!14:05
ihrachys#link http://lists.openstack.org/pipermail/openstack-dev/2016-November/106725.html14:05
*** cdub has quit IRC14:05
ihrachysthe version number (1.x instead of 0.x) does not mean the effort is complete in any way14:05
dasm\o/14:05
ihrachyswe have a lot of work to do14:05
*** aloga_ has quit IRC14:05
ihrachyswe have Ocata-1 in one or two weeks14:05
ihrachysthat will, traditionally, not include anything major :)14:06
ihrachysalso, in case you haven't noticed, we had a summit a week or two ago14:06
*** Hosam has quit IRC14:06
ihrachysdesign session chairs were asked to send recap emails to openstack-dev@ [neutron]14:06
ihrachysnova/neutron session: http://lists.openstack.org/pipermail/openstack-dev/2016-November/106478.html14:07
ihrachysneutron-server recap: http://lists.openstack.org/pipermail/openstack-dev/2016-November/106684.html14:07
ihrachysneutron-lib recap: http://lists.openstack.org/pipermail/openstack-dev/2016-November/106719.html14:07
ihrachysops/end user session: http://lists.openstack.org/pipermail/openstack-dev/2016-November/106903.html14:07
ihrachysneutron-lbaas: http://lists.openstack.org/pipermail/openstack-dev/2016-November/106911.html14:07
* HenryG sneaks in late14:07
ihrachysplease review them to stay in sync with reality14:07
ihrachysthere are probably more recaps the queue, I hope other session chairs will update the ML on their topics in due course14:07
amotokiI have to send a client one... I had a nasty cold last week. I will send it tomorrow.14:07
ihrachysamotoki: get well! and thanks.14:07
ihrachysfinally, the last organization announcement14:08
ihrachyssome of you may probably know that I will change my timezone in a month to the one not too comfortable to chair the meeting14:08
ihrachysto anticipate that, armax decided to move the responsibility for the Tuesday meeting to jlibosva starting from the next week14:08
ihrachys(who hasn't showed up today; what a shame!!!)14:08
amullerhe's taking a day off due to working when he wasn't supposed to14:08
*** irenab has quit IRC14:09
amullerI trust in our fearless leader, Jakub :)14:09
* ihrachys hoped the number of !!! reflected it was a joke!14:09
dasmamuller: i believe there is no such thing like "working when wasn't supposed to" in OpenSource ;)14:09
ajo:D14:09
ihrachysI will work with Jakub to make the transition smooth14:09
ihrachysthere is a patch for the official change at https://review.openstack.org/#/c/394716/ in case you care to vote14:09
amullerdasm: Unfortunately code monkies are actually humans14:09
ihrachyscongrats for everyone tired of me mumbling on the meeting :)14:09
amullerI hear humans need rest14:10
*** zhhuabj_ has joined #openstack-meeting14:10
dasmamuller: rumors :P14:10
ihrachysok, let's finally switch to more meaningful stuff!14:10
*** Liuqing has quit IRC14:10
electrocucarachathanks ihrachys14:10
ihrachys#topic Blueprints14:10
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:10
ihrachys#link https://launchpad.net/neutron/+milestone/ocata-114:10
ihrachysI checked the list an hour ago, and I believe the list of High importance RFEs neatly reflects reality of Ocata14:11
*** Liuqing has joined #openstack-meeting14:11
*** sridharg has quit IRC14:11
ihrachysthere are some Low importance RFEs in the list that may well slip over into a future release14:11
ihrachysthere is not much to say except...14:12
ihrachys#topic OVO/no API downtime14:12
*** openstack changes topic to "OVO/no API downtime (Meeting topic: networking)"14:12
ihrachystl;dr for those lazy to read my neutron-server recap email, we target the feature(s) to Ocata14:12
ihrachysat this point, we are looking at a significant number of transitioning patches that lack reviews14:12
ihrachys#link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db14:12
ihrachysthe link should capture most of relevant patches14:13
ajolazy or not quick enough ;)14:13
ihrachysit would be wise to give those patches some attention from core and not-yet-core reviewers in next months so that we can make progress on the switch to versioned objects for database interaction14:13
*** Liuqing has quit IRC14:14
ihrachysajo: aren't we all superhumans here? laziness is the only viable explanation.14:14
ajowow, that's a lot of patches14:14
ihrachysI understand that people are still recovering from the summit, but since the cycle is rather short, it's better not to hang on the patches for too long14:14
ajoin my case assume lazyness :)14:14
ihrachysajo: right that's a lot, and we need to squash all of them and more!14:14
*** korzen has joined #openstack-meeting14:14
* ajo takes good note of the URL to do more proactive reviews on that area14:14
ihrachyssadly some of us were and some are still distracted by other stuff, but we should get back to work, taking each and shaving it until it lands14:15
ihrachyson a relevant note, there is a spec up for review that captures the current thinking around how we plan to deliver no API dowtime upgrades in Ocata14:15
ihrachys#link https://review.openstack.org/#/q/status:open+branch:master+topic:bp/online-upgrades14:15
ihrachysthere are no more patches for the topic except the spec atm, but except more actual code changes in near future14:16
ihrachysI don't have anything specific of OVO transitioning patches to point out here, it's just a matter of working on landing those patches in queue at this point14:16
*** rbowen has quit IRC14:17
ihrachysin next meetings, we may run thru specific patches that may be blocking progress; for now, moving on14:17
ihrachys#topic Bugs and Gate failures14:17
*** openstack changes topic to "Bugs and Gate failures (Meeting topic: networking)"14:17
ihrachysbefore we bug our bug deputy (pun!) and look at the gate, I'd like to mention something14:17
ihrachys#link http://lists.openstack.org/pipermail/openstack-dev/2016-November/106906.html14:17
ihrachystl;dr ^ infra wants all projects to switch to Xenial for both newton and ocata branches in a less than a month14:17
ihrachyswhich is rather tough I admit14:18
ajode we try with our jobs?, any issues with xenial?14:18
ihrachyswe run some jobs with xenial already14:18
*** manjeets has joined #openstack-meeting14:18
ihrachysI think tempest based, and unit tests, docs, pep8 are all xenial14:18
ihrachyssome jobs are not, like grenade (?), or functional/fullstack14:18
ihrachysand I talk about master at this point14:19
ajoand what's the usual way?, replicating a job with xenial in -nv, and then switching when all is finel?14:19
*** rbowen has joined #openstack-meeting14:19
ihrachysI think jlibosva was tracking the switch for functional/fullstack14:19
ajofinel=fine14:19
ihrachysajo: or experimental path14:19
ajowell, experimental right14:19
ihrachysfor functional/fullstack, I think we have some experimental jobs that everyone can trigger and debug14:19
ajowho handled the other changes?, are we tracking this somewhere? etherpad/something ?14:20
ihrachyseven if we switch ocata to all xenial, there is a non obvious work to identify the needed backports for newton14:20
ajoI'd be glad to help a bit with that matter, I don't have lots of time, but I could try to team up and take a job14:20
ihrachysajo: yeah, at this point, I believe we need a tracker14:20
ihrachysand etherpad may be a good solution14:20
ihrachysand probably not just a tracker, but a squad team to make it to completion14:21
ihrachysbecause the time is tight14:21
ajohttps://etherpad.openstack.org/p/moving-neutron-jobs-to-xenial sounds good?14:21
ihrachysI guess I will ask armax to identify what our next steps are14:21
ihrachysajo: let's use it, yes!14:21
ihrachysajo: let's fill it in after the meeting14:22
*** eharney has quit IRC14:22
ihrachysok, so that's one high impact thing14:22
ihrachysas for day to day stuff, the gate looks quiet for the most part: http://grafana.openstack.org/dashboard/db/neutron-failure-rate14:22
ihrachysthe only suspicious thing is some tempest jobs - linuxbridge and dvr - are a bit higher in the trend, 10% and 15% correspondingly14:23
ihrachyswe may want to have someone to take a look, but overall it does not seem critical (just yet)14:24
ihrachysobviously, functional is at 15%, but unless folks step in to fix the job, it won't become better14:24
*** maeker has joined #openstack-meeting14:24
ihrachysand that's about it for the gate14:24
ihrachysas for bugs, we had several bug deputies to cover during the summit time and around it14:25
ihrachysI believe it was dasanind, dasm, and dougwig (all d's!) who handled bugs in last three weeks for us.14:25
*** eharney has joined #openstack-meeting14:25
*** lixinhui_ has quit IRC14:25
ihrachysfolks, would you like to give some brief status for weeks you covered?14:25
*** toscalix_ has quit IRC14:25
ihrachysanything critical to mention?14:26
dasmdasanind_: you first14:26
*** toscalix has quit IRC14:26
dasanind_ihrachys: there were 31 bugs and 4 RFE's14:26
dasanind_most of the bugs were medium or low and some were marked as invalid14:26
*** jgregor has joined #openstack-meeting14:27
ihrachysdasanind_: anything that you could not triage/tag yourself?14:27
dasanind_there were couple of bugs for fwaas, lbaas and cisco which I could not triage14:28
ihrachyscisco is not our scope, we just move it to networking-cisco and move on14:29
johnsomI can take a pass on the lbaas bugs14:29
ihrachysdasanind_: as long as you tag the bugs with fwaas/lbaas, that should work fine14:29
dasanind_blogan helped with the lbass bugs14:29
johnsomYep14:29
dasanind_lbass=lbaas14:29
dasanind_njohnston helped with the fwaas one14:29
ihrachysI don't think we necessarily need to triage to completeness all of them; the most important thing is to pull attention of matter experts via tags.14:29
ihrachysok cool. thanks dasanind_ for covering for us!14:30
ihrachysdasm: your turn14:30
dasmsummit week was very calm. just 3 or 4 bugs.14:30
dasmi was expecting to have *plenty* of time, but was buried under pile of other responsibilities, so currently trying to triage all outstanding bugs.14:30
ihrachyslucky you are, but not surprising :)14:30
ihrachysdasm: thanks. dougwig may have swiped through some of them already. but I suspect he won't update just now :)14:31
dasmack14:31
*** hieulq_ has joined #openstack-meeting14:31
ihrachysdasm: let's at least make sure nothing slips thru the cracks, and all bugs are tagged properly.14:31
ihrachysall new bugs I mean14:31
*** toscalix has joined #openstack-meeting14:32
*** hieulq_ has quit IRC14:32
ihrachysdasm: thanks for working on it14:32
ihrachyswe also need new volunteers to serve as bug deputies for next two weeks. anyone?14:32
andreas_sI can take one14:32
andreas_swhich doesn't matter14:32
electrocucarachaI can be after andreas_s14:33
ihrachyssold!14:33
ihrachysandreas_s: electrocucaracha: please update the wiki page after the meeting to document you are the deputies for next weeks14:33
ihrachysthanks volunteers for stepping in, that was quick this time, and I appreciate that!14:34
ihrachys#topic Docs14:34
*** openstack changes topic to "Docs (Meeting topic: networking)"14:34
*** hieulq_ has joined #openstack-meeting14:34
*** weshay is now known as weshay_vote14:34
ihrachysanyone to update us on docs?14:34
john-davidgeihrachys: Just a note that the bi-weekly netowkring guide meeting has been removed14:35
john-davidgeNetworking guide discussion will now take place in the regular documentation team meeting14:35
*** uxdanielle has joined #openstack-meeting14:35
ihrachysjohn-davidge: does it indicate it's too good or it's too bad? :)14:35
john-davidgeihrachys: It was so good everyone was too intimidated to ever join :)14:36
ihrachyshaha14:36
ihrachysbut now everything will change!!14:36
ihrachys /s14:36
ihrachysthanks john-davidge for the notice14:36
amotokiI think the main purpose of the dedicated meeting is to discuss the reorganization of the guide, but it looks over.14:36
ihrachysamotoki: makes sense. so it seems like it's 'good' in the end.14:37
* ihrachys breathes with relief14:37
ihrachyson a relevant note, we have doc bugs to squash, as usual14:37
ihrachys#link https://bugs.launchpad.net/neutron/+bugs?field.tag=doc14:37
ihrachysswipe through the list and take what you can handle (of course if it was your DocImpact patch, everyone expects you to close the loop)14:38
ihrachysI just did assign some to myself14:38
ihrachys#topic Transition to OSC14:38
*** openstack changes topic to "Transition to OSC (Meeting topic: networking)"14:38
ihrachysrtheis: are you still with us? :)14:39
*** absubram has joined #openstack-meeting14:39
ihrachysok, anyone else to update on the OSC progress?14:39
rtheisaround and wrapping up most of my work14:39
rtheisamotoki will take over14:39
amotokiafter talking with rtheis, i took over his role of OSC transition.14:39
ihrachysrtheis: thanks a lot for all your work on the topic, we are definitely in a better place now14:40
rtheisyw14:40
ihrachysto the point where we deprecated neutronclient CLI :)14:40
amotokiI was in bad health last week and I am now catching up with his role.14:40
*** absubram_ has joined #openstack-meeting14:40
amotokino solid report this week. will report next week14:40
*** jgregor has quit IRC14:41
ihrachys#link https://review.openstack.org/#/c/393903/ neutronclient CLI deprecation patch14:41
ihrachysamotoki: thanks for stepping in14:41
ihrachys#topic Neutron-lib and planned neutron refactoring14:41
*** openstack changes topic to "Neutron-lib and planned neutron refactoring (Meeting topic: networking)"14:41
*** sofianes_ has joined #openstack-meeting14:41
ihrachysas I said, 1.0.0 released lately14:41
sindhuamotoki: rtheis ihrachys : Is there a timeline/deadline for the OSC work?14:42
amotokithe main work will be done by ocata feature freeze14:42
ihrachyssindhu: I guess it's always yesterday; but no new features or even some bug fixes are now allowed in neutronclient14:42
ihrachys#link http://lists.openstack.org/pipermail/openstack-dev/2016-November/106725.html the 1.0.0 release announcement14:42
sindhuihrachys: Ok, thanks!14:42
ihrachyssince neutron-lib now adopted reno, we have a neat and easy way to advertise new developments in the library14:42
*** noama_ has joined #openstack-meeting14:43
ihrachysfor details, see in the announcement emails14:43
*** kylek3h has joined #openstack-meeting14:43
ihrachysto remind, there was a decision made on neutron-lib design session that we don't want to linger removal of the code moved into neutron-lib for too long in neutron repo, so we change the procedure for maintaining the code.14:43
HenryGAnd I hope everyone is aware of the faster adoption plan14:43
ihrachysinstead of deprecating such code for cycles in neutron repo until removal, we do the following:14:43
ihrachys1. move the code into neutron-lib14:43
ihrachys2. release a new version of the library14:43
ihrachys3. announce changes on the team meeting (in this exact section)14:43
ihrachys4. in several weeks the least, remove the code from neutron tree14:44
*** absubram has quit IRC14:44
*** absubram_ is now known as absubram14:44
ihrachysin this way, subprojects are given a chance to switch to the new code without leaving their gates broken14:44
ihrachysand neutron team can proceed with other work instead of maintaining deprecated code14:44
ihrachysquestions? critics? concerns?14:44
*** SridharP_ has joined #openstack-meeting14:44
bodenihrachys: does that apply to hacking checks as well?14:45
ihrachyssubprojects are expected to track new lib announcements, AND read meeting logs to be informed about things that may affect their gates14:45
*** jamesdenton has joined #openstack-meeting14:45
bodenperhaps thats a topic for the neutron-lib meeting14:45
*** tosky has joined #openstack-meeting14:45
*** fnaval has joined #openstack-meeting14:45
ihrachysboden: what do you mean? it applies only to neutron in-tree code that is not supposed to be shared with subprojects. hacking checks from neutron tree are afaik not used by anyone anymore14:45
ihrachysif they are, they do it wrong and should switch to neutron-lib factory/checks asap14:46
ihrachysand honestly I wouldn't cry if they are hit by a gate failure because of that at this point14:46
* ihrachys thinks how an 'evil' smiley would look like14:46
bodenihrachys: the general question is if we can roll out new hacking checks that quickly as well.. and also there are subprojects using neutron hacking check factory14:46
bodenwe can take this offline; don’t want to derail14:46
*** fnaval has quit IRC14:47
HenryGWith the new "faster" plan we must be more aggressive about the hacking checks too14:47
ihrachysboden: the new change in the process is not about how we roll in new things in neutron-lib, but about how quickly we can remove deprecated code from neutron tree14:47
*** fnaval has joined #openstack-meeting14:47
ihrachysyeah, we can discuss it in neutron-lib venue in more details14:47
ihrachysthanks for bringing it up thoug!14:47
*** noama_ has quit IRC14:47
ihrachysso one thing that is currently in review and that projects should be aware of is the removal of neutron manager code from neutron tree14:48
ihrachys#link https://review.openstack.org/#/c/386845/14:48
ihrachysI believe the new neutron-lib now includes the manager, and so all subprojects are advised to adopt it asap14:48
ihrachysor else ;)14:48
ihrachyseveryone is silent. stunned by the evil?14:49
bodenI like this new process.. “or else” ;)14:49
ihrachysok, report your complaints to your magnificent PTL14:49
HenryGI get the impression that people actually like the new plan14:49
amotokiihrachys: is it an announcement?14:50
ihrachysHenryG: haha, until they are hit by the bus :P14:50
ihrachysamotoki: it's in a way an announcement, yes; we don't know for how long the deprecation warning for the manager will stay with us, even though the current patch set leaves some deprecation path.14:50
ihrachysamotoki: or you mean more generally the announcement of the new process?14:51
*** sofianes_ has quit IRC14:51
amotokino. i think it is enough.14:51
amotokione suggestion is to use #info.14:51
*** oshidoshi has quit IRC14:51
dasmihrachys: btw "hitting by bus", is it already decided, which projects are not any longer in stadium? https://review.openstack.org/#/c/389397/14:51
*** asselin has joined #openstack-meeting14:51
ihrachysok cool. obviously, we are not completely evil, and so we will consider impact of our actions on case by case basis when ripping off code from neutron tree.14:51
electrocucarachaihrachys: just to be precise the point 4, how many weeks are we talking about?14:52
HenryGihrachys: Make an #info blurb about the new process, then I have one other lib item14:52
ihrachyselectrocucaracha: I don't think we set any specific number, but we are all adults here. I guess 2-3 would be a good compromise.14:52
*** spotz_zzz is now known as spotz14:53
ihrachys#info new neutron-lib obsolete code process in place, subprojects are to track new library releases and read meeting minutes and adopt accordingly14:53
ihrachysHenryG: your stage14:53
HenryGWe need more core reviewer attention in neutron-lib repo patches14:54
HenryGPlease. :)14:54
ihrachysI second the gentleman14:54
* ihrachys feels guilty himself14:54
bloganHenryG: im sure you're looking for just more reviews, but are you asking for more +2 power?14:55
HenryGWe have plenty of +2 power14:55
HenryGNot enough eyes on the code14:55
bloganok got it14:56
*** asselin has quit IRC14:56
ihrachysHenryG: thanks for bringing that to attention14:56
ihrachys#topic Stadium update14:56
*** openstack changes topic to "Stadium update (Meeting topic: networking)"14:56
ihrachysdasm raised a good point14:56
ihrachysas you know we had stadium revisited somewhat lately14:56
ihrachysit's still in progress14:56
ihrachysthe relevant patches are in https://review.openstack.org/#/q/topic:stadium-implosion14:56
*** acoles is now known as acoles_14:57
ihrachysarmax was assessing all stadium projects to decide which are governed well or not14:57
ihrachyssome will go out this cycle14:57
ihrachyswe will do changes in governance repos accordingly14:57
ihrachysto reflect the new world14:57
*** penick has joined #openstack-meeting14:57
ihrachysdasm: to answer your question, it's up to PTL to interpret assessments accordingly14:57
ihrachysdasm: but I hope summaries in assessments reflect the upcoming decision14:58
*** rbak has joined #openstack-meeting14:58
ihrachysreach out to armax if there are still specific questions14:58
*** penick has quit IRC14:58
ihrachysany questions on stadium thing before we close the meeting (sadly without open floor this time)?14:58
dasmihrachys: just wanted to know, if we're already finishing/finished stadium implosion. thanks14:59
ihrachysdasm: I think we imploded it previous cycles; now we are shrinking it a bit ;)14:59
dasm:D14:59
*** shintaro has quit IRC14:59
manjeets70015:00
ihrachysok thanks all stadium participants who are working on filling in identified gaps lately, it's worth some claps15:00
ihrachysok we are out of time15:00
ihrachysthanks everyone15:00
ihrachysand may the Force be with you15:00
dasanind_thanks ihrachys15:00
ihrachys#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Tue Nov  8 15:00:31 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-11-08-14.01.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-11-08-14.01.txt15:00
lindycoderThanks ihrachys15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-11-08-14.01.log.html15:00
sindhuthanks :)15:00
*** stn1 has joined #openstack-meeting15:00
dasm\o15:00
hoangcxbye15:00
*** acoles_ is now known as acoles15:00
*** pc_m has left #openstack-meeting15:01
electrocucarachabye15:01
*** ralonsoh_ has joined #openstack-meeting15:01
*** tosky has left #openstack-meeting15:01
*** electrocucaracha has left #openstack-meeting15:01
*** haleyb_ has joined #openstack-meeting15:01
*** haleyb__ has joined #openstack-meeting15:01
*** haleyb__ has quit IRC15:01
*** haleyb_ has quit IRC15:01
*** haleyb_ has joined #openstack-meeting15:02
*** ralonsoh has quit IRC15:02
*** tonytan4ever has joined #openstack-meeting15:02
*** stn2 has joined #openstack-meeting15:02
*** korzen has quit IRC15:02
amotokithanks15:04
*** yangyapeng has quit IRC15:04
*** hoangcx has quit IRC15:04
*** edtubill has joined #openstack-meeting15:04
*** stn1 has quit IRC15:05
*** Julien-zte has joined #openstack-meeting15:05
*** bobh has joined #openstack-meeting15:05
*** jgregor has joined #openstack-meeting15:06
radezHOw are you?15:07
radezsure be happy to talk15:07
*** SridharP has joined #openstack-meeting15:07
*** HeOS has quit IRC15:08
*** SridharP_ has quit IRC15:08
*** weshay_vote is now known as weshay15:08
*** amuller has left #openstack-meeting15:08
*** huanxuan has quit IRC15:08
*** jprovazn has quit IRC15:09
stn2hi15:09
*** yuval has quit IRC15:12
*** yamamoto has quit IRC15:12
*** hieulq_ has quit IRC15:12
*** hieulq_ has joined #openstack-meeting15:13
*** rossella_s has joined #openstack-meeting15:20
*** absubram has quit IRC15:22
*** lindycoder has left #openstack-meeting15:24
*** slayer has joined #openstack-meeting15:25
*** annegentle has joined #openstack-meeting15:25
*** boden has left #openstack-meeting15:27
*** yamahata has quit IRC15:28
*** haleyb_ has quit IRC15:28
*** yamamoto has joined #openstack-meeting15:28
*** yamamoto has quit IRC15:28
*** yamamoto has joined #openstack-meeting15:29
*** nmagnezi has quit IRC15:29
*** david-lyle has joined #openstack-meeting15:29
*** ishafran has quit IRC15:33
*** jgregor_ has joined #openstack-meeting15:33
*** jaugustine has joined #openstack-meeting15:33
*** galstrom_zzz is now known as galstrom15:34
*** david-lyle has quit IRC15:34
*** jgregor has quit IRC15:35
*** rrecio has joined #openstack-meeting15:37
*** dmorita has joined #openstack-meeting15:38
*** jgregor has joined #openstack-meeting15:39
*** jmckind has joined #openstack-meeting15:39
*** qwebirc69533 has joined #openstack-meeting15:40
*** tongli has quit IRC15:40
*** qwebirc69533 has quit IRC15:41
*** numans has quit IRC15:41
*** rrecio has quit IRC15:41
*** john-davidge has quit IRC15:42
*** armax has joined #openstack-meeting15:42
*** dmorita has quit IRC15:42
*** rrecio has joined #openstack-meeting15:42
*** jgregor_ has quit IRC15:42
*** singhj has joined #openstack-meeting15:42
*** sandanar has quit IRC15:43
*** balajiiyer has joined #openstack-meeting15:43
*** sukhdev has joined #openstack-meeting15:45
*** caboucha has joined #openstack-meeting15:45
*** rbartal has quit IRC15:46
*** balajiiyer1 has joined #openstack-meeting15:47
*** balajiiyer has quit IRC15:48
*** jgregor_ has joined #openstack-meeting15:50
*** ayoung has joined #openstack-meeting15:52
*** SridharP has quit IRC15:52
*** jgregor has quit IRC15:53
*** diga has quit IRC15:54
*** adiantum has quit IRC15:54
*** n-harada has joined #openstack-meeting15:54
*** balajiiyer1 has left #openstack-meeting15:55
*** tung_doan has joined #openstack-meeting15:58
*** rbak_ has joined #openstack-meeting15:58
*** belmoreira has quit IRC15:58
*** rbak has quit IRC15:58
*** diga has joined #openstack-meeting15:58
*** tbh has joined #openstack-meeting15:59
*** acoles is now known as acoles_15:59
*** sxa123 has joined #openstack-meeting16:00
*** s3wong has joined #openstack-meeting16:00
*** sxa123 has left #openstack-meeting16:00
sripriya#startmeeting tacker16:00
openstackMeeting started Tue Nov  8 16:00:56 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:01
openstackThe meeting name has been set to 'tacker'16:01
sripriyahello tackers!16:01
stn2hi16:01
sripriya#topic Roll Call16:01
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"16:01
tbho/16:01
digao/16:01
*** Guest6570 has quit IRC16:01
*** saggi has quit IRC16:01
s3wongo/16:01
n-haradao/16:01
stn2o/16:01
spzalao/16:01
sripriyatbh: diga s3wong n-harada stn2 spzala: hi!16:02
*** KanagarajM has joined #openstack-meeting16:02
tung_doanhi all16:02
KanagarajMhi16:02
*** armax has quit IRC16:02
sripriyatung_doan: KanagarajM : hi!16:03
*** galstrom is now known as galstrom_zzz16:03
sripriyai have no announcements to make, but welcome back everyone!16:03
*** galstrom_zzz is now known as galstrom16:03
*** markstur has joined #openstack-meeting16:03
*** bobh has quit IRC16:04
sripriyahope you all had a great summit and it was great meeting you fellow tackers at the summit!16:04
sripriya#chair tbh16:04
openstackCurrent chairs: sripriya tbh16:04
sripriya#tbh s3wong16:04
sripriya#chair tbh s3wong16:04
openstackCurrent chairs: s3wong sripriya tbh16:04
*** Sridharp has joined #openstack-meeting16:04
sripriyahere is the agenda for today16:05
sripriya#link https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Nov_7th.2C_201616:05
sripriyasince we have spzala here, let us start the topics from the reverse order16:05
*** henrynash has left #openstack-meeting16:05
spzalasripriya: :)16:06
spzalathanks16:06
sripriya#topic VDU targets scaling policy - nested templates16:06
*** openstack changes topic to "VDU targets scaling policy - nested templates (Meeting topic: tacker)"16:06
*** oshidoshi has joined #openstack-meeting16:07
sripriyaKanagarajM: spzala we discussed this topic in cross project design session16:07
sripriyaspzala: i believe we now have support in HT for supporting nested templates16:07
spzalaCool, sorry I missed it16:07
spzalathough thanks to tbh and bobh I have some idea on the discussion16:07
spzalasripiray: that's correct16:07
KanagarajMsripriya, sure.16:07
spzalasripriya: sorry type16:08
spzalaahh.. typo16:08
KanagarajMsripriya, spzala whats up :)16:08
spzalayou can tell not fully recovered yet :)16:08
sripriyaKanagarajM: since you implemented the scaling policy, are there any pending items from HT side which they need to take care of?16:08
*** janzian has left #openstack-meeting16:08
spzalaso with the multiple template support, I guess the expected support is API driven access to those templates16:09
sripriyaspzala: :-)16:09
spzalaKanagarajM: we have this patch in progress, https://review.openstack.org/#/c/342675/316:09
spzala:-)16:09
sripriyaspzala: looking16:09
KanagarajMsripriya, spzala , i am planning to strip of the logics from tacker once HT implement as expected16:10
KanagarajMspzala, sure. i will look into this patch16:10
*** sridharg has joined #openstack-meeting16:10
sripriyaspzala: can you brief a bit about this patch?16:10
spzalanot quite clear patch yet but as part of it, we should have an object to access translator vs a flat output16:10
spzalasripriya: :) ^^  Mathiue is working on it, and I also had comment to update the commit message with more detail for folks to understand the changes16:11
spzalasripriya: but overall as I mentioned instead of flat output of yaml file there will be an object to access templates16:11
*** manikanta has joined #openstack-meeting16:12
spzalait will create a new method that which outputs a map of filenames and their content16:12
sripriyaspzala: okay, will the object contain the yaml file?16:12
spzalayou can access a single or multiple yaml files (in case of autoscaling) with it16:13
*** Julien-zte has quit IRC16:13
spzalaKanagarajM: sripriya: is that something will work for Tacker? or you have a different need or approach16:13
spzala(suggest different approach)16:14
*** Julien-zte has joined #openstack-meeting16:14
sripriyaspzala: okay, we will now need to handle the individual files from the object in Tacker16:14
KanagarajMspzala, when nested tmpl is generated, it could be accessed via python api from HT16:14
*** Julien-zte has quit IRC16:14
*** Julien-zte has joined #openstack-meeting16:15
spzalaKanagarajM: true, that's what it's will be after the patch changes are merged16:15
*** Julien-zte has quit IRC16:15
KanagarajMonce its ready, i am planning to migrate the tacker to adhear to the new change in HT16:15
sripriyaspzala:  is the scaling patch based on the heat resource group?16:15
spzalaKanagajM: sripriya: having an object we can add more apis as well to access programmatically16:15
*** SridharP1 has joined #openstack-meeting16:16
*** Julien-zte has joined #openstack-meeting16:16
sripriyaspzala: agree16:16
spzalaKanagaraM: that sounds good.16:16
*** Julien-zte has quit IRC16:16
spzalasripriya: yes, that's true16:16
*** oshidoshi1 has joined #openstack-meeting16:16
*** Julien-zte has joined #openstack-meeting16:16
spzalasripriya: depending on how you use TOSCA policies in TOSCA yaml, you can have a translated template with Heat AutoScalingGroup or Senlin resource16:17
*** Julien-zte has quit IRC16:17
sripriyaspzala: i thought HT used the scaling policy/scaling group to create the resources16:17
*** Julien-zte has joined #openstack-meeting16:17
*** Julien-zte has quit IRC16:17
spzalasripriya: ^ the translation will be to Heat resources either ASG or Senlin related16:18
*** Julien-zte has joined #openstack-meeting16:18
*** Julien-zte has quit IRC16:18
spzalasripriya: I have this doc update created yesterday https://review.openstack.org/#/c/394673/16:18
*** Julien-zte has joined #openstack-meeting16:19
spzalasripriya: to help little bit on what to expect with autoscaling translation16:19
*** Julien-zte has quit IRC16:19
sripriyaspzala: okay, it is clear now16:19
*** oshidoshi has quit IRC16:19
*** Julien-zte has joined #openstack-meeting16:19
spzalasripriya: cool16:19
sripriyaspzala: so scaling is supported for both senlin and auto scaling group16:19
sripriyaspzala: thanks for the doc link16:20
spzalasripriya: that's true16:20
*** Julien-zte has quit IRC16:20
spzalasripriya: yrw16:20
*** eharney has quit IRC16:20
*** rcernin has quit IRC16:20
*** jgregor_ has quit IRC16:21
*** edtubill has quit IRC16:21
sripriyaKanagarajM: i guess once this is merged,  i think in tacker we can implement multiple policies with this feature right?16:21
*** slayer has quit IRC16:22
*** mageshgv has joined #openstack-meeting16:22
sripriyaspzala: any rough estimate on when this will be merged since tacker is dependent on this patch16:22
spzalaKanagarajM: once the merge conflict is resolved for https://review.openstack.org/#/c/342675/3 if you can please review it that would be great.16:22
KanagarajMspzala,  sure16:22
KanagarajMsripriya, yes hope so. i need to see how HT will expose the feature16:22
spzalasripriya: I actually just talked to Mathiue this morning and we have that discussion in the patch itself, we are shooting for around two weeks16:23
spzalaKanagarajM: cool, thanks!!16:23
sripriyaKanagarajM: spzala: thanks!16:23
spzalasripriya: yrw16:24
sripriyaspzala: while you are here, i wanted to ask quickly on NSD support in TP, we touched a bit on the NFV profile 1.0 for NSD to integrate VNFFG16:24
sripriyaspzala: in tacker design session16:25
spzalasripriya: sure16:25
sripriyaspzala: i remember trozet (who implemented the VNFFG feature) discussed about the inconsistency in tosca doc vs what is implemented in TP16:25
trozethi sripriya16:26
spzalasripriya: ahhh..16:26
sripriyaspzala: did you happen to have more information on this?16:26
spzalasripriya: trozet: it would be great if you can open a bug against TP with detail on it16:26
sripriyatrozet: hello!16:26
sripriyatrozet: i was just discussing with spzala on NSD support for VNFFG16:27
sripriyatrozet: spzala: we plan to implement NSD in this current cycle, and right now node types for VNFFG are hosted in tacker's nfv defs16:27
spzalasripriya: trozet: a bug with more on current inconsistency would be very helpful16:28
sripriyatrozet: feel free to provide more information on this16:28
sripriyaspzala: sure16:28
*** edtubill has joined #openstack-meeting16:28
*** diablo_rojo_phon has quit IRC16:28
*** chris_morrell has joined #openstack-meeting16:29
sripriyatrozet: as spzala requested, please create a bug for this in TP, hopefully we can move the node types from Tacker to TP16:29
spzalasripriya: trozet: great, we will fix it with priority or please feel free to provide/update solution if you can16:29
trozetsripriya, spzala: is "TP" tosca parser?16:29
sripriyaspzala: thanks16:30
spzalatrozet: that's true16:30
sripriyatrozet: yes :-)16:30
spzala:-)16:30
spzalaTP and HT .. lol16:30
*** uxdanielle has quit IRC16:30
spzalacan be confusing16:30
*** Sridharp has quit IRC16:30
sripriyaspzala: it will be great if you can let us know any significant features coming up on this cycle16:30
trozetspzala, sripriya: i think i fixed one bug already16:31
sripriyatrozet: link?16:31
spzalasripriya: sure I will be updating on it. On the same line, from Tacker side any new feature requests can be documented or opened up a blueprint that would be great16:31
trozetspzala, sripriya: https://review.openstack.org/#/c/321312/16:32
*** Janki has joined #openstack-meeting16:32
spzalatrozet: I guess that was some long time back16:32
sripriyaspzala: right16:32
trozetsripriya, spzala: i think the problems we faced with VNFFG were centered around that we are not providing a full NSD to TP16:33
spzalasripriya: yup, so if it's already fixed that's great16:33
*** rossella_s has quit IRC16:33
trozetsripriya, spzala: so when we provided a VNFFG with members, TP had no idea where the VNFD and VL definitions were16:33
trozetsripriya, spzala: so it would error16:33
*** chris_morrell has quit IRC16:33
sripriyatrozet: does substitution mapping help here?16:34
trozetsripriya: i'm not sure.  I think we just need to implement full NSD in tacker and then see what we hit with TP16:35
spzalasripriya: I doubt16:35
sripriyatrozet: spzala okay16:35
spzalaI agree .. sub mappings is more general abstraction16:35
*** baoli_ has quit IRC16:35
*** Leo_ has joined #openstack-meeting16:36
sripriyatrozet: okay, are you dependent on the NSD spec which dkushwaha is working on16:37
*** hieulq_ has quit IRC16:37
trozetsripriya: my thought was leave vnffg as it is and add the NSD layer on top of it.16:38
trozetsripriya: then parsing NSD will just result in VNFM calls and the vnffg NFVO calls16:38
sripriyatrozet: i'm trying to see how we can identify the NSD requirements for VNFFG to let TP know on the gaps16:40
sripriyatrozet: NSD spec is going to take some time to implement16:40
trozetsripriya: it should be fairly easy right?  All the underlying pieces are there, just more up front parsing and calls to existing methods16:40
sripriyatrozet: well NSD spec needs mistral integration and we plan to build a workflow generator for the same16:42
sripriyatrozet: it may be go through few more iterations even though the actual NSD feature implementation is straight forward16:42
sripriyatrozet: the more i think of this, we can try to have a version 0.1 without the mistral support and see where we stand, we can then continue to iterate over the feature to bring in mistral support hopefully with minimal impact16:45
*** yamamoto has quit IRC16:46
sripriyamoving on to next topics...16:46
tbhsripriya, I think that's the better approach16:46
sripriyadkushwaha, mike_m ping?16:46
sripriyatbh: yes16:46
*** jaypipes has quit IRC16:46
*** slayer has joined #openstack-meeting16:47
sripriya i do not see them here in the channel, i will sync up with them offline16:47
sripriya#topic Barcelona Summit Roundup16:48
*** openstack changes topic to "Barcelona Summit Roundup (Meeting topic: tacker)"16:48
*** chandrav has joined #openstack-meeting16:48
*** yamahata has joined #openstack-meeting16:48
sripriyathank you for attending the tacker design sessions, we had some good discussions around specific topics we outlined in the etherpad16:49
sripriya#link https://etherpad.openstack.org/p/tacker-ocata-summit16:49
sripriyathe etherpad is updated with high level notes that were captured in the design sessions16:49
*** chandrav has quit IRC16:50
sripriyai plan to send a ML summary as well on the design sessions soon16:50
*** lhx_ has quit IRC16:50
sripriyadid anyone have followup questions based on the discussions we had in the summit?16:51
sripriyai think the major action item for supporting VMware infra as a VIM in tacker is to refactor our VIM module16:53
*** yamahata has quit IRC16:53
sripriyacurrently we have openstack keystone related attributes exposed at the API level, we need to revisit that to make it more generic and consumable for any VIM16:54
*** cdub has joined #openstack-meeting16:54
*** stn2 has left #openstack-meeting16:54
sripriyaon the other topics, esp. on containers, we need to evaluate further on zun or go with specific container plugins16:55
sripriyatbh: did you want to add more on this?16:55
*** stn2 has joined #openstack-meeting16:55
*** rcernin has joined #openstack-meeting16:56
*** tonytan4ever has quit IRC16:56
tbhsripriya, regarding zun, I think they are planning to redesign the container-create process16:56
*** stn2 has left #openstack-meeting16:56
sripriyatbh: i see, is this on the API level?16:56
*** singhj has quit IRC16:56
*** marchetti has joined #openstack-meeting16:56
*** tonytan4ever has joined #openstack-meeting16:56
tbhsripriya, nope, mostly implementation part16:57
tbhsripriya, I couldn't see the API changes in the design16:57
sripriyatbh: okay16:57
sripriyatbh: let us continue to evaluate further on zun project and see if we can consume it in tacker16:58
tbhsripriya, sure16:58
sripriya#topic open discussions16:58
*** openstack changes topic to "open discussions (Meeting topic: tacker)"16:58
*** liamji has quit IRC16:58
sripriyafolks, please continue to review and contribute on the minor RFEs as we chug along for these major features in ocata cycle16:59
sripriyait is a wrap for today16:59
*** oshidoshi1 has quit IRC16:59
sripriyathanks for joining the meeting16:59
sripriya#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Tue Nov  8 16:59:30 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-08-16.00.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-11-08-16.00.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-11-08-16.00.log.html16:59
*** jaugustine has quit IRC17:01
*** Janki has quit IRC17:01
*** tung_doan has quit IRC17:02
*** maeker has quit IRC17:03
*** jgregor has joined #openstack-meeting17:03
*** xyang1 has quit IRC17:04
*** ijw has joined #openstack-meeting17:04
*** bobh has joined #openstack-meeting17:04
*** jgregor_ has joined #openstack-meeting17:04
*** ALUVial has joined #openstack-meeting17:06
*** gouthamr has joined #openstack-meeting17:06
*** xyang1 has joined #openstack-meeting17:07
*** n-harada has left #openstack-meeting17:07
*** jgregor has quit IRC17:08
*** chandrav has joined #openstack-meeting17:09
*** bobh has quit IRC17:09
*** ijw has quit IRC17:13
*** ijw has joined #openstack-meeting17:13
*** lpetrut has quit IRC17:13
*** Naeil has quit IRC17:14
*** frasantoro has quit IRC17:15
*** srwilkers has joined #openstack-meeting17:15
*** mickeys has joined #openstack-meeting17:16
*** mickeys has quit IRC17:16
*** mickeys has joined #openstack-meeting17:17
*** matrohon has quit IRC17:17
*** mickeys has quit IRC17:18
*** acoles_ is now known as acoles17:19
*** s3wong has quit IRC17:19
*** mickeys has joined #openstack-meeting17:19
*** iyamahat has joined #openstack-meeting17:20
*** ijw has quit IRC17:20
*** efried has quit IRC17:20
*** andreas_s has quit IRC17:20
*** ijw has joined #openstack-meeting17:20
*** singhj has joined #openstack-meeting17:21
*** mickeys has quit IRC17:22
*** mickeys has joined #openstack-meeting17:22
*** Guest76339 has quit IRC17:23
*** SridharP1 has left #openstack-meeting17:23
*** SimonC_ has joined #openstack-meeting17:23
*** haleyb_ has joined #openstack-meeting17:25
*** caboucha has quit IRC17:26
*** rcernin has quit IRC17:29
*** edtubill has quit IRC17:30
*** sudipto has quit IRC17:30
*** sudipto_ has quit IRC17:30
*** haleyb_ has quit IRC17:30
*** edtubill has joined #openstack-meeting17:31
*** rfolco has quit IRC17:32
*** bogdando has joined #openstack-meeting17:33
*** caboucha has joined #openstack-meeting17:34
*** Daisy has joined #openstack-meeting17:35
*** ijw has quit IRC17:35
*** mageshgv has quit IRC17:35
*** Apoorva has joined #openstack-meeting17:36
*** Apoorva has quit IRC17:36
*** SimonC_ has quit IRC17:37
*** Daisy has quit IRC17:39
*** singhj has quit IRC17:39
*** fzdarsky is now known as fzdarsky|afk17:40
*** jprovazn has joined #openstack-meeting17:40
*** jmckind has quit IRC17:43
*** trown is now known as trown|lunchnvote17:43
*** Apoorva has joined #openstack-meeting17:43
*** dmorita has joined #openstack-meeting17:44
*** rajinir has joined #openstack-meeting17:45
*** david-lyle has joined #openstack-meeting17:46
*** brucetan has quit IRC17:46
*** hashar has quit IRC17:48
*** lpetrut has joined #openstack-meeting17:48
*** KanagarajM has quit IRC17:52
*** baoli has joined #openstack-meeting17:54
*** gagehugo has joined #openstack-meeting17:55
*** singhj has joined #openstack-meeting17:55
*** slayer has quit IRC17:55
*** bobh has joined #openstack-meeting17:55
*** nk2527 has joined #openstack-meeting17:56
*** jmckind has joined #openstack-meeting17:56
stevemaro/17:57
*** rfolco has joined #openstack-meeting17:57
stevemarping ajayaa, amakarov, ayoung, breton, browne, crinkle, claudiub, davechen, david8hu, dolphm, dstanek, edmondsw, gagehugo, gyee, henrynash, hogepodge, htruta, jamielennox, jaugustine, jgrassler, joesavak, jorge_munoz, knikolla, lbragstad, MaxPC, morgan, nishaYadav, nkinder, notmorgan, raildo, ravelar, rodrigods, rderose, roxanaghe, samleon, samueldmq, shaleh, stevemar, tsymanczyk, topol, vivekd, wanghong, xek, Stefa17:58
stevemarnPaetowJisc17:58
lbragstadstevemar o/17:58
gagehugoo/17:58
lamto/17:58
rderoseo/17:58
ayoungAyuh17:58
lbragstadstevemar looks like we need to prune our list :(17:58
stevemar#startmeeting keystone17:58
openstackMeeting started Tue Nov  8 17:58:24 2016 UTC and is due to finish in 60 minutes.  The chair is stevemar. Information about MeetBot at http://wiki.debian.org/MeetBot.17:58
rodrigodshello17:58
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:58
*** openstack changes topic to " (Meeting topic: keystone)"17:58
stevemarlbragstad: yeah17:58
openstackThe meeting name has been set to 'keystone'17:58
knikollao/17:58
*** ijw has joined #openstack-meeting17:58
*** davidsha has joined #openstack-meeting17:58
*** jgrassler has joined #openstack-meeting17:58
edtubillo/17:59
*** davidsha has quit IRC17:59
bretonto early!17:59
lbragstadstevemar we did that through a roll call over the course of a couple meetings the last time we pruned the list didn't we?17:59
stevemarlbragstad: i'll trim the list soon17:59
bretonit's :5917:59
*** spilla has joined #openstack-meeting17:59
stevemarbreton: :O :O17:59
*** singhj has quit IRC17:59
stevemarbreton: i wanted to give a few extra minutes to the people who will inevitably be caught by daylight savings time change17:59
bretonok, we're good to go, it's :00 now18:00
*** browne has joined #openstack-meeting18:00
bknudsonhi18:00
crinkleo/18:00
browneo/18:00
gagehugodst is rough18:00
srwilkerso/18:00
stevemarlbragstad: i'll look at the logs, anyone who hasn't said anything in the last 4 meetings will be cut18:00
*** henrynash has joined #openstack-meeting18:00
*** henrynash has left #openstack-meeting18:00
jgrasslerHello18:00
*** henrynash_ has joined #openstack-meeting18:01
*** sukhdev has quit IRC18:01
stevemaralright, let's get the show on the road18:01
samueldmqhi all18:01
stevemar#topic announcements18:01
*** openstack changes topic to "announcements (Meeting topic: keystone)"18:01
henrynash_(hi)18:01
stevemarNew keystone/horizon meeting18:01
dstaneko/18:01
*** ralonsoh_ has quit IRC18:01
samueldmqstevemar: weekly meeting ?18:02
stevemartheres a new meeting that'll take place (it's on tuesdays just after this one or an hour after)18:02
samueldmqnice18:02
stevemarsamueldmq: today is the kick starter18:02
stevemarwe'll see how it goes18:02
* samueldmq nods18:02
knikollagreat!18:02
*** SimonC_ has joined #openstack-meeting18:02
stevemarbut basically we want to form a squad to take down these long standing keystone/horizon integration issues18:02
stevemarif you're interested, let me know18:03
lbragstadstevemar is that one proposed to the openstack meeting tracker?18:03
*** unicell1 has quit IRC18:03
stevemarlbragstad: probably18:03
lbragstadso that people can grab the .ics file?18:03
stevemarlbragstad: link?18:03
lbragstadstevemar looking18:03
*** uxdanielle has joined #openstack-meeting18:03
stevemarwhat will be discussed is here: https://etherpad.openstack.org/p/ocata-keystone-horizon18:03
ayoungnice18:03
rodrigodsnice effort18:03
*** maeker has joined #openstack-meeting18:04
stevemarit'll be nice to either a) get patches up for the issues, or b) create an undertstanding between the teams on things that can't be fixed18:04
stevemarthe whole thing is in the spirit of more cross team communication18:04
ayoungthat is a good time for the meeting18:04
dstanekI think that's a real good idea. Is the first one right after this?18:05
edtubillnice, so there's a keystone/horizon meeting today at 19:00 UTC?18:05
david-lylestevemar, just noticing that's at the same time as the TC meeting, thinking may need to move the meeting time18:05
stevemardavid-lyle: i can live with it, meh18:05
stevemardavid-lyle: but we can bring that up at the kick off18:06
david-lylestevemar, fair enough18:06
stevemardstanek: sounds like the first one is in an hour after keystone ends18:06
bretonwhere will it be?18:06
stevemarkeep an eye on the #openstack-meeting-cp channel18:06
stevemarbreton: ^18:06
bretonok18:06
lbragstadwe should propose it here - https://github.com/openstack-infra/irc-meetings18:06
stevemarif you're interested, add your name to the keystone meeting etherpad, i'll make sure you get pinged18:07
stevemarso far it's just rderose :)18:07
rderoseI like to be firs6t18:08
rderose*first18:08
samueldmqstevemar: nice. that will also help us in UX aspects18:08
stevemarsamueldmq: yep18:08
*** bobh has quit IRC18:08
*** rvasilets___ has quit IRC18:08
ayoungok, hold Horizon issues until that meeting.18:08
stevemarsecond announcement is #What we agreed to do for Ocata-ish18:08
stevemari tried to recap all the items from the various work sessions18:09
stevemar#link https://docs.google.com/document/d/1dCJyP2bfXIWoQK_wWALU83EF3G-2fJSMaFgNGCJsIhs/edit?usp=sharing18:09
*** BobH has joined #openstack-meeting18:09
stevemarplease comment on it, i'm trying to figure out a way to best represent and track the items18:09
*** anilvenkata has quit IRC18:09
stevemari can see folks are already commenting on it :)18:10
stevemari'm done announcements18:10
stevemarwe can switch gears to spec reviews18:10
stevemaroh i guess on more announcement18:11
stevemari added the keystone specific dates to https://releases.openstack.org/ocata/schedule.html18:11
stevemarthe first one is "Keystone Spec Proposal Deadline" -- next week18:11
stevemarthe dates were decided at the summit18:11
stevemarso if you want to propose a spec, get it up soon!18:12
jgrasslerRegarding the Google doc: Cannot edit, vimperator conflicting with Google docs... :-/18:12
bretonjgrassler: press insert18:12
bretonjgrassler: or shift-escape18:12
*** mickeys has quit IRC18:13
stevemarjgrassler: breton you guys are too leet for me, i just use chrome18:13
jgrasslerbreton: Ah, the latter did the trick. Thanks :-)18:13
dstanekjgrassler: turn it off for that site18:13
gagehugothat looks interesting18:13
ayounganyone have anything to propose that is not on the list yet?18:13
jgrasslerbreton: I'll have to try that for the Horizon console, too, one of these days18:13
stevemardstanek: did you want to propose the pysaml middleware for ocata?18:13
knikollai will cough up a spec that details the overall plans for the devstack plugin and how it ties with integration/functional tests18:14
*** slayer has joined #openstack-meeting18:14
stevemarknikolla: cool18:14
dstanekstevemar: unless there is a tangible reason not to finish, I'm going to finish anyway. better that it's tracked18:15
stevemardstanek: eh? i'm asking for a spec for it. do you already have a patch proposed?18:16
stevemardstanek: did you name it something funny like "nteresting idea" or "do not review me"18:16
* stevemar pokes dstanek18:17
dstanekstevemar: mostly written but not submitted. I wanted to hear if it was talked about at summit and what the response was...18:17
lbragstadstevemar i found an open time slot and a room for the cross project horizon/keystone meeting https://review.openstack.org/#/c/395106/18:18
stevemardstanek: oh, it was talked about, and the ops in the room think it'll be nice to not have to restart apache18:18
dstanekstevemar: then I shall button up my draft and submit18:19
stevemar\o/18:19
stevemarlbragstad: thanks!18:19
stevemaralright18:20
stevemar#topic spec discussion18:20
*** openstack changes topic to "spec discussion (Meeting topic: keystone)"18:20
stevemarthis should take up the bulk of the meeting18:20
*** noama_ has joined #openstack-meeting18:20
stevemarPCI-DSS Reason in Notifications18:20
stevemarhttps://review.openstack.org/#/c/381302/18:20
stevemar#link https://review.openstack.org/#/c/381302/18:20
gagehugoyes18:20
stevemarit's got 2x +2s18:21
stevemaranyone against it?18:21
*** toscalix has quit IRC18:21
stevemarhas anyone not been given enough time to review it...?18:21
ayoungpush it on ahead18:21
rodrigodslooks good to me18:22
*** lpetrut has quit IRC18:22
rodrigodsand makes total sense18:22
ayoungI'll +2...one sec18:22
bknudsondo we have versioning of notifications?18:22
stevemaryeah, the notification ones are rarely contentious18:22
stevemarbknudson: no18:22
*** eharney has joined #openstack-meeting18:22
stevemardo we have 2 people that have the bandwidth to review it?18:23
stevemari can probably do it, but need one other person18:23
ayoungwhich one?18:23
ayoungjust +2A https://review.openstack.org/#/c/381302/18:23
knikollaayoung +2/+A-ed18:23
ayoungNext18:24
stevemarayoung: i'm assuming you will help me review it then :) thanks for volunteering :)18:24
stevemarnext18:24
stevemarPCI-DSS Expired Password Users18:24
stevemar#link https://review.openstack.org/#/c/38383218:25
stevemarthis one is a bit weird18:25
gagehugoyeah18:25
*** comay has quit IRC18:25
*** comay has joined #openstack-meeting18:25
stevemari keep mixing the terms enabled/disabled and expired18:25
*** jgregor_ has quit IRC18:25
gagehugoyeah it is confusing18:25
stevemarbut expired users can still be enabled and should be allowed to reset their password18:25
bknudsonuser has a new attribute?18:26
*** jgregor has joined #openstack-meeting18:26
gagehugopassword_expires_at18:26
stevemarwhat this spec does it allow an admin to get a list of users who have expired passwords18:26
bknudsonalthough unlikely, somebody could be using that already18:26
stevemarthe other funny funny about this is the query string18:27
gagehugothe ewwwwww comment?18:28
stevemar"password_expires_at=gt:2016-10-14T15:30:22Z"18:28
stevemar:)18:28
stevemargagehugo: its better now!18:28
gagehugoyes, much better18:28
bknudsonit's not clear if every user now has a new attribute.18:28
rderoseyeah, that would be weird18:28
rderosemost likely on greater than, less than18:28
gagehugobknudson: that spec doesnt add a new attribute18:29
gagehugoif that's what you mean18:29
rderosebknudson: every user now already has the password_expires_at attribute18:29
bknudsonit says that when you list users you get back a new attribute18:29
bknudsonok18:29
bknudsonI thought we already supported querying by attribute values18:29
*** asselin has joined #openstack-meeting18:29
rderosebknudson: me too18:30
*** mickeys has joined #openstack-meeting18:30
rderosebknudson: I think it is only partially implemented18:30
stevemarbknudson: it'll be a little different since it's a timestamp18:30
*** cleong has joined #openstack-meeting18:30
*** bobh_ has joined #openstack-meeting18:30
*** noama_ has quit IRC18:31
lamtI don't think it allows for inequality match18:31
*** jgregor has quit IRC18:31
*** lpetrut has joined #openstack-meeting18:31
*** chandrav has quit IRC18:31
knikollai see more value to this being a relative timestamp. like 'expires_in=1d'18:31
dstanekno, the gt,inequality,etc needs to be done18:31
*** acoles is now known as acoles_18:31
rderosedstanek: ++18:31
ayoungWe don't need a generla puproe comparator language18:32
ayoungmake it part of the URL:   all_after  etc18:32
bknudsonI thought we already had a general purpose comparator language18:32
dstanekapi-wg defined one18:32
stevemarsounds like no one is really against it. do we have people who are willing to review the code ?18:32
*** myoung is now known as myoung|afk18:32
*** krtaylor has quit IRC18:32
ayoungpassword_expires_after18:32
knikollaayoung: ++18:33
stevemari think the use case is "i want to list all users that are expired as of now"18:33
dstanekI will review18:33
*** unicell has joined #openstack-meeting18:33
stevemardstanek: thanks, anyone else?18:33
knikollastevemar: for that case is it not enough a expired=True?18:34
bknudsonhttp://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/driver_hints.py#n8518:34
rderosestevemar: I've already reviewed it18:34
gagehugono because a user can be expired but their enabled field does not change18:34
stevemarrderose: i mean, someone who is willing to review the implementation :)18:34
* rodrigods can review18:34
stevemargood enough for me18:34
dstanekknikolla: nope. I need to notify users that expire in 7 days18:34
rderoseah18:34
*** ihrachys has quit IRC18:34
lbragstadbknudson you want to use hints to get that information?18:35
bknudsonlbragstad: isn't that what it's for?18:35
*** Swami has joined #openstack-meeting18:35
stevemarapproved it18:35
dstanekknikolla: just like your employer probably does for your corporate account18:35
stevemarthe implementation detail can change while we review the impl.18:35
gagehugoyeah we can fine tune it18:36
lbragstadbknudson yeah - we'd have to enrich the hints functionality though - it has bugs18:36
stevemargagehugo: do you mind if we review https://review.openstack.org/#/c/345113/ before the project/props one?18:36
bknudsonthat sounds like a useful thing to do anyways18:36
gagehugostevemar: yeah go for it18:36
stevemarNext spec is https://review.openstack.org/#/c/345113/18:36
*** rfolco has quit IRC18:36
stevemargood ol MFA18:36
dstanekit's a good idea18:37
stevemari like it18:37
stevemarand adriant already has the impl. up18:37
stevemarit just didn't make the cut off last cycle, but i think it's good to go18:37
*** jgregor has joined #openstack-meeting18:38
stevemarthere are limitations (won't be enforced in v2 only deployments), but i'm still OK with it18:38
stevemarthere will be some issues with the client side work too, but we'll need to work that out separately18:38
*** baoli has quit IRC18:39
dstanekstevemar: I thought client side was a non-issue18:39
lbragstadi thought i remember that, too18:39
lbragstadwasn't the client just going to concatenate the code and password together?18:39
stevemardstanek: the issue there was that the user would need to get a new token every time and keep retyping their passcode18:40
dstanekyou just combine the code and password18:40
stevemarsince passcodes are only good for a few seconds18:40
knikollabut code expires, and user will have to resource the rc file18:40
dstanekAh, I see18:40
stevemarwe need to do a better job of caching tokens and getting new ones on the client side18:40
bknudsonuser could get an oauth token or something18:40
lbragstadah - so this is a different usability issue18:40
dstaneklooks like we need client side token caching18:40
knikollayeah18:41
bknudsonyou can cache the token but it's going to expire18:41
stevemardstanek: which has been an osc issue for a while18:41
lbragstad++ that would be good overall18:41
stevemargiven that limitation, i think we're still OK for approving it on the server side18:41
dstanekstevemar: I wanna discuss that offline with you... If I can remember18:41
stevemardstanek: sure, pull in jamielennox too18:42
*** jgregor has quit IRC18:42
dstaneksure18:42
stevemardstanek: lbragstad bknudson i'll let you guys approve it if you agree to review the impl.18:42
*** rfolco has joined #openstack-meeting18:43
dstanekalready been!18:43
ayoungstevemar, better job caching tokens where?18:43
*** rasca has quit IRC18:43
knikollaclient side18:43
stevemarayoung: on the client side18:43
knikollaopenstackclient doesn't cache tokens18:43
ayoungI'm gonna mess that up18:43
dstanekayoung: ?18:44
ayoungif we merge role validation into the token validation, caching is not going to be worth much18:44
ayoungsame token, different call, will have to be reauthenticated18:44
stevemarthat definitely messes things up18:44
dstanekclient will still be able to use the same token more than once right?18:44
lbragstaddstanek maybe, maybe not18:44
lbragstaddepends on the call the user is making18:45
bknudsonit was just getting the token that required the code18:45
*** chris_morrell has joined #openstack-meeting18:45
lbragstada token might be valid for one call and invalid for another depending on the operation18:45
ayoungheh18:45
ayoungglad I could derail this18:45
stevemaryeah lets put the train back on the tracks18:45
dstanekso we wouldn't support OS_TOKEN anymore?18:46
stevemarcomment on the spec if need be18:46
ayoungso..yeah, its going to wreak total havoc with caching18:46
*** SimonC_ has quit IRC18:46
stevemarayoung: the fallout from your spec is independent of this new one18:46
ayoungheh18:46
stevemarit'll break caching everywhere18:46
stevemarso reviewers: do not treat the two as related...18:46
lbragstadwe probably need to set aside time to talk about that one again18:47
dstanekayoung: which spec is that?18:47
bknudsonayoung: I think it'll depend on if the server returns a 401 or 403 error18:47
ayoungbut if you are talking about having the client reuse tokens, that is different, and yes, we should do that18:47
*** pvaneck has joined #openstack-meeting18:47
bknudsonnot having role should return 40318:47
*** david-lyle_ has joined #openstack-meeting18:47
knikollahttps://review.openstack.org/#/c/391624/18:47
bknudsoninvalid token should return 40118:47
lbragstad#link https://review.openstack.org/#/c/391624/18:47
stevemardstanek: https://review.openstack.org/#/c/391624/18:47
dstanek:) thx all18:47
stevemarayoung: you added everyone to that review18:48
*** sridharg has quit IRC18:48
ayoungstever, well, not EVERYONE, but yeah18:48
dstanekif OS_TOKEN stops work than my personal automation will stop working :-(18:48
*** tonytan4ever has quit IRC18:48
stevemardstanek: a lot of automation would stop working18:48
bknudsondstanek loves the admin token18:49
stevemarbknudson: different than admin token18:49
dstanekyeah, but i'm mostly worried about mine18:49
ayoungOS_TOKEN should and will die18:49
ayoungdie die die die18:49
stevemar10 minutes left, lets jump to the last spec18:50
stevemarProjects and properties!18:50
ayoungMazes and Monsters!18:50
stevemar#link https://review.openstack.org/#/c/388886/18:50
stevemari posted this to the mailing list18:50
stevemarMailing List Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-November/106806.html18:50
ayoungYeah, this is a bad idea18:50
gagehugoThere was good discussion on the mailing list18:50
bknudsonthe response on the mailing list was that we hate quotas18:51
lbragstadi thought we got some good feedback from other developers18:51
ayoungYouthought HMT was hard to solve...18:51
*** tonytan4ever has joined #openstack-meeting18:51
ayounganyone care to summarizethe feedback?18:51
stevemarayoung: ops are for it18:52
stevemarnova folks are saying to watch out for a few things18:52
stevemarmake sure you use a strict set of valid keys18:52
bknudsonthere's an extra metadata call for projects?18:52
lbragstad#link http://lists.openstack.org/pipermail/openstack-dev/2016-November/106822.html18:52
stevemarjaypipes said to use tags18:52
dstaneki'm definitely not a fan of this yet18:53
*** adisky has quit IRC18:53
bknudsonhorizon already has panels for editing metadata18:53
*** david-lyle_ has quit IRC18:53
stevemarbknudson: keystone metadata?18:53
*** bobmel has quit IRC18:53
stevemarwell.. extras?18:53
bknudsonno, volume and instance18:53
ayounghere is one way to think of it18:53
gagehugos/metadata/properties18:53
stevemarso should be copy/paste for keystone projects :D18:54
ayoungfrom a Keystone perspective, no service is special18:54
bknudsonI don't know what it has for projects18:54
ayoungNova is no more special than Neutron18:54
*** tbh has quit IRC18:54
ayoungand that goes out into the things floating around the big tent18:54
ayoungand off into the sunset18:54
stevemardstanek: why are you against it?18:54
ayoungwe are not making a clearing house of project specific information, because if the project can't figure out how to deal with the type of info, ofbbing it off on Keystone will not solve the problem18:55
ayoungit will exacerbate it18:55
ayoungif we need a sound approach to quotas, solve quotas18:55
*** bobmel has joined #openstack-meeting18:55
ayoungdon't solve it in a project specific manner, but make sure the solution works for cinder and neutron18:55
bretonlets not talk quota yet18:55
dstanekstevemar: well, i think it's an interesting usecase, but in implementing it we open a can of worms18:55
*** ebalduf has quit IRC18:55
gagehugoproject properties is not for quotas18:55
stevemarbreton: ++ this isn't for quotas18:56
ayoungbreton, this is all about quotas18:56
*** chris_morrell has quit IRC18:56
ayoungit is the same damn thing18:56
bretonayoung: no it isn't, and it is different :)18:56
ayoungquota is a specific instnace of a type of data specific to nova, neutron18:56
dstanekfor instance, i commented on the spec that it was broken because it allowed people with the ability to create projects to edit the metadata18:56
lbragstadthis sounds like extras v218:56
stevemarayoung: read adriant's use case: http://lists.openstack.org/pipermail/openstack-dev/2016-November/106839.html18:56
ayoungand the billing info tags etc18:56
gagehugolbragstad: yes, more or less18:56
dstanekthat makes sense unless you real the usecase which is really wanting only the cloud admin to edit18:56
gagehugowhich is what we want18:57
dstanekso does this mean we are opening ourselves to have multple levels or metadata controlled by permissions?18:57
lbragstadso - i know everyone here pretty much hates the idea of extras and we've been trying to get rid of it for a while... if we move forward with properties we need to make sure we don't reimplement the things we hate about extras18:57
stevemarwe already have to support "extras", may as well make a decent API for it18:57
ayoungwe have not even solved basic RBAC.  We can't do what they want.18:57
*** jaugustine has joined #openstack-meeting18:57
dstaneklbragstad: it is formalizing extras in a way, but their usecase limits who should have the ability to modify the metadata18:57
dstanek(at least some of the metadata)18:58
ayoungstevemar, we make NO guarnatees about that data.  AAnd if people realized just how easy it was for that data to be something other than what they want it to be, they will freak18:58
dstanekstevemar: this isn't an api for metadata.18:58
*** Rockyg has joined #openstack-meeting18:58
*** jaugustine has left #openstack-meeting18:58
*** jaugustine has joined #openstack-meeting18:58
stevemardstanek: eh?18:59
dstanekthe original spec made it seem that way, but i was not aligned with the usecase18:59
*** chris_morrell has joined #openstack-meeting18:59
lamtmetadata might be an overloaded term - it is more storing properties (or tags) and associate it with keystone entities18:59
lamtright now the user table's stores emails in the extra column18:59
stevemari dunno, i can't believe we're arguing over what seems like a basic use case18:59
stevemartimes up19:00
stevemar#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Nov  8 19:00:13 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-08-17.58.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-11-08-17.58.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-11-08-17.58.log.html19:00
fungiinfra team, assemble!19:00
bknudsondon't forget to vote19:00
clarkbhello19:00
crinkleo/19:00
fungithis week's topics proposed by dhellmann, fungi19:00
*** browne has left #openstack-meeting19:00
*** skelso has joined #openstack-meeting19:00
*** spilla has left #openstack-meeting19:00
*** chris_morrell has quit IRC19:00
dhellmanno/19:01
*** Sukhdev has joined #openstack-meeting19:01
Zarao/19:01
ianwo/19:01
*** tojuvone has joined #openstack-meeting19:01
jheskethMorning19:02
fungiinfra-root: courtesy ping, i know timezones have changed for at least a few of you19:02
bkeroo/19:02
mordredo/19:02
pabelangerOooh19:02
pabelangerthanks19:02
*** maeker has quit IRC19:02
*** lpetrut has quit IRC19:02
fungi#startmeeting infra19:03
openstackMeeting started Tue Nov  8 19:03:01 2016 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
*** openstack changes topic to " (Meeting topic: infra)"19:03
openstackThe meeting name has been set to 'infra'19:03
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:03
fungi#topic Announcements19:03
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:03
fungi#info Our "Ocata Cycle" [2048R/0x8B1B03FD54E2AC07] signing key has been generated; infra-root admins are requested to follow our attestation process as soon as possible.19:03
*** maeker has joined #openstack-meeting19:03
fungi#link https://sks-keyservers.net/pks/lookup?op=vindex&search=0xd47bab1b7dc2e262a4f6171e8b1b03fd54e2ac07&fingerprint=on OpenStack Infra (Ocata Cycle) <infra-root@openstack.org>19:03
fungi#link http://docs.openstack.org/infra/system-config/signing.html#attestation Attestation process19:03
fungias always, feel free to hit me up with announcements you want included in future meetings19:03
SotKo/19:03
*** sambetts is now known as sambetts|afk19:03
fungi#topic Actions from last meeting19:04
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:04
fungi#link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-11-01-19.03.html19:04
fungifungi send summit session summary to infra ml19:04
fungiyour terrible ptl is backlogged, but it is at least in the process of being drafted19:04
fungi#action fungi send summit session summary to infra ml19:04
fungipabelanger announce upcoming wheel-less pep8 job transition to openstack-dev ml19:04
fungi#link http://lists.openstack.org/pipermail/openstack-dev/2016-November/106668.html important changes to pep8 python jobs19:04
fungithanks pabelanger! you want to do the follow-up one next week as well?19:04
*** s3wong has joined #openstack-meeting19:04
pabelangerfungi: Yup, I was going to send that out later today19:04
fungi#action pabelanger send followup announcement for wheel-less pep8 job transition19:05
* fungi predicted that response, being all prescient and ptl-like19:05
fungifungi generate and sign ocata cycle signing key19:05
fungithat's done (see above link in this week's announcements)19:05
fungi#topic Specs approval19:05
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:05
*** Shrews has joined #openstack-meeting19:05
fungi#info APPROVED "Neutral governance website" spec19:05
fungi#link http://specs.openstack.org/openstack-infra/infra-specs/specs/neutral-governance-website.html "Neutral governance website" spec19:05
*** bobh_ has quit IRC19:06
fungittx: ^ in case you missed that it merged19:06
*** electrofelix has quit IRC19:06
fungi#topic Specs approval: PROPOSED "Automate Creating Branches" spec (dhellmann)19:06
*** openstack changes topic to "Specs approval: PROPOSED "Automate Creating Branches" spec (dhellmann) (Meeting topic: infra)"19:06
fungi#link https://review.openstack.org/369643 "Automate Creating Branches" spec review19:06
dhellmannhi!19:06
fungilooks like you and jhesketh have given it a council thumbs-up already19:06
zaroo/19:06
dhellmannso far the comments on this look positive, so I would like to start working on implementation19:06
dhellmannbefore I do, I wanted to get the official sign-off19:07
fungioh, that was tonyb and jhesketh who have it a council thumbs-up actually19:07
fungidhellmann: yep, sounds good!19:07
fungi#info The "Automate Creating Branches" spec is open for Infra Council vote until 19:00 UTC Thursday, November 10.19:07
dhellmanncool, thanks19:07
*** gagehugo has left #openstack-meeting19:07
jeblairdhellmann: are you thinking about automating deletion?19:08
dhellmannjeblair : not in this go-round, but eventually tonyb wants to automate the eol process19:08
*** bobh_ has joined #openstack-meeting19:08
fungiyeah, we talked about it on summit friday, in the release management room i think19:08
jeblaircool.  i think the baby steps approach is good.  just wondering if it was a twinkle in your eye.19:08
jeblairglad to hear it is :)19:08
fungiseemed there was general agreement on the idea19:08
fungiit would be a big help both to stable maint and infra19:09
dhellmannI'm not sure about "delete" but definitely "eol"19:09
*** skelso has quit IRC19:09
dhellmannsomething like a feature branch might have a different process for "delete", I guess19:09
fungiright, generally we "delete" branches by eol'ing them, so that sounds like enough of what we want19:09
dhellmannanyway, yes, baby steps :-)19:09
jeblair++19:09
dhellmannok, that would cover both cases then19:09
fungibut as you say, that's a topic for another day! ;)19:10
dhellmannand tonyb volunteered, so he owns that ;-)19:10
fungiheh, perfect19:10
fungianything else you need to squeeze in about this spec before we move on to other meeting topics?19:10
dhellmannthat's it from me. I'll look for questions on the review.19:10
fungithanks!19:10
fungi#topic Priority Efforts19:11
dhellmannthank you!19:11
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:11
funginothing is called out on the agenda this week, but i did approve rcarrillocruz's change to move infra-cloud to implemented19:11
fungiand have removed it from the priority efforts subtopics on our weekly meeting agenda as well19:11
clarkbfungi: did the zanata change to make that implemented get pushed/merged too?19:11
*** skelso has joined #openstack-meeting19:11
fungiclarkb: ooh, i think? lemme check real fast19:12
*** sekelso has joined #openstack-meeting19:12
*** baoli has joined #openstack-meeting19:12
fungioh, i think it already was in implemented19:12
fungiat any rate, it's there now19:13
clarkbah ok ianychoi mentioned that we needed to update it but I didn't check if it was already done19:13
fungiif memory served, the upshot was that he was confused by the fact that it was still in the index, but turned out it was in the implemented section of the index19:13
clarkbgotcha19:14
*** diga has quit IRC19:14
fungialso asselin has one up to mark the openstackci spec as implemented19:14
fungi#link https://review.openstack.org/393492 Mark openstackci spec as complete19:14
fungilooks like that's been up for almost a week19:14
pabelanger+119:15
rcarrillocruz++19:15
fungiif anybody objects that it's complete, say so on the review, otherwise i'll merge it on thursday as well19:15
*** ayoung has quit IRC19:16
asselin++ thanks!19:16
fungi#topic Ensuring projects adhere to the Consistent Testing Interface (fungi)19:16
*** openstack changes topic to "Ensuring projects adhere to the Consistent Testing Interface (fungi) (Meeting topic: infra)"19:16
fungi#link https://review.openstack.org/394620 Make sure opportunistic DB use in unit tests works19:16
fungii was collaborating with notmyname on a change to get an xfs tempdir available in swift unit test jobs19:17
*** ayoung has joined #openstack-meeting19:17
*** egallen has quit IRC19:17
fungithere had been pushback against them only running their unit tests like that, concerned that it might violate the consistent testing interface mandated by the tc19:17
fungiwhen looking for examples to follow there, it dawned on me that this is already exactly the case for projects whose unit tests are only run with special mysql and postgres databases prevonfigured19:18
jeblairfungi: oh, i thought the swift thing was for a new job19:19
*** numans has joined #openstack-meeting19:19
jeblairit's meant to replace the existing py27 job?19:19
fungiso i pushed this up as a sort of straw-man for whether we think this is equivalent, and whether it's something we think needs to be done as well, or whether i should put forward an amendment to the cti that would make deviations like these acceptable19:19
*** jgregor has joined #openstack-meeting19:19
fungiin swift's case they're adding an xfs variant of their unit test job, but they'd rather just run it with xfs available because the only difference is that without an xfs filesystem to use a subset of their unit tests are disabled19:20
jeblairgotcha19:20
fungithey only made it a separate, additional job because concerns were voiced that doing otherwise may violate the cti19:21
fungibut if it does, then probably so do all these unit tests that only get run with special db configs present19:21
ianwsorry if this sounds silly, but why would we run with preconfigured databases at all then?  shouldn't every test know how to set itself up?19:21
clarkbfungi: I had previously used the database example for why I thought swifts thing was fine...19:21
fungifor example, we don't test that nova's unit test jobs work without mysql and postgres databases set up for them in advance19:21
jeblairwell, the *intent* of the pti was so that we are able to maintain the roughly 5000 standardized jobs19:21
jeblairit's not to be arbitrary -- it's just to set a standard19:22
jeblairso i think if we need to adjust it to accomodate a more flexible idea of preconfiguration, that's fine.  but it probably should entail some thinking about how that would look in the project-config repo.  because if the outcome is that every project has their own py27 variant and they don't share builders, etc, then we've lost our ability to do things like "change run-tox.sh" or "upgrade os distros"19:23
*** maeker has quit IRC19:23
*** jgregor has quit IRC19:24
jeblair(perhaps modularity and reuse of jjb builder macros -- in the way that notmyname was constructing that job -- would solve those problems)19:24
fungiyeah, in the swift xfs case, it would just have been a separate job template basically identical to the python27 one except adding a builder immediately before revoke-sudo19:24
fungithat does teh xfs setup step19:24
jeblairthat seems like a sensible way to approach it.  it stays out of the way of the parts of the interface we need to make assumptions about.19:25
fungiso i guess the first question, does anybody feel like custom job templates that add some database permissions or mount a special filesystem before running, say, `tox -e py27` is out of line with the cti?19:25
fungi#link http://governance.openstack.org/reference/cti/python_cti.html#specific-commands Consistent Testing Interface: Python (Specific commands)19:26
mordredI tihnk those are fine in the way described above - where the actual invocation of the CTI portion is unchanged19:26
fungiif there's no general disagreement on that point, then we can probably forego amending the cti in governance unless it becomes more contentious19:27
jeblairi don't disagree.  i think clarifying it would be fine though.19:27
*** ljxiash has quit IRC19:27
*** haleyb_ has joined #openstack-meeting19:27
clarkbfungi: I don't think they are as long as the test suite can still run on my laptop without root19:28
clarkbso swift should handle the no xfs case and nova should handle the no db case19:28
jeblairya19:28
clarkbI know nova does this, I dunno if swift does19:28
fungiif that's the case, do we need to _test_ that upstream?19:28
clarkbwe haven't had to test it upstream so far because enough people seem to run the tests locally that this is covered19:28
*** skelso has left #openstack-meeting19:28
fungithat's what the current swift job addition and my db jobs change linked above would do19:28
jeblairclarkb: well, i disagree that projects need to test the null case.19:28
jeblairclarkb: we can talk about that if you want, however, it's not at issue here, so we could skip it.  :)19:29
clarkbok :)19:29
jeblairi don't think we need to run the tests twice, without the db.19:30
clarkbya it hasn't been an issue so far in the few years we have only tested with the db19:30
mordred++19:31
fungi#agreed Infra consensus is that jobs adding custom database configuration or special filesystems prior to running CTI-mandated test commands do not necessarily violate the CTI as worded; clarification in the CTI on this point and that projects should try to make some of their tests viable even without such setup (even if that case is not tested upstream) would be a welcome addition.19:31
fungii struggled at finding a less-wordy distillation of the position there19:31
fungianyone have suggestions?19:31
jeblairwell, i still disagree with the last part.19:32
fungi#undo19:32
openstackRemoving item from minutes: <ircmeeting.items.Agreed object at 0x7fac55465ed0>19:32
*** maeker has joined #openstack-meeting19:32
*** haleyb_ has quit IRC19:32
jeblairif swift, hypothetically, chose *only* to support xfs, i don't think it would be sensible for us to say that its unit tests must work without it19:32
fungiokay, so we should test that they're runnable even without te db setup or filesystem mounted?19:32
fungiaha, so other way around19:32
jeblairfungi: right -- other way around :)19:33
fungiand yes, it sounds like it's pretty close to that in the swift case19:33
persiaTo help express complex cases in policy, the use of a Statement; Rationale; Implications structure (as in https://www.gov.uk/government/publications/open-standards-principles/open-standards-principles) can be useful.  Note that this doesn't help the wording above unless someone wants to redraft everything.19:33
fungibasically their advanced attribute support only works on xfs19:33
jeblairalso, i think it's insane that nova tests with sqlite (it has caused *no end* of problems over the years)19:33
clarkbjeblair: oh swift doesn't only support xfs19:33
clarkbwhich is why I think their tests should still work on ext4 for example19:33
clarkbor btrfs19:33
jeblairclarkb: agreed.  i was postulating a hypothetical19:34
clarkbgotcha19:34
jeblairto illustrate why i think it's okay for unit/function tests to, in some cases, require this kind of setup19:34
*** armax has joined #openstack-meeting19:34
fungi#agreed Infra consensus is that jobs adding custom database configuration or special filesystems prior to running CTI-mandated test commands do not necessarily violate the CTI as worded; clarification in the CTI on this point would be a welcome addition.19:34
fungibetter?19:34
*** trown|lunchnvote is now known as trown19:35
jeblairbasically, i think we need to not let the tail wag the dog here -- we should test what makes sense for the project and developers.  but we should push back on projects that go overboard in their tests and require crazy things (like root).19:35
jeblairfungi: agreed19:36
*** rrecio_ has joined #openstack-meeting19:36
clarkbjeblair: +119:36
fungiyeah, i think a fundamental element here may be that the prerequisite steps requiring root access be clearly defined somewhere by the project19:36
jeblair"this project is useless without a database" okay, install the db.  "this project can do cool stuff with a giant ceph cluster" maybe don't require that for the unit tests.  :)19:37
fungiso, for example, packages need installing with root access... a bindep.txt and readme paragraph satisfies that19:37
*** mickeys has quit IRC19:37
fungithat is a case we've heavily automated because it's a shared divergence across many/most projects19:38
jeblairfungi: ++19:38
*** vishwanathj has joined #openstack-meeting19:38
fungithings like database and filesystem setup are just slightly less common prerequisites root has to satisfy19:38
*** vishwanathj has quit IRC19:38
fungithanks, that gets me a good place to start from, i think19:39
fungi#action fungi propose clarification about project-specific test preconditions (databases, filesystems) for cti19:39
fungii'm tapped out on this topic, thanks for entertaining my existentialist whims here19:39
*** hashar has joined #openstack-meeting19:39
*** rrecio has quit IRC19:40
fungi#topic Open discussion19:40
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:40
fungianything else?19:40
fungiwe have 20 minutes left over for a change19:40
*** markstur has quit IRC19:40
jeblairi promise i haven't forgotten about the zuulv3 spec updates19:40
clarkbtoday is election day, does that make tomorrow an unofficial recovery holiday?19:40
fungihangover day?19:40
clarkbfungi: tahts the more direct way of putting it :)19:41
ianwpholio is up ... fungi did you look into removing the other hosts i mentioned?19:41
fungiianw: yep, those are cleaned up19:41
zaroi forgot to set topic for gerrit upgrade, a spec is in review.  #link https://review.openstack.org/#/c/388190/  should we go over it next week?19:41
clarkbzaro: lets19:41
fungii have not purchased a cert for pholio.o.o though19:41
ianwfungi: thanks19:41
fungi#action fungi purchase cert for pholio.openstack.org19:41
jeblairi have a bunch of notes on the 'secrets' one.  when i type that up, i'll ask folks to take another look.19:41
fungiianw: also i spotted that the vhost seems to think it's pholio01.o.o, have you adjusted that in puppet yet?19:42
fungiit may have a baked-in assumption that the vhost name is ==$::fqdn19:42
jeblairon the afs-docs thing, i hope that https://review.openstack.org/394658  will correct the problems we saw with some jobs publishing19:42
jeblairthat needs to be approved and we need a zuul-launcher restart19:42
ianwfungi: ahh, ok, i have not.  i think it idoes19:42
fungijeblair: the pycrypto vs pyca/cryptography thread on the -dev ml might also be relevant to that spec addition19:43
jeblairfungi: ah thanks, i'll take a look.19:43
clarkbI sent the first You need to use Xenial email19:43
pabelangerI've started taking a stab at fixing our abort loop issue with zuul, 395056. Looking for some initial feedback.19:43
clarkbintend to send one every monday until our switchover19:43
fungia lot of openstack is switching functions over to use the cryptography lib, though that would cause zuul sdist installs to need to link against openssl-dev headers19:44
clarkbfungi: already does19:44
fungioh, in that case we may want to strongly prefer pyca/cryptography19:44
*** csomerville has quit IRC19:44
clarkbI had to update the devstack gate reproduce.sh header to reflect that19:44
*** singhj has joined #openstack-meeting19:44
*** csomerville has joined #openstack-meeting19:44
fungithe implementation rcarrillocruz was looking into though (pkcs#1 with oaep) would still be effectively the same19:45
*** david-lyle has quit IRC19:45
*** jgregor has joined #openstack-meeting19:45
fungithere's methods to supply that in cryptography, and it also lacks pkcs#7 support just like pycrypto19:46
rcarrillocruzgood call, thanks19:46
fungidifference would be that it would be handled by libssl directly rather than custom forks/backports of rsa code in pycrypto19:46
*** claudiub has quit IRC19:46
mordredI like things when libssl handles them19:47
jeblairfungi: wow.  don't oversell it.  :)19:47
*** ijw has quit IRC19:47
fungiheh19:47
jeblairfungi: 'local, hand-made, artisnal backports'19:47
*** numans has quit IRC19:48
fungi#link http://lists.openstack.org/pipermail/openstack-dev/2016-November/106827.html pycrypto vs cryptography19:48
fungithat's teh start of the thread19:48
mordredjeblair: I think you just gave someone a business idea ...19:48
*** ijw has joined #openstack-meeting19:48
*** ijw has quit IRC19:48
jeblairmordred: was it you?19:49
*** ijw has joined #openstack-meeting19:49
bkeromordred: I believe some of our employers are already in that racket.19:49
mordredjeblair: oh golly no19:49
* bkero looks at his kernel.19:49
fungitouché19:49
mordredif I were starting this business, it would not include "hand-made" anywhere in its remit19:49
fungimy hands are too delicate for hand-rolled crypto19:50
*** ijw has quit IRC19:50
fungianyway, as is pointed out in that thread, a good reason to consider dropping pycrypto is that it's been effectively dead upstream for 2-3 years19:51
fungiwhich is not the sort of thing you want in a security-sensitive library19:51
jeblairyeah, so maybe i'll throw the words "python" "crytpography" and "library" into that spec update too.19:51
jeblairpossibly in that order.19:51
flaper87o/19:52
fungiseems like we've even run out of open discussion. i give you all 7 minutes of your week back19:53
flaper87quick one19:53
*** joehuang has joined #openstack-meeting19:53
flaper87https://review.openstack.org/#/c/391588/19:53
fungioh!19:53
flaper87I thought I'd give a quick update on the badges thing I brought up 3 weeks ago19:53
fungiplease do!19:53
flaper87I've implemented the badges generation as part of the governance repo CI jobs19:53
flaper87no need to host another service or doing other changes19:53
*** kenji-i has joined #openstack-meeting19:54
fungiyeah, i looked at one of the rendered svg images. neat stuff19:54
flaper87I just have one question19:54
jeblairnice!19:54
flaper87it'd be great if we could make the 404 response for the `/badges/` subdir a badge19:54
fungii was trying to figure out if there's a good way to overlay those on the git.o.o webui (maybe some javascript tricks) without getting in the way too much19:55
flaper87That is, if someone tries to load a badge for a non-official project, the response will be 404 and I'd like to return a "project: unofficial" badge along with that response19:55
clarkbflaper87: we should be able to configure the web server to do that19:55
flaper87would that be possible ?19:55
flaper87awesome19:55
mordredyah. good old apache19:55
fungiflaper87: a custom 404 page would probably be able to do that? or we could just to a pattern-based redirect19:55
*** gordc has joined #openstack-meeting19:55
fungier, just do a19:55
*** anilvenkata has joined #openstack-meeting19:55
flaper87we might want to just do this for the /badges/ subdir/path19:55
*** lpetrut has joined #openstack-meeting19:56
fungiright, i think either method should be able to be restricted by location19:56
mordredall 404s across all of infra should become the unofficial badge ;)19:56
flaper87I'll add the 404 badge generation to this sphinx plugin too19:56
flaper87mordred: :D19:56
fungiwill need to play around with it a little. if you have time to fiddle with apache configuration locally and work out the syntax, i'm happy to point you at where we would need to add it19:56
ianwflaper87: .htaccess might work?19:57
flaper87fungi: yes, point me at it19:57
flaper87ianw: it might, I just didn't know if we were using apache19:57
*** CarolBarrett has joined #openstack-meeting19:57
clarkbwe are apacheing19:57
fungi#link http://git.openstack.org/cgit/openstack-infra/system-config/tree/modules/openstack_project/templates/static-governance.vhost.erb erb template for governance.o.o site19:58
fungiflaper87: ^19:58
flaper87I'll optimize the badges layout next but that doesn't impact any of this work19:58
ianwwe are, so it might make sense to keep in the repo.  anyway, plenty of options19:58
flaper87fungi: awesome, thanks19:58
*** raildo has quit IRC19:58
flaper87I'll try with .htaccess first. if it doesn't work, I'll change apache's config19:58
fungiflaper87: thanks for using up our otherwise wasted last 7 minutes!19:59
jeblairif we want to use htaccess, we may need to allow setting the 404 page19:59
flaper87:D19:59
fungiwe're out of time--thanks everyone!19:59
flaper87I think htaccess would be better in this case because it isolates the work in one place19:59
* flaper87 stfu19:59
jeblairflaper87: thanks!19:59
fungi#endmeeting19:59
flaper87my pleasure19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Nov  8 19:59:59 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-11-08-19.03.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-11-08-19.03.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-11-08-19.03.log.html20:00
ttxo/20:00
* fungi opts to stick around and see what meeting comes next20:00
flaper87o/20:00
stevemaro/20:00
mordredo/20:00
mordredfungi: that's clearly a mistake20:00
ttxdhellmann, dims, dtroyer, johnthetubaguy: around ?20:00
dhellmanno/20:00
ttxsdague, EmilienM, thingee and mtreinish are excused20:00
* flaper87 is happy for being able to enjoy the TC meeting w/ daylight20:00
*** ebalduf has joined #openstack-meeting20:01
jroll\o20:01
dtroyero/20:01
dimso/20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue Nov  8 20:01:12 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
*** sekelso has quit IRC20: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
* edleafe lurks in the back20:01
*** cdent has joined #openstack-meeting20:01
* mordred hands edleafe some popcorn20:01
ttxHi everyone20:01
* Rockyg slinks into back of room20:01
*** sekelso has joined #openstack-meeting20:01
johnthetubaguyo/20:01
ttxOur agenda for today20:01
* flaper87 right-clicks on edleafe and selects "Bring to front" option20:01
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:01
mordredRockyg: you'll have to share edleafe's popcorn20:01
*** sekelso has quit IRC20:01
mordredflaper87: nice20:01
edleafeRockyg: help yourself!20:01
ttx(remember to use #info #idea and #link liberally to make for a more readable summary)20:01
*** uxdanielle has quit IRC20:01
ttx#topic Adjust TC and PTL election timeframes20:02
edleafeflaper87: heh20:02
*** openstack changes topic to "Adjust TC and PTL election timeframes (Meeting topic: tc)"20:02
* sigmavirus lurks with edleafe 20:02
ttx#link https://review.openstack.org/38595120:02
* edleafe thinks we'll need more popcorn20:02
ttxOK so the deadline is up for this one20:02
ttxWe got a lot of PTLs to chime in, which is great20:02
*** ijw has joined #openstack-meeting20:02
*** Shrews has left #openstack-meeting20:02
ttxAny last minute objection to getting this merged now ?20:02
ttxAt this point I'd rather keep the votes and do wording tweaks in a separate change.20:02
flaper87++20:02
johnthetubaguy+1 for merge now20:02
dtroyer++20:03
mordred++20:03
dimsttx ++20:03
stevemarmege it!20:03
stevemaror merge even20:03
RockygThanks, edleafe !20:03
sigmavirusstevemar: either one works really20:03
*** rfolco has quit IRC20:03
ttxdone20:03
edleafemerge now20:03
ttx#topic remove expired entries for extra-atcs20:03
*** openstack changes topic to "remove expired entries for extra-atcs (Meeting topic: tc)"20:03
*** skelso has joined #openstack-meeting20:03
ttx#link https://review.openstack.org/38817020:04
ttxThis one seems ripe as well. Objections ?20:04
*** claudiub has joined #openstack-meeting20:04
fungione concern20:04
fungithough i don't object20:04
*** Swami has quit IRC20:04
fungithis guts the ux team electorate20:04
ttxPeople can still re-add themselves20:05
fungiyep20:05
fungiwhich is why i don't object20:05
*** david-lyle has joined #openstack-meeting20:05
*** raildo has joined #openstack-meeting20:05
fungijust want to make sure people are aware that there are effectively no ux team contributors once this merges, until they ask to add some again20:05
dhellmannI did add the PTLs as reviewers20:05
ttxI suspect removing them will be a strong incentive20:06
ttxto refresh it in time for elections20:06
ttxfungi: or you could take an action to reach out more directly :)20:06
dhellmannshould I try to contact Piet directly?20:06
johnthetubaguy+1 fungi and ttx on the ux project20:06
*** skelso has left #openstack-meeting20:06
johnthetubaguyyeah, we should reach out20:06
ttxdhellmann: I don't think that should block the patch though20:06
ttxthose entries are expired20:07
flaper87I'd probably reach out, yeah20:07
flaper87++ ttx20:07
*** dbecker has quit IRC20:07
dhellmannttx: ack20:07
flaper87I mean, let's merge it and reach out anyway20:07
fungisame, they'd need to submit a change to governance to either readd or update expirations either way20:07
ttxso let's approve now + reach out20:07
johnthetubaguy+120:07
ttx#info we merge this one now but should reach out to UX directly so that they refresh their list before elections20:07
ttxok done20:08
fungii can write something to the -dev ml using their mailing list tag unless someone else was already planning to do so20:08
dhellmannI'll do it20:08
fungithanks dhellmann!20:08
dhellmann#action dhellmann contact the ux team about their electorate20:08
ttx#action dhellmann will reach out to UX for extra-atc refresh20:08
ttx#undo20:08
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x7fac554663d0>20:08
ttx#topic Add project Tricircle to OpenStack big-tent20:08
*** openstack changes topic to "Add project Tricircle to OpenStack big-tent (Meeting topic: tc)"20:08
ttx#link https://review.openstack.org/33879620:09
joehuanghi20:09
mordredlook it's a joehuang20:09
ttxjoehuang: hi!20:09
ttxQuick intro... this project team was proposed back in July20:09
ttxBack then it was rejected, in part because making it an official project created confusion as to what the top API for an OpenStack cloud is20:09
ttxin part because the proxying approach sounded a bit brittle20:09
ttxjoehuang worked with mordred to limit the scope of the team, which resulted in a split of Tricircle repos20:09
*** rrecio_ has quit IRC20:09
ttxTricircle is now focused on providing Network automation across region boundaries20:09
ttxThe "top cell" proxying stuff has been renamed to trio2o is kept unofficial/separate20:10
*** rrecio has joined #openstack-meeting20:10
ttxwhich removes most of my "slippery slope" concerns20:10
mordredyup. same here20:10
mordredI think this is a great split20:10
*** megm has quit IRC20:10
joehuangyes, one second, 3 thanks:)20:10
ttxjoehuang, mordred: anything to add ?20:10
joehuangThank you for your time to talk with  most of TCs (and also Russell and Armando) for a while in Barcelona summit, but missed the chance to talk with some TCs due to session overlapping.20:10
mordredI'd just like to say that I think the goals of the new slimmer tricircle are things that would be quite useful to end users20:11
joehuangThanks to Monty for helping Tricircle move forward, and learned that Tricircle and Shade/Oaktree in OpenStack-Infra can compliment each other for multi-clouds. Thanks to Thirrey for allocating summit venue and session slots.20:11
*** bobmel has quit IRC20:11
joehuangThank you for your insistance in API, which makes Tricircle being more focused and better and better.20:11
mordredjoehuang: thanks for working with us on getting this to a good place!20:11
ttxjoehuang: thanks for your patience !20:11
joehuangthank you all again20:11
ttxQuestions, comments ?20:11
joehuangSimilar requirements could also be found in the ops session in OpenStack Barcelona summit "Control Plane Design (multi-region)" Line 25~26, 47~50: https://etherpad.openstack.org/p/BCN-ops-control-plane-design20:11
*** chandrav has joined #openstack-meeting20:11
joehuangthey need tricircle networking capability across region20:12
*** megm has joined #openstack-meeting20:12
*** anilvenkata has quit IRC20:12
dimsjoehuang : any feedback from neutron cores/ptl on this? (just curious)20:13
sigmavirus1 comment: I've seen more tricircle activity on the mailing list than even some official projects (glance, security, etc.) and I think that bodes well20:13
joehuangI talked with Armando in Barcelona20:13
dhellmannso tricircle is limited to only networking functions now?20:13
mordredsigmavirus: ++20:14
ttxyes, and nice organizational diversity on the project too20:14
dimssigmavirus ++20:14
joehuangto dhellmann yes20:14
dimsjoehuang : cool20:14
ttxdhellmann: it facilitates bridging networking functions across cloud regions20:14
joehuangtalked to Armando in Barcelona20:14
dhellmannjoehuang : and the implementation is through a neutron plugin, and not a substitute neutron API?20:14
*** dmorita has quit IRC20:14
ttx(not finished yet afaict)20:14
joehuangto dhellmann, yes plugin, no api substitue20:15
dhellmannjoehuang : great, thanks for confirming that20:15
stevemarsounds like most of the concerns have been addressed20:15
dtroyerwill users see the regions similarly to how they appear for Compute operations? ie, user's only see one region setup20:15
flaper87indeed20:15
* dims steps out to answer the door20:15
joehuangthank you20:15
joehuangto dtroyer, yes20:15
*** dmorita has joined #openstack-meeting20:15
johnthetubaguyI think the scope is *much* improved, totally see the need for the network orchestration, but I would love a +1 from armax on that20:15
joehuangsee multi-region20:15
dtroyerjoehuang: thanks20:16
dhellmannjoehuang: I'm curious about how your interactions with the neutron team have been going. I know they are decomposing the stadium. Was there any interest in adopting the driver you've written?20:16
ttxarmax's +1 wouldn't hurt the proposal, but I'm fine with it as it stands20:16
*** Swami has joined #openstack-meeting20:16
joehuangArmax said he will review it, but I don't know he finished it or not after back from summit20:17
flaper87dhellmann: was about to ask that +120:17
*** Swami has quit IRC20:17
joehuangto dhellmann, there are tricircle's database, standalone API service, and XJOB20:17
joehuangit's not simply a plugin, including local and central plugin20:18
ttxI'm fine waiting for at least a comment from armax before finally approving20:18
*** Swami has joined #openstack-meeting20:18
*** Swami_ has joined #openstack-meeting20:18
dhellmannjoehuang : ah, I see.20:18
*** efried has joined #openstack-meeting20:18
flaper87ttx: we'll have to wait till next week anyway, there's no quorum on the patch yet20:19
dhellmannas long as there is no proxy api for neutron itself, I think it's fine to move ahead. Especially since the neutron team is dissolving the stadium.20:19
mordreddhellmann: ++20:19
dhellmannbut yeah, wait for quorum, of course :-)20:19
mordreddissolving a stadium seems like it would take much longer than using explosives to implode it ...20:19
mordredunless it's some really strong acid20:19
flaper87lol20:20
*** dmorita has quit IRC20:20
ttx#info No objections so far, but some TC members would really much like to get armax's opinion on it before final approval20:20
joehuangwould like to know when Amando can give feedback? He was added to reviewer since july20:20
ttxWe'll reach out to him and proceed next week with or without his comment20:21
dhellmann++20:21
ttxI don't want to hold it to some other PTL approval20:21
*** egallen has joined #openstack-meeting20:21
joehuangok, thank  you all20:21
flaper87joehuang: thanks for the work and the patience20:21
ttxAlso lots of TC members off today, won't hurt to let them ask a few more questions20:21
joehuangmy pleasure :)20:21
ttxSorry that may mean crazy hours for you next week as well20:21
joehuangslepless night:)20:22
ttx#info Tricircle shall be finally approved (barring any objection) next week meeting20:22
joehuangbut my pleasure anyway:)20:22
dtroyerjoehuang: thanks for making the personal time sacrifice to be here, it is really helpful20:22
ttxnext topic, small reordering upon request20:22
dhellmann++20:22
dimsjoehuang : thanks!20:23
joehuangthanks bye20:23
ttx#topic Add "Assume Good Faith" to OpenStack principles20:23
*** openstack changes topic to "Add "Assume Good Faith" to OpenStack principles (Meeting topic: tc)"20:23
*** ijw has quit IRC20:23
ttx#link https://review.openstack.org/36559020:23
*** joehuang has quit IRC20:23
ttxWe discussed that one last week20:23
ttxin flaper87's absence nobody felt strongly for or against it, lots of +0s20:23
ttxpersonally I think that for something to make it into our principles list there needs to be enough people caring strongly about it20:23
flaper87++20:23
ttxotherwise I fear we'll end up with a very long list of "sure, why not" principles20:23
dhellmannthe current version feels more like an admonition than a principle20:23
ttxso we waited until flaper87 was back20:23
dtroyerI am still struggling with this, it just doesn't feel right to be _here_.20:23
dhellmannyeah, it's definitely something I like, I'm not sure it fits with the other items we've put in this category so far, though20:24
flaper87dtroyer: where would you put it ?20:24
ttxMy position is that we don't have a critical mass of people that think it should definitely be a part of our principles20:24
*** raildo has quit IRC20:24
ttxI'm fine with it if there is such a critical mass, but I just don't see it20:24
dhellmannflaper87 : last week we talked about adding a "communication guidelines" section to the PTG20:25
dtroyerflaper87: I'm not sure20:25
flaper87dhellmann: mmh, I guess that could help20:25
edleafeHow would adding this change anything? That's what I don't understand20:25
armaxttx: I can have a pass at it today20:25
ttxarmax: that would be awesome thank you20:25
dtroyerflaper87: I agree with the ideal20:26
flaper87If folks feel more comfortable having it in the PTG, then I'll move it there. I'm, of course, ok with it being in the principles reference doc20:26
sigmavirusedleafe: as I understand it, the principles documentation is meant to document what are our principles today20:26
flaper87but I can see why peopl may not feel as comfortable with it20:26
sigmavirusedleafe: not so much "what does this fix?" or "what does this do to change things?"20:26
dimsflaper87 : dhellmann : y  "communication guidelines" would seem better20:26
jrollsigmavirus: +120:26
* sigmavirus wasn't around last week but supports this being documented somewhere20:26
dimssigmavirus ++20:26
fungii was in favor of dhellmann's suggestion last week for 'a "how to communicate successfully" section of the project team guide'20:27
ttxyeah, I would be much more comfortable if personal behavior guidelines like this were in the Project Team Guide or the CoC20:27
sigmavirusI don't have particularly strong feelings as to where, although I think it could fit there20:27
edleafesigmavirus: IMO, it's more of a "where do we _want_ to be", not "where are we now"20:27
dhellmannedleafe : it will become that, but we've said at this point we're still trying to write down where we are20:27
ttxbecause I don't think we should have 100 principles and I can see us having a 100 personal behavior guidelines :)20:27
*** dandruta has joined #openstack-meeting20:27
smcginnis+120:27
dhellmannugh, I hope not 100 of those, either20:28
sigmavirusttx: so it's not just about personal behaviour, in my opinion. Yes communication is the primary place where we should be assuming good faith, but it also applies in patches20:28
flaper87Ok, I'll move it... I don't feel strongly about this being a principle20:28
ttxdhellmann: figure of speech20:28
dtroyeredleafe: I hope the majority of the community already does this… but maybe not given the kinds of comments made during the last election cycle20:28
* flaper87 really thought it was, though.20:28
sigmavirusI think that a lot of the mailing discussions about mass sending of patches are missing this point20:28
dhellmannttx: :-)20:28
fungisigmavirus: code is speech ;)20:28
*** krtaylor has joined #openstack-meeting20:28
edleafedtroyer: exactly. It's aspirational, but not where things are today20:28
stevemarsigmavirus: or mass bug subscriptions :)20:28
sigmavirusfungi: fair, I think most people distinguish between "code" and "email" where they view email more as communication20:28
*** lyarwood has left #openstack-meeting20:28
sigmavirusstevemar: right, these are things that are annoying, but I suspect the people are doing it in good faith20:29
ttxedleafe: it's also difficult to mandate20:29
fungii expect as a community we communicate more through code review comments than e-mail20:29
*** cdent has quit IRC20:29
edleafettx: that too20:29
ttx#agreed this should be put in the Project Team Guide instead20:29
jroll1/b 4020:29
sigmavirusfungi: absolutely. I'm just thinking of events on the mailing where people felt they were being attacked instead of assuming good faith20:29
jrolloops.20:29
dhellmannfungi : that's certainly my goal20:29
sigmavirusjroll: don't use irssi :P20:29
flaper87would people feel comfortable with this being in the principles doc once we start adding "where we want to be" ?20:29
*** jaugustine has quit IRC20:29
ttx#info no critical mass of members agree this should live as a principle at this stage20:29
jrollsigmavirus: I would never (weechat) :D20:30
dtroyerflaper87: yes20:30
flaper87Or is the concept of assuming good faith that folks are not comfortable with ?20:30
fungisigmavirus: i agree it's just as possible to crop up in bug triage, code review, irc channels... we have lots of means of communication20:30
flaper87I mean, comfortable with having it in the principles file20:30
flaper87mmh20:30
ttxflaper87: sounds like a "vision" rather than a "principles list" :)20:30
sigmavirusflaper87: that's a good question20:30
dhellmannflaper87 : possibly phrased differently20:30
edleafeflaper87: I don't think it's possible to tell people how to feel20:30
flaper87dhellmann: what would be your suggestion? Asking because the last wording came out of feedback20:30
ttxI don 't think "where we want to be" belongs in the principles doc20:31
dhellmannflaper87 : maybe something more general about taking open and clear communication seriously20:31
flaper87The feedback was to make it more asperational20:31
fungihowever, it's possible to explain that certain positions in communication are more effective at getting your point across than others, and at understanding the points made by others20:31
sigmavirusedleafe: that's not how I read flaper87's review in the slightest20:31
flaper87edleafe: it's not how ppl should feel but how they should communicate20:31
*** david-lyle_ has joined #openstack-meeting20:32
*** CarolBarrett has quit IRC20:32
flaper87Ok, I'll abandon this path or reword it entirely to not mention good faith but focus on communication20:32
fungi"assuming good faith" is less about feeling a certain way, and more about making conscious vs unconscious choices when interpreting personal communication, private or public20:32
*** david-lyle has quit IRC20:32
ttxedleafe: I still think it's valuable that we document expected communication behavior -- just think it's not a "principle", and should live in the Poject Team Guide instead20:32
RockygWell, the principle is we act in good faith.20:32
*** jaugustine has joined #openstack-meeting20:32
sigmavirusfungi:++20:32
*** jaugustine has quit IRC20:33
sigmavirusRockyg: right20:33
dhellmannflaper87 : I have some ideas about the communication angle, if you'd like to work together on that20:33
edleafePositive communication is a great angle, even if you don't assume someone is acting in good faith. Always rise above.20:33
flaper87dhellmann: I'd appreciate your help on this, thanks20:34
dhellmannflaper87 : cool, maybe early next week we can chat20:34
flaper87sounds perfect, this week would be impossible for me20:34
*** Swami has quit IRC20:34
ttxok, let's move on ?20:34
*** Swami has joined #openstack-meeting20:34
flaper87yup, I'm good20:35
ttx#topic Create a project tag for zero-downtime upgrades20:35
*** openstack changes topic to "Create a project tag for zero-downtime upgrades (Meeting topic: tc)"20:35
ttx#link https://review.openstack.org/37268620:35
ttxThis one looks pretty close.20:35
ttxThere is a one-word change suggested by Doug that we might want to add before or after we approve it20:35
stevemargetting the testing going on that one is going to be hard, but i appreciate the high target/goal that dolphm is setting20:36
ttxunless dolphm is around to fix it, we can approve this and then change the word in a subsequent change ?20:36
fungisounds fine to me20:36
mordredstevemar: ++20:36
mordredI like the phrase "continuous tempest"20:37
dolphmi am around20:37
ttxstevemar: yes. I like that it's not ready to apply but sets the vision20:37
dolphmi'm happy to make the change, but wanted to wait for any additional feedback before doing a minor revision20:37
ttxdolphm: we can either approve it now or you fix it and we reapply our votes20:37
ttxdolphm: it has majority support already20:38
dhellmannttx: I'm OK with changing that word later20:38
dolphmttx: just submitted the revision :)20:38
ttxyes, it's not as if people would apply that tag tomorrow20:38
ttxok, reapply votes20:38
ttxI'm first20:38
ttxstevemar: ?20:39
ttxlast call20:40
johnthetubaguywere we going to also discuss the follow on change? https://review.openstack.org/#/c/38930020:41
ttxok, approving now20:41
stevemarsorry, double booked...20:41
stevemarttx: +1 from me :)20:42
ttxhmm, now I'm confused20:42
dolphmstevemar: i proposed a minor revision and cleared your vote20:42
ttxSomehow I missed that there were two of those20:42
stevemardolphm: yes, i see that, re-adding it now (even if it's approved)20:42
fungizero downtime is less restrictive than zero impact20:42
dolphmthe subsequent change (zero-impact upgrades) was proposed substantially more recently (in case we want more time to socialize it)20:43
ttxjohnthetubaguy: so yes we should20:43
dolphmfungi: other way around20:43
dolphmfungi: zero-impact is the ultimate goal20:43
johnthetubaguythe session on these at the summit was good, there is *down* and a bit degraded, and *no* degredation20:43
fungii think that's what i said?20:43
dolphmfungi: oh wow, i misread :)20:44
ttxzero-impact looks ok to me20:44
dolphmfungi: you were totally correct20:44
*** ayoung has quit IRC20:44
fungiokay, just making sure i was reading the specs the right way 'round ;)20:44
ttxI propose we approve it too unless someone objects20:44
*** CarolBarrett has joined #openstack-meeting20:44
ttx#link https://review.openstack.org/#/c/38930020:44
ttxeven if it wasn't formally on the agenda20:44
johnthetubaguyyeah, I think approve both, I like the completeness that gives us20:45
ttxalright then, last chance to vote on it20:46
fungiit's been up and had the formal-vote tag for a few weeks at this point, so seems like plenty of time20:46
*** myoung|afk is now known as myoung20:46
ttxannnd... approved20:46
ttxThanks dolphm for painting that shiny picture20:46
dolphm\o/20:46
ttx#topic Add "servant leadership" to principles20:46
johnthetubaguy+120:46
*** openstack changes topic to "Add "servant leadership" to principles (Meeting topic: tc)"20:46
funginow we just need some projects to start buying the reprints20:46
ttx#link https://review.openstack.org/39086420:46
ttxchecking out the last rev20:47
*** mickeys has joined #openstack-meeting20:47
jrollohai20:47
mordredjroll: will you kill me if I nitpick two words at this point?20:47
stevemarmordred: :)20:47
mordredoh - nevermind - it's consistent with other principles20:47
ttxWe are not allowed to pass a principle without nitpicking anyway20:47
jrollmordred: I've had patches in flight for nine months in the past, this is nothing20:47
*** toscalix_ has joined #openstack-meeting20:48
edleafettx: You should add "nitpicking" as a principle20:48
ttxI like it20:48
ttxedleafe: maybe an expected behavior20:48
jrolllol20:48
* mordred was going to quibble about the word "should"20:48
dhellmannedleafe : I think we call that bike shedding, don't we? ;-)20:48
mordredjroll: I have patches still open from 201420:48
ttxmordred: you want "shalt" ?20:48
fungiit's slightly disjoint with the respective electorates, but i'm okay with the assertion that leaders serve more people than merely those who are able to vote to elect them20:48
Rockygwell, wouldn't it really be bikeshedding :-)20:48
mordredttx: I just wanted to remove the word should20:49
jrollmordred: I purge sometimes :)20:49
mordred"OpenStack leaders should hold their positions only in order to serve" to "OpenStack leaders hold their positions in order to serve"20:49
ttxI think we can refine the wording but I think it is a key principle we have20:49
fungimordred: yeah, an ietf reading of "should" there waters it down, agreed20:49
Rockygdang dhellmann totally type faster...20:49
mordredfungi: yah. the ietf infects my brain20:49
fungii prefer an ietf "must"20:49
ttxmordred: yes, I kind of agree with you here20:49
mordredI think it's great though - maybe that's a follow up patch?20:50
jrollmmm, yeah, that's a good point20:50
dhellmannmordred : ++ to removing20:50
*** srwilkers has quit IRC20:50
ttxmaybe jroll can ninja it20:50
mordredsame with the TC line - the PTL line is good20:50
jrollI could20:50
* dhellmann makes sound effects to go with jroll's ninja-ing20:50
ttxclickety click20:50
jrollninja'd20:51
dhellmannttx: I didn't know you were a foley artist20:51
ttxjroll: stopped the wallclock, ninja time 8.33Sec20:51
*** Swami has quit IRC20:52
jrollttx: I'm slow today because sitting on the couch20:52
ttxreapply votes ad lib20:52
dimsjroll : "contributors to and users"...sounds slightly off20:52
dtroyerdims "and users of"20:52
ttx"contributors to and users of"20:52
jrolldims: "contributors to and users of"20:52
*** Swami_ has quit IRC20:53
jrollcontributors to the project and users of the project20:53
ttxI did a double read on that one too20:53
jrollwould be the long form20:53
dimskk20:53
jrollhappy to do grammar-y things in a follow-up if this is hard to read :)20:53
dhellmannI think you want some commas: contributors to, and users of, ...20:53
ttxdims: nitpicking accepted, we can now proceed20:53
ttxthe check queue is on fire today20:54
dimshehe, i already voted20:54
ttxapproved20:54
ttx#topic Open discussion20:54
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:54
ttxOne change I wanted to attract your attention on is the Neutron project cleanup patch20:54
ttx#link https://review.openstack.org/#/c/392010/20:54
ttxIn particular I was wondering if neutron-vpnaas can be un-officialized this fast, since it was assert:follows-standard-deprecation20:54
ttxI wonder if we should not mandate a longer path for that one20:54
jrollquick note, I'll have a patch to clean up a couple ironic governance things sometime this week20:55
ttx(otherwise there is a risk of depreciating the protection supposedly offered by this tag)20:55
mordredI think we should ... HOWEVER ... it apparently has no humans20:55
mordredso we may be finding ourselves in a tricky spot20:55
jroll(ironic clarified what does and doesn't belong, and also has a dead project or two)20:55
ttxyeah... hopefully it doesn't have any user either20:55
dhellmannif it's going to bypass the deprecation period, we need to make a lot of noise about that so any users do know20:56
ttxmordred: in an ideal world the thread on -ops that the deprecation process would raise would confirm that there is no user20:56
ttxand if there are, could trigger them to actually take it over20:56
*** tonytan4ever has quit IRC20:56
fungisimilar questions were raised in one of the teams' driver removal discussions20:56
dhellmannwe have a nice long list of patches related to the cycle goal already20:56
dhellmann#link https://review.openstack.org/#/q/topic:goal-remove-incubated-oslo-code20:56
*** e0ne has joined #openstack-meeting20:57
*** tonytan4ever has joined #openstack-meeting20:57
*** srwilkers has joined #openstack-meeting20:57
ttxmordred: though in all fairness they are not removing the feature20:57
ttxso /technically/ nothing is deprecated or removed20:57
ttxjust left to bitrot20:58
fungii guess at some point ttx will just fast-approve the topic:goal-remove-incubated-oslo-code changes that have sufficient roll-call +1 right?20:58
amrithto all new TC members, I offered to post this PSA in the TC meeting today for gothicmindfood who isn't able to attend. Would you please let her know what your schedule looks like to attend the TC training similar to the one which was conducted earlier this year. Thanks!20:58
ttxfungi: yes20:58
ttxanyway, if you carte one way or another, please chime on the patch. We'll likely review that one next week20:58
ttxcare*20:58
dtroyeramrith: I heard her say 'next year' in BCN, do you know if that is still the case?20:59
ttx"2017"20:59
*** claudiub has quit IRC20:59
ttxFYI PTG registration should officially open today or tomorrow20:59
*** rcernin has joined #openstack-meeting20:59
ttxdepending on how much energy I have left to review forms and web pages20:59
*** CarolBarrett has quit IRC21:00
ttxand time is up21:00
amrithdtroyer, I believe that you are correct. let me check if she provided me with some dates.21:00
dhellmannfungi : yes, the approval rules are at http://governance.openstack.org/reference/house-rules.html#goal-updates-from-ptls21:00
amrithI don't think so though21:00
amrithone second, will catch you21:00
ttxThanks everyone!21:00
amrithon some other channel if not this one21:00
jrollthanks ttx21:00
ttx#endmeeting21:00
amriththx ttx21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Tue Nov  8 21:00:32 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-08-20.01.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-11-08-20.01.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-11-08-20.01.log.html21:00
*** Swami_ has joined #openstack-meeting21:00
*** Swami has joined #openstack-meeting21:01
*** jdurgin has quit IRC21:01
*** singhj has quit IRC21:03
*** jdurgin has joined #openstack-meeting21:04
*** comay_ has joined #openstack-meeting21:04
*** david-lyle_ has quit IRC21:05
*** david-lyle_ has joined #openstack-meeting21:05
*** dmorita has joined #openstack-meeting21:09
*** askb has joined #openstack-meeting21:11
*** Hosam has joined #openstack-meeting21:14
*** Hosam has quit IRC21:14
*** Hosam_ has joined #openstack-meeting21:14
*** fzdarsky|afk has quit IRC21:17
*** camunoz has joined #openstack-meeting21:17
*** kenji-i has quit IRC21:18
*** Guest24494 is now known as melwitt21:18
*** dprince has quit IRC21:18
*** e0ne has quit IRC21:19
*** lblanchard has quit IRC21:20
*** bobmel has joined #openstack-meeting21:23
*** david-lyle_ has quit IRC21:24
*** srwilkers has quit IRC21:26
*** toscalix_ has quit IRC21:27
*** bobmel has quit IRC21:29
*** jprovazn has quit IRC21:33
*** singhj has joined #openstack-meeting21:33
*** krtaylor has quit IRC21:34
*** beisner has quit IRC21:35
*** egallen has quit IRC21:36
*** beisner has joined #openstack-meeting21:39
*** ijw has joined #openstack-meeting21:40
*** spotz is now known as spotz_zzz21:40
*** ijw has quit IRC21:41
*** ijw has joined #openstack-meeting21:41
*** gordc has left #openstack-meeting21:42
*** Swami has quit IRC21:43
*** Swami_ has quit IRC21:43
*** balajiiyer has joined #openstack-meeting21:46
*** Hosam_ has quit IRC21:48
*** Hosam has joined #openstack-meeting21:48
*** singhj has quit IRC21:50
*** annegentle has quit IRC21:50
*** caboucha has quit IRC21:50
*** gouthamr has quit IRC21:52
*** cleong has quit IRC21:54
*** beisner- has joined #openstack-meeting21:54
*** beisner has quit IRC21:56
*** beisner- is now known as beisner21:56
*** chris_morrell has joined #openstack-meeting21:57
*** trown is now known as trown|outtypewww21:59
*** JRobinson__ has joined #openstack-meeting21:59
*** chandrav has quit IRC22:02
*** lpetrut has quit IRC22:02
*** jgregor has quit IRC22:03
*** jgregor has joined #openstack-meeting22:03
*** rtheis has quit IRC22:05
*** annegentle has joined #openstack-meeting22:06
*** Swami_ has joined #openstack-meeting22:06
*** Swami has joined #openstack-meeting22:06
*** julim has quit IRC22:07
*** eharney has quit IRC22:07
*** jamesdenton has quit IRC22:07
*** jgregor has quit IRC22:08
*** singhj has joined #openstack-meeting22:12
*** ykatabam has joined #openstack-meeting22:13
*** edtubill has quit IRC22:14
*** chris_morrell has quit IRC22:15
*** rossella_s has joined #openstack-meeting22:18
*** jgregor has joined #openstack-meeting22:20
*** bobmel has joined #openstack-meeting22:25
*** david-lyle has joined #openstack-meeting22:26
*** ijw has quit IRC22:27
*** cody-somerville has joined #openstack-meeting22:28
*** cody-somerville has quit IRC22:28
*** cody-somerville has joined #openstack-meeting22:28
*** bobmel has quit IRC22:30
*** csomerville has quit IRC22:30
*** haleyb_ has joined #openstack-meeting22:30
*** thorst_ has quit IRC22:32
*** haleyb_ has quit IRC22:35
*** jgregor has quit IRC22:36
*** tonytan4ever has quit IRC22:36
*** jgregor has joined #openstack-meeting22:37
*** baoli has quit IRC22:37
*** darrenc is now known as darrenc_vpn22:39
*** pradk has quit IRC22:40
*** jgregor has quit IRC22:41
*** dandruta has quit IRC22:41
*** mriedem has quit IRC22:44
*** slayer has quit IRC22:47
*** designbybeck has quit IRC22:50
*** david-lyle_ has joined #openstack-meeting22:50
*** david-lyle_ has quit IRC22:54
*** thorst_ has joined #openstack-meeting22:55
*** singhj has quit IRC23:00
*** efried has quit IRC23:01
*** galstrom is now known as galstrom_zzz23:02
*** paw_away has joined #openstack-meeting23:02
*** ijw has joined #openstack-meeting23:05
*** egallen has joined #openstack-meeting23:05
*** paw_ has quit IRC23:06
*** rajinir has quit IRC23:06
*** gyee has joined #openstack-meeting23:07
*** thorst_ has quit IRC23:07
*** maeker has quit IRC23:08
*** asselin has quit IRC23:08
*** maeker has joined #openstack-meeting23:08
*** kaminohana has joined #openstack-meeting23:13
*** spzala has quit IRC23:14
*** rrecio_ has joined #openstack-meeting23:15
*** rrecio_ has quit IRC23:15
*** ijw has quit IRC23:16
*** lixinhui_ has joined #openstack-meeting23:16
*** paw_ has joined #openstack-meeting23:16
*** lamt has quit IRC23:16
*** jmckind has quit IRC23:17
*** lixinhui_ has quit IRC23:17
*** mriedem has joined #openstack-meeting23:17
*** rrecio has quit IRC23:18
*** rcernin has quit IRC23:18
*** paw_away has quit IRC23:20
*** absubram has joined #openstack-meeting23:21
*** bobh_ has quit IRC23:24
*** bobh_ has joined #openstack-meeting23:25
*** darrenc_vpn is now known as darrenc23:28
*** netapp has quit IRC23:28
*** netapp has joined #openstack-meeting23:29
*** spzala has joined #openstack-meeting23:30
*** bobh_ has quit IRC23:30
*** ijw has joined #openstack-meeting23:31
*** rossella_s has quit IRC23:31
*** Hosam has quit IRC23:34
*** xyang1 has quit IRC23:35
*** spzala has quit IRC23:35
*** ijw has quit IRC23:36
*** gyee has quit IRC23:38
*** david-lyle has quit IRC23:38
*** david-lyle has joined #openstack-meeting23:40
*** comay_ has quit IRC23:43
*** Patifa has joined #openstack-meeting23:46
*** ijw has joined #openstack-meeting23:46
*** rbak_ has quit IRC23:46
*** ayoung has joined #openstack-meeting23:53
*** ijw has quit IRC23:53
*** hashar has quit IRC23:57
*** oomichi has quit IRC23:57
*** oomichi has joined #openstack-meeting23:58

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