| *** Manuel_112 has joined #openstack-meeting-4 | 00:02 | |
| *** jamesbenson has joined #openstack-meeting-4 | 00:03 | |
| *** yifei has joined #openstack-meeting-4 | 00:03 | |
| *** Manuel_112 has quit IRC | 00:05 | |
| *** jamesbenson has quit IRC | 00:07 | |
| *** gmann has quit IRC | 00:13 | |
| *** baoli has joined #openstack-meeting-4 | 00:13 | |
| *** gmann has joined #openstack-meeting-4 | 00:13 | |
| *** yfauser has joined #openstack-meeting-4 | 00:15 | |
| *** yfauser has quit IRC | 00:19 | |
| *** lei-zh has joined #openstack-meeting-4 | 00:29 | |
| *** thorst has joined #openstack-meeting-4 | 00:49 | |
| *** thorst has quit IRC | 00:50 | |
| *** lei-zh1 has joined #openstack-meeting-4 | 00:51 | |
| *** lei-zh has quit IRC | 00:51 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 00:56 | |
| *** Manuel_112 has quit IRC | 01:00 | |
| *** baoli has quit IRC | 01:01 | |
| *** baoli has joined #openstack-meeting-4 | 01:04 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 01:04 | |
| *** dave-mccowan has joined #openstack-meeting-4 | 01:06 | |
| *** cathrich_ has joined #openstack-meeting-4 | 01:08 | |
| *** cathrichardson has quit IRC | 01:08 | |
| *** Manuel_112 has quit IRC | 01:09 | |
| *** harlowja has quit IRC | 01:13 | |
| *** zhurong has joined #openstack-meeting-4 | 01:13 | |
| *** hongbin has joined #openstack-meeting-4 | 01:14 | |
| *** kevzha01 has joined #openstack-meeting-4 | 01:15 | |
| *** bobh has quit IRC | 01:21 | |
| *** yfauser has joined #openstack-meeting-4 | 01:26 | |
| *** yfauser has quit IRC | 01:31 | |
| *** Julien-zte has quit IRC | 01:38 | |
| *** Julien-zte has joined #openstack-meeting-4 | 01:39 | |
| *** yamahata has quit IRC | 01:43 | |
| *** iyamahat has quit IRC | 01:43 | |
| *** bobh has joined #openstack-meeting-4 | 01:45 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 01:59 | |
| *** Manuel_112 has quit IRC | 02:03 | |
| *** lei-zh1 has quit IRC | 02:04 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 02:07 | |
| *** Manuel_112 has quit IRC | 02:10 | |
| *** lei-zh has joined #openstack-meeting-4 | 02:14 | |
| *** woodard has joined #openstack-meeting-4 | 02:16 | |
| *** yamamoto has joined #openstack-meeting-4 | 02:17 | |
| *** woodard has quit IRC | 02:21 | |
| *** woodard has joined #openstack-meeting-4 | 02:21 | |
| *** yfauser has joined #openstack-meeting-4 | 02:27 | |
| *** yfauser has quit IRC | 02:31 | |
| *** yfauser has joined #openstack-meeting-4 | 02:36 | |
| *** SarathMekala has joined #openstack-meeting-4 | 02:37 | |
| *** SarathMekala has quit IRC | 02:38 | |
| *** yamamoto has quit IRC | 02:38 | |
| *** yfauser has quit IRC | 02:41 | |
| *** yamamoto has joined #openstack-meeting-4 | 02:48 | |
| *** thorst has joined #openstack-meeting-4 | 02:51 | |
| *** thorst has quit IRC | 02:59 | |
| *** markvoelker has quit IRC | 02:59 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 03:01 | |
| *** Manuel_112 has quit IRC | 03:06 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 03:10 | |
| *** bobh has quit IRC | 03:11 | |
| *** Manuel_112 has quit IRC | 03:13 | |
| *** woodard has quit IRC | 03:20 | |
| *** mattmceuen has joined #openstack-meeting-4 | 03:29 | |
| *** woodard has joined #openstack-meeting-4 | 03:34 | |
| *** hongbin has quit IRC | 03:36 | |
| *** yfauser has joined #openstack-meeting-4 | 03:37 | |
| *** woodard has quit IRC | 03:40 | |
| *** woodard has joined #openstack-meeting-4 | 03:42 | |
| *** yfauser has quit IRC | 03:42 | |
| *** mattmceuen has quit IRC | 03:43 | |
| *** woodard has quit IRC | 03:46 | |
| *** hieulq has quit IRC | 03:57 | |
| *** hieulq has joined #openstack-meeting-4 | 03:57 | |
| *** yamamoto has quit IRC | 03:57 | |
| *** aavraham has joined #openstack-meeting-4 | 03:57 | |
| *** links has joined #openstack-meeting-4 | 03:58 | |
| *** yamamoto has joined #openstack-meeting-4 | 03:59 | |
| *** dave-mccowan has quit IRC | 04:01 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 04:04 | |
| *** yamamoto has quit IRC | 04:04 | |
| *** yamamoto has joined #openstack-meeting-4 | 04:05 | |
| *** Manuel_112 has quit IRC | 04:07 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 04:12 | |
| *** yamamoto has quit IRC | 04:14 | |
| *** reedip has quit IRC | 04:14 | |
| *** reedip has joined #openstack-meeting-4 | 04:15 | |
| *** yamamoto has joined #openstack-meeting-4 | 04:15 | |
| *** Manuel_112 has quit IRC | 04:17 | |
| *** yamamoto has quit IRC | 04:21 | |
| *** psachin has joined #openstack-meeting-4 | 04:21 | |
| *** trinaths has joined #openstack-meeting-4 | 04:26 | |
| *** harlowja has joined #openstack-meeting-4 | 04:31 | |
| *** janki has joined #openstack-meeting-4 | 04:33 | |
| *** yfauser has joined #openstack-meeting-4 | 04:38 | |
| *** yfauser has quit IRC | 04:44 | |
| *** yamamoto has joined #openstack-meeting-4 | 04:44 | |
| *** yamahata has joined #openstack-meeting-4 | 04:45 | |
| *** harlowja has quit IRC | 04:47 | |
| *** yfauser has joined #openstack-meeting-4 | 04:48 | |
| *** janki has quit IRC | 04:50 | |
| *** yfauser has quit IRC | 04:53 | |
| *** zhurong has quit IRC | 04:55 | |
| *** markvoelker has joined #openstack-meeting-4 | 05:00 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 05:06 | |
| *** Manuel_1_ has joined #openstack-meeting-4 | 05:08 | |
| *** Manuel_1_ has quit IRC | 05:10 | |
| *** Manuel_112 has quit IRC | 05:11 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 05:16 | |
| *** Manuel_112 has quit IRC | 05:27 | |
| *** janki has joined #openstack-meeting-4 | 05:30 | |
| *** yfauser has joined #openstack-meeting-4 | 05:34 | |
| *** markvoelker has quit IRC | 05:34 | |
| *** harlowja has joined #openstack-meeting-4 | 05:46 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 05:47 | |
| *** zhurong has joined #openstack-meeting-4 | 05:50 | |
| *** thorst has joined #openstack-meeting-4 | 05:56 | |
| *** thorst has quit IRC | 06:01 | |
| *** Adri2000 has joined #openstack-meeting-4 | 06:07 | |
| *** kzaitsev_ws has joined #openstack-meeting-4 | 06:22 | |
| *** baoli has quit IRC | 06:22 | |
| *** kzaitsev_ has joined #openstack-meeting-4 | 06:31 | |
| *** markvoelker has joined #openstack-meeting-4 | 06:31 | |
| *** kevzha01 is now known as kevinz | 06:32 | |
| *** anilvenkata has joined #openstack-meeting-4 | 06:33 | |
| *** kzaitsev_ has quit IRC | 06:37 | |
| *** harlowja has quit IRC | 06:42 | |
| *** markvoelker has quit IRC | 07:04 | |
| *** jamesbenson has joined #openstack-meeting-4 | 07:15 | |
| *** yujunz-zte has joined #openstack-meeting-4 | 07:16 | |
| *** bogdando has joined #openstack-meeting-4 | 07:17 | |
| *** jamesbenson has quit IRC | 07:20 | |
| *** adisky__ has joined #openstack-meeting-4 | 07:20 | |
| *** kkxue has joined #openstack-meeting-4 | 07:26 | |
| *** yfauser has quit IRC | 07:29 | |
| *** yfauser has joined #openstack-meeting-4 | 07:29 | |
| *** yfauser has quit IRC | 07:34 | |
| *** zeih has joined #openstack-meeting-4 | 07:43 | |
| *** egonzalez has joined #openstack-meeting-4 | 07:43 | |
| *** ralonsoh has joined #openstack-meeting-4 | 07:46 | |
| *** zeih has quit IRC | 07:53 | |
| *** zeih has joined #openstack-meeting-4 | 07:54 | |
| *** thorst has joined #openstack-meeting-4 | 07:57 | |
| *** ifat_afek has joined #openstack-meeting-4 | 07:58 | |
| ifat_afek | #startmeeting vitrage | 08:00 |
|---|---|---|
| openstack | Meeting started Wed Jul 19 08:00:38 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:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:00 |
| *** openstack changes topic to " (Meeting topic: vitrage)" | 08:00 | |
| openstack | The meeting name has been set to 'vitrage' | 08:00 |
| ifat_afek | Hi :-) | 08:00 |
| *** annarez has joined #openstack-meeting-4 | 08:01 | |
| *** zeih has quit IRC | 08:01 | |
| annarez | Hi! | 08:01 |
| *** danoffek has joined #openstack-meeting-4 | 08:01 | |
| *** alexey_weyl has joined #openstack-meeting-4 | 08:01 | |
| alexey_weyl | Hello | 08:01 |
| alexey_weyl | What is up? | 08:02 |
| *** thorst has quit IRC | 08:02 | |
| danoffek | Hi guys | 08:02 |
| *** zeih has joined #openstack-meeting-4 | 08:03 | |
| *** lei-zh has quit IRC | 08:03 | |
| *** lei-zh has joined #openstack-meeting-4 | 08:04 | |
| ifat_afek | Today’s agenda: | 08:04 |
| ifat_afek | •Sydney summit | 08:04 |
| ifat_afek | •Status and Updates | 08:04 |
| ifat_afek | •Open Discussion | 08:04 |
| ifat_afek | #topic Sydney Summit | 08:05 |
| *** openstack changes topic to "Sydney Summit (Meeting topic: vitrage)" | 08:05 | |
| ifat_afek | The Sydney summit CFP is now closed. In the ehterpad below you can find all of the Vitrage submissions. Good luck to us all | 08:05 |
| ifat_afek | #link https://etherpad.openstack.org/p/vitrage-sydney-cpf | 08:05 |
| ifat_afek | #topic Status and Updates | 08:05 |
| *** openstack changes topic to "Status and Updates (Meeting topic: vitrage)" | 08:05 | |
| annarez | good luck! | 08:05 |
| ifat_afek | Reminder about the release dates: | 08:05 |
| ifat_afek | Client libraries final releases (i.e. python-vitrageclient): July 27 | 08:06 |
| *** yujunz-zte has quit IRC | 08:06 | |
| ifat_afek | Feature freeze: July 27 | 08:06 |
| ifat_afek | Final Pike release: August 30 | 08:06 |
| *** dwj has joined #openstack-meeting-4 | 08:06 | |
| ifat_afek | python-vitrageclient will be freezed by the end of next week! If you would like to add new API functionality, or new features, you need to do it by then. | 08:06 |
| ifat_afek | After that date, we will be able to make fixes in existing features, but not to add new ones. | 08:06 |
| ifat_afek | I pushed a change that splits the Pike specs to two folders – Approved and Implemented. | 08:07 |
| ifat_afek | #link https://review.openstack.org/#/c/485076/ | 08:07 |
| ifat_afek | My updates: I worked on a bug fix for the Collectd datasource, and then we found another bug: | 08:07 |
| ifat_afek | apparently the latest Vitrage ID changes affected the Collectd datasource, and now Collectd alarms are not cleared. Fixing it is estimated with a one week work. | 08:07 |
| ifat_afek | Another update: I continue working on the Vitrage-Mistral integration. I plan to finish it before the feature freeze. | 08:07 |
| ifat_afek | That’s it for me. Who wants to update next? | 08:07 |
| *** idan_hefetz has joined #openstack-meeting-4 | 08:08 | |
| idan_hefetz | Hi | 08:09 |
| alexey_weyl | I will update | 08:09 |
| alexey_weyl | I have solved a bug that was raised | 08:10 |
| alexey_weyl | the bug happened because the evaluator is updating the smaple_timestamp in entities and it is causing problems | 08:11 |
| danoffek | Do we have a new field ? | 08:11 |
| alexey_weyl | we have decided not to update the sample_timestamp in evaluator updates on existing entities | 08:11 |
| alexey_weyl | keep working on the DB Dao | 08:11 |
| alexey_weyl | thats it | 08:11 |
| danoffek | DB Dao : | 08:11 |
| danoffek | What's the status ? | 08:11 |
| alexey_weyl | I have managed to create the vitrage database, but hasn't managed to create the tables in the database yet | 08:13 |
| danoffek | Any clue ? Need help ? | 08:13 |
| danoffek | I'm also in need of the DB :) | 08:13 |
| idan_hefetz | we had another issue with vitrage-dashbaord, causing all horizon to fail, i merged a fix yesterday. | 08:14 |
| danoffek | IdaN | 08:14 |
| *** yujunz-zte has joined #openstack-meeting-4 | 08:14 | |
| danoffek | Still waiting for Alexey answer | 08:14 |
| danoffek | DB issue still open | 08:14 |
| alexey_weyl | not yet, maybe later | 08:14 |
| danoffek | Thnks | 08:15 |
| ifat_afek | idan_hefetz: Thanks. I guess we will need to tag another version. I’ll do it next week | 08:15 |
| annarez | I have a short update | 08:16 |
| annarez | I had exams at the university so I didn't proceed a lot with the machine learning feature | 08:16 |
| annarez | but now I'm back to it | 08:16 |
| danoffek | How were the exams? | 08:16 |
| annarez | ok I hope :) | 08:16 |
| annarez | that's it for me | 08:17 |
| ifat_afek | Cool, thanks. Anyone else? | 08:17 |
| *** idan_hefetz has quit IRC | 08:20 | |
| danoffek | bye | 08:21 |
| *** danoffek has left #openstack-meeting-4 | 08:21 | |
| ifat_afek | Ok, bye everyone :-) | 08:21 |
| annarez | bye | 08:21 |
| ifat_afek | #endmeeting | 08:21 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 08:21 | |
| openstack | Meeting ended Wed Jul 19 08:21:55 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 08:21 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-07-19-08.00.html | 08:21 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-07-19-08.00.txt | 08:21 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-07-19-08.00.log.html | 08:22 |
| *** annarez has quit IRC | 08:22 | |
| *** dwj has quit IRC | 08:22 | |
| *** ifat_afek has left #openstack-meeting-4 | 08:24 | |
| *** cshen_ has joined #openstack-meeting-4 | 08:29 | |
| *** yfauser has joined #openstack-meeting-4 | 08:30 | |
| *** ralonsoh has quit IRC | 08:33 | |
| *** ralonsoh_ has joined #openstack-meeting-4 | 08:33 | |
| *** yfauser has quit IRC | 08:34 | |
| *** cshen_ has quit IRC | 08:34 | |
| *** alexey_weyl has quit IRC | 08:47 | |
| *** yujunz-zte has quit IRC | 08:48 | |
| *** kysse_ has quit IRC | 08:50 | |
| *** lei-zh has quit IRC | 08:51 | |
| *** lei-zh has joined #openstack-meeting-4 | 08:52 | |
| *** kysse has joined #openstack-meeting-4 | 09:01 | |
| *** markvoelker has joined #openstack-meeting-4 | 09:02 | |
| *** cshen_ has joined #openstack-meeting-4 | 09:05 | |
| *** yamamoto has quit IRC | 09:06 | |
| *** yamamoto has joined #openstack-meeting-4 | 09:10 | |
| *** yamamoto has quit IRC | 09:10 | |
| *** mjblack has quit IRC | 09:10 | |
| *** yfauser has joined #openstack-meeting-4 | 09:11 | |
| *** yamamoto has joined #openstack-meeting-4 | 09:14 | |
| *** yfauser has quit IRC | 09:15 | |
| *** salmankhan has joined #openstack-meeting-4 | 09:18 | |
| *** yfauser has joined #openstack-meeting-4 | 09:28 | |
| *** vishnoianil has quit IRC | 09:33 | |
| *** markvoelker has quit IRC | 09:35 | |
| *** yamamoto has quit IRC | 09:36 | |
| *** yamamoto has joined #openstack-meeting-4 | 09:36 | |
| *** sdague has joined #openstack-meeting-4 | 09:37 | |
| *** yifei has quit IRC | 09:38 | |
| *** sambetts|afk is now known as sambetts | 09:42 | |
| *** kevinz has quit IRC | 09:44 | |
| *** cshen_ has quit IRC | 09:52 | |
| *** lei-zh has quit IRC | 09:53 | |
| *** bogdando has quit IRC | 09:57 | |
| *** thorst has joined #openstack-meeting-4 | 09:58 | |
| *** thorst has quit IRC | 10:03 | |
| *** jamesbenson has joined #openstack-meeting-4 | 10:05 | |
| *** jamesbenson has quit IRC | 10:10 | |
| *** Manuel_112 has quit IRC | 10:24 | |
| *** yamahata has quit IRC | 10:30 | |
| *** salmankhan has quit IRC | 10:32 | |
| *** kysse has quit IRC | 10:32 | |
| *** markvoelker has joined #openstack-meeting-4 | 10:32 | |
| *** salmankhan has joined #openstack-meeting-4 | 10:36 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 10:40 | |
| *** kysse has joined #openstack-meeting-4 | 10:40 | |
| *** bogdando has joined #openstack-meeting-4 | 10:49 | |
| *** zhurong has quit IRC | 10:53 | |
| *** yamamoto has quit IRC | 10:55 | |
| *** neiljerram has joined #openstack-meeting-4 | 10:59 | |
| *** kysse has quit IRC | 10:59 | |
| *** markvoelker has quit IRC | 11:06 | |
| *** alexchadin has joined #openstack-meeting-4 | 11:09 | |
| *** rwallner has joined #openstack-meeting-4 | 11:10 | |
| *** armstrong has joined #openstack-meeting-4 | 11:14 | |
| *** kysse has joined #openstack-meeting-4 | 11:16 | |
| *** dave-mccowan has joined #openstack-meeting-4 | 11:26 | |
| *** yamamoto has joined #openstack-meeting-4 | 11:40 | |
| *** kysse has quit IRC | 11:40 | |
| *** kysse has joined #openstack-meeting-4 | 11:42 | |
| *** zeih has quit IRC | 11:43 | |
| *** kevzha01 has joined #openstack-meeting-4 | 11:58 | |
| *** cshen_ has joined #openstack-meeting-4 | 12:01 | |
| *** thorst has joined #openstack-meeting-4 | 12:02 | |
| *** leo_wang has quit IRC | 12:02 | |
| *** markvoelker has joined #openstack-meeting-4 | 12:03 | |
| *** yamamoto has quit IRC | 12:03 | |
| *** thorst_ has joined #openstack-meeting-4 | 12:04 | |
| *** thorst has quit IRC | 12:06 | |
| *** anilvenkata has quit IRC | 12:15 | |
| *** aavraham has left #openstack-meeting-4 | 12:19 | |
| *** yamamoto has joined #openstack-meeting-4 | 12:21 | |
| *** gmann_ has joined #openstack-meeting-4 | 12:23 | |
| *** neiljerram has quit IRC | 12:23 | |
| *** markvoelker has quit IRC | 12:25 | |
| *** markvoelker has joined #openstack-meeting-4 | 12:26 | |
| *** julim has quit IRC | 12:28 | |
| *** kevzha01 has quit IRC | 12:31 | |
| *** baoli has joined #openstack-meeting-4 | 12:31 | |
| *** ralonsoh_ has quit IRC | 12:32 | |
| *** baoli_ has joined #openstack-meeting-4 | 12:33 | |
| *** baoli has quit IRC | 12:37 | |
| *** Yumeng__ has joined #openstack-meeting-4 | 12:37 | |
| *** dimak has quit IRC | 12:38 | |
| *** dimak has joined #openstack-meeting-4 | 12:39 | |
| *** yifei has joined #openstack-meeting-4 | 12:44 | |
| *** kylek3h has joined #openstack-meeting-4 | 12:51 | |
| *** lyan has joined #openstack-meeting-4 | 12:56 | |
| *** pbourke has quit IRC | 12:57 | |
| *** lyan has quit IRC | 12:57 | |
| *** pbourke has joined #openstack-meeting-4 | 12:58 | |
| alex_xu | #startmeeting nova api | 13:00 |
| openstack | Meeting started Wed Jul 19 13:00:17 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 |
| stephenfin | o/ | 13:00 |
| gmann_ | o/ | 13:00 |
| alex_xu | ok, let us start the meeting | 13:01 |
| alex_xu | #link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/service-hyper-uuid-in-api | 13:02 |
| *** mriedem has joined #openstack-meeting-4 | 13:02 | |
| mriedem | o/ although i'm on another call | 13:02 |
| alex_xu | ^ I guess this is the last microversion we merged in this release | 13:02 |
| alex_xu | not sure we can merge other microversion, since only one week left, but let's see | 13:03 |
| gmann_ | alex_xu: mriedem what we decided on service APIs ? | 13:03 |
| mriedem | os-services and os-hypervisors? | 13:04 |
| mriedem | those changes go together | 13:04 |
| mriedem | i'll ask dansmith to review those again today | 13:04 |
| alex_xu | yea, the -2 is just for preventing one of them merged | 13:04 |
| mriedem | right | 13:04 |
| mriedem | they have to go together | 13:04 |
| gmann_ | the Idempotency behavior | 13:04 |
| alex_xu | gmann_: I guess all the people agreed on the idempotency behaviour | 13:05 |
| gmann_ | ok | 13:05 |
| alex_xu | next, we probably need to ensure the python-novaclient patch merged | 13:07 |
| alex_xu | as I know, there should be 2.52, and then 2.53 client side patch | 13:07 |
| alex_xu | gmann_: stephenfin I saw some policy docs patch last week, are all of them merged? | 13:08 |
| stephenfin | alex_xu: Yup, I think mriedem got them all merged | 13:09 |
| alex_xu | stephenfin: cool \o/, thanks for take care them | 13:09 |
| gmann_ | 1 still stuck in gate | 13:09 |
| gmann_ | https://review.openstack.org/#/c/484646/ | 13:09 |
| gmann_ | #link https://review.openstack.org/#/c/484646/ | 13:09 |
| gmann_ | i did recheck lets see | 13:09 |
| alex_xu | gmann_: cool, thanks | 13:09 |
| alex_xu | #link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/api-no-more-extensions-pike | 13:09 |
| alex_xu | ^ the last thing... | 13:10 |
| alex_xu | if I got this patch works https://review.openstack.org/#/c/485061/, then I can begin a patch to remove the code related to stevedore | 13:10 |
| gmann_ | alex_xu: and then we start merging the extensions code | 13:11 |
| alex_xu | gmann_: do we really want to merge them? | 13:11 |
| gmann_ | alex_xu: to single file. right? | 13:12 |
| gmann_ | as it is scattered in different place | 13:12 |
| alex_xu | gmann_: yea, I also afraid that may generate some huge file | 13:13 |
| *** pmesserli has joined #openstack-meeting-4 | 13:13 | |
| gmann_ | alex_xu: sure but most of them of extend response things will go on view side | 13:14 |
| gmann_ | anyways let's try few of them and see how they looks like | 13:14 |
| gmann_ | schema merge is worth to make those more readable | 13:15 |
| alex_xu | gmann_: yea, I'm also thinking about that, after freeze, let us what is the best choice | 13:15 |
| gmann_ | yea sure | 13:15 |
| *** lyan has joined #openstack-meeting-4 | 13:15 | |
| alex_xu | gmann_: I guess you only think about merge them https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/routes.py#L273-L281 ? | 13:15 |
| gmann_ | yea for server things | 13:16 |
| gmann_ | alex_xu: let me try some merge of schema and respone extend and see how it looks like | 13:16 |
| gmann_ | after FF | 13:16 |
| alex_xu | gmann_: cool, thanks | 13:16 |
| *** mriedem is now known as mriedem_meeting | 13:17 | |
| alex_xu | gmann_: I'm also thinking about the case like we deprecated the network quotas, we may forget them in somewhere. that is due to we separate the network stuff anywhere. | 13:18 |
| alex_xu | maybe we should group thing in another way | 13:18 |
| gmann_ | yea | 13:18 |
| alex_xu | but anyway, i'm not sure how to do it. let see that detail later | 13:19 |
| gmann_ | yea, with some example patches it will be more clear | 13:19 |
| *** ralonsoh has joined #openstack-meeting-4 | 13:19 | |
| *** ralonsoh has quit IRC | 13:20 | |
| alex_xu | ok, that is all I have, anything else anyone want to bring up? | 13:20 |
| *** ralonsoh has joined #openstack-meeting-4 | 13:20 | |
| gmann_ | nothing from my side | 13:20 |
| alex_xu | ok, let us close the meeting, thanks all! | 13:21 |
| alex_xu | #endmeeting | 13:21 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 13:21 | |
| openstack | Meeting ended Wed Jul 19 13:21:44 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:21 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-07-19-13.00.html | 13:21 |
| gmann_ | thanks alex_xu | 13:21 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-07-19-13.00.txt | 13:21 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-07-19-13.00.log.html | 13:21 |
| *** woodard has joined #openstack-meeting-4 | 13:23 | |
| *** woodard has quit IRC | 13:23 | |
| *** woodard has joined #openstack-meeting-4 | 13:24 | |
| *** gmann_ has quit IRC | 13:26 | |
| *** dimak has quit IRC | 13:31 | |
| *** cathrichardson has joined #openstack-meeting-4 | 13:31 | |
| *** dimak has joined #openstack-meeting-4 | 13:31 | |
| *** Yumeng__ has left #openstack-meeting-4 | 13:33 | |
| *** cathrich_ has quit IRC | 13:33 | |
| *** julim has joined #openstack-meeting-4 | 13:36 | |
| *** cshen_ has quit IRC | 13:36 | |
| *** bobh has joined #openstack-meeting-4 | 13:37 | |
| *** woodard_ has joined #openstack-meeting-4 | 13:39 | |
| *** woodard has quit IRC | 13:39 | |
| *** trinaths has left #openstack-meeting-4 | 13:45 | |
| *** lihi has quit IRC | 13:47 | |
| *** lihi has joined #openstack-meeting-4 | 13:48 | |
| *** hongbin has joined #openstack-meeting-4 | 13:49 | |
| *** jrist has quit IRC | 13:53 | |
| *** yifei has quit IRC | 13:55 | |
| *** alexchadin has quit IRC | 14:02 | |
| *** Beppe has joined #openstack-meeting-4 | 14:02 | |
| *** suzhengwei has joined #openstack-meeting-4 | 14:03 | |
| *** armstrong has quit IRC | 14:03 | |
| *** jrist has joined #openstack-meeting-4 | 14:06 | |
| *** Beppe has quit IRC | 14:09 | |
| *** yamamoto has quit IRC | 14:09 | |
| *** anilvenkata has joined #openstack-meeting-4 | 14:10 | |
| *** hoppalm has joined #openstack-meeting-4 | 14:10 | |
| *** kevzha01 has joined #openstack-meeting-4 | 14:16 | |
| *** links has quit IRC | 14:18 | |
| *** woodard_ has quit IRC | 14:20 | |
| *** marst has joined #openstack-meeting-4 | 14:35 | |
| *** Sukhdev has joined #openstack-meeting-4 | 14:39 | |
| *** suzhengwei has quit IRC | 14:41 | |
| *** tobberydberg has joined #openstack-meeting-4 | 14:42 | |
| *** jamesbenson has joined #openstack-meeting-4 | 14:45 | |
| *** Manuel_112 has quit IRC | 14:48 | |
| *** tobberydberg has quit IRC | 14:48 | |
| *** abhishekk_ has joined #openstack-meeting-4 | 14:49 | |
| *** rhallisey has joined #openstack-meeting-4 | 14:50 | |
| *** premsankar has joined #openstack-meeting-4 | 14:54 | |
| *** lyan has quit IRC | 14:55 | |
| *** iyamahat has joined #openstack-meeting-4 | 14:59 | |
| *** galstrom_zzz is now known as galstrom | 15:00 | |
| *** rhallisey has left #openstack-meeting-4 | 15:01 | |
| *** janki has quit IRC | 15:03 | |
| *** mriedem_meeting is now known as mriedem | 15:03 | |
| *** cathrichardson has left #openstack-meeting-4 | 15:06 | |
| *** mriedem has left #openstack-meeting-4 | 15:06 | |
| *** psachin has quit IRC | 15:08 | |
| *** kevzha01 has quit IRC | 15:08 | |
| *** yamamoto has joined #openstack-meeting-4 | 15:09 | |
| *** kevzha01 has joined #openstack-meeting-4 | 15:13 | |
| *** yamahata has joined #openstack-meeting-4 | 15:15 | |
| *** lyan has joined #openstack-meeting-4 | 15:18 | |
| *** yamamoto has quit IRC | 15:19 | |
| *** liangy has joined #openstack-meeting-4 | 15:21 | |
| *** rwallner has quit IRC | 15:22 | |
| *** lyan has quit IRC | 15:23 | |
| *** kevzha01 has quit IRC | 15:23 | |
| *** rwallner has joined #openstack-meeting-4 | 15:23 | |
| *** cholcombe has quit IRC | 15:26 | |
| *** cholcombe has joined #openstack-meeting-4 | 15:26 | |
| *** woodard has joined #openstack-meeting-4 | 15:28 | |
| gibi | sjmc7: hi! You missed me yesterday. I tried to answer your question about the instance status on the ML http://lists.openstack.org/pipermail/openstack-dev/2017-July/119891.html | 15:29 |
| sjmc7 | ah, great, thankyou | 15:29 |
| sjmc7 | urk. i don’t really want to reproduce that map if i can avoid it | 15:30 |
| *** woodard has quit IRC | 15:30 | |
| sjmc7 | i guess i’ll do a simplified version and wait til it’s added in queens | 15:30 |
| *** woodard has joined #openstack-meeting-4 | 15:31 | |
| gibi | sjmc7: I understand your pain | 15:32 |
| sjmc7 | i should’ve noticed it earlier, my bad | 15:32 |
| gibi | sjmc7: If it is super important for searchlight then I suggest to express that on the ML. Let's see if the cores agree to push that change in as a bug | 15:33 |
| *** Duonghq has joined #openstack-meeting-4 | 15:33 | |
| sjmc7 | ok, i’ll reply to it. it’s kind of important; the ‘Status’ field is what horizon makes most prominent and most users understand | 15:33 |
| gibi | sjmc7: I can offer my help to implement the change as a bugfix but I don't know if cores will accept that at this point of Pike | 15:34 |
| *** abhishekk_ has quit IRC | 15:35 | |
| *** Duonghq has quit IRC | 15:38 | |
| *** kzaitsev_ws has quit IRC | 15:38 | |
| *** chyka has joined #openstack-meeting-4 | 15:38 | |
| *** Sukhdev_ has joined #openstack-meeting-4 | 15:39 | |
| *** anilvenkata has quit IRC | 15:39 | |
| *** iberezovskiy has quit IRC | 15:40 | |
| *** iberezovskiy has joined #openstack-meeting-4 | 15:43 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 15:45 | |
| *** jamesbenson has quit IRC | 15:46 | |
| *** Duonghq has joined #openstack-meeting-4 | 15:48 | |
| *** emagana has joined #openstack-meeting-4 | 15:50 | |
| *** inc0 has joined #openstack-meeting-4 | 15:50 | |
| *** Rockyg has joined #openstack-meeting-4 | 15:52 | |
| *** vishwana_ has joined #openstack-meeting-4 | 15:52 | |
| *** kzaitsev_ws has joined #openstack-meeting-4 | 15:52 | |
| *** mwhahaha has joined #openstack-meeting-4 | 15:53 | |
| *** flaper87 has joined #openstack-meeting-4 | 15:53 | |
| *** Manuel_112 has quit IRC | 15:54 | |
| *** vishwanathj has quit IRC | 15:56 | |
| *** Daidv has joined #openstack-meeting-4 | 15:57 | |
| *** spsurya_ has joined #openstack-meeting-4 | 15:58 | |
| *** abhishekk_ has joined #openstack-meeting-4 | 15:58 | |
| *** jascott1 has joined #openstack-meeting-4 | 15:58 | |
| *** shardy has joined #openstack-meeting-4 | 15:58 | |
| *** vhosakot has joined #openstack-meeting-4 | 16:00 | |
| vhosakot | o/ | 16:00 |
| sbezverk | o/ | 16:00 |
| spsurya_ | o/ | 16:00 |
| kfox1111 | o/ | 16:00 |
| inc0 | #startmeeting kolla | 16:00 |
| flaper87 | o/ | 16:00 |
| openstack | Meeting started Wed Jul 19 16:00:39 2017 UTC and is due to finish in 60 minutes. The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
| Daidv | o/ | 16:00 |
| *** openstack changes topic to " (Meeting topic: kolla)" | 16:00 | |
| openstack | The meeting name has been set to 'kolla' | 16:00 |
| inc0 | #topic rollcall | 16:00 |
| spsurya_ | woot 0/ | 16:00 |
| flaper87 | o/ | 16:00 |
| Duonghq | o/ | 16:00 |
| kfox1111 | o/ | 16:00 |
| *** openstack changes topic to "rollcall (Meeting topic: kolla)" | 16:00 | |
| sbezverk | o/ | 16:01 |
| Jeffrey4l | o/ | 16:01 |
| *** caboucha has joined #openstack-meeting-4 | 16:01 | |
| egonzalez | woot o/ | 16:01 |
| *** serlex has joined #openstack-meeting-4 | 16:01 | |
| rwellum | o/ | 16:01 |
| vhosakot | woot \o/ | 16:01 |
| EmilienM | hello | 16:01 |
| jascott1 | woot | 16:01 |
| inc0 | let's get to it right away | 16:02 |
| inc0 | #topic announcement | 16:02 |
| *** openstack changes topic to "announcement (Meeting topic: kolla)" | 16:02 | |
| shardy | Hi all! | 16:02 |
| mwhahaha | o/ | 16:03 |
| inc0 | We're closing to P-3 which will be feature freeze for us, I'm not aware of any features that will be hit by this, but just so you know. Regular services has it next week, which gives us 2 weeks more | 16:03 |
| kfox1111 | special welcome to all the tripleo folks. :) | 16:03 |
| inc0 | we need to make sure upgrades works after services tags | 16:03 |
| inc0 | yup and that, welcome :) | 16:03 |
| inc0 | let's get to meaty stuff then | 16:03 |
| sdake | o/ | 16:03 |
| inc0 | #topic TripleO+Kolla-k8s discussion (inc0) | 16:03 |
| *** openstack changes topic to "TripleO+Kolla-k8s discussion (inc0) (Meeting topic: kolla)" | 16:03 | |
| flaper87 | o/ | 16:04 |
| flaper87 | if you don't mind, I've some stuff I can copy/pasta to introduce the topic | 16:04 |
| krtaylor | o/ | 16:04 |
| inc0 | #link https://etherpad.openstack.org/p/tripleo-ptg-queens-kubernetes this is etherpad flaper87 linked | 16:04 |
| *** aarefiev is now known as aarefiev_afk | 16:04 | |
| inc0 | flaper87: go ahead | 16:04 |
| kfox1111 | flaper87: sounds good. | 16:04 |
| flaper87 | sorry in advance ;) | 16:04 |
| flaper87 | hey folks, thanks for hosting us. Going to cut to the chase. TripleO is looking for a tool to manage an OpenStack deployment on Kubernetes. | 16:04 |
| flaper87 | Preferably, this tool should be based on Ansible, given the current goal of the project to migrate a significant part of the code base to it. | 16:04 |
| flaper87 | I've prepared an etherpad that will hopefully help framing the meeting as I do want to take the most out of it. https://etherpad.openstack.org/p/tripleo-ptg-queens-kubernetes | 16:04 |
| flaper87 | By all means, you should not let the etherpad dictate what should be talked about but I do want us to stay away from discussions about competition, wheel re-invention or any other thing that is not going to help with what I'm (we are) actually interested in: What can we collaborate on? | 16:04 |
| flaper87 | I know there are *many* things we have to say and want to talk about but this is IRC and the time is limited. Let's try to allow ppl to speak and participate and avoid doing brain dumps on IRC. I'm not good with 10 parallel IRC conversations. | 16:04 |
| flaper87 | I've listed some of the motivations why I believe a helm based solution would not be the best solution for TripleO. It has more to do with TripleO current direction than Helm itself, although there are some aspects directly related to Helm that I'm not entirely happy with. | 16:04 |
| flaper87 | This is of course my opinion based on my own research. Some members of the TripleO team seem to agree with this assestment while others seem to disagree. This is perfect! | 16:04 |
| flaper87 | I think we know what we would have to do if TripleO were to adopt kolla-kubernetes (k-k) and the different benefits of this. We would all contribute to k-k, we would have ansible+helm, etc. | 16:04 |
| flaper87 | Now, what would it mean for OpenStack and TripleO if the team decides to not use k-k but to wok on a solution like the one proposed in the email (ansible --(direct)-> k8s )? Can we still use k-k to some extent? Are there things we can collaborate on? What would we be missing (besides the opportunity to collaborate on k-k, which is important)? | 16:04 |
| vhosakot | wow, that's fast typing | 16:04 |
| * flaper87 is trying to save time by typing ahead of the meeting | 16:04 | |
| shardy | lol :) | 16:05 |
| * flaper87 stfu and lets ppl talk | 16:05 | |
| flaper87 | hope that's a fair intro | 16:05 |
| inc0 | ok, so I did some preparation myself and I have few comments;) | 16:05 |
| flaper87 | awesome | 16:06 |
| shardy | Yeah, I think the tl;dr is what would collaboration look like if it was just ansible+k8s vs helm+k8s | 16:06 |
| *** sridhar_ram has quit IRC | 16:06 | |
| inc0 | there are few reasons why helm might be good idea after all and at least won't be that impactful | 16:06 |
| sdake | shardy that is how i parsed it as well | 16:06 |
| shardy | e.g I'm intersted in how the archtiecture might look if we layered things to enable e.g common ansible roles | 16:06 |
| flaper87 | shardy: sdake yup | 16:06 |
| coolsvap | o/ | 16:07 |
| inc0 | 1. in our arch helm is just a templating language, you don't even really need tiller (service run in k8s) for kolla-k8s | 16:07 |
| *** trinaths has joined #openstack-meeting-4 | 16:07 | |
| *** slagle has joined #openstack-meeting-4 | 16:07 | |
| sdake | inc0 - i think the thing that interests flaper87 and shardy is what would collaboratin look like in a helm-free world | 16:07 |
| inc0 | so clue of discussion here is how do we get from templates to k8s yamls | 16:07 |
| kfox1111 | so, part of the issue there I think is language. | 16:07 |
| trinaths | o/ | 16:08 |
| *** anilvenkata has joined #openstack-meeting-4 | 16:08 | |
| kfox1111 | we did origionally use jinja2 for the templates. | 16:08 |
| inc0 | because I assume we should strive to have yamls similar if not identical | 16:08 |
| kfox1111 | then spent months switching to gotl. (go templating language). | 16:08 |
| *** bogdando has quit IRC | 16:08 | |
| inc0 | and now helm accepts different templating languages so technically (maybe!) we could switch back to jinja and be consumable by both ansible and helm?;) | 16:09 |
| kfox1111 | we could either come up with a gotl -> jinja2 converter, or a meta yaml template that can generate the other two types of templates, but that gets back to that xkcd comic. :/ | 16:09 |
| sdake | shardy to answer your question in a tldr format - helm is based upon gotpl and ansible is fundamentally based upon jinja2 | 16:09 |
| kfox1111 | inc0: possible, but its only theoreticle. | 16:09 |
| sdake | these two DSLs can be translated | 16:09 |
| kfox1111 | they don't have any non gotl template engine currently. | 16:09 |
| *** dprince has joined #openstack-meeting-4 | 16:09 | |
| inc0 | jascott1: do you knwo anything about helm support for jinja2? | 16:09 |
| jascott1 | no | 16:09 |
| jascott1 | can look into it | 16:10 |
| inc0 | please do | 16:10 |
| kfox1111 | inc0: helm itself has no interest in implementing it. but wont block it. | 16:10 |
| jascott1 | they are all out this week | 16:10 |
| kfox1111 | its a go vs python issue. | 16:10 |
| flaper87 | so, assuming the templating thing is not a problem, what would we be able to collaborate on? Can we use kolla-kubernetes roles anyway ? | 16:10 |
| flaper87 | what parts of these roles can we use? | 16:10 |
| sdake | the fundamental thing i think possibly shardy or flaper87 don't understand is the amount to produce the "fundamental building blocks of openstack on kubernetes" | 16:10 |
| flaper87 | we can come up with ansible modules that would make the templating part "pluggable/flexible" I think | 16:10 |
| inc0 | flaper87: as of today k8s is collection of k8s resources with little orchestration | 16:10 |
| kfox1111 | flaper87: at the moment we dont' have roles. | 16:11 |
| sdake | rather amount of work | 16:11 |
| inc0 | so it's very unopinionated today | 16:11 |
| kfox1111 | lets back up and let me try and explain where I think we're at. | 16:11 |
| shardy | sdake: ack, I think it's more than just the templating language, as e.g the OpenShift community have interest in using "playbook bundles" to define the apps deployed on k8s and their lifecycle | 16:11 |
| * flaper87 reads carefully | 16:11 | |
| inc0 | that being said we have things like this | 16:11 |
| shardy | https://github.com/openshift/ansible-service-broker | 16:11 |
| inc0 | #link https://review.openstack.org/#/c/473588/ | 16:11 |
| kfox1111 | tripleo's got a pretty solid installer and is looking at changing the orchestration engine. | 16:11 |
| shardy | so, while we don't have to do exactly that, there's interest in how the different approaches may align and/or be integrated | 16:11 |
| inc0 | shardy: what I'm saying is kolla-k8s is really written in a way that it's nothing more than templating | 16:12 |
| sdake | shardy - kolla-kubernetes really has no orchestration that is feasible at this time - only the fundamental buliding blocks of building openstack on kubernetes | 16:12 |
| inc0 | and another alternative would be to write gotpl parser in python, make ansible module out of it and just use kolla-k8s resources | 16:12 |
| flaper87 | shardy: your last message is important. This conclusion has little to do with what OpenShift is doing and more with what is useful for TripleO that looks like a good common ground | 16:12 |
| inc0 | we don't use helm lifecycle features | 16:12 |
| kfox1111 | kolla kubernetes has gotten to the point where it is the equivelenet of kolla-containers for k8s. a db of prebaked openstack building blocks. | 16:12 |
| *** liangy has quit IRC | 16:12 | |
| kfox1111 | the middle piece, the orchestration piece is really rather undefined in both projects at the moment. | 16:12 |
| inc0 | yes, and helm in our way of using it won't stand in a way | 16:13 |
| inc0 | it's again, just client-only template parser | 16:13 |
| flaper87 | inc0: sdake kfox1111 let's try to just have 1 conversation at a time. I think what kfox1111 is saying is important background. Let's build on top of that | 16:13 |
| inc0 | right | 16:13 |
| inc0 | issue is, our building blocks are written in gotph | 16:13 |
| shardy | flaper87: yes, I'm just trying to provide a little more context around your ML approach/summary, and why the prototyping has gone in that direction so far | 16:14 |
| inc0 | gotpl | 16:14 |
| sdake | flaper87 i am expanding on kfox1111 's statements above not 2 conversations :) | 16:14 |
| flaper87 | sdake: sorry, got confused :P Thanks! | 16:14 |
| inc0 | really what we can say is kolla-k8s doesn't use helm, it's written in gotpl and that's it | 16:14 |
| inc0 | and have helm-based dir structure | 16:14 |
| kfox1111 | yeah, its more gotl then helm, but can be consumed direcly as a helm chart. | 16:15 |
| flaper87 | inc0: so, how do you guys run services on k8s? Is that by calling kubectl directly ? | 16:15 |
| inc0 | no, we call helm, but helm underneath calls kubectl | 16:15 |
| sdake | flaper87 parsing gotpl is moost optimal atm using helm | 16:15 |
| kfox1111 | we currently launch via helm, but you could also: | 16:15 |
| inc0 | we could do sth like "gotemplatethis our-dir && kubectl create -f our-dir" | 16:16 |
| kfox1111 | helm template kolla/nova-api-deployment | kubectl create -f - | 16:16 |
| kfox1111 | or whatever golang thing to do the generation. | 16:16 |
| inc0 | where helm template is just generation thingy;) | 16:16 |
| kfox1111 | helm template is a command that runs gotl templtaing without tiller. | 16:16 |
| sdake | fundamentally helm is not an orchestration system | 16:16 |
| inc0 | so I understand issue of new templating language and I, for one, am not huge fan of go template | 16:16 |
| flaper87 | mind if I ask whether ansible-kubernetes module was ever an option? | 16:17 |
| inc0 | however, I'd like to say that in my most honest of opinions, it's harder to learn how to run services on top of k8s than templating language | 16:17 |
| flaper87 | or wasn't it around at that time? | 16:17 |
| kfox1111 | yeah. I have my qualms about it. but it is an established k8s standard too. | 16:17 |
| inc0 | flaper87: https://review.openstack.org/#/c/473588/ | 16:17 |
| EmilienM | sdake: yeah, looks like a wrapper | 16:17 |
| sdake | the challenge you will have flaper87 and shardy with kfox1111 's approach is that understanding the *building blocks* is complex - took me 3 months of constantly banging on it to understand them | 16:17 |
| inc0 | history behind our helm is an intereting one | 16:18 |
| sdake | inc0 lets just not get into the histroy :) | 16:18 |
| inc0 | I'd be happy to tell you all about it over drinks;) | 16:18 |
| kfox1111 | sdake: it takes longer to write stable k8s objects for openstack. | 16:18 |
| flaper87 | inc0: I like that! Let's put the full history on hold | 16:18 |
| sdake | kfox1111 agreed | 16:18 |
| flaper87 | I'm more interested in: "We looked into it but it's not good" | 16:18 |
| inc0 | thing is, ansible was our first run and we had some progress over time | 16:18 |
| flaper87 | or "It wasn't around" | 16:18 |
| inc0 | but we jumped on helm | 16:19 |
| flaper87 | etc | 16:19 |
| flaper87 | ok | 16:19 |
| inc0 | and after that our learning and ideas grew as well | 16:19 |
| flaper87 | I'll take that and I'll pay for the full story | 16:19 |
| sdake | flaper87 you are asking for history then - our history in summation was that we wrote the templates in jinja2- then converted them to gotpl | 16:19 |
| sdake | same building blocks | 16:19 |
| flaper87 | I'll take that and I'll pay for the full story :D | 16:19 |
| inc0 | and I think ansible is great tool for the job today, part of me wishes that we'd stick to it all along, but ansible is a bit loaded with religion among ops | 16:19 |
| flaper87 | (with beers) | 16:19 |
| slagle | could someone possible point me to the templates in kolla-k8s that might parallel with what is done in e.g., https://github.com/fusor/apb-examples/blob/master/rhscl-mariadb-apb/roles/provision-rhscl-mariadb-apb/tasks/main.yml | 16:19 |
| sdake | slagle we would hvae to break eqaqch of th ose into distiinct objects - because that is what kk does | 16:20 |
| flaper87 | so, if tripleo decideds to go with the ansible-kubernetes modules. What are the possible areas where we could collaborate? | 16:20 |
| slagle | i was thinking that might be an area to collaborate, e.g., I assume helm has some parallel to the ansible k8s_v1_service ansible module | 16:20 |
| kfox1111 | slagle: https://github.com/openstack/kolla-kubernetes/tree/master/helm/microservice/mariadb* | 16:20 |
| inc0 | flaper87: modules themselves ofc | 16:20 |
| kfox1111 | note, those are for deployment, not orchestration. so you would still use an ansible role to do the deployment step by step. | 16:21 |
| inc0 | and frankly? I'd love to have these playbooks in kolla-k8s or at least pluggable to kolla-k8s | 16:21 |
| inc0 | we don't have orch figured out, you want to figure out orch, we do to | 16:21 |
| inc0 | we can figure out orch together and put it in whatever repo | 16:21 |
| slagle | kfox1111: thanks | 16:21 |
| flaper87 | inc0: I like that, I like the sound of that | 16:21 |
| inc0 | but there is no need to have tripleo orch and kolla orch as far as I'm concerned | 16:21 |
| flaper87 | or the look of that | 16:21 |
| flaper87 | inc0: yes, I think we agree on that | 16:22 |
| inc0 | we can put it under tripleo, we can put it under kolla or have new one completely | 16:22 |
| flaper87 | (btw, I'll be incorporating some summaries of this meeting into the etherpad and later the email thread) | 16:22 |
| inc0 | logistics can be solved | 16:22 |
| kfox1111 | I think likely there may be some of both for a while. | 16:22 |
| sdake | kfox1111 tend to agree | 16:22 |
| kfox1111 | since tripleo must have migration from baremetal to containers, | 16:22 |
| flaper87 | kfox1111: as long as the goal is to converge those, I think it's fine | 16:22 |
| kfox1111 | some of the roles may be pretty tripleo historic. | 16:22 |
| sdake | the problem with the tripelo approach is it is openshift only | 16:22 |
| inc0 | today biggest barrier imho would be this go tpl as it doesn't make much sense in ansible world, we can discuss which approach would be best | 16:22 |
| *** caboucha has quit IRC | 16:22 | |
| kfox1111 | once the migration has been made though, maybe they can all be merged? | 16:23 |
| flaper87 | we can still share some of the playbooks and stuff | 16:23 |
| rwellum | If we can serve kolla-k8s with helm, as it works already, I don't understand the aversion to helm? | 16:23 |
| shardy | kfox1111: yeah, I think we can probably leave the upgrade problem aside for now, but it's something to consider for sure ;) | 16:23 |
| inc0 | and frankly? (this is my personal opinion, not official PTLish), after we release 1.0, I wouldn't be opposed to dropping gotpl and moving back to jinja (if we have manpower to do it) | 16:23 |
| * sdake smacks inc0 around | 16:23 | |
| dprince | sdake: some things optional things may require openshift but I think the underlying building blocks could be shared right? | 16:23 |
| kfox1111 | shardy: my number one concern is usually upgrades. if you lick that problem, usually all the rest is easy. :) | 16:23 |
| inc0 | since again, it's just templating yamls, we can provice smooth upgrade experience | 16:23 |
| *** bobh has quit IRC | 16:24 | |
| sdake | dprince right - i was speaking only of orchestration | 16:24 |
| kfox1111 | shardy: thats another reason why kolla-kubernetes looks the way it does. to facilitate upgrades. :) | 16:24 |
| kfox1111 | so, maybe one question is how tripleo wants to do roles. | 16:24 |
| sbezverk | inc0: why?? in 6 month there will be another group of dudes who asked to re-write everything to XYZ thing, so we do it agaoin? | 16:24 |
| sdake | dprince ansible-service-broker is openshift only - more specifically | 16:24 |
| shardy | kfox1111: Yeah, I just mean the details of upgrading from TripleO as it exists today may not be a common problem? But maybe it's the same as the brownfield problems that were discussed in atlanta | 16:24 |
| sbezverk | maybe at one point we should stop bending for everybody | 16:24 |
| flaper87 | sdake: it's not openshift only. It uses openshift for their examples | 16:24 |
| kfox1111 | shardy: exactly. | 16:24 |
| flaper87 | let's not bring openshift into the conversation, please | 16:24 |
| inc0 | sbezverk: I'm just throwing this idea around, not planning anything:( | 16:25 |
| inc0 | keep an open mind folks | 16:25 |
| flaper87 | I'm interested in kubernetes and how we can support the upstream community and enable collaboration | 16:25 |
| kfox1111 | would tripleo be wanting to do an ansible role per openstack service? | 16:25 |
| shardy | kfox1111: fwiw it's likely to be container->container upgrades, as we're close to switching to kolla containers running on baremetal, just not orchestrated by k8s yet | 16:25 |
| inc0 | but this is pure priority discussion | 16:25 |
| kfox1111 | shardy: ah. ok. that would probably make things easier. | 16:25 |
| flaper87 | TBH, I like the idea of collaborating on the orch pieces a lot | 16:26 |
| dprince | shardy: true, but we'd likely still have remnants of old baremetal stuff to cleanup by then | 16:26 |
| sdake | back on target - the common area for collaboration is in the templating of the bulding blocks - which at this point and probably forever will be gotpl bsaed | 16:26 |
| dprince | shardy: maybe :) | 16:26 |
| sdake | this is fundmanetally how we collobrate on docker images as well | 16:26 |
| sdake | (at the building block level) | 16:26 |
| sbezverk | I think if somebody does not want to use helm just for some political reason, is not good enough to start discussion to switch from it.. | 16:26 |
| inc0 | flaper87: building blocks are pretty much ready, but there are always missing pieces | 16:26 |
| flaper87 | inc0: roger | 16:26 |
| inc0 | so if we use existing building blocks and together write orch from scrach | 16:26 |
| inc0 | we can get there pretty soon | 16:26 |
| flaper87 | also, note tripleo is currently using kolla-images and I don't think (keep me honest here) there's any plan to change that | 16:27 |
| sdake | flaper87 i've depoyed kk in 3 node with ha - works like a champ with the buliding blocks as they are | 16:27 |
| inc0 | especially that we (kolla-k8s) were playing with different orch mechanisms for a year now | 16:27 |
| inc0 | and have lot of knowledge to bring to the table | 16:27 |
| EmilienM | I see some collaboration on ansible role to generate configuration files for OpenStack services | 16:27 |
| kfox1111 | plus we have been gating almost everything for a long time now too. a lot of tests have gone into the objects. | 16:27 |
| flaper87 | EmilienM: was going to get to that now! :) | 16:27 |
| EmilienM | flaper87 & dhellmann already kicked off serious amount of work, that is demoable today | 16:27 |
| inc0 | as of today config files are generated by ansible | 16:27 |
| inc0 | ripped out of kolla-ansible really, but that works | 16:28 |
| EmilienM | inc0: we have something without doing templating | 16:28 |
| EmilienM | and we use pure oslo.config tooling | 16:28 |
| flaper87 | inc0: could you point us to the pieces of kolla-ansible that do this? | 16:28 |
| kfox1111 | EmilienM: yeah, been following that tangentially a bit. what I've seen looks really slick. :) | 16:28 |
| kfox1111 | flaper87: the fork of kolla-ansible genconfig in kolla-kubernetes was done just for development purpuses. | 16:29 |
| kfox1111 | it wasn't intended to be perminant. | 16:29 |
| inc0 | yeah, but that injects dependency on oslo.config to deploy node. something to discuss. If we run ansible play in container (my personal favorite today) it's not an issue | 16:29 |
| EmilienM | kfox1111: we gave up (for now) the etcd idea | 16:29 |
| shardy | Yeah leaving the comments re helm aside we definitely have clear scope for collaboration on orchestration and config management here IMO | 16:29 |
| sdake | fundamentally the kk buliding blocks don't require collobration on configuration methods - so there are two areas to collaborate (indepdently) | 16:29 |
| flaper87 | kfox1111: glad you like it so far. I've made some extra progress | 16:29 |
| kfox1111 | EmilienM: yeah. I think the etcd one has a lot of ugly corner cases. | 16:29 |
| inc0 | EmilienM: https://github.com/openstack/kolla-kubernetes/tree/master/ansible | 16:29 |
| inc0 | flaper87: sorry | 16:29 |
| flaper87 | kfox1111: roger | 16:29 |
| inc0 | ^ | 16:29 |
| flaper87 | inc0: thanks | 16:29 |
| *** bobh has joined #openstack-meeting-4 | 16:30 | |
| kfox1111 | for kolla-kubernetes, configgeneration is kind of like orchestration. | 16:30 |
| kfox1111 | a nice reference implementation isn't done yet, and you can always use your own. | 16:30 |
| flaper87 | kfox1111: ideally, we would all use the same tool/roles here | 16:30 |
| inc0 | yeah | 16:30 |
| sdake | flaper87 - i'd suggest trying the ansible orchestraiton playb0ook we do hve to do deploymnet today to really get a feel for what building blocks are in the gotpl format | 16:30 |
| kfox1111 | kubectl create configmap <service>.... is all it needs. | 16:30 |
| inc0 | no need for duplication and none of us is emotionally bound to this ansible | 16:31 |
| mwhahaha | config generation should be a step in the orchestration but should be properly separated so it can be reused | 16:31 |
| kfox1111 | flaper87: +1. just saying, if you have someting great already, it might be something we all can use. :) | 16:31 |
| flaper87 | the current PoC is pure ansible role but I think it'd be better to have an ansible module, which I'm playing with already. Then everyone can upload it to k8s the way they want | 16:31 |
| inc0 | we put it there because we didn't want to write it;) | 16:31 |
| EmilienM | mwhahaha: yes, like in a role probably | 16:31 |
| flaper87 | kfox1111: will send emails soon (in between travels) | 16:31 |
| kfox1111 | flaper87: sounds good. :) | 16:31 |
| inc0 | flaper87: how about this helm module you wrote other day?;) | 16:31 |
| inc0 | again, if we write ansible module that could do helm template, we're good | 16:32 |
| flaper87 | inc0: the ansible one? That was part of my experimentation and research to be able to call helm from ansible | 16:32 |
| kfox1111 | inc0: yeah. I think thats all it would take. | 16:32 |
| flaper87 | the module is in ansible core now and it can be consumed after the next release | 16:32 |
| inc0 | that and learning gotpl which isn't that bad | 16:32 |
| flaper87 | seems to be working decently but it's of course missing some features | 16:32 |
| flaper87 | anyway, that removes the need of calling helm from the CLI | 16:32 |
| inc0 | we just need helm template thing really | 16:32 |
| kfox1111 | sweet. :) | 16:33 |
| flaper87 | inc0: that can be added | 16:33 |
| kfox1111 | I've been talking with technosophos about merging the template plugin directly into helm. | 16:33 |
| kfox1111 | he was neutral to mildly supportive of the idea. | 16:33 |
| kfox1111 | I think if more folks ask, it will tip the scales. | 16:33 |
| inc0 | especially if we commit to writing the thing | 16:33 |
| kfox1111 | yeah. he already basically wrote the thing for us. :) | 16:34 |
| inc0 | I mean making it mergable because it's written | 16:34 |
| *** david-lyle has quit IRC | 16:34 | |
| inc0 | so, my personal favorite direction now is: | 16:34 |
| kfox1111 | but it requires 2 binaries instead of 1. this would just merge it into one. | 16:34 |
| inc0 | 1. use kolla-k8s resources | 16:34 |
| EmilienM | flaper87: do you mind sharing the link of the help module that you wrote? | 16:34 |
| sdake | slagle back on the tripleo playbook - if you reach the logical conclusion of compute kit - you end up with approximately 170 plays | 16:35 |
| inc0 | 2. use ansible-helm module to render templates | 16:35 |
| EmilienM | flaper87: helm* | 16:35 |
| sdake | slagle each of these steps is represented by a separate gotpl object in kolla-kubernetes | 16:35 |
| flaper87 | EmilienM: inc0 kfox1111 https://github.com/ansible/ansible/blob/2a7e586801712c949263315dd79580ae67f7443e/lib/ansible/modules/cloud/misc/helm.py | 16:35 |
| inc0 | 3. write full ansible orch for deployment | 16:35 |
| flaper87 | that's the ansible helm module | 16:35 |
| EmilienM | flaper87: thanks | 16:35 |
| kfox1111 | flaper87: very nice. thanks. :) | 16:35 |
| inc0 | 4*. put it all into a container and run ansible from inside pod;) | 16:35 |
| sdake | slagle naturally you could use each of these building blocks in the playbook individually as a result - that is how kolla-kubernetes is structured | 16:36 |
| kfox1111 | for reference, here's the helm template plugin: https://github.com/technosophos/helm-template | 16:37 |
| slagle | sdake: when you say "building blocks", is it all of these? https://github.com/openstack/kolla-kubernetes/tree/master/helm/microservice | 16:37 |
| sdake | those are them slagle | 16:38 |
| slagle | thanks, just wanted to make sure i was looking in the right place | 16:38 |
| flaper87 | inc0: so I think 3 we can definitely collaborate on. Under what number do you put config management? | 16:38 |
| kfox1111 | slagle: yeah. | 16:38 |
| inc0 | conf mgmt is part of 3 as far as I'm concerned | 16:38 |
| kfox1111 | flaper87: probably very similar to orchestration. | 16:38 |
| kfox1111 | yeah. | 16:38 |
| flaper87 | ok | 16:39 |
| inc0 | part of orchestration | 16:39 |
| flaper87 | just wanted to make sure | 16:39 |
| flaper87 | so we can basically break #3 down into different areas | 16:39 |
| sdake | slagle we also played with composition of these building blocks using helm (the helm/services) directory - I feel this has been sort of a failure of our understanding of hem initially - in that helm is not an orchestration system | 16:39 |
| flaper87 | but yeah | 16:39 |
| flaper87 | I agree | 16:39 |
| kfox1111 | it could be split out if we think it has some different qualities. | 16:39 |
| EmilienM | flaper87: yes, breakdown | 16:39 |
| inc0 | thing is, I'm not sure if we can write orchestration for 2 different resource definitions | 16:39 |
| inc0 | and it won't be ideal | 16:39 |
| EmilienM | I wish we could write some ansible roles for config management that would be re-usable outside kolla/tripleo too | 16:39 |
| inc0 | so I'd say we should try to use common resource definitions | 16:39 |
| EmilienM | if we just write a stupid role that generate a file from a list of parameters | 16:40 |
| kfox1111 | EmilienM: big +1. | 16:40 |
| inc0 | ansible module would be nice | 16:40 |
| *** jamesbenson has joined #openstack-meeting-4 | 16:40 | |
| flaper87 | inc0: when you say common resource edefinition, you're referring to using gotl | 16:40 |
| EmilienM | nothing more, so everyone can use it and do what they like before / after, as long as they use this role | 16:40 |
| kfox1111 | kolla-kubernetes has been writen with config generation completely seperate so that whatever the right tool for config gen was, it can be used. | 16:40 |
| inc0 | I'm referring to yamls that would be rendered by gotpl | 16:40 |
| kfox1111 | having a generic ansible genconfig woudl be sweet. :) | 16:40 |
| inc0 | templates in whatever language are just a means to get these yamls | 16:41 |
| sdake | jinja2 / gotpl are analogs | 16:41 |
| EmilienM | I'm pretty sure openstack-ansible would also be interested by using this role sometimes | 16:41 |
| inc0 | yamls should be identical for orch to work properly | 16:41 |
| inc0 | and if we have 2 codebases for them that will be hard to maintain | 16:41 |
| kfox1111 | EmilienM: yeah. could share all that between all the projects. :) | 16:41 |
| inc0 | EmilienM: ofc | 16:41 |
| sdake | the cost to tripleo to using gotpl is in some way converting gotpl into a format suitable for consumption by whatever tooling you want to use (which sounds like jinja2) | 16:42 |
| kfox1111 | or maintaining 2 languages. | 16:42 |
| sdake | the alternative is to write all those buliding blocks from scratch - which can be done - which is painful | 16:42 |
| kfox1111 | jinja2 for config, gotl for k8s objects. | 16:42 |
| kfox1111 | sdake: yeah. | 16:43 |
| flaper87 | technically, we could pass yaml files to ansible-kubernetes modules. That said, the resources topic is one that we should def figure out | 16:43 |
| *** cshen_ has joined #openstack-meeting-4 | 16:43 | |
| inc0 | yeah, once we have yamls, we're good | 16:43 |
| inc0 | really orch is about having yamls and running them in correct order with wait conditions | 16:43 |
| inc0 | + config mgmt | 16:43 |
| sdake | inc0+ | 16:43 |
| inc0 | however getting these yamls correctly is not a trivial task | 16:44 |
| sdake | sorting out the order for the building blocks is no easy task - although it has already been prototyped | 16:44 |
| EmilienM | there is one important aspect we have to think about is tripleo is interested to simplify operator's life and reduce the number of technologies (in some sort) used to deploy OpenStack - I don't think we want to add too much langages in the stack, at least not more than we have now | 16:44 |
| sdake | sorting out the kubernetes object is an order of magnitude more difficult | 16:44 |
| flaper87 | which is why I like the idea of just using ansible-kubernetes module | 16:44 |
| sdake | object/objects | 16:45 |
| inc0 | yeah I think so too flaper87 | 16:45 |
| EmilienM | jinja2 is already part of tripleo and gotl is somehow required for k8s world, so I guess that would be fine - plus ansible which is also something we want | 16:45 |
| flaper87 | EmilienM: gotl is not really required for k8s | 16:45 |
| inc0 | well, I still have some issues with ansible k8s module, or rather that ansible is not great in templating to variable (can do it but there are caveats) | 16:45 |
| flaper87 | EmilienM: it's required by helm | 16:45 |
| slagle | flaper87: do you know if it's possible to get the k8s yaml as output from the ansible-kubernetes modules? | 16:45 |
| flaper87 | slagle: I was literally looking into that | 16:46 |
| flaper87 | :P | 16:46 |
| EmilienM | flaper87: oh ok. So yeah, we would have one new layer for our operators | 16:46 |
| flaper87 | slagle: if it isn't, I'm sure it can be added | 16:46 |
| inc0 | slagle: ansible-kubernetes takes yamls as input | 16:46 |
| kfox1111 | kubectl get pod <thingy> -o yaml | 16:46 |
| flaper87 | which was going to be my next comment | 16:46 |
| inc0 | output is kubectl create | echo templated-yaml | 16:46 |
| inc0 | or other way around rather | 16:46 |
| flaper87 | if we get ansible-kubernetes to output yaml files, it means that we can focus on orch pieces | 16:46 |
| kfox1111 | output yamls from where? | 16:46 |
| sdake | what is ansible-kubernetes? | 16:47 |
| inc0 | if we get ansible-helm to output yamls then we can reuse whole of kolla-k8s;) | 16:47 |
| slagle | inc0: yea, i wasn't sure if the yaml input was the same format expected by kubectl | 16:47 |
| flaper87 | sdake: ansible's module to talk to kubernetes. | 16:47 |
| flaper87 | sdake: https://github.com/ansible/ansible-kubernetes-modules | 16:47 |
| sdake | oh right thanks | 16:47 |
| flaper87 | inc0: slagle the output is the same. It's a k8s yaml file | 16:47 |
| kfox1111 | ansible-kubernetes as I understand it is more of a, here's a yaml, load it into k8s? | 16:47 |
| inc0 | yeah, source of where it comes from is the question here I think | 16:48 |
| kfox1111 | something needs to generate the yaml though to feed in. | 16:48 |
| flaper87 | kfox1111: it's more like: Use ansible tasks to create k8s resources | 16:48 |
| flaper87 | but it can also take yamls as input | 16:48 |
| kfox1111 | thats what kolla-kubernetes is about. | 16:48 |
| flaper87 | That said, we could have the task output the yaml for us | 16:48 |
| kfox1111 | so, something like helm template kolla/nova-api-deployment > yamlfile. | 16:48 |
| flaper87 | register that yaml into a variable or something | 16:48 |
| inc0 | so again, one thing I'd not like to see personally is 2 different sets of templates with same orch layer | 16:48 |
| flaper87 | kfox1111: exactly | 16:49 |
| kfox1111 | ansible-kubernetes load yamlfile ? | 16:49 |
| inc0 | since 2 different sets of templates is *a lot of* duplicated work which has to be kept in sync because of common orch layer | 16:49 |
| kfox1111 | yeah. I thin kthat would work. | 16:49 |
| mwhahaha | that's kinda the problem with templates is that trying to capture all use cases in templates is really hard | 16:49 |
| sdake | mwhahaha not if decomposed properly | 16:49 |
| mwhahaha | it'd be better to define the datastructures and reuse generic ones rather than templates | 16:49 |
| inc0 | but our use cases are largely the same | 16:49 |
| kfox1111 | mwhahaha: we do some of that today too. | 16:50 |
| kfox1111 | mwhahaha: see kolla-kubernetes/helm/kolla-common/templates/* | 16:50 |
| mwhahaha | i'm not saying it can't be done, i'm just saying that it needs to be kept in mind | 16:50 |
| flaper87 | ok, we have like 10mins left | 16:50 |
| inc0 | at the end of the day both of us wants openstack running on top of k8s | 16:50 |
| kfox1111 | we share a lot of code between the microservices that way. | 16:50 |
| mwhahaha | and templates generally is where you're problem is because there's always a bunch of edge cases that only gets worse the more template syou add | 16:50 |
| inc0 | yeah we won't make any decisions today | 16:50 |
| flaper87 | inc0: I would like to dive a bit more into what scenarios could happen if we end up with 2 set of yamls | 16:50 |
| sdake | flaper87 an analog would be two sets of dockerfile descriptors | 16:51 |
| flaper87 | inc0: wasn't planning to make any decision today :P but rather getting the conversation framed and started | 16:51 |
| sdake | flaper87 except fastly more complex | 16:51 |
| flaper87 | sdake: gotcha | 16:51 |
| kfox1111 | flaper87: same senerio with any split code base? bugs get fixed in one and not in the other, etc. | 16:51 |
| inc0 | sure, and I'd like to make sure that we examine all possibilities to have single set of templates | 16:51 |
| sdake | fastly/vastly | 16:51 |
| EmilienM | we have 10 mins like flaper87 said - let's take some actions from now | 16:51 |
| inc0 | again, trust me in that, getting these resource devinitions right is not trivial | 16:51 |
| *** Manuel_112 has joined #openstack-meeting-4 | 16:51 | |
| kfox1111 | k. | 16:52 |
| inc0 | took us months to get it right | 16:52 |
| sdake | more like 14 months inc0 :) | 16:52 |
| *** abhishekk_ has quit IRC | 16:52 | |
| inc0 | right | 16:52 |
| *** david-lyle has joined #openstack-meeting-4 | 16:52 | |
| EmilienM | what can we do "tomorrow" to start this effort? | 16:52 |
| flaper87 | Besides summarizing the meeting and trying to move the conversation forward on the mailing list, I would like to explore the idea of collaborating on the orchestration aspects of the deployment. | 16:52 |
| *** hoppalm has quit IRC | 16:52 | |
| sdake | EmilienM personallly I think a good first step is for the tripeo cats to leran a little bit about what orchestration looks like to them with the templates in kk | 16:53 |
| flaper87 | I would also like to explore a bit more on what it would mean to have a common set of resources from a tripleo perspective | 16:53 |
| *** cshen_ has quit IRC | 16:53 | |
| inc0 | EmilienM: I'd like to have proper PTG meeting for technical planning, so we need to have direction agreed upon by then | 16:53 |
| kfox1111 | EmilienM: maybe a prototype of the helm template plugin -> ansible-kubernetes would be good to see if the idea has wings? | 16:53 |
| flaper87 | sdake: beat me by 10s | 16:53 |
| flaper87 | inc0: I don't want to wait until the PTG, fwiw. I'd like to get to the PTG with a more formal plan | 16:53 |
| kfox1111 | inc0: +1 to ptg meeting. though thats not 'tomorrow' | 16:54 |
| inc0 | jascott1 and me can handle prototype (he knows helm, I know ansible;)) | 16:54 |
| flaper87 | unless that's what you meant and I just misunderstood you | 16:54 |
| flaper87 | in which case, I'm sorry | 16:54 |
| EmilienM | yeah we have ~1 month and half - in the meantime we can do some work | 16:54 |
| dprince | inc0: EmilienM can we try to make sure the PTG sessions for Kolla and TripleO don't overlap? | 16:54 |
| inc0 | flaper87: yeah what I was thingking about is PTG = actual implementation plans | 16:54 |
| EmilienM | dprince: yes, I'll make sure of than, with inc0 | 16:54 |
| EmilienM | s/than/that | 16:54 |
| flaper87 | crazy (not?) question: Would it be possible to generate k-k templates without helm? As in, just gotl | 16:55 |
| inc0 | we have 3 days (incl Friday) | 16:55 |
| sdake | i'd encourage folks to have a look at https://review.openstack.org/#/c/473588/ | 16:55 |
| * flaper87 is just trying to understand kk boundaries better | 16:55 | |
| inc0 | flaper87: yeah, if we write tooling | 16:55 |
| sdake | this represents one model of orchestration (using ansible) that explores the consumption of helm directly | 16:55 |
| kfox1111 | flaper87: the templates are just gotl. just something needs to render it. | 16:55 |
| inc0 | that's what I was trying to say;) | 16:55 |
| inc0 | it's *just* templating renderer;) | 16:55 |
| flaper87 | kfox1111: right, some gotl cli I was thinking | 16:55 |
| sdake | simple to replace all the helm calls with the helm template calls | 16:55 |
| kfox1111 | :) | 16:55 |
| flaper87 | asking because of the possiblity to collaborate on the orc parts | 16:56 |
| inc0 | flaper87: thing is, helm template is exactly cli you want | 16:56 |
| kfox1111 | flaper87: yeah. which I think thats all the helm template plugin does. | 16:56 |
| kfox1111 | take in gotl stuff, spit out yaml. :) | 16:56 |
| inc0 | it's helm only by name | 16:56 |
| *** hoppalm has joined #openstack-meeting-4 | 16:56 | |
| flaper87 | gotcha | 16:56 |
| kfox1111 | I think you can even run it without helm. | 16:56 |
| flaper87 | kfox1111: that was my question :P | 16:57 |
| kfox1111 | all helm plugins do are chain the cli call. | 16:57 |
| inc0 | gotpl as language is the barrier here | 16:57 |
| EmilienM | yeah, you use helm as a wrapper right? | 16:57 |
| *** Manuel_112 has quit IRC | 16:57 | |
| sdake | EmilienM right - helm is a wrapper around kubectl | 16:57 |
| kfox1111 | so helm <x> just execs ~/.helm/plugins/bin/<x> | 16:57 |
| flaper87 | ok | 16:57 |
| kfox1111 | helm is a couple of thigns. | 16:57 |
| flaper87 | I'll work on my action items as soon as possible and get back to y'all | 16:57 |
| EmilienM | so if we wanted to re-use your templates we would need a convertor like sdake proposes to investigate | 16:57 |
| kfox1111 | 1. a gotl parser. | 16:57 |
| flaper87 | I'll probably start new threads (or just follow up on that one) to discuss further some of these topics | 16:58 |
| inc0 | or just use gotpl, it's not *that* bad | 16:58 |
| kfox1111 | 2. a package fetcher/searcher. (yum search, yum list) | 16:58 |
| inc0 | ok we're at the end of times | 16:58 |
| *** salmankhan has quit IRC | 16:58 | |
| sdake | check out that review - learn how it works :) | 16:58 |
| inc0 | or at least this meeting time;) | 16:58 |
| flaper87 | thank y'all for allowing us to "steal" your meeting | 16:58 |
| flaper87 | I really appreciate your time | 16:59 |
| shardy | thanks for the dicussion everyone! | 16:59 |
| EmilienM | thanks yeah | 16:59 |
| flaper87 | your patience and for walking us through the project | 16:59 |
| flaper87 | looking forward to collaborate more and as much as possible | 16:59 |
| EmilienM | #action inc0 & EmilienM to work together on ptg scheduling | 16:59 |
| inc0 | thank you all, let's kick off ML thread and get some cool prototypes going | 16:59 |
| inc0 | right | 16:59 |
| inc0 | thank you all! | 16:59 |
| flaper87 | inc0: that's on my list | 16:59 |
| inc0 | #endmeeting kolla | 16:59 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:59 | |
| openstack | Meeting ended Wed Jul 19 16:59:39 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:59 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-07-19-16.00.html | 16:59 |
| Duonghq | Cya | 16:59 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-07-19-16.00.txt | 16:59 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-07-19-16.00.log.html | 16:59 |
| *** jascott1 has left #openstack-meeting-4 | 17:00 | |
| *** mwhahaha has left #openstack-meeting-4 | 17:00 | |
| *** salmankhan has joined #openstack-meeting-4 | 17:00 | |
| *** shardy has left #openstack-meeting-4 | 17:01 | |
| *** egonzalez has quit IRC | 17:02 | |
| *** Daidv has quit IRC | 17:03 | |
| *** Duonghq has quit IRC | 17:04 | |
| *** vhosakot has left #openstack-meeting-4 | 17:14 | |
| *** serlex has quit IRC | 17:16 | |
| *** jamesbenson has quit IRC | 17:18 | |
| *** sjmc7 has left #openstack-meeting-4 | 17:19 | |
| *** harlowja has joined #openstack-meeting-4 | 17:25 | |
| *** harlowja has quit IRC | 17:25 | |
| *** harlowja has joined #openstack-meeting-4 | 17:26 | |
| *** bobh has quit IRC | 17:29 | |
| *** bobh has joined #openstack-meeting-4 | 17:31 | |
| *** yfauser has quit IRC | 17:31 | |
| *** yfauser has joined #openstack-meeting-4 | 17:32 | |
| *** yfauser has quit IRC | 17:37 | |
| *** dprince has quit IRC | 17:37 | |
| *** ralonsoh has quit IRC | 17:42 | |
| *** deep-book-gk_ has joined #openstack-meeting-4 | 17:45 | |
| *** jamesbenson has joined #openstack-meeting-4 | 17:46 | |
| *** deep-book-gk_ has quit IRC | 17:46 | |
| *** jamesbenson has quit IRC | 17:50 | |
| *** jamesbenson has joined #openstack-meeting-4 | 17:52 | |
| *** aavraham has joined #openstack-meeting-4 | 17:52 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 17:53 | |
| *** Rockyg has quit IRC | 17:54 | |
| *** yamahata has quit IRC | 17:54 | |
| *** iyamahat has quit IRC | 17:54 | |
| *** trinaths has left #openstack-meeting-4 | 17:56 | |
| *** yfauser has joined #openstack-meeting-4 | 17:57 | |
| *** Manuel_112 has quit IRC | 17:59 | |
| *** yfauser has quit IRC | 17:59 | |
| *** yfauser has joined #openstack-meeting-4 | 18:00 | |
| *** yfauser has quit IRC | 18:04 | |
| *** baoli_ has quit IRC | 18:11 | |
| *** iyamahat has joined #openstack-meeting-4 | 18:12 | |
| *** baoli has joined #openstack-meeting-4 | 18:15 | |
| *** u_nuSLASHkm8 has joined #openstack-meeting-4 | 18:19 | |
| *** u_nuSLASHkm8 has left #openstack-meeting-4 | 18:20 | |
| *** Julien-zte has quit IRC | 18:20 | |
| *** Julien-zte has joined #openstack-meeting-4 | 18:23 | |
| *** dprince has joined #openstack-meeting-4 | 18:23 | |
| *** bobh has quit IRC | 18:24 | |
| *** aavraham has quit IRC | 18:26 | |
| *** dprince has quit IRC | 18:26 | |
| *** baoli has quit IRC | 18:27 | |
| *** yamahata has joined #openstack-meeting-4 | 18:31 | |
| *** hoppalm has quit IRC | 18:38 | |
| *** bobh has joined #openstack-meeting-4 | 18:38 | |
| *** Sukhdev has quit IRC | 18:39 | |
| *** hoppalm has joined #openstack-meeting-4 | 18:45 | |
| *** vds has quit IRC | 18:48 | |
| *** lyan has joined #openstack-meeting-4 | 18:50 | |
| *** hoppalm has quit IRC | 18:50 | |
| *** vds has joined #openstack-meeting-4 | 18:52 | |
| *** hoppalm has joined #openstack-meeting-4 | 18:52 | |
| *** hoppalm has quit IRC | 18:53 | |
| *** hoppalm has joined #openstack-meeting-4 | 18:53 | |
| *** salmankhan has quit IRC | 18:54 | |
| *** hoppalm_ has joined #openstack-meeting-4 | 18:55 | |
| *** hoppalm has quit IRC | 18:56 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 18:56 | |
| *** adisky__ has quit IRC | 18:58 | |
| *** yfauser has joined #openstack-meeting-4 | 19:00 | |
| *** Manuel_112 has quit IRC | 19:01 | |
| *** yfauser has quit IRC | 19:04 | |
| *** kkxue_ has joined #openstack-meeting-4 | 19:05 | |
| *** hoppalm_ has quit IRC | 19:07 | |
| *** yfauser has joined #openstack-meeting-4 | 19:08 | |
| *** kkxue has quit IRC | 19:08 | |
| *** vishnoianil has joined #openstack-meeting-4 | 19:09 | |
| *** hoppalm has joined #openstack-meeting-4 | 19:12 | |
| *** yfauser has quit IRC | 19:12 | |
| *** tinyurl_comSLASH has joined #openstack-meeting-4 | 19:20 | |
| *** tinyurl_comSLASH has left #openstack-meeting-4 | 19:21 | |
| *** kbyrne has quit IRC | 19:22 | |
| *** kbyrne has joined #openstack-meeting-4 | 19:25 | |
| *** tinyurl_comSLASH has joined #openstack-meeting-4 | 19:31 | |
| *** makowals has quit IRC | 19:32 | |
| *** tinyurl_comSLASH has left #openstack-meeting-4 | 19:32 | |
| *** cshen_ has joined #openstack-meeting-4 | 19:44 | |
| *** coolsvap has quit IRC | 19:51 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 19:57 | |
| *** anilvenkata has quit IRC | 20:06 | |
| *** cathrichardson has joined #openstack-meeting-4 | 20:07 | |
| *** thorst_ has quit IRC | 20:07 | |
| *** Manuel_112 has quit IRC | 20:07 | |
| *** yfauser has joined #openstack-meeting-4 | 20:08 | |
| *** thorst has joined #openstack-meeting-4 | 20:10 | |
| *** rwallner has quit IRC | 20:14 | |
| *** thorst has quit IRC | 20:14 | |
| *** makowals has joined #openstack-meeting-4 | 20:16 | |
| *** rwallner has joined #openstack-meeting-4 | 20:18 | |
| *** Sukhdev_ has quit IRC | 20:19 | |
| *** Sukhdev has joined #openstack-meeting-4 | 20:20 | |
| *** rwallner has quit IRC | 20:22 | |
| *** lyan has quit IRC | 20:23 | |
| *** vds has quit IRC | 20:23 | |
| *** lyan has joined #openstack-meeting-4 | 20:24 | |
| *** cshen_ has quit IRC | 20:52 | |
| *** yfauser_ has joined #openstack-meeting-4 | 20:54 | |
| *** yfauser_ has quit IRC | 20:57 | |
| *** yfauser has quit IRC | 20:58 | |
| *** yfauser has joined #openstack-meeting-4 | 21:00 | |
| *** kylek3h has quit IRC | 21:02 | |
| *** yfauser has quit IRC | 21:03 | |
| *** woodard_ has joined #openstack-meeting-4 | 21:05 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 21:05 | |
| *** anilvenkata has joined #openstack-meeting-4 | 21:05 | |
| *** Manuel_112 has quit IRC | 21:06 | |
| *** yfauser has joined #openstack-meeting-4 | 21:07 | |
| *** yfauser has quit IRC | 21:07 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 21:08 | |
| *** woodard has quit IRC | 21:08 | |
| *** Manuel_112 has quit IRC | 21:08 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 21:08 | |
| *** woodard_ has quit IRC | 21:09 | |
| *** julim has quit IRC | 21:10 | |
| *** galstrom is now known as galstrom_zzz | 21:10 | |
| *** anilvenkata has quit IRC | 21:11 | |
| *** Manuel_112 has quit IRC | 21:11 | |
| *** sambetts is now known as sambetts|afk | 21:13 | |
| *** thorst has joined #openstack-meeting-4 | 21:14 | |
| *** jamesbenson has quit IRC | 21:17 | |
| *** thorst has quit IRC | 21:19 | |
| *** makowals has quit IRC | 21:22 | |
| *** thorst has joined #openstack-meeting-4 | 21:25 | |
| *** vds has joined #openstack-meeting-4 | 21:26 | |
| *** makowals has joined #openstack-meeting-4 | 21:27 | |
| *** bobh has quit IRC | 21:36 | |
| *** makowals has quit IRC | 21:40 | |
| *** Sukhdev has quit IRC | 21:42 | |
| *** Sukhdev has joined #openstack-meeting-4 | 21:42 | |
| *** baoli has joined #openstack-meeting-4 | 21:47 | |
| *** baoli has quit IRC | 21:48 | |
| *** marst_ has joined #openstack-meeting-4 | 21:48 | |
| *** baoli has joined #openstack-meeting-4 | 21:50 | |
| *** marst has quit IRC | 21:52 | |
| *** galstrom_zzz is now known as galstrom | 21:54 | |
| *** rwallner has joined #openstack-meeting-4 | 21:54 | |
| *** rwallner has quit IRC | 21:55 | |
| *** rwallner has joined #openstack-meeting-4 | 21:55 | |
| *** marst_ has quit IRC | 21:57 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 22:09 | |
| *** woodard has joined #openstack-meeting-4 | 22:11 | |
| *** woodard has joined #openstack-meeting-4 | 22:11 | |
| *** Manuel_112 has quit IRC | 22:14 | |
| *** jamesbenson has joined #openstack-meeting-4 | 22:17 | |
| *** jamesbenson has quit IRC | 22:22 | |
| *** baoli has quit IRC | 22:26 | |
| *** makowals has joined #openstack-meeting-4 | 22:28 | |
| *** julim has joined #openstack-meeting-4 | 22:31 | |
| *** sdague has quit IRC | 22:33 | |
| *** baoli has joined #openstack-meeting-4 | 22:36 | |
| *** galstrom is now known as galstrom_zzz | 22:41 | |
| *** thorst has quit IRC | 22:56 | |
| *** vishwana_ has quit IRC | 22:58 | |
| *** vishwanathj has joined #openstack-meeting-4 | 22:58 | |
| *** rwallner has quit IRC | 23:04 | |
| *** yamamoto has joined #openstack-meeting-4 | 23:04 | |
| *** lyan has quit IRC | 23:04 | |
| *** Manuel_112 has joined #openstack-meeting-4 | 23:11 | |
| *** sbezverk has quit IRC | 23:15 | |
| *** Manuel_112 has quit IRC | 23:15 | |
| *** yamamoto has quit IRC | 23:18 | |
| *** pmesserli has quit IRC | 23:27 | |
| *** hongbin has quit IRC | 23:30 | |
| *** chyka has quit IRC | 23:37 | |
| *** makowals has quit IRC | 23:51 | |
| *** jamesbenson has joined #openstack-meeting-4 | 23:54 | |
| *** jamesbenson has quit IRC | 23:58 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!