| *** woodard_ has quit IRC | 00:01 | |
| *** woodard has joined #openstack-meeting-4 | 00:01 | |
| *** revon has quit IRC | 00:03 | |
| *** marst has joined #openstack-meeting-4 | 00:04 | |
| *** uck has joined #openstack-meeting-4 | 00:07 | |
| *** uck_ has quit IRC | 00:07 | |
| *** yfauser has joined #openstack-meeting-4 | 00:08 | |
| *** armax has quit IRC | 00:10 | |
| *** yfauser has quit IRC | 00:12 | |
| *** Sukhdev has quit IRC | 00:12 | |
| *** uck has quit IRC | 00:22 | |
| *** reedip has joined #openstack-meeting-4 | 00:26 | |
| *** Syed__ has quit IRC | 00:35 | |
| *** bobh has quit IRC | 00:36 | |
| *** woodard has quit IRC | 00:37 | |
| *** erikmwilson has quit IRC | 00:37 | |
| *** woodard has joined #openstack-meeting-4 | 00:37 | |
| *** bobh has joined #openstack-meeting-4 | 00:38 | |
| *** erikmwilson has joined #openstack-meeting-4 | 00:39 | |
| *** woodard has quit IRC | 00:42 | |
| *** limao has joined #openstack-meeting-4 | 00:44 | |
| *** cjloader has joined #openstack-meeting-4 | 00:46 | |
| *** armax has joined #openstack-meeting-4 | 00:51 | |
| *** Julien-zte has joined #openstack-meeting-4 | 00:52 | |
| *** amotoki has joined #openstack-meeting-4 | 00:53 | |
| *** zhurong has joined #openstack-meeting-4 | 00:53 | |
| *** cjloader has quit IRC | 00:55 | |
| *** bobh has quit IRC | 00:55 | |
| *** erikmwilson has quit IRC | 01:07 | |
| *** erikmwilson has joined #openstack-meeting-4 | 01:08 | |
| *** yfauser has joined #openstack-meeting-4 | 01:09 | |
| *** yfauser has quit IRC | 01:14 | |
| *** unicell has quit IRC | 01:20 | |
| *** britthouser has joined #openstack-meeting-4 | 01:24 | |
| *** britthouser6 has quit IRC | 01:24 | |
| *** reedip has quit IRC | 01:25 | |
| *** yfauser has joined #openstack-meeting-4 | 01:31 | |
| *** yfauser has quit IRC | 01:36 | |
| *** cathrich_ has joined #openstack-meeting-4 | 01:43 | |
| *** s3wong has quit IRC | 01:56 | |
| *** lei-zh has joined #openstack-meeting-4 | 01:59 | |
| *** iyamahat has quit IRC | 02:00 | |
| *** lei-zh has quit IRC | 02:03 | |
| *** amotoki has quit IRC | 02:05 | |
| *** amotoki has joined #openstack-meeting-4 | 02:05 | |
| *** erikmwilson has quit IRC | 02:07 | |
| *** yamahata has quit IRC | 02:08 | |
| *** erikmwilson has joined #openstack-meeting-4 | 02:09 | |
| *** FrankZhang has joined #openstack-meeting-4 | 02:13 | |
| *** gongysh has joined #openstack-meeting-4 | 02:14 | |
| *** FrankZhang_ has joined #openstack-meeting-4 | 02:17 | |
| *** FrankZhang has quit IRC | 02:17 | |
| *** erikmwilson has quit IRC | 02:37 | |
| *** erikmwilson has joined #openstack-meeting-4 | 02:37 | |
| *** wxy_ has joined #openstack-meeting-4 | 02:44 | |
| *** hongbin has joined #openstack-meeting-4 | 02:56 | |
| *** FrankZhang_ has quit IRC | 03:01 | |
| *** markvoelker has quit IRC | 03:06 | |
| *** reedip has joined #openstack-meeting-4 | 03:06 | |
| *** erikmwil_ has joined #openstack-meeting-4 | 03:09 | |
| *** erikmwilson has quit IRC | 03:09 | |
| *** FrankZhang has joined #openstack-meeting-4 | 03:13 | |
| *** erikmwil_ has quit IRC | 03:17 | |
| *** FrankZhang has quit IRC | 03:18 | |
| *** pcarver has quit IRC | 03:19 | |
| *** unicell has joined #openstack-meeting-4 | 03:26 | |
| *** bobh has joined #openstack-meeting-4 | 03:26 | |
| *** Jeffrey4l has quit IRC | 03:28 | |
| *** amotoki has quit IRC | 03:32 | |
| *** pcarver has joined #openstack-meeting-4 | 03:32 | |
| *** yfauser has joined #openstack-meeting-4 | 03:33 | |
| *** tovin07_ has joined #openstack-meeting-4 | 03:33 | |
| *** yfauser has quit IRC | 03:38 | |
| *** bobh has quit IRC | 03:39 | |
| *** Jeffrey4l has joined #openstack-meeting-4 | 03:41 | |
| *** hongbin has quit IRC | 03:42 | |
| *** bobh has joined #openstack-meeting-4 | 03:49 | |
| *** amotoki has joined #openstack-meeting-4 | 03:49 | |
| *** amotoki has quit IRC | 03:50 | |
| *** woodard has joined #openstack-meeting-4 | 03:50 | |
| *** amotoki has joined #openstack-meeting-4 | 03:52 | |
| *** amotoki has quit IRC | 03:54 | |
| *** woodard has quit IRC | 03:55 | |
| *** links has joined #openstack-meeting-4 | 03:56 | |
| *** bobh has quit IRC | 03:57 | |
| *** Julien-zte has quit IRC | 04:03 | |
| *** bobh has joined #openstack-meeting-4 | 04:04 | |
| *** Julien-zte has joined #openstack-meeting-4 | 04:04 | |
| *** Julien-zte has quit IRC | 04:04 | |
| *** Julien-zte has joined #openstack-meeting-4 | 04:05 | |
| *** Julien-zte has joined #openstack-meeting-4 | 04:05 | |
| *** Julien-zte has quit IRC | 04:06 | |
| *** Julien-zte has joined #openstack-meeting-4 | 04:06 | |
| *** Julien-zte has quit IRC | 04:06 | |
| *** markvoelker has joined #openstack-meeting-4 | 04:07 | |
| *** Julien-zte has joined #openstack-meeting-4 | 04:07 | |
| *** rfolco has quit IRC | 04:10 | |
| *** bobh has quit IRC | 04:11 | |
| *** markvoelker has quit IRC | 04:13 | |
| *** psachin has joined #openstack-meeting-4 | 04:19 | |
| *** amotoki has joined #openstack-meeting-4 | 04:22 | |
| *** vks1 has joined #openstack-meeting-4 | 04:25 | |
| *** adisky_ has joined #openstack-meeting-4 | 04:26 | |
| *** gongysh has quit IRC | 04:39 | |
| *** amotoki has quit IRC | 04:39 | |
| *** qwebirc76200 has joined #openstack-meeting-4 | 04:44 | |
| *** premsankar has joined #openstack-meeting-4 | 04:45 | |
| *** anilvenkata has joined #openstack-meeting-4 | 04:47 | |
| *** yfauser has joined #openstack-meeting-4 | 04:52 | |
| *** yfauser has quit IRC | 04:57 | |
| *** psachin has quit IRC | 05:00 | |
| *** zhurong has quit IRC | 05:00 | |
| *** david-lyle has quit IRC | 05:04 | |
| *** psachin has joined #openstack-meeting-4 | 05:17 | |
| *** gongysh has joined #openstack-meeting-4 | 05:17 | |
| *** amotoki has joined #openstack-meeting-4 | 05:30 | |
| *** Julien-zte has joined #openstack-meeting-4 | 05:37 | |
| *** Julien-zte has quit IRC | 05:48 | |
| *** Julien-zte has joined #openstack-meeting-4 | 05:49 | |
| *** psachin has quit IRC | 05:49 | |
| *** Julien-zte has quit IRC | 05:51 | |
| *** Julien-zte has joined #openstack-meeting-4 | 05:52 | |
| *** psachin has joined #openstack-meeting-4 | 05:57 | |
| *** yamahata has joined #openstack-meeting-4 | 05:59 | |
| *** amotoki has quit IRC | 06:00 | |
| *** Julien-zte has quit IRC | 06:07 | |
| *** Julien-zte has joined #openstack-meeting-4 | 06:07 | |
| *** markvoelker has joined #openstack-meeting-4 | 06:09 | |
| *** yfauser has joined #openstack-meeting-4 | 06:10 | |
| *** amotoki has joined #openstack-meeting-4 | 06:11 | |
| *** markvoelker has quit IRC | 06:13 | |
| *** yfauser has quit IRC | 06:15 | |
| *** Julien-zte has quit IRC | 06:19 | |
| *** armax has quit IRC | 06:20 | |
| *** yfauser has joined #openstack-meeting-4 | 06:24 | |
| *** unicell1 has joined #openstack-meeting-4 | 06:29 | |
| *** unicell has quit IRC | 06:30 | |
| *** nkrinner_afk is now known as nkrinner | 06:36 | |
| *** yfauser_ has joined #openstack-meeting-4 | 06:36 | |
| *** yfauser has quit IRC | 06:38 | |
| *** SerenaFeng has joined #openstack-meeting-4 | 06:47 | |
| *** SerenaFeng has quit IRC | 06:48 | |
| *** SerenaFeng has joined #openstack-meeting-4 | 06:48 | |
| *** janki has joined #openstack-meeting-4 | 06:49 | |
| *** Julien-zte has joined #openstack-meeting-4 | 06:49 | |
| *** zhurong has joined #openstack-meeting-4 | 06:57 | |
| *** karthiks_afk is now known as karthiks | 07:01 | |
| *** unicell1 has quit IRC | 07:21 | |
| *** alexchadin has joined #openstack-meeting-4 | 07:26 | |
| *** gongysh has quit IRC | 07:34 | |
| *** janki is now known as janki|lunch | 07:34 | |
| *** wxy_ has quit IRC | 07:36 | |
| *** qwebirc76200 has quit IRC | 07:36 | |
| *** wxy has joined #openstack-meeting-4 | 07:36 | |
| *** wxy_ has joined #openstack-meeting-4 | 07:38 | |
| *** premsankar has quit IRC | 07:40 | |
| *** iyamahat has joined #openstack-meeting-4 | 07:42 | |
| *** wxy_ has quit IRC | 07:44 | |
| *** wxy_ has joined #openstack-meeting-4 | 07:44 | |
| *** trinaths has joined #openstack-meeting-4 | 07:45 | |
| *** ltomasbo|away is now known as ltomasbo | 07:45 | |
| *** gongysh has joined #openstack-meeting-4 | 07:50 | |
| *** trinaths has quit IRC | 07:52 | |
| *** woodard has joined #openstack-meeting-4 | 07:54 | |
| *** matrohon has joined #openstack-meeting-4 | 07:55 | |
| *** woodard has quit IRC | 07:58 | |
| *** eyalb has joined #openstack-meeting-4 | 08:00 | |
| *** dwj has joined #openstack-meeting-4 | 08:01 | |
| *** ifat_afek has joined #openstack-meeting-4 | 08:01 | |
| *** matrohon has quit IRC | 08:02 | |
| ifat_afek | Hi, are you in the middle of an ironic meeting? we are supposed to have a Vitrage meeting now | 08:02 |
|---|---|---|
| ifat_afek | UTC+2 | 08:02 |
| ifat_afek | 8:00 UTC+2 | 08:02 |
| *** alexey_weyl has joined #openstack-meeting-4 | 08:03 | |
| *** yujunz has joined #openstack-meeting-4 | 08:03 | |
| ifat_afek | #startmeeting vitrage | 08:04 |
| openstack | Meeting started Wed Mar 15 08:04:03 2017 UTC and is due to finish in 60 minutes. The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:04 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:04 |
| *** openstack changes topic to " (Meeting topic: vitrage)" | 08:04 | |
| openstack | The meeting name has been set to 'vitrage' | 08:04 |
| ifat_afek | Hi :-) | 08:04 |
| yujunz | Hi | 08:04 |
| alexey_weyl | Hi | 08:04 |
| eyalb | \o | 08:04 |
| *** elisha_r has joined #openstack-meeting-4 | 08:05 | |
| elisha_r | hi | 08:05 |
| *** pcaruana has joined #openstack-meeting-4 | 08:05 | |
| ifat_afek | Today’s agenda: | 08:06 |
| ifat_afek | •Pike Design Sessions | 08:06 |
| ifat_afek | •Status and Updates | 08:06 |
| ifat_afek | •Boston Summit | 08:06 |
| ifat_afek | •Open Discussion | 08:06 |
| ifat_afek | #topic Pike Design Sessions | 08:06 |
| *** openstack changes topic to "Pike Design Sessions (Meeting topic: vitrage)" | 08:06 | |
| ifat_afek | I think that the Pike Design Sessions were very successful. Thanks to everyone who contributed! | 08:06 |
| ifat_afek | The etherpad with the discussions summary: | 08:06 |
| ifat_afek | #link https://etherpad.openstack.org/p/vitrage-pike-design-sessions | 08:06 |
| ifat_afek | \ | 08:06 |
| yujunz | Is the pike roadmap published? I mean the slides shown on the close | 08:07 |
| *** dwj_ has joined #openstack-meeting-4 | 08:07 | |
| *** joedborg has joined #openstack-meeting-4 | 08:07 | |
| *** dwj has quit IRC | 08:08 | |
| ifat_afek | I wrote it all in the etherpad, but did not publish anywhere else. I guess it belongs in Vitrage wiki page. I’ll update it after the wiki | 08:08 |
| yujunz | Got it | 08:09 |
| yujunz | Starting on L184 | 08:09 |
| ifat_afek | Right | 08:09 |
| *** markvoelker has joined #openstack-meeting-4 | 08:10 | |
| ifat_afek | #topic Status and Updates | 08:10 |
| *** openstack changes topic to "Status and Updates (Meeting topic: vitrage)" | 08:10 | |
| ifat_afek | My updates: Working on Doctor stuff. I finished writing the manual installation instructions, and it was merged | 08:10 |
| ifat_afek | I’m almost done with the test script as well. | 08:10 |
| ifat_afek | #link https://gerrit.opnfv.org/gerrit/#/c/28593/ | 08:11 |
| ifat_afek | #link https://gerrit.opnfv.org/gerrit/#/c/28845/ | 08:11 |
| ifat_afek | Note that Andrea Wisnyei is working on the “real” Vitrage installation guide. | 08:11 |
| ifat_afek | That’s it for my updates | 08:11 |
| eyalb | I will update | 08:11 |
| eyalb | I have been working several days now to fix the puppet-openstack-integration for vitrage | 08:12 |
| eyalb | the smoke test failed | 08:12 |
| eyalb | I did some fixes in vitrage tempest tests and in the puppet moudle | 08:12 |
| eyalb | I am waiting for the changes to be merged to RDO ci system and then I will recheck | 08:13 |
| eyalb | hopefully it will work this time :-) | 08:13 |
| eyalb | thats it | 08:13 |
| ifat_afek | Good luck ;-) | 08:13 |
| *** markvoelker has quit IRC | 08:14 | |
| elisha_r | I'll update for Anna Reznikov | 08:15 |
| elisha_r | She pushed a BP for the Vitrage support for SNMP traps. I believe the code was pushed a week or two ago | 08:15 |
| yujunz | SNMP traps as a notifier, right? | 08:16 |
| *** iyamahat has quit IRC | 08:17 | |
| elisha_r | For those who don't know, this means that if you activate this feature, you can get SNMPv2 traps sent to locations that the user defines | 08:17 |
| elisha_r | yup, it's another notifier | 08:17 |
| elisha_r | traps will be generated whenever a vitrage deduced alarm is generated | 08:18 |
| elisha_r | not for other alarms | 08:18 |
| elisha_r | like Zabbix, nagios etc | 08:18 |
| elisha_r | anyhow, this feature should now be fully functional. See the BP for details. | 08:19 |
| ifat_afek | Links to Anna’s changes: | 08:19 |
| elisha_r | I'm done | 08:19 |
| ifat_afek | #link https://review.openstack.org/#/c/437397/ | 08:19 |
| ifat_afek | #link https://review.openstack.org/#/c/445574/ | 08:19 |
| ifat_afek | elisha_r: thanks | 08:19 |
| ifat_afek | Anyone else has updates? | 08:20 |
| yujunz | I will | 08:20 |
| alexey_weyl | I am still working on the 'not' operator for the templates and the evaluator | 08:20 |
| alexey_weyl | Hopefully it ill be done till the end of the week. | 08:20 |
| yujunz | Made some progress on mitmstack. It now supports multiplying the result of `nova list` | 08:21 |
| alexey_weyl | I really want to finish it because it takes too much time already | 08:21 |
| alexey_weyl | Done | 08:22 |
| ifat_afek | alexey_weyl: Great, thanks | 08:22 |
| yujunz | Ok, I'll continue | 08:22 |
| ifat_afek | yujunz: So you mean it can already return 10000 fake vms? | 08:22 |
| yujunz | If you have n vm, mitmstack can return n*m vms for you | 08:22 |
| ifat_afek | Cool | 08:22 |
| *** SerenaFeng has quit IRC | 08:22 | |
| yujunz | #link https://github.com/mitmstack/cheat-the-client | 08:23 |
| *** usman_ has joined #openstack-meeting-4 | 08:23 | |
| *** efoley__ has joined #openstack-meeting-4 | 08:23 | |
| yujunz | #undo | 08:23 |
| yujunz | #link https://github.com/mitmstack/cheat-the-client/blob/master/multiply.py | 08:23 |
| yujunz | Currently the it fakes only the 'id' | 08:24 |
| yujunz | So we get different 'id' on the faked list | 08:24 |
| yujunz | A question on vitrage | 08:24 |
| *** SerenaFeng has joined #openstack-meeting-4 | 08:24 | |
| yujunz | does it supports http_proxy for the openstack endpoints | 08:24 |
| eyalb | I am not aware of such a feature | 08:25 |
| ifat_afek | yujunz: What do you mean exactly? | 08:25 |
| *** salmankhan has joined #openstack-meeting-4 | 08:26 | |
| yujunz | When vitrage requests vm list from nova, go through http_proxy if env var is set | 08:26 |
| yujunz | nova client supports it well | 08:26 |
| yujunz | #link https://github.com/mitmstack/cheat-the-client#nova-list-multiplier | 08:26 |
| yujunz | Note the difference between first `nova list` and second one | 08:27 |
| eyalb | what ever url you define for vitrage in the catalog it will be used | 08:27 |
| eyalb | I will check the link | 08:27 |
| *** iyamahat has joined #openstack-meeting-4 | 08:27 | |
| yujunz | The same url, but go through http proxy | 08:27 |
| *** zhurong has quit IRC | 08:28 | |
| yujunz | nova client will check the environment var http_proxy to determine how to make the request | 08:28 |
| eyalb | no we don't support it | 08:28 |
| yujunz | I see | 08:28 |
| ifat_afek | yujunz: Is it supported in other projects? | 08:28 |
| yujunz | nova client supports it well | 08:28 |
| ifat_afek | Except Nova? I mean, is it something common? | 08:28 |
| yujunz | I didn't test other | 08:29 |
| ifat_afek | Because we were not aware of it | 08:29 |
| yujunz | But I assume it is a common feature | 08:29 |
| ifat_afek | And what is the goal - do you want Vitrage to call Nova via the proxy? or do you want to call Vitrage via the proxy? | 08:29 |
| yujunz | The former | 08:30 |
| yujunz | vitrage call nova via proxy | 08:30 |
| ifat_afek | I guess in order to make it consistent with the result that mitmstack gets? | 08:30 |
| ifat_afek | And to allow mitmstack to mess with the results | 08:30 |
| *** salmankhan has quit IRC | 08:31 | |
| yujunz | Kind of, force vitrage to go through mitmstack to nova | 08:31 |
| yujunz | setting http_proxy is easiest to deploy | 08:31 |
| *** yamahata has quit IRC | 08:31 | |
| ifat_afek | Ok | 08:31 |
| ifat_afek | I think I understand | 08:31 |
| *** d0ugal has joined #openstack-meeting-4 | 08:31 | |
| yujunz | I'll check and submit a patch to support http_proxy in vitrage | 08:32 |
| ifat_afek | Ok | 08:32 |
| yujunz | It won't be too difficult since it should be supported by most client library | 08:32 |
| yujunz | That's all from my side | 08:32 |
| eyalb | I think it is supported by the requests library which we use | 08:32 |
| *** iyamahat has quit IRC | 08:33 | |
| eyalb | so maybe it is supported | 08:33 |
| eyalb | it needs to be checked | 08:33 |
| eyalb | #link http://docs.python-requests.org/en/latest/user/advanced/#proxies | 08:33 |
| yujunz | Could be. Not sure about the default behavior. | 08:33 |
| ifat_afek | Any other updates? | 08:34 |
| *** salmankhan has joined #openstack-meeting-4 | 08:34 | |
| *** amotoki has quit IRC | 08:35 | |
| usman_ | Ifat: is there any comment or suggestion for virtual switch extension in Vitrage? | 08:35 |
| ifat_afek | usman_: Hi, I’m sorry but I still don’t have answer. I think the suggestion makes sense, but would like to discuss it with someone else (who is not in the IRC channel now) | 08:36 |
| *** limao has quit IRC | 08:36 | |
| ifat_afek | BTW, you can send it also to the general mailing list with [vitrage] in the title, if you want to hear other opinions | 08:37 |
| *** limao has joined #openstack-meeting-4 | 08:37 | |
| *** alexchadin has quit IRC | 08:37 | |
| ifat_afek | And in any case I will reply to your mail soon | 08:37 |
| usman_ | Ifat: okay thanks | 08:37 |
| ifat_afek | Any other issues to discuss before I move on to the next topic? | 08:38 |
| ifat_afek | #topic Boston Summit | 08:38 |
| *** openstack changes topic to "Boston Summit (Meeting topic: vitrage)" | 08:38 | |
| ifat_afek | There will be six Vitrage sessions in the Boston Summit! | 08:38 |
| alexey_weyl | wohoooooooooooo | 08:39 |
| eyalb | \0/ | 08:39 |
| ifat_afek | Here they are: | 08:39 |
| alexey_weyl | Way the go Vitrage!!! | 08:39 |
| ifat_afek | #link https://www.openstack.org/summit/boston-2017/summit-schedule/events/17926/beyond-automation-taking-vitrage-into-the-realm-of-machine-learning | 08:39 |
| ifat_afek | #link https://www.openstack.org/summit/boston-2017/summit-schedule/events/17737/collectd-and-vitrage-integration-an-eventful-presentation | 08:39 |
| ifat_afek | #link https://www.openstack.org/summit/boston-2017/summit-schedule/events/17928/the-vitrage-story-from-nothing-to-the-big-tent | 08:39 |
| ifat_afek | #link https://www.openstack.org/summit/boston-2017/summit-schedule/events/17922/advanced-use-cases-for-root-cause-analysis | 08:39 |
| ifat_afek | #link https://www.openstack.org/summit/boston-2017/summit-schedule/events/18067/get-hands-on-with-vitrage-the-fault-management-service-for-root-cause-analysis-and-deduced-alarms | 08:39 |
| *** salmankhan has quit IRC | 08:39 | |
| ifat_afek | #link https://www.openstack.org/summit/boston-2017/summit-schedule/events/18595/project-update-vitrage | 08:39 |
| ifat_afek | In addition, we can (and should) suggest ideas for the Forum sessions. As far as I understood, a forum session is similar to the fishbowl session we had in Barcelona – a high level discussion, either about cross-project topics, or about a project specific issues | 08:40 |
| yujunz | cool | 08:40 |
| ifat_afek | #link https://wiki.openstack.org/wiki/Forum | 08:40 |
| ifat_afek | I created an etherpad for gathering ideas. Please add yours: | 08:40 |
| ifat_afek | #link https://etherpad.openstack.org/p/vitrage-boston-forum-ideas | 08:40 |
| ifat_afek | I just created the etherpad, didn’t have time to think of ideas yet… | 08:40 |
| ifat_afek | Sorry for not talking, I was writing in the etherpad… | 08:44 |
| ifat_afek | Moving on | 08:45 |
| ifat_afek | #topic Open Discussion | 08:45 |
| *** openstack changes topic to "Open Discussion (Meeting topic: vitrage)" | 08:45 | |
| ifat_afek | There is one issue I would like to raise – our review policy. | 08:45 |
| ifat_afek | Usually we write our comments, and wait for the committer to fix them | 08:46 |
| ifat_afek | On other OpenStack projects, people write -1/-2 when they have comments. This prevents other reviewers from mistakenly merging a change that is not ready yet | 08:46 |
| ifat_afek | I think we should start replying with -1/-2 as well. What do you think? | 08:46 |
| eyalb | +1 | 08:46 |
| eyalb | use more -1 | 08:46 |
| alexey_weyl | I agree | 08:46 |
| alexey_weyl | +1 | 08:46 |
| eyalb | -2 is rarely used | 08:47 |
| alexey_weyl | unless it is a very small issue I believe we can use 0 as well | 08:47 |
| alexey_weyl | In my opinion | 08:47 |
| ifat_afek | Ok. That’s it for me. Anyone wants to discuss anything else? | 08:49 |
| *** matrohon has joined #openstack-meeting-4 | 08:50 | |
| ifat_afek | Goodbye then! | 08:50 |
| eyalb | bye | 08:51 |
| alexey_weyl | see ya | 08:51 |
| *** alexey_weyl has quit IRC | 08:51 | |
| usman_ | bye | 08:51 |
| ifat_afek | #endmeeting | 08:51 |
| *** openstack changes topic to " (Meeting topic: ironic_neutron)" | 08:51 | |
| openstack | Meeting ended Wed Mar 15 08:51:25 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 08:51 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-03-15-08.04.html | 08:51 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-03-15-08.04.txt | 08:51 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-03-15-08.04.log.html | 08:51 |
| *** eyalb has left #openstack-meeting-4 | 08:51 | |
| *** alexchadin has joined #openstack-meeting-4 | 08:54 | |
| *** ralonsoh has joined #openstack-meeting-4 | 08:55 | |
| *** Julien-zte has quit IRC | 08:56 | |
| *** Julien-zte has joined #openstack-meeting-4 | 09:00 | |
| *** bogdando has joined #openstack-meeting-4 | 09:01 | |
| *** yujunz has quit IRC | 09:09 | |
| *** bogdando has quit IRC | 09:19 | |
| *** bogdando has joined #openstack-meeting-4 | 09:19 | |
| *** zhurong has joined #openstack-meeting-4 | 09:28 | |
| *** Julien-zte has quit IRC | 09:33 | |
| *** dwj_ has quit IRC | 09:33 | |
| *** alexchadin has quit IRC | 09:36 | |
| *** neiljerram has joined #openstack-meeting-4 | 09:37 | |
| *** zhurong has quit IRC | 09:38 | |
| *** zhurong has joined #openstack-meeting-4 | 09:43 | |
| *** elisha_r has quit IRC | 09:46 | |
| *** zhurong has quit IRC | 09:53 | |
| *** dmellado has quit IRC | 09:54 | |
| *** rwallner has quit IRC | 09:54 | |
| *** ltomasbo has quit IRC | 09:54 | |
| *** ltomasbo|away has joined #openstack-meeting-4 | 10:00 | |
| *** dmellado has joined #openstack-meeting-4 | 10:02 | |
| *** ifat_afek has left #openstack-meeting-4 | 10:02 | |
| *** pbourke has quit IRC | 10:04 | |
| *** pbourke has joined #openstack-meeting-4 | 10:04 | |
| *** salmankhan has joined #openstack-meeting-4 | 10:05 | |
| *** limao has quit IRC | 10:05 | |
| *** tovin07_ has quit IRC | 10:05 | |
| *** limao has joined #openstack-meeting-4 | 10:05 | |
| *** SerenaFeng has quit IRC | 10:07 | |
| *** salmankhan has quit IRC | 10:09 | |
| *** limao has quit IRC | 10:10 | |
| *** markvoelker has joined #openstack-meeting-4 | 10:10 | |
| *** ltomasbo|away is now known as ltomasbo | 10:12 | |
| *** markvoelker has quit IRC | 10:15 | |
| *** rfolco has joined #openstack-meeting-4 | 10:19 | |
| *** joedborg has quit IRC | 10:26 | |
| *** sdague has joined #openstack-meeting-4 | 10:27 | |
| *** joedborg has joined #openstack-meeting-4 | 10:30 | |
| *** janonymous has joined #openstack-meeting-4 | 10:42 | |
| *** SerenaFeng has joined #openstack-meeting-4 | 10:55 | |
| *** janki|lunch has quit IRC | 10:59 | |
| *** janki|lunch has joined #openstack-meeting-4 | 11:00 | |
| *** rwallner has joined #openstack-meeting-4 | 11:00 | |
| *** gongysh has quit IRC | 11:01 | |
| *** Julien-zte has joined #openstack-meeting-4 | 11:01 | |
| *** SerenaFeng has quit IRC | 11:10 | |
| *** amotoki has joined #openstack-meeting-4 | 11:14 | |
| *** jchhatbar has joined #openstack-meeting-4 | 11:20 | |
| *** jchhatbar is now known as janki | 11:20 | |
| *** amotoki has quit IRC | 11:21 | |
| *** janki|lunch has quit IRC | 11:22 | |
| *** psachin has quit IRC | 11:30 | |
| *** psachin has joined #openstack-meeting-4 | 11:30 | |
| *** ralonsoh has quit IRC | 11:32 | |
| *** rwallner has quit IRC | 11:36 | |
| *** amotoki has joined #openstack-meeting-4 | 11:38 | |
| *** amotoki has quit IRC | 11:48 | |
| *** bobh has joined #openstack-meeting-4 | 11:54 | |
| *** bobh has quit IRC | 11:54 | |
| *** bobh has joined #openstack-meeting-4 | 11:55 | |
| *** alexchadin has joined #openstack-meeting-4 | 11:57 | |
| *** rwallner has joined #openstack-meeting-4 | 12:03 | |
| *** SerenaFeng has joined #openstack-meeting-4 | 12:08 | |
| *** vks1 has quit IRC | 12:11 | |
| *** markvoelker has joined #openstack-meeting-4 | 12:11 | |
| *** gongysh has joined #openstack-meeting-4 | 12:12 | |
| *** markvoelker has quit IRC | 12:16 | |
| *** bobh has quit IRC | 12:17 | |
| *** bobh has joined #openstack-meeting-4 | 12:19 | |
| *** SerenaFeng has quit IRC | 12:19 | |
| *** rbak_ has quit IRC | 12:19 | |
| *** rbak_ has joined #openstack-meeting-4 | 12:20 | |
| *** bobh has quit IRC | 12:26 | |
| *** shintaro has joined #openstack-meeting-4 | 12:27 | |
| *** Julien-zte has quit IRC | 12:32 | |
| *** woodard has joined #openstack-meeting-4 | 12:33 | |
| *** woodard has quit IRC | 12:35 | |
| *** woodard has joined #openstack-meeting-4 | 12:35 | |
| *** baoli has joined #openstack-meeting-4 | 12:36 | |
| *** cathrich_ has quit IRC | 12:36 | |
| *** markvoelker has joined #openstack-meeting-4 | 12:38 | |
| *** baoli has quit IRC | 12:39 | |
| *** baoli has joined #openstack-meeting-4 | 12:40 | |
| *** Julien-zte has joined #openstack-meeting-4 | 12:41 | |
| *** janonymous has quit IRC | 12:44 | |
| *** baoli has quit IRC | 12:44 | |
| *** klamath has joined #openstack-meeting-4 | 12:45 | |
| *** klamath has quit IRC | 12:45 | |
| *** klamath has joined #openstack-meeting-4 | 12:46 | |
| *** usman_ has quit IRC | 12:51 | |
| *** reedip has quit IRC | 12:52 | |
| *** SerenaFeng has joined #openstack-meeting-4 | 12:53 | |
| *** SerenaFeng has quit IRC | 12:54 | |
| *** wxy_ has quit IRC | 12:54 | |
| *** ostroverkhov has joined #openstack-meeting-4 | 12:54 | |
| *** reedip has joined #openstack-meeting-4 | 12:54 | |
| *** efoley_ has joined #openstack-meeting-4 | 12:55 | |
| *** wxy_ has joined #openstack-meeting-4 | 12:56 | |
| *** SerenaFeng has joined #openstack-meeting-4 | 12:57 | |
| *** efoley__ has quit IRC | 12:58 | |
| *** mriedem has joined #openstack-meeting-4 | 12:58 | |
| alex_xu | #startmeeting nova api | 13:00 |
| openstack | Meeting started Wed Mar 15 13:00:03 2017 UTC and is due to finish in 60 minutes. The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:00 |
| *** 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 |
| *** ostroverkhov has left #openstack-meeting-4 | 13:00 | |
| sdague | o/ | 13:00 |
| *** dtardivel has joined #openstack-meeting-4 | 13:00 | |
| *** efoley__ has joined #openstack-meeting-4 | 13:01 | |
| alex_xu | I guess johnthetubaguy still in lunch | 13:01 |
| johnthetubaguy | o/ | 13:01 |
| alex_xu | ok :) | 13:01 |
| alex_xu | #topic priorities | 13:01 |
| *** openstack changes topic to "priorities (Meeting topic: nova api)" | 13:01 | |
| alex_xu | #link https://etherpad.openstack.org/p/pike-nova-priorities-tracking | 13:01 |
| alex_xu | beside policy, just want to mention, this API spec looks like very close https://review.openstack.org/265282 | 13:02 |
| *** links has quit IRC | 13:02 | |
| *** efoley__ has quit IRC | 13:02 | |
| *** efoley__ has joined #openstack-meeting-4 | 13:03 | |
| sdague | alex_xu: cool, will need to revisit that one | 13:03 |
| johnthetubaguy | oops, i should hit that one | 13:03 |
| alex_xu | sdague: yea, just for you and johnthetubaguy :) | 13:03 |
| johnthetubaguy | there was another, just trying to find it | 13:04 |
| *** efoley_ has quit IRC | 13:04 | |
| alex_xu | for the policy, maybe we should adverties the doc one in the nova weekly meeting, that is simple and can be merge quick | 13:04 |
| *** efoley__ has quit IRC | 13:04 | |
| *** efoley_ has joined #openstack-meeting-4 | 13:04 | |
| johnthetubaguy | #link https://review.openstack.org/#/c/440580/ | 13:04 |
| johnthetubaguy | alex_xu: a good idea, been trying to bug folks directly too | 13:04 |
| *** SerenaFeng has quit IRC | 13:04 | |
| gmann | this one also very close, #link https://review.openstack.org/#/c/415315/ | 13:05 |
| alex_xu | ah, yea, i forget to revisit that one | 13:05 |
| gmann | johnthetubaguy: you had +2 then some trivial updates | 13:05 |
| *** jed56 has joined #openstack-meeting-4 | 13:06 | |
| alex_xu | so we want to have a limit dict for the response of hints? | 13:06 |
| *** jed56 has quit IRC | 13:06 | |
| *** jed56 has joined #openstack-meeting-4 | 13:06 | |
| alex_xu | I guess no, that isn't match the request | 13:06 |
| *** SerenaFeng has joined #openstack-meeting-4 | 13:06 | |
| alex_xu | gmann: thanks | 13:07 |
| alex_xu | gmann: i put it in the therpad | 13:07 |
| johnthetubaguy | alex_xu: what limit do you mean? | 13:07 |
| johnthetubaguy | I think we have a limit on the size of the tag, and limit on the number of tags anyways, so that should just carry over here | 13:08 |
| alex_xu | johnthetubaguy: the scheduler hints schema have 'addtionalProperties': True | 13:08 |
| johnthetubaguy | oh right | 13:08 |
| alex_xu | that means user can put anything into the hints, and that store in the db, and can be get from the response | 13:08 |
| johnthetubaguy | we left that as an extension point, mostly until we have traits sorted I guess | 13:08 |
| alex_xu | another open metadata api | 13:08 |
| johnthetubaguy | yeah, it kinda is open | 13:08 |
| johnthetubaguy | do we limit the number of scheduler hits you can set? | 13:09 |
| alex_xu | good news, the hints can't update | 13:09 |
| * mriedem sneaks in late | 13:09 | |
| johnthetubaguy | alex_xu: yeah | 13:09 |
| *** pmesserli has joined #openstack-meeting-4 | 13:09 | |
| alex_xu | I think no, just limit by the length of request body | 13:09 |
| johnthetubaguy | hmm, probably should fix that up | 13:10 |
| johnthetubaguy | tags has a limit of 50 | 13:10 |
| alex_xu | then I will drop in the question whether we need microversion :) i hate that question | 13:10 |
| johnthetubaguy | I think we can pretend its a security fix, but I am willing to have that shot down | 13:11 |
| *** reedip has quit IRC | 13:11 | |
| *** liangy has joined #openstack-meeting-4 | 13:11 | |
| mriedem | what is the question/issue? | 13:11 |
| *** cathrichardson has joined #openstack-meeting-4 | 13:11 | |
| johnthetubaguy | bigger question, do we want to fix up the scheduler hint limit before we allow the adding of the GET api? | 13:12 |
| johnthetubaguy | mriedem: scheduler hit spec, link is above | 13:12 |
| mriedem | right, but summarize? | 13:12 |
| johnthetubaguy | you can set an unlimited number of hints today | 13:13 |
| mriedem | this is the one that's proposing to return scheduler hints from the original instance build request right? | 13:13 |
| johnthetubaguy | then we start returning them too | 13:13 |
| johnthetubaguy | yeah | 13:13 |
| mriedem | so the GET response could have a million hints in it | 13:13 |
| *** erikmwilson has joined #openstack-meeting-4 | 13:13 | |
| alex_xu | mriedem: the hints in the request is open for any key-value, and then can get from the API response from that spec | 13:13 |
| *** baoli has joined #openstack-meeting-4 | 13:13 | |
| mriedem | what is the size on the key/value? | 13:14 |
| sdague | johnthetubaguy: is there a reason why it's in the server document instead of dedicated sub resource? | 13:14 |
| mriedem | sdague: they're following the flavors spec | 13:14 |
| mriedem | flavors in server response | 13:14 |
| alex_xu | no limit as i know | 13:14 |
| sdague | I get the idea of why we'd roll flavor up here, because everyone has flavors | 13:14 |
| sdague | but scheduler hints seem really specific, and only some percentage of applications is going to be using them | 13:15 |
| mriedem | alex_xu: what table stores scheduler hints anyway? request_specs? | 13:15 |
| *** reedip has joined #openstack-meeting-4 | 13:15 | |
| *** cathrichardson has left #openstack-meeting-4 | 13:15 | |
| *** cdent has joined #openstack-meeting-4 | 13:15 | |
| johnthetubaguy | we kinda agreed to it at the PTG, on the basis of what goes in, should usually come out somehow | 13:15 |
| mriedem | "somehow" could be a subresource, | 13:15 |
| mriedem | is i think sean's point | 13:15 |
| sdague | right | 13:15 |
| *** shintaro has quit IRC | 13:15 | |
| mriedem | and doesn't clutter up the main, already large, response | 13:15 |
| johnthetubaguy | oh, I missed what you meant there, that does make sense | 13:16 |
| sdague | I think the important difference between flavor and scheduler hints | 13:16 |
| sdague | *everyone* has a flavor | 13:16 |
| johnthetubaguy | sdague: yeah, that makes good sense | 13:16 |
| sdague | *only some instances* have hints set | 13:16 |
| johnthetubaguy | I don't think its needed in /servers/detail either | 13:16 |
| sdague | right | 13:16 |
| * johnthetubaguy wishes he didn't always forget about the sub resource as an option | 13:17 | |
| sdague | johnthetubaguy: the use case for this is? | 13:17 |
| alex_xu | mriedem: yea, i guess in request spec | 13:17 |
| * alex_xu always forget those detail | 13:17 | |
| mriedem | sdague: rebuilding an instance using the same hints as before | 13:17 |
| johnthetubaguy | sdague: I think it was launching another VM that is similar | 13:17 |
| mriedem | was what i remember from the ptg | 13:17 |
| mriedem | *not rebuilding, duplicating | 13:18 |
| johnthetubaguy | or working out what state your instance groups are in, I guess | 13:18 |
| johnthetubaguy | well, server groups | 13:18 |
| mriedem | hmm, | 13:19 |
| mriedem | the request_spec is not scoped to an instance, | 13:19 |
| mriedem | oh wait yes it is | 13:19 |
| sdague | where is this sitting the db models? | 13:19 |
| mriedem | so we get the request_spec by instance_uuid from the api db, | 13:19 |
| mriedem | deserialize the blob, | 13:20 |
| mriedem | pull out the scheduler hints, and return those in the response | 13:20 |
| mriedem | so yeah there is no key/value size limit on the hints in the db | 13:20 |
| alex_xu | can we query the member of server-group by /server-groups api? | 13:20 |
| johnthetubaguy | mriedem: yeah, I think thats all correct | 13:20 |
| mriedem | we have some known in-tree hints in the json schema validation, | 13:20 |
| mriedem | but additionalProperties=True | 13:21 |
| mriedem | so it's totally open ended | 13:21 |
| gmann | yea | 13:21 |
| johnthetubaguy | +1 | 13:21 |
| mriedem | i could build a server with a million-char key/value | 13:21 |
| johnthetubaguy | +1 for that being the current state, not +1 for keeping it like that | 13:21 |
| mriedem | right, i'm just getting caught up, | 13:21 |
| mriedem | seems we should limit the size of the key/value in the request schema, | 13:21 |
| johnthetubaguy | mriedem: thats probably a security related bug, all bit not a major one | 13:21 |
| mriedem | and as for the total number of hints per request, we could use quota like we do for metadata | 13:21 |
| johnthetubaguy | mriedem: +1 I was suggesting we follow tags with a static 50 limit | 13:22 |
| alex_xu | +1 for a hard-code number | 13:22 |
| johnthetubaguy | metadata I think is a quota based limit, which feels like overkill as a starting point | 13:22 |
| mriedem | i was thinking metadata, which is i think 255 | 13:22 |
| sdague | mriedem: well, if this is just a GET, what is the limit concern? | 13:22 |
| johnthetubaguy | mriedem: Oh, you mean the string lenght? | 13:22 |
| *** vks1 has joined #openstack-meeting-4 | 13:22 | |
| mriedem | johnthetubaguy: yeah | 13:22 |
| mriedem | do we leave the string length on the key/values unbounded? | 13:23 |
| johnthetubaguy | mriedem: I was thinking the number of strings, but both need fixing I gues | 13:23 |
| sdague | mriedem: it already is right? | 13:23 |
| johnthetubaguy | mriedem: I thought the DB limited that, but maybe I miss-remembered that | 13:23 |
| *** limao has joined #openstack-meeting-4 | 13:23 | |
| mriedem | this is stored in the request_specs table in a json blob, | 13:23 |
| sdague | so, I'm still trying to figure out where this is stored. Is this just jammed into user_data? | 13:23 |
| mriedem | in a Text field, so there is a limit in the db, but it's rather large | 13:24 |
| johnthetubaguy | oh right | 13:24 |
| mriedem | sdague: request_specs, | 13:24 |
| mriedem | nova_api db | 13:24 |
| mriedem | https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api_models.py#L171 | 13:24 |
| alex_xu | ah | 13:24 |
| sdague | oh, api_models.py | 13:24 |
| mriedem | the RequestSpec object serializes/deserializes from the json blob | 13:24 |
| *** psachin has quit IRC | 13:24 | |
| sdague | when are request specs deleted? | 13:24 |
| mriedem | i wouldn't be surprised if they aren't, but would need to check | 13:25 |
| alex_xu | i guess there will be 500 when over the Text field limit | 13:25 |
| mriedem | alex_xu: yup | 13:26 |
| mriedem | bauzas: are request_specs ever deleted? | 13:26 |
| mriedem | they are in the api db so when we delete an instance we're in the wrong db to clean those up | 13:26 |
| sdague | I think my biggest concern to exposing this is that it locks us into lifecycle management constraints on that | 13:27 |
| sdague | because it's in a different table | 13:27 |
| sdague | in the flavor case, it's all super easy, because it's in the same tabl | 13:27 |
| mriedem | well, not really, | 13:28 |
| mriedem | flavors are in instance_extra | 13:28 |
| mriedem | but same db :) | 13:28 |
| mriedem | from what i can tell, we never delete request_specs records | 13:28 |
| sdague | mriedem: ok, well in a table linked to the instance pretty strongly | 13:28 |
| mriedem | so i can fill up your api db with just bogus server build requests with a million hints | 13:28 |
| sdague | mriedem: right, I'm sure we're going to have to solve that | 13:28 |
| mriedem | i suppose i should open a bug | 13:29 |
| johnthetubaguy | yeah, bug time for sure | 13:29 |
| gmann | but if limiting to 50 is not too much ? does anyone use 50 hints all together ? | 13:29 |
| johnthetubaguy | mriedem: quota does usually limit these attacks though | 13:30 |
| johnthetubaguy | gmann: does it matter? its about the next instance that gets created really | 13:30 |
| johnthetubaguy | if we break that person, its a good fix | 13:30 |
| sdague | honestly, I'm less concerned on the limit here | 13:31 |
| alex_xu | sdague: what is your main concern? | 13:31 |
| mriedem | johnthetubaguy: we don't have quotas on hints do we? | 13:31 |
| sdague | honestly, I just wonder about exposing this | 13:32 |
| johnthetubaguy | mriedem: I mean on build instance | 13:32 |
| sdague | I do get that "it would be nice" | 13:32 |
| alex_xu | sdague: if expose it just for server-group...then we have /server-groups API | 13:32 |
| sdague | but, I also think that anyone that's actively using scheduler hints, isn't doing them in an add hoc way | 13:32 |
| sdague | they are doing them with a system to coordinate them | 13:32 |
| mriedem | johnthetubaguy: i'm saying, single server create request, with a scheduler hints dict with a million keys in it | 13:33 |
| mriedem | we don't have quota limits on hints | 13:33 |
| johnthetubaguy | mriedem: I couldn't find where the that DB entry is deleted either | 13:33 |
| gmann | why people want that use case implement new sch hint as "same_scheduler_hint" like same_host | 13:33 |
| mriedem | like we do for metadata or injected files | 13:33 |
| sdague | and so using nova as redundant key retreival for this seems... odd | 13:33 |
| johnthetubaguy | mriedem: sorry, yep +1 that | 13:33 |
| sdague | gmann: right, but if they launched that server from their program, they know what hints those were | 13:33 |
| sdague | the only real case is when Bob manually does an ``openstack server create .... hints`` | 13:34 |
| sdague | outside of a programatic environment | 13:34 |
| gmann | humm | 13:34 |
| sdague | then Jane wants to duplicate that | 13:34 |
| sdague | which, seems like a nice thing to do, but doesn't seem urgent | 13:34 |
| mriedem | i don't want to make assumptions on the usefulness or use case for this, | 13:35 |
| sdague | especially if we want to spend brain power around quotas / policy | 13:35 |
| gmann | if nova implement that sch hint so that Jane can use that sch hint and nova internally does magic at very starting | 13:35 |
| johnthetubaguy | sdague: thats basically what I was thinking too, nice to have, acceptable, but not urgent | 13:35 |
| mriedem | if we want to know if this is a silly idea, we should ask the ops list | 13:35 |
| sdague | mriedem: well, it's a trade off. How many hours are we going to spend on this one. | 13:35 |
| johnthetubaguy | we have that feedback at the PTG already, saying it was useful for the folks in the room | 13:35 |
| johnthetubaguy | not sure it was urgent as such | 13:36 |
| mriedem | it seems relatively straight-forward if we agree on where it lives in the REST API (subresource or not), | 13:36 |
| mriedem | i think the quota limit and deleting request specs are separate issues that need to be dealt with anyway | 13:36 |
| mriedem | as bugs | 13:36 |
| sdague | johnthetubaguy: do we have ideas about who those folks were, and vs. policy or other things | 13:36 |
| mriedem | i think it was a team working with gibi | 13:36 |
| mriedem | so probably related to ericsson and telcos | 13:37 |
| johnthetubaguy | sdague: I thought it was chris f as well? | 13:37 |
| mriedem | so do we want to take a couple of actions and move on? | 13:37 |
| mriedem | 1. ask the ops list about usefulness of this? | 13:37 |
| mriedem | 2. report bugs for the limits/delete issue? | 13:37 |
| mriedem | and make the bugs a prerequisite for the api change? | 13:38 |
| mriedem | if we do the api chngae | 13:38 |
| mriedem | *change | 13:38 |
| sdague | I want a more comprehensive use case | 13:38 |
| sdague | I just left -1 feedback for that | 13:38 |
| johnthetubaguy | yup, agreement on 2 seemed important | 13:38 |
| sdague | the current use case is just "I want to get this out of nova" | 13:38 |
| johnthetubaguy | sdague: better use case makes good sense | 13:38 |
| sdague | That's not a use case | 13:38 |
| alex_xu | +1 for #2 should be fixed | 13:38 |
| johnthetubaguy | sdague: did you add about the sub resource thing as well? | 13:39 |
| mriedem | #action mriedem to open bugs for lack of limits on scheduler hints and a bug about how we never delete request_specs | 13:39 |
| gmann | yea, it really save to blowup the DB | 13:39 |
| sdague | I did not, because I think that until there is a more detailed use case I'm -1 regardless | 13:39 |
| edleafe | sdague: when migrating an instances, wouldn't the hints be necessary to ensure that it lands on a host that meets the original requirements? | 13:39 |
| edleafe | s/instances/instance | 13:39 |
| sdague | edleafe: I think that's a different issue | 13:40 |
| johnthetubaguy | sdague: fair enough | 13:40 |
| sdague | migrating an instance should keep the hints, the user shouldn't have to respecify them | 13:40 |
| mriedem | edleafe: we already pull the hints when migrating | 13:40 |
| gmann | and limit on sch hint as version bump right or we can discuss on bug anyways | 13:40 |
| mriedem | from the request spec | 13:40 |
| johnthetubaguy | edleafe: that already all fixed I believe, ask bauzas for details | 13:40 |
| mriedem | sdague: that's how it already works i think, yeah | 13:40 |
| edleafe | mriedem: ah, ok | 13:40 |
| alex_xu | i guess we can move on, as we said, this isn't urgent one, otherwise, we will spend whole hour on that :) | 13:40 |
| johnthetubaguy | ++ | 13:40 |
| edleafe | mriedem: I thought this was tied to that problem | 13:40 |
| sdague | edleafe: it might be, and the proposers are a couple of releases back | 13:41 |
| sdague | hence, please provide more detailed use case | 13:41 |
| edleafe | sdague: got it | 13:41 |
| alex_xu | johnthetubaguy: anything more for policy? otherwise we done for the priorites | 13:42 |
| johnthetubaguy | other than be smiling at mriedem about the spec? | 13:42 |
| mriedem | i've got it in a tab :) | 13:42 |
| mriedem | https://review.openstack.org/#/c/433010 right? | 13:42 |
| johnthetubaguy | mriedem: cool, I hope your screen looks better than mine, but I suspect not | 13:42 |
| alex_xu | mriedem: it's worth to adverties on the nova weekly meeting for getting more feedback for the policy spec | 13:42 |
| johnthetubaguy | mriedem: thats the one | 13:42 |
| mriedem | alex_xu: ok can you update the weekly nova meeting agenda and post highlights for the api subteam? | 13:43 |
| mriedem | when we have the weekly meeting, there is usually not many people around that were also at the api meeting, depending on time of day when we have the nova meeting | 13:43 |
| alex_xu | mriedem: yea, I will update the agenda, but i can't attend the meeting this week, it is in the super early time for me | 13:43 |
| mriedem | i'm only attending this one because i'm working from home now :) | 13:43 |
| johnthetubaguy | alex_xu: I think the follow on specs need your feedback | 13:43 |
| alex_xu | johnthetubaguy: got it | 13:44 |
| mriedem | alex_xu: right - just need the agenda update with highlights, i'll repeat them | 13:44 |
| johnthetubaguy | mriedem: welcome to the club, btw | 13:44 |
| alex_xu | mriedem: thanks | 13:44 |
| mriedem | johnthetubaguy: i can feel my health deteriorating already :) | 13:44 |
| johnthetubaguy | mriedem: :) | 13:44 |
| * cdent expects mriedem's usually stellar hygiene to begin a slow gentle decay | 13:44 | |
| mriedem | leg atrophy and whatnot | 13:44 |
| cdent | sigh, yet more crypto-jinxing | 13:44 |
| alex_xu | we talk about extension removing, so I did some experiment on removing the stevedore https://review.openstack.org/445864 | 13:45 |
| alex_xu | #link https://review.openstack.org/445864 | 13:45 |
| alex_xu | another single one | 13:45 |
| alex_xu | #link https://review.openstack.org/445361 | 13:45 |
| johnthetubaguy | alex_xu: any way to avoid api-paste.ini changes? | 13:45 |
| johnthetubaguy | alex_xu: I should read your change better! | 13:46 |
| sdague | johnthetubaguy: it should be easy to do by just changing the class inline | 13:46 |
| johnthetubaguy | yeah, he fixed it already, I was just being dumb | 13:46 |
| alex_xu | johnthetubaguy: i guess so, i just get circle import problem, but i want to make it works before the meeting, so i just hack the code quickly | 13:47 |
| johnthetubaguy | ah, thats no fun | 13:47 |
| *** cjloader has joined #openstack-meeting-4 | 13:47 | |
| alex_xu | it copies the placement api pattern to list the routes explicitly https://review.openstack.org/#/c/445864/2/nova/api/openstack/compute/router.py@110 | 13:47 |
| sdague | right, the explicit routes is very nice | 13:48 |
| mriedem | when i saw that i was thinking router as in neutron router | 13:48 |
| sdague | it makes it so much easier to understand what is going on | 13:48 |
| *** kylek3h has quit IRC | 13:49 | |
| gmann | +1 | 13:49 |
| johnthetubaguy | alex_xu: looking good, +1 all what they just said | 13:49 |
| sdague | there is still a lot to unwind to really clean this up, but I think this a very good push | 13:49 |
| alex_xu | and before that, we should think about removing the extension point in the server controller https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/servers.py#L155 | 13:50 |
| alex_xu | probably similar way as what i do in the patch | 13:50 |
| johnthetubaguy | yeah, those ones would be good to kill | 13:50 |
| alex_xu | is it something we want to do in Pike? | 13:51 |
| sdague | alex_xu: ++ | 13:51 |
| gmann | alex_xu: that will go away by merging the extension class in server.py's create() right | 13:51 |
| sdague | alex_xu: I think this would be a great debt reduction | 13:51 |
| johnthetubaguy | as long as policy is still higher in priority, it beats and API features I have seen so far | 13:51 |
| johnthetubaguy | so +1 for pike | 13:51 |
| johnthetubaguy | closely followed by work on the API concept guide I guess | 13:52 |
| alex_xu | gmann: not sure, based on if merge didn't generate too much works | 13:52 |
| *** FrankZhang has joined #openstack-meeting-4 | 13:52 | |
| alex_xu | ok, i can do more futher work, and try to get more detail out, and I need a spec before freeze | 13:53 |
| johnthetubaguy | maybe specless bp is fine for this | 13:53 |
| gmann | spec ? | 13:53 |
| sdague | alex_xu: one thing to make sure to keep an eye on is that this doesn't break project_id in the url by changing up the router | 13:53 |
| johnthetubaguy | best to evolve the idea in gerrit I guess | 13:53 |
| *** markvoelker_ has joined #openstack-meeting-4 | 13:54 | |
| alex_xu | sdague: yea, i just break the project_id in the afternoon :) | 13:54 |
| gmann | +1 for specless bp | 13:54 |
| alex_xu | ok, i will work more poc code, until people feel it is good, then request the bp approve | 13:54 |
| alex_xu | #topic open | 13:55 |
| *** openstack changes topic to "open (Meeting topic: nova api)" | 13:55 | |
| alex_xu | so 5 mins left... | 13:55 |
| *** markvoelker has quit IRC | 13:55 | |
| alex_xu | please bring up anything for the last 5 mins | 13:55 |
| johnthetubaguy | lots of talk about the forum, are there any API things we want to raise at the forum? | 13:55 |
| johnthetubaguy | #link https://etherpad.openstack.org/p/BOS-Nova-brainstorming | 13:56 |
| sdague | so, fyi, I started writing up the microversion architecture document, which is taking the old blog post and readapting it for more permanent archival https://review.openstack.org/#/c/444892/ | 13:56 |
| johnthetubaguy | #link https://wiki.openstack.org/wiki/Forum/Boston2017 | 13:56 |
| *** SerenaFeng has quit IRC | 13:56 | |
| sdague | including input from things heard at the PTG which are common questions that I think we have answers with | 13:56 |
| sdague | answers for | 13:56 |
| alex_xu | are most of developers going to the summit? | 13:57 |
| johnthetubaguy | alex_xu: my gut tells me no | 13:57 |
| mriedem | i doubt it, | 13:57 |
| *** bobmel has quit IRC | 13:57 | |
| mriedem | i actually wanted to start getting a list of who is going, or trying to get approval to go | 13:57 |
| mriedem | #action mriedem to start an etherpad to get an idea of who is going to the summit/forum | 13:58 |
| johnthetubaguy | I am trying to be there, but not yet confirmed | 13:58 |
| alex_xu | ok, i also didn't hear anything about summit travel strategy from my manager also | 13:58 |
| johnthetubaguy | I was thinking what do we want feedback on from operators and users | 13:58 |
| mriedem | johnthetubaguy: there is a thread about something like that in the ops ML, | 13:58 |
| johnthetubaguy | the ironic raise min version discussion is the only thing that came to mind really | 13:58 |
| mriedem | and basically there wasn't a lot of feedback, or requests for sessions, | 13:58 |
| mriedem | so the forum organizers are a bit surprised and nervous from what i gather, | 13:59 |
| johnthetubaguy | yeah, there is a dev thread on that too, I think | 13:59 |
| mriedem | and a lot of operators won't be there because the summit is so close after the ops meetup | 13:59 |
| mriedem | so i suspect a fair amount of thumb twiddling | 13:59 |
| alex_xu | ... | 13:59 |
| alex_xu | it is the time close the meeting | 13:59 |
| mriedem | one last thing, | 14:00 |
| alex_xu | #endmeeting | 14:00 |
| *** openstack changes topic to " (Meeting topic: ironic_neutron)" | 14:00 | |
| openstack | Meeting ended Wed Mar 15 14:00:05 2017 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/2017/nova_api.2017-03-15-13.00.html | 14:00 |
| mriedem | https://review.openstack.org/#/c/391060/ is for deleting the request spec | 14:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-03-15-13.00.txt | 14:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-03-15-13.00.log.html | 14:00 |
| gmann | thanks | 14:00 |
| alex_xu | mriedem: let us back to nova channel :) | 14:00 |
| *** cdent has left #openstack-meeting-4 | 14:00 | |
| johnthetubaguy | mriedem: I forgot about that bit too | 14:00 |
| *** SerenaFeng has joined #openstack-meeting-4 | 14:01 | |
| alex_xu | i remember there is another meeting after us before | 14:01 |
| *** zhurong_ has joined #openstack-meeting-4 | 14:03 | |
| *** mriedem has left #openstack-meeting-4 | 14:03 | |
| *** alexchadin has quit IRC | 14:05 | |
| *** cathrichardson has joined #openstack-meeting-4 | 14:05 | |
| *** links has joined #openstack-meeting-4 | 14:05 | |
| *** zhurong_ has quit IRC | 14:06 | |
| *** baoli has quit IRC | 14:07 | |
| *** reedip has quit IRC | 14:09 | |
| *** baoli has joined #openstack-meeting-4 | 14:10 | |
| *** cjloader has quit IRC | 14:12 | |
| *** chigang has joined #openstack-meeting-4 | 14:13 | |
| *** irenab_ has joined #openstack-meeting-4 | 14:15 | |
| *** erikmwilson has quit IRC | 14:15 | |
| *** erikmwilson has joined #openstack-meeting-4 | 14:15 | |
| *** kylek3h has joined #openstack-meeting-4 | 14:17 | |
| *** reedip has joined #openstack-meeting-4 | 14:18 | |
| *** hrw has joined #openstack-meeting-4 | 14:24 | |
| *** reedip has quit IRC | 14:24 | |
| *** reedip has joined #openstack-meeting-4 | 14:26 | |
| *** woodard has quit IRC | 14:29 | |
| *** amotoki has joined #openstack-meeting-4 | 14:29 | |
| *** woodard has joined #openstack-meeting-4 | 14:31 | |
| *** Julien-zte has quit IRC | 14:35 | |
| *** efoley__ has joined #openstack-meeting-4 | 14:35 | |
| *** marst has quit IRC | 14:36 | |
| *** karthiks is now known as karthiks_afk | 14:36 | |
| *** galstrom_zzz is now known as galstrom | 14:36 | |
| *** mnasiadka has joined #openstack-meeting-4 | 14:37 | |
| *** Julien-zte has joined #openstack-meeting-4 | 14:37 | |
| *** Julien-zte has quit IRC | 14:38 | |
| *** iyamahat has joined #openstack-meeting-4 | 14:38 | |
| *** dave-mccowan has joined #openstack-meeting-4 | 14:38 | |
| *** efoley_ has quit IRC | 14:39 | |
| *** dasanind has quit IRC | 14:40 | |
| *** dasanind has joined #openstack-meeting-4 | 14:41 | |
| *** d0ugal has quit IRC | 14:42 | |
| *** links has quit IRC | 14:42 | |
| *** erikmwilson has quit IRC | 14:42 | |
| *** marst has joined #openstack-meeting-4 | 14:42 | |
| *** d0ugal has joined #openstack-meeting-4 | 14:43 | |
| *** hongbin has joined #openstack-meeting-4 | 14:43 | |
| *** erikmwilson has joined #openstack-meeting-4 | 14:44 | |
| *** irenab_ has quit IRC | 14:50 | |
| *** skraynev has joined #openstack-meeting-4 | 14:50 | |
| *** Sukhdev has joined #openstack-meeting-4 | 14:51 | |
| *** gongysh has quit IRC | 14:51 | |
| *** cjloader has joined #openstack-meeting-4 | 14:52 | |
| *** cjloader has quit IRC | 14:52 | |
| *** cjloader has joined #openstack-meeting-4 | 14:53 | |
| *** bobmel has joined #openstack-meeting-4 | 14:54 | |
| *** cathrichardson has quit IRC | 14:54 | |
| *** Sukhdev_ has joined #openstack-meeting-4 | 14:55 | |
| *** tonytan4ever has joined #openstack-meeting-4 | 14:55 | |
| *** yamahata has joined #openstack-meeting-4 | 14:55 | |
| *** sayantan_ has joined #openstack-meeting-4 | 14:56 | |
| *** premsankar has joined #openstack-meeting-4 | 14:58 | |
| *** cathrichardson has joined #openstack-meeting-4 | 14:59 | |
| *** bobmel has quit IRC | 14:59 | |
| *** bobmel has joined #openstack-meeting-4 | 15:00 | |
| *** jascott1 has joined #openstack-meeting-4 | 15:01 | |
| *** caboucha has joined #openstack-meeting-4 | 15:04 | |
| *** mbruzek has joined #openstack-meeting-4 | 15:04 | |
| *** janki has quit IRC | 15:05 | |
| *** kjackal has joined #openstack-meeting-4 | 15:05 | |
| *** bobh has joined #openstack-meeting-4 | 15:06 | |
| *** marcoceppi has joined #openstack-meeting-4 | 15:06 | |
| *** Syed__ has joined #openstack-meeting-4 | 15:08 | |
| *** zhubingbing has joined #openstack-meeting-4 | 15:09 | |
| *** limao has quit IRC | 15:10 | |
| *** Sukhdev_ has quit IRC | 15:10 | |
| *** limao has joined #openstack-meeting-4 | 15:11 | |
| *** Sukhdev_ has joined #openstack-meeting-4 | 15:11 | |
| *** erikmwilson has quit IRC | 15:12 | |
| *** zhubingbing has quit IRC | 15:14 | |
| *** erikmwilson has joined #openstack-meeting-4 | 15:14 | |
| *** zhubingbing has joined #openstack-meeting-4 | 15:14 | |
| *** Sukhdev_ has quit IRC | 15:15 | |
| *** vks1 has quit IRC | 15:29 | |
| *** sayantan_ has quit IRC | 15:32 | |
| *** amotoki has quit IRC | 15:33 | |
| *** armax has joined #openstack-meeting-4 | 15:37 | |
| *** unicell has joined #openstack-meeting-4 | 15:37 | |
| *** Jeffrey4l has quit IRC | 15:38 | |
| *** berendt has joined #openstack-meeting-4 | 15:38 | |
| *** SerenaFeng has quit IRC | 15:39 | |
| *** Jeffrey4l has joined #openstack-meeting-4 | 15:39 | |
| *** limao has quit IRC | 15:42 | |
| *** persia has quit IRC | 15:42 | |
| *** limao has joined #openstack-meeting-4 | 15:42 | |
| *** persia has joined #openstack-meeting-4 | 15:45 | |
| *** irenab has quit IRC | 15:48 | |
| *** zhubingbing has quit IRC | 15:49 | |
| *** mnaser has joined #openstack-meeting-4 | 15:50 | |
| *** reedip has quit IRC | 15:50 | |
| *** wxy| has joined #openstack-meeting-4 | 15:50 | |
| *** nkrinner is now known as nkrinner_afk | 15:53 | |
| *** duonghq has joined #openstack-meeting-4 | 15:54 | |
| *** limao has quit IRC | 15:56 | |
| *** david-lyle has joined #openstack-meeting-4 | 15:56 | |
| *** irenab has joined #openstack-meeting-4 | 15:57 | |
| *** mnasiadka has quit IRC | 15:57 | |
| *** Sukhdev_ has joined #openstack-meeting-4 | 15:58 | |
| inc0 | #startmeeting kolla | 15:59 |
| openstack | Meeting started Wed Mar 15 15:59:23 2017 UTC and is due to finish in 60 minutes. The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:59 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:59 |
| *** openstack changes topic to " (Meeting topic: kolla)" | 15:59 | |
| openstack | The meeting name has been set to 'kolla' | 15:59 |
| *** egonzalez has joined #openstack-meeting-4 | 15:59 | |
| inc0 | #topic rollcall, w00t | 15:59 |
| duonghq | o/ | 15:59 |
| inc0 | you know what to do | 15:59 |
| *** openstack changes topic to "rollcall, w00t (Meeting topic: kolla)" | 15:59 | |
| mnaser | o/ bonjour | 15:59 |
| hrw | o/ | 15:59 |
| pbourke | WOOT | 15:59 |
| duonghq | oops | 15:59 |
| akwasnie | o/ | 16:00 |
| berendt | o/ | 16:00 |
| Jeffrey4l | woot | 16:00 |
| egonzalez | woot o/ | 16:00 |
| spsurya_ | o/ | 16:00 |
| *** zhubingbing_ has joined #openstack-meeting-4 | 16:00 | |
| *** sayantan_ has joined #openstack-meeting-4 | 16:01 | |
| jascott1 | o/ | 16:01 |
| sayantan_ | woot | 16:01 |
| *** vhosakot has joined #openstack-meeting-4 | 16:01 | |
| zhubingbing_ | woot | 16:01 |
| spsurya_ | woot | 16:01 |
| zhubingbing_ | o/ | 16:01 |
| vhosakot | o/ w00t w00t | 16:01 |
| qwang | O/ | 16:02 |
| *** vsaienk0 has quit IRC | 16:02 | |
| inc0 | #topic announcements | 16:02 |
| *** openstack changes topic to "announcements (Meeting topic: kolla)" | 16:02 | |
| inc0 | 1. we releaed ocata! | 16:02 |
| Jeffrey4l | so many people today ;) | 16:02 |
| inc0 | congrats everyone | 16:02 |
| spsurya_ | gratz | 16:03 |
| qwang | Jeffrey4l: for DST | 16:03 |
| hrw | yay! more reviewers! | 16:03 |
| *** doude has quit IRC | 16:03 | |
| Jeffrey4l | aha | 16:03 |
| inc0 | 2. One more week for voting for duonghq to become core, if anyone from core team missed it, please vote | 16:03 |
| vhosakot | yep, will vote | 16:04 |
| duonghq | thank inc0 | 16:04 |
| spsurya_ | duonghq: congrats | 16:04 |
| inc0 | so last week we canibalized regular agenda for release discussion, so now let's get back to it | 16:04 |
| *** hongbin has quit IRC | 16:05 | |
| inc0 | #topic Need to formalize policy around pushing to dockerhub | 16:05 |
| *** openstack changes topic to "Need to formalize policy around pushing to dockerhub (Meeting topic: kolla)" | 16:05 | |
| inc0 | agree ^ | 16:05 |
| inc0 | formalize and automate | 16:05 |
| *** mandre has joined #openstack-meeting-4 | 16:05 | |
| inc0 | #link https://bugs.launchpad.net/kolla-ansible/+bug/1669075/comments/4 | 16:05 |
| openstack | Launchpad bug 1669075 in kolla-ansible "kolla-ansible pull with kolla_ansible-4.0.0.0rc1 fails, because of missing tag in docker registry" [Low,Invalid] | 16:05 |
| berendt | regarding automate: i can add this to our jenkins instance | 16:05 |
| pbourke | #linkhttps://wiki.openstack.org/wiki/Meetings/Kolla#Agenda_for_next_meeting_.28Mar_8th_2017.29 | 16:05 |
| pbourke | #link https://wiki.openstack.org/wiki/Meetings/Kolla#Agenda_for_next_meeting_.28Mar_8th_2017.29 | 16:05 |
| *** l4yerffeJ has joined #openstack-meeting-4 | 16:06 | |
| Jeffrey4l | rc is unstable, push them will cause lots of issue, imo. | 16:06 |
| mnaser | but wont they technically never be pulled | 16:06 |
| Jeffrey4l | especially for hub.docker.com. | 16:06 |
| mnaser | unless you're running an rc release of kolla-ansible/kubernetes? | 16:06 |
| Jeffrey4l | but push them into tarballs.openstack.org is OK, i think. | 16:06 |
| berendt | Jeffrey4l: when you visit our docs the master documents including the tag 4.0.0 was published | 16:07 |
| inc0 | alternatively, instead of rc | 16:07 |
| *** doude has joined #openstack-meeting-4 | 16:07 | |
| berendt | because of this david opened this bug | 16:07 |
| inc0 | keep pushing stable/ocata | 16:07 |
| pbourke | is there a reason we can't push to dockerhub along side tarballs.oo | 16:07 |
| inc0 | with some meaninful thag | 16:07 |
| inc0 | tag | 16:07 |
| inc0 | like 4.0.0-latest | 16:07 |
| berendt | the master branch is only usable when building own images | 16:07 |
| mnaser | i think what inc0 makes a lot of sense, that means backports can make their way much faster | 16:08 |
| Jeffrey4l | pbourke, i want to know how to keep hub.docker.com credential in ci. | 16:08 |
| inc0 | yeah and also fixes what egonzalez mentioned on main channel - some other project deploys critical fix | 16:08 |
| Jeffrey4l | inc0, 4.0.0-latest is a good idea. | 16:08 |
| inc0 | we have it upstream immediatly | 16:08 |
| *** Serlex has joined #openstack-meeting-4 | 16:08 | |
| inc0 | and :latest for master | 16:08 |
| inc0 | berendt: my question is...what jenkins instance?:) | 16:09 |
| mnaser | inc0: well technically, you wouldnt, unless you manually trigger stable/<branch> (i could be wrong)? | 16:09 |
| berendt | inc0: company one | 16:09 |
| berendt | not sure if we have to add it to the openstack jenkins | 16:09 |
| inc0 | right | 16:09 |
| Jeffrey4l | berendt, re docs, sorry, i do not get your point ;( | 16:09 |
| berendt | Jeffrey4l: david opened the bug because the kolla-ansible repository on the master branch is not usable without building own images | 16:10 |
| inc0 | so how about we will create crontab entries and keep them in our repo | 16:10 |
| Jeffrey4l | mnaser, we can , there is a period pipeline in zuul. | 16:10 |
| mnaser | oh cool1 | 16:10 |
| inc0 | Jeffrey4l: really? so we can run a gate daily? | 16:10 |
| Jeffrey4l | inc0, yep. | 16:10 |
| inc0 | or rather, job to build+push? | 16:11 |
| Jeffrey4l | pretty sure. | 16:11 |
| inc0 | cool | 16:11 |
| mnaser | yes i recall now the periodic pipeline | 16:11 |
| mnaser | https://docs.openstack.org/infra/system-config/zuul.html > periodic | 16:11 |
| inc0 | do we agree that we create branch :4.0.0-latest for daily stable ocata and :latest for daily master? | 16:11 |
| Jeffrey4l | #link https://docs.openstack.org/infra/system-config/zuul.html | 16:11 |
| inc0 | or maybe not latest | 16:11 |
| inc0 | let's call it master or trunk | 16:12 |
| inc0 | as latest is default tag | 16:12 |
| mnaser | would it be a lot more work to add newton? :X | 16:12 |
| inc0 | no it wouldnt | 16:12 |
| inc0 | we can do neutron too | 16:12 |
| Jeffrey4l | neutron? | 16:12 |
| mnaser | it would be quite beneficial (as ocata is still "fresh") | 16:12 |
| inc0 | newton | 16:12 |
| mnaser | i think he means newton :-P | 16:12 |
| inc0 | sorry | 16:12 |
| inc0 | I'm still waking up;) | 16:12 |
| Jeffrey4l | so i guess push branch is acceptable by all guys, right? | 16:13 |
| inc0 | #action inc0: write bp for daily gerrit jobs | 16:13 |
| Jeffrey4l | tag name is not a big deal. | 16:13 |
| inc0 | yeah | 16:13 |
| inc0 | we can continue discussion in bp and as usual | 16:13 |
| pbourke | inc0: how are we going to get credentials into these jobs | 16:14 |
| Jeffrey4l | another thing related to this is: auto bump the service tag in source. | 16:14 |
| Jeffrey4l | pbourke, good point. | 16:14 |
| inc0 | pbourke: that's a good question, I'll check with infra for secret storage | 16:14 |
| pbourke | inc0: cool | 16:14 |
| inc0 | I think they have hiera (they need to;)) | 16:14 |
| inc0 | maybe we can somehow tap into it | 16:14 |
| mnaser | they do have hiera | 16:15 |
| mnaser | pypi credentials are stored in there for example | 16:15 |
| Jeffrey4l | cool. | 16:15 |
| Jeffrey4l | mnaser, you know lots of think about ci? | 16:15 |
| Jeffrey4l | thing* | 16:15 |
| * mnaser has been in openstack since 2011 | 16:16 | |
| Jeffrey4l | wow | 16:16 |
| mnaser | our cloud is running newton (but it started its life off as bexar actually) -- looking to get more involved but we can get into that later :) | 16:16 |
| hrw | mnaser: perfect person for '10y of openstack experience' offers | 16:16 |
| Jeffrey4l | lol | 16:16 |
| inc0 | mnaser: so from Bexar?:0 | 16:16 |
| berendt | lol | 16:17 |
| egonzalez | lol | 16:17 |
| mnaser | http://jeffrose.wpengine.netdna-cdn.com/wp-content/uploads/2011/12/dr.-evil-million-dollar-term-policy-300x241.jpg | 16:17 |
| inc0 | ok let's move on | 16:17 |
| berendt | we started first environment with bexar, too, funny times | 16:17 |
| inc0 | #topic drop root | 16:17 |
| *** openstack changes topic to "drop root (Meeting topic: kolla)" | 16:17 | |
| inc0 | duonghq: you're u | 16:17 |
| inc0 | up | 16:17 |
| duonghq | thank inc0 | 16:17 |
| duonghq | I see we have 2 bugs relate to drop root topic: | 16:18 |
| duonghq | #info keystone https://bugs.launchpad.net/kolla/+bug/1576794 | 16:18 |
| openstack | Launchpad bug 1576794 in kolla "drop root for keystone" [Critical,In progress] - Assigned to Surya Prakash Singh (confisurya) | 16:18 |
| duonghq | #info crontab https://bugs.launchpad.net/kolla/+bug/1560744 | 16:18 |
| openstack | Launchpad bug 1560744 in kolla "drop root for crontab" [Critical,Confirmed] | 16:18 |
| *** rbak_ has quit IRC | 16:18 | |
| duonghq | for crontab, I see that sdake commented it cannot be dropped in centos, for keystone, I'm not sure | 16:19 |
| spsurya_ | inc0: first to check is this valid bug , need to b fix ? | 16:19 |
| duonghq | so if we can confirm for crontab one, I think we can close the bug | 16:19 |
| *** cathrichardson has quit IRC | 16:19 | |
| spsurya_ | we pbourke comment too for keystone one | 16:19 |
| spsurya_ | that root can't be dropped | 16:19 |
| *** cathrichardson has joined #openstack-meeting-4 | 16:20 | |
| *** bobmel has quit IRC | 16:20 | |
| *** vsaienk0 has joined #openstack-meeting-4 | 16:20 | |
| inc0 | well for keystone, and other apache based apis, it can't be dropped | 16:20 |
| *** rbak has joined #openstack-meeting-4 | 16:20 | |
| inc0 | afair | 16:20 |
| duonghq | pbourke, how do you think? | 16:20 |
| pbourke | would be interested in what the keystone guys have to say on this | 16:20 |
| pbourke | suddenly forcing root on operators is a strange decision | 16:21 |
| pbourke | regardless of the benefits brought by running behind apache | 16:21 |
| hrw | if it can run on >1024 port then should be doable without root | 16:21 |
| Jeffrey4l | copy from net: Apache has to run as root initially in order to bind to port 80. If you don't run it as root initially then you cannot bind to port 80. If you want to bind to some port above 1024 then yes, you can. | 16:21 |
| spsurya_ | pbourke: +1 | 16:21 |
| Jeffrey4l | https://superuser.com/questions/316705/running-apache-as-a-different-user | 16:21 |
| Jeffrey4l | all the port we are using now > 1024 | 16:21 |
| inc0 | Jeffrey4l: horizon is still 80/443 | 16:22 |
| inc0 | well 80 | 16:22 |
| Jeffrey4l | oh, right. horizon is. | 16:22 |
| duonghq | so, we can move it to higher port, and drop root? | 16:22 |
| mnaser | haproxy as well? | 16:22 |
| mnaser | for the horizon backends | 16:22 |
| inc0 | but technically we could run horizon on 1024< and bind 80 on haproxy | 16:22 |
| inc0 | just not backwards compatible change so let's not do it | 16:23 |
| spsurya_ | seems like >1024 would be ok for dropping | 16:23 |
| Jeffrey4l | inc0, haproxy is optional. | 16:23 |
| mnaser | aio deployments might become a bit weird though ^ | 16:23 |
| inc0 | everything is optional;) | 16:23 |
| inc0 | but yeah, can break stuff | 16:23 |
| Jeffrey4l | kolla support run without haproxy. | 16:23 |
| duonghq | mnaser, in default setting, AIO still use haproxy | 16:23 |
| *** lei-zh has joined #openstack-meeting-4 | 16:23 | |
| mnaser | it seems like the root requirement is there, regardless | 16:23 |
| inc0 | yeah, and keepalived;) | 16:23 |
| mnaser | there's quite a few components which will need root at the end of the day | 16:24 |
| inc0 | well, either way | 16:24 |
| duonghq | we still can bind port from docker side | 16:24 |
| inc0 | keystone shouldn't need it because of apache | 16:24 |
| Jeffrey4l | so we can drop root for apache with port > 1024 , right? | 16:24 |
| mnaser | yes Jeffrey4l | 16:24 |
| *** cathrichardson has quit IRC | 16:24 | |
| inc0 | duonghq: that's good alternative, but we would need to drop net=host for apis | 16:24 |
| inc0 | which I wouldn't be opposed to | 16:24 |
| hrw | at linaro we only deploy nova/neutron/cinder/glance/horizon/keystone + openvswitch + ceph iirc | 16:25 |
| *** julim_ has quit IRC | 16:25 | |
| *** rbak has quit IRC | 16:25 | |
| Jeffrey4l | hrw, so? | 16:25 |
| *** l4yerffeJ has quit IRC | 16:25 | |
| duonghq | inc0, hmm, forgot that, one of our goals | 16:25 |
| *** rbak has joined #openstack-meeting-4 | 16:25 | |
| mnaser | i like net=host being there. it makes life simple. once you get out of it, you have to start playing around overlay networsk and you start adding a lot of the complexities (imho) | 16:25 |
| Jeffrey4l | there is another parameter may be helpful to drop root: docker run --cap-add | 16:25 |
| Jeffrey4l | but i am not sure. | 16:26 |
| mnaser | actually thats a really good suggestion | 16:26 |
| *** julim has joined #openstack-meeting-4 | 16:26 | |
| inc0 | yeah, and also there were performance issues | 16:26 |
| pbourke | how many people see this as high priority? | 16:26 |
| *** l4yerffeJ has joined #openstack-meeting-4 | 16:26 | |
| Jeffrey4l | pbourke, drop root, or? | 16:26 |
| mnaser | as a deployer, i dont really care about the keystone container running as root (honestly) | 16:26 |
| pbourke | breaking out of a container is a theoretical exploit... meanwhile we have world readable passwords on all target nodes | 16:26 |
| Jeffrey4l | btw, even though keystone container running as root, but keystone wsgi run as keystone user. | 16:26 |
| mnaser | httpd is going to be running as root in most other deployments methods in the first place and the keystone processes fork under keystone | 16:27 |
| inc0 | and getting into container is arguably harder than root host | 16:27 |
| *** unicell has quit IRC | 16:27 | |
| inc0 | as we don't run any services there besides one we need | 16:27 |
| *** sshnaidm is now known as sshnaidm|nnl | 16:27 | |
| *** sshnaidm|nnl is now known as sshnaidm|bbl | 16:27 | |
| Jeffrey4l | can i say: drop root is not critical issue, but nice to have ? | 16:27 |
| mnaser | i would agree with that ^ | 16:28 |
| pbourke | I think so | 16:28 |
| inc0 | but regardless, can we examine drop root for ks as there doesn't seem to be compelling reason why not? | 16:28 |
| *** robputt_ has quit IRC | 16:28 | |
| *** clayton has quit IRC | 16:28 | |
| inc0 | it's still better to remove it | 16:28 |
| Jeffrey4l | so if drop-root for any container is possible, and anyone who interested in this? please implement it :) | 16:28 |
| inc0 | just not critical | 16:28 |
| spsurya_ | Jeffrey4l: we can its type to medium ? | 16:28 |
| duonghq | sure | 16:28 |
| pbourke | someone should investigate and update the docs if its not currently feasable | 16:28 |
| inc0 | yeah let's make all drop root medium bugs | 16:28 |
| *** cathrichardson has joined #openstack-meeting-4 | 16:29 | |
| Jeffrey4l | medium, agree. | 16:29 |
| duonghq | so we drop its "importance"? | 16:29 |
| duonghq | lol | 16:29 |
| inc0 | lol | 16:29 |
| spsurya_ | duonghq: lol | 16:29 |
| duonghq | I'll ask sdake later when I see him | 16:29 |
| duonghq | about crontab | 16:29 |
| inc0 | (and I bet *nobody* actually laughted out loud) | 16:29 |
| spsurya_ | although we need to fix it anyway | 16:29 |
| spsurya_ | inc0: +1 | 16:30 |
| duonghq | ya, alright | 16:30 |
| inc0 | right, let's move on | 16:30 |
| *** robputt has joined #openstack-meeting-4 | 16:30 | |
| spsurya_ | yes no body | 16:30 |
| inc0 | #topic canonical k8s deployment | 16:30 |
| *** openstack changes topic to "canonical k8s deployment (Meeting topic: kolla)" | 16:30 | |
| *** reedip has joined #openstack-meeting-4 | 16:30 | |
| inc0 | so I think we don't have our canonical guys around | 16:31 |
| inc0 | (do we have kolla-k8s people?) | 16:31 |
| Jeffrey4l | Canonical company? interesting | 16:31 |
| inc0 | kfox1111 around? | 16:31 |
| inc0 | ok it seems we don't have quorum for that, pushing to next meeting | 16:32 |
| zhubingbing_ | ;) | 16:32 |
| *** kbyrne has quit IRC | 16:32 | |
| inc0 | #topic open discussion | 16:32 |
| *** openstack changes topic to "open discussion (Meeting topic: kolla)" | 16:32 | |
| inc0 | since we ran out of agenda items, anything needing our immediate attention? | 16:32 |
| vhosakot | I'm still deploying kolla-k8s and will update docs as needed. | 16:32 |
| duonghq | can I? | 16:32 |
| inc0 | duonghq: go ahead | 16:32 |
| duonghq | forgot add this to agenda, I drafted on bp from last week | 16:33 |
| duonghq | #link https://blueprints.launchpad.net/kolla/+spec/unix-signals-handling | 16:33 |
| *** clayton has joined #openstack-meeting-4 | 16:33 | |
| duonghq | can you give me some comment? | 16:33 |
| duonghq | hmm, where is the bot, I think bot'll put the title | 16:33 |
| duonghq | Unix singals handling in Kolla image | 16:33 |
| inc0 | duonghq: first, we need to figure out which services allows sighup | 16:33 |
| inc0 | second, that won't work with CONFIG_ONCE | 16:34 |
| berendt | duonghq: i think he doesn't because of the leading #link | 16:34 |
| *** david-lyle_ has joined #openstack-meeting-4 | 16:34 | |
| duonghq | berendt, roger | 16:34 |
| *** david-lyle has quit IRC | 16:34 | |
| duonghq | inc0, ya, but in COPY_ALWAYS, it'll be nice feature to reload setting w/o downtime | 16:34 |
| Jeffrey4l | duonghq, have u tried sighup. it should work with dumb-init. | 16:34 |
| mnaser | also, i think this is a big of a weird situation because not all config values are reloaded | 16:34 |
| duonghq | w/o restart container | 16:34 |
| mnaser | so for example oslo_log might notice the change but some other part of another component will | 16:35 |
| duonghq | Jeffrey4l, I'm not sure w/ dumb-init, just plain service, it's ok | 16:35 |
| mnaser | so i think its important to keep in mind of the possible complexity that might introduce knowing which config values will reload and which ones wont | 16:35 |
| duonghq | mnaser, ya, and we also have some service support graceful shutdown by signal | 16:35 |
| mnaser | i think graceful shutdown is miles more important especially for cases like nova-compute for example | 16:36 |
| Jeffrey4l | sighup should be handle properly, as long as the real service could handle it. | 16:36 |
| *** kbyrne has joined #openstack-meeting-4 | 16:36 | |
| Jeffrey4l | currently, we use sighup for haproxy configure reload. | 16:36 |
| Jeffrey4l | so i think this pb is already done ;) | 16:37 |
| inc0 | yeah, sigkill is more importnat | 16:37 |
| mnaser | but i think on reconfigure's sending signal instead of just killing the container (unless docker already does that?) | 16:37 |
| duonghq | mnaser, it's depend on argument we pass to docker | 16:38 |
| inc0 | docker does sigkill and then timeout (30s I believe) before force termination | 16:38 |
| duonghq | the signal indeed | 16:38 |
| Jeffrey4l | inc0, 10s | 16:38 |
| mnaser | gotcha inc0 that's good for nova-compute | 16:38 |
| *** zhubingbing_ has quit IRC | 16:38 | |
| mnaser | but 10 seconds might be a bit too short but i think that's anothre discussion | 16:38 |
| Jeffrey4l | it is configurable. | 16:38 |
| Jeffrey4l | for each container. | 16:39 |
| mnaser | thats good to know, thanks Jeffrey4l | 16:39 |
| Jeffrey4l | docker stop -t <num> | 16:39 |
| inc0 | but I don't believe we use this config | 16:39 |
| inc0 | maybe that's good bug to kolla_docker? | 16:39 |
| duonghq | Jeffrey4l, should we figure what service support SIGHUP to reload whole service config, then passthrough the signal to that service? | 16:39 |
| portdirect | sorry to burst in late - we can also controll the signals in k8s - so would be great to get kfox and sbezverk to have some input on that | 16:39 |
| Jeffrey4l | kolla-ansible do not support this parameter so far. | 16:39 |
| inc0 | portdirect: yeah k8s is better in this spae | 16:40 |
| Jeffrey4l | duonghq, not all parameter support SIGHUP, jut part of them, iirc. | 16:40 |
| duonghq | Jeffrey4l, it's docker-py, docker issue or our issue? | 16:40 |
| inc0 | our issue | 16:41 |
| *** zhubingbing_ has joined #openstack-meeting-4 | 16:41 | |
| Jeffrey4l | wait 1 min. which issue are u talking? | 16:41 |
| inc0 | well, we don't allow to override 10s | 16:41 |
| inc0 | that's it | 16:41 |
| mnaser | i think a summary of what inc0 is saying is overriding the docker kill timeout for containers | 16:41 |
| mnaser | (aka the time period from when it sends a signal to stop and then forcingly terminates the container) | 16:42 |
| Jeffrey4l | 1. kolla container support sighub, it pass to the real process 2. container is killed after 10s without stopped. | 16:42 |
| inc0 | and for 2 - let's add this config so we can extend period for services like n-cpu or heat | 16:42 |
| Jeffrey4l | inc0, ++ | 16:43 |
| duonghq | Jeffrey4l, just for sure, we already support passing SIGHUP to container? | 16:43 |
| mnaser | as you're using dumb-init i believe you it should happen automagically | 16:43 |
| duonghq | inc0, +1 | 16:43 |
| Jeffrey4l | duonghq, yep. with dumb-init, SIGHUP is handle properly. | 16:43 |
| duonghq | mnaser, Jeffrey4l roger | 16:43 |
| mnaser | i have a few things to bring up if we're done with this | 16:43 |
| Jeffrey4l | you can try it simplely. | 16:43 |
| duonghq | iirc, we're planing to move to another init | 16:43 |
| inc0 | yeah, but correct me if I'm wrong but we don't *really* use sighup during reconfigure | 16:44 |
| duonghq | tini? | 16:44 |
| Jeffrey4l | but another thing is: not all parameter in nova.conf support SIGHUP. | 16:44 |
| duonghq | inc0, yup | 16:44 |
| duonghq | Jeffrey4l, of course | 16:44 |
| Jeffrey4l | inc0, for haproxy, yes. others no. | 16:44 |
| duonghq | it's mnaser said: it's make things go wired | 16:44 |
| inc0 | question is, is it a big deal really | 16:44 |
| duonghq | i.e. all oslo log support it, | 16:44 |
| Jeffrey4l | it is impossible, imo. | 16:44 |
| inc0 | at least very hard | 16:45 |
| Jeffrey4l | we do not know which parameter is change, so we can not know whether we should restart or sighup. | 16:45 |
| Jeffrey4l | so it is impossible. | 16:45 |
| *** yamahata has quit IRC | 16:45 | |
| inc0 | right | 16:45 |
| mnaser | i think if you want to revise the bp duonghq you would maybe look into merge_configs to notice what changed | 16:45 |
| duonghq | but for glance, it's support SIGHUP for all config | 16:45 |
| inc0 | safer to do full restart | 16:45 |
| duonghq | I mean, by the time, maybe more service support this kind of reconfiguration | 16:46 |
| mnaser | and then maybe if SIGHUP becomes "the way to go" long term, you'd easily be able to do that | 16:46 |
| *** iyamahat has quit IRC | 16:46 | |
| Jeffrey4l | if one service announce he support SIGHUP for all config, i think we can implement this. | 16:46 |
| duonghq | so, for services have not supported yet, we can ignore that, | 16:46 |
| duonghq | we can have some kind of fully supported list | 16:46 |
| mnaser | just on a deployer perspective | 16:47 |
| inc0 | duonghq: but if we introduce 2 different modes of reload | 16:47 |
| inc0 | that's complexity | 16:47 |
| mnaser | i would much rather have a full restart | 16:47 |
| mnaser | i doubt SIGHUP reloads have undergone heavy testing | 16:47 |
| Jeffrey4l | COPY_ONCE is another big concern when using SIGHUP. | 16:47 |
| Jeffrey4l | mnaser, ++ | 16:47 |
| duonghq | inc0, sure, | 16:47 |
| mnaser | deploy X change, send SIGHUP, makes sure everthing is working is probably not something that's tested | 16:47 |
| Jeffrey4l | in most of case, restart is not a big deal. | 16:47 |
| duonghq | ok | 16:48 |
| inc0 | another question | 16:48 |
| mnaser | if it is a big deal then you have mutliple controllers and serial will do controlled restarts so you should be okay | 16:48 |
| inc0 | different topic | 16:48 |
| inc0 | draining of connections on haproxy | 16:48 |
| inc0 | during upgrade | 16:48 |
| Jeffrey4l | restart means: kill the process and start it again, reload/sighup means recreate the inner class/object again. | 16:48 |
| *** Sukhdev_ has quit IRC | 16:48 | |
| Jeffrey4l | inc0, at that point, we should support rolling upgrade first. | 16:49 |
| inc0 | right... | 16:49 |
| mnaser | instead of draining connections, i think shutting all services down and letting haproxy return 502 is an acceptable thing | 16:49 |
| inc0 | any ideas about that btw | 16:49 |
| inc0 | ? | 16:49 |
| Jeffrey4l | otherwise the remaining connection won't work. | 16:49 |
| duonghq | about draining connection on haproxy, iirc, egonzalez have a solution | 16:49 |
| Jeffrey4l | mnaser, i like you. | 16:50 |
| Jeffrey4l | lolo | 16:50 |
| egonzalez | inc0, yep, ansible support setting a haproxy backend as maintenance mode | 16:50 |
| inc0 | yay..but it doesn't support serial way we need it;) | 16:50 |
| duonghq | we can drain connection than upgrade the node, so it appear no downtime at that point | 16:50 |
| Jeffrey4l | serial is not rolling upgrade. we talked about this | 16:50 |
| inc0 | ok, anyway, rolling upgrade | 16:50 |
| inc0 | that's what I meant | 16:51 |
| mnaser | i would: pull all new images, shutdown all $service containers, run db syncs, start all $service containers. naturally, during the time of this happening, haproxy will be giving back 502s | 16:51 |
| duonghq | about rolling upgrade, graceful shutdown is important for achieve that | 16:51 |
| mnaser | for rolling upgrades, here's what i'd throw in the table, add multiple steps to it (or maybe even multiple kolla-ansible steps) | 16:51 |
| mnaser | step #1, upgrade control plane (this happens with no serial) | 16:51 |
| Jeffrey4l | mnaser, shutdown all service means shutdown haproxy. | 16:52 |
| mnaser | nope, shut down a specific service, ex: glance | 16:52 |
| Jeffrey4l | got. | 16:52 |
| mnaser | step #2, upgrade data plan (this happens with say, 20% serial or whatever) | 16:52 |
| Jeffrey4l | duonghq, graceful shutdown mean? | 16:52 |
| mnaser | as part of step #1, you'd set upgrade_levels on the controllers too | 16:52 |
| inc0 | yeah, we thought of 2 different plays | 16:52 |
| mnaser | and then the final step would be, remove all upgrade_levels and restart $service | 16:52 |
| duonghq | glance (for example) has glance-control to coordinate its microservice, we have not supported that | 16:53 |
| inc0 | hmm, upgrade playbook can call 3 plays with serial | 16:53 |
| duonghq | Jeffrey4l, we send some signal to container, it'll drain connection by itself | 16:53 |
| inc0 | 1 - upgrade control, no serial, set upgrade_lebels | 16:53 |
| inc0 | 2- upgrade compute, with serial | 16:53 |
| inc0 | 3 - remove controller upgrade_levels | 16:53 |
| mnaser | ideally id like to see those split (and one that is combined). we usually prefer to upgrade control plane and make sure everything is a-ok | 16:54 |
| *** zhubingbing_ has quit IRC | 16:54 | |
| Jeffrey4l | do all services support upgrade_levels? | 16:54 |
| mnaser | the large scale ones do (aka neutron+nova) | 16:54 |
| mnaser | the rest i dont really know but they're so lightweight that it's not as big of a deal | 16:54 |
| mnaser | most people dont have 300 heat-engine instances for example | 16:55 |
| Jeffrey4l | yep. | 16:55 |
| inc0 | separating upgrade to multiple plays - I really like that | 16:56 |
| Jeffrey4l | draining connection is trying to reduce the downtime in #1 | 16:56 |
| *** baoli has quit IRC | 16:56 | |
| mnaser | i have few things | 16:56 |
| mnaser | before the end if people dont mind | 16:56 |
| inc0 | I'd do it after we make upgrade gats really | 16:56 |
| Jeffrey4l | two topics we are haveing. | 16:56 |
| duonghq | Jeffrey4l, minute, does dumb-init support passsing SIGKILL to the process? in general, every signal? | 16:56 |
| Jeffrey4l | mnaser, please. | 16:56 |
| mnaser | https://review.openstack.org/#/c/445690/ keystone-ssh is broken | 16:56 |
| duonghq | inc0, +1 for your 3 plays | 16:56 |
| Jeffrey4l | duonghq, yep. | 16:56 |
| *** baoli has joined #openstack-meeting-4 | 16:56 | |
| mnaser | multinode rotation of fernet tokens doesnt work | 16:56 |
| duonghq | Jeffrey4l, cool | 16:56 |
| mnaser | if people can give some love to that review, it would be wonderful | 16:56 |
| mnaser | ill backport afterwards | 16:57 |
| Jeffrey4l | duonghq, dumb-init works like systemd. | 16:57 |
| mnaser | and as a closer for next time maybe, i want to float the idea of using bindep when installing from source to avoid problems like this - https://review.openstack.org/#/c/446032/ | 16:57 |
| Jeffrey4l | +2ed | 16:58 |
| duonghq | Jeffrey4l, ok, I'll experiment that, thanks | 16:58 |
| *** baoli has quit IRC | 16:58 | |
| *** cathrichardson has left #openstack-meeting-4 | 16:58 | |
| inc0 | ok, we're running out of time | 16:58 |
| inc0 | thank you all for coming | 16:58 |
| duonghq | thanks | 16:58 |
| inc0 | #endmeeting kolla | 16:58 |
| *** openstack changes topic to " (Meeting topic: ironic_neutron)" | 16:58 | |
| openstack | Meeting ended Wed Mar 15 16:58:41 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:58 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-03-15-15.59.html | 16:58 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-03-15-15.59.txt | 16:58 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-03-15-15.59.log.html | 16:58 |
| *** lei-zh has quit IRC | 16:58 | |
| *** lazyPwr has joined #openstack-meeting-4 | 16:59 | |
| *** hrw has left #openstack-meeting-4 | 17:01 | |
| *** duonghq has quit IRC | 17:02 | |
| *** egonzalez has quit IRC | 17:02 | |
| *** britthouser7 has joined #openstack-meeting-4 | 17:03 | |
| *** vhosakot has left #openstack-meeting-4 | 17:04 | |
| *** salmankhan has joined #openstack-meeting-4 | 17:05 | |
| *** britthouser has quit IRC | 17:05 | |
| *** unicell has joined #openstack-meeting-4 | 17:05 | |
| *** iyamahat has joined #openstack-meeting-4 | 17:05 | |
| *** unicell has quit IRC | 17:05 | |
| *** baoli has joined #openstack-meeting-4 | 17:06 | |
| *** anilvenkata has quit IRC | 17:07 | |
| *** chigang has quit IRC | 17:09 | |
| *** wxy| has quit IRC | 17:11 | |
| *** erikmwilson has quit IRC | 17:12 | |
| *** erikmwilson has joined #openstack-meeting-4 | 17:13 | |
| *** rtheis has joined #openstack-meeting-4 | 17:13 | |
| *** rtheis has quit IRC | 17:16 | |
| *** Swami has joined #openstack-meeting-4 | 17:20 | |
| *** yamahata has joined #openstack-meeting-4 | 17:24 | |
| *** matrohon has quit IRC | 17:28 | |
| *** pcaruana has quit IRC | 17:28 | |
| *** unicell has joined #openstack-meeting-4 | 17:28 | |
| *** unicell has quit IRC | 17:29 | |
| *** ltomasbo is now known as ltomasbo|away | 17:32 | |
| *** unicell has joined #openstack-meeting-4 | 17:33 | |
| *** Sukhdev_ has joined #openstack-meeting-4 | 17:34 | |
| *** Sukhdev has quit IRC | 17:36 | |
| *** reedip has quit IRC | 17:38 | |
| *** jed56 has quit IRC | 17:40 | |
| *** jamespage has joined #openstack-meeting-4 | 17:44 | |
| *** pmesserl_ has joined #openstack-meeting-4 | 17:46 | |
| *** pmesserli has quit IRC | 17:46 | |
| *** unicell has quit IRC | 17:53 | |
| *** armax has quit IRC | 17:55 | |
| *** s3wong has joined #openstack-meeting-4 | 17:57 | |
| *** arosales has joined #openstack-meeting-4 | 18:00 | |
| *** liangy has quit IRC | 18:03 | |
| *** efoley_ has joined #openstack-meeting-4 | 18:04 | |
| *** marst has quit IRC | 18:05 | |
| *** marst has joined #openstack-meeting-4 | 18:05 | |
| *** Sukhdev_ has quit IRC | 18:07 | |
| *** efoley__ has quit IRC | 18:08 | |
| *** baoli has quit IRC | 18:09 | |
| *** efoley_ has quit IRC | 18:09 | |
| *** baoli has joined #openstack-meeting-4 | 18:10 | |
| *** baoli has quit IRC | 18:14 | |
| *** jascott1 has left #openstack-meeting-4 | 18:15 | |
| *** bogdando has quit IRC | 18:16 | |
| *** joedborg has quit IRC | 18:18 | |
| *** baoli has joined #openstack-meeting-4 | 18:22 | |
| *** krtaylor has quit IRC | 18:26 | |
| *** unicell has joined #openstack-meeting-4 | 18:27 | |
| *** marst has quit IRC | 18:28 | |
| *** armax has joined #openstack-meeting-4 | 18:30 | |
| *** marst has joined #openstack-meeting-4 | 18:33 | |
| *** sshnaidm|bbl is now known as sshnaidm | 18:36 | |
| *** unicell has quit IRC | 18:37 | |
| *** unicell has joined #openstack-meeting-4 | 18:41 | |
| *** bnemec has quit IRC | 18:41 | |
| *** cathrichardson has joined #openstack-meeting-4 | 18:44 | |
| *** unicell1 has joined #openstack-meeting-4 | 18:44 | |
| *** unicell has quit IRC | 18:44 | |
| *** bnemec has joined #openstack-meeting-4 | 18:44 | |
| *** liangy has joined #openstack-meeting-4 | 18:45 | |
| *** unicell1 has quit IRC | 18:47 | |
| *** skraynev has quit IRC | 18:48 | |
| *** cathrichardson has quit IRC | 18:49 | |
| *** unicell has joined #openstack-meeting-4 | 18:50 | |
| *** unicell has quit IRC | 18:53 | |
| *** marst has quit IRC | 18:54 | |
| *** marst has joined #openstack-meeting-4 | 18:55 | |
| *** Serlex has quit IRC | 18:56 | |
| *** unicell has joined #openstack-meeting-4 | 18:56 | |
| *** erikmwilson has quit IRC | 19:12 | |
| *** erikmwilson has joined #openstack-meeting-4 | 19:13 | |
| *** krtaylor has joined #openstack-meeting-4 | 19:16 | |
| *** marst has quit IRC | 19:22 | |
| *** vishnoianil has quit IRC | 19:22 | |
| *** Sukhdev has joined #openstack-meeting-4 | 19:23 | |
| *** pmesserl_ has quit IRC | 19:24 | |
| *** cathrichardson has joined #openstack-meeting-4 | 19:24 | |
| *** pmesserli has joined #openstack-meeting-4 | 19:24 | |
| *** kylek3h has quit IRC | 19:42 | |
| *** aunnam has quit IRC | 19:45 | |
| *** dharinic has quit IRC | 19:45 | |
| *** pshedimb has quit IRC | 19:45 | |
| *** shasha_t- has quit IRC | 19:45 | |
| *** raj_singh has quit IRC | 19:45 | |
| *** sneti has quit IRC | 19:45 | |
| *** iurygregory has quit IRC | 19:47 | |
| *** iurygregory has joined #openstack-meeting-4 | 19:50 | |
| *** bobmel has joined #openstack-meeting-4 | 19:53 | |
| *** iurygregory has quit IRC | 19:56 | |
| *** bobmel has quit IRC | 19:57 | |
| *** david-lyle_ is now known as david-lyle | 19:57 | |
| *** iurygregory has joined #openstack-meeting-4 | 20:00 | |
| *** MeganR has joined #openstack-meeting-4 | 20:00 | |
| *** matrohon has joined #openstack-meeting-4 | 20:00 | |
| *** uck has joined #openstack-meeting-4 | 20:01 | |
| *** sayantan_ has quit IRC | 20:02 | |
| *** Sukhdev has quit IRC | 20:02 | |
| *** salmankhan has quit IRC | 20:08 | |
| *** hongbin has joined #openstack-meeting-4 | 20:13 | |
| *** vishnoianil has joined #openstack-meeting-4 | 20:13 | |
| *** rwallner has quit IRC | 20:14 | |
| *** rwallner has joined #openstack-meeting-4 | 20:17 | |
| *** marst has joined #openstack-meeting-4 | 20:19 | |
| *** rwallner_ has joined #openstack-meeting-4 | 20:19 | |
| *** rwallner_ has quit IRC | 20:19 | |
| *** rwallner_ has joined #openstack-meeting-4 | 20:19 | |
| *** rwallner has quit IRC | 20:21 | |
| *** marst_ has joined #openstack-meeting-4 | 20:25 | |
| *** marst has quit IRC | 20:28 | |
| *** dave-mccowan has quit IRC | 20:29 | |
| *** matrohon has quit IRC | 20:31 | |
| *** sneti has joined #openstack-meeting-4 | 20:34 | |
| *** salmankhan has joined #openstack-meeting-4 | 20:35 | |
| *** marst_ has quit IRC | 20:36 | |
| *** cathrichardson has left #openstack-meeting-4 | 20:37 | |
| *** stream10 has joined #openstack-meeting-4 | 20:40 | |
| *** dtardivel has quit IRC | 20:40 | |
| *** uck has quit IRC | 20:51 | |
| *** MeganR has quit IRC | 20:59 | |
| *** yfauser_ has quit IRC | 21:04 | |
| *** yfauser has joined #openstack-meeting-4 | 21:05 | |
| *** sneti has quit IRC | 21:05 | |
| *** hongbin has quit IRC | 21:06 | |
| *** stream10 has quit IRC | 21:06 | |
| *** cjloader_ has joined #openstack-meeting-4 | 21:07 | |
| *** sdague has quit IRC | 21:09 | |
| *** yfauser has quit IRC | 21:09 | |
| *** cjloader has quit IRC | 21:11 | |
| *** cjloader_ has quit IRC | 21:12 | |
| *** dave-mccowan has joined #openstack-meeting-4 | 21:13 | |
| *** dave-mcc_ has joined #openstack-meeting-4 | 21:17 | |
| *** dave-mccowan has quit IRC | 21:19 | |
| *** FrankZhang has quit IRC | 21:19 | |
| *** revon has joined #openstack-meeting-4 | 21:22 | |
| *** salmankhan has quit IRC | 21:25 | |
| *** krtaylor has quit IRC | 21:27 | |
| *** sneti has joined #openstack-meeting-4 | 21:30 | |
| *** salmankhan has joined #openstack-meeting-4 | 21:30 | |
| *** sneti has quit IRC | 21:30 | |
| *** yfauser has joined #openstack-meeting-4 | 21:34 | |
| *** l4yerffeJ_ has joined #openstack-meeting-4 | 21:34 | |
| *** tonytan4ever has quit IRC | 21:34 | |
| *** l4yerffeJ has quit IRC | 21:35 | |
| *** Jeffrey4l_ has joined #openstack-meeting-4 | 21:35 | |
| *** Jeffrey4l has quit IRC | 21:35 | |
| *** Sukhdev has joined #openstack-meeting-4 | 21:36 | |
| *** yfauser has quit IRC | 21:38 | |
| *** Sukhdev has quit IRC | 21:41 | |
| *** caboucha has quit IRC | 21:41 | |
| *** FrankZhang has joined #openstack-meeting-4 | 21:46 | |
| *** cjloader has joined #openstack-meeting-4 | 21:47 | |
| *** rwallner_ has quit IRC | 21:49 | |
| *** FrankZhang has quit IRC | 21:51 | |
| *** baoli has quit IRC | 21:54 | |
| *** galstrom is now known as galstrom_zzz | 21:54 | |
| *** Sukhdev has joined #openstack-meeting-4 | 21:57 | |
| *** Julien-zte has joined #openstack-meeting-4 | 21:59 | |
| *** cjloader has quit IRC | 22:05 | |
| *** uck has joined #openstack-meeting-4 | 22:05 | |
| *** Julien-zte has quit IRC | 22:13 | |
| *** krtaylor has joined #openstack-meeting-4 | 22:17 | |
| *** armax has quit IRC | 22:19 | |
| *** rfolco has quit IRC | 22:23 | |
| *** baoli has joined #openstack-meeting-4 | 22:34 | |
| *** yfauser has joined #openstack-meeting-4 | 22:35 | |
| *** gongysh has joined #openstack-meeting-4 | 22:37 | |
| *** mbruzek has quit IRC | 22:38 | |
| *** baoli has quit IRC | 22:38 | |
| *** vishnoianil has quit IRC | 22:40 | |
| *** yfauser has quit IRC | 22:40 | |
| *** vishnoianil has joined #openstack-meeting-4 | 22:41 | |
| *** hongbin has joined #openstack-meeting-4 | 22:43 | |
| *** bobh has quit IRC | 22:45 | |
| *** klamath has quit IRC | 22:59 | |
| *** rfolco has joined #openstack-meeting-4 | 23:04 | |
| *** haleyb has joined #openstack-meeting-4 | 23:10 | |
| *** pmesserli has quit IRC | 23:11 | |
| *** rfolco has quit IRC | 23:14 | |
| *** haleyb has quit IRC | 23:21 | |
| *** salmankhan has quit IRC | 23:23 | |
| *** salmankhan has joined #openstack-meeting-4 | 23:24 | |
| *** bobmel has joined #openstack-meeting-4 | 23:38 | |
| *** bobmel has quit IRC | 23:43 | |
| *** yfauser has joined #openstack-meeting-4 | 23:53 | |
| *** yfauser has quit IRC | 23:57 | |
| *** joanna has joined #openstack-meeting-4 | 23:58 | |
| *** adisky_ has quit IRC | 23:59 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!
