Problem of build

[yan_5...@163.com]

If I modify a function and make sure the modify is correct,and run "mvn clean 
install",it will be many kinds of strange error.

who can help me? Thanks very much



yan_5...@163.com

Re: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Erik Weber]

On Wed, Sep 10, 2014 at 5:31 PM, sebgoa  wrote:

> Hi All,
>
> I've created a 4.3.1 release, with the following artifacts up for a vote:
>
>

I don't know if packaging issues is relevant or not, but rpms require
openjdk 1.6 rather than 1.7, which makes the kvm agent unable to start.

[root@cloud-lab-node3 cloudstack]# cat agent/cloudstack-agent.err

log4j:WARN No appenders could be found for logger
(com.cloud.agent.AgentShell).

log4j:WARN Please initialize the log4j system properly.

log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
more info.

java.lang.reflect.InvocationTargetException

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:622)

at
org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:177)

Caused by: java.lang.UnsupportedClassVersionError:
com/ceph/rados/RadosException : Unsupported major.minor version 51.0

at java.lang.ClassLoader.defineClass1(Native Method)

at java.lang.ClassLoader.defineClass(ClassLoader.java:643)

at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)

at java.net.URLClassLoader.defineClass(URLClassLoader.java:277)

at java.net.URLClassLoader.access$000(URLClassLoader.java:73)

at java.net.URLClassLoader$1.run(URLClassLoader.java:212)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(URLClassLoader.java:205)

at java.lang.ClassLoader.loadClass(ClassLoader.java:323)

at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)

at java.lang.ClassLoader.loadClass(ClassLoader.java:268)

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Class.java:190)

at com.cloud.agent.AgentShell.launchAgentFromClassInfo(AgentShell.java:371)

at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:358)

at com.cloud.agent.AgentShell.start(AgentShell.java:455)

... 5 more

11/09/2014 12:07:25 5122 jsvc.exec error: Cannot start daemon

-- 
Erik

Re: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Rohit Yadav]

Hi Erik,

On 11-Sep-2014, at 10:11 am, Erik Weber  wrote:
> I don't know if packaging issues is relevant or not, but rpms require
> openjdk 1.6 rather than 1.7, which makes the kvm agent unable to start.
>
> [root@cloud-lab-node3 cloudstack]# cat agent/cloudstack-agent.err
>
> log4j:WARN No appenders could be found for logger
> (com.cloud.agent.AgentShell).

I checked cloud.spec, The rpms requires java 1.6.0 or above, when you install 
cloudstack-agent does it automatically only install openjdk 1.6? If you install 
openjdk 1.7 does this problem go away?

Are you using the rpms from the repo I shared, those RPMs were build using JDK 
1.7 so running them on 1.6 JRE/JVM can cause issues. Can you try building the 
rpms yourself using JDK 1.6 and running them on 1.6 and see if you can 
reproduce this issue.

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: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Nux!]

I'm going to try upgrading an existing 4.3.0 env, do we also need to upgrade 
the SystemVMs?



--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro


- Original Message -
> From: "sebgoa" 
> To: dev@cloudstack.apache.org
> Sent: Wednesday, 10 September, 2014 4:31:09 PM
> Subject: [VOTE] Release Apache CloudStack 4.3.1 round #4
> 
> Hi All,
> 
> I've created a 4.3.1 release, with the following artifacts up for a vote:
> 
> Git Branch and Commit SH:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
> Commit: 1687bcdd9b8de1e372b308dffda5bf819b5c4296
> 
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=CHANGES.md;hb=4.3
> 
> Source release (checksums and signatures are available at the same location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.3.1/
> 
> PGP release keys (signed using 8F89EB84):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> 
> Vote will be open for 72 hours.
> 
> Please use
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
> to test at least for the keys, rat etc.
> 
> For sanity in tallying the vote, can PMC members please be sure to indicate
> "(binding)" with their vote?
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)

RE: [TRAVIS] - failing for pull request #18

[Wilder Rodrigues]

Hi Ian,

One job is fixed. What happened? I would say one should not stay awake until 
2AM doing cloudstack. ;) There were things I did not push, sorry by that.

Concerning the other 2 jobs, I just got the simulator environment running and 
already found the reason why they are failing. In the refactor of the 
deployRouter() method, the code related to the support hypervisor has changed 
in term of behaviour. The refactor should have been done in 2 steps: first 
restructure the code; then make it better. Along our hard 10 weeks of work 
those 2 steps were mix[messed]-up a bit.

Sorry for bothering you with that, I will fix it.

Cheers,
Wilder


From: Wilder Rodrigues
Sent: Wednesday, September 10, 2014 12:44 PM
To: 'Ian Duffy'
Cc: CloudStack Dev; int-toolkit; int-cloud
Subject: RE: [TRAVIS] - failing for pull request #18

Okay…

I’m cloning it in a different place, just to make sure I follow the same steps 
as you.

Once I get it tested… will share my thoughts again. ☺

Thanks again for the support.

Cheers,
Wilder

From: Ian Duffy [mailto:i...@ianduffy.ie]
Sent: woensdag 10 september 2014 12:06
To: Wilder Rodrigues
Cc: CloudStack Dev; int-toolkit; int-cloud
Subject: Re: [TRAVIS] - failing for pull request #18

> You clone the “test-cmd-rebase” branch,  right?

Yes positive:
$ git status
On branch test-cmd-rebase
Your branch is up-to-date with 'origin/test-cmd-rebase'.

Try your work against the simulator.

On 10 September 2014 10:44, Wilder Rodrigues 
mailto:wrodrig...@schubergphilis.com>> wrote:
Thanks Ian,

I will follow the same steps, because it’s really weird.

I’m running with mvn –pl :cloud-ui jetty:run, but no simulator.

Accounts page looks fine, I even executed the accounts related tests. Advance 
zone was also deployed successfully.

The data form my accounts page:

admin  Admin  ROOT  enabled
baremetal-system-account User ROOT  enabled
test-a-TestVpcRemoteAccessVpn-4SYLK3   User ROOT  enabled
test-a-TestVpcRemoteAccessVpn-5WDDUJ User ROOT  enabled

You clone the “test-cmd-rebase” branch,  right?

I was busy running all the tests I have again, the result was successful and I 
also kept tracking the “running.txt” Marvin log file during execution.

The only difference IPs I have in the advanced.cfg, because I do not use the 
ranges that are there.



Test Create Account and user for that account ... === TestName: 
test_01_create_account | Status : SUCCESS ===
ok
Test Sub domain allowed to launch VM  when a Domain level zone is created ... 
=== TestName: test_01_add_vm_to_subdomain | Status : SUCCESS ===
ok
Test delete domain without force option ... === TestName: test_DeleteDomain | 
Status : SUCCESS ===
ok
Test delete domain with force option ... === TestName: test_forceDeleteDomain | 
Status : SUCCESS ===
ok
Test update admin details ... === TestName: test_updateAdminDetails | Status : 
SUCCESS ===
ok
Test update domain admin details ... === TestName: 
test_updateDomainAdminDetails | Status : SUCCESS ===
ok
Test user update API ... === TestName: test_updateUserDetails | Status : 
SUCCESS ===
ok
Test login API with domain ... === TestName: test_LoginApiDomain | Status : 
SUCCESS ===
ok
Test if Login API does not return UUID's ... === TestName: 
test_LoginApiUuidResponse | Status : SUCCESS ===
ok

--
Ran 9 tests in 832.310s

OK

test_privategw_acl (ekholabs.acs.tests.test_privategw_acl.TestPrivateGwACL) ... 
=== TestName: test_privategw_acl | Status : SUCCESS ===
ok

--
Ran 1 test in 100.582s

OK

Test reset virtual machine on reboot ... === TestName: 
test_01_reset_vm_on_reboot | Status : SUCCESS ===
ok

--
Ran 1 test in 183.507s

OK

Test router internal basic zone ... SKIP: Marvin configuration has no host 
credentials to check router services
Test router internal advanced zone ... SKIP: Marvin configuration has no host 
credentials to check router services
Test restart network ... === TestName: test_03_restart_network_cleanup | Status 
: SUCCESS ===
ok
Test restart network without cleanup ... SKIP: Marvin configuration has no host 
credentials to check router services
Test router basic setup ... === TestName: test_05_router_basic | Status : 
SUCCESS ===
ok
Test router advanced setup ... === TestName: test_06_router_advanced | Status : 
SUCCESS ===
ok
Test stop router ... === TestName: test_07_stop_router | Status : SUCCESS ===
ok
Test start router ... === TestName: test_08_start_router | Status : SUCCESS ===
ok
Test reboot router ... === TestName: test_09_reboot_router | Status : SUCCESS 
===
ok

--
Ran 9 tests in 354.245s

OK (SKIP=3)

Test to create service offering ... === TestName: 
test_01_create_service_offering | Status : SUCCESS ===
ok
Test to update existing service offering ... === TestName: 
test_02

Re: Review Request 25290: CLOUDSTACK-7441: Fixed template register issue in test_resource_limits.py

[Gaurav Aradhye]

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

(Updated Sept. 11, 2014, 2:59 p.m.)


Review request for cloudstack, sanjeev n, Santhosh Edukulla, and 
SrikanteswaraRao Talluri.


Changes
---

Fixed same issue for test_05_templates_per_domain


Repository: cloudstack-git


Description
---

Templates were earlier registered with the admin api client, however they 
should be registered with the apiclient of the account in which the template 
has to be registered.

This will list out template properly when listed.


Diffs (updated)
-

  test/integration/component/test_resource_limits.py 35128b4 

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


Testing
---

Yes.

Log:
Test Templates limit per account ... === TestName: 
test_05_templates_per_account | Status : SUCCESS ===
ok

--
Ran 1 test in 1361.574s

OK


Thanks,

Gaurav Aradhye

Re: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Erik Weber]

On Thu, Sep 11, 2014 at 10:54 AM, Rohit Yadav 
wrote:

> Hi Erik,
>
> On 11-Sep-2014, at 10:11 am, Erik Weber  wrote:
> > I don't know if packaging issues is relevant or not, but rpms require
> > openjdk 1.6 rather than 1.7, which makes the kvm agent unable to start.
> >
> > [root@cloud-lab-node3 cloudstack]# cat agent/cloudstack-agent.err
> >
> > log4j:WARN No appenders could be found for logger
> > (com.cloud.agent.AgentShell).
>
> I checked cloud.spec, The rpms requires java 1.6.0 or above, when you
> install cloudstack-agent does it automatically only install openjdk 1.6? If
> you install openjdk 1.7 does this problem go away?
>
>
Yes, I only had openjdk 1.6 installed. Installing openjdk 1.7 and removing
1.6 solved the issue.



> Are you using the rpms from the repo I shared, those RPMs were build using
> JDK 1.7 so running them on 1.6 JRE/JVM can cause issues. Can you try
> building the rpms yourself using JDK 1.6 and running them on 1.6 and see if
> you can reproduce this issue.
>
>
I actually used the latest from jenkins. The spec file is the same, but I
can try building them myself just to be sure.

-- 
Erik

RE: Problem of build

[Stephen Turner]

Could you send the exact errors?

-- 
Stephen Turner


-Original Message-
From: yan_5...@163.com [mailto:yan_5...@163.com] 
Sent: 11 September 2014 08:35
To: dev
Subject: Problem of build

If I modify a function and make sure the modify is correct,and run "mvn clean 
install",it will be many kinds of strange error.

who can help me? Thanks very much



yan_5...@163.com

Jenkins build is still unstable: simulator-singlerun #341

[jenkins]

See 

Review Request 25536: Adding new test case to verify the fix for issue "Exception when attaching data disk to Rhel vm on vSphere"

[sanjeev n]

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

Review request for cloudstack, Santhosh Edukulla and SrikanteswaraRao Talluri.


Repository: cloudstack-git


Description
---

@desc: Exception when attaching data disk to RHEL VM on vSphere
Step1: Confirm that vmware.root.disk.controller = "ide" in Global Settings.
Step2: Register RHEl 6.0 template and deploy a VM.
Step3: Note that the root disk is attached to IDE.
Step4: Create new DATA disk and attempt to attach it to the VM.
Verify that step4 succeeds without any exception


Diffs
-

  test/integration/component/test_escalations_vmware.py PRE-CREATION 
  tools/marvin/marvin/config/test_data.py 4133aba 

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


Testing
---

Yes


Thanks,

sanjeev n

Review Request 25535: CLOUDSTACK-7391: Passing virtualmachineid while retrieving suitable hosts for migration

[Gaurav Aradhye]

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

Review request for cloudstack, sanjeev n, Santhosh Edukulla, and 
SrikanteswaraRao Talluri.


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


Repository: cloudstack-git


Description
---

virutalmachineid should be passed to listHosts api for retrieving the hosts 
suitable for VM migration.

Also fixed pep8 issues.


Diffs
-

  test/integration/component/maint/test_host_high_availability.py 4cd7fd8 

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


Testing
---

Yes.

Log:
Test VM deployments (Create HA enabled Compute Service Offering and VM) ... 
SKIP: skip
Verify you can not create new VMs on hosts with an ha.tag ... SKIP: skip
Verify you can not migrate VMs to hosts with an ha.tag (positive) ... === 
TestName: test_03_cant_migrate_vm_to_host_with_ha_positive | Status : SUCCESS 
===
ok
Verify you can not migrate VMs to hosts with an ha.tag (negative) ... SKIP: skip
Verify that none of the VMs with HA enabled migrate to an ha tagged host during 
live migration ... SKIP: skip
Verify that none of the VMs without HA enabled migrate to an ha tagged host 
during live migration ... SKIP: skip

--
Ran 6 tests in 191.673s

OK (SKIP=5)


Thanks,

Gaurav Aradhye

Regarding gateway ip getting allocated to user VMs in shared network.

[Bharat Kumar]

Hi All,

I have found that the gateway ip can get allocated to the uservms in case of 
shared networks. This is a corner case and might happen accidentally. 

This happens because we allow addition guest ip ranges containing the gateway 
ip, while creating a shared network and internally there is no check 
to see if the ip getting allocated is a gateway ip. 

Simple way to fix this would be to fail the network creation if the supplied 
guest ip range contains the gateway ip.

example
gateway=172.16.88.1
netmask=255.255.255.0
guestIpRange=172.16.88.1 to 172.16.88.20.

we fail the network creation in this case as the gateway ip is a part of the 
guest ip range.


Any concerns or suggestions regarding this fix ?

bug id CLOUDSTACK-7536

Re: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Rohit Yadav]

On 11-Sep-2014, at 11:10 am, Nux!  wrote:
> I'm going to try upgrading an existing 4.3.0 env, do we also need to upgrade 
> the SystemVMs?

Ideally, yes

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.

Jenkins build is still unstable: simulator-singlerun #342

[jenkins]

See 

Re: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Erik Weber]

I'll revert my initial message.

Making sure the RPMs are built with openjdk 1.6 does indeed work, so this
is a build issue.

This is however something that could bite someone though.

The spec requires openjdk 1.6 to build, but you can easily have both 1.6
and 1.7 installed and have it built with 1.7 if that is your default java,
am I correct?

I'm not saying this should warrant the vote to fail, just want to mention
it.

-- 
Erik

-- 
Erik


On Thu, Sep 11, 2014 at 11:38 AM, Erik Weber  wrote:

> On Thu, Sep 11, 2014 at 10:54 AM, Rohit Yadav 
> wrote:
>
>> Hi Erik,
>>
>> On 11-Sep-2014, at 10:11 am, Erik Weber  wrote:
>> > I don't know if packaging issues is relevant or not, but rpms require
>> > openjdk 1.6 rather than 1.7, which makes the kvm agent unable to start.
>> >
>> > [root@cloud-lab-node3 cloudstack]# cat agent/cloudstack-agent.err
>> >
>> > log4j:WARN No appenders could be found for logger
>> > (com.cloud.agent.AgentShell).
>>
>> I checked cloud.spec, The rpms requires java 1.6.0 or above, when you
>> install cloudstack-agent does it automatically only install openjdk 1.6? If
>> you install openjdk 1.7 does this problem go away?
>>
>>
> Yes, I only had openjdk 1.6 installed. Installing openjdk 1.7 and removing
> 1.6 solved the issue.
>
>
>
>> Are you using the rpms from the repo I shared, those RPMs were build
>> using JDK 1.7 so running them on 1.6 JRE/JVM can cause issues. Can you try
>> building the rpms yourself using JDK 1.6 and running them on 1.6 and see if
>> you can reproduce this issue.
>>
>>
> I actually used the latest from jenkins. The spec file is the same, but I
> can try building them myself just to be sure.
>
> --
> Erik
>
>

Re: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Nux!]

Hello,

I've upgraded and it looks ok for now.
I have used these system VMs 
http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/ and added 
them as systemvm-kvm-4.3 in the Templates.
I expected them to replace SystemVM Template (KVM), but they are still listed 
as systemvm-kvm-4.3 alongside the old ones.
Other than that everything seems ok for now.

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Rohit Yadav" 
> To: dev@cloudstack.apache.org
> Sent: Thursday, 11 September, 2014 12:16:44 PM
> Subject: Re: [VOTE] Release Apache CloudStack 4.3.1 round #4
> 
> 
> On 11-Sep-2014, at 11:10 am, Nux!  wrote:
> > I'm going to try upgrading an existing 4.3.0 env, do we also need to
> > upgrade the SystemVMs?
> 
> Ideally, yes

Review Request 25537: [UI][CLOUDSTACK-7525] Add "Edit Tags" functionality to SecurityGroup rules UI

[Ilia Shakitko]

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

Review request for cloudstack, Brian Federle, Ian Duffy, Jessica Wang, and 
Nitin Mehta.


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


Repository: cloudstack-git


Description
---

An addition to the tagging support for security group rules: 
https://reviews.apache.org/r/24557/

Displays edit tags icon for every SecurityGroup Ingress/Egress rule and allows 
manage them.


Diffs
-

  ui/scripts/network.js 8a758c8 

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


Testing
---

Tested on latest master (11th of September).

Screenshots are here: https://issues.apache.org/jira/browse/CLOUDSTACK-7525

Tags can be added and deleted from UI in different browsers, no 
exceptions/errors.


Thanks,

Ilia Shakitko

Re: Review Request 25537: [UI][CLOUDSTACK-7525] Add "Edit Tags" functionality to SecurityGroup rules UI

[Ilia Shakitko]

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

(Updated Sept. 11, 2014, 1:06 p.m.)


Review request for cloudstack, Brian Federle, Ian Duffy, Jessica Wang, Nitin 
Mehta, Stephen Hoogendijk, and Wei Zhou.


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


Repository: cloudstack-git


Description
---

An addition to the tagging support for security group rules: 
https://reviews.apache.org/r/24557/

Displays edit tags icon for every SecurityGroup Ingress/Egress rule and allows 
manage them.


Diffs
-

  ui/scripts/network.js 8a758c8 

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


Testing
---

Tested on latest master (11th of September).

Screenshots are here: https://issues.apache.org/jira/browse/CLOUDSTACK-7525

Tags can be added and deleted from UI in different browsers, no 
exceptions/errors.


Thanks,

Ilia Shakitko

Re: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Rohit Yadav]

On 11-Sep-2014, at 2:06 pm, Erik Weber  wrote:
> The spec requires openjdk 1.6 to build, but you can easily have both 1.6
> and 1.7 installed and have it built with 1.7 if that is your default java,
> am I correct?
>
> I'm not saying this should warrant the vote to fail, just want to mention
> it.

Thanks, you’re right.

I think for 4.4.1 and master/4.5.0 we can fix it to have it built by 1.7 jdk 
and the packages requires 1.7.0 or above when they get installed.

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: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Erik Weber]

On Thu, Sep 11, 2014 at 3:15 PM, Rohit Yadav 
wrote:

>
> On 11-Sep-2014, at 2:06 pm, Erik Weber  wrote:
> > The spec requires openjdk 1.6 to build, but you can easily have both 1.6
> > and 1.7 installed and have it built with 1.7 if that is your default
> java,
> > am I correct?
> >
> > I'm not saying this should warrant the vote to fail, just want to mention
> > it.
>
> Thanks, you’re right.
>
> I think for 4.4.1 and master/4.5.0 we can fix it to have it built by 1.7
> jdk and the packages requires 1.7.0 or above when they get installed.
>
>
Isn't that already done? Ref the change to java 1.7 earlier this year.

the cloud.spec in branch 4.4 requires java7, so I think this only applies
to previous versions, and a note in the build section of the docs is
probably enough.

-- 
Erik

Re: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Erik Weber]

On Thu, Sep 11, 2014 at 3:01 PM, Nux!  wrote:

> Hello,
>
> I've upgraded and it looks ok for now.
> I have used these system VMs
> http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/ and
> added them as systemvm-kvm-4.3 in the Templates.
> I expected them to replace SystemVM Template (KVM), but they are still
> listed as systemvm-kvm-4.3 alongside the old ones.
> Other than that everything seems ok for now.
>
>
Is there an upgrade path from 4.3.0 systemvm template to 4.3.1? Log on to a
newly deployed one and check /etc/cloudstack-version

-- 
Erik

Re: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Wei ZHOU]

As far as I know, there is no systemvm change during upgrade from 4.3.0 to
4.3.1

2014-09-11 15:22 GMT+02:00 Erik Weber :

> On Thu, Sep 11, 2014 at 3:01 PM, Nux!  wrote:
>
> > Hello,
> >
> > I've upgraded and it looks ok for now.
> > I have used these system VMs
> > http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/ and
> > added them as systemvm-kvm-4.3 in the Templates.
> > I expected them to replace SystemVM Template (KVM), but they are still
> > listed as systemvm-kvm-4.3 alongside the old ones.
> > Other than that everything seems ok for now.
> >
> >
> Is there an upgrade path from 4.3.0 systemvm template to 4.3.1? Log on to a
> newly deployed one and check /etc/cloudstack-version
>
> --
> Erik
>

404 Error

[mo]

I am presently getting 404 error when attempting to access the UI. I believe 
it’s due to the version of my Tomcat. However, I am unsure what version I 
should be using. As I seem to have not disabled automatic updates, as such, 
many things have been updated.

Please advise,

Mo

Re: Review Request 25537: [UI][CLOUDSTACK-7525] Add "Edit Tags" functionality to SecurityGroup rules UI

[Wei Zhou]

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

Ship it!


Ship It!

- Wei Zhou


On 九月 11, 2014, 1:06 p.m., Ilia Shakitko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25537/
> ---
> 
> (Updated 九月 11, 2014, 1:06 p.m.)
> 
> 
> Review request for cloudstack, Brian Federle, Ian Duffy, Jessica Wang, Nitin 
> Mehta, Stephen Hoogendijk, and Wei Zhou.
> 
> 
> Bugs: CLOUDSTACK-7525
> https://issues.apache.org/jira/browse/CLOUDSTACK-7525
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> An addition to the tagging support for security group rules: 
> https://reviews.apache.org/r/24557/
> 
> Displays edit tags icon for every SecurityGroup Ingress/Egress rule and 
> allows manage them.
> 
> 
> Diffs
> -
> 
>   ui/scripts/network.js 8a758c8 
> 
> Diff: https://reviews.apache.org/r/25537/diff/
> 
> 
> Testing
> ---
> 
> Tested on latest master (11th of September).
> 
> Screenshots are here: https://issues.apache.org/jira/browse/CLOUDSTACK-7525
> 
> Tags can be added and deleted from UI in different browsers, no 
> exceptions/errors.
> 
> 
> Thanks,
> 
> Ilia Shakitko
> 
>

Re: Review Request 25537: [UI][CLOUDSTACK-7525] Add "Edit Tags" functionality to SecurityGroup rules UI

[Wei Zhou]

> On 九月 11, 2014, 1:48 p.m., Wei Zhou wrote:
> > Ship It!

already committed to master and 4.4 branch

Branch: refs/heads/master
Commit: 281c866206036235790773fbcb86edede0ac739d
Parents: 4f3de02
Author: Ilia Shakitko 
Authored: Thu Sep 11 12:25:09 2014 +0200
Committer: Wei Zhou 
Committed: Thu Sep 11 15:47:21 2014 +0200


- Wei


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


On 九月 11, 2014, 1:06 p.m., Ilia Shakitko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25537/
> ---
> 
> (Updated 九月 11, 2014, 1:06 p.m.)
> 
> 
> Review request for cloudstack, Brian Federle, Ian Duffy, Jessica Wang, Nitin 
> Mehta, Stephen Hoogendijk, and Wei Zhou.
> 
> 
> Bugs: CLOUDSTACK-7525
> https://issues.apache.org/jira/browse/CLOUDSTACK-7525
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> An addition to the tagging support for security group rules: 
> https://reviews.apache.org/r/24557/
> 
> Displays edit tags icon for every SecurityGroup Ingress/Egress rule and 
> allows manage them.
> 
> 
> Diffs
> -
> 
>   ui/scripts/network.js 8a758c8 
> 
> Diff: https://reviews.apache.org/r/25537/diff/
> 
> 
> Testing
> ---
> 
> Tested on latest master (11th of September).
> 
> Screenshots are here: https://issues.apache.org/jira/browse/CLOUDSTACK-7525
> 
> Tags can be added and deleted from UI in different browsers, no 
> exceptions/errors.
> 
> 
> Thanks,
> 
> Ilia Shakitko
> 
>

Re: 404 Error

[Carlos Reátegui]

Tomcat probably got updated and restarted after the update causing the prob. 
Stop tomcat and cloudstack manger then start cloudstack manager again. You 
should be all set. 

> On Sep 11, 2014, at 6:47 AM, mo  wrote:
> 
> I am presently getting 404 error when attempting to access the UI. I believe 
> it’s due to the version of my Tomcat. However, I am unsure what version I 
> should be using. As I seem to have not disabled automatic updates, as such, 
> many things have been updated.
> 
> Please advise,
> 
> Mo
> 

Re: 404 Error

[mo]

Seems that did not work, still getting 404. :-(



On September 11, 2014 at 10:01:28 AM, Carlos Reátegui (create...@gmail.com) 
wrote:

Tomcat probably got updated and restarted after the update causing the prob.  
Stop tomcat and cloudstack manger then start cloudstack manager again. You 
should be all set.  

> On Sep 11, 2014, at 6:47 AM, mo  wrote:  
>  
> I am presently getting 404 error when attempting to access the UI. I believe 
> it’s due to the version of my Tomcat. However, I am unsure what version I 
> should be using. As I seem to have not disabled automatic updates, as such, 
> many things have been updated.  
>  
> Please advise,  
>  
> Mo  
>  

Re: 404 Error

[Wei ZHOU]

try to stop tomcat and then restart management server.

2014-09-11 15:47 GMT+02:00 mo :

> I am presently getting 404 error when attempting to access the UI. I
> believe it’s due to the version of my Tomcat. However, I am unsure what
> version I should be using. As I seem to have not disabled automatic
> updates, as such, many things have been updated.
>
> Please advise,
>
> Mo
>
>

Re: S3/Swift Problem around Virtual Size

[Punith S]

sure mike :)

and it seems in context of managed storage we are creating the SAN volume
before downloading the template from S3 to staging store; means the SAN
volume of false size will be already created before fetching the actual
virtual size of the template !

hence i'm hitting the same issue again, saying not enough space !

so in case of S3 and Swift, shall we reserve minimum size of the SAN volume
for allowing the copy and later shall the admin resize the SAN volume to
his needs?

any thoughts ?

thanks

On Wed, Sep 10, 2014 at 10:18 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Also, of course feel free to put me down as a reviewer when you are ready
> and I can review the code shortly after.
>
> Thanks!
>
> On Wed, Sep 10, 2014 at 10:47 AM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> I have not heard recently on when code freeze for 4.5 is, per se.
>>
>> Regardless, I'd say this is an important-enough issue that we should wait
>> for your patch.
>>
>> We're still in the process of getting 4.3.1 and 4.4.1 out the door, so I
>> think it'll be a bit before 4.5 goes out.
>>
>> Thanks for your time and effort on this, Punith!
>>
>> On Wed, Sep 10, 2014 at 10:32 AM, Punith S 
>> wrote:
>>
>>> yes mike,
>>>
>>> i'm fixing the issue w.r.t option 2.
>>>
>>> testing the patch is consuming much time, since i have to register the
>>> templates via S3, and it has to download via S3 to staging store.
>>>
>>> can i know when is the code freez for 4.5 ?
>>>
>>> thanks!
>>>
>>> On Tue, Sep 9, 2014 at 9:30 PM, Mike Tutkowski <
>>> mike.tutkow...@solidfire.com> wrote:
>>>
 Yeah, either solution will fix this issue for managed storage in
 general (ex. SolidFire, CloudByte).

 On Tue, Sep 9, 2014 at 9:58 AM, Francois Gaudreault <
 fgaudrea...@cloudops.com> wrote:

> That's great Punith :)
>
> Thanks for handling this one. I am not too worried about the option,
> as long as it fixes SF integration for 4.5 :)
>
> FG
>
> On Tue, Sep 9, 2014 at 11:55 AM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> Thanks for the info, Punith!
>>
>> Does that mean you are fixing the issue via Option2?
>>
>> On Tue, Sep 9, 2014 at 7:52 AM, Punith S 
>> wrote:
>>
>>> yes mike,
>>>
>>> w.r.t to option 1:
>>> it will be like creating a VM w.r.t ISO, where admin will have to
>>> specify the os disk(ROOT) disk size.
>>>
>>> for option 2:
>>> i have figured out the issue, post downloading the template to S3,
>>> cloudstack will again download the template from S3 to staging nfs 
>>> store.
>>> here we need to access the file and process it with VHD processor in
>>> order to calculate the virtualsize but we are skipping this process,
>>> hence the virtual size is not being calculated while using the S3 or
>>> swift.
>>>
>>> the templates already present in the staging nfs storage cannot be
>>> applied to this process.
>>>
>>> for option 3:
>>> it's convenient to calculate the template virtual size while it is
>>> being copied from s3 to staged nfs store instead of staged nfs to 
>>> primary,
>>> since admin might be using more than one primary stores.
>>>
>>> i'm fixing the issue, will post the patch ASAP for 4.5.snapshot.
>>>
>>> thanks!
>>>
>>> On Tue, Sep 9, 2014 at 11:13 AM, Mike Tutkowski <
>>> mike.tutkow...@solidfire.com> wrote:
>>>
 By the way, for anyone new to this issue, this is what we're
 referring to here:

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

 On Mon, Sep 8, 2014 at 11:41 PM, Mike Tutkowski <
 mike.tutkow...@solidfire.com> wrote:

> Great :) Then a question might be, "Is it too late in the game to
> interrogate the template to discover its virtual size if we're just 
> about
> to copy the template to primary storage?"
>
> If it's not, this might be the place to run the logic to figure
> out the virtual size.
>
> Really, there are three big possibilities:
>
> 1) Just ask the end user to provide the virtual size (not
> commenting here on what happens for already-uploaded templates)
>
> or
>
> 2) Figure out the virtual size when the template is copied from
> object storage to secondary storage and update the DB with this info 
> (not
> sure what happens if the template has already been copied to
> (secondary-storage) NFS because it was used before)
>
> or
>
> 3) Figure out the virtual size when the template is about to be
> copied from secondary storage to primary storage
>
> On Mon, Sep 8, 2014 at 11:35 PM, Sanjeev Neelarapu <
> sanjeev.neelar...@citrix.com> wrote:
>

Re: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Nux!]

+1 from me then, I deleted the SystemVM and nothing blew up, I can create VMs, 
stop, destroy them, change security groups.


--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro


- Original Message -
> From: "Wei ZHOU" 
> To: dev@cloudstack.apache.org
> Sent: Thursday, 11 September, 2014 2:44:57 PM
> Subject: Re: [VOTE] Release Apache CloudStack 4.3.1 round #4
> 
> As far as I know, there is no systemvm change during upgrade from 4.3.0 to
> 4.3.1
> 
> 2014-09-11 15:22 GMT+02:00 Erik Weber :
> 
> > On Thu, Sep 11, 2014 at 3:01 PM, Nux!  wrote:
> >
> > > Hello,
> > >
> > > I've upgraded and it looks ok for now.
> > > I have used these system VMs
> > > http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/ and
> > > added them as systemvm-kvm-4.3 in the Templates.
> > > I expected them to replace SystemVM Template (KVM), but they are still
> > > listed as systemvm-kvm-4.3 alongside the old ones.
> > > Other than that everything seems ok for now.
> > >
> > >
> > Is there an upgrade path from 4.3.0 systemvm template to 4.3.1? Log on to a
> > newly deployed one and check /etc/cloudstack-version
> >
> > --
> > Erik
> >
> 

Re: 404 Error

[Carlos Reátegui]

Any clues in your logs?

After stopping tomcat and CS make sure nothing is listening on 8080 before 
attempting to start CS. 

> On Sep 11, 2014, at 7:03 AM, mo  wrote:
> 
> Seems that did not work, still getting 404. :-(
> 
> 
> 
>> On September 11, 2014 at 10:01:28 AM, Carlos Reátegui (create...@gmail.com) 
>> wrote:
>> 
>> Tomcat probably got updated and restarted after the update causing the prob. 
>> Stop tomcat and cloudstack manger then start cloudstack manager again. You 
>> should be all set. 
>> 
>> > On Sep 11, 2014, at 6:47 AM, mo  wrote: 
>> > 
>> > I am presently getting 404 error when attempting to access the UI. I 
>> > believe it’s due to the version of my Tomcat. However, I am unsure what 
>> > version I should be using. As I seem to have not disabled automatic 
>> > updates, as such, many things have been updated. 
>> > 
>> > Please advise, 
>> > 
>> > Mo 
>> > 

Jenkins build is still unstable: simulator-singlerun #343

[jenkins]

See 

how to add devcloud

[sandeep khandekar]

Dear cloudstackers,

I am trying to install cloudstack 4.2  developer version from the following
link.
http://docs.cloudstack.apache.org/en/master/developer_guide.html

How to add devcloud?
downloaded and started devcloud on virtualbox,

when I login I cant see primary and secondary storage, default templates
not yet started?
My doubt is do I need to execute the following commands in devcloud or my
management server host
Adding DevCloud as an Hypervisor

Picking up from a clean build:

mvn -Pdeveloper,systemvm clean install
mvn -P developer -pl developer,tools/devcloud -Ddeploydb

 At this stage install marvin similarly than with the simulator:

pip install tools/marvin/dist/Marvin-0.1.0.tar.gz

 Start the management server

mvn -pl client jetty:run

 Then you are going to configure CloudStack to use the running DevCloud
instance:

cd tools/devcloud
python ../marvin/marvin/deployDataCenter.py -i devcloud.cfg

I execute the above commands on host not in devcloud.
My management server is in ubuntu and devcloud is on virtualbox.

How to add secstorage and primary storage after executing the below command

python ../marvin/marvin/deployDataCenter.py -i devcloud.cfg

How to bring ssvm up and how to install tiny linux?

Thank you.

-- 
SANDEEP KHANDEKAR
Assistant Professor
Department of Computer science and engineering
Sreenidhi Institute of science and Technology
Hyderabad

Jenkins build is still unstable: simulator-singlerun #344

[jenkins]

See 

Re: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Erik Weber]

Except heartbleed fix.

I was merely checking if it's even poosible to do an automated upgrade.

The way i know the upgrade process we add some sql magic to check for new
systemvm templates. If that's not made for 4.3.1 it won't do much good to
add it as systemvm-hypervisor-version.

Erik
11. sep. 2014 15:45 skrev "Wei ZHOU"  følgende:

> As far as I know, there is no systemvm change during upgrade from 4.3.0 to
> 4.3.1
>
> 2014-09-11 15:22 GMT+02:00 Erik Weber :
>
> > On Thu, Sep 11, 2014 at 3:01 PM, Nux!  wrote:
> >
> > > Hello,
> > >
> > > I've upgraded and it looks ok for now.
> > > I have used these system VMs
> > > http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/
> and
> > > added them as systemvm-kvm-4.3 in the Templates.
> > > I expected them to replace SystemVM Template (KVM), but they are still
> > > listed as systemvm-kvm-4.3 alongside the old ones.
> > > Other than that everything seems ok for now.
> > >
> > >
> > Is there an upgrade path from 4.3.0 systemvm template to 4.3.1? Log on
> to a
> > newly deployed one and check /etc/cloudstack-version
> >
> > --
> > Erik
> >
>

Re: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Mike Tutkowski]

I have an integration test failing when trying to create a (XenServer)
storage repository.

Let me look into it for an hour or so and then I can respond back as to if
it's a code issue.

I'm thinking now it's a problem with XAPI. At first the code wasn't
compiling due to XAPI changes and now I'm getting this XAPI issue when
trying to create a storage repository. Seems possibly related.

On Thu, Sep 11, 2014 at 10:37 AM, Erik Weber  wrote:

> Except heartbleed fix.
>
> I was merely checking if it's even poosible to do an automated upgrade.
>
> The way i know the upgrade process we add some sql magic to check for new
> systemvm templates. If that's not made for 4.3.1 it won't do much good to
> add it as systemvm-hypervisor-version.
>
> Erik
> 11. sep. 2014 15:45 skrev "Wei ZHOU"  følgende:
>
> > As far as I know, there is no systemvm change during upgrade from 4.3.0
> to
> > 4.3.1
> >
> > 2014-09-11 15:22 GMT+02:00 Erik Weber :
> >
> > > On Thu, Sep 11, 2014 at 3:01 PM, Nux!  wrote:
> > >
> > > > Hello,
> > > >
> > > > I've upgraded and it looks ok for now.
> > > > I have used these system VMs
> > > > http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/
> > and
> > > > added them as systemvm-kvm-4.3 in the Templates.
> > > > I expected them to replace SystemVM Template (KVM), but they are
> still
> > > > listed as systemvm-kvm-4.3 alongside the old ones.
> > > > Other than that everything seems ok for now.
> > > >
> > > >
> > > Is there an upgrade path from 4.3.0 systemvm template to 4.3.1? Log on
> > to a
> > > newly deployed one and check /etc/cloudstack-version
> > >
> > > --
> > > Erik
> > >
> >
>



-- 
*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: [Help] Help for setting up Vmware Cluster in CloudStack...

[Ritu Sabharwal]

Hello CS developers,

I need help in setting up Vmware cluster in CloudStack.

Any help is appreciated!

Thanks & Regards,
Ritu S.

-Original Message-
From: Ritu Sabharwal [mailto:rsabh...@brocade.com] 
Sent: Friday, September 05, 2014 4:51 PM
To: ilya musayev
Cc: dev@cloudstack.apache.org; Adip Shetty
Subject: RE: [Help] Help for setting up Vmware Cluster in CloudStack...

Hi Ilya,

I am trying to do this vmware integration with Cloudstack again but seeing some 
issues. Need your help to move forward.

I followed the steps from the tutorial: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Advanced+Network+Tutorial+-+Step+by+Step

I imported the system template from the location  
http://cloudstack.apt-get.eu/systemvm/systemvm64template-2014-01-14-master-vmware.ova
 by running the command

/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt 
-m /mnt/secondary -u systemvm64template-2014-01-14-master-vmware.ova -h vmware 
-F

Looks like the import did not happen successfully because the ova file created 
under /mnt/secondary/template/tmpl/1/8/ is of size 0.

I followed rest of the steps in the tutorial . All went fine, adding zone, pod, 
cluster, primary storage, secondary storage but the system vms (Secondary 
storage VM and Console Proxy VM)  are not deployed.

Now when I am trying to create a user VM, I don't see any templates available 
to create it.

Please help to unblock me with this setup.

Thanks & Regards,
Ritu S.

From: ilya musayev [mailto:ilya.mailing.li...@gmail.com]
Sent: Wednesday, July 09, 2014 10:53 PM
To: Ritu Sabharwal; Hugo Trippaers
Cc: dev@cloudstack.apache.org
Subject: Re: [Help] Help for setting up Vmware Cluster in CloudStack...

I'm in Sunnyvale. I've been trying to do a meetup and perhaps demo the whole 
vmware/cloudstack setup, but i never really got to do this.

Hopefully, we can put something together for July or early August timeframe for 
the meetup.

Also, Router VMs have 1 Management and 1 Guest IP - just realized i missed it.

If i can give you a suggestion in the meantime, try to get your setup working 
with stable 4.3. Once you figure the process out - which is really not that 
difficult in my opinion (should take 10-30 minutes at most - granted you have 
everything pre-set), then try it with master codebase, and only then master 
codebase and your patch.

You did not mention if you are using VLAN tagging btw. Not that it matters 
greatly, but consider using newer vSphere, you can download trials from VMware 
site, you can even do a nested setup and run many vSphere CloudStack 
environments for dev/qa - which is what i've been doing lately. You have 60 day 
trial, post that, you can reset the environment to be compliant with vmware 
licensing model - needless to say, this can be semi or completely automated, 
depends how much effort you want to put into this. I'd double check this with 
vmware rep to be on the safe side.


On 7/9/14, 5:36 PM, Ritu Sabharwal wrote:
Hi Ilya,

Thanks for your replies.

This is really helpful. We can surely get into some video conferencing and get 
this setup ready. I am in San Jose, CA.

Thanks & Regards,
Ritu S.

From: ilya musayev [mailto:ilya.mailing.li...@gmail.com]
Sent: Wednesday, July 09, 2014 12:58 PM
To: Ritu Sabharwal; Hugo Trippaers
Cc: dev@cloudstack.apache.org
Subject: Re: [Help] Help for setting up Vmware Cluster in CloudStack...

Ritu,

That tutorial is a bit old.

Let me try to answer them, i do have an alternative solution, perhaps we can 
get on the phone and do a webex session or something similar - this week is bad 
for me, i'm traveling, but next week, Thursday and beyond - my schedule is 
flexible. I assume you are on PST timezone somewhere in bay area.

Please see response inline to your inquiries.



On 7/8/14, 6:29 PM, Ritu Sabharwal wrote:


Hi Ilya,

I am trying to add VMWare DC for the first time in CloudStack management server 
and need help in doing so. I am trying to test the Brocade Network Plugin 
functionality. The Jira id is : 
https://issues.apache.org/jira/browse/CLOUDSTACK-6823

I am following the Tutorial: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Advanced+Network+Tutorial+-+Step+by+Step

My Network setup:


1.   2 ESXi hosts 4.1.0 hosts.

2.   vCenter 5.0

Network layout:

vSwitch0: For Management Network
vSwitch0: for Guest Network

vSwitch0 is assigned 1 Physical Nic. This Nic is connected to Brocade VDX 
switch.


My test includes:

 *   Create an isolated network; verify that the port-profile is created on the 
Brocade switch.
 *   Attach a VM to the network; verify that the VMs MAC address is associated 
with the port profile of the network on the Brocade switch.
 *   Add VMs to the same guest network but on different hosts and verify 
connectivity.
 *   Check the availability of the switch by using the CloudStack API: 
http://:8096/client/api?command=listHosts&type=L2Networkin

Re: [Help] Help for setting up Vmware Cluster in CloudStack...

[Amogh Vasekar]

Hi,

The management server logs will help.
Templates for launching user Vms won't be available until SSVM comes up
and downloads them to the correct location.
You may want to confirm if you are using the right systemVM template for
the (4.5?) build. 
Adding Rayees who may be able to point to the right systemVM template.

Thanks,
Amogh

On 9/11/14 11:25 AM, "Ritu Sabharwal"  wrote:

>Hello CS developers,
>
>I need help in setting up Vmware cluster in CloudStack.
>
>Any help is appreciated!
>
>Thanks & Regards,
>Ritu S.
>
>-Original Message-
>From: Ritu Sabharwal [mailto:rsabh...@brocade.com]
>Sent: Friday, September 05, 2014 4:51 PM
>To: ilya musayev
>Cc: dev@cloudstack.apache.org; Adip Shetty
>Subject: RE: [Help] Help for setting up Vmware Cluster in CloudStack...
>
>Hi Ilya,
>
>I am trying to do this vmware integration with Cloudstack again but
>seeing some issues. Need your help to move forward.
>
>I followed the steps from the tutorial:
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Advanced
>+Network+Tutorial+-+Step+by+Step
>
>I imported the system template from the location
>http://cloudstack.apt-get.eu/systemvm/systemvm64template-2014-01-14-master
>-vmware.ova by running the command
>
>/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-t
>mplt -m /mnt/secondary -u systemvm64template-2014-01-14-master-vmware.ova
>-h vmware -F
>
>Looks like the import did not happen successfully because the ova file
>created under /mnt/secondary/template/tmpl/1/8/ is of size 0.
>
>I followed rest of the steps in the tutorial . All went fine, adding
>zone, pod, cluster, primary storage, secondary storage but the system vms
>(Secondary storage VM and Console Proxy VM)  are not deployed.
>
>Now when I am trying to create a user VM, I don't see any templates
>available to create it.
>
>Please help to unblock me with this setup.
>
>Thanks & Regards,
>Ritu S.
>
>From: ilya musayev [mailto:ilya.mailing.li...@gmail.com]
>Sent: Wednesday, July 09, 2014 10:53 PM
>To: Ritu Sabharwal; Hugo Trippaers
>Cc: dev@cloudstack.apache.org
>Subject: Re: [Help] Help for setting up Vmware Cluster in CloudStack...
>
>I'm in Sunnyvale. I've been trying to do a meetup and perhaps demo the
>whole vmware/cloudstack setup, but i never really got to do this.
>
>Hopefully, we can put something together for July or early August
>timeframe for the meetup.
>
>Also, Router VMs have 1 Management and 1 Guest IP - just realized i
>missed it.
>
>If i can give you a suggestion in the meantime, try to get your setup
>working with stable 4.3. Once you figure the process out - which is
>really not that difficult in my opinion (should take 10-30 minutes at
>most - granted you have everything pre-set), then try it with master
>codebase, and only then master codebase and your patch.
>
>You did not mention if you are using VLAN tagging btw. Not that it
>matters greatly, but consider using newer vSphere, you can download
>trials from VMware site, you can even do a nested setup and run many
>vSphere CloudStack environments for dev/qa - which is what i've been
>doing lately. You have 60 day trial, post that, you can reset the
>environment to be compliant with vmware licensing model - needless to
>say, this can be semi or completely automated, depends how much effort
>you want to put into this. I'd double check this with vmware rep to be on
>the safe side.
>
>
>On 7/9/14, 5:36 PM, Ritu Sabharwal wrote:
>Hi Ilya,
>
>Thanks for your replies.
>
>This is really helpful. We can surely get into some video conferencing
>and get this setup ready. I am in San Jose, CA.
>
>Thanks & Regards,
>Ritu S.
>
>From: ilya musayev [mailto:ilya.mailing.li...@gmail.com]
>Sent: Wednesday, July 09, 2014 12:58 PM
>To: Ritu Sabharwal; Hugo Trippaers
>Cc: dev@cloudstack.apache.org
>Subject: Re: [Help] Help for setting up Vmware Cluster in CloudStack...
>
>Ritu,
>
>That tutorial is a bit old.
>
>Let me try to answer them, i do have an alternative solution, perhaps we
>can get on the phone and do a webex session or something similar - this
>week is bad for me, i'm traveling, but next week, Thursday and beyond -
>my schedule is flexible. I assume you are on PST timezone somewhere in
>bay area.
>
>Please see response inline to your inquiries.
>
>
>
>On 7/8/14, 6:29 PM, Ritu Sabharwal wrote:
>
>
>Hi Ilya,
>
>I am trying to add VMWare DC for the first time in CloudStack management
>server and need help in doing so. I am trying to test the Brocade Network
>Plugin functionality. The Jira id is :
>https://issues.apache.org/jira/browse/CLOUDSTACK-6823
>
>I am following the Tutorial:
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Advanced
>+Network+Tutorial+-+Step+by+Step
>
>My Network setup:
>
>
>1.   2 ESXi hosts 4.1.0 hosts.
>
>2.   vCenter 5.0
>
>Network layout:
>
>vSwitch0: For Management Network
>vSwitch0: for Guest Network
>
>vSwitch0 is assigned 1 Physical Nic. This Nic is connected to Bro

Re: Review Request 22147: CLOUDSTACK-6722: Fix: [OVS][UI] Network created with StretchedL2Subnet is not available for vm deployement in other zones

[Brian Federle]

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

Ship it!


Ship It!

- Brian Federle


On June 2, 2014, 5:10 p.m., Gabor Apati-Nagy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/22147/
> ---
> 
> (Updated June 2, 2014, 5:10 p.m.)
> 
> 
> Review request for cloudstack, Brian Federle and Jessica Wang.
> 
> 
> Bugs: CLOUDSTACK-6722
> https://issues.apache.org/jira/browse/CLOUDSTACK-6722
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fix for CLOUDSTACK-6722: [OVS][UI] Network created with StretchedL2Subnet is 
> not available for vm deployement in other zones
> 
> 
> Diffs
> -
> 
>   ui/scripts/instanceWizard.js 9df6ecc 
> 
> Diff: https://reviews.apache.org/r/22147/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gabor Apati-Nagy
> 
>

Re: Review Request 22143: CLOUDSTACK-6725: Fix: [OVS][UI] vm deployment wizard does not show all available zones in a region while deploying vm in a Regionlevel vpc

[Brian Federle]

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

Ship it!


Ship It!

- Brian Federle


On June 2, 2014, 5:07 p.m., Gabor Apati-Nagy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/22143/
> ---
> 
> (Updated June 2, 2014, 5:07 p.m.)
> 
> 
> Review request for cloudstack, Brian Federle and Jessica Wang.
> 
> 
> Bugs: CLOUDSTACK-6725
> https://issues.apache.org/jira/browse/CLOUDSTACK-6725
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fix for CLOUDSTACK-6725 [OVS][UI] vm deployment wizard does not show all 
> available zones in a region while deploying vm in a Regionlevel vpc 
> 
> 
> Diffs
> -
> 
>   ui/scripts/instanceWizard.js 9df6ecc 
> 
> Diff: https://reviews.apache.org/r/22143/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gabor Apati-Nagy
> 
>

Jenkins build is still unstable: simulator-singlerun #345

[jenkins]

See 

Re: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Mike Tutkowski]

OK, I looked into this more.

It turns out the regression test that was failing is only valid in 4.4 and
beyond, so it is not a valid test for 4.3.

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

> I have an integration test failing when trying to create a (XenServer)
> storage repository.
>
> Let me look into it for an hour or so and then I can respond back as to if
> it's a code issue.
>
> I'm thinking now it's a problem with XAPI. At first the code wasn't
> compiling due to XAPI changes and now I'm getting this XAPI issue when
> trying to create a storage repository. Seems possibly related.
>
> On Thu, Sep 11, 2014 at 10:37 AM, Erik Weber  wrote:
>
>> Except heartbleed fix.
>>
>> I was merely checking if it's even poosible to do an automated upgrade.
>>
>> The way i know the upgrade process we add some sql magic to check for new
>> systemvm templates. If that's not made for 4.3.1 it won't do much good to
>> add it as systemvm-hypervisor-version.
>>
>> Erik
>> 11. sep. 2014 15:45 skrev "Wei ZHOU"  følgende:
>>
>> > As far as I know, there is no systemvm change during upgrade from 4.3.0
>> to
>> > 4.3.1
>> >
>> > 2014-09-11 15:22 GMT+02:00 Erik Weber :
>> >
>> > > On Thu, Sep 11, 2014 at 3:01 PM, Nux!  wrote:
>> > >
>> > > > Hello,
>> > > >
>> > > > I've upgraded and it looks ok for now.
>> > > > I have used these system VMs
>> > > >
>> http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/
>> > and
>> > > > added them as systemvm-kvm-4.3 in the Templates.
>> > > > I expected them to replace SystemVM Template (KVM), but they are
>> still
>> > > > listed as systemvm-kvm-4.3 alongside the old ones.
>> > > > Other than that everything seems ok for now.
>> > > >
>> > > >
>> > > Is there an upgrade path from 4.3.0 systemvm template to 4.3.1? Log on
>> > to a
>> > > newly deployed one and check /etc/cloudstack-version
>> > >
>> > > --
>> > > Erik
>> > >
>> >
>>
>
>
>
> --
> *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: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Wei ZHOU]

Sorry I just notice Rohit made a systemvm template change (commit
3a0f1550289a8a2a50b0f786821cec2e5c914e62) on 9th, September.
The systemvm template will be built based on debian 7.5.0 instead of 7.4.0



==

commit 3a0f1550289a8a2a50b0f786821cec2e5c914e62
Author: Rohit Yadav 
Date:   Tue Sep 9 18:37:15 2014 +0200

appliance: fix newer debian iso links and checksums for debian

Signed-off-by: Rohit Yadav 
(cherry picked from commit ac5309b8b47ddb1e5588a2d5090f2bcce0e7c2a4)

Conflicts:
tools/appliance/definitions/systemvm64template/definition.rb
tools/appliance/definitions/systemvmtemplate/definition.rb

diff --git a/tools/appliance/definitions/systemvm64template/definition.rb
b/tools/appliance/definitions/systemvm64template/definition.rb
index f9308a0..bd59025 100644
--- a/tools/appliance/definitions/systemvm64template/definition.rb
+++ b/tools/appliance/definitions/systemvm64template/definition.rb
@@ -3,9 +3,9 @@ Veewee::Definition.declare({
   :memory_size=> '256',
   :disk_size => '2500', :disk_format => 'VDI', :hostiocache => 'off',
   :os_type_id => 'Debian_64',
-  :iso_file => "debian-7.4.0-amd64-netinst.iso",
-  :iso_src => "
http://cdimage.debian.org/mirror/cdimage/archive/7.4.0/amd64/iso-cd/debian-7.4.0-amd64-netinst.iso
",
-  :iso_md5 => "e7e9433973f082a297793c3c5010b2c5",
+  :iso_file => "debian-7.5.0-amd64-netinst.iso",
+  :iso_src => "
http://cdimage.debian.org/mirror/cdimage/archive/7.5.0/amd64/iso-cd/debian-7.5.0-amd64-netinst.iso
",
+  :iso_md5 => "8fdb6715228ea90faba58cb84644d296",
   :iso_download_timeout => "1000",
   :boot_wait => "10", :boot_cmd_sequence => [
  '',
diff --git a/tools/appliance/definitions/systemvmtemplate/definition.rb
b/tools/appliance/definitions/systemvmtemplate/definition.rb
index fcaab4d..9b57379 100644
--- a/tools/appliance/definitions/systemvmtemplate/definition.rb
+++ b/tools/appliance/definitions/systemvmtemplate/definition.rb
@@ -3,9 +3,9 @@ Veewee::Definition.declare({
   :memory_size=> '256',
   :disk_size => '2500', :disk_format => 'VDI', :hostiocache => 'off',
   :os_type_id => 'Debian',
-  :iso_file => "debian-7.4.0-i386-netinst.iso",
-  :iso_src => "
http://cdimage.debian.org/mirror/cdimage/archive/7.4.0/i386/iso-cd/debian-7.4.0-i386-netinst.iso
",
-  :iso_md5 => "7339b668a81b417ac023d73739dc6a03",
+  :iso_file => "debian-7.5.0-i386-netinst.iso",
+  :iso_src => "
http://cdimage.debian.org/mirror/cdimage/archive/7.5.0/i386/iso-cd/debian-7.5.0-i386-netinst.iso
",
+  :iso_md5 => "0e6eaacb5a5828473afe90f6df9c8f16",
   :iso_download_timeout => "1000",
   :boot_wait => "10", :boot_cmd_sequence => [
  '',


2014-09-11 21:50 GMT+02:00 Sebastien Goasguen :

>
> On Sep 11, 2014, at 3:47 PM, Mike Tutkowski 
> wrote:
>
> > OK, I looked into this more.
> >
> > It turns out the regression test that was failing is only valid in 4.4
> and
> > beyond, so it is not a valid test for 4.3.
> >
>
> so can you vote ? we need your binding vote :)
>
> > On Thu, Sep 11, 2014 at 11:14 AM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com> wrote:
> >
> >> I have an integration test failing when trying to create a (XenServer)
> >> storage repository.
> >>
> >> Let me look into it for an hour or so and then I can respond back as to
> if
> >> it's a code issue.
> >>
> >> I'm thinking now it's a problem with XAPI. At first the code wasn't
> >> compiling due to XAPI changes and now I'm getting this XAPI issue when
> >> trying to create a storage repository. Seems possibly related.
> >>
> >> On Thu, Sep 11, 2014 at 10:37 AM, Erik Weber 
> wrote:
> >>
> >>> Except heartbleed fix.
> >>>
> >>> I was merely checking if it's even poosible to do an automated upgrade.
> >>>
> >>> The way i know the upgrade process we add some sql magic to check for
> new
> >>> systemvm templates. If that's not made for 4.3.1 it won't do much good
> to
> >>> add it as systemvm-hypervisor-version.
> >>>
> >>> Erik
> >>> 11. sep. 2014 15:45 skrev "Wei ZHOU"  følgende:
> >>>
>  As far as I know, there is no systemvm change during upgrade from
> 4.3.0
> >>> to
>  4.3.1
> 
>  2014-09-11 15:22 GMT+02:00 Erik Weber :
> 
> > On Thu, Sep 11, 2014 at 3:01 PM, Nux!  wrote:
> >
> >> Hello,
> >>
> >> I've upgraded and it looks ok for now.
> >> I have used these system VMs
> >>
> >>> http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/
>  and
> >> added them as systemvm-kvm-4.3 in the Templates.
> >> I expected them to replace SystemVM Template (KVM), but they are
> >>> still
> >> listed as systemvm-kvm-4.3 alongside the old ones.
> >> Other than that everything seems ok for now.
> >>
> >>
> > Is there an upgrade path from 4.3.0 systemvm template to 4.3.1? Log
> on
>  to a
> > newly deployed one and check /etc/cloudstack-version
> >
> > --
> > Erik
> >
> 
> >>>
> >>
> >>
> >>
> >> --
> >> *Mike Tutkowski*
> >> *Senior CloudStack Developer, SolidFire Inc.*

Re: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Sebastien Goasguen]

On Sep 11, 2014, at 3:47 PM, Mike Tutkowski  
wrote:

> OK, I looked into this more.
> 
> It turns out the regression test that was failing is only valid in 4.4 and
> beyond, so it is not a valid test for 4.3.
> 

so can you vote ? we need your binding vote :)

> On Thu, Sep 11, 2014 at 11:14 AM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
> 
>> I have an integration test failing when trying to create a (XenServer)
>> storage repository.
>> 
>> Let me look into it for an hour or so and then I can respond back as to if
>> it's a code issue.
>> 
>> I'm thinking now it's a problem with XAPI. At first the code wasn't
>> compiling due to XAPI changes and now I'm getting this XAPI issue when
>> trying to create a storage repository. Seems possibly related.
>> 
>> On Thu, Sep 11, 2014 at 10:37 AM, Erik Weber  wrote:
>> 
>>> Except heartbleed fix.
>>> 
>>> I was merely checking if it's even poosible to do an automated upgrade.
>>> 
>>> The way i know the upgrade process we add some sql magic to check for new
>>> systemvm templates. If that's not made for 4.3.1 it won't do much good to
>>> add it as systemvm-hypervisor-version.
>>> 
>>> Erik
>>> 11. sep. 2014 15:45 skrev "Wei ZHOU"  følgende:
>>> 
 As far as I know, there is no systemvm change during upgrade from 4.3.0
>>> to
 4.3.1
 
 2014-09-11 15:22 GMT+02:00 Erik Weber :
 
> On Thu, Sep 11, 2014 at 3:01 PM, Nux!  wrote:
> 
>> Hello,
>> 
>> I've upgraded and it looks ok for now.
>> I have used these system VMs
>> 
>>> http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/
 and
>> added them as systemvm-kvm-4.3 in the Templates.
>> I expected them to replace SystemVM Template (KVM), but they are
>>> still
>> listed as systemvm-kvm-4.3 alongside the old ones.
>> Other than that everything seems ok for now.
>> 
>> 
> Is there an upgrade path from 4.3.0 systemvm template to 4.3.1? Log on
 to a
> newly deployed one and check /etc/cloudstack-version
> 
> --
> Erik
> 
 
>>> 
>> 
>> 
>> 
>> --
>> *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: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Sebastien Goasguen]

On Sep 11, 2014, at 3:56 PM, Wei ZHOU  wrote:

> Sorry I just notice Rohit made a systemvm template change (commit
> 3a0f1550289a8a2a50b0f786821cec2e5c914e62) on 9th, September.
> The systemvm template will be built based on debian 7.5.0 instead of 7.4.0
> 

Wei, can you test and vote ? that would be great

> 
> 
> ==
> 
> commit 3a0f1550289a8a2a50b0f786821cec2e5c914e62
> Author: Rohit Yadav 
> Date:   Tue Sep 9 18:37:15 2014 +0200
> 
>appliance: fix newer debian iso links and checksums for debian
> 
>Signed-off-by: Rohit Yadav 
>(cherry picked from commit ac5309b8b47ddb1e5588a2d5090f2bcce0e7c2a4)
> 
>Conflicts:
>tools/appliance/definitions/systemvm64template/definition.rb
>tools/appliance/definitions/systemvmtemplate/definition.rb
> 
> diff --git a/tools/appliance/definitions/systemvm64template/definition.rb
> b/tools/appliance/definitions/systemvm64template/definition.rb
> index f9308a0..bd59025 100644
> --- a/tools/appliance/definitions/systemvm64template/definition.rb
> +++ b/tools/appliance/definitions/systemvm64template/definition.rb
> @@ -3,9 +3,9 @@ Veewee::Definition.declare({
>   :memory_size=> '256',
>   :disk_size => '2500', :disk_format => 'VDI', :hostiocache => 'off',
>   :os_type_id => 'Debian_64',
> -  :iso_file => "debian-7.4.0-amd64-netinst.iso",
> -  :iso_src => "
> http://cdimage.debian.org/mirror/cdimage/archive/7.4.0/amd64/iso-cd/debian-7.4.0-amd64-netinst.iso
> ",
> -  :iso_md5 => "e7e9433973f082a297793c3c5010b2c5",
> +  :iso_file => "debian-7.5.0-amd64-netinst.iso",
> +  :iso_src => "
> http://cdimage.debian.org/mirror/cdimage/archive/7.5.0/amd64/iso-cd/debian-7.5.0-amd64-netinst.iso
> ",
> +  :iso_md5 => "8fdb6715228ea90faba58cb84644d296",
>   :iso_download_timeout => "1000",
>   :boot_wait => "10", :boot_cmd_sequence => [
>  '',
> diff --git a/tools/appliance/definitions/systemvmtemplate/definition.rb
> b/tools/appliance/definitions/systemvmtemplate/definition.rb
> index fcaab4d..9b57379 100644
> --- a/tools/appliance/definitions/systemvmtemplate/definition.rb
> +++ b/tools/appliance/definitions/systemvmtemplate/definition.rb
> @@ -3,9 +3,9 @@ Veewee::Definition.declare({
>   :memory_size=> '256',
>   :disk_size => '2500', :disk_format => 'VDI', :hostiocache => 'off',
>   :os_type_id => 'Debian',
> -  :iso_file => "debian-7.4.0-i386-netinst.iso",
> -  :iso_src => "
> http://cdimage.debian.org/mirror/cdimage/archive/7.4.0/i386/iso-cd/debian-7.4.0-i386-netinst.iso
> ",
> -  :iso_md5 => "7339b668a81b417ac023d73739dc6a03",
> +  :iso_file => "debian-7.5.0-i386-netinst.iso",
> +  :iso_src => "
> http://cdimage.debian.org/mirror/cdimage/archive/7.5.0/i386/iso-cd/debian-7.5.0-i386-netinst.iso
> ",
> +  :iso_md5 => "0e6eaacb5a5828473afe90f6df9c8f16",
>   :iso_download_timeout => "1000",
>   :boot_wait => "10", :boot_cmd_sequence => [
>  '',
> 
> 
> 2014-09-11 21:50 GMT+02:00 Sebastien Goasguen :
> 
>> 
>> On Sep 11, 2014, at 3:47 PM, Mike Tutkowski 
>> wrote:
>> 
>>> OK, I looked into this more.
>>> 
>>> It turns out the regression test that was failing is only valid in 4.4
>> and
>>> beyond, so it is not a valid test for 4.3.
>>> 
>> 
>> so can you vote ? we need your binding vote :)
>> 
>>> On Thu, Sep 11, 2014 at 11:14 AM, Mike Tutkowski <
>>> mike.tutkow...@solidfire.com> wrote:
>>> 
 I have an integration test failing when trying to create a (XenServer)
 storage repository.
 
 Let me look into it for an hour or so and then I can respond back as to
>> if
 it's a code issue.
 
 I'm thinking now it's a problem with XAPI. At first the code wasn't
 compiling due to XAPI changes and now I'm getting this XAPI issue when
 trying to create a storage repository. Seems possibly related.
 
 On Thu, Sep 11, 2014 at 10:37 AM, Erik Weber 
>> wrote:
 
> Except heartbleed fix.
> 
> I was merely checking if it's even poosible to do an automated upgrade.
> 
> The way i know the upgrade process we add some sql magic to check for
>> new
> systemvm templates. If that's not made for 4.3.1 it won't do much good
>> to
> add it as systemvm-hypervisor-version.
> 
> Erik
> 11. sep. 2014 15:45 skrev "Wei ZHOU"  følgende:
> 
>> As far as I know, there is no systemvm change during upgrade from
>> 4.3.0
> to
>> 4.3.1
>> 
>> 2014-09-11 15:22 GMT+02:00 Erik Weber :
>> 
>>> On Thu, Sep 11, 2014 at 3:01 PM, Nux!  wrote:
>>> 
 Hello,
 
 I've upgraded and it looks ok for now.
 I have used these system VMs
 
> http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/
>> and
 added them as systemvm-kvm-4.3 in the Templates.
 I expected them to replace SystemVM Template (KVM), but they are
> still
 listed as systemvm-kvm-4.3 alongside the old ones.
 Other than that everything seems ok for now.
 
 
>>> Is there an upgrade path from 4.3.0 syste

Re: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Mike Tutkowski]

Based on my regression testing, I am +1.

On Thu, Sep 11, 2014 at 1:50 PM, Sebastien Goasguen 
wrote:

>
> On Sep 11, 2014, at 3:47 PM, Mike Tutkowski 
> wrote:
>
> > OK, I looked into this more.
> >
> > It turns out the regression test that was failing is only valid in 4.4
> and
> > beyond, so it is not a valid test for 4.3.
> >
>
> so can you vote ? we need your binding vote :)
>
> > On Thu, Sep 11, 2014 at 11:14 AM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com> wrote:
> >
> >> I have an integration test failing when trying to create a (XenServer)
> >> storage repository.
> >>
> >> Let me look into it for an hour or so and then I can respond back as to
> if
> >> it's a code issue.
> >>
> >> I'm thinking now it's a problem with XAPI. At first the code wasn't
> >> compiling due to XAPI changes and now I'm getting this XAPI issue when
> >> trying to create a storage repository. Seems possibly related.
> >>
> >> On Thu, Sep 11, 2014 at 10:37 AM, Erik Weber 
> wrote:
> >>
> >>> Except heartbleed fix.
> >>>
> >>> I was merely checking if it's even poosible to do an automated upgrade.
> >>>
> >>> The way i know the upgrade process we add some sql magic to check for
> new
> >>> systemvm templates. If that's not made for 4.3.1 it won't do much good
> to
> >>> add it as systemvm-hypervisor-version.
> >>>
> >>> Erik
> >>> 11. sep. 2014 15:45 skrev "Wei ZHOU"  følgende:
> >>>
>  As far as I know, there is no systemvm change during upgrade from
> 4.3.0
> >>> to
>  4.3.1
> 
>  2014-09-11 15:22 GMT+02:00 Erik Weber :
> 
> > On Thu, Sep 11, 2014 at 3:01 PM, Nux!  wrote:
> >
> >> Hello,
> >>
> >> I've upgraded and it looks ok for now.
> >> I have used these system VMs
> >>
> >>> http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/
>  and
> >> added them as systemvm-kvm-4.3 in the Templates.
> >> I expected them to replace SystemVM Template (KVM), but they are
> >>> still
> >> listed as systemvm-kvm-4.3 alongside the old ones.
> >> Other than that everything seems ok for now.
> >>
> >>
> > Is there an upgrade path from 4.3.0 systemvm template to 4.3.1? Log
> on
>  to a
> > newly deployed one and check /etc/cloudstack-version
> >
> > --
> > Erik
> >
> 
> >>>
> >>
> >>
> >>
> >> --
> >> *Mike Tutkowski*
> >> *Senior CloudStack Developer, SolidFire Inc.*
> >> e: mike.tutkow...@solidfire.com
> >> o: 303.746.7302
> >> Advancing the way the world uses the cloud
> >> *™*
> >>
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the cloud
> > *™*
>
>


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

Jenkins build is still unstable: simulator-singlerun #346

[jenkins]

See 

Jenkins build is still unstable: simulator-singlerun #347

[jenkins]

See 

[GitHub] cloudstack pull request: VPC and Virtual Network Managers refactor...

[wilderrodrigues]

Github user wilderrodrigues closed the pull request at:

https://github.com/apache/cloudstack/pull/18


---
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.
---

[GitHub] cloudstack pull request: VPC and Virtual Network Managers refactor...

[wilderrodrigues]

Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/18#issuecomment-55340207
  
Closing this PR because it was not working properly due to another PR, 
which has alsch creation. Will openmulator and a which has also been tested on 
the simulator and a host with xenserver + xentools


---
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.
---

[GitHub] cloudstack pull request: VPC and Virtual Network Managers refactor...

[wilderrodrigues]

GitHub user wilderrodrigues opened a pull request:

https://github.com/apache/cloudstack/pull/19

VPC and Virtual Network Managers refactor. Part of the VPC Redundant Router 
work

This is a new Pull Request in order to fix the conflicts we found in the 
old pull request #14 . I will put the most update version of the description 
here:

Pull request of changes in the "cloud-server" module

In the last 10 weeks we have worked in the cloud-server, focusing our time 
in the refactor of the [Vpc]VirtualNetworkApplianceManagerImpl. We had a mains 
goals increase of Maintainability, Extensibility, Readability and test 
coverage. That was just a first step towards the development, still in 
progress, of the Redundant Virtual Routers for VPC.

== What has been done so far:

• The VirtualNetworkApplianceManagerImpl class line numbers dropped from 
4440 to 2558
• The VpcVirtualNetworkApplianceImpl class line numbers dropped from 1484 
to 749
• We created 35 new classes in order to split the code/responsibility
• We added 97.8% unit test coverage for com.cloud.network.element/router 
and org.cloud.network.router.deployment packages
o The most complex classes we changed are in those packages
o About 1700 lines of unit tests
• We executed many Marvin tests that we got from ACS and made compliant 
with our domain:
o test_01_create_account
o test_01_add_vm_to_subdomain
o test_DeleteDomain
o test_forceDeleteDomain
o test_updateAdminDetails
o test_updateDomainAdminDetails
o test_updateUserDetails
o test_LoginApiDomain
o test_LoginApiUuidResponse
o test_privategw_acl
o test_01_reset_vm_on_reboot
o test_03_restart_network_cleanup
o test_05_router_basic
o test_06_router_advanced
o test_07_stop_router
o test_08_start_router
o test_09_reboot_router
o test_01_create_service_offering
o test_02_edit_service_offering
o test_03_delete_service_offering
o test_01_start_stop_router_after_addition_of_one_guest_network
o test_02_reboot_router_after_addition_of_one_guest_network
o test_04_chg_srv_off_router_after_addition_of_one_guest_network
o test_05_destroy_router_after_addition_of_one_guest_network
o test_01_stop_start_router_after_creating_vpc
o test_02_reboot_router_after_creating_vpc
o test_04_change_service_offerring_vpc
o test_05_destroy_router_after_creating_vpc
o test_vpc_remote_access_vpn
o test_vpc_site2site_vpn

We started the changes in the network area, trying to identify the 
differences in the 2 types of network we have. For that we created Basic and 
Advanced Network Topology classes. The network topology classes are responsible 
by invoking the Apply/Setup/Create/Save rules that were previously done by the 
[Vpc]VirtualNetworkAppliance. A topology instance is retrieved via a context 
object that is injected in the [Vpc]VirtualElement. The context object will 
return the most appropriate topology instance based on the Network Type, which 
is defined in the Data Centre. That was the first step towards the refactor.

From the topology class we reach the Rule Applier implementation that will 
be used to do all the rule setup preparation (i.e. invoke DAOs and prepare the 
command object). The RuleApplier interface was extracted from the 
VirtualNetworkApplianceManagerImpl, where it use to be an inner interface. For 
each anonymous implementation of the RuleApplier we created a concrete class. 
The rules are used as elements of a Visitor class, which will perform some 
extra logic, depending on the rule it's visiting, and call the send commands to 
router method. The latter has also been extracted from the 
VirtualNetworkApplianceManagerImpl and is now in a new helper class: 
NetworkHelperImpl.

The visitor has been used because we were aiming to split the 
responsibility and also because the way the RuleApplier was implemented before, 
it was clear that every command sent to the router was following a 2-steps 
approach: gather information to create the commands, apply some logic to send 
to the router. For those reason we implemented the visitor pattern. Since we 
already had the Basic/Advanced Network Topology classes, we created 2 concrete 
classes to visit the rules: Basic/Advanced Network Visitors. Both classes 
extend the abstract class NetworkTopologyVisitor, which defines all the visit 
methods per type of rule. By doing so, we can use the same rule and separate 
the logic based on the type of visitor that we have - Basic or Advanced.

Continuing on the refactor, we also added some helper classes for the 
"getSomething" related methods. Following this approach we ended up having the 
following classes:

• NetworkHelper (interface)
• NetworkHelperImpl
• VpcNetworkHelperImpl
• CommandSetupHelper
• NicProfileHelper
• RouterControlHelper

Last, bu

Re: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Rohit Yadav]

HI,

On 11-Sep-2014, at 9:56 pm, Wei ZHOU  wrote:
> Sorry I just notice Rohit made a systemvm template change (commit
> 3a0f1550289a8a2a50b0f786821cec2e5c914e62) on 9th, September.
> The systemvm template will be built based on debian 7.5.0 instead of 7.4.0

The quoted commit and changes to use 7.5.0 instead of 7.4.0 was done on 4.4 and 
master branches. On 4.3 branch it was changes from 7.0.0 to 7.5.0. This does 
not change the systemvms internal packages but save some bandwidth while 
building them (and have the latest stable kernel from 7.5.0) because we do a 
apt-get update before installing packages 
(tools/appliances/systemvm**/postinstall.sh). Other than this the only major 
change in systemvms was apache rewrite rules from CLOUDSTACK-7405 fix. So, 
while using 4.3.1 systemvms is recommended but not mandatory.

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: [TRAVIS] - failing for pull request #18

[Wilder Rodrigues]

Hi Ian,

I closed the old PR and created a new one, based on a new branch containing all 
the changes (including the commit from Frank Zhang for the CLOUDSTACK-6278 
Baremetal Advanced Networking support with commit id 
e06fa18ed2ee2ee6a417e089cf5ac6bde11d0079).

Except for the vm life cycle tests (which is failing for everybody), all the 
tests are green. You can see the results here: 
https://travis-ci.org/apache/cloudstack/builds/35069594

The pull request can be found here: https://github.com/apache/cloudstack/pull/19

If anyone else wants to do a review, please do not hesitate.
Everything was tested using the Simulator and my environment:

Cheers,
Wilder

From: Wilder Rodrigues
Sent: donderdag 11 september 2014 11:25
To: 'Ian Duffy'
Cc: CloudStack Dev; int-toolkit; int-cloud
Subject: RE: [TRAVIS] - failing for pull request #18

Hi Ian,

One job is fixed. What happened? I would say one should not stay awake until 
2AM doing cloudstack. ;) There were things I did not push, sorry by that.

Concerning the other 2 jobs, I just got the simulator environment running and 
already found the reason why they are failing. In the refactor of the 
deployRouter() method, the code related to the support hypervisor has changed 
in term of behaviour. The refactor should have been done in 2 steps: first 
restructure the code; then make it better. Along our hard 10 weeks of work 
those 2 steps were mix[messed]-up a bit.

Sorry for bothering you with that, I will fix it.

Cheers,
Wilder


From: Wilder Rodrigues
Sent: Wednesday, September 10, 2014 12:44 PM
To: 'Ian Duffy'
Cc: CloudStack Dev; int-toolkit; int-cloud
Subject: RE: [TRAVIS] - failing for pull request #18

Okay…

I’m cloning it in a different place, just to make sure I follow the same steps 
as you.

Once I get it tested… will share my thoughts again. ☺

Thanks again for the support.

Cheers,
Wilder

From: Ian Duffy [mailto:i...@ianduffy.ie]
Sent: woensdag 10 september 2014 12:06
To: Wilder Rodrigues
Cc: CloudStack Dev; int-toolkit; int-cloud
Subject: Re: [TRAVIS] - failing for pull request #18

> You clone the “test-cmd-rebase” branch,  right?

Yes positive:
$ git status
On branch test-cmd-rebase
Your branch is up-to-date with 'origin/test-cmd-rebase'.

Try your work against the simulator.

On 10 September 2014 10:44, Wilder Rodrigues 
mailto:wrodrig...@schubergphilis.com>> wrote:
Thanks Ian,

I will follow the same steps, because it’s really weird.

I’m running with mvn –pl :cloud-ui jetty:run, but no simulator.

Accounts page looks fine, I even executed the accounts related tests. Advance 
zone was also deployed successfully.

The data form my accounts page:

admin  Admin  ROOT  enabled
baremetal-system-account User ROOT  enabled
test-a-TestVpcRemoteAccessVpn-4SYLK3   User ROOT  enabled
test-a-TestVpcRemoteAccessVpn-5WDDUJ User ROOT  enabled

You clone the “test-cmd-rebase” branch,  right?

I was busy running all the tests I have again, the result was successful and I 
also kept tracking the “running.txt” Marvin log file during execution.

The only difference IPs I have in the advanced.cfg, because I do not use the 
ranges that are there.



Test Create Account and user for that account ... === TestName: 
test_01_create_account | Status : SUCCESS ===
ok
Test Sub domain allowed to launch VM  when a Domain level zone is created ... 
=== TestName: test_01_add_vm_to_subdomain | Status : SUCCESS ===
ok
Test delete domain without force option ... === TestName: test_DeleteDomain | 
Status : SUCCESS ===
ok
Test delete domain with force option ... === TestName: test_forceDeleteDomain | 
Status : SUCCESS ===
ok
Test update admin details ... === TestName: test_updateAdminDetails | Status : 
SUCCESS ===
ok
Test update domain admin details ... === TestName: 
test_updateDomainAdminDetails | Status : SUCCESS ===
ok
Test user update API ... === TestName: test_updateUserDetails | Status : 
SUCCESS ===
ok
Test login API with domain ... === TestName: test_LoginApiDomain | Status : 
SUCCESS ===
ok
Test if Login API does not return UUID's ... === TestName: 
test_LoginApiUuidResponse | Status : SUCCESS ===
ok

--
Ran 9 tests in 832.310s

OK

test_privategw_acl (ekholabs.acs.tests.test_privategw_acl.TestPrivateGwACL) ... 
=== TestName: test_privategw_acl | Status : SUCCESS ===
ok

--
Ran 1 test in 100.582s

OK

Test reset virtual machine on reboot ... === TestName: 
test_01_reset_vm_on_reboot | Status : SUCCESS ===
ok

--
Ran 1 test in 183.507s

OK

Test router internal basic zone ... SKIP: Marvin configuration has no host 
credentials to check router services
Test router internal advanced zone ... SKIP: Marvin configuration has no host 
credentials to check router services
Test restart network ... === TestName: test_03_restart_network_cleanup | Status 
: SUCCESS ==

[ACS441][ACS431] Release-notes

[Pierre-Luc Dion]

Hi Daan,

could you create following public Jira filter to start Release-Notes for
4.3.1 and 4.4.1.

4.4.1 fixed
project = CLOUDSTACK AND type = Bug AND fixVersion = 4.4.1 AND resolution
!= "\"Unresolved\"" ORDER BY created DESC, priority DESC, key ASC

4.4.1 known
project = CLOUDSTACK AND type = Bug AND (affectedVersion = 4.4.1 or
affectedVersion = 4.4.0) AND resolution is EMPTY AND level = "Public" ORDER
BY priority DESC, key ASC

4.3.1 fixed
project = CLOUDSTACK AND type = Bug AND fixVersion = 4.3.1 AND resolution
!= "\"Unresolved\"" ORDER BY created DESC, priority DESC, key ASC

4.3.1 known
project = CLOUDSTACK AND type = Bug AND (affectedVersion = 4.3.1 or
affectedVersion = 4.3.0) AND resolution is EMPTY AND level = "Public" ORDER
BY priority DESC, key ASC


Also , does anyone is working on RN of 4.4.1 or 4.3.1? I can work on 4.4.1,
maybe on the 4.3.1.

Re: [ACS441][ACS431] Release-notes

[Pierre-Luc Dion]

Sorry I've sent this email too fast,

Also, should we removed untested upgrade path on those Release-notes?

Thanks,


*Pierre-Luc DION*
Architecte de Solution Cloud | Cloud Solutions Architect
t 855.652.5683

*CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_


On Thu, Sep 11, 2014 at 10:15 PM, Pierre-Luc Dion 
wrote:

> Hi Daan,
>
> could you create following public Jira filter to start Release-Notes for
> 4.3.1 and 4.4.1.
>
> 4.4.1 fixed
> project = CLOUDSTACK AND type = Bug AND fixVersion = 4.4.1 AND resolution
> != "\"Unresolved\"" ORDER BY created DESC, priority DESC, key ASC
>
> 4.4.1 known
> project = CLOUDSTACK AND type = Bug AND (affectedVersion = 4.4.1 or
> affectedVersion = 4.4.0) AND resolution is EMPTY AND level = "Public" ORDER
> BY priority DESC, key ASC
>
> 4.3.1 fixed
> project = CLOUDSTACK AND type = Bug AND fixVersion = 4.3.1 AND resolution
> != "\"Unresolved\"" ORDER BY created DESC, priority DESC, key ASC
>
> 4.3.1 known
> project = CLOUDSTACK AND type = Bug AND (affectedVersion = 4.3.1 or
> affectedVersion = 4.3.0) AND resolution is EMPTY AND level = "Public" ORDER
> BY priority DESC, key ASC
>
>
> Also , does anyone is working on RN of 4.4.1 or 4.3.1? I can work on
> 4.4.1, maybe on the 4.3.1.
>

Re: [VOTE] Release Apache CloudStack 4.3.1 round #4

[Erik Weber]

Do we have an official upgrade path for those who want to upgrade?

Erik
12. sep. 2014 01:15 skrev "Rohit Yadav" 
følgende:

> HI,
>
> On 11-Sep-2014, at 9:56 pm, Wei ZHOU  wrote:
> > Sorry I just notice Rohit made a systemvm template change (commit
> > 3a0f1550289a8a2a50b0f786821cec2e5c914e62) on 9th, September.
> > The systemvm template will be built based on debian 7.5.0 instead of
> 7.4.0
>
> The quoted commit and changes to use 7.5.0 instead of 7.4.0 was done on
> 4.4 and master branches. On 4.3 branch it was changes from 7.0.0 to 7.5.0.
> This does not change the systemvms internal packages but save some
> bandwidth while building them (and have the latest stable kernel from
> 7.5.0) because we do a apt-get update before installing packages
> (tools/appliances/systemvm**/postinstall.sh). Other than this the only
> major change in systemvms was apache rewrite rules from CLOUDSTACK-7405
> fix. So, while using 4.3.1 systemvms is recommended but not mandatory.
>
> 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 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.
>

Review Request 25573: CLOUDSTACK-7135: test_baremetal.py - Tagging test case as invalid

[Gaurav Aradhye]

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

Review request for cloudstack, sanjeev n, Santhosh Edukulla, and 
SrikanteswaraRao Talluri.


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


Repository: cloudstack-git


Description
---

The test case tries to create a guest network in basic zone, which is not 
possible on daily run setups as the setup would have already a guest network 
present.

As confirmed by Frank Zhang, this test case should be skipped in daily runs as 
there is no valid test case right now present for baremetal. The test case has 
never passed in any of the past build.

Removing "basic" tag from test case and adding "invalid" tag. Removal of basic 
tag ensures the test case is not picked up in runs. Adding of "invalid" tag 
tellls us this test case is invalid.


Diffs
-

  test/integration/component/test_baremetal.py 6ab9146 

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


Testing
---

N/A


Thanks,

Gaurav Aradhye