Tuesday, 2016-08-09

*** kylek3h has joined #openstack-meeting00:02
*** shaohe_feng has quit IRC00:05
*** shaohe_feng has joined #openstack-meeting00:05
*** Julien-zte has joined #openstack-meeting00:08
*** Swami has quit IRC00:09
*** myoung has quit IRC00:10
*** markvoelker has joined #openstack-meeting00:11
*** vishnoianil has joined #openstack-meeting00:11
*** amitgandhinz has joined #openstack-meeting00:11
*** Leom has quit IRC00:14
*** shaohe_feng has quit IRC00:15
*** amitgandhinz has quit IRC00:16
*** shaohe_feng has joined #openstack-meeting00:16
*** sarob has joined #openstack-meeting00:19
*** sarob has quit IRC00:23
*** shaohe_feng has quit IRC00:26
*** shaohe_feng has joined #openstack-meeting00:26
*** pvaneck has quit IRC00:27
*** guoshan has joined #openstack-meeting00:28
*** banix has quit IRC00:32
*** yassou has quit IRC00:35
*** shaohe_feng has quit IRC00:36
*** shaohe_feng has joined #openstack-meeting00:37
*** abhiraut has quit IRC00:39
*** synegy34 has joined #openstack-meeting00:40
*** tonytan4ever has quit IRC00:41
*** abhiraut has joined #openstack-meeting00:41
*** toddjohn has joined #openstack-meeting00:42
*** abhiraut has left #openstack-meeting00:42
*** gatekeep has quit IRC00:43
*** shaohe_feng has quit IRC00:46
*** shaohe_feng has joined #openstack-meeting00:46
*** hieulq_ has joined #openstack-meeting00:47
*** gyee has quit IRC00:48
*** enriquetaso has quit IRC00:48
*** mtanino has joined #openstack-meeting00:54
*** banix has joined #openstack-meeting00:54
*** hoangcx has quit IRC00:54
*** hoangcx has joined #openstack-meeting00:55
*** shaohe_feng has quit IRC00:56
*** Sukhdev has quit IRC00:57
*** shaohe_feng has joined #openstack-meeting00:57
*** thorst has quit IRC01:02
*** thorst has joined #openstack-meeting01:03
*** maeca1 has joined #openstack-meeting01:03
*** cdelatte has quit IRC01:04
*** shaohe_feng has quit IRC01:07
*** shaohe_feng has joined #openstack-meeting01:07
*** guoshan has quit IRC01:08
*** hoangcx has quit IRC01:09
*** hoangcx has joined #openstack-meeting01:10
*** sarob has joined #openstack-meeting01:10
*** dmacpher has joined #openstack-meeting01:11
*** karthikp_ has quit IRC01:12
*** thorst has quit IRC01:12
*** amitgandhinz has joined #openstack-meeting01:12
*** karthikp_ has joined #openstack-meeting01:12
*** bobh has joined #openstack-meeting01:14
*** sarob has quit IRC01:15
*** liuhanxi has quit IRC01:16
*** shaohe_feng has quit IRC01:17
*** jimholl_ has quit IRC01:17
*** zhurong has joined #openstack-meeting01:18
*** amitgandhinz has quit IRC01:18
*** shaohe_feng has joined #openstack-meeting01:18
*** piet has quit IRC01:22
*** beekhof_mb has quit IRC01:22
*** dimtruck is now known as zz_dimtruck01:22
*** Apoorva_ has joined #openstack-meeting01:22
*** sindhu has joined #openstack-meeting01:22
*** guoshan has joined #openstack-meeting01:23
*** rfolco has quit IRC01:24
*** hieulq_ has quit IRC01:25
*** Apoorva has quit IRC01:26
*** b1airo has quit IRC01:26
*** b1airo has joined #openstack-meeting01:26
*** hoangcx has quit IRC01:26
*** sdake has quit IRC01:27
*** Apoorva_ has quit IRC01:27
*** beekhof_mb has joined #openstack-meeting01:27
*** shaohe_feng has quit IRC01:27
*** hoangcx has joined #openstack-meeting01:27
*** shaohe_feng has joined #openstack-meeting01:28
*** sdake has joined #openstack-meeting01:29
*** yifei has joined #openstack-meeting01:29
*** toddjohn has quit IRC01:29
*** karthikp_ has quit IRC01:31
*** b1airo has quit IRC01:32
*** b1airo has joined #openstack-meeting01:32
*** dslevin has quit IRC01:33
*** unicell has quit IRC01:35
*** jrist has quit IRC01:36
*** dslevin has joined #openstack-meeting01:36
*** hongbin_ has joined #openstack-meeting01:36
*** shaohe_feng has quit IRC01:37
*** shaohe_feng has joined #openstack-meeting01:38
*** banix has quit IRC01:38
*** ebalduf has quit IRC01:39
*** tonytan4ever has joined #openstack-meeting01:42
*** kylek3h has quit IRC01:42
*** sarob has joined #openstack-meeting01:43
*** amitkqed has quit IRC01:43
*** amitkqed has joined #openstack-meeting01:43
*** jimholl_ has joined #openstack-meeting01:43
*** jamespd_ has quit IRC01:43
*** liuhanxi has joined #openstack-meeting01:45
*** fnaval has joined #openstack-meeting01:45
*** tonytan4ever has quit IRC01:47
*** sarob has quit IRC01:48
*** shaohe_feng has quit IRC01:48
*** shaohe_feng has joined #openstack-meeting01:48
*** jrist has joined #openstack-meeting01:50
*** jrist has joined #openstack-meeting01:50
*** ivc_ has quit IRC01:51
*** liuhanxi has quit IRC01:52
*** liuhanxi has joined #openstack-meeting01:53
*** s3wong has quit IRC01:53
*** baoli has joined #openstack-meeting01:58
*** shaohe_feng has quit IRC01:58
*** shaohe_feng has joined #openstack-meeting01:58
*** reed_ has joined #openstack-meeting02:00
*** zz_dimtruck is now known as dimtruck02:00
*** reed_ has quit IRC02:01
*** yamahata has quit IRC02:02
*** sarob has joined #openstack-meeting02:05
*** esberglu has joined #openstack-meeting02:07
*** yamahata has joined #openstack-meeting02:08
*** shaohe_feng has quit IRC02:08
*** sarob has quit IRC02:09
*** shaohe_feng has joined #openstack-meeting02:09
*** woodster_ has quit IRC02:09
*** hoangcx has quit IRC02:12
*** iyamahat has quit IRC02:14
*** jrist has quit IRC02:14
*** amitgandhinz has joined #openstack-meeting02:14
*** toscalix has quit IRC02:17
*** shaohe_feng has quit IRC02:18
*** amitgandhinz has quit IRC02:19
*** coolsvap has joined #openstack-meeting02:19
*** maeca1 has quit IRC02:25
*** shaohe_feng has joined #openstack-meeting02:26
*** jrist has joined #openstack-meeting02:26
*** sindhu has quit IRC02:27
*** jamespd has joined #openstack-meeting02:27
*** shaohe_feng has quit IRC02:29
*** Wenzhi__ has quit IRC02:29
*** Wenzhi has joined #openstack-meeting02:29
*** shaohe_feng has joined #openstack-meeting02:30
*** zhurong_ has joined #openstack-meeting02:31
*** mkrai has joined #openstack-meeting02:35
*** zhurong has quit IRC02:35
*** sindhu has joined #openstack-meeting02:36
*** Benj_ has quit IRC02:37
*** shaohe_feng has quit IRC02:39
*** shaohe_feng has joined #openstack-meeting02:40
*** b1airo has quit IRC02:41
*** baoli has quit IRC02:43
*** bobh has quit IRC02:43
*** piet has joined #openstack-meeting02:47
*** fnaval_ has joined #openstack-meeting02:47
*** itzdilip has joined #openstack-meeting02:48
*** vikasc has joined #openstack-meeting02:49
*** shaohe_feng has quit IRC02:49
*** shaohe_feng has joined #openstack-meeting02:50
*** fnaval has quit IRC02:50
*** fnaval has joined #openstack-meeting02:51
*** dixiaoli has joined #openstack-meeting02:52
*** esberglu has quit IRC02:52
*** ebalduf has joined #openstack-meeting02:53
*** fnaval_ has quit IRC02:55
*** jckasper has joined #openstack-meeting02:56
*** yanyanhu has joined #openstack-meeting02:57
*** Namrata has joined #openstack-meeting02:57
*** gongysh has joined #openstack-meeting02:58
*** coolsvap is now known as coolsvap_02:59
*** shaohe_feng has quit IRC02:59
*** shubhams has joined #openstack-meeting03:00
hongbin_#startmeeting zun03:00
openstackMeeting started Tue Aug  9 03:00:09 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-09_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
*** julim has quit IRC03:00
yanyanhuhi, yanyan is here03:00
*** flwang has joined #openstack-meeting03:01
*** shaohe_feng has joined #openstack-meeting03:01
*** armax has quit IRC03:01
hongbin_Thanks for joining the meeting Namrata shubhams mkrai Wenzhi yanyanhu itzdilip vikasc flwang03:01
hongbin_#topic Announcements03:01
*** openstack changes topic to "Announcements (Meeting topic: zun)"03:01
hongbin_I have no announcement, anyone has?03:01
*** oferby has quit IRC03:01
hongbin_#topic Review Action Items03:01
*** openstack changes topic to "Review Action Items (Meeting topic: zun)"03:01
*** oferby has joined #openstack-meeting03:02
hongbin_#topic Runtimes API design (mkrai)03:02
*** openstack changes topic to "Runtimes API design (mkrai) (Meeting topic: zun)"03:02
hongbin_mkrai: ^^03:02
*** roxanaghe has joined #openstack-meeting03:02
mkraiI have tested the api patch and it is working for all apis except for container-show command03:02
mkraiI have uploaded the patch in zunclient for all container related command03:03
mkrai#link https://review.openstack.org/#/c/352357/03:03
*** janki has joined #openstack-meeting03:03
mkraiEveryone please review the patch03:04
hongbin_What is wrong with the show command though?03:04
mkraiThe container controller patch needs a revision which I will do after meeting03:04
mkraihongbin_, Issue is with response being an object03:04
mkraiIt should not be a difficult issue03:05
mkraiI will fix it today03:05
hongbin_sounds good03:05
mkraiRest of the commands are working fine :)03:05
mkraiPlease feel free to test the APIs and post your comments03:05
mkraihongbin_, I have also updated your compute patch03:06
hongbin_mkrai: Yes, I saw that. It looks good03:06
mkraiYes it is working now03:06
mkraiThat's all from my side03:07
hongbin_Thanks mkrai .03:07
*** epico has joined #openstack-meeting03:07
hongbin_Any question about the runtime API?03:07
hongbin_#topic Nova integration (Namrata)03:08
*** openstack changes topic to "Nova integration (Namrata) (Meeting topic: zun)"03:08
hongbin_#link https://blueprints.launchpad.net/zun/+spec/nova-integration The BP03:08
hongbin_#link https://etherpad.openstack.org/p/zun-containers-nova-integration The etherpad03:08
hongbin_Namrata: ^^03:08
NamrataI am working on the specs of nova integration03:08
Namrataand will submit it by this week03:08
*** larainema has quit IRC03:09
mkraiNamrata, let us know if you need any help on that03:09
Namratayeah sure03:09
NamrataThanks mkrai03:09
*** shaohe_feng has quit IRC03:10
hongbin_Namrata: Could you tell us your general thoughs about the design?03:10
NamrataI will include both the implementation details which we discussed in last meeting03:11
*** shaohe_feng has joined #openstack-meeting03:11
*** sudipto has joined #openstack-meeting03:11
NamrataAnd as of now we don't of scheduler so we will consider Nova's scheduler only03:11
NamrataAnd the driver will work same as ironic driver03:11
hongbin_I remembered we discussed two approach at the last meeting03:12
hongbin_1. Ironic approach (use nova shceduler)03:12
NamrataYeah i will write both the implemenatations in the spec03:12
hongbin_2. VMWare approach (disable nova scheduler)03:13
hongbin_En, ok03:13
*** sudipto_ has joined #openstack-meeting03:13
mkraihongbin_, Is there a way to disable scheduler?03:13
hongbin_mkrai: Just use Nova as a proxy03:13
*** sudipto has quit IRC03:14
hongbin_Nova -> ZUn API -> Zun scheduler -> Zun compute03:14
mkraiOk got it03:14
hongbin_Like this: http://docs.openstack.org/kilo/config-reference/content/vmware.html03:14
yanyanhuhongbin_, actually nova scheduler still takes effect. Just the scheduling happens cross multiple vcenters03:15
*** vinayp has joined #openstack-meeting03:15
hongbin_yanyanhu: Then, it sounds like a two level scheduling03:15
yanyanhuhongbin_, yes, basically, the 'real' scheduling is done inside vcenter/zun03:15
*** amitgandhinz has joined #openstack-meeting03:15
yanyanhuif we only have one zun/vcenter instance there03:15
mkraiyes scheduler is tightly coupled so it can't be disabled I guess03:16
yanyanhuso, what you stated is right03:16
yanyanhumkrai, using the second way, the will be only one available host for nova scheduler to choose actually :)03:16
yanyanhus/host/nova-compute node03:17
yanyanhuthe compute-node is actually zun service03:17
mkraiyanyanhu, How?03:17
*** liuhanxi has quit IRC03:17
*** iyamahat has joined #openstack-meeting03:17
yanyanhuin that case, Zun will be a nova-compute node for Nova03:17
yanyanhuthere is no real scheduling happen at nova side I feel03:18
Wenzhiyes just like ironic03:18
yanyanhuif we choose another way, nova will be responsible to schedule instance03:19
*** amitgandhinz has quit IRC03:19
hongbin_I think the first appraoch is more scalable: Nova choose a cluster, Zun pick a node in the cluster03:20
*** shaohe_feng has quit IRC03:20
yanyanhujust my understanding, maybe not accurate03:20
*** shaohe_feng has joined #openstack-meeting03:20
yanyanhuhongbin_, what you mean here by cluster?03:20
*** yamahata has quit IRC03:21
hongbin_Like VMWare, Nova pick a cluster, vcenter pick a host03:21
yanyanhuI see03:21
hongbin_Oh, I might misunderstand something03:21
yanyanhuso two level scheduling03:21
hongbin_OK, let's discuss the detail in the spec Namrata will write03:22
hongbin_Thanks Namrata for working on this03:22
hongbin_#topic Integrate with Mesos scheduler (sudipto)03:23
*** openstack changes topic to "Integrate with Mesos scheduler (sudipto) (Meeting topic: zun)"03:23
hongbin_sudipto_: here?03:23
*** acoles_ is now known as acoles03:23
*** ijw has quit IRC03:23
hongbin_It looks sudipto is not here. Anyone else want to discuss this topic?03:24
*** itzdilip is now known as dsunkum03:24
*** piet has quit IRC03:24
hongbin_OK. Then, let's start the open discussion03:24
hongbin_#topic Open Discussion03:24
*** openstack changes topic to "Open Discussion (Meeting topic: zun)"03:24
hongbin_I have one topic to discuss, if nobody else has anyting03:25
mkraihongbin_, After we have the basic docker API support, what shall we work on?03:25
yanyanhusure, go ahead plz03:25
hongbin_mkrai: There are several priority03:25
mkraiWe should decide on some features03:25
hongbin_mkrai: image, network, storage03:25
* sudipto_ is eavesdropping 03:26
hongbin_mkrai: Do you have any feature in mind?03:26
hongbin_sudipto_: hey03:26
mkraiSo I think we should add few of these topics in next meeting03:26
sudipto_sorry i am out for a customer visit... so couldn't join in time.03:26
*** acoles is now known as acoles_03:26
mkraiI also feel image, storage and networking are priority03:27
hongbin_mkrai: sure, will start exploring additional topics next time03:27
hongbin_sudipto_: NP at all03:27
*** iyamahat has quit IRC03:27
*** hongbin_ has quit IRC03:27
mkraiLet's enhance the docker support first03:27
*** ijw has joined #openstack-meeting03:27
*** hongbin has joined #openstack-meeting03:28
mkraiThanks hongbin03:28
hongbinNot sure why my name changed03:28
hongbinOK. Let's continue03:28
sudipto_yeah my view is the same, the mesos updates can wait till we finalise the docker support...03:28
hongbinsudipto_: ack03:29
hongbinFor the next priority, I remembered we have an etherpad to list them03:29
* hongbin is finding the etherpad03:29
*** hurricanerix has quit IRC03:30
hongbin#link https://etherpad.openstack.org/p/container-management-service03:30
*** shaohe_feng has quit IRC03:30
*** larainema has joined #openstack-meeting03:30
hongbinSeveral things in the list03:31
hongbin1. Implement a simple scheduler03:31
*** shaohe_feng has joined #openstack-meeting03:31
hongbin2. Neutron integration03:31
mkraiyes let's list it somewhere so  that contributors can take it03:32
hongbin3. Cinder integration03:32
hongbinmkrai: sure. First, we needs to decide which one is the priority first03:32
hongbin4. Glance integration03:32
*** ijw has quit IRC03:32
hongbinmkrai: Do we have a Keystone integration ready?03:33
vikascneutron intergration should be easiest one03:33
*** merooney has quit IRC03:33
vikascsince kuryr already supports libnetwork03:33
hongbinvikasc: hopefully, it is easy03:34
*** csomerville has quit IRC03:34
*** csomerville has joined #openstack-meeting03:34
vikascand kuryr currently supports baremetal only03:34
hongbinmkrai: How about multi-tenancy?03:34
mkraihongbin, No it is not yet supported03:35
hongbinmkrai: ack. I think multi-tenancy is very important03:35
mkraiWe need to look into it03:35
mkraiYes agree03:35
hongbin#action hongbin created a BP for multi-tenancy support03:35
hongbinAnything else?03:36
hongbin5. Host management03:36
hongbin6. Magnum integration03:36
yanyanhualso Composition maybe03:37
yanyanhubut not urgent03:37
hongbinyanyanhu: ack03:37
mkraiShall we pick some priority topics to be included in next meeting?03:37
hongbinmkrai: if you want, yes03:37
mkraiI think multi tenancy and glance integration is priority I feel03:38
sudipto_mkrai, totally agreed. I think we have to narrow our focus to get something working first.03:38
hongbinsudipto_: mkrai get the basic of runtime API working already03:38
sudipto_hongbin, oh great. I wasn't aware.03:39
yanyanhu+1 as well for glance integration and multi-tenancy support03:39
sudipto_Maybe i could do some code reviews - if you guys add me?03:39
mkraisure sudipto_ I will add you03:39
hongbinsudipto_: as core reviewer?03:39
sudipto_hongbin, well i didn't ask for that :) A basic reviewer would do too.03:40
hongbinsudipto_: a basic review don't need to be added :)03:40
*** shaohe_feng has quit IRC03:40
hongbinHowever, I can propose you to be a core03:40
mkrai+1 for it hongbin :)03:41
sudipto_hongbin, alright sounds good!03:41
yanyanhu+1 from me03:41
hongbinsudipto_: will propose you later03:41
sudipto_hongbin, ok thanks!03:41
hongbinanyone else want to become a core. Please contact me as well03:41
*** shaohe_feng has joined #openstack-meeting03:41
hongbinOK. Back to the Glance integration.03:42
hongbinWe have about 17 minutes left, want to discuss Glance integration now?03:42
*** myoung has joined #openstack-meeting03:42
mkraiI see glance integration is taken by Fei long03:42
hongbinflwang: ^^03:43
sudipto_flwang, are you there?03:43
hongbinI am not sure if you guys know. Glare has been splitted out from Glance03:43
*** ijw has joined #openstack-meeting03:43
sudipto_I am not really sure where glance is going.03:43
sudipto_with Glare and all that.03:44
yanyanhuyes, long thread in mailing list :)03:44
yanyanhusome discussion (argument as well :P )03:44
hongbinYes, it is a long debate03:44
hongbinGlare's API is suitable to implement layers of docker images03:45
hongbinBasically, Glare is like a superset of Glance03:46
yanyanhuoh, I thought it is for template storing before03:46
hongbinyanyanhu: It seems it is not. It is a model to represent the image and its meta-data03:46
yanyanhuI see03:46
yanyanhuso basically add versioning support03:47
hongbinWhat we needs is the ability to express dependencies between image layers03:47
*** bobh has joined #openstack-meeting03:47
hongbinwhich Glare can do03:47
sudipto_so you want to detach yourself from the docker hub and create a private registry of sorts?03:48
*** ijw has quit IRC03:48
hongbinsudipto_: Yes, that is an alternative03:48
hongbinflwang: hey03:49
hongbinflwang: I guess you saw the news that Glare was splited out?03:49
flwangyep i know03:49
hongbinflwang: Then, what the Glare API will look like, a superset of Glance API?03:49
flwangand as the discussion with nikhil, implement the layer in glance is most like 'impossible'03:49
flwanghongbin: it's an artifacts repo03:50
flwangnot a superset of glance api03:50
hongbinflwang: I see03:50
*** fnaval_ has joined #openstack-meeting03:50
*** shaohe_feng has quit IRC03:51
flwangin other words, or IMHO, it's most like a definition for an OS/image03:51
*** dsunkum has quit IRC03:51
*** shaohe_feng has joined #openstack-meeting03:51
flwangit can define very detailed attributes of an image03:51
hongbinflwang: but the image blob data must store somewhere?03:51
sudipto_till glance and glare sorts out stuff, should we just go with a private registry?03:52
*** itzdilip has joined #openstack-meeting03:52
flwangi would say the image data is still in glance03:52
flwangsudipto_: that's a reasonable option03:52
flwangsince i can see it will still last very long time to settle down03:53
sudipto_flwang, same feelings.03:53
hongbinThe weakness of docker registry is the multi-tenancy support03:53
hongbinand keystone03:53
*** fnaval has quit IRC03:53
flwanghongbin: right03:54
hongbinIt looks docker registry is single tenant, that means we need to setup one registry per tenant03:54
hongbinor modify the docker registry to make it compatible with multi-tennacy model03:54
flwanghongbin: and it's hard to maintain i think03:54
hongbinflwang: I might have a crazy idea. Have Glance backed by docker registry03:55
hongbinso that we use Glance API at front, use docker registry as a backend03:56
flwanghongbin: that's the initial plan I discussed with Sam03:56
flwangyears ago03:56
flwangbut i can't remember the details now :(03:56
hongbinsounds like the idea was rejected03:56
flwangbecause even if you can work out docker registry as a glance backend, you still have to make glance respect the layers03:58
hongbinflwang: maybe not03:58
*** fnaval has joined #openstack-meeting03:58
sudipto_how about an offline mailing list discussion on this? maybe not to the whole community but with a few of us in it?03:58
flwangok, sure03:58
sudipto_coz we are on the brink of the hour.03:58
flwanglet's back to zun channel03:58
hongbinAll, thanks for joining the meeting03:59
*** hongbin_ has joined #openstack-meeting03:59
mkraiMeetbot isn't working?03:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"04:00
openstackMeeting ended Tue Aug  9 04:00:00 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-08-09-03.00.html04:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-08-09-03.00.txt04:00
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-08-09-03.00.log.html04:00
*** sudipto_ has quit IRC04:01
*** shaohe_feng has quit IRC04:01
*** hongbin has quit IRC04:01
*** janki has quit IRC04:01
*** fnaval_ has quit IRC04:01
*** shaohe_feng has joined #openstack-meeting04:02
*** jamespage has quit IRC04:02
*** b1airo has joined #openstack-meeting04:02
*** hongbin_ has quit IRC04:03
*** bobh has quit IRC04:03
*** guoshan has quit IRC04:06
*** vinayp__ has joined #openstack-meeting04:09
*** unicell has joined #openstack-meeting04:09
*** vinayp__ has quit IRC04:10
*** shaohe_feng has quit IRC04:11
*** links has joined #openstack-meeting04:11
*** mkrai has quit IRC04:12
*** shaohe_feng has joined #openstack-meeting04:12
*** numans has joined #openstack-meeting04:13
*** vinayp has left #openstack-meeting04:14
*** amitgandhinz has joined #openstack-meeting04:16
*** iyamahat has joined #openstack-meeting04:18
*** amitgandhinz has quit IRC04:20
*** Na3iL has quit IRC04:20
*** shaohe_feng has quit IRC04:21
*** shaohe_feng has joined #openstack-meeting04:22
*** 16WAAYRKN has joined #openstack-meeting04:22
*** unicell has quit IRC04:24
*** mkrai has joined #openstack-meeting04:28
*** yamahata has joined #openstack-meeting04:29
*** unicell has joined #openstack-meeting04:29
*** shaohe_feng has quit IRC04:32
*** shaohe_feng has joined #openstack-meeting04:32
*** rossella_s has quit IRC04:38
*** rossella_s has joined #openstack-meeting04:38
*** Namrata has quit IRC04:40
*** shaohe_feng has quit IRC04:42
*** shaohe_feng has joined #openstack-meeting04:43
*** trozet has quit IRC04:45
*** trozet has joined #openstack-meeting04:45
*** yanyanhu has left #openstack-meeting04:48
*** guoshan has joined #openstack-meeting04:49
*** 16WAAYRKN has quit IRC04:49
*** khushbu_ has joined #openstack-meeting04:49
*** coolsvap_ is now known as coolsvap04:51
*** shaohe_feng has quit IRC04:52
*** shaohe_feng has joined #openstack-meeting04:52
*** guoshan has quit IRC04:55
*** Poornima has joined #openstack-meeting04:57
*** _nadya_ has joined #openstack-meeting04:58
*** jckasper has quit IRC04:58
*** jckasper has joined #openstack-meeting04:59
*** mtanino has quit IRC05:01
*** r-mibu has joined #openstack-meeting05:02
*** shaohe_feng has quit IRC05:02
*** moizarif has joined #openstack-meeting05:02
*** jckasper has quit IRC05:03
*** shaohe_feng has joined #openstack-meeting05:03
*** sudipto_ has joined #openstack-meeting05:05
*** liusheng has quit IRC05:05
*** moizarif_ has quit IRC05:06
*** shubhams has left #openstack-meeting05:06
*** liusheng has joined #openstack-meeting05:07
*** david-lyle_ has joined #openstack-meeting05:11
*** shaohe_feng has quit IRC05:13
*** david-lyle has quit IRC05:13
*** shaohe_feng has joined #openstack-meeting05:13
*** AmitGalitz has joined #openstack-meeting05:14
*** amitgandhinz has joined #openstack-meeting05:17
*** roxanaghe has quit IRC05:17
*** khushbu_ has quit IRC05:20
*** rcernin has joined #openstack-meeting05:21
*** amitgandhinz has quit IRC05:21
*** shaohe_feng has quit IRC05:23
*** shaohe_feng has joined #openstack-meeting05:23
*** khushbu has joined #openstack-meeting05:24
*** sdake has quit IRC05:26
*** jtomasek_ has joined #openstack-meeting05:26
*** jtomasek has quit IRC05:26
*** sdake has joined #openstack-meeting05:29
*** lpetrut has joined #openstack-meeting05:31
*** shaohe_feng has quit IRC05:33
*** shaohe_feng has joined #openstack-meeting05:34
*** comay has quit IRC05:34
*** unicell has quit IRC05:35
*** unicell1 has joined #openstack-meeting05:35
*** jtomasek_ is now known as jtomasek05:37
*** _nadya_ has quit IRC05:38
*** comay has joined #openstack-meeting05:40
*** janki has joined #openstack-meeting05:42
*** guoshan has joined #openstack-meeting05:43
*** shaohe_feng has quit IRC05:43
*** trozet has quit IRC05:44
*** shaohe_feng has joined #openstack-meeting05:44
*** sridharg has joined #openstack-meeting05:47
*** guoshan has quit IRC05:48
*** sindhu has quit IRC05:49
*** andymaier has joined #openstack-meeting05:51
*** andymaier has quit IRC05:52
*** shaohe_feng has quit IRC05:54
*** shaohe_feng has joined #openstack-meeting05:54
*** nkrinner_afk is now known as nkrinner06:01
*** zhangguoqing has joined #openstack-meeting06:04
*** shaohe_feng has quit IRC06:04
*** shaohe_feng has joined #openstack-meeting06:04
*** Ravikiran_K has joined #openstack-meeting06:05
*** saju_m has joined #openstack-meeting06:05
*** roxanaghe has joined #openstack-meeting06:08
*** jprovazn has joined #openstack-meeting06:10
*** anilvenkata has joined #openstack-meeting06:10
*** kaminohana has quit IRC06:10
*** ebalduf has quit IRC06:12
*** roxanaghe has quit IRC06:13
*** shaohe_feng has quit IRC06:14
*** shaohe_feng has joined #openstack-meeting06:15
*** amitgandhinz has joined #openstack-meeting06:17
*** guoshan has joined #openstack-meeting06:19
*** akuznetsov has joined #openstack-meeting06:20
*** unicell has joined #openstack-meeting06:21
*** unicell1 has quit IRC06:21
*** amitgandhinz has quit IRC06:22
*** saju_m has quit IRC06:23
*** shaohe_feng has quit IRC06:24
*** radeks has joined #openstack-meeting06:24
*** scottda has quit IRC06:25
*** sweston has quit IRC06:26
*** scottda has joined #openstack-meeting06:26
*** sweston has joined #openstack-meeting06:26
*** yuval has joined #openstack-meeting06:26
*** shaohe_feng has joined #openstack-meeting06:27
*** ihrachys has joined #openstack-meeting06:27
*** ttx has quit IRC06:27
*** ttx has joined #openstack-meeting06:28
*** Poornima has quit IRC06:29
*** iyamahat has quit IRC06:31
*** adiantum has quit IRC06:33
*** shaohe_feng has quit IRC06:35
*** shaohe_feng has joined #openstack-meeting06:35
*** lpetrut has quit IRC06:36
*** saju_m has joined #openstack-meeting06:37
*** sdake has quit IRC06:38
*** pcaruana has joined #openstack-meeting06:39
*** ihrachys has quit IRC06:39
*** _nadya_ has joined #openstack-meeting06:41
*** jckasper has joined #openstack-meeting06:42
*** Poornima has joined #openstack-meeting06:44
*** tesseract- has joined #openstack-meeting06:45
*** shaohe_feng has quit IRC06:45
*** shaohe_feng has joined #openstack-meeting06:45
*** mickeys has joined #openstack-meeting06:45
*** lpetrut has joined #openstack-meeting06:47
*** jckasper has quit IRC06:47
*** mickeys has quit IRC06:50
*** coolsvap is now known as coolsvap_06:51
*** nkrinner is now known as nkrinner_afk06:52
*** JRobinson__ has quit IRC06:54
*** shaohe_feng has quit IRC06:55
*** shaohe_feng has joined #openstack-meeting06:55
*** rbartal has joined #openstack-meeting06:57
*** ihrachys has joined #openstack-meeting06:57
yamamoto#startmeeting networking_midonet07:00
openstackMeeting started Tue Aug  9 07:00:35 2016 UTC and is due to finish in 60 minutes.  The chair is yamamoto. Information about MeetBot at http://wiki.debian.org/MeetBot.07:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:00
*** openstack changes topic to " (Meeting topic: networking_midonet)"07:00
openstackThe meeting name has been set to 'networking_midonet'07:00
*** belmoreira has joined #openstack-meeting07:01
*** mkrai has left #openstack-meeting07:01
yamamoto#topic Agenda07:04
*** openstack changes topic to "Agenda (Meeting topic: networking_midonet)"07:04
yamamoto#link https://wiki.openstack.org/wiki/Meetings/NetworkingMidoNet07:04
yamamotonot much agenda07:04
yamamoto#topic Announcements07:04
*** openstack changes topic to "Announcements (Meeting topic: networking_midonet)"07:04
yamamotonothing from me07:05
yamamoto#topic Bugs07:05
*** openstack changes topic to "Bugs (Meeting topic: networking_midonet)"07:05
*** shaohe_feng has quit IRC07:05
yamamotowe had gate blocking issues recently but most of them have been solved07:06
yamamoto#topic Open Discussion07:06
*** openstack changes topic to "Open Discussion (Meeting topic: networking_midonet)"07:06
*** shaohe_feng has joined #openstack-meeting07:06
* yamamoto waiting for a while before closing the meeting07:06
*** lpetrut has quit IRC07:07
*** manikanta_tadi has joined #openstack-meeting07:11
*** dimtruck is now known as zz_dimtruck07:11
*** tung_doan has joined #openstack-meeting07:13
*** tung_doan has quit IRC07:14
*** shaohe_feng has quit IRC07:16
*** shaohe_feng has joined #openstack-meeting07:16
*** amitgandhinz has joined #openstack-meeting07:18
yamamotothank you!07:20
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"07:20
openstackMeeting ended Tue Aug  9 07:20:42 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:20
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_midonet/2016/networking_midonet.2016-08-09-07.00.html07:20
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_midonet/2016/networking_midonet.2016-08-09-07.00.txt07:20
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_midonet/2016/networking_midonet.2016-08-09-07.00.log.html07:20
*** jlanoux has joined #openstack-meeting07:21
*** nmagnezi has joined #openstack-meeting07:22
*** amitgandhinz has quit IRC07:23
*** jlanoux has quit IRC07:24
*** jlanoux has joined #openstack-meeting07:24
*** saju_m has quit IRC07:25
*** vishnoianil has quit IRC07:25
*** dkehn_ has quit IRC07:25
*** shaohe_feng has quit IRC07:26
*** ddeja has left #openstack-meeting07:26
*** shaohe_feng has joined #openstack-meeting07:27
*** elo has quit IRC07:31
*** sshnaidm|afk has quit IRC07:32
*** yamamoto has quit IRC07:33
*** shaohe_feng has quit IRC07:36
*** shaohe_feng has joined #openstack-meeting07:37
*** vishnoianil has joined #openstack-meeting07:37
*** dkehn_ has joined #openstack-meeting07:38
*** khushbu has quit IRC07:40
*** mikelk has joined #openstack-meeting07:40
*** david-lyle has joined #openstack-meeting07:43
*** david-lyle_ has quit IRC07:46
*** bvandenh has quit IRC07:46
*** shaohe_feng has quit IRC07:46
*** matthewbodkin has joined #openstack-meeting07:46
*** shaohe_feng has joined #openstack-meeting07:47
*** anilvenkata is now known as anilvenkata_afk07:51
*** sdake has joined #openstack-meeting07:51
*** matrohon has joined #openstack-meeting07:51
*** matrohon has quit IRC07:51
*** jckasper has joined #openstack-meeting07:54
*** shaohe_feng has quit IRC07:57
*** coolsvap_ is now known as coolsvap07:58
*** jckasper has quit IRC07:58
*** markvoelker has quit IRC07:59
*** shaohe_feng has joined #openstack-meeting08:00
*** yamahata has quit IRC08:00
*** jamespag` has joined #openstack-meeting08:02
*** khushbu has joined #openstack-meeting08:03
*** jamespag` is now known as jamespage08:03
*** e0ne has joined #openstack-meeting08:03
*** radeks has quit IRC08:04
*** sdake has quit IRC08:06
*** dmacpher has quit IRC08:06
*** lpetrut has joined #openstack-meeting08:07
*** shaohe_feng has quit IRC08:07
*** shaohe_feng has joined #openstack-meeting08:08
*** matrohon has joined #openstack-meeting08:08
*** pece has joined #openstack-meeting08:08
*** pnavarro has joined #openstack-meeting08:09
*** liuhanxi has joined #openstack-meeting08:10
*** sshnaidm|afk has joined #openstack-meeting08:11
*** sshnaidm|afk is now known as sshnaidm08:11
*** akuznetsov has quit IRC08:13
*** manikanta_tadi has quit IRC08:15
*** shaohe_feng has quit IRC08:17
*** shaohe_feng has joined #openstack-meeting08:18
*** amitgandhinz has joined #openstack-meeting08:19
*** amitgandhinz has quit IRC08:23
*** khushbu has quit IRC08:24
*** saju_m has joined #openstack-meeting08:26
*** shaohe_feng has quit IRC08:27
*** zhhuabj_ has joined #openstack-meeting08:27
*** anilvenkata_afk is now known as anilvenkata08:28
*** shaohe_feng has joined #openstack-meeting08:28
*** zhhuabj has quit IRC08:29
*** yassine has joined #openstack-meeting08:31
*** yassine is now known as Guest7369708:32
*** vikasc has quit IRC08:33
*** zhhuabj_ has quit IRC08:34
*** fnaval_ has joined #openstack-meeting08:35
*** yamamoto has joined #openstack-meeting08:35
*** fnaval has quit IRC08:37
*** mickeys has joined #openstack-meeting08:37
*** shaohe_feng has quit IRC08:38
*** rossella_s has quit IRC08:38
*** rossella_s has joined #openstack-meeting08:38
*** shaohe_feng has joined #openstack-meeting08:39
*** myoung is now known as myoung|afk08:40
*** yamamoto has quit IRC08:41
*** yamamoto has joined #openstack-meeting08:42
*** acoles_ is now known as acoles08:43
*** mickeys has quit IRC08:44
*** mickeys has joined #openstack-meeting08:44
*** matrohon has quit IRC08:45
*** adiantum has joined #openstack-meeting08:46
*** shaohe_feng has quit IRC08:48
*** mickeys has quit IRC08:48
*** shaohe_feng has joined #openstack-meeting08:49
*** zhhuabj_ has joined #openstack-meeting08:50
*** yamamoto has quit IRC08:52
*** yamamoto has joined #openstack-meeting08:52
*** yamamoto has quit IRC08:52
*** yamamoto has joined #openstack-meeting08:53
*** xiangxinyong has joined #openstack-meeting08:55
*** yamamoto has quit IRC08:57
*** shaohe_feng has quit IRC08:58
*** shaohe_feng has joined #openstack-meeting08:59
*** markvoelker has joined #openstack-meeting09:00
*** roxanaghe has joined #openstack-meeting09:00
*** yamamoto has joined #openstack-meeting09:01
*** fawadkhaliq has joined #openstack-meeting09:01
*** fawadkhaliq has quit IRC09:01
*** matrohon has joined #openstack-meeting09:01
*** zhonghua-lee has joined #openstack-meeting09:02
*** zz_dimtruck is now known as dimtruck09:02
*** markvoelker has quit IRC09:05
*** roxanaghe has quit IRC09:06
*** electrofelix has joined #openstack-meeting09:08
*** shaohe_feng has quit IRC09:08
*** coolsvap is now known as coolsvap_09:09
*** shaohe_feng has joined #openstack-meeting09:09
*** dimtruck is now known as zz_dimtruck09:16
*** shaohe_feng has quit IRC09:19
*** amitgandhinz has joined #openstack-meeting09:20
*** bvandenh has joined #openstack-meeting09:20
*** jckasper has joined #openstack-meeting09:20
*** matrohon has quit IRC09:20
*** shaohe_feng has joined #openstack-meeting09:22
*** amitgandhinz has quit IRC09:24
*** jckasper has quit IRC09:25
*** zhhuabj_ has quit IRC09:27
*** shaohe_feng has quit IRC09:29
*** gongysh has quit IRC09:30
*** shaohe_feng has joined #openstack-meeting09:30
*** matrohon has joined #openstack-meeting09:36
*** dixiaoli has quit IRC09:39
*** shaohe_feng has quit IRC09:39
*** shaohe_feng has joined #openstack-meeting09:40
*** zhhuabj_ has joined #openstack-meeting09:40
*** numans has quit IRC09:46
*** mrunge_ has joined #openstack-meeting09:46
*** mrunge has quit IRC09:47
*** shaohe_feng has quit IRC09:49
*** shaohe_feng has joined #openstack-meeting09:50
*** matrohon has quit IRC09:51
*** vikasc has joined #openstack-meeting09:54
*** ivc_ has joined #openstack-meeting09:59
*** shaohe_feng has quit IRC10:00
*** shaohe_feng has joined #openstack-meeting10:00
*** markvoelker has joined #openstack-meeting10:01
*** ivc_ has quit IRC10:01
*** HeOS has quit IRC10:03
*** ivc_ has joined #openstack-meeting10:03
*** HeOS has joined #openstack-meeting10:03
*** markvoelker has quit IRC10:05
*** Nakato has quit IRC10:05
*** zhurong_ has quit IRC10:05
*** Nakato has joined #openstack-meeting10:06
*** radeks has joined #openstack-meeting10:07
*** matrohon has joined #openstack-meeting10:07
*** zhangguoqing has quit IRC10:08
*** Mishra has joined #openstack-meeting10:09
*** shaohe_feng has quit IRC10:10
*** guoshan has quit IRC10:10
*** shaohe_feng has joined #openstack-meeting10:11
*** sdague has joined #openstack-meeting10:11
*** guoshan has joined #openstack-meeting10:11
*** guoshan has quit IRC10:16
*** shaohe_feng has quit IRC10:20
*** amitgandhinz has joined #openstack-meeting10:20
*** shaohe_feng has joined #openstack-meeting10:21
*** matrohon has quit IRC10:24
*** mrmartin has joined #openstack-meeting10:25
*** amitgandhinz has quit IRC10:25
*** Mishra has quit IRC10:27
*** shaohe_feng has quit IRC10:30
*** ntpttr- has quit IRC10:31
*** shaohe_feng has joined #openstack-meeting10:31
*** jlanoux_ has joined #openstack-meeting10:31
*** jlanoux has quit IRC10:32
*** ntpttr has joined #openstack-meeting10:39
*** sshnaidm is now known as sshnaidm|lnch10:39
*** shaohe_feng has quit IRC10:41
*** matrohon has joined #openstack-meeting10:41
*** shaohe_feng has joined #openstack-meeting10:41
*** guoshan has joined #openstack-meeting10:46
*** roxanaghe has joined #openstack-meeting10:48
*** obondarev has joined #openstack-meeting10:50
*** shaohe_feng has quit IRC10:51
*** shaohe_feng has joined #openstack-meeting10:52
*** sdake has joined #openstack-meeting10:53
*** roxanaghe has quit IRC10:53
*** jlanoux has joined #openstack-meeting10:54
*** jlanoux_ has quit IRC10:54
*** Guest73697 has quit IRC10:54
*** matrohon has quit IRC10:58
*** Ravikiran_K has quit IRC10:59
*** zhangguoqing has joined #openstack-meeting11:01
*** obondarev has quit IRC11:01
*** shaohe_feng has quit IRC11:01
*** markvoelker has joined #openstack-meeting11:02
*** shaohe_feng has joined #openstack-meeting11:02
*** guoshan has quit IRC11:03
*** guoshan has joined #openstack-meeting11:03
*** e0ne has quit IRC11:04
*** markvoelker has quit IRC11:06
*** tommylike__hu has joined #openstack-meeting11:07
*** sdake has quit IRC11:08
*** jckasper has joined #openstack-meeting11:08
*** epico has quit IRC11:09
*** r-mibu has quit IRC11:11
*** shaohe_feng has quit IRC11:11
*** shaohe_feng has joined #openstack-meeting11:12
*** jckasper has quit IRC11:13
*** tommylike__hu has quit IRC11:14
*** rtheis has joined #openstack-meeting11:14
*** matrohon has joined #openstack-meeting11:14
*** guoshan has quit IRC11:15
*** akuznetsov has joined #openstack-meeting11:16
*** guoshan has joined #openstack-meeting11:16
*** dkehn_ has quit IRC11:16
*** matrohon has quit IRC11:19
*** r-mibu has joined #openstack-meeting11:19
*** sudipto_ has quit IRC11:20
*** amitgandhinz has joined #openstack-meeting11:21
*** shaohe_feng has quit IRC11:22
*** shaohe_feng has joined #openstack-meeting11:22
*** Julien-zte has quit IRC11:24
*** sudipto has joined #openstack-meeting11:24
*** sshnaidm|lnch is now known as sshnaidm11:25
*** kaminohana has joined #openstack-meeting11:25
*** amitgandhinz has quit IRC11:25
*** alyson_ has joined #openstack-meeting11:28
*** ericksonsantos has joined #openstack-meeting11:29
*** dkehn_ has joined #openstack-meeting11:29
*** yamamoto has quit IRC11:30
*** shaohe_feng has quit IRC11:32
*** shaohe_feng has joined #openstack-meeting11:33
*** samP has quit IRC11:33
*** anilvenkata is now known as anilvenkata_afk11:35
*** matrohon has joined #openstack-meeting11:35
*** oferby has quit IRC11:38
*** oferby has joined #openstack-meeting11:39
*** obondarev has joined #openstack-meeting11:39
*** coolsvap_ is now known as coolsvap11:39
*** gouthamr has joined #openstack-meeting11:41
*** shaohe_feng has quit IRC11:42
*** sindhu has joined #openstack-meeting11:42
*** dprince has joined #openstack-meeting11:43
*** shaohe_feng has joined #openstack-meeting11:43
*** rfolco has joined #openstack-meeting11:45
*** ihrachys has quit IRC11:47
*** julim has joined #openstack-meeting11:47
*** sudipto has quit IRC11:47
*** ihrachys has joined #openstack-meeting11:50
*** yamamoto has joined #openstack-meeting11:51
*** yamamoto has quit IRC11:51
*** sindhu has quit IRC11:52
*** jaypipes has joined #openstack-meeting11:52
*** shaohe_feng has quit IRC11:52
*** matrohon has quit IRC11:53
*** shaohe_feng has joined #openstack-meeting11:53
*** thorst_ has joined #openstack-meeting11:54
*** dprince has quit IRC11:56
*** dprince has joined #openstack-meeting11:56
*** sshnaidm is now known as sshnaidm|afk11:56
*** weshay has joined #openstack-meeting11:57
*** yassine has joined #openstack-meeting12:00
*** yassine is now known as Guest737012:01
*** amitgandhinz has joined #openstack-meeting12:01
*** akuznetsov has quit IRC12:01
*** yamamoto has joined #openstack-meeting12:02
*** numans has joined #openstack-meeting12:02
*** markvoelker has joined #openstack-meeting12:02
*** shaohe_feng has quit IRC12:03
*** shaohe_feng has joined #openstack-meeting12:04
*** ivyyy_ is now known as ivyyy12:04
*** markvoelker has quit IRC12:07
*** sridharg has quit IRC12:09
*** matrohon has joined #openstack-meeting12:09
*** sudipto has joined #openstack-meeting12:12
*** shaohe_feng has quit IRC12:13
*** shaohe_feng has joined #openstack-meeting12:14
*** mrmartin has quit IRC12:14
*** sudipto has quit IRC12:14
*** anilvenkata_afk is now known as anilvenkata12:15
*** sridharg has joined #openstack-meeting12:15
*** zhurong has joined #openstack-meeting12:15
*** pradk has joined #openstack-meeting12:20
*** tommylikehu_ has joined #openstack-meeting12:22
*** markvoelker has joined #openstack-meeting12:23
tommylikehu_who is openstack12:23
*** shaohe_feng has quit IRC12:23
*** shaohe_feng has joined #openstack-meeting12:24
*** e0ne has joined #openstack-meeting12:26
*** amitgandhinz has quit IRC12:26
*** amitgandhinz has joined #openstack-meeting12:27
*** Julien-zte has joined #openstack-meeting12:27
*** matrohon has quit IRC12:28
*** tpsilva has joined #openstack-meeting12:28
*** yamamoto has quit IRC12:29
*** ayoung has quit IRC12:33
*** sshnaidm|afk is now known as sshnaidm12:33
*** shaohe_feng has quit IRC12:33
*** shaohe_feng has joined #openstack-meeting12:34
*** maeca1 has joined #openstack-meeting12:35
*** sshnaidm has quit IRC12:35
*** bill_az has joined #openstack-meeting12:35
*** roxanaghe has joined #openstack-meeting12:36
*** rossella_s has quit IRC12:38
*** rossella_s has joined #openstack-meeting12:39
*** uxdanielle has joined #openstack-meeting12:39
*** uxdanielle has quit IRC12:39
*** bobh has joined #openstack-meeting12:39
*** toddjohn has joined #openstack-meeting12:40
*** roxanaghe has quit IRC12:41
*** baojg has joined #openstack-meeting12:43
*** shaohe_feng has quit IRC12:44
*** matrohon has joined #openstack-meeting12:44
*** shaohe_feng has joined #openstack-meeting12:45
*** toddjohn has quit IRC12:45
*** lbrune has joined #openstack-meeting12:46
*** guoshan_ has joined #openstack-meeting12:47
*** guoshan has quit IRC12:47
*** sindhu has joined #openstack-meeting12:49
*** baojg has quit IRC12:49
*** toddjohn has joined #openstack-meeting12:49
*** bobh has quit IRC12:50
*** jrist has quit IRC12:52
*** Hosam has joined #openstack-meeting12:53
*** piet has joined #openstack-meeting12:53
*** numan_ has joined #openstack-meeting12:54
*** matrohon has quit IRC12:54
*** shaohe_feng has quit IRC12:54
*** shaohe_feng has joined #openstack-meeting12:55
*** kylek3h has joined #openstack-meeting12:55
*** numans has quit IRC12:55
*** jckasper has joined #openstack-meeting12:56
*** epcim has joined #openstack-meeting12:58
*** kylek3h has quit IRC12:58
*** sshnaidm has joined #openstack-meeting12:58
*** coolsvap is now known as _coolsvap_12:58
*** mriedem has joined #openstack-meeting12:59
*** baojg has joined #openstack-meeting12:59
Qiming#startmeeting senlin13:00
openstackMeeting started Tue Aug  9 13:00:19 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
*** zul_ has quit IRC13:00
*** enriquetaso has joined #openstack-meeting13:01
*** elynn has joined #openstack-meeting13:01
*** lixinhui_ has joined #openstack-meeting13:01
*** liuhanxi has quit IRC13:01
*** jckasper has quit IRC13:01
*** andymaier has joined #openstack-meeting13:01
*** dslevin has quit IRC13:01
*** baojg has quit IRC13:03
Qiminghi, elynn13:03
guoshan_hi, everyone~13:03
elynnevening Qiming13:03
Qiminghi, guoshan_13:03
*** myoung|afk is now known as myoung13:04
Qimingpls feel free to add items to the meeting agenda13:04
Qiming#link https://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Weekly_Senlin_.28Clustering.29_meeting13:04
*** shaohe_feng has quit IRC13:04
Qimingdue to firewall problem, adding meeting items is not easy now, we have to use proxy13:04
Qimingyanyan cannot join us today, I heard nothing from xinhui or haiwei13:05
Qiminglet's get started?13:05
guoshan_ok, It's my first time in IRC meeting13:05
Qimingthanks, guoshan_13:05
*** shaohe_feng has joined #openstack-meeting13:05
*** zul_ has joined #openstack-meeting13:05
Qiming#link https://etherpad.openstack.org/p/senlin-newton-workitems13:05
*** jrist has joined #openstack-meeting13:06
*** links has quit IRC13:06
Qiminglet's go thru the etherpad and see where we are13:06
Qimingyanyan has updated the etherpad for Rally support13:07
Qiminghi, lixinhui_13:07
Qimingwe just got started13:07
*** jckasper has joined #openstack-meeting13:07
Qimingthe Rally side support was just merged, Roman has help review another patch in senlin code base, which is good ...13:07
QimingI'm not gonna copy/paste yanyan's update here13:08
*** trozet has joined #openstack-meeting13:08
Qimingplease read it13:08
QimingWill delete those text later13:08
Qimingintegration test13:08
*** sdake has joined #openstack-meeting13:08
Qimingtest job has been merged at gate side13:08
*** sdake has quit IRC13:08
*** sdake has joined #openstack-meeting13:08
Qimingwe found things to be fixed related to neutron set up13:09
Qimingthese tests are pretty important for us to ensure we are not breaking any contracts with any other services13:09
*** piet has quit IRC13:10
*** b1airo has quit IRC13:10
Qimingat the same time, I'm working on revising the docs about testing infrastructure13:10
Qiming#link http://git.openstack.org/cgit/openstack/senlin/tree/doc/source/developer/testing.rst13:10
*** matrohon has joined #openstack-meeting13:10
Qimingthe current doc is only about unit tests13:10
Qimingwhile we have added api test, functional test, integration test and stress test (ongoing)13:11
Qimingneed to update the docs so we all know how to run them in our local env13:11
*** toddjohn has quit IRC13:11
Qimingpls help review the patches and see if there things to be fixed13:12
*** Poornima has quit IRC13:12
guoshan_sure, pleasure to do that13:12
*** cleong has joined #openstack-meeting13:12
*** merooney has joined #openstack-meeting13:12
Qimingmoving on ...13:12
Qiminghealth management13:12
*** baoli has joined #openstack-meeting13:13
Qiminglixinhui_, the LB member status one is fixed?13:13
lixinhui_2 of 3 patches have been approved13:14
lixinhui_the root one is pending for cores' approval13:14
*** baoli_ has joined #openstack-meeting13:14
*** julim has quit IRC13:14
*** shaohe_feng has quit IRC13:14
*** kylek3h has joined #openstack-meeting13:14
*** kylek3h has quit IRC13:14
Qimingnext thing is about fencing13:15
*** kylek3h has joined #openstack-meeting13:15
QimingI know you have added some support into python-openstacksdk side13:15
*** shaohe_feng has joined #openstack-meeting13:15
Qimingthose are already well shaped, just address brian's concern would be fine13:15
lixinhui_neutron-lbaas community is not very active13:15
lixinhui_I added Armando as reviewer13:15
lixinhui_hope he can help13:15
lixinhui_in future, Octavia will replace lbaas13:15
lixinhui_Brian just add comments there13:16
lixinhui_I will followup soon13:16
Qimingfor those of you who are not aware of these patches:13:16
Qimingthese are the ones added to sdk so that we can invoke nova service operations later -- for fencing's purpose13:17
*** sdake has quit IRC13:17
*** xyang1 has joined #openstack-meeting13:17
Qimingmoving on to next item13:17
Qimingdocumentation, not much update from me13:17
*** baoli has quit IRC13:18
Qimingbut I did submitted some patches about api docs13:18
*** xiaohhui has joined #openstack-meeting13:18
Qimingone thing to notice is that the global version requirement of os-api-ref has been bumped to 0.4.013:18
*** permalac has joined #openstack-meeting13:18
Qimingwhich means it has a better support to success code and error code now13:19
*** sdake has joined #openstack-meeting13:19
*** xiaohhui has quit IRC13:19
*** jpeeler has joined #openstack-meeting13:19
Qimingif you are interested in it, you can check this subsection: http://git.openstack.org/cgit/openstack/os-api-ref/tree/doc/source/usage.rst#n18513:20
*** xiaohhui has joined #openstack-meeting13:20
*** cardeois has joined #openstack-meeting13:20
Qimingmoving on to next one13:20
Qimingprofile/policy version control13:20
*** qwebirc78847 has joined #openstack-meeting13:20
Qimingyanyan has proposed a patch which I forgot to review13:20
*** lblanchard has joined #openstack-meeting13:21
Qimingplease jump on to it when you have time13:21
Qimingit is very important a feature, though in future we plan to generalize versioning control of many things13:21
elynnwill review it later.13:22
Qiming^ is the patch13:22
Qimingthx elynn13:22
*** cknight has joined #openstack-meeting13:23
Qimingnext topic is container cluster support13:23
*** esberglu has joined #openstack-meeting13:23
*** sdake_ has joined #openstack-meeting13:23
Qiminghaiwei has a new patchset for review: https://review.openstack.org/#/c/34990613:23
Qimingthough it still not comprehensive, as a working prototype, it looks not bad13:23
*** sdake has quit IRC13:24
Qimingalso need reviews from you13:24
*** nmagnezi has quit IRC13:24
*** xiaohhui has quit IRC13:24
Qiminghaiwei is not online today, seems13:24
Qimingso we move on to next one13:24
Qimingzaqar receiver support13:24
Qimingyanyan has been pushing hard on zaqar support at sdk side13:25
*** shaohe_feng has quit IRC13:25
Qimingdue to api doc and some implementation nits, the patches are still pending for review/merge13:25
Qimingbut we are pretty close to get it done13:25
Qimingnext one13:26
*** shaohe_feng has joined #openstack-meeting13:26
Qimingnot update from me on this, probably we won't have time to get it done in newton13:26
*** ayoung has joined #openstack-meeting13:26
*** liuhanxi has joined #openstack-meeting13:26
Qimingsome updates on cluster-collect13:27
Qimingthe senlin side has a fix to the docs merged: https://review.openstack.org/35098213:28
Qimingand finally we got API micro-versioning support merged in openstacksdk: https://review.openstack.org/34399213:28
Qimingfollowing that, we got a new API (collect_cluster_attrs) merged: https://review.openstack.org/35097813:29
*** yamamoto has joined #openstack-meeting13:29
*** vikasc has quit IRC13:29
QimingI'm now working at senlinclient side on the micro-versioning and cluster-collect operation support13:29
*** jckasper has quit IRC13:30
Qimingthe output is something like this:13:31
Qiming$ senlin cluster-collect -p details.addresses.private[0] c113:31
QimingWARNING (shell) "senlin cluster-collect" is deprecated, please use "openstack cluster collect" instead.13:31
*** jckasper has joined #openstack-meeting13:31
elynnlooks great!13:31
*** thorst_ has quit IRC13:31
Qimingand also this:13:32
Qiming$ openstack cluster collect -f value -c attr_value --path details.addresses.private[0] c113:32
Qimingneed to add test cases then commit the patch13:32
elynna question, how would the users know what kind of attributes they can get?13:33
Qimingit is a JSON path13:33
*** jckasper_ has joined #openstack-meeting13:33
Qimingwhen you do senlin node-show <node_id>13:33
Qimingyou get the attributes13:33
elynnoh, I see.13:33
Qimingthen you think to yourself, how can I get all the values from all nodes instead of doing cluster node-show one by one13:34
Qimingwell, that is when you decide to use senlin cluster-collect or openstack cluster collect13:34
*** rodrigods has quit IRC13:35
*** shaohe_feng has quit IRC13:35
Qimingby the way, just found a bug in sdk and proposed a patch13:35
elynnGlad that we could provide this API.13:35
*** jckasper has quit IRC13:35
*** rodrigods has joined #openstack-meeting13:35
*** bill_az_ has joined #openstack-meeting13:35
Qimingwhen senlin is retrieving the details about a nova server, the 'image' property disappeared, so does the 'flavor' property13:36
*** shaohe_feng has joined #openstack-meeting13:36
Qiminghope it can be merged soon13:36
*** yamamoto has quit IRC13:37
Qimingbesides that, I don't have more updates13:37
*** sarob has joined #openstack-meeting13:37
Qimingquestions/comments about items on etherpad?13:37
*** jckasper_ has quit IRC13:38
Qimingokay, that is a no13:38
elynnNot from me, newton-3 will be end this month?13:38
Qimingyep, http://releases.openstack.org/newton/schedule.html13:38
Qimingnewton-3 on august 2913:39
Qimingrc-1 on sep 1213:39
Qimingrc-2 on sep-2613:39
*** sindhu has quit IRC13:40
Qimingsince we don't have a lot of features pipeline13:40
Qimingso we don't need to practice a feature freeze type of thing13:40
*** _nadya_ has quit IRC13:40
Qimingjust work to our best ... deliver what can be made stable13:41
Qiming#topic open discussions13:41
*** openstack changes topic to "open discussions (Meeting topic: senlin)"13:41
Qiminganything else?13:42
*** sbelous has joined #openstack-meeting13:42
*** matrohon has quit IRC13:42
*** hoangcx has joined #openstack-meeting13:42
lixinhui_Qiming, have you tried the vertioned_nova?13:42
*** sarob has quit IRC13:42
*** anilvenkata is now known as anilvenkata_afk13:42
*** ivc_ has quit IRC13:42
Qimingwhat is versioned_nova?13:42
Qiminga software?13:43
*** sbelous has left #openstack-meeting13:43
Qimingokay, you mean versioned notification from nova13:45
*** shaohe_feng has quit IRC13:45
Qimingit is good to add versioned_notifications as a target13:45
*** shaohe_feng has joined #openstack-meeting13:46
Qimingmy question was whether that new target can be used for notifications with 'notifications' as topic13:46
*** hoangcx has quit IRC13:46
lixinhui_why that way?13:47
*** eharney has joined #openstack-meeting13:47
Qimingor, a different way to ask the question ... has nova migrated all their notifications to this versioned way?13:47
*** rbak has joined #openstack-meeting13:47
*** rfolco has quit IRC13:48
lixinhui_is that enough to migrate all instance.update?13:48
Qiminga safer way to add 'versioned_notifications' as a Target is to keep the old one, we won't get hurt if there are not messages with that topic13:48
*** rfolco has joined #openstack-meeting13:49
*** spzala has joined #openstack-meeting13:50
*** liuhanxi has quit IRC13:50
Qimingbut if nova is only migrating part of their notifications to the versioned way, ... that is bad13:50
lixinhui_according to the doc, original one will be retired13:50
*** toddjohn has joined #openstack-meeting13:50
lixinhui_why we receive two channels13:50
QimingI never trust their docs13:50
Qimingthey said they will work out a v3 api13:50
Qimingthey said they will split scheduler out13:50
*** spotz_zzz is now known as spotz13:51
lixinhui_I tested instance.update and service.update13:51
*** anilvenkata_afk is now known as anilvenkata13:51
Qimingwe can listen to two channels, if one channel is really quiet, we can delete it later13:51
Qimingyes, I figured that13:51
Qimingbut instance.update and service.update is not the whole world, right?13:52
*** jckasper has joined #openstack-meeting13:52
lixinhui_how about noisy13:52
*** SumitNaiksatam has joined #openstack-meeting13:52
lixinhui_according to its design, yes13:52
*** sindhu has joined #openstack-meeting13:52
*** yb has joined #openstack-meeting13:52
lixinhui_whole world of nova notifications13:52
lixinhui_just throw a question here13:52
*** AmitGalitz has quit IRC13:53
*** yb has left #openstack-meeting13:53
lixinhui_we can leave the old one till compute service failure detection13:53
Qiminga target is constructed with a 'topic' and an 'exchange'13:54
Qimingwe already set the 'exchange' to 'nova'13:54
lixinhui_there is no change on exchange13:54
lixinhui_I use Rabbitmq as message provide13:55
Qimingthe combination means, we listen to 'notifications' from 'nova'13:55
*** xiaohhui has joined #openstack-meeting13:55
Qimingif nova has migrated all its notifications to the versioned implementation13:55
Qimingthat target should be quiet13:55
*** uxdanielle has joined #openstack-meeting13:55
*** shaohe_feng has quit IRC13:55
lixinhui_and confirm no change on exchange13:55
Qimingif it is not, it means nova is still doing the migration13:56
*** jckasper has quit IRC13:56
QimingI know you didn't change exchange13:56
*** xiaohhui has quit IRC13:56
*** sindhu has quit IRC13:56
*** mrmartin has joined #openstack-meeting13:56
QimingI'm trying my best to explain to you why I think keeping the existing target doesn't hurt us13:56
*** guoshan_ has quit IRC13:56
*** shaohe_feng has joined #openstack-meeting13:56
*** jckasper_ has joined #openstack-meeting13:56
*** xiaohhui has joined #openstack-meeting13:57
*** guoshan has joined #openstack-meeting13:57
lixinhui_not I change the exchange13:57
*** xiaohhui has quit IRC13:57
*** julim has joined #openstack-meeting13:57
*** xiaohhui has joined #openstack-meeting13:57
lixinhui_I just trying to explain the test result13:57
Qimingif nova has migrated all notifications to versioned one, the existing target will be quiet, we won't get anything from it, we are not hurt13:57
*** jckasper_ has quit IRC13:57
Qimingyou are only testing instance.update and service.update, right?13:58
*** jckasper has joined #openstack-meeting13:58
*** matrohon has joined #openstack-meeting13:58
Qimingdo we know when an instance is stopped, or deleted? using the 'instance.update' notification?13:58
*** wanghao_ has quit IRC13:58
*** matrohon has quit IRC13:59
Qimingor maybe the protocol has changed, I haven't looked into that for a time13:59
*** cdelatte has joined #openstack-meeting13:59
Qimingokay, I'll do some experiements to verify13:59
lixinhui_stop or delete are details of instance.update14:00
Qimingthanks for bringing this up14:00
Qimingtime is up14:00
Qimingthanks for joining, guys14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Tue Aug  9 14:00:21 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-08-09-13.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-08-09-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-08-09-13.00.log.html14:00
*** _coolsvap_ is now known as coolsvap14:00
lixinhui_good night14:01
*** woodster_ has joined #openstack-meeting14:01
*** jamesdenton has joined #openstack-meeting14:02
*** yuval has quit IRC14:02
*** dasanind_ has joined #openstack-meeting14:03
*** spotz is now known as spotz_zzz14:04
*** ebalduf has joined #openstack-meeting14:04
*** elynn has quit IRC14:05
*** tonytan4ever has joined #openstack-meeting14:05
*** xiaohhui has quit IRC14:05
*** john-davidge has joined #openstack-meeting14:06
*** shaohe_feng has quit IRC14:06
*** xiaohhui has joined #openstack-meeting14:06
*** john-davidge has left #openstack-meeting14:06
*** rrecio has joined #openstack-meeting14:06
*** xiaohhui has quit IRC14:06
*** zz_dimtruck is now known as dimtruck14:06
*** xiaohhui has joined #openstack-meeting14:07
*** shaohe_feng has joined #openstack-meeting14:07
*** rrecio_ has joined #openstack-meeting14:07
*** nmagnezi has joined #openstack-meeting14:07
*** iyamahat has joined #openstack-meeting14:07
*** guoshan has quit IRC14:08
*** bobh has joined #openstack-meeting14:09
*** mtanino has joined #openstack-meeting14:09
*** bobh has quit IRC14:10
*** lixinhui_ has quit IRC14:10
*** bobh has joined #openstack-meeting14:10
*** rrecio has quit IRC14:11
*** Hosam has quit IRC14:11
*** mrmartin has quit IRC14:11
*** Hosam has joined #openstack-meeting14:11
*** xiaohhui has quit IRC14:11
*** spotz_zzz is now known as spotz14:12
*** sindhu has joined #openstack-meeting14:12
*** edtubill has joined #openstack-meeting14:12
*** vishwanathj has joined #openstack-meeting14:13
*** galstrom_zzz is now known as galstrom14:14
*** matrohon has joined #openstack-meeting14:15
*** Hosam has quit IRC14:15
*** shaohe_feng has quit IRC14:16
*** jckasper has quit IRC14:18
*** shaohe_feng has joined #openstack-meeting14:19
*** pece has quit IRC14:19
*** mrmartin has joined #openstack-meeting14:21
*** yamahata has joined #openstack-meeting14:22
*** kaminohana has quit IRC14:24
*** jckasper has joined #openstack-meeting14:24
*** RichB has joined #openstack-meeting14:25
*** banix has joined #openstack-meeting14:25
*** mriedem1 has joined #openstack-meeting14:25
*** thorst_ has joined #openstack-meeting14:26
*** mriedem has quit IRC14:26
*** shaohe_feng has quit IRC14:26
*** shaohe_feng has joined #openstack-meeting14:26
*** mrmartin has quit IRC14:27
*** iyamahat has quit IRC14:27
*** jckasper has quit IRC14:28
*** yamahata has quit IRC14:28
*** jckasper has joined #openstack-meeting14:28
*** sdake_ is now known as sdake14:30
*** jorge_munoz has joined #openstack-meeting14:31
*** claudiub has joined #openstack-meeting14:32
*** janki has quit IRC14:33
*** edtubill has quit IRC14:34
*** mrmartin has joined #openstack-meeting14:35
*** jorge_munoz has quit IRC14:36
*** jorge_munoz_ has joined #openstack-meeting14:36
*** mriedem1 is now known as mriedem14:36
*** asettle has joined #openstack-meeting14:36
*** shaohe_feng has quit IRC14:36
*** shaohe_feng has joined #openstack-meeting14:37
*** thorst_ has quit IRC14:38
*** matrohon has quit IRC14:41
*** rbartal has quit IRC14:43
*** obondarev has quit IRC14:43
*** jdurgin1 has joined #openstack-meeting14:45
*** shaohe_feng has quit IRC14:47
*** shaohe_feng has joined #openstack-meeting14:47
*** pnavarro has quit IRC14:51
*** spotz is now known as spotz_zzz14:52
*** yuval has joined #openstack-meeting14:55
*** obondarev has joined #openstack-meeting14:55
*** tommylikehu_ has quit IRC14:55
*** spotz_zzz is now known as spotz14:55
*** nkrinner_afk is now known as nkrinner14:56
*** mickeys has joined #openstack-meeting14:56
*** tonytan4ever has quit IRC14:56
*** sarob has joined #openstack-meeting14:56
*** shaohe_feng has quit IRC14:57
*** tonytan4ever has joined #openstack-meeting14:57
*** dtrainor has joined #openstack-meeting14:57
*** matrohon has joined #openstack-meeting14:57
*** xiangxinyong456 has joined #openstack-meeting14:58
*** shaohe_feng has joined #openstack-meeting14:58
*** saggi has joined #openstack-meeting14:58
*** chenying_ has joined #openstack-meeting14:59
*** edtubill has joined #openstack-meeting14:59
saggi#startmeeting smaug15:00
openstackMeeting started Tue Aug  9 15:00:04 2016 UTC and is due to finish in 60 minutes.  The chair is saggi. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: smaug)"15:00
openstackThe meeting name has been set to 'smaug'15:00
saggiHi everyone15:00
saggiAre we waiting on anyone?15:00
saggi#topic Mascot and name selection15:00
*** openstack changes topic to "Mascot and name selection (Meeting topic: smaug)"15:00
saggiOK, so I'm going to announce the name change after this meeting.15:01
*** saju_m has quit IRC15:01
saggiWe are changing to Karbor15:01
*** banix has quit IRC15:01
*** sarob has quit IRC15:01
saggiand our mascot will be the Tardigrade with the majority of the votes.15:01
*** banix has joined #openstack-meeting15:02
saggiSorry beaver got +215:02
yuvaldo we need to wait for governance approval before we start changing the name? or can we start sending patches and update the wiki immediately?15:02
*** nkrinner is now known as nkrinner_afk15:03
saggiI already got approvals from Thierry15:03
*** lbrune has quit IRC15:03
chenying_Ok So we can start the patches about the name change.15:03
yuvalMyself and chenying listed the things require change: https://etherpad.openstack.org/p/smaug15:03
*** adiantum has quit IRC15:03
yuval(under Project Affected by the name change)15:03
*** matrohon has quit IRC15:04
*** thorst_ has joined #openstack-meeting15:04
yuvalWe need to submit one patch to openstack/governance, and all other patches must have "Depend-On" with that change id15:04
xiangxinyong456I guess we have a lot of work to do15:04
yuvalonce everything is set, we pass the governance patch and the rest just get merged15:05
*** mrmartin has quit IRC15:05
yuvalI can start working on that tomorrow morning, unless someone else wish to15:05
*** zhangguoqing has quit IRC15:06
chenying_Yes I can do the patches about the project smaug and client.15:06
saggiyuval: IIRC it doesn't fix the github mirrors. We need to ask for those to be changed manually.15:07
*** shaohe_feng has quit IRC15:07
saggiSo who does what?15:08
chenying_There are about ten projects.15:08
yuvalSaggi, can you do governance and mailing list announce?15:09
yuvalI'll take infra, requirements and launchpad15:09
xiangxinyong456I could do some works15:09
chenying_I can do the patches about the project smaug and client.15:09
yuvalxiangxinyong456: can you do devstack and wiki?15:10
*** spotz is now known as spotz_zzz15:10
xiangxinyong456yuval: ok15:10
zhonghua-leelet me check and update the documents15:10
*** spotz_zzz is now known as spotz15:10
*** shaohe_feng has joined #openstack-meeting15:10
xiangxinyong456I do Devstack and wiki15:11
chenying_Have we missed some prjects?15:11
yuvalupdated here: https://etherpad.openstack.org/p/smaug15:12
saggiCould you add everything to this list https://etherpad.openstack.org/p/karbor-migration-tasks15:12
*** thorst_ has quit IRC15:12
*** gyee has joined #openstack-meeting15:12
*** gongysh has joined #openstack-meeting15:14
saggi$ python -c "import random; print ['Beaver', 'Tardigrade'][random.randint(0,1)]"15:14
saggiSo Beaver won the tie15:14
yuvalIMO it's to similar to quokka15:15
yuvalat least tell them to draw the distinguished funny tail :)15:15
chenying_It is cute.15:16
xiangxinyong456beaver is good15:16
saggiThe reason is that it makes a den to store food for later15:16
saggiI assume?15:16
*** thorst_ has joined #openstack-meeting15:16
*** links has joined #openstack-meeting15:17
saggiSo I will just send the emails and notify Thierry that we are starting to send patches to move things around.15:17
*** shaohe_feng has quit IRC15:17
*** jorge_munoz_ has quit IRC15:17
saggiPlease add the relevant patches to the etherpad so that I can track everything15:18
saggi#topic open discussion15:18
*** openstack changes topic to "open discussion (Meeting topic: smaug)"15:18
saggiThat was the only topic for tday15:18
*** shaohe_feng has joined #openstack-meeting15:18
saggiWe can finish early if no one has anything to add15:19
*** jlanoux has quit IRC15:19
saggiThan we're done15:20
chenying_There is a good new. One backup software verdor cv, will develop a plugin about application protection.15:20
saggiwhat application?15:20
*** matrohon has joined #openstack-meeting15:20
saggiAre they supported in Trove?15:21
*** e0ne has quit IRC15:21
chenying_Maybe not. local database in vm15:21
chenying_don't support in Trove15:21
*** thorst_ has quit IRC15:21
saggiThan it's important that we push yuval's patches15:22
*** asettle is now known as Apsettle15:22
saggisince they are critical to enable proper application features15:22
*** Na3iL has joined #openstack-meeting15:22
chenying_I think so.15:23
saggigood news!15:23
saggilet me know when the patches are up15:23
*** jorge_munoz has joined #openstack-meeting15:23
*** dasanind_ has quit IRC15:23
saggiAnything else?15:23
chenying_maybe more then one backup verdors plan to develop the plugins.15:23
*** e0ne has joined #openstack-meeting15:24
saggiFor the same DB?15:24
*** armax has joined #openstack-meeting15:24
chenying_I don't know.15:24
saggiAnyway, the more support we get the better15:24
*** karthikp_ has joined #openstack-meeting15:25
* amrith sits in the back rows ...15:25
*** yamamoto has joined #openstack-meeting15:25
*** andymaier has quit IRC15:25
*** yamamoto has quit IRC15:25
*** radeks has quit IRC15:25
xiangxinyong456I see Sean fix some bugs in smaug.15:25
chenying_I also see it.15:26
xiangxinyong456he does a good job15:26
*** matrohon has quit IRC15:27
*** shaohe_feng has quit IRC15:28
saggiwe need to take note for these stuff15:28
saggiI rarely check that all strings are properly translatable15:28
*** shaohe_feng has joined #openstack-meeting15:28
saggiAnything else?15:29
*** thorst_ has joined #openstack-meeting15:29
saggiThings seem to be looking up. Let's hope we get more cooperation in the future.15:30
saggiGoodbye everyone15:30
yuvalgoodbye :)15:30
*** oshidoshi has joined #openstack-meeting15:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:30
openstackMeeting ended Tue Aug  9 15:30:45 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/smaug/2016/smaug.2016-08-09-15.00.html15:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/smaug/2016/smaug.2016-08-09-15.00.txt15:30
openstackLog:            http://eavesdrop.openstack.org/meetings/smaug/2016/smaug.2016-08-09-15.00.log.html15:30
*** Apsettle is now known as asettle15:30
*** yuval has quit IRC15:30
*** mageshgv has joined #openstack-meeting15:31
*** yamamoto has joined #openstack-meeting15:31
*** _nadya_ has joined #openstack-meeting15:31
*** thorst_ has quit IRC15:31
*** xiangxinyong456 has quit IRC15:32
*** banix has quit IRC15:32
*** ntpttr__ has joined #openstack-meeting15:33
*** prateek has joined #openstack-meeting15:33
*** jckasper has quit IRC15:33
*** jckasper has joined #openstack-meeting15:35
*** jckasper has quit IRC15:35
*** banix has joined #openstack-meeting15:35
*** belmoreira has quit IRC15:36
*** yamamoto has quit IRC15:36
*** yamamoto has joined #openstack-meeting15:37
*** chenying_ has quit IRC15:37
*** pnavarro has joined #openstack-meeting15:38
*** shaohe_feng has quit IRC15:38
*** shaohe_feng has joined #openstack-meeting15:39
*** leeantho has joined #openstack-meeting15:39
*** jckasper has joined #openstack-meeting15:40
*** numan_ has quit IRC15:41
*** numan_ has joined #openstack-meeting15:42
*** matrohon has joined #openstack-meeting15:44
*** anilvenkata has quit IRC15:45
*** singhj has joined #openstack-meeting15:46
*** jlanoux has joined #openstack-meeting15:46
*** numan_ has quit IRC15:47
*** sridharg has quit IRC15:48
*** shaohe_feng has quit IRC15:48
*** pcaruana has quit IRC15:48
*** shaohe_feng has joined #openstack-meeting15:48
*** yamamoto has quit IRC15:48
*** rcernin has quit IRC15:50
*** yamamoto has joined #openstack-meeting15:50
*** tesseract- has quit IRC15:50
*** nmagnezi has quit IRC15:51
*** matrohon has quit IRC15:52
*** neel has joined #openstack-meeting15:53
*** thorst_ has joined #openstack-meeting15:53
*** mikelk has quit IRC15:53
*** yamamoto has quit IRC15:53
*** cdnchris has joined #openstack-meeting15:54
*** janki has joined #openstack-meeting15:55
*** xuan0802 has joined #openstack-meeting15:55
*** xuan0802 has quit IRC15:56
*** manikanta_tadi has joined #openstack-meeting15:56
*** yamamoto has joined #openstack-meeting15:56
*** tbh has joined #openstack-meeting15:57
*** gongysh has quit IRC15:57
*** Sukhdev has joined #openstack-meeting15:57
*** tung_doan has joined #openstack-meeting15:57
*** gokrokve has joined #openstack-meeting15:58
*** Jeffreyc42 has joined #openstack-meeting15:58
*** shaohe_feng has quit IRC15:58
*** xuan_ has joined #openstack-meeting15:59
*** sripriya has joined #openstack-meeting15:59
*** shaohe_feng has joined #openstack-meeting15:59
*** s3wong has joined #openstack-meeting16:00
*** fnaval has joined #openstack-meeting16:00
*** baumann has joined #openstack-meeting16:00
*** thorst_ has quit IRC16:00
*** fnaval has quit IRC16:01
*** pnavarro has quit IRC16:01
*** singhj has quit IRC16:01
*** fnaval has joined #openstack-meeting16:01
*** s3wong has quit IRC16:01
*** yamamoto has quit IRC16:01
*** obondarev has quit IRC16:02
*** banix has quit IRC16:02
*** pnavarro has joined #openstack-meeting16:03
*** adiantum has joined #openstack-meeting16:04
*** KanagarajM has joined #openstack-meeting16:04
*** fnaval_ has quit IRC16:04
*** kebray has joined #openstack-meeting16:04
*** dprince has quit IRC16:04
*** RichB has quit IRC16:04
*** dasanind_ has joined #openstack-meeting16:04
sridhar_ram#startmeeting tacker16:04
openstackMeeting started Tue Aug  9 16:04:48 2016 UTC and is due to finish in 60 minutes.  The chair is sridhar_ram. Information about MeetBot at http://wiki.debian.org/MeetBot.16:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:04
*** openstack changes topic to " (Meeting topic: tacker)"16:04
openstackThe meeting name has been set to 'tacker'16:04
sridhar_ram#topic Roll Call16:04
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"16:05
sridhar_ramwho is here?16:05
*** seldenr has joined #openstack-meeting16:05
sridhar_ram.. for tacker meeting :)16:05
manikanta_tadiHi all16:05
sridhar_ramGood to see you all !16:05
*** matthewbodkin has quit IRC16:05
*** dprince has joined #openstack-meeting16:05
sridhar_ramlets start.. sorry for the delay16:06
sridhar_ram#topic Agenda16:06
*** openstack changes topic to "Agenda (Meeting topic: tacker)"16:06
sridhar_ram#link https://wiki.openstack.org/wiki/Meetings/Tacker16:06
sridhar_ramwe have lot to discuss..16:06
sridhar_ram#topic Annoucements16:06
*** openstack changes topic to "Annoucements (Meeting topic: tacker)"16:06
*** natarajk has joined #openstack-meeting16:07
*** zhurong has quit IRC16:07
sridhar_ramThanks everyone for joining the Tacker Midycle Meetup ... i know it was lot of time commitment across two days16:07
*** banix has joined #openstack-meeting16:07
sridhar_ram#info https://etherpad.openstack.org/p/tacker-newton-midcycle16:07
*** dasanind_ has quit IRC16:07
*** baoli_ has quit IRC16:08
*** pnavarro has quit IRC16:08
sridhar_ram#topic Newton Release timeline16:08
*** openstack changes topic to "Newton Release timeline (Meeting topic: tacker)"16:08
*** dasanind_ has joined #openstack-meeting16:08
*** unicell has quit IRC16:08
sridhar_ram#link http://releases.openstack.org/newton/schedule.html16:08
*** Julien-zte has quit IRC16:08
*** shaohe_feng has quit IRC16:09
*** matrohon has joined #openstack-meeting16:09
sridhar_ramGiven we are big-tent project.. we need to adhere to the openstack release teams deadlines..16:09
*** e0ne has quit IRC16:09
sridhar_ramOur project is marked as "release-with-intermediary"16:09
*** shaohe_feng has joined #openstack-meeting16:09
manikanta_tadiSo Aug 29 is the deadline for code freeze ?16:10
sridhar_ram.. for based on that and the newton schedule above, here is the plan..16:10
sridhar_rammanikanta_tadi: will explain in a minute16:10
manikanta_tadisridhar_ram: Ok16:10
*** iyamahat has joined #openstack-meeting16:10
sridhar_ram#info Final release of tackerclient is on Aug 29th16:10
sridhar_ramThis means all tackerclient changes - CLIs, API clients - needs to be finished by Aug 26th (Friday)16:11
sridhar_ramAfter this date no CLI change is possible for Newton16:11
*** numan_ has joined #openstack-meeting16:12
sridhar_ramfor e.g. CLI portion of vnffg, scaling, audit-event log to wrap up by this date16:12
*** Sukhdev has quit IRC16:12
*** e0ne has joined #openstack-meeting16:12
sridhar_ram#info Intermediary release of tacker & tacker-horizon on Aug 29th16:12
*** toddjohn has quit IRC16:12
sridhar_ramthis is a check point newton release for tacker (non-client) portions16:12
*** banix has quit IRC16:13
sripriyasridhar_ram: does this include tacker-horizon freeze?16:13
*** toddjohn has joined #openstack-meeting16:13
sridhar_ramIf your feature this wrapped up by Aug 26th it will get released as part of it..16:13
*** tswanson_ has quit IRC16:13
sridhar_ramsripriya: no.. tacker & tacker-horizon always gets released together16:14
sridhar_ram#info Final release of tacker & tacker-horizon on Sep 23rd16:14
*** santoshk has joined #openstack-meeting16:14
sripriyasridhar_ram:  ok16:14
*** sindhu has quit IRC16:14
*** e0ne has quit IRC16:14
*** dasanind_ has quit IRC16:15
*** amitgandhinz has quit IRC16:15
sridhar_ramWe also need at least 1 - 2 weeks to take care of integration issues..16:15
*** amitgandhinz has joined #openstack-meeting16:16
sridhar_ramthat puts us to Sep 12th as the code-freeze date to make it to newton16:16
*** matrohon has quit IRC16:17
sridhar_rammanikanta_tadi: so, in short we have time till Aug 26th for CLI and Sept 12 for server & horizon changes16:17
sridhar_ramAny questions ?16:17
*** toddjohn has quit IRC16:17
manikanta_tadisridhar_ram: Thanks for clear insight16:18
sridhar_ramWe have a quick challenging time last time during Mitaka release, as we had teething integration and Critical bugs in the last week16:18
*** amitgandhinz has quit IRC16:19
sridhar_ramI'd like to avoid getting us in that situation this time around..16:19
*** shaohe_feng has quit IRC16:19
sridhar_ramSo, we might need to punt some features that are not "release ready" to the follow on Ocata release16:19
*** amitgandhinz has joined #openstack-meeting16:19
*** shaohe_feng has joined #openstack-meeting16:20
sridhar_ramLooking for the team's support in making a feature rich but at the same time well rounded release - less bugs, better docs, etc16:20
sridhar_ramwill stop my soap box now :)16:20
sridhar_ramplease reach out if you think ur feature won't be able to make it in these deadlines16:21
sridhar_rammoving on..16:21
sripriyasridhar_ram: is it possible to provide any critical fixes of these features after the release?16:21
*** dkushwaha has joined #openstack-meeting16:21
sridhar_ramsripriya: yes, you can .. a critical bug fix can go into stable/newton branch at anytime.. but there are some restrictions16:22
sridhar_ramlike .. (a) no requirements.txt changes are allowed - you can pull in new dependencies16:22
sripriyasridhar_ram: hoping we don’t have to :-)16:22
sridhar_ram(b) no db migration scripts are allowed16:23
sridhar_ramsripriya: yep, stable team at times asks teams to revert a patchset if it violates this policy16:23
sridhar_ramit is lot easier to take care before the deadlines listed earlier..16:24
*** dkehn_ has quit IRC16:24
sridhar_ram#topic Newton Priorities16:24
*** openstack changes topic to "Newton Priorities (Meeting topic: tacker)"16:24
sridhar_ramcontinuing on the subject, I'd like to request the team to prioritize patchsets, fixes and most importantly the reviews that are planned for Newton first16:25
sridhar_ramhere is the etherpad with requests to help for newton release ..16:25
sridhar_ram#link newton16:26
* sridhar_ram oops16:26
sridhar_ram#link https://etherpad.openstack.org/p/tacker-newton-release-priority16:26
*** prateek has quit IRC16:27
sridhar_ramcan you please take a look at this etherpad and signup for NEED OWNERS and NEED REVIEWERS..16:27
*** lbrune has joined #openstack-meeting16:27
*** Guest7370 has quit IRC16:28
sridhar_ramanything not listed in this etherpad is deemed low priority for Newton and hence need to move to Ocata16:28
*** dasanind_ has joined #openstack-meeting16:28
tung_doansridhar_ram: Does it have any chance for alarm monitoring? I have intention to finish my code in this week or the early next week.16:28
sridhar_ramso, if you think your patchset is something that is *must have* in newton please add it to this etherpad16:28
sridhar_ramtung_doan: can you remind me, does alarm-monitoring has any CLI / tackerclient changes ?16:29
*** shaohe_feng has quit IRC16:29
tung_doansridhar_ram: no16:29
*** shaohe_feng has joined #openstack-meeting16:29
*** mmalik4 has joined #openstack-meeting16:30
manikanta_tadisridhar_ram : Should we also add VNFC  BP to the priority list16:30
sridhar_ramtung_doan: okay..16:30
tung_doansridhar_ram: I think I can finish before deadline16:30
sridhar_ramtung_doan: the main issue i see is getting reviewer's time .. other than that i don't see why it can't make it to newton16:30
sridhar_ramtung_doan: please add it to the blueprint list in the etherpad16:31
tung_doansridhar_ram: Ok. thanks sridhar16:31
sridhar_rammanikanta_tadi: VNFC BP, IMO, is a best effort.. it came in late in the cycle, so if there is bandwidth *after* we are done w/ the existing ones we shd take VNFC16:32
sridhar_rammanikanta_tadi: btw, does it have any dependency on tosca-parser ?16:32
sridhar_rammanikanta_tadi: in that case, the answer will be no16:32
*** armax has quit IRC16:32
jankisridhar_ram: how about feature of passing vnfd file as API arg16:32
tbhsridhar_ram, we don't have any dependency on tosca-parser16:32
manikanta_tadisridhar_ram: reviewers time is also a bottle neck to make the progess on spec16:32
sridhar_ramtbh: good..16:33
sridhar_rammanikanta_tadi: agree, i acknowledge that is going to the bottleneck for next 4 - 6 weeks... no easy solution there16:33
*** matrohon has joined #openstack-meeting16:33
sridhar_ramjanki: i think that is an RFE level work and it might be okay to support it...16:34
*** toddjohn has joined #openstack-meeting16:34
dkushwahasridhar_ram, Regarding nsd, are we not planning it for newton?16:34
sridhar_ramjanki: again, if there is CLI impact it need to be done soon16:34
jankisridhar_ram: ok. I am almost done. Will submit in 1-2 days16:34
jankisridhar_ram: understood16:35
sridhar_ramdkushwaha: I don't think NSD can fit newton.. it is clearly post-newton16:35
manikanta_tadisridhar_ram : true, I request the entire team in this forum to give their feedback  on VNFC BP  at their convenient time16:35
sridhar_ramdkushwaha: however i think it will be first feature we will take up post newton release..16:35
*** bvandenh has quit IRC16:36
*** banix has joined #openstack-meeting16:37
sridhar_ramdkushwaha: NSD is a significant feature with lots of new API and CLI... and i don't think we can wrap up spec & CLI by Aug 26th16:37
*** jmckind has joined #openstack-meeting16:37
*** spotz is now known as spotz_zzz16:37
sridhar_ramthanks for those who are already signing up in the etherpad .. please continue to do that!16:38
*** rossella_s has quit IRC16:38
sridhar_ramany question on newton priorities ?16:38
manikanta_tadisridhar_ram,: So other low hanging bugs will be taken for review after sep 2316:38
*** rossella_s has joined #openstack-meeting16:39
*** shaohe_feng has quit IRC16:39
*** janki has quit IRC16:40
*** janki has joined #openstack-meeting16:40
*** shaohe_feng has joined #openstack-meeting16:40
sridhar_rammanikanta_tadi: we will use our good judgement.. if there are low hanging bugs that helps towards fit-&-finish of newton release .. nothing stoping us to review & merge bef Sep 2316:40
*** banix has quit IRC16:41
sridhar_rammanikanta_tadi: for e.g. we have a bug where if bad input is given in horizon, there is an ugly looking exception thrown back..16:41
*** iyamahat has quit IRC16:41
*** jdurgin1 has quit IRC16:41
*** tbh has quit IRC16:42
sridhar_rammanikanta_tadi: it is a -ve scenario, yet.. but looks ugly as it is easy for users to get into that16:42
*** dprince has quit IRC16:42
sridhar_ramso, please help w/ your +1s ..16:42
sridhar_ramsolicit folks to review and give their +1s..16:42
manikanta_tadisridhar_ram : Understood!  Thanks..16:42
sridhar_rammany +1s helps to get +2s :)16:43
sridhar_ramwe have beaten this to death..16:43
sridhar_rammoving on16:43
*** dkehn_ has joined #openstack-meeting16:43
*** dprince has joined #openstack-meeting16:43
sridhar_ram#topic Blueprint only development process16:43
*** openstack changes topic to "Blueprint only development process (Meeting topic: tacker)"16:43
sridhar_ramI'd like to propose a slight modification to our dev process...16:44
sridhar_ram#link https://review.openstack.org/#/c/352663/16:44
sridhar_ramThis is something I was planning to bring up in the mid-cycle but didn't had time16:44
*** Benj_ has joined #openstack-meeting16:44
sridhar_ramThere are already couple of blueprints in our queue that doesn't have a need to write an elaborate spec..16:44
sridhar_ramFor e.g. tacker mistral workflows..16:45
sridhar_ram#link https://blueprints.launchpad.net/tacker/+spec/tacker-workflows16:45
*** unicell has joined #openstack-meeting16:45
sridhar_ramPlease review the process change and leave your comments..16:45
sridhar_ramtacker blueprints are looked up across openstack group and beyond .. like OPNFV, etc..16:46
KanagarajMsridhar_ram, +1 :)16:46
sridhar_ramwe should use that more to publicize all the nice work that is happening in this group16:46
sridhar_ramKanagarajM: thanks16:46
*** Benj_ has quit IRC16:47
sridhar_ramMy intention is to make the communities members life as easy as possible.. no process for process-sake :)16:47
*** piet_ has joined #openstack-meeting16:47
dkushwahasridhar_ram, +116:48
sridhar_ramdkushwaha: thanks!16:48
sridhar_ram#topic Sample mistral workflow - BP approval16:48
*** openstack changes topic to "Sample mistral workflow - BP approval (Meeting topic: tacker)"16:48
sridhar_ramrelated to the previous topic..16:48
sridhar_ramI'd like to request team's opinion on this BP..16:48
sridhar_ram#link https://blueprints.launchpad.net/tacker/+spec/tacker-workflows16:49
*** lpetrut has quit IRC16:49
sridhar_ramif anyone think this BP shouldn't be approved .. please reach out in the ML16:49
sridhar_ram#topic NSD16:49
*** openstack changes topic to "NSD (Meeting topic: tacker)"16:49
sridhar_ramdkushwaha: take it away16:50
*** shaohe_feng has quit IRC16:50
*** Sukhdev has joined #openstack-meeting16:50
dkushwahaall please provide your opinion on spec16:50
*** Sukhdev has quit IRC16:50
*** shaohe_feng has joined #openstack-meeting16:51
sridhar_ram#link https://review.openstack.org/#/c/304667/16:51
*** Sukhdev has joined #openstack-meeting16:51
*** matrohon has quit IRC16:51
*** Sukhdev has quit IRC16:51
sridhar_ramthe big decision is with or without mistral !!16:51
*** asettle has quit IRC16:51
*** natarajk has quit IRC16:51
*** armax has joined #openstack-meeting16:51
sridhar_ramdkushwaha: I'm glad you are already coming up to speed quickly on mistral16:52
*** asettle has joined #openstack-meeting16:52
*** Benj_ has joined #openstack-meeting16:52
dkushwahasridhar_ram, I can try to finish the spec by august 26, please suggest the approach16:52
sridhar_ramI know we have only few mins left.. perhaps we shd put that specific question in the agenda and have the team come prepared with their thoughts16:53
sridhar_ramdkushwaha: again, are you looking to see if NSD can make it to newton release ?16:53
dkushwahasridhar_ram, yes16:54
sridhar_ramdkushwaha: I frankly doubt it is possible .. but we can take that up in the #tacker channel after this meeting16:54
*** yamahata has joined #openstack-meeting16:54
*** dprince has quit IRC16:54
sridhar_ramdkushwaha: anything else ?16:55
*** obondarev has joined #openstack-meeting16:55
*** liyifeng has quit IRC16:55
dkushwahasridhar_ram, not for now16:55
sridhar_ramdkushwaha: okay..16:55
sridhar_ram#topic Open Discussion16:55
*** openstack changes topic to "Open Discussion (Meeting topic: tacker)"16:55
sridhar_ramfor once we have 5mins.. :)16:56
sridhar_ramany general thoughts ?16:56
*** SumitNaiksatam has quit IRC16:56
sridhar_ramlots of good discussion in the midcycle .. we shd groom them into blueprints for Ocata..16:56
*** ntpttr__ has quit IRC16:56
*** asettle has quit IRC16:56
*** ntpttr__ has joined #openstack-meeting16:56
dkushwahasridhar_ram, are we considering the meeting timing change ?16:57
sridhar_ramparticularly any takers for Murano plugin for Tacker ?16:57
manikanta_tadisridhar_ram : yeah , midcycle meetup helped the team to understand roadmap16:57
sridhar_ramdkushwaha: I didn't hear any consensus ..16:57
*** mageshgv has quit IRC16:57
*** aarefiev_ is now known as aarefiev16:58
*** baumann has quit IRC16:58
sridhar_ramlet's not change until  the newton release deadline is over..16:58
sridhar_ramanyone violently disagree with ^^^ ?16:58
*** baumann has joined #openstack-meeting16:58
*** baoli has joined #openstack-meeting16:59
sridhar_ramwe could move this meeting 2 hrs earlier .. 1400 UTC.. that was the something we discussed16:59
*** yamamoto has joined #openstack-meeting16:59
*** adiantum has quit IRC17:00
sridhar_rami can put a doodle pool to decide a new time..17:00
sridhar_ramwe are also missing gongysh17:00
sridhar_ramtimes up folks17:00
sridhar_ramthanks for joining17:00
*** shaohe_feng has quit IRC17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Tue Aug  9 17:00:25 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-08-09-16.04.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-08-09-16.04.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-08-09-16.04.log.html17:00
*** shaohe_feng has joined #openstack-meeting17:00
*** vishwanathj has quit IRC17:00
*** manikanta_tadi has quit IRC17:00
*** sripriya has left #openstack-meeting17:01
*** xuan_ has quit IRC17:01
mmedvede#startmeeting third-party17:01
openstackMeeting started Tue Aug  9 17:01:45 2016 UTC and is due to finish in 60 minutes.  The chair is mmedvede. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: third-party)"17:01
openstackThe meeting name has been set to 'third_party'17:01
mmedvedeanyone is around for third-party CI meeting?17:02
*** gokrokve has quit IRC17:02
*** e0ne has joined #openstack-meeting17:02
*** numan_ has quit IRC17:03
*** yamamoto has quit IRC17:03
*** cknight has left #openstack-meeting17:03
*** BobH_ has joined #openstack-meeting17:04
*** KanagarajM has quit IRC17:04
*** neel has quit IRC17:04
asselinhi, i'm here17:05
*** Swami has joined #openstack-meeting17:05
*** asettle has joined #openstack-meeting17:05
mmedvedehey asselin17:05
*** tung_doan has quit IRC17:05
mmedvedenot too big of a crowd lately17:05
*** dkushwaha has left #openstack-meeting17:05
*** qwebirc78847 has quit IRC17:06
asselinno, but a few updates going on in puppet-openstackci17:06
asselinthere was an incompatibility between zuul and nodepool dependencies reported yesterday and fixed in https://review.openstack.org/#/c/352560/17:07
mmedvedeare you talking about pins?17:07
*** liyifeng has joined #openstack-meeting17:07
*** xiaohhui has joined #openstack-meeting17:08
*** KanagarajM has joined #openstack-meeting17:08
asselinwhen installed on the same system. We don't have tests for this...but this would be caught only at the functional level which we don't really have right now.17:08
*** _nadya_ has quit IRC17:08
*** janki has quit IRC17:09
mmedvedeasselin: this is python package dependency problem, correct?17:09
*** piet_ has quit IRC17:09
asselinmmedvede, yes, for apscheduler>=3.017:10
*** asettle has quit IRC17:10
mmedvedeok, so installing in venv should take care of that too17:10
*** shaohe_feng has quit IRC17:10
mmedvedeit is not like zuul depends on nodepool and vice versa17:10
asselinzuul required < 3.0. so jeblair created a new zuul tag 2.5 yesterday that depends on >=3.017:10
*** ijw has joined #openstack-meeting17:11
asselinmmedvede, yes that's another solution and a good idea actually17:11
*** adiantum has joined #openstack-meeting17:11
asselinhaving each service run in it's own venv, not sure if -infra folks would object to that17:12
mmedvedecreating venv is not that much overhead17:12
*** ihrachys has quit IRC17:12
*** xiaohhui has quit IRC17:12
jeblairwe won't run them in venv on infra production servers17:12
*** shaohe_feng has joined #openstack-meeting17:14
mmedvedejeblair: is it because it adds complexity in debugging?17:14
mmedvedeasselin: maybe can be optional just for all-in-one example somehow17:14
jeblairmmedvede: it's also inconvenient for sysadmins17:14
jeblairat any rate, the components should have compatible requirements, so i think we did the right fix this time17:15
asselinmmedvede, either way it would require updating the individual puppet-<service> modules to optionally running in a venv.17:15
*** numan_ has joined #openstack-meeting17:15
mmedvederight, might not be worth it17:16
*** piet_ has joined #openstack-meeting17:16
*** mrmartin has joined #openstack-meeting17:16
asselinok, so as long as there are compatible tags of the tools working together in a single node, I'm fine with the current approach17:17
jeblairthe 2.5.0 tag for zuul also includes *a lot* of bugfixes, btw17:17
mmedvedeasselin: do you have an idea how many third-party CIs run all-in-one, as opposed to similar to infra team's architecture?17:17
asselinmmedvede, my guess is the majority of them...at least for cinder folks17:17
*** ijw has quit IRC17:18
asselinjeblair, thanks again for creating the zuul tag.17:18
*** asettle has joined #openstack-meeting17:19
mmedvedejeblair: +1, I upgraded to 2.5.0 recently, and it runs better so far. I have noticed memory footprint looks better.17:19
asselinI personally prefer keeping tags for all 3rd party ci folks. They have enough stability/maintenance problems as is.17:19
jeblairyeah, we were holding off on tagging that until the known memory leak cleared up, which it seems to have done17:19
*** epcim has quit IRC17:19
*** e0ne has quit IRC17:19
*** shaohe_feng has quit IRC17:20
*** shaohe_feng has joined #openstack-meeting17:21
mmedvedethank you for that17:21
*** dasanind_ has quit IRC17:21
*** vishwanathj has joined #openstack-meeting17:21
jeblairnp :)17:21
mmedvedeworth it, would upgrade again :)17:22
*** armax has quit IRC17:22
*** karthikp_ has quit IRC17:22
*** asettle has quit IRC17:23
*** e0ne has joined #openstack-meeting17:23
*** KanagarajM has quit IRC17:23
*** Na3iL has quit IRC17:23
*** roxanaghe has joined #openstack-meeting17:23
mmedvedeshould probably set the topic, as there are no set items on agenda17:23
mmedvede#topic Open Discussion17:23
*** openstack changes topic to "Open Discussion (Meeting topic: third-party)"17:23
*** obondarev has quit IRC17:24
*** gagehugo has joined #openstack-meeting17:24
*** Swami has quit IRC17:25
mmedvedeasselin: it seems there are either less problems in CIs, or people do not know about the meetings :)17:25
mmedvedeI hope it is the former17:25
*** e0ne has quit IRC17:25
asselinI think there are less problems :)17:25
mmedvedecommon CI definitely helps with that17:26
*** SumitNaiksatam has joined #openstack-meeting17:26
mmedvedethanks for watching that area17:26
asselin\0/ glad to hear it :)17:26
*** dasanind_ has joined #openstack-meeting17:26
*** ijw has joined #openstack-meeting17:27
*** natarajk has joined #openstack-meeting17:28
mmedvedeif there is nothing else to discuss, one fyi for today:17:28
mmedvededevstack has been switched to use neutron by default17:28
*** tonytan4ever has quit IRC17:28
mmedvede#link https://review.openstack.org/#/c/350750/17:28
*** prateek has joined #openstack-meeting17:28
mmedvedeI did not notice any side effects in our nova CI, but have seen problems in ironic third-party CIs, that might have been related17:29
*** lblanchard has quit IRC17:29
*** Patifa has joined #openstack-meeting17:30
*** armax has joined #openstack-meeting17:30
*** weshay has quit IRC17:30
mmedvedeany objections to closing the meeting?17:30
asselinnone from me17:30
*** lblanchard has joined #openstack-meeting17:30
*** zul_ has quit IRC17:30
*** shaohe_feng has quit IRC17:31
*** nishaYadav has joined #openstack-meeting17:31
*** HeOS has quit IRC17:31
*** shaohe_feng has joined #openstack-meeting17:32
mmedvedethanks for attending17:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:32
openstackMeeting ended Tue Aug  9 17:32:30 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-08-09-17.01.html17:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-08-09-17.01.txt17:32
*** dprince has joined #openstack-meeting17:32
*** asettle has joined #openstack-meeting17:32
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-08-09-17.01.log.html17:32
*** adiantum has quit IRC17:32
*** zul has joined #openstack-meeting17:34
*** JoseMello has joined #openstack-meeting17:35
*** rossella_s has quit IRC17:36
*** dasanind_ has quit IRC17:37
*** asettle has quit IRC17:38
*** spotz_zzz is now known as spotz17:39
*** Swami has joined #openstack-meeting17:39
*** ivyyy is now known as ivyyyy-brb17:40
*** zul has quit IRC17:40
*** Swami has quit IRC17:40
*** Swami has joined #openstack-meeting17:41
*** shaohe_feng has quit IRC17:41
*** Sukhdev has joined #openstack-meeting17:41
*** shaohe_feng has joined #openstack-meeting17:42
*** yamahata has quit IRC17:42
*** pcaruana has joined #openstack-meeting17:44
*** Swami has quit IRC17:46
*** weshay has joined #openstack-meeting17:46
*** asettle has joined #openstack-meeting17:46
*** Swami has joined #openstack-meeting17:47
*** knikolla has joined #openstack-meeting17:48
*** sindhu has joined #openstack-meeting17:49
*** pabelanger has joined #openstack-meeting17:50
*** raildo has joined #openstack-meeting17:50
*** dasanind_ has joined #openstack-meeting17:51
*** KanagarajM has joined #openstack-meeting17:51
*** baumann_ has joined #openstack-meeting17:51
*** baumann_ has joined #openstack-meeting17:51
*** mikelk has joined #openstack-meeting17:51
*** asettle has quit IRC17:51
*** shaohe_feng has quit IRC17:51
*** shaohe_feng has joined #openstack-meeting17:52
*** zul has joined #openstack-meeting17:52
*** baumann has quit IRC17:53
*** ezpz has joined #openstack-meeting17:53
*** natarajk has left #openstack-meeting17:53
*** mikelk has quit IRC17:54
*** amakarov has joined #openstack-meeting17:56
*** e0ne has joined #openstack-meeting17:56
*** dasanind_ has quit IRC17:58
*** Shrews has joined #openstack-meeting17:59
*** galstrom is now known as galstrom_zzz17:59
*** bethwhite_ has joined #openstack-meeting17:59
*** asettle has joined #openstack-meeting17:59
*** LamT_ has joined #openstack-meeting18:00
stevemarayoung: o/18:00
dolphmajayaa, 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, xek: https://etherpad.openstack.org/p/keystone-weekly18:00
dolphm* https://etherpad.openstack.org/p/keystone-weekly-meeting18:00
stevemardolphm: copy paste fail18:00
amakarovhi all18:01
jaugustineo/ \o18:01
stevemar /o\18:01
dolphmstevemar: sounds like you're available to run the meeting? :D18:01
*** bethwhite_ has left #openstack-meeting18:01
*** galstrom_zzz is now known as galstrom18:01
dolphmstevemar: i thought you were supposed to be eating steak with topol right about now18:01
stevemardolphm: nah i'm at openstackSV, at the keynotes -- not as cool as keystones18:01
bknudsonI thought stevemar was conferencing18:01
ayoungezpz, wrong hand18:01
*** shaohe_feng has quit IRC18:01
stevemari randomly had 5 minutes to log on18:02
*** lpetrut has joined #openstack-meeting18:02
stevemardolphm: take it away!18:02
dolphm#startmeeting keystone18:02
openstackMeeting started Tue Aug  9 18:02:22 2016 UTC and is due to finish in 60 minutes.  The chair is dolphm. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: keystone)"18:02
openstackThe meeting name has been set to 'keystone'18:02
stevemardolphm: you remember how to run the meeting?18:02
*** KanagarajM has quit IRC18:02
bknudsonjust like old times.18:02
*** shaohe_feng has joined #openstack-meeting18:02
stevemarbknudson: #bettertimes18:02
ayoungmaybe  <o18:02
*** pvaneck has joined #openstack-meeting18:02
dolphm#topic Scheduley bits18:03
*** openstack changes topic to "Scheduley bits (Meeting topic: keystone)"18:03
*** pabelanger has left #openstack-meeting18:03
bknudsontrump will bring back the good old days.18:03
dolphm#info August 22-26 is final release for non-client libs18:03
henrynash(3 minutes in...and first Trump reference already..)18:03
dolphm#info Newton-3 deadline is August ~2918:03
dstanek"Let's make keystone great again"18:03
samueldmqhi all18:04
stevemardolphm: i think the client libraries freeze the same time as the server side18:04
stevemarthe non-client libs (keystoneauth and keystonemiddleware) freeze a week before18:04
bknudsondo we get to choose when our libs freeze?18:04
stevemarbknudson: nope!18:04
*** asettle has quit IRC18:04
dolphm#link http://releases.openstack.org/newton/schedule.html18:04
dolphmnon-client libs freeze a week early to help ease requirements management at the end of the release18:05
*** asettle has joined #openstack-meeting18:05
*** tonytan4ever has joined #openstack-meeting18:05
*** electrofelix has quit IRC18:05
dolphm#topic Let's make HMT great again: support for delete and update18:05
*** openstack changes topic to "Let's make HMT great again: support for delete and update (Meeting topic: keystone)"18:05
*** thorst_ has joined #openstack-meeting18:05
*** piet_ has quit IRC18:05
dolphm#link https://blueprints.launchpad.net/keystone/+spec/project-tree-deletion18:05
dolphmDelete patch: https://review.openstack.org/#/c/244248/ (abandoned)18:05
notmorgani might be lurking tody18:05
* rodrigods hides in the corner18:05
dolphmUpdate patch: https://review.openstack.org/#/c/243585/ (abandoned)18:05
dolphmstevemar: have a minute for this one, since your name is on it?18:06
stevemardolphm: sure18:06
*** rgoodwin has joined #openstack-meeting18:06
stevemarso, we implemented all this stuff in the controller and manager and backend18:06
stevemarand we don't have an API that can hit it18:06
stevemarso... kinda pointless right now18:06
rderose_Revert it all!18:06
amakarovdolphm, is my patch https://review.openstack.org/#/c/285521/ somewhere on the schedule?18:07
rodrigodsmajor issue is because in the HMT design, a project isn't owner of its subtree18:07
dolphmamakarov: no? but feel free to add it https://etherpad.openstack.org/p/keystone-weekly-meeting18:07
gyeesee, see, rderose_ said it18:07
*** Apoorva has joined #openstack-meeting18:07
stevemarso yeah, as rodrigods said, there were issues around policy and what it should look like for deleting / updating a tree of projects18:07
dolphmrodrigods: so the implementation is not ready to be exposed to the API?18:08
stevemari'm only half joking when i say revert it all18:08
dstanekstevemar: --18:08
*** obondarev has joined #openstack-meeting18:08
rodrigodsdolphm, looks like it is impossible to implement it cleany18:08
*** browne has joined #openstack-meeting18:08
samueldmqis there a REAL use case for it ?18:08
stevemarmy argument is that no one has pushed for it in months, so do we really need it?18:08
rodrigodssamueldmq, sure18:08
gyeestevemar, trump was half-joking when he accept the nomination too18:08
notmorganrderose_: revert allof HMT! /snark, (sorry)18:08
henrynashI think part of the problem was a lack of clarity on the conceptual meaning ....i..e is delete/update tree a single command policied in its own right...or is it shorthand for issue update/delete on every node in the tree and teh regular policy  applies to each one?18:09
dstanekrodrigods: so what can we do here?18:09
stevemari'm trying to encourage anyone to pick this up and finish it :)18:09
lbragstadhenrynash isn't that the cascade feature?18:09
stevemarlbragstad: yep18:09
rodrigodsdstanek, think henrynash can be more precise about the issues since he made further investigations on it18:09
samueldmqhenrynash: yes, because there is no way to specify that in the current policies18:10
notmorganupdating a whole tree is potentially scary (tm)18:10
stevemaranyway, i didn't expect a solution to come out of this, just a PSA18:10
henrynashlbragstad: yes, you could argue that this is expanding teh cascade capability to full delete/update (not just the enabled flag which is all you can do with it today)18:10
rodrigodsnotmorgan, the update is to disable, that is required for deletion18:10
notmorganand/or deleting because of our lack of "soft delete"18:10
stevemari was cleaning old BPs and this one keeps getting bumped18:10
samueldmqanyone picking this up ?18:10
dstanekwhat does 'update a tree' actually mean?18:10
rodrigodsdstanek, disable it18:11
henrynashI'm happ to pick it up, just not sure whether can do this for Newton18:11
stevemardstanek: only 'enabled' is allowed to be updated18:11
dolphmhenrynash: why does a disable have to cascade to take effect?18:11
bknudsonwhat happens if nobody picks it up?18:11
notmorgandstanek: specifically a disable18:11
*** e0ne has quit IRC18:11
stevemarbknudson: revert it all! <joking>18:11
notmorganthat cascades18:11
dstanekrodrigods: do you have to explicitly disable all child nodes then?18:11
notmorganbknudson: since no public api... it could be removed?18:11
dolphmhenrynash: if any of a project's parents are disabled, the project is disabled, and amakarov's table should make that check trivial18:11
notmorgandstanek: today iirc yes.18:11
rodrigodsdstanek, for the current design, yes18:11
dstaneksounds like we need to fix the glitch then18:11
bknudsonok, just checking there's no huge bug if we don't do something.18:11
henrynashdolphm: I was just describing what the current cascade does....18:12
*** shaohe_feng has quit IRC18:12
notmorgandstanek: explicit disable. it still preventx login so security is fine, just a cascade delete cannot occur w/o everything disabled as i understand it18:12
dolphmhenrynash: right18:12
*** toddjohn has quit IRC18:12
dolphmrodrigods: it sounds like the problem is with checking the enabled/disabled state of a child (which is a read query), not with "cascading" a write to a bunch of rows in the db18:12
notmorgandolphm: correct. a cascade write would be absurd18:12
*** shaohe_feng has joined #openstack-meeting18:13
notmorganand shouldn't be a thing we do.18:13
*** toddjohn has joined #openstack-meeting18:13
stevemarbknudson: we just end up with lots of ugly branches in our code :(18:13
rodrigodsbut... as of today18:13
notmorgandoing the "is any of my parents disabled" check should be what is done.18:13
rodrigodswe check if everyone is disabled18:13
*** toddjohn has quit IRC18:13
samueldmqI think the code is in18:13
*** toddjohn has joined #openstack-meeting18:14
notmorganthis is a QOL change for operators/users imo18:14
samueldmqwe just don't know how to expose that in the policies18:14
stevemarnotmorgan: you are hardly lurking :)18:14
dolphmsamueldmq: the perceived "enabled" state of a project is just whether a project AND all of it's parent's are enabled18:14
ayoungsamueldmq, policy is kindof all or nothing.  It should check to see if you can do the operation based on a role, but dealing with hierarchy is kindof beyond scope18:14
*** MeganR has joined #openstack-meeting18:14
stevemardolphm: so yeah, just a PSA, didn't expect an outcome here18:14
notmorganstevemar: i can go away again, i just was dropping in to voice the "this should be safe from a security standpoint" view.18:15
dolphmnotmorgan: thanks :)18:15
stevemarnotmorgan: we love having you around :)18:15
dolphmnotmorgan: not for the going away again bit, though18:15
notmorgandolphm: lol18:15
ayoungthe part that should be checked is the applicability of the token used to request the operation to each of the node18:15
henrynashstevemar: Happy to get this assigned to me to go think about it ad come back with a spec (or not) for Ocata18:15
ayoungnodes to be dleted that is18:15
rodrigodsayoung, right18:15
rodrigodscheck auth in the whole tree18:15
ayoungand what do we say if the scoped does not match...probably deny18:15
stevemarhenrynash: i'd be ok with that18:15
samueldmqdolphm: that made me think in something ... if a parent is disabled, shouldn't its children be disabled too (by consequence) ?18:16
dolphmnotmorgan: /nick notnotmorgan ?18:16
samueldmqanyways, we don't do that today18:16
dolphmsamueldmq: correct18:16
rodrigodssamueldmq, that's the point18:16
rodrigodswe don't do that today18:16
ayoungsamueldmq, yes they should18:16
samueldmqand we can't18:16
samueldmqbecause backwards comapt18:16
samueldmqand that would disable auth18:16
dolphmsamueldmq: i wouldn't not consider it to be backwards incompatible to fix that behavior18:16
rodrigodsdon't think changing that breaks the API18:16
dolphmsamueldmq: great!18:16
samueldmqcan taht be considered a securit issue then we fix ?18:17
notmorganayoung: uhm. wouldn't the owner of the top of the tree be allowed to delete even if they don't own down the tree?18:17
dolphmit's not an API change so much as a change in the API's behavior18:17
notmorganjust thinking through the usabilityu18:17
*** cdnchris has quit IRC18:17
notmorganbut traversing up the tree no.18:17
*** karthikp_ has joined #openstack-meeting18:17
dolphmnotmorgan: right18:17
rodrigodsthe API remains the same, the internal representation that changes18:17
ayoungnotmorgan, I was just thinking about that.  I need to see what a Linux system does if you try that with a FS18:17
rodrigodsalthough, every GET project needs to look at the parents18:17
notmorganayoung: depends on the FS iirc.18:17
rodrigodsto check if someone is disabled18:17
samueldmqdolphm: ayoung: cool so we can technically fixthat18:17
stevemari'm excited to get to the rolling upgrade topic :)18:18
dolphmit sounds like we have some consensus on the topic to move forward then?18:18
rodrigodshenrynash will pick it up?18:18
samueldmqhenrynash: picking it up?18:18
dolphmrodrigods: well played18:18
*** dslevin has joined #openstack-meeting18:18
samueldmqhenrynash: thanks18:18
rodrigodshenrynash, o/18:18
notmorganayoung: http://paste.openstack.org/show/552606/18:19
notmorganayoung: now. iirc you can delete files just not directory inodes.18:19
dolphm#topic Let's make HTTP status code documentation and descriptions great again18:19
dolphmlbragstad: o/18:19
*** openstack changes topic to "Let's make HTTP status code documentation and descriptions great again (Meeting topic: keystone)"18:19
dolphm"The docs team wants to provide a template that we can add to our docs that gives some information regarding HTTP status codes along with formal and informal descriptions of what they mean."18:19
dolphm#link https://review.openstack.org/#/c/349551/18:19
lbragstadsome projects have already started18:19
ayoungnotmorgan, so, to a directory, anything inside it is a dentry, whether file or subdir18:19
dolphm"Thoughts about the documentation and additional descriptions? Should we organize an API sprint to knock this out?"18:20
lbragstadI'll take feed back to the next docs meeting18:20
notmorganayoung: yes18:20
ayoungso if I don't have perms to delete a subdir, I can't remove the dir18:20
ayoungso if I have  x/y/z18:20
notmorganayoung: http://paste.openstack.org/show/552608/18:20
ayoungand I don't have permissions to delete y, the tree is protected18:20
notmorganayoung: exactly.for POSIX, non-POSIX... lets just pretend we on't care here18:21
*** obondarev has quit IRC18:21
bknudsonfor keystone, each operation might have a different meaning for each status code.18:21
gagehugolbragstad: seems like it would look nicer than what it currently is18:21
lbragstadbknudson yeah - that's the tough part18:21
notmorganbknudson: also we have duplicated use of status18:21
lbragstadthere are a lot of things that can represent a 40118:21
notmorganbasically the answer should be an "error code" with the status18:21
notmorganwhere we can provide it for security reasons18:21
dolphmlbragstad: it sounds like this is a reverse of the normal API documentation structure, which is "here's an API request, and the possible status codes that could result from it"18:21
ayoungso...on cascading delete, we are doing something like rm -rf   proj18:21
*** cody-somerville has joined #openstack-meeting18:22
*** cody-somerville has quit IRC18:22
*** cody-somerville has joined #openstack-meeting18:22
lbragstadfor example - see https://review.openstack.org/#/c/349551/1/api-ref/source/v2/http-codes.yaml18:22
*** obondarev has joined #openstack-meeting18:22
bknudsonalso, we can have a single status code that has multiple reasons.18:22
notmorganbut we should at least clearly say status possible from API X is Y,Z,Q18:22
* ayoung just realized we moved on18:22
*** shaohe_feng has quit IRC18:22
notmorganayoung: yeah sorry, just wanted to hand you the infos for further digesting down the line. :)18:22
stevemarno one stops the ayoung train18:22
ayoungcan we say "you need role R to perform this operatoin?"18:22
amakarovI'd be happy if I can find out where exactly was decided to raise 401 basing on status code in non-debug mode18:22
samueldmqbknudson: ++18:22
* stevemar runs off18:23
samueldmqbknudson: and maybe generalizing isn't the ideal18:23
stevemarthanks dolphm18:23
*** nisha_ has joined #openstack-meeting18:23
notmorganamakarov: so, 90% of the cases a 401 cannot give much more info18:23
samueldmqwhy not define the status codes in each API ? as they may mean something different18:23
bknudsonthe status codes already have meanings defined by the HTTP standard.18:23
notmorganbecause we're leaking auth related data to the user then (not auth info itself, auth related)18:23
dolphmthere's a table of authentication errors by status code and their reasonings here http://developer.openstack.org/api-ref/identity/v3/index.html#authentication-and-token-management18:24
*** csomerville has quit IRC18:24
notmorganwe would need to restructure our exceptions to directly obscure the auth data.18:24
amakarovnotmorgan, ++18:24
notmorganauth-related data18:24
bknudson^ link to the old table of status codes18:24
lbragstadone thing the docs folks wanted was to see if the projects would be interested in this and they would provide us with a template to fill out18:24
bknudson"Normal response codes: 201 Error response codes: 413,415,405,404,403,401,400,503,409" -- not useful!18:24
ayoungthe tricky thing we do that messes some poeple up is return 404 when we don't want people to know the resource is there but they don't have access18:24
lbragstadcc annegentle was driving that template effort18:25
bknudsona random string of numbers.18:25
*** shaohe_feng has joined #openstack-meeting18:25
bknudsonshould have put "Sad!"18:25
notmorganso, i would recommend 1 of two things.18:25
*** acoles is now known as acoles_18:25
notmorganayoung: i am not a teapot18:25
ayoungnotmorgan, I never said "you" were18:26
ayoung418 says "I" am teapot.18:26
dolphmthis seems like it's not super useful for a data-driven API, which is most of our API beyond auth18:26
notmorganeither we restructure our execptions18:26
notmorganso we don't pass data back.18:26
notmorganif this is something worth changing18:26
*** vishnoianil has quit IRC18:26
notmorganor we add some level of "error code" that can communicate more data to the end user18:26
*** nishaYadav has quit IRC18:26
notmorganbut not leak important things like "does X exist, or do you not have any access"18:27
amakarovnotmorgan, it will ease problem solving18:27
samueldmqlooks like it's orthogonal to whether define the status code or not ?18:27
ayoungwhat I would like to see is that, if someone calls an API, but does not have any roles on their token, they get back a 401 with a list of roles that would be required18:27
*** prateek_ has joined #openstack-meeting18:27
bknudsonbtw, these docs are looking good. Room for improvement like everything, but there has been improvement18:27
*** Jeffreyc42 has quit IRC18:27
samueldmqI see lbragstad as 'define status codes in a single place, in the same way other projects are doing' (which is this topic)18:27
ayoungsomething like a token with scope but no roles...not a pure unscoped token ,as that is a security thing....18:27
bknudsonwe already have securityexception to indicate to hide the details from the user.18:28
dolphmcan we keep the discussion on the documentation issue?18:28
ayoungLet the user then request a token with the appropriate scope, if they like the risk18:28
samueldmqdolphm: ++18:28
ayoungdolphm, is this purely a documentaion question?  Did not realize.  I thought it was about actually changethe responses18:28
notmorganthe doc change is less useful when hitting the auth wall18:28
samueldmqlbragstad: I'd say that's nice to have, just get what we had already from the docs dolphm and bknudson linked above18:28
notmorgansince everything is 401ish18:28
lbragstadI mainly wanted to bring it up here to see what people though  - anne was interested in getting a template rolling18:29
notmorganotherwise the doc change is useful18:29
* ayoung though descriptions meant the message we passed back in the response. Understand better now18:29
dolphmi'm personally skeptical of the value of this, especially for us, because it doesn't match the workflow that i'd be following if i were utilizing API docs for the first time (i'd be looking at the operation first, then the status code i'm getting -- not the other way around)18:29
lbragstadi can go back to the doc meeting and asking for more information about the intended audience18:29
bknudsonis the ask just do we want a summary of how we generally use return codes?18:29
bknudsonor how to make something like "Normal response codes: 201 Error response codes: 413,415,405,404,403,401,400,503,409" actually useful?18:29
dolphmlbragstad: that's basically here http://developer.openstack.org/api-ref/identity/v3/index.html#authentication-and-token-management18:29
lbragstaddolphm i see18:30
*** prateek has quit IRC18:30
dolphmfor auth, anyway18:30
lbragstaddolphm sure18:30
samueldmqdolphm: yes, having the status code described in the api description itself is more meaninigful to me18:30
dstanekbknudson: that's what i don't quite understand18:30
dolphmwhich is our only "interesting" use of status codes?18:30
samueldmqas the API (arguments, etc) would be all in one spot18:30
dstanekwho is to use this, how and why?18:30
dolphmsamueldmq: that's a better way to describe it18:30
bknudsonany application writer wants to know this information!18:30
bknudsondeployers want to know why something failed18:30
ayoungI suspect the goal is to keep the meaning of response codes consistent across the services, but having a single doc to start with18:31
bknudsonand currently we don't provide that information.18:31
ayoungof course, we are long past "starting"18:31
lbragstaddstanek yeah - i can bring all this to the next meeting and see if I can clarify it further18:31
amakarovbknudson, as for me if I can determine the code that kicked request out, the problem is solved18:31
bknudsonamakarov: what if the same code means lots of things? like a 400 ?18:31
samueldmqlbragstad: it would be nice to ahve an exceptions.yaml, somehting like parameters.yaml18:31
amakarovwhather it'll be by status code or some magic in status message - doesn't matter18:31
*** bill_az has quit IRC18:32
amakarovbknudson, that's the problem18:32
samueldmqlbragstad: you reference the exceptions in the api description, then they get rendered by getting what is in that file18:32
lbragstadok so18:32
lbragstadthere is a fear of duplication18:32
*** shaohe_feng has quit IRC18:32
lbragstad(duplication of docs)18:32
lbragstadDoes it match the workflow for anyone using this (why would they use this versus the regular API)?18:32
lbragstadDoes this make sense for a data-driven API?18:32
dstanekdone...you're welcome: http://git.openstack.org/cgit/openstack/api-wg/tree/guidelines/http.rst#n8318:32
dolphm#topic Let's make rolling upgrades great again18:33
*** openstack changes topic to "Let's make rolling upgrades great again (Meeting topic: keystone)"18:33
*** lpetrut has quit IRC18:33
dolphmso, last week after we approved henry's spec for rolling upgrades, I proposed a simplification (hopefully) of the spec18:33
dolphmthis is the spec revision https://review.openstack.org/#/c/351798/18:34
dolphmi also proposed a draft of what our docs would look like for deployers https://review.openstack.org/#/c/350793/18:34
bknudson+154, -149 -- looks more complicated!18:34
ayoungdolphm, any propsal to deal with revocations during that time?18:34
*** ihrachys has joined #openstack-meeting18:35
dolphmand implemented a read-only mode config option to support the spec https://review.openstack.org/#/c/349700/18:35
dolphmayoung: yes - in that you can't disable or delete anything anyway, so no need to revoke anything ;)18:35
*** shaohe_feng has joined #openstack-meeting18:35
*** obondarev has quit IRC18:35
henrynashso I have a number of questions/concerns about this:18:36
ayoungdolphm, um..you do see thefallacy there, right?18:36
ayoungYou are, I assume, just joking.18:36
gyeecan't list ldap users either as we can't external IDs18:36
henrynash1) Obviously it is different to what other services are doing18:36
*** toddjohn has quit IRC18:36
gyeecan't issue tokens and shadow users18:36
dolphmthe tl;dr of the change is that i cut out a few commands from henry's spec for managing metadata about the state of the rolling upgrade, added a read-only mode to protect the live migration process and the application from stomping on each other (which also prevents us from having to write code to handle multiple states of the DB in a single release)18:36
henrynash2) It isn't clear to me that a RO mode will suit everyone (and of course certainly not anyon on UUID tkes)18:36
dolphmgyee: you can issue Fernet tokens of course, but not UUID/etc tokens18:37
*** toddjohn has joined #openstack-meeting18:37
gyeedolphm, what about shadowing?18:37
henrynash3) Minor concern over use of config variable, since it means keystone comes up, by default, as RO (on a clean install)18:37
dolphmgyee: there's certainly a constraint there, but my assumption is that if you're pursuing rolling upgrades, you're probably already on board with Fernet (if that's a bad assumption, i'd love to hear feedback)18:37
dolphmgyee: it'd be blocked :(18:37
henrynash(but you could get round that with a database variable instead)18:37
rderose_gyee: you wouldn't be able to onboard new users during the upgrade18:37
dolphmgyee: no writes to the db during the data migration process at all18:37
gyeedolphm, rderose_, yeah that make sense18:38
*** eharney has quit IRC18:38
dolphmhenrynash: (1) is my biggest concern, but i'd also wager that no other project other than maybe glance would remain particularly useful during a read-only mode18:38
*** toddjohn has quit IRC18:38
dolphmglance can still serve images, for example18:38
*** eharney has joined #openstack-meeting18:39
*** toddjohn has joined #openstack-meeting18:39
dolphm(during a rolling upgrade of a similar nature to glance)18:39
gyeenow rolling upgrade on a mult-site datacenter will be even more fun :-)18:39
dolphmso, during a rolling upgrade of keystone, you'd suffer a "partial service outage", wherein you can't onboard new users (including shadowing), manage authz, tweak your service catalog, etc, but you'd be able to create and validate tokens all day18:40
bknudsonI hope it doesn't take all day18:40
*** links has quit IRC18:40
dolphmgyee: the duration of read-only mode becomes the concern in that case -- the more nodes you're upgrading, the more time you're likely spending in read-only mode18:40
ayoungdolphm, can we store revoations in a flat file, and run them all post upgrade?18:40
dolphmbknudson: i hope not too :)18:40
dstanekalso PCI things would be off during that time. e.g. no recording failed auths18:41
dolphmbknudson: in reality, you're not upgrading one node at a time, but groups of nodes at once18:41
bknudsonit would be interesting to see some kind of timing on this, since it's something we've had to guess on.18:41
*** david-lyle has quit IRC18:41
rderose_dstanek: correct18:41
*** thorst_ has quit IRC18:41
bknudsonI have no idea if the read-only period is 5 mins or 5 days.18:41
henrynashdolphm: so it's probably worth perhaps you giving the reasons why you feel the current spec isn't teh right way to go18:41
* ayoung wonders if we should be backing revocations to a KVS anyway18:41
bknudsonwe should be backing all keystone data to a kvs.18:42
dolphmayoung: you can always write to the db yourself? keystone-manage revoke-things-manually18:42
*** david-lyle has joined #openstack-meeting18:42
*** SumitNaiksatam has quit IRC18:42
ayoungdolphm, nah, I am thinking of all the Horizon log-outs18:42
gyeeanyone gone through multi-site upgrade so far, I presume there's a step to redo the replication after the upgrade?18:42
lbragstadraw sql for the win18:42
*** mickeys has quit IRC18:42
*** shaohe_feng has quit IRC18:42
dolphmayoung: good point18:43
dstanekgyee: what replication?18:43
bknudsondoes the server return some http status?18:43
bknudsonwhen it's read-only18:43
henrynashas far as I am concerned we have a perfectly good solution right now agreed...albeit with more steps required (which of course means more possibiliy of operater error)18:43
*** shaohe_feng has joined #openstack-meeting18:43
gyeedstanek, like replicating data between sites?18:43
dolphmbknudson: yes, 503 on POST and PATCH, for example18:43
lbragstadgyee are you thinking part of the deployment is in read-only?18:43
lbragstadand the other part isn't?18:43
dstanekgyee: in RO mode everything is RO until the upgrade is completed18:44
*** sneti has quit IRC18:44
lbragstaddstanek ++18:44
lbragstaddstanek thats how I understand it18:44
dolphmbknudson: new exception is implemented here https://review.openstack.org/#/c/349700/3/keystone/exception.py18:44
gyeedstanek, right, but we'll have to configure to replace any new tables don't we18:44
*** alpha_ori has quit IRC18:44
bknudsonmakes sense. I'll not that we already see 503 errors (from proxy server)18:44
dolphmgyee: i don't understand18:44
*** sneti_ has quit IRC18:45
lbragstadgyee no we just not allowing writes through keystone18:45
dolphmbknudson: yeah, this would be the first 503 from keystone itself18:45
lbragstadgyee the upgrade will still write to the database18:45
gyeedolphm, you want to upgrade all the sites, then turn replication back on right?18:45
lbragstadgyee which will replicate like it normally would18:45
dolphmlbragstad: the database itself is not read-only, it's the keystone service that is rejecting write requests18:46
gyeeincluding the new tables and tables we don't want to replicate18:46
dolphmgyee: *^18:46
lbragstadgyee what dolphm said18:46
dolphmgyee: what tables don't you want to replicate? why do they exist18:46
henrynashdolphm: what about my question of how the RO mode is achiveed...si this by code in keystone itself? If so, would this change only be execuatable for Newton->Ocata18:46
notmorgandon't table creates get replicated?18:46
dolphmhenrynash: yes, it's literally this one liner https://review.openstack.org/#/c/349700/3/keystone/common/sql/core.py,unified18:47
lbragstadhenrynash read-only meaning keystone will reject requests to write to the database18:47
notmorganin standard replication models?18:47
lbragstadnotmorgan yeah18:47
dolphmhenrynash: any driver trying to open a write session with respond to http requests with a 503 instead18:47
notmorganwhy are we... i 'm not sure what the issue here is18:47
henrynashdolphm: so that means we can't use it to roll upgrades from Mitaka to Newton18:47
notmorganhenrynash: that is already the case.18:47
lbragstadwe're not flipping any specific database bits to make this read only18:47
*** mrmartin has quit IRC18:47
henrynashnotmorgan: ?18:48
notmorganhenrynash: mitaka => Newton is not rolling upgrade iirc, wouldn't the base be newton to -> o?18:48
notmorgansince support is landing in n?18:48
dolphmhenrynash: and L129 documents a workaround for Mitaka->Newton https://review.openstack.org/#/c/350793/2/doc/source/upgrading.rst18:48
henrynashnotmotgan: yes it is18:48
*** sindhu has quit IRC18:48
henrynashnotmorgan: that's what we agreed in the spec at the midcycle18:48
henrynashand that's what is already up for review18:48
dolphmnotmorgan: yeah, good support will be newton to O18:49
notmorgandolphm: ok :)18:49
dolphmbut in my head, this is possible with some extra effort for mitaka -> newton upgrades if you really wanted to18:49
*** saju_m has joined #openstack-meeting18:49
*** pabelanger has joined #openstack-meeting18:50
henrynashso although I'm always up for simplification, I don't see why we should move away from a commitment of a full RW rolling upgrade....18:50
*** alpha_ori has joined #openstack-meeting18:50
*** sneti has joined #openstack-meeting18:50
*** rcernin has joined #openstack-meeting18:51
*** fnaval has quit IRC18:51
*** andymaier has joined #openstack-meeting18:51
dolphmhenrynash: no other project has successfully delivered on true rolling upgrades yet - i'm skeptical that we're going to be able to achieve it in a single release without serious race conditions and other unexpected bugs related to the complexity of the required implementations18:52
dolphmwhen we have the testing in place to assert that we're doing things correctly and safely (or to show that we're doing it wrong), i'll feel much more comfortable pursuing more complicated implementations18:53
*** shaohe_feng has quit IRC18:53
gyeeyeah, lets give it a try, experimental18:53
*** nishaYadav has joined #openstack-meeting18:53
*** tr3buchet is now known as harry18:53
dolphmgyee: i can't stomach the idea of treating upgrades as "experimental"18:53
rderose_I think the difficult part, is that the code has to behave differently based on the deployment phase, read/write to old and new columns for example.  Whereas with read-only strategy, it's much simpler in that respect.18:53
henrynashgiven that in Newton we are doing all the migrartion in one go in the expand phase, I think this lowers our risk18:53
*** shaohe_feng has joined #openstack-meeting18:53
*** harry is now known as tr3buchet18:53
bknudsonif we implement the read-only upgrade, does that block moving to the full r-w upgrade?18:54
dolphmgyee: almost ANY bug during an upgrade is treated as critical18:54
notmorgandolphm: ++18:54
rderose_bknudson: I don't think so18:54
henrynashbknudson: not technically...although the guidance from the offsite was have the same commands as the zero-downtime rolling upgrade approach,18:54
gyeedolphm, yeah, but we guarantee this going to work?18:55
lbragstadbknudson not that I am aware of - a RO upgrade is a little more restrictive and a few less cases18:55
*** myoung|alt has joined #openstack-meeting18:55
dolphmbknudson: no; because we can relax the requirement for read-only mode later, and introduce new commands for more granular steps in the ugprade process later18:55
rderose_gyee: oh yeah, 100% guaranteed :)18:55
*** myoung has quit IRC18:55
gyeealllrighty then18:55
dolphmbknudson: the basic expand -> migrate -> contract pattern would still hold18:55
*** sindhu has joined #openstack-meeting18:55
*** myoung|alt is now known as myoung18:55
lbragstada lot of the complexity comes from the write-side of the problem18:56
dolphmall / most *18:56
ayoung4 minutes left18:56
dolphmayoung: thanks18:56
*** nisha_ has quit IRC18:56
*** gagehugo has left #openstack-meeting18:56
henrynashlbragstad: which we are not doing in N anyway...we are doing the migration in one go....18:56
*** maishsk has joined #openstack-meeting18:56
*** armax has quit IRC18:57
lbragstadhenrynash but we don't claim any upgrade support currently, right?18:58
dolphmhenrynash: i absolutely want to get to a full R/W capable upgrade, but this feels like a safe step in the correct direction for the next release or two, until we get some experience operating and testing minimal/zero downtime upgrades as a broader community18:58
henrynashlbragdatad: for M->N, yes we will18:58
henrynashlbragstad: we just doing do the migrations piecemeal, on the fly...18:58
*** AJaeger has joined #openstack-meeting18:59
dolphmhenrynash: you mean we can't / aren't going to refactor the migrations we've already landed?18:59
*** toscalix has joined #openstack-meeting18:59
henrynashdolphm: no, but we do repair anything the leave unset18:59
dolphmlet's carry this on in a mailing list discussion?19:00
dolphmi'd be happy to start it19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Aug  9 19:00:34 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
*** dasanind_ has joined #openstack-meeting19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-08-09-18.02.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-08-09-18.02.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-08-09-18.02.log.html19:00
fungiinfra team: assemble!19:00
* mordred hands fungi the conch19:00
* jeblair attaches arms19:00
* mordred found it laying outside19:00
fungi(and i'll form the head)19:01
fungi(until next election, maybe)19:01
mordredfungi: if only we could vote on which body part each of us is going to be ... we need a 2-dimensional CIVS19:01
*** bethwhite_ has joined #openstack-meeting19:01
* mordred should clearly not be the liver19:02
jeblairmordred: just exhaustively list all options?19:02
jeblairmordred: the civs folks will never expect that :)19:02
anteayaha ha ha19:02
mordredjeblair: but what if the top three answers were "fungi | head" , "fungi | arm" , "fungi19:02
anteayamordred: no way do I want you as my liver19:02
mordred| gall bladder"19:02
*** d34dh0r53 is now known as d34dh0r53_24_8919:02
jeblairmordred: the people will have spoken19:02
mordredjeblair: good point19:03
*** shaohe_feng has quit IRC19:03
ianwfungi: i never realised there was a car voltron until recently, i thought it was only cats19:03
* jeblair is *not* going to say brexit during *this week's* meeting!19:03
Zaraoh wait!19:03
*** toscalix has quit IRC19:03
mordredZara: it's ok - the meeting hasn't started for real yet19:03
*** oshidoshi has quit IRC19:04
*** jlanoux has quit IRC19:04
*** toscalix has joined #openstack-meeting19:04
*** shaohe_feng has joined #openstack-meeting19:04
fungitoday's topics brought to you by: zaro, ianw, AJaeger, jpmaxman, Krenair, fungi (if we get all the way through the proposed agenda anyway)19:04
fungi#startmeeting infra19:04
openstackMeeting started Tue Aug  9 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
fungi#topic Announcements19:04
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:04
fungi#info New IRC channel #zuul for discussions on development of Zuul19:04
*** browne has quit IRC19:04
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2016-August/004614.html19:04
fungi#info New IRC channel #openstack-shade for discussions on development of the Shade library19:05
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2016-August/004616.html19:05
fungiapparently the #openstack-infra show has two exciting new spin-offs19:05
fungihopefully these won't be like laverne and shirley19:05
mordredin stereo?19:05
fungiunless maybe it's the lesser known animated laverne and shirley. that might be okay19:05
fungiexcept we hope these channels will last more than one season19:05
anteayaI liked laverne and shirley19:05
jesusaurshould that be #openstack-zuul? or is it just #zuul?19:05
AJaegerjust #zuul19:05
fungijust #zuul, as it's not openstack-specific19:05
anteayalooks like #zuul was created in 200919:05
anteayawhich predates openstack19:06
mordredanteaya: we're really good at time travel19:06
fungizuul gets used far and wide beyond our community borders, so trying to do what we can to avoid making it look like it's openstack-centric19:06
anteayayou are so19:06
*** d34dh0r53_24_89 is now known as d34dh0r53123412319:06
ianwthere is also now #openstack-dib for diskimage-builder which may sometimes be relevant to infra concerns19:06
AJaegerJust as quick announcement - if we need more time, we can discuss later:19:06
AJaegerbindep: We've changed the default file name from other-requirements.txt to bindep.txt and once we have done a new bindep release, I suggest we advocate usage of it more. I plan to send an email to the mailing list about this.19:06
AJaegerconstraints: All tox based jobs can now use constraints in the gate. I'm currently struggling with a translation change (waiting for merge) and still test a bit but plan to send an announcement to the list about this in the next days.19:06
fungiAJaeger: yeah, i left teh bindep one out of announcements for today, we still need a release, image updates...19:07
AJaegerfungi, yeah...19:07
fungiAJaeger: i have your items as meeting topics19:07
fungiso we can discuss19:07
fungi#info Results Presentation: Operator Information Needs19:07
fungiPiet has invited infra team members (at least those okay with proprietary videoconferencing systems) to see a presentation summarizing feedback from operator interviews19:07
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2016-August/004611.html19:07
AJaegerfungi, ok19:07
*** fnaval has joined #openstack-meeting19:07
fungialso the obligatory...19:07
fungi#info Reminder: late-cycle joint Infra/QA get together to be held September 19-21 (CW38) in at SAP offices in Walldorf, DE19:07
fungi#link https://wiki.openstack.org/wiki/Sprints/QAInfraNewtonSprint19:07
fungi#topic Actions from last meeting19:07
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:07
fungi#link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-08-02-19.04.html19:08
fungi"1. (none)"19:08
fungi#topic Specs approval19:08
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:08
fungi#info APPROVED: Pholio Service Installation19:08
fungi#link http://specs.openstack.org/openstack-infra/infra-specs/specs/pholio.html19:08
fungi#topic Priority Efforts: A Task Tracker for OpenStack (zaro)19:08
*** openstack changes topic to "Priority Efforts: A Task Tracker for OpenStack (zaro) (Meeting topic: infra)"19:08
fungizaro: you have some changes linked on the agenda for gerrit 2.11.4 upgrades and its-storyboard fixes, which i approved earlier today19:08
fungineed to discuss anything specific about these?19:08
zaroyes, one more change for its-storyboar #link https://review.openstack.org/#/c/35304619:09
zaroalso for gerrit upgrade.  thanks for approving those.19:09
AJaegerFYI, there are two changes up to fix warnings/errors building specs: 352215 and 35221819:09
zaroi'm going to test the features it bring today.19:09
*** myoung has quit IRC19:09
zaroi'm wondering if we need to schedule an upgrade time/date?19:10
*** myoung has joined #openstack-meeting19:10
zaroi mean to review.o.o19:10
zaroor should i just work with an infra-root to approve and make sure it doesn't fail19:10
fungisounds good. as soon as you're comfortable with the state of review-dev, we should decide on a convenient window (or have you already checked out review-dev at this point?)19:10
zarohave not tested on review-dev yet.19:11
anteayawe are in R-8, feature freeze is R-519:11
fungisince it's a minor update and we don't need to do any offline reindex, we should be able to schedule a brief outage on short notice19:11
zarowill do today but shouldn't take too long19:11
*** toscalix has quit IRC19:11
*** armax has joined #openstack-meeting19:11
*** olaph has joined #openstack-meeting19:11
*** jckasper has quit IRC19:11
* mordred is excited19:12
fungibut yeah, we're ramping up to high volume time for our whole ci, so soon it'll be harder to do much with it19:12
*** ntpttr__ has quit IRC19:12
Zara=D I've tested the storyboard changes on review-dev and they look good19:12
AJaegerIt feels already very high volume ;(19:12
fungizaro: i could help with the upgrade-related restart on this friday if all goes well. just let me know later today and i'll send out a maintenance announcement19:12
anteayaAJaeger: huge backlog at the very least19:12
*** ntpttr__ has joined #openstack-meeting19:12
zarofungi: cool19:13
fungi#topic Switch to chrony (ianw)19:13
*** openstack changes topic to "Switch to chrony (ianw) (Meeting topic: infra)"19:13
fungiianw: there's a novel on the agenda for this topic. care to summarize?19:13
*** shaohe_feng has quit IRC19:13
*** vishnoianil has joined #openstack-meeting19:13
ianwfungi: ntpd has been giving us some issues since we tried to deprecate ntpdate19:13
anteayawho is us?19:14
*** shaohe_feng has joined #openstack-meeting19:14
fungiour (openstack's) ci system19:14
*** andymaier has quit IRC19:14
fungithough it sounds like it primarily hit tripleo19:14
fungior their workers19:14
ianwif i put up changes to switch everything to chronyd, will people have issues with this?19:14
*** kragniz has joined #openstack-meeting19:14
*** andymaier has joined #openstack-meeting19:15
pabelangerI commented on the review, if we are going to do it, we'd need to create puppet-chrony as a drop in replacement for puppetlabs-ntp19:15
ianwit seems chronyd is better suited to our needs than ntpd, as discussed (as noted, at some length) in the attached bug19:15
jeblairwhat about ntpd for servers and chrony for zuul worker nodes?19:15
ianwpabelanger: yep, happy to do that, if we agree to follow that path19:15
fungiianw: my take was that since chrony was what red hat is replacing ntpd with instead of rolling forward to a default ntpd that has deprecated ntpdate, we should switch to chronyd on red hat based platforms19:15
ianwso i just wondered if it's worth keeping two things running in our puppet, etc19:16
jeblair(could be an opportunity to move ntp out of the worker template and into a dib element)19:16
ianwwhy i was proposing a global change19:16
pabelangerjeblair: or ansible?19:16
fungias debian/ubuntu are sticking with ntpd as their default time sync implementation, we continue to use ntpd there19:16
jeblairpabelanger: just so we're really, really, clear -- we are NOT using ansible to build images19:16
jeblairevery week we seem to have a conversation about that19:16
jeblairand this is the last one i'm participating in19:17
pabelangerjeblair: right, but have DIB elements to run ansible (over puppet)19:17
*** toscalix has joined #openstack-meeting19:17
fungipabelanger: which dib elements are running ansible?19:17
jeblairpabelanger: i don't have an opinion on that19:17
*** jckasper has joined #openstack-meeting19:18
pabelangerI'm pulling the topic sideways, but none today19:18
fungii thought we were trying to get configuration management/orchestration services out of our dib elements over time19:18
fungiso that we can avoid having them installed on our images19:18
fungibut yes, different topic19:18
pabelangerI'm happy to talk more about it after the meeting19:19
jeblairianw: anyway, we know that separating long-running server infra from our worker images is something we want to do anyway, so pulling ntp from the worker puppet (but keeping it in server puppet), then doing something to install chrony in the images via an element seems like a good step19:19
fungiso to bring this back around, are we saying switch from ntpdate/ntpd to chronyd on centos and fedora single-use job nodes, but stick with ntp-wait/ntpd on debian and ubuntu? or switch to chronyd on all single-use job nodes regardless of distro?19:19
*** andymaier has quit IRC19:20
jeblairdo we have the same ntp-wait problem on debuntu?19:20
ianwwell i would rather not have two branches of time-keeping logic, so we should choose one or the other19:20
ianwjeblair: in the minutes there is a review where someone is having issues, they are using a snapshot though19:20
fungito my knowledge, the symptom has so far only been observed on centos/fedora dib images booted in tripleo's environment19:21
mordredso, replacing ntpd seems strange to me BUT - if it's a thing we need to do, I tend to fall in favor of doing it everywhere rather than just half of the places19:21
pabelangertripleo-test-cloud-rh2 was a networking issue19:21
*** thorst_ has joined #openstack-meeting19:21
pabelangertripleo-test-cloud-rh1 is actually working today19:21
*** ksantoshk has joined #openstack-meeting19:21
jeblairfungi: oh.  hrm.19:21
jeblairokay, what's really going on then?19:21
anteayaI'm in favour of the solution addressing the problem19:22
ianwmordred: yes, that was my feeling, if we could get agreement19:22
mordredianw: ++19:22
fungii just worry that switching all our distros to chronyd flip-flops us from using a non-default time sync implementation on one family of distros to using a non-default time sync implementation on the other family of nodes19:22
*** jckasper has quit IRC19:22
fungii'm more in favor of sticking with whatever each distro's default recommendation is, even if they disagree19:22
jeblairfungi: i lean toward that way of thinking as well19:22
* crinkle too19:23
jeblair(unless we have a Good Reason(TM))19:23
*** santoshk has quit IRC19:23
*** shaohe_feng has quit IRC19:23
fungidebian and ubuntu seem to be moving forward with the assumption that ntpdate should no longer be used and ntpd needs a rapid quiescence at boot option, while red hat seems to say you should continue to use ntpdate, or switch to chrony because that's what they plan to default to19:24
pabelangerianw: is 352621 an issue anymore now that ntpdate.service was enabled?19:24
*** jckasper has joined #openstack-meeting19:24
*** santoshk has joined #openstack-meeting19:24
*** toscalix has quit IRC19:24
*** shaohe_feng has joined #openstack-meeting19:24
ianwpabelanger: i think it might be a separate issue due to the use of snapshots19:24
fungibut my interpretation of the bug ianw linked is that red hat's package maintainers have little interest in doing away with ntpdate, and would rather just drop ntpd altogether19:25
*** toscalix has joined #openstack-meeting19:25
ianwif the choice is to maintain two time-sync paths, then i think i'd prefer to just have a decree that infra uses ntpd and we just suck up any issues19:25
jeblairalso, we don't use snapshots19:25
jeblair(and we're not planning on supporting them in nodepool in the future)19:25
ianwjeblair: sure, but my thought is that we might make life easier for everyone19:26
*** ksantoshk has quit IRC19:26
ianwif chronyd is making better choices about keeping the time in sync for our situation19:26
jeblairyeah, just wanted to throw that out as not being a primary use case19:26
fungiianw: well, if support for ntpd on red hat is planned to evaporate, it doesn't sound like we should continue using it there19:26
*** thorst_ has quit IRC19:26
fungidoes chronyd do a good job of keeping subsecond synchronization over teh course of a long-running job, or is it going to be more subject to skips and jumps?19:27
*** liyifeng has quit IRC19:27
*** ntpttr__ has quit IRC19:27
fungi(and do we care, i guess?)19:27
*** mrhillsman has quit IRC19:27
*** liyifeng has joined #openstack-meeting19:27
ianwfungi: i think for the most part, we're syncing the time in devstack-gate, and from that point we're not going to be jumping much19:28
ianwof course we could move that sync out of d-g into a more generic part19:28
*** jckasper has quit IRC19:28
*** toscalix has quit IRC19:29
*** ntpttr__ has joined #openstack-meeting19:29
fungii guess the ultimate requirements are, 1. make sure we have a fairly high-precision global synchronization of time on our job workers, and 2. make sure it's actually in sync prior to starting job payloads19:30
ianwfor something like this, are people happy with a "if redhat include ::chrony else include ::ntp" ? http://git.openstack.org/cgit/openstack-infra/puppet-kerberos/tree/manifests/client.pp19:30
*** jckasper has joined #openstack-meeting19:30
*** toscalix has joined #openstack-meeting19:31
ianwreally, that seems to want to say "kerberos needs the time in sync", but how that happens seems orthogonal19:31
*** jckasper has quit IRC19:31
jeblairi'm still at:  chrony in dib on rh, ntp in dib on debuntu (support both in d-g), and ntp in puppet for servers19:31
*** jckasper has joined #openstack-meeting19:31
mordredjeblair: what about rh servers?19:31
AJaegermordred: do we have any?19:31
fungisure, our git servers at least19:32
anteayathe git farm runs centos19:32
fungiand pbx servers19:32
anteayapleia2: centos6 isn't it?19:32
mordredI mean, it's old centos so does not have a problem currently19:32
fungior did we switch those to trusty/.19:32
*** merooney has quit IRC19:32
AJaegermordred: ah, thanks19:32
fungimordred: git servers are centos 7.x... not sure how old you mean19:32
mordredme either19:33
jeblairif we want to advance the state of our puppet to be able to run servers on fedora, i'm not opposed to that conditional.19:33
*** sambetts is now known as sambetts|afk19:33
*** shaohe_feng has quit IRC19:34
pleia2yeah, they're on 7.219:34
fungiianw: what was the bugzilla link for that ntpd systemd element dependency bug pabelanger opened and the maintainer closed>?19:34
*** prateek_ has quit IRC19:35
fungier, systemd unit19:35
*** ihrachys has quit IRC19:35
ianwfungi: not sure i saw that one.  was it to wait for the network to be up before ntpd starts?19:35
*** bobh has quit IRC19:35
fungiyeah, i thought that's the one where they had said red hat was going to be defaulting to chrony anyway19:35
ianwcause it kind of deliberately does *not* do that ... ntpd itself picks up when interfaces appear19:36
pabelangerfungi: I haven't created that one etc. It was a dependency issue on networking, which ntpdate.service provided19:36
fungipabelanger: right, that's the one i'm referring to19:36
*** bobh has joined #openstack-meeting19:36
pabelangerfungi: That fixed the need to restart ntpd to get ntp-wait working19:36
*** shaohe_feng has joined #openstack-meeting19:37
*** gyee has quit IRC19:37
ianwyeah, it is the default for rhel and fedora https://bugzilla.redhat.com/show_bug.cgi?id=1361382#c719:37
fungi#link https://bugzilla.redhat.com/show_bug.cgi?id=1361382#c319:37
openstackbugzilla.redhat.com bug 1361382 in ntp "ntp-wait hangs after boot for a long time, unless ntpd is restarted" [Unspecified,Closed: notabug] - Assigned to mlichvar19:37
*** mrhillsman has joined #openstack-meeting19:37
fungijust found it in the channel logs19:37
*** bobh__ has joined #openstack-meeting19:37
*** radeks has joined #openstack-meeting19:37
anteayafungi: thanks for the link19:37
AJaegerah, fungi-the-irc-search-engine ;)19:37
*** toscalix_ has joined #openstack-meeting19:38
ianwalright, well in conclusion, not much interest in switching to chronyd everywhere19:38
*** ihrachys has joined #openstack-meeting19:38
*** toscalix_ has quit IRC19:38
fungi"As a long-term solution it's probably best to switch to chrony. It's the default NTP client in Fedora/RHEL [...]"19:38
ianwi can see what it looks like to just switch centos/fedora, but i'm not really sold on keeping both paths tbh19:38
fungithat's the quote i was looking for19:38
*** toscalix has quit IRC19:38
*** merooney has joined #openstack-meeting19:39
fungiso based on that i can see switching to chrony as our default ntp client in fedora/centos19:39
fungibecause we're running a non-default on those distros right now19:39
fungiand our usual preference is to operate our servers and run our jobs on as default an upstream choice of options as possible19:40
jeblairwe have a lot of switches like that in puppet, fwiw.  comes with the territory i think.  we could abstract it with a new module so we only have the switch in one place and use that module everywhere in puppet.19:40
pabelangerI believe that discussion could also happen upstream with puppetlabs-ntp too, improving support for RHEL / fedore19:40
jeblair(but i still think dib is the way to go if we want to focus on worker nodes first)19:40
mordredI think worker nodes are the most important part of this19:40
fungii concur19:40
*** bobh has quit IRC19:41
*** david-lyle_ has joined #openstack-meeting19:41
*** numan_ has quit IRC19:41
fungi#agreed We should take a phased approach switching CentOS/Fedora DIB images from ntpdate and ntpd to chronyd, and then consider whether to also switch to chronyd on our long-running CentOS servers and with conditionals in any of our various puppet modules19:42
ianwok, thanks, onward ...19:42
fungithat a close enough summary?19:42
*** dasanind_ has quit IRC19:42
anteayalooks good to me19:42
fungithanks ianw!19:42
*** dasanind_ has joined #openstack-meeting19:43
fungi#topic Bindep uses now bindep.txt by default (AJaeger)19:43
*** openstack changes topic to "Bindep uses now bindep.txt by default (AJaeger) (Meeting topic: infra)"19:43
*** mickeys has joined #openstack-meeting19:43
fungiAJaeger just wanted to mention that some possoble mass change proposals are coming, i think19:43
fungiat least after we get a new bindep release tagged, and then confirmed present on all our images19:43
AJaegeryeah, exactly19:43
mordredonly like 150 projects19:43
AJaegeryeah, only ;(19:43
*** david-lyle has quit IRC19:43
*** Apoorva has quit IRC19:43
fungii'm happy to submit that change when the time comes, if you want19:44
AJaegerIf anybody wants to vote in all PTL elections, please tell me and youcan do the changes ;)19:44
anteayaI actually am surprised these days if I see an AJaeger patch that isnt' a mass change19:44
*** shaohe_feng has quit IRC19:44
anteayaha ha ha19:44
fungiheh, AJaeger has a lot of good non-mass changes ;)19:44
*** nishaYadav has quit IRC19:45
AJaegerfungi, I'm fine doing it myself - like to complete this...19:45
fungianyway, for those that missed the discussion, rationale is in the review and commit message19:45
*** ihrachys_ has joined #openstack-meeting19:45
*** shaohe_feng has joined #openstack-meeting19:45
*** Patifa has quit IRC19:45
fungi#link https://review.openstack.org/35018419:45
fungithere we go19:45
*** galstrom is now known as galstrom_zzz19:45
fungi#topic Constraints can be used in tox (AJaeger)19:45
*** openstack changes topic to "Constraints can be used in tox (AJaeger) (Meeting topic: infra)"19:46
AJaegerAll tox based jobs can now use constraints in the gate. I'm currently struggling with a translation change (waiting for merge) and still test a bit but plan to send an announcement to the list about this in the next days.19:46
*** penick has joined #openstack-meeting19:46
fungithis was a ton of work, thanks for pushing through it AJaeger19:46
anteayathank you AJaeger19:46
*** ntpttr__ has quit IRC19:46
AJaegerA lot of work by many different people - implementation, review, design discussions, ....19:46
anteayathanks for shepherding it19:46
* mordred suggests AJaeger celebrate at White Trash Fast Food (it's what I would do if I were anywhere near Berlin)19:46
anteayaha ha ha19:47
*** Patifa has joined #openstack-meeting19:47
anteayaAJaeger: are you near Belin?19:47
anteayaor just closer than the rest of us?19:47
* AJaeger will drink a glass of wine after the meeting ;)19:47
AJaegeranteaya: closer than the rest of you ;) 300 miles away19:47
anteayaha ha ha19:47
mordredanteaya: :)19:47
anteayaday trip for some fast food ha h aha19:48
*** mugsie_ has joined #openstack-meeting19:48
fungiwow, now that i've searched for that venue, i'm all up for catching a punk show there19:48
AJaegerA plea for everybody: The tricky part are the post and release jobs with constraints. If anything unusual pops up, please carefully evaluate!19:48
*** mickeys has quit IRC19:48
*** ihrachys has quit IRC19:48
mordredfungi: it's like the best place ever19:48
fungiright, those have been switched the most recently, so not entirely certain all the bugs have shaken out19:49
*** amitgandhinz has quit IRC19:49
*** AmitGalitz has joined #openstack-meeting19:49
AJaegerand those are also the ones that most people do not check ;(19:49
*** amitgandhinz has joined #openstack-meeting19:49
fungiokay, anything else on constraints?19:50
AJaegernothing further from me on this unless there are questions19:50
fungi#topic wiki status update (jpmaxman, Krenair, fungi)19:50
*** openstack changes topic to "wiki status update (jpmaxman, Krenair, fungi) (Meeting topic: infra)"19:50
*** galstrom_zzz is now known as galstrom19:50
fungijpmaxman has done some awesome work getting through an in-place upgrade to mediawiki 1.27 with a copy of our production data19:50
fungithat demo is up for all to poke at and see if they can spot anything broken, particularly plugins/extensions we may have forgotten about19:51
fungi#link https://wiki-upgrade-test.openstack.org/19:51
*** coolsvap has quit IRC19:51
anteayathank you jpmaxman19:51
fungiit's set up with the newer "nocaptcha" recaptcha which is supposed to be a lot better at thwarting spammers19:51
* mordred hands jpmaxman a cat that isn't too angry19:52
*** Jeffreyc42 has joined #openstack-meeting19:52
fungialso Krenair has worked out the bits needed to puppet a mw 1.27 deployment on ubuntu trusty19:52
fungi#link https://review.openstack.org/#/q/topic:wiki-upgrade+is:open19:52
*** lbrune has quit IRC19:52
* AJaeger hands jpeeler a glass of wine and says thanks!19:52
AJaegerargh, completion ;(19:52
*** kylek3h has quit IRC19:53
* AJaeger hands jpmaxman a glass of wine and says thanks!19:53
*** Hosam has joined #openstack-meeting19:53
anteayathanks krenair19:53
pleia2fungi: also important to note: "ReCaptcha module will be removed in the near future" https://lists.wikimedia.org/pipermail/mediawiki-announce/2016-August/000193.html so it's good we're switching19:53
*** AmitGalitz has quit IRC19:53
fungii've also added a trove database running mysql 5.6 and our "sane" configuration defaults which jpmaxman is working out some tests of our production data in next19:53
jpmaxmanhah hah19:53
fungiafter the meeting i'll be following up to the -dev ml with a call for testing on the wiki-upgrade-test site as well19:54
anteayaoh good19:54
*** shaohe_feng has quit IRC19:54
anteayahopefully the keep the wiki folks will show up in droves19:54
*** shaohe_feng has joined #openstack-meeting19:55
* jpmaxman blushes19:55
fungiworth noting, new account creation has been open again on the production wiki for a few weeks at this point (i'm just manually deleting spam and blocking spammer accounts a few times a day for now), but file/image uploads have been disabled since the older recaptcha plugin didn't cover them19:55
pleia2super glad to have Krenair's help on this, lots of great patches19:55
fungii don't think there's been any testing yet of whether the new nocaptcha confirmedit plugin covers file uploads but we can try that out after we switch production to 1.2719:56
jpmaxmanhappy to help hopefully we can bring this home19:56
anteayawill new wiki allow file/image uploads?19:56
*** annegentle_ has joined #openstack-meeting19:56
jpmaxmananteaya: right now it is disabled19:56
fungiyeah, "to be determined"19:56
anteayajpmaxman: thank you19:56
fungithere are also some other extensions we can try adding to further thwart spammers, if need be19:57
jpmaxmanyeah there will be work still to be done for sure - the objective is a feature limited spam free wiki to start ;)19:57
fungias well as the somewhat nuclear option of adding a robots.txt to stop search engines indexing wiki content entirely19:57
fungiif we need to19:57
jpmaxmanfungi: I got word we can do that as a short term solution if needed19:57
AJaegerfungi, we could also only blacklist certain file types or all uploads from indexing...19:58
jpmaxmanI think the foundation would rather that than the google juice be diluted for all of www.o.o - but that ideally people would be able to find content on the wiki in the future so it should be a short term fix only19:58
fungiAJaeger: yeah, we did that already. blacklisted pdfs and they switched to uploading images19:58
anteayawhat do you mean you got word?19:58
*** lpetrut has joined #openstack-meeting19:58
jpmaxmananteaya: briefly discussed with jamesmcarthur and sparkycollier19:59
fungihe checked with the foundation site maintainers as to whether they thought it would help mitigate their concerns about the wiki spam influencing keyword rankings for the www site19:59
fungianyway, we're out of time20:00
anteayathank you fungi20:00
fungithanks everyone!20:00
*** gordc has joined #openstack-meeting20:00
*** toscalix has joined #openstack-meeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Aug  9 20:00:25 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-08-09-19.04.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-08-09-19.04.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-08-09-19.04.log.html20:00
flaper87TC folks?20:00
flaper87 annegentle dims dhellmann flaper87 johnthetubaguy mestery mtreinish thingee mordred morgan russellb sdague ttx20:00
* amrith carries pop-corn to comfy seat 20:00
* edleafe finds a comfy seat in the back20:01
* mugsie lurks20:01
flaper87ooooooooooooooook, we've quorum20:01
flaper87Hello everyone!20:01
openstackflaper87: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'20:01
flaper87As usual, you can find today's agenda here: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda20:01
flaper87Let's start with a few "easy" ones20:01
*** Shrews has left #openstack-meeting20:01
flaper87#topic Clarify that cycle-trailing projects follow the milestone deadlines20:01
flaper87#link https://review.openstack.org/34850120:01
AJaegerflaper87: readd #startmeeting20:01
amrithyou want to startmeeting again20:01
flaper87#startmeeting tc20:01
openstackMeeting started Tue Aug  9 20:01:34 2016 UTC and is due to finish in 60 minutes.  The chair is flaper87. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
flaper87Hello everyone!20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
flaper87As usual, you can find today's agenda here: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda20:01
*** openstack changes topic to " (Meeting topic: tc)"20:01
flaper87Let's start with a few "easy" ones20:01
openstackThe meeting name has been set to 'tc'20:01
flaper87#topic Clarify that cycle-trailing projects follow the milestone deadlines20:01
*** openstack changes topic to "Clarify that cycle-trailing projects follow the milestone deadlines (Meeting topic: tc)"20:01
flaper87#link https://review.openstack.org/34850120:01
flaper87AJaeger: I got this20:01
flaper87#topic Refresh I18n ATC list20:01
*** openstack changes topic to "Refresh I18n ATC list (Meeting topic: tc)"20:02
flaper87#link https://review.openstack.org/35148020:02
notmorganflaper87: you can remove me from the ping list20:02
flaper87notmorgan: yup20:02
notmorganflaper87: as of today, I'm no longer part of the TC.20:02
russellbnotmorgan: thanks again for your service :)20:02
flaper87notmorgan: thanks for your service20:02
* flaper87 will update the governance repo20:02
flaper87ok, this one has majority already20:02
annegentle_notmorgan: sorry to see you go, thanks for the support and service20:02
*** pabelanger has left #openstack-meeting20:02
flaper87any reason why this shouldn't be merged ?20:02
annegentle_flaper87: looks good to me20:03
johnthetubaguywe could try wait for consensus instead, just for giggles, but otherwise, I am happy20:03
*** ihrachys has joined #openstack-meeting20:03
*** ihrachys_ has quit IRC20:03
flaper87now, onto the one I skipped after my failed w/ my copy/paste to start the meeting20:03
annegentle_johnthetubaguy: 9 is pretty darn close :)20:03
flaper87#topic Clarify that cycle-trailing projects follow the milestone deadlines20:03
*** openstack changes topic to "Clarify that cycle-trailing projects follow the milestone deadlines (Meeting topic: tc)"20:03
flaper87#link https://review.openstack.org/34850120:03
flaper87This one has 8 votes already20:04
flaper87that's majority already.20:04
flaper87Any reason why this shouldn't be merged?20:04
dhellmanndoes anyone have any other questions about that one?20:04
*** shaohe_feng has quit IRC20:04
annegentle_can't think of one myself20:04
* flaper87 is good with it20:05
*** kebray has quit IRC20:05
flaper87ok, sold... I guess20:05
*** shaohe_feng has joined #openstack-meeting20:05
flaper87Now, onto more heated topics20:05
flaper87#topic Replacing Morgan's seat20:06
*** openstack changes topic to "Replacing Morgan's seat (Meeting topic: tc)"20:06
flaper87#link http://lists.openstack.org/pipermail/openstack-tc/2016-August/001233.html, including various proposals20:06
flaper87#link https://review.openstack.org/351104 (flaper87)20:06
flaper87#link https://review.openstack.org/351295 (dhellmann)20:06
flaper87#link https://review.openstack.org/351427 (anteaya)20:06
flaper87There are several proposals. The first one proposes using the next closest election to elect all the missing seats. If 1 or more vacants would open before the election, those would be added to the number of seats up for election.20:06
flaper87The second proposal is to adopt the same model as the foundation and it proposes three different scenarios: 1) Vacancy openned less than 4 weeks before the election and the seat will be contested, then nothing is done till the election. 2)  Vacancy openned less than 4 weeks before the election and the seat will not be contested, then candidates that don't win a seat would be asked if they want to20:06
flaper87serve 3) Vacancy opens more than 4 weeks before the election, the TC consults the last results.20:06
flaper87The third proposal is to have by-elections as soon as the vacancies open, regardless what time in the cycle we're at.20:06
flaper87#link https://en.wikipedia.org/wiki/By-election20:06
*** bill_az_ has quit IRC20:06
flaper87I'm fine with either the first or the third option, to be honest. The 2 first points of the second option are fine. The third one is the one that doesn't sit well with me. The main reason is that if it happens too late in the cycle, then I believe we'd be pulling in someone in the TC that could loose to others anyway.20:06
flaper87The way the community and its members evolve in the cycle is really hard to predict, which is why I'd prefer to leave it up for elections either to the closest election or a by-election.20:06
* flaper87 hopes that summarizes the three proposals20:06
flaper87(fairly summarizes would be better)20:06
anteayaflaper87: the third proposal is not by-election as soon as the vacany is open20:07
flaper87anteaya: mind clarifying?20:07
flaper87anteaya: sorry about that20:07
anteayathe third proposal is by-election, timing and details to be determined based on circumstances20:07
flaper87anteaya: thanks! Sorry for not summarizing it well  :)20:08
dhellmannit's reasonable to expect that we would want to do it relatively quickly, but it's not required20:08
anteayadhellmann: right20:08
mugsieanteaya: but always holding a by-election?20:08
anteayamugsie: yes20:08
anteayaby-election could be held with other election20:08
*** thorst_ has joined #openstack-meeting20:08
anteayaor if vacancy occurs at christmas the electon could be held when it makes sense to do so20:08
annegentle_anteaya: other election such as a PTL election? Or along with the already-scheduled TC election?20:08
anteayaannegentle_: either20:08
anteayawhatever makes sense20:09
annegentle_anteaya: check, thanks for clarifying.20:09
anteayaannegentle_: thanks for asking20:09
mordredthere are times when I wish we could CIVS a set of competing specs20:09
sdaguemy preference is dhellmann's proposal, which aligns with how the board does it more or less. It feels to me like 5 month old results are still pretty fresh in the community given our current turn over rate.20:09
dimsi agree with sdague and dhellmann20:09
johnthetubaguyso I am currently preferring option 2, because it saves lots of people a lot of time, and still seems to respect the will of the voters20:09
*** ntpttr__ has joined #openstack-meeting20:09
flaper87sdague: 5 months old results is exactly what doesn't sit well with me20:10
mugsieflaper87: no?20:10
*** ntpttr__ has quit IRC20:10
russellbthe board doesn't actually specify "consult last results"20:10
flaper87Things change, people come/go, opinions evolve, etc20:10
russellbit's just up to the individual directors to appoint, and in practice, that's how they've done it so far20:10
sdaguerussellb: that's why I said "more or less"20:10
russellbbut it's not coded that way20:10
thingeeI'm ok with the 5 month old results. Not ok with an election to happen and assume voters will be around.20:10
russellbthe flexibility is nice20:10
mugsieits a pretty short period of time.20:10
annegentle_I feel / sense that the 4 week window one is best for a bunch of groups; the electorate, the election officials not having to do a by-election on-demand, and the TC members themselves feeling like there's a process for when you just can't finish your term.20:10
*** merooney has quit IRC20:10
anteayathingee: that is why the timing is not set in the patch20:10
sdaguerussellb: to be fair, I'd also be fine with more flexibility in there as well20:11
edleafeflaper87: we elect people for a full year; I doubt that someone who was voted for last election isn't desireable 5 months hence20:11
* annegentle_ still needs to vote20:11
dhellmannrussellb : I would also be ok with a proposal that said it that way, but some other folks seemed to want the details written down20:11
flaper87thingee: fwiw, my proposal says we could elect the open sits on the next closest election. Not saying it's better, though20:11
anteayathingee: so the timing can be selected to ensure voters are around20:11
johnthetubaguythingee: good point, we don't have the best turn out anyways, a by-election is likely much worse20:11
*** asselin_ has joined #openstack-meeting20:11
*** julim has quit IRC20:11
flaper87edleafe: well, if that person won already, there's not much to do. If that person didn't win, then there is20:11
sdaguejohnthetubaguy / thingee ++20:11
thingeeanteaya: that's hard to figure though20:11
annegentle_oh, and I still am confused on one point... just a sec.20:11
thingeeanteaya: we already have problems with usual scheduled elections20:12
anteayathingee: we can look at email and gerrit activity20:12
edleafeflaper87: but "won" is a relative term in CIVS20:12
*** david-lyle_ is now known as david-lyle20:12
anteayathingee: yes we do, no argument there20:12
*** thorst_ has quit IRC20:12
annegentle_so do we need the wording from https://review.openstack.org/351104 so that the four-week proposal works (https://review.openstack.org/351295)? They are independent, right?20:12
flaper87edleafe: yeah yeah, made it into the N seats up for election20:12
sdagueand picking voting times then becomes another extra effort20:12
anteayabut I think we are futher ahead to have more elections, when warrented, not fewer20:12
*** iyamahat has joined #openstack-meeting20:12
thingeesdague: right20:12
*** AJaeger has left #openstack-meeting20:12
dhellmannanteaya : flaper87's proposal and mine are mutually exclusive. We don't want both of them.20:12
amrithflaper87, dhellmann I think the compromise between the three proposals is my Aug 8, 6:43am comment. with threshold = 4 weeks.20:12
annegentle_dhellmann: ok20:13
thingeegoing down a list of previous voted people is less effort imo20:13
dhellmannoops, meant that for annegentle_ , tab-complete-fail20:13
* thingee is lazy20:13
anteayathingee: yes it is less effort20:13
annegentle_dhellmann: happens all the time right anteaya ? :)20:13
anteayano question about how much effort it is20:13
anteayaI'm talking about value20:13
anteayaand doing right by the electorate20:13
sdaguegiven the historical drift of candidates on the TC list (who ranked where cycle after cycle), I think that a special election is largely going to give us the same results as just pulling from the last election, except with a ton of extra work20:13
anteayaannegentle_: all the time20:14
edleafevacancies are filled with either appointment or re-vote. Picking from previous results is just one way to handle an appointed replacement20:14
thingeeLooking at the list now of the next people in-line, are these people still active and participating?20:14
dhellmannamrith : I don't think civs results in ties, does it?20:14
thingeewould anyone have a problem with them?20:14
anteayadhellmann: it can20:14
* flaper87 doesn't want special elections but a simple election on the closest one20:14
*** ihrachys has quit IRC20:14
amrithdhellmann, let me check. I think I looked it up and found that it could.20:14
anteayadhellmann: but we have rules for tie breaking20:14
anteayadhellmann: we just have never had to invoke them20:14
*** shaohe_feng has quit IRC20:15
*** baoli has quit IRC20:15
edleafethingee: that's the vetting process. If they aren't active, or would upset affiliation, move on to the next in line20:15
annegentle_thingee: yeah I wondered if we had polled the people next on the list yet...20:15
*** sindhu has quit IRC20:15
dhellmannsdague : I think you're probably right.20:15
*** baoli has joined #openstack-meeting20:15
sdaguethingee: they mostly all seem active to me, and I wouldn't have a problem going down that list in order20:15
edleafethingee: or if they are simply no longer interested20:15
thingeeedleafe: +120:15
anteaya#link https://wiki.openstack.org/wiki/Governance/TieBreaking20:15
russellbanyone have a link handy to the last TC election results?20:15
*** toscalix has quit IRC20:15
*** shaohe_feng has joined #openstack-meeting20:15
sdagueyeh, one sec20:15
*** singlethink has joined #openstack-meeting20:16
sdaguedtroyer would be the fix ask20:16
johnthetubaguyjust to be clear, did we rule out the not filling the seat until its next up for election approach?20:16
thingeedon't think anyone would be upset with dtroyer :)20:16
dhellmannjohnthetubaguy : we did not explicitly decide that.20:16
sdaguethen david-lyle, sdake, anteaya, cdent (in that order)20:16
amrithdhellmann, anteaya found the link I was loking for; thanks anteaya20:16
russellbthingee: truth20:16
anteayajohnthetubaguy: that would leave the seat vacant until next north american spring20:16
johnthetubaguyanteaya: yes20:16
notmorganjohnthetubaguy: my seat would be up in spring.20:16
anteayaamrith: welcome20:16
notmorganlong time w/ an unfilled seat.20:17
anteayajohnthetubaguy: I didn't see that proposal up for discussion, no20:17
dimsAll 4 algorithms end up with same result dtroyer20:17
anteayadims: this time20:17
dhellmannjohnthetubaguy : you raise a good point, and I think we should at least agree that we want to fill the seat if there's some minimum amount of time left.20:17
dhellmannjohnthetubaguy : my proposed minimum is 1 month20:17
dimsanteaya : y20:17
notmorgandhellmann: i think your review specified 4wks, i would go with that over 1 month20:17
notmorgandhellmann: since months vary in length20:18
dhellmannnotmorgan : tomato, tomato20:18
anteayaand the rules we are creating are for filling the seat in an uncontesed way even if someone has an issue with the candidate20:18
flaper87dhellmann: the only reason I think we must do that is because we don't have a consensus model for reaching agreement20:18
notmorgandhellmann: precision :P20:18
flaper87that being filling up the seat20:18
mtreinishdhellmann: yeah, I think that was a good minimum20:18
flaper87otherwise we could live with an empty seat until the next election20:18
sdagueyeh, 4 weeks seems like a very reasonable time frame20:18
dimseither works for me 4 weeks or 1 month20:18
johnthetubaguydhellmann: yeah, that seems a good minimum, 4 weeks20:18
annegentle_#link http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_fef5cc22eb3dc27a20:18
*** bethwhite_ has left #openstack-meeting20:18
dhellmannflaper87 : that's a separate discussion, but sure20:18
notmorganflaper87: to be fair, I could have also just disappeared and it would be the net effect of an empty seat until next election it was up20:19
dhellmannnotmorgan : we would have noticed20:19
flaper87notmorgan: sure, but we would have noticed20:19
annegentle_dhellmann: what was an exercise in findability for me was "when do we hold TC elections"20:19
dhellmannare we at least agreed on the 4 week question?20:19
anteayanotmorgan: well then we would have had the disappearing leader issue again20:19
dims+1 on 4 weeks dhellmann20:19
notmorgandhellmann: right, but there was no handling of that here, and has the same result.20:19
annegentle_answer: 5 weeks before the Summit20:19
anteayaannegentle_: it is in the charter20:19
sdaguedhellmann: yeh, seems like20:20
flaper87dhellmann: I'm not happy with it, tbh. 5 months old results don't sit well with be but most people seem to be happy with 4 weeks20:20
flaper87so, I'll live by it20:20
notmorgananyway. sorry. I'm going back afk and getting food. /me ducks out of this convo20:20
dhellmannflaper87: yeah, one question at a time: so you're ok with 4 weeks?20:20
*** Apoorva has joined #openstack-meeting20:20
flaper87dhellmann: no, I meant to say I'm not ok with 4 weeks. Perhaps we could make the threshold bigger: 8 weeks ?20:21
dhellmannflaper87 : so you're saying if I resign 8 weeks before the end of my term, you would not replace me until the next election?20:21
flaper87dhellmann: yes20:21
dhellmannthat's not the direction I expected you to go20:21
anteayaannegentle_: The election is held 3 weeks prior20:21
sdaguethat seems long for me20:21
anteayato each design summit, with nominations due 4 weeks prior to the summit and20:21
dimstoo long imho20:21
anteayaelections held open for no less than five business days.20:21
dhellmannwhy would you be willing to wait so long?20:21
annegentle_anteaya: oh I'd better find the other source I found.20:21
anteayaannegentle_: #link http://git.openstack.org/cgit/openstack/governance/tree/reference/charter.rst20:21
*** asselin_ has quit IRC20:21
edleafedhellmann: 8 weeks before the next election, or the end of your term?20:22
anteayaannegentle_: under Election for TC seats20:22
*** asselin_ has joined #openstack-meeting20:22
dhellmannedleafe : either, really20:22
flaper87dhellmann: the reason is that I don't feel ok with using a 5months old results to pick someone that will fill the remaining 7 months of the person leaving20:22
anteayaannegentle_: the only doc that trumps the charter is the foundation by-laws20:22
dhellmannedleafe : the question is how long do we want to allow an empty seat20:22
sdagueso, I guess the question we should figure out, is whether anyone objects besides flaper87 ? Because we're +6 on dhellmann's proposal right now20:23
edleafedhellmann: exactly. The next election keeps that vacancy short20:23
dhellmannedleafe : I think I'm not being clear, so I'm just going to stop offering alternatives. Let's pick one of the two that are written up.20:24
*** ezpz has left #openstack-meeting20:24
dhellmannsorry, 320:24
*** cdelatte has quit IRC20:24
edleafedhellmann: :)20:24
edleafeI think 8 weeks is much too long20:24
sdaguedhellmann: agreed, we don't need to spend from now until the next election discussing how to fill an empty seat :)20:24
flaper87Ok, there are 7 votes on dhellmann review20:24
flaper87I guess we should go w/ that one20:24
johnthetubaguyHonestly, I don't think running a new by-election gains enough to justify the effort of all those nominations, voting, etc, etc20:24
mordredsdague: I disagree20:24
dhellmannflaper87: this is a sort of important one, so I'd like to get most everyone on board one way or the other if we can20:25
*** shaohe_feng has quit IRC20:25
fungiin the past we have had a tc election where some of the seats were for a one-year term and some for a half-year term, when bootstrapping the current committee size20:25
anteayayeah charter changes aren't simple majority20:25
annegentle_flaper87: only if you can support it. We can work towards consensus here.20:25
russellbdhellmann: would be good to know if the others are abstain / -1 / neutral ...20:25
*** shaohe_feng has joined #openstack-meeting20:25
flaper87dhellmann: I'm with your proposal. I'm not happy with the 4 weeks but I'm willing to live by it20:25
dhellmannfungi : yeah, that's more or less what I based my proposal on.20:25
fungiso there is precedent for a seat in an election being for a partial term20:25
sdaguedhellmann: right, I'd like to have everyone on the TC register here20:25
annegentle_only thing the charter says is, "After the initial election, the elections for the Technical Committee shall be held at least every six months."20:26
* flaper87 is not trying to rush the discussion but rather trying to reach consensus20:26
sdagueI don't want to move forward on simple majority20:26
annegentle_#link https://www.openstack.org/legal/technical-committee-member-policy/20:26
johnthetubaguy+1 for getting everyones vote on this20:26
dhellmannflaper87 : ok. I'm willing to discuss changing that, maybe as a separate thing next week?20:26
flaper87sdague: that is not what I said, fwiw20:26
russellbmaybe quick poll of whoever hasn't voted yet?20:26
flaper87dhellmann: sounds perfect20:26
annegentle_yeah I'm also fine with waiting20:26
dhellmannflaper87 : I picked what seemed like a pragmatic number but I'm not wedded to it20:26
anteayaAmendments to this Technical Committee charter shall be proposed in a special20:26
anteayamotion, which needs to be approved by the affirmative vote of at least20:26
anteayatwo-thirds of the total number of TC members (rounded up: in a 13-member20:26
mtreinishrussellb: assuming they're around20:26
anteayacommittee that means a minimum of 9 approvers).20:26
sdakesdague fwiw, I am still available for TC seat filling if necessary -but sounds like dtroyer using the 4 algos gets the seat.20:27
russellbmtreinish: yup.20:27
sdakettyl )20:27
*** radeks has quit IRC20:27
anteaya#link http://git.openstack.org/cgit/openstack/governance/tree/reference/charter.rst under Ammendment20:27
sdake:) i mean to say20:27
dimssdake ack :)20:27
annegentle_sdake: thanks, good to know20:28
sdagueso ttx is out, dhellmann hasn't voted, who is the missing vote on there?20:28
anteayacharter changes need 9 votes20:28
*** lblanchard has quit IRC20:28
*** raildo has quit IRC20:28
russellbnotmorgan hasn't voted, heh20:28
annegentle_russellb: right :)20:28
flaper87we have 12 votes20:28
notmorgani am not a member of the TC, I do not get to vote20:28
dims#link https://review.openstack.org/#/c/351295/20:28
thingeettx did vote +1 at one point20:28
flaper87and one is dhellmann's on his own patch20:28
notmorgani officially stepped down effective today20:28
thingeejust not the current patch :)20:28
flaper87which counts like a vote20:28
sdaguemestery: ?20:28
russellbnotmorgan: i know, just joking ... were couting up the votes (or missing votes)20:29
notmorganemail was sent to secretary@o.o confirming this.20:29
russellbmestery is probably out, at openstack silicon valley20:29
dhellmannflaper87 : I went ahead and registered my vote20:29
annegentle_russellb: he's tweeting from there anyway :)20:29
flaper87dhellmann: thanks20:29
flaper87that helps20:29
flaper87ok, we're missing ttx and mestery20:29
sdagueif we hold it open for 2 more days, think both of them will have a chance to weigh in?20:29
*** asettle has quit IRC20:29
dhellmann10 is more than 2/3 of 12, right?20:29
flaper87we can wait for those and address questions/concerns next week if there are more20:29
sdagueit is20:29
anteayadhellmann: you need 9 votes20:30
flaper87but we should be fine20:30
annegentle_dhellmann: it is but this is a good chance to practice consensus20:30
*** jprovazn has quit IRC20:30
sdagueI just want to make sure people had the ability to voice an opinion20:30
dhellmannannegentle_ : sure20:30
*** asettle has joined #openstack-meeting20:30
*** asettle has quit IRC20:30
flaper87So, Does anyone have concerns about dhellmann's proposal?20:30
flaper87#link https://review.openstack.org/#/c/351295/20:30
edleafeanteaya: the TC is only 12 members as of today, so technically, 8 are needed20:30
flaper87Any other questions about the process?20:30
flaper87Any other questions about the requirements?20:30
dhellmannalright, I'm fine leaving it open until next week. we should ask dtroyer to join us for the meeting.20:30
*** asettle has joined #openstack-meeting20:31
*** baoli has quit IRC20:31
annegentle_dhellmann: sounds good20:31
dtroyerfwiw, I'm here20:31
amrithedleafe, normally in the computation of vote margins, it is the size of the body, not the number currently present. so 9 is still required; IMHO20:31
dhellmanndtroyer : I meant to make sure you were here next week :-)20:31
annegentle_dtroyer: thanks for being here20:31
edleafeamrith: the body is only 1220:31
dtroyerdhellmann: roger20:31
amrithno, the body is 13, 12 members.20:31
mugsieamrith: the wording would indicate 12 memebers20:31
*** spotz is now known as spotz_zzz20:31
sdaguedtroyer: so, question, do you remain interested in serving on the TC?20:31
flaper87we'll have to wait till ttx is back anyway. I don't have +W and It'd be great to have his opinion (and mestery's too)20:31
dhellmannamrith : 10 is also > 2/3 of 1320:31
sdaguebecause if the answer is yes, that simplifies talking with folks down the list20:31
dtroyersdague: yes, I would happily fill the remaining term if asked20:32
*** spotz_zzz is now known as spotz20:32
sdagueok, cool, so we have that data point in public20:32
dimsthanks dtroyer20:32
flaper87dtroyer: danke20:32
sdagueok, I move we leave voting open until ttx and mestery express a vote, or next meeting, whichever comes first20:32
sdagueand we move to next topic20:32
flaper87sdague: just said that :P20:32
*** karthikp_ has quit IRC20:32
dims++ flaper87 sdague20:33
amrithdhellmann, you are correct. sorry; 9 or >20:33
dhellmannflaper87 : as chair, will you ping both ttx and mestery in the mean time?20:33
flaper87dhellmann: yup, on it20:33
flaper87moving on20:33
flaper87#topic Community-wide goals20:33
*** openstack changes topic to "Community-wide goals (Meeting topic: tc)"20:33
flaper87#link https://review.openstack.org/34906820:33
flaper87#link https://review.openstack.org/34906920:33
flaper87#link https://review.openstack.org/34907020:33
flaper87dhellmann: I'll let you summarize/introduce this one20:33
dhellmannthis is the write-up of the idea that we discussed the thursday of the training in ann arbor20:34
dhellmannthe idea is to be a little more active in encouraging the community to take some specific actions each cycle20:34
*** HeOS has joined #openstack-meeting20:34
dhellmannI've included 2 specific proposals from the list that we discussed as examples20:35
dhellmannthere has been a fair amount of concern about consequences for not following through on goals, but very little discussion of the specific goals proposed20:35
*** dfflanders has joined #openstack-meeting20:35
*** shaohe_feng has quit IRC20:35
sdagueI think both goals are good small scoped ones20:35
*** shaohe_feng has joined #openstack-meeting20:35
thingeesdague: +120:35
* flaper87 likes what's up there20:36
dhellmannI'll try to summarize ttx's comments on the consequences by saying that failing to follow through is not an immediate trigger for being dropped, but it may be seen as part of a larger set of signals that a project does not really consider itself part of the community20:36
mordredI also think that starting from a "hey everybody, let's all try to ..." is great. nobody has done it yet. might someone choose to not play ball? sure20:36
dhellmannhis wording on the mailing list is probably better20:36
sdaguegood to test the process, mostly I've been thinking about how to use something similar to help drive the upgrades conversation20:36
mordredand then yeah, ttx said that well20:36
annegentle_dhellmann: are the two proposed the "typical" scope you'd expect?20:36
annegentle_dhellmann: or are you ready for more to be proposed by others?20:36
annegentle_sdague: yeah and I was thinking of something around api-ref now that I have the numbers and the nav is coming together.20:36
thingeettx's wording http://lists.openstack.org/pipermail/openstack-dev/2016-August/100670.html20:37
dhellmannannegentle_ : my sense is that we only want a couple of these each cycle, so I don't think we want more right now unless we reject one of these20:37
mugsiemordred: sure - but I am not sure I would be happy top have this morph into "do this or leave" conversation20:37
*** gyee has joined #openstack-meeting20:37
annegentle_#link http://lists.openstack.org/pipermail/openstack-dev/2016-August/100670.html20:37
sdagueannegentle_: right, we'd probably have done *this* for api-ref this cycle if we had this process20:37
mordredmugsie: totally20:37
sdaguewe kind of ad-hoced it20:37
*** dprince has quit IRC20:37
dhellmannas far as scope, we want things to be finished in a cycle, rather than being of indefinite length, and that's going to naturally limit the scope20:37
sdaguebut, it would be a very reasonable 3rd thing to use this process this next cycle20:37
mugsiewhich is why I think there needs to be more concrete wording about consequences20:37
flaper87dhellmann: question: I don't remember if it was mentioned/discussed whether some of this goals would eventually become requirements for entrance to the big tent. I think I read new projects have 1 year to be compliant with some of these goals, is that right?20:37
dhellmannlarge initiatives will need to be broken into phases20:37
mordredmugsie: I think I'd rather just see people get excited about a few shared esprit-de-corps types of things - without us holding an axe over anyone's head20:38
*** Hosam has quit IRC20:38
annegentle_dhellmann: ok, makes sense20:38
flaper87For example, if all projects manage to migrate to py35, we might want to ask new projects to be py35 compliant20:38
dhellmannflaper87 : I believe somewhere in that patch I say that all teams need to do the goals. that would apply to new teams, too.20:38
johnthetubaguysdague: I was just going to suggest we might want to add it still20:38
mugsiemordred: yeah - but the ML has been hinting at it having consequences20:38
dhellmannflaper87 : if we need to clarify that, we can work on language in another patch?20:38
*** iyamahat has quit IRC20:38
thingeemugsie: I don't really find it productive to speculate that there would be a goal agreed that would cause problems.20:38
annegentle_dhellmann: Also, forgive me if I'm behind on the ML discussion: do we see these as themes for a release such as what the product group has discussed?20:38
flaper87dhellmann: yup, sounds perfect. I;ve voted already20:38
dhellmannannegentle_ : a bit more narrow, though ttx did mention that the foundation might use them as "look what we did" type messaging at summits20:39
johnthetubaguyannegentle_: I think these goals are generally more specific20:39
mugsiethingee: well, teams are differning sizes. A team might decide that actully writing docs this cycle is better for users, for example20:39
sdaguehonestly, I really rather just think of this as information gathering and exposure20:39
mordredmugsie: I tihnk thingee just said what I was thinking - hopefully these are all just putting words to things that are already on people's lists anyway20:39
johnthetubaguysdague: +120:39
mordredmugsie: and I think there's a difference in "we couldn't get to it" and "screw you guys, we're not doing it"20:39
mugsiethe current 2 are fine, nice small, and common sense20:39
sdaguebecause I think that we state some goals, ask people to work towards them, make sure we captures what's getting done, and it helps us all have a better picture of the state of openstack20:39
thingeemordred: +120:40
flaper87I think this is a very good start for the community-goals effort20:40
*** MeganR has quit IRC20:40
thingeeflaper87: agreed, it has to start somewhere.20:40
annegentle_I sorta read it as "replace the giant cross-project spec with smaller goals" -- is that an accurate assessment?20:40
*** amitgandhinz has quit IRC20:40
thingeeannegentle_: I think specs will still exist as reference20:40
*** thorst_ has joined #openstack-meeting20:40
thingeethere is no replacing here20:40
dhellmannannegentle_ : not really. by the time something is ready to be approved as a goal, I would expect the path to finishing it to be very clear already.20:40
*** amitgandhinz has joined #openstack-meeting20:41
johnthetubaguydhellmann: so I was kinda expecting us to merge the goals post summit, but I guess this is us going to the summit with some merged ideas to spark the conversation?20:41
dhellmannfor example, one of the other things discussed was moving all projects so they can be deployed behind apache20:41
thingeedhellmann: +120:41
sdaguethis feels more about execution support20:41
flaper87johnthetubaguy: yeah20:41
dhellmannfiguring out how to do that is going to require work up front20:41
annegentle_ok that's useful thanks dhellmann thingee20:41
dhellmannjohnthetubaguy : right, we need to land these in time for teams to (a) know about the fact that we expect them to dedicate time to them and (b) have time to do any planning at the summit20:42
dhellmannjohnthetubaguy : in future cycles, we'll be doing this right before the PTG20:42
annegentle_only other question that I hadn't put on review is related to: if you author the goal are you then responsible/accountable for follow up in supporting teams to get what they need to complete the goal?20:42
*** maishsk has quit IRC20:42
sdaguebecause a bunch of the openstack-specs were like "let's do this thing!" and even if they got approved, then actually doing that thing, and figuring out where that stood in all the projects, was pretty nebulous. And if you can't see how far away the end game is, people get demotivated20:42
*** omghai2u has joined #openstack-meeting20:42
*** maishsk has joined #openstack-meeting20:42
annegentle_sdague: yeah exactly the scenario I played through too20:42
sdagueit was amazing how much just doing this http://burndown.dague.org/ helped us work through our api-ref on nova20:42
dhellmannannegentle_ : that's a good question. I hope not. I've written this so that we only want goals to be documented by a tc member, in part to avoid having the governance repo turn into the cross-project specs repo.20:43
annegentle_dhellmann: ayup, got it.20:43
mugsieso, in that line of thinking, would goals that only really affect a few projects be accepted?20:43
thingeeannegentle_, dhellmann: I don't think it should. it should be up to the team.20:43
dimsannegentle_ : +1 should have sufficient help to the teams20:43
flaper87sdague: lol, I read "execution support" entirely wrong20:43
flaper87sdague: good thing you elaborated on that20:43
sdagueflaper87: heh20:43
johnthetubaguysdague: it was so good we stole that for the configuration options:
thingeeannegentle_, dhellmann the TC may review who has followed through the goals though and may reach out to projects.20:44
dhellmannmugsie : the oslo goal that's up now affects fewer projects than I thought when I wrote it up, but we wouldn't be likely to take something as "community wide" if we knew from the outset that it was only 2 projects.20:44
dhellmannthingee : yes, we need to do that review at the end of each cycle20:44
thingeedhellmann: great, I think that's the only follow-up that needs to happen. leave the goal author out of it20:45
dhellmannsdague : I may be interested in the code for that for release tracking20:45
annegentle_dhellmann: and is it worthwhile to propose something that affects one team only? Or is that a 1:1 convo with that team's lead?20:45
*** rgoodwin has quit IRC20:45
dhellmannannegentle_ : these are for community-wide goals20:45
sdaguedhellmann: yeh, sure, I have thoughts about how to make it more generic. We can do that offline.20:45
thingeedhellmann: I think it's going to be enough work just getting a goal agreed.20:45
dhellmannannegentle_ : if we need a way to make recommendations to individual teams, we need a new process20:45
johnthetubaguysdague: markus_z did a bit of that, possibly20:45
flaper87thingee: ++20:45
*** shaohe_feng has quit IRC20:45
dhellmannannegentle_ : I'd be happy to collaborate on designing that20:45
annegentle_dhellmann: ok, thanks20:46
*** shaohe_feng has joined #openstack-meeting20:46
flaper87ok, we have 5 more mins for this topic. Anything else people would like to ask? Other open questions? Huge objections?20:46
johnthetubaguydhellmann: would we not just use the team's own process for work, if its team specific?20:46
flaper87The review will be open till ttx is back so there's still time to comment on the review20:46
russellbi like it.  thanks for driving this, dhellmann20:46
annegentle_that's all I have, hadn't voted yet as I needed to ask these20:46
sdagueI think this process is useful for even fully understanding how far away we are from things, as dhellmann said, we didn't even know how big the oslo gap was (which is smaller than anticipated) until doing that analysis20:46
russellband the goals seem like obviously good ones20:46
johnthetubaguysdague: +120:46
sdaguewhich is incredibly valuable all on it's own20:47
dhellmannjohnthetubaguy : if the tc is asking a team to do something they're not already prioritizing, we may want to do that a different way20:47
*** asselin__ has joined #openstack-meeting20:47
flaper87annegentle_: I always look forward to your questions, fwiw20:47
johnthetubaguydhellmann: honestly, that feels bad to me, but thats a separate conversation20:47
annegentle_heh :)20:47
johnthetubaguyso I love the goals20:47
*** asselin_ has quit IRC20:47
sdagueand I agree with russellb, thanks dhellmann for driving this20:47
dhellmannjohnthetubaguy : right20:47
johnthetubaguyits totally something I wanted to see happen while I was on the TC, and love this approach20:47
flaper87Ok, unless there are other questions/comments, I think we can move on20:48
johnthetubaguyI am tempted to say what we have before the PTG/summit is a draft that could get torn up, but thats just splitting hairs20:48
annegentle_johnthetubaguy: yeah I do think timing will matter too20:48
johnthetubaguywe need something before, else nothing will happen20:49
johnthetubaguybut its likely to get revised20:49
dhellmannyeah, we're going to need to work quickly to get goals out of this summit to work on before the ptg in feb20:49
johnthetubaguybut honestly, we should just do it20:49
flaper87johnthetubaguy: yeah, that was one of the goals20:49
dimswe should encourage PTL's to file some too? (ex stevemar to add a goal for keystone v3 api support in all projects)20:49
annegentle_dims: good Q20:49
dhellmanndims : as written, this says tc members will write them up20:50
dhellmannI want *us* to be active in this process.20:50
dimsdhellmann : ok collaborate with one of us to file it20:50
russellbneed to keep a reasonable limit on the number of these, too20:50
dhellmanneveryone can propose them, but I want us to take the step of documenting them, and choosing them20:50
johnthetubaguyI guess its just a case of getting a sponsor via the ML20:50
*** spotz is now known as spotz_zzz20:50
flaper87dims: and I see those as different goals but we can elaborate on this later20:50
sdaguedhellmann: ++20:50
russellband just approve a couple/few highest priority ones..20:50
sdaguelet's start with us deep in the middle of this20:51
annegentle_dhellmann: yeah I'd imagine a deadline, then a discussion meeting at regular TC meeting time.20:51
russellbat least to start with20:51
dhellmanndims : also, I do not expect us to be choosing from a bunch of written up goals each cycle. I expect us to have a list of things coming out of the summit, get it narrowed down, then write up a couple of finalists.20:51
russellbdhellmann: ++20:51
flaper87russellb: I thin kthe priority of some of these goals will be the key of how they will be merged20:51
flaper87dhellmann: ++20:51
annegentle_dhellmann: oh even better20:51
sdaguedhellmann: ++20:51
johnthetubaguydhellmann: ++ thats what I was kinda trying to say20:51
*** edtubill has quit IRC20:51
dimsack dhellmann20:51
flaper87ok, 10 mins left, let's move onto Open Discussion! Thanks again, dhellmann20:51
dhellmannwe're the last step in this process20:51
mtreinishdhellmann: ++20:51
dimsmakes sense20:51
dhellmannwell, aside from implementation :-)20:51
flaper87#topic Open discussion20:52
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:52
flaper87dhellmann: got mestery to vote on the patch20:52
dhellmannflaper87 : ++20:52
flaper87ttx will vote when he's back20:52
* dims is away on vacation next week20:52
flaper87* Agree to at least temporarily abandon stalled items:20:52
flaper87#link https://review.openstack.org/33879620:52
flaper87#link https://review.openstack.org/31469120:52
flaper87#link https://review.openstack.org/29597120:52
flaper87#link https://review.openstack.org/29552820:52
* flaper87 is away on vacation next week too20:52
flaper87Any comments on those reviews?20:52
dhellmannflaper87 : those release model items can be dropped20:52
mtreinishflaper87: I'll abandon mine on that list20:52
flaper87Any reason why those shouldn't be abandoned ?20:52
flaper87mtreinish: thanks20:52
flaper87sdake: ^20:52
mtreinishI still need to write up the followup proposal20:52
dhellmannflaper87 : sorry, the 'type' tag items20:53
mtreinishI keep forgetting to do that20:53
thingeedon't think 338796 is stalled ... the author has been active and waiting for a response from the tc20:53
dhellmannthe release team isn't going to use those for now20:53
thingeemordred: ^20:53
*** thorst_ has quit IRC20:53
sdakeflaper87 it makes it hard for me to find the original comments20:53
annegentle_thingee: yeah I'd agree with that assessment too20:53
russellbmestery voted on the tc vacancy review as well20:53
sdakeflaper87 but i guess I can unabandon them when I get around to it20:53
*** mickeys has joined #openstack-meeting20:53
flaper87sdake: yes20:53
*** blakec has joined #openstack-meeting20:53
dhellmannsdake : yes, please20:53
flaper87sdake: please :)20:53
sdaguesdake: owner:self status:abandoned20:53
flaper87sdake: both of them, if you don't mind20:54
sdagueit's easy to search for them20:54
mordredthingee: yah - it's on my list20:54
flaper87ok, who's out next week?20:54
fungioh, that reminds me we need the vmt to weigh in on https://review.openstack.org/350597 (which will just be a request to start with a thread on the -dev ml)20:54
sdakeflaper87 feel free to abandon them - they will be in my inbox20:54
thingeeflaper87: me20:54
thingeespain and burning man20:54
flaper87sdake: either you or ttx can do that :(20:54
dhellmannsdake : flaper87 doesn't have permission to do it20:54
sdakeflaper87 i'll get around to em some day when shit isn't on fire ;)20:54
sdakeoh ok20:54
sdakegot specific links?20:54
*** lpetrut has quit IRC20:55
anteayasdake: can we not swear please20:55
sdakesome day when things are not on fire20:55
dhellmannsdake : https://review.openstack.org/#/c/295971/ and https://review.openstack.org/#/c/295528/20:55
anteayathank you20:55
sdakethanks dhellmann20:55
flaper87sdake: https://review.openstack.org/29597120:55
flaper87sdake: https://review.openstack.org/29552820:55
flaper87so, thingee dims and myself will be out20:55
flaper87anyone else?20:55
annegentle_flaper87: your linking is on fire today :)20:55
dimsgood job flaper87 :)20:55
mtreinishflaper87: next week?20:55
flaper87sounds like there will be quorum so, there should be meeting20:55
dhellmannyeah, thanks again for being chair flaper8720:55
flaper87mtreinish: yes20:55
*** seldenr has quit IRC20:56
annegentle_flaper87: yeah thanks20:56
flaper87my pleasure :)20:56
*** shaohe_feng has quit IRC20:56
edleafeyeah - kudos flaper87!20:56
*** shaohe_feng has joined #openstack-meeting20:56
flaper87edleafe: annegentle_ danke danke :)20:56
flaper87ok, anything else pressing to discuss ?20:57
russellbthanks, flaper87, and enjoy your time off!20:57
*** radeks has joined #openstack-meeting20:57
flaper87otherwise, we can call it a meeting and be happy to have closed it a couple of mins earlier20:57
flaper87Or I can do the flaper87 thing and keep talking till time's up20:57
* flaper87 is Italian, he knows how to do that20:57
flaper87russellb: thanks :)20:57
sdaguethanks flaper8720:58
sdakeflaper87 your wish is my command :)20:58
* flaper87 bows20:58
flaper87ok, let's call it!20:58
flaper87thanks everyone20:58
flaper87have a great rest of your week20:58
amriththx flaper8720:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:58
openstackMeeting ended Tue Aug  9 20:58:28 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-08-09-20.01.html20:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-08-09-20.01.txt20:58
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-08-09-20.01.log.html20:58
*** leong has joined #openstack-meeting20:59
*** rfolco has quit IRC20:59
*** rfolco has joined #openstack-meeting20:59
*** rfolco has quit IRC21:00
*** cody-somerville has quit IRC21:00
*** leeantho_ has joined #openstack-meeting21:01
*** isunil has joined #openstack-meeting21:01
*** seldenr has joined #openstack-meeting21:01
*** leeantho has quit IRC21:02
*** annegentle_ has quit IRC21:02
stevemardims: for sure21:05
*** omghai2u has quit IRC21:05
*** enriquetaso has quit IRC21:06
*** shaohe_feng has quit IRC21:06
*** leong has left #openstack-meeting21:06
*** Sukhdev has quit IRC21:06
dimsstevemar : how was your presentation?21:06
*** shaohe_feng has joined #openstack-meeting21:06
*** dasanind_ has quit IRC21:08
*** s3wong has joined #openstack-meeting21:09
*** yamamoto has joined #openstack-meeting21:09
*** Sukhdev has joined #openstack-meeting21:09
*** leeantho_ has quit IRC21:10
*** karthikp_ has joined #openstack-meeting21:10
*** leeantho_ has joined #openstack-meeting21:11
*** yamamoto has quit IRC21:13
*** yamamoto has joined #openstack-meeting21:13
*** yamamoto has quit IRC21:13
*** yamamoto has joined #openstack-meeting21:15
*** yamamoto has quit IRC21:15
*** f13o has joined #openstack-meeting21:16
*** shaohe_feng has quit IRC21:16
*** isunil has quit IRC21:16
*** shaohe_feng has joined #openstack-meeting21:16
*** blakec has quit IRC21:17
*** ayoung has quit IRC21:19
*** radeks has quit IRC21:20
*** synegi has joined #openstack-meeting21:22
*** baumann_ has quit IRC21:23
*** rtheis has quit IRC21:23
stevemardims: was good i think :)21:24
*** gordc has left #openstack-meeting21:25
*** synegy34 has quit IRC21:26
*** shaohe_feng has quit IRC21:26
*** shaohe_feng has joined #openstack-meeting21:27
*** sindhu has joined #openstack-meeting21:28
*** leeantho_ has quit IRC21:29
*** iyamahat has joined #openstack-meeting21:30
*** zigo has quit IRC21:32
*** sindhu has quit IRC21:33
*** sindhu has joined #openstack-meeting21:33
*** eharney has quit IRC21:33
*** maishsk has quit IRC21:34
*** iyamahat has quit IRC21:34
*** zigo has joined #openstack-meeting21:35
*** cleong has quit IRC21:36
*** shaohe_feng has quit IRC21:37
*** jamesdenton has quit IRC21:37
*** shaohe_feng has joined #openstack-meeting21:37
*** cody-somerville has joined #openstack-meeting21:38
*** weshay has quit IRC21:38
*** julim has joined #openstack-meeting21:40
*** jmckind has quit IRC21:41
*** amitgandhinz has quit IRC21:41
*** amitgandhinz has joined #openstack-meeting21:42
*** seldenr has quit IRC21:45
*** shaohe_feng has quit IRC21:47
*** shaohe_feng has joined #openstack-meeting21:48
*** seldenr has joined #openstack-meeting21:50
*** designbybeck_ has quit IRC21:52
*** toddjohn has quit IRC21:54
*** esberglu has quit IRC21:55
*** dasanind_ has joined #openstack-meeting21:55
*** mickeys has quit IRC21:57
*** f13o has quit IRC21:57
*** shaohe_feng has quit IRC21:57
*** sdake has quit IRC21:57
*** mriedem has quit IRC21:57
*** mickeys has joined #openstack-meeting21:57
*** sindhu has quit IRC21:59
*** yamamoto has joined #openstack-meeting21:59
*** shaohe_feng has joined #openstack-meeting22:00
*** amitgandhinz has quit IRC22:00
*** bobh__ has quit IRC22:00
*** gouthamr has quit IRC22:01
*** mickeys has quit IRC22:01
*** rcernin has quit IRC22:02
*** sindhu has joined #openstack-meeting22:02
*** toscalix has joined #openstack-meeting22:03
*** karthikp_ has quit IRC22:03
*** alyson_ has quit IRC22:03
*** asettle has quit IRC22:04
*** jckasper has quit IRC22:05
*** jckasper has joined #openstack-meeting22:06
*** dimtruck is now known as zz_dimtruck22:06
*** xiaohhui has joined #openstack-meeting22:07
*** shaohe_feng has quit IRC22:07
*** shaohe_feng has joined #openstack-meeting22:08
*** jckasper_ has joined #openstack-meeting22:10
*** jckasper has quit IRC22:11
*** xiaohhui has quit IRC22:12
*** uxdanielle has quit IRC22:12
*** jckasper has joined #openstack-meeting22:13
*** jckasper_ has quit IRC22:15
*** jckasper_ has joined #openstack-meeting22:15
*** jaypipes has quit IRC22:17
*** jckasper has quit IRC22:17
*** dasanind_ has quit IRC22:18
*** shaohe_feng has quit IRC22:18
*** efried has quit IRC22:18
*** shaohe_feng has joined #openstack-meeting22:18
*** jckasper_ has quit IRC22:20
*** iyamahat has joined #openstack-meeting22:20
*** itzdilip has quit IRC22:21
*** Julien-zte has joined #openstack-meeting22:25
*** davidlenwell has quit IRC22:25
*** tonytan4ever has quit IRC22:26
*** shaohe_feng has quit IRC22:28
*** tpsilva has quit IRC22:28
*** tonytan4ever has joined #openstack-meeting22:28
*** shaohe_feng has joined #openstack-meeting22:29
*** sdake has joined #openstack-meeting22:30
*** sdake has quit IRC22:30
*** sdake has joined #openstack-meeting22:30
*** sarob has joined #openstack-meeting22:32
*** sdake_ has joined #openstack-meeting22:33
*** sdake has quit IRC22:34
*** toddjohn has joined #openstack-meeting22:35
*** sarob has quit IRC22:37
*** davidlenwell has joined #openstack-meeting22:38
*** shaohe_feng has quit IRC22:38
*** sdake_ is now known as sdake22:38
*** singlethink has quit IRC22:40
*** vishnoianil has quit IRC22:40
*** toddjohn has quit IRC22:40
*** toscalix has quit IRC22:40
*** galstrom is now known as galstrom_zzz22:41
*** LamT_ has quit IRC22:41
*** toddjohn has joined #openstack-meeting22:41
*** itlinux has joined #openstack-meeting22:42
*** shaohe_feng has joined #openstack-meeting22:43
*** Jeff_Collins has joined #openstack-meeting22:46
*** itlinux has quit IRC22:46
*** seldenr has quit IRC22:48
*** shaohe_feng has quit IRC22:48
*** Jeffreyc42 has quit IRC22:49
*** rbak has quit IRC22:49
*** Jeff_Collins has quit IRC22:51
*** shaohe_feng has joined #openstack-meeting22:51
*** cloudrancher has quit IRC22:52
*** yamamoto has quit IRC22:52
*** dasanind_ has joined #openstack-meeting22:52
*** toscalix has joined #openstack-meeting22:55
*** toscalix has quit IRC22:55
*** toscalix has joined #openstack-meeting22:57
*** shaohe_feng has quit IRC22:59
*** dasanind_ has quit IRC22:59
*** shaohe_feng has joined #openstack-meeting22:59
*** sindhu has quit IRC22:59
*** JoseMello has quit IRC23:00
*** amitgandhinz has joined #openstack-meeting23:01
*** yamamoto has joined #openstack-meeting23:05
*** yamamoto has quit IRC23:05
*** amitgandhinz has quit IRC23:05
*** yamamoto has joined #openstack-meeting23:07
*** shaohe_feng has quit IRC23:09
*** shaohe_feng has joined #openstack-meeting23:09
*** b1airo has joined #openstack-meeting23:09
*** yamamoto has quit IRC23:11
*** yamamoto has joined #openstack-meeting23:11
*** yamamoto has quit IRC23:11
*** hemna is now known as hemnafk23:12
*** sdague has quit IRC23:15
*** Sukhdev has quit IRC23:15
*** karthikp_ has joined #openstack-meeting23:15
*** yamamoto has joined #openstack-meeting23:15
*** karthikp_ has quit IRC23:16
*** Sukhdev has joined #openstack-meeting23:16
*** karthikp_ has joined #openstack-meeting23:16
*** rrecio_ has quit IRC23:18
*** shaohe_feng has quit IRC23:19
*** david-lyle has quit IRC23:20
*** merooney has joined #openstack-meeting23:20
*** yamamoto has quit IRC23:20
*** shaohe_feng has joined #openstack-meeting23:20
*** Swami has quit IRC23:21
*** karthikp_ has quit IRC23:21
*** saju_m has quit IRC23:22
*** samP has joined #openstack-meeting23:24
*** yamamoto has joined #openstack-meeting23:27
*** bobh has joined #openstack-meeting23:27
*** yamamoto has quit IRC23:27
*** roxanaghe has quit IRC23:29
*** shaohe_feng has quit IRC23:29
*** cardeois has quit IRC23:30
*** shaohe_feng has joined #openstack-meeting23:30
*** iyamahat has quit IRC23:30
*** mickeys has joined #openstack-meeting23:32
*** gongysh has joined #openstack-meeting23:32
*** vishnoianil has joined #openstack-meeting23:35
*** xyang1 has quit IRC23:35
*** karthikp_ has joined #openstack-meeting23:35
*** ayoung has joined #openstack-meeting23:35
*** mmalik4 has quit IRC23:37
*** david-lyle has joined #openstack-meeting23:38
*** rubasov has quit IRC23:39
*** jamesdenton has joined #openstack-meeting23:39
*** cody-somerville has quit IRC23:39
*** cody-somerville has joined #openstack-meeting23:39
*** cody-somerville has quit IRC23:39
*** cody-somerville has joined #openstack-meeting23:39
*** shaohe_feng has quit IRC23:40
*** shaohe_feng has joined #openstack-meeting23:40
*** csomerville has joined #openstack-meeting23:41
*** zhurong has joined #openstack-meeting23:43
*** cody-somerville has quit IRC23:45
*** sdake has quit IRC23:45
*** gyee_ has joined #openstack-meeting23:47
*** gyee_ has quit IRC23:47
*** Julien-zte has quit IRC23:48
*** karthik__ has joined #openstack-meeting23:49
*** Patifa has quit IRC23:49
*** karthikp_ has quit IRC23:49
*** bobh has quit IRC23:50
*** shaohe_feng has quit IRC23:50
*** shaohe_feng has joined #openstack-meeting23:50
*** b1airo has quit IRC23:53
*** katomo has joined #openstack-meeting23:54
*** esberglu has joined #openstack-meeting23:56
*** Fdaisuke has quit IRC23:56
*** liuhanxi has joined #openstack-meeting23:57
*** esberglu has quit IRC23:57
*** rcarrillocruz has quit IRC23:58
*** spzala has quit IRC23:59
*** rcarrillocruz has joined #openstack-meeting23:59
*** spzala has joined #openstack-meeting23:59

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