RE: FW: [ACS44] Cherry pick for CLOUDSTACK-6519

Thanks Daan. -Original Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: Friday, May 30, 2014 11:32 PM To: dev Subject: Re: FW: [ACS44] Cherry pick for CLOUDSTACK-6519 Rajesh, it seems this is already in 4.4 it was pulled in May 13th. On Fri, May 30, 2014 at 12:49 PM

Re: [DOCS] Problem generating 4.4 API docs

Hi Will, I don't know why it was not updated, one reason, I'm anticipating, could be that we moved to Spring for many things which uses bunch of xmls for some configuration, any not this properties file anymore? Probably Alex or Kelven could comment if this is the case. I think you can add the cl

Re: [DISCUSS] Proposal to submit NuageVsp plugin support in CloudStack 4.5

LGTM. Please add the spec on the wiki. Take a look at the spec template https://cwiki.apache.org/confluence/display/CLOUDSTACK/Design+Document+Template Please consider how one might test your feature without actually running the controller. From: cloudstack-ci mailto:cloudstack...@nuagenetworks

Re: [DISCUSS] Brocade network plugin to orchestrate Brocade VCS cluster for CloudStack 4.5

LGTM. Please create an FS on the wiki if you haven’t already. Take a look at the document template: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Design+Document+Template From: Ritu Sabharwal mailto:rsabh...@brocade.com>> Reply-To: "dev@cloudstack.apache.org

Re: [ACS44] Cherry pick CLOUDSTACK-6599

Please cherry-pick be765ce8680564b743a73dd360c590c0e495c204 as well as part of this bug. One more thing to add, majority of code is for the functionality which I found missing in 4.4 and found some bugs which I termed as improvements over previous design. Thanks, -Nitin On 30/05/14 3:06 PM, "Niti

Re: [PROPOSAL] - Change Primary IP Address

Although it appears to be trivial, you have to take care of PF and LB rules that might already exist to the old IP. From: Chiradeep Vittal mailto:chiradeep.vit...@citrix.com>> Reply-To: "dev@cloudstack.apache.org" mailto:dev@cloudstack.apache.org>> Date: Wednes

Re: [DOCS] Problem generating 4.4 API docs

I have completely started from scratch with a new clone of the CloudStack repo. Master is now pointing to 4.5, so I checked out the 4.4 branch. I put all the deps in place as well as the vhd-util file. I completely removed my ~/.m2 directory so I am starting from completely clean. I checked the

Re: [QUESTION] CallContext

Thanks, Daan I logged the following ticket: https://issues.apache.org/jira/browse/CLOUDSTACK-6815 On Fri, May 30, 2014 at 2:50 PM, Daan Hoogland wrote: > h Mike, sounds like a bug to me :) > > On Fri, May 30, 2014 at 8:14 PM, Mike Tutkowski > wrote: > > Any thoughts on this? > > > > Thanks!

Re: [ACS44] Cherry pick CLOUDSTACK-6599

Daan - Here improvements are actually bug fixes that should be fixed. Thanks, -Nitin On 30/05/14 1:47 PM, "Daan Hoogland" wrote: >That's a lot of improvements without tests, Nitin. > >On Fri, May 30, 2014 at 8:14 PM, Nitin Mehta >wrote: >> Hello Daan, >> >> Can you please cherry-pick the follo

Re: The distribution of your message dated Fri, 30 May 2014...

I've been getting them all day about my polemic wiht Marcus. All mail went through though so I didn't give them my second braincel. On Fri, May 30, 2014 at 7:50 PM, Mike Tutkowski wrote: > I know it says no action is required on my part, but I've never received an > automated message like this fr

Re: Review Request 22093: VPC's VR missing public NIC eth1

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/22093/ --- (Updated May 30, 2014, 9 p.m.) Review request for cloudstack and Marcus Sorense

Re: VPC's VR missing public NIC eth1

On Fri, May 30, 2014 at 10:51 PM, Marcus wrote: > Looks good to me, aside from he debug statement. Ah, the first line was not in my line of sight. -- Daan

Re: [DOCS] Problem generating 4.4 API docs

On 05/30/2014 10:40 PM, Will Stevens wrote: Thanks Rohit, I will do all those steps. I know the git branch is correct, but I will do a clean anyway. Removing the maven repositories is a good idea. NB; for this issue, e.g., fear of old cloudstack stuff being used rather then newly built bits,

RE: License to be signed for contributing to CloudStack

Hi Sebastian, This gives a real good picture of the IP clearance process. I sent a Proposal email to mailing list last week, still waiting for acceptance. Can you please have a look at it and provide feedback? I am in the state to submit my design document to CloudStack wiki. I have created ac

Re: [QUESTION] CallContext

h Mike, sounds like a bug to me :) On Fri, May 30, 2014 at 8:14 PM, Mike Tutkowski wrote: > Any thoughts on this? > > Thanks! :) > > > On Sat, May 24, 2014 at 10:39 PM, Mike Tutkowski < > mike.tutkow...@solidfire.com> wrote: > >> Hi, >> >> I noticed while executing the createStoragePool command t

Re: [ACS44] Cherry pick CLOUDSTACK-6599

That's a lot of improvements without tests, Nitin. On Fri, May 30, 2014 at 8:14 PM, Nitin Mehta wrote: > Hello Daan, > > Can you please cherry-pick the following commit from 4.4-forward to 4.4 ? > > commit 48ea9e0b5e87fee067b711890cd5a5d7c9079bf1 > CLOUDSTACK-6599: > 1. Adding the missing

Re: seeing "Unknown parameters : ctxdetails" for addResourceDetail/removeResourceDetail

I am alright with the ability to turn it off, preferably at run time. On Fri, May 30, 2014 at 8:20 PM, Nitin Mehta wrote: > Hey Daan, > In the thread we have discussed the merits and demerits of having this. > IMHO, I am not convinced why we should have this but very concerned that > the downside

Re: [DOCS] Problem generating 4.4 API docs

Thanks Rohit, I will do all those steps. I know the git branch is correct, but I will do a clean anyway. Removing the maven repositories is a good idea. Thx, Will On Fri, May 30, 2014 at 4:35 PM, Rohit Yadav wrote: > Check if git branch or source code in question is correct, git clean -df >

Review Request 22093: VPC's VR missing public NIC eth1

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/22093/ --- Review request for cloudstack and Marcus Sorensen. Repository: cloudstack-git

Re: [DOCS] Problem generating 4.4 API docs

Check if git branch or source code in question is correct, git clean -df (note: this will remove files not tracked by git), check that the commands.properties has the API you were searching in apidocs, remove ~/.m2 and do mvn clean install, if that does not work check if the API/plugin in question

Re: [DOCS] Problem generating 4.4 API docs

On May 30, 2014, at 4:25 PM, Will Stevens wrote: > By clean install you mean starting from scratch, not 'mvn clean install' > right? I have been doing mvn clean installs… > Will, quickly stated I think that piece of code is a nightmare + folks have complained about our apidocs. Since you ar

Re: [DOCS] Problem generating 4.4 API docs

By clean install you mean starting from scratch, not 'mvn clean install' right? I have been doing mvn clean installs... Will On Fri, May 30, 2014 at 4:22 PM, Rohit Yadav wrote: > Hi Will, > > Based on my last memories of the apidocs tool and maven poms, I think it > used to scan built jar art

Re: [DOCS] Problem generating 4.4 API docs

Hi Will, Based on my last memories of the apidocs tool and maven poms, I think it used to scan built jar artifacts and reference them against something like a properties file (commands.properties?) and internally scans bunch of annotations in available class files to find apis and create apidocs.

[DOCS] Problem generating 4.4 API docs

Hey All, Paul Angus and I have both tested this and this is what we are seeing. When we compile the the 'master' branch, the docs in 'tools/apidoc/target/xmldoc/html', but they appear to be the wrong docs. Yes, we know that the versions that appear in the output is hardcoded in the XSL files, but

Re: License to be signed for contributing to CloudStack

On May 30, 2014, at 1:55 PM, Ritu Sabharwal wrote: > Hi ilya, David, > > Thanks for the information! > > I am working with Brocade Communications Systems and we are implementing a > network plugin for their VDX integration for L2 services. We are targeting > for 4.5 release. > > Some follo

Re: seeing "Unknown parameters : ctxdetails" for addResourceDetail/removeResourceDetail

Hey Daan, In the thread we have discussed the merits and demerits of having this. IMHO, I am not convinced why we should have this but very concerned that the downsides includes performance of apis, unnecessary clutter in the logs etc. Its evident that not every one wants this ability. There should

[ACS44] Cherry pick CLOUDSTACK-6599

Hello Daan, Can you please cherry-pick the following commit from 4.4-forward to 4.4 ? commit 48ea9e0b5e87fee067b711890cd5a5d7c9079bf1 CLOUDSTACK-6599: 1. Adding the missing Template/Volume URLs expiration functionality 2. Improvement - While deleting the volume during expiration use r

Re: [QUESTION] CallContext

Any thoughts on this? Thanks! :) On Sat, May 24, 2014 at 10:39 PM, Mike Tutkowski < mike.tutkow...@solidfire.com> wrote: > Hi, > > I noticed while executing the createStoragePool command that the following > does not work entirely as expected: > > Account csAccount = CallContext.current().getCa

Re: FW: [ACS44] Cherry pick for CLOUDSTACK-6519

Rajesh, it seems this is already in 4.4 it was pulled in May 13th. On Fri, May 30, 2014 at 12:49 PM, Rajesh Battala wrote: > > > From: Rajesh Battala > Sent: Tuesday, May 13, 2014 9:17 PM > To: dev@cloudstack.apache.org > Subject: [ACS44] Cherry pick for CLOUDSTACK-6519 > > Hi Daan, > > Please c

Re: [PROPOSAL] git workflow

Yep, that's what I was referring to in that a particular fix for an old release may not apply to newer versions. That does happen. We used to mark those as "don't need to merge to branch x" in SVN and then you handed it however made sense on the applicable branch(es). On Fri, May 30, 2014 at 11:

RE: License to be signed for contributing to CloudStack

Hi ilya, David, Thanks for the information! I am working with Brocade Communications Systems and we are implementing a network plugin for their VDX integration for L2 services. We are targeting for 4.5 release. Some follow up questions: 1. Since I am not an Apache committer, I need not sign

RE: Unable to deploy guest vm

Hello Tejas, May I know whether you can access the DomR via vCenter and check if the DomR has a link local IP Address ( 169.254.x.x) ? Looks like the DomR didn’t get a link local IP Address, Thank you, Chandan. -Original Message- From: Tejas Gadaria [mailto:refond.g...@gmail.com] Sent

RE: [PROPOSAL] git workflow

What happens if a fix isn't relevant for newer versions, or has to be rewritten for newer versions because the code has changed? Don't the branches diverge and you end up cherry-picking after that? -- Stephen Turner -Original Message- From: Mike Tutkowski [mailto:mike.tutkow...@solidf

Fwd: The distribution of your message dated Fri, 30 May 2014...

I know it says no action is required on my part, but I've never received an automated message like this from this list. Any thoughts on what's going on here? -- Forwarded message -- From: Alcatel-Lucent LISTSERV Server (16.0) Date: Fri, May 30, 2014 at 11:48 AM Subject: The distr

Re: [PROPOSAL] git workflow

I think this flow is something we should seriously consider. I find cherry picking from branch to branch to be error prone in that it's easy for someone to forget to cherry pick to all applicable branches and you don't have any easy way to see the cherry picks are related. When I worked at HP, we

Re: [ACS4.4] cheery-pick request

two pulled On Fri, May 30, 2014 at 12:30 PM, Rajani Karuturi wrote: > Hi Daan, > > Can you cherry-pick the below commits from 4.4-forward to 4.4? > > commit c5a1423d3d02e33c33eb630f6f4df24b731eba69 - CLOUDSTACK-6808 > > commit cc663bb7fc515a4960cd483e8f5697bc141ce95e - CLOUDSTACK-6669 > > > ~Raja

Re: Review Request 22077: CLOUDSTACK-6669 Support volume resize in usage server

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/22077/#review44380 --- Commit c476312a10073240c1436664477c10219141ac6e in cloudstack's bran

Re: [ACS 4.4] Cherry-pick for CLOUDSTACK-6802 and CLOUDSTACK-6810

On Fri, May 30, 2014 at 12:01 PM, Devdeep Singh wrote: > f5ce280da32c4e0837fa39651dc801ba3f906e41 is in -- Daan

[PROPOSAL] git workflow

Hi all, Our current git workflow is confusing with the *forward branches and cherry-picking. Its hard to track on what all releases the commit has gone into unless I do some git log greping. Also, as a contributor, I endup creating patches for each branch as it doesn’t cleanly apply on differ

Re: VPC's VR missing public NIC eth1

It's not valid if you've got code that says does string 'vlan://untagged' equal 'untagged'. On Fri, May 30, 2014 at 10:17 AM, Daan Hoogland wrote: > CLOUDSTACK-5505 looks alright. As for the solution; Isn't 'untagged' a > valid uri in itself? I would expect it would have always the value > with

Re: VPC's VR missing public NIC eth1

I agree, I actually brought this issue up several months ago when we had all of the 'untagged' discussions. I believe I pointed out that vlan:// was now in the db. My impression was that the change was intentional, if you're telling me you didn't intend to do that then we can change it back. At t

Re: VPC's VR missing public NIC eth1

CLOUDSTACK-5505 looks alright. As for the solution; Isn't 'untagged' a valid uri in itself? I would expect it would have always the value without the 'vlan://'. That said a solution is better then no solution, maybe the db upgrade path is best. Andrija, can you try as Marcus suggests, editing the

Re: VPC's VR missing public NIC eth1

If that works, then I think the fix is better to update the database upgrade script to look for this and change the vlan_id. That way new installs and upgrades have consistent data. We could fix it in the code by filtering it through BroadcastDomainType.Vlan.toUri(ipAddr.getVlanTag()), but then lat

Re: VPC's VR missing public NIC eth1

Marcus, I don't think it should be 'vlan://untagged'. If it works as you describe this seems a bug. 'untagged' should be broadcastdomaintype agnostic, shouldn't it? If it should work that way then it is a bug/omission in the db upgrade. On Fri, May 30, 2014 at 5:57 PM, Marcus wrote: > Actually, i

Re: VPC's VR missing public NIC eth1

Actually, if you're in the position to play a bit... New deployments seem to work, and I believe it's because that broadcastUri is stored in the db in the new format: mysql> select id,vlan_id from vlan where network_id = (select id from networks where traffic_type="Public"); ++---

Re: VPC's VR missing public NIC eth1

I thinnk the commit that caused the change was this or related to it. Is there any way you could test a fix? Do you need me to build 4.3 RPMs or can I just provide a patch? What works for you? commit 53d09c6f1843f04c5f1ab76be9419f5584302d1e Date: Mon Aug 5 11:52:40 2013 +0200 uri code per b

Re: VPC's VR missing public NIC eth1

Note the differences in broadcastUri, here is your plug command: { "com.cloud.agent.api.PlugNicCommand": { "nic": { "deviceId": 1, "networkRateMbps": 9, "defaultNic": true, "uuid": "6c782af3-2071-4543-acdc-cb30096e89ff", "

Re: VPC's VR missing public NIC eth1

I believe I've found the issue. In 4.3, some changes were made to BroadcastDomainType, to standardize Broadcast URIs to prepend vlan://. The issue is that your IpAssocVpcCommand doesn't use this new format for the broadcastUri it passes, so it fails to map the plugged device into the broadcastUriT

Re: VPC's VR missing public NIC eth1

yes, correct, eth1 is present, and can be started by static IP configuration... On 30 May 2014 17:25, Marcus wrote: > Let me make sure I understand... the 'Plug' of the nic works fine, as it > seems you do have an eth1 and can manually assign the IP to get it to work? > If that's the case then

Re: VPC's VR missing public NIC eth1

Let me make sure I understand... the 'Plug' of the nic works fine, as it seems you do have an eth1 and can manually assign the IP to get it to work? If that's the case then there's probably not an issue in BridgeVifDriver or the XML. It is definitely in fetching/matching the eth device here vpc_ip

Re: VPC's VR missing public NIC eth1

Nope, started, did check, it is reported now as Debian 5 VM, but still doesn't work... Rebooted VPC (destroyed VR, new one created...) $ virsh dumpxml r-812-VM ... Debian GNU/Linux 5(64-bit) ... hvm :( On 30 May 2014 16:24, Andrija Panic wrote: > I confirm, the highest is

Re: VPC's VR missing public NIC eth1

I confirm, the highest is Debian 5 64bit Per docs http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.3/rnotes.html#upgrade-from-4-2-x-to-4-3 , you should use Debian 7.0 64bit as OS type for system-kvm-4.3 template... (same for xen and vmware templatest) Will change now DB to

Re: quarterly board report, initial draft

On Fri, May 30, 2014 at 03:23:09PM +0200, Hugo Trippaers wrote: > Hey all, > > We are due for our quarterly board reports. I’ve drafted an initial version. > Please review and post any feedback and/or questions. > > DESCRIPTION > Apache CloudStack is open source software designed to deploy and m

Re: quarterly board report, initial draft

On Fri, May 30, 2014 at 03:23:09PM +0200, Hugo Trippaers wrote: > Hey all, > > We are due for our quarterly board reports. I’ve drafted an initial version. > Please review and post any feedback and/or questions. Also, don't forget to add to the wiki here: https://cwiki.apache.org/confluence/dis

Re: Review Request 21773: sysctl improvements regarding nf_conntrack_max, panic and nonlocal_bind

> On May 27, 2014, 4:59 p.m., Chiradeep Vittal wrote: > > I like the idea of taking action on OOM in the VR/systemvm. However there > > is a missing (very important) piece: the VR stays unconfigured. So, it > > should actually stop, not reboot in order for the management server to take > > not

Re: VPC's VR missing public NIC eth1

Andrija, The thing is I don't know who the os matching on KVM works. There must be a way to list supported os types. I also did some queuing on the guest_os_hypervisor table (ACS 4.3) and I don't see Debian 7 for KVM listed. select * from guest_os join guest_os_hypervisor on guest_os.id=guest_os

Re: VPC's VR missing public NIC eth1

Joris, do you have recommendation on how in particular to try ? I'm not sure how to fix that, except playing with editing systemvm-4.3 template to define it as another OS type... ? Thanks again, Andrija On 30 May 2014 15:30, Joris van Lieshout wrote: > I've read back a bit in the code and if

Re: VPC's VR missing public NIC eth1

I've read back a bit in the code and if you look at BridgeVifDriver.java (this is where the log message with the nic profile is generated) you can see that the nic information might be off already once ACS hits the LibvirtVMDef.InterfaceDef plug function. This leads be to believer that the HVM/PV O

Re: VPC's VR missing public NIC eth1

OK, thanks Joris. I will try playing with OS version option, on the systemvm-kvm-4.3 template... Let me know if I can help with anything more. Thanks. Andrija On 30 May 2014 15:19, Joris van Lieshout wrote: > Hi Andrija, > > That does sound familiar and in the start xml of KVM you can see "

quarterly board report, initial draft

Hey all, We are due for our quarterly board reports. I’ve drafted an initial version. Please review and post any feedback and/or questions. DESCRIPTION Apache CloudStack is open source software designed to deploy and manage large networks of virtual machines, as a highly available, highly scalab

Re: VPC's VR missing public NIC eth1

Hi Andrija, That does sound familiar and in the start xml of KVM you can see "hvm". I don't know KVM+ACS well enough to judge if this is the cause but I thing focusing on getting the VR started as PV guest might be worth trying. On the other hand I do see patchviasocket.pl being executed successfu

Re: VPC's VR missing public NIC eth1

Hi Joris, I have turned on DEBUG loging in agent.log on cs1.xxx/net host: So, management logs again: http://pastebin.com/F6BRf7Y9 Agent logs on cs1.xxx: http://pastebin.com/BJauKbaC Not playing smart, but there is some error: [kvm.resource.KVMGuestOsMapper] (agentRequest-Handler-3:) Can't find t

Re: VPC's VR missing public NIC eth1

Hi Andrija, Bold formatting does not come trough on the dev list. :) But u might need a bit more info. At a certain point I see this line 2014-05-30 13:56:23,935 DEBUG [c.c.a.t.Request] (Job-Executor-77:ctx-ec3d358e ctx-f35b12af) Seq 1-609104082: Sending { Cmd , MgmtId: 161344838950, via: 1(cs1

Re: [ACS45][ACS50][PROPOSAL] move forward feature freeze

On May 29, 2014, at 9:34 PM, Mike Tutkowski wrote: > In an effort to help keep our releases from getting out of hand, I think we > should consider moving the Feature Proposal deadline up, as well. > > My main concern is that many people have three CloudStack-related "threads" > executing right

Re: VPC's VR missing public NIC eth1

Hi Joris, here is the management log: http://pastebin.com/zxnKxFhk Interesting parts (to me): in bold 2014-05-30 13:56:21,899 DEBUG [o.a.c.s.m.AncientDataMotionStrategy] (Job-Executor-77:ctx-ec3d358e ctx-f35b12af) copyAsync inspecting src type TEMPLATE copyAsync inspecting dest type VOLUME 2014-

Re: VPC's VR missing public NIC eth1

Hi Andrija, Just the start of the VR should be sufficient. Kind regards, Joris van Lieshout Schuberg Philis Boeingavenue 271 1119 PD Schiphol-Rijk schubergphilis.com +31 20-7506672 +31 6-51428188 On 30/05/14 13:48, "Andrija Panic" wrote: >Hi Joris, > >just to be sure - you want me to cap

Re: VPC's VR missing public NIC eth1

Hi Joris, just to be sure - you want me to capture the log from the moment I reboot router - or you want me to stop it, then start capturing log, and start it (and continue capture untill ethnull errors inside VR) ? Thanks, On 30 May 2014 13:39, Joris van Lieshout wrote: > Hi Andrija, > > Tha

Unable to deploy guest vm

SSVM & Console proxy working fine. while trying to create vm from ISO on new setup it throws below exception. 2014-05-30 16:42:20,358 ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-62:ctx-97ac79ab 10.129.137.199) Unable to execute ping command on DomR (null), domR may not be ready yet. failure due

Re: VPC's VR missing public NIC eth1

Hi Andrija, Thanks for the answers. In deed your situation is different so PV/HVM is not the issue. When reading back the log output you have provided I noted that the VR messages log indicates that it's waiting for ethnull to be up. This raises the question where null was introduced instead of 1

FW: [ACS44] Cherry pick for CLOUDSTACK-6519

From: Rajesh Battala Sent: Tuesday, May 13, 2014 9:17 PM To: dev@cloudstack.apache.org Subject: [ACS44] Cherry pick for CLOUDSTACK-6519 Hi Daan, Please cherry-pick to 4.4 260e06d64c07c6e5f3c133d8bdc2779fad62c672 https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=260e06d Thanks Rajesh B

[ACS4.4] cheery-pick request

Hi Daan, Can you cherry-pick the below commits from 4.4-forward to 4.4? commit c5a1423d3d02e33c33eb630f6f4df24b731eba69 - CLOUDSTACK-6808 commit cc663bb7fc515a4960cd483e8f5697bc141ce95e - CLOUDSTACK-6669 ~Rajani

[ACS 4.4] Cherry-pick for CLOUDSTACK-6802 and CLOUDSTACK-6810

Hi Daan, Could you please cherry-pick commit f5ce280da32c4e0837fa39651dc801ba3f906e41 from 4.4-forward branch to 4.4 branch. commit f5ce280da32c4e0837fa39651dc801ba3f906e41 Author: Devdeep Singh Date: Tue May 20 11:40:51 2014 +0530 CLOUDSTACK-6810: Fix storage migration of a vm with volu

Re: Review Request 22075: Database Information missing in Alter table statements in a commit to schema-430to440.sql

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/22075/#review44352 --- Ship it! dbd05e3ff5015a867652d805b08965851608e577 - Kishan Kavala

Re: Review Request 22077: CLOUDSTACK-6669 Support volume resize in usage server

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/22077/#review44351 --- Ship it! Ship It! - Kishan Kavala On May 30, 2014, 12:09 p.m., R

Re: Review Request 21773: sysctl improvements regarding nf_conntrack_max, panic and nonlocal_bind

> On May 27, 2014, 4:59 p.m., Chiradeep Vittal wrote: > > I like the idea of taking action on OOM in the VR/systemvm. However there > > is a missing (very important) piece: the VR stays unconfigured. So, it > > should actually stop, not reboot in order for the management server to take > > not

Re: Review Request 22077: CLOUDSTACK-6669 Support volume resize in usage server

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/22077/#review44349 --- Commit bdde5335f9988e460a667da97ebe0cde2e74e7a1 in cloudstack's bran

Re: Review Request 22077: CLOUDSTACK-6669 Support volume resize in usage server

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/22077/#review44348 --- Commit cc663bb7fc515a4960cd483e8f5697bc141ce95e in cloudstack's bran

RE: [PROPOSAL] - Change Primary IP Address

(slightly biased) +1 I see very few 'purist cloud' implementations. At best they are a mix. And the only way to enable organisations to make the transition to 'cloud' using CloudStack is to enable them to migrate their workloads; Traditional without CloudStack -> traditional with CloudStack ->

Re: VPC's VR missing public NIC eth1

Hi Deen, no, in DB there is field "vlan_id" with value "untagged" - that "vlan://untagged" is shown from ACS gui, and is used in API call (or better said commands that are seen in management server logs). Best, Andrija On 30 May 2014 10:37, Daan Hoogland wrote: > Andrija, > > Do not just assig

Re: VPC's VR missing public NIC eth1

Andrija, Do not just assign a second net vlan://500 You have one like that and you don't want conflicting nets using the same vlan. I am wondering why 'untagged' comes out as 'vlan://untagged'. I think that is the bug. Did you find the string 'vlan://untagged' in your db? On Fri, May 30, 2014 at

Re: [ACS4.4] [Issue] Unable to create a autoscalevmprofile

Long accountId = _accountService.finalyzeAccountId(accountName, domainId, projectId, true); _accountService didn't get initialized/injected!?! The spring stuff should have taken care of that. I think the problem is in the test initialization not in the base code. On Fri, May 30, 2014 at 7

Re: VPC's VR missing public NIC eth1

Hi Joris, thank you for taking time to address this issue :) So...: - I'm on KVM (stock CentOS 6.2 patched by Inktank for CEPH support), OS is Centos 6.5, libvirt 1.2.3 compiled. - ACS 4.3 having problems, ACS 4.2.1 was fine - not XS, so I guess no answers for this part :) - guest_os_id is 184 =

Re: Review Request 21946: CLOUDSTACK-6392 system template always create with name "master" instead of specific branch

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/21946/#review44343 --- Commit b4021284b853362f414e68e52deb5ba92734a7e2 in cloudstack's bran