Members present: Animesh, vogxn, _ps_, chipc, Humbedooh, jzb, widodh, sudhap, serverchief, ke4qqq
---------------- Meeting summary: ---------------- 1. Preface 2. Active Feature Release: Overall Status a. chipc start thread on the quality of 4.1.0 (jzb, 2) b. http://is.gd/api41bugs (jzb, 2) c. widodh to merge DEB packaging changes into 4.1 (cherry-pick) on Friday (chipc, 2) d. https://issues.apache.org/jira/browse/CLOUDSTACK-1515 (chipc, 2) 3. Active Feature Release: QA Status 4. Active Feature Release: Doc Status a. jzb send doc status to the ML (jzb, 4) 5. Active Feature Release: Additional Issues a. jzb start 4.1.0 marketing discussion on -marketing ML (jzb, 5) 6. Active Bug-Fix Release 7. Active Bug-Fix Release: Additional Issues 8. Master branch 9. Infra 10. Additional Items? -------- Actions: -------- - chipc start thread on the quality of 4.1.0 (jzb, 17:11:29) - widodh to merge DEB packaging changes into 4.1 (cherry-pick) on Friday (chipc, 17:15:37) - jzb send doc status to the ML (jzb, 17:34:03) - jzb start 4.1.0 marketing discussion on -marketing ML (jzb, 17:38:13) IRC log follows: # 1. Preface # 17:05:41 [jzb]: Good morning, afternoon, or evening as the case may be. Thanks for showing up, folks. 17:06:02 [jzb]: Let's get started with the standing agenda # 2. Active Feature Release: Overall Status # 17:06:20 [jzb]: chipc: you want to take it away? 17:06:31 [chipc]: sure 17:06:38 [chipc]: 2013-03-22 is supposed to be our first RC 17:06:46 [chipc]: as of right now, we have 7 outstanding blockers and 22 critical bugs for 4.1... that's a big number IMO 17:06:49 [chipc]: We need to bring the release criteria thread to a close 17:07:01 [chipc]: specifically, because I think it's going to matter when we evaluate readiness for 4.1 17:07:10 [chipc]: also sebgoa suggested a bug sprint... my thought is that this is a good thing, but I'm concerned about "code churn", so it will have to 17:07:11 [chipc]: be carefully orchestrated 17:07:25 [chipc]: packaging remains outstanding, and is concerning 17:07:25 [chipc]: not sure what to do about that 17:07:25 [serverchief]: chipc, where would i find list of bugs 17:07:40 [serverchief]: is that something send by Sudha on dev list? 17:07:47 [chipc]: serverchief: issues.a.o/browse/CLOUDSTACK 17:07:47 [ke4qqq]: serverchief: query it on jira 17:07:55 [chipc]: then search for "affects version" of 4.1 17:07:57 [serverchief]: got it 17:08:32 [chipc]: so basically, that's all I have for 4.1... concerned about bug counts, and concerned about how to do a bug "sprint" in a way that does more good than harm 17:08:41 [chipc]: topics that need to be worked out on the ML though 17:08:47 [chipc]: so for overview EOF 17:09:05 [jzb]: ke4qqq: any experience with bug sprints from Fedora? 17:09:18 [jzb]: without excess "churn" ? 17:09:27 [ke4qqq]: jzb: sure, but nothing that quells the concerns of chipc 17:09:43 [jzb]: I'm really concerned about the number of major bugs outstanding. 17:10:10 [ke4qqq]: I'm terribly concerned about the number of API bugs 17:10:10 [chipc]: ok, so perhaps we just need to do the sprint anyway... and figure out how to do regression testing after it 17:10:10 [jzb]: I don't think we necessarily have to close *all* bugs that are tagged major, but releasing with more than 100 seems bad. 17:10:25 [chipc]: ke4qqq: +1 to the API concerns 17:10:52 [chipc]: ok, how about this... we don't have a specific ML thread talking about the quality state of 4.1 started 17:10:53 [ke4qqq]: ACTION is going to triage a number of those bugs - many of them are really 4.2 bugs (add new UI functionality for instance) 17:11:00 [chipc]: I'll take that action, and we can work this on list 17:11:00 [sudhap]: chipc:QA just got unblocked on features and you will see more incoming 17:11:07 [sudhap]: so count that for bug sprints 17:11:09 [chipc]: sudhap: I was sure we would 17:11:29 [jzb]: #action chipc start thread on the quality of 4.1.0 17:11:44 [chipc]: jzb: thx - you beat me to it 17:12:06 [chipc]: actually, packaging may need to happen first 17:12:14 [chipc]: we are still outstanding on DEB packaging 17:12:27 [jzb]: #link http://is.gd/api41bugs 17:12:42 [ke4qqq]: chipc: I am tempted to merge what they have - so we find more problems sooner 17:12:50 [chipc]: I know widodh was working on it a bit, and noa helped a bit as well... but we need to bring it to closure 17:12:50 [jzb]: Looks like 17 API bugs outstanding, 17:12:58 [ke4qqq]: s/merge/have merged 17:13:13 [widodh]: chipc: here 17:13:27 [widodh]: I'm actually working on the packaging every day, the agent is at 98% 17:13:35 [chipc]: widodh: any thoughs on how we can help get that completed / tested? 17:13:42 [widodh]: haven't touched the management server, aka, haven't verified if it works yet 17:14:08 [widodh]: for now it's mainly just install the packages and see what goes wrong. We can create issues for everything, but most of the time the fixes are very small 17:14:22 [serverchief]: FYI: I can do QA on vmware related bugs.. please ping me if needed 17:14:30 [chipc]: widodh: can we merge current state into 4.1? 17:14:44 [chipc]: that will get the testers going 17:14:45 [widodh]: chipc: Let's do that on Friday, I'll cherry-pick the stuff 17:14:52 [chipc]: sudhap: what do you think? 17:14:53 [chipc]: widodh: ok 17:15:00 [sudhap]: sounds good 17:15:00 [widodh]: otherwise I'm afraid I'll get a lot of issue reports for what I already know 17:15:08 [chipc]: widodh: fair 17:15:31 [sudhap]: chipc:how about upgrade issues 17:15:37 [chipc]: #action widodh to merge DEB packaging changes into 4.1 (cherry-pick) on Friday 17:15:45 [chipc]: sudhap: specifically what issues? 17:16:22 [widodh]: sudhap: Upgrading is one of the things. For the agent (deb) has been dealt with 17:16:45 [sudhap]: are all features have upgrade included?? looks like packages are not enabled for upgrade ( this could be how we packaged internally and resolve this easily) but main concern is about features 17:16:45 [widodh]: agent.properties and log4j-cloud.xml are copied from /etc/cloud/agent to /etc/cloudstack/agent by the postinst files 17:17:00 [sudhap]: widodh: thanks for the upgrade 17:17:03 [widodh]: So that's what I'm testing the last couple of days 17:17:53 [chipc]: sudhap: so DEB packaging / upgrades can be a test focus after the commits hit 4.1 on Friday 17:18:00 [chipc]: sudhap: are there upgrade issues for RPMs? 17:18:17 [sudhap]: sure 17:18:45 [sudhap]: this is the first attempt on upgrade - CLOUDSTACK-1515 17:18:52 [sudhap]: that blocked QA to go any further 17:19:02 [sudhap]: lot of features require upgrade to be done to close the feature validation 17:19:08 [sudhap]: that is why we are looking in to that 17:19:30 [jzb]: CLOUDSTACK-1515 17:20:04 [vogxn]: issue :) 17:20:10 [chipc]: ke4qqq: I don't think it's enabled in this channel 17:20:10 [vogxn]: nm 17:20:10 [jzb]: I thought Humbedooh enabled it? 17:20:10 [chipc]: sudhap: ok - so we have widodh's thoughts on upgrades for DEB 17:20:10 [jzb]: ACTION dimly recalls using it in a prior meeting 17:20:10 [Humbedooh]: no, that was for #cloudstack and #cloudstack-dev 17:20:18 [jzb]: ah, dang 17:20:28 [chipc]: sudhap: we need to get an update from Hugo 17:20:32 [chipc]: for RPM 17:20:47 [ke4qqq]: sudhap: who's rpms are being used for that? 17:21:34 [ke4qqq]: and where did install.sh come from? are you using Hugo's spec file to build packages - I put obsoletes and provides in to deal with upgrades. 17:21:41 [Humbedooh]: nvm, it is enabled for #cloudstack-meeting, must be something up with JIRA 17:21:47 [sudhap]: ke4qqq - using citrix built ones but those are dependent on hugo's 17:22:02 [sudhap]: once he checks in will be picking that up 17:22:18 [ke4qqq]: sudhap: I'll test after lunch and see whats up 17:22:25 [vogxn]: ke4qqq: those include the nonoss bits packaged into a simple installer script. i don't think there is much difference between what' s on jenkins and what' internal. just that a localinstall is done from a temp repo. 17:22:25 [chipc]: #link https://issues.apache.org/jira/browse/CLOUDSTACK-1515 17:23:19 [ke4qqq]: vogxn: ok - I'll figure it out this afternoon. 17:23:26 [chipc]: ok, so that's I guess a wrap on packaging? 17:23:40 [vogxn]: ack 17:23:40 [jzb]: OK 17:23:50 [jzb]: chipc: wrapped on overall/feature status? 17:23:54 [chipc]: yes 17:24:02 [chipc]: QA discussion time # 3. Active Feature Release: QA Status # 17:24:47 [sudhap]: First topic: Want to discontinue QA Scrum and will roll that in to this meeting 17:24:55 [sudhap]: so request all QA to join this mtg going forward 17:25:26 [chipc]: sudhap: that seems reasonable 17:25:47 [sudhap]: Second topic: Blockers - pl do drive them to conclusion - QA is finally unblocked and in a good momentum - don't want to get blocked again 17:25:49 [chipc]: sudhap: are you going to suggest that on the ML? 17:26:02 [sudhap]: chipc: yes 17:26:10 [chipc]: thx 17:26:32 [sudhap]: Third topic: I am gonig through all features and cleaning them up i.e closing and requesting info is something is pending 17:26:54 [sudhap]: by 3/22 we should close QA tasks for new features/improvements 17:27:47 [chipc]: sudhap: that's great news... 17:27:55 [sudhap]: Forth topic: can the bug sprint include testing as well or is it going to be only fixing 17:28:11 [chipc]: sudhap: well, we don't know what it is or how it will work yet, so sure! 17:28:24 [vogxn]: should include testing IMO. close and resolve as much as QA can 17:28:24 [serverchief]: my trouble with some of QA items, its hard to get the master branch functional sometimes 17:28:32 [ke4qqq]: sudhap: do you really want to merge with this meeting or is a dedicated QA meeting better? (not suggesting either way, just wondering - you're doing the work, so decision is yours) 17:28:58 [jzb]: is that going to substantially increase the length of this meeting? 17:29:02 [chipc]: serverchief: 4.2 discussion is coming up during the "master branch" topic 17:29:18 [sudhap]: My intention is to include 1 day for validation of a feature or certain area of the product to get feedback but we have only 4 weeks left so not sure if that would benefit but it can continue beyond 4.1 17:29:22 [jzb]: ACTION doesn't know how long the QA meetings last 17:29:22 [serverchief]: thanks chipc 17:29:22 [chipc]: ke4qqq: IMO, the QA calls are fast and status focused 17:29:37 [chipc]: jzb: I like sudhap's idea to bring those folks into this folkd 17:29:44 [jzb]: OK 17:29:52 [jzb]: I'm not opposed - just curious 17:29:52 [chipc]: we have to keep the pace up, and not go down rabbit holes 17:30:07 [vogxn]: me too. qa should join the meeting. 17:30:10 [chipc]: makes being the meeting moderator more important ;-) 17:30:31 [jzb]: speaking of moderating... 17:30:35 [jzb]: are we done with the QA topic now? :-) 17:30:42 [vogxn]: we'll learn to keep pace up. we have 20 ppl at most. when it becomes a 100 we'll think about splitting meeetings :) 17:31:20 [jzb]: going once, twice... # 4. Active Feature Release: Doc Status # 17:31:41 [jzb]: OK, so we had a doc sprint last week that closed out several bugs 17:31:56 [jzb]: I was pleased with the turnout for the first meeting, but we can certainly do better 17:32:13 [jzb]: I sent a note to the ML about another sprint this Friday 17:32:27 [jzb]: we have a number of unassigned bugs that need to be picked up 17:32:41 [jzb]: otherwise several features will be undocumented when we ship 4.1.0 17:33:11 [chipc]: ACTION doesn't like that! 17:33:18 [jzb]: I'm on the install, release notes, and a few others. I hope to have the install guide done for review by Friday 17:33:20 [jzb]: ACTION doesn't like that either. 17:33:48 [jzb]: I'll send a status update to the list after the meeting 17:34:03 [jzb]: #action jzb send doc status to the ML 17:34:11 [jzb]: that's it from me on docs. Anybody else? 17:34:33 [chipc]: jzb: I think that the install guide may end up with some tweaks after packaging is cleaned up... right? 17:34:48 [jzb]: chipc: almost certainly 17:35:11 [jzb]: but I want to get it as far as possible and tweak as necessary 17:35:33 [chipc]: indeed 17:35:33 [chipc]: ok 17:35:33 [chipc]: sorry 17:35:48 [chipc]: we can move on! 17:35:48 [jzb]: groovy # 5. Active Feature Release: Additional Issues # 17:36:04 [jzb]: any additional issues we need to touch on for 4.1.0? 17:36:56 [chipc]: not this week... but once we get closer to an RC I'd like to start having marketing related planning 17:37:11 [jzb]: chipc: do we want to do that here or a separate meeting? 17:37:18 [jzb]: IIRC we were going to have a separate meeting for that. 17:37:18 [chipc]: in the ML will be a good place 17:37:33 [jzb]: chipc: which ML? 17:37:33 [chipc]: I'm talking about specific to 4.1.0 17:37:33 [jzb]: :-) 17:37:42 [chipc]: and cloudstack-marketing@i.a.o 17:37:48 [jzb]: OK 17:38:01 [jzb]: I can take that, at least as far as starting the discussion, etc. 17:38:13 [chipc]: but I think release marketing is a topic for a feature release, worth discussing here in this meeting when we are in that phase of the release cycle 17:38:13 [jzb]: #action jzb start 4.1.0 marketing discussion on -marketing ML 17:38:43 [jzb]: chipc: we can try that. I fear a marketing discussion may consume the entire hour. 17:39:13 [chipc]: status then, not actual debate 17:39:15 [jzb]: OK 17:39:36 [jzb]: Moving on... 17:39:43 [chipc]: IMO, it's a topic that's part of the release process... and will have actions, tasks, etc... hence why I suggested it 17:40:06 [jzb]: chipc: sure. # 6. Active Bug-Fix Release # 17:40:46 [jzb]: We currently have two blocker bugs for 4.0.2 17:41:09 [Animesh]: jzb: I am following up with Abhi, he has not responded yet 17:41:16 [jzb]: OK 17:41:33 [jzb]: One is unassigned (CLOUDSTACK-528) and one is assigned but no activity (CLOUDSTACK-1151) 17:41:46 [Animesh]: Sudha and I have been syncing up daily on 4.1/4.2 blockers and criticals, we will include 4.0.2 as well 17:42:24 [jzb]: I've tried reaching the developer directly, but have had no response, I'm going to send to the list today and see if we can get someone to pick those up. 17:42:41 [jzb]: Animesh: that shouldn't preclude you from working the issue as well 17:43:08 [Animesh]: yes I know I am expecting a response soon 17:44:10 [jzb]: that's the status of 4.0.2 at the moment. 17:44:31 [jzb]: In general, I don't really feel like people are prioritizing the bug fix releases 17:45:09 [chipc]: ACTION feels that way about bugs generally 17:45:16 [ke4qqq]: ACTION agrees with chip - not a 4.0.2 problem 17:45:18 [jzb]: chipc: were are we at with wrapping up the release / support discussion? 17:45:26 [jzb]: or should that be directed at ke4qqq ? 17:45:45 [chipc]: jzb: or directed to the group as a whole 17:45:52 [chipc]: it's not wrapped up obviously 17:45:59 [chipc]: we need to bring to conclusion 17:46:01 [jzb]: chipc: right, I just meant I forgot who started the thread # 7. Active Bug-Fix Release: Additional Issues # 17:46:51 [jzb]: any additional issues for 4.0.2? 17:47:14 [chipc]: jzb: actually tied to 4.0.1, but related to 4.0.2 17:47:36 [chipc]: ke4qqq: hate to ask, but is there a way we can get the non-oss build loaded into widodh's repo? 17:48:14 [chipc]: and actually, we probably need that process doc'ed somewhere so that someone remembers and knows how to and has access to (etc...) do it for 4.0.2 and 4.1.0 17:48:26 [chipc]: even though it's not official 17:48:26 [chipc]: it's used 17:48:56 [ke4qqq]: chipc: it's on my todo list 17:49:04 [ke4qqq]: I've just not been getting it done 17:49:27 [chipc]: we all have lots to do, so no harm... was just thinking about how we can make it easier 17:49:27 [ke4qqq]: in general the process is documented in the install guide (tho clearly not the nonoss bits) 17:49:56 [chipc]: access I guess is the outstanding question 17:50:26 [ke4qqq]: yeah - I don't think I even have access to it - I send wido a link to a tarball of the repo 17:50:56 [chipc]: ah 17:51:03 [chipc]: ok, well that'll work too 17:52:28 [jzb]: any other issues? 17:52:58 [jzb]: OK # 8. Master branch # 17:53:13 [jzb]: any issues for the master branch this week? 17:53:35 [chipc]: serverchief: you had one 17:54:05 [Animesh]: Well build breakage is troubling 17:54:29 [Animesh]: I see three build break emails this morning 17:54:35 [_ps_]: +jzb: So there was a issue until yesterday that no one was able to add a basic zone successfully from the UI coz of the IPv6 changes....it's now resolved and committed to master ! Perhaps QA didn't happen to notice this ! 17:55:29 [vogxn]: Animesh: there's a problem with those emails 17:55:38 [vogxn]: they're delayed because of starving executors on builds.a.o 17:55:47 [vogxn]: so some emails reach 5 hours after the actual break 17:55:58 [vogxn]: i emailed builds.a.o seeking help on that 17:56:05 [vogxn]: will have an update may be in a few days 17:56:26 [ke4qqq]: vogxn: I've stood up another jenkins instance - and have plenty of capacity for builders 17:56:35 [Animesh]: I also see messages in build that Maven JVM terminated unexpectedly with exit code 143 17:57:03 [vogxn]: ke4qqq: nice! olamy mentioned tehre were no nexus proxy speeding up builds. so we could use the local jenkins 17:57:43 [serverchief]: chipc, my issue is in general, its really hard to get something tested on master branch 17:58:03 [chipc]: serverchief: so we're discussing that same issue then 17:59:38 [vogxn]: so i'm trying to enable the devcloud-ci as well so we have some defense. 17:59:46 [vogxn]: that's one item i'm working on towards making master a little stable 17:59:53 [vogxn]: so if something breaks on it. i'll file a blocker :) 18:00:01 [serverchief]: one other master branch concern - which applies to source code in general 18:00:13 [serverchief]: can we make db name usage dynamic 18:00:30 [serverchief]: its does not really work when you change the configs 18:00:51 [serverchief]: since many sql files reference "cloud" as a db name 18:00:51 [vogxn]: what do you mean db name usage? 18:00:59 [vogxn]: ah 18:01:08 [serverchief]: i'd like to run many versions of CS on the same host 18:01:39 [serverchief]: VS having 1 CS version per host due to static name of db = cloud 18:02:28 [serverchief]: i wonder if anyone else see's that or had this issue.. 18:02:56 [vogxn]: that would be a new feature IMO 18:03:56 [serverchief]: i c.. i will file an enhacement request 18:05:29 [jzb]: anything else on this topic? 18:05:37 [serverchief]: eof for me 18:05:58 [jzb]: OK # 9. Infra # 18:06:08 [jzb]: any Infra topics to discuss that we haven't touched on? 18:07:06 [jzb]: OK # 10. Additional Items? # 18:07:21 [jzb]: any additional items? 18:08:07 [serverchief]: what is the take on running CS spins 18:08:35 [serverchief]: i recall Chip and David gave good overview 18:08:56 [serverchief]: basically, i will be merging some features of 4.1 and 4.2 18:09:43 [serverchief]: should this be separate project apart from ASF 18:09:56 [serverchief]: or can we have a branch in git 18:10:18 [ke4qqq]: please do it separately. 18:10:42 [serverchief]: got it.. will do 18:10:48 [ke4qqq]: and please do take chips admonition to becareful with the cloudstack trademarks (or even not use them) 18:11:03 [serverchief]: i'll reach out prior to be sure all is proper 18:11:26 [serverchief]: EOF 18:12:41 [jzb]: OK 18:12:43 [jzb]: I think that's it for today 18:12:48 [jzb]: thanks everybody!
