Tuesday, 2016-08-02

*** kei_ has joined #openstack-meeting00:00
*** rossella_s has quit IRC00:00
*** rossella_s has joined #openstack-meeting00:00
*** Suyi_ has quit IRC00:01
*** kei has quit IRC00:01
*** adrianofr has quit IRC00:01
*** spzala has quit IRC00:04
*** rickyhai has joined #openstack-meeting00:04
*** yamamoto has joined #openstack-meeting00:04
*** sindhu has joined #openstack-meeting00:05
*** esberglu has quit IRC00:06
*** zhangguoqing has quit IRC00:07
*** rickyhai has quit IRC00:08
*** shaohe_feng has quit IRC00:09
*** armax has quit IRC00:09
*** shaohe_feng has joined #openstack-meeting00:10
*** amitgandhinz has joined #openstack-meeting00:10
*** baoli has quit IRC00:10
*** r-daneel has quit IRC00:11
*** bcafarel has joined #openstack-meeting00:12
*** amitgandhinz has quit IRC00:15
*** _AmitGalitz has quit IRC00:15
*** jesusaur has joined #openstack-meeting00:16
*** thorst has quit IRC00:16
*** thorst has joined #openstack-meeting00:17
*** bcafarel has quit IRC00:17
*** spzala has joined #openstack-meeting00:17
*** lazy_prince has joined #openstack-meeting00:18
*** shaohe_feng has quit IRC00:19
*** shaohe_feng has joined #openstack-meeting00:20
*** thorst has quit IRC00:21
*** lazy_prince has quit IRC00:22
*** banix has quit IRC00:22
*** onovy has quit IRC00:23
*** cdelatte has quit IRC00:23
*** onovy has joined #openstack-meeting00:23
*** JRobinson__ has quit IRC00:23
*** jesusaur has quit IRC00:23
*** JRobinson__ has joined #openstack-meeting00:26
*** mtanin___ has joined #openstack-meeting00:28
*** doug-fish has quit IRC00:29
*** shaohe_feng has quit IRC00:29
*** mtanino has quit IRC00:30
*** shaohe_feng has joined #openstack-meeting00:30
*** pvaneck has quit IRC00:31
*** number80 has quit IRC00:34
*** sindhu has quit IRC00:38
*** achanda has joined #openstack-meeting00:39
*** rfolco_ has joined #openstack-meeting00:39
*** shaohe_feng has quit IRC00:40
*** shaohe_feng has joined #openstack-meeting00:40
*** dmacpher has joined #openstack-meeting00:40
*** myoung|biab is now known as myoung00:49
*** bobh has joined #openstack-meeting00:49
*** shaohe_feng has quit IRC00:50
*** rfolco_ has quit IRC00:50
*** jesusaur has joined #openstack-meeting00:50
*** shaohe_feng has joined #openstack-meeting00:51
*** sindhu has joined #openstack-meeting00:52
*** yuanying has quit IRC00:54
*** toddjohn has joined #openstack-meeting00:55
*** lblanchard has joined #openstack-meeting00:56
*** jesusaur has quit IRC00:57
*** toddjohn has quit IRC00:59
*** Mortir has joined #openstack-meeting01:00
*** jesusaur has joined #openstack-meeting01:00
*** shaohe_feng has quit IRC01:00
*** shaohe_feng has joined #openstack-meeting01:01
*** yuanying has joined #openstack-meeting01:02
*** gyee has quit IRC01:02
*** yamamoto has quit IRC01:03
*** banix has joined #openstack-meeting01:04
*** tochi has quit IRC01:05
*** spzala has quit IRC01:05
*** jaypipes has quit IRC01:06
*** Mortir has quit IRC01:07
*** spzala has joined #openstack-meeting01:07
*** zhurong has joined #openstack-meeting01:08
*** achanda has quit IRC01:10
*** shaohe_feng has quit IRC01:10
*** spzala has quit IRC01:11
*** amitgandhinz has joined #openstack-meeting01:11
*** shaohe_feng has joined #openstack-meeting01:11
*** liyifeng has quit IRC01:12
*** sdake has quit IRC01:14
*** amitgandhinz has quit IRC01:16
*** ajmiller_ has quit IRC01:18
*** banix has quit IRC01:19
*** thorst has joined #openstack-meeting01:20
*** ajmiller has joined #openstack-meeting01:20
*** shaohe_feng has quit IRC01:21
*** yamamoto has joined #openstack-meeting01:21
*** shaohe_feng has joined #openstack-meeting01:21
*** cknight has joined #openstack-meeting01:25
*** Apoorva_ has joined #openstack-meeting01:25
*** thorst has quit IRC01:26
*** singhj has quit IRC01:26
*** toddjohn has joined #openstack-meeting01:27
*** bcafarel has joined #openstack-meeting01:28
*** ajmiller has quit IRC01:29
*** Apoorva has quit IRC01:29
*** ajmiller has joined #openstack-meeting01:29
*** thorst has joined #openstack-meeting01:29
*** banix has joined #openstack-meeting01:29
*** Apoorva_ has quit IRC01:30
*** thorst has quit IRC01:30
*** shaohe_feng has quit IRC01:31
*** achanda has joined #openstack-meeting01:31
*** shaohe_feng has joined #openstack-meeting01:32
*** toddjohn has quit IRC01:34
*** bcafarel has quit IRC01:36
*** banix has quit IRC01:39
*** unicell1 has quit IRC01:39
*** unicell has joined #openstack-meeting01:39
*** shaohe_feng has quit IRC01:41
*** shaohe_feng has joined #openstack-meeting01:42
*** mickeys has joined #openstack-meeting01:42
*** mickeys has quit IRC01:43
*** mickeys has joined #openstack-meeting01:44
*** yamamoto has quit IRC01:44
*** mickeys has quit IRC01:45
*** yuanying has quit IRC01:45
*** mickeys has joined #openstack-meeting01:45
*** yuanying has joined #openstack-meeting01:46
*** s3wong has quit IRC01:49
*** mickeys has quit IRC01:50
*** uxdanielle has joined #openstack-meeting01:50
*** jhesketh has quit IRC01:51
*** shaohe_feng has quit IRC01:51
*** jhesketh has joined #openstack-meeting01:51
*** mtanin___ has quit IRC01:52
*** shaohe_feng has joined #openstack-meeting01:52
*** armax has joined #openstack-meeting01:53
*** yuanying has quit IRC01:55
*** ljxiash has joined #openstack-meeting01:55
*** synegi has joined #openstack-meeting01:55
*** sindhu has quit IRC01:55
*** zhurong has quit IRC01:57
*** zhurong has joined #openstack-meeting01:58
*** synegy34 has quit IRC01:59
*** yamamoto has joined #openstack-meeting01:59
*** unicell has quit IRC02:02
*** shaohe_feng has quit IRC02:02
*** bobh has quit IRC02:02
*** shaohe_feng has joined #openstack-meeting02:02
*** asselin has quit IRC02:03
*** liyifeng has joined #openstack-meeting02:03
*** karthikp_ has quit IRC02:04
*** yuanying has joined #openstack-meeting02:04
*** hoangcx2 has quit IRC02:06
*** hongbin has joined #openstack-meeting02:07
*** maeca1 has joined #openstack-meeting02:07
*** shaohe_feng has quit IRC02:12
*** shaohe_feng has joined #openstack-meeting02:12
*** amitgandhinz has joined #openstack-meeting02:13
*** enriquetaso has joined #openstack-meeting02:15
*** enriquetaso has quit IRC02:16
*** amitgandhinz has quit IRC02:18
*** bcafarel has joined #openstack-meeting02:21
*** shaohe_feng has quit IRC02:22
*** shaohe_feng has joined #openstack-meeting02:22
*** mriedem has quit IRC02:23
*** sudipto has joined #openstack-meeting02:23
*** claudiub has joined #openstack-meeting02:24
*** zhurong has quit IRC02:24
*** yuanying has quit IRC02:24
*** yuanying has joined #openstack-meeting02:25
*** markvoelker has joined #openstack-meeting02:25
*** bcafarel has quit IRC02:25
*** zhurong has joined #openstack-meeting02:26
*** gongysh has joined #openstack-meeting02:28
*** amitkqed has quit IRC02:30
*** amitkqed has joined #openstack-meeting02:30
*** markvoelker_ has joined #openstack-meeting02:30
*** markvoelker has quit IRC02:30
*** thorst has joined #openstack-meeting02:31
*** lamt_ has quit IRC02:31
*** toddjohn has joined #openstack-meeting02:31
*** achanda has quit IRC02:32
*** yuanying has quit IRC02:32
*** shaohe_feng has quit IRC02:32
*** shaohe_feng has joined #openstack-meeting02:33
*** mkrai has joined #openstack-meeting02:33
*** mickeys has joined #openstack-meeting02:34
*** mickeys has quit IRC02:36
*** thorst has quit IRC02:36
*** mickeys has joined #openstack-meeting02:36
*** bobh has joined #openstack-meeting02:37
*** spzala has joined #openstack-meeting02:37
*** toddjohn has quit IRC02:38
*** uxdanielle has quit IRC02:38
*** gcb has joined #openstack-meeting02:40
*** Leo_ has joined #openstack-meeting02:40
*** mickeys has quit IRC02:41
*** shaohe_feng has quit IRC02:43
*** spzala has quit IRC02:43
*** shaohe_feng has joined #openstack-meeting02:43
*** achanda has joined #openstack-meeting02:44
*** harlowja_at_home has joined #openstack-meeting02:49
*** dmorita has quit IRC02:51
*** Namrata has joined #openstack-meeting02:51
*** yamahata has quit IRC02:52
*** iyamahat has quit IRC02:52
*** bobh has quit IRC02:52
*** dmorita has joined #openstack-meeting02:53
*** shaohe_feng has quit IRC02:53
*** sudipto has quit IRC02:54
*** Namrata_ has joined #openstack-meeting02:54
*** shaohe_feng has joined #openstack-meeting02:54
*** sudipto has joined #openstack-meeting02:54
*** Namrata has quit IRC02:56
*** dimtruck is now known as zz_dimtruck02:56
*** sindhu has joined #openstack-meeting02:57
*** harlowja_at_home has quit IRC02:57
*** tochi has joined #openstack-meeting02:57
hongbin#startmeeting zun03:00
openstackMeeting started Tue Aug  2 03:00:30 2016 UTC and is due to finish in 60 minutes.  The chair is hongbin. Information about MeetBot at http://wiki.debian.org/MeetBot.03:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.03:00
*** openstack changes topic to " (Meeting topic: zun)"03:00
openstackThe meeting name has been set to 'zun'03:00
hongbin#link https://wiki.openstack.org/wiki/Zun#Agenda_for_2016-08-02_0300_UTC Today's agenda03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
mkraiMadhuri Kumari03:00
*** lazy_prince has joined #openstack-meeting03:00
*** yanyanhu has joined #openstack-meeting03:01
yanyanhuhi, sorry, I'm late03:01
WenzhiWenzhi Yu03:01
*** shashank_hegde has quit IRC03:01
*** Sukhdev has quit IRC03:01
hongbinThanks for joining the meeting eliqiao mkrai Namrata_ yanyanhu sudipto Wenzhi itzdilip03:01
hongbin#topic Announcements03:01
*** openstack changes topic to "Announcements (Meeting topic: zun)"03:01
hongbinI have no annoucement03:02
hongbinAny of you have?03:02
hongbin#topic Review Action Items03:02
*** openstack changes topic to "Review Action Items (Meeting topic: zun)"03:02
hongbin#topic Runtimes API design (mkrai)03:02
*** spzala has joined #openstack-meeting03:02
*** openstack changes topic to "Runtimes API design (mkrai) (Meeting topic: zun)"03:02
hongbinmkrai: ^^03:02
*** dtrainor has quit IRC03:03
mkraiI have implemented the APIs using pecan03:03
mkraiUploaded the patch yesterday03:03
mkraiCurrently some of the APIs are not running03:03
*** shaohe_feng has quit IRC03:03
mkraiWaiting for the RPCs to test it03:03
*** shubhams has joined #openstack-meeting03:03
mkraiI see hongbin has already uploaded patch for compute agent03:04
eliqiaohttps://review.openstack.org/#/c/328444/ mkrai?03:04
mkraiI will test using it this week03:04
mkraiYes eliqiao03:04
shubhamsHi o/03:04
*** shaohe_feng has joined #openstack-meeting03:04
mkraiI would like team to review patch once I set it as ready for review03:04
*** lazy_prince has quit IRC03:05
mkraiThat's all I have.03:05
mkraiAnyone have any question?03:05
hongbinThanks mkrai03:05
eliqiaoWe may use zun to test swarm bay(created bay Magnum) mkrai03:05
mkraieliqiao,  Yes we can03:05
*** lazy_prince has joined #openstack-meeting03:05
mkraiIt depends on the implementation of compute apis now03:06
hongbineliqiao: Or you can simply run a docker daemon at localhost and test it03:06
*** zz_dimtruck is now known as dimtruck03:06
eliqiaohongbin: sure.03:06
*** asettle has joined #openstack-meeting03:07
mkraiAlso there is change in the APIs endpoint03:07
*** spzala has quit IRC03:07
mkraiwhich I will update in spec etherpad03:07
hongbinThe API endpoint should be a configurable string03:07
mkraiThat is for all the action APIs03:07
*** dmorita has quit IRC03:08
hongbin#topic Nova integration (Namrata)03:08
*** openstack changes topic to "Nova integration (Namrata) (Meeting topic: zun)"03:08
hongbinNamrata_: any update from you?03:08
*** janki has joined #openstack-meeting03:08
Namrata_as per discussion with hongbin03:09
Namrata_That is using nova scheduler with nova integration03:09
mkraihongbin, I, sudipto had some discussion last week which we recorded in etherpad03:09
mkrai#link https://etherpad.openstack.org/p/zun-containers-nova-integration03:09
Namrata_and if without nova zun's scheduler03:10
Namrata_can we ask opinion fro  the team03:10
*** kei has joined #openstack-meeting03:10
hongbinNamrata_: I think you can relay your inputs to the etherpad above03:11
Namrata_Okay hongbin03:11
* hongbin is reading hte etherpad03:11
*** dmorita has joined #openstack-meeting03:12
mkraiNamrata_, In that case does it mean our Zun scheduler should be optional?03:12
*** kei_ has quit IRC03:12
mkraiHmm that means we expect host information in APIs03:13
Namrata_True that03:13
hongbinYes, Zun should be able to return a list hosts03:13
mkraiNot sure about this implementation03:13
*** shaohe_feng has quit IRC03:13
*** asettle has quit IRC03:13
hongbinmkrai: That is exactly how Ironic is integrated with Nova03:14
*** amitgandhinz has joined #openstack-meeting03:14
hongbinmkrai: Ironic return a list of nodes for nova scheduler to pick03:14
*** shaohe_feng has joined #openstack-meeting03:14
yanyanhuhongbin, you mean providing host list to nova and let it choose one?03:14
*** achanda has quit IRC03:14
hongbinyanyanhu: yes03:14
mkraiBut ironic doesn't have a scheduler. Right?03:14
hongbinmkrai: yes03:15
Wenzhithen maybe we need to enroll the nodes manually03:15
hongbinYes,all nodes should be enrolled at Zun03:15
*** dmorita has quit IRC03:16
*** sindhu has quit IRC03:16
yanyanhuany one know how vcenter being integrated with nova?03:17
*** lblanchard has quit IRC03:17
Wenzhiok, but how does Nova decide the dest node?03:17
hongbinyanyanhu: no idea from me03:17
yanyanhuwhich is a similar case I guess?03:17
mkraiWenzhi, based on filters03:17
hongbinWenzhi: nova retrieve the list of hosts, use filters and weithers to choose a host03:18
Wenzhimkrai: yes, but currently nova do not have any filters for container case , right?03:18
eliqiaoyanyanhu: +103:18
yanyanhusome reference: http://docs.openstack.org/kilo/config-reference/content/vmware.html03:18
*** amitgandhinz has quit IRC03:18
mkraiYes Wenzhi03:19
hongbinWenzhi: container is represented as a Nova instance if nova integration03:19
eliqiaoin that case, nova-compute is just a gateway, vcenter will decide vm will be runing on which host.03:19
mkraiBut some general filter would work for us too03:19
mkraieliqiao, What is vcenter?03:19
yanyanhueliqiao,  right, that's why I feel it could be a similar case :)03:19
yanyanhu"The VMware vCenter driver enables the nova-compute service to communicate with a VMware vCenter server that manages one or more ESX host clusters."03:20
eliqiaomkrai: just talking about how vmware driver works from yanyanhu03:20
Wenzhihongbin: if so, seems we need to introduce something like container flavor03:20
hongbinWenzhi: yes03:20
yanyanhuWenzhi, yes I guess so03:20
*** Leo_ has quit IRC03:21
eliqiaoyanyanhu: the case of vCenter is strange, it will allow 1 compute node have multiple hosts.03:21
eliqiaofor libvirt: only one compute node vs one host03:21
Wenzhieliqiao: like powervc, hha03:21
hongbineliqiao: In Ironic, there could be multiple hosts as well03:21
hongbinIn the case of vcentre, basically, the nova scheduler is disabled?03:22
itzdilipno with respect to compute, vcenter is considered as host03:23
Wenzhihongbin: not sure but I guess so03:23
Wenzhivcenter itself is a cloud03:23
*** r-mibu has quit IRC03:23
yanyanhueliqiao, yes, just considering the use case of container is very different from vm(at least in Zun scope),  I guess this could be a feasible way to integrate Zun with nova?03:23
hongbinsounds like we need more investigation in this area03:23
*** shaohe_feng has quit IRC03:24
yanyanhujust providing limited support for provisioning container through nova03:24
hongbinThat will work as well03:24
*** r-mibu has joined #openstack-meeting03:24
*** epico has joined #openstack-meeting03:24
*** shaohe_feng has joined #openstack-meeting03:25
mkraiLet's get a very simple implementation as Ironic and later we can of course enhance it as we evolve03:25
eliqiaoIf we intergrate with Nova, things get sucks, if not, we will lose the entry point of Nova ...03:25
Wenzhimaybe nova-zun-driver can just pass the nova cmd to zun and let zun do the whole work03:25
yanyanhuWenzhi, yes, that's is what I'm thinking03:26
hongbinThat is the proxy approach, basically, bypass the nova scheduler03:26
yanyanhuyes, Zun has its own scheduling strategy, based on 'container' use cases03:26
*** amotoki has joined #openstack-meeting03:27
eliqiaohongbin: just heard from colleague from nova mid-cycle, nova scheduler will be split out in one of two release.03:27
yanyanhueliqiao, good news :)03:27
*** coolsvap has joined #openstack-meeting03:28
Qimingin the long run, we as one community, should converge to one scheduler as possible as we can, we are not supposed to reinvent everything03:28
hongbinQiming: agree03:28
Qimingfor the short term and mid-term experimentation, it might be okay to run a simple stupid scheduler algorithm, but the interface to that to-be-split scheduler should be clear03:29
eliqiaoQiming: ++03:30
*** brnelson has quit IRC03:30
*** brnelson has joined #openstack-meeting03:30
hongbinNamrata_: do you have enough information to proceed?03:31
hongbinNamrata_: or anything that needs to be clarify?03:31
Namrata_Hongbin I will investigate more on it03:32
Namrata_or maybe start with code03:32
hongbinNamrata_: sure. you can start with code, or start with a spec is also fine03:33
Namrata_okay hongbin03:33
hongbinThanks Namrata_03:33
WenzhiNamrata_: I think you need to start with a spec, nova demands that03:33
*** klkumar has joined #openstack-meeting03:33
hongbinWenzhi: We started the work totally out of Nova I think03:34
hongbinAlthough start with a spec is a good idea03:34
*** shaohe_feng has quit IRC03:34
Namrata_It will bot be in nova tree. Do we still need it?03:34
hongbinWe can push it to nova tree later03:34
hongbinbut I am not sure if Nova team will accpet it03:35
*** shaohe_feng has joined #openstack-meeting03:35
hongbinIf not, then the driver needs to stay at our tree03:35
WenzhiI have the same concern ^^03:35
*** sindhu has joined #openstack-meeting03:35
Namrata_I will submit spec in zun03:35
yanyanhuno harm to have a try :) after we are ready03:36
hongbinOK. advance topic03:36
hongbin#topic Integrate with Mesos scheduler (sudipto)03:36
*** openstack changes topic to "Integrate with Mesos scheduler (sudipto) (Meeting topic: zun)"03:36
*** thorst has joined #openstack-meeting03:36
hongbinsudipto: could you outline the idea of integating with mesos secheduler that you mentioned before ?03:37
yanyanhulet zun stay upon mesos? :)03:37
sudiptohongbin, ok - so my thought was to have a way to run zun as a framework on top of mesos.03:37
sudiptokeep in mind, this is just one way03:38
sudiptothere is going to be a z-sched as you guys are discussing so far.03:38
sudiptobut i'd like that to be pluggable. so that it can be overridden by a mesos scheduler.03:38
*** JRobinson__ is now known as JRobinson__afk03:38
sudiptothe job of creation of container will also be done using mesos via it's executor.03:39
mkrai+1 sudipto. Schedulers should be pluggable so that we can integrate with any runtimes scheduler easily03:39
sudiptothis would allow you to run zun with other container frameworks. presently the ones integrated with mesos are kubernetes and marathon as a frameworks03:40
sudiptoso keep the interfaces clean and pluggable - that should do.03:41
sudiptounless there are thoughts/comments - i am done hongbin  :)03:41
hongbinsudipto: I guess mesos is not just a scheduler03:42
hongbinsudipto: it also manages hosts?03:42
yanyanhuhongbin, it does03:42
sudiptohongbin, it has to run a slave on each of the hosts.03:42
yanyanhuit is a resource pool management service IMO03:42
yanyanhuand frameworks upon it provide strategy03:43
hongbinYes, then with this idea, the mesos slave will replace the compute agent03:43
yanyanhuto manage lifecycle of tasks03:43
hongbinyanyanhu: what do you think about this idea?03:43
yanyanhuhongbin, interesting idea :)03:43
yanyanhujust not sure whether we should deeply depends on mesos03:44
hongbinyanyanhu: you steal my comments :)03:44
yanyanhuhongbin, :)03:44
hongbin(interesting idea)03:44
yanyanhuanother concern about mesos is it's C++ based03:44
*** shaohe_feng has quit IRC03:44
hongbinQiming: what do you think?03:44
yanyanhucould that be a problem for dependency building?03:44
sudiptoso the workflow happens like this: there's a mesos master that talks to the mesos slaves. The mesos master gets a list of offers and presents it to the framework. the list of offers is nothing but a set of resources for a task deployment and then the framework makes the decision of where to schedule it.03:44
sudiptoi would suggest keep this as optional.03:45
yanyanhusudipto,  just like how k8s on mesos works :)03:45
*** thorst has quit IRC03:45
sudiptoyanyanhu, yeah precisely.03:45
*** shaohe_feng has joined #openstack-meeting03:45
hongbinYes, it should be optional at the beginning03:46
sudiptomesos allows you to simultaneously run two frameworks on the same set of hosts.03:46
sudiptothat's the value add.03:46
*** dkehn_ has quit IRC03:46
*** bill_az has quit IRC03:46
sudiptos/two/two or more03:46
hongbinI think another value add is that we don't need to re-implement resource management from scatch03:46
sudiptowell that depends if you want to treat as mandatory or optional03:47
hongbinhowever, it is optional, so we still need a resource management03:47
*** julenl has joined #openstack-meeting03:47
hongbinA drawback is as yanyanhu mentioned, it is C++03:47
sudiptono that is not a drawback03:48
hongbinhowever, it could be solved by containerized the mesos-master and slave03:48
sudiptoit has the python bindings.03:48
*** yuanying has joined #openstack-meeting03:48
sudiptoso why is C++ a drawback then? :)03:48
sudiptothe mesos core is written in C++ - we don't have to touch that code.03:48
hongbinI guess packing will be more difficult03:48
hongbinThere is a big discussion about whether openstack should allow Golang03:49
hongbinand the packing team has a strong disagreement with the proposal03:49
hongbinsame for c++03:49
sudiptoi don't think we will package mesos with openstack ?03:49
sudiptoor intend to.03:49
hongbinno, if it is containerized03:50
hongbinOH, I see what you mean03:50
hongbinNo, it is packaged by the OS distro03:50
hongbinso that looks fine03:51
*** julen has quit IRC03:51
sudiptoi mean this could be something  very similar to this :03:51
sudipto#link: https://github.com/docker/swarm/blob/master/cluster/mesos/README.md03:51
sudiptobut this is definitely not a priority i would say.03:52
hongbinI guess hte network and storage needs to be investigated03:52
sudiptomore focus at the moment should be on the API design and the other pieces that would make zun stand on it's own feet first.03:52
hongbin#topic Open Discussion03:53
*** openstack changes topic to "Open Discussion (Meeting topic: zun)"03:53
jankiHi. I am Janki, new to Zun. I am looking for contributing to Zun.03:53
hongbinwelcome to join the meeting janki03:53
jankiNot quite sure where to start as all BP are taken and those not taken are all long term03:53
sudiptoso are we looking at timelines yet to achieve things? I am guessing i'd be able to meet you guys at Barcelona. But should we aim for a PoC before that?03:54
jankihongbin: Thank you :)03:54
sudiptojanki, don't worry about the BPs yet. Start with the reviews if you like it.03:54
mkraiYes atleast docker support sudipto :)03:54
jankisudipto: Will do03:54
hongbinsudipto: PoC?03:54
sudiptohongbin, i mean something to work with or demo with.03:54
*** shaohe_feng has quit IRC03:54
sudiptoi change my words - a working project :)03:55
*** Na3iL has joined #openstack-meeting03:55
sudiptomkrai, yeah agreed.03:55
*** achanda has joined #openstack-meeting03:55
hongbinyes, if we can make that, that is great03:55
mkraiJanki there is lots of work to be done in Zun03:55
*** shaohe_feng has joined #openstack-meeting03:55
*** achanda has quit IRC03:55
mkraiAttend meetings you will get the idea on which things you can work03:55
jankimkrai: I would be happy to work on those.03:55
jankimkrai: Sure, will attend03:56
mkraicool :03:56
sudiptolike for instance, can we say that during the next meeting we can have the API design finalised and mostly up for review?03:56
mkraiHopefully yes sudipto :)03:56
*** saju_m has quit IRC03:57
sudiptomkrai, i am happy to help!03:57
mkraihongbin, Can I use the compute code now?03:57
mkraiIs it ready?03:57
mkraiThanks sudipto03:57
hongbinmkrai: I haven't tested it yet :)03:57
hongbinmkrai: but everyone are free to revise it03:57
mkraiOk I will try once03:58
hongbinThere will be a lot fo bugs though :)03:58
sudiptomkrai, i think the API code can move with stubs for now?03:58
mkraiThe current one is just bypassing the RPC calls03:58
sudiptoare we going to be using the docker remote apis ?03:58
sudiptoanyway i think we are on the brink of the hour. I will catch on the zun channel.03:59
mkraiWe will use the compute rpc apis03:59
mkraiThanks all!03:59
hongbinAll, thanks for joining the meeting03:59
hongbinNext meeting is the next week the same time03:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"03:59
openstackMeeting ended Tue Aug  2 03:59:49 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-08-02-03.00.html03:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-08-02-03.00.txt03:59
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-08-02-03.00.log.html03:59
*** dkehn_ has joined #openstack-meeting03:59
*** hongbin has quit IRC04:00
*** rossella_s has quit IRC04:00
mkraijanki, catch us on #openstack-zun if you have any doubts04:00
*** rossella_s has joined #openstack-meeting04:00
jankimkrai: Thanks. I am an active listener there04:00
*** bcafarel has joined #openstack-meeting04:00
*** janki has quit IRC04:02
*** claudiub has quit IRC04:05
*** shaohe_feng has quit IRC04:05
*** anilvenkata has joined #openstack-meeting04:05
*** Leo_ has joined #openstack-meeting04:06
*** shaohe_feng has joined #openstack-meeting04:06
*** gcb has quit IRC04:06
*** bcafarel has quit IRC04:06
*** sudipto has quit IRC04:06
*** gcb has joined #openstack-meeting04:06
*** shubhams has left #openstack-meeting04:07
*** jaypipes has joined #openstack-meeting04:07
*** Leo_ has quit IRC04:10
*** amitgandhinz has joined #openstack-meeting04:15
*** shaohe_feng has quit IRC04:15
*** markvoelker_ has quit IRC04:15
*** shaohe_feng has joined #openstack-meeting04:18
*** julim has quit IRC04:19
*** amitgandhinz has quit IRC04:19
*** armax has quit IRC04:21
*** shaohe_feng has quit IRC04:25
*** shaohe_feng has joined #openstack-meeting04:26
*** jungleboyj has joined #openstack-meeting04:26
*** iyamahat has joined #openstack-meeting04:29
*** jungleboyj has quit IRC04:31
*** unicell has joined #openstack-meeting04:32
*** crinkle has quit IRC04:35
*** toddjohn has joined #openstack-meeting04:35
*** crinkle has joined #openstack-meeting04:35
*** shaohe_feng has quit IRC04:35
*** shaohe_feng has joined #openstack-meeting04:36
*** links has joined #openstack-meeting04:36
*** toddjohn has quit IRC04:39
*** mkrai has quit IRC04:42
*** JRobinson__afk is now known as JRobinson__04:42
*** iyamahat has quit IRC04:43
*** thorst has joined #openstack-meeting04:43
*** maeca1 has quit IRC04:45
*** roxanagh_ has joined #openstack-meeting04:45
*** shaohe_feng has quit IRC04:46
*** shaohe_feng has joined #openstack-meeting04:46
*** sudipto has joined #openstack-meeting04:46
*** harlowja_at_home has joined #openstack-meeting04:49
*** thorst has quit IRC04:51
*** elo has joined #openstack-meeting04:52
*** harlowja_at_home has quit IRC04:55
*** eric_lopez has quit IRC04:55
*** shaohe_feng has quit IRC04:56
*** irenab has quit IRC04:57
*** shaohe_feng has joined #openstack-meeting04:57
*** Leo_ has joined #openstack-meeting05:00
*** Namrata_ has quit IRC05:00
*** Na3iL has quit IRC05:02
*** spzala has joined #openstack-meeting05:02
*** mkrai has joined #openstack-meeting05:02
*** Leo_ has quit IRC05:04
*** shaohe_feng has quit IRC05:06
*** singhj has joined #openstack-meeting05:06
*** flwang1 has quit IRC05:06
*** spzala has quit IRC05:07
*** shaohe_feng has joined #openstack-meeting05:07
*** ljxiash has quit IRC05:08
*** markvoelker has joined #openstack-meeting05:10
*** radek_ has joined #openstack-meeting05:11
*** Na3iL has joined #openstack-meeting05:15
*** amitgandhinz has joined #openstack-meeting05:15
*** markvoelker has quit IRC05:16
*** shaohe_feng has quit IRC05:16
*** shaohe_feng has joined #openstack-meeting05:17
*** nkrinner_afk is now known as nkrinner05:17
*** janki has joined #openstack-meeting05:19
*** amitgandhinz has quit IRC05:21
*** ihrachys has joined #openstack-meeting05:22
*** unicell has quit IRC05:22
*** bcafarel has joined #openstack-meeting05:23
*** ihrachys has quit IRC05:25
*** ihrachys has joined #openstack-meeting05:26
*** shaohe_feng has quit IRC05:27
*** shaohe_feng has joined #openstack-meeting05:27
*** unicell has joined #openstack-meeting05:27
*** cknight has quit IRC05:28
*** _alastor- has quit IRC05:28
*** _alastor__ has joined #openstack-meeting05:28
*** persia_ has quit IRC05:28
*** Poornima has joined #openstack-meeting05:29
*** persia_ has joined #openstack-meeting05:31
*** cknight has joined #openstack-meeting05:31
*** elopez_ has quit IRC05:31
*** number80 has joined #openstack-meeting05:31
*** ljxiash has joined #openstack-meeting05:33
*** klkumar has quit IRC05:34
*** klkumar has joined #openstack-meeting05:35
*** sindhu has quit IRC05:37
*** shaohe_feng has quit IRC05:37
*** shaohe_feng has joined #openstack-meeting05:38
*** ihrachys has quit IRC05:38
*** katomo has joined #openstack-meeting05:41
*** derekjhyang has quit IRC05:42
*** roxanagh_ has quit IRC05:42
*** unicell has quit IRC05:44
*** unicell has joined #openstack-meeting05:45
*** achanda has joined #openstack-meeting05:46
*** JRobinson__ has quit IRC05:46
*** shaohe_feng has quit IRC05:47
*** shaohe_feng has joined #openstack-meeting05:48
*** thorst has joined #openstack-meeting05:48
*** obondarev has joined #openstack-meeting05:49
*** ljxiash has quit IRC05:49
*** ljxiash has joined #openstack-meeting05:50
*** singhj has quit IRC05:51
*** flwang1 has joined #openstack-meeting05:52
*** irenab has joined #openstack-meeting05:52
*** Leo_ has joined #openstack-meeting05:54
*** ljxiash has quit IRC05:54
*** ihrachys has joined #openstack-meeting05:55
*** AJaeger has joined #openstack-meeting05:55
*** trozet has quit IRC05:55
*** thorst has quit IRC05:55
*** ihrachys has quit IRC05:56
*** ljxiash has joined #openstack-meeting05:57
*** shaohe_feng has quit IRC05:57
*** shaohe_feng has joined #openstack-meeting05:58
*** Leo_ has quit IRC05:59
*** Poornima has quit IRC05:59
loquacitieshi everyone, we're due to start the install guide meeting, but i'm just going to wait 5 mins as andreas is running late06:00
*** shashank_hegde has joined #openstack-meeting06:01
*** ljxiash_ has joined #openstack-meeting06:02
*** mkrai has left #openstack-meeting06:02
*** flwang1 has quit IRC06:03
*** spzala has joined #openstack-meeting06:03
*** cknight has quit IRC06:03
*** numans has joined #openstack-meeting06:03
*** unicell has quit IRC06:04
*** ljxiash has quit IRC06:05
loquacitiesok, shall we get started?06:06
*** lpetrut has joined #openstack-meeting06:06
loquacities#startmeeting docinstallteam06:06
openstackMeeting started Tue Aug  2 06:06:19 2016 UTC and is due to finish in 60 minutes.  The chair is loquacities. Information about MeetBot at http://wiki.debian.org/MeetBot.06:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.06:06
*** openstack changes topic to " (Meeting topic: docinstallteam)"06:06
openstackThe meeting name has been set to 'docinstallteam'06:06
loquacitieswho's here?06:06
*** markvoelker has joined #openstack-meeting06:06
* AJaeger 06:06
loquacitiesheya :)06:06
*** obondarev has quit IRC06:07
*** cody-somerville has quit IRC06:07
loquacitiesis katomo around?06:07
*** cody-somerville has joined #openstack-meeting06:07
*** spzala has quit IRC06:07
*** unicell has joined #openstack-meeting06:07
loquacitiesanyone else?06:07
*** dbite has joined #openstack-meeting06:07
loquacitiesmight be just us three06:07
*** shaohe_feng has quit IRC06:08
loquacitiesoh hi dbite06:08
loquacitiesok, not too much to go through, but a couple of things that need to be discussed06:08
dbiteI should be able to attend more regularly now :)06:08
loquacities#topic Manila patch is stalled06:08
*** openstack changes topic to "Manila patch is stalled (Meeting topic: docinstallteam)"06:08
loquacities#link https://review.openstack.org/#/c/317152/06:08
loquacitiesdbite: that's great! :)06:09
loquacitiesi'm not sure what needs to happen here, but i can reach out to goutham06:09
AJaegerplease do, loquacities06:09
loquacities#action loquacities to ask goutham about 317152 progress06:10
loquacities#topic ops:docs:install-guide tag06:10
*** openstack changes topic to "ops:docs:install-guide tag (Meeting topic: docinstallteam)"06:10
loquacities#info original patch abandoned: https://review.openstack.org/#/c/341933/06:10
loquacities#info Followed up here: https://review.openstack.org/#/c/347224/06:10
*** shaohe_feng has joined #openstack-meeting06:10
loquacitiesnot sure if there's any action there from us, but it's an FYI, at the very least06:11
*** dixiaoli has joined #openstack-meeting06:11
loquacities#topic Testing06:12
*** openstack changes topic to "Testing (Meeting topic: docinstallteam)"06:12
loquacitiesit's occurred to me that we need to start thinking about this06:12
loquacitiesi assume we'll go ahead and test the core install guide as per usual06:12
loquacitiesdoes anyone have any thoughts on that?06:12
loquacitiesi don't want this to be too arduous, as it defeats the purpose of splitting off the guides otherwise06:12
*** markvoelker has quit IRC06:13
AJaegerI'm under the impression we test only "our" part - not the one in the project-teams.06:14
loquacitiesmy thoughts too06:14
*** liamji has joined #openstack-meeting06:14
loquacitiesok, if that's all we have to say on that06:15
katomosomething automation, such as Ansible or Puppet, works for us?06:15
loquacities#topic Work Items06:15
*** openstack changes topic to "Work Items (Meeting topic: docinstallteam)"06:15
AJaegermight still be good to include them and ask them to test...06:15
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x7f5bbf33cc10>06:15
loquacitieskatomo: there is a work item for automation06:15
loquacitiesAJaeger: i assume nothing has happened on that at this point, though?06:16
loquacitiesand yes, i'll ping the individual projects when we go into testing mode06:16
*** amitgandhinz has joined #openstack-meeting06:16
loquacitiesi'll also engage with the CPLs to get testers, as well as the packagers for the distros06:16
dbiteHow long before we have the testing mode?06:16
AJaegerloquacities: nothing coordinated has happened06:16
loquacitiesAJaeger: i suspected that06:17
loquacitiesdbite: what do you mean by testing mode?06:17
dbiteloquacities: Your words "before we go into testing mode"06:17
loquacitiesoh, i see06:18
*** shaohe_feng has quit IRC06:18
*** cartik has joined #openstack-meeting06:18
loquacitiesi meant "when we begin testing"06:18
loquacitieswhich i would think will be in the next week or two06:18
loquacitiesi want to go through the guide more thoroughly before then06:18
*** shaohe_feng has joined #openstack-meeting06:19
loquacities#link https://wiki.openstack.org/wiki/Documentation/InstallGuideWorkItems06:19
loquacitiesso other than those couple of tasks we mentioned, we're pretty much ready06:19
dbiteloquacities: Ok, I will try to coordinate trainig-labs scripts for Newton around the same time. Hopefully we could make things easier to test for the install guides team.06:20
loquacitiesthat would be great :)06:20
loquacities#topic other business06:20
*** openstack changes topic to "other business (Meeting topic: docinstallteam)"06:20
loquacitiesanything else?06:20
*** amitgandhinz has quit IRC06:21
AJaegerloquacities: I lost overview on what all needs to be done, too busy with other stuff. I hope you have not lost it.06:21
loquacitiesyeah, that's cool06:22
loquacitiesi think we're in good shapee06:22
*** adiantum has joined #openstack-meeting06:22
*** unicell has quit IRC06:22
loquacitieswith the exception of manila, everything is pretty close to ready06:22
*** unicell1 has joined #openstack-meeting06:22
loquacitieswe just need to do the usual testing/update before newton, then publish everything up06:22
katomofacilitate any other projects?06:22
loquacitieswe probably need to consider some patches to the index page, too, but it will work until then06:23
AJaegerloquacities: is designate on your radar? https://review.openstack.org/#/c/341622/06:23
loquacitieskatomo: yes, but i'm pretty much waiting for them to come to me at this stage06:23
AJaegerThat's one I'm aware of as well (just checking my open reviews)06:23
katomoloquacities: got it06:23
loquacitiesah, no i hadn't seen that one!06:23
loquacitiescool :)06:23
AJaegerseems stuck as well ;(06:24
loquacitiesyeah, OS problems ...06:24
katomo#link https://review.openstack.org/#/c/333536/06:24
loquacitiessame old same old06:24
katomomaybe zaqar06:24
*** gcb has quit IRC06:24
loquacitiesi was aware of zaqar, but thought they had everything in06:25
*** sridharg has joined #openstack-meeting06:25
loquacitiesthanks for this, i'll investigate further06:25
loquacitieslast i spoke to flwang he said they had all their jobs in, but was worried zaqar wouldn't get published with everything else06:26
AJaegerit's up here: http://docs.openstack.org/project-install-guide/messaging/draft/06:27
AJaegerWe still need to implement the publishing logic to publish to /newton once a newton branch is created...06:27
*** gcb has joined #openstack-meeting06:27
loquacitiesyeah, i told him we'd take care of that06:27
AJaegerMy only known open action item on this ;)06:27
loquacitiesthat and the automated testing, but that can be held over :P06:28
*** shaohe_feng has quit IRC06:28
AJaegerautomated testing is for dbite ...06:29
loquacitiesi'll let you two argue over that :P06:29
*** shaohe_feng has joined #openstack-meeting06:29
dbiteAwesome :)06:29
loquacitiesok, cool06:30
loquacitiesshall we call it done?06:30
dbiteAJaeger: Taking a look at the work items.06:30
dbiteloquacities: Its not done06:30
AJaegerno need to argue - I won't have time to do it. I discussed a bit with dbite and will continue if needed but cannot do anything myself06:30
loquacitiesoh, i meant the meeting, not the automation ;)06:30
loquacitiesAJaeger: ok, cool06:30
dbiteloquacities: lol, yes.06:30
loquacitiesi know the automation isn't done yet ;)06:31
loquacitiesanything else?06:31
dbiteloquacities: Yes it is partially done on my private repository06:31
loquacitiesah, excellent :)06:32
dbitetrying to get it completed.06:32
*** shashank_hegde has quit IRC06:32
*** whenry has quit IRC06:32
loquacitieswell, best of luck06:32
AJaegerloquacities: do we need to update the basis guide for Newton? Do you know what needs to be done? Hope that's on the agenda for the future...06:32
loquacitiesi want to engage the packagers and the CPLs06:33
loquacitiesto work out what we need to do before we begin testing06:33
loquacitiesso yes, definitely on the agenda, but i don't yet know what needs to be done06:34
*** toddjohn has joined #openstack-meeting06:36
loquacitiesok, we're out of time here06:37
loquacitiesany other items?06:37
AJaegernone from my side06:37
katomonothing from me06:37
loquacitiesok, cool06:37
loquacitiesthanks guys :)06:37
dbiteim good06:37
katomothanks, all06:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:37
openstackMeeting ended Tue Aug  2 06:37:36 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docinstallteam/2016/docinstallteam.2016-08-02-06.06.html06:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docinstallteam/2016/docinstallteam.2016-08-02-06.06.txt06:37
openstackLog:            http://eavesdrop.openstack.org/meetings/docinstallteam/2016/docinstallteam.2016-08-02-06.06.log.html06:37
*** dbite has quit IRC06:37
*** katomo has quit IRC06:37
*** shaohe_feng has quit IRC06:38
*** AJaeger has left #openstack-meeting06:38
*** roxanagh_ has joined #openstack-meeting06:39
*** shaohe_feng has joined #openstack-meeting06:39
*** cartik has quit IRC06:39
*** toddjohn has quit IRC06:40
*** tesseract- has joined #openstack-meeting06:43
*** comay has quit IRC06:43
*** fnaval has quit IRC06:44
*** fnaval has joined #openstack-meeting06:44
*** roxanagh_ has quit IRC06:44
*** gongysh has quit IRC06:45
*** saju_m has joined #openstack-meeting06:47
*** rbartal has joined #openstack-meeting06:48
*** Leo_ has joined #openstack-meeting06:48
*** whenry has joined #openstack-meeting06:48
*** shaohe_feng has quit IRC06:49
*** shaohe_feng has joined #openstack-meeting06:49
*** belmoreira has joined #openstack-meeting06:50
*** Leo_ has quit IRC06:53
*** thorst has joined #openstack-meeting06:53
*** comay has joined #openstack-meeting06:53
*** dongfeng has joined #openstack-meeting06:54
*** janki has quit IRC06:54
*** fnaval has quit IRC06:58
*** manikanta_tadi has joined #openstack-meeting06:59
*** shaohe_feng has quit IRC06:59
*** shaohe_feng has joined #openstack-meeting06:59
*** thorst has quit IRC07:01
*** markvoelker has joined #openstack-meeting07:02
*** RuiChen has joined #openstack-meeting07:04
*** spzala has joined #openstack-meeting07:04
*** manikanta_tadi has quit IRC07:05
*** yanyanhu has left #openstack-meeting07:08
*** whenry has quit IRC07:08
*** markvoelker has quit IRC07:08
*** kaminohana has quit IRC07:08
*** spzala has quit IRC07:08
*** shaohe_feng has quit IRC07:09
*** zul has quit IRC07:09
*** shaohe_feng has joined #openstack-meeting07:10
*** shashank_hegde has joined #openstack-meeting07:12
*** Mortir has joined #openstack-meeting07:14
*** Mortir has quit IRC07:15
*** achanda has quit IRC07:15
*** dimtruck is now known as zz_dimtruck07:15
*** amitgandhinz has joined #openstack-meeting07:17
*** cschwede has joined #openstack-meeting07:19
*** shaohe_feng has quit IRC07:19
*** shaohe_feng has joined #openstack-meeting07:20
*** mikelk has joined #openstack-meeting07:20
*** amitgandhinz has quit IRC07:22
*** yuval has joined #openstack-meeting07:23
*** zul has joined #openstack-meeting07:23
*** sshnaidm|afk has quit IRC07:24
*** nmagnezi has joined #openstack-meeting07:24
*** shashank_hegde has quit IRC07:25
*** sshnaidm|afk has joined #openstack-meeting07:25
*** lpetrut has quit IRC07:26
*** shaohe_feng has quit IRC07:30
*** shaohe_feng has joined #openstack-meeting07:30
*** toscalix has joined #openstack-meeting07:33
*** manikanta_tadi has joined #openstack-meeting07:33
*** janki has joined #openstack-meeting07:33
*** mrunge has quit IRC07:33
*** jlanoux has joined #openstack-meeting07:34
*** zz_dimtruck is now known as dimtruck07:35
*** mbound has joined #openstack-meeting07:35
*** jlanoux has quit IRC07:36
*** pnavarro has joined #openstack-meeting07:37
*** lpetrut has joined #openstack-meeting07:37
*** jlanoux has joined #openstack-meeting07:37
*** fnaval has joined #openstack-meeting07:38
*** fnaval has quit IRC07:38
*** fnaval has joined #openstack-meeting07:39
*** dmacpher has quit IRC07:40
*** shaohe_feng has quit IRC07:40
*** shaohe_feng has joined #openstack-meeting07:40
*** aarefiev has joined #openstack-meeting07:43
*** dongfeng has quit IRC07:44
*** lbrune has joined #openstack-meeting07:44
*** obondarev has joined #openstack-meeting07:45
*** lpetrut has quit IRC07:46
*** dimtruck is now known as zz_dimtruck07:46
*** klkumar has quit IRC07:47
*** mrunge has joined #openstack-meeting07:48
*** klkumar has joined #openstack-meeting07:49
*** shaohe_feng has quit IRC07:50
*** shaohe_feng has joined #openstack-meeting07:51
*** mickeys has joined #openstack-meeting07:52
*** mickeys_ has joined #openstack-meeting07:53
*** mickeys_ has quit IRC07:55
*** yamahata has joined #openstack-meeting07:56
*** mickeys has quit IRC07:57
*** thorst has joined #openstack-meeting07:58
*** markvoelker has joined #openstack-meeting07:58
*** shaohe_feng has quit IRC08:00
*** shaohe_feng has joined #openstack-meeting08:01
*** hichihara has joined #openstack-meeting08:03
*** markvoelker has quit IRC08:04
*** spzala has joined #openstack-meeting08:04
*** thorst has quit IRC08:05
*** tangchen has quit IRC08:08
*** tangchen_ has quit IRC08:08
*** fbo has joined #openstack-meeting08:08
*** spzala has quit IRC08:09
*** edleafe has quit IRC08:10
*** mlekkas has quit IRC08:10
*** shaohe_feng has quit IRC08:11
*** shaohe_feng has joined #openstack-meeting08:12
*** marekd2 has joined #openstack-meeting08:14
*** achanda has joined #openstack-meeting08:16
*** mrvinti has quit IRC08:16
*** iyamahat has joined #openstack-meeting08:16
*** mrvinti has joined #openstack-meeting08:16
*** lekha has quit IRC08:16
*** mdenny has quit IRC08:16
*** hemna_ has joined #openstack-meeting08:16
*** adiantum has quit IRC08:17
*** shaohe_feng has quit IRC08:17
*** jpmaxman has quit IRC08:17
*** yamamoto has quit IRC08:17
*** darvon has quit IRC08:17
*** meteorfox has quit IRC08:17
*** nk2527 has quit IRC08:17
*** yamamoto has joined #openstack-meeting08:17
*** hemnafk has quit IRC08:17
*** rods has quit IRC08:17
*** amitgandhinz has joined #openstack-meeting08:18
*** yamahata has quit IRC08:18
*** strigazi has quit IRC08:18
*** jpmaxman has joined #openstack-meeting08:19
*** klkumar has quit IRC08:19
*** lekha has joined #openstack-meeting08:19
*** sileht has quit IRC08:19
*** shaohe_feng has joined #openstack-meeting08:19
*** clenimar has quit IRC08:19
*** DuncanT has quit IRC08:19
*** lbrune has quit IRC08:19
*** DuncanT has joined #openstack-meeting08:20
*** sridharg has quit IRC08:20
*** meteorfox has joined #openstack-meeting08:20
*** tangchen has joined #openstack-meeting08:20
*** tangchen_ has joined #openstack-meeting08:20
*** rods has joined #openstack-meeting08:20
*** sileht has joined #openstack-meeting08:21
*** jogo has quit IRC08:21
*** klkumar has joined #openstack-meeting08:21
*** darvon_ has joined #openstack-meeting08:21
*** shaohe_feng has quit IRC08:21
*** jogo has joined #openstack-meeting08:22
*** fungi has quit IRC08:22
*** shaohe_feng has joined #openstack-meeting08:22
*** neiljerram has joined #openstack-meeting08:22
*** sridharg has joined #openstack-meeting08:22
*** achanda has quit IRC08:22
*** amitgandhinz has quit IRC08:22
*** clenimar has joined #openstack-meeting08:23
*** fungi has joined #openstack-meeting08:24
*** neiljerram has quit IRC08:24
*** sshnaidm|afk is now known as sshnaidm08:24
*** ygbo has joined #openstack-meeting08:24
*** edleafe has joined #openstack-meeting08:26
*** links has quit IRC08:26
*** strigazi has joined #openstack-meeting08:26
*** iyamahat has quit IRC08:27
*** yassou has joined #openstack-meeting08:28
*** aloga has quit IRC08:28
*** aloga has joined #openstack-meeting08:28
*** greghaynes has quit IRC08:29
*** nk2527 has joined #openstack-meeting08:30
*** shaohe_feng has quit IRC08:31
*** shaohe_feng has joined #openstack-meeting08:32
*** zhhuabj has quit IRC08:33
*** Leo_ has joined #openstack-meeting08:36
*** asettle has joined #openstack-meeting08:40
*** isq_ has quit IRC08:40
*** greghaynes has joined #openstack-meeting08:41
*** mrmartin has joined #openstack-meeting08:41
*** Leo_ has quit IRC08:41
*** isq_ has joined #openstack-meeting08:41
*** zhonghua-lee has joined #openstack-meeting08:41
*** links has joined #openstack-meeting08:41
*** shaohe_feng has quit IRC08:41
*** shaohe_feng has joined #openstack-meeting08:42
*** xiangxinyong has joined #openstack-meeting08:42
*** neiljerram has joined #openstack-meeting08:45
*** lbrune has joined #openstack-meeting08:45
*** mbound has quit IRC08:47
*** saggi has joined #openstack-meeting08:48
*** yizhihui has joined #openstack-meeting08:48
*** shaohe_feng has quit IRC08:52
*** shaohe_feng has joined #openstack-meeting08:53
*** markvoelker has joined #openstack-meeting08:54
*** ihrachys has joined #openstack-meeting08:55
*** electrofelix has joined #openstack-meeting08:56
*** mbound has joined #openstack-meeting08:56
*** fzdarsky has joined #openstack-meeting09:00
saggi#startmeeting smaug09:00
openstackMeeting started Tue Aug  2 09:00:34 2016 UTC and is due to finish in 60 minutes.  The chair is saggi. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: smaug)"09:00
openstackThe meeting name has been set to 'smaug'09:00
saggiHi everyone09:00
*** markvoelker has quit IRC09:00
*** chenying has joined #openstack-meeting09:01
*** zengchen has joined #openstack-meeting09:01
saggiAre we waiting on anyone? yiwei, chenzeng, etc09:02
*** shaohe_feng has quit IRC09:02
*** lpetrut has joined #openstack-meeting09:02
*** ivc_ has joined #openstack-meeting09:02
*** shaohe_feng has joined #openstack-meeting09:03
*** thorst has joined #openstack-meeting09:03
yuvalchenzeng should be here, he wanted to discuss his suggestion09:03
chenyingyinwei is off the office today.09:03
saggiDo you guys know where everyone is?09:03
zhonghua-leeI am here :)09:04
zengchenyuval:as i descirbed on the launchpad, we may need to add a new executor09:04
*** zhangshuai has joined #openstack-meeting09:04
saggiOK let's start09:05
saggi#topic mascot selection09:05
*** openstack changes topic to "mascot selection (Meeting topic: smaug)"09:05
saggiWe didn't get the koala mascot09:05
saggiKolla won the coin toss09:05
zengchensaggi:i am online09:05
zhonghua-leeis there any option?09:05
*** spzala has joined #openstack-meeting09:05
saggiTheir name is also an alternative name for a Koala so they have the same claim on the animal.09:05
chenyingwe use Karbor as the name  or voting a new name?09:06
zhonghua-leeso we have to pick another one?09:06
saggiWe can change the name since we did not announce the name yet09:07
saggiWe suggested a tardigrade http://apod.nasa.gov/apod/ap130306.html which is the most resilient animal on earth.09:07
saggiNot as a name but a mascot09:07
*** lbrune has quit IRC09:07
zhonghua-leesaggi:what's that?09:07
*** acoles_ is now known as acoles09:07
*** zz_dimtruck is now known as dimtruck09:09
*** spzala has quit IRC09:10
zhonghua-leelooks good09:10
zhonghua-leeexcept looks like maggot09:10
zhonghua-leeforgive me09:10
*** thorst has quit IRC09:10
chenyingIt looks fearsome.09:10
saggiThat's the problem. It fits thematically but it not as cute.09:10
yuvalimo it is quite cute09:11
chenyingCan we pick another cute animal?09:11
saggiBut it needs to be somewhat related.09:11
zhonghua-leecan we use dragon?09:12
saggiThey don't allow mythical animals.09:12
*** shaohe_feng has quit IRC09:12
xiangxinyongI guess this animal is from the mars09:12
chenyingcan we use panda?09:12
saggiyuval: Where is the list of the taken mascots?09:13
*** shaohe_feng has joined #openstack-meeting09:13
yuvalthey just added another batch of taken mascots09:13
saggiThe problem with panda is that the name is to generic.09:13
saggiAnd that the WWF already uses it as a mascot09:14
*** zhangshuai_ has joined #openstack-meeting09:14
*** Ravikiran_K has joined #openstack-meeting09:14
xiangxinyongwhat about the glass crab?09:14
*** vhoward has joined #openstack-meeting09:14
yuvalbtw Quokka taken09:14
*** tochi has quit IRC09:14
xiangxinyongyizhihui: welcome to join the weekly meeting09:16
zhonghua-leecamel, good idea09:16
yizhihuior Black Mamba09:16
*** lbrune has joined #openstack-meeting09:17
*** zhangshuai has quit IRC09:17
*** tommylike_321 has joined #openstack-meeting09:18
chenyinggolden monkey09:18
zhonghua-leeI think we can not get the conclusion this time09:18
saggiPlease send suggestions if you have any.09:18
*** amitgandhinz has joined #openstack-meeting09:18
xiangxinyongI guess we can submit the mascot in this link. https://etherpad.openstack.org/p/smaugmascot09:18
chenyinghttp://s15.sinaimg.cn/mw690/65d9d9a5tx6CFUsY8z4be&690   golden monkey09:19
saggi#topic Add a new executor for Operation Engine service09:19
*** openstack changes topic to "Add a new executor for Operation Engine service (Meeting topic: smaug)"09:19
zhonghua-leesaggi: +109:19
*** dimtruck is now known as zz_dimtruck09:19
saggiping zengchen, this is your item09:20
openstackLaunchpad bug 1608415 in Smaug "Add a new executor for Operation Engine service" [High,Triaged] - Assigned to zengchen (chenzeng2)09:20
chenyingIt is better add the mascot with a picuter link.09:20
tommylike_321monkey +109:21
zengchendo you have seen it.09:21
*** pnavarro has quit IRC09:21
yuvalzengchen: sounds like a good idea09:21
*** mrmartin has quit IRC09:22
saggizengchen: It's a great idea09:22
saggiLooks simple enough to implement09:22
*** shaohe_feng has quit IRC09:22
saggiand have it retrofitted so we don't need the threaded one09:22
zengchenyuval:ok, if you all agree with it, i will try to implement it.09:22
*** amitgandhinz has quit IRC09:23
saggizengchen: will it come instead of the threaded one09:23
*** shaohe_feng has joined #openstack-meeting09:23
zengchensaggi:we can keep the thead, because we can set the config to choose which to be used.09:23
zhonghua-leeis it a addition or default?09:23
zengchenzhonghua-lee:i suggest to be default.09:24
saggiisn't the green thread one more powerful. Why would you want the threaded one?09:24
zhonghua-leezengchen: thanks09:24
chenyingI only care about the executor whether meet all the test scene of engine.09:24
*** tommylike_321 has quit IRC09:25
zengchensaggi:you mean delete the codes of thread?09:25
*** HeOS has quit IRC09:25
zengchensaggi:i suggest to wait a time. when the new executor runs, we can try to delete it.09:26
*** HeOS has joined #openstack-meeting09:26
saggizengchen: OK, but I'd rather not have a lot of code goes unused.09:26
*** ihrachys has quit IRC09:27
*** aeng has joined #openstack-meeting09:27
zengchensaggi:ok, i will keep the codes clean.09:27
*** lbrune has left #openstack-meeting09:27
saggi# topic Scheduled Operation Improvements Proposal09:27
saggiping xiangxinyong09:27
xiangxinyonghello saggi09:27
xiangxinyongcould you take a look at this link?09:28
saggiI already did09:28
*** gsagie has joined #openstack-meeting09:28
*** links has quit IRC09:28
gsagieSo what is Smaug mascot?09:28
xiangxinyongsaggi:what do you think about it?09:29
*** gongysh has joined #openstack-meeting09:29
chenyingWe will add the suggested mascot to the link.09:29
saggiIt's fine by me as long as you can set retention time and max checkpoint to be infinite09:29
zhonghua-leeI think it's reasonable to add the description09:29
saggigsagie: We already selected a mascot: https://media.licdn.com/media/p/2/000/18e/3dd/1d99b9c.jpg09:30
*** aeng has quit IRC09:30
xiangxinyongyeah. i need to add description into scheduled operation09:30
yuvalsaggi: :P:09:30
saggixiangxinyong: +109:31
saggiThe rest can be added if they are optional09:31
xiangxinyongsaggi: about retention_duration and max_backups09:31
*** gongysh has quit IRC09:31
chenyingadd description into scheduled operation--- I also think add the description filed to other resources. like plan resotre09:31
xiangxinyongyeah. description is optinal09:31
saggichenying: Also retention and max_backups09:32
*** mrmartin has joined #openstack-meeting09:32
saggishould be optional09:32
chenyingname  and  description field have different meaning.09:32
saggixiangxinyong: I think we are all in agreement that these are good additions as long as they are optional.09:33
*** shaohe_feng has quit IRC09:33
chenyingyes it is optional09:33
saggiIs retention time per checkpoint?09:33
xiangxinyongbut how to implement max_backups and retention_duration for scheduled operation?09:33
*** shaohe_feng has joined #openstack-meeting09:33
xiangxinyongdo you have some suggestions?09:33
zhonghua-leeadd new Operation?09:34
*** e0ne has joined #openstack-meeting09:34
saggiYou run the operation periodically looking for checkpoints that you created that are older than duration.09:34
saggiYou will need to keep record of all created checkpoints in the operation db since querying the bank is slow.09:34
yuvalI don't understand: if I manually create a checkpoint, and then later a scheduled operation is defined with max_backups, it may delete my checkpoint?09:35
saggiIf it was created by this operation09:35
xiangxinyongI guess we need to launch a delete checkpoint request from the operation engine service09:35
zhonghua-leesaggi: who will trigger this operation? Operation engine?09:35
saggiSince it's policy09:36
xiangxinyongI guess operation engine service will trigger09:36
chenyingall  retention time and max backups are the parameters of policys.09:36
xiangxinyongOK. I will write a spec about this features09:37
xiangxinyongthanks guys09:38
chenyingxiangxinyong:+1 need a spec about these parameters.09:38
zhonghua-leexiangxinyong: some guys may want to know the detaild flow09:38
yuvalHow will the scheduled operation find all the checkpoints?09:38
yuvaloriginated from it?09:38
chenyingcall the list checkpoint api09:38
saggiyuval: When it creates the checkpoint it will need to keep the ID returned09:39
yuvalchenying: and list ALL checkpoints?09:39
yuvalchenying: we don't have filter on metadata09:39
yuvalsaggi: keep where?09:39
saggioperation engine db09:39
xiangxinyongyuval: but i guess we filter it by plan09:39
saggiSince it's local09:39
*** links has joined #openstack-meeting09:40
chenyingmake sure we have save the checkpoint id to the operation engine db09:40
chenying not the operation engine db some operation db table.09:40
zhonghua-leexiangxinyong: do you consider the use case: user can create it manually09:40
zengcheni suggest xiangxinyong give a complete desgin.09:41
saggiDon't design anything that filters the checkpoints. It won't scale until we decide on a querying mechanism. This will only happen for P-version, not Newton.09:41
saggizengchen: +109:41
xiangxinyongzhonghua-lee: yeah. The requirement is only about the scheduled protection09:41
xiangxinyongOK.guys. I will specify a spec about this feature09:42
zhonghua-leexiangxinyong: so it is just a policy, not for the protection resource09:42
saggi#action xiangxinyong write a BP on advance backup policy09:42
saggi#topic Volume OPTIONS_SCHEMA Improvements Proposal09:42
*** openstack changes topic to "Volume OPTIONS_SCHEMA Improvements Proposal (Meeting topic: smaug)"09:42
*** shaohe_feng has quit IRC09:43
saggiDon't Huawei implement this through Cinder Backup?09:43
chenyingi note that SAVE_SCHEMA not being used when creat checkpoint data.09:43
xiangxinyongsaggi: there is some differenece09:44
*** shaohe_feng has joined #openstack-meeting09:44
xiangxinyongwe could add emc volume plugin or eisoo volume plugin.09:44
xiangxinyongguys,please review it. thanks09:45
saggixiangxinyong: I would like to have everything else in the reference implementation working perfectly before adding new protection plugins.09:45
saggiAlso we need these to be tested as well09:45
saggiI the full stack tests09:45
yuvalxiangxinyong: you want these to be added to the default cinder protection plugin?09:46
*** epico has quit IRC09:47
xiangxinyongyuval: yeah. I want to add a new protection volume plugin09:47
saggixiangxinyong: Id09:48
*** dixiaoli has quit IRC09:48
saggixiangxinyong: I'd rather wait with alternative plugins until we have everything we gurantee for v1 solid..09:48
zhonghua-leesaggi: do we accept other vendors to join us?09:49
*** markvoelker has joined #openstack-meeting09:49
xiangxinyongsaggi: good suggestions09:49
saggizhonghua-lee: Sure, everyone is invited09:49
zhonghua-leeespacially the backup vendors09:50
zhonghua-leesaggi: :)09:50
saggiAnd if they spend the time on their plugins it's OK. But we, as the core team, should concentrate on the core for now.09:50
chenyingI think verdor can add their plugins. Like backup software verdor can add ther plugins.09:50
saggiWe also need to take the Cinder route and only accept plugins with proper tests and CI09:50
zhonghua-leesaggi: OK09:51
saggiOtherwise we have to do all the testing ourselves, which doesn't scale.09:51
*** ajmiller has quit IRC09:51
*** ajmiller has joined #openstack-meeting09:52
zhonghua-leeaccording the conclusion, I think we prefer to delay this proposal09:52
yizhihuiwhen will v1 solid?09:53
*** shaohe_feng has quit IRC09:53
saggiWhen N is stable hopefully09:53
saggiThat the target09:53
*** shaohe_feng has joined #openstack-meeting09:54
zhonghua-leeyizhihui: why you ask this question?09:54
zhonghua-leeyizhihui: do you have any plan to add your plug-in?09:54
saggiIf we get there sooner we can tag and start building v2. BTW, v2 roadmap will be discussed at Bacelona.09:55
chenying<yizhihui is from a backup software vendors. They plan to develop a new plugin about app backup.09:55
zhonghua-leesaggi: yizhihui: I guess you can add it as you please09:56
*** yassou has quit IRC09:56
saggiroadmap is here https://etherpad.openstack.org/p/smaug09:56
zhonghua-leesaggi: what's your opinion?09:56
*** markvoelker has quit IRC09:56
saggizhonghua-lee: about what?09:56
*** adiantum has joined #openstack-meeting09:56
zhonghua-leesaggi: yizhihui is from 3rd backup vendor, he wants to add a plug-in into Smaug09:56
zhonghua-leesaggi: can he add it now?09:57
*** epico has joined #openstack-meeting09:57
saggiYou can add anything to Ocata. it's just candidates09:57
saggiWe will filter the list in Barcelona09:57
saggiWe will accept 3rd party plugin code even now. But we can't gurantee it will ship as supported in N.09:59
saggiAlso, it will require dedication as things are moving fast and breakage may oocure in the plugin interface before N.09:59
yizhihuisaggi: I got it09:59
zhonghua-leesaggi: +109:59
saggiWe are out of time10:00
saggi#topic open discussion10:00
*** openstack changes topic to "open discussion (Meeting topic: smaug)"10:00
saggiany last words?10:00
*** gsagie has left #openstack-meeting10:01
saggiThank you everybody10:01
xiangxinyonggood bye10:01
saggiyizhihui: Hope to see you next time as well10:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"10:01
openstackMeeting ended Tue Aug  2 10:01:23 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/smaug/2016/smaug.2016-08-02-09.00.html10:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/smaug/2016/smaug.2016-08-02-09.00.txt10:01
openstackLog:            http://eavesdrop.openstack.org/meetings/smaug/2016/smaug.2016-08-02-09.00.log.html10:01
yizhihuiI'd like to10:01
*** sdague has joined #openstack-meeting10:02
*** yizhihui has quit IRC10:03
*** shaohe_feng has quit IRC10:03
*** shaohe_feng has joined #openstack-meeting10:04
*** spzala has joined #openstack-meeting10:06
*** yamamoto has quit IRC10:06
*** bcafarel has quit IRC10:08
*** thorst has joined #openstack-meeting10:08
*** dmorita has joined #openstack-meeting10:09
*** zhurong has quit IRC10:10
*** spzala has quit IRC10:11
*** dmorita has quit IRC10:13
*** shaohe_feng has quit IRC10:14
*** shaohe_feng has joined #openstack-meeting10:14
*** thorst has quit IRC10:15
*** mikelk has quit IRC10:18
*** mikelk has joined #openstack-meeting10:18
*** amitgandhinz has joined #openstack-meeting10:19
*** achanda has joined #openstack-meeting10:20
*** zhangshuai_ has quit IRC10:22
*** amitgandhinz has quit IRC10:24
*** shaohe_feng has quit IRC10:24
*** Leo_ has joined #openstack-meeting10:24
*** shaohe_feng has joined #openstack-meeting10:25
*** achanda has quit IRC10:26
*** jlanoux has quit IRC10:26
*** jlanoux has joined #openstack-meeting10:27
*** asettle has quit IRC10:28
*** Kevin_Zheng has quit IRC10:28
*** epico has quit IRC10:29
*** Leo_ has quit IRC10:29
*** ntpttr- has quit IRC10:30
*** Kevin_Zheng has joined #openstack-meeting10:30
*** shaohe_feng has quit IRC10:34
*** shaohe_feng has joined #openstack-meeting10:35
*** rodrigods has quit IRC10:36
*** rodrigods has joined #openstack-meeting10:36
*** sudipto has quit IRC10:38
*** ntpttr- has joined #openstack-meeting10:39
*** asettle has joined #openstack-meeting10:40
*** tangchen_ has quit IRC10:42
*** tangchen has quit IRC10:42
*** asettle has quit IRC10:43
*** jlanoux has quit IRC10:43
*** zhhuabj has joined #openstack-meeting10:43
*** jlanoux has joined #openstack-meeting10:44
*** asettle has joined #openstack-meeting10:44
*** shaohe_feng has quit IRC10:44
*** tangchen_ has joined #openstack-meeting10:44
*** mrmartin has quit IRC10:44
*** markvoelker has joined #openstack-meeting10:45
*** tangchen has joined #openstack-meeting10:45
*** shaohe_feng has joined #openstack-meeting10:45
*** darvon_ is now known as darvon10:45
*** neiljerram has quit IRC10:51
*** markvoelker has quit IRC10:51
*** yamamoto has joined #openstack-meeting10:52
*** kaminohana has joined #openstack-meeting10:52
*** ihrachys has joined #openstack-meeting10:54
*** shaohe_feng has quit IRC10:55
*** shaohe_feng has joined #openstack-meeting10:55
*** mrmartin has joined #openstack-meeting10:58
*** mbound has quit IRC10:58
*** obondarev has quit IRC11:02
*** ljxiash_ has quit IRC11:03
*** shaohe_feng has quit IRC11:05
*** ljxiash has joined #openstack-meeting11:06
*** shaohe_feng has joined #openstack-meeting11:06
*** spzala has joined #openstack-meeting11:07
*** sudipto has joined #openstack-meeting11:08
*** neiljerram has joined #openstack-meeting11:09
*** ljxiash has quit IRC11:10
*** sshnaidm is now known as sshnaidm|afk11:10
*** zz_dimtruck is now known as dimtruck11:10
*** weshay has quit IRC11:11
*** spzala has quit IRC11:11
*** thorst has joined #openstack-meeting11:12
*** ihrachys has quit IRC11:13
*** shaohe_feng has quit IRC11:15
*** shaohe_feng has joined #openstack-meeting11:16
*** yassine has joined #openstack-meeting11:18
*** hrybacki|appt is now known as hrybacki11:18
*** yassine is now known as Guest2619411:18
*** amitgandhinz has joined #openstack-meeting11:20
*** dimtruck is now known as zz_dimtruck11:20
*** thorst has quit IRC11:20
*** ljxiash has joined #openstack-meeting11:23
*** amitgandhinz has quit IRC11:25
*** shaohe_feng has quit IRC11:25
*** shaohe_feng has joined #openstack-meeting11:26
*** sdake has joined #openstack-meeting11:27
*** ljxiash has quit IRC11:27
*** ihrachys has joined #openstack-meeting11:29
*** sdake_ has joined #openstack-meeting11:30
*** manikanta_tadi has quit IRC11:30
*** thorst has joined #openstack-meeting11:30
*** sdake has quit IRC11:31
*** tangchen has quit IRC11:32
*** claudiub has joined #openstack-meeting11:32
*** liamji has quit IRC11:32
*** Kiall has quit IRC11:34
*** rtheis has joined #openstack-meeting11:34
*** shaohe_feng has quit IRC11:36
*** Kiall has joined #openstack-meeting11:36
*** shaohe_feng has joined #openstack-meeting11:36
*** bcafarel has joined #openstack-meeting11:37
*** matrohon has joined #openstack-meeting11:39
*** markvoelker has joined #openstack-meeting11:39
*** ihrachys has quit IRC11:41
*** rfolco_ has joined #openstack-meeting11:41
*** obondarev has joined #openstack-meeting11:43
*** markvoelker_ has joined #openstack-meeting11:44
*** markvoelker has quit IRC11:44
*** thorst has quit IRC11:46
*** shaohe_feng has quit IRC11:46
*** shaohe_feng has joined #openstack-meeting11:47
*** tangchen has joined #openstack-meeting11:48
*** reedip has quit IRC11:51
*** sdake_ is now known as sdake11:51
*** sshnaidm|afk is now known as sshnaidm11:52
*** dprince has joined #openstack-meeting11:55
*** shaohe_feng has quit IRC11:56
*** jungleboyj has joined #openstack-meeting11:56
*** weshay has joined #openstack-meeting11:57
*** shaohe_feng has joined #openstack-meeting11:57
*** reedip has joined #openstack-meeting11:59
*** rossella_s has quit IRC12:00
*** rossella_s has joined #openstack-meeting12:00
*** uxdanielle has joined #openstack-meeting12:02
*** sindhu has joined #openstack-meeting12:03
*** ihrachys has joined #openstack-meeting12:04
*** shaohe_feng has quit IRC12:06
*** zhurong has joined #openstack-meeting12:07
*** shaohe_feng has joined #openstack-meeting12:07
*** alyson_ has joined #openstack-meeting12:08
*** Guest52823 is now known as honza12:08
*** neiljerram has quit IRC12:08
*** sindhu has quit IRC12:09
*** honza is now known as Guest864412:09
*** manikanta_tadi has joined #openstack-meeting12:10
*** phil_h has left #openstack-meeting12:10
*** obondarev has quit IRC12:11
*** zhurong has quit IRC12:11
*** numans has quit IRC12:12
*** matrohon has quit IRC12:12
*** Leo_ has joined #openstack-meeting12:13
*** manikanta_tadi has quit IRC12:14
*** zhurong has joined #openstack-meeting12:14
*** yamamoto has quit IRC12:15
*** yamamoto has joined #openstack-meeting12:15
*** shaohe_feng has quit IRC12:17
*** Leo_ has quit IRC12:17
*** baoli has joined #openstack-meeting12:18
*** shaohe_feng has joined #openstack-meeting12:18
*** maeca1 has joined #openstack-meeting12:18
*** baoli_ has joined #openstack-meeting12:18
*** zhurong has quit IRC12:19
*** zhurong has joined #openstack-meeting12:19
*** yamamoto has quit IRC12:21
*** amitgandhinz has joined #openstack-meeting12:21
*** ihrachys has quit IRC12:22
*** baoli has quit IRC12:22
*** uxdanielle has quit IRC12:23
*** achanda has joined #openstack-meeting12:24
*** amitgandhinz has quit IRC12:25
*** shaohe_feng has quit IRC12:27
*** shaohe_feng has joined #openstack-meeting12:28
*** achanda has quit IRC12:29
*** adrianofr has joined #openstack-meeting12:30
*** xyang1 has joined #openstack-meeting12:31
*** zul has quit IRC12:32
*** hoangcx has joined #openstack-meeting12:32
*** zul has joined #openstack-meeting12:32
*** shaohe_feng has quit IRC12:37
*** shaohe_feng has joined #openstack-meeting12:38
*** thorst has joined #openstack-meeting12:40
*** yamamoto has joined #openstack-meeting12:41
*** toddjohn has joined #openstack-meeting12:41
*** numans has joined #openstack-meeting12:42
*** toddjohn has quit IRC12:43
*** toddjohn has joined #openstack-meeting12:44
*** bobh has joined #openstack-meeting12:44
*** lblanchard has joined #openstack-meeting12:47
*** shaohe_feng has quit IRC12:47
*** janki has quit IRC12:48
*** links has quit IRC12:48
*** shaohe_feng has joined #openstack-meeting12:48
*** janki has joined #openstack-meeting12:48
*** xiaohhui has joined #openstack-meeting12:49
*** dane_leblanc has joined #openstack-meeting12:50
*** xiaohhui has quit IRC12:51
*** xiaohhui has joined #openstack-meeting12:51
*** bobh has quit IRC12:52
*** trozet has joined #openstack-meeting12:53
*** dane_leblanc_ has joined #openstack-meeting12:54
*** zz_dimtruck is now known as dimtruck12:56
*** jungleboyj has quit IRC12:56
*** xiaohhui has quit IRC12:56
*** dane_leblanc has quit IRC12:57
*** liyifeng has quit IRC12:57
*** haiwei_ has joined #openstack-meeting12:58
*** shaohe_feng has quit IRC12:58
*** lixinhui_ has joined #openstack-meeting12:58
*** shaohe_feng has joined #openstack-meeting12:58
*** tpsilva_ has joined #openstack-meeting12:58
*** tpsilva_ is now known as tpsilva12:59
Qiming#startmeeting senlin13:00
openstackMeeting started Tue Aug  2 13:00:36 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
*** yanyanhu has joined #openstack-meeting13:01
Qimingevening, xinhui, haiwei13:01
yanyanhusorry I'm late13:01
Qiminghi, yanyan13:01
*** ljxiash has joined #openstack-meeting13:01
Qimingpls review agenda and see if you got items to add13:02
Qiming#link https://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Weekly_Senlin_.28Clustering.29_meeting13:02
Qimingfirst item, newton work items13:02
*** mtanino has joined #openstack-meeting13:02
Qiming#topic newton work items13:02
*** openstack changes topic to "newton work items (Meeting topic: senlin)"13:02
*** Raildo has joined #openstack-meeting13:02
Qiming#link https://etherpad.openstack.org/p/senlin-newton-workitems13:02
*** bvandenh has quit IRC13:03
*** cschulz has joined #openstack-meeting13:03
Qimingupdates ?13:03
yanyanhurally plugin13:03
yanyanhuthe patch for rally side is still in progress, will check and fix latest issues tomorrow morning13:04
yanyanhuhope can finish it soon13:04
Qimingokay, just got some comments from Roman ...13:04
yanyanhufor senlin repo, plugin for cluster scaling has been proposed13:04
yanyanhuQiming, yes13:04
yanyanhuneed quick fix and also some explanation13:05
Qiminginteresting ... we are still exposing 'parent' to client?13:05
yanyanhuthe one for cluster scaling13:05
yanyanhuI guess there is still some out of date msg in doc?13:05
*** obondarev has joined #openstack-meeting13:06
Qimingokay, it has been hanging there for some days13:06
yanyanhuwill check it and reply to roman13:06
*** toddjohn has quit IRC13:06
Qimingsounds great13:06
yanyanhuyes, hope can complete it soon13:06
Qimingmaybe we can ask some helps from cmcc13:06
*** toddjohn has joined #openstack-meeting13:06
Qimingdon't know eldon can offer a hand13:06
yanyanhuQiming, yes, I think we can ask them for some use case reference13:07
yanyanhufor coding, it's ok for me since13:07
yanyanhuthere is no critical issue left I feel13:07
yanyanhuanyway, will keep working on it13:07
Qiminganything else in this space?13:07
yanyanhunope I think13:08
Qimingmoving on13:08
lixinhui_About Fencing13:08
*** shaohe_feng has quit IRC13:08
Qiminghealth management, no progress from my side last week13:08
lixinhui_I add some points on Qiming's HA etherpad13:08
*** spzala has joined #openstack-meeting13:09
*** shaohe_feng has joined #openstack-meeting13:09
*** clenimar has quit IRC13:09
lixinhui_First step is to target fencing nova compute service13:09
*** ericksonsantos has quit IRC13:09
lixinhui_Second step is fencing of vm13:09
lixinhui_for compute service fencing13:09
*** gabriel-bezerra has quit IRC13:09
lixinhui_which should happen when some host failure happens13:10
Qimingthat is actually abouf fencing a nova compute node, correct?13:10
lixinhui_Yes, Qiming13:10
QimingI don't have a multi-node setup at hand13:10
*** clenimar has joined #openstack-meeting13:10
Qimingcannot produce a compute node failure to observe the host failure events13:10
*** toddjohn has quit IRC13:10
lixinhui_So I wonder if proper to add this into healthmonitor13:10
Qiminghave you got any hints on that? either by digging into the source or doc or thru experimentation?13:11
*** gabriel-bezerra has joined #openstack-meeting13:11
*** mkoderer_cloud has joined #openstack-meeting13:11
lixinhui_compute node failure can only be known by polling service status13:11
Qimingobserving host failure could only be done thru events13:11
*** gjayavelu has joined #openstack-meeting13:11
*** ericksonsantos has joined #openstack-meeting13:12
QimingI'm a little reluctant to poll nova compute services13:12
lixinhui_Nova today use heartbeat to know if host is alive or not13:12
Qimingthat is their internals13:12
*** yanyanhu has quit IRC13:12
*** Guest8644 is now known as honza13:12
Qimingwe are not supposed to peek into that13:12
lixinhui_There are only two types of event for nova to notice13:13
lixinhui_one if the node.update13:13
*** spzala has quit IRC13:13
*** yanyanhu has joined #openstack-meeting13:13
lixinhui_the other is service.update13:13
QimingIIRC, nova has event reports when a host fails13:13
Qimingokay, then we can listen to those events13:14
lixinhui_Service.update can be sent only when the change happen on the nova services by nova service*13:14
Qimingdon't understand13:14
lixinhui_you can read the code of nova/objects/service13:15
*** spzala has joined #openstack-meeting13:15
Qimingcan you pls just explain your last sentence?13:15
lixinhui_my experiments proove this13:15
lixinhui_that means the up or down of nova services will be changes based on heatbeat without notice13:16
lixinhui_but service.update will be sent when I enable or disable some serivce13:16
Qimingokay, those are the nova internal state maintenance, we cannot check it from outside13:16
Qimingif nova-compute is down, no event notification is sent?13:17
lixinhui_after two cycle13:17
lixinhui_the serivce becomes down13:17
lixinhui_that is all13:17
lixinhui_after detection that, we can fencing the compute13:18
Qiminggood/bad to know ...13:18
*** shaohe_feng has quit IRC13:18
Qimingsounds like the only way for failure detection is polling?13:18
Qimingneed to double check that13:18
Qimingthat was my understanding13:19
lixinhui_or read the status of nova service13:19
Qimingbut last time in a mailinglist discussion, I raised this question13:19
lixinhui_that would be good if you can double check13:19
Qimingsomeone told me that nova is already capable of sending out notifications when a compute service is down13:19
QimingI hope I have ten heads13:20
Qimingneed to dig that email13:20
Qimingor the source code13:20
*** bobh has joined #openstack-meeting13:20
Qiming#action Qiming to double check nova's capability of notifying host down13:21
lixinhui_they indeed add some notices13:21
Qimingmoving on13:21
*** links has joined #openstack-meeting13:21
Qimingdocumentation side13:21
*** shaohe_feng has joined #openstack-meeting13:21
Qimingadded some user references docs last week13:21
Qimingmainly a reorg around auto-scaling, receivers ... etc13:21
*** amitgandhinz has joined #openstack-meeting13:22
QimingI was thinking of adding a tutorial about auto-scaling, but later I realized that is a huge topic, not suitable for a tutorial, which is supposed to be pretty short13:22
QimingI have also moved the heat based autoscaling under a scenarios subdirectory13:23
Qimingwhere in future we can add more scenarios for references13:23
*** markvoelker_ has quit IRC13:23
*** dane_leblanc_ has quit IRC13:23
Qimingwill check if tutorial doc can be left there ...13:24
Qimingnext ...13:24
Qimingyanyan just started adding version control to profile and policy specs13:24
*** cleong has joined #openstack-meeting13:24
Qimingthis is necessary, pls help review13:24
yanyanhuyes, just proposed the first patch https://review.openstack.org/34870913:24
*** jckasper has quit IRC13:25
yanyanhuto add version support to schema and spec13:25
Qimingin parallel, I'm looking into oslo.versionedobjects for a more wholistic solution13:25
Qimingwill update later13:25
*** jckasper has joined #openstack-meeting13:25
Qimingmoving on ...13:25
yanyanhumy pleasure. Really need some discussion about this topic13:25
Qimingcontainer profile support13:25
*** julim has joined #openstack-meeting13:26
Qiminghaiwei just pushed a commit: https://review.openstack.org/#/c/34990613:26
*** amitgandhinz has quit IRC13:26
*** julim has quit IRC13:26
*** jckasper has quit IRC13:27
haiwei_yes, Qiming13:27
QimingI haven't got time to review13:27
haiwei_I only tested it partly13:27
Qimingjust a quick glance13:27
Qimingteam, please take a look at it and help polish it when you got cycles13:27
yanyanhusure, will check it13:28
*** liamji has joined #openstack-meeting13:28
Qimingmoving on13:28
haiwei_I think the point for that patch is where should we store 'host_node' uuid? in that patch I stored it in the metadata of profile13:28
*** mriedem has joined #openstack-meeting13:28
*** shaohe_feng has quit IRC13:28
Qimingmaybe node.data ?13:29
Qimingif you check other policy decisions such as zone placement, region placement ...13:29
*** shaohe_feng has joined #openstack-meeting13:29
haiwei_ok, I will think about it13:29
Qimingwe are injecting data into the 'data' field of the node (abstract one)13:29
Qimingthen when we are about to create the physical resource, we extract those policy decisions13:30
Qimingprofile metadata was designed for users to use13:30
haiwei_in service layer we got host_node, but it is not the server's id, so we need to pass server's id to profile13:30
Qiminge.g. {'author': 'haiwei', 'last-updated': '2016-08-02', ... } etc13:31
Qimingwe can pass those information in node.data field13:31
*** dimtruck is now known as zz_dimtruck13:31
*** efried has joined #openstack-meeting13:31
*** zz_dimtruck is now known as dimtruck13:31
haiwei_I will check it later13:31
Qimingthe node.data field was designed to carry those data around13:31
Qimingpls also think if we can move the policy decision out into a policy type13:32
*** sindhu has joined #openstack-meeting13:32
Qiming1. that will make the engine code cleaner; 2. we could later improve/replace that policy type implementation easily13:33
haiwei_what policy decision?13:33
*** julim has joined #openstack-meeting13:33
haiwei_currently I am thinking about node_create13:33
Qimingby "policy decision" I mean the selection of node in a hosting cluster13:33
*** irenab has quit IRC13:34
Qimingjust something to keep in mind, I'm not sure how feasible it is without digging into the code13:34
*** lixinhui_ has quit IRC13:34
*** rbowen has quit IRC13:34
Qiminggreat, moving on13:34
Qimingzaqar based receiver13:34
Qimingyanyan has been busy working on that ...13:35
yanyanhuyes, have confirmed with zaqar team again about the usage of "project_id" and "client_id" today13:35
*** mbound has joined #openstack-meeting13:35
yanyanhujust as you said, we should expose them out for invoker of sdk proxy call13:35
yanyanhuhave post the latest result in the follow patches:   * https://review.openstack.org/34936913:36
yanyanhu   * https://review.openstack.org/33804113:36
Qimingokay, the thing to bear in mind is ...13:36
Qimingif you put 'client_id = Header('Client-ID') in that Message class13:37
Qimingthe header still won't appear in the final request ...13:37
Qimingthat is something I missed when reviewing your last patch13:37
yanyanhuoverriding resource calls will make it take effect I think?13:38
Qimingso ... your way of overriding those methods are still valid, though there are rooms for improvement13:38
yanyanhulike the latest patch does13:38
yanyanhureally not graceful way13:38
Qimingit is ugly, but ... you know, people need time to understand the issue we are facing13:38
*** lixinhui_ has joined #openstack-meeting13:38
*** shaohe_feng has quit IRC13:39
Qimingwe should allow custom headers in all those create, get, list calls13:39
yanyanhuhope brian can figure it out when building resource213:39
yanyanhuusing better way13:39
Qimingresource2 is already there ...13:39
yanyanhuif so, that will be much better13:39
yanyanhuQiming, it still needs some improvement I think13:39
Qimingbut he doesn't seem buy in the idea of adding more parameters13:39
yanyanhufor those "corner" use cases13:40
*** shaohe_feng has joined #openstack-meeting13:40
Qimingthanks for keeping the balls rolling13:40
Qimingwill review your new patchset tomorrow13:40
yanyanhuthanks a lot13:40
Qimingmoving on13:40
*** mbound has quit IRC13:40
Qimingno update from me in this space13:40
*** dimtruck is now known as zz_dimtruck13:41
Qimingactually I was trapped in a more general issue .... versioning of things13:41
*** mtanino has quit IRC13:41
Qimingokay, next topic13:41
Qiming#topic newton deliverables13:41
*** openstack changes topic to "newton deliverables (Meeting topic: senlin)"13:41
*** dane_leblanc_ has joined #openstack-meeting13:41
*** kei_ has joined #openstack-meeting13:42
Qimingthough I've been digging into the issue of versioning of things, I don't think we can get it done by this cycle13:42
Qimingon the other hand, the new features about cluster-collect and cluster-do will have to base on micro-version support13:43
*** cdelatte has joined #openstack-meeting13:43
Qimingwhich is also blocked here: https://review.openstack.org/#/c/343992/13:43
*** zhurong has quit IRC13:43
*** merooney has joined #openstack-meeting13:43
*** kei has quit IRC13:43
Qimingstill need time to convince brian that the current patch is already okay13:43
yanyanhuthis part is really complicated...13:44
Qimingthe overall design and impl is good, there are some trivial coding style things for communication13:44
Qiminghealth policy implementation ...13:44
*** toddjohn has joined #openstack-meeting13:44
QimingI do hope we can deliver a basic, working version by this cycle13:45
Qimingas for container cluster13:45
*** rbowen has joined #openstack-meeting13:45
yanyanhureally need to achieve that goal I feel13:45
Qimingit would be GREAT we can have a basic, working version13:45
*** cschulz has quit IRC13:45
Qimingyes, people are asking questions on that13:45
Qiminglet's keep working hard on this13:46
*** xiaohhui has joined #openstack-meeting13:46
Qimingnext topic I added is about versioned objects13:46
Qimingwhen adding new properties to policy (e.g. the lb policy revision lately)13:46
*** uxdanielle has joined #openstack-meeting13:47
Qimingwe need to bump policy version13:47
Qimingso ... we have a lot of things to be versioned13:47
Qiming1. API micro-version13:47
Qiming2. API request body version13:47
Qiming3. API response version13:47
Qiming4. RPC version13:47
Qiming5. DB object version13:48
Qiming6. Event/Notification version13:48
Qiming7, Policy type version13:48
Qiming8. Profile type version13:48
*** xiaohhui has quit IRC13:48
*** namnh has joined #openstack-meeting13:48
Qiming9. Receiver version13:48
Qimingwithout proper versioning infra at hand, we will quickly loose control of things13:49
*** xiaohhui has joined #openstack-meeting13:49
yanyanhuQiming, yes, almost every elements that could vary over time13:49
Qimingand things will break in a thousand ways13:49
*** shaohe_feng has quit IRC13:49
Qimingso... I'm investigating oslo.versionedobjects, every single line of code there13:49
Qimingand also jsonschema doc/implementation13:49
*** sindhu has quit IRC13:50
*** shaohe_feng has joined #openstack-meeting13:50
QimingI think I have got a rough idea on how to unify all object versioning into the same framework13:50
*** hoangcx has quit IRC13:50
Qimingbut that warrants a lot of experimentation and code churn13:50
*** zhipeng has joined #openstack-meeting13:50
Qimingwill leave that as a long term work, maybe by end of Ocata we will have this framework completely landed13:51
*** hoangcx has joined #openstack-meeting13:51
Qimingideally, after that, when you want to add a new property to an existing resource13:51
*** lixinhui_ has quit IRC13:51
*** zhurong has joined #openstack-meeting13:51
Qimingyou won't need to modify a few hundred lines of code while still worrying about breaking existing users13:52
yanyanhugreat, we can add version support for different elements gradually I think13:52
Qimingsome preliminary code have proved the feasibility of this13:52
Qimingwe can even make the api-ref documentation generated out of these objects13:53
*** rubasov has joined #openstack-meeting13:53
yanyanhustart from most basic part and keep it in mind when making changes on those "unversioned" stuff13:53
*** xiaohhui has quit IRC13:53
*** jlibosva has joined #openstack-meeting13:53
Qimingso that is my update in this thread13:53
*** annp has joined #openstack-meeting13:54
QimingI didn't leave any time for questions/comments13:54
*** regXboi has joined #openstack-meeting13:54
*** yottatsa has joined #openstack-meeting13:54
Qiming#topic open discussion13:54
*** openstack changes topic to "open discussion (Meeting topic: senlin)"13:54
*** nmagnezi has quit IRC13:54
yanyanhuno problem, will check the code :)13:54
*** mlavalle has joined #openstack-meeting13:54
yanyanhuvoting is open now :)13:54
yanyanhugood luck for senlin's topic13:54
*** ralonsoh has joined #openstack-meeting13:55
*** jckasper has joined #openstack-meeting13:55
Qimingthis is a very strange document to read ... http://json-schema.org/latest/json-schema-validation.html13:55
*** e0ne has quit IRC13:55
*** rbak has joined #openstack-meeting13:56
Qimingand that is their most comprehensive one I guess .... :)13:56
yanyanhureally hope we are native eng speaker :)13:56
Qiminghi, namnh13:56
*** john-davidge has joined #openstack-meeting13:57
*** korzen has joined #openstack-meeting13:57
*** sindhu has joined #openstack-meeting13:57
*** dasanind has joined #openstack-meeting13:57
Qiminganything else?13:57
yanyanhunope from me13:57
*** ebalduf has joined #openstack-meeting13:58
Qimingseems lixinhui has dropped13:58
*** e0ne has joined #openstack-meeting13:58
yanyanhuwill over time soon13:58
Qimingbut anyway I will look into the nova code13:58
Qimingthanks, guys13:59
Qiminglet's meet next week13:59
yanyanhuthanks, have a good night13:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:59
*** JoseMello has joined #openstack-meeting13:59
openstackMeeting ended Tue Aug  2 13:59:28 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-08-02-13.00.html13:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-08-02-13.00.txt13:59
*** xiaohhui has joined #openstack-meeting13:59
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-08-02-13.00.log.html13:59
*** shaohe_feng has quit IRC13:59
HenryGHello neutrinos13:59
HenryG#startmeeting networking14:00
openstackMeeting started Tue Aug  2 14:00:01 2016 UTC and is due to finish in 60 minutes.  The chair is HenryG. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
*** haiwei_ has quit IRC14:00
*** shaohe_feng has joined #openstack-meeting14:00
*** janzian has joined #openstack-meeting14:00
*** hynekm has joined #openstack-meeting14:00
ajoo/ :)14:00
*** Sam-I-Am has joined #openstack-meeting14:00
*** pc_m has joined #openstack-meeting14:01
*** Leo_ has joined #openstack-meeting14:01
HenryG#link https://wiki.openstack.org/wiki/Network/Meetings14:01
HenryG#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
HenryGThe midcycle is approaching14:02
HenryG#link https://etherpad.openstack.org/p/newton-neutron-midcycle14:02
*** markvoelker has joined #openstack-meeting14:02
Sam-I-Ami'll be missing it :/14:02
*** bill_az has joined #openstack-meeting14:02
HenryGWe have a comprehensive list of workitems14:02
HenryG#link https://etherpad.openstack.org/p/newton-neutron-midcycle-workitems14:03
HenryGAny other announcements?14:03
*** yanyanhu has quit IRC14:03
amotokiI will announce the API reference cleanup sprint soon.14:03
*** designbybeck_ has joined #openstack-meeting14:03
*** boden has joined #openstack-meeting14:03
amotokiplease check my email on the dev list.  in the meeting last week we decided to start it this week,14:04
*** baoli_ has quit IRC14:04
HenryGLooking forward to it amotoki, thanks.14:04
amotokibut the preparation took time more than what I expected :-(14:04
HenryGNo problem. We appreciate the effort.14:05
*** Leo_ has quit IRC14:05
HenryG#topic Blueprints14:06
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:06
HenryG#link https://launchpad.net/neutron/+milestone/newton-314:06
*** claudiub has quit IRC14:06
*** zhurong has quit IRC14:06
HenryGA reminder to keep your progress up to date in the BP whiteboards14:06
*** zhurong has joined #openstack-meeting14:07
HenryGI think the Keystone V3 (tenant_id rename to project_id) patch will merge this week and it could be quite disruptive.14:09
HenryGPlease pay close attention. Especially if you maintain a sub-project.14:09
HenryG#topic Bugs14:09
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:09
*** shaohe_feng has quit IRC14:09
HenryGelectrocucaracha was deputy?14:10
jlibosvaI was14:10
*** shaohe_feng has joined #openstack-meeting14:10
HenryGSorry electrocucaracha is this week14:10
mlavalleI think electrocucaracha is this week14:10
HenryGAnything to report jlibosva14:10
jlibosvaso we had two bugs as gate-failures: one broke tempest fwaas - https://bugs.launchpad.net/bugs/1607625 - is fixed by now14:11
openstackLaunchpad bug 1607625 in neutron "gate-neutron-fwaas-dsvm-tempest is not working properly" [Critical,Fix released] - Assigned to YAMAMOTO Takashi (yamamoto)14:11
*** zz_dimtruck is now known as dimtruck14:11
jlibosvasecond didn't occur that often - https://bugs.launchpad.net/bugs/1607412 - also fixed by now14:11
openstackLaunchpad bug 1607412 in neutron "gate-grenade-dsvm-neutron-multinode fails server build on newton side with "Unrecognized attribute(s) 'dns_name'"" [High,In progress] - Assigned to Miguel Lavalle (minsel)14:11
mlavalleFor this one, the fix is close to merge14:12
*** links has quit IRC14:12
jlibosvawe have a critical bug that appeared after switching to native of_interface - https://bugs.launchpad.net/bugs/160778714:12
openstackLaunchpad bug 1607787 in neutron "Missing secure fail mode on physical bridges" [Critical,In progress] - Assigned to Hynek Mlnarik (hmlnarik-s)14:12
*** xiaohhui has quit IRC14:12
hynekmIt seems that native ofctl interface does not work properly under high load, ovs loses connection with the ryu controller and that leads to interruption of network traffic. It seems that there is setting secure fail mode missing on phys bridges, but something more than it might be an issue. Under investigation currently.14:12
jlibosvait breaks l2 connectivity via phys bridges in case of ovs agent restarts or when node is under heavy load14:13
*** xiaohhui has joined #openstack-meeting14:13
*** namnh_ has joined #openstack-meeting14:13
jlibosvathe work in progress for that last one can be found here: https://review.openstack.org/34888914:13
jlibosvaHenryG: that's all from my side14:14
*** namnh__ has joined #openstack-meeting14:14
HenryGThanks jlibosva14:14
HenryGAny other bugs to highlight from anyone else?14:15
mlavallejlibosva, HenryG: for 1607412, we need a final nudge for the fix: https://review.openstack.org/#/c/349214/14:15
*** gcb has quit IRC14:15
*** eharney_ has joined #openstack-meeting14:15
jlibosvagood point, sorry I marked it as fixed :) backport is crucial14:15
*** gcb has joined #openstack-meeting14:15
HenryGWho wants to volunteer for bug deputy next week?14:16
*** banix has joined #openstack-meeting14:17
*** namnh has quit IRC14:17
john-davidgeI can do it if there are no other volunteers14:17
*** tonytan4ever has joined #openstack-meeting14:17
HenryGThanks john-davidge !!14:17
*** namnh_ has quit IRC14:17
john-davidgeHenryG: No worries :)14:17
HenryG#action john-davidge bug deputy for the week of August 8th14:18
dasmshould we also find someone for mid-cycle week?14:18
dasmor leave it to armax? :)14:18
amotokijohn-davidge: thanks for volunteer twice these two months!14:18
HenryGAnyone can volunteer at any time. Just add your name to the table in https://wiki.openstack.org/wiki/Network/Meetings14:19
john-davidgeHenryG: Actually, I think I have to un-volunteer myself :( I have a wedding to go to next week14:19
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x7f5bc0020550>14:19
*** spotz_zzz is now known as spotz14:19
john-davidgeHenryG: Sorry to get your hopes up!! :(14:19
HenryGjohn-davidge: no problem, weddings are important too :)14:20
*** shaohe_feng has quit IRC14:20
john-davidgeIf there's anything reading this wondering if they should volunteer for the first time, do it! It's a great learning experience :)14:20
njohnstonI'll do it next week14:20
*** xiaohhui has quit IRC14:20
*** shaohe_feng has joined #openstack-meeting14:20
mlavalleand there's plenty of help around14:20
HenryGnjohnston: No weddings next week? ;)14:21
HenryGnjohnston: Thanks!14:21
HenryG#action njohnston bug deputy for the week of August 8th14:21
* regXboi likes the idea of anything being the bug deputy for a week14:21
*** yuval has quit IRC14:21
*** rockyg has joined #openstack-meeting14:21
john-davidgeregXboi: BugDeputyBot? I think that would be very popular...14:22
regXboiit very well could be ...14:22
*** amitgandhinz has joined #openstack-meeting14:22
HenryGSomehow I don't think a bot would be good at this.14:22
HenryGMoving on...14:22
HenryG#topic Docs14:23
*** openstack changes topic to "Docs (Meeting topic: networking)"14:23
HenryGWe already touched on the upcoming api-ref sprint14:23
*** zhipeng has quit IRC14:23
Sam-I-Amcouple patches to the networking guide in review14:24
Sam-I-Amother than that, i'm trying to work on updates to the config scenarios14:24
Sam-I-Amfor those of you who missed it, the reorg patch merged14:25
HenryGSam-I-Am: Thanks. Do you have the review links handy?14:25
Sam-I-Amnow it might be backported, so the mitaka guide has better organizaion14:25
Sam-I-Amno, i dont14:25
*** zhipeng has joined #openstack-meeting14:25
amotokihandy review links https://review.openstack.org/#/q/status:open+project:openstack/openstack-manuals+path:%255Edoc/networking-guide/.*14:25
HenryGamotoki: nice!14:25
HenryG#link https://review.openstack.org/#/q/status:open+project:openstack/openstack-manuals+path:%255Edoc/networking-guide/.*14:26
Sam-I-Amthats one way to do it14:26
*** amitgandhinz has quit IRC14:27
*** ajmiller has quit IRC14:27
HenryG#topic OSC14:27
*** openstack changes topic to "OSC (Meeting topic: networking)"14:27
*** ajmiller has joined #openstack-meeting14:27
HenryGrtheis: Anything to report this week?14:27
*** asettle has quit IRC14:28
rtheisprogress continues both on OSC network commands and OSC plugin in neutronclient14:28
*** diga has joined #openstack-meeting14:28
rtheisjust one reminder14:28
rtheiswhen writing commands, please review https://github.com/openstack/python-openstackclient/blob/master/doc/source/commands.rst14:28
amotokirtheis: according to https://etherpad.openstack.org/p/osc-neutron-support, it seems all planned network commands in OSC side has been implemented.14:29
*** amitgandhinz has joined #openstack-meeting14:29
rtheisamotoki: no, the first pass of core command are done14:29
rtheisamotoki: there are several more to go and likely some missing options which we can handle separately too14:30
*** shaohe_feng has quit IRC14:30
amotokirtheis: ah.. we need to see L.165 or after in the etherpad page14:30
*** esberglu has joined #openstack-meeting14:30
HenryG#link https://github.com/openstack/python-openstackclient/blob/master/doc/source/commands.rst14:30
HenryG#link https://etherpad.openstack.org/p/osc-neutron-support14:30
rtheisaddition OSC guidance for plugins is under https://github.com/openstack/python-openstackclient/tree/master/doc/source14:31
*** shaohe_feng has joined #openstack-meeting14:31
rtheisthat's it for now14:31
HenryG#link https://github.com/openstack/python-openstackclient/tree/master/doc/source14:31
HenryGThanks rtheis, and amotoki14:31
*** zhipeng has quit IRC14:31
*** jlibosva has quit IRC14:31
HenryG#topic Open Discussion14:31
*** openstack changes topic to "Open Discussion (Meeting topic: networking)"14:31
*** jlibosva has joined #openstack-meeting14:32
*** jamesdenton has joined #openstack-meeting14:32
yottatsaHi, I'd like to discuss rfe about CIDR updating14:32
*** asettle has joined #openstack-meeting14:32
yottatsa#link https://bugs.launchpad.net/neutron/+bug/160534314:32
openstackLaunchpad bug 1605343 in neutron "[rfe] update CIDR for subnet" [Wishlist,Triaged] - Assigned to Vladimir Eremin (yottatsa)14:32
*** zhipeng_ has joined #openstack-meeting14:32
*** baumann has joined #openstack-meeting14:33
HenryGyottatsa: unless there is someone present who wants to chime in, I would suggest a discussion with carl_baldwin present14:34
yottatsaOk, skip14:34
HenryGyottatsa: Let's try on Thursday at the drivers meeting14:35
john-davidgePerhaps an ML thread? I'd be interested to hear more about the use case14:35
HenryGAn ML post would help, yes.14:35
yottatsajohn-davidge HenryG I'll drop email in openstack-dev then and will be on Thursday14:35
HenryGyottatsa: great, sounds good14:35
*** achanda has joined #openstack-meeting14:36
*** obondarev has quit IRC14:36
HenryGIf there is nothing else, let's get back to real work.14:37
*** yottatsa has quit IRC14:37
dasmthanks o/14:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:37
openstackMeeting ended Tue Aug  2 14:37:59 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-08-02-14.00.html14:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-08-02-14.00.txt14:38
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-08-02-14.00.log.html14:38
*** hynekm has left #openstack-meeting14:38
hoangcxbye all14:38
mlavallehave a nice day14:38
*** jlibosva has left #openstack-meeting14:38
*** hoangcx has quit IRC14:39
*** namnh__ has quit IRC14:39
*** hoangcx has joined #openstack-meeting14:39
*** pc_m has left #openstack-meeting14:39
*** Sam-I-Am has left #openstack-meeting14:40
*** shaohe_feng has quit IRC14:40
*** regXboi has left #openstack-meeting14:40
*** shaohe_feng has joined #openstack-meeting14:41
*** boden has left #openstack-meeting14:42
*** xiaohhui has joined #openstack-meeting14:42
*** gagehugo has joined #openstack-meeting14:44
*** eharney_ is now known as eharney14:44
*** jungleboyj has joined #openstack-meeting14:44
*** karthikp_ has joined #openstack-meeting14:45
*** mtanino has joined #openstack-meeting14:45
*** hichihara has quit IRC14:45
*** annp has quit IRC14:45
*** zhipeng_ has quit IRC14:46
*** ajmiller has quit IRC14:47
*** obondarev has joined #openstack-meeting14:47
*** ajmiller has joined #openstack-meeting14:47
*** achanda has quit IRC14:48
*** hoangcx has quit IRC14:50
*** hoangcx2 has joined #openstack-meeting14:50
*** neiljerram has joined #openstack-meeting14:50
*** shaohe_feng has quit IRC14:50
*** ihrachys has joined #openstack-meeting14:50
*** neiljerram has quit IRC14:51
*** hoangcx2 has quit IRC14:51
*** shaohe_feng has joined #openstack-meeting14:51
*** hoangcx has joined #openstack-meeting14:51
*** rrecio has joined #openstack-meeting14:53
*** asettle has quit IRC14:53
*** asettle has joined #openstack-meeting14:54
*** neiljerram has joined #openstack-meeting14:55
*** Leo_ has joined #openstack-meeting14:56
*** korzen has quit IRC14:56
*** mickeys has joined #openstack-meeting14:56
*** amitgandhinz has quit IRC14:56
*** amitgandhinz has joined #openstack-meeting14:57
*** klkumar has quit IRC14:58
*** rrecio_ has joined #openstack-meeting14:59
*** Leo_ has quit IRC15:00
*** shaohe_feng has quit IRC15:01
*** mbonell has joined #openstack-meeting15:01
*** iyamahat has joined #openstack-meeting15:01
*** shaohe_feng has joined #openstack-meeting15:01
*** kebray has joined #openstack-meeting15:01
carl_baldwin#startmeeting neutron_routed_networks15:01
openstackMeeting started Tue Aug  2 15:01:25 2016 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_routed_networks)"15:01
openstackThe meeting name has been set to 'neutron_routed_networks'15:01
carl_baldwin#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_routed_networks)"15:01
*** rrecio has quit IRC15:01
carl_baldwin#link https://etherpad.openstack.org/p/routed-provider-networks-notes15:01
carl_baldwinStandard announcements15:02
carl_baldwinMid-cycle is just about two weeks away in Cork, Ireland.15:02
*** dtrainor has joined #openstack-meeting15:02
*** mbonell has left #openstack-meeting15:02
carl_baldwin#link https://etherpad.openstack.org/p/newton-neutron-midcycle15:02
*** anilvenkata has quit IRC15:03
carl_baldwinI'm going.15:03
mlavalleme too and john-davidge too15:03
carl_baldwinWe have just four weeks left until Newton-315:03
carl_baldwinmlavalle: john-davidge: it will be great to see you there.15:03
carl_baldwin#link http://releases.openstack.org/newton/schedule.html15:03
carl_baldwinAny other announcements?15:04
*** jungleboyj has quit IRC15:04
*** claudiub has joined #openstack-meeting15:05
carl_baldwin#topic Reviews15:05
*** openstack changes topic to "Reviews (Meeting topic: neutron_routed_networks)"15:05
*** baumann has quit IRC15:05
carl_baldwin#link https://review.openstack.org/#/q/status:open+topic:bp/routed-networks15:05
*** baoli has joined #openstack-meeting15:06
carl_baldwin#link https://review.openstack.org/#/q/status:open+topic:bp/neutron-routed-networks15:06
carl_baldwin^ these are the Nova ones.15:06
carl_baldwinI think we've done a pretty good job of whittling these down.15:06
*** yamamoto_ has joined #openstack-meeting15:07
carl_baldwinIt is great to see that the deferred IP port one in Nova has just been approved.15:07
*** dtrainor has quit IRC15:07
* blogan sneaks in late15:07
mlavallebad blogan15:08
*** singhj has joined #openstack-meeting15:08
carl_baldwinMany thanks to the Nova team, especially johnthetubaguy and mriedem for all their help getting this through.15:08
carl_baldwinWe will continue to refine this Nova / Neutron interaction but this is a big step just to be sure that we can used deferred IP ports.15:08
*** lezbar has quit IRC15:09
carl_baldwinWe should include this too.15:09
carl_baldwin#link https://review.openstack.org/#/q/status:open+topic:bp/service-subnets15:09
*** lezbar has joined #openstack-meeting15:09
*** mbound has joined #openstack-meeting15:10
john-davidgecarl_baldwin: Thanks, the main CRUD patch is in good shape. I'll be ready to push the follow-up for review very soon15:10
*** cknight has joined #openstack-meeting15:10
*** yamamoto has quit IRC15:10
carl_baldwinjohn-davidge: great. I look forward to reviewing that. Make sure to ping me when it is up for review.15:10
john-davidgecarl_baldwin: Will do. Expect it by the end of today or early tomorow15:11
*** shaohe_feng has quit IRC15:11
*** synegi is now known as gatekeep15:11
*** gatekeep has quit IRC15:11
*** gatekeep has joined #openstack-meeting15:11
*** adiantum has quit IRC15:12
john-davidgecarl_baldwin: Great news on the update from armax! Thanks15:12
carl_baldwinxiaohhui: you around? I see you're making some progress on your patches. I hope you're settling in to your new position comfortably.15:13
* haleyb wakes up and looks around meeting15:13
*** janki has quit IRC15:13
xiaohhuiI did a rebase to the patch15:13
*** shaohe_feng has joined #openstack-meeting15:14
*** saju_m has quit IRC15:14
*** baumann has joined #openstack-meeting15:14
carl_baldwinI'd like to get https://review.openstack.org/#/c/317358/ wrapped up. What do you think we need there/15:14
*** claudiub has quit IRC15:15
*** ebalduf has quit IRC15:15
*** dtrainor has joined #openstack-meeting15:15
xiaohhuiI think we need some review to it15:15
carl_baldwinxiaohhui: I guess seeing if kevinbenton could take another quick look would be a good first step.15:16
xiaohhuikevin will be good person for the review15:16
carl_baldwinxiaohhui: Would you mind sending him a quick note?15:16
*** baumann has joined #openstack-meeting15:16
*** baumann has quit IRC15:16
*** jungleboyj has joined #openstack-meeting15:17
*** nkrinner is now known as nkrinner_afk15:17
xiaohhuihe had given some good feedback15:17
xiaohhuiI will send him a mail today15:17
*** karthikp_ has quit IRC15:17
*** Patifa has joined #openstack-meeting15:17
carl_baldwinxiaohhui: Great.15:17
carl_baldwinI just noticed https://review.openstack.org/#/c/333716/ has made some good progress while I was away. I'll have a look at it today to see if it can be merged.15:18
*** mkoderer_cloud has quit IRC15:18
*** enriquetaso has joined #openstack-meeting15:18
*** baumann has joined #openstack-meeting15:18
*** baumann has quit IRC15:18
mlavalleyeah, I think that one is ready to merge15:19
*** karthikp_ has joined #openstack-meeting15:20
*** baumann has joined #openstack-meeting15:20
*** baumann has quit IRC15:20
carl_baldwinAny other work in progress that should be discussed?15:20
*** Sukhdev has joined #openstack-meeting15:20
*** ebalduf has joined #openstack-meeting15:20
*** lezbar has quit IRC15:20
*** belmoreira has quit IRC15:21
carl_baldwinI think our pace has continue to be pretty impressive.15:21
*** lezbar has joined #openstack-meeting15:21
*** shaohe_feng has quit IRC15:21
*** shaohe_feng has joined #openstack-meeting15:21
carl_baldwin#topic Docs15:21
*** openstack changes topic to "Docs (Meeting topic: neutron_routed_networks)"15:21
*** ihrachys has quit IRC15:22
carl_baldwinI dropped the ball here for a few weeks. I did start something locally but didn't get very far.15:22
carl_baldwinI'm at a point where I think I can knock out at least a rough beginning.15:22
carl_baldwinSo, I'll take that action item.15:22
carl_baldwin#action carl_baldwin will knock out initial docs15:23
carl_baldwin#topic Testing15:23
*** openstack changes topic to "Testing (Meeting topic: neutron_routed_networks)"15:23
mlavallewe are making progress with the tempest tests15:24
mlavalleBin has posted two revisions to the scenario test15:24
mlavalleexperiencing some problems that he is working on15:24
mlavallejanzian is working on the api tests15:24
*** hoangcx has quit IRC15:24
*** Sukhdev has quit IRC15:25
mlavalleWe should have a scenario test by the end of this week15:25
mlavallewith the two happy paths15:25
mlavalleand to that we will add a connectivity test of vm's on different segments15:25
*** yamahata has joined #openstack-meeting15:25
*** zhipeng has joined #openstack-meeting15:26
*** armax has joined #openstack-meeting15:26
mlavalle#link https://review.openstack.org/#/c/34718815:26
*** hoangcx has joined #openstack-meeting15:27
carl_baldwinSounds like good progress.15:27
*** dfflanders has joined #openstack-meeting15:27
mlavallethat's it this week15:28
*** jmckind has joined #openstack-meeting15:29
carl_baldwin#topic Integration with Nova Scheduler15:29
*** openstack changes topic to "Integration with Nova Scheduler (Meeting topic: neutron_routed_networks)"15:29
carl_baldwinmlavalle: back to you. :)15:29
mlavalleI have started coding the interaction of Neutron with the generic resource pools api15:29
*** zhurong has quit IRC15:30
*** Sukhdev has joined #openstack-meeting15:30
mlavalleI am using the client I wrote for generic resource pools15:30
mlavalleit's been slower that I expected. But I should have a first prototype soon15:30
carl_baldwinSounds cool.15:31
*** shaohe_feng has quit IRC15:31
carl_baldwinAnything to discuss?15:31
mlavalleNot now. I'll yell if I need help15:32
*** xiaohhui_ has joined #openstack-meeting15:32
carl_baldwin#topic Service Subnets15:32
*** openstack changes topic to "Service Subnets (Meeting topic: neutron_routed_networks)"15:32
*** baumann has joined #openstack-meeting15:33
carl_baldwinjohn-davidge: haleyb: I guess we already talked about this a bit.15:33
*** xiaohhui_ has quit IRC15:33
*** rbartal has quit IRC15:33
carl_baldwinThere was something I wanted to bring up but I'm having just a little trouble finding it.15:33
*** xiaohhui_ has joined #openstack-meeting15:33
john-davidgecarl_baldwin: Yeah I think i covered eveything from me on this15:33
haleybyes.  I just pushed a new OSC patch, think it's close as well, https://review.openstack.org/#/c/342976/15:34
*** ljxiash has quit IRC15:34
carl_baldwinI remember now.15:34
*** shaohe_feng has joined #openstack-meeting15:34
carl_baldwin#link https://review.openstack.org/#/c/304647/15/neutron/services/segments/plugin.py15:34
carl_baldwin^ I wanted to point this out.15:34
carl_baldwin#link https://review.openstack.org/#/c/304647/16/neutron/services/segments/plugin.py15:35
*** xiaohhui has quit IRC15:35
carl_baldwin^ I put a TODO here.15:35
carl_baldwinI hope it makes sense.15:35
*** mageshgv has joined #openstack-meeting15:35
* john-davidge looking15:36
carl_baldwinBasically, with service subnets and routed networks, we'll eventually have subnets that aren't attached to segments. The main one is floating IP service subnets.15:36
*** sindhu has quit IRC15:36
carl_baldwinThat was my thinking anyway.15:36
*** karthikp_ has quit IRC15:36
*** kebray has quit IRC15:36
*** kaminohana has quit IRC15:37
*** xiaohhui_ has quit IRC15:38
john-davidgeYes, that sounds right to me I think15:38
haleybyes, think that makes sense15:38
john-davidgeEither way that simplification seems sensible for now15:38
carl_baldwinIt could be tricky given that a few places in code make the assumption that all of the subnets are attached to segments.15:39
*** pnavarro has joined #openstack-meeting15:39
*** shashank_hegde has joined #openstack-meeting15:39
john-davidgeA fun hurdle to deal with when we come to it :)15:39
*** kebray has joined #openstack-meeting15:39
carl_baldwinBut, I think we can finish the initial service subnet functionality without regard to routed networks. Then, we can look at reconciling the two.15:40
*** mikelk has quit IRC15:40
carl_baldwinOne step at a time.15:40
*** manikanta_tadi has joined #openstack-meeting15:41
haleybyes.  i'm sure there will be some implementation details wrt the service subnet being different from the FIP subnet for example, whether we need to tweak routes/rules, etc15:41
*** dtrainor has quit IRC15:41
carl_baldwinhaleyb: I'll take a look at your OSC patch.15:41
*** karthikp_ has joined #openstack-meeting15:41
haleybcarl_baldwin: thanks, i might need to add more tests now that i seem to have it working15:41
*** cknight has quit IRC15:41
carl_baldwinAnything else?15:41
haleybnot from me15:42
*** shaohe_feng has quit IRC15:42
carl_baldwin#topic Client15:42
*** openstack changes topic to "Client (Meeting topic: neutron_routed_networks)"15:42
carl_baldwinrtheis: Are you around?15:42
*** shaohe_feng has joined #openstack-meeting15:42
carl_baldwinAnything in the client being neglected?15:42
rtheiscarl_baldwin: yes15:42
rtheisright now I'm waiting on create and delete segment in neutron to merge15:43
*** jlanoux has quit IRC15:43
rtheisthen I can remove WIP from "network segment create" and "network segment delete"15:43
carl_baldwinrtheis: Yeah, that is one that we're focusing attention to now.15:43
*** singhj has quit IRC15:43
rtheiscarl_baldwin: are there any other client changes that are needed15:44
rtheisI will review https://review.openstack.org/#/c/342976/15:44
carl_baldwinrtheis: Off the top of my head, I can't think of any.15:44
carl_baldwinrtheis: thanks.15:44
*** dasanind has quit IRC15:45
*** Patifa has quit IRC15:45
rtheiscarl_baldwin: do you think name and description will be added to segment15:45
*** annabelleonabike has joined #openstack-meeting15:45
carl_baldwinrtheis: I'll let you know if I discover any others as I'm writing the documentation.15:45
*** zhonghua-lee has quit IRC15:45
*** Patifa has joined #openstack-meeting15:45
rtheisIf so, then I'll have a few minor updates for that15:45
carl_baldwinrtheis: We have a patch for that. It has been somewhat neglected due to priority but I think we can start taking another look.15:45
*** kaminohana has joined #openstack-meeting15:45
rtheissounds good15:46
*** kaminohana has quit IRC15:46
*** lamt_ has joined #openstack-meeting15:46
rtheisnothing else15:46
carl_baldwinrtheis: Thanks.15:46
carl_baldwin#topic Open Discussion15:46
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_routed_networks)"15:46
carl_baldwinAnything that we 're neglecting?15:47
mlavalleI am working on a patchset to return the segment id in the port dictionary15:47
*** lamt_ has quit IRC15:47
mlavalleI only need to add unit tests. I will push it later today15:47
*** lamt_ has joined #openstack-meeting15:47
carl_baldwinmlavalle: Great, is that one already listed on the etherpad? It keeps slipping my mind. :(15:48
mlavalleit is15:48
carl_baldwinmlavalle: But, that is an important piece. I'm glad it's not slipping yours.15:48
mlavalleI return the segment id in the port dictionary if the network is routed15:49
*** dasanind has joined #openstack-meeting15:49
*** sindhu has joined #openstack-meeting15:50
*** yb has joined #openstack-meeting15:50
carl_baldwinThanks, let us know when it is up.15:50
mlavalleand it is built on top of the work you did for the deferral attribuet15:50
*** hemna_ is now known as hemna15:50
mlavalleI also want to introduce yb to the team15:51
mlavalleHe is the one working on the tempest scenario test15:51
*** lezbar has quit IRC15:51
*** Guest26194 has quit IRC15:51
mlavalleand he will be attending this meeting from nw on to report his progress on that subject15:51
carl_baldwinyb: hi15:51
*** lezbar has joined #openstack-meeting15:51
ybhi :)15:52
*** annabelleonabike has left #openstack-meeting15:52
*** shaohe_feng has quit IRC15:52
mlavalleHis name is Bin Yu and he is based out of Shanghai15:52
*** shashank_hegde has quit IRC15:52
ybcal_baldwin: hi:)15:52
mlavalleThat's all fom me and yb15:53
carl_baldwinmlavalle: yb: thanks15:53
*** shaohe_feng has joined #openstack-meeting15:53
carl_baldwinAnyone else have anything?15:53
*** banix has quit IRC15:53
*** weshay is now known as weshay_lunch15:54
*** sarob has joined #openstack-meeting15:54
*** ygbo has quit IRC15:54
*** claudiub has joined #openstack-meeting15:54
*** dtrainor has joined #openstack-meeting15:55
*** janki has joined #openstack-meeting15:56
*** baumann has joined #openstack-meeting15:56
*** baumann has quit IRC15:56
*** sarob has quit IRC15:57
*** baumann has joined #openstack-meeting15:57
*** yamamoto_ has quit IRC15:59
*** singhj has joined #openstack-meeting15:59
*** rossella_s has quit IRC16:00
*** rossella_s has joined #openstack-meeting16:00
*** s3wong has joined #openstack-meeting16:00
*** Leo_ has joined #openstack-meeting16:01
john-davidgecarl_baldwin: endmeeting?16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
openstackMeeting ended Tue Aug  2 16:01:38 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_routed_networks/2016/neutron_routed_networks.2016-08-02-15.01.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_routed_networks/2016/neutron_routed_networks.2016-08-02-15.01.txt16:01
*** KanagarajM has joined #openstack-meeting16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_routed_networks/2016/neutron_routed_networks.2016-08-02-15.01.log.html16:01
john-davidgecarl_baldwin :)16:01
carl_baldwinMy apologies if someone was waiting for that.16:02
mlavalleHave a nice rest of the day / evening / night16:02
carl_baldwinjohn-davidge: Thanks!16:02
*** gokrokve has joined #openstack-meeting16:02
*** Leom has joined #openstack-meeting16:02
*** shaohe_feng has quit IRC16:02
*** tangchen_ has quit IRC16:02
*** john-davidge has left #openstack-meeting16:03
*** tangchen has quit IRC16:03
*** shaohe_feng has joined #openstack-meeting16:03
*** s3wong has quit IRC16:03
*** weshay_lunch is now known as weshay16:04
*** Sukhdev has quit IRC16:05
*** Leo_ has quit IRC16:05
*** sridharg has quit IRC16:06
*** numans has quit IRC16:09
*** mlavalle has left #openstack-meeting16:11
*** shaohe_feng has quit IRC16:12
*** shaohe_feng has joined #openstack-meeting16:13
*** Patifa has quit IRC16:13
*** nishaYadav has joined #openstack-meeting16:15
*** asettle has quit IRC16:16
*** tangchen_ has joined #openstack-meeting16:16
*** korzen has joined #openstack-meeting16:17
*** gokrokve has quit IRC16:17
*** toddjohn has quit IRC16:17
*** diga has quit IRC16:19
*** janzian has left #openstack-meeting16:19
*** amitgandhinz has quit IRC16:21
*** yb has quit IRC16:21
*** mbound has quit IRC16:21
*** amitgandhinz has joined #openstack-meeting16:21
*** unicell has joined #openstack-meeting16:21
*** piet has joined #openstack-meeting16:22
*** maeca1 has quit IRC16:23
*** shaohe_feng has quit IRC16:23
*** gatekeep has quit IRC16:23
*** tangchen has joined #openstack-meeting16:23
*** gatekeep has joined #openstack-meeting16:23
*** gatekeep has quit IRC16:23
*** gatekeep has joined #openstack-meeting16:23
*** shaohe_feng has joined #openstack-meeting16:23
*** unicell1 has quit IRC16:24
*** shashank_hegde has joined #openstack-meeting16:26
*** krotscheck is now known as krot_sickleave16:27
*** elopez has joined #openstack-meeting16:27
*** Sukhdev has joined #openstack-meeting16:27
*** marekd2 has quit IRC16:28
*** elopez is now known as Guest1653316:28
*** e0ne has quit IRC16:28
*** amotoki has quit IRC16:28
*** e0ne has joined #openstack-meeting16:28
*** marekd2 has joined #openstack-meeting16:28
*** yamamoto has joined #openstack-meeting16:30
*** JoseMello has quit IRC16:30
*** csomerville has joined #openstack-meeting16:30
*** rhagarty has joined #openstack-meeting16:31
*** Guest16533 has quit IRC16:32
*** neiljerram has quit IRC16:33
*** marekd2 has quit IRC16:33
*** shaohe_feng has quit IRC16:33
*** cody-somerville has quit IRC16:33
*** neiljerram has joined #openstack-meeting16:34
*** shaohe_feng has joined #openstack-meeting16:34
*** yamamoto has quit IRC16:34
*** neiljerram has quit IRC16:35
*** manikanta_tadi has quit IRC16:37
*** Apoorva has joined #openstack-meeting16:42
*** shashank_hegde has quit IRC16:42
*** shaohe_feng has quit IRC16:43
*** shaohe_feng has joined #openstack-meeting16:44
*** efried has quit IRC16:45
*** banix has joined #openstack-meeting16:46
*** sudipto has quit IRC16:48
*** obondarev has quit IRC16:49
*** dmorita has joined #openstack-meeting16:49
*** eumel8 has joined #openstack-meeting16:50
*** corvus is now known as jeblair16:51
*** tesseract- has quit IRC16:51
*** shashank_hegde has joined #openstack-meeting16:51
*** iyamahat has quit IRC16:53
*** toddjohn_ has joined #openstack-meeting16:53
*** shaohe_feng has quit IRC16:53
*** dmorita has quit IRC16:54
*** ajmiller has quit IRC16:54
*** shaohe_feng has joined #openstack-meeting16:54
*** ajmiller has joined #openstack-meeting16:54
*** yamahata has quit IRC16:55
*** dmorita has joined #openstack-meeting16:55
*** lpetrut has quit IRC16:55
*** unicell has quit IRC16:56
*** shashank_hegde has quit IRC16:57
*** ihrachys has joined #openstack-meeting16:58
*** rockyg has quit IRC17:00
*** rbak_ has joined #openstack-meeting17:00
*** kebray has quit IRC17:01
*** ralonsoh has quit IRC17:01
igordcardif somebody is here for the common classifier meeting: it's not expected that there will be one17:01
*** rbak has quit IRC17:02
*** yamamoto has joined #openstack-meeting17:02
*** julim has quit IRC17:02
*** shaohe_feng has quit IRC17:04
*** piet has quit IRC17:04
*** shaohe_feng has joined #openstack-meeting17:05
*** korzen has quit IRC17:05
*** julim has joined #openstack-meeting17:06
*** ihrachys has quit IRC17:06
*** bobh has quit IRC17:08
*** claudiub has quit IRC17:08
*** ihrachys has joined #openstack-meeting17:09
*** iyamahat has joined #openstack-meeting17:12
*** yamamoto has quit IRC17:12
*** shaohe_feng has quit IRC17:14
*** HeOS has quit IRC17:14
*** shaohe_feng has joined #openstack-meeting17:14
*** HeOS has joined #openstack-meeting17:16
*** mbound has joined #openstack-meeting17:16
*** rbak_ has quit IRC17:17
*** crinkle has quit IRC17:17
*** cdub has joined #openstack-meeting17:18
*** piet has joined #openstack-meeting17:18
*** shashank_hegde has joined #openstack-meeting17:19
*** rbak has joined #openstack-meeting17:19
*** cdub has quit IRC17:20
*** cdub has joined #openstack-meeting17:20
*** lbrune has joined #openstack-meeting17:20
*** cdub has quit IRC17:21
*** lbrune has left #openstack-meeting17:21
*** cdub has joined #openstack-meeting17:21
*** janki has quit IRC17:21
*** Apoorva has quit IRC17:21
*** Apoorva has joined #openstack-meeting17:22
*** e0ne has quit IRC17:24
*** maeca1 has joined #openstack-meeting17:24
*** unicell has joined #openstack-meeting17:24
*** shaohe_feng has quit IRC17:24
*** singhj has quit IRC17:25
*** shaohe_feng has joined #openstack-meeting17:25
*** reedip has quit IRC17:26
*** ihrachys has quit IRC17:26
*** singhj has joined #openstack-meeting17:26
*** gjayavelu has quit IRC17:28
*** karthikp_ has quit IRC17:30
*** claudiub has joined #openstack-meeting17:32
*** yamahata has joined #openstack-meeting17:33
*** toscalix has quit IRC17:33
*** zhhuabj has quit IRC17:34
*** shaohe_feng has quit IRC17:34
*** ajmiller_ has joined #openstack-meeting17:34
*** sambetts is now known as sambetts|afk17:35
*** ajmiller_ has quit IRC17:35
*** shaohe_feng has joined #openstack-meeting17:35
*** Na3iL has quit IRC17:35
*** tangchen has quit IRC17:35
*** vishnoianil has quit IRC17:36
*** ajmiller has quit IRC17:37
*** bobh has joined #openstack-meeting17:38
*** reedip has joined #openstack-meeting17:38
*** numans has joined #openstack-meeting17:38
*** bobh has quit IRC17:39
*** tangchen has joined #openstack-meeting17:39
*** andymaier has joined #openstack-meeting17:39
*** yamamoto has joined #openstack-meeting17:40
*** singhj has quit IRC17:40
*** liamji has quit IRC17:42
*** Patifa has joined #openstack-meeting17:42
*** eezhova_ has joined #openstack-meeting17:44
*** unicell has quit IRC17:44
*** unicell1 has joined #openstack-meeting17:44
*** shaohe_feng has quit IRC17:45
*** shaohe_feng has joined #openstack-meeting17:46
*** Sukhdev has quit IRC17:46
*** eezhova has quit IRC17:47
*** adriant has joined #openstack-meeting17:48
*** dasanind has quit IRC17:49
*** sarob has joined #openstack-meeting17:50
*** lpetrut has joined #openstack-meeting17:51
*** _sarob has joined #openstack-meeting17:51
*** yamamoto has quit IRC17:52
*** andymaier has quit IRC17:52
*** electrofelix has quit IRC17:54
*** sarob has quit IRC17:55
*** s3wong has joined #openstack-meeting17:55
*** shaohe_feng has quit IRC17:55
*** browne has joined #openstack-meeting17:56
*** shaohe_feng has joined #openstack-meeting17:56
*** baumann_ has joined #openstack-meeting17:56
*** numans has quit IRC17:56
*** _sarob has quit IRC17:57
*** karthikp_ has joined #openstack-meeting17:57
*** sarob has joined #openstack-meeting17:57
*** zhhuabj has joined #openstack-meeting17:59
*** cdub has quit IRC17:59
*** sarob has quit IRC17:59
stevemar#startmeeting keystone17:59
openstackMeeting started Tue Aug  2 17:59:53 2016 UTC and is due to finish in 60 minutes.  The chair is stevemar. Information about MeetBot at http://wiki.debian.org/MeetBot.17:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:59
stevemarping 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, xek17:59
*** openstack changes topic to " (Meeting topic: keystone)"17:59
*** baumann has quit IRC17:59
openstackThe meeting name has been set to 'keystone'17:59
*** MeganR has joined #openstack-meeting18:00
*** crinkle has joined #openstack-meeting18:00
*** sarob has joined #openstack-meeting18:00
stevemardolphm, rderose and henrynash gotta be different18:00
rodrigodsstevemar, hey, cascade deletion is useful!18:00
rodrigodsjust kidding18:00
stevemarwe're missing gyee and samuel today18:00
dolphmstevemar: someone has to wave back18:00
henrynash(practicing my yoga)18:00
*** singhj has joined #openstack-meeting18:00
dolphmstevemar: we can't all just wave in the same direction18:00
stevemarhenrynash: lol18:00
stevemarhenrynash: kudo to you if you can still get into \\o//18:01
stevemaragenda: https://etherpad.openstack.org/p/keystone-weekly-meeting18:01
henrynashzero chance...I'm the entertainment for the class18:01
stevemarwait a minute for the rest of the folks to trickle in18:01
*** tangchen has quit IRC18:02
*** amakarov_ has joined #openstack-meeting18:02
henrynashbreton: those spiders really get me18:02
ayoungOyez Oyez18:02
*** jamielennox has joined #openstack-meeting18:02
* stevemar avoids topol because he's gonna ask about our openstackSV presentation and if i'm done the slides...18:02
topolstevemar!!!!! Im comin for ya18:02
stevemarwe got critical mass, lets go!18:02
*** mbound has quit IRC18:02
stevemar#topic release status18:03
*** openstack changes topic to "release status (Meeting topic: keystone)"18:03
*** dmorita has quit IRC18:03
stevemarwe've got  a few weeks to go til newton-3! http://releases.openstack.org/newton/schedule.html18:03
stevemar#link http://releases.openstack.org/newton/schedule.html18:03
stevemarwe've got a bunch of bugs and blueprints, see https://launchpad.net/keystone/+milestone/newton-318:03
stevemargood news is almost everything has patches up18:03
*** dmorita has joined #openstack-meeting18:03
stevemarso we're in decent shape18:04
*** tangchen has joined #openstack-meeting18:04
stevemarand almost all patches associated with those blueprints and bugs have been seeing good reviews18:04
stevemarso thanks everyone for that18:04
*** amakarov_ is now known as amakarov18:04
stevemarjust gotta keep it up for another 4 weeks til newton-3 and we're smooth sailing til barcelona (tapas on me)18:05
*** singhj has quit IRC18:05
* topol wish our OpenStackSV prez was in as good shape :-)18:05
stevemarOK that was good18:05
*** shaohe_feng has quit IRC18:05
ayoungdngit we need the OSC client support for DSRs18:05
*** shaohe_feng has joined #openstack-meeting18:06
stevemarso if you're looking for things to review, pick a bug or BP from https://launchpad.net/keystone/+milestone/newton-3 and look for the gerrit link18:06
stevemarayoung: henrynash is working on that18:06
stevemari'm done my spiel18:06
henrynashayoung: DSR patch for osc is in final review18:06
stevemarthanks again for the reviews and triaging everyone!18:06
stevemar#topic fix cache invalidation18:06
*** openstack changes topic to "fix cache invalidation (Meeting topic: keystone)"18:06
lbragstad#link https://bugs.launchpad.net/keystone/+bug/160755318:07
openstackLaunchpad bug 1607553 in OpenStack Identity (keystone) "Revocation event caching is broken across processes" [High,New]18:07
stevemarbreton, lbragstad, dstanek ^18:07
bretoni and lbragstad ran into the same issue independently: https://bugs.launchpad.net/keystone/+bug/160755318:07
lbragstadok - I spent a good portion of friday trying to figure out why we can't switch to fernet18:07
dstanekthis is a fun one18:07
*** sarob has quit IRC18:07
bknudsonso just looking at the review comments "this is a hack" and "this doesn't work"18:07
bretonpatch for it doesn't fully work, but because of a technical issue18:07
bknudsonnot sure what the point is of discussing it.18:07
bretonthe bug is a blocker for making fernet the default18:07
stevemarbknudson: slow down turbo18:08
bretonthe patch we are talking about is https://review.openstack.org/#/c/327885/ .18:08
lbragstadI think we need to figure out what our best option is for moving forward so that we can invalidate cache regions across processes18:08
bretonthe problem with it is that it *will* break with the new release of dogpile.cache18:08
bretonbecause it relies on internal interfaces of dogpile.cache18:08
bknudsonso -218:08
bretonbut using internal interfaces looks like the only way in stable dogpile.cache18:08
dstanekbreton: i think that my version won't once it's working18:09
amakarovbknudson: OTOH it's the only solution for current stable/* branches18:09
bretonthe fix for the bug also needs to be backported to stable/mitaka18:09
bknudsondoes dogpile.cache not accept code submissions18:09
lbragstadbknudson they do - amakarov added support for region invalidation across processes18:09
dstanekbknudson: the problem is (and according to dolphm we can push back) the policy for bumping version numbers in stable branches18:09
lbragstad#link https://review.openstack.org/#/c/349704/ this is dstanek's approach to fixing the problem18:10
bretondstanek: have you and lbragstad tested it against fernet patches?18:10
stevemari see amakarov's commit here: https://bitbucket.org/zzzeek/dogpile.cache/commits/all18:10
dstaneki think this is a solved problem there and ideally that's what i'd like to use18:10
amakarovlbragstad: but I needed to ask zzzeek for permission - it's not automatic18:10
dstanekbreton: i get similar results. less test failures, but i was still getting some18:10
bretondstanek: is it backportable to stable/mitaka?18:11
dstanekbreton: should be, but i didn't try it18:11
*** KanagarajM has quit IRC18:11
amakarovstevemar: yes, and with this update it's possible to solve the issue in oslo18:11
dstanekbut i'd rather push forward18:11
*** ihrachys has joined #openstack-meeting18:11
stevemardogpile is currently capped at 0.5.7 in stable/mitaka18:12
*** toddjohn_ has quit IRC18:12
amakarovstevemar: exactly18:12
bretonstevemar: can we merge one fix for stable/mitaka and completely different to master?18:12
dolphmamakarov: what would the new version of dogpile be released as?18:12
stevemarbreton: you ... can, it's not ideal, but it's possible18:13
bknudsonaccording to this dogpile.cache is not capped.18:13
*** toddjohn has joined #openstack-meeting18:13
stevemarbknudson: https://github.com/openstack/requirements/blob/stable/mitaka/upper-constraints.txt#L11818:13
amakarovI suggest using breton's patch and cap dogpile.cache to the version prior to my patch18:13
bknudsonthat's not a cap that's just what is used for testing.18:14
stevemarthe one after 0.5.7 is 0.6.018:14
bknudsonif the min version is updated then that means every deployer/packager needs to upgrade.18:14
dstanekamakarov: i'd want to immediately follow up with the right way to do it in master18:14
*** Ravikiran_K has quit IRC18:14
*** sarob has joined #openstack-meeting18:14
bretondstanek: me too18:14
amakarovbknudson: yes, though if we miss dogpile.cache release with my patch with breton's on merged, we'll be in trouble )18:14
dolphmbknudson: ? http://git.openstack.org/cgit/openstack/requirements/tree/upper-constraints.txt?h=stable/mitaka#n11818:14
bretondstanek: but we need to do something with mitaka18:15
lbragstaddstanek breton but are we sure the propose path actually fixes the race conditions?18:15
*** enriquetaso has quit IRC18:15
bknudsonupper-constraints is what the community uses for testing. It's not a cap.18:15
bretonlbragstad: lets leave technical issue aside18:15
amakarovdstanek: right now breton follows it )18:15
dstanekbreton: right, that's why i said we should immediately fix master18:15
*** shaohe_feng has quit IRC18:15
bretonlbragstad: i thing we can figure it out in reviews/#openstack-keystone18:15
dstaneklbragstad: i don't think this fixes the race at all18:15
amakarovsounds like a consensus18:15
stevemarbknudson: but that's what'll be laid down when the dsvm tests run18:16
dolphmpackagers are not likely going to repackage dogpile 0.6.0 just for us (potentially breaking other consumers), especially if it contains a breaking API change18:16
dstanekunspoken alternative is to recomment revocation caching be turned off18:16
amakarovdolphm: good point!18:16
*** shaohe_feng has joined #openstack-meeting18:16
bretondolphm: it doesn't contain breaking api change18:16
dolphmdstanek: so i might have to take back the idea to bump the requirement18:16
bretondolphm: the patch relies on private stuff :(18:16
lbragstaddstanek at least until it works properly18:16
*** sarob has quit IRC18:16
dstanekdolphm: i don't know that it contains a breaking api change18:17
*** e0ne has joined #openstack-meeting18:17
dolphmoh, only we would break if we upgraded, then?18:17
lbragstadright - it breaks because we rely on internal interfaces of dogpile18:17
dstanekdolphm: out hacks are monkey patching protected variables18:17
bretondolphm: yes18:17
bknudsoncan dogpile.cache do a fix release 0.5.8 ?18:17
bknudsonprobably not.18:17
dolphmwhy would dogpile require a 0.6.0 release instead of a 0.5.8 release, then? because this is perceived as a feature?18:17
lbragstadamakarov ^ ?18:18
*** acoles is now known as acoles_18:18
stevemarbreton: the 0.6.0 release had an api change, they moved things around IIRC18:18
*** sarob has joined #openstack-meeting18:18
bretonstevemar: oh, ok.18:18
bretonzzz... is not here18:18
dolphmstevemar: unrelated to this fix?18:18
dstanekstevemar: really?j18:18
amakarovdolphm: don't remember exactly if the patch has a bug specified (18:18
bretonok, since dstanek has a patch, here is what i suggest18:19
breton1. Try his patch out, it doesn't rely on protected variables18:19
breton2. if it works, merge, backport, code using amakarov's new feature18:19
lbragstad#link https://review.openstack.org/#/c/349704/18:19
stevemardolphm: i thought so? https://bitbucket.org/zzzeek/dogpile.cache/commits/761dc0a9e4c08f9af4b732ced3604e72d74f09af18:19
amakarov#link https://bitbucket.org/zzzeek/dogpile.cache/issues/38/invalidate-entire-cache18:19
breton3. if not, figure out at the next meeting18:20
amakarovoops... it's a bugfix18:20
*** yamamoto has joined #openstack-meeting18:20
bretonwhat do you think?18:20
dstanekbreton: i still need to figure out if the transients are my fault or not18:20
lbragstadbreton that path will require us to bump the version of dogpile for the backport - right?18:20
dstanekthat's the case for both patches i guess18:20
bretonlbragstad: dstanek's? No.18:20
dstanekbreton: lbragstad: no version bump needed for mine18:21
stevemarbreton: #2 "code using amakarov's new feature" << whats that mean?18:21
dolphmstevemar: ++18:21
dolphmconsume it in master, maybe?18:21
bretonstevemar: ^ >  i see amakarov's commit here18:21
bretonstevemar: the one in dogpile.cache18:21
bretonstevemar: https://gerrit.sqlalchemy.org/#/c/108/18:22
lbragstad#link https://bitbucket.org/zzzeek/dogpile.cache/commits/d521db7eb4eab4ad2bacf5f1f5fd89bd3e43a0fa18:22
stevemarbreton: hmm, his dogpile commit, has it been released yet?18:22
*** sarob has quit IRC18:22
bretonstevemar: it is not release yet, but i guess it will soon be18:22
bretonstevemar: and when it is, "code using amakarov's new feature".18:22
*** leeantho has joined #openstack-meeting18:22
stevemarohhhh okay18:22
bknudsonwhen you backport to mitaka you can have the code check for the right version of dogpile.cache before using the new features.18:23
stevemari get it18:23
*** sarob has joined #openstack-meeting18:23
stevemarbreton: sounds like a plan18:23
bretonbknudson: dstanek's patch won't need any version checking18:23
rodrigodsnice work on chasing this down18:23
dstanekok, so concensus is breton, lbragstad and i will work on making sure my patch works and we'll get that merged and backported18:24
stevemarmerge dstaneks patch in master and mitaka, then using amakarov's new feature when it's released in master18:24
breton#action breton, dstanek, lbragstad: check if patch by dstanek works not worse than https://review.openstack.org/#/c/327885/18:24
dstanek++ sounds good18:24
stevemar #action breton, dstanek, lbragstad: check if patch by dstanek works not worse than https://review.openstack.org/#/c/327885/18:24
stevemari was expecting some bot feedback *shrugs*18:24
stevemarthanks breton, lbragstad and dstanek18:24
lbragstadthanks for the time18:25
stevemar#topic Validating trust-scoped tokens with v2.0 API18:25
*** openstack changes topic to "Validating trust-scoped tokens with v2.0 API (Meeting topic: keystone)"18:25
stevemarbreton you're up again18:25
bretona trust-scoped token can be obtained via v2.0 API18:25
bretonwhy cannot it be validated against v2.0 API?18:25
*** rockyg has joined #openstack-meeting18:25
stevemarmaybe it was just overlooked? is this by design ayoung?18:25
lbragstadI believe that was something that changed when we consolidated the fernet token provider into the common provider18:26
*** shaohe_feng has quit IRC18:26
amakarovgood point: trust doesn't scope to domains18:26
breton./test_auth.py heavily relies on getting trusts via v2.018:26
*** shaohe_feng has joined #openstack-meeting18:26
ayoungbreaking that is still a backwards non-compat change until v2.0 goes away18:26
lbragstadI worked on getting a patch up for supporting trust auth/validate for v2.018:27
lbragstad#link https://review.openstack.org/#/c/278693/18:27
*** jrist has quit IRC18:27
bretonlbragstad: for fernet or for all types of token?18:27
lbragstadbreton specifically for fernet18:27
jamielennoxis this a fernet only problem?18:27
bretonjamielennox: no18:27
bretonjamielennox: initially i found it for uuid18:27
jamielennoxi'm sure there is trust code in v218:27
lbragstadjamielennox nope18:27
*** flwang1 has joined #openstack-meeting18:28
*** jrist has joined #openstack-meeting18:28
*** julim has quit IRC18:29
stevemarso this should be working with any token provider18:29
stevemarbreton: file a bug and let's get it fixed18:29
lbragstadbreton we can probably fix it with https://review.openstack.org/#/c/278693/ (once it's revived)18:30
*** jrist has quit IRC18:30
*** yamamoto has quit IRC18:30
bknudsonhttps://review.openstack.org/#/c/278693/ says you can validate trust with v218:30
stevemarbreton: file a bug for it, currently https://review.openstack.org/#/c/278693/ is missing one :\18:31
stevemarbknudson: pki18:31
*** julim has joined #openstack-meeting18:31
*** pvaneck has joined #openstack-meeting18:31
bknudsonpki what?18:32
bknudsonhttps://review.openstack.org/#/c/278693/ says that uuid works18:32
*** hoangcx has quit IRC18:32
stevemarbknudson: ah damn, it does eh18:32
stevemarbut breton found the bug with uuid18:32
*** vishnoianil has joined #openstack-meeting18:32
bretonok, i will file a bug18:33
bknudsonthere's a contradiction here.18:33
stevemarbreton: yeah, let's start there, we need more info on this one18:33
stevemari guess the only good part is that no one has noticed this is broken18:34
stevemarnext topic18:34
stevemar#topic Rolling upgrades18:34
*** openstack changes topic to "Rolling upgrades (Meeting topic: keystone)"18:34
stevemarhenrynash: you're up18:34
stevemari'm just about ready to +A this spec, but if anyone else wants to chime in, now is the time18:34
henrynashso that was first thing....18:34
henrynashany other comments? (dtsanek, thanks for yours)18:35
stevemarspec is here: https://review.openstack.org/#/c/337680/18:35
henrynash3 patches are up for implementation, starting at: https://review.openstack.org/#/c/349703/218:35
stevemardolphm: ayoung lbragstad ?18:35
stevemarand it would land for newton18:36
*** shaohe_feng has quit IRC18:36
lbragstadstevemar I haven't weighed in on it yet18:36
henrynashsome of the implementation is still WIP, but it IS functional, and I am closing out some corner cases, adding more testing and then add docs18:36
dstanekhenrynash: the only think i didn't quite get was the steps that appeared to be duplicated18:37
*** shaohe_feng has joined #openstack-meeting18:37
dolphmstevemar: i was pretty happy with our discussion at the midcycle, only had a few nits on the spec itself that i don't care that much about18:37
henrynashdstanek: so I added a comment on that...it is to prevent problems once we have on-the-fly migrations18:37
henrynashdtsanek: but happy to followup with clarifications18:38
*** devananda has quit IRC18:38
stevemarokay i'll give lbragstad til EOD then punt it through18:38
stevemarhenrynash: keep workin on the code ;)18:38
lbragstadstevemar I might not get around to it today - but I trust the judgement of others who have weighed in on it18:39
henrynashstevemar: yes sir18:39
stevemarhenrynash: you even got a +1 from xek18:39
*** Suyi_ has joined #openstack-meeting18:39
stevemarlbragstad: rgr that18:39
henrynashstevemar: yep, gonna bank that one18:39
*** bobh has joined #openstack-meeting18:39
stevemarhenrynash: turns out mulling this over for a year makes it safe18:39
stevemarnext topic18:39
henrynashstevemar; shockin' that18:39
dstanekhenrynash: so in step #3 we have all nodes upgraded and only reading/writing from old column. after that you only need to start reading from the new column18:40
*** Leom has quit IRC18:40
stevemar#topic MFA18:40
*** openstack changes topic to "MFA (Meeting topic: keystone)"18:40
stevemaradriant: o/18:40
stevemarsorry for the wait  :)18:40
adriantnp :)18:40
dstanekhenrynash: i thought that set #5 would actually stop using the old column altogether18:41
stevemarspec: https://review.openstack.org/#/c/345113/ and patch: https://review.openstack.org/#/c/343422/18:41
adriantI'd like to get MFA working in OpenStack, and easiest way without breaking anything is password+passcode concatenation.18:41
*** lpetrut has quit IRC18:41
adriantOptional MFA plugin, works like password auth18:41
stevemaradriant: does it matter to you if this lands in N or O?18:41
adriantjust also checked TOTP if present.18:41
*** saju_m has joined #openstack-meeting18:41
adriantstevemar: N would be better, but can wait18:42
adriantstevemar: I can backport for our own purposes easily enough18:42
henrynashdstanek: (whct you need to prevent is one node that thinks its Ok to write to just the new column and one thinking it only has to read from teh old column...and since I decided against a spooky entaglement at a distance lock, we need a send phase of reboots, I think)18:42
stevemaradriant: so you guys are running something like this already correct?18:42
adriantMy main worry is the v2 api18:42
*** sarob has quit IRC18:42
adriantstevemar: Not yet18:42
adriantstevemar: but the goal is to be up and running with MFA in the next 3-6 months18:42
stevemarrgr that18:43
jamielennoxi have most of the same concerns i've had in the past once we get in to which projects require what level of 2fa, what happens when they don't ahve a totp key etc18:43
adriantjaminelennox: I've kept per project MFA out of this spec and patch18:43
stevemarif no TOTP key, it should act just like password auth18:43
jamielennoxand do federation, but i feel like i've beat that drum a fair bit now18:43
adriantjamielennox: as it's a requirement that would need too much work across all of keystone to make viable18:44
stevemarand no per-project support18:44
*** bobh has quit IRC18:44
jamielennoxyep, ok18:44
*** marekd2 has joined #openstack-meeting18:44
adriantif a project needs MFA, it is up to the project to enforce all users have it active18:44
jamielennoxmost other concerns are negated by the fact we already support a totp of some form18:44
*** Shrews has joined #openstack-meeting18:44
stevemarjamielennox: it'll enable MFA support for SQL users, which as we've found out, a lot of people use -- and they won't be moving all those users to federation any time soon18:45
adriantShould also work for LDAP users.18:45
*** devananda has joined #openstack-meeting18:46
*** devananda has quit IRC18:46
adriantI've suggested in the docs that disabling V2 is part of the suggested method to enable MFA18:46
stevemaradriant: can you elaborate why it won't work with v2?18:46
adriantas I'm not sure touching the V2 auth code for this is a good idea18:46
*** shaohe_feng has quit IRC18:46
*** maeca1 has quit IRC18:46
adriantv2 doesn't appear to be pluggable, and unless edited, does not do the TOTP check.18:47
bknudsonwe don't require tempest testing for features?18:47
*** shaohe_feng has joined #openstack-meeting18:47
*** singhj has joined #openstack-meeting18:47
*** karthikp__ has joined #openstack-meeting18:47
*** devananda has joined #openstack-meeting18:47
rodrigodsbknudson, no :(18:47
adriantstevemar: are there ways to edit the v2 auth without changing the default?18:48
adriantMy worry is, a user with a TOTP cred on v3 will need password+passcode18:48
adrianton v2, just password18:48
adriantso v2 is a way around MFA unless v2 also has some MFA changes18:49
dolphmadriant: don't deploy v218:49
dstanekadriant: disable v2?18:49
*** marekd2 has quit IRC18:49
stevemardstanek: dolphm right, that's what adriant recommended18:49
*** unicell1 has quit IRC18:49
stevemarv2 auth won't be going away for a long time18:49
stevemarI think if the v2 auth limitation is clearly documented then it's good enough.18:50
bknudsonwhy doesn't v2 use the password plugin?18:50
adriantnot the v3 one18:50
*** Sukhdev has joined #openstack-meeting18:50
dolphmbknudson: as in, just hardcode it to use the native password plugin?18:50
adriantbknudson: It looks to be it's own separate auth plugin18:51
bknudsonright, just like v3 auth hardcodes the "external" plugin.18:51
*** mickeys has quit IRC18:51
dolphmthis seems like a rabbit hole. why does v3 hardcode the external plugin?18:51
stevemarwe could create a v2_password plugin18:52
bknudsonv3 uses the "external" plugin if there's EXTERNAL_USER or whatever it is.18:52
jamielennoxlol, don't look at auth!18:53
jamielennoxit makes you sad18:53
adriantstevemar: yep, I've looked at how i could edit that v2 auth controller to support MFA, but I didn't want to edit older defaults.18:53
stevemaradriant: we could just add  credential lookup to the v2 auth code18:53
*** claudiub has quit IRC18:53
*** unicell has joined #openstack-meeting18:53
*** unicell has quit IRC18:53
*** unicell has joined #openstack-meeting18:53
adriantstevemar: maybe, but it would need to be based on if the v3 auth is using the the "password_totp" plugin18:54
stevemarso core team, i'm putting you on the spot here, thoughts on this? y'all are being unusually quiet...18:54
bknudsonfound it: http://git.openstack.org/cgit/openstack/keystone/tree/keystone/auth/controllers.py#n50418:54
bknudsonmy opinion - we need to clean up existing keystone before adding new features.18:54
stevemarlbragstad: dstanek bknudson dolphm jamielennox everyone, yay or nay?18:54
bknudsonotherwise we're just adding technical debt on top of debt.18:54
*** xiaohhui has joined #openstack-meeting18:55
rodrigodsbknudson, this is something that has being raised a couple of times18:55
*** unicell1 has joined #openstack-meeting18:55
bknudsonand using crappy existing code as a reason to not support v2 is a poor excuse.18:55
*** unicell has quit IRC18:55
stevemarbknudson: in my grand scheme, PCI and MFA were the last "features" i wanted to add, then start paying off technical debt18:55
*** devananda has quit IRC18:55
*** Raildo has quit IRC18:55
stevemarso i'm a bit biased here18:55
rodrigodsstevemar, bknudson, can we track somewhere stuff that is simply not good enough and need to be revisited? i guess the next topic falls into that18:56
dstanekstevemar: so what is the proposal...to fix v2?18:56
bknudsonI'm actually fine with the feature since it's optional.18:56
*** shaohe_feng has quit IRC18:56
stevemardstanek: whether or not to add MFA as its designed in the currently spec18:57
*** shaohe_feng has joined #openstack-meeting18:57
bknudsonalthough we really need to start requiring tempest testing for features.18:57
*** carolbarrett has joined #openstack-meeting18:57
*** hoangcx has joined #openstack-meeting18:57
jamielennoxi agree with bknudson, i'm concerned about the layers on layers of stuff and how you do things like message that a 2fa cred is required18:57
jamielennoxthe whole pipeline through there is a disaster18:57
jamielennoxbut honestly the scariest parts of this have already been merged so at this point whatever18:58
dolphmadding totp auth support to v2 is not an API change, right?18:58
*** sarob has joined #openstack-meeting18:58
stevemarjamielennox: the alternative is we wait until the S release to include new features :P18:58
*** sarob has quit IRC18:58
*** sarob has joined #openstack-meeting18:58
*** yamamoto has joined #openstack-meeting18:58
bknudsonadding totp to v2 is as much an api change as adding it to v3.18:58
adriantdolphm: the problem isn't adding totp auth, it's adding password+totp auth18:58
stevemarto the existing password auth18:59
stevemarbah, move to -keystone18:59
dolphmmaybe i need to revisit the new spec again18:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:59
openstackMeeting ended Tue Aug  2 18:59:23 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-08-02-17.59.html18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-08-02-17.59.txt18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-08-02-17.59.log.html18:59
*** xiaohhui has quit IRC18:59
fungiwho's up for another exciting installment of [GENERIC INFRA TEAM WEEKLY MEETING]?18:59
*** pdardeau has joined #openstack-meeting18:59
Shrewsooh, ooh. me!!!18:59
fungigood, i'm not alone ;)19:00
jeblairfungi: who's our sponsor this week?19:00
fungitoday's topics brought to you by craige, fungi, pabelanger19:00
nibalizerwooo meeting19:00
* jeblair is brought to you by a fried chicken sandwich19:00
fungithe part of craige will be played by yours truly in case he's still asleep19:00
* mordred rides in on a pillar of fire fueled by toml thoughts19:00
*** Raildo has joined #openstack-meeting19:01
jeblairoh good, i'm glad we've moved on.  :)19:01
anteayais pabelanger around?19:01
*** gagehugo has left #openstack-meeting19:01
*** Raildo has quit IRC19:01
*** olaph has joined #openstack-meeting19:01
fungimaybe he'll show up before his topic comes around. if not i can move it to last position to give him a few extra minutes to get here19:02
*** amitgandhinz has quit IRC19:03
*** asettle has joined #openstack-meeting19:03
*** mbound has joined #openstack-meeting19:03
*** amitgandhinz has joined #openstack-meeting19:03
*** lpetrut has joined #openstack-meeting19:03
fungiokay, i'll get started19:04
*** karthikp_ has quit IRC19:04
fungi#startmeeting infra19:04
*** karthikp__ is now known as karthikp_19:04
openstackMeeting started Tue Aug  2 19:04: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:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:04
*** openstack changes topic to " (Meeting topic: infra)"19:04
openstackThe meeting name has been set to 'infra'19:04
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:04
*** julim has quit IRC19:04
fungi#topic Announcements19:04
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:04
fungi#info Reminder: late-cycle joint Infra/QA get together to be held September 19-21 (CW38) in at SAP offices in Walldorf, DE19:05
fungi#link https://wiki.openstack.org/wiki/Sprints/QAInfraNewtonSprint19:05
*** pdardeau has left #openstack-meeting19:05
*** amakarov has quit IRC19:05
fungi#info Reminder: get me additions for the announcements section of the meeting if you have any additions for next week19:05
fungi#topic Actions from last meeting19:05
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:05
fungi#link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-07-26-19.03.html19:05
fungipleia2 Submit a spec to host an instance of limesurvey19:05
*** pabelanger has joined #openstack-meeting19:06
*** jamielennox has left #openstack-meeting19:06
*** julim has joined #openstack-meeting19:06
*** enriquetaso has joined #openstack-meeting19:06
fungi#link https://review.openstack.org/349831 spec "Survey Server"19:06
anteayapleia2: thank you19:06
*** rbowen has quit IRC19:06
fungimaybe next week we'll see it proposed for council vote19:06
fungishe mentioned earlier she won't be around for the meeting today19:06
fungibut her spec is here in her place!19:06
fungifungi start a poll for infra mascot19:07
*** fifieldt has quit IRC19:07
*** shaohe_feng has quit IRC19:07
fungidone, have a meeting topic later to discuss the results19:07
fungii haven't officially closed the poll yet, so that i can maintain some air of mystery around the results until we get to that point in the meeting (even i have no idea what people picked!)19:07
fungistay tuned...19:07
fungi#topic Specs approval: PROPOSED: Pholio Service Installation (craige, fungi)19:07
*** openstack changes topic to "Specs approval: PROPOSED: Pholio Service Installation (craige, fungi) (Meeting topic: infra)"19:07
*** rbowen has joined #openstack-meeting19:07
fungi#link https://review.openstack.org/340641 spec "Pholio Service Installation"19:07
fungicraige probably isn't around for the meeting but this is already in progress19:07
*** shaohe_feng has joined #openstack-meeting19:07
fungiso i'm going ahead and seeing if we can get council agreement on it in its latest iteration19:07
fungiallowing us to track the changes a little better19:07
fungiany objection to putting it to a vote by this time thursday?19:08
*** mbound has quit IRC19:08
anteayaI do not object19:08
anteayawe can still tweak the spec if need be after it is published19:08
jeblairno, earlier is better with specs.  :)19:08
fungi#info Spec "Pholio Service Installation" is open for council voting un til 19:00 UTC Thursday, August 419:09
openstackRemoving item from minutes: <ircmeeting.items.Info object at 0x7f5bc06f8e90>19:09
fungi#info Spec "Pholio Service Installation" is open for council voting until 19:00 UTC Thursday, August 419:09
fungistray space snuck into that first one19:09
*** yamamoto has quit IRC19:09
*** prometheanfire has joined #openstack-meeting19:09
*** browne has left #openstack-meeting19:09
fungibasically this is a distillation of the earlier phabricator spec but just for the pholio design wireframe/mockup subsystem so the ui/ux team can move off of the (proprietary) invision service they're using19:10
anteayawhich is a great direction19:10
fungithey've already tried out a demo craige put together a while back and are very eager to be able to use it once we can get it running19:10
anteayaoh wonderful19:10
*** dasanind has joined #openstack-meeting19:11
fungipiet has already started archiving pdfs of their old work from invision so they'll have it to refer to for historical context19:11
fungi#topic Priority Efforts19:11
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:11
fungilooks like no new blockers on the agenda this week19:11
fungi#topic Infra mascot/logo (fungi)19:12
*** openstack changes topic to "Infra mascot/logo (fungi) (Meeting topic: infra)"19:12
fungithought about saving this for last, but i guess we'll just get it out of teh way now19:12
*** carolbarrett has quit IRC19:12
*** dmorita has quit IRC19:12
fungiThe poll has been ended. It was announced to end 2016-08-01 23:59:59 UTC.19:12
fungi#link http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_c2c11d642eafb0e0 and the results and just now coming in...19:13
*** nishaYadav has quit IRC19:13
jeblairis this going to be like brexit?  ("i only voted for ... because i didn't think it would win")19:13
fungitop choices in descending order:19:13
SotKtoo soon :(19:13
anteayaSotK: :(19:13
fungibeaver/woodchuck (i think we just planned for this to be beaver after subsequent discussion)19:14
jeblairSotK, Zara: sorry :(19:14
anteayawell as I said before, ant and bee are ruled by queens19:14
* bkero petitions the leadership for a re-vote followed by searching Google for 'what is the infra?'19:14
anteayawhich I didn't think the group would like the symbology of19:14
*** devananda has joined #openstack-meeting19:14
fungii'll give the full ranked list to heidijoy for review so she can cross off ones that are in conflict with what other teams have already picked19:14
*** prometheanfire has quit IRC19:14
anteayawell keystone picked turtle19:14
fungii like the ant. they work together and build things. the queen is just a figure head after all19:15
fungianyway, we'll see what heidijoy comes back with19:15
*** prometheanfire has joined #openstack-meeting19:15
Shrewscan I now nominate mordred as our queen?19:15
persiaAnt and Bee feeding strategies are also a good map to cores in different projects.19:16
*** MeganR has quit IRC19:16
*** karthik__ has joined #openstack-meeting19:16
fungifair point. my mom does a lot of beekeeping and i hear all sorts of great ideas i should begin applying to our team ;)19:16
zaroShrews: dress him up for a pic19:16
anteayazaro: ++19:16
* fungi would pay for queen mordred photos19:16
*** samuel_ has joined #openstack-meeting19:17
*** samuel_ has quit IRC19:17
fungicrown and sceptre are a must though19:17
*** carolbarrett has joined #openstack-meeting19:17
anteayafungi: I want to see your version of the nectar dance19:17
*** shaohe_feng has quit IRC19:17
*** nishaYadav has joined #openstack-meeting19:17
fungithat'll take some planning19:17
*** shaohe_feng has joined #openstack-meeting19:17
*** nishaYadav is now known as Guest5394119:17
Zarathere are some dramatic videos out there of swarms of bees being removed from walls and things19:17
*** samueldmq has joined #openstack-meeting19:17
Zarahave ended up chain-watching when in the grip of insomnia before19:18
fungiokay, unless anyone else has any important mascot discussion items, we can revisit this next week with something solid19:18
jeblairwe'll have an ascii version of the mascot, right?19:18
fungii thought that was the only version we'd have? ;)19:18
*** fifieldt has joined #openstack-meeting19:18
fungi#topic AFS mirror for puppet module Git repos (pabelanger)19:19
*** openstack changes topic to "AFS mirror for puppet module Git repos (pabelanger) (Meeting topic: infra)"19:19
fungi#link https://review.openstack.org/345669 AFS mirror for puppet module Git repos19:19
*** toddjohn has quit IRC19:19
fungithe floor is yours19:19
fungiand maybe a wall or two19:19
pabelangerThis has come up as part of the effort to remove private infrastructure from tripleo-ci19:19
*** toddjohn has joined #openstack-meeting19:19
pabelangeras a result, they currently mirror some git repos (github.com) to that server19:19
*** toddjohn has quit IRC19:19
*** toddjohn has joined #openstack-meeting19:20
*** toddjohn has quit IRC19:20
pabelangerthere were some objections about mirroring git repos however19:20
fungii think a great example for this is our infra puppet module tests19:20
pabelangersince we don't really like doing that19:20
*** toddjohn has joined #openstack-meeting19:20
jeblairi'd be more on board with this if we had a story about how it was needed by more than one project19:20
fungiwe have jobs that reclone a ton of puppet modules from github for testing (should/can we get them from tarballs or something instead?)19:21
jeblairwhat about puppet-openstack-puppet?19:21
pabelangerRight, I think we could make this use tarballs for puppet modules, and I think tripleo is on board with that.19:21
pabelangerwhich means we don't need a git afs mirror19:21
jeblair(what do they need -- while i go look up which order their project's name is in)19:22
jeblairPuppetOpenStack!  that's the one :)19:22
pabelangerbasically, this is a list of there current mirror: a lot of things are puppet modules19:22
bkeroNon-openstack puppet modules at that19:23
EmilienMnot sure I'm in the context but we have tarballs for every puppet module, tarballs.openstack.org/puppet-*19:23
EmilienMexcept non PuppetOpenStack :-)19:23
pabelangerright, this applies to external puppet modules19:23
jeblairEmilienM: in ci, where do your external dependencies come from?19:24
*** cebruns has quit IRC19:24
*** toddjohn has quit IRC19:24
jeblairso would a local mirror as either a git repo or (daily generated?) tarballs be helpful?19:25
fungiwhich is why i was using our puppet module tests as an exampkle19:25
*** cebruns_ has joined #openstack-meeting19:25
fungiwe do see false negative results from time to time because we failed to clone from github successfully in one of our module test jobs19:26
pabelangerI actually don't know the requirement for tripleo-ci, I was hoping just to offer up another mirror that was under the control of openstack-infra19:26
pabelangerI can go back and find out the answers19:26
jeblairfungi: ya.  i guess we count too, though i'm personally not sure our problems rise to the point of needing this.19:26
fungiagreed, we're an example of the behavior, not necessarily a reason to change anything19:27
*** shaohe_feng has quit IRC19:27
*** shaohe_feng has joined #openstack-meeting19:27
bkeroA lot of the external module cloning comes from using a tool called r10k to clone repos from a file19:28
*** toddjohn has joined #openstack-meeting19:28
jeblairif it's just tripleo that needs this, then, for me, this underscores the unusual situation that tripleo-ci is in19:28
crinklepuppet-openstack sees the same false negatives issue and would benefit from such a mirror19:28
bkeroHere: http://git.openstack.org/cgit/openstack/puppet-openstack-integration/tree/Puppetfile19:28
crinklei can't speak for chef but i would expect they would see the same thing from time to time19:28
*** dmorita has joined #openstack-meeting19:29
jeblair(which we should probably address one way or the other -- either make it part of the ci system available to everyone, or run it as a third-party ci)19:29
mordredit would be important to make sure that things like r10k can deal with the mirror if it's present and if not use the stated upstream19:29
jeblairi also wonder if a proxy would be more appropriate for this?19:29
mordredand/or figure out what pre-cloning would be good for19:29
jeblairour _mirrors_ are _mirrors_ where as this is starting to look more like 'cache some local data'.19:30
*** weshay has quit IRC19:30
pabelangera proxy would work too19:30
*** roxanaghe has quit IRC19:30
mordredssl ?19:30
jeblairmordred: i believe true http proxies support ssl19:32
fungiyeah, looking at the proposed change it's not entirely clear to me how this would be leveraged19:32
*** jamesdenton has quit IRC19:32
pabelangerI am happy to table this for now and move to the next topic. I don't have a need for an answer today, but something I wanted to highlight and get the ball rolling on19:32
fungihow we actually serve up the cache in a way jobs could conveniently consume would be a big (missing) part of this puzzle for me19:33
*** dmorita has quit IRC19:33
*** adriant has quit IRC19:33
bkeroAren't things like this something we traditionally preload on nodepool images?19:33
jeblairpabelanger: i'm happy to discuss further any of the points i raised if you are interested19:33
pabelangerjeblair: sure, I'd like that19:34
*** cdub has joined #openstack-meeting19:34
fungibkero: we have time. there's only one other item on the agenda for today anyway and it's a quick one19:35
fungier, pabelanger ^19:35
fungisorry bkero19:35
*** csomerville has quit IRC19:36
fungii'd be curious how tripleo-ci jobs are currently using their cache of these repos19:36
*** cebruns has joined #openstack-meeting19:36
fungido they have their own custom tooling that knows to look for cached copies before downloading?19:37
fungior are they using some existing puppet ecosystem tool that has that as a feature?19:37
pabelangerright, custom tooling.19:37
fungilike, a primary clone url and a backup one?19:37
*** shaohe_feng has quit IRC19:37
*** yamamoto has joined #openstack-meeting19:37
pabelangerfrom what I see, they simply clone from the mirror 100% of the time19:38
fungiwould you also want the smart http git backend cgi set up on the mirror servers, with the model you're suggesting?19:38
*** shaohe_feng has joined #openstack-meeting19:38
fungior were you thinking they'd just be served as flat filesystem copies?19:38
pabelangerthat way the patch is written is just to use apache to server up the bare git repos.  It's a pretty crude first step19:39
*** vhoward has quit IRC19:40
pabelangerI think for now, the question highlight this is not ready to move forward at the moment and maybe requires a spec to be put in place19:40
*** bobh has joined #openstack-meeting19:40
pabelangerand I am happy to do that and talk more about it19:40
fungisounds good--looking forward to reading that19:40
fungithanks pabelanger!19:40
fungi#topic Attesting to our new artifact signing key (fungi)19:41
*** openstack changes topic to "Attesting to our new artifact signing key (fungi) (Meeting topic: infra)"19:41
fungi#link http://docs.openstack.org/infra/system-config/signing.html#attestation Attesting to our new artifact signing key19:41
*** coolsvap has quit IRC19:41
fungiin short, we have a documented process for infra-root members confirming this signing key via ssh access checking local disk on the puppetmaster server19:41
fungiit would be excellent if as many of us as possible could follow that process soon and push key signatures up to the keyserver network for it19:42
fungii've just done a successfuly test as part of the bindep 2.0.1 release today to create detached signatures for its sdist and wheel and serve them from tarballs.o.o alongside19:43
fungier, successful test19:43
anteayahas anyone other than you attested so far fungi?19:43
*** cody-somerville has joined #openstack-meeting19:43
*** cody-somerville has quit IRC19:43
*** cody-somerville has joined #openstack-meeting19:43
fungianteaya: not to my knowledge19:43
fungiand soon expect that all our new release artifacts on tarballs.o.o19:43
jeblairanteaya: i think we were waiting for fungi to tell us he was ready19:43
ianwfungi: cool, just use our most connected key?19:43
anteayajeblair: ah, very good19:43
fungiianw: yep19:44
fungier, that all our new release artifacts on tarballs.o.o will start having these19:44
fungialso the same key is being used by dhellmann in tests now for automated signing of git tags19:44
fungii think we have a couple of outstanding patches that need review19:44
fungi#link https://review.openstack.org/#/q/topic:artifact-signing+status:open19:45
jeblairfungi: signing01 creates the git tags?19:45
*** gordc has joined #openstack-meeting19:45
fungijeblair: right, from metadata approved by the release team in the releases repo19:45
jeblaircool, gtk19:45
fungijeblair: or at least that's their thought behind it. they want to get out of teh business of pushing tags into gerrit themselves19:45
fungianyway, the attestation instructions are hopefully pretty straightforward19:46
*** Benj_ has joined #openstack-meeting19:46
fungii included an example using gnu privacy guard v219:47
fungibut really it's just a matter of retrieving, signing and pushing up the keysig via whatever tool you're normally comfortable with19:47
mordredfungi: the instructions are straightforward - however, "Some" confused me for about 5 seconds, fwiw19:47
*** bobh has quit IRC19:47
fungithe important bit is making sure the fingerprint of teh key on puppetmaster.o.o matches the fingerprint of teh key you retrieved19:47
*** shaohe_feng has quit IRC19:48
jeblairmordred: the "Some Cycle" is a new HBO production based on a long running fantasy series19:48
*** yamamoto has quit IRC19:48
*** shaohe_feng has joined #openstack-meeting19:48
fungimordred: yeah, the "Some" was a placeholder because i was trying to generalize this process to apply to each time we rotate our per-cycle keys19:49
anteayahow original19:49
fungiokay, any questions on this? if not i'll move on to open discussion time19:50
mordredfungi: yah - I understand that now. also, I have signed the key19:50
*** cleong has quit IRC19:50
mordredthank YOU19:50
fungi#topic Open discussion19:51
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:51
*** dprince has quit IRC19:51
prometheanfiremordred: depending on how close the ansible bits are to being used I'd rather work on adding gentoo support to them than puppet then ansible both19:51
prometheanfirealso, hi19:51
*** ivc_ has quit IRC19:52
mordredhi prometheanfire - I think rcarrillocruz has started looking at that area19:52
prometheanfirecool, I'll try to remember to bug them19:53
jeblairi think we're confused about this again19:53
jeblairwhat ansible bits?19:54
rcarrillocruzjeblair: indeed19:54
prometheanfirethe ones to replace puppet in nodepool images19:54
rcarrillocruzso mordred stuff is about creating base images19:54
jeblairthere are no ansible bits to replace puppet in nodepool images19:54
zarolast week we talked about approving these changes for storyboard gerrit integration: https://review.openstack.org/330922 https://review.openstack.org/330925 and https://review.openstack.org/34451919:54
*** timburke has joined #openstack-meeting19:54
rcarrillocruzi thought the role was about images in general19:54
*** pdardeau has joined #openstack-meeting19:54
jeblairprometheanfire: everything that you and i and others talked about this the last time is still the case19:54
*** edleafe_ has joined #openstack-meeting19:54
rcarrillocruzso yeah, we can use that to create base images and follow the plan as you explained to me about using plain dib elements and nothing puppet19:54
zaroit's still outstanding, was wondering whether if we can get eyes on it?19:55
*** dmorita has joined #openstack-meeting19:55
fungizaro: i think i +2'd them all already, so probably if one other helpful core reviewer has time it'll be a quick review19:55
prometheanfirejeblair: just to be clear then, is the ansible work being done only for infra side? not nodepool side?19:55
fungizaro: hrm, i haven't +2'd those. i'll review this afternoon19:56
zarofungi: a few of them already have 2 +2 but no approval19:56
anteayazaro: I think mordred felt that some of that series would require a gerrit restart or reindex19:56
fungiand approve ;)19:56
fungizaro: oh, right, that was an outstanding question19:56
anteayazaro: do any require a reindex?19:57
fungithe one that adds story tracking lookups implied possibly an addition to the search indexes, so does that require an offline reindexing?19:57
jeblairprometheanfire: i honestly don't know much about it.  i think it's an experimental effort to see about using ansible to create base images for infra.  i'm not certain that we have really discussed it as a group or decided it's a direction we want to go.19:57
prometheanfirejeblair: ah, k, guess it'd be further off then anyway and I should do puppety stuff19:58
*** jrist has joined #openstack-meeting19:58
*** shaohe_feng has quit IRC19:58
jeblairprometheanfire: that is, to create base images for our long running servers19:58
zarofungi: none really needs reindex. 344519 will only work after reindex19:58
*** jesusaur has quit IRC19:58
fungii've as of yet heard nothing to indicate that it would be sane to replace teh puppet bits in our image builds with ansible vs just some shell scripts19:58
*** docaedo has quit IRC19:58
fungizaro: okay, so if we want the feature implemented, we need to plan for a reindex outage (4+ hours or so)19:59
prometheanfirejeblair: ah, diferent then19:59
*** shaohe_feng has joined #openstack-meeting19:59
* Zara is really excited about gerrit integration! :D19:59
zarofungi: sure, that's accurate19:59
*** thingee has joined #openstack-meeting19:59
fungizaro: thanks. we'll make sure to incorporate that into planning for the restart20:00
*** rossella_s has quit IRC20:00
fungioh, we're out of time--thanks everyone!20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Aug  2 20:00:38 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
*** jesusaur has joined #openstack-meeting20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-08-02-19.04.html20:00
*** annegent_ has joined #openstack-meeting20:00
*** rossella_s has joined #openstack-meeting20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-08-02-19.04.txt20:00
bkeroo/ bye20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-08-02-19.04.log.html20:00
fungiall yours, ttx20:00
* gothicmindfood lurks20:00
amrithgreetings from 36,000 feet20:01
ttxdims, dhellmann, flaper87, johnthetubaguy, mestery, mtreinish, thingee, mordred, morgan, russellb, sdague : around ?20:01
* mugsie lurks20:01
* jroll pokes his head in20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue Aug  2 20:01:42 2016 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: tc)"20:01
openstackThe meeting name has been set to 'tc'20:01
ttxHello everyone! Our agenda for today:20:01
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:01
* flaper87 bows and says hi20:01
ttx(remember to use #info #idea and #link liberally to make for a more readable summary)20:02
ttx#topic Limited Use of Alternate Programming Languages vs. Policy and process for alternate programming languages20:02
*** openstack changes topic to "Limited Use of Alternate Programming Languages vs. Policy and process for alternate programming languages (Meeting topic: tc)"20:02
ttx(NB: if the discussion gets too noisy we might switch to voice turns, but let's try simple first)20:02
*** dasanind has quit IRC20:02
ttxWe have two proposals on how we could selectively allow alternate programming languages20:02
ttx#link https://review.openstack.org/33917520:02
ttx#link https://review.openstack.org/34624320:02
*** cody-somerville has quit IRC20:02
ttxThe first one from dims I would summarize as "allow selectively after analysis"20:03
ttxThe second one from notmyname I would summarize as "allow by default, get progress reports, potential veto before merge"20:03
* edleafe_ reads on his phone20:03
*** gatekeep has quit IRC20:03
ttxBoth introduce the concept of two tier of languages (official/supported vs. alternate/unsupported) as a way to clearly state what the "default" languages are.20:03
thingeethat was my understanding of each as well20:03
dimsgood summary ttx20:03
ttxBoth assume that we actually want to allow usage of such alternate languages whenever that usage is "warranted" (i.e. when the default languages can't be used to solve the issue at hand)20:03
ttx(rather than, say,  find a way to artificially keep things written in another language outside of official "OpenStack")20:04
*** gatekeep has joined #openstack-meeting20:04
ttxSo maybe we should first discuss that (agree on the end goal), and if we do, then discuss the less painful and most efficient way to reach it20:04
*** olaph has left #openstack-meeting20:04
ttx(i.e. the best way to discourage gratuitous usage of alternate languages and limit team frustration when rejected)20:04
ttxSo question to TC members to kick this off: how much do you like the idea of allowing usage of alternate languages whenever that usage is "warranted" ?20:04
*** julim has quit IRC20:04
mtreinishttx: define warranted20:05
mtreinishthat's my issue with proposals like that because it's always kinda subjective20:05
flaper87not much. My concerns remain and I think we'll have a hard time defining warranted objectively20:05
ttxmtreinish: as defined above: when the default languages can't be used to solve the issue at han20:05
dimsone thing to add ttx, in my proposal, TC acts as a gatekeeper for new languages and the cross project team acts as keeper for allowing projects to use the blessed languages on a need basis20:05
flaper87My concerns == community impact20:05
russellbi like the idea of allowing usage of alternative languages when warranted.  (for some definition of warranted)20:06
gordcflaper87: community impact on the project or on openstack?20:06
flaper87gordc: both ?20:06
mordredgordc: openstack20:06
flaper87but yeha, mostly openstack20:06
thingeegordc: both20:06
ttxjohnthetubaguy seems +1 on the intent if I read his comments correctly (he had to drop off the meeting)20:07
mordredso ... I don't have well structured thoughts here, even though the topic has been lurking for quite a while now20:07
dhellmannmy reluctance to take this path is still based on the teams asking to go first. One team hasn't demonstrated to me that they need to use another tool, and the other team hasn't demonstrated that they have the community commitment to be the right group to establish best practices for a new tool.20:07
prometheanfirehow are we going to track the dep trees of these new languages, will this need to be done in requirements?20:07
devanandaafter a quick skim of the current state of both specs, i don't see a clear and objective definition of how the TC can decide what is or is not "warranted"20:07
gordcif it's openstack, i'm assuming it's always going to have some non-trivial impact.20:08
notmynamehasn't the idea of alternate languages already come up when javascript was added to python?20:08
*** shaohe_feng has quit IRC20:08
mordrednotmyname: no, not really20:08
ttxnotmyname: I think it was more discussed when we decided to keep Horizon "in" OpenStack20:08
*** Guest53941 has quit IRC20:09
mordredjavascript is not an alternate language for writing openstack services20:09
ttxand JS being grandfathered in as a result20:09
*** dasanind has joined #openstack-meeting20:09
flaper87mordred: ++20:09
annegent_to me, the line is about REST API services also20:09
mordredI do not think JS and openstack is a relevant comparison, grandfathered or no20:09
dimsmordred : ++20:09
notmynamemordred: horizon isn't an openstack service?20:09
ttxyeah, I don't place Go in the same group as JS (or YAML for the matter)20:09
mordredannegent_: yes20:09
annegent_the "pain outweighs gains" warranted line20:09
mordrednotmyname: it does not implement a server process in javascript20:09
ttxbasically we have one language for one task currently20:09
annegent_er, maybe I mean that the other way 'round20:09
mugsiewell, just to play devils advocate ... there is nothing in the policy that blocks a nodejs server project ...20:09
mordrednotmyname: it uses javascript in browser to interact with the REST API it has that is written in python20:09
devanandamordred's point is key -- and also goes to the other languages in your proposal, notmyname20:09
*** macron has joined #openstack-meeting20:09
annegent_mugsie there is policy that blocks that now.20:09
devanandabash and yaml are languages, sure, but have not been used to write an openstack service20:10
mordredwe have PLENTY of non-python code in openstack20:10
notmynameI think my point is that the supported language set used to be len 1, and now it's len > 1. so the idea of "only python is sufficient for openstack" seems to have already been crossed off the list20:10
notmorgandevananda: if you write an openstack service in yaml (only), I'll be so impressed.20:10
annegent_#link http://governance.openstack.org/resolutions/20150901-programming-languages.html20:10
mordredall of that code is in service either of specific communities (ruby for puppet/chef) or domain specific piurposes (browser actions)20:10
*** docaedo has joined #openstack-meeting20:10
jrollnotmorgan: I need deva doing useful things, please don't challenge him :D20:10
ttxyes, so there seems to be room for allowing extra languages whenever Python can really not be used (think JS)20:11
mordrednotmyname: I can see why you'd think that, but I disagree20:11
mtreinishjroll: but I kinda want to see a service all in yaml too :)20:11
mordrednotmyname: and I refer to my previous 2 sentences20:11
notmorganjroll: *shiftyeyes*20:11
*** amitgandhinz has quit IRC20:11
*** amitgandhinz has joined #openstack-meeting20:11
dhellmanncould we cut the chatter today, please?20:11
* edleafe is back home20:12
mordreddhellmann: ++20:12
* jroll apologizes20:12
ttxThe way I see it, we are OK with adding languages where Python can't be used. If Go was used to implement a piece that handled disk i/o in Swift I think we wouldn't have the same discussion -- the issue here is that it also is used for code that we usually run Python for (the REST API)20:12
flaper87ttx: are we waiting for other votes from other TC members? How can we move the discussion forwarD?20:12
flaper87you faster than me20:12
mordredit has been and continues to be my position that if we're going to start rewriting parts of openstack services in not-python, it should be as part of an effort to completely rewrite everything20:12
notmynamettx: an internal api that happens to be rest-ish right now and may or may not be in the future20:13
ttxhence the risk of contagion to other services and the threat of gratuitous usage20:13
*** shaohe_feng has joined #openstack-meeting20:13
russellband if we were rewriting everything, i dont' think language would be problem #1 to deal with20:13
mordredit is my opinion that the cost of just having some bits of some services in python and some in go is not a clear enough win to justify the cost20:13
mugsieso, is the problem the people who asked to use the language, or the possibility of the new language. the former seems to be the bone of contention for some people20:13
notmynamettx: that's what we've been working on in swift in golang20:13
ttxnotmyname: good point -- do you mean there wouldn't be a rewrite of the proxy server in Go ?20:13
thingeerussellb: +120:13
mordredrussellb: ++20:14
*** eumel8 has quit IRC20:14
notmynamettx: I'm not interested in that right now. IMO there's a ton of other stuff we should be focusing on, and the ecosystem cost to dropping python (actually, wsgi) from the proxy server would be huge20:14
*** Leo_ has joined #openstack-meeting20:14
notmynamettx: clarification: I'm not interested in a golang proxy server. I am interested in this discussion and your thoughts20:15
*** docaedo has quit IRC20:15
ttxflaper87: to answer your question, I want to have an idea of how much we support the end goal of those two proposals. We ended up the previous run with the idea that we could explore selectively adf20:15
ttxrather than blanket adding20:15
thingeeas from the thread kevin fox posted on issues that pre-date big tent ... there are some other priority technical issues to be dealt with20:15
ttxThose two proposals propose selective add20:15
ttxso are we ok with that goal ? No point in debating the details of each if we aren't.20:15
notmynamemugsie: good question :-)20:16
*** Leom has joined #openstack-meeting20:16
ttxPersonally I'm fine with the idea, but would like the implementation to prevent contagion20:16
mordredttx: I am not on board with that goal, personally, no20:16
flaper87ttx: you might want to use a #vote here, I guess20:16
flaper87That way I think it'd be clearer20:16
mordredso, consider me in the "no, I don't think it's worth debating details" camp20:16
ttxok, let me set that up20:16
flaper87and it'd also stay logged/summarized20:16
devanandafwiw, I am still not convinced we need to add another language, like Go, within the openstack namespace, for implementing components of the services that a) are implementable in python b) could be implemented as an external library and then consumed by existing python20:17
flaper87I'd also try to avoid the "if warranted" part in the question as that's, imho, not relevant to this vote20:17
mugsieflaper87: ++20:17
annegent_I'd also say I'm unconvinced of a warranted need for a service rewrite in Golang.20:17
*** yamamoto has joined #openstack-meeting20:17
mordredflaper87: ++20:17
ttx#startvote Do we agree with the end goal of selectively allowing extra languages in OpenStack whenever Python ends up not being not the optimal tool for the task? yes, no20:17
openstackBegin voting on: Do we agree with the end goal of selectively allowing extra languages in OpenStack whenever Python ends up not being not the optimal tool for the task? Valid vote options are yes, no.20:17
openstackVote using '#vote OPTION'. Only your last vote counts.20:18
edleafedevananda: +120:18
ttxdoes that work ?20:18
mordredttx: actually ...20:18
mordredI think it would be worth being clearer20:18
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x7f5bbf2ca950>20:18
*** weshay has joined #openstack-meeting20:18
*** roxanaghe has joined #openstack-meeting20:18
mordredsince as notmyname points out we already have other lnaguages20:18
dhellmannyou might have to endvote first? that removed a link...20:18
russellbheh, that undo didn't quite work ..20:18
openstackVoted on "Do we agree with the end goal of selectively allowing extra languages in OpenStack whenever Python ends up not being not the optimal tool for the task?" Results are20:18
ttx#link  https://review.openstack.org/34624320:18
*** shaohe_feng has quit IRC20:18
ttxle sigh20:18
*** flwang1 has quit IRC20:18
mordredI think the thing we're talking about is specifically key/necessary components of services20:18
flaper87"Do we agree with the end goal of selectively allowing extra languages in OpenStack?"20:19
dhellmann#link http://governance.openstack.org/resolutions/20150901-programming-languages.html20:19
*** shaohe_feng has joined #openstack-meeting20:19
*** Leo_ has quit IRC20:19
ttxmordred: propose alt text20:19
mordred"Do we agree with the end goal of selectively allowing extra languages in OpenStack for the purposes of writing services?"20:19
flaper87mordred: ++20:19
* devananda deletes what he was typing20:19
devanandamordred: ++20:19
dims"when absolutely necessary"? :)20:19
ttxmordred: dedfine services, as the objectserver is an internal node in Swift... would that count ?20:19
mordredttx: yes20:20
ttxWould the dns proxy from designate count ?20:20
russellb"However we should not limit OpenStack service projects to these three programming languages in the future, as it would either mean using suboptimal tools, not being able to address specific problem spaces, or artificially excluding specific project teams."20:20
mordredit's a key/required part of the swift service20:20
devanandarussellb: three?20:20
russellbdevananda: quote from the resolution dhellmann linked, bash/JS/Python20:20
mordredthat hummingbird is not the rest api itself does not make it any more essential in a world where it's merged, to swift as a service20:20
ttxmordred: ok, so services/nodes20:20
ttxlet me cast that one20:21
mordredsorry for that mistype -it really does change the meaning of the sentence20:21
mugsiettx: miniDNS is also a required sub service of designate20:21
mordredmugsie: we do not write miniDNS20:21
mugsiedesignate does20:21
mordredoh - is that the go dns thing?20:21
*** lpetrut has quit IRC20:21
mugsiedesignate-mdns is (currently) a pythoin DNS server20:21
mordredso yes - I agree, it's the equivilent example20:22
mugsiemdns stands for miniDNS20:22
annegent_is miniDNS something that can be reviewed and packaged separately?20:22
ttx#startvote Do we agree with the end goal of selectively allowing extra languages in OpenStack for the purpose of writing services? yes, no20:22
openstackBegin voting on: Do we agree with the end goal of selectively allowing extra languages in OpenStack for the purpose of writing services? Valid vote options are yes, no.20:22
openstackVote using '#vote OPTION'. Only your last vote counts.20:22
mordred#vote no20:22
flaper87#vote no20:22
mtreinish#vote no20:22
ttx#vote yes20:22
thingeeannegent_: this was our proposal to have the separate swift component written in go be packaged separately.20:22
dims#vote yes20:22
dhellmann#vote no20:22
thingee#vote no20:23
russellb#vote yes20:23
ttx(for some serious amount of "selectively"20:23
annegent_#vote no20:23
* edleafe wishes he could vote...20:23
sdague#vote no20:23
openstackVoted on "Do we agree with the end goal of selectively allowing extra languages in OpenStack for the purpose of writing services?" Results are20:23
openstackyes (3): dims, ttx, russellb20:23
openstackno (7): annegent_, mtreinish, thingee, sdague, mordred, dhellmann, flaper8720:23
ttxOK, so far from consensus with heavy leaning on NO20:24
ttxMy next question then would be...20:24
ttxHow do we address Swift needs ? What is their next step ?20:24
notmynamefantastic question20:24
ttxThey clearly rujn into an issue where Python don't get them the disk i/o behavior they need20:24
*** toddjohn has quit IRC20:25
thingeettx: when this was originally proposed, the TC recommended it be packaged separate for the component that warrants a different language.20:25
russellbartificial code split of in/out of OpenStack is kind of lame IMO...20:25
jbrycerussellb: ++20:25
mugsierussellb: ++20:25
edleafeWasn't the suggestion that hummingbird be packaged separately rejected becuase it would "fracture the team"?20:25
*** docaedo has joined #openstack-meeting20:25
dougwigrussellb: so is an inconsistent policy in this case.20:25
ttxrussellb: yes, I'm not happy with that solution either20:25
devanandathingee: that has been my suggestion a couple times, but it creates a significant impact on any developer(s) writing the go-side of that20:25
ttxAll those who voted no, would the "external" development be your answer to the "next step" question, or do you have other ideas ?20:25
thingeedevananda: for the folks who have leaned on separate packaging, it was to reduce the impact by having it be on a project, not the entire community.20:26
notmynamebeyond the team impact (which would be huge), it would also have a significantly high technical cost, and beyond that, it would force us into a situation of presenting to users an upstream "openstack" version that isn't supported/maintained or just flat out missing20:26
mordredttx: IFF the external development item can be installed via normal distro package mangaers in a way that allows for pip + other-requirements to express the need20:26
*** toddjohn has joined #openstack-meeting20:27
edleafenotmyname: there are lots of requirements that are used by projects that are not part of OpenStack20:27
tdasilvadoes "external" development mean completely outside of the openstack namespace?20:27
mordredttx: if the thing is an external component that is onlyu installable by cloning a git repo and running a build process somewhere, I do not think that would be particularly useful20:27
edleafethat doesn't make them any less 'upstream'20:27
dhellmanntdasilva : no20:27
ttxtdasilva: no, just outside of TC's reach20:27
flaper87ttx: that would be the solution I'd propose too.20:27
ttxso smae tooling20:27
flaper87tdasilva: CI/gerrit/etc will still be available20:28
*** yamamoto has quit IRC20:28
ttxwhich kinda reduces the technical pain, but the lameness stays imho20:28
tdasilvaso we would break apart a repo like openstack/swift and openstack/hummingbird just because....seems really lame20:28
*** efried has joined #openstack-meeting20:28
jbrycefor me it’s not just about hummingbird, it’s about losing the thing that has made openstack work as a competitive maketplace of ideas. tools will change and grow. many of the things we use for our great development process around python didn’t exist in their form before we put them together over the last few years. future innovation is going to happen in languages other than python and that can happen in openstack or20:28
jbryceoutside of openstack, wherever those contributors feel welcome20:28
russellblame++ :)20:28
mugsiei will give an example from designates side - for us to add a new record type  (A, AAAA, CNAME, etc) we would have to release a version of designate that created the tables, then a version of mdns that could render it to wire format, then a version of designate that used the version of mdns with tghe new code20:28
devanandasame tooling, with the end goal of being packaged by various distros and installable via apt/yum/... would be technically feasible and yet still alienate that team20:28
russellbjbryce: ++20:28
*** shaohe_feng has quit IRC20:29
mordredanother option is to write performance critical bits in cython or something similar20:29
jbrycesometimes it feels to me like when a proprietary company gets really stuck on the decision of what to do when they have a cash machine on an existing product while facing a disruption from a cheaper competitor20:29
*** shaohe_feng has joined #openstack-meeting20:29
*** dimtruck is now known as zz_dimtruck20:29
ttxThere is another solution, which is to grant Swift a specific exception, but it's also lame because it's just one more way Swift is special, and this time it's not coming from them20:29
jbrycemordred: the thing is, developers in our community already wrote a more performant version. they wrote winning code and a winning implementation20:29
mtreinishmordred: that is the normal pattern for something like this20:30
mugsiemordred: that is a possiblity  - but are we allowed?20:30
mugsieits C, whihc is not on the list20:30
edleafemordred: you could write them in go and compile to a Python module20:30
mugsiewhich comes back to the "ever have a new language vote" that just happened20:30
russellbright, not sure why that's different or better (Python C bindings)20:30
*** toddjohn has quit IRC20:31
dougwigif you're setting the expectation of non-python projects in infra as non-openstack projects, what kind of priority level for support will there be for breakages?  i would implicitly assume it's less than official projects?20:31
ttxdougwig: best effort I would say, yes20:31
*** singhj has quit IRC20:31
*** dfflanders has quit IRC20:31
mugsiewhich some of the critical gate infra structure might rely on20:31
jbrycethe thing that can keep an open community from falling into that proprietary company trap (milk the cash cow or disrupt yourself because someone else will do it if you don’t), is that we don’t have the income imperative and we can develop these technologies in the open and see which approaches are working or not.20:32
mugsiei.e. if there is a bug in hummingbird and it is an unoffical project - but it blocks the gate for $reason - what do we do?20:32
*** e0ne has quit IRC20:32
annegent_jbryce my sense is that it's the plugability that I struggle with. If you can't make the golang piece plugable it means you're abandoning the other service implementation?20:32
mordredmugsie: actually, cythion  is done in a python syntax, and pip/setuptools deals with it just fine20:32
mordredso to me it's still 'python'20:32
mugsiemordred: OK, I would not have made that distinction.20:33
annegent_jbryce which is what I read from notmyname "presenting to users an upstream "openstack" version that isn't supported/maintained or just flat out missing"20:33
mordredjbryce: I hear that argument, I really do. I'm not ignoring it. just in my personal best judgement it is not currently worth the pain20:33
annegent_jbryce it's still too black and white.20:33
dhellmannmy concerns about doing this, in this way, starting with this team, are too long for irc, so: http://paste.openstack.org/show/545744/20:34
ttxMy desired outcome here is that we find a solution for Swift that lets them use the tech they need, but without creating a contagion effect of gratuitous rewrites throughout OpenStack services. I'd also like an outcome where other Python coders in our community would go and help Designate write their stuff in Python (or allow them to use Go too if that ends up not being possible, but I don't20:34
ttxbelieve in that). Feels like I'm a minority though20:34
*** singhj has joined #openstack-meeting20:34
mordredjbryce: I do not believe we have achieved the success we have achieved by letting everyone do everything in whatever way they feel. in fact, I think we have achieved success in spite of the amount of divergence we already have. I do not believe introduction of more divergence will lead to greater success20:34
ttx#link http://paste.openstack.org/show/545744/20:34
russellbttx: i'm with you.20:34
mordredthat is, of course, merely my point of view, and as always, I'm happy to defer to others happily should I wind up to be wrong20:35
*** docaedo has quit IRC20:35
mugsiedhellmann: so, your conceres are still the teams, not the "should we have another language" ?20:35
russellbbut i'm not getting the feeling that any positions are changing here20:35
dhellmannmugsie : both, but this is why I'm comfortable sticking with "no" for now20:36
devanandajbryce: innovation is happening in many languages, not just golang or python, but our development process/tooling is, as you pointed out, pushing the envelope of what can be done with python. allowing in another language doesn't immediately create the same benefits for that languages' developers20:36
dhellmannmugsie : all of the community division and technical divergence concerns I have would be addressed better by a team that had proven willing to collaborate on those areas in the past20:36
sdaguemordred: I think I mostly agree with you there, especially as someone that has wrangled with a lot of that divergence (though less so than dhellmann)20:36
JayFdevananda: jbryce: My fear; and I think the underlying fear in jbryce's comments, is that we'll lose smart folks who want to point their brain in that direction, rather than winning them over to the "OpenStack way"20:37
jbrycedevananda: but goland is the other language where innovation is happening amount OUR developers already. right now. dramatically improving the operation of a core service20:37
devanandajbryce: in fact, trying to enable the same scale of development process we have done in Python for other languages will take away resources from what we're doing with pyhton today20:37
mordredjbryce: it improves the operational performance. it does not improve its alignment with the operation of the other openstack services20:37
jbrycedevananda: that’s assuming that making an inclusive decision here will not include anyone else who wants to pitch in on those things20:37
ttxSo my read of the TC today is "the majority of us don't want to selectively add alternate languages, components in another language should be written as unofficial repositories and be depended on" -- is that correct ?20:37
dhellmannttx: that is my position, for now20:38
flaper87ttx: yes20:38
*** rhagarty has quit IRC20:38
annegent_mine as well20:38
mordredttx: yes20:38
ttxI'll info it then20:38
mugsiedhellmann: what could be done to help move your position?20:38
dhellmannmugsie : address the concerns I've described in that pastebin20:38
ttx#info the majority of us don't want to selectively add alternate languages, components in another language should be written as unofficial repositories and be depended on20:39
*** shaohe_feng has quit IRC20:39
annegent_mugsie I won't speak for dhellmann but addressing the concerns listed there would help show a willingness and attitude shift.20:39
dhellmannmugsie : and not just ticking the boxes, but demonstrating a difference in approach over the long term20:39
mordredannegent_, dhellmann ++20:39
ttxstill need to read that pastebin20:39
mugsiedhellmann: and for designate - I would think we cover most if not all of these20:39
russellbwhat we call "in" vs "out" of openstack is feeling more and more artificial and meaningless ... this position makes that worse20:40
*** shaohe_feng has joined #openstack-meeting20:40
dhellmannmugsie : in the email thread where this came up someone showed significant performance improvements with what seemed like quite small changes to designate, so you haven't met the technical bar, in my mind20:40
jbrycerussellb: ++20:40
ttxrussellb: worse, but not unfixable in the future20:40
mugsiedhellmann: they were not "quite small"20:41
dhellmannrussellb : my position isn't set in stone. this is how I feel today, based on what I've seen20:41
ttxi.e. having a separate repo for the Go piece kinda makes sense to me20:41
mordredrussellb: same with dhellmann20:41
mordredI could totally be convinced20:41
dhellmannmugsie : ok, my impression was that some were things like moving database queries out of tight loops20:41
mordredI just have not yet been convinced20:41
ttxi.e. one language per repo20:41
ttxthat's sane practice anyway20:41
dhellmannmugsie : I have not tried to dig into the patches myself, so I may be completely misunderstanding20:41
notmynamettx: shall we drop rst and yaml and bahs from repos that include python?20:41
mordrednotmyname: no, and you know that's not the case20:42
mtreinishttx: yeah, that would make things much easier to swallow for me too20:42
mtreinishI work in some dual language repos, it makes things more difficult20:42
mugsiedhellmann: there was never any patches. just numbers, and a direction to "go use caching"20:42
ttxnotmyname: ask distro packagers (that's where my belief comes from) and they will tell you the same thing20:42
mugsiewhich, for a component that can be global distributed is .... interesting20:42
devanandanotmyname: that's a strawman. rst and yaml are not service languages, they're documentation and configuration.20:43
annegent_russellb jbryce in and out, it's a false dichotomy that I won't buy into. I'm definitely willing to keep discussing and become convinced of a solution.20:43
dougwigthis entire discussion feels to me like we are letting day-to-day operational concerns define the vision and scope of openstack, which feels entirely backwards to me.  IMO.20:44
edleafeannegent_: +120:44
JayFTo be clear; an alternative not yet mentioned here would be for swift to voluntarily choose to not be an official openstack project anymore as a whole, correct?20:44
jbryceannegent_: you just told them it’s out20:44
*** jrichli has joined #openstack-meeting20:44
mordredre: in and out - I don't think this has created a false dichotomy at all. I think that we've said "we want to be able to install openstack via  a combination of pip and distro packaging"20:44
ttxSo the way forward that the majority recommends for Swift is, if I read right, to land the alternate object server in Go (hummingbird) into a specific repo and make it unofficial for the time being20:45
mordredmany of our python projects have dependencies that are not written in python - but we consume them from stanard linux distro sources20:45
mordredwhere those components is developed, whether in openstack's repos or elsewhere, is irrelevant20:45
flaper87JayF: it wasn't mentioned here but it was mentioned when this discussion started. I'm not advocating for that, though.20:45
ttxI have the feeling this is not the last time we discuss this20:45
flaper87ttx: ++20:45
mugsiedougwig: ++20:45
flaper87ttx: but that's good, isn't it ?20:45
edleafePlease don't forget the middle ground of gopy - https://github.com/go-python/gopy20:46
* flaper87 has no problems with revisitng this again in the future20:46
ttxyes, it's good, just not sure how practical the proposed way forward is for Swift20:46
jbrycemordred: i disagree that it’s irrelevant. but we may need to be on a beach to really have this discussion. = )20:46
*** kamal__ has quit IRC20:46
*** tonytan4ever has quit IRC20:46
flaper87ttx: It's a start, for sure.20:46
mordredjbryce: :)20:46
*** kamal__ has joined #openstack-meeting20:46
ttxWe need to switch topic20:47
mordredjbryce: I think what I'm trying to say is that if people are hearing a weird false distinction, then we're communicating something wrong20:47
mordredthe actual thing is quite clear and distinc to me20:47
dhellmannmugsie : you're right, I don't see actual patches in http://lists.openstack.org/pipermail/openstack-dev/2016-May/094568.html20:47
mordredjbryce: I'd be more than happy to use you as a sounding board to figure out who we're being unclear though20:47
tdasilvaI just don't understand how this decision helps with all the arguments being made. In the end, swift will be forced to create another repo, where we you have swift developers in reviewing/writing code in both. It won' t really help with the 'community impact' anyway...20:47
mugsiedhellmann: fwiw i asked - I was quite interested in them20:48
ttxtdasilva: I think the idea is taht it will prevent contagion and further fragmentation20:48
tdasilvawill it?20:48
mordredtdasilva: we're focused on the total of openstack developers broadly, not the swift developers specifically. yes, this will suck for swift. sometimes things suck for one part of a larger whole20:48
dhellmannmugsie : good, and I expect there's a lot more to the story that I haven't heard20:48
ttxtdasilva: I'm not convinced, which is why I voted for some sort of compromise20:48
gordcis there a requirement that they maintain both the 'unofficial' go version and the 'official' python version?20:49
flaper87The compromise I voted for is to start with this and evaluate the growth and impact as it comes20:49
flaper87Also, what dhellmann said in the pastebin20:49
ttxgordc: no20:49
tdasilvamordred: it's not just that it sucks for swift, but we might be forcing other projects to follow the same route.20:49
*** shaohe_feng has quit IRC20:49
ttxgordc: a lot of things in openstack depend on components written in other languages outside teh official projects20:49
*** rbowen has quit IRC20:49
*** shaohe_feng has joined #openstack-meeting20:49
ttxnothing says 'everything has to be python'20:50
mordredtdasilva: my desire would be that they learn from this experience and don't get themselves into such a rough place20:50
flaper87mordred: ++20:50
ttxok, next topic20:50
*** docaedo has joined #openstack-meeting20:50
notmynamemordred: nice project you got there. shame if something were to happen to it20:50
ttx#topic Adds a docs: URL entry to projects.yaml20:50
*** openstack changes topic to "Adds a docs: URL entry to projects.yaml (Meeting topic: tc)"20:50
ttx#link https://review.openstack.org/31639620:50
annegent_thanks dhellmann for the patche20:50
ttxthis one is close but it's a rebase hell so I think we can quickly rebase / review / merge it in-meeting and be done20:51
mtreinishI had a question inline, it lgtm though20:51
annegent_notmyname threats do not have a place here.20:51
annegent_mtreinish ok20:51
annegent_mtreinish I can look20:51
mtreinishit was just about projects that use developer/ for everything not just contribution docs20:51
* flaper87 not a super fan of the missing `api` items but he's got no strong opinions there20:51
dhellmannmtreinish : that's a good point20:52
annegent_mtreinish oh right. that's not what we're looking for _quite_ yet, mostly need to get a handle on the sizes.20:52
mugsieit is a lot of projects20:52
notmynameapologies, my last comment wasn't meant to be a threat at all. it didnt' translate in text20:52
ttxnotmyname: I read it as joke fwiw20:53
mugsieand linking to designate/developer has a lot of completly unreleated docs20:53
annegent_such as, Oslo has 28 of the 80 contributor docs links20:53
*** cody-somerville has joined #openstack-meeting20:53
mtreinishannegent_: size as in the number of things that have things up on docs.o.o/developer?20:53
ttxannegent_: given how difficult it is to merge things without triggering a merge conflict, I'd rather approve it now if we can20:53
dhellmannttx: ++20:54
mugsieshould this not link to the actual contributor docs?20:54
annegent_mtreinish mugsie yeah, basically a content audit when there's 80 projects, what percentage are developer-centric? Turns out quite a lot on a page basis.20:54
thingeettx: +120:54
* dims just finished reading the pastebin 20:54
mtreinishttx: I was fine with landing it as is, since it helps. I was just worried about the messaging around contributor (or whatever it was)20:54
annegent_ttx yay yes20:54
flaper87ttx: ++20:54
mtreinishbut we can fix that in a followup20:54
ttxok, let's merge it now then, please pile on +1s20:54
annegent_mtreinish yes, I do want to address that eventually...20:54
dhellmannmugsie : with this patch in place, I think annegent_ could ask teams to "fix" their links either in this repo, or by getting publishing working, or both20:54
*** jrichli has left #openstack-meeting20:54
*** pabelanger has left #openstack-meeting20:54
annegent_mugsie also I think it might help us think more about "frameworks" for docs rather than "write the docs"20:55
mugsiedhellmann: annegent_ ack20:55
mugsieannegent_: you read my mind :)20:55
annegent_:) check!20:55
*** marekd2 has joined #openstack-meeting20:55
*** notmyname has quit IRC20:55
mtreinishdhellmann: did you mean to -1 the patch? There wasn't a reason on it20:56
dhellmannmtreinish : no, I can't remember how to use gerrit20:56
mtreinishdhellmann: heh, that's what I figure it was :)20:56
*** yamamoto has joined #openstack-meeting20:57
dhellmannmtreinish : thanks for pointing that out :-)20:57
ttxok, merging now20:57
*** csomerville has joined #openstack-meeting20:57
ttx#topic Open discussion20:57
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:57
ttxI'll miss next week meeting again -- flaper87 still interested in replacing me ?20:57
annegent_thanks all, whew!20:57
flaper87ttx: yup, I'll be around20:58
amrithannegent_ ++20:58
dimsdhellmann : will you be posting that pastebin somewhere? Mailing list? gerrit comment?20:58
*** kbyrne has quit IRC20:58
dhellmannI would appreciate some more feedback on the "goals" process proposal: https://review.openstack.org/#/c/349068/20:58
ttxAnything else, anyone ?20:58
flaper87#link https://review.openstack.org/#/c/342069/20:58
ttxdhellmann: I was a bit surprised at the initial reaction on it... A lot of people seemed to conflate defining a few release themes into some intolerable intrusion in project design territory20:58
dhellmanndims : I hadn't planned to post it anywhere other than these meeting logs20:58
flaper87round-table discussions for meetbot20:58
flaper87needs some love20:58
* flaper87 will ping infra folks20:59
flaper87mordred: https://review.openstack.org/#/c/342069/20:59
dimsdhellmann : the content may get lost :(20:59
dhellmannttx: I was less surprised by that than the concern about being kicked out immediately20:59
russellbflaper87: cool patch :)20:59
flaper87russellb: thanks :D20:59
dhellmanndims : ok, I'll post it as a comment on your patch20:59
*** elo has quit IRC20:59
dimsthanks dhellmann !20:59
* flaper87 will add more to it as soon as the first version lands20:59
*** shaohe_feng has quit IRC20:59
anteayathanks ttx21:00
amrithdhellmann, yes, surprising reactions.21:00
*** toddjohn has joined #openstack-meeting21:00
*** shaohe_feng has joined #openstack-meeting21:00
*** marekd2 has quit IRC21:00
ttxok, end of meeting, thanks everyone21:00
*** cody-somerville has quit IRC21:00
russellbbye, all21:00
*** dasanind has quit IRC21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
dimsthanks ttx21:00
openstackMeeting ended Tue Aug  2 21:00:41 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-08-02-20.01.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-08-02-20.01.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-08-02-20.01.log.html21:00
amriththx ttx21:00
*** JRobinson__ has joined #openstack-meeting21:01
*** timburke has left #openstack-meeting21:01
*** ihrachys has quit IRC21:02
*** toddjohn has quit IRC21:03
*** toddjohn has joined #openstack-meeting21:03
*** ivc_ has joined #openstack-meeting21:04
*** amitgandhinz has quit IRC21:04
*** yamamoto has quit IRC21:04
*** yamamoto has joined #openstack-meeting21:05
*** dasanind has joined #openstack-meeting21:05
*** banix has quit IRC21:06
*** macron has quit IRC21:07
*** baumann_ has quit IRC21:07
*** baumann has joined #openstack-meeting21:07
*** jungleboyj has quit IRC21:08
*** toddjohn has quit IRC21:09
*** enriquetaso has quit IRC21:09
*** shaohe_feng has quit IRC21:10
*** mickeys has joined #openstack-meeting21:10
*** cdub has quit IRC21:10
*** singhj has quit IRC21:10
*** yamamoto has quit IRC21:10
*** mbound has joined #openstack-meeting21:11
*** shaohe_feng has joined #openstack-meeting21:12
*** baumann has quit IRC21:13
*** dasanind has quit IRC21:14
*** singhj has joined #openstack-meeting21:15
*** thorst has quit IRC21:16
*** karthik__ has quit IRC21:16
*** ivc_ has quit IRC21:16
*** thorst has joined #openstack-meeting21:16
*** ivc_ has joined #openstack-meeting21:17
*** ivc_ has quit IRC21:18
*** kbyrne has joined #openstack-meeting21:19
*** singhj has quit IRC21:19
*** shaohe_feng has quit IRC21:20
*** thorst has quit IRC21:20
*** shaohe_feng has joined #openstack-meeting21:21
*** kebray has joined #openstack-meeting21:24
*** rockyg has quit IRC21:25
*** sarob has quit IRC21:25
*** kebray has quit IRC21:25
*** _sarob has joined #openstack-meeting21:26
*** pvaneck has quit IRC21:26
*** pvaneck has joined #openstack-meeting21:27
*** shaohe_feng has quit IRC21:30
*** sdague has quit IRC21:30
*** lblanchard has quit IRC21:31
*** baoli has quit IRC21:31
*** shaohe_feng has joined #openstack-meeting21:31
*** annegent_ has quit IRC21:33
*** pnavarro has quit IRC21:34
*** flwang1 has joined #openstack-meeting21:34
*** mriedem has quit IRC21:36
*** shaohe_feng has quit IRC21:40
*** karthik__ has joined #openstack-meeting21:41
*** designbybeck_ has quit IRC21:41
*** shaohe_feng has joined #openstack-meeting21:41
*** singhj has joined #openstack-meeting21:41
*** rockyg has joined #openstack-meeting21:43
*** Na3iL has joined #openstack-meeting21:44
*** bobh has joined #openstack-meeting21:44
*** prometheanfire has left #openstack-meeting21:46
*** jmckind has quit IRC21:46
*** tonytan4ever has joined #openstack-meeting21:47
*** bobh has quit IRC21:49
*** ivc_ has joined #openstack-meeting21:50
*** shaohe_feng has quit IRC21:51
*** shaohe_feng has joined #openstack-meeting21:51
*** lbrune has joined #openstack-meeting21:52
*** tonytan4ever has quit IRC21:52
*** rockyg has quit IRC21:53
*** markvoelker has quit IRC21:54
*** mageshgv has quit IRC21:56
*** lbrune has quit IRC21:56
*** karthik__ has quit IRC21:58
*** annegentle has joined #openstack-meeting21:58
*** esberglu has quit IRC22:00
*** shaohe_feng has quit IRC22:01
*** shaohe_feng has joined #openstack-meeting22:02
*** singhj has quit IRC22:02
*** singhj has joined #openstack-meeting22:03
*** alyson_ has quit IRC22:03
*** ivc_ has quit IRC22:04
*** amitgandhinz has joined #openstack-meeting22:05
*** rbak has quit IRC22:05
*** Apoorva_ has joined #openstack-meeting22:06
*** efried has quit IRC22:07
*** rbak has joined #openstack-meeting22:09
*** Apoorva has quit IRC22:09
*** asettle has quit IRC22:10
*** amitgandhinz has quit IRC22:10
*** mageshgv has joined #openstack-meeting22:11
*** shaohe_feng has quit IRC22:11
*** shaohe_feng has joined #openstack-meeting22:12
*** sindhu has quit IRC22:12
*** lbrune has joined #openstack-meeting22:13
*** rfolco_ has quit IRC22:15
*** annegentle has quit IRC22:16
*** zz_dimtruck is now known as dimtruck22:16
*** sindhu has joined #openstack-meeting22:18
*** lbrune has quit IRC22:18
*** weshay has quit IRC22:19
*** shaohe_feng has quit IRC22:21
*** elo has joined #openstack-meeting22:22
*** lpetrut has joined #openstack-meeting22:22
*** gordc has quit IRC22:22
*** shaohe_feng has joined #openstack-meeting22:22
*** _sarob has quit IRC22:24
*** sarob has joined #openstack-meeting22:24
*** singhj has quit IRC22:25
*** dane_leblanc_ has quit IRC22:26
*** jckasper has quit IRC22:27
*** hoangcx has quit IRC22:28
*** sarob has quit IRC22:28
*** eharney has quit IRC22:30
*** Na3iL has quit IRC22:30
*** lpetrut has quit IRC22:31
*** Na3iL has joined #openstack-meeting22:31
*** shaohe_feng has quit IRC22:32
*** shaohe_feng has joined #openstack-meeting22:32
*** ivc_ has joined #openstack-meeting22:33
*** sindhu has quit IRC22:34
*** lbrune has joined #openstack-meeting22:35
*** singhj has joined #openstack-meeting22:35
*** julenl has quit IRC22:37
*** lbrune has quit IRC22:40
*** sdake has quit IRC22:40
*** mbound has quit IRC22:41
*** karthik__ has joined #openstack-meeting22:41
*** shaohe_feng has quit IRC22:42
*** sindhu has joined #openstack-meeting22:43
*** Apoorva_ has quit IRC22:43
*** Apoorva has joined #openstack-meeting22:44
*** ivc_ has quit IRC22:44
*** shaohe_feng has joined #openstack-meeting22:45
*** ivc_ has joined #openstack-meeting22:45
*** hoangcx has joined #openstack-meeting22:47
*** carolbarrett has quit IRC22:48
*** sindhu has quit IRC22:48
*** delattec has joined #openstack-meeting22:48
*** mbound has joined #openstack-meeting22:49
*** zhipeng has quit IRC22:49
*** david-lyle has quit IRC22:50
*** Na3iL has quit IRC22:50
*** cdelatte has quit IRC22:51
*** david-lyle has joined #openstack-meeting22:51
*** shaohe_feng has quit IRC22:52
*** yamahata has quit IRC22:52
*** shaohe_feng has joined #openstack-meeting22:53
*** mbound has quit IRC22:54
*** uxdanielle has quit IRC22:55
*** singhj has quit IRC22:56
*** spzala has quit IRC22:56
*** lbrune has joined #openstack-meeting22:56
*** spzala has joined #openstack-meeting22:57
*** tpsilva has quit IRC22:58
*** sindhu has joined #openstack-meeting22:58
*** banix has joined #openstack-meeting22:59
*** singhj has joined #openstack-meeting23:00
*** mriedem has joined #openstack-meeting23:00
*** spzala has quit IRC23:01
*** lbrune has quit IRC23:01
*** rbak has quit IRC23:01
*** sarob has joined #openstack-meeting23:02
*** shaohe_feng has quit IRC23:02
*** shaohe_feng has joined #openstack-meeting23:03
*** julim has joined #openstack-meeting23:03
*** merooney has quit IRC23:04
*** firin has joined #openstack-meeting23:04
*** singhj has quit IRC23:04
*** ivc_ has quit IRC23:05
*** amitgandhinz has joined #openstack-meeting23:07
*** marekd2 has joined #openstack-meeting23:07
*** mickeys has quit IRC23:09
*** mickeys has joined #openstack-meeting23:10
*** spzala has joined #openstack-meeting23:11
*** amitgandhinz has quit IRC23:11
*** marekd2 has quit IRC23:12
*** shaohe_feng has quit IRC23:13
*** firin has left #openstack-meeting23:13
*** shaohe_feng has joined #openstack-meeting23:13
*** yamahata has joined #openstack-meeting23:13
*** mickeys has quit IRC23:14
*** sdake has joined #openstack-meeting23:15
*** sdake_ has joined #openstack-meeting23:17
*** lbrune has joined #openstack-meeting23:19
*** sdake has quit IRC23:20
*** sdake_ is now known as sdake23:21
*** mickeys has joined #openstack-meeting23:22
*** saju_m has quit IRC23:23
*** shaohe_feng has quit IRC23:23
*** shaohe_feng has joined #openstack-meeting23:23
*** lbrune has quit IRC23:24
*** xyang1 has quit IRC23:29
*** mrmartin has quit IRC23:33
*** shaohe_feng has quit IRC23:33
*** edleafe_ has quit IRC23:34
*** radek_ has quit IRC23:34
*** shaohe_feng has joined #openstack-meeting23:34
*** liyifeng has joined #openstack-meeting23:34
*** leeantho has quit IRC23:37
*** csomerville has quit IRC23:38
*** RuiChen has quit IRC23:38
*** Benj_ has quit IRC23:38
*** kaminohana has joined #openstack-meeting23:38
*** tochi has joined #openstack-meeting23:39
*** lbrune has joined #openstack-meeting23:41
*** sigmavirus is now known as sigmavirus_away23:41
*** shaohe_feng has quit IRC23:43
*** bill_az has quit IRC23:44
*** shaohe_feng has joined #openstack-meeting23:44
*** lbrune has quit IRC23:45
*** Leom has quit IRC23:46
*** Leo_ has joined #openstack-meeting23:46
*** radek_ has joined #openstack-meeting23:46
*** ivc_ has joined #openstack-meeting23:48
*** hoangcx2 has joined #openstack-meeting23:51
*** roxanaghe has quit IRC23:52
*** hoangcx has quit IRC23:53
*** esberglu has joined #openstack-meeting23:53
*** shaohe_feng has quit IRC23:54
*** liuhanxi has joined #openstack-meeting23:54
*** shaohe_feng has joined #openstack-meeting23:54
*** dprince has joined #openstack-meeting23:56

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