15:00:48 #startmeeting craton 15:00:49 Meeting started Mon Jun 6 15:00:48 2016 UTC and is due to finish in 60 minutes. The chair is sarob. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:50 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:53 o/ 15:00:53 The meeting name has been set to 'craton' 15:00:57 roll call! 15:01:12 Hi! I'm Ian Cordasco (Rackspace) 15:01:34 hey sigmavirus24 15:01:56 hey there sarob 15:02:31 o/ folks, Sulochan Acharya from Rackspace 15:02:39 hello sulo 15:03:05 there wasnt an agenda posted at 15:03:26 yeah we've been kinda heads down with phase 1 stuff 15:03:33 #link https://wiki.openstack.org/wiki/Meetings/craton 15:03:43 lets start there 15:03:45 hopefully from next week we have a better meeting plan 15:03:54 #what's phase 1 stuff 15:04:00 #topic what's phase 1 stuff 15:04:15 so i think we discussed this briefly during first meeting 15:04:31 give me very high level 15:04:38 we wanted to get a minimal working product (MVP sort) 15:04:51 with atleast a working inventory 15:04:56 for newton release 15:04:57 with rest and python api 15:05:07 sounds reasonable 15:05:20 some thought around python version 15:05:37 assuming the plan is to write it in python 15:06:01 sarob: so i think the consensus is py3 all the way 15:06:15 expected 15:06:34 but support py27 for client 15:06:37 so the code at #link https://github.com/rackerlabs/craton 15:06:43 is the start? 15:06:51 sarob: yes 15:07:26 we've been tracking issues etc there as well for now 15:07:40 but i assume we will move to openstack infra soon 15:07:53 long list 15:08:30 i can take care of the move when we have a team discussion to move 15:08:39 sounds good 15:08:54 i think it should be a action item for next meet 15:08:55 we will need to move the issues to launchpad 15:08:57 as well 15:09:05 +1 15:09:05 oh, agenda sstart now 15:09:16 * sarob likes 15:10:21 #action sarob add when to move to openstack github org to next weeks agenda 15:10:56 ill write up some basic steps like launchpad use 15:11:07 cool 15:11:08 newton release publish 15:11:18 also there is some work started on the cli 15:11:30 client is good 15:11:39 separate repo? 15:11:47 yes 15:12:01 i think folks have started to work on the doc in teh same repo right now 15:12:22 python-craton-client? 15:12:39 or just doc on what to build so far? 15:13:14 i think jim has python-craton reserved or soemthing need to check on that but yes in general 15:13:17 sarob: yes https://github.com/rackerlabs/craton/pull/84 15:13:26 roger that 15:13:31 is a start .. i think we need to clenup the api docs a bit more 15:13:41 so that it matches up with what the cli expects 15:14:11 i am refering to https://github.com/rackerlabs/craton/blob/master/craton/api-ref/swagger/swagger-inventory-api.yaml 15:14:19 and is purely for craton-inventory 15:14:29 we will surely have more on workflow api 15:14:41 okay so i think phase 1 : inventory, basic client, major bugfixes, api = newton releaese 15:14:50 plus docs 15:15:14 that sounds good 15:15:20 thats probably alot for a new team 15:15:29 yeah 15:16:10 ill work on getting you a few contributors from my larger team 15:16:19 so one item i had was what if anything do we want to add in inventory modeling 15:16:33 this question purely comes from our previous discussion 15:16:56 * sarob reviewing 15:16:56 i think few folks from walmart labs were looking at including cinder swift into inventory 15:17:34 i had started tracking it here: https://github.com/rackerlabs/craton/issues/63 15:17:56 would be nice to include any changes in this cycle 15:18:27 this is assuming that the current inv model does not meet the need 15:18:42 looks like hvprash and anton put their hand up 15:19:05 hvprash_: you online? 15:19:11 hvprash: you online? 15:19:43 #action hyprash, anton: researching https://github.com/rackerlabs/craton/issues/63 15:19:46 we can leave that as something to discuss next week if folks are not around today 15:19:53 yup 15:19:59 k 15:20:13 action list for follow up 15:20:42 speaking of that 15:20:58 #topic follow up action items from last week 15:21:02 #link http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-05-23-14.31.html 15:21:22 thanks for that :) 15:21:36 #info item 1 we just pushed to next week 15:21:57 #info item 2 jimbaker describe integration with external rest api-based cmdb (such as rackspace core) 15:22:12 jimbaker: is on vaca 15:22:18 i heard 15:22:21 yeah he is out today 15:23:30 #link https://github.com/rackerlabs/craton/issues/2 15:23:42 is that the issue tracking the action item? 15:24:27 yes 15:24:29 sarob: I think #2 describes Craton's API? 15:24:44 we might not be tracking the correct ones though 15:24:50 for that epic 15:25:08 closer inspection looks like the issue doesnt exist yet 15:26:00 any details on what type of integration we are talking about here? 15:26:30 sarob: I think of the cmd integration like keystone's ldap integration 15:26:33 Does that make sense? 15:26:42 i think it was about integrating external cmdb type systems example rax or oneops with craton api 15:27:10 okey dokey 15:28:01 #action jimbaker follow up on describe, post issue on integration with external rest api-based cmdb (such as rackspace core, oneops) 15:28:22 that is for last week 15:29:03 #topic new topics 15:30:42 i have one or two people that are going to start working on this project 15:30:58 awesome 15:31:00 ill see if i can get them up this early ;) 15:31:17 everyone seems to be on hawaii time 15:31:44 which is convenent for holding meetings in hawaii 15:32:24 anything else for the record before I call this meeting? 15:32:39 nothing from my side 15:32:46 thanks sarob 15:32:58 thanks for attending 15:33:05 have a great week 15:33:25 #endmeeting