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

[Paul Angus]

If I manually fix the white spaces I can get past MySQL HA Strategy, but then I 
hit:

[INFO] 
[INFO] Building Apache CloudStack Client UI 4.3.0
[INFO] 
Downloading: 
http://repo.maven.apache.org/maven2/org/apache/cloudstack/cloud-plugin-database-mysqlha/4.3.0/cloud-plugin-database-mysqlha-4.3.0.pom
[WARNING] The POM for 
org.apache.cloudstack:cloud-plugin-database-mysqlha:jar:4.3.0 is missing, no 
dependency information available
Downloading: 
http://repo.maven.apache.org/maven2/org/apache/cloudstack/cloud-plugin-database-mysqlha/4.3.0/cloud-plugin-database-mysqlha-4.3.0.jar
[ERROR] Failed to execute goal on project cloud-client-ui: Could not resolve 
dependencies for project org.apache.cloudstack:cloud-client-ui:war:4.3.0: Could 
not find artifact org.apache.cloudstack:cloud-plugin-database-mysqlha:jar:4.3.0 
in central (http://repo.maven.apache.org/maven2) -> [Help 1]

MySQL HA Strategy seems to need a bit of work.


Regards,

Paul Angus
Cloud Architect
S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus
paul.an...@shapeblue.com

-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
Sent: 11 March 2014 19:31
To: dev@cloudstack.apache.org
Cc: Hugo Trippaers; Hugo Trippaers (htrippa...@schubergphilis.com); Paul Angus
Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)



> -Original Message-
> From: Paul Angus [mailto:paul.an...@shapeblue.com]
> Sent: Tuesday, March 11, 2014 10:35 AM
> To: dev@cloudstack.apache.org
> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>
> Trying to build 4.3,  the process bombs out for me at MySQL HA Strategy.
> And strangely it seems to be trying to build MySQL from Master (4.4.0-
> SNAPSHOT)?
[Animesh] Ok this came in from Hugo's commit that I cherry-picked
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=472a387d2d828e21aff93a750ed3e178837a1879

from file plugins/database/mysql-ha/pom.xml This is a  version issue which can 
be fixed but should not affect functioning. Lets hear from Hugo on this.


The other errors are formatting issues caught by checkstyle plugin that can be 
ignored. The Jenkins build is successful.

>
> Ideas anyone?
>
>
> [INFO] Apache CloudStack Plugin - MySQL HA Strategy .. FAILURE
> [1.110s] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-
> plugin:2.11:check (cloudstack-checkstyle) on project
> cloud-plugin-database-
> mysqlha: Failed during checkstyle execution: There are 6 checkstyle
> errors. -> [Help 1]
>
> [INFO]
> --
> -- [INFO] Building Apache CloudStack Plugin - MySQL HA Strategy 4.4.0-
> SNAPSHOT [INFO]
> --
> --
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
> cloud-plugin- database-mysqlha --- [INFO] Deleting
> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
> 4.3.0/plugins/database/mysql-ha/target (includes = [**/*], excludes =
> []) [INFO] Deleting
> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
> 4.3.0/plugins/database/mysql-ha (includes = [target, dist], excludes =
> []) [INFO] [INFO] --- maven-checkstyle-plugin:2.11:check
> (cloudstack-checkstyle) @ cloud-plugin-database-mysqlha --- [INFO] Starting 
> audit...
> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
> 4.3.0/plugins/database/mysql-
> ha/src/com/cloud/utils/db/StaticStrategy.java:54: Line has trailing spaces.
> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
> 4.3.0/plugins/database/mysql-
> ha/src/com/cloud/utils/db/StaticStrategy.java:58: Line has trailing spaces.
> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
> 4.3.0/plugins/database/mysql-
> ha/src/com/cloud/utils/db/StaticStrategy.java:60: Line has trailing spaces.
> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
> 4.3.0/plugins/database/mysql-
> ha/src/com/cloud/utils/db/StaticStrategy.java:110: Line has trailing spaces.
> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
> 4.3.0/plugins/database/mysql-
> ha/src/com/cloud/utils/db/StaticStrategy.java:120: Line has trailing spaces.
> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
> 4.3.0/plugins/database/mysql-
> ha/src/com/cloud/utils/db/StaticStrategy.java:127: Line has trailing spaces.
> Audit done.
>
> Regards,
>
> Paul Angus
> Cloud Architect
> S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus
> paul.an...@shapeblue.com
>
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: 11 March 2014 03:00
> To: dev@cloudstack.apache.org
> Subject: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>
>
>
> Hi All,
>
>
>
> I've created a 4.3.0 release, with the following artifacts up for a
>
> vote:
>
>
>
>
>
> Git Branch and 

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

[Hugo Trippaers]

Hey Paul,

Just to be clear, this problem only occurs during the noredist build right?

Mysql HA is one of the noredist features, so it should not be present in the 
regular build.

I’m checking the poms now to see if everything is configured correctly.

Cheers,

Hugo

On 12 mrt. 2014, at 08:14, Paul Angus  wrote:

> If I manually fix the white spaces I can get past MySQL HA Strategy, but then 
> I hit:
> 
> [INFO] 
> 
> [INFO] Building Apache CloudStack Client UI 4.3.0
> [INFO] 
> 
> Downloading: 
> http://repo.maven.apache.org/maven2/org/apache/cloudstack/cloud-plugin-database-mysqlha/4.3.0/cloud-plugin-database-mysqlha-4.3.0.pom
> [WARNING] The POM for 
> org.apache.cloudstack:cloud-plugin-database-mysqlha:jar:4.3.0 is missing, no 
> dependency information available
> Downloading: 
> http://repo.maven.apache.org/maven2/org/apache/cloudstack/cloud-plugin-database-mysqlha/4.3.0/cloud-plugin-database-mysqlha-4.3.0.jar
> [ERROR] Failed to execute goal on project cloud-client-ui: Could not resolve 
> dependencies for project org.apache.cloudstack:cloud-client-ui:war:4.3.0: 
> Could not find artifact 
> org.apache.cloudstack:cloud-plugin-database-mysqlha:jar:4.3.0 in central 
> (http://repo.maven.apache.org/maven2) -> [Help 1]
> 
> MySQL HA Strategy seems to need a bit of work.
> 
> 
> Regards,
> 
> Paul Angus
> Cloud Architect
> S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus
> paul.an...@shapeblue.com
> 
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: 11 March 2014 19:31
> To: dev@cloudstack.apache.org
> Cc: Hugo Trippaers; Hugo Trippaers (htrippa...@schubergphilis.com); Paul Angus
> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)
> 
> 
> 
>> -Original Message-
>> From: Paul Angus [mailto:paul.an...@shapeblue.com]
>> Sent: Tuesday, March 11, 2014 10:35 AM
>> To: dev@cloudstack.apache.org
>> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>> 
>> Trying to build 4.3,  the process bombs out for me at MySQL HA Strategy.
>> And strangely it seems to be trying to build MySQL from Master (4.4.0-
>> SNAPSHOT)?
> [Animesh] Ok this came in from Hugo's commit that I cherry-picked
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=472a387d2d828e21aff93a750ed3e178837a1879
> 
> from file plugins/database/mysql-ha/pom.xml This is a  version issue which 
> can be fixed but should not affect functioning. Lets hear from Hugo on this.
> 
> 
> The other errors are formatting issues caught by checkstyle plugin that can 
> be ignored. The Jenkins build is successful.
> 
>> 
>> Ideas anyone?
>> 
>> 
>> [INFO] Apache CloudStack Plugin - MySQL HA Strategy .. FAILURE
>> [1.110s] [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-checkstyle-
>> plugin:2.11:check (cloudstack-checkstyle) on project
>> cloud-plugin-database-
>> mysqlha: Failed during checkstyle execution: There are 6 checkstyle
>> errors. -> [Help 1]
>> 
>> [INFO]
>> --
>> -- [INFO] Building Apache CloudStack Plugin - MySQL HA Strategy 4.4.0-
>> SNAPSHOT [INFO]
>> --
>> --
>> [INFO]
>> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
>> cloud-plugin- database-mysqlha --- [INFO] Deleting
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-ha/target (includes = [**/*], excludes =
>> []) [INFO] Deleting
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-ha (includes = [target, dist], excludes =
>> []) [INFO] [INFO] --- maven-checkstyle-plugin:2.11:check
>> (cloudstack-checkstyle) @ cloud-plugin-database-mysqlha --- [INFO] Starting 
>> audit...
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-
>> ha/src/com/cloud/utils/db/StaticStrategy.java:54: Line has trailing spaces.
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-
>> ha/src/com/cloud/utils/db/StaticStrategy.java:58: Line has trailing spaces.
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-
>> ha/src/com/cloud/utils/db/StaticStrategy.java:60: Line has trailing spaces.
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-
>> ha/src/com/cloud/utils/db/StaticStrategy.java:110: Line has trailing spaces.
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-
>> ha/src/com/cloud/utils/db/StaticStrategy.java:120: Line has trailing spaces.
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-
>> ha/src/com/cloud/utils/db/StaticStrategy.java:127: Line has trailing spaces.
>> Audit 

Review Request 19039: CLOUDSTACK-2266: Adding automation tests for IP reservation feature

[Ashutosh Kelkar]

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

Review request for cloudstack, Santhosh Edukulla and SrikanteswaraRao Talluri.


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


Repository: cloudstack-git


Description
---

Adding first set of automation tests for IP reservation feature.


Diffs
-

  test/integration/component/test_ip_reservation.py 224212f 
  tools/marvin/marvin/config/config.cfg 356a291 

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


Testing
---

Yes. Log below.

test_RVR_network (test_ip_reservation.TestIpReservation) ... SKIP: Skip - WIP
test_ip_reservation_in_multiple_networks_same_account 
(test_ip_reservation.TestIpReservation) ... ok
test_nat_rules_nat rule (test_ip_reservation.TestIpReservation) ... ok
test_nat_rules_static nat rule (test_ip_reservation.TestIpReservation) ... ok
test_update_cidr_multiple_vms_not_all_inclusive 
(test_ip_reservation.TestIpReservation) ... ok
test_update_cidr_single_vm_not_inclusive 
(test_ip_reservation.TestIpReservation) ... ok
test_user_defined_cidr (test_ip_reservation.TestIpReservation) ... ok
test_vm_create_after_reservation_LB-NS (test_ip_reservation.TestIpReservation) 
... SKIP: Skipping - this test required netscaler configured in the network
test_vm_create_after_reservation_LB-VR (test_ip_reservation.TestIpReservation) 
... ok
test_vm_create_outside_cidr_after_reservation_LB-NS 
(test_ip_reservation.TestIpReservation) ... SKIP: Skipping - this test required 
netscaler configured in the network
test_vm_create_outside_cidr_after_reservation_LB-VR 
(test_ip_reservation.TestIpReservation) ... ok
--
Ran 11 tests in 3753.613s

OK

Two tests which require Netscaler configured are skipped due to netscaler was 
not available on setup.


Thanks,

Ashutosh Kelkar

Build failed in Jenkins: build-master-slowbuild #410

[jenkins]

See 

--
[...truncated 18098 lines...]

Tests run: 4, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi ---
[INFO] Cobertura 2.0.3 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/amazon/ec2/AmazonEC2SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/amazon/s3/AmazonS3SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SAcl.java.  Ensure this class was instrumented, and this 
data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SBucket.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SHost.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/BucketPolicyDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackAccountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackConfigurationDao.java.  Ensure this 
class was instrumented, and this data file contains the instrumentation 
information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackSvcOfferingDao.java.  Ensure this class 
was instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackUserDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostMountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartPartsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartUploadsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultipartMetaDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does 

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

[Hugo Trippaers]

The compile / pom problems are fixed in 4.3 branch.

@Animesh, i pushed them straight into 4.3 as 4.3-forward is a bit of a mess at 
the moment. See other thread.

Cheers,

Hugo


On 12 mrt. 2014, at 08:14, Paul Angus  wrote:

> If I manually fix the white spaces I can get past MySQL HA Strategy, but then 
> I hit:
> 
> [INFO] 
> 
> [INFO] Building Apache CloudStack Client UI 4.3.0
> [INFO] 
> 
> Downloading: 
> http://repo.maven.apache.org/maven2/org/apache/cloudstack/cloud-plugin-database-mysqlha/4.3.0/cloud-plugin-database-mysqlha-4.3.0.pom
> [WARNING] The POM for 
> org.apache.cloudstack:cloud-plugin-database-mysqlha:jar:4.3.0 is missing, no 
> dependency information available
> Downloading: 
> http://repo.maven.apache.org/maven2/org/apache/cloudstack/cloud-plugin-database-mysqlha/4.3.0/cloud-plugin-database-mysqlha-4.3.0.jar
> [ERROR] Failed to execute goal on project cloud-client-ui: Could not resolve 
> dependencies for project org.apache.cloudstack:cloud-client-ui:war:4.3.0: 
> Could not find artifact 
> org.apache.cloudstack:cloud-plugin-database-mysqlha:jar:4.3.0 in central 
> (http://repo.maven.apache.org/maven2) -> [Help 1]
> 
> MySQL HA Strategy seems to need a bit of work.
> 
> 
> Regards,
> 
> Paul Angus
> Cloud Architect
> S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus
> paul.an...@shapeblue.com
> 
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: 11 March 2014 19:31
> To: dev@cloudstack.apache.org
> Cc: Hugo Trippaers; Hugo Trippaers (htrippa...@schubergphilis.com); Paul Angus
> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)
> 
> 
> 
>> -Original Message-
>> From: Paul Angus [mailto:paul.an...@shapeblue.com]
>> Sent: Tuesday, March 11, 2014 10:35 AM
>> To: dev@cloudstack.apache.org
>> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>> 
>> Trying to build 4.3,  the process bombs out for me at MySQL HA Strategy.
>> And strangely it seems to be trying to build MySQL from Master (4.4.0-
>> SNAPSHOT)?
> [Animesh] Ok this came in from Hugo's commit that I cherry-picked
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=472a387d2d828e21aff93a750ed3e178837a1879
> 
> from file plugins/database/mysql-ha/pom.xml This is a  version issue which 
> can be fixed but should not affect functioning. Lets hear from Hugo on this.
> 
> 
> The other errors are formatting issues caught by checkstyle plugin that can 
> be ignored. The Jenkins build is successful.
> 
>> 
>> Ideas anyone?
>> 
>> 
>> [INFO] Apache CloudStack Plugin - MySQL HA Strategy .. FAILURE
>> [1.110s] [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-checkstyle-
>> plugin:2.11:check (cloudstack-checkstyle) on project
>> cloud-plugin-database-
>> mysqlha: Failed during checkstyle execution: There are 6 checkstyle
>> errors. -> [Help 1]
>> 
>> [INFO]
>> --
>> -- [INFO] Building Apache CloudStack Plugin - MySQL HA Strategy 4.4.0-
>> SNAPSHOT [INFO]
>> --
>> --
>> [INFO]
>> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
>> cloud-plugin- database-mysqlha --- [INFO] Deleting
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-ha/target (includes = [**/*], excludes =
>> []) [INFO] Deleting
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-ha (includes = [target, dist], excludes =
>> []) [INFO] [INFO] --- maven-checkstyle-plugin:2.11:check
>> (cloudstack-checkstyle) @ cloud-plugin-database-mysqlha --- [INFO] Starting 
>> audit...
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-
>> ha/src/com/cloud/utils/db/StaticStrategy.java:54: Line has trailing spaces.
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-
>> ha/src/com/cloud/utils/db/StaticStrategy.java:58: Line has trailing spaces.
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-
>> ha/src/com/cloud/utils/db/StaticStrategy.java:60: Line has trailing spaces.
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-
>> ha/src/com/cloud/utils/db/StaticStrategy.java:110: Line has trailing spaces.
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-
>> ha/src/com/cloud/utils/db/StaticStrategy.java:120: Line has trailing spaces.
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-
>> ha/src/com/cloud/utils/db/StaticStrategy.java:127: Line has trailing spaces.
>> Audit done.
>> 
>> Regards,
>> 
>> Paul Angus
>> Cloud Architect
>> S: +44 20 3603 0540 | M: +44

Differences between 4.3 and 4.3-forward

[Hugo Trippaers]

Hey,

There is a sizable number of differences between the two branch. Maybe it’s 
time to ditch 4.3-forward and recreate it based on current 4.3?

Cheers,

Hugo


Hugos-MacBook-Pro:cloudstack hugo (4.3-forward)$ git diff --stat 4.3-forward 4.3
 
api/src/org/apache/cloudstack/api/command/user/loadbalancer/AssignCertToLoadBalancerCmd.java
|3 +-
 
api/src/org/apache/cloudstack/api/command/user/loadbalancer/RemoveCertFromLoadBalancerCmd.java
  |2 +-
 awsapi/pom.xml 
 |2 +-
 client/pom.xml 
 |   20 ++-
 client/tomcatconf/catalina.properties.in   
 |2 +-
 debian/changelog   
 |7 +-
 developer/pom.xml  
 |1 -
 engine/components-api/src/com/cloud/template/TemplateManager.java  
 |9 +-
 engine/orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java   
 |   36 +
 
engine/orchestration/src/org/apache/cloudstack/engine/orchestration/VolumeOrchestrator.java
 |   10 +-
 
engine/schema/resources/META-INF/cloudstack/core/spring-engine-schema-core-daos-context.xml
 |2 +-
 
engine/schema/src/org/apache/cloudstack/storage/datastore/db/PrimaryDataStoreDao.java
   |2 -
 
engine/schema/src/org/apache/cloudstack/storage/datastore/db/PrimaryDataStoreDaoImpl.java
   |   48 +-
 engine/storage/integration-test/pom.xml
 |5 -
 
engine/storage/src/org/apache/cloudstack/storage/allocator/LocalStoragePoolAllocator.java
   |8 +-
 framework/db/pom.xml   
 |5 -
 framework/db/src/com/cloud/utils/db/StaticStrategy.java
 |  130 
 plugins/database/mysql-ha/pom.xml  
 |   28 
 plugins/database/mysql-ha/src/com/cloud/utils/db/StaticStrategy.java   
 |  133 
 
plugins/hypervisors/hyperv/DotNet/ServerResource/AgentShell/AgentService.Designer.cs
|2 +-
 plugins/hypervisors/hyperv/DotNet/ServerResource/AgentShell/App.config 
 |7 +-
 
plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java
 |6 +-
 
plugins/hypervisors/simulator/src/com/cloud/agent/manager/SimulatorManagerImpl.java
 |6 +-
 
plugins/hypervisors/simulator/src/org/apache/cloudstack/storage/datastore/driver/SimulatorImageStoreDriverImpl.java
 |6 -
 
plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
   |   85 +-
 
plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/discoverer/XcpServerDiscoverer.java
|7 +-
 
plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/CitrixResourceBase.java
   |   70 +++--
 
plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/XcpOssResource.java
   |5 +
 
plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/XenServerConnectionPool.java
  |  452 
-
 plugins/network-elements/juniper-contrail/pom.xml  
 |2 +-
 plugins/pom.xml
 |   11 ++
 pom.xml
 |2 +-
 scripts/vm/network/security_group.py   
 |2 +-
 server/src/com/cloud/api/doc/Argument.java 
 |   14 +-
 server/src/com/cloud/consoleproxy/ConsoleProxyManagerImpl.java 
 |4 +-
 server/src/com/cloud/hypervisor/kvm/discoverer/LibvirtServerDiscoverer.java
 |   14 +-
 server/src/com/cloud/network/E

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

[Paul Angus]

Yes that's correct. I'm building noredist


Regards,

Paul Angus
S: +44 20 3603 0540 | M: 
+447711418784
T: @CloudyAngus
paul.an...@shapeblue.com


 Original message 
From: Hugo Trippaers
Date:12/03/2014 07:32 (GMT+00:00)
To: Paul Angus
Cc: Animesh Chaturvedi ,dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round)

Hey Paul,

Just to be clear, this problem only occurs during the noredist build right?

Mysql HA is one of the noredist features, so it should not be present in the 
regular build.

I’m checking the poms now to see if everything is configured correctly.

Cheers,

Hugo

On 12 mrt. 2014, at 08:14, Paul Angus  wrote:

> If I manually fix the white spaces I can get past MySQL HA Strategy, but then 
> I hit:
>
> [INFO] 
> 
> [INFO] Building Apache CloudStack Client UI 4.3.0
> [INFO] 
> 
> Downloading: 
> http://repo.maven.apache.org/maven2/org/apache/cloudstack/cloud-plugin-database-mysqlha/4.3.0/cloud-plugin-database-mysqlha-4.3.0.pom
> [WARNING] The POM for 
> org.apache.cloudstack:cloud-plugin-database-mysqlha:jar:4.3.0 is missing, no 
> dependency information available
> Downloading: 
> http://repo.maven.apache.org/maven2/org/apache/cloudstack/cloud-plugin-database-mysqlha/4.3.0/cloud-plugin-database-mysqlha-4.3.0.jar
> [ERROR] Failed to execute goal on project cloud-client-ui: Could not resolve 
> dependencies for project org.apache.cloudstack:cloud-client-ui:war:4.3.0: 
> Could not find artifact 
> org.apache.cloudstack:cloud-plugin-database-mysqlha:jar:4.3.0 in central 
> (http://repo.maven.apache.org/maven2) -> [Help 1]
>
> MySQL HA Strategy seems to need a bit of work.
>
>
> Regards,
>
> Paul Angus
> Cloud Architect
> S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus
> paul.an...@shapeblue.com
>
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: 11 March 2014 19:31
> To: dev@cloudstack.apache.org
> Cc: Hugo Trippaers; Hugo Trippaers (htrippa...@schubergphilis.com); Paul Angus
> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>
>
>
>> -Original Message-
>> From: Paul Angus [mailto:paul.an...@shapeblue.com]
>> Sent: Tuesday, March 11, 2014 10:35 AM
>> To: dev@cloudstack.apache.org
>> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>>
>> Trying to build 4.3,  the process bombs out for me at MySQL HA Strategy.
>> And strangely it seems to be trying to build MySQL from Master (4.4.0-
>> SNAPSHOT)?
> [Animesh] Ok this came in from Hugo's commit that I cherry-picked
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=472a387d2d828e21aff93a750ed3e178837a1879
>
> from file plugins/database/mysql-ha/pom.xml This is a  version issue which 
> can be fixed but should not affect functioning. Lets hear from Hugo on this.
>
>
> The other errors are formatting issues caught by checkstyle plugin that can 
> be ignored. The Jenkins build is successful.
>
>>
>> Ideas anyone?
>>
>>
>> [INFO] Apache CloudStack Plugin - MySQL HA Strategy .. FAILURE
>> [1.110s] [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-checkstyle-
>> plugin:2.11:check (cloudstack-checkstyle) on project
>> cloud-plugin-database-
>> mysqlha: Failed during checkstyle execution: There are 6 checkstyle
>> errors. -> [Help 1]
>>
>> [INFO]
>> --
>> -- [INFO] Building Apache CloudStack Plugin - MySQL HA Strategy 4.4.0-
>> SNAPSHOT [INFO]
>> --
>> --
>> [INFO]
>> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
>> cloud-plugin- database-mysqlha --- [INFO] Deleting
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-ha/target (includes = [**/*], excludes =
>> []) [INFO] Deleting
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-ha (includes = [target, dist], excludes =
>> []) [INFO] [INFO] --- maven-checkstyle-plugin:2.11:check
>> (cloudstack-checkstyle) @ cloud-plugin-database-mysqlha --- [INFO] Starting 
>> audit...
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-
>> ha/src/com/cloud/utils/db/StaticStrategy.java:54: Line has trailing spaces.
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-
>> ha/src/com/cloud/utils/db/StaticStrategy.java:58: Line has trailing spaces.
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-
>> ha/src/com/cloud/utils/db/StaticStrategy.java:60: Line has trailing spaces.
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-
>> ha/src/com/cloud/utils/db/StaticStrategy.java:110: Line

Re: [DISCUSS] realhostip.com going away

[Nux!]

On 12.03.2014 01:13, Amogh Vasekar wrote:

Hi,

I was looking at your blog and found you have mentioned that :
"The problem is the intermediate CA cert cannot be added from the web
interface."

Can you please let me know the error you faced while uploading the
intermediate CA cert via the UI?

Thanks,
Amogh


There is no error. You can only upload the CRT and the KEY, there is no 
box for the intermediate. You could try combining the CRT and 
intermediate and put them in the CRT text box, but that didn't get me 
the proper results (ie browser was still complaining about invalid 
cert). Only after I messed with it via phpMyAdmin as described in that 
blog post has it finally started working fine and browsers no longer 
complained.


HTH
Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Re: [DISCUSS]{BEHAVIORAL-CHANGE]Domain-Account-User Sync Up Among Multiple Regions

[Daan Hoogland]

H Alex, I considder Chiradeeps comments quite valid and serious enough
to anticipate not making friday 14:00 CET. That would mean no merge
before 4.4. Can you live with that?

On Wed, Mar 12, 2014 at 6:40 AM, Chiradeep Vittal
 wrote:
> Hi Alex,
>
> If you look at the general design of CloudStack, there are Singleton
> service interfaces which are then implemented with real classes. This
> facilitates easy testing by mocking the interface. In your new files
> (BaseInterface, which by the way is NOT an interface, AccountService,
> which is NOT a service like other CloudStack services, and so on), this
> design paradigm is not followed. Therefore it is incongruous to the rest
> of the code base.
>
> Furthermore this has been plopped right in the middle of other core
> CloudStack code (server/src/com/cloud/region/). If you look at the
> EventBus logic, it has been written as a plugin, thereby enabling users
> who do not need it to disable it. This level of configuration is needed
> and I can't find it.
>
> So, to  summarize:
> 1. Split it into patches. Patch A is the change to the core DAOs, db
> logic, schema upgrade code, etc.
> 2. Patch B is the actual sync service written as an optional plugin with
> the package name space of org.apache.
>
> On 3/11/14, 3:09 PM, "Alex Ough"  wrote:
>
>>Hi Daan,
>>
>>I didn't update the patch after the couple of works because I wanted to do
>>it with others Chiradeep asked if any.
>>Let me know when you want me to.
>>
>>Thanks
>>Alex Ough
>>
>>
>>On Tue, Mar 11, 2014 at 4:37 PM, Daan Hoogland
>>wrote:
>>
>>> I will call the merge in a moment, but won't do it immediately.
>>>
>>> Be there for me when any issues come up. If not I will revert it.
>>>
>>> @Chiradeep: did Alex answer your concerns adequately?
>>>
>>>
>>> kind regards,
>>>
>>> On Tue, Mar 11, 2014 at 6:43 PM, Alex Ough 
>>>wrote:
>>> > I worked on a couple of items, so can you give me the confirmation for
>>> the
>>> > rest items so that I can wrap this up?
>>> > I really want to include this into 4.4.
>>> >
>>> > Thanks
>>> > Alex Ough
>>> >
>>> >
>>> > On Mon, Mar 10, 2014 at 3:41 PM, Alex Ough 
>>> wrote:
>>> >
>>> >> Please see my reply/question in blue.
>>> >>
>>> >> Thanks
>>> >> Alex Ough
>>> >>
>>> >>
>>> >> On Mon, Mar 10, 2014 at 1:25 PM, Chiradeep Vittal <
>>> >> chiradeep.vit...@citrix.com> wrote:
>>> >>
>>> >>> I haven¹t looked at it because it is huge. But preliminary scan:
>>> >>>
>>> >>> - there are unit tests missing for changes to core CS code
>>> >>>
>>> >>  Unit tests for only new classes were added because I
>>>couldn't
>>> >> find unit tests of the ones I modified
>>> >>
>>> >>
>>> >>> - uses com.amazonaws.util.json (why?)
>>> >>>
>>> >>  They are used to handle the json objects. Let me know if you
>>> >> want me to replace it with another.
>>> >>
>>> >> - code format does not follow coding convention ( placement of {},
>>>camel
>>> >>> case api_interface )
>>> >>>
>>> >>  Done
>>> >>
>>> >>
>>> >>> - package namespace is com.cloud instead of org.apache for new files
>>> >>>
>>> >>  I didn't know that. So do I need to use 'org.apache' package
>>> for
>>> >> all new classes?
>>> >>
>>> >> - no file-level comments. What does LocalAccountManager do? Why does
>>>it
>>> >>> exist? Etc.
>>> >>>
>>> >>  Done.
>>> >>
>>> >>
>>> >>> - No interfaces, only abstract classes. No use of @Inject. While
>>>this
>>> >>> might be OK, it does make it harder to test and does not follow the
>>> rest
>>> >>> of ACS conventions.
>>> >>>
>>> >> I don't think there is any interface, but let me know if you
>>> find
>>> >> any.
>>> >> Any recommendation to replace @inject?
>>> >>
>>> >>>
>>> >>> I would urge the submitter to break up the submission.
>>> >>> A) the changes to CS core, with explanations / comments and tests
>>> >>> B) the sync service should be an interface with concrete
>>> implementations
>>> >>> in its own package
>>> >>> C) more tests
>>> >>>
>>> >> can you give me a little specific what kind of tests you need
>>> >> more?
>>> >>
>>> >>
>>> >>
>>> >>>  On 3/10/14, 3:37 AM, "Daan Hoogland" 
>>>wrote:
>>> >>>
>>> >>> >Hi everyody,
>>> >>> >
>>> >>> >The people at sungard have been making this change for 4.4 and I
>>>want
>>> >>> >to merge/apply it this week. It is more then a screenfull and might
>>> >>> >cause issue is a setup or two.
>>> >>> >
>>> >>> >have a look at https://reviews.apache.org/r/17790/
>>> >>> >
>>> >>> >a ref to ticket and fs page are in the review request.
>>> >>> >
>>> >>> >kind regards,
>>> >>> >--
>>> >>> >Daan
>>> >>>
>>> >>>
>>> >>>
>>> >>
>>>
>>>
>>>
>>> --
>>> Daan
>>>
>>>
>



-- 
Daan

[WIKI] Release test procedure contains wrong version of Java Open JDK

[Wilder Rodrigues]

Hi guys and gals,

Could I get rights to the Apache Wiki page? In case that's not possible, could 
someone please edit the page and change the version of the Java JDK? It now 
says 1.6 instead of 1.7.

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

sudo aptitude install openjdk-6-jdk

Thanks in advance

Cheers,
Wilder

RE: [WIKI] Release test procedure contains wrong version of Java Open JDK

[Wilder Rodrigues]

Already got rights and page has been edited.

Thanks, Daan!

Cheers,
Wilder

-Original Message-
From: Wilder Rodrigues [mailto:wrodrig...@schubergphilis.com] 
Sent: Wednesday, March 12, 2014 10:19 AM
To: dev@cloudstack.apache.org
Subject: [WIKI] Release test procedure contains wrong version of Java Open JDK

Hi guys and gals,

Could I get rights to the Apache Wiki page? In case that's not possible, could 
someone please edit the page and change the version of the Java JDK? It now 
says 1.6 instead of 1.7.

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

sudo aptitude install openjdk-6-jdk

Thanks in advance

Cheers,
Wilder

Can't create system VM

[Tejas Gadaria]

Hi,

I am facing following error while trying to create system vm's.
I am using CS 4.0.2
Logs are given below..

2014-03-12 14:36:03,819 ERROR [vmware.mo.VirtualMachineMO]
(DirectAgent-3:10.129.146.101) VMware createSnapshot_Task failed due to
Invalid virtual machine configuration. com.vmware.vim25.InvalidVmConfig
2014-03-12 14:36:04,023 DEBUG [cloud.server.StatsCollector]
(StatsCollector-3:null) VmStatsCollector is running...
2014-03-12 14:36:05,283 ERROR [vmware.manager.VmwareStorageManagerImpl]
(DirectAgent-3:10.129.146.101) Unable to create base snapshot for template,
templateName: routing-8, templateUuid: 041eb0533104aa0ce5b8122ff868
2014-03-12 14:36:05,283 ERROR [vmware.manager.VmwareStorageManagerImpl]
(DirectAgent-3:10.129.146.101) Unable to execute
PrimaryStorageDownloadCommand due to exception
java.lang.Exception: Unable to create base snapshot for template,
templateName: routing-8, templateUuid: 041eb0533104aa0ce5b8122ff868
at
com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.copyTemplateFromSecondaryToPrimary(VmwareStorageManagerImpl.java:477)
at
com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.execute(VmwareStorageManagerImpl.java:138)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3509)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:401)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:701)
2014-03-12 14:36:05,285 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-3:null) Seq 1-1844903945: Response Received:
2014-03-12 14:36:05,285 DEBUG [agent.transport.Request]
(DirectAgent-3:null) Seq 1-1844903945: Processing:  { Ans: , MgmtId:
345052169635, via: 1, Ver: v1, Flags: 110,
[{"storage.PrimaryStorageDownloadAnswer":{"templateSize":0,"result":false,"details":"Unable
to execute PrimaryStorageDownloadCommand due to exception","wait":0}}] }
2014-03-12 14:36:05,286 DEBUG [agent.transport.Request]
(consoleproxy-1:null) Seq 1-1844903945: Received:  { Ans: , MgmtId:
345052169635, via: 1, Ver: v1, Flags: 110, { PrimaryStorageDownloadAnswer }
}
2014-03-12 14:36:05,286 DEBUG [agent.manager.AgentManagerImpl]
(consoleproxy-1:null) Details from executing class
com.cloud.agent.api.storage.PrimaryStorageDownloadCommand: Unable to
execute PrimaryStorageDownloadCommand due to exception
2014-03-12 14:36:05,286 DEBUG [cloud.template.TemplateManagerImpl]
(consoleproxy-1:null) Template 8 download to pool 202 failed due to Unable
to execute PrimaryStorageDownloadCommand due to exception
2014-03-12 14:36:05,286 DEBUG [cloud.template.TemplateManagerImpl]
(consoleproxy-1:null) Downloading 8 via 1
2014-03-12 14:36:05,290 DEBUG [agent.manager.AgentAttache]
(DirectAgent-3:null) Seq 1-1844903945: No more commands found
2014-03-12 14:36:05,292 DEBUG [agent.transport.Request]
(consoleproxy-1:null) Seq 1-1844903966: Sending  { Cmd , MgmtId:
345052169635, via: 1, Ver: v1, Flags: 100111,
[{"storage.PrimaryStorageDownloadCommand":{"localPath":"/mnt/a108a303-3f9c-3369-8ed1-c66d52b325e1","poolUuid":"a108a303-3f9c-3369-8ed1-c66d52b325e1","poolId":202,"secondaryStorageUrl":"nfs://
10.129.146.41/vol/secondary","primaryStorageUrl":"nfs://
10.129.146.41/vol/primary/","url":"nfs://
10.129.146.41/vol/secondary/template/tmpl/1/8/","format":"OVA","accountId":1,"name":"routing-8","wait":10800}}]
}
2014-03-12 14:36:05,292 DEBUG [agent.transport.Request]
(consoleproxy-1:null) Seq 1-1844903966: Executing:  { Cmd , MgmtId:
345052169635, via: 1, Ver: v1, Flags: 100111,
[{"storage.PrimaryStorageDownloadCommand":{"localPath":"/mnt/a108a303-3f9c-3369-8ed1-c66d52b325e1","poolUuid":"a108a303-3f9c-3369-8ed1-c66d52b325e1","poolId":202,"secondaryStorageUrl":"nfs://
10.129.146.41/vol/secondary","primaryStorageUrl":"nfs://
10.129.146.41/vol/primary/","url":"nfs://
10.129.146.41/vol/secondary/template/tmpl/1/8/","format":"OVA","accountId":1,"name":"routing-8","wait":10800}}]
}
2014-03-12 14:36:05,293 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-18:null) Seq 1-1844903966: Executing request
2014-03-12 14:36:05,295 INFO  [vmware.resource.VmwareResource]
(DirectAgent-18:10.129.146.101) Executing resource
PrimaryStorageDownloadCommand:
{"localPath":"/mnt/a108a303-3f9c-3369-8ed1-c66d52b325e1","poolUuid":"a108a303-3f9c-3369-8ed1-

RE: [DISCUSS] Enabling databse upgrades on master branch

[Miguel Ferreira]

I did a quick scan of the two tools proposed by Rajani and here's what I found:


-Liquibase:

o   With Liquibase we would need to specify the changes (in change sets) to the 
database (using either XML, YAML, JSON or SQL).

o   Each change set would then be applied by the tool to a running DB , and 
that would entail schema changes as well as data migration.

o   The data migration part seems especially simple, yet powerful.

o   The tool seems to offer the rollback capability for free as long as the 
change sets are written using its own dialect. But if the change set is 
specified directly in SQL, there is the option to define (also in SQL) the 
rollback procedure.

-Flyaway

o   Flyaway seems to be very much similar to the DB upgrade tool ACS currently 
has, although more elaborate and feature rich.

o   It provides a java API, a command line tool, as well as maven, gradle, ant 
and SBT support.

o   Compared with Liquibase it seems to me a more free-form-like approach 
(again, similar to what exists now in ACS)

o   Incremental changes to the DB are programmed in Java and then applied by 
the tool.

o   It supports upgrades to specific versions (say from 4.2 to 3.4 when the 
latest is 4.0 for example), as proposed by Alex Huang.

Both tools seem capable of improving the current DB upgrade procedure, but they 
both require the change I already proposed in the way ACS developers maintain 
DB related code. They both require that changes are made incrementally and 
independently of each other.

All-in-all I think Liquibase is a better tool for the job.

Cheers,
Miguel

From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: dinsdag 11 maart 2014 6:52
To: dev@cloudstack.apache.org
Cc: Miguel Ferreira
Subject: Re: [DISCUSS] Enabling databse upgrades on master branch

Right...I'll just quickly chime in on this, but Daan described the issue well.

We simply do not have a way to upgrade the DB (in an automated way) in a 
fine-grained enough fashion during development. This is a common problem on 
many projects...not just CloudStack.

Sometimes it's easy enough to perform a manual upgrade. In these cases, I would 
encourage developers to send out an e-mail with the [DB-CHANGE] tag and let 
others now how to perform such an upgrade. This will decrease the number of 
times people have to destroy and re-create their environments.


At some point, hopefully we can have Git send out an e-mail to notify people of 
schema changes. Then they will at least know not to fetch the latest until they 
are ready to deal with the consequences.

On Tue, Mar 11, 2014 at 4:18 AM, Daan Hoogland 
mailto:daan.hoogl...@gmail.com>> wrote:
Alex,

That would only work in a dev environment, would it? so running maven
you could choose to upgrade your db. At the moment when your db is at
master, how would you decide you need to upgrade beyond your prior
commit up to the present one? Also, having pulled in new code, not
upgrading the db is not an option with our present way of working as
the dao object would throw all kinds of errors.

What Mike is seeing is due to the granularity of the upgrade being not
fine grained enough for his needs, not due to the absence of it, i
agree. Any one, developer or not that dares to upgrade more often the
by following the release schedule, thus helping us with valuable test
data, will run into this problem.


On Tue, Mar 11, 2014 at 11:06 AM, Alex Huang 
mailto:alex.hu...@citrix.com>> wrote:
> I'm fine with us moving toward other tools but I do want to point this out.  
> What Mike and others are seeing is NOT due to CloudStack's schema upgrade 
> procedure is not incremental but the fact that incremental upgrade is 
> automatically performed when CloudStack management server is rebooted.
>
> As I've said in other threads, we should just replace the automatic db 
> upgrade in CloudStack with a check for the correct version and put in a pom 
> step to upgrade the db so a developer can upgrade the db schema when they so 
> chooses.
>
> --Alex
>
>> -Original Message-
>> From: Miguel Ferreira 
>> [mailto:mferre...@schubergphilis.com]
>> Sent: Tuesday, March 11, 2014 2:58 AM
>> To: dev@cloudstack.apache.org
>> Cc: Alex Huang
>> Subject: RE: [DISCUSS] Enabling databse upgrades on master branch
>>
>> Hi Rajani,
>>
>> Indeed I see the overlap with the previous discussion that is taking place. I
>> actually tried to chip-in that discussion.
>> I do agree with you on introducing tools that can support the database
>> upgrade process, but meanwhile a small change in the way developers
>> maintain the database related code could already bring us very far.
>>
>> As of now I'm working on a separate project with the following roadmap:
>> - detect potential conflicts (and collect data about them)
>> - learn from the data collected which conflicts can we resolve automatically,
>> which we cannot
>> - for the conflicts th

Affinity Groups and Project

[zcsu]

Question: Whether Project can not support Affinity Groups?
Environment: CS4.2 + Xenserver6.2
   Advance Zone
Step:
1.  I set a host as dedicated host to an account, affinity groups will 
auto create a affinity groups with type ExplicitDedication .
 2. Then I create a Project and add the account has dedicated host.
 
when I try creat a VM in Project view, I can select affinity groups has been 
auto created. but created VM will failed with error "Entity AffinityGroup 
[dc4751ao-d2cb-463e-8351-384b9422313] and entity acct 
[3f526aid-d9ab-40ec-a6a5-9b61c84cb1el-PrjAcct-CPSM-1] belong to different 
accounts"
 
Note: I also try to create new affinity groups in project ,the same error 
happend.
 
So  Project can not use Affinity Groups? If is yes, why affinity group display 
in project view?
 
Anybody can answer, very thanks!
 
 
 
 
  

Re: Review Request 18964: Windowsfication of CloudStack Management Server - Changes to support windows OS

[Donal Lafferty]

> On March 11, 2014, 12:28 p.m., Donal Lafferty wrote:
> > 1.  How do you guarantee that 'sudo' is never added to scripts created by 
> > the Script class?  See (utils/src/com/cloud/utils/script/Script.java)
> > 
> > 2.  How do you version control the .exe?
> > 
> > 3.  WiX can be run on Linux in a WINE environment.  Could the 
> > Windowsfication team check whether it would be reasonable to call WiX from 
> > a Maven POM that does uses WINE if in a Linux environment?  This might 
> > avoid having to checkin a .exe
> 
> Damodar Reddy Talakanti wrote:
> 1. The final thing we wanted to do is to convert all shell scripts which 
> are getting called inside management server(This does not include Agents as 
> always they run on Linux Environments) to python scripts. For now I 
> identified the shell scripts those are getting called in side management 
> server and written python script(s) for them (Still need to write for seed 
> system template) and calling for only windows environemnt. In the next phase 
> I will remove OS 
> checks inside the code and will call python scripts only.
> 2. start.exe is generated out of start.bat so version control is on 
> start.bar actually.
> 3. We will check on this.
> 
> Donal Lafferty wrote:
> Hi Damodar,
> 
> WRT #2, I don't mean source version control.  I was thinking of the 
> version reported by the .exe  E.g windows .exe's often use the pattern 
> Major.Minor.Build.Revision  I want to understand where the version 
> information on start.exe is coming from.
> 
> Could you point me to the source for start.exe?
>
> 
> Damodar Reddy Talakanti wrote:
> Hi Donal,
> 
>  I was also looking into the specific format of .exe but I could not get 
> much on that. If you can point me to some link that is good for me. 
> Actually we have used Quick Batch Compiler to convert to .exe format.

Hi Damodar,

If I understand correctly, start.exe is generated from the most recent 
start.bat using "Quick Batch Compiler".  In that case, it would not be 
appropriate to check in start.exe, because it would be like checking in .class 
files.  Would it be possible to create a Maven task to carry these instructions 
out, and document setup at 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Cloudstack+Windowsfication
 ?

WRT running as a Windows Service, you will not see Start/Stop functionality if 
you register start.exe as a service.  The batch file does not expose the hooks 
that Windows Service Control Manager (SCM) uses to control a service DLL.  You 
start the underlying TomCat as a Windows Service instead, e.g. 
http://tomcat.apache.org/tomcat-6.0-doc/windows-service-howto.html.  Note that 
the Hyper-V agent implements SCM hooks by subtyping ServiceBase, see 
http://msdn.microsoft.com/en-us/library/System.ServiceProcess(v=vs.110).aspx  
Java equivalents are discussed here: 
http://stackoverflow.com/questions/68113/how-to-create-a-windows-service-from-java-app

WRT testing, the feature spec says you are targeting Win2K12R2, which is not 
the same as Windows8.  I would strongly recommend you test the target platform. 
 To save time, why don't you ask if any community members are able to do the 
checks for you.

WRT scripting, how did you seed the systemVM templates?  Is there a work around 
until a python script is available?

 


- Donal


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


On March 11, 2014, 12:45 p.m., Damodar Reddy Talakanti wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/18964/
> ---
> 
> (Updated March 11, 2014, 12:45 p.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and Chiradeep Vittal.
> 
> 
> Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-6105
> 
> https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/CLOUDSTACK-6105
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Windowsfication of CloudStack Management Server
> 
> 
> Diffs
> -
> 
>   scripts/installer/windows/acs.wxs PRE-CREATION 
>   scripts/installer/windows/client.wxs PRE-CREATION 
>   scripts/installer/windows/start.bat PRE-CREATION 
>   scripts/installer/windows/start.exe PRE-CREATION 
>   scripts/vm/systemvm/injectkeys.py PRE-CREATION 
>   server/src/com/cloud/server/ConfigurationServerImpl.java b8da4c8 
> 
> Diff: https://reviews.apache.org/r/18964/diff/
> 
> 
> Testing
> ---
> 
> Tested in Linux environment after changes 
> Also tested in Windows environment(For now tested on windows-8) to make sure 
> it is getting installed and management service is running.
> 
> Able to add zones, able to register templates, able to launc

Re: [DISCUSS] Enabling databse upgrades on master branch

[Daan Hoogland]

H Miguel,

Are these tools free for each dev. This might not be a restriction but
would have my preference. what about redistributable parts, like
classes that are part of the engine they implement?

On Wed, Mar 12, 2014 at 10:41 AM, Miguel Ferreira
 wrote:
> I did a quick scan of the two tools proposed by Rajani and here's what I 
> found:
>
>
> -Liquibase:
>
> o   With Liquibase we would need to specify the changes (in change sets) to 
> the database (using either XML, YAML, JSON or SQL).
>
> o   Each change set would then be applied by the tool to a running DB , and 
> that would entail schema changes as well as data migration.
>
> o   The data migration part seems especially simple, yet powerful.
>
> o   The tool seems to offer the rollback capability for free as long as the 
> change sets are written using its own dialect. But if the change set is 
> specified directly in SQL, there is the option to define (also in SQL) the 
> rollback procedure.
>
> -Flyaway
>
> o   Flyaway seems to be very much similar to the DB upgrade tool ACS 
> currently has, although more elaborate and feature rich.
>
> o   It provides a java API, a command line tool, as well as maven, gradle, 
> ant and SBT support.
>
> o   Compared with Liquibase it seems to me a more free-form-like approach 
> (again, similar to what exists now in ACS)
>
> o   Incremental changes to the DB are programmed in Java and then applied by 
> the tool.
>
> o   It supports upgrades to specific versions (say from 4.2 to 3.4 when the 
> latest is 4.0 for example), as proposed by Alex Huang.
>
> Both tools seem capable of improving the current DB upgrade procedure, but 
> they both require the change I already proposed in the way ACS developers 
> maintain DB related code. They both require that changes are made 
> incrementally and independently of each other.
>
> All-in-all I think Liquibase is a better tool for the job.
>
> Cheers,
> Miguel
>
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: dinsdag 11 maart 2014 6:52
> To: dev@cloudstack.apache.org
> Cc: Miguel Ferreira
> Subject: Re: [DISCUSS] Enabling databse upgrades on master branch
>
> Right...I'll just quickly chime in on this, but Daan described the issue well.
>
> We simply do not have a way to upgrade the DB (in an automated way) in a 
> fine-grained enough fashion during development. This is a common problem on 
> many projects...not just CloudStack.
>
> Sometimes it's easy enough to perform a manual upgrade. In these cases, I 
> would encourage developers to send out an e-mail with the [DB-CHANGE] tag and 
> let others now how to perform such an upgrade. This will decrease the number 
> of times people have to destroy and re-create their environments.
>
>
> At some point, hopefully we can have Git send out an e-mail to notify people 
> of schema changes. Then they will at least know not to fetch the latest until 
> they are ready to deal with the consequences.
>
> On Tue, Mar 11, 2014 at 4:18 AM, Daan Hoogland 
> mailto:daan.hoogl...@gmail.com>> wrote:
> Alex,
>
> That would only work in a dev environment, would it? so running maven
> you could choose to upgrade your db. At the moment when your db is at
> master, how would you decide you need to upgrade beyond your prior
> commit up to the present one? Also, having pulled in new code, not
> upgrading the db is not an option with our present way of working as
> the dao object would throw all kinds of errors.
>
> What Mike is seeing is due to the granularity of the upgrade being not
> fine grained enough for his needs, not due to the absence of it, i
> agree. Any one, developer or not that dares to upgrade more often the
> by following the release schedule, thus helping us with valuable test
> data, will run into this problem.
>
>
> On Tue, Mar 11, 2014 at 11:06 AM, Alex Huang 
> mailto:alex.hu...@citrix.com>> wrote:
>> I'm fine with us moving toward other tools but I do want to point this out.  
>> What Mike and others are seeing is NOT due to CloudStack's schema upgrade 
>> procedure is not incremental but the fact that incremental upgrade is 
>> automatically performed when CloudStack management server is rebooted.
>>
>> As I've said in other threads, we should just replace the automatic db 
>> upgrade in CloudStack with a check for the correct version and put in a pom 
>> step to upgrade the db so a developer can upgrade the db schema when they so 
>> chooses.
>>
>> --Alex
>>
>>> -Original Message-
>>> From: Miguel Ferreira 
>>> [mailto:mferre...@schubergphilis.com]
>>> Sent: Tuesday, March 11, 2014 2:58 AM
>>> To: dev@cloudstack.apache.org
>>> Cc: Alex Huang
>>> Subject: RE: [DISCUSS] Enabling databse upgrades on master branch
>>>
>>> Hi Rajani,
>>>
>>> Indeed I see the overlap with the previous discussion that is taking place. 
>>> I
>>> actually tried to chip-in that discussion.
>>> I do agree with you on introducing tool

RE: Affinity Groups and Project

[Saksham Srivastava]

Can you provide more logs, you can upload them on pastebin.

Thanks,
Saksham

-Original Message-
From: zcsu [mailto:szc...@hotmail.com] 
Sent: Wednesday, March 12, 2014 3:15 PM
To: dev@cloudstack.apache.org
Subject: Affinity Groups and Project

Question: Whether Project can not support Affinity Groups?
Environment: CS4.2 + Xenserver6.2
   Advance Zone
Step:
1.  I set a host as dedicated host to an account, affinity groups will 
auto create a affinity groups with type ExplicitDedication .
 2. Then I create a Project and add the account has dedicated host.
 
when I try creat a VM in Project view, I can select affinity groups has been 
auto created. but created VM will failed with error "Entity AffinityGroup 
[dc4751ao-d2cb-463e-8351-384b9422313] and entity acct 
[3f526aid-d9ab-40ec-a6a5-9b61c84cb1el-PrjAcct-CPSM-1] belong to different 
accounts"
 
Note: I also try to create new affinity groups in project ,the same error 
happend.
 
So  Project can not use Affinity Groups? If is yes, why affinity group display 
in project view?
 
Anybody can answer, very thanks!
 
 
 
 
  

Re: [DISCUSS] Enabling databse upgrades on master branch

[Rajani Karuturi]

both are under Open Source: Apache 2.0 License

I would also vote for liquibase as it xml driven(and database independent 
format) and it can output SQL to file(easier for db reviews).

But, as Miguel already said, our current setup is more close flywaydb and it 
may be easier to migrate to it.


~Rajani



On 12-Mar-2014, at 3:28 pm, Daan Hoogland 
mailto:daan.hoogl...@gmail.com>> wrote:

H Miguel,

Are these tools free for each dev. This might not be a restriction but
would have my preference. what about redistributable parts, like
classes that are part of the engine they implement?

On Wed, Mar 12, 2014 at 10:41 AM, Miguel Ferreira
mailto:mferre...@schubergphilis.com>> wrote:
I did a quick scan of the two tools proposed by Rajani and here's what I found:


-Liquibase:

o   With Liquibase we would need to specify the changes (in change sets) to the 
database (using either XML, YAML, JSON or SQL).

o   Each change set would then be applied by the tool to a running DB , and 
that would entail schema changes as well as data migration.

o   The data migration part seems especially simple, yet powerful.

o   The tool seems to offer the rollback capability for free as long as the 
change sets are written using its own dialect. But if the change set is 
specified directly in SQL, there is the option to define (also in SQL) the 
rollback procedure.

-Flyaway

o   Flyaway seems to be very much similar to the DB upgrade tool ACS currently 
has, although more elaborate and feature rich.

o   It provides a java API, a command line tool, as well as maven, gradle, ant 
and SBT support.

o   Compared with Liquibase it seems to me a more free-form-like approach 
(again, similar to what exists now in ACS)

o   Incremental changes to the DB are programmed in Java and then applied by 
the tool.

o   It supports upgrades to specific versions (say from 4.2 to 3.4 when the 
latest is 4.0 for example), as proposed by Alex Huang.

Both tools seem capable of improving the current DB upgrade procedure, but they 
both require the change I already proposed in the way ACS developers maintain 
DB related code. They both require that changes are made incrementally and 
independently of each other.

All-in-all I think Liquibase is a better tool for the job.

Cheers,
Miguel

From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: dinsdag 11 maart 2014 6:52
To: dev@cloudstack.apache.org
Cc: Miguel Ferreira
Subject: Re: [DISCUSS] Enabling databse upgrades on master branch

Right...I'll just quickly chime in on this, but Daan described the issue well.

We simply do not have a way to upgrade the DB (in an automated way) in a 
fine-grained enough fashion during development. This is a common problem on 
many projects...not just CloudStack.

Sometimes it's easy enough to perform a manual upgrade. In these cases, I would 
encourage developers to send out an e-mail with the [DB-CHANGE] tag and let 
others now how to perform such an upgrade. This will decrease the number of 
times people have to destroy and re-create their environments.


At some point, hopefully we can have Git send out an e-mail to notify people of 
schema changes. Then they will at least know not to fetch the latest until they 
are ready to deal with the consequences.

On Tue, Mar 11, 2014 at 4:18 AM, Daan Hoogland 
mailto:daan.hoogl...@gmail.com>>
 wrote:
Alex,

That would only work in a dev environment, would it? so running maven
you could choose to upgrade your db. At the moment when your db is at
master, how would you decide you need to upgrade beyond your prior
commit up to the present one? Also, having pulled in new code, not
upgrading the db is not an option with our present way of working as
the dao object would throw all kinds of errors.

What Mike is seeing is due to the granularity of the upgrade being not
fine grained enough for his needs, not due to the absence of it, i
agree. Any one, developer or not that dares to upgrade more often the
by following the release schedule, thus helping us with valuable test
data, will run into this problem.


On Tue, Mar 11, 2014 at 11:06 AM, Alex Huang 
mailto:alex.hu...@citrix.com>>
 wrote:
I'm fine with us moving toward other tools but I do want to point this out.  
What Mike and others are seeing is NOT due to CloudStack's schema upgrade 
procedure is not incremental but the fact that incremental upgrade is 
automatically performed when CloudStack management server is rebooted.

As I've said in other threads, we should just replace the automatic db upgrade 
in CloudStack with a check for the correct version and put in a pom step to 
upgrade the db so a developer can upgrade the db schema when they so chooses.

--Alex

-Original Message-
From: Miguel Ferreira 
[mailto:mferre...@schubergphilis.com]
Sent: Tuesday, March 11, 2014 2:58 AM
To: 
dev@cloudstack.apache.org

RE: How writing a new api of Pause VirtualMachine

[Stephen Turner]

Not answering your question, but note that XenServer has two different 
concepts: pause/unpause and suspend/resume. Normally you want suspend, which 
suspends to disk; with pause, the VM will continue using memory. In fact, the 
XenServer UI (XenCenter) doesn't even expose pause.

-- 
Stephen Turner


-Original Message-
From: Yitao Jiang [mailto:willier...@gmail.com] 
Sent: 12 March 2014 04:55
To: dev@cloudstack.apache.org
Subject: How writing a new api of Pause VirtualMachine

Hi,
  I wanna pause a vm and resume it in cloudstack4.2.1 with xenserver 6.2 
hypervisor, but CS did not implement this feature, so i wondered if you 
experienced guys can do something for this.Or give me some useful informations 
about how doing this.

Thanks,

Yitao

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

[Damoder Reddy]

HI Paul,

 After you pull Hugo changes are you able to build now?

Thanks & Regards
Damodar/

-Original Message-
From: Paul Angus [mailto:paul.an...@shapeblue.com] 
Sent: Wednesday, March 12, 2014 2:04 PM
To: Hugo Trippaers
Cc: Animesh Chaturvedi; dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round)

Yes that's correct. I'm building noredist


Regards,

Paul Angus
S: +44 20 3603 0540 | M: 
+447711418784
T: @CloudyAngus
paul.an...@shapeblue.com


 Original message 
From: Hugo Trippaers
Date:12/03/2014 07:32 (GMT+00:00)
To: Paul Angus
Cc: Animesh Chaturvedi ,dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round)

Hey Paul,

Just to be clear, this problem only occurs during the noredist build right?

Mysql HA is one of the noredist features, so it should not be present in the 
regular build.

I'm checking the poms now to see if everything is configured correctly.

Cheers,

Hugo

On 12 mrt. 2014, at 08:14, Paul Angus  wrote:

> If I manually fix the white spaces I can get past MySQL HA Strategy, but then 
> I hit:
>
> [INFO] 
> --
> -- [INFO] Building Apache CloudStack Client UI 4.3.0 [INFO] 
> --
> --
> Downloading: 
> http://repo.maven.apache.org/maven2/org/apache/cloudstack/cloud-plugin
> -database-mysqlha/4.3.0/cloud-plugin-database-mysqlha-4.3.0.pom
> [WARNING] The POM for 
> org.apache.cloudstack:cloud-plugin-database-mysqlha:jar:4.3.0 is 
> missing, no dependency information available
> Downloading: 
> http://repo.maven.apache.org/maven2/org/apache/cloudstack/cloud-plugin
> -database-mysqlha/4.3.0/cloud-plugin-database-mysqlha-4.3.0.jar
> [ERROR] Failed to execute goal on project cloud-client-ui: Could not 
> resolve dependencies for project 
> org.apache.cloudstack:cloud-client-ui:war:4.3.0: Could not find 
> artifact org.apache.cloudstack:cloud-plugin-database-mysqlha:jar:4.3.0 
> in central (http://repo.maven.apache.org/maven2) -> [Help 1]
>
> MySQL HA Strategy seems to need a bit of work.
>
>
> Regards,
>
> Paul Angus
> Cloud Architect
> S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus 
> paul.an...@shapeblue.com
>
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: 11 March 2014 19:31
> To: dev@cloudstack.apache.org
> Cc: Hugo Trippaers; Hugo Trippaers (htrippa...@schubergphilis.com); 
> Paul Angus
> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>
>
>
>> -Original Message-
>> From: Paul Angus [mailto:paul.an...@shapeblue.com]
>> Sent: Tuesday, March 11, 2014 10:35 AM
>> To: dev@cloudstack.apache.org
>> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>>
>> Trying to build 4.3,  the process bombs out for me at MySQL HA Strategy.
>> And strangely it seems to be trying to build MySQL from Master 
>> (4.4.0- SNAPSHOT)?
> [Animesh] Ok this came in from Hugo's commit that I cherry-picked
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;
> h=472a387d2d828e21aff93a750ed3e178837a1879
>
> from file plugins/database/mysql-ha/pom.xml This is a  version issue which 
> can be fixed but should not affect functioning. Lets hear from Hugo on this.
>
>
> The other errors are formatting issues caught by checkstyle plugin that can 
> be ignored. The Jenkins build is successful.
>
>>
>> Ideas anyone?
>>
>>
>> [INFO] Apache CloudStack Plugin - MySQL HA Strategy .. FAILURE 
>> [1.110s] [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-checkstyle-
>> plugin:2.11:check (cloudstack-checkstyle) on project
>> cloud-plugin-database-
>> mysqlha: Failed during checkstyle execution: There are 6 checkstyle 
>> errors. -> [Help 1]
>>
>> [INFO]
>> -
>> -
>> -- [INFO] Building Apache CloudStack Plugin - MySQL HA Strategy 
>> 4.4.0- SNAPSHOT [INFO]
>> -
>> -
>> --
>> [INFO]
>> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
>> cloud-plugin- database-mysqlha --- [INFO] Deleting
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-ha/target (includes = [**/*], excludes =
>> []) [INFO] Deleting
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-ha (includes = [target, dist], excludes 
>> =
>> []) [INFO] [INFO] --- maven-checkstyle-plugin:2.11:check
>> (cloudstack-checkstyle) @ cloud-plugin-database-mysqlha --- [INFO] Starting 
>> audit...
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-
>> ha/src/com/cloud/utils/db/StaticStrategy.java:54: Line has trailing spaces.
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-
>> ha/src/com/cloud/utils/db/S

Developer access to JIRA please

[Stephen Turner]

I have three developers on my team who have started to work on CloudStack, 
mostly in the UI and API area. Could somebody kindly give our JIRA accounts 
developer rights, so that we can assign and resolve bugs? Our ids are:

stephen.tur...@citrix.com (Yes, my id is the 
same as my email address)
gabora (Gabor Apati-Nagy)
mihaelas (Mihaela Stoica)
kc284 (Konstantina Chremmou, known as Tina)

Thank you very much,

--
Stephen Turner

Re: [CS4.1] Error during ip range creation

[nicolas.lamirault]

I've got the same error during creation of a network :

http://pastebin.com/aXryp0jj

Le 11/03/2014 15:13, nicolas.lamira...@orange.com a écrit :

Hi,
Nobody has ideas for what concerns ?

Le 10/03/2014 17:32, LAMIRAULT Nicolas MBS a écrit :

Hi,

I creates a network using API.
Then, I try to creates a new IP Range associated to this network. I've
got an error. This is the output logs in this paste [1]

Searching into the Cloudstack code, I find that :

if (vlanId.equals(vlan.getVlanTag()) &&
newVlanSubnet.equals(otherVlanSubnet)) {
   if (NetUtils.ipRangesOverlap(startIP, endIP, otherVlanStartIP,
otherVlanEndIP)) {
 throw new InvalidParameterValueException("The IP range with
tag: " + vlan.getVlanTag()
 + " already has IPs that overlap with the new range.
Please specify a different start IP/end IP.");
   }
   if (!vlanGateway.equals(otherVlanGateway)) {
throw new InvalidParameterValueException("The IP range with
tag: " + vlan.getVlanTag() + " has already been added with gateway " +
otherVlanGateway
  + ". Please specify a different tag.");
   }
}

According to database, there is 6 VLANs with same gateway :

mysql> select * from vlan where  vlan_gateway = '10.200.244.129';


+-+-++-+---++++--+-+-+--+---+
| id  | vlan_id | vlan_gateway   | vlan_netmask| description
  | vlan_type  | data_center_id | network_id | uuid
 | physical_network_id | ip6_gateway |
ip6_cidr | ip6_range |
+-+-++-+---++++--+-+-+--+---+
| 114 | 2046| 10.200.244.129 | 255.255.255.192 |
10.200.244.187-10.200.244.190 | DirectAttached |  1 |
335 | 9339bbfb-c6e0-43b8-94e1-3b1c0b15d3ed | 200 |
NULL| NULL | NULL  |
| 117 | 2046| 10.200.244.129 | 255.255.255.192 |
10.200.244.187-10.200.244.190 | DirectAttached |  3 |
338 | e39717b8-913b-44ba-85cb-449ad5cd8c9a | 202 |
NULL| NULL | NULL  |
| 141 | 2037| 10.200.244.129 | 255.255.255.192 |
10.200.244.154-10.200.244.158 | DirectAttached |  1 |
365 | 658b4dbd-295e-4083-9ab2-6a73b324c21a | 200 |
NULL| NULL | NULL  |
| 144 | 2037| 10.200.244.129 | 255.255.255.192 |
10.200.244.186-10.200.244.190 | DirectAttached |  3 |
368 | d91846f5-a5c7-40f6-9d59-0a2bc04563c2 | 202 |
NULL| NULL | NULL  |
| 172 | 2013| 10.200.244.129 | 255.255.255.192 |
10.200.244.185-10.200.244.190 | DirectAttached |  1 |
396 | f7bd1314-5376-4fa5-b131-89fc37ea480d | 200 |
NULL| NULL | NULL  |
| 182 | 2013| 10.200.244.129 | 255.255.255.192 |
10.200.244.128-10.200.244.128 | DirectAttached |  1 |
408 | 8c72cad9-2305-4105-8c26-17cc81af82c9 | 200 |
NULL| NULL | NULL  |
+-+-++-+---++++--+-+-+--+---+
6 rows in set (0.00 sec)

But all theses VLANs are associated to 'DESTROY' networks :


mysql> select * from networks where id in (335,338,365,368,396,408);
+-+--+--+--+---+---++---+--+-+-++---+-+-+---++--+--+---+++-++-+-+--+--+---+--++-+--+
| id  | name | display_text | traffic_type |
broadcast_domain_type | broadcast_uri | gateway| cidr
  | mode | network_offering_id | physical_network_id | data_center_id
| guru_name | state   | related | domain_id | account_id | dns1
| dns2 | guru_data | set_fields | guest_type | network_domain  |
reservation_id | created | removed | uuid
 | restart_required | specify_ip_ranges |
acl_type | vpc_id | ip6_gateway | ip6_cidr |
+-+--+--+--+---+---++---+--+-+-++---+-+-+

Build failed in Jenkins: build-master-slowbuild #411

[jenkins]

See 

--
[...truncated 18098 lines...]

Tests run: 4, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi ---
[INFO] Cobertura 2.0.3 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/amazon/ec2/AmazonEC2SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/amazon/s3/AmazonS3SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SAcl.java.  Ensure this class was instrumented, and this 
data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SBucket.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SHost.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/BucketPolicyDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackAccountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackConfigurationDao.java.  Ensure this 
class was instrumented, and this data file contains the instrumentation 
information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackSvcOfferingDao.java.  Ensure this class 
was instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackUserDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostMountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartPartsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartUploadsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultipartMetaDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does 

Re: [MERGE] resize-root branch

[Nux!]

On 11.03.2014 20:17, Marcus wrote:

I'd like to merge the resize-root branch for the requested feature of
being able to resize root volumes. I have pulled from master and
tested.

I should note that this feature is affected by an existing bug in
master that was introduced recently, breaking the existing data disk
resize feature on Ubuntu 12.04 + stock libvirt, but has otherwise been
tested to work with Ubuntu 12.04 + recent libvirt and CentOS 6.4,6.5.
We are discussing how to proceed with that separate issue on-list.

Integration tests were added for deploy in a new file
"test_deploy_vm_root_resize.py" and existing resize tests were
extended to root volumes in the existing test_volumes.py.

Findbugs indicates there are no new issues introduced (220/220), as
reported by running the following on both master and resize-root. This
was just my stab in the dark at trying to make sense of the output in
absence of familiarity with findbugs:

# mvn -P enablefindbugs verify
# find . -name findbugs.xml -exec xmllint --format {} \; | grep -c 
BugInstance


FS: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Root+Resize+Support

JIRA: https://issues.apache.org/jira/browse/CLOUDSTACK-6181


Thanks Marcus,

This works great for me with local storage, CLVM, GlusterFS and NFS.

Regards,
Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

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

[Paul Angus]

Yes, I can build now.

:-)

Regards

Paul Angus
Cloud Architect
S: +44 20 3603 0540 | M: +447711418784 | T: CloudyAngus
paul.an...@shapeblue.com

-Original Message-
From: Damoder Reddy [mailto:damoder.re...@citrix.com]
Sent: 12 March 2014 10:49
To: dev@cloudstack.apache.org; Hugo Trippaers
Cc: Animesh Chaturvedi
Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)

HI Paul,

 After you pull Hugo changes are you able to build now?

Thanks & Regards
Damodar/

-Original Message-
From: Paul Angus [mailto:paul.an...@shapeblue.com]
Sent: Wednesday, March 12, 2014 2:04 PM
To: Hugo Trippaers
Cc: Animesh Chaturvedi; dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round)

Yes that's correct. I'm building noredist


Regards,

Paul Angus
S: +44 20 3603 0540 | M: 
+447711418784
T: @CloudyAngus
paul.an...@shapeblue.com


 Original message 
From: Hugo Trippaers
Date:12/03/2014 07:32 (GMT+00:00)
To: Paul Angus
Cc: Animesh Chaturvedi ,dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round)

Hey Paul,

Just to be clear, this problem only occurs during the noredist build right?

Mysql HA is one of the noredist features, so it should not be present in the 
regular build.

I'm checking the poms now to see if everything is configured correctly.

Cheers,

Hugo

On 12 mrt. 2014, at 08:14, Paul Angus  wrote:

> If I manually fix the white spaces I can get past MySQL HA Strategy, but then 
> I hit:
>
> [INFO]
> --
> -- [INFO] Building Apache CloudStack Client UI 4.3.0 [INFO]
> --
> --
> Downloading:
> http://repo.maven.apache.org/maven2/org/apache/cloudstack/cloud-plugin
> -database-mysqlha/4.3.0/cloud-plugin-database-mysqlha-4.3.0.pom
> [WARNING] The POM for
> org.apache.cloudstack:cloud-plugin-database-mysqlha:jar:4.3.0 is
> missing, no dependency information available
> Downloading:
> http://repo.maven.apache.org/maven2/org/apache/cloudstack/cloud-plugin
> -database-mysqlha/4.3.0/cloud-plugin-database-mysqlha-4.3.0.jar
> [ERROR] Failed to execute goal on project cloud-client-ui: Could not
> resolve dependencies for project
> org.apache.cloudstack:cloud-client-ui:war:4.3.0: Could not find
> artifact org.apache.cloudstack:cloud-plugin-database-mysqlha:jar:4.3.0
> in central (http://repo.maven.apache.org/maven2) -> [Help 1]
>
> MySQL HA Strategy seems to need a bit of work.
>
>
> Regards,
>
> Paul Angus
> Cloud Architect
> S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus
> paul.an...@shapeblue.com
>
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: 11 March 2014 19:31
> To: dev@cloudstack.apache.org
> Cc: Hugo Trippaers; Hugo Trippaers (htrippa...@schubergphilis.com);
> Paul Angus
> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>
>
>
>> -Original Message-
>> From: Paul Angus [mailto:paul.an...@shapeblue.com]
>> Sent: Tuesday, March 11, 2014 10:35 AM
>> To: dev@cloudstack.apache.org
>> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>>
>> Trying to build 4.3,  the process bombs out for me at MySQL HA Strategy.
>> And strangely it seems to be trying to build MySQL from Master
>> (4.4.0- SNAPSHOT)?
> [Animesh] Ok this came in from Hugo's commit that I cherry-picked
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;
> h=472a387d2d828e21aff93a750ed3e178837a1879
>
> from file plugins/database/mysql-ha/pom.xml This is a  version issue which 
> can be fixed but should not affect functioning. Lets hear from Hugo on this.
>
>
> The other errors are formatting issues caught by checkstyle plugin that can 
> be ignored. The Jenkins build is successful.
>
>>
>> Ideas anyone?
>>
>>
>> [INFO] Apache CloudStack Plugin - MySQL HA Strategy .. FAILURE
>> [1.110s] [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-checkstyle-
>> plugin:2.11:check (cloudstack-checkstyle) on project
>> cloud-plugin-database-
>> mysqlha: Failed during checkstyle execution: There are 6 checkstyle
>> errors. -> [Help 1]
>>
>> [INFO]
>> -
>> -
>> -- [INFO] Building Apache CloudStack Plugin - MySQL HA Strategy
>> 4.4.0- SNAPSHOT [INFO]
>> -
>> -
>> --
>> [INFO]
>> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
>> cloud-plugin- database-mysqlha --- [INFO] Deleting
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-ha/target (includes = [**/*], excludes =
>> []) [INFO] Deleting
>> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack-
>> 4.3.0/plugins/database/mysql-ha (includes = [target, dist], excludes
>> =
>> []) [INFO] [INFO] --- maven-checkstyle-plugin:2.11:check
>> (cloudstack-checkstyl

Re: [CS4.1] Error during ip range creation

[Wei ZHOU]

select * from networks where  broadcast_uri ='vlan://2013'


2014-03-12 11:58 GMT+01:00 :

> I've got the same error during creation of a network :
>
> http://pastebin.com/aXryp0jj
>
> Le 11/03/2014 15:13, nicolas.lamira...@orange.com a écrit :
>
>  Hi,
>> Nobody has ideas for what concerns ?
>>
>> Le 10/03/2014 17:32, LAMIRAULT Nicolas MBS a écrit :
>>
>>> Hi,
>>>
>>> I creates a network using API.
>>> Then, I try to creates a new IP Range associated to this network. I've
>>> got an error. This is the output logs in this paste [1]
>>>
>>> Searching into the Cloudstack code, I find that :
>>>
>>> if (vlanId.equals(vlan.getVlanTag()) &&
>>> newVlanSubnet.equals(otherVlanSubnet)) {
>>>if (NetUtils.ipRangesOverlap(startIP, endIP, otherVlanStartIP,
>>> otherVlanEndIP)) {
>>>  throw new InvalidParameterValueException("The IP range with
>>> tag: " + vlan.getVlanTag()
>>>  + " already has IPs that overlap with the new range.
>>> Please specify a different start IP/end IP.");
>>>}
>>>if (!vlanGateway.equals(otherVlanGateway)) {
>>> throw new InvalidParameterValueException("The IP range with
>>> tag: " + vlan.getVlanTag() + " has already been added with gateway " +
>>> otherVlanGateway
>>>   + ". Please specify a different tag.");
>>>}
>>> }
>>>
>>> According to database, there is 6 VLANs with same gateway :
>>>
>>> mysql> select * from vlan where  vlan_gateway = '10.200.244.129';
>>>
>>>
>>> +-+-++-+
>>> ---+++--
>>> --+--+--
>>> ---+-+--+---+
>>> | id  | vlan_id | vlan_gateway   | vlan_netmask| description
>>>   | vlan_type  | data_center_id | network_id | uuid
>>>  | physical_network_id | ip6_gateway |
>>> ip6_cidr | ip6_range |
>>> +-+-++-+
>>> ---+++--
>>> --+--+--
>>> ---+-+--+---+
>>> | 114 | 2046| 10.200.244.129 | 255.255.255.192 |
>>> 10.200.244.187-10.200.244.190 | DirectAttached |  1 |
>>> 335 | 9339bbfb-c6e0-43b8-94e1-3b1c0b15d3ed | 200 |
>>> NULL| NULL | NULL  |
>>> | 117 | 2046| 10.200.244.129 | 255.255.255.192 |
>>> 10.200.244.187-10.200.244.190 | DirectAttached |  3 |
>>> 338 | e39717b8-913b-44ba-85cb-449ad5cd8c9a | 202 |
>>> NULL| NULL | NULL  |
>>> | 141 | 2037| 10.200.244.129 | 255.255.255.192 |
>>> 10.200.244.154-10.200.244.158 | DirectAttached |  1 |
>>> 365 | 658b4dbd-295e-4083-9ab2-6a73b324c21a | 200 |
>>> NULL| NULL | NULL  |
>>> | 144 | 2037| 10.200.244.129 | 255.255.255.192 |
>>> 10.200.244.186-10.200.244.190 | DirectAttached |  3 |
>>> 368 | d91846f5-a5c7-40f6-9d59-0a2bc04563c2 | 202 |
>>> NULL| NULL | NULL  |
>>> | 172 | 2013| 10.200.244.129 | 255.255.255.192 |
>>> 10.200.244.185-10.200.244.190 | DirectAttached |  1 |
>>> 396 | f7bd1314-5376-4fa5-b131-89fc37ea480d | 200 |
>>> NULL| NULL | NULL  |
>>> | 182 | 2013| 10.200.244.129 | 255.255.255.192 |
>>> 10.200.244.128-10.200.244.128 | DirectAttached |  1 |
>>> 408 | 8c72cad9-2305-4105-8c26-17cc81af82c9 | 200 |
>>> NULL| NULL | NULL  |
>>> +-+-++-+
>>> ---+++--
>>> --+--+--
>>> ---+-+--+---+
>>> 6 rows in set (0.00 sec)
>>>
>>> But all theses VLANs are associated to 'DESTROY' networks :
>>>
>>>
>>> mysql> select * from networks where id in (335,338,365,368,396,408);
>>> +-+--+--+--+
>>> ---+---++---
>>> +--+-+--
>>> ---++---+-+-
>>> +---++--+--+---+
>>> ++-+
>>> +-+-+---
>>> ---+--+-
>>> --+--++-+--+
>>> | id  | name | display_text | traffic_type |
>>> broadcast_domain_type | broadcast_uri | gateway| cidr
>>>   | mode | network_offering_id | physical_network_id | data_center_id
>>> | guru_name | state   | related | domain_id | account_id | dns1
>>> | dns2 | guru_da

Re: Review Request 19022: List VM enhancement to support querying with multiple VM IDs

[Koushik Das]

On 11-Mar-2014, at 7:24 PM, Daan Hoogland  wrote:

> You are saying it must be null and not empty?

[Koushik] Yes.


> 
> 
> On Tue, Mar 11, 2014 at 1:41 PM, Koushik Das  wrote:
> 
>>   This is an automatically generated e-mail. To reply, visit:
>> https://reviews.apache.org/r/19022/
>> 
>> On March 11th, 2014, 7:41 a.m. UTC, *daan Hoogland* wrote:
>> 
>>  
>> server/src/com/cloud/api/query/QueryManagerImpl.java
>>  (Diff
>> revision 1)
>> 
>> public class QueryManagerImpl extends ManagerBase implements QueryService {
>> 
>>   731
>> 
>>List ids = null;
>> 
>>  Why not be lenient and consider the id as part of ids?
>> You are being strict on something that isn't hurtful but an empty ids when 
>> no id is given is not checked!
>> 
>> On March 11th, 2014, 8:34 a.m. UTC, *Koushik Das* wrote:
>> 
>> I haven't removed 'id' due to back-compat. As I have mentioned 'id' and 
>> 'ids' are mutually exclusive. Also it is a valid scenario to not pass any of 
>> id or ids.
>> 
>> On March 11th, 2014, 10:56 a.m. UTC, *daan Hoogland* wrote:
>> 
>> ok, I don't see why id and ids should be mutually exclusive, but i don't 
>> mind either. If passing no id at all is a valid scenario then it is allright 
>> to not check but I would still initialize the list and addAll to it. Not an 
>> issue thought!
>> 
>> Thanks for the comment Daan.
>> 
> I would still initialize the list and addAll to it
>> I don't quite follow what do you mean by addAll to the list. The sql query 
>> that gets generated looks like "where id in (1, 2, 3)" if the list is 
>> non-null. If there is no id specified then the list is null and is not 
>> considered while building the query.
>> 
>> 
>> - Koushik
>> 
>> On March 11th, 2014, 6:29 a.m. UTC, Koushik Das wrote:
>>  Review request for cloudstack, daan Hoogland and Min Chen.
>> By Koushik Das.
>> 
>> *Updated March 11, 2014, 6:29 a.m.*
>> *Bugs: * 
>> CLOUDSTACK-6052
>> *Repository: * cloudstack-git
>> Description
>> 
>> Currently list VM can only be called using a single VM ID. So if there is a 
>> need to query a set of VMs using ID then either multiple list VM calls need 
>> to be made or all VMs needs to be fetched and then do a client side 
>> filtering. Both approaches are sub-optimal - the former results in multiple 
>> queries to database and the latter will be an overkill if you need a small 
>> subset from a very large number of VMs.
>> 
>> The proposal is to have an additional parameter to specify a list of VM IDs 
>> for which the data needs to be fetched. Using this the required VMs can be 
>> queried in an efficient manner. With the new parameter the syntax would look 
>> like 
>> http://localhost:8096/api?command=listVirtualMachines&listAll=true&ids=eddac053-9b12-4d2e-acb7-233de2e98112,009966fc-4d7b-4f84-8609-254979ba0134
>> 
>> The new 'ids' parameter will be mutually exclusive with the existing 'id' 
>> parameter.
>> 
>>  Testing
>> 
>> Added integration test, also verified manually.
>> 
>>  Diffs
>> 
>>   - api/src/org/apache/cloudstack/api/command/user/vm/ListVMsCmd.java
>>   (1a564f6)
>>   - server/src/com/cloud/api/query/QueryManagerImpl.java (4200799)
>>   - test/integration/smoke/test_deploy_vm.py (425aeb7)
>> 
>> View Diff 
>> 
> 
> 
> 
> -- 
> Daan

Re: [CS4.1] Error during ip range creation

[nicolas.lamirault]

A lot of networks :

mysql> select * from networks where  broadcast_uri ='vlan://2013' ;
+-+---+---+--+---+---++---+--+-+-++-
--+-+-+---++--+--+---+++-++-+-+--+--+---+--++-+--+
| id  | name  | display_text  | traffic_type | 
broadcast_domain_type | broadcast_uri | gateway| cidr 
   | mode | network_offering_id | physical_network_id | data_center_id 
| guru
_name | state   | related | domain_id | account_id | dns1 | dns2 
| guru_data | set_fields | guest_type | network_domain  | 
reservation_id | created | removed | uuid 
  | restart_required | specify_ip_ranges | 
acl_type | vpc_id | ip6_gateway | ip6_cidr |

+-+---+---+--+---+---++---+--+-+-++-
--+-+-+---++--+--+---+++-++-+-+--+--+---+--++-+--+
| 217 | QUESO_PRP-ADMIN   | QUESO_PRP-ADMIN   | Guest| Vlan 
 | vlan://2013   | 10.200.245.1   | 10.200.245.0/26   | 
Dhcp |   7 | 200 |  1 | Dire
ctNetworkGuru | Destroy | 217 | 6 |  7 | NULL | NULL 
| NULL  |  0 | Shared | admin-prp.cloud.mbs | NULL 
 | 2013-02-15 11:07:50 | 2013-07-30 07:34:13 | 217
 |0 | 1 | Account 
|   NULL | NULL| NULL |
| 258 | NIMBUS_PRP-ADMIN  | NIMBUS_PRP-ADMIN  | Guest| Vlan 
 | vlan://2013   | 10.200.245.1   | 10.200.245.0/27   | 
Dhcp |   7 | 201 |  2 | Dire
ctNetworkGuru | Destroy | 258 | 1 |  1 | NULL | NULL 
| NULL  |  0 | Shared | admin-prp.cloud.mbs | NULL 
 | 2013-09-16 09:17:25 | 2014-03-05 15:11:42 | 628b6cf1-b1dc-45
3c-8336-5844dcc7c85d |0 | 1 | Domain   | 
  NULL | NULL| NULL |
| 260 | NIMBUS_PRP-ADMIN  | NIMBUS_PRP-ADMIN  | Guest| Vlan 
 | vlan://2013   | 10.200.245.1   | 10.200.245.0/27   | 
Dhcp |   7 | 201 |  2 | Dire
ctNetworkGuru | Destroy | 260 | 1 |  1 | NULL | NULL 
| NULL  |  0 | Shared | admin-prp.cloud.mbs | NULL 
 | 2013-09-16 15:56:00 | 2014-03-05 15:11:42 | 20a910a6-fb89-47
d1-8d6d-3e72c8168fd8 |0 | 1 | Domain   | 
  NULL | NULL| NULL |
| 359 | SARGE_ITG-ADMIN   | SARGE_ITG-ADMIN   | Guest| Vlan 
 | vlan://2013   | 10.200.244.65  | 10.200.244.64/26  | 
Dhcp |   7 | 200 |  1 | Dire
ctNetworkGuru | Destroy | 359 | 1 |  1 | NULL | NULL 
| NULL  |  0 | Shared | admin-dev.cloud.mbs | NULL 
 | 2014-01-15 13:19:47 | 2014-03-05 11:26:08 | 3cefddd5-3b7c-4f
72-9da8-a3abc5d2275f |0 | 1 | Domain   | 
  NULL | NULL| NULL |
| 362 | SARGE_ITG-ADMIN   | SARGE_ITG-ADMIN   | Guest| Vlan 
 | vlan://2013   | 10.200.244.65  | 10.200.244.64/26  | 
Dhcp |   7 | 202 |  3 | Dire
ctNetworkGuru | Destroy | 362 | 1 |  1 | NULL | NULL 
| NULL  |  0 | Shared | admin-dev.cloud.mbs | NULL 
 | 2014-01-15 13:19:48 | 2014-03-05 11:26:08 | 9f27e7e7-a00a-40
2f-821b-66154849fea8 |0 | 1 | Domain   | 
  NULL | NULL| NULL |
| 396 | CLOUD_ITG-ADMIN   | CLOUD_ITG-ADMIN   | Guest| Vlan 
 | vlan://2013   | 10.200.244.129 | 10.200.244.128/26 | 
Dhcp |   7 | 200 |  1 | Dire
ctNetworkGuru | Destroy | 396 | 1 |  1 | NULL | NULL 
| NULL  |  0 | Shared | admin-dev.cloud.mbs | NULL 
 | 2014-02-28 15:36:23 | 2014-03-05 11:26:56 | 9655256c-42aa-4a
91-b472-64f67a641f2f |0 | 1 | Domain   | 
  NULL | NULL| NULL |
| 398 | CLOUD_ITG-ADMIN   | CLOUD_ITG-ADMIN   | Guest| Vlan 
 | vlan://2013   | 10.200.246.65  | 10.200.246.64/26  | 
Dhcp | 

Re: [DISCUSS]{BEHAVIORAL-CHANGE]Domain-Account-User Sync Up Among Multiple Regions

[Alex Ough]

Hi Chiradeep,

Can you give me the example of the Singleton service class you mentioned?
I'm not sure if you are asking the name changes or else because those
classes are abstract classes and do not need to be singleton class.

And let me try the refactoring and ask confirmations to you, so I hope I
can get the reply soon.

Thanks
Alex Ough


On Wed, Mar 12, 2014 at 4:13 AM, Daan Hoogland wrote:

> H Alex, I considder Chiradeeps comments quite valid and serious enough
> to anticipate not making friday 14:00 CET. That would mean no merge
> before 4.4. Can you live with that?
>
> On Wed, Mar 12, 2014 at 6:40 AM, Chiradeep Vittal
>  wrote:
> > Hi Alex,
> >
> > If you look at the general design of CloudStack, there are Singleton
> > service interfaces which are then implemented with real classes. This
> > facilitates easy testing by mocking the interface. In your new files
> > (BaseInterface, which by the way is NOT an interface, AccountService,
> > which is NOT a service like other CloudStack services, and so on), this
> > design paradigm is not followed. Therefore it is incongruous to the rest
> > of the code base.
> >
> > Furthermore this has been plopped right in the middle of other core
> > CloudStack code (server/src/com/cloud/region/). If you look at the
> > EventBus logic, it has been written as a plugin, thereby enabling users
> > who do not need it to disable it. This level of configuration is needed
> > and I can't find it.
> >
> > So, to  summarize:
> > 1. Split it into patches. Patch A is the change to the core DAOs, db
> > logic, schema upgrade code, etc.
> > 2. Patch B is the actual sync service written as an optional plugin with
> > the package name space of org.apache.
> >
> > On 3/11/14, 3:09 PM, "Alex Ough"  wrote:
> >
> >>Hi Daan,
> >>
> >>I didn't update the patch after the couple of works because I wanted to
> do
> >>it with others Chiradeep asked if any.
> >>Let me know when you want me to.
> >>
> >>Thanks
> >>Alex Ough
> >>
> >>
> >>On Tue, Mar 11, 2014 at 4:37 PM, Daan Hoogland
> >>wrote:
> >>
> >>> I will call the merge in a moment, but won't do it immediately.
> >>>
> >>> Be there for me when any issues come up. If not I will revert it.
> >>>
> >>> @Chiradeep: did Alex answer your concerns adequately?
> >>>
> >>>
> >>> kind regards,
> >>>
> >>> On Tue, Mar 11, 2014 at 6:43 PM, Alex Ough 
> >>>wrote:
> >>> > I worked on a couple of items, so can you give me the confirmation
> for
> >>> the
> >>> > rest items so that I can wrap this up?
> >>> > I really want to include this into 4.4.
> >>> >
> >>> > Thanks
> >>> > Alex Ough
> >>> >
> >>> >
> >>> > On Mon, Mar 10, 2014 at 3:41 PM, Alex Ough 
> >>> wrote:
> >>> >
> >>> >> Please see my reply/question in blue.
> >>> >>
> >>> >> Thanks
> >>> >> Alex Ough
> >>> >>
> >>> >>
> >>> >> On Mon, Mar 10, 2014 at 1:25 PM, Chiradeep Vittal <
> >>> >> chiradeep.vit...@citrix.com> wrote:
> >>> >>
> >>> >>> I haven¹t looked at it because it is huge. But preliminary scan:
> >>> >>>
> >>> >>> - there are unit tests missing for changes to core CS code
> >>> >>>
> >>> >>  Unit tests for only new classes were added because I
> >>>couldn't
> >>> >> find unit tests of the ones I modified
> >>> >>
> >>> >>
> >>> >>> - uses com.amazonaws.util.json (why?)
> >>> >>>
> >>> >>  They are used to handle the json objects. Let me know if
> you
> >>> >> want me to replace it with another.
> >>> >>
> >>> >> - code format does not follow coding convention ( placement of {},
> >>>camel
> >>> >>> case api_interface )
> >>> >>>
> >>> >>  Done
> >>> >>
> >>> >>
> >>> >>> - package namespace is com.cloud instead of org.apache for new
> files
> >>> >>>
> >>> >>  I didn't know that. So do I need to use 'org.apache'
> package
> >>> for
> >>> >> all new classes?
> >>> >>
> >>> >> - no file-level comments. What does LocalAccountManager do? Why does
> >>>it
> >>> >>> exist? Etc.
> >>> >>>
> >>> >>  Done.
> >>> >>
> >>> >>
> >>> >>> - No interfaces, only abstract classes. No use of @Inject. While
> >>>this
> >>> >>> might be OK, it does make it harder to test and does not follow the
> >>> rest
> >>> >>> of ACS conventions.
> >>> >>>
> >>> >> I don't think there is any interface, but let me know if you
> >>> find
> >>> >> any.
> >>> >> Any recommendation to replace @inject?
> >>> >>
> >>> >>>
> >>> >>> I would urge the submitter to break up the submission.
> >>> >>> A) the changes to CS core, with explanations / comments and tests
> >>> >>> B) the sync service should be an interface with concrete
> >>> implementations
> >>> >>> in its own package
> >>> >>> C) more tests
> >>> >>>
> >>> >> can you give me a little specific what kind of tests you
> need
> >>> >> more?
> >>> >>
> >>> >>
> >>> >>
> >>> >>>  On 3/10/14, 3:37 AM, "Daan Hoogland" 
> >>>wrote:
> >>> >>>
> >>> >>> >Hi everyody,
> >>> >>> >
> >>> >>> >The people at sungard have been making this change for 4.4 and I
> >>>want
> >>> >>> >to merge/apply it this week. 

Re: Developer access to JIRA please

[Daan Hoogland]

On Wed, Mar 12, 2014 at 11:57 AM, Stephen Turner
 wrote:
> kc284


added, the other accounts don't exist in jira. Please create and I
will give you all rights.

-- 
Daan

Review Request 19119: CLOUDSTACK-5887: Resolved issue in test_base_image_updation.py

[Gaurav Aradhye]

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

Review request for cloudstack, Santhosh Edukulla and SrikanteswaraRao Talluri.


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


Repository: cloudstack-git


Description
---

The test case was failing while checking snapshot policies. In case the volume 
is deleted, snapshot policy won't list but if the volumes is not yet deleted, 
in that case snapshot policy list will be empty.
We should be checking both these conditions.


Diffs
-

  test/integration/component/test_base_image_updation.py af968cc 

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


Testing
---

Yes.

Log:
Test deploy an instance with service offerings with IsVolatile set. ... SKIP: 
skip
Test rebooting instances created with isVolatile service offerings ... SKIP: 
skip
Test restoring a vm with different template than the one it was created with 
... SKIP: skip
Create a VM using the Service offering IsVolatile enabled ... ok

--
Ran 4 tests in 1441.368s

OK (SKIP=3)


Thanks,

Gaurav Aradhye

RE: Developer access to JIRA please

[Stephen Turner]

Thanks, Dan, but we all have accounts already. We're talking about 
issues.apache.org, right?

-- 
Stephen Turner


-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] 
Sent: 12 March 2014 13:35
To: dev
Subject: Re: Developer access to JIRA please

On Wed, Mar 12, 2014 at 11:57 AM, Stephen Turner  
wrote:
> kc284


added, the other accounts don't exist in jira. Please create and I will give 
you all rights.

--
Daan

Re: [REGRESSION][4.2]

[Daan Hoogland]

since no reaction came I will create a bug, apply this to master,
4.3-forward and ask Animesh to cherry-pick shortly.

On Thu, Mar 6, 2014 at 10:46 AM, Daan Hoogland
 wrote:
> H,
>
> We found a functionality that we use once in a while no longer is permitted 
> in 4.2.1. It seems in line with the philosophy of cloudstack but is hurting 
> our operation. In 4.1.1 we could add a bridged network with the following 
> network offering:
>
> cno.traffictype = "GUEST"
> cno.guestiptype = "Isolated"
> cno.specifyipranges = True
> cno.specifyvlan = False
>
> cno.serviceproviderlist = [ { "service": "Connectivity", "provider": 
> "NiciraNvp"},
> { "service": "UserData", "provider": 
> "VirtualRouter"},
> { "service": "Dhcp", "provider": "VirtualRouter"} 
> ]
>
> This is no longer allowed. The use case we have for this is to bridge 
> isolated networks using nicira into hardware/baremetal networks. We tried to 
> work around it yesterday by using shared networks but can't because as of now 
> we only support isolated networks on nicira. The cause of the regression is 
> part of commit
> commit bdac0f8ebc6ee9368d52a263156259a747a219a6
> Author: Anthony Xu  2013-07-22 23:16:20
>
> in one zone, Admin should not be allowed to add a Shared Network with a 
> subnet that is already associated with another Vlan.
>
> Which changes mostly the overlap code in 
> server/src/com/cloud/configuration/ConfigurationManagerImpl.java but also 
> some code in NetworkServiceImpl:
> - server/src/com/cloud/network/NetworkServiceImpl.java 
> 
> diff --git a/server/src/com/cloud/network/NetworkServiceImpl.java 
> b/server/src/com/cloud/network/NetworkServiceImpl.java
> index 5ebd702..7e6b581 100755
> --- a/server/src/com/cloud/network/NetworkServiceImpl.java
> +++ b/server/src/com/cloud/network/NetworkServiceImpl.java
> @@ -1248,13 +1248,10 @@
>  }
>  }
> -// Vlan is created in 2 cases - works in Advance zone only:
> +// Vlan is created in 1 cases - works in Advance zone only:
>  // 1) GuestType is Shared
> -// 2) GuestType is Isolated, but SourceNat service is disabled
>  boolean createVlan = (startIP != null && endIP != null && 
> zone.getNetworkType() == NetworkType.Advanced
> -&& ((ntwkOff.getGuestType() == Network.GuestType.Shared)
> -|| (ntwkOff.getGuestType() == GuestType.Isolated &&
> -!areServicesSupportedByNetworkOffering(ntwkOff.getId(), 
> Service.SourceNat;
> +&& (ntwkOff.getGuestType() == Network.GuestType.Shared));
>  if (!createVlan) {
>   // Only support advance shared network in IPv6, which means 
> createVlan is a must
> I made a custom patch for 4.2.1 to maintain daily operation and would like to 
> consider putting this in 4.3 as well. Any alternatives will be considered.
>
> Kind regards,
> Daan



-- 
Daan

Re: Developer access to JIRA please

[Daan Hoogland]

../jira yes (even when not being called Dan)

I looked at
stephen.t
gabora

and

mihaelas

and got no matches found on each search.  kc284 was matched with no
delay. please triple check.

On Wed, Mar 12, 2014 at 2:40 PM, Stephen Turner
 wrote:
> Thanks, Dan, but we all have accounts already. We're talking about 
> issues.apache.org, right?
>
> --
> Stephen Turner
>
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: 12 March 2014 13:35
> To: dev
> Subject: Re: Developer access to JIRA please
>
> On Wed, Mar 12, 2014 at 11:57 AM, Stephen Turner  
> wrote:
>> kc284
>
>
> added, the other accounts don't exist in jira. Please create and I will give 
> you all rights.
>
> --
> Daan



-- 
Daan

karma for editing versions

[Daan Hoogland]

H,

Can I get rights to jira to adjust versions and move versions around
from future to released?

thanks,
-- 
Daan

Re: Review Request 19022: List VM enhancement to support querying with multiple VM IDs

[Daan Hoogland]

On Wed, Mar 12, 2014 at 1:13 PM, Koushik Das  wrote:
> [Koushik] Yes.
>


then ship

-- 
Daan

Build failed in Jenkins: build-master-slowbuild #412

[jenkins]

See 

--
[...truncated 18098 lines...]

Tests run: 4, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi ---
[INFO] Cobertura 2.0.3 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/amazon/ec2/AmazonEC2SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/amazon/s3/AmazonS3SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SAcl.java.  Ensure this class was instrumented, and this 
data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SBucket.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SHost.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/BucketPolicyDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackAccountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackConfigurationDao.java.  Ensure this 
class was instrumented, and this data file contains the instrumentation 
information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackSvcOfferingDao.java.  Ensure this class 
was instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackUserDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostMountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartPartsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartUploadsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultipartMetaDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does 

[4.4] ConsoleProxyListener says there is an error in the connect process

[Nux!]

Hello,

This might be related to changes regarding realhostip. Can anyone shed 
more light on this? At the moment the console proxy service is not 
working at all.


http://fpaste.org/84666/13946337/raw/

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

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

[Saksham Srivastava]

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

(Updated March 12, 2014, 2:23 p.m.)


Review request for cloudstack, Jayapal Reddy and Sateesh Chodapuneedi.


Changes
---

Adding the output of marvin tests.


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


Repository: cloudstack-git


Description
---

Add a new utility method for comparing 2 CIDRs.
The method takes in 2 cidrs, cidrA and cidrB and returns true if cidrA's IP 
range is equal or a subset of cidrB's IP range.


Diffs (updated)
-

  utils/src/com/cloud/utils/net/NetUtils.java 6350986 
  utils/test/com/cloud/utils/net/NetUtilsTest.java 3183826 

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


Testing (updated)
---

Added unit test for the utility.
Tested locally.
Build is successful.
Patch applies cleanly.
No FindBug issues.

Results of marvin test: test_vpc.py
Test list VPC APIs ... ok
Test restart VPC having no networks ... ok
Test restart VPC having networks ... ok
Test delete VPC having no networks ... ok
Test delete VPC having networks ... ok
Test list VPC APIs for different user roles ... ok
Test Restart VPC when there are multiple networks associated ... ok
Test vpc deletion after account deletion ... ok
Test to create vpc and verify VPC state, VR and SourceNatIP ... ok
Test creation of multiple VPCs with non-overlapping CIDRs ... ok
Test deployment of vm in a VPC without network domain ... ok
Test deployment of vm in a VPC with network domain ... ok
Test deployment of vm in a VPC with network domain ... ok
Test vm deploy in network by a user where VPC was created without 
account/domain ID ... ok
Test deployment of vm in a network in a domain admin account where VPC is 
created without account/domain ID ... ok
Test deployment of vm in a network by root admin for user. ... ok
Test deployment of vm in a network by domain admin for user. ... ok
Test creation of network by domain admin for user from different domain ... ok
Test creation of VPC without mandatory parameters ... ok
Test to verify updation of vpc name and display text ... ok

few tests from: test_vpc_network.py
Test create network in VPC ... ok
Test create network in VPC ... SKIP: Netscaler not configured: skipping test
Test create network in VPC mismatched services (Should fail) ... ok
Test create multiple networks with LB service (Should fail) ... ok
Test create network with external LB devices ... ok
Test create network with redundant router capability ... SKIP: skipped - RvR 
didn't support VPC currently
Test create network services not supported by VPC (Should fail) ... ok
Test create network without sourceNAT service in VPC (should fail) ... ok
Test create network with shared network offering ... ok
Test create network with conserve mode ON ... ok
Test create network with conserve mode ON ... ok
Test network gc after shutdown of vms in the network ... ok
Test network rules after starting a VpcVr that was shutdown after network.gc 
... ok
Test Stop all the Vms that are part of the a Network ... ok
Test create network outside cidr range of VPC ... ok
Test create network outside cidr range of VPC ... ok
Test create network inside cidr range of VPC ... ok
Test create network overlapping cidr range of VPC ... ok
Test create network from different account in VPC ... ok
Test update Network that is NOT part of a VPC to a nw offering that has 
services that are provided by VPCVR and vice versa ... ok


Thanks,

Saksham Srivastava

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

[Saksham Srivastava]

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

(Updated March 12, 2014, 2:25 p.m.)


Review request for cloudstack, Jayapal Reddy and Sateesh Chodapuneedi.


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


Repository: cloudstack-git


Description
---

Add a new utility method for comparing 2 CIDRs.
The method takes in 2 cidrs, cidrA and cidrB and returns true if cidrA's IP 
range is equal or a subset of cidrB's IP range.


Diffs
-

  utils/src/com/cloud/utils/net/NetUtils.java 6350986 
  utils/test/com/cloud/utils/net/NetUtilsTest.java 3183826 

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


Testing
---

Added unit test for the utility.
Tested locally.
Build is successful.
Patch applies cleanly.
No FindBug issues.

Results of marvin test: test_vpc.py
Test list VPC APIs ... ok
Test restart VPC having no networks ... ok
Test restart VPC having networks ... ok
Test delete VPC having no networks ... ok
Test delete VPC having networks ... ok
Test list VPC APIs for different user roles ... ok
Test Restart VPC when there are multiple networks associated ... ok
Test vpc deletion after account deletion ... ok
Test to create vpc and verify VPC state, VR and SourceNatIP ... ok
Test creation of multiple VPCs with non-overlapping CIDRs ... ok
Test deployment of vm in a VPC without network domain ... ok
Test deployment of vm in a VPC with network domain ... ok
Test deployment of vm in a VPC with network domain ... ok
Test vm deploy in network by a user where VPC was created without 
account/domain ID ... ok
Test deployment of vm in a network in a domain admin account where VPC is 
created without account/domain ID ... ok
Test deployment of vm in a network by root admin for user. ... ok
Test deployment of vm in a network by domain admin for user. ... ok
Test creation of network by domain admin for user from different domain ... ok
Test creation of VPC without mandatory parameters ... ok
Test to verify updation of vpc name and display text ... ok

few tests from: test_vpc_network.py
Test create network in VPC ... ok
Test create network in VPC ... SKIP: Netscaler not configured: skipping test
Test create network in VPC mismatched services (Should fail) ... ok
Test create multiple networks with LB service (Should fail) ... ok
Test create network with external LB devices ... ok
Test create network with redundant router capability ... SKIP: skipped - RvR 
didn't support VPC currently
Test create network services not supported by VPC (Should fail) ... ok
Test create network without sourceNAT service in VPC (should fail) ... ok
Test create network with shared network offering ... ok
Test create network with conserve mode ON ... ok
Test create network with conserve mode ON ... ok
Test network gc after shutdown of vms in the network ... ok
Test network rules after starting a VpcVr that was shutdown after network.gc 
... ok
Test Stop all the Vms that are part of the a Network ... ok
Test create network outside cidr range of VPC ... ok
Test create network outside cidr range of VPC ... ok
Test create network inside cidr range of VPC ... ok
Test create network overlapping cidr range of VPC ... ok
Test create network from different account in VPC ... ok
Test update Network that is NOT part of a VPC to a nw offering that has 
services that are provided by VPCVR and vice versa ... ok


Thanks,

Saksham Srivastava

Re: karma for editing versions

[David Nalley]

You should have karma to do this. Lets talk on IRC if you are having problems.

On Wed, Mar 12, 2014 at 9:46 AM, Daan Hoogland  wrote:
> H,
>
> Can I get rights to jira to adjust versions and move versions around
> from future to released?
>
> thanks,
> --
> Daan

RE: Developer access to JIRA please

[Stephen Turner]

Oops, sorry for mis-spelling your name, Daan.

https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mihaelas
https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gabora
https://issues.apache.org/jira/secure/ViewProfile.jspa?name=stephen.tur...@citrix.com

all exist.

-- 
Stephen Turner


-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] 
Sent: 12 March 2014 13:45
To: Stephen Turner
Cc: dev@cloudstack.apache.org
Subject: Re: Developer access to JIRA please

../jira yes (even when not being called Dan)

I looked at
stephen.t
gabora

and

mihaelas

and got no matches found on each search.  kc284 was matched with no delay. 
please triple check.

On Wed, Mar 12, 2014 at 2:40 PM, Stephen Turner  
wrote:
> Thanks, Dan, but we all have accounts already. We're talking about 
> issues.apache.org, right?
>
> --
> Stephen Turner
>
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: 12 March 2014 13:35
> To: dev
> Subject: Re: Developer access to JIRA please
>
> On Wed, Mar 12, 2014 at 11:57 AM, Stephen Turner  
> wrote:
>> kc284
>
>
> added, the other accounts don't exist in jira. Please create and I will give 
> you all rights.
>
> --
> Daan



--
Daan

Re: Developer access to JIRA please

[Daan Hoogland]

hm, I have been trying to add you guys to confluence, sorry

On Wed, Mar 12, 2014 at 3:58 PM, Stephen Turner
 wrote:
> Oops, sorry for mis-spelling your name, Daan.
>
> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mihaelas
> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gabora
> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=stephen.tur...@citrix.com
>
> all exist.
>
> --
> Stephen Turner
>
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: 12 March 2014 13:45
> To: Stephen Turner
> Cc: dev@cloudstack.apache.org
> Subject: Re: Developer access to JIRA please
>
> ../jira yes (even when not being called Dan)
>
> I looked at
> stephen.t
> gabora
>
> and
>
> mihaelas
>
> and got no matches found on each search.  kc284 was matched with no delay. 
> please triple check.
>
> On Wed, Mar 12, 2014 at 2:40 PM, Stephen Turner  
> wrote:
>> Thanks, Dan, but we all have accounts already. We're talking about 
>> issues.apache.org, right?
>>
>> --
>> Stephen Turner
>>
>>
>> -Original Message-
>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>> Sent: 12 March 2014 13:35
>> To: dev
>> Subject: Re: Developer access to JIRA please
>>
>> On Wed, Mar 12, 2014 at 11:57 AM, Stephen Turner  
>> wrote:
>>> kc284
>>
>>
>> added, the other accounts don't exist in jira. Please create and I will give 
>> you all rights.
>>
>> --
>> Daan
>
>
>
> --
> Daan



-- 
Daan

Re: Developer access to JIRA please

[Daan Hoogland]

now we are a bit better off.

after retrying stubbornly, you are all in.

cheers,

On Wed, Mar 12, 2014 at 4:03 PM, Daan Hoogland  wrote:
> hm, I have been trying to add you guys to confluence, sorry
>
> On Wed, Mar 12, 2014 at 3:58 PM, Stephen Turner
>  wrote:
>> Oops, sorry for mis-spelling your name, Daan.
>>
>> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mihaelas
>> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gabora
>> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=stephen.tur...@citrix.com
>>
>> all exist.
>>
>> --
>> Stephen Turner
>>
>>
>> -Original Message-
>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>> Sent: 12 March 2014 13:45
>> To: Stephen Turner
>> Cc: dev@cloudstack.apache.org
>> Subject: Re: Developer access to JIRA please
>>
>> ../jira yes (even when not being called Dan)
>>
>> I looked at
>> stephen.t
>> gabora
>>
>> and
>>
>> mihaelas
>>
>> and got no matches found on each search.  kc284 was matched with no delay. 
>> please triple check.
>>
>> On Wed, Mar 12, 2014 at 2:40 PM, Stephen Turner  
>> wrote:
>>> Thanks, Dan, but we all have accounts already. We're talking about 
>>> issues.apache.org, right?
>>>
>>> --
>>> Stephen Turner
>>>
>>>
>>> -Original Message-
>>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>>> Sent: 12 March 2014 13:35
>>> To: dev
>>> Subject: Re: Developer access to JIRA please
>>>
>>> On Wed, Mar 12, 2014 at 11:57 AM, Stephen Turner 
>>>  wrote:
 kc284
>>>
>>>
>>> added, the other accounts don't exist in jira. Please create and I will 
>>> give you all rights.
>>>
>>> --
>>> Daan
>>
>>
>>
>> --
>> Daan
>
>
>
> --
> Daan



-- 
Daan

Re: Review Request 17790: Domain-Account-User Sync Up Among Multiple Regions

[Alex Ough]

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

(Updated March 12, 2014, 3:14 p.m.)


Review request for cloudstack.


Changes
---

This is a patch A that includes changes in core classes.


Repository: cloudstack-git


Description
---

Currently, under the environment of cloudstack with multiple regions, each 
region has its own management server running with a separate database, which 
will cause data discrepancies when users create/update/delete 
domain/account/user data independently in each management server. So to support 
multiple regions and provide one point of entry for each customer, this 
implementation duplicates domain/account/user information of customers in one 
region to all of the regions independently whenever there is any change.

https://issues.apache.org/jira/browse/CLOUDSTACK-4992
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Domain-Account-User+Sync+Up+Among+Multiple+Regions


Diffs (updated)
-

  api/src/com/cloud/domain/Domain.java c4755d7 
  api/src/com/cloud/event/EventTypes.java ec54ea1 
  api/src/com/cloud/user/Account.java 99ef954 
  api/src/com/cloud/user/AccountService.java a9be292 
  api/src/com/cloud/user/User.java 36e9028 
  api/src/com/cloud/user/UserAccount.java c5a0637 
  api/src/org/apache/cloudstack/api/ApiConstants.java 14df653 
  api/src/org/apache/cloudstack/api/BaseCmd.java e869ddf 
  api/src/org/apache/cloudstack/api/response/AccountResponse.java b7d30ca 
  api/src/org/apache/cloudstack/api/response/DomainResponse.java 0c0281e 
  api/src/org/apache/cloudstack/api/response/UserResponse.java 40e1561 
  api/src/org/apache/cloudstack/region/Region.java df64e44 
  
engine/schema/resources/META-INF/cloudstack/core/spring-engine-schema-core-daos-context.xml
 08efb83 
  engine/schema/src/com/cloud/domain/DomainVO.java f6494b3 
  engine/schema/src/com/cloud/user/AccountVO.java fb1b58a 
  engine/schema/src/com/cloud/user/UserAccountVO.java cef9239 
  engine/schema/src/com/cloud/user/UserVO.java 68879f6 
  engine/schema/src/org/apache/cloudstack/region/RegionVO.java 608bd2b 
  framework/db/src/com/cloud/utils/db/Attribute.java 82c2bdb 
  framework/db/src/com/cloud/utils/db/GenericDao.java cb401cd 
  framework/db/src/com/cloud/utils/db/GenericDaoBase.java cecea84 
  framework/db/src/com/cloud/utils/db/SqlGenerator.java befe34b 
  
plugins/network-elements/juniper-contrail/test/org/apache/cloudstack/network/contrail/management/MockAccountManager.java
 fa7be58 
  server/src/com/cloud/api/ApiDispatcher.java 5bdefe7 
  server/src/com/cloud/api/ApiResponseHelper.java 81bfe21 
  server/src/com/cloud/api/query/dao/AccountJoinDaoImpl.java 5e087fd 
  server/src/com/cloud/api/query/dao/UserAccountJoinDaoImpl.java 923a238 
  server/src/com/cloud/api/query/vo/AccountJoinVO.java 8d642ed 
  server/src/com/cloud/api/query/vo/UserAccountJoinVO.java ed29284 
  server/src/com/cloud/event/ActionEventUtils.java 9724d99 
  server/src/com/cloud/projects/ProjectManagerImpl.java 5a0ed1c 
  server/src/com/cloud/server/StatsCollector.java 548587c 
  server/src/com/cloud/user/AccountManager.java 983caf1 
  server/src/com/cloud/user/AccountManagerImpl.java 186cfb2 
  server/src/com/cloud/user/DomainManager.java f72b18a 
  server/src/com/cloud/user/DomainManagerImpl.java b2a478e 
  server/test/com/cloud/user/MockAccountManagerImpl.java 62e7fc8 
  server/test/com/cloud/user/MockDomainManagerImpl.java 7dddefb 
  setup/db/db/schema-430to440.sql acc7e21 

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


Testing
---

1. Successfully tested real time synchronization as soon as resources are 
created/deleted/modified in one region.
2. Successfully tested full scans to synchronize resources that were missed 
during real time synchronization because of any reasons like network connection 
issues.
3. The tests were done manually and also automatically by randomly generating 
changes each region.


Thanks,

Alex Ough

Re: [DISCUSS]{BEHAVIORAL-CHANGE]Domain-Account-User Sync Up Among Multiple Regions

[Alex Ough]

I uploaded the patch A that includes only core changes, so please review it
and let me know if you have any comments.

Thanks
Alex Ough


On Wed, Mar 12, 2014 at 8:24 AM, Alex Ough  wrote:

> Hi Chiradeep,
>
> Can you give me the example of the Singleton service class you mentioned?
> I'm not sure if you are asking the name changes or else because those
> classes are abstract classes and do not need to be singleton class.
>
> And let me try the refactoring and ask confirmations to you, so I hope I
> can get the reply soon.
>
> Thanks
> Alex Ough
>
>
> On Wed, Mar 12, 2014 at 4:13 AM, Daan Hoogland wrote:
>
>> H Alex, I considder Chiradeeps comments quite valid and serious enough
>> to anticipate not making friday 14:00 CET. That would mean no merge
>> before 4.4. Can you live with that?
>>
>> On Wed, Mar 12, 2014 at 6:40 AM, Chiradeep Vittal
>>  wrote:
>> > Hi Alex,
>> >
>> > If you look at the general design of CloudStack, there are Singleton
>> > service interfaces which are then implemented with real classes. This
>> > facilitates easy testing by mocking the interface. In your new files
>> > (BaseInterface, which by the way is NOT an interface, AccountService,
>> > which is NOT a service like other CloudStack services, and so on), this
>> > design paradigm is not followed. Therefore it is incongruous to the rest
>> > of the code base.
>> >
>> > Furthermore this has been plopped right in the middle of other core
>> > CloudStack code (server/src/com/cloud/region/). If you look at the
>> > EventBus logic, it has been written as a plugin, thereby enabling users
>> > who do not need it to disable it. This level of configuration is needed
>> > and I can't find it.
>> >
>> > So, to  summarize:
>> > 1. Split it into patches. Patch A is the change to the core DAOs, db
>> > logic, schema upgrade code, etc.
>> > 2. Patch B is the actual sync service written as an optional plugin with
>> > the package name space of org.apache.
>> >
>> > On 3/11/14, 3:09 PM, "Alex Ough"  wrote:
>> >
>> >>Hi Daan,
>> >>
>> >>I didn't update the patch after the couple of works because I wanted to
>> do
>> >>it with others Chiradeep asked if any.
>> >>Let me know when you want me to.
>> >>
>> >>Thanks
>> >>Alex Ough
>> >>
>> >>
>> >>On Tue, Mar 11, 2014 at 4:37 PM, Daan Hoogland
>> >>wrote:
>> >>
>> >>> I will call the merge in a moment, but won't do it immediately.
>> >>>
>> >>> Be there for me when any issues come up. If not I will revert it.
>> >>>
>> >>> @Chiradeep: did Alex answer your concerns adequately?
>> >>>
>> >>>
>> >>> kind regards,
>> >>>
>> >>> On Tue, Mar 11, 2014 at 6:43 PM, Alex Ough 
>> >>>wrote:
>> >>> > I worked on a couple of items, so can you give me the confirmation
>> for
>> >>> the
>> >>> > rest items so that I can wrap this up?
>> >>> > I really want to include this into 4.4.
>> >>> >
>> >>> > Thanks
>> >>> > Alex Ough
>> >>> >
>> >>> >
>> >>> > On Mon, Mar 10, 2014 at 3:41 PM, Alex Ough 
>> >>> wrote:
>> >>> >
>> >>> >> Please see my reply/question in blue.
>> >>> >>
>> >>> >> Thanks
>> >>> >> Alex Ough
>> >>> >>
>> >>> >>
>> >>> >> On Mon, Mar 10, 2014 at 1:25 PM, Chiradeep Vittal <
>> >>> >> chiradeep.vit...@citrix.com> wrote:
>> >>> >>
>> >>> >>> I haven¹t looked at it because it is huge. But preliminary scan:
>> >>> >>>
>> >>> >>> - there are unit tests missing for changes to core CS code
>> >>> >>>
>> >>> >>  Unit tests for only new classes were added because I
>> >>>couldn't
>> >>> >> find unit tests of the ones I modified
>> >>> >>
>> >>> >>
>> >>> >>> - uses com.amazonaws.util.json (why?)
>> >>> >>>
>> >>> >>  They are used to handle the json objects. Let me know if
>> you
>> >>> >> want me to replace it with another.
>> >>> >>
>> >>> >> - code format does not follow coding convention ( placement of {},
>> >>>camel
>> >>> >>> case api_interface )
>> >>> >>>
>> >>> >>  Done
>> >>> >>
>> >>> >>
>> >>> >>> - package namespace is com.cloud instead of org.apache for new
>> files
>> >>> >>>
>> >>> >>  I didn't know that. So do I need to use 'org.apache'
>> package
>> >>> for
>> >>> >> all new classes?
>> >>> >>
>> >>> >> - no file-level comments. What does LocalAccountManager do? Why
>> does
>> >>>it
>> >>> >>> exist? Etc.
>> >>> >>>
>> >>> >>  Done.
>> >>> >>
>> >>> >>
>> >>> >>> - No interfaces, only abstract classes. No use of @Inject. While
>> >>>this
>> >>> >>> might be OK, it does make it harder to test and does not follow
>> the
>> >>> rest
>> >>> >>> of ACS conventions.
>> >>> >>>
>> >>> >> I don't think there is any interface, but let me know if
>> you
>> >>> find
>> >>> >> any.
>> >>> >> Any recommendation to replace @inject?
>> >>> >>
>> >>> >>>
>> >>> >>> I would urge the submitter to break up the submission.
>> >>> >>> A) the changes to CS core, with explanations / comments and tests
>> >>> >>> B) the sync service should be an interface with concrete
>> >>> implementations
>> >>> >>> in its own package
>> >>> >>> C) more tests
>> >>> >>>

RE: Developer access to JIRA please

[Stephen Turner]

Thank you very much, Daan.

-- 
Stephen Turner


-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] 
Sent: 12 March 2014 15:09
To: Stephen Turner
Cc: dev@cloudstack.apache.org
Subject: Re: Developer access to JIRA please

now we are a bit better off.

after retrying stubbornly, you are all in.

cheers,

On Wed, Mar 12, 2014 at 4:03 PM, Daan Hoogland  wrote:
> hm, I have been trying to add you guys to confluence, sorry
>
> On Wed, Mar 12, 2014 at 3:58 PM, Stephen Turner 
>  wrote:
>> Oops, sorry for mis-spelling your name, Daan.
>>
>> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mihaelas
>> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gabora
>> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=stephen.t
>> ur...@citrix.com
>>
>> all exist.
>>
>> --
>> Stephen Turner
>>
>>
>> -Original Message-
>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>> Sent: 12 March 2014 13:45
>> To: Stephen Turner
>> Cc: dev@cloudstack.apache.org
>> Subject: Re: Developer access to JIRA please
>>
>> ../jira yes (even when not being called Dan)
>>
>> I looked at
>> stephen.t
>> gabora
>>
>> and
>>
>> mihaelas
>>
>> and got no matches found on each search.  kc284 was matched with no delay. 
>> please triple check.
>>
>> On Wed, Mar 12, 2014 at 2:40 PM, Stephen Turner  
>> wrote:
>>> Thanks, Dan, but we all have accounts already. We're talking about 
>>> issues.apache.org, right?
>>>
>>> --
>>> Stephen Turner
>>>
>>>
>>> -Original Message-
>>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>>> Sent: 12 March 2014 13:35
>>> To: dev
>>> Subject: Re: Developer access to JIRA please
>>>
>>> On Wed, Mar 12, 2014 at 11:57 AM, Stephen Turner 
>>>  wrote:
 kc284
>>>
>>>
>>> added, the other accounts don't exist in jira. Please create and I will 
>>> give you all rights.
>>>
>>> --
>>> Daan
>>
>>
>>
>> --
>> Daan
>
>
>
> --
> Daan



--
Daan

RE: Review Request 17889: CLOUDSTACK-4762: Enabling vGPU support for XenServer.

[Stephen Turner]

Does anyone else have a view on this? I'm not familiar with the code base yet, 
so am I worrying about nothing?

-- 
Stephen Turner


-Original Message-
From: Stephen Turner [mailto:stephen.tur...@citrix.com] 
Sent: 11 March 2014 16:13
To: dev@cloudstack.apache.org
Cc: Sanjay Tripathi
Subject: RE: Review Request 17889: CLOUDSTACK-4762: Enabling vGPU support for 
XenServer.

Thanks for your reply, Sanjay. I understand that it's only K1 and K2 cards at 
the moment, but when they add more, do we really want to have to edit the code 
to match? What is the notification process by which we know there are new 
types? Does the user have to upgrade CloudStack to get access to the new types? 
In contrast, if we could use the current list from the server, we don't have to 
worry about it: it will just keep itself up to date.

-- 
Stephen Turner


-Original Message-
From: Sanjay Tripathi 
Sent: 11 March 2014 16:05
To: Stephen Turner; dev@cloudstack.apache.org
Subject: RE: Review Request 17889: CLOUDSTACK-4762: Enabling vGPU support for 
XenServer.

Hi Stephen,

As of now, there are 2 GPU cards available in market i.e. NVIDIA GRID K1 and K2 
cards. These card supports 5 different configurations of vGPUs which we call as 
vGPU types (for details: http://www.nvidia.com/object/virtual-gpus.html).  In 
future, if this list grows, then we'll add a separate table similar to guest_os 
table, which will have the list of supported vGPU types.

Also, the table "vgpu_types" has the entries of different vGPU types supported 
in hosts managed by CloudStack.

--Sanjay

-Original Message-
From: Stephen Turner 
Sent: Tuesday, March 11, 2014 5:54 PM
To: dev@cloudstack.apache.org
Cc: Sanjay Tripathi
Subject: RE: Review Request 17889: CLOUDSTACK-4762: Enabling vGPU support for 
XenServer.

I see that the change has been pushed already, but I'm a bit concerned about 
there being a hard-coded list of vGPU types in the class GPU. I anticipate that 
Nvidia or other vendors will add more vGPU types later, and this will require 
us to keep up with the list. Is there a way we can use the list of vGPU types 
returned from the servers instead?

-- 
Stephen Turner



-Original Message-
From: ASF Subversion and Git Services [mailto:nore...@reviews.apache.org] On 
Behalf Of ASF Subversion and Git Services
Sent: 11 March 2014 10:10
To: Koushik Das; Devdeep Singh; Alex Huang
Cc: Sanjay Tripathi; ASF Subversion and Git Services; cloudstack
Subject: Re: Review Request 17889: CLOUDSTACK-4762: Enabling vGPU support for 
XenServer.


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


Commit c7d31fe288b13ff4f0f046f83f9eb4a9c2bf06c5 in cloudstack's branch 
refs/heads/master from Sanjay Tripathi [ 
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c7d31fe ]

CLOUDSTACK-4760 : Enabling GPU support for XenServer.
CLOUDSTACK-4762 : Enabling VGPU support for XenServer.

This feature is to enable the GPU-passthrough and vGPU functionality, with the 
help of this feature, admins/users will be able to leverage the GPU graphics 
unit power by deploying a virtul machine with GPU or vGPU support or by 
changing the service offering of an existing VM at any later point of time. 
There GPU/vGPU enabled VMs are able to run graphical applications.
For now, this feature is only supported with XenServer hypervisor but can be 
extended to add the support of other hypervisors.


- ASF Subversion and Git Services


On Feb. 27, 2014, 12:35 p.m., Sanjay Tripathi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/17889/
> ---
> 
> (Updated Feb. 27, 2014, 12:35 p.m.)
> 
> 
> Review request for cloudstack, Alex Huang, Devdeep Singh, and Koushik Das.
> 
> 
> Bugs: CLOUDSTACK-4760 and CLOUDSTACK-4762
> https://issues.apache.org/jira/browse/CLOUDSTACK-4760
> https://issues.apache.org/jira/browse/CLOUDSTACK-4762
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-4760 : Enabling GPU support for XenServer.
> CLOUDSTACK-4762 : Enabling VGPU support for XenServer.
> 
> This feature is to enable the GPU-passthrough and vGPU functionality, 
> with the help of this feature, admins/users will be able to leverage 
> the GPU graphics unit power by deploying a virtul machine with GPU or 
> vGPU support or by changing the service offering of an existing VM at 
> any later point of time. There GPU/vGPU enabled VMs are able to run 
> graphical applications.
> For now, this feature is only supported with XenServer hypervisor but 
> can be extended to add the support of other hypervisors.
> 
> 
> Diffs
> -
> 
>   api/src/com/cloud/agent/api/to/GPUDeviceTO.java PRE-CREATION 

RE: Review Request 17889: CLOUDSTACK-4762: Enabling vGPU support for XenServer.

[Erik Weber]

Anything that's hard coded is potentially a problem to change for a user.

You can take a somewhat similar view on the vmware disk controller issue
(cloudstack-4787 iirc) , where it is hard coded what to use, and changing
it to ui based has taken a couple of versions and is still not fixed. Which
is why i would vote against any hard coded value that could and should
either be dynamic or user specified.

Regards,
Erik Weber
12. mars 2014 16:24 skrev "Stephen Turner" 
følgende:

> Does anyone else have a view on this? I'm not familiar with the code base
> yet, so am I worrying about nothing?
>
> --
> Stephen Turner
>
>
> -Original Message-
> From: Stephen Turner [mailto:stephen.tur...@citrix.com]
> Sent: 11 March 2014 16:13
> To: dev@cloudstack.apache.org
> Cc: Sanjay Tripathi
> Subject: RE: Review Request 17889: CLOUDSTACK-4762: Enabling vGPU support
> for XenServer.
>
> Thanks for your reply, Sanjay. I understand that it's only K1 and K2 cards
> at the moment, but when they add more, do we really want to have to edit
> the code to match? What is the notification process by which we know there
> are new types? Does the user have to upgrade CloudStack to get access to
> the new types? In contrast, if we could use the current list from the
> server, we don't have to worry about it: it will just keep itself up to
> date.
>
> --
> Stephen Turner
>
>
> -Original Message-
> From: Sanjay Tripathi
> Sent: 11 March 2014 16:05
> To: Stephen Turner; dev@cloudstack.apache.org
> Subject: RE: Review Request 17889: CLOUDSTACK-4762: Enabling vGPU support
> for XenServer.
>
> Hi Stephen,
>
> As of now, there are 2 GPU cards available in market i.e. NVIDIA GRID K1
> and K2 cards. These card supports 5 different configurations of vGPUs which
> we call as vGPU types (for details:
> http://www.nvidia.com/object/virtual-gpus.html).  In future, if this list
> grows, then we'll add a separate table similar to guest_os table, which
> will have the list of supported vGPU types.
>
> Also, the table "vgpu_types" has the entries of different vGPU types
> supported in hosts managed by CloudStack.
>
> --Sanjay
>
> -Original Message-
> From: Stephen Turner
> Sent: Tuesday, March 11, 2014 5:54 PM
> To: dev@cloudstack.apache.org
> Cc: Sanjay Tripathi
> Subject: RE: Review Request 17889: CLOUDSTACK-4762: Enabling vGPU support
> for XenServer.
>
> I see that the change has been pushed already, but I'm a bit concerned
> about there being a hard-coded list of vGPU types in the class GPU. I
> anticipate that Nvidia or other vendors will add more vGPU types later, and
> this will require us to keep up with the list. Is there a way we can use
> the list of vGPU types returned from the servers instead?
>
> --
> Stephen Turner
>
>
>
> -Original Message-
> From: ASF Subversion and Git Services [mailto:nore...@reviews.apache.org]
> On Behalf Of ASF Subversion and Git Services
> Sent: 11 March 2014 10:10
> To: Koushik Das; Devdeep Singh; Alex Huang
> Cc: Sanjay Tripathi; ASF Subversion and Git Services; cloudstack
> Subject: Re: Review Request 17889: CLOUDSTACK-4762: Enabling vGPU support
> for XenServer.
>
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/17889/#review36769
> ---
>
>
> Commit c7d31fe288b13ff4f0f046f83f9eb4a9c2bf06c5 in cloudstack's branch
> refs/heads/master from Sanjay Tripathi [
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c7d31fe ]
>
> CLOUDSTACK-4760 : Enabling GPU support for XenServer.
> CLOUDSTACK-4762 : Enabling VGPU support for XenServer.
>
> This feature is to enable the GPU-passthrough and vGPU functionality, with
> the help of this feature, admins/users will be able to leverage the GPU
> graphics unit power by deploying a virtul machine with GPU or vGPU support
> or by changing the service offering of an existing VM at any later point of
> time. There GPU/vGPU enabled VMs are able to run graphical applications.
> For now, this feature is only supported with XenServer hypervisor but can
> be extended to add the support of other hypervisors.
>
>
> - ASF Subversion and Git Services
>
>
> On Feb. 27, 2014, 12:35 p.m., Sanjay Tripathi wrote:
> >
> > ---
> > This is an automatically generated e-mail. To reply, visit:
> > https://reviews.apache.org/r/17889/
> > ---
> >
> > (Updated Feb. 27, 2014, 12:35 p.m.)
> >
> >
> > Review request for cloudstack, Alex Huang, Devdeep Singh, and Koushik
> Das.
> >
> >
> > Bugs: CLOUDSTACK-4760 and CLOUDSTACK-4762
> > https://issues.apache.org/jira/browse/CLOUDSTACK-4760
> > https://issues.apache.org/jira/browse/CLOUDSTACK-4762
> >
> >
> > Repository: cloudstack-git
> >
> >
> > Description
> > ---
> >
> > CLOUDSTACK-4760 : Enabling GPU support for XenServer.
> > CLOU

Re: Review Request 17790: Domain-Account-User Sync Up Among Multiple Regions

[Alex Ough]

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

(Updated March 12, 2014, 3:57 p.m.)


Review request for cloudstack.


Changes
---

This is the patch B that includes new implementation for multi region support.


Repository: cloudstack-git


Description
---

Currently, under the environment of cloudstack with multiple regions, each 
region has its own management server running with a separate database, which 
will cause data discrepancies when users create/update/delete 
domain/account/user data independently in each management server. So to support 
multiple regions and provide one point of entry for each customer, this 
implementation duplicates domain/account/user information of customers in one 
region to all of the regions independently whenever there is any change.

https://issues.apache.org/jira/browse/CLOUDSTACK-4992
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Domain-Account-User+Sync+Up+Among+Multiple+Regions


Diffs (updated)
-

  
plugins/event-bus/rabbitmq/src/org/apache/cloudstack/mom/rabbitmq/AccountSubscriber.java
 PRE-CREATION 
  
plugins/event-bus/rabbitmq/src/org/apache/cloudstack/mom/rabbitmq/DomainSubscriber.java
 PRE-CREATION 
  
plugins/event-bus/rabbitmq/src/org/apache/cloudstack/mom/rabbitmq/MultiRegionEventBus.java
 PRE-CREATION 
  
plugins/event-bus/rabbitmq/src/org/apache/cloudstack/mom/rabbitmq/MultiRegionSubscriber.java
 PRE-CREATION 
  
plugins/event-bus/rabbitmq/src/org/apache/cloudstack/mom/rabbitmq/UserSubscriber.java
 PRE-CREATION 
  
plugins/event-bus/rabbitmq/test/org/apache/cloudstack/mom/rabbitmq/AccountSubscriberTest.java
 PRE-CREATION 
  
plugins/event-bus/rabbitmq/test/org/apache/cloudstack/mom/rabbitmq/DomainSubscriberTest.java
 PRE-CREATION 
  
plugins/event-bus/rabbitmq/test/org/apache/cloudstack/mom/rabbitmq/MultiRegionSubscriberTest.java
 PRE-CREATION 
  
plugins/event-bus/rabbitmq/test/org/apache/cloudstack/mom/rabbitmq/UserSubscriberTest.java
 PRE-CREATION 
  server/src/org/apache/cloudstack/region/multi/api/AccountInterface.java 
PRE-CREATION 
  server/src/org/apache/cloudstack/region/multi/api/BaseInterface.java 
PRE-CREATION 
  server/src/org/apache/cloudstack/region/multi/api/DomainInterface.java 
PRE-CREATION 
  server/src/org/apache/cloudstack/region/multi/api/UserInterface.java 
PRE-CREATION 
  
server/src/org/apache/cloudstack/region/multi/service/AccountFullSyncProcessor.java
 PRE-CREATION 
  server/src/org/apache/cloudstack/region/multi/service/AccountService.java 
PRE-CREATION 
  server/src/org/apache/cloudstack/region/multi/service/BaseService.java 
PRE-CREATION 
  
server/src/org/apache/cloudstack/region/multi/service/DomainFullSyncProcessor.java
 PRE-CREATION 
  server/src/org/apache/cloudstack/region/multi/service/DomainService.java 
PRE-CREATION 
  server/src/org/apache/cloudstack/region/multi/service/FullScanner.java 
PRE-CREATION 
  server/src/org/apache/cloudstack/region/multi/service/FullSyncProcessor.java 
PRE-CREATION 
  
server/src/org/apache/cloudstack/region/multi/service/LocalAccountManager.java 
PRE-CREATION 
  server/src/org/apache/cloudstack/region/multi/service/LocalDomainManager.java 
PRE-CREATION 
  server/src/org/apache/cloudstack/region/multi/service/LocalUserManager.java 
PRE-CREATION 
  
server/src/org/apache/cloudstack/region/multi/service/RemoteAccountEventProcessor.java
 PRE-CREATION 
  
server/src/org/apache/cloudstack/region/multi/service/RemoteDomainEventProcessor.java
 PRE-CREATION 
  
server/src/org/apache/cloudstack/region/multi/service/RemoteEventProcessor.java 
PRE-CREATION 
  
server/src/org/apache/cloudstack/region/multi/service/RemoteUserEventProcessor.java
 PRE-CREATION 
  
server/src/org/apache/cloudstack/region/multi/service/UserFullSyncProcessor.java
 PRE-CREATION 
  server/src/org/apache/cloudstack/region/multi/service/UserService.java 
PRE-CREATION 
  
server/src/org/apache/cloudstack/region/multi/simulator/AccountLocalGenerator.java
 PRE-CREATION 
  
server/src/org/apache/cloudstack/region/multi/simulator/AccountLocalGeneratorEvent.java
 PRE-CREATION 
  server/src/org/apache/cloudstack/region/multi/simulator/AutoGenerator.java 
PRE-CREATION 
  
server/src/org/apache/cloudstack/region/multi/simulator/DomainLocalGenerator.java
 PRE-CREATION 
  
server/src/org/apache/cloudstack/region/multi/simulator/DomainLocalGeneratorEvent.java
 PRE-CREATION 
  server/src/org/apache/cloudstack/region/multi/simulator/LocalGenerator.java 
PRE-CREATION 
  
server/src/org/apache/cloudstack/region/multi/simulator/UserLocalGenerator.java 
PRE-CREATION 
  
server/src/org/apache/cloudstack/region/multi/simulator/UserLocalGeneratorEvent.java
 PRE-CREATION 
  server/test/org/apache/cloudstack/region/multi/api/AccountInterfaceTest.java 
PRE-CREATION 
  server/test/org/apache/cloudstack/region/multi/api/BaseInterfaceTest.java 
PRE-CREATION 
 

Re: [DISCUSS]{BEHAVIORAL-CHANGE]Domain-Account-User Sync Up Among Multiple Regions

[Alex Ough]

And I also uploaded the patch B that includes new implementation to support
multi regions.

Thanks
Alex Ough


On Wed, Mar 12, 2014 at 10:17 AM, Alex Ough  wrote:

> I uploaded the patch A that includes only core changes, so please review
> it and let me know if you have any comments.
>
> Thanks
> Alex Ough
>
>
> On Wed, Mar 12, 2014 at 8:24 AM, Alex Ough  wrote:
>
>> Hi Chiradeep,
>>
>> Can you give me the example of the Singleton service class you mentioned?
>> I'm not sure if you are asking the name changes or else because those
>> classes are abstract classes and do not need to be singleton class.
>>
>> And let me try the refactoring and ask confirmations to you, so I hope I
>> can get the reply soon.
>>
>> Thanks
>> Alex Ough
>>
>>
>> On Wed, Mar 12, 2014 at 4:13 AM, Daan Hoogland 
>> wrote:
>>
>>> H Alex, I considder Chiradeeps comments quite valid and serious enough
>>> to anticipate not making friday 14:00 CET. That would mean no merge
>>> before 4.4. Can you live with that?
>>>
>>> On Wed, Mar 12, 2014 at 6:40 AM, Chiradeep Vittal
>>>  wrote:
>>> > Hi Alex,
>>> >
>>> > If you look at the general design of CloudStack, there are Singleton
>>> > service interfaces which are then implemented with real classes. This
>>> > facilitates easy testing by mocking the interface. In your new files
>>> > (BaseInterface, which by the way is NOT an interface, AccountService,
>>> > which is NOT a service like other CloudStack services, and so on), this
>>> > design paradigm is not followed. Therefore it is incongruous to the
>>> rest
>>> > of the code base.
>>> >
>>> > Furthermore this has been plopped right in the middle of other core
>>> > CloudStack code (server/src/com/cloud/region/). If you look at the
>>> > EventBus logic, it has been written as a plugin, thereby enabling users
>>> > who do not need it to disable it. This level of configuration is needed
>>> > and I can't find it.
>>> >
>>> > So, to  summarize:
>>> > 1. Split it into patches. Patch A is the change to the core DAOs, db
>>> > logic, schema upgrade code, etc.
>>> > 2. Patch B is the actual sync service written as an optional plugin
>>> with
>>> > the package name space of org.apache.
>>> >
>>> > On 3/11/14, 3:09 PM, "Alex Ough"  wrote:
>>> >
>>> >>Hi Daan,
>>> >>
>>> >>I didn't update the patch after the couple of works because I wanted
>>> to do
>>> >>it with others Chiradeep asked if any.
>>> >>Let me know when you want me to.
>>> >>
>>> >>Thanks
>>> >>Alex Ough
>>> >>
>>> >>
>>> >>On Tue, Mar 11, 2014 at 4:37 PM, Daan Hoogland
>>> >>wrote:
>>> >>
>>> >>> I will call the merge in a moment, but won't do it immediately.
>>> >>>
>>> >>> Be there for me when any issues come up. If not I will revert it.
>>> >>>
>>> >>> @Chiradeep: did Alex answer your concerns adequately?
>>> >>>
>>> >>>
>>> >>> kind regards,
>>> >>>
>>> >>> On Tue, Mar 11, 2014 at 6:43 PM, Alex Ough 
>>> >>>wrote:
>>> >>> > I worked on a couple of items, so can you give me the confirmation
>>> for
>>> >>> the
>>> >>> > rest items so that I can wrap this up?
>>> >>> > I really want to include this into 4.4.
>>> >>> >
>>> >>> > Thanks
>>> >>> > Alex Ough
>>> >>> >
>>> >>> >
>>> >>> > On Mon, Mar 10, 2014 at 3:41 PM, Alex Ough 
>>> >>> wrote:
>>> >>> >
>>> >>> >> Please see my reply/question in blue.
>>> >>> >>
>>> >>> >> Thanks
>>> >>> >> Alex Ough
>>> >>> >>
>>> >>> >>
>>> >>> >> On Mon, Mar 10, 2014 at 1:25 PM, Chiradeep Vittal <
>>> >>> >> chiradeep.vit...@citrix.com> wrote:
>>> >>> >>
>>> >>> >>> I haven¹t looked at it because it is huge. But preliminary scan:
>>> >>> >>>
>>> >>> >>> - there are unit tests missing for changes to core CS code
>>> >>> >>>
>>> >>> >>  Unit tests for only new classes were added because I
>>> >>>couldn't
>>> >>> >> find unit tests of the ones I modified
>>> >>> >>
>>> >>> >>
>>> >>> >>> - uses com.amazonaws.util.json (why?)
>>> >>> >>>
>>> >>> >>  They are used to handle the json objects. Let me know if
>>> you
>>> >>> >> want me to replace it with another.
>>> >>> >>
>>> >>> >> - code format does not follow coding convention ( placement of {},
>>> >>>camel
>>> >>> >>> case api_interface )
>>> >>> >>>
>>> >>> >>  Done
>>> >>> >>
>>> >>> >>
>>> >>> >>> - package namespace is com.cloud instead of org.apache for new
>>> files
>>> >>> >>>
>>> >>> >>  I didn't know that. So do I need to use 'org.apache'
>>> package
>>> >>> for
>>> >>> >> all new classes?
>>> >>> >>
>>> >>> >> - no file-level comments. What does LocalAccountManager do? Why
>>> does
>>> >>>it
>>> >>> >>> exist? Etc.
>>> >>> >>>
>>> >>> >>  Done.
>>> >>> >>
>>> >>> >>
>>> >>> >>> - No interfaces, only abstract classes. No use of @Inject. While
>>> >>>this
>>> >>> >>> might be OK, it does make it harder to test and does not follow
>>> the
>>> >>> rest
>>> >>> >>> of ACS conventions.
>>> >>> >>>
>>> >>> >> I don't think there is any interface, but let me know if
>>> you
>>> >>> find
>>> >>> >> any.
>>> >>> >> Any recommendation to replac

[4.3] CLOUDSTACK cidr list length

[Daan Hoogland]

Animesh,

This is one of two production issues that we have. I will be sending you the 
other one shortly. I was planning to wait till 4.3.1 but that one is a blocker 
for us.

This one is
454cac448d83b973d8cd337cf214b17e31828b93

Thanks,
Daan

Re: Review Request 19021: Cloudbyte Elastistor storage plug-in

[punith s]

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

(Updated March 12, 2014, 9:39 p.m.)


Review request for cloudstack, edison su and Mike Tutkowski.


Changes
---

modified cloudbyte storage plugin after first review on 11-12/3/2014


Repository: cloudstack-git


Description
---

This patch implements a basic storage plug-in for cloudbyte elastistor v1.3.0, 
The plug-in is a new feature for cloudstack 4.4 and above.

this does not implement managed storage yet, it is been integrated only with 
CreateStoragePool and DeleteStoragePool api's.

the desired behavior of the plugin are:

* Allow an Admin to create a primary storage at cluster level, hence creates a 
volume in elastistor and gets attached to the host with the given capacityiops 
and capacitybytes through CreateStoragePool api with provider being elastistor.

*Allow an admin to delete a primary storage at cluster level, hence it deletes 
the volume from host in cloudstack and deletes the respective volume in 
elastistor.

* volume and datadisks fuctions performs the default storage fuctions, ie. the 
driver extends the CloudStackPrimaryDataStoreDriverImpl.

* support for both nfs and icsci primary storage.


Diffs (updated)
-

  plugins/storage/volume/cloudbyte/pom.xml PRE-CREATION 
  
plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/spring-storage-volume-cloudbyte-context.xml
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/BaseCommand.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/ElastiCenterClient.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/ElastiCenterCommand.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/AddQosGroupCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/CreateTsmCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/CreateVolumeCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/DeleteTsmCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/DeleteVolumeCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/ListCapabilitiesCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/ListTsmCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/QueryAsyncJobResultCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/driver/ElastistorPrimaryDataStoreDriver.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/Async.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/Capabilities.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/FileSystem.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/FileSystemWrapper.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/FilesystemQoSWrapper.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/JobId.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/QoSGroup.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/QoSGroupWrapper.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/StorageVolume.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/StorageVolumeWrapper.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/StorageVolumes.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/Tsm.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/TsmWrapper.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/Tsms.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/VolumeProperties.ja

Re: Review Request 19021: Cloudbyte Elastistor storage plug-in

[punith s]

> On March 12, 2014, 9:39 a.m., Mike Tutkowski wrote:
> > plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java,
> >  line 345
> > 
> >
> > Perhaps I don't understand, but isn't this storage provider servicing a 
> > cluster...not an entire zone?
> > 
> > If it's only servicing a cluster, I'm not sure why we're getting the 
> > hosts for the entire zone?
> > 
> > Maybe you want to use a HostListener instead to create an association 
> > between hosts in a cluster and this storage?

yes, i have worked on cluster scope , but i have implemented the same logic of 
default storage in attachZone, so it will work as usual with respect to default 
storage plugin.

i have no implementation at attachZone apart for default one.

yes, i'm using HostListner to create an association between hosts in a cluster 
and elastistor storage volume.


- punith


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


On March 12, 2014, 9:39 p.m., punith s wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19021/
> ---
> 
> (Updated March 12, 2014, 9:39 p.m.)
> 
> 
> Review request for cloudstack, edison su and Mike Tutkowski.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> This patch implements a basic storage plug-in for cloudbyte elastistor 
> v1.3.0, The plug-in is a new feature for cloudstack 4.4 and above.
> 
> this does not implement managed storage yet, it is been integrated only with 
> CreateStoragePool and DeleteStoragePool api's.
> 
> the desired behavior of the plugin are:
> 
> * Allow an Admin to create a primary storage at cluster level, hence creates 
> a volume in elastistor and gets attached to the host with the given 
> capacityiops and capacitybytes through CreateStoragePool api with provider 
> being elastistor.
> 
> *Allow an admin to delete a primary storage at cluster level, hence it 
> deletes the volume from host in cloudstack and deletes the respective volume 
> in elastistor.
> 
> * volume and datadisks fuctions performs the default storage fuctions, ie. 
> the driver extends the CloudStackPrimaryDataStoreDriverImpl.
> 
> * support for both nfs and icsci primary storage.
> 
> 
> Diffs
> -
> 
>   plugins/storage/volume/cloudbyte/pom.xml PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/spring-storage-volume-cloudbyte-context.xml
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/BaseCommand.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/ElastiCenterClient.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/ElastiCenterCommand.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/AddQosGroupCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/CreateTsmCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/CreateVolumeCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/DeleteTsmCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/DeleteVolumeCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/ListCapabilitiesCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/ListTsmCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/QueryAsyncJobResultCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/driver/ElastistorPrimaryDataStoreDriver.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/Async.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/Capabilities.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/FileSystem.java
>  PRE-CREATION 
>   
> plugins/sto

Re: Review Request 19021: Cloudbyte Elastistor storage plug-in

[punith s]

> On March 12, 2014, 7:18 a.m., Mike Tutkowski wrote:
> > plugins/storage/volume/cloudbyte/pom.xml, line 1
> > 
> >
> > Looks like the license section is having some trouble with end-line 
> > chars

yea, checkstyle is not working on xml files in my workspace so. thanks.


> On March 12, 2014, 7:18 a.m., Mike Tutkowski wrote:
> > plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/driver/ElastistorPrimaryDataStoreDriver.java,
> >  line 65
> > 
> >
> > It's OK to override this method, but if you're just going to call the 
> > base implementation, it would be faster to not override this method.

yea , thanks for optimization , it'll do better now.


> On March 12, 2014, 7:18 a.m., Mike Tutkowski wrote:
> > plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/BaseCommand.java,
> >  line 1
> > 
> >
> > Generally vendor-specific classes are not placed in generic CloudStack 
> > packages.
> > 
> > Could you give me a little background regarding what an ElastiCenter 
> > command is?
> > 
> > Are these commands sent from your storage plug-in to your SAN?
> > 
> > Please place all CloudByte classes/interfaces in CloudByte packages.
> > 
> > Feel free to reference the SolidFire plug-in as an example.

yea i consider that, so now i have put all my elastistor rest client ,commands 
and response java files in my util with reference to solidfire.

Elasticenter command is an interface which is being implemented by all the rest 
commands where the plugin is issuing to elasticenter(management part of 
elastistor).

YES, all these commands which are put into my until now are being called to my 
SAN(elasticenter) through storage plugin only.

yes now all of the Cloudbyte classes/interfaces are now placed into util class.

thanks mike.


- punith


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


On March 12, 2014, 9:39 p.m., punith s wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19021/
> ---
> 
> (Updated March 12, 2014, 9:39 p.m.)
> 
> 
> Review request for cloudstack, edison su and Mike Tutkowski.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> This patch implements a basic storage plug-in for cloudbyte elastistor 
> v1.3.0, The plug-in is a new feature for cloudstack 4.4 and above.
> 
> this does not implement managed storage yet, it is been integrated only with 
> CreateStoragePool and DeleteStoragePool api's.
> 
> the desired behavior of the plugin are:
> 
> * Allow an Admin to create a primary storage at cluster level, hence creates 
> a volume in elastistor and gets attached to the host with the given 
> capacityiops and capacitybytes through CreateStoragePool api with provider 
> being elastistor.
> 
> *Allow an admin to delete a primary storage at cluster level, hence it 
> deletes the volume from host in cloudstack and deletes the respective volume 
> in elastistor.
> 
> * volume and datadisks fuctions performs the default storage fuctions, ie. 
> the driver extends the CloudStackPrimaryDataStoreDriverImpl.
> 
> * support for both nfs and icsci primary storage.
> 
> 
> Diffs
> -
> 
>   plugins/storage/volume/cloudbyte/pom.xml PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/spring-storage-volume-cloudbyte-context.xml
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/BaseCommand.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/ElastiCenterClient.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/ElastiCenterCommand.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/AddQosGroupCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/CreateTsmCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/CreateVolumeCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/DeleteTsmCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/DeleteVolumeCmd.java
>  PRE-CREATION 
>   
> plugins/storage

Build failed in Jenkins: build-master #452

[jenkins]

See 

Changes:

[Daan Hoogland] [CLOUDSTACK-6232] bridging allowed in isolated networks

--
[...truncated 1189 lines...]
[INFO] Compiling 643 source files to 

[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-engine-schema ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
cloud-engine-schema ---
[INFO] Compiling 2 source files to 

[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ cloud-engine-schema 
---
[INFO] Surefire report directory: 


---
 T E S T S
---
Running com.cloud.upgrade.dao.DatabaseAccessObjectTest
Tests run: 25, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.77 sec
Running com.cloud.upgrade.dao.DbUpgradeUtilsTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.215 sec

Results :

Tests run: 33, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Framework - Event Notification 4.4.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
cloud-framework-events ---
[INFO] Deleting 
 
(includes = [**/*], excludes = [])
[INFO] Deleting 
 (includes 
= [target, dist], excludes = [])
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-framework-events ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-framework-events ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-framework-events ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
cloud-framework-events ---
[INFO] Compiling 5 source files to 

[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-framework-events ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
cloud-framework-events ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ 
cloud-framework-events ---
[INFO] Surefire report directory: 


---
 T E S T S
---

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Cloud Engine Internal Components API 
4.4.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
cloud-engine-components-api ---
[INFO] Deleting 

 (includes = [**/*], excludes = [])
[INFO] Deleting 
 
(includes = [target, dist], excludes = [])
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-engine-components-api ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-engine-components-api ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (defau

Re: Review Request 19021: Cloudbyte Elastistor storage plug-in

[Mike Tutkowski]

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



plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorUtil.java


I like how you removed the standalone files for each command and integrated 
the commands into this one file.

Quick question: It looks like your testing includes creating and deleting a 
storage pool, which would lead to the creation and deletion of a SAN volume. 
Have you had a chance to create a root disk and/or a data disk on such a 
storage pool and then delete it?


- Mike Tutkowski


On March 12, 2014, 4:09 p.m., punith s wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19021/
> ---
> 
> (Updated March 12, 2014, 4:09 p.m.)
> 
> 
> Review request for cloudstack, edison su and Mike Tutkowski.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> This patch implements a basic storage plug-in for cloudbyte elastistor 
> v1.3.0, The plug-in is a new feature for cloudstack 4.4 and above.
> 
> this does not implement managed storage yet, it is been integrated only with 
> CreateStoragePool and DeleteStoragePool api's.
> 
> the desired behavior of the plugin are:
> 
> * Allow an Admin to create a primary storage at cluster level, hence creates 
> a volume in elastistor and gets attached to the host with the given 
> capacityiops and capacitybytes through CreateStoragePool api with provider 
> being elastistor.
> 
> *Allow an admin to delete a primary storage at cluster level, hence it 
> deletes the volume from host in cloudstack and deletes the respective volume 
> in elastistor.
> 
> * volume and datadisks fuctions performs the default storage fuctions, ie. 
> the driver extends the CloudStackPrimaryDataStoreDriverImpl.
> 
> * support for both nfs and icsci primary storage.
> 
> 
> Diffs
> -
> 
>   plugins/storage/volume/cloudbyte/pom.xml PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/spring-storage-volume-cloudbyte-context.xml
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/BaseCommand.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/ElastiCenterClient.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/ElastiCenterCommand.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/AddQosGroupCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/CreateTsmCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/CreateVolumeCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/DeleteTsmCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/DeleteVolumeCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/ListCapabilitiesCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/ListTsmCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/QueryAsyncJobResultCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/driver/ElastistorPrimaryDataStoreDriver.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/Async.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/Capabilities.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/FileSystem.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/FileSystemWrapper.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/FilesystemQoSWrapper.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/JobId.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/QoSGrou

Build failed in Jenkins: build-master-slowbuild #413

[jenkins]

See 

Changes:

[Daan Hoogland] CLOUDSTACK-6231 allow for cidr list entry of more than 256 chars

--
[...truncated 18098 lines...]

Tests run: 4, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi ---
[INFO] Cobertura 2.0.3 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/amazon/ec2/AmazonEC2SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/amazon/s3/AmazonS3SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SAcl.java.  Ensure this class was instrumented, and this 
data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SBucket.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SHost.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/BucketPolicyDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackAccountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackConfigurationDao.java.  Ensure this 
class was instrumented, and this data file contains the instrumentation 
information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackSvcOfferingDao.java.  Ensure this class 
was instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackUserDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostMountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartPartsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartUploadsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultipartMetaDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation informati

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

[Wilder Rodrigues]

Hi guys and gals,

Based on the findings after my first round of tests, I give a +1 to the 4.3 RC

Please, find below what I have tested so far:

* Environment
  - Management Server: Debian 7 VM under VirtualBox
  - DevCloud: XenServer 6.2
  - MySQL: running on the DevCloud
  - System VM: Latest from 
http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/

* Initial start-up
  - Everything seems to work fine

* Zone
  - DNS1: 8.8.8.8
  - DNS2: 8.8.4.4
  - Hypervisor: XenServer
  - Guest CIDR: 10.1.2.0/24
  - Local Storage enabled: true
  
* Public Traffic
  - 10.1.1.1 / 255.255.255.0 / 10.1.1.2 / 10.1.1.100
  
* POD
  - 10.1.1.1 / 255.255.255.0 / 10.1.1.101 / 10.1.1.200
  
* VLAN
  - 101 - 109
  
* Host
  - Host Name: 178.237.34.120
  - Username: root
  - Password: blah
  
* Secondary Storage
  - Provider: NFS
  - Name: sec01
  - Server: 10.1.1.114
  - Path: /opt/storage/secondary
  
::: ALL GREEN UP TO NOW :::

* Create Instance
  - Featured: Tiny Linux
  - Compute Offering: Tiny Offering
  - Disk Offering: None
  - Instance name: cs43-01
  
* NIC Information
  - IP Address: 10.1.2.186
  - Gateway: 10.1.2.1
  - Netmask: 255.255.255.0
  
* Create Network
  - Name: devcloud-net01
  - Type: Isolated
  - CIDR: 10.1.2.0/24
  - Public IP: 10.1.1.4 [Source NAT]
  - Egress Rules: 0.0.0.0/0 - All
  - Network Offering: Offering for Isolated networks with Source Nat service 
enabled
  
* Create ACLs
  - 10.1.0.0/16 - TCP - 22 - 22
  - 10.1.0.0/16 - TCP - 443 - 443
  
* Create Port Forwarding
  - 22:22 - 22:22 - instance cs43-01 [10.1.2.186]
  - 443:443 - 443:443 - instance cs43-01 [10.1.2.186]
  
* SSH into the new instance via the Public IP:

[root@devcloud-wil01 ~]# ssh root@10.1.1.4
The authenticity of host '10.1.1.4 (10.1.1.4)' can't be established.
RSA key fingerprint is 02:43:6c:24:c5:79:b6:e2:c8:b7:e8:3c:8d:13:37:91.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.1.1.4' (RSA) to the list of known hosts.
root@10.1.1.4's password: 
% 
% 
% ls
ssh-host-dss-key.pub  ssh-host-rsa-key.pub
% cd /
% ls
bin bootdev etc homelib 
lost+found  mnt procrootsbinsys tmp 
usr var
%

With kind regards,
Wilder

-Original Message-
From: Paul Angus [mailto:paul.an...@shapeblue.com] 
Sent: Wednesday, March 12, 2014 12:45 PM
To: dev@cloudstack.apache.org; Hugo Trippaers
Cc: Animesh Chaturvedi
Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)

Yes, I can build now.

:-)

Regards

Paul Angus
Cloud Architect
S: +44 20 3603 0540 | M: +447711418784 | T: CloudyAngus paul.an...@shapeblue.com

-Original Message-
From: Damoder Reddy [mailto:damoder.re...@citrix.com]
Sent: 12 March 2014 10:49
To: dev@cloudstack.apache.org; Hugo Trippaers
Cc: Animesh Chaturvedi
Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)

HI Paul,

 After you pull Hugo changes are you able to build now?

Thanks & Regards
Damodar/

-Original Message-
From: Paul Angus [mailto:paul.an...@shapeblue.com]
Sent: Wednesday, March 12, 2014 2:04 PM
To: Hugo Trippaers
Cc: Animesh Chaturvedi; dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round)

Yes that's correct. I'm building noredist


Regards,

Paul Angus
S: +44 20 3603 0540 | M: 
+447711418784
T: @CloudyAngus
paul.an...@shapeblue.com


 Original message 
From: Hugo Trippaers
Date:12/03/2014 07:32 (GMT+00:00)
To: Paul Angus
Cc: Animesh Chaturvedi ,dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round)

Hey Paul,

Just to be clear, this problem only occurs during the noredist build right?

Mysql HA is one of the noredist features, so it should not be present in the 
regular build.

I'm checking the poms now to see if everything is configured correctly.

Cheers,

Hugo

On 12 mrt. 2014, at 08:14, Paul Angus  wrote:

> If I manually fix the white spaces I can get past MySQL HA Strategy, but then 
> I hit:
>
> [INFO]
> --
> -- [INFO] Building Apache CloudStack Client UI 4.3.0 [INFO]
> --
> --
> Downloading:
> http://repo.maven.apache.org/maven2/org/apache/cloudstack/cloud-plugin
> -database-mysqlha/4.3.0/cloud-plugin-database-mysqlha-4.3.0.pom
> [WARNING] The POM for
> org.apache.cloudstack:cloud-plugin-database-mysqlha:jar:4.3.0 is 
> missing, no dependency information available
> Downloading:
> http://repo.maven.apache.org/maven2/org/apache/cloudstack/cloud-plugin
> -database-mysqlha/4.3.0/cloud-plugin-database-mysqlha-4.3.0.jar
> [ERROR] Failed to execute goal on project cloud-client-ui: Could not 
> resolve dependencies for project
> org.apache.cloudstack:cloud-client-ui:war:4.3.0: Could not find 
> artifact org.apache.cloudstack:cloud-plugin-database-mysqlha:jar:4.3.0
> in central (

Jenkins build is back to normal : build-master #453

[jenkins]

See 

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

[Mike Tutkowski]

I hate to point this out as I know we've been struggling to get 4.3 out the
door, but this week is probably not a great week to count votes for 4.3 as
it is the last week before 4.4 Feature Freeze.


On Wed, Mar 12, 2014 at 11:09 AM, Wilder Rodrigues <
wrodrig...@schubergphilis.com> wrote:

> Hi guys and gals,
>
> Based on the findings after my first round of tests, I give a +1 to the
> 4.3 RC
>
> Please, find below what I have tested so far:
>
> * Environment
>   - Management Server: Debian 7 VM under VirtualBox
>   - DevCloud: XenServer 6.2
>   - MySQL: running on the DevCloud
>   - System VM: Latest from
> http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/
>
> * Initial start-up
>   - Everything seems to work fine
>
> * Zone
>   - DNS1: 8.8.8.8
>   - DNS2: 8.8.4.4
>   - Hypervisor: XenServer
>   - Guest CIDR: 10.1.2.0/24
>   - Local Storage enabled: true
>
> * Public Traffic
>   - 10.1.1.1 / 255.255.255.0 / 10.1.1.2 / 10.1.1.100
>
> * POD
>   - 10.1.1.1 / 255.255.255.0 / 10.1.1.101 / 10.1.1.200
>
> * VLAN
>   - 101 - 109
>
> * Host
>   - Host Name: 178.237.34.120
>   - Username: root
>   - Password: blah
>
> * Secondary Storage
>   - Provider: NFS
>   - Name: sec01
>   - Server: 10.1.1.114
>   - Path: /opt/storage/secondary
>
> ::: ALL GREEN UP TO NOW :::
>
> * Create Instance
>   - Featured: Tiny Linux
>   - Compute Offering: Tiny Offering
>   - Disk Offering: None
>   - Instance name: cs43-01
>
> * NIC Information
>   - IP Address: 10.1.2.186
>   - Gateway: 10.1.2.1
>   - Netmask: 255.255.255.0
>
> * Create Network
>   - Name: devcloud-net01
>   - Type: Isolated
>   - CIDR: 10.1.2.0/24
>   - Public IP: 10.1.1.4 [Source NAT]
>   - Egress Rules: 0.0.0.0/0 - All
>   - Network Offering: Offering for Isolated networks with Source Nat
> service enabled
>
> * Create ACLs
>   - 10.1.0.0/16 - TCP - 22 - 22
>   - 10.1.0.0/16 - TCP - 443 - 443
>
> * Create Port Forwarding
>   - 22:22 - 22:22 - instance cs43-01 [10.1.2.186]
>   - 443:443 - 443:443 - instance cs43-01 [10.1.2.186]
>
> * SSH into the new instance via the Public IP:
>
> [root@devcloud-wil01 ~]# ssh root@10.1.1.4
> The authenticity of host '10.1.1.4 (10.1.1.4)' can't be established.
> RSA key fingerprint is 02:43:6c:24:c5:79:b6:e2:c8:b7:e8:3c:8d:13:37:91.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added '10.1.1.4' (RSA) to the list of known hosts.
> root@10.1.1.4's password:
> %
> %
> % ls
> ssh-host-dss-key.pub  ssh-host-rsa-key.pub
> % cd /
> % ls
> bin bootdev etc homelib
> lost+found  mnt procrootsbinsys tmp
> usr var
> %
>
> With kind regards,
> Wilder
>
> -Original Message-
> From: Paul Angus [mailto:paul.an...@shapeblue.com]
> Sent: Wednesday, March 12, 2014 12:45 PM
> To: dev@cloudstack.apache.org; Hugo Trippaers
> Cc: Animesh Chaturvedi
> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>
> Yes, I can build now.
>
> :-)
>
> Regards
>
> Paul Angus
> Cloud Architect
> S: +44 20 3603 0540 | M: +447711418784 | T: CloudyAngus
> paul.an...@shapeblue.com
>
> -Original Message-
> From: Damoder Reddy [mailto:damoder.re...@citrix.com]
> Sent: 12 March 2014 10:49
> To: dev@cloudstack.apache.org; Hugo Trippaers
> Cc: Animesh Chaturvedi
> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>
> HI Paul,
>
>  After you pull Hugo changes are you able to build now?
>
> Thanks & Regards
> Damodar/
>
> -Original Message-
> From: Paul Angus [mailto:paul.an...@shapeblue.com]
> Sent: Wednesday, March 12, 2014 2:04 PM
> To: Hugo Trippaers
> Cc: Animesh Chaturvedi; dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>
> Yes that's correct. I'm building noredist
>
>
> Regards,
>
> Paul Angus
> S: +44 20 3603 0540 | M: +447711418784 +447711418784>
> T: @CloudyAngus
> paul.an...@shapeblue.com
>
>
>  Original message 
> From: Hugo Trippaers
> Date:12/03/2014 07:32 (GMT+00:00)
> To: Paul Angus
> Cc: Animesh Chaturvedi ,dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>
> Hey Paul,
>
> Just to be clear, this problem only occurs during the noredist build right?
>
> Mysql HA is one of the noredist features, so it should not be present in
> the regular build.
>
> I'm checking the poms now to see if everything is configured correctly.
>
> Cheers,
>
> Hugo
>
> On 12 mrt. 2014, at 08:14, Paul Angus  wrote:
>
> > If I manually fix the white spaces I can get past MySQL HA Strategy, but
> then I hit:
> >
> > [INFO]
> > --
> > -- [INFO] Building Apache CloudStack Client UI 4.3.0 [INFO]
> > --
> > --
> > Downloading:
> > http://repo.maven.apache.org/maven2/org/apache/cloudstack/cloud-plugin
> > -database-mysqlha/4.3.0/cloud-plugin-da

[REVIEW] OpenStack Swift as Object Storage Service

[Will Stevens]

Hello Everyone,
I would like your opinion on the work I have done to integrate OpenStack
Swift into CloudStack as an Object Storage Service available to the end
users.

*Functional Spec:*
https://cwiki.apache.org/confluence/display/CLOUDSTACK/OpenStack+Swift+as+Object+Storage+Service

*Jira Ticket:* https://issues.apache.org/jira/browse/CLOUDSTACK-6230

I have included a patch off master as of noon 2014/03/12 (today) so you can
see the changes I have made to the code (I would recommend viewing the
patch in an editor).

I have not created an actual Review Request yet because I am not sure which
version of CloudStack is reasonable to target adding this change.  I think
4.4 is probably too tight.

There is one global variable I want to add before this gets committed as
well.  The global variable would allow this functionality to be disabled in
the UI (that may be the default actually, since it requires a Swift install
to function).

Let me know if you have questions and I will do my best to answer them and
clarify the FS.

Cheers,

Will

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

[Animesh Chaturvedi]

Well we chose to keep the feature freeze while we had 4.3 still in progress. I 
don't think we want to hold off 4.3 because of 4.4. It needs to go out

Animesh

From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Wednesday, March 12, 2014 10:25 AM
To: dev@cloudstack.apache.org
Cc: Hugo Trippaers; Animesh Chaturvedi
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round)

I hate to point this out as I know we've been struggling to get 4.3 out the 
door, but this week is probably not a great week to count votes for 4.3 as it 
is the last week before 4.4 Feature Freeze.

On Wed, Mar 12, 2014 at 11:09 AM, Wilder Rodrigues 
mailto:wrodrig...@schubergphilis.com>> wrote:
Hi guys and gals,

Based on the findings after my first round of tests, I give a +1 to the 4.3 RC

Please, find below what I have tested so far:

* Environment
  - Management Server: Debian 7 VM under VirtualBox
  - DevCloud: XenServer 6.2
  - MySQL: running on the DevCloud
  - System VM: Latest from 
http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/

* Initial start-up
  - Everything seems to work fine

* Zone
  - DNS1: 8.8.8.8
  - DNS2: 8.8.4.4
  - Hypervisor: XenServer
  - Guest CIDR: 10.1.2.0/24
  - Local Storage enabled: true

* Public Traffic
  - 10.1.1.1 / 255.255.255.0 / 10.1.1.2 / 10.1.1.100

* POD
  - 10.1.1.1 / 255.255.255.0 / 10.1.1.101 / 10.1.1.200

* VLAN
  - 101 - 109

* Host
  - Host Name: 178.237.34.120
  - Username: root
  - Password: blah

* Secondary Storage
  - Provider: NFS
  - Name: sec01
  - Server: 10.1.1.114
  - Path: /opt/storage/secondary

::: ALL GREEN UP TO NOW :::

* Create Instance
  - Featured: Tiny Linux
  - Compute Offering: Tiny Offering
  - Disk Offering: None
  - Instance name: cs43-01

* NIC Information
  - IP Address: 10.1.2.186
  - Gateway: 10.1.2.1
  - Netmask: 255.255.255.0

* Create Network
  - Name: devcloud-net01
  - Type: Isolated
  - CIDR: 10.1.2.0/24
  - Public IP: 10.1.1.4 [Source NAT]
  - Egress Rules: 0.0.0.0/0 - All
  - Network Offering: Offering for Isolated networks with Source Nat service 
enabled

* Create ACLs
  - 10.1.0.0/16 - TCP - 22 - 22
  - 10.1.0.0/16 - TCP - 443 - 443

* Create Port Forwarding
  - 22:22 - 22:22 - instance cs43-01 [10.1.2.186]
  - 443:443 - 443:443 - instance cs43-01 [10.1.2.186]

* SSH into the new instance via the Public IP:

[root@devcloud-wil01 ~]# ssh root@10.1.1.4
The authenticity of host '10.1.1.4 (10.1.1.4)' can't be established.
RSA key fingerprint is 02:43:6c:24:c5:79:b6:e2:c8:b7:e8:3c:8d:13:37:91.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.1.1.4' (RSA) to the list of known hosts.
root@10.1.1.4's password:
%
%
% ls
ssh-host-dss-key.pub  ssh-host-rsa-key.pub
% cd /
% ls
bin bootdev etc homelib 
lost+found  mnt procrootsbinsys tmp 
usr var
%

With kind regards,
Wilder

-Original Message-
From: Paul Angus 
[mailto:paul.an...@shapeblue.com]
Sent: Wednesday, March 12, 2014 12:45 PM
To: dev@cloudstack.apache.org; Hugo Trippaers
Cc: Animesh Chaturvedi
Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)

Yes, I can build now.

:-)

Regards

Paul Angus
Cloud Architect
S: +44 20 3603 0540 | M: 
+447711418784 | T: CloudyAngus 
paul.an...@shapeblue.com

-Original Message-
From: Damoder Reddy 
[mailto:damoder.re...@citrix.com]
Sent: 12 March 2014 10:49
To: dev@cloudstack.apache.org; Hugo Trippaers
Cc: Animesh Chaturvedi
Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)

HI Paul,

 After you pull Hugo changes are you able to build now?

Thanks & Regards
Damodar/

-Original Message-
From: Paul Angus 
[mailto:paul.an...@shapeblue.com]
Sent: Wednesday, March 12, 2014 2:04 PM
To: Hugo Trippaers
Cc: Animesh Chaturvedi; 
dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round)

Yes that's correct. I'm building noredist


Regards,

Paul Angus
S: +44 20 3603 0540 | 
M: +447711418784>
T: @CloudyAngus
paul.an...@shapeblue.com>


 Original message 
From: Hugo Trippaers
Date:12/03/2014 07:32 (GMT+00:00)
To: Paul Angus
Cc: Animesh Chaturvedi 
,dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round)

Hey Paul,

Just to be clear, this problem only occurs during the noredist build right?

Mysql HA is one of the noredist features, so it should not be present in the 
regular build.

I'm check

Re: [REVIEW] OpenStack Swift as Object Storage Service

[David Nalley]

Hi Will:

This looks interesting; and I am thrilled to see it.

PLUpload is GPLv2 - which likely at best limits us to noredist
inclusion. I haven't yet looked at this in-depth, just got that far in
reading the spec.

--David

On Wed, Mar 12, 2014 at 1:24 PM, Will Stevens  wrote:
> Hello Everyone,
> I would like your opinion on the work I have done to integrate OpenStack
> Swift into CloudStack as an Object Storage Service available to the end
> users.
>
> *Functional Spec:*
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/OpenStack+Swift+as+Object+Storage+Service
>
> *Jira Ticket:* https://issues.apache.org/jira/browse/CLOUDSTACK-6230
>
> I have included a patch off master as of noon 2014/03/12 (today) so you can
> see the changes I have made to the code (I would recommend viewing the
> patch in an editor).
>
> I have not created an actual Review Request yet because I am not sure which
> version of CloudStack is reasonable to target adding this change.  I think
> 4.4 is probably too tight.
>
> There is one global variable I want to add before this gets committed as
> well.  The global variable would allow this functionality to be disabled in
> the UI (that may be the default actually, since it requires a Swift install
> to function).
>
> Let me know if you have questions and I will do my best to answer them and
> clarify the FS.
>
> Cheers,
>
> Will

Re: [jira] [Commented] (CLOUDSTACK-6232) isolated network can no longer reserve ip range

[Daan Hoogland]

Ah, that is what you meant. Let me look at it

On Wed, Mar 12, 2014 at 6:21 PM, Alena Prokharchyk (JIRA)
 wrote:
>
> [ 
> https://issues.apache.org/jira/browse/CLOUDSTACK-6232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932035#comment-13932035
>  ]
>
> Alena Prokharchyk commented on CLOUDSTACK-6232:
> ---
>
> Daan, looks like we also has to change createVlanIpRange call in addition to 
> createNetwork, otherwise the fix would be partial. This call is executed when 
> the network is already created, and you want to extend its range.
>
> Configuration ManagerImpl, public Vlan 
> createVlanAndPublicIpRange(CreateVlanIpRangeCmd cmd)
>
>   // If networkId is not specified, and vlan is Virtual or Direct
> // Untagged, try to locate default networks
> if (forVirtualNetwork) {
> if (network == null) {
> // find default public network in the zone
> networkId = 
> _networkModel.getSystemNetworkByZoneAndTrafficType(zoneId, 
> TrafficType.Public).getId();
> network = _networkModel.getNetwork(networkId);
> } else if (network.getGuestType() != null || 
> network.getTrafficType() != TrafficType.Public) {
> throw new InvalidParameterValueException("Can't find Public 
> network by id=" + networkId);
> }
> } else {
> if (network == null) {
> if (zone.getNetworkType() == DataCenter.NetworkType.Basic) {
> networkId = 
> _networkModel.getExclusiveGuestNetwork(zoneId).getId();
> network = _networkModel.getNetwork(networkId);
> } else {
> network = 
> _networkModel.getNetworkWithSecurityGroupEnabled(zoneId);
> if (network == null) {
> throw new InvalidParameterValueException("Nework id 
> is required for Direct vlan creation ");
> }
> networkId = network.getId();
> zoneId = network.getDataCenterId();
> }
> CHANGE THIS LINE BY ADDING  :} else if (network.getGuestType() == 
> null || network.getGuestType() == Network.GuestType.Isolated) {WITH
>
>  } else if (network.getGuestType() == null || (network.getGuestType() == 
> Network.GuestType.Isolated && 
> areServicesSupportedByNetworkOffering(ntwkOff.getId(), Service.SourceNat)))
>
>
> throw new InvalidParameterValueException("Can't create direct 
> vlan for network id=" + networkId + " with type: " + network.getGuestType());
> }
> }
>
>> isolated network can no longer reserve ip range
>> ---
>>
>> Key: CLOUDSTACK-6232
>> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6232
>> Project: CloudStack
>>  Issue Type: Bug
>>  Security Level: Public(Anyone can view this level - this is the 
>> default.)
>>  Components: Network Controller
>>Affects Versions: 4.2.0, 4.3.0, 4.4.0
>>Reporter: Daan Hoogland
>>Assignee: Daan Hoogland
>>Priority: Blocker
>> Fix For: 4.4.0
>>
>>
>> We found a functionality that we use once in a while no longer is permitted 
>> in 4.2.1. It seems in line with the philosophy of cloudstack but is hurting 
>> our operation. In 4.1.1 we could add a bridged network with the following 
>> network offering:
>> cno.traffictype = "GUEST"
>> cno.guestiptype = "Isolated"
>> cno.specifyipranges = True
>> cno.specifyvlan = False
>> cno.serviceproviderlist = [ { "service": "Connectivity", "provider": 
>> "NiciraNvp"},
>> { "service": "UserData", "provider": 
>> "VirtualRouter"},
>> { "service": "Dhcp", "provider": 
>> "VirtualRouter"} ]
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.2#6252)



-- 
Daan

Re: karma for editing versions

[Daan Hoogland]

On Wed, Mar 12, 2014 at 3:40 PM, David Nalley  wrote:
> have karma to do this.


Ok, David, I just may have. Moving to released is automatic by setting
a date on it, I gather?

-- 
Daan

RE: [4.3] CLOUDSTACK cidr list length

[Animesh Chaturvedi]

I see your this commit + one another f78e7ae51f55da17ed5ba239f99457ee8bc7c4d8 
for CLOUDSTACK-6232

That is it right so two commits. 


There is one more I just saw that is mostly checkstyle fixes 
0379dbb489b2502b8cf89583afd1a1f3baec93a3 which is trivial

> -Original Message-
> From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com]
> Sent: Wednesday, March 12, 2014 9:08 AM
> To: dev@cloudstack.apache.org
> Subject: [4.3] CLOUDSTACK cidr list length
> 
> Animesh,
> 
> This is one of two production issues that we have. I will be sending you the
> other one shortly. I was planning to wait till 4.3.1 but that one is a blocker
> for us.
> 
> This one is
> 454cac448d83b973d8cd337cf214b17e31828b93
> 
> Thanks,
> Daan

Re: Review Request 18552: Internal LB support for Juniper contrail VPC implementation

[Suresh Balineni]

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

(Updated March 12, 2014, 6:19 p.m.)


Review request for cloudstack and Alena Prokharchyk.


Repository: cloudstack-git


Description
---

Internal LB support for Juniper contrail VPC implementation.

- This implementation just extends the existing implementation of internal lb.
- New element  uses juniper contrail network offering so that nics are 
impelemented by contrail element. 
- LB VM deployment functionality is reused (new element is extended from 
existing Internal LB element implementation).


Diffs
-

  api/src/com/cloud/network/Network.java 6dc6752 
  api/src/org/apache/cloudstack/api/BaseCmd.java 0e83cee 
  plugins/network-elements/juniper-contrail/pom.xml 8c6877d 
  
plugins/network-elements/juniper-contrail/resources/META-INF/cloudstack/contrail/spring-contrail-context.xml
 99ab02e 
  
plugins/network-elements/juniper-contrail/src/org/apache/cloudstack/network/contrail/management/ContrailInternalLbElementImpl.java
 PRE-CREATION 
  
plugins/network-elements/juniper-contrail/src/org/apache/cloudstack/network/contrail/management/ContrailManagerImpl.java
 01be7db 
  server/src/com/cloud/network/vpc/VpcManagerImpl.java 2157eac 

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


Testing
---

Tested LB VM deployment. Traffic tests are done.


Thanks,

Suresh Balineni

Re: [4.3] CLOUDSTACK cidr list length

[Daan Hoogland]

H Animesh,

tyhe other one is for 6232 and I cherrypicked it without recompile,
hence the tabs to spaces commit.

I am still in discussion with Alena about it. She thinks it is
incomplete. It is functional for us, but she might be right anyway.

I don't think it will compile with the trivial one but
f78e7ae51f55da17ed5ba239f99457ee8bc7c4d8  is the blocker (regression)


On Wed, Mar 12, 2014 at 7:16 PM, Animesh Chaturvedi
 wrote:
> I see your this commit + one another f78e7ae51f55da17ed5ba239f99457ee8bc7c4d8 
> for CLOUDSTACK-6232
>
> That is it right so two commits.
>
>
> There is one more I just saw that is mostly checkstyle fixes 
> 0379dbb489b2502b8cf89583afd1a1f3baec93a3 which is trivial
>
>> -Original Message-
>> From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com]
>> Sent: Wednesday, March 12, 2014 9:08 AM
>> To: dev@cloudstack.apache.org
>> Subject: [4.3] CLOUDSTACK cidr list length
>>
>> Animesh,
>>
>> This is one of two production issues that we have. I will be sending you the
>> other one shortly. I was planning to wait till 4.3.1 but that one is a 
>> blocker
>> for us.
>>
>> This one is
>> 454cac448d83b973d8cd337cf214b17e31828b93
>>
>> Thanks,
>> Daan



-- 
Daan

[4.3][CLOUDSTACK-6232]isolated network can no longer reserve ip range

[Daan Hoogland]

Animesh, I really feel for you in your role as release manager. I
don't think anybody ever had such a hard time.

again this one solves our isolated net problem
f78e7ae51f55da17ed5ba239f99457ee8bc7c4d8

and this one my bogus tabs

0379dbb489b2502b8cf89583afd1a1f3baec93a3

and this one should get the ip space expansion in for isolated nets

edf97ac86c94741ae8964b640bdfc0234929c1e4

Do you drink, Animesh. I really want to buy you one and i think
everybody in the community should
-- 
Daan

Re: Review Request 18978: Ability to manipulate guest OS mappings

[Amogh Vasekar]

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

(Updated March 12, 2014, 6:48 p.m.)


Review request for cloudstack and Nitin Mehta.


Changes
---

Rebased to latest master


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

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


Repository: cloudstack-git


Description
---

Add APIs for ability to add new guest OS types, and their hypervisor specific 
mappings.
The table guest_os_hypervisor is currently maintained but not used, and the 
APIs reuse the same.


Diffs (updated)
-

  api/src/com/cloud/event/EventTypes.java 
a5fc0f0f7d3492fc0775b4514e4a9f506acb1ed7 
  api/src/com/cloud/server/ManagementService.java 
5fcf0b5fc5279193db4147607e9919433b2a56db 
  api/src/com/cloud/storage/GuestOS.java 
437cd37d1abaf131e09a294dfabbfe9e901af596 
  api/src/com/cloud/storage/GuestOSHypervisor.java 
f022722af04331b3feb9562683efa384b0ce5676 
  api/src/org/apache/cloudstack/api/ApiCommandJobType.java 
f27f001f868ffb0b8315f5468e67d2ec67db4306 
  api/src/org/apache/cloudstack/api/ApiConstants.java 
0a3fafda312ab72fea96928e68e37f25790e431c 
  api/src/org/apache/cloudstack/api/ResponseGenerator.java 
1cb53886a7cd4262f6d5636af6679a17f6a86dcd 
  api/src/org/apache/cloudstack/api/command/admin/guest/AddGuestOsCmd.java 
PRE-CREATION 
  
api/src/org/apache/cloudstack/api/command/admin/guest/AddGuestOsMappingCmd.java 
PRE-CREATION 
  
api/src/org/apache/cloudstack/api/command/admin/guest/ListGuestOsMappingCmd.java
 PRE-CREATION 
  api/src/org/apache/cloudstack/api/command/admin/guest/RemoveGuestOsCmd.java 
PRE-CREATION 
  
api/src/org/apache/cloudstack/api/command/admin/guest/RemoveGuestOsMappingCmd.java
 PRE-CREATION 
  api/src/org/apache/cloudstack/api/command/admin/guest/UpdateGuestOsCmd.java 
PRE-CREATION 
  
api/src/org/apache/cloudstack/api/command/admin/guest/UpdateGuestOsMappingCmd.java
 PRE-CREATION 
  api/src/org/apache/cloudstack/api/response/GuestOsMappingResponse.java 
PRE-CREATION 
  client/tomcatconf/commands.properties.in 
879c58d63425369eb411325bf6d2fb9d7de9d77a 
  engine/schema/src/com/cloud/storage/GuestOSHypervisorVO.java 
8210abf8c3d3becdc2b7d092a382f4b06123b7dd 
  engine/schema/src/com/cloud/storage/GuestOSVO.java 
57b852953a9fe4caae31043b8a63e1df2ff28f9b 
  engine/schema/src/com/cloud/storage/dao/GuestOSHypervisorDao.java 
651cfb56700857669fcfffd6b134358d2c4bb044 
  engine/schema/src/com/cloud/storage/dao/GuestOSHypervisorDaoImpl.java 
be680dc3a50830a9cd17b5cd203cdbc2db3e8936 
  server/src/com/cloud/api/ApiResponseHelper.java 
81bfe21ee819130957a6d3826417c1fdd4deba79 
  server/src/com/cloud/server/ManagementServer.java 
3b5f5ff206a28acaca964b0b4efeeb30c8c05da8 
  server/src/com/cloud/server/ManagementServerImpl.java 
663d4e505c5ff7acb215143bdf67f2e114912710 
  setup/db/db/schema-430to440.sql ee4cf215fb777fcd46c5715d2b21ffe157692e2a 

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


Testing
---

Tested on local environment on master branch for the APIs, including some edge 
cases.
Ran with findbugs and RAT to ensure no errors in added code


Thanks,

Amogh Vasekar

Re: [DISCUSS] realhostip.com going away

[Erik Weber]

On Fri, Mar 7, 2014 at 9:39 PM, Nux!  wrote:

> On 07.03.2014 20:28, John Kinsella wrote:
>
>> Soo...I'd recommend against something like Nux's suggestion below. I've
>> only looked briefly at VirtualDNS.java, and it looks fine from a
>> glance, but I'm willing to bet I can a) DOS it, and b) use it for a
>> reflection attack. I could be wrong, don't really have time to look
>> closely, but based on it looking like the design pattern for a basic
>> UDP server, I wouldn't recommend the community to build a network of
>> those.
>>
>
> I'd love not having to run that java DNS server, but the alternative is to
> add records for all IPs that I am going to use for guest network, which I
> imagine will keep increasing in time and this would be difficult and
> probably messy.
> Isn't realhostip service that Java thing now? How is the name translation
> done, if not?
>
>

Here's a first try at a PowerDNS lua script that provides a similar feature
to realhostip.com.
It's not been heavily tested, so I'd recommend to keep it out of production
environments as of now

https://github.com/terbolous/powerdns-cloudstack-proxy-dns


-- 
Erik Weber

Re: karma for editing versions

[David Nalley]

On Wed, Mar 12, 2014 at 2:11 PM, Daan Hoogland  wrote:
> On Wed, Mar 12, 2014 at 3:40 PM, David Nalley  wrote:
>> have karma to do this.
>
>
> Ok, David, I just may have. Moving to released is automatic by setting
> a date on it, I gather?
>

Yes

[QUESTION] About debugging a "Connection refused" SSVM error

[Mike Tutkowski]

Hi,

I don't yet have much experience with debugging SSVM issues.

Today I received a "Connection refused" status when trying to upload an
ISO. I assume this is coming from the SSVM when it tries to establish a
connection to the URL I provided. I have been able to successfully upload
ISOs as recently as yesterday.

1) I can ping the IP address of the URL I provided from within the SSVM.

2) I can download the ISO from another box on the same network as the SSVM.

3) I looked at cloud.log on the SSVM, but didn't see anything noteworthy.

Any thoughts on this?

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

Build failed in Jenkins: build-master-slowbuild #414

[jenkins]

See 

Changes:

[Daan Hoogland] [CLOUDSTACK-6232] bridging allowed in isolated networks

[Daan Hoogland] check-style: tabs to spaces

[Daan Hoogland] CLOUDSTACK-6232 allow expansion of ip on isolated networks as 
well

--
[...truncated 18098 lines...]

Tests run: 4, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi ---
[INFO] Cobertura 2.0.3 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/amazon/ec2/AmazonEC2SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/amazon/s3/AmazonS3SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SAcl.java.  Ensure this class was instrumented, and this 
data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SBucket.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SHost.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/BucketPolicyDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackAccountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackConfigurationDao.java.  Ensure this 
class was instrumented, and this data file contains the instrumentation 
information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackSvcOfferingDao.java.  Ensure this class 
was instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackUserDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostMountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartPartsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartUploadsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/d

Re: [QUESTION] About debugging a "Connection refused" SSVM error

[Chiradeep Vittal]

You probably need to configure secstorage.allowed.internal.sites

http://goo.gl/Z3tXqi

On 3/12/14, 1:01 PM, "Mike Tutkowski"  wrote:

>Hi,
>
>I don't yet have much experience with debugging SSVM issues.
>
>Today I received a "Connection refused" status when trying to upload an
>ISO. I assume this is coming from the SSVM when it tries to establish a
>connection to the URL I provided. I have been able to successfully upload
>ISOs as recently as yesterday.
>
>1) I can ping the IP address of the URL I provided from within the SSVM.
>
>2) I can download the ISO from another box on the same network as the
>SSVM.
>
>3) I looked at cloud.log on the SSVM, but didn't see anything noteworthy.
>
>Any thoughts on this?
>
>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: [4.4] ConsoleProxyListener says there is an error in the connect process

[Amogh Vasekar]

It actually seems related to the DB encryption key, where it is unable to
decrypt values in the DB.

Thanks,
Amogh

On 3/12/14 7:19 AM, "Nux!"  wrote:

>Hello,
>
>This might be related to changes regarding realhostip. Can anyone shed
>more light on this? At the moment the console proxy service is not
>working at all.
>
>http://fpaste.org/84666/13946337/raw/
>
>-- 
>Sent from the Delta quadrant using Borg technology!
>
>Nux!
>www.nux.ro

Re: [WIKI] Release test procedure contains wrong version of Java Open JDK

[Amogh Vasekar]

Isn't it still JDK 1.6 for 4.3 = the current release, for which the old
page was actually correct?

Thanks,
Amogh

On 3/12/14 2:32 AM, "Wilder Rodrigues" 
wrote:

>Already got rights and page has been edited.
>
>Thanks, Daan!
>
>Cheers,
>Wilder
>
>-Original Message-
>From: Wilder Rodrigues [mailto:wrodrig...@schubergphilis.com]
>Sent: Wednesday, March 12, 2014 10:19 AM
>To: dev@cloudstack.apache.org
>Subject: [WIKI] Release test procedure contains wrong version of Java
>Open JDK
>
>Hi guys and gals,
>
>Could I get rights to the Apache Wiki page? In case that's not possible,
>could someone please edit the page and change the version of the Java
>JDK? It now says 1.6 instead of 1.7.
>
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+proced
>ure
>
>sudo aptitude install openjdk-6-jdk
>
>Thanks in advance
>
>Cheers,
>Wilder

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

[Steve Wilson]

I think it was suggested multiple times that we push out the 4.4 freeze
date because the 4.3 work has been lagging.  I think this is just another
indicator we need to evaluate our release cadence as a community.

That being said, I don¹t think we want to hold 4.3 any further.  This must
be the best tested RC in the history of software at this point.  Unless
someone finds a new showstopper (that wasn¹t in the previous 6 builds!)
then let¹s get this puppy out! :-)

-Steve

On 3/12/14, 10:25 AM, "Mike Tutkowski" 
wrote:

>I hate to point this out as I know we've been struggling to get 4.3 out
>the
>door, but this week is probably not a great week to count votes for 4.3 as
>it is the last week before 4.4 Feature Freeze.
>
>
>On Wed, Mar 12, 2014 at 11:09 AM, Wilder Rodrigues <
>wrodrig...@schubergphilis.com> wrote:
>
>> Hi guys and gals,
>>
>> Based on the findings after my first round of tests, I give a +1 to the
>> 4.3 RC
>>
>> Please, find below what I have tested so far:
>>
>> * Environment
>>   - Management Server: Debian 7 VM under VirtualBox
>>   - DevCloud: XenServer 6.2
>>   - MySQL: running on the DevCloud
>>   - System VM: Latest from
>> http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/
>>
>> * Initial start-up
>>   - Everything seems to work fine
>>
>> * Zone
>>   - DNS1: 8.8.8.8
>>   - DNS2: 8.8.4.4
>>   - Hypervisor: XenServer
>>   - Guest CIDR: 10.1.2.0/24
>>   - Local Storage enabled: true
>>
>> * Public Traffic
>>   - 10.1.1.1 / 255.255.255.0 / 10.1.1.2 / 10.1.1.100
>>
>> * POD
>>   - 10.1.1.1 / 255.255.255.0 / 10.1.1.101 / 10.1.1.200
>>
>> * VLAN
>>   - 101 - 109
>>
>> * Host
>>   - Host Name: 178.237.34.120
>>   - Username: root
>>   - Password: blah
>>
>> * Secondary Storage
>>   - Provider: NFS
>>   - Name: sec01
>>   - Server: 10.1.1.114
>>   - Path: /opt/storage/secondary
>>
>> ::: ALL GREEN UP TO NOW :::
>>
>> * Create Instance
>>   - Featured: Tiny Linux
>>   - Compute Offering: Tiny Offering
>>   - Disk Offering: None
>>   - Instance name: cs43-01
>>
>> * NIC Information
>>   - IP Address: 10.1.2.186
>>   - Gateway: 10.1.2.1
>>   - Netmask: 255.255.255.0
>>
>> * Create Network
>>   - Name: devcloud-net01
>>   - Type: Isolated
>>   - CIDR: 10.1.2.0/24
>>   - Public IP: 10.1.1.4 [Source NAT]
>>   - Egress Rules: 0.0.0.0/0 - All
>>   - Network Offering: Offering for Isolated networks with Source Nat
>> service enabled
>>
>> * Create ACLs
>>   - 10.1.0.0/16 - TCP - 22 - 22
>>   - 10.1.0.0/16 - TCP - 443 - 443
>>
>> * Create Port Forwarding
>>   - 22:22 - 22:22 - instance cs43-01 [10.1.2.186]
>>   - 443:443 - 443:443 - instance cs43-01 [10.1.2.186]
>>
>> * SSH into the new instance via the Public IP:
>>
>> [root@devcloud-wil01 ~]# ssh root@10.1.1.4
>> The authenticity of host '10.1.1.4 (10.1.1.4)' can't be established.
>> RSA key fingerprint is 02:43:6c:24:c5:79:b6:e2:c8:b7:e8:3c:8d:13:37:91.
>> Are you sure you want to continue connecting (yes/no)? yes
>> Warning: Permanently added '10.1.1.4' (RSA) to the list of known hosts.
>> root@10.1.1.4's password:
>> %
>> %
>> % ls
>> ssh-host-dss-key.pub  ssh-host-rsa-key.pub
>> % cd /
>> % ls
>> bin bootdev etc homelib
>> lost+found  mnt procrootsbinsys
>>tmp
>> usr var
>> %
>>
>> With kind regards,
>> Wilder
>>
>> -Original Message-
>> From: Paul Angus [mailto:paul.an...@shapeblue.com]
>> Sent: Wednesday, March 12, 2014 12:45 PM
>> To: dev@cloudstack.apache.org; Hugo Trippaers
>> Cc: Animesh Chaturvedi
>> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>>
>> Yes, I can build now.
>>
>> :-)
>>
>> Regards
>>
>> Paul Angus
>> Cloud Architect
>> S: +44 20 3603 0540 | M: +447711418784 | T: CloudyAngus
>> paul.an...@shapeblue.com
>>
>> -Original Message-
>> From: Damoder Reddy [mailto:damoder.re...@citrix.com]
>> Sent: 12 March 2014 10:49
>> To: dev@cloudstack.apache.org; Hugo Trippaers
>> Cc: Animesh Chaturvedi
>> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>>
>> HI Paul,
>>
>>  After you pull Hugo changes are you able to build now?
>>
>> Thanks & Regards
>> Damodar/
>>
>> -Original Message-
>> From: Paul Angus [mailto:paul.an...@shapeblue.com]
>> Sent: Wednesday, March 12, 2014 2:04 PM
>> To: Hugo Trippaers
>> Cc: Animesh Chaturvedi; dev@cloudstack.apache.org
>> Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>>
>> Yes that's correct. I'm building noredist
>>
>>
>> Regards,
>>
>> Paul Angus
>> S: +44 20 3603 0540 | M: +447711418784> +447711418784>
>> T: @CloudyAngus
>> paul.an...@shapeblue.com
>>
>>
>>  Original message 
>> From: Hugo Trippaers
>> Date:12/03/2014 07:32 (GMT+00:00)
>> To: Paul Angus
>> Cc: Animesh Chaturvedi ,dev@cloudstack.apache.org
>> Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>>
>> Hey Paul,
>>
>> Just to be clear, this problem only occurs during the noredist build
>>right?
>>
>> Mysql HA is one o

RE: [4.3] CLOUDSTACK cidr list length

[Animesh Chaturvedi]

Ok so does the last commit edf97ac86c94741ae8964b640bdfc0234929c1e4 is the 
final one and addresses Alena's concern. I want to rebuild RC if we are good to 
go

> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Wednesday, March 12, 2014 11:26 AM
> To: dev
> Subject: Re: [4.3] CLOUDSTACK cidr list length
> 
> H Animesh,
> 
> tyhe other one is for 6232 and I cherrypicked it without recompile, hence the
> tabs to spaces commit.
> 
> I am still in discussion with Alena about it. She thinks it is incomplete. It 
> is
> functional for us, but she might be right anyway.
> 
> I don't think it will compile with the trivial one but
> f78e7ae51f55da17ed5ba239f99457ee8bc7c4d8  is the blocker (regression)
> 
> 
> On Wed, Mar 12, 2014 at 7:16 PM, Animesh Chaturvedi
>  wrote:
> > I see your this commit + one another
> > f78e7ae51f55da17ed5ba239f99457ee8bc7c4d8 for CLOUDSTACK-6232
> >
> > That is it right so two commits.
> >
> >
> > There is one more I just saw that is mostly checkstyle fixes
> > 0379dbb489b2502b8cf89583afd1a1f3baec93a3 which is trivial
> >
> >> -Original Message-
> >> From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com]
> >> Sent: Wednesday, March 12, 2014 9:08 AM
> >> To: dev@cloudstack.apache.org
> >> Subject: [4.3] CLOUDSTACK cidr list length
> >>
> >> Animesh,
> >>
> >> This is one of two production issues that we have. I will be sending
> >> you the other one shortly. I was planning to wait till 4.3.1 but that
> >> one is a blocker for us.
> >>
> >> This one is
> >> 454cac448d83b973d8cd337cf214b17e31828b93
> >>
> >> Thanks,
> >> Daan
> 
> 
> 
> --
> Daan

Re: [4.3] CLOUDSTACK cidr list length

[Daan Hoogland]

on my behalve we are,

thanks

On Wed, Mar 12, 2014 at 9:54 PM, Animesh Chaturvedi
 wrote:
> Ok so does the last commit edf97ac86c94741ae8964b640bdfc0234929c1e4 is the 
> final one and addresses Alena's concern. I want to rebuild RC if we are good 
> to go
>
>> -Original Message-
>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>> Sent: Wednesday, March 12, 2014 11:26 AM
>> To: dev
>> Subject: Re: [4.3] CLOUDSTACK cidr list length
>>
>> H Animesh,
>>
>> tyhe other one is for 6232 and I cherrypicked it without recompile, hence the
>> tabs to spaces commit.
>>
>> I am still in discussion with Alena about it. She thinks it is incomplete. 
>> It is
>> functional for us, but she might be right anyway.
>>
>> I don't think it will compile with the trivial one but
>> f78e7ae51f55da17ed5ba239f99457ee8bc7c4d8  is the blocker (regression)
>>
>>
>> On Wed, Mar 12, 2014 at 7:16 PM, Animesh Chaturvedi
>>  wrote:
>> > I see your this commit + one another
>> > f78e7ae51f55da17ed5ba239f99457ee8bc7c4d8 for CLOUDSTACK-6232
>> >
>> > That is it right so two commits.
>> >
>> >
>> > There is one more I just saw that is mostly checkstyle fixes
>> > 0379dbb489b2502b8cf89583afd1a1f3baec93a3 which is trivial
>> >
>> >> -Original Message-
>> >> From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com]
>> >> Sent: Wednesday, March 12, 2014 9:08 AM
>> >> To: dev@cloudstack.apache.org
>> >> Subject: [4.3] CLOUDSTACK cidr list length
>> >>
>> >> Animesh,
>> >>
>> >> This is one of two production issues that we have. I will be sending
>> >> you the other one shortly. I was planning to wait till 4.3.1 but that
>> >> one is a blocker for us.
>> >>
>> >> This one is
>> >> 454cac448d83b973d8cd337cf214b17e31828b93
>> >>
>> >> Thanks,
>> >> Daan
>>
>>
>>
>> --
>> Daan



-- 
Daan

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

[Daan Hoogland]

Steve,

As I have suggested before, we shoud not lengthen releas periods but
shorten them. I highly object to the idea of enlarging the window and
the release. It will pnly make relasing more difficult.

with n releases there are n*(n-1) potential conficts of the simlest
kind and n*(n-1)(n-2) potential conflicts of a slightly mor complex
kind... The higher n ... do the math. The more we postpone a feature
freeze the higher n will get. And that is only talking of features.
not about the simpler fixes that are added.

postponing when we have difficulty releasing quality makes no sense.

kind regards,
Daan Hoogland

On Wed, Mar 12, 2014 at 9:46 PM, Steve Wilson  wrote:
> I think it was suggested multiple times that we push out the 4.4 freeze
> date because the 4.3 work has been lagging.  I think this is just another
> indicator we need to evaluate our release cadence as a community.
>
> That being said, I don¹t think we want to hold 4.3 any further.  This must
> be the best tested RC in the history of software at this point.  Unless
> someone finds a new showstopper (that wasn¹t in the previous 6 builds!)
> then let¹s get this puppy out! :-)
>
> -Steve
>
> On 3/12/14, 10:25 AM, "Mike Tutkowski" 
> wrote:
>
>>I hate to point this out as I know we've been struggling to get 4.3 out
>>the
>>door, but this week is probably not a great week to count votes for 4.3 as
>>it is the last week before 4.4 Feature Freeze.
>>
>>
>>On Wed, Mar 12, 2014 at 11:09 AM, Wilder Rodrigues <
>>wrodrig...@schubergphilis.com> wrote:
>>
>>> Hi guys and gals,
>>>
>>> Based on the findings after my first round of tests, I give a +1 to the
>>> 4.3 RC
>>>
>>> Please, find below what I have tested so far:
>>>
>>> * Environment
>>>   - Management Server: Debian 7 VM under VirtualBox
>>>   - DevCloud: XenServer 6.2
>>>   - MySQL: running on the DevCloud
>>>   - System VM: Latest from
>>> http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/
>>>
>>> * Initial start-up
>>>   - Everything seems to work fine
>>>
>>> * Zone
>>>   - DNS1: 8.8.8.8
>>>   - DNS2: 8.8.4.4
>>>   - Hypervisor: XenServer
>>>   - Guest CIDR: 10.1.2.0/24
>>>   - Local Storage enabled: true
>>>
>>> * Public Traffic
>>>   - 10.1.1.1 / 255.255.255.0 / 10.1.1.2 / 10.1.1.100
>>>
>>> * POD
>>>   - 10.1.1.1 / 255.255.255.0 / 10.1.1.101 / 10.1.1.200
>>>
>>> * VLAN
>>>   - 101 - 109
>>>
>>> * Host
>>>   - Host Name: 178.237.34.120
>>>   - Username: root
>>>   - Password: blah
>>>
>>> * Secondary Storage
>>>   - Provider: NFS
>>>   - Name: sec01
>>>   - Server: 10.1.1.114
>>>   - Path: /opt/storage/secondary
>>>
>>> ::: ALL GREEN UP TO NOW :::
>>>
>>> * Create Instance
>>>   - Featured: Tiny Linux
>>>   - Compute Offering: Tiny Offering
>>>   - Disk Offering: None
>>>   - Instance name: cs43-01
>>>
>>> * NIC Information
>>>   - IP Address: 10.1.2.186
>>>   - Gateway: 10.1.2.1
>>>   - Netmask: 255.255.255.0
>>>
>>> * Create Network
>>>   - Name: devcloud-net01
>>>   - Type: Isolated
>>>   - CIDR: 10.1.2.0/24
>>>   - Public IP: 10.1.1.4 [Source NAT]
>>>   - Egress Rules: 0.0.0.0/0 - All
>>>   - Network Offering: Offering for Isolated networks with Source Nat
>>> service enabled
>>>
>>> * Create ACLs
>>>   - 10.1.0.0/16 - TCP - 22 - 22
>>>   - 10.1.0.0/16 - TCP - 443 - 443
>>>
>>> * Create Port Forwarding
>>>   - 22:22 - 22:22 - instance cs43-01 [10.1.2.186]
>>>   - 443:443 - 443:443 - instance cs43-01 [10.1.2.186]
>>>
>>> * SSH into the new instance via the Public IP:
>>>
>>> [root@devcloud-wil01 ~]# ssh root@10.1.1.4
>>> The authenticity of host '10.1.1.4 (10.1.1.4)' can't be established.
>>> RSA key fingerprint is 02:43:6c:24:c5:79:b6:e2:c8:b7:e8:3c:8d:13:37:91.
>>> Are you sure you want to continue connecting (yes/no)? yes
>>> Warning: Permanently added '10.1.1.4' (RSA) to the list of known hosts.
>>> root@10.1.1.4's password:
>>> %
>>> %
>>> % ls
>>> ssh-host-dss-key.pub  ssh-host-rsa-key.pub
>>> % cd /
>>> % ls
>>> bin bootdev etc homelib
>>> lost+found  mnt procrootsbinsys
>>>tmp
>>> usr var
>>> %
>>>
>>> With kind regards,
>>> Wilder
>>>
>>> -Original Message-
>>> From: Paul Angus [mailto:paul.an...@shapeblue.com]
>>> Sent: Wednesday, March 12, 2014 12:45 PM
>>> To: dev@cloudstack.apache.org; Hugo Trippaers
>>> Cc: Animesh Chaturvedi
>>> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>>>
>>> Yes, I can build now.
>>>
>>> :-)
>>>
>>> Regards
>>>
>>> Paul Angus
>>> Cloud Architect
>>> S: +44 20 3603 0540 | M: +447711418784 | T: CloudyAngus
>>> paul.an...@shapeblue.com
>>>
>>> -Original Message-
>>> From: Damoder Reddy [mailto:damoder.re...@citrix.com]
>>> Sent: 12 March 2014 10:49
>>> To: dev@cloudstack.apache.org; Hugo Trippaers
>>> Cc: Animesh Chaturvedi
>>> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>>>
>>> HI Paul,
>>>
>>>  After you pull Hugo changes are you able to build now?
>>>
>>> Thanks & Regards
>>> Damodar/
>>>
>>> -Or

Recalculating cpuallocated

[Timothy Ehlers]

First of all i pulled in the cpuallocation fix slated for 4.3 but im on the
4.2.1 codebase.

When you adjust cpu over-provisioning the % usage increase by the same
factor "a note pops up to warn you about this"

But i need to recalulate rather than re-launch all the vms. Is there a
planned feature or where is it storing this data?


server1 Memory: 60.844698  cpuallocated: 293%
setting overprovision to 4x
server1 Memory: 60.844698  cpuallocated: 1172.01%

Relaunching all of the vms sets things back to normal.

-- 
Tim Ehlers

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

[Mike Tutkowski]

There has to be some minimum boundary, though, right? Otherwise we might as
well release every week. :)


On Wed, Mar 12, 2014 at 3:10 PM, Daan Hoogland wrote:

> Steve,
>
> As I have suggested before, we shoud not lengthen releas periods but
> shorten them. I highly object to the idea of enlarging the window and
> the release. It will pnly make relasing more difficult.
>
> with n releases there are n*(n-1) potential conficts of the simlest
> kind and n*(n-1)(n-2) potential conflicts of a slightly mor complex
> kind... The higher n ... do the math. The more we postpone a feature
> freeze the higher n will get. And that is only talking of features.
> not about the simpler fixes that are added.
>
> postponing when we have difficulty releasing quality makes no sense.
>
> kind regards,
> Daan Hoogland
>
> On Wed, Mar 12, 2014 at 9:46 PM, Steve Wilson 
> wrote:
> > I think it was suggested multiple times that we push out the 4.4 freeze
> > date because the 4.3 work has been lagging.  I think this is just another
> > indicator we need to evaluate our release cadence as a community.
> >
> > That being said, I don¹t think we want to hold 4.3 any further.  This
> must
> > be the best tested RC in the history of software at this point.  Unless
> > someone finds a new showstopper (that wasn¹t in the previous 6 builds!)
> > then let¹s get this puppy out! :-)
> >
> > -Steve
> >
> > On 3/12/14, 10:25 AM, "Mike Tutkowski" 
> > wrote:
> >
> >>I hate to point this out as I know we've been struggling to get 4.3 out
> >>the
> >>door, but this week is probably not a great week to count votes for 4.3
> as
> >>it is the last week before 4.4 Feature Freeze.
> >>
> >>
> >>On Wed, Mar 12, 2014 at 11:09 AM, Wilder Rodrigues <
> >>wrodrig...@schubergphilis.com> wrote:
> >>
> >>> Hi guys and gals,
> >>>
> >>> Based on the findings after my first round of tests, I give a +1 to the
> >>> 4.3 RC
> >>>
> >>> Please, find below what I have tested so far:
> >>>
> >>> * Environment
> >>>   - Management Server: Debian 7 VM under VirtualBox
> >>>   - DevCloud: XenServer 6.2
> >>>   - MySQL: running on the DevCloud
> >>>   - System VM: Latest from
> >>> http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/
> >>>
> >>> * Initial start-up
> >>>   - Everything seems to work fine
> >>>
> >>> * Zone
> >>>   - DNS1: 8.8.8.8
> >>>   - DNS2: 8.8.4.4
> >>>   - Hypervisor: XenServer
> >>>   - Guest CIDR: 10.1.2.0/24
> >>>   - Local Storage enabled: true
> >>>
> >>> * Public Traffic
> >>>   - 10.1.1.1 / 255.255.255.0 / 10.1.1.2 / 10.1.1.100
> >>>
> >>> * POD
> >>>   - 10.1.1.1 / 255.255.255.0 / 10.1.1.101 / 10.1.1.200
> >>>
> >>> * VLAN
> >>>   - 101 - 109
> >>>
> >>> * Host
> >>>   - Host Name: 178.237.34.120
> >>>   - Username: root
> >>>   - Password: blah
> >>>
> >>> * Secondary Storage
> >>>   - Provider: NFS
> >>>   - Name: sec01
> >>>   - Server: 10.1.1.114
> >>>   - Path: /opt/storage/secondary
> >>>
> >>> ::: ALL GREEN UP TO NOW :::
> >>>
> >>> * Create Instance
> >>>   - Featured: Tiny Linux
> >>>   - Compute Offering: Tiny Offering
> >>>   - Disk Offering: None
> >>>   - Instance name: cs43-01
> >>>
> >>> * NIC Information
> >>>   - IP Address: 10.1.2.186
> >>>   - Gateway: 10.1.2.1
> >>>   - Netmask: 255.255.255.0
> >>>
> >>> * Create Network
> >>>   - Name: devcloud-net01
> >>>   - Type: Isolated
> >>>   - CIDR: 10.1.2.0/24
> >>>   - Public IP: 10.1.1.4 [Source NAT]
> >>>   - Egress Rules: 0.0.0.0/0 - All
> >>>   - Network Offering: Offering for Isolated networks with Source Nat
> >>> service enabled
> >>>
> >>> * Create ACLs
> >>>   - 10.1.0.0/16 - TCP - 22 - 22
> >>>   - 10.1.0.0/16 - TCP - 443 - 443
> >>>
> >>> * Create Port Forwarding
> >>>   - 22:22 - 22:22 - instance cs43-01 [10.1.2.186]
> >>>   - 443:443 - 443:443 - instance cs43-01 [10.1.2.186]
> >>>
> >>> * SSH into the new instance via the Public IP:
> >>>
> >>> [root@devcloud-wil01 ~]# ssh root@10.1.1.4
> >>> The authenticity of host '10.1.1.4 (10.1.1.4)' can't be established.
> >>> RSA key fingerprint is 02:43:6c:24:c5:79:b6:e2:c8:b7:e8:3c:8d:13:37:91.
> >>> Are you sure you want to continue connecting (yes/no)? yes
> >>> Warning: Permanently added '10.1.1.4' (RSA) to the list of known hosts.
> >>> root@10.1.1.4's password:
> >>> %
> >>> %
> >>> % ls
> >>> ssh-host-dss-key.pub  ssh-host-rsa-key.pub
> >>> % cd /
> >>> % ls
> >>> bin bootdev etc homelib
> >>> lost+found  mnt procrootsbinsys
> >>>tmp
> >>> usr var
> >>> %
> >>>
> >>> With kind regards,
> >>> Wilder
> >>>
> >>> -Original Message-
> >>> From: Paul Angus [mailto:paul.an...@shapeblue.com]
> >>> Sent: Wednesday, March 12, 2014 12:45 PM
> >>> To: dev@cloudstack.apache.org; Hugo Trippaers
> >>> Cc: Animesh Chaturvedi
> >>> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)
> >>>
> >>> Yes, I can build now.
> >>>
> >>> :-)
> >>>
> >>> Regards
> >>>
> >>> Paul Angus
> >>> Cloud Architect
> >>> S: +44 20 360

Re: [QUESTION] About debugging a "Connection refused" SSVM error

[Mike Tutkowski]

Thanks, Chiradeep - that helped! Not sure why I wasn't ever having trouble
with that before, though.


On Wed, Mar 12, 2014 at 2:14 PM, Chiradeep Vittal <
chiradeep.vit...@citrix.com> wrote:

> You probably need to configure secstorage.allowed.internal.sites
>
> http://goo.gl/Z3tXqi
>
> On 3/12/14, 1:01 PM, "Mike Tutkowski" 
> wrote:
>
> >Hi,
> >
> >I don't yet have much experience with debugging SSVM issues.
> >
> >Today I received a "Connection refused" status when trying to upload an
> >ISO. I assume this is coming from the SSVM when it tries to establish a
> >connection to the URL I provided. I have been able to successfully upload
> >ISOs as recently as yesterday.
> >
> >1) I can ping the IP address of the URL I provided from within the SSVM.
> >
> >2) I can download the ISO from another box on the same network as the
> >SSVM.
> >
> >3) I looked at cloud.log on the SSVM, but didn't see anything noteworthy.
> >
> >Any thoughts on this?
> >
> >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: [VOTE] Apache CloudStack 4.3.0 (seventh round)

[Daan Hoogland]

If we produce a new feature per week, why not?

On Wed, Mar 12, 2014 at 10:34 PM, Mike Tutkowski
 wrote:
> There has to be some minimum boundary, though, right? Otherwise we might as
> well release every week. :)
>
>
> On Wed, Mar 12, 2014 at 3:10 PM, Daan Hoogland wrote:
>
>> Steve,
>>
>> As I have suggested before, we shoud not lengthen releas periods but
>> shorten them. I highly object to the idea of enlarging the window and
>> the release. It will pnly make relasing more difficult.
>>
>> with n releases there are n*(n-1) potential conficts of the simlest
>> kind and n*(n-1)(n-2) potential conflicts of a slightly mor complex
>> kind... The higher n ... do the math. The more we postpone a feature
>> freeze the higher n will get. And that is only talking of features.
>> not about the simpler fixes that are added.
>>
>> postponing when we have difficulty releasing quality makes no sense.
>>
>> kind regards,
>> Daan Hoogland
>>
>> On Wed, Mar 12, 2014 at 9:46 PM, Steve Wilson 
>> wrote:
>> > I think it was suggested multiple times that we push out the 4.4 freeze
>> > date because the 4.3 work has been lagging.  I think this is just another
>> > indicator we need to evaluate our release cadence as a community.
>> >
>> > That being said, I don¹t think we want to hold 4.3 any further.  This
>> must
>> > be the best tested RC in the history of software at this point.  Unless
>> > someone finds a new showstopper (that wasn¹t in the previous 6 builds!)
>> > then let¹s get this puppy out! :-)
>> >
>> > -Steve
>> >
>> > On 3/12/14, 10:25 AM, "Mike Tutkowski" 
>> > wrote:
>> >
>> >>I hate to point this out as I know we've been struggling to get 4.3 out
>> >>the
>> >>door, but this week is probably not a great week to count votes for 4.3
>> as
>> >>it is the last week before 4.4 Feature Freeze.
>> >>
>> >>
>> >>On Wed, Mar 12, 2014 at 11:09 AM, Wilder Rodrigues <
>> >>wrodrig...@schubergphilis.com> wrote:
>> >>
>> >>> Hi guys and gals,
>> >>>
>> >>> Based on the findings after my first round of tests, I give a +1 to the
>> >>> 4.3 RC
>> >>>
>> >>> Please, find below what I have tested so far:
>> >>>
>> >>> * Environment
>> >>>   - Management Server: Debian 7 VM under VirtualBox
>> >>>   - DevCloud: XenServer 6.2
>> >>>   - MySQL: running on the DevCloud
>> >>>   - System VM: Latest from
>> >>> http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/
>> >>>
>> >>> * Initial start-up
>> >>>   - Everything seems to work fine
>> >>>
>> >>> * Zone
>> >>>   - DNS1: 8.8.8.8
>> >>>   - DNS2: 8.8.4.4
>> >>>   - Hypervisor: XenServer
>> >>>   - Guest CIDR: 10.1.2.0/24
>> >>>   - Local Storage enabled: true
>> >>>
>> >>> * Public Traffic
>> >>>   - 10.1.1.1 / 255.255.255.0 / 10.1.1.2 / 10.1.1.100
>> >>>
>> >>> * POD
>> >>>   - 10.1.1.1 / 255.255.255.0 / 10.1.1.101 / 10.1.1.200
>> >>>
>> >>> * VLAN
>> >>>   - 101 - 109
>> >>>
>> >>> * Host
>> >>>   - Host Name: 178.237.34.120
>> >>>   - Username: root
>> >>>   - Password: blah
>> >>>
>> >>> * Secondary Storage
>> >>>   - Provider: NFS
>> >>>   - Name: sec01
>> >>>   - Server: 10.1.1.114
>> >>>   - Path: /opt/storage/secondary
>> >>>
>> >>> ::: ALL GREEN UP TO NOW :::
>> >>>
>> >>> * Create Instance
>> >>>   - Featured: Tiny Linux
>> >>>   - Compute Offering: Tiny Offering
>> >>>   - Disk Offering: None
>> >>>   - Instance name: cs43-01
>> >>>
>> >>> * NIC Information
>> >>>   - IP Address: 10.1.2.186
>> >>>   - Gateway: 10.1.2.1
>> >>>   - Netmask: 255.255.255.0
>> >>>
>> >>> * Create Network
>> >>>   - Name: devcloud-net01
>> >>>   - Type: Isolated
>> >>>   - CIDR: 10.1.2.0/24
>> >>>   - Public IP: 10.1.1.4 [Source NAT]
>> >>>   - Egress Rules: 0.0.0.0/0 - All
>> >>>   - Network Offering: Offering for Isolated networks with Source Nat
>> >>> service enabled
>> >>>
>> >>> * Create ACLs
>> >>>   - 10.1.0.0/16 - TCP - 22 - 22
>> >>>   - 10.1.0.0/16 - TCP - 443 - 443
>> >>>
>> >>> * Create Port Forwarding
>> >>>   - 22:22 - 22:22 - instance cs43-01 [10.1.2.186]
>> >>>   - 443:443 - 443:443 - instance cs43-01 [10.1.2.186]
>> >>>
>> >>> * SSH into the new instance via the Public IP:
>> >>>
>> >>> [root@devcloud-wil01 ~]# ssh root@10.1.1.4
>> >>> The authenticity of host '10.1.1.4 (10.1.1.4)' can't be established.
>> >>> RSA key fingerprint is 02:43:6c:24:c5:79:b6:e2:c8:b7:e8:3c:8d:13:37:91.
>> >>> Are you sure you want to continue connecting (yes/no)? yes
>> >>> Warning: Permanently added '10.1.1.4' (RSA) to the list of known hosts.
>> >>> root@10.1.1.4's password:
>> >>> %
>> >>> %
>> >>> % ls
>> >>> ssh-host-dss-key.pub  ssh-host-rsa-key.pub
>> >>> % cd /
>> >>> % ls
>> >>> bin bootdev etc homelib
>> >>> lost+found  mnt procrootsbinsys
>> >>>tmp
>> >>> usr var
>> >>> %
>> >>>
>> >>> With kind regards,
>> >>> Wilder
>> >>>
>> >>> -Original Message-
>> >>> From: Paul Angus [mailto:paul.an...@shapeblue.com]
>> >>> Sent: Wednesday, March 12, 2014 12:45 PM
>> >>> To: dev@cloudsta

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

[Erik Weber]

That would require a whole other way of upgrading though. Having to restart
all system vms every week or two is not something i would look forward to.

On the other side, with more releases it wouldn't be that big issue to miss
a freeze date, and with fewer new features / improvements it should
hopefully require less fixes.

-- 
Erik Weber
12. mars 2014 22:53 skrev "Daan Hoogland" 
følgende:

> If we produce a new feature per week, why not?
>
> On Wed, Mar 12, 2014 at 10:34 PM, Mike Tutkowski
>  wrote:
> > There has to be some minimum boundary, though, right? Otherwise we might
> as
> > well release every week. :)
> >
> >
> > On Wed, Mar 12, 2014 at 3:10 PM, Daan Hoogland  >wrote:
> >
> >> Steve,
> >>
> >> As I have suggested before, we shoud not lengthen releas periods but
> >> shorten them. I highly object to the idea of enlarging the window and
> >> the release. It will pnly make relasing more difficult.
> >>
> >> with n releases there are n*(n-1) potential conficts of the simlest
> >> kind and n*(n-1)(n-2) potential conflicts of a slightly mor complex
> >> kind... The higher n ... do the math. The more we postpone a feature
> >> freeze the higher n will get. And that is only talking of features.
> >> not about the simpler fixes that are added.
> >>
> >> postponing when we have difficulty releasing quality makes no sense.
> >>
> >> kind regards,
> >> Daan Hoogland
> >>
> >> On Wed, Mar 12, 2014 at 9:46 PM, Steve Wilson 
> >> wrote:
> >> > I think it was suggested multiple times that we push out the 4.4
> freeze
> >> > date because the 4.3 work has been lagging.  I think this is just
> another
> >> > indicator we need to evaluate our release cadence as a community.
> >> >
> >> > That being said, I don¹t think we want to hold 4.3 any further.  This
> >> must
> >> > be the best tested RC in the history of software at this point.
>  Unless
> >> > someone finds a new showstopper (that wasn¹t in the previous 6
> builds!)
> >> > then let¹s get this puppy out! :-)
> >> >
> >> > -Steve
> >> >
> >> > On 3/12/14, 10:25 AM, "Mike Tutkowski" 
> >> > wrote:
> >> >
> >> >>I hate to point this out as I know we've been struggling to get 4.3
> out
> >> >>the
> >> >>door, but this week is probably not a great week to count votes for
> 4.3
> >> as
> >> >>it is the last week before 4.4 Feature Freeze.
> >> >>
> >> >>
> >> >>On Wed, Mar 12, 2014 at 11:09 AM, Wilder Rodrigues <
> >> >>wrodrig...@schubergphilis.com> wrote:
> >> >>
> >> >>> Hi guys and gals,
> >> >>>
> >> >>> Based on the findings after my first round of tests, I give a +1 to
> the
> >> >>> 4.3 RC
> >> >>>
> >> >>> Please, find below what I have tested so far:
> >> >>>
> >> >>> * Environment
> >> >>>   - Management Server: Debian 7 VM under VirtualBox
> >> >>>   - DevCloud: XenServer 6.2
> >> >>>   - MySQL: running on the DevCloud
> >> >>>   - System VM: Latest from
> >> >>>
> http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/
> >> >>>
> >> >>> * Initial start-up
> >> >>>   - Everything seems to work fine
> >> >>>
> >> >>> * Zone
> >> >>>   - DNS1: 8.8.8.8
> >> >>>   - DNS2: 8.8.4.4
> >> >>>   - Hypervisor: XenServer
> >> >>>   - Guest CIDR: 10.1.2.0/24
> >> >>>   - Local Storage enabled: true
> >> >>>
> >> >>> * Public Traffic
> >> >>>   - 10.1.1.1 / 255.255.255.0 / 10.1.1.2 / 10.1.1.100
> >> >>>
> >> >>> * POD
> >> >>>   - 10.1.1.1 / 255.255.255.0 / 10.1.1.101 / 10.1.1.200
> >> >>>
> >> >>> * VLAN
> >> >>>   - 101 - 109
> >> >>>
> >> >>> * Host
> >> >>>   - Host Name: 178.237.34.120
> >> >>>   - Username: root
> >> >>>   - Password: blah
> >> >>>
> >> >>> * Secondary Storage
> >> >>>   - Provider: NFS
> >> >>>   - Name: sec01
> >> >>>   - Server: 10.1.1.114
> >> >>>   - Path: /opt/storage/secondary
> >> >>>
> >> >>> ::: ALL GREEN UP TO NOW :::
> >> >>>
> >> >>> * Create Instance
> >> >>>   - Featured: Tiny Linux
> >> >>>   - Compute Offering: Tiny Offering
> >> >>>   - Disk Offering: None
> >> >>>   - Instance name: cs43-01
> >> >>>
> >> >>> * NIC Information
> >> >>>   - IP Address: 10.1.2.186
> >> >>>   - Gateway: 10.1.2.1
> >> >>>   - Netmask: 255.255.255.0
> >> >>>
> >> >>> * Create Network
> >> >>>   - Name: devcloud-net01
> >> >>>   - Type: Isolated
> >> >>>   - CIDR: 10.1.2.0/24
> >> >>>   - Public IP: 10.1.1.4 [Source NAT]
> >> >>>   - Egress Rules: 0.0.0.0/0 - All
> >> >>>   - Network Offering: Offering for Isolated networks with Source Nat
> >> >>> service enabled
> >> >>>
> >> >>> * Create ACLs
> >> >>>   - 10.1.0.0/16 - TCP - 22 - 22
> >> >>>   - 10.1.0.0/16 - TCP - 443 - 443
> >> >>>
> >> >>> * Create Port Forwarding
> >> >>>   - 22:22 - 22:22 - instance cs43-01 [10.1.2.186]
> >> >>>   - 443:443 - 443:443 - instance cs43-01 [10.1.2.186]
> >> >>>
> >> >>> * SSH into the new instance via the Public IP:
> >> >>>
> >> >>> [root@devcloud-wil01 ~]# ssh root@10.1.1.4
> >> >>> The authenticity of host '10.1.1.4 (10.1.1.4)' can't be established.
> >> >>> RSA key fingerprint is
> 02:43:6c:24:c5:79:b6:e2:c8:b7:e8:3c:8d:13:37:91.
> >> >>> A

Re: Recalculating cpuallocated

[Nitin Mehta]

Do give the FS on this feature a read -
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CPU+and+RAM+Overcomm
it

Do read the future tasks that should be done.

Thanks,
-Nitin

On 12/03/14 2:19 PM, "Timothy Ehlers"  wrote:

>First of all i pulled in the cpuallocation fix slated for 4.3 but im on
>the
>4.2.1 codebase.
>
>When you adjust cpu over-provisioning the % usage increase by the same
>factor "a note pops up to warn you about this"
>
>But i need to recalulate rather than re-launch all the vms. Is there a
>planned feature or where is it storing this data?
>
>
>server1 Memory: 60.844698  cpuallocated: 293%
>setting overprovision to 4x
>server1 Memory: 60.844698  cpuallocated: 1172.01%
>
>Relaunching all of the vms sets things back to normal.
>
>-- 
>Tim Ehlers

Re: Review Request 19021: Cloudbyte Elastistor storage plug-in

[edison su]

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


Could you upload a new patch? I can't apply it on master branch, git complains 
that some files are not indexed.

- edison su


On March 12, 2014, 4:09 p.m., punith s wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19021/
> ---
> 
> (Updated March 12, 2014, 4:09 p.m.)
> 
> 
> Review request for cloudstack, edison su and Mike Tutkowski.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> This patch implements a basic storage plug-in for cloudbyte elastistor 
> v1.3.0, The plug-in is a new feature for cloudstack 4.4 and above.
> 
> this does not implement managed storage yet, it is been integrated only with 
> CreateStoragePool and DeleteStoragePool api's.
> 
> the desired behavior of the plugin are:
> 
> * Allow an Admin to create a primary storage at cluster level, hence creates 
> a volume in elastistor and gets attached to the host with the given 
> capacityiops and capacitybytes through CreateStoragePool api with provider 
> being elastistor.
> 
> *Allow an admin to delete a primary storage at cluster level, hence it 
> deletes the volume from host in cloudstack and deletes the respective volume 
> in elastistor.
> 
> * volume and datadisks fuctions performs the default storage fuctions, ie. 
> the driver extends the CloudStackPrimaryDataStoreDriverImpl.
> 
> * support for both nfs and icsci primary storage.
> 
> 
> Diffs
> -
> 
>   plugins/storage/volume/cloudbyte/pom.xml PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/spring-storage-volume-cloudbyte-context.xml
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/BaseCommand.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/ElastiCenterClient.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/ElastiCenterCommand.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/AddQosGroupCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/CreateTsmCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/CreateVolumeCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/DeleteTsmCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/DeleteVolumeCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/ListCapabilitiesCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/ListTsmCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/QueryAsyncJobResultCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/driver/ElastistorPrimaryDataStoreDriver.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/Async.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/Capabilities.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/FileSystem.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/FileSystemWrapper.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/FilesystemQoSWrapper.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/JobId.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/QoSGroup.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/QoSGroupWrapper.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/StorageVolume.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/StorageVolumeWrapper.java
>  PRE-CREATION 
>   
> plugins/storage

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

[Alex Hitchins]

This could also have an impact on adoption of the technology. People might shy 
away from a package that changes so frequently.

I think a much more rigorous testing schedule would be a massive help to get 
RC's out the door. If you propose a feature I think part of the spec should be 
testing requirements (not code tests) and some indication of who will be 
performing the testing. Treat it as UAT.

Regards

Alex Hitchins

D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969

alex.hitch...@shapeblue.com

-Original Message-
From: Erik Weber [mailto:terbol...@gmail.com]
Sent: 12 March 2014 22:02
To: dev
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round)

That would require a whole other way of upgrading though. Having to restart all 
system vms every week or two is not something i would look forward to.

On the other side, with more releases it wouldn't be that big issue to miss a 
freeze date, and with fewer new features / improvements it should hopefully 
require less fixes.

--
Erik Weber
12. mars 2014 22:53 skrev "Daan Hoogland" 
følgende:

> If we produce a new feature per week, why not?
>
> On Wed, Mar 12, 2014 at 10:34 PM, Mike Tutkowski
>  wrote:
> > There has to be some minimum boundary, though, right? Otherwise we
> > might
> as
> > well release every week. :)
> >
> >
> > On Wed, Mar 12, 2014 at 3:10 PM, Daan Hoogland
> > >wrote:
> >
> >> Steve,
> >>
> >> As I have suggested before, we shoud not lengthen releas periods
> >> but shorten them. I highly object to the idea of enlarging the
> >> window and the release. It will pnly make relasing more difficult.
> >>
> >> with n releases there are n*(n-1) potential conficts of the simlest
> >> kind and n*(n-1)(n-2) potential conflicts of a slightly mor complex
> >> kind... The higher n ... do the math. The more we postpone a
> >> feature freeze the higher n will get. And that is only talking of features.
> >> not about the simpler fixes that are added.
> >>
> >> postponing when we have difficulty releasing quality makes no sense.
> >>
> >> kind regards,
> >> Daan Hoogland
> >>
> >> On Wed, Mar 12, 2014 at 9:46 PM, Steve Wilson
> >> 
> >> wrote:
> >> > I think it was suggested multiple times that we push out the 4.4
> freeze
> >> > date because the 4.3 work has been lagging.  I think this is just
> another
> >> > indicator we need to evaluate our release cadence as a community.
> >> >
> >> > That being said, I don¹t think we want to hold 4.3 any further.
> >> > This
> >> must
> >> > be the best tested RC in the history of software at this point.
>  Unless
> >> > someone finds a new showstopper (that wasn¹t in the previous 6
> builds!)
> >> > then let¹s get this puppy out! :-)
> >> >
> >> > -Steve
> >> >
> >> > On 3/12/14, 10:25 AM, "Mike Tutkowski"
> >> > 
> >> > wrote:
> >> >
> >> >>I hate to point this out as I know we've been struggling to get
> >> >>4.3
> out
> >> >>the
> >> >>door, but this week is probably not a great week to count votes
> >> >>for
> 4.3
> >> as
> >> >>it is the last week before 4.4 Feature Freeze.
> >> >>
> >> >>
> >> >>On Wed, Mar 12, 2014 at 11:09 AM, Wilder Rodrigues <
> >> >>wrodrig...@schubergphilis.com> wrote:
> >> >>
> >> >>> Hi guys and gals,
> >> >>>
> >> >>> Based on the findings after my first round of tests, I give a
> >> >>> +1 to
> the
> >> >>> 4.3 RC
> >> >>>
> >> >>> Please, find below what I have tested so far:
> >> >>>
> >> >>> * Environment
> >> >>>   - Management Server: Debian 7 VM under VirtualBox
> >> >>>   - DevCloud: XenServer 6.2
> >> >>>   - MySQL: running on the DevCloud
> >> >>>   - System VM: Latest from
> >> >>>
> http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/
> >> >>>
> >> >>> * Initial start-up
> >> >>>   - Everything seems to work fine
> >> >>>
> >> >>> * Zone
> >> >>>   - DNS1: 8.8.8.8
> >> >>>   - DNS2: 8.8.4.4
> >> >>>   - Hypervisor: XenServer
> >> >>>   - Guest CIDR: 10.1.2.0/24
> >> >>>   - Local Storage enabled: true
> >> >>>
> >> >>> * Public Traffic
> >> >>>   - 10.1.1.1 / 255.255.255.0 / 10.1.1.2 / 10.1.1.100
> >> >>>
> >> >>> * POD
> >> >>>   - 10.1.1.1 / 255.255.255.0 / 10.1.1.101 / 10.1.1.200
> >> >>>
> >> >>> * VLAN
> >> >>>   - 101 - 109
> >> >>>
> >> >>> * Host
> >> >>>   - Host Name: 178.237.34.120
> >> >>>   - Username: root
> >> >>>   - Password: blah
> >> >>>
> >> >>> * Secondary Storage
> >> >>>   - Provider: NFS
> >> >>>   - Name: sec01
> >> >>>   - Server: 10.1.1.114
> >> >>>   - Path: /opt/storage/secondary
> >> >>>
> >> >>> ::: ALL GREEN UP TO NOW :::
> >> >>>
> >> >>> * Create Instance
> >> >>>   - Featured: Tiny Linux
> >> >>>   - Compute Offering: Tiny Offering
> >> >>>   - Disk Offering: None
> >> >>>   - Instance name: cs43-01
> >> >>>
> >> >>> * NIC Information
> >> >>>   - IP Address: 10.1.2.186
> >> >>>   - Gateway: 10.1.2.1
> >> >>>   - Netmask: 255.255.255.0
> >> >>>
> >> >>> * Create Network
> >> >>>   - Name: devcloud-net01
> >> >>>   - Type: Isolated
> >> >>>   - CIDR: 10.1.2.0/24
> >> >>>   - Public IP: 10.1.1.

Build failed in Jenkins: build-master-slowbuild #415

[jenkins]

See 

--
[...truncated 18098 lines...]

Tests run: 4, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi ---
[INFO] Cobertura 2.0.3 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/amazon/ec2/AmazonEC2SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/amazon/s3/AmazonS3SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SAcl.java.  Ensure this class was instrumented, and this 
data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SBucket.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SHost.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/BucketPolicyDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackAccountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackConfigurationDao.java.  Ensure this 
class was instrumented, and this data file contains the instrumentation 
information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackSvcOfferingDao.java.  Ensure this class 
was instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackUserDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostMountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartPartsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartUploadsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultipartMetaDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does 

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

[Nux!]

On 12.03.2014 22:47, Alex Hitchins wrote:

This could also have an impact on adoption of the technology. People
might shy away from a package that changes so frequently.


Precisely. I was hoping Cloudstack to be the RHEL of cloud, not the 
Archlinux, if I may be allowed this metaphor. :)
If people want moving sands, there is that already in the form of 
Openstack.


I realise rolling release may make devs happy, but it would be a 
nightmare for the consumers. From this point of view I loved this RC 
series, good proper testing and rigour went into it, the kind of things 
that make people confident in a product.


imho
Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

RE: Affinity Groups and Project

[Prachi Damle]

Yes Affinity Groups feature does not support projects. This is mentioned in the 
FS for that feature, check the FAQ part
https://cwiki.apache.org/confluence/display/CLOUDSTACK/FS+-+Affinity-Anti-affinity+groups


You should probably log a ticket to change the display result for project view.

Thanks,
Prachi

-Original Message-
From: Saksham Srivastava [mailto:saksham.srivast...@citrix.com] 
Sent: Wednesday, March 12, 2014 3:07 AM
To: dev@cloudstack.apache.org
Subject: RE: Affinity Groups and Project

Can you provide more logs, you can upload them on pastebin.

Thanks,
Saksham

-Original Message-
From: zcsu [mailto:szc...@hotmail.com] 
Sent: Wednesday, March 12, 2014 3:15 PM
To: dev@cloudstack.apache.org
Subject: Affinity Groups and Project

Question: Whether Project can not support Affinity Groups?
Environment: CS4.2 + Xenserver6.2
   Advance Zone
Step:
1.  I set a host as dedicated host to an account, affinity groups will 
auto create a affinity groups with type ExplicitDedication .
 2. Then I create a Project and add the account has dedicated host.
 
when I try creat a VM in Project view, I can select affinity groups has been 
auto created. but created VM will failed with error "Entity AffinityGroup 
[dc4751ao-d2cb-463e-8351-384b9422313] and entity acct 
[3f526aid-d9ab-40ec-a6a5-9b61c84cb1el-PrjAcct-CPSM-1] belong to different 
accounts"
 
Note: I also try to create new affinity groups in project ,the same error 
happend.
 
So  Project can not use Affinity Groups? If is yes, why affinity group display 
in project view?
 
Anybody can answer, very thanks!
 
 
 
 
  

[CANCELLED] [VOTE] Apache CloudStack 4.3.0 (seventh round)

[Animesh Chaturvedi]

Cancelling this VOTE because of issues called out by Daan and Paul and off to 
building another RC

From: Animesh Chaturvedi
Sent: Monday, March 10, 2014 8:00 PM
To: dev@cloudstack.apache.org
Subject: [VOTE] Apache CloudStack 4.3.0 (seventh round)



Hi All,



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

vote:





Git Branch and Commit SH:

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



List of changes:

New Features in 4.3: https://issues.apache.org/jira/issues/?filter=12325248

Improvement in 4.3: https://issues.apache.org/jira/issues/?filter=12325249

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

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







Source release (checksums and signatures are available at the same

location):

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



PGP release keys (signed using 94BE0D7C):

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



Testing instructions are here:

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



Vote will be open for 36 hours (Thursday evening PST 8:00 PM)



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)

Guidelines for writing/modifying CS APIs

[Alena Prokharchyk]

I’ve created a wiki page under Development 101 explaining all the rules that 
have to be followed when writing new CS Apis/modifying existing ones:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+API+Coding+Guidelines

The page emphasizes what rules to follow to ensure the backwards compatibility 
as well as:


  *   CS API name conventions
  *   where to place and how register/set permissions for the API request 
deepening if your command comes as a part of CS core or third party 
plugin/service
  *   How to annotate Command/Response and its parameters

Please feel free to update the page with more rules to follow. In the future, 
we might automate the process of reviewing new APIs and modifications for 
existing ones, to ensure the backwards compatibility.

-Alena.

Review Request 19163: Adding some more parameter names that should not be considered unknown since they belong to general use parameters

[Antonio Fornie]

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

Review request for cloudstack and Alena Prokharchyk.


Repository: cloudstack-git


Description
---

Adding some more parameter names that should not be considered unknown since 
they belong to general use parameters


Diffs
-

  api/src/org/apache/cloudstack/api/ApiConstants.java 0a3fafd 
  server/src/com/cloud/api/dispatch/ParamGenericValidationWorker.java f456468 
  server/test/com/cloud/api/dispatch/ParamGenericValidationWorkerTest.java 
0803a2b 

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


Testing
---

Full maven build including Junit Tests (updated)


Thanks,

Antonio Fornie

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

[Mike Tutkowski]

Right, I agree - in theory - one could release even daily, if one had the
automation in place (build, package, test, etc.) to support such a desire.

However, from a practical standpoint, I don't think end users would
appreciate that approach much.

I think a four-month schedule is fine - if we can hold to it with good
quality.

Overlapping releases is a bit problematic in that it encourages developers
to focus on the future release (such as this week) versus the past one
that's not yet out.


On Wed, Mar 12, 2014 at 5:08 PM, Nux!  wrote:

> On 12.03.2014 22:47, Alex Hitchins wrote:
>
>> This could also have an impact on adoption of the technology. People
>> might shy away from a package that changes so frequently.
>>
>
> Precisely. I was hoping Cloudstack to be the RHEL of cloud, not the
> Archlinux, if I may be allowed this metaphor. :)
> If people want moving sands, there is that already in the form of
> Openstack.
>
> I realise rolling release may make devs happy, but it would be a nightmare
> for the consumers. From this point of view I loved this RC series, good
> proper testing and rigour went into it, the kind of things that make people
> confident in a product.
>
> imho
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>



-- 
*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: [VOTE] Apache CloudStack 4.3.0 (seventh round)

[Mike Tutkowski]

Hey Daan,

I'm trying to understand this paragraph:

"with n releases there are n*(n-1) potential conficts of the simlest
kind and n*(n-1)(n-2) potential conflicts of a slightly mor complex
kind... The higher n ... do the math. The more we postpone a feature
freeze the higher n will get. And that is only talking of features.
not about the simpler fixes that are added."

I'm not following what it means. Can you define what n is? What do you mean
by a conflict of the simplest kind? Of a slightly more complex kind?

Thanks! I'm just curious what you were referring to here.

Talk to you later!
Mike


On Wed, Mar 12, 2014 at 3:10 PM, Daan Hoogland wrote:

> Steve,
>
> As I have suggested before, we shoud not lengthen releas periods but
> shorten them. I highly object to the idea of enlarging the window and
> the release. It will pnly make relasing more difficult.
>
> with n releases there are n*(n-1) potential conficts of the simlest
> kind and n*(n-1)(n-2) potential conflicts of a slightly mor complex
> kind... The higher n ... do the math. The more we postpone a feature
> freeze the higher n will get. And that is only talking of features.
> not about the simpler fixes that are added.
>
> postponing when we have difficulty releasing quality makes no sense.
>
> kind regards,
> Daan Hoogland
>
> On Wed, Mar 12, 2014 at 9:46 PM, Steve Wilson 
> wrote:
> > I think it was suggested multiple times that we push out the 4.4 freeze
> > date because the 4.3 work has been lagging.  I think this is just another
> > indicator we need to evaluate our release cadence as a community.
> >
> > That being said, I don¹t think we want to hold 4.3 any further.  This
> must
> > be the best tested RC in the history of software at this point.  Unless
> > someone finds a new showstopper (that wasn¹t in the previous 6 builds!)
> > then let¹s get this puppy out! :-)
> >
> > -Steve
> >
> > On 3/12/14, 10:25 AM, "Mike Tutkowski" 
> > wrote:
> >
> >>I hate to point this out as I know we've been struggling to get 4.3 out
> >>the
> >>door, but this week is probably not a great week to count votes for 4.3
> as
> >>it is the last week before 4.4 Feature Freeze.
> >>
> >>
> >>On Wed, Mar 12, 2014 at 11:09 AM, Wilder Rodrigues <
> >>wrodrig...@schubergphilis.com> wrote:
> >>
> >>> Hi guys and gals,
> >>>
> >>> Based on the findings after my first round of tests, I give a +1 to the
> >>> 4.3 RC
> >>>
> >>> Please, find below what I have tested so far:
> >>>
> >>> * Environment
> >>>   - Management Server: Debian 7 VM under VirtualBox
> >>>   - DevCloud: XenServer 6.2
> >>>   - MySQL: running on the DevCloud
> >>>   - System VM: Latest from
> >>> http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/
> >>>
> >>> * Initial start-up
> >>>   - Everything seems to work fine
> >>>
> >>> * Zone
> >>>   - DNS1: 8.8.8.8
> >>>   - DNS2: 8.8.4.4
> >>>   - Hypervisor: XenServer
> >>>   - Guest CIDR: 10.1.2.0/24
> >>>   - Local Storage enabled: true
> >>>
> >>> * Public Traffic
> >>>   - 10.1.1.1 / 255.255.255.0 / 10.1.1.2 / 10.1.1.100
> >>>
> >>> * POD
> >>>   - 10.1.1.1 / 255.255.255.0 / 10.1.1.101 / 10.1.1.200
> >>>
> >>> * VLAN
> >>>   - 101 - 109
> >>>
> >>> * Host
> >>>   - Host Name: 178.237.34.120
> >>>   - Username: root
> >>>   - Password: blah
> >>>
> >>> * Secondary Storage
> >>>   - Provider: NFS
> >>>   - Name: sec01
> >>>   - Server: 10.1.1.114
> >>>   - Path: /opt/storage/secondary
> >>>
> >>> ::: ALL GREEN UP TO NOW :::
> >>>
> >>> * Create Instance
> >>>   - Featured: Tiny Linux
> >>>   - Compute Offering: Tiny Offering
> >>>   - Disk Offering: None
> >>>   - Instance name: cs43-01
> >>>
> >>> * NIC Information
> >>>   - IP Address: 10.1.2.186
> >>>   - Gateway: 10.1.2.1
> >>>   - Netmask: 255.255.255.0
> >>>
> >>> * Create Network
> >>>   - Name: devcloud-net01
> >>>   - Type: Isolated
> >>>   - CIDR: 10.1.2.0/24
> >>>   - Public IP: 10.1.1.4 [Source NAT]
> >>>   - Egress Rules: 0.0.0.0/0 - All
> >>>   - Network Offering: Offering for Isolated networks with Source Nat
> >>> service enabled
> >>>
> >>> * Create ACLs
> >>>   - 10.1.0.0/16 - TCP - 22 - 22
> >>>   - 10.1.0.0/16 - TCP - 443 - 443
> >>>
> >>> * Create Port Forwarding
> >>>   - 22:22 - 22:22 - instance cs43-01 [10.1.2.186]
> >>>   - 443:443 - 443:443 - instance cs43-01 [10.1.2.186]
> >>>
> >>> * SSH into the new instance via the Public IP:
> >>>
> >>> [root@devcloud-wil01 ~]# ssh root@10.1.1.4
> >>> The authenticity of host '10.1.1.4 (10.1.1.4)' can't be established.
> >>> RSA key fingerprint is 02:43:6c:24:c5:79:b6:e2:c8:b7:e8:3c:8d:13:37:91.
> >>> Are you sure you want to continue connecting (yes/no)? yes
> >>> Warning: Permanently added '10.1.1.4' (RSA) to the list of known hosts.
> >>> root@10.1.1.4's password:
> >>> %
> >>> %
> >>> % ls
> >>> ssh-host-dss-key.pub  ssh-host-rsa-key.pub
> >>> % cd /
> >>> % ls
> >>> bin bootdev etc homelib
> >>> lost+found  mnt procrootsbinsys
> >>>tmp
> >>>   

Re: Review Request 18978: Ability to manipulate guest OS mappings

[Nitin Mehta]

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

Ship it!


Ship It!

- Nitin Mehta


On March 12, 2014, 6:48 p.m., Amogh Vasekar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/18978/
> ---
> 
> (Updated March 12, 2014, 6:48 p.m.)
> 
> 
> Review request for cloudstack and Nitin Mehta.
> 
> 
> Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-6217
> 
> https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/CLOUDSTACK-6217
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Add APIs for ability to add new guest OS types, and their hypervisor specific 
> mappings.
> The table guest_os_hypervisor is currently maintained but not used, and the 
> APIs reuse the same.
> 
> 
> Diffs
> -
> 
>   api/src/com/cloud/event/EventTypes.java 
> a5fc0f0f7d3492fc0775b4514e4a9f506acb1ed7 
>   api/src/com/cloud/server/ManagementService.java 
> 5fcf0b5fc5279193db4147607e9919433b2a56db 
>   api/src/com/cloud/storage/GuestOS.java 
> 437cd37d1abaf131e09a294dfabbfe9e901af596 
>   api/src/com/cloud/storage/GuestOSHypervisor.java 
> f022722af04331b3feb9562683efa384b0ce5676 
>   api/src/org/apache/cloudstack/api/ApiCommandJobType.java 
> f27f001f868ffb0b8315f5468e67d2ec67db4306 
>   api/src/org/apache/cloudstack/api/ApiConstants.java 
> 0a3fafda312ab72fea96928e68e37f25790e431c 
>   api/src/org/apache/cloudstack/api/ResponseGenerator.java 
> 1cb53886a7cd4262f6d5636af6679a17f6a86dcd 
>   api/src/org/apache/cloudstack/api/command/admin/guest/AddGuestOsCmd.java 
> PRE-CREATION 
>   
> api/src/org/apache/cloudstack/api/command/admin/guest/AddGuestOsMappingCmd.java
>  PRE-CREATION 
>   
> api/src/org/apache/cloudstack/api/command/admin/guest/ListGuestOsMappingCmd.java
>  PRE-CREATION 
>   api/src/org/apache/cloudstack/api/command/admin/guest/RemoveGuestOsCmd.java 
> PRE-CREATION 
>   
> api/src/org/apache/cloudstack/api/command/admin/guest/RemoveGuestOsMappingCmd.java
>  PRE-CREATION 
>   api/src/org/apache/cloudstack/api/command/admin/guest/UpdateGuestOsCmd.java 
> PRE-CREATION 
>   
> api/src/org/apache/cloudstack/api/command/admin/guest/UpdateGuestOsMappingCmd.java
>  PRE-CREATION 
>   api/src/org/apache/cloudstack/api/response/GuestOsMappingResponse.java 
> PRE-CREATION 
>   client/tomcatconf/commands.properties.in 
> 879c58d63425369eb411325bf6d2fb9d7de9d77a 
>   engine/schema/src/com/cloud/storage/GuestOSHypervisorVO.java 
> 8210abf8c3d3becdc2b7d092a382f4b06123b7dd 
>   engine/schema/src/com/cloud/storage/GuestOSVO.java 
> 57b852953a9fe4caae31043b8a63e1df2ff28f9b 
>   engine/schema/src/com/cloud/storage/dao/GuestOSHypervisorDao.java 
> 651cfb56700857669fcfffd6b134358d2c4bb044 
>   engine/schema/src/com/cloud/storage/dao/GuestOSHypervisorDaoImpl.java 
> be680dc3a50830a9cd17b5cd203cdbc2db3e8936 
>   server/src/com/cloud/api/ApiResponseHelper.java 
> 81bfe21ee819130957a6d3826417c1fdd4deba79 
>   server/src/com/cloud/server/ManagementServer.java 
> 3b5f5ff206a28acaca964b0b4efeeb30c8c05da8 
>   server/src/com/cloud/server/ManagementServerImpl.java 
> 663d4e505c5ff7acb215143bdf67f2e114912710 
>   setup/db/db/schema-430to440.sql ee4cf215fb777fcd46c5715d2b21ffe157692e2a 
> 
> Diff: https://reviews.apache.org/r/18978/diff/
> 
> 
> Testing
> ---
> 
> Tested on local environment on master branch for the APIs, including some 
> edge cases.
> Ran with findbugs and RAT to ensure no errors in added code
> 
> 
> Thanks,
> 
> Amogh Vasekar
> 
>

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

[Paul Angus]

I agree with Alex and would go further and say that the fact that for 4.3 RC7 
the noredist build was broken was an epic fail in the automated testing, which 
needs addressing.

Regards,

Paul Angus
Cloud Architect
S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus
paul.an...@shapeblue.com

-Original Message-
From: Alex Hitchins [mailto:alex.hitch...@shapeblue.com]
Sent: 12 March 2014 22:47
To: dev@cloudstack.apache.org
Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)

This could also have an impact on adoption of the technology. People might shy 
away from a package that changes so frequently.

I think a much more rigorous testing schedule would be a massive help to get 
RC's out the door. If you propose a feature I think part of the spec should be 
testing requirements (not code tests) and some indication of who will be 
performing the testing. Treat it as UAT.

Regards

Alex Hitchins

D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969

alex.hitch...@shapeblue.com

-Original Message-
From: Erik Weber [mailto:terbol...@gmail.com]
Sent: 12 March 2014 22:02
To: dev
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round)

That would require a whole other way of upgrading though. Having to restart all 
system vms every week or two is not something i would look forward to.

On the other side, with more releases it wouldn't be that big issue to miss a 
freeze date, and with fewer new features / improvements it should hopefully 
require less fixes.

--
Erik Weber
12. mars 2014 22:53 skrev "Daan Hoogland" 
følgende:

> If we produce a new feature per week, why not?
>
> On Wed, Mar 12, 2014 at 10:34 PM, Mike Tutkowski
>  wrote:
> > There has to be some minimum boundary, though, right? Otherwise we
> > might
> as
> > well release every week. :)
> >
> >
> > On Wed, Mar 12, 2014 at 3:10 PM, Daan Hoogland
> > >wrote:
> >
> >> Steve,
> >>
> >> As I have suggested before, we shoud not lengthen releas periods
> >> but shorten them. I highly object to the idea of enlarging the
> >> window and the release. It will pnly make relasing more difficult.
> >>
> >> with n releases there are n*(n-1) potential conficts of the simlest
> >> kind and n*(n-1)(n-2) potential conflicts of a slightly mor complex
> >> kind... The higher n ... do the math. The more we postpone a
> >> feature freeze the higher n will get. And that is only talking of features.
> >> not about the simpler fixes that are added.
> >>
> >> postponing when we have difficulty releasing quality makes no sense.
> >>
> >> kind regards,
> >> Daan Hoogland
> >>
> >> On Wed, Mar 12, 2014 at 9:46 PM, Steve Wilson
> >> 
> >> wrote:
> >> > I think it was suggested multiple times that we push out the 4.4
> freeze
> >> > date because the 4.3 work has been lagging.  I think this is just
> another
> >> > indicator we need to evaluate our release cadence as a community.
> >> >
> >> > That being said, I don¹t think we want to hold 4.3 any further.
> >> > This
> >> must
> >> > be the best tested RC in the history of software at this point.
>  Unless
> >> > someone finds a new showstopper (that wasn¹t in the previous 6
> builds!)
> >> > then let¹s get this puppy out! :-)
> >> >
> >> > -Steve
> >> >
> >> > On 3/12/14, 10:25 AM, "Mike Tutkowski"
> >> > 
> >> > wrote:
> >> >
> >> >>I hate to point this out as I know we've been struggling to get
> >> >>4.3
> out
> >> >>the
> >> >>door, but this week is probably not a great week to count votes
> >> >>for
> 4.3
> >> as
> >> >>it is the last week before 4.4 Feature Freeze.
> >> >>
> >> >>
> >> >>On Wed, Mar 12, 2014 at 11:09 AM, Wilder Rodrigues <
> >> >>wrodrig...@schubergphilis.com> wrote:
> >> >>
> >> >>> Hi guys and gals,
> >> >>>
> >> >>> Based on the findings after my first round of tests, I give a
> >> >>> +1 to
> the
> >> >>> 4.3 RC
> >> >>>
> >> >>> Please, find below what I have tested so far:
> >> >>>
> >> >>> * Environment
> >> >>>   - Management Server: Debian 7 VM under VirtualBox
> >> >>>   - DevCloud: XenServer 6.2
> >> >>>   - MySQL: running on the DevCloud
> >> >>>   - System VM: Latest from
> >> >>>
> http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/
> >> >>>
> >> >>> * Initial start-up
> >> >>>   - Everything seems to work fine
> >> >>>
> >> >>> * Zone
> >> >>>   - DNS1: 8.8.8.8
> >> >>>   - DNS2: 8.8.4.4
> >> >>>   - Hypervisor: XenServer
> >> >>>   - Guest CIDR: 10.1.2.0/24
> >> >>>   - Local Storage enabled: true
> >> >>>
> >> >>> * Public Traffic
> >> >>>   - 10.1.1.1 / 255.255.255.0 / 10.1.1.2 / 10.1.1.100
> >> >>>
> >> >>> * POD
> >> >>>   - 10.1.1.1 / 255.255.255.0 / 10.1.1.101 / 10.1.1.200
> >> >>>
> >> >>> * VLAN
> >> >>>   - 101 - 109
> >> >>>
> >> >>> * Host
> >> >>>   - Host Name: 178.237.34.120
> >> >>>   - Username: root
> >> >>>   - Password: blah
> >> >>>
> >> >>> * Secondary Storage
> >> >>>   - Provider: NFS
> >> >>>   - Name: sec01
> >> >>>   - Server: 10.1.1.114
> >> >>>   - Path: /opt/storage/secondary
> >> >>>
> >> >>> ::: ALL GRE