Re: [VOTE] Apache CloudStack 4.3.0 (first round)

[Hugo Trippaers]

Thanks Animesh,

Great to see the first RC for 4.3.

I’ve been running some findbugs analysis on master and found several issues 
that also seem to be present in the 4.3 branch. I’ve made two commit on master 
that fixed some issues that i spotted (c2da2803476d55e814ec0d849482bd07c4f9f8f1 
and d19157fbb169eec029d1efee9ddd06e6b6aad9a4). Both fix an issue where an 
object is compared by using == instead of equals. I’m doubting if this is worth 
to -1 the current RC as i can’t oversee the impact of these bugs and looking 
for opinions.

Cheers,

Hugo






On 23 jan. 2014, at 06:54, Animesh Chaturvedi  
wrote:

> 
> 
> 
> Hi All,
> 
> 
> 
> I've created a 4.3.0 release, with the following artifacts up for a
> 
> vote:
> 
> 
> 
> Git Branch and Commit SH:
> 
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
> Commit: 43d485c92d5919085cacb1cd0c7e78503ab9788a
> 
> 
> 
> List of changes:
> 
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.3
> 
> 
> 
> Source release (checksums and signatures are available at the same
> 
> location):
> 
> https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
> 
> 
> 
> PGP release keys (signed using 94BE0D7C):
> 
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> 
> 
> 
> Testing instructions are here:
> 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
> 
> 
> 
> Vote will be open for 72 hours.
> 
> 
> 
> For sanity in tallying the vote, can PMC members please be sure to indicate 
> "(binding)" with their vote?
> 
> 
> 
> [ ] +1  approve
> 
> [ ] +0  no opinion
> 
> [ ] -1  disapprove (and reason why)
> 
> 
> 

SSH to VM via default network failing

[Ashutosh Kelkar]

Hi,

I have a VM deployed in two isolated networks. I am doing following things
with each network.

1) Acquire public IP
2) Open firewall for this IP
3) Create port forwarding rule using this IP for the above mentioned VM

Now when I try to SSH to VM using these 2 IPs, SSH via IP belonging to
non-default network succeeds but through the IP belonging to default
network fails.

Can someone throw some light on why would this be happening? Shouldn't it
work for both the IPs?

-- 
Regards,
Ashutosh

Re: SSH to VM via default network failing

[Jayapal Reddy Uradi]

Hi Ashutosh,

1. Check the router public interface is configured with the acquired public ip
2. Check the rules specific to FW/PF are configured correctly on VR.
3. If 1,2 are correct try to debug the traffic by capturing the packets on 
router and vm
4. If the packets reached to router and then VM, there could be issue in return 
traffic path.
5. If the packets reached router but not VM, issue with the router iptables 
rules


Thanks,
Jayapal

On 23-Jan-2014, at 2:38 PM, Ashutosh Kelkar  wrote:

> Hi,
> 
> I have a VM deployed in two isolated networks. I am doing following things
> with each network.
> 
> 1) Acquire public IP
> 2) Open firewall for this IP
> 3) Create port forwarding rule using this IP for the above mentioned VM
> 
> Now when I try to SSH to VM using these 2 IPs, SSH via IP belonging to
> non-default network succeeds but through the IP belonging to default
> network fails.
> 
> Can someone throw some light on why would this be happening? Shouldn't it
> work for both the IPs?
> 
> -- 
> Regards,
> Ashutosh

Re: SSH to VM via default network failing

[Ashutosh Kelkar]

Thanks Jayapal, I will check and revert.


On Thu, Jan 23, 2014 at 2:55 PM, Jayapal Reddy Uradi <
jayapalreddy.ur...@citrix.com> wrote:

> Hi Ashutosh,
>
> 1. Check the router public interface is configured with the acquired
> public ip
> 2. Check the rules specific to FW/PF are configured correctly on VR.
> 3. If 1,2 are correct try to debug the traffic by capturing the packets on
> router and vm
> 4. If the packets reached to router and then VM, there could be issue in
> return traffic path.
> 5. If the packets reached router but not VM, issue with the router
> iptables rules
>
>
> Thanks,
> Jayapal
>
> On 23-Jan-2014, at 2:38 PM, Ashutosh Kelkar  wrote:
>
> > Hi,
> >
> > I have a VM deployed in two isolated networks. I am doing following
> things
> > with each network.
> >
> > 1) Acquire public IP
> > 2) Open firewall for this IP
> > 3) Create port forwarding rule using this IP for the above mentioned VM
> >
> > Now when I try to SSH to VM using these 2 IPs, SSH via IP belonging to
> > non-default network succeeds but through the IP belonging to default
> > network fails.
> >
> > Can someone throw some light on why would this be happening? Shouldn't it
> > work for both the IPs?
> >
> > --
> > Regards,
> > Ashutosh
>
>


-- 
Regards,
Ashutosh

Create GRE tunnel failed in 4.2 with XenServer.

[Nguyen Anh Tu]

Guys,

Florin raised a problem in creating GRE tunnel with ACS 4.2 release and
XenServer 6.2. I found the problem come from enableXenserverNetwork method.
CloudStack made a tricky to create network when plugging a VIF to dom0 and
then unplugging immediately. With XCP version I done in GSOC, I bypassed
that step so that no problem.

Didn't know why we need that tricky and how to solve it. I'm working on it.
Any help or explaination?

Thanks,

--Tuna

Sent from my GT-N7000

Re: [VOTE] Apache CloudStack 4.3.0 (first round)

[Abhinandan Prateek]

Long values till at least 128 are cached, the ref being same, the ==
operator is guaranteed to work for values from -127 to 128.
It the value can go beyond that range then this is a potential mine.

-abhi

On 23/01/14 1:51 pm, "Hugo Trippaers"  wrote:

>Thanks Animesh,
>
>Great to see the first RC for 4.3.
>
>I¹ve been running some findbugs analysis on master and found several
>issues that also seem to be present in the 4.3 branch. I¹ve made two
>commit on master that fixed some issues that i spotted
>(c2da2803476d55e814ec0d849482bd07c4f9f8f1 and
>d19157fbb169eec029d1efee9ddd06e6b6aad9a4). Both fix an issue where an
>object is compared by using == instead of equals. I¹m doubting if this is
>worth to -1 the current RC as i can¹t oversee the impact of these bugs
>and looking for opinions.
>
>Cheers,
>
>Hugo
>
>
>
>
>
>
>On 23 jan. 2014, at 06:54, Animesh Chaturvedi
> wrote:
>
>> 
>> 
>> 
>> Hi All,
>> 
>> 
>> 
>> I've created a 4.3.0 release, with the following artifacts up for a
>> 
>> vote:
>> 
>> 
>> 
>> Git Branch and Commit SH:
>> 
>> 
>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=ref
>>s/heads/4.3
>> Commit: 43d485c92d5919085cacb1cd0c7e78503ab9788a
>> 
>> 
>> 
>> List of changes:
>> 
>> 
>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=C
>>HANGES;hb=4.3
>> 
>> 
>> 
>> Source release (checksums and signatures are available at the same
>> 
>> location):
>> 
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
>> 
>> 
>> 
>> PGP release keys (signed using 94BE0D7C):
>> 
>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>> 
>> 
>> 
>> Testing instructions are here:
>> 
>> 
>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+proce
>>dure
>> 
>> 
>> 
>> Vote will be open for 72 hours.
>> 
>> 
>> 
>> For sanity in tallying the vote, can PMC members please be sure to
>>indicate "(binding)" with their vote?
>> 
>> 
>> 
>> [ ] +1  approve
>> 
>> [ ] +0  no opinion
>> 
>> [ ] -1  disapprove (and reason why)
>> 
>> 
>> 
>

Review Request 17233: Fix for Issue CLOUDSTACK-5875

[Santhosh Edukulla]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17233/
---

Review request for cloudstack and Koushik Das.


Bugs: CLOUDSTACK-5875
https://issues.apache.org/jira/browse/CLOUDSTACK-5875


Repository: cloudstack-git


Description
---

Fixed the issue CLOUDSTACK-5875
The crash issue happens because of null value for CallContext.current() under 
discoverHostsFull, when called from thread for SystemVMHandler. Currently, 
there is no call context set for this thread. Currently, as part of 
MockAgentManagerImpl.java, SystemVMHandler implements Runnable, but when it 
calls discoverHosts, it does not have any call context set and it is crashing. 
Because of which agent was not coming up and template sync and resource 
discovery failed. Added a register and unregister of callcontext of system user 
for this thread.
2. There was a new column added by name "state" under "vm_templates" table. The 
value of this column for "Active" was checked for listing the templates if 
there was no removed attribute set for list templates api. This column was not 
present in 4.2. Added a column value "Active" for simulator schema. The value 
of this column was not Active and so listing failed.
Testing:
1. Built the CS using the changes. Tested the column value, post deploydb and 
it was now set to "Active". Deployed a DC and list template works. 
2. Deploy DC worked fine with simulator . Created an instance using the 
template and it worked to start. Agent for systemvm was coming up.
Note: 
1. For listing templates, a hypervisor in the zone need to be present because 
listtemplates api is looking for it. Use the list templates post the deployDC 
and it works.
2. We need to set router.version.check to false under global properties of CS 
post run using simulator. Otherwise you may see errors related to router 
upgrade etc. This i believe is a known issue and nothing to do with simulator.
3. Post the changes, tested only with simulator.
3. Also, please change the component field. AS such it is not related to Marvin.


Diffs
-

  
plugins/hypervisors/simulator/src/com/cloud/agent/manager/MockAgentManagerImpl.java
 4071aeb 
  setup/db/templates.simulator.sql 5f9b67d 

Diff: https://reviews.apache.org/r/17233/diff/


Testing
---

Testing:
1. Built the CS 4.3-forward using the changes. Tested the column value change, 
post deploydb and it was now set to "Active". Deployed a DC and list template 
works. 
2. Deploy DC worked fine with simulator . Created an instance using the 
template and it worked to start. Agent for systemvm was coming up.
Note: 
1. For listing templates, a hypervisor in the zone need to be present because 
listtemplates api is looking for it. Use the list templates post the deployDC 
and it works.
2. We need to set router.version.check to false under global properties of CS 
post run using simulator. Otherwise you may see errors related to router 
upgrade etc. This i believe is a known issue and nothing to do with simulator.
3. Post the changes, tested only with simulator.


Thanks,

Santhosh Edukulla

RE: Location of the 4.3 System VM Templates

[Radhika Puthiyetath]

Thanks.

-Original Message-
From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
Sent: Thursday, January 23, 2014 12:25 PM
To: dev
Subject: Re: Location of the 4.3 System VM Templates

The best location for the system vm images is 
http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/. There we 
have the systemvm images that belong to the latest build agains the 4.3 tree. 
Look for the 'Last Successful Artifacts' on that page.

Cheers,

Hugo


On 23 jan. 2014, at 07:30, Abhisek Basu  wrote:

> I was able to get them from path like: 
> http://download.cloud.com/templates/4.3/systemvm64template-2013-12-23-hyperv.vhd.bz2
> 
> Regards,
> 
> Abhisek
> 
> -Original Message- From: Radhika Puthiyetath
> Sent: Thursday, January 23, 2014 11:15 AM
> To: dev@cloudstack.apache.org
> Subject: Location of the 4.3 System VM Templates
> 
> Hi,
> 
> Could someone please help me with the location of the System VM Templates for 
> 4.3 release ?
> 
> I am unable to access http://download.cloud.com. I assume that they are 
> posted to templates directory.
> 
> Thanks
> -Radhika
> 

Re: Review Request 17231: review request for master of defect CLOUDSTACJ-2031

[Jayapal Reddy]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17231/#review32603
---



setup/db/db/schema-421to430.sql


Please move this changes to schema-43to44.sql


- Jayapal Reddy


On Jan. 23, 2014, 7:18 a.m., Damodar Reddy Talakanti wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/17231/
> ---
> 
> (Updated Jan. 23, 2014, 7:18 a.m.)
> 
> 
> Review request for cloudstack and Jayapal Reddy.
> 
> 
> Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-2031
> 
> https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/CLOUDSTACK-2031
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> This is for master branch of the review request 
> https://reviews.apache.org/r/16780/
> 
> 
> Diffs
> -
> 
>   api/src/org/apache/cloudstack/api/command/user/vm/AddIpToVmNicCmd.java 
> c0e8d3e 
>   engine/schema/src/com/cloud/vm/dao/NicSecondaryIpDao.java 9fbfa27 
>   engine/schema/src/com/cloud/vm/dao/NicSecondaryIpDaoImpl.java 2f3cc29 
>   server/src/com/cloud/configuration/Config.java 9117bc4 
>   server/src/com/cloud/network/NetworkServiceImpl.java 056190f 
>   setup/db/db/schema-421to430.sql ccff7c1 
> 
> Diff: https://reviews.apache.org/r/17231/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Damodar Reddy Talakanti
> 
>

[ANNOUNCE] Switch to Java 7 in master branch on Monday Jan 27th 2014

[Wido den Hollander]

Hi,

We had multiple threads discussing the switch to Java 7 which all ended 
in +1 everywhere.


The most recent [0] one is from the beginning of this month and since 
nobody actually took the step I'll do it.


On 27-01-2014 11:00:00 CET / GMT +1 I'll push a commit where on the 
pom.xml cs.jdk.version will be set to 1.7.


I'll also update the Debian and RPM packaging to only depend on Java 7 
packages and no longer on Java 6.


Without any objections I'll continue with this on the date specified above.

Wido

[0]: 
http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201401.mbox/%3CCEF079AF.5E3AB%25kelven.yang%40citrix.com%3E

RE: Location of the 4.3 System VM Templates

[Radhika Puthiyetath]

Are 32-bit templates not supported for 4.3 ?

-Original Message-
From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
Sent: Thursday, January 23, 2014 12:25 PM
To: dev
Subject: Re: Location of the 4.3 System VM Templates

The best location for the system vm images is 
http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/. There we 
have the systemvm images that belong to the latest build agains the 4.3 tree. 
Look for the 'Last Successful Artifacts' on that page.

Cheers,

Hugo


On 23 jan. 2014, at 07:30, Abhisek Basu  wrote:

> I was able to get them from path like: 
> http://download.cloud.com/templates/4.3/systemvm64template-2013-12-23-hyperv.vhd.bz2
> 
> Regards,
> 
> Abhisek
> 
> -Original Message- From: Radhika Puthiyetath
> Sent: Thursday, January 23, 2014 11:15 AM
> To: dev@cloudstack.apache.org
> Subject: Location of the 4.3 System VM Templates
> 
> Hi,
> 
> Could someone please help me with the location of the System VM Templates for 
> 4.3 release ?
> 
> I am unable to access http://download.cloud.com. I assume that they are 
> posted to templates directory.
> 
> Thanks
> -Radhika
> 

Re: Location of the 4.3 System VM Templates

[Abhinandan Prateek]

KVM = 
http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-maste
r-kvm.qcow2.bz2  (85a1bed07bf43cbf022451cb2ecae4ff)
Xenserver = 
http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-maste
r-xen.vhd.bz2 (3e29b40377272803eebccfe40efea199)
VMWare = 
http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-maste
r-vmware.ova (ef593a061f3b7594ab0bfd9b0ed0a0d4)
HyperV = 
http://download.cloud.com/templates/4.3/systemvm64template-2013-12-23-hyper
v.vhd.bz2 (96725cc10a42b7203dffd69a0e804708)


On 23/01/14 11:15 am, "Radhika Puthiyetath"
 wrote:

>Hi,
>
>Could someone please help me with the location of the System VM Templates
>for 4.3 release ?
>
>I am unable to access http://download.cloud.com. I assume that they are
>posted to templates directory.
>
>Thanks
>-Radhika
>

Re: Review Request 17233: Fix for Issue CLOUDSTACK-5875

[ASF Subversion and Git Services]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17233/#review32604
---


Commit d31fa09c7e5bb04fcc4594c0352d9b91171e9d1a in branch 
refs/heads/4.3-forward from Santhosh Edukulla
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d31fa09 ]

Added Fix for CLOUDSTACK-5875

Added fix for exception and listing. Mentioned details under bug.
Post the fix, simulator works fine.

Signed-off-by: Santhosh Edukulla 
Signed-off-by: Koushik Das 


- ASF Subversion and Git Services


On Jan. 23, 2014, 10:27 a.m., Santhosh Edukulla wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/17233/
> ---
> 
> (Updated Jan. 23, 2014, 10:27 a.m.)
> 
> 
> Review request for cloudstack and Koushik Das.
> 
> 
> Bugs: CLOUDSTACK-5875
> https://issues.apache.org/jira/browse/CLOUDSTACK-5875
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fixed the issue CLOUDSTACK-5875
> The crash issue happens because of null value for CallContext.current() under 
> discoverHostsFull, when called from thread for SystemVMHandler. Currently, 
> there is no call context set for this thread. Currently, as part of 
> MockAgentManagerImpl.java, SystemVMHandler implements Runnable, but when it 
> calls discoverHosts, it does not have any call context set and it is 
> crashing. Because of which agent was not coming up and template sync and 
> resource discovery failed. Added a register and unregister of callcontext of 
> system user for this thread.
> 2. There was a new column added by name "state" under "vm_templates" table. 
> The value of this column for "Active" was checked for listing the templates 
> if there was no removed attribute set for list templates api. This column was 
> not present in 4.2. Added a column value "Active" for simulator schema. The 
> value of this column was not Active and so listing failed.
> Testing:
> 1. Built the CS using the changes. Tested the column value, post deploydb and 
> it was now set to "Active". Deployed a DC and list template works. 
> 2. Deploy DC worked fine with simulator . Created an instance using the 
> template and it worked to start. Agent for systemvm was coming up.
> Note: 
> 1. For listing templates, a hypervisor in the zone need to be present because 
> listtemplates api is looking for it. Use the list templates post the deployDC 
> and it works.
> 2. We need to set router.version.check to false under global properties of CS 
> post run using simulator. Otherwise you may see errors related to router 
> upgrade etc. This i believe is a known issue and nothing to do with simulator.
> 3. Post the changes, tested only with simulator.
> 3. Also, please change the component field. AS such it is not related to 
> Marvin.
> 
> 
> Diffs
> -
> 
>   
> plugins/hypervisors/simulator/src/com/cloud/agent/manager/MockAgentManagerImpl.java
>  4071aeb 
>   setup/db/templates.simulator.sql 5f9b67d 
> 
> Diff: https://reviews.apache.org/r/17233/diff/
> 
> 
> Testing
> ---
> 
> Testing:
> 1. Built the CS 4.3-forward using the changes. Tested the column value 
> change, post deploydb and it was now set to "Active". Deployed a DC and list 
> template works. 
> 2. Deploy DC worked fine with simulator . Created an instance using the 
> template and it worked to start. Agent for systemvm was coming up.
> Note: 
> 1. For listing templates, a hypervisor in the zone need to be present because 
> listtemplates api is looking for it. Use the list templates post the deployDC 
> and it works.
> 2. We need to set router.version.check to false under global properties of CS 
> post run using simulator. Otherwise you may see errors related to router 
> upgrade etc. This i believe is a known issue and nothing to do with simulator.
> 3. Post the changes, tested only with simulator.
> 
> 
> Thanks,
> 
> Santhosh Edukulla
> 
>

RE: Create GRE tunnel failed in 4.2 with XenServer.

[Florin Dumitrascu]

Hi,

Just want to add a few of my observations to what Tuna said.


a.   I managed to have GRE isolation working with CloudStack 4.1.1 and a 
quick patch to bypass "enableXenserverNetwork" method.



b.  I tried GRE isolation with CloudStack 4.2.1 with the same quick patch 
for bypassing "enableXenserverNetwork".

Once that method was bypassed, guest VMs came up, but the tunnel was not 
created. It seems to me that OvsElement methods (implement, prepare) are not 
invoked.

Did something change in 4.2 to affect this ? I am setting 
"sdn.ovs.controller=true" in global settings and select GRE isolation method in 
the guest physical network.


Thank you,
Florin



From: ng.t...@gmail.com [mailto:ng.t...@gmail.com] On Behalf Of Nguyen Anh Tu
Sent: Thursday, January 23, 2014 10:15 AM
To: dev@cloudstack.apache.org; Sebastien Goasguen; Chiradeep Vittal; Florin 
Dumitrascu
Subject: Create GRE tunnel failed in 4.2 with XenServer.


Guys,

Florin raised a problem in creating GRE tunnel with ACS 4.2 release and 
XenServer 6.2. I found the problem come from enableXenserverNetwork method. 
CloudStack made a tricky to create network when plugging a VIF to dom0 and then 
unplugging immediately. With XCP version I done in GSOC, I bypassed that step 
so that no problem.

Didn't know why we need that tricky and how to solve it. I'm working on it. Any 
help or explaination?

Thanks,

--Tuna

Sent from my GT-N7000

IMPORTANT NOTE: The information in this e-mail (and any attachments) is 
confidential. The contents may not be disclosed or used by anyone other than 
the addressee. If you are not the intended recipient, please notify the sender 
immediately or telephone: +353 (0)1 6204700. We cannot accept any 
responsibility for the accuracy or completeness of this message as it has been 
transmitted over a public network. If you suspect that the message may have 
been intercepted or amended, please call the sender.

RE: [ACS 4.3] RC update

[Santhosh Edukulla]

Simulator issue is fixed. It now works, please check.

Santhosh

From: sebgoa [run...@gmail.com]
Sent: Wednesday, January 15, 2014 5:50 AM
To: Santhosh Edukulla
Cc: dev@cloudstack.apache.org; gir...@clogeny.com; Prasanna Santhanam
Subject: Re: [ACS 4.3] RC update

On Jan 14, 2014, at 3:53 PM, sebgoa  wrote:

>
> On Jan 14, 2014, at 3:48 PM, Santhosh Edukulla  
> wrote:
>
>> Sebastian,
>>
>> 1. As such the  profile issue mentioned in the bug is fixed( submitted a 
>> patch, not yet applied ), instead of using the same bug for other issue 
>> related to simulator, may be we can log a separate bug.
>> The reason being the issues reported are different and this new issue 
>> reported is inside the simulator code if any but nothing to do with marvin 
>> though? Let me know.
>>
>
> not note fixed yet, I will post additional comments/logs in your review

Ok I am happy with your comments in the review, I went ahead and committed the 
patch to master, 4.3 and 4.2
I closed
https://issues.apache.org/jira/browse/CLOUDSTACK-5864

and opened:
 https://issues.apache.org/jira/browse/CLOUDSTACK-5875 as a non blocker, even 
though I feel we should fix it for 4.3 because it prevents truly automated 
integration tests to run on jenkins.
So if you could grab 5875 in JIRA (assign it to yourself) and fix the simulator 
that would be great.

thanks,

-Sebastien

>
>>
>> Regards,
>> Santhosh
>> 
>> From: sebgoa [run...@gmail.com]
>> Sent: Tuesday, January 14, 2014 9:10 AM
>> To: Santhosh Edukulla
>> Cc: dev@cloudstack.apache.org; gir...@clogeny.com; Prasanna Santhanam
>> Subject: Re: [ACS 4.3] RC update
>>
>> On Jan 14, 2014, at 2:28 PM, Santhosh Edukulla 
>>  wrote:
>>
>>> Hi Sebastian,
>>>
>>> Note1 : The nose command you are running is right ( Just use nosetests-2.7 
>>> ),  I just ran the simulator using the below mentioned commands followed by 
>>> deployDataCenter, on 4.2 and 4.3 separately, there were  no errors  
>>> reported on 4.2. I could see that templates were available, displayed and 
>>> deployDataCenter worked fine on 4.2 but not on 4.3 and its throwing the 
>>> error you mentioned. We will look in to it.
>>>
>>
>> ok thanks, this is important. If we want to remove the maven profile then we 
>> need to make sure the nosetests way of configuring the DC works.
>>
>>> Note2: Regarding the templates not available in UI, we need to register the 
>>> template to work with simulator post deploy for testing ( atleast with 
>>> 4.2.1 or later ), this behavior i believe was due to some issue in 
>>> simulator code in later code and i was told to register and proceed with 
>>> tests then.
>>>
>>> Note3: Profile issue, i fixed and submitted a review.
>>>
>>
>> I tested it on 4.3, it seems to work but never returns. Is that the newly 
>> expected behavior ?
>>
>>> Note4: Registering a template issue manually and below for addCluster 
>>> Command, we will look in to it. This i believe is nothing to do with marvin 
>>> though.
>>>
>>
>> your note4 and note3 seem to be talking about the same thing. My concern is 
>> that this was working in 4.2, so if it's broken in 4.2.1 this is brand new 
>> error.
>> I understand that few people use the simulator, but we should fix it in 4.3 
>> (and apply patch to 4.2 branch as well )
>>
>>
>>
>>> Let me know.
>>>
>>> Thanks!
>>> Santhosh
>>> 
>>> From: sebgoa [run...@gmail.com]
>>> Sent: Tuesday, January 14, 2014 5:22 AM
>>> To: Santhosh Edukulla
>>> Cc: dev@cloudstack.apache.org; gir...@clogeny.com; Prasanna Santhanam
>>> Subject: Re: [ACS 4.3] RC update
>>>
>>> On Jan 13, 2014, at 6:45 PM, Santhosh Edukulla 
>>>  wrote:
>>>
 Hi Sebastian,

 1. I was able to get the simulator up and running following the below 
 instructions @link:

 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Simulator+integration

 mvn -Pdeveloper -Dsimulator clean install
 mvn -Pdeveloper -pl developer -Ddeploydb
 mvn -Pdeveloper -pl developer -Ddeploydb-simulator
 mvn -pl client jetty:run -Dsimulator

 Thereafter deploying a datacenter worked either by "python 
 deployDataCenter.py -i " or "python deployAndRun.py -c 
 "

>>>
>>> Santhosh, I tried this and it works.
>>> I am pretty sure that we did not need to use the -Dsimulator before ( I 
>>> documented it without), but we can skip this.
>>>
>>> However when accessing the UI and trying to run an instance, there are no 
>>> templates available.
>>> The systemVMs are running.
>>>
>>> Also, I used to be able to use nosetests as well and configure the DC with:
>>> nosetests --with-marvin --marvin-config=setup/dev/basic.cfg
>>>
>>> it gave me this:
>>>
>>> $ nosetests --with-marvin --marvin-config=setup/dev/basic.cfg
>>>
>>> Exception Occurred Under __deployDC : Execute cmd: addcluster failed, due 
>>> to: errorCode: 431, errorText:Could not find corresponding resource manager 
>>> 

Re: Create GRE tunnel failed in 4.2 with XenServer.

[Murali Reddy]

Please see the thread

https://www.mail-archive.com/dev@cloudstack.apache.org/msg17396.html



On 23/01/14 5:10 PM, "Florin Dumitrascu"
 wrote:

>Hi,
>
>Just want to add a few of my observations to what Tuna said.
>
>
>a.   I managed to have GRE isolation working with CloudStack 4.1.1
>and a quick patch to bypass "enableXenserverNetwork" method.
>
>
>
>b.  I tried GRE isolation with CloudStack 4.2.1 with the same quick
>patch for bypassing "enableXenserverNetwork".
>
>Once that method was bypassed, guest VMs came up, but the tunnel was not
>created. It seems to me that OvsElement methods (implement, prepare) are
>not invoked.
>
>Did something change in 4.2 to affect this ? I am setting
>"sdn.ovs.controller=true" in global settings and select GRE isolation
>method in the guest physical network.
>
>
>Thank you,
>Florin
>
>
>
>From: ng.t...@gmail.com [mailto:ng.t...@gmail.com] On Behalf Of Nguyen
>Anh Tu
>Sent: Thursday, January 23, 2014 10:15 AM
>To: dev@cloudstack.apache.org; Sebastien Goasguen; Chiradeep Vittal;
>Florin Dumitrascu
>Subject: Create GRE tunnel failed in 4.2 with XenServer.
>
>
>Guys,
>
>Florin raised a problem in creating GRE tunnel with ACS 4.2 release and
>XenServer 6.2. I found the problem come from enableXenserverNetwork
>method. CloudStack made a tricky to create network when plugging a VIF to
>dom0 and then unplugging immediately. With XCP version I done in GSOC, I
>bypassed that step so that no problem.
>
>Didn't know why we need that tricky and how to solve it. I'm working on
>it. Any help or explaination?
>
>Thanks,
>
>--Tuna
>
>Sent from my GT-N7000
>
>IMPORTANT NOTE: The information in this e-mail (and any attachments) is
>confidential. The contents may not be disclosed or used by anyone other
>than the addressee. If you are not the intended recipient, please notify
>the sender immediately or telephone: +353 (0)1 6204700. We cannot accept
>any responsibility for the accuracy or completeness of this message as it
>has been transmitted over a public network. If you suspect that the
>message may have been intercepted or amended, please call the sender.
>

Re: Review Request 17233: Fix for Issue CLOUDSTACK-5875

[ASF Subversion and Git Services]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17233/#review32605
---


Commit f999a01837e60f0c51ef0eb4ad19c29e43ca3037 in branch refs/heads/master 
from Santhosh Edukulla
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f999a01 ]

Added Fix for CLOUDSTACK-5875

Added fix for exception and listing. Mentioned details under bug.
Post the fix, simulator works fine.

Signed-off-by: Santhosh Edukulla 
Signed-off-by: Koushik Das 


- ASF Subversion and Git Services


On Jan. 23, 2014, 10:27 a.m., Santhosh Edukulla wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/17233/
> ---
> 
> (Updated Jan. 23, 2014, 10:27 a.m.)
> 
> 
> Review request for cloudstack and Koushik Das.
> 
> 
> Bugs: CLOUDSTACK-5875
> https://issues.apache.org/jira/browse/CLOUDSTACK-5875
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fixed the issue CLOUDSTACK-5875
> The crash issue happens because of null value for CallContext.current() under 
> discoverHostsFull, when called from thread for SystemVMHandler. Currently, 
> there is no call context set for this thread. Currently, as part of 
> MockAgentManagerImpl.java, SystemVMHandler implements Runnable, but when it 
> calls discoverHosts, it does not have any call context set and it is 
> crashing. Because of which agent was not coming up and template sync and 
> resource discovery failed. Added a register and unregister of callcontext of 
> system user for this thread.
> 2. There was a new column added by name "state" under "vm_templates" table. 
> The value of this column for "Active" was checked for listing the templates 
> if there was no removed attribute set for list templates api. This column was 
> not present in 4.2. Added a column value "Active" for simulator schema. The 
> value of this column was not Active and so listing failed.
> Testing:
> 1. Built the CS using the changes. Tested the column value, post deploydb and 
> it was now set to "Active". Deployed a DC and list template works. 
> 2. Deploy DC worked fine with simulator . Created an instance using the 
> template and it worked to start. Agent for systemvm was coming up.
> Note: 
> 1. For listing templates, a hypervisor in the zone need to be present because 
> listtemplates api is looking for it. Use the list templates post the deployDC 
> and it works.
> 2. We need to set router.version.check to false under global properties of CS 
> post run using simulator. Otherwise you may see errors related to router 
> upgrade etc. This i believe is a known issue and nothing to do with simulator.
> 3. Post the changes, tested only with simulator.
> 3. Also, please change the component field. AS such it is not related to 
> Marvin.
> 
> 
> Diffs
> -
> 
>   
> plugins/hypervisors/simulator/src/com/cloud/agent/manager/MockAgentManagerImpl.java
>  4071aeb 
>   setup/db/templates.simulator.sql 5f9b67d 
> 
> Diff: https://reviews.apache.org/r/17233/diff/
> 
> 
> Testing
> ---
> 
> Testing:
> 1. Built the CS 4.3-forward using the changes. Tested the column value 
> change, post deploydb and it was now set to "Active". Deployed a DC and list 
> template works. 
> 2. Deploy DC worked fine with simulator . Created an instance using the 
> template and it worked to start. Agent for systemvm was coming up.
> Note: 
> 1. For listing templates, a hypervisor in the zone need to be present because 
> listtemplates api is looking for it. Use the list templates post the deployDC 
> and it works.
> 2. We need to set router.version.check to false under global properties of CS 
> post run using simulator. Otherwise you may see errors related to router 
> upgrade etc. This i believe is a known issue and nothing to do with simulator.
> 3. Post the changes, tested only with simulator.
> 
> 
> Thanks,
> 
> Santhosh Edukulla
> 
>

Re: Review Request 17233: Fix for Issue CLOUDSTACK-5875

[Koushik Das]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17233/#review32606
---

Ship it!


4.3-forward -> d31fa09c7e5bb04fcc4594c0352d9b91171e9d1a
master -> f999a01837e60f0c51ef0eb4ad19c29e43ca3037

- Koushik Das


On Jan. 23, 2014, 10:27 a.m., Santhosh Edukulla wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/17233/
> ---
> 
> (Updated Jan. 23, 2014, 10:27 a.m.)
> 
> 
> Review request for cloudstack and Koushik Das.
> 
> 
> Bugs: CLOUDSTACK-5875
> https://issues.apache.org/jira/browse/CLOUDSTACK-5875
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fixed the issue CLOUDSTACK-5875
> The crash issue happens because of null value for CallContext.current() under 
> discoverHostsFull, when called from thread for SystemVMHandler. Currently, 
> there is no call context set for this thread. Currently, as part of 
> MockAgentManagerImpl.java, SystemVMHandler implements Runnable, but when it 
> calls discoverHosts, it does not have any call context set and it is 
> crashing. Because of which agent was not coming up and template sync and 
> resource discovery failed. Added a register and unregister of callcontext of 
> system user for this thread.
> 2. There was a new column added by name "state" under "vm_templates" table. 
> The value of this column for "Active" was checked for listing the templates 
> if there was no removed attribute set for list templates api. This column was 
> not present in 4.2. Added a column value "Active" for simulator schema. The 
> value of this column was not Active and so listing failed.
> Testing:
> 1. Built the CS using the changes. Tested the column value, post deploydb and 
> it was now set to "Active". Deployed a DC and list template works. 
> 2. Deploy DC worked fine with simulator . Created an instance using the 
> template and it worked to start. Agent for systemvm was coming up.
> Note: 
> 1. For listing templates, a hypervisor in the zone need to be present because 
> listtemplates api is looking for it. Use the list templates post the deployDC 
> and it works.
> 2. We need to set router.version.check to false under global properties of CS 
> post run using simulator. Otherwise you may see errors related to router 
> upgrade etc. This i believe is a known issue and nothing to do with simulator.
> 3. Post the changes, tested only with simulator.
> 3. Also, please change the component field. AS such it is not related to 
> Marvin.
> 
> 
> Diffs
> -
> 
>   
> plugins/hypervisors/simulator/src/com/cloud/agent/manager/MockAgentManagerImpl.java
>  4071aeb 
>   setup/db/templates.simulator.sql 5f9b67d 
> 
> Diff: https://reviews.apache.org/r/17233/diff/
> 
> 
> Testing
> ---
> 
> Testing:
> 1. Built the CS 4.3-forward using the changes. Tested the column value 
> change, post deploydb and it was now set to "Active". Deployed a DC and list 
> template works. 
> 2. Deploy DC worked fine with simulator . Created an instance using the 
> template and it worked to start. Agent for systemvm was coming up.
> Note: 
> 1. For listing templates, a hypervisor in the zone need to be present because 
> listtemplates api is looking for it. Use the list templates post the deployDC 
> and it works.
> 2. We need to set router.version.check to false under global properties of CS 
> post run using simulator. Otherwise you may see errors related to router 
> upgrade etc. This i believe is a known issue and nothing to do with simulator.
> 3. Post the changes, tested only with simulator.
> 
> 
> Thanks,
> 
> Santhosh Edukulla
> 
>

Re: [ACS 4.3] RC update

[Prasanna Santhanam]

On Thu, Jan 23, 2014 at 11:39:30AM +, Santhosh Edukulla wrote:
> Simulator issue is fixed. It now works, please check.

CLOUDSTACK-5875 probably needs to go to master as well. Didn't see a
commit there. Once it's fixed in master all jobs in [1]
will show success. These are run on a per-commit basis.   

[1] http://jenkins.buildacloud.org/view/simulator/

Thanks,
-- 
Prasanna.,


Powered by BigRock.com

Re: Create GRE tunnel failed in 4.2 with XenServer.

[Nguyen Anh Tu]

Wow... I thought everything was done in XenServer before my submitted patch.

--Tuna

Sent from my GT-N7000
On Jan 23, 2014 6:49 PM, "Murali Reddy"  wrote:

> Please see the thread
>
> https://www.mail-archive.com/dev@cloudstack.apache.org/msg17396.html
>
>
>
> On 23/01/14 5:10 PM, "Florin Dumitrascu"
>  wrote:
>
> >Hi,
> >
> >Just want to add a few of my observations to what Tuna said.
> >
> >
> >a.   I managed to have GRE isolation working with CloudStack 4.1.1
> >and a quick patch to bypass "enableXenserverNetwork" method.
> >
> >
> >
> >b.  I tried GRE isolation with CloudStack 4.2.1 with the same quick
> >patch for bypassing "enableXenserverNetwork".
> >
> >Once that method was bypassed, guest VMs came up, but the tunnel was not
> >created. It seems to me that OvsElement methods (implement, prepare) are
> >not invoked.
> >
> >Did something change in 4.2 to affect this ? I am setting
> >"sdn.ovs.controller=true" in global settings and select GRE isolation
> >method in the guest physical network.
> >
> >
> >Thank you,
> >Florin
> >
> >
> >
> >From: ng.t...@gmail.com [mailto:ng.t...@gmail.com] On Behalf Of Nguyen
> >Anh Tu
> >Sent: Thursday, January 23, 2014 10:15 AM
> >To: dev@cloudstack.apache.org; Sebastien Goasguen; Chiradeep Vittal;
> >Florin Dumitrascu
> >Subject: Create GRE tunnel failed in 4.2 with XenServer.
> >
> >
> >Guys,
> >
> >Florin raised a problem in creating GRE tunnel with ACS 4.2 release and
> >XenServer 6.2. I found the problem come from enableXenserverNetwork
> >method. CloudStack made a tricky to create network when plugging a VIF to
> >dom0 and then unplugging immediately. With XCP version I done in GSOC, I
> >bypassed that step so that no problem.
> >
> >Didn't know why we need that tricky and how to solve it. I'm working on
> >it. Any help or explaination?
> >
> >Thanks,
> >
> >--Tuna
> >
> >Sent from my GT-N7000
> >
> >IMPORTANT NOTE: The information in this e-mail (and any attachments) is
> >confidential. The contents may not be disclosed or used by anyone other
> >than the addressee. If you are not the intended recipient, please notify
> >the sender immediately or telephone: +353 (0)1 6204700. We cannot accept
> >any responsibility for the accuracy or completeness of this message as it
> >has been transmitted over a public network. If you suspect that the
> >message may have been intercepted or amended, please call the sender.
> >
>
>
>

Re: Review Request 17231: review request for master of defect CLOUDSTACJ-2031

[Damodar Reddy Talakanti]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17231/
---

(Updated Jan. 23, 2014, 12:07 p.m.)


Review request for cloudstack and Jayapal Reddy.


Changes
---

moved db schema changes to 430to440 insted of 421to430.


Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-2031

https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/CLOUDSTACK-2031


Repository: cloudstack-git


Description
---

This is for master branch of the review request 
https://reviews.apache.org/r/16780/


Diffs (updated)
-

  api/src/org/apache/cloudstack/api/command/user/vm/AddIpToVmNicCmd.java 
c0e8d3e 
  engine/schema/src/com/cloud/vm/dao/NicSecondaryIpDao.java 9fbfa27 
  engine/schema/src/com/cloud/vm/dao/NicSecondaryIpDaoImpl.java 2f3cc29 
  server/src/com/cloud/configuration/Config.java 9117bc4 
  server/src/com/cloud/network/NetworkServiceImpl.java 056190f 
  setup/db/db/schema-430to440.sql 1b6a9ab 

Diff: https://reviews.apache.org/r/17231/diff/


Testing
---


Thanks,

Damodar Reddy Talakanti

Re: Review Request 17231: review request for master of defect CLOUDSTACJ-2031

[Damodar Reddy Talakanti]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17231/
---

(Updated Jan. 23, 2014, 12:10 p.m.)


Review request for cloudstack, Abhinandan Prateek and Jayapal Reddy.


Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-2031

https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/CLOUDSTACK-2031


Repository: cloudstack-git


Description
---

This is for master branch of the review request 
https://reviews.apache.org/r/16780/


Diffs
-

  api/src/org/apache/cloudstack/api/command/user/vm/AddIpToVmNicCmd.java 
c0e8d3e 
  engine/schema/src/com/cloud/vm/dao/NicSecondaryIpDao.java 9fbfa27 
  engine/schema/src/com/cloud/vm/dao/NicSecondaryIpDaoImpl.java 2f3cc29 
  server/src/com/cloud/configuration/Config.java 9117bc4 
  server/src/com/cloud/network/NetworkServiceImpl.java 056190f 
  setup/db/db/schema-430to440.sql 1b6a9ab 

Diff: https://reviews.apache.org/r/17231/diff/


Testing
---


Thanks,

Damodar Reddy Talakanti

Re: Review Request 17231: review request for master of defect CLOUDSTACJ-2031

[Damodar Reddy Talakanti]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17231/
---

(Updated Jan. 23, 2014, 12:09 p.m.)


Review request for cloudstack, Abhinandan Prateek and Jayapal Reddy.


Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-2031

https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/CLOUDSTACK-2031


Repository: cloudstack-git


Description
---

This is for master branch of the review request 
https://reviews.apache.org/r/16780/


Diffs
-

  api/src/org/apache/cloudstack/api/command/user/vm/AddIpToVmNicCmd.java 
c0e8d3e 
  engine/schema/src/com/cloud/vm/dao/NicSecondaryIpDao.java 9fbfa27 
  engine/schema/src/com/cloud/vm/dao/NicSecondaryIpDaoImpl.java 2f3cc29 
  server/src/com/cloud/configuration/Config.java 9117bc4 
  server/src/com/cloud/network/NetworkServiceImpl.java 056190f 
  setup/db/db/schema-430to440.sql 1b6a9ab 

Diff: https://reviews.apache.org/r/17231/diff/


Testing
---


Thanks,

Damodar Reddy Talakanti

RE: Create GRE tunnel failed in 4.2 with XenServer.

[Florin Dumitrascu]

Hi Murali, Tuna,

Thank you for this piece of information. All starts to make sense now.
I am wondering if there is a better way to communicate this issue to end users. 
It would save others a couple of weeks struggling.
If GRE is not just a technology preview (meaning it has been explicitly 
mentioned in previous release notes), the known issues lists for 4.2.0 and 
4.2.1 should be explicitly updated.

Leaving 4.2 behind now, which will be the first release to include GRE 
refactoring with OVS service provider ?

Regards,
Florin

-Original Message-
From: ng.t...@gmail.com [mailto:ng.t...@gmail.com] On Behalf Of Nguyen Anh Tu
Sent: Thursday, January 23, 2014 11:56 AM
To: Murali Reddy
Cc: dev@cloudstack.apache.org; Chiradeep Vittal; Sebastien Goasguen
Subject: Re: Create GRE tunnel failed in 4.2 with XenServer.

Wow... I thought everything was done in XenServer before my submitted patch.

--Tuna

Sent from my GT-N7000
On Jan 23, 2014 6:49 PM, "Murali Reddy"  wrote:

> Please see the thread
>
> https://www.mail-archive.com/dev@cloudstack.apache.org/msg17396.html
>
>
>
> On 23/01/14 5:10 PM, "Florin Dumitrascu"
>  wrote:
>
> >Hi,
> >
> >Just want to add a few of my observations to what Tuna said.
> >
> >
> >a.   I managed to have GRE isolation working with CloudStack 4.1.1
> >and a quick patch to bypass "enableXenserverNetwork" method.
> >
> >
> >
> >b.  I tried GRE isolation with CloudStack 4.2.1 with the same quick
> >patch for bypassing "enableXenserverNetwork".
> >
> >Once that method was bypassed, guest VMs came up, but the tunnel was
> >not created. It seems to me that OvsElement methods (implement,
> >prepare) are not invoked.
> >
> >Did something change in 4.2 to affect this ? I am setting
> >"sdn.ovs.controller=true" in global settings and select GRE isolation
> >method in the guest physical network.
> >
> >
> >Thank you,
> >Florin
> >
> >
> >
> >From: ng.t...@gmail.com [mailto:ng.t...@gmail.com] On Behalf Of
> >Nguyen Anh Tu
> >Sent: Thursday, January 23, 2014 10:15 AM
> >To: dev@cloudstack.apache.org; Sebastien Goasguen; Chiradeep Vittal;
> >Florin Dumitrascu
> >Subject: Create GRE tunnel failed in 4.2 with XenServer.
> >
> >
> >Guys,
> >
> >Florin raised a problem in creating GRE tunnel with ACS 4.2 release
> >and XenServer 6.2. I found the problem come from
> >enableXenserverNetwork method. CloudStack made a tricky to create
> >network when plugging a VIF to
> >dom0 and then unplugging immediately. With XCP version I done in
> >GSOC, I bypassed that step so that no problem.
> >
> >Didn't know why we need that tricky and how to solve it. I'm working
> >on it. Any help or explaination?
> >
> >Thanks,
> >
> >--Tuna
> >
> >Sent from my GT-N7000
> >
> >IMPORTANT NOTE: The information in this e-mail (and any attachments)
> >is confidential. The contents may not be disclosed or used by anyone
> >other than the addressee. If you are not the intended recipient,
> >please notify the sender immediately or telephone: +353 (0)1 6204700.
> >We cannot accept any responsibility for the accuracy or completeness
> >of this message as it has been transmitted over a public network. If
> >you suspect that the message may have been intercepted or amended, please 
> >call the sender.
> >
>
>
>

IMPORTANT NOTE: The information in this e-mail (and any attachments) is 
confidential. The contents may not be disclosed or used by anyone other than 
the addressee. If you are not the intended recipient, please notify the sender 
immediately or telephone: +353 (0)1 6204700. We cannot accept any 
responsibility for the accuracy or completeness of this message as it has been 
transmitted over a public network. If you suspect that the message may have 
been intercepted or amended, please call the sender.

Re: Review Request 17231: review request for master of defect CLOUDSTACJ-2031

[Jayapal Reddy]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17231/#review32615
---

Ship it!


Ship It!

- Jayapal Reddy


On Jan. 23, 2014, 12:10 p.m., Damodar Reddy Talakanti wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/17231/
> ---
> 
> (Updated Jan. 23, 2014, 12:10 p.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and Jayapal Reddy.
> 
> 
> Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-2031
> 
> https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/CLOUDSTACK-2031
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> This is for master branch of the review request 
> https://reviews.apache.org/r/16780/
> 
> 
> Diffs
> -
> 
>   api/src/org/apache/cloudstack/api/command/user/vm/AddIpToVmNicCmd.java 
> c0e8d3e 
>   engine/schema/src/com/cloud/vm/dao/NicSecondaryIpDao.java 9fbfa27 
>   engine/schema/src/com/cloud/vm/dao/NicSecondaryIpDaoImpl.java 2f3cc29 
>   server/src/com/cloud/configuration/Config.java 9117bc4 
>   server/src/com/cloud/network/NetworkServiceImpl.java 056190f 
>   setup/db/db/schema-430to440.sql 1b6a9ab 
> 
> Diff: https://reviews.apache.org/r/17231/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Damodar Reddy Talakanti
> 
>

Re: [VOTE] Apache CloudStack 4.3.0 (first round)

[Hugo Trippaers]

Thanks Abhi. I think that means that we need to consider this a mine and needs 
fixing. 

Unfortunately that means a -1 on the current RC, but i hope people will 
continue testing this RC so we get some more feedback.




Cheers,

Hugo




On 23 jan. 2014, at 10:16, Abhinandan Prateek  
wrote:

> Long values till at least 128 are cached, the ref being same, the ==
> operator is guaranteed to work for values from -127 to 128.
> It the value can go beyond that range then this is a potential mine.
> 
> -abhi
> 
> On 23/01/14 1:51 pm, "Hugo Trippaers"  wrote:
> 
>> Thanks Animesh,
>> 
>> Great to see the first RC for 4.3.
>> 
>> I¹ve been running some findbugs analysis on master and found several
>> issues that also seem to be present in the 4.3 branch. I¹ve made two
>> commit on master that fixed some issues that i spotted
>> (c2da2803476d55e814ec0d849482bd07c4f9f8f1 and
>> d19157fbb169eec029d1efee9ddd06e6b6aad9a4). Both fix an issue where an
>> object is compared by using == instead of equals. I¹m doubting if this is
>> worth to -1 the current RC as i can¹t oversee the impact of these bugs
>> and looking for opinions.
>> 
>> Cheers,
>> 
>> Hugo
>> 
>> 
>> 
>> 
>> 
>> 
>> On 23 jan. 2014, at 06:54, Animesh Chaturvedi
>>  wrote:
>> 
>>> 
>>> 
>>> 
>>> Hi All,
>>> 
>>> 
>>> 
>>> I've created a 4.3.0 release, with the following artifacts up for a
>>> 
>>> vote:
>>> 
>>> 
>>> 
>>> Git Branch and Commit SH:
>>> 
>>> 
>>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=ref
>>> s/heads/4.3
>>> Commit: 43d485c92d5919085cacb1cd0c7e78503ab9788a
>>> 
>>> 
>>> 
>>> List of changes:
>>> 
>>> 
>>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=C
>>> HANGES;hb=4.3
>>> 
>>> 
>>> 
>>> Source release (checksums and signatures are available at the same
>>> 
>>> location):
>>> 
>>> https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
>>> 
>>> 
>>> 
>>> PGP release keys (signed using 94BE0D7C):
>>> 
>>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>> 
>>> 
>>> 
>>> Testing instructions are here:
>>> 
>>> 
>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+proce
>>> dure
>>> 
>>> 
>>> 
>>> Vote will be open for 72 hours.
>>> 
>>> 
>>> 
>>> For sanity in tallying the vote, can PMC members please be sure to
>>> indicate "(binding)" with their vote?
>>> 
>>> 
>>> 
>>> [ ] +1  approve
>>> 
>>> [ ] +0  no opinion
>>> 
>>> [ ] -1  disapprove (and reason why)
>>> 
>>> 
>>> 
>> 
> 

Re: [VOTE] Apache CloudStack 4.3.0 (first round)

[Ove Ewerlid]

The list of changes link indicates that the 4.3.0 release notes should 
be here;

  http://cloudstack.apache.org/docs
I'm not seeing any 4.3.0 related docs there.
is there some update that has not propagated to the apache web site yet ...

/Ove

-


Apache CloudStack CHANGES
==

Full release notes for each release are located in the project's 
documentation website:

http://cloudstack.apache.org/docs

Version 4.3.0

Please refer to release notes for list of changes

...

On 01/23/2014 06:54 AM, Animesh Chaturvedi wrote:




Hi All,



I've created a 4.3.0 release, with the following artifacts up for a

vote:



Git Branch and Commit SH:

https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
Commit: 43d485c92d5919085cacb1cd0c7e78503ab9788a



List of changes:

https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.3



Source release (checksums and signatures are available at the same

location):

https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/



PGP release keys (signed using 94BE0D7C):

https://dist.apache.org/repos/dist/release/cloudstack/KEYS



Testing instructions are here:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure



Vote will be open for 72 hours.



For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?



[ ] +1  approve

[ ] +0  no opinion

[ ] -1  disapprove (and reason why)







--
Ove Everlid
System Administrator / Architect / SDN- & Automation- & Linux-hacker
Mobile: +46706662363 (dedicated work mobile)
Country: Sweden, timezone; Middle Europan Time (MET or GMT+1)

RE: [ANNOUNCE] Switch to Java 7 in master branch on Monday Jan 27th 2014

[Alex Huang]

Sounds good.  Thanks Wido!

--Alex

> -Original Message-
> From: Wido den Hollander [mailto:w...@widodh.nl]
> Sent: Thursday, January 23, 2014 10:49 AM
> To: dev@cloudstack.apache.org
> Subject: [ANNOUNCE] Switch to Java 7 in master branch on Monday Jan 27th
> 2014
> 
> Hi,
> 
> We had multiple threads discussing the switch to Java 7 which all ended in +1
> everywhere.
> 
> The most recent [0] one is from the beginning of this month and since
> nobody actually took the step I'll do it.
> 
> On 27-01-2014 11:00:00 CET / GMT +1 I'll push a commit where on the
> pom.xml cs.jdk.version will be set to 1.7.
> 
> I'll also update the Debian and RPM packaging to only depend on Java 7
> packages and no longer on Java 6.
> 
> Without any objections I'll continue with this on the date specified above.
> 
> Wido
> 
> [0]:
> http://mail-archives.apache.org/mod_mbox/cloudstack-
> dev/201401.mbox/%3CCEF079AF.5E3AB%25kelven.yang%40citrix.com%3E

Re: Location of the 4.3 System VM Templates

[David Nalley]

I'll respectfully disagree. We need to find a place for systemVMs
whether that means classifying them as convenience binaries or putting
them on Wido's box, or S3.

The problem with jenkins, and specifically with that link for jenkins
is that 4.3 is still a living branch; and like with 4.2.1 there might
be changes to the system VM. We should promote a known good systemvm.

--David

On Thu, Jan 23, 2014 at 1:55 AM, Hugo Trippaers  wrote:
> The best location for the system vm images is 
> http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/. There 
> we have the systemvm images that belong to the latest build agains the 4.3 
> tree. Look for the 'Last Successful Artifacts’ on that page.
>
> Cheers,
>
> Hugo
>
>
> On 23 jan. 2014, at 07:30, Abhisek Basu  wrote:
>
>> I was able to get them from path like: 
>> http://download.cloud.com/templates/4.3/systemvm64template-2013-12-23-hyperv.vhd.bz2
>>
>> Regards,
>>
>> Abhisek
>>
>> -Original Message- From: Radhika Puthiyetath
>> Sent: Thursday, January 23, 2014 11:15 AM
>> To: dev@cloudstack.apache.org
>> Subject: Location of the 4.3 System VM Templates
>>
>> Hi,
>>
>> Could someone please help me with the location of the System VM Templates 
>> for 4.3 release ?
>>
>> I am unable to access http://download.cloud.com. I assume that they are 
>> posted to templates directory.
>>
>> Thanks
>> -Radhika
>>
>

Re: Location of the 4.3 System VM Templates

[Wido den Hollander]

On 01/23/2014 03:35 PM, David Nalley wrote:

I'll respectfully disagree. We need to find a place for systemVMs
whether that means classifying them as convenience binaries or putting
them on Wido's box, or S3.



I manually sync the images now. Sometimes I download some images to this 
location: http://cloudstack.apt-get.eu/systemvm/


For example the 4.2 Templates should be there currently.


The problem with jenkins, and specifically with that link for jenkins
is that 4.3 is still a living branch; and like with 4.2.1 there might
be changes to the system VM. We should promote a known good systemvm.

--David

On Thu, Jan 23, 2014 at 1:55 AM, Hugo Trippaers  wrote:

The best location for the system vm images is 
http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/. There we 
have the systemvm images that belong to the latest build agains the 4.3 tree. 
Look for the 'Last Successful Artifacts’ on that page.

Cheers,

Hugo


On 23 jan. 2014, at 07:30, Abhisek Basu  wrote:


I was able to get them from path like: 
http://download.cloud.com/templates/4.3/systemvm64template-2013-12-23-hyperv.vhd.bz2

Regards,

Abhisek

-Original Message- From: Radhika Puthiyetath
Sent: Thursday, January 23, 2014 11:15 AM
To: dev@cloudstack.apache.org
Subject: Location of the 4.3 System VM Templates

Hi,

Could someone please help me with the location of the System VM Templates for 
4.3 release ?

I am unable to access http://download.cloud.com. I assume that they are posted 
to templates directory.

Thanks
-Radhika

Re: [VOTE] Apache CloudStack 4.3.0 (first round)

[Srikanteswararao Talluri]

+1

I could successfully deploy an advanced zone with XenServer 6.2 - did some
basic testing around snapshots, templates and VPC.

Thanks,
~Talluri

On 23/01/14 7:06 pm, "Ove Ewerlid"  wrote:

>The list of changes link indicates that the 4.3.0 release notes should
>be here;
>   http://cloudstack.apache.org/docs
>I'm not seeing any 4.3.0 related docs there.
>is there some update that has not propagated to the apache web site yet
>...
>
>/Ove
>
>-
>
>
>Apache CloudStack CHANGES
>==
>
>Full release notes for each release are located in the project's
>documentation website:
>http://cloudstack.apache.org/docs
>
>Version 4.3.0
>
>Please refer to release notes for list of changes
>
>...
>
>On 01/23/2014 06:54 AM, Animesh Chaturvedi wrote:
>>
>>
>>
>> Hi All,
>>
>>
>>
>> I've created a 4.3.0 release, with the following artifacts up for a
>>
>> vote:
>>
>>
>>
>> Git Branch and Commit SH:
>>
>> 
>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=ref
>>s/heads/4.3
>> Commit: 43d485c92d5919085cacb1cd0c7e78503ab9788a
>>
>>
>>
>> List of changes:
>>
>> 
>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=C
>>HANGES;hb=4.3
>>
>>
>>
>> Source release (checksums and signatures are available at the same
>>
>> location):
>>
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
>>
>>
>>
>> PGP release keys (signed using 94BE0D7C):
>>
>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>
>>
>>
>> Testing instructions are here:
>>
>> 
>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+proce
>>dure
>>
>>
>>
>> Vote will be open for 72 hours.
>>
>>
>>
>> For sanity in tallying the vote, can PMC members please be sure to
>>indicate "(binding)" with their vote?
>>
>>
>>
>> [ ] +1  approve
>>
>> [ ] +0  no opinion
>>
>> [ ] -1  disapprove (and reason why)
>>
>>
>>
>>
>
>
>-- 
>Ove Everlid
>System Administrator / Architect / SDN- & Automation- & Linux-hacker
>Mobile: +46706662363 (dedicated work mobile)
>Country: Sweden, timezone; Middle Europan Time (MET or GMT+1)

Re: [ANNOUNCE] Switch to Java 7 in master branch on Monday Jan 27th 2014

[Hugo Trippaers]

+1

Cheers,

Hugo

On 23 jan. 2014, at 14:02, Alex Huang  wrote:

> Sounds good.  Thanks Wido!
> 
> --Alex
> 
>> -Original Message-
>> From: Wido den Hollander [mailto:w...@widodh.nl]
>> Sent: Thursday, January 23, 2014 10:49 AM
>> To: dev@cloudstack.apache.org
>> Subject: [ANNOUNCE] Switch to Java 7 in master branch on Monday Jan 27th
>> 2014
>> 
>> Hi,
>> 
>> We had multiple threads discussing the switch to Java 7 which all ended in +1
>> everywhere.
>> 
>> The most recent [0] one is from the beginning of this month and since
>> nobody actually took the step I'll do it.
>> 
>> On 27-01-2014 11:00:00 CET / GMT +1 I'll push a commit where on the
>> pom.xml cs.jdk.version will be set to 1.7.
>> 
>> I'll also update the Debian and RPM packaging to only depend on Java 7
>> packages and no longer on Java 6.
>> 
>> Without any objections I'll continue with this on the date specified above.
>> 
>> Wido
>> 
>> [0]:
>> http://mail-archives.apache.org/mod_mbox/cloudstack-
>> dev/201401.mbox/%3CCEF079AF.5E3AB%25kelven.yang%40citrix.com%3E

Re: Review Request 16249: CLOUDSTACK-5496 : Account included in ActionEvents is Project Account ID

[David Grizzanti]

> On Jan. 17, 2014, 6:06 a.m., Murali Reddy wrote:
> > changes look good, patch does not apply on master. Can you please resubmit.
> > 
> > Also please see if the patch applies on 4.2, when you resubmit.

Murali,

Added patch for master - it does not apply on 4.2.  Code change enough that it 
won't apply cleanly.  The changes are almost identical except for a few things.


- David


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/16249/#review32129
---


On Jan. 22, 2014, 2:07 p.m., David Grizzanti wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/16249/
> ---
> 
> (Updated Jan. 22, 2014, 2:07 p.m.)
> 
> 
> Review request for cloudstack and Murali Reddy.
> 
> 
> Bugs: CLOUDSTACK-5496
> https://issues.apache.org/jira/browse/CLOUDSTACK-5496
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-5496 : Account included in ActionEvents is Project Account ID
> 
> When Action Events are generated and placed on the Event Bus, an "account" 
> parameter is included with the event. When these events are generated for 
> resources within projects, this "account" parameter is not useful as it's the 
> UUID of the project account, instead of the project. 
> 
> To solve this, I updated ActionEventsUtil class to include a "project" 
> parameter in the generated events when the resource is being 
> changed/add/deleted in a project.
> 
> 
> Diffs
> -
> 
>   server/src/com/cloud/event/ActionEventUtils.java 0363a0d 
>   server/test/org/apache/cloudstack/affinity/AffinityApiUnitTest.java 061fd42 
> 
> Diff: https://reviews.apache.org/r/16249/diff/
> 
> 
> Testing
> ---
> 
> Testing done 4.2
> 
> 
> Thanks,
> 
> David Grizzanti
> 
>

RE: [ANNOUNCE] Switch to Java 7 in master branch on Monday Jan 27th 2014

[Rajesh Battala]

+1. 

-Original Message-
From: Wido den Hollander [mailto:w...@widodh.nl] 
Sent: Thursday, January 23, 2014 4:19 PM
To: dev@cloudstack.apache.org
Subject: [ANNOUNCE] Switch to Java 7 in master branch on Monday Jan 27th 2014

Hi,

We had multiple threads discussing the switch to Java 7 which all ended in +1 
everywhere.

The most recent [0] one is from the beginning of this month and since nobody 
actually took the step I'll do it.

On 27-01-2014 11:00:00 CET / GMT +1 I'll push a commit where on the pom.xml 
cs.jdk.version will be set to 1.7.

I'll also update the Debian and RPM packaging to only depend on Java 7 packages 
and no longer on Java 6.

Without any objections I'll continue with this on the date specified above.

Wido

[0]: 
http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201401.mbox/%3CCEF079AF.5E3AB%25kelven.yang%40citrix.com%3E

DB timeouts on failover

[Francois Gaudreault]

Hi,

There was a thread on the users mailing list around the DB connection 
timeouts when the underlaying MySQL active/passive cluster changes 
master. The solution so far is to use a crontab to monitor if the server 
is crashed.


I'm not too familiar with the tomcat or cloudstack configs, but is there 
any jdbc settings or timeouts we can tweak?


--
Francois Gaudreault
Architecte de Solution Cloud | Cloud Solutions Architect
fgaudrea...@cloudops.com
514-629-6775
- - -
CloudOps
420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_

Re: [VOTE] Apache CloudStack 4.3.0 (first round)

[Daan Hoogland]

Animesh, I can see the commit id that you mention for this release,
but it is a revert of a functional commit commented on as
'CLOUDSTACK-5923: CS doesn't do master switch for XS any more, CS will
depend on XS HA to do master switch, XS HA needs to be enabled.'

Did you forget to push the RC branch? Or was it not created
as you baked the release candidate?

regards,
Daan

On Thu, Jan 23, 2014 at 3:42 PM, Srikanteswararao Talluri
 wrote:
> +1
>
> I could successfully deploy an advanced zone with XenServer 6.2 - did some
> basic testing around snapshots, templates and VPC.
>
> Thanks,
> ~Talluri
>
> On 23/01/14 7:06 pm, "Ove Ewerlid"  wrote:
>
>>The list of changes link indicates that the 4.3.0 release notes should
>>be here;
>>   http://cloudstack.apache.org/docs
>>I'm not seeing any 4.3.0 related docs there.
>>is there some update that has not propagated to the apache web site yet
>>...
>>
>>/Ove
>>
>>-
>>
>>
>>Apache CloudStack CHANGES
>>==
>>
>>Full release notes for each release are located in the project's
>>documentation website:
>>http://cloudstack.apache.org/docs
>>
>>Version 4.3.0
>>
>>Please refer to release notes for list of changes
>>
>>...
>>
>>On 01/23/2014 06:54 AM, Animesh Chaturvedi wrote:
>>>
>>>
>>>
>>> Hi All,
>>>
>>>
>>>
>>> I've created a 4.3.0 release, with the following artifacts up for a
>>>
>>> vote:
>>>
>>>
>>>
>>> Git Branch and Commit SH:
>>>
>>>
>>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=ref
>>>s/heads/4.3
>>> Commit: 43d485c92d5919085cacb1cd0c7e78503ab9788a
>>>
>>>
>>>
>>> List of changes:
>>>
>>>
>>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=C
>>>HANGES;hb=4.3
>>>
>>>
>>>
>>> Source release (checksums and signatures are available at the same
>>>
>>> location):
>>>
>>> https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
>>>
>>>
>>>
>>> PGP release keys (signed using 94BE0D7C):
>>>
>>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>>
>>>
>>>
>>> Testing instructions are here:
>>>
>>>
>>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+proce
>>>dure
>>>
>>>
>>>
>>> Vote will be open for 72 hours.
>>>
>>>
>>>
>>> For sanity in tallying the vote, can PMC members please be sure to
>>>indicate "(binding)" with their vote?
>>>
>>>
>>>
>>> [ ] +1  approve
>>>
>>> [ ] +0  no opinion
>>>
>>> [ ] -1  disapprove (and reason why)
>>>
>>>
>>>
>>>
>>
>>
>>--
>>Ove Everlid
>>System Administrator / Architect / SDN- & Automation- & Linux-hacker
>>Mobile: +46706662363 (dedicated work mobile)
>>Country: Sweden, timezone; Middle Europan Time (MET or GMT+1)
>

XS master handling in 4.3.0

[Francois Gaudreault]

Quick question...

In the 4.3.0 vote thread, I saw this ticket:

CLOUDSTACK-5923

OK fine, but what happens if we are running 4.2.1 with a cluster today? Should 
we enable HA today or only when we upgrade to 4.3?

Thanks!

--
Francois Gaudreault
Architecte de Solution Cloud | Cloud Solutions Architect
fgaudrea...@cloudops.com
514-629-6775
- - -
CloudOps
420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_

Re: Review Request 15247: [DOC] CLOUDSTACK-4967: Add a section to describe VNI allocation matter

[Toshiaki Hatano]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15247/#review32625
---

Ship it!


Ship It!

- Toshiaki Hatano


On Jan. 22, 2014, 5:44 a.m., Yoshikazu Nojima wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15247/
> ---
> 
> (Updated Jan. 22, 2014, 5:44 a.m.)
> 
> 
> Review request for cloudstack, Marcus Sorensen and Toshiaki Hatano.
> 
> 
> Bugs: CLOUDSTACK-4967
> https://issues.apache.org/jira/browse/CLOUDSTACK-4967
> 
> 
> Repository: cloudstack-docs
> 
> 
> Description
> ---
> 
> This patch updates CloudStack Plugin Guide for the VXLAN Plugin.
> 
> - Add a section to describe VNIs allocation matter
> - Remove section that explain how to configure the bridge for traffic label 
> because the bridge configuration is no longer necessary.
> - Update screen shots to catch up new UI visual appearance.
> 
> 
> Diffs
> -
> 
>   vxlan/en-US/images/vxlan-physicalnetwork.png 
> e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
>   vxlan/en-US/images/vxlan-trafficlabel.png 
> 956d5f4f58f592ed3f260d6e1982c238c2ddf06a 
>   vxlan/en-US/images/vxlan-vniconfig.png PRE-CREATION 
>   vxlan/en-US/plugin-vxlan-config-hypervisor.xml 2c5e138 
>   vxlan/en-US/plugin-vxlan-config-management.xml 21f5461 
>   vxlan/en-US/plugin-vxlan-requirements.xml c2e04a6 
>   vxlan/en-US/plugin-vxlan-revision-history.xml ec04d11 
> 
> Diff: https://reviews.apache.org/r/15247/diff/
> 
> 
> Testing
> ---
> 
> I generated and confirmed the PDF.
> 
> 
> Thanks,
> 
> Yoshikazu Nojima
> 
>

Re: [ISSUES] Master VMware is broken

[Min Chen]

It failed in invoking addVmwareDC, where we will invoke vmware API to get
CustomeField. Using java generics, class reflection failed in finding that
declared method, thus throwing NoSuchMethodFound exception.

Thanks
-min

On 1/22/14 10:52 PM, "Hugo Trippaers"  wrote:

>Sorry about that :-(  Thanks for finding and fixing it.
>
>Where did you encounter the error? I wonder why i didn¹t catch it with my
>tests against vmware.
>
>Cheers,
>
>Hugo
>
>On 23 jan. 2014, at 03:01, Min Chen  wrote:
>
>> FYI, I checked in a fix 206c35c620a8e7a707f371e5a9e5dfd795912f5b for
>>this
>> to unblock my testing.
>> 
>> Thanks
>> -min
>> 
>> On 1/22/14 5:43 PM, "Kelven Yang"  wrote:
>> 
>>> Master VMware was broken by this commit
>>> 
>>> author  Hugo 
>>> 
>>>Trippaers>>rc
>>> 
>>>h;h=b20add810e5751f53946f695b6223a8016f104a5;s=Hugo+Trippaers;st=author>
>>> 
>>>>>p=
>>> 
>>>cloudstack.git;a=search;h=b20add810e5751f53946f695b6223a8016f104a5;s=htr
>>>ip
>>> pa...@schubergphilis.com;st=author>
>>>   Wed, 22 Jan 2014 08:34:46 + (09:34 +0100)
>>> committer   Hugo
>>> 
>>>Trippaers>>rc
>>> 
>>>h;h=b20add810e5751f53946f695b6223a8016f104a5;s=Hugo+Trippaers;st=committ
>>>er
 
 

>>>   Wed, 22 Jan 2014 08:37:34 + (09:37 +0100)
>>> commit  b20add810e5751f53946f695b6223a8016f104a5
>>> tree
>>> 
>>>89e7e66704b09959bc5d77e4e20562e6dcc05306>>ep
>>> 
>>>os/asf?p=cloudstack.git;a=tree;h=89e7e66704b09959bc5d77e4e20562e6dcc0530
>>>6;
>>> hb=b20add810e5751f53946f695b6223a8016f104a5>
>>> 
>>>tree>>9e
>>> 
>>>7e66704b09959bc5d77e4e20562e6dcc05306;hb=b20add810e5751f53946f695b6223a8
>>>01
>>> 6f104a5> | 
>>> 
>>>snapshot>>sh
>>> ot;h=b20add810e5751f53946f695b6223a8016f104a5;sf=tgz>
>>> parent  
>>> 
>>>86124138a1a9129dedaf0f73fcd570156bfe53f6>>ep
>>> 
>>>os/asf?p=cloudstack.git;a=commit;h=86124138a1a9129dedaf0f73fcd570156bfe5
>>>3f
>>> 6>  
>>> 
>>>commit>>;h
>>> =86124138a1a9129dedaf0f73fcd570156bfe53f6> |
>>> 
>>>diff>>ff
>>> 
>>>;h=b20add810e5751f53946f695b6223a8016f104a5;hp=86124138a1a9129dedaf0f73f
>>>cd
>>> 570156bfe53f6>
>>> Get rid of compiler warnings in vmware-base
>>> 
>>> Min and I spent two hours on this to trace down the cause,  Hugo,
>>>please
>>> do test before check-in even if it seems like to remove compiler
>>>warning,
>>> but because of the tricky business with Java generics, it does cause
>>> problem at runtime
>>> 
>>> One of the problem comes from following code, please checkout my
>>>comments
>>> below.
>>> 
>>> -Kelven
>>> 
>>> 
>>> import org.apache.log4j.Logger;
>>> 
>>> @@ 
>>> 
>>>-144,6>>=v
>>> 
>>>mware-base/src/com/cloud/hypervisor/vmware/util/VmwareClient.java;h=3c2c
>>>81
>>> 
>>>d8a5ea3e242a6407ab5a0d2710fa1d0b73;hb=3c2c81d8a5ea3e242a6407ab5a0d2710fa
>>>1d
>>> 0b73#l144> 
>>> 
>>>+144,7>>=v
>>> 
>>>mware-base/src/com/cloud/hypervisor/vmware/util/VmwareClient.java;h=e816
>>>65
>>> 
>>>f71b76a3772b13dae5cc0733d26220c64a;hb=e81665f71b76a3772b13dae5cc0733d262
>>>20
>>> c64a#l144> @@ public class VmwareClient {
>>>ServiceContent serviceContent =
>>> vimPort.retrieveServiceContent(svcInstRef);
>>> 
>>>// Extract a cookie. See vmware sample program
>>> com.vmware.httpfileaccess.GetVMFiles
>>> +@SuppressWarnings("unchecked")
>>>Map> headers = (Map>> 
>>>List>)((BindingProvider)vimPort).getResponseContext().get(Messag
>>>eC
>>> ontext.HTTP_RESPONSE_HEADERS);
>>>List cookies = headers.get("Set-cookie");
>>>String cookieValue = cookies.get(0);
>>> @@ 
>>> 
>>>-256,17>>f=
>>> 
>>>vmware-base/src/com/cloud/hypervisor/vmware/util/VmwareClient.java;h=3c2
>>>c8
>>> 
>>>1d8a5ea3e242a6407ab5a0d2710fa1d0b73;hb=3c2c81d8a5ea3e242a6407ab5a0d2710f
>>>a1
>>> d0b73#l256> 
>>> 
>>>+257,18>>f=
>>> 
>>>vmware-base/src/com/cloud/hypervisor/vmware/util/VmwareClient.java;h=e81
>>>66
>>> 
>>>5f71b76a3772b13dae5cc0733d26220c64a;hb=e81665f71b76a3772b13dae5cc0733d26
>>>22
>>> 0c64a#l257> @@ public class VmwareClient {
>>> * @throws Exception
>>> * in case of error.
>>> */
>>> -public Object g

Re: Review Request 15247: [DOC] CLOUDSTACK-4967: Add a section to describe VNI allocation matter

[Toshiaki Hatano]

> On Jan. 23, 2014, 5:08 p.m., Toshiaki Hatano wrote:
> > Ship It!

applied to master and 4.3.
commit c9b8bc0884e9e1166046bfdd1354a991d39d7d71 in master
commit 002c2b22f43f7ace0ade652e92c2d46b92c3136f in 4.3


- Toshiaki


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15247/#review32625
---


On Jan. 22, 2014, 5:44 a.m., Yoshikazu Nojima wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15247/
> ---
> 
> (Updated Jan. 22, 2014, 5:44 a.m.)
> 
> 
> Review request for cloudstack, Marcus Sorensen and Toshiaki Hatano.
> 
> 
> Bugs: CLOUDSTACK-4967
> https://issues.apache.org/jira/browse/CLOUDSTACK-4967
> 
> 
> Repository: cloudstack-docs
> 
> 
> Description
> ---
> 
> This patch updates CloudStack Plugin Guide for the VXLAN Plugin.
> 
> - Add a section to describe VNIs allocation matter
> - Remove section that explain how to configure the bridge for traffic label 
> because the bridge configuration is no longer necessary.
> - Update screen shots to catch up new UI visual appearance.
> 
> 
> Diffs
> -
> 
>   vxlan/en-US/images/vxlan-physicalnetwork.png 
> e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
>   vxlan/en-US/images/vxlan-trafficlabel.png 
> 956d5f4f58f592ed3f260d6e1982c238c2ddf06a 
>   vxlan/en-US/images/vxlan-vniconfig.png PRE-CREATION 
>   vxlan/en-US/plugin-vxlan-config-hypervisor.xml 2c5e138 
>   vxlan/en-US/plugin-vxlan-config-management.xml 21f5461 
>   vxlan/en-US/plugin-vxlan-requirements.xml c2e04a6 
>   vxlan/en-US/plugin-vxlan-revision-history.xml ec04d11 
> 
> Diff: https://reviews.apache.org/r/15247/diff/
> 
> 
> Testing
> ---
> 
> I generated and confirmed the PDF.
> 
> 
> Thanks,
> 
> Yoshikazu Nojima
> 
>

Re: [VOTE] Apache CloudStack 4.3.0 (first round)

[David Nalley]

Since there's already another -1, I'll add something else that needs
to be fixed but I wouldn't necessarily let become a blocker.

debian/changelog needs an entry indicating the version as a release
rather than snapshot.

This needs to be integrated into our release process though.

--David


On Thu, Jan 23, 2014 at 12:54 AM, Animesh Chaturvedi
 wrote:
>
>
>
> Hi All,
>
>
>
> I've created a 4.3.0 release, with the following artifacts up for a
>
> vote:
>
>
>
> Git Branch and Commit SH:
>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
> Commit: 43d485c92d5919085cacb1cd0c7e78503ab9788a
>
>
>
> List of changes:
>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.3
>
>
>
> Source release (checksums and signatures are available at the same
>
> location):
>
> https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
>
>
>
> PGP release keys (signed using 94BE0D7C):
>
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
>
>
> Testing instructions are here:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
>
>
>
> Vote will be open for 72 hours.
>
>
>
> For sanity in tallying the vote, can PMC members please be sure to indicate 
> "(binding)" with their vote?
>
>
>
> [ ] +1  approve
>
> [ ] +0  no opinion
>
> [ ] -1  disapprove (and reason why)
>
>
>

Re: Weird IP address allocation in 4.3

[Mike Tutkowski]

I asked one of our IT guys to look into this. He determined a port was in
the wrong VLAN and that's how my VM got an IP address from a different DHCP
server.

No CloudStack issue here. :)

Thanks


On Wed, Jan 22, 2014 at 11:05 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> That is an interesting possibility. Thanks, guys
>
>
> On Wed, Jan 22, 2014 at 10:59 PM, Ahmad Emneina wrote:
>
>> Mike, you might have another machine serving up DHCP on that network. If
>> thats the case get it to ignore cloudstack assigned mac addresses (06
>> prefix).
>>
>>
>> On Wed, Jan 22, 2014 at 9:53 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>> > Hi Jayapal,
>> >
>> > That table has 8 rows and includes IP addresses from 192.168.128.23 to
>> > 192.168.128.30 (which should be correct).
>> >
>> > Thanks
>> >
>> >
>> > On Wed, Jan 22, 2014 at 10:49 PM, Jayapal Reddy Uradi <
>> > jayapalreddy.ur...@citrix.com> wrote:
>> >
>> > > Hi Mike,
>> > >
>> > > Can you please check the db table user_ip_address to see what are the
>> ips
>> > > addresses are there.
>> > > IP will be picked from this table.
>> > >
>> > > Thanks,
>> > > Jayapal
>> > >
>> > > On 23-Jan-2014, at 10:35 AM, Mike Tutkowski <
>> > mike.tutkow...@solidfire.com>
>> > > wrote:
>> > >
>> > > > Slight correction (this may have been obvious from one of my screen
>> > > shots):
>> > > > The VM with the address outside of the range I gave to CloudStack is
>> > in a
>> > > > XenServer cluster.
>> > > >
>> > > >
>> > > > On Wed, Jan 22, 2014 at 10:03 PM, Mike Tutkowski <
>> > > > mike.tutkow...@solidfire.com> wrote:
>> > > >
>> > > >> The IP address that CloudStack says is assigned to VM i-2-11-VM
>> > > >> (192.168.128.28) does not appear to be assigned to any VM in the
>> > system
>> > > >> (user or system VM).
>> > > >>
>> > > >>
>> > > >> On Wed, Jan 22, 2014 at 9:59 PM, Mike Tutkowski <
>> > > >> mike.tutkow...@solidfire.com> wrote:
>> > > >>
>> > > >>> Hi,
>> > > >>>
>> > > >>> I was wondering if someone who deals with networking in CloudStack
>> > > might
>> > > >>> know something about this.
>> > > >>>
>> > > >>> I have a development setup with one zone, one pod, and three
>> clusters
>> > > >>> (one VMware, one XenServer, and one KVM).
>> > > >>>
>> > > >>> The IP addresses I've given to CloudStack span from
>> 192.168.128.20 to
>> > > >>> 192.168.128.30 (just 11 addresses).
>> > > >>>
>> > > >>> http://i.imgur.com/3SAn98W.png
>> > > >>>
>> > > >>> http://i.imgur.com/cZ1pLun.png
>> > > >>> Somehow one of my VMs was assigned the IP address 192.168.128.118
>> > > >>> (outside of the range above).
>> > > >>>
>> > > >>> http://imgur.com/TeRMEf9
>> > > >>> The zone is using basic networking.
>> > > >>>
>> > > >>> The issue is in my VMware cluster (two hosts in this cluster).
>> > > >>>
>> > > >>> Thanks!
>> > > >>>
>> > > >>> --
>> > > >>> *Mike Tutkowski*
>> > > >>> *Senior CloudStack Developer, SolidFire Inc.*
>> > > >>> e: mike.tutkow...@solidfire.com
>> > > >>> o: 303.746.7302
>> > > >>> Advancing the way the world uses the cloud<
>> > > http://solidfire.com/solution/overview/?video=play>
>> > > >>> *™*
>> > > >>>
>> > > >>
>> > > >>
>> > > >>
>> > > >> --
>> > > >> *Mike Tutkowski*
>> > > >> *Senior CloudStack Developer, SolidFire Inc.*
>> > > >> e: mike.tutkow...@solidfire.com
>> > > >> o: 303.746.7302
>> > > >> Advancing the way the world uses the cloud<
>> > > http://solidfire.com/solution/overview/?video=play>
>> > > >> *™*
>> > > >>
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > *Mike Tutkowski*
>> > > > *Senior CloudStack Developer, SolidFire Inc.*
>> > > > e: mike.tutkow...@solidfire.com
>> > > > o: 303.746.7302
>> > > > Advancing the way the world uses the
>> > > > cloud
>> > > > *™*
>> > >
>> > >
>> >
>> >
>> > --
>> > *Mike Tutkowski*
>> > *Senior CloudStack Developer, SolidFire Inc.*
>> > e: mike.tutkow...@solidfire.com
>> > o: 303.746.7302
>> > Advancing the way the world uses the
>> > cloud
>> > *™*
>> >
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *™*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*™*

Release Managers for 4.3.1 and 4.4.0

[David Nalley]

Hi folks,

It's that time again - we are getting close to the end of the 4.3.0
cycle and we need to start identifying release managers for the next
patch and feature releases. Anyone want to step up and work on doing
this largely thankless task?

--David

RE: Release Managers for 4.3.1 and 4.4.0

[Edison Su]

Maybe before calling out another release manager, we better sit down and talk 
about is there anything we can improve for the release process. Seems it's huge 
mount of work to do as a release manager.

> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: Thursday, January 23, 2014 10:45 AM
> To: dev@cloudstack.apache.org
> Subject: Release Managers for 4.3.1 and 4.4.0
> 
> Hi folks,
> 
> It's that time again - we are getting close to the end of the 4.3.0 cycle and 
> we
> need to start identifying release managers for the next patch and feature
> releases. Anyone want to step up and work on doing this largely thankless
> task?
> 
> --David

RE: [VOTE] Apache CloudStack 4.3.0 (first round)

[Animesh Chaturvedi]

-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] 
Sent: Thursday, January 23, 2014 7:49 AM
To: dev
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (first round)

Animesh, I can see the commit id that you mention for this release, but it is a 
revert of a functional commit commented on as
'CLOUDSTACK-5923: CS doesn't do master switch for XS any more, CS will depend 
on XS HA to do master switch, XS HA needs to be enabled.'
[Animesh] Before pushing this RC I had worked on two of them internally and saw 
this commit made into the branch and asked it to be reverted just before I 
built this RC. So this ended up being the last commit.

Did you forget to push the RC branch? Or was it not created as you 
baked the release candidate?
[Animesh] Can you clarify? I was using the build_asf.sh script in 4.3 branch 
and it does not create a separate RC branch. I had already checked in the 
changes to pom.xml with my first attempt at RC which was never published

regards,
Daan

On Thu, Jan 23, 2014 at 3:42 PM, Srikanteswararao Talluri 
 wrote:
> +1
>
> I could successfully deploy an advanced zone with XenServer 6.2 - did 
> some basic testing around snapshots, templates and VPC.
>
> Thanks,
> ~Talluri
>
> On 23/01/14 7:06 pm, "Ove Ewerlid"  wrote:
>
>>The list of changes link indicates that the 4.3.0 release notes should 
>>be here;
>>   http://cloudstack.apache.org/docs
>>I'm not seeing any 4.3.0 related docs there.
>>is there some update that has not propagated to the apache web site 
>>yet ...
>>
>>/Ove
>>
>>-
>>
>>
>>Apache CloudStack CHANGES
>>==
>>
>>Full release notes for each release are located in the project's 
>>documentation website:
>>http://cloudstack.apache.org/docs
>>
>>Version 4.3.0
>>
>>Please refer to release notes for list of changes
>>
>>...
>>
>>On 01/23/2014 06:54 AM, Animesh Chaturvedi wrote:
>>>
>>>
>>>
>>> Hi All,
>>>
>>>
>>>
>>> I've created a 4.3.0 release, with the following artifacts up for a
>>>
>>> vote:
>>>
>>>
>>>
>>> Git Branch and Commit SH:
>>>
>>>
>>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h
>>>=ref
>>>s/heads/4.3
>>> Commit: 43d485c92d5919085cacb1cd0c7e78503ab9788a
>>>
>>>
>>>
>>> List of changes:
>>>
>>>
>>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain
>>>;f=C
>>>HANGES;hb=4.3
>>>
>>>
>>>
>>> Source release (checksums and signatures are available at the same
>>>
>>> location):
>>>
>>> https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
>>>
>>>
>>>
>>> PGP release keys (signed using 94BE0D7C):
>>>
>>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>>
>>>
>>>
>>> Testing instructions are here:
>>>
>>>
>>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+p
>>>roce
>>>dure
>>>
>>>
>>>
>>> Vote will be open for 72 hours.
>>>
>>>
>>>
>>> For sanity in tallying the vote, can PMC members please be sure to 
>>>indicate "(binding)" with their vote?
>>>
>>>
>>>
>>> [ ] +1  approve
>>>
>>> [ ] +0  no opinion
>>>
>>> [ ] -1  disapprove (and reason why)
>>>
>>>
>>>
>>>
>>
>>
>>--
>>Ove Everlid
>>System Administrator / Architect / SDN- & Automation- & Linux-hacker
>>Mobile: +46706662363 (dedicated work mobile)
>>Country: Sweden, timezone; Middle Europan Time (MET or GMT+1)
>

RE: [VOTE] Apache CloudStack 4.3.0 (first round)

[Animesh Chaturvedi]

Release Notes are still pending and they are not pushed with the RC build 
process, I am still waiting for a volunteer to take over the RN. I had called 
out for help on Release Notes two weeks back. 

I will create a JIRA filter for Known and Fixed issues today which can be put 
into Release Notes.

-Original Message-
From: Ove Ewerlid [mailto:ove.ewer...@oracle.com] 
Sent: Thursday, January 23, 2014 5:37 AM
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (first round)

The list of changes link indicates that the 4.3.0 release notes should be here;
   http://cloudstack.apache.org/docs
I'm not seeing any 4.3.0 related docs there.
is there some update that has not propagated to the apache web site yet ...

/Ove

-


Apache CloudStack CHANGES
==

Full release notes for each release are located in the project's documentation 
website:
http://cloudstack.apache.org/docs

Version 4.3.0

Please refer to release notes for list of changes

...

On 01/23/2014 06:54 AM, Animesh Chaturvedi wrote:
>
>
>
> Hi All,
>
>
>
> I've created a 4.3.0 release, with the following artifacts up for a
>
> vote:
>
>
>
> Git Branch and Commit SH:
>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=
> refs/heads/4.3
> Commit: 43d485c92d5919085cacb1cd0c7e78503ab9788a
>
>
>
> List of changes:
>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;
> f=CHANGES;hb=4.3
>
>
>
> Source release (checksums and signatures are available at the same
>
> location):
>
> https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
>
>
>
> PGP release keys (signed using 94BE0D7C):
>
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
>
>
> Testing instructions are here:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+pr
> ocedure
>
>
>
> Vote will be open for 72 hours.
>
>
>
> For sanity in tallying the vote, can PMC members please be sure to indicate 
> "(binding)" with their vote?
>
>
>
> [ ] +1  approve
>
> [ ] +0  no opinion
>
> [ ] -1  disapprove (and reason why)
>
>
>
>


--
Ove Everlid
System Administrator / Architect / SDN- & Automation- & Linux-hacker
Mobile: +46706662363 (dedicated work mobile)
Country: Sweden, timezone; Middle Europan Time (MET or GMT+1)

RE: [VOTE] Apache CloudStack 4.3.0 (first round)

[Animesh Chaturvedi]

Hugo 

Thanks for running find bugs and finding the issues let's wait for some more 
comments on the issues called out. Copying some folks for input.  It's always 
good to call out the issues but I wish we had run find bugs sooner.

Thanks
Animesh

-Original Message-
From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
Sent: Thursday, January 23, 2014 12:21 AM
To: dev
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (first round)

Thanks Animesh,

Great to see the first RC for 4.3.

I've been running some findbugs analysis on master and found several issues 
that also seem to be present in the 4.3 branch. I've made two commit on master 
that fixed some issues that i spotted (c2da2803476d55e814ec0d849482bd07c4f9f8f1 
and d19157fbb169eec029d1efee9ddd06e6b6aad9a4). Both fix an issue where an 
object is compared by using == instead of equals. I'm doubting if this is worth 
to -1 the current RC as i can't oversee the impact of these bugs and looking 
for opinions.

Cheers,

Hugo






On 23 jan. 2014, at 06:54, Animesh Chaturvedi  
wrote:

> 
> 
> 
> Hi All,
> 
> 
> 
> I've created a 4.3.0 release, with the following artifacts up for a
> 
> vote:
> 
> 
> 
> Git Branch and Commit SH:
> 
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
> Commit: 43d485c92d5919085cacb1cd0c7e78503ab9788a
> 
> 
> 
> List of changes:
> 
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.3
> 
> 
> 
> Source release (checksums and signatures are available at the same
> 
> location):
> 
> https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
> 
> 
> 
> PGP release keys (signed using 94BE0D7C):
> 
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> 
> 
> 
> Testing instructions are here:
> 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
> 
> 
> 
> Vote will be open for 72 hours.
> 
> 
> 
> For sanity in tallying the vote, can PMC members please be sure to indicate 
> "(binding)" with their vote?
> 
> 
> 
> [ ] +1  approve
> 
> [ ] +0  no opinion
> 
> [ ] -1  disapprove (and reason why)
> 
> 
> 

Re: [ISSUES] Master VMware is broken

[Kelven Yang]

Hugo,

The root cause of the problem comes from this line of change, it is very
subtle, but it indeed causes the problem

Method getMorMethod = dpCls.getDeclaredMethod(methodName, (Class)null);


There is a subtle difference between


Method getMorMethod = dpCls.getDeclaredMethod(methodName, (Class)null);


and 

Method getMorMethod = dpCls.getDeclaredMethod(methodName, null);

a plain null will direct Java to search for a method with no parameters,
but a casting of it (Class)null breaks the contract of
getDeclareMethod(String, Class…) since Class… is actually of type
Class[]

so if we really wants explicit typing, it should be written as


Method getMorMethod = dpCls.getDeclaredMethod(methodName,
(Class[])null);

Kelven





On 1/23/14, 9:16 AM, "Min Chen"  wrote:

>It failed in invoking addVmwareDC, where we will invoke vmware API to get
>CustomeField. Using java generics, class reflection failed in finding that
>declared method, thus throwing NoSuchMethodFound exception.
>
>Thanks
>-min
>
>On 1/22/14 10:52 PM, "Hugo Trippaers"  wrote:
>
>>Sorry about that :-(  Thanks for finding and fixing it.
>>
>>Where did you encounter the error? I wonder why i didn¹t catch it with my
>>tests against vmware.
>>
>>Cheers,
>>
>>Hugo
>>
>>On 23 jan. 2014, at 03:01, Min Chen  wrote:
>>
>>> FYI, I checked in a fix 206c35c620a8e7a707f371e5a9e5dfd795912f5b for
>>>this
>>> to unblock my testing.
>>> 
>>> Thanks
>>> -min
>>> 
>>> On 1/22/14 5:43 PM, "Kelven Yang"  wrote:
>>> 
 Master VMware was broken by this commit
 
 author  Hugo 
 
Trippaers
 

   Wed, 22 Jan 2014 08:34:46 + (09:34 +0100)
 committer   Hugo
 
Trippaers 
> 
>f
>?p
> 
>=cloudstack.git;a=search;h=b20add810e5751f53946f695b6223a8016f104a5;s=
>h
>tr
> ippa...@schubergphilis.com;st=committer>
   Wed, 22 Jan 2014 08:37:34 + (09:37 +0100)
 commit  b20add810e5751f53946f695b6223a8016f104a5
 tree
 
89e7e66704b09959bc5d77e4e20562e6dcc05306
 
tree | 
 
snapshot
 parent  
 
86124138a1a9129dedaf0f73fcd570156bfe53f6  
 
commit |
 
diff
 Get rid of compiler warnings in vmware-base
 
 Min and I spent two hours on this to trace down the cause,  Hugo,
please
 do test before check-in even if it seems like to remove compiler
warning,
 but because of the tricky business with Java generics, it does cause
 problem at runtime
 
 One of the problem comes from following code, please checkout my
comments
 below.
 
 -Kelven
 
 
 import org.apache.log4j.Logger;
 
 @@ 
 
-144,6 
 
+144,7 @@ public class VmwareClient {
ServiceContent serviceContent =
 vimPort.retrieveServiceContent(svcInstRef);
 
// Extract a cookie. See vmware

Re: [VOTE] Apache CloudStack 4.3.0 (first round)

[Animesh Chaturvedi]

Folks while we may need another RC but do provide your feedback on this one 
ASAP and don't wait for next RC. Respinning RC's is time consuming and can be 
frustrating and aearlier feedback and fixes goes a long way in making releases 
efficient.

Thanks
Animesh

On Jan 23, 2014, at 11:52 AM, "Animesh Chaturvedi" 
 wrote:

> Hugo 
> 
> Thanks for running find bugs and finding the issues let's wait for some more 
> comments on the issues called out. Copying some folks for input.  It's always 
> good to call out the issues but I wish we had run find bugs sooner.
> 
> Thanks
> Animesh
> 
> -Original Message-
> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> Sent: Thursday, January 23, 2014 12:21 AM
> To: dev
> Subject: Re: [VOTE] Apache CloudStack 4.3.0 (first round)
> 
> Thanks Animesh,
> 
> Great to see the first RC for 4.3.
> 
> I've been running some findbugs analysis on master and found several issues 
> that also seem to be present in the 4.3 branch. I've made two commit on 
> master that fixed some issues that i spotted 
> (c2da2803476d55e814ec0d849482bd07c4f9f8f1 and 
> d19157fbb169eec029d1efee9ddd06e6b6aad9a4). Both fix an issue where an object 
> is compared by using == instead of equals. I'm doubting if this is worth to 
> -1 the current RC as i can't oversee the impact of these bugs and looking for 
> opinions.
> 
> Cheers,
> 
> Hugo
> 
> 
> 
> 
> 
> 
> On 23 jan. 2014, at 06:54, Animesh Chaturvedi  
> wrote:
> 
>> 
>> 
>> 
>> Hi All,
>> 
>> 
>> 
>> I've created a 4.3.0 release, with the following artifacts up for a
>> 
>> vote:
>> 
>> 
>> 
>> Git Branch and Commit SH:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
>> Commit: 43d485c92d5919085cacb1cd0c7e78503ab9788a
>> 
>> 
>> 
>> List of changes:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.3
>> 
>> 
>> 
>> Source release (checksums and signatures are available at the same
>> 
>> location):
>> 
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
>> 
>> 
>> 
>> PGP release keys (signed using 94BE0D7C):
>> 
>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>> 
>> 
>> 
>> Testing instructions are here:
>> 
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
>> 
>> 
>> 
>> Vote will be open for 72 hours.
>> 
>> 
>> 
>> For sanity in tallying the vote, can PMC members please be sure to indicate 
>> "(binding)" with their vote?
>> 
>> 
>> 
>> [ ] +1  approve
>> 
>> [ ] +0  no opinion
>> 
>> [ ] -1  disapprove (and reason why)
> 

Re: Weird IP address allocation in 4.3

[Ahmad Emneina]

blasted vlans and the trunks they rhode in on! :) glad all is well.


On Thu, Jan 23, 2014 at 10:45 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> I asked one of our IT guys to look into this. He determined a port was in
> the wrong VLAN and that's how my VM got an IP address from a different DHCP
> server.
>
> No CloudStack issue here. :)
>
> Thanks
>
>
> On Wed, Jan 22, 2014 at 11:05 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> That is an interesting possibility. Thanks, guys
>>
>>
>> On Wed, Jan 22, 2014 at 10:59 PM, Ahmad Emneina wrote:
>>
>>> Mike, you might have another machine serving up DHCP on that network. If
>>> thats the case get it to ignore cloudstack assigned mac addresses (06
>>> prefix).
>>>
>>>
>>> On Wed, Jan 22, 2014 at 9:53 PM, Mike Tutkowski <
>>> mike.tutkow...@solidfire.com> wrote:
>>>
>>> > Hi Jayapal,
>>> >
>>> > That table has 8 rows and includes IP addresses from 192.168.128.23 to
>>> > 192.168.128.30 (which should be correct).
>>> >
>>> > Thanks
>>> >
>>> >
>>> > On Wed, Jan 22, 2014 at 10:49 PM, Jayapal Reddy Uradi <
>>> > jayapalreddy.ur...@citrix.com> wrote:
>>> >
>>> > > Hi Mike,
>>> > >
>>> > > Can you please check the db table user_ip_address to see what are
>>> the ips
>>> > > addresses are there.
>>> > > IP will be picked from this table.
>>> > >
>>> > > Thanks,
>>> > > Jayapal
>>> > >
>>> > > On 23-Jan-2014, at 10:35 AM, Mike Tutkowski <
>>> > mike.tutkow...@solidfire.com>
>>> > > wrote:
>>> > >
>>> > > > Slight correction (this may have been obvious from one of my screen
>>> > > shots):
>>> > > > The VM with the address outside of the range I gave to CloudStack
>>> is
>>> > in a
>>> > > > XenServer cluster.
>>> > > >
>>> > > >
>>> > > > On Wed, Jan 22, 2014 at 10:03 PM, Mike Tutkowski <
>>> > > > mike.tutkow...@solidfire.com> wrote:
>>> > > >
>>> > > >> The IP address that CloudStack says is assigned to VM i-2-11-VM
>>> > > >> (192.168.128.28) does not appear to be assigned to any VM in the
>>> > system
>>> > > >> (user or system VM).
>>> > > >>
>>> > > >>
>>> > > >> On Wed, Jan 22, 2014 at 9:59 PM, Mike Tutkowski <
>>> > > >> mike.tutkow...@solidfire.com> wrote:
>>> > > >>
>>> > > >>> Hi,
>>> > > >>>
>>> > > >>> I was wondering if someone who deals with networking in
>>> CloudStack
>>> > > might
>>> > > >>> know something about this.
>>> > > >>>
>>> > > >>> I have a development setup with one zone, one pod, and three
>>> clusters
>>> > > >>> (one VMware, one XenServer, and one KVM).
>>> > > >>>
>>> > > >>> The IP addresses I've given to CloudStack span from
>>> 192.168.128.20 to
>>> > > >>> 192.168.128.30 (just 11 addresses).
>>> > > >>>
>>> > > >>> http://i.imgur.com/3SAn98W.png
>>> > > >>>
>>> > > >>> http://i.imgur.com/cZ1pLun.png
>>> > > >>> Somehow one of my VMs was assigned the IP address 192.168.128.118
>>> > > >>> (outside of the range above).
>>> > > >>>
>>> > > >>> http://imgur.com/TeRMEf9
>>> > > >>> The zone is using basic networking.
>>> > > >>>
>>> > > >>> The issue is in my VMware cluster (two hosts in this cluster).
>>> > > >>>
>>> > > >>> Thanks!
>>> > > >>>
>>> > > >>> --
>>> > > >>> *Mike Tutkowski*
>>> > > >>> *Senior CloudStack Developer, SolidFire Inc.*
>>> > > >>> e: mike.tutkow...@solidfire.com
>>> > > >>> o: 303.746.7302
>>> > > >>> Advancing the way the world uses the cloud<
>>> > > http://solidfire.com/solution/overview/?video=play>
>>> > > >>> *™*
>>> > > >>>
>>> > > >>
>>> > > >>
>>> > > >>
>>> > > >> --
>>> > > >> *Mike Tutkowski*
>>> > > >> *Senior CloudStack Developer, SolidFire Inc.*
>>> > > >> e: mike.tutkow...@solidfire.com
>>> > > >> o: 303.746.7302
>>> > > >> Advancing the way the world uses the cloud<
>>> > > http://solidfire.com/solution/overview/?video=play>
>>> > > >> *™*
>>> > > >>
>>> > > >
>>> > > >
>>> > > >
>>> > > > --
>>> > > > *Mike Tutkowski*
>>> > > > *Senior CloudStack Developer, SolidFire Inc.*
>>> > > > e: mike.tutkow...@solidfire.com
>>> > > > o: 303.746.7302
>>> > > > Advancing the way the world uses the
>>> > > > cloud
>>> > > > *™*
>>> > >
>>> > >
>>> >
>>> >
>>> > --
>>> > *Mike Tutkowski*
>>> > *Senior CloudStack Developer, SolidFire Inc.*
>>> > e: mike.tutkow...@solidfire.com
>>> > o: 303.746.7302
>>> > Advancing the way the world uses the
>>> > cloud
>>> > *™*
>>> >
>>>
>>
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkow...@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the 
>> cloud
>> *™*
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *™*
>

Re: [VOTE] Apache CloudStack 4.3.0 (first round)

[Sheng Yang]

I think the issue Hugo fixed should trigger another RC. But still, we need
to test as much as we can for current RC now. It would make the release
work easier.

--Sheng


On Thu, Jan 23, 2014 at 11:51 AM, Animesh Chaturvedi <
animesh.chaturv...@citrix.com> wrote:

> Hugo
>
> Thanks for running find bugs and finding the issues let's wait for some
> more comments on the issues called out. Copying some folks for input.  It's
> always good to call out the issues but I wish we had run find bugs sooner.
>
> Thanks
> Animesh
>
> -Original Message-
> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> Sent: Thursday, January 23, 2014 12:21 AM
> To: dev
> Subject: Re: [VOTE] Apache CloudStack 4.3.0 (first round)
>
> Thanks Animesh,
>
> Great to see the first RC for 4.3.
>
> I've been running some findbugs analysis on master and found several
> issues that also seem to be present in the 4.3 branch. I've made two commit
> on master that fixed some issues that i spotted
> (c2da2803476d55e814ec0d849482bd07c4f9f8f1 and
> d19157fbb169eec029d1efee9ddd06e6b6aad9a4). Both fix an issue where an
> object is compared by using == instead of equals. I'm doubting if this is
> worth to -1 the current RC as i can't oversee the impact of these bugs and
> looking for opinions.
>
> Cheers,
>
> Hugo
>
>
>
>
>
>
> On 23 jan. 2014, at 06:54, Animesh Chaturvedi <
> animesh.chaturv...@citrix.com> wrote:
>
> >
> >
> >
> > Hi All,
> >
> >
> >
> > I've created a 4.3.0 release, with the following artifacts up for a
> >
> > vote:
> >
> >
> >
> > Git Branch and Commit SH:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
> > Commit: 43d485c92d5919085cacb1cd0c7e78503ab9788a
> >
> >
> >
> > List of changes:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.3
> >
> >
> >
> > Source release (checksums and signatures are available at the same
> >
> > location):
> >
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
> >
> >
> >
> > PGP release keys (signed using 94BE0D7C):
> >
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> >
> >
> > Testing instructions are here:
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
> >
> >
> >
> > Vote will be open for 72 hours.
> >
> >
> >
> > For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
> >
> >
> >
> > [ ] +1  approve
> >
> > [ ] +0  no opinion
> >
> > [ ] -1  disapprove (and reason why)
> >
> >
> >
>
>

Re: Master build failing with LICENSE error

[Alena Prokharchyk]

Guys, if anyone knows the workaround for the problem, please share in the
thread. I¹m pretty much blocked on master branch by this issue.

=Alena.

On 1/22/14, 6:03 PM, "Nitin Mehta"  wrote:

>I am seeing this as well.
>
>On 22/01/14 4:43 PM, "Alena Prokharchyk" 
>wrote:
>
>>I am seeing it too.
>>
>>On 1/22/14, 3:23 PM, "Rayees Namathponnan"
>> wrote:
>>
>>>Master build failing with below error, any one faced this?
>>>
>>>
>>>[ERROR] Failed to execute goal com.mycila:license-maven-plugin:2.5:check
>>>(cloudstack-checklicence) on project cloud-plugin-network-nvp: Resource
>>>LICENSE.header   not found in file system, classpath or URL: no
>>>protocol:
>>>LICENSE.header -> [Help   1]
>>>[ERROR]
>>>[ERROR] To see the full stack trace of the errors, re-run Maven with the
>>>-e switch.
>>>[ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>>[ERROR]
>>>[ERROR] For more information about the errors and possible solutions,
>>>please read the following articles:
>>>[ERROR] [Help 1]
>>>http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>>[ERROR]
>>>[ERROR] After correcting the problems, you can resume the build with the
>>>command
>>>[ERROR]   mvn  -rf :cloud-plugin-network-nvp
>>>
>>>
>>>
>>>Regards,
>>>Rayees
>>
>

Re: [ISSUES] Master VMware is broken

[Kelven Yang]

To be exact, line

Method getMorMethod = dpCls.getDeclaredMethod(methodName, 
(Class)null);


will be translated by compiler as

Method getMorMethod = dpCls.getDeclaredMethod(methodName, new Class[] {
null } );


line 

Method getMorMethod = dpCls.getDeclaredMethod(methodName,
(Class[])null); and
Method getMorMethod = dpCls.getDeclaredMethod(methodName, null);

will be translated by compiler as
 
Method getMorMethod = dpCls.getDeclaredMethod(methodName, null);

Kelven





On 1/23/14, 11:54 AM, "Kelven Yang"  wrote:

>Hugo,
>
>The root cause of the problem comes from this line of change, it is very
>subtle, but it indeed causes the problem
>
>Method getMorMethod = dpCls.getDeclaredMethod(methodName, (Class)null);
>
>
>There is a subtle difference between
>
>
>Method getMorMethod = dpCls.getDeclaredMethod(methodName, (Class)null);
>
>
>and 
>
>Method getMorMethod = dpCls.getDeclaredMethod(methodName, null);
>
>a plain null will direct Java to search for a method with no parameters,
>but a casting of it (Class)null breaks the contract of
>getDeclareMethod(String, Class…) since Class… is actually of type
>Class[]
>
>so if we really wants explicit typing, it should be written as
>
>
>Method getMorMethod = dpCls.getDeclaredMethod(methodName,
>(Class[])null);
>
>Kelven
>
>
>
>
>
>On 1/23/14, 9:16 AM, "Min Chen"  wrote:
>
>>It failed in invoking addVmwareDC, where we will invoke vmware API to get
>>CustomeField. Using java generics, class reflection failed in finding
>>that
>>declared method, thus throwing NoSuchMethodFound exception.
>>
>>Thanks
>>-min
>>
>>On 1/22/14 10:52 PM, "Hugo Trippaers"  wrote:
>>
>>>Sorry about that :-(  Thanks for finding and fixing it.
>>>
>>>Where did you encounter the error? I wonder why i didn¹t catch it with
>>>my
>>>tests against vmware.
>>>
>>>Cheers,
>>>
>>>Hugo
>>>
>>>On 23 jan. 2014, at 03:01, Min Chen  wrote:
>>>
 FYI, I checked in a fix 206c35c620a8e7a707f371e5a9e5dfd795912f5b for
this
 to unblock my testing.
 
 Thanks
 -min
 
 On 1/22/14 5:43 PM, "Kelven Yang"  wrote:
 
> Master VMware was broken by this commit
> 
> author  Hugo 
> 
>Trippaerse
>a
>rc
> 
>h;h=b20add810e5751f53946f695b6223a8016f104a5;s=Hugo+Trippaers;st=autho
>r
>>
> 
>f
>?
>p=
> 
>cloudstack.git;a=search;h=b20add810e5751f53946f695b6223a8016f104a5;s=h
>t
>r
>ip
> pa...@schubergphilis.com;st=author>
>   Wed, 22 Jan 2014 08:34:46 + (09:34 +0100)
> committer   Hugo
> 
>Trippaerse
>a
>rc
> 
>h;h=b20add810e5751f53946f695b6223a8016f104a5;s=Hugo+Trippaers;st=commi
>t
>t
>er
>> 
>> 
>>>s
>>f
>>?p
>> 
>>=cloudstack.git;a=search;h=b20add810e5751f53946f695b6223a8016f104a5;s
>>=
>>h
>>tr
>> ippa...@schubergphilis.com;st=committer>
>   Wed, 22 Jan 2014 08:37:34 + (09:37 +0100)
> commit  b20add810e5751f53946f695b6223a8016f104a5
> tree
> 
>89e7e66704b09959bc5d77e4e20562e6dcc05306/
>r
>ep
> 
>os/asf?p=cloudstack.git;a=tree;h=89e7e66704b09959bc5d77e4e20562e6dcc05
>3
>0
>6;
> hb=b20add810e5751f53946f695b6223a8016f104a5>
> 
>tree=
>8
>9e
> 
>7e66704b09959bc5d77e4e20562e6dcc05306;hb=b20add810e5751f53946f695b6223
>a
>8
>01
> 6f104a5> | 
> 
>snapshota
>p
>sh
> ot;h=b20add810e5751f53946f695b6223a8016f104a5;sf=tgz>
> parent  
> 
>86124138a1a9129dedaf0f73fcd570156bfe53f6/
>r
>ep
> 
>os/asf?p=cloudstack.git;a=commit;h=86124138a1a9129dedaf0f73fcd570156bf
>e
>5
>3f
> 6>  
> 
>commiti
>t
>;h
> =86124138a1a9129dedaf0f73fcd570156bfe53f6> |
> 
>diffd
>i
>ff
> 
>;h=b20add810e5751f53946f695b6223a8016f104a5;hp=86124138a1a9129dedaf0f7
>3
>f
>cd
> 570156bfe53f6>
> Get rid of compiler warnings in vmware-base
> 
> Min and I spent two hours on this to trace down the cause,  Hugo,
>please
> do test before check-in even if it seems like to remove compiler
>warning,
> but because of the tricky business with Java generics, it does cause
> problem at runtime
> 
> One of the problem comes from following code, please checkout my
>comments
> below.
> 
> -

RE: XS master handling in 4.3.0

[Animesh Chaturvedi]

That change was reverted and is not in 4.3.0 so the behavior will be the same 
as 4.2.1

-Original Message-
From: Francois Gaudreault [mailto:fgaudrea...@cloudops.com] 
Sent: Thursday, January 23, 2014 7:57 AM
To: dev@cloudstack.apache.org
Subject: XS master handling in 4.3.0

Quick question...

In the 4.3.0 vote thread, I saw this ticket:

CLOUDSTACK-5923

OK fine, but what happens if we are running 4.2.1 with a cluster today? Should 
we enable HA today or only when we upgrade to 4.3?

Thanks!

--
Francois Gaudreault
Architecte de Solution Cloud | Cloud Solutions Architect 
fgaudrea...@cloudops.com
514-629-6775
- - -
CloudOps
420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_

RE: XS master handling in 4.3.0

[Anthony Xu]

The patch will be in next release, XS HA can be enabled only after upgrading to 
the CS release including this patch.
We will provide document in the next CS release.


Anthony

-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
Sent: Thursday, January 23, 2014 3:41 PM
To: dev@cloudstack.apache.org; fgaudrea...@cloudops.com
Subject: RE: XS master handling in 4.3.0

That change was reverted and is not in 4.3.0 so the behavior will be the same 
as 4.2.1

-Original Message-
From: Francois Gaudreault [mailto:fgaudrea...@cloudops.com] 
Sent: Thursday, January 23, 2014 7:57 AM
To: dev@cloudstack.apache.org
Subject: XS master handling in 4.3.0

Quick question...

In the 4.3.0 vote thread, I saw this ticket:

CLOUDSTACK-5923

OK fine, but what happens if we are running 4.2.1 with a cluster today? Should 
we enable HA today or only when we upgrade to 4.3?

Thanks!

--
Francois Gaudreault
Architecte de Solution Cloud | Cloud Solutions Architect 
fgaudrea...@cloudops.com
514-629-6775
- - -
CloudOps
420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_

CloudStack Admin Latency

[Maurice Lawler]

Hello,

Is anyone else experiencing a delay when traveling to their admin page?

Seems as though mine takes 45 seconds roughly to render.

Prior installs rendered much faster.

- Maurice

Re: Master build failing with LICENSE error

[Nitin Mehta]

Hi Alena,
I just moved some commits back (to commit 8612413) and its working fine at
the moment with no db changes required. So probably to unblock yourself
you can try doing that.

Thanks,
-Nitin

On 23/01/14 2:48 PM, "Alena Prokharchyk" 
wrote:

>Guys, if anyone knows the workaround for the problem, please share in the
>thread. I¹m pretty much blocked on master branch by this issue.
>
>=Alena.
>
>On 1/22/14, 6:03 PM, "Nitin Mehta"  wrote:
>
>>I am seeing this as well.
>>
>>On 22/01/14 4:43 PM, "Alena Prokharchyk" 
>>wrote:
>>
>>>I am seeing it too.
>>>
>>>On 1/22/14, 3:23 PM, "Rayees Namathponnan"
>>> wrote:
>>>
Master build failing with below error, any one faced this?


[ERROR] Failed to execute goal
com.mycila:license-maven-plugin:2.5:check
(cloudstack-checklicence) on project cloud-plugin-network-nvp: Resource
LICENSE.header   not found in file system, classpath or URL: no
protocol:
LICENSE.header -> [Help
1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with
the
command
[ERROR]   mvn  -rf :cloud-plugin-network-nvp



Regards,
Rayees
>>>
>>
>

Re: Master build failing with LICENSE error

[Animesh Chaturvedi]

If you know the offending commit revert it for now. It's broken for a day.

Thanks
Animesh

On Jan 23, 2014, at 5:12 PM, "Nitin Mehta"  wrote:

> Hi Alena,
> I just moved some commits back (to commit 8612413) and its working fine at
> the moment with no db changes required. So probably to unblock yourself
> you can try doing that.
> 
> Thanks,
> -Nitin
> 
> On 23/01/14 2:48 PM, "Alena Prokharchyk" 
> wrote:
> 
>> Guys, if anyone knows the workaround for the problem, please share in the
>> thread. I¹m pretty much blocked on master branch by this issue.
>> 
>> =Alena.
>> 
>> On 1/22/14, 6:03 PM, "Nitin Mehta"  wrote:
>> 
>>> I am seeing this as well.
>>> 
>>> On 22/01/14 4:43 PM, "Alena Prokharchyk" 
>>> wrote:
>>> 
 I am seeing it too.
 
 On 1/22/14, 3:23 PM, "Rayees Namathponnan"
  wrote:
 
> Master build failing with below error, any one faced this?
> 
> 
> [ERROR] Failed to execute goal
> com.mycila:license-maven-plugin:2.5:check
> (cloudstack-checklicence) on project cloud-plugin-network-nvp: Resource
> LICENSE.header   not found in file system, classpath or URL: no
> protocol:
> LICENSE.header -> [Help
> 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with
> the
> command
> [ERROR]   mvn  -rf :cloud-plugin-network-nvp
> 
> 
> 
> Regards,
> Rayees
> 

Re: CloudStack Admin Latency

[David Nalley]

Are you talking about when you first visit http://:8080/client ??
If so as Marcus has previously pointed out its the css and images
loading, which is used throughout the UI. And it's a number of
megabytes. There was a proposal to gzip that up but not sure what
happened with it.

--David

On Thu, Jan 23, 2014 at 7:29 PM, Maurice Lawler  wrote:
> Hello,
>
> Is anyone else experiencing a delay when traveling to their admin page?
>
> Seems as though mine takes 45 seconds roughly to render.
>
> Prior installs rendered much faster.
>
> - Maurice

Re: Master build failing with LICENSE error

[David Nalley]

On Thu, Jan 23, 2014 at 8:39 PM, Animesh Chaturvedi
 wrote:
> If you know the offending commit revert it for now. It's broken for a day.
>


Agreed - revert and lets move on.

--David

Re: CloudStack Admin Latency

[Maurice Lawler]

David,

Thank you, that's exactly, what I am referring to. I have noticed each 
time I go in the latency is present, I suspect one will just need to 
deal with it until perhaps a future update?


- Maurice
On 1/23/14, 9:49 PM, David Nalley wrote:

Are you talking about when you first visit http://:8080/client ??
If so as Marcus has previously pointed out its the css and images
loading, which is used throughout the UI. And it's a number of
megabytes. There was a proposal to gzip that up but not sure what
happened with it.

--David

On Thu, Jan 23, 2014 at 7:29 PM, Maurice Lawler  wrote:

Hello,

Is anyone else experiencing a delay when traveling to their admin page?

Seems as though mine takes 45 seconds roughly to render.

Prior installs rendered much faster.

- Maurice

Re: CloudStack Admin Latency

[David Nalley]

On Thu, Jan 23, 2014 at 10:20 PM, Maurice Lawler  wrote:
> David,
>
> Thank you, that's exactly, what I am referring to. I have noticed each time
> I go in the latency is present, I suspect one will just need to deal with it
> until perhaps a future update?
>
> - Maurice
>

I seem to have wrongly attributed this. It seems to be from Lazslo.
You can take a look at the review/comments/discussion here.

https://reviews.apache.org/r/12228/

There doesn't yet seem to be a bug filed for this, so perhaps that is
worthwhile as well.

--David

Re: [VOTE] Apache CloudStack 4.3.0 (first round)

[Animesh Chaturvedi]

Hugo can you put needed commits in 4.3-forward and I will rebuild the RC.



Thanks
Animesh

On Jan 23, 2014, at 5:33 AM, "Hugo Trippaers"  wrote:

> Thanks Abhi. I think that means that we need to consider this a mine and 
> needs fixing. 
> 
> Unfortunately that means a -1 on the current RC, but i hope people will 
> continue testing this RC so we get some more feedback.
> 
> 
> 
> 
> Cheers,
> 
> Hugo
> 
> 
> 
> 
> On 23 jan. 2014, at 10:16, Abhinandan Prateek  
> wrote:
> 
>> Long values till at least 128 are cached, the ref being same, the ==
>> operator is guaranteed to work for values from -127 to 128.
>> It the value can go beyond that range then this is a potential mine.
>> 
>> -abhi
>> 
>> On 23/01/14 1:51 pm, "Hugo Trippaers"  wrote:
>> 
>>> Thanks Animesh,
>>> 
>>> Great to see the first RC for 4.3.
>>> 
>>> I¹ve been running some findbugs analysis on master and found several
>>> issues that also seem to be present in the 4.3 branch. I¹ve made two
>>> commit on master that fixed some issues that i spotted
>>> (c2da2803476d55e814ec0d849482bd07c4f9f8f1 and
>>> d19157fbb169eec029d1efee9ddd06e6b6aad9a4). Both fix an issue where an
>>> object is compared by using == instead of equals. I¹m doubting if this is
>>> worth to -1 the current RC as i can¹t oversee the impact of these bugs
>>> and looking for opinions.
>>> 
>>> Cheers,
>>> 
>>> Hugo
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On 23 jan. 2014, at 06:54, Animesh Chaturvedi
>>>  wrote:
>>> 
 
 
 
 Hi All,
 
 
 
 I've created a 4.3.0 release, with the following artifacts up for a
 
 vote:
 
 
 
 Git Branch and Commit SH:
 
 
 https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=ref
 s/heads/4.3
 Commit: 43d485c92d5919085cacb1cd0c7e78503ab9788a
 
 
 
 List of changes:
 
 
 https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=C
 HANGES;hb=4.3
 
 
 
 Source release (checksums and signatures are available at the same
 
 location):
 
 https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
 
 
 
 PGP release keys (signed using 94BE0D7C):
 
 https://dist.apache.org/repos/dist/release/cloudstack/KEYS
 
 
 
 Testing instructions are here:
 
 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+proce
 dure
 
 
 
 Vote will be open for 72 hours.
 
 
 
 For sanity in tallying the vote, can PMC members please be sure to
 indicate "(binding)" with their vote?
 
 
 
 [ ] +1  approve
 
 [ ] +0  no opinion
 
 [ ] -1  disapprove (and reason why)
> 

CentOS 6.5 | KVM | Cloudstack 4.2

[Maurice Lawler]

Hello,

I am setting up KVM / Cloudstack all under one server. I have done this 
countless of other times, however, this time on a new server I have 
noticed it did not provision cloudbr0 / cloud0 as it has done in the past.


I saw a few tutorials where it says to setup VLANS ifcfg-eth0.100-300 
which I understand. However, right now I am not sure if this is the 
normal for 4.2 to not have those two previously mentioned interfaces 
already setup when you issue the command setup-management / 
setup-databases as it has done before.


Can someone explain this to me?

- Maurice

Re: [ANNOUNCE] Switch to Java 7 in master branch on Monday Jan 27th 2014

[Abhinandan Prateek]

+1, I will update the system vm template scripts to pick up jre 1.7.

-abhi

On 23/01/14 8:56 pm, "Rajesh Battala"  wrote:

>+1. 
>
>-Original Message-
>From: Wido den Hollander [mailto:w...@widodh.nl]
>Sent: Thursday, January 23, 2014 4:19 PM
>To: dev@cloudstack.apache.org
>Subject: [ANNOUNCE] Switch to Java 7 in master branch on Monday Jan 27th
>2014
>
>Hi,
>
>We had multiple threads discussing the switch to Java 7 which all ended
>in +1 everywhere.
>
>The most recent [0] one is from the beginning of this month and since
>nobody actually took the step I'll do it.
>
>On 27-01-2014 11:00:00 CET / GMT +1 I'll push a commit where on the
>pom.xml cs.jdk.version will be set to 1.7.
>
>I'll also update the Debian and RPM packaging to only depend on Java 7
>packages and no longer on Java 6.
>
>Without any objections I'll continue with this on the date specified
>above.
>
>Wido
>
>[0]: 
>http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201401.mbox/%3CCEF
>079AF.5E3AB%25kelven.yang%40citrix.com%3E

Re: CentOS 6.5 | KVM | Cloudstack 4.2

[Marcus Sorensen]

I've always setup cloudbr0 (pub/mgt/guest br) per the documented examples,
and never cloud0 (link local bridge). You can look at the devcloud-kvm doc
for an example of an all-in-one. The traffic labels reference bridges, so
you have to have a bridge to enter as a traffic label in the first place.
If you don't provide traffic labels, it by default looks for cloudbr0 for
public and cloudbr1 for guest and private.

Looking through the code, it looks as though if you stick with an
'untagged' public network (enter no vlan id in your public range), then
you're required to create the bridge yourself, matcing the traffic label
you enter. If you enter a vlan id, then it will create the public bridge
for you, but you still have to identify where you want the bridge to be
created via traffic label. e.g. say you have only cloudbr0, which is your
mgmt bridge, and you want vlan 460 on that same eth device to be public
traffic. You'd enter 460 as the vlan id when entering the public traffic
range, and set the traffic label to 'cloudbr0', to identify where the vlan
460 bridge should be created. it then looks up the physical interface that
cloudbr0 is bridged to (eth0), creates a tagged interface (eth0.460), and a
bridge (breth0-460).

For private traffic (mgmt), it expects you to have already created the
bridge. I believe this is most likely because they expect this to be how
you're reaching the server in the first place (via ssh on mgmt net). Guest
networks are always dynamically created.
On Jan 23, 2014 9:11 PM, "Maurice Lawler"  wrote:

> Hello,
>
> I am setting up KVM / Cloudstack all under one server. I have done this
> countless of other times, however, this time on a new server I have noticed
> it did not provision cloudbr0 / cloud0 as it has done in the past.
>
> I saw a few tutorials where it says to setup VLANS ifcfg-eth0.100-300
> which I understand. However, right now I am not sure if this is the normal
> for 4.2 to not have those two previously mentioned interfaces already setup
> when you issue the command setup-management / setup-databases as it has
> done before.
>
> Can someone explain this to me?
>
> - Maurice
>

RE: [ANNOUNCE] Switch to Java 7 in master branch on Monday Jan 27th 2014

[Rajesh Battala]

Abhi, 
If we switch to jre1.7 for systemvm, we need to generate new systemvm for all 
the Hypervisors.
Will this be for 4.4 and forward only right? It won't be in 4.3.

Thanks
Rajesh Battala

-Original Message-
From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com] 
Sent: Friday, January 24, 2014 9:53 AM
To: dev@cloudstack.apache.org
Subject: Re: [ANNOUNCE] Switch to Java 7 in master branch on Monday Jan 27th 
2014

+1, I will update the system vm template scripts to pick up jre 1.7.

-abhi

On 23/01/14 8:56 pm, "Rajesh Battala"  wrote:

>+1. 
>
>-Original Message-
>From: Wido den Hollander [mailto:w...@widodh.nl]
>Sent: Thursday, January 23, 2014 4:19 PM
>To: dev@cloudstack.apache.org
>Subject: [ANNOUNCE] Switch to Java 7 in master branch on Monday Jan 
>27th
>2014
>
>Hi,
>
>We had multiple threads discussing the switch to Java 7 which all ended 
>in +1 everywhere.
>
>The most recent [0] one is from the beginning of this month and since 
>nobody actually took the step I'll do it.
>
>On 27-01-2014 11:00:00 CET / GMT +1 I'll push a commit where on the 
>pom.xml cs.jdk.version will be set to 1.7.
>
>I'll also update the Debian and RPM packaging to only depend on Java 7 
>packages and no longer on Java 6.
>
>Without any objections I'll continue with this on the date specified 
>above.
>
>Wido
>
>[0]: 
>http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201401.mbox/%3C
>CEF 079AF.5E3AB%25kelven.yang%40citrix.com%3E

Re:[SOLVED] Weird IP address allocation in 4.3

[Jayapal Reddy Uradi]

+users

On 24-Jan-2014, at 2:38 AM, Ahmad Emneina  wrote:

> blasted vlans and the trunks they rhode in on! :) glad all is well.
> 
> 
> On Thu, Jan 23, 2014 at 10:45 AM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
> 
>> I asked one of our IT guys to look into this. He determined a port was in
>> the wrong VLAN and that's how my VM got an IP address from a different DHCP
>> server.
>> 
>> No CloudStack issue here. :)
>> 
>> Thanks
>> 
>> 
>> On Wed, Jan 22, 2014 at 11:05 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>> 
>>> That is an interesting possibility. Thanks, guys
>>> 
>>> 
>>> On Wed, Jan 22, 2014 at 10:59 PM, Ahmad Emneina wrote:
>>> 
 Mike, you might have another machine serving up DHCP on that network. If
 thats the case get it to ignore cloudstack assigned mac addresses (06
 prefix).
 
 
 On Wed, Jan 22, 2014 at 9:53 PM, Mike Tutkowski <
 mike.tutkow...@solidfire.com> wrote:
 
> Hi Jayapal,
> 
> That table has 8 rows and includes IP addresses from 192.168.128.23 to
> 192.168.128.30 (which should be correct).
> 
> Thanks
> 
> 
> On Wed, Jan 22, 2014 at 10:49 PM, Jayapal Reddy Uradi <
> jayapalreddy.ur...@citrix.com> wrote:
> 
>> Hi Mike,
>> 
>> Can you please check the db table user_ip_address to see what are
 the ips
>> addresses are there.
>> IP will be picked from this table.
>> 
>> Thanks,
>> Jayapal
>> 
>> On 23-Jan-2014, at 10:35 AM, Mike Tutkowski <
> mike.tutkow...@solidfire.com>
>> wrote:
>> 
>>> Slight correction (this may have been obvious from one of my screen
>> shots):
>>> The VM with the address outside of the range I gave to CloudStack
 is
> in a
>>> XenServer cluster.
>>> 
>>> 
>>> On Wed, Jan 22, 2014 at 10:03 PM, Mike Tutkowski <
>>> mike.tutkow...@solidfire.com> wrote:
>>> 
 The IP address that CloudStack says is assigned to VM i-2-11-VM
 (192.168.128.28) does not appear to be assigned to any VM in the
> system
 (user or system VM).
 
 
 On Wed, Jan 22, 2014 at 9:59 PM, Mike Tutkowski <
 mike.tutkow...@solidfire.com> wrote:
 
> Hi,
> 
> I was wondering if someone who deals with networking in
 CloudStack
>> might
> know something about this.
> 
> I have a development setup with one zone, one pod, and three
 clusters
> (one VMware, one XenServer, and one KVM).
> 
> The IP addresses I've given to CloudStack span from
 192.168.128.20 to
> 192.168.128.30 (just 11 addresses).
> 
> http://i.imgur.com/3SAn98W.png
> 
> http://i.imgur.com/cZ1pLun.png
> Somehow one of my VMs was assigned the IP address 192.168.128.118
> (outside of the range above).
> 
> http://imgur.com/TeRMEf9
> The zone is using basic networking.
> 
> The issue is in my VMware cluster (two hosts in this cluster).
> 
> Thanks!
> 
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud<
>> http://solidfire.com/solution/overview/?video=play>
> *™*
> 
 
 
 
 --
 *Mike Tutkowski*
 *Senior CloudStack Developer, SolidFire Inc.*
 e: mike.tutkow...@solidfire.com
 o: 303.746.7302
 Advancing the way the world uses the cloud<
>> http://solidfire.com/solution/overview/?video=play>
 *™*
 
>>> 
>>> 
>>> 
>>> --
>>> *Mike Tutkowski*
>>> *Senior CloudStack Developer, SolidFire Inc.*
>>> e: mike.tutkow...@solidfire.com
>>> o: 303.746.7302
>>> Advancing the way the world uses the
>>> cloud
>>> *™*
>> 
>> 
> 
> 
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *™*
> 
 
>>> 
>>> 
>>> 
>>> --
>>> *Mike Tutkowski*
>>> *Senior CloudStack Developer, SolidFire Inc.*
>>> e: mike.tutkow...@solidfire.com
>>> o: 303.746.7302
>>> Advancing the way the world uses the 
>>> cloud
>>> *™*
>>> 
>> 
>> 
>> 
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkow...@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the 
>> cloud
>> *™*
>> 

Re: Review Request 14124: CLOUDSTACK-4622 : If a VM from guest network is added to network tier of VPC then IP reservation allows the CIDR to be a superset of Network CIDR for that VPC tier

[Jayapal Reddy]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14124/#review32472
---


Can you please run marvin test cases of VPC with this patch and update the 
testing done section

- Jayapal Reddy


On Jan. 7, 2014, 11:58 a.m., Saksham Srivastava wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/14124/
> ---
> 
> (Updated Jan. 7, 2014, 11:58 a.m.)
> 
> 
> Review request for cloudstack, Jayapal Reddy and Sateesh Chodapuneedi.
> 
> 
> Bugs: CLOUDSTACK-4622
> https://issues.apache.org/jira/browse/CLOUDSTACK-4622
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Add a new utility method for comparing 2 CIDRs.
> The method takes in 2 cidrs, cidrA and cidrB and returns true if cidrA's IP 
> range is equal or a subset of cidrB's IP range.
> 
> 
> Diffs
> -
> 
>   utils/src/com/cloud/utils/net/NetUtils.java 266a5d1 
>   utils/test/com/cloud/utils/net/NetUtilsTest.java b049516 
> 
> Diff: https://reviews.apache.org/r/14124/diff/
> 
> 
> Testing
> ---
> 
> Added unit test for the utility.
> Tested locally.
> Build is successful.
> Patch applies cleanly.
> 
> 
> Thanks,
> 
> Saksham Srivastava
> 
>

Re: Create GRE tunnel failed in 4.2 with XenServer.

[Murali Reddy]

On 23/01/14 5:48 PM, "Florin Dumitrascu"
 wrote:

>Hi Murali, Tuna,
>
>Thank you for this piece of information. All starts to make sense now.
>I am wondering if there is a better way to communicate this issue to end
>users. It would save others a couple of weeks struggling.
>If GRE is not just a technology preview (meaning it has been explicitly
>mentioned in previous release notes), the known issues lists for 4.2.0
>and 4.2.1 should be explicitly updated.
>
>Leaving 4.2 behind now, which will be the first release to include GRE
>refactoring with OVS service provider ?

Ideally Tuna's fix (to make OVS as Connectivity service provider) should
have gone into 4.2.1. Looks like they did not go into 4.2.1

Tuna,

Can you please ensure your fixes (excluding support for KVM/XCP) went into
4.2, 4.3 branches as well.

Thanks,
Murali

>
>Regards,
>Florin
>
>-Original Message-
>From: ng.t...@gmail.com [mailto:ng.t...@gmail.com] On Behalf Of Nguyen
>Anh Tu
>Sent: Thursday, January 23, 2014 11:56 AM
>To: Murali Reddy
>Cc: dev@cloudstack.apache.org; Chiradeep Vittal; Sebastien Goasguen
>Subject: Re: Create GRE tunnel failed in 4.2 with XenServer.
>
>Wow... I thought everything was done in XenServer before my submitted
>patch.
>
>--Tuna
>
>Sent from my GT-N7000
>On Jan 23, 2014 6:49 PM, "Murali Reddy"  wrote:
>
>> Please see the thread
>>
>> https://www.mail-archive.com/dev@cloudstack.apache.org/msg17396.html
>>
>>
>>
>> On 23/01/14 5:10 PM, "Florin Dumitrascu"
>>  wrote:
>>
>> >Hi,
>> >
>> >Just want to add a few of my observations to what Tuna said.
>> >
>> >
>> >a.   I managed to have GRE isolation working with CloudStack 4.1.1
>> >and a quick patch to bypass "enableXenserverNetwork" method.
>> >
>> >
>> >
>> >b.  I tried GRE isolation with CloudStack 4.2.1 with the same quick
>> >patch for bypassing "enableXenserverNetwork".
>> >
>> >Once that method was bypassed, guest VMs came up, but the tunnel was
>> >not created. It seems to me that OvsElement methods (implement,
>> >prepare) are not invoked.
>> >
>> >Did something change in 4.2 to affect this ? I am setting
>> >"sdn.ovs.controller=true" in global settings and select GRE isolation
>> >method in the guest physical network.
>> >
>> >
>> >Thank you,
>> >Florin
>> >
>> >
>> >
>> >From: ng.t...@gmail.com [mailto:ng.t...@gmail.com] On Behalf Of
>> >Nguyen Anh Tu
>> >Sent: Thursday, January 23, 2014 10:15 AM
>> >To: dev@cloudstack.apache.org; Sebastien Goasguen; Chiradeep Vittal;
>> >Florin Dumitrascu
>> >Subject: Create GRE tunnel failed in 4.2 with XenServer.
>> >
>> >
>> >Guys,
>> >
>> >Florin raised a problem in creating GRE tunnel with ACS 4.2 release
>> >and XenServer 6.2. I found the problem come from
>> >enableXenserverNetwork method. CloudStack made a tricky to create
>> >network when plugging a VIF to
>> >dom0 and then unplugging immediately. With XCP version I done in
>> >GSOC, I bypassed that step so that no problem.
>> >
>> >Didn't know why we need that tricky and how to solve it. I'm working
>> >on it. Any help or explaination?
>> >
>> >Thanks,
>> >
>> >--Tuna
>> >
>> >Sent from my GT-N7000
>> >
>> >IMPORTANT NOTE: The information in this e-mail (and any attachments)
>> >is confidential. The contents may not be disclosed or used by anyone
>> >other than the addressee. If you are not the intended recipient,
>> >please notify the sender immediately or telephone: +353 (0)1 6204700.
>> >We cannot accept any responsibility for the accuracy or completeness
>> >of this message as it has been transmitted over a public network. If
>> >you suspect that the message may have been intercepted or amended,
>>please call the sender.
>> >
>>
>>
>>
>
>IMPORTANT NOTE: The information in this e-mail (and any attachments) is
>confidential. The contents may not be disclosed or used by anyone other
>than the addressee. If you are not the intended recipient, please notify
>the sender immediately or telephone: +353 (0)1 6204700. We cannot accept
>any responsibility for the accuracy or completeness of this message as it
>has been transmitted over a public network. If you suspect that the
>message may have been intercepted or amended, please call the sender.
>

Re: [ANNOUNCE] Switch to Java 7 in master branch on Monday Jan 27th 2014

[Abhinandan Prateek]

On 24/01/14 10:33 am, "Rajesh Battala"  wrote:

>Abhi, 
>If we switch to jre1.7 for systemvm, we need to generate new systemvm for
>all the Hypervisors.
>Will this be for 4.4 and forward only right? It won't be in 4.3.

Changes will go in master and not in 4.3.

>

Re: Create GRE tunnel failed in 4.2 with XenServer.

[Nguyen Anh Tu]

Yes, my fixes will be put to 4.3 tomorrow! I get the flu today. Back to
work tomorrow.

--Tuna

Sent from my GT-N7000
On Jan 24, 2014 12:43 PM, "Murali Reddy"  wrote:

>
> On 23/01/14 5:48 PM, "Florin Dumitrascu"
>  wrote:
>
> >Hi Murali, Tuna,
> >
> >Thank you for this piece of information. All starts to make sense now.
> >I am wondering if there is a better way to communicate this issue to end
> >users. It would save others a couple of weeks struggling.
> >If GRE is not just a technology preview (meaning it has been explicitly
> >mentioned in previous release notes), the known issues lists for 4.2.0
> >and 4.2.1 should be explicitly updated.
> >
> >Leaving 4.2 behind now, which will be the first release to include GRE
> >refactoring with OVS service provider ?
>
> Ideally Tuna's fix (to make OVS as Connectivity service provider) should
> have gone into 4.2.1. Looks like they did not go into 4.2.1
>
> Tuna,
>
> Can you please ensure your fixes (excluding support for KVM/XCP) went into
> 4.2, 4.3 branches as well.
>
> Thanks,
> Murali
>
> >
> >Regards,
> >Florin
> >
> >-Original Message-
> >From: ng.t...@gmail.com [mailto:ng.t...@gmail.com] On Behalf Of Nguyen
> >Anh Tu
> >Sent: Thursday, January 23, 2014 11:56 AM
> >To: Murali Reddy
> >Cc: dev@cloudstack.apache.org; Chiradeep Vittal; Sebastien Goasguen
> >Subject: Re: Create GRE tunnel failed in 4.2 with XenServer.
> >
> >Wow... I thought everything was done in XenServer before my submitted
> >patch.
> >
> >--Tuna
> >
> >Sent from my GT-N7000
> >On Jan 23, 2014 6:49 PM, "Murali Reddy"  wrote:
> >
> >> Please see the thread
> >>
> >> https://www.mail-archive.com/dev@cloudstack.apache.org/msg17396.html
> >>
> >>
> >>
> >> On 23/01/14 5:10 PM, "Florin Dumitrascu"
> >>  wrote:
> >>
> >> >Hi,
> >> >
> >> >Just want to add a few of my observations to what Tuna said.
> >> >
> >> >
> >> >a.   I managed to have GRE isolation working with CloudStack 4.1.1
> >> >and a quick patch to bypass "enableXenserverNetwork" method.
> >> >
> >> >
> >> >
> >> >b.  I tried GRE isolation with CloudStack 4.2.1 with the same quick
> >> >patch for bypassing "enableXenserverNetwork".
> >> >
> >> >Once that method was bypassed, guest VMs came up, but the tunnel was
> >> >not created. It seems to me that OvsElement methods (implement,
> >> >prepare) are not invoked.
> >> >
> >> >Did something change in 4.2 to affect this ? I am setting
> >> >"sdn.ovs.controller=true" in global settings and select GRE isolation
> >> >method in the guest physical network.
> >> >
> >> >
> >> >Thank you,
> >> >Florin
> >> >
> >> >
> >> >
> >> >From: ng.t...@gmail.com [mailto:ng.t...@gmail.com] On Behalf Of
> >> >Nguyen Anh Tu
> >> >Sent: Thursday, January 23, 2014 10:15 AM
> >> >To: dev@cloudstack.apache.org; Sebastien Goasguen; Chiradeep Vittal;
> >> >Florin Dumitrascu
> >> >Subject: Create GRE tunnel failed in 4.2 with XenServer.
> >> >
> >> >
> >> >Guys,
> >> >
> >> >Florin raised a problem in creating GRE tunnel with ACS 4.2 release
> >> >and XenServer 6.2. I found the problem come from
> >> >enableXenserverNetwork method. CloudStack made a tricky to create
> >> >network when plugging a VIF to
> >> >dom0 and then unplugging immediately. With XCP version I done in
> >> >GSOC, I bypassed that step so that no problem.
> >> >
> >> >Didn't know why we need that tricky and how to solve it. I'm working
> >> >on it. Any help or explaination?
> >> >
> >> >Thanks,
> >> >
> >> >--Tuna
> >> >
> >> >Sent from my GT-N7000
> >> >
> >> >IMPORTANT NOTE: The information in this e-mail (and any attachments)
> >> >is confidential. The contents may not be disclosed or used by anyone
> >> >other than the addressee. If you are not the intended recipient,
> >> >please notify the sender immediately or telephone: +353 (0)1 6204700.
> >> >We cannot accept any responsibility for the accuracy or completeness
> >> >of this message as it has been transmitted over a public network. If
> >> >you suspect that the message may have been intercepted or amended,
> >>please call the sender.
> >> >
> >>
> >>
> >>
> >
> >IMPORTANT NOTE: The information in this e-mail (and any attachments) is
> >confidential. The contents may not be disclosed or used by anyone other
> >than the addressee. If you are not the intended recipient, please notify
> >the sender immediately or telephone: +353 (0)1 6204700. We cannot accept
> >any responsibility for the accuracy or completeness of this message as it
> >has been transmitted over a public network. If you suspect that the
> >message may have been intercepted or amended, please call the sender.
> >
>
>
>

RE: [ANNOUNCE] Switch to Java 7 in master branch on Monday Jan 27th 2014

[Rajesh Battala]

Thanks Abhi for the info. 

-Original Message-
From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com] 
Sent: Friday, January 24, 2014 11:18 AM
To: dev@cloudstack.apache.org
Subject: Re: [ANNOUNCE] Switch to Java 7 in master branch on Monday Jan 27th 
2014

On 24/01/14 10:33 am, "Rajesh Battala"  wrote:

>Abhi,
>If we switch to jre1.7 for systemvm, we need to generate new systemvm 
>for all the Hypervisors.
>Will this be for 4.4 and forward only right? It won't be in 4.3.

Changes will go in master and not in 4.3.

>

RE: Review Request 15247: [DOC] CLOUDSTACK-4967: Add a section to describe VNI allocation matter

[Radhika Puthiyetath]

Please apply this patch to 4.3 branch as well. 

-Original Message-
From: Toshiaki Hatano [mailto:nore...@reviews.apache.org] On Behalf Of Toshiaki 
Hatano
Sent: Thursday, January 23, 2014 10:53 PM
To: Marcus Sorensen; Toshiaki Hatano
Cc: Yoshikazu Nojima; cloudstack
Subject: Re: Review Request 15247: [DOC] CLOUDSTACK-4967: Add a section to 
describe VNI allocation matter



> On Jan. 23, 2014, 5:08 p.m., Toshiaki Hatano wrote:
> > Ship It!

applied to master and 4.3.
commit c9b8bc0884e9e1166046bfdd1354a991d39d7d71 in master commit 
002c2b22f43f7ace0ade652e92c2d46b92c3136f in 4.3


- Toshiaki


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15247/#review32625
---


On Jan. 22, 2014, 5:44 a.m., Yoshikazu Nojima wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15247/
> ---
> 
> (Updated Jan. 22, 2014, 5:44 a.m.)
> 
> 
> Review request for cloudstack, Marcus Sorensen and Toshiaki Hatano.
> 
> 
> Bugs: CLOUDSTACK-4967
> https://issues.apache.org/jira/browse/CLOUDSTACK-4967
> 
> 
> Repository: cloudstack-docs
> 
> 
> Description
> ---
> 
> This patch updates CloudStack Plugin Guide for the VXLAN Plugin.
> 
> - Add a section to describe VNIs allocation matter
> - Remove section that explain how to configure the bridge for traffic label 
> because the bridge configuration is no longer necessary.
> - Update screen shots to catch up new UI visual appearance.
> 
> 
> Diffs
> -
> 
>   vxlan/en-US/images/vxlan-physicalnetwork.png 
> e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
>   vxlan/en-US/images/vxlan-trafficlabel.png 
> 956d5f4f58f592ed3f260d6e1982c238c2ddf06a 
>   vxlan/en-US/images/vxlan-vniconfig.png PRE-CREATION 
>   vxlan/en-US/plugin-vxlan-config-hypervisor.xml 2c5e138 
>   vxlan/en-US/plugin-vxlan-config-management.xml 21f5461 
>   vxlan/en-US/plugin-vxlan-requirements.xml c2e04a6 
>   vxlan/en-US/plugin-vxlan-revision-history.xml ec04d11
> 
> Diff: https://reviews.apache.org/r/15247/diff/
> 
> 
> Testing
> ---
> 
> I generated and confirmed the PDF.
> 
> 
> Thanks,
> 
> Yoshikazu Nojima
> 
>

Re: Review Request 17120: added an extra column to mark the imported ldap users as from ldap

[Prachi Damle]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17120/#review32702
---


I see many files unrelated to this fix have been updated and present in the 
patch.
Please can you update the patch with changes needed for the fix only?

Following are some such files.
api/src/com/cloud/user/AccountService.java
engine/schema/src/com/cloud/user/UserVO.java
plugins/dedicated-resources/test/org/apache/cloudstack/dedicated/manager/DedicatedApiUnitTest.java:
 8 changes [ 1 2 3 4 5 6 7 8 ]
plugins/deployment-planners/implicit-dedication/test/org/apache/cloudstack/implicitplanner/ImplicitPlannerTest.java:
 16 changes [ 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 ]
plugins/network-elements/juniper-contrail/test/org/apache/cloudstack/network/contrail/management/MockAccountManager.java
plugins/user-authenticators/ldap/src/org/apache/cloudstack/api/command/LdapCreateAccountCmd.java

Also the below file has all Mockito references replaced by Matchers - what is 
the reason for this change?
plugins/hypervisors/vmware/test/com/cloud/hypervisor/vmware/VmwareDatacenterApiUnitTest.java

- Prachi Damle


On Jan. 22, 2014, 7:24 a.m., Rajani Karuturi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/17120/
> ---
> 
> (Updated Jan. 22, 2014, 7:24 a.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek, Ian Duffy, Min Chen, and 
> Prachi Damle.
> 
> 
> Bugs: CLOUDSTACK-5910
> https://issues.apache.org/jira/browse/CLOUDSTACK-5910
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> added an extra column to mark the imported ldap users as from ldap
> 
> 
> Diffs
> -
> 
>   api/src/com/cloud/user/AccountService.java a9be292 
>   api/src/com/cloud/user/User.java 36e9028 
>   engine/schema/src/com/cloud/user/UserVO.java 68879f6 
>   
> plugins/dedicated-resources/test/org/apache/cloudstack/dedicated/manager/DedicatedApiUnitTest.java
>  213174b 
>   
> plugins/deployment-planners/implicit-dedication/test/org/apache/cloudstack/implicitplanner/ImplicitPlannerTest.java
>  4182193 
>   
> plugins/hypervisors/vmware/test/com/cloud/hypervisor/vmware/VmwareDatacenterApiUnitTest.java
>  4a00489 
>   
> plugins/network-elements/juniper-contrail/test/org/apache/cloudstack/network/contrail/management/MockAccountManager.java
>  2f81688 
>   
> plugins/user-authenticators/ldap/src/org/apache/cloudstack/api/command/LdapCreateAccountCmd.java
>  100ffe6 
>   
> plugins/user-authenticators/ldap/src/org/apache/cloudstack/api/command/LdapImportUsersCmd.java
>  89cec65 
>   server/src/com/cloud/user/AccountManagerImpl.java 5204589 
>   server/test/com/cloud/configuration/ConfigurationManagerTest.java f1bb30a 
>   server/test/com/cloud/network/DedicateGuestVlanRangesTest.java 1615b84 
>   server/test/com/cloud/user/MockAccountManagerImpl.java 62e7fc8 
>   server/test/com/cloud/vm/UserVmManagerTest.java 83f7520 
>   server/test/com/cloud/vpc/NetworkACLManagerTest.java 629afa3 
>   server/test/com/cloud/vpc/NetworkACLServiceTest.java 786789f 
>   server/test/org/apache/cloudstack/affinity/AffinityApiUnitTest.java 061fd42 
>   server/test/org/apache/cloudstack/network/lb/CertServiceTest.java a67a9ab 
>   
> server/test/org/apache/cloudstack/region/gslb/GlobalLoadBalancingRulesServiceImplTest.java
>  d152c66 
>   setup/db/db/schema-421to430.sql ccff7c1 
> 
> Diff: https://reviews.apache.org/r/17120/diff/
> 
> 
> Testing
> ---
> 
> manually tested
> 
> 
> Thanks,
> 
> Rajani Karuturi
> 
>

[ACS 4.3] Release Notes

[Animesh Chaturvedi]

Folks

I have updated the Release Notes in 4.3 with a link to Known Issues and Fixed 
Issues in 4.3 release and kicked off the build. We need a volunteer to fix up 
the release notes.

Here are the JIRA filters if someone is interested to look at them

Issues fixed in 4.3 https://issues.apache.org/jira/issues/?filter=12326161
Known Issues in 4.3 https://issues.apache.org/jira/issues/?filter=12326162

Thanks
Animesh

Re: Review Request 17120: added an extra column to mark the imported ldap users as from ldap

[Rajani Karuturi]

> On Jan. 24, 2014, 6:52 a.m., Prachi Damle wrote:
> > I see many files unrelated to this fix have been updated and present in the 
> > patch.
> > Please can you update the patch with changes needed for the fix only?
> > 
> > Following are some such files.
> > api/src/com/cloud/user/AccountService.java
> > engine/schema/src/com/cloud/user/UserVO.java
> > plugins/dedicated-resources/test/org/apache/cloudstack/dedicated/manager/DedicatedApiUnitTest.java:
> >  8 changes [ 1 2 3 4 5 6 7 8 ]
> > plugins/deployment-planners/implicit-dedication/test/org/apache/cloudstack/implicitplanner/ImplicitPlannerTest.java:
> >  16 changes [ 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 ]
> > plugins/network-elements/juniper-contrail/test/org/apache/cloudstack/network/contrail/management/MockAccountManager.java
> > plugins/user-authenticators/ldap/src/org/apache/cloudstack/api/command/LdapCreateAccountCmd.java
> > 
> > Also the below file has all Mockito references replaced by Matchers - what 
> > is the reason for this change?
> > plugins/hypervisors/vmware/test/com/cloud/hypervisor/vmware/VmwareDatacenterApiUnitTest.java

The major changes for this patch are in the following files:
api/src/com/cloud/user/AccountService.java: 1 change [ 1 ] - > added a new 
overloaded method to take the source of the account for the create call
api/src/com/cloud/user/User.java: 2 changes [ 1 2 ] -> added the new field's 
getter and its enum
engine/schema/src/com/cloud/user/UserVO.java: 4 changes [ 1 2 3 4 ] -> mapped 
the new database cloumn and added getter/setter, also changed the constructor 
to take the new field
plugins/user-authenticators/ldap/src/org/apache/cloudstack/api/command/LdapCreateAccountCmd.java:
 2 changes [ 1 2 ] -> this is the one which is called when creating an ldap 
user and this calls create account with source as LDAP
plugins/user-authenticators/ldap/src/org/apache/cloudstack/api/command/LdapImportUsersCmd.java:
 2 changes [ 1 2 ] -> this is ldap's import multiple users command. change is 
same as above
server/src/com/cloud/user/AccountManagerImpl.java: 6 changes [ 1 2 3 4 5 6 ] -> 
implementation of the new method
setup/db/db/schema-421to430.sql: 2 changes [ 1 2 ] -> SQL to add the new column

The rest changes in tests/mock classes are due to change in constructor of 
UserVo which cant be avoided
VmwareDatacenterApiUnitTest also has the same change as above. I dont see the 
Mockito/Matchers change you mentioned. 
https://reviews.apache.org/r/17120/diff/#5

Also note that patch1/diff1 is for 4.3 and and patch2/diff2 is for master. As 
we are getting conflicts due to spaces changes I created two patches. The 
changes are same in both the patches.


- Rajani


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17120/#review32702
---


On Jan. 22, 2014, 7:24 a.m., Rajani Karuturi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/17120/
> ---
> 
> (Updated Jan. 22, 2014, 7:24 a.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek, Ian Duffy, Min Chen, and 
> Prachi Damle.
> 
> 
> Bugs: CLOUDSTACK-5910
> https://issues.apache.org/jira/browse/CLOUDSTACK-5910
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> added an extra column to mark the imported ldap users as from ldap
> 
> 
> Diffs
> -
> 
>   api/src/com/cloud/user/AccountService.java a9be292 
>   api/src/com/cloud/user/User.java 36e9028 
>   engine/schema/src/com/cloud/user/UserVO.java 68879f6 
>   
> plugins/dedicated-resources/test/org/apache/cloudstack/dedicated/manager/DedicatedApiUnitTest.java
>  213174b 
>   
> plugins/deployment-planners/implicit-dedication/test/org/apache/cloudstack/implicitplanner/ImplicitPlannerTest.java
>  4182193 
>   
> plugins/hypervisors/vmware/test/com/cloud/hypervisor/vmware/VmwareDatacenterApiUnitTest.java
>  4a00489 
>   
> plugins/network-elements/juniper-contrail/test/org/apache/cloudstack/network/contrail/management/MockAccountManager.java
>  2f81688 
>   
> plugins/user-authenticators/ldap/src/org/apache/cloudstack/api/command/LdapCreateAccountCmd.java
>  100ffe6 
>   
> plugins/user-authenticators/ldap/src/org/apache/cloudstack/api/command/LdapImportUsersCmd.java
>  89cec65 
>   server/src/com/cloud/user/AccountManagerImpl.java 5204589 
>   server/test/com/cloud/configuration/ConfigurationManagerTest.java f1bb30a 
>   server/test/com/cloud/network/DedicateGuestVlanRangesTest.java 1615b84 
>   server/test/com/cloud/user/MockAccountManagerImpl.java 62e7fc8 
>   server/test/com/cloud/vm/UserVmManagerTest.java 83f7520 
>   server/test/com/cloud/vpc/NetworkACLManagerTest.java 629afa3 
>   server/test/com/cloud/vpc/NetworkACLServiceTest.java 786789f 
>   server/test/org/apache/clou

RE: [ACS 4.3] Release Notes

[Radhika Puthiyetath]

Hi,

I have picked up the Overview section. 

Thanks
-Radhika

-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
Sent: Friday, January 24, 2014 12:58 PM
To: dev@cloudstack.apache.org
Subject: [ACS 4.3] Release Notes

Folks

I have updated the Release Notes in 4.3 with a link to Known Issues and Fixed 
Issues in 4.3 release and kicked off the build. We need a volunteer to fix up 
the release notes.

Here are the JIRA filters if someone is interested to look at them

Issues fixed in 4.3 https://issues.apache.org/jira/issues/?filter=12326161
Known Issues in 4.3 https://issues.apache.org/jira/issues/?filter=12326162

Thanks
Animesh