14:05:29 <tobberydberg> #startmeeting publiccloud_wg
14:05:30 <openstack> Meeting started Thu Dec 20 14:05:29 2018 UTC and is due to finish in 60 minutes.  The chair is tobberydberg. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:05:31 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:05:34 <openstack> The meeting name has been set to 'publiccloud_wg'
14:05:50 <tobberydberg> Last meeting for the year
14:06:17 <tobberydberg> The very open agenda at https://etherpad.openstack.org/p/publiccloud-wg
14:06:38 <tobberydberg> Feel free to ad your selves and add topics there
14:07:06 <mriedem> i've got 2 things i think
14:07:36 <tobberydberg> Please add them!
14:08:05 <mriedem> i only see dec 20 2017
14:08:07 <tobberydberg> #topic 1. Planning 2019
14:08:32 <mriedem> there we go :)
14:08:51 <tobberydberg> hehe .. .sorry ... my bad in a hurry yesterday =)
14:10:15 <tobberydberg> So, I've adding som comments in the etherpad as we go here as well
14:10:31 <tobberydberg> zhipeng  - feel free to comment on that as well
14:10:59 <zhipeng> No problem :)
14:12:07 <tobberydberg> thanks for adding that link mriedem ... great that adriant is onboard there
14:12:20 <mriedem> np
14:14:23 <tobberydberg> So the plan in general is to do a little bit of a recheck/restart of PP, continue the "missing features list" - with focus on the "2 selected items" (one that hopefully will make it as community goal)
14:15:46 <zhipeng> Do we have the tracking tool ready now ?
14:16:13 <tobberydberg> Maybe take on the ownership about the vendor profiles for the os-client
14:16:36 <tobberydberg> tracking tool of people in the PP?
14:16:47 <mriedem> what is the PP?
14:16:54 <tobberydberg> "Passport program"
14:16:57 <mriedem> ah
14:17:38 <tobberydberg> or what were you thinking about there zhipeng ?
14:18:27 <zhipeng> Tracking for the missing feature progress
14:18:40 <zhipeng> Melvin mentioned a website ?
14:20:16 <tobberydberg> aha
14:20:19 <tobberydberg> sorry
14:20:41 <tobberydberg> No, feedback was to try to not bring on another tool
14:21:01 <zhipeng> So we should stick with uc storyboard ?
14:21:16 <tobberydberg> "Operators most important issues list"
14:21:25 <tobberydberg> added that to the list under missing features
14:21:53 <tobberydberg> lets figure it out ... but yes that was one of the ideas
14:23:24 <zhipeng> Okey, next question is shall we push release team to add a new label similar to "release highlight" to reflect the progress of certain goal ?
14:24:15 <zhipeng> "requirement fulfillment", or some other wording
14:24:55 <mriedem> add a new label where?
14:25:11 <mriedem> like here? https://releases.openstack.org/rocky/highlights.html
14:25:41 <mriedem> that is auto-generated from the deliverables in the releases repo, of which the public cloud sig doesn't have deliverables - i'm sure something could be added to build those docs though
14:26:12 <mriedem> there is also https://governance.openstack.org/tc/goals/ but i'm not sure that's a good fit
14:26:19 <zhipeng> Yeah along the lines of that
14:26:21 <tobberydberg> Do you mean like more officially state "how well Team X delivered upon the goal Y"?
14:26:28 <mriedem> ^ requires accepting a community wide goal first
14:26:35 <zhipeng> Yep :)
14:26:38 <tobberydberg> yup
14:26:55 <mriedem> personally i'd like to see completion % on community wide goals as well
14:27:01 <mriedem> not sure if dhellmann has something for that in the past
14:27:14 <mriedem> e.g. some projects (glance) didn't complete the uwsgi goal
14:27:23 <zhipeng> That is not mutually exclusive :)
14:27:47 <tobberydberg> Think we are on the right track regarding release goals and highlights - 1 operator focused and one "code" focused
14:28:23 <mriedem> so maybe an action item is go to the tc to figure out how to communicate community wide goal completion?
14:28:40 <tobberydberg> Could be good with a more granular view of that as well, but harder with some goals
14:28:54 <zhipeng> I know that was built from deliverable directory, I think we need to add a new field similar to highlight
14:29:12 <mriedem> zhipeng: specifically for community wide goals?
14:29:20 <zhipeng> Yes
14:29:32 <zhipeng> Plus maybe other goals
14:29:39 <zhipeng> It is up to the teams
14:29:46 <mriedem> ok i'll bring this up in the tc office hours which starts in 30 minutes
14:29:52 <zhipeng> And we could consult tc on that
14:29:57 <tobberydberg> zhipeng - could that be an action for you to discuss with TC?
14:30:21 <mriedem> i can float the ideas in 30 min
14:30:21 <zhipeng> Yes it could be lol
14:30:25 <mriedem> since it's late for howard
14:30:36 <zhipeng> Thx Matt
14:30:47 <tobberydberg> +1
14:30:47 <zhipeng> Barely have my eyes open lol
14:30:58 <mriedem> too many hamburgers
14:30:59 <mriedem> so sleepy
14:31:20 <zhipeng> XD
14:31:42 <tobberydberg> hehehe
14:32:07 <tobberydberg> it's the small christmas tree that is getting to you
14:33:34 <tobberydberg> Any thoughts about getting more people to attend meetings?
14:34:07 <mriedem> so,
14:34:22 <mriedem> honestly i wouldn't have even thought to attend if you hadn't sent out a reminder of this upcoming meeting,
14:34:24 <mriedem> so i think that's good
14:34:25 <tobberydberg> Which would be better for questions like yours mriedem as well ... bad when I'm the only one replying
14:34:33 <mriedem> if you have some agenda items beforehand that's even better
14:35:00 <mriedem> now i've got it in my calendar so i can at least attend this one if i'm at the computer in time
14:35:05 <mriedem> (8am here)
14:36:13 <tobberydberg> Yea, trying to do both ... sometimes better thatn other =) But thanks - will have that in mind!
14:36:19 <zhipeng> +1 on prep agenda beforehand
14:36:29 <tobberydberg> Yea, and to late for APAC
14:37:05 <tobberydberg> thats why we have the very early meeting (for me)  next week :-)
14:37:15 <mriedem> yup
14:37:35 <tobberydberg> Will do a shout out to the mailing list as well
14:37:47 <tobberydberg> BTW - Reminder: OpenStack summit call for papers deadline is Jan 23
14:37:56 <tobberydberg> That chocked med :-)
14:38:03 <tobberydberg> *me
14:38:16 <tobberydberg> wasn't prepared for that yet =)
14:39:02 <mriedem> no one is
14:39:15 * tobberydberg reading your email thread mriedem
14:44:25 <tobberydberg> appreciated to have that on "per vm basis"
14:45:02 <tobberydberg> Brings more flexibility and also will be easier to do automated operational work
14:45:31 <mriedem> ok if you're in favor including the pre-live migration safety check please reply to the thread
14:45:42 <mriedem> i kind of need operators speaking up to get through the deadlock here
14:46:50 <tobberydberg> yes, in favor of that ... cna add that
14:47:18 <mriedem> thanks
14:48:06 <tobberydberg> (and thats why we need more ops to be here as well)
14:48:22 <mriedem> as for pre-paid instances, it sounds like that could be generally beneficial
14:48:46 <mriedem> *granular locks would be generally beneficial - which would be a way to implement pre-paid instances
14:49:27 <tobberydberg> Yes. it will for sure bring more flexibility in the offerings to customers
14:49:32 <tobberydberg> "mature customers"
14:49:53 <mriedem> ok so i'll follow up with a ML thread about that to get wider feedback
14:49:54 <mriedem> thanks
14:50:02 <tobberydberg> the number of those today are pretty low, but will of course grown year by year
14:50:42 <tobberydberg> Definitely makes openstack a better "product offering"
14:52:06 <tobberydberg> So, 9 minutes left... Something else?
14:52:27 <mriedem> nope, i have to run to another meeting
14:52:57 <tobberydberg> thanks for joining mriedem and happy holidays
14:53:07 <mriedem> yup you too
14:53:08 <mriedem> o/
14:53:22 <mriedem> enjoy the lutefisk and lefse
14:53:24 <mriedem> :)
14:53:30 <mriedem> my mom's side is swedish
14:53:38 <tobberydberg> hahaha
14:53:46 <zhipeng> Haha
14:54:07 <tobberydberg> xool ... didn't know! Will have a lot of "sill" (herring) at least
14:54:46 <tobberydberg> zhipeng - Christmas break upcoming 2 weeks or should we have a meeting?
14:55:08 <zhipeng> I think we should have a break
14:55:24 <zhipeng> Reconvene after new year's week
14:55:31 <tobberydberg> next meeting 3rd or 10th?
14:56:04 <zhipeng> 10th ?
14:56:10 <tobberydberg> :+1
14:56:35 <zhipeng> We could ask Allison and other foundation folks to join as well
14:56:59 <tobberydberg> Sure ... maybe the 17th is better for that? (time-wise)
14:57:38 <zhipeng> Well anytime they see fit :)
14:57:43 <tobberydberg> heheh
14:58:28 <tobberydberg> Thanks for today zhipeng! Happy holidays to you and talk to you next year ;-)
14:58:43 <tobberydberg> #endmeeting