Test VM life Cycle

[Sebastien Goasguen]

Hi Sailaja,

Looks like you just committed this:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=aa4fea231db714f369f0ec5203a9407c98152984

To fix the test_vm_life_cycle test, that's great but I don't think it works.

With Travis now running the tests for every commit we see that one set of tests 
is still red:
https://travis-ci.org/apache/cloudstack/builds/34359983

And indeed it seems to be this vm life cycle test that is failing.

Ideally, you could fork cloudstack on github, make the commit, travis would run 
the tests on your own fork and once it's "green" you can push to master.

Could you have another look at it ?

thanks,

PS: there might still be issues with the config on travis but from my 
experience yesterday on 4.3, if it fails on travis, it's also failing locally.

-sebastien

Jenkins build is still unstable: simulator-singlerun #284

[jenkins]

See 

simulator run

[Hugo Trippaers]

Heya,

The simulator run reports three errors at the moment:

integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_09_expunge_vm
integration.smoke.test_network.TestReleaseIP.test_releaseIP
integration.smoke.test_network.TestDeleteAccount.test_delete_account

Can somebody with a bit of background on these tests do the investigation? I’m 
happy to help with fixing the issue, but i can’t really figure it out atm.


Cheers,

Hugo

RE: Test VM life Cycle

[Sailaja Mada]

Hi,

I have reverted the commit.  I will recheck locally and commit the fix.

Thanks, 
Sailaja.M

-Original Message-
From: Sebastien Goasguen [mailto:run...@gmail.com] 
Sent: 04 September 2014 12:53
To: dev@cloudstack.apache.org; Sailaja Mada
Subject: Test VM life Cycle

Hi Sailaja,

Looks like you just committed this:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=aa4fea231db714f369f0ec5203a9407c98152984

To fix the test_vm_life_cycle test, that's great but I don't think it works.

With Travis now running the tests for every commit we see that one set of tests 
is still red:
https://travis-ci.org/apache/cloudstack/builds/34359983

And indeed it seems to be this vm life cycle test that is failing.

Ideally, you could fork cloudstack on github, make the commit, travis would run 
the tests on your own fork and once it's "green" you can push to master.

Could you have another look at it ?

thanks,

PS: there might still be issues with the config on travis but from my 
experience yesterday on 4.3, if it fails on travis, it's also failing locally.

-sebastien

Re: Test VM life Cycle

[Sebastien Goasguen]

Thanks for looking into it,

You did not have to revert the commit, I was just pointing out that it did not 
seem to have fixed the issue, and that it would be good to get in the habit of 
testing in our own forks before committing to master.

-sebastien

On Sep 4, 2014, at 3:53 AM, Sailaja Mada  wrote:

> Hi,
> 
> I have reverted the commit.  I will recheck locally and commit the fix.
> 
> Thanks, 
> Sailaja.M
> 
> -Original Message-
> From: Sebastien Goasguen [mailto:run...@gmail.com] 
> Sent: 04 September 2014 12:53
> To: dev@cloudstack.apache.org; Sailaja Mada
> Subject: Test VM life Cycle
> 
> Hi Sailaja,
> 
> Looks like you just committed this:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=aa4fea231db714f369f0ec5203a9407c98152984
> 
> To fix the test_vm_life_cycle test, that's great but I don't think it works.
> 
> With Travis now running the tests for every commit we see that one set of 
> tests is still red:
> https://travis-ci.org/apache/cloudstack/builds/34359983
> 
> And indeed it seems to be this vm life cycle test that is failing.
> 
> Ideally, you could fork cloudstack on github, make the commit, travis would 
> run the tests on your own fork and once it's "green" you can push to master.
> 
> Could you have another look at it ?
> 
> thanks,
> 
> PS: there might still be issues with the config on travis but from my 
> experience yesterday on 4.3, if it fails on travis, it's also failing locally.
> 
> -sebastien

[ACS44] merge hotfix/4.4-7405

[Sebastien Goasguen]

Daan,

I applied a new patch to hotfix/4.4-7405

Can you merge it to 4.4, it fixes metadata rewrite rules issues, bug 7405.
I already committed it to master.

thanks,

-sebastien

Re: Review Request 25170: Summary:pre-add all RewriteRule entries to metadata htaccess file for system vm routers, removes dynamic generation and adds previous fix for bug 7405

[Sebastien Goasguen]

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

Ship it!


applied to master with 355eb72c7d3a3bf29d6d1a2185a5973bc511ed77
and applied to hotfix/4.4-7405 

It did not apply cleanly on 4.3, so I will not apply it there and keep it at 
Erik's patch in vmdata.py

thanks for the patch, you can mark the review as submitted

- Sebastien Goasguen


On Aug. 28, 2014, 10:46 p.m., Fred Clift wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25170/
> ---
> 
> (Updated Aug. 28, 2014, 10:46 p.m.)
> 
> 
> Review request for cloudstack.
> 
> 
> Bugs: 7405
> https://issues.apache.org/jira/browse/7405
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> pre-add all RewriteRule entries to metadata htaccess file  for system vm 
> routers- makes automated router maintanince easier...  The set is static and 
> doesn't ever change after the initial provision - it is identical for every 
> router... 
> 
> Fix htaccess file, vmdata.py that used to modify it, and added comments to 
> producers of meta-data to note the new usage
> 
> Includes updated fix for bug 7405
> 
> We (betterservers.com) have some in-house router-fixing scripts that would 
> like to re-unpack the tarball and not loose the full .htaccess file... 
> 
> 
> Diffs
> -
> 
>   
> core/test/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResourceTest.java
>  aab1e72 
>   
> plugins/hypervisors/baremetal/src/com/cloud/baremetal/networkservice/BaremetalPxeManagerImpl.java
>  e133f7d 
>   server/src/com/cloud/network/element/CloudZonesNetworkElement.java 55cd5fa 
>   server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java 
> 33d7cd7 
>   systemvm/patches/debian/config/opt/cloud/bin/vmdata.py a44c134 
>   systemvm/patches/debian/config/var/www/html/latest/.htaccess 038a4c9 
> 
> Diff: https://reviews.apache.org/r/25170/diff/
> 
> 
> Testing
> ---
> 
> tested before and after getting user-data and metadata, with and without
> trailing slashes.
> 
> provisioned new router.
> 
> 
> Thanks,
> 
> Fred Clift
> 
>

Add OS X 10.9 to the guest os type

[Mohamed Ali Saidi]

Hi,

I'm working on a CI platforme and I want to add OS x 10.9 to Cloudstack
guest os type.

I tried with adding these lines on db:

INSERT INTO `cloud`.`guest_os` (id, uuid, category_id, display_name) VALUES
(226, UUID(), 7, 'Apple Mac OS X 10.9 (32 bit)');
INSERT INTO `cloud`.`guest_os` (id, uuid, category_id, display_name) VALUES
(227, UUID(), 7, 'Apple Mac OS X 10.9 (64 bit)');

INSERT INTO `cloud`.`guest_os_hypervisor` (hypervisor_type, guest_os_name,
guest_os_id) VALUES ("VmWare", 'Apple Mac OS X 10.9 (32 bit)', 226);
INSERT INTO `cloud`.`guest_os_hypervisor` (hypervisor_type, guest_os_name,
guest_os_id) VALUES ("VmWare", 'Apple Mac OS X 10.9 (64 bit)', 227);

And on VmwareGuestOsMapper.java:

s_mapper.put("Apple Mac OS X 10.9 (32
bit)",VirtualMachineGuestOsIdentifier.DARWIN_11_GUEST);
   s_mapper.put("Apple Mac OS X 10.9 (64
bit)",VirtualMachineGuestOsIdentifier.DARWIN_11_64_GUEST);


but it didn't work.

PS:On Vcenter i get  "Other(64 bit)" as vm os guest type.

Thanks

Re: Issue with accessing DNS from VPN IP

[Rohit Yadav]

On 02-Sep-2014, at 12:43 pm, Rohit Yadav  wrote:
> Hi,
>
> When I connect to CloudStack's VPN on a network (L2TP over IPSEC), I’m 
> assigned an IP like 10.1.2.2 and the DNS assigned is 10.1.2.1, but the 
> virtual router is not listening on this IP (VPN) for DNS queries but on guest 
> network so I cannot access resources by using internal dns domain names.
>
> Is this normal behaviour? If it’s not a bug should we fix it? A workaround 
> was to set the necessary DNS IP in the client before connecting (in my case 
> the router’s IP, 10.1.1.1).

ping, any comments?

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.

[GitHub] cloudstack pull request: Fix CLOUDSTACK-7476: always pass along $J...

[lsimons]

GitHub user lsimons opened a pull request:

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

Fix CLOUDSTACK-7476: always pass along $JAVA_HOME

On a secured environment (selinux w/ env_reset enabled in sudoers), the
runuser command that is invoked by the daemon() function does not pass
along environment variables, so $JAVA_HOME is empty, and JSVC falls
back to its default behavior, which may not find java or may not find
the intended java.

This fix simply passes $JAVA_HOME explicitly using the -home argument to
JSVC.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/schubergphilis/cloudstack 
bugfix/CLOUDSTACK-7476

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/15.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #15


commit da9647205aafccee3ae8b60b6ccdee0dcad8c712
Author: Leo Simons 
Date:   2014-09-03T07:32:32Z

Fix CLOUDSTACK-7476: always pass along $JAVA_HOME

On a secured environment (selinux w/ env_reset enabled in sudoers), the
runuser command that is invoked by the daemon() function does not pass
along environment variables, so $JAVA_HOME is empty, and JSVC falls
back to its default behavior, which may not find java or may not find
the intended java.

This fix simply passes $JAVA_HOME explicitly using the -home argument to
JSVC.




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

Re: Review Request 25235: vGPU service offering upgrade test automation

[John Dilley]

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

Ship it!


Ship It!

- John Dilley


On Sept. 3, 2014, 6:12 p.m., sailaja mada wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25235/
> ---
> 
> (Updated Sept. 3, 2014, 6:12 p.m.)
> 
> 
> Review request for cloudstack, Doug Clark, John Dilley, and Sanjay Tripathi.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> vGPU service offering upgrade test automation
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_deploy_vgpu_vm.py eb0bade 
> 
> Diff: https://reviews.apache.org/r/25235/diff/
> 
> 
> Testing
> ---
> 
> Yes. All the testcases are executed with XenServer hypervisor.
> 
> 
> Thanks,
> 
> sailaja mada
> 
>

Jenkins build is still unstable: simulator-singlerun #285

[jenkins]

See 

Re: [ACS44] merge hotfix/4.4-7405

[Daan Hoogland]

merged


On Thu, Sep 4, 2014 at 10:26 AM, Sebastien Goasguen 
wrote:

> Daan,
>
> I applied a new patch to hotfix/4.4-7405
>
> Can you merge it to 4.4, it fixes metadata rewrite rules issues, bug 7405.
> I already committed it to master.
>
> thanks,
>
> -sebastien
>



-- 
Daan

Re: old branches

[Leo Simons]

On Sep 1, 2014, at 4:53 PM, Daan Hoogland  wrote:
> By my possibly slightly incorrect count we now have 158 branches in our
> repo. Those include master and old release branches but also a lot of
> obsolete ones.
> 
> Should we clean? (+1 implied)

+1

> Should an RM be responsible of fix branches? (I feel I am, so don't
> hesitate to say yes on that one)

No opinion...

> Should those responsible for a merge be made responsible for deleting the
> merged branch? (+1 implied)

Depends. I can imagine various scenarios where you want to leave a branch 
around for a while after you’ve merged it in.

Personally I’d suggest just doing a periodic cleanup. You can use

  git branch --merged

to list candidates for cleanup. For example:

  $ git branch -a --merged master | grep remotes/asf | grep -v ‘/master'
  remotes/asf/Commit-Ratio
  remotes/asf/Health-Check-UI
  remotes/asf/LDAP-UI
  remotes/asf/Reset-VM
  remotes/asf/UI-dedicatedResources
  remotes/asf/bugfix/CID-1230585
  remotes/asf/bugfix/CID-1230587
  remotes/asf/cloudstack-globalization
  remotes/asf/cs2163
  remotes/asf/dvswitch-UI
  remotes/asf/javelin
  remotes/asf/ldapplugin
  remotes/asf/namespacechanges
  remotes/asf/object_store
  remotes/asf/rbac
  remotes/asf/rbd-snap-clone
  remotes/asf/reformat
  remotes/asf/regions
  remotes/asf/scale-UP
  remotes/asf/spring-modularization
  remotes/asf/tampa
  remotes/asf/txn-refactor
  remotes/asf/ucs
  remotes/asf/ui-add-remove-nics
  remotes/asf/ui-cisco-asa1000v-support
  remotes/asf/ui-granular-settings
  remotes/asf/ui-plugins
  remotes/asf/ui-primary-storage-target
  remotes/asf/ui-regions
  remotes/asf/ui-vm-affinity
  remotes/asf/vim51_win8

There’s a lot of branches that are not fully in master, though…

  $ all_branches=$(git branch -a | grep remotes/asf | wc -l)
  $ merged_branches=$(git branch -a --merged master | grep remotes/asf | wc -l)
  $ echo not_merged=$((all_branches - merged_branches))
  not_merged=116

Not all of those should go, but I will guess there’s 50+ of them that would 
need cleanup ‘by hand’...I guess a good guess for who should be cleaning those 
up is whoever is the last person that committed on the branch.


cheers,


Leo

SSVM JAVA PROCESS NOT RUNNING, systemvm didn't get patched with the agent specific code

[Punith S]

hi,

i have been working on building noredist of master for vmware,

since i'm using mvn commands and jetty for deploying cloudstack

i'm building the cloudstack using
 $ mvn clean
$ mvn install -Dnoredist

deploying using $ mvn -pl :cloud-client-ui jetty:run -Dnoredist

also i'm seeding the SSVM template by using
as the link suggests
https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack

# mkdir -p /etc/cloudstack/management/
# cp 
./client/target/cloud-client-ui-4.5.0-SNAPSHOT/WEB-INF/classes/db.properties
/etc/cloudstack/management/
#
./client/target/generated-webapp/WEB-INF/classes/scripts/storage/secondary/cloud-install-sys-tmplt
-m /mnt/secondary -u http://
jenkins.buildacloud.org/view/master/job/build-systemvm-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvmtemplate-master-vmware.ova
-h vmware -F

when i deploy a vmware zone,everything come up fine but the systemvm's
agent is not running!

when i log into the ssvm,* i see 4.4.SNAPSHOT jars being patched in the
/use/local/cloud/ssvm*

hence the java process is not running
logs show
2014-09-04 09:20:24,760 INFO  [cloud.agent.AgentShell] (main:null) Agent
started
2014-09-04 09:20:24,764 INFO  [cloud.agent.AgentShell] (main:null)
Implementation Version is 4.4.0-SNAPSHOT
2014-09-04 09:20:24,765 INFO  [cloud.agent.AgentShell] (main:null)
agent.properties found at /usr/local/cloud/systemvm/conf/agent.properties
2014-09-04 09:20:24,772 DEBUG [cloud.agent.AgentShell] (main:null) Found
property: instance
2014-09-04 09:20:24,774 DEBUG [cloud.agent.AgentShell] (main:null) Found
property: resource
2014-09-04 09:20:24,774 INFO  [cloud.agent.AgentShell] (main:null)
Defaulting to using properties file for storage
2014-09-04 09:20:24,781 INFO  [cloud.agent.AgentShell] (main:null)
Defaulting to the constant time backoff algorithm
2014-09-04 09:20:24,801 INFO  [cloud.utils.LogUtils] (main:null) log4j
configuration found at /usr/local/cloud/systemvm/conf/log4j-cloud.xml
2014-09-04 09:20:24,825 DEBUG [cloud.agent.AgentShell] (main:null) Checking
to see if agent.SecStorage.pid exists.
2014-09-04 09:20:24,828 DEBUG [cloud.utils.ProcessUtil] (main:null)
environment.properties could not be opened
2014-09-04 09:20:24,836 DEBUG [cloud.utils.ProcessUtil] (main:null)
Executing: bash -c echo $PPID
2014-09-04 09:20:24,844 DEBUG [cloud.utils.ProcessUtil] (main:null)
Execution is successful.
*2014-09-04 09:20:24,853 ERROR [cloud.agent.AgentShell] (main:null) Unable
to start agent: Resource class not found:
com.cloud.storage.resource.PremiumSecondaryStorageResource due to:
java.lang.ClassNotFoundException:
com.cloud.storage.resource.PremiumSecondaryStorageResource*

i'm guessing there was no patch up between agent specific code !
am i missing out something here ?

thanks!
-- 
regards,

punith s
cloudbyte.com

Jenkins build is back to normal : cloudstack-4.4-maven-build-noredist #369

[jenkins]

See 

Re: Review Request 24794: Review request for CLOUDSTACK-6169 - assignVirtualMachine leaves associated tags assigned to old account

[daan Hoogland]

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


What testing has been done?
Can you ad a unit test for the functions that contain the new code?

- daan Hoogland


On Aug. 18, 2014, 9:54 a.m., Namita Chaudhari wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/24794/
> ---
> 
> (Updated Aug. 18, 2014, 9:54 a.m.)
> 
> 
> Review request for cloudstack and Marcus Sorensen.
> 
> 
> Bugs: CLOUDSTACK-6169 and 
> https://issues.apache.org/jira/browse/CLOUDSTACK-6169
> https://issues.apache.org/jira/browse/CLOUDSTACK-6169
> 
> https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/CLOUDSTACK-6169
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-6169 - assignVirtualMachine leaves associated tags assigned to old 
> account
> 
> When a VM is assigned from one account to another, the tags associated to the 
> VM points to the new account and not old one.
> 
> 
> Diffs
> -
> 
>   engine/schema/src/com/cloud/tags/ResourceTagVO.java ea1 
>   engine/schema/src/com/cloud/tags/dao/ResourceTagDao.java fffe2a47 
>   engine/schema/src/com/cloud/tags/dao/ResourceTagsDaoImpl.java 3611999 
>   server/src/com/cloud/vm/UserVmManagerImpl.java e5de11f 
> 
> Diff: https://reviews.apache.org/r/24794/diff/
> 
> 
> Testing
> ---
> 
> Yes.
> 
> 
> Thanks,
> 
> Namita Chaudhari
> 
>

Jenkins build is still unstable: simulator-singlerun #286

[jenkins]

See 

Re: SSVM JAVA PROCESS NOT RUNNING, systemvm didn't get patched with the agent specific code

[Hugo Trippaers]

Punith,

You need to enable the systemvm flag in cloudstack to make sure a new 
systemvm.iso is build.

mvn -Dnoredist -Psystemvm clean install


Cheers,

Hugo

On 4 sep. 2014, at 11:27, Punith S  wrote:

> hi,
> 
> i have been working on building noredist of master for vmware,
> 
> since i'm using mvn commands and jetty for deploying cloudstack
> 
> i'm building the cloudstack using
> $ mvn clean
> $ mvn install -Dnoredist
> 
> deploying using $ mvn -pl :cloud-client-ui jetty:run -Dnoredist
> 
> also i'm seeding the SSVM template by using
> as the link suggests
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack
> 
> # mkdir -p /etc/cloudstack/management/
> # cp 
> ./client/target/cloud-client-ui-4.5.0-SNAPSHOT/WEB-INF/classes/db.properties
> /etc/cloudstack/management/
> #
> ./client/target/generated-webapp/WEB-INF/classes/scripts/storage/secondary/cloud-install-sys-tmplt
> -m /mnt/secondary -u http://
> jenkins.buildacloud.org/view/master/job/build-systemvm-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvmtemplate-master-vmware.ova
> -h vmware -F
> 
> when i deploy a vmware zone,everything come up fine but the systemvm's
> agent is not running!
> 
> when i log into the ssvm,* i see 4.4.SNAPSHOT jars being patched in the
> /use/local/cloud/ssvm*
> 
> hence the java process is not running
> logs show
> 2014-09-04 09:20:24,760 INFO  [cloud.agent.AgentShell] (main:null) Agent
> started
> 2014-09-04 09:20:24,764 INFO  [cloud.agent.AgentShell] (main:null)
> Implementation Version is 4.4.0-SNAPSHOT
> 2014-09-04 09:20:24,765 INFO  [cloud.agent.AgentShell] (main:null)
> agent.properties found at /usr/local/cloud/systemvm/conf/agent.properties
> 2014-09-04 09:20:24,772 DEBUG [cloud.agent.AgentShell] (main:null) Found
> property: instance
> 2014-09-04 09:20:24,774 DEBUG [cloud.agent.AgentShell] (main:null) Found
> property: resource
> 2014-09-04 09:20:24,774 INFO  [cloud.agent.AgentShell] (main:null)
> Defaulting to using properties file for storage
> 2014-09-04 09:20:24,781 INFO  [cloud.agent.AgentShell] (main:null)
> Defaulting to the constant time backoff algorithm
> 2014-09-04 09:20:24,801 INFO  [cloud.utils.LogUtils] (main:null) log4j
> configuration found at /usr/local/cloud/systemvm/conf/log4j-cloud.xml
> 2014-09-04 09:20:24,825 DEBUG [cloud.agent.AgentShell] (main:null) Checking
> to see if agent.SecStorage.pid exists.
> 2014-09-04 09:20:24,828 DEBUG [cloud.utils.ProcessUtil] (main:null)
> environment.properties could not be opened
> 2014-09-04 09:20:24,836 DEBUG [cloud.utils.ProcessUtil] (main:null)
> Executing: bash -c echo $PPID
> 2014-09-04 09:20:24,844 DEBUG [cloud.utils.ProcessUtil] (main:null)
> Execution is successful.
> *2014-09-04 09:20:24,853 ERROR [cloud.agent.AgentShell] (main:null) Unable
> to start agent: Resource class not found:
> com.cloud.storage.resource.PremiumSecondaryStorageResource due to:
> java.lang.ClassNotFoundException:
> com.cloud.storage.resource.PremiumSecondaryStorageResource*
> 
> i'm guessing there was no patch up between agent specific code !
> am i missing out something here ?
> 
> thanks!
> -- 
> regards,
> 
> punith s
> cloudbyte.com

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

[jenkins]

See 

Changes:

[sailaja.mada] vGPU Service offering test automation after including review 
comments

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

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


---
 T E S T S
---

Results :

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

[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ 
cloud-plugin-api-solidfire-intg-test ---
[INFO] Building jar: 

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

 to 
/jenkins/.m2/repository/org/apache/cloudstack/cloud-plugin-api-solidfire-intg-test/4.5.0-SNAPSHOT/cloud-plugin-api-solidfire-intg-test-4.5.0-SNAPSHOT.jar
[INFO] Installing 

 to 
/jenkins/.m2/repository/org/apache/cloudstack/cloud-plugin-api-solidfire-intg-test/4.5.0-SNAPSHOT/cloud-plugin-api-solidfire-intg-test-4.5.0-SNAPSHOT.pom
[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Plugin - API Discovery 4.5.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
cloud-plugin-api-discovery ---
[INFO] Deleting 

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

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

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

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
cloud-plugin-api-discovery ---
[INFO] Compiling 6 source files to 

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

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
cloud-plugin-api-discovery ---
[INFO] Compiling 1 source file to 

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


---
 T E S T S
---
Running org.apache.cloudstack.discovery.ApiDiscoveryTest
log4j:WARN No appenders could be found for logger 
(org.apache.cloudstack.discovery.ApiDiscoveryServiceImpl).
log4j:WARN Please initialize the log4j system properly

Re: SSVM JAVA PROCESS NOT RUNNING, systemvm didn't get patched with the agent specific code

[Punith S]

thanks Hugo, it's working now :)

cheers!


On Thu, Sep 4, 2014 at 3:32 PM, Hugo Trippaers  wrote:

> Punith,
>
> You need to enable the systemvm flag in cloudstack to make sure a new
> systemvm.iso is build.
>
> mvn -Dnoredist -Psystemvm clean install
>
>
> Cheers,
>
> Hugo
>
> On 4 sep. 2014, at 11:27, Punith S  wrote:
>
> > hi,
> >
> > i have been working on building noredist of master for vmware,
> >
> > since i'm using mvn commands and jetty for deploying cloudstack
> >
> > i'm building the cloudstack using
> > $ mvn clean
> > $ mvn install -Dnoredist
> >
> > deploying using $ mvn -pl :cloud-client-ui jetty:run -Dnoredist
> >
> > also i'm seeding the SSVM template by using
> > as the link suggests
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack
> >
> > # mkdir -p /etc/cloudstack/management/
> > # cp
> ./client/target/cloud-client-ui-4.5.0-SNAPSHOT/WEB-INF/classes/db.properties
> > /etc/cloudstack/management/
> > #
> >
> ./client/target/generated-webapp/WEB-INF/classes/scripts/storage/secondary/cloud-install-sys-tmplt
> > -m /mnt/secondary -u http://
> >
> jenkins.buildacloud.org/view/master/job/build-systemvm-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvmtemplate-master-vmware.ova
> > -h vmware -F
> >
> > when i deploy a vmware zone,everything come up fine but the systemvm's
> > agent is not running!
> >
> > when i log into the ssvm,* i see 4.4.SNAPSHOT jars being patched in the
> > /use/local/cloud/ssvm*
> >
> > hence the java process is not running
> > logs show
> > 2014-09-04 09:20:24,760 INFO  [cloud.agent.AgentShell] (main:null) Agent
> > started
> > 2014-09-04 09:20:24,764 INFO  [cloud.agent.AgentShell] (main:null)
> > Implementation Version is 4.4.0-SNAPSHOT
> > 2014-09-04 09:20:24,765 INFO  [cloud.agent.AgentShell] (main:null)
> > agent.properties found at /usr/local/cloud/systemvm/conf/agent.properties
> > 2014-09-04 09:20:24,772 DEBUG [cloud.agent.AgentShell] (main:null) Found
> > property: instance
> > 2014-09-04 09:20:24,774 DEBUG [cloud.agent.AgentShell] (main:null) Found
> > property: resource
> > 2014-09-04 09:20:24,774 INFO  [cloud.agent.AgentShell] (main:null)
> > Defaulting to using properties file for storage
> > 2014-09-04 09:20:24,781 INFO  [cloud.agent.AgentShell] (main:null)
> > Defaulting to the constant time backoff algorithm
> > 2014-09-04 09:20:24,801 INFO  [cloud.utils.LogUtils] (main:null) log4j
> > configuration found at /usr/local/cloud/systemvm/conf/log4j-cloud.xml
> > 2014-09-04 09:20:24,825 DEBUG [cloud.agent.AgentShell] (main:null)
> Checking
> > to see if agent.SecStorage.pid exists.
> > 2014-09-04 09:20:24,828 DEBUG [cloud.utils.ProcessUtil] (main:null)
> > environment.properties could not be opened
> > 2014-09-04 09:20:24,836 DEBUG [cloud.utils.ProcessUtil] (main:null)
> > Executing: bash -c echo $PPID
> > 2014-09-04 09:20:24,844 DEBUG [cloud.utils.ProcessUtil] (main:null)
> > Execution is successful.
> > *2014-09-04 09:20:24,853 ERROR [cloud.agent.AgentShell] (main:null)
> Unable
> > to start agent: Resource class not found:
> > com.cloud.storage.resource.PremiumSecondaryStorageResource due to:
> > java.lang.ClassNotFoundException:
> > com.cloud.storage.resource.PremiumSecondaryStorageResource*
> >
> > i'm guessing there was no patch up between agent specific code !
> > am i missing out something here ?
> >
> > thanks!
> > --
> > regards,
> >
> > punith s
> > cloudbyte.com
>
>


-- 
regards,

punith s
cloudbyte.com

Jenkins build is unstable: simulator-hotfix-trigger #30

[jenkins]

See 

RE: simulator run

[Koushik Das]

Are the tests present under test/integration/smoke/misc also getting executed? 
If so please exclude them for now.
The tests under /misc folder is based on the new simulator changes to test 
failures from agent layer. These tests can cause interference in other tests.

There are 2 options to make them work together:
- Run tests under /misc folder separately and in sequence
- All existing smoke tests needs to be modified to run against some targeted 
host(s). So that there is no interference from agent layer simulated failures 
(these tests can target some specific hosts that are not used by any other 
tests).

-Original Message-
From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
Sent: Thursday, 4 September 2014 1:09 PM
To: 
Subject: simulator run

Heya,

The simulator run reports three errors at the moment:

integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_09_expunge_vm
integration.smoke.test_network.TestReleaseIP.test_releaseIP
integration.smoke.test_network.TestDeleteAccount.test_delete_account

Can somebody with a bit of background on these tests do the investigation? I'm 
happy to help with fixing the issue, but i can't really figure it out atm.


Cheers,

Hugo

Re: simulator run

[Hugo Trippaers]

Hey,

This is what i’m executing to run the tests:

/usr/local/bin/nosetests-2.7 -v --with-marvin 
--marvin-config=setup/dev/advanced.cfg --with-xunit --xunit-file=xunit.xml -a 
tags=advanced,required_hardware=false --zone=Sandbox-simulator 
--hypervisor=simulator -w test/integration/smoke



Cheers,

Hugo

On 4 sep. 2014, at 13:32, Koushik Das  wrote:

> Are the tests present under test/integration/smoke/misc also getting 
> executed? If so please exclude them for now.
> The tests under /misc folder is based on the new simulator changes to test 
> failures from agent layer. These tests can cause interference in other tests.
> 
> There are 2 options to make them work together:
> - Run tests under /misc folder separately and in sequence
> - All existing smoke tests needs to be modified to run against some targeted 
> host(s). So that there is no interference from agent layer simulated failures 
> (these tests can target some specific hosts that are not used by any other 
> tests).
> 
> -Original Message-
> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> Sent: Thursday, 4 September 2014 1:09 PM
> To: 
> Subject: simulator run
> 
> Heya,
> 
> The simulator run reports three errors at the moment:
> 
> integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_09_expunge_vm
> integration.smoke.test_network.TestReleaseIP.test_releaseIP
> integration.smoke.test_network.TestDeleteAccount.test_delete_account
> 
> Can somebody with a bit of background on these tests do the investigation? 
> I'm happy to help with fixing the issue, but i can't really figure it out atm.
> 
> 
> Cheers,
> 
> Hugo
> 
> 
> 
> 

RE: simulator run

[Koushik Das]

Ok, in that case the tests under /misc won't get executed. Looks like there are 
some other issues with the failing tests

> grep required_hardware= test/integration/smoke/misc/*.py
test/integration/smoke/misc/test_deploy_vm.py:@attr(tags = ['advanced'], 
required_hardware="simulator only")
test/integration/smoke/misc/test_deploy_vm.py:@attr(tags = ['advanced'], 
required_hardware="simulator only")
test/integration/smoke/misc/test_vm_ha.py:@attr(tags = ['advanced'], 
required_hardware="simulator only")
test/integration/smoke/misc/test_vm_sync.py:@attr(tags = ['advanced'], 
required_hardware="simulator only")

-Original Message-
From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
Sent: Thursday, 4 September 2014 5:23 PM
To: dev@cloudstack.apache.org
Subject: Re: simulator run

Hey,

This is what i'm executing to run the tests:

/usr/local/bin/nosetests-2.7 -v --with-marvin 
--marvin-config=setup/dev/advanced.cfg --with-xunit --xunit-file=xunit.xml -a 
tags=advanced,required_hardware=false --zone=Sandbox-simulator 
--hypervisor=simulator -w test/integration/smoke



Cheers,

Hugo

On 4 sep. 2014, at 13:32, Koushik Das  wrote:

> Are the tests present under test/integration/smoke/misc also getting 
> executed? If so please exclude them for now.
> The tests under /misc folder is based on the new simulator changes to test 
> failures from agent layer. These tests can cause interference in other tests.
> 
> There are 2 options to make them work together:
> - Run tests under /misc folder separately and in sequence
> - All existing smoke tests needs to be modified to run against some targeted 
> host(s). So that there is no interference from agent layer simulated failures 
> (these tests can target some specific hosts that are not used by any other 
> tests).
> 
> -Original Message-
> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> Sent: Thursday, 4 September 2014 1:09 PM
> To: 
> Subject: simulator run
> 
> Heya,
> 
> The simulator run reports three errors at the moment:
> 
> integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_09_expunge_v
> m integration.smoke.test_network.TestReleaseIP.test_releaseIP
> integration.smoke.test_network.TestDeleteAccount.test_delete_account
> 
> Can somebody with a bit of background on these tests do the investigation? 
> I'm happy to help with fixing the issue, but i can't really figure it out atm.
> 
> 
> Cheers,
> 
> Hugo
> 
> 
> 
> 

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

[jenkins]

See 

Jenkins build is still unstable: simulator-singlerun #287

[jenkins]

See 

Re: Review Request 25301: CLOUDSTACK-7442: Fixed template permission issue in test_project_resources.py

[Gaurav Aradhye]

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


Gentle Reminder

- Gaurav Aradhye


On Sept. 3, 2014, 9:36 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25301/
> ---
> 
> (Updated Sept. 3, 2014, 9:36 p.m.)
> 
> 
> Review request for cloudstack, sanjeev n, Santhosh Edukulla, and 
> SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-7442
> https://issues.apache.org/jira/browse/CLOUDSTACK-7442
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> The template was registered with admin api client, hence it failed to find 
> the project in the domain while updating the permissions.
> 
> The permissions can only be updated if the resource is present in the same 
> domain as that of the owner account of the template.
> 
> Registered the template with the api client of the account in which the 
> project is added, so that the permissions for template can  successfully be 
> updated for the project.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_project_resources.py e769860 
> 
> Diff: https://reviews.apache.org/r/25301/diff/
> 
> 
> Testing
> ---
> 
> Yes.
> 
> Log:
> Test use of private template in a project ... === TestName: 
> test_05_use_private_template_in_project | Status : SUCCESS ===
> ok
> 
> --
> Ran 1 test in 674.081s
> 
> OK
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: simulator run

[Ian Duffy]

Koushik,

Any chance of getting a list of tests that are valid for execution against
the simulator for 4.3, 4.4 and master?

Thanks,
Ian


On 4 September 2014 13:03, Koushik Das  wrote:

> Ok, in that case the tests under /misc won't get executed. Looks like
> there are some other issues with the failing tests
>
> > grep required_hardware= test/integration/smoke/misc/*.py
> test/integration/smoke/misc/test_deploy_vm.py:@attr(tags =
> ['advanced'], required_hardware="simulator only")
> test/integration/smoke/misc/test_deploy_vm.py:@attr(tags =
> ['advanced'], required_hardware="simulator only")
> test/integration/smoke/misc/test_vm_ha.py:@attr(tags = ['advanced'],
> required_hardware="simulator only")
> test/integration/smoke/misc/test_vm_sync.py:@attr(tags = ['advanced'],
> required_hardware="simulator only")
>
> -Original Message-
> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> Sent: Thursday, 4 September 2014 5:23 PM
> To: dev@cloudstack.apache.org
> Subject: Re: simulator run
>
> Hey,
>
> This is what i'm executing to run the tests:
>
> /usr/local/bin/nosetests-2.7 -v --with-marvin
> --marvin-config=setup/dev/advanced.cfg --with-xunit --xunit-file=xunit.xml
> -a tags=advanced,required_hardware=false --zone=Sandbox-simulator
> --hypervisor=simulator -w test/integration/smoke
>
>
>
> Cheers,
>
> Hugo
>
> On 4 sep. 2014, at 13:32, Koushik Das  wrote:
>
> > Are the tests present under test/integration/smoke/misc also getting
> executed? If so please exclude them for now.
> > The tests under /misc folder is based on the new simulator changes to
> test failures from agent layer. These tests can cause interference in other
> tests.
> >
> > There are 2 options to make them work together:
> > - Run tests under /misc folder separately and in sequence
> > - All existing smoke tests needs to be modified to run against some
> targeted host(s). So that there is no interference from agent layer
> simulated failures (these tests can target some specific hosts that are not
> used by any other tests).
> >
> > -Original Message-
> > From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> > Sent: Thursday, 4 September 2014 1:09 PM
> > To: 
> > Subject: simulator run
> >
> > Heya,
> >
> > The simulator run reports three errors at the moment:
> >
> > integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_09_expunge_v
> > m integration.smoke.test_network.TestReleaseIP.test_releaseIP
> > integration.smoke.test_network.TestDeleteAccount.test_delete_account
> >
> > Can somebody with a bit of background on these tests do the
> investigation? I'm happy to help with fixing the issue, but i can't really
> figure it out atm.
> >
> >
> > Cheers,
> >
> > Hugo
> >
> >
> >
> >
>
>

Re: Review Request 25301: CLOUDSTACK-7442: Fixed template permission issue in test_project_resources.py

[SrikanteswaraRao Talluri]

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

Ship it!


Ship It!

- SrikanteswaraRao Talluri


On Sept. 3, 2014, 4:06 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25301/
> ---
> 
> (Updated Sept. 3, 2014, 4:06 p.m.)
> 
> 
> Review request for cloudstack, sanjeev n, Santhosh Edukulla, and 
> SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-7442
> https://issues.apache.org/jira/browse/CLOUDSTACK-7442
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> The template was registered with admin api client, hence it failed to find 
> the project in the domain while updating the permissions.
> 
> The permissions can only be updated if the resource is present in the same 
> domain as that of the owner account of the template.
> 
> Registered the template with the api client of the account in which the 
> project is added, so that the permissions for template can  successfully be 
> updated for the project.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_project_resources.py e769860 
> 
> Diff: https://reviews.apache.org/r/25301/diff/
> 
> 
> Testing
> ---
> 
> Yes.
> 
> Log:
> Test use of private template in a project ... === TestName: 
> test_05_use_private_template_in_project | Status : SUCCESS ===
> ok
> 
> --
> Ran 1 test in 674.081s
> 
> OK
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Review Request 25301: CLOUDSTACK-7442: Fixed template permission issue in test_project_resources.py

[SrikanteswaraRao Talluri]

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


pushed to master : abfb469f910b2e16b0d439c57f5878dd5ae46526

- SrikanteswaraRao Talluri


On Sept. 3, 2014, 4:06 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25301/
> ---
> 
> (Updated Sept. 3, 2014, 4:06 p.m.)
> 
> 
> Review request for cloudstack, sanjeev n, Santhosh Edukulla, and 
> SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-7442
> https://issues.apache.org/jira/browse/CLOUDSTACK-7442
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> The template was registered with admin api client, hence it failed to find 
> the project in the domain while updating the permissions.
> 
> The permissions can only be updated if the resource is present in the same 
> domain as that of the owner account of the template.
> 
> Registered the template with the api client of the account in which the 
> project is added, so that the permissions for template can  successfully be 
> updated for the project.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_project_resources.py e769860 
> 
> Diff: https://reviews.apache.org/r/25301/diff/
> 
> 
> Testing
> ---
> 
> Yes.
> 
> Log:
> Test use of private template in a project ... === TestName: 
> test_05_use_private_template_in_project | Status : SUCCESS ===
> ok
> 
> --
> Ran 1 test in 674.081s
> 
> OK
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

RE: simulator run

[Koushik Das]

For master/4.4 the command/filter specified by Hugo should work. For 4.3 check 
for tests tagged with "simulator".

-Original Message-
From: Ian Duffy [mailto:i...@ianduffy.ie] 
Sent: Thursday, 4 September 2014 5:50 PM
To: CloudStack Dev
Subject: Re: simulator run

Koushik,

Any chance of getting a list of tests that are valid for execution against the 
simulator for 4.3, 4.4 and master?

Thanks,
Ian


On 4 September 2014 13:03, Koushik Das  wrote:

> Ok, in that case the tests under /misc won't get executed. Looks like 
> there are some other issues with the failing tests
>
> > grep required_hardware= test/integration/smoke/misc/*.py
> test/integration/smoke/misc/test_deploy_vm.py:@attr(tags =
> ['advanced'], required_hardware="simulator only")
> test/integration/smoke/misc/test_deploy_vm.py:@attr(tags =
> ['advanced'], required_hardware="simulator only")
> test/integration/smoke/misc/test_vm_ha.py:@attr(tags = ['advanced'],
> required_hardware="simulator only")
> test/integration/smoke/misc/test_vm_sync.py:@attr(tags = ['advanced'],
> required_hardware="simulator only")
>
> -Original Message-
> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> Sent: Thursday, 4 September 2014 5:23 PM
> To: dev@cloudstack.apache.org
> Subject: Re: simulator run
>
> Hey,
>
> This is what i'm executing to run the tests:
>
> /usr/local/bin/nosetests-2.7 -v --with-marvin 
> --marvin-config=setup/dev/advanced.cfg --with-xunit 
> --xunit-file=xunit.xml -a tags=advanced,required_hardware=false 
> --zone=Sandbox-simulator --hypervisor=simulator -w 
> test/integration/smoke
>
>
>
> Cheers,
>
> Hugo
>
> On 4 sep. 2014, at 13:32, Koushik Das  wrote:
>
> > Are the tests present under test/integration/smoke/misc also getting
> executed? If so please exclude them for now.
> > The tests under /misc folder is based on the new simulator changes 
> > to
> test failures from agent layer. These tests can cause interference in 
> other tests.
> >
> > There are 2 options to make them work together:
> > - Run tests under /misc folder separately and in sequence
> > - All existing smoke tests needs to be modified to run against some
> targeted host(s). So that there is no interference from agent layer 
> simulated failures (these tests can target some specific hosts that 
> are not used by any other tests).
> >
> > -Original Message-
> > From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> > Sent: Thursday, 4 September 2014 1:09 PM
> > To: 
> > Subject: simulator run
> >
> > Heya,
> >
> > The simulator run reports three errors at the moment:
> >
> > integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_09_expunge
> > _v m integration.smoke.test_network.TestReleaseIP.test_releaseIP
> > integration.smoke.test_network.TestDeleteAccount.test_delete_account
> >
> > Can somebody with a bit of background on these tests do the
> investigation? I'm happy to help with fixing the issue, but i can't 
> really figure it out atm.
> >
> >
> > Cheers,
> >
> > Hugo
> >
> >
> >
> >
>
>

Re: simulator run

[Sebastien Goasguen]

On Sep 4, 2014, at 8:42 AM, Koushik Das  wrote:

> For master/4.4 the command/filter specified by Hugo should work. For 4.3 
> check for tests tagged with "simulator".
> 

so in 4.3, even if I deploy an advanced zone, I should run the tests that have 
tags=simulator , and not tags=advanced ?

> -Original Message-
> From: Ian Duffy [mailto:i...@ianduffy.ie] 
> Sent: Thursday, 4 September 2014 5:50 PM
> To: CloudStack Dev
> Subject: Re: simulator run
> 
> Koushik,
> 
> Any chance of getting a list of tests that are valid for execution against 
> the simulator for 4.3, 4.4 and master?
> 
> Thanks,
> Ian
> 
> 
> On 4 September 2014 13:03, Koushik Das  wrote:
> 
>> Ok, in that case the tests under /misc won't get executed. Looks like 
>> there are some other issues with the failing tests
>> 
>>> grep required_hardware= test/integration/smoke/misc/*.py
>> test/integration/smoke/misc/test_deploy_vm.py:@attr(tags =
>> ['advanced'], required_hardware="simulator only")
>> test/integration/smoke/misc/test_deploy_vm.py:@attr(tags =
>> ['advanced'], required_hardware="simulator only")
>> test/integration/smoke/misc/test_vm_ha.py:@attr(tags = ['advanced'],
>> required_hardware="simulator only")
>> test/integration/smoke/misc/test_vm_sync.py:@attr(tags = ['advanced'],
>> required_hardware="simulator only")
>> 
>> -Original Message-
>> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
>> Sent: Thursday, 4 September 2014 5:23 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: simulator run
>> 
>> Hey,
>> 
>> This is what i'm executing to run the tests:
>> 
>> /usr/local/bin/nosetests-2.7 -v --with-marvin 
>> --marvin-config=setup/dev/advanced.cfg --with-xunit 
>> --xunit-file=xunit.xml -a tags=advanced,required_hardware=false 
>> --zone=Sandbox-simulator --hypervisor=simulator -w 
>> test/integration/smoke
>> 
>> 
>> 
>> Cheers,
>> 
>> Hugo
>> 
>> On 4 sep. 2014, at 13:32, Koushik Das  wrote:
>> 
>>> Are the tests present under test/integration/smoke/misc also getting
>> executed? If so please exclude them for now.
>>> The tests under /misc folder is based on the new simulator changes 
>>> to
>> test failures from agent layer. These tests can cause interference in 
>> other tests.
>>> 
>>> There are 2 options to make them work together:
>>> - Run tests under /misc folder separately and in sequence
>>> - All existing smoke tests needs to be modified to run against some
>> targeted host(s). So that there is no interference from agent layer 
>> simulated failures (these tests can target some specific hosts that 
>> are not used by any other tests).
>>> 
>>> -Original Message-
>>> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
>>> Sent: Thursday, 4 September 2014 1:09 PM
>>> To: 
>>> Subject: simulator run
>>> 
>>> Heya,
>>> 
>>> The simulator run reports three errors at the moment:
>>> 
>>> integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_09_expunge
>>> _v m integration.smoke.test_network.TestReleaseIP.test_releaseIP
>>> integration.smoke.test_network.TestDeleteAccount.test_delete_account
>>> 
>>> Can somebody with a bit of background on these tests do the
>> investigation? I'm happy to help with fixing the issue, but i can't 
>> really figure it out atm.
>>> 
>>> 
>>> Cheers,
>>> 
>>> Hugo
>>> 
>>> 
>>> 
>>> 
>> 
>> 

Re: simulator run

[Ian Duffy]

Koushik,

Just to confirm the following should be OK for simulator usage then.

$ grep -R "tags" ~/projects/cloudstack/test/integration/component | grep
"simulator" | grep -o -e "test_.*.py" | sort -u
test_accounts.py
test_affinity_groups.py
test_allocation_states.py
test_cpu_domain_limits.py
test_cpu_limits.py
test_cpu_max_limits.py
test_cpu_project_limits.py
test_custom_hostname.py
test_deploy_vm_userdata_reg.py
test_host_high_availability.py
test_memory_limits.py
test_mm_domain_limits.py
test_mm_max_limits.py
test_mm_project_limits.py
test_non_contiguous_vlan.py
test_project_configs.py
test_project_limits.py
test_project_resources.py
test_project_usage.py
test_projects.py
test_regions.py
test_regions_accounts.py
test_reset_ssh_keypair.py
test_resource_limits.py
test_stopped_vm.py
test_tags.py
test_update_vm.py
test_usage.py
test_volumes.py

RE: simulator run

[Santhosh Edukulla]

1. If we want to collect all tests applicable for simulator, use nose test 
command below (just add these switches to existing nosecmd --collect-only 
--with-xunit --xunit-file=/tmp/x.xml )
It will dump all the tests under directory mentioned with -w switch and 
required_hardware=false(signifying simulator tests) to /tmp/x.xml file
EX:
 /usr/local/bin/nosetests-2.7 -v --with-marvin  
--marvin-config=setup/dev/advanced.cfg --with-xunit --xunit-file=xunit.xml
-a tags=advanced,required_hardware=false --zone=Sandbox-simulator
--hypervisor=simulator -w test/integration/smoke  --collect-only --with-xunit 
--xunit-file=/tmp/x.xml 

2. Under smoke, we have misc directory they also get run as part of the above 
cmd, to exclude misc folder use --exclude-dir = to 
exclude that directory from running. This option is available with noseexclude 
plugin, check pip install noseexclude(something like that to install exclude 
plugin for nose)

3. Misc dir contains few tests, which are like interferring with other running 
tests, though they are written for simulator say to mock few behaviors, but to 
be run in sequentially not along with existing tests, if so you can exclude 
them, but if they are indeed failing even when run sequentially and are having 
required_hardware=false(simulator tests), then there indeed is a simulator mock 
approach problem or tests having issues.



Santhosh

From: Ian Duffy [i...@ianduffy.ie]
Sent: Thursday, September 04, 2014 8:19 AM
To: CloudStack Dev
Subject: Re: simulator run

Koushik,

Any chance of getting a list of tests that are valid for execution against
the simulator for 4.3, 4.4 and master?

Thanks,
Ian


On 4 September 2014 13:03, Koushik Das  wrote:

> Ok, in that case the tests under /misc won't get executed. Looks like
> there are some other issues with the failing tests
>
> > grep required_hardware= test/integration/smoke/misc/*.py
> test/integration/smoke/misc/test_deploy_vm.py:@attr(tags =
> ['advanced'], required_hardware="simulator only")
> test/integration/smoke/misc/test_deploy_vm.py:@attr(tags =
> ['advanced'], required_hardware="simulator only")
> test/integration/smoke/misc/test_vm_ha.py:@attr(tags = ['advanced'],
> required_hardware="simulator only")
> test/integration/smoke/misc/test_vm_sync.py:@attr(tags = ['advanced'],
> required_hardware="simulator only")
>
> -Original Message-
> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> Sent: Thursday, 4 September 2014 5:23 PM
> To: dev@cloudstack.apache.org
> Subject: Re: simulator run
>
> Hey,
>
> This is what i'm executing to run the tests:
>
> /usr/local/bin/nosetests-2.7 -v --with-marvin
> --marvin-config=setup/dev/advanced.cfg --with-xunit --xunit-file=xunit.xml
> -a tags=advanced,required_hardware=false --zone=Sandbox-simulator
> --hypervisor=simulator -w test/integration/smoke
>
>
>
> Cheers,
>
> Hugo
>
> On 4 sep. 2014, at 13:32, Koushik Das  wrote:
>
> > Are the tests present under test/integration/smoke/misc also getting
> executed? If so please exclude them for now.
> > The tests under /misc folder is based on the new simulator changes to
> test failures from agent layer. These tests can cause interference in other
> tests.
> >
> > There are 2 options to make them work together:
> > - Run tests under /misc folder separately and in sequence
> > - All existing smoke tests needs to be modified to run against some
> targeted host(s). So that there is no interference from agent layer
> simulated failures (these tests can target some specific hosts that are not
> used by any other tests).
> >
> > -Original Message-
> > From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> > Sent: Thursday, 4 September 2014 1:09 PM
> > To: 
> > Subject: simulator run
> >
> > Heya,
> >
> > The simulator run reports three errors at the moment:
> >
> > integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_09_expunge_v
> > m integration.smoke.test_network.TestReleaseIP.test_releaseIP
> > integration.smoke.test_network.TestDeleteAccount.test_delete_account
> >
> > Can somebody with a bit of background on these tests do the
> investigation? I'm happy to help with fixing the issue, but i can't really
> figure it out atm.
> >
> >
> > Cheers,
> >
> > Hugo
> >
> >
> >
> >
>
>

Jenkins build is still unstable: simulator-singlerun #288

[jenkins]

See 

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

[lsimons]

GitHub user lsimons opened a pull request:

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

CLOUDSTACK-7143: Refactoring of the systemvm build process

E-mail thread:
  
http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201407.mbox/%3C7A6CF878-7A28-4D4A-BCD2-0C264F8C90B7%40schubergphilis.com%3E

This started out as wanting the systemvm build to take
systemvm/patches/debian/{debian,vpn} from the local machine/branch,
rather than downloading from the apache git master [1]. In working out
how on earth to get veewee to do that cleanly (hint: you can’t, hence
resorting to shar usage) I got quite frustrated with the image rebuild
times.

It so happens that veewee has a --skip-to-postinstall instruction which
is _quite_ useful while debugging these scripts. To get that working
requires the post install steps to be retryable/convergent. Of course,
our existing scripts weren’t set up for that. So I had to add a bunch
of tests whether changes had applied already. Which implied a pretty
significant refactor.

Summarizing this kind of thing is always hard...it’s many little
things...the interesting stuff is at the end/bottom, in particular
the two main improvements

  
https://github.com/schubergphilis/cloudstack/commit/142d087f6a97f6ac70a858a35d2fe8b638c58cbb
When working on the systemvm in isolation, or using vagrant or
similar tools, it can be useful to inject a custom SSH key before
merging a management server systemvm.iso into it. This option
allows that. It should _not_ have effect on management-server-
managed vms which always get their SSH keys injected.

  
https://github.com/schubergphilis/cloudstack/commit/e2240eaed18000d4d94dbf6a6e40612db1aeda34
The current build downloads its script from master by fetching a
cloudstack tarball. Besides being an unneeded load on the apache
git server, this is a problem when working on a branch and
wanting to inject a different set of scripts. It also makes it
pretty likely that the injected copy of the script will not match
what a production release wants, so there is very little chance of
not needing to overwrite the scripts.

Ideally we would just rsync over some files. However, veewee does
not provide an option to do that. In order to keep a 'cleanly
veewee-only' build possible, and work with any recent veewee
version, in this change we restor to using shar
(http://en.wikipedia.org/wiki/Shar) to produce an archive which
can execute as a script, which we feed to veewee to execute.

In order to avoid having to re-do this cleanup twice, I also ended up
merging the systemvm and systemvm64 template definitions, factoring out
their small differences by inspecting the os architecture.

  
https://github.com/schubergphilis/cloudstack/commit/f570b3921cd52672f841fc5f99cdd96f9737d629
  
https://github.com/schubergphilis/cloudstack/commit/50e91217f90fc952182dccac02a5af06ac33fb45

Everything else…well it pretty much falls into two categories:
  * general code cleanup without functional changes
  * general code defensiveness to survive various jenkins build
scenarios

All in all it should help with ongoing maintenance, I think.

Most of these commits are now a while old but I wanted to wait with
sending this upstream until we had sufficiently tested the systemvms
built with this changed approach locally.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/schubergphilis/cloudstack 
feature/systemvm-refactor-for-upstream

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/16.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #16


commit 49cbb4e20b70a19286c626ac8d9111be8752bc3f
Author: Leo Simons 
Date:   2014-07-21T07:54:13Z

CLOUDSTACK-7143: upgrade systemvm to latest debian stable, 7.6.0.

commit 35b1875226201d5923dea57db64bbd789d9ad908
Author: Leo Simons 
Date:   2014-07-21T07:55:37Z

CLOUDSTACK-7143: split base.sh into its two functions.

commit fb258b506964ca339ef85aa92a6217dc12259811
Author: Leo Simons 
Date:   2014-07-21T07:57:49Z

CLOUDSTACK-7143: move network tuning from cleanup.sh to its own script.

commit 50e2c0177b0df04aa80d19264d52c8d55dc02eb3
Author: Leo Simons 
Date:   2014-07-21T08:36:11Z

CLOUDSTACK-7143: merge systemvm templates, step 1: remove differences

commit 03dba3d901997619d9095e33afe4b39a423ac3f6
Author: Leo Simons 
Date:   2014-07-21T08:44:38Z

CLOUDSTACK-7143: merge systemvm templates, step 2: only one template remains

commit afe696edc32dfcaf7eadcb8272f5e1fe31dc32a8
Author: Leo Si

Jenkins build is still unstable: simulator-singlerun #289

[jenkins]

See 

test case tagging and travis output

[Daan Hoogland]

H Ian,

As discussed off-list I am looking at the failure of extractIso in the
travis-ci run of the 4.4 branch. Can I tune it to give more output? Unlike
the expungeVM test, this one is not run in the simulator-singlerun so
looking at the output there doesn't help.

It seems that CLOUDSTACK-6914 introduced some new tagging scheme for test
and I am assuming the new tagging should exclude the test from the travis
run (makes sense and trying now). The new tagging scheme is not documented
in the bug in spite of Alex Brett asking for it, so once again:
@anyone: is this described somewhere?

-- 
Daan

Re: test case tagging and travis output

[Sebastien Goasguen]

On Sep 4, 2014, at 10:14 AM, Daan Hoogland  wrote:

> H Ian,
> 
> As discussed off-list I am looking at the failure of extractIso in the

fwiw, I removed that test from 4.3 testing.

all test seem to pass for 4.3 but Travis still outputs "red" because of some 
strange return values by Marvin

but with the marvin refactoring, there are differences between master, 4.4 and 
4.3.


> travis-ci run of the 4.4 branch. Can I tune it to give more output? Unlike
> the expungeVM test, this one is not run in the simulator-singlerun so
> looking at the output there doesn't help.
> 
> It seems that CLOUDSTACK-6914 introduced some new tagging scheme for test
> and I am assuming the new tagging should exclude the test from the travis
> run (makes sense and trying now). The new tagging scheme is not documented
> in the bug in spite of Alex Brett asking for it, so once again:
> @anyone: is this described somewhere?
> 
> -- 
> Daan

RE: test case tagging and travis output

[Santhosh Edukulla]

One small note regarding return values, if we are running tests using nose, 
then discovery, run and report is all handled by it, so in a way commands 
output depends on the nose handling success, failure and error output from 
tests, its nothing to do much with marvin.


Regards,
Santhosh

From: Sebastien Goasguen [run...@gmail.com]
Sent: Thursday, September 04, 2014 10:19 AM
To: dev@cloudstack.apache.org
Cc: Ian Duffy
Subject: Re: test case tagging and travis output

On Sep 4, 2014, at 10:14 AM, Daan Hoogland  wrote:

> H Ian,
>
> As discussed off-list I am looking at the failure of extractIso in the

fwiw, I removed that test from 4.3 testing.

all test seem to pass for 4.3 but Travis still outputs "red" because of some 
strange return values by Marvin

but with the marvin refactoring, there are differences between master, 4.4 and 
4.3.


> travis-ci run of the 4.4 branch. Can I tune it to give more output? Unlike
> the expungeVM test, this one is not run in the simulator-singlerun so
> looking at the output there doesn't help.
>
> It seems that CLOUDSTACK-6914 introduced some new tagging scheme for test
> and I am assuming the new tagging should exclude the test from the travis
> run (makes sense and trying now). The new tagging scheme is not documented
> in the bug in spite of Alex Brett asking for it, so once again:
> @anyone: is this described somewhere?
>
> --
> Daan

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

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/16#issuecomment-54487736
  
Hi Leo, thanks for the PR.

I see you've refactored the 32 and 64 bit building scripts to one which is 
great!
I'll be able to test it next week and help you get it fixed if needed and 
merged. Meanwhile you may ask Hugo to set a test build job for testing the 
appliances. And some basic tests using those built systemvm templates both 32 
and 64 bits.


---
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: CLOUDSTACK-7143: Refactoring of the syste...

[lsimons]

Github user lsimons commented on the pull request:

https://github.com/apache/cloudstack/pull/16#issuecomment-54490782
  
Hey Rohit, thanks for reviewing!

We actually have a new vagrant-based component test setup for the systemvm 
to contribute, too; I'm working on extracting that now from the schubergphilis 
feature/systemvm-persistent-config branch. Our internal jenkins setup is 
already running those tests, as well as wider-scale marvin-driven integration 
tests that use these new-style systemvms. That's why I think this is ready for 
upstream: I'm pretty confident this stuff all still works properly.tough of 
course that _really_ _really_ needs careful verification outside of our 
assumptions/environment.

I'll try and work with Hugo to port those jenkins builds to 
buildacloud.org...hope he has time for it :)



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

[ACS431] Vote coming

[sebgoa]

Folks,

I am going to send a 4.3.1 release up for vote.

People have been asking me for 4.3.1 for couple months now and it took me a 
while to get to it. There is over 50 bug fixes in this release.

This is a bit new for us as 4.4.0 has already been released. I do feel that 4.3 
is a solid release branch and deserves some effort at figuring out how to do 
some long term support.

The jenkins build jobs are passing except the systemvm ones.
TravisCI was enabled and some smoke tests were run for an advanced zone 
configuration.
Unfortunately the tests do not show up as green and a little more work is 
needed to get there.

However in order to provide a relatively clean upgrade path from 4.3.1 to 4.4.1 
I am starting a vote.

If we could keep the 4.3.1 discussion in this very thread, it would keep the 
VOTE thread clean.

Cheers,

-Sebastien

[VOTE] Release Apache CloudStack 4.3.1

[sebgoa]

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: 41c0eaa14d2f8cd5b58bca71f2254c2390cc6913

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.

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: test case tagging and travis output

[Sebastien Goasguen]

On Sep 4, 2014, at 10:34 AM, Santhosh Edukulla  
wrote:

> One small note regarding return values, if we are running tests using nose, 
> then discovery, run and report is all handled by it, so in a way commands 
> output depends on the nose handling success, failure and error output from 
> tests, its nothing to do much with marvin.
> 

Maybe you can help us figuring out why some tests are red in:

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

Could be the way we deploy the simulator and run the test on travis, could be 
nose, could be the tags we are using...

> 
> Regards,
> Santhosh
> 
> From: Sebastien Goasguen [run...@gmail.com]
> Sent: Thursday, September 04, 2014 10:19 AM
> To: dev@cloudstack.apache.org
> Cc: Ian Duffy
> Subject: Re: test case tagging and travis output
> 
> On Sep 4, 2014, at 10:14 AM, Daan Hoogland  wrote:
> 
>> H Ian,
>> 
>> As discussed off-list I am looking at the failure of extractIso in the
> 
> fwiw, I removed that test from 4.3 testing.
> 
> all test seem to pass for 4.3 but Travis still outputs "red" because of some 
> strange return values by Marvin
> 
> but with the marvin refactoring, there are differences between master, 4.4 
> and 4.3.
> 
> 
>> travis-ci run of the 4.4 branch. Can I tune it to give more output? Unlike
>> the expungeVM test, this one is not run in the simulator-singlerun so
>> looking at the output there doesn't help.
>> 
>> It seems that CLOUDSTACK-6914 introduced some new tagging scheme for test
>> and I am assuming the new tagging should exclude the test from the travis
>> run (makes sense and trying now). The new tagging scheme is not documented
>> in the bug in spite of Alex Brett asking for it, so once again:
>> @anyone: is this described somewhere?
>> 
>> --
>> Daan
> 

Build failed in Jenkins: simulator-singlerun #290

[jenkins]

See 

Changes:

[kishan] CLOUDSTACK-7473: Vm migration is not supported for LXC. When host is 
put in maintenance mode, stop the Vms instead of migrating

--
[...truncated 5007 lines...]
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
cloud-plugin-user-authenticator-plaintext ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ 
cloud-plugin-user-authenticator-plaintext ---
[INFO] Surefire report directory: 


---
 T E S T S
---

Results :

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

[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ 
cloud-plugin-user-authenticator-plaintext ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ 
cloud-plugin-user-authenticator-plaintext ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
cloud-plugin-user-authenticator-plaintext ---
[INFO] Installing 

 to 
/var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-plugin-user-authenticator-plaintext/4.5.0-SNAPSHOT/cloud-plugin-user-authenticator-plaintext-4.5.0-SNAPSHOT.jar
[INFO] Installing 

 to 
/var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-plugin-user-authenticator-plaintext/4.5.0-SNAPSHOT/cloud-plugin-user-authenticator-plaintext-4.5.0-SNAPSHOT.pom
[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Plugin - User Authenticator SAML2 
4.5.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
cloud-plugin-user-authenticator-saml2 ---
[INFO] Deleting 

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

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

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-plugin-user-authenticator-saml2 ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-plugin-user-authenticator-saml2 ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
cloud-plugin-user-authenticator-saml2 ---
[INFO] Compiling 7 source files to 

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

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
cloud-plugin-user-authenticator-saml2 ---
[INFO] Compiling 4 source files to 

[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ 
cloud-plugin-user-authenticator-saml2 ---
[INFO] Surefire report directory: 


---
 T E S T S
---
Running org.apache.cloudstack.SAML2UserAuthenticatorTest
log4j:WARN No appenders could be found for logger 
(org.apache.cloudstack.saml.SAML2UserAuthenticator).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/f

[ASK] Download volume failed for 4.3.0/ESX

[Rohit Yadav]

Hi,

Is anyone having issues around downloading volumes or templates from UI when 
using Apache CloudStack 4.3.0 with vmware/ESXi?

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: [ACS431] Vote coming

[Rohit Yadav]

On 04-Sep-2014, at 5:04 pm, sebgoa  wrote:

> Folks,
>
> I am going to send a 4.3.1 release up for vote.
>
> People have been asking me for 4.3.1 for couple months now and it took me a 
> while to get to it. There is over 50 bug fixes in this release.
>
> This is a bit new for us as 4.4.0 has already been released. I do feel that 
> 4.3 is a solid release branch and deserves some effort at figuring out how to 
> do some long term support.
>
> The jenkins build jobs are passing except the systemvm ones.
> TravisCI was enabled and some smoke tests were run for an advanced zone 
> configuration.
> Unfortunately the tests do not show up as green and a little more work is 
> needed to get there.
>
> However in order to provide a relatively clean upgrade path from 4.3.1 to 
> 4.4.1 I am starting a vote.
>
> If we could keep the 4.3.1 discussion in this very thread, it would keep the 
> VOTE thread clean.

I’ll add an upgrade path from 4.3.1 to 4.4.1 via 4.4.0 in 4.4 branch, and send 
the hotfix pull request to Daan.

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: test case tagging and travis output

[Alex Brett]

On 04 September 2014 15:14, Daan Hoogland [daan.hoogl...@gmail.com] wrote:
> It seems that CLOUDSTACK-6914 introduced some new tagging scheme for test
> and I am assuming the new tagging should exclude the test from the travis
> run (makes sense and trying now). The new tagging scheme is not documented
> in the bug in spite of Alex Brett asking for it, so once again:
> @anyone: is this described somewhere?

I'm not sure what exactly you're trying to achieve, but I've found what was 
done in CLOUDSTACK-6914 is limited as to what it can do - I've got a couple of 
reviews outstanding that could be relevant here which are:

CLOUDSTACK-7307 / https://reviews.apache.org/r/24552/
CLOUDSTACK-7322 / https://reviews.apache.org/r/24605/

Feel free to take a look and see if you agree with what they're trying to do...

Cheers,
Alex

Re: Review Request 24794: Review request for CLOUDSTACK-6169 - assignVirtualMachine leaves associated tags assigned to old account

[Marcus]

As I mentioned, I'm probably the wrong person to review this fix, though I
did record the bug. If someone. If someone has domain knowledge in this
particular area please take a look.
On Sep 4, 2014 12:17 AM, "Namita Chaudhari" 
wrote:

> Gentle reminder..
>
>
> On Mon, Aug 18, 2014 at 3:24 PM, Namita Chaudhari <
> namita.chaudh...@sungard.com> wrote:
>
>>
>> ---
>> This is an automatically generated e-mail. To reply, visit:
>> https://reviews.apache.org/r/24794/
>> ---
>>
>> Review request for cloudstack and Marcus Sorensen.
>>
>>
>> Bugs: CLOUDSTACK-6169 and
>> https://issues.apache.org/jira/browse/CLOUDSTACK-6169
>> https://issues.apache.org/jira/browse/CLOUDSTACK-6169
>>
>> https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/CLOUDSTACK-6169
>>
>>
>> Repository: cloudstack-git
>>
>>
>> Description
>> ---
>>
>> CLOUDSTACK-6169 - assignVirtualMachine leaves associated tags assigned to
>> old account
>>
>> When a VM is assigned from one account to another, the tags associated to
>> the VM points to the new account and not old one.
>>
>>
>> Diffs
>> -
>>
>>   engine/schema/src/com/cloud/tags/ResourceTagVO.java ea1
>>   engine/schema/src/com/cloud/tags/dao/ResourceTagDao.java fffe2a47
>>   engine/schema/src/com/cloud/tags/dao/ResourceTagsDaoImpl.java 3611999
>>   server/src/com/cloud/vm/UserVmManagerImpl.java e5de11f
>>
>> Diff: https://reviews.apache.org/r/24794/diff/
>>
>>
>> Testing
>> ---
>>
>> Yes.
>>
>>
>> Thanks,
>>
>> Namita Chaudhari
>>
>>
>
>
> --
>
> *Namita Chaudhari* ● Engineer - Product Development ● SunGard
> Availability Services, India. ● 2nd Floor, Wing 4, Cluster D, MIDC
> Kharadi Knowledge Park, Pune - 411 014 ● Email:
> namita.chaudh...@sungardas.com  ●
> www.sungardas.in
>
>
>
> [image: Description: cid:image019.png@01CF48EC.6617C7F0]  [image:
> Description: cid:image020.png@01CF48EC.6617C7F0]  [image: Description:
> cid:image021.png@01CF48EC.6617C7F0]  [image: Description:
> cid:image022.png@01CF48EC.6617C7F0]  [image: Description:
> cid:image023.png@01CF48EC.6617C7F0]  [image: Description:
> cid:image024.png@01CF48EC.6617C7F0]
>
>

Jenkins build is unstable: simulator-singlerun #291

[jenkins]

See 

hotfix/4.4/upgradepath-431to441: DB Upgrade path from 4.3.1 to 4.4.1

[Rohit Yadav]

Hi Daan,

Please check and pick commits from this branch, they add db upgrade path from 
4.3.1 to 4.4.1;
hotfix/4.4/upgradepath-431to441

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: [REVIEW] CLOUDSTACK-7468 in master

[Will Stevens]

Following up on this...

Who should I be asking to merge this into master?  Should I just be pushing
my changes directly into master?  I thought we wanted features and fixes to
go through the RM for the release, is this not the case.

I have the following fixes waiting for commit:
CLOUDSTACK-7468:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5d11385
CLOUDSTACK-7418:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=18653f6

Let me know if I should just be pushing these directly into master...

Cheers,

Will



*Will STEVENS*
Lead Developer

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


On Wed, Sep 3, 2014 at 3:02 PM, Will Stevens  wrote:

> Here is a link to the issue:
> https://issues.apache.org/jira/browse/CLOUDSTACK-7468
>
> This fix has been committed in the 4.4 branch already.  I have pushed a
> feature branch called 'CLOUDSTACK-7468' to the ASF repo which is a branch
> off master with the fix applied.  The fix for master is here:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5d11385
>
> I am not sure how the release manager is for 4.5, but can someone please
> review and commit the fix into master?
>
> Thanks,
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
>

Re: Review Request 25289: CLOUDSTACK-7474-Failed-to-start-MS-with-java7-version

[Frank Zhang]

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

Ship it!


Ship It!

- Frank Zhang


On Sept. 3, 2014, 6:25 a.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25289/
> ---
> 
> (Updated Sept. 3, 2014, 6:25 a.m.)
> 
> 
> Review request for cloudstack, Frank Zhang and Hugo Trippaers.
> 
> 
> Bugs: CLOUDSTACK-7474
> https://issues.apache.org/jira/browse/CLOUDSTACK-7474
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Step 1: Deploy new RHEL 6.3 machine
> Step 2 : Install MS
> Step 3: run deploy script and start MS
> 
> Result 
> 
> Installation completed successfully,  both java7 and java got installed as 
> part of MS installation, but MS failed to start java version erro
> 
> we need to load java7 while start MS
> 
> 
> Diffs
> -
> 
>   client/tomcatconf/classpath.conf.in 3ae0fb4 
> 
> Diff: https://reviews.apache.org/r/25289/diff/
> 
> 
> Testing
> ---
> 
> Yes
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

Re: [REVIEW] CLOUDSTACK-7468 in master

[sebgoa]

On Sep 4, 2014, at 7:17 PM, Will Stevens  wrote:

> Following up on this...
> 
> Who should I be asking to merge this into master?  Should I just be pushing
> my changes directly into master?  I thought we wanted features and fixes to
> go through the RM for the release, is this not the case.
> 
> I have the following fixes waiting for commit:
> CLOUDSTACK-7468:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5d11385
> CLOUDSTACK-7418:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=18653f6
> 
> Let me know if I should just be pushing these directly into master…
> 

Hi Will,

So I see two branches from you hotfix/4.4-7418 and CLOUDSTACK-7418

Are these the same fix, did you mean to do this ?

Technically you can push to master yourself without asking.

Ideally :) the build on your hot fix branch should be green with test passing 
and with additional integration tests (assuming they could run with the 
simulator).

Check:

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

If you could spend some time checking the .travis.yml file and understanding 
how it runs the test you could help with making it green :)

-sebastien

> Cheers,
> 
> Will
> 
> 
> 
> *Will STEVENS*
> Lead Developer
> 
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
> 
> 
> On Wed, Sep 3, 2014 at 3:02 PM, Will Stevens  wrote:
> 
>> Here is a link to the issue:
>> https://issues.apache.org/jira/browse/CLOUDSTACK-7468
>> 
>> This fix has been committed in the 4.4 branch already.  I have pushed a
>> feature branch called 'CLOUDSTACK-7468' to the ASF repo which is a branch
>> off master with the fix applied.  The fix for master is here:
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5d11385
>> 
>> I am not sure how the release manager is for 4.5, but can someone please
>> review and commit the fix into master?
>> 
>> Thanks,
>> 
>> *Will STEVENS*
>> Lead Developer
>> 
>> *CloudOps* *| *Cloud Solutions Experts
>> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>> w cloudops.com *|* tw @CloudOps_
>> 
>> 

Re: [REVIEW] CLOUDSTACK-7468 in master

[Will Stevens]

yes, those are both the same fix.  One is targeting the 4.4 branch for Daan
to merge.  The other is targeting the master branch...

as for the tests, I can look into travis.  where is this .travis.yml you
speak of?  is there docs anywhere on this?

I did real tests on an actual environment with my own script/test framework
to make sure everything is functional and works as expected.
ws



*Will STEVENS*
Lead Developer

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


On Thu, Sep 4, 2014 at 1:23 PM, sebgoa  wrote:

>
> On Sep 4, 2014, at 7:17 PM, Will Stevens  wrote:
>
> > Following up on this...
> >
> > Who should I be asking to merge this into master?  Should I just be
> pushing
> > my changes directly into master?  I thought we wanted features and fixes
> to
> > go through the RM for the release, is this not the case.
> >
> > I have the following fixes waiting for commit:
> > CLOUDSTACK-7468:
> > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5d11385
> > CLOUDSTACK-7418:
> > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=18653f6
> >
> > Let me know if I should just be pushing these directly into master…
> >
>
> Hi Will,
>
> So I see two branches from you hotfix/4.4-7418 and CLOUDSTACK-7418
>
> Are these the same fix, did you mean to do this ?
>
> Technically you can push to master yourself without asking.
>
> Ideally :) the build on your hot fix branch should be green with test
> passing and with additional integration tests (assuming they could run with
> the simulator).
>
> Check:
>
> https://travis-ci.org/apache/cloudstack/builds
>
> If you could spend some time checking the .travis.yml file and
> understanding how it runs the test you could help with making it green :)
>
> -sebastien
>
> > Cheers,
> >
> > Will
> >
> >
> >
> > *Will STEVENS*
> > Lead Developer
> >
> > *CloudOps* *| *Cloud Solutions Experts
> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> > w cloudops.com *|* tw @CloudOps_
> >
> >
> > On Wed, Sep 3, 2014 at 3:02 PM, Will Stevens 
> wrote:
> >
> >> Here is a link to the issue:
> >> https://issues.apache.org/jira/browse/CLOUDSTACK-7468
> >>
> >> This fix has been committed in the 4.4 branch already.  I have pushed a
> >> feature branch called 'CLOUDSTACK-7468' to the ASF repo which is a
> branch
> >> off master with the fix applied.  The fix for master is here:
> >> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5d11385
> >>
> >> I am not sure how the release manager is for 4.5, but can someone please
> >> review and commit the fix into master?
> >>
> >> Thanks,
> >>
> >> *Will STEVENS*
> >> Lead Developer
> >>
> >> *CloudOps* *| *Cloud Solutions Experts
> >> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> >> w cloudops.com *|* tw @CloudOps_
> >>
> >>
>
>

Build failed in Jenkins: simulator-hotfix-trigger #31

[jenkins]

See 

--
[...truncated 7106 lines...]
[INFO] 
[INFO] Building Apache CloudStack Developer Mode 4.4.1-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties 
(default) @ cloud-developer ---
[WARNING] Ignoring missing properties file: 

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-developer ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (default) @ cloud-developer ---
[INFO] Executing tasks

main:
[INFO] Executed tasks
[INFO] 
[INFO] >>> exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer >>>
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] <<< exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer <<<
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer ---
log4j:WARN No appenders could be found for logger 
(org.springframework.core.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
> WARNING: Provided file does not exist: 

> Initializing database=simulator with host=localhost port=3306 
username=cloud password=cloud
> Running query: drop database if exists `simulator`
> Running query: create database `simulator`
> Running query: GRANT ALL ON simulator.* to 'cloud'@`localhost` 
identified by 'cloud'
> Running query: GRANT ALL ON simulator.* to 'cloud'@`%` identified 
by 'cloud'
> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ 
cloud-developer ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
cloud-developer ---
[INFO] Installing 

 to 
/var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.4.1-SNAPSHOT/cloud-developer-4.4.1-SNAPSHOT.pom
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 22.837s
[INFO] Finished at: Thu Sep 04 13:17:07 EDT 2014
[INFO] Final Memory: 42M/180M
[INFO] 
[simulator-hotfix-trigger] $ /bin/bash -x /tmp/hudson5794638117678804368.sh
+ grep -q Launcher
+ jps -l
+ rm -f xunit.xml
+ rm -rf /tmp/MarvinLogs
+ echo Check for initialization of the management server
Check for initialization of the management server
+ COUNTER=0
+ SERVER_PID=32396
+ mvn -P systemvm,simulator -pl :cloud-client-ui jetty:run
+ '[' 0 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=1
+ '[' 1 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=2
+ '[' 2 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=3
+ '[' 3 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=4
+ '[' 4 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=5
+ '[' 5 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=6
+ '[' 6 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=7
+ '[' 7 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=8
+ '[' 8 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=9
+ '[' 9 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=10
+ 

Re: [REVIEW] CLOUDSTACK-7468 in master

[Will Stevens]

I found the .travis.yml file.  I still need to figure out how to use
travis, so I will have to research that...

ws


*Will STEVENS*
Lead Developer

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


On Thu, Sep 4, 2014 at 1:49 PM, Will Stevens  wrote:

> yes, those are both the same fix.  One is targeting the 4.4 branch for
> Daan to merge.  The other is targeting the master branch...
>
> as for the tests, I can look into travis.  where is this .travis.yml you
> speak of?  is there docs anywhere on this?
>
> I did real tests on an actual environment with my own script/test
> framework to make sure everything is functional and works as expected.
> ws
>
>
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
>
> On Thu, Sep 4, 2014 at 1:23 PM, sebgoa  wrote:
>
>>
>> On Sep 4, 2014, at 7:17 PM, Will Stevens  wrote:
>>
>> > Following up on this...
>> >
>> > Who should I be asking to merge this into master?  Should I just be
>> pushing
>> > my changes directly into master?  I thought we wanted features and
>> fixes to
>> > go through the RM for the release, is this not the case.
>> >
>> > I have the following fixes waiting for commit:
>> > CLOUDSTACK-7468:
>> > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5d11385
>> > CLOUDSTACK-7418:
>> > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=18653f6
>> >
>> > Let me know if I should just be pushing these directly into master…
>> >
>>
>> Hi Will,
>>
>> So I see two branches from you hotfix/4.4-7418 and CLOUDSTACK-7418
>>
>> Are these the same fix, did you mean to do this ?
>>
>> Technically you can push to master yourself without asking.
>>
>> Ideally :) the build on your hot fix branch should be green with test
>> passing and with additional integration tests (assuming they could run with
>> the simulator).
>>
>> Check:
>>
>> https://travis-ci.org/apache/cloudstack/builds
>>
>> If you could spend some time checking the .travis.yml file and
>> understanding how it runs the test you could help with making it green :)
>>
>> -sebastien
>>
>> > Cheers,
>> >
>> > Will
>> >
>> >
>> >
>> > *Will STEVENS*
>> > Lead Developer
>> >
>> > *CloudOps* *| *Cloud Solutions Experts
>> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>> > w cloudops.com *|* tw @CloudOps_
>> >
>> >
>> > On Wed, Sep 3, 2014 at 3:02 PM, Will Stevens 
>> wrote:
>> >
>> >> Here is a link to the issue:
>> >> https://issues.apache.org/jira/browse/CLOUDSTACK-7468
>> >>
>> >> This fix has been committed in the 4.4 branch already.  I have pushed a
>> >> feature branch called 'CLOUDSTACK-7468' to the ASF repo which is a
>> branch
>> >> off master with the fix applied.  The fix for master is here:
>> >> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5d11385
>> >>
>> >> I am not sure how the release manager is for 4.5, but can someone
>> please
>> >> review and commit the fix into master?
>> >>
>> >> Thanks,
>> >>
>> >> *Will STEVENS*
>> >> Lead Developer
>> >>
>> >> *CloudOps* *| *Cloud Solutions Experts
>> >> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>> >> w cloudops.com *|* tw @CloudOps_
>> >>
>> >>
>>
>>
>

Re: Review Request 25248: Fix NPE in case VM is started and its template does not exist anymore

[Rohit Yadav]

> On Sept. 2, 2014, 7:01 p.m., Nitin Mehta wrote:
> > engine/orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java, line 
> > 814
> > 
> >
> > Checking for template==null masks the whole problem. 
> > 1. Such validations should have happenned in the deployvm api layer if 
> > it comes from that api.
> > 2. If its coming from a startvm api its perfectly fine to have the 
> > template removed since the volume already exists. 
> > 3. If you see how template is used below...if it has to 'create' a new 
> > volume the template shouldnt be removed but again the validations should be 
> > in api layer.
> 
> Rohit Yadav wrote:
> So, I can read code too, upper layers are not passing the template so 
> what do you propose? How may I fix this then?
> 
> Nitin Mehta wrote:
> Firstly, check whether the issue is reproducible. Just realized that from 
> 4.3 onwards templates have 'Inactive' state to mark it removed. Removed 
> attribute should never be set so this exception shouldnt be hit . Check when 
> is the removed flag set as it should be a bug(check CLOUDSTACK-5997 and 
> backporting it already fixes that). 
> Secondly, even if this bug doesnt exist, do a sanity check and see this 
> kind of check is in the api which will ultimately call this method. Check if 
> apis are missing them. But some apis might not need it like StartVm, Rebootvm 
> where new volume is not created. Do write a util method which could be shared 
> by all apis. I guess that should be good enough.

This was for 4.3.1, I guess this is a special case and not a blocker. The issue 
was reproducible when say an admin removed a template where a user may be 
trying to create a VM and was in a wizard. I'm closing as we're not putting 
this for 4.3.1 release.


- Rohit


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


On Sept. 2, 2014, 1:53 p.m., Rohit Yadav wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25248/
> ---
> 
> (Updated Sept. 2, 2014, 1:53 p.m.)
> 
> 
> Review request for cloudstack, Alena Prokharchyk, edison su, Darren Shepherd, 
> Sebastien Goasguen, and Hugo Trippaers.
> 
> 
> Bugs: CLOUDSTACK-6945
> https://issues.apache.org/jira/browse/CLOUDSTACK-6945
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fixes https://issues.apache.org/jira/browse/CLOUDSTACK-6945
> 
> 
> Diffs
> -
> 
>   engine/orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java 
> 2fd7a52 
> 
> Diff: https://reviews.apache.org/r/25248/diff/
> 
> 
> Testing
> ---
> 
> Builds cleanly, will throw resource not available exception when template 
> does not exist.
> 
> 
> Thanks,
> 
> Rohit Yadav
> 
>

Jenkins build is still unstable: simulator-singlerun #292

[jenkins]

See 

Re: Review Request 25289: CLOUDSTACK-7474-Failed-to-start-MS-with-java7-version

[Rohit Yadav]

> On Sept. 3, 2014, 9:32 a.m., Rajani Karuturi wrote:
> > client/tomcatconf/classpath.conf.in, line 37
> > 
> >
> > Can we get the JAVA_HOME from installed java instead of hardcoding it? 
> > The path may be different for different os versions or distributions. 
> > 
> > something similar to what we already did at 
> > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=c468228fe807c621decc5919dadae9bcbb38c753
> > 
> > May we should move this to a common file like setenv.sh and use it 
> > everywhere.
> 
> Frank Zhang wrote:
> +1
> 
> Rayees Namathponnan wrote:
> Hi Rajani,
> 
> I checked your change list, if your machine in running with default java 
> version is 1.6,  this will always return 1.6 and management server will fails 
> to start 
> 
> 
> Even usage sever will be an issue in 4.5, if your machine is runnign with 
> java1.6
> 
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blobdiff;f=packaging/centos63/cloud-usage.rc;h=8434e4d568a066d0766d055847725b1779eb33c4;hp=617037995755024a8c9d5e492bb56b7cc938e48f;hb=c468228fe807c621decc5919dadae9bcbb38c753;hpb=75c9a20c7773c268c02fb006d1a7820cb427c94c
> 
> 
> Regards,
> Rayees
> 
> Alex Brett wrote:
> To expand on this a little bit - in RHEL 6.3 if you have both Java 1.6 
> and Java 7 installed, the default behaviour with the alternatives mechanism 
> makes 1.6 the default Java instance (you can manually set 1.7 as the default, 
> but this is an extra step). This means that the management server / KVM agent 
> then fail to work.
> 
> In 6.5 if you have both then by default Java 7 is used, and all works 
> fine (not sure about 6.4 or 7, I've not tested them).

Since, we want to use 1.7 if available and not 1.6; it makes sense to either 
use Rajani's find JAVA_HOME fix as seen in the init scripts, or try searching 
in paths: JDK_DIRS="/usr/lib/jvm/java-7-openjdk-amd64 
/usr/lib/jvm/java-7-openjdk-i386 /usr/lib/jvm/java-6-openjdk 
/usr/lib/jvm/java-6-openjdk-i386 /usr/lib/jvm/java-6-openjdk-amd64 
/usr/lib/jvm/java-6-sun" ... like we used to do before Rajani's fix


- Rohit


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


On Sept. 3, 2014, 6:25 a.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25289/
> ---
> 
> (Updated Sept. 3, 2014, 6:25 a.m.)
> 
> 
> Review request for cloudstack, Frank Zhang and Hugo Trippaers.
> 
> 
> Bugs: CLOUDSTACK-7474
> https://issues.apache.org/jira/browse/CLOUDSTACK-7474
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Step 1: Deploy new RHEL 6.3 machine
> Step 2 : Install MS
> Step 3: run deploy script and start MS
> 
> Result 
> 
> Installation completed successfully,  both java7 and java got installed as 
> part of MS installation, but MS failed to start java version erro
> 
> we need to load java7 while start MS
> 
> 
> Diffs
> -
> 
>   client/tomcatconf/classpath.conf.in 3ae0fb4 
> 
> Diff: https://reviews.apache.org/r/25289/diff/
> 
> 
> Testing
> ---
> 
> Yes
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

Re: Review Request 25289: CLOUDSTACK-7474-Failed-to-start-MS-with-java7-version

[Rohit Yadav]

> On Sept. 4, 2014, 5:21 p.m., Frank Zhang wrote:
> > Ship It!

Rayees can you please fix it and upload a second patch; don't commit on master 
yet please.


- Rohit


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


On Sept. 3, 2014, 6:25 a.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25289/
> ---
> 
> (Updated Sept. 3, 2014, 6:25 a.m.)
> 
> 
> Review request for cloudstack, Frank Zhang and Hugo Trippaers.
> 
> 
> Bugs: CLOUDSTACK-7474
> https://issues.apache.org/jira/browse/CLOUDSTACK-7474
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Step 1: Deploy new RHEL 6.3 machine
> Step 2 : Install MS
> Step 3: run deploy script and start MS
> 
> Result 
> 
> Installation completed successfully,  both java7 and java got installed as 
> part of MS installation, but MS failed to start java version erro
> 
> we need to load java7 while start MS
> 
> 
> Diffs
> -
> 
>   client/tomcatconf/classpath.conf.in 3ae0fb4 
> 
> Diff: https://reviews.apache.org/r/25289/diff/
> 
> 
> Testing
> ---
> 
> Yes
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

Re: [ASK] Download volume failed for 4.3.0/ESX

[ilya musayev]

Rohit,

I've been using ACS 4.3.0+ with VmWare vSphere 5.1 and 5.5 for quite 
sometime, I do not see any issues with downloads of templates.


Perhaps its related to NFS mount or blocking firewall. You can see all 
the operations performed in vCenter Tasks. Make sure you can mount NFS 
secondary on hypervisors as well as SSVM.


Logs would help, take a look at SSVM logs.

Regards
ilya

On 9/4/14, 9:47 AM, Rohit Yadav wrote:

Hi,

Is anyone having issues around downloading volumes or templates from UI when 
using Apache CloudStack 4.3.0 with vmware/ESXi?

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.

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

[jenkins]

See 

Changes:

[brian.federle] Quickview: Fix alignment

--
[...truncated 5058 lines...]
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ 
cloud-plugin-user-authenticator-md5 ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
cloud-plugin-user-authenticator-md5 ---
[INFO] Installing 

 to 
/jenkins/.m2/repository/org/apache/cloudstack/cloud-plugin-user-authenticator-md5/4.5.0-SNAPSHOT/cloud-plugin-user-authenticator-md5-4.5.0-SNAPSHOT.jar
[INFO] Installing 

 to 
/jenkins/.m2/repository/org/apache/cloudstack/cloud-plugin-user-authenticator-md5/4.5.0-SNAPSHOT/cloud-plugin-user-authenticator-md5-4.5.0-SNAPSHOT.pom
[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Plugin - User Authenticator Plain Text 
4.5.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
cloud-plugin-user-authenticator-plaintext ---
[INFO] Deleting 

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

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

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-plugin-user-authenticator-plaintext ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-plugin-user-authenticator-plaintext ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
cloud-plugin-user-authenticator-plaintext ---
[INFO] Compiling 1 source file to 

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

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


---
 T E S T S
---

Results :

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

[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ 
cloud-plugin-user-authenticator-plaintext ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ 
cloud-plugin-user-authenticator-plaintext ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
cloud-plugin-user-authenticator-plaintext ---
[INFO] Installing 

 to 
/jenkins/.m2/repository/org/apache/cloudstack/cloud-plugin-user-authenticator-plaintext/4.5.0-SNAPSHOT/cloud-plugin-user-authenticator-plaintext-4.5.0-SNAPSHOT.jar
[INFO] Installing 

 to 
/jenkins/.m2/repository/org/apache/cloudstack/cloud-plugin-user-authenticator-plaintext/4.5.0-SNAPSHOT/cloud-plugin-user-authenticator-plaintext-4.5.0-SNAPSHOT.pom
[INFO] 
[INFO] -

Jenkins build is still unstable: simulator-singlerun #293

[jenkins]

See 

Re: [ASK] Download volume failed for 4.3.0/ESX

[Rohit Yadav]

Thank you Ilya! Someone reported this bug to me, and I could not reproduce it 
for KVM and Xen for both 4.3.0 and 4.3.1-voting, since we’re going to release 
4.3.1 I just wanted to check if this really existed as I don’t have ESX setup 
and license to test it out.

I personally think 4.3.0 was a  good release and I think 4.3.1 would further 
ship a robust release for our users. Thanks again for confirming.

On 04-Sep-2014, at 9:14 pm, ilya musayev  wrote:

> Rohit,
>
> I've been using ACS 4.3.0+ with VmWare vSphere 5.1 and 5.5 for quite 
> sometime, I do not see any issues with downloads of templates.
>
> Perhaps its related to NFS mount or blocking firewall. You can see all the 
> operations performed in vCenter Tasks. Make sure you can mount NFS secondary 
> on hypervisors as well as SSVM.
>
> Logs would help, take a look at SSVM logs.
>
> Regards
> ilya
>
> On 9/4/14, 9:47 AM, Rohit Yadav wrote:
>> Hi,
>>
>> Is anyone having issues around downloading volumes or templates from UI when 
>> using Apache CloudStack 4.3.0 with vmware/ESXi?
>>
>> 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.
>
>

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: [ACS431] Vote coming

[Daan Hoogland]

saw the branch, will look at merging, Rohit.


On Thu, Sep 4, 2014 at 6:58 PM, Rohit Yadav 
wrote:

>
> On 04-Sep-2014, at 5:04 pm, sebgoa  wrote:
>
> > Folks,
> >
> > I am going to send a 4.3.1 release up for vote.
> >
> > People have been asking me for 4.3.1 for couple months now and it took
> me a while to get to it. There is over 50 bug fixes in this release.
> >
> > This is a bit new for us as 4.4.0 has already been released. I do feel
> that 4.3 is a solid release branch and deserves some effort at figuring out
> how to do some long term support.
> >
> > The jenkins build jobs are passing except the systemvm ones.
> > TravisCI was enabled and some smoke tests were run for an advanced zone
> configuration.
> > Unfortunately the tests do not show up as green and a little more work
> is needed to get there.
> >
> > However in order to provide a relatively clean upgrade path from 4.3.1
> to 4.4.1 I am starting a vote.
> >
> > If we could keep the 4.3.1 discussion in this very thread, it would keep
> the VOTE thread clean.
>
> I’ll add an upgrade path from 4.3.1 to 4.4.1 via 4.4.0 in 4.4 branch, and
> send the hotfix pull request to Daan.
>
> 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.
>



-- 
Daan

[ACS431] Help testing 4.3.1 vote candidate

[Rohit Yadav]

Dear community,

Please help in testing 4.3.1 voting candidate that Sebastien has just shared 
today. 4.3.0 was a good release, this minor release tries to fix several issues 
but we need regression testing.

To get help from community folks who don’t want to build from source, I’ve 
built and put debs and rpm using the voting candidate 
(41c0eaa14d2f8cd5b58bca71f2254c2390cc6913).

For debian, put this in sources.list and install/upgrade:

deb http://packages.bhaisaab.org/cloudstack/main/debian ./

For centos/fedora/rhel, put this in a yum.repos.d/cloudstack.repo:

[apache-cloudstack]
name=Apache CloudStack
baseurl=http://packages.bhaisaab.org/cloudstack/main/centos/
enabled=1
gpgcheck=0

Feel free to use them, this location is temporary. This repo was created using:
http://cloudstack-installation.readthedocs.org/en/latest/building_from_source.html#building-deb-packages

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: [ASK] Download volume failed for 4.3.0/ESX

[Rohit Yadav]

Hi Ilya,

Quick question — are you also able to download volumes using 4.3.0/ESX?

On 04-Sep-2014, at 9:14 pm, ilya musayev  wrote:
> Rohit,
>
> I've been using ACS 4.3.0+ with VmWare vSphere 5.1 and 5.5 for quite 
> sometime, I do not see any issues with downloads of templates.
>
> Perhaps its related to NFS mount or blocking firewall. You can see all the 
> operations performed in vCenter Tasks. Make sure you can mount NFS secondary 
> on hypervisors as well as SSVM.
>
> Logs would help, take a look at SSVM logs.
>
> Regards
> ilya
>
> On 9/4/14, 9:47 AM, Rohit Yadav wrote:
>> Hi,
>>
>> Is anyone having issues around downloading volumes or templates from UI when 
>> using Apache CloudStack 4.3.0 with vmware/ESXi?
>>
>> 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.
>
>

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: Review Request 25187: test_delete_account and test_releaseIP failing in advanced zone

[Chandan Purushothama]

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

Ship it!


Ship It!

- Chandan Purushothama


On Sept. 3, 2014, 3:17 p.m., Alex Brett wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25187/
> ---
> 
> (Updated Sept. 3, 2014, 3:17 p.m.)
> 
> 
> Review request for cloudstack, Ashutosh Kelkar, Santhosh Edukulla, and 
> SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-7448
> https://issues.apache.org/jira/browse/CLOUDSTACK-7448
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-4840 changed test_data.py to make the lbrule publicport be 22,
> instead of . In doing so, this caused the following tests to fail, as they
> hit a problem where they tried to use port 22 for both the lbrule and for 
> other
> purposes:
> integration.smoke.test_network.TestDeleteAccount.test_delete_account
> integration.smoke.test_network.TestReleaseIP.test_releaseIP
> 
> The reason the change appears to have been made was that in
> test_lb_secondary_ip.py, despite setting up the load balancer using lbrule, 
> the
> tests then used the SSH port from natrule to try and access the VM. By 
> changing
> lbrule to use port 22 (the same as natrule) this avoided the problem.
> 
> This patch updates test_lb_secondary_ip.py to use the SSH port in lbrule where
> necessary to access the VMs, and reverts the change to test_data.py
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_lb_secondary_ip.py f54caa6 
>   tools/marvin/marvin/config/test_data.py fca2442 
> 
> Diff: https://reviews.apache.org/r/25187/diff/
> 
> 
> Testing
> ---
> 
> Ran tests in test_lb_secondary_ip.py with changes in place, verified results 
> equivalent to those seen on regular regression runs.
> Ran test_delete_account and test_releaseIP to verify these now pass as 
> expected.
> 
> 
> Thanks,
> 
> Alex Brett
> 
>

Re: Review Request 25187: test_delete_account and test_releaseIP failing in advanced zone

[Chandan Purushothama]

> On Sept. 4, 2014, 8:24 p.m., Chandan Purushothama wrote:
> > Ship It!

I reviewed the patch. I read the entire test suite to understand the Use Cases. 
The Suite does refer to the wrong dictionary "nat_rule" instead of "lb_rule". 
Alex's patch should fix the issue.


- Chandan


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


On Sept. 3, 2014, 3:17 p.m., Alex Brett wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25187/
> ---
> 
> (Updated Sept. 3, 2014, 3:17 p.m.)
> 
> 
> Review request for cloudstack, Ashutosh Kelkar, Santhosh Edukulla, and 
> SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-7448
> https://issues.apache.org/jira/browse/CLOUDSTACK-7448
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-4840 changed test_data.py to make the lbrule publicport be 22,
> instead of . In doing so, this caused the following tests to fail, as they
> hit a problem where they tried to use port 22 for both the lbrule and for 
> other
> purposes:
> integration.smoke.test_network.TestDeleteAccount.test_delete_account
> integration.smoke.test_network.TestReleaseIP.test_releaseIP
> 
> The reason the change appears to have been made was that in
> test_lb_secondary_ip.py, despite setting up the load balancer using lbrule, 
> the
> tests then used the SSH port from natrule to try and access the VM. By 
> changing
> lbrule to use port 22 (the same as natrule) this avoided the problem.
> 
> This patch updates test_lb_secondary_ip.py to use the SSH port in lbrule where
> necessary to access the VMs, and reverts the change to test_data.py
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_lb_secondary_ip.py f54caa6 
>   tools/marvin/marvin/config/test_data.py fca2442 
> 
> Diff: https://reviews.apache.org/r/25187/diff/
> 
> 
> Testing
> ---
> 
> Ran tests in test_lb_secondary_ip.py with changes in place, verified results 
> equivalent to those seen on regular regression runs.
> Ran test_delete_account and test_releaseIP to verify these now pass as 
> expected.
> 
> 
> Thanks,
> 
> Alex Brett
> 
>

Re: [ACS431] Vote coming

[Daan Hoogland]

Rohit, I see you added a path from 4.3.1 to 4.4.1 via 4.4.0. Is this going
to work? It bypasses all schema - and data upgrades from 4.3.0 to 4.4.0.
Where did these go?

thanks,


On Thu, Sep 4, 2014 at 10:22 PM, Daan Hoogland 
wrote:

> saw the branch, will look at merging, Rohit.
>
>
> On Thu, Sep 4, 2014 at 6:58 PM, Rohit Yadav 
> wrote:
>
>>
>> On 04-Sep-2014, at 5:04 pm, sebgoa  wrote:
>>
>> > Folks,
>> >
>> > I am going to send a 4.3.1 release up for vote.
>> >
>> > People have been asking me for 4.3.1 for couple months now and it took
>> me a while to get to it. There is over 50 bug fixes in this release.
>> >
>> > This is a bit new for us as 4.4.0 has already been released. I do feel
>> that 4.3 is a solid release branch and deserves some effort at figuring out
>> how to do some long term support.
>> >
>> > The jenkins build jobs are passing except the systemvm ones.
>> > TravisCI was enabled and some smoke tests were run for an advanced zone
>> configuration.
>> > Unfortunately the tests do not show up as green and a little more work
>> is needed to get there.
>> >
>> > However in order to provide a relatively clean upgrade path from 4.3.1
>> to 4.4.1 I am starting a vote.
>> >
>> > If we could keep the 4.3.1 discussion in this very thread, it would
>> keep the VOTE thread clean.
>>
>> I’ll add an upgrade path from 4.3.1 to 4.4.1 via 4.4.0 in 4.4 branch, and
>> send the hotfix pull request to Daan.
>>
>> 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.
>>
>
>
>
> --
> Daan
>



-- 
Daan

Re: Review Request 25248: Fix NPE in case VM is started and its template does not exist anymore

[Nitin Mehta]

> On Sept. 2, 2014, 7:01 p.m., Nitin Mehta wrote:
> > engine/orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java, line 
> > 814
> > 
> >
> > Checking for template==null masks the whole problem. 
> > 1. Such validations should have happenned in the deployvm api layer if 
> > it comes from that api.
> > 2. If its coming from a startvm api its perfectly fine to have the 
> > template removed since the volume already exists. 
> > 3. If you see how template is used below...if it has to 'create' a new 
> > volume the template shouldnt be removed but again the validations should be 
> > in api layer.
> 
> Rohit Yadav wrote:
> So, I can read code too, upper layers are not passing the template so 
> what do you propose? How may I fix this then?
> 
> Nitin Mehta wrote:
> Firstly, check whether the issue is reproducible. Just realized that from 
> 4.3 onwards templates have 'Inactive' state to mark it removed. Removed 
> attribute should never be set so this exception shouldnt be hit . Check when 
> is the removed flag set as it should be a bug(check CLOUDSTACK-5997 and 
> backporting it already fixes that). 
> Secondly, even if this bug doesnt exist, do a sanity check and see this 
> kind of check is in the api which will ultimately call this method. Check if 
> apis are missing them. But some apis might not need it like StartVm, Rebootvm 
> where new volume is not created. Do write a util method which could be shared 
> by all apis. I guess that should be good enough.
> 
> Rohit Yadav wrote:
> This was for 4.3.1, I guess this is a special case and not a blocker. The 
> issue was reproducible when say an admin removed a template where a user may 
> be trying to create a VM and was in a wizard. I'm closing as we're not 
> putting this for 4.3.1 release.

Please punt it for 4.5. We should fix it.


- Nitin


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


On Sept. 2, 2014, 1:53 p.m., Rohit Yadav wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25248/
> ---
> 
> (Updated Sept. 2, 2014, 1:53 p.m.)
> 
> 
> Review request for cloudstack, Alena Prokharchyk, edison su, Darren Shepherd, 
> Sebastien Goasguen, and Hugo Trippaers.
> 
> 
> Bugs: CLOUDSTACK-6945
> https://issues.apache.org/jira/browse/CLOUDSTACK-6945
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fixes https://issues.apache.org/jira/browse/CLOUDSTACK-6945
> 
> 
> Diffs
> -
> 
>   engine/orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java 
> 2fd7a52 
> 
> Diff: https://reviews.apache.org/r/25248/diff/
> 
> 
> Testing
> ---
> 
> Builds cleanly, will throw resource not available exception when template 
> does not exist.
> 
> 
> Thanks,
> 
> Rohit Yadav
> 
>

Re: Review Request 25248: Fix NPE in case VM is started and its template does not exist anymore

[Sebastien Goasguen]

On Sep 4, 2014, at 4:36 PM, Nitin Mehta  wrote:

> 
> 
>> On Sept. 2, 2014, 7:01 p.m., Nitin Mehta wrote:
>>> engine/orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java, line 
>>> 814
>>> 
>>> 
>>>Checking for template==null masks the whole problem. 
>>>1. Such validations should have happenned in the deployvm api layer if 
>>> it comes from that api.
>>>2. If its coming from a startvm api its perfectly fine to have the 
>>> template removed since the volume already exists. 
>>>3. If you see how template is used below...if it has to 'create' a new 
>>> volume the template shouldnt be removed but again the validations should be 
>>> in api layer.
>> 
>> Rohit Yadav wrote:
>>So, I can read code too, upper layers are not passing the template so 
>> what do you propose? How may I fix this then?
>> 
>> Nitin Mehta wrote:
>>Firstly, check whether the issue is reproducible. Just realized that from 
>> 4.3 onwards templates have 'Inactive' state to mark it removed. Removed 
>> attribute should never be set so this exception shouldnt be hit . Check when 
>> is the removed flag set as it should be a bug(check CLOUDSTACK-5997 and 
>> backporting it already fixes that). 
>>Secondly, even if this bug doesnt exist, do a sanity check and see this 
>> kind of check is in the api which will ultimately call this method. Check if 
>> apis are missing them. But some apis might not need it like StartVm, 
>> Rebootvm where new volume is not created. Do write a util method which could 
>> be shared by all apis. I guess that should be good enough.
>> 
>> Rohit Yadav wrote:
>>This was for 4.3.1, I guess this is a special case and not a blocker. The 
>> issue was reproducible when say an admin removed a template where a user may 
>> be trying to create a VM and was in a wizard. I'm closing as we're not 
>> putting this for 4.3.1 release.
> 
> Please punt it for 4.5. We should fix it.
> 

Is this the same bug but with a fix ?

https://reviews.apache.org/r/25348/


> 
> - Nitin
> 
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25248/#review52059
> ---
> 
> 
> On Sept. 2, 2014, 1:53 p.m., Rohit Yadav wrote:
>> 
>> ---
>> This is an automatically generated e-mail. To reply, visit:
>> https://reviews.apache.org/r/25248/
>> ---
>> 
>> (Updated Sept. 2, 2014, 1:53 p.m.)
>> 
>> 
>> Review request for cloudstack, Alena Prokharchyk, edison su, Darren 
>> Shepherd, Sebastien Goasguen, and Hugo Trippaers.
>> 
>> 
>> Bugs: CLOUDSTACK-6945
>>https://issues.apache.org/jira/browse/CLOUDSTACK-6945
>> 
>> 
>> Repository: cloudstack-git
>> 
>> 
>> Description
>> ---
>> 
>> Fixes https://issues.apache.org/jira/browse/CLOUDSTACK-6945
>> 
>> 
>> Diffs
>> -
>> 
>>  engine/orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java 
>> 2fd7a52 
>> 
>> Diff: https://reviews.apache.org/r/25248/diff/
>> 
>> 
>> Testing
>> ---
>> 
>> Builds cleanly, will throw resource not available exception when template 
>> does not exist.
>> 
>> 
>> Thanks,
>> 
>> Rohit Yadav
>> 
>> 
> 

Re: Review Request 25248: Fix NPE in case VM is started and its template does not exist anymore

[Rohit Yadav]

On 04-Sep-2014, at 10:59 pm, Sebastien Goasguen  wrote:
> Is this the same bug but with a fix ?
>
> https://reviews.apache.org/r/25348/

This is some other (minor) issue:
https://reviews.apache.org/r/25248

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 #294

[jenkins]

See 

Re: [ACS431] Vote coming

[Rohit Yadav]

Hi Daan,

On 04-Sep-2014, at 10:28 pm, Daan Hoogland  wrote:
> Rohit, I see you added a path from 4.3.1 to 4.4.1 via 4.4.0. Is this going
> to work? It bypasses all schema - and data upgrades from 4.3.0 to 4.4.0.
> Where did these go?

There is no schema change from 4.3.0 to 4.3.1 which means we can reuse the 
upgrade path from 4.3.0 to 4.4.0. The upgrade path (java class) I added simply 
extends the Upgrade430to440 class.

I’ve pushed the branch rebased from 4.4 branch here: 
hotfix/4.4/upgradepath-431to441

On my system, I was able to upgrade from 4.3.1 to 4.4.1 by deploying db from 
4.3.1 candidate and start ACS on 4.4 branch (which upgrades db to 4.4.1). I 
think field testing would be helpful.

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: [ACS431] Help testing 4.3.1 vote candidate

[ilya musayev]

Ack, will be trying later tonight.

On 9/4/14, 1:22 PM, Rohit Yadav wrote:

Dear community,

Please help in testing 4.3.1 voting candidate that Sebastien has just shared 
today. 4.3.0 was a good release, this minor release tries to fix several issues 
but we need regression testing.

To get help from community folks who don’t want to build from source, I’ve 
built and put debs and rpm using the voting candidate 
(41c0eaa14d2f8cd5b58bca71f2254c2390cc6913).

For debian, put this in sources.list and install/upgrade:

deb http://packages.bhaisaab.org/cloudstack/main/debian ./

For centos/fedora/rhel, put this in a yum.repos.d/cloudstack.repo:

[apache-cloudstack]
name=Apache CloudStack
baseurl=http://packages.bhaisaab.org/cloudstack/main/centos/
enabled=1
gpgcheck=0

Feel free to use them, this location is temporary. This repo was created using:
http://cloudstack-installation.readthedocs.org/en/latest/building_from_source.html#building-deb-packages

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: [ACS431] Vote coming

[Daan Hoogland]

Ok, I seemed to recall there was a schema change but it must have been
blocked/reverted or something. I did not mail my previous ;)


On Thu, Sep 4, 2014 at 11:13 PM, Rohit Yadav 
wrote:

> Hi Daan,
>
> On 04-Sep-2014, at 10:28 pm, Daan Hoogland 
> wrote:
> > Rohit, I see you added a path from 4.3.1 to 4.4.1 via 4.4.0. Is this
> going
> > to work? It bypasses all schema - and data upgrades from 4.3.0 to 4.4.0.
> > Where did these go?
>
> There is no schema change from 4.3.0 to 4.3.1 which means we can reuse the
> upgrade path from 4.3.0 to 4.4.0. The upgrade path (java class) I added
> simply extends the Upgrade430to440 class.
>
> I’ve pushed the branch rebased from 4.4 branch here:
> hotfix/4.4/upgradepath-431to441
>
> On my system, I was able to upgrade from 4.3.1 to 4.4.1 by deploying db
> from 4.3.1 candidate and start ACS on 4.4 branch (which upgrades db to
> 4.4.1). I think field testing would be helpful.
>
> 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.
>



-- 
Daan

Re: [ACS431] Vote coming

[Rohit Yadav]

On 04-Sep-2014, at 11:15 pm, Daan Hoogland  wrote:
> Ok, I seemed to recall there was a schema change but it must have been
> blocked/reverted or something. I did not mail my previous ;)

Yes, I asked the community about a bug that required some database schema 
changes but since we decided not to do it I did not put that fix in 4.3; 
therefore now we have no schema changes between 4.3.0 and 4.3.1 (voting 
candidate).

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: hotfix/4.4/upgradepath-431to441: DB Upgrade path from 4.3.1 to 4.4.1

[Daan Hoogland]

merged


On Thu, Sep 4, 2014 at 7:08 PM, Rohit Yadav 
wrote:

> Hi Daan,
>
> Please check and pick commits from this branch, they add db upgrade path
> from 4.3.1 to 4.4.1;
> hotfix/4.4/upgradepath-431to441
>
> 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.
>



-- 
Daan

Re: hotfix/4.4/upgradepath-431to441: DB Upgrade path from 4.3.1 to 4.4.1

[Rohit Yadav]

On 04-Sep-2014, at 11:19 pm, Daan Hoogland  wrote:
> merged

Thanks!

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: [ACS431] Help testing 4.3.1 vote candidate

[Rohit Yadav]

FYI, the deb/rpm repo I shared hosts noredist/nonoss builds.

On 04-Sep-2014, at 11:14 pm, ilya musayev  wrote:
> Ack, will be trying later tonight.

Thanks Ilya. Please also test if you are able to download volumes on 4.3.0/ESX 
as well.

SystemVMs can be downloaded from: http://jenkins.buildacloud.org/view/4.3
They are failing for some issue now, you may use 4.3.0 or the last successful 
builds from the above link.

@Sebastien, @Hugo: can we do something about the failing systemvm builds?

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

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

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

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

Re: SSVM JAVA PROCESS NOT RUNNING, systemvm didn't get patched with the agent specific code

[Nitin Mehta]

For future reference do look at
https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM,+templates,+Sec
ondary+storage+troubleshooting
For ssvm related issues. This was covered by #9 in the wiki.
 
On 04/09/14 3:47 AM, "Punith S"  wrote:

>thanks Hugo, it's working now :)
>
>cheers!
>
>
>On Thu, Sep 4, 2014 at 3:32 PM, Hugo Trippaers  wrote:
>
>> Punith,
>>
>> You need to enable the systemvm flag in cloudstack to make sure a new
>> systemvm.iso is build.
>>
>> mvn -Dnoredist -Psystemvm clean install
>>
>>
>> Cheers,
>>
>> Hugo
>>
>> On 4 sep. 2014, at 11:27, Punith S  wrote:
>>
>> > hi,
>> >
>> > i have been working on building noredist of master for vmware,
>> >
>> > since i'm using mvn commands and jetty for deploying cloudstack
>> >
>> > i'm building the cloudstack using
>> > $ mvn clean
>> > $ mvn install -Dnoredist
>> >
>> > deploying using $ mvn -pl :cloud-client-ui jetty:run -Dnoredist
>> >
>> > also i'm seeding the SSVM template by using
>> > as the link suggests
>> >
>> 
>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+Cloud
>>Stack
>> >
>> > # mkdir -p /etc/cloudstack/management/
>> > # cp
>> 
>>./client/target/cloud-client-ui-4.5.0-SNAPSHOT/WEB-INF/classes/db.propert
>>ies
>> > /etc/cloudstack/management/
>> > #
>> >
>> 
>>./client/target/generated-webapp/WEB-INF/classes/scripts/storage/secondar
>>y/cloud-install-sys-tmplt
>> > -m /mnt/secondary -u http://
>> >
>> 
>>jenkins.buildacloud.org/view/master/job/build-systemvm-master/lastSuccess
>>fulBuild/artifact/tools/appliance/dist/systemvmtemplate-master-vmware.ova
>> > -h vmware -F
>> >
>> > when i deploy a vmware zone,everything come up fine but the systemvm's
>> > agent is not running!
>> >
>> > when i log into the ssvm,* i see 4.4.SNAPSHOT jars being patched in
>>the
>> > /use/local/cloud/ssvm*
>> >
>> > hence the java process is not running
>> > logs show
>> > 2014-09-04 09:20:24,760 INFO  [cloud.agent.AgentShell] (main:null)
>>Agent
>> > started
>> > 2014-09-04 09:20:24,764 INFO  [cloud.agent.AgentShell] (main:null)
>> > Implementation Version is 4.4.0-SNAPSHOT
>> > 2014-09-04 09:20:24,765 INFO  [cloud.agent.AgentShell] (main:null)
>> > agent.properties found at
>>/usr/local/cloud/systemvm/conf/agent.properties
>> > 2014-09-04 09:20:24,772 DEBUG [cloud.agent.AgentShell] (main:null)
>>Found
>> > property: instance
>> > 2014-09-04 09:20:24,774 DEBUG [cloud.agent.AgentShell] (main:null)
>>Found
>> > property: resource
>> > 2014-09-04 09:20:24,774 INFO  [cloud.agent.AgentShell] (main:null)
>> > Defaulting to using properties file for storage
>> > 2014-09-04 09:20:24,781 INFO  [cloud.agent.AgentShell] (main:null)
>> > Defaulting to the constant time backoff algorithm
>> > 2014-09-04 09:20:24,801 INFO  [cloud.utils.LogUtils] (main:null) log4j
>> > configuration found at /usr/local/cloud/systemvm/conf/log4j-cloud.xml
>> > 2014-09-04 09:20:24,825 DEBUG [cloud.agent.AgentShell] (main:null)
>> Checking
>> > to see if agent.SecStorage.pid exists.
>> > 2014-09-04 09:20:24,828 DEBUG [cloud.utils.ProcessUtil] (main:null)
>> > environment.properties could not be opened
>> > 2014-09-04 09:20:24,836 DEBUG [cloud.utils.ProcessUtil] (main:null)
>> > Executing: bash -c echo $PPID
>> > 2014-09-04 09:20:24,844 DEBUG [cloud.utils.ProcessUtil] (main:null)
>> > Execution is successful.
>> > *2014-09-04 09:20:24,853 ERROR [cloud.agent.AgentShell] (main:null)
>> Unable
>> > to start agent: Resource class not found:
>> > com.cloud.storage.resource.PremiumSecondaryStorageResource due to:
>> > java.lang.ClassNotFoundException:
>> > com.cloud.storage.resource.PremiumSecondaryStorageResource*
>> >
>> > i'm guessing there was no patch up between agent specific code !
>> > am i missing out something here ?
>> >
>> > thanks!
>> > --
>> > regards,
>> >
>> > punith s
>> > cloudbyte.com
>>
>>
>
>
>-- 
>regards,
>
>punith s
>cloudbyte.com

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

[jenkins]

See 

Re: [VOTE] Release Apache CloudStack 4.3.1

[Ian Duffy]

 In short +1

Did manual smoke style testing using the source against Xenserver 6.2 with
SP1 using the devcloud database.

- Automated configuration of a basic with marvin.
- Confirm system vms came up.
- Confirm the template auto downloads.
- Confirm booting an instance using the centos template.
- Confirm uploading a template from a http server.
- Confirm removing a template.
- Confirm booting from a instance using a password enabled template.
- Confirmed access a VM via the console proxy.
- Confirmed configuring LDAP against a the included embedded ApacheDS server
- Confirmed import multiple LDAP users and logging in as them.
- Confirmed password changes were not allowed when LDAP is enabled.
- Brought up an Instance and ran a web server. Configured security groups
accordingly and confirmed I could access it from another machine.


On 4 September 2014 16:07, sebgoa  wrote:

> 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: 41c0eaa14d2f8cd5b58bca71f2254c2390cc6913
>
> 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.
>
> 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)
>
>
>

Jenkins build is still unstable: simulator-singlerun #295

[jenkins]

See 

Jenkins build is still unstable: simulator-singlerun #296

[jenkins]

See 

Jenkins build is still unstable: simulator-singlerun #297

[jenkins]

See 

Re: [VOTE] Release Apache CloudStack 4.3.1

[ilya musayev]

I've been running acs 4.3.0+ patches for quite sometime in large scale 
environment with VmWare, but have not had a chance to try out this 
specific build. Looked at commits and dont see very major changes, but 
will try later today on smaller env or laptop build.


This is by far the most stable release, looks like I will be riding it 
for a while.


Regards
ilya
On 9/4/14, 8:07 AM, sebgoa wrote:

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: 41c0eaa14d2f8cd5b58bca71f2254c2390cc6913

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.

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)

Jenkins build is still unstable: simulator-singlerun #298

[jenkins]

See 

Jenkins build is still unstable: simulator-singlerun #299

[jenkins]

See 

Re: Add OS X 10.9 to the guest os type

[Amogh Vasekar]

Hi,

The guest OS mappings have been moved to DB, let me put up a wiki on how
to add new OS to ACS.

In your case, you would need something like the following:

INSERT IGNORE INTO `cloud`.`guest_os_hypervisor` (uuid,hypervisor_type,
hypervisor_version, guest_os_name, guest_os_id, created, is_user_defined)
VALUES (UUID(),'VMware', '5.0', 'darwin11Guest', 226, now(), 0);

This needs to be done for Vmware versions that support OS X 10.9 (5.1,
5.5?)
Also, please note that hypervisor = VMware and not VmWare all throughout
cloudstack.

HTH
Amogh

On 9/4/14 1:27 AM, "Mohamed Ali Saidi" 
wrote:

>Hi,
>
>I'm working on a CI platforme and I want to add OS x 10.9 to Cloudstack
>guest os type.
>
>I tried with adding these lines on db:
>
>INSERT INTO `cloud`.`guest_os` (id, uuid, category_id, display_name)
>VALUES
>(226, UUID(), 7, 'Apple Mac OS X 10.9 (32 bit)');
>INSERT INTO `cloud`.`guest_os` (id, uuid, category_id, display_name)
>VALUES
>(227, UUID(), 7, 'Apple Mac OS X 10.9 (64 bit)');
>
>INSERT INTO `cloud`.`guest_os_hypervisor` (hypervisor_type, guest_os_name,
>guest_os_id) VALUES ("VmWare", 'Apple Mac OS X 10.9 (32 bit)', 226);
>INSERT INTO `cloud`.`guest_os_hypervisor` (hypervisor_type, guest_os_name,
>guest_os_id) VALUES ("VmWare", 'Apple Mac OS X 10.9 (64 bit)', 227);
>
>And on VmwareGuestOsMapper.java:
>
>s_mapper.put("Apple Mac OS X 10.9 (32
>bit)",VirtualMachineGuestOsIdentifier.DARWIN_11_GUEST);
>   s_mapper.put("Apple Mac OS X 10.9 (64
>bit)",VirtualMachineGuestOsIdentifier.DARWIN_11_64_GUEST);
>
>
>but it didn't work.
>
>PS:On Vcenter i get  "Other(64 bit)" as vm os guest type.
>
>Thanks

[GitHub] cloudstack pull request: Fix CLOUDSTACK-7476: always pass along $J...

[karuturi]

Github user karuturi commented on the pull request:

https://github.com/apache/cloudstack/pull/15#issuecomment-54590261
  
If JAVA_HOME is not set, setJavaHome()(cloud-usage.rc:49)  method is trying 
to find it from default java available using something like 
`JAVA_HOME=$(dirname $(dirname $(readlink -e $(which java ` and exits if 
couldn't find anything.
wouldn't that work in this case?


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