| *** pmesserli has quit IRC | 00:01 | |
| *** sdake has joined #openstack-meeting-4 | 00:03 | |
| *** s3wong_ has joined #openstack-meeting-4 | 00:04 | |
| *** s3wong has quit IRC | 00:07 | |
| *** hongbin has quit IRC | 00:10 | |
| *** oanson has left #openstack-meeting-4 | 00:11 | |
| *** JRobinson__ is now known as JRobinson__afk | 00:22 | |
| *** lamt has quit IRC | 00:25 | |
| *** lamt has joined #openstack-meeting-4 | 00:30 | |
| *** limao has joined #openstack-meeting-4 | 00:32 | |
| *** bobh has joined #openstack-meeting-4 | 00:32 | |
| *** spzala has joined #openstack-meeting-4 | 00:32 | |
| *** spzala has quit IRC | 00:37 | |
| *** bobh has quit IRC | 00:40 | |
| *** s3wong_ is now known as s3wong | 00:41 | |
| *** Julien-zte has joined #openstack-meeting-4 | 00:43 | |
| *** Swami has quit IRC | 00:46 | |
| *** arif-ali has quit IRC | 00:51 | |
| *** amotoki has joined #openstack-meeting-4 | 00:52 | |
| *** bobh has joined #openstack-meeting-4 | 00:52 | |
| *** haleyb_ has joined #openstack-meeting-4 | 00:53 | |
| *** bpokorny has joined #openstack-meeting-4 | 00:55 | |
| *** JRobinson__afk is now known as JRobinson__ | 00:56 | |
| *** arif-ali has joined #openstack-meeting-4 | 00:56 | |
| *** amotoki has quit IRC | 00:57 | |
| *** haleyb_ has quit IRC | 00:58 | |
| *** bpokorny has quit IRC | 00:59 | |
| *** uck has quit IRC | 01:03 | |
| *** uck has joined #openstack-meeting-4 | 01:05 | |
| *** uck has quit IRC | 01:10 | |
| *** woodard has quit IRC | 01:13 | |
| *** woodard has joined #openstack-meeting-4 | 01:13 | |
| *** tovin07_ has joined #openstack-meeting-4 | 01:14 | |
| *** bpokorny has joined #openstack-meeting-4 | 01:21 | |
| *** Sukhdev has quit IRC | 01:22 | |
| *** amotoki has joined #openstack-meeting-4 | 01:29 | |
| *** zhurong has joined #openstack-meeting-4 | 01:30 | |
| *** bpokorny_ has joined #openstack-meeting-4 | 01:33 | |
| *** bpokorny has quit IRC | 01:37 | |
| *** bpokorny_ has quit IRC | 01:37 | |
| *** xingchao has joined #openstack-meeting-4 | 01:38 | |
| *** thorst has joined #openstack-meeting-4 | 01:41 | |
| *** thorst has quit IRC | 01:45 | |
| *** thorst has joined #openstack-meeting-4 | 01:49 | |
| *** thorst has quit IRC | 01:51 | |
| *** links has joined #openstack-meeting-4 | 01:55 | |
| *** reedip_ has joined #openstack-meeting-4 | 01:57 | |
| *** lamt has quit IRC | 01:57 | |
| *** tonytan4ever has joined #openstack-meeting-4 | 02:01 | |
| *** bobh has quit IRC | 02:06 | |
| *** links has quit IRC | 02:07 | |
| *** bobh has joined #openstack-meeting-4 | 02:10 | |
| *** coolsvap has joined #openstack-meeting-4 | 02:19 | |
| *** thorst has joined #openstack-meeting-4 | 02:20 | |
| *** haleyb_ has joined #openstack-meeting-4 | 02:32 | |
| *** syed__ has quit IRC | 02:35 | |
| *** thorst has quit IRC | 02:40 | |
| *** armax has quit IRC | 02:44 | |
| *** haleyb_ has quit IRC | 02:44 | |
| *** haleyb_ has joined #openstack-meeting-4 | 02:45 | |
| *** bobmel has joined #openstack-meeting-4 | 02:47 | |
| *** bobmel has quit IRC | 02:51 | |
| *** unicell has quit IRC | 02:56 | |
| *** s3wong has quit IRC | 03:03 | |
| *** baoli has joined #openstack-meeting-4 | 03:03 | |
| *** bobh has quit IRC | 03:04 | |
| *** armax has joined #openstack-meeting-4 | 03:07 | |
| *** spzala has joined #openstack-meeting-4 | 03:16 | |
| *** spzala has quit IRC | 03:20 | |
| *** vishnoianil has quit IRC | 03:21 | |
| *** JRobinson__ is now known as JRobinson__afk | 03:23 | |
| *** spzala has joined #openstack-meeting-4 | 03:30 | |
| *** sdake_ has joined #openstack-meeting-4 | 03:33 | |
| *** sdake has quit IRC | 03:37 | |
| *** armax has quit IRC | 03:39 | |
| *** JRobinson__afk is now known as JRobinson__ | 03:43 | |
| *** xingchao has quit IRC | 03:45 | |
| *** xingchao has joined #openstack-meeting-4 | 03:45 | |
| *** bobh has joined #openstack-meeting-4 | 03:49 | |
| *** xingchao has quit IRC | 03:52 | |
| *** berendt has joined #openstack-meeting-4 | 03:52 | |
| *** baoli has quit IRC | 03:52 | |
| *** xingchao has joined #openstack-meeting-4 | 03:53 | |
| *** berendt has quit IRC | 03:54 | |
| *** psachin has joined #openstack-meeting-4 | 03:54 | |
| *** xingchao_ has joined #openstack-meeting-4 | 03:56 | |
| *** xingchao has quit IRC | 03:57 | |
| *** Jeffrey4l has joined #openstack-meeting-4 | 04:03 | |
| *** spzala has quit IRC | 04:03 | |
| *** cwolferh has quit IRC | 04:04 | |
| *** spzala has joined #openstack-meeting-4 | 04:04 | |
| *** spzala has quit IRC | 04:05 | |
| *** amotoki has quit IRC | 04:09 | |
| *** GB21 has joined #openstack-meeting-4 | 04:12 | |
| *** Sukhdev has joined #openstack-meeting-4 | 04:14 | |
| *** armax has joined #openstack-meeting-4 | 04:16 | |
| *** bobh has quit IRC | 04:20 | |
| *** tonytan4ever has quit IRC | 04:23 | |
| *** tonytan4ever has joined #openstack-meeting-4 | 04:23 | |
| *** tonytan4ever has quit IRC | 04:28 | |
| *** iyamahat has quit IRC | 04:31 | |
| *** yamahata has quit IRC | 04:32 | |
| *** xingchao_ has quit IRC | 04:45 | |
| *** xingchao has joined #openstack-meeting-4 | 04:46 | |
| *** sdake_ is now known as sdake | 04:54 | |
| *** reedip_ has quit IRC | 04:59 | |
| *** xingchao has quit IRC | 05:01 | |
| *** reedip_ has joined #openstack-meeting-4 | 05:03 | |
| *** reedip_ has quit IRC | 05:08 | |
| *** sdake_ has joined #openstack-meeting-4 | 05:10 | |
| *** sdake has quit IRC | 05:14 | |
| *** bobmel has joined #openstack-meeting-4 | 05:14 | |
| *** anilvenkata has joined #openstack-meeting-4 | 05:16 | |
| *** bobmel has quit IRC | 05:19 | |
| *** darrenc is now known as darrenc_afk | 05:19 | |
| *** dims has quit IRC | 05:20 | |
| *** haleyb_ has quit IRC | 05:22 | |
| *** sdake_ has quit IRC | 05:24 | |
| *** Sukhdev has quit IRC | 05:25 | |
| *** prateek has joined #openstack-meeting-4 | 05:27 | |
| *** iyamahat has joined #openstack-meeting-4 | 05:32 | |
| *** gongysh has joined #openstack-meeting-4 | 05:32 | |
| *** Julien-zte has quit IRC | 05:38 | |
| *** Julien-zte has joined #openstack-meeting-4 | 05:41 | |
| *** Julien-zte has joined #openstack-meeting-4 | 05:42 | |
| *** xingchao has joined #openstack-meeting-4 | 05:45 | |
| *** Julien-zte has quit IRC | 05:50 | |
| *** Julien-zte has joined #openstack-meeting-4 | 05:51 | |
| *** harlowja has quit IRC | 05:55 | |
| *** gongysh has quit IRC | 05:56 | |
| *** darrenc_afk is now known as darrenc | 05:57 | |
| *** unicell has joined #openstack-meeting-4 | 05:58 | |
| *** dims has joined #openstack-meeting-4 | 05:59 | |
| *** irenab has joined #openstack-meeting-4 | 05:59 | |
| *** amotoki has joined #openstack-meeting-4 | 06:10 | |
| *** JRobinson__ has quit IRC | 06:12 | |
| *** Julien-zte has quit IRC | 06:12 | |
| *** Julien-zte has joined #openstack-meeting-4 | 06:13 | |
| *** leo_wang has joined #openstack-meeting-4 | 06:14 | |
| *** Julien-zte has quit IRC | 06:18 | |
| *** Julien-zte has joined #openstack-meeting-4 | 06:18 | |
| *** xingchao has quit IRC | 06:20 | |
| *** xingchao has joined #openstack-meeting-4 | 06:23 | |
| *** Julien-zte has quit IRC | 06:27 | |
| *** Julien-zte has joined #openstack-meeting-4 | 06:28 | |
| *** markvoelker has quit IRC | 06:28 | |
| *** iyamahat has quit IRC | 06:36 | |
| *** iyamahat has joined #openstack-meeting-4 | 06:39 | |
| *** irenab has quit IRC | 06:43 | |
| *** nadav has joined #openstack-meeting-4 | 06:46 | |
| *** Julien-zte has quit IRC | 06:48 | |
| *** Julien-zte has joined #openstack-meeting-4 | 06:49 | |
| *** vishnoianil has joined #openstack-meeting-4 | 06:50 | |
| *** armax has quit IRC | 06:52 | |
| *** janki has joined #openstack-meeting-4 | 06:53 | |
| *** janki has quit IRC | 06:56 | |
| *** Julien-zte has quit IRC | 06:56 | |
| *** Julien-zte has joined #openstack-meeting-4 | 06:57 | |
| *** xingchao has quit IRC | 06:59 | |
| *** liuyulong__ has joined #openstack-meeting-4 | 07:04 | |
| *** xingchao has joined #openstack-meeting-4 | 07:06 | |
| *** liuyulong_ has quit IRC | 07:07 | |
| *** unicell has quit IRC | 07:10 | |
| *** unicell has joined #openstack-meeting-4 | 07:11 | |
| *** GB21 has quit IRC | 07:16 | |
| *** yfauser has joined #openstack-meeting-4 | 07:18 | |
| *** alexchadin has joined #openstack-meeting-4 | 07:28 | |
| *** GB21 has joined #openstack-meeting-4 | 07:29 | |
| *** slaweq has left #openstack-meeting-4 | 07:33 | |
| *** vishnoianil has quit IRC | 07:34 | |
| *** pcaruana has joined #openstack-meeting-4 | 07:41 | |
| *** korzen has joined #openstack-meeting-4 | 07:43 | |
| *** yfauser has quit IRC | 07:47 | |
| *** ifat_afek has joined #openstack-meeting-4 | 07:58 | |
| *** Julien-zte has quit IRC | 07:58 | |
| ifat_afek | #startmeeting vitrage | 08:00 |
|---|---|---|
| openstack | Meeting started Wed Nov 16 08:00:13 2016 UTC and is due to finish in 60 minutes. The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:00 |
| *** openstack changes topic to " (Meeting topic: vitrage)" | 08:00 | |
| openstack | The meeting name has been set to 'vitrage' | 08:00 |
| ifat_afek | Hi everyone! | 08:00 |
| nadav | hi | 08:00 |
| *** ricolin has joined #openstack-meeting-4 | 08:00 | |
| *** Julien-zte has joined #openstack-meeting-4 | 08:00 | |
| *** yujunz has joined #openstack-meeting-4 | 08:00 | |
| *** haleyb_ has joined #openstack-meeting-4 | 08:01 | |
| *** alon_heller has joined #openstack-meeting-4 | 08:02 | |
| alon_heller | Hi all :) | 08:02 |
| tovin07 | hi | 08:03 |
| ifat_afek | I | 08:05 |
| ifat_afek | many vitrage developers are out of office today, so the meeting might be shorter | 08:06 |
| ifat_afek | #topic Status and Updates | 08:06 |
| *** openstack changes topic to "Status and Updates (Meeting topic: vitrage)" | 08:06 | |
| *** karthiks has quit IRC | 08:07 | |
| yujunz | Hi all | 08:07 |
| ifat_afek | I’m still trying to arrange vitrage documentation. I’ll be happy if someone can review my change for vitrage-specs | 08:07 |
| ifat_afek | #link https://review.openstack.org/#/c/394550/ | 08:07 |
| ifat_afek | This is how the page looks like at the moment, with only Mitaka blueprints: | 08:08 |
| ifat_afek | #link http://specs.openstack.org/openstack/vitrage-specs/ | 08:08 |
| yujunz | Maybe I can help | 08:08 |
| *** ohad has joined #openstack-meeting-4 | 08:08 | |
| yujunz | I did some work for docs in js-generator-openstack project | 08:08 |
| ifat_afek | and I’m waiting for openstack-infra approval for my change of adding the official vitrage documentation | 08:08 |
| ohad | hi | 08:08 |
| ifat_afek | #link https://review.openstack.org/#/c/394181/ | 08:08 |
| yujunz | It seems already +2ed | 08:10 |
| ifat_afek | As part of Ocata goals, all project teams are requested to remove Oslo incubated code. I checked it, and didn’t seem to find anything in vitrage. let me know if you think there is something we do need to do | 08:10 |
| ifat_afek | yujunz: are you talking about the infra change? I need another +2 and workflow+1 | 08:10 |
| yujunz | Yes | 08:10 |
| yujunz | the infra | 08:10 |
| ifat_afek | I’ll ask for another review in the infra IRC channel later today | 08:11 |
| ifat_afek | these are my updates | 08:12 |
| ifat_afek | any other updates? | 08:12 |
| yujunz | I have three | 08:12 |
| *** miani has joined #openstack-meeting-4 | 08:13 | |
| yujunz | First the skeleton | 08:13 |
| yujunz | #link https://review.openstack.org/396974 | 08:13 |
| miani | Hi guys. | 08:13 |
| yujunz | It is initiated during my creation of static datasource | 08:13 |
| *** ohad has quit IRC | 08:13 | |
| *** ohad has joined #openstack-meeting-4 | 08:14 | |
| yujunz | It seems we need more than a skeleton to copy | 08:14 |
| yujunz | But a generator to create one with specified name | 08:14 |
| ifat_afek | I saw you suggested a generator. any idea how it can be done? | 08:14 |
| yujunz | Maybe rendering from a jinja2 template | 08:14 |
| ifat_afek | I am not familiar with it | 08:15 |
| yujunz | vitrage-dashboard developer should be familiar with it | 08:15 |
| yujunz | Put some tags in the template and replace them with real variable value | 08:15 |
| yujunz | I'll update the details in blueprint | 08:16 |
| yujunz | The original patchset is open for comments on what should be included in the skeleton | 08:16 |
| yujunz | Next static datasource | 08:17 |
| yujunz | #link https://review.openstack.org/#/c/397494/ | 08:17 |
| ifat_afek | yujunz: how is it related to vitrage-dashboard? | 08:17 |
| alon_heller | yujunz: I am familiar with the vitrage-dashboard, but have no idea what is jinja2 | 08:17 |
| *** korzen has quit IRC | 08:18 | |
| alon_heller | Let me know how can I help | 08:18 |
| yujunz | jinja2 is the default template in django, I think | 08:18 |
| alon_heller | Our vitrage-dashboard is written with Angular, and is just a plugin in the Horizon django code | 08:19 |
| yujunz | I see | 08:19 |
| yujunz | Then it is similar to yeoman generator | 08:19 |
| yujunz | #link http://yeoman.io/ | 08:19 |
| *** oshidoshi has joined #openstack-meeting-4 | 08:20 | |
| yujunz | But not that complex | 08:20 |
| alon_heller | ok. but yeoman is usually just for bootstrap your app. You are talking about service or something, not ? | 08:20 |
| yujunz | No, we just want to create a skeleton of new data source | 08:20 |
| *** haleyb_ has quit IRC | 08:20 | |
| *** ralonsoh has joined #openstack-meeting-4 | 08:20 | |
| yujunz | So provide a group of template and render the required source file to bootstrap the creation of a new data source | 08:21 |
| ifat_afek | but how is it related to UI? | 08:21 |
| tovin07 | yujunz: Django use Django template language by default. Jinja2 is default template of Flask. | 08:21 |
| yujunz | Ah, yes | 08:21 |
| ifat_afek | do you think a new datasource can be created out of templates? isn’t it more complex than that? | 08:21 |
| yujunz | No | 08:22 |
| yujunz | A skeleton can be created from that | 08:22 |
| *** karthiks has joined #openstack-meeting-4 | 08:22 | |
| ifat_afek | and how will this skeleton be different than the one you already created? | 08:22 |
| yujunz | s/Skeleton/your_sourcename/g | 08:23 |
| yujunz | Things like that | 08:23 |
| yujunz | Save your effort from replacing every occurence of placehodler | 08:23 |
| ifat_afek | the thing is, that I don’t think the datasources code is that trivial. for example, the code of the monitors (nagios/zabbix/aodh) is very different than the code of openstack datasources (nova, cinder…) | 08:23 |
| ifat_afek | oh, this could help indeed | 08:23 |
| ifat_afek | but the implementation part will simply remain empty? | 08:24 |
| yujunz | Yes | 08:24 |
| ifat_afek | ok, sounds good | 08:24 |
| yujunz | Sorry, it sounds like something big | 08:24 |
| ifat_afek | why sorry? | 08:24 |
| *** tovin07 has quit IRC | 08:24 | |
| yujunz | Made some misunderstanding | 08:24 |
| yujunz | I mean it sounded | 08:25 |
| ifat_afek | no problem, maybe I should have waited to the blueprint to better understand | 08:25 |
| yujunz | Sure | 08:25 |
| yujunz | Next static datasource | 08:26 |
| yujunz | #link https://review.openstack.org/#/c/397494/ | 08:26 |
| yujunz | Most things have be clarified. I will move on to method implementation if no further question | 08:26 |
| ifat_afek | I just read your last comment | 08:27 |
| ifat_afek | how can the parser tell if this is an old format or a new format? | 08:27 |
| ifat_afek | if they are both on the same folder | 08:27 |
| *** dtardivel has joined #openstack-meeting-4 | 08:27 | |
| yujunz | The new format has a `meta` attribute as it is in the evaluator | 08:28 |
| ifat_afek | ok | 08:28 |
| yujunz | Next file utils | 08:28 |
| yujunz | #link https://review.openstack.org/#/c/397572/ | 08:29 |
| *** markvoelker has joined #openstack-meeting-4 | 08:29 | |
| yujunz | Any further comments? | 08:29 |
| ifat_afek | so I basically agreed with your last comment | 08:29 |
| yujunz | That's the best compromise I could think of for now | 08:29 |
| ifat_afek | alexey_weyl is on vacation, he can only see your comment on Sunday. but I think we can approve your code, and if Alexey insists we can change these two lines later | 08:30 |
| yujunz | No problem | 08:30 |
| yujunz | That's all from my side | 08:30 |
| ifat_afek | on the other hand, someone else should also +2, and I’m not sure who can do it today (like I said, many core developers are OOO) | 08:31 |
| ifat_afek | anyone else has updates? | 08:31 |
| ifat_afek | ok, I’ll update on behalf of other people… I noticed the dwj fixed a bug in ceilometer in favor of vitrage, so we will be able to parse event-alarms correctly | 08:33 |
| *** markvoelker has quit IRC | 08:34 | |
| ifat_afek | I know that eyalb is progressing with RedHat regarding the RDO specs | 08:34 |
| ifat_afek | another general issue: I assume you’ve heard about the PTG – the Project Team Gathering, AKA the design summit. It was split from the main summit, and will happen in Atlanta in February 2017. The main summit will be in Boston in May. | 08:35 |
| ifat_afek | I was asked whether the Vitrage team will join the PTG. I don’t really see a need to go. We are doing our designs using the mailing lists, gerrit and IRC, and it seems to work well. Having two days in Atlanta is not necessarily productive, plus none of us (as far as I know) comes from this area. | 08:35 |
| ifat_afek | Anyway, I’ll be happy to hear your thoughts about it. Anyone feels that we should be there? | 08:36 |
| ifat_afek | and while we were speaking, my infra change was approved. I’ll send an email once we have our docs finallized | 08:37 |
| ifat_afek | I think that’s all for now, unless anyone else has something to discuss | 08:38 |
| *** bobmel has joined #openstack-meeting-4 | 08:38 | |
| *** GB21 has quit IRC | 08:38 | |
| ifat_afek | goodbye then :-) | 08:39 |
| miani | by | 08:39 |
| *** miani has left #openstack-meeting-4 | 08:39 | |
| ifat_afek | #endmeeting | 08:39 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 08:39 | |
| openstack | Meeting ended Wed Nov 16 08:39:56 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 08:39 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-11-16-08.00.html | 08:39 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-11-16-08.00.txt | 08:40 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-11-16-08.00.log.html | 08:40 |
| *** Julien-zte has quit IRC | 08:45 | |
| *** yujunz has left #openstack-meeting-4 | 08:45 | |
| *** Julien-zte has joined #openstack-meeting-4 | 08:45 | |
| *** ohad has quit IRC | 08:47 | |
| *** janki has joined #openstack-meeting-4 | 08:50 | |
| *** GB21 has joined #openstack-meeting-4 | 08:51 | |
| *** vishnoianil has joined #openstack-meeting-4 | 08:54 | |
| *** dritto77 has joined #openstack-meeting-4 | 08:55 | |
| *** dritto77 has quit IRC | 08:55 | |
| *** dritto77 has joined #openstack-meeting-4 | 08:55 | |
| *** dritto77 has quit IRC | 08:56 | |
| *** tovin07 has joined #openstack-meeting-4 | 08:57 | |
| *** janki has quit IRC | 08:58 | |
| *** nadav has quit IRC | 09:02 | |
| *** alon_heller has quit IRC | 09:03 | |
| *** karthiks has quit IRC | 09:06 | |
| *** berendt has joined #openstack-meeting-4 | 09:14 | |
| *** karthiks has joined #openstack-meeting-4 | 09:19 | |
| *** numans has joined #openstack-meeting-4 | 09:19 | |
| *** Julien-zte has quit IRC | 09:20 | |
| *** makowals has quit IRC | 09:22 | |
| *** makowals has joined #openstack-meeting-4 | 09:22 | |
| *** tovin07 has quit IRC | 09:23 | |
| *** yfauser has joined #openstack-meeting-4 | 09:24 | |
| *** janki has joined #openstack-meeting-4 | 09:31 | |
| *** diga has joined #openstack-meeting-4 | 09:33 | |
| *** alexchadin has quit IRC | 09:35 | |
| *** alexchad_ has joined #openstack-meeting-4 | 09:35 | |
| *** janki has quit IRC | 09:35 | |
| *** matrohon has joined #openstack-meeting-4 | 09:36 | |
| *** makowals has quit IRC | 09:36 | |
| *** makowals has joined #openstack-meeting-4 | 09:36 | |
| *** sshnaidm|away is now known as sshnaidm | 09:37 | |
| *** alexchad_ is now known as alexchadin | 09:39 | |
| *** iyamahat has quit IRC | 09:39 | |
| *** khushbu has joined #openstack-meeting-4 | 09:45 | |
| *** berendt has quit IRC | 09:48 | |
| *** bogdando has quit IRC | 09:50 | |
| *** bogdando has joined #openstack-meeting-4 | 09:52 | |
| *** yamahata has joined #openstack-meeting-4 | 09:54 | |
| *** limao has quit IRC | 09:57 | |
| *** tovin07_ has quit IRC | 09:57 | |
| *** iyamahat has joined #openstack-meeting-4 | 10:00 | |
| *** zhurong has quit IRC | 10:02 | |
| *** iyamahat has quit IRC | 10:03 | |
| *** yamahata has quit IRC | 10:07 | |
| *** berendt has joined #openstack-meeting-4 | 10:10 | |
| *** alexchadin has quit IRC | 10:16 | |
| *** alexchadin has joined #openstack-meeting-4 | 10:17 | |
| *** alexchadin has quit IRC | 10:17 | |
| *** alexchadin has joined #openstack-meeting-4 | 10:17 | |
| *** alexchadin has quit IRC | 10:18 | |
| *** alexchadin has joined #openstack-meeting-4 | 10:18 | |
| *** alexchadin has quit IRC | 10:19 | |
| *** alexchadin has joined #openstack-meeting-4 | 10:19 | |
| *** alexchadin has quit IRC | 10:19 | |
| *** alexchadin has joined #openstack-meeting-4 | 10:20 | |
| *** alexchadin has quit IRC | 10:20 | |
| *** GB21 has quit IRC | 10:22 | |
| *** asettle has joined #openstack-meeting-4 | 10:23 | |
| *** atuly has joined #openstack-meeting-4 | 10:23 | |
| *** korzen has joined #openstack-meeting-4 | 10:28 | |
| *** sambetts|afk is now known as sambetts | 10:28 | |
| *** markvoelker has joined #openstack-meeting-4 | 10:30 | |
| *** alexchadin has joined #openstack-meeting-4 | 10:32 | |
| *** GB21 has joined #openstack-meeting-4 | 10:34 | |
| *** markvoelker has quit IRC | 10:35 | |
| *** alexchadin has quit IRC | 10:37 | |
| *** berendt has quit IRC | 10:40 | |
| *** yfauser has quit IRC | 10:44 | |
| *** yfauser has joined #openstack-meeting-4 | 10:45 | |
| *** vishnoianil has quit IRC | 10:48 | |
| *** omnipresent has joined #openstack-meeting-4 | 10:52 | |
| *** khushbu has quit IRC | 10:53 | |
| *** omnipresent has quit IRC | 10:57 | |
| *** zenoway has joined #openstack-meeting-4 | 11:02 | |
| *** xingchao has quit IRC | 11:05 | |
| *** xingchao has joined #openstack-meeting-4 | 11:06 | |
| *** yfauser has quit IRC | 11:12 | |
| *** xingchao has quit IRC | 11:17 | |
| *** GB21 has quit IRC | 11:18 | |
| *** atuly has quit IRC | 11:25 | |
| *** amotoki_ has joined #openstack-meeting-4 | 11:30 | |
| *** GB21 has joined #openstack-meeting-4 | 11:31 | |
| *** amotoki has quit IRC | 11:33 | |
| *** berendt has joined #openstack-meeting-4 | 11:33 | |
| *** gongysh has joined #openstack-meeting-4 | 11:36 | |
| *** gongysh has quit IRC | 11:45 | |
| *** bogdando has quit IRC | 11:55 | |
| *** bogdando has joined #openstack-meeting-4 | 11:57 | |
| *** reedip_ has joined #openstack-meeting-4 | 11:58 | |
| *** zenoway has quit IRC | 11:59 | |
| *** zenoway has joined #openstack-meeting-4 | 11:59 | |
| *** korzen has quit IRC | 12:02 | |
| *** xingchao has joined #openstack-meeting-4 | 12:02 | |
| *** korzen has joined #openstack-meeting-4 | 12:03 | |
| *** zenoway has quit IRC | 12:04 | |
| *** zenoway has joined #openstack-meeting-4 | 12:07 | |
| *** coolsvap is now known as coolsvap_ | 12:09 | |
| *** yfauser has joined #openstack-meeting-4 | 12:14 | |
| *** yfauser has quit IRC | 12:15 | |
| *** yfauser has joined #openstack-meeting-4 | 12:15 | |
| *** GB21 has quit IRC | 12:22 | |
| *** yfauser has quit IRC | 12:25 | |
| *** berendt has quit IRC | 12:26 | |
| *** rtheis has joined #openstack-meeting-4 | 12:34 | |
| *** ifat_afek has left #openstack-meeting-4 | 12:34 | |
| *** zhurong has joined #openstack-meeting-4 | 12:35 | |
| *** reedip_ has quit IRC | 12:39 | |
| *** irenab has joined #openstack-meeting-4 | 12:39 | |
| *** berendt has joined #openstack-meeting-4 | 12:40 | |
| *** khushbu_ has joined #openstack-meeting-4 | 12:42 | |
| *** gmann_ has joined #openstack-meeting-4 | 12:44 | |
| *** irenab has quit IRC | 12:44 | |
| *** berendt has quit IRC | 12:45 | |
| *** xingchao has quit IRC | 12:49 | |
| *** khushbu_ has quit IRC | 12:49 | |
| *** jichen has joined #openstack-meeting-4 | 12:53 | |
| *** thorst_ has joined #openstack-meeting-4 | 12:53 | |
| *** sdake has joined #openstack-meeting-4 | 12:53 | |
| *** thorst_ has quit IRC | 12:54 | |
| *** thorst_ has joined #openstack-meeting-4 | 12:54 | |
| *** reedip_ has joined #openstack-meeting-4 | 12:55 | |
| *** korzen has quit IRC | 12:58 | |
| *** diga has quit IRC | 12:58 | |
| * johnthetubaguy goes to grab a coffee | 12:59 | |
| alex_xu | johnthetubaguy: :) | 12:59 |
| alex_xu | #startmeeting nova api | 12:59 |
| openstack | Meeting started Wed Nov 16 12:59:57 2016 UTC and is due to finish in 60 minutes. The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot. | 12:59 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 12:59 |
| *** openstack changes topic to " (Meeting topic: nova api)" | 13:00 | |
| openstack | The meeting name has been set to 'nova_api' | 13:00 |
| alex_xu | who is here today? | 13:00 |
| gmann_ | o/ | 13:00 |
| Kevin_Zheng | o/ | 13:00 |
| *** cdent has joined #openstack-meeting-4 | 13:00 | |
| cdent | o/ | 13:00 |
| alex_xu | let us wait one more minute for johnthetubaguy get a coffee :) | 13:00 |
| johnthetubaguy | ah, I meant don't wait will be back in a sec | 13:01 |
| johnthetubaguy | 0/ | 13:01 |
| jichen | o/ | 13:01 |
| alex_xu | hehe | 13:01 |
| alex_xu | let me whether we have action from previous | 13:01 |
| *** seanmurphy has joined #openstack-meeting-4 | 13:02 | |
| alex_xu | no action from previous | 13:02 |
| alex_xu | #topic priority task | 13:02 |
| *** openstack changes topic to "priority task (Meeting topic: nova api)" | 13:02 | |
| gmann_ | :) | 13:02 |
| alex_xu | #link https://review.openstack.org/388518 | 13:02 |
| alex_xu | ^ thanks cdent point it out actually we can validate single value with max length of list. So I changed the spec, it makes the json-schema simpler | 13:03 |
| alex_xu | avoid to use 'oneOf' | 13:03 |
| alex_xu | but we need use 'array' for all the parameters, but it still looks simper than 'oneOf' | 13:04 |
| alex_xu | #link https://review.openstack.org/#/c/388518/11/specs/ocata/approved/consistent-query-parameters-validation.rst@96 | 13:04 |
| *** bobh has joined #openstack-meeting-4 | 13:04 | |
| alex_xu | ^ you guys can find out the example from the link | 13:04 |
| johnthetubaguy | yeah, just been looking at that, very cunning | 13:04 |
| johnthetubaguy | so in the conversion of the query string params, if its not a list, we add it as an item of one in a list? | 13:05 |
| *** claudiub has joined #openstack-meeting-4 | 13:05 | |
| alex_xu | johnthetubaguy: yes | 13:05 |
| *** sdake_ has joined #openstack-meeting-4 | 13:05 | |
| alex_xu | at line 87, there is example | 13:05 |
| johnthetubaguy | alex_xu: did you mean to delete line 118? | 13:05 |
| johnthetubaguy | oh, I see, keep the utils | 13:05 |
| alex_xu | johnthetubaguy: no, still want to keep them | 13:05 |
| alex_xu | yea | 13:06 |
| alex_xu | I will update the poc later | 13:06 |
| gmann_ | alex_xu: you mean that solve the multiple occurrence of same param thing ? | 13:06 |
| gmann_ | or something else | 13:06 |
| alex_xu | gmann_: yea | 13:07 |
| alex_xu | gmann_: for the case name=abc&name=def | 13:07 |
| gmann_ | alex_xu: but i thought oneOf was only needed for sort_key only | 13:07 |
| alex_xu | gmann_: with new way, we needn't oneOf anymore | 13:08 |
| *** sdake has quit IRC | 13:08 | |
| *** kylek3h has quit IRC | 13:09 | |
| *** kylek3h has joined #openstack-meeting-4 | 13:09 | |
| alex_xu | gmann_: for multiple value, it is array. for single value, it is array limit maxItems=1 | 13:09 |
| gmann_ | alex_xu: but still it would not restrict name=abd&name=def right? | 13:09 |
| gmann_ | alex_xu: ohk, you will parse as list, got it | 13:09 |
| alex_xu | gmann_: yea, we won't for now. | 13:10 |
| alex_xu | so the second spec | 13:10 |
| johnthetubaguy | one sec | 13:10 |
| alex_xu | #link https://review.openstack.org/393205 | 13:10 |
| alex_xu | oops | 13:10 |
| alex_xu | johnthetubaguy: go ahead | 13:10 |
| *** prateek has quit IRC | 13:10 | |
| johnthetubaguy | there was a note about allowing multiple values for a single one | 13:10 |
| johnthetubaguy | like foo=bar,foo=baz | 13:10 |
| johnthetubaguy | today we just pick one of them, or something? | 13:10 |
| gmann_ | alex_xu: so we will be parsing all query params into list and then schema can handle | 13:11 |
| alex_xu | gmann_: yes | 13:11 |
| alex_xu | johnthetubaguy: yes | 13:11 |
| gmann_ | johnthetubaguy: yea json schema just pick one but that same case for request body validation also | 13:11 |
| johnthetubaguy | I was thinking about this bit: https://review.openstack.org/#/c/388518/11/specs/ocata/approved/consistent-query-parameters-validation.rst@193 | 13:11 |
| alex_xu | we just pick oen of them | 13:11 |
| johnthetubaguy | oh, do you have an example of that? | 13:12 |
| alex_xu | yea, that thanks to gmann_ point it out | 13:12 |
| *** acabot_ has joined #openstack-meeting-4 | 13:12 | |
| alex_xu | for example, change-since accept a datefomart | 13:12 |
| gmann_ | johnthetubaguy: if you run create server tests with 2 name there 1 invalid, still pass | 13:12 |
| johnthetubaguy | so you could have multiples in the body | 13:13 |
| johnthetubaguy | I am thinking about keypairs I guess | 13:13 |
| johnthetubaguy | like this one: | 13:13 |
| johnthetubaguy | https://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/keypairs.py#n122 | 13:13 |
| johnthetubaguy | it seems that would only deal if there was a single type parameter | 13:13 |
| *** kylek3h has quit IRC | 13:13 | |
| johnthetubaguy | oops | 13:14 |
| johnthetubaguy | thats the body | 13:14 |
| alex_xu | johnthetubaguy: there are multiple value the user put in the url. Then all the values pass into the nova api python code. | 13:14 |
| alex_xu | The python code only will pick one of them(probably the last one I guess), then validate it | 13:14 |
| johnthetubaguy | I thinking we have ?user_id=2,user_id=3 | 13:15 |
| gmann_ | yea | 13:15 |
| johnthetubaguy | is it the routing code that hides that? | 13:15 |
| alex_xu | maybe other value are invalid, only the last one is valid, the request still can pass the validation | 13:15 |
| gmann_ | and json schema pick either which is valid | 13:15 |
| johnthetubaguy | so once we have strict validation, that would be invalid, it has to pass if it works today | 13:15 |
| *** asettle__ has joined #openstack-meeting-4 | 13:15 | |
| johnthetubaguy | so agreed with the approch | 13:16 |
| alex_xu | But with the new proposal, the json-schema will validate all the input value even the python code only pick the last one | 13:16 |
| gmann_ | johnthetubaguy: alex_xu i simply ran functional tests with 2 name(1 valid) and API did not complain. json schema picked valid one and ignore invalid one | 13:16 |
| johnthetubaguy | yes, that seems correct, longer term | 13:16 |
| gmann_ | alex_xu: 1 sec | 13:16 |
| johnthetubaguy | I am worried more about the query string params, I thought name was a body param? | 13:17 |
| gmann_ | alex_xu: i thought it will pick both and make list where json schema will 400 as maxItem is 1 | 13:17 |
| johnthetubaguy | for json, I believe the last one in the document wins | 13:17 |
| johnthetubaguy | although its a shame we don't call that invalid | 13:17 |
| alex_xu | johnthetubaguy: it isn't longer term, the json-schema will validate all the values for any request | 13:17 |
| johnthetubaguy | sorry, I am crossing the streams/wires here | 13:18 |
| gmann_ | johnthetubaguy: even it can pick first one in case second one is invalid | 13:18 |
| johnthetubaguy | I am trying to see how the current code accepts multiple and ignores one today, for the keypairs API | 13:18 |
| *** asettle has quit IRC | 13:18 | |
| johnthetubaguy | just the query strings for now | 13:19 |
| *** reedip_ has quit IRC | 13:19 | |
| *** Julien-zte has joined #openstack-meeting-4 | 13:19 | |
| alex_xu | emm...sorry, I lost the context also :( | 13:20 |
| gmann_ | alex_xu: last query- so in this spec, if user out multiple value for example for name (name=abc&name-def) it will 400 right. | 13:20 |
| gmann_ | out->put | 13:20 |
| gmann_ | as we are making list for each param and passing to json schema | 13:21 |
| alex_xu | gmann_: do you mean the spec https://review.openstack.org/393205, it won't, just ignore one of them | 13:21 |
| johnthetubaguy | so lets back up | 13:21 |
| johnthetubaguy | I think we should focus on the real api, keypairs | 13:21 |
| johnthetubaguy | thats what the spec is modifying | 13:22 |
| alex_xu | yea | 13:22 |
| gmann_ | alex_xu: no this one - https://review.openstack.org/#/c/388518/11/specs/ocata/approved/consistent-query-parameters-validation.rst@193 | 13:22 |
| johnthetubaguy | so I am trying to work out what happens today with the user param | 13:22 |
| johnthetubaguy | I guess this bit: | 13:23 |
| johnthetubaguy | https://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/keypairs.py#n185 | 13:23 |
| *** lamt has joined #openstack-meeting-4 | 13:23 | |
| johnthetubaguy | I was going blind but I see it now | 13:23 |
| alex_xu | gmann_: that spec only describe the new mechanism, whether we return 400, depend the schema | 13:23 |
| *** atuly has joined #openstack-meeting-4 | 13:24 | |
| *** bobh has quit IRC | 13:24 | |
| gmann_ | alex_xu: yea | 13:24 |
| alex_xu | johnthetubaguy: it only take one of them | 13:24 |
| gmann_ | johnthetubaguy: yea | 13:25 |
| *** asettle__ is now known as asettle | 13:25 | |
| *** dave-mccowan has joined #openstack-meeting-4 | 13:25 | |
| alex_xu | johnthetubaguy: so.... | 13:27 |
| johnthetubaguy | in the distant future, when additional_properties = False | 13:27 |
| johnthetubaguy | we would want user_id=1&user_id=2 to fail | 13:27 |
| johnthetubaguy | right now we just pick the first one | 13:27 |
| johnthetubaguy | it feels like we need to preserve that | 13:27 |
| johnthetubaguy | for the moment | 13:27 |
| johnthetubaguy | the spec says that, I believe? | 13:27 |
| johnthetubaguy | I was unclear... | 13:27 |
| johnthetubaguy | need to keep the same API semantics, so we will not be as strict as we could be about duplicates | 13:27 |
| johnthetubaguy | now, we have a few options for the validation | 13:27 |
| johnthetubaguy | 1) reject the request with duplicates, long term, we probably want that | 13:27 |
| johnthetubaguy | 2) only validate the element the code will touch | 13:27 |
| *** reedip_ has joined #openstack-meeting-4 | 13:27 | |
| *** oshidoshi has quit IRC | 13:27 | |
| *** GB21 has joined #openstack-meeting-4 | 13:27 | |
| alex_xu | oops, I have network delay | 13:28 |
| cdent | I thought the point of putting this stuff under a microversio was so that we _don't_ need to preserve the old ambiguous behavior? | 13:28 |
| gmann_ | but duplicates were just being not taken care, should give 400 | 13:29 |
| gmann_ | which is broken as of now | 13:29 |
| gmann_ | as that was a good example of bad usage | 13:29 |
| johnthetubaguy | cdent: so step one is don't break what we have, just protect us against bad stuff, step 2 is make it better | 13:30 |
| johnthetubaguy | at least thats what I have in my head | 13:30 |
| johnthetubaguy | basically like 2.0 vs 2.1 and the body validation | 13:31 |
| alex_xu | emm...+1 for don't break what we have now | 13:31 |
| *** haleyb_ has joined #openstack-meeting-4 | 13:31 | |
| johnthetubaguy | so you said the validation only takes one of them? | 13:31 |
| johnthetubaguy | I thought it would get passed the full list of params | 13:31 |
| alex_xu | johnthetubaguy: with current proposal, it would get passed the full list of params | 13:32 |
| johnthetubaguy | yep, I am fine with that | 13:32 |
| gmann_ | alex_xu: and 400 for duplicate case | 13:32 |
| johnthetubaguy | well, that breaks the existing requests, that would need a new microversion | 13:33 |
| alex_xu | yea | 13:33 |
| gmann_ | johnthetubaguy: even that usage was not right | 13:33 |
| * alex_xu should put a real example in the REST API impact section | 13:34 | |
| gmann_ | alex_xu: but this will return 400 -https://review.openstack.org/#/c/388518/11/specs/ocata/approved/consistent-query-parameters-validation.rst@102 | 13:34 |
| gmann_ | alex_xu: in current spec | 13:34 |
| gmann_ | so if duplicate value then json object from query param will be like 'name': ['abc', def], | 13:35 |
| johnthetubaguy | which we should totally do at some point, but is not proposed in the current spec (its mentioned as future work) | 13:35 |
| alex_xu | gmann_: maybe I didn't clear about that. It is only an example to show how the new mechanism works, it didn't talk about the real would | 13:35 |
| johnthetubaguy | alex_xu: +1, I think your proposals is good, if I understand it now, but an example would really help | 13:35 |
| *** amotoki_ has quit IRC | 13:36 | |
| gmann_ | yea that was my assumption but examle seems retricted those | 13:36 |
| gmann_ | alex_xu: because maxItems in example makes 400 for duplicate | 13:37 |
| alex_xu | gmann_: I would try to add note clarify that | 13:37 |
| gmann_ | alex_xu: Thanks | 13:37 |
| alex_xu | gmann_: emm....forget that one, this spec is about the real world https://review.openstack.org/393205 :) | 13:37 |
| gmann_ | :) | 13:37 |
| * johnthetubaguy hmm, I think I am seeing network delays somwhere now | 13:38 | |
| alex_xu | I will upda the spec after the meeting, one note for the example, and put a real world example for the thing in the rest api impact section | 13:39 |
| alex_xu | s/upda/update/ | 13:39 |
| alex_xu | so, are we good for the base spec one? let us talk about the second one? | 13:39 |
| *** gmann__ has joined #openstack-meeting-4 | 13:40 | |
| *** korzen has joined #openstack-meeting-4 | 13:40 | |
| alex_xu | I guess i'm waiting for the network delays now :) | 13:41 |
| johnthetubaguy | yeah, lets talk second one | 13:41 |
| alex_xu | #link https://review.openstack.org/393205 | 13:41 |
| gmann__ | yea, sorry got disconnected | 13:41 |
| gmann__ | for me this looks fine, just version bump needs to be more clear | 13:41 |
| alex_xu | gmann__: no worries, you didn't miss anything :) | 13:41 |
| *** kylek3h has joined #openstack-meeting-4 | 13:42 | |
| gmann__ | oh :) | 13:42 |
| gmann__ | alex_xu: johnthetubaguy so that is version bump plan what i stated in comment ? | 13:42 |
| alex_xu | gmann__: so...no version bump at here | 13:42 |
| *** gmann_ has quit IRC | 13:42 | |
| gmann__ | alex_xu: yes, and in future we bump when we will reject invalid filter | 13:43 |
| johnthetubaguy | yeah, the spec says there is a version bump, I thought we were going to not do that for the moment | 13:43 |
| alex_xu | gmann__: yea | 13:43 |
| alex_xu | oops, just found that | 13:43 |
| alex_xu | that is wrong | 13:43 |
| gmann__ | yea just ignore for invalid filter and 400 for invalid sort_key | 13:43 |
| johnthetubaguy | so lets go back to why | 13:44 |
| *** markvoelker has joined #openstack-meeting-4 | 13:44 | |
| johnthetubaguy | existing requests that worked in the past should be accepted | 13:44 |
| gmann__ | +1 | 13:44 |
| johnthetubaguy | bad requests that were dangerous need to be made "safe" | 13:44 |
| johnthetubaguy | so the 500 errors can go to 400 errors | 13:44 |
| johnthetubaguy | the ignore unknown keys seems to be the best approach | 13:45 |
| johnthetubaguy | and fail with invalid values for know keys | 13:45 |
| gmann__ | johnthetubaguy: for sort_key also ? | 13:45 |
| johnthetubaguy | should be the same for both I think | 13:45 |
| johnthetubaguy | they are both "dangerous" in some sense | 13:46 |
| gmann__ | johnthetubaguy: i mean if any other key than whitelist for sort_key | 13:46 |
| gmann__ | johnthetubaguy: yea | 13:46 |
| gmann__ | totally agree with approach. | 13:46 |
| johnthetubaguy | sorry, I get what you mean now | 13:46 |
| johnthetubaguy | the filters are all different keys | 13:46 |
| johnthetubaguy | but the sort thing is a value | 13:46 |
| gmann__ | yea | 13:47 |
| johnthetubaguy | so it will trigger 400 errors | 13:47 |
| johnthetubaguy | thats annoying, but its consistent | 13:47 |
| *** woodard has quit IRC | 13:47 | |
| johnthetubaguy | we support multiple sort keys? | 13:47 |
| gmann__ | yea invalid value gives 400 | 13:48 |
| alex_xu | yes | 13:48 |
| *** woodard has joined #openstack-meeting-4 | 13:48 | |
| alex_xu | yes for multiple sort keys | 13:48 |
| gmann__ | L88 says sort key not sort_key's value :) | 13:48 |
| alex_xu | "so the 500 errors can go to 400 errors": for the filters, it go to ignore, not 400 | 13:48 |
| alex_xu | or you want that go to 400? | 13:49 |
| johnthetubaguy | so it gets tricky | 13:49 |
| johnthetubaguy | we could have a *these are bad* list, and reject those, but ignore unknown values, but that seems like a mess | 13:50 |
| gmann__ | ah, yea | 13:50 |
| johnthetubaguy | I think I am OK with filters we don't know, just getting the standard ignore unknown key treatment for now | 13:50 |
| alex_xu | if user use that bad key, that means the bad request will break their client code? | 13:51 |
| johnthetubaguy | right, hence the ignore / strip approach | 13:52 |
| *** liuyulong_ has joined #openstack-meeting-4 | 13:52 | |
| gmann__ | alex_xu: but current code ignore that right? for admin (as we have only non-admin list in code) | 13:52 |
| *** rtheis has quit IRC | 13:52 | |
| johnthetubaguy | operator feedback on the restriction is probably a good idea, but I am not sure what we do if they don't like it | 13:53 |
| alex_xu | gmann__: I thought the "bad" point to the joined table and column without index | 13:53 |
| gmann__ | for me too, ignore/strip approach is more better way to go | 13:53 |
| johnthetubaguy | going back to that, we seem to be back to having a massive list in the spec | 13:54 |
| *** liuyulong__ has quit IRC | 13:55 | |
| *** exploreshaifali has joined #openstack-meeting-4 | 13:55 | |
| *** rtheis has joined #openstack-meeting-4 | 13:55 | |
| alex_xu | ok, so we continue shrik the list | 13:56 |
| alex_xu | 4 mins left for us | 13:56 |
| johnthetubaguy | well, we need it to match what we have indexed | 13:56 |
| johnthetubaguy | I believe thats the aim | 13:56 |
| johnthetubaguy | that might involve adding an index or two, if we really want to keep some | 13:56 |
| alex_xu | ok | 13:57 |
| gmann__ | humm | 13:57 |
| alex_xu | Kevin_Zheng: is the currently all the proposal filter/sort includes index? | 13:58 |
| Kevin_Zheng | no | 13:58 |
| johnthetubaguy | I am just checking, we are missing loads of them | 13:58 |
| johnthetubaguy | https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/models.py#L196 | 13:58 |
| johnthetubaguy | note that users filter for deleted=false, hence the compound index | 13:58 |
| *** licanwei has joined #openstack-meeting-4 | 13:59 | |
| Kevin_Zheng | some useful fields missing indexes | 13:59 |
| Kevin_Zheng | like user_id | 13:59 |
| *** pshedimb has joined #openstack-meeting-4 | 13:59 | |
| Kevin_Zheng | pretty common to filter by user | 13:59 |
| alex_xu | it's time to close, we should move back to #openstack-nova | 13:59 |
| *** amotoki has joined #openstack-meeting-4 | 13:59 | |
| *** vincentfrancoise has joined #openstack-meeting-4 | 14:00 | |
| alex_xu | #endmeeting | 14:00 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 14:00 | |
| openstack | Meeting ended Wed Nov 16 14:00:07 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:00 |
| alex_xu | thanks all! | 14:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-11-16-12.59.html | 14:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-11-16-12.59.txt | 14:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-11-16-12.59.log.html | 14:00 |
| acabot_ | #startmeeting watcher | 14:00 |
| openstack | Meeting started Wed Nov 16 14:00:29 2016 UTC and is due to finish in 60 minutes. The chair is acabot_. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
| *** openstack changes topic to " (Meeting topic: watcher)" | 14:00 | |
| openstack | The meeting name has been set to 'watcher' | 14:00 |
| acabot_ | o/ | 14:00 |
| *** brunograz has joined #openstack-meeting-4 | 14:00 | |
| sballe_ | ji | 14:00 |
| vincentfrancoise | o/ | 14:00 |
| sballe_ | hi | 14:00 |
| dtardivel | hello | 14:00 |
| brunograz | o/ | 14:00 |
| hvprash_ | hi | 14:01 |
| licanwei | hi | 14:01 |
| exploreshaifali | \o | 14:01 |
| *** reedip_ has quit IRC | 14:01 | |
| pshedimb | hi | 14:01 |
| acabot_ | agenda for today #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#11.2F16.2F2016 | 14:01 |
| acabot_ | #topic Announcements | 14:02 |
| *** openstack changes topic to "Announcements (Meeting topic: watcher)" | 14:02 | |
| *** cdent has left #openstack-meeting-4 | 14:02 | |
| acabot_ | #info We should send a recap of discussions in Barcelona on the ML | 14:02 |
| acabot_ | sballe_ : I dont know if you have seen this action from last meeting | 14:02 |
| acabot_ | I suggested to send a recap of Watcher sessions in Barcelona but as I was not there I'm probably not the best person to do it ;-) | 14:03 |
| sballe_ | no I forgot. But I do want you guys to welcome the two new intel developers to watcher | 14:03 |
| sballe_ | pshedimb: welcome | 14:03 |
| sballe_ | I am not sure what chris' irc nickname is | 14:03 |
| *** korzen has quit IRC | 14:04 | |
| acabot_ | sballe_ : welcome !!! | 14:04 |
| vincentfrancoise | pshedimb: Welcome on board! | 14:04 |
| sballe_ | edwin will be fading out of watcher and moving to a different project. | 14:04 |
| sballe_ | pshedimb: and chris are located int he US | 14:04 |
| vincentfrancoise | sballe_: there is a chrisspencer on #openstack-watcher: is it him? | 14:04 |
| sballe_ | yes | 14:04 |
| pshedimb | thanks you :) | 14:05 |
| *** liuyulong_ has quit IRC | 14:05 | |
| hvprash_ | welcome pshedimb ! | 14:05 |
| vincentfrancoise | sballe_: nice! | 14:05 |
| acabot_ | pshedimb & chrisspencer : welcome on board ! | 14:05 |
| hvprash_ | welcome chrisspencer ! | 14:05 |
| *** liuyulong_ has joined #openstack-meeting-4 | 14:05 | |
| exploreshaifali | welcome psachin, cholcombe :) | 14:06 |
| *** pmesserli has joined #openstack-meeting-4 | 14:06 | |
| *** bobh has joined #openstack-meeting-4 | 14:06 | |
| acabot_ | sballe_ : sorry but we have many subjects to discuss today so I'm moving on, could you send the recap on the ML ? | 14:06 |
| sballe_ | yes will do | 14:06 |
| acabot_ | #action sballe_ send a recap of watcher sessions on the ML | 14:07 |
| acabot_ | #info We will start a thread on the ML to discuss the way we can test available strategies | 14:07 |
| acabot_ | dtardivel : can you handle it ? | 14:07 |
| sballe_ | love it. that is definetly neede | 14:07 |
| dtardivel | acabot_: I sent an email this morning | 14:08 |
| acabot_ | ok sorry I missed it ;-) | 14:09 |
| *** gmann__ has quit IRC | 14:09 | |
| acabot_ | #topic Review Action Items | 14:09 |
| *** openstack changes topic to "Review Action Items (Meeting topic: watcher)" | 14:09 | |
| acabot_ | Watcher specs | 14:09 |
| acabot_ | #info team priorities for Ocata have been merged | 14:09 |
| acabot_ | #link http://specs.openstack.org/openstack/watcher-specs/priorities/ocata-priorities.html | 14:09 |
| acabot_ | scale out or delete instance based on workload should be abandonned | 14:09 |
| acabot_ | #link https://review.openstack.org/#/c/359690/ | 14:09 |
| acabot_ | licanwei : can you do it on behalf on jinquan ? | 14:10 |
| licanwei | yunmeng do it | 14:10 |
| acabot_ | licanwei : by the way is jinquan back on the project ? | 14:10 |
| *** bobh has quit IRC | 14:11 | |
| licanwei | maybe not | 14:11 |
| acabot_ | #action yunmeng abandon the spec https://review.openstack.org/#/c/359690/ | 14:11 |
| acabot_ | licanwei : ok | 14:11 |
| *** rtheis_ has joined #openstack-meeting-4 | 14:11 | |
| acabot_ | automatic triggering of action plans for AUDIT should now be reviewed and merged | 14:11 |
| acabot_ | #link https://review.openstack.org/#/c/342473/ | 14:11 |
| acabot_ | alexchadin took this bp as diga was not there | 14:12 |
| *** rtheis has quit IRC | 14:12 | |
| acabot_ | sballe_ : can you do a final review on https://review.openstack.org/#/c/342473/ ? | 14:12 |
| vincentfrancoise | acabot_: diga started to implement something about it | 14:12 |
| sballe_ | sure | 14:12 |
| *** baoli has joined #openstack-meeting-4 | 14:13 | |
| acabot_ | or hvprash_ | 14:13 |
| *** klamath has joined #openstack-meeting-4 | 14:13 | |
| hvprash_ | yes acabot_. have some clarifications on that BP which may have some dependency with audit tag | 14:13 |
| acabot_ | vincentfrancoise : I saw it right before the meeting, not sure it fit the spec | 14:13 |
| acabot_ | #action acabot_ sballe_ hvprash_ review and merge https://review.openstack.org/#/c/342473/ | 14:14 |
| acabot_ | Specs for watcher-versioned-objects must be merged as code has already been merged | 14:14 |
| vincentfrancoise | acabot_: yes, it's clearly not enough to fully implement what was said in the specs | 14:14 |
| acabot_ | #link https://review.openstack.org/#/c/383718/ | 14:14 |
| acabot_ | again hvprash_ & sballe_ could you please +2 +1 this spec ? | 14:14 |
| *** baoli has quit IRC | 14:14 | |
| sballe_ | definetly | 14:14 |
| hvprash_ | yes | 14:14 |
| vincentfrancoise | acabot_: it's just that I don't know if it's alexchadin or diga that is supposed to work on it at the moment | 14:15 |
| acabot_ | this code will be released tomorrow so please do it today | 14:15 |
| sballe_ | ok | 14:15 |
| *** reedip_ has joined #openstack-meeting-4 | 14:15 | |
| acabot_ | #action sballe_ hvprash_ review and merge https://review.openstack.org/#/c/383718/ today | 14:15 |
| *** baoli has joined #openstack-meeting-4 | 14:15 | |
| acabot_ | Specs for audit-versioned-notifications-api needs final reviews from core | 14:15 |
| vincentfrancoise | sballe_: the code is already merged anyway | 14:15 |
| acabot_ | #link https://review.openstack.org/#/c/385077/ | 14:15 |
| acabot_ | code will be merged today so we need to merge it as well | 14:16 |
| sballe_ | ok | 14:16 |
| acabot_ | #action acabot_ sballe_ hvprash_ review & merge https://review.openstack.org/#/c/385077/ today | 14:16 |
| acabot_ | Define grammar for workload characterization needs reviews | 14:16 |
| acabot_ | #link https://review.openstack.org/#/c/377100/ | 14:16 |
| acabot_ | hvprash_ : can we continue reviewing it ? | 14:17 |
| hvprash_ | thanks sballe_ for reviewing. will add the job priority to the characterization. others review too | 14:17 |
| acabot_ | I will | 14:17 |
| hvprash_ | yes acabot_ pls continue reviewing | 14:17 |
| acabot_ | #action acabot review https://review.openstack.org/#/c/377100/ | 14:17 |
| *** prateek has joined #openstack-meeting-4 | 14:17 | |
| acabot_ | Define when an action plan is stale/invalid needs discussions | 14:17 |
| acabot_ | #link https://review.openstack.org/#/c/386293/ | 14:18 |
| sballe_ | are we not discussing the QoS BP? | 14:18 |
| acabot_ | licanwei : you sent me an email about brunograz comments, I'm sorry I didn't had time to go trough them | 14:18 |
| *** baoli_ has joined #openstack-meeting-4 | 14:18 | |
| acabot_ | sballe_ : link ? | 14:18 |
| sballe_ | Workload Characterization and QoS needs to be assigned to me. I already changed the BP.We submitted a new Blueprint which is a sub-task of: https://blueprints.launchpad.net/watcher/+spec/workload-characterization-qoshttps://blueprints.launchpad.net/watcher/+spec/cache-occupancy-strategySpec is here: https://review.openstack.org/#/c/398162/1 | 14:19 |
| sballe_ | https://usercontent.irccloud-cdn.com/file/M2FRZ3ae/ | 14:19 |
| licanwei | acabot: i need your suggest | 14:19 |
| sballe_ | these where my updates | 14:19 |
| sballe_ | sorry for the weird format | 14:19 |
| sballe_ | Should I just change the ownership to me in the priorities? | 14:19 |
| acabot_ | no its in the agenda | 14:19 |
| acabot_ | just wait | 14:20 |
| sballe_ | ok we can talk afterwards on how to get all this done | 14:20 |
| acabot_ | licanwei : I will review it tomorrow | 14:20 |
| licanwei | acabot: ok,thanks | 14:20 |
| acabot_ | #action acabot review https://review.openstack.org/#/c/386293/ | 14:20 |
| acabot_ | Audit tag in VM Metadata needs a jenkins fix & reviews | 14:20 |
| acabot_ | #link https://review.openstack.org/#/c/391374/ | 14:21 |
| *** baoli has quit IRC | 14:21 | |
| acabot_ | hvprash_ : could you fix it ? | 14:21 |
| sballe_ | i will review | 14:21 |
| *** tonytan4ever has joined #openstack-meeting-4 | 14:21 | |
| hvprash_ | i need to do a PS. also, have some clarifications on implementing this feature. Either acabot_ vincent or jed could help me on this | 14:21 |
| acabot_ | #action sballe_ review https://review.openstack.org/#/c/391374/ | 14:21 |
| vincentfrancoise | acabot_: I will review it too | 14:21 |
| acabot_ | #action acabot_ vincentfrancoise review https://review.openstack.org/#/c/391374/ | 14:22 |
| acabot_ | Add improvements to the planner and workflow mechanisms needs reviews | 14:22 |
| acabot_ | #link https://review.openstack.org/#/c/385871/ | 14:22 |
| acabot_ | we are thinking of splitting this BP in 2 but it needs to be discussed with alexchadin | 14:23 |
| acabot_ | #action acabot_ alexchadin discuss BP split for https://review.openstack.org/#/c/385871/ | 14:23 |
| *** lamt has quit IRC | 14:23 | |
| acabot_ | Add specs for cache occupancy strategy needs discussions | 14:23 |
| acabot_ | #link https://review.openstack.org/#/c/398162/ | 14:24 |
| sballe_ | ok now is the time | 14:24 |
| acabot_ | sballe_ : yes ;-) | 14:24 |
| sballe_ | theworkload charcatrization needs to be assignd to me insead of hvprash_ | 14:24 |
| acabot_ | its great to have a new strategy but if edwin leaves the project, who will work on it ? | 14:24 |
| sballe_ | We submitted a new Blueprint which is a sub-task of: https://blueprints.launchpad.net/watcher/+spec/workload-characterization-qoshttps://blueprints.launchpad.net/watcher/+spec/cache-occupancy-strategySpec is here: https://review.openstack.org/#/c/398162/1 https://usercontent.irccloud-cdn.com/file/R7bYxzNX/ | 14:24 |
| sballe_ | pru and chris and I will work on this. | 14:25 |
| hvprash_ | sballe_, you mean workload characterization qos | 14:25 |
| acabot_ | sballe_ : https://blueprints.launchpad.net/watcher/+spec/workload-characterization-qos assigned to you already | 14:25 |
| sballe_ | yes We have done some design and the way to get to the qos functionality we need is by dividing up that bp into smaller ones | 14:25 |
| hvprash_ | yeah, i think I already assigned to you :) | 14:26 |
| acabot_ | I would suggest that pru & chris work on the framework instead of a strategy if they want to start with watcher | 14:26 |
| *** uxdanielle has joined #openstack-meeting-4 | 14:26 | |
| sballe_ | yes the BP and I will change it in hte ocata priotities | 14:26 |
| sballe_ | acabot_: not an option at this point. | 14:27 |
| sballe_ | the RDT integration is Intel's highest priotity | 14:27 |
| acabot_ | sballe_ : we really need more code reviewers on the framework | 14:27 |
| sballe_ | acabot_: they can review code. | 14:27 |
| acabot_ | sballe_ : I dont think they will review code from the framework if they dont work on it... | 14:28 |
| acabot_ | sballe_ : just guessing | 14:28 |
| acabot_ | sballe_ : but ok if its Intel priority, when do you plan to have this strategy implemented ? ocata-2 , 3 ? | 14:28 |
| sballe_ | let's talk but for now pru or chris will work on moving forward the Intel RDT integration. We could look at some low hanging task for them to work on too | 14:29 |
| *** woodard has quit IRC | 14:29 | |
| sballe_ | ocata-3 | 14:29 |
| acabot_ | ok thx | 14:29 |
| exploreshaifali | low_hanging tasks for me too | 14:29 |
| acabot_ | can we start reviewing the spec from edwin ? | 14:29 |
| vincentfrancoise | there's the config BP that can be done as a starter | 14:29 |
| acabot_ | https://blueprints.launchpad.net/watcher/+spec/centralise-config-opts | 14:30 |
| sballe_ | no it is not ready yet. give it a week and you can review | 14:30 |
| *** dave-mccowan has quit IRC | 14:30 | |
| hvprash_ | sorry, forgot about exploreshaifali. she will be working on some of my BPs | 14:30 |
| exploreshaifali | I am trying to understand the code of watcher, to contribute ahead | 14:30 |
| hvprash_ | yeah, some low hanging will help exploreshaifali to catch up too | 14:30 |
| vincentfrancoise | I already did the base so it will be easier to finish the job without having to start fresh on it | 14:30 |
| sballe_ | same with pshedimb and Chrisspencer | 14:31 |
| acabot_ | ok lets move to Wathcher code base | 14:31 |
| acabot_ | Documentation for workload stabilization [1] & workload consolidation [2] have been merged | 14:31 |
| *** amotoki_ has joined #openstack-meeting-4 | 14:31 | |
| acabot_ | thx alexchadin & brunograz for handling it | 14:31 |
| acabot_ | Documentation for Outlet Temperature Based Strategy need a new PS and reviews | 14:31 |
| sballe_ | I am working on the 3 intel ones. Waiting for some info around version of node manager | 14:31 |
| acabot_ | #link https://review.openstack.org/#/c/397411/ | 14:31 |
| acabot_ | sballe_ : ok cool as you have set W-1 I suppose you dont need review yet | 14:32 |
| dtardivel | acabot_: FYI, a new section named 'algorithm' has been added by alexchain in the template doc. Please take time to add it into your strategy documentation | 14:33 |
| sballe_ | because I still need the version of Node manager I put -1 because even if everything is perfect I don;t want it merged | 14:33 |
| sballe_ | dtardivel: thx for the pointer to the bug id | 14:33 |
| acabot_ | sballe_ : ok so you need reviews ? | 14:33 |
| acabot_ | as the ocata-1 release is tomorrow, we will merge a lot of code right after this meeting | 14:33 |
| sballe_ | you guys can review it but I need to add the NM version | 14:33 |
| acabot_ | ok | 14:34 |
| sballe_ | before I want it merged | 14:34 |
| acabot_ | its still time to put your +1 for stats on all these patches : | 14:34 |
| *** amotoki has quit IRC | 14:34 | |
| acabot_ | #link https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/watcher-notifications-ovo | 14:34 |
| acabot_ | #link https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/audit-versioned-notifications-api | 14:34 |
| acabot_ | #link https://review.openstack.org/#/c/378466/ | 14:35 |
| brunograz | acabot: blind +1? I like it ;) | 14:35 |
| acabot_ | so please do it asap because we will have to deal with merge conflicts | 14:35 |
| acabot_ | brunograz : I would say "stackalytics reviews..." | 14:35 |
| brunograz | :D | 14:36 |
| dtardivel | acabot_: too late for #link https://review.openstack.org/#/c/378466/. I've jut mergd it :) | 14:36 |
| sballe_ | lol | 14:36 |
| acabot_ | as you know its good for the project to have reviewers from diverse companies so please add your +1 ;-) | 14:36 |
| acabot_ | dtardivel : too bad I missed it ;-) | 14:36 |
| *** m1dev has joined #openstack-meeting-4 | 14:37 | |
| sballe_ | lol | 14:37 |
| *** haleyb_ has quit IRC | 14:37 | |
| acabot_ | 2 other patches should be merged for the release | 14:37 |
| *** hemanth|away is now known as hemanth | 14:37 | |
| acabot_ | #link https://review.openstack.org/#/c/398299/ | 14:37 |
| acabot_ | #link https://review.openstack.org/#/c/396281/ | 14:38 |
| acabot_ | so if some of you can review them we can merge them today as well and be part of ocata-1 | 14:38 |
| sballe_ | ok I can review | 14:38 |
| acabot_ | #action sballe_ review https://review.openstack.org/#/c/398299/ https://review.openstack.org/#/c/396281/ | 14:39 |
| vincentfrancoise | ^ anyone interested in working on https://blueprints.launchpad.net/watcher/+spec/centralise-config-opts should probably review https://review.openstack.org/#/c/396281/ | 14:39 |
| hvprash_ | +1 | 14:39 |
| acabot_ | vincentfrancoise : thats right | 14:39 |
| *** haleyb_ has joined #openstack-meeting-4 | 14:39 | |
| atuly | i can if noone is working. | 14:39 |
| hvprash_ | i mean I can review | 14:39 |
| hvprash_ | :) | 14:39 |
| acabot_ | #action exploreshaifali atuly hvprash_ review https://review.openstack.org/#/c/396281/ | 14:40 |
| brunograz | +1 - can review as well | 14:40 |
| *** klamath has quit IRC | 14:40 | |
| exploreshaifali | :) | 14:40 |
| vincentfrancoise | atuly: no need to ask, when it comes to reviewing, just go for it ;) | 14:40 |
| acabot_ | #action brunograz review https://review.openstack.org/#/c/396281/ | 14:40 |
| acabot_ | Watcher CLI | 14:40 |
| acabot_ | Add functional tests to watcherclient needs reviews | 14:40 |
| dtardivel | acabot_: about 398299, we should wait for alexchain review as well .... | 14:40 |
| atuly | :) | 14:40 |
| dtardivel | acabot_: +1 | 14:40 |
| *** klamath has joined #openstack-meeting-4 | 14:41 | |
| *** amotoki_ has quit IRC | 14:41 | |
| acabot_ | #link https://review.openstack.org/#/c/389181/ | 14:41 |
| acabot_ | #action dtardivel review https://review.openstack.org/#/c/389181/ | 14:41 |
| *** lamt has joined #openstack-meeting-4 | 14:41 | |
| acabot_ | dtardivel : thats right I will try to ping alex | 14:42 |
| acabot_ | #topic Blueprint/Bug Review and Discussion | 14:42 |
| *** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)" | 14:42 | |
| acabot_ | #info Ocata-1 will be released tomorrow | 14:42 |
| acabot_ | #link https://launchpad.net/watcher/+milestone/ocata-1 | 14:42 |
| *** diga has joined #openstack-meeting-4 | 14:42 | |
| *** anilvenkata has quit IRC | 14:42 | |
| diga | hi, sorry got late | 14:43 |
| acabot_ | there is still 4 bugs in progress | 14:43 |
| acabot_ | sorry 3 in fact | 14:43 |
| *** bertys has joined #openstack-meeting-4 | 14:43 | |
| acabot_ | #info A couple of unfinished blueprints have been moved to Ocata-2 | 14:44 |
| *** duonghq has joined #openstack-meeting-4 | 14:44 | |
| acabot_ | #link https://launchpad.net/watcher/+milestone/ocata-2 | 14:44 |
| acabot_ | so Ocata-2 is our new target expected 12/12 | 14:44 |
| diga | acabot_: I have started pushing PS on automatic triggerring BP | 14:45 |
| acabot_ | sballe_ : any update from kevin about the graph model ? | 14:45 |
| *** bobh has joined #openstack-meeting-4 | 14:45 | |
| acabot_ | diga : sorry we already discussed it | 14:45 |
| sballe_ | no is thijs here? | 14:45 |
| sballe_ | I'll follow up again :-( | 14:45 |
| diga | acabot_: I can finish the code by EOW, can I continue work on it | 14:46 |
| acabot_ | diga : we will discuss it on watcher channel after the meeting | 14:46 |
| diga | ok | 14:46 |
| acabot_ | #action sballe_ follow up on https://blueprints.launchpad.net/watcher/+spec/graph-based-cluster-model | 14:47 |
| *** cleong has joined #openstack-meeting-4 | 14:47 | |
| acabot_ | #topic Open discussions | 14:47 |
| *** openstack changes topic to "Open discussions (Meeting topic: watcher)" | 14:47 | |
| acabot_ | Should we use Trello to keep progress on Watcher ? | 14:47 |
| sballe_ | yes but only if it makes sense | 14:47 |
| acabot_ | it was a topic to discuss in Barcelona but meetings were too short | 14:48 |
| sballe_ | if peopel are not going ot pay attention to it then no | 14:48 |
| acabot_ | the idea is to keep actions in Trello | 14:48 |
| acabot_ | instead of relying only on the IRC bot from one meeting to another | 14:48 |
| sballe_ | I like the idea so I can tell my management about the Watcher roadmap | 14:48 |
| sballe_ | it looks a lot like JiRA so we can keep track of use stories, etc | 14:49 |
| acabot_ | and also keep ideas for Watcher long term evolutions somewhere | 14:49 |
| seanmurphy | +1 for trello from our side! | 14:49 |
| sballe_ | +1 same here | 14:49 |
| hvprash_ | i like trello too. +1 | 14:49 |
| vincentfrancoise | +1 | 14:49 |
| brunograz | +1 | 14:49 |
| acabot_ | #link https://trello.com/invite/b/qPDRBsG7/d735794f93465d1d45ad18729c8395b9/openstack-watcher | 14:50 |
| acabot_ | I have created a board to give you an overview | 14:50 |
| acabot_ | as everyone seems happy with trello :-) I will prepare our next meeting with it | 14:51 |
| *** psachin has quit IRC | 14:51 | |
| acabot_ | if you want to add a column, feel free to do it | 14:51 |
| sballe_ | cool! | 14:51 |
| *** zhurong has quit IRC | 14:51 | |
| acabot_ | #action acabot_ use Trello for preparing our next IRC meeting | 14:52 |
| acabot_ | licanwei : can you access the Trello board ? | 14:52 |
| acabot_ | licanwei : just to check that you can use it from China | 14:52 |
| licanwei | ok | 14:53 |
| licanwei | i'll try it | 14:53 |
| sballe_ | acabot_: looks great! | 14:53 |
| acabot_ | licanwei : can you just click on the link https://trello.com/invite/b/qPDRBsG7/d735794f93465d1d45ad18729c8395b9/openstack-watcher ? | 14:53 |
| acabot_ | and tell me if it works ? | 14:54 |
| licanwei | acabot: need sign up first | 14:54 |
| acabot_ | ok | 14:54 |
| acabot_ | if you can access the sigh-up page thats fine :-D | 14:54 |
| *** GB21 has quit IRC | 14:54 | |
| licanwei | yes | 14:54 |
| acabot_ | any other topic to discuss today ? | 14:55 |
| sballe_ | nice | 14:55 |
| *** andymaier has joined #openstack-meeting-4 | 14:55 | |
| acabot_ | for our new contributors, feel free to ask questions on #openstack-watcher | 14:55 |
| *** srwilkers has joined #openstack-meeting-4 | 14:55 | |
| acabot_ | there is always someone to help you | 14:55 |
| atuly | acabot : regarding some pointer on Workload balance strategy | 14:55 |
| vincentfrancoise | FYI I'll be on vacation starting next week ;) | 14:56 |
| sballe_ | vincentfrancoise: enjoy | 14:56 |
| acabot_ | vincentfrancoise : oh yes I forgot to mention that Vincent will be off for 4 weeks | 14:56 |
| exploreshaifali | vincentfrancoise, enjoy :) | 14:56 |
| hvprash_ | vincentfrancoise, i need to catch you then this week :) | 14:56 |
| sballe_ | vincentfrancoise: that sounds like a great time off | 14:56 |
| vincentfrancoise | thx all :p | 14:56 |
| *** talonx has joined #openstack-meeting-4 | 14:56 | |
| acabot_ | he really deserves it ;-) | 14:56 |
| hvprash_ | yes +@ | 14:57 |
| hvprash_ | +2 | 14:57 |
| atuly | vincentfrancoise : enjoy:) | 14:57 |
| sballe_ | acabot: do you have 10 mins for a quick chat around Intel contributions? | 14:57 |
| *** andymaier has quit IRC | 14:57 | |
| acabot_ | so during next month, the challenge would be to have more commits than vincentfrancoise on the ocata release ;-) | 14:57 |
| sballe_ | lol | 14:57 |
| exploreshaifali | lol | 14:58 |
| vincentfrancoise | should be easy ;) | 14:58 |
| acabot_ | sballe_ : 10 min max right after the meeting | 14:58 |
| *** ricolin has quit IRC | 14:58 | |
| *** hongbin has joined #openstack-meeting-4 | 14:58 | |
| sballe_ | cool! | 14:58 |
| *** sdake has joined #openstack-meeting-4 | 14:59 | |
| acabot_ | so thank you all | 14:59 |
| acabot_ | time to close the meeting | 14:59 |
| vincentfrancoise | bye all | 14:59 |
| brunograz | bye | 14:59 |
| acabot_ | have a good day/night | 14:59 |
| licanwei | bye | 14:59 |
| atuly | bye | 14:59 |
| *** coolsvap_ is now known as coolsvap | 14:59 | |
| exploreshaifali | bye | 14:59 |
| dtardivel | bye | 14:59 |
| *** vincentfrancoise has left #openstack-meeting-4 | 14:59 | |
| acabot_ | #endmeeting | 14:59 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 14:59 | |
| openstack | Meeting ended Wed Nov 16 14:59:28 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:59 |
| *** brunograz has left #openstack-meeting-4 | 14:59 | |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-11-16-14.00.html | 14:59 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-11-16-14.00.txt | 14:59 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-11-16-14.00.log.html | 14:59 |
| *** licanwei has quit IRC | 14:59 | |
| *** atuly has quit IRC | 14:59 | |
| *** dkusidlo has joined #openstack-meeting-4 | 15:00 | |
| *** exploreshaifali has quit IRC | 15:00 | |
| serverascode | #startmeeting operators_telco_nfv | 15:00 |
| openstack | Meeting started Wed Nov 16 15:00:37 2016 UTC and is due to finish in 60 minutes. The chair is serverascode. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| *** openstack changes topic to " (Meeting topic: operators_telco_nfv)" | 15:00 | |
| openstack | The meeting name has been set to 'operators_telco_nfv' | 15:00 |
| serverascode | #topic roll call | 15:00 |
| *** openstack changes topic to "roll call (Meeting topic: operators_telco_nfv)" | 15:00 | |
| serverascode | Good day to everyone :) | 15:01 |
| serverascode | #link https://etherpad.openstack.org/p/ops-telco-nfv-meeting-agenda | 15:01 |
| serverascode | ^ agenda, feel free to add/change anything | 15:01 |
| *** ad_rien_ has joined #openstack-meeting-4 | 15:01 | |
| *** sdake_ has quit IRC | 15:02 | |
| *** rbak has joined #openstack-meeting-4 | 15:02 | |
| talonx | Hi all | 15:03 |
| serverascode | hi talonx | 15:03 |
| serverascode | so far you and me | 15:04 |
| ad_rien_ | o/ | 15:04 |
| serverascode | hi ad_rien_ | 15:04 |
| ad_rien_ | hi | 15:04 |
| ad_rien_ | should we start ? | 15:04 |
| *** GeraldK has joined #openstack-meeting-4 | 15:05 | |
| serverascode | sure, I was just waiting to see if anyone else was here | 15:05 |
| serverascode | but we can start | 15:05 |
| serverascode | have a look a the agenda I linked above and feel free to add anything | 15:05 |
| serverascode | #topic Consensus on NFVi mid to long term project | 15:06 |
| *** openstack changes topic to "Consensus on NFVi mid to long term project (Meeting topic: operators_telco_nfv)" | 15:06 | |
| serverascode | so the first item I had was ensuring we had consensus on the mid to long term project we discussed last week | 15:06 |
| *** spotz_zzz is now known as spotz | 15:06 | |
| serverascode | we had a good meeting but it was a bit rushed at the end | 15:06 |
| serverascode | anyone have any thoughts on that? | 15:07 |
| serverascode | we don't have a lot of people in the meeting at this time | 15:07 |
| serverascode | I started an etherpad about that page | 15:07 |
| serverascode | #link https://etherpad.openstack.org/p/OTN-nfvi-project | 15:07 |
| serverascode | about that topic I mean | 15:07 |
| serverascode | so have a look at that, there are a few things we need to figure out | 15:08 |
| *** woodard has joined #openstack-meeting-4 | 15:09 | |
| ad_rien_ | I just added information related to G5K (aka Grid'5000) | 15:09 |
| serverascode | thanks ad_rien_ I'm looking at the enos repository now :) | 15:11 |
| *** beisner has quit IRC | 15:11 | |
| GeraldK | question to me is whether we should spend lot of efforts on defining our own reference architecture or better re-use some existing architetcure maintained by someone else. | 15:12 |
| ad_rien_ | GeraldK: such as ? | 15:12 |
| jamemcc | Jamemcc here now also - sorry for being late | 15:12 |
| serverascode | no worries | 15:13 |
| GeraldK | as_rien_: sure, we have to pick one. just wanted to make a point that IMHO we should not consider defining our own one | 15:13 |
| ad_rien_ | the point is a minimal ? | 15:13 |
| ad_rien_ | so what is a minimal NFVi | 15:14 |
| *** acabot_ has quit IRC | 15:14 | |
| GeraldK | good question. minimal to what we want to use it for, i.e. do some initial work on benchmarking. | 15:14 |
| serverascode | that is me using that word | 15:14 |
| *** woodard has quit IRC | 15:14 | |
| *** woodard has joined #openstack-meeting-4 | 15:15 | |
| serverascode | my thoughts on minimal is that it's the most basic openstack posssible, plus something like neutron-sfc | 15:15 |
| ad_rien_ | yes that was roughly the end of our meeting | 15:16 |
| ad_rien_ | basic openstack what does it mean ? how many locations ? | 15:16 |
| ad_rien_ | wich services should be centralized vs distributed? | 15:16 |
| serverascode | I would think one location | 15:17 |
| ad_rien_ | GeraldK: if you have a pointer to some architecture candidates it would be great to give it a look | 15:17 |
| serverascode | yes please if anyone has examples, please let us know | 15:17 |
| ad_rien_ | is one location a NVF infrastructure ? | 15:17 |
| *** hieulq_ has joined #openstack-meeting-4 | 15:17 | |
| serverascode | I believe so | 15:17 |
| jamemcc | I like Curtis start which is just a few componnts of Openstack - seems to me Keystone, Nova and Neutron and then we need to more focus on if waht type of underlying hardware and then how many clouds assuming it is a multi-cloud | 15:17 |
| serverascode | do people here think NFVi has to be mulit-cloud? | 15:18 |
| ad_rien_ | jamemcc: "assuming it is a multi-cloud" | 15:18 |
| ad_rien_ | :-) | 15:18 |
| ad_rien_ | from my understanding NFVi has to be a multi site cloud | 15:18 |
| *** prateek has quit IRC | 15:18 | |
| ad_rien_ | that is several (nano/mini) DCs supervised in an unified manner ? | 15:19 |
| ad_rien_ | but this is my understanding | 15:19 |
| GeraldK | ad_rien_: what about the OPNFV scenarios, e.g. the one from the Colorado release: https://wiki.opnfv.org/display/SWREL/Colorado-Compact+Table+of+Scenarios | 15:19 |
| jamemcc | Ok, good - yes my opinion is that's sort of one step past minimal perhaps - but not nearly as much value to the reference architecture if it's not multi-cloud | 15:19 |
| serverascode | ok, interesting re multi-cloud | 15:21 |
| ad_rien_ | GeraldK: not sure I correctly understand the table, could you explain it in a few lines please ? | 15:21 |
| ad_rien_ | in my mind the minimalist architecture can be to have controllers in a central DC and then only compute nodes deployed on the different sites (i.e. you have a master sites and then several secondary sites. The master hosts keystone, nova controller,… whereas the secondary sites host compute nodes only) | 15:22 |
| serverascode | #link https://wiki.opnfv.org/display/SWREL/Colorado-Compact+Table+of+Scenarios | 15:23 |
| *** m1dev has quit IRC | 15:23 | |
| ad_rien_ | We can evaluate scenarios such as bandwith/latency issues related to the way OpenStack has been designed (we can discover that there is strong assumptions regarding the connectivity between compute nodes and controller ones for instance). | 15:24 |
| *** baoli_ has quit IRC | 15:24 | |
| GeraldK | ad_rien_: second column shows the base scenario, e.g. OpenStack + ONOS. for this scenario several variants exist, e.g. OS + ONOS +SFC. The table then shows that this combination is supported by which installers (e.g. all 4 in the example) | 15:24 |
| *** m-greene has joined #openstack-meeting-4 | 15:24 | |
| serverascode | ad_rien_ so by multi-cloud do you mean that hypervisors can be in different DCs? | 15:24 |
| ad_rien_ | this can be one possibility (among others) | 15:24 |
| ad_rien_ | GeraldK: ok thanks | 15:25 |
| GeraldK | just to confirm, when you talk about NFVi, are you referring to ETSI NFVI + VIM ? | 15:26 |
| *** yfauser has joined #openstack-meeting-4 | 15:26 | |
| *** yfauser_ has joined #openstack-meeting-4 | 15:27 | |
| serverascode | I am yeah, mostly because I'm focussed on openstack, which is, IMHO, NFVi + VIM | 15:27 |
| serverascode | I don't see how you could separate them when talking about OpenStack | 15:27 |
| ad_rien_ | maybe we can clarify that point | 15:27 |
| ad_rien_ | because OpenStack can be just a VIM actually | 15:28 |
| ad_rien_ | at least it can be seen as a VIM (from the ETSI definition), cannot it ? | 15:28 |
| jamemcc | As a proposal- multi-cloud means 2 different instances of OpenStck - basically to satisfy the interoperability of 2 NFVis. Basically if you follow this minimum 2 different operators could get their NFVs to work together. | 15:28 |
| serverascode | ad_rien_ I agree, but what else can openstack control as a vim? vcenter? | 15:29 |
| serverascode | jamemcc +1 on multi-cloud = 2 different instances of openstack | 15:29 |
| ad_rien_ | I just read (once again) the definition on the document that has been linked during the last meeting: | 15:29 |
| ad_rien_ | 1 NFVI: Totality of all hardware and software components thatbuild up the environment in which VNFs are deployed | 15:30 |
| ad_rien_ | 2 VIM: Functional block that is responsible for controlling and managing the NFVI compute, storage and network resources, usually within one operator’s Infrastructure Domain (e.g. NFVI-PoP) | 15:30 |
| ad_rien_ | for me the difference is not clear. | 15:30 |
| *** beisner has joined #openstack-meeting-4 | 15:30 | |
| *** hieulq_ has quit IRC | 15:30 | |
| *** yfauser has quit IRC | 15:30 | |
| serverascode | I've always just though of the vim as things like the API endpoints and the scheduler, authentication | 15:31 |
| serverascode | and NFVi as the parts that provide network, compute, and storage | 15:31 |
| *** syed__ has joined #openstack-meeting-4 | 15:31 | |
| GeraldK | NFVI is kind of the DC, which consists of servers, hypervisors, the operation systems, VMs and network resources | 15:31 |
| ad_rien_ | GeraldK: and VIM is ? | 15:32 |
| GeraldK | the entity that is managing the resources in the NFVI | 15:33 |
| GeraldK | but I see that OpenStack may not easily be mapped to just the VIM | 15:33 |
| ad_rien_ | maybe we should clarify that in a pad (I'm sorry but for me the distinction between the two concept is not clear) | 15:34 |
| ad_rien_ | regarding the remark of : is a NFVi a multi cloud? I would say it depends how the different openstack instances collaborate. | 15:34 |
| serverascode | I'm trying to capture some of it, we can clean it up later, but it is important for all of us to have similar definitions :) so this is good | 15:35 |
| ad_rien_ | There are different approaches. Either there is a middleware (a broker/orchestrator) or you can try to make collaborations directly | 15:35 |
| ad_rien_ | (see the multisite deployment on the Openstack documentation) | 15:35 |
| serverascode | can you link me to the doc? | 15:36 |
| ad_rien_ | #link http://docs.openstack.org/arch-design/multi-site.html | 15:37 |
| ad_rien_ | So the question is : should we investigate the multi operator scenario for the basic use-case ? | 15:37 |
| ad_rien_ | (in reference to the jamemcc remark) | 15:38 |
| ad_rien_ | which means two keystones spaces etc… | 15:38 |
| ad_rien_ | if you look directly to #link http://docs.openstack.org/arch-design/multi-site-architecture.html | 15:39 |
| serverascode | ok, so that doc, to me, is about openstack multi-region | 15:39 |
| ad_rien_ | you can see another reference architecture. | 15:39 |
| *** spzala has joined #openstack-meeting-4 | 15:39 | |
| ad_rien_ | serverascode: yes but the difference is not so big from my point of view, is it? | 15:40 |
| serverascode | multi-region is a totally valid architecture, but it is quite different from a multi-openstack | 15:40 |
| serverascode | well maybe not quite different, the major difference is you share a single keystone (perhaps horizon, perhaps glance) database across regions | 15:41 |
| ad_rien_ | …. hmmm as I said it depends how you make the collaboration between your different openstack instances | 15:41 |
| serverascode | I agree | 15:41 |
| *** sbezverk has joined #openstack-meeting-4 | 15:41 | |
| serverascode | but to be honest, multi-region is not that common, though it is very cool | 15:41 |
| ad_rien_ | so first architecture (very basic): one openstack (i.e horizon, keystone, nova, neutron) and only compute nodes on remote locations | 15:41 |
| ad_rien_ | second architecture the one that is presented in the picture; That is horizon, keystone and maybe glance are shared other services are deployed on the remote locations | 15:42 |
| serverascode | yes, though it is also not common (yet) to put compute nodes in remote locations | 15:42 |
| ad_rien_ | third .... | 15:42 |
| serverascode | typically they are all in the same dc | 15:42 |
| *** sp__ has joined #openstack-meeting-4 | 15:43 | |
| ad_rien_ | for a telco (at least for BT), it may make sense to keep the control plane in one location and distribute only the compute that will host the VM at the edge | 15:43 |
| serverascode | for sure, you just can't really do that with openstack right now as far as I know | 15:43 |
| ad_rien_ | (s/edge/on the customer equipments) | 15:43 |
| ad_rien_ | why ? | 15:43 |
| *** iyamahat has joined #openstack-meeting-4 | 15:44 | |
| ad_rien_ | What does prevent you to do that ? | 15:44 |
| ad_rien_ | that is an interesting question | 15:44 |
| ad_rien_ | that can be the minimal architecture? | 15:44 |
| ad_rien_ | (don't get me wrong, I didn't say we should do that, I just try to put some materials in the discussion) | 15:45 |
| serverascode | I've heard that typically called "fog" or "edge" computing. there is a massively distributed owrking group that is working on that use case | 15:45 |
| ad_rien_ | yes that is indeed one direction we would like to investigate | 15:45 |
| serverascode | it's not impossible, just that openstack wasn't quite designed for that | 15:45 |
| serverascode | for example nova-compute has to tallk to the rabbit cluster | 15:45 |
| jamemcc | If we go with the official OpenStack multi-site reference architecture then it relly just leaves it up to us to be minimizing it downt ot what it takes to support NFV. I kind of like lettign others defince the basica OpenStack and we just use it. | 15:46 |
| serverascode | neutron also becomes a bit of an issue that way too | 15:46 |
| *** egonzalez90 has joined #openstack-meeting-4 | 15:46 | |
| ad_rien_ | actually we would like to answer the question core developers of OpenStack asked to the Tricircle team when they tried to join the big tent. From the Openstack core persons, it seems that you can do multi site scenarios with the vanilla code. | 15:46 |
| *** coolsvap is now known as coolsvap_ | 15:46 | |
| serverascode | #link https://wiki.openstack.org/wiki/Massively_Distributed_Clouds | 15:47 |
| ad_rien_ | serverascode: there is nothing special to deploy rabbitMQ on top of a WAN we already tried it at Inria (see #link https://hal.inria.fr/hal-01320235) | 15:47 |
| ad_rien_ | regarding neutron it might be an issue as we never played with it. | 15:48 |
| *** srwilkers has left #openstack-meeting-4 | 15:48 | |
| *** srwilkers has joined #openstack-meeting-4 | 15:48 | |
| ad_rien_ | jamemcc: not sure I'm following you | 15:48 |
| ad_rien_ | can you clarify/elaborate your point please | 15:48 |
| *** armax has joined #openstack-meeting-4 | 15:49 | |
| serverascode | I think multi-region is great, but I also think telecoms will tie together multiple separate openstack clouds using a higher level system (eg the MANO tier) or, as you mentioned, something like Tricircle | 15:49 |
| jamemcc | In the Multi-site-architecture picture the top comonent is a load balancer - I'm not sure that applies to our refernce architecture - I understand it for a multi-site deployment where the 2 sites in exssence back each other up - but for our purposes here the 2 sites are not duplicate but exist to service different NFVs | 15:49 |
| ad_rien_ | serverascode: but you are right rabbitMQ is definitely not the good choice for production systems but we need to come with strong arguments and performance evaluations to show that to the core devs. | 15:49 |
| ad_rien_ | serverascode: the main issue with an approach that is built on top of distinct OpenStack is that you have to reify all openstack capabilities/features at the high level. | 15:50 |
| ad_rien_ | In somehow you have to implement OpenStack features on top of OpenSTack … which means that you will use only basic features of OpenSTack since all advanced mechanisms will have to be implemented at the higher level. | 15:51 |
| *** mliima has joined #openstack-meeting-4 | 15:51 | |
| *** uxdanielle has quit IRC | 15:52 | |
| ad_rien_ | that is one of the reason Tricircle has not been accepted in the big tent during this summer | 15:52 |
| serverascode | yeah, that makes sense | 15:52 |
| serverascode | I guess I was hoping to avoid all this complexity for now, and just do a single openstack site :) | 15:52 |
| serverascode | for our initial project anyways :) | 15:52 |
| ad_rien_ | finally they splitted the code of Tricircle in two part and now Tricircle just focuses on providing networking automation across Neutron in multi-region OpenStack clouds deployment. | 15:52 |
| serverascode | but, it does sound like some kind of multi-site/region/cloud is important to you and jamemcc | 15:53 |
| *** sukhdev has joined #openstack-meeting-4 | 15:53 | |
| serverascode | (time check: about 5 min left) | 15:53 |
| *** inc0 has joined #openstack-meeting-4 | 15:53 | |
| ad_rien_ | yes I fully agree. The question of interoperability between operators is crucial | 15:53 |
| ad_rien_ | I just say that you have two ways to address this multisite/multi clouds/multi *** scenarios | 15:54 |
| ad_rien_ | I'm used to make a comparison with TCP/IP | 15:54 |
| ad_rien_ | every operator uses TCP/IP to exchange packets and then they have peering agreements | 15:54 |
| serverascode | jamecc do you also feel multi-* is important for this project? | 15:55 |
| ad_rien_ | if we consider that OpenStack is the default VIM/NFVi then why should we reimplement a stack above to ensure interoperability | 15:55 |
| jamemcc | As another observation about the large Telco use case of the multi-site-architecture is that you may choose instead of just 1 centralized Horizon/Keystone/Swift to instead replicate the Keystone and other common configurations. To ad_rien's point - basically above OpenStack. Since that's more of the big Telco thing though - seems to me this multi-site with share Keystone is close enough. | 15:55 |
| ad_rien_ | why not investigating how OpenStack can natively cooperate | 15:55 |
| ad_rien_ | jamemcc: I agree (If I'm correctly understanding). | 15:56 |
| ad_rien_ | I didn't say that there should be one keystone | 15:56 |
| serverascode | ok, cool, so I think we have some consensus here regarding multi-* and in fact specifically multi-region | 15:56 |
| ad_rien_ | you can also envison to have a keystone that is fully distributed across different locations | 15:56 |
| ad_rien_ | using cassandra with replications for instance | 15:56 |
| serverascode | one keystone database | 15:56 |
| ad_rien_ | how can we move forward ? | 15:57 |
| serverascode | shared across locations (which is done with mysql galera at this time) | 15:57 |
| ad_rien_ | Should we try to synthesise our ideas on one pad? | 15:57 |
| ad_rien_ | galera is ok for two three sites | 15:57 |
| ad_rien_ | but it does not scale more than that | 15:57 |
| serverascode | yes for sure, we need to come up with some definitions and agree on them | 15:57 |
| *** Sukhdev_ has joined #openstack-meeting-4 | 15:58 | |
| serverascode | please add your thoughts to the etherpad and next meeting we will move forward | 15:58 |
| serverascode | (1 min left) | 15:58 |
| ad_rien_ | jamecc if you are available we can continue to discuss privately | 15:59 |
| ad_rien_ | (the same servercode ;) ) | 15:59 |
| ad_rien_ | Actually I would really appreciate to clarify that | 15:59 |
| *** pprokop has joined #openstack-meeting-4 | 15:59 | |
| serverascode | I've got a meeting unfortunately, but please feel free to use the #openstack-nfv channel | 15:59 |
| ad_rien_ | just to be sure that I do not pollute the discussion | 16:00 |
| serverascode | I'm going ot have to end the meeting! | 16:00 |
| ad_rien_ | jamecc are you available | 16:00 |
| serverascode | thanks everyone! good discussion :) | 16:00 |
| jamemcc | Sure ad_rien feel free to message me at jamemcc@gmail.com | 16:00 |
| ad_rien_ | I will switch to Openstack-nfv ? | 16:00 |
| *** coolsvap_ is now known as coolsvap | 16:00 | |
| jamemcc | ok | 16:00 |
| ad_rien_ | thanks serverascode | 16:00 |
| serverascode | #endmeeting | 16:00 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:00 | |
| openstack | Meeting ended Wed Nov 16 16:00:42 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-11-16-15.00.html | 16:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-11-16-15.00.txt | 16:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-11-16-15.00.log.html | 16:00 |
| inc0 | #startmeeting Kolla | 16:01 |
| *** talonx has quit IRC | 16:01 | |
| openstack | Meeting started Wed Nov 16 16:01:02 2016 UTC and is due to finish in 60 minutes. The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:01 |
| *** openstack changes topic to " (Meeting topic: Kolla)" | 16:01 | |
| *** rhallisey__ has joined #openstack-meeting-4 | 16:01 | |
| openstack | The meeting name has been set to 'kolla' | 16:01 |
| egonzalez90 | woot o/ | 16:01 |
| inc0 | hello everyone:) | 16:01 |
| *** uxdanielle has joined #openstack-meeting-4 | 16:01 | |
| duonghq | woot/ | 16:01 |
| rhallisey__ | helo | 16:01 |
| sp__ | hi all | 16:01 |
| jascott1 | hello | 16:01 |
| inc0 | #topic w00t for Kolla rollcall | 16:01 |
| duonghq | o/ | 16:01 |
| *** openstack changes topic to "w00t for Kolla rollcall (Meeting topic: Kolla)" | 16:01 | |
| Jeffrey4l | 0/ | 16:01 |
| coolsvap | o/ | 16:01 |
| srwilkers | woot o/ | 16:01 |
| jascott1 | woot | 16:01 |
| egonzalez90 | w00t | 16:01 |
| inc0 | woot:) | 16:01 |
| duonghq | wo0t/// | 16:01 |
| inc0 | ok, let's move on, I bet this will be full time meeting | 16:02 |
| *** portdirect has joined #openstack-meeting-4 | 16:02 | |
| inc0 | #topic Announcements | 16:02 |
| *** openstack changes topic to "Announcements (Meeting topic: Kolla)" | 16:02 | |
| *** mgiles has joined #openstack-meeting-4 | 16:02 | |
| sbezverk | o/ | 16:02 |
| portdirect | o/ | 16:02 |
| inc0 | 1. Kolla ansible is up! Our repo is split at last | 16:02 |
| qwang | o/ | 16:02 |
| *** bertys has quit IRC | 16:02 | |
| inc0 | we will cover logistics around that later in the meeting | 16:02 |
| inc0 | 2. 4.0.0b1 aka ocata-1 releases this week | 16:03 |
| inc0 | any other announcements? | 16:03 |
| inc0 | ok, let's move on to hard stuff | 16:03 |
| inc0 | #topic repo split | 16:04 |
| *** openstack changes topic to "repo split (Meeting topic: Kolla)" | 16:04 | |
| mliima | \o | 16:04 |
| inc0 | #link https://github.com/openstack/kolla-ansible | 16:04 |
| inc0 | we have it:) | 16:04 |
| *** dave-mccowan has joined #openstack-meeting-4 | 16:04 | |
| sdake | o/ | 16:04 |
| inc0 | as you can see this is copy of kolla itself from weekend | 16:04 |
| inc0 | today I'll propose patch removing ansible dir from kolla repo | 16:05 |
| Jeffrey4l | inc0, can we do this until we fixed the gate? | 16:05 |
| *** seanmurphy has quit IRC | 16:05 | |
| inc0 | Jeffrey4l, can we fix gate in kolla-ansible? | 16:06 |
| Jeffrey4l | in ml, i propose leave the deploy gate in kolla. | 16:06 |
| sdake | inc0 i already did the removal of ansible from kolla repo | 16:06 |
| *** v1k0d3n has joined #openstack-meeting-4 | 16:06 | |
| qwang | the patch is there https://review.openstack.org/#/c/398025/ | 16:06 |
| v1k0d3n | sorry, here now | 16:06 |
| inc0 | ahh missed that, sorry sdake | 16:07 |
| inc0 | Jeffrey4l, no, we need to remove ansible asap | 16:07 |
| Jeffrey4l | ok. | 16:07 |
| mliima | i propose remove docker from kolla-ansible | 16:07 |
| inc0 | because people will keep pushing code there | 16:07 |
| mliima | https://review.openstack.org/#/c/398320/ | 16:07 |
| *** yamahata has joined #openstack-meeting-4 | 16:07 | |
| inc0 | mliima, that on the other hand will have to wair | 16:07 |
| inc0 | until we prepare zuul-cloner | 16:07 |
| inc0 | or docker registry in infra | 16:07 |
| mliima | ok inc0 | 16:08 |
| inc0 | as we can build without ansible, we can't deploy without build | 16:08 |
| mliima | ok | 16:08 |
| inc0 | on that note, we'll create zuul-clone of kolla in kolla-ansible | 16:08 |
| inc0 | we can also do git submodule of kolla in kolla ansible | 16:09 |
| inc0 | to keep installation easy | 16:09 |
| inc0 | which means we also need to change our docs | 16:09 |
| inc0 | as deployment procedure will be slightly different | 16:09 |
| inc0 | #link https://etherpad.openstack.org/p/kolla-repo-split | 16:10 |
| inc0 | let's use this etherpad to list out all the logistics and cleanups we need to make | 16:10 |
| sdake | inc0 our docs don't recommend deploying gfrom git | 16:10 |
| inc0 | pip will be diffetent too | 16:10 |
| sdake | inc0 they recommend deploying from pip becasuse of the pbr version problem | 16:11 |
| sdake | git submodules only help developers | 16:11 |
| inc0 | and really, I personally find this an abomination that it's not equivalent | 16:11 |
| sdake | pretty sure everyone thats a dev can check out two repos :) | 16:11 |
| sdake | inc0 feel free to fix it | 16:11 |
| inc0 | but that's discussion for another day | 16:11 |
| sdake | inc0 did best I could with the expert resources (dhellman in particular) available to me | 16:11 |
| *** GeraldK has quit IRC | 16:12 | |
| sdake | Jeffrey4l i thought i saw christmas there for a moment ;) | 16:13 |
| inc0 | let's focus on todo guys for now | 16:13 |
| inc0 | we need this list to be comprehensive to distribute work effectively | 16:13 |
| Jeffrey4l | hmm. sorry, do not get the point :/ | 16:13 |
| sdake | Jeffrey4l nm :) | 16:14 |
| sp__ | sdake: would kolla-k8s arch spec is still open for input ? | 16:16 |
| *** armax has quit IRC | 16:16 | |
| *** rhallisey__ is now known as rhallisey | 16:17 | |
| *** rtheis_ is now known as rtheis | 16:17 | |
| coolsvap | did I lost connection or meeting is actually stalled? | 16:19 |
| srwilkers | im still here | 16:19 |
| inc0 | no, we are in etherpad | 16:19 |
| inc0 | doing todo list for cleanups | 16:19 |
| inc0 | 10 more minutes | 16:19 |
| sdake | coolsvap we are brainstorming - not sure what the window is | 16:19 |
| coolsvap | sorry missed the etherpad | 16:19 |
| sdake | sp__ yes its open until merged | 16:19 |
| *** caboucha has joined #openstack-meeting-4 | 16:19 | |
| egonzalez90 | coolsvap: https://etherpad.openstack.org/p/kolla-repo-split | 16:20 |
| coolsvap | thanks egonzalez90 got there | 16:20 |
| *** asettle has quit IRC | 16:20 | |
| sdake | sp_ reference https://github.com/openstack/kolla-kubernetes/blob/master/specs/README.rst | 16:20 |
| rhallisey | sp_, yes it's still open | 16:20 |
| *** asettle has joined #openstack-meeting-4 | 16:20 | |
| sp__ | thanks sdake and rhallisey for info and link | 16:21 |
| portdirect | hey could you give me a ping when your back | 16:22 |
| portdirect | (from etherpad) | 16:22 |
| *** armax has joined #openstack-meeting-4 | 16:23 | |
| *** numans has quit IRC | 16:25 | |
| *** mordred has joined #openstack-meeting-4 | 16:26 | |
| mordred | inc0: sup? | 16:26 |
| inc0 | 2 more minutes in our brainstorm topic (working on ehterpad now) and we'll move on to how gate kolla-ansible | 16:27 |
| inc0 | but I appreciate having you around:) thanks | 16:27 |
| inc0 | I'll use this time to give you full context mordred | 16:27 |
| inc0 | so as you probably know, we split kolla into kolla and kolla-ansible | 16:28 |
| inc0 | we also have kolla-kubernetes | 16:28 |
| inc0 | kolla now holds all the images | 16:28 |
| sdake | inc0 you mean gate kolla :) | 16:28 |
| inc0 | sdake, hold on | 16:28 |
| inc0 | that'll be topic part;) | 16:28 |
| sdake | oh right | 16:29 |
| inc0 | just giving mordred state we are now | 16:29 |
| mordred | inc0: nod. kolla has the images, kolla-ansible and kolla-k8s want to consume them, yeah? | 16:29 |
| inc0 | yeah | 16:29 |
| inc0 | but... | 16:29 |
| duonghq | portdirect, ping | 16:29 |
| inc0 | #topic gates in brave new world | 16:29 |
| *** openstack changes topic to "gates in brave new world (Meeting topic: Kolla)" | 16:29 | |
| portdirect | cheers | 16:29 |
| inc0 | so mordred fungi and everyone, we want 2 things really | 16:30 |
| inc0 | kolla-ansible and k8s needs to build images today | 16:30 |
| inc0 | as we don't have docker registry for them | 16:30 |
| inc0 | so I expect to use zuul cloner there to pull kolla and build images locally | 16:30 |
| inc0 | but at the end of the day, we would like to have some smoketest gates in kolla to see if our deployments hasn't been broken after a change | 16:31 |
| inc0 | so correct me if I'm wrong, but zuul cloner will allow cross repo gates as in adding gates from kolla to kolla-ansible, but not other way around right? | 16:31 |
| mordred | they can totally be bi-directional | 16:32 |
| inc0 | so zuul clones kolla to kolla-ansible and kolla-ansible to kolla? | 16:32 |
| mordred | so you can say "this job needs the kolla and kolla-ansible repos" then the job will clone both repos in the appropriate state and will run the job content | 16:32 |
| fungi | yeah, it's just a convenience utility to clone arbitrary refs of an arbitrary number of repos, taking advantage of local repo caches and refnames provided by zuul in our ci context | 16:32 |
| mordred | let's say there is a job called "gate-kolla-images" | 16:33 |
| *** magicboiz has joined #openstack-meeting-4 | 16:33 | |
| mordred | that job will be configured to clone kolla, kolla-ansible and kolla-kubernetes | 16:33 |
| magicboiz | Hi | 16:33 |
| mordred | and then in the content of the job, the job will expect those three repos to exist and will do $stuff | 16:33 |
| mordred | then, you can configure the kolla repo to run that job in its gate pipeline, and you can also configure kolla-ansible to do the same | 16:33 |
| fungi | (and kolla-kubernetes too if you want) | 16:34 |
| mordred | yah | 16:34 |
| inc0 | yeah we will want to have smoketest for both | 16:34 |
| inc0 | by smoketest I assume gates we have today;) | 16:34 |
| inc0 | ok, so short term, we need to configure zuul-cloner on both ends | 16:34 |
| inc0 | and keep gates working as they work today | 16:35 |
| inc0 | that will also allow us to remove docker directory from kolla-ansible immediatly | 16:35 |
| inc0 | #link http://docs.openstack.org/infra/zuul/cloner.html | 16:35 |
| inc0 | Jeffrey4l, sdake, others - is this solution acceptable? | 16:36 |
| Jeffrey4l | yep. i like that. | 16:36 |
| coolsvap | +1 | 16:36 |
| sdake | sorry two meetings at once - leemme catch up | 16:36 |
| sdake | DST FTL | 16:36 |
| egonzalez90 | looks fine | 16:36 |
| inc0 | I would refrain of having full fledged deploy gates in kolla as gates will take forever and still be not-voting | 16:36 |
| inc0 | but our current gates are ok for that purpose imho | 16:37 |
| mliima | looks good | 16:37 |
| sdake | yup lgtm | 16:37 |
| sdake | infra cats are experts, follow their lead imo :) | 16:37 |
| inc0 | so we just don't change anything aside of making build gates voting (yes, yay, I think we can do that( | 16:37 |
| sdake | i think mordred suggested having them right? | 16:38 |
| sdake | the reason for corss repo gating is to make sure the kolla imgaes are GTG when committed | 16:38 |
| sdake | the only plalce I know to do that is in the kolla repo | 16:39 |
| mordred | yah - the main thing is just to make sure that the build job does the right thing with the multiple repos | 16:39 |
| mordred | but yes | 16:39 |
| inc0 | so another question since you're here:) | 16:39 |
| * mordred hides | 16:39 | |
| inc0 | (can we wrap up this? I think we know what to do) | 16:39 |
| fungi | yeah, i mostly didn't want to see you roll out something confusing involving hacky git submodules that subsequently locks you out of a lot of convenient options from better testing across your repos | 16:39 |
| inc0 | #topic git submodule | 16:39 |
| *** openstack changes topic to "git submodule (Meeting topic: Kolla)" | 16:39 | |
| mordred | run away screaming | 16:39 |
| inc0 | so, we'll use zuul cloner | 16:39 |
| sdake | fungi ;) | 16:39 |
| mordred | \o/ | 16:39 |
| inc0 | but there are people asking for submodule in kolla-ansible for kolla just for purpose of easier installation for users | 16:40 |
| inc0 | git clone kolla-ansible --recursive and you have all you need locally | 16:40 |
| fungi | git submodules are not a substitute for an installer | 16:40 |
| portdirect | +1 | 16:40 |
| wirehead_ | heh | 16:41 |
| inc0 | I'm asking because other teams well, uses it like that it seems;) | 16:41 |
| inc0 | I guess putting kolla into requirements.txt of kolla-ansible should do the trick? | 16:42 |
| sdake | fungi right - we use pip to install | 16:42 |
| inc0 | sdake, everyone uses something different tbh | 16:42 |
| sdake | well devs use git obviously | 16:42 |
| inc0 | that's my point | 16:42 |
| sdake | operators use pip | 16:42 |
| Jeffrey4l | other project like puppet or openstack ansible are different from kolla. they depend on the code itself. But kolla-ansible depend on the docker images which kolla produced. | 16:43 |
| inc0 | you're right Jeffrey4l, so we don't make any dependency at all? | 16:43 |
| inc0 | and just ask people to install both projects separately? | 16:43 |
| Jeffrey4l | i prefer to no. | 16:43 |
| mordred | sorry - laptop crashed | 16:43 |
| Jeffrey4l | on the deployment node, why i must install kolla and its dependency? | 16:44 |
| inc0 | that's another approach | 16:44 |
| Jeffrey4l | ansibe is enough. | 16:44 |
| portdirect | i think the seperation between containers, and deployment makes sense i think from an ops perspective (ie no submodule) - but thats just me. | 16:44 |
| inc0 | which I actually like | 16:44 |
| inc0 | anyone is against having completely unrelated projects as far as installation goes? | 16:44 |
| sdake | inc0 could you restate the question, it didn't pass my parser | 16:45 |
| *** bobh has quit IRC | 16:45 | |
| Jeffrey4l | if we add kolla-ansible as kolla' submodule, how about the kolla-kubernetes projects? | 16:45 |
| inc0 | sdake, when kolla-ansible is installed in any way, kolla is not | 16:45 |
| sdake | wfm | 16:45 |
| inc0 | ok, for now we keep things totally separate then | 16:45 |
| egonzalez90 | kolla-ansible depends on an image built by kolla, not depends of kolla at all | 16:45 |
| duonghq | maybe we need separate "build-node" from "deployment-node" | 16:45 |
| inc0 | we can | 16:46 |
| inc0 | and it's quite elegant tbh | 16:46 |
| Jeffrey4l | duonghq, +1 | 16:46 |
| mordred | if you do wind up wanting to tie things together, I would strongly suggest that submodules will cause you more pain than they will solve, so trying other approaches first, I would suggest, will make you all much happier | 16:46 |
| egonzalez90 | +1 | 16:46 |
| mliima | duonghq, +1 | 16:46 |
| inc0 | mordred, got it, thanks for warning | 16:46 |
| portdirect | mordred: +1 to that :) | 16:46 |
| mordred | cool. | 16:46 |
| inc0 | but it seems for now we keep things totally separate | 16:46 |
| *** bpokorny has joined #openstack-meeting-4 | 16:46 | |
| *** zenoway has quit IRC | 16:47 | |
| *** reedip_ has quit IRC | 16:47 | |
| mordred | if you do end up getting to the place where it becomes essential - ping us, there are additional features/gotchas in gerrit-land :) | 16:47 |
| mordred | but I like where you're going :) | 16:47 |
| *** zenoway has joined #openstack-meeting-4 | 16:47 | |
| inc0 | ok | 16:48 |
| inc0 | anything else on that note? | 16:48 |
| inc0 | #topic open discussion | 16:48 |
| *** openstack changes topic to "open discussion (Meeting topic: Kolla)" | 16:48 | |
| inc0 | still have few minutes | 16:48 |
| Jeffrey4l | http://lists.openstack.org/pipermail/openstack-dev/2016-November/107429.html | 16:49 |
| rhallisey | the spec | 16:49 |
| rhallisey | it's almost done | 16:49 |
| rhallisey | will have another review up soon | 16:49 |
| Jeffrey4l | we need push some goals for ocata. | 16:49 |
| Jeffrey4l | it breaks our release. | 16:50 |
| Jeffrey4l | https://review.openstack.org/398433 | 16:50 |
| Jeffrey4l | block | 16:50 |
| portdirect | rhallisey: thanks for keeping on top of it! | 16:51 |
| rhallisey | no problem | 16:51 |
| inc0 | it doesn't seem to be the case for us tho | 16:51 |
| rhallisey | just be sure everyone gets their comments in | 16:51 |
| wirehead_ | :) | 16:51 |
| *** zenoway has quit IRC | 16:51 | |
| portdirect | also the impromptu hangouts have been really usefull - I really think we should keep them up when we hit issues | 16:52 |
| *** diga has quit IRC | 16:52 | |
| *** yfauser_ has quit IRC | 16:52 | |
| portdirect | gotta meeting, so need to head - catch you guys later | 16:53 |
| *** portdirect is now known as portdirect_away | 16:53 | |
| *** wirehead_ has left #openstack-meeting-4 | 16:53 | |
| inc0 | ok, I guess we're done for today?:) | 16:53 |
| duonghq | woot | 16:53 |
| inc0 | for meeting* | 16:53 |
| inc0 | today is still ongoing, don't stop working | 16:53 |
| sdake | re impromptu meetings | 16:53 |
| sdake | can we please schedule them | 16:53 |
| sdake | if we are going to have them | 16:53 |
| sdake | they are not inclusive | 16:54 |
| sdake | TIA :) | 16:54 |
| inc0 | schedule impromptu meetings? that's not impromptu | 16:54 |
| sdake | right oxymoron | 16:54 |
| sdake | the problem with improtu meetings is not everyone is aorund | 16:54 |
| inc0 | we jump on hangouts when we can't communicate over irc | 16:54 |
| sdake | 4 guys in a meeting do not make up the communities best judgement | 16:54 |
| inc0 | but they can get into agreement | 16:55 |
| sdake | right - then gotta convince everyone else | 16:55 |
| inc0 | not everyone | 16:55 |
| sdake | not inclusive... | 16:55 |
| sdake | i constantly have conflicts with the spur of the moment hangouts | 16:56 |
| inc0 | we had something called "liberum veto" in Polish history, where single person could throw out voting...spoiler alert - didn't end well | 16:56 |
| inc0 | anyway, will be reflected in spec and totally optional | 16:57 |
| sdake | i'm not asking for much | 16:57 |
| inc0 | so feel free to drop it there | 16:57 |
| inc0 | anyway, I think we exhausted this meetings time | 16:57 |
| inc0 | thanks everyone for comming! | 16:57 |
| inc0 | #endmeeting kolla | 16:58 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:58 | |
| openstack | Meeting ended Wed Nov 16 16:58:03 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:58 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-11-16-16.01.html | 16:58 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-11-16-16.01.txt | 16:58 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-11-16-16.01.log.html | 16:58 |
| *** rhallisey has left #openstack-meeting-4 | 16:58 | |
| mliima | ok, bye guys \o | 16:58 |
| *** jascott1 has left #openstack-meeting-4 | 16:58 | |
| *** sbezverk has left #openstack-meeting-4 | 16:58 | |
| *** mgiles has left #openstack-meeting-4 | 16:58 | |
| *** duonghq has left #openstack-meeting-4 | 16:58 | |
| *** mliima has left #openstack-meeting-4 | 16:58 | |
| *** sp__ has quit IRC | 16:59 | |
| *** magicboiz has left #openstack-meeting-4 | 17:01 | |
| *** Rockyg has joined #openstack-meeting-4 | 17:04 | |
| *** Sukhdev_ has quit IRC | 17:05 | |
| *** sdake has quit IRC | 17:06 | |
| *** unicell1 has joined #openstack-meeting-4 | 17:07 | |
| *** unicell has quit IRC | 17:08 | |
| *** sdake has joined #openstack-meeting-4 | 17:09 | |
| *** uck has joined #openstack-meeting-4 | 17:09 | |
| *** Rockyg has quit IRC | 17:10 | |
| *** egonzalez90 has left #openstack-meeting-4 | 17:10 | |
| *** rtheis_ has joined #openstack-meeting-4 | 17:14 | |
| *** rtheis has quit IRC | 17:15 | |
| *** ad_rien_ has quit IRC | 17:18 | |
| *** dkusidlo has quit IRC | 17:21 | |
| *** bpokorny has quit IRC | 17:23 | |
| *** matrohon has quit IRC | 17:23 | |
| *** Swami has joined #openstack-meeting-4 | 17:29 | |
| *** bpokorny has joined #openstack-meeting-4 | 17:29 | |
| *** baoli has joined #openstack-meeting-4 | 17:30 | |
| *** yfauser has joined #openstack-meeting-4 | 17:39 | |
| *** unicell1 has quit IRC | 17:42 | |
| *** iyamahat has quit IRC | 17:45 | |
| *** bobh has joined #openstack-meeting-4 | 17:46 | |
| *** david-lyle has quit IRC | 17:48 | |
| *** david-lyle has joined #openstack-meeting-4 | 17:48 | |
| *** bobh has quit IRC | 17:51 | |
| *** uxdanielle has quit IRC | 17:52 | |
| *** claudiub has quit IRC | 17:52 | |
| *** julim has quit IRC | 17:54 | |
| *** iyamahat has joined #openstack-meeting-4 | 17:56 | |
| *** ralonsoh has quit IRC | 17:58 | |
| *** cdelatte has joined #openstack-meeting-4 | 18:00 | |
| *** yfauser has quit IRC | 18:01 | |
| *** yamahata has quit IRC | 18:01 | |
| *** iyamahat has quit IRC | 18:02 | |
| *** bpokorny has quit IRC | 18:05 | |
| *** pkoniszewski has quit IRC | 18:07 | |
| *** pkoniszewski has joined #openstack-meeting-4 | 18:10 | |
| *** v1k0d3n has quit IRC | 18:11 | |
| *** sukhdev has quit IRC | 18:11 | |
| *** pbourke has quit IRC | 18:11 | |
| *** pbourke has joined #openstack-meeting-4 | 18:12 | |
| *** m-greene has quit IRC | 18:12 | |
| *** harlowja has joined #openstack-meeting-4 | 18:14 | |
| *** bpokorny has joined #openstack-meeting-4 | 18:15 | |
| *** unicell has joined #openstack-meeting-4 | 18:16 | |
| *** sambetts is now known as sambetts|afk | 18:18 | |
| *** iyamahat has joined #openstack-meeting-4 | 18:20 | |
| *** uxdanielle has joined #openstack-meeting-4 | 18:27 | |
| *** uck_ has joined #openstack-meeting-4 | 18:29 | |
| *** uck has quit IRC | 18:29 | |
| *** bobh has joined #openstack-meeting-4 | 18:31 | |
| *** julim has joined #openstack-meeting-4 | 18:37 | |
| *** yamahata has joined #openstack-meeting-4 | 18:39 | |
| *** m-greene has joined #openstack-meeting-4 | 18:40 | |
| *** mdorman has joined #openstack-meeting-4 | 18:45 | |
| *** julim has quit IRC | 18:50 | |
| *** julim has joined #openstack-meeting-4 | 18:55 | |
| *** julim has quit IRC | 18:55 | |
| *** julim has joined #openstack-meeting-4 | 18:57 | |
| *** yfauser has joined #openstack-meeting-4 | 19:02 | |
| *** galstrom_zzz is now known as galstrom | 19:04 | |
| *** yfauser has quit IRC | 19:06 | |
| *** Sukhdev has joined #openstack-meeting-4 | 19:06 | |
| *** coolsvap has quit IRC | 19:07 | |
| *** hemanth is now known as hemanth|away | 19:07 | |
| *** ad_rien_ has joined #openstack-meeting-4 | 19:10 | |
| *** spotz is now known as spotz_zzz | 19:15 | |
| *** ad_rien_ has quit IRC | 19:16 | |
| *** yfauser has joined #openstack-meeting-4 | 19:16 | |
| *** haleyb_ has quit IRC | 19:20 | |
| *** matrohon has joined #openstack-meeting-4 | 19:26 | |
| *** caboucha has quit IRC | 19:28 | |
| *** betherly_ has joined #openstack-meeting-4 | 19:35 | |
| *** khushbu has joined #openstack-meeting-4 | 19:40 | |
| *** ad_rien_ has joined #openstack-meeting-4 | 19:45 | |
| *** hemanth|away is now known as hemanth | 19:47 | |
| *** haleyb_ has joined #openstack-meeting-4 | 19:49 | |
| *** galstrom is now known as galstrom_zzz | 19:49 | |
| *** ad_rien_ has quit IRC | 19:50 | |
| *** pcaruana has quit IRC | 19:51 | |
| *** uxdanielle has quit IRC | 19:52 | |
| *** haleyb_ has quit IRC | 19:53 | |
| *** tonytan4ever has quit IRC | 20:00 | |
| *** tonytan4ever has joined #openstack-meeting-4 | 20:01 | |
| *** jingting has quit IRC | 20:03 | |
| *** khushbu has quit IRC | 20:12 | |
| *** rainya has joined #openstack-meeting-4 | 20:16 | |
| *** bpokorny has quit IRC | 20:18 | |
| *** rainya has quit IRC | 20:20 | |
| *** uck has joined #openstack-meeting-4 | 20:21 | |
| *** uck_ has quit IRC | 20:21 | |
| *** bpokorny has joined #openstack-meeting-4 | 20:21 | |
| *** rainya has joined #openstack-meeting-4 | 20:22 | |
| *** Sukhdev has quit IRC | 20:23 | |
| *** dtardivel has quit IRC | 20:24 | |
| *** rtheis_ has quit IRC | 20:26 | |
| *** spotz_zzz is now known as spotz | 20:31 | |
| *** sdake has quit IRC | 20:35 | |
| *** rtheis has joined #openstack-meeting-4 | 20:36 | |
| *** sdake has joined #openstack-meeting-4 | 20:36 | |
| *** m-greene_ has joined #openstack-meeting-4 | 20:40 | |
| *** m-greene has quit IRC | 20:41 | |
| *** m-greene_ is now known as m-greene | 20:41 | |
| *** unicell has quit IRC | 20:46 | |
| *** matrohon has quit IRC | 20:47 | |
| *** haleyb_ has joined #openstack-meeting-4 | 20:50 | |
| *** unicell has joined #openstack-meeting-4 | 20:53 | |
| *** rtheis has quit IRC | 20:53 | |
| *** bobmel has quit IRC | 20:54 | |
| *** haleyb_ has quit IRC | 20:55 | |
| *** jichen has quit IRC | 20:55 | |
| *** Swami has quit IRC | 20:56 | |
| *** Swami has joined #openstack-meeting-4 | 20:59 | |
| *** hughsaunders has quit IRC | 21:03 | |
| *** hughsaunders has joined #openstack-meeting-4 | 21:06 | |
| *** uxdanielle has joined #openstack-meeting-4 | 21:12 | |
| *** bpokorny has quit IRC | 21:16 | |
| *** bpokorny has joined #openstack-meeting-4 | 21:17 | |
| *** bpokorny_ has joined #openstack-meeting-4 | 21:21 | |
| *** JRobinson__ has joined #openstack-meeting-4 | 21:22 | |
| *** bpokorny has quit IRC | 21:23 | |
| *** uck has quit IRC | 21:27 | |
| *** jovon has joined #openstack-meeting-4 | 21:28 | |
| *** Jeffrey4l has quit IRC | 21:33 | |
| *** inc0 has quit IRC | 21:33 | |
| *** cdelatte has quit IRC | 21:34 | |
| *** woodard has quit IRC | 21:35 | |
| *** woodard has joined #openstack-meeting-4 | 21:35 | |
| *** tonytan4ever has quit IRC | 21:36 | |
| *** ad_rien_ has joined #openstack-meeting-4 | 21:40 | |
| *** uck has joined #openstack-meeting-4 | 21:44 | |
| *** sdake_ has joined #openstack-meeting-4 | 21:44 | |
| *** woodard_ has joined #openstack-meeting-4 | 21:46 | |
| *** sdake has quit IRC | 21:47 | |
| *** Sukhdev has joined #openstack-meeting-4 | 21:49 | |
| *** woodard has quit IRC | 21:50 | |
| *** irenab has joined #openstack-meeting-4 | 21:50 | |
| *** haleyb_ has joined #openstack-meeting-4 | 21:51 | |
| *** uxdanielle has quit IRC | 21:52 | |
| *** irenab has quit IRC | 21:55 | |
| *** haleyb_ has quit IRC | 21:56 | |
| *** srwilkers has quit IRC | 22:02 | |
| *** woodard has joined #openstack-meeting-4 | 22:03 | |
| *** julim has quit IRC | 22:05 | |
| *** woodard_ has quit IRC | 22:06 | |
| *** woodard has quit IRC | 22:07 | |
| *** kylek3h has quit IRC | 22:09 | |
| *** betherly_ is now known as betherly | 22:10 | |
| *** s3wong has joined #openstack-meeting-4 | 22:12 | |
| *** thorst_ has quit IRC | 22:18 | |
| *** thorst_ has joined #openstack-meeting-4 | 22:19 | |
| *** rainya has quit IRC | 22:22 | |
| *** thorst_ has quit IRC | 22:24 | |
| *** slaweq_ has joined #openstack-meeting-4 | 22:25 | |
| *** rainya has joined #openstack-meeting-4 | 22:27 | |
| *** galstrom_zzz is now known as galstrom | 22:38 | |
| *** rainya has quit IRC | 22:42 | |
| *** kylek3h has joined #openstack-meeting-4 | 22:43 | |
| *** ad_rien_ has quit IRC | 22:45 | |
| *** haleyb_ has joined #openstack-meeting-4 | 22:52 | |
| *** rainya has joined #openstack-meeting-4 | 22:53 | |
| *** haleyb_ has quit IRC | 22:56 | |
| *** spzala has quit IRC | 23:03 | |
| *** bobh has quit IRC | 23:05 | |
| *** sdake has joined #openstack-meeting-4 | 23:06 | |
| *** dave-mccowan has quit IRC | 23:07 | |
| *** sdake_ has quit IRC | 23:10 | |
| *** sdake has quit IRC | 23:16 | |
| *** yfauser has quit IRC | 23:16 | |
| *** reedip_ has joined #openstack-meeting-4 | 23:20 | |
| *** khushbu_ has joined #openstack-meeting-4 | 23:20 | |
| *** cleong has quit IRC | 23:20 | |
| *** asettle has quit IRC | 23:23 | |
| *** uck_ has joined #openstack-meeting-4 | 23:26 | |
| *** uck has quit IRC | 23:26 | |
| *** hemanth is now known as hemanth|away | 23:26 | |
| *** Jeffrey4l has joined #openstack-meeting-4 | 23:31 | |
| *** lamt has quit IRC | 23:33 | |
| *** galstrom is now known as galstrom_zzz | 23:34 | |
| *** claudiub has joined #openstack-meeting-4 | 23:38 | |
| *** irenab has joined #openstack-meeting-4 | 23:38 | |
| *** sdake has joined #openstack-meeting-4 | 23:41 | |
| *** Julien-zte has quit IRC | 23:41 | |
| *** irenab has quit IRC | 23:43 | |
| *** khushbu_ has quit IRC | 23:43 | |
| *** rainya has quit IRC | 23:44 | |
| *** cdelatte has joined #openstack-meeting-4 | 23:49 | |
| *** david-lyle_ has joined #openstack-meeting-4 | 23:50 | |
| *** david-lyle has quit IRC | 23:51 | |
| *** haleyb_ has joined #openstack-meeting-4 | 23:53 | |
| *** rbak has quit IRC | 23:53 | |
| *** klamath has quit IRC | 23:53 | |
| *** rainya has joined #openstack-meeting-4 | 23:55 | |
| *** syed__ has quit IRC | 23:55 | |
| *** Swami has quit IRC | 23:58 | |
| *** reedip_ has quit IRC | 23:59 | |
| *** haleyb_ has quit IRC | 23:59 | |
| *** baoli has quit IRC | 23:59 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!