[GitHub] cloudstack issue #1547: Fixes for VirtualRouters in Basic Networking, especi...
Github user wido commented on the issue: https://github.com/apache/cloudstack/pull/1547 @swill I agree, but that's also because this bug is hitting and hurting us. However, I need other people to say 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. ---
CloudStack 4.8.0 with LXC - LibvirtException: unsupported configuration: System lacks NETNS support
Dear all,
We tried to setup an LXC cluster and add an LXC host into a test CloudStack
4.8.0.1 environment. The cluster is created and the LXC host is created
successfully. We also tried to follow below documentation to create an
Ubuntu LXC template -- we are running Ubuntu 12.04.5 LTS.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/LXC+Template+creation
===
Install lxc: apt-get install lxc
Create a container with any name, in our case 'ubuntu':
sudo lxc-create -t download -n ubuntu -- --dist ubuntu --release trusty
--arch amd64
Creation of the LXC container will take a lot of time, it will be stored
here: /var/lib/lxc/ubuntu
Next stop the container:
sudo lxc-stop -n ubuntu
Next create a temp director, tar the rootfs and export the template:
mkdir -p /tmp/lxc-template
cd /tmp/lxc-template
sudo tar --numeric-owner -czf /tmp/lxc-template/template.tar.gz
/var/lib/lxc/ubuntu/rootfs/
===
As per suggestion from Rohit on another thread, I saved the template file
as .tar and register it to cloudstack with HVM disabled. I then tried to
create an LXC container instance using the template, but after a long
"Creating" process, the provisioning will fail with insufficient capacity
error.
===
2016-06-10 18:24:45,468 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-44:ctx-c8a4afdc job-232) (logid:523a0c37) Complete async
job-232, jobStatus: FAILED, resultCode: 530, result:
org.apache.cloudstack.api.response.ExceptionR
esponse/null/{"uuidList":[],"errorcode":530,"errortext":"Unable to start a
VM due to insufficient capacity"}
===
Further check on the LXC host's agent.log shows that the provisioning
failed due to libvirt exception, which says that the configuration is
unsupported because the system lacks NETNS support
"LibvirtException: unsupported configuration: System lacks NETNS support"
See excerpts of the logs below:
===
2016-06-10 18:24:43,740 DEBUG [resource.wrapper.LibvirtStartCommandWrapper]
(agentRequest-Handler-1:null) starting i-2-42-VM:
i-2-42-VM
c29a74fb-e4bc-4aa2-bef4-3c8844de87df
Ubuntu 14.04 (64-bit)
1048576
1
exe
/sbin/init
1000
restart
destroy
destroy
2016-06-10 18:24:43,743 WARN [resource.wrapper.LibvirtStartCommandWrapper]
(agentRequest-Handler-1:null) LibvirtException
org.libvirt.LibvirtException: unsupported configuration: System lacks NETNS
support
at org.libvirt.ErrorHandler.processError(Unknown Source)
at org.libvirt.ErrorHandler.processError(Unknown Source)
at org.libvirt.Connect.domainCreateXML(Unknown Source)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.startVM(LibvirtComputingResource.java:1293)
at
com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStartCommandWrapper.execute(LibvirtStartCommandWrapper.java:82)
at
com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStartCommandWrapper.execute(LibvirtStartCommandWrapper.java:46)
at
com.cloud.hypervisor.kvm.resource.wrapper.LibvirtRequestWrapper.execute(LibvirtRequestWrapper.java:75)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1317)
at com.cloud.agent.Agent.processRequest(Agent.java:522)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:830)
at com.cloud.utils.nio.Task.call(Task.java:83)
at com.cloud.utils.nio.Task.call(Task.java:29)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
2016-06-10 18:24:43,744 DEBUG [kvm.storage.KVMStoragePoolManager]
(agentRequest-Handler-1:null) Disconnecting disk
6d26a879-999f-4cba-bfcc-1d2d9e70af5c
2016-06-10 18:24:43,744 INFO [kvm.storage.LibvirtStorageAdaptor]
(agentRequest-Handler-1:null) Trying to fetch storage pool
d7678837-9f9f-32ab-99f3-b508feb3595a from libvirt
2016-06-10 18:24:43,744 DEBUG [kvm.resource.LibvirtConnection]
(agentRequest-Handler-1:null) Looking for libvirtd connection at: lxc:///
2016-06-10 18:24:43,751 DEBUG [kvm.storage.LibvirtStorageAdaptor]
(agentRequest-Handler-1:null) Succesfully refreshed pool
d7678837-9f9f-32ab-99f3-b508feb3595a Capacity: 483387244544 Used:
127107334144 Available: 356279910400
2016-06-10 18:24:43,757 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-1:null) Seq 7-8790463522673787745: { Ans: , MgmtId:
181122461655966, via: 7, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.StartAnswer":{"vm":{"id":42,"name":"i-2-42-VM","type":"User","cpus":1,"minSpeed":1000,"maxSpeed":2000,"minRam":1073741824,"maxRam":1073741824,"arch":"x86_64","os":"Ubuntu
14.04 (64-bit)","platformEmulator":"Ubuntu
14.04","bootArgs":"","enableHA":true,"limitCpuUse":true,"enableDynamicallyScaleVm":false,"vncPassword":"hOWX3h7K6kkOpL316OApzQ","vncAddr":"192.168.3.202","params":{"memoryOvercommitRatio":"1.0",
[GitHub] cloudstack issue #1547: Fixes for VirtualRouters in Basic Networking, especi...
Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/1547 @wido judging from your testing and commentary, I believe this has your LGTM? You have not officially specified that it does. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1585: CLOUDSTACK-9399 : NPE during deletion of host when c...
Github user prashanthvarma commented on the issue: https://github.com/apache/cloudstack/pull/1585 Marvin Test Run: CloudStack$ nosetests --with-marvin --marvin-config=nuage.cfg /test/integration/plugins/nuagevsp Marvin Test Results: Test user data and password reset functionality with Nuage VSP SDN plugin ... === TestName: test_nuage_UserDataPasswordReset | Status : SUCCESS === ok Test Nuage VSP VPC Offering with different combinations of LB service providers ... === TestName: test_01_nuage_internallb_vpc_Offering | Status : SUCCESS === ok Test Nuage VSP VPC Network Offering with and without Internal LB service ... === TestName: test_02_nuage_internallb_vpc_network_offering | Status : SUCCESS === ok Test Nuage VSP VPC Networks with and without Internal LB service ... === TestName: test_03_nuage_internallb_vpc_networks | Status : SUCCESS === ok Test Nuage VSP VPC Internal LB functionality with different combinations of Internal LB rules ... === TestName: test_04_nuage_internallb_rules | Status : SUCCESS === ok Test Nuage VSP VPC Internal LB functionality by performing (wget) traffic tests within a VPC ... === TestName: test_05_nuage_internallb_traffic | Status : SUCCESS === ok Test Nuage VSP VPC Internal LB functionality with different LB algorithms by performing (wget) traffic tests ... === TestName: test_06_nuage_internallb_algorithms_traffic | Status : SUCCESS === ok Test Nuage VSP VPC Internal LB functionality with restarts of VPC network components by performing (wget) ... === TestName: test_07_nuage_internallb_vpc_network_restarts_traffic | Status : SUCCESS === ok Test Nuage VSP VPC Internal LB functionality with InternalLbVm appliance operations by performing (wget) ... === TestName: test_08_nuage_internallb_appliance_operations_traffic | Status : SUCCESS === ok Test basic VPC Network functionality with Nuage VSP SDN plugin ... === TestName: test_nuage_vpc_network | Status : SUCCESS === ok Test basic VPC Network functionality with Nuage VSP SDN plugin on multiple zones ... SKIP: There is only one Zone configured: skipping test Test Nuage VSP SDN plugin with basic Isolated Network functionality ... === TestName: test_nuage_vsp | Status : SUCCESS === ok Test Nuage VSP device in the Nuage VSP Physical Network ... === TestName: test_nuage_vsp_device | Status : SUCCESS === ok Ran 13 tests in 8562.574s OK (SKIP=1) Marvin Test Run Logs: [results.txt](https://github.com/apache/cloudstack/files/308973/results.txt) [runinfo.txt](https://github.com/apache/cloudstack/files/308975/runinfo.txt) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #827: BUG-ID: CLOUDSTACK-8849: Usage job should stop usage ...
Github user bvbharatk commented on the issue: https://github.com/apache/cloudstack/pull/827 ### ACS CI BVT Run **Sumarry:** Build Number 176 Hypervisor xenserver NetworkType Advanced Passed=73 Failed=0 Skipped=3 _Link to logs Folder (search by build_no):_ https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0 **Failed tests:** **Skipped tests:** test_vm_nic_adapter_vmxnet3 test_static_role_account_acls test_deploy_vgpu_enabled_vm **Passed test suits:** test_deploy_vm_with_userdata.py test_affinity_groups_projects.py test_portable_publicip.py test_vpc_vpn.py test_over_provisioning.py test_global_settings.py test_scale_vm.py test_service_offerings.py test_routers_iptables_default_policy.py test_routers.py test_reset_vm_on_reboot.py test_snapshots.py test_deploy_vms_with_varied_deploymentplanners.py test_login.py test_list_ids_parameter.py test_public_ip_range.py test_multipleips_per_nic.py test_regions.py test_affinity_groups.py test_network_acl.py test_pvlan.py test_volumes.py test_nic.py test_deploy_vm_root_resize.py test_resource_detail.py test_secondary_storage.py test_vm_life_cycle.py test_disk_offerings.py --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1581: CLOUDSTACK-9404 Fixed ordering of network ACL rules ...
Github user pdube commented on the issue: https://github.com/apache/cloudstack/pull/1581 Thanks @dmabry --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: ICLA for contributors
You are right. The paragraph that I quoted from Apache is pretty clear about that. They do recommend getting ICLAs from everyone but as you said, it is not required. The CCLA is important and I would hope that the main corporate supporters are all covered. Ron On 09/06/2016 1:46 PM, Pierre-Luc Dion wrote: Hi Ron, As far as I know, ICLA and CCLA is required for commiters, but not required for non-commiters contributors. I don't know about all details, someone else in the ML might have more details about this. For sure, you can be a contributor without submitting code as a anyone in this ML is consider as a contributor. Cheers, On Thu, Jun 9, 2016 at 11:46 AM, Ron Wheeler wrote: As part of a discussion during last weeks meeting in Mpntreal, the question was raised about the requirement to have an Individual Contributor License Agreement (ICLA) for each contributor. http://www.apache.org/licenses/ describes the requirements as follows: "The ASF desires that all contributors of ideas, code, or documentation to any Apache projects complete, sign, and submit (via fax or email) an Individual Contributor License Agreement (ICLA). The purpose of this agreement is to clearly define the terms under which intellectual property has been contributed to the ASF and thereby allow us to defend the project should there be a legal dispute regarding the software at some future time. A signed ICLA is required to be on file before an individual is given commit rights to an ASF project. For a corporation that has assigned employees to work on an Apache project, a Corporate CLA (CCLA) is available for contributing intellectual property via the corporation, that may have been assigned as part of an employment agreement. Note that a Corporate CLA does not remove the need for every developer to sign their own ICLA as an individual, to cover any of their contributions which are not owned by the corporation signing the CCLA." There is a split between desirable and mandatory. I am not sure that the argument that submitting a PR is a clear sign of intent to give up all rights, has ever been tested in a court but it is much easier to have an signed ICLA for each contributor. A CCLA for each company that is either paying people to work on the project or has a clause in their employment contract giving the company rights to all IP created during their employment is required. This removes any ambiguity about the individual's right to make a PR. It is a little bit of housekeeping to keep track of the list of contributors with ICLA's. A wiki page listing the contributors is a simple solution. https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+Contributors is what we did at OFBiz. The ICLA and CCLA is good for all Apache projects. Ron -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102
Re: ICLA for contributors
That is correct from my reading of the Apache page as well. I think that your definition of committer and contributor is identical to Apache's. Ron On 09/06/2016 3:57 PM, John Burwell wrote: All, I believe Pierre-Luc’s explanation is correct, and that we may have slightly different definitions of contributor and committer. Generally, we define a contributor, we are referring to anyone (committer, PMC member, any person in the world) who contributes code, documentation, etc to the project. We define a committer as a contributor who demonstrated a strong and sustained commitment to the project. In recognition of this commitment, committers are granted the right to commit changes to the project’s public repositories. Execution of an ICLA and CCLA are required in order for someone to become an Apache CloudStack committer. IANAL, but my understanding is that any individual can contribute to an Apache project without signing an ICLA/CCLA because a committer with one in place will perform commit to the repository. The act of the individual giving code to the project and a committer reviewing and committing it to the repository qualifies as rights assignment under by the ASL. Since execution of an ICLA/CCLA is a prerequisite for all Apache CloudStack committers and Apache secures our repositories to only allow committers read/write access, rights assignment under the ASL for our repositories is properly enforced/managed. Thanks, -John john.burw...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London VA WC2N 4HSUK @shapeblue On Jun 9, 2016, at 1:46 PM, Pierre-Luc Dion wrote: Hi Ron, As far as I know, ICLA and CCLA is required for commiters, but not required for non-commiters contributors. I don't know about all details, someone else in the ML might have more details about this. For sure, you can be a contributor without submitting code as a anyone in this ML is consider as a contributor. Cheers, On Thu, Jun 9, 2016 at 11:46 AM, Ron Wheeler wrote: As part of a discussion during last weeks meeting in Mpntreal, the question was raised about the requirement to have an Individual Contributor License Agreement (ICLA) for each contributor. http://www.apache.org/licenses/ describes the requirements as follows: "The ASF desires that all contributors of ideas, code, or documentation to any Apache projects complete, sign, and submit (via fax or email) an Individual Contributor License Agreement (ICLA). The purpose of this agreement is to clearly define the terms under which intellectual property has been contributed to the ASF and thereby allow us to defend the project should there be a legal dispute regarding the software at some future time. A signed ICLA is required to be on file before an individual is given commit rights to an ASF project. For a corporation that has assigned employees to work on an Apache project, a Corporate CLA (CCLA) is available for contributing intellectual property via the corporation, that may have been assigned as part of an employment agreement. Note that a Corporate CLA does not remove the need for every developer to sign their own ICLA as an individual, to cover any of their contributions which are not owned by the corporation signing the CCLA." There is a split between desirable and mandatory. I am not sure that the argument that submitting a PR is a clear sign of intent to give up all rights, has ever been tested in a court but it is much easier to have an signed ICLA for each contributor. A CCLA for each company that is either paying people to work on the project or has a clause in their employment contract giving the company rights to all IP created during their employment is required. This removes any ambiguity about the individual's right to make a PR. It is a little bit of housekeeping to keep track of the list of contributors with ICLA's. A wiki page listing the contributors is a simple solution. https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+Contributors is what we did at OFBiz. The ICLA and CCLA is good for all Apache projects. Ron -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102
Re: ICLA for contributors
Ron, As part of committer on-boarding, the PMC requires each committer candidate have an ASF ICLA in place and verifies the CCLA of their employer. Thanks, -John > john.burw...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London VA WC2N 4HSUK @shapeblue On Jun 10, 2016, at 10:47 AM, Ron Wheeler wrote: > > That is correct from my reading of the Apache page as well. > I think that your definition of committer and contributor is identical to > Apache's. > > > Ron > > On 09/06/2016 3:57 PM, John Burwell wrote: >> All, >> >> I believe Pierre-Luc’s explanation is correct, and that we may have slightly >> different definitions of contributor and committer. Generally, we define a >> contributor, we are referring to anyone (committer, PMC member, any person >> in the world) who contributes code, documentation, etc to the project. We >> define a committer as a contributor who demonstrated a strong and sustained >> commitment to the project. In recognition of this commitment, committers >> are granted the right to commit changes to the project’s public >> repositories. Execution of an ICLA and CCLA are required in order for >> someone to become an Apache CloudStack committer. >> >> IANAL, but my understanding is that any individual can contribute to an >> Apache project without signing an ICLA/CCLA because a committer with one in >> place will perform commit to the repository. The act of the individual >> giving code to the project and a committer reviewing and committing it to >> the repository qualifies as rights assignment under by the ASL. Since >> execution of an ICLA/CCLA is a prerequisite for all Apache CloudStack >> committers and Apache secures our repositories to only allow committers >> read/write access, rights assignment under the ASL for our repositories is >> properly enforced/managed. >> >> Thanks, >> -John >> >> john.burw...@shapeblue.com >> www.shapeblue.com >> 53 Chandos Place, Covent Garden, London VA WC2N 4HSUK >> @shapeblue >> >> >> On Jun 9, 2016, at 1:46 PM, Pierre-Luc Dion wrote: >>> Hi Ron, >>> >>> As far as I know, ICLA and CCLA is required for commiters, but not required >>> for non-commiters contributors. I don't know about all details, someone >>> else in the ML might have more details about this. For sure, you can be a >>> contributor without submitting code as a anyone in this ML is consider as a >>> contributor. >>> >>> Cheers, >>> >>> >>> On Thu, Jun 9, 2016 at 11:46 AM, Ron Wheeler >>> wrote: As part of a discussion during last weeks meeting in Mpntreal, the question was raised about the requirement to have an Individual Contributor License Agreement (ICLA) for each contributor. http://www.apache.org/licenses/ describes the requirements as follows: "The ASF desires that all contributors of ideas, code, or documentation to any Apache projects complete, sign, and submit (via fax or email) an Individual Contributor License Agreement (ICLA). The purpose of this agreement is to clearly define the terms under which intellectual property has been contributed to the ASF and thereby allow us to defend the project should there be a legal dispute regarding the software at some future time. A signed ICLA is required to be on file before an individual is given commit rights to an ASF project. For a corporation that has assigned employees to work on an Apache project, a Corporate CLA (CCLA) is available for contributing intellectual property via the corporation, that may have been assigned as part of an employment agreement. Note that a Corporate CLA does not remove the need for every developer to sign their own ICLA as an individual, to cover any of their contributions which are not owned by the corporation signing the CCLA." There is a split between desirable and mandatory. I am not sure that the argument that submitting a PR is a clear sign of intent to give up all rights, has ever been tested in a court but it is much easier to have an signed ICLA for each contributor. A CCLA for each company that is either paying people to work on the project or has a clause in their employment contract giving the company rights to all IP created during their employment is required. This removes any ambiguity about the individual's right to make a PR. It is a little bit of housekeeping to keep track of the list of contributors with ICLA's. A wiki page listing the contributors is a simple solution. https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+Contributors is what we did at OFBiz. The ICLA and CCLA is good for all Apache projects. Ron -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435,
[GitHub] cloudstack issue #1585: CLOUDSTACK-9399 : NPE during deletion of host when c...
Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/1585 This fixes a bug in the current master right? I suspect this is a candidate to be merged into the frozen master to be released in 4.9? Please close and reopen this PR or force push to kick off Travis again, it timed out. Can I get one more code review? 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 #1589: Fixing erraneous guest_os_hypervisor mappings
GitHub user nnesic opened a pull request: https://github.com/apache/cloudstack/pull/1589 Fixing erraneous guest_os_hypervisor mappings We noticed some discrepancies in the guest_os_hypervisor mappings, specifically Other PV being mapped to CentOS on Xenserver, Ubuntu 10.04 pointing to CentOS and Ubuntu 12 for VmWare, KVM, and LXC. Here are some queries to show the problematic mappings before correction: ``` mysql> SELECT h.id, hypervisor_type, hypervisor_version, h.guest_os_name, g.display_name FROM guest_os_hypervisor h join guest_os g on g.id = h.guest_os_id where h.id in ( 420, 497, 569, 672, 783, 912, 1061, 1211, 2153, 421, 498, 570, 673, 784, 913, 1062, 1212, 2154, 173, 253, 2018, 254, 2019); +--+-++---+---+ | id | hypervisor_type | hypervisor_version | guest_os_name | display_name | +--+-++---+---+ | 173 | VmWare | default| Ubuntu 12.04 (32-bit) | CentOS 5.7 (64-bit) | | 253 | KVM | default| Ubuntu 10.04 | CentOS 5.7 (64-bit) | | 254 | KVM | default| Ubuntu 10.04 | Ubuntu 12.04 (32-bit) | | 420 | Xenserver | XCP 1.0| CentOS 5 (32-bit) | Other PV (32-bit) | | 421 | Xenserver | XCP 1.0| CentOS 5 (64-bit) | Other PV (64-bit) | | 497 | Xenserver | 5.6 FP1| CentOS 5 (32-bit) | Other PV (32-bit) | | 498 | Xenserver | 5.6 FP1| CentOS 5 (64-bit) | Other PV (64-bit) | | 569 | Xenserver | 5.6 SP2| CentOS 5 (32-bit) | Other PV (32-bit) | | 570 | Xenserver | 5.6 SP2| CentOS 5 (64-bit) | Other PV (64-bit) | | 672 | Xenserver | 6.0| CentOS 5 (32-bit) | Other PV (32-bit) | | 673 | Xenserver | 6.0| CentOS 5 (64-bit) | Other PV (64-bit) | | 783 | Xenserver | 6.0.2 | CentOS 5 (32-bit) | Other PV (32-bit) | | 784 | Xenserver | 6.0.2 | CentOS 5 (64-bit) | Other PV (64-bit) | | 912 | Xenserver | 6.1.0 | CentOS 5 (32-bit) | Other PV (32-bit) | | 913 | Xenserver | 6.1.0 | CentOS 5 (64-bit) | Other PV (64-bit) | | 1061 | Xenserver | 6.2.0 | CentOS 5 (32-bit) | Other PV (32-bit) | | 1062 | Xenserver | 6.2.0 | CentOS 5 (64-bit) | Other PV (64-bit) | | 1211 | Xenserver | 6.2.5 | CentOS 5 (32-bit) | Other PV (32-bit) | | 1212 | Xenserver | 6.2.5 | CentOS 5 (64-bit) | Other PV (64-bit) | | 2018 | LXC | default| Ubuntu 10.04 | CentOS 5.7 (64-bit) | | 2019 | LXC | default| Ubuntu 10.04 | Ubuntu 12.04 (32-bit) | | 2153 | Xenserver | 6.5.0 | CentOS 5 (32-bit) | Other PV (32-bit) | | 2154 | Xenserver | 6.5.0 | CentOS 5 (64-bit) | Other PV (64-bit) | +--+-++---+---+ mysql> select h.hypervisor_type, h.hypervisor_version, h.guest_os_name, g.display_name from guest_os_hypervisor h join guest_os g on g.id = h.guest_os_id where hypervisor_type = "kvm" and guest_os_name like "ubuntu%" order by guest_os_name; +-++---+---+ | hypervisor_type | hypervisor_version | guest_os_name | display_name | +-++---+---+ | KVM | default| Ubuntu 10.04 | Ubuntu 10.04 (32-bit) | | KVM | default| Ubuntu 10.04 | Ubuntu 12.04 (32-bit) | | KVM | default| Ubuntu 10.04 | CentOS 5.7 (64-bit) | | KVM | default| Ubuntu 10.04 | Ubuntu 10.04 (64-bit) | | KVM | default| Ubuntu 10.10 | Ubuntu 10.10 (64-bit) | | KVM | default| Ubuntu 10.10 | Ubuntu 10.10 (32-bit) | | KVM | default| Ubuntu 12.04 | Ubuntu 12.04 (64-bit) | | KVM | default| Ubuntu 14.04 | Ubuntu 14.04 (64-bit) | | KVM | default| Ubuntu 14.04 | Ubuntu 14.04 (32-bit) | | KVM | default| Ubuntu 8.04 | Ubuntu 8.04 (64-bit) | | KVM | default| Ubuntu 8.04 | Ubuntu 8.04 (32-bit) | | KVM | default| Ubuntu 8.10 | Ub
[GitHub] cloudstack issue #1585: CLOUDSTACK-9399 : NPE during deletion of host when c...
Github user prashanthvarma commented on the issue: https://github.com/apache/cloudstack/pull/1585 @swill Yes, this is a bug in current master, and IMHO is a candidate to be merged into the frozen master to be released in 4.9. Note: As of know, there have been two code reviews in this PR from the community. We will force push to kick off Travis again, and will keep you updated. Thank you !! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1455: [CLOUDSTACK-9328]: Fix vlan issues from test suite t...
Github user bvbharatk commented on the issue: https://github.com/apache/cloudstack/pull/1455 ### ACS CI BVT Run **Sumarry:** Build Number 177 Hypervisor xenserver NetworkType Advanced Passed=65 Failed=1 Skipped=3 _Link to logs Folder (search by build_no):_ https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0 **Failed tests:** * test_vm_life_cycle.py * ContextSuite context=TestVMLifeCycle>:setup Failing since 2 runs **Skipped tests:** test_vm_nic_adapter_vmxnet3 test_static_role_account_acls test_deploy_vgpu_enabled_vm **Passed test suits:** test_deploy_vm_with_userdata.py test_affinity_groups_projects.py test_portable_publicip.py test_vpc_vpn.py test_over_provisioning.py test_global_settings.py test_scale_vm.py test_service_offerings.py test_routers_iptables_default_policy.py test_routers.py test_reset_vm_on_reboot.py test_snapshots.py test_deploy_vms_with_varied_deploymentplanners.py test_login.py test_list_ids_parameter.py test_public_ip_range.py test_multipleips_per_nic.py test_regions.py test_affinity_groups.py test_network_acl.py test_pvlan.py test_volumes.py test_nic.py test_deploy_vm_root_resize.py test_resource_detail.py test_secondary_storage.py test_disk_offerings.py --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1585: CLOUDSTACK-9399 : NPE during deletion of host when c...
Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/1585 Thank you. I am currently running CI on it as well to make sure it comes back clean. Hopefully we can get travis clean as well with a close and reopen. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1585: CLOUDSTACK-9399 : NPE during deletion of host when c...
Github user KrisSterckx commented on the issue: https://github.com/apache/cloudstack/pull/1585 @swill, you prefer i close and reopen? 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 issue #1585: CLOUDSTACK-9399 : NPE during deletion of host when c...
Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/1585 It is easier for you to just close and reopen, so that is usually the method people use. You can force push as well, either work... --- 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 #1585: CLOUDSTACK-9399 : NPE during deletion of host...
GitHub user nlivens reopened a pull request: https://github.com/apache/cloudstack/pull/1585 CLOUDSTACK-9399 : NPE during deletion of host when clusterId is null In most network plugins, there's a Resource class which will handle the communication with the actual device / underlaying client / ... They're configured as a host, so ACS is able to send commands towards it. When they're configured as a host, the clusterId is not filled in since it's not relevant. Hence, the NPE while deleting this host because of ```long clusterId = host.getClusterId();``` You can merge this pull request into a Git repository by running: $ git pull https://github.com/nlivens/cloudstack CLOUDSTACK-9399 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1585.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 #1585 commit ffe72ca227a518907bca396603a2641e10c5d02d Author: Nick Livens Date: 2016-06-03T09:04:09Z CLOUDSTACK-9399 : NPE during deletion of host when clusterId is null commit e972273bf17bedd089b0ef0716615b183dec4135 Author: Prashanth Manthena Date: 2016-06-03T18:51:25Z CLOUDSTACK-9399 : Marvin test coverage for Nuage VSP device CRUD operations commit 7531f24d7374be18eac04000ffac12ee5c462953 Author: Prashanth Manthena Date: 2016-06-08T13:35:33Z Nuage VSP : Enhancing Marvin test coverage --- 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 #1585: CLOUDSTACK-9399 : NPE during deletion of host...
Github user nlivens closed the pull request at: https://github.com/apache/cloudstack/pull/1585 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1581: CLOUDSTACK-9404 Fixed ordering of network ACL rules ...
Github user dmabry commented on the issue: https://github.com/apache/cloudstack/pull/1581 @pdube No problem. Think you could kick this off again and see if Travis comes back green? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1443: CLOUDSTACK-9314 - Remove unused code from XenServerS...
Github user bvbharatk commented on the issue: https://github.com/apache/cloudstack/pull/1443 ### ACS CI BVT Run **Sumarry:** Build Number 178 Hypervisor xenserver NetworkType Advanced Passed=72 Failed=1 Skipped=3 _Link to logs Folder (search by build_no):_ https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0 **Failed tests:** * test_vpc_vpn.py * test_01_vpc_remote_access_vpn Failed **Skipped tests:** test_vm_nic_adapter_vmxnet3 test_static_role_account_acls test_deploy_vgpu_enabled_vm **Passed test suits:** test_deploy_vm_with_userdata.py test_affinity_groups_projects.py test_portable_publicip.py test_over_provisioning.py test_global_settings.py test_scale_vm.py test_service_offerings.py test_routers_iptables_default_policy.py test_routers.py test_reset_vm_on_reboot.py test_snapshots.py test_deploy_vms_with_varied_deploymentplanners.py test_login.py test_list_ids_parameter.py test_public_ip_range.py test_multipleips_per_nic.py test_regions.py test_affinity_groups.py test_network_acl.py test_pvlan.py test_volumes.py test_nic.py test_deploy_vm_root_resize.py test_resource_detail.py test_secondary_storage.py test_vm_life_cycle.py test_disk_offerings.py --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack pull request #1581: CLOUDSTACK-9404 Fixed ordering of network ACL...
Github user pdube closed the pull request at: https://github.com/apache/cloudstack/pull/1581 --- 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 #1581: CLOUDSTACK-9404 Fixed ordering of network ACL...
GitHub user pdube reopened a pull request: https://github.com/apache/cloudstack/pull/1581 CLOUDSTACK-9404 Fixed ordering of network ACL rules being sent to the VR. The comparator was inverted. Issue: https://issues.apache.org/jira/browse/CLOUDSTACK-9404 In this example, I created rules with the port numbers the same as the rule numbers. Chain ACL_INBOUND_eth2 (1 references) target prot opt source destination ACCEPT all -- anywhere 225.0.0.50 ACCEPT all -- anywhere vrrp.mcast.net DROP tcp -- anywhere anywhere tcp dpt:netstat DROP tcp -- anywhere anywhere tcp dpt:10 DROP tcp -- anywhere anywhere tcp dpt:5 DROP tcp -- anywhere anywhere tcp dpt:3 DROP tcp -- anywhere anywhere tcp dpt:2 DROP all -- anywhere anywhere We can see above that the rules are inverted. After the fix: Chain ACL_INBOUND_eth2 (1 references) target prot opt source destination ACCEPT all -- anywhere 225.0.0.50 ACCEPT all -- anywhere vrrp.mcast.net DROP tcp -- anywhere anywhere tcp dpt:2 DROP tcp -- anywhere anywhere tcp dpt:3 DROP tcp -- anywhere anywhere tcp dpt:5 DROP tcp -- anywhere anywhere tcp dpt:10 DROP tcp -- anywhere anywhere tcp dpt:netstat DROP all -- anywhere anywhere You can merge this pull request into a Git repository by running: $ git pull https://github.com/pdube/cloudstack network-acl-rules-order Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1581.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 #1581 commit caf4a48075e0f59b5d101efdd3ac6b1bee8f4f39 Author: Patrick Dube Date: 2016-06-02T17:15:38Z Fixed ordering of network ACL rules being sent to the VR. The comparator was inverted commit 4c97a3981dc0d543e02f62f2bb4fc2eb805545c6 Author: Patrick Dube Date: 2016-06-02T17:44:39Z Added unit test to verify ordering commit 9cdd23fdc77e643d886c3af8cb0a60f9c4ddf84f Author: Patrick Dube Date: 2016-06-03T12:48:47Z Added ASF license to unit test file --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1531: systemvmtemplate: fix build and upgrade to debian 7....
Github user bvbharatk commented on the issue: https://github.com/apache/cloudstack/pull/1531 ### ACS CI BVT Run **Sumarry:** Build Number 179 Hypervisor xenserver NetworkType Advanced Passed=73 Failed=0 Skipped=3 _Link to logs Folder (search by build_no):_ https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0 **Failed tests:** **Skipped tests:** test_vm_nic_adapter_vmxnet3 test_static_role_account_acls test_deploy_vgpu_enabled_vm **Passed test suits:** test_deploy_vm_with_userdata.py test_affinity_groups_projects.py test_portable_publicip.py test_vpc_vpn.py test_over_provisioning.py test_global_settings.py test_scale_vm.py test_service_offerings.py test_routers_iptables_default_policy.py test_routers.py test_reset_vm_on_reboot.py test_snapshots.py test_deploy_vms_with_varied_deploymentplanners.py test_login.py test_list_ids_parameter.py test_public_ip_range.py test_multipleips_per_nic.py test_regions.py test_affinity_groups.py test_network_acl.py test_pvlan.py test_volumes.py test_nic.py test_deploy_vm_root_resize.py test_resource_detail.py test_secondary_storage.py test_vm_life_cycle.py test_disk_offerings.py --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1530: Vmdk findbugs
Github user bvbharatk commented on the issue: https://github.com/apache/cloudstack/pull/1530 ### ACS CI BVT Run **Sumarry:** Build Number 180 Hypervisor xenserver NetworkType Advanced Passed=69 Failed=1 Skipped=3 _Link to logs Folder (search by build_no):_ https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0 **Failed tests:** * test_routers.py * test_04_restart_network_wo_cleanup Failed **Skipped tests:** test_vm_nic_adapter_vmxnet3 test_static_role_account_acls test_deploy_vgpu_enabled_vm **Passed test suits:** test_deploy_vm_with_userdata.py test_affinity_groups_projects.py test_portable_publicip.py test_over_provisioning.py test_global_settings.py test_scale_vm.py test_service_offerings.py test_routers_iptables_default_policy.py test_reset_vm_on_reboot.py test_snapshots.py test_deploy_vms_with_varied_deploymentplanners.py test_login.py test_list_ids_parameter.py test_public_ip_range.py test_multipleips_per_nic.py test_regions.py test_affinity_groups.py test_network_acl.py test_pvlan.py test_volumes.py test_nic.py test_deploy_vm_root_resize.py test_resource_detail.py test_secondary_storage.py test_vm_life_cycle.py test_disk_offerings.py --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: CloudStack 4.8.0 with LXC - LibvirtException: unsupported configuration: System lacks NETNS support
Dear all,
Anyone implemented LXC on CloudStack before and can provide some advice?
Documentation is a bit limited on this area. Other than below
documentations, any other pointers anyone can provide?
http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.8/hypervisor/lxc.html
https://cwiki.apache.org/confluence/display/CLOUDSTACK/LXC+Template+creation
https://cwiki.apache.org/confluence/display/CLOUDSTACK/LXC+Support+in+Cloudstack
https://cwiki.apache.org/confluence/display/CLOUDSTACK/LXC+Enhancements
Looking forward to your reply, thank you.
Cheers.
-ip-
On Fri, Jun 10, 2016 at 6:39 PM, Cloud List wrote:
> Dear all,
>
> We tried to setup an LXC cluster and add an LXC host into a test
> CloudStack 4.8.0.1 environment. The cluster is created and the LXC host is
> created successfully. We also tried to follow below documentation to create
> an Ubuntu LXC template -- we are running Ubuntu 12.04.5 LTS.
>
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/LXC+Template+creation
>
> ===
> Install lxc: apt-get install lxc
>
> Create a container with any name, in our case 'ubuntu':
>
> sudo lxc-create -t download -n ubuntu -- --dist ubuntu --release trusty
> --arch amd64
>
> Creation of the LXC container will take a lot of time, it will be stored
> here: /var/lib/lxc/ubuntu
>
> Next stop the container:
> sudo lxc-stop -n ubuntu
>
> Next create a temp director, tar the rootfs and export the template:
> mkdir -p /tmp/lxc-template
> cd /tmp/lxc-template
> sudo tar --numeric-owner -czf /tmp/lxc-template/template.tar.gz
> /var/lib/lxc/ubuntu/rootfs/
> ===
>
> As per suggestion from Rohit on another thread, I saved the template file
> as .tar and register it to cloudstack with HVM disabled. I then tried to
> create an LXC container instance using the template, but after a long
> "Creating" process, the provisioning will fail with insufficient capacity
> error.
>
> ===
> 2016-06-10 18:24:45,468 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-44:ctx-c8a4afdc job-232) (logid:523a0c37) Complete async
> job-232, jobStatus: FAILED, resultCode: 530, result:
> org.apache.cloudstack.api.response.ExceptionR
> esponse/null/{"uuidList":[],"errorcode":530,"errortext":"Unable to start a
> VM due to insufficient capacity"}
> ===
>
> Further check on the LXC host's agent.log shows that the provisioning
> failed due to libvirt exception, which says that the configuration is
> unsupported because the system lacks NETNS support
>
> "LibvirtException: unsupported configuration: System lacks NETNS support"
>
> See excerpts of the logs below:
>
> ===
> 2016-06-10 18:24:43,740 DEBUG
> [resource.wrapper.LibvirtStartCommandWrapper] (agentRequest-Handler-1:null)
> starting i-2-42-VM:
> i-2-42-VM
> c29a74fb-e4bc-4aa2-bef4-3c8844de87df
> Ubuntu 14.04 (64-bit)
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>dir='/mnt/d7678837-9f9f-32ab-99f3-b508feb3595a/6d26a879-999f-4cba-bfcc-1d2d9e70af5c'/>
>
>
>
>
>
>
>
>
>
> 1048576
>
>
>
> 1
>
> exe
> /sbin/init
>
>
> 1000
>
> restart
> destroy
> destroy
>
>
> 2016-06-10 18:24:43,743 WARN
> [resource.wrapper.LibvirtStartCommandWrapper] (agentRequest-Handler-1:null)
> LibvirtException
> org.libvirt.LibvirtException: unsupported configuration: System lacks
> NETNS support
> at org.libvirt.ErrorHandler.processError(Unknown Source)
> at org.libvirt.ErrorHandler.processError(Unknown Source)
> at org.libvirt.Connect.domainCreateXML(Unknown Source)
> at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.startVM(LibvirtComputingResource.java:1293)
> at
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStartCommandWrapper.execute(LibvirtStartCommandWrapper.java:82)
> at
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStartCommandWrapper.execute(LibvirtStartCommandWrapper.java:46)
> at
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtRequestWrapper.execute(LibvirtRequestWrapper.java:75)
> at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1317)
> at com.cloud.agent.Agent.processRequest(Agent.java:522)
> at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:830)
> at com.cloud.utils.nio.Task.call(Task.java:83)
> at com.cloud.utils.nio.Task.call(Task.java:29)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> 2016-06-10 18:24:43,744 DEBUG [kvm.storage.KVMStoragePoolManager]
> (agentRequest-Handler-1:null) Disconnecting disk
> 6d26a879-999f-4cba-bfcc-1d2d9e70af5c
> 2016-06-10 18:24:43,744 INFO [kvm.storage.LibvirtStorageAdaptor]
> (agentRequest-Handler-1:null) Trying to fetch storage pool
> d7678837-9f9f-32ab-99f3-b5
