Monday, 2019-07-01

*** ricolin has joined #openstack-uc01:04
*** VW_ has joined #openstack-uc03:11
*** VW_ has quit IRC03:45
*** ricolin_ has joined #openstack-uc05:03
*** ricolin has quit IRC05:06
*** ricolin_ has quit IRC06:09
*** ricolin has joined #openstack-uc06:09
*** ricolin_ has joined #openstack-uc08:45
*** ricolin_ has quit IRC08:47
*** ricolin_ has joined #openstack-uc08:47
*** ricolin has quit IRC08:48
*** ricolin_ is now known as ricolin09:07
*** ricolin has quit IRC09:20
*** belmoreira has joined #openstack-uc14:07
*** jamesmcarthur has joined #openstack-uc14:20
*** belmoreira has quit IRC14:53
*** VW_ has joined #openstack-uc14:56
*** studarus has joined #openstack-uc14:57
VW_#startmeeting uc14:59
openstackMeeting started Mon Jul  1 14:59:39 2019 UTC and is due to finish in 60 minutes.  The chair is VW_. Information about MeetBot at http://wiki.debian.org/MeetBot.14:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:59
*** openstack changes topic to " (Meeting topic: uc)"14:59
openstackThe meeting name has been set to 'uc'14:59
VW_#chair studarus spotz14:59
openstackCurrent chairs: VW_ spotz studarus14:59
VW_#topic roll call15:00
*** openstack changes topic to "roll call (Meeting topic: uc)"15:00
VW_o/15:00
studaruso/15:00
apriceo/15:00
VW_we'll give folks a couple minutes15:00
jamesmcarthuro/15:00
*** belmoreira has joined #openstack-uc15:01
VW_#chair belmoreira15:01
openstackCurrent chairs: VW_ belmoreira spotz studarus15:01
spotzo/15:02
VW_alrighty let's pick up from last week15:02
VW_#topic Role of the UC15:02
*** openstack changes topic to "Role of the UC (Meeting topic: uc)"15:02
VW_So, jamesmcarthur / aprice - one of you want to re-ask some of the questions that started us last week?15:03
apricesure15:03
apricebasically, we wanted to revisit the role of the UC. This lead into a conversation where we can start with a question of "What are the goals of the UC?"15:04
apricethen we can drill down into specific activities, but it didn't seem like there was consensus around that question last week15:04
VW_so, looks like Belmiro and I put some thoughts in the etherpad15:05
VW_#link https://etherpad.openstack.org/p/uc15:05
VW_we can start there and see if there are any goals that we are missing (or if anything is on the list we don't agree with)15:06
belmoreiramy thoughts are more related to activities and the high level goals15:06
*** josephrsandoval has joined #openstack-uc15:06
VW_#chair josephrsandoval15:06
openstackCurrent chairs: VW_ belmoreira josephrsandoval spotz studarus15:06
belmoreirafor me the s/and/than15:06
studarusdoes outreach and evangelism fall under the UC? basically increasing adoption15:07
spotzbelmoreira: I don't think you're far off for the high end stuff. That's pretty much been our focus. To some degree we haven't been as in your face as the TC so we're les out there15:08
apricestudarus: i think that increasing adoption would be a good goal and if outreach and evangelism get that done, then by all means15:09
belmoreiraaprice studarus I think that's a good point. But I don't feel that should be UC focus. In my view UC should facilitate communication between technical/users15:11
belmoreiraadoption should be an OSF goal15:11
VW_I see a lot of that, but the relationship of the UC to Ambassadors is a space where I do think the UC plays a role in outreach/etc15:12
VW_(have to turn on VPN for a second - might get dropped, but will come back)15:12
apriceyeah i think that's a good point belmoreira15:12
*** VW_ has quit IRC15:13
belmoreiraas UC we always refer to users. But what's not clear to me is what a "user" should be for the UC15:14
apricebelmoreira: i think that the way we have typically defined it is someone who is operating OpenStack15:14
belmoreiraend users usually are not aware what is the cloud platform that they are on. At least is my perception15:15
belmoreiraso for me the focus of the UC should be ops15:15
apriceyeah i think that end users is a different community. rather, it's folks who are directly operating the infrastructure15:15
jamesmcarthurFor reference, here's the way we defined the role of the UC in February 2018 at the Dublin PTG: https://etherpad.openstack.org/p/UC-Rocky-PTG15:16
*** VW_ has joined #openstack-uc15:16
VW_sorry - back15:16
jamesmcarthurThis document was set up as a set of guidelines for how to move the UC forward.  Very few of the agenda items ever ended up with actions associated.15:17
spotzYeah our users are the operators for public/private/hybrid clouds not like Rackspace customers or people in CERN with a login to do stuff15:17
jamesmcarthurspotz: I don't think that's accurate.15:18
jamesmcarthurPeople in CERN and end users of OpenStack clouds are most definitely within the definition of users.15:18
spotzjamesmcarthur: Many of those people have no clue what they're hosted on though15:18
jamesmcarthurBut many do. And for those people looking to give feedback around OpenStack use, they would most definitely be considered a user.15:19
jamesmcarthurThey consume the APIs that are maintained by our community.15:19
josephrsandovalUser by definition is broader in scope compared to operators.15:19
*** ricolin has joined #openstack-uc15:20
jamesmcarthurThat's why we've always made a distinction b/w operators and users.15:20
VW_and it's a fair distinction15:20
VW_I do believe the UC represents both15:20
VW_often, we bias to that Operators - and that's not bad as long as we view them as speaking on behalf of the end users in many cases15:20
belmoreiracloud deployments usually have their own support. Most of my users don't have any idea about OpenStack and no interest to interact with the community. Ops bridge to the OpenStack community15:20
jamesmcarthurI've personally been working with Mohammed on problems with OpenStack public cloud and setting up a working load balancer for a simple web environment.15:22
jamesmcarthurThis is for our setup on Vexxhost for openstack.org and our other web properties.15:22
jamesmcarthurIt's resulted in more than a dozen patches for Ansible and Octavia.15:23
jamesmcarthurSo while you're right, not everyone is clued into their environment, a lot of hosting companies use the OpenStack dashboard and people are very familiar with the environment.15:23
jamesmcarthurAnd can offer valuable feedback to teh community.15:24
jamesmcarthurJust something to consider.15:24
belmoreirajamesmcarthur: I see that as a very particular case15:25
belmoreiramy experience is that when having issues or suggestions they contact the cloud operators. Couldn't be different because any OpenStack cloud is different. We have ~10k users. Over the years I think we didn't have any ticket opened upstream by an user.15:26
spotzWe can hope to educate users to want to be on OpenStack I just don't know if we have/should have access to them15:27
VW_but again - this body has to be thinking both about stability/ease of operatoins (for operators) and feature/function/east of use (for end users) - whether the later comes directly or via the Ops folks themselves15:28
belmoreiraVW_ +1. For me this is ops. Because my users pain is my day work pain (support tickets, requests, ...)15:29
spotzAgree with that15:31
belmoreirain my view if we invest in a strong ops/developers interaction end users will benefit15:32
belmoreiraand we reduce the scope of our committee15:33
VW_So, this is good discussion, but are we narrowing down on agreement/next steps15:37
josephrsandovalfeels like the scope is narrowing on what the user committee aspirationally should be doing.15:38
VW_So, can we commit to updating the thoughts in the etherpad based on this conversation by next Monday?15:42
belmoreirabut having a narrow/focus scope is not bad. Having a well defined target/mission can help us to accomplish more, considering how few we are.15:44
VW_agreed15:44
VW_Ok - well in the spirt of time managment15:46
VW_#action belmoreira spotz studarus VW_ josephrsandoval update etherpad with thoughts on scope/goals based on today's discussion15:47
VW_we can also take the conversation to email, etc15:48
josephrsandoval+115:48
VW_#topic Elections15:48
*** openstack changes topic to "Elections (Meeting topic: uc)"15:48
VW_regardless of the outcome of all these conversations, we need to get the ball rolling on the elections15:49
VW_the following were the dates last year:15:50
VW_August 6 - August 17, 05:59 UTC: Open candidacy for UC positions15:50
VW_August 20 - August 24, 11:59 UTC: UC elections (voting)15:50
VW_We good with August 5 - 16th for candidacy and 19 - 24 for elections15:52
josephrsandovalyes15:52
belmoreiralooks good for me15:52
VW_cool - anyone want to volunteer to create the page for it15:53
VW_similar to15:53
josephrsandovalelection window Aug 19-23 if we are following time cadence15:53
VW_#link https://governance.openstack.org/uc/reference/uc-election-aug2018.html15:53
VW_yes - sorry - typo on my part josephrsandoval15:53
spotzWell who wants to lead the election? Easier if they make the page as well15:55
studarusCan that be someone from the UC or does it need to be outside?15:57
VW_someone not running should be a big driver, but we'll reach out for election officials to run the actual process15:57
studarusI'm not running - I can create the page15:57
VW_cool15:58
VW_we can probably make the call for officials in a week or two15:58
VW_#actoin studarus create page for elections15:58
VW_#topic other business15:58
*** openstack changes topic to "other business (Meeting topic: uc)"15:58
VW_35 seconds - go :)15:58
VW_Thanks for playing, folks - we'll do it again next week15:59
VW_spend some time on the etherpad15:59
VW_#endmeeting16:00
*** openstack changes topic to "OpenStack UC: 2019 Elections coming! Open Candidacy 01/21-02/03 | Meetings @ 1900UTC | Agenda - https://etherpad.openstack.org/p/uc"16:00
openstackMeeting ended Mon Jul  1 16:00:16 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/uc/2019/uc.2019-07-01-14.59.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/uc/2019/uc.2019-07-01-14.59.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/uc/2019/uc.2019-07-01-14.59.log.html16:00
*** josephrsandoval has quit IRC16:01
*** belmoreira has quit IRC16:08
*** ricolin has quit IRC16:13
*** ricolin has joined #openstack-uc16:25
*** openstackgerrit has joined #openstack-uc16:50
openstackgerritJohn Studarus proposed openstack/governance-uc master: August 2019 election details  https://review.opendev.org/66852516:50
*** ricolin has quit IRC16:53
*** jamesmcarthur has quit IRC17:47
*** jamesmcarthur has joined #openstack-uc18:24
*** studarus has quit IRC18:39
*** jamesmcarthur has quit IRC20:45
*** VW_ has quit IRC20:46
*** VW_ has joined #openstack-uc20:54
*** VW_ has quit IRC21:00
*** jamesmcarthur has joined #openstack-uc21:03
*** studarus has joined #openstack-uc21:08
*** jamesmcarthur has quit IRC22:27
*** jamesmcarthur has joined #openstack-uc22:27
*** jamesmcarthur_ has joined #openstack-uc22:28
*** jamesmcarthur has quit IRC22:32
*** jamesmcarthur_ has quit IRC23:05
*** VW_ has joined #openstack-uc23:54

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