date:20130709


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



server/src/com/cloud/configuration/ConfigurationManagerImpl.java


This should have more meaningful values. I think we spoke about it, 
probably using enums ? 



- Abhinandan Prateek


On July 9, 2013, 5:35 a.m., bharat kumar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12323/
> ---
> 
> (Updated July 9, 2013, 5:35 a.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and Jayapal Reddy.
> 
> 
> Bugs: Cloudstack-32141
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Cloudstack-4241 Adding ip range fails if there are two IP ranges existing in 
> two different CIDRs
> 
> 
> Diffs
> -
> 
>   server/src/com/cloud/configuration/ConfigurationManagerImpl.java 1c973b8 
> 
> Diff: https://reviews.apache.org/r/12323/diff/
> 
> 
> Testing
> ---
> 
> Tested on master-stable
> 
> 
> Thanks,
> 
> bharat kumar
> 
>

Re: Review Request 12109: HAProxy maxconn is not configurable


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



plugins/network-elements/internal-loadbalancer/src/org/apache/cloudstack/network/lb/InternalLoadBalancerVMManagerImpl.java


Put a more meaningful message if you need to log.


- Abhinandan Prateek


On July 1, 2013, 3:55 p.m., bharat kumar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12109/
> ---
> 
> (Updated July 1, 2013, 3:55 p.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and Jayapal Reddy.
> 
> 
> Bugs: Cloudstack-2997
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Cloudstack-2997 HAProxy maxconn is not configurable
> https://issues.apache.org/jira/browse/CLOUDSTACK-2997
> 
> 
> Diffs
> -
> 
>   api/src/com/cloud/offering/NetworkOffering.java 5f522eb 
>   api/src/org/apache/cloudstack/api/ApiConstants.java b43f06c 
>   
> api/src/org/apache/cloudstack/api/command/admin/network/CreateNetworkOfferingCmd.java
>  febb0c3 
>   
> api/src/org/apache/cloudstack/api/command/admin/network/UpdateNetworkOfferingCmd.java
>  ba685a9 
>   core/src/com/cloud/agent/api/routing/LoadBalancerConfigCommand.java 1c1fb91 
>   core/src/com/cloud/network/HAProxyConfigurator.java 29fdf4a 
>   engine/schema/src/com/cloud/offerings/NetworkOfferingVO.java fae315b 
>   
> plugins/network-elements/elastic-loadbalancer/src/com/cloud/network/lb/ElasticLoadBalancerManagerImpl.java
>  b21e8f9 
>   
> plugins/network-elements/internal-loadbalancer/src/org/apache/cloudstack/network/lb/InternalLoadBalancerVMManagerImpl.java
>  2bdb28f 
>   
> plugins/network-elements/internal-loadbalancer/test/org/apache/cloudstack/internallbvmmgr/InternalLBVMManagerTest.java
>  a19a82e 
>   server/src/com/cloud/configuration/Config.java 2b0ffaf 
>   server/src/com/cloud/configuration/ConfigurationManager.java 8db037b 
>   server/src/com/cloud/configuration/ConfigurationManagerImpl.java 97f0d33 
>   server/src/com/cloud/network/NetworkManagerImpl.java 8c2806a 
>   server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java 
> 7f3a88e 
>   server/test/com/cloud/vpc/MockConfigurationManagerImpl.java 21b3590 
>   
> server/test/org/apache/cloudstack/networkoffering/CreateNetworkOfferingTest.java
>  4a2c867 
>   setup/db/db/schema-410to420.sql 181f1cb 
> 
> Diff: https://reviews.apache.org/r/12109/diff/
> 
> 
> Testing
> ---
> 
> Tested on master.
> 
> 
> Thanks,
> 
> bharat kumar
> 
>

Re: Review Request 12109: HAProxy maxconn is not configurable


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



core/src/com/cloud/agent/api/routing/LoadBalancerConfigCommand.java


Max connection should be int ?


- Abhinandan Prateek


On July 1, 2013, 3:55 p.m., bharat kumar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12109/
> ---
> 
> (Updated July 1, 2013, 3:55 p.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and Jayapal Reddy.
> 
> 
> Bugs: Cloudstack-2997
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Cloudstack-2997 HAProxy maxconn is not configurable
> https://issues.apache.org/jira/browse/CLOUDSTACK-2997
> 
> 
> Diffs
> -
> 
>   api/src/com/cloud/offering/NetworkOffering.java 5f522eb 
>   api/src/org/apache/cloudstack/api/ApiConstants.java b43f06c 
>   
> api/src/org/apache/cloudstack/api/command/admin/network/CreateNetworkOfferingCmd.java
>  febb0c3 
>   
> api/src/org/apache/cloudstack/api/command/admin/network/UpdateNetworkOfferingCmd.java
>  ba685a9 
>   core/src/com/cloud/agent/api/routing/LoadBalancerConfigCommand.java 1c1fb91 
>   core/src/com/cloud/network/HAProxyConfigurator.java 29fdf4a 
>   engine/schema/src/com/cloud/offerings/NetworkOfferingVO.java fae315b 
>   
> plugins/network-elements/elastic-loadbalancer/src/com/cloud/network/lb/ElasticLoadBalancerManagerImpl.java
>  b21e8f9 
>   
> plugins/network-elements/internal-loadbalancer/src/org/apache/cloudstack/network/lb/InternalLoadBalancerVMManagerImpl.java
>  2bdb28f 
>   
> plugins/network-elements/internal-loadbalancer/test/org/apache/cloudstack/internallbvmmgr/InternalLBVMManagerTest.java
>  a19a82e 
>   server/src/com/cloud/configuration/Config.java 2b0ffaf 
>   server/src/com/cloud/configuration/ConfigurationManager.java 8db037b 
>   server/src/com/cloud/configuration/ConfigurationManagerImpl.java 97f0d33 
>   server/src/com/cloud/network/NetworkManagerImpl.java 8c2806a 
>   server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java 
> 7f3a88e 
>   server/test/com/cloud/vpc/MockConfigurationManagerImpl.java 21b3590 
>   
> server/test/org/apache/cloudstack/networkoffering/CreateNetworkOfferingTest.java
>  4a2c867 
>   setup/db/db/schema-410to420.sql 181f1cb 
> 
> Diff: https://reviews.apache.org/r/12109/diff/
> 
> 
> Testing
> ---
> 
> Tested on master.
> 
> 
> Thanks,
> 
> bharat kumar
> 
>

Re: Review Request 12109: HAProxy maxconn is not configurable


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



core/src/com/cloud/network/HAProxyConfigurator.java


You need not cast globalSection to a List just do globalSection[2] = 
"\tmaxconn " + lbCmd.maxconn;


- Abhinandan Prateek


On July 1, 2013, 3:55 p.m., bharat kumar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12109/
> ---
> 
> (Updated July 1, 2013, 3:55 p.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and Jayapal Reddy.
> 
> 
> Bugs: Cloudstack-2997
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Cloudstack-2997 HAProxy maxconn is not configurable
> https://issues.apache.org/jira/browse/CLOUDSTACK-2997
> 
> 
> Diffs
> -
> 
>   api/src/com/cloud/offering/NetworkOffering.java 5f522eb 
>   api/src/org/apache/cloudstack/api/ApiConstants.java b43f06c 
>   
> api/src/org/apache/cloudstack/api/command/admin/network/CreateNetworkOfferingCmd.java
>  febb0c3 
>   
> api/src/org/apache/cloudstack/api/command/admin/network/UpdateNetworkOfferingCmd.java
>  ba685a9 
>   core/src/com/cloud/agent/api/routing/LoadBalancerConfigCommand.java 1c1fb91 
>   core/src/com/cloud/network/HAProxyConfigurator.java 29fdf4a 
>   engine/schema/src/com/cloud/offerings/NetworkOfferingVO.java fae315b 
>   
> plugins/network-elements/elastic-loadbalancer/src/com/cloud/network/lb/ElasticLoadBalancerManagerImpl.java
>  b21e8f9 
>   
> plugins/network-elements/internal-loadbalancer/src/org/apache/cloudstack/network/lb/InternalLoadBalancerVMManagerImpl.java
>  2bdb28f 
>   
> plugins/network-elements/internal-loadbalancer/test/org/apache/cloudstack/internallbvmmgr/InternalLBVMManagerTest.java
>  a19a82e 
>   server/src/com/cloud/configuration/Config.java 2b0ffaf 
>   server/src/com/cloud/configuration/ConfigurationManager.java 8db037b 
>   server/src/com/cloud/configuration/ConfigurationManagerImpl.java 97f0d33 
>   server/src/com/cloud/network/NetworkManagerImpl.java 8c2806a 
>   server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java 
> 7f3a88e 
>   server/test/com/cloud/vpc/MockConfigurationManagerImpl.java 21b3590 
>   
> server/test/org/apache/cloudstack/networkoffering/CreateNetworkOfferingTest.java
>  4a2c867 
>   setup/db/db/schema-410to420.sql 181f1cb 
> 
> Diff: https://reviews.apache.org/r/12109/diff/
> 
> 
> Testing
> ---
> 
> Tested on master.
> 
> 
> Thanks,
> 
> bharat kumar
> 
>

Re: Review Request 12273: Cloudstack-2150 DB table entries of phisical network is not proper.Shows Duplicate entries Cloudstack-2980 Adding a VLAN range that overlaps with two existing ranges results


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



server/src/com/cloud/network/NetworkServiceImpl.java


check variable naming convention AddVnet 


- Abhinandan Prateek


On July 5, 2013, 5:35 a.m., bharat kumar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12273/
> ---
> 
> (Updated July 5, 2013, 5:35 a.m.)
> 
> 
> Review request for cloudstack and Abhinandan Prateek.
> 
> 
> Bugs: Cloudstack-2150 and Cloudstack-2980
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Cloudstack-2150 DB table entries of phisical network is not proper.Shows 
> Duplicate entries Cloudstack-2980 Adding a
> VLAN range that overlaps with two existing ranges results inconsistent DB 
> entries
> This fix was causing a regression due to which the state of the physical 
> network was not getting updated and as a result basic zone deployment failed. 
> Resubmitting the fixed code.
> 
> 
> Diffs
> -
> 
>   engine/schema/src/com/cloud/dc/dao/DataCenterVnetDaoImpl.java e97f2c6 
>   server/src/com/cloud/network/NetworkServiceImpl.java f88f600 
> 
> Diff: https://reviews.apache.org/r/12273/diff/
> 
> 
> Testing
> ---
> 
> Tested 
> basic zone deployment.
> adding vlan
> removing vlan
> removing all vlan
> checked if all the added vlans are in the db.
> 
> 
> Thanks,
> 
> bharat kumar
> 
>

Re: Review Request 12273: Cloudstack-2150 DB table entries of phisical network is not proper.Shows Duplicate entries Cloudstack-2980 Adding a VLAN range that overlaps with two existing ranges results


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



server/src/com/cloud/network/NetworkServiceImpl.java


This for loop is not exhaustively taking care of all overlap conditions.



server/src/com/cloud/network/NetworkServiceImpl.java


It is possible that only a part of the VLAN range may pre-exist here.

Minor note: newVnetRangeString  String in variable name is sort of 
redundant.



server/src/com/cloud/network/NetworkServiceImpl.java


newEndVnet+1 >= existingStartVnet  is equivalent to newEndVnet > 
existingStartVnet



server/src/com/cloud/network/NetworkServiceImpl.java


Why initialize two diff variables with similar values ?


- Abhinandan Prateek


On July 5, 2013, 5:35 a.m., bharat kumar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12273/
> ---
> 
> (Updated July 5, 2013, 5:35 a.m.)
> 
> 
> Review request for cloudstack and Abhinandan Prateek.
> 
> 
> Bugs: Cloudstack-2150 and Cloudstack-2980
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Cloudstack-2150 DB table entries of phisical network is not proper.Shows 
> Duplicate entries Cloudstack-2980 Adding a
> VLAN range that overlaps with two existing ranges results inconsistent DB 
> entries
> This fix was causing a regression due to which the state of the physical 
> network was not getting updated and as a result basic zone deployment failed. 
> Resubmitting the fixed code.
> 
> 
> Diffs
> -
> 
>   engine/schema/src/com/cloud/dc/dao/DataCenterVnetDaoImpl.java e97f2c6 
>   server/src/com/cloud/network/NetworkServiceImpl.java f88f600 
> 
> Diff: https://reviews.apache.org/r/12273/diff/
> 
> 
> Testing
> ---
> 
> Tested 
> basic zone deployment.
> adding vlan
> removing vlan
> removing all vlan
> checked if all the added vlans are in the db.
> 
> 
> Thanks,
> 
> bharat kumar
> 
>

Re: Review Request 12273: Cloudstack-2150 DB table entries of phisical network is not proper.Shows Duplicate entries Cloudstack-2980 Adding a VLAN range that overlaps with two existing ranges results


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



server/src/com/cloud/network/NetworkServiceImpl.java


What is this for loop trying to do ?


- Abhinandan Prateek


On July 5, 2013, 5:35 a.m., bharat kumar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12273/
> ---
> 
> (Updated July 5, 2013, 5:35 a.m.)
> 
> 
> Review request for cloudstack and Abhinandan Prateek.
> 
> 
> Bugs: Cloudstack-2150 and Cloudstack-2980
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Cloudstack-2150 DB table entries of phisical network is not proper.Shows 
> Duplicate entries Cloudstack-2980 Adding a
> VLAN range that overlaps with two existing ranges results inconsistent DB 
> entries
> This fix was causing a regression due to which the state of the physical 
> network was not getting updated and as a result basic zone deployment failed. 
> Resubmitting the fixed code.
> 
> 
> Diffs
> -
> 
>   engine/schema/src/com/cloud/dc/dao/DataCenterVnetDaoImpl.java e97f2c6 
>   server/src/com/cloud/network/NetworkServiceImpl.java f88f600 
> 
> Diff: https://reviews.apache.org/r/12273/diff/
> 
> 
> Testing
> ---
> 
> Tested 
> basic zone deployment.
> adding vlan
> removing vlan
> removing all vlan
> checked if all the added vlans are in the db.
> 
> 
> Thanks,
> 
> bharat kumar
> 
>

Re: Review Request 12251: Incorporating the review comments given by Alena and Sheng


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



server/src/com/cloud/configuration/ConfigurationManagerImpl.java


You can remove the catch as you jurt rethrow the caught exception.


- Abhinandan Prateek


On July 8, 2013, 5:47 p.m., bharat kumar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12251/
> ---
> 
> (Updated July 8, 2013, 5:47 p.m.)
> 
> 
> Review request for cloudstack, Alena Prokharchyk, Abhinandan Prateek, and 
> Sheng Yang.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Incorporating the review comments given by Alena and Sheng.
> 
> 
> Diffs
> -
> 
>   engine/schema/src/com/cloud/network/dao/IPAddressDao.java 3eba6d8 
>   engine/schema/src/com/cloud/network/dao/IPAddressDaoImpl.java 1051b69 
>   server/src/com/cloud/configuration/ConfigurationManagerImpl.java 27c1a51 
> 
> Diff: https://reviews.apache.org/r/12251/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> bharat kumar
> 
>

Review Request 12358: CLOUDSTACK-3228: system vms are not comming up in zone with two cluster xen and kvm

2013-07-09 Thread Harikrishna Patnala


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

Review request for cloudstack.


Bugs: CLOUDSTACK-3228


Repository: cloudstack-git


Description
---

CLOUDSTACK-3228: system vms are not comming up in zone with two cluster xen and 
kvm;Zone host is ready, but secondary storage vm template: 3 is not ready on 
secondary storage: 2

Shuffling the hypervisors list before getting the first hypervisor in list so 
that on every retry of system vm deployment it chooses different hypervisor and 
checking whether template is downloaded or not.


Diffs
-

  
plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/XenServer56FP1Resource.java
 407f069 
  server/src/com/cloud/consoleproxy/ConsoleProxyManagerImpl.java 5983aa7 
  server/src/com/cloud/resource/ResourceManagerImpl.java 41c6ad7 
  server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java 
05256a8 

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


Testing
---

tested locally


Thanks,

Harikrishna Patnala

Re: Review Request 12358: CLOUDSTACK-3228: system vms are not comming up in zone with two cluster xen and kvm

2013-07-09 Thread Harikrishna Patnala


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

(Updated July 9, 2013, 10:34 a.m.)


Review request for cloudstack, Abhinandan Prateek and Nitin Mehta.


Bugs: CLOUDSTACK-3228


Repository: cloudstack-git


Description
---

CLOUDSTACK-3228: system vms are not comming up in zone with two cluster xen and 
kvm;Zone host is ready, but secondary storage vm template: 3 is not ready on 
secondary storage: 2

Shuffling the hypervisors list before getting the first hypervisor in list so 
that on every retry of system vm deployment it chooses different hypervisor and 
checking whether template is downloaded or not.


Diffs
-

  
plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/XenServer56FP1Resource.java
 407f069 
  server/src/com/cloud/consoleproxy/ConsoleProxyManagerImpl.java 5983aa7 
  server/src/com/cloud/resource/ResourceManagerImpl.java 41c6ad7 
  server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java 
05256a8 

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


Testing
---

tested locally


Thanks,

Harikrishna Patnala

Re: Review Request 12251: Incorporating the review comments given by Alena and Sheng


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


Can you create a new patch that consolidates all these changes and resubmit. 

- Abhinandan Prateek


On July 8, 2013, 5:47 p.m., bharat kumar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12251/
> ---
> 
> (Updated July 8, 2013, 5:47 p.m.)
> 
> 
> Review request for cloudstack, Alena Prokharchyk, Abhinandan Prateek, and 
> Sheng Yang.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Incorporating the review comments given by Alena and Sheng.
> 
> 
> Diffs
> -
> 
>   engine/schema/src/com/cloud/network/dao/IPAddressDao.java 3eba6d8 
>   engine/schema/src/com/cloud/network/dao/IPAddressDaoImpl.java 1051b69 
>   server/src/com/cloud/configuration/ConfigurationManagerImpl.java 27c1a51 
> 
> Diff: https://reviews.apache.org/r/12251/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> bharat kumar
> 
>

Re: Review Request 12358: CLOUDSTACK-3228: system vms are not comming up in zone with two cluster xen and kvm


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



server/src/com/cloud/consoleproxy/ConsoleProxyManagerImpl.java


Though this is a old comment, it is misleading, please provide a better 
error message.


- Abhinandan Prateek


On July 9, 2013, 10:34 a.m., Harikrishna Patnala wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12358/
> ---
> 
> (Updated July 9, 2013, 10:34 a.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and Nitin Mehta.
> 
> 
> Bugs: CLOUDSTACK-3228
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-3228: system vms are not comming up in zone with two cluster xen 
> and kvm;Zone host is ready, but secondary storage vm template: 3 is not ready 
> on secondary storage: 2
> 
> Shuffling the hypervisors list before getting the first hypervisor in list so 
> that on every retry of system vm deployment it chooses different hypervisor 
> and checking whether template is downloaded or not.
> 
> 
> Diffs
> -
> 
>   
> plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/XenServer56FP1Resource.java
>  407f069 
>   server/src/com/cloud/consoleproxy/ConsoleProxyManagerImpl.java 5983aa7 
>   server/src/com/cloud/resource/ResourceManagerImpl.java 41c6ad7 
>   server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java 
> 05256a8 
> 
> Diff: https://reviews.apache.org/r/12358/diff/
> 
> 
> Testing
> ---
> 
> tested locally
> 
> 
> Thanks,
> 
> Harikrishna Patnala
> 
>

Re: cloudstack 4.1 QinQ vlan behaviour

2013-07-09 Thread Valery Ciareszka

So, nobody uses q in q and cloudstack 4.1 ?

On Mon, Jul 8, 2013 at 3:13 PM, Valery Ciareszka
wrote:

> Hi all,
>
> I use the following environment: CS 4.1, KVM, Centos 6.4
> (management+node1+node2), OpenIndiana NFS server as primary and secondary
> storage
> I have advanced networking in zone. I split management/public/guest
> traffic into different vlans, and use kvm network labels (bridge names):
> # cat /etc/cloud/agent/agent.properties |grep device
> guest.network.device=cloudbrguest
> private.network.device=cloudbrmanage
> public.network.device=cloudbrpublic
>
> I have following network configuration:
> eth0+eth1=bond0
> eth2+eth3=bond1
>
> I use  vlan with id=211 on bond1 interface for guest traffic:
> cloudbrguest8000.90e2ba317614   yes vlan211
> cloudbrmanage   8000.90e2ba317614   yes bond1.210
> cloudbrpublic   8000.90e2ba317614   yes bond1.221
> cloudbrstor 8000.0025908814a4   yes bond0
>
>
> The problem appeared after I have upgraded CS from 4.0.2 to 4.1.
>
> How it works in 4.0.2:
> -bridge interface cloudVirBr#VLANID is created on hypervisor, #VLANID -
> value from 1024 to 4096(is specified when creating zone), i.e.
> cloudVirBr1224
> -vlan interface vlan211.#VLANID is created on hypervisor and is plugged
> into cloudVirBr#VLANID
> I should had permitted 211 vlanid on switchports and all guest traffic
> (vlans 1024-4096) was encapsulated.
>
> How it works in 4.1:
> -bridge interface br#ETHNAME-#VLANID is created on hypervisor, where
> #VLANID - value from 1024 to 4096(is specified when creating zone) and
> #ETHNAME - name of device on top of which vlan will be created
> i.e. brbond1-1224
> -vlan interface bond1.#VLANID is created on hypervisor and is plugged into
> br#ETHNAME-#VLANID
> However, vlan interface is created on top of bond1 interface, while I
> would like it to be created on top of vlan211 (bond1.211)
> Now I should permit 1024-4096 vlanid on switchports, that is not
> convenient.
>
> How do I configure CS 4.1 so that it could work with guest vlans the same
> way as it had worked in CS 4.0 ?
>
> --
> Regards,
> Valery
>
> http://protocol.by/slayer
>



-- 
Regards,
Valery

http://protocol.by/slayer

Re: Review Request 11906: CLOUDSTACK-1047: tracking in logs using job id

2013-07-09 Thread Devdeep Singh


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


Patch doesn't apply cleanly on master. Can you verify and share an updated 
patch.

- Devdeep Singh


On July 1, 2013, 2:50 p.m., Sanjay Tripathi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/11906/
> ---
> 
> (Updated July 1, 2013, 2:50 p.m.)
> 
> 
> Review request for cloudstack, Alex Huang, Devdeep Singh, and Nitin Mehta.
> 
> 
> Bugs: CLOUDSTACK-1047
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-1047: tracking in logs using job id
> 
> https://issues.apache.org/jira/browse/CLOUDSTACK-1047
> 
> 
> Diffs
> -
> 
>   server/src/com/cloud/async/AsyncJobManagerImpl.java 0101a8a 
>   server/src/com/cloud/storage/VolumeManagerImpl.java 4297efb 
> 
> Diff: https://reviews.apache.org/r/11906/diff/
> 
> 
> Testing
> ---
> 
> Tests:
> 1. Deploy an Instance.
> 2. In the Management server logs, check the async job description, it should 
> be somthing like: job-[ 22 ] = [ 1075d499-03a8-44c3-ac9e-348dc5b32ba1 ]
> 
> 
> Thanks,
> 
> Sanjay Tripathi
> 
>

How to evaluate performance of a resource allocation policy?

2013-07-09 Thread Linux TUX

Hello All,


As you know, evaluating performance of a resource allocation policy for a cloud 
environment is very important, also it is critical to be able to compare 
different policies' performance with each other. So, I am interested to know 
that do developers of CloudStack use any specific tool to simulate a [new] 
resource allocation policy?


I think it is not reasonable to use a real testbed for every single idea during 
the developing phase. Furthermore, comparing different policies to each other 
(using dependable simulators) can be used a basis to provide benchmarking 
results. Needless to say, by using simulator, I do not mean providing results 
using trial and error.

Best regards,
Pouya

cloudstack-installation

I am trying to install cloudstack following the steps given in the INSTALL.md 
file which is there with the cloudstack release.

However I have been unsuccessful. I am trying to download maven, but all the 
mirrors say "Page Not Found".

Then I am trying to get the KEYS File, but it opens up in a new tab. From where 
can I download it?
Is there any specific directory where I should save it?

Regards,
Gaurav

RE: Unable to start secondary storage in DevCloud

2013-07-09 Thread Tariq Iqbal

Hi Syed,

You could try increasing the overprovisiong factor for storage 
(storage.overprovisioning.factor). You'll find it under Global Settings -> 
search for 'factor'

storage.overprovisioning.factor

There is also the CPU and Memory over provisioning factors there as well.

Once you change any of these settings, you will need to restart the cloudstack 
managemeent service for the changes to take affect.

Kind Regards,
Tariq Iqbal
Senior Consultant

S: +44(0)20 3603 0540 | M: +44(0)790 9911600
tariq.iq...@shapeblue.com | www.shapeblue.com | Twitter:@shapeBlue

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS



From: Syed Mushtaq
Sent: 09 July 2013 04:42
To: dev@cloudstack.apache.org
Subject: Unable to start secondary storage in DevCloud

Hi,

I was trying to setup DevCloud by following
https://cwiki.apache.org/confluence/display/CLOUDSTACK/DevCloud on my
ubuntu machine. I have the xenserver vm running and I see that the
secondary storage is being exported as NFS and I am able to mount it on the
host machine. However it is not being picked up by cloudstack. I get the
InsufficientServerCapacityException exception. I have given 4GB of RAM and
4 CPU cores to the VM. Can you guys please help me figure this out? Here is
the complete stacktrace from the log


WARN  [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:)
Exception while trying to start secondary storage vm
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[SecondaryStorageVm|s-109-VM]Scope=interface
com.cloud.dc.DataCenter; id=1
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:820)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550)
at
com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:260)
at
com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:683)
at
com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1290)
at
com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123)
at
com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50)
at
com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104)
at
com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33)
at
com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81)
at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
INFO  [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:)
Unable to start secondary storage vm for standby capacity, secStorageVm vm
Id : 109, will recycle it and start a new one


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

Re: Unable to start secondary storage in DevCloud

2013-07-09 Thread Syed

Thanks for your reply Tariq. I fiddled around with the settings a bit 
but the problem still persisted. I then saw that the primary storage 
was scoped for the HOST instead of CLUSTER or ZONE. I added one more 
primary storage and then restarted management server and the secondary 
storage came up. Though I do not know if it was the combination of the 
over-provisioning settings and adding primary storage. But still that 
is some progress :) I am now getting a different message of console 
proxy manager not being able to start because of insufficient capacity. 
What does this VM do? Do you have any settings to recommend that I can 
fiddle around and make this VM come up though I do not know what 
exactly this is used for.


Thanks for your help. I was able to get something working.

Thanks
-Syed



WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:) 
Exception while trying to start console proxy
com.cloud.exception.InsufficientServerCapacityException: Unable to 
create a deployment for VM[ConsoleProxy|v-40-VM]Scope=interface 
com.cloud.dc.DataCenter; id=1
	at 
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:820)
	at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
	at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550)
	at 
com.cloud.consoleproxy.ConsoleProxyManagerImpl.startProxy(ConsoleProxyManagerImpl.java:556)
	at 
com.cloud.consoleproxy.ConsoleProxyManagerImpl.allocCapacity(ConsoleProxyManagerImpl.java:927)
	at 
com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:1664)
	at 
com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:157)
	at 
com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111)
	at 
com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33)
	at 
com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81)

at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72)
	at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at 
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)

at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
	at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
	at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

at java.lang.Thread.run(Thread.java:724)



On Tue 09 Jul 2013 09:12:14 AM EDT, Tariq Iqbal wrote:

Hi Syed,

You could try increasing the overprovisiong factor for storage 
(storage.overprovisioning.factor). You'll find it under Global Settings -> 
search for 'factor'

storage.overprovisioning.factor

There is also the CPU and Memory over provisioning factors there as well.

Once you change any of these settings, you will need to restart the cloudstack 
managemeent service for the changes to take affect.

Kind Regards,
Tariq Iqbal
Senior Consultant

S: +44(0)20 3603 0540 | M: +44(0)790 9911600
tariq.iq...@shapeblue.com | www.shapeblue.com | Twitter:@shapeBlue

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS



From: Syed Mushtaq
Sent: 09 July 2013 04:42
To: dev@cloudstack.apache.org
Subject: Unable to start secondary storage in DevCloud

Hi,

I was trying to setup DevCloud by following
https://cwiki.apache.org/confluence/display/CLOUDSTACK/DevCloud on my
ubuntu machine. I have the xenserver vm running and I see that the
secondary storage is being exported as NFS and I am able to mount it on the
host machine. However it is not being picked up by cloudstack. I get the
InsufficientServerCapacityException exception. I have given 4GB of RAM and
4 CPU cores to the VM. Can you guys please help me figure this out? Here is
the complete stacktrace from the log


WARN  [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:)
Exception while trying to start secondary storage vm
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[SecondaryStorageVm|s-109-VM]Scope=interface
com.cloud.dc.DataCenter; id=1
 at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:820)
 at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
 at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550)
 at
com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:260)
 at
com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:683)
 at
com.cloud.storage.secondary.SecondaryStorageM

question about migrate VMs from xenserver 6.1 to cloudstack 3.0.2/4.1

2013-07-09 Thread William Jiang

Hi,
We have a xenserver 6.1 pool with 6 hosts, there are total about 90 VMs. Some 
with one disk and others with 2 disk on NFS shared storage.
In the meanwhile, we have a cloudstack 3.0.2 with xenserver 6.0.2 hosts.(we had 
plan of upgrading to cloudstack 4.1&xenserver 6.1 soon) The storage is on iscsi.

My question is:
If I want move all the vms on xenserver pool to cloudstack, if there is a way 
for fast migration?
Or I have to migrate one by one?
For my understanding, I need export each vm in xenserver, then import it to 
cloudstack as template, and create instance from the imported template.
But in this process, it works only for one-disk vms, how about the vms with 2 
disks?
Any comments or suggestions will be greatly appreciated.

Thanks,
William
This e-mail may be privileged and/or confidential, and the sender does not 
waive any related rights and obligations. Any distribution, use or copying of 
this e-mail or the information it contains by other than an intended recipient 
is unauthorized. If you received this e-mail in error, please advise me (by 
return e-mail or otherwise) immediately. Ce courrier électronique est 
confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations 
qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des 
renseignements qu'il contient par une personne autre que le (les) 
destinataire(s) désigné(s) est interdite. Si vous recevez ce courrier 
électronique par erreur, veuillez m'en aviser immédiatement, par retour de 
courrier électronique ou par un autre moyen.

Re: How to evaluate performance of a resource allocation policy?

On Tue, Jul 09, 2013 at 04:40:37AM -0700, Linux TUX wrote:
> Hello All,
> 
> 
> As you know, evaluating performance of a resource allocation policy for a 
> cloud environment is very important, also it is critical to be able to 
> compare different policies' performance with each other. So, I am interested 
> to know that do developers of CloudStack use any specific tool to simulate a 
> [new] resource allocation policy?
> 
> 
> I think it is not reasonable to use a real testbed for every single idea 
> during the developing phase. Furthermore, comparing different policies to 
> each other (using dependable simulators) can be used a basis to provide 
> benchmarking results. Needless to say, by using simulator, I do not mean 
> providing results using trial and error.
> 
> Best regards,
> Pouya

Consider using the simulator plugin, which will simulate hosts.  You can
follow the testing instructions on the Marvin testing page [1], but
modify your setup to implement whatever number of hosts you want to test
against.  From there, you would need to modify the allocator that's
enabled.

-chip

[1] 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python

Re: Using the ACS simulator for jclouds "live" tests - some questions. =)

On Tue, Jul 09, 2013 at 01:44:26AM +, Edison Su wrote:
> The simulator issue should be fixed on 4.2 branch.

Do you mind pulling those changes into master?

Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?

Edison,

As I read through this thread, we seem to be conflating the following topics:

1. Feature regression testing per release cycle
2. Identifying and back porting defect fixes to previous releases
3. Feature removal process

To my mind, these topics are completely unrelated.  We have regression test and 
defect triage processes to address items 1 and 2.  If you feel that they can be 
improved, then we should discuss those improvements in a separate thread.  No 
community or system will be perfect.  I believe the best we can do is seek to 
do it better today than yesterday.  To that end, observing that we did 
something poorly in the past does not justify continuing to do it poorly or 
removing a feature on which users are relying.  

I am concerned about item 3 -- the merge of a feature removal without community 
consensus.  If you *think* a feature is broken in a previous release, test it 
and lodge defects or request help to regression test it.  We have a maintenance 
release cycle through which we can address these types of defects.  As I stated 
previously, existing feature defects are not a justification to remove that 
feature.

Thanks,
-John

On Jul 8, 2013, at 7:35 PM, Edison Su  wrote:

> And I want to point out, that, it's easy to say this feature and that feature 
> are supported in certain release, but without fully tested for each release, 
> only God will know the status.
> For example, there is a bug in 4.2: 
> https://issues.apache.org/jira/browse/CLOUDSTACK-2583, it says can't backup 
> snapshot from primary storage into S3 if the hypervisor is xenserver. 
> It's fired for 4.2, but actually, 4.1 will have the same issue.
> Will we claim, to support S3 in 4.1, while the major functionality of S3 is 
> broken?
> 
>> -Original Message-
>> From: John Burwell [mailto:jburw...@basho.com]
>> Sent: Monday, July 08, 2013 1:42 PM
>> To: dev@cloudstack.apache.org
>> Cc: 'Chip Childers'
>> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?
>> 
>> All,
>> 
>> I apologize for losing track of this issue.  We discussed the lack of Swift
>> support briefly in late May/early June as part of the first round review, 
>> but I
>> completely lost track of it in the sea of items being addressed.
>> 
>> This gap represents a feature deprecation without any community discussion.
>> A lack of code changes or test requests for a feature does not translate to 
>> no
>> usage.  It also does not provide license for a feature to be dropped without
>> community discussion and consensus.
>> 
>> In summary, post merge is not the time to be asking this question.  I am
>> concerned about the precedent this action will set in future release cycles.
>> Furthermore, re-implementation of a feature should be complete.  To me, it
>> is not acceptable to say, "I re-implemented the functionality with which I 
>> was
>> familiar.  Hey, community, if you like those other parts, you will need to 
>> fill in
>> the gaps."  To my mind, a feature re-implementation should not be
>> acceptable until it implements all of the capabilities it is replacing.
>> 
>> Thanks,
>> -John
>> 
>> On Jul 8, 2013, at 1:30 PM, Sudha Ponnaganti 
>> wrote:
>> 
>>> Swift was tested for older version of Citrix release. There were  no code
>> changes or certification requests, so that area was deprioritized.
>>> 
>>> Thanks
>>> /Sudha
>>> 
>>> -Original Message-
>>> From: Edison Su [mailto:edison...@citrix.com]
>>> Sent: Monday, July 08, 2013 10:15 AM
>>> To: 'Chip Childers'; 
>>> Subject: RE: Swift in 4.2 is broken, anybody wants it to be supported in 
>>> 4.2?
>>> 
>>> 
>>> 
 -Original Message-
 From: Chip Childers [mailto:chip.child...@sungard.com]
 Sent: Monday, July 08, 2013 6:46 AM
 To: ; Edison Su
 Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 
 4.2?
 
 On Mon, Jul 8, 2013 at 9:22 AM, David Nalley  wrote:
> On Wed, Jul 3, 2013 at 5:29 PM, Edison Su  wrote:
>> Due to object store refactor, Swift is broken. The reason, is that,
>> we only
 have S3 test environment in our lab, so only S3 is tested for now.
>> Before adding the feature back, I'd better ask from, the community,
>> do
 we want to support Swift? If so, which version of Swift? This will
 take some efforts to support Swift, are there any volunteers can help the
>> integration?
> 
> 
> Whats the bug ID for this?
> Unplanned/Unannounced deprecation of a feature is a blocker IMO. It
> engenders a bad relationship with our users, and strands them on
> previous versions with no good migration/upgrade path.
> 
> --David
> 
 
 Edison, How broken is it?  Is it shorter to fix or revert the object
 store changes?
>>> It's not working at all. Not sure, revert object store will change it or 
>>> not, as
>> this feature is not tested by QA for a long time.
>>> 
>

Re: cloudstack-installation

On Tue, Jul 09, 2013 at 05:09:06AM -0700, gaurav jain wrote:
> I am trying to install cloudstack following the steps given in the INSTALL.md 
> file which is there with the cloudstack release.
> 
> However I have been unsuccessful. I am trying to download maven, but all the 
> mirrors say "Page Not Found".
> 
> Then I am trying to get the KEYS File, but it opens up in a new tab. From 
> where can I download it?
> Is there any specific directory where I should save it?
> 
> Regards,
> Gaurav

Honestly, we should delete the INSTALL.txt file.  The best instructions
can be found here:

http://cloudstack.apache.org/docs/en-US/index.html

Select the install guide for the version you are
working with.

Re: Review Request 12184: Fix for defect CLOUDSTACK-2927


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


Commit 48d2525f477bf2f2b22b9baabc44c93a10f6d725 in branch 
refs/heads/master-6-17-stable from Rayeesn
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=48d2525 ]

Adding axis2.xml to cloudstack-bridge/webapps/awsapi/WEB-INF/conf as part of 
defect CLOUDSTACK-2927


- ASF Subversion and Git Services


On June 29, 2013, 12:28 a.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12184/
> ---
> 
> (Updated June 29, 2013, 12:28 a.m.)
> 
> 
> Review request for cloudstack and Prachi Damle.
> 
> 
> Bugs: CLOUDSTACK-2927
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Updated cloud.spec to package from  awsapi/resource/Axis2/axis2.xml  
> cloudstack-bridge/webapps/awsapi/WEB-INF/conf
> 
> 
> Diffs
> -
> 
> 
> Diff: https://reviews.apache.org/r/12184/diff/
> 
> 
> Testing
> ---
> 
> tested 
> 
> 
> File Attachments
> 
> 
> File added
>   
> https://reviews.apache.org/media/uploaded/files/2013/06/29/0001-Adding-axis2.xml-to-cloudstack-bridge-webapps-awsapi.patch
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

Re: Review Request 12358: CLOUDSTACK-3228: system vms are not comming up in zone with two cluster xen and kvm

2013-07-09 Thread Harikrishna Patnala


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

(Updated July 9, 2013, 3:02 p.m.)


Review request for cloudstack, Abhinandan Prateek and Nitin Mehta.


Changes
---

Changed the way of getting right template.
Instead of shuffling the hypervisor list, we make a try on each hypervisor 
until it gets a right template.


Bugs: CLOUDSTACK-3228


Repository: cloudstack-git


Description
---

CLOUDSTACK-3228: system vms are not comming up in zone with two cluster xen and 
kvm;Zone host is ready, but secondary storage vm template: 3 is not ready on 
secondary storage: 2

Shuffling the hypervisors list before getting the first hypervisor in list so 
that on every retry of system vm deployment it chooses different hypervisor and 
checking whether template is downloaded or not.


Diffs (updated)
-

  engine/schema/src/com/cloud/storage/dao/VMTemplateDaoImpl.java 9e75990 
  
plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/XenServer56FP1Resource.java
 407f069 
  server/src/com/cloud/consoleproxy/ConsoleProxyManagerImpl.java 5983aa7 
  server/src/com/cloud/resource/ResourceManager.java e35e89a 
  server/src/com/cloud/resource/ResourceManagerImpl.java 41c6ad7 
  server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java 
05256a8 
  server/test/com/cloud/resource/MockResourceManagerImpl.java 18cff80 

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


Testing
---

tested locally


Thanks,

Harikrishna Patnala

Review Request 12364: Follow up fix for CLOUDSTACK-2777

2013-07-09 Thread Rayees Namathponnan


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

Review request for cloudstack, Likitha Shetty and Prachi Damle.


Repository: cloudstack-git


Description
---

Followup fix for CLOUDSTACK-2777, crypto.properties and xes.keystore moved to 
AWSAPI installation location and changed permission  to 666


Diffs
-

  packaging/centos63/cloud.spec f7eb629 

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


Testing
---

Tested 


Thanks,

Rayees Namathponnan

Regions in 4.1

Did the regions model get fully implemented in 4.1? Is it usable and 
functional? Has anyone actually deployed it yet with the 4.1 release?

Thanks,
Matt

Re: Review Request 12364: Follow up fix for CLOUDSTACK-2777

2013-07-09 Thread Likitha Shetty


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

Ship it!


Ship It!

- Likitha Shetty


On July 9, 2013, 3:20 p.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12364/
> ---
> 
> (Updated July 9, 2013, 3:20 p.m.)
> 
> 
> Review request for cloudstack, Likitha Shetty and Prachi Damle.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Followup fix for CLOUDSTACK-2777, crypto.properties and xes.keystore moved to 
> AWSAPI installation location and changed permission  to 666
> 
> 
> Diffs
> -
> 
>   packaging/centos63/cloud.spec f7eb629 
> 
> Diff: https://reviews.apache.org/r/12364/diff/
> 
> 
> Testing
> ---
> 
> Tested 
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

Re: Review Request 12364: Follow up fix for CLOUDSTACK-2777


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


Commit 3e7cebee2967e3523cb679ef30fcb19f7949c2dc in branch refs/heads/master 
from rayeesn
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3e7cebe ]

Followup fix for CLOUDSTACK-2777, crypto.properties and xes.keystore moved to 
AWSAPI installation location and changed permission to 666


- ASF Subversion and Git Services


On July 9, 2013, 3:20 p.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12364/
> ---
> 
> (Updated July 9, 2013, 3:20 p.m.)
> 
> 
> Review request for cloudstack, Likitha Shetty and Prachi Damle.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Followup fix for CLOUDSTACK-2777, crypto.properties and xes.keystore moved to 
> AWSAPI installation location and changed permission  to 666
> 
> 
> Diffs
> -
> 
>   packaging/centos63/cloud.spec f7eb629 
> 
> Diff: https://reviews.apache.org/r/12364/diff/
> 
> 
> Testing
> ---
> 
> Tested 
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

Re: Review Request 12364: Follow up fix for CLOUDSTACK-2777


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


Commit 2005aae7ac0a8a10ab4fc64803354ca4051a6d29 in branch refs/heads/4.2 from 
rayeesn
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2005aae ]

Followup fix for CLOUDSTACK-2777, crypto.properties and xes.keystore moved to 
AWSAPI installation location and changed permission to 666


- ASF Subversion and Git Services


On July 9, 2013, 3:20 p.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12364/
> ---
> 
> (Updated July 9, 2013, 3:20 p.m.)
> 
> 
> Review request for cloudstack, Likitha Shetty and Prachi Damle.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Followup fix for CLOUDSTACK-2777, crypto.properties and xes.keystore moved to 
> AWSAPI installation location and changed permission  to 666
> 
> 
> Diffs
> -
> 
>   packaging/centos63/cloud.spec f7eb629 
> 
> Diff: https://reviews.apache.org/r/12364/diff/
> 
> 
> Testing
> ---
> 
> Tested 
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

Re: Review Request 12364: Follow up fix for CLOUDSTACK-2777


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


Commit e1736bcca50f1c74b1c71dce72e27ef7f62bab30 in branch 
refs/heads/master-6-17-stable from rayeesn
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e1736bc ]

Followup fix for CLOUDSTACK-2777, crypto.properties and xes.keystore moved to 
AWSAPI installation location and changed permission to 666


- ASF Subversion and Git Services


On July 9, 2013, 3:20 p.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12364/
> ---
> 
> (Updated July 9, 2013, 3:20 p.m.)
> 
> 
> Review request for cloudstack, Likitha Shetty and Prachi Damle.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Followup fix for CLOUDSTACK-2777, crypto.properties and xes.keystore moved to 
> AWSAPI installation location and changed permission  to 666
> 
> 
> Diffs
> -
> 
>   packaging/centos63/cloud.spec f7eb629 
> 
> Diff: https://reviews.apache.org/r/12364/diff/
> 
> 
> Testing
> ---
> 
> Tested 
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

Re: cloudstack-installation

2013-07-09 Thread Ryan Lei

If you're working with 4.1, the current documentation contains several path
or URL errors that are not updated with CloudStack refactor.

It's better to refer to the daily build for the unreleased 4.1.1 at jenkins:
http://jenkins.cloudstack.org/view/4.1/job/docs-4.1-installguide/lastSuccessfulBuild/artifact/Apache_CloudStack-4.1.1-Installation_Guide-en-US.pdf

You can just install from the community RPM/DEB packages without building
from source if you're not setting up a development environment. Jump
directly to Chapter 4, or more specifically, Section 4.4.


---
Yu-Heng (Ryan) Lei, Associate Reasearcher
Chunghwa Telecom Laboratories / Cloud Computing Laboratory
ryan...@cht.com.tw
or
ryanlei750...@gmail.com



On Tue, Jul 9, 2013 at 10:56 PM, Chip Childers wrote:

> On Tue, Jul 09, 2013 at 05:09:06AM -0700, gaurav jain wrote:
> > I am trying to install cloudstack following the steps given in the
> INSTALL.md file which is there with the cloudstack release.
> >
> > However I have been unsuccessful. I am trying to download maven, but all
> the mirrors say "Page Not Found".
> >
> > Then I am trying to get the KEYS File, but it opens up in a new tab.
> From where can I download it?
> > Is there any specific directory where I should save it?
> >
> > Regards,
> > Gaurav
>
> Honestly, we should delete the INSTALL.txt file.  The best instructions
> can be found here:
>
> http://cloudstack.apache.org/docs/en-US/index.html
>
> Select the install guide for the version you are
> working with.
>

RE: Unable to start secondary storage in DevCloud

2013-07-09 Thread Tariq Iqbal

Syed,

The Console Proxy VM is also a system VM and presents a console view for a VM 
instance via the web UI. With it being a DevCloud, if you don't need to use the 
console proxy then you can set the maximum number of console proxy vms to 0 
under Global Settings.

Btw have you followed step 8 to deploy the DevCloud configuration from: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/DevCloud?

Kind Regards,
Tariq Iqbal
Senior Consultant

S: +44(0)20 3603 0540 | M: +44(0)790 9911600
tariq.iq...@shapeblue.com | www.shapeblue.com | Twitter:@shapeBlue

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS



From: Syed
Sent: 09 July 2013 15:10
To: dev@cloudstack.apache.org
Cc: Tariq Iqbal
Subject: Re: Unable to start secondary storage in DevCloud

Thanks for your reply Tariq. I fiddled around with the settings a bit
but the problem still persisted. I then saw that the primary storage
was scoped for the HOST instead of CLUSTER or ZONE. I added one more
primary storage and then restarted management server and the secondary
storage came up. Though I do not know if it was the combination of the
over-provisioning settings and adding primary storage. But still that
is some progress :) I am now getting a different message of console
proxy manager not being able to start because of insufficient capacity.
What does this VM do? Do you have any settings to recommend that I can
fiddle around and make this VM come up though I do not know what
exactly this is used for.

Thanks for your help. I was able to get something working.

Thanks
-Syed



WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:)
Exception while trying to start console proxy
com.cloud.exception.InsufficientServerCapacityException: Unable to
create a deployment for VM[ConsoleProxy|v-40-VM]Scope=interface
com.cloud.dc.DataCenter; id=1
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:820)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550)
at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.startProxy(ConsoleProxyManagerImpl.java:556)
at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.allocCapacity(ConsoleProxyManagerImpl.java:927)
at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:1664)
at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:157)
at
com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111)
at
com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33)
at
com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81)
at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)



On Tue 09 Jul 2013 09:12:14 AM EDT, Tariq Iqbal wrote:
> Hi Syed,
>
> You could try increasing the overprovisiong factor for storage 
> (storage.overprovisioning.factor). You'll find it under Global Settings -> 
> search for 'factor'
>
> storage.overprovisioning.factor
>
> There is also the CPU and Memory over provisioning factors there as well.
>
> Once you change any of these settings, you will need to restart the 
> cloudstack managemeent service for the changes to take affect.
>
> Kind Regards,
> Tariq Iqbal
> Senior Consultant
>
> S: +44(0)20 3603 0540 | M: +44(0)790 9911600
> tariq.iq...@shapeblue.com | www.shapeblue.com | Twitter:@shapeBlue
>
> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
>
>
> 
> From: Syed Mushtaq
> Sent: 09 July 2013 04:42
> To: dev@cloudstack.apache.org
> Subject: Unable to start secondary storage in DevCloud
>
> Hi,
>
> I was trying to setup DevCloud by following
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/DevCloud on my
> ubuntu machine. I have the xenserver vm running and I see that the
> secondary storage is being exported as NFS and I am able to mount it on the
> host machine. However it is not being picked up by cloudstack. I get the
> InsufficientServerCapacityException exception. I have given 4GB of RAM and
> 4 CPU cores

Re: Using the ACS simulator for jclouds "live" tests - some questions. =)

During the setup process, I now get some NumberFormatExceptions.

I call:  mvn -Pdeveloper,marvin.setup
-Dmarvin.config=setup/dev/advanced.cfg -pl :cloud-marvin
integration-test

I see in the console:

ERROR [agent.manager.AgentManagerImpl] (Simulator-Agent-Mgr-1:)
Monitor DownloadListener says there is an error in the connect process
for 4 due to null
java.lang.NumberFormatException: null
at java.lang.Long.parseLong(Long.java:404)
at java.lang.Long.parseLong(Long.java:483)
at com.cloud.utils.UriUtils.getRemoteSize(UriUtils.java:113)
at 
org.apache.cloudstack.storage.image.TemplateServiceImpl.handleTemplateSync(TemplateServiceImpl.java:325)
at 
com.cloud.storage.download.DownloadListener.processConnect(DownloadListener.java:307)
at 
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:586)
at 
com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1480)
at 
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1798)
at 
com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:824)
at 
com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:621)
at 
com.cloud.agent.manager.MockAgentManagerImpl$SystemVMHandler.run(MockAgentManagerImpl.java:354)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
INFO  [agent.manager.AgentManagerImpl] (Simulator-Agent-Mgr-1:) Host 4
is disconnecting with event AgentDisconnected
WARN  [cloud.resource.ResourceManagerImpl] (Simulator-Agent-Mgr-1:)
Unable to connect due to
com.cloud.utils.exception.CloudRuntimeException: Unable to connect 4
at 
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:605)
at 
com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1480)
at 
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1798)
at 
com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:824)
at 
com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:621)
at 
com.cloud.agent.manager.MockAgentManagerImpl$SystemVMHandler.run(MockAgentManagerImpl.java:354)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.NumberFormatException: null
at java.lang.Long.parseLong(Long.java:404)
at java.lang.Long.parseLong(Long.java:483)
at com.cloud.utils.UriUtils.getRemoteSize(UriUtils.java:113)
at 
org.apache.cloudstack.storage.image.TemplateServiceImpl.handleTemplateSync(TemplateServiceImpl.java:325)
at 
com.cloud.storage.download.DownloadListener.processConnect(DownloadListener.java:307)
at 
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:586)
... 8 more
Exception in thread "Simulator-Agent-Mgr-1"
com.cloud.utils.exception.CloudRuntimeException: Cannot transit agent
status with event AgentDisconnected for host 4, mangement server id is
2200358551563,Unable to transition to a new state from Creating via
AgentDisconnected
at 
com.cloud.agent.manager.AgentManagerImpl.agentStatusTransitTo(AgentManagerImpl.java:1411)
at 
com.cloud.resource.ResourceManagerImpl.markHostAsDisconnected(ResourceManagerImpl.java:1748)
at 
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1814)
at 
com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:824)
at 
com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:621)
at 
com.cloud.agent.manager.MockAgentManagerImpl$SystemVMHandler.run(MockAgentManagerImpl.java:354)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)

On Mon, Jul 8, 2013 at 9:44 PM, Edison Su  wrote:
> The simulator issue should be fixed on 4.2 branch.
>
>> -Original Message-
>> From: Chip Childers [mailto:chip.child...@sungard.com]
>> Sent: Monday, July 08, 2013 1:56 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: Using the ACS simulator for jclouds "live" tests - some 
>> questions.
>> =)
>>
>> On Thu, Jul 04, 2013 at 08:49:52PM +0530, Prasanna Santhanam wrote:
>> > On Mon, Jun 24, 2013 at 11:08:20AM -0700, Andrew Bayer wrote:
>> > > - At least one available simulator template (best-case would be
>> > > Ubuntu
>> > > 10.04 or 12.04) that can be "booted up" out of the box - for
>> > > whatever reason (I honestly can't tell, from the brief dive I did
>> > > through the code), all the builtin templates come up with
>> > > isready=false in the listTemplates output, which makes jclouds think
>> > > ther

Re: cloudstack-installation

Ryan,
I am new to cloudstack, on the basis of some resources suggested to me
I was starting to set up an environment on my machine.
My main goal is to understand the principle and theory behind cloudstack and 
start
contributing to the community.
So guide me If I am wrong somewhere

Regards
Gaurav

 From: Ryan Lei 
To: "dev@cloudstack.apache.org"  
Cc: gaurav jain  
Sent: Tuesday, July 9, 2013 9:24 PM
Subject: Re: cloudstack-installation

If you're working with 4.1, the current documentation contains several path or 
URL errors that are not updated with CloudStack refactor.

It's better to refer to the daily build for the unreleased 4.1.1 at jenkins:
http://jenkins.cloudstack.org/view/4.1/job/docs-4.1-installguide/lastSuccessfulBuild/artifact/Apache_CloudStack-4.1.1-Installation_Guide-en-US.pdf

You can just install from the community RPM/DEB packages without building from 
source if you're not setting up a development environment. Jump directly to 
Chapter 4, or more specifically, Section 4.4.

---
Yu-Heng (Ryan) Lei, Associate Reasearcher

Chunghwa Telecom Laboratories / Cloud Computing 
Laboratory

ryan...@cht.com.tw or ryanlei750...@gmail.com

On Tue, Jul 9, 2013 at 10:56 PM, Chip Childers  
wrote:

On Tue, Jul 09, 2013 at 05:09:06AM -0700, gaurav jain wrote:
>> I am trying to install cloudstack following the steps given in the 
>> INSTALL.md file which is there with the cloudstack release.
>>
>> However I have been unsuccessful. I am trying to download maven, but all the 
>> mirrors say "Page Not Found".
>>
>> Then I am trying to get the KEYS File, but it opens up in a new tab. From 
>> where can I download it?
>> Is there any specific directory where I should save it?
>>
>> Regards,
>> Gaurav
>
>Honestly, we should delete the INSTALL.txt file.  The best instructions
>can be found here:
>
>http://cloudstack.apache.org/docs/en-US/index.html
>
>Select the install guide for the version you are
>working with.
>

Re: cloudstack-installation

Chip
I was going through and following the steps given on the link suggested by you.
However I was unsuccessful.

http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.0-incubating/html/Installation_Guide/sect-source-verify.html

The KEYS link opens up a html page. I tried copying the data from the page into 
text file. But when I go to step : 

gpg --verify apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc

It shows error saying that there is no asc file and that .sig/.asc file need to 
be run in terminal
before this.

Regards
Gaurav

 From: Chip Childers 
To: dev@cloudstack.apache.org; gaurav jain  
Sent: Tuesday, July 9, 2013 8:26 PM
Subject: Re: cloudstack-installation

On Tue, Jul 09, 2013 at 05:09:06AM -0700, gaurav jain wrote:
> I am trying to install cloudstack following the steps given in the INSTALL.md 
> file which is there with the cloudstack release.
> 
> However I have been unsuccessful. I am trying to download maven, but all the 
> mirrors say "Page Not Found".
> 
> Then I am trying to get the KEYS File, but it opens up in a new tab. From 
> where can I download it?
> Is there any specific directory where I should save it?
> 
> Regards,
> Gaurav

Honestly, we should delete the INSTALL.txt file.  The best instructions
can be found here:

http://cloudstack.apache.org/docs/en-US/index.html

Select the install guide for the version you are
working with.

Re: cloudstack-installation

On Tue, Jul 09, 2013 at 09:55:36AM -0700, gaurav jain wrote:
> Chip
> I was going through and following the steps given on the link suggested by 
> you.
> However I was unsuccessful.
> 
> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.0-incubating/html/Installation_Guide/sect-source-verify.html
> 
> The KEYS link opens up a html page. I tried copying the data from the page 
> into text file. But when I go to step : 
> 
> gpg --verify apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc
> 
> It shows error saying that there is no asc file and that .sig/.asc file need 
> to be run in terminal
> before this.
> 
> 
> Regards
> Gaurav


Sorry, that URL changed after we graduated from the incubator.  Use this
link:

http://www.apache.org/dist/cloudstack/KEYS

> 
> 
> 
> 
> 
> 
>  From: Chip Childers 
> To: dev@cloudstack.apache.org; gaurav jain  
> Sent: Tuesday, July 9, 2013 8:26 PM
> Subject: Re: cloudstack-installation
>  
> 
> On Tue, Jul 09, 2013 at 05:09:06AM -0700, gaurav jain wrote:
> > I am trying to install cloudstack following the steps given in the 
> > INSTALL.md file which is there with the cloudstack release.
> > 
> > However I have been unsuccessful. I am trying to download maven, but all 
> > the mirrors say "Page Not Found".
> > 
> > Then I am trying to get the KEYS File, but it opens up in a new tab. >From 
> > where can I download it?
> > Is there any specific directory where I should save it?
> > 
> > Regards,
> > Gaurav
> 
> Honestly, we should delete the INSTALL.txt file.  The best instructions
> can be found here:
> 
> http://cloudstack.apache.org/docs/en-US/index.html
> 
> Select the install guide for the version you are
> working with.

RE: Regions in 4.1

2013-07-09 Thread Sangeetha Hariharan

There is no UI support for regions in 4.1. All API calls relating to regions 
feature is implemented.
Note that cloudstack does not do data sync between regions.

There are few open issues relating to Regions and Event notifications:

CLOUDSTACK-1673 - AWS Regions - Events - User disable / Domain Delete event 
does not include the UUID of the user/domain that was disabled.
CLOUDSTACK-1775 - Events related User/Domain/Account are not being generated 
expect for USER-DISABLE,DOMAIN-DELETE and ACCOUNT.DISABLE event.
CLOUDSTACK-1819 - AWS Regions - Issues seen when trying to move a zone from 1 
region to another.

-Thanks
Sangeetha
-Original Message-
From: Mathias Mullins [mailto:mathias.mull...@citrix.com] 
Sent: Tuesday, July 09, 2013 8:34 AM
To: dev@cloudstack.apache.org
Subject: Regions in 4.1

Did the regions model get fully implemented in 4.1? Is it usable and 
functional? Has anyone actually deployed it yet with the 4.1 release?

Thanks,
Matt

RE: Using the ACS simulator for jclouds "live" tests - some questions. =)

I think it's the issue https://issues.apache.org/jira/browse/CLOUDSTACK-3139, 
that your mgt server can't access the url of template.

> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Tuesday, July 09, 2013 9:41 AM
> To: 
> Subject: Re: Using the ACS simulator for jclouds "live" tests - some 
> questions.
> =)
> 
> During the setup process, I now get some NumberFormatExceptions.
> 
> I call:  mvn -Pdeveloper,marvin.setup
> -Dmarvin.config=setup/dev/advanced.cfg -pl :cloud-marvin integration-test
> 
> I see in the console:
> 
> ERROR [agent.manager.AgentManagerImpl] (Simulator-Agent-Mgr-1:)
> Monitor DownloadListener says there is an error in the connect process for 4
> due to null
> java.lang.NumberFormatException: null
> at java.lang.Long.parseLong(Long.java:404)
> at java.lang.Long.parseLong(Long.java:483)
> at com.cloud.utils.UriUtils.getRemoteSize(UriUtils.java:113)
> at
> org.apache.cloudstack.storage.image.TemplateServiceImpl.handleTemplate
> Sync(TemplateServiceImpl.java:325)
> at
> com.cloud.storage.download.DownloadListener.processConnect(DownloadL
> istener.java:307)
> at
> com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(
> AgentManagerImpl.java:586)
> at
> com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(A
> gentManagerImpl.java:1480)
> at
> com.cloud.resource.ResourceManagerImpl.createHostAndAgent(Resource
> ManagerImpl.java:1798)
> at
> com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceMan
> agerImpl.java:824)
> at
> com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManager
> Impl.java:621)
> at
> com.cloud.agent.manager.MockAgentManagerImpl$SystemVMHandler.run(
> MockAgentManagerImpl.java:354)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.jav
> a:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.ja
> va:615)
> at java.lang.Thread.run(Thread.java:722)
> INFO  [agent.manager.AgentManagerImpl] (Simulator-Agent-Mgr-1:) Host 4
> is disconnecting with event AgentDisconnected WARN
> [cloud.resource.ResourceManagerImpl] (Simulator-Agent-Mgr-1:) Unable to
> connect due to
> com.cloud.utils.exception.CloudRuntimeException: Unable to connect 4 at
> com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(
> AgentManagerImpl.java:605)
> at
> com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(A
> gentManagerImpl.java:1480)
> at
> com.cloud.resource.ResourceManagerImpl.createHostAndAgent(Resource
> ManagerImpl.java:1798)
> at
> com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceMan
> agerImpl.java:824)
> at
> com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManager
> Impl.java:621)
> at
> com.cloud.agent.manager.MockAgentManagerImpl$SystemVMHandler.run(
> MockAgentManagerImpl.java:354)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.jav
> a:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.ja
> va:615)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: java.lang.NumberFormatException: null at
> java.lang.Long.parseLong(Long.java:404)
> at java.lang.Long.parseLong(Long.java:483)
> at com.cloud.utils.UriUtils.getRemoteSize(UriUtils.java:113)
> at
> org.apache.cloudstack.storage.image.TemplateServiceImpl.handleTemplate
> Sync(TemplateServiceImpl.java:325)
> at
> com.cloud.storage.download.DownloadListener.processConnect(DownloadL
> istener.java:307)
> at
> com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(
> AgentManagerImpl.java:586)
> ... 8 more
> Exception in thread "Simulator-Agent-Mgr-1"
> com.cloud.utils.exception.CloudRuntimeException: Cannot transit agent
> status with event AgentDisconnected for host 4, mangement server id is
> 2200358551563,Unable to transition to a new state from Creating via
> AgentDisconnected at
> com.cloud.agent.manager.AgentManagerImpl.agentStatusTransitTo(Agent
> ManagerImpl.java:1411)
> at
> com.cloud.resource.ResourceManagerImpl.markHostAsDisconnected(Resou
> rceManagerImpl.java:1748)
> at
> com.cloud.resource.ResourceManagerImpl.createHostAndAgent(Resource
> ManagerImpl.java:1814)
> at
> com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceMan
> agerImpl.java:824)
> at
> com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManager
> Impl.java:621)
> at
> com.cloud.agent.manager.MockAgentManagerImpl$SystemVMHandler.run(
> MockAgentManagerImpl.java:354)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.jav
> a:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.ja
> va:615)
> at java.lang.Thread.run(Thread.java:722)
> 
> 
> 
> On Mon, Jul 8, 2013 at 9:44 PM, Edison Su  wrote:
> > The simulator issue should be fixed on 4.2 branch.
> >
> >> -Original Message-
> >> From: Chip Childers [mailto:chip.child...@sungard.com]
> >> Sent: Monday, July 08, 2013 1:56 PM
> >> To: dev@cloudstack.apache.org

Re: cloudstack-installation

Chip
It is a HTML link.
What should I do. Copy the text in a text file? what extension should it have? 
Is there any particular directory I should save it to?






 From: Chip Childers 
To: gaurav jain  
Cc: "dev@cloudstack.apache.org"  
Sent: Tuesday, July 9, 2013 10:27 PM
Subject: Re: cloudstack-installation
 

On Tue, Jul 09, 2013 at 09:55:36AM -0700, gaurav jain wrote:
> Chip
> I was going through and following the steps given on the link suggested by 
> you.
> However I was unsuccessful.
> 
> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.0-incubating/html/Installation_Guide/sect-source-verify.html
> 
> The KEYS link opens up a html page. I tried copying the data from the page 
> into text file. But when I go to step : 
> 
> gpg --verify apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc
> 
> It shows error saying that there is no asc file and that .sig/.asc file need 
> to be run in terminal
> before this.
> 
> 
> Regards
> Gaurav


Sorry, that URL changed after we graduated from the incubator.  Use this
link:

http://www.apache.org/dist/cloudstack/KEYS

> 
> 
> 
> 
> 
> 
>  From: Chip Childers 
> To: dev@cloudstack.apache.org; gaurav jain  
> Sent: Tuesday, July 9, 2013 8:26 PM
> Subject: Re: cloudstack-installation
>  
> 
> On Tue, Jul 09, 2013 at 05:09:06AM -0700, gaurav jain wrote:
> > I am trying to install cloudstack following the steps given in the 
> > INSTALL.md file which is there with the cloudstack release.
> > 
> > However I have been unsuccessful. I am trying to download maven, but all 
> > the mirrors say "Page Not Found".
> > 
> > Then I am trying to get the KEYS File, but it opens up in a new tab. From 
> > where can I download it?
> > Is there any specific directory where I should save it?
> > 
> > Regards,
> > Gaurav
> 
> Honestly, we should delete the INSTALL.txt file.  The best instructions
> can be found here:
> 
> http://cloudstack.apache.org/docs/en-US/index.html
> 
> Select the install guide for the version you are
> working with.

Re: Review Request 12245: CLOUDSTACK-1960: Fix for UK Keyboard Bar symbol.

2013-07-09 Thread Fang Wang


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

Ship it!


looks good, ship it. 

- Fang Wang


On July 3, 2013, 11:43 a.m., Sanjay Tripathi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12245/
> ---
> 
> (Updated July 3, 2013, 11:43 a.m.)
> 
> 
> Review request for cloudstack, Animesh Chaturvedi, Fang Wang, and Ram Ganesh.
> 
> 
> Bugs: CLOUDSTACK-1960
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-1960: Fix for Bar symbol in UK keyboard.
> 
> With this fix, cloudStack will support bar symbol i.e. "|" for UK keyboard.
> 
> 
> Diffs
> -
> 
>   services/console-proxy/server/js/ajaxkeys.js 677962b 
> 
> Diff: https://reviews.apache.org/r/12245/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Sanjay Tripathi
> 
>

Re: cloudstack-installation

On Tue, Jul 09, 2013 at 10:36:24AM -0700, gaurav jain wrote:
> Chip
> It is a HTML link.
> What should I do. Copy the text in a text file? what extension should it 
> have? Is there any particular directory I should save it to?

It's a text file.  Just save it to whatever location or file you want,
and then import the included keys via the instructions.

Frankly though, this is just a verification step that you can do or not
do at your discretion.  Since you mentioned that you are trying to
understand the code, the other option is to just clone the git repo and
checkout the 4.1 branch to work from.

RE: Using the ACS simulator for jclouds "live" tests - some questions. =)



> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Tuesday, July 09, 2013 7:52 AM
> To: dev@cloudstack.apache.org
> Subject: Re: Using the ACS simulator for jclouds "live" tests - some 
> questions.
> =)
> 
> On Tue, Jul 09, 2013 at 01:44:26AM +, Edison Su wrote:
> > The simulator issue should be fixed on 4.2 branch.
> 
> Do you mind pulling those changes into master?

Done.

Re: Using the ACS simulator for jclouds "live" tests - some questions. =)

On Tue, Jul 09, 2013 at 05:24:53PM +, Edison Su wrote:
> I think it's the issue https://issues.apache.org/jira/browse/CLOUDSTACK-3139, 
> that your mgt server can't access the url of template.

Yeah, it appears so.  Thanks for searching for me.  Apparently I was too
lazy to actually check myself.  ;-)

RE: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?



> -Original Message-
> From: John Burwell [mailto:jburw...@basho.com]
> Sent: Tuesday, July 09, 2013 7:53 AM
> To: dev@cloudstack.apache.org
> Cc: 'Chip Childers'
> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?
> 
> Edison,
> 
> As I read through this thread, we seem to be conflating the following topics:
> 
>   1. Feature regression testing per release cycle
>   2. Identifying and back porting defect fixes to previous releases
>   3. Feature removal process
> 
> To my mind, these topics are completely unrelated.  We have regression test
> and defect triage processes to address items 1 and 2.  If you feel that they
> can be improved, then we should discuss those improvements in a separate
> thread.  No community or system will be perfect.  I believe the best we can
> do is seek to do it better today than yesterday.  To that end, observing that
> we did something poorly in the past does not justify continuing to do it
> poorly or removing a feature on which users are relying.
> 
> 
> I am concerned about item 3 -- the merge of a feature removal without
> community consensus.  If you *think* a feature is broken in a previous

This feature is not been tested since about one and half year ago, nobody knows 
the status of swift integration.
If we can't claim to support Swift in 4.0, 4.1, then why you think I am 
removing a feature?

> release, test it and lodge defects or request help to regression test it.  We
> have a maintenance release cycle through which we can address these types
> of defects.  As I stated previously, existing feature defects are not a
> justification to remove that feature.
> 
> Thanks,
> -John
> 
> On Jul 8, 2013, at 7:35 PM, Edison Su  wrote:
> 
> > And I want to point out, that, it's easy to say this feature and that 
> > feature
> are supported in certain release, but without fully tested for each release,
> only God will know the status.
> > For example, there is a bug in 4.2:
> https://issues.apache.org/jira/browse/CLOUDSTACK-2583, it says can't
> backup snapshot from primary storage into S3 if the hypervisor is xenserver.
> > It's fired for 4.2, but actually, 4.1 will have the same issue.
> > Will we claim, to support S3 in 4.1, while the major functionality of S3 is
> broken?
> >
> >> -Original Message-
> >> From: John Burwell [mailto:jburw...@basho.com]
> >> Sent: Monday, July 08, 2013 1:42 PM
> >> To: dev@cloudstack.apache.org
> >> Cc: 'Chip Childers'
> >> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 
> >> 4.2?
> >>
> >> All,
> >>
> >> I apologize for losing track of this issue.  We discussed the lack of
> >> Swift support briefly in late May/early June as part of the first
> >> round review, but I completely lost track of it in the sea of items being
> addressed.
> >>
> >> This gap represents a feature deprecation without any community
> discussion.
> >> A lack of code changes or test requests for a feature does not
> >> translate to no usage.  It also does not provide license for a
> >> feature to be dropped without community discussion and consensus.
> >>
> >> In summary, post merge is not the time to be asking this question.  I
> >> am concerned about the precedent this action will set in future release
> cycles.
> >> Furthermore, re-implementation of a feature should be complete.  To
> >> me, it is not acceptable to say, "I re-implemented the functionality
> >> with which I was familiar.  Hey, community, if you like those other
> >> parts, you will need to fill in the gaps."  To my mind, a feature
> >> re-implementation should not be acceptable until it implements all of the
> capabilities it is replacing.
> >>
> >> Thanks,
> >> -John
> >>
> >> On Jul 8, 2013, at 1:30 PM, Sudha Ponnaganti
> >> 
> >> wrote:
> >>
> >>> Swift was tested for older version of Citrix release. There were  no
> >>> code
> >> changes or certification requests, so that area was deprioritized.
> >>>
> >>> Thanks
> >>> /Sudha
> >>>
> >>> -Original Message-
> >>> From: Edison Su [mailto:edison...@citrix.com]
> >>> Sent: Monday, July 08, 2013 10:15 AM
> >>> To: 'Chip Childers'; 
> >>> Subject: RE: Swift in 4.2 is broken, anybody wants it to be supported in
> 4.2?
> >>>
> >>>
> >>>
>  -Original Message-
>  From: Chip Childers [mailto:chip.child...@sungard.com]
>  Sent: Monday, July 08, 2013 6:46 AM
>  To: ; Edison Su
>  Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in
> 4.2?
> 
>  On Mon, Jul 8, 2013 at 9:22 AM, David Nalley  wrote:
> > On Wed, Jul 3, 2013 at 5:29 PM, Edison Su 
> wrote:
> >> Due to object store refactor, Swift is broken. The reason, is
> >> that, we only
>  have S3 test environment in our lab, so only S3 is tested for now.
> >> Before adding the feature back, I'd better ask from, the
> >> community, do
>  we want to support Swift? If so, which version of Swift? This will
>  take some efforts to suppo

Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?

On Tue, Jul 09, 2013 at 05:56:24PM +, Edison Su wrote:
> 
> 
> > -Original Message-
> > From: John Burwell [mailto:jburw...@basho.com]
> > Sent: Tuesday, July 09, 2013 7:53 AM
> > To: dev@cloudstack.apache.org
> > Cc: 'Chip Childers'
> > Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 
> > 4.2?
> > 
> > Edison,
> > 
> > As I read through this thread, we seem to be conflating the following 
> > topics:
> > 
> > 1. Feature regression testing per release cycle
> > 2. Identifying and back porting defect fixes to previous releases
> > 3. Feature removal process
> > 
> > To my mind, these topics are completely unrelated.  We have regression test
> > and defect triage processes to address items 1 and 2.  If you feel that they
> > can be improved, then we should discuss those improvements in a separate
> > thread.  No community or system will be perfect.  I believe the best we can
> > do is seek to do it better today than yesterday.  To that end, observing 
> > that
> > we did something poorly in the past does not justify continuing to do it
> > poorly or removing a feature on which users are relying.
> > 
> > 
> > I am concerned about item 3 -- the merge of a feature removal without
> > community consensus.  If you *think* a feature is broken in a previous
> 
> This feature is not been tested since about one and half year ago, nobody 
> knows the status of swift integration.
> If we can't claim to support Swift in 4.0, 4.1, then why you think I am 
> removing a feature?

But we *do* claim that support. See [1].

Not having tested it is *not* the same as saying that it isn't
supported.

[1] 
http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.0/html/Installation_Guide/about-secondary-storage.html

RE: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?



> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Tuesday, July 09, 2013 11:00 AM
> To: Edison Su
> Cc: dev@cloudstack.apache.org
> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?
> 
> On Tue, Jul 09, 2013 at 05:56:24PM +, Edison Su wrote:
> >
> >
> > > -Original Message-
> > > From: John Burwell [mailto:jburw...@basho.com]
> > > Sent: Tuesday, July 09, 2013 7:53 AM
> > > To: dev@cloudstack.apache.org
> > > Cc: 'Chip Childers'
> > > Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in
> 4.2?
> > >
> > > Edison,
> > >
> > > As I read through this thread, we seem to be conflating the following
> topics:
> > >
> > >   1. Feature regression testing per release cycle
> > >   2. Identifying and back porting defect fixes to previous releases
> > >   3. Feature removal process
> > >
> > > To my mind, these topics are completely unrelated.  We have
> > > regression test and defect triage processes to address items 1 and
> > > 2.  If you feel that they can be improved, then we should discuss
> > > those improvements in a separate thread.  No community or system
> > > will be perfect.  I believe the best we can do is seek to do it
> > > better today than yesterday.  To that end, observing that we did
> > > something poorly in the past does not justify continuing to do it poorly 
> > > or
> removing a feature on which users are relying.
> > >
> > >
> > > I am concerned about item 3 -- the merge of a feature removal
> > > without community consensus.  If you *think* a feature is broken in
> > > a previous
> >
> > This feature is not been tested since about one and half year ago, nobody
> knows the status of swift integration.
> > If we can't claim to support Swift in 4.0, 4.1, then why you think I am
> removing a feature?
> 
> But we *do* claim that support. See [1].
> 
> Not having tested it is *not* the same as saying that it isn't supported.
> 
> [1] http://cloudstack.apache.org/docs/en-
> US/Apache_CloudStack/4.1.0/html/Installation_Guide/about-secondary-
> storage.html

IMHO, saying something is supported without tested for each release is worse 
than saying not supported.

Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?

On Tue, Jul 09, 2013 at 05:56:24PM +, Edison Su wrote:
> 
> 
> > -Original Message-
> > From: John Burwell [mailto:jburw...@basho.com]
> > Sent: Tuesday, July 09, 2013 7:53 AM
> > To: dev@cloudstack.apache.org
> > Cc: 'Chip Childers'
> > Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 
> > 4.2?
> > 
> > Edison,
> > 
> > As I read through this thread, we seem to be conflating the following 
> > topics:
> > 
> > 1. Feature regression testing per release cycle
> > 2. Identifying and back porting defect fixes to previous releases
> > 3. Feature removal process
> > 
> > To my mind, these topics are completely unrelated.  We have regression test
> > and defect triage processes to address items 1 and 2.  If you feel that they
> > can be improved, then we should discuss those improvements in a separate
> > thread.  No community or system will be perfect.  I believe the best we can
> > do is seek to do it better today than yesterday.  To that end, observing 
> > that
> > we did something poorly in the past does not justify continuing to do it
> > poorly or removing a feature on which users are relying.
> > 
> > 
> > I am concerned about item 3 -- the merge of a feature removal without
> > community consensus.  If you *think* a feature is broken in a previous
> 
> This feature is not been tested since about one and half year ago, nobody 
> knows the status of swift integration.
> If we can't claim to support Swift in 4.0, 4.1, then why you think I am 
> removing a feature?

Edison, I'm working under the assumption that Swift support was simply
missed in the refactoring.  If this isn't the case, then please be
explicit that you made the decision to not include it.  If this is the
case, then can't we agree that it needs to be rectified?

-chip

Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?

On Tue, Jul 09, 2013 at 06:01:08PM +, Edison Su wrote:
> 
> 
> > -Original Message-
> > From: Chip Childers [mailto:chip.child...@sungard.com]
> > Sent: Tuesday, July 09, 2013 11:00 AM
> > To: Edison Su
> > Cc: dev@cloudstack.apache.org
> > Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 
> > 4.2?
> > 
> > On Tue, Jul 09, 2013 at 05:56:24PM +, Edison Su wrote:
> > >
> > >
> > > > -Original Message-
> > > > From: John Burwell [mailto:jburw...@basho.com]
> > > > Sent: Tuesday, July 09, 2013 7:53 AM
> > > > To: dev@cloudstack.apache.org
> > > > Cc: 'Chip Childers'
> > > > Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in
> > 4.2?
> > > >
> > > > Edison,
> > > >
> > > > As I read through this thread, we seem to be conflating the following
> > topics:
> > > >
> > > > 1. Feature regression testing per release cycle
> > > > 2. Identifying and back porting defect fixes to previous 
> > > > releases
> > > > 3. Feature removal process
> > > >
> > > > To my mind, these topics are completely unrelated.  We have
> > > > regression test and defect triage processes to address items 1 and
> > > > 2.  If you feel that they can be improved, then we should discuss
> > > > those improvements in a separate thread.  No community or system
> > > > will be perfect.  I believe the best we can do is seek to do it
> > > > better today than yesterday.  To that end, observing that we did
> > > > something poorly in the past does not justify continuing to do it 
> > > > poorly or
> > removing a feature on which users are relying.
> > > >
> > > >
> > > > I am concerned about item 3 -- the merge of a feature removal
> > > > without community consensus.  If you *think* a feature is broken in
> > > > a previous
> > >
> > > This feature is not been tested since about one and half year ago, nobody
> > knows the status of swift integration.
> > > If we can't claim to support Swift in 4.0, 4.1, then why you think I am
> > removing a feature?
> > 
> > But we *do* claim that support. See [1].
> > 
> > Not having tested it is *not* the same as saying that it isn't supported.
> > 
> > [1] http://cloudstack.apache.org/docs/en-
> > US/Apache_CloudStack/4.1.0/html/Installation_Guide/about-secondary-
> > storage.html
> 
> IMHO, saying something is supported without tested for each release is worse 
> than saying not supported.
> 
> 

Fine, so we screwed up as a community.  I guess it needs to be tested
for all feature releases.

That has nothing to do with the issue of simply "dropping" support of
what might very well have been a functional feature.  Additionally, I
know of at least one major user of older cloudstack versions that *DO* use
swift for secondary storage.  Are you suggesting that we strand another
group of users *on purpose* again?

Here's my issue...  in the rush to make changes to the architecture and
/ or to get a new feature in, we have now run into the situation where
we have asked ourselves to simply drop a function *after the
fact*.  This is unhealthy for the project, crappy for our users, and
a sloppy way to evolve a software system.  I'm not blaming you for this
at all, but the object-storage architectural changes are an example of
this behaviour.  We need to stop this habit.

-chip

Re: Review Request 12245: CLOUDSTACK-1960: Fix for UK Keyboard Bar symbol.



> On July 9, 2013, 5:37 p.m., Fang Wang wrote:
> > looks good, ship it.

Did you commit this Fang?


- Chip


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


On July 3, 2013, 11:43 a.m., Sanjay Tripathi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12245/
> ---
> 
> (Updated July 3, 2013, 11:43 a.m.)
> 
> 
> Review request for cloudstack, Animesh Chaturvedi, Fang Wang, and Ram Ganesh.
> 
> 
> Bugs: CLOUDSTACK-1960
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-1960: Fix for Bar symbol in UK keyboard.
> 
> With this fix, cloudStack will support bar symbol i.e. "|" for UK keyboard.
> 
> 
> Diffs
> -
> 
>   services/console-proxy/server/js/ajaxkeys.js 677962b 
> 
> Diff: https://reviews.apache.org/r/12245/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Sanjay Tripathi
> 
>

RE: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?



> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Monday, July 08, 2013 1:26 PM
> To: Edison Su
> Cc: 
> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?
> 
> On Mon, Jul 08, 2013 at 05:15:19PM +, Edison Su wrote:
> >
> >
> > > -Original Message-
> > > From: Chip Childers [mailto:chip.child...@sungard.com]
> > > Sent: Monday, July 08, 2013 6:46 AM
> > > To: ; Edison Su
> > > Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in
> 4.2?
> > >
> > > On Mon, Jul 8, 2013 at 9:22 AM, David Nalley  wrote:
> > > > On Wed, Jul 3, 2013 at 5:29 PM, Edison Su 
> wrote:
> > > >> Due to object store refactor, Swift is broken. The reason, is
> > > >> that, we only
> > > have S3 test environment in our lab, so only S3 is tested for now.
> > > >> Before adding the feature back, I'd better ask from, the
> > > >> community, do
> > > we want to support Swift? If so, which version of Swift? This will
> > > take some efforts to support Swift, are there any volunteers can help the
> integration?
> > > >
> > > >
> > > > Whats the bug ID for this?
> > > > Unplanned/Unannounced deprecation of a feature is a blocker IMO.
> > > > It engenders a bad relationship with our users, and strands them
> > > > on previous versions with no good migration/upgrade path.
> > > >
> > > > --David
> > > >
> > >
> > > Edison, How broken is it?  Is it shorter to fix or revert the object
> > > store changes?
> > It's not working at all. Not sure, revert object store will change it or 
> > not, as
> this feature is not tested by QA for a long time.
> >
> >
> 
> So any idea what the effort of fixing it looks like?  I mean, just because it

If it's ok to use S3 api talking to swift, then there is zero effort to support 
Swift.
But who will make the decision?

> wasn't tested in the last couple of releases doesn't necessarily mean that it
> wasn't working.  As Sudha mentioned, it wasn't tested only because of a lack
> of change that triggered the expected need to perform regression testing of
> that feature.
> 
> I believe that this was an honest mistake, but we need to figure out what to
> do.  I'm -1 on us saying "we'll drop Swift support".  If necessary, I'd say 
> that
> we need to roll back the object-store branch merge...  I don't want to see
> that happen though.  That's why I'm asking about effort to fix it.
> 
> -chip

Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?

On Tue, Jul 09, 2013 at 06:12:22PM +, Edison Su wrote:
> If it's ok to use S3 api talking to swift, then there is zero effort to 
> support Swift.
> But who will make the decision?

We, as a community.  It's *always* that answer.

If you are proposing this as the corrective path, then ok...  let's see
if others have opinions about this though.

Heres how I see it:

Pros - 
 * Code within the master branch has functional S3 API support
 * We seem to have more contribution around this interface spec
 * Having S3 as the only non-NFS secondary storage API reduces the
   long-term support / test efforts

Cons -
 * We may have an expectation issue for existing users that only have the
   native Swift API enabled in their environment (although I'm not aware
   of the Swift API's stability between their releases)
 * We haven't tested Swift as an S3 API provider yet (but could).

Personally, if it gets tested and proven to work as well or better than
other S3 providers, I'm +1 on this being the remediation approach.

Others?

Re: Review Request 12327: dnsmasq propagation to vpc routervm


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

(Updated July 9, 2013, 6:38 p.m.)


Review request for cloudstack, Jayapal Reddy, Murali Reddy, and Prasanna 
Santhanam.


Bugs: CLOUDSTACK-3357


Repository: cloudstack-git


Description
---

dnsmasq propagation to vpc routervm


Diffs
-

  server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java 
ddfa998 
  
server/src/com/cloud/network/router/VpcVirtualNetworkApplianceManagerImpl.java 
7115499 
  
server/test/com/cloud/network/router/VpcVirtualNetworkApplianceManagerImplTest.java
 PRE-CREATION 

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


Testing
---

a bassc unit test
manual creation of vpc with a networkdomain


Thanks,

daan Hoogland

Re: Review Request 12327: dnsmasq propagation to vpc routervm


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


Getting this error after applying to master:

Tests in error: 
  
testConfigDnsMasq(com.cloud.network.router.VpcVirtualNetworkApplianceManagerImplTest):
 Failed to load ApplicationContext

- Chip Childers


On July 9, 2013, 6:38 p.m., daan Hoogland wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12327/
> ---
> 
> (Updated July 9, 2013, 6:38 p.m.)
> 
> 
> Review request for cloudstack, Jayapal Reddy, Murali Reddy, and Prasanna 
> Santhanam.
> 
> 
> Bugs: CLOUDSTACK-3357
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> dnsmasq propagation to vpc routervm
> 
> 
> Diffs
> -
> 
>   server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java 
> ddfa998 
>   
> server/src/com/cloud/network/router/VpcVirtualNetworkApplianceManagerImpl.java
>  7115499 
>   
> server/test/com/cloud/network/router/VpcVirtualNetworkApplianceManagerImplTest.java
>  PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/12327/diff/
> 
> 
> Testing
> ---
> 
> a bassc unit test
> manual creation of vpc with a networkdomain
> 
> 
> Thanks,
> 
> daan Hoogland
> 
>

Re: Review Request 12327: dnsmasq propagation to vpc routervm



> On July 9, 2013, 6:41 p.m., Chip Childers wrote:
> > Getting this error after applying to master:
> > 
> > Tests in error: 
> >   
> > testConfigDnsMasq(com.cloud.network.router.VpcVirtualNetworkApplianceManagerImplTest):
> >  Failed to load ApplicationContext

FWIW, outside of the test failure this looks good to me.


- Chip


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


On July 9, 2013, 6:38 p.m., daan Hoogland wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12327/
> ---
> 
> (Updated July 9, 2013, 6:38 p.m.)
> 
> 
> Review request for cloudstack, Jayapal Reddy, Murali Reddy, and Prasanna 
> Santhanam.
> 
> 
> Bugs: CLOUDSTACK-3357
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> dnsmasq propagation to vpc routervm
> 
> 
> Diffs
> -
> 
>   server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java 
> ddfa998 
>   
> server/src/com/cloud/network/router/VpcVirtualNetworkApplianceManagerImpl.java
>  7115499 
>   
> server/test/com/cloud/network/router/VpcVirtualNetworkApplianceManagerImplTest.java
>  PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/12327/diff/
> 
> 
> Testing
> ---
> 
> a bassc unit test
> manual creation of vpc with a networkdomain
> 
> 
> Thanks,
> 
> daan Hoogland
> 
>

RE: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?



> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Tuesday, July 09, 2013 11:22 AM
> To: Edison Su
> Cc: 
> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?
> 
> On Tue, Jul 09, 2013 at 06:12:22PM +, Edison Su wrote:
> > If it's ok to use S3 api talking to swift, then there is zero effort to 
> > support
> Swift.
> > But who will make the decision?
> 
> We, as a community.  It's *always* that answer.
> 
> If you are proposing this as the corrective path, then ok...  let's see if 
> others
> have opinions about this though.
> 
> Heres how I see it:
> 
> Pros -
>  * Code within the master branch has functional S3 API support
>  * We seem to have more contribution around this interface spec
>  * Having S3 as the only non-NFS secondary storage API reduces the
>long-term support / test efforts
> 
> Cons -
>  * We may have an expectation issue for existing users that only have the
>native Swift API enabled in their environment (although I'm not aware
>of the Swift API's stability between their releases)

I think you get into the same situation as I did, without input from users who 
is using Swift, or the company who is supporting Swift, what we are talking 
about here is just hypothetic.
If we really want to support Swift, and support it better, we need to get 
domain expert involved in the discuss.

>  * We haven't tested Swift as an S3 API provider yet (but could).
> 
> Personally, if it gets tested and proven to work as well or better than other
> S3 providers, I'm +1 on this being the remediation approach.
> 
> Others?

Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?

On Tue, Jul 09, 2013 at 06:55:03PM +, Edison Su wrote:
> 
> 
> > -Original Message-
> > From: Chip Childers [mailto:chip.child...@sungard.com]
> > Sent: Tuesday, July 09, 2013 11:22 AM
> > To: Edison Su
> > Cc: 
> > Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 
> > 4.2?
> > 
> > On Tue, Jul 09, 2013 at 06:12:22PM +, Edison Su wrote:
> > > If it's ok to use S3 api talking to swift, then there is zero effort to 
> > > support
> > Swift.
> > > But who will make the decision?
> > 
> > We, as a community.  It's *always* that answer.
> > 
> > If you are proposing this as the corrective path, then ok...  let's see if 
> > others
> > have opinions about this though.
> > 
> > Heres how I see it:
> > 
> > Pros -
> >  * Code within the master branch has functional S3 API support
> >  * We seem to have more contribution around this interface spec
> >  * Having S3 as the only non-NFS secondary storage API reduces the
> >long-term support / test efforts
> > 
> > Cons -
> >  * We may have an expectation issue for existing users that only have the
> >native Swift API enabled in their environment (although I'm not aware
> >of the Swift API's stability between their releases)
> 
> I think you get into the same situation as I did, without input from users 
> who is using Swift, or the company who is supporting Swift, what we are 
> talking about here is just hypothetic.
> If we really want to support Swift, and support it better, we need to get 
> domain expert involved in the discuss.

Does your $dayjob happen to have a customer that might be using this
integration?  If so, could your $dayjob product manager chime in on the
discussion?

> 
> >  * We haven't tested Swift as an S3 API provider yet (but could).
> > 
> > Personally, if it gets tested and proven to work as well or better than 
> > other
> > S3 providers, I'm +1 on this being the remediation approach.
> > 
> > Others?
>

Re: [jira] [Commented] (CLOUDSTACK-3417) [Upgrade to 4.2.0] Upgrade to 4.2.0 fails with om.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'cloud.baremetal_dhcp_devices' doesn't exist

Was this fixed in the 4.1 branch as well?

On Tue, Jul 09, 2013 at 07:09:52PM +, Alena Prokharchyk (JIRA) wrote:
> 
> [ 
> https://issues.apache.org/jira/browse/CLOUDSTACK-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703664#comment-13703664
>  ] 
> 
> Alena Prokharchyk commented on CLOUDSTACK-3417:
> ---
> 
> Fixed the missing table problem. Add it as a part of 306-41 upgrade. Now 
> reassigning the bug to Sheng as he needs to fix the foreign key insertion 
> portion for those tables. Currently the keys are being inserted in .sql file; 
> it should be moved to java part of the code and be inserted only when they 
> don't exist. Because some setups might have those keys, and some might miss 
> them. if the setup has the keys, you run into this exception during the 
> upgrade:
> 
> INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Database upgrade must 
> be performed from 3.0.6.2013-07-09T18:58:51Z to 4.2.0-SNAPSHOT
> ERROR [utils.db.ScriptRunner] (Timer-2:) Error executing: ALTER TABLE 
> `cloud`.`baremetal_dhcp_devices` ADD CONSTRAINT 
> `fk_external_dhcp_devices_nsp_id` FOREIGN KEY (`nsp_id`) REFERENCES 
> `physical_network_service_providers` (`id`) ON DELETE CASCADE
> ERROR [utils.db.ScriptRunner] (Timer-2:) java.sql.SQLException: Can't create 
> table 'cloud.#sql-c2_bc' (errno: 121)
> ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Unable to execute 
> upgrade script: 
> /Users/alena/campo/client/target/utilities/scripts/db/db/schema-410to420.sql
> java.sql.SQLException: Can't create table 'cloud.#sql-c2_bc' (errno: 121)
>   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:193)
>   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
>   at 
> com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java
> 
> > [Upgrade to 4.2.0] Upgrade to 4.2.0 fails with 
> > om.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 
> > 'cloud.baremetal_dhcp_devices' doesn't exist 
> > 
> >
> > Key: CLOUDSTACK-3417
> > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3417
> > Project: CloudStack
> >  Issue Type: Bug
> >  Security Level: Public(Anyone can view this level - this is the 
> > default.) 
> >  Components: Install and Setup
> >Affects Versions: 4.2.0
> >Reporter: Abhinav Roy
> >Assignee: Alena Prokharchyk
> >Priority: Blocker
> > Fix For: 4.2.0
> >
> > Attachments: management-server.log
> >
> >
> > Upgrade from CS 3.0.6 to 4.2.0 fails with the following error :
> > 2013-07-09 16:08:56,133 ERROR [utils.db.ScriptRunner] (Timer-1:null) 
> > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 
> > 'cloud.baremetal_dhcp_devices' doesn't exist
> > 2013-07-09 16:08:56,135 ERROR [cloud.upgrade.DatabaseUpgradeChecker] 
> > (Timer-1:null) Unable to execute upgrade script: 
> > /usr/share/cloudstack-management/setup/db/schema-410to420.sql
> > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 
> > 'cloud.baremetal_dhcp_devices' doesn't exist
> > at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:193)
> > at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
> > at 
> > com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:211)
> > at 
> > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:272)
> > at 
> > com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:401)
> > at 
> > com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
> > at 
> > com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
> > at java.util.TimerThread.mainLoop(Timer.java:534)
> > at java.util.TimerThread.run(Timer.java:484)
> > 2013-07-09 16:08:56,139 ERROR [cloud.upgrade.DatabaseUpgradeChecker] 
> > (Timer-1:null) Unable to upgrade the database
> > com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade 
> > script: /usr/share/cloudstack-management/setup/db/schema-410to420.sql
> > at 
> > com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:220)
> > at 
> > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:272)
> > at 
> > com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:401)
> > at 
> > com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
> > at 
> > com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
> > at java.util.Time

Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?

Edison,

Swift does not support S3 multi-part uploads [1] which CloudStack must use in 
order to store files larger than 5 GB.  Therefore, using the Swift's S3 
compatibility layer is not a viable workaround.

Thanks,
-John

[1]:  https://wiki.openstack.org/wiki/Swift/APIFeatureComparison

On Jul 9, 2013, at 2:12 PM, Edison Su  wrote:

> 
> 
>> -Original Message-
>> From: Chip Childers [mailto:chip.child...@sungard.com]
>> Sent: Monday, July 08, 2013 1:26 PM
>> To: Edison Su
>> Cc: 
>> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?
>> 
>> On Mon, Jul 08, 2013 at 05:15:19PM +, Edison Su wrote:
>>> 
>>> 
 -Original Message-
 From: Chip Childers [mailto:chip.child...@sungard.com]
 Sent: Monday, July 08, 2013 6:46 AM
 To: ; Edison Su
 Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in
>> 4.2?
 
 On Mon, Jul 8, 2013 at 9:22 AM, David Nalley  wrote:
> On Wed, Jul 3, 2013 at 5:29 PM, Edison Su 
>> wrote:
>> Due to object store refactor, Swift is broken. The reason, is
>> that, we only
 have S3 test environment in our lab, so only S3 is tested for now.
>> Before adding the feature back, I'd better ask from, the
>> community, do
 we want to support Swift? If so, which version of Swift? This will
 take some efforts to support Swift, are there any volunteers can help the
>> integration?
> 
> 
> Whats the bug ID for this?
> Unplanned/Unannounced deprecation of a feature is a blocker IMO.
> It engenders a bad relationship with our users, and strands them
> on previous versions with no good migration/upgrade path.
> 
> --David
> 
 
 Edison, How broken is it?  Is it shorter to fix or revert the object
 store changes?
>>> It's not working at all. Not sure, revert object store will change it or 
>>> not, as
>> this feature is not tested by QA for a long time.
>>> 
>>> 
>> 
>> So any idea what the effort of fixing it looks like?  I mean, just because it
> 
> If it's ok to use S3 api talking to swift, then there is zero effort to 
> support Swift.
> But who will make the decision?
> 
>> wasn't tested in the last couple of releases doesn't necessarily mean that it
>> wasn't working.  As Sudha mentioned, it wasn't tested only because of a lack
>> of change that triggered the expected need to perform regression testing of
>> that feature.
>> 
>> I believe that this was an honest mistake, but we need to figure out what to
>> do.  I'm -1 on us saying "we'll drop Swift support".  If necessary, I'd say 
>> that
>> we need to roll back the object-store branch merge...  I don't want to see
>> that happen though.  That's why I'm asking about effort to fix it.
>> 
>> -chip

Review Request 12369: Ignore network interfaces without uuids when passing extra config to ESX for nvp

2013-07-09 Thread Venkata Siva Vijayendra Bhamidipati


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

Review request for cloudstack, Chip Childers, Kelven Yang, Sateesh 
Chodapuneedi, and Hugo Trippaers.


Bugs: CLOUDSTACK-3425


Repository: cloudstack-git


Description
---

The VR gets plumbed with 5 interfaces (passed to vmware resource as nicTOs) but 
only three of them are initialized. The other two aren't used rightaway until 
configured later. The extra configs being built and passed on to ESX as part of 
NVP integration is copying over all the 5 nic configs but two of them don't 
have uuids, so the VM reconfigure task fails because of unset values of 
nvp-iface* and VR startup fails. Fixing this by ignoring those unused 
interfaces when building extra configs.


Diffs
-

  
plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java
 372cc1b 

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


Testing
---

With the fix, the VR comes up successfully, and guest VMs get created.


Thanks,

Venkata Siva Vijayendra Bhamidipati

Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?

2013-07-09 Thread Sebastien Goasguen

if swift does not work anymore in 4.0 or 4.1 maybe be should inform swiftstack:
http://swiftstack.com/cloudstack/


On Jul 9, 2013, at 3:57 PM, John Burwell  wrote:

> Edison,
> 
> Swift does not support S3 multi-part uploads [1] which CloudStack must use in 
> order to store files larger than 5 GB.  Therefore, using the Swift's S3 
> compatibility layer is not a viable workaround.
> 
> Thanks,
> -John
> 
> [1]:  https://wiki.openstack.org/wiki/Swift/APIFeatureComparison
> 
> On Jul 9, 2013, at 2:12 PM, Edison Su  wrote:
> 
>> 
>> 
>>> -Original Message-
>>> From: Chip Childers [mailto:chip.child...@sungard.com]
>>> Sent: Monday, July 08, 2013 1:26 PM
>>> To: Edison Su
>>> Cc: 
>>> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 
>>> 4.2?
>>> 
>>> On Mon, Jul 08, 2013 at 05:15:19PM +, Edison Su wrote:
 
 
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Monday, July 08, 2013 6:46 AM
> To: ; Edison Su
> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in
>>> 4.2?
> 
> On Mon, Jul 8, 2013 at 9:22 AM, David Nalley  wrote:
>> On Wed, Jul 3, 2013 at 5:29 PM, Edison Su 
>>> wrote:
>>> Due to object store refactor, Swift is broken. The reason, is
>>> that, we only
> have S3 test environment in our lab, so only S3 is tested for now.
>>> Before adding the feature back, I'd better ask from, the
>>> community, do
> we want to support Swift? If so, which version of Swift? This will
> take some efforts to support Swift, are there any volunteers can help the
>>> integration?
>> 
>> 
>> Whats the bug ID for this?
>> Unplanned/Unannounced deprecation of a feature is a blocker IMO.
>> It engenders a bad relationship with our users, and strands them
>> on previous versions with no good migration/upgrade path.
>> 
>> --David
>> 
> 
> Edison, How broken is it?  Is it shorter to fix or revert the object
> store changes?
 It's not working at all. Not sure, revert object store will change it or 
 not, as
>>> this feature is not tested by QA for a long time.
 
 
>>> 
>>> So any idea what the effort of fixing it looks like?  I mean, just because 
>>> it
>> 
>> If it's ok to use S3 api talking to swift, then there is zero effort to 
>> support Swift.
>> But who will make the decision?
>> 
>>> wasn't tested in the last couple of releases doesn't necessarily mean that 
>>> it
>>> wasn't working.  As Sudha mentioned, it wasn't tested only because of a lack
>>> of change that triggered the expected need to perform regression testing of
>>> that feature.
>>> 
>>> I believe that this was an honest mistake, but we need to figure out what to
>>> do.  I'm -1 on us saying "we'll drop Swift support".  If necessary, I'd say 
>>> that
>>> we need to roll back the object-store branch merge...  I don't want to see
>>> that happen though.  That's why I'm asking about effort to fix it.
>>> 
>>> -chip
>

Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?

On Tue, Jul 9, 2013 at 4:06 PM, Sebastien Goasguen  wrote:
> if swift does not work anymore in 4.0 or 4.1 maybe be should inform 
> swiftstack:
> http://swiftstack.com/cloudstack/

Just to be clear, we're not sure about 4.0 or 4.1 at all.  All that
has been said is that it wasn't in the test plan for those releases,
due to no reason to add them to the regression testing plans being
shared with any of the testers.  ;-)

RE: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?

It sounds like there are a lot of work to do, to support multi-part upload:

http://www.mirantis.com/blog/large-objects-in-cloud-storages/
" As you can see, Amazon S3 API is more high-level while Swift API for large 
objects is pretty raw. Swift doesn't make a distinction between objects and 
object parts. This means it's the user's duty to take care of the parts. E.g., 
you should make sure that the prefix in the manifest doesn't match other 
objects by mistake. If you want to delete an object, you have to remove its 
parts as well, and so on. "
So it's a new issue that not happened on previous release.

> -Original Message-
> From: John Burwell [mailto:jburw...@basho.com]
> Sent: Tuesday, July 09, 2013 12:57 PM
> To: dev@cloudstack.apache.org
> Cc: 'Chip Childers'
> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?
> 
> Edison,
> 
> Swift does not support S3 multi-part uploads [1] which CloudStack must use
> in order to store files larger than 5 GB.  Therefore, using the Swift's S3
> compatibility layer is not a viable workaround.
> 
> Thanks,
> -John
> 
> [1]:  https://wiki.openstack.org/wiki/Swift/APIFeatureComparison
> 
> On Jul 9, 2013, at 2:12 PM, Edison Su  wrote:
> 
> >
> >
> >> -Original Message-
> >> From: Chip Childers [mailto:chip.child...@sungard.com]
> >> Sent: Monday, July 08, 2013 1:26 PM
> >> To: Edison Su
> >> Cc: 
> >> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 
> >> 4.2?
> >>
> >> On Mon, Jul 08, 2013 at 05:15:19PM +, Edison Su wrote:
> >>>
> >>>
>  -Original Message-
>  From: Chip Childers [mailto:chip.child...@sungard.com]
>  Sent: Monday, July 08, 2013 6:46 AM
>  To: ; Edison Su
>  Subject: Re: Swift in 4.2 is broken, anybody wants it to be
>  supported in
> >> 4.2?
> 
>  On Mon, Jul 8, 2013 at 9:22 AM, David Nalley  wrote:
> > On Wed, Jul 3, 2013 at 5:29 PM, Edison Su 
> >> wrote:
> >> Due to object store refactor, Swift is broken. The reason, is
> >> that, we only
>  have S3 test environment in our lab, so only S3 is tested for now.
> >> Before adding the feature back, I'd better ask from, the
> >> community, do
>  we want to support Swift? If so, which version of Swift? This will
>  take some efforts to support Swift, are there any volunteers can
>  help the
> >> integration?
> >
> >
> > Whats the bug ID for this?
> > Unplanned/Unannounced deprecation of a feature is a blocker IMO.
> > It engenders a bad relationship with our users, and strands them
> > on previous versions with no good migration/upgrade path.
> >
> > --David
> >
> 
>  Edison, How broken is it?  Is it shorter to fix or revert the
>  object store changes?
> >>> It's not working at all. Not sure, revert object store will change
> >>> it or not, as
> >> this feature is not tested by QA for a long time.
> >>>
> >>>
> >>
> >> So any idea what the effort of fixing it looks like?  I mean, just
> >> because it
> >
> > If it's ok to use S3 api talking to swift, then there is zero effort to 
> > support
> Swift.
> > But who will make the decision?
> >
> >> wasn't tested in the last couple of releases doesn't necessarily mean
> >> that it wasn't working.  As Sudha mentioned, it wasn't tested only
> >> because of a lack of change that triggered the expected need to
> >> perform regression testing of that feature.
> >>
> >> I believe that this was an honest mistake, but we need to figure out
> >> what to do.  I'm -1 on us saying "we'll drop Swift support".  If
> >> necessary, I'd say that we need to roll back the object-store branch
> >> merge...  I don't want to see that happen though.  That's why I'm asking
> about effort to fix it.
> >>
> >> -chip

RE: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?

Could they(swiftstack) help us, or guide us on how to implement multi-part 
upload?

> -Original Message-
> From: Sebastien Goasguen [mailto:run...@gmail.com]
> Sent: Tuesday, July 09, 2013 1:07 PM
> To: dev@cloudstack.apache.org
> Cc: 'Chip Childers'
> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?
> 
> if swift does not work anymore in 4.0 or 4.1 maybe be should inform
> swiftstack:
> http://swiftstack.com/cloudstack/
> 
> 
> On Jul 9, 2013, at 3:57 PM, John Burwell  wrote:
> 
> > Edison,
> >
> > Swift does not support S3 multi-part uploads [1] which CloudStack must use
> in order to store files larger than 5 GB.  Therefore, using the Swift's S3
> compatibility layer is not a viable workaround.
> >
> > Thanks,
> > -John
> >
> > [1]:  https://wiki.openstack.org/wiki/Swift/APIFeatureComparison
> >
> > On Jul 9, 2013, at 2:12 PM, Edison Su  wrote:
> >
> >>
> >>
> >>> -Original Message-
> >>> From: Chip Childers [mailto:chip.child...@sungard.com]
> >>> Sent: Monday, July 08, 2013 1:26 PM
> >>> To: Edison Su
> >>> Cc: 
> >>> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in
> 4.2?
> >>>
> >>> On Mon, Jul 08, 2013 at 05:15:19PM +, Edison Su wrote:
> 
> 
> > -Original Message-
> > From: Chip Childers [mailto:chip.child...@sungard.com]
> > Sent: Monday, July 08, 2013 6:46 AM
> > To: ; Edison Su
> > Subject: Re: Swift in 4.2 is broken, anybody wants it to be
> > supported in
> >>> 4.2?
> >
> > On Mon, Jul 8, 2013 at 9:22 AM, David Nalley  wrote:
> >> On Wed, Jul 3, 2013 at 5:29 PM, Edison Su 
> >>> wrote:
> >>> Due to object store refactor, Swift is broken. The reason, is
> >>> that, we only
> > have S3 test environment in our lab, so only S3 is tested for now.
> >>> Before adding the feature back, I'd better ask from, the
> >>> community, do
> > we want to support Swift? If so, which version of Swift? This will
> > take some efforts to support Swift, are there any volunteers can
> > help the
> >>> integration?
> >>
> >>
> >> Whats the bug ID for this?
> >> Unplanned/Unannounced deprecation of a feature is a blocker IMO.
> >> It engenders a bad relationship with our users, and strands them
> >> on previous versions with no good migration/upgrade path.
> >>
> >> --David
> >>
> >
> > Edison, How broken is it?  Is it shorter to fix or revert the
> > object store changes?
>  It's not working at all. Not sure, revert object store will change
>  it or not, as
> >>> this feature is not tested by QA for a long time.
> 
> 
> >>>
> >>> So any idea what the effort of fixing it looks like?  I mean, just
> >>> because it
> >>
> >> If it's ok to use S3 api talking to swift, then there is zero effort to 
> >> support
> Swift.
> >> But who will make the decision?
> >>
> >>> wasn't tested in the last couple of releases doesn't necessarily
> >>> mean that it wasn't working.  As Sudha mentioned, it wasn't tested
> >>> only because of a lack of change that triggered the expected need to
> >>> perform regression testing of that feature.
> >>>
> >>> I believe that this was an honest mistake, but we need to figure out
> >>> what to do.  I'm -1 on us saying "we'll drop Swift support".  If
> >>> necessary, I'd say that we need to roll back the object-store branch
> >>> merge...  I don't want to see that happen though.  That's why I'm asking
> about effort to fix it.
> >>>
> >>> -chip
> >

Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?

2013-07-09 Thread Joe Brockmeier

On Tue, Jul 9, 2013, at 03:15 PM, Edison Su wrote:
> Could they(swiftstack) help us, or guide us on how to implement
> multi-part upload?

I've sent an email to John at SwiftStack to see if they might be able to
jump into the conversation. 

Best,

jzb
-- 
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

Re: Review Request 11479: SolidFire storage plug-in and enhancements to the storage framework and GUI

> On June 28, 2013, 3:42 p.m., John Burwell wrote:
> > core/src/com/cloud/agent/api/AttachVolumeCommand.java, line 61
> > 
> >
> > Fix formatting/continuation from the previous line

I think I fixed all formatting issues in this file.

> On June 28, 2013, 3:42 p.m., John Burwell wrote:
> > engine/storage/src/org/apache/cloudstack/storage/datastore/PrimaryDataStoreEntityImpl.java,
> >  line 181
> > 
> >
> > What is the resolution of this TODO?  It appears that this getter is 
> > broken as it doesn't return a parameter value.

It appears this class has been removed from the codebase.

> On June 28, 2013, 3:42 p.m., John Burwell wrote:
> > engine/storage/volume/src/org/apache/cloudstack/storage/datastore/lifecycle/DefaultPrimaryDataStoreLifeCycleImpl.java,
> >  line 111
> > 
> >
> > I know it is out of the scope of this patch, but please correct the 
> > name of this method on the interface and all implementations to conform to 
> > JavaBean property standard.  Accessors for boolean properties should be 
> > named is.  Failure to conform to this convention will 
> > interfere with any reflection tools we elect to use.

This method no longer seems to be present in the codebase.

> On June 28, 2013, 3:42 p.m., John Burwell wrote:
> > plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java,
> >  line 3789
> > 
> >
> > 1) Don't throw Exception generically.  Throw out the specific 
> > exceptions that can occur.
> > 2) What is the error handling here?  This method has no recovery 
> > provisions.  A failure could leave dangling resources.  Seems that we 
> > should be catching Exception, and attempting to undo the operations 
> > performed, and then re-throwing the exception as a CloudRuntimeException.

I agree exceptions should be more specific. The problem here is that this 
VMware code (the VmwareResource class itself) was written with generic 
exception handling all over the place. I think if we want to correct this, it 
will take a larger effort (therefore I'm thinking this change is out of scope 
for this release).

> On June 28, 2013, 3:42 p.m., John Burwell wrote:
> > plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java,
> >  line 3813
> > 
> >
> > Exception is too broad.  Throw a CloudRuntimeException.

I agree exceptions should be more specific. The problem here is that this 
VMware code (the VmwareResource class itself) was written with generic 
exception handling all over the place. I think if we want to correct this, it 
will take a larger effort (therefore I'm thinking this change is out of scope 
for this release).

> On June 28, 2013, 3:42 p.m., John Burwell wrote:
> > plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java,
> >  line 3816
> > 
> >
> > Casting down from a long to int seems dangerous.  Why are casting this 
> > value down?

The VMware API is expecting an int referencing the size in MBs. This code here 
is copied/pasted from another location in the VmwareResource file where the 
same conversion happens.

I have made a utility function for this.

> On June 28, 2013, 3:42 p.m., John Burwell wrote:
> > plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java,
> >  line 3891
> > 
> >
> > 1) Strip out tab characters
> > 2) Fix indentation
> > 3) Don't throw Exception -- it's too generic.  Seems that we should be 
> > catching Exception, and attempting to undo any operations performed in 
> > order to ensure that we don't leave the hypervisor in an inconsistent state 
> > then rethrowing the exception as a CloudRuntimeException.

I agree exceptions should be more specific. The problem here is that this 
VMware code (the VmwareResource class itself) was written with generic 
exception handling all over the place. I think if we want to correct this, it 
will take a larger effort (therefore I'm thinking this change is out of scope 
for this release).

> On June 28, 2013, 3:42 p.m., John Burwell wrote:
> > plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java,
> >  line 3955
> > 
> >
> > Why are we locking a variable with local method scope?  There should be 
> > *no* need to synchronize here, and it is very expensive.

It is actually a local variable that has been passed into multiple threads t

Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?

Edison,

TL;DR The shorter path is to re-implement/fix the Swift driver.

Multipart upload would need to implemented in Swift, not in CloudStack.  
Therefore, such a change would need to be accepted and released by the 
OpenStack project before the 4.2.0 release.  We would also be stranding any of 
our current users who cannot or will not upgrade their Swift instances.

Knowing what it took to implement it in Riak CS, multi-part upload was a lot of 
work to implement in a Dynamo-based system.  The S3 has the following 
three-phase process:

1. Initiate a Upload: Declare the number of parts and their size
2. Submit each part per the definition in Step 1 (e.g. 50 parts = 50 
HTTP PUTs)
3. Complete the multi-part upload: Declare that all parts have been 
uploaded which causes the object to become available

In contrast, Swift uses HTTP chunking to solve the same problem with one API 
call.  In addition to providing all of the reliability guarantees of the S3 
API, an implementor of S3 multipart uploads will have to provide a way to 
translate the 3-phase model into the single call model used by Swift.  

Thanks,
-John

On Jul 9, 2013, at 4:15 PM, Edison Su  wrote:

> Could they(swiftstack) help us, or guide us on how to implement multi-part 
> upload?
> 
>> -Original Message-
>> From: Sebastien Goasguen [mailto:run...@gmail.com]
>> Sent: Tuesday, July 09, 2013 1:07 PM
>> To: dev@cloudstack.apache.org
>> Cc: 'Chip Childers'
>> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?
>> 
>> if swift does not work anymore in 4.0 or 4.1 maybe be should inform
>> swiftstack:
>> http://swiftstack.com/cloudstack/
>> 
>> 
>> On Jul 9, 2013, at 3:57 PM, John Burwell  wrote:
>> 
>>> Edison,
>>> 
>>> Swift does not support S3 multi-part uploads [1] which CloudStack must use
>> in order to store files larger than 5 GB.  Therefore, using the Swift's S3
>> compatibility layer is not a viable workaround.
>>> 
>>> Thanks,
>>> -John
>>> 
>>> [1]:  https://wiki.openstack.org/wiki/Swift/APIFeatureComparison
>>> 
>>> On Jul 9, 2013, at 2:12 PM, Edison Su  wrote:
>>> 

> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Monday, July 08, 2013 1:26 PM
> To: Edison Su
> Cc: 
> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in
>> 4.2?
> 
> On Mon, Jul 08, 2013 at 05:15:19PM +, Edison Su wrote:
>> 
>> 
>>> -Original Message-
>>> From: Chip Childers [mailto:chip.child...@sungard.com]
>>> Sent: Monday, July 08, 2013 6:46 AM
>>> To: ; Edison Su
>>> Subject: Re: Swift in 4.2 is broken, anybody wants it to be
>>> supported in
> 4.2?
>>> 
>>> On Mon, Jul 8, 2013 at 9:22 AM, David Nalley  wrote:
 On Wed, Jul 3, 2013 at 5:29 PM, Edison Su 
> wrote:
> Due to object store refactor, Swift is broken. The reason, is
> that, we only
>>> have S3 test environment in our lab, so only S3 is tested for now.
> Before adding the feature back, I'd better ask from, the
> community, do
>>> we want to support Swift? If so, which version of Swift? This will
>>> take some efforts to support Swift, are there any volunteers can
>>> help the
> integration?

 Whats the bug ID for this?
 Unplanned/Unannounced deprecation of a feature is a blocker IMO.
 It engenders a bad relationship with our users, and strands them
 on previous versions with no good migration/upgrade path.

 --David

>>> 
>>> Edison, How broken is it?  Is it shorter to fix or revert the
>>> object store changes?
>> It's not working at all. Not sure, revert object store will change
>> it or not, as
> this feature is not tested by QA for a long time.
>> 
>> 
> 
> So any idea what the effort of fixing it looks like?  I mean, just
> because it

 If it's ok to use S3 api talking to swift, then there is zero effort to 
 support
>> Swift.
 But who will make the decision?

> wasn't tested in the last couple of releases doesn't necessarily
> mean that it wasn't working.  As Sudha mentioned, it wasn't tested
> only because of a lack of change that triggered the expected need to
> perform regression testing of that feature.
> 
> I believe that this was an honest mistake, but we need to figure out
> what to do.  I'm -1 on us saying "we'll drop Swift support".  If
> necessary, I'd say that we need to roll back the object-store branch
> merge...  I don't want to see that happen though.  That's why I'm asking
>> about effort to fix it.
> 
> -chip
>>> 
>

Re: Review Request 12364: Follow up fix for CLOUDSTACK-2777


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


Commit 3e7cebee2967e3523cb679ef30fcb19f7949c2dc in branch refs/heads/ui-ucs 
from rayeesn
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3e7cebe ]

Followup fix for CLOUDSTACK-2777, crypto.properties and xes.keystore moved to 
AWSAPI installation location and changed permission to 666


- ASF Subversion and Git Services


On July 9, 2013, 3:20 p.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12364/
> ---
> 
> (Updated July 9, 2013, 3:20 p.m.)
> 
> 
> Review request for cloudstack, Likitha Shetty and Prachi Damle.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Followup fix for CLOUDSTACK-2777, crypto.properties and xes.keystore moved to 
> AWSAPI installation location and changed permission  to 666
> 
> 
> Diffs
> -
> 
>   packaging/centos63/cloud.spec f7eb629 
> 
> Diff: https://reviews.apache.org/r/12364/diff/
> 
> 
> Testing
> ---
> 
> Tested 
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

RE: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?



> -Original Message-
> From: John Burwell [mailto:jburw...@basho.com]
> Sent: Tuesday, July 09, 2013 1:31 PM
> To: dev@cloudstack.apache.org
> Cc: 'Chip Childers'
> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?
> 
> Edison,
> 
> TL;DR The shorter path is to re-implement/fix the Swift driver.
> 
> Multipart upload would need to implemented in Swift, not in CloudStack.
> Therefore, such a change would need to be accepted and released by the
> OpenStack project before the 4.2.0 release.  We would also be stranding any
> of our current users who cannot or will not upgrade their Swift instances.
> 
> Knowing what it took to implement it in Riak CS, multi-part upload was a lot
> of work to implement in a Dynamo-based system.  The S3 has the following
> three-phase process:
> 
>   1. Initiate a Upload: Declare the number of parts and their size
>   2. Submit each part per the definition in Step 1 (e.g. 50 parts = 50
> HTTP PUTs)
>   3. Complete the multi-part upload: Declare that all parts have been
> uploaded which causes the object to become available
> 
> In contrast, Swift uses HTTP chunking to solve the same problem with one
> API call.  In addition to providing all of the reliability guarantees of the 
> S3 API,
> an implementor of S3 multipart uploads will have to provide a way to
> translate the 3-phase model into the single call model used by Swift.

Seems swift client can support upload files more than 5GB: 
http://fedoraproject.org/wiki/QA:Testcase_Swift_Upload_Large_File

Ok, so we should just re-implement/fix the existing swift driver.

> 
> Thanks,
> -John
> 
> On Jul 9, 2013, at 4:15 PM, Edison Su  wrote:
> 
> > Could they(swiftstack) help us, or guide us on how to implement multi-part
> upload?
> >
> >> -Original Message-
> >> From: Sebastien Goasguen [mailto:run...@gmail.com]
> >> Sent: Tuesday, July 09, 2013 1:07 PM
> >> To: dev@cloudstack.apache.org
> >> Cc: 'Chip Childers'
> >> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 
> >> 4.2?
> >>
> >> if swift does not work anymore in 4.0 or 4.1 maybe be should inform
> >> swiftstack:
> >> http://swiftstack.com/cloudstack/
> >>
> >>
> >> On Jul 9, 2013, at 3:57 PM, John Burwell  wrote:
> >>
> >>> Edison,
> >>>
> >>> Swift does not support S3 multi-part uploads [1] which CloudStack
> >>> must use
> >> in order to store files larger than 5 GB.  Therefore, using the
> >> Swift's S3 compatibility layer is not a viable workaround.
> >>>
> >>> Thanks,
> >>> -John
> >>>
> >>> [1]:  https://wiki.openstack.org/wiki/Swift/APIFeatureComparison
> >>>
> >>> On Jul 9, 2013, at 2:12 PM, Edison Su  wrote:
> >>>
> 
> 
> > -Original Message-
> > From: Chip Childers [mailto:chip.child...@sungard.com]
> > Sent: Monday, July 08, 2013 1:26 PM
> > To: Edison Su
> > Cc: 
> > Subject: Re: Swift in 4.2 is broken, anybody wants it to be
> > supported in
> >> 4.2?
> >
> > On Mon, Jul 08, 2013 at 05:15:19PM +, Edison Su wrote:
> >>
> >>
> >>> -Original Message-
> >>> From: Chip Childers [mailto:chip.child...@sungard.com]
> >>> Sent: Monday, July 08, 2013 6:46 AM
> >>> To: ; Edison Su
> >>> Subject: Re: Swift in 4.2 is broken, anybody wants it to be
> >>> supported in
> > 4.2?
> >>>
> >>> On Mon, Jul 8, 2013 at 9:22 AM, David Nalley 
> wrote:
>  On Wed, Jul 3, 2013 at 5:29 PM, Edison Su
>  
> > wrote:
> > Due to object store refactor, Swift is broken. The reason, is
> > that, we only
> >>> have S3 test environment in our lab, so only S3 is tested for now.
> > Before adding the feature back, I'd better ask from, the
> > community, do
> >>> we want to support Swift? If so, which version of Swift? This
> >>> will take some efforts to support Swift, are there any
> >>> volunteers can help the
> > integration?
> 
> 
>  Whats the bug ID for this?
>  Unplanned/Unannounced deprecation of a feature is a blocker
> IMO.
>  It engenders a bad relationship with our users, and strands
>  them on previous versions with no good migration/upgrade path.
> 
>  --David
> 
> >>>
> >>> Edison, How broken is it?  Is it shorter to fix or revert the
> >>> object store changes?
> >> It's not working at all. Not sure, revert object store will
> >> change it or not, as
> > this feature is not tested by QA for a long time.
> >>
> >>
> >
> > So any idea what the effort of fixing it looks like?  I mean, just
> > because it
> 
>  If it's ok to use S3 api talking to swift, then there is zero
>  effort to support
> >> Swift.
>  But who will make the decision?
> 
> > wasn't tested in the last couple of releases doesn't necessarily
> > mean that it wasn't working.  As Sudha mentioned, it wasn't tested
> > o

Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?

Edison,

I did not say that Swift can't handle files greater than 5 GB.  With S3, you 
must use multi-part uploads in order to upload a file greater than 5GB.  
Therefore, Swift's S3 compatibility layer must be compatible with the S3 
multipart upload API in order to work with CloudStack.  Please see my previous 
remarks regarding the differences in approach between the two APIs for more a 
detailed explanation regarding the incompatibilities and the difficulties for 
Swift to support S3-style multi-part uploads.

Thanks,
-John

On Jul 9, 2013, at 4:56 PM, Edison Su  wrote:

> 
> 
>> -Original Message-
>> From: John Burwell [mailto:jburw...@basho.com]
>> Sent: Tuesday, July 09, 2013 1:31 PM
>> To: dev@cloudstack.apache.org
>> Cc: 'Chip Childers'
>> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?
>> 
>> Edison,
>> 
>> TL;DR The shorter path is to re-implement/fix the Swift driver.
>> 
>> Multipart upload would need to implemented in Swift, not in CloudStack.
>> Therefore, such a change would need to be accepted and released by the
>> OpenStack project before the 4.2.0 release.  We would also be stranding any
>> of our current users who cannot or will not upgrade their Swift instances.
>> 
>> Knowing what it took to implement it in Riak CS, multi-part upload was a lot
>> of work to implement in a Dynamo-based system.  The S3 has the following
>> three-phase process:
>> 
>>  1. Initiate a Upload: Declare the number of parts and their size
>>  2. Submit each part per the definition in Step 1 (e.g. 50 parts = 50
>> HTTP PUTs)
>>  3. Complete the multi-part upload: Declare that all parts have been
>> uploaded which causes the object to become available
>> 
>> In contrast, Swift uses HTTP chunking to solve the same problem with one
>> API call.  In addition to providing all of the reliability guarantees of the 
>> S3 API,
>> an implementor of S3 multipart uploads will have to provide a way to
>> translate the 3-phase model into the single call model used by Swift.
> 
> Seems swift client can support upload files more than 5GB: 
> http://fedoraproject.org/wiki/QA:Testcase_Swift_Upload_Large_File
> 
> Ok, so we should just re-implement/fix the existing swift driver.
> 
>> 
>> Thanks,
>> -John
>> 
>> On Jul 9, 2013, at 4:15 PM, Edison Su  wrote:
>> 
>>> Could they(swiftstack) help us, or guide us on how to implement multi-part
>> upload?
>>> 
 -Original Message-
 From: Sebastien Goasguen [mailto:run...@gmail.com]
 Sent: Tuesday, July 09, 2013 1:07 PM
 To: dev@cloudstack.apache.org
 Cc: 'Chip Childers'
 Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 
 4.2?
 
 if swift does not work anymore in 4.0 or 4.1 maybe be should inform
 swiftstack:
 http://swiftstack.com/cloudstack/
 
 
 On Jul 9, 2013, at 3:57 PM, John Burwell  wrote:
 
> Edison,
> 
> Swift does not support S3 multi-part uploads [1] which CloudStack
> must use
 in order to store files larger than 5 GB.  Therefore, using the
 Swift's S3 compatibility layer is not a viable workaround.
> 
> Thanks,
> -John
> 
> [1]:  https://wiki.openstack.org/wiki/Swift/APIFeatureComparison
> 
> On Jul 9, 2013, at 2:12 PM, Edison Su  wrote:
> 
>> 
>> 
>>> -Original Message-
>>> From: Chip Childers [mailto:chip.child...@sungard.com]
>>> Sent: Monday, July 08, 2013 1:26 PM
>>> To: Edison Su
>>> Cc: 
>>> Subject: Re: Swift in 4.2 is broken, anybody wants it to be
>>> supported in
 4.2?
>>> 
>>> On Mon, Jul 08, 2013 at 05:15:19PM +, Edison Su wrote:
 
 
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Monday, July 08, 2013 6:46 AM
> To: ; Edison Su
> Subject: Re: Swift in 4.2 is broken, anybody wants it to be
> supported in
>>> 4.2?
> 
> On Mon, Jul 8, 2013 at 9:22 AM, David Nalley 
>> wrote:
>> On Wed, Jul 3, 2013 at 5:29 PM, Edison Su
>> 
>>> wrote:
>>> Due to object store refactor, Swift is broken. The reason, is
>>> that, we only
> have S3 test environment in our lab, so only S3 is tested for now.
>>> Before adding the feature back, I'd better ask from, the
>>> community, do
> we want to support Swift? If so, which version of Swift? This
> will take some efforts to support Swift, are there any
> volunteers can help the
>>> integration?
>> 
>> 
>> Whats the bug ID for this?
>> Unplanned/Unannounced deprecation of a feature is a blocker
>> IMO.
>> It engenders a bad relationship with our users, and strands
>> them on previous versions with no good migration/upgrade path.
>> 
>> --David
>> 
> 
> Edison, How broken is it?  Is i

SimulatorSecondaryDiscoverer bean

2013-07-09 Thread Vijayendra Bhamidipati

Hi Edison,

It looks like this bean is missing from the applicationContext.xml file with 
commit# 5e13327339305cd81993952abbd8c19409a48537, causing the mgmt. server to 
fail to startup with this error :

INFO  [hypervisor.vmware.VmwareServerDiscoverer] (main:) VmwareServerDiscoverer 
is constructed
INFO  [web.context.ContextLoader] (main:) Root WebApplicationContext: 
initialization completed in 20594 ms
INFO  [cloud.utils.LogUtils] (main:) log4j configuration found at 
/root/mywork/cloudstack/asf/latest/cloudstack/client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/log4j-cloud.xml
INFO  [factory.annotation.AutowiredAnnotationBeanPostProcessor] (main:) JSR-330 
'javax.inject.Inject' annotation found and supported for autowiring
2013-07-09 07:19:11.975:INFO::Started SelectChannelConnector@0.0.0.0:8080
[INFO] Started Jetty Server
Exception in thread "Timer-2" 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'mockAgentManagerImpl': Injection of autowired dependencies failed; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Could not autowire field: com.cloud.resource.SimulatorSecondaryDiscoverer 
com.cloud.agent.manager.MockAgentManagerImpl.discoverer; nested exception is 
org.springframework.beans.factory.NoSuchBeanDefinitionException: No matching 
bean of type [com.cloud.resource.SimulatorSecondaryDiscoverer] found for 
dependency: expected at least 1 bean which qualifies as autowire candidate for 
this dependency. Dependency annotations: {@javax.inject.Inject()}
at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:287)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1106)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.configureBean(AbstractAutowireCapableBeanFactory.java:314)
at 
com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:71)
at 
com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
at java.util.TimerThread.mainLoop(Timer.java:534)
at java.util.TimerThread.run(Timer.java:484)
Caused by: org.springframework.beans.factory.BeanCreationException: Could not 
autowire field: com.cloud.resource.SimulatorSecondaryDiscoverer 
com.cloud.agent.manager.MockAgentManagerImpl.discoverer; nested exception is 
org.springframework.beans.factory.NoSuchBeanDefinitionException: No matching 
bean of type [com.cloud.resource.SimulatorSecondaryDiscoverer] found for 
dependency: expected at least 1 bean which qualifies as autowire candidate for 
this dependency. Dependency annotations: {@javax.inject.Inject()}
at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:506)
at 
org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:87)
at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:284)
... 6 more
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No 
matching bean of type [com.cloud.resource.SimulatorSecondaryDiscoverer] found 
for dependency: expected at least 1 bean which qualifies as autowire candidate 
for this dependency. Dependency annotations: {@javax.inject.Inject()}
at 
org.springframework.beans.factory.support.DefaultListableBeanFactory.raiseNoSuchBeanDefinitionException(DefaultListableBeanFactory.java:952)
at 
org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:821)
at 
org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:735)
at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:478)
... 8 more
INFO  [factory.annotation.AutowiredAnnotationBeanPostProcessor] 
(928969643@qtp-386907765-0:) JSR-330 'javax.inject.Inject' annotation found and 
supported for autowiring



Adding the following line to the file fixed the issue:


[root@vijay-vm1 cloudstack]# git diff -w
diff --git a/client/tomcatconf/applicationContext.xml.in 
b/client/tomcatconf/applicationContext.xml.in
index 14255c1..3426d0b 100644
--- a/client/tomcatconf/applicationContext.xml.in
+++ b/client/tomcatconf/applicationContext.xml.in
@@ -859,6 +859,7 @@
   
   

+
   
   
   
@@ -869,6 +870,7 @@
   
   
   
+  
   


[root@vijay-vm1 cloudstack]#

Can you please check in the above change to the master? Thanks!


Regards,
Vijay

RE: SimulatorSecondaryDiscoverer bean

We should move all the simulator related classes into 
client/tomcatconf/simulatorComponentContext.xml.in
Let me fix it, thanks for your report.

> -Original Message-
> From: Vijayendra Bhamidipati
> Sent: Tuesday, July 09, 2013 2:02 PM
> To: dev@cloudstack.apache.org
> Cc: Edison Su
> Subject: SimulatorSecondaryDiscoverer bean
> 
> Hi Edison,
> 
> It looks like this bean is missing from the applicationContext.xml file with
> commit# 5e13327339305cd81993952abbd8c19409a48537, causing the mgmt.
> server to fail to startup with this error :
> 
> INFO  [hypervisor.vmware.VmwareServerDiscoverer] (main:)
> VmwareServerDiscoverer is constructed INFO  [web.context.ContextLoader]
> (main:) Root WebApplicationContext: initialization completed in 20594 ms
> INFO  [cloud.utils.LogUtils] (main:) log4j configuration found at
> /root/mywork/cloudstack/asf/latest/cloudstack/client/target/cloud-client-
> ui-4.2.0-SNAPSHOT/WEB-INF/classes/log4j-cloud.xml
> INFO  [factory.annotation.AutowiredAnnotationBeanPostProcessor] (main:)
> JSR-330 'javax.inject.Inject' annotation found and supported for autowiring
> 2013-07-09 07:19:11.975:INFO::Started
> SelectChannelConnector@0.0.0.0:8080
> [INFO] Started Jetty Server
> Exception in thread "Timer-2"
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'mockAgentManagerImpl': Injection of autowired
> dependencies failed; nested exception is
> org.springframework.beans.factory.BeanCreationException: Could not
> autowire field: com.cloud.resource.SimulatorSecondaryDiscoverer
> com.cloud.agent.manager.MockAgentManagerImpl.discoverer; nested
> exception is
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No
> matching bean of type [com.cloud.resource.SimulatorSecondaryDiscoverer]
> found for dependency: expected at least 1 bean which qualifies as autowire
> candidate for this dependency. Dependency annotations:
> {@javax.inject.Inject()}
> at
> org.springframework.beans.factory.annotation.AutowiredAnnotationBeanP
> ostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostPro
> cessor.java:287)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanF
> actory.populateBean(AbstractAutowireCapableBeanFactory.java:1106)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanF
> actory.configureBean(AbstractAutowireCapableBeanFactory.java:314)
> at
> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(Co
> mponentContext.java:71)
> at
> com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
> at java.util.TimerThread.mainLoop(Timer.java:534)
> at java.util.TimerThread.run(Timer.java:484)
> Caused by: org.springframework.beans.factory.BeanCreationException:
> Could not autowire field: com.cloud.resource.SimulatorSecondaryDiscoverer
> com.cloud.agent.manager.MockAgentManagerImpl.discoverer; nested
> exception is
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No
> matching bean of type [com.cloud.resource.SimulatorSecondaryDiscoverer]
> found for dependency: expected at least 1 bean which qualifies as autowire
> candidate for this dependency. Dependency annotations:
> {@javax.inject.Inject()}
> at
> org.springframework.beans.factory.annotation.AutowiredAnnotationBeanP
> ostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPost
> Processor.java:506)
> at
> org.springframework.beans.factory.annotation.InjectionMetadata.inject(Inj
> ectionMetadata.java:87)
> at
> org.springframework.beans.factory.annotation.AutowiredAnnotationBeanP
> ostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostPro
> cessor.java:284)
> ... 6 more
> Caused by:
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No
> matching bean of type [com.cloud.resource.SimulatorSecondaryDiscoverer]
> found for dependency: expected at least 1 bean which qualifies as autowire
> candidate for this dependency. Dependency annotations:
> {@javax.inject.Inject()}
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.rais
> eNoSuchBeanDefinitionException(DefaultListableBeanFactory.java:952)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.doR
> esolveDependency(DefaultListableBeanFactory.java:821)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.res
> olveDependency(DefaultListableBeanFactory.java:735)
> at
> org.springframework.beans.factory.annotation.AutowiredAnnotationBeanP
> ostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPost
> Processor.java:478)
> ... 8 more
> INFO  [factory.annotation.AutowiredAnnotationBeanPostProcessor]
> (928969643@qtp-386907765-0:) JSR-330 'javax.inject.Inject' annotation found
> and supported for autowiring
> 
> 
> 
> Adding the following line to the file fixed the issue:
> 
> 
> [root@vijay-v

RE: SimulatorSecondaryDiscoverer bean

2013-07-09 Thread Vijayendra Bhamidipati

Ah ok, thanks Edison!

Cheers!
Regards,
Vijay

-Original Message-
From: Edison Su 
Sent: Tuesday, July 09, 2013 2:10 PM
To: Vijayendra Bhamidipati; dev@cloudstack.apache.org
Subject: RE: SimulatorSecondaryDiscoverer bean

We should move all the simulator related classes into 
client/tomcatconf/simulatorComponentContext.xml.in
Let me fix it, thanks for your report.

> -Original Message-
> From: Vijayendra Bhamidipati
> Sent: Tuesday, July 09, 2013 2:02 PM
> To: dev@cloudstack.apache.org
> Cc: Edison Su
> Subject: SimulatorSecondaryDiscoverer bean
> 
> Hi Edison,
> 
> It looks like this bean is missing from the applicationContext.xml 
> file with commit# 5e13327339305cd81993952abbd8c19409a48537, causing the mgmt.
> server to fail to startup with this error :
> 
> INFO  [hypervisor.vmware.VmwareServerDiscoverer] (main:) 
> VmwareServerDiscoverer is constructed INFO  
> [web.context.ContextLoader]
> (main:) Root WebApplicationContext: initialization completed in 20594 
> ms INFO  [cloud.utils.LogUtils] (main:) log4j configuration found at
> /root/mywork/cloudstack/asf/latest/cloudstack/client/target/cloud-clie
> nt- ui-4.2.0-SNAPSHOT/WEB-INF/classes/log4j-cloud.xml
> INFO  [factory.annotation.AutowiredAnnotationBeanPostProcessor] 
> (main:)
> JSR-330 'javax.inject.Inject' annotation found and supported for 
> autowiring
> 2013-07-09 07:19:11.975:INFO::Started
> SelectChannelConnector@0.0.0.0:8080
> [INFO] Started Jetty Server
> Exception in thread "Timer-2"
> org.springframework.beans.factory.BeanCreationException: Error 
> creating bean with name 'mockAgentManagerImpl': Injection of autowired 
> dependencies failed; nested exception is
> org.springframework.beans.factory.BeanCreationException: Could not 
> autowire field: com.cloud.resource.SimulatorSecondaryDiscoverer
> com.cloud.agent.manager.MockAgentManagerImpl.discoverer; nested 
> exception is
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No 
> matching bean of type 
> [com.cloud.resource.SimulatorSecondaryDiscoverer]
> found for dependency: expected at least 1 bean which qualifies as 
> autowire candidate for this dependency. Dependency annotations:
> {@javax.inject.Inject()}
> at
> org.springframework.beans.factory.annotation.AutowiredAnnotationBeanP
> ostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostPro
> cessor.java:287)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanF
> actory.populateBean(AbstractAutowireCapableBeanFactory.java:1106)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanF
> actory.configureBean(AbstractAutowireCapableBeanFactory.java:314)
> at
> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(Co
> mponentContext.java:71)
> at
> com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
> at java.util.TimerThread.mainLoop(Timer.java:534)
> at java.util.TimerThread.run(Timer.java:484)
> Caused by: org.springframework.beans.factory.BeanCreationException:
> Could not autowire field: 
> com.cloud.resource.SimulatorSecondaryDiscoverer
> com.cloud.agent.manager.MockAgentManagerImpl.discoverer; nested 
> exception is
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No 
> matching bean of type 
> [com.cloud.resource.SimulatorSecondaryDiscoverer]
> found for dependency: expected at least 1 bean which qualifies as 
> autowire candidate for this dependency. Dependency annotations:
> {@javax.inject.Inject()}
> at
> org.springframework.beans.factory.annotation.AutowiredAnnotationBeanP
> ostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPost
> Processor.java:506)
> at
> org.springframework.beans.factory.annotation.InjectionMetadata.inject(
> Inj
> ectionMetadata.java:87)
> at
> org.springframework.beans.factory.annotation.AutowiredAnnotationBeanP
> ostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostPro
> cessor.java:284)
> ... 6 more
> Caused by:
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No 
> matching bean of type 
> [com.cloud.resource.SimulatorSecondaryDiscoverer]
> found for dependency: expected at least 1 bean which qualifies as 
> autowire candidate for this dependency. Dependency annotations:
> {@javax.inject.Inject()}
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.r
> ais
> eNoSuchBeanDefinitionException(DefaultListableBeanFactory.java:952)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.d
> oR
> esolveDependency(DefaultListableBeanFactory.java:821)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.r
> es
> olveDependency(DefaultListableBeanFactory.java:735)
> at
> org.springframework.beans.factory.annotation.AutowiredAnnotationBeanP
> ostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPost
> Processor.java:478)
>

Expanding a volume on a SAN

Hi everyone,

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

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

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

Thanks!

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

RE: Expanding a volume on a SAN

2013-07-09 Thread Anthony Xu

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

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


Anthony

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

Hi everyone,

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

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

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

Thanks!

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

Re: Review Request 12348: Fix for NPE when listing eligible primary storage pools for volume migration across primary storages

2013-07-09 Thread Venkata Siva Vijayendra Bhamidipati

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

(Updated July 9, 2013, 10:15 p.m.)

Review request for cloudstack, Chip Childers, Kelven Yang, rajeshbabu
chintaguntla, and Sateesh Chodapuneedi.

Changes
---

Observed the same issue on master branch, so uploading the diff for master.
Testing showed up other issues in volume migration, but they are unrelated to
the issue this patch addresses. The eligible storage pools are listed as
expected out of this fix, so requesting that this fix be applied on top of
master.

Bugs: CLOUDSTACK-3264

Repository: cloudstack-git

Description
---

When listing zone wide primary storages for volume migration, a null pointer
exception is encountered because the listing of the eligible storage pools
missed taking into account the absence of cluster id for zone wide primary
pools. Fixing the same and putting in appropriate checks for other storage type
allocators.

Note: This fix is for the master-6-17-stable branch. It is to be seen whether
this fix is required for master and if so, needs to be ported/tested on the
same.

Diffs (updated)
-

engine/storage/src/org/apache/cloudstack/storage/allocator/AbstractStoragePoolAllocator.java
e16703e

engine/storage/src/org/apache/cloudstack/storage/allocator/ClusterScopeStoragePoolAllocator.java
0933adc

engine/storage/src/org/apache/cloudstack/storage/allocator/LocalStoragePoolAllocator.java
ef9e84e

plugins/storage-allocators/random/src/org/apache/cloudstack/storage/allocator/RandomStoragePoolAllocator.java
76ce663
server/src/com/cloud/server/ManagementServerImpl.java da9d6a2

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

Testing
---

Created multiple zone wide primary storages and confirmed that they show up as
eligible destinations when attempting to migrate a volume currently resident on
a zone wide primary storage pool. Created mixed zone-wide and cluster-wide
primary storages to ensure nothing broke there. Observed that volumes on a zone
wide primary can only be moved to other zone wide primary pools and similarly
with cluster wide pools. Created new guest VM to confirm that existing primary
code paths work correctly with the changes in place.

Thanks,

Venkata Siva Vijayendra Bhamidipati

RE: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?

2013-07-09 Thread Animesh Chaturvedi



> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Tuesday, July 09, 2013 11:57 AM
> To: Edison Su
> Cc: 
> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in
> 4.2?
> 
> On Tue, Jul 09, 2013 at 06:55:03PM +, Edison Su wrote:
> >
> >
> > > -Original Message-
> > > From: Chip Childers [mailto:chip.child...@sungard.com]
> > > Sent: Tuesday, July 09, 2013 11:22 AM
> > > To: Edison Su
> > > Cc: 
> > > Subject: Re: Swift in 4.2 is broken, anybody wants it to be
> supported in 4.2?
> > >
> > > On Tue, Jul 09, 2013 at 06:12:22PM +, Edison Su wrote:
> > > > If it's ok to use S3 api talking to swift, then there is zero
> > > > effort to support
> > > Swift.
> > > > But who will make the decision?
> > >
> > > We, as a community.  It's *always* that answer.
> > >
> > > If you are proposing this as the corrective path, then ok...  let's
> > > see if others have opinions about this though.
> > >
> > > Heres how I see it:
> > >
> > > Pros -
> > >  * Code within the master branch has functional S3 API support
> > >  * We seem to have more contribution around this interface spec
> > >  * Having S3 as the only non-NFS secondary storage API reduces the
> > >long-term support / test efforts
> > >
> > > Cons -
> > >  * We may have an expectation issue for existing users that only
> have the
> > >native Swift API enabled in their environment (although I'm not
> aware
> > >of the Swift API's stability between their releases)
> >
> > I think you get into the same situation as I did, without input from
> users who is using Swift, or the company who is supporting Swift, what
> we are talking about here is just hypothetic.
> > If we really want to support Swift, and support it better, we need to
> get domain expert involved in the discuss.
> 
> Does your $dayjob happen to have a customer that might be using this
> integration?  If so, could your $dayjob product manager chime in on the
> discussion?
> 
[Animesh>] I followed up with $dayjob product manager, there was a customer who 
was interested in this integration a while back but did not end up using it.
> >
> > >  * We haven't tested Swift as an S3 API provider yet (but could).
> > >
> > > Personally, if it gets tested and proven to work as well or better
> > > than other
> > > S3 providers, I'm +1 on this being the remediation approach.
> > >
> > > Others?
> >

RE: How to evaluate performance of a resource allocation policy?

2013-07-09 Thread Alex Huang

> 
> Consider using the simulator plugin, which will simulate hosts.  You can 
> follow
> the testing instructions on the Marvin testing page [1], but modify your setup
> to implement whatever number of hosts you want to test against.  From
> there, you would need to modify the allocator that's enabled.
> 
+1  That's exactly how it should be done.  It's how stress tests are performed.

You can modify the simulator plugin to vary its response to play devil's 
advocate to test out different theories.

Also, the simulator today does not have this but you should be able to make it 
implement the PluggableService interface to expose commands to allow your test 
client to adjust responses on the fly.

--Alex

Re: Expanding a volume on a SAN

Thanks!

Anyone know if CloudStack will recognize the new size of a storage
repository or datastore on its own?


On Tue, Jul 9, 2013 at 4:01 PM, Anthony Xu  wrote:

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

Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?

I've also sent a request off to Mirantis to see if they could lend any
expertise to the fire to help.

Cheers,
Matt 


On 7/9/13 3:19 PM, "Joe Brockmeier"  wrote:

>On Tue, Jul 9, 2013, at 03:15 PM, Edison Su wrote:
>> Could they(swiftstack) help us, or guide us on how to implement
>> multi-part upload?
>
>I've sent an email to John at SwiftStack to see if they might be able to
>jump into the conversation.
>
>Best,
>
>jzb
>-- 
>Joe Brockmeier
>j...@zonker.net
>Twitter: @jzb
>http://www.dissociatedpress.net/

CloudStack Mirrors

Greetings,Is there any plan to make use of mirrors for folks downloading / updating from the repo. Or is there one in existence now?- Maurice

Re: Expanding a volume on a SAN

Hey Anthony,

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

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

Thanks!


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

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



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

Re: CloudStack Mirrors

2013-07-09 Thread Matthew E. Porter

If there is a need, we (Contegix) are happy to host one.


Cheers,
  Matthew 


---
Matthew E. Porter
Contegix
E-mail: matthew.por...@contegix.com
Twitter: @meporter | http://twitter.com/meporter

On Jul 9, 2013, at 7:24 PM, Maurice Lawler  wrote:

> Greetings,
> 
> Is there any plan to make use of mirrors for folks downloading / updating 
> from the repo. Or is there one in existence now?
> 
> 
> - Maurice

Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?

I've been watching from the outside and tracking the entire discussion,
and with what has happened with the delays with 4.0 and 4.1 am worried
that this could be come the next delayer to the release of 4.2. At the
same time, I'm very much in agreement with David N., Chip and John B. that
we can't just drop a feature because it hasn't been attiquately tested in
that past releases.

My observations - 
1. There is not a quick fix here.
2. We don't know who can do it.
3. We're not sure how to do it properly
4. Currently we can't even agree on whether we go with the original
version or the newer one.
5. We can't validate user base immediate need and requirement for the
feature. 
6. We're stuck in Analysis paralysis!

Conclusion - If we don't get past these in short order we are going to
jeopardize 4.2 timely release.

Suggestion:
Based off my work with other (corporate) software releases, if we can't
validate the immediate need, we don't know the immediate fix, and we don't
have the right people to do it should we slate this for 4.2.1 and lower
this to a Major for 4.2? We don't delay a major release, and at the same
time we dedicate ourselves to not stranding a user. We need to do this,
but at this point we need to do it right for that user base too.

We work to fix the previous version and we work to support new versions.
We get the right resources in to assist, and we make it an immediate
priority to address. If we can fix and test properly before the cut of
4.2, WONDERFUL! If not, then it doesn't block the release, but it goes out
with 4.2.1 asap. 

So there's my ramblings. How far off base am I? :-)

Ready, setŠ fire!
Matt 

On 7/9/13 5:23 PM, "Animesh Chaturvedi" 
wrote:

>
>
>> -Original Message-
>> From: Chip Childers [mailto:chip.child...@sungard.com]
>> Sent: Tuesday, July 09, 2013 11:57 AM
>> To: Edison Su
>> Cc: 
>> Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in
>> 4.2?
>> 
>> On Tue, Jul 09, 2013 at 06:55:03PM +, Edison Su wrote:
>> >
>> >
>> > > -Original Message-
>> > > From: Chip Childers [mailto:chip.child...@sungard.com]
>> > > Sent: Tuesday, July 09, 2013 11:22 AM
>> > > To: Edison Su
>> > > Cc: 
>> > > Subject: Re: Swift in 4.2 is broken, anybody wants it to be
>> supported in 4.2?
>> > >
>> > > On Tue, Jul 09, 2013 at 06:12:22PM +, Edison Su wrote:
>> > > > If it's ok to use S3 api talking to swift, then there is zero
>> > > > effort to support
>> > > Swift.
>> > > > But who will make the decision?
>> > >
>> > > We, as a community.  It's *always* that answer.
>> > >
>> > > If you are proposing this as the corrective path, then ok...  let's
>> > > see if others have opinions about this though.
>> > >
>> > > Heres how I see it:
>> > >
>> > > Pros -
>> > >  * Code within the master branch has functional S3 API support
>> > >  * We seem to have more contribution around this interface spec
>> > >  * Having S3 as the only non-NFS secondary storage API reduces the
>> > >long-term support / test efforts
>> > >
>> > > Cons -
>> > >  * We may have an expectation issue for existing users that only
>> have the
>> > >native Swift API enabled in their environment (although I'm not
>> aware
>> > >of the Swift API's stability between their releases)
>> >
>> > I think you get into the same situation as I did, without input from
>> users who is using Swift, or the company who is supporting Swift, what
>> we are talking about here is just hypothetic.
>> > If we really want to support Swift, and support it better, we need to
>> get domain expert involved in the discuss.
>> 
>> Does your $dayjob happen to have a customer that might be using this
>> integration?  If so, could your $dayjob product manager chime in on the
>> discussion?
>> 
>[Animesh>] I followed up with $dayjob product manager, there was a
>customer who was interested in this integration a while back but did not
>end up using it.
>> >
>> > >  * We haven't tested Swift as an S3 API provider yet (but could).
>> > >
>> > > Personally, if it gets tested and proven to work as well or better
>> > > than other
>> > > S3 providers, I'm +1 on this being the remediation approach.
>> > >
>> > > Others?
>> >

System VM

Hello,I'm curious, is this the most recent up to date system VM for download for KVM?http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2

Re: CloudStack Mirrors

2013-07-09 Thread Kelly Hair

That would seem to make sense. Great for redundancy, and if the mirrors are
on multiple continents then it should help with any bandwidth starved
downloaders.
On Jul 9, 2013 8:24 PM, "Maurice Lawler"  wrote:

> Greetings,
>
> Is there any plan to make use of mirrors for folks downloading / updating
> from the repo. Or is there one in existence now?
>
>
> - Maurice
>

Re: CloudStack Mirrors

Agreed, today alone; I am doing another fresh install for some of the RPMs it took 14 minutes. Where others took what appeared seconds. On Jul 09, 2013, at 09:32 PM, Kelly Hair  wrote:That would seem to make sense. Great for redundancy, and if the mirrors are on multiple continents then it should help with any bandwidth starved downloaders. On Jul 9, 2013 8:24 PM, "Maurice Lawler"  wrote: Greetings,Is there any plan to make use of mirrors for folks downloading / updatingfrom the repo. Or is there one in existence now?- Maurice

Re: CloudStack News - Moving to Wednesday

2013-07-09 Thread Ryan Lei

Hi, all. According to the Apache infra status
http://monitoring.apache.org/status/ , the ASF Blog system has been in the
status of CRITICAL or WARNING for many days, and I'm still not able to
browse the newsletter website. It's close to Wednesday now. Does anyone
know what's going on there?

---
Yu-Heng (Ryan) Lei, Associate Reasearcher
Chunghwa Telecom Laboratories / Cloud Computing Laboratory
ryan...@cht.com.tw
or
ryanlei750...@gmail.com



On Tue, Jul 9, 2013 at 2:49 AM, Mathias Mullins
wrote:

> - Multi-list send since this is a community wide announcement
>
> Just a reminder, the community news blog is moving to being published on
> Wednesdays starting this week on July 10! This is to make it more timely
> with the data that we are working on throughout the week.
>
> Please make sure to have any information, events (including dates), or
> topics that you would like to see covered or focused on posted to the
> marketing@c.a.o mailing list by Monday EOD so we have time to get it in.
> We'll try to get stuff happening in on Tuesday as well. If you would like
> to add it directly to the news feed wiki, please add it at:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Weekly+News
> <
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Weekly+News#
> >#<
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Weekly+News#
> >
>
> Thanks,
> Matt Mullins
>

Re: CloudStack News - Moving to Wednesday

2013-07-09 Thread David Nalley

Yes, there are some problems with roller instance (the underlying
software that blogs.a.o runs). Infrastructure has been discussing the
situation.
There is no immediate timeline on having the issue resolved to my knowledge.

--David

On Tue, Jul 9, 2013 at 10:03 PM, Ryan Lei  wrote:
> Hi, all. According to the Apache infra status
> http://monitoring.apache.org/status/ , the ASF Blog system has been in the
> status of CRITICAL or WARNING for many days, and I'm still not able to
> browse the newsletter website. It's close to Wednesday now. Does anyone
> know what's going on there?
>
> ---
> Yu-Heng (Ryan) Lei, Associate Reasearcher
> Chunghwa Telecom Laboratories / Cloud Computing Laboratory
> ryan...@cht.com.tw
> or
> ryanlei750...@gmail.com
>
>
>
> On Tue, Jul 9, 2013 at 2:49 AM, Mathias Mullins
> wrote:
>
>> - Multi-list send since this is a community wide announcement
>>
>> Just a reminder, the community news blog is moving to being published on
>> Wednesdays starting this week on July 10! This is to make it more timely
>> with the data that we are working on throughout the week.
>>
>> Please make sure to have any information, events (including dates), or
>> topics that you would like to see covered or focused on posted to the
>> marketing@c.a.o mailing list by Monday EOD so we have time to get it in.
>> We'll try to get stuff happening in on Tuesday as well. If you would like
>> to add it directly to the news feed wiki, please add it at:
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Weekly+News
>> <
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Weekly+News#
>> >#<
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Weekly+News#
>> >
>>
>> Thanks,
>> Matt Mullins
>>

Re: AWS SDK version for object store

2013-07-09 Thread Thomas O'Dowd

I'm +1 also to taking the latest stable release.

Tom.

On Mon, 2013-07-08 at 13:28 -0400, John Burwell wrote:
> Edison,
> 
> I vote to take the latest stable from Amazon.  In addition to keeping up with 
> security and bug fixes, it also ensures that we stay in sync with any 
> "refinements" that Amazon introduces as part of their continuous 
> improvement/deployment model.
> 
> Thanks,
> -John
> 
> On Jul 8, 2013, at 1:26 PM, Edison Su  wrote:
> 
> > From CloudStack point of view, there should be minor changes in order to 
> > adapt to latest AWS SDK. What's your guys option, John, Thomas? Is it ok to 
> > upgrade to latest SDK?
> > 
> >> -Original Message-
> >> From: Prasanna Santhanam [mailto:t...@apache.org]
> >> Sent: Friday, July 05, 2013 5:58 AM
> >> To: dev@cloudstack.apache.org
> >> Subject: AWS SDK version for object store
> >> 
> >> There was another issue I found today with the SDK v1.3.21. It appears I 
> >> can't
> >> use periods in the name of a bucket. I see an SSL Exception when this is 
> >> done
> >> [1]. The bug is fixed in the v1.3.22. There are also couple of other 
> >> issues fixed
> >> related to s3 on the latest version of the SDK.  Is there any reason not 
> >> to use
> >> the latest stable SDK version in CloudStack? IOW, why did we choose the
> >> v1.3.21?
> >> 
> >> [1] http://issues.apache.org/jira/browse/CLOUDSTACK-3374
> >> 
> >> --
> >> Prasanna.,
> >> 
> >> 
> >> Powered by BigRock.com
> > 
> 

-- 
Cloudian KK - http://www.cloudian.com/get-started.html
Fancy 100TB of full featured S3 Storage?
Checkout the Cloudian® Community Edition!

Re: CloudStack News - Moving to Wednesday

We'll try to get it up as soon as the issues clear up.

Matt 



On 7/9/13 9:06 PM, "David Nalley"  wrote:

>Yes, there are some problems with roller instance (the underlying
>software that blogs.a.o runs). Infrastructure has been discussing the
>situation.
>There is no immediate timeline on having the issue resolved to my
>knowledge.
>
>--David
>
>On Tue, Jul 9, 2013 at 10:03 PM, Ryan Lei  wrote:
>> Hi, all. According to the Apache infra status
>> http://monitoring.apache.org/status/ , the ASF Blog system has been in
>>the
>> status of CRITICAL or WARNING for many days, and I'm still not able to
>> browse the newsletter website. It's close to Wednesday now. Does anyone
>> know what's going on there?
>>
>> 
>>-
>>--
>> Yu-Heng (Ryan) Lei, Associate Reasearcher
>> Chunghwa Telecom Laboratories / Cloud Computing Laboratory
>> 
>>ryan...@cht.com.tw>YpVkiWo8SsDdf3ZqO9AIuAPTzRnFYCUi-z4YljtI_hyVKkNHfn9F1Bn-vUWJnQ4.&URL=mail
>>to%3aryanlei%40cht.com.tw>
>> or
>> ryanlei750...@gmail.com
>>
>>
>>
>> On Tue, Jul 9, 2013 at 2:49 AM, Mathias Mullins
>> wrote:
>>
>>> - Multi-list send since this is a community wide announcement
>>>
>>> Just a reminder, the community news blog is moving to being published
>>>on
>>> Wednesdays starting this week on July 10! This is to make it more
>>>timely
>>> with the data that we are working on throughout the week.
>>>
>>> Please make sure to have any information, events (including dates), or
>>> topics that you would like to see covered or focused on posted to the
>>> marketing@c.a.o mailing list by Monday EOD so we have time to get it
>>>in.
>>> We'll try to get stuff happening in on Tuesday as well. If you would
>>>like
>>> to add it directly to the news feed wiki, please add it at:
>>> 
>>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Weekly
>>>+News
>>> <
>>> 
>>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Weekly
>>>+News#
>>> >#<
>>> 
>>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Weekly
>>>+News#
>>> >
>>>
>>> Thanks,
>>> Matt Mullins
>>>

Review Request 12398: Add cookie field to UCS API

2013-07-09 Thread Amogh Vasekar


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

Review request for cloudstack and Animesh Chaturvedi.


Bugs: 3432


Repository: cloudstack-git


Description
---

Adds cookie to associatesUcsProfiletoBlade API


Diffs
-

  plugins/hypervisors/ucs/src/com/cloud/ucs/manager/UcsCommands.java 9bb77a2 

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


Testing
---

Currently gives Blade ID not found error. Possibly unrelated


Thanks,

Amogh Vasekar

[ACS42] Three weeks to code freeze

2013-07-09 Thread Animesh Chaturvedi

Folks


We are now just 3 weeks from ACS 4.2 code freeze on 7/29. We have around 400 
open defects with 100+ blockers and critical and I expect another 200 new 
defects to come in. As a community we have been fixing roughly 100 defects per 
week, in order to clear up our backlog I request you to help out on 
aggressively fixing the issues. The unassigned issue list is available at 
http://s.apache.org/BlH/. When you fix a bug in 4.2 please make sure it is also 
fixed in master. 

Given the debate on system template changes in last few days of 4.1 requiring 
big testing effort and potential regression, I would like to see that as 
community we lock down system templates for 4.2 pretty soon. If any changes are 
needed we should call it out now and get them resolved.


The detailed bug status is captured below. 

  Bugs| This Week| Last Week

 
-+---+--+---+---+---+--+---+---
  |   Blocker   Critical   Major   Total |   Blocker   Critical 
  Major   Total  
 
-+---+--+---+---+---+--+---+---
  Incoming| 8 10  28  50 |11 34 
 24  72
  Outgoing|26 23  34  86 |26 30 
 40 100
  Open Unassigned | 7 49 129 222 | 6 49 
119 184   
  Open Total  |25 84 232 403 |25 80 
218 385


The status for features or improvement is depicted in table below

|-+---+---|
| New Features / Improvements | Today | Last Week |
|-+---+---|
| Closed  |10 |10 |
| Resolved|59 |57 |
| In Progress |11 |13 |
| Reopened| 1 | 1 |
| Ready To Review | 1 | 1 |
| Open|20 |20 |
|-+---+---|
| Total   |   102 |   102 |
|-+---+---|

Only few feature tickets were updates since I sent out the Open and In progress 
item list. If your contribution did not make it to 4.2 please take it out from 
4.2

There is some improvement in verifying and closing the resolved issues compared 
from last week but is still hovering close to 500. Please check Sudha's email 
from yesterday http://s.apache.org/mzj and help close out resolved issues.



 
Thanks
Animesh

Review Request 12360: custom cpu model for kvm guest.the default model 'QEMU Virtual CPU version xxx' affect the activation of Windows OS and low performance.

2013-07-09 Thread Jijun Liu

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

Review request for cloudstack, edison su, soren, and Wei Zhou.

Summary (updated)
-

custom cpu model for kvm guest.the default model 'QEMU Virtual CPU version xxx'
affect the activation of Windows OS and low performance.

Repository: cloudstack-git

Description (updated)
---

Add cpu model for kvm guest.Now all the kvm guest's cpu model is 'QEMU Virtual
CPU version xxx'. This will affect the activation of Windows OS and low
performance. I add three mode for user to indicate the guest cpu model. some
ideas come from openstack and libvirt.
user can uncomment guest.cpu.mode and guest.cpu.model in agent.properties to
enable this feature.it is disabled by default.
some details as follows:
custom - user custom the CPU model which specified by guest.cpu.model.
host-model - identify the named CPU model which most closely matches the host,
and then request additional CPU flags to complete the match. This should give
close to maximum functionality/performance, which maintaining good
reliability/compatibility if the guest is migrated to another host with
slightly different host CPUs.
host-passthrough - tell KVM to passthrough the host CPU with no modifications.
The difference to host-model, instead of just matching feature flags, every
last detail of the host CPU is matched. This gives absolutely best
performance,and can be important to some apps which check low level CPU
details, but it comes at a cost wrt migration. The guest can only be migrated
to an exactly matching host CPU.

Diffs (updated)
-

agent/conf/agent.properties 60030ae

plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java
914017c

plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtVMDef.java
5120870

plugins/hypervisors/kvm/test/com/cloud/hypervisor/kvm/resource/LibvirtVMDefTest.java
2c0ff8d

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

Testing (updated)
---

1.set guest.cpu.mode=custom,guest.cpu.model=Nehalem in agent.properties,you can
get more guest.cpu.model by execute virsh capabilities .create a new vm
instance or reboot your vm instance,the guest's cpu model will change as
guest.cpu.model specified.
2.set guest.cpu.mode=host-model,create a new vm instance or reboot your vm
instance the guest's cpu model will be a closely cpu model as your hypervisor.
3.set guest.cpu.mode=host-passthrough,create a new vm instance or reboot your
vm instance,the guest's cpu model should be the cpu model as your hypervisor.

Thanks,

Jijun Liu

RE: [DISCUSS] If BVT breaks, revert the commits...

2013-07-09 Thread Alex Huang

Sorry this took a little longer than expected with the holiday in US.  Here's 
the first proposal [1] on the automated test system.  Comments welcome.  

Specifically, I have one question on if we should have a staging branch for all 
release branches and master where all checkins go and the build system 
automatically cherry-pick over commits that passes the tests.

I believe we have a lot of pieces in place.  Prassana, Sudha, Rayees, Ram 
Ganesh, myself, and a few others will be working to get this system in place.  

--Alex
[1] 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Automated+Tests+Rules+and+Guidelines

> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: Friday, June 28, 2013 8:44 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] If BVT breaks, revert the commits...
> 
> On Fri, Jun 28, 2013 at 8:18 PM, Alex Huang  wrote:
> > After Dave's complain in the vmsync [MERGE] thread about BVT in horrible
> shape on master, I went around to figure out what exactly happened.  The
> best I can figure is that after a certain merge (I will leave out which merge 
> as
> that's not important), BVT no longer runs automatically.  It was promised to
> be fixed and there are people who are actively fixing it but it's been in this
> way for about two weeks.  People running BVTs are working around the
> problem but it's not automated anymore and so it's no longer running on
> master.  I understand people are nice and tried to be accommodating to
> other people by working around the problem but sometimes we just have to
> be an arse.  So let me be that arse...
> >
> > New Rule
> > If BVT or automated regression tests break on master or any release
> branch, we revert all commits that broke it.  It doesn't matter if they 
> promise
> to fix it within the next hour.  If it's broken, the release manager will 
> revert
> the commits and developers must resubmit.  It sounds mean but it's the only
> way this problem can be fixed.
> >
> > To avoid having a bunch of reverts and resubmits, the developers should
> be able to request that BVT run on their branch and don't merge until BVT on
> their branch is at 100%.  We will work on figuring out how to do that.
> >
> > Comments?
> >
> > --Alex
> 
> +100 - not only +100 but I will increment ASFBots $beverage counter a
> few in your favor for suggesting this.
> 
> --David

Error Message: Cloud Stack