Re: Create rbd primary storage fail in CS 4.0.1

2013-04-19 Thread Guangjian Liu
Ceph file system can added as Primary storage by RBD, Thanks.

Now I meet the problem in creating VM to Ceph.

First I create computer offer and storage offer with tag "ceph", and define
Ceph Primary storage with tag "ceph".
Then I create VM use "ceph" computer offer, It display exception in Log. It
seems the storage size out off usage.

Create VM fail
2013-04-18 10:23:27,559 DEBUG
[storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-1:job-24) Is
storage pool shared? true
2013-04-18 10:23:27,561 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-1:job-24) Checking pool 209 for storage, totalSize:
146673582080, *usedBytes: 33780317214998658*, usedPct: 230309.48542985672,
disable threshold: 0.85
2013-04-18 10:23:27,561 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-1:job-24) Insufficient space on pool: 209 since its usage
percentage: 230309.48542985672 has crossed the
pool.storage.capacity.disablethreshold: 0.85
2013-04-18 10:23:27,561 DEBUG
[storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-1:job-24)
FirstFitStoragePoolAllocator returning 0 suitable storage pools
2013-04-18 10:23:27,561 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-1:job-24) No suitable pools found for volume:
Vol[8|vm=8|ROOT] under cluster: 1
2013-04-18 10:23:27,562 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-1:job-24) No suitable pools found
2013-04-18 10:23:27,562 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-1:job-24) No suitable storagePools found under this Cluster: 1
2013-04-18 10:23:27,562 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-1:job-24) Could not find suitable Deployment Destination for
this VM under any clusters, returning.
2013-04-18 10:23:27,640 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-1:job-24) VM state transitted from :Starting to Stopped with
event: OperationFailedvm's original host id: null new host id: null host id
before state transition: null
2013-04-18 10:23:27,645 DEBUG [cloud.vm.UserVmManagerImpl]
(Job-Executor-1:job-24) Destroying vm VM[User|ceph-1] as it failed to create
management-server.7z 2013-04-18 10:02

I check CS Web GUI and Database, the storage Allocated 30723TB, but
actually the total size is 138GB.
[image: Inline image 1]


mysql> select * from storage_pool;
+-+-+--+---+--++++---++--+---+-+-+-+-++
| id  | name| uuid | pool_type
| port | data_center_id | pod_id | cluster_id | available_bytes   |
capacity_bytes | host_address | user_info | path| created
  | removed | update_time | status |
+-+-+--+---+--++++---++--+---+-+-+-+-++
| 200 | primary | d9474b9d-afa1-3737-a13b-df333dae295f | NetworkFilesystem
| 2049 |  1 |  1 |  1 |   10301210624 |
 61927849984 | 10.0.0.42| NULL  | /export/primary | 2013-04-17
06:25:47 | NULL| NULL| Up |
| 209 | ceph| 18559bbf-cd1a-3fcc-a4d2-e95cd4f2d78c | RBD
| 6789 |  1 |  1 |  1 | 33780317214998658 |
146673582080
| 10.0.0.41| : | rbd | 2013-04-18 02:02:00 | NULL
 | NULL| Up |
+-+-+--+---+--++++---++--+---+-+-+-+-++
2 rows in set (0.00 sec)





On Thu, Apr 18, 2013 at 3:54 AM, Wido den Hollander  wrote:

> Hi,
>
>
> On 04/17/2013 03:01 PM, Guangjian Liu wrote:
>
>> I still meet the same result.
>>
>> In ubuntu 12.04,
>> 1. I install libvirt-dev as below,
>> apt-get install libvirt-dev
>> 2. rebuild libvirt, see detail build log in attach.
>> root@ubuntu:~/install/libvirt-**0.10.2# ./autogen.sh
>> running CONFIG_SHELL=/bin/bash /bin/bash ./configure --enable-rbd
>> --no-create --no-recursion
>> configure: WARNING: unrecognized options: --enable-rbd
>>
>
> The correct option is "--with-storage-rbd"
>
> But check the output of configure, it should tell you whether RBD was
> enabled or not.
>
> Then verify again if you can create a RBD storage pool manually via
> libvirt.
>
> Wido
>
>  .
>> make
>> make install
>>
>>
>>
>> On Wed, Apr 17, 2013 at 6:25 PM, Wido den Hollander > > wrote:
>>
>> Hi,
>>
>>
>> On 04/17/2013 11:37 AM, Guangjian Liu wrote:
>>
>> Thanks for your mail, you suggest compile libvirt with RBD enable.
>> I already build libvirt-0.10.2.tar.gz as document
>> 
>> http://ceph.com/docs/master/__**rbd/libvirt/

Re: DnsNotifier Example

2013-04-19 Thread Murali Reddy

Since its a example class, its not added in the client war file that jetty
runs. Please add a dependency in client/pom.xml as below

 
   org.apache.cloudstack
   cloud-plugin-example-dns-notifier
   ${project.version}
 



On 19/04/13 5:58 AM, "Soheil Eizadi"  wrote:

>I am trying to run the DnsNotifier example in my CloudStack Environment,
>I am having trouble with the Spring wiring. I modified the
>DnsNotifier.java file to add @Component annotation and modified the two
>files componentContext.xml.in and nonossComponentContext.xml.in to add
>reference to the DnsNotifier. I get everything to build but the Spring
>Class Loader can not find DnsNotifier Class to load, what more needs to
>be done to get this to run?
>-Soheil
>
>ovider,databaseUpgradeChecker,configurationDaoImpl,GlobalLoadBalancingRule
>sServiceImpl,DnsNotifier,niciraNvpDaoImpl,niciraNvpNicMappingDaoImpl,nicir
>aNvpRouterMappingDaoImpl,NiciraNvpGuestNetworkGuru,NiciraNvp,MidoNetGuestN
>etworkGuru,MidoNetElement,userAuthenticators,userPasswordEncoders,security
>Checkers,resourceDiscoverers,haInvestigators,haFenceBuilders,deploymentPla
>nners,podAllocators,hostAllocators,storagePoolAllocators,ipDeployers,dhcpP
>roviders,networkGurus,networkElements,org.springframework.context.annotati
>on.ConfigurationClassPostProcessor$ImportAwareBeanPostProcessor#0]; root
>of factory hierarchy
>ERROR [web.context.ContextLoader] (main:) Context initialization failed
>org.springframework.beans.factory.BeanCreationException: Error creating
>bean with name 'actionEventUtils': Injection of autowired dependencies
>failed; nested exception is
>org.springframework.beans.factory.BeanCreationException: Could not
>autowire field: com.cloud.event.dao.EventDao
>com.cloud.event.ActionEventUtils.eventDao; nested exception is
>org.springframework.beans.factory.CannotLoadBeanClassException: Cannot
>find class [org.apache.cloudstack.network.element.DnsNotifier] for bean
>with name 'DnsNotifier' defined in class path resource
>[componentContext.xml]; nested exception is
>java.lang.ClassNotFoundException:
>org.apache.cloudstack.network.element.DnsNotifier
>
>Administrators-MacBook-Pro-7:cloudstack seizadi$ find . -name
>DnsNotifier.class
>./plugins/network-elements/dns-notifier/target/classes/org/apache/cloudsta
>ck/network/element/DnsNotifier.class
>
>diff --git 
>a/plugins/network-elements/dns-notifier/src/org/apache/cloudstack/network/
>element/DnsNotifier.java
>b/plugins/network-elements/dns-notifier/src/org/apache/cloudstack/network/
>element/DnsNotifier.java
>index c421344..8f8986d 100644
>--- 
>a/plugins/network-elements/dns-notifier/src/org/apache/cloudstack/network/
>element/DnsNotifier.java
>+++ 
>b/plugins/network-elements/dns-notifier/src/org/apache/cloudstack/network/
>element/DnsNotifier.java
>@@ -22,7 +22,9 @@ import java.util.Map;
> import java.util.Set;
>
> import javax.ejb.Local;
>-import javax.naming.ConfigurationException;
>+
>+import org.apache.log4j.Logger;
>+import org.springframework.stereotype.Component;
>
> import com.cloud.deploy.DeployDestination;
> import com.cloud.exception.ConcurrentOperationException;
>@@ -45,13 +47,17 @@ import com.cloud.vm.VirtualMachineProfile;
>  * @author ahuang
>  *
>  */
>+
>+@Component
> @Local(NetworkElement.class)
> public class DnsNotifier extends AdapterBase implements NetworkElement {
>
>
>diff --git a/client/tomcatconf/componentContext.xml.in
>b/client/tomcatconf/componentContext.xml.in
>index bea2f78..202a998 100644
>--- a/client/tomcatconf/componentContext.xml.in
>+++ b/client/tomcatconf/componentContext.xml.in
>@@ -46,6 +46,14 @@
>   class="com.cloud.configuration.dao.ConfigurationDaoImpl" />
>
>   ="org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl"
>/>
>+
>+  class="org.apache.cloudstack.network.element.DnsNotifier">
>+
>+  
>+
>
>  
>   
>
>diff --git a/client/tomcatconf/nonossComponentContext.xml.in
>b/client/tomcatconf/nonossComponentContext.xml.in
>index fc8a9cd..9da3d06 100644
>--- a/client/tomcatconf/nonossComponentContext.xml.in
>+++ b/client/tomcatconf/nonossComponentContext.xml.in
>@@ -79,6 +79,13 @@
>   class="com.cloud.hypervisor.vmware.resource.VmwareContextFactory" />
>
>+  class="org.apache.cloudstack.network.element.DnsNotifier">
>+
>+  
>+
>+  
>   class="com.cloud.network.dao.NiciraNvpDaoImpl" />
>@@ -331,6 +338,8 @@
>   
>   
>   
>+  
> 

Re: ebtables

2013-04-19 Thread Maurice Lawler
Perhaps this was not the best thing, now my ports are open; how can I revert 
back to eatables. 

Along with that, when reverted, how can I drop rules for a particular VM to 
allow communication via second IP address. 


On Apr 18, 2013, at 10:34 PM, Maurice Lawler  wrote:

> Disregard, for now, I have disabled/removed ebtables as shown here:
> 
> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-users/201302.mbox/%3cb1df26ecc0458748ac97cece2da98d41012fa47b6...@sjcpmailbox01.citrite.net%3E
> 
> 
> On Apr 18, 2013, at 11:28 PM, Maurice Lawler  wrote:
> 
>> Hello --
>> 
>> Previously one told me how to do this, but I cannot find my notes on this, 
>> so I hope you can help me out.
>> 
>> I am attempting to allow a secondary IP address on an instance by-pass the 
>> routing rules set forth in ebtables. I recall doing something like 
>> 
>> ebtables nat i-2-25-VM something ... I cannot for the life of me remember.
>> 
>> How to list and/or drop the rules per VM.
>> 
>> Can you guys assist?



RE: qa tests for nicira code in 4.1

2013-04-19 Thread Daan Hoogland
H Rayess,

The tests are mostly manual as of yet. I am working with Hugo now to 
investigate the problem and will report back here

Daan Hoogland

-Original Message-
From: Rayees Namathponnan [mailto:rayees.namathpon...@citrix.com] 
Sent: vrijdag 19 april 2013 0:07
To: dev@cloudstack.apache.org
Subject: RE: qa tests for nicira code in 4.1

Hi Daan,

These test cases are in ASF repo ?

Regards,
Rayees 

-Original Message-
From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com] 
Sent: Thursday, April 18, 2013 12:38 PM
To: dev@cloudstack.apache.org
Subject: qa tests for nicira code in 4.1

LS,

At Schuberg Philis we did some tests on the 4.1 code for the tests in the 
following table
Test Case ID  Test Description Results
   Infrastructure
NVP-001 Create NVP Element pass
NVP-002 Disable NVP Elementpass
NVP-003 Enable NVP Element pass
NVP-004 Delete NVP Element  pass
NVP-005 Create NVP Device   pass
NVP-006 Delete NVP Devicepass
   L2 Functions
NVP-101 Create Logical Switchpass
NVP-102 Create Logical Portpass
NVP-103 Check Connection Pass
NVP-104 Check Connection Pass
NVP-105 Delete Logical SwitchPass
NVP-106 Delete Logical Port Pass
   L3 Functions
NVP-201 Create Logical RouterPass
NVP-202 Create Source Nat rule  Pass
NVP-203 Create Static Nat rulePass
NVP-204 Create Port FW rule   Pass
NVP-205 Check Source Nat rule  Pass
NVP-206 Check Static Nat rule Pass
NVP-207 Check Port FW rule   Pass
NVP-208 Delete Source Nat rule  Pass
NVP-209 Delete Static Nat rule Fail
NVP-210 Delete Port FW rule   Pass
NVP-211 Delete Logical RouterPass

The tests where partly done aith scripts but these are not yet complete and the 
remainder of functionality was done by hand.
For the failed test, NVP-209 a ticket was created, 'CLOUDSTACK-2092'. The 
problem in this case was that deleting the static rule did not result in the 
deletion of the ip adres from the logical router.

Kind regards,
Daan Hoogland


Re: Review Request: CLOUDSTACK-1786: While reserving IPs in guest network, if guestvmcidr is a subset of network cidr but not a subset of cidr, exception is thrown.

2013-04-19 Thread Sateesh Chodapuneedi

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

Ship it!


Lookd good to me!

- Sateesh Chodapuneedi


On March 22, 2013, 11:40 a.m., Saksham Srivastava wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10084/
> ---
> 
> (Updated March 22, 2013, 11:40 a.m.)
> 
> 
> Review request for cloudstack, Murali Reddy and Sateesh Chodapuneedi.
> 
> 
> Description
> ---
> 
> The following scenario:
> 
> networkcidr: 10.1.1.0/24
> 
> cidr: 10.1.1.224/27
> 
> Applying reservation with guestvmcidr: 10.1.1.0/26 results in exception:
> Invalid value of Guest VM CIDR. For IP Reservation, Guest VM CIDR should be a 
> subset of network CIDR: 10.1.1.224/27
> 
> Expected behavior:
> Reservation should happen and new cidr should be 10.1.1.0/26
> 
> 
> This addresses bug CLOUDSTACK-1786.
> 
> 
> Diffs
> -
> 
>   server/src/com/cloud/network/NetworkServiceImpl.java 8303b0b 
> 
> Diff: https://reviews.apache.org/r/10084/diff/
> 
> 
> Testing
> ---
> 
> Manually tested the scenario, reservation occurs and cidr becomes 10.1.1.0/26
> 
> 
> Thanks,
> 
> Saksham Srivastava
> 
>



Re: Review Request: Add docs for MidoNet networking plugin [CLOUDSTACK-996]

2013-04-19 Thread Dave Cahill

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

(Updated April 19, 2013, 8:35 a.m.)


Review request for cloudstack, Hugo Trippaers and Chiradeep Vittal.


Changes
---

Addressed Jessica's comments.


Description
---

Adding docs for MidoNet networking plugin [CLOUDSTACK-996]

Plugin itself is awaiting review / commit here:
[PATCH 1] https://reviews.apache.org/r/9897/
[PATCH 2] https://reviews.apache.org/r/9898/


This addresses bug CLOUDSTACK-996.


Diffs (updated)
-

  docs/en-US/MidoNet_Plugin_Guide.ent PRE-CREATION 
  docs/en-US/MidoNet_Plugin_Guide.xml PRE-CREATION 
  docs/en-US/plugin-midonet-about.xml PRE-CREATION 
  docs/en-US/plugin-midonet-features.xml PRE-CREATION 
  docs/en-US/plugin-midonet-introduction.xml PRE-CREATION 
  docs/en-US/plugin-midonet-preparations.xml PRE-CREATION 
  docs/en-US/plugin-midonet-provider.xml PRE-CREATION 
  docs/en-US/plugin-midonet-revisions.xml PRE-CREATION 
  docs/en-US/plugin-midonet-ui.xml PRE-CREATION 
  docs/en-US/plugin-midonet-usage.xml PRE-CREATION 
  docs/publican-plugin-midonet.cfg PRE-CREATION 

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


Testing
---

Built docs.


Thanks,

Dave Cahill



Re: Create rbd primary storage fail in CS 4.0.1

2013-04-19 Thread Wido den Hollander

Hi,

On 04/19/2013 08:48 AM, Guangjian Liu wrote:

Ceph file system can added as Primary storage by RBD, Thanks.



Great!


Now I meet the problem in creating VM to Ceph.

First I create computer offer and storage offer with tag "ceph", and
define Ceph Primary storage with tag "ceph".
Then I create VM use "ceph" computer offer, It display exception in Log.
It seems the storage size out off usage.



That is indeed odd. How big is the Ceph cluster? (ceph -s).

And what does libvirt say?

1. Log on to a hypervisor
2. virsh pool-list
3. virsh pool-info 

I'm curious about what libvirt reports as pool size.

Wido


Create VM fail
2013-04-18 10:23:27,559 DEBUG
[storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-1:job-24)
Is storage pool shared? true
2013-04-18 10:23:27,561 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-1:job-24) Checking pool 209 for storage, totalSize:
146673582080, *usedBytes: 33780317214998658*, usedPct:
230309.48542985672, disable threshold: 0.85
2013-04-18 10:23:27,561 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-1:job-24) Insufficient space on pool: 209 since its usage
percentage: 230309.48542985672 has crossed the
pool.storage.capacity.disablethreshold: 0.85
2013-04-18 10:23:27,561 DEBUG
[storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-1:job-24)
FirstFitStoragePoolAllocator returning 0 suitable storage pools
2013-04-18 10:23:27,561 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-1:job-24) No suitable pools found for volume:
Vol[8|vm=8|ROOT] under cluster: 1
2013-04-18 10:23:27,562 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-1:job-24) No suitable pools found
2013-04-18 10:23:27,562 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-1:job-24) No suitable storagePools found under this Cluster: 1
2013-04-18 10:23:27,562 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-1:job-24) Could not find suitable Deployment Destination
for this VM under any clusters, returning.
2013-04-18 10:23:27,640 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-1:job-24) VM state transitted from :Starting to Stopped
with event: OperationFailedvm's original host id: null new host id: null
host id before state transition: null
2013-04-18 10:23:27,645 DEBUG [cloud.vm.UserVmManagerImpl]
(Job-Executor-1:job-24) Destroying vm VM[User|ceph-1] as it failed to create
management-server.7z 2013-04-18 10:02

I check CS Web GUI and Database, the storage Allocated 30723TB, but
actually the total size is 138GB.
Inline image 1


mysql> select * from storage_pool;
+-+-+--+---+--++++---++--+---+-+-+-+-++
| id  | name| uuid | pool_type
   | port | data_center_id | pod_id | cluster_id | available_bytes   |
capacity_bytes | host_address | user_info | path| created
   | removed | update_time | status |
+-+-+--+---+--++++---++--+---+-+-+-+-++
| 200 | primary | d9474b9d-afa1-3737-a13b-df333dae295f |
NetworkFilesystem | 2049 |  1 |  1 |  1 |
10301210624 |61927849984 | 10.0.0.42| NULL  |
/export/primary | 2013-04-17 06:25:47 | NULL| NULL| Up |
| 209 | ceph| 18559bbf-cd1a-3fcc-a4d2-e95cd4f2d78c | RBD
   | 6789 |  1 |  1 |  1 | 33780317214998658 |
146673582080 | 10.0.0.41| : | rbd | 2013-04-18
02:02:00 | NULL| NULL| Up |
+-+-+--+---+--++++---++--+---+-+-+-+-++
2 rows in set (0.00 sec)





On Thu, Apr 18, 2013 at 3:54 AM, Wido den Hollander mailto:w...@widodh.nl>> wrote:

Hi,


On 04/17/2013 03:01 PM, Guangjian Liu wrote:

I still meet the same result.

In ubuntu 12.04,
1. I install libvirt-dev as below,
 apt-get install libvirt-dev
2. rebuild libvirt, see detail build log in attach.
root@ubuntu:~/install/libvirt-__0.10.2# ./autogen.sh
running CONFIG_SHELL=/bin/bash /bin/bash ./configure --enable-rbd
--no-create --no-recursion
configure: WARNING: unrecognized options: --enable-rbd


The correct option is "--with-storage-rbd"

But check the output of configure, it should tell you whether RBD
was enabled or not.

Then verify again if you can create a RBD storage pool manually via
libvirt.

Wido

.
make
make install



O

Re: Review Request: CLOUDSTACK-1786: While reserving IPs in guest network, if guestvmcidr is a subset of network cidr but not a subset of cidr, exception is thrown.

2013-04-19 Thread ASF Subversion and Git Services

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


Commit ea893eaf338bfe914e1cb99517a8429128a64152 in branch refs/heads/master 
from Sateesh Chodapuneedi 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ea893ea ]

CLOUDSTACK-1786: While reserving IPs in guest network, if guestvmcidr is a 
subset of network cidr but not a subset of cidr, exception is thrown.

Signed-off-by: Sateesh Chodapuneedi 


- ASF Subversion and Git Services


On March 22, 2013, 11:40 a.m., Saksham Srivastava wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10084/
> ---
> 
> (Updated March 22, 2013, 11:40 a.m.)
> 
> 
> Review request for cloudstack, Murali Reddy and Sateesh Chodapuneedi.
> 
> 
> Description
> ---
> 
> The following scenario:
> 
> networkcidr: 10.1.1.0/24
> 
> cidr: 10.1.1.224/27
> 
> Applying reservation with guestvmcidr: 10.1.1.0/26 results in exception:
> Invalid value of Guest VM CIDR. For IP Reservation, Guest VM CIDR should be a 
> subset of network CIDR: 10.1.1.224/27
> 
> Expected behavior:
> Reservation should happen and new cidr should be 10.1.1.0/26
> 
> 
> This addresses bug CLOUDSTACK-1786.
> 
> 
> Diffs
> -
> 
>   server/src/com/cloud/network/NetworkServiceImpl.java 8303b0b 
> 
> Diff: https://reviews.apache.org/r/10084/diff/
> 
> 
> Testing
> ---
> 
> Manually tested the scenario, reservation occurs and cidr becomes 10.1.1.0/26
> 
> 
> Thanks,
> 
> Saksham Srivastava
> 
>



Re: Review Request: CLOUDSTACK-1786: While reserving IPs in guest network, if guestvmcidr is a subset of network cidr but not a subset of cidr, exception is thrown.

2013-04-19 Thread Sateesh Chodapuneedi

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

Ship it!


Branch: refs/heads/master
Commit: ea893eaf338bfe914e1cb99517a8429128a64152
Parents: 21ce3be


- Sateesh Chodapuneedi


On March 22, 2013, 11:40 a.m., Saksham Srivastava wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10084/
> ---
> 
> (Updated March 22, 2013, 11:40 a.m.)
> 
> 
> Review request for cloudstack, Murali Reddy and Sateesh Chodapuneedi.
> 
> 
> Description
> ---
> 
> The following scenario:
> 
> networkcidr: 10.1.1.0/24
> 
> cidr: 10.1.1.224/27
> 
> Applying reservation with guestvmcidr: 10.1.1.0/26 results in exception:
> Invalid value of Guest VM CIDR. For IP Reservation, Guest VM CIDR should be a 
> subset of network CIDR: 10.1.1.224/27
> 
> Expected behavior:
> Reservation should happen and new cidr should be 10.1.1.0/26
> 
> 
> This addresses bug CLOUDSTACK-1786.
> 
> 
> Diffs
> -
> 
>   server/src/com/cloud/network/NetworkServiceImpl.java 8303b0b 
> 
> Diff: https://reviews.apache.org/r/10084/diff/
> 
> 
> Testing
> ---
> 
> Manually tested the scenario, reservation occurs and cidr becomes 10.1.1.0/26
> 
> 
> Thanks,
> 
> Saksham Srivastava
> 
>



Re: Review Request: NPE while migrating volume

2013-04-19 Thread Devdeep Singh

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

(Updated April 19, 2013, 9:34 a.m.)


Review request for cloudstack and edison su.


Changes
---

Updated the patch after merging with the latest changes on master.


Description
---

The state transitions on the volume that has to be migrated were incorrect. A 
volume to be migrated is in ready state and cannot be transitioned to copying 
state. Similarly, the duplicated volume is in ready state too and cannot be 
transitioned to creating state. Fixed it by transitioning the volume to 
migrating state when a migrateVolume api call is made. Also, a volume has to be 
destroyed first before it can be expunged. Fixed that too.


This addresses bug https://issues.apache.org/jira/browse/CLOUDSTACK-1879.


Diffs (updated)
-

  
engine/storage/volume/src/org/apache/cloudstack/storage/volume/VolumeServiceImpl.java
 e3526de 

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


Testing
---

1. migrated a volume from one storage pool to another and made sure it was 
successful. Attached it to a vm after migrating.
2. Also verified that the patch applies successfully.


Thanks,

Devdeep Singh



Re: Review Request: CLOUDSTACK-1647: IP Reservation should not happen if the guest-vm cidr and network cidr is not same but their start ip and end ip are same.

2013-04-19 Thread Saksham Srivastava

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

(Updated April 19, 2013, 9:45 a.m.)


Review request for cloudstack, Murali Reddy and Sateesh Chodapuneedi.


Changes
---

Added new Utility in NetUtils to check if 2 CIDRs have same IP ranges.


Description
---

In cases where the start ip and end ip of guest vm cidr and network cidr are 
same, even when the cidrs appear to be different,the reservation procedure 
should not go through and user should get a message mentioning that.
Added extra check for the same with proper alert message.


This addresses bug CLOUDSTACK-1647.


Diffs (updated)
-

  server/src/com/cloud/network/NetworkServiceImpl.java 878d2a8 
  utils/src/com/cloud/utils/net/NetUtils.java 5988dd5 

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


Testing
---

CIDR : 10.0.144.0/20, Network CIDR : null, guestVmCidr : 10.0.151.0/20 => 
Reservation is not applied.
CIDR : 10.0.144.0/21, Network CIDR : 10.0.144.0/20, guestVmCidr : 10.0.151.0/20 
=> Existing Reservation is not affected.


Thanks,

Saksham Srivastava



Re: Review Request: CLOUDSTACK-1647: IP Reservation should not happen if the guest-vm cidr and network cidr is not same but their start ip and end ip are same.

2013-04-19 Thread Saksham Srivastava


> On April 18, 2013, 5:21 p.m., Sateesh Chodapuneedi wrote:
> > server/src/com/cloud/network/NetworkServiceImpl.java, line 1888
> > 
> >
> > This code seems dueplicated because the logic to calculate reserved ip 
> > range can be used to check if there exists some ip range to be reserved or 
> > not. If the calculated range is empty then do not attempt to reserve. Code 
> > to prepare response object already had this logic. May be we have to move 
> > this to NetUtils and call that from both places.

Thanks for the comment.

I have added the logic to NetUtils.java to maker it more generic and usable.
However the response method does not need to call this boolean function, so 
making changes only in API checks.


- Saksham


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


On April 19, 2013, 9:45 a.m., Saksham Srivastava wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10005/
> ---
> 
> (Updated April 19, 2013, 9:45 a.m.)
> 
> 
> Review request for cloudstack, Murali Reddy and Sateesh Chodapuneedi.
> 
> 
> Description
> ---
> 
> In cases where the start ip and end ip of guest vm cidr and network cidr are 
> same, even when the cidrs appear to be different,the reservation procedure 
> should not go through and user should get a message mentioning that.
> Added extra check for the same with proper alert message.
> 
> 
> This addresses bug CLOUDSTACK-1647.
> 
> 
> Diffs
> -
> 
>   server/src/com/cloud/network/NetworkServiceImpl.java 878d2a8 
>   utils/src/com/cloud/utils/net/NetUtils.java 5988dd5 
> 
> Diff: https://reviews.apache.org/r/10005/diff/
> 
> 
> Testing
> ---
> 
> CIDR : 10.0.144.0/20, Network CIDR : null, guestVmCidr : 10.0.151.0/20 => 
> Reservation is not applied.
> CIDR : 10.0.144.0/21, Network CIDR : 10.0.144.0/20, guestVmCidr : 
> 10.0.151.0/20 => Existing Reservation is not affected.
> 
> 
> Thanks,
> 
> Saksham Srivastava
> 
>



Re: [ASFCS42] Proposed schedule for our next release

2013-04-19 Thread Murali Reddy

Pardon my ignorance of project management, but it appears to me we are
talking of managing a release after half way through the cycle. May be
this is orthogonal discussion, but how about taking approach of planning a
release early in the cycle (at least for future releases)? Having a time
window between each release where we actually plan for the next release.
Discussions include - direction of the project, what big features are to
be included, rough estimate of the effort, risks and timelines would help
in planning releases better? Perhaps we should use Collab conferences for
this purpose, where we can plan for the next release (apart from show
casing the features of previous release). Since Collab is also scheduled
to happen on a half-yearly timeline it makes this easier to execute
release management starting from there.


On 19/04/13 8:21 AM, "Chip Childers"  wrote:

>On Apr 18, 2013, at 10:29 PM, David Nalley  wrote:
>
>> On Thu, Apr 18, 2013 at 10:26 PM, Chiradeep Vittal
>>  wrote:
>>>
>>>
>>> On 4/18/13 6:41 PM, "David Nalley"  wrote:
>>>
 On Thu, Apr 18, 2013 at 6:26 PM, Will Chan 
wrote:
>
>> -Original Message-
>> From: Chip Childers [mailto:chip.child...@sungard.com]
>> Sent: Monday, April 15, 2013 7:22 AM
>> To: dev@cloudstack.apache.org
>> Cc: cloudstack-...@incubator.apache.org
>> Subject: Re: [ASFCS42] Proposed schedule for our next release
>>
>> On Thu, Apr 11, 2013 at 02:50:02PM -0700, Animesh Chaturvedi wrote:
>>>
>>> I want to call out my concern on technical debt we have accumulated
> so
>> far.
>>>
>>> I did an analysis on JIRA bugs yesterday night PST on "Affects
>>> Version = 4.1" and created since Dec 2012
>>>
>>> Total records : 429
>>> Resolution Type (Invalid, Duplicate, Cannot reproduce etc.) : 87
>>>(30
>>> Blockers, 27 Critical, 27 Major, 4 Minor) Valid Defects  : 429-87=
> 342
>>> Fixed : 246 (60 Blockers, 70 Critical, 99 Majors) out of which 217
>>> were fixed since Feb Unresolved : 96 (1 Blocker, 8 Critical, 64
> Major)
>>>
>>> With this data it looks like we have fixed 2/3 of valid defects in
> little over
>> 2 months and pretty much deferring around 1/3 rd of issues for
>>future
>> release.
>>>
>>> I also looked at overall backlog of bugs (Critical, Major and
> Blockers only)
>> as of 4/10/2013 - 10:0PM PST.
>>>
>>> 284 open (18 Blocker, 38 Critical, 228 Major) ; By Fix version
>>>-  Release 4.0.x and prior: 13
>>>-  4.1: 70
>>>-  4.2 : 97
>>>-  Future: 8
>>>-  No version: 107
>>>
>>> Looking at that we fixed 217 bugs in roughly 2 months during 4.1
> cycle,
>> fixing the backlog of bug  will probably take us 2 months.  Should
>>we
> extend
>> the 4.2 test cycle by 2 months [Original Schedule: 6/1 - 7/22,
> Extended
>> Schedule: 6/1-9/22] to reduce the technical debt significantly? I
> would like
>> to hear how community wants to address technical debt. Based on the
>> input and consensus I will publish the agreed schedule next week.
>>
>> I don't think that an extension of time changes bug counts really.
> IMO, we
>> need to pull together to have some bug-fix focused effort applied to
> the
>> code-base.  It's also another reason that I'm so big on making sure
> that
>> automated tests come in with the new features.  That doesn't address
> test
>> scenarios that human testers can come up with, but if a developer
> spends
>> the time to think about testing the basic feature and codifies that,
> we
>> should at least avoid the "this actually doesn't work at all" types
> of bugs.
>>
>> There's a school of thought that says, don't build another feature
> until you
>> have sorted out the known bugs in the current features.  I don't
> think we
>> could really pull that off, but perhaps a different thread to rally
> people
>> around the bug backlog is in order?
>>
>> -chip
>
> Sorry to chime in so late to this thread as I've been offsite for the
> better part of this week.  I was one of the original 4 month release
> crowd but after the recent two releases of ACS, I'm starting to
>wonder
> if we shouldn't start moving this to a 6 month cycle instead of two.
> Here are some high level observations based on the previous two
>releases:
>
> 1. It doesn't seem like we are on a true 4 month time based release
> schedule.  Both 4.0 and 4.1 were delayed more than several weeks
>past the
> original proposed GA date.  4.0 was released 11/6 and let's assume
>that
> 4.1 will ship within a week or two.  That's almost a 6 month release
> cycle.

 So both 4.0 and 4.1 strike me as extraordinary. 4.0 was our first
 release - and we had lots of issues to resolve. 4.1 introduced

what are the technical reason for not supporting security groups on ovs?

2013-04-19 Thread Venkata SwamyBabu Budumuru
Thanks,
SWAMY


Re: Review Request: NPE while migrating volume

2013-04-19 Thread Abhinandan Prateek

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

Ship it!


Ship It!

- Abhinandan Prateek


On April 19, 2013, 9:34 a.m., Devdeep Singh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10539/
> ---
> 
> (Updated April 19, 2013, 9:34 a.m.)
> 
> 
> Review request for cloudstack and edison su.
> 
> 
> Description
> ---
> 
> The state transitions on the volume that has to be migrated were incorrect. A 
> volume to be migrated is in ready state and cannot be transitioned to copying 
> state. Similarly, the duplicated volume is in ready state too and cannot be 
> transitioned to creating state. Fixed it by transitioning the volume to 
> migrating state when a migrateVolume api call is made. Also, a volume has to 
> be destroyed first before it can be expunged. Fixed that too.
> 
> 
> This addresses bug https://issues.apache.org/jira/browse/CLOUDSTACK-1879.
> 
> 
> Diffs
> -
> 
>   
> engine/storage/volume/src/org/apache/cloudstack/storage/volume/VolumeServiceImpl.java
>  e3526de 
> 
> Diff: https://reviews.apache.org/r/10539/diff/
> 
> 
> Testing
> ---
> 
> 1. migrated a volume from one storage pool to another and made sure it was 
> successful. Attached it to a vm after migrating.
> 2. Also verified that the patch applies successfully.
> 
> 
> Thanks,
> 
> Devdeep Singh
> 
>



RE: what are the technical reason for not supporting security groups on ovs?

2013-04-19 Thread Venkata SwamyBabu Budumuru
By mistake, hit the send button before writing the actual message 


Looks like cloudstack + Xen only supports SecurityGroups with bridge as 
backend. Can someone shed some light on the technical reasons behind we we 
don't support it on OVS?

Thanks,
SWAMY

-Original Message-
From: Venkata SwamyBabu Budumuru [mailto:venkataswamybabu.budum...@citrix.com] 
Sent: Friday, 19 April 2013 3:56 PM
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: what are the technical reason for not supporting security groups on 
ovs?

Thanks,
SWAMY


Re: Review Request: NPE while migrating volume

2013-04-19 Thread Abhinandan Prateek


> On April 19, 2013, 10:43 a.m., Abhinandan Prateek wrote:
> > Ship It!

committed


- Abhinandan


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


On April 19, 2013, 9:34 a.m., Devdeep Singh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10539/
> ---
> 
> (Updated April 19, 2013, 9:34 a.m.)
> 
> 
> Review request for cloudstack and edison su.
> 
> 
> Description
> ---
> 
> The state transitions on the volume that has to be migrated were incorrect. A 
> volume to be migrated is in ready state and cannot be transitioned to copying 
> state. Similarly, the duplicated volume is in ready state too and cannot be 
> transitioned to creating state. Fixed it by transitioning the volume to 
> migrating state when a migrateVolume api call is made. Also, a volume has to 
> be destroyed first before it can be expunged. Fixed that too.
> 
> 
> This addresses bug https://issues.apache.org/jira/browse/CLOUDSTACK-1879.
> 
> 
> Diffs
> -
> 
>   
> engine/storage/volume/src/org/apache/cloudstack/storage/volume/VolumeServiceImpl.java
>  e3526de 
> 
> Diff: https://reviews.apache.org/r/10539/diff/
> 
> 
> Testing
> ---
> 
> 1. migrated a volume from one storage pool to another and made sure it was 
> successful. Attached it to a vm after migrating.
> 2. Also verified that the patch applies successfully.
> 
> 
> Thanks,
> 
> Devdeep Singh
> 
>



Unable to add XenServer host to basic zone

2013-04-19 Thread Venkata SwamyBabu Budumuru
Hi,

I am seeing the following issue on the MASTER build. Currently I filled it with 
priority set to "critical". If anyone else seeing the same either you can apply 
the workaround mentioned in the bug or you can raise the priority.

https://issues.apache.org/jira/browse/CLOUDSTACK-2115 - [BasicZone-XenServer] 
Unable to add host to basic zone that is configured with bridge

Thanks,
SWAMY


Re: Unable to add XenServer host to basic zone

2013-04-19 Thread prasanna
On 19 April 2013 16:29, Venkata SwamyBabu Budumuru
 wrote:
> Hi,
>
> I am seeing the following issue on the MASTER build. Currently I filled it 
> with priority set to "critical". If anyone else seeing the same either you 
> can apply the workaround mentioned in the bug or you can raise the priority.
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-2115 - [BasicZone-XenServer] 
> Unable to add host to basic zone that is configured with bridge

Would you like to submit a patch request with the
result.lower().strip() applied to the vmops plugin? Seems like a
fairly trivial fix.


ReviewRequest: Storage XenMotion Test Plan

2013-04-19 Thread Srikanteswararao Talluri
Please review the test plan for Storage XenMotion and post your comments if any.

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Storage+Xenmotion+Test+Plan

Thanks,
~Talluri


[ACS42][QA]Review Request : CISCO ASA 1000v Firewall Integration Test Plan

2013-04-19 Thread Sailaja Mada
Hi,

CISCO ASA 1000v Firewall Integration Test Plan :  
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CISCO+ASA+Firewall+Test+Plan


Please review the test plan and provide the inputs.



Jira ID: https://issues.apache.org/jira/browse/CLOUDSTACK-742
FS: http://cwiki.apache.org/confluence/display/CLOUDSTACK/Cisco+VNMC+integration

Thanks,
Sailaja.M


Re: failing mvn -P deps in CS 4.0.1

2013-04-19 Thread Ajimangun lintang mas
yes, my pc connected to vpn for internet connectivity. this problem comes
from maven/pom configuration or about internet connectivity?

2013/4/18 Chip Childers 

> On Thu, Apr 18, 2013 at 04:11:42PM +0700, Ajimangun lintang mas wrote:
> > # mvn -P deps
> > [INFO] Scanning for projects...
> > Downloading:
> > http://repo.maven.apache.org/maven2/org/apache/apache/11/apache-11.pom
> > [ERROR] The build could not read 1 project -> [Help 1]
> > [ERROR]
> > [ERROR]   The project
> > org.apache.cloudstack:cloudstack:4.0.1-incubating-SNAPSHOT
> > (/usr/local/apache-cloudstack-4.0.1-incubating-src/pom.xml) has 1 error
> > [ERROR] Non-resolvable parent POM: Could not transfer artifact
> > org.apache:apache:pom:11 from/to central (
> > http://repo.maven.apache.org/maven2): repo.maven.apache.org and
> > 'parent.relativePath' points at wrong local POM @ line 23, column 11:
> > Unknown host repo.maven.apache.org -> [Help 2]
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e
> > switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > [ERROR]
> > [ERROR] For more information about the errors and possible solutions,
> > please read the following articles:
> > [ERROR] [Help 1]
> >
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> > [ERROR] [Help 2]
> >
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> >
> > i've installed mysqld,maven,tomcat,java but when i want to pull
> > denpendencies for CS with "mvn -P deps" command, occuring proccess like
> > that. anybody can help?
> > thanks
>
> That sounds like a connectivity issue in getting to the
> repo.maven.apache.org site.  Are you doing this with a working
> connection to the Internet?  Perhaps the site was done temporarily?
>


Review Request: updated cloud-early-config to wait for the interfaces to IP come up

2013-04-19 Thread Jayapal Reddy

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

Review request for cloudstack, Anthony Urso, Abhinandan Prateek, and edison su.


Description
---

In VmWare setup, VR failed to get the route for management CIDR. This is 
happened because when route add command get executed there no eth1 interface 
set with ip.

So in cloud-early-config setup_interface added some delay to for interface to 
setup with ip.
 


This addresses bug CLOUDSTACK-2118.


Diffs
-

  patches/systemvm/debian/config/etc/init.d/cloud-early-config 3faa1bd 

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


Testing
---

1. Tested in vmware and xenserver VR.
2. Route for mgmt cidr on vmware and default routes added properly


Thanks,

Jayapal Reddy



Re: Review Request: updated cloud-early-config to wait for the interfaces to IP come up

2013-04-19 Thread Abhinandan Prateek

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

Ship it!


Ship It!

- Abhinandan Prateek


On April 19, 2013, 12:06 p.m., Jayapal Reddy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10647/
> ---
> 
> (Updated April 19, 2013, 12:06 p.m.)
> 
> 
> Review request for cloudstack, Anthony Urso, Abhinandan Prateek, and edison 
> su.
> 
> 
> Description
> ---
> 
> In VmWare setup, VR failed to get the route for management CIDR. This is 
> happened because when route add command get executed there no eth1 interface 
> set with ip.
> 
> So in cloud-early-config setup_interface added some delay to for interface to 
> setup with ip.
>  
> 
> 
> This addresses bug CLOUDSTACK-2118.
> 
> 
> Diffs
> -
> 
>   patches/systemvm/debian/config/etc/init.d/cloud-early-config 3faa1bd 
> 
> Diff: https://reviews.apache.org/r/10647/diff/
> 
> 
> Testing
> ---
> 
> 1. Tested in vmware and xenserver VR.
> 2. Route for mgmt cidr on vmware and default routes added properly
> 
> 
> Thanks,
> 
> Jayapal Reddy
> 
>



Re: [VOTE][ACS402] Apache CloudStack 4.0.2 (Second Round)

2013-04-19 Thread Sebastien Goasguen
+1 (binding)

tested based on procedure (except the comparison with git)
tested ec2 functionality as well.

On Apr 18, 2013, at 11:21 PM, Chip Childers  wrote:

> +1 (binding)
> 
> I tested based on the procedure outlined in the test document (after
> editing it a bit).  I did not test the EC2 functionality, but I did
> explore outside of the standard functional path.



RE: [VOTE][ACS402] Apache CloudStack 4.0.2 (Second Round)

2013-04-19 Thread Hugo Trippaers
+1 (binding)

Tested :
* Clean installation on clean Xen Hypervisors
* Upgrade from 4.0.1 to 4.0.2 with clean database
* Upgrade from 4.0.1 to 4.0.2 with copy of a production database
* Nicira L2 Features (QA NVP 001-006 and NVP 101-106)

General test procedure:
  Setup zone (with XenServer)
  CreateNetworkOffering
  CreateNetwork
  2x CreateInstance
  Ping A from B
  Ping internet from B

Cheers,

Hugo

> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Friday, April 19, 2013 5:22 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE][ACS402] Apache CloudStack 4.0.2 (Second Round)
> 
> +1 (binding)
> 
> I tested based on the procedure outlined in the test document (after editing
> it a bit).  I did not test the EC2 functionality, but I did explore outside 
> of the
> standard functional path.


[ACS41] Quick update on status

2013-04-19 Thread Chip Childers
Hi all,

My plan is to cut the RC on Monday for 4.1.0.

I'm waiting for final word on the fix that Hugo's working on for
CLOUDSTACK-2092, which he says he'll be done by COB his time today.

I have a task to modify our release procedure to account for some of the
changes we can make after graduation, and specifically to include the
use of the maven release plugin to set the version number in our
released POM files correctly.

I am *not* planning on pushing the release build to maven central as a
released version of the code at this time.  Unless someone objects, I
don't see much value in that.

Consider this *LAST CALL* for patches that aren't on my radar right now.
Docs, translations, bugs, whatever...

Am I missing anything?

-chip


Re: Review Request: add state change in createVolume back to Allocated if anything fails

2013-04-19 Thread Chip Childers

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

Ship it!


Ship It!

- Chip Childers


On April 19, 2013, 4:59 a.m., Marcus Sorensen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10623/
> ---
> 
> (Updated April 19, 2013, 4:59 a.m.)
> 
> 
> Review request for cloudstack and Chip Childers.
> 
> 
> Description
> ---
> 
> createVolume changes the volume state from 'Allocated' to 'Creating', but has 
> no code to change it back to 'Allocated' if anything goes wrong, despite 
> there already being a path from 'Creating' to 'Allocated' for volumes, via 
> the OperationFailed event. Adding this in fixes the issue and avoids leaving 
> disks in an unusable state.
> 
> 
> This addresses bug CLOUDSTACK-2104.
> 
> 
> Diffs
> -
> 
>   server/src/com/cloud/storage/StorageManagerImpl.java 624361f 
> 
> Diff: https://reviews.apache.org/r/10623/diff/
> 
> 
> Testing
> ---
> 
> Tested in devcloud-kvm, volume that was larger than primary storage failed to 
> attack, and went back to 'Allocated' from 'Creating' upon the failure. I was 
> then able to retry, and delete the disk.
> 
> 
> Thanks,
> 
> Marcus Sorensen
> 
>



Re: failing mvn -P deps in CS 4.0.1

2013-04-19 Thread Chip Childers
On Apr 19, 2013, at 8:01 AM, Ajimangun lintang mas
 wrote:

> yes, my pc connected to vpn for internet connectivity. this problem comes
> from maven/pom configuration or about internet connectivity?

I can tell you that I'm not having any issues.

>
> 2013/4/18 Chip Childers 
>
>> On Thu, Apr 18, 2013 at 04:11:42PM +0700, Ajimangun lintang mas wrote:
>>> # mvn -P deps
>>> [INFO] Scanning for projects...
>>> Downloading:
>>> http://repo.maven.apache.org/maven2/org/apache/apache/11/apache-11.pom
>>> [ERROR] The build could not read 1 project -> [Help 1]
>>> [ERROR]
>>> [ERROR]   The project
>>> org.apache.cloudstack:cloudstack:4.0.1-incubating-SNAPSHOT
>>> (/usr/local/apache-cloudstack-4.0.1-incubating-src/pom.xml) has 1 error
>>> [ERROR] Non-resolvable parent POM: Could not transfer artifact
>>> org.apache:apache:pom:11 from/to central (
>>> http://repo.maven.apache.org/maven2): repo.maven.apache.org and
>>> 'parent.relativePath' points at wrong local POM @ line 23, column 11:
>>> Unknown host repo.maven.apache.org -> [Help 2]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e
>>> switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>> [ERROR] For more information about the errors and possible solutions,
>>> please read the following articles:
>>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
>>> [ERROR] [Help 2]
>> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
>>>
>>> i've installed mysqld,maven,tomcat,java but when i want to pull
>>> denpendencies for CS with "mvn -P deps" command, occuring proccess like
>>> that. anybody can help?
>>> thanks
>>
>> That sounds like a connectivity issue in getting to the
>> repo.maven.apache.org site.  Are you doing this with a working
>> connection to the Internet?  Perhaps the site was done temporarily?
>>


Re: [VOTE][ACS402] Apache CloudStack 4.0.2 (Second Round)

2013-04-19 Thread Joe Brockmeier
On Thu, Apr 18, 2013, at 10:21 PM, Chip Childers wrote:
> +1 (binding)
> 
> I tested based on the procedure outlined in the test document (after
> editing it a bit).  I did not test the EC2 functionality, but I did
> explore outside of the standard functional path.

Thanks for taking the time to test, much appreciated!

Best,

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


Re: [VOTE][ACS402] Apache CloudStack 4.0.2 (Second Round)

2013-04-19 Thread Joe Brockmeier
On Fri, Apr 19, 2013, at 07:25 AM, Sebastien Goasguen wrote:
> +1 (binding)
> 
> tested based on procedure (except the comparison with git)
> tested ec2 functionality as well.

Thanks!

Best,

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


Re: [VOTE][ACS402] Apache CloudStack 4.0.2 (Second Round)

2013-04-19 Thread Joe Brockmeier
On Fri, Apr 19, 2013, at 08:12 AM, Hugo Trippaers wrote:
> +1 (binding)
> 
> Tested :
> * Clean installation on clean Xen Hypervisors
> * Upgrade from 4.0.1 to 4.0.2 with clean database
> * Upgrade from 4.0.1 to 4.0.2 with copy of a production database
> * Nicira L2 Features (QA NVP 001-006 and NVP 101-106)
> 
> General test procedure:
>   Setup zone (with XenServer)
>   CreateNetworkOffering
>   CreateNetwork
>   2x CreateInstance
>   Ping A from B
>   Ping internet from B

Awesome - thanks Hugo!

Best,

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


Re: Review Request: CLOUDSTACK-1647: IP Reservation should not happen if the guest-vm cidr and network cidr is not same but their start ip and end ip are same.

2013-04-19 Thread Chip Childers

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


These new methods are *prime* candidates for having unit tests.  Please provide 
some test that cover the stated manual test conditions in the patch before it's 
committed.

- Chip Childers


On April 19, 2013, 9:45 a.m., Saksham Srivastava wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10005/
> ---
> 
> (Updated April 19, 2013, 9:45 a.m.)
> 
> 
> Review request for cloudstack, Murali Reddy and Sateesh Chodapuneedi.
> 
> 
> Description
> ---
> 
> In cases where the start ip and end ip of guest vm cidr and network cidr are 
> same, even when the cidrs appear to be different,the reservation procedure 
> should not go through and user should get a message mentioning that.
> Added extra check for the same with proper alert message.
> 
> 
> This addresses bug CLOUDSTACK-1647.
> 
> 
> Diffs
> -
> 
>   server/src/com/cloud/network/NetworkServiceImpl.java 878d2a8 
>   utils/src/com/cloud/utils/net/NetUtils.java 5988dd5 
> 
> Diff: https://reviews.apache.org/r/10005/diff/
> 
> 
> Testing
> ---
> 
> CIDR : 10.0.144.0/20, Network CIDR : null, guestVmCidr : 10.0.151.0/20 => 
> Reservation is not applied.
> CIDR : 10.0.144.0/21, Network CIDR : 10.0.144.0/20, guestVmCidr : 
> 10.0.151.0/20 => Existing Reservation is not affected.
> 
> 
> Thanks,
> 
> Saksham Srivastava
> 
>



Re: Review Request: CLOUDSTACK-1647: IP Reservation should not happen if the guest-vm cidr and network cidr is not same but their start ip and end ip are same.

2013-04-19 Thread Chip Childers
On Fri, Apr 19, 2013 at 09:51:56AM +, Saksham Srivastava wrote:
> 
> 
> > On April 18, 2013, 5:21 p.m., Sateesh Chodapuneedi wrote:
> > > server/src/com/cloud/network/NetworkServiceImpl.java, line 1888
> > > 
> > >
> > > This code seems dueplicated because the logic to calculate reserved 
> > > ip range can be used to check if there exists some ip range to be 
> > > reserved or not. If the calculated range is empty then do not attempt to 
> > > reserve. Code to prepare response object already had this logic. May be 
> > > we have to move this to NetUtils and call that from both places.
> 
> Thanks for the comment.
> 
> I have added the logic to NetUtils.java to maker it more generic and usable.
> However the response method does not need to call this boolean function, so 
> making changes only in API checks.

Please see me comment in the review board record.  These new methods are
easily unit tested, so I'd like to see some unit tests to confirm
functionality (positive and negative tests please).


Re: [ASFCS42] Proposed schedule for our next release

2013-04-19 Thread Prasanna Santhanam
On Fri, Apr 19, 2013 at 10:16:35AM +, Murali Reddy wrote:
> 
> Pardon my ignorance of project management, but it appears to me we are
> talking of managing a release after half way through the cycle. May be
> this is orthogonal discussion, but how about taking approach of planning a
> release early in the cycle (at least for future releases)? Having a time
> window between each release where we actually plan for the next release.
> Discussions include - direction of the project, what big features are to
> be included, rough estimate of the effort, risks and timelines would help
> in planning releases better? Perhaps we should use Collab conferences for
> this purpose, where we can plan for the next release (apart from show
> casing the features of previous release). Since Collab is also scheduled
> to happen on a half-yearly timeline it makes this easier to execute
> release management starting from there.

I actually like the idea of 'collab conference' to do release
planning! So +1 to that.

-- 
Prasanna.,


Re: 4.1 Build Stalls

2013-04-19 Thread Prasanna Santhanam
I took a look at the NioTest y'day but forgot to email back. It seems
like there is server created and a client and until the client link
comes up we wait on a never ending while loop. Sometimes that
clientLink doesn't initialize when this stalling happens.

I'll have to see how wireless affects this ...

On Thu, Apr 18, 2013 at 05:14:01AM +, Daan Hoogland wrote:
> I had the same thing runnning mvn -P developer clean test install. I
> was on wireless and it worked with the same command a bit later.
> Apparently without  changes, no code update at least.
> 
> Regards,
> 
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
> Sent: donderdag 18 april 2013 5:19
> To: dev@cloudstack.apache.org
> Subject: Re: 4.1 Build Stalls
> 
> Today I am (working from home)...now that I think of it, I can't remember 
> this ever happening when I'm in the office and not on wireless.
> 
> What were you thinking the issue might be?
> 
> 
> On Wed, Apr 17, 2013 at 8:41 PM, prasanna  wrote:
> 
> >  I've seen this stalling happen for me. Wild guess - Are you on 
> > wireless by any chance?
> >
> > On 18 April 2013 05:16, Mike Tutkowski 
> > wrote:
> > > Actually, it seems kind of random.
> > >
> > > I'm trying to build 4.2 now and I had the same problem.  I just 
> > > cleaned
> > and
> > > installed and eventually it got past the stall.
> > >
> > >
> > > On Wed, Apr 17, 2013 at 2:35 PM, Chip Childers <
> > chip.child...@sungard.com>wrote:
> > >
> > >> On Wed, Apr 17, 2013 at 02:34:29PM -0600, Mike Tutkowski wrote:
> > >> > Sorry...I followed up with that in a subsequent e-mail...I should 
> > >> > have
> > >> put
> > >> > it in the first one.  :)
> > >> >
> > >> > mvn clean install -P developer,systemvm
> > >> >
> > >> > I then sent an e-mail saying this worked:
> > >> >
> > >> > mvn clean
> > >> > mvn install -P developer,systemvm
> > >>
> > >> It *might* be something in the developer or systemvm profiles.
> > >>
> > >> >
> > >> >
> > >> > On Wed, Apr 17, 2013 at 2:26 PM, Chip Childers <
> > >> chip.child...@sungard.com>wrote:
> > >> >
> > >> > > On Wed, Apr 17, 2013 at 02:23:04PM -0600, Mike Tutkowski wrote:
> > >> > > > Hi,
> > >> > > >
> > >> > > > Anyone know why the 4.1 build (updated from today) stalls for 
> > >> > > > me
> > >> here?:
> > >> > > >
> > >> > > > Running com.cloud.utils.testcase.NioTest
> > >> > > > 2013-04-17 14:20:07,810 INFO  [utils.testcase.NioTest] 
> > >> > > > (main:)
> > Test
> > >> > > > 2013-04-17 14:20:07,853 INFO  [utils.nio.NioServer]
> > >> > > > (NioTestServer-Selector:) NioConnection started and listening 
> > >> > > > on
> > >> > > > 0.0.0.0/0.0.0.0:
> > >> > > >
> > >> > > > Thanks!
> > >> > >
> > >> > > What build command are you using?
> > >> > >
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> > *Mike Tutkowski*
> > >> > *Senior CloudStack Developer, SolidFire Inc.*
> > >> > e: mike.tutkow...@solidfire.com
> > >> > o: 303.746.7302
> > >> > Advancing the way the world uses the 
> > >> > cloud
> > >> > *(tm)*
> > >>
> > >
> > >
> > >
> > > --
> > > *Mike Tutkowski*
> > > *Senior CloudStack Developer, SolidFire Inc.*
> > > e: mike.tutkow...@solidfire.com
> > > o: 303.746.7302
> > > Advancing the way the world uses the 
> > > cloud
> > > *(tm)*
> >
> 
> 
> 
> --
> *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)*

-- 
Prasanna.,


RE: qa tests for nicira code in 4.1

2013-04-19 Thread Daan Hoogland
LS,

Hugo fixed the issue in the nicira code that I came up with: commit 
44097eecef0a8695946efc9f62d2373945c79f7b contains the fix. The issue now has a 
unit test, com.cloud.network.element.NiciraNvpElementTest to assure it remains 
working properly. CLOUDSTACK-2092 will be closed by Hugo.

Regards,
Daan


-Original Message-
From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com] 
Sent: vrijdag 19 april 2013 9:26
To: dev@cloudstack.apache.org
Subject: RE: qa tests for nicira code in 4.1

H Rayess,

The tests are mostly manual as of yet. I am working with Hugo now to 
investigate the problem and will report back here

Daan Hoogland

-Original Message-
From: Rayees Namathponnan [mailto:rayees.namathpon...@citrix.com] 
Sent: vrijdag 19 april 2013 0:07
To: dev@cloudstack.apache.org
Subject: RE: qa tests for nicira code in 4.1

Hi Daan,

These test cases are in ASF repo ?

Regards,
Rayees 

-Original Message-
From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com] 
Sent: Thursday, April 18, 2013 12:38 PM
To: dev@cloudstack.apache.org
Subject: qa tests for nicira code in 4.1

LS,

At Schuberg Philis we did some tests on the 4.1 code for the tests in the 
following table
Test Case ID  Test Description Results
   Infrastructure
NVP-001 Create NVP Element pass
NVP-002 Disable NVP Elementpass
NVP-003 Enable NVP Element pass
NVP-004 Delete NVP Element  pass
NVP-005 Create NVP Device   pass
NVP-006 Delete NVP Devicepass
   L2 Functions
NVP-101 Create Logical Switchpass
NVP-102 Create Logical Portpass
NVP-103 Check Connection Pass
NVP-104 Check Connection Pass
NVP-105 Delete Logical SwitchPass
NVP-106 Delete Logical Port Pass
   L3 Functions
NVP-201 Create Logical RouterPass
NVP-202 Create Source Nat rule  Pass
NVP-203 Create Static Nat rulePass
NVP-204 Create Port FW rule   Pass
NVP-205 Check Source Nat rule  Pass
NVP-206 Check Static Nat rule Pass
NVP-207 Check Port FW rule   Pass
NVP-208 Delete Source Nat rule  Pass
NVP-209 Delete Static Nat rule Fail
NVP-210 Delete Port FW rule   Pass
NVP-211 Delete Logical RouterPass

The tests where partly done aith scripts but these are not yet complete and the 
remainder of functionality was done by hand.
For the failed test, NVP-209 a ticket was created, 'CLOUDSTACK-2092'. The 
problem in this case was that deleting the static rule did not result in the 
deletion of the ip adres from the logical router.

Kind regards,
Daan Hoogland


Re: qa tests for nicira code in 4.1

2013-04-19 Thread Chip Childers
On Fri, Apr 19, 2013 at 02:19:12PM +, Daan Hoogland wrote:
> LS,
> 
> Hugo fixed the issue in the nicira code that I came up with: commit 
> 44097eecef0a8695946efc9f62d2373945c79f7b contains the fix. The issue now has 
> a unit test, com.cloud.network.element.NiciraNvpElementTest to assure it 
> remains working properly. CLOUDSTACK-2092 will be closed by Hugo.
> 
> Regards,
> Daan

Hugo,

I see that was committed to 4.1.  Can you please be sure that it's in
master as well?

-chip


RE: qa tests for nicira code in 4.1

2013-04-19 Thread Daan Hoogland
Hy Sudha

Both tickets can be closed.

I am not sure what to do with the page you created for me. Do you want me to 
copy the table below, with the fail changed to pass, in a new child page there?

Regards,
Daan Hoogland

-Original Message-
From: Sudha Ponnaganti [mailto:sudha.ponnaga...@citrix.com] 
Sent: donderdag 18 april 2013 22:17
To: dev@cloudstack.apache.org
Subject: RE: qa tests for nicira code in 4.1

Thanks Daan for posting test results !

I have created a place holder for you to update test results [1] - You can 
update it at your convenience. 
Does this execution cover both of these stories for Nicira [2], [3]. If it 
covers both of these stories, may be these can be closed. Looks like doc is 
also outstanding as per the JIRA status. 

[1] 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.1+Test+Execution
[2] https://issues.apache.org/jira/browse/CLOUDSTACK-726
[3] https://issues.apache.org/jira/browse/CLOUDSTACK-727



Thanks
/Sudha

-Original Message-
From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com] 
Sent: Thursday, April 18, 2013 12:38 PM
To: dev@cloudstack.apache.org
Subject: qa tests for nicira code in 4.1

LS,

At Schuberg Philis we did some tests on the 4.1 code for the tests in the 
following table
Test Case ID  Test Description Results
   Infrastructure
NVP-001 Create NVP Element pass
NVP-002 Disable NVP Elementpass
NVP-003 Enable NVP Element pass
NVP-004 Delete NVP Element  pass
NVP-005 Create NVP Device   pass
NVP-006 Delete NVP Devicepass
   L2 Functions
NVP-101 Create Logical Switchpass
NVP-102 Create Logical Portpass
NVP-103 Check Connection Pass
NVP-104 Check Connection Pass
NVP-105 Delete Logical SwitchPass
NVP-106 Delete Logical Port Pass
   L3 Functions
NVP-201 Create Logical RouterPass
NVP-202 Create Source Nat rule  Pass
NVP-203 Create Static Nat rulePass
NVP-204 Create Port FW rule   Pass
NVP-205 Check Source Nat rule  Pass
NVP-206 Check Static Nat rule Pass
NVP-207 Check Port FW rule   Pass
NVP-208 Delete Source Nat rule  Pass
NVP-209 Delete Static Nat rule Fail
NVP-210 Delete Port FW rule   Pass
NVP-211 Delete Logical RouterPass

The tests where partly done aith scripts but these are not yet complete and the 
remainder of functionality was done by hand.
For the failed test, NVP-209 a ticket was created, 'CLOUDSTACK-2092'. The 
problem in this case was that deleting the static rule did not result in the 
deletion of the ip adres from the logical router.

Kind regards,
Daan Hoogland


Re: [ACS42][QA]Issues with latest Master Build (Xenserver)

2013-04-19 Thread Prasanna Santhanam
On Wed, Apr 17, 2013 at 09:47:04PM -0700, Sangeetha Hariharan wrote:
> When I deploy a Vm with service offering that has memory requirement
> set to 200.00 MB , Vm is in "Running" state but it actually has
> kernel panic.
> 
> I am able to deploy Vms successfully only using "Small Instance"
> service offering that has 512MB memory requirement.
> 
> Wanted to know why we are not able to deploy Vms with lesser RAM ?
> Is anybody else facing this issue?
> 

We actually deploy a number of tiny offering VMs (128MB) in our tests so as to
save capacity for all the tests in our automated test deployment. That happens 
on
Xen 6.0.2 hypervisors and uses the master branch packages. Haven't seen this
issue on our QA setup yet.

Can you do a xe vm-param-list uuid=?

You should see something like :
 memory-actual ( RO): 268435456
 memory-target ( RO): 268435456
 memory-overhead ( RO): 101711872
 memory-static-max ( RW): 8589934592
 memory-dynamic-max ( RW): 268435456
 memory-dynamic-min ( RW): 268435456
 memory-static-min ( RW): 134217728

Put up the out put on apaste.info/paste.cloudstack.org? Perhaps something got
tweaked inadvertently in your xenserver setup. We'd have to nail down if it's
CS or something else doing it.


-- 
Prasanna.,


Re: 4.1 Build Stalls

2013-04-19 Thread Mike Tutkowski
Thanks for looking into that! :)


On Fri, Apr 19, 2013 at 8:11 AM, Prasanna Santhanam  wrote:

> I took a look at the NioTest y'day but forgot to email back. It seems
> like there is server created and a client and until the client link
> comes up we wait on a never ending while loop. Sometimes that
> clientLink doesn't initialize when this stalling happens.
>
> I'll have to see how wireless affects this ...
>
> On Thu, Apr 18, 2013 at 05:14:01AM +, Daan Hoogland wrote:
> > I had the same thing runnning mvn -P developer clean test install. I
> > was on wireless and it worked with the same command a bit later.
> > Apparently without  changes, no code update at least.
> >
> > Regards,
> >
> > -Original Message-
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > Sent: donderdag 18 april 2013 5:19
> > To: dev@cloudstack.apache.org
> > Subject: Re: 4.1 Build Stalls
> >
> > Today I am (working from home)...now that I think of it, I can't
> remember this ever happening when I'm in the office and not on wireless.
> >
> > What were you thinking the issue might be?
> >
> >
> > On Wed, Apr 17, 2013 at 8:41 PM, prasanna  wrote:
> >
> > >  I've seen this stalling happen for me. Wild guess - Are you on
> > > wireless by any chance?
> > >
> > > On 18 April 2013 05:16, Mike Tutkowski 
> > > wrote:
> > > > Actually, it seems kind of random.
> > > >
> > > > I'm trying to build 4.2 now and I had the same problem.  I just
> > > > cleaned
> > > and
> > > > installed and eventually it got past the stall.
> > > >
> > > >
> > > > On Wed, Apr 17, 2013 at 2:35 PM, Chip Childers <
> > > chip.child...@sungard.com>wrote:
> > > >
> > > >> On Wed, Apr 17, 2013 at 02:34:29PM -0600, Mike Tutkowski wrote:
> > > >> > Sorry...I followed up with that in a subsequent e-mail...I should
> > > >> > have
> > > >> put
> > > >> > it in the first one.  :)
> > > >> >
> > > >> > mvn clean install -P developer,systemvm
> > > >> >
> > > >> > I then sent an e-mail saying this worked:
> > > >> >
> > > >> > mvn clean
> > > >> > mvn install -P developer,systemvm
> > > >>
> > > >> It *might* be something in the developer or systemvm profiles.
> > > >>
> > > >> >
> > > >> >
> > > >> > On Wed, Apr 17, 2013 at 2:26 PM, Chip Childers <
> > > >> chip.child...@sungard.com>wrote:
> > > >> >
> > > >> > > On Wed, Apr 17, 2013 at 02:23:04PM -0600, Mike Tutkowski wrote:
> > > >> > > > Hi,
> > > >> > > >
> > > >> > > > Anyone know why the 4.1 build (updated from today) stalls for
> > > >> > > > me
> > > >> here?:
> > > >> > > >
> > > >> > > > Running com.cloud.utils.testcase.NioTest
> > > >> > > > 2013-04-17 14:20:07,810 INFO  [utils.testcase.NioTest]
> > > >> > > > (main:)
> > > Test
> > > >> > > > 2013-04-17 14:20:07,853 INFO  [utils.nio.NioServer]
> > > >> > > > (NioTestServer-Selector:) NioConnection started and listening
> > > >> > > > on
> > > >> > > > 0.0.0.0/0.0.0.0:
> > > >> > > >
> > > >> > > > Thanks!
> > > >> > >
> > > >> > > What build command are you using?
> > > >> > >
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > *Mike Tutkowski*
> > > >> > *Senior CloudStack Developer, SolidFire Inc.*
> > > >> > e: mike.tutkow...@solidfire.com
> > > >> > o: 303.746.7302
> > > >> > Advancing the way the world uses the
> > > >> > cloud
> > > >> > *(tm)*
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > *Mike Tutkowski*
> > > > *Senior CloudStack Developer, SolidFire Inc.*
> > > > e: mike.tutkow...@solidfire.com
> > > > o: 303.746.7302
> > > > Advancing the way the world uses the
> > > > cloud
> > > > *(tm)*
> > >
> >
> >
> >
> > --
> > *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)*
>
> --
> Prasanna.,
>



-- 
*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: failing mvn -P deps in CS 4.0.1

2013-04-19 Thread Ajimangun lintang mas
how about your internet connectivity? with proxy or vpn too or not?


2013/4/19 Chip Childers 

> On Apr 19, 2013, at 8:01 AM, Ajimangun lintang mas
>  wrote:
>
> > yes, my pc connected to vpn for internet connectivity. this problem comes
> > from maven/pom configuration or about internet connectivity?
>
> I can tell you that I'm not having any issues.
>
> >
> > 2013/4/18 Chip Childers 
> >
> >> On Thu, Apr 18, 2013 at 04:11:42PM +0700, Ajimangun lintang mas wrote:
> >>> # mvn -P deps
> >>> [INFO] Scanning for projects...
> >>> Downloading:
> >>> http://repo.maven.apache.org/maven2/org/apache/apache/11/apache-11.pom
> >>> [ERROR] The build could not read 1 project -> [Help 1]
> >>> [ERROR]
> >>> [ERROR]   The project
> >>> org.apache.cloudstack:cloudstack:4.0.1-incubating-SNAPSHOT
> >>> (/usr/local/apache-cloudstack-4.0.1-incubating-src/pom.xml) has 1 error
> >>> [ERROR] Non-resolvable parent POM: Could not transfer artifact
> >>> org.apache:apache:pom:11 from/to central (
> >>> http://repo.maven.apache.org/maven2): repo.maven.apache.org and
> >>> 'parent.relativePath' points at wrong local POM @ line 23, column 11:
> >>> Unknown host repo.maven.apache.org -> [Help 2]
> >>> [ERROR]
> >>> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the
> >> -e
> >>> switch.
> >>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> >>> [ERROR]
> >>> [ERROR] For more information about the errors and possible solutions,
> >>> please read the following articles:
> >>> [ERROR] [Help 1]
> >>
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> >>> [ERROR] [Help 2]
> >>
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> >>>
> >>> i've installed mysqld,maven,tomcat,java but when i want to pull
> >>> denpendencies for CS with "mvn -P deps" command, occuring proccess like
> >>> that. anybody can help?
> >>> thanks
> >>
> >> That sounds like a connectivity issue in getting to the
> >> repo.maven.apache.org site.  Are you doing this with a working
> >> connection to the Internet?  Perhaps the site was done temporarily?
> >>
>


Re: failing mvn -P deps in CS 4.0.1

2013-04-19 Thread Chip Childers
On Fri, Apr 19, 2013 at 09:47:58PM +0700, Ajimangun lintang mas wrote:
> how about your internet connectivity? with proxy or vpn too or not?

Sorry, but I never access the internet via proxy or vpn.  You'll have to
look for help on general maven functionality when through a proxy.  This
is definitely something local to you.

-chip


Re: failing mvn -P deps in CS 4.0.1

2013-04-19 Thread Ajimangun lintang mas
okay... thanks for your suggestion. i'll try it and post the conclusion
later


2013/4/19 Chip Childers 

> On Fri, Apr 19, 2013 at 09:47:58PM +0700, Ajimangun lintang mas wrote:
> > how about your internet connectivity? with proxy or vpn too or not?
>
> Sorry, but I never access the internet via proxy or vpn.  You'll have to
> look for help on general maven functionality when through a proxy.  This
> is definitely something local to you.
>
> -chip
>


Re: [ASFCS42] Proposed schedule for our next release

2013-04-19 Thread Min Chen
I like this idea too, this will be a much better channel for community to
understand features to be planned. +1 to this.

-min

On 4/19/13 7:02 AM, "Prasanna Santhanam"  wrote:

>On Fri, Apr 19, 2013 at 10:16:35AM +, Murali Reddy wrote:
>> 
>> Pardon my ignorance of project management, but it appears to me we are
>> talking of managing a release after half way through the cycle. May be
>> this is orthogonal discussion, but how about taking approach of
>>planning a
>> release early in the cycle (at least for future releases)? Having a time
>> window between each release where we actually plan for the next release.
>> Discussions include - direction of the project, what big features are to
>> be included, rough estimate of the effort, risks and timelines would
>>help
>> in planning releases better? Perhaps we should use Collab conferences
>>for
>> this purpose, where we can plan for the next release (apart from show
>> casing the features of previous release). Since Collab is also scheduled
>> to happen on a half-yearly timeline it makes this easier to execute
>> release management starting from there.
>
>I actually like the idea of 'collab conference' to do release
>planning! So +1 to that.
>
>-- 
>Prasanna.,



[SCREENCAST] 4.0.2 testing procedure

2013-04-19 Thread Sebastien Goasguen
Hi,

I just uploaded an HD screencast that shows me testing the 4.0.2 release:
http://www.youtube.com/watch?v=vvgIkF1e1QE&list=PLb899uhkHRoZCRE00h_9CRgUSiHEgFDbC&index=1

Check it out and do it yourself, then vote !!!

-Sebastien

RE: qa tests for nicira code in 4.1

2013-04-19 Thread Sudha Ponnaganti
If you do additional tests or update any results, you can edit that page and 
update it. Otherwise I just copied your email,

If you don't mind, can you add a note to the ticket on the testing done and 
close them. Thanks

-Original Message-
From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com] 
Sent: Friday, April 19, 2013 7:27 AM
To: dev@cloudstack.apache.org
Subject: RE: qa tests for nicira code in 4.1

Hy Sudha

Both tickets can be closed.

I am not sure what to do with the page you created for me. Do you want me to 
copy the table below, with the fail changed to pass, in a new child page there?

Regards,
Daan Hoogland

-Original Message-
From: Sudha Ponnaganti [mailto:sudha.ponnaga...@citrix.com] 
Sent: donderdag 18 april 2013 22:17
To: dev@cloudstack.apache.org
Subject: RE: qa tests for nicira code in 4.1

Thanks Daan for posting test results !

I have created a place holder for you to update test results [1] - You can 
update it at your convenience. 
Does this execution cover both of these stories for Nicira [2], [3]. If it 
covers both of these stories, may be these can be closed. Looks like doc is 
also outstanding as per the JIRA status. 

[1] 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.1+Test+Execution
[2] https://issues.apache.org/jira/browse/CLOUDSTACK-726
[3] https://issues.apache.org/jira/browse/CLOUDSTACK-727



Thanks
/Sudha

-Original Message-
From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com] 
Sent: Thursday, April 18, 2013 12:38 PM
To: dev@cloudstack.apache.org
Subject: qa tests for nicira code in 4.1

LS,

At Schuberg Philis we did some tests on the 4.1 code for the tests in the 
following table
Test Case ID  Test Description Results
   Infrastructure
NVP-001 Create NVP Element pass
NVP-002 Disable NVP Elementpass
NVP-003 Enable NVP Element pass
NVP-004 Delete NVP Element  pass
NVP-005 Create NVP Device   pass
NVP-006 Delete NVP Devicepass
   L2 Functions
NVP-101 Create Logical Switchpass
NVP-102 Create Logical Portpass
NVP-103 Check Connection Pass
NVP-104 Check Connection Pass
NVP-105 Delete Logical SwitchPass
NVP-106 Delete Logical Port Pass
   L3 Functions
NVP-201 Create Logical RouterPass
NVP-202 Create Source Nat rule  Pass
NVP-203 Create Static Nat rulePass
NVP-204 Create Port FW rule   Pass
NVP-205 Check Source Nat rule  Pass
NVP-206 Check Static Nat rule Pass
NVP-207 Check Port FW rule   Pass
NVP-208 Delete Source Nat rule  Pass
NVP-209 Delete Static Nat rule Fail
NVP-210 Delete Port FW rule   Pass
NVP-211 Delete Logical RouterPass

The tests where partly done aith scripts but these are not yet complete and the 
remainder of functionality was done by hand.
For the failed test, NVP-209 a ticket was created, 'CLOUDSTACK-2092'. The 
problem in this case was that deleting the static rule did not result in the 
deletion of the ip adres from the logical router.

Kind regards,
Daan Hoogland


Re: [ASFCS42] Proposed schedule for our next release

2013-04-19 Thread Chip Childers
On Fri, Apr 19, 2013 at 08:40:48AM -0700, Min Chen wrote:
> I like this idea too, this will be a much better channel for community to
> understand features to be planned. +1 to this.
> 
> -min
> 
> On 4/19/13 7:02 AM, "Prasanna Santhanam"  wrote:
> 
> >On Fri, Apr 19, 2013 at 10:16:35AM +, Murali Reddy wrote:
> >> 
> >> Pardon my ignorance of project management, but it appears to me we are
> >> talking of managing a release after half way through the cycle. May be
> >> this is orthogonal discussion, but how about taking approach of
> >>planning a
> >> release early in the cycle (at least for future releases)? Having a time
> >> window between each release where we actually plan for the next release.
> >> Discussions include - direction of the project, what big features are to
> >> be included, rough estimate of the effort, risks and timelines would
> >>help
> >> in planning releases better? Perhaps we should use Collab conferences
> >>for
> >> this purpose, where we can plan for the next release (apart from show
> >> casing the features of previous release). Since Collab is also scheduled
> >> to happen on a half-yearly timeline it makes this easier to execute
> >> release management starting from there.
> >
> >I actually like the idea of 'collab conference' to do release
> >planning! So +1 to that.
> >
> >-- 
> >Prasanna.,
> 
>

I get the desire to do planning via an in-person meeting, but it's not
going to fly.  Here's the reason:  it's exclusionary.

We are an Apache project, and that means that the list is the place for
planning and decisions.

Now, that doesn't mean that we can't all have talk proposals to discuss
a feature we'd like to see at an event.  On the contrary, that's a great
talk topic.

I'll circle back to Murali's initial email to discuss some of the finer 
points of his post shortly.


Re: [SCREENCAST] 4.0.2 testing procedure

2013-04-19 Thread Chip Childers
On Fri, Apr 19, 2013 at 11:53:14AM -0400, Sebastien Goasguen wrote:
> Hi,
> 
> I just uploaded an HD screencast that shows me testing the 4.0.2 release:
> http://www.youtube.com/watch?v=vvgIkF1e1QE&list=PLb899uhkHRoZCRE00h_9CRgUSiHEgFDbC&index=1
> 
> Check it out and do it yourself, then vote !!!
> 
> -Sebastien

Nice work!


Re: [ASFCS42] Proposed schedule for our next release

2013-04-19 Thread David Nalley
So while I will agree that in person communication is faster, and has
higher throughput, it's not without problems for decision making for
this community.

First it dramatically raises the barrier to participation. This is
supposed to be a meritocracy. But shifting decisions, especially
important decisions like release planning to an on-premise venue
destroys that. It entails extensive travel for many if not most. In
addition to the travel cost, for people whose $dayjob isn't 100% on
CloudStack they'd miss several days of works, and then we can assume
it's probably several hundred dollars a night for a hotel. This is not
a cheap proposition, and we shouldn't presume that everyone wants to
or can afford to attend an event. Keep in mind that the last event had
around 1/3 of committers absent, and probably 1/3 or more of our
current PMC was absent as well. We are not going to disenfranchise
them.

There is a reason that this conference doesn't bear a name like the
CloudStack Design Conference, or CloudStack Leadership Summit.

Off-list decisions are a threat to the health of this community.

While I am not speaking for the PMC, I suspect that we'd sooner revoke
permission for the conference to be held than to permit it to
degenerate into a conference where those who can schedule, travel, and
afford to participate get to make decisions about the project.

--David

On Fri, Apr 19, 2013 at 11:40 AM, Min Chen  wrote:
> I like this idea too, this will be a much better channel for community to
> understand features to be planned. +1 to this.
>
> -min
>
> On 4/19/13 7:02 AM, "Prasanna Santhanam"  wrote:
>
>>On Fri, Apr 19, 2013 at 10:16:35AM +, Murali Reddy wrote:
>>>
>>> Pardon my ignorance of project management, but it appears to me we are
>>> talking of managing a release after half way through the cycle. May be
>>> this is orthogonal discussion, but how about taking approach of
>>>planning a
>>> release early in the cycle (at least for future releases)? Having a time
>>> window between each release where we actually plan for the next release.
>>> Discussions include - direction of the project, what big features are to
>>> be included, rough estimate of the effort, risks and timelines would
>>>help
>>> in planning releases better? Perhaps we should use Collab conferences
>>>for
>>> this purpose, where we can plan for the next release (apart from show
>>> casing the features of previous release). Since Collab is also scheduled
>>> to happen on a half-yearly timeline it makes this easier to execute
>>> release management starting from there.
>>
>>I actually like the idea of 'collab conference' to do release
>>planning! So +1 to that.
>>
>>--
>>Prasanna.,
>


Re: New Committer: Go Chiba

2013-04-19 Thread Chiradeep Vittal
Congrats

On 4/17/13 11:56 PM, "Sebastien Goasguen"  wrote:

>The Project Management Committee (PMC) for Apache CloudStack has asked Go
>Chiba to become a committer and we are pleased to announced that they
>have accepted.
>
>Go has contributed tremendously to the Japanese translations of the
>documentation (runbook, UI and docs).
>Being a committer allows many contributors to contribute more
>autonomously. For developers, it makes it easier to submit changes and
>eliminates the need to have contributions reviewed via the patch
>submission process. Whether contributions are development-related or
>otherwise, it is a recognition of a contributor's participation in the
>project and commitment to the project and the Apache Way.
>Please join me in congratulating Go,
>
>-Sebastien, on behalf of  the Apache CloudStack PMC
>



Re: no tinyLinux template

2013-04-19 Thread Chiradeep Vittal
FWIW, I always revert to the initial snapshot of devcloud2 before
switching contexts.
You should also check
select * from template_host_ref where template_id = 5;

And inside DevCloud2
ls /opt/secondary/template/tmpl/1/5/

And, inside the SSVM
ps -ef | grep java


On 4/18/13 9:54 PM, "Mike Tutkowski"  wrote:

>It's strange...I deleted my entire cloud and re-created it this way:
>
>mvn -pl developer,tools/devcloud -Ddeploydb -P developer
>
>cd tools/devcloud ; python ../marvin/marvin/deployDataCenter.py -i
>devcloud.cfg
>
>but still no tinyLinux template (even though it is in the
>cloud.vm_template
>table).
>
>
>On Thu, Apr 18, 2013 at 10:05 PM, Mike Tutkowski <
>mike.tutkow...@solidfire.com> wrote:
>
>> Here is what I used to deploy the DB:
>>
>> mvn -pl developer,tools/devcloud -Ddeploydb -P developer
>>
>> Also, cloud.vm_template has this row:
>>
>> '5', 'tiny Linux', 'tiny Linux', '2a182234-a87b-11e2-84ee-e322fe93e6c9',
>> '1', '1', 'BUILTIN', '0', '64', '
>> http://people.apache.org/~bhaisaab/vms/ttylinux_pv.vhd', 'VHD',
>> '2013-04-18 16:56:11', NULL, '1', '046e134e642e6d344b34648223ba4bc1',
>>'tiny
>> Linux', '0', '0', '12', '1', '0', '1', '1', 'XenServer', NULL, NULL,
>>'0',
>> NULL, NULL, NULL, NULL, '1'
>>
>>
>>
>> On Thu, Apr 18, 2013 at 9:39 PM, Rohit Yadav 
>>wrote:
>>
>>> On Fri, Apr 19, 2013 at 8:26 AM, Mike Tutkowski <
>>> mike.tutkow...@solidfire.com> wrote:
>>>
>>> > Hi,
>>> >
>>> > I've switched back to 4.2 (from 4.1), cleaned out my database,
>>> re-created
>>> > my DevCloud2 environment and all looks good with the exception that
>>>I do
>>> > not have a tinyLinux template.
>>> >
>>> > My SSVM is up and running.
>>> >
>>> > Any thoughts on what I should do here?
>>> >
>>>
>>> Did you forgot to deploydb with -P tools/devcloud? Looks like db
>>>does
>>> not know about ttylinux; check in cloud.vm_templates etc?
>>>
>>> Cheers.
>>>
>>>
>>> >
>>> > 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
>>> > **
>>> >
>>>
>>
>>
>>
>> --
>> *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: [ASFCS42] Proposed schedule for our next release

2013-04-19 Thread Chip Childers
On Fri, Apr 19, 2013 at 10:16:35AM +, Murali Reddy wrote:
> 
> Pardon my ignorance of project management, but it appears to me we are
> talking of managing a release after half way through the cycle. May be
> this is orthogonal discussion, but how about taking approach of planning a
> release early in the cycle (at least for future releases)? Having a time
> window between each release where we actually plan for the next release.
> Discussions include - direction of the project, what big features are to
> be included, rough estimate of the effort, risks and timelines would help
> in planning releases better? Perhaps we should use Collab conferences for
> this purpose, where we can plan for the next release (apart from show
> casing the features of previous release). Since Collab is also scheduled
> to happen on a half-yearly timeline it makes this easier to execute
> release management starting from there.

I think you're far from ignorant on the topic, and bring up some good
points.

IMO there are 2 models for projects to follow:

1 - feature-based releases
2 - time-based releases

The feature-based approach is one where features are planned and
executed with a target completion date, and is managed much like a
traditional "project" that we are used to in corporate life.  Tasks,
ordering, dependencies, etc...  The release isn't complete until the
features are done, docs are complete, QA is signed off and the marketing
stuff is ready to go out.  Certainly there are target dates, but the
priority is on the feature list of "must have" changes getting done.
Everything in the planning and execution process focuses on those
features as the overall goal of the team.  Things will be pulled, and
changes to the plan / schedule will be made, all in the service of
getting as close to the planned feature set as possible.

The time-based approach (currently the one that I thought we were trying
to follow) is very different.  It decouples feature development (and any
associated planning around task ordering, testing, etc...) from the
act of releasing code.  In doing this, it *should* allow anyone to start
the mechanics of releasing code at almost any point in time.  For us,
this includes a QA cycle, doc and translation work, marketing, etc...
Those tasks take time to get done, and they represent the cost of the
release itself.

I'm an advocate of continuing to get better at time-based releases.  To
get better, I feel that we need to focus on improving the quality and
completeness of what makes it into master.  This means that a feature
development effort will have more work to get done before it's allowed
to merge into the (hopefully) stable and well regression tested master
branch.  It also means that some of the more traditional project
management tasks are going to be happening as part of feature
development, and not part of the release process.

The time-based model, IMO, should work much better for a volunteer
community like this.  If someone goes on vacation or has $dayjob
responsibilities that take their time away from ACS, that only impacts
their feature(s), not the release itself. This is a generalization,
because certainly there could be 2 features that rely on each other, and
we rely on QA, docs, translators, marketing folks, as well as an RM to
actually perform the release...  but I think you should be able to
follow the point there.

As I've said on other topics, there's a natural inclination to want to
apply solutions to planning / execution / whatnot that work well in a
corporate environment to OSS projects.  I have that inclination as well
sometimes.  However, we need to make specific decisions that get us in a
position where community growth and changes in composition are unrelated
to our release cadence and processes.

A bit long winded, sorry, but I think the difference in philosophies
are important to understand.

Happy to debate any of this though.

-chip


RE: Review Request: Storage motion changes for xenserver

2013-04-19 Thread Edison Su
Sorry, I don't realize you are not a committer yet. BTW, let me nominate you as 
a commiter.

> -Original Message-
> From: Devdeep Singh [mailto:devdeep.si...@citrix.com]
> Sent: Thursday, April 18, 2013 2:44 AM
> To: Edison Su; Anthony Xu; Abhinandan Prateek (aprat...@apache.org);
> Alex Huang; dev@cloudstack.apache.org
> Subject: RE: Review Request: Storage motion changes for xenserver
> 
> Hi,
> 
> The feature was given a “Ship It” after the review comments were addressed.
> Can someone apply and commit these changes to the master branch. I have
> verified that the patch applies cleanly to the latest master.
> 
> Regards,
> Devdeep
> 
> From: edison su [mailto:nore...@reviews.apache.org] On Behalf Of edison
> su
> Sent: Wednesday, April 17, 2013 11:53 AM
> To: Anthony Xu; Edison Su; Abhinandan Prateek; Alex Huang
> Cc: cloudstack; Devdeep Singh
> Subject: Re: Review Request: Storage motion changes for xenserver
> 
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10196/
> 
> 
> 
> Ship it!
> 
> Ship It!
> 
> 
> - edison
> 
> 
> On April 15th, 2013, 7:24 a.m., Devdeep Singh wrote:
> Review request for cloudstack, Abhinandan Prateek, edison su, Alex Huang,
> and anthony xu.
> By Devdeep Singh.
> 
> Updated April 15, 2013, 7:24 a.m.
> 
> Description
> 
> Storage motion for Xenserver. FS for the feature
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storag
> e+XenMotion+for+XenServer
> 
> 1. Implemented Api findStoragePoolsForMigration. Added a new response
> objects to list storage pools available for migration.
> 
> 2. Updated migrateVolume api for allowing migrating volumes of running
> vms. These changes are integrated into the latest storage refactoring
> changes.
> 
> 3. Added the implementation for findHostsForMigration api. It lists the
> hosts to which an instance can be migrated, including hosts from within and
> across clusters to which an instance may be migrated with storage motion.
> The work of migrating a volume of a running vm is also done in copyAsync.
> 
> 4. Updated the listHosts api for backward compatibility.
> 
> 5. Added the implementation for migrateVirtualMachineWithVolume api. It
> migrates an instance with its volumes within a cluster and also across 
> clusters.
> Also introduced a new XenServerStorageMotionStrategy for migrating
> volumes of a vm. When a vm is being migrated with its volumes, the vm is
> put in migrating state and a request is send to the volume manager to
> migrate the vm and its volumes. Volume manager calls into the volume
> service which forwards the request to data motion service after moving all
> the volumes to migrating state. Data motion service enumerates the
> strategies and the request reaches the XenServerStorageMotionStrategy. It
> calls in to the resource to complete the operation.
> 
> 6. Resolved an issue where storage xenmotion of 2nd VM created from the
> same template to a host was failing with duplicate_vm exception. Made
> changes to remove the mac_seed key value pair from other_config when
> vms are created. This is was storage motion to fail.
> 
> 7. Updated the db upgrade schema script.
> 
> 8. Added the right permissions in commands.properties
> 
> 9. Marvin tests for testing storage motion. Following scenarios are 
> tested.
> 
> 9.1. A virtual machine is migrated to another host. Its volumes are also
> migrated to another storage pool.
> 
> 9.2. Just the volumes of a vm are migrated to another storage pool while
> the vm continues to run on the same host.
> 
> 10. Unit tests for testing migration of a vm with its volumes.
> 
> 
> Testing
> 
> 1. Unit tests for testing vm migration with volume. They test when a vm is
> migrated within a cluster or across cluster. Also added negative tests for the
> scenrios.
> 
> 2. Marvin tests to do functional testing. Including tests to varify vm 
> migration
> with volume across cluster.
> 
> 3. Marvin test for volume migration to another storage pool in the cluster
> while the vm continues to run on the same host.
> 
> 4. Also did additional manual testing for the following scenarios:
> 
> 4.1 VM migration with volumes within and across cluster.
> 
> 4.2 Tested both the scenarios when 'migrateto' optional parameter is passed
> to the migrate vm with volume api. When it isn't passed, cloudstack picks up
> a storage pool for migration. When it is passed, the volume is migrated to the
> pool passed in the parameter.
> 
> 4.3 Tested that storage tags are honored when a vm is migrated with its
> volumes.
> 
> 4.4 Tested volume migration when the vm stays on the same host.
> 
> 4.5 For volume migration verified that storage tags are honored.
> 
> 
> 
> Other tests done to verify patch:
> 
> 1. Verified that there are no rat failures.
> 
> 2. Applied the patch to verify it applies cleanly.
> 
> Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-659
> Diffs
> 
>   *   api/src/com/clou

Re: ebtables

2013-04-19 Thread Maurice Lawler
Anyone know how to correct my mistake?

- Maurice


On Apr 19, 2013, at 2:01 AM, Maurice Lawler  wrote:

> Perhaps this was not the best thing, now my ports are open; how can I revert 
> back to eatables. 
> 
> Along with that, when reverted, how can I drop rules for a particular VM to 
> allow communication via second IP address. 
> 
> 
> On Apr 18, 2013, at 10:34 PM, Maurice Lawler  wrote:
> 
>> Disregard, for now, I have disabled/removed ebtables as shown here:
>> 
>> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-users/201302.mbox/%3cb1df26ecc0458748ac97cece2da98d41012fa47b6...@sjcpmailbox01.citrite.net%3E
>> 
>> 
>> On Apr 18, 2013, at 11:28 PM, Maurice Lawler  wrote:
>> 
>>> Hello --
>>> 
>>> Previously one told me how to do this, but I cannot find my notes on this, 
>>> so I hope you can help me out.
>>> 
>>> I am attempting to allow a secondary IP address on an instance by-pass the 
>>> routing rules set forth in ebtables. I recall doing something like 
>>> 
>>> ebtables nat i-2-25-VM something ... I cannot for the life of me remember.
>>> 
>>> How to list and/or drop the rules per VM.
>>> 
>>> Can you guys assist?
> 



Re: what are the technical reason for not supporting security groups on ovs?

2013-04-19 Thread Chiradeep Vittal
Security groups are stateful firewalls -- currently it is not possible to
do stateful firewalling inside OVS (you could write a controller or buy
one that does it however). KVM (linux v 3.2 onwards) now has the ability
to chain OVS and bridge so technically it should be possible only on those
hypervisors.

On 4/19/13 3:45 AM, "Venkata SwamyBabu Budumuru"
 wrote:

>By mistake, hit the send button before writing the actual message
>
>
>Looks like cloudstack + Xen only supports SecurityGroups with bridge as
>backend. Can someone shed some light on the technical reasons behind we
>we don't support it on OVS?
>
>Thanks,
>SWAMY
>
>-Original Message-
>From: Venkata SwamyBabu Budumuru
>[mailto:venkataswamybabu.budum...@citrix.com]
>Sent: Friday, 19 April 2013 3:56 PM
>To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
>Subject: what are the technical reason for not supporting security groups
>on ovs?
>
>Thanks,
>SWAMY



RE: [MERGE] Mixed zone management

2013-04-19 Thread Brian Federle
Mixed zone management functionality is now ready and merged to master.

Thanks!

Brian

-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
Sent: Wednesday, April 17, 2013 1:58 PM
To: Chip Childers
Cc: dev@cloudstack.apache.org; Sonny Chhen; Jessica Wang; Pranav Saxena
Subject: RE: [MERGE] Mixed zone management



> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Wednesday, April 17, 2013 1:50 PM
> To: Animesh Chaturvedi
> Cc: dev@cloudstack.apache.org; Sonny Chhen; Jessica Wang; Pranav 
> Saxena
> Subject: Re: [MERGE] Mixed zone management
> 
> On Wed, Apr 17, 2013 at 01:43:58PM -0700, Animesh Chaturvedi wrote:
> > So to be clear for future UI merges does the following makes sense
> > * For pure UI features we need a separate proposal email
> > * If UI is part of a specific feature, the functional spec should 
> > call out the UI
> changes and UI merge request should reference the original feature proposal.
> 
> Sounds right to me.  The key point here is that we make decisions 
> about changes on the list, and feature proposals, regardless of where 
> they are in the code, are critical decisions.
> 
> I'd suggest that any new UI feature or design change deserves an 
> actual discussion on this list...  so if it's covered in the main feature 
> discussion, great.
> But I don't want us to assume that if a feature at the API layer down 
> is discussed, that it means that UI changes aren't just as important 
> for everyone to understand and have an opportunity to weigh in on.
[Animesh>] Yes agreed, no doubt on that


Re: ebtables

2013-04-19 Thread Marcus Sorensen
you can go back and disable security groups in the zone if you don't care
about the ebtables rules, or you can start up ebtables and then restart any
associated VMs through cloudstack. The rules are dynamic, so they're not
going to be saved anywhere on the host to be reinstated, they have to be
reapplied by cloudstack via a restart of the vms.


On Fri, Apr 19, 2013 at 11:12 AM, Maurice Lawler wrote:

> Anyone know how to correct my mistake?
>
> - Maurice
>
>
> On Apr 19, 2013, at 2:01 AM, Maurice Lawler  wrote:
>
> > Perhaps this was not the best thing, now my ports are open; how can I
> revert back to eatables.
> >
> > Along with that, when reverted, how can I drop rules for a particular VM
> to allow communication via second IP address.
> >
> >
> > On Apr 18, 2013, at 10:34 PM, Maurice Lawler 
> wrote:
> >
> >> Disregard, for now, I have disabled/removed ebtables as shown here:
> >>
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-users/201302.mbox/%3cb1df26ecc0458748ac97cece2da98d41012fa47b6...@sjcpmailbox01.citrite.net%3E
> >>
> >>
> >> On Apr 18, 2013, at 11:28 PM, Maurice Lawler 
> wrote:
> >>
> >>> Hello --
> >>>
> >>> Previously one told me how to do this, but I cannot find my notes on
> this, so I hope you can help me out.
> >>>
> >>> I am attempting to allow a secondary IP address on an instance by-pass
> the routing rules set forth in ebtables. I recall doing something like
> >>>
> >>> ebtables nat i-2-25-VM something ... I cannot for the life of me
> remember.
> >>>
> >>> How to list and/or drop the rules per VM.
> >>>
> >>> Can you guys assist?
> >
>
>


RE: no tinyLinux template

2013-04-19 Thread Edison Su
The default ttylinux template does not pre-installed in latest devcloud2 
virtualbox image, and the system vm can't access public network, thus, can't 
download tty template.
Either it should be fixed by Rohit and upload an new image to his devcloud2 
link(http://people.apache.org/~bhaisaab/cloudstack/devcloud/devcloud2.ova), or 
provides a way to generate devcloud virtualbox image automatically in Jenkins.

> -Original Message-
> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
> Sent: Friday, April 19, 2013 9:51 AM
> To: dev@cloudstack.apache.org
> Subject: Re: no tinyLinux template
> 
> FWIW, I always revert to the initial snapshot of devcloud2 before switching
> contexts.
> You should also check
> select * from template_host_ref where template_id = 5;
> 
> And inside DevCloud2
> ls /opt/secondary/template/tmpl/1/5/
> 
> And, inside the SSVM
> ps -ef | grep java
> 
> 
> On 4/18/13 9:54 PM, "Mike Tutkowski" 
> wrote:
> 
> >It's strange...I deleted my entire cloud and re-created it this way:
> >
> >mvn -pl developer,tools/devcloud -Ddeploydb -P developer
> >
> >cd tools/devcloud ; python ../marvin/marvin/deployDataCenter.py -i
> >devcloud.cfg
> >
> >but still no tinyLinux template (even though it is in the
> >cloud.vm_template table).
> >
> >
> >On Thu, Apr 18, 2013 at 10:05 PM, Mike Tutkowski <
> >mike.tutkow...@solidfire.com> wrote:
> >
> >> Here is what I used to deploy the DB:
> >>
> >> mvn -pl developer,tools/devcloud -Ddeploydb -P developer
> >>
> >> Also, cloud.vm_template has this row:
> >>
> >> '5', 'tiny Linux', 'tiny Linux',
> >>'2a182234-a87b-11e2-84ee-e322fe93e6c9',
> >> '1', '1', 'BUILTIN', '0', '64', '
> >> http://people.apache.org/~bhaisaab/vms/ttylinux_pv.vhd', 'VHD',
> >> '2013-04-18 16:56:11', NULL, '1', '046e134e642e6d344b34648223ba4bc1',
> >>'tiny
> >> Linux', '0', '0', '12', '1', '0', '1', '1', 'XenServer', NULL, NULL,
> >>'0',  NULL, NULL, NULL, NULL, '1'
> >>
> >>
> >>
> >> On Thu, Apr 18, 2013 at 9:39 PM, Rohit Yadav 
> >>wrote:
> >>
> >>> On Fri, Apr 19, 2013 at 8:26 AM, Mike Tutkowski <
> >>> mike.tutkow...@solidfire.com> wrote:
> >>>
> >>> > Hi,
> >>> >
> >>> > I've switched back to 4.2 (from 4.1), cleaned out my database,
> >>> re-created
> >>> > my DevCloud2 environment and all looks good with the exception
> >>> > that
> >>>I do
> >>> > not have a tinyLinux template.
> >>> >
> >>> > My SSVM is up and running.
> >>> >
> >>> > Any thoughts on what I should do here?
> >>> >
> >>>
> >>> Did you forgot to deploydb with -P tools/devcloud? Looks like db
> >>>does  not know about ttylinux; check in cloud.vm_templates etc?
> >>>
> >>> Cheers.
> >>>
> >>>
> >>> >
> >>> > 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
> >>> > **
> >>> >
> >>>
> >>
> >>
> >>
> >> --
> >> *Mike Tutkowski*
> >> *Senior CloudStack Developer, SolidFire Inc.*
> >> e: mike.tutkow...@solidfire.com
> >> o: 303.746.7302
> >> Advancing the way the world uses the
> >>cloud
> >> **
> >>
> >
> >
> >
> >--
> >*Mike Tutkowski*
> >*Senior CloudStack Developer, SolidFire Inc.*
> >e: mike.tutkow...@solidfire.com
> >o: 303.746.7302
> >Advancing the way the world uses the
> >cloud
> >**



Re: Review Request: CLOUDSTACK-2053: Fix bash if/else logic to avoid redundant entries in htaccess file, fixed boto/cloud-init support by adding metadata RewriteRules

2013-04-19 Thread ilya musayev


> On April 18, 2013, 11:36 p.m., Chiradeep Vittal wrote:
> > Is the fundamental problem that the data is available under 
> > /latest/metadata instead of /latest/meta-data ?
> >

cloud-init (as of 0.7.2) uses the uripath '/latest/meta-data' (meta-data is the 
default in the boto APIs and the cloud-init code currently does not try to 
override it.) when it issues a GET. 

metadataentry1='RewriteRule ^meta-data/$ ../metadata/%{REMOTE_ADDR}/meta-data 
[L,NC,QSA]'
This rule gets the list of metadata attributes, as meta-data contains a list of 
metadata attributes like. local-ipv4, public-hostname, etc..

Once it gets the list it needs to know which attribute it's pulling data from 
thus the rule below:
metadataentry2='RewriteRule ^meta-data/(.*)$ ../metadata/%{REMOTE_ADDR}/$1 
[L,NC,QSA]'
will pull the actually data from the given metadata attribute (i.e. 
'/latest/meta-data/local-ipv4', '/latest/meta-data/public-hostname', etc.)

We're probably not as familiar with apache rewrite rules and if just having 
metadataentry1 is all that's needed to accomplish the above then by all means 
lets simplify it.


- ilya


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


On April 18, 2013, 11:02 p.m., ilya musayev wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10614/
> ---
> 
> (Updated April 18, 2013, 11:02 p.m.)
> 
> 
> Review request for cloudstack and Chiradeep Vittal.
> 
> 
> Description
> ---
> 
> Addressed 2 issues:
> Rewrote the bash if/else check to fix redundant entries
> Added RewriteRules to support boto/cloud-init - as per Chiradeep - this would 
> only affect VMWare deployments, as this userdata.sh script is only used with 
> vmware system router vms
> 
> 
> This addresses bug CLOUDSTACK-2053.
> 
> 
> Diffs
> -
> 
>   patches/systemvm/debian/config/root/userdata.sh e5d170b 
> 
> Diff: https://reviews.apache.org/r/10614/diff/
> 
> 
> Testing
> ---
> 
> ACS4.1
> 
> 
> Thanks,
> 
> ilya musayev
> 
>



RE: IP tables blocking KVM/Console

2013-04-19 Thread Edison Su


> -Original Message-
> From: Jason Pavao [mailto:jason.pa...@oracle.com]
> Sent: Thursday, April 18, 2013 8:50 AM
> To: dev@cloudstack.apache.org
> Cc: Maurice Lawler; us...@cloudstack.apache.org
> Subject: Re: IP tables blocking KVM/Console
> 
> Maurice,
> I was having the same issues, I tried a number of iptables rule changes, but 
> it
> seems that whenever a new instance was deployed it would overwrite my
> changes and break things again. My temporary fix is to run a cron job that
> runs every minute that issues a service iptables stop.

Do you disable security group when creating the zone? If security group is 
disabled, then there should be no iptables rules created on kvm host when a new 
instance created.

> 
> It's not elegant but it works since I don't have a need for security groups 
> and
> am supporting a jenkins continuous testing environment with no need for
> network ingress/egress rules.
> 
> Does anyone else know why this is happening?
> 
> I am running cs 4.0.1 on oel6.3x64
> 
> Any help would be appreciated.
> Thanks.
> -jason
> 
> On 4/17/2013 7:47 PM, Maurice Lawler wrote:
> > I have stopped iptables at least 15 times, because it keeps blocking
> > my console access to my instances. How can I either A) disable
> > Iptables all together / b add a rule to allow it's access.
> >
> > Right now, it has this:
> >
> > [root@lunder ~]# iptables -L
> > Chain INPUT (policy ACCEPT)
> > target prot opt source   destination
> > ACCEPT udp  --  anywhere anywhereudp
> > dpt:bootps
> > ACCEPT tcp  --  anywhere anywheretcp
> > dpt:bootps
> > ACCEPT tcp  --  anywhere anywheretcp
> > dpts:49152:49216
> > ACCEPT tcp  --  anywhere anywheretcp
> > dpts:vnc-server:synchronet-db
> > ACCEPT tcp  --  anywhere anywheretcp
> > dpt:16509
> > ACCEPT tcp  --  anywhere anywheretcp
> > dpt:websm
> > ACCEPT tcp  --  anywhere anywheretcp dpt:8250
> > ACCEPT tcp  --  anywhere anywheretcp
> > dpt:empowerid
> > ACCEPT tcp  --  anywhere anywheretcp
> > dpt:webcache
> > ACCEPT all  --  anywhere anywhere state
> > RELATED,ESTABLISHED
> > ACCEPT icmp --  anywhere anywhere
> > ACCEPT all  --  anywhere anywhere
> > ACCEPT tcp  --  anywhere anywhere state NEW tcp dpt:ssh
> > REJECT all  --  anywhere anywhere reject-with
> > icmp-host-prohibited
> >
> > Chain FORWARD (policy ACCEPT)
> > target prot opt source   destination
> >
> > Chain OUTPUT (policy ACCEPT)
> > target prot opt source   destination
> > [root@lunder ~]#
> >
> > But there was plenty of other rules previously to my stopping it.
> >
> >
> 
> --
> Thanks.
> -Jason



Re: Review Request: CLOUDSTACK-2053: Fix bash if/else logic to avoid redundant entries in htaccess file, fixed boto/cloud-init support by adding metadata RewriteRules

2013-04-19 Thread ilya musayev


> On April 18, 2013, 11:36 p.m., Chiradeep Vittal wrote:
> > patches/systemvm/debian/config/root/userdata.sh, line 79
> > 
> >
> > why is this needed? shouldn't the first rewrite rule be sufficient?
> >

See comments above.


- ilya


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


On April 18, 2013, 11:02 p.m., ilya musayev wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10614/
> ---
> 
> (Updated April 18, 2013, 11:02 p.m.)
> 
> 
> Review request for cloudstack and Chiradeep Vittal.
> 
> 
> Description
> ---
> 
> Addressed 2 issues:
> Rewrote the bash if/else check to fix redundant entries
> Added RewriteRules to support boto/cloud-init - as per Chiradeep - this would 
> only affect VMWare deployments, as this userdata.sh script is only used with 
> vmware system router vms
> 
> 
> This addresses bug CLOUDSTACK-2053.
> 
> 
> Diffs
> -
> 
>   patches/systemvm/debian/config/root/userdata.sh e5d170b 
> 
> Diff: https://reviews.apache.org/r/10614/diff/
> 
> 
> Testing
> ---
> 
> ACS4.1
> 
> 
> Thanks,
> 
> ilya musayev
> 
>



RE: IP tables blocking KVM/Console

2013-04-19 Thread Edison Su
This rule will reject all the ingress activities: "REJECT all  --  anywhere 
anywherereject-with icmp-host-prohibited"
You can try:
iptables -I INPUT -p tcp -m tcp --dport 5900:6100 -j ACCEPT
to allow console access.

From: Maurice Lawler [mailto:maurice.law...@me.com]
Sent: Wednesday, April 17, 2013 7:48 PM
To: Cloud Dev
Cc: us...@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: IP tables blocking KVM/Console

I have stopped iptables at least 15 times, because it keeps blocking my console 
access to my instances. How can I either A) disable Iptables all together / b 
add a rule to allow it's access.

Right now, it has this:

[root@lunder ~]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source   destination
ACCEPT udp  --  anywhere anywhereudp dpt:bootps
ACCEPT tcp  --  anywhere anywheretcp dpt:bootps
ACCEPT tcp  --  anywhere anywheretcp 
dpts:49152:49216
ACCEPT tcp  --  anywhere anywheretcp 
dpts:vnc-server:synchronet-db
ACCEPT tcp  --  anywhere anywheretcp dpt:16509
ACCEPT tcp  --  anywhere anywheretcp dpt:websm
ACCEPT tcp  --  anywhere anywheretcp dpt:8250
ACCEPT tcp  --  anywhere anywheretcp dpt:empowerid
ACCEPT tcp  --  anywhere anywheretcp dpt:webcache
ACCEPT all  --  anywhere anywherestate 
RELATED,ESTABLISHED
ACCEPT icmp --  anywhere anywhere
ACCEPT all  --  anywhere anywhere
ACCEPT tcp  --  anywhere anywherestate NEW tcp 
dpt:ssh
REJECT all  --  anywhere anywherereject-with 
icmp-host-prohibited

Chain FORWARD (policy ACCEPT)
target prot opt source   destination

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination
[root@lunder ~]#

But there was plenty of other rules previously to my stopping it.




Re: IP tables blocking KVM/Console

2013-04-19 Thread Marcus Sorensen
That's reflected by this line:

ACCEPT tcp  --  anywhere anywheretcp
dpts:vnc-server:synchronet-db

Although we don't know what interfaces it applies to because we don't have
an 'iptables -L -v'

If stopping iptables fixes Maurice's problem it would be interesting to
know, as the rules seem to let VNC through. It should be easy to tcpdump
and see what traffic is actually being blocked because his rules suggest
that VNC is wide open on the KVM host.


On Fri, Apr 19, 2013 at 12:15 PM, Edison Su  wrote:

> This rule will reject all the ingress activities: "REJECT all  --
>  anywhere anywherereject-with icmp-host-prohibited"
> You can try:
> iptables -I INPUT -p tcp -m tcp --dport 5900:6100 -j ACCEPT
> to allow console access.
>
> From: Maurice Lawler [mailto:maurice.law...@me.com]
> Sent: Wednesday, April 17, 2013 7:48 PM
> To: Cloud Dev
> Cc: us...@cloudstack.apache.org; us...@cloudstack.apache.org
> Subject: IP tables blocking KVM/Console
>
> I have stopped iptables at least 15 times, because it keeps blocking my
> console access to my instances. How can I either A) disable Iptables all
> together / b add a rule to allow it's access.
>
> Right now, it has this:
>
> [root@lunder ~]# iptables -L
> Chain INPUT (policy ACCEPT)
> target prot opt source   destination
> ACCEPT udp  --  anywhere anywhereudp dpt:bootps
> ACCEPT tcp  --  anywhere anywheretcp dpt:bootps
> ACCEPT tcp  --  anywhere anywheretcp
> dpts:49152:49216
> ACCEPT tcp  --  anywhere anywheretcp
> dpts:vnc-server:synchronet-db
> ACCEPT tcp  --  anywhere anywheretcp dpt:16509
> ACCEPT tcp  --  anywhere anywheretcp dpt:websm
> ACCEPT tcp  --  anywhere anywheretcp dpt:8250
> ACCEPT tcp  --  anywhere anywheretcp
> dpt:empowerid
> ACCEPT tcp  --  anywhere anywheretcp
> dpt:webcache
> ACCEPT all  --  anywhere anywherestate
> RELATED,ESTABLISHED
> ACCEPT icmp --  anywhere anywhere
> ACCEPT all  --  anywhere anywhere
> ACCEPT tcp  --  anywhere anywherestate NEW tcp
> dpt:ssh
> REJECT all  --  anywhere anywherereject-with
> icmp-host-prohibited
>
> Chain FORWARD (policy ACCEPT)
> target prot opt source   destination
>
> Chain OUTPUT (policy ACCEPT)
> target prot opt source   destination
> [root@lunder ~]#
>
> But there was plenty of other rules previously to my stopping it.
>
>
>


Re: no tinyLinux template

2013-04-19 Thread Mike Tutkowski
Yeah, I generally revert to the DevCloud2 initial state whenever I create a
new CS database...just to be on the safe side.

I see this folder:

/opt/storage/secondary/template/tmpl/1/5/ (the path is a little different
from yours)

It has a VHD file in it.

I looked at devcloud.cfg in the hopes that the secondary storage URL was
different, but it shows the following:

"secondaryStorages": [
{
"url": "nfs://192.168.56.10:/opt/storage/secondary"
}


On Fri, Apr 19, 2013 at 10:51 AM, Chiradeep Vittal <
chiradeep.vit...@citrix.com> wrote:

> FWIW, I always revert to the initial snapshot of devcloud2 before
> switching contexts.
> You should also check
> select * from template_host_ref where template_id = 5;
>
> And inside DevCloud2
> ls /opt/secondary/template/tmpl/1/5/
>
> And, inside the SSVM
> ps -ef | grep java
>
>
> On 4/18/13 9:54 PM, "Mike Tutkowski"  wrote:
>
> >It's strange...I deleted my entire cloud and re-created it this way:
> >
> >mvn -pl developer,tools/devcloud -Ddeploydb -P developer
> >
> >cd tools/devcloud ; python ../marvin/marvin/deployDataCenter.py -i
> >devcloud.cfg
> >
> >but still no tinyLinux template (even though it is in the
> >cloud.vm_template
> >table).
> >
> >
> >On Thu, Apr 18, 2013 at 10:05 PM, Mike Tutkowski <
> >mike.tutkow...@solidfire.com> wrote:
> >
> >> Here is what I used to deploy the DB:
> >>
> >> mvn -pl developer,tools/devcloud -Ddeploydb -P developer
> >>
> >> Also, cloud.vm_template has this row:
> >>
> >> '5', 'tiny Linux', 'tiny Linux', '2a182234-a87b-11e2-84ee-e322fe93e6c9',
> >> '1', '1', 'BUILTIN', '0', '64', '
> >> http://people.apache.org/~bhaisaab/vms/ttylinux_pv.vhd', 'VHD',
> >> '2013-04-18 16:56:11', NULL, '1', '046e134e642e6d344b34648223ba4bc1',
> >>'tiny
> >> Linux', '0', '0', '12', '1', '0', '1', '1', 'XenServer', NULL, NULL,
> >>'0',
> >> NULL, NULL, NULL, NULL, '1'
> >>
> >>
> >>
> >> On Thu, Apr 18, 2013 at 9:39 PM, Rohit Yadav 
> >>wrote:
> >>
> >>> On Fri, Apr 19, 2013 at 8:26 AM, Mike Tutkowski <
> >>> mike.tutkow...@solidfire.com> wrote:
> >>>
> >>> > Hi,
> >>> >
> >>> > I've switched back to 4.2 (from 4.1), cleaned out my database,
> >>> re-created
> >>> > my DevCloud2 environment and all looks good with the exception that
> >>>I do
> >>> > not have a tinyLinux template.
> >>> >
> >>> > My SSVM is up and running.
> >>> >
> >>> > Any thoughts on what I should do here?
> >>> >
> >>>
> >>> Did you forgot to deploydb with -P tools/devcloud? Looks like db
> >>>does
> >>> not know about ttylinux; check in cloud.vm_templates etc?
> >>>
> >>> Cheers.
> >>>
> >>>
> >>> >
> >>> > 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
> >>> > * *
> >>> >
> >>>
> >>
> >>
> >>
> >> --
> >> *Mike Tutkowski*
> >> *Senior CloudStack Developer, SolidFire Inc.*
> >> e: mike.tutkow...@solidfire.com
> >> o: 303.746.7302
> >> Advancing the way the world uses the
> >>cloud
> >> * *
> >>
> >
> >
> >
> >--
> >*Mike Tutkowski*
> >*Senior CloudStack Developer, SolidFire Inc.*
> >e: mike.tutkow...@solidfire.com
> >o: 303.746.7302
> >Advancing the way the world uses the
> >cloud
> >* *
>
>


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


KVM host ( CentOS 6.3 ) can't back from down

2013-04-19 Thread Serg Senko
Hi

Cloudstack v. 4.0.1
KVM host :
CentOS 6.3
libvirt 1.0.1
qemu 1.2.0

After power loss server can't back online ( UP) still in status "Down" with
following error in

 agent log  :

2013-04-19 22:12:35,932 DEBUG [kvm.resource.LibvirtComputingResource]
(Agent-Handler-1:null) Executing:
/usr/lib64/cloud/common/scripts/vm/hypervisor/versions.sh
2013-04-19 22:12:35,956 DEBUG [kvm.resource.LibvirtComputingResource]
(Agent-Handler-1:null) Execution is successful.
2013-04-19 22:12:35,980 WARN  [utils.nio.Task] (Agent-Handler-1:null)
Caught the following exception but pushing on
java.lang.IllegalArgumentException: No enum const class
com.cloud.hypervisor.kvm.resource.LibvirtStoragePoolDef$poolType.FS
at java.lang.Enum.valueOf(Enum.java:214)
at
com.cloud.hypervisor.kvm.resource.LibvirtStoragePoolDef$poolType.valueOf(LibvirtStoragePoolDef.java:20)
at
com.cloud.hypervisor.kvm.resource.LibvirtStoragePoolXMLParser.parseStoragePoolXML(LibvirtStoragePoolXMLParser.java:78)
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.getStoragePoolDef(LibvirtStorageAdaptor.java:286)
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:467)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:57)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.initialize(LibvirtComputingResource.java:3271)
at com.cloud.agent.Agent.sendStartup(Agent.java:320)
at com.cloud.agent.Agent$ServerHandler.doTask(Agent.java:850)
at com.cloud.utils.nio.Task.run(Task.java:83)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)


management log :

2013-04-19 22:17:39,446 INFO  [agent.manager.AgentManagerImpl]
(AgentManager-Handler-15:null) Connection from /10.0.0.10 closed but no
cleanup was done.

libvirtd log :

2013-04-19 19:18:48.989+: 12783: error : virNetSocketReadWire:1321 :
End of file while reading data: Input/output error


Some one can help to debug such problem ?

Thanks.


-- 
ttyv0 "/usr/libexec/gmail Pc"  webcons on secure


RE: Review Request: CLOUDSTACK-2053: Fix bash if/else logic to avoid redundant entries in htaccess file, fixed boto/cloud-init support by adding metadata RewriteRules

2013-04-19 Thread Musayev, Ilya
I wonder what I'm doing wrong.

I've attempted to submit a second patch to address Chiradeeps comment, use 
Update Diff, placed parent and child diffs, and review board - died yet again.


> -Original Message-
> From: ilya musayev [mailto:nore...@reviews.apache.org] On Behalf Of ilya
> musayev
> Sent: Friday, April 19, 2013 2:10 PM
> To: Chiradeep Vittal
> Cc: ilya musayev; cloudstack
> Subject: Re: Review Request: CLOUDSTACK-2053: Fix bash if/else logic to
> avoid redundant entries in htaccess file, fixed boto/cloud-init support by
> adding metadata RewriteRules
> 
> 
> 
> > On April 18, 2013, 11:36 p.m., Chiradeep Vittal wrote:
> > > patches/systemvm/debian/config/root/userdata.sh, line 79
> > >  > > ne79>
> > >
> > > why is this needed? shouldn't the first rewrite rule be sufficient?
> > >
> 
> See comments above.
> 
> 
> - ilya
> 
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10614/#review19416
> ---
> 
> 
> On April 18, 2013, 11:02 p.m., ilya musayev wrote:
> >
> > ---
> > This is an automatically generated e-mail. To reply, visit:
> > https://reviews.apache.org/r/10614/
> > ---
> >
> > (Updated April 18, 2013, 11:02 p.m.)
> >
> >
> > Review request for cloudstack and Chiradeep Vittal.
> >
> >
> > Description
> > ---
> >
> > Addressed 2 issues:
> > Rewrote the bash if/else check to fix redundant entries Added
> > RewriteRules to support boto/cloud-init - as per Chiradeep - this
> > would only affect VMWare deployments, as this userdata.sh script is
> > only used with vmware system router vms
> >
> >
> > This addresses bug CLOUDSTACK-2053.
> >
> >
> > Diffs
> > -
> >
> >   patches/systemvm/debian/config/root/userdata.sh e5d170b
> >
> > Diff: https://reviews.apache.org/r/10614/diff/
> >
> >
> > Testing
> > ---
> >
> > ACS4.1
> >
> >
> > Thanks,
> >
> > ilya musayev
> >
> >



Re: no tinyLinux template

2013-04-19 Thread Rohit Yadav
On Fri, Apr 19, 2013 at 11:18 PM, Edison Su  wrote:

> The default ttylinux template does not pre-installed in latest devcloud2
> virtualbox image, and the system vm can't access public network, thus,
> can't download tty template.
> Either it should be fixed by Rohit and upload an new image to his
> devcloud2 link(
> http://people.apache.org/~bhaisaab/cloudstack/devcloud/devcloud2.ova), or
> provides a way to generate devcloud virtualbox image automatically in
> Jenkins.
>


/me facepalm

DevCloud2 (from the stated url) contains ttylinux. It's a known issue that
vms cannot reach out to the public network in DevCloud2, so I had already
pre-seeded tiny linux template in /opt/storage/secondary/... (you can
confirm the same). It works for me, it must be some other issue?

Cheers.


>
> > -Original Message-
> > From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
> > Sent: Friday, April 19, 2013 9:51 AM
> > To: dev@cloudstack.apache.org
> > Subject: Re: no tinyLinux template
> >
> > FWIW, I always revert to the initial snapshot of devcloud2 before
> switching
> > contexts.
> > You should also check
> > select * from template_host_ref where template_id = 5;
> >
> > And inside DevCloud2
> > ls /opt/secondary/template/tmpl/1/5/
> >
> > And, inside the SSVM
> > ps -ef | grep java
> >
> >
> > On 4/18/13 9:54 PM, "Mike Tutkowski" 
> > wrote:
> >
> > >It's strange...I deleted my entire cloud and re-created it this way:
> > >
> > >mvn -pl developer,tools/devcloud -Ddeploydb -P developer
> > >
> > >cd tools/devcloud ; python ../marvin/marvin/deployDataCenter.py -i
> > >devcloud.cfg
> > >
> > >but still no tinyLinux template (even though it is in the
> > >cloud.vm_template table).
> > >
> > >
> > >On Thu, Apr 18, 2013 at 10:05 PM, Mike Tutkowski <
> > >mike.tutkow...@solidfire.com> wrote:
> > >
> > >> Here is what I used to deploy the DB:
> > >>
> > >> mvn -pl developer,tools/devcloud -Ddeploydb -P developer
> > >>
> > >> Also, cloud.vm_template has this row:
> > >>
> > >> '5', 'tiny Linux', 'tiny Linux',
> > >>'2a182234-a87b-11e2-84ee-e322fe93e6c9',
> > >> '1', '1', 'BUILTIN', '0', '64', '
> > >> http://people.apache.org/~bhaisaab/vms/ttylinux_pv.vhd', 'VHD',
> > >> '2013-04-18 16:56:11', NULL, '1', '046e134e642e6d344b34648223ba4bc1',
> > >>'tiny
> > >> Linux', '0', '0', '12', '1', '0', '1', '1', 'XenServer', NULL, NULL,
> > >>'0',  NULL, NULL, NULL, NULL, '1'
> > >>
> > >>
> > >>
> > >> On Thu, Apr 18, 2013 at 9:39 PM, Rohit Yadav 
> > >>wrote:
> > >>
> > >>> On Fri, Apr 19, 2013 at 8:26 AM, Mike Tutkowski <
> > >>> mike.tutkow...@solidfire.com> wrote:
> > >>>
> > >>> > Hi,
> > >>> >
> > >>> > I've switched back to 4.2 (from 4.1), cleaned out my database,
> > >>> re-created
> > >>> > my DevCloud2 environment and all looks good with the exception
> > >>> > that
> > >>>I do
> > >>> > not have a tinyLinux template.
> > >>> >
> > >>> > My SSVM is up and running.
> > >>> >
> > >>> > Any thoughts on what I should do here?
> > >>> >
> > >>>
> > >>> Did you forgot to deploydb with -P tools/devcloud? Looks like db
> > >>>does  not know about ttylinux; check in cloud.vm_templates etc?
> > >>>
> > >>> Cheers.
> > >>>
> > >>>
> > >>> >
> > >>> > 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
> > >>> > * *
> > >>> >
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> *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: no tinyLinux template

2013-04-19 Thread Rohit Yadav
On Fri, Apr 19, 2013 at 11:56 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Yeah, I generally revert to the DevCloud2 initial state whenever I create a
> new CS database...just to be on the safe side.
>
> I see this folder:
>
> /opt/storage/secondary/template/tmpl/1/5/ (the path is a little different
> from yours)
>
> It has a VHD file in it.
>

It's tiny linux about 50MB.


>
> I looked at devcloud.cfg in the hopes that the secondary storage URL was
> different, but it shows the following:
>
> "secondaryStorages": [
> {
> "url": "nfs://192.168.56.10:/opt/storage/secondary"
> }
>


This is correct as unless you're doing something else, the default IP of
DevCloud2 appliance is 192.168.56.10 and path to secondary storage is
indeed /opt/storage/secondary

Cheers.


>
>
> On Fri, Apr 19, 2013 at 10:51 AM, Chiradeep Vittal <
> chiradeep.vit...@citrix.com> wrote:
>
> > FWIW, I always revert to the initial snapshot of devcloud2 before
> > switching contexts.
> > You should also check
> > select * from template_host_ref where template_id = 5;
> >
> > And inside DevCloud2
> > ls /opt/secondary/template/tmpl/1/5/
> >
> > And, inside the SSVM
> > ps -ef | grep java
> >
> >
> > On 4/18/13 9:54 PM, "Mike Tutkowski" 
> wrote:
> >
> > >It's strange...I deleted my entire cloud and re-created it this way:
> > >
> > >mvn -pl developer,tools/devcloud -Ddeploydb -P developer
> > >
> > >cd tools/devcloud ; python ../marvin/marvin/deployDataCenter.py -i
> > >devcloud.cfg
> > >
> > >but still no tinyLinux template (even though it is in the
> > >cloud.vm_template
> > >table).
> > >
> > >
> > >On Thu, Apr 18, 2013 at 10:05 PM, Mike Tutkowski <
> > >mike.tutkow...@solidfire.com> wrote:
> > >
> > >> Here is what I used to deploy the DB:
> > >>
> > >> mvn -pl developer,tools/devcloud -Ddeploydb -P developer
> > >>
> > >> Also, cloud.vm_template has this row:
> > >>
> > >> '5', 'tiny Linux', 'tiny Linux',
> '2a182234-a87b-11e2-84ee-e322fe93e6c9',
> > >> '1', '1', 'BUILTIN', '0', '64', '
> > >> http://people.apache.org/~bhaisaab/vms/ttylinux_pv.vhd', 'VHD',
> > >> '2013-04-18 16:56:11', NULL, '1', '046e134e642e6d344b34648223ba4bc1',
> > >>'tiny
> > >> Linux', '0', '0', '12', '1', '0', '1', '1', 'XenServer', NULL, NULL,
> > >>'0',
> > >> NULL, NULL, NULL, NULL, '1'
> > >>
> > >>
> > >>
> > >> On Thu, Apr 18, 2013 at 9:39 PM, Rohit Yadav 
> > >>wrote:
> > >>
> > >>> On Fri, Apr 19, 2013 at 8:26 AM, Mike Tutkowski <
> > >>> mike.tutkow...@solidfire.com> wrote:
> > >>>
> > >>> > Hi,
> > >>> >
> > >>> > I've switched back to 4.2 (from 4.1), cleaned out my database,
> > >>> re-created
> > >>> > my DevCloud2 environment and all looks good with the exception that
> > >>>I do
> > >>> > not have a tinyLinux template.
> > >>> >
> > >>> > My SSVM is up and running.
> > >>> >
> > >>> > Any thoughts on what I should do here?
> > >>> >
> > >>>
> > >>> Did you forgot to deploydb with -P tools/devcloud? Looks like db
> > >>>does
> > >>> not know about ttylinux; check in cloud.vm_templates etc?
> > >>>
> > >>> Cheers.
> > >>>
> > >>>
> > >>> >
> > >>> > 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
> > >>> > * *
> > >>> >
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> *Mike Tutkowski*
> > >> *Senior CloudStack Developer, SolidFire Inc.*
> > >> e: mike.tutkow...@solidfire.com
> > >> o: 303.746.7302
> > >> Advancing the way the world uses the
> > >>cloud
> > >> * *
> > >>
> > >
> > >
> > >
> > >--
> > >*Mike Tutkowski*
> > >*Senior CloudStack Developer, SolidFire Inc.*
> > >e: mike.tutkow...@solidfire.com
> > >o: 303.746.7302
> > >Advancing the way the world uses the
> > >cloud
> > >* *
> >
> >
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *™*
>


Re: git commit: updated refs/heads/master to 81e1ba3

2013-04-19 Thread Rohit Yadav
On Fri, Apr 19, 2013 at 9:22 AM, Marcus Sorensen wrote:

> Er, I guess you're asking about the mkdir specifically. I have no idea why
> we'd be doing that in the first place, I'd also be interested in knowing
> that.
>


One of the hacks to make sure a file does not get created on a *nix fs is
to remove the file and make a directory with the same file name. So, this
answers the "why" :)

Abhi suggested that it was causing an issue. In his rinse-repeat-test fix,
he had to remove the directory to make it work with the systemvm appliance
for vmware.

Cheers.


> On Apr 18, 2013 9:51 PM, "Marcus Sorensen"  wrote:
>
> > Those udev rules are often a pain when using VM templates. Their purpose
> > is to tie a specific MAC address to an eth# dev, so for example if you
> > configure an IP address for eth0 and then change the mac address (via VM
> > clone or some such), you suddenly have no IP at all, no eth0, and an eth1
> > tied to the new MAC.
> >
> > The rule in /etc has the MAC to eth# mappings, and the one in /lib
> creates
> > the one in /etc.
> > On Apr 18, 2013 9:41 PM, "Chip Childers" 
> > wrote:
> >
> >>
> >> Hey Rohit,
> >>
> >> Can you explain the change below?  I'm mostly curious.
> >>
> >> On Fri, Apr 19, 2013 at 03:36:36AM +, bhais...@apache.org wrote:
> >> > Updated Branches:
> >> >   refs/heads/master ca6873a9d -> 81e1ba3bb
> >> >
> >> >
> >> > appliance: Don't mkdir 70-persistent-net.rules for systemvms
> >> >
> >> > Signed-off-by: Rohit Yadav 
> >> >
> >> >
> >> > Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo
> >> > Commit:
> >> http://git-wip-us.apache.org/repos/asf/cloudstack/commit/81e1ba3b
> >> > Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/81e1ba3b
> >> > Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/81e1ba3b
> >> >
> >> > Branch: refs/heads/master
> >> > Commit: 81e1ba3bb406f9546f0d46ccbfa3fbbb35b762e2
> >> > Parents: ca6873a
> >> > Author: Rohit Yadav 
> >> > Authored: Fri Apr 19 09:05:42 2013 +0530
> >> > Committer: Rohit Yadav 
> >> > Committed: Fri Apr 19 09:05:42 2013 +0530
> >> >
> >> > --
> >> >  .../definitions/systemvmtemplate/cleanup.sh|1 -
> >> >  .../definitions/systemvmtemplate64/cleanup.sh  |1 -
> >> >  2 files changed, 0 insertions(+), 2 deletions(-)
> >> > --
> >> >
> >> >
> >> >
> >>
> http://git-wip-us.apache.org/repos/asf/cloudstack/blob/81e1ba3b/tools/appliance/definitions/systemvmtemplate/cleanup.sh
> >> > --
> >> > diff --git a/tools/appliance/definitions/systemvmtemplate/cleanup.sh
> >> b/tools/appliance/definitions/systemvmtemplate/cleanup.sh
> >> > index 9e98ab0..701d8d8 100644
> >> > --- a/tools/appliance/definitions/systemvmtemplate/cleanup.sh
> >> > +++ b/tools/appliance/definitions/systemvmtemplate/cleanup.sh
> >> > @@ -12,7 +12,6 @@ rm /var/lib/dhcp/*
> >> >  # Make sure Udev doesn't block our network
> >> >  echo "cleaning up udev rules"
> >> >  rm /etc/udev/rules.d/70-persistent-net.rules
> >> > -mkdir /etc/udev/rules.d/70-persistent-net.rules
> >> >  rm -rf /dev/.udev/
> >> >  rm /lib/udev/rules.d/75-persistent-net-generator.rules
> >> >
> >> >
> >> >
> >>
> http://git-wip-us.apache.org/repos/asf/cloudstack/blob/81e1ba3b/tools/appliance/definitions/systemvmtemplate64/cleanup.sh
> >> > --
> >> > diff --git a/tools/appliance/definitions/systemvmtemplate64/cleanup.sh
> >> b/tools/appliance/definitions/systemvmtemplate64/cleanup.sh
> >> > index 9e98ab0..701d8d8 100644
> >> > --- a/tools/appliance/definitions/systemvmtemplate64/cleanup.sh
> >> > +++ b/tools/appliance/definitions/systemvmtemplate64/cleanup.sh
> >> > @@ -12,7 +12,6 @@ rm /var/lib/dhcp/*
> >> >  # Make sure Udev doesn't block our network
> >> >  echo "cleaning up udev rules"
> >> >  rm /etc/udev/rules.d/70-persistent-net.rules
> >> > -mkdir /etc/udev/rules.d/70-persistent-net.rules
> >> >  rm -rf /dev/.udev/
> >> >  rm /lib/udev/rules.d/75-persistent-net-generator.rules
> >> >
> >> >
> >> >
> >>
> >
>


Re: CS 4.0.0 - vpc deployment - why tier network limited to 200mb/s ?

2013-04-19 Thread benoit lair
Hello Chiradeep,

So with a VR running on a x5550 hexacore with not enough noisy neighboors
with a computing offering with 4 core, 4 gb ram, i can hope to run 20 vlans
with a total troughput of 2 gb max with 10 ip load balanced (each onto 3
vms) for a total amount of 3k connections (max, avg at 500 connect/s) and a
max bp of 200Mb/s (this bp is only for the lb ip) ? Or is it not enough
(hoping it is not impossible) ?


Thanks for your response.

Regards, Benoit.


2013/4/18 Chiradeep Vittal 

> Really depends on
>  - your CPU configuration
>  - your hypervisor
>  - your physical network speed
>  - noisy neighbors around the VR / around the physical network
>  - how many ipsec vpns
>  - how many LB
>  - load on the LB
>  - number of connections
>
> If you just test the VR in isolation with a 512GB RAM/1core configuration
> you should be able to get
>  - 2 Gb/s forwarding / firewalling OR
>  - 4 to 5k conn/s on the LB
>
> You add the other factors and things can vary wildly
>
>
> On 4/18/13 2:58 AM, "benoit lair"  wrote:
>
> >Hello,
> >
> >
> >Thanks for your response.
> >
> >However, do you know in production cases, what are the maximum bandwidth i
> >can manage with a vpc vr ? Are there limitations or any recommendations
> >(sizing limit in order to avoid performance loss) concerning provisionning
> >of the vpc ?
> >
> >
> >Thanks for your advices.
> >
> >Regards, Benoit.
> >
> >2013/4/17 benoit lair 
> >
> >> Hello guys,
> >>
> >>
> >> I'm testing an preproduction environment with cs4.0.0 onto centos 5.3.
> >>
> >> I'm testing a vpc environment.
> >>
> >> I'm asking why does the tier networks are limited to 200mb/s (network
> >> offering DefaultIsolatedNetworkOfferingForVpcNetworksNoLB) ?
> >> So in xencenter, if i look at the network tab of my vpc vr vm, i got a
> >>qos
> >> of 25600 kbytes/sec.
> >>
> >> Is there a risk to create a different network offering with a 1000 mb/s
> >> qos limit ? no limit ?
> >>
> >> What if i want to recreate a multi tier environnment with a no limit of
> >> qos with a 500 mb/s troughput, a 1000mb/s troughput ?
> >>
> >> What do you think about vpc vr capabilities ? any deployment
> >> recommendations ?
> >>
> >>
> >> Thanks for any advice.
> >>
> >> Regards, Benoit Lair.
> >>
> >>
> >>
> >>
>
>


Re: CS 4.0.0 - mysql server connections aborted

2013-04-19 Thread benoit lair
Hello Chiradeep,


Thanks for your response, i'm going to look this more precisely.

I'm going back when got more results.



Regards, Benoit.


2013/4/18 Chiradeep Vittal 

> There should be a way for MySQL to log the connections that get aborted.
> At least it will tell you if it was the client that aborted the
> connection.
>
>
> On 4/18/13 6:16 AM, "benoit lair"  wrote:
>
> >Hello,
> >
> >
> >I'm using a cs 4.0.0 preproduction server onto centos 5.3.
> >
> >I have launched a mysqltuner.pl onto the mysql server of the mgmt server.
> >
> >So it gives me connections aborted.
> >
> >Have you an explication why it show this ? How can i troubleshoot this ?
> >
> >Here is my mysqltuner.pl output :
> >
> >[root@cloudstack-master-server ~]# ./mysqltuner.pl
> >
> > >>  MySQLTuner 1.2.0 - Major Hayden 
> > >>  Bug reports, feature requests, and downloads at
> >http://mysqltuner.com/
> > >>  Run with '--help' for additional options and output filtering
> >Please enter your MySQL administrative login: root
> >Please enter your MySQL administrative password:
> >
> > General Statistics
> >--
> >[--] Skipped version check for MySQLTuner script
> >[OK] Currently running supported MySQL version 5.1.67-log
> >[OK] Operating on 64-bit architecture
> >
> > Storage Engine Statistics
> >---
> >[--] Status: -Archive -BDB -Federated +InnoDB -ISAM -NDBCluster
> >[--] Data in InnoDB tables: 23M (Tables: 166)
> >[--] Data in MEMORY tables: 125K (Tables: 2)
> >[!!] Total fragmented tables: 166
> >
> > Security Recommendations
> >---
> >[OK] All database users have passwords assigned
> >
> > Performance Metrics
> >-
> >[--] Up for: 7m 46s (79K q [169.689 qps], 16 conn, TX: 20M, RX: 6M)
> >[--] Reads / Writes: 93% / 7%
> >[--] Total buffers: 66.0M global + 3.6M per thread (350 max threads)
> >[OK] Maximum possible memory usage: 1.3G (13% of installed RAM)
> >[OK] Slow queries: 0% (0/79K)
> >[OK] Highest usage of available connections: 2% (10/350)
> >[OK] Key buffer size / total MyISAM indexes: 8.0M/92.0K
> >[OK] Key buffer hit rate: 100.0% (24 cached / 0 reads)
> >[OK] Query cache efficiency: 28.7% (7K cached / 25K selects)
> >[OK] Query cache prunes per day: 0
> >[OK] Sorts requiring temporary tables: 0% (0 temp sorts / 844 sorts)
> >[!!] Joins performed without indexes: 35
> >[OK] Temporary tables created on disk: 1% (12 on disk / 936 total)
> >[!!] Thread cache hit rate: 37% (10 created / 16 connections)
> >[OK] Table cache hit rate: 92% (128 open / 138 opened)
> >[OK] Open file limit used: 0% (12/1K)
> >[OK] Table locks acquired immediately: 100% (7K immediate / 7K locks)
> >[!!] Connections aborted: 12%
> >[OK] InnoDB data size / buffer pool: 23.1M/24.0M
> >
> > Recommendations
> >-
> >General recommendations:
> >Run OPTIMIZE TABLE to defragment tables for better performance
> >MySQL started within last 24 hours - recommendations may be inaccurate
> >Enable the slow query log to troubleshoot bad queries
> >Adjust your join queries to always utilize indexes
> >Your applications are not closing MySQL connections properly
> >Variables to adjust:
> >join_buffer_size (> 1.0M, or always use indexes with joins)
> >thread_cache_size (> 4)
> >
> >
> >Thanks for any advice.
> >
> >
> >Regards, Benoit.
>
>


[Discuss] UI for the Dedicated VLANs per Tenant

2013-04-19 Thread Abhinav Roy
Hi,

I am doing the QA for the feature Dedicated VLANs per Tenant and I had some 
queries about what kind of UI will be there for this feature.

In the current implementation after introduction of Non-contiguous VLANs we 
have the following :


1.   If there is an existing VLAN range IP1 - IP10, and we want to add 
another range IP10 - IP20 or IP5 - IP20, then the existing range will be 
extended to IP1 - IP20,

2.   But if we add a VLAN range which is not overlapping like IP25 - IP30 
then a new range gets added.

But for Dedicated VLANs pee tenant we need to dedicate different VLAN ranges to 
different accounts and we need not necessarily expand the range because we may 
need to dedicate them to different accounts. Like ,


1.   There is an existing range IP1 - IP10 which is dedicated to account A1 
but  if I add another range IP10 - IP20 with the intent of dedicating it to 
another account A2 but in the current implementation  the existing range will 
be expanded and as per my understanding it will still be dedicated to A1.


So, I was just curious to know why can't we have the same kind of UI which we 
have for Public IP addresses for VLANs too?


1.   There we can have multiple ranges , contiguous or non-contiguous added 
as per need.

2.   We can dedicate those ranges to accounts as per need and if an account 
needs more than one range or expansion of  the range then we can dedicate those 
ranges separately to that account and hence it will serve both our purpose.

I just wanted an insight on the kind of UI we are going to have for dedicated 
vlans and these things came to my mind. Please help me clarify my doubts.


Thanks and regards,
Abhinav


Re: no tinyLinux template

2013-04-19 Thread Mike Tutkowski
Yeah, the VHD file at that location is about 50 MB.


On Fri, Apr 19, 2013 at 1:36 PM, Rohit Yadav  wrote:

> On Fri, Apr 19, 2013 at 11:56 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
> > Yeah, I generally revert to the DevCloud2 initial state whenever I
> create a
> > new CS database...just to be on the safe side.
> >
> > I see this folder:
> >
> > /opt/storage/secondary/template/tmpl/1/5/ (the path is a little different
> > from yours)
> >
> > It has a VHD file in it.
> >
>
> It's tiny linux about 50MB.
>
>
> >
> > I looked at devcloud.cfg in the hopes that the secondary storage URL was
> > different, but it shows the following:
> >
> > "secondaryStorages": [
> > {
> > "url": "nfs://192.168.56.10:/opt/storage/secondary"
> > }
> >
>
>
> This is correct as unless you're doing something else, the default IP of
> DevCloud2 appliance is 192.168.56.10 and path to secondary storage is
> indeed /opt/storage/secondary
>
> Cheers.
>
>
> >
> >
> > On Fri, Apr 19, 2013 at 10:51 AM, Chiradeep Vittal <
> > chiradeep.vit...@citrix.com> wrote:
> >
> > > FWIW, I always revert to the initial snapshot of devcloud2 before
> > > switching contexts.
> > > You should also check
> > > select * from template_host_ref where template_id = 5;
> > >
> > > And inside DevCloud2
> > > ls /opt/secondary/template/tmpl/1/5/
> > >
> > > And, inside the SSVM
> > > ps -ef | grep java
> > >
> > >
> > > On 4/18/13 9:54 PM, "Mike Tutkowski" 
> > wrote:
> > >
> > > >It's strange...I deleted my entire cloud and re-created it this way:
> > > >
> > > >mvn -pl developer,tools/devcloud -Ddeploydb -P developer
> > > >
> > > >cd tools/devcloud ; python ../marvin/marvin/deployDataCenter.py -i
> > > >devcloud.cfg
> > > >
> > > >but still no tinyLinux template (even though it is in the
> > > >cloud.vm_template
> > > >table).
> > > >
> > > >
> > > >On Thu, Apr 18, 2013 at 10:05 PM, Mike Tutkowski <
> > > >mike.tutkow...@solidfire.com> wrote:
> > > >
> > > >> Here is what I used to deploy the DB:
> > > >>
> > > >> mvn -pl developer,tools/devcloud -Ddeploydb -P developer
> > > >>
> > > >> Also, cloud.vm_template has this row:
> > > >>
> > > >> '5', 'tiny Linux', 'tiny Linux',
> > '2a182234-a87b-11e2-84ee-e322fe93e6c9',
> > > >> '1', '1', 'BUILTIN', '0', '64', '
> > > >> http://people.apache.org/~bhaisaab/vms/ttylinux_pv.vhd', 'VHD',
> > > >> '2013-04-18 16:56:11', NULL, '1',
> '046e134e642e6d344b34648223ba4bc1',
> > > >>'tiny
> > > >> Linux', '0', '0', '12', '1', '0', '1', '1', 'XenServer', NULL, NULL,
> > > >>'0',
> > > >> NULL, NULL, NULL, NULL, '1'
> > > >>
> > > >>
> > > >>
> > > >> On Thu, Apr 18, 2013 at 9:39 PM, Rohit Yadav 
> > > >>wrote:
> > > >>
> > > >>> On Fri, Apr 19, 2013 at 8:26 AM, Mike Tutkowski <
> > > >>> mike.tutkow...@solidfire.com> wrote:
> > > >>>
> > > >>> > Hi,
> > > >>> >
> > > >>> > I've switched back to 4.2 (from 4.1), cleaned out my database,
> > > >>> re-created
> > > >>> > my DevCloud2 environment and all looks good with the exception
> that
> > > >>>I do
> > > >>> > not have a tinyLinux template.
> > > >>> >
> > > >>> > My SSVM is up and running.
> > > >>> >
> > > >>> > Any thoughts on what I should do here?
> > > >>> >
> > > >>>
> > > >>> Did you forgot to deploydb with -P tools/devcloud? Looks like
> db
> > > >>>does
> > > >>> not know about ttylinux; check in cloud.vm_templates etc?
> > > >>>
> > > >>> Cheers.
> > > >>>
> > > >>>
> > > >>> >
> > > >>> > 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
> > > >>> > * *
> > > >>> >
> > > >>>
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> *Mike Tutkowski*
> > > >> *Senior CloudStack Developer, SolidFire Inc.*
> > > >> e: mike.tutkow...@solidfire.com
> > > >> o: 303.746.7302
> > > >> Advancing the way the world uses the
> > > >>cloud
> > > >> * *
> > > >>
> > > >
> > > >
> > > >
> > > >--
> > > >*Mike Tutkowski*
> > > >*Senior CloudStack Developer, SolidFire Inc.*
> > > >e: mike.tutkow...@solidfire.com
> > > >o: 303.746.7302
> > > >Advancing the way the world uses the
> > > >cloud
> > > >* *
> > >
> > >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud
> > *™*
> >
>



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


Re: IP tables blocking KVM/Console

2013-04-19 Thread Maurice Lawler
Marcus, here is that output you mentioned -- To avoid this from happening, I run a cronjob to clear the tables ever so often, as to not repopulate and cause issues.Chain INPUT (policy ACCEPT 13136 packets, 71M bytes) pkts bytes target prot opt in out source   destination Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source   destination   236 19146 BF-cloudbr0  all  --  any    cloudbr0  anywhere anywhere    PHYSDEV match --physdev-is-bridged   219 15428 BF-cloudbr0  all  --  cloudbr0 any anywhere anywhere    PHYSDEV match --physdev-is-bridged   219 15428 DROP   all  --  any    cloudbr0  anywhere anywhere        0 0 DROP   all  --  cloudbr0 any anywhere anywhere    Chain OUTPUT (policy ACCEPT 13116 packets, 71M bytes) pkts bytes target prot opt in out source   destination Chain BF-cloudbr0 (2 references) pkts bytes target prot opt in out source   destination     0 0 ACCEPT all  --  any    any anywhere anywhere    state RELATED,ESTABLISHED   455 34574 BF-cloudbr0-IN  all  --  any    any anywhere anywhere    PHYSDEV match --physdev-is-in --physdev-is-bridged   446 31622 BF-cloudbr0-OUT  all  --  any    any anywhere anywhere    PHYSDEV match --physdev-is-out --physdev-is-bridged     0 0 ACCEPT all  --  any    any anywhere anywhere    PHYSDEV match --physdev-out eth0 --physdev-is-bridged Chain BF-cloudbr0-IN (1 references) pkts bytes target prot opt in out source   destination     9  2952 i-2-30-def  all  --  any    any anywhere anywhere    PHYSDEV match --physdev-in vnet11 --physdev-is-bridged Chain BF-cloudbr0-OUT (1 references) pkts bytes target prot opt in out source   destination     8   766 i-2-30-def  all  --  any    any anywhere anywhere    PHYSDEV match --physdev-out vnet11 --physdev-is-bridged Chain i-2-30-VM (1 references) pkts bytes target prot opt in out source   destination     8   766 DROP   all  --  any    any anywhere anywhere    Chain i-2-30-VM-eg (1 references) pkts bytes target prot opt in out source   destination     0 0 RETURN all  --  any    any anywhere anywhere    Chain i-2-30-def (2 references) pkts bytes target prot opt in out source   destination     0 0 ACCEPT all  --  any    any anywhere anywhere    state RELATED,ESTABLISHED     9  2952 ACCEPT udp  --  any    any anywhere anywhere    PHYSDEV match --physdev-in vnet11 --physdev-is-bridged udp spt:bootpc dpt:bootps     0 0 ACCEPT udp  --  any    any anywhere anywhere    PHYSDEV match --physdev-out vnet11 --physdev-is-bridged udp spt:bootps dpt:bootpc     0 0 RETURN udp  --  any    any 66.232.104.214   anywhere    PHYSDEV match --physdev-in vnet11 --physdev-is-bridged udp dpt:domain     0 0 i-2-30-VM-eg  all  --  any    any 66.232.104.214   anywhere    PHYSDEV match --physdev-in vnet11 --physdev-is-bridged     8   766 i-2-30-VM  all  --  any    any anywhere anywhere    PHYSDEV match --physdev-out vnet11 --physdev-is-bridged On Apr 19, 2013, at 02:22 PM, Marcus Sorensen  wrote:That's reflected by this line:  ACCEPT tcp -- anywhere anywhere tcp dpts:vnc-server:synchronet-db  Although we don't know what interfaces it applies to because we don't have an 'iptables -L -v'  If stopping iptables fixes Maurice's problem it would be interesting to know, as the rules seem to let VNC through. It should be easy to tcpdump and see what traffic is actually being blocked because his rules suggest that VNC is wide open on the KVM host.   On Fri, Apr 19, 2013 at 12:15 PM, Edison Su  wrote:  > This rule will reject all the ingress activities: "REJECT all -- > anywhere anywhere reject-with icmp-host-prohibited" > You can try: > iptables -I INPUT -p tcp -m tcp --dport 5900:6100 -j ACCEPT > to allow console access. > > From: Maurice Lawler [mailto:maurice.law...@me.com] > Sent: Wednesday, April 17, 2013 7:48 PM > To: Cloud Dev > Cc: us...@cloudstack.apache.org; us...@cloudstack.apache.org > Subject: IP tables blocking KVM/Console > > I have stopped iptables at least 15 times, because it keeps blocking my > console access to my instances. How can I either A) disable Iptables all > together / b add a rule to allow it's access. > > Right now, it has this: > > [root@lunder ~]# iptables -L > Chain INPUT (policy ACCEPT) > target prot opt source destin

Re: IP tables blocking KVM/Console

2013-04-19 Thread Maurice Lawler
I've tried it with them disabled (iptables get written) and enabled (the same issue) The cron job seemed to do the trick, until someone just mentioned to try:   iptables -I INPUT -p tcp -m tcp --dport 5900:6100 -j ACCEPTThat's not working, so I am going back to my cronjob!- MauriceOn Apr 19, 2013, at 02:08 PM, Edison Su  wrote:  > -Original Message- > From: Jason Pavao [mailto:jason.pa...@oracle.com] > Sent: Thursday, April 18, 2013 8:50 AM > To: dev@cloudstack.apache.org > Cc: Maurice Lawler; us...@cloudstack.apache.org > Subject: Re: IP tables blocking KVM/Console >  > Maurice, > I was having the same issues, I tried a number of iptables rule changes, but it > seems that whenever a new instance was deployed it would overwrite my > changes and break things again. My temporary fix is to run a cron job that > runs every minute that issues a service iptables stop.  Do you disable security group when creating the zone? If security group is disabled, then there should be no iptables rules created on kvm host when a new instance created.  >  > It's not elegant but it works since I don't have a need for security groups and > am supporting a jenkins continuous testing environment with no need for > network ingress/egress rules. >  > Does anyone else know why this is happening? >  > I am running cs 4.0.1 on oel6.3x64 >  > Any help would be appreciated. > Thanks. > -jason >  > On 4/17/2013 7:47 PM, Maurice Lawler wrote: > > I have stopped iptables at least 15 times, because it keeps blocking > > my console access to my instances. How can I either A) disable > > Iptables all together / b add a rule to allow it's access. > > > > Right now, it has this: > > > > [root@lunder ~]# iptables -L > > Chain INPUT (policy ACCEPT) > > target prot opt source destination > > ACCEPT udp -- anywhere anywhere udp > > dpt:bootps > > ACCEPT tcp -- anywhere anywhere tcp > > dpt:bootps > > ACCEPT tcp -- anywhere anywhere tcp > > dpts:49152:49216 > > ACCEPT tcp -- anywhere anywhere tcp > > dpts:vnc-server:synchronet-db > > ACCEPT tcp -- anywhere anywhere tcp > > dpt:16509 > > ACCEPT tcp -- anywhere anywhere tcp > > dpt:websm > > ACCEPT tcp -- anywhere anywhere tcp dpt:8250 > > ACCEPT tcp -- anywhere anywhere tcp > > dpt:empowerid > > ACCEPT tcp -- anywhere anywhere tcp > > dpt:webcache > > ACCEPT all -- anywhere anywhere state > > RELATED,ESTABLISHED > > ACCEPT icmp -- anywhere anywhere > > ACCEPT all -- anywhere anywhere > > ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh > > REJECT all -- anywhere anywhere reject-with > > icmp-host-prohibited > > > > Chain FORWARD (policy ACCEPT) > > target prot opt source destination > > > > Chain OUTPUT (policy ACCEPT) > > target prot opt source destination > > [root@lunder ~]# > > > > But there was plenty of other rules previously to my stopping it. > > > > >  > -- > Thanks. > -Jason 

Re: ebtables

2013-04-19 Thread Maurice Lawler
<<< text/html; CHARSET=US-ASCII: Unrecognized >>>


Re: CS 4.0.0 - vpc deployment - why tier network limited to 200mb/s ?

2013-04-19 Thread Chiradeep Vittal
Increasing cores won't get you much since the current VR (4.1) linux
2.6.32 where the networking tends to be single-core only. Otherwise YMMV !
Increasing memory also does not give you much -- the bottleneck is the
memory used to store conn track connections -- 512mB will get you about 1
million connections.

Hopefully with the new VR (4.2) we can try and squeeze multi-core
performance out of it.

On 4/19/13 12:54 PM, "benoit lair"  wrote:

>Hello Chiradeep,
>
>So with a VR running on a x5550 hexacore with not enough noisy neighboors
>with a computing offering with 4 core, 4 gb ram, i can hope to run 20
>vlans
>with a total troughput of 2 gb max with 10 ip load balanced (each onto 3
>vms) for a total amount of 3k connections (max, avg at 500 connect/s) and
>a
>max bp of 200Mb/s (this bp is only for the lb ip) ? Or is it not enough
>(hoping it is not impossible) ?
>
>
>Thanks for your response.
>
>Regards, Benoit.
>
>
>2013/4/18 Chiradeep Vittal 
>
>> Really depends on
>>  - your CPU configuration
>>  - your hypervisor
>>  - your physical network speed
>>  - noisy neighbors around the VR / around the physical network
>>  - how many ipsec vpns
>>  - how many LB
>>  - load on the LB
>>  - number of connections
>>
>> If you just test the VR in isolation with a 512GB RAM/1core
>>configuration
>> you should be able to get
>>  - 2 Gb/s forwarding / firewalling OR
>>  - 4 to 5k conn/s on the LB
>>
>> You add the other factors and things can vary wildly
>>
>>
>> On 4/18/13 2:58 AM, "benoit lair"  wrote:
>>
>> >Hello,
>> >
>> >
>> >Thanks for your response.
>> >
>> >However, do you know in production cases, what are the maximum
>>bandwidth i
>> >can manage with a vpc vr ? Are there limitations or any recommendations
>> >(sizing limit in order to avoid performance loss) concerning
>>provisionning
>> >of the vpc ?
>> >
>> >
>> >Thanks for your advices.
>> >
>> >Regards, Benoit.
>> >
>> >2013/4/17 benoit lair 
>> >
>> >> Hello guys,
>> >>
>> >>
>> >> I'm testing an preproduction environment with cs4.0.0 onto centos
>>5.3.
>> >>
>> >> I'm testing a vpc environment.
>> >>
>> >> I'm asking why does the tier networks are limited to 200mb/s (network
>> >> offering DefaultIsolatedNetworkOfferingForVpcNetworksNoLB) ?
>> >> So in xencenter, if i look at the network tab of my vpc vr vm, i got
>>a
>> >>qos
>> >> of 25600 kbytes/sec.
>> >>
>> >> Is there a risk to create a different network offering with a 1000
>>mb/s
>> >> qos limit ? no limit ?
>> >>
>> >> What if i want to recreate a multi tier environnment with a no limit
>>of
>> >> qos with a 500 mb/s troughput, a 1000mb/s troughput ?
>> >>
>> >> What do you think about vpc vr capabilities ? any deployment
>> >> recommendations ?
>> >>
>> >>
>> >> Thanks for any advice.
>> >>
>> >> Regards, Benoit Lair.
>> >>
>> >>
>> >>
>> >>
>>
>>



Re: [ACS41] Quick update on status

2013-04-19 Thread Chip Childers
On Fri, Apr 19, 2013 at 09:17:27AM -0400, Chip Childers wrote:
> Hi all,
> 
> My plan is to cut the RC on Monday for 4.1.0.
> 
> I'm waiting for final word on the fix that Hugo's working on for
> CLOUDSTACK-2092, which he says he'll be done by COB his time today.

This is done.

> 
> I have a task to modify our release procedure to account for some of the
> changes we can make after graduation, and specifically to include the
> use of the maven release plugin to set the version number in our
> released POM files correctly.

This is also done.

> 
> I am *not* planning on pushing the release build to maven central as a
> released version of the code at this time.  Unless someone objects, I
> don't see much value in that.
> 
> Consider this *LAST CALL* for patches that aren't on my radar right now.
> Docs, translations, bugs, whatever...
> 
> Am I missing anything?
> 
> -chip

Last call for 4.1.0 issues!

I will be staging the artifacts over the weekend (Sunday) and calling 
the VOTE after I'm satisfied with the test procedure and the results of 
cutting the RC myself (again, probably Monday).

If I don't see any [ACS41] subject lines on the dev list, and don't see
any new critical or blocker bugs with affects version of 4.1.0, I'll
assume we are good to go.

-chip


Re: [VOTE][ACS402] Apache CloudStack 4.0.2 (Second Round)

2013-04-19 Thread David Nalley
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>

Sadly -1 (binding)
nonoss doesn't build with the release tarball.
I think the problem is version in the vmware-base pom not being updated.

--David


Re: [VOTE][ACS402] Apache CloudStack 4.0.2 (Second Round)

2013-04-19 Thread Simon Weller
-1 for the same reason David mentions below. 


Changing the vmware-base pom version from 4.0.2-SNAPSHOT to 4.0.2 fixes the 
build for me. 

- Original Message -

From: "David Nalley"  
To: dev@cloudstack.apache.org 
Sent: Friday, April 19, 2013 4:43:31 PM 
Subject: Re: [VOTE][ACS402] Apache CloudStack 4.0.2 (Second Round) 

> 
> [ ] +1 approve 
> [ ] +0 no opinion 
> [ ] -1 disapprove (and reason why) 
> 

Sadly -1 (binding) 
nonoss doesn't build with the release tarball. 
I think the problem is version in the vmware-base pom not being updated. 

--David 



RE: [ASFCS42] Proposed schedule for our next release

2013-04-19 Thread Will Chan


> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: Thursday, April 18, 2013 6:41 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [ASFCS42] Proposed schedule for our next release
> 
> On Thu, Apr 18, 2013 at 6:26 PM, Will Chan  wrote:
> >
> > > -Original Message-
> > > From: Chip Childers [mailto:chip.child...@sungard.com]
> > > Sent: Monday, April 15, 2013 7:22 AM
> > > To: dev@cloudstack.apache.org
> > > Cc: cloudstack-...@incubator.apache.org
> > > Subject: Re: [ASFCS42] Proposed schedule for our next release
> > >
> > > On Thu, Apr 11, 2013 at 02:50:02PM -0700, Animesh Chaturvedi wrote:
> > > >
> > > > I want to call out my concern on technical debt we have
> > > > accumulated so
> > > far.
> > > >
> > > >  I did an analysis on JIRA bugs yesterday night PST on "Affects
> > > > Version = 4.1" and created since Dec 2012
> > > >
> > > > Total records : 429
> > > > Resolution Type (Invalid, Duplicate, Cannot reproduce etc.) : 87
> > > > (30 Blockers, 27 Critical, 27 Major, 4 Minor) Valid Defects  :
> > > > 429-87= 342 Fixed : 246 (60 Blockers, 70 Critical, 99 Majors) out
> > > > of which 217 were fixed since Feb Unresolved : 96 (1 Blocker, 8
> > > > Critical, 64 Major)
> > > >
> > > > With this data it looks like we have fixed 2/3 of valid defects in
> > > > little over
> > > 2 months and pretty much deferring around 1/3 rd of issues for
> > > future release.
> > > >
> > > > I also looked at overall backlog of bugs (Critical, Major and
> > > > Blockers only)
> > > as of 4/10/2013 - 10:0PM PST.
> > > >
> > > > 284 open (18 Blocker, 38 Critical, 228 Major) ; By Fix version
> > > > -  Release 4.0.x and prior: 13
> > > > -  4.1: 70
> > > > -  4.2 : 97
> > > > -  Future: 8
> > > > -  No version: 107
> > > >
> > > > Looking at that we fixed 217 bugs in roughly 2 months during 4.1
> > > > cycle,
> > > fixing the backlog of bug  will probably take us 2 months.  Should
> > > we extend the 4.2 test cycle by 2 months [Original Schedule: 6/1 -
> > > 7/22, Extended
> > > Schedule: 6/1-9/22] to reduce the technical debt significantly? I
> > > would like to hear how community wants to address technical debt.
> > > Based on the input and consensus I will publish the agreed schedule
> next week.
> > > >
> > > >
> > >
> > > I don't think that an extension of time changes bug counts really.
> > > IMO, we need to pull together to have some bug-fix focused effort
> > > applied to the code-base.  It's also another reason that I'm so big
> > > on making sure that automated tests come in with the new features.
> > > That doesn't address test scenarios that human testers can come up
> > > with, but if a developer spends the time to think about testing the
> > > basic feature and codifies that, we should at least avoid the "this
> actually doesn't work at all" types of bugs.
> > >
> > > There's a school of thought that says, don't build another feature
> > > until you have sorted out the known bugs in the current features.  I
> > > don't think we could really pull that off, but perhaps a different
> > > thread to rally people around the bug backlog is in order?
> > >
> > > -chip
> >
> > Sorry to chime in so late to this thread as I've been offsite for the better
> part of this week.  I was one of the original 4 month release crowd but after
> the recent two releases of ACS, I'm starting to wonder if we shouldn't start
> moving this to a 6 month cycle instead of two.  Here are some high level
> observations based on the previous two releases:
> >
> > 1. It doesn't seem like we are on a true 4 month time based release
> > schedule.  Both 4.0 and 4.1 were delayed more than several weeks past
> the original proposed GA date.  4.0 was released 11/6 and let's assume that
> 4.1 will ship within a week or two.  That's almost a 6 month release cycle.
> 
> So both 4.0 and 4.1 strike me as extraordinary. 4.0 was our first release -
> and we had lots of issues to resolve. 4.1 introduced a ton of packaging and
> name changes that I also consider to be hopefully one time. Really - we've
> only been through our release cycle once, so I am not ready to declare it
> perpetually behind schedule.
> 
> 
> > Every release incurs a fixed cost of release notes, upgrade testing,
> > etc. that I suspect at least eats a month worth of time depending on
> > people's schedule.  That's 3 months out of the year rather than two if
> > we can get a 6 months cycle.  We can use that extra month for other
> purposes if need be.  I suppose if we want to continue to release past the
> proposed hard GA date, then I guess it doesn't matter if it's 4 or 6 months.
> It's basically a release when the release mgmt. team feels it's right to
> release based on current bugs, etc.
> >
> 
> Having seen the point releases twice now, which still need upgrade testing,
> release notes, etc I don't get the feeling that the 'overhread' referred to
> above is the problem. Joe may disagree with me.
> 
> > 2. As more and more f

Re: CS 4.0.0 - vpc deployment - why tier network limited to 200mb/s ?

2013-04-19 Thread benoit lair
Thanks for your response Chiradeep.


2013/4/19 Chiradeep Vittal 

> Increasing cores won't get you much since the current VR (4.1) linux
> 2.6.32 where the networking tends to be single-core only. Otherwise YMMV !
> Increasing memory also does not give you much -- the bottleneck is the
> memory used to store conn track connections -- 512mB will get you about 1
> million connections.
>
> Hopefully with the new VR (4.2) we can try and squeeze multi-core
> performance out of it.
>
> On 4/19/13 12:54 PM, "benoit lair"  wrote:
>
> >Hello Chiradeep,
> >
> >So with a VR running on a x5550 hexacore with not enough noisy neighboors
> >with a computing offering with 4 core, 4 gb ram, i can hope to run 20
> >vlans
> >with a total troughput of 2 gb max with 10 ip load balanced (each onto 3
> >vms) for a total amount of 3k connections (max, avg at 500 connect/s) and
> >a
> >max bp of 200Mb/s (this bp is only for the lb ip) ? Or is it not enough
> >(hoping it is not impossible) ?
> >
> >
> >Thanks for your response.
> >
> >Regards, Benoit.
> >
> >
> >2013/4/18 Chiradeep Vittal 
> >
> >> Really depends on
> >>  - your CPU configuration
> >>  - your hypervisor
> >>  - your physical network speed
> >>  - noisy neighbors around the VR / around the physical network
> >>  - how many ipsec vpns
> >>  - how many LB
> >>  - load on the LB
> >>  - number of connections
> >>
> >> If you just test the VR in isolation with a 512GB RAM/1core
> >>configuration
> >> you should be able to get
> >>  - 2 Gb/s forwarding / firewalling OR
> >>  - 4 to 5k conn/s on the LB
> >>
> >> You add the other factors and things can vary wildly
> >>
> >>
> >> On 4/18/13 2:58 AM, "benoit lair"  wrote:
> >>
> >> >Hello,
> >> >
> >> >
> >> >Thanks for your response.
> >> >
> >> >However, do you know in production cases, what are the maximum
> >>bandwidth i
> >> >can manage with a vpc vr ? Are there limitations or any recommendations
> >> >(sizing limit in order to avoid performance loss) concerning
> >>provisionning
> >> >of the vpc ?
> >> >
> >> >
> >> >Thanks for your advices.
> >> >
> >> >Regards, Benoit.
> >> >
> >> >2013/4/17 benoit lair 
> >> >
> >> >> Hello guys,
> >> >>
> >> >>
> >> >> I'm testing an preproduction environment with cs4.0.0 onto centos
> >>5.3.
> >> >>
> >> >> I'm testing a vpc environment.
> >> >>
> >> >> I'm asking why does the tier networks are limited to 200mb/s (network
> >> >> offering DefaultIsolatedNetworkOfferingForVpcNetworksNoLB) ?
> >> >> So in xencenter, if i look at the network tab of my vpc vr vm, i got
> >>a
> >> >>qos
> >> >> of 25600 kbytes/sec.
> >> >>
> >> >> Is there a risk to create a different network offering with a 1000
> >>mb/s
> >> >> qos limit ? no limit ?
> >> >>
> >> >> What if i want to recreate a multi tier environnment with a no limit
> >>of
> >> >> qos with a 500 mb/s troughput, a 1000mb/s troughput ?
> >> >>
> >> >> What do you think about vpc vr capabilities ? any deployment
> >> >> recommendations ?
> >> >>
> >> >>
> >> >> Thanks for any advice.
> >> >>
> >> >> Regards, Benoit Lair.
> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
>
>


Re: [VOTE][ACS402] Apache CloudStack 4.0.2 (Second Round)

2013-04-19 Thread Joe Brockmeier


On Fri, Apr 19, 2013, at 04:43 PM, David Nalley wrote:
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> 
> Sadly -1 (binding)
> nonoss doesn't build with the release tarball.
> I think the problem is version in the vmware-base pom not being updated.

Ack. You don't think we could simply doc that in the announcement? 

I'll reroll this tomorrow morning with that fix. 

Best,

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


Re: ebtables

2013-04-19 Thread Marcus Sorensen
I don't remember exactly, but if you look at what IS allowed in the
ebtables output, this will show you example rules.


On Fri, Apr 19, 2013 at 2:20 PM, Maurice Lawler wrote:

> Great -- My ebtables rules are back in place. Now, how can I go about
> dropping the rule to allow a secondary IP traffic to a particular VM.
>
> I cannot remember how to do that, someone once told me.
>
>
>
> On Apr 19, 2013, at 01:42 PM, Marcus Sorensen  wrote:
>
> you can go back and disable security groups in the zone if you don't care
> about the ebtables rules, or you can start up ebtables and then restart any
> associated VMs through cloudstack. The rules are dynamic, so they're not
> going to be saved anywhere on the host to be reinstated, they have to be
> reapplied by cloudstack via a restart of the vms.
>
>
> On Fri, Apr 19, 2013 at 11:12 AM, Maurice Lawler  >wrote:
>
> > Anyone know how to correct my mistake?
> >
> > - Maurice
> >
> >
> > On Apr 19, 2013, at 2:01 AM, Maurice Lawler 
> wrote:
> >
> > > Perhaps this was not the best thing, now my ports are open; how can I
> > revert back to eatables.
> > >
> > > Along with that, when reverted, how can I drop rules for a particular
> VM
> > to allow communication via second IP address.
> > >
> > >
> > > On Apr 18, 2013, at 10:34 PM, Maurice Lawler 
> > wrote:
> > >
> > >> Disregard, for now, I have disabled/removed ebtables as shown here:
> > >>
> > >>
> > 3cb1df26ecc0458748ac97cece2da98d41012fa47b6...@sjcpmailbox01.citrite.net
> %3E'>
> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-users/201302.mbox/%
> 3cb1df26ecc0458748ac97cece2da98d41012fa47b6...@sjcpmailbox01.citrite.net
> %3E
>
> > >>
> > >>
> > >> On Apr 18, 2013, at 11:28 PM, Maurice Lawler 
> > wrote:
> > >>
> > >>> Hello --
> > >>>
> > >>> Previously one told me how to do this, but I cannot find my notes on
> > this, so I hope you can help me out.
> > >>>
> > >>> I am attempting to allow a secondary IP address on an instance
> by-pass
> > the routing rules set forth in ebtables. I recall doing something like
> > >>>
> > >>> ebtables nat i-2-25-VM something ... I cannot for the life of me
> > remember.
> > >>>
> > >>> How to list and/or drop the rules per VM.
> > >>>
> > >>> Can you guys assist?
> > >
> >
> >
>
>


Re: IP tables blocking KVM/Console

2013-04-19 Thread Marcus Sorensen
What do you see in :



On Fri, Apr 19, 2013 at 2:17 PM, Maurice Lawler wrote:

> I've tried it with them disabled (iptables get written) and enabled (the
> same issue)
>
> The cron job seemed to do the trick, until someone just mentioned to try:
>
>   iptables -I INPUT -p tcp -m tcp --dport 5900:6100 -j ACCEPT
>
> That's not working, so I am going back to my cronjob!
>
> - Maurice
>
>
> On Apr 19, 2013, at 02:08 PM, Edison Su  wrote:
>
>
>
> > -Original Message-
> > From: Jason Pavao [mailto:jason.pa...@oracle.com]
> > Sent: Thursday, April 18, 2013 8:50 AM
> > To: dev@cloudstack.apache.org
> > Cc: Maurice Lawler; us...@cloudstack.apache.org
> > Subject: Re: IP tables blocking KVM/Console
> >
> > Maurice,
> > I was having the same issues, I tried a number of iptables rule changes,
> but it
> > seems that whenever a new instance was deployed it would overwrite my
> > changes and break things again. My temporary fix is to run a cron job
> that
> > runs every minute that issues a service iptables stop.
>
> Do you disable security group when creating the zone? If security group is
> disabled, then there should be no iptables rules created on kvm host when a
> new instance created.
>
> >
> > It's not elegant but it works since I don't have a need for security
> groups and
> > am supporting a jenkins continuous testing environment with no need for
> > network ingress/egress rules.
> >
> > Does anyone else know why this is happening?
> >
> > I am running cs 4.0.1 on oel6.3x64
> >
> > Any help would be appreciated.
> > Thanks.
> > -jason
> >
> > On 4/17/2013 7:47 PM, Maurice Lawler wrote:
> > > I have stopped iptables at least 15 times, because it keeps blocking
> > > my console access to my instances. How can I either A) disable
> > > Iptables all together / b add a rule to allow it's access.
> > >
> > > Right now, it has this:
> > >
> > > [root@lunder ~]# iptables -L
> > > Chain INPUT (policy ACCEPT)
> > > target prot opt source destination
> > > ACCEPT udp -- anywhere anywhere udp
> > > dpt:bootps
> > > ACCEPT tcp -- anywhere anywhere tcp
> > > dpt:bootps
> > > ACCEPT tcp -- anywhere anywhere tcp
> > > dpts:49152:49216
> > > ACCEPT tcp -- anywhere anywhere tcp
> > > dpts:vnc-server:synchronet-db
> > > ACCEPT tcp -- anywhere anywhere tcp
> > > dpt:16509
> > > ACCEPT tcp -- anywhere anywhere tcp
> > > dpt:websm
> > > ACCEPT tcp -- anywhere anywhere tcp dpt:8250
> > > ACCEPT tcp -- anywhere anywhere tcp
> > > dpt:empowerid
> > > ACCEPT tcp -- anywhere anywhere tcp
> > > dpt:webcache
> > > ACCEPT all -- anywhere anywhere state
> > > RELATED,ESTABLISHED
> > > ACCEPT icmp -- anywhere anywhere
> > > ACCEPT all -- anywhere anywhere
> > > ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh
> > > REJECT all -- anywhere anywhere reject-with
> > > icmp-host-prohibited
> > >
> > > Chain FORWARD (policy ACCEPT)
> > > target prot opt source destination
> > >
> > > Chain OUTPUT (policy ACCEPT)
> > > target prot opt source destination
> > > [root@lunder ~]#
> > >
> > > But there was plenty of other rules previously to my stopping it.
> > >
> > >
> >
> > --
> > Thanks.
> > -Jason
>
>


Re: IP tables blocking KVM/Console

2013-04-19 Thread Marcus Sorensen
what do you see in:

 cat /proc/sys/net/bridge/bridge*

?  I think I've seen issues with these being set to 1, but I think it might
need to be set to 1 if you're using security groups.


On Fri, Apr 19, 2013 at 5:20 PM, Marcus Sorensen wrote:

> What do you see in :
>
>
>
> On Fri, Apr 19, 2013 at 2:17 PM, Maurice Lawler wrote:
>
>> I've tried it with them disabled (iptables get written) and enabled (the
>> same issue)
>>
>> The cron job seemed to do the trick, until someone just mentioned to try:
>>
>>   iptables -I INPUT -p tcp -m tcp --dport 5900:6100 -j ACCEPT
>>
>> That's not working, so I am going back to my cronjob!
>>
>> - Maurice
>>
>>
>> On Apr 19, 2013, at 02:08 PM, Edison Su  wrote:
>>
>>
>>
>> > -Original Message-
>> > From: Jason Pavao [mailto:jason.pa...@oracle.com]
>> > Sent: Thursday, April 18, 2013 8:50 AM
>> > To: dev@cloudstack.apache.org
>> > Cc: Maurice Lawler; us...@cloudstack.apache.org
>> > Subject: Re: IP tables blocking KVM/Console
>> >
>> > Maurice,
>> > I was having the same issues, I tried a number of iptables rule
>> changes, but it
>> > seems that whenever a new instance was deployed it would overwrite my
>> > changes and break things again. My temporary fix is to run a cron job
>> that
>> > runs every minute that issues a service iptables stop.
>>
>> Do you disable security group when creating the zone? If security group
>> is disabled, then there should be no iptables rules created on kvm host
>> when a new instance created.
>>
>> >
>> > It's not elegant but it works since I don't have a need for security
>> groups and
>> > am supporting a jenkins continuous testing environment with no need for
>> > network ingress/egress rules.
>> >
>> > Does anyone else know why this is happening?
>> >
>> > I am running cs 4.0.1 on oel6.3x64
>> >
>> > Any help would be appreciated.
>> > Thanks.
>> > -jason
>> >
>> > On 4/17/2013 7:47 PM, Maurice Lawler wrote:
>> > > I have stopped iptables at least 15 times, because it keeps blocking
>> > > my console access to my instances. How can I either A) disable
>> > > Iptables all together / b add a rule to allow it's access.
>> > >
>> > > Right now, it has this:
>> > >
>> > > [root@lunder ~]# iptables -L
>> > > Chain INPUT (policy ACCEPT)
>> > > target prot opt source destination
>> > > ACCEPT udp -- anywhere anywhere udp
>> > > dpt:bootps
>> > > ACCEPT tcp -- anywhere anywhere tcp
>> > > dpt:bootps
>> > > ACCEPT tcp -- anywhere anywhere tcp
>> > > dpts:49152:49216
>> > > ACCEPT tcp -- anywhere anywhere tcp
>> > > dpts:vnc-server:synchronet-db
>> > > ACCEPT tcp -- anywhere anywhere tcp
>> > > dpt:16509
>> > > ACCEPT tcp -- anywhere anywhere tcp
>> > > dpt:websm
>> > > ACCEPT tcp -- anywhere anywhere tcp dpt:8250
>> > > ACCEPT tcp -- anywhere anywhere tcp
>> > > dpt:empowerid
>> > > ACCEPT tcp -- anywhere anywhere tcp
>> > > dpt:webcache
>> > > ACCEPT all -- anywhere anywhere state
>> > > RELATED,ESTABLISHED
>> > > ACCEPT icmp -- anywhere anywhere
>> > > ACCEPT all -- anywhere anywhere
>> > > ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh
>> > > REJECT all -- anywhere anywhere reject-with
>> > > icmp-host-prohibited
>> > >
>> > > Chain FORWARD (policy ACCEPT)
>> > > target prot opt source destination
>> > >
>> > > Chain OUTPUT (policy ACCEPT)
>> > > target prot opt source destination
>> > > [root@lunder ~]#
>> > >
>> > > But there was plenty of other rules previously to my stopping it.
>> > >
>> > >
>> >
>> > --
>> > Thanks.
>> > -Jason
>>
>>
>


Re: DnsNotifier Example

2013-04-19 Thread Soheil Eizadi
Thanks, that fixed my problem.
-Soheil

On 4/18/13 11:50 PM, "Murali Reddy"  wrote:

>
>Since its a example class, its not added in the client war file that jetty
>runs. Please add a dependency in client/pom.xml as below
>
> 
>   org.apache.cloudstack
>   cloud-plugin-example-dns-notifier
>   ${project.version}
> 
>
>
>
>On 19/04/13 5:58 AM, "Soheil Eizadi"  wrote:
>
>>I am trying to run the DnsNotifier example in my CloudStack Environment,
>>I am having trouble with the Spring wiring. I modified the
>>DnsNotifier.java file to add @Component annotation and modified the two
>>files componentContext.xml.in and nonossComponentContext.xml.in to add
>>reference to the DnsNotifier. I get everything to build but the Spring
>>Class Loader can not find DnsNotifier Class to load, what more needs to
>>be done to get this to run?
>>-Soheil
>>
>>ovider,databaseUpgradeChecker,configurationDaoImpl,GlobalLoadBalancingRul
>>e
>>sServiceImpl,DnsNotifier,niciraNvpDaoImpl,niciraNvpNicMappingDaoImpl,nici
>>r
>>aNvpRouterMappingDaoImpl,NiciraNvpGuestNetworkGuru,NiciraNvp,MidoNetGuest
>>N
>>etworkGuru,MidoNetElement,userAuthenticators,userPasswordEncoders,securit
>>y
>>Checkers,resourceDiscoverers,haInvestigators,haFenceBuilders,deploymentPl
>>a
>>nners,podAllocators,hostAllocators,storagePoolAllocators,ipDeployers,dhcp
>>P
>>roviders,networkGurus,networkElements,org.springframework.context.annotat
>>i
>>on.ConfigurationClassPostProcessor$ImportAwareBeanPostProcessor#0]; root
>>of factory hierarchy
>>ERROR [web.context.ContextLoader] (main:) Context initialization failed
>>org.springframework.beans.factory.BeanCreationException: Error creating
>>bean with name 'actionEventUtils': Injection of autowired dependencies
>>failed; nested exception is
>>org.springframework.beans.factory.BeanCreationException: Could not
>>autowire field: com.cloud.event.dao.EventDao
>>com.cloud.event.ActionEventUtils.eventDao; nested exception is
>>org.springframework.beans.factory.CannotLoadBeanClassException: Cannot
>>find class [org.apache.cloudstack.network.element.DnsNotifier] for bean
>>with name 'DnsNotifier' defined in class path resource
>>[componentContext.xml]; nested exception is
>>java.lang.ClassNotFoundException:
>>org.apache.cloudstack.network.element.DnsNotifier
>>
>>Administrators-MacBook-Pro-7:cloudstack seizadi$ find . -name
>>DnsNotifier.class
>>./plugins/network-elements/dns-notifier/target/classes/org/apache/cloudst
>>a
>>ck/network/element/DnsNotifier.class
>>
>>diff --git 
>>a/plugins/network-elements/dns-notifier/src/org/apache/cloudstack/network
>>/
>>element/DnsNotifier.java
>>b/plugins/network-elements/dns-notifier/src/org/apache/cloudstack/network
>>/
>>element/DnsNotifier.java
>>index c421344..8f8986d 100644
>>--- 
>>a/plugins/network-elements/dns-notifier/src/org/apache/cloudstack/network
>>/
>>element/DnsNotifier.java
>>+++ 
>>b/plugins/network-elements/dns-notifier/src/org/apache/cloudstack/network
>>/
>>element/DnsNotifier.java
>>@@ -22,7 +22,9 @@ import java.util.Map;
>> import java.util.Set;
>>
>> import javax.ejb.Local;
>>-import javax.naming.ConfigurationException;
>>+
>>+import org.apache.log4j.Logger;
>>+import org.springframework.stereotype.Component;
>>
>> import com.cloud.deploy.DeployDestination;
>> import com.cloud.exception.ConcurrentOperationException;
>>@@ -45,13 +47,17 @@ import com.cloud.vm.VirtualMachineProfile;
>>  * @author ahuang
>>  *
>>  */
>>+
>>+@Component
>> @Local(NetworkElement.class)
>> public class DnsNotifier extends AdapterBase implements NetworkElement {
>>
>>
>>diff --git a/client/tomcatconf/componentContext.xml.in
>>b/client/tomcatconf/componentContext.xml.in
>>index bea2f78..202a998 100644
>>--- a/client/tomcatconf/componentContext.xml.in
>>+++ b/client/tomcatconf/componentContext.xml.in
>>@@ -46,6 +46,14 @@
>>   >class="com.cloud.configuration.dao.ConfigurationDaoImpl" />
>>
>>   >="org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl"
>>/>
>>+
>>+  >class="org.apache.cloudstack.network.element.DnsNotifier">
>>+
>>+  
>>+
>>
>>   >   
>>   
>>
>>diff --git a/client/tomcatconf/nonossComponentContext.xml.in
>>b/client/tomcatconf/nonossComponentContext.xml.in
>>index fc8a9cd..9da3d06 100644
>>--- a/client/tomcatconf/nonossComponentContext.xml.in
>>+++ b/client/tomcatconf/nonossComponentContext.xml.in
>>@@ -79,6 +79,13 @@
>>   >class="com.cloud.hypervisor.vmware.resource.VmwareContextFactory" />
>>
>>+  >class="org.apache.cloudstack.network.element.DnsNotifier">
>>+
>>+  
>>+
>>+  
>>   >class="com.cloud.network.dao.NiciraNvpDaoImpl" />
>>@@ -331,6 +338,8 @@
>>   
>>   
>>   
>>+  
>> 

Re: IP tables blocking KVM/Console

2013-04-19 Thread Maurice Lawler
Output: [root@gizmo scripts]# cat /proc/sys/net/bridge/bridge*11100[root@gizmo scripts]# On Apr 19, 2013, at 07:21 PM, Marcus Sorensen  wrote:what do you see in:  cat /proc/sys/net/bridge/bridge*  ? I think I've seen issues with these being set to 1, but I think it might need to be set to 1 if you're using security groups.   On Fri, Apr 19, 2013 at 5:20 PM, Marcus Sorensen wrote:  > What do you see in : > > > > On Fri, Apr 19, 2013 at 2:17 PM, Maurice Lawler wrote: > >> I've tried it with them disabled (iptables get written) and enabled (the >> same issue) >> >> The cron job seemed to do the trick, until someone just mentioned to try: >> >> iptables -I INPUT -p tcp -m tcp --dport 5900:6100 -j ACCEPT >> >> That's not working, so I am going back to my cronjob! >> >> - Maurice >> >> >> On Apr 19, 2013, at 02:08 PM, Edison Su  wrote: >> >> >> >> > -Original Message- >> > From: Jason Pavao [mailto:jason.pa...@oracle.com] >> > Sent: Thursday, April 18, 2013 8:50 AM >> > To: dev@cloudstack.apache.org >> > Cc: Maurice Lawler; us...@cloudstack.apache.org >> > Subject: Re: IP tables blocking KVM/Console >> > >> > Maurice, >> > I was having the same issues, I tried a number of iptables rule >> changes, but it >> > seems that whenever a new instance was deployed it would overwrite my >> > changes and break things again. My temporary fix is to run a cron job >> that >> > runs every minute that issues a service iptables stop. >> >> Do you disable security group when creating the zone? If security group >> is disabled, then there should be no iptables rules created on kvm host >> when a new instance created. >> >> > >> > It's not elegant but it works since I don't have a need for security >> groups and >> > am supporting a jenkins continuous testing environment with no need for >> > network ingress/egress rules. >> > >> > Does anyone else know why this is happening? >> > >> > I am running cs 4.0.1 on oel6.3x64 >> > >> > Any help would be appreciated. >> > Thanks. >> > -jason >> > >> > On 4/17/2013 7:47 PM, Maurice Lawler wrote: >> > > I have stopped iptables at least 15 times, because it keeps blocking >> > > my console access to my instances. How can I either A) disable >> > > Iptables all together / b add a rule to allow it's access. >> > > >> > > Right now, it has this: >> > > >> > > [root@lunder ~]# iptables -L >> > > Chain INPUT (policy ACCEPT) >> > > target prot opt source destination >> > > ACCEPT udp -- anywhere anywhere udp >> > > dpt:bootps >> > > ACCEPT tcp -- anywhere anywhere tcp >> > > dpt:bootps >> > > ACCEPT tcp -- anywhere anywhere tcp >> > > dpts:49152:49216 >> > > ACCEPT tcp -- anywhere anywhere tcp >> > > dpts:vnc-server:synchronet-db >> > > ACCEPT tcp -- anywhere anywhere tcp >> > > dpt:16509 >> > > ACCEPT tcp -- anywhere anywhere tcp >> > > dpt:websm >> > > ACCEPT tcp -- anywhere anywhere tcp dpt:8250 >> > > ACCEPT tcp -- anywhere anywhere tcp >> > > dpt:empowerid >> > > ACCEPT tcp -- anywhere anywhere tcp >> > > dpt:webcache >> > > ACCEPT all -- anywhere anywhere state >> > > RELATED,ESTABLISHED >> > > ACCEPT icmp -- anywhere anywhere >> > > ACCEPT all -- anywhere anywhere >> > > ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh >> > > REJECT all -- anywhere anywhere reject-with >> > > icmp-host-prohibited >> > > >> > > Chain FORWARD (policy ACCEPT) >> > > target prot opt source destination >> > > >> > > Chain OUTPUT (policy ACCEPT) >> > > target prot opt source destination >> > > [root@lunder ~]# >> > > >> > > But there was plenty of other rules previously to my stopping it. >> > > >> > > >> > >> > -- >> > Thanks. >> > -Jason >> >> >

Re: IP tables blocking KVM/Console

2013-04-19 Thread Marcus Sorensen
yea, so you can play with that and see if it makes any difference. Iptables
may be blocking access to your consoleproxy's service, or something else.


On Fri, Apr 19, 2013 at 5:37 PM, Maurice Lawler wrote:

> Output:
>
> [root@gizmo scripts]# cat /proc/sys/net/bridge/bridge*
> 1
> 1
> 1
> 0
> 0
> [root@gizmo scripts]#
>
>
>
>
> On Apr 19, 2013, at 07:21 PM, Marcus Sorensen  wrote:
>
> what do you see in:
>
> cat /proc/sys/net/bridge/bridge*
>
> ? I think I've seen issues with these being set to 1, but I think it might
> need to be set to 1 if you're using security groups.
>
>
> On Fri, Apr 19, 2013 at 5:20 PM, Marcus Sorensen  >wrote:
>
> > What do you see in :
> >
> >
> >
> > On Fri, Apr 19, 2013 at 2:17 PM, Maurice Lawler  >wrote:
> >
> >> I've tried it with them disabled (iptables get written) and enabled (the
> >> same issue)
> >>
> >> The cron job seemed to do the trick, until someone just mentioned to
> try:
> >>
> >> iptables -I INPUT -p tcp -m tcp --dport 5900:6100 -j ACCEPT
> >>
> >> That's not working, so I am going back to my cronjob!
> >>
> >> - Maurice
> >>
> >>
> >> On Apr 19, 2013, at 02:08 PM, Edison Su  wrote:
> >>
> >>
> >>
> >> > -Original Message-
> >> > From: Jason Pavao [mailto:jason.pa...@oracle.com]
> >> > Sent: Thursday, April 18, 2013 8:50 AM
> >> > To: dev@cloudstack.apache.org
> >> > Cc: Maurice Lawler; us...@cloudstack.apache.org
> >> > Subject: Re: IP tables blocking KVM/Console
> >> >
> >> > Maurice,
> >> > I was having the same issues, I tried a number of iptables rule
> >> changes, but it
> >> > seems that whenever a new instance was deployed it would overwrite my
> >> > changes and break things again. My temporary fix is to run a cron job
> >> that
> >> > runs every minute that issues a service iptables stop.
> >>
> >> Do you disable security group when creating the zone? If security group
> >> is disabled, then there should be no iptables rules created on kvm host
> >> when a new instance created.
> >>
> >> >
> >> > It's not elegant but it works since I don't have a need for security
> >> groups and
> >> > am supporting a jenkins continuous testing environment with no need
> for
> >> > network ingress/egress rules.
> >> >
> >> > Does anyone else know why this is happening?
> >> >
> >> > I am running cs 4.0.1 on oel6.3x64
> >> >
> >> > Any help would be appreciated.
> >> > Thanks.
> >> > -jason
> >> >
> >> > On 4/17/2013 7:47 PM, Maurice Lawler wrote:
> >> > > I have stopped iptables at least 15 times, because it keeps blocking
> >> > > my console access to my instances. How can I either A) disable
> >> > > Iptables all together / b add a rule to allow it's access.
> >> > >
> >> > > Right now, it has this:
> >> > >
> >> > > [root@lunder ~]# iptables -L
> >> > > Chain INPUT (policy ACCEPT)
> >> > > target prot opt source destination
> >> > > ACCEPT udp -- anywhere anywhere udp
> >> > > dpt:bootps
> >> > > ACCEPT tcp -- anywhere anywhere tcp
> >> > > dpt:bootps
> >> > > ACCEPT tcp -- anywhere anywhere tcp
> >> > > dpts:49152:49216
> >> > > ACCEPT tcp -- anywhere anywhere tcp
> >> > > dpts:vnc-server:synchronet-db
> >> > > ACCEPT tcp -- anywhere anywhere tcp
> >> > > dpt:16509
> >> > > ACCEPT tcp -- anywhere anywhere tcp
> >> > > dpt:websm
> >> > > ACCEPT tcp -- anywhere anywhere tcp dpt:8250
> >> > > ACCEPT tcp -- anywhere anywhere tcp
> >> > > dpt:empowerid
> >> > > ACCEPT tcp -- anywhere anywhere tcp
> >> > > dpt:webcache
> >> > > ACCEPT all -- anywhere anywhere state
> >> > > RELATED,ESTABLISHED
> >> > > ACCEPT icmp -- anywhere anywhere
> >> > > ACCEPT all -- anywhere anywhere
> >> > > ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh
> >> > > REJECT all -- anywhere anywhere reject-with
> >> > > icmp-host-prohibited
> >> > >
> >> > > Chain FORWARD (policy ACCEPT)
> >> > > target prot opt source destination
> >> > >
> >> > > Chain OUTPUT (policy ACCEPT)
> >> > > target prot opt source destination
> >> > > [root@lunder ~]#
> >> > >
> >> > > But there was plenty of other rules previously to my stopping it.
> >> > >
> >> > >
> >> >
> >> > --
> >> > Thanks.
> >> > -Jason
> >>
> >>
> >
>
>


https://issues.apache.org/jira/browse/CLOUDSTACK-101 OVS support in KVM

2013-04-19 Thread Angeline Shen
ASF 4.1  cloudstack  with openvswitch  support  for   RHEL 6.3   KVM test  
configuration setup:

After completing 
http://nullworks.wordpress.com/2012/09/19/kvm-and-openvswitch-on-centos-6-3-minimal/
 to setup RHEL 6.3 openvswitch, encountered following problems:

1. In this scenario, after service openvswitch start, host is still up running 
but completely lost connection to network.

[root@Rack3Host16 /]# service openvswitch start
Inserting brcompat module [ OK ]
Starting ovsdb-server [ OK ]
Configuring Open vSwitch system IDs [ OK ]
Starting ovs-vswitchd [ OK ]
Starting ovs-brcompatd [ OK ]
iptables already has a rule for gre, not explicitly enabling.
[root@Rack3Host16 /]#


2. content of various files:

/etc/sysconfig/network-scripts/ifcfg-ovsbr1 :
DEVICE=ovsbr1
ONBOOT=yes
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
IPADDR=10.223.58.195
GATEWAY=10.223.58.193
NETMASK=255.255.255.0
HOTPLUG=no


QUESTION:Is  
http://nullworks.wordpress.com/2012/09/19/kvm-and-openvswitch-on-centos-6-3-minimal/
Valid configuration instructions for   openvswitch   RHEL 6.3or are 
there other updated  correct configuration steps?

Thanks



Re: Review Request: Storage motion changes for xenserver

2013-04-19 Thread Abhinandan Prateek
Yes, I think you should propose Devdeep and few others to be a committer.
The others I will discuss with Alex when he is in Hyd on Monday.

On 19/04/13 10:40 PM, "Edison Su"  wrote:

>Sorry, I don't realize you are not a committer yet. BTW, let me nominate
>you as a commiter.
>
>> -Original Message-
>> From: Devdeep Singh [mailto:devdeep.si...@citrix.com]
>> Sent: Thursday, April 18, 2013 2:44 AM
>> To: Edison Su; Anthony Xu; Abhinandan Prateek (aprat...@apache.org);
>> Alex Huang; dev@cloudstack.apache.org
>> Subject: RE: Review Request: Storage motion changes for xenserver
>> 
>> Hi,
>> 
>> The feature was given a ³Ship It² after the review comments were
>>addressed.
>> Can someone apply and commit these changes to the master branch. I have
>> verified that the patch applies cleanly to the latest master.
>> 
>> Regards,
>> Devdeep
>> 
>> From: edison su [mailto:nore...@reviews.apache.org] On Behalf Of edison
>> su
>> Sent: Wednesday, April 17, 2013 11:53 AM
>> To: Anthony Xu; Edison Su; Abhinandan Prateek; Alex Huang
>> Cc: cloudstack; Devdeep Singh
>> Subject: Re: Review Request: Storage motion changes for xenserver
>> 
>> This is an automatically generated e-mail. To reply, visit:
>> https://reviews.apache.org/r/10196/
>> 
>> 
>> 
>> Ship it!
>> 
>> Ship It!
>> 
>> 
>> - edison
>> 
>> 
>> On April 15th, 2013, 7:24 a.m., Devdeep Singh wrote:
>> Review request for cloudstack, Abhinandan Prateek, edison su, Alex
>>Huang,
>> and anthony xu.
>> By Devdeep Singh.
>> 
>> Updated April 15, 2013, 7:24 a.m.
>> 
>> Description
>> 
>> Storage motion for Xenserver. FS for the feature
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storag
>> e+XenMotion+for+XenServer
>> 
>> 1. Implemented Api findStoragePoolsForMigration. Added a new
>>response
>> objects to list storage pools available for migration.
>> 
>> 2. Updated migrateVolume api for allowing migrating volumes of
>>running
>> vms. These changes are integrated into the latest storage refactoring
>> changes.
>> 
>> 3. Added the implementation for findHostsForMigration api. It lists
>>the
>> hosts to which an instance can be migrated, including hosts from within
>>and
>> across clusters to which an instance may be migrated with storage
>>motion.
>> The work of migrating a volume of a running vm is also done in
>>copyAsync.
>> 
>> 4. Updated the listHosts api for backward compatibility.
>> 
>> 5. Added the implementation for migrateVirtualMachineWithVolume
>>api. It
>> migrates an instance with its volumes within a cluster and also across
>>clusters.
>> Also introduced a new XenServerStorageMotionStrategy for migrating
>> volumes of a vm. When a vm is being migrated with its volumes, the vm is
>> put in migrating state and a request is send to the volume manager to
>> migrate the vm and its volumes. Volume manager calls into the volume
>> service which forwards the request to data motion service after moving
>>all
>> the volumes to migrating state. Data motion service enumerates the
>> strategies and the request reaches the XenServerStorageMotionStrategy.
>>It
>> calls in to the resource to complete the operation.
>> 
>> 6. Resolved an issue where storage xenmotion of 2nd VM created from
>>the
>> same template to a host was failing with duplicate_vm exception. Made
>> changes to remove the mac_seed key value pair from other_config when
>> vms are created. This is was storage motion to fail.
>> 
>> 7. Updated the db upgrade schema script.
>> 
>> 8. Added the right permissions in commands.properties
>> 
>> 9. Marvin tests for testing storage motion. Following scenarios are
>>tested.
>> 
>> 9.1. A virtual machine is migrated to another host. Its volumes are
>>also
>> migrated to another storage pool.
>> 
>> 9.2. Just the volumes of a vm are migrated to another storage pool
>>while
>> the vm continues to run on the same host.
>> 
>> 10. Unit tests for testing migration of a vm with its volumes.
>> 
>> 
>> Testing
>> 
>> 1. Unit tests for testing vm migration with volume. They test when a vm
>>is
>> migrated within a cluster or across cluster. Also added negative tests
>>for the
>> scenrios.
>> 
>> 2. Marvin tests to do functional testing. Including tests to varify vm
>>migration
>> with volume across cluster.
>> 
>> 3. Marvin test for volume migration to another storage pool in the
>>cluster
>> while the vm continues to run on the same host.
>> 
>> 4. Also did additional manual testing for the following scenarios:
>> 
>> 4.1 VM migration with volumes within and across cluster.
>> 
>> 4.2 Tested both the scenarios when 'migrateto' optional parameter is
>>passed
>> to the migrate vm with volume api. When it isn't passed, cloudstack
>>picks up
>> a storage pool for migration. When it is passed, the volume is migrated
>>to the
>> pool passed in the parameter.
>> 
>> 4.3 Tested that storage tags are honored when a vm is migrated with its
>> volumes.
>> 
>> 4.4 Tested volume migration when the vm st

Re: git commit: updated refs/heads/master to 81e1ba3

2013-04-19 Thread Abhinandan Prateek


On 20/04/13 1:09 AM, "Rohit Yadav"  wrote:

>On Fri, Apr 19, 2013 at 9:22 AM, Marcus Sorensen
>wrote:
>
>> Er, I guess you're asking about the mkdir specifically. I have no idea
>>why
>> we'd be doing that in the first place, I'd also be interested in knowing
>> that.
>>
>
>
>One of the hacks to make sure a file does not get created on a *nix fs is
>to remove the file and make a directory with the same file name. So, this
>answers the "why" :)
>
>Abhi suggested that it was causing an issue. In his rinse-repeat-test fix,
>he had to remove the directory to make it work with the systemvm appliance
>for vmware.

As Marcus pointed out the initialisation scripts on the Router systemVM
actually tie the interfaces with mac addresses using udev rules. Since the
file pre existed in form of directory the file creation failed. The
failure resulted in template failing to initialise and rendered it useless.
The new VMWare system template that works is now published in another
thread and related bug.


>
>
>> On Apr 18, 2013 9:51 PM, "Marcus Sorensen"  wrote:
>>
>> > Those udev rules are often a pain when using VM templates. Their
>>purpose
>> > is to tie a specific MAC address to an eth# dev, so for example if you
>> > configure an IP address for eth0 and then change the mac address (via
>>VM
>> > clone or some such), you suddenly have no IP at all, no eth0, and an
>>eth1
>> > tied to the new MAC.
>> >
>> > The rule in /etc has the MAC to eth# mappings, and the one in /lib
>> creates
>> > the one in /etc.
>> > On Apr 18, 2013 9:41 PM, "Chip Childers" 
>> > wrote:
>> >
>> >>
>> >> Hey Rohit,
>> >>
>> >> Can you explain the change below?  I'm mostly curious.
>> >>
>> >> On Fri, Apr 19, 2013 at 03:36:36AM +, bhais...@apache.org wrote:
>> >> > Updated Branches:
>> >> >   refs/heads/master ca6873a9d -> 81e1ba3bb
>> >> >
>> >> >
>> >> > appliance: Don't mkdir 70-persistent-net.rules for systemvms
>> >> >
>> >> > Signed-off-by: Rohit Yadav 
>> >> >
>> >> >
>> >> > Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo
>> >> > Commit:
>> >> http://git-wip-us.apache.org/repos/asf/cloudstack/commit/81e1ba3b
>> >> > Tree: 
>>http://git-wip-us.apache.org/repos/asf/cloudstack/tree/81e1ba3b
>> >> > Diff: 
>>http://git-wip-us.apache.org/repos/asf/cloudstack/diff/81e1ba3b
>> >> >
>> >> > Branch: refs/heads/master
>> >> > Commit: 81e1ba3bb406f9546f0d46ccbfa3fbbb35b762e2
>> >> > Parents: ca6873a
>> >> > Author: Rohit Yadav 
>> >> > Authored: Fri Apr 19 09:05:42 2013 +0530
>> >> > Committer: Rohit Yadav 
>> >> > Committed: Fri Apr 19 09:05:42 2013 +0530
>> >> >
>> >> > 
>>--
>> >> >  .../definitions/systemvmtemplate/cleanup.sh|1 -
>> >> >  .../definitions/systemvmtemplate64/cleanup.sh  |1 -
>> >> >  2 files changed, 0 insertions(+), 2 deletions(-)
>> >> > 
>>--
>> >> >
>> >> >
>> >> >
>> >>
>> 
>>http://git-wip-us.apache.org/repos/asf/cloudstack/blob/81e1ba3b/tools/app
>>liance/definitions/systemvmtemplate/cleanup.sh
>> >> > 
>>--
>> >> > diff --git 
>>a/tools/appliance/definitions/systemvmtemplate/cleanup.sh
>> >> b/tools/appliance/definitions/systemvmtemplate/cleanup.sh
>> >> > index 9e98ab0..701d8d8 100644
>> >> > --- a/tools/appliance/definitions/systemvmtemplate/cleanup.sh
>> >> > +++ b/tools/appliance/definitions/systemvmtemplate/cleanup.sh
>> >> > @@ -12,7 +12,6 @@ rm /var/lib/dhcp/*
>> >> >  # Make sure Udev doesn't block our network
>> >> >  echo "cleaning up udev rules"
>> >> >  rm /etc/udev/rules.d/70-persistent-net.rules
>> >> > -mkdir /etc/udev/rules.d/70-persistent-net.rules
>> >> >  rm -rf /dev/.udev/
>> >> >  rm /lib/udev/rules.d/75-persistent-net-generator.rules
>> >> >
>> >> >
>> >> >
>> >>
>> 
>>http://git-wip-us.apache.org/repos/asf/cloudstack/blob/81e1ba3b/tools/app
>>liance/definitions/systemvmtemplate64/cleanup.sh
>> >> > 
>>--
>> >> > diff --git 
>>a/tools/appliance/definitions/systemvmtemplate64/cleanup.sh
>> >> b/tools/appliance/definitions/systemvmtemplate64/cleanup.sh
>> >> > index 9e98ab0..701d8d8 100644
>> >> > --- a/tools/appliance/definitions/systemvmtemplate64/cleanup.sh
>> >> > +++ b/tools/appliance/definitions/systemvmtemplate64/cleanup.sh
>> >> > @@ -12,7 +12,6 @@ rm /var/lib/dhcp/*
>> >> >  # Make sure Udev doesn't block our network
>> >> >  echo "cleaning up udev rules"
>> >> >  rm /etc/udev/rules.d/70-persistent-net.rules
>> >> > -mkdir /etc/udev/rules.d/70-persistent-net.rules
>> >> >  rm -rf /dev/.udev/
>> >> >  rm /lib/udev/rules.d/75-persistent-net-generator.rules
>> >> >
>> >> >
>> >> >
>> >>
>> >
>>




Re: Review Request: updated cloud-early-config to wait for the interfaces to IP come up

2013-04-19 Thread Anthony Urso

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

Ship it!


Ship It!

- Anthony Urso


On April 19, 2013, 12:06 p.m., Jayapal Reddy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10647/
> ---
> 
> (Updated April 19, 2013, 12:06 p.m.)
> 
> 
> Review request for cloudstack, Anthony Urso, Abhinandan Prateek, and edison 
> su.
> 
> 
> Description
> ---
> 
> In VmWare setup, VR failed to get the route for management CIDR. This is 
> happened because when route add command get executed there no eth1 interface 
> set with ip.
> 
> So in cloud-early-config setup_interface added some delay to for interface to 
> setup with ip.
>  
> 
> 
> This addresses bug CLOUDSTACK-2118.
> 
> 
> Diffs
> -
> 
>   patches/systemvm/debian/config/etc/init.d/cloud-early-config 3faa1bd 
> 
> Diff: https://reviews.apache.org/r/10647/diff/
> 
> 
> Testing
> ---
> 
> 1. Tested in vmware and xenserver VR.
> 2. Route for mgmt cidr on vmware and default routes added properly
> 
> 
> Thanks,
> 
> Jayapal Reddy
> 
>



Re: Unable to add XenServer host to basic zone

2013-04-19 Thread Venkata SwamyBabu Budumuru
Sure prasanna. Will submit the patch.

Thanks




Sent from Samsung tablet

prasanna  wrote:
On 19 April 2013 16:29, Venkata SwamyBabu Budumuru
 wrote:
> Hi,
>
> I am seeing the following issue on the MASTER build. Currently I filled it 
> with priority set to "critical". If anyone else seeing the same either you 
> can apply the workaround mentioned in the bug or you can raise the priority.
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-2115 - [BasicZone-XenServer] 
> Unable to add host to basic zone that is configured with bridge

Would you like to submit a patch request with the
result.lower().strip() applied to the vmops plugin? Seems like a
fairly trivial fix.


Re: Review Request: updated cloud-early-config to wait for the interfaces to IP come up

2013-04-19 Thread Abhinandan Prateek


> On April 20, 2013, 4:33 a.m., Anthony Urso wrote:
> > Ship It!

committed


- Abhinandan


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


On April 19, 2013, 12:06 p.m., Jayapal Reddy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10647/
> ---
> 
> (Updated April 19, 2013, 12:06 p.m.)
> 
> 
> Review request for cloudstack, Anthony Urso, Abhinandan Prateek, and edison 
> su.
> 
> 
> Description
> ---
> 
> In VmWare setup, VR failed to get the route for management CIDR. This is 
> happened because when route add command get executed there no eth1 interface 
> set with ip.
> 
> So in cloud-early-config setup_interface added some delay to for interface to 
> setup with ip.
>  
> 
> 
> This addresses bug CLOUDSTACK-2118.
> 
> 
> Diffs
> -
> 
>   patches/systemvm/debian/config/etc/init.d/cloud-early-config 3faa1bd 
> 
> Diff: https://reviews.apache.org/r/10647/diff/
> 
> 
> Testing
> ---
> 
> 1. Tested in vmware and xenserver VR.
> 2. Route for mgmt cidr on vmware and default routes added properly
> 
> 
> Thanks,
> 
> Jayapal Reddy
> 
>