17:00:30 #startmeeting mercadorproject 17:00:30 Meeting started Fri Aug 14 17:00:30 2015 UTC and is due to finish in 60 minutes. The chair is geoffarnold. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:33 The meeting name has been set to 'mercadorproject' 17:00:39 ping 17:00:48 pong 17:00:53 pong 17:01:01 bud 17:01:38 bud??? ;-) 17:02:04 I was expecting 'light' 17:02:18 dy 17:02:19 OK, we've had some changes since we last met 17:02:46 Based on design discussions over at HP 17:03:09 The basic model is unchanged 17:03:46 Publisher service running in provider cloud, Subscriber running in consuming cloud 17:04:27 However rather than implementing Publisher and Subscriber as independent services, with their own endpoints, installation/configuration, etc.... 17:04:46 we're going to integrate them into Keystone 17:04:54 for now :) 17:05:04 This has some benefits and complications 17:05:09 yes, for now 17:05:39 Benefits: faster spinning up the POC, reduced round-trips between Keystone and Subscriber 17:05:49 gyee: light \o 17:05:53 Complications: it's a fork of Keystone 17:06:15 not quite 17:06:41 de facto, gyee? 17:06:43 gyee, it requires keystone mods beyond just dropping the mercador/ directory in contrib 17:06:55 my commit shows thay 17:07:00 s/thay/that/ 17:07:05 its a fork for conveninence 17:07:12 but we are not touching keystone internals 17:07:15 exactly 17:07:35 except to interpose on CRUD for "project" 17:07:36 it should not require keystone mod 17:07:42 geoffarnold: do you want to use some stable release for this? 17:07:48 just contrib and middleware 17:07:54 yes 17:07:55 raildo, I started with master 17:08:08 not especially, raildo 17:08:54 shaleh can you add raildo to the project in github 17:08:57 raildo, not till we flesh out the landmines 17:09:11 geoffarnold, I just need a github user to invite 17:09:35 maybe this will be a little painful, since we have to be doing a lot of rebases... 17:09:49 geoffarnold: thanks 17:09:52 raildo: what is your github user name? 17:10:01 raildo :P 17:10:06 one moment 17:10:13 raildo, shouldn't be painful, we are NOT touching Keystone internals 17:10:27 if we do, this ain't gonna end well 17:10:54 gyee: ok 17:11:11 if we do, it shows that Keystone's contrib framework isn't as clean as intended 17:11:19 exactly 17:11:37 geoffarnold: I added a "Contributors" team to the Org. Raildo has been invited 17:11:50 There's a Trello at https://trello.com/b/6tlmk3z4/mercador-stackforge-project 17:12:09 raildo: I forked keystone and friends to the Mercador Org on github. We made a branch for mercador-poc there 17:12:15 Still stays "stackforge", but no worries 17:12:36 all changes are intended to be in the keystone/contrib/mercado dir unless 100% necessary 17:12:43 so keeping up with master should be pretty easy 17:12:52 ++ 17:13:04 +++ 17:13:18 at the end, it should be a complete separatable service 17:13:22 sure 17:15:15 Or two 17:15:37 raildo: if I need to fork something else into the Org let me know 17:16:15 the non Openstack project is my Vagrant/Ansible work to federate a collection of virtualbox nodes running devstack 17:16:53 shaleh, how close are you in getting the ansible work done? 17:16:54 shaleh: I think that is it. 17:17:17 gyee: I believe it is done but I need to fully test the federation connectivity 17:17:27 sweet 17:17:41 I have a script to push projects/domains/users etc onto the SPs 17:17:53 then I can try to access them from the Idp using fed-tester box 17:18:01 once that is fully tested I can bless it 17:18:06 hopefully that is today 17:18:42 everything I have is up on GitHub. 17:18:49 I just pushed my API design notes to Pastebin: http://pastebin.com/Sanc8WeR 17:18:58 Formatting sucks; I'll fix it up 17:19:25 geoffarnold: next step is putting that on the wiki yes? 17:19:30 geoffarnold, you'll update the wiki with the API design too right? 17:19:45 Yes - in a few minutes 17:20:18 * geoffarnold mumbles about Word-to-Mediawiki conversion tools 17:20:40 raildo: the fork of Keystone has a "hello world" quality Mercador at the moment. It responds to /v1/subscribers 17:20:49 geoffarnold: so stop using Word :-) 17:21:01 Agreed 17:21:07 hah 17:21:39 ++ haha 17:21:40 markdown ftw 17:22:00 I actually like asciidoc ..... 17:22:35 i'd missed that, shaleh - I'll check it out 17:22:39 shaleh: I found, thanks 17:22:51 http://asciidoctor.org/ 17:23:01 GitHub supports files named ".adoc" 17:23:15 judge a doc by its content, but not its apparent - gyee's paraphrasing MLK 17:23:15 sweet 17:23:45 geoffarnold: what do we have for an agenda? 17:23:53 we have completed show & tell 17:24:06 nothing else AFAIK 17:24:18 Next week is crazy 17:24:24 my plan is to start on the token interceptor work 17:24:52 Monday is shot (Cisco mtgs), Tues-Wed is Operators Meetup, Thurs-Fri is Product WG (I'm hosting) 17:25:01 understood 17:25:18 when we meet the following week I expect to have a demo for the group 17:26:03 geoffarnold, will Cisco folks help out on the rest of the API impl? 17:26:20 davidjc do you want to take a look at the CLI? 17:26:20 I've done my freebie :-) 17:26:29 we are at a point we can multithreading now 17:26:44 well the CLI will be easy to develop once all of the backend APIs are completed 17:27:00 I plan on diving in on that today, or exploring the API backends as discussed 17:27:04 particularly for pub 17:27:08 CLI work expects changes to python-keystoneclient or an equiv 17:27:23 We should start by replicating shaleh's hello world 17:27:54 Just to demonstrate end-to-end 17:27:58 ++ 17:28:08 for CLI/client, I suggest separate packages for python-mercadorclient 17:28:18 + 17:28:19 the Subscriber CRUD is implemented as I understood it from the document 17:28:30 gyee: not a bad idea 17:29:02 copy/paste the existing keystoneclient to get the ball rolling quickly 17:29:15 defined, not yet implemented.... the changed approach means that the URL schemas change a bit (not significant) 17:29:30 there has been a lot of noise on the -dev list about Federation. Was any of it relevant. I have not kept up. 17:29:52 shaleh, no, not relevant to this work 17:29:56 I missed most of it - thought it was ID fed 17:29:59 WebSSO they are arguing over 17:30:05 ah, god 17:30:08 good 17:30:09 we care about K2K 17:30:09 I meant 17:30:09 Yup 17:30:42 raildo: I gave you read/write as a Contributor. 17:30:53 we need to think about how to make K2K config more dynamic 17:30:59 but that's a parallel track 17:31:03 there is not Jenkins gate here so play nice everyone 17:31:15 I mistype "god" for "good" so often, I'm thinking of having MacOS translate "god" to "Cthulu" 17:31:26 god is good 17:31:42 shaleh: ok, if have some user story/task that I can contribute, let me know 17:31:53 * shaleh points to geoffarnold 17:32:27 raildo: you might end up being a dev tester for us if that is acceptable 17:32:38 Hey, raildo, on a parallel track, I'd like to get the reseller user stories into the Product WG discussions 17:32:46 I'll follow up offline 17:33:08 geoffarnold: if there are more people who need Contributor status let me know 17:33:15 shaleh: I can do that :) 17:33:20 davidjc? 17:33:34 geoffarnold: he has been invited as an Owner like you were 17:33:43 geoffarnold: sure, we can discuss when you have some time 17:33:53 (referring to his team) 17:34:00 or I can send a email 17:34:27 raildo thanks, that would be good 17:34:34 I would like contributor status if I do not have such status already 17:34:39 thanks 17:34:50 davidjc: accept the Gihub invite sent Tuesday evening 17:34:55 will do 17:35:35 geoffarnold/davidjc: it probably makes sense for you guys to get some kind of Jenkins gate style system setup on your end to test as you get further along 17:35:46 agreed 17:36:02 one last question (for gyee) 17:36:20 \o 17:36:30 I had to miss the Keystone mtg this week - was there anything important (apart from WebSSO)? 17:36:56 policy distribution 17:37:10 we voted to include it as experimental 17:37:22 same holds for x.509 tokenless authz 17:37:58 thanks 17:38:05 there were some concerns over policy distribution however 17:38:12 performance wise 17:38:29 so its going to be either keystone, consul, or zookeeper 17:38:36 btw we need more reviews in the reseller patches :( 17:38:52 so we still need a bunch of POC work to flush out the land mines 17:39:05 right 17:39:56 I'm still wrestling with the question of how/when we can fix the project/domain namespace problem 17:40:00 raildo, yes will do 17:40:12 raildo, I am having f2f with out PM next week in the ops midcycle 17:40:22 it takes API changes, DB changes, just about everything 17:41:29 come along to the large scale/public cloud breakout at the ops meeting 17:41:31 geoffarnold, v4 :) 17:41:53 federation and safe delegation will be on the table 17:42:41 consul tries to hard to get people onto its pay cloud 17:42:56 but otherwise I kind of like it 17:43:00 I know morgan does too 17:43:17 I'll look at it 17:43:22 I haven't had a chance to dig deep into it yet 17:43:32 geoffarnold: all we can do is point out how painful life is without a fix 17:44:14 Agreed. Maybe we need to bring a QSA along to rip holes in people's smug assumptions about trust 17:44:16 consul is Go lang. Pretty well documented. Written by hashi corp. 17:44:43 I have been messing around with Consul, it has some strengths and weaknesses 17:44:52 davidjc: agreed 17:45:00 Well, if we're going to include more non-Python bits, Go will be popular 17:45:05 I kind of like it over Zookeeper though 17:45:14 the not Java helps :-) 17:45:26 or Oracle will sue ya 17:45:28 Well Consul and Zookeeper are for different purposes 17:45:35 the closest thing to Zookeeper is etcd 17:46:04 talking to Morgan he would like to divest more of Keystone to tools like Consul 17:46:20 +1 17:46:54 On the other hand.... WS-Discovery and UDDI left a lot of people nervous about this stuff 17:47:09 while in principle I agree, it makes OpenStack even more unwieldy 17:47:25 even more moving pieces, points of failure, etc. 17:47:37 I pity the ops crew who have to keep up with all of this mess 17:48:01 shaleh, OpenStack by itself is unusable :) It needs a log of 3rd party tools 17:48:05 too many people in OpenStack seem to only see the DevStack view of the world 17:48:16 Wouldn't it be nice if we could apply all the Consul work (Raft, etc.) to make DNS really usable for this 17:48:25 geoffarnold: agreed 17:48:54 OK, we're drifting into the "over a pint of beer" mode, so let's wrap 17:48:59 and there are load of commercial interest in the 3rd party tools 17:48:59 well the biggest problem with the state of DNS is performance in Python 17:49:10 so we stuck in this no-op land 17:49:16 performance can always be fixed 17:49:26 by choosing a different language 17:49:35 "works good enough" gets you pretty far 17:49:44 are we talking about designate? 17:49:54 cheers all 17:50:05 not really, davidjc 17:50:09 cheers 17:50:13 #endmeeting