Tuesday, 2016-07-12

*** shashank_hegde has joined #openstack-meeting00:01
*** kei has joined #openstack-meeting00:02
*** kei_ has quit IRC00:03
*** leeantho has quit IRC00:03
*** kei_ has joined #openstack-meeting00:05
*** shaohe_feng_ has joined #openstack-meeting00:06
*** shaohe_feng has quit IRC00:06
*** shaohe_feng_ is now known as shaohe_feng00:06
*** ivar-laz_ has joined #openstack-meeting00:06
*** kei has quit IRC00:07
*** heyongli has quit IRC00:07
*** Patifa has quit IRC00:07
*** heyongli has joined #openstack-meeting00:07
*** trozet has joined #openstack-meeting00:08
*** toscalix has joined #openstack-meeting00:09
*** ivar-lazzaro has quit IRC00:09
*** esberglu has joined #openstack-meeting00:09
*** ivar-laz_ has quit IRC00:11
*** shaohe_feng has quit IRC00:15
*** shaohe_feng has joined #openstack-meeting00:16
*** heyongli has quit IRC00:17
*** heyongli has joined #openstack-meeting00:17
*** hoangcx has quit IRC00:18
*** zz_dimtruck is now known as dimtruck00:19
*** roxanaghe has quit IRC00:20
*** karthikp_ has joined #openstack-meeting00:21
*** Suyash has quit IRC00:21
*** toddjohn has joined #openstack-meeting00:21
*** bapalm has quit IRC00:22
*** Julien-zte has joined #openstack-meeting00:23
*** Wenzhi_ has quit IRC00:24
*** Wenzhi has joined #openstack-meeting00:24
*** toscalix has quit IRC00:25
*** bapalm has joined #openstack-meeting00:25
*** Leo_ has joined #openstack-meeting00:25
*** shaohe_feng has quit IRC00:26
*** xarses has quit IRC00:26
*** shaohe_feng has joined #openstack-meeting00:26
*** heyongli has quit IRC00:27
*** dtrainor has joined #openstack-meeting00:28
*** Leom has joined #openstack-meeting00:28
*** heyongli has joined #openstack-meeting00:28
*** sindhu has joined #openstack-meeting00:30
*** Leo_ has quit IRC00:30
*** toddjohn has quit IRC00:32
*** cody-somerville has quit IRC00:33
*** pvaneck has quit IRC00:33
*** annp has quit IRC00:34
*** karthikp_ has quit IRC00:35
*** adiantum has quit IRC00:35
*** karthikp_ has joined #openstack-meeting00:35
*** cody-somerville has joined #openstack-meeting00:36
*** singhj has quit IRC00:36
*** shaohe_feng has quit IRC00:36
*** shaohe_feng has joined #openstack-meeting00:36
*** enriquetaso has quit IRC00:37
*** heyongli has quit IRC00:38
*** heyongli has joined #openstack-meeting00:38
*** gyee has quit IRC00:38
*** bobh has joined #openstack-meeting00:40
*** Leom has quit IRC00:40
*** singhj has joined #openstack-meeting00:40
*** mbound has joined #openstack-meeting00:41
*** banix has joined #openstack-meeting00:41
*** itzdilip has quit IRC00:45
*** singhj has quit IRC00:45
*** itzdilip has joined #openstack-meeting00:45
*** shashank_hegde has quit IRC00:45
*** mbound has quit IRC00:46
*** Suyash has joined #openstack-meeting00:46
*** shaohe_feng has quit IRC00:46
*** shaohe_feng has joined #openstack-meeting00:47
*** heyongli has quit IRC00:48
*** shashank_hegde has joined #openstack-meeting00:48
*** heyongli has joined #openstack-meeting00:48
*** ijw has quit IRC00:50
*** toddjohn has joined #openstack-meeting00:51
*** aranjan_ has joined #openstack-meeting00:51
*** aranjan has quit IRC00:55
*** toddjohn has quit IRC00:55
*** aranjan_ has quit IRC00:56
*** shaohe_feng has quit IRC00:56
*** shaohe_feng has joined #openstack-meeting00:57
*** heyongli has quit IRC00:58
*** heyongli has joined #openstack-meeting00:58
*** Swami has quit IRC00:59
*** jaypipes has quit IRC00:59
*** yinwei_computer has joined #openstack-meeting01:00
*** iceyao has joined #openstack-meeting01:01
*** cody-somerville has quit IRC01:02
*** bobh has quit IRC01:02
*** spzala has quit IRC01:03
*** cody-somerville has joined #openstack-meeting01:04
*** cody-somerville has quit IRC01:04
*** cody-somerville has joined #openstack-meeting01:04
*** dtrainor has quit IRC01:04
*** shaohe_feng has quit IRC01:07
*** shaohe_feng has joined #openstack-meeting01:07
*** toddjohn has joined #openstack-meeting01:07
*** trozet has quit IRC01:07
*** shashank_hegde has quit IRC01:08
*** heyongli has quit IRC01:08
*** ijw has joined #openstack-meeting01:09
*** banix has quit IRC01:10
*** heyongli has joined #openstack-meeting01:11
*** toddjohn_ has joined #openstack-meeting01:11
*** zhurong has joined #openstack-meeting01:12
*** Apoorva_ has joined #openstack-meeting01:13
*** toddjohn has quit IRC01:15
*** azbiswas has joined #openstack-meeting01:15
*** Apoorva has quit IRC01:16
*** Apoorva_ has quit IRC01:17
*** shaohe_feng has quit IRC01:17
*** garthb has quit IRC01:17
*** shaohe_feng has joined #openstack-meeting01:18
*** heyongli has quit IRC01:19
*** toddjohn has joined #openstack-meeting01:19
*** heyongli has joined #openstack-meeting01:19
*** itzdilip has quit IRC01:20
*** azbiswas has quit IRC01:21
*** spzala has joined #openstack-meeting01:21
*** mtanin___ has joined #openstack-meeting01:21
*** thorst has joined #openstack-meeting01:21
*** spzala has quit IRC01:21
*** spzala_ has joined #openstack-meeting01:22
*** toddjohn_ has quit IRC01:22
*** mtanino has quit IRC01:22
*** itzdilip has joined #openstack-meeting01:24
*** dimtruck is now known as zz_dimtruck01:24
*** toddjohn has quit IRC01:25
*** toddjohn has joined #openstack-meeting01:25
*** Qiming has joined #openstack-meeting01:25
*** spzala_ has quit IRC01:25
*** fnaval has quit IRC01:26
*** shaohe_feng has quit IRC01:27
*** shaohe_feng has joined #openstack-meeting01:28
*** heyongli has quit IRC01:29
*** heyongli has joined #openstack-meeting01:29
*** xarses has joined #openstack-meeting01:29
*** s3wong has quit IRC01:30
*** Daisy has joined #openstack-meeting01:32
*** Daisy has quit IRC01:33
*** Daisy has joined #openstack-meeting01:33
*** karthikp_ has quit IRC01:35
*** toddjohn has quit IRC01:36
*** weshay has quit IRC01:37
*** zhhuabj has quit IRC01:37
*** shaohe_feng has quit IRC01:37
*** shaohe_feng has joined #openstack-meeting01:38
*** fnaval has joined #openstack-meeting01:39
*** heyongli has quit IRC01:39
*** sindhu has quit IRC01:39
*** heyongli has joined #openstack-meeting01:40
*** ljxiash has quit IRC01:40
*** ljxiash has joined #openstack-meeting01:40
*** toddjohn has joined #openstack-meeting01:40
*** toddjohn has quit IRC01:41
*** ajmiller has quit IRC01:42
*** ajmiller has joined #openstack-meeting01:42
*** toddjohn has joined #openstack-meeting01:43
*** sindhu has joined #openstack-meeting01:44
*** karthikp_ has joined #openstack-meeting01:45
*** ljxiash has quit IRC01:45
*** thorst has quit IRC01:47
*** Daisy has quit IRC01:47
*** thorst has joined #openstack-meeting01:47
*** shaohe_feng has quit IRC01:48
*** zhangshuai has joined #openstack-meeting01:48
*** shaohe_feng has joined #openstack-meeting01:49
*** heyongli has quit IRC01:49
*** azbiswas has joined #openstack-meeting01:50
*** azbiswas has quit IRC01:50
*** zul has quit IRC01:50
*** zhhuabj has joined #openstack-meeting01:50
*** heyongli has joined #openstack-meeting01:50
*** azbiswas has joined #openstack-meeting01:50
*** thorst has quit IRC01:51
*** piet has quit IRC01:52
*** thorst has joined #openstack-meeting01:55
*** zz_dimtruck is now known as dimtruck01:56
*** thorst has quit IRC01:56
*** casbeki has joined #openstack-meeting01:56
*** thorst has joined #openstack-meeting01:56
*** ljxiash has joined #openstack-meeting01:57
*** unicell1 has quit IRC01:57
*** shaohe_feng has quit IRC01:58
*** shaohe_feng has joined #openstack-meeting01:58
*** heyongli has quit IRC02:00
*** ajmiller has quit IRC02:00
*** ajmiller has joined #openstack-meeting02:00
*** heyongli has joined #openstack-meeting02:00
*** heyongli has quit IRC02:00
*** zul_ has joined #openstack-meeting02:01
*** thorst has quit IRC02:02
*** zul has joined #openstack-meeting02:02
*** singhj has joined #openstack-meeting02:02
*** Daisy has joined #openstack-meeting02:03
*** toddjohn has quit IRC02:03
*** singhj has quit IRC02:06
*** csomerville has joined #openstack-meeting02:06
*** shaohe_feng has quit IRC02:08
*** shaohe_feng has joined #openstack-meeting02:09
*** cody-somerville has quit IRC02:10
*** zul_ has quit IRC02:10
*** zhhuabj has quit IRC02:14
*** casbeki has left #openstack-meeting02:15
*** Sukhdev_ has quit IRC02:15
*** Daisy_ has joined #openstack-meeting02:16
*** sindhu has quit IRC02:17
*** Daisy has quit IRC02:17
*** karthikp_ has quit IRC02:18
*** shaohe_feng has quit IRC02:18
*** karthikp_ has joined #openstack-meeting02:19
*** shaohe_feng has joined #openstack-meeting02:19
*** itzdilip has quit IRC02:28
*** itzdilip has joined #openstack-meeting02:28
*** jamesdenton has joined #openstack-meeting02:28
*** shaohe_feng has quit IRC02:29
*** shaohe_feng has joined #openstack-meeting02:29
*** zhhuabj has joined #openstack-meeting02:31
*** mkrai has joined #openstack-meeting02:32
*** gongysh has joined #openstack-meeting02:34
*** amotoki has joined #openstack-meeting02:36
*** rfolco has quit IRC02:39
*** shaohe_feng has quit IRC02:39
*** yamahata has quit IRC02:40
*** rossella_s has quit IRC02:40
*** shaohe_feng has joined #openstack-meeting02:40
*** rossella_s has joined #openstack-meeting02:40
*** azbiswas has quit IRC02:40
*** iyamahat has quit IRC02:43
*** piet has joined #openstack-meeting02:43
*** mtanino has joined #openstack-meeting02:45
*** itzdilip has quit IRC02:46
*** mtanin___ has quit IRC02:47
*** sindhu has joined #openstack-meeting02:49
*** shubhams has joined #openstack-meeting02:49
*** shaohe_feng has quit IRC02:49
*** shaohe_feng has joined #openstack-meeting02:49
*** mtanino has quit IRC02:50
*** krtaylor has joined #openstack-meeting02:50
*** Namrata has joined #openstack-meeting02:52
*** aranjan has joined #openstack-meeting02:53
*** piet has quit IRC02:54
*** ijw has quit IRC02:54
*** piet has joined #openstack-meeting02:54
*** yanyanhu has joined #openstack-meeting02:56
*** Namrata has quit IRC02:56
*** Daisy_ has quit IRC02:57
*** Daisy has joined #openstack-meeting02:57
*** sarob has joined #openstack-meeting02:57
*** sudipto has joined #openstack-meeting02:58
*** amotoki has quit IRC02:59
*** shaohe_feng has quit IRC02:59
mkrai#startmeeting zun03:00
openstackMeeting started Tue Jul 12 03:00:02 2016 UTC and is due to finish in 60 minutes.  The chair is mkrai. Information about MeetBot at http://wiki.debian.org/MeetBot.03:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.03:00
*** openstack changes topic to " (Meeting topic: zun)"03:00
openstackThe meeting name has been set to 'zun'03:00
mkrai#link https://wiki.openstack.org/wiki/Zun#Agenda_for_2016-07-12_0300_UTC Today's agenda03:00
mkrai#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
WenzhiWenzhi Yu03:00
*** shaohe_feng has joined #openstack-meeting03:00
sudiptoo/03:00
yanyanhuhello03:00
shubhamsshubham o/03:00
eliqiaoo/03:00
mkraiThanks Wenzhi  sudipto yanyanhu shubhams eliqiao for joining today03:01
*** vivek___ has joined #openstack-meeting03:01
mkraiLet's wait for a minute for others to join03:01
*** Namrata_ has joined #openstack-meeting03:01
*** Daisy has quit IRC03:02
mkrai#topic Announcements03:02
*** openstack changes topic to "Announcements (Meeting topic: zun)"03:02
Namrata_O/03:02
mkraihongbin is on travel this week so I will chair this meeting.03:02
mkraiHey Namrata_03:02
mkraiAny other announcement from team?03:02
yanyanhuhe is gonna join openstack day china I think :)03:02
mkraiYes I think he already have done it03:03
yanyanhuyea03:03
flwang1o/03:03
mkraiHey flwang103:03
eliqiaomkrai: not yet, it's the day after tomorrow.03:03
vivek___o/03:03
flwang1mkrai: hey there03:03
mkraiOh I see03:03
mkraiHi vivek___03:03
mkrai#topic Review Action Items03:03
*** openstack changes topic to "Review Action Items (Meeting topic: zun)"03:03
mkraihongbin create an etherpad for the COE API design (TBD)03:04
*** zhhuabj has quit IRC03:04
mkraiThis task is still to be done03:04
mkraiWe will discuss the status in next meeting03:04
mkraiAnyone has something to add on this?03:04
*** zhhuabj has joined #openstack-meeting03:04
*** toddjohn has joined #openstack-meeting03:04
mkraiOk let's advance topic03:05
mkrai#topic Runtimes API design03:05
*** openstack changes topic to "Runtimes API design (Meeting topic: zun)"03:05
mkrai#link https://blueprints.launchpad.net/zun/+spec/api-design The BP03:05
mkrai#link https://etherpad.openstack.org/p/zun-containers-service-api Etherpad03:05
mkraiOk so I have written down all the basic APIs for containers03:06
mkraiAnd also some advanced and miscellaneous03:06
mkraiI will wait for few minutes for everyone to read03:06
*** ljxiash has quit IRC03:06
*** ljxiash has joined #openstack-meeting03:06
mkrai#link https://etherpad.openstack.org/p/zun-containers-service-api-spec03:07
mkraiPlease see above link03:07
mkraiPlease feel free to add or update any APIs03:08
mkraiI plan to submit spec this week03:08
yanyanhuquick question, for basic operations like CUDR, will COEs and runtime based implementation share the same API interface?03:08
mkraiyanyanhu, As of now, no03:09
*** toddjohn has quit IRC03:09
yanyanhuI see03:09
mkraiIt is quite not possible to club both APIs03:09
yanyanhuyes, feel so as well03:09
*** ljxiash_ has joined #openstack-meeting03:09
mkraiWe will create APIs for COEs this week or so03:09
*** shaohe_feng has quit IRC03:10
*** sindhu has quit IRC03:10
mkraiOk I will leave etherpad offline, please add your ideas03:10
*** jamesdenton has quit IRC03:10
*** shaohe_feng has joined #openstack-meeting03:10
*** klkumar has joined #openstack-meeting03:11
mkraiShall we advance or someone has to add anything?03:11
*** ljxiash has quit IRC03:11
*** zhurong has quit IRC03:11
*** Namrata_ has quit IRC03:11
yanyanhuwill add comment offline03:11
mkraiOk thanks yanyanhu03:12
*** Daisy has joined #openstack-meeting03:12
mkrai#topic Nova integration03:12
*** openstack changes topic to "Nova integration (Meeting topic: zun)"03:12
mkrai#link https://blueprints.launchpad.net/zun/+spec/nova-integration The BP03:12
*** Namrata has joined #openstack-meeting03:12
*** zhurong has joined #openstack-meeting03:12
mkraiIs aditi here today?03:12
*** sindhu has joined #openstack-meeting03:12
yanyanhuguess not03:13
mkraiOk I think she has not attended quite few meetings03:13
mkraiAnd as I feel this bp is important for us, so please feel free to take up this one03:13
*** ljxiash has joined #openstack-meeting03:13
mkraiAnyone interested here to work on this?03:13
NamrataYes I am03:14
*** ljxiash_ has quit IRC03:14
mkraiThanks Namrata03:14
mkraiPlease connect with aditi03:14
yanyanhuAnd I guess we may need a spec or etherpad for this topic as well03:14
NamrataOkay03:14
yanyanhufor discussion and tracking03:14
mkraiAgree yanyanhu03:14
Wenzhi+103:14
mkraiYes it will be bit complex as compared to ironic driver03:15
mkrai#action mkrai to create an etherpad for nova-integration03:15
yanyanhuyes, not that straightfoward I think03:15
*** ajmiller has quit IRC03:16
sudiptoIf i may - what does the nova-integration actually mean? Creating a compute driver for zun?03:16
*** ajmiller has joined #openstack-meeting03:16
*** piet has quit IRC03:16
mkraisudipto, yes03:16
NamrataYes03:16
*** jamesdenton has joined #openstack-meeting03:17
sudiptoand ... how does it have similarity to ironic? In terms of a 2 layered scheduler?03:17
mkraisudipto, yes that's what I am trying to highlight that it would be complex as Zun will also have its own scheduler03:17
sudiptoalso, how is it going to be different from the nova-docker driver?03:17
mkrainova-docker driver has very limited functionality I guess03:18
mkraiAnd not even maintained well03:18
sudiptobut has an overlap to this...you probably know why it had issues...03:18
*** treaki_ has joined #openstack-meeting03:18
sudiptothat is w.r.t not integrating well with nova.03:18
mkraiI agree to it to some extent as containers and vms are not same03:19
sudiptoyeah and i think the same debate is going to come up again with this?03:19
mkraiBut here we just aim to provide same set of nova APIs for containers03:20
mkraiYes certainly03:20
*** shaohe_feng has quit IRC03:20
mkraiNova is good point to sell Zun IMO03:20
sudiptoNova providing same set of APIs for containers was the problem with the nova-docker driver AFAIK.03:20
WenzhiI agree, limited by nova data model, I think nova-zun driver will also be difficult to design03:21
mkraisudipto, ack03:21
*** shaohe_feng has joined #openstack-meeting03:21
*** amotoki has joined #openstack-meeting03:21
*** treaki__ has quit IRC03:22
mkraiIt is quite difficult to take out common APIs between VMs and containers, but still we have few that satifies both03:22
*** itzdilip has joined #openstack-meeting03:23
sudiptoI tend to think that the Nova workflow could actually cater to something like an isolated/secure container workflow, that has overlaps with a VM lifecycle.03:23
mkraiAnd IMO it's worth spending some effort to consider this03:23
mkraisudipto, Sorry I don't get it. Could you please explain?03:24
sudiptomkrai, going with a container API that fits the VM APIs is fundamentally wrong and it would lead to the same fate as nova-dockers at least that's what i feel. However, if you imagine something like a container in a VM workflow - that probably fits the APIs of a Virtual Machine.03:25
*** amotoki has quit IRC03:26
*** sambhare has joined #openstack-meeting03:26
*** spzala has joined #openstack-meeting03:26
sudiptohowever with that said - we are free to try and still do whatever we think is the best :)03:26
mkraisudipto, What I understand here is the host where we are running our containers. Right?03:26
*** ajmiller has quit IRC03:26
sudiptomkrai, didn't understand your last statement?03:27
*** ajmiller has joined #openstack-meeting03:27
*** yamamoto has quit IRC03:27
*** yamamoto has joined #openstack-meeting03:27
*** amotoki has joined #openstack-meeting03:27
*** shashank_hegde has joined #openstack-meeting03:27
mkraiOk the point you stated is one where we are running containers inside vm or not inside vm03:27
*** yamahata has joined #openstack-meeting03:28
sudiptowe have stated that we want to support hyper like workflows into openstack - i meant that use case could fit into a nova integration per say - but in general running containers with Nova APIs - sounds similar to nova-docker.03:28
*** tochi has quit IRC03:28
sudiptoI would like to hear everyone's thought around it as well, who knows - i might be short sighted here :)03:29
*** armax has quit IRC03:29
mkraiyes I agree that is similar to nova-docker but with more features03:29
mkraiMore container runtime tools and also COEs03:29
mkraiYes I want to ask team here03:30
shubhamsYou are right sudipto , but anyway from an instance's perspective (baremetal/vm/container) , we need to use nova only, right?03:30
*** Suyash has quit IRC03:30
mkraiDo they feel this work is worth spending some effort?03:30
*** yinwei_computer has quit IRC03:30
*** shaohe_feng has quit IRC03:30
sudiptoshubhams, you mean provision the instance via nova and then have containers run inside them via zun?03:30
shubhamsnope, I mean everything ( a vm/bm or container ) should be provisioned by nova03:31
*** spzala has quit IRC03:31
mkraishubhams, Yes we aim to do so03:31
mkraiBut it is not hard and fast03:31
sudiptoshubhams, why?03:31
sudiptoare you referring to the host management being done by nova?03:31
shubhamsYes sudipto03:32
*** markvoelker has joined #openstack-meeting03:32
mkraiOk let's take this discussion in Open discussion03:32
sudiptoalrite.03:32
shubhamsare we bound to use nova for all this ?03:32
mkraiThanks03:32
*** Daisy has quit IRC03:32
mkrai#topic Re-consider RabbitMQ. How about using key/value store (i.e. etcd) for passing messages03:32
*** openstack changes topic to "Re-consider RabbitMQ. How about using key/value store (i.e. etcd) for passing messages (Meeting topic: zun)"03:32
mkraiIn our last meeting, we discussed about managing state of containers in Zun03:33
*** Daisy has joined #openstack-meeting03:33
mkraiWe talked about etcd which is distributed key-value store03:33
*** ronghui has quit IRC03:33
mkraiHowever we also discussed few more options like rabbitmq and taskflow.03:33
mkraiI want to know team's opinion on it.03:33
mkraiI gues yuanying is not present today03:33
mkrais/gues/guess/03:33
Wenzhifor passing messages, I prefer rabbitmq03:34
*** sindhu has quit IRC03:34
sudiptoI think we need a PoC for etcd03:34
mkrai+1 sudipto03:34
WenzhiI think etcd is not designed for this(message exchange)03:34
mkraiI strongly feel so03:34
mkraiYes it is meant to store distributed data03:34
Wenzhiyes03:34
mkraiAnyone is interested in doing this work?03:35
*** shaohe_feng has joined #openstack-meeting03:35
*** markvoelker_ has joined #openstack-meeting03:35
shubhamsok .. I will take this up03:36
shubhamsalthouugh its new for me .. but will see how to do that03:36
mkraiThanks shubhams03:36
mkraiAppreciate it03:36
mkraiI feel a bp is also needed for it03:36
*** Daisy has quit IRC03:37
mkrai#action shubhams to create a bp for managing state of containers03:37
*** shashank_hegde has quit IRC03:37
itzdilip<mkrai> <shubhams> i like to join too in that03:37
mkraiThanks itzdilip03:37
mkraiYou can work together with shubhams03:37
*** shashank_hegde has joined #openstack-meeting03:37
mkraiPlease feel free to ping me or hongbin anytime on this03:38
shubhamsthanks itzdilip03:38
*** markvoelker has quit IRC03:38
mkraiDo anyone has something to add?03:38
itzdilip<shubhams> <mkrai> sure I will03:38
mkraiAlso yuanying is good point of contact for same03:39
shubhamsmkrai, ok we will connect with yuanying03:39
mkraiThanks shubhams03:40
mkraiShall we advance topic?03:40
shubhamsyep03:40
mkrai#topic Open Discussion03:40
*** openstack changes topic to "Open Discussion (Meeting topic: zun)"03:40
*** rderose has quit IRC03:40
*** shaohe_feng has quit IRC03:40
mkraisudipto, We can continue the discussion03:41
sudiptomkrai, well i guess i was trying to understand shubhams point on 'why nova is needed'03:41
*** shaohe_feng has joined #openstack-meeting03:42
mkraishubhams, Would you like to answer?03:42
shubhamsMy point on nova integration was : Before going ahead , we should first note it down (may be on etherpad) that do we really want to work around "Nova" or we want a separate solution .03:42
shubhamss/work around/work around with nova03:43
mkraishubhams, Separate solution for us is Zun itseld03:43
*** chenpengzi has joined #openstack-meeting03:43
sudiptoZun should be designed as independently as possible IMHO03:43
*** karthikp_ has quit IRC03:43
*** chenpengzi has left #openstack-meeting03:43
mkraiYes sudipto that we all agree03:43
sudiptook - i don't mean to derail the approach...please go ahead if you think it's needed :)03:44
sudiptoand it's something that can eventually fly.03:44
sudiptoI am sure there are probably strong reasons behind doing it.03:44
mkraiThis bp just aims to provision containers from nova as we provision baremetal03:44
mkraiAnd that shouldn't impact Zun design at all03:45
*** ronghui has joined #openstack-meeting03:45
sudiptobaremetal provisioning forms a pre-requisite to VM provisioning, i am not sure that's the case here.03:45
*** ijw has joined #openstack-meeting03:45
*** markvoelker has joined #openstack-meeting03:46
*** JRobinson__ is now known as JRobinson__afk03:46
sudiptoif you ask me, i feel baremetal could be made as a pre-req for container provisioning - but that means an ironic integration to zun03:46
mkraiThat is the host where we run our container i.e host management03:47
mkraiAnd we are not targeting host management in this bp03:47
mkraiExactly the same way nova-docker does03:47
shubhamsYep .. so let host management be the responsibility of nova and container management is left for Zun , right?03:48
mkraishubhams, agree with later part03:48
*** dmorita has joined #openstack-meeting03:48
mkraiBut host management is itself a huge topic in itself03:48
sudiptothink of it like this - if host management is done by nova or something else - why make zun worry about it?03:49
*** amotoki has quit IRC03:49
shubhamsSudipto, agree03:49
*** markvoelker_ has quit IRC03:49
*** epico has joined #openstack-meeting03:49
mkraiHost management can be independent of Zun. Operators can manage host or we might in future want to manage it ourself03:49
*** ijw has quit IRC03:50
*** Namrata_ has joined #openstack-meeting03:50
*** Namrata has quit IRC03:50
*** shashank_hegde has quit IRC03:50
mkraiIt can be either we already have pool of host or we provision one at runtime03:50
*** jckasper has joined #openstack-meeting03:50
mkraiThere are many options that we can think of03:51
*** shaohe_feng has quit IRC03:51
*** mtanino has joined #openstack-meeting03:51
mkraiTeam I want to record an action, whether we want to spend effort on this task?03:52
shubhamsI may be wrong but my whole point is : if we are creating something relevent to what already exists (ex: nova-docker) then we should we have clear boundaries and reasons that why we need the solution that we want to create.03:52
mkrai+1 shubhams03:52
shubhamsand so far I am not sure why we need this03:52
*** _sarob has joined #openstack-meeting03:52
*** spzala has joined #openstack-meeting03:52
*** sarob has quit IRC03:53
mkrai#action madhuri Add points why we want to integrate with nova on BP whiteboard03:53
mkraiTeam feel free to add any points that you have in mind03:53
*** anilvenkata has joined #openstack-meeting03:53
shubhamsYes sure03:53
mkrai#link https://blueprints.launchpad.net/zun/+spec/nova-integration03:54
*** shaohe_feng has joined #openstack-meeting03:54
mkraiAny more discussion do you want to have?03:55
*** jckasper has quit IRC03:55
mkraiIf not, I will end meeting early03:55
shubhamsseems ok to me03:55
mkraiThanks everyone for joining03:55
Wenzhithanks all03:55
Namrata_Thanks03:55
mkrai#endmeeting03:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"03:56
openstackMeeting ended Tue Jul 12 03:56:02 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:56
shubhamsThanks03:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-07-12-03.00.html03:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-07-12-03.00.txt03:56
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-07-12-03.00.log.html03:56
*** gouthamr_ has joined #openstack-meeting03:56
*** spzala has quit IRC03:57
*** shubhams has left #openstack-meeting03:57
*** julim has quit IRC03:58
*** amotoki has joined #openstack-meeting03:59
*** Namrata_ has quit IRC04:00
*** shashank_hegde has joined #openstack-meeting04:00
*** jamesdenton has quit IRC04:01
*** tochi has joined #openstack-meeting04:01
*** shaohe_feng has quit IRC04:01
*** links has joined #openstack-meeting04:02
*** shaohe_feng has joined #openstack-meeting04:02
*** kei__ has joined #openstack-meeting04:02
*** azbiswas has joined #openstack-meeting04:02
*** oferby_ has joined #openstack-meeting04:03
*** kei_ has quit IRC04:05
*** ajmiller has quit IRC04:05
*** ajmiller has joined #openstack-meeting04:05
*** ljxiash has quit IRC04:05
*** ljxiash has joined #openstack-meeting04:06
*** klkumar has quit IRC04:06
*** klkumar has joined #openstack-meeting04:09
*** shaohe_feng has quit IRC04:11
*** shaohe_feng has joined #openstack-meeting04:12
*** Ravikiran_K has quit IRC04:13
*** Sukhdev has joined #openstack-meeting04:14
*** ljxiash has quit IRC04:15
*** shashank_hegde has quit IRC04:16
*** vivek___ has quit IRC04:16
*** gongysh has quit IRC04:21
*** shaohe_feng has quit IRC04:21
*** garthb has joined #openstack-meeting04:22
*** shaohe_feng has joined #openstack-meeting04:22
*** dmorita has quit IRC04:25
*** adisky has joined #openstack-meeting04:25
*** davidlenwell has quit IRC04:28
*** dimtruck is now known as zz_dimtruck04:29
*** shaohe_feng has quit IRC04:32
*** mkrai has quit IRC04:32
*** shaohe_feng has joined #openstack-meeting04:33
*** JRobinson__afk is now known as JRobinson__04:36
*** coolsvap has joined #openstack-meeting04:37
*** davidlenwell has joined #openstack-meeting04:38
*** ljxiash has joined #openstack-meeting04:41
*** gouthamr_ has quit IRC04:42
*** shaohe_feng has quit IRC04:42
*** _sarob has quit IRC04:46
*** gcb has joined #openstack-meeting04:46
*** sarob has joined #openstack-meeting04:46
*** shaohe_feng has joined #openstack-meeting04:47
*** mkrai has joined #openstack-meeting04:47
*** yanyanhu has left #openstack-meeting04:47
*** sudipto has quit IRC04:49
*** unicell has joined #openstack-meeting04:50
*** shaohe_feng has quit IRC04:52
*** shaohe_feng has joined #openstack-meeting04:53
*** xyang1 has quit IRC04:58
*** aranjan has quit IRC04:59
*** Galitz has joined #openstack-meeting04:59
*** elopez_ has joined #openstack-meeting04:59
*** shashank_hegde has joined #openstack-meeting04:59
*** aranjan has joined #openstack-meeting04:59
*** d0ugal has quit IRC05:01
*** fawadkhaliq has joined #openstack-meeting05:01
*** Guest9709 has quit IRC05:01
*** sridharg has joined #openstack-meeting05:02
*** shaohe_feng has quit IRC05:02
*** shaohe_feng has joined #openstack-meeting05:03
*** aranjan has quit IRC05:04
*** flwang1 has quit IRC05:04
*** shashank_hegde has quit IRC05:04
*** Daisy has joined #openstack-meeting05:05
*** toddjohn has joined #openstack-meeting05:06
*** Daisy has quit IRC05:07
*** irenab has joined #openstack-meeting05:07
*** unicell1 has joined #openstack-meeting05:10
*** unicell has quit IRC05:10
*** toddjohn has quit IRC05:10
*** Daisy has joined #openstack-meeting05:10
*** zzxwill has quit IRC05:11
*** shashank_hegde has joined #openstack-meeting05:12
*** shaohe_feng has quit IRC05:13
*** zzxwill has joined #openstack-meeting05:13
*** shaohe_feng has joined #openstack-meeting05:14
*** oferby_ has quit IRC05:15
*** markvoelker_ has joined #openstack-meeting05:16
*** jlwhite has quit IRC05:16
*** luzC has quit IRC05:16
*** lcastell has quit IRC05:16
*** zeih has quit IRC05:18
*** david-lyle has joined #openstack-meeting05:18
*** markvoelker has quit IRC05:19
*** lcastell has joined #openstack-meeting05:19
*** luzC has joined #openstack-meeting05:19
*** sambhare has quit IRC05:20
*** ajmiller has quit IRC05:21
*** jlwhite has joined #openstack-meeting05:22
*** ajmiller has joined #openstack-meeting05:22
*** Kevin_Zheng has quit IRC05:23
*** shaohe_feng has quit IRC05:23
*** garthb has quit IRC05:23
*** sandanar_ has joined #openstack-meeting05:24
*** sandanar has joined #openstack-meeting05:24
*** nkrinner_afk is now known as nkrinner05:24
*** Ed___ has joined #openstack-meeting05:25
*** sdake_ has joined #openstack-meeting05:25
*** dmorita has joined #openstack-meeting05:25
*** breton has quit IRC05:26
*** shaohe_feng has joined #openstack-meeting05:26
*** jlwhite has quit IRC05:26
*** Daisy has quit IRC05:29
*** Daisy has joined #openstack-meeting05:29
*** dmorita has quit IRC05:30
*** Daisy_ has joined #openstack-meeting05:31
*** mickeys has joined #openstack-meeting05:31
*** Daisy has quit IRC05:31
*** azbiswas has quit IRC05:32
*** Daisy_ has quit IRC05:33
*** shaohe_feng has quit IRC05:33
*** mickeys has quit IRC05:33
*** Daisy has joined #openstack-meeting05:34
*** mickeys has joined #openstack-meeting05:34
*** shaohe_feng has joined #openstack-meeting05:34
*** lpetrut has joined #openstack-meeting05:35
*** obondarev has joined #openstack-meeting05:35
*** Ed___ has quit IRC05:37
*** mickeys has quit IRC05:38
*** jlwhite has joined #openstack-meeting05:40
*** sudipto has joined #openstack-meeting05:40
*** esberglu has quit IRC05:41
*** breton has joined #openstack-meeting05:41
*** klkumar has quit IRC05:43
*** shaohe_feng has quit IRC05:44
*** shaohe_feng has joined #openstack-meeting05:44
*** obondarev has quit IRC05:44
*** arif-ali has quit IRC05:45
*** markvoelker_ has quit IRC05:45
*** coolsvap has quit IRC05:46
*** breton has quit IRC05:46
*** breton has joined #openstack-meeting05:47
*** jlwhite has quit IRC05:50
*** hashar has joined #openstack-meeting05:52
*** Sukhdev has quit IRC05:53
*** shaohe_feng has quit IRC05:54
*** breton has quit IRC05:54
*** Ravikiran_K has joined #openstack-meeting05:54
*** breton has joined #openstack-meeting05:54
*** lcastell has quit IRC05:55
*** shaohe_feng has joined #openstack-meeting05:55
*** sarob has quit IRC05:55
*** lcastell has joined #openstack-meeting05:57
*** Ed___ has joined #openstack-meeting05:57
*** fawadkhaliq has quit IRC05:58
*** rcernin has joined #openstack-meeting05:58
*** obondarev has joined #openstack-meeting05:59
*** Rockyg has quit IRC05:59
*** azbiswas has joined #openstack-meeting06:02
*** luzC has quit IRC06:02
*** Ed___ has quit IRC06:02
*** gongysh has joined #openstack-meeting06:03
*** amotoki has quit IRC06:03
*** d0ugal has joined #openstack-meeting06:04
*** shaohe_feng has quit IRC06:04
*** shaohe_feng has joined #openstack-meeting06:05
*** JRobinson__ has quit IRC06:06
*** lcastell has quit IRC06:09
*** manikanta_tadi has joined #openstack-meeting06:10
*** manikanta_ has joined #openstack-meeting06:10
*** jlwhite has joined #openstack-meeting06:12
*** lennyb has quit IRC06:12
*** klkumar has joined #openstack-meeting06:13
*** yinwei_computer has joined #openstack-meeting06:14
*** breton has quit IRC06:14
*** shaohe_feng has quit IRC06:14
*** rajinir has quit IRC06:15
*** shaohe_feng has joined #openstack-meeting06:15
*** roxanaghe has joined #openstack-meeting06:16
*** amotoki has joined #openstack-meeting06:17
*** luzC has joined #openstack-meeting06:17
*** yinwei_computer has quit IRC06:17
*** obondarev has quit IRC06:18
*** lennyb has joined #openstack-meeting06:20
*** breton has joined #openstack-meeting06:21
*** roxanaghe has quit IRC06:21
*** Ed___ has joined #openstack-meeting06:21
*** Daisy_ has joined #openstack-meeting06:23
*** mtanino has quit IRC06:24
*** lcastell has joined #openstack-meeting06:24
*** shaohe_feng has quit IRC06:25
*** shaohe_feng has joined #openstack-meeting06:25
*** obondarev has joined #openstack-meeting06:25
*** dslevin has joined #openstack-meeting06:26
*** Ed___ has quit IRC06:26
*** breton has quit IRC06:26
*** Daisy has quit IRC06:26
*** luzC has quit IRC06:27
*** jlwhite has quit IRC06:28
*** obondarev has quit IRC06:28
*** breton has joined #openstack-meeting06:28
*** Fdaisuke has quit IRC06:29
*** jlwhite has joined #openstack-meeting06:30
*** mkrai has quit IRC06:31
*** luzC has joined #openstack-meeting06:31
*** dmacpher has joined #openstack-meeting06:33
*** hoangcx has joined #openstack-meeting06:34
*** sheel has joined #openstack-meeting06:34
*** shaohe_feng has quit IRC06:35
*** shaohe_feng has joined #openstack-meeting06:35
*** lcastell has quit IRC06:36
*** jlwhite has quit IRC06:36
*** nadya has joined #openstack-meeting06:40
*** jlwhite has joined #openstack-meeting06:42
*** d0ugal has quit IRC06:43
*** lcastell has joined #openstack-meeting06:43
*** luzC has quit IRC06:44
*** shaohe_feng has quit IRC06:45
*** shaohe_feng has joined #openstack-meeting06:45
*** nadya has quit IRC06:45
*** csomerville has quit IRC06:46
*** zeih has joined #openstack-meeting06:46
*** Fdaisuke has joined #openstack-meeting06:47
*** sdake_ has quit IRC06:49
*** nmagnezi has joined #openstack-meeting06:50
*** andreas_s has joined #openstack-meeting06:50
*** mkrai has joined #openstack-meeting06:51
*** luzC has joined #openstack-meeting06:51
*** amotoki has quit IRC06:52
*** zzxwill has quit IRC06:54
*** azbiswas has quit IRC06:54
*** azbiswas has joined #openstack-meeting06:55
*** shaohe_feng has quit IRC06:55
*** fawadkhaliq has joined #openstack-meeting06:56
*** shaohe_feng has joined #openstack-meeting06:56
*** azbiswas has quit IRC06:56
*** dmacpher has quit IRC06:58
*** fawadkhaliq has quit IRC06:59
*** yinwei_computer has joined #openstack-meeting06:59
*** fawadkhaliq has joined #openstack-meeting06:59
*** andymaier has joined #openstack-meeting06:59
*** tesseract- has joined #openstack-meeting07:00
*** pcaruana has joined #openstack-meeting07:00
*** kei has joined #openstack-meeting07:01
*** oshidoshi has joined #openstack-meeting07:01
*** kei__ has quit IRC07:02
*** azbiswas has joined #openstack-meeting07:03
*** mkrai has quit IRC07:03
*** liusheng has joined #openstack-meeting07:04
*** shaohe_feng has quit IRC07:06
*** ociuhandu has quit IRC07:06
*** lpetrut has quit IRC07:06
*** shaohe_feng has joined #openstack-meeting07:06
*** toddjohn has joined #openstack-meeting07:07
*** efried has quit IRC07:08
*** adiantum has joined #openstack-meeting07:10
*** akuznetsov has joined #openstack-meeting07:11
*** toddjohn has quit IRC07:12
*** oshidoshi has quit IRC07:13
*** amotoki has joined #openstack-meeting07:14
*** shaohe_feng has quit IRC07:16
*** karthikp_ has joined #openstack-meeting07:16
*** shaohe_feng has joined #openstack-meeting07:16
*** azbiswas has quit IRC07:17
*** lpetrut has joined #openstack-meeting07:17
*** amotoki has quit IRC07:19
*** efried has joined #openstack-meeting07:19
*** mkrai has joined #openstack-meeting07:19
*** karthikp_ has quit IRC07:20
*** david-lyle has quit IRC07:22
*** shaohe_feng has quit IRC07:26
*** obondarev has joined #openstack-meeting07:26
*** shaohe_feng has joined #openstack-meeting07:26
*** breton has quit IRC07:27
*** dmorita has joined #openstack-meeting07:28
*** Daisy has joined #openstack-meeting07:30
*** ronghui has quit IRC07:33
*** dmorita has quit IRC07:33
*** Daisy_ has quit IRC07:33
*** iyamahat has joined #openstack-meeting07:34
*** efried has quit IRC07:35
*** Daisy has quit IRC07:36
*** Daisy has joined #openstack-meeting07:36
*** shaohe_feng has quit IRC07:36
*** shaohe_feng has joined #openstack-meeting07:37
*** oshidoshi has joined #openstack-meeting07:39
*** breton has joined #openstack-meeting07:41
*** jlanoux has joined #openstack-meeting07:43
*** ronghui has joined #openstack-meeting07:45
*** zhurong has quit IRC07:46
*** eezhova has joined #openstack-meeting07:46
*** dbite has quit IRC07:46
*** shaohe_feng has quit IRC07:47
*** zhurong has joined #openstack-meeting07:47
*** shaohe_feng has joined #openstack-meeting07:47
*** breton has quit IRC07:49
*** breton has joined #openstack-meeting07:50
*** efried has joined #openstack-meeting07:51
*** dfflanders has quit IRC07:52
*** jckasper has joined #openstack-meeting07:52
*** mikelk has joined #openstack-meeting07:54
*** breton has quit IRC07:55
*** lpetrut has quit IRC07:55
*** jrist has joined #openstack-meeting07:55
*** breton has joined #openstack-meeting07:56
*** jckasper has quit IRC07:56
*** zeih has quit IRC07:56
*** shaohe_feng has quit IRC07:57
*** shaohe_feng has joined #openstack-meeting07:57
*** mrmartin has joined #openstack-meeting07:58
*** coolsvap has joined #openstack-meeting07:59
*** fawadkhaliq has quit IRC07:59
*** adiantum has quit IRC08:00
*** dtrainor has joined #openstack-meeting08:00
*** zeih has joined #openstack-meeting08:01
*** breton has quit IRC08:01
*** fawadkhaliq has joined #openstack-meeting08:01
*** breton has joined #openstack-meeting08:02
*** asettle has joined #openstack-meeting08:04
*** yinwei_computer has quit IRC08:05
*** fawadkhaliq has quit IRC08:05
*** dbecker has joined #openstack-meeting08:06
*** breton has quit IRC08:07
*** shaohe_feng has quit IRC08:07
*** shaohe_feng has joined #openstack-meeting08:08
*** toddjohn has joined #openstack-meeting08:08
*** amotoki has joined #openstack-meeting08:09
*** dtrainor has quit IRC08:09
*** jlanoux has quit IRC08:13
*** jlanoux has joined #openstack-meeting08:13
*** amotoki has quit IRC08:13
*** jtomasek_ has joined #openstack-meeting08:13
*** iyamahat has quit IRC08:14
*** toddjohn has quit IRC08:14
*** klkumar has quit IRC08:17
*** gongysh has quit IRC08:17
*** shaohe_feng has quit IRC08:17
*** azbiswas has joined #openstack-meeting08:17
*** shaohe_feng has joined #openstack-meeting08:18
*** Na3iL has joined #openstack-meeting08:19
*** coolsvap_ has joined #openstack-meeting08:19
*** klkumar has joined #openstack-meeting08:19
*** iyamahat has joined #openstack-meeting08:21
*** azbiswas has quit IRC08:22
*** coolsvap has quit IRC08:22
*** oshidoshi has quit IRC08:23
*** zeih has quit IRC08:24
*** shihanzhang has quit IRC08:25
*** shihanzhang has joined #openstack-meeting08:26
*** aranjan has joined #openstack-meeting08:26
*** zeih has joined #openstack-meeting08:26
*** shashank_hegde has quit IRC08:27
*** yassine has joined #openstack-meeting08:27
*** shaohe_feng has quit IRC08:28
*** yassine is now known as Guest3902908:28
*** shaohe_feng has joined #openstack-meeting08:28
*** oshidoshi has joined #openstack-meeting08:28
*** akuznetsov has quit IRC08:28
*** sridharg has quit IRC08:31
*** anilvenkata has quit IRC08:33
*** zhhuabj has quit IRC08:34
*** JRobinson__ has joined #openstack-meeting08:35
*** mickeys has joined #openstack-meeting08:35
*** nadya has joined #openstack-meeting08:36
*** mickeys has quit IRC08:36
*** aranjan has quit IRC08:36
*** mickeys has joined #openstack-meeting08:36
*** aranjan has joined #openstack-meeting08:37
*** ajmiller has quit IRC08:37
*** sshnaidm|afk is now known as sshnaidm08:38
*** ajmiller has joined #openstack-meeting08:38
*** shaohe_feng has quit IRC08:38
*** shaohe_feng has joined #openstack-meeting08:38
*** egallen has joined #openstack-meeting08:38
*** obondarev has quit IRC08:39
*** Fdaisuke has quit IRC08:39
*** mickeys has quit IRC08:40
*** obondarev has joined #openstack-meeting08:41
*** akuznetsov has joined #openstack-meeting08:43
*** Ed___ has joined #openstack-meeting08:43
*** Daisy_ has joined #openstack-meeting08:43
*** anilvenkata has joined #openstack-meeting08:44
*** Na3iL has quit IRC08:45
*** coolsvap_ has quit IRC08:46
*** zhhuabj has joined #openstack-meeting08:47
*** Ed___ has quit IRC08:48
*** shaohe_feng has quit IRC08:48
*** Daisy has quit IRC08:48
*** shaohe_feng has joined #openstack-meeting08:49
*** e0ne has joined #openstack-meeting08:51
*** mkrai has quit IRC08:51
*** iyamahat has quit IRC08:53
*** electrofelix has joined #openstack-meeting08:56
*** obondarev has quit IRC08:56
*** shaohe_feng has quit IRC08:58
*** shaohe_feng has joined #openstack-meeting08:59
*** flwang1 has joined #openstack-meeting08:59
*** flwang1 has quit IRC08:59
*** JRobinson__ has quit IRC09:00
*** aranjan has quit IRC09:02
*** oferby has quit IRC09:02
*** yamahata has quit IRC09:02
*** fawadkhaliq has joined #openstack-meeting09:02
*** oferby has joined #openstack-meeting09:02
*** aranjan has joined #openstack-meeting09:02
*** amotoki has joined #openstack-meeting09:03
*** mkrai has joined #openstack-meeting09:04
*** zhonghua has quit IRC09:05
*** fawadkhaliq has quit IRC09:06
*** aranjan has quit IRC09:06
*** zhonghua-lee has joined #openstack-meeting09:07
*** xarses_ has joined #openstack-meeting09:07
*** claudiub has joined #openstack-meeting09:07
*** xarses has quit IRC09:07
*** xarses_ has quit IRC09:07
*** gongysh has joined #openstack-meeting09:07
*** xarses_ has joined #openstack-meeting09:08
*** tochi has quit IRC09:08
*** shaohe_feng has quit IRC09:09
*** raildo-afk has quit IRC09:09
*** amotoki has quit IRC09:09
*** shaohe_feng has joined #openstack-meeting09:09
*** Daisy_ has quit IRC09:10
*** Daisy has joined #openstack-meeting09:11
*** Daisy has quit IRC09:15
*** lpetrut has joined #openstack-meeting09:17
*** shaohe_feng has quit IRC09:19
*** neiljerram has joined #openstack-meeting09:19
*** shaohe_feng has joined #openstack-meeting09:20
*** mbound has joined #openstack-meeting09:21
*** kaminohana has quit IRC09:21
*** yamahata has joined #openstack-meeting09:22
*** fawadkhaliq has joined #openstack-meeting09:24
*** Ed___ has joined #openstack-meeting09:25
*** ljxiash has quit IRC09:27
*** shaohe_feng has quit IRC09:29
*** Ed___ has quit IRC09:30
*** dmorita has joined #openstack-meeting09:31
*** shaohe_feng has joined #openstack-meeting09:32
*** dtrainor has joined #openstack-meeting09:32
*** zeih has quit IRC09:36
*** dmorita has quit IRC09:36
*** shaohe_feng has quit IRC09:39
*** shaohe_feng has joined #openstack-meeting09:40
*** Ed___ has joined #openstack-meeting09:43
*** toscalix has joined #openstack-meeting09:45
*** Ed___ has quit IRC09:48
*** shaohe_feng has quit IRC09:50
*** gcb has quit IRC09:50
*** shaohe_feng has joined #openstack-meeting09:50
*** gcb has joined #openstack-meeting09:50
*** shu-mutou is now known as shu-mutou-AFK09:51
*** gongysh has quit IRC09:53
*** manikanta_ has quit IRC09:54
*** manikanta_tadi has quit IRC09:54
*** beekhof_mb has quit IRC09:55
*** brunograz has joined #openstack-meeting09:55
*** mbound has quit IRC09:56
*** amotoki has joined #openstack-meeting09:57
*** lblanchard has joined #openstack-meeting09:58
*** beekhof_mb has joined #openstack-meeting09:58
*** ajmiller has quit IRC09:59
*** ajmiller has joined #openstack-meeting09:59
*** shaohe_feng has quit IRC10:00
*** flwang1 has joined #openstack-meeting10:01
*** shaohe_feng has joined #openstack-meeting10:02
*** amotoki has quit IRC10:02
*** d0ugal has joined #openstack-meeting10:02
*** yamahata has quit IRC10:03
*** Ed___ has joined #openstack-meeting10:04
*** oferby has quit IRC10:04
*** oferby has joined #openstack-meeting10:04
*** obondarev has joined #openstack-meeting10:05
*** sindhu has joined #openstack-meeting10:05
*** manikanta_tadi has joined #openstack-meeting10:07
*** manikanta_ has joined #openstack-meeting10:07
*** eezhova has quit IRC10:09
*** Ed___ has quit IRC10:09
*** akuznetsov has quit IRC10:09
*** shaohe_feng has quit IRC10:10
*** shaohe_feng has joined #openstack-meeting10:10
*** toddjohn has joined #openstack-meeting10:11
*** eezhova has joined #openstack-meeting10:12
*** hoangcx has quit IRC10:12
*** egallen has quit IRC10:12
*** zhurong has quit IRC10:13
*** Julien-zte has quit IRC10:13
*** toscalix has quit IRC10:14
*** sindhu has quit IRC10:14
*** toddjohn has quit IRC10:15
*** breton has joined #openstack-meeting10:16
*** egallen has joined #openstack-meeting10:20
*** shaohe_feng has quit IRC10:20
*** shaohe_feng has joined #openstack-meeting10:21
*** eezhova has quit IRC10:21
*** sindhu has joined #openstack-meeting10:23
*** Julien-zte has joined #openstack-meeting10:24
*** jlanoux_ has joined #openstack-meeting10:29
*** zeih has joined #openstack-meeting10:30
*** jlanoux has quit IRC10:30
*** shaohe_feng has quit IRC10:31
*** shaohe_feng has joined #openstack-meeting10:31
*** iceyao has quit IRC10:34
*** iceyao has joined #openstack-meeting10:35
*** elopez has joined #openstack-meeting10:38
*** anilvenkata has quit IRC10:38
*** sindhu has quit IRC10:39
*** elopez is now known as Guest5377010:39
*** iceyao has quit IRC10:39
*** elopez_ has quit IRC10:39
*** yuval has joined #openstack-meeting10:40
*** rossella_s has quit IRC10:40
*** rossella_s has joined #openstack-meeting10:40
*** shaohe_feng has quit IRC10:41
*** shaohe_feng has joined #openstack-meeting10:41
*** jlanoux_ has quit IRC10:44
*** sindhu has joined #openstack-meeting10:44
*** mkrai has quit IRC10:44
*** jlanoux has joined #openstack-meeting10:44
*** Ed___ has joined #openstack-meeting10:46
*** xiangxinyong has joined #openstack-meeting10:46
*** sindhu has quit IRC10:47
*** akuznetsov has joined #openstack-meeting10:47
*** rodrigods has quit IRC10:48
*** rodrigods has joined #openstack-meeting10:48
*** arif-ali has joined #openstack-meeting10:50
*** sridharg has joined #openstack-meeting10:50
*** Ed___ has quit IRC10:50
*** shaohe_feng has quit IRC10:51
*** shaohe_feng has joined #openstack-meeting10:51
*** egallen has left #openstack-meeting10:54
*** eezhova has joined #openstack-meeting10:56
*** obondarev has quit IRC11:00
*** yinwei_computer has joined #openstack-meeting11:00
*** epico has quit IRC11:00
*** shaohe_feng has quit IRC11:01
*** shaohe_feng has joined #openstack-meeting11:02
*** akuznetsov has quit IRC11:02
*** julim has joined #openstack-meeting11:05
*** elopez_ has joined #openstack-meeting11:06
*** sdake has joined #openstack-meeting11:07
*** sdake_ has joined #openstack-meeting11:08
*** Guest53770 has quit IRC11:09
*** akuznetsov has joined #openstack-meeting11:10
*** zeih has quit IRC11:11
*** shaohe_feng has quit IRC11:12
*** tellesnobrega is now known as tellesnobrega_af11:12
*** shaohe_feng has joined #openstack-meeting11:12
*** sdake has quit IRC11:13
*** mrmartin has quit IRC11:15
*** AndroUser has joined #openstack-meeting11:20
*** tpsilva has joined #openstack-meeting11:20
*** shaohe_feng has quit IRC11:22
*** julim has quit IRC11:23
*** Ed___ has joined #openstack-meeting11:23
*** amotoki has joined #openstack-meeting11:25
*** shaohe_feng has joined #openstack-meeting11:26
*** Ed___ has quit IRC11:27
*** shaohe_feng has quit IRC11:32
*** ronghui has quit IRC11:32
*** shaohe_feng has joined #openstack-meeting11:33
*** AndroUser has quit IRC11:33
*** dmorita has joined #openstack-meeting11:33
*** dmorita has quit IRC11:38
*** obondarev has joined #openstack-meeting11:41
*** thorst has joined #openstack-meeting11:41
*** numans has joined #openstack-meeting11:42
*** kaminohana has joined #openstack-meeting11:42
*** weshay has joined #openstack-meeting11:42
*** irenab has quit IRC11:42
*** shaohe_feng has quit IRC11:42
*** irenab has joined #openstack-meeting11:42
*** yuval has quit IRC11:43
*** shaohe_feng has joined #openstack-meeting11:43
*** asettle has quit IRC11:44
*** sambetts|afk is now known as sambetts11:44
*** ronghui has joined #openstack-meeting11:45
*** sudipto has quit IRC11:47
*** pc_m has left #openstack-meeting11:48
*** dmacpher has joined #openstack-meeting11:49
*** tellesnobrega_af is now known as tellesnobrega11:50
*** fawadkhaliq has quit IRC11:50
*** rfolco has joined #openstack-meeting11:51
*** lblanchard has quit IRC11:52
*** shaohe_feng has quit IRC11:53
*** shaohe_feng has joined #openstack-meeting11:53
*** jckasper has joined #openstack-meeting11:54
*** egallen has joined #openstack-meeting11:54
*** jckasper has quit IRC11:58
*** jokke_ has quit IRC11:59
*** asettle has joined #openstack-meeting11:59
*** mrmartin has joined #openstack-meeting11:59
*** jokke_ has joined #openstack-meeting11:59
*** jjmorman has joined #openstack-meeting12:02
*** shaohe_feng has quit IRC12:03
*** Julien-zte has quit IRC12:03
*** jckasper has joined #openstack-meeting12:03
*** asettle has quit IRC12:04
*** pradk has joined #openstack-meeting12:04
*** Ed___ has joined #openstack-meeting12:05
*** Julien-zte has joined #openstack-meeting12:06
*** yinwei_computer has quit IRC12:07
*** abc has joined #openstack-meeting12:07
*** jckasper has quit IRC12:07
*** abc is now known as Guest7981012:07
*** shaohe_feng has joined #openstack-meeting12:07
*** zeih has joined #openstack-meeting12:08
*** gnuoy has joined #openstack-meeting12:08
*** Ed___ has quit IRC12:10
Guest79810HELP12:12
*** Guest79810 has quit IRC12:12
*** amotoki_ has joined #openstack-meeting12:13
*** amotoki has quit IRC12:13
*** shaohe_feng has quit IRC12:13
*** jungleboyj has joined #openstack-meeting12:13
*** TaylorHuang has joined #openstack-meeting12:14
*** shaohe_feng has joined #openstack-meeting12:14
*** brunograz has left #openstack-meeting12:15
*** xiangxinyong has left #openstack-meeting12:15
*** elopez__ has joined #openstack-meeting12:15
*** iceyao has joined #openstack-meeting12:16
*** ajmiller has quit IRC12:16
*** sdake_ has quit IRC12:16
*** ajmiller has joined #openstack-meeting12:16
*** fawadkhaliq has joined #openstack-meeting12:17
*** elopez_ has quit IRC12:17
*** TaylorH has quit IRC12:17
*** cbader has joined #openstack-meeting12:19
*** azbiswas has joined #openstack-meeting12:19
*** nisha has joined #openstack-meeting12:19
*** nisha is now known as Guest8193612:20
*** asettle has joined #openstack-meeting12:20
*** fawadkhaliq has quit IRC12:20
*** pnavarro has joined #openstack-meeting12:21
*** mbound has joined #openstack-meeting12:21
*** piet has joined #openstack-meeting12:22
*** shaohe_feng has quit IRC12:23
*** azbiswas has quit IRC12:24
*** shaohe_feng has joined #openstack-meeting12:24
*** asettle has quit IRC12:25
*** zeih has quit IRC12:25
*** zhurong has joined #openstack-meeting12:26
*** mbound has quit IRC12:26
*** dprince has joined #openstack-meeting12:27
*** spzala has joined #openstack-meeting12:27
*** zeih has joined #openstack-meeting12:27
*** rbowen has joined #openstack-meeting12:31
*** jrist has quit IRC12:31
*** obondarev has quit IRC12:31
*** spzala has quit IRC12:32
*** Julien-zte has quit IRC12:33
*** shaohe_feng has quit IRC12:34
*** markvoelker has joined #openstack-meeting12:34
*** shaohe_feng has joined #openstack-meeting12:34
*** ihrachys has joined #openstack-meeting12:35
*** zhangshuai has quit IRC12:36
*** ihrachys has quit IRC12:37
*** ihrachys has joined #openstack-meeting12:37
*** gouthamr has joined #openstack-meeting12:38
*** obondarev has joined #openstack-meeting12:38
*** baoli has joined #openstack-meeting12:39
*** piet has quit IRC12:40
*** piet has joined #openstack-meeting12:40
*** weshay is now known as weshay_mtg12:40
*** amotoki_ has quit IRC12:41
*** klkumar has quit IRC12:41
*** shaohe_feng has quit IRC12:44
*** shaohe_feng has joined #openstack-meeting12:44
*** adiantum has joined #openstack-meeting12:44
*** toddjohn has joined #openstack-meeting12:45
*** klkumar has joined #openstack-meeting12:46
*** Ed___ has joined #openstack-meeting12:46
*** baoli_ has joined #openstack-meeting12:47
*** baoli has quit IRC12:49
*** amotoki has joined #openstack-meeting12:50
*** jrist has joined #openstack-meeting12:50
*** Ed___ has quit IRC12:51
*** eezhova has quit IRC12:51
*** ajmiller has quit IRC12:53
*** dmorita has joined #openstack-meeting12:53
*** ajmiller has joined #openstack-meeting12:53
*** hashar_ has joined #openstack-meeting12:53
*** hashar__ has joined #openstack-meeting12:53
*** hashar__ has quit IRC12:53
*** shaohe_feng has quit IRC12:54
*** hashar_ has quit IRC12:54
*** shaohe_feng has joined #openstack-meeting12:55
*** cschulz has joined #openstack-meeting12:56
*** eezhova has joined #openstack-meeting12:56
*** yanyanhu has joined #openstack-meeting12:57
*** adiantum1 has joined #openstack-meeting12:58
*** lixinhui_ has joined #openstack-meeting12:59
*** xuhaiwei_ has joined #openstack-meeting12:59
*** kashyap has left #openstack-meeting12:59
Qiming#startmeeting senlin13:00
openstackMeeting started Tue Jul 12 13:00:07 2016 UTC and is due to finish in 60 minutes.  The chair is Qiming. 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
*** nisha has joined #openstack-meeting13:00
*** zzxwill has joined #openstack-meeting13:00
*** zzxwill_ has joined #openstack-meeting13:00
*** nisha is now known as nisha_13:00
*** xyang1 has joined #openstack-meeting13:00
*** zzxwill has left #openstack-meeting13:00
*** Guest81936 has quit IRC13:00
Qimingevening13:00
zzxwill_Good evening.13:00
cschulzHi13:01
*** elynn has joined #openstack-meeting13:01
xuhaiwei_hi13:01
yanyanhuhi13:01
yanyanhuQiming, I thought you are offline :) my network is really poor, sigh13:01
elynnHi, already started?13:01
Qimingyanyanhu, ok13:01
*** lamt has joined #openstack-meeting13:01
Qiminglet's get started13:01
Qiming#link https://etherpad.openstack.org/p/senlin-newton-workitems13:02
Qimingnewton work items13:02
*** mbound has joined #openstack-meeting13:02
*** adiantum has quit IRC13:02
*** adiantum1 is now known as adiantum13:02
QimingI don't have additional agenda items to propose, if you have some, please revise the agenda and let me know13:02
Qiming#link https://wiki.openstack.org/wiki/Meetings/SenlinAgenda13:02
lixinhui_hi13:03
Qimingback to etherpad13:03
*** cknight has joined #openstack-meeting13:03
Qimingtempest testing - done?13:03
*** amotoki has quit IRC13:03
yanyanhuhi, looks like my network disconnected for a little while13:03
*** nisha_ is now known as nisha13:03
*** Na3iL has joined #openstack-meeting13:03
yanyanhuQiming, yes13:04
yanyanhutempest test is done13:04
Qiminggreat, thx13:04
Qimingremoving line 4-613:04
*** woodster_ has joined #openstack-meeting13:04
*** nisha is now known as Guest167813:04
Qimingdo we want to add some integration tests?13:04
*** shaohe_feng has quit IRC13:04
Qimingdoesn't look like a challenging task, but still need some design13:05
yanyanhuno problem :)13:05
*** shaohe_feng has joined #openstack-meeting13:05
Qimingok13:05
yanyanhuQiming, yes, that's a good idea13:05
Qimingnext is performance evaluation13:05
yanyanhuwe can start from a simple one13:06
Qimingany updates? lixinhui_ ?13:06
yanyanhujust to verify the interaction between senlin and nova13:06
lixinhui_around the end of July13:06
lixinhui_I can get performance test bed again13:06
Qimingyanyanhu, that's fine13:06
*** mjturek1 has left #openstack-meeting13:06
Qimingthanks, lixinhui_13:07
lixinhui_then we can try the nova13:07
lixinhui_settings13:07
Qimingokay13:07
Qimingwhat's the status of rally stress testing now? yanyanhu13:07
yanyanhuthat patch for cluster/profile plugins is still pending there13:08
*** Ed___ has joined #openstack-meeting13:08
yanyanhuwill contact with rally team to merge it13:08
yanyanhuI think it has been ready13:08
Qimingsounds good13:08
yanyanhuin my local repo. I also finished test job for scaling and resizing13:09
Qimingmoving on ...13:09
Qiminghealth management13:09
yanyanhubut will wait for the basic cluster/profile support13:09
*** giri has joined #openstack-meeting13:09
*** enriquetaso has joined #openstack-meeting13:09
lixinhui_I am investigating the nova event13:10
lixinhui_about host failure13:10
*** Na3iL has quit IRC13:10
*** toddjohn has quit IRC13:10
Qimingare they sending out any notifications when a compute node is down?13:10
lixinhui_and manually try live miggration13:10
lixinhui_Qiming, still need check13:10
*** toddjohn has joined #openstack-meeting13:11
lixinhui_will give result this week13:11
*** Ed____ has joined #openstack-meeting13:11
Qiminggreat!13:11
lixinhui_seems live migration13:11
lixinhui_behave not steady13:11
lixinhui_and need quiet few of settings13:11
lixinhui_like libvert version13:12
lixinhui_and ssh connection between the source and target host13:12
*** Ed___ has quit IRC13:12
Qiminglive migration is not easy13:12
*** jckasper has joined #openstack-meeting13:13
*** obondarev has quit IRC13:13
*** sudipto has joined #openstack-meeting13:13
lixinhui_if so, we may need to involve system level operation13:13
Qimingnot sure how many people are doing live migration in production environments13:13
lixinhui_since we can not think all the nodes ready for live migration13:13
*** Na3iL has joined #openstack-meeting13:13
*** asettle has joined #openstack-meeting13:13
Qimingbut we will need to know host failures anyway13:14
*** banix has joined #openstack-meeting13:14
lixinhui_okay13:14
*** giri has quit IRC13:14
*** fzdarsky has joined #openstack-meeting13:14
*** shaohe_feng has quit IRC13:15
lixinhui_anyway, KVM live migration is less efficient than vsphere13:15
*** toddjohn has quit IRC13:15
Qimingthe lbaas bug has been there for quite a while, just checked the bug comment history13:15
*** shaohe_feng has joined #openstack-meeting13:15
lixinhui_the bug is tagged as "low handing fruit"13:16
Qimingit is labeled 'low-hanging-fruit' ... but no one is fixing it, it is assigned and reassigned and reassigned ...13:16
*** bzhao has quit IRC13:16
lixinhui_...13:16
*** Ed____ has quit IRC13:16
lixinhui_I already assigned it to myself13:16
lixinhui_but need people to review13:16
lixinhui_if saw the history13:16
*** jamesdenton has joined #openstack-meeting13:16
Qimingyes, it was reported on Feb 2313:17
*** Ed___ has joined #openstack-meeting13:17
*** bzhao has joined #openstack-meeting13:17
lixinhui_I already sticked the fix link there13:17
*** Guest1678 is now known as nisha_13:17
*** nisha_ has quit IRC13:17
*** cleong has joined #openstack-meeting13:17
*** mriedem_away is now known as mriedem13:17
*** nisha_ has joined #openstack-meeting13:17
*** neiljerram has quit IRC13:17
Qimingokay, that two patches are all that needed to fix the bug?13:18
lixinhui_yes13:18
lixinhui_one is framework, the other is implements for driver of octvia13:18
*** esberglu has joined #openstack-meeting13:19
Qimingthen you are supposed to add the 'bug' tag like this in both patches: partial-bug: #154877413:19
openstackbug 1548774 in neutron "LBaas V2: operating_status of 'dead' member is always online with Healthmonitor" [Undecided,Incomplete] https://launchpad.net/bugs/154877413:19
Qimingbecause neither patch is closing the bug13:19
*** dmorita has quit IRC13:20
lixinhui_okay13:21
lixinhui_I will try13:21
*** julim has joined #openstack-meeting13:21
Qimingif we need to push octvia team, we should do it13:21
*** zeih has quit IRC13:21
lixinhui_need let the framework one pass firstly13:22
lixinhui_then octavia and nsx will follow quickly13:22
*** Leo_ has joined #openstack-meeting13:22
Qimingso there is a dependency between those patches13:22
Qimingneed to remind the reviewers as well13:22
lixinhui_yes13:22
Qimingok13:23
Qimingthreshold for cluster health status13:23
lixinhui_already add the dependency in the commit message13:23
*** julim has quit IRC13:23
lixinhui_will add comments if help13:23
*** amotoki has joined #openstack-meeting13:23
*** neiljerram has joined #openstack-meeting13:23
Qiminglixinhui_, contact the reviewers if necessary13:23
*** margaret has quit IRC13:24
Qimingnot all reviewers have subscribed to bug reports I think13:24
*** dmorita has joined #openstack-meeting13:24
*** gcb has quit IRC13:24
lixinhui_oh, okay13:24
*** yanyanhu has quit IRC13:24
Qimingcomments there may get unnoticed/ignored easily13:24
*** margaret has joined #openstack-meeting13:24
*** lblanchard has joined #openstack-meeting13:24
*** gcb has joined #openstack-meeting13:25
*** shaohe_feng has quit IRC13:25
Qimingthreshold for cluster health status, do we agree to remove that item from the etherpad?13:25
*** spzala has joined #openstack-meeting13:25
*** shaohe_feng has joined #openstack-meeting13:25
*** zhurong has quit IRC13:25
*** yanyanhu has joined #openstack-meeting13:25
Qimingwe had that discussion at least twice in the past, it seems to me we don't have an urgent need to add an additional watermark at the moment13:26
Qiming?13:26
lixinhui_I agree13:27
*** tonytan4ever has joined #openstack-meeting13:27
yanyanhuhi, just dropped13:27
xuhaiwei_yes, we can remove I think13:27
Qimingokay, removing it13:28
Qimingabout the HA story line, I'm not aware of any comments/revisions at this moment13:28
*** dmorita has quit IRC13:28
*** amotoki has quit IRC13:28
*** jrist_ has joined #openstack-meeting13:29
*** jtomasek__ has joined #openstack-meeting13:29
Qimingplease don't hesitate to input your thoughts if you have got some13:29
*** dtrainor_ has joined #openstack-meeting13:29
*** dbecker_ has joined #openstack-meeting13:29
Qimingfencing support13:29
*** obondarev has joined #openstack-meeting13:29
Qimingany design/code for review?13:30
*** nisha_ has quit IRC13:30
*** d0ugal_ has joined #openstack-meeting13:30
*** singhj has joined #openstack-meeting13:30
lixinhui_I can share manual steps out13:30
lixinhui_but got no much time thinking design yet13:30
Qimingokay, if needed, we can create a BP for this13:31
*** nisha_ has joined #openstack-meeting13:31
Qimingor a spec13:31
lixinhui_okay13:31
Qimingneed a "whiteboard" to collect ideas13:31
Qimingmoving on13:32
lixinhui_need cluster-do firstly to install fencing lib13:32
lixinhui_maybe ...13:32
*** jrist has quit IRC13:32
*** dtrainor has quit IRC13:32
lixinhui_we discuss more in next few days13:32
*** dbecker has quit IRC13:32
Qimingno update on documentation from my side, deeply trapped by troubles/happiness at home13:32
*** d0ugal has quit IRC13:33
Qimingokay, we can discuss that for sure13:33
zzxwill_'some use cases' for what function?13:33
*** jtomasek_ has quit IRC13:33
*** ajmiller has quit IRC13:33
QimingI'm not sure if we need to install something13:33
*** ajmiller has joined #openstack-meeting13:33
*** baoli_ has quit IRC13:34
Qimingzzxwill_, it is about autoscaling, load-balancing, rolling-upgrade, high-availability ...13:34
*** jrist_ has quit IRC13:34
zzxwill_Noted.13:34
Qimingthe idea is to write something so that users will get a better idea what they can do with senlin13:34
Qimingmoving on ...13:35
Qimingcontainer support, haiwei?13:35
*** shaohe_feng has quit IRC13:35
*** lpetrut has quit IRC13:35
xuhaiwei_I want to have some discussion with you guys13:35
*** d0ugal_ is now known as d0ugal13:35
*** mtanino has joined #openstack-meeting13:36
*** shaohe_feng has joined #openstack-meeting13:36
*** d0ugal is now known as Guest6571513:36
Qimingsure, feel free to call for a online discussion or a phone call, ... whatever13:36
*** designbybeck_ has joined #openstack-meeting13:36
xuhaiwei_first one is shall we use floating_ip in docker client's url13:36
*** Guest65715 has quit IRC13:36
Qiminglast review comment was from May 2613:36
Qiming(referring to the spec)13:36
*** d0ugal_ has joined #openstack-meeting13:36
*** mickeys has joined #openstack-meeting13:37
xuhaiwei_the spec may be not a good place to discuss13:37
zzxwill_Qiming, for example, we need to complete 'Making Your Cluster Elastic13:37
zzxwill_' http://docs.openstack.org/developer/senlin/tutorial/autoscaling.html?13:37
*** baoli has joined #openstack-meeting13:37
xuhaiwei_I will create an ether pad to list the questions I want to discuss with you13:37
Qimingokay, got it, we have quite some tech details for discussion13:37
Qimingokay, pls share with the team13:38
xuhaiwei_ok13:38
Qimingzzxwill_, correct, that is the tutorial documentation we have yet to work on13:38
*** dtrainor_ has quit IRC13:38
*** baoli_ has joined #openstack-meeting13:39
zzxwill_Got it, thanks.13:39
Qimingengine side, no update from me13:39
Qimingzaqar receiver13:39
*** trozet has joined #openstack-meeting13:40
Qimingyanyan has proposed patches to openstacksdk, not elegant solution, but workable13:40
yanyanhuyes, spent some time working on zaqar driver last two weeks13:40
*** Na3iL has quit IRC13:40
Qiminghopefully we can convince that team that a 'headers' param is needed for sure13:40
*** sdake_ has joined #openstack-meeting13:41
yanyanhuI think biran has agree we can use current implementation as solution for zaqar api resources13:41
Qimingwe need that param to send 'openstack-api-version' header so that 'cluster-collect' can work13:41
yanyanhubut not sure whether there will be a more generic solution come in future13:41
QimingI think that is a wrong decision13:41
*** mickeys has quit IRC13:41
*** brnelson has quit IRC13:41
Qimingthe correct fix should be revise the resource2.Resource code, so that a 'headers' param can be passed13:41
Qimingthen you don't have to duplicate the code in your queue implementation13:42
*** dtrainor has joined #openstack-meeting13:42
*** brnelson has joined #openstack-meeting13:42
yanyanhuQiming, yes13:42
Qiminganyway, a small step is still a step forward13:42
*** eharney has joined #openstack-meeting13:42
*** baoli has quit IRC13:42
yanyanhubtw, a more difficult issue we will encounter is zaqar queue update API needs special definition for 'content-type' header13:42
*** mtanino has quit IRC13:43
*** manikanta_tadi has quit IRC13:43
Qimingevent/notification --- I don't have progress to update, sorry13:43
*** manikanta_ has quit IRC13:43
Qimingwe can hide that behind the zaqar service api in SDK13:43
yanyanhubut in keystoneauth, request method will always set 'content-type' to 'application/json' when sending out patch request13:43
*** jamesmcarthur has joined #openstack-meeting13:43
yanyanhuso still didn't find a workaround for it13:44
Qimingthe internal resource2.Resource class should open to all headers13:44
*** d0ugal_ has quit IRC13:44
*** akuznetsov has quit IRC13:44
Qiming.... I'm speechless on this13:44
*** d0ugal has joined #openstack-meeting13:44
Qiminghave you mentioned that to feilong?13:44
yanyanhuunless we can make some changes on the implementation of keystoneauth1.session13:45
yanyanhualthough we currently don't need queue update API interface I think13:45
Qimingit sounds like their problem to fix13:45
yanyanhuQiming, yes13:45
yanyanhuI feel so as well13:45
yanyanhuwill talk with feilong about it13:45
yanyanhulooks like a big problem13:45
Qimingokay13:45
*** amotoki has joined #openstack-meeting13:45
*** jrist_ has joined #openstack-meeting13:45
*** shaohe_feng has quit IRC13:45
Qiminglet's move on to the next topic13:46
Qiming#topic barcelona summit13:46
*** openstack changes topic to "barcelona summit (Meeting topic: senlin)"13:46
*** shaohe_feng has joined #openstack-meeting13:46
*** toddjohn has joined #openstack-meeting13:46
QimingI have spent some time yesterday and today on reviewing all the proposals I know of13:46
Qiming15208: Get Your Resource Pool Managed on OpenStack13:46
Qiming15209: Managing clusters of thousands of VMs using Senlin13:46
Qiming15037: On Building an Auto-healing Resource Cluster using Senlin13:46
*** rderose has joined #openstack-meeting13:47
lixinhui_And13:47
lixinhui_1525113:47
lixinhui_Extensible, Flexible, Fine-granularity Cluster Management and Controlling Tool - Senlin13:47
Qimingwhen reviewing these proposals, I really like 15037 - the HA story and 15209 - the scalability analysis and experience sharing13:48
*** bobh has joined #openstack-meeting13:48
*** matthewbodkin has joined #openstack-meeting13:48
*** clenimar has quit IRC13:48
Qimingstill strugging with 15208 - the comparison between heat resource types and senlin service13:48
yanyanhufor 15208, maybe change the name to "Get Your Resource Pool Better Managed on OpenStack"?13:48
Qimingwhen revising that one, I have got some feeling that the comparison is unfair13:49
*** e0ne has quit IRC13:49
Qimingwe are comparing apple to orange13:49
Qimingwe cannot compare a resource type to a service13:49
xuhaiwei_I think we can say by using Senlin, user can use Heat better13:50
Qimingwhat's more, we have already delivered a strong message during Austin summit -- what senlin is, why we started it, it's status, its plan13:50
elynnI just want users to be aware of senlin cluster and maybe migrate from heat ASG to senlin cluster after listening this presentation.13:50
Qimingelynn, users have their own concerns when doing this migration13:51
*** saju_m has joined #openstack-meeting13:51
Qimingif that is the point we want to deliver, we'd better provide some tool/guide for them13:51
*** amrith has quit IRC13:51
yanyanhuso maybe we focus on a specific scenario, autoscaling to deliver the idea13:51
Qimingit doesn't sound that sexy a topic for the barcelona summit13:52
*** amrith has joined #openstack-meeting13:52
yanyanhuwe compare the cons and pros and why there are those difference13:52
yanyanhuthen give user the knowledge about both of them13:52
elynnBy comparing the details of heat ASG and senlin, they might know of what heat ASG can do and what Senlin cluster can do, so they won't keep asking heat to add more features to ASG13:52
Qimingwhy do we need to do that again and again?13:52
Qimingelynn, are you aware of any such requests lately?13:53
*** e0ne has joined #openstack-meeting13:53
yanyanhuthis can be a pure technical comparison I feel13:53
Qimingif there are such request, can we redirect them to senlin ?13:53
elynnNot from community13:54
*** bobh has quit IRC13:54
yanyanhuI guess some users will ask this question :P13:54
Qimingback in austin, we have three talks, and in each one of them, we mentioned that difference13:54
*** r-mibu has quit IRC13:54
yanyanhusince they don't have time to read the code and they want to understand the tech differentiation between these two designs :)13:54
*** r-mibu has joined #openstack-meeting13:54
Qimingit is not interesting to me13:54
QimingI'm more interested in topic 413:55
elynnI think we might need to address those questions in a public place, like summit.13:55
Qimingthe cluster-do feature13:55
*** ajmiller has quit IRC13:55
Qimingwhich is totally new, and designed to solve real life problems for operators13:55
*** ajmiller has joined #openstack-meeting13:55
*** shaohe_feng has quit IRC13:56
*** singhj has quit IRC13:56
Qimingthis time, we have got some restrictions on proposals13:56
*** gongysh has joined #openstack-meeting13:56
Qimingeach presenter can have at most 3 talk proposals, and each proposal may have at most 3 speakers13:56
*** shaohe_feng has joined #openstack-meeting13:56
Qimingso ... I'd like moving my name from the 3rd topic to the 4th one13:57
*** banix has quit IRC13:57
yanyanhuthat is ok I think. We can reorg our presentation later if they are accepted I think ?13:57
*** akuznetsov has joined #openstack-meeting13:57
yanyanhuto better present to the audience13:58
lixinhui_sounds good13:58
*** baojg has joined #openstack-meeting13:58
lixinhui_the limits are hash13:58
*** dmorita has joined #openstack-meeting13:58
lixinhui_s/hash/harsh13:58
yanyanhuso the deadline is tomorrow night beijing time?13:58
Qimingyes13:59
Qimingwe don't have much time on this13:59
*** xarses_ has quit IRC13:59
yanyanhuok, so we have one day to revise the proposal13:59
QimingI have revised topic 313:59
*** yamamoto has quit IRC13:59
yanyanhuneed to finish it tomorrow morning13:59
*** Julien-zte has joined #openstack-meeting13:59
*** dmorita has quit IRC13:59
zzxwill_'The content on this page is obsolete. The autoscaling solution is offloaded from Heat to Senlin since Mitaka." I learn this official message recently. Sounds cool!13:59
QimingI mean the text, I'd propose replace my name by someone else13:59
elynnyes, not much time to do it13:59
Qiming... oh ... time's up13:59
*** sarob has joined #openstack-meeting13:59
Qimingpls go back to #senlin channel for this14:00
yanyanhulets move back to senlin channel14:00
Qimingwe'd release this channel14:00
lixinhui_ok14:00
zzxwill_Okay.14:00
*** singhj has joined #openstack-meeting14:00
Qimingthanks for joining everyone14:00
Qiming#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Tue Jul 12 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-07-12-13.00.html14:00
zzxwill_Thank you.14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-07-12-13.00.txt14:00
*** sarob has quit IRC14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-07-12-13.00.log.html14:00
*** xuhaiwei_ has quit IRC14:00
*** banix has joined #openstack-meeting14:00
*** sarob has joined #openstack-meeting14:00
*** Galitz has quit IRC14:01
*** dasanind has joined #openstack-meeting14:01
*** banix has quit IRC14:01
*** dmorita has joined #openstack-meeting14:01
*** dmorita has quit IRC14:02
*** dmorita has joined #openstack-meeting14:02
*** cschulz has quit IRC14:02
*** Ed___ has quit IRC14:03
*** dasanind has quit IRC14:03
*** cdelatte has joined #openstack-meeting14:03
*** rbak has joined #openstack-meeting14:03
*** ronghui has quit IRC14:04
*** piet has quit IRC14:04
*** sheel has quit IRC14:06
*** mickeys has joined #openstack-meeting14:06
*** shaohe_feng has quit IRC14:06
*** shaohe_feng has joined #openstack-meeting14:07
*** zzxwill_ has quit IRC14:08
*** lpetrut has joined #openstack-meeting14:09
*** zzxwill_ has joined #openstack-meeting14:10
*** kaminohana has quit IRC14:10
*** markvoelker has quit IRC14:11
*** ronghui has joined #openstack-meeting14:12
*** ravelar159 has joined #openstack-meeting14:13
*** zz_dimtruck is now known as dimtruck14:13
*** ikutukov_ has joined #openstack-meeting14:14
*** wznoinsk_ has joined #openstack-meeting14:14
*** ikutukov has quit IRC14:15
*** wznoinsk has quit IRC14:15
*** Nakato has quit IRC14:15
*** numans has quit IRC14:15
*** kprabhuv- has quit IRC14:15
*** karthikp_ has joined #openstack-meeting14:15
*** Wenzhi has quit IRC14:15
*** timrc has quit IRC14:15
*** sigmavirus has quit IRC14:15
*** numan_ has joined #openstack-meeting14:15
*** ikutukov_ is now known as ikutukov14:15
*** links has quit IRC14:15
*** Wenzhi has joined #openstack-meeting14:15
*** timrc has joined #openstack-meeting14:16
*** Nakato has joined #openstack-meeting14:16
*** shaohe_feng has quit IRC14:16
*** shaohe_feng has joined #openstack-meeting14:17
*** _sigmavirus24 has joined #openstack-meeting14:17
*** yanyanhu has quit IRC14:17
*** tonytan_brb has joined #openstack-meeting14:17
*** dasanind has joined #openstack-meeting14:17
*** Julien-zte has quit IRC14:18
*** Julien-zte has joined #openstack-meeting14:19
*** _sigmavirus24 is now known as sigmavirus14:19
*** sigmavirus has joined #openstack-meeting14:19
*** tonytan4ever has quit IRC14:20
*** azbiswas has joined #openstack-meeting14:21
*** karthikp_ has quit IRC14:22
*** spzala has quit IRC14:22
*** saju_m has quit IRC14:23
*** Ed___ has joined #openstack-meeting14:23
*** acoles_ is now known as acoles14:23
*** liamji has joined #openstack-meeting14:24
*** azbiswas has quit IRC14:26
*** zzxwill_ has quit IRC14:26
*** shaohe_feng has quit IRC14:26
*** shaohe_feng has joined #openstack-meeting14:27
*** nisha_ has quit IRC14:27
*** zzxwill_ has joined #openstack-meeting14:27
*** Ed___ has quit IRC14:28
*** mriedem1 has joined #openstack-meeting14:28
*** piet has joined #openstack-meeting14:28
*** zzxwill_ has quit IRC14:29
*** mriedem has quit IRC14:29
*** zzxwill_ has joined #openstack-meeting14:30
*** jmckind has joined #openstack-meeting14:30
*** markvoelker has joined #openstack-meeting14:30
*** ljxiash has joined #openstack-meeting14:30
*** toddjohn_ has joined #openstack-meeting14:31
*** julim has joined #openstack-meeting14:31
*** mriedem1 is now known as mriedem14:31
*** fnaval has quit IRC14:31
*** toddjohn has quit IRC14:32
*** zhhuabj has quit IRC14:32
*** eharney has quit IRC14:32
*** mtanino has joined #openstack-meeting14:32
*** egallen has quit IRC14:32
*** dmacpher is now known as dmacpher-afk14:33
*** amitgandhinz has quit IRC14:33
*** gongysh has quit IRC14:33
*** ajmiller has quit IRC14:33
*** amitgandhinz has joined #openstack-meeting14:33
*** ajmiller has joined #openstack-meeting14:34
*** fzdarsky has quit IRC14:36
*** ajmiller has quit IRC14:36
*** ajmiller has joined #openstack-meeting14:36
*** tonytan4ever has joined #openstack-meeting14:36
*** shaohe_feng has quit IRC14:37
*** zzxwill_ has quit IRC14:37
*** ljxiash has quit IRC14:37
*** lixinhui_ has quit IRC14:37
*** shaohe_feng has joined #openstack-meeting14:37
*** karthikp_ has joined #openstack-meeting14:38
*** singhj has quit IRC14:38
*** tonytan_brb has quit IRC14:39
*** rossella_s has quit IRC14:40
*** spotz_zzz is now known as spotz14:40
*** rossella_s has joined #openstack-meeting14:40
*** oshidoshi has quit IRC14:41
*** ljxiash has joined #openstack-meeting14:42
*** dmorita has quit IRC14:42
*** fnaval has joined #openstack-meeting14:44
*** clenimar has joined #openstack-meeting14:44
*** Ed___ has joined #openstack-meeting14:45
*** david-lyle has joined #openstack-meeting14:46
*** shaohe_feng has quit IRC14:47
*** dasanind has quit IRC14:47
*** shaohe_feng has joined #openstack-meeting14:48
*** Ed___ has quit IRC14:49
*** singhj has joined #openstack-meeting14:49
*** eezhova has quit IRC14:49
*** ljxiash has quit IRC14:50
*** toscalix has joined #openstack-meeting14:50
*** zeih has joined #openstack-meeting14:51
*** xarses has joined #openstack-meeting14:52
*** xarses has quit IRC14:52
*** xarses has joined #openstack-meeting14:53
*** gongysh has joined #openstack-meeting14:53
*** iyamahat has joined #openstack-meeting14:53
*** dslevin has quit IRC14:54
*** nmagnezi has quit IRC14:54
*** nisha_ has joined #openstack-meeting14:55
*** spzala has joined #openstack-meeting14:56
*** singhj has quit IRC14:56
*** shaohe_feng has quit IRC14:57
*** nkrinner is now known as nkrinner_afk14:58
*** shaohe_feng has joined #openstack-meeting14:58
*** pnavarro has quit IRC14:58
*** baojg has quit IRC14:58
*** dslevin has joined #openstack-meeting14:59
*** singhj has joined #openstack-meeting14:59
*** cody-somerville has joined #openstack-meeting14:59
*** yamamoto has joined #openstack-meeting14:59
*** spotz is now known as spotz_zzz15:00
*** dasanind has joined #openstack-meeting15:01
*** dane_leblanc has joined #openstack-meeting15:01
*** jamesmca_ has joined #openstack-meeting15:02
*** jamesmcarthur has quit IRC15:02
*** elynn has quit IRC15:04
*** weshay_mtg is now known as weshay15:05
*** baojg has joined #openstack-meeting15:05
*** ihrachys has quit IRC15:06
*** yamamoto has quit IRC15:07
*** ronghui has quit IRC15:07
*** nadya has quit IRC15:07
*** hashar is now known as hasharAway15:07
*** shaohe_feng has quit IRC15:07
*** ronghui has joined #openstack-meeting15:07
*** shaohe_feng has joined #openstack-meeting15:08
*** Ravikiran_K has quit IRC15:08
*** dasanind has quit IRC15:08
*** dmorita has joined #openstack-meeting15:09
*** numan_ has quit IRC15:09
*** dmorita has quit IRC15:10
*** baojg has quit IRC15:10
*** yamahata has joined #openstack-meeting15:10
*** adisky has quit IRC15:11
*** lpetrut has quit IRC15:12
*** anshukch has joined #openstack-meeting15:12
*** Oshidoshi has joined #openstack-meeting15:16
*** dmorita has joined #openstack-meeting15:17
*** shaohe_feng has quit IRC15:18
*** ihrachys has joined #openstack-meeting15:18
*** belmoreira has joined #openstack-meeting15:18
*** dmorita has quit IRC15:18
*** sarob has quit IRC15:19
*** acoles is now known as acoles_15:19
*** vishwanathj has joined #openstack-meeting15:19
*** timcline has joined #openstack-meeting15:19
*** timcline has quit IRC15:20
*** timcline has joined #openstack-meeting15:20
*** jaypipes has joined #openstack-meeting15:21
*** nkrinner_afk is now known as nkrinner15:22
*** andymaier has quit IRC15:23
*** shaohe_feng has joined #openstack-meeting15:23
*** jmckind_ has joined #openstack-meeting15:23
*** tellesnobrega is now known as tellesnobrega_af15:24
*** david-lyle has quit IRC15:24
*** xarses has quit IRC15:25
*** jmckind has quit IRC15:26
*** xarses has joined #openstack-meeting15:26
*** klkumar has quit IRC15:26
*** Ed___ has joined #openstack-meeting15:26
*** e0ne has quit IRC15:26
*** ericksonsantos has joined #openstack-meeting15:26
*** harlowja_at_home has joined #openstack-meeting15:27
*** shaohe_feng has quit IRC15:28
*** shaohe_feng has joined #openstack-meeting15:28
*** fzdarsky has joined #openstack-meeting15:30
*** Ed___ has quit IRC15:31
*** ajmiller has quit IRC15:31
*** armax has joined #openstack-meeting15:32
*** ajmiller has joined #openstack-meeting15:32
*** Leo_ has quit IRC15:32
*** ronghui has quit IRC15:33
*** rajinir has joined #openstack-meeting15:35
*** sdake_ has quit IRC15:36
*** manikanta_tadi has joined #openstack-meeting15:36
*** lpetrut has joined #openstack-meeting15:36
*** sdake_ has joined #openstack-meeting15:36
*** akuznetsov has quit IRC15:37
*** Oshidoshi has quit IRC15:38
*** spotz_zzz is now known as spotz15:38
*** shaohe_feng has quit IRC15:38
*** shaohe_feng has joined #openstack-meeting15:39
*** lpetrut1 has joined #openstack-meeting15:39
*** sridharg has quit IRC15:39
*** bauzas is now known as bauzas_notabot15:40
*** lpetrut has quit IRC15:40
*** lpetrut1 is now known as lpetrut15:40
*** belmoreira has quit IRC15:42
*** jamesmca_ has quit IRC15:42
*** banix has joined #openstack-meeting15:45
*** ronghui has joined #openstack-meeting15:45
*** ericksonsantos has quit IRC15:48
*** mikelk has quit IRC15:48
*** ericksonsantos has joined #openstack-meeting15:48
*** shaohe_feng has quit IRC15:48
*** Leo_ has joined #openstack-meeting15:48
*** shaohe_feng has joined #openstack-meeting15:49
*** andreas_s has quit IRC15:49
*** mestery has quit IRC15:49
*** mriedem1 has joined #openstack-meeting15:49
*** toscalix has quit IRC15:50
*** mestery has joined #openstack-meeting15:50
*** mriedem has quit IRC15:51
*** dmorita has joined #openstack-meeting15:52
*** dmorita has quit IRC15:52
*** mriedem has joined #openstack-meeting15:52
*** penick has joined #openstack-meeting15:53
*** janki has joined #openstack-meeting15:54
*** mriedem1 has quit IRC15:54
*** xuhaiwei_ has joined #openstack-meeting15:54
*** gyee has joined #openstack-meeting15:55
*** obondarev has quit IRC15:56
*** adiantum has quit IRC15:57
*** ajmiller has quit IRC15:57
*** ajmiller has joined #openstack-meeting15:58
*** shaohe_feng has quit IRC15:59
*** sripriya has joined #openstack-meeting15:59
*** shaohe_feng has joined #openstack-meeting15:59
*** kebray has joined #openstack-meeting16:00
*** tbh has joined #openstack-meeting16:00
*** kylek3h has joined #openstack-meeting16:00
*** s3wong has joined #openstack-meeting16:00
*** spzala has quit IRC16:00
*** tung_doan has joined #openstack-meeting16:00
*** pcaruana has quit IRC16:00
sridhar_ram#startmeeting tacker16:01
openstackMeeting started Tue Jul 12 16:01:06 2016 UTC and is due to finish in 60 minutes.  The chair is sridhar_ram. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: tacker)"16:01
openstackThe meeting name has been set to 'tacker'16:01
sridhar_ram#topic Roll Call16:01
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"16:01
manikanta_tadio/16:01
jankio/16:01
s3wongo/16:01
*** rrecio has joined #openstack-meeting16:01
*** leeantho has joined #openstack-meeting16:01
sripriyao/16:01
tbho/16:01
vishwanathjo/16:01
sridhar_ramHowdy folks !16:01
xuhaiwei_hi, I am new to Tacker, this is my first team meeting16:02
tung_doanHi all16:02
sridhar_ramHere is a shout out to silent observers .. if they are interested in introducing themselves. !16:02
sridhar_ramxuhaiwei_: welcome to the project!16:02
vishwanathjxuhaiwei_ Welcome16:02
*** obondarev has joined #openstack-meeting16:02
xuhaiwei_thanks, guys16:02
*** spzala has joined #openstack-meeting16:03
sridhar_ramlets start..16:03
sridhar_ram#topic Agenda16:03
*** openstack changes topic to "Agenda (Meeting topic: tacker)"16:03
sridhar_ram#link https://wiki.openstack.org/wiki/Meetings/Tacker16:03
*** rcernin has quit IRC16:03
sridhar_ramanything else beyond the ones listed ?16:03
*** KanagarajM_ has joined #openstack-meeting16:03
*** jlanoux has quit IRC16:04
*** jmckind_ has quit IRC16:04
sridhar_ramI've one last minute item related to Team mascot16:04
sridhar_ram#topic Announcements16:04
*** openstack changes topic to "Announcements (Meeting topic: tacker)"16:04
sridhar_ram#info Lin Hua Cheng has stepped down tacker-horizon core team16:05
vishwanathjoh16:05
sridhar_ramLin's work has moved away from OpenStack and he has stepped down both as horizon core and in tacker-horizon project16:05
sridhar_ramI'd like to thank Lin for his help so far in the project..16:06
sripriya+116:06
vishwanathj+116:06
manikanta_tadi+116:06
tbh+116:06
*** dprince has quit IRC16:06
sridhar_ramHe has introduced Tacker project to Horizon PTL for further tacker - horizon collaboration16:06
KanagarajM_really appreciate Lin, thanks !16:06
*** harlowja_at_home has quit IRC16:06
*** jckasper has quit IRC16:06
*** tonytan_brb has joined #openstack-meeting16:07
sridhar_ramA shout out for Tacker is planned in Horizon project's upcoming mid-cycle16:07
*** ihrachys has quit IRC16:07
*** ober37 has quit IRC16:07
sridhar_ramnext...16:07
*** spzala has quit IRC16:08
*** jckasper has joined #openstack-meeting16:08
*** Ed___ has joined #openstack-meeting16:08
sridhar_ramSummit talk deadline is tomorrow..16:08
*** bkeller` has quit IRC16:08
*** Julien-zte has quit IRC16:08
sridhar_ramPlease use #Tacker to tag all the talks related to this project..16:08
*** azbiswas has joined #openstack-meeting16:08
sridhar_ramIt was initially missing and i had the Summit team add it for us16:09
sridhar_ramanything else to announce from anyone here ?16:09
*** shaohe_feng has quit IRC16:09
*** sdake_ has quit IRC16:09
sridhar_rammoving on..16:09
sridhar_ram#topic Alarm based monitoring16:09
*** openstack changes topic to "Alarm based monitoring (Meeting topic: tacker)"16:09
*** tesseract- has quit IRC16:09
*** tonytan4ever has quit IRC16:09
*** shaohe_feng has joined #openstack-meeting16:10
sridhar_ramtung_doan: please take over..16:10
*** sdake_ has joined #openstack-meeting16:10
tung_doansridhar, thanks16:10
tung_doanCurrently, I started to code. My first focus is on implementing new abstract driver, alarm-listener and modifying monitoring framework16:10
*** jmckind has joined #openstack-meeting16:10
tung_doanI will finish soon and hope you guys review later.16:10
*** karthikp_ has quit IRC16:10
sridhar_ramtung_doan: cool, some code / prototyping helps to shape the spec better16:11
tung_doansridhar_ram: yeah.. i try to do it...16:11
tung_doansridhar_ram: As Sridhar mentioned in the last meeting, in case scaling is triggered by alarm-based monitoring driver, I agree that it has an overlap with scaling spec16:11
tung_doansridhar_ram: So in the view of alarm spec, can I support KanagarajM to implement scaling usecase?16:12
*** Ed___ has quit IRC16:12
*** jckasper has quit IRC16:12
*** david-lyle has joined #openstack-meeting16:13
sridhar_ramKanagarajM_: do you need tung_doan to pitch in for scaling ?16:13
tung_doanKanagarajM: last week, I reviewed scaling code and realized that Heat driver should add alarm monitoring policy. I would like to update this...16:13
*** toddjohn_ has quit IRC16:13
*** dmorita has joined #openstack-meeting16:13
tung_doanKanagarajM: , please help me to review.. if possible16:13
KanagarajM_sridhar_ram, I am fine if tung_doan really want to impl16:14
*** tellesnobrega_af is now known as tellesnobrega16:14
*** toddjohn has joined #openstack-meeting16:14
*** toddjohn has quit IRC16:14
KanagarajM_tung_doan, sure. I will review. thanks for looking at it.16:14
tung_doanKanagarajM: thanks.. I will update ASAP16:14
sridhar_ramtung_doan: it is unclear to me which part of scaling you are interested.. my understanding is scaling is fully taken care in KanagarajM_ spec and code..16:14
*** nkrinner is now known as nkrinner_afk16:15
sridhar_ramtung_doan: alarm-mon spec will stop at invoke *any* specified action.. one of the action could be scaling16:15
*** bauzas_notabot is now known as bauzas16:15
*** obondarev has quit IRC16:16
sridhar_ramtung_doan: so, the only thing i anticipate is an integration work after both yours and KanagarajM_ work lands16:16
tung_doansridhar_ram:  right.. I mean that auto-scaling will need to have monitoiring policy if we want to do it automatically16:16
*** Patifa has joined #openstack-meeting16:16
*** jamesmcarthur has joined #openstack-meeting16:16
tung_doansridhar_ram:  not about alarm-based monitoring driver.. it is different16:16
KanagarajM_sridhar_ram, yes. one change needed from scaling is, setup the metadata to support auto-scaling16:16
*** bkeller` has joined #openstack-meeting16:17
sridhar_ramtung_doan: yes, but scaling feature is designed in a way it doesn't matter who triggers it.. manual vs alarm-mon16:17
KanagarajM_tung_doan, sridhar_ram i will do it once scaling impl lands16:17
sridhar_ramKanagarajM_: okay...16:17
*** ober37 has joined #openstack-meeting16:18
sridhar_ramKanagarajM_: tung_doan: sure, you guys can definitely collaborate to get that delta taken care..16:18
sridhar_ramtung_doan: KanagarajM_: thanks for the explanation..16:18
KanagarajM_sridhar_ram, sure.16:18
*** jckasper has joined #openstack-meeting16:18
tung_doansridhar_ram:  thanks for reviewing my spec :)16:18
sridhar_ramanother general sticking point is .. "vnf-update" to change the threshold16:19
sridhar_ramthis is something new for Tacker..16:19
*** dmorita has quit IRC16:19
*** shaohe_feng has quit IRC16:19
sridhar_ramnot sure, if we have thought about all the implications it brings in16:19
*** ajmiller has quit IRC16:19
tung_doansridhar_ram:  i think that's something we should support16:19
*** ajmiller has joined #openstack-meeting16:19
sridhar_ramtung_doan: why ? can't we expect the VNF operator to feed to correct threshold values during instantiation ?16:20
*** shaohe_feng has joined #openstack-meeting16:20
sridhar_ram*feed he16:20
sridhar_ram**feed the16:20
KanagarajM_sridhar_ram, if we want to change any thing mentioned int VNFD after provisioning, we may need to peacefully handle VNFD first before updatign the actual VNF16:20
tung_doansridhar_ram:  actually, ceilometer already support this for alarm16:21
*** toddjohn has joined #openstack-meeting16:21
*** david-lyle has quit IRC16:21
sridhar_ramKanagarajM_: we can't "touch" VNFD after it is uploaded.. FWIW, it could in a git repo16:21
KanagarajM_sridhar_ram, yes.16:22
*** armax_ has joined #openstack-meeting16:22
KanagarajM_sridhar_ram, i just insisted on it :)16:22
sridhar_ramNFV catalog evolution is a whole different topic :)16:22
KanagarajM_sridhar_ram, got it :)16:22
*** Swami has joined #openstack-meeting16:22
*** shashank_hegde has joined #openstack-meeting16:22
sridhar_ramback to updating alarm thresholds in the middle of a VNF life-cycle .. i'm trying to judge whether it is MUST-HAVE or a nice-to-have16:23
*** karthikp_ has joined #openstack-meeting16:23
*** sandanar_ has quit IRC16:23
sridhar_ramwhat is the team's take ?16:23
*** gongysh has quit IRC16:23
KanagarajM_tung_doan, is therosold not captured in the VNFD ?16:24
vishwanathjHave you see any requests for that feature lately?16:24
*** sdake_ has quit IRC16:24
*** armax has quit IRC16:24
*** armax_ is now known as armax16:24
*** sandanar has quit IRC16:24
*** d0ugal has quit IRC16:24
*** garthb has joined #openstack-meeting16:24
tung_doansridhar_ram:  yes.16:24
sripriyasridhar_ram: it is nice-to-have, we can then just parameterize the template for the thresholds and then update it on the VNF16:25
*** toddjohn has quit IRC16:25
*** dbecker_ has quit IRC16:25
vishwanathjsripriya good point16:25
*** jmckind has quit IRC16:25
sridhar_ramsripriya: agree, but our parameterization story stops at initiation .. and it doesn't come into picture after a VNF goes ACTIVE16:26
*** obondarev has joined #openstack-meeting16:26
*** jmckind has joined #openstack-meeting16:26
sridhar_ramthat is my I see this as a new precedence.. in fact, not even related to alarm-mon..16:26
*** jtomasek__ has quit IRC16:26
sridhar_ramit has other implications.. to change VNF properties after it is instantiated..16:26
sripriyasridhar_ram: yes, right now we only update the config and this will be something new to be handled as part of vnf-update16:26
sripriyasridhar_ram: agree it is a separate RFE and need not be mixed with alarm-mon feature16:27
*** KanagarajM has joined #openstack-meeting16:27
sridhar_ramexactly, that is why i don't want this to come in as part of alarm-mon, instead consciously bring it in as a tacker capability16:27
*** ninag has joined #openstack-meeting16:27
*** jmckind has quit IRC16:28
*** jmckind has joined #openstack-meeting16:28
sridhar_ramtung_doan: our vnf-update flow is currently restricted to invoking mgmt-driver16:28
sripriyasridhar_ram: yeah16:28
tung_doansridhar_ram:  it's fine for me.16:29
*** dtrainor has quit IRC16:29
sridhar_ramtung_doan: I'd recommend we take the "vnf-update" portion of your spec in a follow on16:29
*** KanagarajM__ has joined #openstack-meeting16:29
*** shaohe_feng has quit IRC16:29
*** jmckind has quit IRC16:29
sridhar_ramtung_doan: other than this, i'm good to go w/ the spec..16:29
*** KanagarajM_ has quit IRC16:29
sripriyatung_doan: you could capture it in future enhancements nice-to-have in your spec16:29
*** MIDENN_ has joined #openstack-meeting16:30
*** mdenny has quit IRC16:30
*** ijw has joined #openstack-meeting16:30
tung_doansridhar_ram:  sripriya: thanks16:30
sridhar_ramtung_doan: captured few editorial comments as well16:30
sridhar_ramtung_doan: overall looks good !16:30
*** jmckind has joined #openstack-meeting16:30
*** shaohe_feng has joined #openstack-meeting16:30
*** tellesnobrega is now known as tellesnobrega_af16:30
tung_doansridhar_ram: ok.. will do16:30
sridhar_ramanything else on alarm-mon ?16:30
*** jrist_ has quit IRC16:30
sridhar_ram#topic NSD support16:31
*** openstack changes topic to "NSD support (Meeting topic: tacker)"16:31
sridhar_ramdkushwaha: tbh: are you here ?16:31
manikanta_tadisridhar_ram: I think you have missed VNFC Support in the agenda ?16:32
*** obondarev has quit IRC16:32
*** KanagarajM has quit IRC16:32
*** ninag has quit IRC16:32
tbhhi sridhar_ram , I couldn't have much updates from NSD side this week, dharmendra updated the spec regarding the ReST APi16:32
sridhar_rammanikanta_tadi: will get to VNFC after NSD16:33
manikanta_tadisridhar_ram: Ok16:33
sridhar_ramtbh: thanks, np16:33
sridhar_ramteam: here is the spec to review .. https://review.openstack.org/#/c/304667/4/specs/newton/nsd-support.rst16:33
sridhar_ramwe can continue the discussion in the gerrit16:34
sridhar_rammoving on..16:34
sridhar_ram#topic VNFC support16:34
*** openstack changes topic to "VNFC support (Meeting topic: tacker)"16:34
sridhar_ramtbh: manikanta_tadi: please take over16:34
*** Rockyg has joined #openstack-meeting16:34
manikanta_tadisridhar_ram, I am working with tbh to bring the spec to better shape.16:34
*** KanagarajM has joined #openstack-meeting16:34
tbhsridhar_ram, we have created the spec for VNFC support https://review.openstack.org/#/c/339798/16:35
*** jmckind has quit IRC16:35
manikanta_tadii have one doubt in mind, Why should not we have VNFC as seperate resource in the Tacker ...rather as parameter in the TOSCA templates ?16:36
KanagarajMsorry team, my internet became too bad today !16:36
*** jmckind has joined #openstack-meeting16:36
*** KanagarajM__ has quit IRC16:36
sridhar_ramKanagarajM: noticed that, it is like weather16:36
*** david-lyle has joined #openstack-meeting16:36
*** e0ne has joined #openstack-meeting16:36
KanagarajMsridhar_ram, :)16:36
KanagarajMsridhar_ram, not sure if i missed to answer .16:37
sridhar_rammanikanta_tadi: it about modeling, logically VNFC maps to the runtime s/w within a Virtual Machine (VDU)16:37
*** asettle has quit IRC16:37
sridhar_ramso, VNFC is a sub-component of VNF16:38
sridhar_ramwe don't have a tacker resource that is granular than VNF today..16:38
*** mrmartin has quit IRC16:38
manikanta_tadisridhar_ram: Ok16:39
tbhsridhar_ram, manikanta_tadi  raised that point because we want to make use of VNFC for updating of s/w too16:39
sridhar_ramVNFC is something a VNFD author need to decide when "designing" a VNF.. it is not the "Operator" job to decide which VNFC should go where16:39
*** shaohe_feng has quit IRC16:40
sridhar_ramtbh: yes, we need to support "vnf-upgrade" operation in the near future16:40
*** sdake_ has joined #openstack-meeting16:40
*** shashank_hegde has quit IRC16:40
manikanta_tadisridhar_ram: But then i am not sure how a vnf upgrade needs to be handled16:40
sridhar_ramtbh: we can still refer to the VNFC within the VNFD for the upgrade / update operation...16:40
*** shaohe_feng has joined #openstack-meeting16:40
*** asettle has joined #openstack-meeting16:41
tbhsridhar_ram, if it binds to VNF, how can we try to use vnf-upgrade?16:41
KanagarajMsridhar_ram, tbh, i was assuming that VNF mostly go with golden image concept instead16:41
*** ebalduf_ has joined #openstack-meeting16:41
sridhar_rammanikanta_tadi: that could be similar to how we do "vnf-scaling <policy-name>"16:41
sridhar_ramKanagarajM: Exactly16:41
*** jmckind has quit IRC16:41
KanagarajMsridhar_ram, so do we need to support software installation on top of running VNF ?16:42
*** eharney has joined #openstack-meeting16:42
*** thorst is now known as thorst_afk16:42
sridhar_ramthe spec need to clearly mention the motivation behind this ask.. operators want security hardened, golden base image (like CentOS) and populate installation s/w on top of it16:42
sridhar_ramKanagarajM: yes, that is the crux of the VNFC support..16:43
*** rderose_ has joined #openstack-meeting16:43
manikanta_tadiKanagarajM, sridhar_ram : We should some one wants to build the images , I think its good to have the loose coupling between the software component and underlying image?16:43
sridhar_raminstead of sneaking in s/w installation into cloud-init.. VNFC will explicit "model" the s/w installed on golden base image16:43
*** unicell1 has quit IRC16:43
sridhar_rammanikanta_tadi: yes, +1 for loose coupling16:44
KanagarajMsridhar_ram, +116:44
sripriyai had the same concern, so this spec deals with installing VNF application on a running VNF instance with prebuilt image than having the application also tightly integrated with the VNF instance16:44
sripriya+116:44
*** myoung is now known as myoung|afk16:44
sridhar_ramsripriya: sorry, what is the concern here ?16:45
*** asettle has quit IRC16:46
*** karthikp_ has quit IRC16:46
*** Suyash has joined #openstack-meeting16:46
sridhar_ramIMO, the main design knot to crack is the mechanism by which tacker will install, uninstall s/w on the VM it spawned16:46
*** azbiswas_ has joined #openstack-meeting16:46
*** dbecker has joined #openstack-meeting16:46
*** asettle has joined #openstack-meeting16:46
*** karthikp_ has joined #openstack-meeting16:47
*** rderose has quit IRC16:47
sridhar_ramKanagarajM: i'm assuming Heat's SoftwareComponent would've solved this problem for cloud-init enabled VMs ?16:47
manikanta_tadisridhar_ram: I thought Operator will  be the VNFD Author , is it not true16:47
KanagarajMsridhar_ram, yes16:47
sridhar_ramwell, the person who pushes the button on "vnf-create" is probably the not the same person who wrote the VNFD template16:48
*** david-lyle has quit IRC16:48
tbhsridhar_ram, I am here not totally depending on the SoftwareComponent of heat16:49
*** dmorita has joined #openstack-meeting16:49
*** KanagarajM_ has joined #openstack-meeting16:49
*** Ed___ has joined #openstack-meeting16:49
*** azbiswas has quit IRC16:49
*** shaohe_feng has quit IRC16:50
*** roxanaghe has joined #openstack-meeting16:50
sridhar_ramHere is my key take away for the VNFC effort (a) we need TOSCA modeling for the s/w running in "blank" VMs - this is not possible today and we need this support (b) once specified in the VNFD model, tacker server need to get the bits into those blank VMs spawnd and invoke the install sequence .. that is the scope of this effort .. Make sense ? Did i miss16:50
sridhar_ramanything ?16:50
*** shaohe_feng has joined #openstack-meeting16:50
KanagarajM_sridhar_ram, why blank VM ?16:51
*** liamji has quit IRC16:52
manikanta_tadisridhar_ram :  I think,we should consider adding vnf component upgrade in this spec ?16:52
*** Daisy_ has joined #openstack-meeting16:52
sridhar_ramtbh: take a look at heat SoftwareComponent.. it is works for the above funtionalty we shd make use of it - to save effort + tosca-parser / heat-translator also has SoftwarreComponent support (AFAIK)16:52
tbhsridhar_ram, for invoking, can we provide multiple options to the user?16:52
*** KanagarajM has quit IRC16:52
sridhar_rammanikanta_tadi: no, differ to the next follow-on16:52
sridhar_ramKanagarajM_: by blank VM i meant VM with just the base OS16:53
tbhsridhar_ram, in the spec we mentioned about using SSH instead of SoftwareComponent16:53
*** dmorita has quit IRC16:53
sridhar_ramtbh: you can definitely list diff options in the spec..16:53
sridhar_ramtbh: .. we can discuss it16:54
sripriyasridhar_ram: tbh: i thought the spec mentioned about limited capability  of Sofware Component16:54
vishwanathjIs SoftwareComponent support available for a VM that is already up and running?16:54
*** Ed___ has quit IRC16:54
*** saju_m has joined #openstack-meeting16:54
*** Apoorva has joined #openstack-meeting16:55
*** KanagarajM has joined #openstack-meeting16:55
tbhsripriya, yes I am not sure, does all types of VDUs can support cloud-init itself which SoftwareComponent is using I guess16:55
*** Apoorva has quit IRC16:55
tbhvishwanathj, am not sure it will support16:56
sridhar_ramtbh: ssh might be an option.. i'd suggest you to make some reasonable assumptions.. like the base VMs need to be cloud-init enabled..16:56
sripriyatbh: it can only depend on the image itself if it has cloud-init capability, i dont think we should be based off that dependency16:56
*** zhurong has joined #openstack-meeting16:56
*** Daisy_ has quit IRC16:56
*** jjmorman has quit IRC16:57
*** dprince has joined #openstack-meeting16:57
sridhar_ramsripriya: is it unreasonable in this day & age to insist cloud-init ?16:57
*** KanagarajM_ has quit IRC16:57
sripriyasridhar_ram: does openwrt support this?16:57
sridhar_ramssh has many downsides as well, the primary being credential storage16:57
sridhar_ramopenwrt is different story.. here we are talking about an horizontal capability16:58
sridhar_ramFolks .. we are out of time for today16:58
sridhar_ramlet's continue this next week..16:58
sripriyasridhar_ram: ack16:58
sridhar_ramtbh: please capture different install options in the spec..16:59
tbhsridhar_ram, thanks for the inputs16:59
sridhar_ramtbh: we can zoom in on 1 or more based on further discussion16:59
sridhar_ramgood discussion16:59
sridhar_ram#topic Open Discussion16:59
*** openstack changes topic to "Open Discussion (Meeting topic: tacker)"16:59
*** ajmiller has quit IRC16:59
*** KanagarajM_ has joined #openstack-meeting16:59
sridhar_ramsorry no time this week :)16:59
*** sajeesh has joined #openstack-meeting16:59
sridhar_rambye everyone...16:59
s3wongbye17:00
sridhar_ram#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
*** ajmiller has joined #openstack-meeting17:00
manikanta_tadiThanks All..Bye !17:00
tung_doanbye17:00
openstackMeeting ended Tue Jul 12 17:00:02 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-07-12-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-07-12-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-07-12-16.01.log.html17:00
*** Apoorva has joined #openstack-meeting17:00
*** s3wong has quit IRC17:00
*** sripriya has quit IRC17:00
mmedvede#startmeeting third-party17:00
openstackMeeting started Tue Jul 12 17:00:20 2016 UTC and is due to finish in 60 minutes.  The chair is mmedvede. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: third-party)"17:00
openstackThe meeting name has been set to 'third_party'17:00
*** ja3 has joined #openstack-meeting17:00
*** KanagarajM has quit IRC17:00
*** tung_doan has quit IRC17:00
*** shaohe_feng has quit IRC17:00
mmedvedehi everyone, time for third-party WG meeting17:00
*** xenogear has joined #openstack-meeting17:00
ja3ye haw17:00
mmedvedequick announcement17:00
*** anshukch has left #openstack-meeting17:00
*** shaohe_feng has joined #openstack-meeting17:01
mmedvede#topic Announcements17:01
*** openstack changes topic to "Announcements (Meeting topic: third-party)"17:01
mmedvedeIn case anyone is tracking master branch of nodepool, it is now time to pin it17:01
*** xuhaiwei_ has quit IRC17:01
*** sarob has joined #openstack-meeting17:01
mmedvede(thanks to asselin__ for sending email to ML)17:02
mmedvede#link https://review.openstack.org/#/c/293112/17:02
*** jamesmcarthur has quit IRC17:02
*** zhurong has quit IRC17:02
*** zhurong has joined #openstack-meeting17:03
mmedvede#topic Action items from last meeting17:03
*** openstack changes topic to "Action items from last meeting (Meeting topic: third-party)"17:03
*** mrmartin has joined #openstack-meeting17:04
*** KanagarajM_ has left #openstack-meeting17:04
mmedvede#topic cmmedvede to add jenkins version cap in puppet-jenkins17:04
*** openstack changes topic to "cmmedvede to add jenkins version cap in puppet-jenkins (Meeting topic: third-party)"17:04
*** spotz is now known as spotz_zzz17:04
*** armax_ has joined #openstack-meeting17:04
*** matthewbodkin has quit IRC17:04
mmedvederight after meeting I noticed there was a patch to puppet-jenkins to work around jenkins new security feature17:05
mmedvede#link workaround for Jenkins' SECURITY-170  https://review.openstack.org/#q,I737a6e46b05ec2c02a4a38c94d51b0f6f1bb665e,n,z17:05
mmedvedeso there is no need to cap jenkins version, given the patch above would merge17:05
*** kebray has quit IRC17:06
mmedvedereminder - the new security feature in jenkins would prevent you from sending arbitrary non-whitelisted parameters to the job17:06
*** tbh has left #openstack-meeting17:06
mmedvede#topic Open Discussion17:07
*** openstack changes topic to "Open Discussion (Meeting topic: third-party)"17:07
*** armax has quit IRC17:07
*** armax_ is now known as armax17:07
ja3[crickets]17:08
mmedvedeany topic for discussion?17:08
*** Leo_ has quit IRC17:08
*** singhj has quit IRC17:08
mmedvedeI wonder who else is here :)17:08
*** karthikp_ has quit IRC17:09
ja3nobody but us chickens17:09
mmedvedeshow yourselves17:09
mmedvedehehe17:09
ja3hey hey, no harry potter spells there17:09
*** numan_ has joined #openstack-meeting17:09
*** sarob has quit IRC17:09
*** karthikp_ has joined #openstack-meeting17:09
*** lpetrut has quit IRC17:09
*** toddjohn has joined #openstack-meeting17:09
*** jaypipes has quit IRC17:09
mmedvedeja3: do you have anything to discuss, or lets make it under short today?17:10
*** toddjohn has quit IRC17:10
*** jrist_ has joined #openstack-meeting17:10
ja3no topics heya17:10
*** toddjohn has joined #openstack-meeting17:10
mmedvede*wanted to say under 10 minutes, but it is not happening now :)17:10
*** jckasper has quit IRC17:10
*** manikanta_tadi has quit IRC17:10
*** shaohe_feng has quit IRC17:10
mmedvedeja3: thanks. I'll keep the meeting open for a bit, in case someone shows up17:10
ja3well at least it will be amusing, read (a) later (b) quickly (c) out of context17:11
*** shaohe_feng has joined #openstack-meeting17:11
*** ihrachys has joined #openstack-meeting17:11
*** singhj has joined #openstack-meeting17:13
*** pfallenop has quit IRC17:15
*** sajeesh has quit IRC17:15
mmedvedeso seems none around. thanks ja3 for joining17:16
mmedvede#endmeeting17:16
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:16
openstackMeeting ended Tue Jul 12 17:16:25 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:16
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-07-12-17.00.html17:16
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-07-12-17.00.txt17:16
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-07-12-17.00.log.html17:16
*** jtomasek__ has joined #openstack-meeting17:17
*** pfallenop has joined #openstack-meeting17:17
*** sdake_ has quit IRC17:17
*** QuantaStor has joined #openstack-meeting17:18
*** unicell has joined #openstack-meeting17:18
*** QuantaStor has quit IRC17:18
*** jmckind has joined #openstack-meeting17:19
*** shaohe_feng has quit IRC17:21
*** jrist_ has quit IRC17:21
*** shaohe_feng has joined #openstack-meeting17:22
*** zhurong has quit IRC17:22
*** jtomasek__ has quit IRC17:22
*** janki has quit IRC17:24
*** spzala has joined #openstack-meeting17:24
*** banix has quit IRC17:25
*** s3wong has joined #openstack-meeting17:26
*** spzala_ has joined #openstack-meeting17:27
*** spzala has quit IRC17:27
*** mrmartin has quit IRC17:28
*** elopez_ has joined #openstack-meeting17:29
*** shaohe_feng has quit IRC17:31
*** karthikp_ has quit IRC17:31
*** shaohe_feng has joined #openstack-meeting17:31
*** elopez__ has quit IRC17:31
*** jckasper has joined #openstack-meeting17:32
*** jckasper has quit IRC17:32
*** jckasper has joined #openstack-meeting17:32
*** adiantum has joined #openstack-meeting17:33
*** mickeys has quit IRC17:33
*** mickeys has joined #openstack-meeting17:34
*** topol_ has joined #openstack-meeting17:34
*** kebray has joined #openstack-meeting17:34
*** kebray has quit IRC17:35
*** ijw has quit IRC17:35
*** topol_ has quit IRC17:36
*** ijw has joined #openstack-meeting17:38
*** mickeys has quit IRC17:38
*** shashank_hegde has joined #openstack-meeting17:38
*** ijw has quit IRC17:39
*** dprince has quit IRC17:41
*** shaohe_feng has quit IRC17:41
*** asettle has quit IRC17:41
*** spzala_ has quit IRC17:42
*** shaohe_feng has joined #openstack-meeting17:42
*** spzala has joined #openstack-meeting17:42
*** dprince has joined #openstack-meeting17:43
*** ivar-lazzaro has joined #openstack-meeting17:43
*** thorst_afk is now known as thorst17:45
*** dslevin has left #openstack-meeting17:46
*** gagehugo has joined #openstack-meeting17:46
*** mdenny has joined #openstack-meeting17:46
*** mrmartin has joined #openstack-meeting17:46
*** qwebirc1886 has joined #openstack-meeting17:47
*** spzala has quit IRC17:47
*** puiterwijk is now known as puiterwijk|otg17:47
*** puiterwijk|otg is now known as puiterwijk|outag17:47
*** MIDENN_ has quit IRC17:48
*** puiterwijk|outag is now known as puiterwijk17:49
*** asettle has joined #openstack-meeting17:49
*** asettle has quit IRC17:49
*** asettle has joined #openstack-meeting17:49
*** Wenzhi has quit IRC17:51
*** shaohe_feng has quit IRC17:51
*** andymaier has joined #openstack-meeting17:51
*** shaohe_feng has joined #openstack-meeting17:52
*** Wenzhi has joined #openstack-meeting17:52
*** jaugustine has joined #openstack-meeting17:53
*** amakarov has joined #openstack-meeting17:53
*** aranjan has joined #openstack-meeting17:53
*** pvaneck has joined #openstack-meeting17:53
*** tonytan_brb has quit IRC17:54
*** henrynash has joined #openstack-meeting17:55
*** ijw has joined #openstack-meeting17:56
*** rloo has joined #openstack-meeting17:56
*** electrofelix has quit IRC17:57
*** nk2527 has joined #openstack-meeting17:57
*** fawadkhaliq has joined #openstack-meeting17:57
*** sudipto has quit IRC17:57
*** pabelanger has joined #openstack-meeting17:57
*** e0ne has quit IRC17:58
*** iceyao has quit IRC17:58
*** andymaier has quit IRC17:58
*** dmorita has joined #openstack-meeting17:58
*** haneef has joined #openstack-meeting17:58
*** samueldmq has joined #openstack-meeting17:58
*** andymaier has joined #openstack-meeting17:58
*** browne has joined #openstack-meeting17:58
*** Apoorva_ has joined #openstack-meeting17:59
*** aranjan has quit IRC17:59
*** ajmiller has quit IRC18:00
bretontime?18:00
henrynashabout 7pm, guv18:00
*** ajmiller has joined #openstack-meeting18:00
*** samleon has joined #openstack-meeting18:00
*** pabelanger has left #openstack-meeting18:00
bretontime!18:00
stevemaro/18:00
lbragstado/18:00
stevemarmeeting time!18:00
stevemarget in here! ajayaa, amakarov, ayoung, breton, browne, crinkle, claudiub, davechen, david8hu, dolphm, dstanek, edmondsw, gagehugo, gyee, henrynash, hogepodge, htruta, jamielennox, jaugustine, joesavak, jorge_munoz, knikolla, lbragstad, MaxPC, morgan, nkinder, notmorgan, raildo, rodrigods, rderose, roxanaghe, samleon, samueldmq, shaleh, stevemar, tsymanczyk, topol, vivekd, wanghong, xek18:00
amakarovo/18:00
*** raildo has joined #openstack-meeting18:00
roxanagheo/18:00
browneo/18:00
*** rloo has left #openstack-meeting18:01
gagehugoo/18:01
raildoo/18:01
stevemar#startmeeting keystone18:01
openstackMeeting started Tue Jul 12 18:01:09 2016 UTC and is due to finish in 60 minutes.  The chair is stevemar. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
jaugustineo/18:01
*** openstack changes topic to " (Meeting topic: keystone)"18:01
openstackThe meeting name has been set to 'keystone'18:01
knikollao/18:01
stevemarof course they are testing the fire alarm now...18:01
nk2527howdy18:01
bknudson_hi18:01
dstaneko/18:01
henrynashstevemar: pardon? can;t hear you18:01
rderose_o/18:01
stevemar\o/18:01
*** azbiswas_ has quit IRC18:01
samueldmqhey folks o/18:01
*** sripriya has joined #openstack-meeting18:02
*** shaohe_feng has quit IRC18:02
gagehugohi18:02
*** azbiswas has joined #openstack-meeting18:02
*** jamielennox has joined #openstack-meeting18:02
*** sripriya has left #openstack-meeting18:02
stevemarsilenced it18:02
stevemarokay, let's go!18:02
lamthello18:02
*** shaohe_feng has joined #openstack-meeting18:02
stevemarlamt: hey!18:02
stevemaragenda link: Newton-2 is being cut this week18:02
stevemarerr18:02
stevemaragenda link: https://etherpad.openstack.org/p/keystone-weekly-meeting18:02
*** azbiswas has quit IRC18:02
stevemarcopy paste fail18:02
gyee\o18:02
*** Apoorva has quit IRC18:03
stevemarfun and full meeting today!18:03
stevemarso many topics18:03
stevemar#topic Newton-2 is being cut this week18:03
*** openstack changes topic to "Newton-2 is being cut this week (Meeting topic: keystone)"18:03
stevemarthis is just an update18:03
stevemarfriday we will propose our newton-2 driver18:03
stevemarno serious bugs so far18:03
*** Leo_ has joined #openstack-meeting18:04
stevemari bumped the following blueprints to newton-3: I have bumped the following blueprints: pci-dss, microversions, schema-validation, project-tree-deletion18:04
stevemarThe credentials-encryption blueprint is the only one left targeted for newton-2: https://review.openstack.org/#/c/317169/18:04
stevemarand it could use some eyes... dolphm ^ nonameentername ^18:04
nisha_o/18:04
stevemarthere were no new specs that landed last week (henrynash's is still pending)18:05
stevemarany questions / comments?18:05
samueldmqstevemar: hmt spec ?18:05
*** akuznetsov has joined #openstack-meeting18:05
stevemarsamueldmq: yes, that is henrynash's that i was referring to18:06
samueldmqgotcha18:06
stevemarbut it's not approved, we agreed to wait til midcycle to discuss18:06
henrynashstevemarL indeed18:06
stevemaroh breton had a spec approved, can you create a blueprint for it and target newton-3?18:06
* samueldmq nods18:06
bretonstevemar: yep18:07
stevemarbreton: thank you!18:07
stevemarnext topic ?18:07
*** amotoki has quit IRC18:07
*** lpetrut has joined #openstack-meeting18:07
*** eharney has quit IRC18:08
stevemar#topic keystone mascot/logo18:08
*** openstack changes topic to "keystone mascot/logo (Meeting topic: keystone)"18:08
lbragstadi think dstanek had a suggestion for our mascot...18:08
stevemarthis one is bound to be fun18:08
stevemarthere is a mailing list topic about it: http://lists.openstack.org/pipermail/openstack-dev/2016-July/099046.html18:08
nisha_:D18:08
stevemarThe foundation wants consistent logos from each openstack project/service, they're taking suggestion based on things in the natural world: an animal, fish, plant, or natural feature such as a mountain or waterfall. A professional illustrator will be creating them for all projects18:08
henrynashi added a few suggestions :-)18:08
stevemari think it's a great idea18:09
rderose_++18:09
stevemarDeadline is July 27th18:09
stevemarInfo: http://www.openstack.org/project-mascots18:09
stevemarSuggestions: https://etherpad.openstack.org/p/keystone-mascot18:09
raildo#link https://www.youtube.com/watch?v=LOdsuNr2T-o for more informations18:09
dstaneklbragstad: i'm pretty sure it wouldn't be allowed :-)18:09
stevemarawww, sorry to whoever recommended fluffy, only *real* things are allowed18:09
stevemarso no unicorns, dragons, 3 headed dogs, etc :)18:10
gyeepikachu?18:10
amakarovstevemar: A big fat burocrat sitting behind his desk!18:10
dstanekwhat about a wombat?18:10
stevemarCan my mascot be an imaginary animal/feature?18:10
stevemarNo. (Dragons, unicorns, centaurs, etc., are excluded.)18:10
stevemaramakarov: are you calling me that or is that a logo suggestion? :]18:11
bknudson_Do wombats actually exist?18:11
*** elopez__ has joined #openstack-meeting18:11
dstanekwe nicknamed a project wombat because it looks cool, but can also stand for 'waste of money brains and time' - management didn't know the second part18:11
*** sdake_ has joined #openstack-meeting18:11
amakarovstevemar: Are you sitting behind a buro? ;)18:11
lbragstaddstanek lol18:11
*** jamesmcarthur has joined #openstack-meeting18:11
dstanekunicorns exist18:12
samueldmqyeah, there are many in Brazil18:12
*** shaohe_feng has quit IRC18:12
gyeedstanek, whatever you are smoking, I want some of that18:12
dstaneknext topic!18:12
lbragstadwhat about the loch ness monster18:12
stevemaroh i like the turtle idea18:12
*** andymaier has quit IRC18:12
dstanek....or i will waste all your times18:12
*** ajmiller has quit IRC18:13
stevemaranyway, please add +1's or i'll send out a survey soon18:13
*** shaohe_feng has joined #openstack-meeting18:13
*** ajmiller has joined #openstack-meeting18:13
amakarovstevemar: http://www.stihi.ru/pics/2015/10/23/5845.jpg18:13
stevemarthats me!18:13
stevemarhehe18:13
samueldmqlol18:14
*** mickeys has joined #openstack-meeting18:14
stevemaralright, so please add suggestions to the etherpad18:14
*** elopez_ has quit IRC18:14
*** banix has joined #openstack-meeting18:14
stevemari'll send out a poll EOW to anyone who has had a patch land this release or last18:14
*** gouthamr has quit IRC18:14
notmorganI hear pokemon are real gyee,you just need an app on your phone to see them.18:14
stevemarif i can figure that out :P18:15
dstanektrolls under a bridge18:15
stevemarnext topic, should be quick18:15
bretonoh these non-tech topics18:15
notmorganmay i recommend a "keystone" animal18:15
gyeenotmorgan, I know! :-)18:15
stevemarbreton: they get more participation :P18:15
notmorganlook it up :)18:15
stevemar#topic Keystone API sprint18:15
*** openstack changes topic to "Keystone API sprint (Meeting topic: keystone)"18:15
stevemarit's tomorrow!18:15
amakarovnotmorgan: squeezed Scrappy from Ice Age? ;)18:16
stevemardetails here: https://etherpad.openstack.org/p/keystone-api-sprint18:16
samueldmqnotmorgan: hmm, looks like there is something called "keystone species"18:16
samueldmq:)18:16
stevemari'll add a google hangout link to the etherpad18:16
samueldmqoops, topic changed, sorry18:16
notmorgansamueldmq: yes.18:16
stevemaryou can see the APIs are being pulled from the keystone repo now18:16
*** toddjohn has quit IRC18:16
stevemarlet's remove them from the keystone-specs repo, and have a single source of truth18:17
*** toddjohn has joined #openstack-meeting18:17
samueldmqstevemar: ++18:18
stevemarlooking forward to it18:18
samueldmqstevemar: a good thing is that the code merges with the API change18:18
stevemar#topic Midcycle sprint agenda18:18
*** openstack changes topic to "Midcycle sprint agenda (Meeting topic: keystone)"18:18
stevemarsamueldmq: yep18:18
samueldmqas separate from the spec, so the code *always* match the API docs18:18
stevemarmidcycle is coming up: https://etherpad.openstack.org/p/keystone-newton-midcycle18:18
stevemarkeep the etherpad for the agenda, use the wiki to find information about the location and such18:19
*** anilvenkata has joined #openstack-meeting18:19
stevemarit'll be fun to see everyone soon!18:19
*** dbecker has quit IRC18:19
stevemari'll cancel next weeks meeting since we'll be traveling18:19
*** tonytan4ever has joined #openstack-meeting18:20
stevemarno questions, good, got through all this in 20 minutes!18:20
stevemar#topic microversions18:20
*** openstack changes topic to "microversions (Meeting topic: keystone)"18:20
stevemarhenrynash: ^18:20
henrynashok  right18:20
stevemarbreton: you have your wish :)18:20
henrynashso we merged a spec for this…but questions is…should we do it anyway….or only if we have a chnage to the API that needs it?18:21
samueldmqI think we should start with a real use for it18:21
henrynash(however, you *could* argue that any change to the API should be microversioned, even teh addtion of a new attribute)18:21
samueldmqotherwise seems unnecessary ?18:22
henrynashlike rderose’s password_valid_to attribute18:22
*** shaohe_feng has quit IRC18:22
rderose_* password_expires_at :)18:22
rodrigodsshould be used only if it is impossible to keep API compatbility without it18:22
dstaneki don'18:22
henrynashoops, sorry18:22
bretonstevemar: huh?18:22
dstanekt think adding should be microversioned18:22
*** shaohe_feng has joined #openstack-meeting18:23
*** karthikp_ has joined #openstack-meeting18:23
dstaneki don't think it would be bad to start supporting it now. that way we get it in and get some experience before we're under the gun18:23
jamielennoxso we've always had the incrementing API version, just noone really uses it18:23
stevemarbreton: we're finally on a technical topic :)18:23
knikolladstanek: ++18:23
samueldmqwhen we add we create a new version anyways (keystone 3.6, 3.7 and so on)18:23
*** aranjan has joined #openstack-meeting18:23
henrynashjamielennox: yep…and there is no way of asking for an API for any other version that the current one18:23
topolo/ catching up18:24
jamielennoxi'm not sure anyone would use the microversions either unless we had a reason people had to for different behaviour18:24
samueldmqhenrynash: jamielennox but generally changes that add things are backward compat18:24
jamielennoxhenrynash: well it means that every new addition to the API has been optional, the old behaviour is just not adding the new options18:24
samueldmqso new arguments are optional making it still possible to use an old version...18:24
gyeeI don't think OCLI have a generic way to facilitate microversion right now18:25
bknudson_is the change to add password_expires_at backwards compatible? If I start sending that to an old keystone it's not going to work as expected.18:25
stevemargyee: true18:25
jamielennoxbknudson_: that could be argued for every API change > 3.018:25
gyeethere will be a whole bunch of changes, including the way we load the plugins18:26
henrynashsamueldmq: … and a on old client would get slight different things back if they spoke to an old and a new server at the moment18:26
samueldmqhenrynash: speaking to 2 different versions of keystone ?18:27
samueldmqthe same client? that seems odd18:27
dstaneksamueldmq: i do it all the time18:27
bknudson_for example is_domain on projects... that would break using old keystone.18:27
*** mriedem1 has joined #openstack-meeting18:27
henrynashbknduson:_: yep18:27
*** dmorita has quit IRC18:27
*** anilvenkata has quit IRC18:27
*** elopez_ has joined #openstack-meeting18:28
samueldmqhmm, so other projects can't decide whether is_domain is available or not ... e.g if version is 3.6 then is_domain exists18:28
henrynashsmaueldmq: imagine access differnet pubcl cloud kestones with agiven client, how would you know what you would get18:28
samueldmqbut there is no way to differentiate things inside 3.x18:28
bknudson_you can get the version from keystone.18:28
*** Apoorva_ has quit IRC18:28
rderose_bknudson: password_expires_at is only returned in the response object18:28
rderose_bknudson: so response now has the new attribute, but not allowed in the request18:28
samueldmqbkeller`: you're correct18:28
*** Apoorva has joined #openstack-meeting18:28
stevemari don't think we've thought about how to fully use microversions end to end18:29
*** singhj has quit IRC18:29
stevemarosc doesn't have support for it :(18:29
*** mriedem2 has joined #openstack-meeting18:29
stevemarso how are keystone users going to take advantage of microversions18:29
henrynashstvevemar: not generic support, no18:29
*** mriedem has quit IRC18:29
*** eharney has joined #openstack-meeting18:29
*** agireud has quit IRC18:30
jamielennoxi realy don't think it's something that should ever be exposed to users via OSC18:30
*** elopez__ has quit IRC18:30
dstaneki would really like to start baking in the support first and before we expose things to the end user.18:30
jamielennoxbut i'm pretty sure i lost that18:30
dstaneklots of details need to be looked at...how do have support different validation for different versions...etc18:30
henrynashdstanek: that’s kind of my feeling…..18:30
samueldmqdstanek: ++18:30
stevemaryep, thats what i was referring to18:31
samueldmqotherwise we endup as driver versioning18:31
*** nisha_ has quit IRC18:31
*** agireud has joined #openstack-meeting18:31
bknudson_doesn't sound like we have an immediate need for microversions so let's not add the complexity18:31
samueldmq(which we are droping support now)18:31
stevemaragreed18:31
stevemarbknudson_: that somewhat brings up the next topic18:32
*** mriedem1 has quit IRC18:32
rderose_bknudson_++18:32
bknudson_the next person to propose a backwards-incompatible change is going to have technical debt to deal with18:32
gyee++18:32
henrynashok, so general feelin is..whait till we nned it18:32
bknudson_and hopefully we can get them to pay down the debt rather than just adding more.18:32
*** shaohe_feng has quit IRC18:32
*** sdake_ has quit IRC18:32
stevemarhenrynash: cue the topic change?18:32
henrynashyep18:32
dstanekfwict keystone have never been backward compatible between releases18:32
jamielennoxyep, i don't think we need it yet18:32
samueldmq++18:33
stevemar#topic Booleans or key-only query attributes in our Identity spec18:33
*** openstack changes topic to "Booleans or key-only query attributes in our Identity spec (Meeting topic: keystone)"18:33
*** shaohe_feng has joined #openstack-meeting18:33
*** Sukhdev has joined #openstack-meeting18:33
*** sdake_ has joined #openstack-meeting18:33
dstanekthat's a little scarry...(to wait)...but alright18:33
notmorgandstanek: fwiw, people have run keystone with older openstacks usually if they upgrade one component18:33
notmorganvs. all18:33
henrynashok, query attributes as booleans18:33
notmorganwe are mostly compatible in most cases.18:34
henrynashso we have mixture in our API18:34
bknudson_great, now we're going to find out we need microversion.18:34
henrynashsome are key-only, some are booleans (where we expect ‘0’ for flase)18:34
*** mriedem2 is now known as mriedem18:35
rodrigodsbooleans are the "more" correct18:35
henrynashthe api guidlines group are discussing this, but no conclusion18:35
rodrigodsat least, for the API spec18:35
jamielennoxplease go booleans18:35
topolplease keep interoperability in mind as we discuss things like microversions, etc18:35
gyeewhere's the API working group when we need them?18:35
jamielennoxi really dislike the raw flag, particularly if it then doesn't check like ?nocatalog=0 for false18:35
gyeethis is API consistency matter18:35
henrynashif the API working have a leaning, it appears to be for booleans rather than key-only18:35
rodrigodsgyee, yes... but we started using key-only18:35
notmorganas long as you don't change that "0" works if it works today18:36
gyeeI mean guidelines should come from API working group18:36
notmorganagain, don't break backwards compatibility18:36
rodrigodsand then realised they are not so great18:36
gyeeI don't care what it is so as long as it is consistent for ALL APIs18:36
notmorganyou can prefer booleans18:36
notmorganut if 0 works today, maintain it18:36
rderose_gyee++18:36
bknudson_I'd prefer no booleans but instead essentially enums18:36
bknudson_e.g. ?catalog=none18:36
notmorganbknudson_: i like that the best.18:37
dstanekwhen we say boolean we are talking 'false' instead of 0?18:37
rodrigodsbknudson_, ++ not "booleans" but key/value pair18:37
notmorganbut again, if we support it today, don't break it.18:37
stevemarwhat does the API working group recommend?18:37
notmorganalso do not make a config flag that changes behavior.18:37
henrynashthe challenge for booleans is that there isn’t really a standard for what should match true/false as aI said we chsoe ‘0’ for false and anyting eles mans true (including myvalue=’false’)18:37
rodrigodskey-only generates weirdness like: https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/base.py#L357-L36418:37
lbragstadthere also isn't a python library to convert key/value query strings, is there?18:38
rodrigodshenrynash, that challenge was introduced by key-only18:38
bknudson_requests or our crappy library not supporting key-only is a poor argument.18:38
*** asettle has quit IRC18:38
dstaneklbragstad: sure is18:38
rodrigodslbragstad, sure18:38
rodrigodskey-only doesn't18:38
lbragstadah - gotcha18:38
notmorganalso shouldn't ?nocatalog18:38
notmorganjust work18:38
notmorganeven without a value?18:38
gyeenocatalog works18:39
raildonotmorgan, I believe so18:39
*** ivar-laz_ has joined #openstack-meeting18:39
notmorganso, key-only seems to be api breaking. fwiw18:39
gyeewhile we are at it, should names be case-sensitive? :-)18:40
samleon?include_names, without value still works, what's confusing is ?include_names=false, it returns true18:40
henrynashdolphm: you here  - I know you have some string feelings here…?18:40
lbragstadhenrynash dolphm is on vacation today i believe18:40
rodrigodsaccepting all kind of "positive" values with key-only was the first mistake18:40
*** vipulnayyar has joined #openstack-meeting18:40
notmorganit is easy to convert values to booleans fwiw18:40
rodrigodsbut now we need to be backwards compatible18:40
lbragstadso can we deprecate the use of key-only?18:41
jamielennox>>> parse.parse_qs('test=1&nocatalog')18:41
jamielennox{'test': ['1']}18:41
*** mohitmotiani has joined #openstack-meeting18:41
notmorgan{'false', False, 0, "0", None}[key.tolower()]18:41
bknudson_we can introduce a microversion to change the arguments18:41
henrynashlbragstad: with a microversion :-)18:41
lbragstadand introduce key/value instead?18:41
notmorganor well18:41
rodrigodsjamielennox, ++18:41
jamielennoxso it's not just a requests/client problem18:41
jamielennoxit means we have to scan the string manually18:41
notmorganor whatever. but you can check the string18:42
notmorganbasically make it a set.18:42
notmorganand lower it.18:42
henrynashnotmorgan: which is how I think I tried to write it orgionally way back when we first added passing filter queries down to SQL…but go shot down18:42
*** ivar-lazzaro has quit IRC18:42
*** shaohe_feng has quit IRC18:43
*** shaohe_feng has joined #openstack-meeting18:43
henrynashnotmorgan: what abour foreign languages? do we have support Non, Neit etc.?18:43
gyeehahah, nice one18:43
*** david-lyle has joined #openstack-meeting18:43
rodrigodslol18:43
notmorganhenrynash: we only support documented python falses.18:43
rodrigodsnão :)18:43
stevemarcan we not just document how it'll work if there's a key-only and deal with the technical debt18:43
gyeenocatalog=是18:43
notmorganit is all we can expect to support.18:44
*** ivar-laz_ has quit IRC18:44
rodrigodsstevemar, makes sense18:44
notmorganbut in either case, this is api incompatible change18:44
notmorganbut i'm tired of harping on this point18:44
henrynashnotmorgan: I agree with you (but not everyone did at the time)18:44
amakarovgyee: i18n for keys too! ftw ))18:44
bknudson_are there proposals for new query arguments?18:44
bknudson_how about document what should be done for new ones?18:45
notmorgangoing forward and new query argts we can be much more strict18:45
notmorganand we should be18:45
jamielennoxso we can't break backwards compat, future API should all use booleans18:45
notmorganjamielennox: yes.18:45
gyeelet me ask again, what is OpenStack API working group for?18:45
notmorganand we should be very explicit goring forward and very strict18:45
*** singhj has joined #openstack-meeting18:45
*** dmorita has joined #openstack-meeting18:45
*** ebalduf has quit IRC18:45
dstanekjamielennox: what is the value of a boolean? 0/1, 'false'/'true'?18:45
rodrigodsdstanek, 0/118:45
*** myoung|afk is now known as myoung18:46
bknudson_how about "maybe"?18:46
rodrigodshaha18:46
dstanek'roll dice'18:46
notmorganbknudson_: "sortof"18:46
jamielennoxdstanek: as dfeined by: https://github.com/openstack/oslo.utils/blob/master/oslo_utils/strutils.py#L11118:46
notmorganbknudson_: ?nocatalog=sortof18:46
*** AJaeger has joined #openstack-meeting18:46
* notmorgan stops joking18:46
bknudson_I'd be worried about using the library since they change the lib to add more and our API changes.18:47
amakarovshreddinger_arg=0/118:47
jamielennoxdstanek: not my favourite way to do it, but it's predefined18:47
notmorgantrue/false imo is the boolean i'd support18:47
jamielennox1/0 as what we would recomment18:47
jamielennoxrecommend18:47
dstanekjamielennox: is anything else false?18:47
notmorganbut 1/0 is also fine.18:47
bknudson_we should define what happens if the value is not one that's expected18:47
bknudson_e.g., maybe 40018:47
dstanek1/0 would be my preference....certainly for the docs even if we support other values18:47
notmorgani'd look at http spec/jaascript/rfcs for general consistency18:48
dstanekbknudson_: ++18:48
jamielennoxdstanek: you can strict=True18:48
henrynashok, so proposal is: 1) document how it works today (since I don’t think we really do that), and s2) omehow when you introce a new boolean define how it should work…which would be different exits booleans (yuk)18:48
*** piet has quit IRC18:48
*** spzala has joined #openstack-meeting18:48
amakarovbknudson_: why not 'true/yes' is TRUE, and FALSE - everything else?18:48
dstanekamakarov: i'd rather have a strict false value18:49
bknudson_OpenStack seems to be moving towards being less lenient.18:49
lbragstaddstanek ++18:49
notmorganbe strict / explicit18:49
notmorganother web services tend to not be "true" or "yes"18:49
rodrigodshttp://webmasters.stackexchange.com/questions/78512/how-to-fail-in-case-of-incorrect-uri-parameter18:49
notmorganthey tend to expect a single "true" value18:49
notmorganif boolean18:49
*** david-lyle has quit IRC18:49
stevemarnotmorgan: what if unspecified?18:49
dstanekotherwise we'll get in a situation where we want 'yes', 'no' or 'it depends' and we'll be talking about backward compatibility again18:49
notmorganstevemar: most apps throwout/ignore invalid params unless they are filters18:50
notmorganiirc18:50
*** mickeys has quit IRC18:50
rodrigodsfallback to default values18:50
jamielennoxi don't like to ignore things you don't understand, always better to error18:50
*** mickeys has joined #openstack-meeting18:51
stevemargot a point18:51
bknudson_we'll definitely need microversions if we don't ignore unexpected inputs18:51
amakarovrodrigods: the question I see, what if client passes "param=yep" and expects it treated as true18:51
stevemaryeah, can't start tossing up errors18:51
notmorganamakarov: just be clear going forward what is expected18:52
amakarovI'm agree about ignoring18:52
rodrigodsnotmorgan, ++18:52
notmorganamakarov: doesn't matter what the client does after that18:52
*** dmorita has quit IRC18:52
stevemarhenrynash: can you recap again, but include what happens if value is not present :)18:52
notmorganamakarov: if it doesn't conform ... it isn't valid18:52
*** spzala has quit IRC18:52
*** shaohe_feng has quit IRC18:53
samleonstevemar, if value not there, it will be true18:53
henrynashstevemar: so in today’s spec we have two different types of “booleans”…we weither say they are key-only (and no value is epcted) or “real” boolean18:53
amakarovnotmorgan: yes, the concern is: should we ignore the parameter of throw an error18:53
rodrigodsshould *always* be key/value18:53
*** asettle has joined #openstack-meeting18:53
gyeesamleon, I wish that how we count votes in election day :-)18:53
*** asettle has quit IRC18:53
*** rcarrillocruz has joined #openstack-meeting18:53
rodrigodsimo18:54
*** asettle has joined #openstack-meeting18:54
notmorganamakarov: specify for new params the response.18:54
henrynashif keyonly, then if it;s in there we say it is true, irrespective of value (if one was supplied018:54
samleongyee++18:54
dstanekamakarov: i would ingore unknows params, but 400 on know params with invalid values18:54
henrynashif boolean, if value is ‘0’ it is false, anything else is true18:54
stevemardstanek: +++++18:54
amakarovnotmorgan, dstanek: why? :)18:54
*** lbrune has joined #openstack-meeting18:54
dstanekamakarov: why which part?18:54
notmorganamakarov: because it's the common behavior18:54
notmorgango to any webapp18:55
notmorganpass random query args18:55
*** Ed___ has joined #openstack-meeting18:55
dstaneknotmorgan: ++18:55
notmorganthey are thrownout/mostly ignored18:55
amakarovdstanek: I mean: do we have some measurables to say: yes - this approach is true18:55
stevemarso let's live with the existing ones and document the behaviour that we want (ugh)18:55
*** mickeys has quit IRC18:55
henrynashso one challenge is that if we intrioduce the “new improved boolean”, that operates different to the old boolenas, it might be pretty confusing18:55
*** shaohe_feng has joined #openstack-meeting18:55
stevemarif we go forward with microversions, this'll be item #1 to fix :P18:55
bknudson_we could add a microversion and bring the existing behavior up to spec.18:55
*** spotz_zzz is now known as spotz18:55
bknudson_oops, behaviour18:55
dstanekamakarov: we will define what values are acceptable for true/false18:55
notmorganbknudson_: ++18:56
stevemarbknudson_: thanks for speaking canadian18:56
anteayaeh?18:56
gyeenice one18:56
stevemarjamielennox: you have 3 minutes18:56
henrynashstevemar: “document what we want”….you mean what we supprot today?18:56
jamielennoxoh, gah18:56
*** piet has joined #openstack-meeting18:57
*** aranjan_ has joined #openstack-meeting18:57
stevemarhenrynash: both, what we support today vs what we just agreed upon18:57
*** pabelanger has joined #openstack-meeting18:57
jamielennoxSo quickly i proposed https://review.openstack.org/#/c/339356/18:57
stevemar#topic Require auth_context middleware18:57
*** openstack changes topic to "Require auth_context middleware (Meeting topic: keystone)"18:57
stevemari don't see the issue with depending on auth_context18:57
jamielennoxit would make auth_context required in the pipeline and remove the last of the places where keystone again validates a token18:57
*** mohitmotiani has quit IRC18:58
gyeejamielennox, ++18:58
jamielennoxlooking around at how auth_context is used i think you would find a bunch of edge cases that fail if you don't have auth_context enabled today18:58
topoljamielennox waiting for the downside18:58
gyeedoes auth_context always need a token?18:58
gyeeit shouldn't18:58
stevemarnotmorgan: dolphm y'all are the history buffs here, any thoyghts?18:58
stevemaror even thoughts18:59
jamielennoxso mostly it's an awareness thing, i want everone to know it's happening and a chance to stop it if you know anywhere we will have problems18:59
*** akuznetsov has quit IRC18:59
amakarovjamielennox: according to the last phrase the solution looks like a workaround...18:59
bknudson_I think you're saying that auth_context is actually required now?18:59
henrynashI just raised the concern to make sure we’re not going to break any deployments18:59
gyeejamielennox, make sure token is NOT required18:59
*** aranjan has quit IRC18:59
jamielennoxgyee: it would be enforced in @protected18:59
gyeethat's good18:59
jamielennoxso it will only be required in places where you are already going to do a policy check18:59
stevemarlet's just to -keystone to continue19:00
stevemar#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Jul 12 19:00:07 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-07-12-18.01.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-07-12-18.01.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-07-12-18.01.log.html19:00
notmorganas long as it all continue to work.19:00
*** dmorita has joined #openstack-meeting19:00
fungiinfra team, ensemble!19:00
*** Ed___ has quit IRC19:00
*** gagehugo has left #openstack-meeting19:00
*** gagehugo has quit IRC19:00
*** ociuhandu has joined #openstack-meeting19:00
fungitoday's topics courtesy of clarkb, mtreinish, fungi, jeblair, anteaya, heidijoy, wznoinsk, pleia219:00
clarkbdoes that mean we sing?19:00
anteayaI am here19:00
anteayaha ha ha19:00
pleia2o/19:00
anteayaclarkb: what do you want to sing?19:00
rcarrillocruzo/19:00
fungiclarkb: clearly you should follow up to the barcelona singing thread on the ml19:00
*** dmorita has quit IRC19:00
notmorganfungi: ooh can i sleep instead then :P since i'm not on the list.19:01
*** samleon has quit IRC19:01
*** browne has left #openstack-meeting19:01
clarkbanteaya: whatever an ensemble sings19:01
pabelangerbeep boop19:01
anteayaha ha ha19:01
Zarao/19:01
notmorganpabelanger: robot?19:01
fungithe infra core dodecatet ensemble?19:01
ianwo/19:01
pabelangerwaiting for fungi to setup the game and reference voltron19:01
SotKo/19:01
jeblairnotmorgan: yeah, but i am, and i'm going to say your name ;)19:01
pabelangerstep-up*19:01
notmorganjeblair: crud.19:01
bkeroo/19:01
notmorganjeblair: i guess sleeping is right out19:02
notmorgan then19:02
zaroo/19:02
jesusauro/19:02
fungipeople seem to be around and paying attention already. also very full agenda (i doubt we'll get to it all but i'll try) so guess we can get started19:02
fungi#startmeeting infra19:02
openstackMeeting started Tue Jul 12 19:02:40 2016 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: infra)"19:02
openstackThe meeting name has been set to 'infra'19:02
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:02
fungi#topic Announcements19:02
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:02
fungi#info Reminder: late-cycle joint Infra/QA get together to be held September 19-21 (CW38) in at SAP offices in Walldorf, DE19:03
fungi#link https://wiki.openstack.org/wiki/Sprints/QAInfraNewtonSprint19:03
fungi#topic Actions from last meeting19:03
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:03
zaroGerrit hackathon is on same week!19:03
fungi#link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-07-05-19.02.html19:03
*** shaohe_feng has quit IRC19:03
fungithere were "(none)"19:03
clarkbzaro: at the asme place, see you there? :)19:03
fungi#topic Specs approval19:03
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:03
zaroi bee there!19:03
fungi#topic PROPOSED: Spec for testing Newton on Xenial transition (clarkb)19:03
*** openstack changes topic to "PROPOSED: Spec for testing Newton on Xenial transition (clarkb) (Meeting topic: infra)"19:03
fungi#link https://review.openstack.org/33790519:03
fungi#info Council voting is open on "Spec for testing Newton on Xenial transition" until 19:00 UTC, Thursday, July 1419:04
*** jaugustine has quit IRC19:04
*** henrynash has quit IRC19:04
funginote that's being proposed as a priority spec19:04
*** shaohe_feng has joined #openstack-meeting19:04
fungianything we need to say about it this week clarkb?19:04
fungiother than it's basically already underway19:04
*** mohitmotiani has joined #openstack-meeting19:04
*** gouthamr has joined #openstack-meeting19:04
*** toddjohn has quit IRC19:04
clarkbjust that there is also a zuul and nodepool change proposed that I should update the topics on and I am doing a ton of testing for tox things across the projects that run python-jobs in zuul19:04
fungicool19:05
clarkband other claenup stuff is shaking out of that like empty repos and repos missing tox.ini and so on19:05
clarkbso will likely transition to trying to clean that up post xenial switch19:05
clarkbits amazing what you find when you run all the tests in a giant loop :)19:05
fungiyeah, daunting!19:05
clarkbbut no major issues with xenial yet19:06
*** toddjohn has joined #openstack-meeting19:06
anteayathank you for dusting out the corners19:06
clarkba possible sqlite3 problem and nodepool is unhappy with the newer mysql19:06
*** toddjohn has quit IRC19:06
clarkbnotmorgan: ^ I think you have a change to address the nodepool thing?19:06
*** toddjohn has joined #openstack-meeting19:06
*** leeantho has quit IRC19:06
zarolooks like bindep is the trick to make this work however i don't see any examples of an actual others-requirements.txt file. can we add something that's definative?19:06
zaroi mean in the docs19:06
*** tellesnobrega_af is now known as tellesnobrega19:06
*** Guest39029 has quit IRC19:06
fungizaro: AJaeger has been proposing a bunch of them to projects so far, so get up with him when he's around19:07
*** prometheanfire has joined #openstack-meeting19:07
fungior i can find you some after the meeting19:07
zarocool.19:07
clarkboh right for python-jenkins19:07
clarkbI can help with that too19:07
fungithanks clarkb!19:08
fungi#topic PROPOSED: Firehose, a unified message bus for Infra services (mtreinish, fungi)19:08
*** openstack changes topic to "PROPOSED: Firehose, a unified message bus for Infra services (mtreinish, fungi) (Meeting topic: infra)"19:08
*** adiantum has quit IRC19:08
*** azbiswas has joined #openstack-meeting19:08
fungi#link https://review.openstack.org/32911519:08
*** sdake_ has quit IRC19:08
fungi#info Council voting is open on "Firehose, a unified message bus for Infra services" until 19:00 UTC, Thursday, July 1419:08
pabelangerI am excited for this19:08
fungifun side project i promised to help mtreinish with19:08
fungidon't really need to discuss it in meeting unless there are serious concerns with it at this point19:08
pleia2my questions are already addressed in the spec, so yay exciting19:09
fungibut please review. we're submitting a talk for the upstream dev track about it19:09
*** timcline has quit IRC19:09
rcarrillocruzi'm very intrigued what things we'll be able to do with it :-)19:09
*** timcline has joined #openstack-meeting19:10
fungi#topic Priority Efforts: Zuul v3 and Nodepool+Zookeeper (jeblair)19:10
*** openstack changes topic to "Priority Efforts: Zuul v3 and Nodepool+Zookeeper (jeblair) (Meeting topic: infra)"19:10
fungii guess i should have listed Shrews there as well19:10
jeblairprepared text bomb to save time:19:10
*** nadya has joined #openstack-meeting19:10
fungi(consider yourself pinged!)19:10
jeblairi think the zuulv2.5 work is stable now, and i and some other folks are focusing significantly on zuulv3 now.  we're setting an ambitious goal of having enough done to do serious migration work by the time of the infra/qa latecycle.19:10
jeblairi'm volunteering to help people find things to work on in v3 -- here's what people are working on now19:10
jeblairShrews is working on zookeeper for nodepool, which i consider in the critical path for v319:10
jeblairnotmorgan is working on converting zuul to py3 so that we can have nice websockets and console streaming19:10
jeblairi'm working on the mind-bending configuration changes in the v3 spec19:10
jeblairjhesketh is working on forward-porting some of the stuff we learned about ansible in v2.519:10
jeblairmordred is working on figuring out how we can securely run jobs that are native ansible19:10
jeblairso if you want to pitch in or follow any of those efforts, those are the folks to talk to19:11
jeblairif you have significant time and ability to contribute to zuulv3, let me know and i can find something for you19:11
jeblairif you are looking for smaller things, then at this point, probably helping review those efforts would be best,19:11
jeblairor, alternatively, i have been sprinkling the code with lots of "TODOv3" items -- many of those could probably be worked in smaller chunks (they have my name on them, but that just means i have to explain what they mean, not that i have to do them)19:11
*** elopez__ has joined #openstack-meeting19:11
fungi[bam]19:11
jeblair(also, i'm stuffing my face with a sandwich, so that helps)19:11
clarkbjeblair: can we also tack on there "fix floating ip support in nodepool"19:11
clarkbits not directly related but is important because we have ltos of users of nodepool that may not be able to use provider nets19:12
fungii have doubts that fip support in nodepool is tied to zookeeper19:12
notmorganso fwiw19:12
clarkbit isn't19:12
jeblairclarkb: s/nodepool/openstack/? :)  .... but er, what's that about?19:12
fungibut yeah, that's something that can be worked on regardless i'm sure19:12
notmorganthe py3 stuff, zuulv3 will not be py27 compat.19:12
clarkbjeblair: well that too, but we know that nodepool can be made to work better bceause it did work better in the past19:12
*** vishwanathj has quit IRC19:12
notmorganwe will be dropping (currently planned) py27 support19:12
clarkbjeblair: but recent chagnes have been a major regression in the reliability even though things weren't perfect before19:13
pabelangerI'm happy to help get our zookeeper cluster online. https://review.openstack.org/#/c/324037/ adds a single instance to nodepool.o.o but wonder if we should expand it to the full cluster out of box19:13
rcarrillocruzjeblair: i'm happy to get streams of work19:13
*** vishwanathj has joined #openstack-meeting19:13
jeblairpabelanger: i'd like to just run one zk on nodepool.o.o19:13
rcarrillocruzso i'll follow up with people you mentioned or feel free to ping me later with whatever you think i could work on19:13
*** jamielennox has left #openstack-meeting19:13
*** azbiswas has quit IRC19:13
pabelangerjeblair: then we are ready :)19:13
jeblairrcarrillocruz: cool, we'll chat later19:13
*** shaohe_feng has quit IRC19:13
fungiwe're mainly not impacted by the fip issues at this point because one of our fip-requiring providers went out of business, one switched to provider networks and one is offline19:14
*** elopez_ has quit IRC19:14
*** nadya has quit IRC19:14
fungibut presumably other users of nodepool are in situations where fip use is mandatory for silly reasons19:14
*** spzala has joined #openstack-meeting19:14
jeblairclarkb: this feels like a +mordred+Shrews conversation; mordred is not in a compatible tz atm19:14
clarkbok maybe we can pcik this up when mordred and shrews are in compatible timezones19:15
*** timcline has quit IRC19:15
jeblairyeah, let's pick this up later... but i agree, i don't want to be in a position where we have to turn down a cloud because fips dont work19:15
fungii think the fip takeaway (and i share clarkb's concern) is that we ought to make sure that new development on nodepool stuff doesn't cause us to forget that we still need to fix a use case we were supporting and severely regressed19:15
jeblair++19:16
fungiwe are technically turning down bluebox right now for that reason19:16
pabelangerI'd also be interested in a discussion to maybe convert a few of our JJB templates into ansible roles.  When time permits, maybe get a short list together19:16
*** shaohe_feng has joined #openstack-meeting19:16
pabelangeror ansible playbooks19:16
jeblairi hope the fix for that is in shade anyway19:16
jeblairso it should at least have a good api barrier19:16
mordredmorning all19:16
clarkbfungi: yup that19:16
bkeropabelanger: what's the impetus behind that?19:16
fungipabelanger: i'm hoping that i can pitch in on the jjb->ansible conversion effort when zuul v3 draws closer19:16
pabelangerbkero: we won't have JJB for zuulv319:17
bkeroAh, makes sense19:17
clarkbpabelanger: you can likely automate/compile the vast majority to start19:17
clarkbpabelanger: shell builder becomes ansible shell module19:17
jeblairfungi, pabelanger: yeah, i'm hoping we can do a lot of that closer to the end -- maybe during the latecycle meetup.  but starting to poke at it a little may help inform development/testing19:17
clarkband so on19:17
*** gaso84ne has joined #openstack-meeting19:18
fungicool, anything else on the zuul v3 and nodepool+zookeeper topic?19:18
jeblairclarkb: there's two forks -- how to convert all of our jobs, but also, how would we redesign the jobs with the additional tools we have19:18
bkeroMoving to ansible should get us better resources to analyze run failures tool \o/19:18
pabelangerclarkb: Yup, if we get some good working examples, other projects can be quickly bootstrapped for the conversion19:18
*** gyee has quit IRC19:18
*** obondarev has joined #openstack-meeting19:18
fungibkero: yep19:19
clarkbjeblair: ya definitely don't want to stick to the jjb model long term if we can make things better19:19
pabelanger++19:19
jeblairfungi: the only other point i wanted to raise is....19:19
fungiaha, see it in the agenda now19:19
jeblairthat i had been thinking we would drop dedicated zuul mergers in v3, in favor of combined ansible merge/launch workers19:19
jeblairbut after writing 340597, i think zuul may need some horsepower to gather proposed config changes19:20
jeblairand i'm wondering if having a dedicated merger option might be a good idea19:20
fungiit does seem reasonable to make the merge work independently scalable from the job runnning19:20
jeblairi honestly don't know, but it's a potentially significant deployment difference19:20
fungione is a per-changeish/enqueue workload, the other is a per-job-run workload19:21
jeblairso i wanted to bring it up as something for folks to think about19:21
jeblairfungi: exactly -- and i'm wondering, can we skim off the top of the merge-launchers for that, or will it be too much...19:21
clarkbjeblair: the underlying concern being related to in project configs?19:22
jeblairfortunately, i hadn't gotten far in gutting them, so it's not too hard if we want to keep em around19:22
fungijeblair: i guess if the merge task is treated in the abstract like a kind of job, then maybe?19:22
jeblairclarkb: yes -- we need mergers to merge and read those files19:22
anteayawill this affect zuul downstream consumers?19:22
fungiso you have a "job" to create teh merge commits, and then your other jobs depend on that "job"19:22
*** ijw has quit IRC19:23
jeblairfungi: it's a bit less abstract than that because it happens before zuul decides what jobs to run19:23
fungiand i guess teh v3 ref push model does get simpler if the launcher has those commits locally on hand already19:23
jeblairfungi: but the main thing is that it's using *part* of the merger-launcher resources, but not as much as a real launched job19:23
fungijeblair: good point, since the merge commits reflect repo states that have job configuraiton in them19:23
*** shaohe_feng has quit IRC19:24
*** shaohe_feng has joined #openstack-meeting19:24
*** adiantum has joined #openstack-meeting19:24
fungioh, though one launcher would be generating the merge commits, other launchers might run the jobs?19:24
fungiso you'd still need to shuffle them around the network19:25
jeblairfungi: indeed.  so instead of that, we'd probably just end up merging commits more than once.  :(19:25
clarkbanteaya: yes the whiole thing is a large non backard compat change19:25
anteayaclarkb: okey dokey19:25
clarkbanteaya: so anyone downstream will need new configs and deployment stuff19:25
anteayaor can pin to v2.5 and stay there a while19:25
*** ajmiller has quit IRC19:25
*** prometheanfire has left #openstack-meeting19:25
jeblair(if we don't have dedicated workers, there is a small chance a merge-launcher could reuse a commit on hand, but we will be large enough that won't happen often)19:25
fungizuul 3.0.0 will be a major configuration, dependency and behavior change from <319:26
*** ajmiller has joined #openstack-meeting19:26
anteayaack19:26
jeblairanteaya: yeah, so all this is happening in a branch; deployment of it will be a very considered affair later on19:26
jeblairfungi: (that's eot from me)19:26
anteayaah okay, sorry, I'll table my question19:26
*** sdake_ has joined #openstack-meeting19:26
*** mikelk has joined #openstack-meeting19:26
fungianybody else have questions on this work before i move on to general meeting topics?19:26
*** mohitmotiani has quit IRC19:27
fungiWhat is the current status of the gerrit its-storyboard plugin? (anteaya)19:27
fungier19:27
fungi#topic: What is the current status of the gerrit its-storyboard plugin? (anteaya)19:27
*** openstack changes topic to ": What is the current status of the gerrit its-storyboard plugin? (anteaya) (Meeting topic: infra)"19:27
fungi#undo19:28
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x7f5bc0869990>19:28
fungi#topic What is the current status of the gerrit its-storyboard plugin? (anteaya)19:28
*** openstack changes topic to "What is the current status of the gerrit its-storyboard plugin? (anteaya) (Meeting topic: infra)"19:28
*** trandles has joined #openstack-meeting19:28
fungimust be time for my afternoon coffee19:28
anteayathis is a question for zaro19:28
*** ebalduf_ has quit IRC19:28
*** mohitmotiani has joined #openstack-meeting19:28
anteayaso there are some patches: https://review.openstack.org/#/q/topic:its-storyboard19:28
*** ihrachys has quit IRC19:28
fungi#link https://review.openstack.org/#/q/topic:its-storyboard19:28
anteayaand some look ready to go save for some reviews19:28
anteayazaro: do you just need reviews at this point or do you need anything else?19:28
zaroyes, they are all ready19:29
zarojesusaur says change https://review.openstack.org/#/c/340605/  is failing due to https://review.openstack.org/#/c/340529/19:29
anteayawell the one system-config patch depends on two puppet-gerrit patches, one of which is failing lint tests19:29
zaroi really have no idea if that's true or not19:29
fungii guess it would be good to go ahead and get those through. i should probably have put this under Priority Efforts: A Task Tracker for OpenStack19:29
*** sambetts is now known as sambetts|afk19:29
anteayazaro: this has a lint failure: https://review.openstack.org/#/c/331523/19:30
anteayaah sorry, I'll put it there next time19:30
zaroyes, 340529 is causing that lint failure according to jesusaur19:30
*** julim has quit IRC19:30
anteayazaro: ah thank you19:30
zarobut he also says he wasn't able to test it so i'm not sure whether it's a fact19:31
anteayaso nibalizer crinkle rcarrillocruz could anyone spare some puppety type review time for https://review.openstack.org/#/c/340529/19:31
anteayaand I guess that is it for this topic, thank you19:31
anteayaunless you have more zaro19:31
zaronope, other than it's been testing with review-dev & sb-dev19:31
zaroseems to be working19:32
Zara\o/19:32
anteayawonderful, thank you19:32
anteayathanks fungi19:32
SotKthat's good news, thanks for working on this zaro :)19:32
fungiawesome19:32
fungi#topic Mascot/logo for your project (heidijoy, fungi)19:32
*** openstack changes topic to "Mascot/logo for your project (heidijoy, fungi) (Meeting topic: infra)"19:32
fungi#link http://lists.openstack.org/pipermail/openstack-dev/2016-July/099046.html19:32
fungijust a heads up that the foundation wants some consistent logos/mascots for each project team, primarily for them to use on foundation sites, but they have an illustrator on board to work with us on the design and we can reuse the artwork for any other community things we want19:32
*** ronghui has quit IRC19:32
*** esker has joined #openstack-meeting19:33
fungii figure there are probably some on the team who have an affinity for this sort of bikeshed, so we can do that via ml or etherpad19:33
bkeroinfra badger?19:33
rcarrillocruzawww19:33
fungipreference?19:33
anteayawell we have had a gear19:33
pabelangeromfra animal19:33
Zarafungi's pet betta?19:33
* rcarrillocruz remembers pleia2 showing zuul mascot in some talk :D19:33
anteayathat was a pink dragon I think19:34
fungiyeah, pleia2's awesome mascot is disqualified for being a mythological creature19:34
*** ajmiller_ has joined #openstack-meeting19:34
rcarrillocruzhah19:34
pleia2it was a pink dragon19:34
*** shaohe_feng has quit IRC19:34
anteayafungi: what, there are rules?19:34
fungiapparently that's an important aspect for reasons i'm unable to entirely reconcile19:34
pabelangerocelot19:34
fungianteaya: see the linked e-mail for details19:34
*** shaohe_feng has joined #openstack-meeting19:34
bkeroIt's hard to get mythical creatures for the OpenStack field trip to the Sydney petting zoo19:35
fungibut anyway, i don't want to take up meeting time soliciting mascots, just to figure out where we should coordinate ideas and come to some consensus (for those who care about it)19:35
anteayait just says "from nature"19:35
anteayait doesn't say no dragons19:35
persiaIt says "animal or natural feature" at http://www.openstack.org/project-mascots19:36
fungianteaya: touché. komodo dragon is probably already taken though19:36
anteayaI'll pick it up later, moving on19:36
anteayawe can try19:36
anteayaI'm arguing for dragon as a feature19:36
anteayaokay I'll stop19:36
*** Ed___ has joined #openstack-meeting19:36
*** annegentle has joined #openstack-meeting19:37
fungi#link https://etherpad.openstack.org/p/infra-mascot-ideas19:37
fungi#info post mascot ideas and discussion to the etherpad, and we'll have a vote in the meeting next week19:37
*** ajmiller has quit IRC19:38
fungior we can decide in next week's meeting to do a civs poll instead19:38
fungiwhatever19:38
fungianyway, week for feedback19:38
fungi#topic Intel/Mellanox Barcelona talk proposal: Openstack CI - testing SRIOV/NFV (wznoinsk)19:38
*** openstack changes topic to "Intel/Mellanox Barcelona talk proposal: Openstack CI - testing SRIOV/NFV (wznoinsk) (Meeting topic: infra)"19:38
fungiwznoinsk_: around>?19:39
fungii guess let's come back to this at the end if we still have time19:39
fungi#topic Translations Checksite status and call for help, now with more data! (pleia2)19:40
*** openstack changes topic to "Translations Checksite status and call for help, now with more data! (pleia2) (Meeting topic: infra)"19:40
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2016-July/004524.html19:40
*** vishnoianil has quit IRC19:40
pleia2mostly I just need some feedback here19:40
pleia2I outlined the issues we're having, hopefully clearly, in that email19:41
pleia2happy to have this discussion on list, I just need that to happen :)19:41
*** dmorita has joined #openstack-meeting19:41
*** Ed___ has quit IRC19:41
clarkbI'll admit to raeding the email and not knowign where to start19:41
fungiyep, so the primary issue is that redeploying devstack periodically is extremely failure-prone?19:41
*** adiantum has quit IRC19:42
*** ihrachys has joined #openstack-meeting19:42
rcarrillocruzyeah, i'm confused why devstack is needed19:42
fungispecifically deploying from master branch tip with most services (those getting active translations) enabled?19:42
clarkbfungi: and configuring the fakes on the backend I think19:43
fungircarrillocruz: well, we don't need devstack exactly, we just need running openstack services deployed from master branch tip, with accounts configured for translators to log into and check their applied translations19:43
rcarrillocruzwell19:43
pleia2yeah, so translations cleanly apply19:43
pleia2since they're also translating from dev19:43
rcarrillocruzthat looks like a job the launcher could help with19:43
rcarrillocruzi assume the issue is doing the initial boostrap of the 'cloud'19:43
rcarrillocruzprojects, users et19:43
rcarrillocruzc19:43
rcarrillocruz?19:43
clarkbrcarrillocruz: no I don't think so, that all works fine with devstack19:44
fungiyeah, we need to import/carry over the config19:44
*** sarob has joined #openstack-meeting19:44
rcarrillocruzso yeah, or no?19:44
clarkbcould we run it as a periodic zuul job on a dedicated static host?19:44
*** shaohe_feng has quit IRC19:44
*** dmacpher-afk has quit IRC19:44
fungido we also need to preserve database contents between redeploys?19:44
clarkbthen we don't have to worry about puppet or any of that19:44
*** shaohe_feng has joined #openstack-meeting19:44
pleia2the trouble is we're not really involving CI in this right now, since the in-progress translations come from Zanata, not git19:44
pleia2they only hit git when they reach 75% complete19:45
*** _sarob has joined #openstack-meeting19:45
pleia2fungi: no19:45
*** dmorita has quit IRC19:45
*** ociuhandu has quit IRC19:46
*** timcline has joined #openstack-meeting19:46
*** ronghui has joined #openstack-meeting19:46
fungiwell, we _could_ have a zuul job which does the devstack deployment and retrieves the translations i guess, with a static node as clarkb mentioned, though i'm not sure that changes the nature of the problem much19:46
clarkbfungi: it avoids the runtime issues19:46
rcarrillocruzyeah, i mean19:46
pleia2fungi: nods19:46
rcarrillocruzthe real issue is fragility of puppetry19:46
clarkbfungi: and uses the tools we expect to work all day19:46
rcarrillocruz?19:46
*** ociuhandu has joined #openstack-meeting19:46
pabelangerit would be cool if we could use selenium some how to long into devstack and take screenshots of the current pages, then store them for people to review19:46
pabelangerI have no idea how much work that is19:46
clarkbbasically trying to keep up with master of openstack is hard19:46
clarkbthe benefit of using the CI tooling is it by definition needs to keep up19:47
clarkbpabelanger: we already do that19:47
ianwcould you snapshot a .qcow2 that people run locally?19:47
clarkbpabelanger: in the horizon functional job19:47
pabelangerclarkb: really?19:47
pabelangerwow19:47
clarkbpabelanger: yup19:47
pabelangerTIL19:47
fungiproblem though is unreliability of devstack deploying, so whether it's puppet or ansible/shell doing that if we're reusing teh same environment it's hard to fall back to an old but working version19:47
pleia2clarkb: yeah, that's why I had my #4 in my email - we have this "make devstack every day" tooling, can we use it?19:47
*** spotz is now known as spotz_zzz19:48
*** dmorita has joined #openstack-meeting19:48
fungifor red/blue i guess we could deploy to alternating nodes and update dns, but we don't currently have any dns automation either19:48
pleia2ianw: most translators don't have access to the resources (and sometimes lack the expertise) to run such a thing, they need a hosted solution they can just log into with a web browser19:48
*** sarob has quit IRC19:49
fungiyep, which was basically the crux of the request from the translation team to start with19:49
fungirun something where we can demo our translations, because we can't all run openstack19:50
* pleia2 nods19:50
*** timcline has quit IRC19:50
pleia2I don't think we need to solve this in this meeting, but I could use one or two of you to hash over some options with19:50
fungiit boils down to a very constrained continuous deployment of openstack problem, but it is as noted still very hard to continuously deploy openstack from master with any real consistency19:51
clarkbfungi: it won't sovle anything to use the gate infrastructure but so much of that tooling is literally make devstack reliable19:51
*** adiantum has joined #openstack-meeting19:51
*** ebalduf has joined #openstack-meeting19:51
*** ebalduf has quit IRC19:51
fungiclarkb: yep, i think using the ci for this is a viable choice, it just wasn't what got chosen in the original spec and subsequently partially implemented19:51
*** dmorita has quit IRC19:51
ianwwell, i can help with devstack ... but yeah, devstack just isn't very good for keeping things running longer-term in a no-touch manner19:52
fungianyway, i can try to carve out some time to poke at this, though hopefully there are others with available time to help19:52
*** dmorita has joined #openstack-meeting19:52
pleia2I'm not traveling again until the end of the month, so just grab me whenever, I'm around19:52
*** maishsk has joined #openstack-meeting19:52
fungi#topic Make it more obvious that OpenStack source on GitHub is a mirror (pleia2)19:52
*** openstack changes topic to "Make it more obvious that OpenStack source on GitHub is a mirror (pleia2) (Meeting topic: infra)"19:53
*** dmorita has quit IRC19:53
fungithis will almost certainly eat up the remainder of the meeting time19:53
*** fawadkhaliq has quit IRC19:53
fungiwznoinsk_: if you're around, find us in #openstack-infra after the meeting19:53
rcarrillocruzpleia2: yeah, happy to help on ansible/puppet front19:53
pleia2we talked about this before the meeting a bit :)19:53
pleia2#link http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2016-07-12.log.html#t2016-07-12T18:35:1519:53
rcarrillocruzi need to really read the whole thing to understand the problems19:53
pabelangerI think the idea in general pleia2. Update the descriptions is a good first step I think19:54
pleia2rcarrillocruz: thanks, the spec + what we have in the puppet module is pretty comprehensive19:54
*** ijw has joined #openstack-meeting19:54
pleia2I've seen an increase in people submitting pull requests on github against OpenStack projects, about once a day19:54
pabelangers/think/like/19:54
*** shaohe_feng has quit IRC19:54
pleia2I think this is just an increase in popularity of github in general, but we don't have obvious blinking banners telling people not to do that19:54
*** johnthetubaguy-w has joined #openstack-meeting19:54
*** cody-somerville has quit IRC19:55
*** mikelk has quit IRC19:55
persiaJust a link to the cgit repo in the README is probably enough for most things.19:55
*** shaohe_feng has joined #openstack-meeting19:55
persiaPart of the issue is that github has better google-fu than cgit19:55
fungipersia: yep, and we do that, but this is solving the corner cases19:55
bkeroThere's always something like https://nopullrequests.appspot.com/19:55
*** flwang1 has quit IRC19:55
*** karthikp_ has quit IRC19:55
bkeropull request bot that closes them and leaves them a message about the proper place to submit patches19:55
fungibkero: we also automatically close all pull requests with a polite message19:55
pleia2bkero: we have one19:56
*** annegentle has quit IRC19:56
bkerooh cool19:56
pleia2but it makes people feel sad and angry19:56
rcarrillocruzyeah, iirc jeepyb does something like that19:56
pleia2they put in effort, just to be told "nope, go here"19:56
pabelangerYup, I can confirm the rage of closing a PR19:56
pleia2anyway, the point of this agenda item is to make sure it's worth my time and effort for a multi-prong approach to improve the situation19:56
pleia2as pabelanger said, maybe appending descriptions we sync with Read Only:19:56
anteayapleia2: what do you want to fix and do you think it will be fixable?19:57
fungias mentioned before the meeting, i'm in favor of doing whatever else is relatively easy and automated to help make this even more obvious. just be wary that we'll never cover 100% of people who don't read what's right in front of them nor people who get incredulous over the idea of using anything besides github19:57
pleia2also looking into adding a PR template explaining19:57
anteayaif you want to spend time doing this, I support you19:57
persiafungi: My suggestion is to have that near the top, rather than later on.  As an example, maybe replace "OpenStack Compute (Nova) http://openstack.org" with "OpenStack Compute (Nova) http://openstack.org https://git.openstack.org/cgit/openstack/nova/" or something.19:57
ZaraI feel like better contributors would be willing to understand, so I'd be wary of trying too hard to please the grumps19:57
pleia2Zara: agreed19:57
anteayabut I don't think we will reduce or eliminate people who have bad experiences19:57
pleia2it won't solve the problem, but I seek to reduce it as much as possible19:57
fungialso be aware that mass api operations against github are terribly slow and unreliable19:57
fungiwe used to update project descriptions via jeepyb/manage-projects19:57
fungiwe had to stop19:58
pleia2I didn't realize we had stopped19:58
pleia2/o\19:58
fungia couple years ago, yeah19:58
*** ihrachys has quit IRC19:58
pleia2alright, I'll see what's feasible for automation and report back in the form of patches and things19:58
clarkbit was making important ops like make project fail19:58
fungiyou can fairly reliably update _a_ project's description via the github api19:58
clarkbI think you get 5k requests per hour19:58
*** jamemcc has joined #openstack-meeting19:58
*** annegentle has joined #openstack-meeting19:58
*** ijw has quit IRC19:59
fungiif you try to update a hundred in a loop, you should expect it to not work so well19:59
jeblairfor a one time thing, i'm sure we can handle updating descriptions slowly19:59
*** Apoorva has quit IRC19:59
fungiand if you want to do all 1k+ of our repos in one go, brace yourself for disappointment19:59
*** eglynn has joined #openstack-meeting19:59
pleia2noted19:59
*** julim has joined #openstack-meeting19:59
*** hasharAway is now known as hashar20:00
fungiyep, that's basically my point. don't expect that we'll be able to dynamically adjust this at will. plan for it to be a manual update and for it to take a while20:00
anteayathanks for the meeting20:00
*** joehuang has joined #openstack-meeting20:00
fungithanks everyone!20:00
*** leeantho has joined #openstack-meeting20:00
fungi#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Jul 12 20:00:35 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-07-12-19.02.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-07-12-19.02.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-07-12-19.02.log.html20:00
ttxohai20:00
devanandao/20:00
mesteryo/20:00
amrith<cough>20:00
* bkero waves20:00
jamespageo/20:00
*** banix has quit IRC20:00
*** Apoorva has joined #openstack-meeting20:00
flaper87o/20:01
*** zeih has quit IRC20:01
ttxannegentle, dims, dhellmann, johnthetubaguy, mtreinish, thingee, mordred, morgan, russellb, sdague : around ?20:01
jroll\o20:01
dhellmanno/20:01
*** zhipeng has joined #openstack-meeting20:01
annegentleo/20:01
johnthetubaguy-wo/20:01
ttxwaiting for the 7th20:01
*** sdake_ has quit IRC20:01
dimso/20:01
* edleafe sips his coffee20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue Jul 12 20:01:40 2016 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
* johnthetubaguy-w sits on train waiting to loose signal20:01
*** openstack changes topic to " (Meeting topic: tc)"20:01
openstackThe meeting name has been set to 'tc'20:01
* flaper87 bows20:01
ttxHello everyone! Our agenda for today:20:02
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:02
ttxRemember to use #info #idea and #link liberally to make for a more readable summary20:02
ttx#topic Propose Stewardship Working Group (SWG)20:02
flaper87++20:02
*** openstack changes topic to "Propose Stewardship Working Group (SWG) (Meeting topic: tc)"20:02
ttx#link https://review.openstack.org/33789520:02
ttxamrith: care to introduce the topic ?20:02
amrithsure, thx ttx20:02
amrithin re: https://review.openstack.org/337895, the proposal for the SWG.20:02
amrithI took an action item to submit this proposal on behalf of a number of people, mostly20:02
amrithmembers of the TC, on the third day of the training we attended in Ann Arbor. A quick20:02
amrithsynopsis about that training; it was conducted at ZingTrain (http://www.zingtrain.com). The20:02
amrithtraining focused on a concept called 'servant leadership' which it turns out is surprisingly20:02
amrithwell applicable to the model of leadership in OpenStack.20:02
amrithOur feeling was that there was much that we could learn from this and that it was something20:03
amriththat we must investigate further, as a group, and not something that we could just discuss20:03
amrithand decide there as a small group.20:03
amrithWe therefore felt that it would be appropriate to setup an OpenStack20:03
amrithworking group that would make specific recommendations to20:03
amriththe TC, and that the TC could then deliberate and if20:03
amrithapplicable, adopt.20:03
*** saju_m has quit IRC20:03
*** ijw has joined #openstack-meeting20:03
flaper87#info this is an advisory group20:03
flaper87amrith: thanks for writing this down!20:03
Rockyg /me multitasks poorly20:03
amrith<sorry for the formatting>20:03
amrithI am happy to see that even in the drafting of this resolution, we have received and20:03
amrithincorporated input from jroll, johnthetubaguy, and eglynn. eglynn if you are here, I hope20:03
amriththe comment from dhellmann addresses your concern; the SWG is purely an advisory body, it20:03
amrithhas no authority to make decisions, merely make recommendations to the TC that the TC can20:03
amriththen deliberate and decide on a course of action.20:03
* johnthetubaguy-w makes happy noises in the general direction of that group and its intent20:03
amrithAll are welcome to participate. There's an OpenStack channel (#openstack-swg), there's a20:04
amrithweekly meeting that has been proposed (https://review.openstack.org/#/c/338134/) for20:04
amrithThursdays at 1800UTC. At this point, the time does not appear to be broadly acceptable, I20:04
amrithwill have to find an alternate time. This will likely result in a doodle20:04
*** banix has joined #openstack-meeting20:04
* Rockyg can't even type right20:04
amriththx to flaper87 for the #info20:04
amrith#link https://review.openstack.org/33789520:04
amrith#link https://review.openstack.org/#/c/338134/20:04
*** jamesmcarthur has quit IRC20:04
amrithThanks TTX. I'll shut up now and listen. Thoughts, comments, questions, ...20:04
*** pradk_ has joined #openstack-meeting20:04
flaper87unless someone has a strong opposition against this group, I think it's an "easy" one.20:04
*** shaohe_feng has quit IRC20:05
ttxneed to digest what you just pasted20:05
*** timcline has joined #openstack-meeting20:05
*** pabelanger has left #openstack-meeting20:05
*** mriedem1 has joined #openstack-meeting20:05
flaper87I really look forward to see what this group comes out with and to see the group grow20:05
ttxprotip: paste one line at a time and pretend you type superfast :)20:05
annegentlettx knows20:05
annegentle:)20:05
amrithI prepared a paste; among friends, no need to pretend :)20:05
ttxWe already have enough votes to pass this. Is there any question ?20:05
flaper87I'd love to see the knowledge in this group to be spread20:05
*** shaohe_feng has joined #openstack-meeting20:05
flaper87no objections or comments here20:06
dimsand recruit actively PTL(s), core(s) etc20:06
amrithdims, that is part of the plan20:06
*** jamesmcarthur has joined #openstack-meeting20:06
amriththere is a session proposed for summit20:06
amrith<shameless plug>20:06
dims++ amrith20:06
ttxLooks like the present membvers all voted for it anyway, so we won't have more questions20:06
amrithwhere we'd like to share more about the concept20:06
amrithand get more people involved.20:06
johnthetubaguy-wI want to help with that group, an awesome effort20:06
annegentleI like it, and can it then take on the work that ttx and flaper87 and I were going to do last week of coming up with more communications ideas?20:06
amrithis eglynn here?20:06
dhellmannI'm not sure how big we want this group to really be. At some point it will grow big enough to not be that productive.20:07
amriththx johnthetubaguy-w20:07
jrolldhellmann: true that20:07
*** ijw has quit IRC20:07
ttxlet's see how it goes20:07
dimsdhellmann : "Anyone20:07
dimsinterested in leadership, stewardship, and OpenStack is welcome to20:07
dimsjoin the working group."20:07
amrithone question for all; can we have the first meeting on thursday at 1800UTC20:07
amrithand figure out the best thing to do for schedule moving forward20:07
eglynnamrith: I am ... and TBH happier that the proposed WG is not restricted to the Ann Arbor training attendees20:07
ttxamrith: I won't be around, but don't let that stop you20:07
amrithor should I resort to a doodle?20:07
*** vipulnayyar has quit IRC20:07
jrollamrith: I'm free20:07
dhellmanndims : yes, though I don't know if we want to heavily recruit. the point was to have a small working group.20:08
johnthetubaguy-wdhellmann understand that concern it's totally valid, need to make progress, not just talk20:08
*** mriedem has quit IRC20:08
*** tonytan4ever has quit IRC20:08
mesteryeglynn: ++20:08
*** cody-somerville has joined #openstack-meeting20:08
dims++ johnthetubaguy-w dhellmann20:08
ttxAlright, I'll approve this now20:08
amriththx eglynn; wanted to make sure we closed the loop with you20:08
*** toddjohn has quit IRC20:08
flaper87dhellmann: true! The growth I'd love to see is more like new members coming and others passing the torch. I'd love to see the knowledge in the group to be shared and a process to exist.20:08
amrithdhellmann, will go ahead with first meeting20:08
eglynnamrith: thanks!20:08
* amrith shuts up20:08
flaper87eglynn: I don't think it was meant to be like that but I'm glad you commented. That helps clarify it for others too20:08
dhellmannamrith : so the 14th at 1800 UTC?20:08
amrithdhellmann, correct20:08
RockygThanks!  sounds rally healthy for OpenStack20:08
amriththursday (my math was bad; i said 15th earlier)20:09
amrith14th, 1800UTC20:09
* gothicmindfood high fives everyone20:09
ttx#info first meeting Thursday Jul 14 at 1800 UTC20:09
flaper87amrith: I don't think I'll be able to make it at that time but I'll follow it on ML and logs20:09
amrithas currently proposed in https://review.openstack.org/#/c/338134/20:09
ttxAlright approved20:09
*** csomerville has joined #openstack-meeting20:09
amriththx ttx20:09
flaper87w000h000020:09
ttxLet's move on20:09
jrollgothicmindfood: ^520:09
ttx#topic Add Juju Charms for OpenStack20:10
*** openstack changes topic to "Add Juju Charms for OpenStack (Meeting topic: tc)"20:10
amriththx gothicmindfood ...20:10
annegentlejroll: nice20:10
ttxgothicmindfood: ^520:10
ttx#link https://review.openstack.org/22479720:10
*** mriedem has joined #openstack-meeting20:10
ttxQuick bit of history, this was originally proposed in September 201520:10
ttxIt was rejected back then due to absence of prior activity.20:10
* johnthetubaguy-w wonders how long he will have data know :( stupid trains20:10
ttxThen it was reproposed in May 2016, but since then we clarified the licensing requirements and the Juju Charms were not compatible20:10
ttxThis is now fixed and "third time's a charm"20:10
dhellmannthird time's the charm?20:10
dhellmannheh20:10
ttx(slow clap)20:10
ttxdhellmann: I win20:10
* dhellmann yields20:11
* Rockyg *groans*20:11
edleafettx: did you reject them twice just so you could write that? :)20:11
ttxQuestions ?20:11
ttxedleafe: Noooooo20:11
* flaper87 can tell ttx is laughing right now20:11
*** dmorita has joined #openstack-meeting20:12
annegentlegroaaan20:12
flaper87it looks good to me!20:12
dimslol20:12
*** karthikp_ has joined #openstack-meeting20:12
annegentleyou win at #dadjoke ttx20:12
*** mriedem1 has quit IRC20:12
*** carolbarrett has joined #openstack-meeting20:12
*** cody-somerville has quit IRC20:12
ttxjamespage: My main objection at this point is that my spam filter tags all [charms] emails as [SPAM]20:13
mesteryttx: seems legit ;)20:13
jamespagettx, lol20:13
*** dmorita has quit IRC20:13
annegentlethat's funny!20:13
jamespageI'll replace some of the letters with [ch4rm$]20:13
jamespagesee if that helps20:13
*** mohitmotiani has quit IRC20:13
johnthetubaguy-wHeh20:14
*** mohitmotiani has joined #openstack-meeting20:14
ttxCould use one more vote20:14
notmorganjamespage: [sɯɹɐɥɔ]20:14
jamespagethat will make my neck hurt20:14
ttxannegentle, johnthetubaguy-w ?20:14
johnthetubaguy-wOh, I thought I voted already20:15
*** shaohe_feng has quit IRC20:15
ttxnew patchset20:15
ttxannegentle: same20:15
jamespagediff was for the readthedoc.io link to the charm-guide20:15
*** shaohe_feng has joined #openstack-meeting20:15
johnthetubaguy-wYeah, I missed that, my bad20:15
annegentlejamespage: cool, thanks for doing that20:16
ttxannegentle: last call20:16
jamespagenp - thanks for the reviews and feedback :-)20:16
*** sindhu has joined #openstack-meeting20:16
annegentlettx: done!20:16
*** Pramod has joined #openstack-meeting20:16
ttxand win20:16
*** mohitmotiani has quit IRC20:17
ttxjamespage: thanks for your patience !20:17
flaper87jamespage: seriously! :)20:17
ttxAlright, next up20:17
jamespagettx, no problem - thankyou for being patient whilst we re-licensed!20:17
ttx#topic Add project Tricircle to OpenStack big-tent20:17
*** openstack changes topic to "Add project Tricircle to OpenStack big-tent (Meeting topic: tc)"20:17
ttx#link https://review.openstack.org/33879620:17
joehuanghello20:17
ttxjoehuang: thanks for being present! Hoping you're not based in China20:18
*** Ed___ has joined #openstack-meeting20:18
joehuangfirst, [Flavio Percoco]'s comment was just answered20:18
*** AJaeger has left #openstack-meeting20:18
ttxbecause that would be an unresonable hour20:18
annegentlehi joehuang20:18
flaper87joehuang: just read them1 Thanks for explaining :)20:18
joehuangI am in china :(20:18
joehuanghei20:18
ttxjoehuang: oops.20:18
annegentlejoehuang: eesh, thanks for joining us20:18
ttxOK, let me introduce the topic first20:18
joehuangthanks for understanding20:18
flaper87joehuang: :( it must be super late. thanks for joining20:18
ttxTricircle is a mechanism for scaling Nova/Cinder/Neutron beyond a single installation and onto several bottom pods20:19
ttxjoehuang: feel free to correct me20:19
*** david-lyle_ has joined #openstack-meeting20:19
ttxIt uses a top setup with Keystone and API proxies, which record the tenant / pod relation, and then pass requests through20:19
joehuangwill do if needed20:19
*** mrmartin has quit IRC20:19
ttxReading the current comments on the review, we can find on the positive side that it's mostly stateless, using a design close to how Ubernetes scales beyond a single K8s cluster20:19
ttxOn the negative side, it reimplements some APIs into the proxies, adds a layer of complexity, and is a bit orthogonal to the Cellsv2 effort20:19
joehuangcorrecet, simally as ubernets20:20
ttxLet's try to have an actionable discussion about this, I propose we take turns exposing our views rather than talk all together at the same time20:20
ttxWill make it easier for joehuang given it's like 3am where he is20:20
annegentlettx: such as with handraising?20:20
flaper87++20:20
dhellmann++20:20
ttxannegentle: yes20:20
annegentlettx: and ++ good idea20:20
annegentlettx: got it20:20
flaper87o/20:20
johnthetubaguy-wI'll be honest, it's the proxies that worry me, it reimplements APIs in a not very interop friendly way20:20
ttxflaper87 has the mike20:20
flaper87johnthetubaguy-w: hand raising >.>20:21
maishsko/20:21
flaper87:P20:21
joehuanghello, john, already explained in the reply to ttx,20:21
flaper87Well, as johnthetubaguy-w said, I think the proxying part is the one that really worries me. It's good that they are using tempest20:21
johnthetubaguy-wI worry we will end up with two ways of scaling openstack that are not API compatible20:21
flaper87which makes it less worrisome as it actually tests the API. However, I've the feeling that won't be enough20:21
flaper87And we'll make clouds not interoperable20:22
flaper87I'm done20:22
dhellmanno/20:22
joehuangok, let me answer a little20:22
*** Ed___ has quit IRC20:23
joehuangfirst, the bottom openstack can still use cellsv2 in nova20:23
dimso/20:24
joehuangsecond, tricircle deals cross neutron networking20:24
*** tdasilva has quit IRC20:24
*** obondarev has quit IRC20:24
*** cdelatte has quit IRC20:25
joehuangthe third, some use cases, for example, use case2, use cases3 use case 4, multiple openstack instances required20:25
joehuangnot just to scale single openstack20:25
*** shaohe_feng has quit IRC20:25
ttx(next up dhellmann, dims, maishsk)20:25
joehuangthe deployment decision has already for multiple openstack instances20:25
joehuangespecially use case 220:25
joehuangfinancial area is serious on security20:26
mordredo/20:26
*** shaohe_feng has joined #openstack-meeting20:26
ttxdhellmann: go for your question20:26
joehuangfor flaper8620:26
dhellmannI share the concerns about this being a proxy.20:26
dhellmannWe've previously declared that DefCore should not test via proxies, because it removes control of the API definition from the team implementing the API. http://governance.openstack.org/resolutions/20160504-defcore-proxy-tests.html20:27
dhellmannRegardless of whether the intent is to be absolutely compatible or not, the practice of using a "smart" proxy introduces the chance that some incompatibility will be there, and so a cloud with Tricircle and a cloud without Tricircle will behave differently.20:27
dhellmannSo while the team itself seems to be doing things a good way, I'm afraid adding this project will break our previous proxy rule.20:27
* dhellmann hands the mic back to ttx20:27
*** Sukhdev has quit IRC20:27
joehuangwe'll use tempest test cases to test the tricircle for compatibility, and defcore test if needed20:28
*** vishnoianil has joined #openstack-meeting20:28
* dhellmann picks up the mic for a follow-up response20:28
ttxdhellmann: that was not a question, more of a statement of incompatibility, but that's fair20:28
joehuangto dhellman, defcore test can be added20:28
dhellmannjoehuang : the point is that we have already very clearly said that defcore should not test projects through a proxy like this20:28
dhellmannso whether or not the tests pass isn't the point20:28
joehuangif the api is incompatible, the tricircle has no value20:28
*** dmorita has joined #openstack-meeting20:29
ttxdims: you're up20:29
flaper87o/ (again)20:29
dimsjoehuang : has tricircle team been able to influence other teams? to make things easier for you?20:30
johnthetubaguy-wo/ (joins queue)20:30
joehuangtricircle is to route the nova/cinder api, can discuss how to pass the defcore test20:30
dimsjoehuang : how is the collaboration going say with Nova etc?20:30
jroll\o20:30
* dims waits for response20:30
joehuangto dims, currently has interaction with L2GW20:31
ttx(next up: mordred, flaper87, johnthetubaguy-w, maishsk, jroll)20:31
joehuangand no feature requirements on nova yet, so new requirement to nova20:31
*** sindhu has quit IRC20:31
ttxmordred: go for it20:31
flaper87( mordred before me? I won't ever talk)20:31
maishsk;)20:32
dimsjoehuang : looking for any positive collbarations. thanks for your answer20:32
mordredhaha20:32
joehuangthanks20:32
mordredso - two short things:20:32
flaper87mordred: <320:32
joehuangand also tacker talked to tricircle for multi-site support20:32
annegentlewait did maishsk get to go?20:32
mordreda) you said that api compat is important, but then you're hiding region names from your api proxy - can you explain the difference?20:32
ttx(annegentle: I prioritize TC members over non-TC, hopefully there will be time for outside questions as well)20:33
mordredb) for the TC folks - this is a big tent, not a defcore inclusion discussion, so I do hope we don't fall into the trap of judging all of the tech decisions the tricircle team has made20:33
*** qwebirc1886 has quit IRC20:33
* jroll is fine putting his comments in gerrit instead, if it comes to that20:33
joehuangto mordred, region name is not used in any api to nova/cinder/neutro yet : )20:33
joehuangyes, thankyou20:34
*** jamesdenton has quit IRC20:34
*** ebalduf has joined #openstack-meeting20:34
joehuangfor big tent20:34
joehuangI think two factors to discuss:20:34
mordredjoehuang: but it is used in the keysotne connection, and it's pretty important data for an end user to understand where their resource are?20:34
joehuangdoes tricircle ruin the mission of openstack20:34
joehuangwhether tricircle follow the four "open"20:35
joehuangit's bigtent, not core project20:35
*** shaohe_feng has quit IRC20:35
mordredyah. I agree with that. I think the only bigtent concern I have is actually on the subject of duplication of effort20:35
*** csomerville has quit IRC20:35
ttxflaper87: you're back20:36
joehuangto mordred, in keystone, all region, subregion can be shown by the admin20:36
mordredwhich I think is why I was asking about the region name thing - it seems like a difference in conceptual model which could lead it to be a competing view of how we should think of resources20:36
joehuangand keystone supports region/sub-region model20:36
*** shaohe_feng has joined #openstack-meeting20:36
flaper87Still on the proxy argument. I wonder how tricircle is planning to keep up with project's adding new APIs. It takes a bit longer for defcore to add an API but projects could add new APIs every cycle. In addition to this, I'd like to remind ppl that Glance is still paying the price of nova's image proxy.20:36
flaper87If someone uses Tricircle internally, I think it's less of a problem. Tricircle as a public service is probably what worries me the most.20:36
joehuangso you will see like a region/sub-region tree20:36
flaper87Re mordred's #b point. I'm worried about the proxy and the technical impact that has on the projects and the duplication of efforts.20:36
*** amakarov has quit IRC20:37
ttx(next up: johnthetubaguy-w, maishsk, jroll)20:37
joehuangto flaper8720:37
*** ja3 has quit IRC20:37
joehuangfirst, this is bigtent application, and I answered the concerns on one bigtent project, am I wrong?20:38
joehuangsecond20:38
*** jungleboyj has quit IRC20:38
joehuangthe reference matrial[1] has listed the use cases where we have to use the tricircle20:39
joehuangfor adding new api, tricircle is a bigtent project(if), will not block nova,cinder/neutorn to add new appi20:39
*** irenab has quit IRC20:40
ttxI guess one way to see this question is whether Tricircle is OpenStack, or something that consumes OpenStacks. It's not an easy question and this will likely require several meetings to iron out.20:40
joehuangif these projects add new api, tricircle will implement later(not reimplement all code)20:40
ttxjohnthetubaguy-w: you're next20:40
* johnthetubaguy-w notes nova adds lots of API microversions on every cycle http://docs.openstack.org/developer/nova/api_microversion_history.html20:40
jrollttx++20:40
johnthetubaguy-wSo I am worried this hurts the openstack mission20:40
flaper87johnthetubaguy-w: my point exactly20:41
*** mohitmotiani has joined #openstack-meeting20:41
edleafettx: my thoughts too20:41
johnthetubaguy-wWe have regions and federation, etc20:41
flaper87#info Is Tricircle OpenStack? Or is it a project consuming OpenStack?20:41
joehuangto john, for these who use nova/cinder/neutron directly can have latest api20:41
flaper87not really info, more like a note20:41
johnthetubaguy-wNow if it were all client side I would wave it through say, sounds fancy might help someone, cool bananas20:42
ttxjohnthetubaguy-w: +120:42
*** csomerville has joined #openstack-meeting20:42
flaper87#info most members worried about the duplication of efforts and the gateway aspect of tricircle20:42
joehuangtricirle will introduce the feature and microversion later20:42
johnthetubaguy-wNow if it's a different API that does a specific thing, then that's not so bad either, it's more like competing with heat orchestration20:42
johnthetubaguy-wFeels like heat should orchestra setting up the security groups and l2 gateways between regions20:43
joehuangto john, could you read the reply to you about heat20:43
joehuangand we need to consider the use cases in the material[1]20:43
johnthetubaguy-wBeen offline most of the day, so not read all the conversation on there yet20:43
ttxmaishsk: thanks for waiting. What was your question ?20:43
ttx(if it wasn't answered yet)20:44
maishskttx: THanks20:44
maishskFirstly I think the concept  would be a great addition to OpenStack. My question is about the DB. You mentioned in the commit that Tricircle uses its own DB - can you elaborate a bit more on that? What DB is used? Are you re-using existing DB technologies already present in other OpenStack projects?20:44
joehuangto maishsk,20:44
joehuangno, it's a small db for routing table20:44
ttxjroll: Thanks for waiting. What was your question ?20:44
jrollI'm curious how Tricircle does the scheduling. Does it choose an OpenStack instance at random, or does it actually inspect the resources available in each instance and schedule based on that? I worry that this will eventually reimplement Nova's scheduler, or even be different enough that a request would be scheduled to an OpenStack instance that cannot satisfy the request.20:45
jroll(also posted in gerrit)20:45
joehuangto jroll, not random, in expansion scenario20:45
*** david-lyle_ has quit IRC20:45
jrollthis is about when the user does not specify an openstack instance, by the way20:45
joehuangif one exhausted, the new added one should be selected20:45
*** shaohe_feng has quit IRC20:46
*** karthikp_ has quit IRC20:46
joehuangit's on openstack instance level20:46
jrolljoehuang: how about geo-distributed case?20:46
maishskjoehuang: I dont think you answered the question. A small DB - which means another DB technology in OpenStack?20:46
joehuangnot on compute node level20:46
joehuangto maishsk,20:46
jrolljoehuang: how does tricircle know that an instance can satisfy the request?20:46
ttxmaishsk: I think he means a separate database, not a special one20:47
*** karthikp_ has joined #openstack-meeting20:47
*** elopez__ has quit IRC20:47
joehuangthe database has several tables for the tricircle20:47
jrollright, it appears to use sqlalchemy https://github.com/openstack/tricircle/blob/master/tricircle/db/models.py20:47
joehuangto ttx, +1, thanks20:47
*** priteau has joined #openstack-meeting20:47
*** elopez__ has joined #openstack-meeting20:47
maishskjoehuang: understood - much obliged!20:47
Rockygjoehuang, is db mysql?20:47
joehuangto jroll, support geo-distributed case20:48
Rockygoops.  Thank jroll20:48
*** esker has quit IRC20:48
*** gyee has joined #openstack-meeting20:48
*** shaohe_feng has joined #openstack-meeting20:48
ttxWe still have time for one or two questions before we need to move on to Open discussion20:48
*** cknight has quit IRC20:48
*** tdasilva has joined #openstack-meeting20:48
joehuangmore question can be commented in the patch20:48
joehuangso can answer in detail20:48
jrollI'm still curious how tricircle knows that an openstack instance can satisfy a build request before scheduling, but that can be answered in gerrit20:49
*** david-lyle_ has joined #openstack-meeting20:49
flaper87joehuang: thanks again for your patience and your time. We'll try to put everything on the patch and spare you another meeting20:49
ttxThe main concern, I think is that a Tricircle cloud is not really an OpenStack cloud. It may look like one, but it's different20:49
joehuangto ttx : +++++120:49
johnthetubaguy-w+1 for async20:49
*** markvoelker has quit IRC20:49
annegentlejoehuang: thanks for either staying awake or waking early20:49
ttxand including it in "OpenStack" would make it a bit confusing20:49
joehuangso how to express to reduce missunderstanding20:50
*** cdelatte has joined #openstack-meeting20:50
joehuangbut for bigtent, the tricircle does not ruin the openstack mission20:50
ttxjoehuang: we'll likely have to think about this question quite a bit, iterate on the review and future meetings.20:50
*** trozet has quit IRC20:50
joehuangplease consider the use cases20:50
johnthetubaguy-wIt's the API I find confusing, rather than the text / presentation20:50
joehuangwhich need the tircircle20:51
ttxjoehuang: thanks again for staying up so late. We'll try to make progress through the review and ML threads to reduce dependence on presence in the meeting20:51
johnthetubaguy-wI don't get the need for a single API endpoint I guess20:51
jrollthe big red flag to me is that tricircle doesn't do microversions yet, which shows me how behind the APIs might get from reality20:51
*** mohitmotiani has quit IRC20:51
flaper87Let's put all these comments on the review if they are not there already20:51
johnthetubaguy-wJroll +120:51
joehuangto jroll, this could be implemeted step by srep20:51
jrolljoehuang: I understand that :)20:52
joehuangyes in the review comment, so I can answer offline in detail20:52
ttx#topic Open discussion20:52
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:52
jroll++20:52
flaper87o/20:52
flaper87just a quick, hopefully, one20:52
flaper87https://review.openstack.org/#/c/332751/20:52
dhellmannttx: do we know when the joint tc/board/uc meeting is in barcelona?20:52
*** mickeys has joined #openstack-meeting20:52
*** JRobinson__ has joined #openstack-meeting20:52
flaper87Can we do a quick review on that one? I've moved all the changes requiring discussion to the follow-up patch20:52
ttxdhellmann: just asked for update. Looks like the plan is to have it Monday afternoon20:53
ttx(summit starts on Tuesday)20:53
dhellmannttx: ok, thanks20:53
flaper87++20:53
* dhellmann is trying to plan travel20:53
ttx"2:30-5:00pm Joint TC / UC / BoD mtg"20:53
dhellmannthose are local times?20:53
ttx#info Board+TC+UC meeting planned for 2:30pm Monday Oct 2420:53
*** dmorita has quit IRC20:53
ttxyes20:53
flaper87dhellmann: yup20:53
ttxflaper87: I'm fine approving it if you can gather enough votes in-meeting to make it happen :)20:54
ttxNext week we have a lot of TC members on the road, due to conferences and various midcycles, so I propose we skip it20:54
flaper87annegentle: dhellmann mestery mordred https://review.openstack.org/#/c/332751/20:54
flaper87:P20:54
*** ijw has joined #openstack-meeting20:54
ttxThe week after, July 26, I'll be off -- flaper87 are you still interested in standing in for me ?20:54
flaper87dhellmann: oh you voted already20:54
mesteryflaper87: I got your back, the first one was good to me20:54
flaper87+! for skipping next week's meeting20:55
flaper87+120:55
*** ijw has quit IRC20:55
ttxmordred: any progress on the P/Q naming side ?20:55
flaper87I'm taking the 26th meeting20:55
*** ijw has joined #openstack-meeting20:55
dhellmann+1 to skipping next week20:55
mordredttx: yes - I spoke with Andrew from Cornell20:55
mordredI uploaded too many emails at a time - which has also caused Cornell IT to be cross with him20:55
mordredonce things have settled down, I'll reupload in batches20:55
mordredand all should be good20:56
ttxmordred: I'd love to meet that guy!20:56
flaper87mordred: annegentle: https://review.openstack.org/#/c/332751/ :D20:56
* flaper87 got his email20:56
*** shaohe_feng has quit IRC20:56
*** gouthamr has quit IRC20:56
*** shaohe_feng has joined #openstack-meeting20:56
johnthetubaguy-w+1 on the skip20:56
*** rbudden has joined #openstack-meeting20:56
flaper87ttx: 7, go!20:56
*** piet has quit IRC20:56
*** mohitmotiani has joined #openstack-meeting20:56
annegentleI'm out 7/26 anyway20:56
joehuanghello, may meet some tc in OpenStack china days to talk about the tricircle f2f20:56
ttx#info Skipping Jul 19 meeting due to too many TC members on the road. Next meeting on Jul 26 with flaper87 chairing20:57
* flaper87 writes that down in his calendar20:57
flaper87"Do not travel on the 26th"20:57
*** dmorita has joined #openstack-meeting20:57
mordredflaper87: good luck with that20:57
ttxflaper87: you might not have quorum either on Jul 26 but worth a try20:57
flaper87mordred: :P20:57
ttxAny other work in progress someone wants to report on ?20:57
flaper87ttx: yeah20:57
*** mohitmotiani has quit IRC20:57
*** shashank_hegde has quit IRC20:57
*** mohitmotiani has joined #openstack-meeting20:58
*** singhj has quit IRC20:58
*** lblanchard has quit IRC20:58
annegentleI'd like to reschedule with ttx and flaper87 this week to talk comms, I'll send an invite20:58
*** oneswig has joined #openstack-meeting20:58
annegentleand of course anyone else who wants to join20:58
dims#link https://review.openstack.org/#/c/339175/20:58
flaper87annegentle: thanks!20:58
ttxAt the TC meeting time, I'll be watching a play at the Avignon theater festival20:58
*** mickeys has quit IRC20:58
ttx(on the 26th)20:58
dimswould love to have folks chime in again20:58
*** wznoinsk_ is now known as wznoinsk20:58
flaper87ttx: I'll make sure to have OPs pwoer to kick/ban you if you show up on the 26th from the play20:59
*** dmorita has quit IRC20:59
ttxannegentle: I'm off Wed-Fri this week, then traveling Mon-Thu next week. Feel free to move to email or have it without me20:59
ttxAnything else, anyone ?20:59
flaper87dims: on my to read for tomorrow! Thanks for writing that down20:59
* flaper87 stfu20:59
*** elopez has joined #openstack-meeting21:00
dimsthanks flaper8721:00
annegentleok21:00
*** rfolco has quit IRC21:00
*** elopez is now known as Guest8930121:00
*** markvoelker has joined #openstack-meeting21:00
ttxalrighty, closing this21:01
ttx#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Tue Jul 12 21:01:15 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
ttxThanks everyone!21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-07-12-20.01.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-07-12-20.01.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-07-12-20.01.log.html21:01
mesteryThanks ttx!21:01
*** shashank_hegde has joined #openstack-meeting21:01
mesteryAnd thanks joehuang for staying with us late into the night :)21:01
*** zeih has joined #openstack-meeting21:01
ttxI hope he is in bed now21:01
mestery++21:01
*** johnthetubaguy-w has quit IRC21:01
*** elopez__ has quit IRC21:01
*** henrynash has joined #openstack-meeting21:02
*** jamesmcarthur has quit IRC21:02
*** jamesmcarthur has joined #openstack-meeting21:02
*** julian1 has joined #openstack-meeting21:02
*** jmlowe has joined #openstack-meeting21:02
*** dmorita has joined #openstack-meeting21:02
*** claudiub has quit IRC21:02
*** dmorita has quit IRC21:02
*** singhj has joined #openstack-meeting21:03
*** mickeys has joined #openstack-meeting21:03
*** trozet has joined #openstack-meeting21:03
oneswigNearly there y'all21:03
*** david-lyle has joined #openstack-meeting21:04
*** b1airo has joined #openstack-meeting21:04
b1airohello!21:05
jmloweHello21:05
priteauevening!21:05
b1airosorry - had to have coffee in hand, brain slightly mushy this morning21:05
*** xenogear has quit IRC21:05
rbuddenhello21:05
oneswigTake it away b1airo21:05
b1airo#startmeeting scientific-wg21:05
openstackMeeting started Tue Jul 12 21:05:50 2016 UTC and is due to finish in 60 minutes.  The chair is b1airo. Information about MeetBot at http://wiki.debian.org/MeetBot.21:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:05
*** openstack changes topic to " (Meeting topic: scientific-wg)"21:05
openstackThe meeting name has been set to 'scientific_wg'21:05
b1airo#chair oneswig21:05
openstackCurrent chairs: b1airo oneswig21:05
oneswigHi everyone21:06
*** elopez_ has joined #openstack-meeting21:06
*** shaohe_feng has quit IRC21:06
*** shaohe_feng has joined #openstack-meeting21:06
*** piet has joined #openstack-meeting21:07
*** Guest89301 has quit IRC21:07
b1airo#topic Review of Activity Areas and opportunities for progress21:07
*** openstack changes topic to "Review of Activity Areas and opportunities for progress (Meeting topic: scientific-wg)"21:07
*** singhj has quit IRC21:07
*** lpetrut has quit IRC21:07
b1airo#topic Bare metal21:07
*** openstack changes topic to "Bare metal (Meeting topic: scientific-wg)"21:07
*** banix has quit IRC21:08
oneswigb1airo: any development with your plans here?21:08
*** aranjan_ has quit IRC21:08
b1airopurely for selfish reasons (we are planning a datacentre move and complete border, core, DC network refresh and design) i'd like to talk about Ironic's network requirements21:08
*** jamesmcarthur has quit IRC21:09
*** aranjan has joined #openstack-meeting21:09
*** jamesmcarthur has joined #openstack-meeting21:09
*** shashank_hegde has quit IRC21:09
oneswigmy experience (a year old now) is that provisioning is flat but any other network can have VLAN segmentation21:09
*** _sarob has quit IRC21:10
*** dmorita has joined #openstack-meeting21:10
*** dmorita has quit IRC21:10
*** zhipeng has quit IRC21:10
b1airotraditionally we've used Cisco FEXs as our out-of-band switching, connecting e.g. to iLO/DRAC and we also usually have a separate 1G interface into our hypervisors (separate to the high-bandwidth front-side/fabric) just in case we have driver issues etc21:10
*** rderose_ has quit IRC21:11
*** aranjan_ has joined #openstack-meeting21:11
b1airooneswig, i believe there is at least some work towards segregated provisioning nets21:11
*** trozet has quit IRC21:11
priteauoneswig: How do you configure Ironic to do perform provisioning on a different network than the one used by the instance in the end?21:12
rbuddenb1airo: we have a similar setup21:12
oneswigThere's a long-standing patch, still digging for it21:12
*** aranjan has quit IRC21:12
b1airowhen i last looked i figured FEXs wouldn't work, but since then i see Cisco seem to have broad Nexus support in an ML2 driver21:12
oneswigpriteau: we had trusted instance images, I'm not sure if you can "unconnect" the provisioning network once the node is up21:12
*** jamesmcarthur has quit IRC21:13
b1airoanyone used it (with or without Ironic)?21:13
*** jamesmcarthur has joined #openstack-meeting21:13
priteauoneswig: I see. In Chameleon we are developing our solution for this, currently in testing phase21:13
b1airooneswig, priteau - sorry i should have been clear, disconnecting the BM instance from the provisioning network would be a requirement for us21:13
priteauWill be specific to our networking hardware (Dell S6000)21:14
*** mbound has quit IRC21:14
b1airoso we'd be trying to use the DRAC provisioning driver in the first instance21:14
oneswigb1airo, priteau: how do you / will you hide access to the provisioning network?21:15
b1airoand looking for a provisioning network whose Neutron driver untrunked the relevant V[X]LAN from the BM instances physical ports after boot21:15
*** annegentle has quit IRC21:15
priteauoneswig: we are instrumenting OpenStack to change VLAN port config once the provisioning is done21:16
*** joehuang has quit IRC21:16
b1airopriteau, cool - you had to do that yourself? i assumed it'd end up being Neutron driver dependent, no?21:16
*** shaohe_feng has quit IRC21:16
*** thorst has quit IRC21:16
*** singhj has joined #openstack-meeting21:17
*** thorst has joined #openstack-meeting21:17
*** shaohe_feng has joined #openstack-meeting21:17
priteaub1airo: Yes we had to develop Neutron integration ourselves21:17
priteauit's currently in testing phase21:18
b1airoand of course we'd prefer not to have a flat provisioning network too, to avoid boot hijacking hijinx and so forth, but not strictly needed as we probably wouldn't use this for anything more than our own UnderCloud provisioning and perhaps HPC team21:18
oneswigpriteau: is there an Ironic state machine transition you can trigger this from?  I wonder if there's an 'official' way to do that21:18
*** thorst_ has joined #openstack-meeting21:18
priteauoneswig: I haven't seen the code yet actually, it's developed by Northwestern University and quite recent21:19
b1airo#action b1airo to ask about Ironic provisioning network unplugging on os-dev[ironic]21:19
oneswigpriteau: in a more general form I am sure this would find value in many other places21:19
priteauI know there is similar work happening upstream21:20
*** thorst__ has joined #openstack-meeting21:20
oneswigpriteau: I assume Rackspace onmetal has already solved this21:20
priteauit was discussed at the Austin meeting21:20
*** tonytan4ever has joined #openstack-meeting21:20
*** julian1 has quit IRC21:20
*** rcernin has joined #openstack-meeting21:21
b1airook, i've scratched my itch sufficiently - thanks! shall we move on unless anyone has other BM things to discuss?21:21
*** singhj has quit IRC21:21
oneswignothing here21:21
*** dmorita has joined #openstack-meeting21:21
b1airo#topic Parallel filesystems21:21
*** openstack changes topic to "Parallel filesystems (Meeting topic: scientific-wg)"21:21
*** maishsk_ has joined #openstack-meeting21:21
*** dmorita has quit IRC21:21
*** thorst has quit IRC21:21
*** esker has joined #openstack-meeting21:22
*** zeih has quit IRC21:22
b1airoso, seems like a HPFS panel at Barcelona might be a goer21:22
*** thorst_ has quit IRC21:23
*** dmorita has joined #openstack-meeting21:23
oneswigb1airo: I think it's going to be popular!21:23
oneswigyou might find it difficult to get a room big enough once the panel are all sitting down :-)21:24
jmloweGreat, how many panelists have you found?21:24
*** thorst__ has quit IRC21:24
*** maishsk has quit IRC21:24
*** maishsk_ is now known as maishsk21:24
b1airoi particularly liked jmlowe's comment21:24
b1airooneswig, lol21:24
b1airoIIUC the max for a panel session is 4 panelists plus a moderator21:25
oneswigjmlowe: not sure exactly but I saw some quick uptake following your mail21:25
b1airothough i can't imagine that is a hard ceiling21:25
b1airojust on that thread we already have 4 without counting me :-)21:26
b1aironot sure i'd make a great moderator, but i'd give it a crack21:26
*** tonytan4ever has quit IRC21:26
*** shaohe_feng has quit IRC21:27
*** esker has quit IRC21:27
*** mohitmotiani has quit IRC21:27
*** shaohe_feng has joined #openstack-meeting21:27
b1airoi may give it another 24 hours in the ether and then through something into the proposals21:27
oneswigb1airo: asking the questions not answering them?  Given your experience it makes more sense the other way?21:27
*** cdelatte has quit IRC21:28
devanandab1airo: ironic/neutron network integration has been underway for a couple cycles - we're trying to get it in, but the feature is complex, and involves nova integration as well21:28
b1airooneswig, may as well have a moderator that knows the lay of the land to some extent though21:28
oneswigThere was also the question on vendors vs users21:28
*** esker has joined #openstack-meeting21:28
b1airohi devananda - thanks for jumping in!21:28
oneswigHi devananda!21:28
*** dmorita has quit IRC21:28
rbuddenhello devananda!21:29
devanandab1airo: short version is that ironic will call out to neutron at specific stages in provisioning/cleaning to attach/detach the instance from provider networks, so that tenants are isolated from the control plane -- and from each other21:29
*** flwang1 has joined #openstack-meeting21:29
oneswigdevananda: any idea on an ETA?21:29
*** pnavarro has joined #openstack-meeting21:29
devanandaon the network side, neutron ML2 framework is used. I've been testing with OVS, which seems to have broad support (your TOR must have HW VTEP support, at least)21:30
b1airodevananda, ok cool, so that's what i had thought was happening in current versions or is still in dev?21:30
*** jmckind has quit IRC21:30
devanandab1airo: there's a partial implementation, where we can move the Node onto a special 'cleaning_network', that exists today21:30
oneswigdevananda: what is the current solution for mapping ironic ports to physical switch ports for manipulating vlan state - is it a per-driver solution?21:30
devanandabut tenant isolation and tenant-defined networks is not in-tree yet21:30
*** jamesmcarthur has quit IRC21:31
devanandaoneswig: that's in flight still. several companies have downstream solutions, but the upstream / generic solution is taking time21:31
*** csomerville has quit IRC21:31
*** jamesmcarthur has joined #openstack-meeting21:31
b1airoright, so a BM instance must be connected to a specific provider network then?21:31
oneswigdevananda: ok thanks, which solutions are leading this?21:31
*** csomerville has joined #openstack-meeting21:31
*** dmorita has joined #openstack-meeting21:31
*** david-lyle has quit IRC21:31
devanandaas far as ETA - I'd love to have a definitive answer, but I don't. I _HOPE_ we'll land enough of this in Newton to cal lit functional21:31
*** priteau has quit IRC21:32
*** priteau has joined #openstack-meeting21:33
devanandaoneswig: arista, HP, rackspace, cisco are the main contributors to the code right now. I won't speak to any vendor-specific products/solutions21:33
*** spzala has quit IRC21:33
*** asettle has quit IRC21:33
*** esker has quit IRC21:33
oneswigdevananda: LLDP-enabled ramdisk?21:33
b1airodevananda, i was originally asking about this in the context of building a new out of band network infrastructure in a new DC. i'm assuming if we go with a policy of separate physical iLO + 1x embedded connection that we'll have covered ourselves sufficiently, but then comes the question of vendor support for Neutron21:33
*** spzala has joined #openstack-meeting21:34
*** spzala has quit IRC21:34
devanandab1airo: if your TOR supports OVSDB and HW-VTEP, I think it should work21:34
*** spzala has joined #openstack-meeting21:34
devanandaI've even done some testing on relatively old Juniper switches (with new firmware) and had some success21:34
*** fzdarsky has quit IRC21:34
devanandaoneswig: that's been proposed, but is separate work21:35
b1airoawesome, thanks21:35
devanandanp! hope that info is helpful :)21:35
*** singhj has joined #openstack-meeting21:35
oneswigThanks devananda21:35
b1airooneswig, back to your question re. vendors in HPFS panel -21:36
*** hashar has quit IRC21:36
*** dmorita has quit IRC21:36
*** dprince has quit IRC21:36
oneswigI think the "war stories" can't come from manufacturers of munitions...21:36
*** dmorita has joined #openstack-meeting21:36
b1airoi think Dean specifically would be fine, but ultimately if there are other interested end-users/deployers it'd probably be better to have them21:36
*** jamesmcarthur has quit IRC21:36
*** shaohe_feng has quit IRC21:37
b1airocertainly we don't want product managers or "technical" sales21:37
*** shaohe_feng has joined #openstack-meeting21:37
oneswigIt's most important to have speakers who who are well informed and objective on vendor products21:38
*** adiantum has quit IRC21:38
b1airobrb...21:38
oneswigPerhaps he is both, I don't know21:38
*** jamesmcarthur has joined #openstack-meeting21:39
*** spzala has quit IRC21:39
oneswigHow do people envisage structuring a panel on HPFS?  Might be good to have lightning talks from each member on their use case scenario before open discussion21:40
*** adiantum has joined #openstack-meeting21:41
b1airoback21:41
b1airo(2yo decided to fall off the bathroom stool)21:41
oneswigall well I hope :-)21:42
b1airooneswig, good idea yeah21:42
b1airoand then leave plenty of time for audience question/discussion21:42
oneswigI wonder if it's possible to ask for more than 40 minutes for the session21:42
*** pnavarro has quit IRC21:43
*** banix has joined #openstack-meeting21:43
oneswigRecall the Austin summit, we had 4x Ironic lightning talks and no panel discussion in 40 minutes21:43
*** cleong has quit IRC21:43
b1airooh PS: i'm one of the track chairs for HPC/Research, did you ever through your name in oneswig ?21:44
oneswigI did, think it's come through21:44
*** dmorita has quit IRC21:44
b1airook, so we are in a good position to try and get a longer spot then :-)21:44
oneswigPerhaps we can run a couple of much longer sessions, drawing from WG activity areas21:45
*** egallen has joined #openstack-meeting21:46
b1airothat'd be nice, 40 mins in a good energised session never seems enough21:46
*** shaohe_feng has quit IRC21:47
*** amitgandhinz has quit IRC21:47
*** aranjan_ has quit IRC21:47
b1airoi guess bare-metal would have enough working group contributors, and it'd probably facilitate good UC <-> Dev crossover21:47
*** shaohe_feng has joined #openstack-meeting21:48
*** aranjan has joined #openstack-meeting21:48
oneswigI wonder if we could have a session in which representatives from various deploy projects (OpenStack-Ansible, TripleO, etc.) demonstrate how to deploy and configure some HPC-like capabilities using their projects21:48
b1aironot sure about accounting/scheduling though, i feel like there are a lot of large subtopics there without a lot of clear solutions21:48
oneswigb1airo: agreed, too nebulous right now21:48
rbuddenoneswig: that would be interesting21:48
*** aranjan has quit IRC21:49
*** aranjan_ has joined #openstack-meeting21:49
b1airooneswig, think it's worth calling out to the relevant dev list topics for takers?21:50
oneswig#action oneswig to make enquiries re: deployment and report back21:50
oneswigb1airo: my thoughts exactly :-)21:50
b1airogreat minds21:50
oneswigI wouldn't know...21:50
b1airook, i think we'll skip account and scheduling unless anyone has something to raise?21:50
b1airo(in today's meeting i mean)21:50
*** aranjan has joined #openstack-meeting21:51
b1airo#topic OpenStack & HPC white paper21:51
*** openstack changes topic to "OpenStack & HPC white paper (Meeting topic: scientific-wg)"21:51
*** mohitmotiani has joined #openstack-meeting21:51
b1airoanything to talk about on this oneswig ?21:51
oneswigSo this is starting to come together, here's the latest21:51
b1airoi guess you are just in the think of plugging away whilst also trying to help with the Cambridge deployment?21:51
oneswigIn time for SC, we are looking to generate content on 5ish topics21:52
oneswigI'm pretty maxed out on the Cambridge deployment right now but as of this week we have a lull21:52
*** adiantum has quit IRC21:52
*** adiantum has joined #openstack-meeting21:53
oneswigEach topic, a problem statement, solution concept plus some positive words from a subject matter expert21:53
oneswigI'll find those topics...21:53
*** toddjohn has joined #openstack-meeting21:53
rbuddenis this related to or in conjunction with the SC Panel?21:53
*** clenimar_ has joined #openstack-meeting21:54
*** mohitmotiani has quit IRC21:54
*** aranjan_ has quit IRC21:54
oneswigrbudden: in addition - this is basically brochures and a whitepaper download21:54
*** ijw has quit IRC21:54
rbuddenok great21:54
oneswigOK they are:21:54
b1airorbudden, related, though i guess oneswig might be calling in the direction of the panel for SMEs as needed21:54
oneswig1) Virtualisation strategies and alternatives for HPC21:54
rbuddeni missed last meeting, but did have an action item on this… I have PSC approval for passing out brochures, etc. at our boot21:54
oneswig2) OpenStack and HPC network fabrics21:55
oneswig3) OpenStack and high performance data (filesystems, objects etc)21:55
oneswig4) OpenStack and HPC workload management21:55
b1airorbudden, brilliant, thanks for following that up!21:55
oneswig5) OpenStack and HPC infrastructure management21:55
rbuddenb1airo: no problem. if we want to do demos/presentations that possible with additional heads up and/or approval21:56
oneswigPossible bonus topic on federation, but that's not HPC-specific plus I think we'll have our hands full21:56
oneswigI'm generating much of this content as part of my contract with Cambridge but will be seeking SME input in many areas - look out y'all21:57
*** azbiswas has joined #openstack-meeting21:57
b1airo#topic Other Business21:57
*** Sukhdev has joined #openstack-meeting21:57
*** openstack changes topic to "Other Business (Meeting topic: scientific-wg)"21:57
*** shaohe_feng has quit IRC21:57
b1airotime's almost up21:57
*** toddjohn has quit IRC21:58
*** shaohe_feng has joined #openstack-meeting21:58
*** azbiswas has quit IRC21:58
*** jckasper has quit IRC21:58
b1airoi did quickly want to call out for contributions to the hypervisor tuning guide, particularly on hypervisors other than KVM21:58
*** markvoelker has quit IRC21:59
*** azbiswas has joined #openstack-meeting21:59
*** designbybeck_ has quit IRC21:59
b1airoJoe Topjian from Cybera put it together originally from the output of various hypervisor tuning ops sessions, but we haven't quite figured out what to do with it from there21:59
oneswigIsn't KVM something like 90% of deployments now?21:59
b1airowould be nice to lift it out of wiki obscurity21:59
b1airooneswig, yes it's certainly the most popular, don't know about the actual numbers breakdown of the top of my head though22:00
rbuddenKVM is pretty dominate22:00
b1airothe Xen people always have nice t-shorts though, so i have a soft spot for them :-D22:00
rbuddeni remember the Havana Summit and I was the only one doing Xen in general in an entire room :P22:00
b1airo*t-shirts22:00
oneswigI wonder if there's anything you can tune with Canonical's LXD22:00
b1aironot sure what a t-short is, but it sounds uncomfortable22:01
b1airooneswig, i guess there would be22:01
jmlowesorry, re SC'16: I'm still waiting for the scheduling for our booth, it's just a question of how many time slots for booth talks, at least 30 min /day would be minimum22:02
*** dmorita has joined #openstack-meeting22:02
*** mohitmotiani has joined #openstack-meeting22:02
oneswig#action oneswig to ask his friends at canonical re LXD tuning22:02
*** carolbarrett has quit IRC22:02
oneswigWe are over time22:02
b1airojmlowe, are you planning to show off any of your OpenStack work?22:03
*** mohitmotiani has quit IRC22:03
rbuddenspeaking of SC, one thing to add, if we want talks/demos we should prep that earlier. I can likely get approval for those but the content/timeslots need arranged earlier rather than later22:03
b1airorbudden, yes certainly need to have that organised well in advance. at this stage i suspect it'll largely be the whitepaper oneswig was talking about plus some other generic foundation materials22:04
jmloweb1airo: yes, I was also thinking general Openstack and HPC booth talks open to any wg member22:04
*** markvoelker has joined #openstack-meeting22:04
rbuddenb1airo: sounds good. I do have a pair of NUCs I can bring if we had a purpose to show a demo of sorts22:05
b1airoin terms of demos, that'd be cool but i'm not sure we'll get anything from folks that do not already have a booth presence, unless the foundation has a wheel-in demo system already going (only things i have seen are vendor specific)22:05
*** esberglu has quit IRC22:06
*** clenimar_ has quit IRC22:06
b1airojmlowe, ok that's great to know. we may get a better idea once we see some of the summit proposals and then match up with folks who might be at SC22:06
rbuddenjmlowe: maybe the talk we are working on about Murano/Heat w/VM Repo would be interesting to demo22:07
*** shaohe_feng has quit IRC22:08
* b1airo ears prick up22:08
*** dmorita has quit IRC22:08
jmloweYep, should cross you inbox as a summit talk soon22:08
*** mriedem has quit IRC22:08
rbuddenb1airo: we are working on a talk for Barcelona22:08
*** shaohe_feng has joined #openstack-meeting22:08
rbuddenwe won’t ruin the surprise ;)22:08
b1airoexcellent!22:08
oneswigCan't get you guys off the stage it seems :-)22:08
rbuddenhaha, that’s the plan!22:08
b1airook, must run - got to get to work o_022:09
oneswigLook forward to it22:09
oneswigOK, lets wrap up?22:09
jmloweCross site collaboration is a great way to wrestle loose some travel money22:09
rbuddenyeah we are a bit over anyway22:09
*** priteau has quit IRC22:09
b1airothanks once again all!22:09
oneswigthanks everyone22:09
b1airo#endmeeting22:09
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:09
openstackMeeting ended Tue Jul 12 22:09:47 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:09
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_wg/2016/scientific_wg.2016-07-12-21.05.html22:09
rbuddenthanks!22:09
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_wg/2016/scientific_wg.2016-07-12-21.05.txt22:09
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_wg/2016/scientific_wg.2016-07-12-21.05.log.html22:09
*** jmlowe has left #openstack-meeting22:09
*** priteau has joined #openstack-meeting22:10
*** b1airo has quit IRC22:10
*** rbudden has left #openstack-meeting22:12
*** mickeys has quit IRC22:12
*** priteau has quit IRC22:13
*** cbader has quit IRC22:14
*** mbound has joined #openstack-meeting22:14
*** dmorita has joined #openstack-meeting22:14
*** elopez_ has quit IRC22:16
*** karthikp_ has quit IRC22:17
*** shaohe_feng has quit IRC22:18
*** dmorita has quit IRC22:18
*** shaohe_feng has joined #openstack-meeting22:18
*** zeih has joined #openstack-meeting22:19
*** clenimar_ has joined #openstack-meeting22:19
*** mbound has quit IRC22:20
*** kylek3h has quit IRC22:20
*** shashank_hegde has joined #openstack-meeting22:21
*** david-lyle_ is now known as david-lyle22:22
*** xyang1 has quit IRC22:23
*** Ed___ has joined #openstack-meeting22:23
*** zeih has quit IRC22:25
*** galstrom_zzz is now known as galstrom22:25
*** thorst has joined #openstack-meeting22:25
*** ijw has joined #openstack-meeting22:26
*** dane_leblanc has quit IRC22:26
*** tpsilva has quit IRC22:28
*** Ed___ has quit IRC22:28
*** shaohe_feng has quit IRC22:28
*** thorst_ has joined #openstack-meeting22:29
*** shaohe_feng has joined #openstack-meeting22:29
*** Sukhdev has quit IRC22:29
*** Leo_ has quit IRC22:29
*** larainema has quit IRC22:29
*** thorst has quit IRC22:30
*** elopez has joined #openstack-meeting22:32
*** elopez is now known as Guest5055522:32
*** thorst_ has quit IRC22:34
*** rrecio has quit IRC22:34
*** spzala has joined #openstack-meeting22:35
*** rrecio has joined #openstack-meeting22:35
*** rcernin has quit IRC22:35
*** dmorita has joined #openstack-meeting22:35
*** zul has quit IRC22:36
*** henrynash has quit IRC22:36
*** zul has joined #openstack-meeting22:36
*** tonytan4ever has joined #openstack-meeting22:37
*** dmorita has quit IRC22:37
*** dmorita has joined #openstack-meeting22:37
*** shaohe_feng has quit IRC22:38
*** shaohe_feng has joined #openstack-meeting22:39
*** somerville32 has joined #openstack-meeting22:39
*** somerville32 has quit IRC22:39
*** somerville32 has joined #openstack-meeting22:39
*** rrecio has quit IRC22:39
*** rossella_s has quit IRC22:40
*** ajmiller_ has quit IRC22:40
*** spzala has quit IRC22:40
*** rossella_s has joined #openstack-meeting22:41
*** lamt has quit IRC22:41
*** tonytan4ever has quit IRC22:42
*** dmorita has quit IRC22:42
*** csomerville has quit IRC22:43
*** csomerville has joined #openstack-meeting22:43
*** Guest50555 has quit IRC22:44
*** weshay has quit IRC22:45
*** leeantho has quit IRC22:45
*** Fdaisuke has joined #openstack-meeting22:45
*** Ed___ has joined #openstack-meeting22:45
*** Julien-zte has joined #openstack-meeting22:46
*** somerville32 has quit IRC22:47
*** elopez_ has joined #openstack-meeting22:48
*** shaohe_feng has quit IRC22:49
*** shaohe_feng has joined #openstack-meeting22:49
*** Ed___ has quit IRC22:50
*** timcline has quit IRC22:51
*** timcline has joined #openstack-meeting22:51
*** elopez_ has quit IRC22:52
*** dimtruck is now known as zz_dimtruck22:52
*** mriedem has joined #openstack-meeting22:53
*** rbak has quit IRC22:53
*** elopez_ has joined #openstack-meeting22:53
*** pradk has quit IRC22:54
*** egallen has quit IRC22:55
*** timcline has quit IRC22:56
*** vishwanathj has quit IRC22:57
*** vishwanathj has joined #openstack-meeting22:58
*** Patifa has quit IRC22:58
*** shaohe_feng has quit IRC22:59
*** shaohe_feng has joined #openstack-meeting22:59
*** singhj has quit IRC22:59
*** csomerville has quit IRC23:00
*** markvoelker has quit IRC23:00
*** oneswig has quit IRC23:02
*** vishwanathj has quit IRC23:02
*** shashank_hegde has quit IRC23:03
*** csomerville has joined #openstack-meeting23:03
*** vishwanathj has joined #openstack-meeting23:03
*** Sukhdev has joined #openstack-meeting23:03
*** dmorita has joined #openstack-meeting23:03
*** shashank_hegde has joined #openstack-meeting23:03
*** leeantho has joined #openstack-meeting23:06
*** markvoelker has joined #openstack-meeting23:06
*** galstrom is now known as galstrom_zzz23:07
*** rrecio has joined #openstack-meeting23:07
*** vishwanathj has quit IRC23:07
*** elopez_ has quit IRC23:08
*** mohitmotiani has joined #openstack-meeting23:08
*** vishwanathj has joined #openstack-meeting23:08
*** dmorita has quit IRC23:08
*** ijw has quit IRC23:08
*** vishwanathj has quit IRC23:08
*** vishwanathj has joined #openstack-meeting23:09
*** shaohe_feng has quit IRC23:09
*** shaohe_feng has joined #openstack-meeting23:10
*** penick has quit IRC23:11
*** mohitmotiani has quit IRC23:12
*** ravelar159 has quit IRC23:12
*** mohitmotiani has joined #openstack-meeting23:12
*** elopez_ has joined #openstack-meeting23:12
*** Sukhdev has quit IRC23:14
*** karthikp_ has joined #openstack-meeting23:16
*** galstrom_zzz is now known as galstrom23:17
*** Suyash has quit IRC23:19
*** gaso84ne has quit IRC23:19
*** Suyi_ has joined #openstack-meeting23:19
*** shashank_hegde has quit IRC23:19
*** shaohe_feng has quit IRC23:19
*** shaohe_feng has joined #openstack-meeting23:20
*** zeih has joined #openstack-meeting23:20
*** hemna is now known as hemnafk23:22
*** xarses has quit IRC23:23
*** dmorita_ has joined #openstack-meeting23:24
*** kaminohana has joined #openstack-meeting23:24
*** bobh has joined #openstack-meeting23:24
*** ijw has joined #openstack-meeting23:25
*** zeih has quit IRC23:26
*** Ed___ has joined #openstack-meeting23:27
*** dmorita_ has quit IRC23:28
*** banix has quit IRC23:29
*** Suyi_ has quit IRC23:30
*** shaohe_feng has quit IRC23:30
*** enriquetaso has quit IRC23:30
*** vishwanathj has quit IRC23:30
*** vishwanathj has joined #openstack-meeting23:31
*** Ed___ has quit IRC23:32
*** tochi has joined #openstack-meeting23:32
*** shaohe_feng has joined #openstack-meeting23:32
*** ronghui has quit IRC23:32
*** rrecio has quit IRC23:33
*** baoli_ has quit IRC23:35
*** vishwanathj has quit IRC23:36
*** spzala has joined #openstack-meeting23:36
*** vishwanathj has joined #openstack-meeting23:36
*** ijw has quit IRC23:36
*** Sukhdev has joined #openstack-meeting23:38
*** bobh has quit IRC23:38
*** mickeys has joined #openstack-meeting23:39
*** shaohe_feng has quit IRC23:40
*** shaohe_feng has joined #openstack-meeting23:41
*** mohitmotiani has quit IRC23:41
*** spzala has quit IRC23:42
*** toddjohn has joined #openstack-meeting23:44
*** ronghui has joined #openstack-meeting23:45
*** rderose has joined #openstack-meeting23:46
*** katomo has joined #openstack-meeting23:46
*** amitgandhinz has joined #openstack-meeting23:48
*** Julien-zte has quit IRC23:48
*** shaohe_feng has quit IRC23:50
*** shaohe_feng has joined #openstack-meeting23:50
*** zz_dimtruck is now known as dimtruck23:51
*** thorst has joined #openstack-meeting23:51
*** amitgandhinz has quit IRC23:53
*** shashank_hegde has joined #openstack-meeting23:53
*** shu-mutou-AFK is now known as shu-mutou23:54
*** mohitmotiani has joined #openstack-meeting23:57
*** jungleboyj has joined #openstack-meeting23:58
*** fnaval has quit IRC23:59

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