Re: systemvm templates

[Abhinandan Prateek]

There are no issues with java 1.6.4x or higher. I checked the current
template it download version 1.6.0, I guess if we can fix that to get any
version equal to or higher than 1.6.4x then we are safe from the observed
venter session issues.

-abhi

On 21/01/14 12:55 pm, "Hugo Trippaers"  wrote:

>Abhi,
>
>The ticket you reference states that it works fine with java 1.6.4x or
>higher. Is that indeed the case? Then we don’t need to upgrade the java
>version. Also the same code is running in the management server, which
>also depends on java 1.6. Has anyone reported the same problems for the
>management server?
>
>I’m very much against running java 7 on the systemvm while java 6 is
>still being used for the cloudstack management server. If we upgrade, we
>should do both.
>
>Cheers,
>
>Hugo
>
>
>On 21 jan. 2014, at 07:54, Abhinandan Prateek
> wrote:
>
>> Hugo,
>> 
>>  I went and looked at several support tickets that were filed.
>> Filed this ticket: https://issues.apache.org/jira/browse/CLOUDSTACK-5914
>> summarising the issue.
>> There was a good amount of affect that went into troubleshooting this
>>and
>> finally nailing it to Java version.
>> 
>> Several test were done in various environments to nail it down. I was
>>not
>> able to find enough information to nail it to a particular java known
>> issues or get enough information to file a bug against java version
>>1.6.2.
>> Since, internally we are convinced that this is a serious issue we will
>>go
>> ahead with the fix, I will put the patch for review for ASF.
>> 
>> -abhi
>> 
>> 
>> 
>> On 18/01/14 12:45 pm, "Hugo Trippaers"  wrote:
>> 
>>> Hey Abhi,
>>> 
>>> Do you have more details on this? A stacktrace or error log would be
>>> great.
>>> 
>>> I would really need to see the details before we make a decision on
>>>this.
>>> 
>>> Cheers,
>>> 
>>> Hugo
>>> 
>>> Sent from my iPhone
>>> 
 On 17 jan. 2014, at 23:42, Abhinandan Prateek
  wrote:
 
 In SSVM for VMWare, copying template to primary storage fails in some
 cases with jre 6.
 
 -abhi
 
> On 18/01/14 1:08 am, "Alex Huang"  wrote:
> 
> Why is jre7 required for vmware?  Kelven, you have any idea?
> 
> --Alex
> 
>> -Original Message-
>> From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com]
>> Sent: Friday, January 17, 2014 9:08 AM
>> To: dev@cloudstack.apache.org
>> Subject: Re: systemvm templates
>> 
>> Hugo,
>> 
>> First of all my bad that I jumped the gun on jre7 change. I will be
>> testing the
>> full build on master and then update the urls and other changes.
>> In the current template jre7 package is not available by default,
>> needs
>> apt-
>> get update. jre7 is a absolute necessity for VMWare template.
>> 
>> Once I have a successful local build I will update the thread.
>> 
>> -abhi
>> 
>> 
>>> On 17/01/14 10:20 pm, "Hugo Trippaers"  wrote:
>>> 
>>> Abhi,
>>> 
>>> I have the debian 7.0.0 isis local on the jenkins server, so we
>>>don¹t
>>> depend on the external URLs.
>>> 
>>> Do you want to switch master to the new image? No trouble for me to
>>> make it happen.
>>> 
>>> Cheers,
>>> 
>>> Hugo
>>> 
>>> On 17 jan. 2014, at 17:12, Abhinandan Prateek
>>>  wrote:
>>> 
 
 While trying to build systemvm templates I noticed that the urls
to
 download the debian images are invalid as in definition.rb in
 respective
 folders:
 
 For 64 bit template
 
 
http://cdimage.debian.org/mirror/cdimage/archive/7.0.0/i386/iso-cd/
de
 b
 ian
 -7.0.0-i386-netinst.iso
 For 32 bit template
 
 
http://cdimage.debian.org/mirror/cdimage/archive/7.0.0/i386/iso-cd/
de
 b
 ian
 -7.0.0-i386-netinst.iso
 
 I will be updating these to following respectively, once I have a
 successful local build:
 
 
 
 
http://ftp.acc.umu.se/mirror/cdimage/release/7.3.0/i386/iso-cd/debi
an
 -
>> 7.3
 .0-i386-netinst.iso   MD5: 04c58f30744e64a0459caf7d7cace479
 
 
 
http://ftp.acc.umu.se/mirror/cdimage/release/7.3.0/ia64/iso-cd/debi
an
 -
 7.3 .0-ia64-netinst.iso  MD5: a6b93666a5393334accb7ac4ee28d949
 
 Not sure if jenkins job is building the right templates now ?
 
 -abhi
 
>> 
>

Re: VmWare SDK to vijava

[Hugo Trippaers]

Heya,

Does anyone know about the current status the legal discussions around 
including the WSDL or code generated by parsing the WSDL?

I would really like to have the vmware support in the normal build instead of 
just in the noredist build. It would probably boost adoption amongst people 
using vmware. I’m at a point where i’m about to just commit a change to use 
vijava so we can do it. I’d rather revert that change later when the legal 
issues are sorted then wait another release before we have vmware support in 
the normal build. We already missed the 4.3 release, let’s make sure its fixed 
in 4.4.


Cheers,

Hugo


On 4 okt. 2013, at 19:04, Darren Shepherd  wrote:

> I created https://issues.apache.org/jira/browse/LEGAL-180 for this.
> 
> Darren

Re: Review Request 16867: Test Suite for Testing Remote Access VPN on VPC

[Santhosh Edukulla]

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



test/integration/component/test_remotevpn_vpc.py


Move services class to config.cfg under config directory. Then use 
testclient getconfig object to get the configuration parsed as dictionary.



test/integration/component/test_remotevpn_vpc.py


Please use try except block for entire setUpClass and do clean up in case 
of any exception here? Otherwise we may miss to clean up few things in case of 
exception. Exit in case of exception and don't proceed further



test/integration/component/test_remotevpn_vpc.py


Append to list like we did for appending an account



test/integration/component/test_remotevpn_vpc.py


VirtualMachine class under base.py has services as second argument but we 
are passing services["virtual_machine"], why so?

Also, inside the create method, we are using account details as well passed 
from services class. Can we check this?



test/integration/component/test_remotevpn_vpc.py


Use common way of using services class. Here we are referring using class 
name, below we referred using services class. Use one way.



test/integration/component/test_remotevpn_vpc.py


Why assign port and protocol values here? We could see its already 
available under services class?



test/integration/component/test_remotevpn_vpc.py


Remove prints and use log methods provided



test/integration/component/test_remotevpn_vpc.py


Please add some comments, otherwise code looks little cluttered and not 
clear to understand. Organize them as functional units if possible. 



test/integration/component/test_remotevpn_vpc.py


Are we creating same account with similar parameters twice, once 
firstaccount and then secondaccount here?



test/integration/component/test_remotevpn_vpc.py


add try except block and exit the test run in case of exception



test/integration/component/test_remotevpn_vpc.py


Do we need this rpm? Can we have allthese packages available as part of 
test client already? Dont we want to exit in case these steps fail? If we need 
this rpm can we have these packages available already rather than downloading 
every time? TC may take more time right?



test/integration/component/test_remotevpn_vpc.py


move these calls in to a function call with proper arguments, rather the 
code looks repetitive?



test/integration/component/test_remotevpn_vpc.py


We can move this required files to a marvin lib/config directory with your 
module name and use the scripts\conf from there? This will make code look 
neater. As well, we are not sure open with w+ may fail in case the file already 
exists?



test/integration/component/test_remotevpn_vpc.py


is %d right here?



test/integration/component/test_remotevpn_vpc.py


why some static methods and few class methods?



test/integration/component/test_remotevpn_vpc.py


move these scripts as ready and hands on scripts rather than writing inside 
of test code and make sure that all paths are used in common rather 
open(file,"mode") use open( relative_path + file_name,"mode")



test/integration/component/test_remotevpn_vpc.py


what is this l?



test/integration/component/test_remotevpn_vpc.py


Please move this to a new file and separate it from this test module?



test/integration/component/test_remotevpn_vpc.py


Can we move this script outside of this test module and checkin as a 
separate script, it will then be available under marvin path for use?



test/integration/component/test_remotevpn_vpc.py


how does first argument to shell script is interpreted as start function? 
or stop function?



test/integration/component/test_remotevpn_vpc.py


Please move this to library utils\common



te

Apply patches to master

[sebgoa]

All,

Hugo and I are having a chat on IRC about patches.

As we are fixing bugs to 4.3 prior to the release, it's important to apply the 
patch to master.
Apply to master and cherry-pick to 4.3
Otherwise we will see the bug again in 4.4.

Trivial, but a reminder never hurts.

-Sebastien

Re: Apply patches to master

[Wei ZHOU]

Make sense.
It is recommended to use "git cherry-pick -x".


2014/1/21 sebgoa 

> All,
>
> Hugo and I are having a chat on IRC about patches.
>
> As we are fixing bugs to 4.3 prior to the release, it's important to apply
> the patch to master.
> Apply to master and cherry-pick to 4.3
> Otherwise we will see the bug again in 4.4.
>
> Trivial, but a reminder never hurts.
>
> -Sebastien

Re: Review Request 16867: Test Suite for Testing Remote Access VPN on VPC

[Santhosh Edukulla]

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



test/integration/component/test_remotevpn_vpc.py


Not clearly understood this line of socket.setdefa...? What is the purpose 
of this? There are no explicit socket calls opened?


- Santhosh Edukulla


On Jan. 16, 2014, 7:12 p.m., Chandan Purushothama wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/16867/
> ---
> 
> (Updated Jan. 16, 2014, 7:12 p.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar, SrikanteswaraRao Talluri, 
> and Sheng Yang.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Test Suite for Testing Remote Access VPN on VPC. 
> 
> I successfully automated the following components:
> 
> 1.VPN Client Installation on Linux
> 2.Component that efficiently verifies Remote VPN Access between client and 
> the Server.
> 3.Developed a component that automates VPN Client Configuration and services.
> 4.Test Cases of the Feature
> 5.Tested the Code multiple times on XenServer and fixed the bugs.
> 6.Requirement on VMWare: Default Template should be CentOS 5.5 or higher for 
> the test suite to work. VPN Client cannot be installed on CentOS 5.3 Default 
> Template on VMWare.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_remotevpn_vpc.py PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/16867/diff/
> 
> 
> Testing
> ---
> 
> Test case no : Enable VPN for Public IP Address on the VPC ... ok
> Test case no : Remote a VPN User ... ok
> Test case no : Add a Different VPN User and Test Access with already existing 
> VPN User ... ok
> Test case no : Add a Previously Removed VPN User from the VPC and Test the 
> VPN Connectivity ... ok
> Test case no : Disable the VPN Service on the VPC ... ok
> Test case no : Enabled Previously Dsiabled VPN Access to VPC. ... ok
> Test case no : Create Nine VPN Users to test the remote.vpn.user.limit=8 
> Configuration parameter ... ok
> 
> --
> Ran 7 tests in 645.787s
> 
> OK
> 
> 
> File Attachments
> 
> 
> 0001-Test-Suite-for-Remote-Access-VPN-on-VPC.patch
>   
> https://reviews.apache.org/media/uploaded/files/2014/01/14/c6d3f593-d0eb-407c-aad2-574ebf9ca0f8__0001-Test-Suite-for-Remote-Access-VPN-on-VPC.patch
> 
> 
> Thanks,
> 
> Chandan Purushothama
> 
>

UI Issues

[Alex Hitchins]

I can't see thorough my mail what the resolution was regards to the new UI CSS.

What was the resolution?

Regards,

Alex Hitchins
VP Software Engineering

[cid:image001.png@01CDA880.0BBDC9C0]

S: +44 20 3603 0540 | M: +44 07788 423 969
www.shapeblue.com | 
Twitter:@ShapeBlue

Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure 
Support offers the 
best 24/7 SLA for CloudStack Environments.

Apache CloudStack Bootcamp training courses

**NEW!** CloudStack 4.2 training
08/09 January 2014, London
13-17 January 2014, GLOBAL. Instructor led, 
On-line
20-24 January 2014, GLOBAL. Instructor led, 
On-line

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 is a registered trademark.

4.3 Automated Regression test results - KVM (CentOS 6.3)

[Srikanteswararao Talluri]

As snapshots on KVM are not supported, snapshot related tests(~35) are failing. 
Rest of the test failures are related to ssh timeout issues. I don’t see any 
product bug among the failures.

http://jenkins.buildacloud.org/job/test-regression-matrix


Test Run: #284 and #287



Total:453

Fail :66

Skip :26




name   passfailskip

test_security_groups/ 1   0   0

test_multiple_ip_ranges/  1   0   0

test_vm_passwdenabled/1   0   0

test_project_configs/ 2   0   3

test_project_usage/   8   1   0

test_volumes/ 9   0   0

test_snapshot_limits/ 0   1   0

test_templates/   2   2   0

test_eip_elb/ 1   0   0

test_project_limits/  7   1   0

test_usage/   8   1   0

test_stopped_vm/ 15   2   0

test_vpc_routers/ 8   2   0

test_affinity_groups/41   0   1

test_routers/ 5   1   0

test_storage_motion/  0   0   2

test_egress_rules/1   0   0

test_blocker_bugs/4   3   0

test_vpc_network/17   1   9

test_vpc_vms_deployment/  6   1   0

test_network_offering/3   0   0

test_vpc/19   1   0

test_egress_fw_rules/21   1   4

test_haproxy/11   0   0

test_allocation_states/   6   0   0

test_assign_vm/  13   4   0

test_vpc_network_lbrules/15   0   0

test_redundant_router_cleanups/   3   0   0

test_update_vm/   1   0   0

test_vpn_users/   7   0   0

test_reset_ssh_keypair/   9   1   0

test_implicit_planner/0   0   1

test_vpc_offerings/   8   0   0

test_redundant_router_services/   1   0   0

test_recurring_snapshots/ 0   2   0

test_project_resources/   6   1   0

test_regions/ 3   0   0

test_snapshot_gc/ 0   1   0

test_vpc_vm_life_cycle/  19  14   0

test_redundant_router_upgrades/   2   0   0

test_explicit_dedication/ 0   0   1

test_snapshots/   0   7   0

test_projects/   10   0   0

test_vpc_network_staticnatrule/   2   4   0

test_accounts/   13   1   0

test_advancedsg_networks/ 1   0   0

test_ip_reservation/  4   0   0

test_tags/   18   1   1

test_shared_networks/12   0   1

test_vpc_network_pfrules/ 2   8   0

test_custom_hostname/ 3   0   3

test_resource_limits/ 9   2   0

test_regions_accounts/3   0   0



Thanks,
~Talluri

xentools on systemvmtemplate not visible to xen

[Abhinandan Prateek]

The xentools are installed on systemvm templates but still xenserver is unable 
to recognise those.
There was discussion on this sometime back and it did not get concluded.
If someone knows the steps to make the xentoosl visible to xen, please chime in.
It may be that we just need to start the daemon process that informs xen of the 
tools ?

-abhi

Re: Review Request 16867: Test Suite for Testing Remote Access VPN on VPC

[Santhosh Edukulla]

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



test/integration/component/test_remotevpn_vpc.py


This is not added to clean up?


- Santhosh Edukulla


On Jan. 16, 2014, 7:12 p.m., Chandan Purushothama wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/16867/
> ---
> 
> (Updated Jan. 16, 2014, 7:12 p.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar, SrikanteswaraRao Talluri, 
> and Sheng Yang.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Test Suite for Testing Remote Access VPN on VPC. 
> 
> I successfully automated the following components:
> 
> 1.VPN Client Installation on Linux
> 2.Component that efficiently verifies Remote VPN Access between client and 
> the Server.
> 3.Developed a component that automates VPN Client Configuration and services.
> 4.Test Cases of the Feature
> 5.Tested the Code multiple times on XenServer and fixed the bugs.
> 6.Requirement on VMWare: Default Template should be CentOS 5.5 or higher for 
> the test suite to work. VPN Client cannot be installed on CentOS 5.3 Default 
> Template on VMWare.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_remotevpn_vpc.py PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/16867/diff/
> 
> 
> Testing
> ---
> 
> Test case no : Enable VPN for Public IP Address on the VPC ... ok
> Test case no : Remote a VPN User ... ok
> Test case no : Add a Different VPN User and Test Access with already existing 
> VPN User ... ok
> Test case no : Add a Previously Removed VPN User from the VPC and Test the 
> VPN Connectivity ... ok
> Test case no : Disable the VPN Service on the VPC ... ok
> Test case no : Enabled Previously Dsiabled VPN Access to VPC. ... ok
> Test case no : Create Nine VPN Users to test the remote.vpn.user.limit=8 
> Configuration parameter ... ok
> 
> --
> Ran 7 tests in 645.787s
> 
> OK
> 
> 
> File Attachments
> 
> 
> 0001-Test-Suite-for-Remote-Access-VPN-on-VPC.patch
>   
> https://reviews.apache.org/media/uploaded/files/2014/01/14/c6d3f593-d0eb-407c-aad2-574ebf9ca0f8__0001-Test-Suite-for-Remote-Access-VPN-on-VPC.patch
> 
> 
> Thanks,
> 
> Chandan Purushothama
> 
>

Review Request 17142: CLOUDSTACK-5916: associateIpAddress" leaves an IP in allocating state

[Saksham Srivastava]

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

Review request for cloudstack and Murali Reddy.


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


Repository: cloudstack-git


Description
---

associateIpAddress leaves an IP in allocating state (user_ip_address table), 
although the API command is executed on incorrectly.

Steps to repro :
1) create a vpc tier.
2) Execute associateIpAddress" API on the vpc tier but do not specify the vpc 
id.
#cloudmonkey
>>associate ipaddress networkid=09ffc45f-beba-4690-8be7-425891915d44
Async job ea020246-d0e8-4e58-ac84-fccb55c3b646 failed
Error 530, Can't assign ip to the network directly when network belongs to 
VPC.Specify vpcId to associate ip address to VPC
accountid = a6ba35b3-7e76-11e3-8490-7614eba325e6
cmd = org.apache.cloudstack.api.command.user.address.AssociateIPAddrCmd
created = 2014-01-21T10:46:46+0530
jobid = ea020246-d0e8-4e58-ac84-fccb55c3b646
jobprocstatus = 0
jobresult:
errorcode = 530
errortext = Can't assign ip to the network directly when network belongs to 
VPC.Specify vpcId to associate ip address to VPC
jobresultcode = 530
jobresulttype = object
jobstatus = 2
userid = a6ba5844-7e76-11e3-8490-7614eba325e6

Expected behavior:
There should be no allocation of IP .

Actual behaviour:
The public IP remains in 'Allocating' state

The fix releases the IP incase of exception.


Diffs
-

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

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


Testing
---

Tested the following scenarios:
:8096/client/api?command=associateIpAddress&networkid=09ffc45f-beba-4690-8be7-425891915d44
There is no allocation of public IP (no IP is put in Allocating state in the 
db).
 
:8096/client/api?command=associateIpAddress&networkid=09ffc45f-beba-4690-8be7-425891915d44&vpcid=1
Successfully associates the IP.

Build passes successfully.
Patch applies cleanly.


Thanks,

Saksham Srivastava

Re: 4.3 Automated Regression test results - KVM (CentOS 6.3)

[sebgoa]

Talluri,

Is there a difference between:

http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-regression-matrix/

and

http://jenkins.buildacloud.org/view/cloudstack-qa-4.3/job/test-regression-matrix/

they have the same jobid…seems to be the same jobs ?

On Jan 21, 2014, at 12:12 PM, Srikanteswararao Talluri 
 wrote:

> As snapshots on KVM are not supported, snapshot related tests(~35) are 
> failing. Rest of the test failures are related to ssh timeout issues. I don’t 
> see any product bug among the failures.
> 
> http://jenkins.buildacloud.org/job/test-regression-matrix
> 
> 
> Test Run: #284 and #287
> 
> 
> 
> Total:453
> 
> Fail :66
> 
> Skip :26
> 
> 
> 
> 
> name   passfailskip
> 
> test_security_groups/ 1   0   0
> 
> test_multiple_ip_ranges/  1   0   0
> 
> test_vm_passwdenabled/1   0   0
> 
> test_project_configs/ 2   0   3
> 
> test_project_usage/   8   1   0
> 
> test_volumes/ 9   0   0
> 
> test_snapshot_limits/ 0   1   0
> 
> test_templates/   2   2   0
> 
> test_eip_elb/ 1   0   0
> 
> test_project_limits/  7   1   0
> 
> test_usage/   8   1   0
> 
> test_stopped_vm/ 15   2   0
> 
> test_vpc_routers/ 8   2   0
> 
> test_affinity_groups/41   0   1
> 
> test_routers/ 5   1   0
> 
> test_storage_motion/  0   0   2
> 
> test_egress_rules/1   0   0
> 
> test_blocker_bugs/4   3   0
> 
> test_vpc_network/17   1   9
> 
> test_vpc_vms_deployment/  6   1   0
> 
> test_network_offering/3   0   0
> 
> test_vpc/19   1   0
> 
> test_egress_fw_rules/21   1   4
> 
> test_haproxy/11   0   0
> 
> test_allocation_states/   6   0   0
> 
> test_assign_vm/  13   4   0
> 
> test_vpc_network_lbrules/15   0   0
> 
> test_redundant_router_cleanups/   3   0   0
> 
> test_update_vm/   1   0   0
> 
> test_vpn_users/   7   0   0
> 
> test_reset_ssh_keypair/   9   1   0
> 
> test_implicit_planner/0   0   1
> 
> test_vpc_offerings/   8   0   0
> 
> test_redundant_router_services/   1   0   0
> 
> test_recurring_snapshots/ 0   2   0
> 
> test_project_resources/   6   1   0
> 
> test_regions/ 3   0   0
> 
> test_snapshot_gc/ 0   1   0
> 
> test_vpc_vm_life_cycle/  19  14   0
> 
> test_redundant_router_upgrades/   2   0   0
> 
> test_explicit_dedication/ 0   0   1
> 
> test_snapshots/   0   7   0
> 
> test_projects/   10   0   0
> 
> test_vpc_network_staticnatrule/   2   4   0
> 
> test_accounts/   13   1   0
> 
> test_advancedsg_networks/ 1   0   0
> 
> test_ip_reservation/  4   0   0
> 
> test_tags/   18   1   1
> 
> test_shared_networks/12   0   1
> 
> test_vpc_network_pfrules/ 2   8   0
> 
> test_custom_hostname/ 3   0   3
> 
> test_resource_limits/ 9   2   0
> 
> test_regions_accounts/3   0   0
> 
> 
> 
> Thanks,
> ~Talluri
> 

Re: 4.3 Automated Regression test results - KVM (CentOS 6.3)

[Srikanteswararao Talluri]

Yes sebastiean, they both contain  same jobs  but in a different view
which is not very useful (I realised it after I created one). We can
remove the view cloudstack-qa-4.3.
I¹ll go ahead and remove it.

I have fixed all the infra issues that we were facing in test jobs and now
I have scheduled test-matrix-extended(which is a comprehensive job
containing all the test jobs) to run every 8 hours and
disabled 'test-matrix¹ job which is a subset of test-matrix-extended.

I¹ll come up with some more enhancements to the existing test jobs like
addition of basic zone, zone with external devices. Will send out a mail
with what I intend to do shortly and seek suggestions
from the community.

Thanks,
~Talluri

On 21/01/14 5:20 pm, "sebgoa"  wrote:

>Talluri,
>
>Is there a difference between:
>
>http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-regression-matr
>ix/
>
>and
>
>http://jenkins.buildacloud.org/view/cloudstack-qa-4.3/job/test-regression-
>matrix/
>
>they have the same jobidŠseems to be the same jobs ?
>
>On Jan 21, 2014, at 12:12 PM, Srikanteswararao Talluri
> wrote:
>
>> As snapshots on KVM are not supported, snapshot related tests(~35) are
>>failing. Rest of the test failures are related to ssh timeout issues. I
>>don¹t see any product bug among the failures.
>> 
>> http://jenkins.buildacloud.org/job/test-regression-matrix
>> 
>> 
>> Test Run: #284 and #287
>> 
>> 
>> 
>> Total:453
>> 
>> Fail :66
>> 
>> Skip :26
>> 
>> 
>> 
>> 
>> name   passfailskip
>> 
>> test_security_groups/ 1   0   0
>> 
>> test_multiple_ip_ranges/  1   0   0
>> 
>> test_vm_passwdenabled/1   0   0
>> 
>> test_project_configs/ 2   0   3
>> 
>> test_project_usage/   8   1   0
>> 
>> test_volumes/ 9   0   0
>> 
>> test_snapshot_limits/ 0   1   0
>> 
>> test_templates/   2   2   0
>> 
>> test_eip_elb/ 1   0   0
>> 
>> test_project_limits/  7   1   0
>> 
>> test_usage/   8   1   0
>> 
>> test_stopped_vm/ 15   2   0
>> 
>> test_vpc_routers/ 8   2   0
>> 
>> test_affinity_groups/41   0   1
>> 
>> test_routers/ 5   1   0
>> 
>> test_storage_motion/  0   0   2
>> 
>> test_egress_rules/1   0   0
>> 
>> test_blocker_bugs/4   3   0
>> 
>> test_vpc_network/17   1   9
>> 
>> test_vpc_vms_deployment/  6   1   0
>> 
>> test_network_offering/3   0   0
>> 
>> test_vpc/19   1   0
>> 
>> test_egress_fw_rules/21   1   4
>> 
>> test_haproxy/11   0   0
>> 
>> test_allocation_states/   6   0   0
>> 
>> test_assign_vm/  13   4   0
>> 
>> test_vpc_network_lbrules/15   0   0
>> 
>> test_redundant_router_cleanups/   3   0   0
>> 
>> test_update_vm/   1   0   0
>> 
>> test_vpn_users/   7   0   0
>> 
>> test_reset_ssh_keypair/   9   1   0
>> 
>> test_implicit_planner/0   0   1
>> 
>> test_vpc_offerings/   8   0   0
>> 
>> test_redundant_router_services/   1   0   0
>> 
>> test_recurring_snapshots/ 0   2   0
>> 
>> test_project_resources/   6   1   0
>> 
>> test_regions/ 3   0   0
>> 
>> test_snapshot_gc/ 0   1   0
>> 
>> test_vpc_vm_life_cycle/  19  14   0
>> 
>> test_redundant_router_upgrades/   2   0   0
>> 
>> test_explicit_dedication/ 0   0   1
>> 
>> test_snapshots/   0   7   0
>> 
>> test_projects/   10   0   0
>> 
>> test_vpc_network_staticnatrule/   2   4   0
>> 
>> test_accounts/   13   1   0
>> 
>> test_advancedsg_networks/ 1   0   0
>> 
>> test_ip_reservation/  4   0   0
>> 
>> test_tags/   18   1   1
>> 
>> test_shared_networks/12   0   1
>> 
>> test_vpc_network_pfrules/ 2   8   0
>> 
>> test_custom_hostname/ 3   0   3
>> 
>> test_resource_limits/ 9   2   0
>> 
>> test_regions_accounts/3   0   0
>> 
>> 
>> 
>> Thanks,
>> ~Talluri
>> 
>

Re: 4.3 Automated Regression test results - KVM (CentOS 6.3)

[sebgoa]

On Jan 21, 2014, at 1:18 PM, Srikanteswararao Talluri 
 wrote:

> Yes sebastiean, they both contain  same jobs  but in a different view
> which is not very useful (I realised it after I created one). We can
> remove the view cloudstack-qa-4.3.
> I¹ll go ahead and remove it.

then we need different jobs in each view…

IMHO we need running integration tests for master, and we need integration 
tests for specific releases.

I would not delete the view, I would just make sure that there are different 
test-* jobs for master and for 4.3.

> 
> I have fixed all the infra issues that we were facing in test jobs and now
> I have scheduled test-matrix-extended(which is a comprehensive job
> containing all the test jobs) to run every 8 hours and
> disabled 'test-matrix¹ job which is a subset of test-matrix-extended.
> 
> I¹ll come up with some more enhancements to the existing test jobs like
> addition of basic zone, zone with external devices. Will send out a mail
> with what I intend to do shortly and seek suggestions
> from the community.
> 
> Thanks,
> ~Talluri
> 
> On 21/01/14 5:20 pm, "sebgoa"  wrote:
> 
>> Talluri,
>> 
>> Is there a difference between:
>> 
>> http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-regression-matr
>> ix/
>> 
>> and
>> 
>> http://jenkins.buildacloud.org/view/cloudstack-qa-4.3/job/test-regression-
>> matrix/
>> 
>> they have the same jobidŠseems to be the same jobs ?
>> 
>> On Jan 21, 2014, at 12:12 PM, Srikanteswararao Talluri
>>  wrote:
>> 
>>> As snapshots on KVM are not supported, snapshot related tests(~35) are
>>> failing. Rest of the test failures are related to ssh timeout issues. I
>>> don¹t see any product bug among the failures.
>>> 
>>> http://jenkins.buildacloud.org/job/test-regression-matrix
>>> 
>>> 
>>> Test Run: #284 and #287
>>> 
>>> 
>>> 
>>> Total:453
>>> 
>>> Fail :66
>>> 
>>> Skip :26
>>> 
>>> 
>>> 
>>> 
>>> name   passfailskip
>>> 
>>> test_security_groups/ 1   0   0
>>> 
>>> test_multiple_ip_ranges/  1   0   0
>>> 
>>> test_vm_passwdenabled/1   0   0
>>> 
>>> test_project_configs/ 2   0   3
>>> 
>>> test_project_usage/   8   1   0
>>> 
>>> test_volumes/ 9   0   0
>>> 
>>> test_snapshot_limits/ 0   1   0
>>> 
>>> test_templates/   2   2   0
>>> 
>>> test_eip_elb/ 1   0   0
>>> 
>>> test_project_limits/  7   1   0
>>> 
>>> test_usage/   8   1   0
>>> 
>>> test_stopped_vm/ 15   2   0
>>> 
>>> test_vpc_routers/ 8   2   0
>>> 
>>> test_affinity_groups/41   0   1
>>> 
>>> test_routers/ 5   1   0
>>> 
>>> test_storage_motion/  0   0   2
>>> 
>>> test_egress_rules/1   0   0
>>> 
>>> test_blocker_bugs/4   3   0
>>> 
>>> test_vpc_network/17   1   9
>>> 
>>> test_vpc_vms_deployment/  6   1   0
>>> 
>>> test_network_offering/3   0   0
>>> 
>>> test_vpc/19   1   0
>>> 
>>> test_egress_fw_rules/21   1   4
>>> 
>>> test_haproxy/11   0   0
>>> 
>>> test_allocation_states/   6   0   0
>>> 
>>> test_assign_vm/  13   4   0
>>> 
>>> test_vpc_network_lbrules/15   0   0
>>> 
>>> test_redundant_router_cleanups/   3   0   0
>>> 
>>> test_update_vm/   1   0   0
>>> 
>>> test_vpn_users/   7   0   0
>>> 
>>> test_reset_ssh_keypair/   9   1   0
>>> 
>>> test_implicit_planner/0   0   1
>>> 
>>> test_vpc_offerings/   8   0   0
>>> 
>>> test_redundant_router_services/   1   0   0
>>> 
>>> test_recurring_snapshots/ 0   2   0
>>> 
>>> test_project_resources/   6   1   0
>>> 
>>> test_regions/ 3   0   0
>>> 
>>> test_snapshot_gc/ 0   1   0
>>> 
>>> test_vpc_vm_life_cycle/  19  14   0
>>> 
>>> test_redundant_router_upgrades/   2   0   0
>>> 
>>> test_explicit_dedication/ 0   0   1
>>> 
>>> test_snapshots/   0   7   0
>>> 
>>> test_projects/   10   0   0
>>> 
>>> test_vpc_network_staticnatrule/   2   4   0
>>> 
>>> test_accounts/   13   1   0
>>> 
>>> test_advancedsg_networks/ 1   0   0
>>> 
>>> test_ip_reservation/  

Re: 4.3 Automated Regression test results - KVM (CentOS 6.3)

[Srikanteswararao Talluri]

On 21/01/14 6:00 pm, "sebgoa"  wrote:

>
>On Jan 21, 2014, at 1:18 PM, Srikanteswararao Talluri
> wrote:
>
>> Yes sebastiean, they both contain  same jobs  but in a different view
>> which is not very useful (I realised it after I created one). We can
>> remove the view cloudstack-qa-4.3.
>> I¹ll go ahead and remove it.
>
>then we need different jobs in each view…
>
>IMHO we need running integration tests for master, and we need
>integration tests for specific releases.
>
>I would not delete the view, I would just make sure that there are
>different test-* jobs for master and for 4.3.

In this case, we need to replicate test jobs for different releases.

>
>> 
>> I have fixed all the infra issues that we were facing in test jobs and
>>now
>> I have scheduled test-matrix-extended(which is a comprehensive job
>> containing all the test jobs) to run every 8 hours and
>> disabled 'test-matrix¹ job which is a subset of test-matrix-extended.
>> 
>> I¹ll come up with some more enhancements to the existing test jobs like
>> addition of basic zone, zone with external devices. Will send out a mail
>> with what I intend to do shortly and seek suggestions
>> from the community.
>> 
>> Thanks,
>> ~Talluri
>> 
>> On 21/01/14 5:20 pm, "sebgoa"  wrote:
>> 
>>> Talluri,
>>> 
>>> Is there a difference between:
>>> 
>>> 
>>>http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-regression-ma
>>>tr
>>> ix/
>>> 
>>> and
>>> 
>>> 
>>>http://jenkins.buildacloud.org/view/cloudstack-qa-4.3/job/test-regressio
>>>n-
>>> matrix/
>>> 
>>> they have the same jobidŠseems to be the same jobs ?
>>> 
>>> On Jan 21, 2014, at 12:12 PM, Srikanteswararao Talluri
>>>  wrote:
>>> 
 As snapshots on KVM are not supported, snapshot related tests(~35) are
 failing. Rest of the test failures are related to ssh timeout issues.
I
 don¹t see any product bug among the failures.
 
 http://jenkins.buildacloud.org/job/test-regression-matrix
 
 
 Test Run: #284 and #287
 
 
 
 Total:453
 
 Fail :66
 
 Skip :26
 
 
 
 
 name   passfailskip
 
 test_security_groups/ 1   0   0
 
 test_multiple_ip_ranges/  1   0   0
 
 test_vm_passwdenabled/1   0   0
 
 test_project_configs/ 2   0   3
 
 test_project_usage/   8   1   0
 
 test_volumes/ 9   0   0
 
 test_snapshot_limits/ 0   1   0
 
 test_templates/   2   2   0
 
 test_eip_elb/ 1   0   0
 
 test_project_limits/  7   1   0
 
 test_usage/   8   1   0
 
 test_stopped_vm/ 15   2   0
 
 test_vpc_routers/ 8   2   0
 
 test_affinity_groups/41   0   1
 
 test_routers/ 5   1   0
 
 test_storage_motion/  0   0   2
 
 test_egress_rules/1   0   0
 
 test_blocker_bugs/4   3   0
 
 test_vpc_network/17   1   9
 
 test_vpc_vms_deployment/  6   1   0
 
 test_network_offering/3   0   0
 
 test_vpc/19   1   0
 
 test_egress_fw_rules/21   1   4
 
 test_haproxy/11   0   0
 
 test_allocation_states/   6   0   0
 
 test_assign_vm/  13   4   0
 
 test_vpc_network_lbrules/15   0   0
 
 test_redundant_router_cleanups/   3   0   0
 
 test_update_vm/   1   0   0
 
 test_vpn_users/   7   0   0
 
 test_reset_ssh_keypair/   9   1   0
 
 test_implicit_planner/0   0   1
 
 test_vpc_offerings/   8   0   0
 
 test_redundant_router_services/   1   0   0
 
 test_recurring_snapshots/ 0   2   0
 
 test_project_resources/   6   1   0
 
 test_regions/ 3   0   0
 
 test_snapshot_gc/ 0   1   0
 
 test_vpc_vm_life_cycle/  19  14   0
 
 test_redundant_router_upgrades/   2   0   0
 
 test_explicit_dedication/ 0   0   1
 
 test_snapshots/   0   7   0
 
 test_p

Re: 4.3 Automated Regression test results - KVM (CentOS 6.3)

[sebgoa]

On Jan 21, 2014, at 1:37 PM, Srikanteswararao Talluri 
 wrote:

> 
> 
> On 21/01/14 6:00 pm, "sebgoa"  wrote:
> 
>> 
>> On Jan 21, 2014, at 1:18 PM, Srikanteswararao Talluri
>>  wrote:
>> 
>>> Yes sebastiean, they both contain  same jobs  but in a different view
>>> which is not very useful (I realised it after I created one). We can
>>> remove the view cloudstack-qa-4.3.
>>> I¹ll go ahead and remove it.
>> 
>> then we need different jobs in each view…
>> 
>> IMHO we need running integration tests for master, and we need
>> integration tests for specific releases.
>> 
>> I would not delete the view, I would just make sure that there are
>> different test-* jobs for master and for 4.3.
> 
> In this case, we need to replicate test jobs for different releases.

at least on master and the major release being worked on.

> 
>> 
>>> 
>>> I have fixed all the infra issues that we were facing in test jobs and
>>> now
>>> I have scheduled test-matrix-extended(which is a comprehensive job
>>> containing all the test jobs) to run every 8 hours and
>>> disabled 'test-matrix¹ job which is a subset of test-matrix-extended.
>>> 
>>> I¹ll come up with some more enhancements to the existing test jobs like
>>> addition of basic zone, zone with external devices. Will send out a mail
>>> with what I intend to do shortly and seek suggestions
>>> from the community.
>>> 
>>> Thanks,
>>> ~Talluri
>>> 
>>> On 21/01/14 5:20 pm, "sebgoa"  wrote:
>>> 
 Talluri,
 
 Is there a difference between:
 
 
 http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-regression-ma
 tr
 ix/
 
 and
 
 
 http://jenkins.buildacloud.org/view/cloudstack-qa-4.3/job/test-regressio
 n-
 matrix/
 
 they have the same jobidŠseems to be the same jobs ?
 
 On Jan 21, 2014, at 12:12 PM, Srikanteswararao Talluri
  wrote:
 
> As snapshots on KVM are not supported, snapshot related tests(~35) are
> failing. Rest of the test failures are related to ssh timeout issues.
> I
> don¹t see any product bug among the failures.
> 
> http://jenkins.buildacloud.org/job/test-regression-matrix
> 
> 
> Test Run: #284 and #287
> 
> 
> 
> Total:453
> 
> Fail :66
> 
> Skip :26
> 
> 
> 
> 
> name   passfailskip
> 
> test_security_groups/ 1   0   0
> 
> test_multiple_ip_ranges/  1   0   0
> 
> test_vm_passwdenabled/1   0   0
> 
> test_project_configs/ 2   0   3
> 
> test_project_usage/   8   1   0
> 
> test_volumes/ 9   0   0
> 
> test_snapshot_limits/ 0   1   0
> 
> test_templates/   2   2   0
> 
> test_eip_elb/ 1   0   0
> 
> test_project_limits/  7   1   0
> 
> test_usage/   8   1   0
> 
> test_stopped_vm/ 15   2   0
> 
> test_vpc_routers/ 8   2   0
> 
> test_affinity_groups/41   0   1
> 
> test_routers/ 5   1   0
> 
> test_storage_motion/  0   0   2
> 
> test_egress_rules/1   0   0
> 
> test_blocker_bugs/4   3   0
> 
> test_vpc_network/17   1   9
> 
> test_vpc_vms_deployment/  6   1   0
> 
> test_network_offering/3   0   0
> 
> test_vpc/19   1   0
> 
> test_egress_fw_rules/21   1   4
> 
> test_haproxy/11   0   0
> 
> test_allocation_states/   6   0   0
> 
> test_assign_vm/  13   4   0
> 
> test_vpc_network_lbrules/15   0   0
> 
> test_redundant_router_cleanups/   3   0   0
> 
> test_update_vm/   1   0   0
> 
> test_vpn_users/   7   0   0
> 
> test_reset_ssh_keypair/   9   1   0
> 
> test_implicit_planner/0   0   1
> 
> test_vpc_offerings/   8   0   0
> 
> test_redundant_router_services/   1   0   0
> 
> test_recurring_snapshots/ 0   2   0
> 
> test_project_resources/   6   1   0
> 
> test_regions/ 3   0   0
> 
> test_snapshot_gc/ 

Re: 4.3 Automated Regression test results - KVM (CentOS 6.3)

[Prasanna Santhanam]

On Tue, Jan 21, 2014 at 01:39:14PM +0100, sebgoa wrote:
> >> 
> >> IMHO we need running integration tests for master, and we need
> >> integration tests for specific releases.
> >> 
> >> I would not delete the view, I would just make sure that there are
> >> different test-* jobs for master and for 4.3.
> > 
> > In this case, we need to replicate test jobs for different releases.
> 
> at least on master and the major release being worked on.
> 

views make for good separation during major releases, but since the
infra is reused we won't/shouldn't be running the same jobs in more
than one view.

ideally, get 1 view to always run on master and create ephemeral views
during release phases makes sense.


Powered by BigRock.com

Re: VXLAN problems

[Nux!]

On 21.01.2014 05:25, Toshiaki Hatano wrote:

Hi Nux, Marcus,

It's FYI: There's compiled vxlan document in Jenkins.
http://jenkins.buildacloud.org/job/build-docs-vxlan-master/


Bookmarked, thanks!

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Re: xentools on systemvmtemplate not visible to xen

[Hugo Trippaers]

Hey Abhi,

i don’t think the xentools are installed. At least they are not in the 
postinstall.sh

Cheers,
Hugo


On 21 jan. 2014, at 12:27, Abhinandan Prateek  
wrote:

> The xentools are installed on systemvm templates but still xenserver is 
> unable to recognise those.
> There was discussion on this sometime back and it did not get concluded.
> If someone knows the steps to make the xentoosl visible to xen, please chime 
> in.
> It may be that we just need to start the daemon process that informs xen of 
> the tools ?
> 
> -abhi

Adding KVM host fails

[Gaurav Aradhye]

Hello,

I configured a new KVM host on top of Ubuntu (12.04.4) following everything
on [1]. I am facing two issues.

1) When I updated network interfaces with following and rebooted the host,
the original static IP of the host got changed and I had to remove this
change.

# Public network
auto cloudbr0
iface cloudbr0 inet manual
bridge_ports eth0.200
bridge_fd 5
bridge_stp off
bridge_maxwait 1

# Private network
auto cloudbr1
iface cloudbr1 inet manual
bridge_ports eth0.300
bridge_fd 5
bridge_stp off
bridge_maxwait 1


2) While trying to add the host to Cloudstack, operation fails with
"Unable to add the host" and the management server log says:


2014-01-21 15:26:31,582 DEBUG [kvm.discoverer.LibvirtServerDiscoverer]
(catalina-exec-17:null) Timeout, to wait for the host connecting to
mgt svr, assuming it is failed
2014-01-21 15:26:31,583 WARN  [cloud.resource.ResourceManagerImpl]
(catalina-exec-17:null) Unable to find the server resources at
http://192.168.100.210
2014-01-21 15:26:31,584 INFO  [utils.exception.CSExceptionErrorCode]
(catalina-exec-17:null) Could not find exception:
com.cloud.exception.DiscoveryException in error code list for
exceptions
2014-01-21 15:26:31,584 WARN  [admin.host.AddHostCmd]
(catalina-exec-17:null) Exception:
com.cloud.exception.DiscoveryException: Unable to add the host
at 
com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:798)
at 
com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:590)
at 
org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372)
at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305)
at com.cloud.api.ApiServlet.doPost(ApiServlet.java:71)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at 
org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
at 
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)

at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2014-01-21 15:26:31,585 INFO  [cloud.api.ApiServer] (catalina-exec-17:null)
Unable to add the host
2014-01-21 15:26:31,589 DEBUG [cloud.api.ApiServlet]
(catalina-exec-17:null) ===END===  192.168.100.41 -- POST
 command=addHost&response=json&sessionkey=4yR04FYeisMdiNFElfJD%2FezU%2FRE%3D
2014-01-21 15:26:47,341 DEBUG
[storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 2
is not ready to launch secondary storage VM yet
2014-01-21 15:26:47,762 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage
UPintenance mode
2014-01-21 15:26:55,397 DEBUG
[cloud.network.ExternalDeviceUsageManagerImpl]
(ExternalNetworkMonitor-1:null) External devices stats collector is
running...
2014-01-21 15:26:55,436 INFO  [cloud.ha.HighAvailabilityManagerImpl]
(HA-3:null) checking health of usage server
2014-01-21 15:26:55,438 DEBUG [cloud.ha.HighAvailabilityManagerImpl]
(HA-3:null) usage server running? false, heartbeat: null
2014-01-21 15:26:55,438 WARN  [apache.cloudstack.alerts] (HA-3:null)
 alertType:: 13 // dataCenterId:: 0 // podId:: 0 // clusterId:: null //
message:: No usage server process running


Can someone give me some specific checkpoints to look exactly what is going
wrong and which server resource I am missing?

The qemu/kvm, libvirt versions are well above required.

I have 4.2.1 setup.

1.
https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.2/html/Installation_Guide/hypervisor-kvm-install-flow.html

Regards,
Gaurav

[ANNOUNCE] New PMC Member: Giles Sirett

[Chip Childers]

The Project Management Committee (PMC) for Apache CloudStack has asked
Giles Sirett to join the PMC and we are pleased to announce that he
has accepted.

Join me in congratulating Giles!

-The CloudStack PMC

Re: VmWare SDK to vijava

[Chip Childers]

I bet we never got an answer. Frankly, I'd like to see us use
something where the licensing is clear.  That, or we don't include the
WSDL in our repo / distro.

On Tue, Jan 21, 2014 at 3:40 AM, Hugo Trippaers  wrote:
> Heya,
>
> Does anyone know about the current status the legal discussions around 
> including the WSDL or code generated by parsing the WSDL?
>
> I would really like to have the vmware support in the normal build instead of 
> just in the noredist build. It would probably boost adoption amongst people 
> using vmware. I’m at a point where i’m about to just commit a change to use 
> vijava so we can do it. I’d rather revert that change later when the legal 
> issues are sorted then wait another release before we have vmware support in 
> the normal build. We already missed the 4.3 release, let’s make sure its 
> fixed in 4.4.
>
>
> Cheers,
>
> Hugo
>
>
> On 4 okt. 2013, at 19:04, Darren Shepherd  wrote:
>
>> I created https://issues.apache.org/jira/browse/LEGAL-180 for this.
>>
>> Darren
>

Re: Adding KVM host fails

[Marty Sweet]

Hi,

What's the current contents of your /etc/network/interfaces file?

Thanks,
Marty

On Tuesday, January 21, 2014, Gaurav Aradhye 
wrote:

> Hello,
>
> I configured a new KVM host on top of Ubuntu (12.04.4) following everything
> on [1]. I am facing two issues.
>
> 1) When I updated network interfaces with following and rebooted the host,
> the original static IP of the host got changed and I had to remove this
> change.
>
> # Public network
> auto cloudbr0
> iface cloudbr0 inet manual
> bridge_ports eth0.200
> bridge_fd 5
> bridge_stp off
> bridge_maxwait 1
>
> # Private network
> auto cloudbr1
> iface cloudbr1 inet manual
> bridge_ports eth0.300
> bridge_fd 5
> bridge_stp off
> bridge_maxwait 1
>
>
> 2) While trying to add the host to Cloudstack, operation fails with
> "Unable to add the host" and the management server log says:
>
>
> 2014-01-21 15:26:31,582 DEBUG [kvm.discoverer.LibvirtServerDiscoverer]
> (catalina-exec-17:null) Timeout, to wait for the host connecting to
> mgt svr, assuming it is failed
> 2014-01-21 15:26:31,583 WARN  [cloud.resource.ResourceManagerImpl]
> (catalina-exec-17:null) Unable to find the server resources at
> http://192.168.100.210
> 2014-01-21 15:26:31,584 INFO  [utils.exception.CSExceptionErrorCode]
> (catalina-exec-17:null) Could not find exception:
> com.cloud.exception.DiscoveryException in error code list for
> exceptions
> 2014-01-21 15:26:31,584 WARN  [admin.host.AddHostCmd]
> (catalina-exec-17:null) Exception:
> com.cloud.exception.DiscoveryException: Unable to add the host
> at
> com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:798)
> at
> com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:590)
> at
> org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514)
> at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372)
> at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305)
> at com.cloud.api.ApiServlet.doPost(ApiServlet.java:71)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at
> org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
> at
> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
>
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2014-01-21 15:26:31,585 INFO  [cloud.api.ApiServer] (catalina-exec-17:null)
> Unable to add the host
> 2014-01-21 15:26:31,589 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-17:null) ===END===  192.168.100.41 -- POST
>
>  command=addHost&response=json&sessionkey=4yR04FYeisMdiNFElfJD%2FezU%2FRE%3D
> 2014-01-21 15:26:47,341 DEBUG
> [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 2
> is not ready to launch secondary storage VM yet
> 2014-01-21 15:26:47,762 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
> (consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage
> UPintenance mode
> 2014-01-21 15:26:55,397 DEBUG
> [cloud.network.ExternalDeviceUsageManagerImpl]
> (ExternalNetworkMonitor-1:null) External devices stats collector is
> running...
> 2014-01-21 15:26:55,436 INFO  [cloud.ha.HighAvailabilityManagerImpl]
> (HA-3:null) checking health of usage server
> 2014-01-21 15:26:55,438 DEBUG [cloud.ha.HighAvailabilityManagerImpl]
> (HA-3:null) usage server running? false, heartbeat: null
> 2014-01-21 15:26:55,438 WARN  [apache.cloudstack.alerts] (HA-3:null)
>  alertType:: 13 // dataCenterId:: 0 // podId:: 0 // clusterId:: null //
> message:: No usage server process running
>
>
> Can someone give me some specific checkpoints to l

RE: [ANNOUNCE] New PMC Member: Giles Sirett

[Paul Angus]

Congratulations Mr Sirett!  (sir, m'lord, your majesty)

Regards,

Paul Angus
Cloud Architect
S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus
paul.an...@shapeblue.com

-Original Message-
From: Chip Childers [mailto:chipchild...@apache.org]
Sent: 21 January 2014 14:45
To: dev@cloudstack.apache.org
Subject: [ANNOUNCE] New PMC Member: Giles Sirett

The Project Management Committee (PMC) for Apache CloudStack has asked Giles 
Sirett to join the PMC and we are pleased to announce that he has accepted.

Join me in congratulating Giles!

-The CloudStack PMC
Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure 
Support offers the 
best 24/7 SLA for CloudStack Environments.

Apache CloudStack Bootcamp training courses

**NEW!** CloudStack 4.2 training
08/09 January 2014, London
13-17 January 2014, GLOBAL. Instructor led, 
On-line
20-24 January 2014, GLOBAL. Instructor led, 
On-line

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 is a registered trademark.

Re: [ANNOUNCE] New PMC Member: Giles Sirett

[sebgoa]

congrats Giles, well deserved

On Jan 21, 2014, at 3:52 PM, Paul Angus  wrote:

> Congratulations Mr Sirett!  (sir, m'lord, your majesty)
> 
> Regards,
> 
> Paul Angus
> Cloud Architect
> S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus
> paul.an...@shapeblue.com
> 
> -Original Message-
> From: Chip Childers [mailto:chipchild...@apache.org]
> Sent: 21 January 2014 14:45
> To: dev@cloudstack.apache.org
> Subject: [ANNOUNCE] New PMC Member: Giles Sirett
> 
> The Project Management Committee (PMC) for Apache CloudStack has asked Giles 
> Sirett to join the PMC and we are pleased to announce that he has accepted.
> 
> Join me in congratulating Giles!
> 
> -The CloudStack PMC
> Need Enterprise Grade Support for Apache CloudStack?
> Our CloudStack Infrastructure 
> Support offers the 
> best 24/7 SLA for CloudStack Environments.
> 
> Apache CloudStack Bootcamp training courses
> 
> **NEW!** CloudStack 4.2 training
> 08/09 January 2014, London
> 13-17 January 2014, GLOBAL. Instructor led, 
> On-line
> 20-24 January 2014, GLOBAL. Instructor led, 
> On-line
> 
> 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 is a registered 
> trademark.

RE: [ANNOUNCE] New PMC Member: Giles Sirett

[Giles Sirett]

Thanks all - looking forward to continuing to help this project however I can


Kind Regards
Giles

D: +44 20 3603 0541 | M: +44 796 111 2055
giles.sir...@shapeblue.com




-Original Message-
From: sebgoa [mailto:run...@gmail.com]
Sent: 21 January 2014 14:57
To: dev@cloudstack.apache.org
Subject: Re: [ANNOUNCE] New PMC Member: Giles Sirett

congrats Giles, well deserved

On Jan 21, 2014, at 3:52 PM, Paul Angus  wrote:

> Congratulations Mr Sirett!  (sir, m'lord, your majesty)
>
> Regards,
>
> Paul Angus
> Cloud Architect
> S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus
> paul.an...@shapeblue.com
>
> -Original Message-
> From: Chip Childers [mailto:chipchild...@apache.org]
> Sent: 21 January 2014 14:45
> To: dev@cloudstack.apache.org
> Subject: [ANNOUNCE] New PMC Member: Giles Sirett
>
> The Project Management Committee (PMC) for Apache CloudStack has asked Giles 
> Sirett to join the PMC and we are pleased to announce that he has accepted.
>
> Join me in congratulating Giles!
>
> -The CloudStack PMC
> Need Enterprise Grade Support for Apache CloudStack?
> Our CloudStack Infrastructure 
> Support offers the 
> best 24/7 SLA for CloudStack Environments.
>
> Apache CloudStack Bootcamp training courses
>
> **NEW!** CloudStack 4.2
> training
> 08/09 January 2014, London
> 13-17 January 2014, GLOBAL. Instructor led,
> On-line
> 20-24 January 2014, GLOBAL. Instructor led,
> On-line
>
> 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 is a registered 
> trademark.

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 is a registered trademark.

Re: [ANNOUNCE] New PMC Member: Giles Sirett

[Daan Hoogland]

go get'm Giles,
euh i mean welcome dear sir.

On Tue, Jan 21, 2014 at 3:56 PM, sebgoa  wrote:
> congrats Giles, well deserved
>
> On Jan 21, 2014, at 3:52 PM, Paul Angus  wrote:
>
>> Congratulations Mr Sirett!  (sir, m'lord, your majesty)
>>
>> Regards,
>>
>> Paul Angus
>> Cloud Architect
>> S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus
>> paul.an...@shapeblue.com
>>
>> -Original Message-
>> From: Chip Childers [mailto:chipchild...@apache.org]
>> Sent: 21 January 2014 14:45
>> To: dev@cloudstack.apache.org
>> Subject: [ANNOUNCE] New PMC Member: Giles Sirett
>>
>> The Project Management Committee (PMC) for Apache CloudStack has asked Giles 
>> Sirett to join the PMC and we are pleased to announce that he has accepted.
>>
>> Join me in congratulating Giles!
>>
>> -The CloudStack PMC
>> Need Enterprise Grade Support for Apache CloudStack?
>> Our CloudStack Infrastructure 
>> Support offers the 
>> best 24/7 SLA for CloudStack Environments.
>>
>> Apache CloudStack Bootcamp training courses
>>
>> **NEW!** CloudStack 4.2 training
>> 08/09 January 2014, London
>> 13-17 January 2014, GLOBAL. Instructor led, 
>> On-line
>> 20-24 January 2014, GLOBAL. Instructor led, 
>> On-line
>>
>> 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 is a registered 
>> trademark.
>

Re: VmWare SDK to vijava

[David Nalley]

On Tue, Jan 21, 2014 at 9:46 AM, Chip Childers  wrote:
> I bet we never got an answer. Frankly, I'd like to see us use
> something where the licensing is clear.  That, or we don't include the
> WSDL in our repo / distro.
>

Additionally, we are an open source project that is in the business of
producing open source software. Depending on non-free and
non-opensource libraries is suboptimal, but its worse when there is a
open source alternative.

--David

Re: 4.3 Regression automation result - Xen 6.2

[Daan Hoogland]

On Tue, Jan 21, 2014 at 6:43 AM, Rayees Namathponnan
 wrote:
> Total  : 444
> Failed :  28
> Skip:  22
>
> Most the failures are due to timeout error
>
> Regards,


Rayees, one litle query. Are those timeout issues intermittend over
runs? Meaning do different tests fail each run? Do you have data on
that? If so I think we can ignore them but if not we have a problem.
We then cannot assess how serious they are. Any thoughts?

Daan

Re: [ANNOUNCE] New PMC Member: Giles Sirett

[Wido den Hollander]

Congrats Giles! Great to have you onboard!

Wido

On 01/21/2014 03:45 PM, Chip Childers wrote:

The Project Management Committee (PMC) for Apache CloudStack has asked
Giles Sirett to join the PMC and we are pleased to announce that he
has accepted.

Join me in congratulating Giles!

-The CloudStack PMC

Re: 4.3 Regression automation result - Xen 6.2

[Rayees Namathponnan]

Timeout failures are intermediate, If we re-run these test individually
test gets pass.

I observed similar issues in previous run also, in my analysis I didn¹t
see any product failures with this run.

Regards,
Rayees


On 1/21/14 7:28 AM, "Daan Hoogland"  wrote:

>On Tue, Jan 21, 2014 at 6:43 AM, Rayees Namathponnan
> wrote:
>> Total  : 444
>> Failed :  28
>> Skip:  22
>>
>> Most the failures are due to timeout error
>>
>> Regards,
>
>
>Rayees, one litle query. Are those timeout issues intermittend over
>runs? Meaning do different tests fail each run? Do you have data on
>that? If so I think we can ignore them but if not we have a problem.
>We then cannot assess how serious they are. Any thoughts?
>
>Daan

Re: 4.3 Regression automation result - Xen 6.2

[Daan Hoogland]

Thanks Rayees, great!!!

On Tue, Jan 21, 2014 at 4:51 PM, Rayees Namathponnan
 wrote:
> Timeout failures are intermediate, If we re-run these test individually
> test gets pass.
>
> I observed similar issues in previous run also, in my analysis I didn¹t
> see any product failures with this run.
>
> Regards,
> Rayees
>
>
> On 1/21/14 7:28 AM, "Daan Hoogland"  wrote:
>
>>On Tue, Jan 21, 2014 at 6:43 AM, Rayees Namathponnan
>> wrote:
>>> Total  : 444
>>> Failed :  28
>>> Skip:  22
>>>
>>> Most the failures are due to timeout error
>>>
>>> Regards,
>>
>>
>>Rayees, one litle query. Are those timeout issues intermittend over
>>runs? Meaning do different tests fail each run? Do you have data on
>>that? If so I think we can ignore them but if not we have a problem.
>>We then cannot assess how serious they are. Any thoughts?
>>
>>Daan
>

Re: Apply patches to master

[Animesh Chaturvedi]

Actually git cherry-pick -x -s if someone else cherry picks it will include 
their sign off

Thanks
Animesh

On Jan 21, 2014, at 2:28 AM, "Wei ZHOU"  wrote:

> Make sense.
> It is recommended to use "git cherry-pick -x".
> 
> 
> 2014/1/21 sebgoa 
> 
>> All,
>> 
>> Hugo and I are having a chat on IRC about patches.
>> 
>> As we are fixing bugs to 4.3 prior to the release, it's important to apply
>> the patch to master.
>> Apply to master and cherry-pick to 4.3
>> Otherwise we will see the bug again in 4.4.
>> 
>> Trivial, but a reminder never hurts.
>> 
>> -Sebastien

Re: VmWare SDK to vijava

[Kelven Yang]

Hugo,

I think we seems to come to a census that to use WSDL to generate the java
stub which is pretty much compatible to what we have right now.

Kelven 

On 1/21/14, 12:40 AM, "Hugo Trippaers"  wrote:

>Heya,
>
>Does anyone know about the current status the legal discussions around
>including the WSDL or code generated by parsing the WSDL?
>
>I would really like to have the vmware support in the normal build
>instead of just in the noredist build. It would probably boost adoption
>amongst people using vmware. I¹m at a point where i¹m about to just
>commit a change to use vijava so we can do it. I¹d rather revert that
>change later when the legal issues are sorted then wait another release
>before we have vmware support in the normal build. We already missed the
>4.3 release, let¹s make sure its fixed in 4.4.
>
>
>Cheers,
>
>Hugo
>
>
>On 4 okt. 2013, at 19:04, Darren Shepherd 
>wrote:
>
>> I created https://issues.apache.org/jira/browse/LEGAL-180 for this.
>> 
>> Darren
>

Re: VmWare SDK to vijava

[Chiradeep Vittal]

Suboptimal for?
Wouldn't the ACS user want the best / supported client libraries?
Alternatively, can't we just compile the WSDL and check in the generated
sources? Not check-in the WSDL, but the client sources.

On 1/21/14 7:18 AM, "David Nalley"  wrote:

>On Tue, Jan 21, 2014 at 9:46 AM, Chip Childers 
>wrote:
>> I bet we never got an answer. Frankly, I'd like to see us use
>> something where the licensing is clear.  That, or we don't include the
>> WSDL in our repo / distro.
>>
>
>Additionally, we are an open source project that is in the business of
>producing open source software. Depending on non-free and
>non-opensource libraries is suboptimal, but its worse when there is a
>open source alternative.
>
>--David

Blacklists for passwords

[Demetrius Tsitrelis]

CloudStack does not enforce complexity rules for user passwords even in its 
built-in user database. For some accounts in particular, such as the root 
domain admin, it would seem a good idea to have some minimum requirements.  
Empty passwords, for example, should not be allowed. What do you think about 
having a blacklist of
unacceptable passwords (e.g., “password”, “admin”, etc.) for the rood domain 
admin?

  

DHCP entry fails to apply on the latest master

[Alena Prokharchyk]

I’ve deployed the latest master code, re-deployed the DB and uploaded new 
system templates with 4.3 version. After that, UserVm fails to start because 
DHCP entry fails to apply on the VR.
Its a xen host deployment, and I’ve tested that ssh to the VR works just fine. 
Sheng, can you please take a look? It happened on a couple of setups.

-Alena.

Re: DHCP entry fails to apply on the latest master

[Nitin Mehta]

I also face this issue. Here is the snippet of logs. Please let me know if
you need any other info.

2014-01-21 10:52:46,909 INFO  [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-1:ctx-57a7ba8c ctx-933fbba1) Unable to contact resource.
com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1]
is unreachable: Unable to apply dhcp entry on router
at 
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(Virt
ualNetworkApplianceManagerImpl.java:3826)
at 
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEntry(
VirtualNetworkApplianceManagerImpl.java:2956)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3
9)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
l.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)






On 21/01/14 11:01 AM, "Alena Prokharchyk" 
wrote:

>I¹ve deployed the latest master code, re-deployed the DB and uploaded new
>system templates with 4.3 version. After that, UserVm fails to start
>because DHCP entry fails to apply on the VR.
>Its a xen host deployment, and I¹ve tested that ssh to the VR works just
>fine. Sheng, can you please take a look? It happened on a couple of
>setups.
>
>-Alena.

Re: DHCP entry fails to apply on the latest master

[Sheng Yang]

The systemvm iso changed. You need to rebuild system iso, clean up the tags
on xen host(assume), then the new iso would be copied to Xen host after you
reboot the mgmt server.

Check /opt/xensource/packages/iso/systemvm.iso ensure it's updated.

--Sheng


On Tue, Jan 21, 2014 at 11:09 AM, Nitin Mehta wrote:

> I also face this issue. Here is the snippet of logs. Please let me know if
> you need any other info.
>
> 2014-01-21 10:52:46,909 INFO  [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-1:ctx-57a7ba8c ctx-933fbba1) Unable to contact resource.
> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1]
> is unreachable: Unable to apply dhcp entry on router
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(Virt
> ualNetworkApplianceManagerImpl.java:3826)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEntry(
> VirtualNetworkApplianceManagerImpl.java:2956)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3
> 9)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
> l.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
>
>
>
>
>
>
> On 21/01/14 11:01 AM, "Alena Prokharchyk" 
> wrote:
>
> >I¹ve deployed the latest master code, re-deployed the DB and uploaded new
> >system templates with 4.3 version. After that, UserVm fails to start
> >because DHCP entry fails to apply on the VR.
> >Its a xen host deployment, and I¹ve tested that ssh to the VR works just
> >fine. Sheng, can you please take a look? It happened on a couple of
> >setups.
> >
> >-Alena.
>
>

Re: DHCP entry fails to apply on the latest master

[Alena Prokharchyk]

To fix it, you should cleanup the tags on your xen host, so the MS will
copy the newest ISO there.

Sheng, thank you for helping to debug it.

-Alena.

On 1/21/14, 11:09 AM, "Nitin Mehta"  wrote:

>I also face this issue. Here is the snippet of logs. Please let me know if
>you need any other info.
>
>2014-01-21 10:52:46,909 INFO  [c.c.v.VirtualMachineManagerImpl]
>(Job-Executor-1:ctx-57a7ba8c ctx-933fbba1) Unable to contact resource.
>com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1]
>is unreachable: Unable to apply dhcp entry on router
>at 
>com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(Vir
>t
>ualNetworkApplianceManagerImpl.java:3826)
>at 
>com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEntry
>(
>VirtualNetworkApplianceManagerImpl.java:2956)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at 
>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
>3
>9)
>at 
>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
>p
>l.java:25)
>at java.lang.reflect.Method.invoke(Method.java:597)
>
>
>
>
>
>
>On 21/01/14 11:01 AM, "Alena Prokharchyk" 
>wrote:
>
>>I¹ve deployed the latest master code, re-deployed the DB and uploaded new
>>system templates with 4.3 version. After that, UserVm fails to start
>>because DHCP entry fails to apply on the VR.
>>Its a xen host deployment, and I¹ve tested that ssh to the VR works just
>>fine. Sheng, can you please take a look? It happened on a couple of
>>setups.
>>
>>-Alena.
>

Re: Review Request 17124: CLOUDSTACK-5884 make getTargetSwitch(NicTO nicTo) do all the work to select switch name, type and vlan token. Change preference to use the tags set on the physical network.

[ASF Subversion and Git Services]

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


Commit d4e069ecc8708ca37785a82fa8c6442d47363974 in branch refs/heads/master 
from Sheng Yang
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d4e069e ]

Fix noredist build issue

Introduced by:

commit ac65f8fddf182534a2dbea81c7e155b80e7c98ea
Author: Hugo Trippaers 
Date:   Mon Jan 20 18:03:02 2014 +0100

CLOUDSTACK-5884 make getTargetSwitch(NicTO nicTo) do all the work to select
switch name, type and vlan token. Change preference to use the tags set on the
physical network.


- ASF Subversion and Git Services


On Jan. 20, 2014, 5:14 p.m., Hugo Trippaers wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/17124/
> ---
> 
> (Updated Jan. 20, 2014, 5:14 p.m.)
> 
> 
> Review request for cloudstack and Animesh Chaturvedi.
> 
> 
> Bugs: CLOUDSTACK-5884
> https://issues.apache.org/jira/browse/CLOUDSTACK-5884
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-5884 make getTargetSwitch(NicTO nicTo) do all the work to select 
> switch name, type and vlan token. Change preference to use the tags set on 
> the physical network.
> 
> Based on commit ac65f8fddf182534a2dbea81c7e155b80e7c98ea in master
> 
> 
> Diffs
> -
> 
>   
> plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java
>  e47fd9e 
>   vmware-base/src/com/cloud/hypervisor/vmware/mo/HypervisorHostHelper.java 
> 3ba27d0 
> 
> Diff: https://reviews.apache.org/r/17124/diff/
> 
> 
> Testing
> ---
> 
> Created Vmware zone from scratch
>  Two physical networks, both with guest traffic type
>network 1, using VLAN isolation and vSwitch0
>network 2, using STT isolation and integration-dvSwitch
> 
> Check working ssvm
> Check working cvm
> 
> Create network offering with tag for network 1, deploy instance, test 
> connectivity
> Create network offering with tag for network 2, deploy instance, test 
> connectivity
> 
> 
> Thanks,
> 
> Hugo Trippaers
> 
>

Review Request 16973: Contrail Event Interceptor fix

[Suresh Balineni]

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

Review request for cloudstack.


Repository: cloudstack-git


Description
---

When project/domains are created,  our plugin code won't get invoked. Our 
contrail plugin uses Event infrastructure provided by cloudstack to receive 
these events and handle them accordingly. It is must to create domains/projects 
before creating a virtual network/vm object in contrail implementation. Hence 
our plugin must need a way to get notified about project/domain events.


Diffs
-

  
plugins/network-elements/juniper-contrail/resources/META-INF/cloudstack/system/spring-contrail-system-context-inheritable.xml
 PRE-CREATION 
  
plugins/network-elements/juniper-contrail/src/org/apache/cloudstack/network/contrail/management/EventUtils.java
 dd18ca6 

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


Testing
---


Thanks,

Suresh Balineni

Re: xentools on systemvmtemplate not visible to xen

[Chiradeep Vittal]

I was under the impression that they actually get in the way of live
migration and XS upgrades because then XS gets to be finicky about
supported OS and such.

On 1/21/14 5:56 AM, "Hugo Trippaers"  wrote:

>Hey Abhi,
>
>i don¹t think the xentools are installed. At least they are not in the
>postinstall.sh
>
>Cheers,
>Hugo
>
>
>On 21 jan. 2014, at 12:27, Abhinandan Prateek
> wrote:
>
>> The xentools are installed on systemvm templates but still xenserver is
>>unable to recognise those.
>> There was discussion on this sometime back and it did not get concluded.
>> If someone knows the steps to make the xentoosl visible to xen, please
>>chime in.
>> It may be that we just need to start the daemon process that informs
>>xen of the tools ?
>> 
>> -abhi
>

Re: Devcloud update for 4.3

[Prabhakaran Ganesan]

Second TryŠ

Adding some more context here. When the SSVM starts up, it says it is
downloading cents 5.3 (which doesn't require HVM), as shown in logs below.

INFO  [o.a.c.s.i.TemplateServiceImpl]
(AgentConnectTaskPool-1:ctx-a82352c8) Downloading template centos53-x86_64
to image store nfs://192.168.56.10/opt/storage/secondary

But when I try to boot the tinylinux template, I get eh HVM_REQUIRED
error. Also, when I look at the template details in the UI, it shows up as
Centos 5.6 (which I understand requires HVM). Any idea what's happening
here?
 


On 1/16/14 3:47 PM, "Prabhakaran Ganesan"  wrote:

>I also get the following error when I try to launch an instance the
>tinylinux template. This time I was trying with NFS-based primary storage
>and uselocalstorage = false. I did not get this error earlier. The
>tinylinux template settings indicate that it is Centos 5.6 x86_64.
>
>INFO  [o.a.c.f.j.i.AsyncJobMonitor] (Job-Executor-1:ctx-35100a3e) Add
>job-24 into job monitoring
>WARN  [c.c.h.x.r.CitrixResourceBase] (DirectAgent-14:ctx-e494228b) Task
>failed! Task record: uuid:
>a752017f-94a3-0682-28aa-62235059c010
>   nameLabel: Async.VM.start_on
> nameDescription:
>   allowedOperations: []
>   currentOperations: {}
> created: Thu Jan 16 07:42:55 PST 2014
>finished: Thu Jan 16 07:42:55 PST 2014
>  status: failure
>  residentOn: com.xensource.xenapi.Host@3ba61fa8
>progress: 1.0
>type: 
>  result:
>   errorInfo: [VM_HVM_REQUIRED,
>OpaqueRef:93f3b6fa-27c1-4fe5-2185-3c724e087ae6]
> otherConfig: {}
>   subtaskOf: com.xensource.xenapi.Task@aaf13f6f
>subtasks: []
>
>Thanks
>Prabhakaran
>
>
>
>On 1/16/14 1:20 PM, "Prabhakaran Ganesan"  wrote:
>
>>All the while, I was using my own NFS based secondary storage and I Was
>>downloading the systemvm templates from jenkins. I made the secondary
>>storage point to 192.168.56.10:/opt/storage/secondary (I used the maven
>>deploySvr script to configure the whole thing). I edited the 'host'
>>parameter in GlobalSettings and restarted the management server. 'Host'
>>addition failed once, but the host got added after I rebooted the
>>DevCloud
>>VM. The system VMs came up and I found that the tiny linux template got
>>downloaded. It also shows up when I try to launch an instance.
>>
>>When I launch the tiny linux instance, I run into the following error.
>>The
>>router VM got started properly, but the linux instance didn't. It is
>>complaining about some storage issues. Any idea what is happening here?
>>
>>Thanks
>>Prabhakar
>>
>>INFO  [o.a.c.f.j.i.AsyncJobMonitor] (Job-Executor-1:ctx-62fc8d1c) Add
>>job-14 into job monitoring
>>WARN  [c.c.h.x.r.CitrixResourceBase] (DirectAgent-12:ctx-45af0575) There
>>are 0 storageid: 9f3f9262-3f77-09cc-2df7-0d8475676260
>>WARN  [c.c.h.x.r.CitrixResourceBase] (DirectAgent-56:ctx-cc6fb225)
>>Detecting a change in platform for r-8-VM
>>WARN  [o.a.c.f.j.i.AsyncJobMonitor] (Timer-2:ctx-18e096c3) Task (job-14)
>>has been pending for 98 seconds
>>WARN  [c.c.h.x.r.CitrixResourceBase] (DirectAgent-3:ctx-b1e5b734) There
>>are 0 storageid: 9f3f9262-3f77-09cc-2df7-0d8475676260
>>INFO  [o.a.c.s.v.VolumeServiceImpl] (Job-Executor-1:ctx-62fc8d1c
>>ctx-29a1762b) lock is acquired for VMTemplateStoragePool 13
>>WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-26:ctx-29532703)
>>There are 0 SRs with same name: 9f3f9262-3f77-09cc-2df7-0d8475676260
>>INFO  [o.a.c.s.v.VolumeServiceImpl] (Job-Executor-1:ctx-62fc8d1c
>>ctx-29a1762b) releasing lock for VMTemplateStoragePool 13
>>WARN  [c.c.u.d.Merovingian2] (Job-Executor-1:ctx-62fc8d1c ctx-29a1762b)
>>Was unable to find lock for the key template_spool_ref13 and thread id
>>1518511247
>>INFO  [c.c.v.VirtualMachineManagerImpl] (Job-Executor-1:ctx-62fc8d1c
>>ctx-29a1762b) Unable to contact resource.
>>com.cloud.exception.StorageUnavailableException: Resource [StoragePool:1]
>>is unreachable: Unable to create Vol[7|vm=7|ROOT]:There are 0 SRs with
>>same name: 9f3f9262-3f77-09cc-2df7-0d8475676260
>>  at 
>>org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVol
>>u
>>m
>>e(VolumeOrchestrator.java:1174)
>>  at 
>>org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(Vol
>>u
>>m
>>eOrchestrator.java:1216)
>>  at 
>>com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineMan
>>a
>>g
>>erImpl.java:944)
>>  at 
>>com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManager
>>I
>>m
>>pl.java:747)
>>  at 
>>com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.ja
>>v
>>a
>>:593)
>>  at 
>>org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployV
>>i
>>r
>>tualMachine(VMEntityManagerImpl.java:228)
>>  at 
>>org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.de
>>p
>>l
>>oy(VirtualMachineEntityImpl.java:207)
>>  at 
>>com.cloud.vm.UserVmMa

Re: Review Request 16973: Contrail Event Interceptor fix

[David Nalley]

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


What bug does this fix? 


- David Nalley


On Jan. 21, 2014, 7:55 p.m., Suresh Balineni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/16973/
> ---
> 
> (Updated Jan. 21, 2014, 7:55 p.m.)
> 
> 
> Review request for cloudstack.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> When project/domains are created,  our plugin code won't get invoked. Our 
> contrail plugin uses Event infrastructure provided by cloudstack to receive 
> these events and handle them accordingly. It is must to create 
> domains/projects before creating a virtual network/vm object in contrail 
> implementation. Hence our plugin must need a way to get notified about 
> project/domain events.
> 
> 
> Diffs
> -
> 
>   
> plugins/network-elements/juniper-contrail/resources/META-INF/cloudstack/system/spring-contrail-system-context-inheritable.xml
>  PRE-CREATION 
>   
> plugins/network-elements/juniper-contrail/src/org/apache/cloudstack/network/contrail/management/EventUtils.java
>  dd18ca6 
> 
> Diff: https://reviews.apache.org/r/16973/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Suresh Balineni
> 
>

Re: Review Request 16973: Contrail Event Interceptor fix

[Suresh Balineni]

Hi All,

This is contrail event interceptor fix for plugin to receive cloudstack events.
This is must required for contrail plugin to work.
Please review and shit this in 4.3.

Thanks

On Jan 21, 2014, at 11:56 AM, "Suresh Balineni" 
mailto:sbalin...@juniper.net>> wrote:

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

Review request for cloudstack.
By Suresh Balineni.
Repository: cloudstack-git
Description

When project/domains are created,  our plugin code won't get invoked. Our 
contrail plugin uses Event infrastructure provided by cloudstack to receive 
these events and handle them accordingly. It is must to create domains/projects 
before creating a virtual network/vm object in contrail implementation. Hence 
our plugin must need a way to get notified about project/domain events.


Diffs

  *   
plugins/network-elements/juniper-contrail/resources/META-INF/cloudstack/system/spring-contrail-system-context-inheritable.xml
 (PRE-CREATION)
  *   
plugins/network-elements/juniper-contrail/src/org/apache/cloudstack/network/contrail/management/EventUtils.java
 (dd18ca6)

View Diff

RE: [ACS 4.3] RC update

[Animesh Chaturvedi]

Folks

I don't see any outstanding blockers, the automation results were also 
published and seemed satisfactory.  I will process with building RC later today 
 I will also pull in few issues that were under discussion in security mailing 
list but later were identified as hardening issues (unencrypted passwords) and 
did not require to go through security process. 


Thanks
Animesh

-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
Sent: Friday, January 10, 2014 10:08 PM
To: dev@cloudstack.apache.org
Subject: RE: [ACS 4.3] RC update

Folks

Today is the scheduled RC date for ACS 4.3 We are very close with just a few 
lingering issues below.



| Jayapal Reddy| CLOUDSTACK-5848 : [Upgrade3.0.6-4.3]"Unable to parse 
VLAN tag" message when network associated with SRX external firewall device is 
rebooted. |
| edison su| CLOUDSTACK-5831 : As regular user , when trying to 
take a snapshot , snapshot succeeds but user is presented with "The given 
command does not exist or it is not available for user" message. |
| Unassigned   | CLOUDSTACK-5743 : Download ROOT Volume when the VM is 
in stopped state is failing with "Forbidden You don't have permission to access 
/userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server" |
| Likitha Shetty   | CLOUDSTACK-5707 : Hitting multiple exceptions when the 
Vsphere client is upgraded to 5.5 from 5.1  
   |
| Daan Hoogland| CLOUDSTACK-5502 : [Automation] createVlanIpRange API 
failing, if you pass VLAN   
 |
| Marcus Sorensen  | CLOUDSTACK-5432 : [Automation] Libvtd getting crashed 
and agent going to alert start  
|
| Sateesh Chodapuneedi | CLOUDSTACK-5408 : [Automation] Failed to deploy vm in 
vmware environment with error "due to java.io.IOException: Cannot run program 
"mount": java.io.IOException: error=12, Cannot allocate memory"   |
| Wei Zhou | CLOUDSTACK-5144 : [Automation]: Basic Zone Security 
Groups - SSH to VM is allowed even when there is no ingress rule defined for 
the security group   |


If you have not played with 4.3 yet please take it for a spin and call out any 
critical issues, I plan to build an RC early next week. 

Thanks
Animesh

-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
Sent: Tuesday, January 07, 2014 10:51 AM
To: dev@cloudstack.apache.org
Subject: [ACS 4.3] RC update

Folks

Happy new year everyone. I hope you all had a good recharging time off during 
holiday. I want to bring our attention and focus to getting the 4.3 release out 
the door. While our scheduled RC date is this Friday 1/10 but we still have 
many open blocker and critical. Please review your backlog of issues and bring 
them to resolution ASAP and provide a "Due Date" in the bug.  We need to 
absolutely make sure upgrades are working. If you encounter upgrade issue 
please file them as blockers. I will escalate all current upgrade issues to 
blocker.

For the most recent release status please visit the 4.3 Release Dashboard [1].  
I am following up on individual issues directly in JIRA so do watch JIRA emails

[1] http://s.apache.org/dFk

Thanks
Animesh

[Proposal]CloudStack IAM plugin feature (CLOUDSTACK-5920)

[Prachi Damle]

Min and myself would like to propose an identity and access management plugin 
for CloudStack for the ACS 4.4 release.

Here is the functional spec we have drafted for the first phase:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Identity+and+Access+Management+%28IAM%29+Plugin

Currently CloudStack provides very limited IAM services and there are several 
drawbacks:

- Offers few roles out of the box (user and admin) with prebaked access 
control. There is no way to create customized policies and permissions.
- Some resources have access control baked into them. E.g., shared networks, 
projects etc.
- We have to create special dedicateXXX APIs to grant permissions to resources.
- Also it does not provide the flexibility to integrate with other RBAC 
implementations say using AD/LDAP

Goal for this feature would be to address these limitations and offer true IAM 
services in a phased manner.
As a first phase, we need to separate out the current access control into a 
separate component based on the standard IAM terminologies. Also we need to 
create an access check mechanism to be used by the API layer to avoid the 
checks scattered over the api/service layer. The read/listing APIs need to be 
refactored accordingly to consider the policy based access granting.

Please provide feedback/suggestions anyone has.

Thanks,
Prachi & Min

Re: [ACS 4.3] RC update

[Erik Weber]

On Tue, Jan 21, 2014 at 10:41 PM, Animesh Chaturvedi <
animesh.chaturv...@citrix.com> wrote:

> Folks
>
> I don't see any outstanding blockers, the automation results were also
> published and seemed satisfactory.  I will process with building RC later
> today  I will also pull in few issues that were under discussion in
> security mailing list but later were identified as hardening issues
> (unencrypted passwords) and did not require to go through security process.
>
>

I haven't seen any automation tests for vmware?

-- 
Erik Weber

Re: [Proposal]CloudStack IAM plugin feature (CLOUDSTACK-5920)

[Erik Weber]

On Tue, Jan 21, 2014 at 10:57 PM, Prachi Damle wrote:

> Min and myself would like to propose an identity and access management
> plugin for CloudStack for the ACS 4.4 release.
>
> Here is the functional spec we have drafted for the first phase:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Identity+and+Access+Management+%28IAM%29+Plugin
>
> Currently CloudStack provides very limited IAM services and there are
> several drawbacks:
>
> - Offers few roles out of the box (user and admin) with prebaked access
> control. There is no way to create customized policies and permissions.
> - Some resources have access control baked into them. E.g., shared
> networks, projects etc.
> - We have to create special dedicateXXX APIs to grant permissions to
> resources.
> - Also it does not provide the flexibility to integrate with other RBAC
> implementations say using AD/LDAP
>
> Goal for this feature would be to address these limitations and offer true
> IAM services in a phased manner.
> As a first phase, we need to separate out the current access control into
> a separate component based on the standard IAM terminologies. Also we need
> to create an access check mechanism to be used by the API layer to avoid
> the checks scattered over the api/service layer. The read/listing APIs need
> to be refactored accordingly to consider the policy based access granting.
>
> Please provide feedback/suggestions anyone has.
>
>

Would love to see SAML 2.0 support, but any IAM solution is a good start :-)

-- 
Erik Weber

RE: [ACS 4.3] RC update

[Animesh Chaturvedi]

-Original Message-
From: Erik Weber [mailto:terbol...@gmail.com] 
Sent: Tuesday, January 21, 2014 1:58 PM
To: dev@cloudstack.apache.org
Subject: Re: [ACS 4.3] RC update

On Tue, Jan 21, 2014 at 10:41 PM, Animesh Chaturvedi < 
animesh.chaturv...@citrix.com> wrote:

> Folks
>
> I don't see any outstanding blockers, the automation results were also 
> published and seemed satisfactory.  I will process with building RC 
> later today  I will also pull in few issues that were under discussion 
> in security mailing list but later were identified as hardening issues 
> (unencrypted passwords) and did not require to go through security process.
>
>

I haven't seen any automation tests for vmware?
[Animesh] We only run automation for Xen and KVM in apache Jenkins infra

--
Erik Weber

RE: [ACS 4.3] RC update

[Sudha Ponnaganti]

VMware is noredist (non-oss) platform so it is not run just like KVM and Xen. 
However some of the teams may be running it locally in their labs. 

-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
Sent: Tuesday, January 21, 2014 2:03 PM
To: dev@cloudstack.apache.org
Subject: RE: [ACS 4.3] RC update



-Original Message-
From: Erik Weber [mailto:terbol...@gmail.com]
Sent: Tuesday, January 21, 2014 1:58 PM
To: dev@cloudstack.apache.org
Subject: Re: [ACS 4.3] RC update

On Tue, Jan 21, 2014 at 10:41 PM, Animesh Chaturvedi < 
animesh.chaturv...@citrix.com> wrote:

> Folks
>
> I don't see any outstanding blockers, the automation results were also 
> published and seemed satisfactory.  I will process with building RC 
> later today  I will also pull in few issues that were under discussion 
> in security mailing list but later were identified as hardening issues 
> (unencrypted passwords) and did not require to go through security process.
>
>

I haven't seen any automation tests for vmware?
[Animesh] We only run automation for Xen and KVM in apache Jenkins infra

--
Erik Weber

Cloudstack 4.3 on Centos i686

[Prabhakaran Ganesan]

Hi

Does 4.3 support Centos i686? I am able to download and build the source on my 
Centos host (32-bit). But I get the following Java exception when I try to 
start the management server. Is the problem with Java or is it some 64-bit 
dependency?

Thanks
Prabhakar

INFO  [c.c.s.GsonHelper] (main:null) Default Builder inited.
INFO  [c.c.u.c.ComponentContext] (main:null) Setup Spring Application context
INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Running system 
integrity checker com.cloud.upgrade.DatabaseIntegrityChecker@1344568
INFO  [c.c.u.DatabaseIntegrityChecker] (main:null) Grabbing lock to check for 
database integrity.
INFO  [c.c.u.DatabaseIntegrityChecker] (main:null) Performing database 
integrity check
INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Running system 
integrity checker 
org.apache.cloudstack.utils.identity.ManagementServerNode@4a3e92
INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Configuring 
CloudStack Components
2014-01-21 09:27:07.585:WARN::Failed startup of context 
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext@b71be{/client,/root/cloudstack/client/target/generated-webapp}
org.springframework.context.ApplicationContextException: Failed to start bean 
'cloudStackLifeCycle'; nested exception is net.sf.ehcache.CacheException: 
Unable to create CacheManagerPeerListener. Initial cause was 
sdk-vee-appliance-2.englab.juniper.net: sdk-vee-appliance-2.englab.juniper.net
at 
org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:170)
at 
org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51)
at 
org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339)
at 
org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143)
at 
org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108)
at 
org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:945)
at 
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:141)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:119)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:239)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:244)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:244)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:227)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:115)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(DefaultModuleDefinitionSet.java:78)
at 
org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules(ModuleBasedContextFactory.java:37)
at 
org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init(CloudStackSpringContext.java:69)
at 
org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContext.java:56)
at 
org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContext.java:60)
at 
org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener.contextInitialized(CloudStackContextLoaderListener.java:51)
at 
org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:549)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1282)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499)
at 
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:115)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at 
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at 
org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at 
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:224)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeC

Re: Cloudstack 4.3 on Centos i686

[Wido den Hollander]

On 01/21/2014 11:31 PM, Prabhakaran Ganesan wrote:

Hi

Does 4.3 support Centos i686? I am able to download and build the source on my 
Centos host (32-bit). But I get the following Java exception when I try to 
start the management server. Is the problem with Java or is it some 64-bit 
dependency?



Well, I think it should. The JVM should take care of the 32-bit/64-bit 
stuff, but my question is: Why still 32-bit?


I really don't see a memory related problem here, but you never know if 
the 4GB memory limit is a problem. I've never run CS under i686.


Wido


Thanks
Prabhakar

INFO  [c.c.s.GsonHelper] (main:null) Default Builder inited.
INFO  [c.c.u.c.ComponentContext] (main:null) Setup Spring Application context
INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Running system 
integrity checker com.cloud.upgrade.DatabaseIntegrityChecker@1344568
INFO  [c.c.u.DatabaseIntegrityChecker] (main:null) Grabbing lock to check for 
database integrity.
INFO  [c.c.u.DatabaseIntegrityChecker] (main:null) Performing database 
integrity check
INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Running system 
integrity checker 
org.apache.cloudstack.utils.identity.ManagementServerNode@4a3e92
INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Configuring 
CloudStack Components
2014-01-21 09:27:07.585:WARN::Failed startup of context 
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext@b71be{/client,/root/cloudstack/client/target/generated-webapp}
org.springframework.context.ApplicationContextException: Failed to start bean 
'cloudStackLifeCycle'; nested exception is net.sf.ehcache.CacheException: 
Unable to create CacheManagerPeerListener. Initial cause was 
sdk-vee-appliance-2.englab.juniper.net: sdk-vee-appliance-2.englab.juniper.net
at 
org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:170)
at 
org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51)
at 
org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339)
at 
org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143)
at 
org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108)
at 
org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:945)
at 
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:141)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:119)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:239)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:244)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:244)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:227)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:115)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(DefaultModuleDefinitionSet.java:78)
at 
org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules(ModuleBasedContextFactory.java:37)
at 
org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init(CloudStackSpringContext.java:69)
at 
org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContext.java:56)
at 
org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContext.java:60)
at 
org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener.contextInitialized(CloudStackContextLoaderListener.java:51)
at 
org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:549)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1282)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499)
at 
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:115)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at 
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at 
org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at 
org.mortbay.jetty.handler

Re: VmWare SDK to vijava

[Hugo Trippaers]

Let's not repeat the previous discussion. We allready agreed that the wsdl is 
the way forward. However we can't get any legal entity to say that it is ok to 
do so.

Hence my proposal to at least move forward even if it means to temporarily use 
vijava. 

I really don't care what we do, as long as we have VMware in the regular build 
before the 4.4 feature freeze.

If anyone of you is willing to chase VMware legal on this, please have a go at 
it.

Hugo

Sent from my iPhone

> On 21 jan. 2014, at 19:32, Chiradeep Vittal  
> wrote:
> 
> Suboptimal for?
> Wouldn't the ACS user want the best / supported client libraries?
> Alternatively, can't we just compile the WSDL and check in the generated
> sources? Not check-in the WSDL, but the client sources.
> 
>> On 1/21/14 7:18 AM, "David Nalley"  wrote:
>> 
>> On Tue, Jan 21, 2014 at 9:46 AM, Chip Childers 
>> wrote:
>>> I bet we never got an answer. Frankly, I'd like to see us use
>>> something where the licensing is clear.  That, or we don't include the
>>> WSDL in our repo / distro.
>> 
>> Additionally, we are an open source project that is in the business of
>> producing open source software. Depending on non-free and
>> non-opensource libraries is suboptimal, but its worse when there is a
>> open source alternative.
>> 
>> --David
> 

Re: VmWare SDK to vijava

[Hugo Trippaers]

Chiradeep,

Even on the generated sources nobody seems willing to state that it is ok to 
include them at the moment. Otherwise I would have put them in already.

Hugo

Sent from my iPhone

> On 21 jan. 2014, at 19:32, Chiradeep Vittal  
> wrote:
> 
> Suboptimal for?
> Wouldn't the ACS user want the best / supported client libraries?
> Alternatively, can't we just compile the WSDL and check in the generated
> sources? Not check-in the WSDL, but the client sources.
> 
>> On 1/21/14 7:18 AM, "David Nalley"  wrote:
>> 
>> On Tue, Jan 21, 2014 at 9:46 AM, Chip Childers 
>> wrote:
>>> I bet we never got an answer. Frankly, I'd like to see us use
>>> something where the licensing is clear.  That, or we don't include the
>>> WSDL in our repo / distro.
>> 
>> Additionally, we are an open source project that is in the business of
>> producing open source software. Depending on non-free and
>> non-opensource libraries is suboptimal, but its worse when there is a
>> open source alternative.
>> 
>> --David
> 

Re: Cloudstack 4.3 on Centos i686

[Prabhakaran Ganesan]

Hi Wido

Thanks a lot for your response. I happened to have a i686 Centos host,
hence the question. Let me upgrade the server to x86_64 and give it a try.

Thanks
Prabhakar

On 1/21/14 2:38 PM, "Wido den Hollander"  wrote:

>
>
>On 01/21/2014 11:31 PM, Prabhakaran Ganesan wrote:
>> Hi
>>
>> Does 4.3 support Centos i686? I am able to download and build the
>>source on my Centos host (32-bit). But I get the following Java
>>exception when I try to start the management server. Is the problem with
>>Java or is it some 64-bit dependency?
>>
>
>Well, I think it should. The JVM should take care of the 32-bit/64-bit
>stuff, but my question is: Why still 32-bit?
>
>I really don't see a memory related problem here, but you never know if
>the 4GB memory limit is a problem. I've never run CS under i686.
>
>Wido
>
>> Thanks
>> Prabhakar
>>
>> INFO  [c.c.s.GsonHelper] (main:null) Default Builder inited.
>> INFO  [c.c.u.c.ComponentContext] (main:null) Setup Spring Application
>>context
>> INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Running
>>system integrity checker
>>com.cloud.upgrade.DatabaseIntegrityChecker@1344568
>> INFO  [c.c.u.DatabaseIntegrityChecker] (main:null) Grabbing lock to
>>check for database integrity.
>> INFO  [c.c.u.DatabaseIntegrityChecker] (main:null) Performing database
>>integrity check
>> INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Running
>>system integrity checker
>>org.apache.cloudstack.utils.identity.ManagementServerNode@4a3e92
>> INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Configuring
>>CloudStack Components
>> 2014-01-21 09:27:07.585:WARN::Failed startup of context
>>org.mortbay.jetty.plugin.Jetty6PluginWebAppContext@b71be{/client,/root/cl
>>oudstack/client/target/generated-webapp}
>> org.springframework.context.ApplicationContextException: Failed to
>>start bean 'cloudStackLifeCycle'; nested exception is
>>net.sf.ehcache.CacheException: Unable to create
>>CacheManagerPeerListener. Initial cause was
>>sdk-vee-appliance-2.englab.juniper.net:
>>sdk-vee-appliance-2.englab.juniper.net
>> at 
>>org.springframework.context.support.DefaultLifecycleProcessor.doStart(Def
>>aultLifecycleProcessor.java:170)
>> at 
>>org.springframework.context.support.DefaultLifecycleProcessor.access$200(
>>DefaultLifecycleProcessor.java:51)
>> at 
>>org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGr
>>oup.start(DefaultLifecycleProcessor.java:339)
>> at 
>>org.springframework.context.support.DefaultLifecycleProcessor.startBeans(
>>DefaultLifecycleProcessor.java:143)
>> at 
>>org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(D
>>efaultLifecycleProcessor.java:108)
>> at 
>>org.springframework.context.support.AbstractApplicationContext.finishRefr
>>esh(AbstractApplicationContext.java:945)
>> at 
>>org.springframework.context.support.AbstractApplicationContext.refresh(Ab
>>stractApplicationContext.java:482)
>> at 
>>org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet
>>.loadContext(DefaultModuleDefinitionSet.java:141)
>> at 
>>org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet
>>$2.with(DefaultModuleDefinitionSet.java:119)
>> at 
>>org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet
>>.withModule(DefaultModuleDefinitionSet.java:239)
>> at 
>>org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet
>>.withModule(DefaultModuleDefinitionSet.java:244)
>> at 
>>org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet
>>.withModule(DefaultModuleDefinitionSet.java:244)
>> at 
>>org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet
>>.withModule(DefaultModuleDefinitionSet.java:227)
>> at 
>>org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet
>>.loadContexts(DefaultModuleDefinitionSet.java:115)
>> at 
>>org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet
>>.load(DefaultModuleDefinitionSet.java:78)
>> at 
>>org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loa
>>dModules(ModuleBasedContextFactory.java:37)
>> at 
>>org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init(
>>CloudStackSpringContext.java:69)
>> at 
>>org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.>>(CloudStackSpringContext.java:56)
>> at 
>>org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.>>(CloudStackSpringContext.java:60)
>> at 
>>org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener.c
>>ontextInitialized(CloudStackContextLoaderListener.java:51)
>> at 
>>org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java
>>:549)
>> at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
>> at 
>>org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:12
>>82)
>> at 
>>org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
>> at 
>>org.mortbay.jetty.webapp.WebAppContext.doS

Re: VmWare SDK to vijava

[Chiradeep Vittal]

Apparently we can 
https://communities.vmware.com/docs/DOC-7983
http://markmail.org/thread/ttamcfb4d6azzbw7


On 1/21/14 2:46 PM, "Hugo Trippaers"  wrote:

>Chiradeep,
>
>Even on the generated sources nobody seems willing to state that it is ok
>to include them at the moment. Otherwise I would have put them in already.
>
>Hugo
>
>Sent from my iPhone
>
>> On 21 jan. 2014, at 19:32, Chiradeep Vittal
>> wrote:
>> 
>> Suboptimal for?
>> Wouldn't the ACS user want the best / supported client libraries?
>> Alternatively, can't we just compile the WSDL and check in the generated
>> sources? Not check-in the WSDL, but the client sources.
>> 
>>> On 1/21/14 7:18 AM, "David Nalley"  wrote:
>>> 
>>> On Tue, Jan 21, 2014 at 9:46 AM, Chip Childers
>>>
>>> wrote:
 I bet we never got an answer. Frankly, I'd like to see us use
 something where the licensing is clear.  That, or we don't include the
 WSDL in our repo / distro.
>>> 
>>> Additionally, we are an open source project that is in the business of
>>> producing open source software. Depending on non-free and
>>> non-opensource libraries is suboptimal, but its worse when there is a
>>> open source alternative.
>>> 
>>> --David
>> 

Re: VmWare SDK to vijava

[Kelven Yang]

Q. Can I redistribute the VI SDK libraries and sample code?
A. You can redistribute only those parts of the SDK package that have been
designated as ³distributable code².
In VI SDK 2.5, the following components can be redistributed: vim.jar,
vim25.jar. To note developers typically generate web service stubs from
the WSDL file that is included in the VI SDK using a SOAP toolkit.

>> The stubs source and the compiled stubs can also be distributed.


Could this solve our license problem, we discussed before that generating
our own java stub can give us flexibility to support co-existence of
different versions of VMware web service API inside CloudStack.

If we see this as urgency, we need to have someone work on to put WSDL
generation process to maven build

For latest names of VI SDK libraries that can be redistributed visit
http://vmware.com/go/sdk-redistribution-info



On 1/21/14, 3:18 PM, "Chiradeep Vittal" 
wrote:

>Apparently we can 
>https://communities.vmware.com/docs/DOC-7983
>http://markmail.org/thread/ttamcfb4d6azzbw7
>
>
>On 1/21/14 2:46 PM, "Hugo Trippaers"  wrote:
>
>>Chiradeep,
>>
>>Even on the generated sources nobody seems willing to state that it is ok
>>to include them at the moment. Otherwise I would have put them in
>>already.
>>
>>Hugo
>>
>>Sent from my iPhone
>>
>>> On 21 jan. 2014, at 19:32, Chiradeep Vittal
>>> wrote:
>>> 
>>> Suboptimal for?
>>> Wouldn't the ACS user want the best / supported client libraries?
>>> Alternatively, can't we just compile the WSDL and check in the
>>>generated
>>> sources? Not check-in the WSDL, but the client sources.
>>> 
 On 1/21/14 7:18 AM, "David Nalley"  wrote:
 
 On Tue, Jan 21, 2014 at 9:46 AM, Chip Childers

 wrote:
> I bet we never got an answer. Frankly, I'd like to see us use
> something where the licensing is clear.  That, or we don't include
>the
> WSDL in our repo / distro.
 
 Additionally, we are an open source project that is in the business of
 producing open source software. Depending on non-free and
 non-opensource libraries is suboptimal, but its worse when there is a
 open source alternative.
 
 --David
>>> 
>

Re: Review Request 16867: Test Suite for Testing Remote Access VPN on VPC

[Chandan Purushothama]

> On Jan. 21, 2014, 10:22 a.m., Santhosh Edukulla wrote:
> > test/integration/component/test_remotevpn_vpc.py, line 432
> > 
> >
> > is %d right here?

%defaultroute is specific to ipsec.conf file. It is not %d implying int. 
Dropping the issue based on this reason. Kindly reopen it in case if more 
explanation is required.


> On Jan. 21, 2014, 10:22 a.m., Santhosh Edukulla wrote:
> > test/integration/component/test_remotevpn_vpc.py, line 447
> > 
> >
> > why some static methods and few class methods?

I used static methods for the operations where i have to just create a file and 
obtain the file. It doesn't have to know anything about the class or instance 
it was called on. It just gets the arguments that were passed, no implicit 
first argument. 

Dropping the issue based on this reason. Kindly reopen it in case if more 
explanation is required.


- Chandan


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


On Jan. 16, 2014, 7:12 p.m., Chandan Purushothama wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/16867/
> ---
> 
> (Updated Jan. 16, 2014, 7:12 p.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar, SrikanteswaraRao Talluri, 
> and Sheng Yang.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Test Suite for Testing Remote Access VPN on VPC. 
> 
> I successfully automated the following components:
> 
> 1.VPN Client Installation on Linux
> 2.Component that efficiently verifies Remote VPN Access between client and 
> the Server.
> 3.Developed a component that automates VPN Client Configuration and services.
> 4.Test Cases of the Feature
> 5.Tested the Code multiple times on XenServer and fixed the bugs.
> 6.Requirement on VMWare: Default Template should be CentOS 5.5 or higher for 
> the test suite to work. VPN Client cannot be installed on CentOS 5.3 Default 
> Template on VMWare.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_remotevpn_vpc.py PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/16867/diff/
> 
> 
> Testing
> ---
> 
> Test case no : Enable VPN for Public IP Address on the VPC ... ok
> Test case no : Remote a VPN User ... ok
> Test case no : Add a Different VPN User and Test Access with already existing 
> VPN User ... ok
> Test case no : Add a Previously Removed VPN User from the VPC and Test the 
> VPN Connectivity ... ok
> Test case no : Disable the VPN Service on the VPC ... ok
> Test case no : Enabled Previously Dsiabled VPN Access to VPC. ... ok
> Test case no : Create Nine VPN Users to test the remote.vpn.user.limit=8 
> Configuration parameter ... ok
> 
> --
> Ran 7 tests in 645.787s
> 
> OK
> 
> 
> File Attachments
> 
> 
> 0001-Test-Suite-for-Remote-Access-VPN-on-VPC.patch
>   
> https://reviews.apache.org/media/uploaded/files/2014/01/14/c6d3f593-d0eb-407c-aad2-574ebf9ca0f8__0001-Test-Suite-for-Remote-Access-VPN-on-VPC.patch
> 
> 
> Thanks,
> 
> Chandan Purushothama
> 
>

Re: [Proposal]CloudStack IAM plugin feature (CLOUDSTACK-5920)

[Chiradeep Vittal]

SAML 2.0 is not precluded with this design, it seems.
I found the FS both confusing and illuminating. I think what confuses me
is the interchange of 'acl', 'iam' and 'policy'.
Especially since ACL is used in the networking context.

IMO, renaming the tables and APIs to not use ACL but IAM would clarify
matters.
For example:
Tables: iam_policy, iam_policy_permission, iam_group
API: createIAMGroup createIAMPolicy createIAMPermission
addIAMPermissionToAclPolicy attachPolicyToIAMGroup addAccountToIAMGroup
(or better, house the api under the client/iam/?command= sub-url)
Annotation: @IamPolicyCheck

Also, there is no reference to what one would normally find in an IAM user
guide: Principal, Role, etc.
Am I right in assuming that Account is the Principal here? Are there
roles, or even a default role?

What is envisioned for Phase 2, 3Š

Ideally, this is a separate service that can be enhanced by 3rd parties.
As an example, I want to provide my DBaaS service on an ACS-powered cloud.
I want to utilize the same Principals (and IAM infrastructure) rather than
provide my own. 

--
Chiradeep



On 1/21/14 2:01 PM, "Erik Weber"  wrote:

>On Tue, Jan 21, 2014 at 10:57 PM, Prachi Damle
>wrote:
>
>> Min and myself would like to propose an identity and access management
>> plugin for CloudStack for the ACS 4.4 release.
>>
>> Here is the functional spec we have drafted for the first phase:
>>
>> 
>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Identit
>>y+and+Access+Management+%28IAM%29+Plugin
>>
>> Currently CloudStack provides very limited IAM services and there are
>> several drawbacks:
>>
>> - Offers few roles out of the box (user and admin) with prebaked access
>> control. There is no way to create customized policies and permissions.
>> - Some resources have access control baked into them. E.g., shared
>> networks, projects etc.
>> - We have to create special dedicateXXX APIs to grant permissions to
>> resources.
>> - Also it does not provide the flexibility to integrate with other RBAC
>> implementations say using AD/LDAP
>>
>> Goal for this feature would be to address these limitations and offer
>>true
>> IAM services in a phased manner.
>> As a first phase, we need to separate out the current access control
>>into
>> a separate component based on the standard IAM terminologies. Also we
>>need
>> to create an access check mechanism to be used by the API layer to avoid
>> the checks scattered over the api/service layer. The read/listing APIs
>>need
>> to be refactored accordingly to consider the policy based access
>>granting.
>>
>> Please provide feedback/suggestions anyone has.
>>
>>
>
>Would love to see SAML 2.0 support, but any IAM solution is a good start
>:-)
>
>-- 
>Erik Weber

Re: [Proposal]CloudStack IAM plugin feature (CLOUDSTACK-5920)

[Chiradeep Vittal]

Also not clear on how the dedicateXyZ problem is being solved in Phase1
(or not).
Can I (end user) create a VPC and allow user Bob to create VMs in my VPC?

On 1/21/14 4:20 PM, "Chiradeep Vittal"  wrote:

>SAML 2.0 is not precluded with this design, it seems.
>I found the FS both confusing and illuminating. I think what confuses me
>is the interchange of 'acl', 'iam' and 'policy'.
>Especially since ACL is used in the networking context.
>
>IMO, renaming the tables and APIs to not use ACL but IAM would clarify
>matters.
>For example:
>Tables: iam_policy, iam_policy_permission, iam_group
>API: createIAMGroup createIAMPolicy createIAMPermission
>addIAMPermissionToAclPolicy attachPolicyToIAMGroup addAccountToIAMGroup
>(or better, house the api under the client/iam/?command= sub-url)
>Annotation: @IamPolicyCheck
>
>Also, there is no reference to what one would normally find in an IAM user
>guide: Principal, Role, etc.
>Am I right in assuming that Account is the Principal here? Are there
>roles, or even a default role?
>
>What is envisioned for Phase 2, 3Š
>
>Ideally, this is a separate service that can be enhanced by 3rd parties.
>As an example, I want to provide my DBaaS service on an ACS-powered cloud.
>I want to utilize the same Principals (and IAM infrastructure) rather than
>provide my own. 
>
>--
>Chiradeep
>
>
>
>On 1/21/14 2:01 PM, "Erik Weber"  wrote:
>
>>On Tue, Jan 21, 2014 at 10:57 PM, Prachi Damle
>>wrote:
>>
>>> Min and myself would like to propose an identity and access management
>>> plugin for CloudStack for the ACS 4.4 release.
>>>
>>> Here is the functional spec we have drafted for the first phase:
>>>
>>> 
>>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Identi
>>>t
>>>y+and+Access+Management+%28IAM%29+Plugin
>>>
>>> Currently CloudStack provides very limited IAM services and there are
>>> several drawbacks:
>>>
>>> - Offers few roles out of the box (user and admin) with prebaked access
>>> control. There is no way to create customized policies and permissions.
>>> - Some resources have access control baked into them. E.g., shared
>>> networks, projects etc.
>>> - We have to create special dedicateXXX APIs to grant permissions to
>>> resources.
>>> - Also it does not provide the flexibility to integrate with other RBAC
>>> implementations say using AD/LDAP
>>>
>>> Goal for this feature would be to address these limitations and offer
>>>true
>>> IAM services in a phased manner.
>>> As a first phase, we need to separate out the current access control
>>>into
>>> a separate component based on the standard IAM terminologies. Also we
>>>need
>>> to create an access check mechanism to be used by the API layer to
>>>avoid
>>> the checks scattered over the api/service layer. The read/listing APIs
>>>need
>>> to be refactored accordingly to consider the policy based access
>>>granting.
>>>
>>> Please provide feedback/suggestions anyone has.
>>>
>>>
>>
>>Would love to see SAML 2.0 support, but any IAM solution is a good start
>>:-)
>>
>>-- 
>>Erik Weber
>

RE: [Proposal]CloudStack IAM plugin feature (CLOUDSTACK-5920)

[Prachi Damle]

Some answers inline.

Prachi

-Original Message-
From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] 
Sent: Tuesday, January 21, 2014 4:20 PM
To: dev@cloudstack.apache.org
Subject: Re: [Proposal]CloudStack IAM plugin feature (CLOUDSTACK-5920)

SAML 2.0 is not precluded with this design, it seems.
>>[Prachi] Yes this design does not include the SAML 2.0 support
I found the FS both confusing and illuminating. I think what confuses me is the 
interchange of 'acl', 'iam' and 'policy'.
Especially since ACL is used in the networking context.

IMO, renaming the tables and APIs to not use ACL but IAM would clarify matters.
For example:
Tables: iam_policy, iam_policy_permission, iam_group
API: createIAMGroup createIAMPolicy createIAMPermission 
addIAMPermissionToAclPolicy attachPolicyToIAMGroup addAccountToIAMGroup (or 
better, house the api under the client/iam/?command= sub-url)
Annotation: @IamPolicyCheck

>>[Prachi] I guess yes to avoid confusion, given that the term ACL is already 
>>used in networking context, we can stick to using 'iam' and rename our 
>>APIs/annotations 


Also, there is no reference to what one would normally find in an IAM user
guide: Principal, Role, etc.
Am I right in assuming that Account is the Principal here? 
>>[Prachi] yes, CloudStack Account is analogous the IAM term Principal . As 
>>mentioned all the permission controls are done at the CS Account level.

Are there roles, or even a default role?
>>[Prachi] There is no 'role' entity. We are using the IAM 
>>Group-Policy-Permission model.
The current default roles of CloudStack (user,admin,domainAdmin) will be 
translated into default policies as mentioned in the FS 'Default Policy' 
section.  These will be loaded as metadata.


What is envisioned for Phase 2, 3Š
>>[Prachi] 
- Firstly some easier way of creating custome policies and permissions. The 
current FS does not include any UI/tool to create custom policies - all is API 
based for first phase.  
- Also, based on earlier suggestion from the community, a JSON based policy 
structure will bring in more flexibility.
- SAML 2.0,identity federation to be considered

Ideally, this is a separate service that can be enhanced by 3rd parties.
As an example, I want to provide my DBaaS service on an ACS-powered cloud.
I want to utilize the same Principals (and IAM infrastructure) rather than 
provide my own. 

--
Chiradeep



On 1/21/14 2:01 PM, "Erik Weber"  wrote:

>On Tue, Jan 21, 2014 at 10:57 PM, Prachi Damle
>wrote:
>
>> Min and myself would like to propose an identity and access 
>> management plugin for CloudStack for the ACS 4.4 release.
>>
>> Here is the functional spec we have drafted for the first phase:
>>
>> 
>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Iden
>>tit
>>y+and+Access+Management+%28IAM%29+Plugin
>>
>> Currently CloudStack provides very limited IAM services and there are 
>> several drawbacks:
>>
>> - Offers few roles out of the box (user and admin) with prebaked 
>> access control. There is no way to create customized policies and 
>> permissions.
>> - Some resources have access control baked into them. E.g., shared 
>> networks, projects etc.
>> - We have to create special dedicateXXX APIs to grant permissions to 
>> resources.
>> - Also it does not provide the flexibility to integrate with other 
>> RBAC implementations say using AD/LDAP
>>
>> Goal for this feature would be to address these limitations and offer 
>>true  IAM services in a phased manner.
>> As a first phase, we need to separate out the current access control 
>>into  a separate component based on the standard IAM terminologies. 
>>Also we need  to create an access check mechanism to be used by the 
>>API layer to avoid  the checks scattered over the api/service layer. 
>>The read/listing APIs need  to be refactored accordingly to consider 
>>the policy based access granting.
>>
>> Please provide feedback/suggestions anyone has.
>>
>>
>
>Would love to see SAML 2.0 support, but any IAM solution is a good 
>start
>:-)
>
>--
>Erik Weber

RE: [ACS 4.3] RC update

[Animesh Chaturvedi]

Now that we are getting ready to build first RC for 4.3. I wanted to call out 
for volunteers  help on updating the Release Notes, Documentation and 
Translations.


Thanks
Animesh

-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
Sent: Tuesday, January 21, 2014 1:41 PM
To: dev@cloudstack.apache.org
Subject: RE: [ACS 4.3] RC update

Folks

I don't see any outstanding blockers, the automation results were also 
published and seemed satisfactory.  I will process with building RC later today 
 I will also pull in few issues that were under discussion in security mailing 
list but later were identified as hardening issues (unencrypted passwords) and 
did not require to go through security process. 


Thanks
Animesh

-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
Sent: Friday, January 10, 2014 10:08 PM
To: dev@cloudstack.apache.org
Subject: RE: [ACS 4.3] RC update

Folks

Today is the scheduled RC date for ACS 4.3 We are very close with just a few 
lingering issues below.



| Jayapal Reddy| CLOUDSTACK-5848 : [Upgrade3.0.6-4.3]"Unable to parse 
VLAN tag" message when network associated with SRX external firewall device is 
rebooted. |
| edison su| CLOUDSTACK-5831 : As regular user , when trying to 
take a snapshot , snapshot succeeds but user is presented with "The given 
command does not exist or it is not available for user" message. |
| Unassigned   | CLOUDSTACK-5743 : Download ROOT Volume when the VM is 
in stopped state is failing with "Forbidden You don't have permission to access 
/userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server" |
| Likitha Shetty   | CLOUDSTACK-5707 : Hitting multiple exceptions when the 
Vsphere client is upgraded to 5.5 from 5.1  
   |
| Daan Hoogland| CLOUDSTACK-5502 : [Automation] createVlanIpRange API 
failing, if you pass VLAN   
 |
| Marcus Sorensen  | CLOUDSTACK-5432 : [Automation] Libvtd getting crashed 
and agent going to alert start  
|
| Sateesh Chodapuneedi | CLOUDSTACK-5408 : [Automation] Failed to deploy vm in 
vmware environment with error "due to java.io.IOException: Cannot run program 
"mount": java.io.IOException: error=12, Cannot allocate memory"   |
| Wei Zhou | CLOUDSTACK-5144 : [Automation]: Basic Zone Security 
Groups - SSH to VM is allowed even when there is no ingress rule defined for 
the security group   |


If you have not played with 4.3 yet please take it for a spin and call out any 
critical issues, I plan to build an RC early next week. 

Thanks
Animesh

-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
Sent: Tuesday, January 07, 2014 10:51 AM
To: dev@cloudstack.apache.org
Subject: [ACS 4.3] RC update

Folks

Happy new year everyone. I hope you all had a good recharging time off during 
holiday. I want to bring our attention and focus to getting the 4.3 release out 
the door. While our scheduled RC date is this Friday 1/10 but we still have 
many open blocker and critical. Please review your backlog of issues and bring 
them to resolution ASAP and provide a "Due Date" in the bug.  We need to 
absolutely make sure upgrades are working. If you encounter upgrade issue 
please file them as blockers. I will escalate all current upgrade issues to 
blocker.

For the most recent release status please visit the 4.3 Release Dashboard [1].  
I am following up on individual issues directly in JIRA so do watch JIRA emails

[1] http://s.apache.org/dFk

Thanks
Animesh

RE: [Proposal]CloudStack IAM plugin feature (CLOUDSTACK-5920)

[Prachi Damle]

-Original Message-
From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] 
Sent: Tuesday, January 21, 2014 4:27 PM
To: dev@cloudstack.apache.org
Subject: Re: [Proposal]CloudStack IAM plugin feature (CLOUDSTACK-5920)

Also not clear on how the dedicateXyZ problem is being solved in Phase1 (or 
not).
>>[Prachi] Yes, the dedicate APIs is not yet included

Can I (end user) create a VPC and allow user Bob to create VMs in my VPC?
>>[Prachi]  So looks like for current CS VPC, there is no access checks done on 
>>the VPC entry itself - the access checks are all the individual networks of 
>>the VPC tiers. 

So if  user A grants access to the network n1 in the VPC to another user B - 
then user B can invoke deployVM API using this networkId.
To do this user A has to:
- Create a policy with 'Allow' permission to this networkId (scope: Resource, 
scopeId: n1, resourceType: Network) for 'listNetworks' action/ 'use' access 
- Attach this policy to a group and add account to that group.

For phase1 we are still thinking if the IAM APIs (creation of 
group/policies/granting) should be root admin only to restrict the scope of the 
feature.

But the model does support  granting at three levels and will support such use 
cases:
- Grant by Domain and Resource Type: grant permissions to all resources of 
the given resource type under the given domain.
   -  Grant by Account and Resource Type: grant permissions to all resources of 
the given resource type under the given account.
- Grant by individual resource: grant permission to an individual resource.

Prachi

On 1/21/14 4:20 PM, "Chiradeep Vittal"  wrote:

>SAML 2.0 is not precluded with this design, it seems.
>I found the FS both confusing and illuminating. I think what confuses 
>me is the interchange of 'acl', 'iam' and 'policy'.
>Especially since ACL is used in the networking context.
>
>IMO, renaming the tables and APIs to not use ACL but IAM would clarify 
>matters.
>For example:
>Tables: iam_policy, iam_policy_permission, iam_group
>API: createIAMGroup createIAMPolicy createIAMPermission 
>addIAMPermissionToAclPolicy attachPolicyToIAMGroup addAccountToIAMGroup 
>(or better, house the api under the client/iam/?command= sub-url)
>Annotation: @IamPolicyCheck
>
>Also, there is no reference to what one would normally find in an IAM 
>user
>guide: Principal, Role, etc.
>Am I right in assuming that Account is the Principal here? Are there 
>roles, or even a default role?
>
>What is envisioned for Phase 2, 3Š
>
>Ideally, this is a separate service that can be enhanced by 3rd parties.
>As an example, I want to provide my DBaaS service on an ACS-powered cloud.
>I want to utilize the same Principals (and IAM infrastructure) rather 
>than provide my own.
>
>--
>Chiradeep
>
>
>
>On 1/21/14 2:01 PM, "Erik Weber"  wrote:
>
>>On Tue, Jan 21, 2014 at 10:57 PM, Prachi Damle
>>wrote:
>>
>>> Min and myself would like to propose an identity and access 
>>> management plugin for CloudStack for the ACS 4.4 release.
>>>
>>> Here is the functional spec we have drafted for the first phase:
>>>
>>> 
>>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Ide
>>>nti
>>>t
>>>y+and+Access+Management+%28IAM%29+Plugin
>>>
>>> Currently CloudStack provides very limited IAM services and there 
>>> are several drawbacks:
>>>
>>> - Offers few roles out of the box (user and admin) with prebaked 
>>> access control. There is no way to create customized policies and 
>>> permissions.
>>> - Some resources have access control baked into them. E.g., shared 
>>> networks, projects etc.
>>> - We have to create special dedicateXXX APIs to grant permissions to 
>>> resources.
>>> - Also it does not provide the flexibility to integrate with other 
>>> RBAC implementations say using AD/LDAP
>>>
>>> Goal for this feature would be to address these limitations and 
>>>offer true  IAM services in a phased manner.
>>> As a first phase, we need to separate out the current access control 
>>>into  a separate component based on the standard IAM terminologies. 
>>>Also we need  to create an access check mechanism to be used by the 
>>>API layer to avoid  the checks scattered over the api/service layer. 
>>>The read/listing APIs need  to be refactored accordingly to consider 
>>>the policy based access granting.
>>>
>>> Please provide feedback/suggestions anyone has.
>>>
>>>
>>
>>Would love to see SAML 2.0 support, but any IAM solution is a good 
>>start
>>:-)
>>
>>--
>>Erik Weber
>

Re: [SUMMARY][DISCUSS][PROPOSAL] Move docs to .rst format and readthedocs

[David Nalley]

In IRC Sebastien was noting that the content was already becoming
quite large for a single 'site'/pdf/epub, and it soon gets
bewildering.

I am going to open up a few additional git repos and see if that
alleviates the issue.

--David

On Sat, Dec 21, 2013 at 12:37 PM, Sebastien Goasguen  wrote:
> Looks like we have a consensus,
>
> I will take this on and make sure it gets implemented as fast as possible.
>
> If any one wants to start to contribute docs over christmas, please send pr 
> to:
> https://github.com/runseb/acsdocs
>
> Thanks to Shankar for already sending a trouble shooting guide.
>
> You can also send a rst or markdown file to review board, I will pull, 
> convert and merge everything.
> Once the move is made I will document the entire process.
>
> Merry Christmas everyone,
>
> -Sebastien
>
>
> On Dec 19, 2013, at 4:47 PM, Animesh Chaturvedi 
>  wrote:
>
>>
>>
>> -Original Message-
>> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>> Sent: Tuesday, December 10, 2013 9:24 AM
>> To: dev@cloudstack.apache.org
>> Cc: Radhika Puthiyetath; msweet@gmail.com; Mike Tutkowski
>> Subject: RE: [DISCUSS][PROPOSAL] Move docs to .rst format and readthedocs
>>
>>
>>
>> -Original Message-
>> From: Sebastien Goasguen [mailto:run...@gmail.com]
>> Sent: Monday, December 09, 2013 11:31 PM
>> To: dev@cloudstack.apache.org
>> Cc: Radhika Puthiyetath; msweet@gmail.com; Mike Tutkowski
>> Subject: Re: [DISCUSS][PROPOSAL] Move docs to .rst format and readthedocs
>>
>>
>> On Dec 9, 2013, at 9:37 PM, Animesh Chaturvedi 
>>  wrote:
>>
>>> I am +1 to make documentation easier but we just passed code freeze for 4.3 
>>> and I feel we need to do it after 4.3.
>>>
>>
>> docs are not in the 4.3 code branch. it's different releases...
>>
>> Animesh> But they will be released together.
>> [Animesh] Sebastien what is the planned ETA for the conversion to RST. ACS 
>> 4.3 planned RC date is 1/10 and I would like to have the documentation ready 
>> by 1/3.
>>
>>>
>>> Animesh
>>>
>>> -Original Message-
>>> From: sebgoa [mailto:run...@gmail.com]
>>> Sent: Monday, December 09, 2013 3:54 AM
>>> To: dev@cloudstack.apache.org
>>> Cc: Radhika Puthiyetath; msweet@gmail.com; Mike Tutkowski
>>> Subject: [DISCUSS][PROPOSAL] Move docs to .rst format and readthedocs
>>>
>>> Hi,
>>>
>>> There has been lots of discussion about docs over the last 3/4 months, in 
>>> summary the issues are:
>>>
>>> -Difficult to maintain and keep website up to date (issues with lang and 
>>> issues with pdf formatting lately) -Difficult to contribute to easily, 
>>> docbook is fine but tedious to work on.
>>> -Errors in the docs don't get properly fixed -Mix of OS information -Lack 
>>> of content for certain features -Docs release cycle. Docs have bugs that 
>>> will never get fixed in that specific release (because we see it as code 
>>> release)
>>>
>>> To remedy some of those issues and work on a new release process specific 
>>> to docs we moved the docs to its own repo:
>>>
>>> https://git-wip-us.apache.org/repos/asf?p=cloudstack-docs.git
>>>
>>> *I propose that we move away from docbook and use a more readable format: 
>>> restructuredtext*
>>>
>>> I have worked on a prototype that uses restructured text:
>>> http://docutils.sourceforge.net/rst.html
>>>
>>> This format makes it extremely easy to write docs. Existing docbook content 
>>> could be converted to .rst using a tool like pandoc:
>>> http://johnmacfarlane.net/pandoc/
>>>
>>> *In addition to changing the format I propose that we use readthedocs.org*
>>>
>>> This will help with the release and build of the docs. readthedocs grabs 
>>> the docs from a git repo, builds html, pdf and epub.
>>> It can also maintain several releases. We can apply a specific -theme- to 
>>> our docs.
>>>
>>> See a prototype here:
>>>
>>> http://cloudstack.readthedocs.org/en/latest/
>>>
>>> *I propose that we move to this as early as 4.3 documentation*
>>>
>>> Assuming this proposal passes, we would need to:
>>>
>>> -re-architect the repo
>>> -create the proper cnames to be in accordance with trademark guidelines -we 
>>> can decide what content to keep or not and convert what we keep.
>>> -decide how we organize the content
>>> -start accepting pull requests (noting that pages can be edited directly 
>>> from github) -make a first release of this new doc site at the same time 
>>> than 4.3 release.
>>>
>>>
>>> Thoughts, flames ?
>>>
>>>
>>> -Sebastien
>>
>

Build failed in Jenkins: cloudstack-4.3-maven-build #446

[jenkins]

See 

Changes:

[anthony.xu] CLOUDSTACK-5923: CS doesn't do master switch for XS any more, CS 
will depend on XS HA to do master switch, XS HA needs to be enabled.

[Alena Prokharchyk] Changed "authenticate" method to return both - result of 
authentication, and action to perform when authentication failed - to the 
accountManagerImpl. Only if authenicators request 
INCREMENT_INCORRECT_LOGIN_ATTEMPT_COUNT, the incorrect_login_attempts parameter 
will be increased

--
[...truncated 2841 lines...]
[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ 
cloud-plugin-user-authenticator-ldap ---
[INFO] Surefire report directory: 


---
 T E S T S
---

Results :

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

[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Plugin - User Authenticator MD5 4.3.0
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
cloud-plugin-user-authenticator-md5 ---
[INFO] Deleting 

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

 (includes = [target, dist], excludes = [])
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-plugin-user-authenticator-md5 ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-plugin-user-authenticator-md5 ---
[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-md5 ---
[INFO] Compiling 1 source file to 

[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-plugin-user-authenticator-md5 ---
[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-md5 ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ 
cloud-plugin-user-authenticator-md5 ---
[INFO] Surefire report directory: 


---
 T E S T S
---

Results :

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

[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Plugin - User Authenticator Plain Text 4.3.0
[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-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-authentic

Build failed in Jenkins: build-master #100

[jenkins]

See 

Changes:

[Alena Prokharchyk] Changed "authenticate" method to return both - result of 
authentication, and action to perform when authentication failed - to the 
accountManagerImpl. Only if authenicators request 
INCREMENT_INCORRECT_LOGIN_ATTEMPT_COUNT, the incorrect_login_attempts parameter 
will be increased

--
[...truncated 3314 lines...]
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-plugin-user-authenticator-md5 ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-plugin-user-authenticator-md5 ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-plugin-user-authenticator-md5 ---
[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-md5 ---
[INFO] Compiling 1 source file to 

[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-plugin-user-authenticator-md5 ---
[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-md5 ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ 
cloud-plugin-user-authenticator-md5 ---
[INFO] Surefire report directory: 


---
 T E S T S
---

Results :

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

[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Plugin - User Authenticator Plain Text 
4.4.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] 
[INFO] Building Apache CloudStack Plugin - User Au

Build failed in Jenkins: cloudstack-4.3-maven-build #447

[jenkins]

See 

Changes:

[animesh] Pom.xml script updater erroneously removed SNAPSOT from XAPI 
dependency causing build failure

--
[...truncated 2841 lines...]
[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ 
cloud-plugin-user-authenticator-ldap ---
[INFO] Surefire report directory: 


---
 T E S T S
---

Results :

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

[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Plugin - User Authenticator MD5 4.3.0
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
cloud-plugin-user-authenticator-md5 ---
[INFO] Deleting 

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

 (includes = [target, dist], excludes = [])
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-plugin-user-authenticator-md5 ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-plugin-user-authenticator-md5 ---
[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-md5 ---
[INFO] Compiling 1 source file to 

[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-plugin-user-authenticator-md5 ---
[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-md5 ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ 
cloud-plugin-user-authenticator-md5 ---
[INFO] Surefire report directory: 


---
 T E S T S
---

Results :

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

[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Plugin - User Authenticator Plain Text 4.3.0
[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-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:t

Build failed in Jenkins: build-master #101

[jenkins]

See 

Changes:

[anthony.xu] CLOUDSTACK-5923: CS doesn't do master switch for XS any more, CS 
will depend on XS HA to do master switch, XS HA needs to be enabled.

[sheng.yang] CLOUDSTACK-5779: Update vmdata command in Vmware

[anthony.xu] fix build

--
[...truncated 3314 lines...]
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-plugin-user-authenticator-md5 ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-plugin-user-authenticator-md5 ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-plugin-user-authenticator-md5 ---
[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-md5 ---
[INFO] Compiling 1 source file to 

[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-plugin-user-authenticator-md5 ---
[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-md5 ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ 
cloud-plugin-user-authenticator-md5 ---
[INFO] Surefire report directory: 


---
 T E S T S
---

Results :

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

[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Plugin - User Authenticator Plain Text 
4.4.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] 
[INFO] Building Apache CloudStack Plugin - User Authenticator SHA256 Salted 
4.4.0-SNAPSHOT
[INFO] ---

[ACS 43] Do not checkin to 4.3 branch

[Animesh Chaturvedi]

I am building our first RC candidate. Consider 4.3 branch as now locked, if you 
have critical fixes check them into 4.3-forward branch and ask on dev list for 
cherry pick into 4.3 release branch.

Thanks
Animesh

-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
Sent: Tuesday, January 21, 2014 6:04 PM
To: dev@cloudstack.apache.org
Subject: RE: [ACS 4.3] RC update

Now that we are getting ready to build first RC for 4.3. I wanted to call out 
for volunteers  help on updating the Release Notes, Documentation and 
Translations.


Thanks
Animesh

-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
Sent: Tuesday, January 21, 2014 1:41 PM
To: dev@cloudstack.apache.org
Subject: RE: [ACS 4.3] RC update

Folks

I don't see any outstanding blockers, the automation results were also 
published and seemed satisfactory.  I will process with building RC later today 
 I will also pull in few issues that were under discussion in security mailing 
list but later were identified as hardening issues (unencrypted passwords) and 
did not require to go through security process. 


Thanks
Animesh

-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
Sent: Friday, January 10, 2014 10:08 PM
To: dev@cloudstack.apache.org
Subject: RE: [ACS 4.3] RC update

Folks

Today is the scheduled RC date for ACS 4.3 We are very close with just a few 
lingering issues below.



| Jayapal Reddy| CLOUDSTACK-5848 : [Upgrade3.0.6-4.3]"Unable to parse 
VLAN tag" message when network associated with SRX external firewall device is 
rebooted. |
| edison su| CLOUDSTACK-5831 : As regular user , when trying to 
take a snapshot , snapshot succeeds but user is presented with "The given 
command does not exist or it is not available for user" message. |
| Unassigned   | CLOUDSTACK-5743 : Download ROOT Volume when the VM is 
in stopped state is failing with "Forbidden You don't have permission to access 
/userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server" |
| Likitha Shetty   | CLOUDSTACK-5707 : Hitting multiple exceptions when the 
Vsphere client is upgraded to 5.5 from 5.1  
   |
| Daan Hoogland| CLOUDSTACK-5502 : [Automation] createVlanIpRange API 
failing, if you pass VLAN   
 |
| Marcus Sorensen  | CLOUDSTACK-5432 : [Automation] Libvtd getting crashed 
and agent going to alert start  
|
| Sateesh Chodapuneedi | CLOUDSTACK-5408 : [Automation] Failed to deploy vm in 
vmware environment with error "due to java.io.IOException: Cannot run program 
"mount": java.io.IOException: error=12, Cannot allocate memory"   |
| Wei Zhou | CLOUDSTACK-5144 : [Automation]: Basic Zone Security 
Groups - SSH to VM is allowed even when there is no ingress rule defined for 
the security group   |


If you have not played with 4.3 yet please take it for a spin and call out any 
critical issues, I plan to build an RC early next week. 

Thanks
Animesh

-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
Sent: Tuesday, January 07, 2014 10:51 AM
To: dev@cloudstack.apache.org
Subject: [ACS 4.3] RC update

Folks

Happy new year everyone. I hope you all had a good recharging time off during 
holiday. I want to bring our attention and focus to getting the 4.3 release out 
the door. While our scheduled RC date is this Friday 1/10 but we still have 
many open blocker and critical. Please review your backlog of issues and bring 
them to resolution ASAP and provide a "Due Date" in the bug.  We need to 
absolutely make sure upgrades are working. If you encounter upgrade issue 
please file them as blockers. I will escalate all current upgrade issues to 
blocker.

For the most recent release status please visit the 4.3 Release Dashboard [1].  
I am following up on individual issues directly in JIRA so do watch JIRA emails

[1] http://s.apache.org/dFk

Thanks
Animesh

Xapi version in pom.xml updated erroneously

[Animesh Chaturvedi]

While building the ACS 4.3 RC  I ran into the same issue as seen by Abhi for 
4.2.1 

Build_asf.sh messes the XAPI version. I have reopened CLOUDSTACK-4827


>(2) the xapi version in deps/XenServerJava/pom.xml should not be 
>changed when you bump the version from 4.2.1-SNAPSHOT to 4.2.1. (see
>CLOUDSTACK-4827)

Ok, I can see that the build script is trying to revert back the version to 
4.2.1-SNAPSHOT but in the final build the version is not reverted.
Will be checking what is causing that.

-abhi

RE: git commit: updated refs/heads/4.2 to 2b34dc5

[Animesh Chaturvedi]

I ran into this issue again with tools/build/build_asf.sh while building 4.3 
RC. I have gotten around it locally with help from Sheng but do not know what 
it the correct way to fix it. I have reopened CLOUDSTACK-4827

Any help is appreciated 

-Original Message-
From: Wei Zhou [mailto:w.z...@leaseweb.com] 
Sent: Monday, December 16, 2013 2:25 AM
To: Abhinandan Prateek; dev@cloudstack.apache.org
Cc: aprat...@apache.org
Subject: RE: git commit: updated refs/heads/4.2 to 2b34dc5

Abhi, Chips

The issue CLOUDSTACK-4827 happened when one build 4.2 (with xapi-5.6.100-1) if 
compiled 4.1 (with xapi-5.6.100-1-SNAPSHOT) before.

I just tested some times (built 4.1 at first, then 4.2 with xapi-5.6.100-1), 
the issue did not appear. It is weird.
Now I vote +1 on removing -SNAPSHOT as I cannot reproduce it.
If anyone meet this issue later, they can fix it by removing the 
org/apache/cloudstack/xapi/ folder in local maven repository.


Kind Regards,

Wei ZHOU
Innovation Engineer Cloud, LeaseWeb B.V.
w.z...@leaseweb.com

-Original Message-
From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com] 
Sent: zaterdag, 14 december, 2013 04:02
To: dev@cloudstack.apache.org
Cc: aprat...@apache.org; Wei Zhou
Subject: Re: git commit: updated refs/heads/4.2 to 2b34dc5



On 13/12/13 9:20 pm, "Chip Childers"  wrote:
>>
>> >  xapi
>> >  5.6.100-1-SNAPSHOT
>> 
>> The specific project version ^^
>> 
>> For all previous releases, we have been releasing this specific 
>> pom.xml file with the appropriate *non SNAPSHOT* versions for both 
>> the parent version number and the XenServerJava project's version 
>> number (specifically setting the latter to 5.6.100-1).
>> 
>> Since we are releasing the XenServerJava code as part of ACS, why 
>> would we leave the SNAPSHOT in there?
>> 
>> Did something change that requires it to be added back?
>> 
>> -chip
>
>I'll also point out that the reason that this is doing a mv then the 
>perl string changes is that there used to be a bug in the mvn versions 
>plugin that changed the XenServerJava version to the ACS version.  This 
>appears to have been fixed (just tested).  So actually, the mv can be 
>removed or not, it doesn't really matter because it's basically a noop.
>
>However -1 still stands unless someone convinces me that we should 
>release the XenServerJava project with -SNAPSHOT.  IIRC, that actually 
>caused problems for us somehow (but I can't find a reference to that to 
>back up my sometimes fuzzy memory).
>

I was pointed to this ticket CLOUDSTACK-4827. The info is not very clear and it 
appears that this fixes probably a bad version for the repo, and not for the 
build. 

-abhi

>

Re: DHCP entry fails to apply on the latest master

[Jayapal Reddy Uradi]

+users

When ever we see the error 'Unable to contact resource', I suggest to check the 
host agent logs (for xen /var/log/SMlog).
It will give you idea of what is going wrong from the router. Most of times 
there could be script execution failures.

Adding command to clean up tags on xenserver
xe host-param-clear param-name=tags uuid=[uuid]

-Jayapal

On 22-Jan-2014, at 12:49 AM, Alena Prokharchyk  
wrote:

> To fix it, you should cleanup the tags on your xen host, so the MS will
> copy the newest ISO there.
> 
> Sheng, thank you for helping to debug it.
> 
> -Alena.
> 
> On 1/21/14, 11:09 AM, "Nitin Mehta"  wrote:
> 
>> I also face this issue. Here is the snippet of logs. Please let me know if
>> you need any other info.
>> 
>> 2014-01-21 10:52:46,909 INFO  [c.c.v.VirtualMachineManagerImpl]
>> (Job-Executor-1:ctx-57a7ba8c ctx-933fbba1) Unable to contact resource.
>> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1]
>> is unreachable: Unable to apply dhcp entry on router
>>   at 
>> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(Vir
>> t
>> ualNetworkApplianceManagerImpl.java:3826)
>>   at 
>> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEntry
>> (
>> VirtualNetworkApplianceManagerImpl.java:2956)
>>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>   at 
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
>> 3
>> 9)
>>   at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
>> p
>> l.java:25)
>>   at java.lang.reflect.Method.invoke(Method.java:597)
>> 
>> 
>> 
>> 
>> 
>> 
>> On 21/01/14 11:01 AM, "Alena Prokharchyk" 
>> wrote:
>> 
>>> I¹ve deployed the latest master code, re-deployed the DB and uploaded new
>>> system templates with 4.3 version. After that, UserVm fails to start
>>> because DHCP entry fails to apply on the VR.
>>> Its a xen host deployment, and I¹ve tested that ssh to the VR works just
>>> fine. Sheng, can you please take a look? It happened on a couple of
>>> setups.
>>> 
>>> -Alena.
>> 
> 

Re: git commit: updated refs/heads/4.2 to 2b34dc5

[Abhinandan Prateek]

Animesh,

  When you run build_asf script it does the following:

1. Removes the -SNAPSHOT extensions from all version numbers, including
xapi.
2. It creates a commit for this updated pom.xml without the extension.
Generates a tag too.
3. It does all the building stuff etc.
4. Reverses the commit created in 2.

Now if you push the commits, you should see 2 commits: one commit changing
versions and second reverting it, the branch returns to the pre-build
state where ³-SNAPSHOT² is restored.

-abhi

On 22/01/14 10:15 am, "Animesh Chaturvedi" 
wrote:

>I ran into this issue again with tools/build/build_asf.sh while building
>4.3 RC. I have gotten around it locally with help from Sheng but do not
>know what it the correct way to fix it. I have reopened CLOUDSTACK-4827
>
>Any help is appreciated
>
>-Original Message-
>From: Wei Zhou [mailto:w.z...@leaseweb.com]
>Sent: Monday, December 16, 2013 2:25 AM
>To: Abhinandan Prateek; dev@cloudstack.apache.org
>Cc: aprat...@apache.org
>Subject: RE: git commit: updated refs/heads/4.2 to 2b34dc5
>
>Abhi, Chips
>
>The issue CLOUDSTACK-4827 happened when one build 4.2 (with
>xapi-5.6.100-1) if compiled 4.1 (with xapi-5.6.100-1-SNAPSHOT) before.
>
>I just tested some times (built 4.1 at first, then 4.2 with
>xapi-5.6.100-1), the issue did not appear. It is weird.
>Now I vote +1 on removing -SNAPSHOT as I cannot reproduce it.
>If anyone meet this issue later, they can fix it by removing the
>org/apache/cloudstack/xapi/ folder in local maven repository.
>
>
>Kind Regards,
>
>Wei ZHOU
>Innovation Engineer Cloud, LeaseWeb B.V.
>w.z...@leaseweb.com
>
>-Original Message-
>From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com]
>Sent: zaterdag, 14 december, 2013 04:02
>To: dev@cloudstack.apache.org
>Cc: aprat...@apache.org; Wei Zhou
>Subject: Re: git commit: updated refs/heads/4.2 to 2b34dc5
>
>
>
>On 13/12/13 9:20 pm, "Chip Childers"  wrote:
>>>
>>> >  xapi
>>> >  5.6.100-1-SNAPSHOT
>>> 
>>> The specific project version ^^
>>> 
>>> For all previous releases, we have been releasing this specific
>>> pom.xml file with the appropriate *non SNAPSHOT* versions for both
>>> the parent version number and the XenServerJava project's version
>>> number (specifically setting the latter to 5.6.100-1).
>>> 
>>> Since we are releasing the XenServerJava code as part of ACS, why
>>> would we leave the SNAPSHOT in there?
>>> 
>>> Did something change that requires it to be added back?
>>> 
>>> -chip
>>
>>I'll also point out that the reason that this is doing a mv then the
>>perl string changes is that there used to be a bug in the mvn versions
>>plugin that changed the XenServerJava version to the ACS version.  This
>>appears to have been fixed (just tested).  So actually, the mv can be
>>removed or not, it doesn't really matter because it's basically a noop.
>>
>>However -1 still stands unless someone convinces me that we should
>>release the XenServerJava project with -SNAPSHOT.  IIRC, that actually
>>caused problems for us somehow (but I can't find a reference to that to
>>back up my sometimes fuzzy memory).
>>
>
>I was pointed to this ticket CLOUDSTACK-4827. The info is not very clear
>and it appears that this fixes probably a bad version for the repo, and
>not for the build.
>
>-abhi
>
>>
>

Jenkins build is back to normal : cloudstack-4.3-maven-build #448

[jenkins]

See 

Re: Review Request 15247: [DOC] CLOUDSTACK-4967: Add a section to describe VNI allocation matter

[Yoshikazu Nojima]

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

(Updated Jan. 22, 2014, 5:04 a.m.)


Review request for cloudstack, Marcus Sorensen and Toshiaki Hatano.


Changes
---

- keep the section describes the way to use a bridge as a traffic label left.
- fix the typo (XVLAN -> VXLAN)

# So sorry for belated update.


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


Repository: cloudstack-docs


Description
---

This patch updates CloudStack Plugin Guide for the VXLAN Plugin.

- Add a section to describe VNIs allocation matter
- Remove section that explain how to configure the bridge for traffic label 
because the bridge configuration is no longer necessary.
- Update screen shots to catch up new UI visual appearance.


Diffs (updated)
-

  vxlan/en-US/images/vxlan-physicalnetwork.png 
e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
  vxlan/en-US/images/vxlan-trafficlabel.png 
956d5f4f58f592ed3f260d6e1982c238c2ddf06a 
  vxlan/en-US/images/vxlan-vniconfig.png PRE-CREATION 
  vxlan/en-US/plugin-vxlan-config-hypervisor.xml 2c5e138 
  vxlan/en-US/plugin-vxlan-config-management.xml 21f5461 
  vxlan/en-US/plugin-vxlan-revision-history.xml ec04d11 

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


Testing
---

I generated and confirmed the PDF.


Thanks,

Yoshikazu Nojima

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

[jenkins]

See 

Re: Review Request 17120: added an extra column to mark the imported ldap users as from ldap

[Rajani Karuturi]

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

(Updated Jan. 22, 2014, 5:05 a.m.)


Review request for cloudstack, Abhinandan Prateek, Ian Duffy, Min Chen, and 
Prachi Damle.


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


Repository: cloudstack-git


Description
---

added an extra column to mark the imported ldap users as from ldap


Diffs
-

  api/src/com/cloud/user/AccountService.java 8153a3f 
  api/src/com/cloud/user/User.java dcf27a0 
  engine/schema/src/com/cloud/user/UserVO.java 2a85758 
  
plugins/dedicated-resources/test/org/apache/cloudstack/dedicated/manager/DedicatedApiUnitTest.java
 f2803b1 
  
plugins/deployment-planners/implicit-dedication/test/org/apache/cloudstack/implicitplanner/ImplicitPlannerTest.java
 24368ee 
  
plugins/hypervisors/vmware/test/com/cloud/hypervisor/vmware/VmwareDatacenterApiUnitTest.java
 cdd883a 
  
plugins/network-elements/juniper-contrail/test/org/apache/cloudstack/network/contrail/management/MockAccountManager.java
 195e932 
  
plugins/user-authenticators/ldap/src/org/apache/cloudstack/api/command/LdapCreateAccountCmd.java
 981e72e 
  
plugins/user-authenticators/ldap/src/org/apache/cloudstack/api/command/LdapImportUsersCmd.java
 1855d5d 
  server/src/com/cloud/user/AccountManagerImpl.java 0655f8c 
  server/test/com/cloud/configuration/ConfigurationManagerTest.java 2d2c03d 
  server/test/com/cloud/network/DedicateGuestVlanRangesTest.java ea7167b 
  server/test/com/cloud/user/MockAccountManagerImpl.java 38cc1a84 
  server/test/com/cloud/vm/UserVmManagerTest.java 34090ef 
  server/test/com/cloud/vpc/NetworkACLManagerTest.java 42619b2 
  server/test/com/cloud/vpc/NetworkACLServiceTest.java b17491a 
  server/test/org/apache/cloudstack/affinity/AffinityApiUnitTest.java 91d6958 
  server/test/org/apache/cloudstack/network/lb/CertServiceTest.java a37e626 
  
server/test/org/apache/cloudstack/region/gslb/GlobalLoadBalancingRulesServiceImplTest.java
 504ab9c 
  setup/db/db/schema-421to430.sql 8bfec37 

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


Testing
---

manually tested


Thanks,

Rajani Karuturi

Re: git commit: updated refs/heads/4.2 to 2b34dc5

[Abhinandan Prateek]

I looked at 4.3-forward and it seems the revert commit is missing. That is
why the “SNAPSHOT” extension is not restored.

On 22/01/14 10:31 am, "Abhinandan Prateek" 
wrote:

>Animesh,
>
>  When you run build_asf script it does the following:
>
>1. Removes the -SNAPSHOT extensions from all version numbers, including
>xapi.
>2. It creates a commit for this updated pom.xml without the extension.
>Generates a tag too.
>3. It does all the building stuff etc.
>4. Reverses the commit created in 2.
>
>Now if you push the commits, you should see 2 commits: one commit changing
>versions and second reverting it, the branch returns to the pre-build
>state where ³-SNAPSHOT² is restored.
>
>-abhi
>
>On 22/01/14 10:15 am, "Animesh Chaturvedi" 
>wrote:
>
>>I ran into this issue again with tools/build/build_asf.sh while building
>>4.3 RC. I have gotten around it locally with help from Sheng but do not
>>know what it the correct way to fix it. I have reopened CLOUDSTACK-4827
>>
>>Any help is appreciated
>>
>>-Original Message-
>>From: Wei Zhou [mailto:w.z...@leaseweb.com]
>>Sent: Monday, December 16, 2013 2:25 AM
>>To: Abhinandan Prateek; dev@cloudstack.apache.org
>>Cc: aprat...@apache.org
>>Subject: RE: git commit: updated refs/heads/4.2 to 2b34dc5
>>
>>Abhi, Chips
>>
>>The issue CLOUDSTACK-4827 happened when one build 4.2 (with
>>xapi-5.6.100-1) if compiled 4.1 (with xapi-5.6.100-1-SNAPSHOT) before.
>>
>>I just tested some times (built 4.1 at first, then 4.2 with
>>xapi-5.6.100-1), the issue did not appear. It is weird.
>>Now I vote +1 on removing -SNAPSHOT as I cannot reproduce it.
>>If anyone meet this issue later, they can fix it by removing the
>>org/apache/cloudstack/xapi/ folder in local maven repository.
>>
>>
>>Kind Regards,
>>
>>Wei ZHOU
>>Innovation Engineer Cloud, LeaseWeb B.V.
>>w.z...@leaseweb.com
>>
>>-Original Message-
>>From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com]
>>Sent: zaterdag, 14 december, 2013 04:02
>>To: dev@cloudstack.apache.org
>>Cc: aprat...@apache.org; Wei Zhou
>>Subject: Re: git commit: updated refs/heads/4.2 to 2b34dc5
>>
>>
>>
>>On 13/12/13 9:20 pm, "Chip Childers"  wrote:

 >  xapi
 >  5.6.100-1-SNAPSHOT
 
 The specific project version ^^
 
 For all previous releases, we have been releasing this specific
 pom.xml file with the appropriate *non SNAPSHOT* versions for both
 the parent version number and the XenServerJava project's version
 number (specifically setting the latter to 5.6.100-1).
 
 Since we are releasing the XenServerJava code as part of ACS, why
 would we leave the SNAPSHOT in there?
 
 Did something change that requires it to be added back?
 
 -chip
>>>
>>>I'll also point out that the reason that this is doing a mv then the
>>>perl string changes is that there used to be a bug in the mvn versions
>>>plugin that changed the XenServerJava version to the ACS version.  This
>>>appears to have been fixed (just tested).  So actually, the mv can be
>>>removed or not, it doesn't really matter because it's basically a noop.
>>>
>>>However -1 still stands unless someone convinces me that we should
>>>release the XenServerJava project with -SNAPSHOT.  IIRC, that actually
>>>caused problems for us somehow (but I can't find a reference to that to
>>>back up my sometimes fuzzy memory).
>>>
>>
>>I was pointed to this ticket CLOUDSTACK-4827. The info is not very clear
>>and it appears that this fixes probably a bad version for the repo, and
>>not for the build.
>>
>>-abhi
>>
>>>
>>
>

RE: git commit: updated refs/heads/4.2 to 2b34dc5

[Animesh Chaturvedi]

That seems kludgy we need an elegant solution

-Original Message-
From: Abhinandan Prateek 
Sent: Tuesday, January 21, 2014 9:11 PM
To: dev@cloudstack.apache.org
Cc: Animesh Chaturvedi
Subject: Re: git commit: updated refs/heads/4.2 to 2b34dc5

I looked at 4.3-forward and it seems the revert commit is missing. That is why 
the "SNAPSHOT" extension is not restored.

On 22/01/14 10:31 am, "Abhinandan Prateek" 
wrote:

>Animesh,
>
>  When you run build_asf script it does the following:
>
>1. Removes the -SNAPSHOT extensions from all version numbers, including 
>xapi.
>2. It creates a commit for this updated pom.xml without the extension.
>Generates a tag too.
>3. It does all the building stuff etc.
>4. Reverses the commit created in 2.
>
>Now if you push the commits, you should see 2 commits: one commit 
>changing versions and second reverting it, the branch returns to the 
>pre-build state where ³-SNAPSHOT² is restored.
>
>-abhi
>
>On 22/01/14 10:15 am, "Animesh Chaturvedi" 
>
>wrote:
>
>>I ran into this issue again with tools/build/build_asf.sh while 
>>building
>>4.3 RC. I have gotten around it locally with help from Sheng but do 
>>not know what it the correct way to fix it. I have reopened 
>>CLOUDSTACK-4827
>>
>>Any help is appreciated
>>
>>-Original Message-
>>From: Wei Zhou [mailto:w.z...@leaseweb.com]
>>Sent: Monday, December 16, 2013 2:25 AM
>>To: Abhinandan Prateek; dev@cloudstack.apache.org
>>Cc: aprat...@apache.org
>>Subject: RE: git commit: updated refs/heads/4.2 to 2b34dc5
>>
>>Abhi, Chips
>>
>>The issue CLOUDSTACK-4827 happened when one build 4.2 (with
>>xapi-5.6.100-1) if compiled 4.1 (with xapi-5.6.100-1-SNAPSHOT) before.
>>
>>I just tested some times (built 4.1 at first, then 4.2 with 
>>xapi-5.6.100-1), the issue did not appear. It is weird.
>>Now I vote +1 on removing -SNAPSHOT as I cannot reproduce it.
>>If anyone meet this issue later, they can fix it by removing the 
>>org/apache/cloudstack/xapi/ folder in local maven repository.
>>
>>
>>Kind Regards,
>>
>>Wei ZHOU
>>Innovation Engineer Cloud, LeaseWeb B.V.
>>w.z...@leaseweb.com
>>
>>-Original Message-
>>From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com]
>>Sent: zaterdag, 14 december, 2013 04:02
>>To: dev@cloudstack.apache.org
>>Cc: aprat...@apache.org; Wei Zhou
>>Subject: Re: git commit: updated refs/heads/4.2 to 2b34dc5
>>
>>
>>
>>On 13/12/13 9:20 pm, "Chip Childers"  wrote:

 >  xapi
 >  5.6.100-1-SNAPSHOT
 
 The specific project version ^^
 
 For all previous releases, we have been releasing this specific 
 pom.xml file with the appropriate *non SNAPSHOT* versions for both 
 the parent version number and the XenServerJava project's version 
 number (specifically setting the latter to 5.6.100-1).
 
 Since we are releasing the XenServerJava code as part of ACS, why 
 would we leave the SNAPSHOT in there?
 
 Did something change that requires it to be added back?
 
 -chip
>>>
>>>I'll also point out that the reason that this is doing a mv then the 
>>>perl string changes is that there used to be a bug in the mvn 
>>>versions plugin that changed the XenServerJava version to the ACS 
>>>version.  This appears to have been fixed (just tested).  So 
>>>actually, the mv can be removed or not, it doesn't really matter because 
>>>it's basically a noop.
>>>
>>>However -1 still stands unless someone convinces me that we should 
>>>release the XenServerJava project with -SNAPSHOT.  IIRC, that 
>>>actually caused problems for us somehow (but I can't find a reference 
>>>to that to back up my sometimes fuzzy memory).
>>>
>>
>>I was pointed to this ticket CLOUDSTACK-4827. The info is not very 
>>clear and it appears that this fixes probably a bad version for the 
>>repo, and not for the build.
>>
>>-abhi
>>
>>>
>>
>

Re: git commit: updated refs/heads/4.2 to 2b34dc5

[Abhinandan Prateek]

One solution was given by Dan where he suggested that for RC we create a
branch. That I guess is still in review board.

-abhi

On 22/01/14 10:42 am, "Animesh Chaturvedi" 
wrote:

>That seems kludgy we need an elegant solution
>
>-Original Message-
>From: Abhinandan Prateek
>Sent: Tuesday, January 21, 2014 9:11 PM
>To: dev@cloudstack.apache.org
>Cc: Animesh Chaturvedi
>Subject: Re: git commit: updated refs/heads/4.2 to 2b34dc5
>
>I looked at 4.3-forward and it seems the revert commit is missing. That
>is why the “SNAPSHOT” extension is not restored.
>
>On 22/01/14 10:31 am, "Abhinandan Prateek" 
>wrote:
>
>>Animesh,
>>
>>  When you run build_asf script it does the following:
>>
>>1. Removes the -SNAPSHOT extensions from all version numbers, including
>>xapi.
>>2. It creates a commit for this updated pom.xml without the extension.
>>Generates a tag too.
>>3. It does all the building stuff etc.
>>4. Reverses the commit created in 2.
>>
>>Now if you push the commits, you should see 2 commits: one commit
>>changing versions and second reverting it, the branch returns to the
>>pre-build state where ³-SNAPSHOT² is restored.
>>
>>-abhi
>>
>>On 22/01/14 10:15 am, "Animesh Chaturvedi"
>>
>>wrote:
>>
>>>I ran into this issue again with tools/build/build_asf.sh while
>>>building
>>>4.3 RC. I have gotten around it locally with help from Sheng but do
>>>not know what it the correct way to fix it. I have reopened
>>>CLOUDSTACK-4827
>>>
>>>Any help is appreciated
>>>
>>>-Original Message-
>>>From: Wei Zhou [mailto:w.z...@leaseweb.com]
>>>Sent: Monday, December 16, 2013 2:25 AM
>>>To: Abhinandan Prateek; dev@cloudstack.apache.org
>>>Cc: aprat...@apache.org
>>>Subject: RE: git commit: updated refs/heads/4.2 to 2b34dc5
>>>
>>>Abhi, Chips
>>>
>>>The issue CLOUDSTACK-4827 happened when one build 4.2 (with
>>>xapi-5.6.100-1) if compiled 4.1 (with xapi-5.6.100-1-SNAPSHOT) before.
>>>
>>>I just tested some times (built 4.1 at first, then 4.2 with
>>>xapi-5.6.100-1), the issue did not appear. It is weird.
>>>Now I vote +1 on removing -SNAPSHOT as I cannot reproduce it.
>>>If anyone meet this issue later, they can fix it by removing the
>>>org/apache/cloudstack/xapi/ folder in local maven repository.
>>>
>>>
>>>Kind Regards,
>>>
>>>Wei ZHOU
>>>Innovation Engineer Cloud, LeaseWeb B.V.
>>>w.z...@leaseweb.com
>>>
>>>-Original Message-
>>>From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com]
>>>Sent: zaterdag, 14 december, 2013 04:02
>>>To: dev@cloudstack.apache.org
>>>Cc: aprat...@apache.org; Wei Zhou
>>>Subject: Re: git commit: updated refs/heads/4.2 to 2b34dc5
>>>
>>>
>>>
>>>On 13/12/13 9:20 pm, "Chip Childers"  wrote:
>
> >  xapi
> >  5.6.100-1-SNAPSHOT
> 
> The specific project version ^^
> 
> For all previous releases, we have been releasing this specific
> pom.xml file with the appropriate *non SNAPSHOT* versions for both
> the parent version number and the XenServerJava project's version
> number (specifically setting the latter to 5.6.100-1).
> 
> Since we are releasing the XenServerJava code as part of ACS, why
> would we leave the SNAPSHOT in there?
> 
> Did something change that requires it to be added back?
> 
> -chip

I'll also point out that the reason that this is doing a mv then the
perl string changes is that there used to be a bug in the mvn
versions plugin that changed the XenServerJava version to the ACS
version.  This appears to have been fixed (just tested).  So
actually, the mv can be removed or not, it doesn't really matter
because it's basically a noop.

However -1 still stands unless someone convinces me that we should
release the XenServerJava project with -SNAPSHOT.  IIRC, that
actually caused problems for us somehow (but I can't find a reference
to that to back up my sometimes fuzzy memory).

>>>
>>>I was pointed to this ticket CLOUDSTACK-4827. The info is not very
>>>clear and it appears that this fixes probably a bad version for the
>>>repo, and not for the build.
>>>
>>>-abhi
>>>

>>>
>>
>

Re: Review Request 15247: [DOC] CLOUDSTACK-4967: Add a section to describe VNI allocation matter

[Yoshikazu Nojima]

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

(Updated Jan. 22, 2014, 5:44 a.m.)


Review request for cloudstack, Marcus Sorensen and Toshiaki Hatano.


Changes
---

- update Linux distribution list to include CentOS 6.5


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


Repository: cloudstack-docs


Description
---

This patch updates CloudStack Plugin Guide for the VXLAN Plugin.

- Add a section to describe VNIs allocation matter
- Remove section that explain how to configure the bridge for traffic label 
because the bridge configuration is no longer necessary.
- Update screen shots to catch up new UI visual appearance.


Diffs (updated)
-

  vxlan/en-US/images/vxlan-physicalnetwork.png 
e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
  vxlan/en-US/images/vxlan-trafficlabel.png 
956d5f4f58f592ed3f260d6e1982c238c2ddf06a 
  vxlan/en-US/images/vxlan-vniconfig.png PRE-CREATION 
  vxlan/en-US/plugin-vxlan-config-hypervisor.xml 2c5e138 
  vxlan/en-US/plugin-vxlan-config-management.xml 21f5461 
  vxlan/en-US/plugin-vxlan-requirements.xml c2e04a6 
  vxlan/en-US/plugin-vxlan-revision-history.xml ec04d11 

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


Testing
---

I generated and confirmed the PDF.


Thanks,

Yoshikazu Nojima

Re: VmWare SDK to vijava

[Hugo Trippaers]

Kelven, Chiradeep,

What license governs the redistribution, what do we include in our notice file 
and is that license compatible with the ASF license policy?

Hugo

Sent from my iPhone

> On 22 jan. 2014, at 00:44, Kelven Yang  wrote:
> 
> Q. Can I redistribute the VI SDK libraries and sample code?
> A. You can redistribute only those parts of the SDK package that have been
> designated as ³distributable code².
> In VI SDK 2.5, the following components can be redistributed: vim.jar,
> vim25.jar. To note developers typically generate web service stubs from
> the WSDL file that is included in the VI SDK using a SOAP toolkit.
> 
>>> The stubs source and the compiled stubs can also be distributed.
> 
> 
> Could this solve our license problem, we discussed before that generating
> our own java stub can give us flexibility to support co-existence of
> different versions of VMware web service API inside CloudStack.
> 
> If we see this as urgency, we need to have someone work on to put WSDL
> generation process to maven build
> 
> For latest names of VI SDK libraries that can be redistributed visit
> http://vmware.com/go/sdk-redistribution-info
> 
> 
> 
> On 1/21/14, 3:18 PM, "Chiradeep Vittal" 
> wrote:
> 
>> Apparently we can 
>> https://communities.vmware.com/docs/DOC-7983
>> http://markmail.org/thread/ttamcfb4d6azzbw7
>> 
>> 
>>> On 1/21/14 2:46 PM, "Hugo Trippaers"  wrote:
>>> 
>>> Chiradeep,
>>> 
>>> Even on the generated sources nobody seems willing to state that it is ok
>>> to include them at the moment. Otherwise I would have put them in
>>> already.
>>> 
>>> Hugo
>>> 
>>> Sent from my iPhone
>>> 
 On 21 jan. 2014, at 19:32, Chiradeep Vittal
  wrote:
 
 Suboptimal for?
 Wouldn't the ACS user want the best / supported client libraries?
 Alternatively, can't we just compile the WSDL and check in the
 generated
 sources? Not check-in the WSDL, but the client sources.
 
> On 1/21/14 7:18 AM, "David Nalley"  wrote:
> 
> On Tue, Jan 21, 2014 at 9:46 AM, Chip Childers
> 
> wrote:
>> I bet we never got an answer. Frankly, I'd like to see us use
>> something where the licensing is clear.  That, or we don't include
>> the
>> WSDL in our repo / distro.
> 
> Additionally, we are an open source project that is in the business of
> producing open source software. Depending on non-free and
> non-opensource libraries is suboptimal, but its worse when there is a
> open source alternative.
> 
> --David
> 

Re: VmWare SDK to vijava

[Hugo Trippaers]

We are now again at the exact same point as where Darren was.

This is the legal ticket relevant to the license discussion: 
https://issues.apache.org/jira/plugins/servlet/mobile#issue/LEGAL-180

Either we get an ok from legal or we need to find an alternative. Kelven, 
Chiradeep, are you guys going to chase this ticket?

Hugo

Sent from my iPhone

> On 22 jan. 2014, at 07:04, "Hugo Trippaers"  wrote:
> 
> Kelven, Chiradeep,
> 
> What license governs the redistribution, what do we include in our notice 
> file and is that license compatible with the ASF license policy?
> 
> Hugo
> 
> Sent from my iPhone
> 
>> On 22 jan. 2014, at 00:44, Kelven Yang  wrote:
>> 
>> Q. Can I redistribute the VI SDK libraries and sample code?
>> A. You can redistribute only those parts of the SDK package that have been
>> designated as ³distributable code².
>> In VI SDK 2.5, the following components can be redistributed: vim.jar,
>> vim25.jar. To note developers typically generate web service stubs from
>> the WSDL file that is included in the VI SDK using a SOAP toolkit.
>> 
 The stubs source and the compiled stubs can also be distributed.
>> 
>> 
>> Could this solve our license problem, we discussed before that generating
>> our own java stub can give us flexibility to support co-existence of
>> different versions of VMware web service API inside CloudStack.
>> 
>> If we see this as urgency, we need to have someone work on to put WSDL
>> generation process to maven build
>> 
>> For latest names of VI SDK libraries that can be redistributed visit
>> http://vmware.com/go/sdk-redistribution-info
>> 
>> 
>> 
>> On 1/21/14, 3:18 PM, "Chiradeep Vittal" 
>> wrote:
>> 
>>> Apparently we can 
>>> https://communities.vmware.com/docs/DOC-7983
>>> http://markmail.org/thread/ttamcfb4d6azzbw7
>>> 
>>> 
 On 1/21/14 2:46 PM, "Hugo Trippaers"  wrote:
 
 Chiradeep,
 
 Even on the generated sources nobody seems willing to state that it is ok
 to include them at the moment. Otherwise I would have put them in
 already.
 
 Hugo
 
 Sent from my iPhone
 
> On 21 jan. 2014, at 19:32, Chiradeep Vittal
>  wrote:
> 
> Suboptimal for?
> Wouldn't the ACS user want the best / supported client libraries?
> Alternatively, can't we just compile the WSDL and check in the
> generated
> sources? Not check-in the WSDL, but the client sources.
> 
>> On 1/21/14 7:18 AM, "David Nalley"  wrote:
>> 
>> On Tue, Jan 21, 2014 at 9:46 AM, Chip Childers
>> 
>> wrote:
>>> I bet we never got an answer. Frankly, I'd like to see us use
>>> something where the licensing is clear.  That, or we don't include
>>> the
>>> WSDL in our repo / distro.
>> 
>> Additionally, we are an open source project that is in the business of
>> producing open source software. Depending on non-free and
>> non-opensource libraries is suboptimal, but its worse when there is a
>> open source alternative.
>> 
>> --David
>> 

Re: xentools on systemvmtemplate not visible to xen

[Abhinandan Prateek]

I think the question we should be asking is if everything seems to work
fine with current templates, do we really need xentools on systemVMS.

On 22/01/14 12:57 am, "Chiradeep Vittal" 
wrote:

>I was under the impression that they actually get in the way of live
>migration and XS upgrades because then XS gets to be finicky about
>supported OS and such.
>
>On 1/21/14 5:56 AM, "Hugo Trippaers"  wrote:
>
>>Hey Abhi,
>>
>>i don¹t think the xentools are installed. At least they are not in the
>>postinstall.sh
>>
>>Cheers,
>>Hugo
>>
>>
>>On 21 jan. 2014, at 12:27, Abhinandan Prateek
>> wrote:
>>
>>> The xentools are installed on systemvm templates but still xenserver is
>>>unable to recognise those.
>>> There was discussion on this sometime back and it did not get
>>>concluded.
>>> If someone knows the steps to make the xentoosl visible to xen, please
>>>chime in.
>>> It may be that we just need to start the daemon process that informs
>>>xen of the tools ?
>>> 
>>> -abhi
>>
>

Re: Review Request 17113: Phase1 Marvin Changes.Fix-for-CLOUDSTACK-5674, 5498, 5500

[ASF Subversion and Git Services]

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


Commit 939327561192eba7f21f6d5acb0119278984b510 in branch refs/heads/marvin 
from Santhosh Edukulla
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9393275 ]

CLOUDSTACK-5674: Added Fix for CLOUDSTACK-5674,5498,5500 and other issues as
 part of cleanup


- ASF Subversion and Git Services


On Jan. 20, 2014, 8:42 a.m., Santhosh Edukulla wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/17113/
> ---
> 
> (Updated Jan. 20, 2014, 8:42 a.m.)
> 
> 
> Review request for cloudstack and Girish Shilamkar.
> 
> 
> Bugs: CLOUDSTACK-5498, CLOUDSTACK-5500 and CLOUDSTACK-5674
> https://issues.apache.org/jira/browse/CLOUDSTACK-5498
> https://issues.apache.org/jira/browse/CLOUDSTACK-5500
> https://issues.apache.org/jira/browse/CLOUDSTACK-5674
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> 1. Added-Fix-for-CLOUDSTACK-5674,5498,5500-and other changes mentioned @ the 
> link below: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Phase1%3A+Marvin+Changes
> 
> 2. The changes and the patch need to be applied to separate topic branch 
> created for Marvin.
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/marvin
> 
> 3. Few more changes pending for tests suites need to be done and will  call 
> for a merge to main
> branches post that. 
> 
> Girish,
> 
> As discussed, submitted the patch. This patch needs to be applied "only" to 
> new topic branch created.
> 
> 
> Diffs
> -
> 
>   setup/dev/advanced.cfg 23981f0 
>   setup/dev/basic.cfg 3e39d6d 
>   test/integration/component/test_add_remove_network.py 8ec2971 
>   test/integration/component/test_affinity_groups.py 7e4fabe 
>   test/integration/component/test_cpu_domain_limits.py c427e4f 
>   test/integration/component/test_cpu_limits.py bdf2869 
>   test/integration/component/test_cpu_max_limits.py 317df16 
>   test/integration/component/test_cpu_project_limits.py a8a1b3c 
>   test/integration/component/test_memory_limits.py 7921e4b 
>   test/integration/component/test_mm_domain_limits.py 68660c1 
>   test/integration/component/test_mm_max_limits.py e10c119 
>   test/integration/component/test_mm_project_limits.py c314011 
>   test/integration/component/test_portable_ip.py b09daf9 
>   test/integration/component/test_vpc.py 1af8d81 
>   test/integration/component/test_vpn_users.py 02dd026 
>   test/integration/smoke/test_affinity_groups.py c96a580 
>   test/integration/smoke/test_deploy_vm.py 425aeb7 
>   test/integration/smoke/test_deploy_vm_with_userdata.py e3788cf 
>   tools/marvin/marvin/asyncJobMgr.py ee0e891 
>   tools/marvin/marvin/cloudstackConnection.py fb03e3b 
>   tools/marvin/marvin/cloudstackException.py 623 
>   tools/marvin/marvin/cloudstackTestClient.py 4ac510b 
>   tools/marvin/marvin/codegenerator.py e0f056f 
>   tools/marvin/marvin/codes.py 74fb05d 
>   tools/marvin/marvin/config/test_data.cfg PRE-CREATION 
>   tools/marvin/marvin/configGenerator.py 0d79e8e 
>   tools/marvin/marvin/dbConnection.py 99014ab 
>   tools/marvin/marvin/deployDataCenter.py c4f6e1e 
>   tools/marvin/marvin/integration/lib/common.py 550de1a 
>   tools/marvin/marvin/jsonHelper.py ae40b8d 
>   tools/marvin/marvin/marvinInit.py f722058 
>   tools/marvin/marvin/marvinLog.py 76de185 
>   tools/marvin/marvin/marvinPlugin.py df7d7a3 
>   tools/marvin/marvin/tcExecuteEngine.py f959e7e 
> 
> Diff: https://reviews.apache.org/r/17113/diff/
> 
> 
> Testing
> ---
> 
> Few more changes pending for tests suites need to be done and will  call for 
> a merge to main
> branches post that. 
> 
> 
> Thanks,
> 
> Santhosh Edukulla
> 
>

Re: Review Request 17113: Phase1 Marvin Changes.Fix-for-CLOUDSTACK-5674, 5498, 5500

[ASF Subversion and Git Services]

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


Commit 939327561192eba7f21f6d5acb0119278984b510 in branch refs/heads/marvin 
from Santhosh Edukulla
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9393275 ]

CLOUDSTACK-5674: Added Fix for CLOUDSTACK-5674,5498,5500 and other issues as
 part of cleanup


- ASF Subversion and Git Services


On Jan. 20, 2014, 8:42 a.m., Santhosh Edukulla wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/17113/
> ---
> 
> (Updated Jan. 20, 2014, 8:42 a.m.)
> 
> 
> Review request for cloudstack and Girish Shilamkar.
> 
> 
> Bugs: CLOUDSTACK-5498, CLOUDSTACK-5500 and CLOUDSTACK-5674
> https://issues.apache.org/jira/browse/CLOUDSTACK-5498
> https://issues.apache.org/jira/browse/CLOUDSTACK-5500
> https://issues.apache.org/jira/browse/CLOUDSTACK-5674
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> 1. Added-Fix-for-CLOUDSTACK-5674,5498,5500-and other changes mentioned @ the 
> link below: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Phase1%3A+Marvin+Changes
> 
> 2. The changes and the patch need to be applied to separate topic branch 
> created for Marvin.
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/marvin
> 
> 3. Few more changes pending for tests suites need to be done and will  call 
> for a merge to main
> branches post that. 
> 
> Girish,
> 
> As discussed, submitted the patch. This patch needs to be applied "only" to 
> new topic branch created.
> 
> 
> Diffs
> -
> 
>   setup/dev/advanced.cfg 23981f0 
>   setup/dev/basic.cfg 3e39d6d 
>   test/integration/component/test_add_remove_network.py 8ec2971 
>   test/integration/component/test_affinity_groups.py 7e4fabe 
>   test/integration/component/test_cpu_domain_limits.py c427e4f 
>   test/integration/component/test_cpu_limits.py bdf2869 
>   test/integration/component/test_cpu_max_limits.py 317df16 
>   test/integration/component/test_cpu_project_limits.py a8a1b3c 
>   test/integration/component/test_memory_limits.py 7921e4b 
>   test/integration/component/test_mm_domain_limits.py 68660c1 
>   test/integration/component/test_mm_max_limits.py e10c119 
>   test/integration/component/test_mm_project_limits.py c314011 
>   test/integration/component/test_portable_ip.py b09daf9 
>   test/integration/component/test_vpc.py 1af8d81 
>   test/integration/component/test_vpn_users.py 02dd026 
>   test/integration/smoke/test_affinity_groups.py c96a580 
>   test/integration/smoke/test_deploy_vm.py 425aeb7 
>   test/integration/smoke/test_deploy_vm_with_userdata.py e3788cf 
>   tools/marvin/marvin/asyncJobMgr.py ee0e891 
>   tools/marvin/marvin/cloudstackConnection.py fb03e3b 
>   tools/marvin/marvin/cloudstackException.py 623 
>   tools/marvin/marvin/cloudstackTestClient.py 4ac510b 
>   tools/marvin/marvin/codegenerator.py e0f056f 
>   tools/marvin/marvin/codes.py 74fb05d 
>   tools/marvin/marvin/config/test_data.cfg PRE-CREATION 
>   tools/marvin/marvin/configGenerator.py 0d79e8e 
>   tools/marvin/marvin/dbConnection.py 99014ab 
>   tools/marvin/marvin/deployDataCenter.py c4f6e1e 
>   tools/marvin/marvin/integration/lib/common.py 550de1a 
>   tools/marvin/marvin/jsonHelper.py ae40b8d 
>   tools/marvin/marvin/marvinInit.py f722058 
>   tools/marvin/marvin/marvinLog.py 76de185 
>   tools/marvin/marvin/marvinPlugin.py df7d7a3 
>   tools/marvin/marvin/tcExecuteEngine.py f959e7e 
> 
> Diff: https://reviews.apache.org/r/17113/diff/
> 
> 
> Testing
> ---
> 
> Few more changes pending for tests suites need to be done and will  call for 
> a merge to main
> branches post that. 
> 
> 
> Thanks,
> 
> Santhosh Edukulla
> 
>

Re: Review Request 17116: Phase1 Marvin Changes.Fix-for-CLOUDSTACK-5674, 5498, 5500( Fixed Few issues in patch 17113 )

[Girish Shilamkar]

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


Santhosh,

This patch seems to be the updated version of 17113. We will need a patch which 
will apply on top of 17113.
Could you please fetch the marvin branch and create the patch. 

Thanks,
Girish

- Girish Shilamkar


On Jan. 20, 2014, 9:26 a.m., Santhosh Edukulla wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/17116/
> ---
> 
> (Updated Jan. 20, 2014, 9:26 a.m.)
> 
> 
> Review request for cloudstack and Girish Shilamkar.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fixed few issues including pep8 in previous submitted patch ( 17113 ). Tested 
> Deploying a DC. 
> 
> 
> Diffs
> -
> 
>   setup/dev/advanced.cfg 23981f0 
>   setup/dev/basic.cfg 3e39d6d 
>   test/integration/component/test_add_remove_network.py 8ec2971 
>   test/integration/component/test_affinity_groups.py 7e4fabe 
>   test/integration/component/test_cpu_domain_limits.py c427e4f 
>   test/integration/component/test_cpu_limits.py bdf2869 
>   test/integration/component/test_cpu_max_limits.py 317df16 
>   test/integration/component/test_cpu_project_limits.py a8a1b3c 
>   test/integration/component/test_memory_limits.py 7921e4b 
>   test/integration/component/test_mm_domain_limits.py 68660c1 
>   test/integration/component/test_mm_max_limits.py e10c119 
>   test/integration/component/test_mm_project_limits.py c314011 
>   test/integration/component/test_portable_ip.py b09daf9 
>   test/integration/component/test_vpc.py 1af8d81 
>   test/integration/component/test_vpn_users.py 02dd026 
>   test/integration/smoke/test_affinity_groups.py c96a580 
>   test/integration/smoke/test_deploy_vm.py 425aeb7 
>   test/integration/smoke/test_deploy_vm_with_userdata.py e3788cf 
>   tools/marvin/marvin/asyncJobMgr.py ee0e891 
>   tools/marvin/marvin/cloudstackConnection.py fb03e3b 
>   tools/marvin/marvin/cloudstackException.py 623 
>   tools/marvin/marvin/cloudstackTestClient.py 4ac510b 
>   tools/marvin/marvin/codegenerator.py e0f056f 
>   tools/marvin/marvin/codes.py 74fb05d 
>   tools/marvin/marvin/config/test_data.cfg PRE-CREATION 
>   tools/marvin/marvin/configGenerator.py 0d79e8e 
>   tools/marvin/marvin/dbConnection.py 99014ab 
>   tools/marvin/marvin/deployDataCenter.py c4f6e1e 
>   tools/marvin/marvin/integration/lib/common.py 550de1a 
>   tools/marvin/marvin/jsonHelper.py ae40b8d 
>   tools/marvin/marvin/marvinInit.py f722058 
>   tools/marvin/marvin/marvinLog.py 76de185 
>   tools/marvin/marvin/marvinPlugin.py df7d7a3 
>   tools/marvin/marvin/tcExecuteEngine.py f959e7e 
> 
> Diff: https://reviews.apache.org/r/17116/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Santhosh Edukulla
> 
>

snapshot releases for checkstyle and xapi

[Hugo Trippaers]

Hey,

pulling this into a separate discussion from the release discussion.

The idea with -SNAPSHOT releases is that maven knows that this version is under 
active development and it should always try to download a more recent build. 
Hence in your master branch all releases will be tagged with SNAPSHOT. However 
this doesn’t mean that we have to depend on these particular snapshot versions 
in other parts of the code. In fact in our case it might be a better idea to 
put a stable version of both xapi and checkstyle in the maven repository and 
depend on those versions.

My proposal would be to build and distribute (to the apache maven repo) version 
xapi 5.6.100-1 and checkstyle 1.0.0 as stable versions. Update the dependencies 
in the other poms to those particular versions. Then update the master branch 
and set the module version to version 5.6.100-2-SNAPSHOT on xapi and 
1.1.0-SNAPSHOT on checkstyle. That way all parts of cloudstack would still 
reference the stable version of those projects (including the master branch). 
If we ever need to update we can change master to point to the snapshot 
version, update and release.

Cheers,

Hugo 

Re: Review Request 17120: added an extra column to mark the imported ldap users as from ldap

[Rajani Karuturi]

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

(Updated Jan. 22, 2014, 7:24 a.m.)


Review request for cloudstack, Abhinandan Prateek, Ian Duffy, Min Chen, and 
Prachi Damle.


Changes
---

updated with a patch for master


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


Repository: cloudstack-git


Description
---

added an extra column to mark the imported ldap users as from ldap


Diffs (updated)
-

  api/src/com/cloud/user/AccountService.java a9be292 
  api/src/com/cloud/user/User.java 36e9028 
  engine/schema/src/com/cloud/user/UserVO.java 68879f6 
  
plugins/dedicated-resources/test/org/apache/cloudstack/dedicated/manager/DedicatedApiUnitTest.java
 213174b 
  
plugins/deployment-planners/implicit-dedication/test/org/apache/cloudstack/implicitplanner/ImplicitPlannerTest.java
 4182193 
  
plugins/hypervisors/vmware/test/com/cloud/hypervisor/vmware/VmwareDatacenterApiUnitTest.java
 4a00489 
  
plugins/network-elements/juniper-contrail/test/org/apache/cloudstack/network/contrail/management/MockAccountManager.java
 2f81688 
  
plugins/user-authenticators/ldap/src/org/apache/cloudstack/api/command/LdapCreateAccountCmd.java
 100ffe6 
  
plugins/user-authenticators/ldap/src/org/apache/cloudstack/api/command/LdapImportUsersCmd.java
 89cec65 
  server/src/com/cloud/user/AccountManagerImpl.java 5204589 
  server/test/com/cloud/configuration/ConfigurationManagerTest.java f1bb30a 
  server/test/com/cloud/network/DedicateGuestVlanRangesTest.java 1615b84 
  server/test/com/cloud/user/MockAccountManagerImpl.java 62e7fc8 
  server/test/com/cloud/vm/UserVmManagerTest.java 83f7520 
  server/test/com/cloud/vpc/NetworkACLManagerTest.java 629afa3 
  server/test/com/cloud/vpc/NetworkACLServiceTest.java 786789f 
  server/test/org/apache/cloudstack/affinity/AffinityApiUnitTest.java 061fd42 
  server/test/org/apache/cloudstack/network/lb/CertServiceTest.java a67a9ab 
  
server/test/org/apache/cloudstack/region/gslb/GlobalLoadBalancingRulesServiceImplTest.java
 d152c66 
  setup/db/db/schema-421to430.sql ccff7c1 

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


Testing
---

manually tested


Thanks,

Rajani Karuturi