THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
17:01:11 <jzb> #startmeeting
17:01:11 <cs-meeting> Meeting started Wed Sep 26 17:01:11 2012 UTC. The chair is jzb. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:01:11 <cs-meeting> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:01:39 <jzb> #chair bhaisaab cvittal edison_cs rohityadav Spark404 vogxn widodh Sailaja jlkinsel
17:01:39 <cs-meeting> Current chairs: Sailaja Spark404 bhaisaab cvittal edison_cs jlkinsel jzb rohityadav vogxn widodh
17:01:47 <jzb> OK, let's get this party started
17:01:59 <jzb> (Obligatory "Cabin in the Woods" reference...)
17:02:04 <jzb> let
17:02:20 <jzb> let's go in alpha order - if you have nothing, please say so.
17:02:31 <jzb> bhaisaab: do you have anything to report or discuss?
17:02:36 * rohityadav is bhaisaab
17:02:41 <rohityadav> jzb: yes,
17:02:48 * vogxn is in
17:02:51 <rohityadav> some progress to share, questions to ask
17:03:20 <rohityadav> jdeb/maven/debian packaging works now, jfi… all builds with waf/maven/ant are working fine
17:03:23 <widodh> I'm here!
17:03:38 * Spark404 waves at widodh
17:03:38 <rohityadav> In, client and awsapi, I'm not sure how we should package them
17:04:27 <rohityadav> most of the the scripts have their variables @@ expanded by war, don't know how to proceed, or should we maintain two version of these scripts… one for debian/ubuntu and one for rhel/centos/fedora
17:04:57 <vogxn> rohityadav: mvn profiles can do the trick?
17:05:02 <rohityadav> also some scripts in agent/bindir, server/bindir… a lot of files there for different distros
17:05:16 <rohityadav> vogxn: it will be tricky, will have to replace @@ by [[ ]]
17:05:42 <rohityadav> second issue, is to have a rpm repo like the deb one
17:05:45 <Spark404> rohityadav: antrun from within maven can do it
17:05:54 <edison_cs> i am coming
17:06:25 <rohityadav> Spark404: how about maintaining two hard coded versions? one for debian based distros and one for rpms based
17:06:34 <rohityadav> it was suggest was edison_cs once
17:06:35 <jzb> #chair sudhap
17:06:35 <cs-meeting> Current chairs: Sailaja Spark404 bhaisaab cvittal edison_cs jlkinsel jzb rohityadav sudhap vogxn widodh
17:07:14 <rohityadav> third issue is: oss vs nonoss builds, their testing and how we will release?
17:08:10 <rohityadav> summary: 1. deb packaging for some submodules not clear, awsapi, client; and what to do about preprocessing scripts; 2. rpm repo 3. builds and releases
17:08:12 <rohityadav> discuss!
17:08:14 <widodh> rohityadav: I haven't set up the RPM repo, but I'll do
17:08:32 <widodh> never done it before, Deb was easy since I've done it a couple of times
17:08:46 <rohityadav> widodh: that would be just great!
17:08:54 <edison_cs> rohityadav: the maven packaging stuff is not in the 4.0, we can defer it
17:08:55 <rohityadav> okay, I'll look into it too
17:08:56 <Spark404> widodh: pretty easy, have a look at mrepo
17:08:56 <vogxn> widodh: once we have rpms yum's createrepo script will do a yum repo
17:09:19 <vogxn> and then just add the repo to /etc/yum.repos.d
17:09:24 <rohityadav> edison_cs: okay, I wanted to discuss so we start putting stuff asap after 4.0
17:09:25 <widodh> I'll check that out
17:09:51 <rohityadav> okay let's postpone 1. discussion for now.
17:10:01 <jzb> rohityadav: you'll take that to the mailing list?
17:10:16 <rohityadav> jzb: already have, but will repost
17:10:20 <Spark404> rohityadav: after 4.0 release means pushing source jars to apache maven repo, others can make the packages right?
17:11:01 <rohityadav> Spark404: after 4.0 => review/commit patches from https://github.com/bhaisaab/incubator-cloudstack/tree/maven-debs
17:11:27 <rohityadav> and introducing some plugins in maven, deprecating waf/ant altogether
17:11:51 <Spark404> rohityadav: should package building realy be included in the "main" source, still not sure about that
17:12:22 <rohityadav> Spark404: just a maven plugin, user should be able to package from source too right?
17:12:33 <vogxn> Spark404: i guess having them under profiles until package managers get to it should be good?
17:12:56 * ke4qqq shows back up from a phone call
17:13:04 <Spark404> rohityadav: depends on what you mean by package. I think package is jars,wars etc. and leave the distro specific stuff to whoever want to do it
17:13:06 <rohityadav> yes vogxn, Spark404 you can merge my branch to master right now, they are in a profile, won't affect anything unless you select that profile
17:13:17 <rohityadav> with correct build lifecycle, mvn package -P deb
17:13:25 <jlkinsel> seems to me like we're saving folks a good amount of work by including capabilitites to build rpm/debs
17:13:39 <vogxn> +1
17:13:56 <rohityadav> Spark404: ??? we already have code that packages in our 'main' master etc. source, debian/ cloud.spec, waf all these stuff?
17:14:01 <ke4qqq> jlkinsel: the problem is that the packaging purists don't do things that way - they want to use dpkg and rpmbuild
17:14:22 <Spark404> jlkinsel: yup, for sure.. but i also want to make it easy for people to package it for their favorit distro.
17:14:33 <ke4qqq> Spark404: me too!!!
17:14:43 <jlkinsel> ke4qqq: what's stopping them? It's a convenience build, no?
17:15:14 <edison_cs> ke4qqq: is it possible to get ubuntu/fedora guys's feedback on packaging?
17:15:15 <rohityadav> ke4qqq, jlkinsel: I'm packaging for hours these days, it's not maintainable
17:15:20 <Spark404> jlkinsel: our current build procedure is too integrated with the packaging. we need clear intermediate steps t think
17:15:36 <Spark404> source -> binary release (war, jar) -> optional dep,rpm
17:15:37 <ke4qqq> jlkinsel: nothing inherently - but I'd like to see an install profile - that installs and lets me munge dest dirs
17:15:48 <widodh> Spark404: agree
17:15:50 <rohityadav> say, I a plugin develop don't want to learn war, ant or cloud.spec or control/rules… i drop in my code in plugin/** and it should just work… only possible with maven
17:16:12 <widodh> ke4qqq: Indeed, it shoud create for example: artifacts/build/usr/share/java
17:16:13 <ke4qqq> edison_cs: wido can provide good deb/ubuntu feedback - and I am happy to provide fedora rpm feedback.
17:16:16 <rohityadav> yes, if we can simplify that will just work
17:16:20 <widodh> RPM and DEB can pick that up
17:16:30 <ke4qqq> widodh: +1
17:16:30 <widodh> or you can make a tarball and drop it on your system
17:16:40 <rohityadav> widodh: what about scripts, custom paths and post pre inst rules for many
17:16:42 <widodh> That way we can use dpkg-buildpackage with the rules and control file for building the packages
17:16:54 <Spark404> widodh: i'm in the tarball camp
17:16:58 <widodh> In postinst and preinst there are no custom directories
17:17:09 <widodh> In your *.install files you define what paths you are using
17:17:15 <rohityadav> for each cloud-python gets stuff from cloud-cli during packing, and cloud-cli gets stuff from cloud-python?
17:17:23 <jlkinsel> actually that brings up another question - why don't we product a war currently? ( I don't think we do...)
17:17:38 <widodh> For example, dpkg calls mvn with a "prefix" set to /usr
17:17:46 <widodh> just like dpkg 'normally' calls configure and make
17:17:53 <Spark404> jlkinsel: we do, if you enable the client profile during build (at least for client)
17:17:55 <widodh> --prefix=/usr --sysconfigdir=/etc
17:18:20 <jlkinsel> Spark404: ok, will look closer.
17:18:25 <rohityadav> tell me nowI've written about 4k pom lines to get deb working, will throw that code right away if what you guys are saying can work and would be maintainable… (and we won;t use war or ant with it)
17:18:28 <Spark404> jlkinsel: most of that stuff is already in the maven branch, will work on that next week with edison
17:18:47 <widodh> rohityadav: You can make one big tree which contains your whole build and every package can cherry pick what they want
17:18:48 <jlkinsel> i was lookin in the ant configs, still coming up to speed on maven stuff
17:19:00 <widodh> rohityadav: Not to have you throw stuff away, but this just came to mind
17:19:08 <ke4qqq> rohityadav: please don't take it as saying that it's bad - just at least one other option would be nice.
17:19:26 <rohityadav> widodh: not maintainable, you're not considering this case, if I only want to package api, I should be able to do that
17:19:26 <widodh> I also build this ant based a couple of months back, replacing waf by ant
17:19:46 <widodh> rohityadav: I have to be honest, I haven't checked the code yet
17:19:56 <widodh> So I'm not judging or not considering
17:20:07 <rohityadav> ke4qqq: I'm not saying good vs bad, meh, it should be maintainable
17:20:08 <widodh> I just have the OpenSUSE guys and other distro's in the back of my mind
17:20:10 <cvittal> can we steer the discussion back to ASF CS 4.0 ?
17:20:19 <jlkinsel> yeah
17:20:21 <rohityadav> consider cases when we add new modules, plugins etc
17:20:21 <jlkinsel> sorry
17:20:21 <jzb> cvittal: thanks
17:20:30 <widodh> cvittal: Yes, but you can make an action: I'll put this on the ml
17:20:34 <widodh> for further discussion
17:20:48 <jzb> widodh: what's your action, specifically?
17:20:48 <rohityadav> If it does not make sense, I don't want to continue is all I'm saying 
17:21:08 <widodh> jzb: Bring up our complete package building and getting waf out of the door
17:21:12 <jzb> rohityadav: anything else on your list?
17:21:24 <rohityadav> jzb: jlkinsel: actually that brings up another question - why don't we product a war currently? ( I don't think we do...)
17:21:31 <rohityadav> that's a good idea too
17:21:32 <jzb> #action widodh bring up complete package building and getting WAF out the door.
17:21:45 <jzb> rohityadav: is that crucial for 4.0? or can we move that to the list?
17:22:01 <rohityadav> sorry, yes let's move on
17:22:15 <jzb> cvittal: anything to discuss or report ?
17:22:24 <vogxn> there was an action on widodh for the yumrepo too. missed that i guess?
17:22:41 <widodh> vogxn: Later on, when it's my turn
17:22:52 <vogxn> widodh: sure. 
17:23:10 <cvittal> not much. anybody have an opinion on CLOUDSTACK-147 ?
17:23:28 <cvittal> only config file blocker remaining.
17:23:44 <ke4qqq> conntrack isn't still an issue?
17:23:44 <jzb> #link https://issues.apache.org/jira/browse/CLOUDSTACK-147
17:23:57 <jzb> cvittal: I need to update the ticket, but we're good on that one.
17:24:08 <cvittal> ok
17:24:09 <jzb> I have talked to upstream, got a mail back yesterday saying it's good.
17:24:15 <cvittal> ok cool
17:24:28 <cvittal> ke4qqq we nuked conntrack it seems
17:24:39 <jzb> cvittal: anything else?
17:24:39 <ke4qqq> Cloudstack-166 is still open
17:25:04 <jzb> #link https://issues.apache.org/jira/browse/CLOUDSTACK-166
17:25:20 <ke4qqq> is it no longer needed?
17:26:07 <cvittal> it affects ubuntu on XenServer
17:26:20 <cvittal> we may need to document it as a known issue
17:26:59 <cvittal> practically speaking when folks download the system vm template from download.cloud.com they will not face the issue since that template has the fix
17:27:28 <jzb> cvittal: last update was from David, can you update the ticket with the resolution if we have one?
17:27:32 <jzb> (on the ticket)
17:27:49 <jzb> (sorry, last update was from ke4qqq for those of you following along on IRC...)
17:27:53 <cvittal> you mean CLOUDSTACK-166?
17:27:55 <jzb> yes
17:28:05 <cvittal> oh, sorry, got confused
17:28:11 <cvittal> disregard my last comments
17:28:20 <jzb> now I'm confused
17:28:26 <jzb> but that's normal.
17:28:31 <cvittal> I was referring to the iptables patch that used to be in there
17:28:46 <cvittal> I have no opinion/update on CLOUDSTACK-166
17:28:47 <cvittal>
17:28:51 <jzb> OK. Thanks!
17:28:54 <jzb> let
17:29:00 <jzb> let's move on -
17:29:05 <jzb> edison_cs: anything to report or discuss?
17:29:11 <edison_cs> yes
17:29:19 <edison_cs> there are two bugs related to kvm
17:29:27 <edison_cs> one is ubuntu installation
17:29:33 <edison_cs> http://markmail.org/message/gfjo36aqeicehvd5
17:29:46 <edison_cs> widodh: do you have idea?
17:30:14 <edison_cs> if qa switching to your new installation guide, will that help?
17:30:17 <widodh> Yes, probably. Wanted to check those out
17:30:28 <widodh> Yes, I think it will help since install.sh doesn't get all dependencies
17:30:41 <widodh> And I need to add the dependency for cloud-scripts to cloud-client
17:30:55 <rohityadav> widodh: pl. do that, for me in basic zone it worked, but yes....
17:31:22 <edison_cs> another bug is https://issues.apache.org/jira/browse/CLOUDSTACK-120
17:31:42 <edison_cs> people complains that refresh install
17:31:49 <jzb> #link https://issues.apache.org/jira/browse/CLOUDSTACK-120
17:31:52 <edison_cs> kvm agent will not work properly
17:32:19 <rohityadav> edison_cs: I got email from Abhinav that after rebooting the kvm host, it works?
17:32:19 <edison_cs> seems like ssh key is not populated on kvm host
17:32:26 <ke4qqq> widodh: while we are picking on you - did you see this message? http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201209.mbox/%3C8EA64E8D-9EAB-4259-BF52-5A78DDC69731%40shankerbalan.net%3E
17:32:31 * rohityadav o.O
17:32:31 <edison_cs> rohityadav: you can't do that,
17:32:43 <widodh> ke4qqq: Yes, got it!
17:32:59 <widodh> I'm getting so much e-mail in one day.. Still have a company next to it to run as well
17:33:00 <edison_cs> rohityadav: don't need to reboot or restart agent, it should just works
17:33:00 <rohityadav> edison_cs: sorry do what?
17:33:05 <rohityadav> oh
17:33:17 <ke4qqq> widodh: pesky dayjob
17:33:42 <widodh> So yes, I'm aware of those issues. Most are minor fixes. That cloud-scripts is easily fixed and that mail ke4qqq just mentioned as well
17:33:46 <edison_cs> i;ll look at the CLOUDSTACK-120
17:33:52 <widodh> Great
17:33:57 <rohityadav> +1 thanks
17:34:06 <ke4qqq> widodh: I'll take care of the dependency issue if you need me to
17:34:16 <widodh> ke4qqq: No, I'll handle that after the meeting
17:34:33 <vogxn> another kvm issue was related to snapshots on rhel6.3
17:34:38 <vogxn> just filed today
17:34:42 <vogxn> seems critical
17:34:52 <edison_cs> vogxn: no snapshot support
17:34:52 <widodh> Saw that one as well, already had a discussion on it, ke4qqq had a good point
17:34:56 <widodh> seems legacy code
17:35:40 <widodh> but we are drifting again
17:35:55 <widodh> Other people are waiting on us
17:36:21 <widodh> #action widodh takes care of dependency issues mentioned on the dev list. Mostly cloud-scripts
17:36:28 <jzb> thanks, widodh
17:36:29 <widodh> #action edison_cs will handle CS-120
17:36:36 <jzb> edison_cs: anything else on your plate?
17:36:39 <jzb> #names
17:36:42 <edison_cs> no more
17:36:43 <jzb> oops
17:36:56 <jzb> that brings us to jlkinsel - anything to report or discuss?
17:37:20 <jlkinsel> not from me
17:37:30 <jzb> thanks.
17:38:09 <jzb> that brings us to me - we've already discussed the configuration tickets that I've got. I'm going to work with ke4qqq on the crypto issue and we'll try to get that resolved ASAP.
17:38:14 <jzb> that's it for me for ACS 4.0
17:38:22 <jzb> ke4qqq: do you have anything to report or discuss?
17:38:24 <ke4qqq> yes
17:38:33 <ke4qqq> two requests:
17:38:42 <jzb> #action jzb follow up with ke4qqq on Crypto issue.
17:39:01 <ke4qqq> 1. please look at the tarball, grep, vim, RAT, and find any remaining legal issues.
17:39:34 <ke4qqq> 2. off topic - but please consider dropping a talk proposal in at http://collab12.cloudstack.org
17:39:57 <ke4qqq> EOF
17:40:13 <jzb> thanks ke4qqq
17:40:17 <jzb> ok, next up
17:40:24 <jzb> mrkite: do you have anything to report or discuss.
17:40:31 <jzb> that was a question, sorry.
17:40:35 <jzb> welcome nslater
17:40:38 <jzb> #chair nslater
17:40:38 <cs-meeting> Current chairs: Sailaja Spark404 bhaisaab cvittal edison_cs jlkinsel jzb nslater rohityadav sudhap vogxn widodh
17:41:22 <jzb> ok, we'll circle back to mrkite
17:41:28 <jzb> we've already heard from rohityadav
17:41:36 <jzb> Sailaja: do you have anything to report or discuss?
17:41:40 <Sailaja> Yes
17:41:47 <Sailaja> 2 questions
17:42:03 <Sailaja> 1. Upgrade issue reported by abhinav 209
17:42:25 <jzb> #link https://issues.apache.org/jira/browse/CLOUDSTACK-209
17:42:32 <Sailaja> 2. Are we going to document steps for non oss installation
17:42:44 <jzb> Sailaja: what's the actual question about the ticket?
17:42:53 <widodh> Sailaja: 1 is know, fixing that. Same dependency problem (again)
17:42:57 <ke4qqq> Sailaja: would you like to document, we'd love to see the patch
17:43:23 <mrkite> no thanks, just lurking
17:43:46 <jzb> mrkite: OK, lurk on.
17:43:52 <jzb> thanks for lurking
17:43:58 <Sailaja> Okay i will prepapre the steps
17:44:11 <ke4qqq> Sailaja: thanks!
17:44:19 <jzb> #action Sailaja will document non-oss installation for ACS 4.0
17:44:31 <jzb> (and thanks from me as well.)
17:44:36 <jzb> Sailaja: anything else?
17:44:43 <Sailaja> nothing . Thanks
17:44:50 <jzb> Sailaja: thank you
17:44:56 <jzb> Spark404: anything to report or discuss?
17:45:00 <Spark404> yeah
17:45:22 <Spark404> i was wondering if QA is doing anything with QA testing the Nicira SDN integration
17:45:54 <sudhap_> Spark404: no
17:46:01 <vogxn> nothing in the test plan about nicira/rbd
17:46:35 <Spark404> ok, clear. should that be part of the test plan? It is a major feature we are introducing in 4.0
17:46:46 <Spark404> i think the code works, but i wrote it so i'm partial 
17:46:48 <ke4qqq> Spark404: could you define test cases?
17:47:34 <Spark404> ke4qqq: yeah, should not be to hard. except the QA teams needs a sdn setup
17:47:52 <sudhap_> Spark404:Woud like to solicit help from community who has experience in that area if possible
17:47:52 <ke4qqq> Spark404: also - how can folks get access to NVP
17:48:02 <rohityadav> vogxn, edison_cs: that can be arranged?
17:48:17 <ke4qqq> Spark404: is SP using this in production yet?
17:48:30 <Spark404> ke4qqq: yes
17:49:02 <edison_cs> if other company can donate a sdn to us, that will be great...
17:49:25 <ke4qqq> Spark404: can we see about getting nicira to grant an NVP license for testing?
17:49:27 <Spark404> i'm at nicira this week, i'll see what can be done about that
17:49:51 <rohityadav> +1
17:50:12 <edison_cs> Spark404: +1
17:50:26 <cvittal> also Spark404, doc team has been asking for docs on this feature for a long time
17:50:27 <Spark404> so actions for me, write testplan and see about sdn setup for citrix qa team
17:51:06 <Spark404> cvittal: true, should get to that. i'll work on that next week
17:51:07 <jzb> #action Spark404 write testplan and see about SDN setup for Citrix QA
17:51:19 <jzb> Spark404: are you committing to docs as well?
17:51:50 <Spark404> also as i'm at vmware now, what is the blocker for including vmware plugin in the oss build. might be able to start a discusion here about that
17:51:55 <ke4qqq> Spark404: perhaps you could delegate to someone else at SP - since you are clearly already using it.
17:52:07 <jzb> Spark404: I think it's licensing.
17:52:07 <ke4qqq> Spark404: SDK licensing terms
17:52:46 <Spark404> ke4qqq: can you send me a mail with the details, i got some offers from people here to have a look at it
17:53:18 <widodh> That would be a big win for 4.0 if that could be fixed on short-term!
17:53:49 <Spark404> no promises, but at least we can statt eh discussion
17:53:56 <jzb> Spark404: anything else?
17:54:08 <ke4qqq> Spark404: absolutely
17:54:14 <Spark404> jzb: no
17:54:30 <jzb> #action ke4qqq send email about licensing issues with VMware SDK, follow up with Spark404
17:54:33 <jzb> OK, groovy
17:54:36 <jzb> thanks Spark404
17:54:47 <jzb> sudhap_: anything to report or discuss?
17:54:54 <sudhap_> yes
17:55:26 <jzb> sudhap_: fire wawy
17:55:27 <jzb> er away
17:55:29 <sudhap_> from QA standpoint, i have posted metrics - we are running couple of days behind schedule
17:55:49 <nslater> hi guys
17:57:17 <ke4qqq> #link https://cwiki.apache.org/CLOUDSTACK/asf-cs-40-qa-metrics.html
17:57:27 <ke4qqq> sudhap_: confidence level from a quality standpoint?
17:57:52 <sudhap_> I am confident on the covered areas
17:58:15 <ke4qqq> sudhap_: do you have remaining bandwidth to cover the remaining 31% or is the schedule slippage mean we lose a few days of testing?
17:58:40 <sudhap_> ke4qqq: I asked team to finish by 28th but we will run in to early next week
17:58:46 <cvittal> need to leave now for another meeting
17:59:12 <sudhap_> list of deployment issues are posted yesterday by Sailaja and addressed already
17:59:17 <ke4qqq> thanks for coming cvittal
17:59:42 <jzb> btw - I'll have a hard stop in about 15 minutes.
17:59:49 <jzb> so does ke4qqq
18:00:22 <ke4qqq> sudhap_: thanks for running the stats and putting your folks to work on this.
18:00:43 <sudhap_> Regarding documentation - would all non-oss references will be removed from installation guildes??
18:00:48 <Spark404> +1 awesome job
18:01:01 <ke4qqq> sudhap_: no they aren't and don't need to be
18:01:12 <widodh> sudhap_: I don't think so? We just mention you need a non-OSS build?
18:01:18 <widodh> Along those lines
18:02:39 <sudhap_> This is a little confusing and I got several questions from team about this
18:02:51 <ke4qqq> http://www.apache.org/legal/3party.html#options
18:03:01 <ke4qqq> For add-ons under excluded licenses, the PMC may provide a link/reference on the product web site or within product documentation to some other web site that hosts such add-ons (e.g. a SF.net project or some third-party site dedicated to distributing add-ons for the Apache product) as long as it is made clear to users that the host site is not part of the Apache product nor endorsed by the ASF.
18:03:28 <archetech_> there was an email sent on behalf of the users in the cloudstack channel not long ago requesting that the networking docs be expanded to show a standard topology using basic and adv'ed nets
18:03:31 <sudhap_> Ok
18:03:51 <archetech_> from iswc
18:04:22 <sudhap_> ok
18:04:25 <archetech_> we get new users who have to be explained over and over the basics of the network setups
18:04:27 <jzb> sudhap_: all done?
18:04:38 <jzb> archetech_: we're going in order.
18:04:50 <archetech_> al I have
18:04:50 <sudhap_> yes
18:04:53 <archetech_> all
18:04:58 <jzb> thanks sudhap_
18:05:14 <jzb> ok, vogxn anything on your end?
18:05:17 <vogxn> small update: the setup for marvin functional tests is coming together. I hope to have an update this week on this. This will run on citrix loaned hw. Will be using a cobbler+puppet solution on this with packages coming widodh's repo for deb.
18:05:30 <jzb> vogxn: nice!
18:05:41 <rohityadav> +1 vogxn
18:05:45 <ke4qqq> vogxn: please blog about this when it is up
18:05:51 <jzb> +1
18:05:52 <vogxn> ke4qqq: will do
18:06:01 <jlkinsel> +1
18:06:02 * vogxn passes the baton
18:06:08 <jzb> #action vogxn will blog about Marvin test work.
18:06:12 * ke4qqq has one more question
18:06:15 <jzb> vogxn: awesome.
18:06:16 <vogxn> sure
18:06:29 <vogxn> question for me? shoot
18:06:33 <ke4qqq> it's re: blogging - jlkinsel whats up with planet - I saw some commits
18:07:08 * ke4qqq now shuts up
18:07:15 <jlkinsel> yeah I keep getting interrupted when I go to work on it. 
First I thought I had made that commit before I went on vacation weeks ago - fell off the radar so hopped back on it last night
18:07:48 <jlkinsel> there's one more commit comming to fix the URLs in there, then I'm updating the ticket with infra, once the move or say something, I'll fix or invite feeds from others
18:08:31 <ke4qqq> awesome
18:08:40 <jzb> ok, that brings us to widodh
18:08:46 <widodh> Ok, got 4 points
18:08:48 <jzb> widodh: anything to report or discuss?
18:09:15 <widodh> Two connected to eachother. Like I mentioned on the ml I'm working on the docs and easing the installation by using yum and apt
18:09:36 <widodh> Still need to set up the RPM repo, DEB is done. I'd like QA to actually test these repos and the docs which go along with it
18:09:48 <widodh> Seems it's already happening, just wanted to mention it again
18:10:09 <sudhap_> widodh: sure
18:10:13 <widodh> Looking for somebody who already set up a RPM repo, never done that before, so I might be asking for help
18:10:24 <ke4qqq> widodh: I can do that for you
18:10:26 <jlkinsel> happy to help
18:10:27 <widodh> It should just be a new repo in /etc/yum/repos.d/ and you'r done
18:10:29 <jlkinsel> or ke4qqq
18:10:29 <widodh> Ok, great
18:10:35 <ke4qqq> jlkinsel: please run with it
18:10:41 <jlkinsel> k
18:10:42 <widodh> That were actually my first two points in one
18:11:05 <widodh> 3rd, together with Spark404 I'm setting up a Apache MeetupNL on October 16th in the Netherlands
18:11:17 <widodh> the one last week at Spark404's office was unofficial, this one will be "official"
18:11:30 <widodh> Maybe we can warm more people for 4.0 and have them test it.
18:11:35 <ke4qqq> regardless - it's simple - should be scriptable and then you can replace jlkinsel or i with a few lines of code.
18:11:53 <widodh> What we saw last week is that a LOT of people still run 2.2.14 and never upgraded to 3.0
18:12:03 <widodh> We need to help them with getting to 4.0 or 4.1 at some point
18:12:18 <jzb> widodh: can you send me the info + I can put up an event on CloudStack.org and help promote?
18:12:23 <jzb> (the meetup)
18:12:31 <widodh> #action widodh sends MeetUp info to jzb
18:13:03 <widodh> My last point, not really 4.0 related, but what do we do with vacation? With that I mean, do we (committers / PPMC) announce it somewhere?
18:13:12 <widodh> I'm going to be in Prague from Sept 29th until October 4th
18:13:28 <jzb> widodh: I don't think there's a standard rule or practice right now.
18:13:32 <ke4qqq> widodh: perhaps list - other projects I've been on have a wiki page.
18:13:32 <vogxn> we can have a wiki page
18:13:34 <widodh> So my e-mail response will be delayed, I don't want people to wait on me
18:13:44 <jzb> widodh: but announcing it on the -dev list would be good community practice.
18:14:13 <widodh> maybe a tag for this? like we have ASF40
18:14:30 <ke4qqq> widodh: good idea - i have some vacation coming up as well
18:14:39 <widodh> It's just to prevent tickets being assigned
18:14:46 <widodh> or people waiting for your response
18:15:22 <widodh> For now let's keep it to the -dev list? Or do we need a vote on that one?
18:15:33 <widodh> But that were my points
18:15:39 <ke4qqq> no vote- just do the work and establish behavior
18:15:58 <jzb> OK, thanks widodh
18:16:19 <jzb> OK, all - I have a hard stop now. Any objections to ending the meeting?
18:16:43 <jzb> going once... going twice
18:17:21 <jzb> OK, I'll take that as no objections - thanks to everyone for attending and all your hard work!
18:17:26 <jzb> #endmeeting
Overview
Content Tools
Apps