Review Request: Snapshot errors with multiple secondary storage in one zone.

2012-10-14 Thread deepti dohare
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/7594/ --- Review request for cloudstack, Nitin Mehta and anthony xu. Description ---

[jira] [Assigned] (CLOUDSTACK-235) Network rate can be set in 2 places. Clarify docs on how this works.

2012-10-14 Thread Radhika Nair (JIRA)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair reassigned CLOUDSTACK-235: --- Assignee: Radhika Nair > Network rate can be set in 2 places. Clarify docs on

[jira] [Commented] (CLOUDSTACK-344) Docs still point to old location for many of the cloud-* tools

2012-10-14 Thread David Nalley (JIRA)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475974#comment-13475974 ] David Nalley commented on CLOUDSTACK-344: - please leave this open until the co

[jira] [Reopened] (CLOUDSTACK-344) Docs still point to old location for many of the cloud-* tools

2012-10-14 Thread David Nalley (JIRA)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley reopened CLOUDSTACK-344: - > Docs still point to old location for many of the cloud-* tools > --

Re: Review Request: Fixed CLOUDSTACK-303 and CLOUDSTACK-344 (Upgrade instructions in RN and location for many of the cloud-* tools in multiple install doc files)

2012-10-14 Thread Radhika PC
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/7593/ --- (Updated Oct. 15, 2012, 5:04 a.m.) Review request for cloudstack, David Nalley,

[jira] [Resolved] (CLOUDSTACK-344) Docs still point to old location for many of the cloud-* tools

2012-10-14 Thread Radhika Nair (JIRA)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-344. - Resolution: Fixed Fix Version/s: 4.0.0 > Docs still point to old location

[jira] [Resolved] (CLOUDSTACK-303) Upgrade instructions in the 4.0 release notes are wrong.

2012-10-14 Thread Radhika Nair (JIRA)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-303. - Resolution: Fixed Fix Version/s: 4.0.0 https://reviews.apache.org/r/7593/

[jira] [Commented] (CLOUDSTACK-344) Docs still point to old location for many of the cloud-* tools

2012-10-14 Thread Radhika Nair (JIRA)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475965#comment-13475965 ] Radhika Nair commented on CLOUDSTACK-344: - fixed https://reviews.apache.org/r/

Review Request: Fixed CLOUDSTACK-303 and CLOUDSTACK-344 (Upgrade instructions in RN and location for many of the cloud-* tools in multiple install doc files)

2012-10-14 Thread Radhika PC
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/7593/ --- Review request for cloudstack, David Nalley, Chip Childers, Jessica Tomechak, and

[jira] [Assigned] (CLOUDSTACK-301) Nexus 1000v DVS integration is not functional

2012-10-14 Thread Devdeep Singh (JIRA)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-301: Assignee: Sateesh Chodapuneedi (was: Devdeep Singh) > Nexus 1000v DVS inte

[jira] [Commented] (CLOUDSTACK-303) Upgrade instructions in the 4.0 release notes are wrong.

2012-10-14 Thread Radhika Nair (JIRA)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475960#comment-13475960 ] Radhika Nair commented on CLOUDSTACK-303: - There is no upgrade process as such

[jira] [Assigned] (CLOUDSTACK-344) Docs still point to old location for many of the cloud-* tools

2012-10-14 Thread Radhika Nair (JIRA)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair reassigned CLOUDSTACK-344: --- Assignee: Radhika Nair > Docs still point to old location for many of the clo

[jira] [Closed] (CLOUDSTACK-340) Tomcat config files broken after ant deploy-server

2012-10-14 Thread edison su (JIRA)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] edison su closed CLOUDSTACK-340. Resolution: Fixed > Tomcat config files broken after ant deploy-server > --

[jira] [Commented] (CLOUDSTACK-340) Tomcat config files broken after ant deploy-server

2012-10-14 Thread edison su (JIRA)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475953#comment-13475953 ] edison su commented on CLOUDSTACK-340: -- It will go away after 4.0, when we move t

Re: FS on cloudStack createSnapshot synchronization improvement

2012-10-14 Thread Alena Prokharchyk
Anthony, I implemented the threshold logic on Api Layer, in SyncQueueJob manager. In other words, before submitting the job for execution, we should know the host the job would go first to – that would be the object we are synchronizing on. For createSnapshot it's always the host where vm is 1)

RE: FS on cloudStack createSnapshot synchronization improvement

2012-10-14 Thread Anthony Xu
There are several commands need this kind of threshold, e.g. Move volume, create template from snapshot, So this is common requirement , not only for createsnapshot. Can we add threshold mechanism in host command queue to resolve this issue? Anthony -Original Message- From: Edison Su [m

[jira] [Created] (CLOUDSTACK-345) libvirt on el6.3 doesn't start without disabling mdns advertisement

2012-10-14 Thread David Nalley (JIRA)
David Nalley created CLOUDSTACK-345: --- Summary: libvirt on el6.3 doesn't start without disabling mdns advertisement Key: CLOUDSTACK-345 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-345 Proje

RE: Egress firewall rules for guest network.

2012-10-14 Thread Anthony Xu
> We need to understand how network ACL rules are different from >Firewall rules. The difference comes about when you look at the >stateful/stateless nature of traffic being shaped by the router. In >most networking parlance I have seen, network ACLs serve only stateless >behaviour. Firewalls

[jira] [Created] (CLOUDSTACK-344) Docs still point to old location for many of the cloud-* tools

2012-10-14 Thread David Nalley (JIRA)
David Nalley created CLOUDSTACK-344: --- Summary: Docs still point to old location for many of the cloud-* tools Key: CLOUDSTACK-344 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-344 Project: C

Re: [HUMOR] [VOTE] Apache Cloudstack 4.0.0-incubating Release, second round

2012-10-14 Thread Chip Childers
Sebastian was making a joke. Please keep reviewing the RC and voting. - chip Sent from my iPhone. On Oct 14, 2012, at 4:50 PM, Noah Slater wrote: > Gmail hid that from me. What I'm getting at is is there any truth to what > Sebastien said? I don't understand it. > > On Sun, Oct 14, 2012 at 9:4

Re: [HUMOR] [VOTE] Apache Cloudstack 4.0.0-incubating Release, second round

2012-10-14 Thread Noah Slater
Gmail hid that from me. What I'm getting at is is there any truth to what Sebastien said? I don't understand it. On Sun, Oct 14, 2012 at 9:46 PM, Chip Childers wrote: > Note the "[HUMOR]" prefix. ;) > > - chip > > Sent from my iPhone. > > On Oct 14, 2012, at 4:22 PM, Noah Slater wrote: > > > Ple

Re: [HUMOR] [VOTE] Apache Cloudstack 4.0.0-incubating Release, second round

2012-10-14 Thread Chip Childers
Note the "[HUMOR]" prefix. ;) - chip Sent from my iPhone. On Oct 14, 2012, at 4:22 PM, Noah Slater wrote: > Please clarify, Sebastien. > > On Sun, Oct 14, 2012 at 8:58 PM, Sebastien Goasguen wrote: > >> In our angst to get the RC out and vote, it appears to me that we failed >> to put up an al

Re: [HUMOR] [VOTE] Apache Cloudstack 4.0.0-incubating Release, second round

2012-10-14 Thread Noah Slater
Please clarify, Sebastien. On Sun, Oct 14, 2012 at 8:58 PM, Sebastien Goasguen wrote: > In our angst to get the RC out and vote, it appears to me that we failed > to put up an alternative release candidate. > > Shouldn't we have a debate and organize polls for couple weeks before > actually votin

[HUMOR] [VOTE] Apache Cloudstack 4.0.0-incubating Release, second round

2012-10-14 Thread Sebastien Goasguen
In our angst to get the RC out and vote, it appears to me that we failed to put up an alternative release candidate. Shouldn't we have a debate and organize polls for couple weeks before actually voting ? We could have Super PACs and the likes…What fun !!! -Sebastien On Oct 14, 2012, at 4:34

[jira] [Commented] (CLOUDSTACK-340) Tomcat config files broken after ant deploy-server

2012-10-14 Thread David Nalley (JIRA)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475876#comment-13475876 ] David Nalley commented on CLOUDSTACK-340: - I think Edison's intent is to say t

[jira] [Reopened] (CLOUDSTACK-340) Tomcat config files broken after ant deploy-server

2012-10-14 Thread John Kinsella (JIRA)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Kinsella reopened CLOUDSTACK-340: -- That's what we're going to tell our users?? > Tomcat config files brok

Re: Rant: Request for better commit messages

2012-10-14 Thread Marcus Sorensen
Yeah, that's an option too. The reason I was thinking going the hook route was because we could provide one file that will work for everyone (auto populate the signed-off-by and perhaps other things). Basically because it's scriptable. Then they can just copy it to .git/hooks on their own. That's t

[jira] [Updated] (CLOUDSTACK-343) Document what tools and packages are required to build, package and install CloudStack 4.0

2012-10-14 Thread Rohit Yadav (JIRA)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav updated CLOUDSTACK-343: --- Environment: This was verified for only Ubuntu 12.04. > Document what tools and packa

Re: Debian packaging buildrequires: was Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, second round

2012-10-14 Thread Rohit Yadav
On 14-Oct-2012, at 9:45 PM, David Nalley wrote: > Rohit: > > Can you make sure a bug gets filed so that these are listed as > requires or build requires? Sure, done: https://issues.apache.org/jira/browse/CLOUDSTACK-343 > > --David > > On Sun, Oct 14, 2012 at 10:34 AM, Rohit Yadav wrote: >>

[jira] [Created] (CLOUDSTACK-343) Document what tools and packages are required to build, package and install CloudStack 4.0

2012-10-14 Thread Rohit Yadav (JIRA)
Rohit Yadav created CLOUDSTACK-343: -- Summary: Document what tools and packages are required to build, package and install CloudStack 4.0 Key: CLOUDSTACK-343 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3

Re: Rant: Request for better commit messages

2012-10-14 Thread Rohit Yadav
On 14-Oct-2012, at 9:18 PM, Marcus Sorensen wrote: > I'm by no means a git guru, but in searching around it didn't seem like > there was a way to enforce the application of hooks from the repo side. > I'm not sure we'd want to anyway. I was just going to commit the file and > then add instructio

Debian packaging buildrequires: was Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, second round

2012-10-14 Thread David Nalley
Rohit: Can you make sure a bug gets filed so that these are listed as requires or buildrequires? --David On Sun, Oct 14, 2012 at 10:34 AM, Rohit Yadav wrote: > +1 > > Tested on Ubuntu 12.04 > > Corrected the building/packaging wiki; [0] > For debian packaging make sure you've following preinsta

Re: Rant: Request for better commit messages

2012-10-14 Thread Marcus Sorensen
I'm by no means a git guru, but in searching around it didn't seem like there was a way to enforce the application of hooks from the repo side. I'm not sure we'd want to anyway. I was just going to commit the file and then add instructions on the wiki for people to add it in their local repo config

[jira] [Resolved] (CLOUDSTACK-341) Failing to display Management Traffic Details on the UI

2012-10-14 Thread Rohit Yadav (JIRA)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav resolved CLOUDSTACK-341. Resolution: Fixed Applied in master: commit 4c69cac42e907ccdae3e5d3793ab91da1c1d617c Au

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, second round

2012-10-14 Thread Rohit Yadav
+1 Tested on Ubuntu 12.04 Corrected the building/packaging wiki; [0] For debian packaging make sure you've following preinstalled: aptitude dpkg-dev debhelper tomcat6 libws-commons-util-java python-mysqldb (for installation via install.sh, aptitude should be installed) - No build, packaging, or

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, second round

2012-10-14 Thread Sebastien Goasguen
+1 Followed test procedure on 10.8.1 macbook air, (skipped md5, git comparison), started/destroyed instance via GUI. started/destroyed instance via python boto, describe images via SOAP, terminated instance via SOAP. Happy :) -sebastien On Oct 14, 2012, at 4:32 AM, Chip Childers wrote: > Hi

[jira] [Updated] (CLOUDSTACK-341) Failing to display Management Traffic Details on the UI

2012-10-14 Thread Sudha Ponnaganti (JIRA)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-341: Assignee: Rohit Yadav > Failing to display Management Traffic Details on th

Re: Rant: Request for better commit messages

2012-10-14 Thread Rohit Yadav
On 12-Oct-2012, at 10:29 PM, Marcus Sorensen wrote: > Sure thing. A few questions: > > the "CLOUDSTACK- prefix:" line, should that be changed to > simply "Bug id:"? I guess as there are already several commits that follow CLOUDSTACK-BUGID convention, we should continue that. Also, there are