14:59:41 #startmeeting craton 14:59:41 Meeting started Mon Jun 20 14:59:41 2016 UTC and is due to finish in 60 minutes. The chair is jimbaker. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:59:42 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:59:44 The meeting name has been set to 'craton' 15:00:10 o/ 15:00:12 o/ 15:00:14 o/ 15:00:27 o/ 15:02:03 the eavesdrop for the agenda is actually one week old - for june 6, not june 13 15:02:13 anyone have an up-to-date link? 15:02:55 i will suggest however discussing a demo that sulo and i did last friday first 15:03:18 b3rnard0 will be posting the video to youtube shortly 15:03:33 #action b3rnard0 youtube demo link 15:04:47 to recap, most of the issues we were tracking for https://waffle.io/rackerlabs/craton?milestone=MVP (what i have been calling recently phase 1) are done 15:05:30 the remaining issues - OSIC ingest and ansible inventory - we did in fact demo, they just need to be finalized 15:07:00 sulo, do you want to add a diff to get that ansible inventory fixed on my PR? 15:07:15 yeah i will do that 15:07:34 cool, that will be very helpful - just whatever you did to get it to work for the demo :) 15:07:49 (made it!) 15:07:51 ok 15:08:03 rainya, o/ 15:08:06 hi rainya 15:08:35 morning! 15:08:51 sarob, good to see you! 15:08:58 thx 15:09:33 so the demo was open, but we did a bad job of promoting it outside of the OSIC team 15:10:21 this week we are going to try to open up communications further. it will be a continual process 15:10:57 sarob, do you have last week's eavesdrop handy by chance? 15:11:06 hmm, let me see 15:11:12 this is the first item for us to cover, but the agenda has the june 6 link 15:11:33 * jimbaker is stalling for time apparently :) 15:11:59 anyway, i think the demo went well 15:12:28 jimbaker: last weeks log ? 15:12:29 sulo drove the actual demo 15:12:30 http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-06-13-15.15.html 15:12:34 sulo, thanks 15:12:43 thx 15:13:01 should we discuss where we are with the action items ? 15:13:29 in particular, we demonstrated using craton's inventory rest api to load and query against the osic reference cluster 15:13:52 this included ansible inventory integration; and showing how variables can override 15:14:08 sarob, and with that, let's move to that part of the agenda 15:14:24 #topic action items from last week 15:14:45 soooo 15:14:51 sarob, what's the status of that infra patch? 15:15:15 i need to know the core-reviews 15:15:21 (we are now ready to make a changeover at any time, now that we have completed phase 1 work) 15:15:34 (if with minor cleanup) 15:15:43 and i need to be added to the launchpad https://launchpad.net/~craton 15:15:56 sarob, so i just added you to the ~craton group 15:16:06 excellent 15:16:18 sarob, should we make that group open to anyone who wants to add themselves? 15:16:28 that group sure 15:16:47 yeah, we can always add a ~craton-dev or whatever 15:16:48 im going to create a core-reviewers group 15:17:11 that will be the only ones that can modify the launchpad craton group 15:17:21 and same group 15:17:30 sarob, +1 15:17:39 for permitting merge through gerrit 15:17:59 i should be done with all the bit today 15:18:03 bits 15:18:06 so the usual openstack practice. thanks for taking care of that! 15:18:22 shirely 15:18:24 ok, so sounds like good progress on that action item, sarob 15:18:40 * jimbaker was working on the blueprint re integration patterns 15:19:01 i made the following progress: started a blueprint placeholder 15:19:43 for specs? 15:19:46 also i had some good discussions re integration with oneops with VitalyZ 15:20:03 and with nova, cinder with KrishR 15:20:33 sarob, this most likely will drive some spects 15:20:35 specs 15:20:51 we need a place to land specs in the repo 15:21:07 sarob, so my feeling is that blueprints should start specs 15:21:16 right on 15:21:21 with docs about those specs making their way into the repo once approved 15:22:04 blueprints seem to be reasonably lightweight for this purpose 15:22:07 so blueprint in launchpad 15:22:13 yes 15:22:24 if complicated enough then spec in repo with review 15:22:26 go through the approval process 15:22:45 sarob, ahh, this is where i can see scope for misunderstanding 15:23:00 so i think all specs going forward should use blueprints 15:23:07 yeah 15:23:19 but not all blueprints need a spec? 15:23:25 but not everyone reads the blueprints, nor should they 15:24:00 so detailed out specs, especially ones relevant to users of craton, should go in the repo 15:24:14 it's two places, so that's not so great 15:24:31 but docs are often that way 15:24:44 i always add URL to each in each 15:24:57 sarob, +1 15:25:40 jimbaker: is the expectation that going forward (once infra is ready) we will transition from existing git repos and waffle? 15:25:51 i will continue to work on that blueprint re integration patterns 15:26:08 cmspence, yes, we are fully going to move over to standard openstack practice 15:26:33 waffle, github issues, github PRs was just a stopgap for us 15:26:36 Waffle has been fun at least :) Standards for the win! 15:26:58 rainya_, i agree that waffle is rather nice/lightweight 15:27:22 storyboard will save us! 15:27:23 it raises a larger question of if the existing standards could be streamlined, but well out of scope for this project 15:27:54 i'm ok with us using storyboard, but i do not know the way 15:28:13 its still in development 15:28:17 b3rnard0 could be our gandalf here 15:28:30 jimbaker, as you all ID the need for communication assitance, which seems to be a challenge for any new project with the team fully engaged in development, tap me for that please? 15:28:44 im dubious if it will be ready 15:28:57 rainya, that sounds great! 15:29:23 meeting notifications, "newsletters", spec process changes, etc -- things you'd like a program manager type for; dont' have the bandwidth for code contribution but i can help with the program stuff 15:29:38 thanks for volunteering here, it's very much appreciated 15:30:03 rainya, jimbaker: lets start dropping all email on openstack-dev 15:30:11 its a start 15:30:24 sarob, that was my action item in fact :) 15:30:33 at least cc: openstack-dev 15:30:59 sarob jimbaker, excellent idea 15:30:59 sarob, first one must write the emails :) 15:31:14 jimbaker, i'll write something up, send to you for review/proof and then you can either send it or i can 15:31:32 rainya, i'm happy to review with you something 15:31:38 as a new meeting / project, having a summary of "hey, we had a meeting this week go read about it!" is a good start 15:31:39 we could just do it up on an etherpad 15:31:44 and if you write it, please send it :) 15:32:06 heh, but then I can't stay under the radar ;) 15:32:12 etherpad meeting notes are a good idea 15:32:28 #action rainya to draft etherpad note to openstack-dev with jimbaker 15:32:34 (i didn't action correctly i don't think) 15:32:35 thanks! 15:32:46 i need to do it as chair 15:32:47 #action rainya to draft etherpad note to openstack-dev with jimbaker 15:33:02 cool, well now I feel useful and a contributing member! woot! 15:33:15 it's the usual open source way 15:33:23 step in where there's a problem 15:33:28 good stuff 15:33:48 * sarob hand up 15:33:55 sarob, ? 15:33:58 i need a core-review list 15:34:06 (also i was going to ask about antongribok's action item) 15:34:10 core-reviewer 15:34:23 i was being funny 15:34:27 putting my hand up 15:34:31 sigh 15:34:42 sarob, is this something we need to do from ~craton launchpad? 15:34:42 * sarob drops mic 15:34:55 part of creating project stuff 15:35:37 right, let me suggest we move this discussion to #craton - i know i have not read the manual here so-to-speak 15:35:50 and we don't have too much time left in this meeting 15:35:56 no prob 15:36:11 so how about sarob, you and i work together today as we have time to finalize everything we can do right now 15:36:31 * jimbaker was too busy last week for finalizing phase 1/demo. not so bad now 15:37:01 #action jimbaker works with sarob re outstanding openstack infra issues 15:37:23 jimbaker: yeah ive gots mgmt stuff going on 15:37:43 between that today can give you some time 15:37:49 sounds good, and thanks 15:38:26 re antongribok's action item, there's a meeting tomorrow about this 15:38:56 rainya, you will want to be part of that, and regardless we will want to make sure this meeting is publicized 15:39:54 there are actually two pieces here: 1. what inventory modeling do we need to accommodate describing hardware devices for swift/ceph/cinder setup 15:40:48 2. what can we do to better support integrating with the services that are setup - also include nova here 15:41:06 anyway, that's the scope for that meeting 15:41:23 kvprash is organizing; sulo and i will also be attending 15:41:25 jimbaker, what time / place for tomorrow? 15:41:34 jimbaker, or is it in the meeting etherpad we started 15:41:59 sulo, can you find that meeting invite? 15:43:01 rainya, hopefully we will doc here in this meeting, but if not, it will be discussed on #craton 15:43:09 +1 15:43:54 and going forward, this is incredibly important for getting communications opened up for the project as a whole 15:44:27 as an aside, we are having a retrospective/planning meeting this wednesday, we will also be sure to make that call public 15:46:09 sarob, did we get anything set up with VitalyZ to discuss oneops integration? 15:46:57 jimbaker: if you have a perf time, let me know, i will pass it on 15:47:17 jimbaker: he is on another call right now 15:47:35 sarob, no worries. i suspect end of week is best for me 15:47:46 jimbaker: passing on 15:48:05 time is running out here... time to move on :) 15:48:14 * sarob is a irc to slack interpeter 15:48:21 sarob, :) 15:48:43 * jimbaker is a poorly coded select loop 15:49:14 #topic outstanding issues 15:49:33 waffle provides a good summary: https://waffle.io/rackerlabs/craton 15:50:14 so we will want to triage this backlog - are these cards still relevant? etc 15:51:29 overall, i see three key things we will be looking at: 1. workflows, including scheduling; 2. inventory extensions, including RBAC; 3. integration 15:52:30 the meetings tues/wed will help define these priorities; we will also be working with the taskflow project to be sure to use their capabilities for our workflow needs 15:53:21 rainya, btw, i think this will be some key info to expose to openstack-dev about what we are doing 15:54:15 jimbaker, roger that 15:54:52 jimbaker, will be drafting our first email on https://etherpad.openstack.org/p/craton-meetings 15:55:08 rainya, thanks, sounds like a good place to take care of that 15:55:23 time check: 5 minutes 15:55:37 any other questions as we wrap up? 15:55:43 #topic wrap up 15:57:22 cool. i think the team put in some amazing effort to get phase 1 (basically) completed; and hopefully everyone had some great rest/relaxation over the weekend 15:58:03 looking forward to some more great work! 15:58:15 time to move discussion over to #craton 15:58:24 cheers! 15:58:25 thanks everyone! 15:58:49 #endmeeting