Tuesday, 2018-04-24

*** hoangcx has quit IRC00:30
*** spzala has joined #openstack-meeting-500:49
*** spzala has quit IRC01:13
*** yamahata has quit IRC01:26
*** spzala has joined #openstack-meeting-501:52
*** spzala has quit IRC01:57
*** zhipeng has joined #openstack-meeting-502:03
*** zhipeng has quit IRC02:17
*** ricolin has joined #openstack-meeting-502:25
*** spzala has joined #openstack-meeting-502:34
*** spzala has quit IRC02:48
*** yamamoto has quit IRC02:53
*** yamamoto has joined #openstack-meeting-502:54
*** yamamoto has quit IRC02:59
*** ianychoi has quit IRC04:02
*** ianychoi has joined #openstack-meeting-504:04
*** ianychoi has quit IRC04:28
*** markvoelker has quit IRC04:29
*** ianychoi has joined #openstack-meeting-504:31
*** slaweq has joined #openstack-meeting-504:39
*** slaweq has quit IRC04:47
*** MarkBaker has quit IRC06:07
*** markvoelker has joined #openstack-meeting-506:30
*** MarkBaker has joined #openstack-meeting-506:31
*** slaweq has joined #openstack-meeting-506:32
*** slaweq has quit IRC06:42
*** ianychoi has quit IRC07:00
*** markvoelker has quit IRC07:04
*** ianychoi has joined #openstack-meeting-507:11
*** slaweq has joined #openstack-meeting-507:16
*** zhipeng has joined #openstack-meeting-507:40
*** spzala has joined #openstack-meeting-507:53
*** spzala has quit IRC07:57
*** markvoelker has joined #openstack-meeting-508:01
*** zhipeng has quit IRC08:10
*** markvoelker has quit IRC08:34
*** derekh has joined #openstack-meeting-508:41
*** MarkBaker has quit IRC08:42
*** radeks has joined #openstack-meeting-508:48
*** ricolin_ has joined #openstack-meeting-509:01
*** ricolin has quit IRC09:04
*** ricolin_ has quit IRC09:25
*** markvoelker has joined #openstack-meeting-509:31
*** markvoelker has quit IRC10:06
*** markvoelker has joined #openstack-meeting-511:02
*** markvoelker has quit IRC11:36
*** mjturek has joined #openstack-meeting-511:37
*** mjturek has quit IRC11:39
*** spzala has joined #openstack-meeting-511:53
*** spzala has quit IRC11:57
*** yamamoto has joined #openstack-meeting-512:14
*** markvoelker has joined #openstack-meeting-512:16
*** portdirect has quit IRC12:36
*** portdirect has joined #openstack-meeting-512:36
*** mjturek has joined #openstack-meeting-512:38
*** felipemonteiro__ has joined #openstack-meeting-512:52
*** spzala has joined #openstack-meeting-512:53
*** spzala has quit IRC12:57
*** spzala has joined #openstack-meeting-513:26
*** yamamoto has quit IRC13:28
*** yamamoto has joined #openstack-meeting-513:28
*** jbryce has quit IRC13:37
*** jbryce has joined #openstack-meeting-513:37
*** rwellum has quit IRC13:39
*** rwellum has joined #openstack-meeting-513:39
*** hoangcx has joined #openstack-meeting-513:50
*** felipemonteiro__ has quit IRC13:57
*** felipemonteiro__ has joined #openstack-meeting-513:57
*** hongbin_ has joined #openstack-meeting-513:59
*** annp has joined #openstack-meeting-514:00
*** yamahata has joined #openstack-meeting-514:04
*** hoangcx has quit IRC14:09
*** d|k has joined #openstack-meeting-514:11
*** JawonChoo has joined #openstack-meeting-514:14
*** annp has quit IRC14:16
*** annp has joined #openstack-meeting-514:16
*** JawonChoo is now known as jawonchoo14:17
*** iyamahat has joined #openstack-meeting-514:19
*** hoangcx_ has joined #openstack-meeting-514:25
*** iyamahat has quit IRC14:26
*** iyamahat has joined #openstack-meeting-514:26
*** cristicalin has joined #openstack-meeting-514:32
*** powerds0111 has quit IRC14:37
*** powerds0111 has joined #openstack-meeting-514:37
*** gagehugo has joined #openstack-meeting-514:46
*** annp has quit IRC14:57
*** hoangcx_ has quit IRC14:57
*** yamamoto has quit IRC14:58
mattmceuen#startmeeting openstack-helm15:00
openstackMeeting started Tue Apr 24 15:00:52 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
mattmceuen#topic rollcall15:00
*** openstack changes topic to " (Meeting topic: openstack-helm)"15:00
openstackThe meeting name has been set to 'openstack_helm'15:00
*** openstack changes topic to "rollcall (Meeting topic: openstack-helm)"15:00
cristicalino/15:01
gagehugoo/15:01
jawonchooo/15:01
mattmceuenagenda: https://etherpad.openstack.org/p/openstack-helm-meeting-2018-04-2415:01
mattmceuenPLease add anything you'd like to discuss15:01
*** wxy| has joined #openstack-meeting-515:02
lamto/15:02
srwilkerso/15:02
rwellumo/15:03
d|ko/15:03
*** mattmceuen has quit IRC15:03
*** mattmceuen has joined #openstack-meeting-515:04
srwilkersmatt has lost internet connection15:04
srwilkershe's coming back15:04
*** qwebirc41871 has joined #openstack-meeting-515:04
mattmceuengreat timing sorry guys :)15:04
mattmceuen#topic Vancouver Summit15:05
*** openstack changes topic to "Vancouver Summit (Meeting topic: openstack-helm)"15:05
mattmceuendo we have @jayahn in the house?15:05
mattmceuenLet's go out of order, this one was something he wanted to discuss15:06
mattmceuen#topic 1.0 timeline15:06
*** openstack changes topic to "1.0 timeline (Meeting topic: openstack-helm)"15:06
mattmceuenIt would be really great if we could reach 1.0 readiness by the Vancouver summit :)15:06
mattmceuen    https://review.openstack.org/#/c/556325/ -- definition-in-progress of 1.015:07
mattmceuenIt's not something we want to rush into tagging if we're not ready, but I think we should shoot for being ready15:07
mattmceuenwe'd discussed using storyboard as a way to coordinate this work15:08
mattmceuenrwellum, do you have a feel yet for risk / work involved with migrating?15:09
mattmceuenstoryboard is another thing we don't want to rush, but if it's low hanging fruit and ready, then we could start creating work items stat15:10
* srwilkers scurries off for coffee15:10
mattmceuenAll it takes is one mention of scope management tooling to make srwilkers run for the door15:11
rwellummattmceuen: spent a little time, but nothing conclusive yet. I have been watching Ironic  - which is the biggest project to use it so far.15:11
*** renmak_ has joined #openstack-meeting-515:11
*** renmak__ has joined #openstack-meeting-515:11
rwellumI'm off traveling this week but I'll get something out by early next if that's ok?15:11
mattmceuenYup, that would be perfect15:12
mattmceuenIf we can get the spec merged by next week, and then start entering / assigning out work items (in launchpad or storyboard as appropriate) next week, that will set us up well I think15:12
*** felipemonteiro_ has joined #openstack-meeting-515:13
mattmceuenanything else on this topic15:13
rwellumI thought the spec was really good btw15:13
* srwilkers grumbles about people leaving empty coffee pots15:13
mattmceuenAwesome, thanks rwellum15:14
mattmceuen#topic Adding ldap integration to Elasticsearch, Kibana, Grafana, Prometheus15:14
*** openstack changes topic to "Adding ldap integration to Elasticsearch, Kibana, Grafana, Prometheus (Meeting topic: openstack-helm)"15:14
mattmceuenChannel your grumpiness into some LMA for us srwilkers15:14
srwilkersso currently, elasticsearch, kibana and grafana are all just relying on basic auth15:14
srwilkerswhich is fine for kicking the tires somewhat, but doesnt necessarily provide a meaningful solution beyond that15:15
srwilkersi've been working on using the ldap chart in openstack-helm as a reference for providing authentication via ldap for those services15:15
srwilkersit required a change in the elasticsearch and kibana charts since they're using an apache reverse proxy to front those containers.  the changed involved moving the host configuration into values to verify it works15:16
srwilkersi plan on including docs on how to use it and the necessary configuration parameters to take into account when looking to use it15:16
*** felipemonteiro__ has quit IRC15:16
srwilkersi think doing it in this manner makes sense at the moment, as the values-driven model allows an operator to provide overrides to further restrict the access certain groups and users have to specific paths for those services15:17
srwilkersbut i'd also appreciate feedback on those15:17
mattmceuen    https://review.openstack.org/#/c/563270/ (grafana)15:18
mattmceuen    https://review.openstack.org/#/c/563260/ (kibana/apache)15:18
mattmceuen    https://review.openstack.org/#/c/543553/ (prometheus, basic auth first)15:18
srwilkersgrafana's got built in support for ldap, so its being handled differently.  it's just a matter of finding the appropriate binds and group mappings to use at this point i think15:18
srwilkersits not quite there yet but close15:18
srwilkersprometheus currently has no sort of auth mechanism, but ive got a patchset to add the same functionality the elasticsearch and kibana charts have15:18
mattmceuenI know the ldap integration has been an interesting journey - any outstanding questions to pose while we have everyone's eyeballs here?15:19
srwilkersthat's all i really had on it for the moment.  ive been chewing on whether ldap integration for prometheus is required15:20
srwilkersalmost thinking it just needs to be locked up, as grafana can be used to display all the pretty dashboards to anyone authorized to view them15:21
srwilkersthat does restrict access to prometheus, but ive always been skeptical of giving free reign to the prometheus endpoint to an authenticated user15:21
mattmceuenAgree15:22
srwilkersbut thats it for me15:22
mattmceuenLocking up prometheus may be a good Plan A in any case, we can always expose it with some kind of auth tie-in later if use cases come up and someone does the work :)15:22
srwilkersyeah, thats what im thinking15:22
mattmceuencool15:23
mattmceuenThanks srwilkers.15:23
mattmceuenNext one is your topic as well15:23
mattmceuen#topic Ceph radosgw s3 api for Elastic Curator15:23
*** openstack changes topic to "Ceph radosgw s3 api for Elastic Curator (Meeting topic: openstack-helm)"15:23
srwilkersthis is one of those situations where you come to hate something you introduced in the past15:23
srwilkerscurrently the elasticsearch chart supports creating a RWM backed PVC to use as a filesystem snapshot repository for ealstucsearch15:24
srwilkersi thought it'd be great to have a default mechanism for using elastic curator to take snapshots of the indices and place them in a PVC15:24
srwilkersproblem is that requires some method for provisioning RWM volumes, which may not always be an option15:25
srwilkersso to get around that, I've been working on using the s3 ceph radosgw api to provide the ability to use the s3 repository type for elasticsearch15:25
srwilkersthis brings us back in line to being able to use ceph to back our snapshot repositories, which i think is a good thing15:26
srwilkersit's been a bit touchy along the way, but im very close to having this functional in the elasticsearch chart15:26
jayahno/15:26
mattmceuenThat's awesome and thanks for sharing this in progress15:26
mattmceueno/ jay!15:26
srwilkersim also using this as a shameless plug for a blogpost, as there's not a single clear walkthrough i could find with my googlefu15:27
srwilkersso i plan on sharing what i did for anyone else looking to use the s3 rgw api in the future15:27
srwilkersthats all i had really15:28
mattmceuenSo the reason s3 radosgw > cephfs-PVC approach is because older kernels don't support cephfs, right?  Will radosgw also be better performance?15:28
srwilkerswell, thats part of it.  the alternative would be to use something like NFS, but not everyone wants to use NFS either15:28
portdirectObject storage > filesystem here15:29
srwilkersyep.  performance-wise, should be roughly the same as the bulk of the work is Elasticsearch performing the snapshots of the indices i think15:30
mattmceuencool beans15:30
srwilkersat the end, it just  dumps the compressed snapshot wherever youve pointed it at15:30
mattmceuengotcha15:30
mattmceuenjayahn you are up!15:31
jayahni am15:31
mattmceuen#topic Vancouver Summit Talks15:31
*** openstack changes topic to "Vancouver Summit Talks (Meeting topic: openstack-helm)"15:31
* srwilkers coffee scurry 2.015:31
jayahnsorry, i fall asleep....15:31
mattmceuenno problemo at all15:31
mattmceuenhttps://etherpad.openstack.org/p/openstack-helm-meeting-2018-04-2415:31
mattmceuenI can start :)15:31
*** spsurya has quit IRC15:31
*** spsurya has joined #openstack-meeting-515:32
mattmceuenFor the talk I have w/ you and Seungkyu - I have a draft ppt to share with you, will get it in your inbox for tomorrow morning15:32
jayahnvancouver summit15:32
jayahngreat!15:32
mattmceuenIt's a lightning talk, I probably already have too many slides :D  let's drink lots of coffee first15:32
jayahn:)15:33
mattmceuenOk -- workshop talk, want to share your thoughts?15:33
jayahnyeah 10 min talk15:33
jayahnhands-on workshop15:33
jayahncertainly we need more people assisting workshop, and I would like to have one of "native" english speaker to lead "presentation" part of workshop.15:34
* jayahn try to decide if pete is native or its own kind. :)15:34
jayahnfor actual hands-on demo,15:35
jayahnopenstack-helm deployment + lma deployment would be basic step to do.15:36
jayahnI would like to ask if we need to do version update as a part of hands-on.15:36
mattmceuenI think version update would be pretty powerful15:37
jayahnthen, we need to decide from which to which15:37
mattmceuenThinking back to what we did last time vs what we could do this time - would be great to get some snazzy new things in there so we're not repeating ourselves15:37
mattmceuenLMA is a great add in that regard15:37
mattmceuenHow about newton->ocata?15:38
jayahnbut, newton is pretty old one.15:38
mattmceuen(LMA: let's actually have them log into grafana)15:38
mattmceuenThere are two arguments to made for versions -- 1) newton->ocata is really good because that's what we'll be gating for 1.0.  2) ocata->(newer) would be a good preview of the fact that OSH works well with newer versions, even thought the gates haven't caught up yet15:39
jayahnyeap.15:40
jayahnexactly15:40
mattmceuenThe version that we upgrade to should be something we're pretty comfortable with I think15:40
jayahn1) vs 2) what you guys think?15:40
mattmceuenBecause folks will take the scripts home and use them for standing things up15:40
srwilkersI’m comfortable with 1. That’s my take though15:41
rwellumI agree stick to the 1.0 deliverable.15:42
jayahnokay.15:42
mattmceuenI think #1 is good, along with a spoken note that we are targeting Newton & Ocata for 1.0, and that our next order of business post-1.0 will be to gate newer versions of OpenStack (which largely already work with OSH)15:43
mattmceuenOne more reason to have 1.0 ready by Vancouver if possible :)15:43
mattmceuenPete is multitasking right now, but Im sure he'll be good with speaking based on conversations I've had with him15:44
jayahnthen, we probably need to describe very well about openstack-helm chart being independent from openstack versions. we can surely support newer versions of openstack.15:44
mattmceuenGood idea.  a brief sugar cube diagram :)15:45
jayahni really don't want to give a negative feeling about openstack-helm being only capable of deploying old openstack.15:45
jayahnsugar cube diagram!15:45
jayahnlove it.15:45
rwellum+115:46
mattmceuenWould it be possible to get overrides created for newer versions, and ideally experimental gates for them too, by then?15:46
jayahni think it is matter of minute to add experimental gates for ocata, probably for much newer ones.15:47
jayahnpersonally, i think ocata to pike is very doable. :)15:48
mattmceuenThat's excellent, and agree 100% on Pike doability.  With gates in place I'd feel much more comfortable promoting Ocata->Pike.15:48
jayahnbut, also agrees on reason to pick #115:48
mattmceuenwell #1 can be fallback in any case15:49
jayahnsure thing. :)15:49
mattmceuenShould just be a matter of switching the overrides file15:49
*** felipemonteiro_ has quit IRC15:49
mattmceuenDo we have a solution planned for the VMs for the workshop?15:49
jayahnyeap15:49
*** felipemonteiro_ has joined #openstack-meeting-515:49
rwellumI almost feel you guys should consider skipping a release - jump straight to Queens. I mean you're not 1.0 yet - so can assume that customers coming onboard post 1.0 will want the latest?15:50
mattmceuenwoooot jayahn15:50
jayahnthat is very good and serious question15:50
mattmceuenpost-1.0 will definitely want the latest15:50
jayahnnope. my "yeap" is a bit late typing answer15:50
jayahnnot to your VM question15:50
portdirectwe need to get them sorted asap15:51
portdirectas without this the workshop is dead in the water.15:51
jayahni know.15:51
jayahnI will try to find "VM donors" more, but15:52
jayahndo you guys have any potential sponsor?15:52
rwellumSometime OS infra provides resources?15:52
srwilkersrwellum: i'd like to see something like the version used in the user survey.  i wouldnt necessarily assume everyones wanting to use latest15:53
mattmceuenWe don't have any approval for funding the VMs or other sponsors identified, do you have any ideas for sponsors?15:54
mattmceuensrwilkers developers want to be running the latest on their laptops, that much is true :)15:54
mattmceuenBut good point - from a prod perspective definitely not, and that's why the 1.0 / post-1.0 distinction is important15:55
rwellumsrwilkers: agreed. But other projects are caught up (kolla-ansible) etc - and my company are on queens right now - so to pitch them osh I personally need the latest. But I know that's just one voice.15:55
srwilkersmattmceuen: nothing wrong with that, we'll get there.  just cant see those wanting to use this in a prod like environment wanting to use latest15:55
jayahnskt currently does not have a good public cloud service. most of things are internal usage only. getting VMs with public internal access is damn hard.15:55
portdirectwe also need a decent level of iops15:56
jayahnis it possible to show "some company's logo" on our hands-on demo slide?15:56
jayahnIf that company provides VMs?15:56
rwellumQuick change to Horizon is easy15:56
portdirectlast we need a min spec of: 30gb Ram, 4vCPU, 80Gb GP2 SSD15:56
rwellumjayahn: ^^^15:57
portdirectbefore we discuss branding - and of course we can15:57
portdirectlets get the hw issue resolved15:57
jayahni am trying to get my weapon to get VM sponsors :)15:57
portdirectit was approx $600 for AWS last time15:58
mattmceuenat the last summit, we used a public cloud provider behind the scenes, and the only branding was AT&T & SKT as far as I remember :)15:58
* mattmceuen super secret public cloud provider there15:58
rwellumSorry - just want to repeat - in previous workshops I think OpenStack Infra has provided some resources? Maybe just imagining this.15:58
mattmceuenI didn't realize that rwellum15:59
portdirectOVH has typically in the past15:59
mattmceuenyikes, lost track of time15:59
jayahn1 min left for the meeing15:59
mattmceuent-minus one minute15:59
*** yamamoto has joined #openstack-meeting-515:59
portdirectthough i think we may have missed the window there? though worth checkinh15:59
mattmceuenGoing to have to table - feel free to continue discussin in the chat room!15:59
rwellumAny chance on getting a +W for: https://review.openstack.org/#/c/562097/ ? :)15:59
mattmceuen#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:59
openstackMeeting ended Tue Apr 24 15:59:50 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-04-24-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-04-24-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-04-24-15.00.log.html15:59
srwilkersdone15:59
rwellumty16:00
mattmceuenthanks all!16:00
*** gagehugo has left #openstack-meeting-516:00
jayahnso back to osh channel?16:00
*** yamamoto has quit IRC16:04
*** iyamahat has quit IRC16:10
*** yamahata has quit IRC16:15
*** cristicalin has quit IRC16:16
*** felipemonteiro__ has joined #openstack-meeting-516:59
*** yamamoto has joined #openstack-meeting-517:00
*** felipemonteiro__ has quit IRC17:01
*** derekh has quit IRC17:01
*** felipemonteiro__ has joined #openstack-meeting-517:01
*** felipemonteiro_ has quit IRC17:02
*** felipemonteiro has joined #openstack-meeting-517:03
*** iyamahat has joined #openstack-meeting-517:03
*** yamamoto has quit IRC17:06
*** felipemonteiro__ has quit IRC17:06
*** felipemonteiro_ has joined #openstack-meeting-517:17
*** felipemonteiro has quit IRC17:20
*** wxy| has quit IRC17:40
*** wxy| has joined #openstack-meeting-517:40
*** sshank has joined #openstack-meeting-517:43
*** cristicalin has joined #openstack-meeting-517:46
*** cristicalin has quit IRC17:47
*** sshank has quit IRC17:50
*** wxy| has quit IRC17:55
*** yamamoto has joined #openstack-meeting-518:03
*** yamamoto has quit IRC18:08
*** ianychoi has quit IRC18:26
*** iyamahat has quit IRC18:26
*** ianychoi has joined #openstack-meeting-518:26
*** jawonchoo has quit IRC18:33
*** jawonchoo has joined #openstack-meeting-518:33
*** jawonchoo has quit IRC18:38
*** felipemonteiro__ has joined #openstack-meeting-518:39
*** felipemonteiro_ has quit IRC18:39
*** dims has quit IRC19:02
*** yamahata has joined #openstack-meeting-519:04
*** yamamoto has joined #openstack-meeting-519:04
*** iyamahat has joined #openstack-meeting-519:05
*** dims has joined #openstack-meeting-519:09
*** yamamoto has quit IRC19:10
*** radeks has quit IRC19:14
*** ianychoi has quit IRC19:39
*** ianychoi has joined #openstack-meeting-519:41
*** renmak__ has quit IRC19:43
*** renmak_ has quit IRC19:43
*** jawonchoo has joined #openstack-meeting-520:03
*** ianychoi has quit IRC20:05
*** yamamoto has joined #openstack-meeting-520:06
*** jawonchoo has quit IRC20:08
*** ianychoi has joined #openstack-meeting-520:09
*** yamamoto has quit IRC20:11
*** slaweq has quit IRC20:25
*** slaweq has joined #openstack-meeting-520:26
*** iyamahat has quit IRC20:28
*** yamahata has quit IRC20:29
*** spzala has quit IRC20:32
*** spzala has joined #openstack-meeting-520:32
*** spzala has quit IRC20:34
*** ianychoi has quit IRC20:39
*** ianychoi has joined #openstack-meeting-520:40
*** iyamahat has joined #openstack-meeting-520:50
*** iyamahat_ has joined #openstack-meeting-520:50
*** iyamahat has quit IRC20:55
*** jawonchoo has joined #openstack-meeting-520:58
*** jawonchoo has quit IRC21:02
*** yamamoto has joined #openstack-meeting-521:08
*** yamahata has joined #openstack-meeting-521:09
*** yamamoto has quit IRC21:14
*** slaweq has quit IRC21:14
*** sshank has joined #openstack-meeting-521:15
*** slaweq has joined #openstack-meeting-521:15
*** slaweq has quit IRC21:20
*** ianychoi has quit IRC21:24
*** ianychoi has joined #openstack-meeting-521:25
*** ianychoi has quit IRC21:35
*** ianychoi has joined #openstack-meeting-521:36
*** ianychoi has quit IRC22:02
*** ianychoi has joined #openstack-meeting-522:04
*** yamamoto has joined #openstack-meeting-522:09
*** yamamoto has quit IRC22:14
*** sshank has quit IRC22:22
*** jawonchoo has joined #openstack-meeting-522:46
*** jawonchoo has quit IRC22:50
*** yamamoto has joined #openstack-meeting-523:10
*** felipemonteiro__ has quit IRC23:16
*** yamamoto has quit IRC23:16
*** jawonchoo has joined #openstack-meeting-523:19
*** jawonchoo has quit IRC23:23
*** hongbin_ has quit IRC23:33
*** mjturek has quit IRC23:42
*** yamamoto has joined #openstack-meeting-523:58

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