Thursday, 2015-08-20

*** FallenPegasus has joined #openstack-meeting-400:00
*** xingchao has joined #openstack-meeting-400:00
*** bnemec has joined #openstack-meeting-400:03
*** SimonChung has joined #openstack-meeting-400:03
*** geoffarn_ has quit IRC00:04
*** xingchao has quit IRC00:04
*** geoffarnold has joined #openstack-meeting-400:06
*** SimonChung1 has joined #openstack-meeting-400:06
*** SimonChung has quit IRC00:08
*** geoffarnold has quit IRC00:10
*** banix has quit IRC00:10
*** bnemec has quit IRC00:10
*** padkrish has quit IRC00:14
*** padkrish has joined #openstack-meeting-400:15
*** padkrish has quit IRC00:19
*** armax has quit IRC00:20
*** armax has joined #openstack-meeting-400:22
*** padkrish has joined #openstack-meeting-400:22
*** armax has quit IRC00:24
*** bnemec has joined #openstack-meeting-400:25
*** padkrish has quit IRC00:27
*** dannywil_ has quit IRC00:28
*** salv-orl_ has quit IRC00:29
*** dims has joined #openstack-meeting-400:30
*** padkrish has joined #openstack-meeting-400:30
*** bnemec has quit IRC00:30
*** padkrish has quit IRC00:34
*** padkrish has joined #openstack-meeting-400:37
*** xingchao has joined #openstack-meeting-400:39
*** FallenPegasus has quit IRC00:43
*** bnemec has joined #openstack-meeting-400:44
*** sigmavirus24 is now known as sigmavirus24_awa00:46
*** xichengc has joined #openstack-meeting-400:51
*** VW_ has quit IRC00:51
*** VW_ has joined #openstack-meeting-400:52
*** shuoy has joined #openstack-meeting-400:52
*** chizhang has joined #openstack-meeting-400:54
*** chizhang has quit IRC00:54
*** shuoy has left #openstack-meeting-400:55
*** xuhan has joined #openstack-meeting-400:55
*** shuoy has joined #openstack-meeting-400:55
*** baigk has joined #openstack-meeting-400:55
*** chenshuai has joined #openstack-meeting-400:56
*** VW_ has quit IRC00:57
* xichengc waves hello to shuoy00:57
shuoyHi xichengc, let’s start our meeting in 2 mins.00:57
xichengcOK shuoy00:57
*** harshs has quit IRC00:58
chenshuaiHi00:58
*** vishwanathj has quit IRC00:58
*** xingchao has quit IRC00:58
*** chizhang has joined #openstack-meeting-400:59
shuoy#wave chenshuai00:59
xichengcHi chenshuai00:59
xichengcIs chigang joining>00:59
xichengc?00:59
chenshuaiyes00:59
xichengcok thanks00:59
shuoyYes, chigang is online, I think.00:59
chizhanghello, everyone00:59
* chigang wave to xichengc00:59
xichengchi chigang01:00
shuoy#startmeeting01:00
openstackshuoy: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'01:00
chigangxichengc: hi01:00
shuoy#startmeeting Compass online design session01:00
openstackMeeting started Thu Aug 20 01:00:19 2015 UTC and is due to finish in 60 minutes.  The chair is shuoy. Information about MeetBot at http://wiki.debian.org/MeetBot.01:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:00
*** openstack changes topic to " (Meeting topic: Compass online design session)"01:00
openstackThe meeting name has been set to 'compass_online_design_session'01:00
shuoyHi everyone, let’s get started for the meeting with 3 topics: 1) Status on Ansible; 2) Improved support of networking config; 3) Shall we prepare for "rule the stack" contest, which is sponsored by Intel at past Summits.01:01
shuoyLet’s go through them one by one01:01
shuoy#topic  1) Status on Ansible;01:02
*** openstack changes topic to "1) Status on Ansible; (Meeting topic: Compass online design session)"01:02
shuoyxichengc, can you give the context and update this?01:03
xichengcyes, the upstream OSAD(openstack-ansible-deployment) repo deploys openstack components onto baremetal servers, with some of the components in Linux containers01:03
*** grace-yu has joined #openstack-meeting-401:04
xichengcI have created an etherpad at https://etherpad.openstack.org/p/compass-osad-integration01:04
shuoyxichengc: have you talked/engaged with the OSAD developers?01:05
xichengcI have not. I think the interactions should be based on further understanding of OSAD playbooks.01:06
xichengcwhich is the ungoing effort, and should be done soon.01:06
*** FallenPegasus has joined #openstack-meeting-401:06
*** baoli has joined #openstack-meeting-401:07
xichengcI am iterating through the playbooks to assess all the necessary parameters that will have to come from compass.01:07
xichengcafter I have finished updating the etherpad, I will engage more with OSAD developers, with questions.01:08
shuoy#action xichengc, try to reach out OSAD developer and see if they are willing to help out accelerate the OSAD understanding repos; and give OSAD developers the context and background of this engagement.01:08
chigangxichengc: is it support HA controller?01:08
*** tfukushima has quit IRC01:08
xichengcit does, as well as active/active queue and galera mysql db HA01:08
*** tfukushima has joined #openstack-meeting-401:09
chigangwell01:09
xichengc#action xichengc: wrap up OSAD understanding process.01:09
xichengcchigang01:09
xichengcHas baiguoku got a chance to look at OSAD?01:09
baigka little01:10
xichengccould you take some time to see if you can deploy a minimal environment using OSAD?01:11
*** baoli has quit IRC01:12
chigangwhat is mean of minial environment? Can you clear it more? In one baremetal?01:12
*** xingchao has joined #openstack-meeting-401:12
*** yamamoto has joined #openstack-meeting-401:12
xichengcall in one would be good enough01:12
shuoychigang/baigk: the high level idea is this: ‘if we can use OSAD solution as our Ansible playbook for the containerized components, then we are going to use OSAD as our target system driver’ — this is what OpenStack community would love to see: avoid duplicated work if possible01:13
baigkOK, I will try01:13
shuoybaigk: and the upside of doing this is that in the long run, OSAD become a solution plug-in for Compass.01:14
xichengc#action baigk: try to deploy an openstack cluster onto one baremetal machine using OSAD solutions.01:14
shuoyxichengc: please involve baigk at the right moment during conversation with OSAD team.01:15
xichengcwill do.01:15
xichengcmoving on?01:16
chigangI think OSAD will be online deployment.01:16
chigang#unod01:16
chigang#undo01:16
chigangsorry,  I misunderstand01:17
shuoyI would love to see the OPNFV requirement (which is basically some kind of spec) get translated into OSAD code — one stone two birds to maximize the OSAD code base usage.01:17
shuoyLet’s move on the next topic.01:17
chigangsure01:17
shuoy#topic 2) Improved support of networking config01:17
*** openstack changes topic to "2) Improved support of networking config (Meeting topic: Compass online design session)"01:17
shuoychigang, can you please explain the context and problem statement for this item?01:18
xuhannow,  al network is configured by os_installer01:19
xuhanit's unable to support more complex networking01:20
shuoyxuhan: so we would love to see network configuration “late binding”, is that the correct interpretation?01:20
xuhanfor example, we can not use one intf support two logic network01:20
xuhanyes01:20
xichengc#agreed01:20
xuhanlike bonding01:20
xuhanvlan setting01:20
xuhanovs bridge prepare01:21
*** sdake_ has joined #openstack-meeting-401:21
shuoyxichangc, will this be a proper task for late stage configuration? (e.g., Ansible stage)01:21
xichengcxuhan, so the networking config should be independent from any installers, in a global level>01:21
xuhanyes01:22
xuhanI has completed the preliminary implemention01:22
xuhaninstall network is configured by the cobblerm, use DHCP01:22
xuhanand other network(mgmt, storage, tenant, external) is configured by Ansible.01:22
xuhanconfig file reference to FusionSphere's config file01:22
xichengcshuoy, yes01:22
xichengcOSAD should be able to do that as well.01:23
shuoyxuhan: try to make sure our solution follow the OSAD framework — i.e., make the networking configuration part a relatively independent module so that OSAD community is more willing to accept it.01:24
shuoyok, any action item on this one?01:24
*** sdake has quit IRC01:25
*** dims has quit IRC01:25
chigang#action Xuhan try to contribute the network config in OSAD framework01:25
xuhanOK, I'd like a general outline to begin with OSAD01:26
chigangxuhan: shuoy: is it OK?01:26
*** xichengc has quit IRC01:27
shuoy#action Xuhan co-ordinate with xichengc to reach out OSAD team regarding our motivation, and why this is valuable to OSAD (I suppose they may also want to achieve ’network configuration late binding’)01:28
shuoychigang: yes, this is great. Let’s move on to next topic.01:28
chigangsure:)01:29
shuoy#topic 3) Shall we prepare for "rule the stack" contest?01:29
*** openstack changes topic to "3) Shall we prepare for "rule the stack" contest? (Meeting topic: Compass online design session)"01:29
shuoy#info https://01.org/openstack/openstacksummitvancouverbc2015/rule-stack-vancouver is the context of this topic.01:30
*** Brd_ has quit IRC01:31
chigangIs it ongoing?01:31
shuoyhere is what I would suggest on this subject, let Compass developers in Shanghai read the ‘rule the stack’ document, may even engage Intel Shanghai OTG (opensource technology group) and see whether we can do this.01:32
*** xichengc has joined #openstack-meeting-401:33
shuoychigang, it is a kind of contest across openstack installers — to see which one is a robust and quick installer.01:33
xichengc#info xicheng chang01:33
*** padkrish has quit IRC01:33
xichengcGot disconnected, sorry01:33
shuoywelcome back01:34
xichengcAre we on the 3rd topic?01:34
*** s3wong has quit IRC01:35
*** asselin has left #openstack-meeting-401:35
shuoyso let’s defer the decision of this (whether we want to participate that kind of contest) to the next IRC meeting01:35
chigangshuoy: interesting! it is game in intallers.01:35
shuoyyes, we are on the 3rd topic.01:35
shuoychigang: yes01:35
xichengcpreparing for this would require some time, I don't think we have a chance to win this contest01:36
shuoyxichengc: I just said that we at least defer this decision to next IRC meeting.01:37
xichengcSure. Thanks, shuoy01:37
shuoychigang, for better community building-up, it does not hurt if you guys can engage Intel OTG in the Shanghai office.01:38
*** xuhan1 has joined #openstack-meeting-401:38
*** xuhan has quit IRC01:39
*** xuhan1 is now known as xuhan01:39
shuoyOk, I think we have already have all the topics discussed. Any thing that ppl in this meeting want to bring up?01:39
*** yamamoto has quit IRC01:40
chigangshuoy: do you know someone from OTG?01:40
shuoyI will try to help you link with someone.01:40
chigangshuoy: thanks01:40
shuoy#action: shuoy to engages Intel developers and see if they are interested in Compass project01:41
xichengcquestion: what did we conclude from the 2nd topic?01:42
xichengcsorry i missed that part01:42
shuoy1) Xuhan co-ordinate with xichengc to reach out OSAD team regarding our motivation, and why this is valuable to OSAD (I suppose they may also want to achieve ’network configuration late binding’); 2) Xuhan try to contribute the network config in OSAD framework01:43
shuoyno other topics? counting once…01:43
shuoyno other topics? counting twice…01:44
xichengcthanks01:44
shuoyok, thanks to everyone for the time. See you next time01:44
*** xichengc has quit IRC01:44
shuoy#endmeeting01:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"01:44
openstackMeeting ended Thu Aug 20 01:44:54 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)01:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/compass_online_design_session/2015/compass_online_design_session.2015-08-20-01.00.html01:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/compass_online_design_session/2015/compass_online_design_session.2015-08-20-01.00.txt01:44
openstackLog:            http://eavesdrop.openstack.org/meetings/compass_online_design_session/2015/compass_online_design_session.2015-08-20-01.00.log.html01:45
*** britthouser has joined #openstack-meeting-401:45
*** chizhang has quit IRC01:45
*** grace-yu has quit IRC01:45
*** britthou_ has joined #openstack-meeting-401:46
*** britthouser has quit IRC01:50
*** shuoy has quit IRC01:51
*** britthou_ has quit IRC01:52
*** britthouser has joined #openstack-meeting-401:54
*** britthou_ has joined #openstack-meeting-401:55
*** britthouser has quit IRC01:59
*** ajmiller has joined #openstack-meeting-401:59
*** ajmiller_ has joined #openstack-meeting-402:02
*** ajmiller has quit IRC02:05
*** banix has joined #openstack-meeting-402:06
*** baoli has joined #openstack-meeting-402:08
*** jerryz has quit IRC02:10
*** baoli has quit IRC02:12
*** xuhan has quit IRC02:15
*** dims has joined #openstack-meeting-402:21
*** xuhan has joined #openstack-meeting-402:21
*** vivek-ebay has quit IRC02:22
*** xuhan has quit IRC02:24
*** vivek-ebay has joined #openstack-meeting-402:28
*** vivek-ebay has quit IRC02:28
*** dims has quit IRC02:29
*** dims has joined #openstack-meeting-402:30
*** harshs has joined #openstack-meeting-402:33
*** dims has quit IRC02:34
*** yamamoto has joined #openstack-meeting-402:40
*** vinsh has quit IRC02:42
*** salv-orlando has joined #openstack-meeting-402:44
*** markvoelker has quit IRC02:46
*** ivar-laz_ has joined #openstack-meeting-402:46
*** sbalukoff has quit IRC02:46
*** ivar-lazzaro has quit IRC02:49
*** ivar-laz_ has quit IRC02:50
*** xuhan has joined #openstack-meeting-402:51
*** britthou_ has quit IRC02:51
*** salv-orlando has quit IRC02:51
*** yamahata has quit IRC02:53
*** salv-orlando has joined #openstack-meeting-402:55
*** salv-orlando has quit IRC03:02
*** armax has joined #openstack-meeting-403:15
*** nhairston has joined #openstack-meeting-403:17
*** baoli has joined #openstack-meeting-403:23
*** jerryz has joined #openstack-meeting-403:27
*** baoli has quit IRC03:28
*** harshs has quit IRC03:31
*** nhairston has quit IRC03:33
*** vivek-ebay has joined #openstack-meeting-403:37
*** VW_ has joined #openstack-meeting-403:38
*** VW_ has quit IRC03:39
*** VW_ has joined #openstack-meeting-403:40
*** vivek-eb_ has joined #openstack-meeting-403:43
*** vivek-ebay has quit IRC03:43
*** VW_ has quit IRC03:45
*** VW_ has joined #openstack-meeting-403:45
*** markvoelker has joined #openstack-meeting-403:46
*** banix has quit IRC03:49
*** VW_ has quit IRC03:50
*** markvoelker has quit IRC03:51
*** KunalGan_ has quit IRC04:08
*** irenab has quit IRC04:09
*** irenab has joined #openstack-meeting-404:11
*** chenshuai has quit IRC04:12
*** lakshmiS has joined #openstack-meeting-404:20
*** baoli has joined #openstack-meeting-404:24
*** baoli has quit IRC04:29
*** fawadkhaliq has joined #openstack-meeting-404:32
*** salv-orlando has joined #openstack-meeting-404:32
*** harshs has joined #openstack-meeting-404:32
*** vivek-ebay has joined #openstack-meeting-404:35
*** salv-orlando has quit IRC04:35
*** vivek-eb_ has quit IRC04:38
*** Sukhdev has joined #openstack-meeting-404:43
*** salv-orlando has joined #openstack-meeting-404:47
*** Sukhdev has quit IRC04:47
*** xuhan has quit IRC04:48
*** salv-orlando has quit IRC04:51
*** Sukhdev has joined #openstack-meeting-404:58
*** harshs has quit IRC04:59
*** lakshmiS_ has joined #openstack-meeting-405:01
*** ajmiller_ has quit IRC05:02
*** lakshmiS has quit IRC05:02
*** FallenPegasus has quit IRC05:05
*** sdake has joined #openstack-meeting-405:07
*** sdake_ has quit IRC05:11
*** jpekkari has joined #openstack-meeting-405:16
*** irenab has quit IRC05:21
*** Sukhdev has quit IRC05:26
*** irenab has joined #openstack-meeting-405:32
*** xuhan has joined #openstack-meeting-405:33
*** vivek-ebay has quit IRC05:37
*** amotoki has quit IRC05:39
*** geoffarnold has joined #openstack-meeting-405:39
*** geoffarnold has quit IRC05:43
*** geoffarnold has joined #openstack-meeting-405:43
*** geoffarnold is now known as geoffarnoldX05:45
*** nkrinner has joined #openstack-meeting-405:52
*** numan has joined #openstack-meeting-405:55
*** sankarshan_away is now known as sankarshan05:56
*** armax has quit IRC06:00
*** zeih has joined #openstack-meeting-406:01
*** salv-orlando has joined #openstack-meeting-406:05
*** zeih has quit IRC06:06
*** VW_ has joined #openstack-meeting-406:09
*** amotoki has joined #openstack-meeting-406:09
*** xuhan has quit IRC06:14
*** ajayaa has joined #openstack-meeting-406:14
*** salv-orlando has quit IRC06:16
*** VW_ has quit IRC06:21
*** VW_ has joined #openstack-meeting-406:21
*** xuhan has joined #openstack-meeting-406:24
*** jerryz has quit IRC06:28
*** salv-orlando has joined #openstack-meeting-406:32
*** ajayaa has quit IRC06:37
*** fawadkhaliq has quit IRC06:45
*** ajayaa has joined #openstack-meeting-406:50
*** fawadkhaliq has joined #openstack-meeting-407:09
*** nkrinner has quit IRC07:17
*** yamamoto has quit IRC07:19
*** nkrinner has joined #openstack-meeting-407:21
*** xuhan1 has joined #openstack-meeting-407:28
*** xuhan has quit IRC07:29
*** xuhan has joined #openstack-meeting-407:30
*** xuhan1 has quit IRC07:32
*** xuhan has quit IRC07:37
*** xuhan has joined #openstack-meeting-407:37
*** tfukushima has quit IRC07:38
*** salv-orlando has quit IRC07:40
*** yamamoto has joined #openstack-meeting-407:40
*** xuhan has quit IRC07:41
*** markvoelker has joined #openstack-meeting-407:48
*** markvoelker has quit IRC07:53
*** salv-orlando has joined #openstack-meeting-407:55
*** lakshmiS_ has quit IRC07:56
*** lakshmiS_ has joined #openstack-meeting-407:56
*** yamahata has joined #openstack-meeting-408:00
*** tfukushima has joined #openstack-meeting-408:00
*** akwasnie has joined #openstack-meeting-408:09
*** zeih has joined #openstack-meeting-408:17
*** fawadkhaliq has quit IRC08:23
*** fawadkhaliq has joined #openstack-meeting-408:26
*** xingchao has quit IRC08:28
*** VW_ has quit IRC08:36
*** VW_ has joined #openstack-meeting-408:36
*** chenshuai has joined #openstack-meeting-408:37
*** VW_ has quit IRC08:40
*** zeih has quit IRC08:48
*** zeih has joined #openstack-meeting-408:50
*** ashtokol_ has joined #openstack-meeting-408:55
*** ashtokol_ has quit IRC08:55
*** ashtokol_ has joined #openstack-meeting-408:56
*** yamamoto has quit IRC09:04
*** 7GHAAZ22K has joined #openstack-meeting-409:04
*** fawadkhaliq has quit IRC09:08
*** ashtokol_ has quit IRC09:09
*** sbalukoff has joined #openstack-meeting-409:09
*** sdake_ has joined #openstack-meeting-409:18
*** sdake has quit IRC09:21
*** yamahata has quit IRC09:32
*** britthouser has joined #openstack-meeting-409:32
*** britthou_ has joined #openstack-meeting-409:33
*** ajo has joined #openstack-meeting-409:36
*** ajo has left #openstack-meeting-409:36
*** openkarma has joined #openstack-meeting-409:37
*** britthouser has quit IRC09:37
*** openkarma has quit IRC09:38
*** lakshmiS_ has quit IRC09:43
*** openkarma has joined #openstack-meeting-409:44
*** openkarma has quit IRC09:44
*** markvoelker has joined #openstack-meeting-409:49
*** markvoelker has quit IRC09:54
*** dims has joined #openstack-meeting-409:56
*** fawadkhaliq has joined #openstack-meeting-409:58
*** amotoki has quit IRC10:08
*** fawadkhaliq has quit IRC10:13
*** bharath_ has joined #openstack-meeting-410:13
*** sdake_ is now known as sdake10:15
*** jpekkari has quit IRC10:15
*** jpekkari has joined #openstack-meeting-410:17
*** britthou_ has quit IRC10:20
*** zeih has quit IRC10:23
*** 7GHAAZ22K has quit IRC10:25
*** ashtokol_ has joined #openstack-meeting-410:36
*** fawadkhaliq has joined #openstack-meeting-410:38
*** zeih has joined #openstack-meeting-410:50
*** xingchao has joined #openstack-meeting-410:51
*** lazy_prince has joined #openstack-meeting-410:52
*** xingchao has quit IRC10:55
*** ashtokol_ has quit IRC11:09
*** britthouser has joined #openstack-meeting-411:12
*** yamamoto_ has joined #openstack-meeting-411:14
*** dims has quit IRC11:15
*** dims has joined #openstack-meeting-411:16
*** lakshmiS has joined #openstack-meeting-411:17
*** dims has quit IRC11:20
*** baoli has joined #openstack-meeting-411:25
*** baoli has quit IRC11:30
*** dims has joined #openstack-meeting-411:33
*** markvoelker has joined #openstack-meeting-411:35
*** woodard has joined #openstack-meeting-411:40
*** markvoelker has quit IRC11:40
*** yamamoto_ has quit IRC11:44
*** xingchao has joined #openstack-meeting-411:45
*** woodard has quit IRC11:45
*** salv-orlando has quit IRC11:45
*** woodard has joined #openstack-meeting-411:46
*** xingchao has quit IRC11:50
*** britthouser has quit IRC11:55
*** klamath has joined #openstack-meeting-412:10
*** salv-orlando has joined #openstack-meeting-412:11
*** jmckind has quit IRC12:12
*** singlethink has joined #openstack-meeting-412:13
*** bharath_ has quit IRC12:13
*** singleth_ has joined #openstack-meeting-412:14
*** sdake has quit IRC12:17
*** singlethink has quit IRC12:17
*** fawadkhaliq has quit IRC12:24
*** singleth_ has quit IRC12:27
*** banix has joined #openstack-meeting-412:32
*** britthouser has joined #openstack-meeting-412:36
*** chenshuai has quit IRC12:36
*** sankarshan is now known as sankarshan_away12:38
*** markvoelker has joined #openstack-meeting-412:39
*** chenshuai has joined #openstack-meeting-412:40
*** banix has quit IRC12:40
*** xingchao has joined #openstack-meeting-412:43
*** yamamoto has joined #openstack-meeting-412:44
*** VW_ has joined #openstack-meeting-412:49
*** yamamoto has quit IRC12:49
*** yamamoto has joined #openstack-meeting-412:51
*** yamamoto has quit IRC12:51
*** yamamoto has joined #openstack-meeting-412:52
*** yamamoto has quit IRC12:52
*** yamamoto has joined #openstack-meeting-412:52
*** xingchao has quit IRC12:56
*** jpekkari has quit IRC13:00
*** VW_ has quit IRC13:05
*** singlethink has joined #openstack-meeting-413:07
*** aventerav has joined #openstack-meeting-413:07
*** VW_ has joined #openstack-meeting-413:08
*** ashtokol_ has joined #openstack-meeting-413:09
*** chenshuai has quit IRC13:10
*** sankarshan_away is now known as sankarshan13:13
*** VW_ has quit IRC13:14
*** VW_ has joined #openstack-meeting-413:15
*** rfolco has joined #openstack-meeting-413:15
*** ajayaa has quit IRC13:18
*** krtaylor has quit IRC13:18
*** VW_ has quit IRC13:19
*** woodard has quit IRC13:23
*** fawadkhaliq has joined #openstack-meeting-413:24
*** bogdando has quit IRC13:25
*** bogdando has joined #openstack-meeting-413:25
*** chenshuai has joined #openstack-meeting-413:26
*** fawadkhaliq has quit IRC13:28
*** krtaylor has joined #openstack-meeting-413:31
*** woodard has joined #openstack-meeting-413:33
*** xingchao has joined #openstack-meeting-413:34
*** dims_ has joined #openstack-meeting-413:35
*** woodard has quit IRC13:38
*** dims has quit IRC13:39
*** geoffarnoldX is now known as geoffarnold13:42
*** dims_ has quit IRC13:44
*** dims has joined #openstack-meeting-413:46
*** fawadkhaliq has joined #openstack-meeting-413:48
*** bpoulos has joined #openstack-meeting-413:51
*** jecarey has joined #openstack-meeting-413:51
*** shalq has joined #openstack-meeting-413:52
*** tfukushima has quit IRC13:57
nikhil_kCourtesy meeting reminder: ativelkov, cpallares, esheffield, flaper87, flwang1, hemanthm, ivasilevskaya, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k, Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, zhiyan, pkoniszewski, krykowski, ajayaa, GB21, bpoulos, harshs, abhishekk, bunting, dshakhray13:59
*** chenshuai has quit IRC13:59
*** singleth_ has joined #openstack-meeting-413:59
nikhil_k#startmeeting glance14:00
openstackMeeting started Thu Aug 20 14:00:07 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: glance)"14:00
*** bunting has joined #openstack-meeting-414:00
openstackThe meeting name has been set to 'glance'14:00
nikhil_k#topic agenda and roll call14:00
*** openstack changes topic to "agenda and roll call (Meeting topic: glance)"14:00
nikhil_k#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:00
*** singlet__ has joined #openstack-meeting-414:02
nikhil_kit would be best to cancle this meeting if no one is around14:02
*** singlethink has quit IRC14:03
buntingprobably so14:03
*** mclaren has joined #openstack-meeting-414:03
*** sigmavirus24_awa is now known as sigmavirus2414:03
bpouloso/14:03
sigmavirus24o/14:03
*** singlethink has joined #openstack-meeting-414:03
mclareno/14:03
hemanthmo/14:03
rosmaitao/14:03
sigmavirus24nikhil_k: just running a couple minutes late, sorry14:03
nikhil_ksigmavirus24: np :)14:04
shalqwhat's the first topic ?14:04
*** harshs has joined #openstack-meeting-414:05
*** singleth_ has quit IRC14:05
mfedosino/14:05
nikhil_kI was waiting to see if anyone - ativelkov mfedosin or by anyone else, artifacts related updates can be provided14:05
harshso/14:05
mfedosinwe're fixing the bugs to adopt artifacts in Murano14:06
*** singlet__ has quit IRC14:06
mfedosincurrently I'm implementing filtering by ranges14:06
mfedosinMurano needs it to fetch versions like it's done in pip14:07
mfedosinfor example >=1.0.0, <=2.0.014:07
nikhil_kI think we still need to work out the API14:08
mfedosinI think it's a question to Alex14:08
nikhil_kyep and since there are no updates on14:08
nikhil_khttps://etherpad.openstack.org/p/glance-v3-api14:08
mfedosinI will publish my proposals next week about API14:08
nikhil_kit would be best to get some here or via email14:09
nikhil_kthat would be good, mfedosin14:09
mfedosinindependently from existing14:09
sigmavirus24is the v3 API spec still in flux?14:09
sigmavirus24(question to mfedosin who seems to know what ativelkov is thinking/doing)14:09
mfedosinso we can discuss it next Monday14:09
nikhil_ksigmavirus24: that's the to-be formal proposal14:10
nikhil_kthat == etherpad details14:10
mfedosinhis activity most in Murano14:10
sigmavirus24nikhil_k: I mean the spec that was in review for glance-specs around the v3 API14:10
nikhil_kah14:10
sigmavirus24The thing is that was still in flux14:10
sigmavirus24Even though we've merged v3 API code14:10
*** geoffarnold has quit IRC14:10
sigmavirus24And now we have a consumer for that API14:10
mfedosincurrently he's sitting behind me14:11
sigmavirus24And that spec was supposed to change to reflect API wg objects14:11
sigmavirus24*objections14:11
sigmavirus24But now that will be much harder with murano (prematurely) adopting the API14:11
nikhil_ksigmavirus24: right and the EXPERIMENTAL flag would change once those concerns are resolved14:11
sigmavirus24nikhil_k: sure14:11
*** ajayaa has joined #openstack-meeting-414:11
nikhil_kand any consumers would need to adopt the same14:11
sigmavirus24Just seems like the murano team will get angry at us no matter what happens14:11
nikhil_kright, and that clause needs to be clear14:12
sigmavirus24(considering they were angry at the summit that artifacts wasn't already merged)14:12
mfedosinit's not about Murano team, but our management :)14:12
nikhil_kso, question: will murano not be angry if ativelkov is willing to accept this change in the artifacts API?14:12
mfedosinand Alex is here to make them not be angry at us14:13
nikhil_kthere's a bus factor14:13
sigmavirus24okay14:13
nikhil_kbut best of what we have14:13
nikhil_kcool14:13
sigmavirus24I'm just making sure everyone knows the risks murano is taking right now14:13
mfedosinhe's a liason between Murano and Glance14:13
ativelkovoops, sorry for being late guys. I am right in the middle of murano's voice meeting14:13
*** ajmiller has joined #openstack-meeting-414:13
sigmavirus24hah14:13
sigmavirus24no worries ativelkov that's why we have mfedosin14:13
ativelkovmultitaking i hard for me14:13
nikhil_kmfedosin: it would be nice to state that in the wiki14:13
sigmavirus24you two do share a datalink between your brains right?14:13
ativelkovso, murano is aware about experimental nature of our API14:14
nikhil_kmfedosin: ativelkov : can anyone of you please update this etherpad with details about liaisons?14:14
nikhil_k#link https://wiki.openstack.org/wiki/CrossProjectLiaisons#Inter-project_Liaisons14:14
ativelkovthey (actually, we) are ok with v3 API changing any time14:14
ativelkovnikhil_k: I will14:15
nikhil_kgreat14:15
mfedosinnikhil_k, will be done14:15
nikhil_kthanks ativelkov14:15
*** lakshmiS has quit IRC14:15
nikhil_k:)14:15
*** chenshuai1 has joined #openstack-meeting-414:15
nikhil_ksigmavirus24: any more concerns before we move to reviews?14:15
sigmavirus24Nope14:15
ativelkovSo, right now there are a number of bugs in the code which is already merged14:15
ativelkovand we'd like them to be fixed before doing the major redesign of v3 API14:16
ativelkovboth mfedosin and me are working on that14:16
sigmavirus24ativelkov: that makes sense, sounded like new features were being added too14:16
sigmavirus24that's why I asked about the spec (I haven't had time to check on it yet)14:16
nikhil_kativelkov: so, I think the plan should be keeping v3 experimental for Liberty?14:16
ativelkovI've asked the new mmber of our team (Kairat) to move that etherpad to specs14:16
ativelkovnikhil_k: I think so, as FF is coming14:16
nikhil_kthat would be excellent14:17
*** TravT has joined #openstack-meeting-414:17
nikhil_kativelkov: FF is per project14:17
*** yamamoto has quit IRC14:17
nikhil_kand doesn't apply to experimental and non-verlaping features14:17
ativelkovah, that's cool to hear14:17
mfedosinI think we should discuss it more detailed on the summit before making api stable14:17
nikhil_kcool, sounds like a good plan14:18
nikhil_k#topic Reviews, Bugs and Releases14:19
*** openstack changes topic to "Reviews, Bugs and Releases (Meeting topic: glance)"14:19
*** yamamoto has joined #openstack-meeting-414:19
*** yamamoto has quit IRC14:19
*** yamamoto has joined #openstack-meeting-414:19
nikhil_khttps://review.openstack.org/#/c/195820/14:19
nikhil_knot sure if this was raised by flaper87 or wko ?14:19
mclarenNot sure. It has three +2s14:21
mclarenIs there anything in particular blocking it at this point does anyone know?14:22
nikhil_kmclaren: I read you got a chance to test this personally14:22
mclarenNope.14:22
nikhil_kah14:22
mclarenI can do though if that helps14:22
nikhil_kguess I either need to trust eric or force myself to find time for it14:22
nikhil_kwhoever wants a backport can propose one but likely to not get approved, that's usually true for db migrations14:23
nikhil_kmclaren: that would really help!14:23
mclarenOk, np14:23
* mclaren wonders if bunting might do it14:24
sigmavirus24wokuma probably added that to the agenda14:24
nikhil_kcool14:24
nikhil_kgreat to have awareness about an important patch14:24
nikhil_knext one is image-member reuse14:25
nikhil_khttps://review.openstack.org/#/c/207042/14:25
nikhil_khttps://review.openstack.org/#/c/190895/14:25
buntingI would be up for testing it14:25
nikhil_kseems like we don't have any concerns raised on that even after an APIImpact14:25
mclarenbunting: cheers :-)14:26
nikhil_kI would just amend the spec to include it and merge it14:26
nikhil_kbunting: awesome, ty!14:26
shalqcan core members help review the code in 190895 ?14:27
sigmavirus24nikhil_k: I don't think there's been a lot of review for that spec14:27
sigmavirus24so I wouldn't say that there haven't been any concerns raise14:27
*** jwagner_away is now known as jwagner14:27
*** vishwanathj has joined #openstack-meeting-414:27
sigmavirus24*raised14:27
nikhil_ksigmavirus24: we did a impromptu during one of the drivers' meeting14:27
sigmavirus24Ah14:27
nikhil_kand people then were okay, we were just giving some time for any last minute red flags. there were none!14:28
nikhil_kI can put that up on my review list as I have reviewed it already a couple times and know the change14:29
nikhil_kI like what abhishek is suggesting there14:29
nikhil_kshalq: so, that minor change should cover it for your patch14:29
shalqok14:29
nikhil_knext one is from bpoulos14:30
nikhil_khttps://review.openstack.org/#/c/183137/14:30
bpoulosI would appreciate feedback on the code, especially on two aspects:14:30
bpoulos1. Does the location where the signature verification occurs make sense (ie, right after the checksum is computed)?14:30
bpoulos2. Does the handling of a failed signature verification make sense (ie, set status to killed and delete the image)?14:30
bpoulos(I realize I have a few cleanup comments, and I will address them today)14:30
*** banix has joined #openstack-meeting-414:30
nikhil_kbunting: about the delete, the general practice is to not set to deleted and leave it to the user14:31
nikhil_khaving it in the killed (mostly used for error state) would make more sense14:31
bpoulosso just change the status to killed?14:32
rosmaitai have a question about #2 ... i thought the glance-side verification was a user convenience, maybe if i upload an image and specify an incorrect signature, i'd prefer to just update the sig, rather than do the entire upload?14:32
*** FallenPegasus has joined #openstack-meeting-414:33
*** fawadkhaliq has quit IRC14:33
bpoulosjust update the signature, and repeat the verification without doing another upload?14:33
rosmaitabpoulos: possibly, though i don't see how you could trigger that14:33
bpoulosyeah, that seems pretty round-about14:33
rosmaitaunless you add a 'validate image' task14:33
nikhil_k:)14:34
bpoulosin which case, we wouldn't want to set the status to killed when verification failed?14:34
rosmaitanot sure ... the verification status doesn't really affect the image14:35
rosmaitamaybe among the metadata you're adding, you add 'glance_verified: true14:35
rosmaita or something like that14:35
bpoulosas a property?14:36
rosmaitayeah14:36
nikhil_kthat's suseptible to breakage though14:36
rosmaitathough it would be kind of meaningless except to the original uploader14:36
bpoulosalright, so the user could easily decide whether or not to trigger verification?14:36
bpoulosi think if the user doesn't want to trigger verification, they can easily provide the properties after the upload completes14:36
nikhil_kwe need define global prot properties for arbitrary meta for image-signing verification14:36
bpoulosnikhil_k: where does that definition go?14:37
rosmaitahmmm .... maybe for first implementation, we should just delete the image and decide what makes sense for M14:37
*** shalq has quit IRC14:37
nikhil_kbpoulos: and how do we prot the +w mode on that prop after correct validation?14:37
nikhil_kyeah14:37
nikhil_kwait, why delete14:38
bpoulosdelete, or just set to killed?14:38
nikhil_kit would disappear under the user's node without notice14:38
nikhil_knose*14:38
rosmaitaso, killed and let the user delete (or re-upload if that bp is impelmented)14:38
nikhil_kyeah14:39
rosmaitai think we also need to be clear about the status of the metadata on the image14:39
nikhil_knot sure what's the best way to convey to the user _why_ the upload failed14:39
rosmaitathe consumer has to use it to verify everything for themselves14:39
nikhil_kright14:39
nikhil_kmutating the meta on first write might be a good option14:39
nikhil_kbut we don't have that granularity14:40
bpoulosdo we need to protect the properties?14:40
*** zeih has quit IRC14:40
nikhil_kbpoulos: if you want to use them for verification14:40
nikhil_kyes14:40
*** geoffarnold has joined #openstack-meeting-414:40
*** chenshuai1 is now known as chenshuai14:40
bpoulosprotect as in prevent changing or protect as in define exactly what they are?14:40
rosmaitanikhil_k: what would be the implications of allowing a change?14:41
*** vikram has joined #openstack-meeting-414:41
rosmaitai'm thinking if it's image-consumer-beware, maybe it doesn't matter?14:41
nikhil_krosmaita: hmm, I think for a shared image. it could be rendered useless by someone who did not intend to mutate the prop14:42
bpoulosI think one attack scenario we're considering is that an attacker could delete or modify them -- even if we prevent normal routes of doing so -- but the fact that we have an external CA that limits the valid certificates helps us14:42
bpoulosyeah, it could be removed unintentioanlly14:42
nikhil_krosmaita: just loopholes for confusion on the usage, that's all14:42
bpoulosand if the client requires the properties, then the client won't be able to boot it14:42
rosmaitanikhil_k: agreed14:43
bpoulosso the user has to provide them before the upload, or not at all?14:43
bpoulosie, they can't add them after the fact?14:43
bpoulos(so that glance doesn't verify, but a client still could)14:43
*** nhairston has joined #openstack-meeting-414:43
rosmaitait's sounding to me more and more like a task is better suited for this14:43
*** zeih has joined #openstack-meeting-414:43
nikhil_kbpoulos: we have somethign already like those and they are called base properties :)14:43
bpouloswould we want to make these base properties though?14:43
nikhil_krosmaita: or a migration that adds another base prop14:44
nikhil_kbpoulos: the issue is the arbitrary size, right14:44
nikhil_kso, (I take the comment back) probably no14:44
bpoulosideally, we'd like to not even be limited to 25514:44
nikhil_kyep14:44
rosmaitayeah, so cant' predict in advance14:44
bpoulos1024 or 2048 would be even better for signature sizes14:44
jokke_++14:45
nikhil_kI think we need to give some time to other reviews posted14:46
bpoulosok :) thanks for discussing image signing for a bit14:46
nikhil_khow about we chat on this topic, if needed, after the meeting on -glance14:47
mclarendo we have similar behaviour with checksums? where a user can supply the checksum in advance?14:47
bpoulossure, we can continue on -glance14:47
nikhil_kit's a base prop though14:47
*** chenshuai has quit IRC14:47
mclarenok, how bad would adding a new base prop be?14:47
nikhil_kI think she wants many such14:48
nikhil_kand size of those can be relatively large14:48
*** zeih has quit IRC14:48
mclarenah, ok14:48
*** vikram has quit IRC14:48
bpoulosi have four that i'd like to add14:48
*** GB21 has joined #openstack-meeting-414:49
bpoulosbut we can move on to other reviews14:49
nikhil_kcool14:49
nikhil_kmclaren: next one is yours?14:49
nikhil_khttps://review.openstack.org/#/c/211086/14:49
mclarenoh, not a big deal just a client patch14:49
nikhil_kwe've had this behavior for along time!14:50
nikhil_kbut I guess it makes sense to not enforce it during listing14:50
mfedosinI agree to +2 it14:51
rosmaitaor at all ... what's the rationale behind confirming that the info supplied by glance meets the schema?14:51
mclarenrosmaita: interesting question. Arguably it's more useful when you're putting stuff in rather than reading it back14:52
jokke_rosmaita: point ... who we trust if not our own server ;)14:52
rosmaitai mean, unless there's a bug in glance, glance knows what the schema is, and supplies data accordingly14:52
rosmaitamclaren: +1 for upload, client should validate, but for download seems pointless14:53
rosmaitai mean, what are you going to do? take your business elsewhere?14:53
nikhil_krosmaita: this was introduced when strict enforcement on GET was a thing14:53
mclarenwell let's agree on list first :-)14:53
rosmaitagood point14:53
*** lakshmiS has joined #openstack-meeting-414:54
rosmaitafrom the patch, you can see that we already agreed not to validate all the returned images in a list14:54
rosmaitaso let's just take that to an extreme and not validate any14:55
jokke_rosmaita: yeah that validation was killing the v2 performance14:55
rosmaitaor we could just validate a random one, and drive users crazy14:55
mfedosinI think we can add --validate flag to image-list maybe to validate them all14:55
jokke_rosmaita: and leave that bug still open, what this change would fix?14:56
mfedosinif it's necessary14:56
nikhil_kI can think of a reason for validating this during listing but it's not strong enough to break the response. Glance client does on the behalf of the user if the images registered match with the prop articulation as defined by operator needs14:56
mclarenmfedosin: an operator may be interested in that I guess14:56
rosmaitamfedosin: that's a good compromise14:56
nikhil_kyep14:56
jokke_mfedosin: wanna propose spec for that? :P14:56
nikhil_kbut it can be confusing flag14:57
jokke_I don't think it should be blocking this going in14:57
mfedosinno, it's enough specs for me :)14:57
nikhil_kas it overlaps with bpoulos terminology for validation14:57
rosmaitai think as long as v1 is around, the glanceclient has to be liberal in what it accepts14:57
mfedosinbut I can ask Darja to implement it14:57
nikhil_kok, we have a couple mins for that late addition14:57
*** pbourke has quit IRC14:57
nikhil_kmfedosin: yours?14:57
nikhil_khttps://review.openstack.org/#/c/200554/14:57
mfedosinyep it's mine14:58
*** pbourke has joined #openstack-meeting-414:58
mfedosinThere is a Flavio's concern about adding new config parameter in Glance.14:58
mfedosinBut for example cinder has it.14:58
mfedosinhttps://github.com/openstack/cinder/blob/master/cinder/volume/drivers/rbd.py#L8214:58
mfedosinSo I want to hear your opinion - should I abandon it or it's okay?14:58
mfedosinSince we have plans to create oslo.rbd project, all these config params will be there and Glance will use them anyway.14:59
jokke_I do agree with flaper87's point that it does not make sense to dublicate that. and which one would take preference if you have different values?14:59
nikhil_kmfedosin: that sounds better14:59
nikhil_kWe are out of time.15:00
nikhil_kThanks all!15:00
mclarenthanks!15:00
jokke_thnx15:00
mfedosinokay, thanks :)15:00
nikhil_k#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Thu Aug 20 15:00:20 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-08-20-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-08-20-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-08-20-14.00.log.html15:00
*** ativelkov has left #openstack-meeting-415:00
nikhil_kTravT: hi15:00
TravThi nikhil_k15:00
TravT#startmeeting openstack search15:00
openstackMeeting started Thu Aug 20 15:00:48 2015 UTC and is due to finish in 60 minutes.  The chair is TravT. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** bunting has left #openstack-meeting-415:00
*** openstack changes topic to " (Meeting topic: openstack search)"15:00
openstackThe meeting name has been set to 'openstack_search'15:00
rosmaitao/15:01
nikhil_ko/15:01
TravTLet's give a couple mins.15:01
lakshmiSo/15:01
david-lyleo/15:01
sigmavirus24o/15:01
*** nhairston has quit IRC15:01
TravTI don't think sjmc7 will be here at least at the start.  There is an HP meeting in seattle that he had to go to.15:02
*** sjmc7 has joined #openstack-meeting-415:02
sjmc7morning15:02
TravTand there he is15:02
TravT:)15:02
*** vikram_choudhary has joined #openstack-meeting-415:02
sjmc7sorry, bit under the weather15:02
TravThttps://etherpad.openstack.org/p/search-team-meeting-agenda15:02
TravTAdd anything you want as usual15:02
TravT#topic Testing15:03
*** openstack changes topic to "Testing (Meeting topic: openstack search)"15:03
TravTAs mentioned last week, we put up a review for python 3 in the gate.15:03
*** chenshuai has joined #openstack-meeting-415:03
TravTIt went through.15:03
TravTthat's all.15:03
sjmc7:)15:03
TravTFunctional tests.15:04
TravTlakshmiS how are they coming?15:04
TravTyou were going to put up an initial patch?15:04
*** mclaren has quit IRC15:04
lakshmiSready to go. will put up the patch before the weekend.15:04
TravTGreat!15:05
TravTany discussion needed on them with the group here?15:05
lakshmiSnothing specific i can think about15:05
TravTok, well, i'm looking forward to seeing them.15:05
lakshmiSeven though i tried to cover the RBAC filters that rosmaita initially gave15:05
*** fawadkhaliq has joined #openstack-meeting-415:06
sjmc7there were some in that patch i had in glance a while back15:06
sjmc7if that's useful15:06
lakshmiSsjmc7: yeah i ported them15:06
sjmc7great, thanks15:07
TravT#topic reviews process15:07
*** openstack changes topic to "reviews process (Meeting topic: openstack search)"15:07
*** SimonChung1 has quit IRC15:07
*** blahRus has joined #openstack-meeting-415:08
TravTso, we're only a couple weeks out in liberty15:08
TravTi'm still hopeful we can have a release.15:08
TravTbut i also know that having time to do reviews is difficult for a number of people right now.15:08
TravTi've been trying to catch up on them.15:09
TravTand they are time consuming to fully test.15:09
TravTbut wanted to open up some discussion on ideas for how to facilitate getting reviews down in timely manner.15:10
TravTand also what is / isn't okay process-wise15:10
TravTIn the early phases of this project.15:11
sjmc7i know one thing we've tried to stick to is to have +2s from multiple companies, even though there are a majority of HP folks on the core list15:11
sjmc7if people are ok with approving changes with 2 +2s even if it's just HP folks just as the summit deadline approaches that might help, especially for bug fixes15:12
david-lyleI think for now that may be a good relaxation of the review guidelines15:12
rosmaitai agree15:12
rosmaitai keep hosing my devstack, which is slowing my reviews, so i am part of the problem here15:13
david-lylewe're still working on critical mass15:13
nikhil_ksame with me15:13
nikhil_kI agree too, but would be good if someone can test them functionally. I know TravT is very particular about it and best to keep that practice15:13
sjmc7yeah, i've been testing them15:13
sjmc7it is time consuming btu esp given our tests it's necessary15:13
TravTyeah, i seem to be spending a large portion of my days just playing QA recently.15:14
nikhil_k:)15:14
*** nkrinner has quit IRC15:14
lakshmiSwe need downstream applications using searchlight to do that for us:)15:15
TravTlol15:15
sjmc7we've got people itching to use it :)15:15
TravTI'd still like to ensure that everybody has an opportunity to weigh in at least conceptually.15:15
lakshmiSa +1 would be good to have15:15
TravTyes, just to indicate the idea seems right.15:16
sjmc7yeah - for features or bp implementations i'd definitely like additional input15:16
sjmc7but for pure bugfixes it seems less important15:17
TravTyes, and we have several high and critical's sitting out there right now with code proposed.15:17
TravTI also will consider the functional tests to be critical.15:17
TravTbecause i don't want to see any regressions.15:18
TravTany other input on this specifically?15:19
TravTlakshmiS, last week you had mentioned the idea of having an hour or so available each week for people to interact on specific reviews through end of liberty15:20
nikhil_kthat would be nice!15:21
lakshmiSyes lets schedule it15:21
*** dannywilson has joined #openstack-meeting-415:21
TravThow about Tuesday or Wednesdays at this same time?15:21
TravTin the searchlight room15:22
nikhil_ki don'tmind sparing a couple hours tomorrow just on reviews if someone is available15:22
TravTnikhil_k, there is a question on the nova patch I have for you when we get to it later in this meeting.15:23
rosmaitatuesday would be better for me15:23
nikhil_kwed looks better for me, otherwise15:23
lakshmiSboth are good with me15:23
nikhil_ki am travelling for work mon, tue most likely15:24
*** FallenPegasus has quit IRC15:24
TravTi can do either.15:24
TravTis wednesday out for you rosmaita15:24
TravT?15:24
sjmc7either's ok with me, wednesday maybe a bit easier15:25
david-lyleI' fine with either15:26
TravTdavid-lyle: i'm still trying to figure out if i can psych myself up for your added early morning horizon meeting on wednesday. :(15:26
sjmc7:)15:26
nikhil_kactaully, I may be online at 1500utc on tuesday but not 100% sure15:27
TravTIf possible, let's shoot for Tuesday15:27
TravTI'll check in on Monday with everybody15:27
david-lylejust not 2000 or 2100 UTC on Tues those are taken with TC and X-Project15:28
TravTthat is way too late for lakshmiS anyway15:29
TravThttp://everytimezone.com/#2015-8-20,180,cn315:29
david-lyleok, just making sure15:29
TravTthat's the time slot shooting for on Tuesday.15:29
TravTif you can't make it nikhil_k, we'll bump to wednesday15:29
TravTok, on to but reviews15:29
nikhil_kthanks TravT15:29
TravT#topic bugs15:30
*** openstack changes topic to "bugs (Meeting topic: openstack search)"15:30
lakshmiSit says 8:30 PM local time for me which is same as now15:30
TravTso, this one:15:30
TravT    Fix for Authentication not happening https://review.openstack.org/21104715:30
rosmaitaTravT: i cann do wed, but have team mtg at 15:3015:30
TravTI kind of like tuesday better than wednesday15:31
TravTjust so we have a day between that and this meeting15:31
TravTso, this one: Fix for Authentication not happening https://review.openstack.org/21104715:31
*** Swami has joined #openstack-meeting-415:31
TravTeven with allowing 2 +2s from same company, it needs another.15:32
TravTit is a critical bug15:32
TravTso, nikhil_k, david-lyle, sigmavirus24, rosmaita, if one of you could take a look15:32
*** sankarshan is now known as sankarshan_away15:32
nikhil_kack15:33
TravTnote that i co-authored, so I can't +2 it.  my +1 was only to indicate it was ready for reviews.15:33
*** woodard has joined #openstack-meeting-415:33
david-lylelooking, can try out the patch after this15:33
sjmc7thatnks david15:34
rosmaitai am looking at that, but hosed my devstack15:34
TravTthanks david-lyle15:34
sjmc7i did test it, generated configs and docs looked good to me15:34
TravTthere are a couple more critical highs.15:35
TravT    Fix RBAC filters https://review.openstack.org/21256315:35
TravTI tested that one yesterday with images and the nova servers patch.15:35
sjmc7yeah, this was a good one15:35
TravTtried about 8 different queries on it.15:35
TravTi put those in a paste in my review comments.15:35
TravTlaskhmiS, would be good to consider that with any of the RBAC functional tests you are doing15:36
TravTso maybe you could take a look lakshmiS?15:36
sjmc7we should provide guidance on writing these in the docs, or abstract some of it to the base class at some point. it's easy to screw up15:36
lakshmiSok i will check if its covered15:36
*** chenshuai has quit IRC15:37
TravTYour sorting patch, sjmc7     Sorting https://review.openstack.org/#/c/206268/15:37
TravTI will look at this one15:37
sjmc7yeah.. just needs reviews15:37
sjmc7it should be pretty straightforward15:37
sjmc7passthrough of the e-s DSL for sorting15:37
TravTok.15:38
TravTOn to BPs15:38
sjmc7you actually could do it already by passing it inside the 'query' parameter15:38
sjmc7but this makes it more explicit15:38
*** VW_ has joined #openstack-meeting-415:39
TravT#topic nova plugin15:39
*** openstack changes topic to "nova plugin (Meeting topic: openstack search)"15:39
TravT    Nova instances plugin https://review.openstack.org/19885215:39
TravTi've been harassing sjmc7 on this one quite a bit15:39
TravTand it is very close15:40
sjmc7i do feel quite harassed15:40
TravTquestion for rosmaita and nikhil_k15:40
TravTcurrently the following fields are filtered if you aren't admin15:40
*** pennerc has joined #openstack-meeting-415:40
TravTOS-EXT-SRV-ATTR:host15:40
TravTOS-EXT-SRV-ATTR:hypervisor_hostname15:41
*** geoffarnold has quit IRC15:41
TravTare there others we should add?15:41
sjmc7there's a hostId too15:41
sigmavirus24Sorry, in the middle of a sad sad video call15:41
sjmc7which it occurs should probably be protected15:41
TravTsigmavirus24: need some kleenexes?15:41
sjmc7:)  sigmavirus24. the best kind!15:41
sigmavirus24no15:42
sigmavirus24send the strongest of alcohol15:42
TravTlol15:42
TravTrosmaita: nikhil_k: if you could add a comment on that patch in this file about fields to filter for admin15:43
TravThttps://review.openstack.org/#/c/198852/14/searchlight/elasticsearch/plugins/nova/servers.py15:43
nikhil_kTravT: don't quite have them ready but can check15:43
TravTsure. line 30.15:44
*** armax has joined #openstack-meeting-415:44
TravTother than a few other nits on that patch and some ideas for future things, that patch worked quite nicely for me15:45
TravTso, maybe we can get nova support in by end of this week.15:45
nikhil_kTravT: so, I am not sure about the extensions and their indexing15:45
nikhil_kam aware that they were being proposed to be purged or moved to regular api but not sure if we can ever come up with a list of all the ext attrs that are admin only15:46
nikhil_kthey depend on which ext are enabled by the deployer and we will be playing cat and mouse15:46
nikhil_kso, sorry some context:15:46
*** GB21 has quit IRC15:46
TravTnikhil_k: in some of my comments on that patch, i suggested that we add a plugin config for whitelisting / blacklisting fields.15:46
nikhil_kOS-EXT-* are OS Extensions added to nova api15:47
sjmc7until we do that we could have a whitelist of extension fields in the code15:47
sjmc7so we don't accidentally scrape up any we shouldn't15:47
nikhil_kthat sounds good15:47
TravThere's a comment I put on the patch:15:48
TravTIt really also occurs to me that when we do that the nova plugin should support having separate extension files for all these extension fields. The extensions enabled would all be invoked during serialize function and also would be called to add to the mapping. This way deployers could add their extension without modifying source just like they do for nova. BP needed.15:48
sjmc7yeah. maybe not a liberty timescale thing at this point15:48
*** vikram_choudhary has quit IRC15:49
*** odyssey4me has joined #openstack-meeting-415:49
*** belmoreira has joined #openstack-meeting-415:49
nikhil_kah cool15:49
TravTnikhil_k, you mentioned having review time tomorrow.15:50
nikhil_kyes15:50
TravTmaybe you could do another pass on the nova patch.15:50
nikhil_ksure15:50
nikhil_kon my list now15:50
TravThopefully sjmc7 will be able to address my current comments before tomorrow and i'll do another pass15:50
TravTok.15:51
sjmc7yeah, will do15:51
nikhil_kdarn, evernote app broke on my m/c15:51
TravTok, did want to mention that following our BP review last week I opened the client blueprint we discussed.15:51
TravThttps://blueprints.launchpad.net/searchlight/+spec/initial-openstack-client-search-plugin15:51
TravTjust FYI15:51
*** salv-orlando has quit IRC15:52
TravT#topic open discussion15:52
*** openstack changes topic to "open discussion (Meeting topic: openstack search)"15:52
*** chenshuai has joined #openstack-meeting-415:52
sjmc7i've actually got to run, meeting i have to attend in the office15:52
*** vikram_ has joined #openstack-meeting-415:52
TravTok.15:52
sjmc7anything anyone needs, i'll be in the SL channel in a biit15:53
TravTi think everybody is quite busy these days.15:53
david-lylehttp://lists.openstack.org/pipermail/openstack-dev/2015-August/072082.html15:53
david-lyleis a thread about keystone and pagination15:53
david-lylebut the current stance by keystone on the v3 API makes it impossible to index15:53
sjmc7i saw that one :)15:53
sjmc7good reading!15:53
*** hogepodge has quit IRC15:53
TravToh interesting.15:54
david-lyleso, that's awesome15:54
TravTi didn't see it15:54
*** TheIntern has joined #openstack-meeting-415:54
david-lylethis is not new, but progress is feeling unlikely15:54
TravTthat is awesome. :(15:54
lakshmiSpromising15:54
*** pennerc has quit IRC15:55
david-lylethe other option is build based on other indexed data15:55
*** armax has quit IRC15:56
*** pennerc has joined #openstack-meeting-415:56
TravTdavid-lyle?15:56
TravTtrying to figure out what you mean.15:56
david-lyleme too :P15:56
TravTok, well, i'll read through that thread15:57
david-lyleno, you could go do a secondary request based on results from nova, etc15:57
david-lylenova data will have project ids, you could request data on project ids returned with the data15:57
david-lylebut that's an incomplete index15:58
david-lyleso maybe worse :(15:58
TravTwe could just run a scheduled job and periodically get all projects from keystone.15:58
*** belmoreira has quit IRC15:58
david-lylewell no, you can't actually15:58
TravTyay15:59
*** lazy_prince has quit IRC15:59
david-lyleyou'll get the first 500 or 1000 and an error saying there are more15:59
*** aruncewind has joined #openstack-meeting-415:59
david-lylebut no way to index into them15:59
*** salv-orlando has joined #openstack-meeting-415:59
lakshmiSwill have to go to their db then:)15:59
david-lyleunless you dynamically build up a filtering scheme until you get below the MAX return # threshold15:59
*** b3rnard0 has joined #openstack-meeting-416:00
*** evrardjp has joined #openstack-meeting-416:00
TravTokay, we are out of time, but this was good to bring up16:00
nikhil_kThanks!16:00
TravTwe can continue16:00
TravTon it in the future.16:00
TravT#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu Aug 20 16:00:44 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-08-20-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-08-20-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-08-20-15.00.log.html16:00
odyssey4me#startmeeting OpenStack Ansible Meeting16:00
openstackMeeting started Thu Aug 20 16:00:58 2015 UTC and is due to finish in 60 minutes.  The chair is odyssey4me. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: OpenStack Ansible Meeting)"16:01
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:01
TheInterno/16:01
*** bpoulos has left #openstack-meeting-416:01
odyssey4me#topic Agenda & rollcall16:01
*** openstack changes topic to "Agenda & rollcall (Meeting topic: OpenStack Ansible Meeting)"16:01
hughsaundershey16:01
d34dh0r53o/16:01
serverascodeo/16:01
TheInterno/16:01
*** TravT has left #openstack-meeting-416:01
evrardjpo/16:01
dstaneko/16:02
andymccrhi16:02
*** VW_ has quit IRC16:02
*** harshs has quit IRC16:03
*** lakshmiS has left #openstack-meeting-416:03
*** VW_ has joined #openstack-meeting-416:03
*** singleth_ has joined #openstack-meeting-416:04
sigmavirus24o/16:04
b3rnard0hello16:04
odyssey4meHowdy all - nice to see that we have a fair set of attendeed.16:05
odyssey4me*attendees16:05
odyssey4me#topic Review action items from last week16:05
*** openstack changes topic to "Review action items from last week (Meeting topic: OpenStack Ansible Meeting)"16:05
odyssey4meACTION: sigmavirus24 and cloudnull to put together a POC for pip and epoch's16:05
* sigmavirus24 sighs16:05
sigmavirus24maybe after all this ugprade nonsense is done16:06
odyssey4mehehe, now that cloudnull is back, perhaps that can go ahead - we carry again?16:06
sigmavirus24please16:06
odyssey4me#action sigmavirus24 and cloudnull to put together a POC for pip and epoch's16:06
sigmavirus24cloudnull isn't exactly back 100%16:06
*** pennerc has quit IRC16:06
odyssey4meACTION: odyssey4me to add upstream liberty milestones to the trunk series16:06
*** VW_ has quit IRC16:06
*** sdake has joined #openstack-meeting-416:06
odyssey4methis has been done - it's perhaps useful to target trunk bugs against liberty-3 and liberty-release16:07
*** VW_ has joined #openstack-meeting-416:07
odyssey4meI just ask that any liberty-related bugs also be added as a related bug to the liberty blueprint please16:07
odyssey4me#link https://blueprints.launchpad.net/openstack-ansible/+spec/liberty16:07
odyssey4meACTION: all to review blueprints, self-assign and target, then submit and review blueprints16:07
*** singlethink has quit IRC16:07
odyssey4mehopefully some of that has been done, we'll go into that in a bit16:08
*** singlethink has joined #openstack-meeting-416:08
odyssey4mebefore we dive into blueprints, I'd like to shuffle the agenda a little to get the rest out the way16:08
odyssey4meare we happy with that?16:08
*** yamahata has joined #openstack-meeting-416:09
evrardjpok16:09
odyssey4me#topic Broken Gate16:09
*** openstack changes topic to "Broken Gate (Meeting topic: OpenStack Ansible Meeting)"16:09
odyssey4meI think most people in the meeting are aware that gating for master has been broken for almost 3 weeks now16:10
odyssey4methe issue has been tempest failing when testing nova/cinder16:10
odyssey4meit only happens in hpcloud16:10
odyssey4metoday we hope that we've found the solution in https://review.openstack.org/21509316:10
odyssey4menote that juno/kilo gating has been fine all this time16:11
*** singleth_ has quit IRC16:11
*** GB21 has joined #openstack-meeting-416:11
*** VW_ has quit IRC16:11
odyssey4meif the above review doesn't work, then https://review.openstack.org/215028 is a workaround to get dev moving again and allow more time to figure out the issue16:11
odyssey4meany comments/questions about that?16:11
palendaeNone from me16:13
evrardjpnone16:13
odyssey4mealright16:13
odyssey4me#topic Stackforge -> Openstack16:13
*** openstack changes topic to "Stackforge -> Openstack (Meeting topic: OpenStack Ansible Meeting)"16:13
evrardjpif this isn't the solution, I'll try to have a closer look on friday with you. we need to have it working16:13
odyssey4methanks evrardjp :)16:13
odyssey4meAnother update16:13
odyssey4meWe are on the list for upcoming project renames, which will rename the project from os-ansible-deployment to openstack-ansible, and move the repo to the openstack namespace: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Project_Renames16:14
odyssey4me#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Project_Renames16:14
evrardjpI read it wasn't that easy, what's the impact for us?16:14
odyssey4mea process for handling renames has been sent out on the mailing list - please read and provide feedback16:15
odyssey4me#link http://lists.openstack.org/pipermail/openstack-dev/2015-August/071816.html16:15
evrardjpok thanks16:15
odyssey4me#link http://lists.openstack.org/pipermail/openstack-dev/2015-August/072140.html16:15
hughsaundersgit remote set-url many times16:15
odyssey4meevrardjp so the repo name will change, and the organisation name will change16:15
odyssey4mewhat hughsaunders said16:15
odyssey4meand probably many docs changes for us too16:16
evrardjpthat's what I understand, and the remotes, that's what seems logical to me at first, but will it impact other processes/gating/documentation?16:16
evrardjpok16:16
odyssey4meyeah, the gate stuff will be handled in the rename - but we'll have some in-repo changes which will need to be sorted out too16:17
odyssey4mewe'll deal with that when it happens - it's a pretty easy search and replace for most of it16:17
odyssey4meany more thoughts/comments/questions?16:18
*** krtaylor has quit IRC16:18
evrardjpnone16:18
odyssey4me#topic Upcoming Milestones16:18
*** openstack changes topic to "Upcoming Milestones (Meeting topic: OpenStack Ansible Meeting)"16:18
hughsaundersodyssey4me: Birthdays?16:19
evrardjp\o/16:19
odyssey4melol, my birthday was last week hughsaunders :p16:19
*** SimonChung has joined #openstack-meeting-416:19
odyssey4mewho else is having one?16:19
evrardjphappy birthday then, sorry for being late on this one!16:19
andymccrodyssey4me: everybody is having one at some point.16:19
TheInternHappy Birthday!16:20
hughsaundersdeep andymccr16:20
odyssey4meandymccr ever the pragmatist16:20
evrardjpsarcastic I'd say16:20
*** cloudnull has joined #openstack-meeting-416:20
andymccradding that dose of realism that was required16:20
cloudnullo/16:21
odyssey4meso https://launchpad.net/openstack-ansible/+milestone/11.2.0 is set for 11 Sep, but we needed to release 11.1.2 early due to some changes upstream and some stuff I broke in the requirements16:21
* cloudnull late was in a meeting.16:21
odyssey4meIt appears that the ceph work is largely done and that the work is ready for backporting16:21
*** xingchao has quit IRC16:21
odyssey4meI suggest that we bring forward the 11.2.0 date to Friday next week (28 Aug), then continue from there16:22
odyssey4meany objections to that?16:22
evrardjpFYI, I'm using it in kilo right now, not tested the cinder-backup, but everything looks fine16:22
evrardjpeasy backporting then16:22
evrardjpno objection16:22
odyssey4meyup, there are some extra tweaks in flight which we can merge and backport easily once master is unblocked16:22
odyssey4mewelcome cloudnull :)16:23
*** hogepodge has joined #openstack-meeting-416:23
hughsaunders+1 on bringing 11.2.0 forward16:23
odyssey4mehughsaunders andymccr are you guys happy to bring the 11.2.0 milestone forward?16:23
odyssey4me:p16:23
*** stevelle has joined #openstack-meeting-416:23
andymccrsure16:25
odyssey4me#action odyssey4me to move 11.2.0 milestone to 28 Aug16:25
odyssey4me#topic Blueprints16:25
*** openstack changes topic to "Blueprints (Meeting topic: OpenStack Ansible Meeting)"16:25
odyssey4me#link https://blueprints.launchpad.net/openstack-ansible16:25
odyssey4mewe have a few blueprints of note16:26
*** chenshuai has quit IRC16:26
odyssey4meliberty is coming up16:26
odyssey4me#link https://blueprints.launchpad.net/openstack-ansible/+spec/liberty16:26
odyssey4memaster's development from the end of august will start  to diverge from kilo somewhat as we focus a little more on liberty changes16:26
odyssey4meplease see the dependency tree at the bottom of the page16:27
odyssey4mepalendae & cloudnull there are blueprints that liberty's release depend on there16:27
*** geoffarnold has joined #openstack-meeting-416:27
*** vivek-ebay has joined #openstack-meeting-416:27
odyssey4methese aren't hard deps, except perhaps for the upgrade path - but I'd like to confirm that we think we can get these done in time?16:27
palendaeWhen's the liberty release date?16:28
odyssey4mecloudnull I know that you had much of the work for yours done already16:28
odyssey4meliberty-release is on 19 Sep: https://launchpad.net/openstack-ansible/+milestone/liberty-release16:28
palendaeI would say yes, unless people have problems with the upgrade path proposed16:28
palendaeThen we need to actually write kilo->liberty upgrades16:28
*** akwasnie has quit IRC16:29
odyssey4me#link https://review.openstack.org/20771316:29
odyssey4methat's the spec for the upgrade path - it's gone through some reviews already16:29
odyssey4mewe need more attention on that now as it's going to hit crunch time soon16:29
palendaeI'll likely need some help, given the timeline; but I have an idea for a starting point if people aren't opposed to me starting a parallel code path16:29
palendaeparallel code patch*16:30
*** sdake_ has joined #openstack-meeting-416:30
odyssey4mepalendae I think it's fairly safe to say that master is available to start ripping the upgrade stuff apart and doing the thing16:30
*** salv-orlando has quit IRC16:30
*** evrardjp has left #openstack-meeting-416:30
odyssey4meI'd suggest trying to break it into parts so that the patches are easier to test and review.16:30
palendaeodyssey4me: Cool, then I will try to start on that tonight or tomorrow, at least to get a commit on for people to lob comments at16:30
palendaeRight16:30
odyssey4mesigmavirus24 cloudnull hughsaunders andymccr please review https://review.openstack.org/207713 asap16:31
odyssey4mewe need to finalise and approve that before we get any patches merged16:31
hughsaundersneeds manual rebase16:32
odyssey4me#action cores to review the liberty upgrade spec https://review.openstack.org/20771316:32
sigmavirus24^^16:32
*** jckasper has quit IRC16:32
palendaeMy first patch is basically, for master, going to be ripping out everything and leaving a blank slate so we can start filling stuff in that's relevant16:32
*** matrohon has quit IRC16:32
palendaeMaybe an error message if Juno config files are found letting the deployer know they should go to kilo16:32
odyssey4mehughsaunders I think we need to revise gating in time for liberty too - will you be able to put https://blueprints.launchpad.net/openstack-ansible/+spec/split-aio-gates together before the next meeting?16:32
palendaeThat's where I'll start, and probably need to get started on the upgrade gate script very soon, too16:33
*** jckasper has joined #openstack-meeting-416:33
*** vikram_ has quit IRC16:33
odyssey4mehughsaunders I'm happy to work with you on it, but our gating issues are starting to cause major disruption and the tests are not trusted, resulting in delays for reviews16:33
*** sdake has quit IRC16:33
hughsaundersodyssey4me: cool, lets collaborate, I thought I saw you working on some sort of gating matrix.16:34
*** ivar-lazzaro has joined #openstack-meeting-416:34
palendaeFor upgrade testing: are people ok with just verifying the upgrade runs then running tempest after the upgrade?16:34
palendaeAs in install (current-1), upgrade to current, run current's tempest16:34
palendaeShould probably put that in the spec16:34
*** sdake_ is now known as sdake16:34
hughsaundersdeploy, tempest, upgrade, tempest16:35
stevelleI think that is a great place to target for liberty, palendae16:35
*** numan has quit IRC16:35
odyssey4mepalendae I think tempest both times would be better - and I think that the upgrade tests should perhaps be periodic, rather than per commit - the upgrade test will be very long16:35
hughsaundersotherwise you don't know whether hte initial deploy or the upgrade failed16:35
palendaehughsaunders: Why a tempest in the middle, out of curiosity? I'm leaving out because of (current -1) because (hopefully) its gate is doing that16:35
palendaeodyssey4me: Yes, that needs to be periodic16:35
palendaeI need to get it written before I ask infra about it, but yep16:36
*** numan has joined #openstack-meeting-416:36
odyssey4mepalendae we'll be doing work with infra and can help with that - figure out the bits in our repo and once you have a process that works then we can put a gate test in that uses it16:36
palendaeYep16:36
hughsaunderspalendae: tempest is a reasonably short amount of time out of a deploy-upgrade run, and running it after the initial deploy makes determining the source of a problem easier16:36
palendaehughsaunders: Fair enough16:37
*** fawadk has joined #openstack-meeting-416:37
odyssey4meagreed with hughsaunders - if we don't know that the starting env was ok, then any fails in the upgrade are not determinable16:37
*** fawadkhaliq has quit IRC16:37
*** geoffarnold has quit IRC16:37
*** puranamr has joined #openstack-meeting-416:38
palendaeOk, that's fair16:38
palendaeIt's why I asked :)16:38
*** aruncewind has quit IRC16:38
*** jckasper has quit IRC16:38
odyssey4mebeyond liberty, in the M cycle, we have these blueprints to cover16:39
odyssey4me#link https://blueprints.launchpad.net/openstack-ansible/+spec/independent-role-repositories16:39
odyssey4me#link https://blueprints.launchpad.net/openstack-ansible/+spec/implement-rally-support16:39
*** SimonChung has quit IRC16:39
*** SimonChung1 has joined #openstack-meeting-416:39
odyssey4me#link https://blueprints.launchpad.net/openstack-ansible/+spec/multi-platform-host16:39
*** numan has quit IRC16:39
odyssey4methe rally role is actually ready already, but before we register a new repo for it we need to agree to register independent repositories for roles16:40
*** chenshuai has joined #openstack-meeting-416:40
odyssey4meie we need the agreement in principle to do it which is covered in https://review.openstack.org/21377916:41
odyssey4meI'd like us to get that review ready so that I can push it out to the ML for feedback next week.16:42
*** vikram_ has joined #openstack-meeting-416:42
*** armax has joined #openstack-meeting-416:43
odyssey4me#action hughsaunders and odyssey4me to prepare a spec for https://blueprints.launchpad.net/openstack-ansible/+spec/split-aio-gates16:43
odyssey4medoes anyone want to work with me to prepare a spec for https://blueprints.launchpad.net/openstack-ansible/+spec/multi-platform-host ?16:43
* hughsaunders looks around for redhat people16:44
odyssey4mehughsaunders so the idea I have is simply to instrument the plays to support alternative platforms16:45
*** ivar-laz_ has joined #openstack-meeting-416:45
odyssey4meit's easy enough to do - I have tested it out and have a method16:45
palendaeYeah, there's a standard pattern for that now16:45
odyssey4meat least from a package standpoint16:45
palendaePer-distro vars/playbooks16:45
odyssey4measide: https://review.openstack.org/215093 has merged on hpcloud - master is fair game (just rebase)16:45
odyssey4mepalendae no need for per distro playbooks - just vars will do16:46
palendaeAh, cool16:46
odyssey4meit won't make the code path onerous, so I think it's actually pretty easy16:46
palendaeI must be thinking of puppet then16:46
palendaeYeah16:46
*** ivar-lazzaro has quit IRC16:46
odyssey4mealso https://blueprints.launchpad.net/openstack-ansible/+spec/add-support-for-systemd will help16:47
odyssey4meI think that cloudnull has mostly got that worked out in a lab already16:47
palendaeYep16:47
palendaeAnd I would imagine there will be talk of moving ot 16.0416:47
palendaeThis needs to be done before that16:48
palendaeOr, rather, would make doing that move much, much easier16:48
odyssey4meyep16:48
palendaeAnd supporting distros already on systemd16:48
odyssey4me#topic Reviews16:49
*** openstack changes topic to "Reviews (Meeting topic: OpenStack Ansible Meeting)"16:49
odyssey4meas always, please keep an eye out on https://review.openstack.org/#/q/starredby:%22Jesse+Pretorius%22+project:stackforge/os-ansible-deployment,n,z16:49
odyssey4me#link https://review.openstack.org/#/q/starredby:%22Jesse+Pretorius%22+project:stackforge/os-ansible-deployment,n,z16:50
odyssey4me#topic Open discussion16:50
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack Ansible Meeting)"16:50
odyssey4meanyone want to raise anything?16:50
*** maxklyus has joined #openstack-meeting-416:51
*** VW_ has joined #openstack-meeting-416:51
odyssey4mealright, that's it then - thank you all for your time!16:52
odyssey4me#endmeeting16:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:52
palendaeNothing from me right now16:52
openstackMeeting ended Thu Aug 20 16:52:37 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-08-20-16.00.html16:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-08-20-16.00.txt16:52
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-08-20-16.00.log.html16:52
*** odyssey4me has left #openstack-meeting-416:52
*** TheIntern has left #openstack-meeting-416:53
*** IBerezovskiy has quit IRC16:53
*** stevelle has left #openstack-meeting-416:53
*** mohankumar_ has joined #openstack-meeting-416:56
*** cathy_ has joined #openstack-meeting-416:56
*** armax has quit IRC16:57
*** cathy_ has quit IRC16:58
*** johnsom_ has joined #openstack-meeting-416:59
*** klyusmax has joined #openstack-meeting-417:01
*** ashtokol_ has quit IRC17:01
*** Brian___ has joined #openstack-meeting-417:01
*** abhisriatt has joined #openstack-meeting-417:01
*** VW_ has quit IRC17:01
*** abhisriatt has left #openstack-meeting-417:02
*** armax has joined #openstack-meeting-417:02
*** abhisriatt has joined #openstack-meeting-417:02
*** VW_ has joined #openstack-meeting-417:02
*** cathy_ has joined #openstack-meeting-417:02
*** LouisF has joined #openstack-meeting-417:03
cathy_#startmeeting service_chaining17:03
openstackMeeting started Thu Aug 20 17:03:13 2015 UTC and is due to finish in 60 minutes.  The chair is cathy_. Information about MeetBot at http://wiki.debian.org/MeetBot.17:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:03
*** openstack changes topic to " (Meeting topic: service_chaining)"17:03
openstackThe meeting name has been set to 'service_chaining'17:03
*** georgewang has joined #openstack-meeting-417:03
georgewanghi17:03
cathy_hi everyone17:03
LouisFhi17:03
pcarverhi17:03
mohankumar_Hi Everyone !17:03
Swamihi17:03
Brian___hi17:03
maxklyushi17:03
abhisriatthi17:03
*** padkrish has joined #openstack-meeting-417:04
vikram_hi17:04
johnsom_o/17:04
cathy_today I have two topics to discuss. one is the review of the spec and codes including the insertion type. the other is the encap format17:04
cathy_any other topic?17:04
cathy_ok let's start with the first topic17:05
*** jay_s_b has joined #openstack-meeting-417:05
cathy_#topic review of the spec and codes17:05
*** openstack changes topic to "review of the spec and codes (Meeting topic: service_chaining)"17:05
cathy_Here is the link to review17:05
cathy_#link https://review.openstack.org/#/q/status:open+project:openstack/networking-sfc+branch:master+topic:networking-sfc,n,z17:05
*** VW_ has quit IRC17:07
*** pennerc has joined #openstack-meeting-417:07
cathy_The API spec has been ope for review for over 4 weeks. Now let's discuss the insertion/network type and reach consensus. Then I think it is ready for merge.17:07
cathy_I see Vikram and Paul's comment.17:07
cathy_The network type is per SF. That is, different SF could have different network types.17:08
pcarverwithin the same chain?17:08
cathy_We cna not predict what types of SFs a chain will have17:08
cathy_pcarver: yes.17:09
pcarverok17:09
LouisFpcarver: the may  be a mix of SFs in the same chain17:09
cathy_So we need to associate this network type with a SF's port pair, not with a chain17:10
*** dahoo has joined #openstack-meeting-417:10
*** dahoo is now known as jerryz17:10
*** KunalGandhi has joined #openstack-meeting-417:11
cathy_This network type is a attribute of a SF. SF could be provided by different vendors and could be of different types.17:11
vikram_can it have a default value?17:11
*** pennerc has quit IRC17:11
cathy_we do not know the default value since it is decided by the design/funcitonality provided by the SF vendor of the SF17:11
cathy_we do not know the default value since it is decided by the design/funcitonality provided by the SF vendor17:12
abhisriattwhat does “networy type” mean here? any example?17:12
*** chenshuai has quit IRC17:12
cathy_abhisriatt: network type means whether it is a L2 or L3 type SF or bump in the wire type17:13
abhisriattcathy_: Got it.17:13
cathy_The Switch's behavior will be different when forwarding the flow packet to different types of SF17:13
cathy_We have gone through these exercise in the data plane and found out that we need this network type specification in order for the data plane work properly17:14
cathy_So does everyone agree with adding this attribute to the port pair?17:14
LouisF+117:15
Brian___+117:15
LouisFi will change the name from insertion_type to network_type in the API doc17:15
georgewang+117:15
pcarver+117:15
abhisriatt+117:15
mohankumar_cathy_ : +1.. if we dont other way to handle it !17:16
*** ivar-la__ has joined #openstack-meeting-417:16
cathy_#agree add network_type attribute to the port pair in the API17:16
*** jwarendt has joined #openstack-meeting-417:17
*** s3wong has joined #openstack-meeting-417:17
*** ivar-laz_ has quit IRC17:17
s3wongsorry, late. 101N was terrible17:18
cathy_Could everyone go to the review links for all the spec and codes and either give your +1 or your comments. I am going to ask the Neutron PTL to approve it if no more major comments? They have been open for review for quite some time.17:18
cathy_s3wong: No. Thanks for joining17:18
cathy_Now let's go to second topic17:18
cathy_#topic data path encap format17:19
*** openstack changes topic to "data path encap format (Meeting topic: service_chaining)"17:19
cathy_Here is the link to the encap format which abhisriatt and I have put. Let's walk through them and see if any questions17:20
cathy_#link https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining17:20
cathy_abhisriatt: I see that you change the destination mac at the source VM's OVS. right?17:21
abhisriattcathy_:right.17:21
cathy_What type of SF are you assume is running on VM2?17:22
abhisriattcathy_:we have open flow rules on that host’s ovs to modify the destination mac.17:22
*** geoffarnold has joined #openstack-meeting-417:22
cathy_abhisriatt: Yes, I understand that. My question is whether we need to modify the destination mac.17:23
cathy_If the SF is L2 type, then there seems no need to modify the destination mac, but if it is L3, then yes we need to modify the destination mac otherwise the L3 SF will drop the packet17:24
cathy_For L2 type, the SF itself has L2 capability and can figure out how to forward the packet properly based on mac learning. Just think about when forwarding a packet to a L2 Switch, we would not need to modify the destination mac to be the switch's mac17:25
abhisriattcathy_: we modified the mac to make sure that the packet is steered to the SF node, instead of going to the destination.17:25
abhisriattwe didn’t assume anything as far as SFs are concerned.17:26
*** vikram_ has quit IRC17:26
abhisriattWe are still using Openstack’s GRE tunnels without creating any additional tunnels.17:26
*** SimonChung1 has quit IRC17:26
*** SimonChung has joined #openstack-meeting-417:26
cathy_OK, I see. Let me go through your flow again17:27
LouisFabhisriatt:   so in step 4 in your diagram you set DMAC to M4 when sending packet to VM217:27
*** harshs has joined #openstack-meeting-417:28
abhisriattLouisF: DMAC is set to M4 at step 2.17:28
abhisriattstep 4 is just carrying the same packet. At step 4, GRE tunnels will be stripped at br-tun, and the packet is delivered to VM2.17:29
*** chenshuai has joined #openstack-meeting-417:29
cathy_abhisriatt: OK, I think your flow format is good. But I will go through it after the meeting.17:30
LouisFabhisriatt: that means flow on node 1 must be aware of MAC on node 2?17:30
*** tfukushima has joined #openstack-meeting-417:31
abhisriattLouisF: Yes. we build that information graph as soon as we receive the SF request.17:31
cathy_I guess other people might need more time to go through it and we can continue reviewing the flow format after the meeting.17:31
LouisFabhisriatt: since you set DMAC = M4 on node 117:31
abhisriattcathy_ : sure.17:31
*** sjmc7 has left #openstack-meeting-417:31
*** ashtokol_ has joined #openstack-meeting-417:32
cathy_Another option is to change the destination mac on OVS 2 instead of OVS1. What do you think?17:32
abhisriattcathy_: Yes. But how would packet be routed to OVS2 to make that happen. If mac is not modified, the packet would have gone to OVS3.17:33
cathy_Since the OVS is programmed by OVS driver, we can choose how to program it.17:33
cathy_The outer header will make it to OVS217:33
abhisriattcathy_: The underlying GRE tunnels do the MAC learning. In that case, you have to flush the existing rules and create handcrafted rules.17:34
*** yamahata has quit IRC17:34
abhisriattcathy_: that would also affect the routing of other flows classes not part of SF.17:34
*** smccully has joined #openstack-meeting-417:34
cathy_abhisriatt: I think you are right.17:35
abhisriattcathy_: with this approach, we can rely on the underlying openstack networking to do all the work.17:36
*** yamamoto has quit IRC17:36
cathy_abhisriatt: let me think about this more and we can discuss this further in next meeting. And other folks could have time to think about it and bring their input/comments17:36
abhisriattcathy_: sounds good.17:37
cathy_abhisriatt: Agree17:37
abhisriattcathy_:yes.17:37
mohankumar_cathy_: okay17:37
*** geoffarnold has quit IRC17:38
s3wongcathy_: need to digest the diagram first17:39
cathy_abhisriatt: My original thought is same as yours and the diagram I sent you has the same flow format as yours. But later I feel some problem. Now I need to think about this again.17:39
cathy_s3wong: sure17:39
cathy_Any other topic ?17:39
pcarverI have a topic17:39
cathy_pcarver:OK17:40
abhisriattcathy_:”But later I feel some problem” — which encapsulation method are referring to?17:40
pcarverDo we know what the expectation is for packaging and deployment? I mean we're making some changes to existing components such as the OvS agent and neutronclient. How would we expect that this gets deployed?17:40
cathy_The one you posted. But now I think yours is correct. Let me think about it after the meeting and get back to you17:41
cathy_pcarver: god question17:41
pcarverDoes this have to get merged back into Neutron before it's practically available?17:41
abhisriattcathy_:sure. sounds good.17:41
*** salv-orlando has joined #openstack-meeting-417:42
pcarverOr do we have some notion of how someone would deploy Neutron and then additionally deploy networking-sfc17:42
cathy_We will follow similar mechanism done for DVR or other Neutron approved sub-project17:42
Swamicathy_: DVR was part of neutron17:42
cathy_I need to do some investigation or ask Kyle/Armando or other core member on this.17:43
s3wonghow is it done for l2gw?17:43
pcarverthis big tent thing is new17:43
cathy_pcarver: yes, it is new. Let me ask Kyle on that17:43
pcarverI was going to post to the mailing list to see if there's a general view on how it should work17:44
cathy_s3wong: yes, L2GW is an example17:44
cathy_or dragonflow sub-project17:44
cathy_AFAIK dragonflow will be release in Liberty17:44
cathy_Swami: welcome back! do you know how other sub-project is packaged and released, deployed?17:45
SwamiSwami: no I don't know17:45
pcarverIt seems to me that somehow there has to be a code merge17:46
pcarverIf we're making copies of existing Neutron components into the networking-sfc repo17:46
*** salv-orlando has quit IRC17:46
pcarverIf we only used inheritance or APIs then it would be different17:46
s3wongl2gw seems to be using ovsdb instead of extending existing ovs agent; nevermind17:46
pcarverbut I believe we're actually making changes to specific Python files that would be pre-existing from Neutron packages17:47
*** krtaylor has joined #openstack-meeting-417:47
pcarverAnd a deployer wouldn't want to overwrite Liberty Neutron packages with files from networking-sfc if we haven't merged in all non-sfc Liberty Neutron development17:48
s3wongdragonfly seems to also has its own agent instead of extending Neutron OVS agent...17:48
*** bharath has joined #openstack-meeting-417:48
*** SumitNaiksatam has joined #openstack-meeting-417:48
s3wong* dragonflow (damn auto-correct)17:48
pcarverThat's part of the reason that the AT&T SFC that abhisriatt worked on in R&D was built as a standalone thing17:48
s3wongwe may have to do that as well --- have our own OVS-sfc agent17:49
*** johnsom_ is now known as johnsom17:49
LouisFs3wong: yes that may be a solution17:49
abhisriattpcarver: I was going to give the same reason :)17:49
pcarverIt was built to interact with public Neutron APIs and it manipulates OvS directly rather than modifying Neutron's OvS agent17:49
s3wongpcarver: seems like that is the approach for the other subprojects that are using OVS as well17:50
pcarverIt does make sense to integrate it long term, but I'm not clear on how it will work in the big tent model17:50
cathy_pcarver: you raised a very criitical question. We need to get a clear answer on this.17:50
abhisriatts3wong: can we not adopt the same external approach?17:50
s3wongpcarver: yeah... for stuff like dragonflow, I am not sure if it would ever be merged into Neutron core repo17:51
*** padkrish has quit IRC17:51
cathy_pcarver: s3wong would you like to take this action item together with me?17:51
*** mk has joined #openstack-meeting-417:51
s3wongabhisriatt: what is the alternative? Refactor OVS agent to make it extensible?17:51
*** mk is now known as Guest7127417:52
pcarvers3wong: now that might not be a bad idea to think about17:52
s3wongcathy_: sure... I meant to investigate this actually. It was a good thing pcarver brought it up17:52
pcarverAlterntively, how clear are you on super()?17:52
abhisriatts3wong: having a separate SFC agent to talk to ovs switches.17:52
pcarverI've watched Raymond Hettinger's PyCon talk on Super considered super and I'm wondering if we might leverage that approach17:53
*** georgewang has quit IRC17:53
s3wongpcarver: so SFC would implement a child class of ova agent class?17:53
cathy_AFAIK, modifying existing OVS agent is the way some other projects use17:54
pcarverI haven't thought through all the details here, but wondering if would be possible to alter the components in Neutron to inherit functions from SFC classes17:54
cathy_I mean extending OVS agent17:54
s3wongabhisriatt: that was what we've been talking about so far, right? Have our own agent that runs (hopefully never in conflict with) in conjunction with the Neutron OVS agent?17:54
LouisFs3wong: yes can have a child class of ovs agent17:54
*** klyusmax has quit IRC17:54
abhisriatts3wong: yes.17:54
pcarverI think the two options are to write totally independent components (for API, DB and agent) or to find a way to dynamically (at runtime) inherit functionality17:55
cathy_OK, let's take the action item and find out how we should proceed with the packaging, release, and coding17:56
pcarverWhat I don't think will work well is to have a Neutron version of a given .py file and a networking-sfc version of the same .py file17:56
*** daneyon_ has left #openstack-meeting-417:56
s3wongpcarver: in generally, SFC library has a dependency on Neutron package --- so we can have Neutron ovs agent inheriting from SFC OVS agent class to adopt functionality17:57
s3wong* in general17:57
cathy_s3wong: +117:57
cathy_Time is up. Let's warp up.17:57
s3wong* can't17:57
s3wong(sorry)17:57
pcarverThe direction of the inheritance is what I haven't figured out yet. The obvious approach would be to strictly inherit from Neutron into our own classes. But Hettinger's talk about replacing suppliers at runtime got me thinking of maybe doing it the other way around.17:57
s3wongpcarver: obviously I am not a Python expert :-)17:58
*** puranamr has quit IRC17:58
s3wongcathy_: let's put that investigation as an #action17:58
pcarverIn that case I highly recommend the talk. It's on Youtube. I'm not a Python guru either but I found it enlightening.17:58
s3wongpcarver: sure17:58
pcarverhttps://www.youtube.com/watch?v=EiOglTERPEo17:58
mohankumar_for client code , we inherit neutronclient code and using it as extension API17:59
*** puranamr has joined #openstack-meeting-417:59
cathy_pcarver: thanks for the link17:59
s3wongmohankumar_: yes, that direction makes sense17:59
*** woodard has quit IRC17:59
cathy_Ok, everyone, let's sync up next meeting. Please go to the links to give your final review.17:59
cathy_bye for now18:00
s3wongmohankumar_: though now we are thinking about having installed and loaded an agent on host, then dynamically load a library on top... don't know if it has been done before yet18:00
s3wongThanks guys!18:00
Brian___bye18:00
LouisFbye18:00
abhisriattbye18:00
cathy_#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Thu Aug 20 18:00:52 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-08-20-17.03.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-08-20-17.03.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-08-20-17.03.log.html18:00
*** puranamr has quit IRC18:00
mohankumar_its been followed other extension pjt also18:00
mohankumar_bye18:01
*** chenshuai has quit IRC18:01
*** VW_ has joined #openstack-meeting-418:01
*** CheKoLyN has joined #openstack-meeting-418:04
*** padkrish has joined #openstack-meeting-418:04
*** johnsom has left #openstack-meeting-418:05
*** mohankumar_ has quit IRC18:06
*** woodard has joined #openstack-meeting-418:06
*** puranamr has joined #openstack-meeting-418:06
*** woodard has quit IRC18:07
*** abhisriatt has left #openstack-meeting-418:07
*** woodard has joined #openstack-meeting-418:07
*** jay_s_b has quit IRC18:08
*** Brian___ has quit IRC18:09
*** bapalm has quit IRC18:11
*** jwagner is now known as jwagner_away18:13
*** bapalm has joined #openstack-meeting-418:14
*** GB21 has quit IRC18:15
*** padkrish has quit IRC18:16
*** padkrish has joined #openstack-meeting-418:17
*** chenshuai has joined #openstack-meeting-418:17
*** ashtokol_ has quit IRC18:18
*** armax has quit IRC18:18
*** nhairston has joined #openstack-meeting-418:21
*** padkrish has quit IRC18:21
*** padkrish has joined #openstack-meeting-418:21
*** pennerc has joined #openstack-meeting-418:24
*** fawadk has quit IRC18:27
*** pennerc has quit IRC18:27
*** pennerc has joined #openstack-meeting-418:27
*** SimonChung1 has joined #openstack-meeting-418:28
*** SimonChung has quit IRC18:28
*** geoffarnold has joined #openstack-meeting-418:28
*** nhairston has quit IRC18:33
*** CheKoLyN has quit IRC18:34
*** Sukhdev has joined #openstack-meeting-418:34
*** yamamoto has joined #openstack-meeting-418:37
*** VW_ has quit IRC18:38
*** pennerc has quit IRC18:38
*** pennerc has joined #openstack-meeting-418:39
*** yamamoto has quit IRC18:42
*** pennerc has quit IRC18:43
*** dannywilson has quit IRC18:44
*** dannywilson has joined #openstack-meeting-418:46
*** cathy_ has quit IRC18:47
*** vivek-ebay has quit IRC18:49
*** vivek-ebay has joined #openstack-meeting-418:49
*** davidlenwell has quit IRC18:50
*** chenshuai has quit IRC18:50
*** CheKoLyN has joined #openstack-meeting-418:51
*** davidlenwell has joined #openstack-meeting-418:51
*** nhairston has joined #openstack-meeting-418:57
*** davidlenwell has quit IRC18:58
*** puranamr has quit IRC18:58
*** davidlenwell has joined #openstack-meeting-418:59
*** geoffarnold has quit IRC19:00
*** singleth_ has joined #openstack-meeting-419:00
*** singlethink has quit IRC19:03
*** dannywilson has quit IRC19:04
*** dannywilson has joined #openstack-meeting-419:05
*** chenshuai has joined #openstack-meeting-419:06
*** dannywilson has quit IRC19:10
*** dannywilson has joined #openstack-meeting-419:10
*** tfukushima has quit IRC19:12
*** tfukushima has joined #openstack-meeting-419:19
*** Guest71274 has quit IRC19:19
*** dims_ has joined #openstack-meeting-419:26
*** vishwana_ has joined #openstack-meeting-419:26
*** ivar-lazzaro has joined #openstack-meeting-419:27
*** tfukushima has quit IRC19:27
*** dolphm has quit IRC19:27
*** ttx has quit IRC19:27
*** jckasper has joined #openstack-meeting-419:27
*** rex_lee has quit IRC19:27
*** dims has quit IRC19:28
*** masteinhauser has quit IRC19:28
*** davidlenwell has quit IRC19:28
*** ivar-la__ has quit IRC19:28
*** vishwanathj has quit IRC19:28
*** sbalukoff has quit IRC19:28
*** palendae has quit IRC19:28
*** timsim has quit IRC19:28
*** sankarshan_away has quit IRC19:28
*** sbog has quit IRC19:28
*** serverascode has quit IRC19:28
*** yhvh has quit IRC19:28
*** irenab has quit IRC19:29
*** davidlenwell has joined #openstack-meeting-419:31
*** masteinhauser has joined #openstack-meeting-419:32
*** masteinhauser is now known as Guest7776119:32
*** serverascode has joined #openstack-meeting-419:32
*** VW_ has joined #openstack-meeting-419:33
*** ttx has joined #openstack-meeting-419:33
*** yhvh has joined #openstack-meeting-419:33
*** rex_lee has joined #openstack-meeting-419:34
*** timsim has joined #openstack-meeting-419:35
*** sbog has joined #openstack-meeting-419:36
*** dolphm has joined #openstack-meeting-419:36
*** palendae has joined #openstack-meeting-419:36
*** padkrish has quit IRC19:36
*** puranamr has joined #openstack-meeting-419:38
*** ivar-lazzaro has quit IRC19:39
*** s3wong has quit IRC19:39
*** chenshuai has quit IRC19:39
*** alex_didenko has quit IRC19:41
*** alex_didenko has joined #openstack-meeting-419:41
*** salv-orlando has joined #openstack-meeting-419:41
*** sbalukoff has joined #openstack-meeting-419:42
*** VW_ has quit IRC19:43
*** VW_ has joined #openstack-meeting-419:43
*** SimonChung has joined #openstack-meeting-419:46
*** SimonChung1 has quit IRC19:46
*** timsim has quit IRC19:47
*** armax has joined #openstack-meeting-419:47
*** FallenPegasus has joined #openstack-meeting-419:47
*** timsim has joined #openstack-meeting-419:47
*** SimonChung1 has joined #openstack-meeting-419:48
*** SimonChung has quit IRC19:48
*** VW_ has quit IRC19:48
*** singlethink has joined #openstack-meeting-419:51
*** padkrish has joined #openstack-meeting-419:52
*** padkrish has joined #openstack-meeting-419:52
*** ajmiller has quit IRC19:53
*** singleth_ has quit IRC19:54
*** chenshuai has joined #openstack-meeting-419:55
*** padkrish has quit IRC19:56
*** chenshuai has quit IRC19:59
*** chenshuai has joined #openstack-meeting-419:59
*** puranamr has quit IRC20:00
*** puranamr has joined #openstack-meeting-420:13
*** irenab has joined #openstack-meeting-420:15
*** ajayaa has quit IRC20:19
*** VW_ has joined #openstack-meeting-420:22
*** Guest77761 is now known as masteinhauser20:22
*** chenshuai has quit IRC20:29
*** VW_ has quit IRC20:30
*** VW_ has joined #openstack-meeting-420:31
*** ashtokol_ has joined #openstack-meeting-420:33
*** Sukhdev has quit IRC20:34
*** VW_ has quit IRC20:35
*** ashtokol_ has quit IRC20:37
*** padkrish has joined #openstack-meeting-420:38
*** padkrish has quit IRC20:42
*** chenshuai has joined #openstack-meeting-420:44
*** FallenPegasus has quit IRC20:44
*** aventera_ has joined #openstack-meeting-420:47
*** geoffarnold has joined #openstack-meeting-420:47
*** aventera_ has quit IRC20:47
*** puranamr has quit IRC20:47
*** aventera_ has joined #openstack-meeting-420:48
*** armax has quit IRC20:49
*** SimonChung1 has quit IRC20:50
*** aventerav has quit IRC20:50
*** geoffarnold has quit IRC20:52
*** ashtokol_ has joined #openstack-meeting-420:53
*** dannywil_ has joined #openstack-meeting-421:00
*** geoffarnold has joined #openstack-meeting-421:00
*** ivar-lazzaro has joined #openstack-meeting-421:02
*** dannywilson has quit IRC21:03
*** FallenPegasus has joined #openstack-meeting-421:05
*** woodard has quit IRC21:05
*** yamahata has joined #openstack-meeting-421:10
*** chenshuai has quit IRC21:14
*** chenshuai has joined #openstack-meeting-421:14
*** FallenPegasus has quit IRC21:22
*** rfolco has quit IRC21:23
*** padkrish has joined #openstack-meeting-421:24
*** krtaylor has quit IRC21:26
*** armax has joined #openstack-meeting-421:26
*** nhairston has quit IRC21:36
*** sigmavirus24 is now known as sigmavirus24_awa21:38
*** dannywil_ has quit IRC21:40
*** VW_ has joined #openstack-meeting-421:43
*** SimonChung has joined #openstack-meeting-421:43
*** chenshuai has quit IRC21:46
*** chenshuai has joined #openstack-meeting-421:46
*** FallenPegasus has joined #openstack-meeting-421:48
*** bapalm has quit IRC21:49
*** bapalm has joined #openstack-meeting-421:52
*** dannywilson has joined #openstack-meeting-421:54
*** britthouser has quit IRC21:54
*** sigmavirus24_awa is now known as sigmavirus2421:54
*** bapalm has quit IRC21:57
*** geoffarnold has quit IRC22:01
*** geoffarnold has joined #openstack-meeting-422:02
*** bapalm has joined #openstack-meeting-422:03
*** klamath has quit IRC22:05
*** LouisF has quit IRC22:06
*** bapalm has quit IRC22:08
*** s3wong has joined #openstack-meeting-422:12
*** bapalm has joined #openstack-meeting-422:14
*** krtaylor has joined #openstack-meeting-422:18
*** bapalm has quit IRC22:19
*** chenshuai has quit IRC22:19
*** jecarey has quit IRC22:28
*** bapalm has joined #openstack-meeting-422:29
*** bapalm has quit IRC22:34
*** chenshuai has joined #openstack-meeting-422:35
*** bapalm has joined #openstack-meeting-422:35
*** tfukushima has joined #openstack-meeting-422:37
*** rfolco has joined #openstack-meeting-422:39
*** jwagner_away is now known as jwagner22:42
*** bapalm has quit IRC22:43
*** bapalm has joined #openstack-meeting-422:43
*** ashtokol_ has quit IRC22:44
*** georgewang has joined #openstack-meeting-422:45
georgewang#help22:46
georgewangwhois22:46
georgewangwhois georgewang22:46
georgewang#whois georgewang22:47
georgewang#whois22:47
*** bapalm has quit IRC22:48
*** dannywilson has quit IRC22:48
*** georgewang_ has joined #openstack-meeting-422:48
*** bapalm has joined #openstack-meeting-422:51
*** georgewang has quit IRC22:51
*** s3wong has quit IRC22:52
*** tfukushima has quit IRC22:55
*** dannywilson has joined #openstack-meeting-422:57
*** singlethink has quit IRC22:59
*** FallenPegasus has quit IRC23:08
*** chenshuai has quit IRC23:08
*** FallenPegasus has joined #openstack-meeting-423:10
*** aventera_ has quit IRC23:11
*** sigmavirus24 is now known as sigmavirus24_awa23:18
*** blahRus has quit IRC23:18
*** jpekkari has joined #openstack-meeting-423:18
*** dannywilson has quit IRC23:19
*** chenshuai has joined #openstack-meeting-423:23
*** VW_ has quit IRC23:25
*** VW_ has joined #openstack-meeting-423:25
*** dannywilson has joined #openstack-meeting-423:30
*** VW_ has quit IRC23:30
*** banix has quit IRC23:33
*** VW_ has joined #openstack-meeting-423:34
*** s3wong has joined #openstack-meeting-423:35
*** geoffarnold has quit IRC23:43
*** salv-orlando has quit IRC23:46
*** Swami has quit IRC23:48
*** ashtokol_ has joined #openstack-meeting-423:49
*** harshs has quit IRC23:50
*** ashtokol_ has quit IRC23:54
*** chenshuai has quit IRC23:56
*** FallenPegasus has quit IRC23:56
*** dannywilson has quit IRC23:56
*** VW_ has quit IRC23:56
*** VW_ has joined #openstack-meeting-423:57
*** SumitNaiksatam has quit IRC23:59

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