Thursday, 2017-09-28

*** lukebrowning has joined #openstack-tc00:01
*** kumarmn has joined #openstack-tc00:03
*** lukebrowning has quit IRC00:05
*** lukebrowning has joined #openstack-tc00:07
*** tonyb has joined #openstack-tc00:10
*** lukebrowning has quit IRC00:11
tonybttx: Has the election config been approved? can we +W https://review.openstack.org/#/c/506310/ ?00:11
*** lukebrowning has joined #openstack-tc00:13
*** lukebrowning has quit IRC00:18
*** kumarmn has quit IRC00:19
*** lukebrowning has joined #openstack-tc00:19
*** kumarmn has joined #openstack-tc00:19
*** kumarmn has quit IRC00:19
*** kumarmn has joined #openstack-tc00:20
*** lukebrowning has quit IRC00:24
*** kumarmn has quit IRC00:33
*** kumarmn has joined #openstack-tc00:34
*** kumarmn has quit IRC00:37
*** kumarmn has joined #openstack-tc00:37
*** lukebrowning has joined #openstack-tc00:45
*** lukebrowning has quit IRC00:50
*** lukebrowning has joined #openstack-tc00:51
*** lukebrowning has quit IRC00:56
*** lukebrowning has joined #openstack-tc01:05
*** lukebrowning has quit IRC01:09
*** lukebrowning has joined #openstack-tc01:11
*** lukebrowning has quit IRC01:16
*** lukebrowning has joined #openstack-tc01:18
*** lukebrowning has quit IRC01:22
*** lukebrowning has joined #openstack-tc01:24
*** lukebrowning has quit IRC01:28
*** lukebrowning has joined #openstack-tc01:30
*** gcb has joined #openstack-tc01:31
*** kumarmn has quit IRC01:32
*** kumarmn has joined #openstack-tc01:33
*** kumarmn has quit IRC01:37
*** lukebrowning has quit IRC01:41
*** lukebrowning has joined #openstack-tc01:43
*** lukebrowning has quit IRC01:48
*** lukebrowning has joined #openstack-tc01:49
*** lukebrowning has quit IRC01:54
*** lukebrowning has joined #openstack-tc01:56
*** lukebrowning has quit IRC02:00
*** lukebrowning has joined #openstack-tc02:02
*** sdague has quit IRC02:05
*** lukebrowning has quit IRC02:07
*** lukebrowning has joined #openstack-tc02:08
*** lukebrowning has quit IRC02:13
*** lukebrowning has joined #openstack-tc02:14
*** lukebrowning has quit IRC02:19
*** lukebrowning has joined #openstack-tc02:21
*** lukebrowning has quit IRC02:25
*** lukebrowning has joined #openstack-tc02:32
*** lukebrowning has quit IRC02:37
*** lukebrowning has joined #openstack-tc02:38
*** lukebrowning has quit IRC02:43
*** rosmaita has quit IRC02:44
*** lukebrowning has joined #openstack-tc02:45
*** lukebrowning has quit IRC02:49
*** Rockyg has joined #openstack-tc02:50
*** lukebrowning has joined #openstack-tc02:51
*** lukebrowning has quit IRC02:56
*** lukebrowning has joined #openstack-tc02:57
*** kumarmn has joined #openstack-tc02:59
*** lukebrowning has quit IRC03:02
*** lukebrowning has joined #openstack-tc03:03
*** lukebrowning has quit IRC03:08
*** lukebrowning has joined #openstack-tc03:10
*** lukebrowning has quit IRC03:14
*** lukebrowning has joined #openstack-tc03:16
*** lukebrowning has quit IRC03:20
*** lukebrowning has joined #openstack-tc03:22
*** lukebrowning has quit IRC03:27
*** tdasilva has quit IRC03:53
*** kumarmn has quit IRC03:58
*** tdasilva has joined #openstack-tc04:11
*** lukebrowning has joined #openstack-tc04:23
*** lukebrowning has quit IRC04:35
*** lukebrowning has joined #openstack-tc04:37
*** lukebrowning has quit IRC04:41
*** Rockyg has quit IRC04:42
*** lukebrowning has joined #openstack-tc04:43
*** lukebrowning has quit IRC04:52
*** lukebrowning has joined #openstack-tc04:54
*** kumarmn has joined #openstack-tc04:58
*** lukebrowning has quit IRC04:58
*** lukebrowning has joined #openstack-tc05:00
*** kumarmn has quit IRC05:02
*** lukebrowning has quit IRC05:05
*** lukebrowning has joined #openstack-tc05:15
*** lukebrowning has quit IRC05:19
*** lukebrowning has joined #openstack-tc05:21
*** lukebrowning has quit IRC05:25
*** lukebrowning has joined #openstack-tc06:06
*** lukebrowning has quit IRC06:18
*** lukebrowning has joined #openstack-tc06:20
*** lukebrowning has quit IRC06:25
*** lukebrowning has joined #openstack-tc06:26
*** kumarmn has joined #openstack-tc06:30
*** lukebrowning has quit IRC06:31
*** lukebrowning has joined #openstack-tc06:32
*** kumarmn has quit IRC06:34
*** lukebrowning has quit IRC06:37
*** lukebrowning has joined #openstack-tc06:39
*** lukebrowning has quit IRC06:43
*** lukebrowning has joined #openstack-tc06:45
*** lukebrowning has quit IRC06:49
*** lukebrowning has joined #openstack-tc06:51
*** lukebrowning has quit IRC06:56
*** lukebrowning has joined #openstack-tc06:57
ttxtonyb: I asked for review, so they had their chance to comment, consider it +107:01
*** lukebrowning has quit IRC07:02
*** lukebrowning has joined #openstack-tc07:08
*** lukebrowning has quit IRC07:12
*** lukebrowning has joined #openstack-tc07:14
*** lukebrowning has quit IRC07:19
*** lukebrowning has joined #openstack-tc07:21
*** lukebrowning has quit IRC07:25
*** lukebrowning has joined #openstack-tc07:27
*** lukebrowning has quit IRC07:31
*** lukebrowning has joined #openstack-tc07:33
*** lukebrowning has quit IRC07:38
*** lukebrowning has joined #openstack-tc07:39
*** lukebrowning has quit IRC07:44
*** jpich has joined #openstack-tc07:44
*** lukebrowning has joined #openstack-tc07:45
*** lukebrowning has quit IRC07:50
*** lukebrowning has joined #openstack-tc07:52
*** lukebrowning has quit IRC07:56
*** lukebrowning has joined #openstack-tc07:58
*** lukebrowning has quit IRC08:02
*** lukebrowning has joined #openstack-tc08:09
*** lukebrowning has quit IRC08:13
*** lukebrowning has joined #openstack-tc08:15
*** lukebrowning has quit IRC08:20
*** lukebrowning has joined #openstack-tc08:21
*** lukebrowning has quit IRC08:26
*** kumarmn has joined #openstack-tc08:31
*** lukebrowning has joined #openstack-tc08:35
*** kumarmn has quit IRC08:36
*** lukebrowning has quit IRC08:40
*** lukebrowning has joined #openstack-tc08:42
*** lukebrowning has quit IRC08:46
*** lukebrowning has joined #openstack-tc08:48
*** lukebrowning has quit IRC08:53
*** lukebrowning has joined #openstack-tc08:54
*** lukebrowning has quit IRC08:59
*** lukebrowning has joined #openstack-tc09:00
*** lukebrowning has quit IRC09:05
*** lukebrowning has joined #openstack-tc09:07
*** lukebrowning has quit IRC09:11
*** lukebrowning has joined #openstack-tc09:13
tonybttx: okay thanks.09:16
*** lukebrowning has quit IRC09:18
*** lukebrowning has joined #openstack-tc09:19
*** lukebrowning has quit IRC09:24
ttxStarted the draft on last TC membership activity / vision progress https://etherpad.openstack.org/p/jpcEHdh9eU09:29
ttxjohnthetubaguy, cdent: iirc you were interested in helping with that draft09:30
ttxI seeded it with the stuff that got merged and some of the things we discussed at the PTG09:31
*** kumarmn has joined #openstack-tc09:32
ttxwould be great to have it ready for tomorrow (or Monday) so tat we can post it next to the call for nominations09:32
*** kumarmn has quit IRC09:36
*** sdague has joined #openstack-tc09:44
johnthetubaguyttx: I should be able to take a look tomorrow09:59
*** cdent has joined #openstack-tc10:19
*** lukebrowning has joined #openstack-tc10:20
*** lukebrowning has quit IRC10:32
*** lukebrowning has joined #openstack-tc10:44
*** lukebrowning has quit IRC10:49
*** gcb has quit IRC10:50
*** lukebrowning has joined #openstack-tc10:51
*** lukebrowning has quit IRC10:55
*** lukebrowning has joined #openstack-tc10:57
*** lukebrowning has quit IRC11:01
*** lukebrowning has joined #openstack-tc11:03
*** gcb has joined #openstack-tc11:07
*** lukebrowning has quit IRC11:07
*** lukebrowning has joined #openstack-tc11:09
*** lukebrowning has quit IRC11:14
*** lukebrowning has joined #openstack-tc11:15
*** lukebrowning has quit IRC11:20
*** lukebrowning has joined #openstack-tc11:22
*** rosmaita has joined #openstack-tc11:24
*** lukebrowning has quit IRC11:26
*** lukebrowning has joined #openstack-tc11:28
*** lukebrowning has quit IRC11:32
*** kumarmn has joined #openstack-tc11:33
*** lukebrowning has joined #openstack-tc11:34
*** kumarmn has quit IRC11:38
*** lukebrowning has quit IRC11:38
*** lukebrowning has joined #openstack-tc11:40
*** lukebrowning has quit IRC11:45
*** lukebrowning has joined #openstack-tc11:51
*** lukebrowning has quit IRC11:56
*** lukebrowning has joined #openstack-tc11:57
*** lukebrowning has quit IRC12:02
*** lukebrowning has joined #openstack-tc12:04
*** lukebrowning has quit IRC12:08
*** lukebrowning has joined #openstack-tc12:10
*** gcb has quit IRC12:12
*** gcb has joined #openstack-tc12:12
*** lukebrowning has quit IRC12:14
*** lukebrowning has joined #openstack-tc12:16
*** cdent has quit IRC12:21
*** lukebrowning has quit IRC12:21
*** lukebrowning has joined #openstack-tc12:29
*** lukebrowning has quit IRC12:33
*** lukebrowning has joined #openstack-tc12:35
*** lukebrowning has quit IRC12:39
*** lukebrowning has joined #openstack-tc12:41
*** kumarmn has joined #openstack-tc12:44
*** lukebrowning has quit IRC12:46
*** kumarmn has quit IRC12:49
*** cdent has joined #openstack-tc12:51
*** lukebrowning has joined #openstack-tc12:52
*** lukebrowning has quit IRC12:57
*** gcb has quit IRC12:58
*** lukebrowning has joined #openstack-tc12:58
*** gcb has joined #openstack-tc13:02
*** lukebrowning has quit IRC13:03
*** lukebrowning has joined #openstack-tc13:04
*** kumarmn has joined #openstack-tc13:05
*** kumarmn has quit IRC13:05
*** lukebrowning has quit IRC13:09
*** lukebrowning has joined #openstack-tc13:11
*** lukebrowning has quit IRC13:15
*** lukebrowning has joined #openstack-tc13:17
*** lukebrowning has quit IRC13:21
*** lukebrowning has joined #openstack-tc13:23
*** lukebrowning has quit IRC13:28
*** lukebrowning has joined #openstack-tc13:29
ttxgetting tired of explaining to the PWG that external prioritization will never work13:31
ttx"Having a single priority list for projects" sigh13:32
cdentttx it is a bit of a broken record13:34
*** lukebrowning has quit IRC13:34
cdenthowever, that they keep doing it suggests that there’s an unstatisfied need13:34
ttxthat need is called "control without investment"13:34
cdentthere’s probably more than one13:35
*** lukebrowning has joined #openstack-tc13:36
cdentif projects weren’t as backlogged as they are the situation might be different, including in terms of barriers to investment being lower13:36
ttxcdent: btw Started the draft on last TC membership activity / vision progress https://etherpad.openstack.org/p/jpcEHdh9eU13:36
ttxICYMI in the backlog13:37
cdentah, excellent13:37
ttxwould be great to have it ready for tomorrow (or Monday) so that we can post it next to the call for nominations13:37
cdentI’ll stick it in my read queue for today13:37
*** lukebrowning has quit IRC13:40
*** lukebrowning has joined #openstack-tc13:42
*** lukebrowning has quit IRC13:47
*** lukebrowning has joined #openstack-tc13:53
*** alex_xu has quit IRC13:54
*** gcb has quit IRC13:54
*** alex_xu has joined #openstack-tc13:54
*** zhouyaguo has joined #openstack-tc13:55
*** lukebrowning has quit IRC13:58
*** lukebrowning has joined #openstack-tc13:59
*** alex_xu has quit IRC14:02
*** gcb has joined #openstack-tc14:02
*** lukebrowning has quit IRC14:03
*** lukebrowning has joined #openstack-tc14:05
*** lukebrowning has quit IRC14:10
*** lukebrowning has joined #openstack-tc14:11
*** lukebrowning has quit IRC14:16
*** lukebrowning has joined #openstack-tc14:18
*** kumarmn has joined #openstack-tc14:19
*** lukebrowning has quit IRC14:22
*** zhouyaguo has quit IRC14:24
*** lukebrowning has joined #openstack-tc14:24
*** zhouyaguo has joined #openstack-tc14:24
*** lukebrowning has quit IRC14:28
*** hongbin has joined #openstack-tc14:35
*** lukebrowning has joined #openstack-tc14:36
johnthetubaguyttx: ++ on the PWG comment14:38
*** lukebrowning has quit IRC14:40
johnthetubaguyttx: I spent a lot of time on that discussion in vancover I think it was14:41
*** lukebrowning has joined #openstack-tc14:42
cdentttx, have read through https://etherpad.openstack.org/p/jpcEHdh9eU and made one long comment, and fixed a few typos14:44
cdentit really feels like there could be more there, but I’m not sure what, which depresses me somewhat14:45
*** lukebrowning has quit IRC14:47
ttxcdent: te big thing missing is overall technical progress -- like saying how many projects are now supporting rolling upgrades or such14:47
ttxI focused on the TC direct achievements but I guess there could be space for that14:48
cdentshould we add anything about which project-wide goals were approved or completed?14:49
ttxit's a bit staggered but ye14:49
ttxs14:49
ttxI mean, the Pike goals were decided before this membership, and implemented by others14:49
cdentI guess the progressive in me wants the document to answer “how has openstack changed because of the TC” and if the answer is “not much” then I feel like a conservative and I’ve let myself down :)14:49
ttxBTW should we have a session on constellations at the Forum ?14:50
cdentgiven that we need some sessions, I would say yes14:50
ttxwe definitely need some brainstorm time around that14:50
ttxwho was interested in pushing that that we could convince to file ?14:51
ttxanything more vision-related that we should add there ?14:51
ttx"Making OpenStack more palatable to part-time contributors", maybe ?14:52
cdentit’s certainly a topic that needs discussion14:52
ttxok, I'll file that second one14:52
*** lukebrowning has joined #openstack-tc14:53
cdentI meant to think some up this week, but have been swamped, will try some more tomorrow, or maybe today’s office hour will prompt something14:54
*** lukebrowning has quit IRC14:58
*** lukebrowning has joined #openstack-tc15:00
ttxyay office hour15:01
amrithyeah15:01
amrith:)15:01
* ttx gets his ping list15:01
ttxshould really have a bot for that15:02
cdenttc-members assemble!15:03
ttxAs I mentioned earlier, at the PTG we said we should post something of a end-of-membership progress report along with the call to nominations for the TC election15:04
ttxdraft is at https://etherpad.openstack.org/p/jpcEHdh9eU for those interested in helping15:04
*** lukebrowning has quit IRC15:04
EmilienMhello15:04
ttxAlso the deadline for forum topic submission is tomorrow, so if there is anything you'd like to discuss I encourage you to post there15:05
ttxI filed a couple15:05
cdentI was going to mention LTS, but it’s already there15:06
ttxNeed one volunteer to lead Constellations brainstorming15:06
fungicount me in for the palatable to part-time contributors discussion. that's my primary reason for pushing on the icla->dco work in the coming cycle15:06
*** lukebrowning has joined #openstack-tc15:06
ttxgreat!15:06
amrithttx ... I have a quick item for the meeting once you are done with whatever you are (now) up to.15:06
fungialso i'm well-placed to field the inevitable "why doesn't openstack just move development to gh?" sort of questions ;)15:07
EmilienMis it a meeting ? :-)15:07
*** sdague has quit IRC15:07
cdentI’ll put myself in as a backup on constellations, but if I can avoid it, I don’t want to lead as I’ve got a few other irons in the fire, so if nothing is in place by tomorrow evening, I’ll add something15:07
ttxamrith: feel free to say anything15:07
smcginnisfungi: :)15:07
fungiEmilienM: when people come together in a common venue, it's technically "a meeting" ;)15:08
fungiif an informal one in this case15:08
amrithmaking a paste15:08
EmilienMfungi: you win :P15:08
cdentsemanticsRus15:08
EmilienMfungi: I was still in the corridor ;-)15:08
smcginnisttx, fungi: I'm interested in the part time contributor discussion. Been doing onboarding talks at openstack days and helping the upstream institute stuff where I can.15:08
fungismcginnis: awesome!15:09
fungioh, and in case i don't respond in a timely fashion during office hour today, we started the zuul v3 cutover outage at the same time (zuul v2 is currently completely offline)15:09
* ttx wonders if a ptgbot hackathon would be ontopic for forum15:10
ttxprobably a bit overspecific15:10
smcginnisttx: That could be fun!15:10
* ttx continues to go down his todo list15:10
cdentI guess sometime between now and summit I’m going to need to come up with some topics on the community health thing, I guess chatting with alison is a way forward on that?15:10
fungittx: granted, less disruptive than the informal ptg hackathon we had going on at the ptg ;)15:10
fungier, ptgbot hackathon15:10
*** lukebrowning has quit IRC15:10
amrithhttps://review.openstack.org/#/c/488947/15:11
amrithHad a chat with dims and fungi at last TC office hours re: the above issue (Trove maintenance mode). I’ve put it down to WF-1 with the understanding that the current team will be working on trying to improve things. I’ll leave things like single vendor, lack of diversity up to someone else to decide. In parallel, I am advancing the other project that I’ve been working on; called Hoard.15:11
smcginnisamrith: ++15:11
ttxamrith: you should know better than take my cues on project naming15:11
fungiit does definitely sound like trove will lack diversity of affiliation for core reviewers in the coming months, so wouldn't be a bad idea to get that updated15:12
johnthetubaguyamrith: did you do a blog post of something on Trove vs Hoard? I am curious about the lessons learnt.15:12
*** lukebrowning has joined #openstack-tc15:12
amrithI did not15:12
amrithwill explain15:12
amrithI don't want to poison the well, is the short version.15:13
ttxalso please all note that Cyborg will be approved tomorrow morning unless we have new objections15:14
ttxhttps://review.openstack.org/#/c/504940/15:14
amrithhence I was hoping the maintenance mode patch would land.15:14
amrithBut, since it didn't I will in effect be poisoning that well.15:14
amrithwhich I'm not happy about, but so be it. I play the hand I have been dealt.15:15
cdentcyborg++15:16
cdentamrith: I’m not following. What’s the poison?15:17
*** lukebrowning has quit IRC15:17
* mordred waves to everyone15:17
* mordred hopes everyone enjoys our new Zuul v3 overlords15:17
cdentyay!15:17
dimsmordred : emerging from the dungeons after slaying the v2 beast15:17
smcginnismordred: Is it done?15:18
amrithcdent if there's a team that is trying to get trove to run again (big hill, not good odds) and another new project comes along and says we fix those problems ...15:18
mordredsmcginnis: it is currently processing15:18
smcginnishttps://media.giphy.com/media/3oEjI6hkw6nbYNQkz6/giphy.gif15:18
*** lukebrowning has joined #openstack-tc15:18
cdentamrith: I think we over-estimate the cost of multiple approaches to similar problems. We should look at many of these efforts as research, not solutions15:20
johnthetubaguythe problem I worry about with replacements / winners is the moving costs for users15:22
cdentthat’s a valid concern, but in the case where we have two things neither of which are done or hugely deployed…?15:22
cdent(that is trove v hoard is different from the (not actually real) glance v glare concern)15:23
*** lukebrowning has quit IRC15:23
amrithcdent yes, but I think that is a technical perspective (IMHO). From a customer (user) perspective though, this is a concern; saying that there are problems of a significant nature that warrant a new project, the lack of continuity (API, team), etc., are things that raise red flags.15:24
mordredcdent, amrith: *user hat on* only main concern Ihave is that different approaches have different service-type entries15:24
cdentmordred: :)15:24
*** lukebrowning has joined #openstack-tc15:25
mordredas long as hoard doesn't try to use the same service-type as trove, I think it'll all be good15:25
amrithmordred yes, started that conversation with dean troyer (briefly). so long as a user doesn't install both, hoard can use the same service name (in keystone) if I understand your comment correctly. Same with client.15:25
mordrednononononononono15:26
mordrednononononononononononono15:26
dhellmannoh, no, no15:26
amrithmordred ... I do (currently) intend to register service 'database'.15:26
dhellmannhoard will have a new name and a new service type15:26
mordredplesae do not15:26
dhellmannit is a different thing15:26
ttxno no oh no15:26
mordred'user' in this case means two diferent things15:26
amrithok, is 'dbaas' OK15:26
mordreduser as in deployer is a person who can make a choice to install hoard or trove15:26
amrithso, hoard registers as service 'dbaas'15:26
mordreduser as a consumer can't15:27
mordredamrith: awesome15:27
cdentaccording to server-types-authority, only one project can have any service type15:27
smcginnisamrith: I like that. Kind of a good differentiation between the two if I remember your goal right.15:27
mordredcdent: yah- unless a second project was intending on being a completely compatible second implementation - and so far we haven't had anyone want to do that15:27
*** zhouyaguo has quit IRC15:27
amrithmordred: +1, no intent to make them compatible15:28
johnthetubaguycdent: +1 your comment, its a different conversation for those two cases15:28
fungialso "replacement" is a strong word there... it's a competing implementation but one provider could offer both in parallel and let users choose which they want to use15:29
*** lukebrowning has quit IRC15:29
fungiunlike, say, replacing the image storing backend for nova15:29
dhellmannttx: the draft email looks ok, assuming the comments about line 13 are resolved15:29
amrithfungi as a project, I would strongly urge against that; for example, I'd use the same openstack 'CLI' words. Like openstack database create.15:30
amrithAt least, that's the first part of a conversation with Dean.15:31
*** lukebrowning has joined #openstack-tc15:31
ttxdhellmann: fixed15:31
dhellmannttx: ++15:32
mordredamrith: well - from a shade perspective (and an ansible perspective) - we should chat about what that means semantically15:32
mordredamrith: we totally paper over different backend implementations of the same thign at the shade layer - such as hiding whether nova or neutron is responsible for security groups on a cloud15:33
mordredamrith: BUT - a nova security group and a neutron security group are *basically* the same thing so can be semantically normalized15:34
amrithmordred sure. None of this (to be clear) represents a cornerstone of any kind of design. so let's definitely discuss it more.15:34
johnthetubaguyttx: I like the content of the etherpad now, will think on what is missing, can't think of anything right now15:34
mordredamrith: if a trove database and a hoard database can also be reasonably semantically normalized into an end-user 'database' object15:34
amrithyes, a trove database cluster and a hoard database cluster would be totally different things.15:34
mordredamrith: nod. so we'll want to figure out some good english to use to describe them15:34
amrithso 'openstack database create' would do very different things depending on the backend.15:34
amrithand I was hoping I could prescriptively say that it is 'trove' or 'hoard' but never the twain shall meet. Hence share the service type (database), ...15:35
cdentamrith: so is hoard “build me a database cluster” not “give me a database url”?15:35
mordredamrith: yah- in that case I would not have cloud.create_database be a front end for either/or and would likely try to come up with good english15:35
*** lukebrowning has quit IRC15:36
amrithcdent hoard would be a mix of things, it could be as little as 'build me the infrastructure for a database cluster and I'll make the cluster and get the URL through some vendor specified tool' to 'get me a database cluster URL'.15:36
cdentthat sounds like a lot of different things15:36
amrithspecifically, with cassandra (for example). If you used the community one, you could build the cluster and hand back a URL. But some people want to use DSE with its management UI. In that case you leave it up to the user to build the cluster.15:37
*** lukebrowning has joined #openstack-tc15:37
amrithyes, they are two very different things but both are dbaas use-cases and Trove was not able to address because it insisted on the 'I will get you the URL' approach.15:37
amrithif I have a cluster of resources, the DSE management tool can't (and Datastax has shown no interest in improving it to) provision resources in OpenStack.15:38
amritha very important use case for us at Verizon is the ability to orchestrate a set of resources that will be compute, storage and networking, including the DSE components, and use the DSE management UI to make and manage the cluster. But, use OpenStack for resource provisioning.15:39
cdentI guess my question is mostly around satisfying the most generic use case: “I’m a user who wants to store some data in a SQL database and I expect _you_ to keep it performant but don’t care about anything else”15:39
amrithcdent that particular use case is something which hoard will support. yes.15:39
amrithto be precise, Trove was intended to be a framework within which that could be satisfied. Hoard will similarly be a framework within which that can be implemented. Where hoard will extend trove is that Trove was a rigid framework; it would be the ONLY management interface to manage a cluster.15:40
amrithHoard will not take that position; it will allow for coexistance with other management mechanisms.15:40
*** lukebrowning has quit IRC15:42
*** lukebrowning has joined #openstack-tc15:43
amrithcdent mordred fungi ^^15:45
* cdent nods15:45
fungithanks for the clarification15:46
*** lukebrowning has quit IRC15:48
*** lukebrowning has joined #openstack-tc15:54
amrithso ... mordred cdent fungi ttx - what do you folks recommend? That I put up a spec for review and have the members of the TC review also? or have this discussion at a specific time at the tc office hours, something else. I'd hate to go a long way and be walking off into no mans land for no good reason.15:58
cdentamrith: spec for reviewing what in particular? the existence of hoard or something else?15:58
*** lukebrowning has quit IRC15:59
amrithcdent, both, but independently. for hoard to exist or not in the short term is not so much of a review as my pushing up a skeleton of a project. But the approach and the way it fits into the openstack world.16:00
amrithfor example, the namespace to use in openstack CLI16:00
amrithfor example, the service name16:00
*** lukebrowning has joined #openstack-tc16:00
amrithI'd hate to be much farther along and then find that these are things I could have fixed at the beginning16:00
cdentamrith, starting another meeting, will come back to this when I can16:01
ttxI guess you could set up a "hoard-specs" repo and push base design there for review16:02
smcginnisThat might be a good way to start.16:02
ttxbut i'm not sure we can promise now that it will be approved as official whenever proposed16:02
amriththx ttx, smcginnis cdent16:02
amrithttx, understood.16:02
amrithbut to be clear, if it is about the name, ttx chose that :)16:03
dhellmannas far as the service type, there's a team managing that list in a separate repo, so they're the ones to talk to about good names16:03
ttxalso imply the ML in early design review16:03
smcginnisamrith: I do like the name. ;)16:03
amrithsmcginnis take it up with ttx, he's the boss of me16:03
amrithttx, understood re: ML16:03
smcginnishah16:04
mordredamrith: yah - and I think discussing semantics of the differences so that we can know what sort of UI we can provide to users so that we don't wind up with trove/hoard being a nova-net/neutron level of fun16:04
*** lukebrowning has quit IRC16:05
*** lukebrowning has joined #openstack-tc16:07
*** lukebrowning has quit IRC16:11
*** lukebrowning has joined #openstack-tc16:13
amrithmordred YES! thanks, I'll push up specs and will be advertising broadly16:16
dtroyerdang, my apologies for missing this discussuin…16:17
*** lukebrowning has quit IRC16:18
amrithhi dtroyer ... I took your name a couple of times.16:18
amrithsigned you up for a bunch of things, including providing nice t-shirts for the team.16:18
dtroyerre the resource naming, what I recall talking about is where hoard and trove resources overlap (similar to security groups) we could look at common resource names16:18
* dtroyer just finished reading scrollback16:18
amrithYUP. the consensus is that I should write these up in more detail into a spec and use the normal review process (with more specifics and details).16:19
*** lukebrowning has joined #openstack-tc16:19
dtroyeramrith: I think it is a good idea to flesh out some of that early on, expected resource names and actions peerformed against them, to see how things fall out16:19
amrithwhat we talked about was at a high level and when the rubber meets the road, we may find that we have to change that approach.16:19
amrithso while we think (now) that we could come up with common resource names, we may figure that it is too much of a pain and just have hoard use new names.16:20
dtroyersure, but like you said, there will be some things that can and should be sorted early to make everyones lives better down the road, sounds like you are heading there16:20
amrithfine with that, would like to know early; hence the conversations early.16:20
amrithyup16:20
*** lukebrowning has quit IRC16:24
*** lukebrowning has joined #openstack-tc16:25
*** lukebrowning has quit IRC16:30
*** lukebrowning has joined #openstack-tc16:32
cdentamrith: the sad but true is that any writing you do will only limit, not remove, the possibility that down the road someone will say “this is not what we need”, “you’re doing it completely wrong” or any of the variants on those themes16:36
*** lukebrowning has quit IRC16:36
*** lukebrowning has joined #openstack-tc16:44
*** cdent has quit IRC16:49
*** lukebrowning has quit IRC16:49
amrithcdent, understood.16:54
*** lukebrowning has joined #openstack-tc16:55
*** jpich has quit IRC16:59
*** lukebrowning has quit IRC16:59
*** lukebrowning has joined #openstack-tc17:01
*** rosmaita_ has joined #openstack-tc18:53
*** rosmaita has quit IRC18:56
*** rosmaita_ has quit IRC19:05
*** rosmaita has joined #openstack-tc19:06
*** cdent has joined #openstack-tc20:03
*** kumarmn has quit IRC22:03
*** lbragstad has quit IRC22:37
*** lukebrowning has quit IRC22:53
*** lukebrowning has joined #openstack-tc22:53
*** lukebrowning has quit IRC22:58
*** lukebrowning has joined #openstack-tc22:59
*** lukebrowning has quit IRC23:04
*** lukebrowning has joined #openstack-tc23:06
*** hongbin has quit IRC23:07
*** lukebrowning has quit IRC23:11
*** lukebrowning has joined #openstack-tc23:12
*** lukebrowning has quit IRC23:16
*** lukebrowning has joined #openstack-tc23:24
*** cdent has quit IRC23:27
*** kumarmn has joined #openstack-tc23:28
*** lukebrowning has quit IRC23:29
*** lukebrowning has joined #openstack-tc23:31
*** kumarmn has quit IRC23:31
*** kumarmn has joined #openstack-tc23:31
*** lukebrowning has quit IRC23:35
*** kumarmn has quit IRC23:36
*** lukebrowning has joined #openstack-tc23:42
*** lukebrowning has quit IRC23:46
*** lukebrowning has joined #openstack-tc23:48
*** kumarmn has joined #openstack-tc23:48
*** lukebrowning has quit IRC23:52
*** lukebrowning has joined #openstack-tc23:54

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