16:00:58 #startmeeting Solum Team Meeting 16:00:59 Meeting started Tue Feb 11 16:00:58 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:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:03 The meeting name has been set to 'solum_team_meeting' 16:01:52 #link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2014-02-11_1600_UTC Our Agenda 16:02:01 #topic Roll Call 16:02:04 Adrian Otto 16:02:06 Paul Montgomery 16:02:08 murali allada 16:02:09 Pierre Padrixe 16:02:10 Paul Czarkowski 16:02:10 Julien Vey 16:02:15 Nikita Marchenko, Mirantis 16:02:25 Devdatta 16:02:35 Rajdeep Dua 16:02:41 Noorul Islam 16:02:54 Swapnil 16:03:44 hello everyone 16:04:09 feel free to chime in at any time to record your attendance if you have not already 16:04:18 #topic Announcements 16:04:34 we have selected a date for our upcoming for Solum Summit 16:04:40 two dates, actually 16:04:50 Tuesday, March 25, 2014 16:04:50 Wednesday, March 26, 2014 16:05:16 Red Hat has offered to host us in North Carolina 16:05:29 we will get you additional details on the specifics soon 16:05:39 so that you can plan your travel arrangements. 16:06:13 for those of you planning to attend remotely, please earmark your time on these dates to ensure your availability 16:06:39 next up, I created a bunch of new blueprints for the various API resources 16:06:58 they don't have details in them. If you are interested, links to them are in the agenda 16:07:11 adrian_otto: thanks for creating these!! 16:07:24 adrian_otto: Good :) 16:07:32 You can thank me once I've put the grinding hours into fleshing each one out ;-) 16:07:49 the good news is that we actually have code for all of these already 16:07:55 so this is not a lift from zero. 16:08:06 true. 16:08:24 but this gives us a place to focus design work in a place with more narrow scope 16:08:45 ok, next topic 16:08:47 #topic Review Action Items 16:08:55 * adrian_otto adrian_otto to hold a vote for next F2F location 16:09:01 Status: Completed 16:09:09 * adrian_otto 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:09:17 Status: Completed 16:09:22 although I have a question about this 16:09:28 yes.. 16:09:35 kraman owned the second 16:09:43 and devkulkarni owned the first 16:09:54 who should I ask for the updates for the combination of the two? 16:10:21 adrian_otto: I think anyone of us can give updates. we are working together on this. 16:10:32 ok 16:10:44 and our last action item 16:10:46 * adrian_otto kraman to submit zuul work into Gerrit as WIP for review. Tests to be added as they are created. 16:10:55 I think kraman is out today. I can give an update on this. 16:11:03 ok 16:11:46 I am going to work with kraman today/tomorrow to start submitting WIPs for review. I have more updates which I can give now or when we go to BP status discussion. 16:12:10 ok, so I should resubmit this as an open action for this week, correct? 16:12:21 yes, that makes sense 16:12:21 should I keep it assigned to kraman, or assign it to devkulkarni? 16:12:36 for now I would say lets keep it assigned to kraman.. 16:12:47 #action kraman to submit zuul work into Gerrit as WIP for review. Tests to be added as they are created. 16:12:50 I will check with him if we want to reassign it 16:12:56 ok, so I will revisit that next week for status. 16:13:03 sounds good. 16:13:14 ready to begin Blueprint updates? 16:13:21 #topic Review Blueprints: https://launchpad.net/solum/+milestone/milestone-1 16:13:31 #link https://blueprints.launchpad.net/solum/+spec/api Solum API (aotto) 16:13:57 there has been a lot of progress on this. Many reviews were posted over the past two weeks to add methods to the api, and wire them to the db layer 16:14:10 I also created 7 new blueprints for the API 16:14:22 which I will report status on at this position in the agenda. 16:14:40 feel free to claim those blueprints if you have open reviews against them 16:14:53 also, please resubmit your commit messages to reference these blueprints 16:14:59 about that.. 16:15:09 devananda: yes? 16:15:15 devkulkarni: yes? 16:15:20 has anyone figured out why blueprint links in the commit message do not go to solum project? 16:15:21 sorry devananda 16:15:41 Yes! 16:15:55 that happens because the blueprint slug does not start with the word solum 16:16:03 so they are not necessarily unique 16:16:16 all of the ones I create are properly named, so that should work properly for you 16:16:22 I thought it is because solum is not yet part of openstack 16:16:39 also, I have been renaming them as I approve them to prevent this from continuing with new ones 16:16:59 no, it's a quirk about the way that Gerrit links to Launchpad 16:17:09 adrian_otto: That seems to be incorrect, See https://review.openstack.org/#/c/71923/ 16:17:41 noorul: oh, I see. 16:18:16 I remember asking this question initially to infra and they said it is because we are not part of openstack yet 16:18:21 ok, so that should work at such time that this project enters an incubation phase 16:18:37 ok, sorry for the misinformation before 16:19:08 so I still want to have the references in the commit messages 16:19:13 so in the interim, do we put direct links in the commit message? I think gokrokve_ did that for some of his patches 16:19:17 even if the links do what they do now 16:19:29 we can put both in 16:19:50 another option is to put a comment in as you submit the patch that has the full link 16:20:11 that way you won't run into the caracter maximum for a line in the commit message 16:20:22 s/caracter/character/ 16:20:38 okay. that would work. 16:20:41 more thoughts on the API work? 16:20:49 I will mention... 16:21:05 Are all these APIs required for M1? 16:21:10 muralia has stepped up to help with fleshing out the API for the enablement of the CLI tool 16:21:26 not all capabilities of all resources are required for M1 16:21:39 I will make it clear in the blueprint descriptions wich parts are essential 16:21:59 we need to be able to create/modify/delete plans and assemblies 16:22:09 and list assemblies 16:22:11 I think it is right time we come up with the list of items we should concentrate for M1 16:22:16 that should be enough to start 16:22:31 adrian_otto: noorul has shown the way of how to do this, muralia is taking it from there. (btw, that is the update for the next bp) 16:22:34 noorul: I agree completely. We ahve an agenda item for that 16:22:36 for today 16:22:54 nice segway devkulkarni 16:22:55 #link https://blueprints.launchpad.net/solum/+spec/solum-minimal-cli Command Line Interface for Solum (devdatta-kulkarni) 16:23:11 submitted around 6 patches last week 16:23:11 :) thanks noorul. thanks muralia 16:23:19 sure 16:23:28 noorul: awesome stuff!! 16:23:46 Thanks 16:24:05 I was thinking whether we should add functional tests 16:24:07 noorul: +1 Thanks! 16:24:38 on the subject of the functional tests... 16:24:41 noorul: what do other projects do? 16:25:01 They have it in tempest, but some read only operations alone 16:25:01 other projects really don't test much, as the tests for the CLI are relatively low value 16:25:23 Trove for example just runs the cli script to cause it to emit the API version 16:25:36 and does a string check against that to be sure it's the expected string value 16:25:38 what do recent projects like Heat do? 16:25:43 and that's the extent of the test 16:26:11 let us not add it now 16:26:15 I have another question 16:26:18 https://etherpad.openstack.org/p/MinimalCLI 16:26:27 I think it's a pretty low value test, so we should focus on features 16:26:39 It just talks about assembly and app 16:26:58 What about other resources? 16:27:18 those are the two essential to basic operation 16:27:21 Am I missing something? 16:27:22 app = plan 16:27:47 so if we have plans and assemblies working, we can demonstrate simple end-to-end functionality 16:27:49 How can I define component, lang pack ,etc? 16:27:59 good question... 16:28:08 components get defined by Solum when interpreting the plan 16:28:30 and the first language pack can be pre-loaded in the base distribution 16:28:51 We should take a second look and see if this etherpad has everything required for M1. I can do that and update it in the next few days as I start work on the CLI 16:29:27 I see 16:29:29 muralia: are you willing to take that as an action item? 16:29:34 yes 16:29:40 I would love your help with that 16:29:52 sure. I'll do that 16:30:02 It will be great if you can provide an example 16:30:18 #action muralia to review https://etherpad.openstack.org/p/MinimalCLI to verify that everything for M1 is tracked, and placed into the appropriate blueprints. 16:30:23 How user will invoke assembly create with all those data? 16:30:46 #action adrian_otto to support muralia for review of https://etherpad.openstack.org/p/MinimalCLI 16:31:14 noorul: sure. i'll provide examples 16:31:18 noorul: what data are you concerned about? 16:31:35 muralia: ok thanks 16:31:52 adrian_otto: How do we pass all these info in command line 16:31:58 the info placed into the plan file is what we use as input 16:32:08 adrian_otto: Oh I se 16:32:13 adrian_otto: got it 16:32:14 that goes into the plan, and is subsequently given to the assembly 16:32:18 ok, good 16:32:29 any mote on this topic? 16:32:30 more 16:32:35 I am good 16:33:07 Next is two blueprints combined as a single update subject 16:33:09 #link https://blueprints.launchpad.net/solum/+spec/solum-git-pull Pull integration of Solum from an external Git repo (kraman) 16:33:09 #link https://blueprints.launchpad.net/solum/+spec/solum-zuul-integration Solum integration with Zuul (devdatta-kulkarni) 16:33:18 I have following updates: 16:34:00 1) For Solum specific changes we had to modify Zuul's scheduler. I have added tests to those. 16:34:28 2) I am working with kraman to split the code and tests into patches to be submitted to Zuul repo 16:34:30 claytonc: wlecome. devkulkarni is giving us the update on Git pull and Zuul 16:34:50 sorry about the delay 16:35:10 3) We still need tests to be added for the changes to the layout in Zuul. Will be working with coolsvap to get those in 16:35:21 4) We discussed about an 'interim service'. 16:35:38 There is not a concrete plan yet about how to build it, but.. 16:36:12 devkulkarni: correct me if i'm wrong but we hypothesized not needing an interim service because we could fill that role via the hooks 16:36:13 yesterday asalkeld seemed to be thinking along those lines as well and he said he will create a wiki page with his thoughts/ideas etc. I am planning to get this to tomorrow's git-integration meeting 16:36:41 will take that to the meeting tomorrow though 16:36:53 claytonc: cool. we can discuss more then. 16:37:00 adrian_otto: that is all. 16:37:08 ok, let's get that wiki linked as the design to the "https://blueprints.launchpad.net/solum/+spec/solum-git-pull/+edit" of the blueprint 16:37:20 sure. 16:37:38 ok, also, I'd like to have you add the link to the breakout meetings into our agenda here 16:37:46 I think that will help us follow along 16:38:10 okay. can do that from next time 16:38:19 so as soon as you generate the chat log.minutes, please add them to https://wiki.openstack.org/wiki/Meetings/Solum 16:38:36 that way I can link to them in the subsequent team meeting so they become more visible to the wider audience 16:38:48 sounds good. 16:38:55 I think we are already recording those on the breakout meeting wiki page, right? 16:39:16 if not, we should get back into that habbit 16:39:19 I will have to double check.. 16:39:30 i'm pretty sure they are 16:39:37 but we missed one meeting and rescheduled another 16:39:38 not critically important, but it would be nice for the full history to be linked there 16:39:40 will follow up 16:40:32 #action claytonc t make sure that https://wiki.openstack.org/wiki/Solum/BreakoutMeetings links to all logs and minutes from breakout meetings we have held 16:40:41 thanks claytonc 16:40:58 more on this topic? 16:41:23 #link https://blueprints.launchpad.net/solum/+spec/specify-lang-pack Specify the language pack to be used for app deploy (devdatta-kulkarni) 16:41:30 Here are the updates on this: 16:41:59 aratim has been making great progress on the data model definition, which was the remaining part of this work. 16:42:23 btw, thanks claytonc for discussions the other day about the data model 16:42:57 another thing is.. we need to start including the plan work either in this bp or discuss it as part of some other bp. 16:43:14 devkulkarni: agreed 16:43:30 which plan work do you mean, devkulkarni? 16:43:31 the title of the bp is 'specify-lang-pack'. what aratim is part of the story — 'get the list of available lang-packs'. 16:43:49 adrian_otto: the work that asalkeld has done on the plan API. 16:44:10 *aratim's work is part of the story of this bp 16:44:59 I am currently working on connecting the lang pack API to the DB 16:45:11 we could rename this bp to something like 'get-lang-pack' and then it should be fine 16:45:25 since there is already a bp for plans 16:45:32 devkulkarni: perhaps we could land that on https://blueprints.launchpad.net/solum/+spec/solum-api-plan 16:45:34 +1 devkulkarni 16:45:53 wait 16:46:10 let's not rename a bp that we have linked to in prior meeting minutes 16:46:18 oh right!! 16:46:24 if we need another BP, we can make a new one 16:46:58 I can create a new bp and link it to the specify-lang-pack bp. 16:47:14 sounds like it would be one that depends on the current blueprint 16:47:30 scope of this BP - defining how plans change as language packs generate DU's, and how plans are used to create templates? 16:48:15 #action devkulkarni to make a new blueprint for language pack selection that would have a dependency link relation with specify-lang-pack 16:48:21 claytonc: actually, no. I was referring to a BP that will capture the work that aratim is doing. 16:48:44 ah 16:48:59 ok, ready to advance to the next item in the agenda? 16:49:01 adrian_otto: that is all 16:49:14 #link https://blueprints.launchpad.net/solum/+spec/logging Logging Architecture (paulmo) 16:49:23 After much discussion and design, I created a new pull request for logging/trace: https://review.openstack.org/#/c/71970/ 16:49:23 If folks like Angus, kgriffs, gokrokve and anyone else interested could take a look at it and give feedback, I would appreciate it. 16:50:01 thanks for putting that together, paulmo! 16:50:21 questions on that item? 16:50:31 trace_test.py can be run to see an example with lots of comments inline. 16:50:45 thanks paulmo. 16:50:48 #topic M1 Completion 16:50:54 Do we have all gaps addressed? 16:51:15 adrian_otto: Deployment workflow bp is missing in the list of BP updates. 16:51:29 Roshan is working on a new wiki page that further describes the ideal end-to-end user experience 16:51:46 devkulkarni: yes, let's get that in there now 16:52:00 actually, running low on time 16:52:03 I will take an action 16:52:19 I can give brief update on it. asalkeld is progressing on it.. 16:52:34 #action adrian_otto to add Deployment workflow bp to our subsequent agenda for review updates 16:52:46 devkulkarni: yes, please 16:52:53 ^^ 16:53:09 ok, so back to M1 completion 16:53:21 any other gaps that need our focus? 16:53:36 are we good on devstack setup? 16:53:49 how would someone try out solum end-to-end? 16:53:58 top priorities are getting minimal implementaitons of the CLI and Git integration working with a simple plan and have Solum create an Assembly 16:54:23 paulczar: what do you think on the devstack question? 16:54:53 whom are we targetting M1 with? 16:55:16 noorul: M1 should be suitable for a public demo 16:55:17 there are scripts in contrib for the hookup to devstack 16:55:21 M1 requires to run keystone and glance 16:55:28 to illustrate the concept of Solum 16:55:41 as long as we keep those up to date as we build on solum we should be okay with devstack integration 16:56:09 we might also have a dependency on swift 16:56:15 I think it is always easy to use devstack if we have multiple services to run 16:56:25 the vagrantfile in the solum-dev repo on rackerlabs does the hookup when it starts devstack 16:56:28 noorul: agreed 16:56:37 we will also have dependency on heat (and may be zuul) 16:57:01 #topic Open Discussion 16:57:03 so zuul is independent of devstack 16:57:26 we have a few minutes remaining, so we can continue on this, or bring up any other topics 16:57:40 I have one question 16:57:47 noorul: if someone want to try end-to-end, they would need zuul setup. I was thinking it can be made part of devstack, like other services 16:57:54 noorul: proceed 16:58:02 How early can we start applying for incubation? 16:58:20 noorul: good question. 16:58:45 I suppose that if we want to pursue incubation, it's never too early to publicly state that as an intent of ours 16:59:12 and when we all feel we are ready to apply, in terms of functionality… then we can do that 16:59:27 anyone have objections to stating an intent to file for incubation? 16:59:34 devkulkarni: correct, I think we would need to add scripts in contrib/devstack/lib/solum to install/start external tools such as zuul 17:00:01 paulczar: So that needs a bp 17:00:07 noorul: we could adjust that part of our Wiki to make that intent more clear. 17:00:18 adrian_otto: ok 17:00:24 anyone agree? 17:00:25 adrian_otto: Should we ask M? 17:00:28 ML? 17:00:38 let;s put it on next weeks agenda 17:00:48 so we can ave a good discussion about it 17:01:02 adrian_otto: ok, thank you! 17:01:06 noorul: good point about bp 17:01:13 #action adrian_otto to add incubation discussion to next agenda 17:01:18 thanks everyone! 17:01:23 #endmeeting