Summary of IRC meeting in #cloudstack-meeting, Wed Apr 3 17:04:15 2013

[ASF IRC Services <as...@wilderness.apache.org>]

Members present: sangeetha, jzb, topcloud, vogxn, sudhap, chipc, kdamage, widodh

----------------
Meeting summary:
----------------

1. Preface

2. 4.1 overall status

3. 4.1 QA updates

4. 4.1 docs

5. 4.1 other items

6. master branch
  a. vogxn to notify the ML about how to test via BVT prior to a push (chipc, 6)

7. other topics


--------
Actions:
--------
- vogxn to notify the ML about how to test via BVT prior to a push (chipc, 17:36:09)

IRC log follows:


# 1. Preface #
17:04:44 [chipc]: so we might have a light meeting today, given that the citrix folks are in a $dayjob meeting
17:04:59 [chipc]: but we'll do the usual - start with 4.1, then discuss master and then other topics
17:05:00 [chipc]: so...


# 2. 4.1 overall status #
17:05:21 [chipc]: We're close with 4.1 to an RC
17:05:36 [chipc]: as it stands now, we have 1 blocker: CLOUDSTACK-1877	
17:05:51 [chipc]: and 4 critical bugs
17:06:08 [chipc]: CLOUDSTACK-1877
17:06:21 [chipc]: widodh: I assigned that one to you, given your comments
17:06:29 [chipc]: are you doing ok with the fix?
17:06:36 [widodh]: chipc: Yes, I'm working on that one
17:06:45 [chipc]: excellent...  any ETA?
17:06:53 [widodh]: seems a packaging issues and the mgmt server opens a wrong db.properties
17:07:37 [chipc]: is it the type of bug that will take a day or so?  or perhaps today?
17:07:44 [widodh]: chipc: I think I have it "fixed" locally
17:07:51 [kdamage]: goodmorning
17:07:51 [chipc]: excellent - so you're just testing the fix before pushing
17:07:59 [chipc]: good deal
17:07:59 [widodh]: I'm not sure, it seems like a encryption issue. Not sure what it is yet
17:08:06 [chipc]: hm
17:08:06 [widodh]: chipc: I just disabled encryption and everything works
17:08:16 [widodh]: chipc: It also fixed my agent issues, with them not connecting
17:08:29 [chipc]: alrighty then...  I guess shout on the ML if you need help
17:08:44 [chipc]: oh good, I was going to ask about the agent connection issue too
17:08:46 [chipc]: ok, next one
17:08:47 [chipc]: CLOUDSTACK-1837
17:08:52 [widodh]: chipc: Was planning on doing so.
17:09:06 [chipc]: jzb has that one, and it's really just the upgrade procedure
17:09:16 [chipc]: jzb: will perhaps ask you about docs generally in that topic
17:09:29 [chipc]: CLOUDSTACK-1842
17:09:51 [widodh]: chipc: Asking me about it?
17:09:59 [chipc]: widodh: no
17:10:14 [chipc]: 1842 is assigned to Abhi, but I haven't seen any updated in the ticket or to my ML questions about it
17:10:26 [chipc]: so we're still waiting to hear about 1842
17:10:46 [chipc]: CLOUDSTACK-1868
17:11:09 [chipc]: Sateesh has that one assigned, and again no updates on it
17:11:18 [chipc]: hopefully it can be looked at in the next day
17:11:31 [chipc]: last one:
17:11:31 [chipc]: CLOUDSTACK-1874
17:11:46 [chipc]: 1874 may not be a critical bug, given the comments
17:12:09 [chipc]: but I'm waiting to hear back from Kishan on if there is a fix or not that's easily applied
17:12:18 [chipc]: and that's it for the bug list...
17:12:31 [widodh]: chipc: About 1842, that's just a DB thingie
17:12:46 [widodh]: I've looked at it some months ago, but wasn't that special
17:12:48 [chipc]: widodh: check the ML for a thread where I asked about it
17:12:54 [chipc]: perhaps we can resolve easily
17:13:24 [chipc]: I'd be willing to make the fix, but I was looking for a response that it was the right way to do it
17:13:24 [topcloud]: chipc: I believe it can be resolved quickly.  region no longer keeps track of where an account is created.
17:13:39 [chipc]: topcloud: you mean 1874?
17:13:54 [chipc]: topcloud: I agree - I just need a patch to fix it
17:13:54 [topcloud]: yes...that's the current topic?
17:14:16 [chipc]: topcloud: we were jumping around a little
17:14:24 [widodh]: chipc: I'll check the ml regarding that. It's just that 1877 already took me a whole day today.
17:14:39 [chipc]: widodh: understood
17:14:46 [topcloud]: chipc: i'll take it up 1847.
17:14:49 [topcloud]: 1874
17:14:54 [chipc]: topcloud is 1874 as easy as just removing that column from the SQL?
17:15:01 [chipc]: topcloud: excellent...  thank you
17:15:03 [chipc]: assinging to you now
17:15:24 [chipc]: ok, moving on


# 3. 4.1 QA updates #
17:15:46 [chipc]: does anyone want to provide a 4.1 QA overview today?
17:16:01 [sudhap]: chipc: Upgrade testing is one that is being tested 
17:16:01 [chipc]: I know I just went through the bugs, but is there still testing outstanding?
17:16:09 [sangeetha]: I had started a tread on component.xml and db.properties for upgrade
17:16:09 [chipc]: sudhap: cool
17:16:19 [chipc]: sangeetha: ack - we need people to reply
17:16:39 [chipc]: topcloud / widodh: mind looking at sangeetha's thread?
17:16:46 [widodh]: chipc: sangeetha: db.properties is already fixed in both RPM and DEB
17:17:09 [widodh]: they copy the old one to the new location. components.xml is a lot harder, no way to merge that script-wise
17:17:19 [topcloud]: chipc: i did take a quick look.  it's a tough problem.
17:17:40 [chipc]: indeed, and if the solution is to simply provide upgrade instructions then that's what we have to do
17:17:41 [topcloud]: have to think about that a little bit.
17:17:47 [sangeetha]: So we document that users should manually keep their db.properties in sync ..? wanted to confirm 
17:18:01 [topcloud]: the main problem is how many people have edited components.xml?
17:18:01 [widodh]: sangeetha: No, the DEB and RPM will copy it for them
17:18:09 [topcloud]: is it something we really need to worry about?
17:18:17 [widodh]: and all other configuration they might have. It's just that components.xml completely changed
17:18:24 [chipc]: topcloud: I'd suggest that very few do, but that we need to put it in bold in the release notes
17:18:46 [topcloud]: chipc: agreed.  that might be the only solution.
17:19:09 [chipc]: topcloud: perhaps you can drop a simple description over to jzb for the release notes?
17:19:09 [sangeetha]: Dont know ..how important it is ..but wanted to dicuss since the component.xml is very different now
17:19:10 [topcloud]: chipc: I'll check with kelven again.  the thing i don't want to happen is for it to change again in the next release.
17:19:24 [chipc]: topcloud: +1
17:19:48 [topcloud]: I'll check with kelven to make sure he's got it exactly in the format he thinks it should be.
17:20:04 [sangeetha]: Sure ..I will add the db.properties and component.xml documentation step to existing doc bug - CLOUDSTACK-1837
17:20:27 [chipc]: sangeetha: ok
17:20:47 [chipc]: sudhap / sangeetha / vogxn / others...  any other 4.1 QA topics?
17:21:10 [vogxn]: none from my side. just merged the bvt branch. hope people start using it before checkin
17:21:26 [chipc]: vogxn: that's master branch... ;-)
17:21:34 [vogxn]: d'oh. yes
17:21:41 [vogxn]: out of context. apologies
17:21:42 [chipc]: ok, so let's move on and see if jzb can comment on docs


# 4. 4.1 docs #
17:22:04 [chipc]: jzb: are you free for a quick note about where docs are for 4.1?
17:22:26 [chipc]: 
ACTION waits for a minute

17:22:27 [jzb]: chipc: I'm working on Releaes Notes (still)
17:22:42 [jzb]: ran into a bit of a fun issue that we no longer generate a diff.txt of changes in the APIs
17:22:57 [chipc]: hmmm
17:23:05 [chipc]: need help with that?
17:23:07 [jzb]: if anybody who was working on the conversion from Ant to Maven has any idea how to resurrect this handy thing… I'd be very happy to know
17:23:34 [jzb]: chipc: yeah, otherwise I'm going to be picking through HTML docs manually
17:23:41 [jzb]: which … well, is going to take a while. 
17:24:07 [jzb]: I sent a note to dev@ yesterday, no responses so far
17:24:18 [chipc]: can you send me the "how" for how it was done before?  I'd be willing to try to figure it out
17:24:40 [jzb]: chipc: So, it was an automatic byproduct of generating the docs with Ant
17:24:42 [chipc]: ah
17:24:47 [jzb]: I don't know the "how" otherewise
17:24:48 [jzb]: er, otherwise
17:24:49 [chipc]: ok, I'll dig a little then
17:24:54 [widodh]: 
ACTION wants to note that I still think the docs could be a lot better. It's just that the time to fix them

17:25:09 [jzb]: widodh: specifics?
17:25:26 [jzb]: and yes, there's a lot that needs to be done, but it takes a fair amount of time.
17:25:31 [widodh]: jzb: Around the KVM hypervisor installation. Setting up agents. That cloud-setup-agent isn't required
17:25:39 [widodh]: How to do so with Puppet or Chef for example
17:25:46 [chipc]: widodh: we need to get ourselves more OSS docs folks to help out overall
17:25:54 [widodh]: chipc: +2
17:25:54 [jzb]: +1
17:26:11 [chipc]: ok, let's move on to the next topic


# 5. 4.1 other items #
17:26:39 [chipc]: so the only other item I'd note is that jzb posted a draft announcement to the marketing list for 4.1
17:26:54 [chipc]: and I see that Sony is playing with a banner image to use
17:26:56 [chipc]: all good stuff
17:27:02 [chipc]: any other 4.1 topics?
17:27:09 [jzb]: please take a look at the announcement
17:27:16 [jzb]: and give a +1 if it's OK, or suggestions if not.
17:27:24 [chipc]: jzb: ack
17:27:31 [jzb]: we could also use some blog posts about the new features...
17:27:32 [jzb]: I'm going to try to do a few.
17:27:40 [jzb]: but… we have ~10 exceptional new features
17:27:48 [jzb]: that should be more widely publicized.
17:28:01 [jzb]: EOF
17:28:01 [chipc]: thx
17:28:11 [chipc]: ok then, anything else about 4.1?
17:28:24 [kdamage]: I can do a brief on my blog and I'll push on the linkedin marketing machine
17:28:24 [widodh]: chipc: Packaging is still work-in-progress
17:28:31 [chipc]: widodh: really?
17:28:39 [widodh]: DEB is almost there I  think, but it's taking more time then expected
17:28:39 [chipc]: I thought that it was basically resolved now
17:28:54 [chipc]: since the QA folks have been testing it
17:28:54 [widodh]: chipc: Yes, 99% is resolved
17:28:56 [widodh]: but I found some little thingies
17:29:01 [chipc]: ah
17:29:02 [widodh]: during my hunt for 1877 today
17:29:39 [sudhap]: widodh:do you recommend to cover certain areas
17:29:42 [chipc]: so then just so we're all on the same page - I'm going to wait to hear from you specifically that you are good to go with DEB packaging before cutting a RC
17:29:56 [chipc]: widodh: ^^ was for you
17:30:01 [widodh]: sudhap: Management server
17:30:16 [widodh]: chipc: I understand. I'll try to work on them this week.
17:30:24 [chipc]: widodh: thx
17:30:31 [widodh]: I have a Webinar tomorrow and a talk on Saturday, so kind of packed
17:30:54 [chipc]: yup
17:31:09 [chipc]: 
ACTION would like to offload packaging to the distros at some point

17:31:09 [chipc]: ;-)
17:31:24 [chipc]: ok, next topic then


# 6. master branch #
17:31:39 [chipc]: I'll keep it general as master / 4.2
17:31:46 [widodh]: Don't break it!
17:31:46 [chipc]: anyone have topics to discuss?
17:31:54 [chipc]: widodh: +1
17:31:56 [topcloud]: is vogxn on?
17:32:01 [widodh]: If you commit, at least do a git clean, mvn clean and build before pushing
17:32:01 [sudhap]: chipc:there are several blokcers on master
17:32:02 [chipc]: vogxn: thanks for the BVT merge
17:32:02 [vogxn]: hi
17:32:09 [vogxn]: i'm here
17:32:24 [topcloud]: vogxn: with the bvt merge, when should we require people to run checkin tests?
17:32:57 [vogxn]: whenever they checkin they can run the tests
17:33:24 [chipc]: vogxn: I think it's time to codify that practice into a community policy
17:33:24 [topcloud]: so we can start today for example?
17:33:39 [topcloud]: +1
17:33:54 [vogxn]: yes. i've put the steps in to the how to build master branch wiki
17:33:56 [vogxn]: so i think we should start now
17:34:16 [chipc]: vogxn / topcloud: we need to have a ML discussion to ensure concensus on that proposal
17:34:24 [chipc]: which one of you wants to start that thread
17:34:25 [topcloud]: vogxn: then we should put that out to the ML.  do we need 72 hours before putting into practice?
17:34:31 [vogxn]: naah!
17:34:33 [chipc]: topcloud: we need concensus
17:34:34 [vogxn]: that's only for merge
17:35:09 [topcloud]: no, I'm thinking everytime they push to master, people have to run this step.
17:35:16 [vogxn]: yeah. it takes an additional minute
17:35:26 [chipc]: since we're really asking folks to do it, and not able to enforce, it's really all about educating people
17:35:31 [vogxn]: so it shouldn't be an overhead. i'll send out a note on the ML
17:35:39 [chipc]: and then reverting commits that break it
17:36:01 [topcloud]: vogxn: ok...thanks.  i'm going to be offline starting friday so i don't think i can wait for the consensus.
17:36:01 [vogxn]: or fix the tests that invalidate the run
17:36:09 [topcloud]: vogxn: thanks for doing it.
17:36:09 [chipc]: #action vogxn to notify the ML about how to test via BVT prior to a push
17:36:39 [chipc]: ok, let's move on
17:36:46 [chipc]: sudhap: want to talk about the blockers on master?
17:38:11 [sudhap]: chipc:would RM be following up on those as some are pending for sometime
17:38:39 [chipc]: sudhap: anyone can follow up on them...
17:38:47 [chipc]: wouldn't the tester be pestering the developer?
17:38:54 [sudhap]: chipc:sure
17:38:57 [sangeetha]: IPV6 feature blocked when testing with system generated templates..
17:39:01 [chipc]: or do we have bugs that are not really tied to a specific feature?
17:39:39 [chipc]: sudhap: I really want to get to a point where people blocked by somebody else are able to sort that out for themselves
17:40:16 [chipc]: coordinating on behalf of others is a low value activity IMO...  it's required sometimes, but bad to assume there needs to be a proxy
17:40:24 [sudhap]: chipc: agreed
17:40:40 [chipc]: Animesh is going to be RM'ing 4.2 though...  so if you need him to help pester, because of no repsponse, then get his help
17:40:46 [chipc]: ;-)
17:40:54 [widodh]: One thing I'd like to note about master
17:41:10 [widodh]: I believe nobody breaks master on purpose, but it blocked me a couple of times
17:41:24 [chipc]: it's blocked many folks
17:41:24 [widodh]: I spend hours with Hugo figuring out what went wrong.
17:41:26 [chipc]: quite frustrating
17:41:33 [widodh]: I couldn't spend those hours on development
17:41:46 [vogxn]: i think it's broken now :P
17:42:01 [topcloud]: widodh: thanks for your efforts!
17:42:09 [widodh]: topcloud: Your welcome :)
17:42:16 [chipc]: vogxn: indeed, I think it's tied to that unit test taht requires a DB
17:42:24 [vogxn]: midonet.
17:42:24 [chipc]: Hugo mentioned, IIRC, that he was going to help fix that
17:42:27 [topcloud]: Hopefully, vogxn's tests will help in keeping master free of these problems.
17:42:39 [chipc]: midonet is what broke it
17:42:39 [chipc]: ?
17:42:49 [vogxn]: likitha reported a stack trace. i'm just starting the server using htat
17:43:32 [chipc]: ok
17:43:39 [vogxn]: i'll circle back on the lists if there is an issue
17:43:47 [vogxn]: but yes. ho[pefullly the bvt stuff will prevent the blocks
17:44:09 [chipc]: ok, any other master branch topics?
17:44:47 [chipc]: ok, moving on then


# 7. other topics #
17:45:01 [chipc]: any general topics for the meeting?
17:45:09 [widodh]: 
ACTION doesn't have anything left

17:45:24 [chipc]: I have one, from serverchief...  I don't think the right folks are here to talk about it though
17:45:40 [chipc]: Ilya mentioned the concurrency of operations for VMware as being a pretty important enhancement
17:46:01 [kdamage]: very true
17:46:02 [chipc]: I asked him to look at specing it out and seeing if he can get a dev to build it
17:46:24 [chipc]: so that's all I have
17:46:26 [chipc]: anything else from anybody?
17:47:16 [chipc]: ok, then that's the meeting!  Thanks everyone.