Thursday, 2015-09-10

*** banix has joined #openstack-meeting-400:00
*** markvoelker has quit IRC00:01
*** Sukhdev has quit IRC00:07
*** Sukhdev has joined #openstack-meeting-400:07
*** SimonChung has quit IRC00:08
*** CheKoLyN has joined #openstack-meeting-400:14
*** watanabe_isao has joined #openstack-meeting-400:16
*** watanabe_isao has quit IRC00:17
*** wshao has joined #openstack-meeting-400:24
*** qwebirc71560 has joined #openstack-meeting-400:27
*** CheKoLyN has quit IRC00:29
*** bharathm has quit IRC00:33
*** ivar-lazzaro has quit IRC00:39
*** puranamr has joined #openstack-meeting-400:39
*** chenshuai has joined #openstack-meeting-400:40
*** xichengc has joined #openstack-meeting-400:40
*** CheKoLyN has joined #openstack-meeting-400:42
*** Swami has quit IRC00:46
*** xichengc has quit IRC00:48
*** armax has joined #openstack-meeting-400:50
*** xichengc has joined #openstack-meeting-400:50
*** qwebirc71560 has quit IRC00:50
*** rfolco has quit IRC00:52
*** rockyg has joined #openstack-meeting-400:57
*** markvoelker has joined #openstack-meeting-400:58
*** stanchan_ has joined #openstack-meeting-400:58
xichengchey rockyg00:59
xichengclet's wait for Weidong to log on00:59
rockyghi xichengc00:59
chenshuaihi guys00:59
chigangbaigk is going to apply his passport, so he will miss this meeting01:00
xichengcWill you cover his part?01:00
xichengcToday will be about status sync01:01
xichengchello wshao01:01
*** grakiss has joined #openstack-meeting-401:01
wshaolet's sync up on the upstream ansible status01:01
chigangxichengc: xuhan will cover baigk, let us wait01:01
*** xuhan1 has joined #openstack-meeting-401:01
*** FallenPegasus has joined #openstack-meeting-401:02
chigangxuhan1: hi01:02
xichengc#startmeeting Compass Status Syncup01:02
openstackMeeting started Thu Sep 10 01:02:23 2015 UTC and is due to finish in 60 minutes.  The chair is xichengc. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:02
wshaochigang: we are waiting on more detailed info on the status so that we can integrate the Compass metadata etc to support it01:02
*** openstack changes topic to " (Meeting topic: Compass Status Syncup)"01:02
openstackThe meeting name has been set to 'compass_status_syncup'01:02
*** markvoelker has quit IRC01:02
*** xuhan has joined #openstack-meeting-401:02
xichengc#topic upstream ansible status01:02
*** openstack changes topic to "upstream ansible status (Meeting topic: Compass Status Syncup)"01:02
*** Brian has joined #openstack-meeting-401:03
*** Brian is now known as Guest564101:03
chigang#info we have finished deploying AllinOne Openstack by OSAD01:04
wshaoany further progress beyond all-in-one?01:04
chigang#info but speed is too low01:04
xichengcchigang could you provide us the paramters as we talked about?01:04
wshaochigang: we shall raise the question to the mailing list, on offline install option.01:05
chigangwshao: OSAD dont support offline installation01:05
xichengc#action wshao and chigang to raise the installation speed question to the openstack-dev mailing list01:05
wshaoxichengc: could you send a message with [Compass] and [Openstack-ansible-deployment] prefix?01:06
xichengcwshao to the openstack-dev mailing list?01:06
wshaoit does not support. But shall they support the use case of offline-install?01:06
chigangwshao: it is too slow installation in China, the network condition is not good for us01:06
wshaoA common requirement for many data center installation.01:06
*** gyu has joined #openstack-meeting-401:07
wshaoyes. openstack-dev01:07
xichengcwshao the question is "is OSAD responsible for supporting offline install or is it compass/fuel's responsibility to support it in our installers"01:08
wshaoinstallers. but OSAD as a building block has to support it also.01:09
*** bharathm has joined #openstack-meeting-401:09
xuhanOSAD will build repo, if installer do another, it may waste more time01:10
rockygxichengc, it's not who is responsible.  There is a use case for offline install.  The question is whether they plan to address the use case, or maybe someone can provide it to them01:10
xichengcother than putting rpm repo urls and download links in config file instead of hardcoding it in ansible yml tasks, I am not sure what else they can do to support offline installation01:10
*** geoffarnold is now known as geoffarnoldX01:10
chenshuaithe aim of OPNFV for installers is to support deployment offline, and compass4nfv is working on this01:11
chenshuaiso I think OSAD need support also01:11
wshaook. one way to do that is to have OSAD support two phases: build and install.01:11
wshaoAt build phase, internet access is assumed. but at install phase, it support offline. Let me study if that is possible, and then send out a question to them.01:12
xichengcrockyg are they fully aware of this use case? Is there any installers that have already done it?01:12
chenshuaiwshao: yes, build phase is not needed offline, but deployment need01:12
wshaoxichengc: the requirement is valid, regardless of the current status.01:13
wshaochenshuai: thanks,01:13
wshaook, let's move on01:14
xichengcshould i action it to you?01:14
rockygDon't know if they are aware.  So, the way to write the email is to first state the use case and that it is a fairly common one.  then to pose the question of whether they are planning to address it already or if a new spec needs to be written.01:14
wshaorockyg: thanks01:14
xichengcthanks rockyg01:14
wshaomove on to the topic of "plugin".01:15
xichengc#action wshao to conduct research on the possibility of having two phases of installation: build and install01:15
*** dims_ has joined #openstack-meeting-401:16
xichengc#topic status on OSAD as a compass plugin01:16
*** openstack changes topic to "status on OSAD as a compass plugin (Meeting topic: Compass Status Syncup)"01:16
wshaocurrent plugins are not cleanly separated from compass-core, Carl is looking into a better plugin mechanism. Fuel 6.0 has a clean way of adding plugin. It allows extensions from independent 3rd-party developers.01:16
*** bobmel has joined #openstack-meeting-401:17
wshaoIn our case, the Cobbler is tightly coupled from compass-core code, so is the snmp-based discovery, and Chef-based package installer.01:17
*** armax has quit IRC01:17
wshaohope to see some progress on this by next week.01:18
xichengcthanks wshao. what about adding OSAD as a compass adapter?01:19
*** dims has quit IRC01:19
xichengca separate topic?01:19
chenshuaiwhat's difference between as a plugin and as a adapter?01:20
*** bobmel has quit IRC01:21
wshaogood question, a plugin is a code extension. where a single plugin may support more than one adapters.01:21
wshaoeg., chef installer could be a plugin, but that pluging support two adapters => IceHouse chef cookbooks, and Kilo.01:22
*** puranamr has quit IRC01:22
chenshuaiall right, thanks01:22
wshaook. any other topics?01:23
*** puranamr has joined #openstack-meeting-401:23
*** julim has joined #openstack-meeting-401:23
xichengcHas gyu received the paramters from baigk?01:24
gyunot yet01:24
xichengccan we accelerate on that? chigang01:24
wshaoxichengc: have an action on that.01:24
*** xingchao has joined #openstack-meeting-401:24
chigangbaigk is leaving for apply passport01:25
chigangwhen he come back, I will tell to handle it01:25
xichengc#action baigk to provide parameters to gyu for OSAD integration01:25
chigangmaybe next month he will go to Santa Clara:)01:26
xichengcwshao anything else?01:26
*** wshao_ has joined #openstack-meeting-401:27
xichengcwshao had to leave first01:29
xichengcany other topics?01:29
xichengcany other topics? 5..01:30
xichengcany other topics? 4..01:30
xichengcany other topics? 3..01:30
*** sballe has joined #openstack-meeting-401:30
xichengcany other topics? 2..01:30
xichengcany other topics? 1..01:30
xichengcThank you01:30
*** openstack changes topic to "OpenStack Meetings ||"01:30
openstackMeeting ended Thu Sep 10 01:30:21 2015 UTC.  Information about MeetBot at . (v 0.1.4)01:30
openstackMinutes (text):
rockygthanks all01:30
*** gyu has quit IRC01:30
chigangthanks all,too01:30
*** xichengc has quit IRC01:31
*** xuhan1 has quit IRC01:32
*** rockyg has quit IRC01:33
*** wshao has quit IRC01:36
*** wshao_ is now known as wshao01:36
*** stanchan has joined #openstack-meeting-401:42
*** harshs has quit IRC01:42
*** armax has joined #openstack-meeting-401:42
*** stanchan_ has quit IRC01:43
*** baoli has joined #openstack-meeting-401:43
*** Sukhdev has quit IRC01:43
*** s3wong has quit IRC01:50
*** vishwanathj has quit IRC01:50
*** xingchao has quit IRC01:51
*** baoli has quit IRC01:56
*** zeih has quit IRC01:59
*** zeih has joined #openstack-meeting-402:00
*** FallenPegasus has quit IRC02:01
*** dannywilson has quit IRC02:04
*** baoli has joined #openstack-meeting-402:04
*** armax has quit IRC02:16
*** sbalukoff has quit IRC02:19
*** yamahata has quit IRC02:20
*** VW_ has joined #openstack-meeting-402:22
*** CheKoLyN has quit IRC02:24
*** stanchan has quit IRC02:29
*** stanchan has joined #openstack-meeting-402:32
*** KunalGandhi has quit IRC02:32
*** xingchao has joined #openstack-meeting-402:33
*** tfukushima has joined #openstack-meeting-402:37
*** stanchan has quit IRC02:42
*** puranamr has quit IRC02:45
*** stanchan has joined #openstack-meeting-402:47
*** vivek-ebay has quit IRC02:48
*** geoffarnoldX is now known as geoffarnold02:50
*** puranamr has joined #openstack-meeting-402:52
*** VW_ has quit IRC02:53
*** VW_ has joined #openstack-meeting-402:54
*** markvoelker has joined #openstack-meeting-402:55
*** sdake_ has joined #openstack-meeting-402:56
*** sdake__ has joined #openstack-meeting-402:57
*** sdake has quit IRC02:58
*** VW_ has quit IRC02:59
*** armax has joined #openstack-meeting-402:59
*** sdake_ has quit IRC03:01
*** yamamoto has joined #openstack-meeting-403:01
*** stanchan_ has joined #openstack-meeting-403:01
*** jerryz has quit IRC03:02
*** puranamr has quit IRC03:03
*** stanchan has quit IRC03:03
*** puranamr has joined #openstack-meeting-403:03
*** stanchan has joined #openstack-meeting-403:09
*** harshs has joined #openstack-meeting-403:12
*** stanchan_ has quit IRC03:13
*** xuhan1 has joined #openstack-meeting-403:14
*** stanchan_ has joined #openstack-meeting-403:16
*** stanchan has quit IRC03:18
*** zeih has quit IRC03:20
*** zeih has joined #openstack-meeting-403:20
*** stanchan_ has quit IRC03:21
*** dims_ has quit IRC03:23
*** stanchan has joined #openstack-meeting-403:24
*** sarob has quit IRC03:25
*** timsim has quit IRC03:26
*** dolphm has quit IRC03:27
*** sigmavirus24 has quit IRC03:27
*** eglute has quit IRC03:27
*** d34dh0r53 has quit IRC03:27
*** palendae has quit IRC03:27
*** sarob has joined #openstack-meeting-403:28
*** d34dh0r53 has joined #openstack-meeting-403:28
*** timsim has joined #openstack-meeting-403:28
*** eglute has joined #openstack-meeting-403:28
*** dolphm has joined #openstack-meeting-403:28
*** VW_ has joined #openstack-meeting-403:29
*** palendae has joined #openstack-meeting-403:29
*** sdake__ is now known as sdake03:30
*** sigmavirus24 has joined #openstack-meeting-403:30
*** stanchan has quit IRC03:32
*** stanchan_ has joined #openstack-meeting-403:32
*** palendae has quit IRC03:36
*** palendae has joined #openstack-meeting-403:37
*** jerryz has joined #openstack-meeting-403:38
*** sigmavirus24 is now known as sigmavirus24_awa03:39
*** bobmel has joined #openstack-meeting-403:44
*** puranamr has quit IRC03:48
*** bobmel has quit IRC03:48
*** lakshmiS has joined #openstack-meeting-403:48
*** jckasper has quit IRC03:49
*** SimonChung has joined #openstack-meeting-403:49
*** geoffarnold is now known as geoffarnoldX03:51
*** SimonChung1 has joined #openstack-meeting-403:51
*** stanchan has joined #openstack-meeting-403:51
*** SimonChung has quit IRC03:54
*** baigk has quit IRC03:54
*** wshao has quit IRC03:54
*** stanchan_ has quit IRC03:55
*** sbalukoff has joined #openstack-meeting-403:56
*** sballe has quit IRC03:56
*** VW_ has quit IRC03:57
*** VW_ has joined #openstack-meeting-403:57
*** chenshuai1 has joined #openstack-meeting-404:00
*** watanabe_isao has joined #openstack-meeting-404:00
*** chenshuai has quit IRC04:01
*** chenshuai1 is now known as chenshuai04:01
*** baigk has joined #openstack-meeting-404:01
*** VW_ has quit IRC04:02
*** sbalukoff has quit IRC04:02
*** sbalukoff has joined #openstack-meeting-404:03
*** Guest5641 has quit IRC04:05
*** baoli has quit IRC04:10
*** geoffarnoldX is now known as geoffarnold04:19
*** banix has quit IRC04:19
*** geoffarnold is now known as geoffarnoldX04:20
*** dims has joined #openstack-meeting-404:23
*** watanabe_isao has quit IRC04:24
*** Brian has joined #openstack-meeting-404:26
*** Brian is now known as Guest6584504:26
*** FallenPegasus has joined #openstack-meeting-404:27
*** lazy_prince has joined #openstack-meeting-404:27
*** dims has quit IRC04:30
*** Guest65845 has quit IRC04:31
*** IlyaG has quit IRC04:34
*** xingchao has quit IRC04:35
*** jckasper has joined #openstack-meeting-404:48
*** chenshuai has quit IRC04:52
*** xuhan1 has quit IRC04:54
*** markvoelker has quit IRC04:55
*** yamahata has joined #openstack-meeting-404:59
*** sdake_ has joined #openstack-meeting-405:12
*** jpekkari has joined #openstack-meeting-405:13
*** sdake has quit IRC05:15
*** sdake_ has quit IRC05:16
*** sdake_ has joined #openstack-meeting-405:18
*** Sukhdev has joined #openstack-meeting-405:19
*** sdake_ is now known as sdake05:21
*** baigk has quit IRC05:24
*** vishwanathj has joined #openstack-meeting-405:27
*** vishwanathj has quit IRC05:28
*** baigk has joined #openstack-meeting-405:28
*** sdake_ has joined #openstack-meeting-405:29
*** sdake has quit IRC05:30
*** baigk has quit IRC05:31
*** Brian has joined #openstack-meeting-405:33
*** Brian is now known as Guest4078905:33
*** baigk has joined #openstack-meeting-405:36
*** harshs has quit IRC05:55
*** numans has joined #openstack-meeting-405:56
*** markvoelker has joined #openstack-meeting-405:56
*** lakshmiS has quit IRC06:00
*** markvoelker has quit IRC06:01
*** lakshmiS has joined #openstack-meeting-406:03
*** simon-AS559 has joined #openstack-meeting-406:03
*** simon-AS5591 has joined #openstack-meeting-406:05
*** simon-AS559 has quit IRC06:08
*** sdake has joined #openstack-meeting-406:08
*** simon-AS5591 has quit IRC06:09
*** bobmel has joined #openstack-meeting-406:11
*** ajayaa has joined #openstack-meeting-406:11
*** sdake_ has quit IRC06:11
*** chenshuai has joined #openstack-meeting-406:15
*** bobmel has quit IRC06:16
*** bouthors has joined #openstack-meeting-406:23
*** ajayaa has quit IRC06:25
*** stanchan has quit IRC06:26
*** GB21 has joined #openstack-meeting-406:27
*** sdake has quit IRC06:28
*** stanchan has joined #openstack-meeting-406:28
*** sdake has joined #openstack-meeting-406:28
*** simon-AS559 has joined #openstack-meeting-406:29
*** May-meimei has quit IRC06:34
*** ajayaa has joined #openstack-meeting-406:37
*** May-meimei has joined #openstack-meeting-406:39
*** evgenyf has joined #openstack-meeting-406:50
*** stanchan_ has joined #openstack-meeting-406:50
*** irenab has joined #openstack-meeting-406:50
*** stanchan has quit IRC06:52
*** FallenPegasus has quit IRC06:55
*** simon-AS559 has left #openstack-meeting-406:58
*** bouthors has quit IRC07:09
*** Sukhdev has quit IRC07:19
*** matrohon has joined #openstack-meeting-407:39
*** amotoki has joined #openstack-meeting-407:55
*** markvoelker has joined #openstack-meeting-407:57
*** bapalm has quit IRC07:58
*** bapalm has joined #openstack-meeting-408:00
*** markvoelker has quit IRC08:02
*** lakshmiS has quit IRC08:03
*** lakshmiS has joined #openstack-meeting-408:03
*** sdake has quit IRC08:17
*** s-kawabata has quit IRC08:25
*** fitoduarte has joined #openstack-meeting-408:28
*** numans has quit IRC08:34
*** xingchao has joined #openstack-meeting-408:40
*** yamamoto_ has joined #openstack-meeting-408:44
*** yamamoto has quit IRC08:44
*** yamamoto has joined #openstack-meeting-408:44
*** yamamoto_ has quit IRC08:48
*** numans has joined #openstack-meeting-408:53
*** numans has quit IRC08:54
*** numans has joined #openstack-meeting-408:54
*** markvoelker has joined #openstack-meeting-408:58
*** fitoduarte has quit IRC08:58
*** ashtokolov has joined #openstack-meeting-409:01
*** markvoelker has quit IRC09:02
*** vbel has left #openstack-meeting-409:03
*** bnemec has quit IRC09:13
*** bnemec has joined #openstack-meeting-409:14
*** jerryz has quit IRC09:24
*** numans has quit IRC09:26
*** GB21 has quit IRC09:30
*** dims has joined #openstack-meeting-409:31
*** dims has quit IRC09:38
*** GB21 has joined #openstack-meeting-409:45
*** dims has joined #openstack-meeting-409:49
*** bobmel has joined #openstack-meeting-409:54
*** salv-orl_ has joined #openstack-meeting-409:56
*** matrohon has quit IRC09:57
*** numans has joined #openstack-meeting-409:59
*** salv-orlando has quit IRC10:00
*** salv-orl_ has quit IRC10:04
*** salv-orl_ has joined #openstack-meeting-410:05
*** salv-orl_ has quit IRC10:10
*** salv-orlando has joined #openstack-meeting-410:11
*** salv-orl_ has joined #openstack-meeting-410:13
*** salv-orlando has quit IRC10:16
*** asselin_ has quit IRC10:20
*** salv-orlando has joined #openstack-meeting-410:25
*** salv-orl_ has quit IRC10:26
*** lazy_prince has quit IRC10:29
*** GB21 has quit IRC10:31
*** irenab has quit IRC10:41
*** irenab has joined #openstack-meeting-410:42
*** salv-orl_ has joined #openstack-meeting-410:48
*** ashtokolov has quit IRC10:48
*** salv-orlando has quit IRC10:51
*** salv-orl_ has quit IRC10:51
*** salv-orlando has joined #openstack-meeting-410:52
*** markvoelker has joined #openstack-meeting-410:59
*** markvoelker has quit IRC11:04
*** Guest40789 has quit IRC11:20
*** salv-orl_ has joined #openstack-meeting-411:21
*** salv-orl_ has quit IRC11:24
*** salv-orl_ has joined #openstack-meeting-411:24
*** salv-orlando has quit IRC11:25
*** lexholden has joined #openstack-meeting-411:27
*** irenab has quit IRC11:30
*** irenab has joined #openstack-meeting-411:32
*** salv-orl_ has quit IRC11:34
*** sambetts has quit IRC11:35
*** salv-orlando has joined #openstack-meeting-411:35
*** sambetts has joined #openstack-meeting-411:35
*** lexholden has quit IRC11:42
*** xingchao has quit IRC11:43
*** xingchao has joined #openstack-meeting-411:50
*** markvoelker has joined #openstack-meeting-411:55
*** rfolco has joined #openstack-meeting-411:56
*** klamath has joined #openstack-meeting-411:56
*** xingchao has quit IRC11:56
*** klamath has quit IRC11:57
*** klamath has joined #openstack-meeting-411:57
*** xingchao has joined #openstack-meeting-412:02
*** delattec has joined #openstack-meeting-412:02
*** banix has joined #openstack-meeting-412:03
*** jckasper has quit IRC12:08
*** tfukushima has quit IRC12:09
*** tfukushima has joined #openstack-meeting-412:12
*** Brian has joined #openstack-meeting-412:17
*** Brian is now known as Guest6302812:17
*** lexholden has joined #openstack-meeting-412:21
*** Guest63028 has quit IRC12:21
*** dims has quit IRC12:22
*** salv-orl_ has joined #openstack-meeting-412:23
*** dims has joined #openstack-meeting-412:23
*** salv-orlando has quit IRC12:27
*** salv-orlando has joined #openstack-meeting-412:29
*** xingchao has quit IRC12:30
*** salv-orl_ has quit IRC12:30
*** armax has quit IRC12:33
*** salv-orl_ has joined #openstack-meeting-412:36
*** salv-orlando has quit IRC12:36
*** sballe has joined #openstack-meeting-412:43
*** jpekkari has quit IRC12:48
*** woodard has joined #openstack-meeting-412:48
*** dashakhray has joined #openstack-meeting-412:48
*** dashakhray is now known as dshakhray12:49
*** woodard has quit IRC12:49
*** woodard has joined #openstack-meeting-412:50
*** mohankumar_ has quit IRC12:53
*** jpekkari has joined #openstack-meeting-412:55
*** yamamoto has quit IRC12:56
*** puranamr has joined #openstack-meeting-412:57
*** jpekkari has quit IRC12:59
*** jckasper has joined #openstack-meeting-413:01
*** armax has joined #openstack-meeting-413:02
*** armax has quit IRC13:04
*** lazy_prince has joined #openstack-meeting-413:08
*** armax has joined #openstack-meeting-413:08
*** abhishekk has joined #openstack-meeting-413:10
*** baoli has joined #openstack-meeting-413:10
*** pmesserli has joined #openstack-meeting-413:13
*** puranamr has quit IRC13:15
*** baoli_ has joined #openstack-meeting-413:16
*** puranamr has joined #openstack-meeting-413:16
*** Brian has joined #openstack-meeting-413:18
*** Brian is now known as Guest2709913:19
*** baoli has quit IRC13:19
*** bknudson has joined #openstack-meeting-413:19
*** Guest27099 has quit IRC13:22
*** VW_ has joined #openstack-meeting-413:28
*** chenshuai has quit IRC13:30
*** jecarey has joined #openstack-meeting-413:33
*** kairat has joined #openstack-meeting-413:45
*** puranamr has quit IRC13:48
*** ajayaa has quit IRC13:51
*** Piet has quit IRC13:52
*** xingchao has joined #openstack-meeting-413:53
*** bunting has joined #openstack-meeting-413:58
*** TravT has joined #openstack-meeting-413:58
*** bpoulos has joined #openstack-meeting-413:59
*** dannywilson has joined #openstack-meeting-413:59
*** harshs has joined #openstack-meeting-414:00
nikhil_k_Courtesy meeting reminder: ativelkov, cpallares, 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, dshakhray14:00
nikhil_k_#startmeeting glance14:00
openstackMeeting started Thu Sep 10 14:00:38 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k_. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
nikhil_k_#topic agenda14:00
*** openstack changes topic to "agenda (Meeting topic: glance)"14:00
nikhil_k_Welcome all14:00
*** mclaren has joined #openstack-meeting-414:00
nikhil_k_Let's get started14:02
nikhil_k_#topic Updates14:02
*** openstack changes topic to "Updates (Meeting topic: glance)"14:02
nikhil_k_#info artifacts updates14:02
mfedosinhi! just a couple of things14:03
*** cloudtrainme has joined #openstack-meeting-414:03
mfedosinas you may know we have successfully ported artifacts in murano client14:03
*** sigmavirus24_awa is now known as sigmavirus2414:03
*** wokuma has joined #openstack-meeting-414:03
mfedosinand everything works fine there14:03
flaper87mfedosin: awesome!14:03
mfedosinbut also we have many commits on review14:03
mfedosinand and their number is increasing14:04
mfedosinI haven't reviewed all of them, neither did Alex14:05
sigmavirus24mfedosin: sounds like Fast Track isn't so fast eh?14:05
mfedosinbut we have several critical there14:05
mfedosinsigmavirus24, kind of :)14:05
nikhil_k_that looks like a good compilation14:05
nikhil_k_mfedosin: so, we need to wait on config changes, api changes and other important stuff until after RC is cut (just fyi)14:06
nikhil_k_RC period is intensive testing and bug fixing14:06
mfedosinI will prepare a list of changes that we need asap14:06
*** stanchan has joined #openstack-meeting-414:06
nikhil_k_we wouldn't want other stuff blocking and interfering with it14:06
mfedosinif it's possible they have to be merged this week14:06
nikhil_k_mfedosin: a sub-heading in that etherpad should help with critical fixes14:06
mfedosinother commit may wait14:06
jokke_mfedosin: bugfixes?14:06
*** stanchan_ has quit IRC14:07
mfedosinjokke_, yep, some of them with security issues14:07
mfedosin*other commits14:07
flaper87mfedosin: pls, don't disclose the security fixes here (just a friendly reminder)14:08
*** rbak has joined #openstack-meeting-414:08
* flaper87 has seen that in the past (not from mfedosin, though)14:08
mfedosinit's an experimental api14:08
* flaper87 is paranoid14:08
mfedosinno one cares about it :)14:08
jokke_mfedosin: feel free to ping me as well if you get some things popping up. I have not focused that closely t oartifacts as we have had our own client crisis ongoing14:09
mfedosinthat's why we disabled v3 by default14:09
nikhil_k_let's not discuss anything about security issues here14:09
mfedosinjokke_, cool, thanks!14:09
mfedosinnikhil_k_, lol, okay14:09
nikhil_k_thank you.14:10
nikhil_k_#info drivers updates14:10
nikhil_k_So, we had a small meeting this tuesday14:10
sigmavirus24flaper87: what do you mean we shouldn't discuss security problems in public logged channels? Isn't that standard operating procedure for this project?14:10
*** wokuma1 has joined #openstack-meeting-414:10
*** wokuma has quit IRC14:10
flaper87sigmavirus24: I'll open a security bug to track that and we can talk about it in our next meeting14:10
*** mhayden has left #openstack-meeting-414:11
jokke_sigmavirus24: I din't care what your "tenant" does but here in OpenStack we prefer not to do that :P14:11
jokke_don't even14:11
mfedosineven the bug is not declared as private, I think we can discuss it here14:11
flaper87mfedosin: ah, :(14:11
rosmaitaspeaking of security issues, i want to nominate hemanthm_ for the glance security team14:11
flaper87anyway, lets stay on topic (drivers updates)14:12
flaper87I know FFE was granted for the OVF work14:12
openstackLaunchpad bug 1489902 in Glance "Artifacts: public artifact may be modified by any user" [Undecided,In progress] - Assigned to Alexander Tivelkov (ativelkov)14:12
nikhil_k_so, we asked for some action items from the ova-lite tem and they have the updated spec. FFE was granted after that.14:12
*** aswadr has joined #openstack-meeting-414:13
flaper87nikhil_k_: I've been keeping an eye on the code, I just did a quick review14:13
flaper87and I'll keep doing so14:13
nikhil_k_So, now the follow up on that should be a update twice a week till 25th on the status of the spec changes14:13
flaper87we should keep track of the progress and be ready to take a step back if we're getting too close to RC1 and the patch is not ready14:13
nikhil_k_they have agreed to work with flaper87 and sabari14:13
nikhil_k_so, thanks flaper87 !14:13
*** carl_baldwin has joined #openstack-meeting-414:14
*** dannywilson has quit IRC14:14
flaper87I don't think we'll have to do that but...14:14
nikhil_k_flaper87: agreed14:14
nikhil_k_on both fronts14:14
nikhil_k_we also discussed a bit on lite-specs and some process changes for mitaka. the plan is to discuss them after RC period14:14
mclarensounds good14:15
nikhil_k_however, I have a few request on the FFE possibly using the lite-specs concept14:15
nikhil_k_so, we can discuss the possiblity of the same in the open discussion14:15
nikhil_k_moving on to next topic14:15
nikhil_k_#topic py-client 1.x.x back-compat like changes14:16
*** openstack changes topic to "py-client 1.x.x back-compat like changes (Meeting topic: glance)"14:16
*** ivar-lazzaro has joined #openstack-meeting-414:16
nikhil_k_here's the email to openstack-operators list14:16
nikhil_k_there are some replies that have +1 on having back-compat14:16
nikhil_k_so, my duckduckgo did not get me a link to the thread14:17
nikhil_k_however, the subject is14:17
nikhil_k_[Openstack-operators] Adding v1 LIKE support to python-glanceclient releases 1.x.x14:17
buntingThis is we should aim to be backwards-compatable as possible, because this is exactly what our users want to see14:18
mfedosinis it for cli only?14:19
sigmavirus24mfedosin: I'd hope so14:19
nikhil_k_so, I am inclining towards having those changes. However, the catch there is14:19
mclaren(thanks for reaching out nikhil_k_)14:20
*** Brian has joined #openstack-meeting-414:20
nikhil_k_shell api is supposed to be stable api14:20
*** Brian is now known as Guest2375614:20
jokke_nikhil_k_: you mean CLI?14:20
nikhil_k_so what we have in 1.x.x is likely going to stay for say 5 years (if not more). but that's just an estimate14:20
nikhil_k_mclaren: np14:20
*** nhairston has joined #openstack-meeting-414:21
flaper87IMHO, the CLI api should be intuitive enough and it does not need to match 1:1 the server API14:21
nikhil_k_yep, I am trying to prefix the word "API" with specifics  to be explicit and more clear. essentially CLI14:21
flaper87The difference between adding all this backwards compat changes now rather than later is that once we added them, we can't just take them back14:21
buntingWhy would we want to ever take them back?14:22
nikhil_k_I think the concern is to add them prior to stable cut14:22
flaper87bunting: because we're humans and we make mistakes and what we think makes sense now might be a pain to maintain later14:22
jokke_ok so we have client API and we have client CLI14:22
flaper87Not all "compatible band aids" are good14:22
*** vishwanathj has joined #openstack-meeting-414:23
nikhil_k_jokke_: well elaborated14:23
flaper87I'm not saying we shouldn't add them at all. I'm just asking to not rush this14:23
jokke_as in Abbreviation of Program Interface and CommandLine Interface ;)14:23
mfedosinby the way, what do you think about openstack-client?14:23
mclarenif we don't add them before we cut stable, their usefulness is somewhat diminished14:23
flaper87jokke_: yup, that's always been the case. That's one of the reasons why I like openstackclient, it just takes the CLI out of the *library*14:23
nikhil_k_bunting: yes, so that's a good pointer. is there a way you can use py-openstackclient instead ?14:24
flaper87and helps people to reason about libraries for what they are14:24
jokke_well my point is if we talk about cli lets keep the talk in cli not cli api or shell api etc. it's not api it's cli14:24
*** Guest23756 has quit IRC14:24
*** vishwanathj has quit IRC14:24
jokke_at least I get hwell of mixed up no matter how hard I try to follow14:24
jokke_So I'd like to remind couple of things here what I keep hearing over and over14:25
*** Piet has joined #openstack-meeting-414:25
*** degorenko has quit IRC14:26
jokke_we as in community want to have Glance Images API v2 stabilized and consumed and v1 deprecated14:26
nikhil_k_bunting: so the response from Clayton O'Neill in the ethedpad suggested that py-os client was a possibility14:26
nikhil_k_mclaren: ^14:26
jokke_this is not just day dream of glance to get rid of that burden but OpenStack community widely14:26
mclarenjokke_: so you don't think backwards compatability is important in this case?14:27
*** vikram has joined #openstack-meeting-414:27
*** kairat has quit IRC14:27
flaper87I don't think anyone is advocating for not being compatible14:27
jokke_that in mind I don't think we should implement certain inconsistencies to our v2 specially that --is-public is we will be stuck with it14:27
flaper87I think the discussion here goes around: 1) 1.0 being a major release 2) Being pragmatic 3) Trying to fix some of our g'old mistakes14:27
jokke_if we will be stuck with it even14:28
*** harshs_ has joined #openstack-meeting-414:28
*** harshs has quit IRC14:28
*** harshs_ is now known as harshs14:28
jokke_I think it's way more important to consider long term impact at this point vs. short term inconveniences14:28
nikhil_k_so, here's the alternative14:29
mclarenSo, I spoke with Duncan Thomas (who works for HP and is a long standing cinder core). I asked specifically what Cinder would do in the case of is-public. they would maintain backwards compatability -- like our users are asking for14:29
nikhil_k_what if we release 0.19.x based on commit prior to default being v214:29
nikhil_k_and cut stable out of it14:29
nikhil_k_fix bugs there14:29
jokke_and if we need to maintain all that compatibility layer for years and keep having binary command line options for non binary values just because we decided once in 2015 to help out few script writers who did not read release notes of major release, I do not think that's sustainablwe14:30
mclarenjokke_: let's talk offline14:30
flaper87nikhil_k_: I don't think that'll take us anywhere in our hope to migrate to v214:31
nikhil_k_flaper87: why so?14:31
nikhil_k_I mean, is client version the only blocker and is that the most important blocker?14:31
flaper87Because switching the default is also to raise awarness that there's a v2 API that is the currently maintained one14:31
flaper87it's not to just release the major14:32
nikhil_k_I doubt if it's a good programmatic way of conveying that message14:32
nikhil_k_the supportability status is the source of truth14:32
jokke_the major version bump was consequence, not the goal14:32
buntingI think it comes down to do operators particually care about what version they are runnin or that it just works?14:32
nikhil_k_I think both, depending on who your users are14:33
mclarenOperators actually want to spend as little time as possible thinking about OpenStack. Ideally it should 'just work'.14:34
nikhil_k_if it's just the dashboard your user then no, it can be internal team with good awareness on what's happening with your versioning14:34
flaper87I'd keep the things the way they are going, discuss each patch specifically and then do minor client releases if any of those patches land14:34
nikhil_k_mclaren: I agree that those are majority ones14:34
flaper87mclaren: I agree w/ that, FWIW14:34
nikhil_k_but not necessarily all14:34
mclarenOk, so what are folks thoughts on Niall's patch overall?14:35
* mclaren looks for link14:35
*** jruano_ has joined #openstack-meeting-414:35
*** lazy_prince has quit IRC14:36
*** lazy_prince has joined #openstack-meeting-414:36
flaper87I think we'll have to evaluate each of those additions separatedly14:36
nikhil_k_so flaper87 besides the awareness of versioning, do we have any other blockers for cutting 0.19.1,2 stable/ ?14:36
nikhil_k_jokke_: mclaren bunting ^14:37
nikhil_k_I think we can do is establish that awareness period for stable/mitaka to not have such back compat changes14:38
jokke_I was in general pro it until I heard that every single one of those we merge we're stuck with, as it was supposed to be migration path, not granted functionality maintained until non-foreseeable future14:38
mfedosinfolks, one question about list validation14:38
flaper87nikhil_k_: I don't think that will solve this issue/discussion but postpone it until mitaka14:38
mfedosinwe have disabled it, afair14:38
nikhil_k_looks like the tradeoff is small, maintain something for 1 cycle vs maintain back-compat for 10 years14:38
jokke_nikhil_k_: I don't think that either14:38
flaper87but I might be missing one piece14:39
flaper87not sure :D14:39
mfedosinso, there is a patch to enable validation for list
nikhil_k_flaper87: jokke_ : you guys think, we will need to keep back compat in 1.x.x even in that case! ?14:39
jokke_nikhil_k_: I don't see how we would get around that14:39
flaper87we already released it14:40
flaper87I need some extra time to think about this, TBH14:40
nikhil_k_why can't we give 1 cycle time to scripter to change scripts, send email to ML14:40
flaper87I think I was not around when this was first proposed14:40
flaper87(cutting stable from 0.1914:40
nikhil_k_ok, I need to know more from all the concerned individuals why so14:40
nikhil_k_flaper87: it was , just a few mins ago14:40
nikhil_k_ok, let's give some time to other topic14:41
flaper87nikhil_k_: please, thanks. I'll put thoughts around this14:41
nikhil_k_#topic     FFE ?14:41
*** openstack changes topic to "FFE ? (Meeting topic: glance)"14:41
nikhil_k_mclaren: you ?14:41
mclarenthat's me!14:41
mclarenSo, I'm wondering what the chances of landing this is?14:41
jokke_nikhil_k_: so has defcore told you that we need to stick and support our stable/liberty for ever or we need to support what ever functionality we are releasing in our client?14:42
mclarenIf it was just glance_store it might be, but I'd need a global requirements bump on swiftclient to 2.6.014:42
mclarenis it worth proposing the swiftclient change?14:42
nikhil_k_jokke_: we need to tell defcore, but we can talk more on that offline14:42
flaper87mclaren: I think reqs freeze was a while back14:43
flaper87if you need to bump it, it'll be really hard14:43
mclarenyeah, kinda guessed as much14:43
flaper87probably worth waiting till mitaka in that case14:43
*** salv-orl_ has quit IRC14:43
*** yamamoto has joined #openstack-meeting-414:43
*** salv-orlando has joined #openstack-meeting-414:43
*** salv-orlando has quit IRC14:44
nikhil_k_yeah, I can't find a way around this for Liberty14:44
mclarensure. had to ask!14:44
*** salv-orlando has joined #openstack-meeting-414:44
nikhil_k_#topic Reviews, Bugs and Releases14:45
flaper87mclaren: sorry :(14:45
*** openstack changes topic to "Reviews, Bugs and Releases (Meeting topic: glance)"14:45
nikhil_k_we already discussed client release14:45
nikhil_k_#info glance-store 0.9.1 released14:45
nikhil_k_who proposed that?14:45
flaper87nikhil_k_: Matt, I believe.14:45
flaper870.9.0 broke the gate14:46
flaper87and .1 has the fix14:46
jokke_Matt Riedemann14:46
flaper87jokke_: thanks, I had forgotten his lastname14:46
jokke_yes it broke rdb gate so matt fixed it and requested release ...14:46
*** zeih has quit IRC14:47
*** geoffarnoldX is now known as geoffarnold14:48
nikhil_k_there's a email to openstack-announce on the release 0.9.1 that I can't find in this hurry14:48
nikhil_k_anyways, moving on if nothing more here14:48
wokuma1Just wanted to remind cores to review for Liberty...thanks mclaren for reviewing...14:48
wokuma1It's been listed here as critical:
flaper87#link (glance_store 0.9.1)14:49
nikhil_k_haha, awesome flaper8714:49
flaper87nikhil_k_: :D14:49
nikhil_k_wokuma1: yeah, I think we need that in before rc114:50
flaper87wokuma1: I'll review14:50
wokuma1nikhil_k: agree14:50
nikhil_k_hopefully there's no migration for artifacts in the pipe currently, mfedosin ?14:50
wokuma1flaper87: thans14:50
mfedosinbut they will be in Mitaka14:51
openstackLaunchpad bug 1493859 in python-glanceclient "The glance client should not raise HTTP errors" [Undecided,Opinion] - Assigned to Niall Bunting (niall-bunting)14:51
buntingI discovered that the client raises http errors14:51
nikhil_k_I think this fix makes sense14:52
nikhil_k_bug is in opinion14:52
*** mmedvede has joined #openstack-meeting-414:52
* flaper87 clicks14:52
buntingI was just wondering what people thought about removing this14:52
buntingas it seems confusing to me14:52
nikhil_k_bunting: you should check nova/cinder about this atleast14:52
*** degorenko has joined #openstack-meeting-414:53
*** kairat has joined #openstack-meeting-414:53
nikhil_k_may be even horizon, ironic14:53
flaper87I'll review that too. I agree w/ jokke_ that we need to be careful becasue we may break the library14:53
nikhil_k_nova used locations in few places14:53
flaper87nikhil_k_: it still does14:54
nikhil_k_if they are expecting exc.HTTPNotFound('Unknown URL(s): %s' % list(missing_locs))14:54
nikhil_k_oops, I meant _uses_14:54
jokke_yes my problem is that this change _is_ actually breaking backwards compatibility, while being sensible idea but by the looks of it, the way those are done looks very intentional mocking HTTL responses ... anyone remembers long enough backwards for reasoning for those?14:54
flaper87nikhil_k_: gotcha14:54
nikhil_k_good catch, thanks14:54
nikhil_k_jokke_: we will have to discover14:55
flaper87nikhil_k_: ++14:55
flaper87further tests and reviews are needed14:55
flaper87other than that, it seems sensible14:55
nikhil_k_last one on the agenda, a very late addition so will go in open discussion14:55
nikhil_k_#topic open discussion14:55
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:55
nikhil_k_hemanthm_: ^14:56
hemanthm_I wanted to see if there a way of getting this into L.14:56
hemanthm_At a point we were waiting for lite-specs and now it looks like it won't happen in L.14:56
jcookit's a borderline bug / feature14:57
hemanthm_jcook ^14:57
mclarenhmm 'So,14:57
mclarenthis change also monkey patches essential python modules.'14:57
hemanthm_mclaren: that's more a bug fix.14:57
hemanthm_those modules should have been monkeypatched any way14:58
jcookin the scrubber, which is a tiny code base14:58
nikhil_k_yeah, but they are in scrubber. I think api does this already14:58
jcookand which cause incorrecet behavior14:58
nikhil_k_the worry part for me is the config14:58
jcooktrue, it adds a config14:58
*** lexholden has quit IRC14:58
jcookthat is why I say it's borderline14:58
flaper87If there's a spec for it, I'd be happy to consider a late FFE14:58
nikhil_k_a good lit-spec14:58
jcookwe can create a spec, would it follow same process or would there be deltas with current spec process?14:59
flaper87too bad we don't have lite-specs, I guess a normal spec but short should be enough14:59
hemanthm_flaper87: there isn't one yet. But, I can write one soon14:59
nikhil_k_yeah, if people wanna do ffe consideration rather than lite-spec, that works for me14:59
flaper87I'd be ok w/ a FFE for this14:59
jcookwe can absolutely do that14:59
mclarenI'd probably lean slightly against, but if others disagree that's ok14:59
flaper87I agree it's borderline and it doesn't break the current behavior14:59
nikhil_k_jcook: let's discuss detils offline15:00
jcooksounds good15:00
nikhil_k_thanks all, we are out of time15:00
jokke_around the FFE ... I'd really like to hear positive statement from doc folks before giving my +115:00
*** Shamail has joined #openstack-meeting-415:00
jcookjokke_: we can reach out15:00
*** openstack changes topic to "OpenStack Meetings ||"15:00
openstackMeeting ended Thu Sep 10 15:00:40 2015 UTC.  Information about MeetBot at . (v 0.1.4)15:00
openstackMinutes (text):
flaper87jcook: ++15:00
*** abhishekk has quit IRC15:00
jcookmclaren: curious of your concerns, don't see you in #openstack-glance atm15:01
*** dwalleck has joined #openstack-meeting-415:01
jcookI'll be there15:01
*** sjmc7 has joined #openstack-meeting-415:01
TravT#startmeeting openstack search15:01
openstackMeeting started Thu Sep 10 15:01:34 2015 UTC and is due to finish in 60 minutes.  The chair is TravT. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: openstack search)"15:01
openstackThe meeting name has been set to 'openstack_search'15:01
sjmc7that's starting to look creepy15:02
TravTthe agenda or the o/15:02
TravTplz add anything to it.15:02
TravT#topic general status updates15:03
*** vishwanathj has joined #openstack-meeting-415:03
*** openstack changes topic to "general status updates (Meeting topic: openstack search)"15:03
TravTthanks for some productivity yesterday at the review hour.15:03
TravTi know not everybody could  make it15:03
*** blahRus has joined #openstack-meeting-415:03
TravTbut we actually did get 5 patches in yesterday15:03
TravTi don't have any other general updates. so...15:04
TravT#topic Release15:04
*** openstack changes topic to "Release (Meeting topic: openstack search)"15:04
TravTbeen looking at this:15:05
TravTI think that's similar to what we want to do, but I saw in the release tools repo there are some new scripts15:05
*** chenshuai has joined #openstack-meeting-415:06
*** jruano_ has quit IRC15:06
*** mclaren has quit IRC15:06
sjmc7probably nikhil and david have the most experience with the release tooling15:06
TravTI was planning to reach out to rel management team next week15:06
*** bunting has quit IRC15:06
TravTto see if we need to run it ourselves or not15:06
nikhil_k_+1 to that15:07
TravTdavid-lyle: nikhil_k_: they pretty much do it for horizon and glance, right?15:07
nikhil_k_if we import os libraries we should run by them15:07
TravTbeing part of the integrated release.15:07
david-lyleTravT: yes15:07
nikhil_k_sjmc7: the most I've used it the gerrit review system with SHA to tag stuff15:08
nikhil_k_TravT: we would need to define requirements similar to global caps. not sure if we have a patch that does it now15:08
TravTone thing we'll have to figure out, which maybe nikhil_k_ and david-lyle would know is if we need to reset the milestone target on all our bugs and BPs15:09
*** kairat has left #openstack-meeting-415:09
david-lyleautomated if through relmgr15:09
david-lylethey have scripts15:09
*** irenab has quit IRC15:09
TravTright now, i've been keeping them up with when they would have released had we done milestone releases15:09
david-lyleI think even if you do the release, you would use the same scripts and tooling15:09
*** jwagner_away is now known as jwagner15:10
TravTok.  well, i'll reach out to the release management team next week to start prep work.15:10
TravTalso, as we discussed awhile back, i'll set up a seccore team15:11
TravTit will be a subset of the core team.15:11
*** dwalleck has quit IRC15:11
nikhil_k_I think so too. or thierry can run the script (with admin rights or whatever) to fix the bug statuses15:11
TravTok, good to know15:12
TravTso, if you get an invite to join the seccore team, please accept it if you can.15:12
TravTif you specifically have an interest of being on it, let me know.15:12
TravTso, lets talk about current BP statuses a bit.15:14
*** Shamail has quit IRC15:14
TravTlakshmiS how are functional tests coming?  still looking to be good for liberty release?15:14
lakshmiSyes i removed WIP status15:14
lakshmiSready for reviews15:15
*** salv-orlando has quit IRC15:15
TravTok.  i filed a bug yesterday that I didn't put up a patch on.15:15
TravTbut i think it'll affect functional tests15:15
lakshmiSwe can always add more but i guess there's enough of them now15:15
TravTare you testing for "Fields" now?15:15
lakshmiSapi, load and listener core functionality is tested15:15
sjmc7lakshmiS, i'll revierw that again today15:16
lakshmiSFields in ES response?15:16
*** ajmiller_ has joined #openstack-meeting-415:16
TravTas input.15:16
openstackLaunchpad bug 1493586 in OpenStack Search (Searchlight) "Missing _source parameter" [Undecided,New]15:16
TravTi have no idea why we are remapping fields to _source15:16
TravTbut we shouldn't IMO.15:16
*** Shamail has joined #openstack-meeting-415:17
TravTyou can send in fields parameter to searchlight15:17
sjmc7if you specify 'fields' e-s won't return the _source doc15:17
TravTbut it is actually _source15:17
TravTbut there is a fields parameter for ES15:17
TravTthat is different15:17
sjmc7err... um.15:17
TravTconfused the heck out of me yesterday15:17
sjmc7me too :) i'll have a look if i get time later15:17
TravTor a day ago...15:17
lakshmiSwe do get _source15:17
*** jckasper has quit IRC15:18
TravTwell, possibly i was doing something wrong.  it was nearly midnight15:18
TravTbut i'm pretty sure we pop fields from the request and send it in as _source15:18
TravTanyway, lakshmiS, that's great about the functional tests15:19
TravTI'll try to give them a go.15:19
TravTnext bp is designate.15:20
TravTekarlso has been really working through that with sjmc7 and i15:20
TravTseems that it is very close15:20
TravTi asked to put in parent child relationship for some of the data mapping, which has caused a little churn on it15:21
TravTbut i think designate will be in for release.15:21
*** dwalleck has joined #openstack-meeting-415:21
*** numans has quit IRC15:21
TravTbp glance-metadef-plugin15:22
*** tfukushima has quit IRC15:22
TravTlakshmiS found one bug in that15:22
*** dannywilson has joined #openstack-meeting-415:22
TravTand has a fix up15:22
TravTi also have been experiencing some pain with metadefs on some horizon work i'm doing15:22
*** dwalleck has quit IRC15:22
sjmc7*hangs head*15:23
TravTbut haven't debugged that yet.15:23
TravTnikhil_k_: that's yours ^15:23
nikhil_k_TravT: I doubt if I can complete them in next 2 weeks. THings have been sitting for a while as Glance was heavy past few weeks15:24
TravTwell, i don't think it is a release blocker.15:24
nikhil_k_But if we really need them, I can try to define some scenarios that we can try to get in for L15:24
nikhil_k_sure, we can chat offline when you have a better picture of all other features15:25
sjmc7i think it's fine after L. it's to feed into fixing things15:25
TravTsounds good... i think perf testing will be a big topic in a lot of areas...15:25
nikhil_k_yeah, possibly cross project interaction and some types queries15:25
sjmc7yeah. it would be good to do before the summit tho15:25
TravTi'm actually a bit more worried about indexing perf than query perf15:25
sjmc7me too15:26
nikhil_k_I see15:26
TravTI agree that perf scenarios and testing should be really tackled in M.15:27
TravTso nikhil_k_, i'll defer that BP to next15:27
TravTnext up, of interest to you david-lyle15:28
TravThorizon integration.15:28
*** Shamail has quit IRC15:28
TravTwe won't have an in horizon trunk integration for liberty, but...15:28
*** Shamail has joined #openstack-meeting-415:28
TravTi have a search panel for horizon that's coming along okay.15:29
*** Shamail has left #openstack-meeting-415:29
TravTit won't be perfect, but i've been thinking about what to do with it.15:29
TravTi was thinking about a few options15:29
TravT1) holding off and proposing to mitaka horizon trunk15:30
TravT2) putting it into contrib on searchlight repo15:30
TravT3) creating a new repo15:30
*** evgenyf has quit IRC15:30
TravTbut we need something to actually show searchlight capabilities in liberty15:31
sjmc7we've also been fiddling with a single search box type thing15:31
TravTyes, i gave a thumbs up to the invision mocks on that15:31
TravTwent back and forth a bit15:31
TravTbut the search panel actually brings some qualities that the top nav search doesn't have.15:32
TravTand can be plugged in.15:32
TravTi have a fear that it'll be the end of mitaka before we can get the top nav figured out in horizon proper.15:32
*** jwagner is now known as jwagner_away15:33
*** stanchan_ has joined #openstack-meeting-415:33
TravTdavid-lyle must be asleep15:33
david-lyledoh, too many streams15:33
TravTbasically i'm asking what I should do with a proof of concept horizon search panel plugin for liberty searchlight15:34
*** stanchan has quit IRC15:35
david-lyleeasiest if probably a different github repo for now or a feature branch, that way you could continue to iterate up to the summit15:35
david-lyleand then merge into master when baked15:35
david-lyleotherwise the patch approval process will slow you down, I fear15:35
TravTyeah, last week I came to the realization that we had to do something like this15:36
david-lyleI think it's valid to demo a POC that is targeted to merging15:37
*** lazy_prince has quit IRC15:37
*** stanchan_ has quit IRC15:37
TravTwell, perhaps I just should keep it as one massive patch and propose to horizon.15:37
david-lylecould do that as well15:37
TravTit subsumes the searchlight api patch steve already had up.15:37
*** vikram has quit IRC15:38
TravTok, that is pretty easy...15:38
*** tfukushima has joined #openstack-meeting-415:38
TravTi'll start with that.15:38
david-lylenever enough runway ;)15:39
TravTwill be nice to get the code (as ugly as it is at the moment up into a system off mine).15:39
*** chenshuai has quit IRC15:39
TravTokay.  next BP: plugin-config-options15:39
TravTekarlso and sjmc7 were debating starting that yesterday15:40
TravTi think ekarlso said he'd put up a patch15:40
sjmc7i'm pretty keen to sort out the config stuff before L15:40
TravTprobably based off what they have in designate15:40
TravTme too sjmc715:40
sjmc7it's going to be a problem for actual deployments15:40
sjmc7which will no doubt fall into my lap :)15:40
TravTi look forward to much cursing from you15:41
sjmc7an advantage of being english15:41
TravTok, so let's keep that BP for liberty15:41
TravTbp enable-cors15:41
TravTi'm still very much interested in this, but it still isn't a must15:41
TravTat least for horizon use cases15:42
TravTsince we proxy through horizon atm.15:42
david-lyleseems like a nice Mitaka item15:42
TravTyeah, most likely.15:42
*** harshs has quit IRC15:43
TravT#topic bugs15:43
*** openstack changes topic to "bugs (Meeting topic: openstack search)"15:43
TravTso far we've done a good job staying on top of them.15:43
TravTbut there are a few opportunities out there.15:43
TravTdoes anybody have any they'd like to discuss?15:44
lakshmiSso what are we deciding on  modified fields for glance client 1.0.015:44
openstackLaunchpad bug 1490697 in OpenStack Search (Searchlight) "python glance-client for image-members has upgraded" [High,In progress] - Assigned to Lakshmi N Sampath (lakshmi-sampath)15:44
lakshmiSfunctional tests depend on this bug15:44
TravTnikhil_k_: sigmavirus24: rosmaita: ^15:45
sjmc7ah, yeah. so what was the deal - use glance-client 1.0.0 or no?15:45
sjmc7what's global-requirements doing?15:45
*** erikwilson has joined #openstack-meeting-415:45
sjmc7python-glanceclient>=0.18.0 is in global-reqs on master15:45
sjmc7no upper cap15:45
*** VanL has joined #openstack-meeting-415:45
*** SimonChung1 has quit IRC15:46
lakshmiSthat leaves it open :)15:46
TravTnikhil_k_: if you look at comments on bottom of that patch15:46
sjmc7does horizon show image members?15:46
*** degorenko has quit IRC15:46
*** dwalleck has joined #openstack-meeting-415:47
TravTwe just aren't sure if we should put a hard requirement on glance client 1.0 on searchlight15:47
david-lyleI don't believe so15:47
TravTor if we need some conditional code15:47
lakshmiSnot sure how other projects deal with backward incompatible code on python clients15:48
*** zeih has joined #openstack-meeting-415:48
sjmc7if there's no global-reqs cap, everyone will get 1.0.015:48
TravThorizon does not explicitly show image members or even allow updating them.15:48
TravTbut it does do filtering based on image members15:48
sjmc7we could put a hack in though; look for both attributes15:48
TravTbut i believe it is implicit15:48
nikhil_k_lakshmiS: TravT currently, jokke_ and I are having that conversation on how to deal with the situation15:48
*** bobmel_ has joined #openstack-meeting-415:49
TravTif not owned by me and is not public, then must be shared with me.15:49
sjmc7worst case, we do the conversion - look for member_id and turn it into member. or vice versa15:50
lakshmiShack would be easy if we dont have a clear solution15:50
sjmc7it's not really a hack per se15:51
TravTnikhil_k, can you give a two sentence summary15:51
sjmc7i'm ok with doing it15:51
TravTlakshmiS: i more okay with that than only working with glanceclient 1.015:51
*** bobmel has quit IRC15:51
nikhil_k_TravT: we are currently deciding if the CLI should support back-compact changes for v1 API15:52
lakshmiSi will meanwhile update the  patch with the hack15:52
TravTi also have terrible grammar in irc15:52
*** b3rnard0 has joined #openstack-meeting-415:52
lakshmiSnikhil_k: if you are going to take a decision please update the patch. I will wait until monday15:52
sjmc7let's put the conditional in15:52
sjmc7or that :)15:52
nikhil_k_TravT: sorry, that's just one line and that's it15:53
nikhil_k_lakshmiS: sure15:53
*** zeih has quit IRC15:53
TravTtbh, i'd just put in the conditional15:53
*** jwagner_away is now known as jwagner15:53
lakshmiSTravT: sure15:54
*** rromans has joined #openstack-meeting-415:54
TravTok, cool15:54
*** nhairston1 has joined #openstack-meeting-415:54
TravTlakshmiS: i saw you also updated the member notification patch based on feedback from nikhil_k_15:54
TravTis it ready for him and other glance guys to review?15:55
lakshmiSyes I did fix some of the test cases.15:55
lakshmiSthere are still 2 tests failing on glance store which i am looking currently (need to understand that part of code which is new to me)15:55
nikhil_k_thanks, if you have a link it would help a ton! (got around 100 FF tabs open atm)15:55
*** vivek-ebay has joined #openstack-meeting-415:55
*** nhairston has quit IRC15:56
*** evrardjp has joined #openstack-meeting-415:56
*** prometheanfire has joined #openstack-meeting-415:57
TravTok, just a couple minutes left15:57
*** hughhalf has quit IRC15:57
TravTif i send out another "review hour" request for next week tuesday or wednesday, would that be helpful?15:57
*** hughhalf has joined #openstack-meeting-415:58
TravTpreference in days?15:58
lakshmiSany day is fine with me15:59
*** stevelle has joined #openstack-meeting-415:59
TravTok, my coffee IV line needs to be changed and we are out of time anyway.15:59
TravTthanks everybody!15:59
sjmc7aye. thanks15:59
*** sjmc7 has left #openstack-meeting-416:00
*** openstack changes topic to "OpenStack Meetings ||"16:00
openstackMeeting ended Thu Sep 10 15:59:59 2015 UTC.  Information about MeetBot at . (v 0.1.4)16:00
openstackMinutes (text):
cloudnull#startmeeting OpenStack Ansible Meeting16:00
openstackMeeting started Thu Sep 10 16:00:17 2015 UTC and is due to finish in 60 minutes.  The chair is cloudnull. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: OpenStack Ansible Meeting)"16:00
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:00
*** lakshmiS has left #openstack-meeting-416:00
*** mgariepy has joined #openstack-meeting-416:00
*** Sam-I-Am has joined #openstack-meeting-416:00
*** nhairston has joined #openstack-meeting-416:00
cloudnull#topic rollcall16:00
*** openstack changes topic to "rollcall (Meeting topic: OpenStack Ansible Meeting)"16:00
prometheanfirecloudnull: will be getting food at the start16:01
*** odyssey4me has joined #openstack-meeting-416:03
*** nhairston1 has quit IRC16:03
cloudnullcouple more min to let some folks trickle in16:03
cloudnull#chair openstack16:03
openstackCurrent chairs: cloudnull openstack16:03
cloudnull#chair odyssey4me16:04
openstackCurrent chairs: cloudnull odyssey4me openstack16:04
evrardjpI'm sorry I'm not familiar with english, did you consider odyssey4me as furniture? ;)16:04
cloudnullhe is a fixture :)16:05
cloudnull#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
cloudnullitem: make a BP to track each OS service and remove deprecated variables16:05
*** mhayden has joined #openstack-meeting-416:05
odyssey4meah, my bad - that should have been me and I haven't done it yet16:06
Sam-I-Amcloudnull: does this include new things for liberty too?16:06
odyssey4meadd that as one allocated to me please16:06
Sam-I-Amthere's a lot of those changes16:06
odyssey4meoh yes, I did do a liberty spec :)16:06
*** banix has quit IRC16:06
cloudnullnow we need people to review it16:06
Sam-I-Ami have some neutron changes that someday i'll get time to do16:06
*** VW_ has quit IRC16:07
cloudnullSam-I-Am: If you have the changes outlined can you write them down somewhere so we can get to it if you cant16:07
*** VW_ has joined #openstack-meeting-416:08
cloudnulletherpad, spec review, etc are all perfectly acceptable.16:08
*** dwalleck has quit IRC16:08
odyssey4mebetter yet, comment on the review that you want to be on the neutron work - there's a spot in the work task list16:08
Sam-I-Amalthough i'm waiting on a better way to add configurability16:08
Sam-I-Ami think you had a patch for that16:09
*** degorenko has joined #openstack-meeting-416:09
cloudnullbase your changes off of the change if needed.16:09
odyssey4memy suggestion is that we try and pair up the work, ideally with pairs that are in different time zones to get better coverage and hand over16:09
cloudnullas a reference this is the review for the better config capabilities16:10
*** asselin has joined #openstack-meeting-416:11
*** Bjoern_ has joined #openstack-meeting-416:11
cloudnullcode to make it go and an implementation example ^16:11
*** jwagner is now known as jwagner_away16:11
*** Bjoern_ is now known as BjoernT16:11
cloudnullo/ BjoernT16:11
cloudnullnext: prometheanfire to get involved with the ops meetup ligtning and moderator talks16:11
Sam-I-Amcloudnull: needs more docs :)16:12
prometheanfireI've added myself as a possible moderator and will do at least one lightening talk16:12
*** VW_ has quit IRC16:12
prometheanfiremoderating for infra containers16:12
d34dh0r53o/ sorry I'm late, phonecall16:13
cloudnull#topic Liberty Release Blueprints16:13
*** openstack changes topic to "Liberty Release Blueprints (Meeting topic: OpenStack Ansible Meeting)"16:13
*** Brian has joined #openstack-meeting-416:13
*** Swami has joined #openstack-meeting-416:13
cloudnullfrom a bp prosepctive i think we're good.16:13
*** Brian is now known as Guest7707616:14
cloudnullwe just need reviewers on the implementations of the approved bps16:14
odyssey4meI found myself thinking this morning that perhaps the liberty release should focus primarily on a greenfield deployment, then we work on the upgrade mechanism for a .1 release later16:15
Sam-I-Amliberty release - do the things'16:15
*** jwagner_away is now known as jwagner16:15
cloudnullI'm good with that.16:15
odyssey4meI'm concerned about the code churn in the release prep interfering with the ability to effectively do upgrade testing16:15
palendaeodyssey4me: I think that's going to be the practical thing16:15
palendaeodyssey4me: Right now it's been hard to get people to do even greenfield stuff16:15
odyssey4meI'm also concerned with resourcing16:15
evrardjpI'm not fond of it, because I'll need to upgrade ;)16:16
*** vivek-ebay has quit IRC16:16
evrardjpbut I understand16:16
odyssey4methe .1 release with confirmed upgradability could be released very soon after .0 - but I'd prefer that we have a more focused sprint or two on it16:16
Sam-I-Amturns out... most of the kilo stuff works in liberty plus a few deprecation messages16:17
odyssey4meevrardjp this suggestion is for your protection :) also, we'd like your help with the upgrade testing16:17
Sam-I-Amhowever, liberty wouldnt really be liberty without fixing that stuff16:17
palendaeHelp on testing upgrades would be very, very appreciated16:17
*** Guest77076 has quit IRC16:18
Sam-I-Amone of these days... upgrade gating16:18
*** VanL has quit IRC16:18
odyssey4meone other thing I think we should discuss is when we want to release liberty16:18
Sam-I-Amwhen its ready16:18
*** vikram has joined #openstack-meeting-416:19
Sam-I-Amwhen all liberty-related config changes are done16:19
odyssey4medo we want to target the same day as the upstream release, the friday that follows, or when?16:19
*** adityavajjha has joined #openstack-meeting-416:19
odyssey4meSam-I-Am vague target dates are never good - things never get done16:19
cloudnullI personally think that we rev all of our sha's and if gate passes we release.16:20
*** tfukushima has quit IRC16:20
odyssey4mewe should set a target and endeavour to meet it16:20
Sam-I-Amjust because the gate passes doesnt mean its liberty16:20
evrardjpit's the 19th of this month, right?16:20
Sam-I-Ami found that out with keystone this morning16:20
*** dwalleck has joined #openstack-meeting-416:20
Sam-I-Amnext month?16:20
cloudnulli disagree. if gate passes and its running the liberty code, its liberty16:20
stevelleRC1 is this month on the 24th iirc16:20
Sam-I-Amthis is why gating fails to be realistic16:21
Sam-I-Amneutron technically passes the gate16:21
odyssey4meSam-I-Am you're talking about a tangential issue - liberty will not release until it has passed the integrated gate tests16:21
Sam-I-Amwhat i'm concerned about is releasing, then having to make considerable changes to config files for a point release16:21
odyssey4meit's entirely different to the testing that's done day to day, and is a distraction in this conversation16:21
Sam-I-Ambecause it wasnt really using liberty config items16:22
odyssey4meSam-I-Am so that's the point of the items to review all the config files16:22
Sam-I-Amyes, and the reason why i was saying we shouldnt release until those are done16:22
odyssey4meso we need to set a date when we expect that to be done, and we need volunteers to do it16:22
Sam-I-Amwhich hopefully is on or around the upstream release16:22
Sam-I-Amthey should be frozen now at least16:22
cloudnulland if you have thoughts on that please contribute them to the spec so we can implement the changes.16:23
odyssey4mewe can do the checks and adjustments with the RC's16:23
odyssey4meif anyone has the inclination, that inspection can already be started now16:23
Sam-I-Amodyssey4me: sort of working on that a a side-effect of upstream install guide updates16:24
odyssey4mepatches for policy/config file changes are welcome right now16:24
cloudnull^ that would be awesome for somebody to start16:24
Sam-I-Amworking my way through the services16:24
Sam-I-Amkeystone is going to be fun16:24
cloudnullSam-I-Am:  if you have a diff as you work through the services in the install guide refresh we can work off that16:24
Sam-I-Amcloudnull: its more like notes rather than a diff, but there's something16:24
cloudnullor if you're keeping track on an etherpad we can lurk there too16:25
Sam-I-Amalso need to determine what is a packaging bug16:25
Sam-I-Amhence why i shall test these in osad too16:25
Sam-I-Amahh yeah thats a good idea16:25
Sam-I-Ama matts-liberty-ramblings etherpad16:25
cloudnullwould you mind starting an etherpad ?16:25
cloudnull#action Sam-I-Am to create an etherpad for the config changes he finds for future OSAD implementation16:26
odyssey4me#action odyssey4me to switch the blueprint for juno->liberty upgrades to 12.1.016:26
*** tfukushima has joined #openstack-meeting-416:26
palendaeWhoa what?16:26
palendaeJuno to liberty?16:26
palendaeKilo to liberty?16:27
odyssey4mecorrection, Kilo->Liberty y'all know what I'm sa'in16:27
palendaeI've heard some crazy things in the past few months, so... :)16:27
Sam-I-Ampalendae: i heard we're upgrading icehouse to liberty16:27
Sam-I-Ampalendae: tag, you're it16:28
Sam-I-Amfor various definitions of seam16:28
Sam-I-Amand lessly16:28
palendaeSam-I-Am: You can tag me all you want16:28
*** tfukushima has quit IRC16:28
*** tfukushima has joined #openstack-meeting-416:28
cloudnullso next up16:28
cloudnull#topic Mitaka Summit Discussion Agenda16:28
*** openstack changes topic to "Mitaka Summit Discussion Agenda (Meeting topic: OpenStack Ansible Meeting)"16:28
odyssey4meit would seem to me that testing swift-only deployments and support for systemd also need to move to a later milestone?16:29
Sam-I-Amwont be there16:29
cloudnulljust real quick , please add items to the etherpad for consideration at the summit16:29
prometheanfireodyssey4me: probably16:29
*** hemanthm_ is now known as hemanthm16:29
Sam-I-Amout of expendable organs16:29
stevelleyou got spare lung, kidney...16:30
evrardjpmaybe we could remove haproxy-v2, it's not that important I guess16:30
*** s3wong has joined #openstack-meeting-416:30
prometheanfireis this things required for liberty to 'release'?16:31
odyssey4meprometheanfire uh, what are you referring to?16:31
*** VW_ has joined #openstack-meeting-416:31
Sam-I-Amwe're talking about mitaka summit discussions?16:31
prometheanfireliberty specs16:31
Sam-I-Amwelcome to 10 minutes ago?16:32
prometheanfireah, don't think the previous topic was closed16:32
cloudnullthe systemd support Im sure I can get to, I just need reviewers to make the other irons in the fire go. But if someone else wants to implement the change they're welcome to it16:32
evrardjpfor the summit discussion, shouldn't talk about the docs?16:32
odyssey4mecloudnull my concern is that if it doesn't make it into 12.0.0 then it may have to wait until 13.0.0, unless it's not a breaking change?16:32
prometheanfireodyssey4me: nice to have or need to have? and manpower16:33
odyssey4meI'd rather get that into a .0 release so that it's there when we get into thorough upgrade testing16:33
cloudnullyes 12 or 13 IMO we could do it as a major release but that feels dirty16:33
prometheanfirewith the new versioning we can version when we want16:33
*** baoli_ has quit IRC16:33
prometheanfirenot that we already couldn't16:34
odyssey4meprometheanfire yes, but we've opted to stay in line for major versions16:34
cloudnullths is what we have so far for liberty (spec wise)16:34
prometheanfiredid we want the ipv6 spec for it?16:35
prometheanfireI think you said it'd be nice to have for liberty16:35
cloudnullnamed veths would be a good one to complete theres a second part to that process which is here:
Sam-I-Amveth betterification in general16:36
odyssey4meprometheanfire yeah, although considering the work we already have on our plate I'm inclined to say we should rather get that going in the Mitaka cycle16:36
Sam-I-Amits been an annoying problem16:36
odyssey4mecloudnull on the veth issue16:36
evrardjpodyssey4me: should I remove haproxy v2?16:36
prometheanfireodyssey4me: ya, doesn't mater to me when tbh16:36
cloudnull#topic reviews16:37
*** openstack changes topic to "reviews (Meeting topic: OpenStack Ansible Meeting)"16:37
odyssey4meI have the impression from somewhere that naming the veths will cause the container restarts to not work at all... although I'm not clear on whether that is all the time or only sometimes16:37
cloudnullodyssey4me:  yes that is true16:37
palendaeodyssey4me: Correct, if they dangle16:37
Sam-I-Amit only fails if the veth pair still exists?16:37
odyssey4meevrardjp it's up to you whether you want to discuss it or not16:37
cloudnulland intended.16:37
Sam-I-Amhence why there's the veth-deleter thingy16:37
prometheanfiremhayden: ping16:37
palendaeThe 2nd half of the solution is that because we can now know the names, we can delete them16:37
cloudnullthe second part of that fix resolves it though16:38
cloudnullwhat palendae said16:38
palendaeThe names without the delete are bad, though16:38
odyssey4mepalendae cloudnull ok, then the missing piece for me to make that all go is that ensure that there is an included script for cleaning up the dangling dirties16:38
Sam-I-Ampalendae: at least things fail a little better16:38
palendaeBut generally agreed to be better than veth pairs floating in the ether.  vether pairs.16:38
mhaydenprometheanfire: echo reply16:38
odyssey4meah, I see the cleaner is in
odyssey4meok cool - I'm down with that :)16:39
cloudnullit would be great to backport that to kilo too16:39
prometheanfiremhayden: we are talking about the veth stuff here16:39
odyssey4mecloudnull is that not perhaps a breaking change though?16:39
mhaydeni'm still trying to figure out how to fix this in LXC, but i'm not well versed in C16:39
palendaemhayden: That may be a long tail thing16:40
palendaeSounds like LXC's tools could use some love overall16:40
mhaydenlong story short, LXC should be cleaning up the veths -- if the kernel netlink backlog is overloaded, LXC should try to re-do it16:40
odyssey4mepalendae considering your work on this issue, I'm surprised not seeing your vote on ?16:40
mhaydenextraordinarily long tail :)16:40
*** bharathm has quit IRC16:40
palendaeodyssey4me: Last week was meeting hell, this week's been cinder investigation hell. I'll re-visit that this afternoon though16:41
cloudnullnext review I want to highlight evrardjp16:41
*** nhairston1 has joined #openstack-meeting-416:41
*** VanL has joined #openstack-meeting-416:41
*** nhairston has quit IRC16:41
evrardjpFirst, the status:16:41
* cloudnull hands mic to evrardjp16:41
evrardjpThey were 2 patches for delivering keepalived for haproxy. We've got an agreement, and therefore we are closer to release keepalived for haproxy.16:41
evrardjpHowever, there is still work to do.16:41
evrardjpone of its is to decide the inventory form.16:41
evrardjpwe'll have to introduce an env.d/ file if there are ppl who'd like to test keepalived in containers.16:42
evrardjpI'd not personnally do it, so I don't really care BUT I think keepalived/haproxy deserve an env.d/ file, whether it's to define variables for it or generate containers.16:42
evrardjpI was planning to create "keepalived" containers, but it seems that the name isn't obvious.16:42
evrardjpWe can decide whether we use "haproxy", "keepalived" or do nothing.16:42
evrardjpKeepalived: you can use the same name/container for other services than haproxy. I doubt that ppl will do that though.16:42
*** bradjones|away is now known as bradjones16:42
*** KunalGandhi has joined #openstack-meeting-416:42
evrardjpHaproxy: the name of the container reflects better of what's running inside in this case: haproxy16:42
*** vivek-ebay has joined #openstack-meeting-416:42
Sam-I-Amodyssey4me: i'd +1 except i sort of worked with cloudnull to write it, so not sure here.16:42
*** jckasper has joined #openstack-meeting-416:42
evrardjpnothing: if I'm not mistaken (cloudnull, could you confirm?) NOT setting an env.d would make the keepalived playbook run on the target you mention in conf.d. So it will run automatically on bare metal. The setup-hosts will not generate any containers.16:42
evrardjpSo what's your opinion on this first topic? ;)16:43
odyssey4mehmm, so I find myself wondering why anyone would seperate their keepalived router from the service16:44
odyssey4medo they not need to colocate?16:44
cloudnullI think if we're making haproxy and keepalived a first class citizen it should have an entry in env.d16:44
odyssey4meie keepalived does start and stop scripts for haproxy, so surely they need to be on the same system16:44
evrardjpI propose as haproxy16:44
palendaeI agree with the env.d entry16:44
evrardjpwe seem to agree :)16:45
odyssey4meso for me it seems sensible to have a container for haproxy, and keepalived can facilitate the vip for it in the same container16:45
evrardjpthat part will be tricky though16:45
evrardjpkeepalived in containers with multicast... not so sure...16:45
evrardjpit should be tested16:45
cloudnullodyssey4me:  brings up a good point. but in this case keepalived could, in the future, be used with multiple services. so from a role prospective i think it makes snese to have two roles for haproxy and keepalived16:45
odyssey4meoh dear, yes... there is that16:45
odyssey4mecloudnull ++16:46
evrardjpyeah, that seem obvious16:46
cloudnullwe could then set keepalived as a dep of the haproxy role passing vars into as needed16:46
evrardjpit shouldn't even be a dep16:46
evrardjpit's not mandatory16:46
*** bpoulos has quit IRC16:46
odyssey4meevrardjp to keep things simple for now I'd suggest leaving out trying to make it work in a container and rather set that as a future improvement task16:46
evrardjpyou could16:46
evrardjpand it will work16:46
evrardjpthere is another point:16:46
cloudnullmaybe a dep with a conditional ?16:46
evrardjpwe could16:47
evrardjpso about the other point:16:47
cloudnullconditional executes when there os > 1 host ?16:47
evrardjpat the moment I'm importing my changes from galaxy to this repo, so it's kinda annoying.16:47
odyssey4mecloudnull I would prefer it not to be a dep in the haproxy role as it is too prescriptive of the architecture16:47
odyssey4meit would be better to include the roles in the playbooks, that way the playbook describes the architecture but the roles are independent16:47
evrardjpwhat's inside the current commit is almost good I'd say16:47
evrardjpwe can just include the keepalived playbook conditionnaly in haproxy's one16:48
*** dims_ has joined #openstack-meeting-416:48
odyssey4meevrardjp yeah, I'm down with that16:48
evrardjpso about the galaxt part:16:48
cloudnullodyssey4me: if someone wanted haproxy on >1 host then they would need something like keepalived so having it as a dep makes sense to me.16:48
odyssey4mecloudnull but maybe they want to use another way of doing the virtual ip16:49
*** ivar-lazzaro has quit IRC16:49
evrardjplike corosync etc.16:49
*** zeih has joined #openstack-meeting-416:49
odyssey4meless prescriptive in the role, more prescriptive in the playbooks16:49
evrardjpso this is a good topic, I think it would be best to continue it on the commit maybe?16:49
*** ivar-lazzaro has joined #openstack-meeting-416:50
evrardjpthis way I can have another part of my message :)16:50
cloudnullok carry on16:50
evrardjpif I could use the ansible-role-requirements.yml(.example), that would be of some help to avoid double work for me16:50
evrardjpI know there is no consensus yet, but do we have a timeline for it?16:50
odyssey4meah, so you mean the approval to allow independent role repositories?16:51
*** dims has quit IRC16:51
*** aswadr has quit IRC16:51
*** jay_s_b has joined #openstack-meeting-416:51
odyssey4meI have a revision to make on the spec after feedback from hughsaunders and cloudnull16:51
evrardjpso definitely not until mitaka summit16:52
odyssey4meit still seems that everyone is confused about the spec and thinks that it's the button to break out the current roles, which it is not16:52
cloudnullevrardjp: I view that more like a meta spec .16:52
cloudnullonce we approve it we can start the process.16:52
evrardjpI thought this could be a good use case, that's all16:52
cloudnulland if moving the keepalived to the requirements file makes sense then i think we do that16:52
evrardjpthe keepalived's role16:53
odyssey4meevrardjp it would :)16:53
cloudnullas to not duplicate work16:53
evrardjpI have another last topic, but I've taken too much time, sorry16:53
odyssey4meok, I'll revise that spec in the morning and hopefully we'll get some reviews through the day16:53
cloudnullIMHO if that spec goes in we should have the ability to add requirement roles to the stack from liberty >16:53
*** zeih has quit IRC16:54
*** ivar-lazzaro has quit IRC16:54
evrardjpso that's all for me16:54
cloudnullwe have only 5 min left16:55
cloudnull#topic Open discussion16:55
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack Ansible Meeting)"16:55
cloudnullanything ?16:55
mhaydenand input on the security hardening thread is good ;)16:56
* mhayden is considering drafting a spec16:56
*** jmckind has joined #openstack-meeting-416:56
palendaemhayden: Yes, we should :)16:56
*** LouisF has joined #openstack-meeting-416:56
* mhayden will do the things16:56
*** yamamoto has quit IRC16:56
evrardjpthere should be a lot of discussion about SSLing things then :p16:56
*** tfukushima has quit IRC16:57
evrardjpand omg... apparmor ><16:57
mhaydenTOMOYO? ;)16:57
mhaydensince we can stack LSM's in Linux 4.2 now16:57
prometheanfiremhayden: and replied to the reply16:57
* mhayden wanders off-topic and waits for cloudnull to throw a keyboard16:57
palendaemhayden: Is 4.2 in 16.04? :)16:57
cloudnull4.2 or bust !16:57
prometheanfirethe LSM stacking is not that useful imo :P16:57
mhaydenpalendae: 17.1016:58
mhaydeni still can't convince people that one LSM at a time is a good thing :P16:58
prometheanfiremhayden: selinux or bust16:58
cloudnullim sure RHEL will backport it to 3.10 ...16:58
prometheanfirecloudnull: why don't we have selinux support?16:58
mhaydeni heard selinux sucks16:58
cloudnullwe do16:58
* mhayden giggles16:58
Sam-I-Amthey all suck16:58
cloudnullsetenforce = 016:58
*** puranamr has joined #openstack-meeting-416:59
mhaydencloudnull: sigh16:59
prometheanfireI though about wearing that tshirt today :P16:59
*** johnsom has joined #openstack-meeting-416:59
mhaydengreat, now someone will buy that :P16:59
odyssey4metime to end the meeting16:59
cloudnullok we're done here16:59
* mhayden woots16:59
cloudnullthanks everyone !16:59
*** cathy_ has joined #openstack-meeting-416:59
Sam-I-Amlates d00ds16:59
*** openstack changes topic to "OpenStack Meetings ||"16:59
openstackMeeting ended Thu Sep 10 16:59:57 2015 UTC.  Information about MeetBot at . (v 0.1.4)16:59
openstackMinutes (text):
*** odyssey4me has left #openstack-meeting-417:00
*** Sam-I-Am has left #openstack-meeting-417:00
*** prometheanfire has left #openstack-meeting-417:00
*** evrardjp has left #openstack-meeting-417:00
cathy_#startmeeting service_chaining17:00
openstackMeeting started Thu Sep 10 17:00:30 2015 UTC and is due to finish in 60 minutes.  The chair is cathy_. Information about MeetBot at
*** mohankumar_ has joined #openstack-meeting-417:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: service_chaining)"17:00
openstackThe meeting name has been set to 'service_chaining'17:00
*** KunalGandhi has quit IRC17:00
cathy_hi everyone17:00
*** Anh has joined #openstack-meeting-417:00
*** ivar-lazzaro has joined #openstack-meeting-417:01
mohankumar_Hi everyone17:01
cathy_does anyone have any topic that you would like to discuss?17:01
*** rromans has left #openstack-meeting-417:02
*** stevelle has left #openstack-meeting-417:02
*** wokuma1 has left #openstack-meeting-417:02
*** KunalGandhi has joined #openstack-meeting-417:02
cathy_I have three: status of the project, networking-sfc doc publishing, testing17:03
cathy_#topic status of the project17:03
*** openstack changes topic to "status of the project (Meeting topic: service_chaining)"17:03
cathy_we have got the specs reviewed and merged ! Thanks everyone!17:04
*** baoli has joined #openstack-meeting-417:04
mohankumar_cathy_:  great !17:05
cathy_The unit test scripts, updated API and DB files, Service Plugin files to be compliant with the approved APIs are planned to be posted this Friday17:05
*** jwarendt has joined #openstack-meeting-417:05
cathy_The first patch of the OVS driver and DB is planned to be posted within the next week or two17:06
*** bouthors has joined #openstack-meeting-417:06
LouisFbouthors: hi17:06
cathy_any question on this topic?17:06
cathy_#topic networking-sfc doc publishing17:07
*** openstack changes topic to "networking-sfc doc publishing (Meeting topic: service_chaining)"17:07
*** baoli_ has joined #openstack-meeting-417:07
cathy_Thanks Paul for this work!17:07
pcarverHopefully this will do the trick17:07
pcarverhasn't merged yet, but I think it's what's needed17:08
*** TravT has quit IRC17:08
cathy_pcarver: openstack-infra needs to approve it to be merged, right?17:08
*** afv_ has joined #openstack-meeting-417:08
pcarvercathy_: correct17:08
pcarversame +2 requirement as any other code I think17:08
*** baoli has quit IRC17:08
cathy_maybe you would like to go to the infra channel to let them know this and review it?17:09
pcarverI'm guessing that core members of infra project probally watch for +1 reviews and then review them17:09
pcarversure, I can do that17:09
cathy_pcarver: thanks!17:09
*** bharathm has joined #openstack-meeting-417:09
pcarverI also sent a message to the admins of the Launchpad page because there doesn't appear to be a networking-sfc page17:09
pcarveri.e. on the list on
cathy_pcarver: thanks for straightening all these out!17:11
pcarver exists, it just doesn't appear on the OpenStack page with the other networking-X projects17:11
johnsomWe also need to have the neutron infra liaisons chime in I suspect.17:11
xgermanthose are the lt. like dougwig, amax, etc.17:11
pcarverAlso, semi-related, everyone should take a look at17:12
pcarverwhich is a devref for sub-projects17:12
cathy_pcarver: sure.17:13
pcarverIt talks about release to PyPi and Launchpad release tagging and tarballs17:13
vikramKyle helped us in releasing for networking-onos17:13
pcarverThe whole doc is worth reading, not just the part changed in that review17:14
*** nikhil_k_ is now known as nikhil_k-bbiab17:14
cathy_johnsom: could you mean we meed someone from infra to review paul's change of adding networking-sfc doc?17:14
vikramI believe only the authorized person can make a release17:15
johnsomcathy_ We need a neutron lt. to +1 before infra will look at it.  It's part of the new infra liaison plan17:15
cathy_vikram: Yes, let's ask Kyle or Armando to help on this.17:15
*** mohankumar__ has joined #openstack-meeting-417:15
pcarverThe maintainer listed on the networking-sfc page on Launchpad is xiaodongwang17:16
s3wongwho is xiaodongwang?17:16
cathy_pcarver: could you post the link of the launchpad?17:17
pcarverIt may be that is abandoned and needs to be revived17:17
cathy_s3wong: xiaodongwang is contributing to this project too17:17
s3wongcathy_: I see17:18
*** adityavajjha has quit IRC17:18
cathy_pcarver: Do you mean we need to create networking-sfc in, not a separate one in
johnsomcathy_ FYI on infra:
*** mgariepy has left #openstack-meeting-417:20
pcarvercathy_: I don't think so, but I think a connection is missing17:20
pcarverCompare with for example17:20
pcarverNote that the OVN page (and other networking-X projects) show "Part of OpenStack" on their page17:21
pcarverSomehow the SFC page exists but doesn't seem to have the connection to OpenStack that the other networking-X projects have17:21
pcarverAssuming we intend to use Launchpad for bug reports we'll want it setup correctly17:22
*** erikwilson has quit IRC17:23
pcarverI already sent an inquiry yesterday using the "Contact this team's admins" link on but I haven't heard back yet.17:23
cathy_pcarver: OK, I see. thanks17:23
pcarverIf I don't get a response in a couple of days I'll do more asking on the -dev list and/or infra IRC channel17:24
*** salv-orlando has joined #openstack-meeting-417:24
*** mohankumar__ has quit IRC17:25
*** jerryz has joined #openstack-meeting-417:25
cathy_johnsom: thanks for the link!17:25
*** puranamr has quit IRC17:28
*** SimonChung has joined #openstack-meeting-417:28
*** VanL has quit IRC17:28
cathy_pcarver: for your patch of adding the networking-sfc doc, you may want to ask the infra channel whether you need to get the Neutron API LT +1 or which Neutron LT you need +1.17:28
pcarverIt looks like armax is a Neutron Infra Lieutenant17:29
*** salv-orlando has quit IRC17:29
s3wongand it seems like armax has already given his +1 :-)17:29
pcarverNo, I don't think so17:29
pcarveroh, wait, I just hit refresh17:30
cathy_s3wong: really. Cool! armax always gives us the support at the right time.17:30
*** salv-orlando has joined #openstack-meeting-417:30
cathy_pcarver: yes, armax gives it +117:30
cathy_can we go to the next topic?17:31
cathy_#topic testing for networking-sfc17:32
*** openstack changes topic to "testing for networking-sfc (Meeting topic: service_chaining)"17:32
cathy_Besides UT, any other tests we should do ?17:33
cathy_we also need to do tempest17:34
*** SumitNaiksatam has joined #openstack-meeting-417:34
vikramcathy: Yes17:34
vikramcathy: API & Functional17:34
*** b3rnard0 has left #openstack-meeting-417:35
cathy_vikram: do you mean Unit test on API and functional or other types of test17:35
vikramI meant tempest tests17:35
vikram+ there is something called full-stack test17:35
*** jay_s_b has quit IRC17:35
cathy_vikram: OK. Yes we will do that17:36
vikramWe need to check it's applicability17:36
cathy_vikram: good point.17:36
vikramAPI --> tempest test... but functional is little different.. .17:36
*** armax has quit IRC17:37
cathy_vikram: Is it a integration test with other component? can you help check that and get back to us?17:37
vikramokay .. will check17:38
cathy_vikram: thanks!17:38
LouisFvikram: looks like full-stack testing would be useful17:38
cathy_maybe we need to check what other tests neutron core feature does17:39
cathy_anyone can help checking out this and get back to us in next meeting?17:39
*** VanL has joined #openstack-meeting-417:39
cathy_s3wong: can you help with this?17:40
s3wongcathy_: sure17:41
cathy_s3wong: thanks!17:41
pcarvercathy_: I don't see Abhinav here today, but I did send him an email asking that he plan to spend some time writing functional tests. I haven't heard back from him yet.17:41
cathy_pcarver: great! maybe you can ask him to join next meeting and share the info?17:42
*** armax has joined #openstack-meeting-417:42
pcarvercathy_: I'll continue to follow up with him. I don't know exactly what his workload is, but I'm hoping that I can get a percentage of his time committed.17:43
cathy_  pcarver OK, thanks.17:43
*** VanL has quit IRC17:44
cathy_Now I am going to list the action items17:44
cathy_#action Louis or Cathy finish and post the UT codes17:44
cathy_#action Louis or Cathy finish and post the updated API, DB, DB migration, Driver Manager etc. codes to be compliant with the approved APIs17:45
*** julim has quit IRC17:46
cathy_#action vikram investigate full-stack testing and bring the info back in next IRC meeting17:46
cathy_#action s3wong investigate neutron feature testing and bring the info back in next IRC meeting17:47
cathy_#action pcarver follow up with Abhinav on functional testing and get back to us in next meeting.17:48
*** salv-orlando has quit IRC17:48
cathy_#topic integration of CLI with networking-sfc API on Neutron Server17:49
*** openstack changes topic to "integration of CLI with networking-sfc API on Neutron Server (Meeting topic: service_chaining)"17:49
*** armax has quit IRC17:50
cathy_mohan will start the integration testing with Louis next week, right?17:50
*** zeih has joined #openstack-meeting-417:50
LouisFcathy_: ok17:50
cathy_thanks, folks!17:50
cathy_we make some good progress this week. Hope we will do the same next week and two. let's target on getting the codes completed and reviewed by early October17:51
cathy_thanks everyone's contribution!17:51
LouisFcathy_: sounds like aplan17:51
mohankumar_Thumps up !17:52
cathy_anything else you would like to discuss?17:52
s3wongcathy_: are we doing anything on the design summit?
cathy_#topic design summit17:53
*** openstack changes topic to "design summit (Meeting topic: service_chaining)"17:53
pcarverI added an item to discuss relationship between SFC and BGPVPNs17:53
s3wongpcarver: I see17:54
pcarversome people at AT&T consider them inextricably entwined17:54
LouisFpcarver: is that item 7?17:54
cathy_we can also add an item to discuss the relationship between sfc and tacker17:54
vikrampcarver: I remember a talk about this in the lat summit17:54
*** zeih has quit IRC17:55
s3wongcathy_: and as Tacker team member I would welcome that17:55
*** jwagner is now known as jwagner_away17:55
s3wongcathy_: though we need to integrate with Heat first...17:55
LouisFs3wong: definitely17:56
pcarvercathy_: Good idea. s3wong: Is there a separate Etherpad for Tacker?17:56
vikrams3wong: mhankumar_ is doing that17:56
vikrams3wong: mohankumar_ is doing that17:56
LouisFmohankumar_: great!17:56
s3wongpcarver: no --- unfortunately, as a project not yet in the tent, we (tacker) didn't get any design session slot17:56
cathy_vikram: are you saying that mohankumar_ is doing the integration of heat and networking-sfc? cool!17:56
*** banix has joined #openstack-meeting-417:56
*** dwalleck has quit IRC17:56
vikramcathy_: yes.. afaik he is:)17:57
mohankumar_cathy_: yes17:57
pcarvers3wong: Maybe a Friday informal session17:57
*** tfukushima has joined #openstack-meeting-417:57
cathy_mohankumar_: thanks!17:57
*** yamamoto has joined #openstack-meeting-417:57
s3wongpcarver: is there any? My understanding from ttx's email is that all the non-tent session only get to go to lunch tables... :-)17:58
cathy_shall we add that item to the Neutron design Summit or which one?17:58
*** jwarendt has quit IRC17:58
*** stanchan has joined #openstack-meeting-417:58
cathy_the integration of sfc with tacker one17:58
pcarvers3wong: No room reservations, but I believe Friday is supposed to be open and unstructured17:58
pcarverat least it was in Vancouver. People were just gathering in small groups without fixed room assignments17:59
cathy_pcarver: could you take care of adding that integration of tacker with sfc and let us know which slot? time is up17:59
s3wongpcarver: OK17:59
cathy_we need to end the meeting now17:59
vikrampcarver: I remember seeing a mail saying we have lot of rooms this time:)17:59
vikrampcarver: but got to book one for our project18:00
pcarverI'll look into it18:00
vikrampcarver: thanks18:00
s3wongorchestration bye!18:00
*** openstack changes topic to "OpenStack Meetings ||"18:00
openstackMeeting ended Thu Sep 10 18:00:41 2015 UTC.  Information about MeetBot at . (v 0.1.4)18:00
openstackMinutes (text):
*** vikram has quit IRC18:01
*** tfukushima has quit IRC18:01
*** yamamoto has quit IRC18:02
*** cathy_ has quit IRC18:05
*** puranamr has joined #openstack-meeting-418:08
*** bknudson has quit IRC18:10
*** dwalleck has joined #openstack-meeting-418:13
*** afv_ has quit IRC18:13
*** bknudson has joined #openstack-meeting-418:16
*** dzamboni has joined #openstack-meeting-418:16
*** nikhil_k-bbiab is now known as nikhil_k18:17
*** carl_baldwin has quit IRC18:18
*** VW_ has quit IRC18:23
*** VW_ has joined #openstack-meeting-418:23
*** johnsom has left #openstack-meeting-418:24
*** VanL has joined #openstack-meeting-418:24
*** VW__ has joined #openstack-meeting-418:26
*** VW_ has quit IRC18:27
*** tfukushima has joined #openstack-meeting-418:27
*** xingchao has quit IRC18:28
*** iurygregory has quit IRC18:30
*** tfukushima has quit IRC18:32
*** iurygregory has joined #openstack-meeting-418:34
*** jwagner_away is now known as jwagner18:36
*** julim has joined #openstack-meeting-418:37
*** julim_ has joined #openstack-meeting-418:39
*** matrohon has joined #openstack-meeting-418:40
*** julim has quit IRC18:42
*** IlyaG has joined #openstack-meeting-418:44
*** harshs has joined #openstack-meeting-418:45
*** zeih has joined #openstack-meeting-418:51
*** puranamr has quit IRC18:51
*** zeih has quit IRC18:55
*** jecarey has quit IRC18:58
*** matrohon has quit IRC19:01
*** salv-orlando has joined #openstack-meeting-419:04
*** dwalleck has quit IRC19:06
*** dims_ has quit IRC19:11
*** dims has joined #openstack-meeting-419:11
*** salv-orlando has quit IRC19:12
*** lexholden has joined #openstack-meeting-419:13
*** carl_baldwin has joined #openstack-meeting-419:13
*** cloudtrainme has quit IRC19:14
*** ivar-lazzaro has quit IRC19:14
*** ivar-lazzaro has joined #openstack-meeting-419:15
*** nhairston1 has quit IRC19:15
*** ivar-lazzaro has quit IRC19:15
*** ivar-lazzaro has joined #openstack-meeting-419:15
*** dwalleck has joined #openstack-meeting-419:16
*** dwalleck has quit IRC19:17
*** puranamr has joined #openstack-meeting-419:19
*** Anh has quit IRC19:19
*** lexholden has quit IRC19:19
*** carl_baldwin has quit IRC19:19
*** VanL has quit IRC19:20
*** puranamr has quit IRC19:23
*** Sukhdev has joined #openstack-meeting-419:23
*** stanchan has quit IRC19:24
*** stanchan has joined #openstack-meeting-419:25
*** cloudtrainme has joined #openstack-meeting-419:25
*** stanchan has quit IRC19:25
*** stanchan has joined #openstack-meeting-419:26
*** nhairston has joined #openstack-meeting-419:27
*** xingchao has joined #openstack-meeting-419:29
*** nhairston1 has joined #openstack-meeting-419:31
*** puranamr has joined #openstack-meeting-419:31
*** nhairston has quit IRC19:32
*** xingchao has quit IRC19:33
*** carl_baldwin has joined #openstack-meeting-419:33
*** geoffarnold has quit IRC19:34
*** IlyaG has quit IRC19:38
*** IlyaG has joined #openstack-meeting-419:38
*** matrohon has joined #openstack-meeting-419:40
*** rbak has quit IRC19:40
*** VanL has joined #openstack-meeting-419:43
*** salv-orlando has joined #openstack-meeting-419:46
*** rbak has joined #openstack-meeting-419:46
*** IlyaG has quit IRC19:47
*** zeih has joined #openstack-meeting-419:51
*** yamahata has quit IRC19:52
*** jecarey has joined #openstack-meeting-419:54
*** sdake has joined #openstack-meeting-419:54
*** zeih has quit IRC19:56
*** sdake_ has joined #openstack-meeting-420:02
*** amotoki has quit IRC20:03
*** mohankumar_ has quit IRC20:03
*** SumitNaiksatam has quit IRC20:05
*** sdake has quit IRC20:05
*** salv-orlando has quit IRC20:05
*** SumitNaiksatam has joined #openstack-meeting-420:07
*** cloudtrainme has quit IRC20:09
*** cloudtrainme has joined #openstack-meeting-420:10
*** salv-orlando has joined #openstack-meeting-420:15
*** salv-orlando has quit IRC20:16
*** salv-orlando has joined #openstack-meeting-420:17
*** yamahata has joined #openstack-meeting-420:18
*** delattec has quit IRC20:20
*** salv-orlando has quit IRC20:21
*** cloudtra_ has joined #openstack-meeting-420:24
*** jckasper has quit IRC20:25
*** vivek-ebay has quit IRC20:25
*** vivek-ebay has joined #openstack-meeting-420:26
*** matrohon has quit IRC20:26
*** cloudtrainme has quit IRC20:27
*** tfukushima has joined #openstack-meeting-420:28
*** isq has quit IRC20:30
*** salv-orlando has joined #openstack-meeting-420:31
*** tfukushima has quit IRC20:33
*** puranamr has quit IRC20:36
*** LouisF has quit IRC20:42
*** puranamr has joined #openstack-meeting-420:43
*** VanL has quit IRC20:44
*** IlyaG has joined #openstack-meeting-420:47
*** IlyaG has quit IRC20:48
*** IlyaG has joined #openstack-meeting-420:48
*** geoffarnold has joined #openstack-meeting-420:51
*** zeih has joined #openstack-meeting-420:52
*** zeih has quit IRC20:57
*** vivek-ebay has quit IRC21:11
*** vivek-ebay has joined #openstack-meeting-421:11
*** sdake_ has quit IRC21:13
*** Piet has quit IRC21:16
*** rfolco has quit IRC21:17
*** stanchan has quit IRC21:22
*** stanchan_ has joined #openstack-meeting-421:22
*** Sukhdev has quit IRC21:23
*** VanL has joined #openstack-meeting-421:25
*** sdake has joined #openstack-meeting-421:26
*** KunalGandhi has quit IRC21:27
*** stanchan has joined #openstack-meeting-421:28
*** tfukushima has joined #openstack-meeting-421:29
*** KunalGandhi has joined #openstack-meeting-421:30
*** stanchan_ has quit IRC21:30
*** jmckind has quit IRC21:33
*** nhairston has joined #openstack-meeting-421:34
*** tfukushima has quit IRC21:34
*** puranamr has quit IRC21:34
*** puranamr has joined #openstack-meeting-421:35
*** jwagner is now known as jwagner_away21:36
*** banix has quit IRC21:36
*** nhairston1 has quit IRC21:38
*** jecarey has quit IRC21:38
*** VanL has quit IRC21:40
*** nhairston has quit IRC21:40
*** geoffarnold has quit IRC21:41
*** VW__ has quit IRC21:43
*** VW_ has joined #openstack-meeting-421:43
*** jckasper has joined #openstack-meeting-421:44
*** geoffarnold has joined #openstack-meeting-421:44
*** VW_ has quit IRC21:48
*** stanchan has quit IRC21:48
*** dshakhray has quit IRC21:52
*** zeih has joined #openstack-meeting-421:53
*** zeih has quit IRC21:58
*** jckasper has quit IRC22:01
*** dzamboni has quit IRC22:02
*** klamath has quit IRC22:02
*** bknudson has quit IRC22:04
*** stanchan has joined #openstack-meeting-422:04
*** Piet has joined #openstack-meeting-422:05
*** geoffarnold has quit IRC22:09
*** VW_ has joined #openstack-meeting-422:15
*** sigmavirus24 is now known as sigmavirus24_awa22:18
*** dims_ has joined #openstack-meeting-422:20
*** VW__ has joined #openstack-meeting-422:22
*** stanchan has quit IRC22:22
*** dims has quit IRC22:23
*** geoffarnold has joined #openstack-meeting-422:24
*** VW_ has quit IRC22:26
*** VW__ has quit IRC22:26
*** isq has joined #openstack-meeting-422:29
*** yamahata has quit IRC22:30
*** yamahata has joined #openstack-meeting-422:31
*** carl_baldwin has quit IRC22:36
*** BjoernT has quit IRC22:37
*** cdelatte has joined #openstack-meeting-422:44
*** carl_baldwin has joined #openstack-meeting-422:45
*** dannywilson has quit IRC22:52
*** dannywilson has joined #openstack-meeting-422:53
*** zeih has joined #openstack-meeting-422:54
*** banix has joined #openstack-meeting-422:54
*** salv-orl_ has joined #openstack-meeting-422:56
*** zeih has quit IRC22:58
*** salv-orlando has quit IRC22:59
*** baoli_ has quit IRC23:01
*** baoli has joined #openstack-meeting-423:02
*** bknudson has joined #openstack-meeting-423:05
*** baoli has quit IRC23:07
*** baoli has joined #openstack-meeting-423:08
*** cdelatte has quit IRC23:08
*** pmesserli has quit IRC23:12
*** geoffarnold has quit IRC23:15
*** delattec has joined #openstack-meeting-423:18
*** delattec has quit IRC23:19
*** woodard_ has joined #openstack-meeting-423:22
*** jpekkari has joined #openstack-meeting-423:25
*** woodard has quit IRC23:26
*** cloudtra_ has quit IRC23:28
*** stanchan has joined #openstack-meeting-423:28
*** mmedvede has quit IRC23:29
*** tfukushima has joined #openstack-meeting-423:30
*** stanchan has quit IRC23:32
*** woodard_ has quit IRC23:33
*** tfukushima has quit IRC23:35
*** bharathm has quit IRC23:42
*** Swami has quit IRC23:42
*** salv-orl_ has quit IRC23:43
*** baoli has quit IRC23:47
*** yamamoto has joined #openstack-meeting-423:48
*** dannywilson has quit IRC23:53
*** stancha60 has joined #openstack-meeting-423:53
*** zeih has joined #openstack-meeting-423:54
*** geoffarnold has joined #openstack-meeting-423:55
*** dannywilson has joined #openstack-meeting-423:55
*** dannywilson has quit IRC23:58
*** Sukhdev has joined #openstack-meeting-423:58
*** zeih has quit IRC23:59
*** nhairston has joined #openstack-meeting-423:59

Generated by 2.14.0 by Marius Gedminas - find it at!