Fwd: Re: Upgrade to 4.3.1

[Mārtiņš Jakubovičs]

Hello,

I installed fresh CS 4.3.1 and it also don't use 
"consoleproxy.url.domain" value.


This is in console proxy, source:

v-2-VMsrc="https://.realhostip.com/ajax?token=1cttHTopOwqQbK_Q9gYmoYMOnzK9fcHUlUv3q6rIUsyVdY3hU7Kmwa7A9RxTz7ZuG4MherlIa0tllGr5XWez73GVyP19iBqxP-c5eCttLrUAotMhMu3GLqPDdEzB2JmVFLZp2DLMBiiAYcdtnNvRl6by-V065VBXyZ729Awd-dnGWE1dNebljz78M5RmNWJXy7HsmrWalWaJyUoI2vMYjBc7FEDksGmCGS_akmN_rPmKH6CdPEyHhNAcvEfb0EiaFFMSA2NUZ9sDfhmmapVxGc1_mHWNWyTqq0WxMfIt6y5CvjmOSUutcagll5sm_SbdUcp7NHB_xZmNAx7yWKnyiMm9XMnYTPnqfrJe8YSSNc481oCgPgPBiQOwbwaoOqtR6PZLDwTPIT6ULkDpy-nL9eVX-lPUJByWzAmgDOGN3ZxV7gwZbvPJGn8cF65Sa5Cb8WN97mYqNqgFZlMChx5ADxNaBYxvWKHfATQoo6utXRg";>


When I set in url correct domain my-ip-add.domain.com, than console 
works, example like this:


https://11-111-111-11.domain.com/ajax?token=1cttHTopOwqQbK_Q9gYmoYMOnzK9fcHUlUv3q6rIUsyVdY3hU7Kmwa7A9RxTz7ZuG4MherlIa0tllGr5XWez73GVyP19iBqxP-c5eCttLrUAotMhMu3GLqPDdEzB2JmVFLZp2DLMBiiAYcdtnNvRl6by-V065VBXyZ729Awd-dnGWE1dNebljz78M5RmNWJXy7HsmrWalWaJyUoI2vMYjBc7FEDksGmCGS_akmN_rPmKH6CdPEyHhNAcvEfb0EiaFFMSA2NUZ9sDfhmmapVxGc1_mHWNWyTqq0WxMfIt6y5CvjmOSUutcagll5sm_SbdUcp7NHB_xZmNAx7yWKnyiMm9XMnYTPnqfrJe8YSSNc481oCgPgPBiQOwbwaoOqtR6PZLDwTPIT6ULkDpy-nL9eVX-lPUJByWzAmgDOGN3ZxV7gwZbvPJGn8cF65Sa5Cb8WN97mYqNqgFZlMChx5ADxNaBYxvWKHfATQoo6utXRg


 Forwarded Message 
Subject:Re: Upgrade to 4.3.1
Date:   Wed, 17 Sep 2014 09:05:21 +0300
From:   Mārtiņš Jakubovičs 
To: us...@cloudstack.apache.org



Hello Ilya,

Thanks for response, I upgraded from 4.3.0 to 4.3.1.

On 2014.09.17. 03:34, ilya musayev wrote:

Mārtiņš

If you dont get a response here, please post on dev. I'll try this out
shortly in my env, what version did you upgrade from?

Regards
ilya
On 9/16/14, 6:07 AM, Mārtiņš Jakubovičs wrote:

Hello,

In CentOS 6.5 today I discovered that is available update for CS 4.3.
I installed it but after management service restart "
consoleproxy.url.domain" value stopped to work. When I launch console
proxy, it connect to ".realhostip.com" domain in a way to connect my
real domain. When I clean this value, console proxy connects to IP.
After entering any other value it connects to ".realhostip.com"
anyway. How I can solve this?

Thanks.

[GitHub] cloudstack pull request: CLOUDSTACK-7143: Refactoring of the syste...

[lsimons]

Github user lsimons commented on the pull request:

https://github.com/apache/cloudstack/pull/16#issuecomment-55866128
  
Hey Rohit, like I thought, a ruby issue.I'm surprised RVM isn't enabled 
already since the build was already using it (I think...). The fix should be 
along the lines of http://rvm.io/integration/jenkins .

The other part of the fix is making sure that the inline shell scripts act 
as login scripts so that rvm is loaded, i.e. they need to start with
```
#!/bin/bash -l
```


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Review Request 25637: CLOUDSTACK-7387: Corrected code related to adding host tags

[SrikanteswaraRao Talluri]

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


commit 20f9d3dcd8a980e03b651629b510b6e98e411271
Author: Gaurav Aradhye 
Date:   Mon Sep 15 14:03:49 2014 +0530

CLOUDSTACK-7387: Corrected code related to adding host tags

Signed-off-by: SrikanteswaraRao Talluri 

commit 374d6ad7981bbec2270e414b161f2e7e74a93758
Author: SrikanteswaraRao Talluri 
Date:   Wed Sep 17 14:34:18 2014 +0530

Revert "CLOUDSTACK-7387: Corrected code related to adding host tags"

This reverts commit 1b14fa6abef5811079eeb7cbd26ab718f6f69405.

- SrikanteswaraRao Talluri


On Sept. 16, 2014, 6:08 a.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25637/
> ---
> 
> (Updated Sept. 16, 2014, 6:08 a.m.)
> 
> 
> Review request for cloudstack, sanjeev n, Santhosh Edukulla, and 
> SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-7387
> https://issues.apache.org/jira/browse/CLOUDSTACK-7387
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> The host tags were not defined and not added to hosts before.
> 
> Changes:
> 1) Searched for cluster with two hosts within the given zone.
> 2) Updated hosts with host tags and added same tags in service offerings used 
> to created VM.
> 3) Deleted the host tags in cleanup.
> 4) Corrected the imports.
> 
> 
> Diffs
> -
> 
>   test/integration/component/maint/test_vpc_host_maintenance.py 83ba271 
> 
> Diff: https://reviews.apache.org/r/25637/diff/
> 
> 
> Testing
> ---
> 
> Yes.
> 
> Ran setUpClass by skipping the test cases. Hosts updated successfully with 
> tags and VMs were deployed.
> 
> Log:
> Test enable Maintenance Mode on Hosts which have VPC elements ... SKIP: skip
> Test cancel Maintenance Mode on the above Hosts + Migrate VMs Back ... SKIP: 
> skip
> Test reconnect Host which has VPC elements ... SKIP: skip
> 
> --
> Ran 3 tests in 465.545s
> 
> OK (SKIP=3)
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Review Request 25684: CLOUDSTACK-7557: test_vpc_network.py - Fixed wait period of network state check

[SrikanteswaraRao Talluri]

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

Ship it!


58ea99a9d665b4370651fe867988d597ea16165e master

- SrikanteswaraRao Talluri


On Sept. 16, 2014, 6:44 a.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25684/
> ---
> 
> (Updated Sept. 16, 2014, 6:44 a.m.)
> 
> 
> Review request for cloudstack, Santhosh Edukulla and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-7557
> https://issues.apache.org/jira/browse/CLOUDSTACK-7557
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> After stopping VMs, the network state should change from "Implemented" to 
> "Allocated" after some time.
> 
> Root cause of failure:
> The wait time in test case is too less. It's 6 sec instead of 60 seconds. 
> Hence the test case failed before the state changed to Allocated.
> 
> Resolution:
> Fixed the wait time.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_vpc_network.py b399765 
> 
> Diff: https://reviews.apache.org/r/25684/diff/
> 
> 
> Testing
> ---
> 
> Yes.
> 
> Log:
> Test update Network that is part of a VPC to a network offering that has more 
> services ... === TestName:
> test_01_network_services_upgrade | Status : SUCCESS ===
> ok
> 
> --
> Ran 1 test in 538.298s
> 
> OK
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Review Request 25642: CLOUDSTACK-7547: Brocade Device Data was hard coded, moved it to config file

[SrikanteswaraRao Talluri]

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

Ship it!


71611da17f082d9d813c89767a69c5b13ba5adf1 master

- SrikanteswaraRao Talluri


On Sept. 16, 2014, 6:02 a.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25642/
> ---
> 
> (Updated Sept. 16, 2014, 6:02 a.m.)
> 
> 
> Review request for cloudstack, Ritu  Sabharwal, Santhosh Edukulla, and 
> SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-7547
> https://issues.apache.org/jira/browse/CLOUDSTACK-7547
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Brocade device data was hard coded. 
> 
> 1) Made changes so that it can be read from the config file. (Config 
> tranlated to the config file we provide to jenkins, not test_data.py file, 
> because dynamic data should always be placed in config, not test_data.py)
> 2) Skipped the test case if the data is not present in config file.
> 3) Removed * from imports and made appropriate changes.
> 
> Following data is supposed to be present in config file, if not present, test 
> case will be skipped.
> 
> "brocadeDeviceData":
> {
> "ipaddress": "X.X.X.X",
> "username": "userxxx",
> "password": "passxxx"
> }
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_brocade_vcs.py a5eff53 
> 
> Diff: https://reviews.apache.org/r/25642/diff/
> 
> 
> Testing
> ---
> 
> Yes.
> 
> Tested all the scenarios of valid and invalid data.
> Skipping of test case was proper.
> 
> When all the data was present, test case moved forward to adding the brocade 
> device but test case still failed because the details I put in config file 
> were not valid (I don't have brocade device details).
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Review Request 23819: CLOUDSTACK-2251: Automation tests for dedicated public IP addreses per tenant feature

[SrikanteswaraRao Talluri]

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


Is this patch still valid?

- SrikanteswaraRao Talluri


On Sept. 2, 2014, 6:26 a.m., Girish Shilamkar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/23819/
> ---
> 
> (Updated Sept. 2, 2014, 6:26 a.m.)
> 
> 
> Review request for cloudstack, sanjeev n and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-2251
> https://issues.apache.org/jira/browse/CLOUDSTACK-2251
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-2251: Automation tests for dedicated public IP addreses per tenant 
> feature
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_dedicate_public_ip_range.py PRE-CREATION 
>   tools/marvin/marvin/config/test_data.py ade8657 
>   tools/marvin/marvin/lib/base.py 99a541a 
> 
> Diff: https://reviews.apache.org/r/23819/diff/
> 
> 
> Testing
> ---
> 
> Yes
> 
> 
> Thanks,
> 
> Girish Shilamkar
> 
>

[GitHub] cloudstack pull request: CLOUDSTACK-7143: Refactoring of the syste...

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/16#issuecomment-55868179
  
Leo, From the jenkins job log [1] I see that the newly refactored build 
script is trying to setup ruby [2] and failing because of this. The jenkins job 
[1] already has rvm setup as I simply cloned it from previous systemvm jobs. 
Can you look at the job and fix it? If you don't have an account on [1], can 
may request access to Hugo, Edison, Chip and other PMC members.

[1] 
http://jenkins.buildacloud.org/job/systemvm-refactor-CLOUDSTACK-7143/3/console
[2] 
https://github.com/schubergphilis/cloudstack/blob/feature/systemvm-refactor-for-upstream/tools/appliance/build.sh#L272


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Review Request 23819: CLOUDSTACK-2251: Automation tests for dedicated public IP addreses per tenant feature

[Gaurav Aradhye]

I will check if it applies properly. It is a valid patch in terms of
whether it should be added to repo or not.

Regards,
Gaurav

On Wed, Sep 17, 2014 at 2:42 PM, SrikanteswaraRao Talluri <
srikanteswararao.tall...@citrix.com> wrote:

>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/23819/#review53670
> ---
>
>
> Is this patch still valid?
>
> - SrikanteswaraRao Talluri
>
>
> On Sept. 2, 2014, 6:26 a.m., Girish Shilamkar wrote:
> >
> > ---
> > This is an automatically generated e-mail. To reply, visit:
> > https://reviews.apache.org/r/23819/
> > ---
> >
> > (Updated Sept. 2, 2014, 6:26 a.m.)
> >
> >
> > Review request for cloudstack, sanjeev n and SrikanteswaraRao Talluri.
> >
> >
> > Bugs: CLOUDSTACK-2251
> > https://issues.apache.org/jira/browse/CLOUDSTACK-2251
> >
> >
> > Repository: cloudstack-git
> >
> >
> > Description
> > ---
> >
> > CLOUDSTACK-2251: Automation tests for dedicated public IP addreses per
> tenant feature
> >
> >
> > Diffs
> > -
> >
> >   test/integration/component/test_dedicate_public_ip_range.py
> PRE-CREATION
> >   tools/marvin/marvin/config/test_data.py ade8657
> >   tools/marvin/marvin/lib/base.py 99a541a
> >
> > Diff: https://reviews.apache.org/r/23819/diff/
> >
> >
> > Testing
> > ---
> >
> > Yes
> >
> >
> > Thanks,
> >
> > Girish Shilamkar
> >
> >
>
>

[CCCEU14] hackathons

[Daan Hoogland]

H devs,

In the schedule for ccceu there is no hackathon day. The reason is that
hackathons have been decreasing in popularity and success. What we do have
is;

1. a room for getting together and working on things
2. a planning page for hackathons, which we might hence forth give another
name at [1].

At the page, there are 7 subjects there but only one of them has more then
one attendee. Please use dev@cloudstack and this page to plan your
hackathon/Birds of a feather/workshop/discussion and design sessions. Hope
to see you all in Budapest and work with you all.

[1]
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Collaboration+Conference+EU

-- 
Daan

Re: CloudStack Docker and Mesos Support

[Sebastien Goasguen]

On Sep 16, 2014, at 7:20 PM, ilya musayev  wrote:

> Hi all,
> 
> Would you know where we stand with Mesos and Docker?
> 

That's a big question.

Mesos is a resource allocator that multiple frameworks can use to run workloads 
of various sorts.
The interest is to mix workloads: big data, long running services, parallel 
computing, docker in order to maximize utilization of your resources.

For instance Aurora (mesos framework) can execute long running services within 
docker containers.

The challenge with docker is the coordination of multiple containers. 
Kubernetes for example coordinate docker containers to run HA applications.

What we see (IMHO) is things like Kubernetes being deployed in the cloud (gce, 
azure, backspace are currently "supported" in kubernetes). And at mesoscon, 
there was a small demo of running kuberneters as a mesos framework.

So…bottom line for me is that I see Mesos and everything on top as a workload 
that can be run in CloudStack. Similar thing with CoreOS. If a CloudStack cloud 
makes available CoreOS templates, then users can start CoreOS cluster and 
manage Docker straight up or via Kubernetes (because of course there is CoreOS 
"support" in Kubernetes).

Hence, there is nothing to do, except for CloudStack clouds to show that they 
can offer Mesos* or Kubernetes* on demand.

However if we were to re-architect CloudStack entirely, we could use Mesos as a 
base resource allocator and write a VM framework. The framework would ask for 
"hypervisors" to mesos and once allocated CloudStack would start them…etc. The 
issue would still be in the networking. The advantage is that a user could run 
a Mesos cluster and mix workloads: CloudStack + Big Data + docker….

Anything we can do to make CoreOS "cloud stackable" and create a cloudstack 
driver in Kubernetes would be really nice.

> Thanks
> ilya

Inter-network Communication

[Pradeep Cloudstack]

In OpenStack, there is a workflow wherein user can create multiple networks, 
then create a router
and attach to it some of the previously created networks to enable 
inter-network communication.

What is the equivalent workflow in Cloudstack ?

-Pradeep

RE: [CCCEU14] hackathons

[Stephen Turner]

Thanks for the pointer, Daan. I'm interested in the API, but when are we 
planning to do this? On the day before the conference starts?

-- 
Stephen Turner


-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] 
Sent: 17 September 2014 10:26
To: dev
Cc: market...@cloudstack.apache.org
Subject: [CCCEU14] hackathons

H devs,

In the schedule for ccceu there is no hackathon day. The reason is that 
hackathons have been decreasing in popularity and success. What we do have is;

1. a room for getting together and working on things 2. a planning page for 
hackathons, which we might hence forth give another name at [1].

At the page, there are 7 subjects there but only one of them has more then one 
attendee. Please use dev@cloudstack and this page to plan your hackathon/Birds 
of a feather/workshop/discussion and design sessions. Hope to see you all in 
Budapest and work with you all.

[1]
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Collaboration+Conference+EU

--
Daan

Travis failures

[sebgoa]

Hi folks,

With Travis tests now passing, it's a good time for everyone to get familiar 
with it and understanding the tests that are being run (advanced zone, 
simulator, smoke tests).

While most builds have been green since yesterday there was two commits (from 
Edison and Min) that turned out red.

https://travis-ci.org/apache/cloudstack/builds

Ideally we should all get in the habit of committing on a separate branch, let 
the tests run and when they pass we can commit to master or the main develop 
branch.

my 2cts

-Sebastien

Re: Inter-network Communication

[Jayapal Reddy Uradi]

Hi Pradeep,

In cloudstack create network and launch vm in that to create router.
To communicate between the networks depends on the network type in cloudstack.

If you want multiple networks with single router use VPC networks/tiers and 
configure ACL between them.

Isolated networks will one router per each network. If vm want to communicate 
to other network
it can be done by  adding nic in that network or Create nat,firewall rules to 
reach vms in other network.

Thanks,
Jayapal

On 17-Sep-2014, at 4:40 PM, Pradeep Cloudstack 

 wrote:

> In OpenStack, there is a workflow wherein user can create multiple networks, 
> then create a router
> and attach to it some of the previously created networks to enable 
> inter-network communication.
> 
> What is the equivalent workflow in Cloudstack ?
> 
> -Pradeep

Re: Review Request 25647: enabling the rootdisksize variable for vm creation wrt managed storage

[punith s]

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

(Updated Sept. 17, 2014, 5:52 p.m.)


Review request for cloudstack and Mike Tutkowski.


Changes
---

removing the fix for IOPS null issue(will be posting it in another review), V3 
only contains the fix for bug 7406


Bugs: 7406
https://issues.apache.org/jira/browse/7406


Repository: cloudstack-git


Description
---

since cloudstack is not able to process the S3 or Switf templates for its 
virtual size(root disk size), admin is facing issues while creating a vm using 
third party storage plugins like cloudbyte and solidfire etc.
this patch enables the resize of root disk, on passing a  variable 
ismanagedstorage = true in deployVmCmd as a detail.
hence template root disksize is overriden by the given rootdisk size by the 
admin

this patch also fixes the iops null issue.

for more ref
https://issues.apache.org/jira/browse/CLOUDSTACK-7406


Diffs (updated)
-

  server/src/com/cloud/vm/UserVmManagerImpl.java 0ea2a89 

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


Testing
---

dry run only.


Thanks,

punith s

Review Request 25732: null IOPS is being processed while creating a vm using third party storage plugins

[punith s]

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

Review request for cloudstack and Mike Tutkowski.


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


Repository: cloudstack-git


Description
---

this bug will only occur in the following scenario
1> create a compute offering with custom mode but not custom IOPS
2> input the required min and max IOPS
3> now create a VM based on the created compute offering

issue:
ServiceOfferingVO dummyoffering = new ServiceOfferingVO(serviceOffering);
this constructor is not setting the min and max IOPS for the dummyoffering

fix: 
adding the min and max iops to the following constructor.


Diffs
-

  engine/schema/src/com/cloud/service/ServiceOfferingVO.java df68fb8 
  engine/schema/src/com/cloud/storage/DiskOfferingVO.java 152fa2c 

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


Testing
---

system testing done


Thanks,

punith s

Re: Travis failures

[Ian Duffy]

If the community wishes we can enable travis-ci to do email alerts. It will
email the person who broke the branch.

On 17 September 2014 12:33, sebgoa  wrote:

> Hi folks,
>
> With Travis tests now passing, it's a good time for everyone to get
> familiar with it and understanding the tests that are being run (advanced
> zone, simulator, smoke tests).
>
> While most builds have been green since yesterday there was two commits
> (from Edison and Min) that turned out red.
>
> https://travis-ci.org/apache/cloudstack/builds
>
> Ideally we should all get in the habit of committing on a separate branch,
> let the tests run and when they pass we can commit to master or the main
> develop branch.
>
> my 2cts
>
> -Sebastien

Re: [CCCEU14] hackathons

[Rafael Weingartner]

Are we going to have hackathons in ccceu in Hungary in November the 19th?

On Wed, Sep 17, 2014 at 8:29 AM, Stephen Turner 
wrote:

> Thanks for the pointer, Daan. I'm interested in the API, but when are we
> planning to do this? On the day before the conference starts?
>
> --
> Stephen Turner
>
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: 17 September 2014 10:26
> To: dev
> Cc: market...@cloudstack.apache.org
> Subject: [CCCEU14] hackathons
>
> H devs,
>
> In the schedule for ccceu there is no hackathon day. The reason is that
> hackathons have been decreasing in popularity and success. What we do have
> is;
>
> 1. a room for getting together and working on things 2. a planning page
> for hackathons, which we might hence forth give another name at [1].
>
> At the page, there are 7 subjects there but only one of them has more then
> one attendee. Please use dev@cloudstack and this page to plan your
> hackathon/Birds of a feather/workshop/discussion and design sessions. Hope
> to see you all in Budapest and work with you all.
>
> [1]
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Collaboration+Conference+EU
>
> --
> Daan
>



-- 
Rafael Weingärtner

Re: Travis failures

[Daan Hoogland]

The checkin by Min was not the problem (Edisons was on his own branch)
Rohit showed me the travis run on this commit in his travis account. It was
green.

So our travis setup is not perfect yet :(

On Wed, Sep 17, 2014 at 2:34 PM, Ian Duffy  wrote:

> If the community wishes we can enable travis-ci to do email alerts. It will
> email the person who broke the branch.
>
> On 17 September 2014 12:33, sebgoa  wrote:
>
> > Hi folks,
> >
> > With Travis tests now passing, it's a good time for everyone to get
> > familiar with it and understanding the tests that are being run (advanced
> > zone, simulator, smoke tests).
> >
> > While most builds have been green since yesterday there was two commits
> > (from Edison and Min) that turned out red.
> >
> > https://travis-ci.org/apache/cloudstack/builds
> >
> > Ideally we should all get in the habit of committing on a separate
> branch,
> > let the tests run and when they pass we can commit to master or the main
> > develop branch.
> >
> > my 2cts
> >
> > -Sebastien
>



-- 
Daan

Re: [CCCEU14] hackathons

[Daan Hoogland]

We are going to have a launch for organising them. So please add your ideas
and find people to join in. I will extend the table on the wiki to include
timeslot and leaf room for extra 'contestants' to add their name.

On Wed, Sep 17, 2014 at 2:49 PM, Rafael Weingartner <
rafaelweingart...@gmail.com> wrote:

> Are we going to have hackathons in ccceu in Hungary in November the 19th?
>
> On Wed, Sep 17, 2014 at 8:29 AM, Stephen Turner  >
> wrote:
>
> > Thanks for the pointer, Daan. I'm interested in the API, but when are we
> > planning to do this? On the day before the conference starts?
> >
> > --
> > Stephen Turner
> >
> >
> > -Original Message-
> > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> > Sent: 17 September 2014 10:26
> > To: dev
> > Cc: market...@cloudstack.apache.org
> > Subject: [CCCEU14] hackathons
> >
> > H devs,
> >
> > In the schedule for ccceu there is no hackathon day. The reason is that
> > hackathons have been decreasing in popularity and success. What we do
> have
> > is;
> >
> > 1. a room for getting together and working on things 2. a planning page
> > for hackathons, which we might hence forth give another name at [1].
> >
> > At the page, there are 7 subjects there but only one of them has more
> then
> > one attendee. Please use dev@cloudstack and this page to plan your
> > hackathon/Birds of a feather/workshop/discussion and design sessions.
> Hope
> > to see you all in Budapest and work with you all.
> >
> > [1]
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Collaboration+Conference+EU
> >
> > --
> > Daan
> >
>
>
>
> --
> Rafael Weingärtner
>



-- 
Daan

Review Request 25734: CLOUDSTACK-7565: Fixes to avoid QEMU issue in attach volume operation by changing test case steps

[Gaurav Aradhye]

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

Review request for cloudstack, Santhosh Edukulla and SrikanteswaraRao Talluri.


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


Repository: cloudstack-git


Description
---

Attach volume test cases failed with following exception from QEMU:
internal error unable to execute QEMU command '__com.redhat_drive_add': 
Duplicate ID 'drive-virtio-disk1' for drive

It has been observed that this issue occurs when disks are repeatedly attached 
and detached from VM and this is an intermittent issue.

However we can avoid this issue by creating new account and a VM in it and 
attaching volume to this VM. This fixes 8 test cases from 
test_escalations_volume.py test suite.


Changes:
1) Moved account creation and VM deployment from setUpClass() to setUp()
2) Fixed import * issues
3) Fixed pep8 issues


Diffs
-

  test/integration/component/test_escalations_volumes.py db4c3d8 

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


Testing
---

Yes. Ran whole test suite against KVM and all test cases passed.

Log:
@summary: Test List Volumes pagination ... === TestName: 
test_01_list_volumes_pagination | Status : SUCCESS ===
ok
@summary: Test List Volumes with Id ... === TestName: test_02_list_volume_byid 
| Status : SUCCESS ===
ok
@summary: Test to verify creation and resize of data volume ... === TestName: 
test_03_data_volume_resize | Status : SUCCESS ===
ok
@summary: Test to verify creation and resize of custom volume ... === TestName: 
test_04_custom_volume_resize | Status : SUCCESS ===
ok
@summary: Test to verify creation of snapshot from volume and creation of 
template, volume from snapshot ... === TestName: test_05_volume_snapshot | 
Status : SUCCESS
===
ok
@summary: Test to verify creation of Hourly Snapshot policies from volume ... 
=== TestName: test_06_volume_snapshot_policy_hourly | Status : SUCCESS ===
ok
@summary: Test to verify creation of Daily Snapshot policies from volume ... 
=== TestName: test_07_volume_snapshot_policy_daily | Status : SUCCESS ===
ok
@summary: Test to verify creation of Weekly Snapshot policies from volume ... 
=== TestName: test_08_volume_snapshot_policy_weekly | Status : SUCCESS ===
ok
@summary: Test to verify creation of Monthly Snapshot policies from volume ... 
=== TestName: test_09_volume_snapshot_policy_monthly | Status : SUCCESS ===
ok
@summary: Test to verify pagination of snapshots for Volume ... === TestName: 
test_10_volume_snapshots_pagination | Status : SUCCESS ===
ok
@summary: Test to verify extract/download a Volume ... === TestName: 
test_11_volume_extract | Status : SUCCESS ===
ok
@summary: Test to verify upload volume ... === TestName: test_12_volume_upload 
| Status : SUCCESS ===
ok

--
Ran 12 tests in 2657.038s

OK


Thanks,

Gaurav Aradhye

Re: Travis failures

[Rohit Yadav]

On 17-Sep-2014, at 2:58 pm, Daan Hoogland  wrote:
> The checkin by Min was not the problem (Edisons was on his own branch)
> Rohit showed me the travis run on this commit in his travis account. It was
> green.
>
> So our travis setup is not perfect yet :(

We have a hypothesis that all the apache repos are kicking jobs at Travis and 
competing for resources etc which is causing incorrect build results. Ian has 
sent an email to verify that and to get more resources for the repo.

I’ve a mirror with travis and you can see it’s all green:
https://travis-ci.org/shapeblue/cloudstack/builds

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +41 779015219 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab



Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

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

Re: [DISCUSS] CloudStack Future

[John Kinsella]

Ah, from that POV. Gotchya. I think also making it easier to develop the UI 
would help. Feels like a big black box to me, and probably to others…


On Sep 16, 2014, at 10:37 PM, Rohit Yadav 
mailto:rohit.ya...@shapeblue.com>> wrote:

So, most of the developers of CloudStack don’t use it as a user. If we dogfood, 
we make try to make it more user friendly and improve its UX over time.

Build failed in Jenkins: build-master #1638

[jenkins]

See 

Changes:

[Rohit Yadav] CID-1192805: Remove dead local store from 
OvsNetworkTopologyGuruImpl

[Rohit Yadav] CID-1192811: Remove dead local store from VolumeJoinDaoImpl

[Rohit Yadav] CID-1192812: Remove dead code from DataCenterJoinDaoImpl

[Rohit Yadav] CID-1199715: Remove dead code from LibvirtStorageAdaptor

--
[...truncated 1244 lines...]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

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

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


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

Results :

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

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

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-framework-jobs ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-framework-jobs ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
cloud-framework-jobs ---
[INFO] Compiling 33 source files to 

[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-framework-jobs ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 4 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
cloud-framework-jobs ---
[INFO] Compiling 4 source files to 

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


---
 T E S T S
---

Results :

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

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

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

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-engine-components-api ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-engine-components-api ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] 

Build failed in Jenkins: simulator-singlerun #387

[jenkins]

See 

Changes:

[Rohit Yadav] CID-1233085: Fix potential NPE in AccountManagerImpl from 
VpcManagerImpl

[Rohit Yadav] CID-1192805: Remove dead local store from 
OvsNetworkTopologyGuruImpl

[Rohit Yadav] CID-1192811: Remove dead local store from VolumeJoinDaoImpl

[Rohit Yadav] CID-1192812: Remove dead code from DataCenterJoinDaoImpl

[Rohit Yadav] CID-1199715: Remove dead code from LibvirtStorageAdaptor

--
[...truncated 1626 lines...]
---

Results :

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

[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ cloud-framework-jobs ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ 
cloud-framework-jobs ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
cloud-framework-jobs ---
[INFO] Installing 

 to 
/var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-framework-jobs/4.5.0-SNAPSHOT/cloud-framework-jobs-4.5.0-SNAPSHOT.jar
[INFO] Installing 

 to 
/var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-framework-jobs/4.5.0-SNAPSHOT/cloud-framework-jobs-4.5.0-SNAPSHOT.pom
[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Cloud Engine Internal Components API 
4.5.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
cloud-engine-components-api ---
[INFO] Deleting 

 (includes = [**/*], excludes = [])
[INFO] Deleting 

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

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-engine-components-api ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-engine-components-api ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
cloud-engine-components-api ---
[INFO] Compiling 31 source files to 

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

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


---
 T E S T S
---

Results :

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

[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ cloud-engine-components-api 
---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ 
cloud-engine-components-api ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
cloud-engine-components-api ---
[INFO] Installing 

 to 
/var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-engine-components-api/4.5.0-SNAPSHOT/cloud-engine-components-api-4.5.0-SNAPSHOT.jar
[INFO] Installing 

 to 
/var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-engine-components-api/4

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

[jenkins]

See 

Re: Travis failures

[sebgoa]

On Sep 17, 2014, at 3:28 PM, Rohit Yadav  wrote:

> 
> On 17-Sep-2014, at 2:58 pm, Daan Hoogland  wrote:
>> The checkin by Min was not the problem (Edisons was on his own branch)
>> Rohit showed me the travis run on this commit in his travis account. It was
>> green.
>> 
>> So our travis setup is not perfect yet :(
> 
> We have a hypothesis that all the apache repos are kicking jobs at Travis and 
> competing for resources etc which is causing incorrect build results. Ian has 
> sent an email to verify that and to get more resources for the repo.
> 
> I’ve a mirror with travis and you can see it’s all green:
> https://travis-ci.org/shapeblue/cloudstack/builds

Interesting, thanks for sharing.



> 
> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +41 779015219 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
> 
> 
> 
> Find out more about ShapeBlue and our range of CloudStack related services
> 
> IaaS Cloud Design & Build
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Infrastructure 
> Support
> CloudStack Bootcamp Training 
> Courses
> 
> This email and any attachments to it may be confidential and are intended 
> solely for the use of the individual to whom it is addressed. Any views or 
> opinions expressed are solely those of the author and do not necessarily 
> represent those of Shape Blue Ltd or related companies. If you are not the 
> intended recipient of this email, you must neither take any action based upon 
> its contents, nor copy or show it to anyone. Please contact the sender if you 
> believe you have received this email in error. Shape Blue Ltd is a company 
> incorporated in England & Wales. ShapeBlue Services India LLP is a company 
> incorporated in India and is operated under license from Shape Blue Ltd. 
> Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
> operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
> registered by The Republic of South Africa and is traded under license from 
> Shape Blue Ltd. ShapeBlue is a registered trademark.

RE: [CCCEU14] hackathons

[Stephen Turner]

Shall do, but it looks like I don't have wiki edit rights yet. Could you grant 
them to me? stephen.tur...@citrix.com. Thanks.

-- 
Stephen Turner


-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] 
Sent: 17 September 2014 14:01
To: dev
Subject: Re: [CCCEU14] hackathons

We are going to have a launch for organising them. So please add your ideas and 
find people to join in. I will extend the table on the wiki to include timeslot 
and leaf room for extra 'contestants' to add their name.

On Wed, Sep 17, 2014 at 2:49 PM, Rafael Weingartner < 
rafaelweingart...@gmail.com> wrote:

> Are we going to have hackathons in ccceu in Hungary in November the 19th?
>
> On Wed, Sep 17, 2014 at 8:29 AM, Stephen Turner 
>  >
> wrote:
>
> > Thanks for the pointer, Daan. I'm interested in the API, but when 
> > are we planning to do this? On the day before the conference starts?
> >
> > --
> > Stephen Turner
> >
> >
> > -Original Message-
> > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> > Sent: 17 September 2014 10:26
> > To: dev
> > Cc: market...@cloudstack.apache.org
> > Subject: [CCCEU14] hackathons
> >
> > H devs,
> >
> > In the schedule for ccceu there is no hackathon day. The reason is 
> > that hackathons have been decreasing in popularity and success. What 
> > we do
> have
> > is;
> >
> > 1. a room for getting together and working on things 2. a planning 
> > page for hackathons, which we might hence forth give another name at [1].
> >
> > At the page, there are 7 subjects there but only one of them has 
> > more
> then
> > one attendee. Please use dev@cloudstack and this page to plan your 
> > hackathon/Birds of a feather/workshop/discussion and design sessions.
> Hope
> > to see you all in Budapest and work with you all.
> >
> > [1]
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Coll
> aboration+Conference+EU
> >
> > --
> > Daan
> >
>
>
>
> --
> Rafael Weingärtner
>



--
Daan

Re: Review Request 24892: passwd_server attempts to start but terminates with the exit code 137

[Sheng Yang]

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

Ship it!


Ship It!

- Sheng Yang


On Aug. 20, 2014, 2:25 p.m., bharat kumar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/24892/
> ---
> 
> (Updated Aug. 20, 2014, 2:25 p.m.)
> 
> 
> Review request for cloudstack and Sheng Yang.
> 
> 
> Bugs: CLOUDSTACK-7376
> https://issues.apache.org/jira/browse/CLOUDSTACK-7376
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> https://issues.apache.org/jira/browse/CLOUDSTACK-7376
> passwd_server attempts to start but terminates with the exit code 137
> 
> 
> Diffs
> -
> 
>   systemvm/patches/debian/config/opt/cloud/bin/passwd_server 0f4a772 
> 
> Diff: https://reviews.apache.org/r/24892/diff/
> 
> 
> Testing
> ---
> 
> I was able to reproduce this in the older version but not on master.
> but iam putting this patch anyway as this will not effect the regular runs.
> 
> 
> Thanks,
> 
> bharat kumar
> 
>

Re: Fwd: Re: Upgrade to 4.3.1

[ilya musayev]

Has this worked for you in 4.3.0, before the upgrade to 4.3.1?

I've briefly looked through change log from 4.3.0 to 4.3.1, i dont see 
any changes related to console - but this check was very brief.


Regards
ilya
On 9/17/14, 1:42 AM, Mārtiņš Jakubovičs wrote:

Hello,

I installed fresh CS 4.3.1 and it also don't use 
"consoleproxy.url.domain" value.


This is in console proxy, source:

v-2-VMsrc="https://.realhostip.com/ajax?token=1cttHTopOwqQbK_Q9gYmoYMOnzK9fcHUlUv3q6rIUsyVdY3hU7Kmwa7A9RxTz7ZuG4MherlIa0tllGr5XWez73GVyP19iBqxP-c5eCttLrUAotMhMu3GLqPDdEzB2JmVFLZp2DLMBiiAYcdtnNvRl6by-V065VBXyZ729Awd-dnGWE1dNebljz78M5RmNWJXy7HsmrWalWaJyUoI2vMYjBc7FEDksGmCGS_akmN_rPmKH6CdPEyHhNAcvEfb0EiaFFMSA2NUZ9sDfhmmapVxGc1_mHWNWyTqq0WxMfIt6y5CvjmOSUutcagll5sm_SbdUcp7NHB_xZmNAx7yWKnyiMm9XMnYTPnqfrJe8YSSNc481oCgPgPBiQOwbwaoOqtR6PZLDwTPIT6ULkDpy-nL9eVX-lPUJByWzAmgDOGN3ZxV7gwZbvPJGn8cF65Sa5Cb8WN97mYqNqgFZlMChx5ADxNaBYxvWKHfATQoo6utXRg";> 



When I set in url correct domain my-ip-add.domain.com, than console 
works, example like this:


https://11-111-111-11.domain.com/ajax?token=1cttHTopOwqQbK_Q9gYmoYMOnzK9fcHUlUv3q6rIUsyVdY3hU7Kmwa7A9RxTz7ZuG4MherlIa0tllGr5XWez73GVyP19iBqxP-c5eCttLrUAotMhMu3GLqPDdEzB2JmVFLZp2DLMBiiAYcdtnNvRl6by-V065VBXyZ729Awd-dnGWE1dNebljz78M5RmNWJXy7HsmrWalWaJyUoI2vMYjBc7FEDksGmCGS_akmN_rPmKH6CdPEyHhNAcvEfb0EiaFFMSA2NUZ9sDfhmmapVxGc1_mHWNWyTqq0WxMfIt6y5CvjmOSUutcagll5sm_SbdUcp7NHB_xZmNAx7yWKnyiMm9XMnYTPnqfrJe8YSSNc481oCgPgPBiQOwbwaoOqtR6PZLDwTPIT6ULkDpy-nL9eVX-lPUJByWzAmgDOGN3ZxV7gwZbvPJGn8cF65Sa5Cb8WN97mYqNqgFZlMChx5ADxNaBYxvWKHfATQoo6utXRg 




 Forwarded Message 
Subject: Re: Upgrade to 4.3.1
Date: Wed, 17 Sep 2014 09:05:21 +0300
From: Mārtiņš Jakubovičs 
To: us...@cloudstack.apache.org



Hello Ilya,

Thanks for response, I upgraded from 4.3.0 to 4.3.1.

On 2014.09.17. 03:34, ilya musayev wrote:

Mārtiņš

If you dont get a response here, please post on dev. I'll try this out
shortly in my env, what version did you upgrade from?

Regards
ilya
On 9/16/14, 6:07 AM, Mārtiņš Jakubovičs wrote:

Hello,

In CentOS 6.5 today I discovered that is available update for CS 4.3.
I installed it but after management service restart "
consoleproxy.url.domain" value stopped to work. When I launch console
proxy, it connect to ".realhostip.com" domain in a way to connect my
real domain. When I clean this value, console proxy connects to IP.
After entering any other value it connects to ".realhostip.com"
anyway. How I can solve this?

Thanks.

Review Request 25749: Fixed CLOUDSTACK-7573: ISO Guest OS Change

[Chandan Purushothama]

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

Review request for cloudstack, Amogh Vasekar, sangeetha hariharan, and sanjeev 
n.


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


Repository: cloudstack-git


Description
---

The Bug results in VM deployment failure across different configurations. 
Correcting the guest OS Type resolves the issue


Diffs
-

  tools/marvin/marvin/config/test_data.py 9b2aee7 

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


Testing
---

I tested manually on a different setup.


Thanks,

Chandan Purushothama

Re: Review Request 25685: Fixed the test_usage.py script bug - CLOUDSTACK-7555

[Chandan Purushothama]

> On Sept. 16, 2014, 11:25 a.m., SrikanteswaraRao Talluri wrote:
> > test/integration/component/test_usage.py, line 748
> > 
> >
> > Please change this to self.account.name and self.account.domainid

Talluri,
account is a class attribute. It is not conventionally correct to refer a class 
attribute using object reference(self). Hence I intentionally referenced the 
account via its Class name,

Thank you,
Chandan.


- Chandan


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


On Sept. 16, 2014, 6:46 a.m., Chandan Purushothama wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25685/
> ---
> 
> (Updated Sept. 16, 2014, 6:46 a.m.)
> 
> 
> Review request for cloudstack, sangeetha hariharan, sanjeev n, and 
> SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-7555
> https://issues.apache.org/jira/browse/CLOUDSTACK-7555
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> 
> TestTemplateUsage.test_01_template_usage fails with the following error 
> message & Stack Trace
> 
> Stacktrace
> 
>   File "/usr/lib/python2.7/unittest/case.py", line 332, in run
> testMethod()
>   File "/root/cloudstack/test/integration/component/test_usage.py", line 802, 
> in test_01_template_usage
> "Check TEMPLATE.CREATE event in events table"
>   File "/usr/lib/python2.7/unittest/case.py", line 516, in assertEqual
> assertion_func(first, second, msg=msg)
>   File "/usr/lib/python2.7/unittest/case.py", line 509, in _baseAssertEqual
> raise self.failureException(msg)
> 'Check TEMPLATE.CREATE event in events table\n
> 
> This is because the Template is being created as admin and it belongs to the 
> admin account. The template should belong to the Regular User in order to 
> check for the TEMPLATE.CREATE Event.
> 
> Fixed the script such that the Template now belongs to the regular account.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_usage.py e99bb81 
> 
> Diff: https://reviews.apache.org/r/25685/diff/
> 
> 
> Testing
> ---
> 
> No testing is done.
> 
> 
> Thanks,
> 
> Chandan Purushothama
> 
>

RE: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Ritu Sabharwal]

Hi Mike,

I updated the master just now and tried the setup. I see the same error on same 
line number.

Thanks & Regards,
Ritu S.

-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
Sent: Tuesday, September 16, 2014 8:32 PM
To: dev@cloudstack.apache.org
Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with 
Vmware setup with CS server

Can you tell us what commit SHA you are running under?

I just updated master and line 2094 in VmwareResource is the following:

String[] diskChain = diskInfo.getDiskChain();

The only candidate for a NullPointerException there is diskInfo; however, the 
previous line would have caught this as it looks like this:

assert (diskInfo != null);

That being the case, I'm curious what commit SHA you saw this on?

Thanks!

On Tue, Sep 16, 2014 at 5:22 PM, Ritu Sabharwal 
wrote:

> Hi Sateesh, Koushik,
>
> I am setting up Vmware Cluster with CS (master) and seeing errors. 
> ilya was helping me for this setup and figured out this error.
>
> The System VMs(Secondary Stogare VM and Console Proxy VM) are not 
> coming up properly. The system vms are reconfiguring and destroying 
> again and again in cycle.
>
> I have used Vmware Vsphere 5.1 SDK for building CS.
>
> The error logs give this error:
>
> 2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource] 
> (DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd: 
> StartCommand) StartCommand failed due to Exception: 
> java.lang.NullPointerException
> Message: null
>
> java.lang.NullPointerException
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.postDiskConfigBeforeStart(VmwareResource.java:2094)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1685)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:448)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:294)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
>
> Please help to resolve this issue.
>
> Thanks & Regards,
> Ritu S.
>
>


--
*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 25685: Fixed the test_usage.py script bug - CLOUDSTACK-7555

[Chandan Purushothama]

> On Sept. 16, 2014, 11:26 a.m., SrikanteswaraRao Talluri wrote:
> > It is good to add test results to the patch.

Agreed


- Chandan


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


On Sept. 16, 2014, 6:46 a.m., Chandan Purushothama wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25685/
> ---
> 
> (Updated Sept. 16, 2014, 6:46 a.m.)
> 
> 
> Review request for cloudstack, sangeetha hariharan, sanjeev n, and 
> SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-7555
> https://issues.apache.org/jira/browse/CLOUDSTACK-7555
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> 
> TestTemplateUsage.test_01_template_usage fails with the following error 
> message & Stack Trace
> 
> Stacktrace
> 
>   File "/usr/lib/python2.7/unittest/case.py", line 332, in run
> testMethod()
>   File "/root/cloudstack/test/integration/component/test_usage.py", line 802, 
> in test_01_template_usage
> "Check TEMPLATE.CREATE event in events table"
>   File "/usr/lib/python2.7/unittest/case.py", line 516, in assertEqual
> assertion_func(first, second, msg=msg)
>   File "/usr/lib/python2.7/unittest/case.py", line 509, in _baseAssertEqual
> raise self.failureException(msg)
> 'Check TEMPLATE.CREATE event in events table\n
> 
> This is because the Template is being created as admin and it belongs to the 
> admin account. The template should belong to the Regular User in order to 
> check for the TEMPLATE.CREATE Event.
> 
> Fixed the script such that the Template now belongs to the regular account.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_usage.py e99bb81 
> 
> Diff: https://reviews.apache.org/r/25685/diff/
> 
> 
> Testing
> ---
> 
> No testing is done.
> 
> 
> Thanks,
> 
> Chandan Purushothama
> 
>

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Marcus]

Aren't asserts ignored by default? I think we had an issue with asserts in
the past, and I believe at the time the default config had asserts disabled.


On Wed, Sep 17, 2014 at 1:35 PM, Ritu Sabharwal 
wrote:

> Hi Mike,
>
> I updated the master just now and tried the setup. I see the same error on
> same line number.
>
> Thanks & Regards,
> Ritu S.
>
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Tuesday, September 16, 2014 8:32 PM
> To: dev@cloudstack.apache.org
> Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
> with Vmware setup with CS server
>
> Can you tell us what commit SHA you are running under?
>
> I just updated master and line 2094 in VmwareResource is the following:
>
> String[] diskChain = diskInfo.getDiskChain();
>
> The only candidate for a NullPointerException there is diskInfo; however,
> the previous line would have caught this as it looks like this:
>
> assert (diskInfo != null);
>
> That being the case, I'm curious what commit SHA you saw this on?
>
> Thanks!
>
> On Tue, Sep 16, 2014 at 5:22 PM, Ritu Sabharwal 
> wrote:
>
> > Hi Sateesh, Koushik,
> >
> > I am setting up Vmware Cluster with CS (master) and seeing errors.
> > ilya was helping me for this setup and figured out this error.
> >
> > The System VMs(Secondary Stogare VM and Console Proxy VM) are not
> > coming up properly. The system vms are reconfiguring and destroying
> > again and again in cycle.
> >
> > I have used Vmware Vsphere 5.1 SDK for building CS.
> >
> > The error logs give this error:
> >
> > 2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource]
> > (DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd:
> > StartCommand) StartCommand failed due to Exception:
> > java.lang.NullPointerException
> > Message: null
> >
> > java.lang.NullPointerException
> > at
> >
> com.cloud.hypervisor.vmware.resource.VmwareResource.postDiskConfigBeforeStart(VmwareResource.java:2094)
> > at
> >
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1685)
> > at
> >
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:448)
> > at
> >
> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:294)
> > at
> >
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> > at
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> > at
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> > at
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> > at
> >
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> > at
> > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> > at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> > at
> >
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> > at
> >
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > at java.lang.Thread.run(Thread.java:744)
> >
> > Please help to resolve this issue.
> >
> > Thanks & Regards,
> > Ritu S.
> >
> >
>
>
> --
> *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: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

You're right, Marcus. Now that I think about it, asserts are ignored by
default.

On Wed, Sep 17, 2014 at 1:59 PM, Marcus  wrote:

> Aren't asserts ignored by default? I think we had an issue with asserts in
> the past, and I believe at the time the default config had asserts
> disabled.
>
>
> On Wed, Sep 17, 2014 at 1:35 PM, Ritu Sabharwal 
> wrote:
>
> > Hi Mike,
> >
> > I updated the master just now and tried the setup. I see the same error
> on
> > same line number.
> >
> > Thanks & Regards,
> > Ritu S.
> >
> > -Original Message-
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > Sent: Tuesday, September 16, 2014 8:32 PM
> > To: dev@cloudstack.apache.org
> > Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
> > Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
> > with Vmware setup with CS server
> >
> > Can you tell us what commit SHA you are running under?
> >
> > I just updated master and line 2094 in VmwareResource is the following:
> >
> > String[] diskChain = diskInfo.getDiskChain();
> >
> > The only candidate for a NullPointerException there is diskInfo; however,
> > the previous line would have caught this as it looks like this:
> >
> > assert (diskInfo != null);
> >
> > That being the case, I'm curious what commit SHA you saw this on?
> >
> > Thanks!
> >
> > On Tue, Sep 16, 2014 at 5:22 PM, Ritu Sabharwal 
> > wrote:
> >
> > > Hi Sateesh, Koushik,
> > >
> > > I am setting up Vmware Cluster with CS (master) and seeing errors.
> > > ilya was helping me for this setup and figured out this error.
> > >
> > > The System VMs(Secondary Stogare VM and Console Proxy VM) are not
> > > coming up properly. The system vms are reconfiguring and destroying
> > > again and again in cycle.
> > >
> > > I have used Vmware Vsphere 5.1 SDK for building CS.
> > >
> > > The error logs give this error:
> > >
> > > 2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource]
> > > (DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd:
> > > StartCommand) StartCommand failed due to Exception:
> > > java.lang.NullPointerException
> > > Message: null
> > >
> > > java.lang.NullPointerException
> > > at
> > >
> >
> com.cloud.hypervisor.vmware.resource.VmwareResource.postDiskConfigBeforeStart(VmwareResource.java:2094)
> > > at
> > >
> >
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1685)
> > > at
> > >
> >
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:448)
> > > at
> > >
> >
> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:294)
> > > at
> > >
> >
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> > > at
> > >
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> > > at
> > >
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> > > at
> > >
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> > > at
> > >
> >
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> > > at
> > > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> > > at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> > > at
> > >
> >
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> > > at
> > >
> >
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> > > at
> > >
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> > > at
> > >
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > > at java.lang.Thread.run(Thread.java:744)
> > >
> > > Please help to resolve this issue.
> > >
> > > Thanks & Regards,
> > > Ritu S.
> > >
> > >
> >
> >
> > --
> > *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 24090: Externalized the hard-coded strings from JavaScript files to resource bundles.

[Brian Federle]

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

Ship it!


Ship It!

- Brian Federle


On Sept. 12, 2014, 9:53 a.m., Vetrivel Chinnasamy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/24090/
> ---
> 
> (Updated Sept. 12, 2014, 9:53 a.m.)
> 
> 
> Review request for cloudstack, Brian Federle and Jessica Wang.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Externalized the hard-coded strings from JavaScript files to resource 
> bundles. Updated the dictionary.jsp file accordingly. Also got the 
> externalized strings translated in JA & SC.
> 
> 
> Diffs
> -
> 
>   client/WEB-INF/classes/resources/messages.properties 4655973 
>   client/WEB-INF/classes/resources/messages_ja_JP.properties ed6a1b1 
>   client/WEB-INF/classes/resources/messages_zh_CN.properties 2c497bc 
>   ui/dictionary.jsp 0102144 
>   ui/dictionary2.jsp PRE-CREATION 
>   ui/index.jsp 48afa6a 
>   ui/modules/vnmcAsa1000v/vnmcAsa1000v.js 621c52a 
>   ui/modules/vnmcNetworkProvider/vnmcNetworkProvider.js c9295a3 
>   ui/scripts/accounts.js cc4624a 
>   ui/scripts/autoscaler.js c8963fd 
>   ui/scripts/cloudStack.js 38cf501 
>   ui/scripts/configuration.js a70c672 
>   ui/scripts/domains.js 488382e 
>   ui/scripts/events.js 2731cb6 
>   ui/scripts/instances.js 4d536e3 
>   ui/scripts/lbStickyPolicy.js 16995f6 
>   ui/scripts/network.js 02dd269 
>   ui/scripts/projects.js 53b7964 
>   ui/scripts/regions.js 368c1bf 
>   ui/scripts/sharedFunctions.js 41f5d3a 
>   ui/scripts/storage.js f4ab6e1 
>   ui/scripts/system.js 54aafe2 
>   ui/scripts/templates.js 6dcd6da 
>   ui/scripts/ui-custom/autoscaler.js 0aa6c77 
>   ui/scripts/ui-custom/healthCheck.js 4e10f1c 
>   ui/scripts/ui-custom/physicalResources.js 110945e 
>   ui/scripts/ui-custom/regions.js 986e009 
>   ui/scripts/ui-custom/zoneWizard.js f3a1aae 
>   ui/scripts/ui/dialog.js 6c77924 
>   ui/scripts/ui/widgets/listView.js c7b4a4d 
>   ui/scripts/ui/widgets/multiEdit.js 47e5f43 
>   ui/scripts/vpc.js 786cb26 
>   ui/scripts/zoneWizard.js 4498534 
> 
> Diff: https://reviews.apache.org/r/24090/diff/
> 
> 
> Testing
> ---
> 
> Tested by replacing the modified javascript , dictionary.jsp and properties 
> files.
> 
> 
> Thanks,
> 
> Vetrivel Chinnasamy
> 
>

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

I can set up a VMware cluster hopefully later tonight and see if I can
reproduce this.

Off hand I'm not sure why the "managed" logic would be causing this, though.

In your situation, "managed" should be false and the "standard" logic
should run.

Is this where I can get the latest system template for VMware?

http://jenkins.buildacloud.org/job/build-systemvm64-master/

I see an OVA and a VMDK. Which one do I use for seeding secondary storage
for VMware (it's been a while since I've used VMware a system template)?

Thanks!

On Wed, Sep 17, 2014 at 2:53 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> You're right, Marcus. Now that I think about it, asserts are ignored by
> default.
>
> On Wed, Sep 17, 2014 at 1:59 PM, Marcus  wrote:
>
>> Aren't asserts ignored by default? I think we had an issue with asserts in
>> the past, and I believe at the time the default config had asserts
>> disabled.
>>
>>
>> On Wed, Sep 17, 2014 at 1:35 PM, Ritu Sabharwal 
>> wrote:
>>
>> > Hi Mike,
>> >
>> > I updated the master just now and tried the setup. I see the same error
>> on
>> > same line number.
>> >
>> > Thanks & Regards,
>> > Ritu S.
>> >
>> > -Original Message-
>> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> > Sent: Tuesday, September 16, 2014 8:32 PM
>> > To: dev@cloudstack.apache.org
>> > Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
>> > Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
>> > with Vmware setup with CS server
>> >
>> > Can you tell us what commit SHA you are running under?
>> >
>> > I just updated master and line 2094 in VmwareResource is the following:
>> >
>> > String[] diskChain = diskInfo.getDiskChain();
>> >
>> > The only candidate for a NullPointerException there is diskInfo;
>> however,
>> > the previous line would have caught this as it looks like this:
>> >
>> > assert (diskInfo != null);
>> >
>> > That being the case, I'm curious what commit SHA you saw this on?
>> >
>> > Thanks!
>> >
>> > On Tue, Sep 16, 2014 at 5:22 PM, Ritu Sabharwal 
>> > wrote:
>> >
>> > > Hi Sateesh, Koushik,
>> > >
>> > > I am setting up Vmware Cluster with CS (master) and seeing errors.
>> > > ilya was helping me for this setup and figured out this error.
>> > >
>> > > The System VMs(Secondary Stogare VM and Console Proxy VM) are not
>> > > coming up properly. The system vms are reconfiguring and destroying
>> > > again and again in cycle.
>> > >
>> > > I have used Vmware Vsphere 5.1 SDK for building CS.
>> > >
>> > > The error logs give this error:
>> > >
>> > > 2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource]
>> > > (DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd:
>> > > StartCommand) StartCommand failed due to Exception:
>> > > java.lang.NullPointerException
>> > > Message: null
>> > >
>> > > java.lang.NullPointerException
>> > > at
>> > >
>> >
>> com.cloud.hypervisor.vmware.resource.VmwareResource.postDiskConfigBeforeStart(VmwareResource.java:2094)
>> > > at
>> > >
>> >
>> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1685)
>> > > at
>> > >
>> >
>> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:448)
>> > > at
>> > >
>> >
>> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:294)
>> > > at
>> > >
>> >
>> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
>> > > at
>> > >
>> >
>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
>> > > at
>> > >
>> >
>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
>> > > at
>> > >
>> >
>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
>> > > at
>> > >
>> >
>> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
>> > > at
>> > >
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>> > > at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>> > > at
>> > >
>> >
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>> > > at
>> > >
>> >
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>> > > at
>> > >
>> >
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> > > at
>> > >
>> >
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> > > at java.lang.Thread.run(Thread.java:744)
>> > >
>> > > Please help to resolve this issue.
>> > >
>> > > Thanks & Regards,
>> > > Ritu S.
>> > >
>> > >
>> >
>> >
>> > --
>> > *Mike Tutkowski*
>> > *Senior CloudStack Developer

Build failed in Jenkins: build-master-simulator #686

[jenkins]

See 

--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-ac1 
(cloudstack-buildslave-centos6) in workspace 

Fetching changes from the remote Git repository
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
ERROR: Timeout after 400 minutes
FATAL: Failed to fetch from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
hudson.plugins.git.GitException: Failed to fetch from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:625)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:847)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:872)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1320)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518)
at hudson.model.Run.execute(Run.java:1688)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags 
--progress https://git-wip-us.apache.org/repos/asf/cloudstack.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: error: RPC failed; result=52, HTTP code = 100
error: fetch-pack died of signal 15

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1086)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:968)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:71)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:197)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:701)

Jenkins build is back to normal : build-master-simulator #687

[jenkins]

See 

RE: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Ritu Sabharwal]

Hi Mike,

Sure, it will help to see if you can reproduce the error.

I used the system vm template :  
http://cloudstack.apt-get.eu/systemvm/systemvm64template-2014-01-14-master-vmware.ova
 but http://jenkins.buildacloud.org/job/build-systemvm64-master/  is latest and 
OVA is to be used.


Thanks & Regards,
Ritu S.

-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
Sent: Wednesday, September 17, 2014 2:17 PM
To: dev@cloudstack.apache.org
Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with 
Vmware setup with CS server

I can set up a VMware cluster hopefully later tonight and see if I can 
reproduce this.

Off hand I'm not sure why the "managed" logic would be causing this, though.

In your situation, "managed" should be false and the "standard" logic should 
run.

Is this where I can get the latest system template for VMware?

http://jenkins.buildacloud.org/job/build-systemvm64-master/

I see an OVA and a VMDK. Which one do I use for seeding secondary storage for 
VMware (it's been a while since I've used VMware a system template)?

Thanks!

On Wed, Sep 17, 2014 at 2:53 PM, Mike Tutkowski < mike.tutkow...@solidfire.com> 
wrote:

> You're right, Marcus. Now that I think about it, asserts are ignored 
> by default.
>
> On Wed, Sep 17, 2014 at 1:59 PM, Marcus  wrote:
>
>> Aren't asserts ignored by default? I think we had an issue with 
>> asserts in the past, and I believe at the time the default config had 
>> asserts disabled.
>>
>>
>> On Wed, Sep 17, 2014 at 1:35 PM, Ritu Sabharwal 
>> 
>> wrote:
>>
>> > Hi Mike,
>> >
>> > I updated the master just now and tried the setup. I see the same 
>> > error
>> on
>> > same line number.
>> >
>> > Thanks & Regards,
>> > Ritu S.
>> >
>> > -Original Message-
>> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> > Sent: Tuesday, September 16, 2014 8:32 PM
>> > To: dev@cloudstack.apache.org
>> > Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
>> > Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System 
>> > VMs with Vmware setup with CS server
>> >
>> > Can you tell us what commit SHA you are running under?
>> >
>> > I just updated master and line 2094 in VmwareResource is the following:
>> >
>> > String[] diskChain = diskInfo.getDiskChain();
>> >
>> > The only candidate for a NullPointerException there is diskInfo;
>> however,
>> > the previous line would have caught this as it looks like this:
>> >
>> > assert (diskInfo != null);
>> >
>> > That being the case, I'm curious what commit SHA you saw this on?
>> >
>> > Thanks!
>> >
>> > On Tue, Sep 16, 2014 at 5:22 PM, Ritu Sabharwal 
>> > 
>> > wrote:
>> >
>> > > Hi Sateesh, Koushik,
>> > >
>> > > I am setting up Vmware Cluster with CS (master) and seeing errors.
>> > > ilya was helping me for this setup and figured out this error.
>> > >
>> > > The System VMs(Secondary Stogare VM and Console Proxy VM) are not 
>> > > coming up properly. The system vms are reconfiguring and 
>> > > destroying again and again in cycle.
>> > >
>> > > I have used Vmware Vsphere 5.1 SDK for building CS.
>> > >
>> > > The error logs give this error:
>> > >
>> > > 2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource] 
>> > > (DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd:
>> > > StartCommand) StartCommand failed due to Exception:
>> > > java.lang.NullPointerException
>> > > Message: null
>> > >
>> > > java.lang.NullPointerException
>> > > at
>> > >
>> >
>> com.cloud.hypervisor.vmware.resource.VmwareResource.postDiskConfigBef
>> oreStart(VmwareResource.java:2094)
>> > > at
>> > >
>> >
>> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareRes
>> ource.java:1685)
>> > > at
>> > >
>> >
>> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(Vm
>> wareResource.java:448)
>> > > at
>> > >
>> >
>> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAg
>> entAttache.java:294)
>> > > at
>> > >
>> >
>> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(Ma
>> nagedContextRunnable.java:49)
>> > > at
>> > >
>> >
>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.ca
>> ll(DefaultManagedContext.java:56)
>> > > at
>> > >
>> >
>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.call
>> WithContext(DefaultManagedContext.java:103)
>> > > at
>> > >
>> >
>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runW
>> ithContext(DefaultManagedContext.java:53)
>> > > at
>> > >
>> >
>> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(Mana
>> gedContextRunnable.java:46)
>> > > at
>> > >
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:47
>> 1)
>> > > at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>> > > at
>> > >
>> >
>> java.util

Re: Upgrade to 4.3.1

[Amogh Vasekar]

Hi,

Please set the value to "*.yourdomain.com" (note the asterisk)
The management server needs a restarted when you change the global config
value.
If this was a fresh install - by default console proxy will run on HTTP.
When you switch from HTTP to HTTPS or vice versa, you need to destroy the
old console proxy VM so that it may configure correctly and open right
port.

HTH
Amogh


On 9/17/14 10:56 AM, "ilya musayev"  wrote:

>Has this worked for you in 4.3.0, before the upgrade to 4.3.1?
>
>I've briefly looked through change log from 4.3.0 to 4.3.1, i dont see
>any changes related to console - but this check was very brief.
>
>Regards
>ilya
>On 9/17/14, 1:42 AM, M?rti?š Jakubovičs wrote:
>> Hello,
>>
>> I installed fresh CS 4.3.1 and it also don't use
>> "consoleproxy.url.domain" value.
>>
>> This is in console proxy, source:
>>
>> v-2-VM> 
>>src="https://.realhostip.com/ajax?token=1cttHTopOwqQbK_Q9gYmoYMOnzK9fcHUl
>>Uv3q6rIUsyVdY3hU7Kmwa7A9RxTz7ZuG4MherlIa0tllGr5XWez73GVyP19iBqxP-c5eCttLr
>>UAotMhMu3GLqPDdEzB2JmVFLZp2DLMBiiAYcdtnNvRl6by-V065VBXyZ729Awd-dnGWE1dNeb
>>ljz78M5RmNWJXy7HsmrWalWaJyUoI2vMYjBc7FEDksGmCGS_akmN_rPmKH6CdPEyHhNAcvEfb
>>0EiaFFMSA2NUZ9sDfhmmapVxGc1_mHWNWyTqq0WxMfIt6y5CvjmOSUutcagll5sm_SbdUcp7N
>>HB_xZmNAx7yWKnyiMm9XMnYTPnqfrJe8YSSNc481oCgPgPBiQOwbwaoOqtR6PZLDwTPIT6ULk
>>Dpy-nL9eVX-lPUJByWzAmgDOGN3ZxV7gwZbvPJGn8cF65Sa5Cb8WN97mYqNqgFZlMChx5ADxN
>>aBYxvWKHfATQoo6utXRg">
>>
>>
>> When I set in url correct domain my-ip-add.domain.com, than console
>> works, example like this:
>>
>> 
>>https://11-111-111-11.domain.com/ajax?token=1cttHTopOwqQbK_Q9gYmoYMOnzK9f
>>cHUlUv3q6rIUsyVdY3hU7Kmwa7A9RxTz7ZuG4MherlIa0tllGr5XWez73GVyP19iBqxP-c5eC
>>ttLrUAotMhMu3GLqPDdEzB2JmVFLZp2DLMBiiAYcdtnNvRl6by-V065VBXyZ729Awd-dnGWE1
>>dNebljz78M5RmNWJXy7HsmrWalWaJyUoI2vMYjBc7FEDksGmCGS_akmN_rPmKH6CdPEyHhNAc
>>vEfb0EiaFFMSA2NUZ9sDfhmmapVxGc1_mHWNWyTqq0WxMfIt6y5CvjmOSUutcagll5sm_SbdU
>>cp7NHB_xZmNAx7yWKnyiMm9XMnYTPnqfrJe8YSSNc481oCgPgPBiQOwbwaoOqtR6PZLDwTPIT
>>6ULkDpy-nL9eVX-lPUJByWzAmgDOGN3ZxV7gwZbvPJGn8cF65Sa5Cb8WN97mYqNqgFZlMChx5
>>ADxNaBYxvWKHfATQoo6utXRg
>>
>>
>>
>>  Forwarded Message 
>> Subject: Re: Upgrade to 4.3.1
>> Date: Wed, 17 Sep 2014 09:05:21 +0300
>> From: M?rti?š Jakubovičs 
>> To: us...@cloudstack.apache.org
>>
>>
>>
>> Hello Ilya,
>>
>> Thanks for response, I upgraded from 4.3.0 to 4.3.1.
>>
>> On 2014.09.17. 03:34, ilya musayev wrote:
>>> M?rti?š
>>>
>>> If you dont get a response here, please post on dev. I'll try this out
>>> shortly in my env, what version did you upgrade from?
>>>
>>> Regards
>>> ilya
>>> On 9/16/14, 6:07 AM, M?rti?š Jakubovičs wrote:
 Hello,

 In CentOS 6.5 today I discovered that is available update for CS 4.3.
 I installed it but after management service restart "
 consoleproxy.url.domain" value stopped to work. When I launch console
 proxy, it connect to ".realhostip.com" domain in a way to connect my
 real domain. When I clean this value, console proxy connects to IP.
 After entering any other value it connects to ".realhostip.com"
 anyway. How I can solve this?

 Thanks.

>>>
>>
>>
>>
>>
>

RE: Travis failures

[Edison Su]

I only checked into my personal branch: pytest, which is converting nose to 
pytest, so if you run nose against pytest test cases, definitely, it will fail.
I think it's ok to fail for travis on my pytest branch at this time, as I 
haven't start the discussion in the community about how to improve marvin yet.

> -Original Message-
> From: sebgoa [mailto:run...@gmail.com]
> Sent: Wednesday, September 17, 2014 4:34 AM
> To: dev@cloudstack.apache.org; Edison Su; Min Chen
> Subject: Travis failures
> 
> Hi folks,
> 
> With Travis tests now passing, it's a good time for everyone to get familiar
> with it and understanding the tests that are being run (advanced zone,
> simulator, smoke tests).
> 
> While most builds have been green since yesterday there was two commits
> (from Edison and Min) that turned out red.
> 
> https://travis-ci.org/apache/cloudstack/builds
> 
> Ideally we should all get in the habit of committing on a separate branch, let
> the tests run and when they pass we can commit to master or the main
> develop branch.
> 
> my 2cts
> 
> -Sebastien

Re: Review Request 25749: Fixed CLOUDSTACK-7573: ISO Guest OS Change

[sangeetha hariharan]

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

Ship it!


Ship It!

- sangeetha hariharan


On Sept. 17, 2014, 7:28 p.m., Chandan Purushothama wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25749/
> ---
> 
> (Updated Sept. 17, 2014, 7:28 p.m.)
> 
> 
> Review request for cloudstack, Amogh Vasekar, sangeetha hariharan, and 
> sanjeev n.
> 
> 
> Bugs: CLOUDSTACK-7573
> https://issues.apache.org/jira/browse/CLOUDSTACK-7573
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> The Bug results in VM deployment failure across different configurations. 
> Correcting the guest OS Type resolves the issue
> 
> 
> Diffs
> -
> 
>   tools/marvin/marvin/config/test_data.py 9b2aee7 
> 
> Diff: https://reviews.apache.org/r/25749/diff/
> 
> 
> Testing
> ---
> 
> I tested manually on a different setup.
> 
> 
> Thanks,
> 
> Chandan Purushothama
> 
>

Jenkins build is back to normal : simulator-singlerun #388

[jenkins]

See 

Build failed in Jenkins: build-master-noredist #3557

[jenkins]

See 

Changes:

[sangeetha.hariharan] CLOUDSTACK-7573 : Fixed the Guest OS Type used for the ISO

--
[...truncated 1814 lines...]
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.582 sec
Running com.cloud.keystore.KeystoreTest
org.apache.cloudstack.api.response.UserVmResponse/null/{"id":"3","securitygroup":[],"nic":[],"tags":[],"affinitygroup":[]}
org.apache.cloudstack.api.response.AlertResponse/null/{"id":"100","description":"Hello"}
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.229 sec
Running com.cloud.alert.AlertControlsUnitTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.029 sec
Running com.cloud.capacity.CapacityManagerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.166 sec
Running com.cloud.servlet.StaticResourceServletTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.16 sec
Running com.cloud.servlet.ConsoleProxyServletTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running com.cloud.resourcelimit.ResourceLimitManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running com.cloud.network.firewall.FirewallManagerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0 sec
Running com.cloud.network.ExternalLoadBalancerDeviceManagerImplTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.765 sec
Running com.cloud.network.element.VirtualRouterElementTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.971 sec
Running com.cloud.network.UpdatePhysicalNetworkTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.175 sec
Running com.cloud.network.CreatePrivateNetworkTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.047 sec
Running com.cloud.network.NetworkModelTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.064 sec
Running com.cloud.network.router.VirtualNetworkApplianceManagerImplTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.062 sec
Running com.cloud.network.security.SecurityGroupManagerImplTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.401 sec
Running com.cloud.network.security.SecurityGroupQueueTest
Total jobs dequeued = 10, num queued=1008 queue current size=998
Num Vms= 50 Queue size = 50
Num Vms= 2 Queue size = 2 time=956 ms
Num Vms= 5000 Queue size = 5000 time=1042 ms
Num Vms= 1 Queue size = 1 time=0 ms
Num Vms= 100 Queue size = 100 time=239 ms
Total jobs dequeued = 10, num queued=1009 queue current size=1000
Tests run: 4, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 2.687 sec <<< 
FAILURE!
Running com.cloud.network.vpc.VpcManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.028 sec
Running com.cloud.network.DedicateGuestVlanRangesTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.025 sec
Running com.cloud.network.lb.AssignLoadBalancerTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.087 sec
Running com.cloud.network.dao.NetworkDaoTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec
Running com.cloud.vm.DeploymentPlanningManagerImplTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.718 sec
Running com.cloud.vm.snapshot.VMSnapshotManagerTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.131 sec
Running com.cloud.vm.UserVmManagerTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.259 sec
Running com.cloud.configuration.ValidateIpRangeTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 sec
Running com.cloud.configuration.ConfigurationManagerTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.057 sec
Running com.cloud.server.ConfigurationServerImplTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec
Running com.cloud.template.TemplateManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec
Running com.cloud.vpc.Site2SiteVpnTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.511 sec
Running com.cloud.vpc.NetworkACLServiceTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.188 sec
Running com.cloud.vpc.NetworkACLManagerTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.19 sec
Running com.cloud.storage.VolumeApiServiceImplTest
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.121 sec
Running com.cloud.user.AccountManagerImplTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.147 sec
Running com.cloud.api.ApiServletTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time el

Re: [DISCUSS] CloudStack Future

[Fernandez, H.J.]

Hi all,

I’ll personally improve monitoring and autoscalability, I believe both systems 
can be adapted to today’s requirements bringing more accurate results and 
user-experience. Inline with this proposal, I’d also address the same issues 
taking into account a new virtualization layer, the LXC containers (explicitly 
with support for Docker or not).

Thanks.

Hector
Software Engineer
Linkedin: 
linkedin.com/in/hector2fernandez
Twitter:  twitter.com/hectorj2f





On Sep 17, 2014, at 7:02 AM, John Kinsella 
mailto:j...@stratosec.co>> wrote:

I love seeing thoughts/actions around organizing.

but… (Rohit, you keep doing good stuff and I keep popping up to be negative, 
sorry :) )

Can we do this within the ASF infrastructure? Trello is cool (I’ve used it 
internally in the past) but can’t we do this on a Confluence page? This allows 
folks to use existing ASF credentials to be part of the party.  If there’s 
major reasons (usability or otherwise) that we can’t, let us know them. I know 
at least Rohit likes the cool new toys (not meant in a bad way) and that ASF 
usually won’t have the cool new toys (also not meant in a bad way) but I think 
we’ll benefit from building our sand castles within the existing sandbox…

That said…

ACS demo appliance - let’s chat on this one, I’ve got the basics in place 
https://www.youtube.com/watch?v=Ql8eAO9rvQE I’ve been slowly gearing to push 
that to https://github.com/jlk/LiveCloud

“Aim for stable master” gives me a really big :( but I get it.

Under Development column, what’s “ET” ?

VM importer shouldn’t be in development - this needs to be in production 
releases.

Would like to see an expansion on “developer dogfooding” - e.g. develop within 
ACS VMs, or??

Keep running with this - I’d just rather see it happening on existing 
"old-school" technology that Rohit doesn’t like ;)

John

Also, I believe we have a Jira Aglie license, so if we really want to go down 
this path we can create agile/kanban stories/epics and do that whole thing.

On Sep 16, 2014, at 3:55 PM, Outback Dingo 
mailto:outbackdi...@gmail.com>> wrote:

Some of us would love to contribute, yet don't feel the requirement to
sign-up for "sites" to simply post their feelings.
That being said... heres mine in public.. remove the "dependency"
on NFS as primary/secondary allow
for more configurable storage options. Its one of the reasons why we
dropped cloudstack. That and certain networking
configuration requirements didn't fit our network topology.

On Wed, Sep 17, 2014 at 2:51 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

Hi everyone,

First: Thanks to Rohit and Daan for working on this.

Next: Definitely feel free to e-mail ideas privately; however, I'd like to
especially encourage people to make their ideas known publicly, if you feel
comfortable doing this. Doing it publicly might make it easier for us as a
community to brainstorm the ideas and play around with taking them in
different directions.

Thanks!
Mike

On Tue, Sep 16, 2014 at 3:08 AM, Rohit Yadav 
mailto:rohit.ya...@shapeblue.com>>
wrote:

Hi everyone,

Some of us are in Amsterdam and discussing various things we want to do
for the project. I’ve aggregated some of them on a Trello board here:
https://trello.com/b/nj8dDBWl/apache-cloudstack-future

Please share your ideas, publicly or private to me; I’ll add them on the
board. Our main focus right now is testing, release quality and aligning
efforts.

We’re now able to run simulator tests on TravisCI for 4.4 and master
branches:
https://travis-ci.org/apache/cloudstack/builds

Some of us are also experimenting with Github pull requests and we
already
see that it’s encouraging to get TravisCI verify them.

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +41 779015219 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab

Find out more about ShapeBlue and our range of CloudStack related
services

IaaS Cloud Design & Build<
http://shapeblue.com/iaas-cloud-design-and-build//>
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Infrastructure Support<
http://shapeblue.com/cloudstack-infrastructure-support/>
CloudStack Bootcamp Training Courses<
http://shapeblue.com/cloudstack-training/>

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

Fwd: JIRA

[Mike Tutkowski]

Punith was trying to assign a JIRA ticket to himself, but does not seem to
have the appropriate authority (and I cannot seem to find his username in
the list of people who I can assign tickets to).

Does anyone know who can give this to him?

Thanks!

-- Forwarded message --
From: Punith S 
Date: Wed, Sep 17, 2014 at 5:55 AM
Subject: Re: JIRA
To: Mike Tutkowski 


hi mike,

my user name is punith
now i have uploaded my profile pic to make it clear.

perhaps you can find me in these links
https://issues.apache.org/jira/secure/ViewProfile.jspa
https://issues.apache.org/jira/browse/CLOUDSTACK-7003

thanks!

On Tue, Sep 16, 2014 at 10:25 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Hi Punith,
>
> Can you tell me what your username is on JIRA? I typed in "Punith" and
> variations of that, but didn't see anything that looked like it would be
> you.
>
> Thanks!
> Mike
>
> On Tue, Sep 16, 2014 at 12:12 AM, Punith S  wrote:
>
>> hi mike,
>>
>> i'm trying to assign myself a bug, but i'm not sure that i have
>> permission to do so.
>> or am i missing something here ? can you elaborate me about how to assign
>> oneself a bug ?
>>
>> thanks
>>
>> On Tue, Sep 16, 2014 at 2:55 AM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>>> Hi Punith,
>>>
>>> If you don't already have one, would you create a username in JIRA and
>>> assign the ticket you're working on to yourself?
>>>
>>> https://issues.apache.org/jira/browse/CLOUDSTACK-7406
>>>
>>> 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
>>> *™*
>>>
>>
>>
>>
>> --
>> regards,
>>
>> punith s
>> cloudbyte.com
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> *™*
>



-- 
regards,

punith s
cloudbyte.com



-- 
*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: Fwd: JIRA

[David Nalley]

Anyone on the PMC should be able to take care of this. (assuming they are 
listed as being on the PMC in Jira) 

Punith: You should now have karma to assign tickets to yourself or be assigned 
tickets. 

—David


On September 17, 2014 at 7:35:29 PM, Mike Tutkowski 
(mike.tutkow...@solidfire.com) wrote:
> Punith was trying to assign a JIRA ticket to himself, but does not seem to
> have the appropriate authority (and I cannot seem to find his username in
> the list of people who I can assign tickets to).
>  
> Does anyone know who can give this to him?
>  
> Thanks!
>  
> -- Forwarded message --
> From: Punith S  
> Date: Wed, Sep 17, 2014 at 5:55 AM
> Subject: Re: JIRA
> To: Mike Tutkowski  
>  
>  
> hi mike,
>  
> my user name is punith
> now i have uploaded my profile pic to make it clear.
>  
> perhaps you can find me in these links
> https://issues.apache.org/jira/secure/ViewProfile.jspa
> https://issues.apache.org/jira/browse/CLOUDSTACK-7003
>  
> thanks!
>  
> On Tue, Sep 16, 2014 at 10:25 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>  
> > Hi Punith,
> >
> > Can you tell me what your username is on JIRA? I typed in "Punith" and
> > variations of that, but didn't see anything that looked like it would be
> > you.
> >
> > Thanks!
> > Mike
> >
> > On Tue, Sep 16, 2014 at 12:12 AM, Punith S wrote:
> >
> >> hi mike,
> >>
> >> i'm trying to assign myself a bug, but i'm not sure that i have
> >> permission to do so.
> >> or am i missing something here ? can you elaborate me about how to assign
> >> oneself a bug ?
> >>
> >> thanks
> >>
> >> On Tue, Sep 16, 2014 at 2:55 AM, Mike Tutkowski <
> >> mike.tutkow...@solidfire.com> wrote:
> >>
> >>> Hi Punith,
> >>>
> >>> If you don't already have one, would you create a username in JIRA and
> >>> assign the ticket you're working on to yourself?
> >>>
> >>> https://issues.apache.org/jira/browse/CLOUDSTACK-7406
> >>>
> >>> 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
> >>> *™*
> >>>
> >>
> >>
> >>
> >> --
> >> regards,
> >>
> >> punith s
> >> cloudbyte.com
> >>
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the cloud
> > *™*
> >
>  
>  
>  
> --
> regards,
>  
> punith s
> cloudbyte.com
>  
>  
>  
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> *™*
>  

Build failed in Jenkins: build-master-noredist #3558

[jenkins]

See 

Changes:

[anthony.xu] in tagCommand, AsyncJobExecutionContext doesn't need to be created 
if it doesn't exist

[anthony.xu] added hypervisor capacity for XS 6.5.0

--
[...truncated 1814 lines...]
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.585 sec
Running com.cloud.keystore.KeystoreTest
org.apache.cloudstack.api.response.UserVmResponse/null/{"id":"3","securitygroup":[],"nic":[],"tags":[],"affinitygroup":[]}
org.apache.cloudstack.api.response.AlertResponse/null/{"id":"100","description":"Hello"}
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.223 sec
Running com.cloud.alert.AlertControlsUnitTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec
Running com.cloud.capacity.CapacityManagerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.173 sec
Running com.cloud.servlet.StaticResourceServletTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.165 sec
Running com.cloud.servlet.ConsoleProxyServletTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running com.cloud.resourcelimit.ResourceLimitManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running com.cloud.network.firewall.FirewallManagerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0 sec
Running com.cloud.network.ExternalLoadBalancerDeviceManagerImplTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.753 sec
Running com.cloud.network.element.VirtualRouterElementTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.725 sec
Running com.cloud.network.UpdatePhysicalNetworkTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.131 sec
Running com.cloud.network.CreatePrivateNetworkTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec
Running com.cloud.network.NetworkModelTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.023 sec
Running com.cloud.network.router.VirtualNetworkApplianceManagerImplTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.043 sec
Running com.cloud.network.security.SecurityGroupManagerImplTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.59 sec
Running com.cloud.network.security.SecurityGroupQueueTest
Total jobs dequeued = 10, num queued=1003 queue current size=993
Num Vms= 50 Queue size = 50
Num Vms= 2 Queue size = 2 time=144 ms
Num Vms= 5000 Queue size = 5000 time=1582 ms
Num Vms= 1 Queue size = 1 time=1 ms
Num Vms= 100 Queue size = 100 time=330 ms
Total jobs dequeued = 10, num queued=1006 queue current size=996
Total jobs dequeued = 1, num queued=1001 queue current size=1000
Total jobs dequeued = 10, num queued=1000 queue current size=990
Total jobs dequeued = 10, num queued=10 queue current size=0
Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.475 sec <<< 
FAILURE!
Running com.cloud.network.vpc.VpcManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec
Running com.cloud.network.DedicateGuestVlanRangesTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.036 sec
Running com.cloud.network.lb.AssignLoadBalancerTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.061 sec
Running com.cloud.network.dao.NetworkDaoTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running com.cloud.vm.DeploymentPlanningManagerImplTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.738 sec
Running com.cloud.vm.snapshot.VMSnapshotManagerTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.145 sec
Running com.cloud.vm.UserVmManagerTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.186 sec
Running com.cloud.configuration.ValidateIpRangeTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.017 sec
Running com.cloud.configuration.ConfigurationManagerTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.054 sec
Running com.cloud.server.ConfigurationServerImplTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec
Running com.cloud.template.TemplateManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
Running com.cloud.vpc.Site2SiteVpnTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.835 sec
Running com.cloud.vpc.NetworkACLServiceTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.194 sec
Running com.cloud.vpc.NetworkACLManagerTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.2 sec
Running com.cloud.storage.VolumeApiServiceImplTest
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.194 sec
Running 

Re: JIRA

[Mike Tutkowski]

Thanks, David

I should look and find out how you do that in JIRA.

On Wednesday, September 17, 2014, David Nalley  wrote:

> Anyone on the PMC should be able to take care of this. (assuming they are
> listed as being on the PMC in Jira)
>
> Punith: You should now have karma to assign tickets to yourself or be
> assigned tickets.
>
> —David
>
>
> On September 17, 2014 at 7:35:29 PM, Mike Tutkowski (
> mike.tutkow...@solidfire.com ) wrote:
> > Punith was trying to assign a JIRA ticket to himself, but does not seem
> to
> > have the appropriate authority (and I cannot seem to find his username in
> > the list of people who I can assign tickets to).
> >
> > Does anyone know who can give this to him?
> >
> > Thanks!
> >
> > -- Forwarded message --
> > From: Punith S
> > Date: Wed, Sep 17, 2014 at 5:55 AM
> > Subject: Re: JIRA
> > To: Mike Tutkowski
> >
> >
> > hi mike,
> >
> > my user name is punith
> > now i have uploaded my profile pic to make it clear.
> >
> > perhaps you can find me in these links
> > https://issues.apache.org/jira/secure/ViewProfile.jspa
> > https://issues.apache.org/jira/browse/CLOUDSTACK-7003
> >
> > thanks!
> >
> > On Tue, Sep 16, 2014 at 10:25 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com > wrote:
> >
> > > Hi Punith,
> > >
> > > Can you tell me what your username is on JIRA? I typed in "Punith" and
> > > variations of that, but didn't see anything that looked like it would
> be
> > > you.
> > >
> > > Thanks!
> > > Mike
> > >
> > > On Tue, Sep 16, 2014 at 12:12 AM, Punith S wrote:
> > >
> > >> hi mike,
> > >>
> > >> i'm trying to assign myself a bug, but i'm not sure that i have
> > >> permission to do so.
> > >> or am i missing something here ? can you elaborate me about how to
> assign
> > >> oneself a bug ?
> > >>
> > >> thanks
> > >>
> > >> On Tue, Sep 16, 2014 at 2:55 AM, Mike Tutkowski <
> > >> mike.tutkow...@solidfire.com > wrote:
> > >>
> > >>> Hi Punith,
> > >>>
> > >>> If you don't already have one, would you create a username in JIRA
> and
> > >>> assign the ticket you're working on to yourself?
> > >>>
> > >>> https://issues.apache.org/jira/browse/CLOUDSTACK-7406
> > >>>
> > >>> 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
> > >>> *™*
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> regards,
> > >>
> > >> punith s
> > >> cloudbyte.com
> > >>
> > >
> > >
> > >
> > > --
> > > *Mike Tutkowski*
> > > *Senior CloudStack Developer, SolidFire Inc.*
> > > e: mike.tutkow...@solidfire.com 
> > > o: 303.746.7302
> > > Advancing the way the world uses the cloud
> > > *™*
> > >
> >
> >
> >
> > --
> > regards,
> >
> > punith s
> > cloudbyte.com
> >
> >
> >
> > --
> > *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
*™*

4.5.0 - status - looming dates

[David Nalley]

Hi folks,

4.3.1 is out the door now, so I am trying to get things lined up around 4.5.0.

Please consider us in feature freeze right now - and my plan is to
branch 4.5.0  this coming weekend. I'd like to see us hit code freeze
by end of October. Right now, we have 4 blocker bugs and 63 critical
bugs for the 4.5.0 release, so we have plenty to fix.

If any of these elements cause you concern, please say so.

--David

Jenkins build is back to normal : build-master-noredist #3559

[jenkins]

See 

Re: Inter-network Communication

[Pradeep Cloudstack]

I am working on a Proof-Of-Concept for a private cloud setup.
Here is the organizational requirement:
- Organization has Finance, Engineering and Marketing departments
- Each Dept has a Cloudstack account
- Each Dept has a separate network to which VMs are attached
- Access to the Finance Dept Network should go through Firewall security
- Access to the Marketing Dept Network shouldnot go through Firewall security

- VMs in Engineering network can only communicate with each other but not with 
VMs in other networks


The VPC feature doesnot help in this case as there are different accounts for 
each tenant

Can you pls guide me on how I can achieve this ?


-Pradeep



 From: Jayapal Reddy Uradi 
To: "" ; Pradeep 
Cloudstack  
Sent: Wednesday, September 17, 2014 5:03 PM
Subject: Re: Inter-network Communication
 

Hi Pradeep,

In cloudstack create network and launch vm in that to create router.
To communicate between the networks depends on the network type in cloudstack.

If you want multiple networks with single router use VPC networks/tiers and 
configure ACL between them.

Isolated networks will one router per each network. If vm want to communicate 
to other network
it can be done by  adding nic in that network or Create nat,firewall rules to 
reach vms in other network.

Thanks,
Jayapal


On 17-Sep-2014, at 4:40 PM, Pradeep Cloudstack 

wrote:

> In OpenStack, there is a workflow wherein user can create multiple networks, 
> then create a router
> and attach to it some of the previously created networks to enable 
> inter-network communication.
> 
> What is the equivalent workflow in Cloudstack ?
> 
> -Pradeep

Review Request 25768: changing value of cpu/mem.overprovisioning.factor for xen cluster is not affecting total memory at zone level

[bharat kumar]

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

Review request for cloudstack and Kishan Kavala.


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


Repository: cloudstack-git


Description
---

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


Diffs
-

  engine/schema/src/com/cloud/capacity/dao/CapacityDaoImpl.java 9cae045 

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


Testing
---

Tested on master.


Thanks,

bharat kumar

Re: Review Request 25734: CLOUDSTACK-7565: Fixes to avoid QEMU issue in attach volume operation by changing test case steps

[SrikanteswaraRao Talluri]

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

Ship it!


This workaround looks good to me w.r.t test. However, we need to file a CS bug 
and have someone look at the root cause of the issue. Please file a bug for 
this issue.

- SrikanteswaraRao Talluri


On Sept. 17, 2014, 1:21 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25734/
> ---
> 
> (Updated Sept. 17, 2014, 1:21 p.m.)
> 
> 
> Review request for cloudstack, Santhosh Edukulla and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-7565
> https://issues.apache.org/jira/browse/CLOUDSTACK-7565
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Attach volume test cases failed with following exception from QEMU:
> internal error unable to execute QEMU command '__com.redhat_drive_add': 
> Duplicate ID 'drive-virtio-disk1' for drive
> 
> It has been observed that this issue occurs when disks are repeatedly 
> attached and detached from VM and this is an intermittent issue.
> 
> However we can avoid this issue by creating new account and a VM in it and 
> attaching volume to this VM. This fixes 8 test cases from 
> test_escalations_volume.py test suite.
> 
> 
> Changes:
> 1) Moved account creation and VM deployment from setUpClass() to setUp()
> 2) Fixed import * issues
> 3) Fixed pep8 issues
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_escalations_volumes.py db4c3d8 
> 
> Diff: https://reviews.apache.org/r/25734/diff/
> 
> 
> Testing
> ---
> 
> Yes. Ran whole test suite against KVM and all test cases passed.
> 
> Log:
> @summary: Test List Volumes pagination ... === TestName: 
> test_01_list_volumes_pagination | Status : SUCCESS ===
> ok
> @summary: Test List Volumes with Id ... === TestName: 
> test_02_list_volume_byid | Status : SUCCESS ===
> ok
> @summary: Test to verify creation and resize of data volume ... === TestName: 
> test_03_data_volume_resize | Status : SUCCESS ===
> ok
> @summary: Test to verify creation and resize of custom volume ... === 
> TestName: test_04_custom_volume_resize | Status : SUCCESS ===
> ok
> @summary: Test to verify creation of snapshot from volume and creation of 
> template, volume from snapshot ... === TestName: test_05_volume_snapshot | 
> Status : SUCCESS
> ===
> ok
> @summary: Test to verify creation of Hourly Snapshot policies from volume ... 
> === TestName: test_06_volume_snapshot_policy_hourly | Status : SUCCESS ===
> ok
> @summary: Test to verify creation of Daily Snapshot policies from volume ... 
> === TestName: test_07_volume_snapshot_policy_daily | Status : SUCCESS ===
> ok
> @summary: Test to verify creation of Weekly Snapshot policies from volume ... 
> === TestName: test_08_volume_snapshot_policy_weekly | Status : SUCCESS ===
> ok
> @summary: Test to verify creation of Monthly Snapshot policies from volume 
> ... === TestName: test_09_volume_snapshot_policy_monthly | Status : SUCCESS 
> ===
> ok
> @summary: Test to verify pagination of snapshots for Volume ... === TestName: 
> test_10_volume_snapshots_pagination | Status : SUCCESS ===
> ok
> @summary: Test to verify extract/download a Volume ... === TestName: 
> test_11_volume_extract | Status : SUCCESS ===
> ok
> @summary: Test to verify upload volume ... === TestName: 
> test_12_volume_upload | Status : SUCCESS ===
> ok
> 
> --
> Ran 12 tests in 2657.038s
> 
> OK
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Review Request 25734: CLOUDSTACK-7565: Fixes to avoid QEMU issue in attach volume operation by changing test case steps

[SrikanteswaraRao Talluri]

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


Please fix the below pep8 issues and re-submit the patch.

test/integration/component/test_escalations_volumes.py:128:80: E501 line too 
long (80 > 79 characters)
test/integration/component/test_escalations_volumes.py:131:80: E501 line too 
long (113 > 79 characters)
test/integration/component/test_escalations_volumes.py:149:80: E501 line too 
long (81 > 79 characters)
test/integration/component/test_escalations_volumes.py:160:80: E501 line too 
long (84 > 79 characters)
test/integration/component/test_escalations_volumes.py:164:80: E501 line too 
long (80 > 79 characters)
test/integration/component/test_escalations_volumes.py:203:80: E501 line too 
long (91 > 79 characters)
test/integration/component/test_escalations_volumes.py:232:80: E501 line too 
long (88 > 79 characters)
test/integration/component/test_escalations_volumes.py:249:80: E501 line too 
long (87 > 79 characters)
test/integration/component/test_escalations_volumes.py:325:80: E501 line too 
long (87 > 79 characters)
test/integration/component/test_escalations_volumes.py:526:80: E501 line too 
long (103 > 79 characters)
test/integration/component/test_escalations_volumes.py:685:80: E501 line too 
long (112 > 79 characters)
test/integration/component/test_escalations_volumes.py:902:80: E501 line too 
long (81 > 79 characters)
test/integration/component/test_escalations_volumes.py:1033:80: E501 line too 
long (80 > 79 characters)
test/integration/component/test_escalations_volumes.py:1163:80: E501 line too 
long (81 > 79 characters)
test/integration/component/test_escalations_volumes.py:1293:80: E501 line too 
long (82 > 79 characters)
test/integration/component/test_escalations_volumes.py:1304:80: E501 line too 
long (80 > 79 characters)
test/integration/component/test_escalations_volumes.py:1441:80: E501 line too 
long (80 > 79 characters)
test/integration/component/test_escalations_volumes.py:1445:80: E501 line too 
long (92 > 79 characters)
test/integration/component/test_escalations_volumes.py:1553:80: E501 line too 
long (90 > 79 characters)
test/integration/component/test_escalations_volumes.py:1568:80: E501 line too 
long (90 > 79 characters)
test/integration/component/test_escalations_volumes.py:1732:80: E501 line too 
long (83 > 79 characters)
test/integration/component/test_escalations_volumes.py:1753:80: E501 line too 
long (86 > 79 characters)

- SrikanteswaraRao Talluri


On Sept. 17, 2014, 1:21 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25734/
> ---
> 
> (Updated Sept. 17, 2014, 1:21 p.m.)
> 
> 
> Review request for cloudstack, Santhosh Edukulla and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-7565
> https://issues.apache.org/jira/browse/CLOUDSTACK-7565
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Attach volume test cases failed with following exception from QEMU:
> internal error unable to execute QEMU command '__com.redhat_drive_add': 
> Duplicate ID 'drive-virtio-disk1' for drive
> 
> It has been observed that this issue occurs when disks are repeatedly 
> attached and detached from VM and this is an intermittent issue.
> 
> However we can avoid this issue by creating new account and a VM in it and 
> attaching volume to this VM. This fixes 8 test cases from 
> test_escalations_volume.py test suite.
> 
> 
> Changes:
> 1) Moved account creation and VM deployment from setUpClass() to setUp()
> 2) Fixed import * issues
> 3) Fixed pep8 issues
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_escalations_volumes.py db4c3d8 
> 
> Diff: https://reviews.apache.org/r/25734/diff/
> 
> 
> Testing
> ---
> 
> Yes. Ran whole test suite against KVM and all test cases passed.
> 
> Log:
> @summary: Test List Volumes pagination ... === TestName: 
> test_01_list_volumes_pagination | Status : SUCCESS ===
> ok
> @summary: Test List Volumes with Id ... === TestName: 
> test_02_list_volume_byid | Status : SUCCESS ===
> ok
> @summary: Test to verify creation and resize of data volume ... === TestName: 
> test_03_data_volume_resize | Status : SUCCESS ===
> ok
> @summary: Test to verify creation and resize of custom volume ... === 
> TestName: test_04_custom_volume_resize | Status : SUCCESS ===
> ok
> @summary: Test to verify creation of snapshot from volume and creation of 
> template, volume from snapshot ... === TestName: test_05_volume_snapshot | 
> Status : SUCCESS
> ===
> ok
> @summary: Test to verify creation of Hourly Snapshot policies from volume ... 
> === TestName: test_06_volume_snapshot_policy_hourly | Status : SUCCESS ===
> ok
> @summary: Test to verify creation of Da

Re: Review Request 25647: enabling the rootdisksize variable for vm creation wrt managed storage

[punith s]

> On Sept. 16, 2014, 12:14 p.m., punith s wrote:
> > engine/orchestration/src/org/apache/cloudstack/engine/orchestration/CloudOrchestrator.java,
> >  line 200
> > 
> >
> > yes mike, when you create a compute offering with  a specified min and 
> > max iops on contrary to the custom iops, iops was setting null for the root 
> > disk, since a new rootdiskoffering object is being created, predefined iops 
> > were not being set.
> > 
> > and yes, this issue is not related to this S3 bug, but i thought it to 
> > be a minor one, so i clubbed it with this review.
> 
> Mike Tutkowski wrote:
> That's interesting...none of my regression tests indicated that 
> fixed-size IOPS (i.e. non-custom IOPS) were not being set for root volumes. I 
> actually create VMs using these kinds of Compute Offerings regularly and my 
> IOPS seem to be set properly on the SolidFire SAN.
> 
> Have you actually observed this as an issue in practice or does the code 
> as is simply not look like it would work?
> 
> Thanks for clarifying!

hi mike,

i have sent a new review request on this bug, also i have mentioned the 
scenario when this was actually occuring.
https://reviews.apache.org/r/25732/

thanks.


- punith


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


On Sept. 17, 2014, 5:52 p.m., punith s wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25647/
> ---
> 
> (Updated Sept. 17, 2014, 5:52 p.m.)
> 
> 
> Review request for cloudstack and Mike Tutkowski.
> 
> 
> Bugs: 7406
> https://issues.apache.org/jira/browse/7406
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> since cloudstack is not able to process the S3 or Switf templates for its 
> virtual size(root disk size), admin is facing issues while creating a vm 
> using third party storage plugins like cloudbyte and solidfire etc.
> this patch enables the resize of root disk, on passing a  variable 
> ismanagedstorage = true in deployVmCmd as a detail.
> hence template root disksize is overriden by the given rootdisk size by the 
> admin
> 
> this patch also fixes the iops null issue.
> 
> for more ref
> https://issues.apache.org/jira/browse/CLOUDSTACK-7406
> 
> 
> Diffs
> -
> 
>   server/src/com/cloud/vm/UserVmManagerImpl.java 0ea2a89 
> 
> Diff: https://reviews.apache.org/r/25647/diff/
> 
> 
> Testing
> ---
> 
> dry run only.
> 
> 
> Thanks,
> 
> punith s
> 
>

Re: JIRA

[Punith S]

thanks, David.

On Thu, Sep 18, 2014 at 7:14 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Thanks, David
>
> I should look and find out how you do that in JIRA.
>
> On Wednesday, September 17, 2014, David Nalley  wrote:
>
> > Anyone on the PMC should be able to take care of this. (assuming they are
> > listed as being on the PMC in Jira)
> >
> > Punith: You should now have karma to assign tickets to yourself or be
> > assigned tickets.
> >
> > —David
> >
> >
> > On September 17, 2014 at 7:35:29 PM, Mike Tutkowski (
> > mike.tutkow...@solidfire.com ) wrote:
> > > Punith was trying to assign a JIRA ticket to himself, but does not seem
> > to
> > > have the appropriate authority (and I cannot seem to find his username
> in
> > > the list of people who I can assign tickets to).
> > >
> > > Does anyone know who can give this to him?
> > >
> > > Thanks!
> > >
> > > -- Forwarded message --
> > > From: Punith S
> > > Date: Wed, Sep 17, 2014 at 5:55 AM
> > > Subject: Re: JIRA
> > > To: Mike Tutkowski
> > >
> > >
> > > hi mike,
> > >
> > > my user name is punith
> > > now i have uploaded my profile pic to make it clear.
> > >
> > > perhaps you can find me in these links
> > > https://issues.apache.org/jira/secure/ViewProfile.jspa
> > > https://issues.apache.org/jira/browse/CLOUDSTACK-7003
> > >
> > > thanks!
> > >
> > > On Tue, Sep 16, 2014 at 10:25 PM, Mike Tutkowski <
> > > mike.tutkow...@solidfire.com > wrote:
> > >
> > > > Hi Punith,
> > > >
> > > > Can you tell me what your username is on JIRA? I typed in "Punith"
> and
> > > > variations of that, but didn't see anything that looked like it would
> > be
> > > > you.
> > > >
> > > > Thanks!
> > > > Mike
> > > >
> > > > On Tue, Sep 16, 2014 at 12:12 AM, Punith S wrote:
> > > >
> > > >> hi mike,
> > > >>
> > > >> i'm trying to assign myself a bug, but i'm not sure that i have
> > > >> permission to do so.
> > > >> or am i missing something here ? can you elaborate me about how to
> > assign
> > > >> oneself a bug ?
> > > >>
> > > >> thanks
> > > >>
> > > >> On Tue, Sep 16, 2014 at 2:55 AM, Mike Tutkowski <
> > > >> mike.tutkow...@solidfire.com > wrote:
> > > >>
> > > >>> Hi Punith,
> > > >>>
> > > >>> If you don't already have one, would you create a username in JIRA
> > and
> > > >>> assign the ticket you're working on to yourself?
> > > >>>
> > > >>> https://issues.apache.org/jira/browse/CLOUDSTACK-7406
> > > >>>
> > > >>> 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
> > > >>> *™*
> > > >>>
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> regards,
> > > >>
> > > >> punith s
> > > >> cloudbyte.com
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > *Mike Tutkowski*
> > > > *Senior CloudStack Developer, SolidFire Inc.*
> > > > e: mike.tutkow...@solidfire.com 
> > > > o: 303.746.7302
> > > > Advancing the way the world uses the cloud
> > > > *™*
> > > >
> > >
> > >
> > >
> > > --
> > > regards,
> > >
> > > punith s
> > > cloudbyte.com
> > >
> > >
> > >
> > > --
> > > *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
> *™*
>



-- 
regards,

punith s
cloudbyte.com

Re: Review Request 25734: CLOUDSTACK-7565: Fixes to avoid QEMU issue in attach volume operation by changing test case steps

[Gaurav Aradhye]

> On Sept. 18, 2014, 10:54 a.m., SrikanteswaraRao Talluri wrote:
> > Please fix the below pep8 issues and re-submit the patch.
> > 
> > test/integration/component/test_escalations_volumes.py:128:80: E501 line 
> > too long (80 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:131:80: E501 line 
> > too long (113 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:149:80: E501 line 
> > too long (81 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:160:80: E501 line 
> > too long (84 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:164:80: E501 line 
> > too long (80 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:203:80: E501 line 
> > too long (91 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:232:80: E501 line 
> > too long (88 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:249:80: E501 line 
> > too long (87 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:325:80: E501 line 
> > too long (87 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:526:80: E501 line 
> > too long (103 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:685:80: E501 line 
> > too long (112 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:902:80: E501 line 
> > too long (81 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:1033:80: E501 line 
> > too long (80 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:1163:80: E501 line 
> > too long (81 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:1293:80: E501 line 
> > too long (82 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:1304:80: E501 line 
> > too long (80 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:1441:80: E501 line 
> > too long (80 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:1445:80: E501 line 
> > too long (92 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:1553:80: E501 line 
> > too long (90 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:1568:80: E501 line 
> > too long (90 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:1732:80: E501 line 
> > too long (83 > 79 characters)
> > test/integration/component/test_escalations_volumes.py:1753:80: E501 line 
> > too long (86 > 79 characters)

Fixed


- Gaurav


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


On Sept. 17, 2014, 6:51 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25734/
> ---
> 
> (Updated Sept. 17, 2014, 6:51 p.m.)
> 
> 
> Review request for cloudstack, Santhosh Edukulla and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-7565
> https://issues.apache.org/jira/browse/CLOUDSTACK-7565
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Attach volume test cases failed with following exception from QEMU:
> internal error unable to execute QEMU command '__com.redhat_drive_add': 
> Duplicate ID 'drive-virtio-disk1' for drive
> 
> It has been observed that this issue occurs when disks are repeatedly 
> attached and detached from VM and this is an intermittent issue.
> 
> However we can avoid this issue by creating new account and a VM in it and 
> attaching volume to this VM. This fixes 8 test cases from 
> test_escalations_volume.py test suite.
> 
> 
> Changes:
> 1) Moved account creation and VM deployment from setUpClass() to setUp()
> 2) Fixed import * issues
> 3) Fixed pep8 issues
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_escalations_volumes.py db4c3d8 
> 
> Diff: https://reviews.apache.org/r/25734/diff/
> 
> 
> Testing
> ---
> 
> Yes. Ran whole test suite against KVM and all test cases passed.
> 
> Log:
> @summary: Test List Volumes pagination ... === TestName: 
> test_01_list_volumes_pagination | Status : SUCCESS ===
> ok
> @summary: Test List Volumes with Id ... === TestName: 
> test_02_list_volume_byid | Status : SUCCESS ===
> ok
> @summary: Test to verify creation and resize of data volume ... === TestName: 
> test_03_data_volume_resize | Status : SUCCESS ===
> ok
> @summary: Test to verify creation and resize of custom volume ... === 
> TestName: test_04_custom_volume_resize | Status : SUCCESS ===
> ok
> @summary: Test to verify creation of snapshot from volume and creation of 
> template, volume from snapshot ... === TestName: test_05_volume_snapsh

Re: Review Request 25734: CLOUDSTACK-7565: Fixes to avoid QEMU issue in attach volume operation by changing test case steps

[Gaurav Aradhye]

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

(Updated Sept. 18, 2014, 11:48 a.m.)


Review request for cloudstack, Santhosh Edukulla and SrikanteswaraRao Talluri.


Changes
---

Fixed more pep8 issues.


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


Repository: cloudstack-git


Description
---

Attach volume test cases failed with following exception from QEMU:
internal error unable to execute QEMU command '__com.redhat_drive_add': 
Duplicate ID 'drive-virtio-disk1' for drive

It has been observed that this issue occurs when disks are repeatedly attached 
and detached from VM and this is an intermittent issue.

However we can avoid this issue by creating new account and a VM in it and 
attaching volume to this VM. This fixes 8 test cases from 
test_escalations_volume.py test suite.


Changes:
1) Moved account creation and VM deployment from setUpClass() to setUp()
2) Fixed import * issues
3) Fixed pep8 issues


Diffs (updated)
-

  test/integration/component/test_escalations_volumes.py db4c3d8 

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


Testing
---

Yes. Ran whole test suite against KVM and all test cases passed.

Log:
@summary: Test List Volumes pagination ... === TestName: 
test_01_list_volumes_pagination | Status : SUCCESS ===
ok
@summary: Test List Volumes with Id ... === TestName: test_02_list_volume_byid 
| Status : SUCCESS ===
ok
@summary: Test to verify creation and resize of data volume ... === TestName: 
test_03_data_volume_resize | Status : SUCCESS ===
ok
@summary: Test to verify creation and resize of custom volume ... === TestName: 
test_04_custom_volume_resize | Status : SUCCESS ===
ok
@summary: Test to verify creation of snapshot from volume and creation of 
template, volume from snapshot ... === TestName: test_05_volume_snapshot | 
Status : SUCCESS
===
ok
@summary: Test to verify creation of Hourly Snapshot policies from volume ... 
=== TestName: test_06_volume_snapshot_policy_hourly | Status : SUCCESS ===
ok
@summary: Test to verify creation of Daily Snapshot policies from volume ... 
=== TestName: test_07_volume_snapshot_policy_daily | Status : SUCCESS ===
ok
@summary: Test to verify creation of Weekly Snapshot policies from volume ... 
=== TestName: test_08_volume_snapshot_policy_weekly | Status : SUCCESS ===
ok
@summary: Test to verify creation of Monthly Snapshot policies from volume ... 
=== TestName: test_09_volume_snapshot_policy_monthly | Status : SUCCESS ===
ok
@summary: Test to verify pagination of snapshots for Volume ... === TestName: 
test_10_volume_snapshots_pagination | Status : SUCCESS ===
ok
@summary: Test to verify extract/download a Volume ... === TestName: 
test_11_volume_extract | Status : SUCCESS ===
ok
@summary: Test to verify upload volume ... === TestName: test_12_volume_upload 
| Status : SUCCESS ===
ok

--
Ran 12 tests in 2657.038s

OK


Thanks,

Gaurav Aradhye

Re: Inter-network Communication

[Gaurav Aradhye]

Pradeep,

You have not mentioned any intern-network communication here. If all
departments are independent, you can have isolated network for each account
and then configure FireWall Rules for the network individually according to
you needs.

Another option is you can use security groups in advanced zone. Have
security group for each department, and then you can configure traffic for
each security group. You can also specify the communication between two
security groups with the help of ingress and egress rules.

Regards,
Gaurav

On Thu, Sep 18, 2014 at 9:22 AM, Pradeep Cloudstack <
pradeepcloudst...@yahoo.com.invalid> wrote:

> I am working on a Proof-Of-Concept for a private cloud setup.
> Here is the organizational requirement:
> - Organization has Finance, Engineering and Marketing departments
> - Each Dept has a Cloudstack account
> - Each Dept has a separate network to which VMs are attached
> - Access to the Finance Dept Network should go through Firewall security
> - Access to the Marketing Dept Network shouldnot go through Firewall
> security
>
> - VMs in Engineering network can only communicate with each other but not
> with VMs in other networks
>
>
> The VPC feature doesnot help in this case as there are different accounts
> for each tenant
>
> Can you pls guide me on how I can achieve this ?
>
>
> -Pradeep
>
>
> 
>  From: Jayapal Reddy Uradi 
> To: "" ; Pradeep
> Cloudstack 
> Sent: Wednesday, September 17, 2014 5:03 PM
> Subject: Re: Inter-network Communication
>
>
> Hi Pradeep,
>
> In cloudstack create network and launch vm in that to create router.
> To communicate between the networks depends on the network type in
> cloudstack.
>
> If you want multiple networks with single router use VPC networks/tiers
> and configure ACL between them.
>
> Isolated networks will one router per each network. If vm want to
> communicate to other network
> it can be done by  adding nic in that network or Create nat,firewall rules
> to reach vms in other network.
>
> Thanks,
> Jayapal
>
>
> On 17-Sep-2014, at 4:40 PM, Pradeep Cloudstack
> 
> wrote:
>
> > In OpenStack, there is a workflow wherein user can create multiple
> networks, then create a router
> > and attach to it some of the previously created networks to enable
> inter-network communication.
> >
> > What is the equivalent workflow in Cloudstack ?
> >
> > -Pradeep
>

Re: Review Request 25734: CLOUDSTACK-7565: Fixes to avoid QEMU issue in attach volume operation by changing test case steps

[SrikanteswaraRao Talluri]

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


032bce5b544afe7316651227e593c977430f2cde master

- SrikanteswaraRao Talluri


On Sept. 18, 2014, 6:18 a.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25734/
> ---
> 
> (Updated Sept. 18, 2014, 6:18 a.m.)
> 
> 
> Review request for cloudstack, Santhosh Edukulla and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-7565
> https://issues.apache.org/jira/browse/CLOUDSTACK-7565
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Attach volume test cases failed with following exception from QEMU:
> internal error unable to execute QEMU command '__com.redhat_drive_add': 
> Duplicate ID 'drive-virtio-disk1' for drive
> 
> It has been observed that this issue occurs when disks are repeatedly 
> attached and detached from VM and this is an intermittent issue.
> 
> However we can avoid this issue by creating new account and a VM in it and 
> attaching volume to this VM. This fixes 8 test cases from 
> test_escalations_volume.py test suite.
> 
> 
> Changes:
> 1) Moved account creation and VM deployment from setUpClass() to setUp()
> 2) Fixed import * issues
> 3) Fixed pep8 issues
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_escalations_volumes.py db4c3d8 
> 
> Diff: https://reviews.apache.org/r/25734/diff/
> 
> 
> Testing
> ---
> 
> Yes. Ran whole test suite against KVM and all test cases passed.
> 
> Log:
> @summary: Test List Volumes pagination ... === TestName: 
> test_01_list_volumes_pagination | Status : SUCCESS ===
> ok
> @summary: Test List Volumes with Id ... === TestName: 
> test_02_list_volume_byid | Status : SUCCESS ===
> ok
> @summary: Test to verify creation and resize of data volume ... === TestName: 
> test_03_data_volume_resize | Status : SUCCESS ===
> ok
> @summary: Test to verify creation and resize of custom volume ... === 
> TestName: test_04_custom_volume_resize | Status : SUCCESS ===
> ok
> @summary: Test to verify creation of snapshot from volume and creation of 
> template, volume from snapshot ... === TestName: test_05_volume_snapshot | 
> Status : SUCCESS
> ===
> ok
> @summary: Test to verify creation of Hourly Snapshot policies from volume ... 
> === TestName: test_06_volume_snapshot_policy_hourly | Status : SUCCESS ===
> ok
> @summary: Test to verify creation of Daily Snapshot policies from volume ... 
> === TestName: test_07_volume_snapshot_policy_daily | Status : SUCCESS ===
> ok
> @summary: Test to verify creation of Weekly Snapshot policies from volume ... 
> === TestName: test_08_volume_snapshot_policy_weekly | Status : SUCCESS ===
> ok
> @summary: Test to verify creation of Monthly Snapshot policies from volume 
> ... === TestName: test_09_volume_snapshot_policy_monthly | Status : SUCCESS 
> ===
> ok
> @summary: Test to verify pagination of snapshots for Volume ... === TestName: 
> test_10_volume_snapshots_pagination | Status : SUCCESS ===
> ok
> @summary: Test to verify extract/download a Volume ... === TestName: 
> test_11_volume_extract | Status : SUCCESS ===
> ok
> @summary: Test to verify upload volume ... === TestName: 
> test_12_volume_upload | Status : SUCCESS ===
> ok
> 
> --
> Ran 12 tests in 2657.038s
> 
> OK
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>