RE: 4-2-advanced-zone-security-group

[Anthony Xu]

Thanks for reporting this,

It didn't work in normal advanced zone or advanced zone with security group.

In advanced zone with security group, only one shared network security group 
network is supported, which is created when you create the zone, you may not be 
able to create another guest network.


Anthony

From: Paul Angus [mailto:paul.an...@shapeblue.com]
Sent: Saturday, May 18, 2013 10:00 AM
To: dev@cloudstack.apache.org
Cc: Anthony Xu
Subject: 4-2-advanced-zone-security-group

Hi Anthony,

I've been doing some testing on the [4-2-advanced-zone-security-group] branch.

I found that the 'Add Guest Network' button does not work from the Network tab 
(it does via Zone > Physical Network > Guest).
I've tried as root admin and a domain guest. And using chrome and Firefox - no 
joy.

Regards,

Paul Angus
Senior Consultant / Cloud Architect
[cid:image001.png@01CE554C.1DD951A0]

S: +44 20 3603 0540 | M: +447711418784
paul.an...@shapeblue.com<mailto:geoff.higginbot...@shapeblue.com> | 
www.shapeblue.com | Twitter:@shapeblue<https://twitter.com/>
ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS

ShapeBlue are proud to be sponsoring CloudStack Collaboration  Conference NA
[https://cwiki.apache.org/confluence/download/attachments/30760149/CloudStack+Collaboration+Conference+Banner+v2+Blue+Background+Only.jpg?version=3&modificationDate=1367282397297]<http://www.cloudstackcollab.net/>

Apache CloudStack Bootcamp training courses
20/21 May, London<http://www.shapeblue.com/cloudstack-bootcamp-training-course/>
22/23 June, Santa Clara  
CA<http://www.shapeblue.com/cloudstack-bootcamp-training-course/>

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is operated under 
license from Shape Blue Ltd. ShapeBlue is a registered trademark.

[MERGE] security group advanced zone branch into master

[Anthony Xu]

Hi all,
   CloudStack has this feature in 2.2.14, but drops it in 3.0.2 
somehow. In this branch, we add this feature back, below is brief description 
for this feature,

-  Introduce advanced zone with security group, in this zone, only one 
shared network with security group is allowed, no other network allowed.

-  Support both xenserver and kvm in this zone.

-  Security group rule in this zone is like that in basic zone.


Branch: 4-2-advanced-zone-security-group

-   Except for the feature code, there are upgrade code , thanks to 
Alena, and integration/devcloud test code, thanks a lot to wei zhou.

-  UI code is in master



Test:
 I did some basic manual tests, vm can boot up, security group works 
fine
 Wei zhou added devcloud tests and integration tests, devcloud test 
works fine.



You can find more information in below bug.


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



Best Regards,
Anthony

RE: [MERGE] security group advanced zone branch into master

[Anthony Xu]

I didn't hear any objection , I'll merge this today.


Thanks,
Anthony

From: Anthony Xu
Sent: Wednesday, May 22, 2013 4:25 PM
To: dev@cloudstack.apache.org
Cc: Alena Prokharchyk; Wei Zhou (w.z...@leaseweb.com); Anthony Xu
Subject: [MERGE] security group advanced zone branch into master

Hi all,
   CloudStack has this feature in 2.2.14, but drops it in 3.0.2 
somehow. In this branch, we add this feature back, below is brief description 
for this feature,

-  Introduce advanced zone with security group, in this zone, only one 
shared network with security group is allowed, no other network allowed.

-  Support both xenserver and kvm in this zone.

-  Security group rule in this zone is like that in basic zone.


Branch: 4-2-advanced-zone-security-group

-   Except for the feature code, there are upgrade code , thanks to 
Alena, and integration/devcloud test code, thanks a lot to wei zhou.

-  UI code is in master



Test:
 I did some basic manual tests, vm can boot up, security group works 
fine
 Wei zhou added devcloud tests and integration tests, devcloud test 
works fine.



You can find more information in below bug.


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




Best Regards,
Anthony

RE: Create a VDI in an SR as large as possible

[Anthony Xu]

Please notice the maximum size of VDI is 2T,

Anthony

-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
Sent: Tuesday, June 11, 2013 10:37 AM
To: dev@cloudstack.apache.org
Subject: Re: Create a VDI in an SR as large as possible

At one point I tried the following, but it didn't work (the VDI's size was set 
too high):

vdir.virtualSize = sr.getPhysicalSize(conn) - sr.getPhysicalUtilisation(conn);


On Tue, Jun 11, 2013 at 11:31 AM, Mike Tutkowski < 
mike.tutkow...@solidfire.com> wrote:

> Hi,
>
> I want to create an SR that has a single VDI that takes up all of the 
> available space of the SR.
>
> The SR has some metadata on it, so I can't just set the size of the 
> VDI equal to the size of the SR.
>
> Right now, I take the size of the SR and trim off some hard-coded number.
>
> Anyone know how I can come up with this number dynamically?
>
> 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
> *(tm)*
>



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

RE: Expanding a volume on a SAN

[Anthony Xu]

http://support.citrix.com/article/CTX120865

for XenServer, VMs need to be shut down or migrated away before  expanding a 
volume.


Anthony

-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
Sent: Tuesday, July 09, 2013 2:25 PM
To: dev@cloudstack.apache.org
Cc: Edison Su; John Burwell
Subject: Expanding a volume on a SAN

Hi everyone,

I had a question posed to me today regarding how CloudStack and the underlying 
hypervisor deal with an iSCSI volume that is expanded.

For example, let's say I'm using XenServer or ESX and I create a storage 
repository or datastore, respectively, for each hypervisor based on an iSCSI 
target. I then tie this into CloudStack as Primary Storage.

If I increase the size of the iSCSI target (the SAN volume/LUN), does this 
increased size feed into the hypervisor and CloudStack?

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
*(tm)*

RE: Expanding a volume on a SAN

[Anthony Xu]

CS will see the new size, 


Anthony

-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
Sent: Tuesday, July 09, 2013 5:25 PM
To: dev@cloudstack.apache.org
Subject: Re: Expanding a volume on a SAN

Hey Anthony,

I assume this would be a candidate situation where you'd put the primary 
storage in maintenance mode and then perform the steps you referred me to?

When the storage is brought out of maintenance mode, will it see the new size 
or is there something more that has to be done on the CS side?

Thanks!


On Tue, Jul 9, 2013 at 6:09 PM, Mike Tutkowski  wrote:

> Thanks!
>
> Anyone know if CloudStack will recognize the new size of a storage 
> repository or datastore on its own?
>
>
> On Tue, Jul 9, 2013 at 4:01 PM, Anthony Xu  wrote:
>
>> http://support.citrix.com/article/CTX120865
>>
>> for XenServer, VMs need to be shut down or migrated away before  
>> expanding a volume.
>>
>>
>> Anthony
>>
>> -Original Message-
>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> Sent: Tuesday, July 09, 2013 2:25 PM
>> To: dev@cloudstack.apache.org
>> Cc: Edison Su; John Burwell
>> Subject: Expanding a volume on a SAN
>>
>> Hi everyone,
>>
>> I had a question posed to me today regarding how CloudStack and the 
>> underlying hypervisor deal with an iSCSI volume that is expanded.
>>
>> For example, let's say I'm using XenServer or ESX and I create a 
>> storage repository or datastore, respectively, for each hypervisor 
>> based on an iSCSI target. I then tie this into CloudStack as Primary Storage.
>>
>> If I increase the size of the iSCSI target (the SAN volume/LUN), does 
>> this increased size feed into the hypervisor and CloudStack?
>>
>> 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>
>> *(tm)*
>>
>
>
>
> --
> *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>
> *(tm)*
>



--
*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>
*(tm)*

RE: Expanding a volume on a SAN

[Anthony Xu]

If you put the primary storage in maintenance mode to evacuate the VM, when you 
cancel maintenance mode for the primary storage, CS will get the new size of 
the primary storage.


Anthony

-Original Message-
From: Alex Huang [mailto:alex.hu...@citrix.com] 
Sent: Wednesday, July 10, 2013 4:07 PM
To: dev@cloudstack.apache.org
Subject: RE: Expanding a volume on a SAN

ah sorry.  Yes.  From the CloudStack management UI, you can force cloudstack to 
reconnect to the host.  This forces cloudstack to flush it's connection and 
restablish the connection.  On restablishing the connection, there's a series 
of checks and information gathered.  Size of the storage pool is one such 
information.

--Alex

> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Wednesday, July 10, 2013 3:13 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Expanding a volume on a SAN
> 
> Hey Alex,
> 
> When you say, "force a reconnection," I'm not sure to what part of the 
> system you're referring. Is this an action performed on the CloudStack side?
> 
> Thanks!
> 
> 
> On Wed, Jul 10, 2013 at 4:10 PM, Alex Huang  wrote:
> 
> > You might have to force a reconnection to the xenserver in order for 
> > CS to see it.  On every connection, CS checks these items and 
> > updates its database.
> >
> > --Alex
> >
> > > -Original Message-
> > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > > Sent: Wednesday, July 10, 2013 2:14 PM
> > > To: dev@cloudstack.apache.org
> > > Subject: Re: Expanding a volume on a SAN
> > >
> > > OK, great - thanks!
> > >
> > > So, it sounds like on XenServer, you have to perform some manual 
> > > activity for it to see the new size of the iSCSI target (and there 
> > > is probably a
> > similar
> > > requirement with ESX), but CloudStack will notice the size 
> > > difference automatically (once the storage repository or datastore 
> > > has been manually re-configured).
> > >
> > >
> > > On Wed, Jul 10, 2013 at 2:48 PM, Anthony Xu 
> > wrote:
> > >
> > > > CS will see the new size,
> > > >
> > > >
> > > > Anthony
> > > >
> > > > -Original Message-
> > > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > > > Sent: Tuesday, July 09, 2013 5:25 PM
> > > > To: dev@cloudstack.apache.org
> > > > Subject: Re: Expanding a volume on a SAN
> > > >
> > > > Hey Anthony,
> > > >
> > > > I assume this would be a candidate situation where you'd put the 
> > > > primary storage in maintenance mode and then perform the steps 
> > > > you
> > > referred me to?
> > > >
> > > > When the storage is brought out of maintenance mode, will it see 
> > > > the new size or is there something more that has to be done on 
> > > > the CS
> side?
> > > >
> > > > Thanks!
> > > >
> > > >
> > > > On Tue, Jul 9, 2013 at 6:09 PM, Mike Tutkowski < 
> > > > mike.tutkow...@solidfire.com
> > > > > wrote:
> > > >
> > > > > Thanks!
> > > > >
> > > > > Anyone know if CloudStack will recognize the new size of a 
> > > > > storage repository or datastore on its own?
> > > > >
> > > > >
> > > > > On Tue, Jul 9, 2013 at 4:01 PM, Anthony Xu 
> > > > > 
> > > wrote:
> > > > >
> > > > >> http://support.citrix.com/article/CTX120865
> > > > >>
> > > > >> for XenServer, VMs need to be shut down or migrated away 
> > > > >> before expanding a volume.
> > > > >>
> > > > >>
> > > > >> Anthony
> > > > >>
> > > > >> -Original Message-
> > > > >> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > > > >> Sent: Tuesday, July 09, 2013 2:25 PM
> > > > >> To: dev@cloudstack.apache.org
> > > > >> Cc: Edison Su; John Burwell
> > > > >> Subject: Expanding a volume on a SAN
> > > > >>
> > > > >> Hi everyone,
> > > > >>
> > > > >> I had a question posed to me today regarding how CloudStack 
> > > > >> and the underlying hypervisor deal with an iS

RE: [rant] stupid test cases

[Anthony Xu]

+1   VM can be in "Stopped" state


Anthony

-Original Message-
From: Marcus Sorensen [mailto:shadow...@gmail.com] 
Sent: Wednesday, July 17, 2013 10:47 PM
To: dev@cloudstack.apache.org
Subject: Re: [rant] stupid test cases

I can understand that we may want to test that everything related to the domain 
gets cleaned up properly. We have run into all sorts of things when deleting 
accounts, for example where resources won't clean up because the account is 
gone and we throw null pointers because a bunch of code looks up account when 
deleting. However, to your point, VMs can be created in a "stopped" state and 
that wouldn't incur the overhead of deployment.
On Jul 17, 2013 11:33 PM, "Prasanna Santhanam"  wrote:

> I was just going through one of the automated test cases and I find it 
> really silly that there's the following test:
>
> def test_forceDeleteDomain(self):
> """ Test delete domain force option"""
>
> # Steps for validations
> # 1. create a domain DOM
> # 2. create 2 users under this domain
> # 3. deploy 1 VM into each of these user accounts
> # 4. create PF / FW rules for port 22 on these VMs for their
> #respective accounts
> # 5. delete the domain with force=true option
> # Validate the following
> # 1. listDomains should list the created domain
> # 2. listAccounts should list the created accounts
> # 3. listvirtualmachines should show the Running VMs
> # 4. PF and FW rules should be shown in listFirewallRules
> # 5. domain should delete successfully and above three list calls
> #should show all the resources now deleted. listRouters should
> #not return any routers in the deleted accounts/domains
>
> Why would one need the overhead of creating VMs in a domain deletion test?
> Do
> we not understand that the basics accounts/domains/ etc that 
> cloudstack has nothing to do with the virtual machines? This kind of a 
> test slows down other useful tests that we could be running. More over 
> when this fails in the VM creation step I'd have to go in and analyse 
> logs to realize that deletedomain was perhaps fine but vm creation has 
> failed.
>
> That's a pointless effort. I'm sure there are others in the automated 
> tests that do this kind of wasteful testing. So please please pleaes 
> &*()#@()# please review test plans before automating them!
>
> I'm not going to be looking at this forever to fix these issues when 
> we want to see pretty metrics and numbers.
>
> --
> Prasanna.,
>
> 
> Powered by BigRock.com
>
>

Re: Review Request 13643: Unplug the nic when there are no ips set on the interface

[anthony xu]

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

Ship it!


Ship It!

- anthony xu


On Aug. 19, 2013, 10:58 a.m., Jayapal Reddy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13643/
> ---
> 
> (Updated Aug. 19, 2013, 10:58 a.m.)
> 
> 
> Review request for cloudstack, anthony xu, Abhinandan Prateek, and Murali 
> Reddy.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Unplugging the public nic on the VR when there are no ips set on the 
> interface.
> This issue of not reusing the public nic is present in the xen and mvm.
> 
> For vmware the nic got reused.
> 
> 
> Diffs
> -
> 
>   
> core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java 
> 1fb86e0 
>   patches/systemvm/debian/config/opt/cloud/bin/ipassoc.sh ae2d7e4 
>   
> plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java
>  9104504 
>   
> plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/CitrixResourceBase.java
>  338e741 
> 
> Diff: https://reviews.apache.org/r/13643/diff/
> 
> 
> Testing
> ---
> 
> Tested in xen and kvm.
> 
> 
> Thanks,
> 
> Jayapal Reddy
> 
>

RE: VPG only in VPC VRs?

[Anthony Xu]

VPC VR doesn't have remote access VPN and public IP based firewall.


Anthony

-Original Message-
From: Marcus Sorensen [mailto:shadow...@gmail.com] 
Sent: Friday, August 23, 2013 12:31 PM
To: dev@cloudstack.apache.org
Cc: jeffrey.mcgov...@sungard.com
Subject: Re: VPG only in VPC VRs?

I agree with Chiradeep, but it brings up a point that in some future release we 
probably need to convert/migrate existing VR/isolated network combos into VPCs 
so we can deprecate them entirely, as well as migrate the applicable api calls 
into creating the functionally equivalent VPCs... or something like that.

I think VPC is probably also lacking in a few features yet, so they're not 
quite a replacement at the moment. Remote access VPN for example.

On Fri, Aug 23, 2013 at 1:22 PM, Chiradeep Vittal  
wrote:
> Are you asking why VR for isolated networks does not have this feature?
> I feel that isolated networks are legacy and whatever you want to do 
> with isolated networks you should be able to do with a VPC in a single tier.
>
>
> On 8/23/13 11:19 AM, "Chip Childers"  wrote:
>
>>Can someone explain the history / reasoning around why VPG's are only 
>>available for VPC VRs?
>>
>>And while we're at it...  how about the same question around 
>>Site-to-site VPN's (and client VPN's in reverse)?
>>
>>Thanks!
>>
>>-chip
>

RE: Apache CloudStack 4.2.0 (fifth round)

[Anthony Xu]

Xe-daemon is used to collect cpu/memory usage info inside VM, the VM cannot 
migrate without installing xe-daemon in XenServer,
But CloudStack has  a script scripts/vm/hypervisor/xenserver/make_migratable.sh 
to make VM migratable without xe-daemon, because user might forget to install 
xe-daemon inside Linux VM.


Anthony

-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] 
Sent: Monday, September 16, 2013 10:23 AM
To: dev
Subject: Re: Apache CloudStack 4.2.0 (fifth round)

It does not not work completely. It has no xe-daemon running when instantiated 
so migration would fail is the theory, also some of our monitoring scripts fail.

We failed to see it at first as well as it starts up and networking works

On Mon, Sep 16, 2013 at 7:17 PM, Marcus Sorensen  wrote:
> Ok, so you mean even the stock one does not work for Xen.  Can anyone 
> else who as been testing Xen comment?
>
> On Mon, Sep 16, 2013 at 11:14 AM, Daan Hoogland  
> wrote:
>> On Mon, Sep 16, 2013 at 7:11 PM, Marcus Sorensen  wrote:
>>>
>>> Xenserver
>>> http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-
>>> master-xen.vhd.bz2
>>
>> I know, it does not have the xenstore binary on board that is called 
>> by xe-update-guest-attrs

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

[Anthony Xu]

>>The XenServer (6.0.2) I am using already came bundled with vhd-util, I 
>>did not have to download it. I have not read the detail of

Hi Soheil,

We added one function in vhd-util, which allows vhd-util specifiy parent when 
do coalesce, basically you can coalesce a VHD file to other VHD file. 
CS uses this vhd-util function in API creating template/volume from snapshot.  
These APIs might not work with bundled vhd-util in XenServer.


Anthony



-Original Message-
From: Soheil Eizadi [mailto:seiz...@infoblox.com] 
Sent: Saturday, April 13, 2013 11:05 PM
To: dev@cloudstack.apache.org
Subject: Re: deployDataCenter.py doesn't work for me on master

Downloaded the vhd-util to my environment and had the same problem. I Debugged 
this further by running the copy_vhd_from_secondarystorage.sh on the XenServer. 
It looks like the copy_vhd_from_secondarystorage.sh is looking for vhd-util in 
/opt/xensource/bin/ rather than /usr/bin/

I looked at this further and looks like what is built in the client/target 
directory is not consistent with what is in the ./scripts/vm in my tree.
There are two versions of copy_vhd_from_secondarystorage.sh.

I removed the client/target directory and rebuilt, but had the same files 
appear again. I am not sure how they are getting pulled in to the client/target 
directory. Any ideas why my build is broken and how to proceed to fix this?

For now I patched this on my XenServer and was able to get ssvm and cproxyvm 
running and brought up my CloudStack zone completely.
-Soheil


Administrators-MacBook-Pro-7:cloudstack seizadi$ find . -name 
copy_vhd_from_secondarystorage.sh 
./client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/scripts/vm/h
ypervisor/xenserver/copy_vhd_from_secondarystorage.sh
./client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/scripts/vm/h
ypervisor/xenserver/xcposs/copy_vhd_from_secondarystorage.sh
./client/target/generated-webapp/WEB-INF/classes/scripts/vm/hypervisor/xens
erver/copy_vhd_from_secondarystorage.sh
./client/target/generated-webapp/WEB-INF/classes/scripts/vm/hypervisor/xens
erver/xcposs/copy_vhd_from_secondarystorage.sh
./scripts/vm/hypervisor/xenserver/copy_vhd_from_secondarystorage.sh
./scripts/vm/hypervisor/xenserver/xcposs/copy_vhd_from_secondarystorage.sh


Administrators-MacBook-Pro-7:cloudstack seizadi$ find . -name 
copy_vhd_from_secondarystorage.sh -exec diff 
./client/target/generated-webapp/WEB-INF/classes/scripts/vm/hypervisor/xens
erver/copy_vhd_from_secondarystorage.sh {} \;
92c92
< VHDUTIL="/opt/xensource/bin/vhd-util"
---
> VHDUTIL="/usr/bin/vhd-util"
113c113
< if [ $type != "nfs" -a $type != "ext" ]; then
---
> if [ $type != "nfs" -a $type != "ext" -a $type != "file" ]; then
143c143
<   desvhd=/var/run/sr-mount/$sruuid/$uuid.vhd
---
>   desvhd=/run/sr-mount/$sruuid/$uuid.vhd
160a161,166
> elif [ $type == "file" ]; then
>   pbd=`xe sr-param-list uuid=$sruuid |grep PBDs | awk '{print $3}'`
>   path=`xe pbd-param-list uuid=$pbd |grep device-config |awk '{print 
>$4}'`
>   desvhd=$path/$uuid.vhd
>   copyvhd $desvhd $vhdfile 0 $type
> 
92c92
< VHDUTIL="/opt/xensource/bin/vhd-util"
---
> VHDUTIL="/usr/bin/vhd-util"
113c113
< if [ $type != "nfs" -a $type != "ext" ]; then
---
> if [ $type != "nfs" -a $type != "ext" -a $type != "file" ]; then
143c143
<   desvhd=/var/run/sr-mount/$sruuid/$uuid.vhd
---
>   desvhd=/run/sr-mount/$sruuid/$uuid.vhd
160a161,166
> elif [ $type == "file" ]; then
>   pbd=`xe sr-param-list uuid=$sruuid |grep PBDs | awk '{print $3}'`
>   path=`xe pbd-param-list uuid=$pbd |grep device-config |awk '{print 
>$4}'`
>   desvhd=$path/$uuid.vhd
>   copyvhd $desvhd $vhdfile 0 $type
> 
Š.


[root@xenserver-devcloud /]# copy_vhd_from_secondarystorage.sh 
172.16.197.134:/opt/storage/secondary/template/tmpl/1/1/
7e934fee-96b5-b297-2c25-b20a14139fd9 DEVTEST
/opt/xensource/bin/copy_vhd_from_secondarystorage.sh: line 133:
/opt/xensource/bin/vhd-util: No such file or directory
Error: Failed to parse field 'virtual-size': expecting an integer (possibly 
with suffix) 9#can not create vdi in sr 7e934fee-96b5-b297-2c25-b20a14139fd9

[root@xenserver-devcloud /]# cp /usr/sbin/vhd-util /opt/xensource/bin/vhd-util 
[root@xenserver-devcloud /]# copy_vhd_from_secondarystorage.sh 
172.16.197.134:/opt/storage/secondary/template/tmpl/1/1/
7e934fee-96b5-b297-2c25-b20a14139fd9 DEVTEST
1001+1 records in
1001+1 records out
2101252608 bytes (2.1 GB) copied, 178.662 seconds, 11.8 MB/s
0#c9cb5877-9434-4f3e-93b7-2f895cc62642






On 4/12/13 5:04 PM, "Chiradeep Vittal"  wrote:

>Because of this
>http://s.apache.org/Nsd
>
>On 4/12/13 4:32 PM, "Soheil Eizadi"  wrote:
>
>>That patch is about downloading vhd-util to XenServer.
>>
>>The XenServer (6.0.2) I am using already came bundled with vhd-util, I 
>>did not have to download it. I have not read the detail of 
>>copy_vhd_from_secondarystorage.sh which throws the error to figure out 
>>exactly why it is failing in my environment. I have used this same 
>>XenServer ima

RE: [jira] [Commented] (CLOUDSTACK-2463) CS Upgrade 2.2.14 to 4.1.0 failed due to no public network found (configuration : advanced network with security groups)

[Anthony Xu]

Advance zone with SG is not in 4.1.

Anthony

-Original Message-
From: Alena Prokharchyk 
Sent: Monday, May 13, 2013 1:37 PM
To: dev@cloudstack.apache.org; Chip Childers; Anthony Xu
Subject: Re: [jira] [Commented] (CLOUDSTACK-2463) CS Upgrade 2.2.14 to 4.1.0 
failed due to no public network found (configuration : advanced network with 
security groups)

Anthony, do we even support Advance zone with SG in 4.1? I thought you've 
checked it in in 4.2 only. If this is true, then:

* no upgrade support for SG enabled setups to 4.1 should be provided
* 4.1 UI shouldn't let you create Advance zone with SG enabled. If UI for SG 
enabled Advance zone was somehow merged to 4.1 branch, it should be reverted as 
there is no backend/db upgrade support exist there.


-Alena.



On 5/13/13 1:10 PM, "Paul Angus"  wrote:

>Done. :)
>
>Regards,
>
>Paul Angus
>S: +44 20 3603 0540 | M: +447711418784
>paul.an...@shapeblue.com
>
>-Original Message-
>From: Wei ZHOU [mailto:ustcweiz...@gmail.com]
>Sent: 13 May 2013 18:38
>To: dev@cloudstack.apache.org
>Subject: Re: [jira] [Commented] (CLOUDSTACK-2463) CS Upgrade 2.2.14 to
>4.1.0 failed due to no public network found (configuration : advanced 
>network with security groups)
>
>Thanks,  Paul.
>
>Could you login to the database and paste the result of the commands 
>Nicolas listed in Description?
>
>
>2013/5/13 Paul Angus (JIRA) 
>
>>
>> [
>> https://issues.apache.org/jira/browse/CLOUDSTACK-2463?page=com.atlass
>> i 
>> an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentI
>> d
>> =13656100#comment-13656100]
>>
>> Paul Angus commented on CLOUDSTACK-2463:
>> 
>>
>> On a clean build of ACS4.1-SNAPSHOT from 13/05/13 I created an 
>> advanced zone with security groups.
>>
>> When attempting to enable the zone I received the following message:
>>
>> 'Cannot enable this Zone since: Unable to find the default physical 
>> network with traffic=Public in the specified zone id'
>>
>> As it was an advanced zone with security groups I didn't get the 
>> option to add/configure a public network.
>>
>> > CS Upgrade 2.2.14 to 4.1.0 failed due to no public network found
>> (configuration : advanced network with security groups)
>> >
>> -
>> -
>> --
>> >
>> > Key: CLOUDSTACK-2463
>> > URL:
>> https://issues.apache.org/jira/browse/CLOUDSTACK-2463
>> > Project: CloudStack
>> >  Issue Type: Bug
>> >  Security Level: Public(Anyone can view this level - this is 
>> > the
>> default.)
>> >Affects Versions: 4.1.0
>> >Reporter: Nicolas Lamirault
>> >Assignee: Wei Zhou
>> >Priority: Blocker
>> > Fix For: 4.1.0
>> >
>> >
>> > According Wei Zhou last patch (
>> https://issues.apache.org/jira/browse/CLOUDSTACK-528), i can add a 
>> new secondary storage. The SSVM creation failed due to :
>> > 2013-05-13 15:17:52,868 DEBUG
>> [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) 
>> Zone 1 is ready to launch secondary storage VM
>> > 2013-05-13 15:17:52,879 INFO
>> [cloud.secstorage.PremiumSecondaryStorageManagerImpl]
>> (secstorage-1:null) No running secondary storage vms found in 
>> datacenter id=1, starting one
>> > 2013-05-13 15:17:52,889 INFO
>> [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) 
>> No stopped secondary storage vm is available, need to allocate a new 
>> secondary storage vm
>> > 2013-05-13 15:17:52,894 DEBUG
>> [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) 
>> Assign secondary storage vm from a newly started instance for request 
>> from data center : 1
>> > 2013-05-13 15:17:52,922 WARN [cloud.vm.SystemVmLoadScanner]
>> (secstorage-1:null) Unexpected exception Found 22 networks of type 
>> Guest when expect to find 1
>> > com.cloud.utils.exception.CloudRuntimeException: Found 22 networks 
>> > of
>> type Guest when expect to find 1
>> > at
>> com.cloud.storage.secondary.SecondaryStorageManagerImpl.createSecStor
>> a
>> geVmInstance(SecondaryStorageManagerImpl.java:552)
>> > at
>> com.cloud.storage.secondary.SecondaryStorageManagerImpl.startNew(Seco
>> n
>> daryStorageManagerImpl

RE: [ACS41] System VMs not syncing time - does this block the release?

[Anthony Xu]

In 3.0.x system VM template, /proc/sys/xen/independent_wallclock is set to 0, 
that means system VM is using dom0 time, it is always synced with dom0 time.
In 4.2 system VM template,  /proc/sys/xen/independent_wallclock doesn't exist,  
looks like it is 1 by default by checking 
http://wiki.xensource.com/wiki/Xen_FAQ_DomU#How_can_i_synchronize_a_dom0_clock.3F,
 which might cause time drift, maybe we need to enable NTP inside system VM.

Anthony




-Original Message-
From: John Burwell [mailto:jburw...@basho.com] 
Sent: Wednesday, May 15, 2013 10:30 AM
To: dev@cloudstack.apache.org
Subject: Re: [ACS41] System VMs not syncing time - does this block the release?

Chiradeep,

The issue I am experiencing is that the system VMs are not syncing to dom0 on 
devcloud (i.e. the dom0 clock and the SSVM clock are different).  As I 
mentioned earlier in this thread, the syncing was working previously which 
seems to jibe with your findings.  What mechanism is used to sync the dom0 and 
domU clocks (e.g. NTP, kernel driver, etc)?  It may be a situation where the 
pieces are present, but they aren't configured properly or simply not running.

As an aside, we can not run VirtualBox Additions on devcloud due a conflict 
with the Xen kernel.  Therefore, I hard execute "ntpdate pool.ntp.org"
periodically on the devcloud host to keep the clock synced with the "real 
world".  Another approach is to configure NTP with a very large drift and 
increase check frequency to accomodate the large clock swings that can occur.

Thanks,
-John


On Wed, May 15, 2013 at 1:21 PM, Chiradeep Vittal < 
chiradeep.vit...@citrix.com> wrote:

> Perhaps this is a problem with DevCloud?
> http://nerdboys.com/2011/03/15/how-to-fix-virtualbox-time-synchonizati
> on-pr
> oblems/
>
>
>
> On 5/15/13 10:17 AM, "Chiradeep Vittal" 
> wrote:
>
> >According to our resident Xen expert, any PV kernel automatically 
> >syncs to the hardware clock on dom0.
> >
> >On 5/15/13 9:50 AM, "John Burwell"  wrote:
> >
> >>Marcus,
> >>
> >>Agreed.  I think we need to add a set of hypervisor agnostic  time 
> >>keeping guidelines to the documentation.  I just wanted to make sure 
> >>there wasn't anything KVM specific that should be added as well.
> >>
> >>Thanks,
> >>-John
> >>
> >>On May 15, 2013, at 12:48 PM, Marcus Sorensen 
> >>wrote:
> >>
> >>> Just the general one that system vms sync their time to the 
> >>> hypervisor, thus admins need to keep the hypervisor time correct. 
> >>> It sounds like that will be the case for all three, if we can manage it.
> >>>
> >>> On Wed, May 15, 2013 at 10:44 AM, John Burwell 
> >>>
> >>>wrote:
>  Marcus,
> 
>  Excellent.  So, it looks like we have KVM resolved.  We just need 
> to address Xen and VMWare now.  Do you think we need to any 
> guidance to the documentation regarding KVM time keeping (e.g. 
> environmental prerequisites)?
> 
>  Thanks,
>  -John
> 
> 
> 
>  On May 15, 2013, at 12:39 PM, Marcus Sorensen 
> 
> wrote:
> 
> > KVM LibvirtComputingResource has been patched in master. Tested 
> > on master, 4.1, and both the acton and current system vm 
> > templates. This patch makes system vms use 'kvmclock' for their 
> > timer, which is a vm driver that gets it's time from the 
> > hypervisor. No change to the system vm template itself.
> >
> > bfc5887a1bf6b41e88dd7a8f9987fcee8d3d9175
> >
> > On Wed, May 15, 2013 at 9:08 AM, Chip Childers 
> >  wrote:
> >> On Wed, May 15, 2013 at 11:03:16AM -0400, John Burwell wrote:
> >>> Chip,
> >>>
> >>> One other item I neglected to mention was that clock sync, at 
> >>>least for Xen system VMs, wasn't an issue in the Jan-Feb timeframe.
> >>>Previously when I encountered these issues, syncing the host's 
> >>>clock and rebuilding the system VMs addressed the issue.  I 
> >>>assumed, but never verified, that the SSVM was syncing back 
> >>>against the host's clock through hypervisor.  During my testing 
> >>>yesterday, aside from hard setting the clock, I was unable to 
> >>>force clock sync on the SSVM.
> >>>
> >>> Thanks,
> >>> -John
> >>
> >> I think that's our issue right now...  answering the question: 
> >>Why is  this only an issue now?  Did we just get lucky up to 
> >>this point?
> >>Since
> >> the SSVMs are the same template as the timeframe you mention, I 
> >>tend to  believe that you / we were just lucky.
> >>
> >> Anyone else have thoughts?
> >>
> >>>
> >>> On May 15, 2013, at 10:18 AM, Chip Childers 
> >>> wrote:
> >>>
>  Starting a thread on this specific issue.
> 
>  CLOUDSTACK-2492 was opened, which is basically the fact that 
> the System  VMs aren't syncing time to the host or to an NTP 
> server.  The S3  integration is broken because of this 
> problem, and therefore could not  be considered a func

RE: [ACS41] Discuss CLOUDSTACK-2463 being resolved in 4.1 vs 4.2

[Anthony Xu]

I'll work on 4.2, after that, people can merge it to 4.1.

Anthony

-Original Message-
From: Chip Childers [mailto:chip.child...@sungard.com] 
Sent: Wednesday, May 15, 2013 9:25 AM
To: dev@cloudstack.apache.org
Subject: Re: [ACS41] Discuss CLOUDSTACK-2463 being resolved in 4.1 vs 4.2

On Wed, May 15, 2013 at 09:20:06AM -0700, Alex Huang wrote:
> I'm a very strong believer that CloudStack releases should always be 
> upgradable from previous releases.  We can't strand our user base on a 
> previous release.

Agreed conceptually.  Let's be clear though...  these users have been stranded 
for many versions now.

I'm OK with focusing on fixing this for 4.1.0...  but we need someone(s) to 
commit to doing the work.

> 
> --Alex
> 
> > -Original Message-
> > From: Wei ZHOU [mailto:ustcweiz...@gmail.com]
> > Sent: Wednesday, May 15, 2013 8:28 AM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [ACS41] Discuss CLOUDSTACK-2463 being resolved in 4.1 
> > vs 4.2
> > 
> > Half of our platforms are on 2.2.14 (advanced zone with security groups).
> > These platform work well. We are looking for a way to upgrade to 4.* 
> > for more functionalities, so that we do not need to take the 
> > difference of cloudstack version into account in development.
> > 
> > As I know, the citrix guys are working on this. Jessica Wang said 
> > the feature will be merged into master branch soon.It looks the coding is 
> > almost done.
> > 
> > I hope this feature could be included in 4.1, of course. However, we 
> > also need some days for testing and bug fix. It means cloudstack 4.1 
> > will delay for uncertain days (it is very bad, right?). It is a difficult 
> > choice.
> > 
> > I do not know how many companies are using 2.2.14  (advanced zone 
> > with security groups) and eager to upgrade. I will join the dev and 
> > testing if needed.
> > 
> > 
> > 2013/5/15 Chip Childers 
> > 
> > > Sebastian re-opened CLOUDSTACK-2463 due to users wanting to 
> > > upgrade from 2.x to 4.1.  This relates to the security groups 
> > > feature being available when using VLANs in an advanced networking 
> > > zone.  This feature was apparently broken in the 3.x series, and 
> > > is not slated to be reintroduced until 4.2.
> > >
> > > This is a horrible situation, and one that we've now encountered 
> > > for a third time.
> > >
> > > IMO, we have 2 very specific options:
> > >
> > > 1) We pull that new feature into 4.1, and do the relevant testing.
> > >
> > > 2) We do not pull that feature into 4.1, and release as is with a 
> > > strong message in the release notes highlighting that we know that 
> > > 2.x to 4.1 will not support it (and state that those users 
> > > requiring the feature should wait for 4.2).
> > >
> > > At this point, I don't have a preference.  We probably need to 
> > > understand the effort for (1), as well as understand who would do 
> > > that work (dev AND testing).
> > >
> > > Thoughts?
> > >
> > > -chip
> > >
> 

RE: [ACS41] Discuss CLOUDSTACK-2463 being resolved in 4.1 vs 4.2

[Anthony Xu]

I'm afraid it might introduce extra effort to allow them to use SG again if 
they manage to upgrade to 4.1.
I already checked in the patch in 4-2-advanced-zone-security-group from master 
and did some basic tests.
Wei Zhou kindly agreed to do more tests in that branch and add some integration 
test cases. I think after this we can merge this branch to master and 4.1.

Thanks
Anthony



-Original Message-
From: Chip Childers [mailto:chip.child...@sungard.com] 
Sent: Thursday, May 16, 2013 7:01 AM
To: dev@cloudstack.apache.org
Cc: Anthony Xu
Subject: Re: [ACS41] Discuss CLOUDSTACK-2463 being resolved in 4.1 vs 4.2

On Thu, May 16, 2013 at 03:59:06PM +0200, nicolas.lamira...@orange.com wrote:
> Le 16/05/2013 15:56, Chip Childers a écrit :
> >If we were able to upgrade you correctly to 4.1, but security groups 
> >were not yet functional, would that suffice?
> 
> yes.

Anthony,

Since VMware support for SG's in Advanced zones isn't in your current scope for 
the feature work, is there a method to enable an upgrade if SG's aren't 
actually in use but the user's are blocked from upgrades now?

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_

RE: faketime?

[Anthony Xu]

XS used to save local time(not GMC) into VHD file, it is fine with XS pool , 
because normally all hosts in a XS pool have same time zone. But in Cloudstack, 
Cloudstack might move volume (VHD file) to different cluster (XS pool) with 
different time zone, which may cause timestamp in VHD file is in the future 
compared to the XS host, XS consider this VHD file as invalid. Faketime is a 
workaround for this.

XS fixed this issue in XS 6.2.  Maybe after the EOL of XS version before XS 
6.2, we can remove faketime.


Anthony

-Original Message-
From: Chiradeep Vittal 
Sent: Thursday, February 27, 2014 10:30 PM
To: dev@cloudstack.apache.org
Cc: Anthony Xu
Subject: Re: faketime?

XenServer does not like it if the timestamp in the vhd metadata is in the 
future. This can happen when templates are created in a timezone that is ahead 
and made available to an XS that is in an earlier timezone..

On 2/27/14, 8:00 AM, "Daan Hoogland"  wrote:

>LS,
>
>Why do we use faketime in the template conversion for xen? It seems 
>unnecessary.
>
>$ faketime 2010-01-01 vhd-util convert -s 0 -t 1 -i img.raw -o 
>stagefixed.vhd Fail to get source file size.
>Fail to convert RAW disk to VHD fixed disk.
>
>$ faketime 2014-01-01 vhd-util convert -s 0 -t 1 -i img.raw -o 
>stagefixed.vhd Fail to get source file size.
>Fail to convert RAW disk to VHD fixed disk.
>
>$ vhd-util convert -s 0 -t 1 -i img.raw -o stagefixed.vhd
>NOTE: For better performance, we will do the overwritten convert!
>Done! Convert to stagefixed.vhd.
>
>the second call of faketime is not in the way, so I don't mind that 
>one;)
>
>--
>Daan

[PROPOSAL] Use XS HA to swithc XS master host when master host is down

[Anthony Xu]

Hi All,
I would like to propose using XS HA to switch XS master host when XS master 
host is down

Reason,
We found below issue recently,
https://issues.apache.org/jira/browse/CLOUDSTACK-6177

When XS master is down, CS uses pool-emergency-transition-to-master and 
pool-recover-slaves API to choose a new master, this API is not safe, and 
should be only used in emergent situation, this API may cause XS use a little 
bit old(5 seconds old) version of XS DB, some of object may be missing in the 
old XS DB, which may cause weird behavior, you may not be able to start VM.


Short term solution

CS doesn't do XS master switch any more to avoid this issue.

Impact,

1.  When master host is down, CS loses connect to the whole XS pool(CS 
cluster), CS cannot get VMs info in this cluster, and the whole cluster is not 
operable.

2.  Require admin to recover the XS master host manually, if recovering XS 
master host is not possible, admin can use uses 
pool-emergency-transition-to-master and pool-recover-slaves to recover the 
pool, per the issue I mentioned before , this should be the last resort.

Long term solution

Integrate XS HA, use XS HA to do XS master switch.

1.  It might take  some time to integrate XS HA.

2.  Old free version XS doesn't have XS HA feature, user might need to 
upgrade to XS 6.2( which is free) to get the feature.


I think we can fix this issue in two steps.

1.  Since this issue is very critical, CS should not  do XS master switch 
immediately to avoid this issue.

2.  Integrate XS HA.


Comments, suggestions are highly appreciated!

Best Regards.
Anthony

RE: Exception adding XenServer host to CS

[Anthony Xu]

Hi Mike,

If you are using Security group enabled zone or basic zone, you need to switch 
XS network mode from OVS to bridge since security group doesn't work on OVS.

xe-switch-network-backend bridge.


Anthony

-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
Sent: Monday, March 03, 2014 12:39 PM
To: dev@cloudstack.apache.org; jaya...@apache.org
Subject: Re: Exception adding XenServer host to CS

Hi Jayapal,

I was wondering if this commit could be the reason why people can no longer add 
XenServer hosts to clusters?

4b3784a98e57bc22bc0a8dd53462d452c322cb8c

In my case, _canBridgeFirewall is false and so an exception is thrown.

Please let me know what you think.

Thanks!

Mike


On Mon, Mar 3, 2014 at 12:35 PM, Mike Tutkowski < mike.tutkow...@solidfire.com> 
wrote:

> It looks like this problem has existed since at least February 5th. 
> I'm currently in the process of building and running the codebase 
> based on old commits to see where this was introduced.
>
>
> On Mon, Mar 3, 2014 at 11:33 AM, Mike Tutkowski < 
> mike.tutkow...@solidfire.com> wrote:
>
>> Thanks, Sheng!
>>
>>
>> On Mon, Mar 3, 2014 at 11:28 AM, Sheng Yang  wrote:
>>
>>> Sorry for just notice your issue. But it's unrelated to my chance.
>>>
>>> The scripts I deleted are scripts used to access the VR, not the 
>>> host... So I don't think it's the cause of your issue. These files 
>>> has been replaced by executing in the VR directly. I would remove 
>>> the wrong warnings.
>>>
>>> can_bridge_firewall() called vmops plugin rather than the files you 
>>> listed.
>>>
>>> Maybe take a look at /var/log/SMlog would give more details?
>>>
>>> --Sheng
>>>
>>> On Mon, Mar 3, 2014 at 10:18 AM, Mike Tutkowski 
>>>  wrote:
>>> > Hi Sheng,
>>> >
>>> > It looks like you removed these scripts on January 16th, 17th, and
>>> 20th.
>>> >
>>> > Any chance this could be the cause of the bug we're seeing where
>>> XenServer
>>> > hosts cannot be added to a cluster?
>>> >
>>> > Thanks!
>>> >
>>> >
>>> > On Mon, Mar 3, 2014 at 10:47 AM, Mike Tutkowski < 
>>> > mike.tutkow...@solidfire.com> wrote:
>>> >
>>> >> bumpUpPriority.sh and dhcp_entry.sh were deleted in
>>> >>
>>> >> 0cdf0f6f67c99a06fc1b94c2f2a38eff020f3f67
>>> >>
>>> >> call_loadbalancer.shh was deleted in
>>> >>
>>> >> e88cc488e5a9011f2c199f906bb0dacdb95685d7
>>> >>
>>> >> save_password_to_domr.sh was deleted in
>>> >>
>>> >> ca81e7b465fb40866fd14d1d1d27a2c42e1a2741
>>> >>
>>> >>
>>> >> On Mon, Mar 3, 2014 at 10:42 AM, Mike Tutkowski < 
>>> >> mike.tutkow...@solidfire.com> wrote:
>>> >>
>>> >>> It looks like, for example, call_firewall.sh was deleted in
>>> >>>
>>> >>> 0ea1c7dfc411db0d3710ac2c4fb238111cbec328
>>> >>>
>>> >>>
>>> >>> On Mon, Mar 3, 2014 at 10:27 AM, Mike Tutkowski < 
>>> >>> mike.tutkow...@solidfire.com> wrote:
>>> >>>
>>>  OK, I've had a bit of time to investigate this.
>>> 
>>>  I noticed in CitrixResourceBase that can_bridge_firewall (which
>>> calls a
>>>  plug-in on the XenServer host) returns false:
>>> 
>>>   if (_securityGroupEnabled) {
>>> 
>>>  _canBridgeFirewall = can_bridge_firewall(conn);
>>> 
>>>  if (!_canBridgeFirewall) {
>>> 
>>>  String msg = "Failed to configure brige
>>> firewall";
>>> 
>>>  s_logger.warn(msg);
>>> 
>>>  s_logger.warn("Check host " + _host.ip +" 
>>>  for
>>> CSP
>>>  is installed or not and check network mode for bridge");
>>> 
>>>  return new SetupAnswer(cmd, msg);
>>> 
>>>  }
>>> 
>>> 
>>>  }
>>> 
>>> 
>>>  Right before this code, the XenServer server resource tries to 
>>>  copy
>>> a
>>>  bunch of files to the XenServer host, but several of these 
>>>  files
>>> cannot be
>>>  found on the CS management server:
>>> 
>>>  WARN  [c.c.h.x.r.CitrixResourceBase] 
>>>  (DirectAgent-1:ctx-33a9d930) We cannot locate
>>> 
>>> /home/mtutkowski/CloudStack/client/target/generated-webapp/WEB-INF/c
>>> lasses/scripts/vm/hypervisor/xenserver/xenserver60/../../../../netwo
>>> rk/domr//call_firewall.sh
>>>  WARN  [c.c.h.x.r.CitrixResourceBase] 
>>>  (DirectAgent-1:ctx-33a9d930) We cannot locate
>>> 
>>> /home/mtutkowski/CloudStack/client/target/generated-webapp/WEB-INF/c
>>> lasses/scripts/vm/hypervisor/xenserver/xenserver60/../../../../netwo
>>> rk/domr//bumpUpPriority.sh
>>>  WARN  [c.c.h.x.r.CitrixResourceBase] 
>>>  (DirectAgent-1:ctx-33a9d930) We cannot locate
>>> 
>>> /home/mtutkowski/CloudStack/client/target/generated-webapp/WEB-INF/c
>>> lasses/scripts/vm/hypervisor/xenserver/xenserver60/../../../../netwo
>>> rk/domr//dhcp_entry.sh
>>>  WARN  [c.c.h.x.r.CitrixResourceBase] 
>>>  (DirectAgent-1:ctx-33a9d930) We cannot locate
>>> 
>>> /home/mtutkowski/CloudStack/client/target/generated-we

RE: Exception adding XenServer host to CS

[Anthony Xu]

>Do people have to run xe-switch-network-backend bridge before upgrading to
>4.4 (if they are using a Basic Zone)?
Correct.

>In my case, since I'm developing and able to start with a fresh DB and 
>XenServer hosts, it looks like I can just run xe-switch-network-backend bridge 
>before I create my zone, right?
Correct,

BTW,  reboot XS host is required to make the change take effect.

Anthony


-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
Sent: Monday, March 03, 2014 2:52 PM
To: dev@cloudstack.apache.org
Cc: jaya...@apache.org
Subject: Re: Exception adding XenServer host to CS

Hi Anthony,

Thanks for the reply.

It looks like this is a change in 4.4.

Do people have to run xe-switch-network-backend bridge before upgrading to
4.4 (if they are using a Basic Zone)?

In my case, since I'm developing and able to start with a fresh DB and 
XenServer hosts, it looks like I can just run xe-switch-network-backend bridge 
before I create my zone, right?

Thanks!
Mike


On Mon, Mar 3, 2014 at 3:45 PM, Anthony Xu  wrote:

> Hi Mike,
>
> If you are using Security group enabled zone or basic zone, you need 
> to switch XS network mode from OVS to bridge since security group 
> doesn't work on OVS.
>
> xe-switch-network-backend bridge.
>
>
> Anthony
>
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Monday, March 03, 2014 12:39 PM
> To: dev@cloudstack.apache.org; jaya...@apache.org
> Subject: Re: Exception adding XenServer host to CS
>
> Hi Jayapal,
>
> I was wondering if this commit could be the reason why people can no 
> longer add XenServer hosts to clusters?
>
> 4b3784a98e57bc22bc0a8dd53462d452c322cb8c
>
> In my case, _canBridgeFirewall is false and so an exception is thrown.
>
> Please let me know what you think.
>
> Thanks!
>
> Mike
>
>
> On Mon, Mar 3, 2014 at 12:35 PM, Mike Tutkowski < 
> mike.tutkow...@solidfire.com> wrote:
>
> > It looks like this problem has existed since at least February 5th.
> > I'm currently in the process of building and running the codebase 
> > based on old commits to see where this was introduced.
> >
> >
> > On Mon, Mar 3, 2014 at 11:33 AM, Mike Tutkowski < 
> > mike.tutkow...@solidfire.com> wrote:
> >
> >> Thanks, Sheng!
> >>
> >>
> >> On Mon, Mar 3, 2014 at 11:28 AM, Sheng Yang  wrote:
> >>
> >>> Sorry for just notice your issue. But it's unrelated to my chance.
> >>>
> >>> The scripts I deleted are scripts used to access the VR, not the 
> >>> host... So I don't think it's the cause of your issue. These files 
> >>> has been replaced by executing in the VR directly. I would remove 
> >>> the wrong warnings.
> >>>
> >>> can_bridge_firewall() called vmops plugin rather than the files 
> >>> you listed.
> >>>
> >>> Maybe take a look at /var/log/SMlog would give more details?
> >>>
> >>> --Sheng
> >>>
> >>> On Mon, Mar 3, 2014 at 10:18 AM, Mike Tutkowski 
> >>>  wrote:
> >>> > Hi Sheng,
> >>> >
> >>> > It looks like you removed these scripts on January 16th, 17th, 
> >>> > and
> >>> 20th.
> >>> >
> >>> > Any chance this could be the cause of the bug we're seeing where
> >>> XenServer
> >>> > hosts cannot be added to a cluster?
> >>> >
> >>> > Thanks!
> >>> >
> >>> >
> >>> > On Mon, Mar 3, 2014 at 10:47 AM, Mike Tutkowski < 
> >>> > mike.tutkow...@solidfire.com> wrote:
> >>> >
> >>> >> bumpUpPriority.sh and dhcp_entry.sh were deleted in
> >>> >>
> >>> >> 0cdf0f6f67c99a06fc1b94c2f2a38eff020f3f67
> >>> >>
> >>> >> call_loadbalancer.shh was deleted in
> >>> >>
> >>> >> e88cc488e5a9011f2c199f906bb0dacdb95685d7
> >>> >>
> >>> >> save_password_to_domr.sh was deleted in
> >>> >>
> >>> >> ca81e7b465fb40866fd14d1d1d27a2c42e1a2741
> >>> >>
> >>> >>
> >>> >> On Mon, Mar 3, 2014 at 10:42 AM, Mike Tutkowski < 
> >>> >> mike.tutkow...@solidfire.com> wrote:
> >>> >>
> >>> >>> It looks like, for example, call_firewall.sh was deleted in
> >>> >>>
> >>> &

RE: [ACS4.3] Schedule reminder : 10 days to code freeze

[Anthony Xu]

4.3/4.4?



-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
Sent: Tuesday, November 26, 2013 9:20 PM
To: dev@cloudstack.apache.org
Subject: [ACS4.3] Schedule reminder : 10 days to code freeze

Folks

We are now 10 days from ACS 4.3 code freeze and our bug fix activity is very 
slow. If you have any issues assigned to you please try to resolve them ASAP 
and help close the unassigned issues.

For detailed report visit the release dashboard [1]

[1] https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12321625

Thanks
Animesh

RE: [4.4]copy_vhd_from_secondarystorage is timing out

[Anthony Xu]

Hi Murali,

It is caused by the commit, I tested the commit on XS 6.2 FOX, which doesn't 
use copy_vhd_from_secondarystorage, that's why I didn't see this issue.

Just disabled XAPI Event in 4.4 branch.


Thanks,
Anthony






-Original Message-
From: Murali Reddy 
Sent: Tuesday, April 15, 2014 10:54 AM
To: dev@cloudstack.apache.org; Anthony Xu
Subject: Re: [4.4]copy_vhd_from_secondarystorage is timing out


I am still running into this issue. Alex reverted complete change replacing 
xapi.jar, which was also resulting XmlRpc exceptions but system VM's were 
launching fine after revert. I may be wrong but looking at the stack trace and 
recent commits, commit
9f44909e63a19b2b8034baa13b92e24ea2eb0227 (use event instead of poll for xapi 
async call in XS 6.2 and above to reduce the pressure on XAPI) may be causing 
this issue. Anthony can you please take a look?


On 14/04/14 8:12 AM, "Mike Tutkowski"  wrote:

>I was seeing a similar issue when XAPI was changed when I tried to 
>create an SR.
>
>I wonder if that XAPI issue hasn't been fully resolved.
>
>
>On Sun, Apr 13, 2014 at 4:16 PM, Srikanteswararao Talluri < 
>srikanteswararao.tall...@citrix.com> wrote:
>
>> Did anybody see this on latest 4.4?
>>
>>
>> 2014-04-14 00:01:34,305 DEBUG [c.c.h.x.r.XenServerConnectionPool]
>> (DirectAgent-71:ctx-12d9be59) XmlRpcException for method: event.from 
>>due to
>> org.apache.xmlrpc.XmlRpcException: Failed to create input stream: 
>>Read  timed out
>>
>> 2014-04-14 00:01:34,305 WARN  [c.c.h.x.r.CitrixResourceBase]
>> (DirectAgent-71:ctx-12d9be59) callHostPlugin failed for cmd:
>> copy_vhd_from_secondarystorage with args mountpoint:
>>10.147.28.7:/export/home/talluri/psec/template/tmpl/1/1/,
>> sruuid: b3dd21aa-8e82-a923-ed29-ee58220d158b, namelabel:
>> cloud-8498d88f-be6b-41b6-bece-a58bbc1fbc32,  due to Failed to create 
>>input
>> stream: Read timed out
>>
>> org.apache.xmlrpc.XmlRpcException: Failed to create input stream: 
>> Read timed out
>>
>> at
>> 
>>org.apache.xmlrpc.client.XmlRpcSunHttpTransport.getInputStream(XmlRpcS
>>unH
>>ttpTransport.java:99)
>>
>> at
>> 
>>org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStrea
>>mTr
>>ansport.java:152)
>>
>> at
>> 
>>org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTra
>>nsp
>>ort.java:143)
>>
>> at
>> 
>>org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunH
>>ttp
>>Transport.java:69)
>>
>> at
>> 
>>org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker
>>.ja
>>va:56)
>>
>> at
>> org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:167)
>>
>> at
>> org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:137)
>>
>> at
>> org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:126)
>>
>> at 
>> com.xensource.xenapi.Connection.dispatch(Connection.java:285)
>>
>> at
>> 
>>com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerCon
>>nec
>>tion.dispatch(XenServerConnectionPool.java:456)
>>
>> at com.xensource.xenapi.Event.properFrom(Event.java:310)
>>
>> at
>> 
>>com.cloud.hypervisor.xen.resource.XenServer620Resource.waitForTask(Xen
>>Ser
>>ver620Resource.java:125)
>>
>> at
>> 
>>com.cloud.hypervisor.xen.resource.CitrixResourceBase.callHostPluginAsy
>>nc(
>>CitrixResourceBase.java:3558)
>>
>> at
>> 
>>com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copy_vhd_f
>>rom
>>_secondarystorage(XenServerStorageProcessor.java:826)
>>
>> at
>> 
>>com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTempla
>>teT
>>oPrimaryStorage(XenServerStorageProcessor.java:962)
>>
>> at
>> 
>>com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(
>>Sto
>>rageSubsystemCommandHandlerBase.java:77)
>>
>> at
>> 
>>com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleSt
>>ora
>>geCommands(StorageSubsystemCommandHandlerBase.java:52)
>>
>> at
>> 
>>com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(Ci
>>tri
>>xResourceBase.java:542)
>>
>> at
>> 
>>com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(X
>

RE: [4.4]copy_vhd_from_secondarystorage is timing out

[Anthony Xu]

Just checked in a fix for this.
change xapitimeout to 600 second,
looks like we need to change some XAPI calls to Async before shorten the timeout


Anthony

From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Wednesday, April 16, 2014 7:27 AM
To: Murali Reddy
Cc: Anthony Xu; dev@cloudstack.apache.org
Subject: Re: [4.4]copy_vhd_from_secondarystorage is timing out

This is a similar problem to what I sent an e-mail out about last night: 
XmlRpcException (Read timed out). For me it's happening when CitrixResourceBase 
issues SR.create.

This issue is currently blocking my testing progress and I'm not really sure 
who might be the right person to look into this.

Any thoughts on this anyone?

On Wed, Apr 16, 2014 at 1:51 AM, Murali Reddy 
mailto:murali.re...@citrix.com>> wrote:
System VM's are launching fine now after Anthony's fix. But user VM's are 
failing to get created with exception.

43275 2014-04-16 12:59:08,647 DEBUG [c.c.h.x.r.XenServerConnectionPool] 
(DirectAgent-137:ctx-4761cb0c) XmlRpcException for method: VDI.snapshot due to 
org.apache.xmlrpc.XmlRpcException: Failed to create input stream: Read timed out
43276 2014-04-16 12:59:08,647 WARN [c.c.h.x.r.XenServerStorageProcessor] 
(DirectAgent-137:ctx-4761cb0c) Catch Exception 
org.apache.xmlrpc.XmlRpcException for template + due to 
org.apache.xmlrpc.XmlRpcException: Failed to create input stream: Read timed out

org.apache.xmlrpc.XmlRpcException: Failed to create input stream: Read timed out
org.apache.xmlrpc.XmlRpcException: Failed to create input stream: Read timed out
at 
org.apache.xmlrpc.client.XmlRpcSunHttpTransport.getInputStream(XmlRpcSunHttpTransport.java:99)
at 
org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:152)
at 
org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTransport.java:143)
at 
org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpTransport.java:69)
at 
org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:56)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:167)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:137)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:126)
at com.xensource.xenapi.Connection.dispatch(Connection.java:285)
at 
com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:456)
at com.xensource.xenapi.VDI.snapshot(VDI.java:1155)
at 
com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTemplateToPrimaryStorage(XenServerStorageProcessor.java:972)
at 
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:77)

From: Mike Tutkowski 
mailto:mike.tutkow...@solidfire.com>>
Date: Wednesday, 16 April 2014 12:35 AM
To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" 
mailto:dev@cloudstack.apache.org>>
Cc: Murali Reddy mailto:murali.re...@citrix.com>>

Subject: Re: [4.4]copy_vhd_from_secondarystorage is timing out

Hi Anthony,

Can you go into a bit more depth about copy_vhd_from_secondarystorage not being 
used with XenServer 6.2?

Does that mean "public Answer copyTemplateToPrimaryStorage(CopyCommand cmd)" in 
XenServerStorageProcessor is not called when XenServer 6.2 is in use?

I'm testing out a feature of mine for 4.4, but have only been using XenServer 
6.1 so far.

Thanks!
Mike

On Tue, Apr 15, 2014 at 12:44 PM, Anthony Xu 
mailto:xuefei...@citrix.com>> wrote:
Hi Murali,

It is caused by the commit, I tested the commit on XS 6.2 FOX, which doesn't 
use copy_vhd_from_secondarystorage, that's why I didn't see this issue.

Just disabled XAPI Event in 4.4 branch.


Thanks,
Anthony






-Original Message-
From: Murali Reddy
Sent: Tuesday, April 15, 2014 10:54 AM
To: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>; Anthony Xu
Subject: Re: [4.4]copy_vhd_from_secondarystorage is timing out


I am still running into this issue. Alex reverted complete change replacing 
xapi.jar, which was also resulting XmlRpc exceptions but system VM's were 
launching fine after revert. I may be wrong but looking at the stack trace and 
recent commits, commit
9f44909e63a19b2b8034baa13b92e24ea2eb0227 (use event instead of poll for xapi 
async call in XS 6.2 and above to reduce the pressure on XAPI) may be causing 
this issue. Anthony can you please take a look?


On 14/04/14 8:12 AM, "Mike Tutkowski" 
mailto:mike.tutkow...@solidfire.com>> wrote:

>I was seeing a similar issue when XAPI was changed when I tried to
>create an SR.
>
>I wonder if that XAPI issue hasn't been fully resolved.
>
>
>On Sun, Apr 13, 2014 at 4:16 PM, Srikanteswararao Talluri <
>srikanteswararao.tall...@citrix.com<mailto:srikanteswararao.tall...@citrix.com>>
> wrote:
>

RE: [4.4]copy_vhd_from_secondarystorage is timing out

[Anthony Xu]

I think you need to change value in DB configuration, changing the java code 
will not change the value in DB if the DB is already initialized.


+--+--+--+--+---+--+---+-+---++
| Advanced | DEFAULT  | AgentManager | xapiwait | 60| Time (in seconds) to 
wait for XAPI to return | NULL  | NULL| NULL  |  0 |

From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Wednesday, April 16, 2014 11:09 AM
To: Anthony Xu
Cc: Murali Reddy; dev@cloudstack.apache.org
Subject: Re: [4.4]copy_vhd_from_secondarystorage is timing out

Thanks, Anthony

I will need to re-test. I changed that value from 60 to 600 last night and 
still saw an issue.

Maybe I'll just start over from scratch and see if all is well.

Thanks for the follow-up!

On Wed, Apr 16, 2014 at 12:05 PM, Anthony Xu 
mailto:xuefei...@citrix.com>> wrote:
Just checked in a fix for this.
change xapitimeout to 600 second,
looks like we need to change some XAPI calls to Async before shorten the timeout


Anthony

From: Mike Tutkowski 
[mailto:mike.tutkow...@solidfire.com<mailto:mike.tutkow...@solidfire.com>]
Sent: Wednesday, April 16, 2014 7:27 AM
To: Murali Reddy
Cc: Anthony Xu; dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>

Subject: Re: [4.4]copy_vhd_from_secondarystorage is timing out

This is a similar problem to what I sent an e-mail out about last night: 
XmlRpcException (Read timed out). For me it's happening when CitrixResourceBase 
issues SR.create.

This issue is currently blocking my testing progress and I'm not really sure 
who might be the right person to look into this.

Any thoughts on this anyone?

On Wed, Apr 16, 2014 at 1:51 AM, Murali Reddy 
mailto:murali.re...@citrix.com>> wrote:
System VM's are launching fine now after Anthony's fix. But user VM's are 
failing to get created with exception.

43275 2014-04-16 12:59:08,647 DEBUG [c.c.h.x.r.XenServerConnectionPool] 
(DirectAgent-137:ctx-4761cb0c) XmlRpcException for method: VDI.snapshot due to 
org.apache.xmlrpc.XmlRpcException: Failed to create input stream: Read timed out
43276 2014-04-16 12:59:08,647 WARN [c.c.h.x.r.XenServerStorageProcessor] 
(DirectAgent-137:ctx-4761cb0c) Catch Exception 
org.apache.xmlrpc.XmlRpcException for template + due to 
org.apache.xmlrpc.XmlRpcException: Failed to create input stream: Read timed out

org.apache.xmlrpc.XmlRpcException: Failed to create input stream: Read timed out
org.apache.xmlrpc.XmlRpcException: Failed to create input stream: Read timed out
at 
org.apache.xmlrpc.client.XmlRpcSunHttpTransport.getInputStream(XmlRpcSunHttpTransport.java:99)
at 
org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:152)
at 
org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTransport.java:143)
at 
org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpTransport.java:69)
at 
org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:56)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:167)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:137)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:126)
at com.xensource.xenapi.Connection.dispatch(Connection.java:285)
at 
com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:456)
at com.xensource.xenapi.VDI.snapshot(VDI.java:1155)
at 
com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTemplateToPrimaryStorage(XenServerStorageProcessor.java:972)
at 
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:77)

From: Mike Tutkowski 
mailto:mike.tutkow...@solidfire.com>>
Date: Wednesday, 16 April 2014 12:35 AM
To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" 
mailto:dev@cloudstack.apache.org>>
Cc: Murali Reddy mailto:murali.re...@citrix.com>>

Subject: Re: [4.4]copy_vhd_from_secondarystorage is timing out

Hi Anthony,

Can you go into a bit more depth about copy_vhd_from_secondarystorage not being 
used with XenServer 6.2?

Does that mean "public Answer copyTemplateToPrimaryStorage(CopyCommand cmd)" in 
XenServerStorageProcessor is not called when XenServer 6.2 is in use?

I'm testing out a feature of mine for 4.4, but have only been using XenServer 
6.1 so far.

Thanks!
Mike

On Tue, Apr 15, 2014 at 12:44 PM, Anthony Xu 
mailto:xuefei...@citrix.com>> wrote:
Hi Murali,

It is caused by the commit, I tested the commit on XS 6.2 FOX, which doesn't 
use copy_vhd_from_secondarystorage, that's why I didn't see this issue.

Just disabled XAPI Event in 4.4 branch.


Thanks,
Anthony






-Original Message-
From: Murali Reddy
Sent: Tuesday, April 15, 2014 10:54 AM
To:

RE: [4.4]copy_vhd_from_secondarystorage is timing out

[Anthony Xu]

Normally , SR.scan will not take too long, if SR.scan times out after 600 
seconds, I think there might be some problems with the SR,  I think you need to 
fix the SR issue first.
You can execute xe sr-scan in any XS hosts to see what's the problem.


Anthony

-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
Sent: Wednesday, April 16, 2014 11:21 AM
To: Anthony Xu
Cc: Murali Reddy; dev@cloudstack.apache.org
Subject: Re: [4.4]copy_vhd_from_secondarystorage is timing out

What I had done was change the xapiwait (or something like that) global setting 
and then re-start my management server.


On Wed, Apr 16, 2014 at 12:19 PM, Mike Tutkowski < 
mike.tutkow...@solidfire.com> wrote:

> Ah, that's probably it. Thanks!
>
>
> On Wed, Apr 16, 2014 at 12:11 PM, Anthony Xu  wrote:
>
>>  I think you need to change value in DB configuration, changing the 
>> java code will not change the value in DB if the DB is already initialized.
>>
>>
>>
>>
>>
>>
>> +--+--+--+--+---+--+---+-+---++
>>
>> | Advanced | DEFAULT  | AgentManager | xapiwait | 60| Time (in
>> seconds) to wait for XAPI to return | NULL  | NULL| NULL
>> |  0 |
>>
>>
>>
>> *From:* Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> *Sent:* Wednesday, April 16, 2014 11:09 AM
>> *To:* Anthony Xu
>> *Cc:* Murali Reddy; dev@cloudstack.apache.org
>>
>> *Subject:* Re: [4.4]copy_vhd_from_secondarystorage is timing out
>>
>>
>>
>> Thanks, Anthony
>>
>>
>>
>> I will need to re-test. I changed that value from 60 to 600 last 
>> night and still saw an issue.
>>
>>
>>
>> Maybe I'll just start over from scratch and see if all is well.
>>
>>
>>
>> Thanks for the follow-up!
>>
>>
>>
>> On Wed, Apr 16, 2014 at 12:05 PM, Anthony Xu 
>> wrote:
>>
>> Just checked in a fix for this.
>>
>> change xapitimeout to 600 second,
>>
>> looks like we need to change some XAPI calls to Async before shorten 
>> the timeout
>>
>>
>>
>>
>>
>> Anthony
>>
>>
>>
>> *From:* Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> *Sent:* Wednesday, April 16, 2014 7:27 AM
>> *To:* Murali Reddy
>> *Cc:* Anthony Xu; dev@cloudstack.apache.org
>>
>>
>> *Subject:* Re: [4.4]copy_vhd_from_secondarystorage is timing out
>>
>>
>>
>> This is a similar problem to what I sent an e-mail out about last night:
>> XmlRpcException (Read timed out). For me it's happening when 
>> CitrixResourceBase issues SR.create.
>>
>>
>>
>> This issue is currently blocking my testing progress and I'm not 
>> really sure who might be the right person to look into this.
>>
>>
>>
>> Any thoughts on this anyone?
>>
>>
>>
>> On Wed, Apr 16, 2014 at 1:51 AM, Murali Reddy 
>> 
>> wrote:
>>
>> System VM's are launching fine now after Anthony's fix. But user VM's 
>> are failing to get created with exception.
>>
>>
>>
>> 43275 2014-04-16 12:59:08,647 DEBUG 
>> [c.c.h.x.r.XenServerConnectionPool]
>> (DirectAgent-137:ctx-4761cb0c) XmlRpcException for method: 
>> VDI.snapshot due to org.apache.xmlrpc.XmlRpcException: Failed to 
>> create input stream: Read timed out
>>
>> 43276 2014-04-16 12:59:08,647 WARN 
>> [c.c.h.x.r.XenServerStorageProcessor]
>> (DirectAgent-137:ctx-4761cb0c) Catch Exception 
>> org.apache.xmlrpc.XmlRpcException for template + due to
>> org.apache.xmlrpc.XmlRpcException: Failed to create input stream: 
>> Read timed out
>>
>>
>>
>> org.apache.xmlrpc.XmlRpcException: Failed to create input stream: 
>> Read timed out
>>
>> org.apache.xmlrpc.XmlRpcException: Failed to create input stream: 
>> Read timed out
>>
>> at
>> org.apache.xmlrpc.client.XmlRpcSunHttpTransport.getInputStream(XmlRpc
>> SunHttpTransport.java:99)
>>
>> at
>> org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStre
>> amTransport.java:152)
>>
>> at
>> org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTr
>> ansport.java:143)
>>
>> at
>> org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSun
>> HttpTransport.java:69)
>>
>> at
>> org.apache.xmlrpc.client.XmlRpcClientWorker.execute(

RE: Anybody addressing this bug ? Overlaping IP subnets across different vlans

[Anthony Xu]

You can add overlapping IP subnets across different vlans if all vlans belong 
to guest network.

CS treats public network differently, CS doesn't want public subnet overlap 
with other guest network.

If different vlans are routable, it is possible that a VM has the same ip as a 
system VM, public ip is accessible from outside, duplicate ip might cause 
system VMs stop working.

It is very hard for us to help users to recover from this scenarios.

Basically you want to use the same subnet for both public network and guest 
network, maybe basic zone is better fit for you.

Anthony

 




-Original Message-
From: Murali Reddy 
Sent: Wednesday, June 11, 2014 2:45 AM
To: dev@cloudstack.apache.org; Anthony Xu
Subject: Re: Anybody addressing this bug ? Overlaping IP subnets across 
different vlans

This is not related to portable IP. This enforcement was added as part of 
commit 657d9e4789d73c7c8ed460e59f088b8cb9aa7697.

Anothony might have context for this check.

On 11/06/14 2:18 PM, "Andrija Panic"  wrote:

>It was not there pre 4.3, and it's just causing me problems, I had to 
>manually add database entries to vlan and user_ip_address tables, not 
>very convinient...
>Thanks,
>Andrija
>
>
>On 11 June 2014 02:45, Chiradeep Vittal 
>wrote:
>
>> Not sure what this has to do with Portable IP. But I agree that the 
>>check  should be removed.
>>
>> From: ilya musayev > ilya.mailing.li...@gmail.com>>
>> Reply-To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
>><
>> dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
>> Date: Friday, June 6, 2014 at 10:38 AM
>> To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <  
>>dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
>> Subject: Re: Anybody addressing this bug ? Overlaping IP subnets 
>>across  different vlans
>>
>> Andrija
>>
>> I dont know if we can qualify this as a bug, this check was placed 
>> with some purpose in mind - yet its not clear what it is and why 
>> would someone think its bad.
>>
>>
>> 
>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=a3
>>b1a
>>49c303a929c754561ca07fd8a9ed84e0382
>>
>> https://issues.apache.org/jira/browse/CLOUDSTACK-3911
>>
>> Chime in on the discussion in thread above,
>>
>> Regards,
>> ilya
>>
>>
>> On 6/6/14, 5:48 AM, Andrija Panic wrote:
>> Hi,
>> aftger upgrade to 4.3, I reported a bug where CS will not let me add 
>> additional IP ranges when there are 2 vlans using same IP range - 
>> I don't see point comparing IP ranges across two separate broadcast 
>> domains...
>>
>> https://issues.apache.org/jira/browse/CLOUDSTACK-6814
>>
>> Thanks,
>>
>>
>>
>
>
>--
>
>Andrija Panić
>--
>  http://admintweets.com
>--
>

RE: Simulator on master is not building

[Anthony Xu]

We used -Dsimulator to include simulator, it is very easy for developers to 
forget it.  Simulator should be built by default , we may use -Dnosimulator to 
exclude simulator.


Anthony

-Original Message-
From: Koushik Das 
Sent: Wednesday, July 30, 2014 3:03 AM
To: dev@cloudstack.apache.org
Cc: Anthony Xu
Subject: RE: Simulator on master is not building

The simulator code should be kept up to date with any changes done in the core 
product. If there are any interface changes, necessary changes should be made 
in simulator plugin as well along with other hypervisor plugins. To build 
simulator code use refer to [1].

-Koushik

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

-Original Message-
From: Santhosh Edukulla [mailto:santhosh.eduku...@citrix.com] 
Sent: Wednesday, 30 July 2014 3:27 PM
To: dev@cloudstack.apache.org
Cc: Anthony Xu
Subject: Simulator on master is not building

I believe for every check-in we decided to run sanity tests on simulator 
atleast, currently build for simulator is failing. 

 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) 
on project cloud-plugin-hypervisor-simulator: Compilation failure: Compilation 
failure:
[ERROR] 
/home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/resource/AgentRoutingResource.java:[230,8]
 error: 'try' without 'catch', 'finally' or resource declarations [ERROR] 
/home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/resource/AgentRoutingResource.java:[251,8]
 error: 'try' without 'catch', 'finally' or resource declarations


Thanks!
Santhosh

RE: Simulator on master is not building

[Anthony Xu]

Hi Koushik,

fixed the build for simulator.

I just found out Simulator use its own VOes for some VOes, it may not be easy 
for developer to add feature for simulator if the feature needs to change VO, 
for example, the new VMsync logic, I don't think simulator test the new VMsync 
logic. 

If we consider Simulator as a hypervisor, ideally it should use the same VOes 
as other hypersivors. Can you help us understand what's the reason behind this?

Thanks
Anthony







./plugins/hypervisors/simulator/src/com/cloud/simulator/MockVMVO.java
./plugins/hypervisors/simulator/src/com/cloud/simulator/MockSecStorageVO.java
./plugins/hypervisors/simulator/src/com/cloud/simulator/MockVolumeVO.java
./plugins/hypervisors/simulator/src/com/cloud/simulator/MockStoragePoolVO.java
./plugins/hypervisors/simulator/src/com/cloud/simulator/MockHostVO.java
./plugins/hypervisors/simulator/src/com/cloud/simulator/MockConfigurationVO.java
./plugins/hypervisors/simulator/src/com/cloud/simulator/MockSecurityRulesVO.java





-Original Message-----
From: Anthony Xu 
Sent: Wednesday, July 30, 2014 10:28 AM
To: Koushik Das; dev@cloudstack.apache.org
Subject: RE: Simulator on master is not building

We used -Dsimulator to include simulator, it is very easy for developers to 
forget it.  Simulator should be built by default , we may use -Dnosimulator to 
exclude simulator.


Anthony

-Original Message-
From: Koushik Das 
Sent: Wednesday, July 30, 2014 3:03 AM
To: dev@cloudstack.apache.org
Cc: Anthony Xu
Subject: RE: Simulator on master is not building

The simulator code should be kept up to date with any changes done in the core 
product. If there are any interface changes, necessary changes should be made 
in simulator plugin as well along with other hypervisor plugins. To build 
simulator code use refer to [1].

-Koushik

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

-Original Message-
From: Santhosh Edukulla [mailto:santhosh.eduku...@citrix.com] 
Sent: Wednesday, 30 July 2014 3:27 PM
To: dev@cloudstack.apache.org
Cc: Anthony Xu
Subject: Simulator on master is not building

I believe for every check-in we decided to run sanity tests on simulator 
atleast, currently build for simulator is failing. 

 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) 
on project cloud-plugin-hypervisor-simulator: Compilation failure: Compilation 
failure:
[ERROR] 
/home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/resource/AgentRoutingResource.java:[230,8]
 error: 'try' without 'catch', 'finally' or resource declarations [ERROR] 
/home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/resource/AgentRoutingResource.java:[251,8]
 error: 'try' without 'catch', 'finally' or resource declarations


Thanks!
Santhosh

RE: Simulator on master is not building

[Anthony Xu]

I see, thanks for explanation.

Anthony

-Original Message-
From: Koushik Das 
Sent: Wednesday, July 30, 2014 10:02 PM
To: Anthony Xu; dev@cloudstack.apache.org
Subject: RE: Simulator on master is not building

There is a separate simulator DB where all these VOs are used. These are only 
used in the 'Simulator' resource layer and are not part of core CS logic. Also 
I have written a sample test for new vmsync 
(test/integration/smoke/test_vm_sync.py). Please check it out and let me know 
if there are any issues.

-Koushik

-Original Message-----
From: Anthony Xu 
Sent: Wednesday, 30 July 2014 11:37 PM
To: Koushik Das; dev@cloudstack.apache.org
Subject: RE: Simulator on master is not building

Hi Koushik,

fixed the build for simulator.

I just found out Simulator use its own VOes for some VOes, it may not be easy 
for developer to add feature for simulator if the feature needs to change VO, 
for example, the new VMsync logic, I don't think simulator test the new VMsync 
logic. 

If we consider Simulator as a hypervisor, ideally it should use the same VOes 
as other hypersivors. Can you help us understand what's the reason behind this?

Thanks
Anthony







./plugins/hypervisors/simulator/src/com/cloud/simulator/MockVMVO.java
./plugins/hypervisors/simulator/src/com/cloud/simulator/MockSecStorageVO.java
./plugins/hypervisors/simulator/src/com/cloud/simulator/MockVolumeVO.java
./plugins/hypervisors/simulator/src/com/cloud/simulator/MockStoragePoolVO.java
./plugins/hypervisors/simulator/src/com/cloud/simulator/MockHostVO.java
./plugins/hypervisors/simulator/src/com/cloud/simulator/MockConfigurationVO.java
./plugins/hypervisors/simulator/src/com/cloud/simulator/MockSecurityRulesVO.java





-Original Message-----
From: Anthony Xu 
Sent: Wednesday, July 30, 2014 10:28 AM
To: Koushik Das; dev@cloudstack.apache.org
Subject: RE: Simulator on master is not building

We used -Dsimulator to include simulator, it is very easy for developers to 
forget it.  Simulator should be built by default , we may use -Dnosimulator to 
exclude simulator.


Anthony

-Original Message-
From: Koushik Das 
Sent: Wednesday, July 30, 2014 3:03 AM
To: dev@cloudstack.apache.org
Cc: Anthony Xu
Subject: RE: Simulator on master is not building

The simulator code should be kept up to date with any changes done in the core 
product. If there are any interface changes, necessary changes should be made 
in simulator plugin as well along with other hypervisor plugins. To build 
simulator code use refer to [1].

-Koushik

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

-Original Message-
From: Santhosh Edukulla [mailto:santhosh.eduku...@citrix.com] 
Sent: Wednesday, 30 July 2014 3:27 PM
To: dev@cloudstack.apache.org
Cc: Anthony Xu
Subject: Simulator on master is not building

I believe for every check-in we decided to run sanity tests on simulator 
atleast, currently build for simulator is failing. 

 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) 
on project cloud-plugin-hypervisor-simulator: Compilation failure: Compilation 
failure:
[ERROR] 
/home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/resource/AgentRoutingResource.java:[230,8]
 error: 'try' without 'catch', 'finally' or resource declarations [ERROR] 
/home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/resource/AgentRoutingResource.java:[251,8]
 error: 'try' without 'catch', 'finally' or resource declarations


Thanks!
Santhosh

Re: Review Request 24598: Copy Snapshot command too heavy on XenServer Dom0 resources when using dd top copy incremental snapshots

[anthony xu]

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

Ship it!


This srcipt is not used for XS 6.2 + SP1 + FOX and above, vdi.copy is used 
instead. it is good to have this fix though.

- anthony xu


On Aug. 12, 2014, 11:21 a.m., Joris van Lieshout wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/24598/
> ---
> 
> (Updated Aug. 12, 2014, 11:21 a.m.)
> 
> 
> Review request for cloudstack, Alex Huang, anthony xu, daan Hoogland, edison 
> su, Kishan Kavala, Min Chen, Sanjay Tripathi, and Hugo Trippaers.
> 
> 
> Bugs: CLOUDSTACK-7319
> https://issues.apache.org/jira/browse/CLOUDSTACK-7319
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> We noticed that the dd process was way to agressive on Dom0 causing all kinds 
> of problems on a xenserver with medium workloads. 
> ACS uses the dd command to copy incremental snapshots to secondary storage. 
> This process is to heavy on Dom0 resources and even impacts DomU performance, 
> and can even lead to domain freezes (including Dom0) of more then a minute. 
> We've found that this is because the Dom0 kernel caches the read and write 
> operations of dd.
> Some of the issues we have seen as a consequence of this are:
> - DomU performance/freezes
> - OVS freeze and not forwarding any traffic
> - Including LACPDUs resulting in the bond going down
> - keepalived heartbeat packets between RRVMs not being send/received 
> resulting in flapping RRVM master state
> - Braking snapshot copy processes
> - the xenserver heartbeat script reaching it's timeout and fencing the server
> - poolmaster connection loss
> - ACS marking the host as down and fencing the instances even though they are 
> still running on the origional host resulting in the same instance running on 
> to hosts in one cluster
> - vhd corruption are a result of some of the issues mentioned above
> We've developed a patch on the xenserver scripts 
> /etc/xapi.d/plugins/vmopsSnapshot that added the direct flag of both input 
> and output files (iflag=direct oflag=direct).
> Our test have shown that Dom0 load during snapshot copy is way lower.
> 
> We believe Hot-fix 4 for XS62 sp1 contains a similar fix but for the sparse 
> dd process used for the first copy of a chain.
> 
> http://support.citrix.com/article/CTX140417
> 
> == begin quote ==
> Copying a virtual disk between SRs uses the unbuffered I/O to avoid polluting 
> the pagecache in the Control Domain (dom0). This reduces the dom0 vCPU 
> overhead and allows the pagecache to work more effectively for other 
> operations.
> == end quote ==
> 
> 
> Diffs
> -
> 
>   scripts/vm/hypervisor/xenserver/vmopsSnapshot 5fd69a6 
> 
> Diff: https://reviews.apache.org/r/24598/diff/
> 
> 
> Testing
> ---
> 
> We are running this fix in our beta and prod environment (both using ACS 
> 4.3.0) with great success.
> 
> 
> Thanks,
> 
> Joris van Lieshout
> 
>

Re: Review Request 24648: CLOUDSTACK-7310 - don't try and shink a disk in the volume resize test

[anthony xu]

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

Ship it!


Ship It!

- anthony xu


On Aug. 13, 2014, 2:22 p.m., John Dilley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/24648/
> ---
> 
> (Updated Aug. 13, 2014, 2:22 p.m.)
> 
> 
> Review request for cloudstack and Santhosh Edukulla.
> 
> 
> Bugs: CLOUDSTACK-7310
> https://issues.apache.org/jira/browse/CLOUDSTACK-7310
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Neither XenServer or KVM support shinking a disk. Given that we skip running 
> this on VMWare and Hyper-V, this means this part of the test will never pass. 
> I have therefore removed it.
> 
> 
> Diffs
> -
> 
>   test/integration/smoke/test_volumes.py e2e0d76 
> 
> Diff: https://reviews.apache.org/r/24648/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> John Dilley
> 
>

Re: Review Request 26482: CLOUDSTACK-7688: Do not allow various operations which breaks VM Snapshots

[anthony xu]

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


Can you explain why you remove the code?
 // remove diskAndMemory VM snapshots

- anthony xu


On Oct. 9, 2014, 9:09 a.m., Anshul Gangwar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/26482/
> ---
> 
> (Updated Oct. 9, 2014, 9:09 a.m.)
> 
> 
> Review request for cloudstack, anthony xu and Devdeep Singh.
> 
> 
> Bugs: CLOUDSTACK-7688
> https://issues.apache.org/jira/browse/CLOUDSTACK-7688
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> VM snapshots stops working when following operations are performed on VM with 
> VM snapshots
> 
> 1. Volumes of VM are migrated to other storage
> 2. Add and remove NIC to/from VM
> 3. Attach and Detach volume to VM
> 4. Scale up/down of VM(change service offering)
> 5. Volume snapshot which is not major use case in this scenario
> 6. Resize volume
> 7. Live migration of VM which involves storage migration
> 8. Do not allow VM snapshot in case VM snapshot already exists
> 
> This patche adds the above restrictions
> 
> 
> Diffs
> -
> 
>   server/src/com/cloud/storage/VolumeApiServiceImpl.java e089b77 
>   server/src/com/cloud/vm/UserVmManagerImpl.java 2636096 
>   server/src/com/cloud/vm/snapshot/VMSnapshotManagerImpl.java f85f6c8 
> 
> Diff: https://reviews.apache.org/r/26482/diff/
> 
> 
> Testing
> ---
> 
> verified that all the above operations are not allowed
> 
> 
> Thanks,
> 
> Anshul Gangwar
> 
>

Re: Review Request 26482: CLOUDSTACK-7688: Do not allow various operations which breaks VM Snapshots

[anthony xu]

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

Ship it!


Ship It!

- anthony xu


On Oct. 9, 2014, 9:09 a.m., Anshul Gangwar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/26482/
> ---
> 
> (Updated Oct. 9, 2014, 9:09 a.m.)
> 
> 
> Review request for cloudstack, anthony xu and Devdeep Singh.
> 
> 
> Bugs: CLOUDSTACK-7688
> https://issues.apache.org/jira/browse/CLOUDSTACK-7688
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> VM snapshots stops working when following operations are performed on VM with 
> VM snapshots
> 
> 1. Volumes of VM are migrated to other storage
> 2. Add and remove NIC to/from VM
> 3. Attach and Detach volume to VM
> 4. Scale up/down of VM(change service offering)
> 5. Volume snapshot which is not major use case in this scenario
> 6. Resize volume
> 7. Live migration of VM which involves storage migration
> 8. Do not allow VM snapshot in case VM snapshot already exists
> 
> This patche adds the above restrictions
> 
> 
> Diffs
> -
> 
>   server/src/com/cloud/storage/VolumeApiServiceImpl.java e089b77 
>   server/src/com/cloud/vm/UserVmManagerImpl.java 2636096 
>   server/src/com/cloud/vm/snapshot/VMSnapshotManagerImpl.java f85f6c8 
> 
> Diff: https://reviews.apache.org/r/26482/diff/
> 
> 
> Testing
> ---
> 
> verified that all the above operations are not allowed
> 
> 
> Thanks,
> 
> Anshul Gangwar
> 
>

Re: Review Request 26866: VM Snapshot - Support only for vm revert cases that will not result in VM state change

[anthony xu]

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

Ship it!


Ship It!

- anthony xu


On Oct. 17, 2014, 7:46 a.m., Anshul Gangwar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/26866/
> ---
> 
> (Updated Oct. 17, 2014, 7:46 a.m.)
> 
> 
> Review request for cloudstack, anthony xu and Devdeep Singh.
> 
> 
> Bugs: CLOUDSTACK-7747
> https://issues.apache.org/jira/browse/CLOUDSTACK-7747
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Currently we extend support for all the possible combinations .In cases were 
> the Vm start changes from “Stopped” to “Running”, CS does not account for 
> this VM’s capacity and VM start does not use our allocators.
> 
> Following will be the only configuration we would have to support:
> 
> 1.Revert a "Running" VM to a "Disk and Memory" Snapshot ( with and without 
> "quiesce" option).
> 2.Revert a "Stopped" VM to a "Disk " Snapshot ( with and without "quiesce" 
> option).
> 
> 
> Diffs
> -
> 
>   server/src/com/cloud/vm/snapshot/VMSnapshotManagerImpl.java f85f6c8 
> 
> Diff: https://reviews.apache.org/r/26866/diff/
> 
> 
> Testing
> ---
> 
> tested that VM snapshot revert not allowed for running VM to disk type VM 
> snapshot and stopped VM to disk and memory type snapshot.
> 
> 
> Thanks,
> 
> Anshul Gangwar
> 
>

Re: Review Request 27000: CLOUDSTACK-7762 -[Automation] - Fix test failure for test_02_revert_vm_snapshots in smoke/test_vm_snapshots.py

[anthony xu]

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

Ship it!


Ship It!

- anthony xu


On Oct. 21, 2014, 10:34 p.m., sangeetha hariharan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27000/
> ---
> 
> (Updated Oct. 21, 2014, 10:34 p.m.)
> 
> 
> Review request for cloudstack, anthony xu and Chandan Purushothama.
> 
> 
> Bugs: CLOUDSTACK-7762
> https://issues.apache.org/jira/browse/CLOUDSTACK-7762
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> test_02_revert_vm_snapshots in smoke/test_vm_snapshots.py fails in BVT runs 
> with the following exception:
> 
> 2014-10-20 16:41:00,497 INFO [o.a.c.f.j.i.AsyncJobMonitor] 
> (API-Job-Executor-120:ctx-83b738d9 job-459) Add job-459 into job monitoring
> 2014-10-20 16:41:00,497 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
> (API-Job-Executor-120:ctx-83b738d9 job-459) Executing AsyncJobVO {id:459, 
> userId: 2, accountId: 2, instanceType: None, instanceId: null, cmd: 
> org.apache.cloudstack.api.command.admin.vmsnapshot.RevertToVMSnapshotCmdByAdmin,
>  cmdInfo: {"response":"json","ctxDetails":"
> {\"com.cloud.vm.snapshot.VMSnapshot\":\"12280973-a1e4-43e3-80b3-3afacd607909\"}
> 
> ","cmdEventType":"VMSNAPSHOT.REVERTTO","ctxUserId":"2","httpmethod":"GET","vmsnapshotid":"12280973-a1e4-43e3-80b3-3afacd607909","ctxAccountId":"2","ctxStartEventId":"1406","apiKey":"aJwkScf5ziRwz8gKQ9HB0Ce6hSsTJTUtmUDUQ_U2teV3vVmuLQRLad8xqAgr7CrFOEQbywdVpKSt2yC_ORXLYg","signature":"cYBxgg8eBfktovmCaHYox2xoTE8\u003d"},
>  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
> null, initMsid: 11489258594360, completeMsid: null, lastUpdated: null, 
> lastPolled: null, created: null}
> 2014-10-20 16:41:00,529 ERROR [c.c.a.ApiAsyncJobDispatcher] 
> (API-Job-Executor-120:ctx-83b738d9 job-459) Unexpected exception while 
> executing 
> org.apache.cloudstack.api.command.admin.vmsnapshot.RevertToVMSnapshotCmdByAdmin
> com.cloud.exception.InvalidParameterValueException: VM Snapshot revert not 
> allowed. This will result in VM state change. You can revert running VM to 
> disk and memory type snapshot and stopped VM to disk type snapshot
> at 
> com.cloud.vm.snapshot.VMSnapshotManagerImpl.revertToSnapshot(VMSnapshotManagerImpl.java:581)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> 
> Root Cause :
> reverting Snapshots is allowed only when there is no vm state change 
> associated with it.
> Following are the 2 scenarios allowed: 
> 1.Revert a "Running" VM to a "Disk and Memory" Snapshot ( with and without 
> "quiesce" option).
> 2.Revert a "Stopped" VM to a "Disk " Snapshot ( with and without "quiesce" 
> option).
> 
> In this test case , we are testing reverting to a Disk " Snapshot. Introduced 
> a Vm stop before performing the revert operation.
> 
> 
> Diffs
> -
> 
>   test/integration/smoke/test_vm_snapshots.py 131da99 
> 
> Diff: https://reviews.apache.org/r/27000/diff/
> 
> 
> Testing
> ---
> 
> Tested with advanced zone set up with Xenserver hosts:
> 
> Test to create VM snapshots ... === TestName: test_01_create_vm_snapshots | 
> Status : SUCCESS ===
> ok
> Test to revert VM snapshots ... === TestName: test_02_revert_vm_snapshots | 
> Status : SUCCESS ===
> ok
> Test to delete vm snapshots ... === TestName: test_03_delete_vm_snapshots | 
> Status : SUCCESS ===
> ok
> 
> --
> Ran 3 tests in 795.005s
> 
> OK
> 
> 
> Thanks,
> 
> sangeetha hariharan
> 
>

RE: Blocker bug: can't create the volumes on Xen 6.2.0 on the latest 4.3

[Anthony Xu]

Always put vhd-util in your cloudstack source tree, 
scripts/vm/hypervisor/xenserver/


Anthony

-Original Message-
From: Alena Prokharchyk 
Sent: Monday, December 09, 2013 4:49 PM
To: dev@cloudstack.apache.org; Anthony Xu
Subject: Re: Blocker bug: can't create the volumes on Xen 6.2.0 on the latest 
4.3

That helped, thank you Min.

It would be nice to get a notification email next time from the person making 
this kind of changes to save everybody else's time on debugging.

-Alena.



On 12/9/13, 4:02 PM, "Min Chen"  wrote:

>Is this happening in your ssvm startup? If so, go to your xen host, 
>/opt/cloud/bin folder, check if you have vhd-util there. Not sure why, 
>it seems that we have changed the directory from previous 
>/opt/xensources to /opt/cloud. I ran into a similar problem in starting up 
>ssvm.
>
>Thanks
>-min
>
>On 12/9/13 3:58 PM, "Alena Prokharchyk" 
>wrote:
>
>>There is some regression bug on the latest 4.3  volumes creation 
>>fails on xen 6.2.0. Steps made:
>>
>>1) Deployed CS code and redeployed the DB
>>2) Added xen host to the CS
>>3) VDI creation fails with generic error message
>>
>>
>>2013-12-09 15:56:44,629 WARN  [c.c.h.x.r.XenServerStorageProcessor]
>>(DirectAgent-2:ctx-2d667640) can not create vdi in sr
>>734481f8-fee3-59d9-20e8-dbe3b8124a78
>>2013-12-09 15:56:44,629 WARN  [c.c.h.x.r.XenServerStorageProcessor]
>>(DirectAgent-2:ctx-2d667640) Catch Exception 
>>com.cloud.utils.exception.CloudRuntimeException for template +  due to
>>com.cloud.utils.exception.CloudRuntimeException: can not create vdi in 
>>sr
>>734481f8-fee3-59d9-20e8-dbe3b8124a78
>>com.cloud.utils.exception.CloudRuntimeException: can not create vdi in 
>>sr
>>734481f8-fee3-59d9-20e8-dbe3b8124a78
>>
>>Anthony, I wonder if it can be related to your latest changes. Can you 
>>please take a look as its a blocker.
>>
>>-Alena.
>

RE: Blocker bug: can't create the volumes on Xen 6.2.0 on the latest 4.3

[Anthony Xu]

This patch is on both master and 4.3,
Maybe the scripts in the old location were copied before,


Anthony

-Original Message-
From: Koushik Das [mailto:koushik@citrix.com] 
Sent: Monday, December 09, 2013 9:37 PM
To: 
Cc: Alena Prokharchyk
Subject: Re: Blocker bug: can't create the volumes on Xen 6.2.0 on the latest 
4.3

I see that for XS the location of script files in the host has changed from 
/opt/xensource/bin to /opt/cloud/bin. On latest master branch I see that the 
scripts are still getting placed in the old location while adding a host. Is 
there any commit missed out on master?

-Koushik

On 10-Dec-2013, at 8:06 AM, Anthony Xu  wrote:

> Always put vhd-util in your cloudstack source tree, 
> scripts/vm/hypervisor/xenserver/
> 
> 
> Anthony
> 
> -Original Message-
> From: Alena Prokharchyk
> Sent: Monday, December 09, 2013 4:49 PM
> To: dev@cloudstack.apache.org; Anthony Xu
> Subject: Re: Blocker bug: can't create the volumes on Xen 6.2.0 on the 
> latest 4.3
> 
> That helped, thank you Min.
> 
> It would be nice to get a notification email next time from the person making 
> this kind of changes to save everybody else's time on debugging.
> 
> -Alena.
> 
> 
> 
> On 12/9/13, 4:02 PM, "Min Chen"  wrote:
> 
>> Is this happening in your ssvm startup? If so, go to your xen host, 
>> /opt/cloud/bin folder, check if you have vhd-util there. Not sure 
>> why, it seems that we have changed the directory from previous 
>> /opt/xensources to /opt/cloud. I ran into a similar problem in starting up 
>> ssvm.
>> 
>> Thanks
>> -min
>> 
>> On 12/9/13 3:58 PM, "Alena Prokharchyk" 
>> 
>> wrote:
>> 
>>> There is some regression bug on the latest 4.3  volumes creation 
>>> fails on xen 6.2.0. Steps made:
>>> 
>>> 1) Deployed CS code and redeployed the DB
>>> 2) Added xen host to the CS
>>> 3) VDI creation fails with generic error message
>>> 
>>> 
>>> 2013-12-09 15:56:44,629 WARN  [c.c.h.x.r.XenServerStorageProcessor]
>>> (DirectAgent-2:ctx-2d667640) can not create vdi in sr
>>> 734481f8-fee3-59d9-20e8-dbe3b8124a78
>>> 2013-12-09 15:56:44,629 WARN  [c.c.h.x.r.XenServerStorageProcessor]
>>> (DirectAgent-2:ctx-2d667640) Catch Exception 
>>> com.cloud.utils.exception.CloudRuntimeException for template +  due 
>>> to
>>> com.cloud.utils.exception.CloudRuntimeException: can not create vdi 
>>> in sr
>>> 734481f8-fee3-59d9-20e8-dbe3b8124a78
>>> com.cloud.utils.exception.CloudRuntimeException: can not create vdi 
>>> in sr
>>> 734481f8-fee3-59d9-20e8-dbe3b8124a78
>>> 
>>> Anthony, I wonder if it can be related to your latest changes. Can 
>>> you please take a look as its a blocker.
>>> 
>>> -Alena.
>> 
> 

RE: Blocker bug: can't create the volumes on Xen 6.2.0 on the latest 4.3

[Anthony Xu]

Correct,

Anthony

-Original Message-
From: Alena Prokharchyk 
Sent: Tuesday, December 10, 2013 4:39 PM
To: Anthony Xu; dev@cloudstack.apache.org
Subject: Re: Blocker bug: can't create the volumes on Xen 6.2.0 on the latest 
4.3

Anthony, just wanted to confirm - this file should never get submitted to the 
remote asf repo, right? In this case I will add it to the .gitignore as well.

-Alena.

On 12/9/13, 6:36 PM, "Anthony Xu"  wrote:

>Always put vhd-util in your cloudstack source tree, 
>scripts/vm/hypervisor/xenserver/
>
>
>Anthony
>
>-Original Message-
>From: Alena Prokharchyk
>Sent: Monday, December 09, 2013 4:49 PM
>To: dev@cloudstack.apache.org; Anthony Xu
>Subject: Re: Blocker bug: can't create the volumes on Xen 6.2.0 on the 
>latest 4.3
>
>That helped, thank you Min.
>
>It would be nice to get a notification email next time from the person 
>making this kind of changes to save everybody else's time on debugging.
>
>-Alena.
>
>
>
>On 12/9/13, 4:02 PM, "Min Chen"  wrote:
>
>>Is this happening in your ssvm startup? If so, go to your xen host, 
>>/opt/cloud/bin folder, check if you have vhd-util there. Not sure why, 
>>it seems that we have changed the directory from previous 
>>/opt/xensources to /opt/cloud. I ran into a similar problem in 
>>starting up ssvm.
>>
>>Thanks
>>-min
>>
>>On 12/9/13 3:58 PM, "Alena Prokharchyk" 
>>wrote:
>>
>>>There is some regression bug on the latest 4.3  volumes creation 
>>>fails on xen 6.2.0. Steps made:
>>>
>>>1) Deployed CS code and redeployed the DB
>>>2) Added xen host to the CS
>>>3) VDI creation fails with generic error message
>>>
>>>
>>>2013-12-09 15:56:44,629 WARN  [c.c.h.x.r.XenServerStorageProcessor]
>>>(DirectAgent-2:ctx-2d667640) can not create vdi in sr
>>>734481f8-fee3-59d9-20e8-dbe3b8124a78
>>>2013-12-09 15:56:44,629 WARN  [c.c.h.x.r.XenServerStorageProcessor]
>>>(DirectAgent-2:ctx-2d667640) Catch Exception 
>>>com.cloud.utils.exception.CloudRuntimeException for template +  due 
>>>to
>>>com.cloud.utils.exception.CloudRuntimeException: can not create vdi 
>>>in sr
>>>734481f8-fee3-59d9-20e8-dbe3b8124a78
>>>com.cloud.utils.exception.CloudRuntimeException: can not create vdi 
>>>in sr
>>>734481f8-fee3-59d9-20e8-dbe3b8124a78
>>>
>>>Anthony, I wonder if it can be related to your latest changes. Can 
>>>you please take a look as its a blocker.
>>>
>>>-Alena.
>>
>

RE: [VOTE] 2rd round of voting for ASF 4.2.1 third RC

[Anthony Xu]

My best guess is you don't have vhd-util in your management server.

Check if vhd-util exists in /opt/cloud/bin in your XS host, if not,  you need 
to do following,
1. make sure vhd-util is downloaded in your management server
2. clear XS host tag, execute following command in each XS
  Xe host-param-clear host-uuid= param-name=tags
3. restart management server



Anthony

-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] 
Sent: Tuesday, December 10, 2013 2:09 PM
To: dev
Subject: Re: [VOTE] 2rd round of voting for ASF 4.2.1 third RC

I am going to tentatively -1 this one. There has changed something since last 
rc that makes this one not start a ssvm in my sanity check env after creating a 
zone. I have not pinned down the culprit commit yet so I will keep looking till 
I can be sure as to what is wrong. I have been going back and forth between the 
two versions and commits in the middle and the problem is reproducible it seems.

The new rc throws an insufficient capacity exception and then null pointers as 
it tries to start the console proxy. In the same env with the same config and 
zone spec, the old rc works.

will let you know as I find out more,
Daan

On Tue, Dec 10, 2013 at 2:21 PM, Abhinandan Prateek 
 wrote:
> The vote is open till 13 Dec 2013.
>
> On 10/12/13 6:28 pm, "Abhinandan Prateek" 
> 
> wrote:
>
>>Hi,
>>
>>   This release candidate addresses the following additional issues 
>>reported by community:
>>
>>1. CLOUDSTACK-5145 : ListNetworkACL API should list ACLs owned by the 
>>user only 2. CLOUDSTACK-5214 : 4.2.1 upgrade is broken 3. The CHANGES 
>>file has been fixed to mark some important fixes as such, instead of 
>>new features which they are not.
>>
>>The details of this RC are as:
>>
>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=
>>refs
>>/
>>heads/4.2
>>commit: 43350d64ce66e366f08a9fa13ad09bca462b66da
>>
>>List of changes are available in Release Notes, a summary can be 
>>accessed in CHANGES file:
>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;
>>f=CH
>>A
>>NGES;hb=4.2
>>
>>Source release revision 3865 (checksums and signatures are available 
>>at the same location):
>>https://dist.apache.org/repos/dist/dev/cloudstack/4.2.1/
>>  **note that for release notes separate email will go out subsequently.
>>
>>PGP release keys (signed using RSA Key ID = 42443AA1):
>>https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>
>>Vote will be open for 72 hours (until 12/05 End of day PST).
>>
>>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: Build failed in Jenkins: cloudstack-rat-master #3611

[Anthony Xu]

Added license header,

Anthony

-Original Message-
From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com] 
Sent: Friday, December 13, 2013 4:54 AM
To: dev@cloudstack.apache.org; Anthony Xu
Subject: RE: Build failed in Jenkins: cloudstack-rat-master #3611

Anthony,

It seems you committed scripts/vm/hypervisor/xenserver/cloudlog without a 
license header. Can you add it or is there some reason it cannot work with one? 
I can't tell from the file what format it should have for comments.

Regards,
Daan Hoogland

-Original Message-
From: Apache Jenkins Server [mailto:jenk...@builds.apache.org] 
Sent: Friday, December 13, 2013 1:18 PM
To: cloudstack-comm...@incubator.apache.org; Daan Hoogland; devd...@gmail.com; 
jessicaw...@apache.org; ng.t...@gmail.com; anthony...@citrix.com; 
alena.prokharc...@citrix.com; w...@widodh.nl; alex.hu...@citrix.com; 
w.z...@leaseweb.com; likitha.she...@citrix.com; kis...@cloud.com; 
gir...@clogeny.com; nitin.me...@citrix.com; muralimmre...@gmail.com; 
kous...@apache.org; sheng.y...@citrix.com; kelv...@gmail.com; 
aprat...@apache.org; gshilam...@ddn.com; pra...@cloud.com; jaya...@apache.org; 
tall...@apache.org; min.c...@citrix.com; brian.fede...@citrix.com
Subject: Build failed in Jenkins: cloudstack-rat-master #3611

See <https://builds.apache.org/job/cloudstack-rat-master/3611/changes>

Changes:

[devdeep] CLOUDSTACK-5489: Cloud user doesn't have permissions to copy 
systemvm.iso to secondary.

[kishan] CLOUDSTACK-5435 enabled encryption for ldap params

[kishan] CLOUDSTACK-5483 : Failed to start management server when db

--
Started by an SCM change
Building remotely on ubuntu3 in workspace 
<https://builds.apache.org/job/cloudstack-rat-master/ws/>
Fetching changes from the remote Git repository Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
Checking out Revision b54ac9a6350687bfb511a3cb1002212ad2a94501 (origin/master) 
[cloudstack-rat-master] $ /bin/bash -xe /tmp/hudson6210192666317674027.sh
+ /home/jenkins/tools/maven/latest2/bin/mvn 
+ --projects=org.apache.cloudstack:cloudstack 
+ org.apache.rat:apache-rat-plugin:0.10:check
[INFO] Scanning for projects...
[INFO] 
[INFO] Building Apache CloudStack
[INFO]task-segment: [org.apache.rat:apache-rat-plugin:0.10:check]
[INFO] 
[INFO] [apache-rat:check {execution: default-cli}] [INFO] 51 implicit excludes 
(use -debug for more details).
[INFO] Exclude: CHANGES
[INFO] Exclude: INSTALL.md
[INFO] Exclude: .idea/
[INFO] Exclude: **/*.log
[INFO] Exclude: **/*.patch
[INFO] Exclude: **/.classpath
[INFO] Exclude: **/.project
[INFO] Exclude: **/.idea/**
[INFO] Exclude: **/*.iml
[INFO] Exclude: **/.settings/**
[INFO] Exclude: .metadata/**
[INFO] Exclude: .git/**
[INFO] Exclude: .gitignore
[INFO] Exclude: **/*.crt
[INFO] Exclude: **/*.csr
[INFO] Exclude: **/*.key
[INFO] Exclude: **/authorized_keys
[INFO] Exclude: **/*.war
[INFO] Exclude: **/*.mar
[INFO] Exclude: **/*.jar
[INFO] Exclude: **/*.iso
[INFO] Exclude: **/*.tgz
[INFO] Exclude: **/*.zip
[INFO] Exclude: **/target/**
[INFO] Exclude: **/.vagrant
[INFO] Exclude: awsapi/overlays/**
[INFO] Exclude: build/build.number
[INFO] Exclude: services/console-proxy/server/js/jquery.js
[INFO] Exclude: debian/compat
[INFO] Exclude: debian/control
[INFO] Exclude: debian/dirs
[INFO] Exclude: debian/rules
[INFO] Exclude: deps/XenServerJava/src/com/xensource/xenapi/*.java
[INFO] Exclude: deps/XenServerJava/BSD
[INFO] Exclude: deps/XenServerJava/Makefile [INFO] Exclude: 
dist/console-proxy/js/jquery.js [INFO] Exclude: 
plugins/hypervisors/hyperv/DotNet/ServerResource/ServerResource.sln
[INFO] Exclude: plugins/hypervisors/hyperv/DotNet/ServerResource/packages/**
[INFO] Exclude: plugins/hypervisors/hyperv/DotNet/ServerResource/.nuget/**
[INFO] Exclude: plugins/hypervisors/hyperv/DotNet/ServerResource/**/obj/**
[INFO] Exclude: plugins/hypervisors/hyperv/DotNet/ServerResource/**/bin/**
[INFO] Exclude: 
plugins/hypervisors/hyperv/DotNet/ServerResource/**/packages.config
[INFO] Exclude: plugins/hypervisors/hyperv/DotNet/ServerResource/**/App.config
[INFO] Exclude: plugins/hypervisors/hyperv/DotNet/ServerResource/**/*.csproj
[INFO] Exclude: plugins/hypervisors/hyperv/conf/agent.properties
[INFO] Exclude: scripts/vm/systemvm/id_rsa.cloud [INFO] Exclude: 
services/console-proxy/server/conf/agent.properties
[INFO] Exclude: services/console-proxy/server/conf/environment.properties
[INFO] Exclude: services/secondary-storage/conf/agent.properties
[INFO] Exclude: services/secondary-storage/conf/environment.properties
[INFO] Exclude: 
tools/devcloud/basebuild/puppet-devcloudinitial/files/network.conf
[INFO] Exclude: tools/appliance/definitions/devcloud/*
[INFO] Exclude: tools/appliance/definitions/systemvmtemplate/*
[INFO] Exclude: tools/appliance/definiti