Thursday, 2018-12-20

*** jamesmcarthur has joined #openstack-publiccloud00:53
*** jamesmcarthur has quit IRC00:58
*** jamesmcarthur has joined #openstack-publiccloud01:17
*** jamesmcarthur has quit IRC01:22
*** trident has quit IRC01:36
*** jamesmcarthur has joined #openstack-publiccloud02:15
*** jamesmcarthur has quit IRC02:17
*** jamesmcarthur has joined #openstack-publiccloud02:17
*** trident has joined #openstack-publiccloud02:58
*** jamesmcarthur has quit IRC03:08
*** jamesmcarthur has joined #openstack-publiccloud03:34
*** jamesmcarthur has quit IRC04:29
*** jamesmcarthur has joined #openstack-publiccloud06:30
*** mgagne has quit IRC06:33
*** jamesmcarthur has quit IRC06:34
*** mgagne has joined #openstack-publiccloud06:40
*** jamesmcarthur has joined #openstack-publiccloud07:31
*** jamesmcarthur has quit IRC07:35
*** mriedem has joined #openstack-publiccloud13:39
tobberydbergo/14:00
zhipengo/14:01
mriedemo/14:01
tobberydbergHi folks!14:02
tobberydbergNice to see you here14:02
zhipengHow's Xmas prep going ? :)14:03
tobberydbergJust leave it at "begind schedule" ;-)14:04
tobberydbergHow about yourself?14:04
zhipengA very small tree has arrived :P14:04
tobberydberghehe14:05
tobberydberg#startmeeting publiccloud_wg14:05
openstackMeeting 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:05
*** openstack changes topic to " (Meeting topic: publiccloud_wg)"14:05
openstackThe meeting name has been set to 'publiccloud_wg'14:05
tobberydbergLast meeting for the year14:05
tobberydbergThe very open agenda at https://etherpad.openstack.org/p/publiccloud-wg14:06
tobberydbergFeel free to ad your selves and add topics there14:06
mriedemi've got 2 things i think14:07
tobberydbergPlease add them!14:07
mriedemi only see dec 20 201714:08
tobberydberg#topic 1. Planning 201914:08
*** openstack changes topic to "1. Planning 2019 (Meeting topic: publiccloud_wg)"14:08
mriedemthere we go :)14:08
tobberydberghehe .. .sorry ... my bad in a hurry yesterday =)14:08
tobberydbergSo, I've adding som comments in the etherpad as we go here as well14:10
tobberydbergzhipeng  - feel free to comment on that as well14:10
zhipengNo problem :)14:10
tobberydbergthanks for adding that link mriedem ... great that adriant is onboard there14:12
mriedemnp14:12
tobberydbergSo 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:14
zhipengDo we have the tracking tool ready now ?14:15
tobberydbergMaybe take on the ownership about the vendor profiles for the os-client14:16
tobberydbergtracking tool of people in the PP?14:16
mriedemwhat is the PP?14:16
tobberydberg"Passport program"14:16
mriedemah14:16
tobberydbergor what were you thinking about there zhipeng ?14:17
zhipengTracking for the missing feature progress14:18
zhipengMelvin mentioned a website ?14:18
tobberydbergaha14:20
tobberydbergsorry14:20
tobberydbergNo, feedback was to try to not bring on another tool14:20
zhipengSo we should stick with uc storyboard ?14:21
tobberydberg"Operators most important issues list"14:21
tobberydbergadded that to the list under missing features14:21
tobberydberglets figure it out ... but yes that was one of the ideas14:21
zhipengOkey, 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:23
zhipeng"requirement fulfillment", or some other wording14:24
mriedemadd a new label where?14:24
mriedemlike here? https://releases.openstack.org/rocky/highlights.html14:25
mriedemthat 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 though14:25
mriedemthere is also https://governance.openstack.org/tc/goals/ but i'm not sure that's a good fit14:26
zhipengYeah along the lines of that14:26
tobberydbergDo you mean like more officially state "how well Team X delivered upon the goal Y"?14:26
mriedem^ requires accepting a community wide goal first14:26
zhipengYep :)14:26
tobberydbergyup14:26
mriedempersonally i'd like to see completion % on community wide goals as well14:26
mriedemnot sure if dhellmann has something for that in the past14:27
mriedeme.g. some projects (glance) didn't complete the uwsgi goal14:27
zhipengThat is not mutually exclusive :)14:27
tobberydbergThink we are on the right track regarding release goals and highlights - 1 operator focused and one "code" focused14:27
mriedemso maybe an action item is go to the tc to figure out how to communicate community wide goal completion?14:28
tobberydbergCould be good with a more granular view of that as well, but harder with some goals14:28
zhipengI know that was built from deliverable directory, I think we need to add a new field similar to highlight14:28
mriedemzhipeng: specifically for community wide goals?14:29
zhipengYes14:29
zhipengPlus maybe other goals14:29
zhipengIt is up to the teams14:29
mriedemok i'll bring this up in the tc office hours which starts in 30 minutes14:29
zhipengAnd we could consult tc on that14:29
tobberydbergzhipeng - could that be an action for you to discuss with TC?14:29
mriedemi can float the ideas in 30 min14:30
zhipengYes it could be lol14:30
mriedemsince it's late for howard14:30
zhipengThx Matt14:30
tobberydberg+114:30
zhipengBarely have my eyes open lol14:30
mriedemtoo many hamburgers14:30
mriedemso sleepy14:30
zhipengXD14:31
tobberydberghehehe14:31
tobberydbergit's the small christmas tree that is getting to you14:32
tobberydbergAny thoughts about getting more people to attend meetings?14:33
mriedemso,14:34
mriedemhonestly i wouldn't have even thought to attend if you hadn't sent out a reminder of this upcoming meeting,14:34
mriedemso i think that's good14:34
tobberydbergWhich would be better for questions like yours mriedem as well ... bad when I'm the only one replying14:34
mriedemif you have some agenda items beforehand that's even better14:34
mriedemnow i've got it in my calendar so i can at least attend this one if i'm at the computer in time14:35
mriedem(8am here)14:35
tobberydbergYea, trying to do both ... sometimes better thatn other =) But thanks - will have that in mind!14:36
zhipeng+1 on prep agenda beforehand14:36
tobberydbergYea, and to late for APAC14:36
tobberydbergthats why we have the very early meeting (for me)  next week :-)14:37
mriedemyup14:37
tobberydbergWill do a shout out to the mailing list as well14:37
tobberydbergBTW - Reminder: OpenStack summit call for papers deadline is Jan 2314:37
tobberydbergThat chocked med :-)14:37
tobberydberg*me14:38
tobberydbergwasn't prepared for that yet =)14:38
mriedemno one is14:39
* tobberydberg reading your email thread mriedem 14:39
tobberydbergappreciated to have that on "per vm basis"14:44
tobberydbergBrings more flexibility and also will be easier to do automated operational work14:45
mriedemok if you're in favor including the pre-live migration safety check please reply to the thread14:45
mriedemi kind of need operators speaking up to get through the deadlock here14:45
tobberydbergyes, in favor of that ... cna add that14:46
mriedemthanks14:47
tobberydberg(and thats why we need more ops to be here as well)14:48
mriedemas for pre-paid instances, it sounds like that could be generally beneficial14:48
mriedem*granular locks would be generally beneficial - which would be a way to implement pre-paid instances14:48
tobberydbergYes. it will for sure bring more flexibility in the offerings to customers14:49
tobberydberg"mature customers"14:49
mriedemok so i'll follow up with a ML thread about that to get wider feedback14:49
mriedemthanks14:49
tobberydbergthe number of those today are pretty low, but will of course grown year by year14:50
tobberydbergDefinitely makes openstack a better "product offering"14:50
tobberydbergSo, 9 minutes left... Something else?14:52
mriedemnope, i have to run to another meeting14:52
tobberydbergthanks for joining mriedem and happy holidays14:52
mriedemyup you too14:53
mriedemo/14:53
mriedemenjoy the lutefisk and lefse14:53
mriedem:)14:53
mriedemmy mom's side is swedish14:53
tobberydberghahaha14:53
zhipengHaha14:53
tobberydbergxool ... didn't know! Will have a lot of "sill" (herring) at least14:54
tobberydbergzhipeng - Christmas break upcoming 2 weeks or should we have a meeting?14:54
zhipengI think we should have a break14:55
zhipengReconvene after new year's week14:55
tobberydbergnext meeting 3rd or 10th?14:55
zhipeng10th ?14:56
tobberydberg:+114:56
zhipengWe could ask Allison and other foundation folks to join as well14:56
tobberydbergSure ... maybe the 17th is better for that? (time-wise)14:56
zhipengWell anytime they see fit :)14:57
tobberydbergheheh14:57
tobberydbergThanks for today zhipeng! Happy holidays to you and talk to you next year ;-)14:58
tobberydberg#endmeeting14:58
*** openstack changes topic to "New meeting time!! Thursday odd weeks at 1400 UTC in this channel!!"14:58
openstackMeeting ended Thu Dec 20 14:58:43 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/publiccloud_wg/2018/publiccloud_wg.2018-12-20-14.05.html14:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/publiccloud_wg/2018/publiccloud_wg.2018-12-20-14.05.txt14:58
openstackLog:            http://eavesdrop.openstack.org/meetings/publiccloud_wg/2018/publiccloud_wg.2018-12-20-14.05.log.html14:58
zhipengC y'all next year :)14:59
*** pilgrimstack has joined #openstack-publiccloud15:00
pilgrimstacko/15:01
pilgrimstackhi all15:01
pilgrimstackshould we have the meeting right now ?15:01
zhipenglol we just finished15:01
pilgrimstackok perfect… I have an timezone issue…15:02
zhipengUTC 1400 : P15:02
*** mriedem has left #openstack-publiccloud15:03
pilgrimstackthx15:03
pilgrimstacksorry for that15:03
*** pilgrimstack has quit IRC15:04
*** jamesmcarthur has joined #openstack-publiccloud17:21
*** jamesmcarthur has quit IRC17:27
*** jamesmcarthur has joined #openstack-publiccloud19:31
*** jamesmcarthur has quit IRC20:24
*** jamesmcarthur has joined #openstack-publiccloud20:24
*** jamesmcarthur has quit IRC21:04
*** jamesmcarthur has joined #openstack-publiccloud21:04
*** jamesmcarthur has quit IRC22:00
*** jamesmcarthur has joined #openstack-publiccloud22:01
*** jamesmcarthur has quit IRC22:04

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!