17:00:15 <jzb> #startmeeting
17:00:15 <cs-meeting> Meeting started Wed Oct 10 17:00:15 2012 UTC. The chair is jzb. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:15 <cs-meeting> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:00:40 <jzb> #chair bhaisaab chipc edison_cs iswc ke4qqq noe vogxn widodh
17:00:40 <cs-meeting> Current chairs: bhaisaab chipc edison_cs iswc jzb ke4qqq noe vogxn widodh
17:00:54 <jzb> will give a minute or two for folks to arrive.
17:00:58 <widodh> I; m here
17:01:29 <edison_cs> hi
17:01:52 <chipc> hi - here
17:02:08 <jzb> OK, let's get started
17:02:40 <jzb> to make things run smoothly, please be sure to let me know when you're done speaking as we go around the room.
17:03:01 <jzb> Let's start with bhaisaab - anything to discuss or report?
17:03:07 <jzb> #info bhaisaab has the floor.
17:04:18 <jzb> OK. Will move on.
17:04:29 <jzb> Next, chipc - anything to discuss or report?
17:04:36 <jzb> #info chipc has the floor
17:04:51 <chipc> ok - so here's where I believe we stand with the 4.0.0-incubating release
17:05:16 <chipc> first, we need a test engineer to run through the Ubuntu tests, specifically around AWSAPI
17:05:33 <chipc> this is based on the latest round of changes that widodh made in the 4.0 branch
17:06:01 <chipc> second, I've started the build / verify process for the release (at commit 3854de46ce6e2eaf81de695c31e37f0f77228938 )
17:06:24 <chipc> if QA verifies, we can use my parallel work to kick off the voting process
17:06:33 <chipc> assuming, of course, that my testing works
17:06:40 <chipc> I'm up to the AWSAPI testing part now
17:06:44 <chipc> so far so good
17:07:22 <chipc> I'd also like to know if ke4qqq was able / willing to move forward with the crypto filing (given the response to his latest email on the topic)
17:07:33 <chipc> other than that, I'm good
17:07:34 <ke4qqq> chipc: jimjag gave me blessing this mornigng
17:07:45 <ke4qqq> so I plan on moving forward with that
17:08:02 <widodh> For my information, I'm really not into that
17:08:08 <chipc> ke4qqq: can you get that done before QA signals that they are good to go?
17:08:14 <widodh> but we are exporting source code, what does the crypto export have to do with that?
17:08:24 * widodh is in EU and doesn't really know (smile)
17:08:33 <ke4qqq> widodh: don't expect it to make sense
17:08:40 <widodh> Ok, I'll back off then
17:08:40 <ke4qqq> (smile)
17:08:57 <jzb> widodh: silly US regs.
17:09:01 <chipc> widodh: also, it might not even be required anymore… but we're taking the path more frequently traveled, as the ASF legal folks sort out the current regs
17:09:09 <ke4qqq> chipc: yes - will get that done as soon as the meeting is over
17:09:18 <chipc> ke4qqq: thank you
17:09:21 <widodh> Ok, tnx chipc and jzb
17:09:39 <chipc> #action ke4qqq to do the crypto export filing today
17:10:03 <chipc> jzb: I'm done, but would like to hear that someone from QA has started with testing Ubuntu
17:10:28 <jzb> chipc: OK. Thanks!
17:10:50 <jzb> I'll assume that the meeting bots have nothing to report...
17:11:02 <jzb> Next up, edison_cs - anything to report or discuss?
17:11:09 <jzb> #info edison_cs has the floor
17:11:21 <edison_cs> I am done
17:11:30 <edison_cs> waiting for 4.0
17:12:27 <sudhap> chipc: I will report QA when my turn is up
17:12:54 <jzb> OK
17:13:08 <jzb> next iswc - anything to report or discuss?
17:13:17 <jzb> #info iswc has the floor
17:14:03 * bhaisaab o/
17:14:30 <jzb> bhaisaab: not sure I know how to interpret that.
17:14:50 <bhaisaab> jzb: I'm here now, was away
17:15:05 * bhaisaab is rohityadav
17:15:11 <jzb> bhaisaab: OK. We'll circle back.
17:15:28 <bhaisaab> or we can come at r
17:15:32 <jzb> OK, we'll move on.
17:15:47 <jzb> so... that brings us to me.
17:15:54 <jzb> #info jzb has the floor
17:16:20 <jzb> I sent a note to the mailing list with what I'm working on - getting things ready to transition to pointing cs.org to the apache infra.
17:16:38 <chipc> jzb: thanks for doing that work
17:16:57 <jzb> chipc: is there an Apache page I should look at w/r/t what you're doing about downloads?
17:17:17 <jzb> general release process?
17:17:32 <rohityadav> jzb: http://incubator.apache.org/cloudstack/ this one?
17:18:03 <jzb> chipc: http://incubator.apache.org/guides/releasemanagement.html
17:18:14 <jzb> rohityadav: that's where cs.org will point, yes.
17:18:27 <rohityadav> jzb: +1 that's what I thought (big grin)
17:18:28 <chipc> jzb: we actually don't have a place on the current site that works with the ASF mirrors
17:18:41 <chipc> I have the code ready to add, but I'll just let you know when I go and add it
17:18:48 <jzb> Ah, OK
17:18:51 <jzb> sounds good.
17:19:02 <jzb> let me know if there's anything I can help with there or need to do in particular.
17:19:17 <widodh> jzb: The website is maintained in SVN, correct?
17:19:28 <chipc> should be easy - just wanted you to know that I would be making lots of changes to the download page
17:19:31 <jzb> widodh: that's correct
17:19:34 <chipc> widodh: it is
17:19:58 <jzb> we're using the Apache CMS and it's all in SVN
17:20:08 <jzb> it's been an adventure (smile)
17:20:15 <jzb> ok, that's it from me.
17:20:19 <jzb> moving on...
17:20:29 <jzb> kdamage: anything to report or discuss?
17:20:36 <jzb> #info kdamage has the floor
17:20:39 <kdamage> no today, thanks
17:20:47 <jzb> #action jzb working on cs.org transition
17:20:51 <jzb> kdamage: thanks!
17:21:08 <jzb> next up, ke4qqq - anything to report or discuss?
17:21:14 <ke4qqq> nothing - EOF
17:21:15 <jzb> #info ke4qqq has the floor
17:21:23 <jzb> OK
17:21:28 * jzb likes the pace we're keeping today.
17:21:42 <jzb> mrkite asked to be skipped, I believe
17:21:48 <mrkite> yes, please
17:21:56 <jzb> noe: are you about? Anything to discuss or report?
17:22:21 <noe> yep, and nope
17:22:25 <noe> sorry on a conf call with work
17:22:30 <jzb> succinct. I love it.
17:22:34 <noe> (smile)
17:22:50 <jzb> next we've got rohityadav, the man of many IRC nicks
17:22:56 <rohityadav> (big grin) lol
17:22:58 <jzb> rohityadav: anything to discuss or report?
17:23:23 <rohityadav> alright to report; awsapi related stuff got fixed, we have both oss and nonoss builds for rhel/cent/fedora and debian/ubuntu
17:23:36 <rohityadav> we're code complete just awaiting final thumbs up from QA
17:23:48 <rohityadav> only awaspi/nonoss stuff left on ubuntu nonoss
17:23:51 <rohityadav> done
17:24:05 <rohityadav> added https://cwiki.apache.org/confluence/display/CLOUDSTACK/Building
17:24:30 <rohityadav> this will be our version specific building and packing wiki and also linked to the building on maven wiki
17:24:37 <rohityadav> jzb: done form my side
17:24:41 <rohityadav> *from
17:24:50 <jzb> rohityadav: thank you much
17:24:56 <jzb> I forgot to add the
17:25:04 <jzb> #info rohityadav has the floor
17:25:06 <jzb> dang it.
17:25:13 <rohityadav> !
17:25:16 <jzb> OK, next is sudhap
17:25:23 <jzb> anything to discuss or report?
17:25:28 <sudhap> Yes
17:25:29 <jzb> #info sudhap has the floor
17:25:54 <sudhap> testing is done last night PST for OSS builds on both platforms
17:25:58 <sudhap> everything is working fine
17:26:15 <rohityadav> yay!
17:26:24 <chipc> sudhap: any indication on how long for the new Ubuntu test round to complete?
17:26:25 <rohityadav> sudhap: any updates on ubuntu nonoss?
17:26:39 <sudhap> testing ubuntu now
17:26:43 <sudhap> on non oss
17:26:45 <widodh> great news
17:26:52 <rohityadav> yeah!
17:26:55 <sudhap> should be done in an hour or so
17:27:02 <chipc> sudhap: thanks
17:27:04 <jzb> lovely!
17:27:07 <rohityadav> fantastic
17:27:13 <chipc> crosses fingers
17:27:42 <techpubs> sudhap: you are waiting for the final release notes draft so you can review/test that document, correct? Or have you rec'd it last night?
17:28:03 <sudhap> but want to check again if we need to repeat all the validation again on oss builds with changes that happened last night. looks like no
17:28:22 <sudhap> can widodh or rohityadav confirm??
17:28:44 <widodh> sudhap: I don't think so. We only touched the awsapi
17:28:46 <rohityadav> sudhap: no need
17:28:53 <rohityadav> yes!
17:29:04 <sudhap> techpubs: received the location of docs
17:29:16 <rohityadav> sudhap: only test nonoss related stuff for nonoss build + awsapi related stuff thanks
17:29:21 <chipc> techpubs: if we have it, can we get it committed?
17:29:30 <sudhap> rohityadav: sure
17:29:34 <chipc> techpubs: and you know that I removed the Nexus 1KV stuff, right?
17:29:35 <sudhap> that is in progress
17:29:46 <techpubs> chipc: I think Radhika put it up as a patch
17:29:48 <sudhap> techpubs: will check changed sections in the interest of time
17:30:03 <sudhap> techpubs: we have the links
17:30:20 <chipc> techpubs: can you confirm that it's the one I reviewed / committed already?
17:31:08 <sudhap> techpubs:send the new links to mailing list if they have chagend since last time
17:31:40 <techpubs> chipc: nope, didn't know that. We call it nexus vSwitch in the docs, I think?
17:31:51 <chipc> techpubs: yes
17:32:08 <chipc> we agreed on the list that that feature didn't make it in time from the CloudPlatform code version
17:32:15 <chipc> it was mangled and didn't pass testing
17:32:40 <chipc> so I yanked all references to it as a feature, besides a note that it not working is a known issue (CLOUDSTACK-301, IIRC)
17:33:16 <chipc> jzb: sorry, we went off topic from sudhap's items
17:33:31 <techpubs> I don't read everything on the list, must have missed that one. Radhika and I did ask Alex for a list of which features are different in 4.0 vs. the commercial side
17:33:35 <jzb> chipc: no worries.
17:33:52 <sudhap> sudhap:chipc: we will validate non oss build on ubuntu and post the results to ML
17:33:53 <techpubs> Yes, I can pipe down until my turn.
17:33:59 <jzb> sudhap: anything else to cover?
17:34:03 <sudhap> I am done
17:34:06 <chipc> sudhap: thanks
17:34:14 <sudhap> thanks
17:34:17 <jzb> #action sudhap validate non-OSS build on Ubuntu and post results to ML
17:34:35 <jzb> OK, that brings us to techpubs
17:34:40 <jzb> anything to discuss or report?
17:34:46 <jzb> #info techpubs has the floor
17:36:08 <jzb> (psst, techpubs it's your turn now.)
17:36:36 <techpubs> Was taking notes in another window
17:37:17 <techpubs> So Radhika PC is working on the release notes, and I'll ask her to confirm on Sudha's questions about whether she has up-to-date links
17:37:52 <techpubs> I made a massive commit in the master branch a day ago, which fixes up a lot of things in docs
17:38:02 <techpubs> Should cherry pick that over to 4.0, yes?
17:38:26 <widodh> techpubs: == Jessica?
17:38:27 <jzb> #action techpubs will follow up to make sure Radhika has up-to-date info/links
17:39:00 <rohityadav> Sure, if the commits are only doc related and don't break build-doc/api
17:39:08 <chipc> techpubs: can you point me to the commit please?
17:39:17 <techpubs> Also, Wido, you should see your new hypervisor install section in the Installation Guide that's building on jenkins these days
17:39:19 <chipc> I'd like to gate things going into 4.0 until I can get a vote out
17:39:23 <techpubs> widodh: yep, it's jessica t
17:39:50 <widodh> techpubs: Ok! I'll check the docs again if I can tomorrow
17:40:35 <techpubs> chipc: 1b0e40c3c8157cc76f679899751f374cfa2f2fe0, "Fix the docs builds for Admin, Developer's, and Installation guides. Remove unneeded files. Add new files. Reorganize chapter structure. Can also build all together with publican-all.cfg."
17:41:08 <techpubs> rohityadav: this commit doesn't affect API docs at all
17:41:21 <techpubs> But it will affect the other new doc builds that have been added lately
17:41:36 <techpubs> I tested by building locally before committing, of course
17:41:49 <chipc> techpubs: I'll review and do the cherry-pick
17:42:02 <techpubs> chipc: Thanks very much!
17:42:15 <rohityadav> techpubs: +1 go for the commits
17:42:22 <jzb> #action chipc review techpubs commit and cherry-pick to 4.0
17:42:24 <rohityadav> chipc: ok
17:42:34 <jzb> techpubs: anything else?
17:43:31 <techpubs> btw, I have been kept very busy by my commercial employers on an emergency fix to CloudPlatform release notes over the past 48 hours
17:43:53 <techpubs> That is the Citrix version of CloudStack, if I may be forgiven for mentioning it
17:44:43 <jzb> techpubs: you're forgiven. Anything else?
17:44:54 <techpubs> jzb: haha, thank you.
17:45:21 <techpubs> Nothing else that can't be handled on list, I sent an email or two out in the past couple of days
17:45:28 <jzb> OK, great
17:45:33 <jzb> and last but not least
17:45:41 <techpubs> I will work on closing out the remaining open docs bugs for 4.0 !
17:45:41 <jzb> widodh: anything to discuss or report?
17:45:50 <jzb> #info widodh has the floor
17:45:54 <widodh> jzb: Yes, 4 things
17:46:06 <jzb> wait didn't you have four things last time?
17:46:12 <jzb> you know we don't have a quota, right? (wink)
17:46:27 <widodh> jzb: I know, but it was pure coincidence
17:46:41 * jzb keeps an eye on this 4 things thing.
17:47:07 <widodh> 1. docs: Although our code seems to be 4.0 ready I have the feeling our docs aren't. A lot of effort went into it, but I know that for example the hypervisor install docs aren't 100% yet
17:47:20 <widodh> I've been one of the persons writing that docs, but it isn't ready
17:47:53 <jzb> widodh: are the unready bits filed as bugs?
17:47:57 <widodh> Lucky enough we can update the docs quite easily and put up a new PDF, but do we do that
17:48:05 <widodh> jzb: I haven't checked that, I don't think so
17:48:11 <chipc> widodh / techpubs: two thoughts
17:48:15 * widodh didn't check Jira that much
17:48:29 <jzb> IIRC someone suggesting a 4.0.1 release for a docs update.
17:48:31 <chipc> first, I thought we agreed on the ML that we would be OK doing the release, and letting the docs work continue
17:48:55 <chipc> second - I think that's why I'd like to avoid cherry-picking techpub's suggested commit over to 4.0
17:49:28 <widodh> why avoid? Since it changes a lot?
17:49:49 <widodh> I don't mind working on the docs while 4.0 is out of the door, but I wanted to mention it. I must have missed that ML discussion
17:50:22 * ke4qqq is ok with us doing it this time, but going forward docs should be part of codecomplete IMO
17:50:48 <techpubs> Does this argue for making the docs a separate repo?
17:50:49 <jzb> ke4qqq: how does Fedora handle freeze for docs?
17:51:09 <chipc> widodh: avoid, based on the previous agreement to not focus on them in the 4.0 branch
17:51:17 <chipc> that's the only reason really
17:51:30 <jzb> hmm. I guess a better example would be something like GNOME rather than Fedora.
17:51:41 <techpubs> Because docs are the one thing that consistently needs to change very close to release time
17:52:15 <ke4qqq> jzb: freeze for docs happens long before final freeze
17:52:21 <ke4qqq> a month + before
17:52:24 <ke4qqq> because of l10n
17:52:31 <techpubs> Radhika worked on GNOME docs, I can ask her about how they handled doc freeze
17:52:34 <rohityadav> I would like to have both docs and code shipped together
17:52:57 <widodh> I'd like to see that as well
17:52:58 <jzb> techpubs: if we're factoring in l10n, we can't be working docs this late before a release.
17:53:01 <ke4qqq> techpubs: if code freeze happens early, docs freeze should be able to follow
17:53:01 <rohityadav> and pl. no separating things in separate repo
17:53:06 <jzb> but this sounds like a discussion for the ML
17:53:11 <widodh> jzb: Indeed
17:53:16 <widodh> I just wanted to mention it
17:53:22 <techpubs> jzb: Didn't think we were factoring in l10n prerelease.
17:53:24 <jzb> it's forward-looking + should be a whole project discussion.
17:53:26 <mrkite> i'll chime in on the ML since this is very important
17:53:32 <rohityadav> +1
17:53:44 <jzb> widodh: you still have several more items? (smile)
17:53:51 <widodh> jzb: Yes
17:54:12 <widodh> 2. rohityadav sent a mail on the ml. Just as a note, we should really try to keep the Git repo clean
17:54:30 <widodh> Make clean commits, stuff can break, we are humans, but make sure the commit message is clear
17:54:56 <widodh> That was #2
17:55:05 <rohityadav> yes, i requested everyone to follow our conventions and some git workflows
17:55:23 <widodh> #3: Mail traffic. Although the list has slowed down, the number of mail in the morning for EU guys is huge
17:55:26 <rohityadav> and pl. fix your tabs/editor
17:55:33 <rohityadav> if you have n't that is (big grin)
17:55:38 <widodh> I usually wake up with +/- 100 new e-mails
17:55:49 <rohityadav> widodh: almost same for me
17:55:57 <widodh> although I have filters, we should try to keep conversations shorter. Yes, it's al new
17:56:07 <jzb> widodh: how do you suggest that?
17:56:22 <widodh> jzb: Some times it pings back and forward between two persons
17:56:39 <chipc> widodh: the challenge there is that the "discussion" needs to be on list
17:56:49 <rohityadav> so, maybe they should come on irc, discuss and post their conclusions?
17:56:54 <rohityadav> on ml
17:56:59 <widodh> rohityadav: No, I don't think so
17:56:59 <chipc> and sometimes an email needs an ack
17:57:11 <widodh> chipc: Yes, I'm ok ofcourse with the +1, votes, etc
17:57:26 <chipc> noe was working on getting JIRA shunted over to another list
17:57:27 <widodh> But some discussions can really go on and when you are afk for 12+ hours, the traffic gets huge
17:57:30 <chipc> that might help significantly
17:57:39 <widodh> I already filter that away (wink)
17:57:48 <noe> hi
17:58:07 <noe> chipc: i can do that immediately, though i was a little perturbed by the lack of +1s from the project's principals
17:58:14 <widodh> I don't have an answer, but just a note, try to keep the discussions shorter, as in the number of e-mails
17:58:34 <widodh> the amount of information should ofcourse stay the same, we shouldn't go away from the ml
17:58:46 <rohityadav> noe: I ill subscribe to the other ml with jira msgs too, so virtually no differnce for me in my inbox
17:58:50 <rohityadav> *will
17:58:54 <chipc> noe: personally - I'm actually OK either way - I expect to have to read most / all of it anyway
17:59:01 <noe> it will clear up our mail-archives, which are, currenlty, almost impossuble to use
17:59:03 <chipc> noe: hense the indecision
17:59:10 <rohityadav> ok
17:59:22 <widodh> Ok, my last point, #4
17:59:27 <noe> look at this morras:
17:59:28 <jzb> noe: If I didn't +1 I thought it...
17:59:28 <noe> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201210.mbox/browser
17:59:43 <widodh> with all the commits going into master and 4.0, some go directly into 4.0, others go into master and get cherry picked to 4.0
17:59:51 <jzb> noe: but correct me on this - doesn't lazy consensus factor in here?
18:00:08 <noe> jzb: it does, and i mentioned that explicitly, BUT... i am/was being cautious
18:00:09 * widodh will wait (smile)
18:00:29 <noe> widodh: i think we have a combination of things going on
18:00:42 <noe> massive effort to ship our first release, so all sorts of threads going on in parallel
18:00:49 <noe> it's a huge scramble now the project is with the asf
18:00:49 <jzb> noe: OK. Maybe we should explictly call for +1s if we feel they're needed.
18:00:59 <noe> this should, hopefully, die down post-4.0
18:01:00 <rohityadav> widodh: I tried to sync some commits, but since build system on master is broken, so...
18:01:01 <jzb> if you did on that one, and I didn't +1 I apologize.
18:01:19 <noe> jzb: no worries, nobody has voiced any concerns so far
18:01:27 <noe> i would be interested to know what ke4qqq thinks
18:01:51 <widodh> noe: I do think it dies down post 4.0
18:01:55 <ke4qqq> on mail volume or lack of +1s?
18:01:58 <noe> the idea of hammering through issues on irc is a good one. not everything needs to be done on the mailing list
18:02:09 <rohityadav> I hope it dies too
18:02:13 <noe> ke4qqq: neither, on creating cloudstack-issues@
18:02:23 <rohityadav> noe: +1 yes
18:02:31 <noe> ke4qqq: i assume your tacit agreement, but it would be nice to have it explicitly
18:02:32 <jzb> noe: wait, what? (smile)
18:02:40 <noe> jzb: hmm?
18:02:42 * ke4qqq is in favor - but hopes we'd wait til 4.0 ships - getting people to switch to that layout will take a few weeks and would hate to see missed emails
18:02:48 <noe> ke4qqq: agreed
18:03:05 <jzb> noe: "not everything needs to be done on the mailing list" (wink)
18:03:19 <noe> jzb: yeah, not everything needs to be done there. just project decisions. big difference (wink)
18:03:22 <jzb> +1 ke4qqq
18:03:26 <noe> irc is very useful for hacking, conversational stuff
18:03:29 <jzb> noe: just poking
18:03:31 <noe> hehe
18:03:33 <jzb> I do that
18:03:37 * noe deletes jzb
18:03:56 <jzb> OK, I think we derailed ab it.
18:03:59 <jzb> er, a bit.
18:04:09 <noe> is the mtg still going?
18:04:16 <jzb> noe: yeah
18:04:20 <noe> heh, k
18:04:23 <jzb> widodh: you were on issue 4?
18:04:27 <widodh> jzb: Yes
18:04:29 <widodh> I have the feeling we will re-introduce a bug at some point
18:04:48 <widodh> It's just a feeling, but I think some commits will get "lost", we should be cautious
18:05:01 <widodh> Something that goes into 4.0 and never makes it back to master
18:05:11 <widodh> so the bug comes back in 4.1, when we branch that one off
18:06:07 <chipc> widodh: yes, I think we made a mistake of letting the build break in master
18:06:19 <chipc> that drove some confusion about where to do things
18:06:30 <chipc> lesson learned for next time I guess
18:06:35 <widodh> Indeed
18:06:37 <chipc> and we have to do some work to sync back
18:06:45 <widodh> This was also just a note
18:06:48 <widodh> EOF
18:07:03 <chipc> jzb: I have a request before we end
18:07:08 <jzb> chipc: shoot
18:07:11 <techpubs> And I have a question also
18:07:24 <chipc> actually 2 things
18:07:35 <chipc> techpubs: I just cherry-picked your doc changes to 4.0
18:07:44 <chipc> but I'd like to lock out other doc changes in that branch now
18:07:47 <chipc> that was 1
18:07:53 <techpubs> chipc: does that include the release notes, though?
18:07:57 <chipc> yes
18:08:09 <chipc> we can publish them out of master
18:08:17 <chipc> second, I need someone to jump on the issue that just hit the ML
18:08:21 <techpubs> chipc: ok
18:08:24 <chipc> "I have installed Ubuntu MS with non-oss build CloudStack-non-OSS-4.0.0-12.tar.  There is no cloudbridge db available."
18:08:45 <chipc> I need to know if that is environmental, tied to the install.sh script (that is NOT part of our release), or in the code itself
18:08:52 <chipc> plus, QA needs to be unblocked for actual testing
18:09:05 <chipc> anyone in here willing and able to get into it?
18:09:22 <rohityadav> chipc: that may be a packaging issue, on how/what sqls are deployed
18:09:25 <sudhap> chipc: looks like packaging is missing sql file
18:09:29 <rohityadav> widodh: can you check
18:09:53 <widodh> rohityadav: I can, but I really have no idea, I never used cloudbridge
18:10:02 <widodh> That db needs to get created somehow
18:10:10 <chipc> jzb: perhaps we can close this meeting down now
18:10:26 <chipc> and if we can move discussion over to #cloudstack-dev to figure out what's going wrong for QA?
18:10:50 <jzb> chipc: I believe techpubs had a question
18:10:55 <chipc> sorry!
18:11:01 <rohityadav> chipc: when you do cloud-setup-database it fails?
18:11:03 <jzb> chipc: no worries
18:11:24 <chipc> rohityadav: QA needs the help
18:11:28 <chipc> I was quoting from the ML
18:11:32 <techpubs> jzb: thanks, however my question was the same as Chips point #1, about whether release notes would be frozen on 4.0 from now. I'm done!
18:11:39 <jzb> Awesome
18:11:52 <jzb> OK all, that's a wrap. Thanks and see you same bat-time, and same bat-channel next week
18:11:59 <jzb> #endmeeting

  • No labels