[GitHub] cloudstack issue #1563: CLOUDSTACK-9389:[automation]updating test_routers_ne...

[nitt10prashant]

Github user nitt10prashant commented on the issue:

https://github.com/apache/cloudstack/pull/1563
  
@swill just curious  to know Which guest OS you are using ? Since Cent OS 
template is default in ACS i modified test_data for cent OS.  

Regx should be consider ?
->I Agree with you, will push changes for regx  to make sure it work for 
both ping pattern .

What do you think? Sorry, I don't mean to be combative here, but this is a 
good opertunity for us to review the way we handle OS specific test data.
->Yes this should be  discussed thoroughly and should be documented  
properly


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

[ANNOUNCE] Apache CloudStack Security Releases 4.5.2.1, 4.6.2.1, 4.7.1.1, 4.8.0.1

[Rohit Yadav]

# Apache CloudStack Security Releases 4.5.2.1, 4.6.2.1, 4.7.1.1, 4.8.0.1

The Apache CloudStack project announces security releases 4.5.2.1, 4.6.2.1,
4.7.1.1, 4.8.0.1 that fixes the bug causing vulnerability over previously
released minor versions 4.5.2, 4.6.2, 4.7.1 and 4.8.0 respectively. As a
security release, no new features are included but only includes: (a) the
fix for CVE-2016-3085, and (b) a minor security fix related to
listTemplates API that exposes list of templates to domain admins.

Apache CloudStack is an integrated Infrastructure-as-a-Service
(IaaS) software platform that allows users to build feature-rich public
and private cloud environments. CloudStack includes an intuitive
user interface and rich API for managing the compute, networking,
software, and storage resources. The project became an Apache top level
project in March 2013.

More information about Apache CloudStack can be found at:

http://cloudstack.apache.org/

## Upgrade Notes

Affected users are only required to upgrade their management server(s) to
suitable security release version. The upgrade does not require any
database or systemvm-template related change.

## Downloads

The official source code release can be downloaded from:

http://cloudstack.apache.org/downloads.html

In addition to the official source code release, individual
contributors have also made convenience binaries available on the Apache
CloudStack download page, and as follows:

http://cloudstack.apt-get.eu/ubuntu/dists/
http://cloudstack.apt-get.eu/centos/6/
http://cloudstack.apt-get.eu/centos/7/
http://www.shapeblue.com/packages/

Regards.

[GitHub] cloudstack issue #896: CLOUDSTACK-8908 After copying the template charging f...

[bvbharatk]

Github user bvbharatk commented on the issue:

https://github.com/apache/cloudstack/pull/896
  
### ACS CI BVT Run
 **Sumarry:**
 Build Number 173
 Hypervisor xenserver
 NetworkType Advanced
 Passed=73
 Failed=0
 Skipped=3

_Link to logs Folder (search by build_no):_ 
https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0


**Failed tests:**

**Skipped tests:**
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_deploy_vgpu_enabled_vm

**Passed test suits:**
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_vpc_vpn.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_routers.py
test_reset_vm_on_reboot.py
test_snapshots.py
test_deploy_vms_with_varied_deploymentplanners.py
test_login.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_affinity_groups.py
test_network_acl.py
test_pvlan.py
test_volumes.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_vm_life_cycle.py
test_disk_offerings.py


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

[GitHub] cloudstack issue #899: BUG-ID:CLOUDSTACK-8921

[bvbharatk]

Github user bvbharatk commented on the issue:

https://github.com/apache/cloudstack/pull/899
  
### ACS CI BVT Run
 **Sumarry:**
 Build Number 172
 Hypervisor xenserver
 NetworkType Advanced
 Passed=73
 Failed=0
 Skipped=3

_Link to logs Folder (search by build_no):_ 
https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0


**Failed tests:**

**Skipped tests:**
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_deploy_vgpu_enabled_vm

**Passed test suits:**
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_vpc_vpn.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_routers.py
test_reset_vm_on_reboot.py
test_snapshots.py
test_deploy_vms_with_varied_deploymentplanners.py
test_login.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_affinity_groups.py
test_network_acl.py
test_pvlan.py
test_volumes.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_vm_life_cycle.py
test_disk_offerings.py


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

Re: Introducing Mukul

[ilya]

Hi Mikul

Welcome,

You can also convert your system to linux and run Windows as a VM :)

Then you can do nested KVMs and be fine.

Regards,
ilya

On 6/8/16 6:26 AM, Mukul Rajarshi wrote:
> Hello CloudStack team,
> 
> My name is Mukul Rajarshi and I have joined Accelerite CloudPlatform testing 
> team. Earlier I have worked on in storage systems, cloud computing, 
> virtualization and data management systems.  This is the first time I am 
> working on CloudStack in the process have followed posts/blogs from some of 
> the members in this community and found them really helpful. Excited to be 
> part of this community and hopefully would be to contribute in future.
> 
> Currently I am trying putting up a scratchpad CloudStack environment on 
> VirtualBox. Facing issue when I use KVM hypervisor, XenServer is fine. Let me 
> know there are known issues or gotchas with KVM as a VM.
> 
> 
> ~Mukul
> www.accelerite.com
> 
> 
> 
> 
> DISCLAIMER
> ==
> This e-mail may contain privileged and confidential information which is the 
> property of Accelerite, a Persistent Systems business. It is intended only 
> for the use of the individual or entity to which it is addressed. If you are 
> not the intended recipient, you are not authorized to read, retain, copy, 
> print, distribute or use this message. If you have received this 
> communication in error, please notify the sender and delete all copies of 
> this message. Accelerite, a Persistent Systems business does not accept any 
> liability for virus infected mails.
> 

[GitHub] cloudstack issue #1547: Fixes for VirtualRouters in Basic Networking, especi...

[swill]

Github user swill commented on the issue:

https://github.com/apache/cloudstack/pull/1547
  
BTW, these tests results are for the following tests

```
nosetests --with-marvin --marvin-config=${marvinCfg} -s -a tags=basic \
component/test_deploy_vm_userdata_multi_nic.py \
component/test_escalations_securitygroups.py \
component/test_escalations_vpncustomergateways.py \
component/test_security_groups.py \
smoke/test_multipleips_per_nic.py \
smoke/test_portable_publicip.py \
smoke/test_routers.py

nosetests --with-marvin --marvin-config=${marvinCfg} -s -a \
component/maint/test_multiple_ip_ranges.py
```

With `${marvinCfg}` of:
`/data/shared/marvin/mct-zone1-kvm1-basic.cfg`
and
`/data/shared/marvin/mct-zone3-kvm3-basic.cfg`


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

[GitHub] cloudstack issue #1547: Fixes for VirtualRouters in Basic Networking, especi...

[swill]

Github user swill commented on the issue:

https://github.com/apache/cloudstack/pull/1547
  
I ran the same network tests I mentioned above against master and I had the 
following results.

```
Tests Run: 24
  Skipped: 0
   Failed: 8
   Errors: 2
 Duration: 2h 35m 53s
```

All of the errors were the same on `master`, but in addition it also had a 
failure on this test:
```
FAIL: Test authorize ingress rule
--
Traceback (most recent call last):
  File 
"/data/git/cs2/cloudstack/test/integration/component/test_security_groups.py", 
line 459, in test_01_authorizeIngressRule
(self.virtual_machine.ipaddress, e)
AssertionError: SSH Access failed for 192.168.22.221: SSH connection has 
Failed. Waited 600s. Error is SSH Connection Failed
--
Additional details in: /tmp/MarvinLogs/test_routers_ZEOUOD/results.txt
```

I am not sure if this PR fixed this issue or if it is just an intermittent 
issue, but this shows that this PR did not introduce any new issues into master 
(according to these unverified tests).

Given that this fixes issues in basic networking and does not appear to 
introduce any new issues, I am inclined to add it to the 4.9 release.  

@wido, @remibergsma and @DaanHoogland do you guys agree with this decision? 
 Thanks...


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

[GitHub] cloudstack issue #1581: CLOUDSTACK-9404 Fixed ordering of network ACL rules ...

[dmabry]

Github user dmabry commented on the issue:

https://github.com/apache/cloudstack/pull/1581
  
I tested this in our lab with advanced networking verified the patch is 
working as expected.  I used the following test process.

1. Created an acl and applied it to 1 VPC Network Tier.
``` 
10  192.168.10.0/24 Allow   ALL Ingress  
20  192.168.20.0/24 Allow   ALL Ingress 
30  192.168.30.0/24 Allow   ALL Ingress 
```
2. iptables looked like the following on the VPC VR
```
Chain ACL_INBOUND_eth2 (1 references)
target prot opt source   destination 
ACCEPT all  --  0.0.0.0/0225.0.0.50  
ACCEPT all  --  0.0.0.0/0224.0.0.18  
ACCEPT all  --  192.168.10.0/24  0.0.0.0/0   
ACCEPT all  --  192.168.20.0/24  0.0.0.0/0   
ACCEPT all  --  192.168.30.0/24  0.0.0.0/0   
DROP   all  --  0.0.0.0/00.0.0.0/0   
```
3. I added an additional rule of:
```
40  192.168.40.0/24 Allow   TCP 80  80  
Ingress 
```
4. iptables looked like the following on the VPC VR
```
Chain ACL_INBOUND_eth2 (1 references)
target prot opt source   destination 
ACCEPT all  --  0.0.0.0/0225.0.0.50  
ACCEPT all  --  0.0.0.0/0224.0.0.18  
ACCEPT all  --  192.168.10.0/24  0.0.0.0/0   
ACCEPT all  --  192.168.20.0/24  0.0.0.0/0   
ACCEPT all  --  192.168.30.0/24  0.0.0.0/0   
ACCEPT tcp  --  192.168.40.0/24  0.0.0.0/0tcp dpt:80
DROP   all  --  0.0.0.0/00.0.0.0/0   
```

In summary, it looks like this patch works verified by manual testing in my 
lab.

In short, LGTM based on testing.


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

[GitHub] cloudstack issue #1584: [BLOCKER][FIX] CLOUDSTACK-9409: Add role_id to cloud...

[nvazquez]

Github user nvazquez commented on the issue:

https://github.com/apache/cloudstack/pull/1584
  
Cool, thanks @swill!


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

[GitHub] cloudstack issue #1584: [BLOCKER][FIX] CLOUDSTACK-9409: Add role_id to cloud...

[swill]

Github user swill commented on the issue:

https://github.com/apache/cloudstack/pull/1584
  
Ok, thanks guys.  I will get this merged into 4.9.  Thank you for the bug 
report and fix...


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

Re: ICLA for contributors

[John Burwell]

All,

I believe Pierre-Luc’s explanation is correct, and that we may have slightly 
different definitions of contributor and committer.  Generally, we define a 
contributor, we are referring to anyone (committer, PMC member, any person in 
the world) who contributes code, documentation, etc to the project.  We define 
a committer as a contributor who demonstrated a strong and sustained commitment 
to the project.  In recognition of this commitment, committers are granted the 
right to commit changes to the project’s public repositories.  Execution of an 
ICLA and CCLA are required in order for someone to become an Apache CloudStack 
committer.

IANAL, but my understanding is that any individual can contribute to an Apache 
project without signing an ICLA/CCLA because a committer with one in place will 
perform commit to the repository.  The act of the individual giving code to the 
project and a committer reviewing and committing it to the repository qualifies 
as rights assignment under by the ASL.  Since execution of an ICLA/CCLA is a 
prerequisite for all Apache CloudStack committers and Apache secures our 
repositories to only allow committers read/write access, rights assignment 
under the ASL for our repositories is properly enforced/managed.

Thanks,
-John

> 
john.burw...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London VA WC2N 4HSUK
@shapeblue


On Jun 9, 2016, at 1:46 PM, Pierre-Luc Dion  wrote:
> 
> Hi Ron,
> 
> As far as I know, ICLA and CCLA is required for commiters, but not required
> for non-commiters contributors. I don't know about all details, someone
> else in the ML might have more details about this. For sure, you can be a
> contributor without submitting code as a anyone in this ML is consider as a
> contributor.
> 
> Cheers,
> 
> 
> On Thu, Jun 9, 2016 at 11:46 AM, Ron Wheeler > wrote:
> 
>> As part of a discussion during last weeks meeting in Mpntreal, the
>> question was raised about the requirement to have an Individual Contributor
>> License Agreement (ICLA) for each contributor.
>> 
>> http://www.apache.org/licenses/ describes the requirements as follows:
>> 
>> "The ASF desires that all contributors of ideas, code, or documentation to
>> any Apache projects complete, sign, and submit (via fax or email) an
>> Individual Contributor License Agreement (ICLA). The purpose of this
>> agreement is to clearly define the terms under which intellectual property
>> has been contributed to the ASF and thereby allow us to defend the project
>> should there be a legal dispute regarding the software at some future time.
>> A signed ICLA is required to be on file before an individual is given
>> commit rights to an ASF project.
>> 
>> For a corporation that has assigned employees to work on an Apache
>> project, a Corporate CLA (CCLA) is available for contributing intellectual
>> property via the corporation, that may have been assigned as part of an
>> employment agreement. Note that a Corporate CLA does not remove the need
>> for every developer to sign their own ICLA as an individual, to cover any
>> of their contributions which are not owned by the corporation signing the
>> CCLA."
>> 
>> There is a split between desirable and mandatory.
>> 
>> I am not sure that the argument that submitting a PR is a clear sign of
>> intent to give up all rights, has ever been tested in a court but it is
>> much easier to have an signed ICLA for each contributor.
>> 
>> A CCLA for each company that is either paying people to work on the
>> project or has a clause in their employment contract giving the company
>> rights to all IP created during their employment is required. This removes
>> any ambiguity about the individual's right to make a PR.
>> 
>> It is a little bit of housekeeping to keep track of the list of
>> contributors with ICLA's. A wiki page listing the contributors is a simple
>> solution.
>> 
>> https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+Contributors
>> is what we did at OFBiz.
>> 
>> The ICLA and CCLA is good for all Apache projects.
>> 
>> Ron
>> 
>> --
>> Ron Wheeler
>> President
>> Artifact Software Inc
>> email: rwhee...@artifact-software.com
>> skype: ronaldmwheeler
>> phone: 866-970-2435, ext 102
>> 
>> 

[GitHub] cloudstack issue #1581: CLOUDSTACK-9404 Fixed ordering of network ACL rules ...

[dmabry]

Github user dmabry commented on the issue:

https://github.com/apache/cloudstack/pull/1581
  
I just kicked off a build that includes this PR.  I'm going to push this to 
our lab for testing and report back.


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

[GitHub] cloudstack issue #1548: Compabitility fix for Docker >= 1.11 (docker/docker#...

[dmabry]

Github user dmabry commented on the issue:

https://github.com/apache/cloudstack/pull/1548
  
LGTM based code review.  This is a very straight forward change.


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

[GitHub] cloudstack issue #905: BUG-ID: CLOUDSTACK-8922: Unable to delete IP tag

[bvbharatk]

Github user bvbharatk commented on the issue:

https://github.com/apache/cloudstack/pull/905
  
### ACS CI BVT Run
 **Sumarry:**
 Build Number 170
 Hypervisor xenserver
 NetworkType Advanced
 Passed=73
 Failed=0
 Skipped=3

_Link to logs Folder (search by build_no):_ 
https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0


**Failed tests:**

**Skipped tests:**
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_deploy_vgpu_enabled_vm

**Passed test suits:**
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_vpc_vpn.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_routers.py
test_reset_vm_on_reboot.py
test_snapshots.py
test_deploy_vms_with_varied_deploymentplanners.py
test_login.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_affinity_groups.py
test_network_acl.py
test_pvlan.py
test_volumes.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_vm_life_cycle.py
test_disk_offerings.py


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

Re: ICLA for contributors

[Pierre-Luc Dion]

Hi Ron,

As far as I know, ICLA and CCLA is required for commiters, but not required
for non-commiters contributors. I don't know about all details, someone
else in the ML might have more details about this. For sure, you can be a
contributor without submitting code as a anyone in this ML is consider as a
contributor.

Cheers,


On Thu, Jun 9, 2016 at 11:46 AM, Ron Wheeler  wrote:

> As part of a discussion during last weeks meeting in Mpntreal, the
> question was raised about the requirement to have an Individual Contributor
> License Agreement (ICLA) for each contributor.
>
> http://www.apache.org/licenses/ describes the requirements as follows:
>
> "The ASF desires that all contributors of ideas, code, or documentation to
> any Apache projects complete, sign, and submit (via fax or email) an
> Individual Contributor License Agreement (ICLA). The purpose of this
> agreement is to clearly define the terms under which intellectual property
> has been contributed to the ASF and thereby allow us to defend the project
> should there be a legal dispute regarding the software at some future time.
> A signed ICLA is required to be on file before an individual is given
> commit rights to an ASF project.
>
> For a corporation that has assigned employees to work on an Apache
> project, a Corporate CLA (CCLA) is available for contributing intellectual
> property via the corporation, that may have been assigned as part of an
> employment agreement. Note that a Corporate CLA does not remove the need
> for every developer to sign their own ICLA as an individual, to cover any
> of their contributions which are not owned by the corporation signing the
> CCLA."
>
> There is a split between desirable and mandatory.
>
> I am not sure that the argument that submitting a PR is a clear sign of
> intent to give up all rights, has ever been tested in a court but it is
> much easier to have an signed ICLA for each contributor.
>
> A CCLA for each company that is either paying people to work on the
> project or has a clause in their employment contract giving the company
> rights to all IP created during their employment is required. This removes
> any ambiguity about the individual's right to make a PR.
>
> It is a little bit of housekeeping to keep track of the list of
> contributors with ICLA's. A wiki page listing the contributors is a simple
> solution.
>
> https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+Contributors
> is what we did at OFBiz.
>
> The ICLA and CCLA is good for all Apache projects.
>
> Ron
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwhee...@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>

ICLA for contributors

[Ron Wheeler]

As part of a discussion during last weeks meeting in Mpntreal, the 
question was raised about the requirement to have an Individual 
Contributor License Agreement (ICLA) for each contributor.


http://www.apache.org/licenses/ describes the requirements as follows:

"The ASF desires that all contributors of ideas, code, or documentation 
to any Apache projects complete, sign, and submit (via fax or email) an 
Individual Contributor License Agreement (ICLA). The purpose of this 
agreement is to clearly define the terms under which intellectual 
property has been contributed to the ASF and thereby allow us to defend 
the project should there be a legal dispute regarding the software at 
some future time. A signed ICLA is required to be on file before an 
individual is given commit rights to an ASF project.


For a corporation that has assigned employees to work on an Apache 
project, a Corporate CLA (CCLA) is available for contributing 
intellectual property via the corporation, that may have been assigned 
as part of an employment agreement. Note that a Corporate CLA does not 
remove the need for every developer to sign their own ICLA as an 
individual, to cover any of their contributions which are not owned by 
the corporation signing the CCLA."


There is a split between desirable and mandatory.

I am not sure that the argument that submitting a PR is a clear sign of 
intent to give up all rights, has ever been tested in a court but it is 
much easier to have an signed ICLA for each contributor.


A CCLA for each company that is either paying people to work on the 
project or has a clause in their employment contract giving the company 
rights to all IP created during their employment is required. This 
removes any ambiguity about the individual's right to make a PR.


It is a little bit of housekeeping to keep track of the list of 
contributors with ICLA's. A wiki page listing the contributors is a 
simple solution.


https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+Contributors 
is what we did at OFBiz.


The ICLA and CCLA is good for all Apache projects.

Ron

--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102

[GitHub] cloudstack issue #1584: [BLOCKER][FIX] CLOUDSTACK-9409: Add role_id to cloud...

[nvazquez]

Github user nvazquez commented on the issue:

https://github.com/apache/cloudstack/pull/1584
  
Thanks @rhtyd for this fix!

Just for the record, this was error before this fix:


2016-06-07 11:04:51,233 ERROR [cloud.usage.UsageManagerImpl] 
(Usage-Job-1:null) (logid:) Exception in usage manager
com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
com.mysql.jdbc.JDBC4PreparedStatement@3202d58a: SELECT account.id, 
account.account_name, account.type, account.role_id, account.domain_id, 
account.state, account.removed, account.cleanup_needed, account.network_domain, 
account.uuid, account.default_zone_id, account.default FROM account WHERE 
account.id = 2
...
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: 
Unknown column 'account.role_id' in 'field list' 


And now I can see usage jobs work properly:


2016-06-09 00:00:52,561 DEBUG [cloud.usage.UsageManagerImpl] 
(Usage-HB-1:null) (logid:) Scheduling Usage job...
2016-06-09 00:00:52,561 INFO  [cloud.usage.UsageManagerImpl] 
(Usage-Job-1:null) (logid:) starting usage job...
2016-06-09 00:00:52,568 INFO  [cloud.usage.UsageManagerImpl] 
(Usage-Job-1:null) (logid:) Parsing usage records between Wed Jun 08 00:00:00 
PDT 2016 and Wed Jun 08 23:59:59 PDT 2016

2016-06-09 00:00:53,436 INFO  [cloud.usage.UsageManagerImpl] 
(Usage-Job-1:null) (logid:) usage job complete


LGTM


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

Re: apachecloudstack.net and apachecloudstack.org

[Pierre-Luc Dion]

nice idea Erik,  it worth asking infra about this...



On Thu, Jun 9, 2016 at 9:45 AM, Erik Weber  wrote:

> On Thu, Jun 9, 2016 at 3:40 PM, Wido den Hollander  wrote:
>
> >
> > > Op 9 juni 2016 om 15:21 schreef Pierre-Luc Dion :
> > >
> > >
> > > Hi,
> > >
> > > From the #jenkins slack channel discussion this morning we kind a took
> a
> > > quick action on getting our hands on domain registration for
> > > apachecloudstack{.org,.net}
> > >
> > > So, we also did some DNS updated until we have help from INFRA to use
> > > cloudstack.org  which to me make more sense.
> > >
> > > So we added few dns entry:
> > >
> > > builds.apachecloudstack.net   => new jenkins to replace
> > > jenkins.buildacloud.org
> > > download.apachecloudstack.net =>  cname to cloudstack.apt-get.eu
> > > artifacts.apachecloudstack.net=> nexus service for the new jenkins
> > > system
> > >
> > > all apachecloudstack.org point to .net
> > >
> >
> > Great! download.apachecloudstack.net is already working I see :)
> >
> > Now we just have to make sure that some organization will own these
> domain
> > names instead of a private individual, but that's something for later.
> >
> >
>
> No idea if this is possible within ASF boundaries, but could the ASF own
> them, and provide the PMC access to the management of the zone(s)?
>
> I believe ASF use Bind (or similar) with management in puppet, but if
> allowed there are cloud solutions that works well and have nice APIs
> (CloudFlare is one).
>
>
> --
> Erik
>

Re: VMware vSphere 6.0 support on CloudStack

[Jeff Hair]

One more thing: you will have to add guest OS mappings for VMware 6 into
the database (or use the API). Otherwise the management server will send
the wrong pre-set guest OS to the hypervisor. It will pick a generic guest
otherwise. The generic guest seems to work fine for Linux, but will cause
problems in OSes like Windows.

*Jeff Hair*
Technical Lead and Software Developer

Tel: (+354) 415 0200
j...@greenqloud.com
www.greenqloud.com

On Mon, Jun 6, 2016 at 3:51 PM, Jeff Hair  wrote:

> It works, although it's not officially documented. You should just be able
> to hook it up. The reason it's not in the documentation is because there is
> no official testing of it.
>
> Jeff
>
>
> On Mon, Jun 6, 2016 at 2:14 PM, Couto, Antonio 
> wrote:
>
>> Hello everyone, I’d appreciate your kindly help.
>>
>>
>>
>> Could you provide any information on/if/when *CloudStack* will support
>> VMware vSphere ESXi 6.0?
>>
>>
>>
>> Best regards,
>>
>>
>>
>> *Antonio Couto*
>>
>> Hybrid IT Specialist
>>
>>
>> +55 11 5502 5717  Office
>> +55 11 99943 5185  Mobile
>> São Paulo, SP - Brazil
>> *hpe.com* 
>> @antoniojscouto
>>
>> [image: HPE Logo v1]
>>
>>
>>
>
>

CVE-2016-3085: Apache CloudStack Authentication Bypass Vulnerability

[John Kinsella]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

CVE-2016-3085: Apache CloudStack Authentication Bypass Vulnerability

CVSS v2:
7.5 (AV:N/AC:L/Au:N/C:P/I:P/A:P)

Vendors:
The Apache Software Foundation
Accelerite, Inc

Versions affected:
CloudStack versions 4.5.0 and newer

Description:
Apache CloudStack contains an authentication module providing “single
sign-on” functionality via the SAML data format. Under certain
conditions, a user could manage to access the user interface without
providing proper credentials. As the SAML plugin is disabled by
default, this issue only affects installations that have enabled
and use SAML-based authentication.

Mitigation:
Users of Apache CloudStack using the SAML plugin should upgrade to
one of the following versions, based on which release they are
currently using: 4.5.2.1, 4.6.2.1, 4.7.1.1, or 4.8.0.1. These
versions contain only security updates, and no other functionality
change.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCgAGBQJXWNuFAAoJEOom9N0pCN7Sw8EP/0Q5YgomRGEocod2Cmlfd/E9
JKSBdt38hTclPXcdi3w/1Fq88l54erfHuPLPJObpsIR/vQGiOU0K9KkaO5jYDHtR
uFzb37PDzkR/x0tpfOvl1LqWOl89dSjF0qNAB8gi5ThqSWhBst70bjq0bR1aFxXx
I05JzZgD4eye+3tYRcVoFPOkbP7E5pWFtPo9LKUdRL4bfSwskB7d5MOGUoBMQfBb
vuMp7BikT3kMU7kiXNHKMCdd24iAQeiMOocZo7fPn70DiKANqLzinLxlWZHrd4Lh
IPO/m35s52tIVFxXAIF5N7ThAhOCoqQykxykCAgZN1Wi5444/bBJ/ppaP3StWq8i
gRTPzVYbniCTUfG4ynGZIwLwdDJxMb4M1kBdT3lpQWRhq24vE7/xSPANy8ipegvw
rZ8EYS0b0Ud4Bx60+L3rCMBJAwlSaddX/DDHaYUU8hxT5NRoK0eiWf9p4jd40Ob4
BYM/9mi4tv4Wq6tIEqSZfVMdNKgY3+0oBP5HEhEmXSk9Th0rNLySB7Xpix7dC5iF
4I0kpki8BFirE6rBGiKNARdXZJ9QTUTUG/wk1Ndgoe4kJG3PtR6PuY9DAWomqecz
aF/tmyIZXLeVEyZrS1rKLPlIjRHarALoQgB0Ln+UAhS0oyVJ5LrR4Ie70UDCMRNv
rNjki8AjTUnQarsp14lT
=+Tpv
-END PGP SIGNATURE-

Re: apachecloudstack.net and apachecloudstack.org

[Erik Weber]

On Thu, Jun 9, 2016 at 3:40 PM, Wido den Hollander  wrote:

>
> > Op 9 juni 2016 om 15:21 schreef Pierre-Luc Dion :
> >
> >
> > Hi,
> >
> > From the #jenkins slack channel discussion this morning we kind a took a
> > quick action on getting our hands on domain registration for
> > apachecloudstack{.org,.net}
> >
> > So, we also did some DNS updated until we have help from INFRA to use
> > cloudstack.org  which to me make more sense.
> >
> > So we added few dns entry:
> >
> > builds.apachecloudstack.net   => new jenkins to replace
> > jenkins.buildacloud.org
> > download.apachecloudstack.net =>  cname to cloudstack.apt-get.eu
> > artifacts.apachecloudstack.net=> nexus service for the new jenkins
> > system
> >
> > all apachecloudstack.org point to .net
> >
>
> Great! download.apachecloudstack.net is already working I see :)
>
> Now we just have to make sure that some organization will own these domain
> names instead of a private individual, but that's something for later.
>
>

No idea if this is possible within ASF boundaries, but could the ASF own
them, and provide the PMC access to the management of the zone(s)?

I believe ASF use Bind (or similar) with management in puppet, but if
allowed there are cloud solutions that works well and have nice APIs
(CloudFlare is one).


-- 
Erik

Re: apachecloudstack.net and apachecloudstack.org

[Wido den Hollander]

> Op 9 juni 2016 om 15:21 schreef Pierre-Luc Dion :
> 
> 
> Hi,
> 
> From the #jenkins slack channel discussion this morning we kind a took a
> quick action on getting our hands on domain registration for
> apachecloudstack{.org,.net}
> 
> So, we also did some DNS updated until we have help from INFRA to use
> cloudstack.org  which to me make more sense.
> 
> So we added few dns entry:
> 
> builds.apachecloudstack.net   => new jenkins to replace
> jenkins.buildacloud.org
> download.apachecloudstack.net =>  cname to cloudstack.apt-get.eu
> artifacts.apachecloudstack.net=> nexus service for the new jenkins
> system
> 
> all apachecloudstack.org point to .net
> 

Great! download.apachecloudstack.net is already working I see :)

Now we just have to make sure that some organization will own these domain 
names instead of a private individual, but that's something for later.

Wido

> Cheers,

Re: apachecloudstack.net and apachecloudstack.org

[Daan Hoogland]

Pierre-Luc,

You are great! And now that Mohammed Ali has passed away from us ...

On Thu, Jun 9, 2016 at 3:21 PM, Pierre-Luc Dion  wrote:

> Hi,
>
> From the #jenkins slack channel discussion this morning we kind a took a
> quick action on getting our hands on domain registration for
> apachecloudstack{.org,.net}
>
> So, we also did some DNS updated until we have help from INFRA to use
> cloudstack.org  which to me make more sense.
>
> So we added few dns entry:
>
> builds.apachecloudstack.net   => new jenkins to replace
> jenkins.buildacloud.org
> download.apachecloudstack.net =>  cname to cloudstack.apt-get.eu
> artifacts.apachecloudstack.net=> nexus service for the new jenkins
> system
>
> all apachecloudstack.org point to .net
>
> Cheers,
>



-- 
Daan

apachecloudstack.net and apachecloudstack.org

[Pierre-Luc Dion]

Hi,

>From the #jenkins slack channel discussion this morning we kind a took a
quick action on getting our hands on domain registration for
apachecloudstack{.org,.net}

So, we also did some DNS updated until we have help from INFRA to use
cloudstack.org  which to me make more sense.

So we added few dns entry:

builds.apachecloudstack.net   => new jenkins to replace
jenkins.buildacloud.org
download.apachecloudstack.net =>  cname to cloudstack.apt-get.eu
artifacts.apachecloudstack.net=> nexus service for the new jenkins
system

all apachecloudstack.org point to .net

Cheers,

[GitHub] cloudstack issue #1547: Fixes for VirtualRouters in Basic Networking, especi...

[swill]

Github user swill commented on the issue:

https://github.com/apache/cloudstack/pull/1547
  
Here is a run against advanced networking.

I am trying to test a bunch of basic zone networking tests, but I had never 
previously verified if they were broken.  I have run them against this PR, but 
there are a bunch of issues.  I am going to run the same set of tests against 
master to see if there is a difference in the results.

Unverified tests run against this PR.  Doing the same against master now...
```
Tests Run: 24
  Skipped: 0
   Failed: 7
   Errors: 2
 Duration: 2h 21m 30s
```
(details masked intentionally as this set of tests is unverified)



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

[GitHub] cloudstack issue #1547: Fixes for VirtualRouters in Basic Networking, especi...

[swill]

Github user swill commented on the issue:

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


### CI RESULTS

```
Tests Run: 85
  Skipped: 0
   Failed: 0
   Errors: 0
 Duration: 4h 00m 38s
```



**Associated Uploads**

**`/tmp/MarvinLogs/DeployDataCenter__Jun_09_2016_06_44_20_ETRLGB:`**
* 
[dc_entries.obj](https://objects-east.cloud.ca/v1/e465abe2f9ae4478b9fff416eab61bd9/PR1547-3/tmp/MarvinLogs/DeployDataCenter__Jun_09_2016_06_44_20_ETRLGB/dc_entries.obj)
* 
[failed_plus_exceptions.txt](https://objects-east.cloud.ca/v1/e465abe2f9ae4478b9fff416eab61bd9/PR1547-3/tmp/MarvinLogs/DeployDataCenter__Jun_09_2016_06_44_20_ETRLGB/failed_plus_exceptions.txt)
* 
[runinfo.txt](https://objects-east.cloud.ca/v1/e465abe2f9ae4478b9fff416eab61bd9/PR1547-3/tmp/MarvinLogs/DeployDataCenter__Jun_09_2016_06_44_20_ETRLGB/runinfo.txt)

**`/tmp/MarvinLogs/test_network_N3C2B9:`**
* 
[failed_plus_exceptions.txt](https://objects-east.cloud.ca/v1/e465abe2f9ae4478b9fff416eab61bd9/PR1547-3/tmp/MarvinLogs/test_network_N3C2B9/failed_plus_exceptions.txt)
* 
[results.txt](https://objects-east.cloud.ca/v1/e465abe2f9ae4478b9fff416eab61bd9/PR1547-3/tmp/MarvinLogs/test_network_N3C2B9/results.txt)
* 
[runinfo.txt](https://objects-east.cloud.ca/v1/e465abe2f9ae4478b9fff416eab61bd9/PR1547-3/tmp/MarvinLogs/test_network_N3C2B9/runinfo.txt)

**`/tmp/MarvinLogs/test_vpc_routers_7OVU64:`**
* 
[failed_plus_exceptions.txt](https://objects-east.cloud.ca/v1/e465abe2f9ae4478b9fff416eab61bd9/PR1547-3/tmp/MarvinLogs/test_vpc_routers_7OVU64/failed_plus_exceptions.txt)
* 
[results.txt](https://objects-east.cloud.ca/v1/e465abe2f9ae4478b9fff416eab61bd9/PR1547-3/tmp/MarvinLogs/test_vpc_routers_7OVU64/results.txt)
* 
[runinfo.txt](https://objects-east.cloud.ca/v1/e465abe2f9ae4478b9fff416eab61bd9/PR1547-3/tmp/MarvinLogs/test_vpc_routers_7OVU64/runinfo.txt)


Uploads will be available until `2016-08-09 02:00:00 +0200 CEST`

*Comment created by [`upr comment`](https://github.com/cloudops/upr).*



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

[GitHub] cloudstack issue #1435: Dockerfile4.9

[pdion891]

Github user pdion891 commented on the issue:

https://github.com/apache/cloudstack/pull/1435
  
@runseb I agree, images must be smaller. for the simulator, it's kind of 
usefull to have everything in it but it's not container best practice for sure. 
 other images, we could probably use alpine linux, but still need to figure out 
how to run cloudstack as a single .war file.


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

[GitHub] cloudstack issue #1464: [CLOUDSTACK-9337]Enhance vcenter.py to create data c...

[swill]

Github user swill commented on the issue:

https://github.com/apache/cloudstack/pull/1464
  
Master is frozen in prep for the 4.9 release. This will have to wait for 
4.10. 


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

[GitHub] cloudstack issue #1563: CLOUDSTACK-9389:[automation]updating test_routers_ne...

[swill]

Github user swill commented on the issue:

https://github.com/apache/cloudstack/pull/1563
  
This assumes that people know how to work with the test data and that they 
understand that "this random template needs X format and this other one will 
need Y format".  This is too much to ask without guidance, especially as we try 
to improve the automatability of the testing.  

The regex idea is not a perfect solution, but would allow for us to handle 
more template types with a single entry.  Ideally we would be able to specify 
the expected values for this type of thing in an OS specific way so the tested 
(and verified) values for each OS can live in the test data. It would probably 
need a default that is used if the current OS does not have a match. 

My main problem with this is that it will, by default,  break this test for 
everyone using bubble to automate their testing. Maybe we leave the old default 
test value in place, and people who are testing with other OSs can now override 
manually. 

What do you think? Sorry, I don't mean to be combative here, but this is a 
good opertunity for us to review the way we handle OS specific test data. 


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

[GitHub] cloudstack issue #914: BUG-ID CLOUDSTACK-8939

[bvbharatk]

Github user bvbharatk commented on the issue:

https://github.com/apache/cloudstack/pull/914
  
### ACS CI BVT Run
 **Sumarry:**
 Build Number 167
 Hypervisor xenserver
 NetworkType Advanced
 Passed=73
 Failed=0
 Skipped=3

_Link to logs Folder (search by build_no):_ 
https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0


**Failed tests:**

**Skipped tests:**
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_deploy_vgpu_enabled_vm

**Passed test suits:**
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_vpc_vpn.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_routers.py
test_reset_vm_on_reboot.py
test_snapshots.py
test_deploy_vms_with_varied_deploymentplanners.py
test_login.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_affinity_groups.py
test_network_acl.py
test_pvlan.py
test_volumes.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_vm_life_cycle.py
test_disk_offerings.py


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

[GitHub] cloudstack issue #1451: CLOUDSTACK-9319: Use timeout when applying config to...

[insom]

Github user insom commented on the issue:

https://github.com/apache/cloudstack/pull/1451
  
@bvbharatk Hi, am I supposed to do something with this CI output? It looks 
like all of the errors are related to other parts of CloudStack that aren't 
touched by my commits. I came back to check on this bug because I got bitten by 
this again today (timeout when adding rules to a virtual router, but the 
timeout is actually not getting applied properly).


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

[GitHub] cloudstack issue #1455: [CLOUDSTACK-9328]: Fix vlan issues from test suite t...

[sanju1010]

Github user sanju1010 commented on the issue:

https://github.com/apache/cloudstack/pull/1455
  
Failures from CI are not related to changes in this file. This commit makes 
changes to test_privategw_acl.py


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

[GitHub] cloudstack-www pull request #27: downloads: update page for security release...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack-www/pull/27


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

[GitHub] cloudstack-www issue #27: downloads: update page for security releases

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack-www/pull/27
  
Thanks @runseb will do that


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

[GitHub] cloudstack issue #1563: CLOUDSTACK-9389:[automation]updating test_routers_ne...

[nitt10prashant]

Github user nitt10prashant commented on the issue:

https://github.com/apache/cloudstack/pull/1563
  
-->I think it is important that the test data does not need to be changed 
for our automated(ish) CI to show the tests are passing
@swill  i think test-data meant to be changed depend on your local 
environment and every one should have local copy of their own test data .



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

[GitHub] cloudstack issue #1455: [CLOUDSTACK-9328]: Fix vlan issues from test suite t...

[bvbharatk]

Github user bvbharatk commented on the issue:

https://github.com/apache/cloudstack/pull/1455
  
### ACS CI BVT Run
 **Sumarry:**
 Build Number 166
 Hypervisor xenserver
 NetworkType Advanced
 Passed=70
 Failed=3
 Skipped=3

_Link to logs Folder (search by build_no):_ 
https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0


**Failed tests:**
* test_vpc_vpn.py

 * ContextSuite context=TestRVPCSite2SiteVpn>:setup Failing since 17 runs

 * ContextSuite context=TestVpcRemoteAccessVpn>:setup Failing since 17 runs

 * ContextSuite context=TestVpcSite2SiteVpn>:setup Failing since 17 runs


**Skipped tests:**
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_deploy_vgpu_enabled_vm

**Passed test suits:**
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_routers.py
test_reset_vm_on_reboot.py
test_snapshots.py
test_deploy_vms_with_varied_deploymentplanners.py
test_login.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_affinity_groups.py
test_network_acl.py
test_pvlan.py
test_volumes.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_vm_life_cycle.py
test_disk_offerings.py


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

[GitHub] cloudstack-www issue #27: downloads: update page for security releases

[runseb]

Github user runseb commented on the issue:

https://github.com/apache/cloudstack-www/pull/27
  
@rhtyd +1 LGTM

note that to publish in the site live, you need to merge master in asf-site 
branch 


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

[GitHub] cloudstack issue #1435: Dockerfile4.9

[runseb]

Github user runseb commented on the issue:

https://github.com/apache/cloudstack/pull/1435
  
LGTM

I still think we need to put the db in another container, and start the 
whole thing with compose.
Also we need to make the image smaller, maybe using Debian as base would be 
smaller than then full ubuntu:14.04


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

[GitHub] cloudstack-www pull request #27: downloads: update page for security release...

[rhtyd]

GitHub user rhtyd opened a pull request:

https://github.com/apache/cloudstack-www/pull/27

downloads: update page for security releases


/cc @pdion891 @DaanHoogland @wido @karuturi @runseb @swill and others

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

$ git pull https://github.com/rhtyd/cloudstack-www dot1-update-downloads

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

https://github.com/apache/cloudstack-www/pull/27.patch

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

This closes #27


commit ae034e22dee1da5898488f51895aca1be3a5de30
Author: Rohit Yadav 
Date:   2016-06-09T07:28:01Z

downloads: update page for security releases

Signed-off-by: Rohit Yadav 




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

Failed: Apache CloudStack Administration (0d23f51c)

[Read the Docs]

Build Failed for Apache CloudStack Administration (latest)



You can find out more about this failure here:
https://readthedocs.org/projects/cloudstack-administration/builds/4083563/

If you have questions, a good place to start is the FAQ:
https://docs.readthedocs.org/en/latest/faq.html



Keep documenting,
Read the Docs
--
http://readthedocs.org

[GitHub] cloudstack issue #1464: [CLOUDSTACK-9337]Enhance vcenter.py to create data c...

[sanju1010]

Github user sanju1010 commented on the issue:

https://github.com/apache/cloudstack/pull/1464
  
@swill , BVT results are clean. Can we push this to master? This will not 
have any impact on acs master stablity.


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

[GitHub] cloudstack pull request #1587: WIP: Removed the java dependency for packagin...

[abhinandanprateek]

Github user abhinandanprateek closed the pull request at:

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


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

[GitHub] cloudstack pull request #1588: packaging: remove openjdk install deps on clo...

[rhtyd]

GitHub user rhtyd opened a pull request:

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

packaging: remove openjdk install deps on cloudstack-agent

- Removes openjdk as installation requirement, for oracle jre users we 
don't need that
- Adds oracle JDK home (default) paths

Signed-off-by: Rohit Yadav 

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

$ git pull https://github.com/shapeblue/cloudstack kvm-agent-jdk-pkgfix

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

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

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

This closes #1588


commit 5318f16796a8397be9320dcf0b4bf229e12fa23f
Author: Rohit Yadav 
Date:   2016-06-09T06:39:10Z

packaging: remove openjdk install deps on cloudstack-agent

- Removes openjdk as installation requirement, for oracle jre users we 
don't need that
- Adds oracle JDK home (default) paths

Signed-off-by: Rohit Yadav 




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

[GitHub] cloudstack pull request #1588: packaging: remove openjdk install deps on clo...

[rhtyd]

Github user rhtyd closed the pull request at:

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


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