Thursday, 2017-01-19

*** david-lyle has quit IRC00:05
*** rainya has quit IRC00:08
*** valw has joined #craton00:48
*** harlowja has joined #craton00:52
*** Syed__ has quit IRC01:35
*** VW has joined #craton02:09
*** valw has quit IRC02:11
*** izaakk_ has joined #craton02:34
*** jimbaker` has joined #craton02:41
*** jimbaker has quit IRC02:41
*** wirehead_ has quit IRC02:41
*** izaakk has quit IRC02:41
*** izaakk_ is now known as izaakk02:42
*** wirehead_ has joined #craton03:04
*** VW has quit IRC03:38
*** valw has joined #craton03:49
*** valw has quit IRC04:03
suloo/10:18
*** acabot has quit IRC13:43
*** valw has joined #craton14:42
*** valw has quit IRC15:17
*** valw has joined #craton15:18
*** VW has joined #craton15:20
*** VW has quit IRC15:21
*** valw has quit IRC15:22
*** valw has joined #craton15:22
*** VW has joined #craton15:22
*** jovon has joined #craton15:48
jimbaker`sulo, o/15:53
jimbaker`sulo, i started putting together an agenda for today's meeting, https://etherpad.openstack.org/p/craton-meetings - just barebones, we can add in advance of today's meeting15:54
jimbaker`which again will be here on #craton in just over 1 hour15:54
*** jimbaker` is now known as jimbaker15:56
*** jimbaker has quit IRC15:56
*** jimbaker has joined #craton15:56
*** ChanServ sets mode: +o jimbaker15:56
*** Syed__ has joined #craton15:58
*** david-lyle has joined #craton16:06
*** valw has quit IRC16:12
*** valw has joined #craton16:21
*** valw has quit IRC16:26
*** VW has quit IRC16:36
*** valw has joined #craton16:46
*** david-lyle has quit IRC16:55
*** farid has joined #craton16:59
*** rainya has joined #craton17:00
jimbakerjovon, sigmavirus, sulo, Syed__, let's kick off today's meeting17:02
jimbakertojuvone, ^^^17:02
jimbakeragenda can be found in https://etherpad.openstack.org/p/craton-meetings17:02
* sigmavirus wonders17:02
sigmavirus#startmeeting craton17:03
openstackMeeting started Thu Jan 19 17:03:00 2017 UTC and is due to finish in 60 minutes.  The chair is sigmavirus. Information about MeetBot at http://wiki.debian.org/MeetBot.17:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:03
sigmavirusOh wow17:03
openstackThe meeting name has been set to 'craton'17:03
sigmavirusit will work17:03
sigmavirus#chair sulo jimbaker17:03
openstackCurrent chairs: jimbaker sigmavirus sulo17:03
sigmavirus#link https://etherpad.openstack.org/p/craton-meetings17:03
sigmavirus#info Today's agenda is available on https://etherpad.openstack.org/p/craton-meetings17:03
jimbakersigmavirus, nice, we have meetbot supprt here as well. didn't realize that17:04
jimbakersigmavirus, so i assume your WIP pagination is just that, a chance for us to get an early peek at your progress on that change17:05
sigmavirusjimbaker: I'm thinking of breaking that change up into more discrete parts17:06
sigmavirusAnd there's more after that17:06
sigmavirusI need to completely change the format of the list responses per the spec17:06
jimbakersigmavirus, makes sense. i think the only here that would be nice if you want us to look at WIP is to just note in the summary what is done, what is still being worked on17:07
sigmavirusI thought I had added that but perhaps not17:07
jimbakersigmavirus, there's a summary. is all the functionality noted there implemented?17:08
sigmavirusYes17:08
sigmavirusI haven't given it a real test yet though17:08
jimbakerfwiw, i do like the github approach which allows this stuff to be checked off17:08
sigmavirusjimbaker: yeah, I think I'll create bugs for each item for the bp and link them together17:08
sigmavirusthat might satisfy that for you17:08
jimbakerbut github whining is not so relevant. unless storyboard really is a thing; and they're duplicating that functionality ;)17:09
jimbakersigmavirus, yeah sounds good, we do have that functionality in launchpad to support this aspect17:10
sigmavirusAlso, you don't want to hear me complain about all the things wrong with Github currently17:10
jimbakerand however its gets reported up in gerrit. or something like that. hopefully. ;)17:10
sigmavirusIt's a long list17:10
jimbakersigmavirus, sure, github has its own issues. but perhaps someone built a usable api to github to help resolve at least some of these problems...17:11
sigmavirusDon't look at me17:12
jimbakerexcept for solutions17:12
jimbaker:)17:13
jimbakerso that was very much about process. anything you want to add here on pagination itself?17:13
jimbakerlet's move on then17:14
jimbakersigmavirus, any update on the global reqs stuff? i assume we are just working through that process now that it's been approved17:15
sigmavirusjimbaker: so I need to catch up with Andreas to see if in fact that issue is now fixed17:15
sigmavirusIt should be with teh Flask-Restful merge17:16
jimbakersigmavirus, sounds good. yeah, looks like just some minor that can be easily resolved17:16
sigmavirusjimbaker: also, warning that I'm in 3 IRC meetings at the same time17:16
sigmavirusAttention might be slightly split =P17:16
jimbakersigmavirus, i like to joke about myself that i'm a poorly implemented select loop. but perhaps we all are? ;)17:17
sigmavirusjimbaker: that's a twisted joke17:18
sigmavirus;)17:18
jimbakeri'm not going to react about that17:18
jimbakerok, we children must quiet down17:19
jimbakersulo, so do you have your functional test work in with the set of changes for review?17:20
*** VW has joined #craton17:20
jimbakersulo might be out at this time. we will table functional testing and workflow support until end of this meeting (or later)17:21
sigmavirusheh17:21
jimbakeri have one more item on the agenda, which is auditing (and more generally governance)17:22
jimbakersigmavirus, you missed more interminable discussion by jimbaker on rbac on tues17:22
sigmavirusjimbaker: speaking of ourselves in teh third person now? sigmavirus is confused17:23
sigmavirusbut yeah, I couldn't make that meeting, sorry17:23
jimbakersuffice to say it's going slowly. we also discussed secrets (where we decided to investigate backend storage, say by hashicorp vault)17:23
jimbakersigmavirus, apparently i'm more prone to levity in an irc meeting than in vidyo. surely this argues for keeping this format?17:24
sigmavirusI'm in favor of that17:24
sigmavirusI think my levity is better received in this format too17:25
sigmavirusBut yeah, rbac was not something I expected to move quickly17:25
jimbakeryeah, i think we got most of the pieces worked out at this time, but still need to assemble. first in spec, then in a series of changes17:25
*** VW has quit IRC17:26
jimbakeri do think the discussion on secrets was extremely promising17:26
*** VW has joined #craton17:26
jimbakerbecause sulo suggested a direction where we would write much less code. and therefore more likely to get it right. to be seen17:27
jimbakersigmavirus, one last thing from that meeting which is worthwhile catching up here because it gets in an more accessible format (text!)17:28
jimbakerwe discussed namespaces for variables17:28
*** david-lyle has joined #craton17:28
jimbakeri suggested we will need support for namespacing as we put more things in variables, such as secrets, or virtualized variables, or setting up plugins17:29
jimbakereg ssh/id_ecdsa or nova/blah-blah or plugin/nova, etc - to be distinguished from say ansible vars which either go in a default namespace; or possible in ansible/17:30
jimbakerthis could just be convention - the keys don't care if they contain / or other chars. but we could also provide explicit support. anyway, heads up that i will propose such a spec17:31
jimbakerfor such explicit support17:31
jimbakerok, enough on that, unless sigmavirus or others here you have questions17:32
sigmavirusI'm curious what that will look like17:33
sigmavirusSo I'll reserve thoughts until I have something a bit more concrete17:33
jimbakersigmavirus, ok, you asked :)17:33
sigmavirushah17:33
sigmavirusWasn't asking for more details now17:33
*** VW has quit IRC17:34
jimbakersure. let's just say then that i think it could be part of the variable query for REST; and that we could provide namespace manipulations similar to python (because they are reasonably comprehensive); and necessarily there would be client impact17:34
*** VW has joined #craton17:34
jimbakerto use all of the goodness17:34
jimbakerbut sure, please reserve judgment for now17:35
jimbakerconvention will work for the time being at least17:35
jimbakermaybe that suggests 2 specs? 1) convention; 2) specific support from craton17:35
jimbakeranyway, i bring these things up because we have a mandate to support some requirements, and functionality like virtualized variables, secrets, and rbac help support these reqs17:37
jimbakerauditing is something we have discussed, but not recently17:37
jimbakerand it's an important requirement for us to address, especially because it enters into compliance reqs that customers have17:38
sigmavirusyep17:38
jimbakerso the relevant bug here is https://bugs.launchpad.net/craton/+bug/1606884, which needs to be expanded out into a blueprint and corresponding spec(s)17:39
openstackLaunchpad bug 1606884 in craton "Variables should support governance" [Undecided,New] - Assigned to Jim Baker (jimbaker)17:39
jimbakerby expansion i mean there are other entities that need auditing17:39
jimbakerit's possible that governance can mean just rbac + auditing. or it can mean integration with some workflow17:40
jimbakerprocess workflow, not audit/remediate workflows. but wait, that's a double usage ;)17:40
jimbakeralso a double usage17:40
jimbakerahh, imprecision in language17:40
jimbakeranyway, i like the idea of the linked repo, https://github.com/NerdWalletOSS/versionalchemy17:41
* jimbaker always seem to go for a higher abstraction that might solve multiple problems, vs something just focused on say variables17:42
jimbakerhaving said that, variables do seem special. and also much simpler than being able to track other changes17:42
jimbakerconsider showing history. that seems quite important - to know that this variable had this setting, it was changed by some principal on some time17:44
jimbakerso i do think we should have specific support here for variables. then look at other types of auditing as a future next step17:45
jimbakersigmavirus, thoughts?17:45
jimbakersulo, are you around?17:45
*** valw has quit IRC17:46
*** rainya_ has joined #craton17:46
jimbakeri see that as thundering feedback for jimbaker to explore further; and report back17:47
jimbakerwe have reached the end of our agenda. anything else before i gavel this meeting to a close?17:47
jimbakerseeing none17:48
jovonno additions17:48
jimbaker#endmeeting17:48
openstackMeeting ended Thu Jan 19 17:48:07 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-01-19-17.03.html17:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-01-19-17.03.txt17:48
openstackLog:            http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-01-19-17.03.log.html17:48
jimbakerthanks everyone!17:48
*** rainya has quit IRC17:48
Syed__thanks17:48
Syed__Been playing with solo's functional testing, till now it works fine. need to do few more test and then will post review17:49
*** valw has joined #craton18:00
*** valw has quit IRC18:01
*** valw has joined #craton18:01
sigmavirussorry, I got distracted with other priorities18:02
*** valw has quit IRC18:03
*** valw has joined #craton18:14
*** david-lyle has quit IRC18:18
*** valw has quit IRC18:18
*** VW has quit IRC18:23
*** VW has joined #craton18:31
*** valw has joined #craton18:56
sulohey folks, sorry for missing meeting today, had some internet problems with my provider19:09
*** VW has quit IRC19:12
*** VW has joined #craton19:13
sulosigmavirus: jimbaker: git-harry has raised some nice questions on https://review.openstack.org/#/c/421337/2 .. if you could spend a few queick mins on that and give your views as well i can incorporate all in next update for next round of review19:14
*** valw has quit IRC19:15
suloits a big topic so i am expecting a few rounds of fixing on that spec19:18
*** VW has quit IRC19:21
*** VW has joined #craton19:22
*** valw has joined #craton19:24
*** valw has quit IRC19:29
*** david-lyle has joined #craton19:48
*** valw has joined #craton19:56
jimbakersulo, sounds good. and agreed about expected multiple rounds20:32
*** thomasem has joined #craton20:42
*** VW has quit IRC21:08
*** VW has joined #craton21:29
*** jovon has quit IRC21:30
*** david-lyle has quit IRC21:35
*** david-lyle has joined #craton21:39
*** david-lyle has quit IRC21:39
*** david-lyle has joined #craton21:39
*** valw has quit IRC21:43
*** valw has joined #craton21:46
*** valw has quit IRC22:03
sulo:(( https://bugs.launchpad.net/craton/+bug/165790522:52
openstackLaunchpad bug 1657905 in craton "delete host fails with foreign key constraint error" [High,New]22:52
*** david-lyle has quit IRC23:03
*** wirehead_ has quit IRC23:49
*** wirehead_ has joined #craton23:50

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