16:01:08 #startmeeting Solum Team Meeting 16:01:11 Meeting started Tue Feb 4 16:01:08 2014 UTC and is due to finish in 60 minutes. The chair is adrian_otto. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:15 The meeting name has been set to 'solum_team_meeting' 16:01:16 #link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2014-02-04_1600_UTC Our Agenda 16:01:26 #topic Roll Call 16:01:27 Paul Montgomery 16:01:32 Clayton Coleman 16:01:32 tom blankenship 16:01:33 Pierre Padrixe 16:01:34 Nikita Marchenko, Mirantis 16:01:34 Adrian Otto 16:01:37 Swapnil 16:01:39 Paul Czarkowski 16:01:39 Georgy Okrokvertskhov 16:01:44 Roshan Agrawal 16:01:53 Krishna Raman 16:01:55 Devdatta Kulkarni, Rackspace 16:02:03 Julien Vey 16:02:07 murali allada 16:02:14 Shaunak Kashyap, Rackspace 16:02:51 Arati Mahimane 16:02:53 Welcome everyone! 16:03:15 feel free to chime in at any time to be recorded in the attendance. 16:03:19 #topic Announcements 16:03:28 Any announcements from our team members? 16:03:59 Small update on Glance repository. 16:04:12 gokrokve_: :) 16:04:21 As you know last week there was a Glance mini-summit. 16:04:51 There was a decision made to create generic artifact repository API in Glance. 16:05:17 It will have pluggable architecture to support custom artifact types for specific parsing. 16:05:20 sweet 16:05:22 gokrokve_, That's good news 16:05:52 So, Solum will be able to use it to store its artifacts like LP, definitions and whatever you want. 16:06:09 gokrokve_: where can Solum team members learn more about it? 16:06:15 Some working code will probably be available in J M1 timeframe. 16:06:28 did they already file a BP for it? 16:06:48 gokrokve_: any etherpads? 16:06:52 adrian_otto: Right now there is nothing to learn. I will update you as soon as BPs are submitted and some details appear. 16:07:02 rajdeep: welcome 16:07:12 hi 16:07:16 There are some drafts but they are not represent the idea. 16:07:51 That is it for Glance part :-) 16:08:04 ok, if anyone notices the blueprint go up, please subscribe me, and let's revisit that as a future announcement in one of our team meetings. 16:08:26 we should do our part to participate in the design of that to help make it as useful as possible. 16:08:42 any other announcements? 16:08:57 thanks gokrokve_ 16:09:01 #topic Review Action Items 16:09:19 1) ACTION: adrian_otto to create blueprints for each of the API REST Resources (adrian_otto, 16:12:22) 16:09:34 Status: in progress. This will be done today. 16:09:44 2) ACTION: adrian_otto to propose an alternate meeting time for the Solum team, potentially an alternating time schedule (adrian_otto, 16:46:19) 16:09:55 let's dive into this one a bit 16:09:57 See: https://wiki.openstack.org/wiki/Solum/ProposedMeetingTime 16:10:07 #link https://wiki.openstack.org/wiki/Solum/ProposedMeetingTime 16:10:35 I want input from those who are not attending today because it's the middle of the night 16:11:04 so we won't make a final decision, but I'd like input on the idea of alternating meetings on a */2 week basis 16:11:15 i think current time works better for me.. 16:11:18 so we would alternate between this time, and another time 16:11:29 because no option is good for everyone 16:11:30 current time is best for IST people 16:11:54 I'm particularly sensitive to the effective exclusion of core reviewers from the weekly meeting 16:12:16 current +option 2 16:12:22 and we have cores in at least 4 timezones 16:13:03 current + 12,7,1,9 16:13:06 so what I think I will do is make this into a doodle poll, and get a feeling for the popular vote. 16:13:44 because I do want to balance the interests of high weekly attendance with local convenience for those of us distributed throughout the globe. 16:13:50 i think 12,7,1,9 would be a better option1 ;) 16:14:04 let me look at that, one sec. 16:14:37 #link http://www.worldtimebuddy.com/?qm=1&lid=8,2158177,1277333,2988507&h=8&date=2014-2-4&sln=12-13 16:15:04 so if that were an ever-other-week meeting time, would any of our India contributors attend that? 16:15:43 coolsvap: what do you think? noorul? 16:15:43 you mean the 6am one? 16:16:21 rajdeep: visit the link above, which I think would be ~1:00 AM in India, right? 16:16:32 this is an option not listed on my wiki page. 16:16:40 how about: 9, 4, 10.30, 6 16:16:46 ah.. thats going to be tough 16:16:50 adrian_otto: I don't think 1:30 am is feasible for Indian contributors 16:17:06 so that brings us back to alternating the meeting time 16:18:03 ideally that time would be somewhat convenient for the majority of the regular attendees (mostly in US timezones), and convenient at least once every second week for all the core reviewers. 16:18:42 thoughts on that? 16:18:54 which time are you talking about? 16:19:01 9, 4, 10.30, 6 ? 16:19:25 Our current time, plus Option 1 in https://wiki.openstack.org/wiki/Solum/ProposedMeetingTime 16:19:56 current time is fine for me 16:20:02 I think the best is to have a doodle poll 16:20:15 Option 2 is actually better given our criteria 16:20:26 adrian_otto: yes 16:20:39 ok, I'll set up the poll, and we will revisit it again. Thanks everyone for your input. This is a hard issue to address. 16:20:57 next action item is: 16:21:00 3) ACTION: adrian_otto to get input from team members on F2F meetings, and Summit meeting plans (adrian_otto, 16:59:16) 16:21:07 Status: in-progress. Working to identify an alternate host. If not Rackspace is willing to host. 16:21:26 kraman: was Matt able to join is? 16:21:34 adrian_otto: unfortunately no 16:21:40 he is on the road today 16:21:47 i have asked him to email you back 16:21:52 kraman: ok, thanks 16:22:09 also Angus is now in Brisbane, the wiki page shows melbourne. usually same timezone, except in summer, brisbane doesn't have DST. i.e. right now melba is gmt+11, brisbane is gmt+10 16:22:13 Team, in collaborations it's customary to alternate the location and host of F2F meetings 16:22:28 paulczar: tx! 16:22:54 so I want to give other team members a fair opportunity to host the event if they would like to 16:23:11 we would expect attendance in the 30-40 person range, plus remote attendees. 16:23:39 adrian_otto: we would be glad to host but Paris might be a little too far for you :) 16:23:44 I will participate to the hangout from Paris if it's in Tx 16:23:47 julienvey: Thakns! 16:24:09 Rackspace has a number of different locations in the US 16:24:30 California, Texas, Georgia, Verginia 16:24:54 since the last was on the West coast, we could explore doing a March event elsewhere 16:25:21 I checked and we are all willing to travel to the Bay Area again 16:25:35 if everyone felt that was a good group 16:26:18 Virginia is probably more convenient for the RH team, right kraman and claytonc? 16:26:40 adrian_otto: yes claytonc, dan and jessica re on the east coast 16:26:52 adrian_otto: but its cold there :) 16:26:53 if nobody specifically cares to host, we should do it at a place that reduces travel time for majority … that would be Austin right? ;) 16:27:29 paul, yes, that would be lowest overall distance to travel for the whole group 16:27:53 lowest CO2 16:27:53 so that's my current favorite, but I wanted to get as much input as possible 16:28:12 gokrokve_: would you be able to attend if we did it in Austin? 16:28:29 I think yes. 16:28:30 adrian_otto: perhaps we can make it a action item for all to vote on the location 16:28:50 #action adrian_otto to hold a vote for next F2F location 16:29:05 ok, so now Blueprints 16:29:11 #topic Review Blueprints 16:29:23 #link https://blueprints.launchpad.net/solum/+spec/api Solum API (aotto) 16:29:38 we have a whole bunch of open reviews on this topic 16:30:14 in general I'm feeling pretty good about the progress. It has been steady progress across numerous rest resources in the API 16:30:26 I don't see alarming gaps anywhere. 16:30:42 the new blueprints will help us finish up focus on this 16:30:57 any other thoughts on the API? 16:31:21 devkulkarni: I will ask you about linking the CLI to the API in a moment 16:31:31 #link https://blueprints.launchpad.net/solum/+spec/solum-minimal-cli Command Line Interface for Solum (devdatta-kulkarni) 16:31:54 adrian_otto: this work is progressing nicely. paulmo and noorul are on top of connecting CLI to API 16:32:23 paulmo, noorul: you want to add some more color? 16:32:24 in paulmo's recent M1 cli work, there were callouts to API functionality needed to finish up that BP 16:32:49 Was tied up last week, nothing much to add 16:32:54 Just some minor edits on the CLI text parsing code from reviews and hopefully good to go on that side 16:33:09 paulmo: great! 16:33:18 is the use of PATCH verb common in OpenStack? 16:33:40 paulmo: will you need more help from other Stackers to arrange the bits in the API we need to make the CLI funciton? 16:33:51 rajdeep: no, not yet. PATCH is new. 16:33:58 I'm a little confused, I'm not working on the API side of things, that is Noorul 16:34:22 ok, as i had not seen it very often 16:34:34 paulmo, I know, but noorul has been unable to work on that, so I'm checking to see if you want help from alternate sources 16:34:54 as that's in our critical path for M1 16:34:55 Are you asking me to finish up the REST API side of the CLI? 16:35:11 paulmo: no, I'm actually asking devkulkarni 16:35:27 Initial API code is in 16:35:30 devkulkarni: do we need more help on the API side of this BP? 16:35:32 adrian_otto: let me check back on the CLI to API connection. 16:35:37 I can quickly add more resources 16:35:41 devkulkarni: thanks. 16:35:54 paulmo: I recognize that your part of this is done 16:35:59 noorul: lets chat about it later today. 16:36:04 I'm more concerned that we don't deadlock on this 16:36:17 devkulkarni: thanks! 16:36:32 #link https://blueprints.launchpad.net/solum/+spec/solum-git-pull Pull integration of Solum from an external Git repo (kraman) 16:37:16 devkulkarni: and coolsvap have been working on tests 16:37:38 and we are also looking into a temporary solution while we continue working on gettingcode into zuul 16:38:24 kraman: last week you mentioned that you would begin submitting this work as reviews in openstack-infra. We should not need tests to do that as WIP. Do you have any objections to putting that up for OpenStack review as WIP? 16:38:54 and add in the tests from coolsvap and devkulkarni as they are produced? 16:38:55 I havent had time to do so yet due to other deadlines. But we will be doing that this week 16:39:05 along with adding tests to the WIP patch 16:39:30 I should have the patch submitted for discussion later today 16:39:53 kraman: thanks. Ideally we should get what we have in for review to get more eyeballs on it as early as we reasonably can 16:40:21 yes, makes sense. will take that as an action item for today 16:40:23 also, remember not to drop a huge patch 16:40:37 consider making it into a few smaller patches if it's a lot of code. 16:41:10 ok, will discuss with devkulkarni: coolsvap about splitting up the code into smaller pieces 16:41:12 #action kraman to submit zuul work into Gerrit as WIP for review. Tests to be added as they are created. 16:41:14 it should be possible 16:41:37 kraman: yeah, lets discuss that 16:41:56 kraman: thanks for the update, and the commitment to get that up for review 16:42:04 any more remarks on this BP? 16:42:27 I have schedules a meeting for tomorrow to discuss the temporary service we will put in place while we work n zuul 16:42:53 kraman: please announce the time here 16:43:08 for those who might take an interest in joining in 16:43:23 Meeting will take place at 9 AM PST (http://www.worldtimebuddy.com/?qm=1&lid=100,8,524901,2158177&h=100&date=2014-02-05&sln=17-18) 16:43:35 awesome, thanks! 16:43:39 any more on this? 16:44:02 thats it from my end 16:44:10 next is: 16:44:14 #link https://blueprints.launchpad.net/solum/+spec/specify-lang-pack Specify the language pack to be used for app deploy (devdatta-kulkarni) 16:44:31 The updates on this are: 16:45:18 1) aratim has been doing great progress. code for the API part is almost done. she is continuing to work on the backend datamodel 16:45:46 there are patches for API part available for review. 16:46:25 2) need to touch base with gokrokve_ to understand if we need to work on adding artifact endpoints for solum in glance 16:46:51 that is all 16:47:14 devkulkarni: thanks. On #2 gokrokve_ mentioned this is J M1 code in Glance 16:47:22 so we will need something to use in the mean time 16:47:48 Does glance has versioning? 16:47:50 adrian_otto: yes. so that something will be essentially solum's db itself. 16:48:12 noorul: it has metadata on the entities stored on it, we could use that for a simple versioning scheme 16:48:36 i've the BP for the glance artifacts https://blueprints.launchpad.net/glance/+spec/metadata-artifact-repository 16:48:48 Are we going to support multiple versions in M1? 16:48:53 noorul: It will have versions in new API. But here are no versios in current Glance. You can use metadata tags, though. 16:48:57 I added you adrian_otto and gokrokve_ as subscribers and there is also the etherpad that gokrokve_ was talking about https://etherpad.openstack.org/p/MetadataRepository-ArtifactRepositoryAPI 16:48:58 stannie: WHOOT! 16:49:15 thanks for subscribing me 16:49:47 noorul: probably not multi-version in the initial milestone 16:50:00 ok 16:50:07 in all honesty I don''t think we have fully considered that question yet 16:51:09 ok, devkulkarni any more on this? 16:51:25 adrian_otto: no, that is all on this for now. 16:51:28 next is: 16:51:29 #link https://blueprints.launchpad.net/solum/+spec/logging Logging Architecture (paulmo) 16:51:34 Short update unless there is interest in diving deeper: We've had several community meetings on logging and context over the last week.  I think we are making progress towards a solution everyone can agree on.  May need another meeting or two to get something solid architected. 16:51:35 I know we have good progress on this one 16:52:20 thanks paulmo for facilitating the discussions on this. I felt it was productive. 16:52:27 #link https://blueprints.launchpad.net/solum/+spec/solum-zuul-integration Solum integration with Zuul (devdatta-kulkarni) 16:52:27 Glad to help! :) 16:53:01 adrian_otto: if I remember correctly, last time you had said you will combine this bp with the git-pull bp 16:53:15 in any case, the updates are what kraman provided earlier 16:54:06 #action remove https://blueprints.launchpad.net/solum/+spec/solum-zuul-integration Solum integration with Zuul (devdatta-kulkarni) from recurring agenda, to be combined with https://blueprints.launchpad.net/solum/+spec/solum-git-pull 16:54:16 need assignee 16:54:28 #action adrian_otto remove https://blueprints.launchpad.net/solum/+spec/solum-zuul-integration Solum integration with Zuul (devdatta-kulkarni) from recurring agenda, to be combined with https://blueprints.launchpad.net/solum/+spec/solum-git-pull 16:54:32 ok, there we go! 16:54:45 #topic M1 Completion 16:54:46 adrian_otto: cool. thanks! 16:54:54 Can we complete M1 in February? 16:55:02 I feel we are pretty darn close 16:55:17 lots of little bits here and there to tie up 16:55:17 there is one big missing piece of the puzzle 16:55:26 the 'deployment workflow'. 16:55:39 build part? 16:55:42 implemention of Java - Tomcat language pack did not surface - which blueprint is tracking that work 16:55:42 the bit that generated the heat template. 16:55:53 s/generated/generates/ 16:56:30 roshanagr: Actually paulczar posted a link to that code when we talked about this yesterday. It is in contrib, right? 16:56:35 roshanagr: good question. imo, we should discuss about the overall language-pack working group's work. the part you mentioned is being tackled as one of things in that working group. 16:56:58 adrian_otto: paulcz's was python 16:57:20 devkulkarni: yeah it would be good to talk about the status 16:57:31 it was funzo who owned it but he's fallen a bit behind 16:57:40 and tbh the zuul work blocks a lot of lp 16:58:01 ok, so we probably want a new BP to explicitly call out the component of the system that will do the Heat template generation, and kick off the deploy. 16:58:19 do we have to worry about docker integration in nova for M1 ? 16:58:20 here's the contribs that I talked about yesterday - https://github.com/stackforge/solum/tree/master/contrib/diskimage-builder 16:58:21 that should help fill the gap that devkulkarni is concerned about 16:58:26 adrian_otto: agree 16:58:31 https://blueprints.launchpad.net/solum/+spec/deploy-workflow 16:58:51 devkulkarni: our discussion last week re: plan updates i think is the blocking bit there 16:59:02 transition from plan version a -> plan version b in a controlled fashion 16:59:14 claytonc: yes. that discussion is part of it as well. 16:59:23 devkulkarni: thanks. I will review this, suggest edits, and get that targeted for M1. Any additional thoughts on this? 16:59:35 #link https://blueprints.launchpad.net/solum/+spec/deploy-workflow 16:59:44 claytonc: about lp work being blocked by zuul.. 17:00:07 could we identify exactly what is getting blocked? the reason I ask is, 17:00:33 devkulkarni: sorry, not blocked, just once we have a zuul flow the actual impl of a lp is a 5-10 minute thing 17:00:37 in tomorrow's git-integration meeting, we are planning to discuss an interim service that we should consider while zuul work is still being developed 17:00:41 with the work that paulczar and funzo have done 17:00:50 claytonc: oh okay. 17:01:03 devkulkarni: that BP is now Direction Approved, and targeted for M1 17:01:20 adrian_otto: great. thanks! 17:01:45 over time, sorry 17:01:49 thanks everyone 17:01:54 #endmeeting