Re: Review Request: (CLOUDSTACK-1638) Network plugins won't be notified VM migration.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/9871/ --- (Updated April 11, 2013, 7:22 a.m.) Review request for cloudstack, Hugo Trippaer

Re: CloudStack Chef Cookbooks

We have worked on a Chef cookbook that installs cloudstack/cloudplatform : https://github.com/ClogenyTechnologies/chef-repo/tree/master/cookbooks/csinstaller It works for both XenServer and VMWare. Although it is quite basic and assumes all the infrastructure is available .. -- Regards Chirag On

Share: SystemVM template for VMWare which has open-vm-tools

Hey community! The systemvm build job [1] fails to create VMWare compatible ova, I could not find a solution that would completely use opensource tools so I went ahead to use ovftool. First I import the vmdk produced by this buildjob [1] in a new VMWare Fusion/Workstation VM, fix it's compatibilit

Re: Review Request: Typos fixed

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/10411/#review18995 --- Ship it! Ship It! - Hiroaki Kawai On April 10, 2013, 11:06 p.m.,

Access to Jira system

Dear CloudStack-dev : May I have the access to the jira system(To be the assignee)? I'd like to take some unassigned tasks/issues. Many thanks. Regards Isaac

Access to Jira system

Dear CloudStack-dev : May I have the access to the jira system(To be the assignee)? I'd like to take some unassigned tasks/issues. Many thanks. Regards

Re: [DISCUSS] Don't assign tickets to people when triaging

>> >>I will start with an example: A critical bug (CLOUDSTACK-1941) that is >>blocking a release (4.1) is not picked up by any community member for 5 >>days ! >>The reason being that it is a UI issue but not that clear from the desc, >>the nature of the bug is known after someone spends time on it

Re: [DISCUSS] Don't assign tickets to people when triaging

On 11 April 2013 15:52, Abhinandan Prateek wrote: > >>> >>>I will start with an example: A critical bug (CLOUDSTACK-1941) that is >>>blocking a release (4.1) is not picked up by any community member for 5 >>>days ! >>>The reason being that it is a UI issue but not that clear from the desc, >>>the

Re: Review Request: Storage motion changes for xenserver

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/10196/ --- (Updated April 11, 2013, 11:02 a.m.) Review request for cloudstack, Abhinandan

Re: Associate IP feature request (RE: CLOUDSTACK-1942)

On 11 April 2013 01:08, Ryan Dietrich wrote: > RE: https://issues.apache.org/jira/browse/CLOUDSTACK-1942 > > I added this feature this morning, but before I present the diff to review > board, I'd like to have some feedback on the approach. I just want to make > sure how I did it is ok from the

Re: [DISCUSS] Don't assign tickets to people when triaging

On 11 April 2013 04:08, Abhinandan Prateek wrote: > > Now is it wrong to ask the community members who have expertise on UI to > fix it, in a bid to help Chip get the release out ? > It is certainly not wrong to co-ordinate with people in an effort to ship a release. (I would point out, however,

RE: Review request for storage motion on xenserver

Hi Edison, I have updated the patch [1] after incorporating your review comments. It also includes the changes to address the review comments given by Alex. Kindly take a look at the changes and let me know your comments. [1] https://reviews.apache.org/r/10196/ Regards, Devdeep > -Origina

Re: [DISCUSS] Don't assign tickets to people when triaging

On 11 April 2013 11:22, Abhinandan Prateek wrote: > > 7-8 days is a huge time lost. I was suggesting that this to be 3 days. Let > other community members chime in too. I should have replied to this in my previous missive. But I want to reenforce how unhealthy I believe this practice is. 7-8 day

Re: [DISCUSS] Don't assign tickets to people when triaging

On 11/04/13 4:23 PM, "prasanna" wrote: >On 11 April 2013 15:52, Abhinandan Prateek > wrote: >> I will start with an example: A critical bug (CLOUDSTACK-1941) that is blocking a release (4.1) is not picked up by any community member for 5 days ! The reason being that it is a

Re: [DISCUSS] Don't assign tickets to people when triaging

+1 On Apr 11, 2013, at 7:22 AM, Noah Slater wrote: > On 11 April 2013 11:22, Abhinandan Prateek > wrote: > >> >> 7-8 days is a huge time lost. I was suggesting that this to be 3 days. Let >> other community members chime in too. > > > I should have replied to this in my previous missive. Bu

Re: [DISCUSS] Don't assign tickets to people when triaging

I think it will be good if we also find out a process so that the release cycle is not affected by unclaimed bugs sitting out there. Here I am assuming the releases are important. I guess the discussion has turned into keeping things free without offering solutions to problems that that system wil

Re: [DISCUSS] Don't assign tickets to people when triaging

Of course releases are important. But if our current cadence is putting too much pressure on the community, one option might be to do our releases further apart from each other. Or, we get strict about the principal of time based releases: i.e. if your feature is not ready for the freeze, then it

Re: Access to Jira system

On Thu, Apr 11, 2013 at 5:59 AM, Isaac Chiang wrote: > Dear CloudStack-dev : > May I have the access to the jira system(To be the assignee)? > I'd like to take some unassigned tasks/issues. Many thanks. > > > Regards > Isaac Done Thanks! --David

[DOCS][ACS41] Release notes are failing the build

Hi all, Release notes are failing the build in jenkins.cs.o: http://jenkins.cloudstack.org/job/docs-4.1-releasenotes/372/console Release_Notes.xml:32: validity error : IDREF attribute linkend references an unknown ID "feedback" I created CLOUDSTACK-2007 for this. Joe, I think that you may be t

Re: [DISCUSS] Don't assign tickets to people when triaging

Yes, I think we need to space our releases further apart. I had big trouble when master was unstable for a while and specially on VMware it was difficult to deploy and test features. Yes for each issue I could have shouted on mail list I saw people doing that but the fact is that instability was

[DOCS] Documentation focused committers, and review processes

Hi all, I've observed Radhika struggling to get reviews of her feature docs, and having to work to provide patch after patch for reviewboard submissions. I have a proposal (which I think Joe hinted at in another thread): Doc writers with commit rights shouldn't use reviewboard to elicit reviews

Re: Share: SystemVM template for VMWare which has open-vm-tools

Alright, both of them are uploaded: SystemVM template for VMWare + open-vm-tools: http://people.apache.org/~bhaisaab/cloudstack/systemvmtemplates/systemvmtemplate-openvmtools-vmware.ova SystemVM template for VMWare + vmware-tools: http://people.apache.org/~bhaisaab/cloudstack/systemvmtemplates/sy

Re: Review Request: Typos fixed

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/10411/#review19001 --- Hi - the content looks good, but the actual patch looks wonky. Doesn

Re: Review Request: Typos fixed

> On April 11, 2013, 9:45 a.m., Hiroaki Kawai wrote: > > Ship It! Hiroaki, did this patch apply for you - it didn't for me. I used "git am -3" against master. Curious what you did differently. Thanks! - Joe --- This is an automatically

Re: Review Request: Typos fixed

> On April 11, 2013, 1:26 p.m., Joe Brockmeier wrote: > > Hi - the content looks good, but the actual patch looks wonky. Doesn't > > apply. Can you reformat and make sure that it applies against master? > > (Actually try applying it to master as a patch, if you haven't.) Thanks! my original pl

Re: [DISCUSS] Don't assign tickets to people when triaging

I believe it is possible to "mention" someone in a JIRA ticket in such a way that they get notified. Might this be an effective way of CCing someone into the conversation, without prescribing who should fix it? Might there be some room for exploration here? On Thursday, 11 April 2013, Abhinandan

Re: Access to Jira system

Thanks!:) On Thu, Apr 11, 2013 at 8:18 PM, David Nalley wrote: > On Thu, Apr 11, 2013 at 5:59 AM, Isaac Chiang > wrote: > > Dear CloudStack-dev : > > May I have the access to the jira system(To be the > assignee)? > > I'd like to take some unassigned tasks/issues. Many thanks. >

Re: Review Request: Typos fixed

If you can prepare a patch for master branch, it is welcome of course ! :-) 2013/04/11 22:45、"Pascal Borreli" のメッセージ: > > >> On April 11, 2013, 1:26 p.m., Joe Brockmeier wrote: >>> Hi - the content looks good, but the actual patch looks wonky. Doesn't >>> apply. Can you reformat and make sure

Re: Review Request: Typos fixed

> On April 11, 2013, 1:26 p.m., Joe Brockmeier wrote: > > Hi - the content looks good, but the actual patch looks wonky. Doesn't > > apply. Can you reformat and make sure that it applies against master? > > (Actually try applying it to master as a patch, if you haven't.) Thanks! > > Pascal Bor

Re: [DOCS] Documentation focused committers, and review processes

On Thu, Apr 11, 2013, at 08:04 AM, Chip Childers wrote: > I've observed Radhika struggling to get reviews of her feature docs, and > having to work to provide patch after patch for reviewboard submissions. > > I have a proposal (which I think Joe hinted at in another thread): Indeed. > Doc wri

Re: [DISCUSS] Don't assign tickets to people when triaging

On Thu, Apr 11, 2013, at 05:22 AM, Abhinandan Prateek wrote: > >Never would be too lenient. Maybe assign it after 7-8 days since they > >don't need immediate attention. > > 7-8 days is a huge time lost. I was suggesting that this to be 3 days. > Let other community members chime in too. Are we as

Re: [DOCS][ACS41] Release notes are failing the build

On Thu, Apr 11, 2013, at 07:31 AM, Chip Childers wrote: > Hi all, > > Release notes are failing the build in jenkins.cs.o: > > http://jenkins.cloudstack.org/job/docs-4.1-releasenotes/372/console > > Release_Notes.xml:32: validity error : IDREF attribute linkend > references an unknown ID "feedba

Re: [DISCUSS] Don't assign tickets to people when triaging

On 11 April 2013 15:11, Joe Brockmeier wrote: > > I'm against a policy of never assigning tickets, but it shouldn't be the > norm for one set of folks to triage tickets and assign them to another > set of folks. Me too. We should establish: a) A rule that we avoid ticket assignment by defau

Re: [DISCUSS] Don't assign tickets to people when triaging

On the Jira notification my suggestion will be to have a goto list of people for various domains of expertise. Anyone can register for these domains. When a bug is filed, the filer selects one of the domains he thinks that is right for getting the bug to be resolved. This alerts the people who ha

Re: [DISCUSS] Don't assign tickets to people when triaging

To me, it seems like what you're describing are components. You assign or sort the ticket into a component. Then I guess, people who are interested can watch that component for new issues. I am not sure if there's a way to "watch" a component in JIRA so that you get email notifications for it. I to

Re: [DISCUSS] Don't assign tickets to people when triaging

On Thu, Apr 11, 2013, at 09:28 AM, Noah Slater wrote: > To me, it seems like what you're describing are components. You assign or > sort the ticket into a component. Then I guess, people who are interested > can watch that component for new issues. I am not sure if there's a way > to > "watch" a co

Re: [DOCS][ACS41] Release notes are failing the build

On Thu, Apr 11, 2013, at 07:31 AM, Chip Childers wrote: > Hi all, > > Release notes are failing the build in jenkins.cs.o: > > http://jenkins.cloudstack.org/job/docs-4.1-releasenotes/372/console > > Release_Notes.xml:32: validity error : IDREF attribute linkend > references an unknown ID "feedba

Re: [DISCUSS] Don't assign tickets to people when triaging

On Thu, Apr 11, 2013 at 12:51:34PM +, Abhinandan Prateek wrote: > Yes, I think we need to space our releases further apart. That's a different discussion, which you are free to raise if you'd like. > Also community members should volunteer to own some part so that in above > circumstances a

Re: System VMs Failover

Anyone ever bumped into this yet? Thanks! On Wed, Apr 10, 2013 at 11:27 AM, Jeronimo Garcia wrote: > Hi List. > > Based on documentation and what I'm actually seeing now , system vms can > only failover to other hosts in the same cluster and therefore pod. > > I'm guessing this is because the

Re: [DISCUSS] Don't assign tickets to people when triaging

+1 On 11 April 2013 15:39, Chip Childers wrote: > On Thu, Apr 11, 2013 at 12:51:34PM +, Abhinandan Prateek wrote: > > Yes, I think we need to space our releases further apart. > > That's a different discussion, which you are free to raise if you'd like. > > > Also community members should v

Re: [jira] [Created] (CLOUDSTACK-2008) guest network vlan tag chain issue

I'll take a look at this when I get a moment, I'll wait until I have time before assigning it to myself. I'm thinking this has to do with the 'bond' device, since it's normally supposed to look in /proc/net/vlan, to see if the parent interface is tagged, and then look up the parent of THAT interfa

Re: [jira] [Commented] (CLOUDSTACK-2008) guest network vlan tag chain issue

Just a few quick things... cloudbr0 is being set as your guest bridge, right? See /etc/cloud/agent/agent.properties Is there a /proc/net/vlan/bond0.60? If so, can you send the contents? It should be building guest bridges off of whatever is listed in the "Device:" line in this file. There should

Re: [DISCUSS] Don't assign tickets to people when triaging

On Thu, Apr 11, 2013 at 8:09 PM, Chip Childers wrote: > On Thu, Apr 11, 2013 at 12:51:34PM +, Abhinandan Prateek wrote: > > Yes, I think we need to space our releases further apart. > > That's a different discussion, which you are free to raise if you'd like. > > > Also community members shoul

[ACS41][Patch Request]

commit ca8ac08cf37cd9ea8a50d323ac596da16319e7ab Author: Marcus Sorensen Date: Thu Apr 11 09:50:48 2013 -0600 CLOUDSTACK-2003: When accounts and domains are deleted, cleanup can fail, leaving instances in eternal expunged state. This happens when a domain is deleted while a deleted a

[ACS40][Patch Request]

commit ca8ac08cf37cd9ea8a50d323ac596da16319e7ab Author: Marcus Sorensen Date: Thu Apr 11 09:50:48 2013 -0600 CLOUDSTACK-2003: When accounts and domains are deleted, cleanup can fail, leaving instances in eternal expunged state. This happens when a domain is deleted while a deleted a

Re: [DISCUSS] Don't assign tickets to people when triaging

Abhi - not to gang up on you and I'm glad to see you share your opinions, concerns about release management and such. I see the problem you might be facing though. I think it would be better to have your internal JIRA mirror the ASF JIRA. That way you can triage as you please corporate style ;) in

Re: [ACS40][Patch Request]

On 04/11/2013 10:55 AM, Marcus Sorensen wrote: commit ca8ac08cf37cd9ea8a50d323ac596da16319e7ab Author: Marcus Sorensen Date: Thu Apr 11 09:50:48 2013 -0600 CLOUDSTACK-2003: When accounts and domains are deleted, cleanup can fail, leaving instances in eternal expunged state. This hap

Re: [DISCUSS] Don't assign tickets to people when triaging

On 11 April 2013 20:09, Chip Childers wrote: > On Thu, Apr 11, 2013 at 12:51:34PM +, Abhinandan Prateek wrote: >> Yes, I think we need to space our releases further apart. > > That's a different discussion, which you are free to raise if you'd like. > >> Also community members should volunteer

Re: [DOC] Opening vncextras firewall ports in ESXi 5.1

On 04/10/2013 04:23 PM, Jason Cadmus wrote: I have some documentation on how to accomplish this task and would like to contribute it to the ACS documentation for CS 4.1. Awesome! I am going through the following link below, trying to comprehend how to accomplish this. I have downloaded the so

Re: deployDataCenter.py doesn't work for me on master

I see the same issue here: On 4/10/13 11:00 PM, "Soheil Eizadi" wrote: >can not create vdi in sr

Re: deployDataCenter.py doesn't work for me on master

Is this the same as https://issues.apache.org/jira/browse/CLOUDSTACK-183 Check SMLog on the XenServer (I think it is /var/log/SMLog) On 4/10/13 11:00 PM, "Soheil Eizadi" wrote: >I debugged this further looks like there is problem in my XenServer >creating the VDI, the template vhd that is in t

Re: Associate IP feature request (RE: CLOUDSTACK-1942)

Well, listPublicIpAddress would only return Ip addresses already acquired via associateIpAddress (unless you are the admin, in which case it will return all public ips). On 4/11/13 4:13 AM, "prasanna" wrote: >On 11 April 2013 01:08, Ryan Dietrich wrote: >> RE: https://issues.apache.org/jira/bro

Re: System VMs Failover

Is this on vSphere? For other hypervisors, theoretically HA can start it on other clusters (since the control ip is link local). But if there is capacity available on the first cluster, why not restart it on the original cluster? On 4/11/13 7:54 AM, "Jeronimo Garcia" wrote: >Anyone ever bumped

Re: System VMs Failover

System VMs are tend to be running in stateless mode, instead of fail-over of same VM, we are launching new instance of them, this behave is done for storage and console proxy system VM, for virtual router system VM, there is a redundant configuration, automatic HA would make the redundant configura

systemvm.iso does not get copied with mvn jetty:run

Hi Hugo, With the change 4a7d392f1, the systemvm.iso no longer appears in cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/vms/systemvm.iso For 'clean' hypervisors this means that during a developer build and test, the systemvm.iso is no longer copied over. I'd like to revert this. I do not unders

Re: [ACS41][Patch Request]

On Thu, Apr 11, 2013 at 09:55:38AM -0600, Marcus Sorensen wrote: > commit ca8ac08cf37cd9ea8a50d323ac596da16319e7ab > Author: Marcus Sorensen > Date: Thu Apr 11 09:50:48 2013 -0600 > > CLOUDSTACK-2003: When accounts and domains are deleted, cleanup can > fail, > leaving instances in eter

Re: [ACS41][Patch Request]

On Wed, Apr 10, 2013 at 12:28:57PM -0600, Marcus Sorensen wrote: > This is a follow-up to previous patch request for CLOUDSTACK-1565 that we > though should go into 4.1 > > commit 9670553ea85d6593046425f2c040cc08d2e61733 > Author: Marcus Sorensen > Date: Wed Apr 10 12:17:31 2013 -0600 > >

Re: [ACS41][Patch Request]

On Wed, Apr 10, 2013 at 12:28:57PM -0600, Marcus Sorensen wrote: > This is a follow-up to previous patch request for CLOUDSTACK-1565 that we > though should go into 4.1 > > commit 9670553ea85d6593046425f2c040cc08d2e61733 > Author: Marcus Sorensen > Date: Wed Apr 10 12:17:31 2013 -0600 > >

Re: [ACS41][Patch Request]

On Wed, Apr 10, 2013 at 12:39:24PM -0600, Marcus Sorensen wrote: > commit be55c5b3a58376eb2048a8add155ff09f14e65eb > Author: Marcus Sorensen > Date: Tue Apr 9 16:26:08 2013 -0600 > > VPC - new system vm doesn't bring up eth0 reliably, and we don't set > eth0 to > auto start like we shou

Re: [ACS41][Patch Request]

On Wed, Apr 10, 2013 at 11:11:21PM +, Likitha Shetty wrote: > Branch: refs/heads/master > Commit: a0b5ebccb814cbb12c5f40aa0c8894ebb3b322d6 > Author: Likitha Shetty > Date: Thu Apr 11 04:25:31 2013 +0530 > > CLOUDSTACK-1988. Attempting to register a AWS API user fails with error code >

Re: [MERGE] ASA 1000v as external firewall in isolated guest networks

On Mon, Apr 08, 2013 at 01:08:42PM +, Koushik Das wrote: > I would like to merge the feature "ASA 1000v as external firewall in isolated > guest networks" to master. Please find the details here: > > Proposal: > http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-users/201301.mbox/

Re: deployDataCenter.py doesn't work for me on master

Can you revert 4a7d392f1 in your workspace and rebuild? On 4/11/13 9:55 AM, "Chiradeep Vittal" wrote: >Is this the same as >https://issues.apache.org/jira/browse/CLOUDSTACK-183 > >Check SMLog on the XenServer (I think it is /var/log/SMLog) > > >On 4/10/13 11:00 PM, "Soheil Eizadi" wrote: > >>I

Re: [MERGE] Dedicate Public IP Addresses

On Tue, Apr 09, 2013 at 05:23:05PM +, Likitha Shetty wrote: > Hi all, > > I would like to merge the feature Dedicate Public IP ranges to master. > > Jira ticket - https://issues.apache.org/jira/browse/CLOUDSTACK-704 > Proposal discussion - > http://mail-archives.apache.org/mod_mbox/incubato

RE: [DISCUSS] Don't assign tickets to people when triaging

> -Original Message- > From: Chip Childers [mailto:[email protected]] > Sent: Thursday, April 11, 2013 7:40 AM > To: > Subject: Re: [DISCUSS] Don't assign tickets to people when triaging > > On Thu, Apr 11, 2013 at 12:51:34PM +, Abhinandan Prateek wrote: > > Yes, I think we

Re: systemvm.iso does not get copied with mvn jetty:run

Ouch. I'll try and fix that. Without this commit it would use the systemvm.iso from the previous compile, which is also bad. Probably some tweaking in the phases should be ok. Cheers, Hugo Sent from my iPhone On 11 apr. 2013, at 19:33, Chiradeep Vittal wrote: > Hi Hugo, > > With the chang

RE: [DISCUSS] Don't assign tickets to people when triaging

> -Original Message- > From: Joe Brockmeier [mailto:[email protected]] > Sent: Thursday, April 11, 2013 7:34 AM > To: [email protected] > Subject: Re: [DISCUSS] Don't assign tickets to people when triaging > > On Thu, Apr 11, 2013, at 09:28 AM, Noah Slater wrote: > > To me, it seem

Re: System VMs Failover

Hi. Thanks for your answer . System vms images are normally in secondary storage , and currently i have 3 pods and one and only secondary storage nfs system, When i shut down all the servers on POD1 , the system vms refused to launch in pod2 , would it be cause Pod2 has to have it's own second

[JENKINS] Possible problem with Release Notes build setup

Chip pointed out that the Jenkins process for the release notes in 4.1 was failing, but it looks like a problem with the job rather than the actual docs being busted. See ticket CLOUDSTACK-2007 (https://issues.apache.org/jira/browse/CLOUDSTACK-2007). Can someone with Jenkins access/wizardry tak

Re: systemvm.iso does not get copied with mvn jetty:run

Yes! From: Hugo mailto:[email protected]>> Date: Thursday, April 11, 2013 11:52 AM To: Chiradeep Vittal mailto:[email protected]>> Cc: "[email protected]" mailto:[email protected]>>, "[email protected]" mailto:h.

Re: systemvm.iso does not get copied with mvn jetty:run

Just noticed Kelvens commit f35272b6c585f85c5c0f1e92f99b8224feceb29e That fixed it right? Cheers, Hugo On Thu, Apr 11, 2013 at 8:46 PM, Hugo Trippaers wrote: > Ouch. I'll try and fix that. Without this commit it would use the > systemvm.iso from the previous compile, which is also bad. > > P

[HA][ACS]Running Multiple CS Management hosts under LB

I recall watching one of the videos on youtube where Chiradeep mentioned that CS Management service is stateless and you can run multiple CS MS connected to MySQL DB. We need to setup High Availability hopefully Active/Active for CloudStack Management hosts. With that in mind, I'm curious if a

Re: Review Request: Remove 2k limitation for user data on a deployVMCmd issued as an HTTP POST request

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/10294/#review19030 --- server/src/com/cloud/vm/UserVmManagerImpl.java

Re: Review Request: Remove 2k limitation for user data on a deployVMCmd issued as an HTTP POST request

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/10294/#review19032 --- In your description, you mentioned that it is not extensively tested

[ACS41] Help needed clearing bugs!

Hi all, I need your help clearing out the following bugs... if you have one assigned to you, please see if you can get it completed. If you have any time available, and think you can help resolve one of the unassigned ones, please jump in! We're obviously behind the schedule that we set for our

Re: [HA][ACS]Running Multiple CS Management hosts under LB

this is outlined in the installation guide under section: 4.5.6. Prepare and Start Additional Management Servers. usually fronted by a load balancer with a session/sticky policy. On Thu, Apr 11, 2013 at 1:00 PM, Musayev, Ilya wrote: > I recall watching one of the videos on youtube where Chirade

RE: [MERGE] affinity_groups branch to master

This is now merged to master. Thanks, Prachi -Original Message- From: Chip Childers [mailto:[email protected]] Sent: Wednesday, April 10, 2013 10:54 AM To: [email protected] Subject: Re: [MERGE] affinity_groups branch to master On Fri, Apr 05, 2013 at 05:26:15PM -0700, P

Re: [ACS41] Help needed clearing bugs!

about CLOUDSTACK-1978, it looks like the problem at hypervsor host side, the hypervisor host is either failed to setup the VNC listening interface or failed to configure firewall properly, could KVM developer pick this up(I assume it is KVM hypervisor)? Kelven On 4/11/13 2:11 PM, "Chip Childers"

[ASFCS42] Proposed schedule for our next release

Based on the community discussions of having 4 month cadence I am proposing the following schedule: = 4.2 detailed schedule proposal: = 2013-05-31 Feature Freeze All new feature need to have been merged into master by this date.

Re: [ACS41] Help needed clearing bugs!

I believe I have a fix for CLOUDSTACK-1987. https://reviews.apache.org/r/10426/ On Apr 11, 2013, at 3:40 PM, Kelven Yang wrote: > about CLOUDSTACK-1978, it looks like the problem at hypervsor host side, > the hypervisor host is either failed to setup the VNC listening interface > or failed to c

Re: [ACS41] Help needed clearing bugs!

I haven't even touched openvswitch, or I'd take a look at 1978. Is that a prerequisite for duplicating the issue? On Apr 11, 2013 3:41 PM, "Kelven Yang" wrote: > about CLOUDSTACK-1978, it looks like the problem at hypervsor host side, > the hypervisor host is either failed to setup the VNC listen

RE: [ACS41] Help needed clearing bugs!

Probably, it's a setup issue, e.g openvswitch doesn't work. I'll take a look QA's environment, if it's still there. > -Original Message- > From: Marcus Sorensen [mailto:[email protected]] > Sent: Thursday, April 11, 2013 5:12 PM > To: [email protected] > Subject: Re: [ACS41] Hel

RE: [ACS41] Help needed clearing bugs!

I will take a look at CLOUDSTACK-1987. -Prachi -Original Message- From: Edison Su [mailto:[email protected]] Sent: Thursday, April 11, 2013 5:17 PM To: [email protected] Subject: RE: [ACS41] Help needed clearing bugs! Probably, it's a setup issue, e.g openvswitch doesn't work

[QA][PROPOSAL][ACS4.2] Test plan review: ACLs on Private Gateway Feature in n-Tier

Hello Jayapal, Please review the test plan for feature "ACLs on Private Gateway Feature" and let me know the review comments. The test cases are mentioned in an excel sheet attached to the page. Test Plan : https://cwiki.apache.org/confluence/display/CLOU

Re: [ACS41] Help needed clearing bugs!

Could you look at this first? https://reviews.apache.org/r/10426/ On Apr 11, 2013, at 6:25 PM, Prachi Damle wrote: > I will take a look at CLOUDSTACK-1987. > > -Prachi > > -Original Message- > From: Edison Su [mailto:[email protected]] > Sent: Thursday, April 11, 2013 5:17 PM > To

RE: [ACS41] Help needed clearing bugs!

Hi Ryan, Yes Sure, my bad, will look at the patch first. Thanks, Prachi -Original Message- From: Ryan Dietrich [mailto:[email protected]] Sent: Thursday, April 11, 2013 5:46 PM To: [email protected] Subject: Re: [ACS41] Help needed clearing bugs! Could you look at this fi

Re: Master broken

These issues are caused by that some of components are not really mocked, instead, they are loaded directly main source. One of the benefits from Spring is that it integrates with Mokito nicely, all we need is to probably have a base test configuration that returns all mocked DAOs or other common

Re: [ACS41] Help needed clearing bugs!

Hi Ryan, Maybe I overlooked something, but I could not understand how your patch is fixing CLOUDSTACK-1987. It would be appreciated if you can address my comment in that patch. Thanks -min On 4/11/13 5:52 PM, "Prachi Damle" wrote: >Hi Ryan, > >Yes Sure, my bad, will lo

Re: [ACS41] Help needed clearing bugs!

Does it fix 1989, or perhaps both? https://issues.apache.org/jira/browse/CLOUDSTACK-1989 On Apr 11, 2013 7:08 PM, "Min Chen" wrote: > Hi Ryan, > > Maybe I overlooked something, but I could not understand how your > patch > is fixing CLOUDSTACK-1987. It would be appreciated if you can add

Master api-docs build

Raising this again. Jenkins seems to not be cleaning up properly. The dedicatePublicIpRange patch was reverted a few days ago and the build should be successful. On 4/11/13 3:05 PM, "Apache Jenkins Server" wrote: >See > >Chang

Re: Master api-docs build

452 has actually passed the build. -- Prasanna., - Original Message - From: Chiradeep Vittal [mailto:[email protected]] Sent: Friday, April 12, 2013 09:41 AM To: [email protected] Subject: Master api-docs build Raising this again. Jenkins seems to not be cleaning up pr

Re: [JENKINS] Possible problem with Release Notes build setup

I'll look into this today. Assuming this is on jenkins.cs.o. -- Prasanna., - Original Message - From: Joe Brockmeier [mailto:[email protected]] Sent: Friday, April 12, 2013 03:38 AM To: [email protected] Subject: [JENKINS] Possible problem with Release Notes build setup Chip poin

Re: System VMs Failover

just to clarify I'm using KVM. Thanks! On Thu, Apr 11, 2013 at 1:26 PM, Jeronimo Garcia wrote: > Hi. > > Thanks for your answer . > System vms images are normally in secondary storage , and currently i > have 3 pods and one and only secondary storage nfs system, > > When i shut down all the se

Re: System VMs Failover

Secondary storage is zone wide not pod-specific. Pod2 probably has some problems (enough shared storage perhaps?). The MS logs should indicate the problem. On 4/11/13 7:03 PM, "Jeronimo Garcia" wrote: >just to clarify I'm using KVM. > >Thanks! > > >On Thu, Apr 11, 2013 at 1:26 PM, Jeronimo Garci

Re: Review Request: Remove 2k limitation for user data on a deployVMCmd issued as an HTTP POST request

> On April 11, 2013, 8:54 p.m., Min Chen wrote: > > server/src/com/cloud/vm/UserVmManagerImpl.java, line 2581 > > > > > > Based on your comment, for GET, maxBytes = 4K, for POST, maxBytes = > > 32K. Why not define th

Re: System VMs Failover

Thanks. Is primary storage zone wide too? On Thu, Apr 11, 2013 at 9:06 PM, Chiradeep Vittal < [email protected]> wrote: > Secondary storage is zone wide not pod-specific. > Pod2 probably has some problems (enough shared storage perhaps?). The MS > logs should indicate the problem. >

Re: [JENKINS] Possible problem with Release Notes build setup

On Thu, Apr 11, 2013, at 08:48 PM, Prasanna Santhanam wrote: > I'll look into this today. Assuming this is on jenkins.cs.o. That's correct, it's this job: http://jenkins.cloudstack.org/job/docs-4.1-releasenotes/ Sorry, should have provided that previously. Thanks! Best, jzb -- Joe Brockmeie

[QA][PROPOSAL][ACS4.2] Test plan review: GSLB (Global Server Load Balancing)

Hi Murali, Please review the test plan [1] for feature " GSLB (Global Server Load Balancing)" and let me know the review comments. The test cases are mentioned in an excel sheet attached to the page. [1] Test Plan : https://cwiki.apache.org/confluence/pa

Re: System VMs Failover

it could be per cluster or per host (local storage) at the moment. I believe after the storage refactor work happens is when support for zone wide primary *might* become a reality. On Thu, Apr 11, 2013 at 7:28 PM, Jeronimo Garcia wrote: > Thanks. > > Is primary storage zone wide too? > > > > On

Re: [DISCUSS] Don't assign tickets to people when triaging

+1 To what Chip had to say on this thread. My use of ownership was wrong and I actually meant "interest". I have also started on the producingoss.com as suggested by Rohit, looks like a good way to understand the working of a voluntary community. So now that I am positive on the community feedback

Review Request: Fixed typo in public class

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/10427/ --- Review request for cloudstack. Description --- Fixed typo in public class,

  1   2   >