| *** ricolin has joined #openstack-meeting-5 | 00:47 | |
| *** seungkyua has joined #openstack-meeting-5 | 01:43 | |
| *** seungkyua has quit IRC | 01:47 | |
| *** yamamoto has joined #openstack-meeting-5 | 02:15 | |
| *** yamahata has quit IRC | 03:41 | |
| *** yamamoto_ has joined #openstack-meeting-5 | 06:57 | |
| *** slaweq has joined #openstack-meeting-5 | 06:59 | |
| *** stokvis has joined #openstack-meeting-5 | 07:00 | |
| *** yamamoto has quit IRC | 07:00 | |
| *** radek__ has joined #openstack-meeting-5 | 08:14 | |
| *** roman_g has joined #openstack-meeting-5 | 08:28 | |
| *** derekh has joined #openstack-meeting-5 | 08:46 | |
| *** ricolin has quit IRC | 11:02 | |
| *** yamamoto_ has quit IRC | 11:29 | |
| *** yamamoto has joined #openstack-meeting-5 | 11:35 | |
| *** yamamoto has quit IRC | 11:58 | |
| *** roman_g has quit IRC | 12:30 | |
| *** roman_g has joined #openstack-meeting-5 | 12:31 | |
| *** yamamoto has joined #openstack-meeting-5 | 12:44 | |
| *** yamamoto has quit IRC | 13:44 | |
| *** radeks has joined #openstack-meeting-5 | 13:49 | |
| *** lajoskatona_ has joined #openstack-meeting-5 | 14:00 | |
| *** lajoskatona_ has quit IRC | 14:00 | |
| *** stokvis has quit IRC | 14:18 | |
| *** hongbin has joined #openstack-meeting-5 | 14:21 | |
| *** derekh has quit IRC | 14:44 | |
| *** yamamoto has joined #openstack-meeting-5 | 14:45 | |
| *** tdoc has joined #openstack-meeting-5 | 14:51 | |
| *** yamamoto has quit IRC | 14:51 | |
| *** jgu_ has joined #openstack-meeting-5 | 14:56 | |
| *** yamamoto has joined #openstack-meeting-5 | 14:56 | |
| *** slaweq_ has joined #openstack-meeting-5 | 14:58 | |
| *** slaweq has quit IRC | 14:58 | |
| mattmceuen | #startmeeting openstack-helm | 15:00 |
|---|---|---|
| openstack | Meeting started Tue Jun 5 15:00:19 2018 UTC and is due to finish in 60 minutes. The chair is mattmceuen. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| *** openstack changes topic to " (Meeting topic: openstack-helm)" | 15:00 | |
| openstack | The meeting name has been set to 'openstack_helm' | 15:00 |
| mattmceuen | #topic rollcall | 15:00 |
| *** openstack changes topic to "rollcall (Meeting topic: openstack-helm)" | 15:00 | |
| srwilkers | o/ | 15:00 |
| *** gmmaha has joined #openstack-meeting-5 | 15:00 | |
| mattmceuen | GM srwilkers! | 15:00 |
| gmmaha | o/ | 15:00 |
| srwilkers | hey mattmceuen :D | 15:00 |
| mattmceuen | https://etherpad.openstack.org/p/openstack-helm-meeting-2018-06-05 | 15:00 |
| alanmeadows | o/ | 15:01 |
| roman_g | o/ | 15:01 |
| mattmceuen | Here's our agenda - please add all the burning talking points that have been keeping you up at night | 15:01 |
| lamt | o/ | 15:01 |
| *** yamamoto has quit IRC | 15:01 | |
| srwilkers | thats a long list | 15:01 |
| mattmceuen | please prioritize them to talk about the OSH things first | 15:01 |
| mattmceuen | if we move fast we can work our way down to spicy mexican food | 15:02 |
| mattmceuen | First thing: | 15:02 |
| mattmceuen | #topic Storyboard Friday | 15:02 |
| *** openstack changes topic to "Storyboard Friday (Meeting topic: openstack-helm)" | 15:02 | |
| mattmceuen | Storyboard Friday. | 15:03 |
| mattmceuen | Not sure of the exact time but we'll keep the migration communicated in the channel | 15:03 |
| mattmceuen | I suggest to be safe, let's just stay out of Launchpad on Friday | 15:03 |
| rwellum | Hopefully smooth sailing... o/ | 15:03 |
| srwilkers | hey rwellum o/ | 15:04 |
| rwellum | hi srwilkers | 15:04 |
| *** gagehugo has joined #openstack-meeting-5 | 15:04 | |
| mattmceuen | As far as our daily lives post-storyboard | 15:04 |
| mattmceuen | 1) use Storyboard for all new scope and bugs and specs going forward | 15:05 |
| mattmceuen | there are no more blueprints, no more bugs | 15:05 |
| mattmceuen | Everything is a Story (hence the name) | 15:05 |
| portdirect | specs? | 15:05 |
| mattmceuen | Yep specs should be captured as stories | 15:05 |
| portdirect | I need to read up - but would we no longer be doing them in gerrit? | 15:05 |
| mattmceuen | We should find an example of a story spec | 15:06 |
| mattmceuen | Specs in gerrit | 15:06 |
| mattmceuen | Just no blueprint in launchpad any more - a story in storyboard instead | 15:06 |
| alanmeadows | are folks generally creating a story linking to the gerrit spec for full storyboard awareness? | 15:06 |
| alanmeadows | I am unaware of the sb customs | 15:07 |
| mattmceuen | 2) For linking PS to Stories (in general) here is a quick example from Kendall | 15:07 |
| mattmceuen | As for instructions on git commit headers its pretty simple. You link both the task and the story in the commit. You should know this from Upstream Institute :wink: It ends up looking like this: | 15:07 |
| mattmceuen | ----------------- | 15:07 |
| mattmceuen | Commit message summary line stuff | 15:07 |
| mattmceuen | Commit message body info. All the details. Blah blah blah. | 15:07 |
| mattmceuen | Story: 882882 | 15:07 |
| mattmceuen | Task: 2221 | 15:07 |
| mattmceuen | Change-Id: djk3kj24jk2kj21kj1kj25009sdfk | 15:07 |
| mattmceuen | ---------------- | 15:07 |
| mattmceuen | rwellum - have you seen any good example / prior art for spect-storyboard linking? | 15:08 |
| rwellum | Looking at ironic right now to pull one out | 15:09 |
| mattmceuen | Awesome thanks | 15:09 |
| pcarver_ | I haven't been following storyboard development. Did they standardize on a way of showing release content? | 15:09 |
| mattmceuen | Also thanks to rwellum for leading this effort | 15:09 |
| jayahn | o/ | 15:10 |
| *** pcarver_ is now known as pcarver | 15:10 | |
| mattmceuen | Release content in what sense - like release notes? | 15:10 |
| mattmceuen | hey jayahn! | 15:10 |
| jayahn | hey | 15:10 |
| pcarver | I mean the equivalent to Launchpad's "Series and milestones" pages | 15:10 |
| roman_g | q: would we change URL in #openstack-helm topic from Launchpad to Storyboard? | 15:11 |
| srwilkers | roman_g: i would imagine so | 15:11 |
| pcarver | Where you can see what bugs and blueprints are planned for any future milestone or were contained in any past milestone | 15:11 |
| rwellum | BTW airship is already using storyboard: https://storyboard.openstack.org/#!/project_group/85 | 15:12 |
| mattmceuen | Lucky them, they started there so don't have to do a migration :) | 15:12 |
| mattmceuen | Note I'm planning to shamelessly model after the links on the ironic wiki | 15:13 |
| mattmceuen | https://wiki.openstack.org/wiki/Ironic | 15:13 |
| mattmceuen | re: bug tracker / feature tracker | 15:13 |
| alanmeadows | airship is already hoving over storyboard | 15:13 |
| mattmceuen | specifying the release is not jumping out to me pcarver | 15:13 |
| mattmceuen | alanmeadows is here all day, folks | 15:13 |
| pcarver | Hmm, looking at OSH's Launchpad it doesn't look like you've been tracking any releases yet anyway | 15:14 |
| portdirect | nope | 15:14 |
| portdirect | as we dont yet have one | 15:14 |
| portdirect | though probably should have bee tracking toward it | 15:14 |
| portdirect | *been | 15:14 |
| *** wxy| has joined #openstack-meeting-5 | 15:15 | |
| mattmceuen | Yeah, we just have a spec for 1.0, and I'm going to translate remaining work items into stories. I'll release teg them in the right way if we can figure out what that looks like. | 15:15 |
| pcarver | Neutron is what I usually look at as the ideal example https://launchpad.net/neutron/+series | 15:15 |
| portdirect | pcarver: you know that launchpad is going away? | 15:16 |
| pcarver | You can see every milestone all the way back to the Diablo series and click on any one to see what was in it | 15:16 |
| rwellum | Good example of ironic, plus tags: https://storyboard.openstack.org/#!/story/2002064 | 15:16 |
| pcarver | portdirect: I'm aware of it, but when I asked the Storyboard folks about this functionality 8-12 months ago it wasn't even on their radar | 15:16 |
| portdirect | roger | 15:17 |
| mattmceuen | aha | 15:17 |
| mattmceuen | does subject-prefixing stories-for-specs with "[RFE]" sound good to y'all? | 15:17 |
| pcarver | I'm not sure if it's because they didn't/don't care about recording history or if they just weren't familiar with Launchpad's interface | 15:17 |
| rwellum | This amongst other reasons is why the transition hasn't happened for all. But we reasoned that being fairly new, for OSH it's better now than later. | 15:18 |
| pcarver | They kind of suggested that every project would just invent its own practices | 15:18 |
| rwellum | pcarver: yeah same message I got at the summit. | 15:18 |
| pcarver | Which sounded like an awful idea to me | 15:18 |
| portdirect | we work with what we have :) | 15:18 |
| mattmceuen | +1 :) | 15:18 |
| mattmceuen | aka "do what Ironic does till we see something we don't like" | 15:19 |
| mattmceuen | Alright - any other Storyboard items before we tie this one up and breathlessly wait till friday | 15:19 |
| portdirect | shouldn't be to physically painful | 15:19 |
| pcarver | But if everybody is on their own to establish and follow practices, then it would be at least a good idea to figure out what those are | 15:19 |
| rwellum | pcarver: think it's worthwhile firing off an email to openstack-dev? | 15:19 |
| pcarver | rwellum: Possibly. I haven't been following storyboard migrations, so maybe some teams have already figured out standard practices. | 15:20 |
| mattmceuen | would be helpful for teams to have all best practices summarized in one place, even if it has the caveat to "do whatever you want" | 15:20 |
| mattmceuen | Alright we'd better keep rolling. Let's stay in sync on this in the #openstack-helm channel | 15:22 |
| mattmceuen | #topic Review OSH troubleshooting brainstorming | 15:22 |
| *** openstack changes topic to "Review OSH troubleshooting brainstorming (Meeting topic: openstack-helm)" | 15:22 | |
| pcarver | The main question for any give team to answer (e.g. OSH), is whether the team sees value in maintaining a history of what the series and milestones were and what was in each | 15:22 |
| mattmceuen | https://etherpad.openstack.org/p/openstack-helm-troubleshooting | 15:22 |
| jayahn | i do think there is value in maintinaing history | 15:23 |
| portdirect | I really see value in release notes | 15:23 |
| mattmceuen | Agree - we should start off on the right foot | 15:23 |
| portdirect | as meeting part of that requirements | 15:23 |
| mattmceuen | +1 | 15:23 |
| mattmceuen | We have a reno PS ready to merge in, but we're waiting on having our own release notes best practices documented before pushing that out | 15:24 |
| rwellum | For the trouble shooting, I filled out of a lot of this, which is 'ironic' because I have little osh experience to date - most of this was from my notes on kolla-k8s | 15:24 |
| portdirect | how much is osh specific? | 15:24 |
| portdirect | and how much is general k8s? | 15:24 |
| rwellum | So no hurt feelings if we cut stuff. | 15:24 |
| rwellum | 99% kubernetes | 15:25 |
| *** radeks has quit IRC | 15:25 | |
| rwellum | But added a section: what to do if something goes wrong, that I would expect to be more osh related of course. | 15:25 |
| mattmceuen | +1000 | 15:25 |
| *** radek__ has quit IRC | 15:25 | |
| mattmceuen | I really like that section at the end | 15:26 |
| alanmeadows | I would take this opportunity to say long-term whats needed is a crowsnest OSH chart | 15:26 |
| alanmeadows | something to look at data from k8s, cni, prometheus, OS sevices, and so on | 15:26 |
| mattmceuen | Because it will save us a lot of grief :D even if that is k8s specific, it's a quick list of what info to gather | 15:26 |
| jayahn | crownset? | 15:26 |
| alanmeadows | and provide simple checklists for end users | 15:26 |
| alanmeadows | most of this checking can be mechanized | 15:26 |
| alanmeadows | "You have the following pods in a CrashLoop: ..." | 15:27 |
| alanmeadows | @jayahn: having fun with nautical words.. a simple dashboard | 15:27 |
| mattmceuen | https://goo.gl/images/fZFwuG | 15:27 |
| jayahn | ah.. | 15:27 |
| rwellum | +1 alanmeadows - that's what I was getting at. because you can filter out so many questions this way. | 15:27 |
| tdoc | Being a new user, I think most of the stuff in there is useful, by now most of it I had figured out, but it would surely have helped to have from the start. | 15:27 |
| alanmeadows | this would be the first non-helm development effort of OSH, but it would be tremendous | 15:28 |
| mattmceuen | Since we're in brainstorming mode, it's better to err toward putting stuff in that etherpad now | 15:28 |
| mattmceuen | The trick will be curating that down to OSH documentation without getting too far into the business of hosting k8s-general docs | 15:28 |
| mattmceuen | Maybe some really key concepts, and then link out to k8s docs for more | 15:29 |
| *** slaweq has joined #openstack-meeting-5 | 15:29 | |
| *** nguyenhai93 has joined #openstack-meeting-5 | 15:29 | |
| rwellum | +1 | 15:29 |
| mattmceuen | I think we should let the troubleshooting guide material keep maturing for another week or two - just wanted to remind people it's out there and to please review / add to it | 15:30 |
| jayahn | +1 | 15:30 |
| tdoc | +1 | 15:30 |
| mattmceuen | If alanmeadows wants to turn it into a design doc for a new crowsnest, well that's one of those four opens :) | 15:30 |
| mattmceuen | https://etherpad.openstack.org/p/openstack-helm-troubleshooting | 15:30 |
| mattmceuen | thanks to rwellum, roman_g, and anyone else who's contributed so far (can't see everyone's names) | 15:31 |
| alanmeadows | We threw around the idea of simply extending cockpit, I can look into it | 15:31 |
| alanmeadows | full 360 view | 15:31 |
| mattmceuen | pete has an item on the agenda, but he's in a side convo so we'll come back to him | 15:31 |
| mattmceuen | #topic Elasticsearch S3 snapshot repos via radosgw s3 api | 15:31 |
| *** openstack changes topic to "Elasticsearch S3 snapshot repos via radosgw s3 api (Meeting topic: openstack-helm)" | 15:31 | |
| mattmceuen | @srwilkers take it away | 15:31 |
| rwellum | portdirect: can you take a look (or recomend another experienced user) at the 'what to do when something goes wrong' section, with a strong OSH bias please? | 15:32 |
| srwilkers | so this is something we talked about quite some time ago, when i first introduced curator to the elasticsearch chart | 15:32 |
| *** nguyenhai_ has quit IRC | 15:32 | |
| srwilkers | originally there was a PVC in the chart that relied on a readwritemany provisioner, that could be used to create filesystem snapshot repositories for elasticsearch | 15:32 |
| *** slaweq_ has quit IRC | 15:33 | |
| srwilkers | i think we all agreed it wasnt the best mechanism for providing this functionality, and wanted to use the s3 api for radosgw instead, since elasticsearch includes s3 snapshot repository functionality | 15:33 |
| srwilkers | https://review.openstack.org/559417 | 15:33 |
| srwilkers | there's a few things im working on adding to bring this to the finish line, but i've got it to a point that it's functional | 15:34 |
| srwilkers | im hoping to get the loose ends tied up before the end of the week | 15:34 |
| mattmceuen | that's awesome | 15:35 |
| * portdirect is back | 15:35 | |
| srwilkers | the last bit im working on adding is the ability to create an arbitrary number of snapshot repositories, which can be useful for when curator needs to manage multiple indexes | 15:35 |
| mattmceuen | Once we have the Swift chart in, that will be a secondary s3 mechanism for backups | 15:35 |
| mattmceuen | *snapshots | 15:35 |
| portdirect | does swift support s3? | 15:35 |
| srwilkers | so we can have a repository for standard log snapshots, a repository for things we may want to keep for extended periods of time, or whatever else your heart desires | 15:36 |
| mattmceuen | I haven't tried it, but read that it does | 15:36 |
| srwilkers | anyway, that's all ive got here. can expect some updated docs highlighting the current state of the lma union along with this when its ready | 15:37 |
| mattmceuen | my heart desires lots of logs | 15:37 |
| mattmceuen | Excellent - thanks for the update srwilkers | 15:37 |
| mattmceuen | portdirect: you're up | 15:37 |
| rwellum | I think you mean 'your heart will go on'.. | 15:37 |
| mattmceuen | #topic Helm-Toolkit (portdirect) | 15:37 |
| *** openstack changes topic to "Helm-Toolkit (portdirect) (Meeting topic: openstack-helm)" | 15:37 | |
| mattmceuen | don't make me start singing rwellum, I'll do it | 15:38 |
| * srwilkers grabs the pennywhistle | 15:38 | |
| * rwellum covers ears | 15:38 | |
| * jayahn think he needs to do something as well | 15:39 | |
| mattmceuen | We will come back to portdirect again :) | 15:40 |
| mattmceuen | #topic Production vs Bare Bones values.yaml | 15:40 |
| *** openstack changes topic to "Production vs Bare Bones values.yaml (Meeting topic: openstack-helm)" | 15:40 | |
| mattmceuen | alanmeadows! | 15:40 |
| jayahn | don't understand exactly what it means | 15:41 |
| alanmeadows | sorry dragged into a call | 15:41 |
| mattmceuen | want to hold off on this topic? | 15:41 |
| alanmeadows | sure, its been discussed before but I want to bring it to a wider audience | 15:41 |
| alanmeadows | we can revisit next chat | 15:42 |
| mattmceuen | ok - we will table for now. jayahn a teaser of the topic (bullet points) is in the agenda | 15:42 |
| mattmceuen | srwilkers: | 15:42 |
| mattmceuen | #topic OpenStack Exporter | 15:42 |
| *** openstack changes topic to "OpenStack Exporter (Meeting topic: openstack-helm)" | 15:42 | |
| srwilkers | well, this one couldve used some input from alanmeadows and portdirect but i'll throw it out regardless. it was pretty clear to me in vancouver that there's a real need for a solution for monitoring an openstack control plane via prometheus | 15:43 |
| srwilkers | monasca even goes as far as to mimic prometheus's functionality by providing mechanisms for scraping exporter endpoints | 15:44 |
| portdirect | and AT&T has a nice one in att-comdev? | 15:44 |
| srwilkers | bingo bango | 15:44 |
| portdirect | so - lets move it into -infra | 15:44 |
| srwilkers | portdirect: i think that's a great idea | 15:44 |
| mattmceuen | +1 | 15:44 |
| portdirect | srwilkers: its only great as it was yours | 15:45 |
| portdirect | i just stole your punchline | 15:45 |
| srwilkers | portdirect: youre making me blush | 15:45 |
| mattmceuen | srwilkers can you please collaborate w/ the author to get it into OS infra? | 15:45 |
| srwilkers | mattmceuen: sure can | 15:46 |
| mattmceuen | great | 15:46 |
| mattmceuen | alright we have portdirect -- | 15:46 |
| mattmceuen | #topic Moving of charts to their correct locations | 15:46 |
| *** openstack changes topic to "Moving of charts to their correct locations (Meeting topic: openstack-helm)" | 15:46 | |
| portdirect | so - we really need to get the charts in the right place | 15:47 |
| portdirect | it would be nice to use this an a 1st try at storybarding things? | 15:48 |
| *** wxy| has quit IRC | 15:48 | |
| portdirect | and also for newer devs to get used to the gates etc? | 15:48 |
| *** wxy| has joined #openstack-meeting-5 | 15:49 | |
| mattmceuen | Agree. The work is mentioned in the 1.0 spec and should be a good way to get involved | 15:49 |
| mattmceuen | in the code proper | 15:49 |
| portdirect | it would be fairly simple for me to do a mega ps that moved them all - but think this would be a great opportinity to get some more people working on the gates :D | 15:49 |
| portdirect | rwellum: could you help me with the storyboard side of things | 15:49 |
| portdirect | I'll have a stab at it, but expect I'll need some help | 15:50 |
| rwellum | Sure portdirect | 15:50 |
| portdirect | then once we have that people could grab to story for each chart? | 15:50 |
| mattmceuen | Yeah - let's create per-chart stories for this that account for gating, and then divide & conquer | 15:50 |
| mattmceuen | +1 | 15:50 |
| portdirect | nice | 15:50 |
| pcarver | portdirect: storybarding sounds like a nice variation. Matt can sing along with the stories. | 15:51 |
| mattmceuen | They will be ballads | 15:51 |
| portdirect | its the typo that keeps on giving | 15:51 |
| mattmceuen | we are a heroic team are we not | 15:51 |
| portdirect | my ambition is for us to become the plumbers of openstack | 15:51 |
| mattmceuen | We have 9mins and three items on agenda to go -- portdirect want to tackle helm-tk? | 15:52 |
| portdirect | ok | 15:52 |
| mattmceuen | #Topic Helm Toolkit | 15:52 |
| *** openstack changes topic to "Helm Toolkit (Meeting topic: openstack-helm)" | 15:52 | |
| portdirect | so I'm gonna try and get most of the functions in helm toolkit using maps(dicts) as inputs | 15:52 |
| portdirect | rather than the tuples we have today | 15:52 |
| portdirect | as this will help with a couple of things: | 15:53 |
| portdirect | 1) documentation | 15:53 |
| portdirect | 2) allowing greater flexibilitiy | 15:53 |
| portdirect | 3) wait for it | 15:53 |
| portdirect | ... proper unit tests | 15:53 |
| portdirect | so - as we do this i think its essential we start unit testing the helm-toolkit lib | 15:54 |
| mattmceuen | That would be a much nicer interface to htk and also UNIT TESTS! Are you thinking we should refactoring the dependent chart code as we go, or adapt the old interface htk interface around the new? | 15:54 |
| rwellum | for item in dict.iteritems(): ..... | 15:54 |
| portdirect | refactor as we go | 15:54 |
| portdirect | as we now have the gates for it :D | 15:54 |
| rwellum | There did it for you portdirect ;) jk obviously. | 15:54 |
| portdirect | I'll also work on airship and and other projects (ceph/tungsten fabric) to help them with the shift | 15:55 |
| portdirect | but overall this will put us in a much stronger place | 15:55 |
| srwilkers | +1 | 15:55 |
| portdirect | thats all i got there | 15:55 |
| mattmceuen | Awesome. Let's look for ways to spread this work out as well, since there will be a lot of it, and with some proper examples it shouldn't be too bad | 15:56 |
| mattmceuen | #topic multi-node deployer feedback | 15:56 |
| *** openstack changes topic to "multi-node deployer feedback (Meeting topic: openstack-helm)" | 15:56 | |
| mattmceuen | #rwellum go for it! | 15:56 |
| rwellum | At the summit I spoke to 2 people about OSH, who like me, they had all successfully deployed a single OSH node, but got stuck with multiple-nodes. They were following the guide - but with some confusion over the fact - is it a guide or is it a bunch of gate script(s). I recall this was a somewhat fatal error we made in kolla-k8s - whenever someone claimed is didn't work we'd point to a green Gate run and say 'it | 15:56 |
| rwellum | must be your fault'. Problem was the gate scripts were so utterly tweaked for that specific environment it wasn't always obvious how to apply it to your own. So my question is: should this work in other environments to the gate environment? And has someone experienced tried running through this from scratch lately? (And hopefully - the debugging guide will help too.) | 15:56 |
| rwellum | Hopefully answer a lot shorter than my qn. | 15:57 |
| *** yamamoto has joined #openstack-meeting-5 | 15:58 | |
| mattmceuen | rwellum can we chew on this one a bit and discuss next week? | 15:58 |
| rwellum | For sure... | 15:58 |
| srwilkers | or we can take it to the channel after the meeting too | 15:58 |
| mattmceuen | I think the answer is probably in the middle. And I also want to go thru the install guide fresh with the latest myself. | 15:59 |
| mattmceuen | It's been a couple months | 15:59 |
| mattmceuen | #topic Vitrage Chart | 15:59 |
| *** openstack changes topic to "Vitrage Chart (Meeting topic: openstack-helm)" | 15:59 | |
| mattmceuen | 1 min left :) | 15:59 |
| rwellum | I know we're tight on time... | 15:59 |
| mattmceuen | probably can't do this justice but trying... | 15:59 |
| rwellum | Basically my Mothership did Vitrage and it would be a good way of getting some developers into OSH by producign the chart. | 16:00 |
| rwellum | Was going to have a crack at it | 16:00 |
| mattmceuen | That will be really awesome. | 16:00 |
| portdirect | nice | 16:00 |
| rwellum | So it's a good candidate then? | 16:00 |
| srwilkers | rwellum: thats awesome. we'd be happy to provide any feedback along the way | 16:00 |
| rwellum | Cool beans then | 16:00 |
| portdirect | rwellum: if a dev wants to work on it | 16:00 |
| mattmceuen | Eagerly looking fw to helping with reviews on that - let us know if there is anything we can help with getting that going | 16:00 |
| portdirect | its a good candidate :D | 16:00 |
| mattmceuen | alright we're over time, great meeting all! | 16:01 |
| mattmceuen | #endmeeting | 16:01 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 16:01 | |
| openstack | Meeting ended Tue Jun 5 16:01:13 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:01 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-06-05-15.00.html | 16:01 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-06-05-15.00.txt | 16:01 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-06-05-15.00.log.html | 16:01 |
| *** gmmaha has left #openstack-meeting-5 | 16:01 | |
| *** yamamoto has quit IRC | 16:03 | |
| *** gagehugo has left #openstack-meeting-5 | 16:03 | |
| *** slaweq_ has joined #openstack-meeting-5 | 16:05 | |
| *** slaweq has quit IRC | 16:09 | |
| *** slaweq_ is now known as slaweq | 16:09 | |
| *** tdoc has left #openstack-meeting-5 | 16:09 | |
| *** sshank has joined #openstack-meeting-5 | 16:44 | |
| *** yamamoto has joined #openstack-meeting-5 | 16:50 | |
| *** yamamoto has quit IRC | 17:00 | |
| *** slaweq has quit IRC | 17:04 | |
| *** slaweq has joined #openstack-meeting-5 | 17:04 | |
| *** radeks has joined #openstack-meeting-5 | 17:04 | |
| *** wxy| has quit IRC | 17:11 | |
| *** sshank has quit IRC | 17:13 | |
| *** radeks has quit IRC | 17:15 | |
| *** spiette has quit IRC | 17:17 | |
| *** sshank has joined #openstack-meeting-5 | 17:19 | |
| *** spiette has joined #openstack-meeting-5 | 17:27 | |
| *** yamahata has joined #openstack-meeting-5 | 17:27 | |
| *** jamesgu has joined #openstack-meeting-5 | 17:42 | |
| *** jgu_ has quit IRC | 17:44 | |
| *** yamamoto has joined #openstack-meeting-5 | 17:56 | |
| *** yamamoto has quit IRC | 18:02 | |
| *** radeks has joined #openstack-meeting-5 | 18:38 | |
| *** sshank has quit IRC | 18:55 | |
| *** yamamoto has joined #openstack-meeting-5 | 18:58 | |
| *** yamamoto has quit IRC | 19:03 | |
| *** radeks has quit IRC | 19:11 | |
| *** radeks has joined #openstack-meeting-5 | 19:19 | |
| *** radeks has quit IRC | 19:25 | |
| *** mjturek has quit IRC | 19:38 | |
| *** yamamoto has joined #openstack-meeting-5 | 19:59 | |
| *** yamamoto has quit IRC | 20:05 | |
| *** joe_w has joined #openstack-meeting-5 | 20:44 | |
| *** mjturek has joined #openstack-meeting-5 | 20:48 | |
| *** yamamoto has joined #openstack-meeting-5 | 21:01 | |
| *** yamamoto has quit IRC | 21:05 | |
| *** slaweq has quit IRC | 21:10 | |
| *** yamamoto has joined #openstack-meeting-5 | 22:02 | |
| *** yamamoto has quit IRC | 22:06 | |
| *** mjturek has quit IRC | 22:55 | |
| *** yamamoto has joined #openstack-meeting-5 | 23:03 | |
| *** yamamoto has quit IRC | 23:07 | |
| *** hongbin has quit IRC | 23:27 | |
| *** jamesgu has quit IRC | 23:45 | |
| *** ricolin has joined #openstack-meeting-5 | 23:52 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!