Tuesday, 2017-06-13

*** gomarivera has joined #openstack-meeting-500:03
*** markvoelker has quit IRC00:11
*** markvoelker has joined #openstack-meeting-501:36
*** eanylin has quit IRC01:55
*** gomarivera has quit IRC02:50
*** gomarivera has joined #openstack-meeting-502:51
*** gomarivera has quit IRC02:55
*** eanylin has joined #openstack-meeting-503:21
*** LanceHaig has joined #openstack-meeting-504:38
*** LanceHaig has joined #openstack-meeting-504:38
*** LanceHaig has quit IRC05:27
*** krtaylor has quit IRC05:33
*** krtaylor has joined #openstack-meeting-505:51
*** LanceHaig has joined #openstack-meeting-506:21
*** markvoelker has quit IRC06:25
*** LanceHaig has quit IRC07:07
*** LanceHaig has joined #openstack-meeting-507:13
*** ralonsoh has joined #openstack-meeting-507:45
*** gomarivera has joined #openstack-meeting-507:51
*** gomarivera has quit IRC07:56
*** LanceHaig has quit IRC08:02
*** LanceHaig has joined #openstack-meeting-508:07
*** aarefiev_afk is now known as aarefiev08:07
*** rarcea has joined #openstack-meeting-508:10
*** markvoelker has joined #openstack-meeting-508:26
*** skazi_ has joined #openstack-meeting-508:29
*** benj_ has quit IRC08:35
*** LanceHaig has quit IRC08:37
*** LanceHaig has joined #openstack-meeting-508:37
*** makowals has quit IRC08:38
*** makowals has joined #openstack-meeting-508:41
*** LanceHaig has quit IRC08:45
*** derekh has joined #openstack-meeting-508:47
*** markvoelker has quit IRC08:59
*** stokvis has joined #openstack-meeting-509:02
*** skazi_ has quit IRC09:15
*** skazi has quit IRC09:15
*** skazi_ has joined #openstack-meeting-509:15
*** skazi has joined #openstack-meeting-509:16
*** skazi_ has quit IRC09:16
*** skazi_ has joined #openstack-meeting-509:16
*** skazi_ has quit IRC09:39
*** makowals has quit IRC09:43
*** skazi_ has joined #openstack-meeting-509:48
*** makowals has joined #openstack-meeting-509:49
*** skazi_ has quit IRC09:51
*** markvoelker has joined #openstack-meeting-509:57
*** stokvis has quit IRC10:04
*** markvoelker has quit IRC10:30
*** markvoelker has joined #openstack-meeting-511:27
*** benj_ has joined #openstack-meeting-511:44
*** markvoelker has quit IRC11:59
*** markvoelker has joined #openstack-meeting-512:25
*** gomarivera has joined #openstack-meeting-512:54
*** gomarivera has quit IRC12:58
*** eanylin has quit IRC13:06
*** eanylin has joined #openstack-meeting-513:31
*** gomarivera has joined #openstack-meeting-513:39
*** skazi_ has joined #openstack-meeting-513:49
*** gardlt has joined #openstack-meeting-514:07
*** theyer has joined #openstack-meeting-514:07
*** theyer has quit IRC14:12
*** theyer has joined #openstack-meeting-514:14
*** felipemonteiro_ has joined #openstack-meeting-514:15
*** felipemonteiro__ has joined #openstack-meeting-514:17
*** felipemonteiro_ has quit IRC14:21
*** felipemonteiro__ has quit IRC14:35
*** theyer has quit IRC14:39
*** theyer has joined #openstack-meeting-514:40
*** gagehugo has joined #openstack-meeting-514:55
*** StaceyF has joined #openstack-meeting-514:57
*** theyer has quit IRC14:57
*** srwilkers has joined #openstack-meeting-514:59
*** theyer has joined #openstack-meeting-514:59
*** alraddarla has joined #openstack-meeting-515:00
*** mattmceuen has joined #openstack-meeting-515:00
*** lrensing has joined #openstack-meeting-515:00
srwilkers#startmeeting OpenStack-Helm15:02
openstackMeeting started Tue Jun 13 15:02:56 2017 UTC and is due to finish in 60 minutes.  The chair is srwilkers. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: OpenStack-Helm)"15:02
openstackThe meeting name has been set to 'openstack_helm'15:03
srwilkershey good morning everyone15:03
srwilkersthanks for joining15:03
v1k0d3no/15:03
alraddarlao/15:03
serverascodeo/15:03
gardlto/15:03
duleko/15:03
lrensingo/15:04
srwilkersi don't think we have a lot on the agenda for this meeting, so there are a few items i wanted to touch one, then we can open up the floor and discuss any topics you'd like to raise15:04
*** skazi_ has quit IRC15:04
lamto/15:04
alanmeadows\o15:04
v1k0d3nalanmeadows: just have to be different with that right-handed wave.15:05
srwilkerslook at alanmeadows, leading change15:05
srwilkersfirst thing i wanted to chat about was our list of bugs on launchpad: https://bugs.launchpad.net/openstack-helm15:05
srwilkersive seen a few questions pop up on IRC over the last week about some weird behavior, and i'd like to see those end up in either confirming a bug's existence thats listed or filing a new one if appropriate15:06
v1k0d3nit's because his brain is abnorally large on the left side (engineering/science) that he can't raise his left arm.15:06
srwilkershaha15:06
alanmeadowsim virtually ambidextrous15:07
v1k0d3nleakypipes would  appreciate that one.15:07
alanmeadowssrwilkers: I think the list is a good start, I think at the moment it is unrepresentative of the known issues15:08
srwilkersalanmeadows, agreed15:08
v1k0d3n+115:08
alanmeadowssrwilkers: is the call to action to encourage those reporting them in IRC to go create bugs, or a call to action for regulars to fill those out for them?15:09
srwilkersthe call to action is for anyone reporting behavior they expect is a bug should file a bug in launchpad15:09
alanmeadowsI'm wondering, do we have a creating a bug report documentation page, where we educate potentially new users the information we're after -- similar to the old github templates asking for versions of this that and others15:09
srwilkersthe drivers team should then triage it and verify it's an issue and prioritize it15:10
alanmeadowsI will admit I haven't gone through the process yet to see what information launchpad asks for15:10
alanmeadowsfor this project15:10
lrensingi don't think we do alanmeadows15:10
v1k0d3ndocs need this alanmeadows15:10
srwilkersalanmeadows, i believe there's openstack documentation for filing bugs or issues, let me check15:10
v1k0d3ndocs need love in general, but this would be a good first step15:11
*** leifmadsen has joined #openstack-meeting-515:11
* portdirect enters room huffing and puffing, sorry I'm late peeps15:11
srwilkershttps://wiki.openstack.org/wiki/Bugs#Reporting is a good spot to start, albeit the links are for the core projects15:11
srwilkersbut we can also provide a tl;dr for filing bugs15:11
alanmeadowssure, but likely we want details such as kubernetes versions, kubelet versions15:12
alanmeadowsperhaps offering and suggesting something similar to the gate "dump it all" scripts15:13
portdirect++15:13
srwilkersthat sounds reasonable to me15:13
portdirectthat would be great - for the gate env we have pretty much everything clocked down, bar docker that i can think of - but a summary report would really help there15:14
alanmeadowsso when someone creates a bug report that says mariadb fails to come up, but from the dump its clear their PVC backend is hosed, we know what we're dealing with15:14
srwilkersyeah, that helps reduce the overhead associated with triaging and trying to pin down exactly where the issues may have started.15:15
lrensing++15:15
alanmeadowsso the take away would be a document describing the details we need, directing them to a net-new script (some modified version of gate dump) where they can attach a debug payload15:17
portdirectok - all we need is a quick doc that tells you to set/export LOGS_DIR before running the log dump script15:17
portdirectwhere they attach the payload is anther question though :D15:17
srwilkersportdirect, alanmeadows yep. i think it's reasonable to get that done fairly quickly15:17
srwilkersportdirect, ill let you take it from here for a bit15:18
srwilkersim off to another meeting15:18
* portdirect glares around room15:18
portdirectsuppose we should also discuss blueprints?15:19
portdirectideally we should try and link the work we are doing against them (and I know I'm prob the worst at doing that...)15:19
portdirecti know srwilkers has also been taking to infra about getting the link between launchpad and gerrit running smooth15:20
*** theyer has quit IRC15:20
lrensingyeah we need to be more diligent about referencing blueprints in our patchsets15:21
portdirectI think perhaps we should come to some agreement about what needs a bp15:21
alanmeadowsto be clear, part of the problem is not only linking15:21
alanmeadowsthe bp to link to is missing as well15:21
lrensingmost definitely alanmeadows15:21
portdirect:)15:21
portdirectso, if its a new feature it needs a bp (i think we can all agree here)15:22
lrensingbut to pete's point, how do we determine the scope required for a bp15:22
lrensingyes15:22
portdirectif its a change that is requires as k8s/helm etc change, we should prob make a blueprint in the form of say (bp: support helm 2.4)15:23
portdirectwhich may touch on sveral charts/areas15:23
dulekI guess any new feature needs a blueprint that will explain the motivation.15:23
dulekFixes and minor refactors won't need blueprints.15:24
portdirectagreed15:24
dulekI think that's the simplest classification you can get.15:24
dulekAnd in doubt - ask the core team. :)15:24
lrensingright - to that i'd like to say that project-wide refactors should be given more attention (maybe a bp?)15:24
duleklrensing: Totally. :)15:24
portdirectyeah - as they would need to be justified15:25
alanmeadowsso the list of what doesn't need a bp is "cleanup" refactors focused on a specific chart, and bugs (which are a separate thing)15:25
portdirect++15:25
lrensingyes15:25
portdirectwell that seemed easy :)15:25
lrensingwhat about documentation and blueprints15:25
portdirectso shall we try and enforce, no merge unless we have met this criteria?15:25
portdirecti think when approving the pb, it should require that it includes docs/tests as part of the scope as required15:26
alanmeadowsthat is talking about the bottom layer, we haven't discussed the workflow operations of blueprints themselves which at this moment do not appear to be exercised15:26
alanmeadowsaccepted, assigned, so on15:26
portdirectso its not marked as compete until thats done15:26
alanmeadowsnot only must a bp exist, but it should be accepted to merge commits from15:26
alanmeadowsif a traditional workflow is being followed15:27
portdirectgood point, at the moment most people seem to be creating and self approving15:27
lrensingyeah alanmeadows we're getting ahead of ourselves slightly :)15:27
alanmeadowsthere needs to be a bp grooming process15:27
alanmeadowsits basically roadmap enforcement15:27
alanmeadowsat the bp level15:27
*** theyer has joined #openstack-meeting-515:27
alanmeadowsand so sorry for mentioning the word grooming15:28
portdirectright - so should we make this part of the meeting  - a section for bp reviews15:28
lrensingi am fine with that15:29
lrensingif it becomes too much of a timesink we can address it then15:29
portdirectok - so this week - can we go over all the existing bp's and get them in shape?15:30
portdirecttheres 24 currently so not too much of a task for a quick vetting: https://blueprints.launchpad.net/openstack-helm15:31
portdirectand then we should create pb's for all the appropriate ps's we have in flight (probably mostly looking at myself here...)15:31
alanmeadowsyou are the root of many issues15:32
lrensinglet's dive into it then15:32
portdirectnice - dulek would be great to get your input on the ones out there as well15:34
dulekportdirect: Sure thing, although I don't think I'll be opposed to any of the BP.15:35
portdirectwe done on this topic for now?15:35
portdirectok - so I've got one more thing I want to mention15:37
portdirectI'm hoping that we should have a ceph based deploy running in the three node check by eod15:37
portdirect^^ I'll even make a bp for it :D15:37
lrensingi'll hold you to it portdirect15:38
dulek\o/15:38
alraddarlalolz15:38
portdirectand would really like to get the linter moving to a voting gate - as its been very stable15:38
portdirectso - with that I've run out of steam :)15:39
alanmeadowshttps://cdn.meme.am/instances/400x/55368412.jpg15:39
portdirectany other things people would like to bring up15:39
portdirectyou knows it alanmeadows  :)15:39
serverascodeI was wondering if there is anything obvious for a newb to work on15:39
portdirectserverascode: theres a lot of potential areas :) and it would be awesome to get more hands on the deck. docs are an obvious 1st place (as most of us are too deep int the woods to offer a proper outside perspective)15:41
portdirectbut do you have any areas that interest you or you've worked on before?15:42
serverascodeno not particularly, but I can poke around at docs and see if there is anything I can contribute there15:42
portdirectoff the top of my head, getting assiatnce expanding the 'helm test' stuff from glance and keystone to other charts would be super valuble15:42
serverascodeok, I can take a look into that as well15:43
alanmeadowswhat is the mandate for things exercised in these rally launched tests15:44
alanmeadowsWhat is a test that is "too long"15:44
alanmeadowsor "overkill"15:44
alanmeadowshow are the ones there chosen15:45
portdirectthere is a default timeout of 300s in helm for the enire test to run15:45
alanmeadowsand how would someone else examine a list to do their own choosing15:45
alanmeadowsof candidates for inclusion15:45
portdirectthe ones chosen (to date) have been those that exercise only that service and any immediate dependencies15:46
portdirectas we should have a sperate rally chart that does comprehestive testing15:46
portdirectjayahn has a pb for tempest based tests15:46
portdirectpersonally I'd like to see: rally (driving tempest) where possible, falling back to tempest when not, and finally basic functioal tests via the cli when even thats not avalible for a service15:47
alanmeadowsyes but to the point serverascode is asking, how would a new entrant build such a list for another chart, say nova15:48
alanmeadowsthe framework is clear, the process foe electing tests to go into the rally yaml, not so clear15:48
portdirectah - i see your point15:48
portdirecta good set of tests can be obtained from here for a service: https://github.com/openstack/rally/tree/0.8.1/samples/tasks/scenarios/nova15:49
alanmeadowsthat was where I was going15:49
portdirectand some judgement will be needed, as for example this: https://github.com/openstack/rally/blob/0.8.1/samples/tasks/scenarios/nova/create-and-delete-network.yaml15:49
portdirectwould not be approprate as it rely on novanetwork being used15:50
portdirectalso I've been setting the runner and sla to just exercise the service, not make it sweat: https://github.com/openstack/openstack-helm/blob/master/keystone/templates/etc/_rally_tests.yaml.tpl#L7-L1315:51
portdirect^^ and theres a terminology oxymoron :)15:51
alanmeadowsI sense a need for the test framework to have some documentation including these details15:51
alanmeadowsotherwise contributions on this front will be challenging, and we need contributions here15:52
portdirectright - I'll put together a doc asap15:53
* portdirect mumbles about being caught by his own edicts15:53
alanmeadows:)15:53
lrensinganything else to discuss? i think we covered the big points15:54
portdirectI'm good15:54
lrensingotherwise i think we can wrap this up15:54
alraddarla\o15:55
portdirectcool - so we good to close up?15:56
srwilkers#endmeeting OpenStack-Helm15:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:57
openstackMeeting ended Tue Jun 13 15:57:05 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-06-13-15.02.html15:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-06-13-15.02.txt15:57
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-06-13-15.02.log.html15:57
*** alraddarla has left #openstack-meeting-515:57
*** theyer has quit IRC15:57
*** theyer has joined #openstack-meeting-515:59
*** theyer has quit IRC16:02
*** gardlt has left #openstack-meeting-516:15
*** theyer has joined #openstack-meeting-516:16
*** theyer has quit IRC16:20
*** StaceyF has quit IRC16:20
*** theyer has joined #openstack-meeting-516:30
*** derekh has quit IRC16:43
*** theyer has quit IRC16:47
*** theyer has joined #openstack-meeting-516:48
*** theyer has quit IRC16:51
*** tuanla_fujitsu has joined #openstack-meeting-516:59
*** ricolin has quit IRC16:59
*** felipemonteiro has joined #openstack-meeting-516:59
*** tuanla__ has joined #openstack-meeting-517:00
*** ralonsoh has quit IRC17:03
*** krtaylor has quit IRC17:35
*** tuanla__ has quit IRC17:37
*** tuanla_fujitsu has quit IRC17:37
*** theyer has joined #openstack-meeting-517:39
*** theyer has quit IRC17:45
*** theyer has joined #openstack-meeting-517:46
*** gagehugo has left #openstack-meeting-517:54
*** krtaylor has joined #openstack-meeting-518:20
*** theyer has quit IRC18:26
*** theyer has joined #openstack-meeting-518:33
*** theyer has quit IRC18:49
*** krtaylor has quit IRC19:20
*** gomarivera has quit IRC19:43
*** theyer has joined #openstack-meeting-519:44
*** gomarivera has joined #openstack-meeting-519:47
*** theyer has quit IRC19:51
*** theyer has joined #openstack-meeting-519:51
*** theyer has quit IRC19:57
*** theyer has joined #openstack-meeting-519:58
*** gomarivera has quit IRC19:58
*** krtaylor has joined #openstack-meeting-520:00
*** theyer has quit IRC20:02
*** theyer has joined #openstack-meeting-520:03
*** gomarivera has joined #openstack-meeting-520:05
*** theyer has quit IRC20:34
*** theyer has joined #openstack-meeting-520:38
*** theyer has quit IRC20:56
*** theyer has joined #openstack-meeting-521:03
*** srwilkers has quit IRC21:07
*** krtaylor has quit IRC21:13
*** lrensing has quit IRC21:14
*** Guest11 has joined #openstack-meeting-521:20
*** theyer has quit IRC21:20
*** mattmceuen has quit IRC21:24
*** felipemonteiro has quit IRC21:34
*** Guest11 has quit IRC21:39
*** theyer has joined #openstack-meeting-521:42
*** krtaylor has joined #openstack-meeting-521:53
*** theyer has quit IRC21:53
*** gomarivera has quit IRC21:56
*** gomarivera has joined #openstack-meeting-521:56
*** gomarivera_ has joined #openstack-meeting-521:58
*** gomarivera has quit IRC21:58
*** gomarivera_ has quit IRC22:03
*** rarcea has quit IRC22:15
*** theyer has joined #openstack-meeting-522:29
*** theyer has quit IRC22:33
*** gomarivera has joined #openstack-meeting-523:19
*** gomarivera has quit IRC23:24
*** gomarivera has joined #openstack-meeting-523:40

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