[
https://issues.apache.org/jira/browse/CLOUDSTACK-9379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542770#comment-15542770
]
ASF GitHub Bot commented on CLOUDSTACK-9379:
--------------------------------------------
Github user nvazquez commented on the issue:
https://github.com/apache/cloudstack/pull/1542
Hi @rhtyd, we ran `test_internal_lb.py` and `test_vpc_vpn.py` using
`tl-vmware.ova` template and got this results:
`test_vpc_vpn` is ok:
```
Test Site 2 Site VPN Across redundant VPCs ... === TestName:
test_01_redundant_vpc_site2site_vpn | Status : SUCCESS ===
ok
Test Remote Access VPN in VPC ... === TestName:
test_01_vpc_remote_access_vpn | Status : SUCCESS ===
ok
Test Site 2 Site VPN Across VPCs ... === TestName:
test_01_vpc_site2site_vpn | Status : SUCCESS ===
ok
----------------------------------------------------------------------
Ran 3 tests in 1949.605s
OK
```
However, `test_internal_lb` fails, we could find some issues:
- /sbin/ip is needed but not present in template {Cmd: /sbin/ip addr show
eth0 |grep 'inet '| cut -f6 -d' ' > /tmp/index.html via Host: 10.140.12.107}
{returns: [u'sh: /sbin/ip: not found']}
- 2 more tests fail due to a difference in wget on new template: {Cmd:
/usr/bin/wget -T3 -qO- --user=XX --password=XX http://XXXX:8081/admin?stats via
Host: 10.140.12.106} {returns: [u"/usr/bin/wget: unrecognized option '..
- We have some strange erros in this functions which require more arguments
than given but couldn't find out why
```
2016-10-02 22:13:20,881 - CRITICAL - EXCEPTION:
execute_internallb_haproxy_tests: ['Traceback (most recent call last):\n', '
File "/usr/local/lib/python2.7/unittest/case.py", line 331, in run\n
testMethod()\n', 'TypeError: execute_internallb_haproxy_tests() takes exactly 2
arguments (1 given)\n']
2016-10-02 22:13:20,883 - CRITICAL - EXCEPTION:
execute_internallb_roundrobin_tests: ['Traceback (most recent call last):\n', '
File "/usr/local/lib/python2.7/unittest/case.py", line 331, in run\n
testMethod()\n', 'TypeError: execute_internallb_roundrobin_tests() takes
exactly 2 arguments (1 given)\n']
2016-10-02 22:13:20,885 - CRITICAL - EXCEPTION: run_ssh_test_accross_hosts:
['Traceback (most recent call last):\n', ' File
"/usr/local/lib/python2.7/unittest/case.py", line 331, in run\n
testMethod()\n', 'TypeError: run_ssh_test_accross_hosts() takes at least 3
arguments (1 given)\n']
```
> Support nested virtualization at VM level on VMware Hypervisor
> --------------------------------------------------------------
>
> Key: CLOUDSTACK-9379
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9379
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.9.0
> Reporter: Nicolas Vazquez
> Assignee: Nicolas Vazquez
> Fix For: 4.10.0.0
>
>
> h2. Introduction
> It is desired to support nested virtualization at VM level for VMware
> hypervisor. Current behaviour supports enabling/desabling global nested
> virtualization by modifying global config {{'vmware.nested.virtualization'}}.
> It is wished to improve this feature, having control at VM level instead of a
> global control only.
> h2. Proposal
> A new global configuration is added, to enable/disable VM nested
> virtualization control: {{'vmware.nested.virtualization.perVM'}}. Default
> value=false
> h2. Behaviour
> After a vm deployment or start command, vm params include
> {{nestedVirtualizationFlag}} key and its value is:
> * true -> nested virtualization enabled
> * false -> nested virtualization disabled
> We will determinate nested virtualization enabled/disabled by examining:
> * (1) global configuration {{'vmware.nested.virtualization'}} value
> * (2) global configuration {{'vmware.nested.virtualization.perVM'}} value
> * (3) {{'nestedVirtualizationFlag'}} value in {{user_vm_details}} if present,
> null if not.
> Using this 3 values, there are different use cases:
> # (1) = TRUE, (2) = TRUE, (3) is null -> ENABLED
> # (1) = TRUE, (2) = TRUE, (3) = TRUE -> ENABLED
> # (1) = TRUE, (2) = TRUE, (3) = FALSE -> DISABLED
> # (1) = TRUE, (2) = FALSE -> ENABLED
> # (1) = FALSE, (2) = TRUE, (3) is null -> DISABLED
> # (1) = FALSE, (2) = TRUE, (3) = TRUE -> ENABLED
> # (1) = FALSE, (2) = TRUE, (3) = FALSE -> DISABLED
> # (1) = FALSE, (2) = FALSE -> DISABLED
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
