[GitHub] cloudstack pull request: CLOUDSTACK-9348: Use non-blocking SSL han...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1493#issuecomment-215310531
  
BTW, I built with `-T 2C`, if that is relevant to help you understand why 
it failed...


---
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: OSPF: adding dynamically routing capabili...

2016-04-27 Thread abhinandanprateek
Github user abhinandanprateek commented on the pull request:

https://github.com/apache/cloudstack/pull/1371#issuecomment-215310296
  
+ TMP=/tmp
+ CLOUDDIR=/root/cloudstack_shapeblue
+ mkdir -p /tmp/simulator/smoke/misc
+ nosetests --with-xunit --xunit-file=/tmp/simulator/smoke/test_quota.xml 
--with-marvin --marvin-config=/root/cloudstack_shapeblue/advanced.cfg 
/root/cloudstack_shapeblue/test/integration/component/test_ospf.py -s -a 
tags=advanced,required_hardware=false --zone=Bootcamp --hypervisor=xenserver

 Marvin Init Started 

=== Marvin Parse Config Successful ===

=== Marvin Setting TestData Successful===

 Log Folder Path: /tmp//MarvinLogs//Apr_28_2016_10_11_40_GB5OFJ. All 
logs will be available here 

=== Marvin Init Logging Successful===

 Marvin Init Successful 
test_01_dynamic_routing_using_ospf 
(integration.component.test_ospf.TestCreateDynmaicServiceOffering)
Response ospfEnabled: True
Response ospfSuperCIDR: 200.100.0.0/16
Response ospf Enabled: True
Response ospfSuperCIDR: 200.100.0.0/16
Check if the VPC offering is created successfully?
VPC offering is created successfully - Cosmic VPC off-H7FBTX
VPC Offering id = 605c77b9-e377-485d-b2b0-5b67c0f8c20b
Check if the VPC network is created successfully?
VPC network created successfully - Batman VPC-68RBKE
VPC batman_vpc id = bd637cab-976b-49cb-8b2e-24f105b8580e
Check if the VPC network is created successfully?
VPC network created successfully - Superman VPC-C7UIA5
VPC superman_vpc id = cc52d78a-0388-4879-b86a-a34de16107e7
Dynamic Network offering id = a14c863b-c9e0-4ed5-9102-6ceeb370c51b
Created a network ACL list acl
Added a network ACL b9bef6a8-7787-4e57-8352-a6a6f8760c0a to ACL list acl
Added a network ACL dd6e799a-1070-4de8-8670-67adebd3ba89 to ACL list acl
Verifying list network response to check if network created?
Created batman_network_tier1 with ID: 7d0dbf7b-f510-4cc0-ae0e-e0947144a49a
Created a network ACL list acl
Added a network ACL 77d024bd-2970-4123-952f-577483ce6bb5 to ACL list acl
Added a network ACL 5466f0f2-3ba1-43d4-9236-13e547182026 to ACL list acl
Verifying list network response to check if network created?
Created superman_network_tier1 with ID: 1ce4e645-997f-47cf-9903-570ae92f56bb
Using template 7ecce930-30ee-4201-b442-6d376c869b22 
Using service offering 873acd92-328a-4566-afb4-7270650dcfce 
Deployed VM b501f6b0-29f3-4818-80f8-cfbaf78e214f in network: 
7d0dbf7b-f510-4cc0-ae0e-e0947144a49a
Deployed VM b675cefe-2014-47bb-a5b3-a67a6507bc12 in network: 
1ce4e645-997f-47cf-9903-570ae92f56bb
Acquired public ip for batman vm 192.168.100.69
Static Nat enabled on ip 192.168.100.69
Trying SSH Connection: Host:192.168.100.69 User:root
   Port:22 RetryCnt:60===
===SSH to Host 192.168.100.69 port : 22 SUCCESSFUL===
{Cmd: ping -c 1 200.100.5.101 via Host: 192.168.100.69} {returns: [u'PING 
200.100.5.101 (200.100.5.101): 56 data bytes', u'64 bytes from 200.100.5.101: 
seq=0 ttl=62 time=3.703 ms', u'', u'--- 200.100.5.101 ping statistics ---', u'1 
packets transmitted, 1 packets received, 0% packet loss', u'round-trip 
min/avg/max = 3.703/3.703/3.703 ms']}
[u'PING 200.100.5.101 (200.100.5.101): 56 data bytes', u'64 bytes from 
200.100.5.101: seq=0 ttl=62 time=3.703 ms', u'', u'--- 200.100.5.101 ping 
statistics ---', u'1 packets transmitted, 1 packets received, 0% packet loss', 
u'round-trip min/avg/max = 3.703/3.703/3.703 ms']
{Cmd: ping -c 1 200.100.1.101 via Host: 192.168.100.69} {returns: [u'PING 
200.100.1.101 (200.100.1.101): 56 data bytes', u'64 bytes from 200.100.1.101: 
seq=0 ttl=64 time=0.033 ms', u'', u'--- 200.100.1.101 ping statistics ---', u'1 
packets transmitted, 1 packets received, 0% packet loss', u'round-trip 
min/avg/max = 0.033/0.033/0.033 ms']}
[u'PING 200.100.1.101 (200.100.1.101): 56 data bytes', u'64 bytes from 
200.100.1.101: seq=0 ttl=64 time=0.033 ms', u'', u'--- 200.100.1.101 ping 
statistics ---', u'1 packets transmitted, 1 packets received, 0% packet loss', 
u'round-trip min/avg/max = 0.033/0.033/0.033 ms']
Test successful clearing VMs
Test successful clearing VPC Tiers
Test successful clearing VPCs
=== TestName: test_01_dynamic_routing_using_ospf | Status : SUCCESS ===

===final results are now copied to: /tmp//MarvinLogs/test_ospf_1POT15===



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


[GitHub] cloudstack pull request: CLOUDSTACK-9348: Use non-blocking SSL han...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1493#issuecomment-215309861
  
Failed to build.
```
---
 T E S T S
---
Running com.cloud.utils.testcase.NioTest
2016-04-28 06:23:24,581 INFO  [utils.testcase.NioTest] (main:) Setting up 
Benchmark Test
2016-04-28 06:23:24,879 INFO  [utils.nio.NioServer] (main:) NioConnection 
started and listening on /0:0:0:0:0:0:0:0:58798
2016-04-28 06:23:24,886 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-1:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,886 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-2:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,887 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-4:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,890 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-5:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,891 INFO  [utils.nio.NioClient] (NioClientHandler-1:) 
Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,892 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-6:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,892 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-3:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,893 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-7:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,894 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-8:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,895 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-10:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,924 DEBUG [utils.crypt.EncryptionSecretKeyChecker] 
(pool-1-thread-1:) Encryption Type: null
2016-04-28 06:23:24,928 INFO  [utils.nio.NioClient] (NioClientHandler-2:) 
Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,933 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-11:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,933 WARN  [utils.nio.Link] (pool-1-thread-1:) SSL: Fail 
to find the generated keystore. Loading fail-safe one to continue.
2016-04-28 06:23:24,939 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-13:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,941 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-14:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,944 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-12:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,944 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-15:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,944 INFO  [utils.nio.NioClient] (NioClientHandler-3:) 
Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,945 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-16:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,946 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-9:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,946 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-17:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,946 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-18:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,947 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-19:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,947 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-20:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,948 INFO  [utils.nio.NioClient] (NioClientHandler-4:) 
Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,949 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-21:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,949 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-22:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,949 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-23:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,977 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-25:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,977 INFO  [utils.testcase.NioTest] 
(MaliciousNioClientHandler-24:) Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,981 INFO  [utils.nio.NioClient] (NioClientHandler-5:) 
Connecting to 127.0.0.1:58798
2016-04-28 06:23:24,996 DEBUG [utils.testcase.NioTest] (Thread-0:) 0/5 
tests done. Waiting for completion
2016-04-28 06:23:25,103 WARN  [utils.nio.Link] (pool-1-thread-1:) SSL: Fail 
to find the generated keystore. Loading fail-safe one to continue.
2016-04-28 06:23:25,161 WARN  [utils.nio.Link] (pool-1-thread-1:) SSL: Fail 
to find the generated keystore. Loading fail-safe one to continue.
2016-04-28 06:23:25,211 WARN  [utils.nio.Link] (pool-1-thread-1:) SSL: Fail 
to find the generated keystore. Loading fail-safe one to continue.
2016-04-28 06:23:25,282 WARN  

[GitHub] cloudstack pull request: [CLOUDSTACK-9207] Test to verify restarti...

2016-04-27 Thread sanju1010
Github user sanju1010 commented on the pull request:

https://github.com/apache/cloudstack/pull/1304#issuecomment-215309683
  
Thanks @swill , I will fix the error and update the PR. Thanks for taking 
your time and running it on your CI.


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


[GitHub] cloudstack pull request: CLOUDSTACK-9349: Enable root disk detach ...

2016-04-27 Thread nitt10prashant
Github user nitt10prashant commented on the pull request:

https://github.com/apache/cloudstack/pull/1500#issuecomment-215308516
  
LGTM for test code based on code review 


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


[GitHub] cloudstack pull request: CLOUDSTACK-9323: Fix cancel host maintena...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1454#issuecomment-215303942
  
Sorry for the delay on this one guys.  I think this one is ready now...


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


[GitHub] cloudstack pull request: CLOUDSTACK-8562: Dynamic Role-Based API C...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1489#issuecomment-215291402
  
The CI results show this PR to be in pretty good shape.  We have one LGTM 
and lots of commentary.  Can we get a summary of any concerns and get our code 
reviews in?  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 pull request: CLOUDSTACK-8562: Dynamic Role-Based API C...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1489#issuecomment-215290621
  


### CI RESULTS

```
Tests Run: 100
  Skipped: 1
   Failed: 0
   Errors: 0
```



**Associated Uploads**

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

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

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


Uploads will be available until `2016-06-28 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.
---


Re: Resizing a volume

2016-04-27 Thread Tutkowski, Mike
I opened the following ticket:

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

From: Tutkowski, Mike 
Sent: Wednesday, April 27, 2016 7:12 PM
To: dev@cloudstack.apache.org
Subject: Re: Resizing a volume

It appears the offending code was added here: 
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=d6e21f74163212b198731ddf23dd48bc4c787b84

From: Tutkowski, Mike 
Sent: Wednesday, April 27, 2016 5:33 PM
To: dev@cloudstack.apache.org
Subject: Re: Resizing a volume

I see the problem.

It's in storage.js

if (jsonObj.hypervisor == "KVM" || jsonObj.hypervisor == "XenServer" || 
jsonObj.hypervisor == "VMware") {
if (jsonObj.state == "Ready" || jsonObj.state == "Allocated") {
allowedActions.push("resize");
}
}

jsonObj.hypervisor is equal to undefined (it has the correct hypervisor type 
when I'm logged in as an admin).

We appear to have other code in the vicinity that depends on jsonObj.hypervisor 
and is probably misbehaving.

Maybe a GUI developer can fill us in as to what's expected here?

From: Tutkowski, Mike 
Sent: Wednesday, April 27, 2016 5:13 PM
To: dev@cloudstack.apache.org
Subject: Re: Resizing a volume

Here's a pic:

http://imgur.com/2k380Yd

It's for a volume on KVM, but I see the same behavior on XenServer and VMware, 
too.

I'm logged in as a regular user.

From: Tutkowski, Mike 
Sent: Wednesday, April 27, 2016 4:23 PM
To: dev@cloudstack.apache.org
Subject: Re: Resizing a volume

Hi Wido,

I'm referring to the commands.properties file, where you can set permissions 
for a given API.

However, I see volumeResize has the following setting, which should enable 
users to access it:

resizeVolume=15

Perhaps there's just a bug in the GUI not showing the button?

Talk to you later,
Mike

From: Wido den Hollander 
Sent: Wednesday, April 27, 2016 1:33 AM
To: Tutkowski, Mike; dev@cloudstack.apache.org
Subject: Re: Resizing a volume

> Op 26 april 2016 om 22:37 schreef "Tutkowski, Mike" 
> :
>
>
> ??Hi,
>
>
> I noticed that by default non-admins cannot resize a volume to a different 
> disk offering.
>
>
> Anyone know why that's the default behavior? I would think that would be an 
> expected operation for end users.
>

You mean that it's a setting? I'd say it is preferred that they can do so 
indeed by default.

Wido

>
> Thanks,
>
> Mike


Re: Resizing a volume

2016-04-27 Thread Tutkowski, Mike
It appears the offending code was added here: 
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=d6e21f74163212b198731ddf23dd48bc4c787b84

From: Tutkowski, Mike 
Sent: Wednesday, April 27, 2016 5:33 PM
To: dev@cloudstack.apache.org
Subject: Re: Resizing a volume

I see the problem.

It's in storage.js

if (jsonObj.hypervisor == "KVM" || jsonObj.hypervisor == "XenServer" || 
jsonObj.hypervisor == "VMware") {
if (jsonObj.state == "Ready" || jsonObj.state == "Allocated") {
allowedActions.push("resize");
}
}

jsonObj.hypervisor is equal to undefined (it has the correct hypervisor type 
when I'm logged in as an admin).

We appear to have other code in the vicinity that depends on jsonObj.hypervisor 
and is probably misbehaving.

Maybe a GUI developer can fill us in as to what's expected here?

From: Tutkowski, Mike 
Sent: Wednesday, April 27, 2016 5:13 PM
To: dev@cloudstack.apache.org
Subject: Re: Resizing a volume

Here's a pic:

http://imgur.com/2k380Yd

It's for a volume on KVM, but I see the same behavior on XenServer and VMware, 
too.

I'm logged in as a regular user.

From: Tutkowski, Mike 
Sent: Wednesday, April 27, 2016 4:23 PM
To: dev@cloudstack.apache.org
Subject: Re: Resizing a volume

Hi Wido,

I'm referring to the commands.properties file, where you can set permissions 
for a given API.

However, I see volumeResize has the following setting, which should enable 
users to access it:

resizeVolume=15

Perhaps there's just a bug in the GUI not showing the button?

Talk to you later,
Mike

From: Wido den Hollander 
Sent: Wednesday, April 27, 2016 1:33 AM
To: Tutkowski, Mike; dev@cloudstack.apache.org
Subject: Re: Resizing a volume

> Op 26 april 2016 om 22:37 schreef "Tutkowski, Mike" 
> :
>
>
> ??Hi,
>
>
> I noticed that by default non-admins cannot resize a volume to a different 
> disk offering.
>
>
> Anyone know why that's the default behavior? I would think that would be an 
> expected operation for end users.
>

You mean that it's a setting? I'd say it is preferred that they can do so 
indeed by default.

Wido

>
> Thanks,
>
> Mike


[GitHub] cloudstack pull request: [CLOUDSTACK-9328]: Fix vlan issues from t...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1455#issuecomment-215266469
  
I have tested this and I think we are ready.  Can you please do a force 
push to kick off jenkins again so we can get this PR all green?  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 pull request: [CLOUDSTACK-9328]: Fix vlan issues from t...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1455#issuecomment-215266162
  


### CI RESULTS

```
Tests Run: 4
  Skipped: 0
   Failed: 0
   Errors: 0
```



**Associated Uploads**

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

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


Uploads will be available until `2016-06-27 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.
---


Re: Resizing a volume

2016-04-27 Thread Tutkowski, Mike
I see the problem.

It's in storage.js

if (jsonObj.hypervisor == "KVM" || jsonObj.hypervisor == "XenServer" || 
jsonObj.hypervisor == "VMware") {
if (jsonObj.state == "Ready" || jsonObj.state == "Allocated") {
allowedActions.push("resize");
}
}

jsonObj.hypervisor is equal to undefined (it has the correct hypervisor type 
when I'm logged in as an admin).

We appear to have other code in the vicinity that depends on jsonObj.hypervisor 
and is probably misbehaving.

Maybe a GUI developer can fill us in as to what's expected here?

From: Tutkowski, Mike 
Sent: Wednesday, April 27, 2016 5:13 PM
To: dev@cloudstack.apache.org
Subject: Re: Resizing a volume

Here's a pic:

http://imgur.com/2k380Yd

It's for a volume on KVM, but I see the same behavior on XenServer and VMware, 
too.

I'm logged in as a regular user.

From: Tutkowski, Mike 
Sent: Wednesday, April 27, 2016 4:23 PM
To: dev@cloudstack.apache.org
Subject: Re: Resizing a volume

Hi Wido,

I'm referring to the commands.properties file, where you can set permissions 
for a given API.

However, I see volumeResize has the following setting, which should enable 
users to access it:

resizeVolume=15

Perhaps there's just a bug in the GUI not showing the button?

Talk to you later,
Mike

From: Wido den Hollander 
Sent: Wednesday, April 27, 2016 1:33 AM
To: Tutkowski, Mike; dev@cloudstack.apache.org
Subject: Re: Resizing a volume

> Op 26 april 2016 om 22:37 schreef "Tutkowski, Mike" 
> :
>
>
> ??Hi,
>
>
> I noticed that by default non-admins cannot resize a volume to a different 
> disk offering.
>
>
> Anyone know why that's the default behavior? I would think that would be an 
> expected operation for end users.
>

You mean that it's a setting? I'd say it is preferred that they can do so 
indeed by default.

Wido

>
> Thanks,
>
> Mike


Re: Resizing a volume

2016-04-27 Thread Tutkowski, Mike
Here's a pic:

http://imgur.com/2k380Yd

It's for a volume on KVM, but I see the same behavior on XenServer and VMware, 
too.

I'm logged in as a regular user.

From: Tutkowski, Mike 
Sent: Wednesday, April 27, 2016 4:23 PM
To: dev@cloudstack.apache.org
Subject: Re: Resizing a volume

Hi Wido,

I'm referring to the commands.properties file, where you can set permissions 
for a given API.

However, I see volumeResize has the following setting, which should enable 
users to access it:

resizeVolume=15

Perhaps there's just a bug in the GUI not showing the button?

Talk to you later,
Mike

From: Wido den Hollander 
Sent: Wednesday, April 27, 2016 1:33 AM
To: Tutkowski, Mike; dev@cloudstack.apache.org
Subject: Re: Resizing a volume

> Op 26 april 2016 om 22:37 schreef "Tutkowski, Mike" 
> :
>
>
> ??Hi,
>
>
> I noticed that by default non-admins cannot resize a volume to a different 
> disk offering.
>
>
> Anyone know why that's the default behavior? I would think that would be an 
> expected operation for end users.
>

You mean that it's a setting? I'd say it is preferred that they can do so 
indeed by default.

Wido

>
> Thanks,
>
> Mike


Re: CaaS in CloudStack with Kubernetes

2016-04-27 Thread Nux!
Excellent, good job, you've made me curious. :)

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Sebastien Goasguen" 
> To: dev@cloudstack.apache.org
> Sent: Wednesday, 27 April, 2016 19:15:42
> Subject: Re: CaaS in CloudStack with Kubernetes

>> On Apr 27, 2016, at 4:06 PM, Nux!  wrote:
>> 
>> Hello,
>> 
>> Very nice, but I am somewhat surprised! I thought we were not going after
>> docker/containers/etc and let others (CoreOS etc) do it?
>> What has changed?
>> 
> 
> Nothing has changed,
> 
> The solution we developed is based on CoreOS. We use it as base OS to deploy
> Kubernetes.
> We expose the k8s API, there is no API wrapper or anything like that.
> 
> As a matter of fact we use your coreOS templates :) and we even patched them:
> https://github.com/coreos/coreos-overlay/commit/136b3e248a79817d9ccf0ab3350c9ddfe4e7abac
> 
> Though i shamelessly took a PR from exoscale.
> 
> What we have done is a bit of automation in cloudstack to create a k8s 
> cluster ,
> so it looks like Google GKE offering.
> 
> Our automation could actually be used to create any sort of clusters.
> 
> In addition we are putting some final touches on a CloudStack provider in
> Kubernetes code (which we will submit as PR in coming days or week).
> 
> It is not yet open because we need to tighten a few things (namely secure 
> access
> to k8s), but it will be soon.
> 
>> Lucian
>> 
>> --
>> Sent from the Delta quadrant using Borg technology!
>> 
>> Nux!
>> www.nux.ro
>> 
>> - Original Message -
>>> From: "Sebastien Goasguen" 
>>> To: market...@cloudstack.apache.org
>>> Cc: dev@cloudstack.apache.org
>>> Sent: Friday, 22 April, 2016 17:02:22
>>> Subject: CaaS in CloudStack with Kubernetes
>> 
>>> Hi folks,
>>> 
>>> I have been quite silent this past few weeks because aside from voting in a 
>>> new
>>> VP (soon to be announced), I  have been hard at work for my new endeavors 
>>> with
>>> Skippbox.
>>> 
>>> I am quite excited that today we could not wait and Skippbox together with
>>> Shapeblue announced a preview of a Kubernetes/CloudStack integration:
>>> http://www.benzinga.com/pressreleases/16/04/g7872516/shapeblue-harness-the-power-of-kubernetes-and-apache-cloudstack-to-give
>>> 
>>> This is currently still a by request preview, but once we are done with much
>>> better testing and even tighter integration, the code will be open sourced 
>>> as a
>>> CloudStack plugin.
>>> 
>>> I wouldn’t mind couple supportive tweets and if you want a demo before you 
>>> can
>>> run it yourself, ping me.
>>> 
>>> Cheers,
>>> 
> >> -Sebastien


Re: Resizing a volume

2016-04-27 Thread Tutkowski, Mike
Hi Wido,

I'm referring to the commands.properties file, where you can set permissions 
for a given API.

However, I see volumeResize has the following setting, which should enable 
users to access it:

resizeVolume=15

Perhaps there's just a bug in the GUI not showing the button?

Talk to you later,
Mike

From: Wido den Hollander 
Sent: Wednesday, April 27, 2016 1:33 AM
To: Tutkowski, Mike; dev@cloudstack.apache.org
Subject: Re: Resizing a volume

> Op 26 april 2016 om 22:37 schreef "Tutkowski, Mike" 
> :
>
>
> ??Hi,
>
>
> I noticed that by default non-admins cannot resize a volume to a different 
> disk offering.
>
>
> Anyone know why that's the default behavior? I would think that would be an 
> expected operation for end users.
>

You mean that it's a setting? I'd say it is preferred that they can do so 
indeed by default.

Wido

>
> Thanks,
>
> Mike


[GitHub] cloudstack pull request: Log asynchronous responses in the api log

2016-04-27 Thread kiwiflyer
Github user kiwiflyer commented on the pull request:

https://github.com/apache/cloudstack/pull/1522#issuecomment-215248091
  
@nathanejohnson This is a nice addition that will enable easier tracing of 
events as we pull them into logstash. So those out there using async job calls 
should greatly benefit from this for jobid tracing.

//cc @swill @pdube  @PaulAngus


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


[GitHub] cloudstack pull request: CLOUDSTACK-8302: Removing snapshots on RB...

2016-04-27 Thread kiwiflyer
Github user kiwiflyer commented on the pull request:

https://github.com/apache/cloudstack/pull/1230#issuecomment-215242253
  
Manual testing against a 4.8 hardware lab with Ceph Primary Storage.

2 volume snapshots triggered:
rbd snap ls -p rbdnjcloudhost cabf9a9e-7ac3-44b5-a3bb-02b820bed376
SNAPID NAMESIZE 
70 6efbba74-372c-4bd7-95bb-e539524e7209 5120 MB 
71 de6acd1b-ccac-4d3f-80aa-b40b05b86a63 5120 MB 

both snapshots are deleted
rbd snap ls -p rbdnjcloudhost cabf9a9e-7ac3-44b5-a3bb-02b820bed376
(no results as expected)

Works as expected. Functional tests are good.


---
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: Jenkins

2016-04-27 Thread Rafael Weingärtner
That is probably some misconfigurations at the Maven of the Jenkins’ VM.
That seems to be a username and password configuration to access some
cache/local repository that is under the ASF premises.

Does anyone have access to those VMs? So we could login and fix it.



I also noticed the Java 8, but our maven configuration will compile the
code with Java 7 compatibility (or java 6, I do not from right now the
specific version).



On Wed, Apr 27, 2016 at 6:00 PM, Will Stevens 
wrote:

> Seeing a few jobs with this result recently.
>
> [cloudstack-pr-analysis] $
>
> /home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3/bin/mvn
> clean --projects=org.apache.cloudstack:cloudstack
> org.apache.rat:apache-rat-plugin:0.10:check[ERROR] Error executing
> Maven.[ERROR] 1 problem was encountered while building the effective
> settings[FATAL] Non-parseable settings /home/jenkins/.m2/settings.xml:
> unexpected character in markup % (position: START_TAG seen
> ...\n <%... @14:18)  @
> /home/jenkins/.m2/settings.xml, line 14, column 18
>
> Build step 'Invoke top-level Maven targets' marked build as failure
>
>
> Here are a couple:
> https://builds.apache.org/job/cloudstack-pr-analysis/1057/console
> https://builds.apache.org/job/cloudstack-pr-analysis/1056/console
>
> Do we know what the deal is with this?
>
> Also, I noticed that Jenkins is building with Java 8.  I thought that was
> not yet supported, is that a good idea?
>
> Thx...
>



-- 
Rafael Weingärtner


Re: Jenkins issue

2016-04-27 Thread Will Stevens
I just asked the dev list the same thing.  Here are two more examples #1515
and #1522:

https://builds.apache.org/job/cloudstack-pr-analysis/1057/console
https://builds.apache.org/job/cloudstack-pr-analysis/1056/console

One other thing that I noticed is that Jenkins is building with Java 8,
which I didn't think was supported yet...

*Will STEVENS*
Lead Developer

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

On Wed, Apr 27, 2016 at 4:42 PM, Nathan Johnson  wrote:

> I am aware that there have been some transient issues with Jenkins, but I
> am repeatedly seeing this error and I suspect this might be something
> different:
>
> Unpacking
> https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.3.3/apache-maven-3.3.3-bin.zip
>  to
> /home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3
> on jenkins-test-971
>
> [cloudstack-pr-analysis] $
> /home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3/bin/mvn
> clean --projects=org.apache.cloudstack:cloudstack
> org.apache.rat:apache-rat-plugin:0.10:check
>
> [ERROR] Error executing Maven.
>
> [ERROR] 1 problem was encountered while building the effective settings
>
> [FATAL] Non-parseable settings /home/jenkins/.m2/settings.xml: unexpected
> character in markup % (position: START_TAG seen ...\n
>  <%... @14:18)  @ /home/jenkins/.m2/settings.xml, line 14, column
> 18
>
> I keep getting the same error.  I noticed a comment from rafaelweingartner
> on
> this PR:
>
> https://github.com/apache/cloudstack/pull/1466#issuecomment-214861439
>
> Does anyone have any thoughts on this?
>
> Thank you,
> Nathan Johnson


Jenkins

2016-04-27 Thread Will Stevens
Seeing a few jobs with this result recently.

[cloudstack-pr-analysis] $
/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3/bin/mvn
clean --projects=org.apache.cloudstack:cloudstack
org.apache.rat:apache-rat-plugin:0.10:check[ERROR] Error executing
Maven.[ERROR] 1 problem was encountered while building the effective
settings[FATAL] Non-parseable settings /home/jenkins/.m2/settings.xml:
unexpected character in markup % (position: START_TAG seen
...\n <%... @14:18)  @
/home/jenkins/.m2/settings.xml, line 14, column 18

Build step 'Invoke top-level Maven targets' marked build as failure


Here are a couple:
https://builds.apache.org/job/cloudstack-pr-analysis/1057/console
https://builds.apache.org/job/cloudstack-pr-analysis/1056/console

Do we know what the deal is with this?

Also, I noticed that Jenkins is building with Java 8.  I thought that was
not yet supported, is that a good idea?

Thx...


[GitHub] cloudstack pull request: L10n update 4.8 20160422

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1515#issuecomment-215227139
  
I see another PR with the same error, so I doubt it is your PR.


---
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: L10n update 4.8 20160422

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1515#issuecomment-215226141
  
Well Jenkins just does not like us today.  Can you review the error and see 
if it is a valid error and try again?


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


[GitHub] cloudstack pull request: [CLOUDSTACK-9207] Test to verify restarti...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1304#issuecomment-215224845
  
Don't worry about the connectivity issues, that seems to be my environment 
right now.  The ERROR you do need to fix because that is a problem.  Cheers...


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


[GitHub] cloudstack pull request: [CLOUDSTACK-9207] Test to verify restarti...

2016-04-27 Thread swill
Github user swill commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1304#discussion_r61333278
  
--- Diff: test/integration/component/test_vpc_network.py ---
@@ -2683,6 +2687,65 @@ def setUp(self):
 def tearDown(self):
 return
 
+def listRouter(self):
+routers = Router.list(
+self.apiclient,
+vpcid=self.vpc.id,
+listall="true"
+)
+self.assertEqual(validateList(routers)[0], PASS, "Invalid router 
response")
+return routers[0]
+
+def secondaryIP(self, router):
+hosts = list_hosts(
+self.apiclient,
+id=router.hostid
+)
+self.assertEqual(validateList(hosts)[0], PASS, "Invalid host 
response")
+host = hosts[0]
+if self.hypervisor.lower() in ('vmware', 'hyperv'):
+# SSH into system vms is done via management server for Vmware 
and
+# Hyper-V
+result = get_process_status(
+self.apiclient.connection.mgtSvr,
+22,
+self.apiclient.connection.user,
+self.apiclient.connection.passwd,
+router.privateip,
+"ip addr show",
+hypervisor=self.hypervisor
+)
+else:
+try:
+host.user, host.passwd = get_host_credentials(
+self.config, host.ipaddress
+)
+result = get_process_status(
+host.ipaddress,
+22,
+host.user,
+host.passwd,
+router.linklocalip,
+"ip addr show"
+)
+except KeyError:
+self.skipTest("Marvin configuration has no host 
credentials to check router services")
+return result
+
+def validateResult(self, output):
+ip = self.public_ip_1.ipaddress.ipaddress
+reg = re.compile(ip)
+for line in output:
+m = reg.search(line)
+if m:
+break
+if m.group(0) == ip and re.search("secondary", line):
--- End diff --

`m` is not guaranteed to be set.  You need to check `if m and len(m.group) 
> 0 ...` before you can try to access it.  Check the `Error` in the CI result.  


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


Jenkins issue

2016-04-27 Thread Nathan Johnson
I am aware that there have been some transient issues with Jenkins, but I
am repeatedly seeing this error and I suspect this might be something
different:

Unpacking 
https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.3.3/apache-maven-3.3.3-bin.zip
 to 
/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3
 on jenkins-test-971

[cloudstack-pr-analysis] $ 
/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3/bin/mvn
 clean --projects=org.apache.cloudstack:cloudstack 
org.apache.rat:apache-rat-plugin:0.10:check

[ERROR] Error executing Maven.

[ERROR] 1 problem was encountered while building the effective settings

[FATAL] Non-parseable settings /home/jenkins/.m2/settings.xml: unexpected 
character in markup % (position: START_TAG seen ...\n 
<%... @14:18)  @ /home/jenkins/.m2/settings.xml, line 14, column 18

I keep getting the same error.  I noticed a comment from rafaelweingartner on
this PR:

https://github.com/apache/cloudstack/pull/1466#issuecomment-214861439

Does anyone have any thoughts on this?

Thank you,
Nathan Johnson

[GitHub] cloudstack pull request: [CLOUDSTACK-9207] Test to verify restarti...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1304#issuecomment-215221441
  


### CI RESULTS

```
Tests Run: 92
  Skipped: 0
   Failed: 4
   Errors: 1
```

**Summary of the problem(s):**
```
ERROR: Test restart network with cleanup
--
Traceback (most recent call last):
  File 
"/data/git/cs2/cloudstack/test/integration/component/test_vpc_network.py", line 
2848, in test_restart_network_with_cleanup
self.validateResult(result)
  File 
"/data/git/cs2/cloudstack/test/integration/component/test_vpc_network.py", line 
2742, in validateResult
if m.group(0) == ip and re.search("secondary", line):
AttributeError: 'NoneType' object has no attribute 'group'
--
Additional details in: /tmp/MarvinLogs/test_vpc_network_21FMEY/results.txt
```

```
FAIL: Test redundant router internals
--
Traceback (most recent call last):
  File 
"/data/git/cs2/cloudstack/test/integration/smoke/test_routers_network_ops.py", 
line 483, in test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false
"Attempt to retrieve google.com index page should be successful once 
rule is added!"
AssertionError: Attempt to retrieve google.com index page should be 
successful once rule is added!
--
Additional details in: /tmp/MarvinLogs/test_vpc_network_21FMEY/results.txt
```

```
FAIL: Test network rules after starting a VpcVr that
--
Traceback (most recent call last):
  File 
"/data/git/cs2/cloudstack/test/integration/component/test_vpc_network.py", line 
2465, in test_02_start_vm_network_gc
"Ping to outside world from VM should be successful"
AssertionError: Ping to outside world from VM should be successful
--
Additional details in: /tmp/MarvinLogs/test_vpc_network_21FMEY/results.txt
```

```
FAIL: Test Stop all the Vms that are part of the a Network
--
Traceback (most recent call last):
  File 
"/data/git/cs2/cloudstack/test/integration/component/test_vpc_network.py", line 
2557, in test_03_restart_vpcvr
(self.public_ip_1.ipaddress.ipaddress, e))
AssertionError: Failed to SSH into VM - 192.168.23.54, SSH connection has 
Failed. Waited 600s. Error is SSH Connection Failed
--
Additional details in: /tmp/MarvinLogs/test_vpc_network_21FMEY/results.txt
```

```
FAIL: Test update Network that is part of a VPC to a network
--
Traceback (most recent call last):
  File 
"/data/git/cs2/cloudstack/test/integration/component/test_vpc_network.py", line 
1910, in test_01_network_services_upgrade
"Ping to outside world from VM should be successful"
AssertionError: Ping to outside world from VM should be successful
--
Additional details in: /tmp/MarvinLogs/test_vpc_network_21FMEY/results.txt
```



**Associated Uploads**

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

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

**`/tmp/MarvinLogs/test_vpc_routers_62M97S:`**
* 

[GitHub] cloudstack pull request: kvm: Aqcuire lock when running security g...

2016-04-27 Thread rhtyd
Github user rhtyd commented on the pull request:

https://github.com/apache/cloudstack/pull/1408#issuecomment-215217268
  
@wido I tested your original PR and the current updated PR, the locking 
never happened on my test env (Ubuntu x64).

I read the manpage, and found that when you open a file twice `flock` will 
treat both FDs independently while `fcntl` (the lockf usage) treats them as 
FDs. This means that when two processes could run the python script at the same 
time, no locking would actually occur.

I wrote a test program to demonstrate this: (for testing you may replace 
flock with lockf and see for yourself that it does not lock at all)
https://gist.github.com/rhtyd/5d9983e7d58311ba8e517eefd931a507

So, my suggestion is to:
- use flock instead of lockf, assuming and likely the file exists on local 
filesystem we can use `flock` with no issues
- use the previously used open instead of with open, as with open syntax 
closes file when the statements under it return


---
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: L10n update 4.8 20160422

2016-04-27 Thread milamberspace
Github user milamberspace commented on the pull request:

https://github.com/apache/cloudstack/pull/1515#issuecomment-215215852
  
@swill re-done.


---
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: Log asynchronous responses in the api log

2016-04-27 Thread nathanejohnson
GitHub user nathanejohnson opened a pull request:

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

Log asynchronous responses in the api log

Currently API responses for synchronous calls are logged, but asynchronous 
call responses are not.  This pull request makes a minor modification that logs 
the response including the JobId of all asynchronous requests.

As an example, here is what a stopVirtualMachine request looked like in the 
logs:

2016-04-27 10:43:11,084 INFO  [a.c.c.a.ApiServer] 
(catalina-exec-3:ctx-37d9f693 ctx-d2368de3) (logid:3a0fad97) (userId=2 
accountId=2 sessionId=AF8B1F726ACB5C3A637B8B300AA218A7) 10.103.0.207 -- GET 
command=stopVirtualMachine=f63b6fcc-e0b0-480f-8f7a-cba329634ba1=false=json&_=1461771791036
 200 

After this modification, here is what the logs look like:

2016-04-27 13:37:11,338 INFO  [a.c.c.a.ApiServer] 
(catalina-exec-6:ctx-915b5c84 ctx-a03152fa) (logid:66249df0) (userId=2 
accountId=2 sessionId=9EF127EED5CA6E74797DFE487D980FAF) 10.103.0.207 -- GET 
command=stopVirtualMachine=f63b6fcc-e0b0-480f-8f7a-cba329634ba1=false=json&_=1461782231194
 200 
{"stopvirtualmachineresponse":{"jobid":"5b9f4a9b-eabe-4fa4-849d-3d004bb65634"}}

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

$ git pull https://github.com/myENA/cloudstack logjobid_master

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

https://github.com/apache/cloudstack/pull/1522.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 #1522


commit f0ed8b82d1da24ff1a2aa44ec102345e2131d0c8
Author: Simon Weller 
Date:   2016-03-24T19:45:09Z

Merge pull request #3 from apache/master

Rebase

commit fd9e0e434ca3849407e3958a7aadfa7e5ff1fe3d
Author: Simon Weller 
Date:   2016-04-04T14:29:03Z

Merge pull request #5 from apache/master

Update from ACS

commit 295c4e223ab449c093822b5f0d9b4d4b040f4752
Author: Simon Weller 
Date:   2016-04-12T19:55:44Z

Merge pull request #6 from apache/master

Merge from ACS master

commit 3f85da5d0e174722c44b87a99f0a8d2fe57cd4df
Author: Aaron Hurt 
Date:   2016-04-26T18:42:34Z

Merge remote-tracking branch 'upstream/master'

commit 3e2a5f894c7383085a81fdafa653a5c8a5854b39
Author: Nathan Johnson 
Date:   2016-04-27T19:49:50Z

Log responses from asynchronous api commands

This is mainly useful so that we can see the job ids in the logs
whenever the job is created via the API.




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


[GitHub] cloudstack pull request: CLOUDSTACK-8562: Dynamic Role-Based API C...

2016-04-27 Thread rhtyd
Github user rhtyd commented on the pull request:

https://github.com/apache/cloudstack/pull/1489#issuecomment-215197356
  
Rebased against latest master, please consider this for merge

Performed final rounds of testing:
- Build/maven, unit and integration tests
- Upgrade tests from old deployed to new using packages
- Major regression tests against before/after upgrade LDAP, SAML2 and 
native cloudstack accounts, listApis regression testing, along with API/CLI 
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 pull request: Kvm plugin restructure

2016-04-27 Thread rhtyd
Github user rhtyd commented on the pull request:

https://github.com/apache/cloudstack/pull/1521#issuecomment-215191105
  
@DaanHoogland I'm not sure about others, but gradle has become most popular 
and widely-support in modern java development
@jburwell agree, the discussion here is to evaluate how useful it would be 
to move to maven standard layout if the build chain gets migrated (to say 
gradle, sbt or something else) when doing this adds pain to the 
backporting/forward-porting process at the cost of a cosmetic 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 pull request: CLOUDSTACK-9142 Migrate VM changes xmlDes...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1348#issuecomment-215185737
  
Ok perfect.  I will add this to my merge queue.  Thanks for clarifying 
guys...


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


[GitHub] cloudstack pull request: CLOUDSTACK-9289:Automation for feature de...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1417#issuecomment-215184791
  
@nitt10prashant I have to admit, I am confused on this one.  I have the 
latest Marvin installed that is generated when building this PR.

```
Installing Marvin
DEPRECATION: --allow-external has been deprecated and will be removed in 
the future. Due to changes in the repository protocol, it no longer has any 
effect.
Processing ./tools/marvin/dist/Marvin-4.9.0-SNAPSHOT.tar.gz
Requirement already up-to-date: mysql-connector-python>=1.1.6 in 
/usr/lib/python2.7/site-packages (from Marvin===4.9.0-SNAPSHOT)
Collecting requests>=2.2.1 (from Marvin===4.9.0-SNAPSHOT)
  Downloading requests-2.9.1-py2.py3-none-any.whl (501kB)
100% 
|████████████████████████████████|
 501kB 1.4MB/s 
Collecting paramiko>=1.13.0 (from Marvin===4.9.0-SNAPSHOT)
  Downloading paramiko-1.16.0-py2.py3-none-any.whl (169kB)
100% 
|████████████████████████████████|
 174kB 3.1MB/s 
Requirement already up-to-date: nose>=1.3.3 in 
/usr/lib/python2.7/site-packages/nose-1.3.7-py2.7.egg (from 
Marvin===4.9.0-SNAPSHOT)
Collecting ddt>=0.4.0 (from Marvin===4.9.0-SNAPSHOT)
  Downloading ddt-1.0.1-py2.py3-none-any.whl
Collecting pyvmomi>=5.5.0 (from Marvin===4.9.0-SNAPSHOT)
  Downloading pyvmomi-6.0.0.2016.4.tar.gz (216kB)
100% 
|████████████████████████████████|
 225kB 2.7MB/s 
Collecting netaddr>=0.7.14 (from Marvin===4.9.0-SNAPSHOT)
  Downloading netaddr-0.7.18-py2.py3-none-any.whl (1.5MB)
100% 
|████████████████████████████████|
 1.5MB 614kB/s 
Collecting ecdsa>=0.11 (from paramiko>=1.13.0->Marvin===4.9.0-SNAPSHOT)
  Downloading ecdsa-0.13-py2.py3-none-any.whl (86kB)
100% 
|████████████████████████████████|
 92kB 2.5MB/s 
Requirement already up-to-date: pycrypto!=2.4,>=2.1 in 
/usr/lib64/python2.7/site-packages (from 
paramiko>=1.13.0->Marvin===4.9.0-SNAPSHOT)
Collecting six>=1.7.3 (from pyvmomi>=5.5.0->Marvin===4.9.0-SNAPSHOT)
  Downloading six-1.10.0-py2.py3-none-any.whl
Building wheels for collected packages: Marvin, pyvmomi
  Running setup.py bdist_wheel for Marvin ... done
  Stored in directory: 
/root/.cache/pip/wheels/7f/5a/37/7f723796f0a05b8f4a5eb63ebe90f381663e638e7556f46916
  Running setup.py bdist_wheel for pyvmomi ... done
  Stored in directory: 
/root/.cache/pip/wheels/b8/4a/84/b57aa91d338fdb54c766ef9d3c4b8d7c7a9f6b0da53e7b112d
Successfully built Marvin pyvmomi
Installing collected packages: requests, ecdsa, paramiko, ddt, six, 
pyvmomi, netaddr, Marvin
  Found existing installation: requests 2.6.0
DEPRECATION: Uninstalling a distutils installed project (requests) has 
been deprecated and will be removed in a future version. This is due to the 
fact that uninstalling a distutils project will only partially uninstall the 
project.
Uninstalling requests-2.6.0:
  Successfully uninstalled requests-2.6.0
  Found existing installation: ecdsa 0.11
DEPRECATION: Uninstalling a distutils installed project (ecdsa) has 
been deprecated and will be removed in a future version. This is due to the 
fact that uninstalling a distutils project will only partially uninstall the 
project.
Uninstalling ecdsa-0.11:
  Successfully uninstalled ecdsa-0.11
  Found existing installation: paramiko 1.12.4
Uninstalling paramiko-1.12.4:
  Successfully uninstalled paramiko-1.12.4
  Found existing installation: six 1.9.0
Uninstalling six-1.9.0:
  Successfully uninstalled six-1.9.0
Successfully installed Marvin-4.9.0-SNAPSHOT ddt-1.0.1 ecdsa-0.13 
netaddr-0.7.18 paramiko-1.16.0 pyvmomi-6.0.0.2016.4 requests-2.9.1 six-1.10.0
```

I get the same result I got before, so I tried to install it manually to 
make sure everything was setup.

```
# pip install --upgrade 
/data/git/cs1/cloudstack/tools/marvin/dist/Marvin-*.tar.gz
Processing 
/data/git/cs1/cloudstack/tools/marvin/dist/Marvin-4.9.0-SNAPSHOT.tar.gz
Requirement already up-to-date: mysql-connector-python>=1.1.6 in 
/usr/lib/python2.7/site-packages (from Marvin===4.9.0-SNAPSHOT)
Requirement already up-to-date: requests>=2.2.1 in 
/usr/lib/python2.7/site-packages (from Marvin===4.9.0-SNAPSHOT)
Requirement already up-to-date: paramiko>=1.13.0 in 
/usr/lib/python2.7/site-packages (from Marvin===4.9.0-SNAPSHOT)
Requirement already up-to-date: nose>=1.3.3 in 
/usr/lib/python2.7/site-packages/nose-1.3.7-py2.7.egg (from 
Marvin===4.9.0-SNAPSHOT)
Requirement already up-to-date: 

[GitHub] cloudstack pull request: Kvm plugin restructure

2016-04-27 Thread DaanHoogland
Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1521#issuecomment-215183202
  
+ 1 for moving away from maven. How about sbt?


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


[GitHub] cloudstack pull request: CLOUDSTACK-9142 Migrate VM changes xmlDes...

2016-04-27 Thread DaanHoogland
Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1348#issuecomment-215182527
  
No it won't. the fix in here is valid whichever way we go.


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


[GitHub] cloudstack pull request: CLOUDSTACK-9142 Migrate VM changes xmlDes...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1348#issuecomment-215179261
  
Thanks guys.  I am fine with merging it as is, but does it make sense to 
wait a bit to see what the discussion brings up in the #1521 PR?  Or will it 
not affect this PR?


---
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: CaaS in CloudStack with Kubernetes

2016-04-27 Thread Sebastien Goasguen

> On Apr 27, 2016, at 4:06 PM, Nux!  wrote:
> 
> Hello,
> 
> Very nice, but I am somewhat surprised! I thought we were not going after 
> docker/containers/etc and let others (CoreOS etc) do it?
> What has changed?
> 

Nothing has changed,

The solution we developed is based on CoreOS. We use it as base OS to deploy 
Kubernetes.
We expose the k8s API, there is no API wrapper or anything like that.

As a matter of fact we use your coreOS templates :) and we even patched them:
https://github.com/coreos/coreos-overlay/commit/136b3e248a79817d9ccf0ab3350c9ddfe4e7abac

Though i shamelessly took a PR from exoscale.

What we have done is a bit of automation in cloudstack to create a k8s cluster 
, so it looks like Google GKE offering.

Our automation could actually be used to create any sort of clusters.

In addition we are putting some final touches on a CloudStack provider in 
Kubernetes code (which we will submit as PR in coming days or week).

It is not yet open because we need to tighten a few things (namely secure 
access to k8s), but it will be soon.

> Lucian
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> - Original Message -
>> From: "Sebastien Goasguen" 
>> To: market...@cloudstack.apache.org
>> Cc: dev@cloudstack.apache.org
>> Sent: Friday, 22 April, 2016 17:02:22
>> Subject: CaaS in CloudStack with Kubernetes
> 
>> Hi folks,
>> 
>> I have been quite silent this past few weeks because aside from voting in a 
>> new
>> VP (soon to be announced), I  have been hard at work for my new endeavors 
>> with
>> Skippbox.
>> 
>> I am quite excited that today we could not wait and Skippbox together with
>> Shapeblue announced a preview of a Kubernetes/CloudStack integration:
>> http://www.benzinga.com/pressreleases/16/04/g7872516/shapeblue-harness-the-power-of-kubernetes-and-apache-cloudstack-to-give
>> 
>> This is currently still a by request preview, but once we are done with much
>> better testing and even tighter integration, the code will be open sourced 
>> as a
>> CloudStack plugin.
>> 
>> I wouldn’t mind couple supportive tweets and if you want a demo before you 
>> can
>> run it yourself, ping me.
>> 
>> Cheers,
>> 
>> -Sebastien



[GitHub] cloudstack pull request: Kvm plugin restructure

2016-04-27 Thread jburwell
Github user jburwell commented on the pull request:

https://github.com/apache/cloudstack/pull/1521#issuecomment-215177976
  
@rhtyd +1 for Gradle though it would be a large undertaking.  Since 
Gradle's Java plugin natively supports Maven's directory structure, such a 
transition would actually help a migration Gradle.


---
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: CaaS in CloudStack with Kubernetes

2016-04-27 Thread Sebastien Goasguen
let me reply on dev@ to avoid cross posting.

> On Apr 27, 2016, at 4:06 PM, Nux!  wrote:
> 
> Hello,
> 
> Very nice, but I am somewhat surprised! I thought we were not going after 
> docker/containers/etc and let others (CoreOS etc) do it?
> What has changed?
> 
> Lucian
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> - Original Message -
>> From: "Sebastien Goasguen" 
>> To: market...@cloudstack.apache.org
>> Cc: dev@cloudstack.apache.org
>> Sent: Friday, 22 April, 2016 17:02:22
>> Subject: CaaS in CloudStack with Kubernetes
> 
>> Hi folks,
>> 
>> I have been quite silent this past few weeks because aside from voting in a 
>> new
>> VP (soon to be announced), I  have been hard at work for my new endeavors 
>> with
>> Skippbox.
>> 
>> I am quite excited that today we could not wait and Skippbox together with
>> Shapeblue announced a preview of a Kubernetes/CloudStack integration:
>> http://www.benzinga.com/pressreleases/16/04/g7872516/shapeblue-harness-the-power-of-kubernetes-and-apache-cloudstack-to-give
>> 
>> This is currently still a by request preview, but once we are done with much
>> better testing and even tighter integration, the code will be open sourced 
>> as a
>> CloudStack plugin.
>> 
>> I wouldn’t mind couple supportive tweets and if you want a demo before you 
>> can
>> run it yourself, ping me.
>> 
>> Cheers,
>> 
>> -Sebastien



[GitHub] cloudstack pull request: Kvm plugin restructure

2016-04-27 Thread DaanHoogland
Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1521#issuecomment-215176727
  
@rhtyd I agree we should. At the moment we are already in an intermediate 
state. Some projects were moved to maven standard (I only know utils by head 
and the ovm3 plugin was created as such)

The reason to move this project was that I was going to create test only 
resources and didn't want to put them in the resources dir for production code.


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


[LOGISTICS] Move 'apache/cloudstack' to 'apache-cloudstack/cloudstack'

2016-04-27 Thread Will Stevens
This thread is primarily to work out the logistical details with the ASF
Infra team for making this move.

I thought I had members of the ASF Infra team CC'ed earlier, but that was
not the case, so I appologize if this was not on your radar until now.

I have CC'ed in both the ACS dev@ list and the ASF board@ list to try to
keep everyone on the same page and try to avoid any miscommunication or
misunderstandings.  If you have any questions about any of this, please
speak up and I will make sure your questions are answered.

Because I just CC'ed the world into this thread, I will quickly summarize
some of the history here and what we are trying to solve.

Apache CloudStack (ACS) has been struggling with the ability to maintain a
active (monthly) release cycle while also maintaining the quality of the
code.  This is primarily due to the size of the project and the
environmental complexity required to test it.  ACS is a cloud orchestration
software which supports 4+ hypervisors, many hardware appliances and an
endless number of different configurations.  Because of this complexity, it
is impossible for a single team or stack of infrastructure to test the
entire code base.  This means, in order to be effective, we need to be able
to distribute our CI testing and organize ourselves accordingly.

We have tried to work inside the 'apache' github organization, but due to
the lack of permission granularity, it is not possible.  This is because it
is impossible for individuals to be granted permissions specifically on the
ACS repository without the permissions being given globally on the 'apache'
github org.  Understandably, the ASF Infra team is hesitant to grant
individuals permissions on the entire 'apache' github organization.

I have proposed, and we have voted with unanimous support, to move the ACS
repo from 'apache/cloudstack' to 'apache-cloudstack/cloudstack'.  This
repository will remain be a mirror of the official '
git-wip-us.apache.org/repos/asf/cloudstack.git' which will continue to be
the source of truth for the code.

This new github organization will let us take advantage of additional
features which will enable us to better organize our development and
testing lifecycle.

Some of these features include:
- Labels: Trying to coordinate the status of an ever growing number of Pull
Requests (PRs) without labels is daunting.  This will greatly improve our
ability to coordinate CI runs and prioritize PRs that are close to being
ready to merge.
- Status: Currently we are not able to update the status of a PR based on
distributed CI runs.  This makes it difficult to coordinate testing and
makes it hard to know if a PR is ready to merge.
- Close PRs: We currently have no way to close a PR without making a 'fake
commit' to the official ASF repository.  This is both inconvenient and
pollutes our commit history.
- Hooks: The ability to configure post-commit hooks will greatly improve
our ability to automate the kick off or queuing of distributed CI runs and
other verification tools.

This is not an exhaustive list, but is enough to help you understand the
types of features which will greatly improve our workflow.

The ACS PMC would like to have owner rights to this new organizations, but
also welcomes members of the ASF Infra team to have ownership rights as
well.

All that said, here is our current progress:
- All parties are in agreement with the decision to make the move [1][2][3].
- I have talked to Github support about getting the 'mirror' setup after
the move.  They said that a user who has admin access to both organizations can
email them after the transfer and they will setup the mirror for us.
- I have setup the 'apache-cloudstack' github organization.
- I have added Sam, Chris and David (as well as some PMC members) as owners
of the 'apache-cloudstack' org.

Please advise which other ASF members should be added as owners of the '
apache-cloudstack' github organization.

I would like to remind everyone to remain constructive and respectful.
There are a lot of eyes on this and it is in everyone's interest that we
handle this well.

I am looking forward to working with you guys.  Please voice any questions
or concerns in this thread so we can resolve them openly.

Cheers,

Will

Some additional reading if you would like a little more history and
context...

[1]
http://markmail.org/message/4an7nivshnndo25c?q=list:org%2Eapache%2Eincubator%2Ecloudstack-%2A+apache-cloudstack/cloudstack
[2]
http://markmail.org/message/53ct2mma4x4jm6s2?q=list:org%2Eapache%2Eincubator%2Ecloudstack-%2A+External+fork+of+Cloudstack
[3]
http://markmail.org/message/2phudhgcjjo236ay?q=list:org%2Eapache%2Eincubator%2Ecloudstack-%2A+External+fork+of+Cloudstack


[GitHub] cloudstack pull request: Kvm plugin restructure

2016-04-27 Thread rhtyd
Github user rhtyd commented on the pull request:

https://github.com/apache/cloudstack/pull/1521#issuecomment-215172757
  
In my experience when you are doing a lot of backporting or forward-porting 
work, if a plugin/module has got its filesystem structure (for example, due to 
moving to maven standard layout) changed it creates a lot of issues and the 
process becomes painful.

One option is that we decide to move the entire codebase to maven standards 
before LTS (do it for once and for all), and bear the pain for next some months 
only. Though, lately at some point what if we decide to migrate to gradle or 
something else (just speculating future).

@jburwell @DaanHoogland @wido @swill what do you guys think?


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


[GitHub] cloudstack pull request: CLOUDSTACK-8562: Dynamic Role-Based API C...

2016-04-27 Thread jburwell
Github user jburwell commented on the pull request:

https://github.com/apache/cloudstack/pull/1489#issuecomment-215171740
  
@koushik-das I don't understand how adoption of this feature differs from 
any other feature.  A user deploys the release into a test/pilot environment 
and determine whether or not it they wish to migrate to it.  To be clear, 
existing users are **not** automatically migrated.

Per the FS, this feature alows the definition of custom roles as you 
describe.  For backwards compatibility, all roles must be mapped to one of the 
four types.  

I don't understand your point about someone writing a plugin to allow 
custom roles.  This PR is exactly the plugin you describe.


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


[GitHub] cloudstack pull request: CLOUDSTACK-9142 Migrate VM changes xmlDes...

2016-04-27 Thread rhtyd
Github user rhtyd commented on the pull request:

https://github.com/apache/cloudstack/pull/1348#issuecomment-215170748
  
@swill yes that was a good to have suggestion; keep large string based test 
data separated from test, though since this request is cosmetic in nature I'm 
okay if we decide to merge 


---
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: Building Ubuntu 16.04 packages

2016-04-27 Thread Wido den Hollander

> Op 27 april 2016 om 14:19 schreef Rohit Yadav :
> 
> 
> Hi Wido,
> 
> Thanks for starting this discussion. I'm not sure exactly how to do it 
> either, but I suppose we can exploit post installation step to write custom 
> scripts that setup initd or systemd scripts at suitable locations. For this 
> we include both init/systemd scripts in the package (let say at some location 
> like /usr/share/... and let post install script pick up the template and 
> setup inid scripts). This way I think we can explore if there is a way to 
> solve for building universal deb package.
> 

No, a postinst file is not the way to go, that I am sure of.

I'm looking at the Ceph project and how they build their packages. They have 
the same issue. I haven't figured it out completely, but they are not doing 
this in the postinst or so.

You should never do that either since dpkg should always know which files it 
created when installing a package.

Wido

> Regards.
> 
> Regards,
> 
> Rohit Yadav
> 
> rohit.ya...@shapeblue.com 
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
> 
> -Original Message-
> From: Wido den Hollander [mailto:w...@widodh.nl] 
> Sent: Wednesday, April 27, 2016 1:40 PM
> To: dev@cloudstack.apache.org
> Subject: Building Ubuntu 16.04 packages
> 
> Hi,
> 
> Ubuntu 16.04 LTS was released about a week ago and I want to start on 
> packages.
> 
> The cool things about the LTS:
> - systemd
> - Java 8
> - libvirt 1.3.1
> - Qemu 2.5
> 
> I'm familiar with building DEB packages, but there is something which I don't 
> know how to fix yet.
> 
> We want to build packages for Ubuntu 14.04 and Ubuntu 16.04, but the first 
> still uses Upstart / sysvinit and the newest uses systemd.
> 
> We already have systemd service files in 'packaging/systemd', so that is no 
> the problem.
> 
> I however don't know how to build packages for 14.04 (Trusty) and 16.04 
> (Xenial) using dpkg-buildpackage.
> 
> I see other projects use tools like pbuilder [0], but I don't know how that 
> exactly works.
> 
> Before I put a lot of effort in this: Does anybody know how to build packages 
> for different Ubuntu versions?
> 
> Eventually we will end up with packages like:
> 
> - cloudstack-agent-XXX~trusty.deb
> - cloudstack-agent-XXX~xenial.deb
> 
> Thanks,
> 
> Wido
> 
> [0]: https://pbuilder.alioth.debian.org/


[GitHub] cloudstack pull request: CLOUDSTACK-8562: Dynamic Role-Based API C...

2016-04-27 Thread rhtyd
Github user rhtyd commented on the pull request:

https://github.com/apache/cloudstack/pull/1489#issuecomment-215165382
  
@mlsorensen 
- presently, setting bitmask to 0 in commands.properties does not disable 
the API but that no roles would have that API; though if an API through its 
`authroized` annotation enables itself for a roletype that will be considered
- this feature implements a DENY rule that is checked before annotations 
are checked to provide a mechanism to disable an API (or group of APIs if a 
wildcard rule is used) that could have been enabled by the annotation (for 
example)

@koushik-das 
- Existing users are not migrated automatically, they continue to use 
static-checker
- Commands.properties file is only removed from codebase, after an upgrade 
this file won't be removed by the deb/rpm packages
- New users and installations are no longer encouraged to use the old 
static-checker, therefore with the aim of deprecating the static-checker over 
time dynamic-checker is enabled by default
- Any change can introduce side-effects and bugs but that does not mean we 
should stop innovating or stop improving cloudstack; such an attitude would be 
harmful for any project
- I really appreciate your code review, improvement suggestions and testing 
feedback instead, on this PR. 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 pull request: Remove unused images

2016-04-27 Thread remibergsma
Github user remibergsma closed the pull request at:

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


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


[GitHub] cloudstack pull request: CLOUDSTACK-8562: Dynamic Role-Based API C...

2016-04-27 Thread mlsorensen
Github user mlsorensen commented on the pull request:

https://github.com/apache/cloudstack/pull/1489#issuecomment-215147096
  
@koushik-das -- I'd say yes, that testing is good enough. If a test can 
determine that the default roles allow the expected access to the APIs then 
we're good.

There was some discussion of commands.properties deprecation in 2013. In 
particular, plugin developers had issues with the way it works. People should 
really have been using the annotations by now, but I believe it was not well 
communicated and the fact that commands.properties is still around has confused 
new developers. From the original discussion, the only reason it was left in 
place was in case users wanted to disable APIs entirely by setting the bitmask 
of an API to 0. Do we have that functionality covered now?


http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201310.mbox/%3c2b439486-9c4b-41b7-a698-b7ade234b...@netapp.com%3E


https://github.com/apache/cloudstack/commit/9f7b4884a7a0bf0b15d94777cff449fde4664af2

Note also that existing installations are not being affected, they have to 
choose to use the new mechanism. In theory, I'm fine with some sort of staged 
transition where the dynamic checking is opt-in for a release, but I worry that 
it will perpetuate the issue we've seen since 2013, and puts a burden on the 
community to go back and clean up at some later date. For these reasons, I 
think if it's functionally identical on new installs and doesn't affect 
existing installs use of commands.properties, we should just cut over.



---
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: CPU socket count reporting correction

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1520#issuecomment-215143364
  
Great, thanks @remibergsma.  :)


---
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: CPU socket count reporting correction

2016-04-27 Thread remibergsma
Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1520#issuecomment-215143007
  
@swill more details here: 
https://github.com/MissionCriticalCloud/cosmic-plugin-hypervisor-kvm/pull/16


---
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: kvm: Aqcuire lock when running security g...

2016-04-27 Thread wido
Github user wido commented on the pull request:

https://github.com/apache/cloudstack/pull/1408#issuecomment-215138161
  
@rhtyd The lock does not have to be released. It is done when the script 
exists. This is usually within 100ms or so.


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


Up to date hypervisor support matrix

2016-04-27 Thread Erik Weber
There has been quite some differences between what features that
are supported on different hypervisors.

Does anyone know If the feature support matrix is up to date? In particular
I am interested in what features we do (and don't) support with KVM

Erik


[GitHub] cloudstack pull request: Kvm plugin restructure

2016-04-27 Thread DaanHoogland
Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1521#issuecomment-215131396
  
@swil @rhtyd this is the follow up of #1348. The initial rat failure was 
genuine but next files where found that are .gitignored. not sure what happened


---
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: CPU socket count reporting correction

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1520#issuecomment-215124694
  
@NuxRo can you do a force push to kick off jenkins and travis again.  Also, 
can you show this change fixes the behavior with a screenshot or something.  I 
don't think the code change warrants a full CI run since nothing new was 
introduced, only the value of a variable has changed and it uses proper 
defensive programming...  It would be nice to see the problem it solves 
though...


---
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: Kvm plugin restructure

2016-04-27 Thread DaanHoogland
GitHub user DaanHoogland opened a pull request:

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

Kvm plugin restructure

test and project restructure without functional implications

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

$ git pull https://github.com/DaanHoogland/cloudstack kvm-plugin-restructure

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

https://github.com/apache/cloudstack/pull/1521.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 #1521


commit 8a6afa6d9ff6b69e45209c4a871d0624d016af74
Author: Daan Hoogland 
Date:   2016-01-18T16:43:43Z

CLOUDSTACK-9142 Migrate VM changes xmlDesc in a safe way

commit 385d1980a090e6a53c204ed3ec77302efd48d5b7
Author: Daan Hoogland 
Date:   2016-04-27T13:45:27Z

plugin src restructure to adhere to maven standards

commit 1d8749b770cf92c391555722b69d73fb2c2e3fb4
Author: Daan Hoogland 
Date:   2016-04-27T15:27:16Z

externalize xml input and -result for test




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


[GitHub] cloudstack pull request: CLOUDSTACK-8302: Removing snapshots on RB...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1230#issuecomment-215122706
  
@kiwiflyer Thank you sir.  :)


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


[GitHub] cloudstack pull request: CLOUDSTACK-8800 : Improved the listVirtua...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1444#issuecomment-215122425
  
I would like to get at least one LGTM in this PR.  The code is basically 
the same as the previous one other than the fixes to the potential NPE issues.  
I think we should get some reviews here regardless.


---
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: Another question about Marvin

2016-04-27 Thread Will Stevens
Perfect.  That is what I was looking for.  Thanks...  :)

*Will STEVENS*
Lead Developer

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

On Wed, Apr 27, 2016 at 11:07 AM, Prashanth Manthena <
prashanth.manth...@nuagenetworks.net> wrote:

> Hi Will,
>
> 1) will run a, b, c
> 2) will run only b
> 3) will run only c
>
> Nosetests will run all the testcases that match attribute (tags)
> combination you specify in the command.
>
> Default (no tag(s) specified): It will run all the testcases.
>
> With regards,
> Prashanth
>
>
>
> On Wed, Apr 27, 2016 at 4:30 PM, Will Stevens 
> wrote:
>
> > So I see a few different ways in which tests are defined.
> >
> > For example, here are a few different attribute configurations:
> >
> > a) @attr(tags=["advanced", "intervlan"])
> > b) @attr(tags=["advanced", "intervlan"], required_hardware="true")
> > c) @attr(tags=["advanced", "intervlan"], required_hardware="false")
> >
> > Then there are different ways to run tests.  Some examples are:
> >
> > 1) nosetests --with-marvin --marvin-config=${marvinCfg} -s -a
> tags=advanced
> > 2) nosetests --with-marvin --marvin-config=${marvinCfg} -s -a
> > tags=advanced,required_hardware=true
> > 3) nosetests --with-marvin --marvin-config=${marvinCfg} -s -a
> > tags=advanced,required_hardware=false
> >
> > I am trying to figure out which tests are run in each case.
> >
> > I think 2) is the easiest case because it should only run b).
> >
> > 3) is a little less clear to me because I know it will run c), but will
> it
> > run a)?
> >
> > 1) is the least clear to me because I don't know if it will run any of
> the
> > 'required_hardware' tests.
> >
> > Can someone drop a little knowledge on me?
> >
> > Thanks,
> >
> > Will
> >
>


[GitHub] cloudstack pull request: CLOUDSTACK-9349: Enable root disk detach ...

2016-04-27 Thread dmabry
Github user dmabry commented on the pull request:

https://github.com/apache/cloudstack/pull/1500#issuecomment-215120369
  
OK, all checks have passed!  ;)  Looking for another 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.
---


[GitHub] cloudstack pull request: CLOUDSTACK-8302: Removing snapshots on RB...

2016-04-27 Thread kiwiflyer
Github user kiwiflyer commented on the pull request:

https://github.com/apache/cloudstack/pull/1230#issuecomment-215118770
  
I'm building this now and I'll give it a final manual test. Then we'll do a 
CI run against a hardware lab.


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


[GitHub] cloudstack pull request: CLOUDSTACK-9368: Fix for Support configur...

2016-04-27 Thread rafaelweingartner
Github user rafaelweingartner commented on the pull request:

https://github.com/apache/cloudstack/pull/1518#issuecomment-215116783
  
@nvazquez I believe so.
This way we can reduce a little bit of code.


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


[GitHub] cloudstack pull request: CLOUDSTACK-9368: Fix for Support configur...

2016-04-27 Thread nvazquez
Github user nvazquez commented on the pull request:

https://github.com/apache/cloudstack/pull/1518#issuecomment-215116050
  
Thanks @rafaelweingartner, I like the idea, I think the best way would be 
leave hierarchy like this:


- Command
-- NEW CLASS
--- StorageCommand
--- SsCommand
--- CopyVolumeCommand
--- SecStorageSetupCommand
--- GetStorageStatsCommand

- TemplateOrVolumePostUploadCommand


This way it can be avoided `nfsVersion` parameter in every class in Command 
hierarchy, because they won't need it, and just leave 
`TemplateOrVolumePostUploadCommand` separate in this hierarchy. Would this be 
ok?


---
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: [ANNOUNCE] Open source distributed virtual machine scheduling platform

2016-04-27 Thread Gabriel Beims Bräscher
Hi all,
Thanks for your cheers, it means a lot for us.

Anshul, thanks for asking. We are very excited about the project, our plan
is to add new algorithms. Also, We foresee the need to use/add other types
of agents. All of that is going to be done as our research goes forward.

That is great that you have already worked on this. You probably understand
how hard it is to work alone in a project like this. Gladly, we are not
alone on this boat. Today our whole system is based on symbolic artificial
intelligence, our heuristics are based on specialist knowledge. But, as you
pointed out the use of machine learning (connectionist artificial
intelligence) is pretty interesting for some problems. And yes, we intend
to use some neural/Bayesian Network techniques to help us improve our
heuristics. Again, that is something that will be done as our research and
project go forward.

Cheers, Gabriel.

2016-04-27 3:27 GMT-03:00 Anshul Gangwar :

> Hi Gabriel,
>
> Project looks promising.
>
> I was curious to know whether you guys are planning to add new algorithms
> or use the existing algorithms.
>
> P.S. I was working on same problem for my master’s thesis some 5 years
> back. My main intention was to utilise the machine learning based
> approaches to solve the problem.
>
>
>
>
> On 27/04/16, 2:29 AM, "Gabriel Beims Bräscher" 
> wrote:
>
> >Hello CloudStack community members (@dev and @users),
> >
> >This email is meant to announce the publication of a project on Github
> that
> >provides a distributed virtual machine scheduling platform that can be
> >easily integrated with Apache CloudStack (ACS). The project is available
> at
> >[1], you can find a detailed explanation of the idea of the project, its
> >aspirations, basic concepts, installation and uninstallation processes and
> >other information at [2]. Also, if you want to know more about the
> >Autonomiccs and its creators, you can access the link [3].
> >
> >The code that was opened at Github is part of a bigger system that has the
> >goal of managing a cloud computing environment autonomously. All of that
> is
> >being developed and used in my Ph. D. thesis and the masters’ thesis of
> >some colleagues. The formalization of that component will be published at
> >the 12th IEEE World Congress on Services (SERVICES 2016) at San Francisco
> >USA.
> >
> >You can see the stats of our code at [4] and [5]. Right now we only have
> >~40% of code test coverage. However, we intend to increase that value to
> >~60% until next week and ~90% until the end of June.
> >
> >To give you a picture of what we are preparing for the future, we can
> >highlight the following goals for this year (You can find others short
> term
> >goals at [6]):
> >
> >   -
> >
> >   Integrate our platform [1] with a multi-agent system (MAS) platform, in
> >   order to facilitate the development of agents. Currently, we are using
> >   Spring-integration to “emulate” and an agent life cycle; that can
> become a
> >   problem when needing to add more agents and they start to communicate
> with
> >   each other. Therefore, we will integrate the platform in [1] with JADE
> [7];
> >   -
> >
> >   Today the metrics about the use of resource are not properly gathered
> by
> >   ACS; in order to develop more accurate predictions we need to store
> >   resource usage metrics. Also, those metrics have to be gathered in a
> >   distributed way without causing service degradation. For that and a few
> >   other reasons (you can send us an email so we can provide you more
> >   details), we are developing an autonomic monitoring platform that will
> >   integrate with the system available in [1];
> >   -
> >
> >   We also foresee the need to develop a better way to visualize the cloud
> >   environment, a way to detect hot spots (pods and hosts) with higher
> >   resource usage trends (VMs trends). We see the need to change the
> rustic
> >   view of the environment with tables for a better suitable one for
> humans
> >   (this is a surprise that we intend to present at the CCCBR).
> >
> >We hope you like the software and that it meets your expectations. If it
> >does not suffice all of your needs, let’s work together to improve it. If
> >you have any doubts or suggestions please send us an email; we will reply
> >it as fast as we can. Also, critics that can help us improve that platform
> >are very welcome.
> >
> >[1] https://github.com/Autonomiccs/autonomiccs-platform
> >
> >[2] https://github.com/Autonomiccs/autonomiccs-platform/wiki
> >
> >[3] http://autonomiccs.com.br/
> >
> >[4] http://jenkins.autonomiccs.com.br/
> >
> >[5] http://sonar.autonomiccs.com.br/
> >
> >[6] https://github.com/Autonomiccs/autonomiccs-platform#project-evolution
> >
> >[7] http://jade.tilab.com/
> >
> >
> >Cheers, Gabriel.
>
>
>
> DISCLAIMER
> ==
> This e-mail may contain privileged and confidential information which is
> the property of Accelerite, a Persistent 

Re: Another question about Marvin

2016-04-27 Thread Prashanth Manthena
Hi Will,

1) will run a, b, c
2) will run only b
3) will run only c

Nosetests will run all the testcases that match attribute (tags)
combination you specify in the command.

Default (no tag(s) specified): It will run all the testcases.

With regards,
Prashanth



On Wed, Apr 27, 2016 at 4:30 PM, Will Stevens 
wrote:

> So I see a few different ways in which tests are defined.
>
> For example, here are a few different attribute configurations:
>
> a) @attr(tags=["advanced", "intervlan"])
> b) @attr(tags=["advanced", "intervlan"], required_hardware="true")
> c) @attr(tags=["advanced", "intervlan"], required_hardware="false")
>
> Then there are different ways to run tests.  Some examples are:
>
> 1) nosetests --with-marvin --marvin-config=${marvinCfg} -s -a tags=advanced
> 2) nosetests --with-marvin --marvin-config=${marvinCfg} -s -a
> tags=advanced,required_hardware=true
> 3) nosetests --with-marvin --marvin-config=${marvinCfg} -s -a
> tags=advanced,required_hardware=false
>
> I am trying to figure out which tests are run in each case.
>
> I think 2) is the easiest case because it should only run b).
>
> 3) is a little less clear to me because I know it will run c), but will it
> run a)?
>
> 1) is the least clear to me because I don't know if it will run any of the
> 'required_hardware' tests.
>
> Can someone drop a little knowledge on me?
>
> Thanks,
>
> Will
>


[GitHub] cloudstack pull request: CLOUDSTACK-8800 : Improved the listVirtua...

2016-04-27 Thread rafaelweingartner
Github user rafaelweingartner commented on the pull request:

https://github.com/apache/cloudstack/pull/1444#issuecomment-215111745
  
@swill, I am so sorry, I had forgotten this PR. I opened the email to help 
in a review thinking that this was from someone else.

Are you sure we can count the LGTMs from other PR here?
We have not received any LGTMs. I do not know if the code was reviewed 
though.



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


[GitHub] cloudstack pull request: CLOUDSTACK-8800 : Improved the listVirtua...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1444#issuecomment-215109078
  
Ran the usage tests to make sure everything is passing.  Don't worry about 
the snapshot issue, it is not related to this PR.

I think this PR is ready if I count the LGTM votes from the previous PR.  
Any final thoughts???


---
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: L10n update 4.8 20160422

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1515#issuecomment-215109976
  
@milamberspace and again.  :P sorry...


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


[GitHub] cloudstack pull request: CLOUDSTACK-8800 : Improved the listVirtua...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1444#issuecomment-215108116
  


### CI RESULTS

```
Tests Run: 18
  Skipped: 0
   Failed: 0
   Errors: 2
```

**Summary of the problem(s):**
```
ERROR: Test Create/Delete a manual snap shot and verify
--
Traceback (most recent call last):
  File 
"/data/git/cs1/cloudstack/test/integration/component/test_project_usage.py", 
line 1376, in test_01_snapshot_usage
snapshot = Snapshot.create(self.apiclient, volumes[0].id)
  File "/usr/lib/python2.7/site-packages/marvin/lib/base.py", line 1014, in 
create
return Snapshot(apiclient.createSnapshot(cmd).__dict__)
  File 
"/usr/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py", 
line 797, in createSnapshot
response = self.connection.marvinRequest(command, 
response_type=response, method=method)
  File "/usr/lib/python2.7/site-packages/marvin/cloudstackConnection.py", 
line 379, in marvinRequest
raise e
CloudstackAPIException: Execute cmd: createsnapshot failed, due to: 
errorCode: 530, errorText:KVM Snapshot is not supported: 1
--
Additional details in: /tmp/MarvinLogs/test_usage_0CACSG/results.txt
```

```
ERROR: Test Create/Delete a manual snap shot and verify
--
Traceback (most recent call last):
  File "/data/git/cs1/cloudstack/test/integration/component/test_usage.py", 
line 1300, in test_01_snapshot_usage
snapshot = Snapshot.create(self.apiclient, volumes[0].id)
  File "/usr/lib/python2.7/site-packages/marvin/lib/base.py", line 1014, in 
create
return Snapshot(apiclient.createSnapshot(cmd).__dict__)
  File 
"/usr/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py", 
line 797, in createSnapshot
response = self.connection.marvinRequest(command, 
response_type=response, method=method)
  File "/usr/lib/python2.7/site-packages/marvin/cloudstackConnection.py", 
line 379, in marvinRequest
raise e
CloudstackAPIException: Execute cmd: createsnapshot failed, due to: 
errorCode: 530, errorText:KVM Snapshot is not supported: 1
--
Additional details in: /tmp/MarvinLogs/test_usage_0CACSG/results.txt
```



**Associated Uploads**

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

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


Uploads will be available until `2016-06-27 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 pull request: CLOUDSTACK-9349: Enable root disk detach ...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1500#issuecomment-215103065
  
@koushik-das can I get your code review on this?  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 pull request: CLOUDSTACK-9349: Enable root disk detach ...

2016-04-27 Thread dmabry
Github user dmabry commented on the pull request:

https://github.com/apache/cloudstack/pull/1500#issuecomment-215103808
  
Yea, I saw that jenkins failed pulling 4.7 branch, so I kicked it off 
again.  I'm going to keep an eye on travis and jenkins.  There is no reason 
those tests should fail.  Hopefully, I'll get a green this time around.  ;)


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


[GitHub] cloudstack pull request: CLOUDSTACK-9349: Enable root disk detach ...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1500#issuecomment-215102785
  
Thanks @kiwiflyer.  :)  I was about to ask you to re-push to kick off the 
runs again and you did it as I was typing.  👍 


---
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: Failed to create VPC: Unable to start VPC VR (VM DomainRouter) due to error in finalizeStart, not retrying

2016-04-27 Thread Remi Bergsma
If this is about KVM and ovs vifdriver (we use NSX which uses ovs) then an 
issue we recently fixed may be the same issue as you have here. 
https://github.com/MissionCriticalCloud/cosmic-plugin-hypervisor-kvm/pull/14

When I find some spare time I can look into backporting it. 

Regards, Remi 


> On 27 Apr 2016, at 15:59, Nick LIVENS  wrote:
> 
> Simon Weller (who added a comment on the ticket itself) said the following
> : "According to the 4.8 docs, OVS and KVM VPC doesn't currently work. I'm
> not aware of any work that has changed this in master.
> 
> http://docs.cloudstack.apache.org/en/latest/networking/ovs-plugin.html#using-the-ovs-plugin-with-vpc
> "
> 
> Looking at the logs in the ticket, the request reaches the cloudstack-agent
> (so connectivity is fine), but it fails do to an error in 'cs_ip.py' :
> 
> File "/opt/cloud/bin/cs_ip.py", line 32, in mergeip['device'] =
> 'eth' + str(ip['nic_dev_id'])KeyError: 'nic_dev_id'
> 
> 
> Kind regards,
> Nick Livens
> 
>> On Wed, Apr 27, 2016 at 3:09 PM, Will Stevens  wrote:
>> 
>> It looks like your host(9) is unreachable.  Can you verify that the
>> connectivity is all setup correctly?
>> 
>> *Will STEVENS*
>> Lead Developer
>> 
>> *CloudOps* *| *Cloud Solutions Experts
>> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>> w cloudops.com *|* tw @CloudOps_
>> 
>> On Wed, Apr 27, 2016 at 8:31 AM, Prashanth Manthena <
>> prashanth.manth...@nuagenetworks.net> wrote:
>> 
>>> Hi All,
>>> 
>>> I am seeing the following issue on master:
>>> https://issues.apache.org/jira/browse/CLOUDSTACK-9370.
>>> 
>>> Is anyone else seeing this issue on master ?
>>> 
>>> Let me know, if you need more information from my side.
>>> 
>>> With regards,
>>> Prashanth
>> 


Another question about Marvin

2016-04-27 Thread Will Stevens
So I see a few different ways in which tests are defined.

For example, here are a few different attribute configurations:

a) @attr(tags=["advanced", "intervlan"])
b) @attr(tags=["advanced", "intervlan"], required_hardware="true")
c) @attr(tags=["advanced", "intervlan"], required_hardware="false")

Then there are different ways to run tests.  Some examples are:

1) nosetests --with-marvin --marvin-config=${marvinCfg} -s -a tags=advanced
2) nosetests --with-marvin --marvin-config=${marvinCfg} -s -a
tags=advanced,required_hardware=true
3) nosetests --with-marvin --marvin-config=${marvinCfg} -s -a
tags=advanced,required_hardware=false

I am trying to figure out which tests are run in each case.

I think 2) is the easiest case because it should only run b).

3) is a little less clear to me because I know it will run c), but will it
run a)?

1) is the least clear to me because I don't know if it will run any of the
'required_hardware' tests.

Can someone drop a little knowledge on me?

Thanks,

Will


[GitHub] cloudstack pull request: CLOUDSTACK-9349: Enable root disk detach ...

2016-04-27 Thread kiwiflyer
Github user kiwiflyer commented on the pull request:

https://github.com/apache/cloudstack/pull/1500#issuecomment-215099770
  
Tested this patch manually on a KVM 4.8 lab. We also ran the new Marvin 
unit tests successfully against the simulator, bubble instance and a hardware 
lab. Works as designed. 

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


[GitHub] cloudstack pull request: SystemVM cleanups

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1414#issuecomment-215097877
  
@bvbharatk I am guessing you are still having some environment issues in 
your CI or are these results correct?  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 pull request: CLOUDSTACK-6975: Prevent dnsmasq from sta...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1514#issuecomment-215095216
  
The test that failed is one that periodically fails in my env, so I don't 
think we can assume it is related to this PR.


---
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: CaaS in CloudStack with Kubernetes

2016-04-27 Thread Nux!
Hello,

Very nice, but I am somewhat surprised! I thought we were not going after 
docker/containers/etc and let others (CoreOS etc) do it?
What has changed?

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Sebastien Goasguen" 
> To: market...@cloudstack.apache.org
> Cc: dev@cloudstack.apache.org
> Sent: Friday, 22 April, 2016 17:02:22
> Subject: CaaS in CloudStack with Kubernetes

> Hi folks,
> 
> I have been quite silent this past few weeks because aside from voting in a 
> new
> VP (soon to be announced), I  have been hard at work for my new endeavors with
> Skippbox.
> 
> I am quite excited that today we could not wait and Skippbox together with
> Shapeblue announced a preview of a Kubernetes/CloudStack integration:
> http://www.benzinga.com/pressreleases/16/04/g7872516/shapeblue-harness-the-power-of-kubernetes-and-apache-cloudstack-to-give
> 
> This is currently still a by request preview, but once we are done with much
> better testing and even tighter integration, the code will be open sourced as 
> a
> CloudStack plugin.
> 
> I wouldn’t mind couple supportive tweets and if you want a demo before you can
> run it yourself, ping me.
> 
> Cheers,
> 
> -Sebastien


RE: [ANNOUNCE] Open source distributed virtual machine scheduling platform

2016-04-27 Thread Giles Sirett
Rafael
This is very exciting to see, congrats in getting your project out of the gate



Kind Regards
Giles


Regards,

Giles Sirett

giles.sir...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue

-Original Message-
From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com] 
Sent: 27 April 2016 02:59
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: Re: [ANNOUNCE] Open source distributed virtual machine scheduling 
platform

Thank you guys for the cheers. That is a very warm welcome for our little 
project ;) You bet we will keep the hard work. There is much (really much) more 
to work on, with this project we will have at least 2 masters’ thesis and 3 
Ph.D. thesis; that is something to keep us busy for the next 5+ years only in 
research and development (RD).

We hope you guys test the Autonomiccs platform and may even use it in your 
production environments.
If any of you want to chat in person, I will be at the ApacheCon NA (Thanks for 
the ASF funding) that will be happening between May 09-11 in Vancouver and at 
the SERVICES conference that will be happening between June 27 and July 02 in 
San Francisco.


On Tue, Apr 26, 2016 at 10:28 PM, Ahmad Emneina  wrote:

> This looks really cool and promising! Keep up the great work.
>
> On Tue, Apr 26, 2016 at 1:59 PM, Gabriel Beims Bräscher < 
> gabrasc...@gmail.com> wrote:
>
> > Hello CloudStack community members (@dev and @users),
> >
> > This email is meant to announce the publication of a project on 
> > Github
> that
> > provides a distributed virtual machine scheduling platform that can 
> > be easily integrated with Apache CloudStack (ACS). The project is 
> > available
> at
> > [1], you can find a detailed explanation of the idea of the project, 
> > its aspirations, basic concepts, installation and uninstallation 
> > processes
> and
> > other information at [2]. Also, if you want to know more about the 
> > Autonomiccs and its creators, you can access the link [3].
> >
> > The code that was opened at Github is part of a bigger system that 
> > has
> the
> > goal of managing a cloud computing environment autonomously. All of 
> > that
> is
> > being developed and used in my Ph. D. thesis and the masters’ thesis 
> > of some colleagues. The formalization of that component will be 
> > published at the 12th IEEE World Congress on Services (SERVICES 
> > 2016) at San Francisco USA.
> >
> > You can see the stats of our code at [4] and [5]. Right now we only 
> > have ~40% of code test coverage. However, we intend to increase that 
> > value to ~60% until next week and ~90% until the end of June.
> >
> > To give you a picture of what we are preparing for the future, we 
> > can highlight the following goals for this year (You can find others 
> > short
> term
> > goals at [6]):
> >
> >-
> >
> >Integrate our platform [1] with a multi-agent system (MAS) 
> > platform,
> in
> >order to facilitate the development of agents. Currently, we are using
> >Spring-integration to “emulate” and an agent life cycle; that can 
> > become a
> >problem when needing to add more agents and they start to 
> > communicate with
> >each other. Therefore, we will integrate the platform in [1] with 
> > JADE [7];
> >-
> >
> >Today the metrics about the use of resource are not properly 
> > gathered
> by
> >ACS; in order to develop more accurate predictions we need to store
> >resource usage metrics. Also, those metrics have to be gathered in a
> >distributed way without causing service degradation. For that and 
> > a
> few
> >other reasons (you can send us an email so we can provide you more
> >details), we are developing an autonomic monitoring platform that will
> >integrate with the system available in [1];
> >-
> >
> >We also foresee the need to develop a better way to visualize the
> cloud
> >environment, a way to detect hot spots (pods and hosts) with higher
> >resource usage trends (VMs trends). We see the need to change the
> rustic
> >view of the environment with tables for a better suitable one for
> humans
> >(this is a surprise that we intend to present at the CCCBR).
> >
> > We hope you like the software and that it meets your expectations. 
> > If it does not suffice all of your needs, let’s work together to 
> > improve it. If you have any doubts or suggestions please send us an 
> > email; we will reply it as fast as we can. Also, critics that can 
> > help us improve that
> platform
> > are very welcome.
> >
> > [1] https://github.com/Autonomiccs/autonomiccs-platform
> >
> > [2] https://github.com/Autonomiccs/autonomiccs-platform/wiki
> >
> > [3] http://autonomiccs.com.br/
> >
> > [4] http://jenkins.autonomiccs.com.br/
> >
> > [5] http://sonar.autonomiccs.com.br/
> >
> > [6]
> https://github.com/Autonomiccs/autonomiccs-platform#project-evolution
> >
> > [7] http://jade.tilab.com/
> >
> 

[GitHub] cloudstack pull request: CLOUDSTACK-8800 : Improved the listVirtua...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1444#issuecomment-215094461
  
The issues that we see here are environment issues that sometimes show up.  
They are not related to this PR.  

I am running another set of usage specific integration tests.  I am not 
sure of the state of these tests, so I will post the results when they are done 
and we can go from there.


---
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: Failed to create VPC: Unable to start VPC VR (VM DomainRouter) due to error in finalizeStart, not retrying

2016-04-27 Thread Nick LIVENS
Simon Weller (who added a comment on the ticket itself) said the following
: "According to the 4.8 docs, OVS and KVM VPC doesn't currently work. I'm
not aware of any work that has changed this in master.

http://docs.cloudstack.apache.org/en/latest/networking/ovs-plugin.html#using-the-ovs-plugin-with-vpc
"

Looking at the logs in the ticket, the request reaches the cloudstack-agent
(so connectivity is fine), but it fails do to an error in 'cs_ip.py' :

File "/opt/cloud/bin/cs_ip.py", line 32, in mergeip['device'] =
'eth' + str(ip['nic_dev_id'])KeyError: 'nic_dev_id'


Kind regards,
Nick Livens

On Wed, Apr 27, 2016 at 3:09 PM, Will Stevens  wrote:

> It looks like your host(9) is unreachable.  Can you verify that the
> connectivity is all setup correctly?
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Wed, Apr 27, 2016 at 8:31 AM, Prashanth Manthena <
> prashanth.manth...@nuagenetworks.net> wrote:
>
> > Hi All,
> >
> > I am seeing the following issue on master:
> > https://issues.apache.org/jira/browse/CLOUDSTACK-9370.
> >
> > Is anyone else seeing this issue on master ?
> >
> > Let me know, if you need more information from my side.
> >
> > With regards,
> > Prashanth
> >
>


[GitHub] cloudstack pull request: CLOUDSTACK-8800 : Improved the listVirtua...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1444#issuecomment-215090037
  


### CI RESULTS

```
Tests Run: 85
  Skipped: 0
   Failed: 3
   Errors: 0
```

**Summary of the problem(s):**
```
FAIL: Test redundant router internals
--
Traceback (most recent call last):
  File 
"/data/git/cs1/cloudstack/test/integration/smoke/test_routers_network_ops.py", 
line 290, in test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true
"Attempt to retrieve google.com index page should be successful!"
AssertionError: Attempt to retrieve google.com index page should be 
successful!
--
Additional details in: /tmp/MarvinLogs/test_network_NAELYA/results.txt
```

```
FAIL: test_03_vpc_privategw_restart_vpc_cleanup 
(integration.smoke.test_privategw_acl.TestPrivateGwACL)
--
Traceback (most recent call last):
  File 
"/data/git/cs1/cloudstack/test/integration/smoke/test_privategw_acl.py", line 
265, in test_03_vpc_privategw_restart_vpc_cleanup
self.performVPCTests(vpc_off, True)
  File 
"/data/git/cs1/cloudstack/test/integration/smoke/test_privategw_acl.py", line 
324, in performVPCTests
self.check_pvt_gw_connectivity(vm1, public_ip_1, vm2.nic[0].ipaddress)
  File 
"/data/git/cs1/cloudstack/test/integration/smoke/test_privategw_acl.py", line 
559, in check_pvt_gw_connectivity
"Ping to outside world from VM should be successful"
AssertionError: Ping to outside world from VM should be successful
--
Additional details in: /tmp/MarvinLogs/test_network_NAELYA/results.txt
```

```
FAIL: test_04_rvpc_privategw_static_routes 
(integration.smoke.test_privategw_acl.TestPrivateGwACL)
--
Traceback (most recent call last):
  File 
"/data/git/cs1/cloudstack/test/integration/smoke/test_privategw_acl.py", line 
277, in test_04_rvpc_privategw_static_routes
self.performVPCTests(vpc_off)
  File 
"/data/git/cs1/cloudstack/test/integration/smoke/test_privategw_acl.py", line 
324, in performVPCTests
self.check_pvt_gw_connectivity(vm1, public_ip_1, vm2.nic[0].ipaddress)
  File 
"/data/git/cs1/cloudstack/test/integration/smoke/test_privategw_acl.py", line 
559, in check_pvt_gw_connectivity
"Ping to outside world from VM should be successful"
AssertionError: Ping to outside world from VM should be successful
--
Additional details in: /tmp/MarvinLogs/test_network_NAELYA/results.txt
```



**Associated Uploads**

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

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

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


Uploads will be available until `2016-06-27 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 

[GitHub] cloudstack pull request: CLOUDSTACK-6975: Prevent dnsmasq from sta...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1514#issuecomment-215089828
  


### CI RESULTS

```
Tests Run: 85
  Skipped: 0
   Failed: 1
   Errors: 0
```

**Summary of the problem(s):**
```
FAIL: test_03_vpc_privategw_restart_vpc_cleanup 
(integration.smoke.test_privategw_acl.TestPrivateGwACL)
--
Traceback (most recent call last):
  File 
"/data/git/cs2/cloudstack/test/integration/smoke/test_privategw_acl.py", line 
265, in test_03_vpc_privategw_restart_vpc_cleanup
self.performVPCTests(vpc_off, True)
  File 
"/data/git/cs2/cloudstack/test/integration/smoke/test_privategw_acl.py", line 
331, in performVPCTests
self.check_pvt_gw_connectivity(vm1, public_ip_1, vm2.nic[0].ipaddress)
  File 
"/data/git/cs2/cloudstack/test/integration/smoke/test_privategw_acl.py", line 
559, in check_pvt_gw_connectivity
"Ping to outside world from VM should be successful"
AssertionError: Ping to outside world from VM should be successful
--
Additional details in: /tmp/MarvinLogs/test_network_FCU6EL/results.txt
```



**Associated Uploads**

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

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

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


Uploads will be available until `2016-06-27 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 pull request: CLOUDSTACK-9142 Migrate VM changes xmlDes...

2016-04-27 Thread DaanHoogland
Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1348#issuecomment-215087562
  
That's correct. I am doing the restructure now based on this PR's source 
branch and will make a new PR shortly. If it gets tested before this one I will 
close this one but it is really a pedantic play-with-myself kind of thing and 
the wether outside is fine.


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


[GitHub] cloudstack pull request: CLOUDSTACK-9349: Enable root disk detach ...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1500#issuecomment-215087358
  
Thank you for the results.  I think that is all we need from a CI 
perspective.  Jenkins and Travis have been kicked off again as well, so that is 
good.  Hopefully we will be all green on that front too.

We need some LGTM code reviews on this one.  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 pull request: CLOUDSTACK-9349: Enable root disk detach ...

2016-04-27 Thread dmabry
Github user dmabry commented on the pull request:

https://github.com/apache/cloudstack/pull/1500#issuecomment-215084188
  

[test_volumes_NV6XFO.zip](https://github.com/apache/cloudstack/files/238694/test_volumes_NV6XFO.zip)

Here is the zip file containing the test results.

Thanks in advance for the reviews!


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


[GitHub] cloudstack pull request: CLOUDSTACK-9142 Migrate VM changes xmlDes...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1348#issuecomment-215084100
  
So if I am following this correctly, we are all set.  @rhtyd requested a 
change to move the test data to an overridable location, but did not require 
this change for his LGTM.  @DaanHoogland would have to restructure the plugin 
in order to make that happen and feels it is outside the scope of this fix and 
would prefer to address that to a future improvement.  Does that all make sense?

I will put this in my merge queue, but will wait for confirmation that we 
are good to go before merging.  Thanks guys...


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


[GitHub] cloudstack pull request: CLOUDSTACK-9349: Enable root disk detach ...

2016-04-27 Thread dmabry
Github user dmabry commented on the pull request:

https://github.com/apache/cloudstack/pull/1500#issuecomment-215083560
  
Ok, I have run this through my lab again and specifically ran the 
test_volumes.py file.  All tests passed.  See below.  I have also attached the 
results dir as a zip file for review.

Test Volume attach/detach to VM (5 data volumes) ... === TestName: 
test_01_volume_attach_detach | Status : SUCCESS ===
ok
Test Root Volume attach/detach to VM ... === TestName: 
test_02_root_volume_attach_detach | Status : SUCCESS ===
ok
Test Attach volumes (max capacity) ... === TestName: test_01_volume_attach 
| Status : SUCCESS ===
ok
Test attach volumes (more than max) to an instance ... === TestName: 
test_02_volume_attach_max | Status : SUCCESS ===
ok
Test custom disk sizes beyond range ... === TestName: 
test_deployVmWithCustomDisk | Status : SUCCESS ===
ok
Attach a created Volume to a Running VM ... === TestName: 
test_01_attach_volume | Status : SUCCESS ===
ok
Detach a Volume attached to a VM ... === TestName: test_02_detach_volume | 
Status : SUCCESS ===
ok
Delete a Volume unattached to an VM ... === TestName: 
test_03_delete_detached_volume | Status : SUCCESS ===
ok
Create a volume under a non-root domain as non-root-domain user ... === 
TestName: test_create_volume_under_domain | Status : SUCCESS ===
ok

--
Ran 9 tests in 539.126s

OK

@swill - Looking at the standard bubble test suite that is run, it doesn't 
even run this test, so I thought it prudent in this case to run it specifically 
and post the results.  Once we get the bubble stuff standardized, I'm happy to 
run the full test and post those results.  Until then, I would like to submit 
this PR for code review again.


---
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: 4.9 mvn version safeupgradeonly

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1510#issuecomment-215081538
  
Thank you gentlemen.  I think this one is ready now.  👍 


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


[GitHub] cloudstack pull request: CLOUDSTACK-9199: Fixed deployVirtualMachi...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1280#issuecomment-215080256
  
Looking for one more LGTM for this one...  Thx...


---
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: More VR performance!

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1356#issuecomment-215079521
  
I am not seeing the issue on master.  It appears that your issue may be 
related to the Host(9) being unreachable.  I would validate the connectivity is 
all working as expected in your environment.


---
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: engine/schema: fix upgrade path to work w...

2016-04-27 Thread swill
Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1517#issuecomment-215077801
  
Thanks for the validation discussion.  I think this is ready...


---
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: Failed to create VPC: Unable to start VPC VR (VM DomainRouter) due to error in finalizeStart, not retrying

2016-04-27 Thread Will Stevens
It looks like your host(9) is unreachable.  Can you verify that the
connectivity is all setup correctly?

*Will STEVENS*
Lead Developer

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

On Wed, Apr 27, 2016 at 8:31 AM, Prashanth Manthena <
prashanth.manth...@nuagenetworks.net> wrote:

> Hi All,
>
> I am seeing the following issue on master:
> https://issues.apache.org/jira/browse/CLOUDSTACK-9370.
>
> Is anyone else seeing this issue on master ?
>
> Let me know, if you need more information from my side.
>
> With regards,
> Prashanth
>


[GitHub] cloudstack pull request: CLOUDSTACK-9142 Migrate VM changes xmlDes...

2016-04-27 Thread DaanHoogland
Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1348#issuecomment-215075290
  
@rhtyd as a part of loading from resource I am restructuring the project 
layout to adhere to maven standards. Doing so it seems not appropriate to 
include such a change in this bug fix.@swill I think this can be merged.


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


[GitHub] cloudstack pull request: CLOUDSTACK-9199: Fixed deployVirtualMachi...

2016-04-27 Thread koushik-das
Github user koushik-das commented on the pull request:

https://github.com/apache/cloudstack/pull/1280#issuecomment-215070344
  
LGTM. Verified on a simulator setup. Also the test failures from CI run are 
unrelated to this 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.
---


Failed to create VPC: Unable to start VPC VR (VM DomainRouter) due to error in finalizeStart, not retrying

2016-04-27 Thread Prashanth Manthena
Hi All,

I am seeing the following issue on master:
https://issues.apache.org/jira/browse/CLOUDSTACK-9370.

Is anyone else seeing this issue on master ?

Let me know, if you need more information from my side.

With regards,
Prashanth


RE: Building Ubuntu 16.04 packages

2016-04-27 Thread Rohit Yadav
Hi Wido,

Thanks for starting this discussion. I'm not sure exactly how to do it either, 
but I suppose we can exploit post installation step to write custom scripts 
that setup initd or systemd scripts at suitable locations. For this we include 
both init/systemd scripts in the package (let say at some location like 
/usr/share/... and let post install script pick up the template and setup inid 
scripts). This way I think we can explore if there is a way to solve for 
building universal deb package.

Regards.

Regards,

Rohit Yadav

rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue

-Original Message-
From: Wido den Hollander [mailto:w...@widodh.nl] 
Sent: Wednesday, April 27, 2016 1:40 PM
To: dev@cloudstack.apache.org
Subject: Building Ubuntu 16.04 packages

Hi,

Ubuntu 16.04 LTS was released about a week ago and I want to start on packages.

The cool things about the LTS:
- systemd
- Java 8
- libvirt 1.3.1
- Qemu 2.5

I'm familiar with building DEB packages, but there is something which I don't 
know how to fix yet.

We want to build packages for Ubuntu 14.04 and Ubuntu 16.04, but the first 
still uses Upstart / sysvinit and the newest uses systemd.

We already have systemd service files in 'packaging/systemd', so that is no the 
problem.

I however don't know how to build packages for 14.04 (Trusty) and 16.04 
(Xenial) using dpkg-buildpackage.

I see other projects use tools like pbuilder [0], but I don't know how that 
exactly works.

Before I put a lot of effort in this: Does anybody know how to build packages 
for different Ubuntu versions?

Eventually we will end up with packages like:

- cloudstack-agent-XXX~trusty.deb
- cloudstack-agent-XXX~xenial.deb

Thanks,

Wido

[0]: https://pbuilder.alioth.debian.org/


Re: PRs for 4.9 Release

2016-04-27 Thread Nux!
Same thing, pr for the right master :)

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

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Nux!" 
> To: dev@cloudstack.apache.org
> Sent: Wednesday, 27 April, 2016 10:59:37
> Subject: Re: PRs for 4.9 Release

> Thanks, created
> 
> https://github.com/NuxRo/cloudstack/pull/1
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> - Original Message -
>> From: "Remi Bergsma" 
>> To: dev@cloudstack.apache.org
>> Sent: Wednesday, 27 April, 2016 09:09:26
>> Subject: Re: PRs for 4.9 Release
> 
>> Let's make this your first PR Lucian ;-)
>> 
>> You can do it! Let me know if you need help :-)
>> 
>> Regards, Remi
>> 
>> Sent from my iPhone
>> 
>>> On 27 Apr 2016, at 10:06, Nux!  wrote:
>>> 
>>> Hello,
>>> 
>>> Can we pull this in as well? A simple fix to a silly simple issue (wrong CPU
>>> count for libvirt)?
>>> 
>>> https://github.com/MissionCriticalCloud/cosmic-plugin-hypervisor-kvm/pull/16
>>> 
>>> Thanks
>>> 
>>> --
>>> Sent from the Delta quadrant using Borg technology!
>>> 
>>> Nux!
>>> www.nux.ro
>>> 
>>> - Original Message -
 From: "Will Stevens" 
 To: dev@cloudstack.apache.org
 Sent: Thursday, 7 April, 2016 17:15:38
 Subject: PRs for 4.9 Release
>>> 
 I know this is not how this usually works, but I need to crowd source some
 info to be more effective.
 
 I am slowly getting things rolling for the 4.9 release.  My CI is chugging
 away and I have a queue of PRs to get tested, so I will be getting through
 them as quickly as I can.  I have finally gotten to where I have a
 relatively steady stream of merges going in and I am working through final
 logistics on a whole bunch.
 
 I would like some help prioritizing PRs that we feel MUST get into 4.9.
 There are almost 200 PRs open right now so it is not realistic for me to
 expect to get them all into the 4.9 release simply due to the number of CI
 hours needed.
 
 If you know of PRs that you think are important to get in, please reply
 with a link to the Github PR so I can get them into my active list.
 
 One more thing...
 
 If you have any extra hardware available that is not currently being used
 and you are willing to help with the CI effort, please email me and I will
 get you setup so you can contribute to testing.  I would like to try to get
 a distributed network of CI environments working to better test the ACS
 code base, so even if you only have the hardware free for 2 weeks, we can
 make use of it.  I can help you get the hardware up and running ready for
 testing in a couple hours.
 
 Thanks you for the support...
 
> > >> Will


[GitHub] cloudstack pull request: CPU socket count reporting correction

2016-04-27 Thread NuxRo
GitHub user NuxRo opened a pull request:

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

CPU socket count reporting correction

CPU socket count reporting correction
From 
https://github.com/MissionCriticalCloud/cosmic-plugin-hypervisor-kvm/pull/16

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

$ git pull https://github.com/NuxRo/cloudstack kvm-numa-cpu-reporting

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

https://github.com/apache/cloudstack/pull/1520.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 #1520


commit 42de1f81ed13145374a5838459ce068881966e8c
Author: NuxRo 
Date:   2016-04-27T09:49:53Z

CPU socket count reporting correction

CPU socket count reporting correction
From 
https://github.com/MissionCriticalCloud/cosmic-plugin-hypervisor-kvm/pull/16




---
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: 4.9 mvn version safeupgradeonly

2016-04-27 Thread DaanHoogland
Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1510#issuecomment-215048942
  
LGTM, i had run the tests as well, with no more then the usual problems 
&*%(^%. Note that part of the change is mine when you take my lgtm for it;)


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


  1   2   >