date:20170220

Re: [PROPOSAL] add native vm-cluster orchestration service (was: [PROPOSAL] add native container orchestration service)

2017-02-20 Thread Wido den Hollander


> Op 20 februari 2017 om 14:56 schreef Daan Hoogland 
> :
> 
> 
> So, being very late in the discussion but havingread the whole thread before 
> editting the title of this thread,
> 
> Can we agree that we want a generic vm-cluster service and leave the 
> container bits to containers? Kishan can you share your design? Shapeblue 
> wants to rebase their k8 service on top of this and I would like yours and 
> Murali's work to not conflict.
> 

I like that a lot more. This way it wouldn't only be containers, but think of 
spawning a cluster of VMs together which form a MariaDB Galera cluster for 
example.

Such features are very welcome!

Wido

> daan.hoogl...@shapeblue.com 
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, Utrecht Utrecht 3531 VENetherlands
> @shapeblue
>   
>  
> 
> 
> -Original Message-
> From: Paul Angus [mailto:paul.an...@shapeblue.com] 
> Sent: dinsdag 7 februari 2017 08:14
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native container orchestration service
> 
> Will is 100% correct.  As I mentioned the Title is misleading.  However, 
> Murali did clarify in his explanation; this is really about vm cluster 
> orchestration.
> 
> 
> 
> 
> From: Will Stevens 
> Sent: 6 Feb 2017 22:54
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native container orchestration service
> 
> My understanding is that what Paul is talking about is what is already built 
> and IS what the thread is talking about.
> 
> *Will STEVENS*
> Lead Developer
> 
> 
> 
> On Mon, Feb 6, 2017 at 2:29 PM, Rajesh Ramchandani < 
> rajesh.ramchand...@accelerite.com> wrote:
> 
> > Hi Paul - I think this is different from what the thread was about. 
> > The conversation was specifically about adding support for container 
> > orchestrators. You are talking about provisioning a group of VMs. 
> > Although, this is something I think several Cloudstack users have 
> > requested before and we should propose a solution to this.
> >
> > Raj
> >
> > 
> > From: Paul Angus 
> > Sent: Monday, February 6, 2017 11:16:41 AM
> > To: dev@cloudstack.apache.org
> > Subject: RE: [PROPOSAL] add native container orchestration service
> >
> > #WhatHeSaid
> >
> > The title is misleading.  The proposal is purely to add the notion of 
> > Clusters of VMs to CloudStack.  These may be for databases, containers 
> > or anything else that needs 'clusters' of compute. Self-healing and 
> > autoscaling are logical next steps to be added.
> >
> > Those guys at ShapeBlue have open-sourced their whole k8s container 
> > service piece.  If/when the 'cluster' part of that work is added into 
> > CloudStack, the k8s specific pieces can be used by anyone who wants 
> > to, alternatively they could be used for reference in order to create 
> > another types of cluster.  (or ignored completely).
> >
> >
> >
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Will Stevens [mailto:williamstev...@gmail.com]
> > Sent: 31 January 2017 13:26
> > To: dev@cloudstack.apache.org
> > Subject: Re: [PROPOSAL] add native container orchestration service
> >
> > s/cloud-init/cloud-config/
> >
> > On Jan 31, 2017 7:24 AM, "Will Stevens"  wrote:
> >
> > > I think that is covered in this proposal. There is nothing k8s
> > > specific in this integration (from what I understand), all the k8s
> > > details are passed in via the cloud-init configuration after the cluster
> > has been provisioned.
> > >
> > > On Jan 31, 2017 3:06 AM, "Lianghwa Jou" 
> > > wrote:
> > >
> > >
> > > There are many container orchestrators. Those container orchestrators
> > > are happy to run on any VMs or bare metal machines. K8s is just one of
> > > them and there will be more in the future. It may not be a good idea
> > > to make CloudStack to be k8s aware. IMO, the relationship between k8s
> > > and cloudstack should be similar to application and os. It probably
> > > not a good idea to make your OS to be aware of any specific
> > > applications so IMHO I don’t think k8s should be native to CloudStack.
> > > It makes more sense to provide some generic services that many
> > > applications can take advantages of. Some generic resource grouping
> > > service makes sense so a group of VMs, baremetal machines or network
> > > can be treated as a single entity. Some life cycle management will be
> > > necessary for these entities too. We can deploy k8s, swarm, dcos or
> > > even non-container specific services on top of CloudStack. The k8s is
> > > changing fast. One single tenant installation may need more than one
> > > VM group and may actually requires more (k8s federation). It will be a
> > >

[GitHub] cloudstack issue #1841: CLOUDSTACK-9684 Invalid zone id error while listing ...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1841
  
Trillian test result (tid-861)
Environment: vmware-60u2 (x2), Advanced Networking with Mgmt server 7
Total time taken: 43746 seconds
Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1841-t861-vmware-60u2.zip
Intermitten failure detected: /marvin/tests/smoke/test_internal_lb.py
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermitten failure detected: 
/marvin/tests/smoke/test_routers_network_ops.py
Intermitten failure detected: /marvin/tests/smoke/test_snapshots.py
Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
Test completed. 47 look ok, 2 have error(s)


Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_04_rvpc_privategw_static_routes | `Failure` | 788.65 | 
test_privategw_acl.py
test_02_list_snapshots_with_removed_data_store | `Error` | 70.86 | 
test_snapshots.py
test_02_list_snapshots_with_removed_data_store | `Error` | 75.94 | 
test_snapshots.py
ContextSuite context=TestSnapshotRootDisk>:teardown | `Error` | 101.23 | 
test_snapshots.py
test_03_vpc_privategw_restart_vpc_cleanup | `Error` | 817.80 | 
test_privategw_acl.py
test_03_vpc_privategw_restart_vpc_cleanup | `Error` | 848.20 | 
test_privategw_acl.py
test_01_vpc_site2site_vpn | Success | 332.24 | test_vpc_vpn.py
test_01_vpc_remote_access_vpn | Success | 182.45 | test_vpc_vpn.py
test_01_redundant_vpc_site2site_vpn | Success | 549.91 | test_vpc_vpn.py
test_02_VPC_default_routes | Success | 335.12 | test_vpc_router_nics.py
test_01_VPC_nics_after_destroy | Success | 666.47 | test_vpc_router_nics.py
test_05_rvpc_multi_tiers | Success | 581.68 | test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics | Success | 1529.06 | 
test_vpc_redundant.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
Success | 669.18 | test_vpc_redundant.py
test_02_redundant_VPC_default_routes | Success | 614.34 | 
test_vpc_redundant.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1300.01 | 
test_vpc_redundant.py
test_09_delete_detached_volume | Success | 20.84 | test_volumes.py
test_06_download_detached_volume | Success | 45.47 | test_volumes.py
test_05_detach_volume | Success | 100.27 | test_volumes.py
test_04_delete_attached_volume | Success | 10.20 | test_volumes.py
test_03_download_attached_volume | Success | 15.28 | test_volumes.py
test_02_attach_volume | Success | 49.27 | test_volumes.py
test_01_create_volume | Success | 505.66 | test_volumes.py
test_change_service_offering_for_vm_with_snapshots | Success | 496.97 | 
test_vm_snapshots.py
test_03_delete_vm_snapshots | Success | 275.20 | test_vm_snapshots.py
test_02_revert_vm_snapshots | Success | 222.17 | test_vm_snapshots.py
test_01_test_vm_volume_snapshot | Success | 136.18 | test_vm_snapshots.py
test_01_create_vm_snapshots | Success | 161.64 | test_vm_snapshots.py
test_deploy_vm_multiple | Success | 252.74 | test_vm_life_cycle.py
test_deploy_vm | Success | 0.03 | test_vm_life_cycle.py
test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py
test_10_attachAndDetach_iso | Success | 26.71 | test_vm_life_cycle.py
test_09_expunge_vm | Success | 125.25 | test_vm_life_cycle.py
test_08_migrate_vm | Success | 55.97 | test_vm_life_cycle.py
test_07_restore_vm | Success | 0.11 | test_vm_life_cycle.py
test_06_destroy_vm | Success | 5.13 | test_vm_life_cycle.py
test_03_reboot_vm | Success | 5.14 | test_vm_life_cycle.py
test_02_start_vm | Success | 20.29 | test_vm_life_cycle.py
test_01_stop_vm | Success | 10.14 | test_vm_life_cycle.py
test_CreateTemplateWithDuplicateName | Success | 191.32 | test_templates.py
test_08_list_system_templates | Success | 0.03 | test_templates.py
test_07_list_public_templates | Success | 0.04 | test_templates.py
test_05_template_permissions | Success | 0.06 | test_templates.py
test_04_extract_template | Success | 10.18 | test_templates.py
test_03_delete_template | Success | 5.11 | test_templates.py
test_02_edit_template | Success | 90.19 | test_templates.py
test_01_create_template | Success | 91.26 | test_templates.py
test_10_destroy_cpvm | Success | 211.82 | test_ssvm.py
test_09_destroy_ssvm | Success | 233.76 | test_ssvm.py
test_08_reboot_cpvm | Success | 156.64 | test_ssvm.py
test_07_reboot_ssvm | Success | 188.58 | test_ssvm.py
test_06_stop_cpvm | Success | 171.95 | test_ssvm.py
test_05_stop_ssvm | Success | 268.73 | test_ssvm.py
test_04_cpvm_internals | Success | 1.22 | test_ssvm.py
test_03_ssvm_internals | Success | 3.54 | test_ssvm.py
test_02_list_cpvm_vm | Success | 0.14 | test_ssvm.py
test_01_list_sec_storage_vm | Success | 0.14 | test_ssvm.py

[GitHub] cloudstack issue #843: Security group ingress/egress issues with xenserver 6...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/843
  
Packaging result: âcentos6 âcentos7 âdebian. JID-516


---
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 #1861: CLOUDSTACK-9698 [VMware] Make hardcorded wait timeou...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1861
  
Trillian test result (tid-857)
Environment: vmware-60u2 (x2), Advanced Networking with Mgmt server 7
Total time taken: 43900 seconds
Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1861-t857-vmware-60u2.zip
Intermitten failure detected: /marvin/tests/smoke/test_password_server.py
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermitten failure detected: 
/marvin/tests/smoke/test_routers_network_ops.py
Intermitten failure detected: /marvin/tests/smoke/test_snapshots.py
Test completed. 46 look ok, 3 have error(s)


Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_04_rvpc_privategw_static_routes | `Failure` | 839.08 | 
test_privategw_acl.py
ContextSuite context=TestSnapshotRootDisk>:setup | `Error` | 0.00 | 
test_snapshots.py
test_01_vpc_site2site_vpn | Success | 362.16 | test_vpc_vpn.py
test_01_vpc_remote_access_vpn | Success | 152.29 | test_vpc_vpn.py
test_01_redundant_vpc_site2site_vpn | Success | 568.38 | test_vpc_vpn.py
test_02_VPC_default_routes | Success | 339.73 | test_vpc_router_nics.py
test_01_VPC_nics_after_destroy | Success | 705.08 | test_vpc_router_nics.py
test_05_rvpc_multi_tiers | Success | 622.89 | test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics | Success | 1524.82 | 
test_vpc_redundant.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
Success | 694.21 | test_vpc_redundant.py
test_02_redundant_VPC_default_routes | Success | 634.97 | 
test_vpc_redundant.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1335.68 | 
test_vpc_redundant.py
test_09_delete_detached_volume | Success | 31.39 | test_volumes.py
test_06_download_detached_volume | Success | 45.51 | test_volumes.py
test_05_detach_volume | Success | 100.28 | test_volumes.py
test_04_delete_attached_volume | Success | 10.58 | test_volumes.py
test_03_download_attached_volume | Success | 15.45 | test_volumes.py
test_02_attach_volume | Success | 49.22 | test_volumes.py
test_01_create_volume | Success | 507.32 | test_volumes.py
test_03_delete_vm_snapshots | Success | 275.25 | test_vm_snapshots.py
test_02_revert_vm_snapshots | Success | 222.18 | test_vm_snapshots.py
test_01_test_vm_volume_snapshot | Success | 161.81 | test_vm_snapshots.py
test_01_create_vm_snapshots | Success | 161.63 | test_vm_snapshots.py
test_deploy_vm_multiple | Success | 267.76 | test_vm_life_cycle.py
test_deploy_vm | Success | 0.03 | test_vm_life_cycle.py
test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py
test_10_attachAndDetach_iso | Success | 26.98 | test_vm_life_cycle.py
test_09_expunge_vm | Success | 185.31 | test_vm_life_cycle.py
test_08_migrate_vm | Success | 66.29 | test_vm_life_cycle.py
test_07_restore_vm | Success | 0.11 | test_vm_life_cycle.py
test_06_destroy_vm | Success | 5.13 | test_vm_life_cycle.py
test_03_reboot_vm | Success | 5.15 | test_vm_life_cycle.py
test_02_start_vm | Success | 20.23 | test_vm_life_cycle.py
test_01_stop_vm | Success | 5.13 | test_vm_life_cycle.py
test_CreateTemplateWithDuplicateName | Success | 206.46 | test_templates.py
test_08_list_system_templates | Success | 0.03 | test_templates.py
test_07_list_public_templates | Success | 0.04 | test_templates.py
test_05_template_permissions | Success | 0.06 | test_templates.py
test_04_extract_template | Success | 10.19 | test_templates.py
test_03_delete_template | Success | 5.11 | test_templates.py
test_02_edit_template | Success | 90.11 | test_templates.py
test_01_create_template | Success | 105.83 | test_templates.py
test_10_destroy_cpvm | Success | 236.82 | test_ssvm.py
test_09_destroy_ssvm | Success | 268.80 | test_ssvm.py
test_08_reboot_cpvm | Success | 156.59 | test_ssvm.py
test_07_reboot_ssvm | Success | 158.47 | test_ssvm.py
test_06_stop_cpvm | Success | 206.94 | test_ssvm.py
test_05_stop_ssvm | Success | 203.91 | test_ssvm.py
test_04_cpvm_internals | Success | 1.23 | test_ssvm.py
test_03_ssvm_internals | Success | 3.67 | test_ssvm.py
test_02_list_cpvm_vm | Success | 0.13 | test_ssvm.py
test_01_list_sec_storage_vm | Success | 0.14 | test_ssvm.py
test_04_change_offering_small | Success | 93.45 | test_service_offerings.py
test_03_delete_service_offering | Success | 0.04 | test_service_offerings.py
test_02_edit_service_offering | Success | 0.06 | test_service_offerings.py
test_01_create_service_offering | Success | 0.14 | test_service_offerings.py
test_02_sys_template_ready | Success | 0.17 | test_secondary_storage.py
test_01_sys_vm_start | Success | 0.18 | test_secondary_storage.py
test_09_reboot_router | Success | 145.98 | test_routers.py

[GitHub] cloudstack issue #1878: CLOUDSTACK-9717: [VMware] RVRs have mismatching MAC ...

2017-02-20 Thread borisstoyanov

Github user borisstoyanov commented on the issue:

https://github.com/apache/cloudstack/pull/1878
  
@blueorangutan package


---
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 #1950: [4.10] CLOUDSTACK-9462: Build packages on Ubuntu 14....

2017-02-20 Thread borisstoyanov

Github user borisstoyanov commented on the issue:

https://github.com/apache/cloudstack/pull/1950
  
Hi @rhtyd, Ubuntu installation of ACS fails with the dependency error we 
discussed last week. Don't know where is the issue since it fails on the 
Trillian images, but you reported you were able to install it locally on 14.04. 


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

[GitHub] cloudstack issue #1951: CLOUDSTACK-9792: Add upgrade path for 4.9.3.0

2017-02-20 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1951
  
Thanks @borisstoyanov 
@karuturi ping


---
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 #1950: [4.10] CLOUDSTACK-9462: Build packages on Ubuntu 14....

2017-02-20 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1950
  
@borisstoyanov can you please identify the failures against Ubuntu 
environment, thanks.


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

[GitHub] cloudstack issue #1948: [CLOUDSTACK-9793] Faster IP in subnet check

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1948
  
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been 
kicked to run smoke tests


---
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 #1948: [CLOUDSTACK-9793] Faster IP in subnet check

2017-02-20 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1948
  
@borisstoyanov cloud-scripts tarball in the systemvm.iso will have the 
router/scripts. We can test it.
@blueorangutan 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 issue #1949: Automated Cloudstack bugs 9277 9276 9275 9274 9273 9...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1949
  
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you 
posted as I make progress.


---
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 #1949: Automated Cloudstack bugs 9277 9276 9275 9274 9273 9...

2017-02-20 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1949
  
@blueorangutan package


---
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 #1829: CLOUDSTACK-9363: Fix HVM VM restart bug in XenServer

2017-02-20 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1829
  
@karuturi let's merge 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 issue #1779: CLOUDSTACK-9610: Disabled Host Keeps Being up status...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1779
  
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you 
posted as I make progress.


---
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 #1779: CLOUDSTACK-9610: Disabled Host Keeps Being up status...

2017-02-20 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1779
  
@blueorangutan package


---
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 #843: Security group ingress/egress issues with xenserver 6...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/843
  
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you 
posted as I make progress.


---
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 #1829: CLOUDSTACK-9363: Fix HVM VM restart bug in XenServer

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1829
  
Trillian test result (tid-859)
Environment: vmware-60u2 (x2), Advanced Networking with Mgmt server 7
Total time taken: 41776 seconds
Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1829-t859-vmware-60u2.zip
Intermitten failure detected: /marvin/tests/smoke/test_network_acl.py
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermitten failure detected: 
/marvin/tests/smoke/test_routers_network_ops.py
Intermitten failure detected: /marvin/tests/smoke/test_routers.py
Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
Test completed. 47 look ok, 1 have error(s)


Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_04_rvpc_privategw_static_routes | `Failure` | 793.81 | 
test_privategw_acl.py
test_01_vpc_site2site_vpn | Success | 335.98 | test_vpc_vpn.py
test_01_vpc_remote_access_vpn | Success | 151.80 | test_vpc_vpn.py
test_01_redundant_vpc_site2site_vpn | Success | 573.88 | test_vpc_vpn.py
test_02_VPC_default_routes | Success | 344.49 | test_vpc_router_nics.py
test_01_VPC_nics_after_destroy | Success | 620.84 | test_vpc_router_nics.py
test_05_rvpc_multi_tiers | Success | 712.09 | test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics | Success | 1503.75 | 
test_vpc_redundant.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
Success | 663.91 | test_vpc_redundant.py
test_02_redundant_VPC_default_routes | Success | 660.26 | 
test_vpc_redundant.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1326.76 | 
test_vpc_redundant.py
test_09_delete_detached_volume | Success | 20.84 | test_volumes.py
test_06_download_detached_volume | Success | 45.49 | test_volumes.py
test_05_detach_volume | Success | 100.28 | test_volumes.py
test_04_delete_attached_volume | Success | 10.19 | test_volumes.py
test_03_download_attached_volume | Success | 15.32 | test_volumes.py
test_02_attach_volume | Success | 48.82 | test_volumes.py
test_01_create_volume | Success | 435.15 | test_volumes.py
test_03_delete_vm_snapshots | Success | 275.22 | test_vm_snapshots.py
test_02_revert_vm_snapshots | Success | 189.72 | test_vm_snapshots.py
test_01_test_vm_volume_snapshot | Success | 146.51 | test_vm_snapshots.py
test_01_create_vm_snapshots | Success | 161.85 | test_vm_snapshots.py
test_deploy_vm_multiple | Success | 252.67 | test_vm_life_cycle.py
test_deploy_vm | Success | 0.03 | test_vm_life_cycle.py
test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py
test_10_attachAndDetach_iso | Success | 26.87 | test_vm_life_cycle.py
test_09_expunge_vm | Success | 185.26 | test_vm_life_cycle.py
test_08_migrate_vm | Success | 61.32 | test_vm_life_cycle.py
test_07_restore_vm | Success | 0.10 | test_vm_life_cycle.py
test_06_destroy_vm | Success | 10.22 | test_vm_life_cycle.py
test_03_reboot_vm | Success | 5.15 | test_vm_life_cycle.py
test_02_start_vm | Success | 15.21 | test_vm_life_cycle.py
test_01_stop_vm | Success | 5.12 | test_vm_life_cycle.py
test_CreateTemplateWithDuplicateName | Success | 186.38 | test_templates.py
test_08_list_system_templates | Success | 0.03 | test_templates.py
test_07_list_public_templates | Success | 0.04 | test_templates.py
test_05_template_permissions | Success | 0.06 | test_templates.py
test_04_extract_template | Success | 10.20 | test_templates.py
test_03_delete_template | Success | 5.10 | test_templates.py
test_02_edit_template | Success | 90.18 | test_templates.py
test_01_create_template | Success | 95.72 | test_templates.py
test_10_destroy_cpvm | Success | 201.86 | test_ssvm.py
test_09_destroy_ssvm | Success | 233.61 | test_ssvm.py
test_08_reboot_cpvm | Success | 156.70 | test_ssvm.py
test_07_reboot_ssvm | Success | 188.51 | test_ssvm.py
test_06_stop_cpvm | Success | 171.84 | test_ssvm.py
test_05_stop_ssvm | Success | 178.69 | test_ssvm.py
test_04_cpvm_internals | Success | 1.10 | test_ssvm.py
test_03_ssvm_internals | Success | 3.41 | test_ssvm.py
test_02_list_cpvm_vm | Success | 0.12 | test_ssvm.py
test_01_list_sec_storage_vm | Success | 0.15 | test_ssvm.py
test_01_snapshot_root_disk | Success | 21.18 | test_snapshots.py
test_04_change_offering_small | Success | 86.76 | test_service_offerings.py
test_03_delete_service_offering | Success | 0.04 | test_service_offerings.py
test_02_edit_service_offering | Success | 0.07 | test_service_offerings.py
test_01_create_service_offering | Success | 0.11 | test_service_offerings.py
test_02_sys_template_ready | Success | 0.13 | test_secondary_storage.py
test_01_sys_vm_start | Success | 0.17 | test_secondary_storage.py
test_09_reboot_router |

[GitHub] cloudstack issue #843: Security group ingress/egress issues with xenserver 6...

2017-02-20 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/843
  
Thanks @jayapalu makes sense.
@blueorangutan package


---
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 #1847: CLOUDSTACK-9691: Fixed unhandeled excetion in list s...

2017-02-20 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1847
  
@borisstoyanov can you have a look at ^^, thanks.


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

[GitHub] cloudstack issue #1880: CLOUDSTACK-9720: [VMware] template_spool_ref table i...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1880
  
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + vmware-55u3) has been 
kicked to run smoke tests


---
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: [QUESTION] Upgrade path to JDK8

2017-02-20 Thread Wei ZHOU

Marco,

Good point. Is there any issue if we compile code with jdk8 but run it on
jdk7 (systemvm) ?

-Wei

2017-02-21 7:43 GMT+01:00 Marc-Aurèle Brothier :

> There's a list of compatibility issues between Java 7 & Java 8 here
> http://www.oracle.com/technetwork/java/javase/8-
> compatibility-guide-2156366.
> html
>
> The main problem I would see in two system communicating while running
> different Java version is the way they handle serialization and
> de-serialization of objects which had been a problem in the past between
> some Java versions. AFAIK we're using JSON for that now, so if the code
> already compiles with Java8, it should not be a problem.
>
> On Mon, Feb 20, 2017 at 10:36 PM, Wei ZHOU  wrote:
>
> > We tested 4.7.1+systemd patches as well, it also works fine.
> >
> > -Wei
> >
> > 2017-02-20 22:34 GMT+01:00 Wei ZHOU :
> >
> > > @Will and @Syed, I build the packages of 4.9.2+systemd patches on
> ubuntu
> > > 16.04 (openjdk 8).
> > > Then install the packages to management server and kvm hosts (all are
> > > ubuntu 16.04 with openjdk8).
> > > The systemvm template is 4.6 with openjdk7.
> > >
> > > cpvm and ssvm work fine.
> > >
> > > As there is no java process in VR, so I did not check, VR should not be
> > > impacted.
> > >
> > > -Wei
> > >
> > > 2017-02-20 22:16 GMT+01:00 Pierre-Luc Dion :
> > >
> > >> That's quite interesting Chiradeep!
> > >>
> > >> so I could do something like this I guest:
> > >>
> > >> mvn clean install
> > >>
> > >> and then this one to build the systemvm.iso:
> > >> mvn -Psystemvm -source 1.7 -target 1.7 install
> > >>
> > >>
> > >> I'll give it a try! but for now, I'm worried about existing VR, they
> > must
> > >> continue to work while running on jdk7.  newer VPC would be ok to run
> > with
> > >> jdk8.  but we need to make sure while upgrading the management-server
> we
> > >> are not in the obligation to upgrade VR's.
> > >>
> > >> For sure it is required for strongswan + JDK8 to ugprade the VR, but a
> > >>  existing VR should remain usable for port forwarding, vm creation and
> > >> such...
> > >>
> > >> I'll post my finding...
> > >>
> > >> Thanks !
> > >>
> > >>
> > >>
> > >> On Mon, Feb 20, 2017 at 3:59 PM, Chiradeep Vittal <
> chirade...@gmail.com
> > >
> > >> wrote:
> > >>
> > >> > You can build the system vm with  -source 1.7 -target 1.7
> > >> > Also unless you are using Java8 features (lambda) the classfiles
> > >> produced
> > >> > by javac 8 should work in a 1.7 JVM
> > >> >
> > >> > Sent from my iPhone
> > >> >
> > >> > > On Feb 20, 2017, at 11:51 AM, Will Stevens  >
> > >> > wrote:
> > >> > >
> > >> > > yes, that is what I was expecting.  which is why I was asking
> about
> > >> Wei's
> > >> > > setup because he seems to have worked around that problem.  Or he
> > has
> > >> a
> > >> > > custom SystemVM template running with both JDK7 and JDK8.
> > >> > >
> > >> > > *Will STEVENS*
> > >> > > Lead Developer
> > >> > >
> > >> > > 
> > >> > >
> > >> > >> On Mon, Feb 20, 2017 at 2:20 PM, Syed Ahmed  >
> > >> > wrote:
> > >> > >>
> > >> > >> The problem is that systemvm.iso is built with java 8 whereas
> java
> > on
> > >> > the
> > >> > >> VR is java 7
> > >> > >>> On Mon, Feb 20, 2017 at 13:20 Will Stevens <
> wstev...@cloudops.com
> > >
> > >> > wrote:
> > >> > >>>
> > >> > >>> Did it work after resetting a VPC or when blowing away the SSVM
> or
> > >> > >> CPVM?  I
> > >> > >>> would not expect the SSVM or the CPVM to come up if the
> management
> > >> > server
> > >> > >>> was built with JDK8 and the system vm template is only using
> JDK7.
> > >> Can
> > >> > >> you
> > >> > >>> confirm?
> > >> > >>>
> > >> > >>> *Will STEVENS*
> > >> > >>> Lead Developer
> > >> > >>>
> > >> > >>> 
> > >> > >>>
> > >> >  On Mon, Feb 20, 2017 at 1:15 PM, Wei ZHOU <
> ustcweiz...@gmail.com
> > >
> > >> > wrote:
> > >> > 
> > >> >  We've tested management server 4.7.1 with ubuntu 16.04/openjdk8
> > and
> > >> >  systemvm 4.6 with debian7/openjdk7.
> > >> >  The systemvms (ssvm, cpvm) work fine.
> > >> > 
> > >> >  I agree we need consider the openjdk upgrade in systemvm
> > template.
> > >> > 
> > >> >  -Wei
> > >> > 
> > >> >  2017-02-20 18:15 GMT+01:00 Will Stevens  >:
> > >> > 
> > >> > > Regarding my question. Is it because of the version of Java
> that
> > >> the
> > >> > > systemvm.iso is built on?
> > >> > >
> > >> > > On Feb 20, 2017 11:58 AM, "Will Stevens" <
> wstev...@cloudops.com
> > >
> > >> > >>> wrote:
> > >> > >
> > >> > >> A question that is hidden in here is:
> > >> > >> - Why does the JDK version on the management server have to
> > match
> > >> > >> the
> > >> >  JDK
> > >> > >> version of the System VM?
> > >> > >>
> > >> > >> *Will STEVENS*
> > >> >

[GitHub] cloudstack issue #1880: CLOUDSTACK-9720: [VMware] template_spool_ref table i...

2017-02-20 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1880
  
@blueorangutan test centos7 vmware-55u3



---
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 #1875: CLOUDSTACK-8608: [VMware] System VMs failed to start...

2017-02-20 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1875
  
@blueorangutan test centos7 vmware-55u3



---
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 #1879: CLOUDSTACK-9719: [VMware] VR loses DHCP settings and...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1879
  
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + vmware-55u3) has been 
kicked to run smoke tests


---
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 #1875: CLOUDSTACK-8608: [VMware] System VMs failed to start...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1875
  
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + vmware-55u3) has been 
kicked to run smoke tests


---
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 #1879: CLOUDSTACK-9719: [VMware] VR loses DHCP settings and...

2017-02-20 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1879
  
@blueorangutan test centos7 vmware-55u3



---
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: [QUESTION] Upgrade path to JDK8

2017-02-20 Thread Marc-Aurèle Brothier

There's a list of compatibility issues between Java 7 & Java 8 here
http://www.oracle.com/technetwork/java/javase/8-compatibility-guide-2156366.
html

The main problem I would see in two system communicating while running
different Java version is the way they handle serialization and
de-serialization of objects which had been a problem in the past between
some Java versions. AFAIK we're using JSON for that now, so if the code
already compiles with Java8, it should not be a problem.

On Mon, Feb 20, 2017 at 10:36 PM, Wei ZHOU  wrote:

> We tested 4.7.1+systemd patches as well, it also works fine.
>
> -Wei
>
> 2017-02-20 22:34 GMT+01:00 Wei ZHOU :
>
> > @Will and @Syed, I build the packages of 4.9.2+systemd patches on ubuntu
> > 16.04 (openjdk 8).
> > Then install the packages to management server and kvm hosts (all are
> > ubuntu 16.04 with openjdk8).
> > The systemvm template is 4.6 with openjdk7.
> >
> > cpvm and ssvm work fine.
> >
> > As there is no java process in VR, so I did not check, VR should not be
> > impacted.
> >
> > -Wei
> >
> > 2017-02-20 22:16 GMT+01:00 Pierre-Luc Dion :
> >
> >> That's quite interesting Chiradeep!
> >>
> >> so I could do something like this I guest:
> >>
> >> mvn clean install
> >>
> >> and then this one to build the systemvm.iso:
> >> mvn -Psystemvm -source 1.7 -target 1.7 install
> >>
> >>
> >> I'll give it a try! but for now, I'm worried about existing VR, they
> must
> >> continue to work while running on jdk7.  newer VPC would be ok to run
> with
> >> jdk8.  but we need to make sure while upgrading the management-server we
> >> are not in the obligation to upgrade VR's.
> >>
> >> For sure it is required for strongswan + JDK8 to ugprade the VR, but a
> >>  existing VR should remain usable for port forwarding, vm creation and
> >> such...
> >>
> >> I'll post my finding...
> >>
> >> Thanks !
> >>
> >>
> >>
> >> On Mon, Feb 20, 2017 at 3:59 PM, Chiradeep Vittal  >
> >> wrote:
> >>
> >> > You can build the system vm with  -source 1.7 -target 1.7
> >> > Also unless you are using Java8 features (lambda) the classfiles
> >> produced
> >> > by javac 8 should work in a 1.7 JVM
> >> >
> >> > Sent from my iPhone
> >> >
> >> > > On Feb 20, 2017, at 11:51 AM, Will Stevens 
> >> > wrote:
> >> > >
> >> > > yes, that is what I was expecting.  which is why I was asking about
> >> Wei's
> >> > > setup because he seems to have worked around that problem.  Or he
> has
> >> a
> >> > > custom SystemVM template running with both JDK7 and JDK8.
> >> > >
> >> > > *Will STEVENS*
> >> > > Lead Developer
> >> > >
> >> > > 
> >> > >
> >> > >> On Mon, Feb 20, 2017 at 2:20 PM, Syed Ahmed 
> >> > wrote:
> >> > >>
> >> > >> The problem is that systemvm.iso is built with java 8 whereas java
> on
> >> > the
> >> > >> VR is java 7
> >> > >>> On Mon, Feb 20, 2017 at 13:20 Will Stevens  >
> >> > wrote:
> >> > >>>
> >> > >>> Did it work after resetting a VPC or when blowing away the SSVM or
> >> > >> CPVM?  I
> >> > >>> would not expect the SSVM or the CPVM to come up if the management
> >> > server
> >> > >>> was built with JDK8 and the system vm template is only using JDK7.
> >> Can
> >> > >> you
> >> > >>> confirm?
> >> > >>>
> >> > >>> *Will STEVENS*
> >> > >>> Lead Developer
> >> > >>>
> >> > >>> 
> >> > >>>
> >> >  On Mon, Feb 20, 2017 at 1:15 PM, Wei ZHOU  >
> >> > wrote:
> >> > 
> >> >  We've tested management server 4.7.1 with ubuntu 16.04/openjdk8
> and
> >> >  systemvm 4.6 with debian7/openjdk7.
> >> >  The systemvms (ssvm, cpvm) work fine.
> >> > 
> >> >  I agree we need consider the openjdk upgrade in systemvm
> template.
> >> > 
> >> >  -Wei
> >> > 
> >> >  2017-02-20 18:15 GMT+01:00 Will Stevens :
> >> > 
> >> > > Regarding my question. Is it because of the version of Java that
> >> the
> >> > > systemvm.iso is built on?
> >> > >
> >> > > On Feb 20, 2017 11:58 AM, "Will Stevens"  >
> >> > >>> wrote:
> >> > >
> >> > >> A question that is hidden in here is:
> >> > >> - Why does the JDK version on the management server have to
> match
> >> > >> the
> >> >  JDK
> >> > >> version of the System VM?
> >> > >>
> >> > >> *Will STEVENS*
> >> > >> Lead Developer
> >> > >>
> >> > >> 
> >> > >>
> >> > >> On Mon, Feb 20, 2017 at 11:50 AM, Pierre-Luc Dion <
> >> > >>> pd...@cloudops.com>
> >> > >> wrote:
> >> > >>
> >> > >>> Hi,
> >> > >>>
> >> > >>> In the context of deployment of CloudStack with VPCs,
> >> > >>> What will happen to a cloud when upgrading to 4.10 that now
> use
> >> > >>> jdk8?
> >> > >>>
> >> > >>> Does upgrading the management-server to 4.10 jdk8 and

Re: [DISCUSS][FS] Host HA for CloudStack

2017-02-20 Thread Rohit Yadav

Hi Koushik,


Thanks for sharing your comments and questions.


1. Yes, the FS is divided into two parts - a general HA framework which makes 
no assumption about the type of resource and HA provider implementation that 
works on a type of resource/hypervisor/storage etc. Specifically, with this 
feature we want to solve the problem of HA-ing a host reliably and use 
out-of-band management subsystem (i.e. ipmi based status/reboot/power-off to 
investigate/recover/fence the host) in the HA provider implementation. Yes, a 
host HA should trigger VM HA, i.e. for the host being fenced move HA VMs to 
other hosts. This also reliably solves the issue of disk corruption when same 
HA VMs get started on multiple hosts.


2. The old VM HA implementation makes a lot of assumptions about the type of 
resource (i.e. VM) it is HA-ing, it is tied to VM HA which is why HA for host 
could not be added in a straight forward way without regressions we could not 
test. With this new HA framework, it does not make any assumption around type 
of the resource and separates policy from mechanism, we also want to add 
deterministic tests (using marvin tests and a simulator based ha provider 
implementation) to demonstrate the generic HA functionality. In future with 
this framework, HA for various resources such as VM, storage, network can be 
added. As a first step we want to get the framework in, and support for Host as 
a resource type. We also want to reduce assumptions, or dependency as both VM 
HA and Host HA are related (sequence etc). The HAProvider interface would be 
something every hypervisor can implement.


3. While an existing (VM) HA framework exists, it was safer to write new code 
and demonstrate it works for any general HA resource than refactor and 
implement this in the old framework which could introduce serious regressions 
leading to production issues. For the most part, we've avoided to alter 
anything in the old HA framework while making sure that old (VM) HA works well 
with the new HA framework. The JIRA issue for the feature is in the FS.


4. Any HA operation can be blocking in nature, one of the things included is a 
background polling manager that polls for changes, and a task/activity executor 
as out-of-band operations can take time. Therefore, all the 
health/activity/fencing/recovery operations have some timeout, limits and 
specific queues. The existing framework does not provide any abstraction to 
queue, restrict operation timeout, and tie them against a FSM. The existing 
framework also is hard to test, specifically to validate using integration 
test. We also wanted to avoid adding any regressions to existing/old VM HA. 
Lastly, the primary use of IPMI/out-of-band management in performing host-ha is 
not for investigation but for recovery (try a reboot), and fencing (power off).


Hope this answers your questions, please feel free add more comments and 
questions. Thanks.


Regards.



From: Koushik Das 
Sent: 20 February 2017 11:45
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS][FS] Host HA for CloudStack

Rohit,

Thanks for the effort you have put in writing the FS. I have some questions 
based on my initial reading of the FS.

1. “Host HA” – In the FS you are talking about a generic HA framework but it is 
not clear what is meaning of “host HA”. Is it something like all or some VMs 
running on a host will be started on another host(s) in case of a failure or is 
it something else? How is it different from the existing “VM HA” that is 
already there?
2. You have mentioned that “Cloudstack lacks a way to reliably fence host”. 
Cloudstack considers VM as a 1st class object and so provides fencing for VM 
instead of host. There are hypervisor specific plugins that implement mechanism 
to fence a VM. I am not sure if it makes sense to expose host fencing as end 
user doesn’t care about it. Now the VM fencing implementation can use something 
like “host fencing” internally.
3. There is an existing HA framework which provides plugins for doing 
investigation if a VM is alive or not, host is alive or not, fencing of VM in 
case it is not alive. It will be good to understand the limitations of the 
existing framework and how the new framework helps in solving these problems. 
We also need to understand if the limitation is in the framework or some 
specific plugin implementation that is causing issues. Reference to JIRA issues 
would help.
4. You have mentioned about ipmi to investigate host failure. I would like to 
understand why same can’t be used in the existing framework.

Thanks,
Koushik

On 16/02/17, 4:48 PM, "Rohit Yadav"  wrote:

All,


I would like to start discussion on a new feature - Host HA for CloudStack.

CloudStack lacks a way to reliably fence a host, the idea of the host-ha 
feature is to provide a general purpose HA framework and HA provider 
implementation specific for

Re: [DISCUSS][FS] Host HA for CloudStack

2017-02-20 Thread Rohit Yadav

Hi David,


Thank you for your questions.


As per the FS, there is a HA framework implementation that is agnostic of the 
resource and is not tied to how the HA is performed separating policy from 
mechanism. The task of fencing is implemented by a HA provider which is 
implementation specific.


The first version will include a HA provider for KVM (with NFS backed primary 
storage) in which we've chosen to put the host into maintenance mode when it is 
fenced (by oobm/ipmi) and the admin is required to manually put them back to 
the pool (i.e. remove from maintenance mode) because doing this automatically 
may have side-effects. Also, by having the HA framework separated from the 
hypervisor/storage specific logic anyone is free to implement their own HA 
provider with custom logic, options and algorithms (as a plugin).


We can start by getting the HA framework and some initial HA provider (driver 
implementations) reviewed and accepted, and over time support for other 
hypervisor and storage options such as Ceph can be added.


Regards.



From: David Mabry 
Sent: 18 February 2017 03:40
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS][FS] Host HA for CloudStack



 Rohit,

First, thanks for all the work you have put into this.  This is something that 
CS has sorely needed for a long time.

A couple of items:

1.) You state the following:
“Before invoking the HA provider’s fence operation, the HA resource management 
will place the resource in maintenance mode. The intention is to require an 
administrator to manually verify that a resource is ready to return service by 
requiring an administrator to take it out of maintenance mode.”
I agree that putting a host in maintenance mode to require manual intervention 
in order to bring it back online is ideal and honestly how I would probably 
prefer to do it.  However, I also like to give the end user/operator choice.  
Perhaps we could add an option to bring the Host out of Maintenance mode 
automatically if it passes all checks and comes back into an ELIGIBLE state.  
This way, if the operator chooses, the host could come back into full operation 
and start recovering VMs if needed.  This could also be handy if your 
environment isn’t quite n+1 when it comes to host capacity and you need to have 
the host back up and running as soon as possible to minimize the outage 
duration.  Again, I know it isn’t ideal, but I don’t see the harm in giving the 
operator the choice.

2.) You state the following:
“For the initial release, only KVM with NFS storage will be supported. However, 
the storage check component will be implemented in a modular fashion allowing 
for checks using other storage platforms(e.g. Ceph) in the future. HA provider 
plugins can be implemented for other hypervisors.”
We are using KVM with a Ceph backend and would be very interested in helping 
make it a part of the initial push for this feature.  I have a Dev environment 
backed by Ceph that we could use for teseting and would be willing to help with 
the development of the Ceph activity checks.

I’m looking forward to getting this feature added to CS.  Again, great job 
putting this together and starting the conversation.

Thanks,
Mabry


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

[GitHub] cloudstack issue #1882: CLOUDSTACK-8737: Removed the missed out-of-band VR r...

2017-02-20 Thread cloudmonger

Github user cloudmonger commented on the issue:

https://github.com/apache/cloudstack/pull/1882
  
### ACS CI BVT Run
 **Sumarry:**
 Build Number 367
 Hypervisor xenserver
 NetworkType Advanced
 Passed=105
 Failed=0
 Skipped=7

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


**Failed tests:**

**Skipped tests:**
test_01_test_vm_volume_snapshot
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_11_ss_nfs_version_on_ssvm
test_nested_virtualization_vmware
test_3d_gpu_support
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_loadbalance.py
test_routers.py
test_reset_vm_on_reboot.py
test_deploy_vms_with_varied_deploymentplanners.py
test_network.py
test_router_dns.py
test_non_contigiousvlan.py
test_login.py
test_deploy_vm_iso.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_routers_network_ops.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 #1900: CLOUDSTACK-8862: Introduced new state attaching for ...

2017-02-20 Thread anshul1886

Github user anshul1886 commented on the issue:

https://github.com/apache/cloudstack/pull/1900
  
@karuturi @koushik-das @sateesh-chodapuneedi , I had analysed those 
failures and working on how to go about those. Issue here is that there are 
marvin tests which are for something which was never working. But nobody has 
reported any bugs for that. 
When we create VM without starting it(startvm=false), then there are 
issues. So in this scenario if we try to attach the uploaded volume then its 
failing in this PR. But in existing code it is passing successfully i.e. DB 
entries are created. Now when we start the VM then we are doing nothing for 
uploaded Volume and they always remains in uploaded state and not attached to 
VM on hypervisor.

This marvin test is there for ages but nobody has reported any issue 
regarding this. So I am currently analysing how to go about this. Is this even 
used by Users? Because if they were using this then somebody should have 
reported this as this was introduced some five years back. I am thinking of  
simple solution  which would be to inform user that they have to start vm first 
(root volume created) before trying to attach volume.


---
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 #1945: CLOUDSTACK-9787: Fix wrong return value in NetUtils....

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1945
  
Trillian test result (tid-862)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 28922 seconds
Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1945-t862-kvm-centos7.zip
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Test completed. 47 look ok, 1 have error(s)


Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_04_rvpc_privategw_static_routes | `Failure` | 365.60 | 
test_privategw_acl.py
test_01_vpc_site2site_vpn | Success | 170.06 | test_vpc_vpn.py
test_01_vpc_remote_access_vpn | Success | 66.09 | test_vpc_vpn.py
test_01_redundant_vpc_site2site_vpn | Success | 265.98 | test_vpc_vpn.py
test_02_VPC_default_routes | Success | 277.65 | test_vpc_router_nics.py
test_01_VPC_nics_after_destroy | Success | 535.79 | test_vpc_router_nics.py
test_05_rvpc_multi_tiers | Success | 518.84 | test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics | Success | 1400.94 | 
test_vpc_redundant.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
Success | 564.10 | test_vpc_redundant.py
test_02_redundant_VPC_default_routes | Success | 754.84 | 
test_vpc_redundant.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1300.39 | 
test_vpc_redundant.py
test_09_delete_detached_volume | Success | 156.42 | test_volumes.py
test_08_resize_volume | Success | 156.30 | test_volumes.py
test_07_resize_fail | Success | 161.31 | test_volumes.py
test_06_download_detached_volume | Success | 156.15 | test_volumes.py
test_05_detach_volume | Success | 155.94 | test_volumes.py
test_04_delete_attached_volume | Success | 151.29 | test_volumes.py
test_03_download_attached_volume | Success | 156.41 | test_volumes.py
test_02_attach_volume | Success | 95.21 | test_volumes.py
test_01_create_volume | Success | 711.26 | test_volumes.py
test_deploy_vm_multiple | Success | 247.57 | test_vm_life_cycle.py
test_deploy_vm | Success | 0.03 | test_vm_life_cycle.py
test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py
test_10_attachAndDetach_iso | Success | 26.65 | test_vm_life_cycle.py
test_09_expunge_vm | Success | 125.19 | test_vm_life_cycle.py
test_08_migrate_vm | Success | 40.85 | test_vm_life_cycle.py
test_07_restore_vm | Success | 0.14 | test_vm_life_cycle.py
test_06_destroy_vm | Success | 125.79 | test_vm_life_cycle.py
test_03_reboot_vm | Success | 125.77 | test_vm_life_cycle.py
test_02_start_vm | Success | 10.16 | test_vm_life_cycle.py
test_01_stop_vm | Success | 40.33 | test_vm_life_cycle.py
test_CreateTemplateWithDuplicateName | Success | 40.45 | test_templates.py
test_08_list_system_templates | Success | 0.03 | test_templates.py
test_07_list_public_templates | Success | 0.03 | test_templates.py
test_05_template_permissions | Success | 0.05 | test_templates.py
test_04_extract_template | Success | 5.34 | test_templates.py
test_03_delete_template | Success | 5.14 | test_templates.py
test_02_edit_template | Success | 90.15 | test_templates.py
test_01_create_template | Success | 40.40 | test_templates.py
test_10_destroy_cpvm | Success | 161.84 | test_ssvm.py
test_09_destroy_ssvm | Success | 163.68 | test_ssvm.py
test_08_reboot_cpvm | Success | 101.57 | test_ssvm.py
test_07_reboot_ssvm | Success | 133.58 | test_ssvm.py
test_06_stop_cpvm | Success | 131.69 | test_ssvm.py
test_05_stop_ssvm | Success | 163.74 | test_ssvm.py
test_04_cpvm_internals | Success | 1.25 | test_ssvm.py
test_03_ssvm_internals | Success | 3.59 | test_ssvm.py
test_02_list_cpvm_vm | Success | 0.12 | test_ssvm.py
test_01_list_sec_storage_vm | Success | 0.12 | test_ssvm.py
test_01_snapshot_root_disk | Success | 11.34 | test_snapshots.py
test_04_change_offering_small | Success | 239.64 | test_service_offerings.py
test_03_delete_service_offering | Success | 0.03 | test_service_offerings.py
test_02_edit_service_offering | Success | 0.05 | test_service_offerings.py
test_01_create_service_offering | Success | 0.10 | test_service_offerings.py
test_02_sys_template_ready | Success | 0.12 | test_secondary_storage.py
test_01_sys_vm_start | Success | 0.17 | test_secondary_storage.py
test_09_reboot_router | Success | 40.33 | test_routers.py
test_08_start_router | Success | 30.28 | test_routers.py
test_07_stop_router | Success | 10.14 | test_routers.py
test_06_router_advanced | Success | 0.05 | test_routers.py
test_05_router_basic | Success | 0.04 | test_routers.py
test_04_restart_network_wo_cleanup | Success | 5.73 | test_routers.py
test_03_restart_network_cleanup | Success | 60.51 | test_routers.py
test_02_router_internal_adv | Success | 1.11 |

[GitHub] cloudstack issue #1915: CLOUDSTACK-9746 system-vm: logrotate config causes c...

2017-02-20 Thread kiwiflyer

Github user kiwiflyer commented on the issue:

https://github.com/apache/cloudstack/pull/1915
  
We pulled this in and tested it alongside 
https://github.com/apache/cloudstack/pull/1954


![image](https://cloud.githubusercontent.com/assets/17278194/23148479/b8c73e42-f7ab-11e6-8ffc-b884f802b520.png)

We did remove the delay compress in our testing.




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

[GitHub] cloudstack issue #1954: CLOUDSTACK-9795: moved logrotate from cron.daily to ...

2017-02-20 Thread luhaijiao

Github user luhaijiao commented on the issue:

https://github.com/apache/cloudstack/pull/1954
  
This one is ready for merging.


---
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 #1882: CLOUDSTACK-8737: Removed the missed out-of-band VR r...

2017-02-20 Thread cloudmonger

Github user cloudmonger commented on the issue:

https://github.com/apache/cloudstack/pull/1882
  
### ACS CI BVT Run
 **Sumarry:**
 Build Number 366
 Hypervisor xenserver
 NetworkType Advanced
 Passed=104
 Failed=1
 Skipped=7

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


**Failed tests:**
* test_non_contigiousvlan.py

 * test_extendPhysicalNetworkVlan Failed


**Skipped tests:**
test_01_test_vm_volume_snapshot
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_11_ss_nfs_version_on_ssvm
test_nested_virtualization_vmware
test_3d_gpu_support
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_loadbalance.py
test_routers.py
test_reset_vm_on_reboot.py
test_deploy_vms_with_varied_deploymentplanners.py
test_network.py
test_router_dns.py
test_login.py
test_deploy_vm_iso.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_routers_network_ops.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 #1956: CLOUDSTACK-9796 - Fix NPE in VirtualMachineManagerIm...

2017-02-20 Thread GabrielBrascher

Github user GabrielBrascher commented on the issue:

https://github.com/apache/cloudstack/pull/1956
  
Thanks for the code that prevents NULL pointer exception.
Based on code revirew and that all checks have passed 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 #1926: CLOUDSTACK-9768: Time displayed for events in...

2017-02-20 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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 #1926: CLOUDSTACK-9768: Time displayed for events in UI is ...

2017-02-20 Thread karuturi

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1926
  
LGTM. merging


---
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 #1900: CLOUDSTACK-8862: Introduced new state attaching for ...

2017-02-20 Thread karuturi

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1900
  
@anshul1886  can you take a look at the travis and jenkins failures?
volume related tests failed on travis

> 
> 
+--+--+--+--+
> | test_04_deploy_s | Failure  | 15.836   | 
test_stopped_vm  |
> | tartvm_false_att |  |  |
  |
> | ach_volume   |  |  |
  |
> 
+--+--+--+--+
> 
+--+--+--+--+
> | test_06_deploy_s | Failure  | 10.782   | 
test_stopped_vm  |
> | tartvm_attach_de |  |  |
  |
> | tach |  |  |
  |
> 
+--+--+--+--+
> | test_08_deploy_a | Failure  | 21.020   | 
test_stopped_vm  |
> | ttached_volume   |  |  |
  |
> 
+--+--+--+--+


---
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 #1924: CLOUDSTACK-9766 : Executing deleteSnapshot api with ...

2017-02-20 Thread karuturi

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1924
  
merging


---
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 #1924: CLOUDSTACK-9766 : Executing deleteSnapshot ap...

2017-02-20 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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 #1878: CLOUDSTACK-9717: [VMware] RVRs have mismatching MAC ...

2017-02-20 Thread sureshanaparti

Github user sureshanaparti commented on the issue:

https://github.com/apache/cloudstack/pull/1878
  
@borisstoyanov Can you please run trillian tests for 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.
---

[GitHub] cloudstack pull request #1874: CLOUDSTACK-9711: Fixed error reporting while ...

2017-02-20 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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 #1878: CLOUDSTACK-9717: [VMware] RVRs have mismatching MAC ...

2017-02-20 Thread sureshanaparti

Github user sureshanaparti commented on the issue:

https://github.com/apache/cloudstack/pull/1878
  
@rafaelweingartner Updated the changes.


---
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 #1878: CLOUDSTACK-9717: [VMware] RVRs have mismatching MAC ...

2017-02-20 Thread sureshanaparti

Github user sureshanaparti commented on the issue:

https://github.com/apache/cloudstack/pull/1878
  
@rafaelweingartner  Sure. I'll move these lines to a method and push the 
changes.


---
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 #1953: CLOUDSTACK-9794: Unable to attach more than 14 devic...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1953
  
Trillian test result (tid-855)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 30017 seconds
Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1953-t855-kvm-centos7.zip
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermitten failure detected: /marvin/tests/smoke/test_snapshots.py
Test completed. 47 look ok, 2 have error(s)


Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_04_rvpc_privategw_static_routes | `Failure` | 325.73 | 
test_privategw_acl.py
test_02_list_snapshots_with_removed_data_store | `Error` | 0.04 | 
test_snapshots.py
test_01_vpc_site2site_vpn | Success | 165.60 | test_vpc_vpn.py
test_01_vpc_remote_access_vpn | Success | 66.17 | test_vpc_vpn.py
test_01_redundant_vpc_site2site_vpn | Success | 260.79 | test_vpc_vpn.py
test_02_VPC_default_routes | Success | 277.42 | test_vpc_router_nics.py
test_01_VPC_nics_after_destroy | Success | 565.35 | test_vpc_router_nics.py
test_05_rvpc_multi_tiers | Success | 517.19 | test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics | Success | 1418.42 | 
test_vpc_redundant.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
Success | 563.39 | test_vpc_redundant.py
test_02_redundant_VPC_default_routes | Success | 765.56 | 
test_vpc_redundant.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1313.50 | 
test_vpc_redundant.py
test_09_delete_detached_volume | Success | 156.82 | test_volumes.py
test_08_resize_volume | Success | 156.52 | test_volumes.py
test_07_resize_fail | Success | 161.54 | test_volumes.py
test_06_download_detached_volume | Success | 156.37 | test_volumes.py
test_05_detach_volume | Success | 155.90 | test_volumes.py
test_04_delete_attached_volume | Success | 151.64 | test_volumes.py
test_03_download_attached_volume | Success | 156.37 | test_volumes.py
test_02_attach_volume | Success | 129.32 | test_volumes.py
test_01_create_volume | Success | 711.37 | test_volumes.py
test_03_delete_vm_snapshots | Success | 275.15 | test_vm_snapshots.py
test_02_revert_vm_snapshots | Success | 95.72 | test_vm_snapshots.py
test_01_create_vm_snapshots | Success | 158.76 | test_vm_snapshots.py
test_deploy_vm_multiple | Success | 273.02 | test_vm_life_cycle.py
test_deploy_vm | Success | 0.03 | test_vm_life_cycle.py
test_advZoneVirtualRouter | Success | 0.03 | test_vm_life_cycle.py
test_10_attachAndDetach_iso | Success | 26.67 | test_vm_life_cycle.py
test_09_expunge_vm | Success | 125.17 | test_vm_life_cycle.py
test_08_migrate_vm | Success | 41.01 | test_vm_life_cycle.py
test_07_restore_vm | Success | 0.17 | test_vm_life_cycle.py
test_06_destroy_vm | Success | 125.86 | test_vm_life_cycle.py
test_03_reboot_vm | Success | 125.87 | test_vm_life_cycle.py
test_02_start_vm | Success | 10.17 | test_vm_life_cycle.py
test_01_stop_vm | Success | 40.33 | test_vm_life_cycle.py
test_CreateTemplateWithDuplicateName | Success | 40.46 | test_templates.py
test_08_list_system_templates | Success | 0.06 | test_templates.py
test_07_list_public_templates | Success | 0.04 | test_templates.py
test_05_template_permissions | Success | 0.06 | test_templates.py
test_04_extract_template | Success | 5.16 | test_templates.py
test_03_delete_template | Success | 5.24 | test_templates.py
test_02_edit_template | Success | 90.14 | test_templates.py
test_01_create_template | Success | 30.38 | test_templates.py
test_10_destroy_cpvm | Success | 191.67 | test_ssvm.py
test_09_destroy_ssvm | Success | 163.63 | test_ssvm.py
test_08_reboot_cpvm | Success | 131.62 | test_ssvm.py
test_07_reboot_ssvm | Success | 133.60 | test_ssvm.py
test_06_stop_cpvm | Success | 131.75 | test_ssvm.py
test_05_stop_ssvm | Success | 133.87 | test_ssvm.py
test_04_cpvm_internals | Success | 1.22 | test_ssvm.py
test_03_ssvm_internals | Success | 3.62 | test_ssvm.py
test_02_list_cpvm_vm | Success | 0.15 | test_ssvm.py
test_01_list_sec_storage_vm | Success | 0.13 | test_ssvm.py
test_01_snapshot_root_disk | Success | 11.11 | test_snapshots.py
test_04_change_offering_small | Success | 242.67 | test_service_offerings.py
test_03_delete_service_offering | Success | 0.04 | test_service_offerings.py
test_02_edit_service_offering | Success | 0.06 | test_service_offerings.py
test_01_create_service_offering | Success | 0.14 | test_service_offerings.py
test_02_sys_template_ready | Success | 0.13 | test_secondary_storage.py
test_01_sys_vm_start | Success | 0.19 | test_secondary_storage.py
test_09_reboot_router | Success | 35.35 | test_routers.py
test_08_start_router | Success | 30.33 |

[GitHub] cloudstack issue #1953: CLOUDSTACK-9794: Unable to attach more than 14 devic...

2017-02-20 Thread sureshanaparti

Github user sureshanaparti commented on the issue:

https://github.com/apache/cloudstack/pull/1953
  
@remibergsma The KVM support for max data volumes 32 was updated in the DB 
as part of CLOUDSTACK-8992 (PR #980). CloudStack supports till device Id 15, 
without this changes. Might be the limit 32 was tested manually in the VM.  As 
you pointed, in KVM, I see there is a problem with the device name after device 
id 25. As soon as the device name ends with suffix 'z' for device id 25, it 
should take the next suffix 'aa', 'ab',...so on. I think it is better to 
improve the code to generate a valid device name suffix with the given device 
id. As this is specific to KVM, I'll create a separate PR with these changes. 
Thanks.


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

[GitHub] cloudstack issue #1881: CLOUDSTACK-9721: Remove deprecated/unused global con...

2017-02-20 Thread cloudmonger

Github user cloudmonger commented on the issue:

https://github.com/apache/cloudstack/pull/1881
  
### ACS CI BVT Run
 **Sumarry:**
 Build Number 365
 Hypervisor xenserver
 NetworkType Advanced
 Passed=105
 Failed=0
 Skipped=7

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


**Failed tests:**

**Skipped tests:**
test_01_test_vm_volume_snapshot
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_11_ss_nfs_version_on_ssvm
test_nested_virtualization_vmware
test_3d_gpu_support
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_loadbalance.py
test_routers.py
test_reset_vm_on_reboot.py
test_deploy_vms_with_varied_deploymentplanners.py
test_network.py
test_router_dns.py
test_non_contigiousvlan.py
test_login.py
test_deploy_vm_iso.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_routers_network_ops.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: [QUESTION] Upgrade path to JDK8

2017-02-20 Thread Wei ZHOU

We tested 4.7.1+systemd patches as well, it also works fine.

-Wei

2017-02-20 22:34 GMT+01:00 Wei ZHOU :

> @Will and @Syed, I build the packages of 4.9.2+systemd patches on ubuntu
> 16.04 (openjdk 8).
> Then install the packages to management server and kvm hosts (all are
> ubuntu 16.04 with openjdk8).
> The systemvm template is 4.6 with openjdk7.
>
> cpvm and ssvm work fine.
>
> As there is no java process in VR, so I did not check, VR should not be
> impacted.
>
> -Wei
>
> 2017-02-20 22:16 GMT+01:00 Pierre-Luc Dion :
>
>> That's quite interesting Chiradeep!
>>
>> so I could do something like this I guest:
>>
>> mvn clean install
>>
>> and then this one to build the systemvm.iso:
>> mvn -Psystemvm -source 1.7 -target 1.7 install
>>
>>
>> I'll give it a try! but for now, I'm worried about existing VR, they must
>> continue to work while running on jdk7.  newer VPC would be ok to run with
>> jdk8.  but we need to make sure while upgrading the management-server we
>> are not in the obligation to upgrade VR's.
>>
>> For sure it is required for strongswan + JDK8 to ugprade the VR, but a
>>  existing VR should remain usable for port forwarding, vm creation and
>> such...
>>
>> I'll post my finding...
>>
>> Thanks !
>>
>>
>>
>> On Mon, Feb 20, 2017 at 3:59 PM, Chiradeep Vittal 
>> wrote:
>>
>> > You can build the system vm with  -source 1.7 -target 1.7
>> > Also unless you are using Java8 features (lambda) the classfiles
>> produced
>> > by javac 8 should work in a 1.7 JVM
>> >
>> > Sent from my iPhone
>> >
>> > > On Feb 20, 2017, at 11:51 AM, Will Stevens 
>> > wrote:
>> > >
>> > > yes, that is what I was expecting.  which is why I was asking about
>> Wei's
>> > > setup because he seems to have worked around that problem.  Or he has
>> a
>> > > custom SystemVM template running with both JDK7 and JDK8.
>> > >
>> > > *Will STEVENS*
>> > > Lead Developer
>> > >
>> > > 
>> > >
>> > >> On Mon, Feb 20, 2017 at 2:20 PM, Syed Ahmed 
>> > wrote:
>> > >>
>> > >> The problem is that systemvm.iso is built with java 8 whereas java on
>> > the
>> > >> VR is java 7
>> > >>> On Mon, Feb 20, 2017 at 13:20 Will Stevens 
>> > wrote:
>> > >>>
>> > >>> Did it work after resetting a VPC or when blowing away the SSVM or
>> > >> CPVM?  I
>> > >>> would not expect the SSVM or the CPVM to come up if the management
>> > server
>> > >>> was built with JDK8 and the system vm template is only using JDK7.
>> Can
>> > >> you
>> > >>> confirm?
>> > >>>
>> > >>> *Will STEVENS*
>> > >>> Lead Developer
>> > >>>
>> > >>> 
>> > >>>
>> >  On Mon, Feb 20, 2017 at 1:15 PM, Wei ZHOU 
>> > wrote:
>> > 
>> >  We've tested management server 4.7.1 with ubuntu 16.04/openjdk8 and
>> >  systemvm 4.6 with debian7/openjdk7.
>> >  The systemvms (ssvm, cpvm) work fine.
>> > 
>> >  I agree we need consider the openjdk upgrade in systemvm template.
>> > 
>> >  -Wei
>> > 
>> >  2017-02-20 18:15 GMT+01:00 Will Stevens :
>> > 
>> > > Regarding my question. Is it because of the version of Java that
>> the
>> > > systemvm.iso is built on?
>> > >
>> > > On Feb 20, 2017 11:58 AM, "Will Stevens" 
>> > >>> wrote:
>> > >
>> > >> A question that is hidden in here is:
>> > >> - Why does the JDK version on the management server have to match
>> > >> the
>> >  JDK
>> > >> version of the System VM?
>> > >>
>> > >> *Will STEVENS*
>> > >> Lead Developer
>> > >>
>> > >> 
>> > >>
>> > >> On Mon, Feb 20, 2017 at 11:50 AM, Pierre-Luc Dion <
>> > >>> pd...@cloudops.com>
>> > >> wrote:
>> > >>
>> > >>> Hi,
>> > >>>
>> > >>> In the context of deployment of CloudStack with VPCs,
>> > >>> What will happen to a cloud when upgrading to 4.10 that now use
>> > >>> jdk8?
>> > >>>
>> > >>> Does upgrading the management-server to 4.10 jdk8 and then keep
>> > >> the
>> >  old
>> > >>> VRs
>> > >>> run for a while that run on JDK7 will still work ?
>> > >>>
>> > >>> Because If we upgrade the management-server to jdk8, we need to
>> > >> keep
>> >  VR
>> > > to
>> > >>> work until they get upgraded but we can't force an upgrade of VR
>> > >>> just
>> > >>> because the management-server is now using JDK8.
>> > >>>
>> > >>> Thanks,
>> > >>>
>> > >>
>> > >>
>> > >
>> > 
>> > >>>
>> > >>
>> >
>>
>
>

Re: [QUESTION] Upgrade path to JDK8

2017-02-20 Thread Wei ZHOU

@Will and @Syed, I build the packages of 4.9.2+systemd patches on ubuntu
16.04 (openjdk 8).
Then install the packages to management server and kvm hosts (all are
ubuntu 16.04 with openjdk8).
The systemvm template is 4.6 with openjdk7.

cpvm and ssvm work fine.

As there is no java process in VR, so I did not check, VR should not be
impacted.

-Wei

2017-02-20 22:16 GMT+01:00 Pierre-Luc Dion :

> That's quite interesting Chiradeep!
>
> so I could do something like this I guest:
>
> mvn clean install
>
> and then this one to build the systemvm.iso:
> mvn -Psystemvm -source 1.7 -target 1.7 install
>
>
> I'll give it a try! but for now, I'm worried about existing VR, they must
> continue to work while running on jdk7.  newer VPC would be ok to run with
> jdk8.  but we need to make sure while upgrading the management-server we
> are not in the obligation to upgrade VR's.
>
> For sure it is required for strongswan + JDK8 to ugprade the VR, but a
>  existing VR should remain usable for port forwarding, vm creation and
> such...
>
> I'll post my finding...
>
> Thanks !
>
>
>
> On Mon, Feb 20, 2017 at 3:59 PM, Chiradeep Vittal 
> wrote:
>
> > You can build the system vm with  -source 1.7 -target 1.7
> > Also unless you are using Java8 features (lambda) the classfiles produced
> > by javac 8 should work in a 1.7 JVM
> >
> > Sent from my iPhone
> >
> > > On Feb 20, 2017, at 11:51 AM, Will Stevens 
> > wrote:
> > >
> > > yes, that is what I was expecting.  which is why I was asking about
> Wei's
> > > setup because he seems to have worked around that problem.  Or he has a
> > > custom SystemVM template running with both JDK7 and JDK8.
> > >
> > > *Will STEVENS*
> > > Lead Developer
> > >
> > > 
> > >
> > >> On Mon, Feb 20, 2017 at 2:20 PM, Syed Ahmed 
> > wrote:
> > >>
> > >> The problem is that systemvm.iso is built with java 8 whereas java on
> > the
> > >> VR is java 7
> > >>> On Mon, Feb 20, 2017 at 13:20 Will Stevens 
> > wrote:
> > >>>
> > >>> Did it work after resetting a VPC or when blowing away the SSVM or
> > >> CPVM?  I
> > >>> would not expect the SSVM or the CPVM to come up if the management
> > server
> > >>> was built with JDK8 and the system vm template is only using JDK7.
> Can
> > >> you
> > >>> confirm?
> > >>>
> > >>> *Will STEVENS*
> > >>> Lead Developer
> > >>>
> > >>> 
> > >>>
> >  On Mon, Feb 20, 2017 at 1:15 PM, Wei ZHOU 
> > wrote:
> > 
> >  We've tested management server 4.7.1 with ubuntu 16.04/openjdk8 and
> >  systemvm 4.6 with debian7/openjdk7.
> >  The systemvms (ssvm, cpvm) work fine.
> > 
> >  I agree we need consider the openjdk upgrade in systemvm template.
> > 
> >  -Wei
> > 
> >  2017-02-20 18:15 GMT+01:00 Will Stevens :
> > 
> > > Regarding my question. Is it because of the version of Java that
> the
> > > systemvm.iso is built on?
> > >
> > > On Feb 20, 2017 11:58 AM, "Will Stevens" 
> > >>> wrote:
> > >
> > >> A question that is hidden in here is:
> > >> - Why does the JDK version on the management server have to match
> > >> the
> >  JDK
> > >> version of the System VM?
> > >>
> > >> *Will STEVENS*
> > >> Lead Developer
> > >>
> > >> 
> > >>
> > >> On Mon, Feb 20, 2017 at 11:50 AM, Pierre-Luc Dion <
> > >>> pd...@cloudops.com>
> > >> wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> In the context of deployment of CloudStack with VPCs,
> > >>> What will happen to a cloud when upgrading to 4.10 that now use
> > >>> jdk8?
> > >>>
> > >>> Does upgrading the management-server to 4.10 jdk8 and then keep
> > >> the
> >  old
> > >>> VRs
> > >>> run for a while that run on JDK7 will still work ?
> > >>>
> > >>> Because If we upgrade the management-server to jdk8, we need to
> > >> keep
> >  VR
> > > to
> > >>> work until they get upgraded but we can't force an upgrade of VR
> > >>> just
> > >>> because the management-server is now using JDK8.
> > >>>
> > >>> Thanks,
> > >>>
> > >>
> > >>
> > >
> > 
> > >>>
> > >>
> >
>

Re: [QUESTION] Upgrade path to JDK8

2017-02-20 Thread Pierre-Luc Dion

That's quite interesting Chiradeep!

so I could do something like this I guest:

mvn clean install

and then this one to build the systemvm.iso:
mvn -Psystemvm -source 1.7 -target 1.7 install


I'll give it a try! but for now, I'm worried about existing VR, they must
continue to work while running on jdk7.  newer VPC would be ok to run with
jdk8.  but we need to make sure while upgrading the management-server we
are not in the obligation to upgrade VR's.

For sure it is required for strongswan + JDK8 to ugprade the VR, but a
 existing VR should remain usable for port forwarding, vm creation and
such...

I'll post my finding...

Thanks !



On Mon, Feb 20, 2017 at 3:59 PM, Chiradeep Vittal 
wrote:

> You can build the system vm with  -source 1.7 -target 1.7
> Also unless you are using Java8 features (lambda) the classfiles produced
> by javac 8 should work in a 1.7 JVM
>
> Sent from my iPhone
>
> > On Feb 20, 2017, at 11:51 AM, Will Stevens 
> wrote:
> >
> > yes, that is what I was expecting.  which is why I was asking about Wei's
> > setup because he seems to have worked around that problem.  Or he has a
> > custom SystemVM template running with both JDK7 and JDK8.
> >
> > *Will STEVENS*
> > Lead Developer
> >
> > 
> >
> >> On Mon, Feb 20, 2017 at 2:20 PM, Syed Ahmed 
> wrote:
> >>
> >> The problem is that systemvm.iso is built with java 8 whereas java on
> the
> >> VR is java 7
> >>> On Mon, Feb 20, 2017 at 13:20 Will Stevens 
> wrote:
> >>>
> >>> Did it work after resetting a VPC or when blowing away the SSVM or
> >> CPVM?  I
> >>> would not expect the SSVM or the CPVM to come up if the management
> server
> >>> was built with JDK8 and the system vm template is only using JDK7.  Can
> >> you
> >>> confirm?
> >>>
> >>> *Will STEVENS*
> >>> Lead Developer
> >>>
> >>> 
> >>>
>  On Mon, Feb 20, 2017 at 1:15 PM, Wei ZHOU 
> wrote:
> 
>  We've tested management server 4.7.1 with ubuntu 16.04/openjdk8 and
>  systemvm 4.6 with debian7/openjdk7.
>  The systemvms (ssvm, cpvm) work fine.
> 
>  I agree we need consider the openjdk upgrade in systemvm template.
> 
>  -Wei
> 
>  2017-02-20 18:15 GMT+01:00 Will Stevens :
> 
> > Regarding my question. Is it because of the version of Java that the
> > systemvm.iso is built on?
> >
> > On Feb 20, 2017 11:58 AM, "Will Stevens" 
> >>> wrote:
> >
> >> A question that is hidden in here is:
> >> - Why does the JDK version on the management server have to match
> >> the
>  JDK
> >> version of the System VM?
> >>
> >> *Will STEVENS*
> >> Lead Developer
> >>
> >> 
> >>
> >> On Mon, Feb 20, 2017 at 11:50 AM, Pierre-Luc Dion <
> >>> pd...@cloudops.com>
> >> wrote:
> >>
> >>> Hi,
> >>>
> >>> In the context of deployment of CloudStack with VPCs,
> >>> What will happen to a cloud when upgrading to 4.10 that now use
> >>> jdk8?
> >>>
> >>> Does upgrading the management-server to 4.10 jdk8 and then keep
> >> the
>  old
> >>> VRs
> >>> run for a while that run on JDK7 will still work ?
> >>>
> >>> Because If we upgrade the management-server to jdk8, we need to
> >> keep
>  VR
> > to
> >>> work until they get upgraded but we can't force an upgrade of VR
> >>> just
> >>> because the management-server is now using JDK8.
> >>>
> >>> Thanks,
> >>>
> >>
> >>
> >
> 
> >>>
> >>
>

[GitHub] cloudstack pull request #1956: CLOUDSTACK-9796 - Fix NPE in VirtualMachineMa...

2017-02-20 Thread nathanejohnson

GitHub user nathanejohnson opened a pull request:

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

CLOUDSTACK-9796 - Fix NPE in VirtualMachineManagerImpl.java

This checks the work variable for NULL in all cases where it is
used.  Fixes CLOUDSTACK-9796.

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

$ git pull https://github.com/myENA/cloudstack bug/49npe_vmimpl

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

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


commit 7f62924f582671ae264ddab779c30ef5180bcbb4
Author: Nathan Johnson 
Date:   2017-02-20T20:58:20Z

CLOUDSTACK-9796 - Fix NPE in VirtualMachineManagerImpl.java

This checks the work variable for NULL in all cases where it is
used.  Fixes CLOUDSTACK-9796.




---
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: [QUESTION] Upgrade path to JDK8

2017-02-20 Thread Chiradeep Vittal

You can build the system vm with  -source 1.7 -target 1.7 
Also unless you are using Java8 features (lambda) the classfiles produced by 
javac 8 should work in a 1.7 JVM

Sent from my iPhone

> On Feb 20, 2017, at 11:51 AM, Will Stevens  wrote:
> 
> yes, that is what I was expecting.  which is why I was asking about Wei's
> setup because he seems to have worked around that problem.  Or he has a
> custom SystemVM template running with both JDK7 and JDK8.
> 
> *Will STEVENS*
> Lead Developer
> 
> 
> 
>> On Mon, Feb 20, 2017 at 2:20 PM, Syed Ahmed  wrote:
>> 
>> The problem is that systemvm.iso is built with java 8 whereas java on the
>> VR is java 7
>>> On Mon, Feb 20, 2017 at 13:20 Will Stevens  wrote:
>>> 
>>> Did it work after resetting a VPC or when blowing away the SSVM or
>> CPVM?  I
>>> would not expect the SSVM or the CPVM to come up if the management server
>>> was built with JDK8 and the system vm template is only using JDK7.  Can
>> you
>>> confirm?
>>> 
>>> *Will STEVENS*
>>> Lead Developer
>>> 
>>> 
>>> 
 On Mon, Feb 20, 2017 at 1:15 PM, Wei ZHOU  wrote:
 
 We've tested management server 4.7.1 with ubuntu 16.04/openjdk8 and
 systemvm 4.6 with debian7/openjdk7.
 The systemvms (ssvm, cpvm) work fine.
 
 I agree we need consider the openjdk upgrade in systemvm template.
 
 -Wei
 
 2017-02-20 18:15 GMT+01:00 Will Stevens :
 
> Regarding my question. Is it because of the version of Java that the
> systemvm.iso is built on?
> 
> On Feb 20, 2017 11:58 AM, "Will Stevens" 
>>> wrote:
> 
>> A question that is hidden in here is:
>> - Why does the JDK version on the management server have to match
>> the
 JDK
>> version of the System VM?
>> 
>> *Will STEVENS*
>> Lead Developer
>> 
>> 
>> 
>> On Mon, Feb 20, 2017 at 11:50 AM, Pierre-Luc Dion <
>>> pd...@cloudops.com>
>> wrote:
>> 
>>> Hi,
>>> 
>>> In the context of deployment of CloudStack with VPCs,
>>> What will happen to a cloud when upgrading to 4.10 that now use
>>> jdk8?
>>> 
>>> Does upgrading the management-server to 4.10 jdk8 and then keep
>> the
 old
>>> VRs
>>> run for a while that run on JDK7 will still work ?
>>> 
>>> Because If we upgrade the management-server to jdk8, we need to
>> keep
 VR
> to
>>> work until they get upgraded but we can't force an upgrade of VR
>>> just
>>> because the management-server is now using JDK8.
>>> 
>>> Thanks,
>>> 
>> 
>> 
> 
 
>>> 
>>

[GitHub] cloudstack issue #1955: CLOUDSTACK-8239 Add VirtIO SCSI support for KVM host...

2017-02-20 Thread remibergsma

Github user remibergsma commented on the issue:

https://github.com/apache/cloudstack/pull/1955
  
Nice work @kiwiflyer @dmabry, thanks! Will give it a go soon.


---
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 #1773: CLOUDSTACK-9607: Preventing template deletion when t...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1773
  
@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has 
been kicked to run smoke tests


---
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 #1773: CLOUDSTACK-9607: Preventing template deletion when t...

2017-02-20 Thread borisstoyanov

Github user borisstoyanov commented on the issue:

https://github.com/apache/cloudstack/pull/1773
  
@blueorangutan 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 issue #1773: CLOUDSTACK-9607: Preventing template deletion when t...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1773
  
Packaging result: âcentos6 âcentos7 âdebian. JID-515


---
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: [QUESTION] Upgrade path to JDK8

2017-02-20 Thread Will Stevens

yes, that is what I was expecting.  which is why I was asking about Wei's
setup because he seems to have worked around that problem.  Or he has a
custom SystemVM template running with both JDK7 and JDK8.

*Will STEVENS*
Lead Developer



On Mon, Feb 20, 2017 at 2:20 PM, Syed Ahmed  wrote:

> The problem is that systemvm.iso is built with java 8 whereas java on the
> VR is java 7
> On Mon, Feb 20, 2017 at 13:20 Will Stevens  wrote:
>
> > Did it work after resetting a VPC or when blowing away the SSVM or
> CPVM?  I
> > would not expect the SSVM or the CPVM to come up if the management server
> > was built with JDK8 and the system vm template is only using JDK7.  Can
> you
> > confirm?
> >
> > *Will STEVENS*
> > Lead Developer
> >
> > 
> >
> > On Mon, Feb 20, 2017 at 1:15 PM, Wei ZHOU  wrote:
> >
> > > We've tested management server 4.7.1 with ubuntu 16.04/openjdk8 and
> > > systemvm 4.6 with debian7/openjdk7.
> > > The systemvms (ssvm, cpvm) work fine.
> > >
> > > I agree we need consider the openjdk upgrade in systemvm template.
> > >
> > > -Wei
> > >
> > > 2017-02-20 18:15 GMT+01:00 Will Stevens :
> > >
> > > > Regarding my question. Is it because of the version of Java that the
> > > > systemvm.iso is built on?
> > > >
> > > > On Feb 20, 2017 11:58 AM, "Will Stevens" 
> > wrote:
> > > >
> > > > > A question that is hidden in here is:
> > > > > - Why does the JDK version on the management server have to match
> the
> > > JDK
> > > > > version of the System VM?
> > > > >
> > > > > *Will STEVENS*
> > > > > Lead Developer
> > > > >
> > > > > 
> > > > >
> > > > > On Mon, Feb 20, 2017 at 11:50 AM, Pierre-Luc Dion <
> > pd...@cloudops.com>
> > > > > wrote:
> > > > >
> > > > >> Hi,
> > > > >>
> > > > >> In the context of deployment of CloudStack with VPCs,
> > > > >> What will happen to a cloud when upgrading to 4.10 that now use
> > jdk8?
> > > > >>
> > > > >> Does upgrading the management-server to 4.10 jdk8 and then keep
> the
> > > old
> > > > >> VRs
> > > > >> run for a while that run on JDK7 will still work ?
> > > > >>
> > > > >> Because If we upgrade the management-server to jdk8, we need to
> keep
> > > VR
> > > > to
> > > > >> work until they get upgraded but we can't force an upgrade of VR
> > just
> > > > >> because the management-server is now using JDK8.
> > > > >>
> > > > >> Thanks,
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>

[GitHub] cloudstack issue #1872: CLOUDSTACK-3223 Exception observed while creating CP...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1872
  
@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + vmware-60u2) has 
been kicked to run smoke tests


---
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 #1861: CLOUDSTACK-9698 [VMware] Make hardcorded wait timeou...

2017-02-20 Thread borisstoyanov

Github user borisstoyanov commented on the issue:

https://github.com/apache/cloudstack/pull/1861
  
@blueorangutan test centos7 vmware-60u2


---
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 #1872: CLOUDSTACK-3223 Exception observed while creating CP...

2017-02-20 Thread borisstoyanov

Github user borisstoyanov commented on the issue:

https://github.com/apache/cloudstack/pull/1872
  
@blueorangutan test centos7 vmware-60u2


---
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 #1841: CLOUDSTACK-9684 Invalid zone id error while listing ...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1841
  
@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + vmware-60u2) has 
been kicked to run smoke tests


---
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 #1872: CLOUDSTACK-3223 Exception observed while creating CP...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1872
  
@borisstoyanov unsupported parameters provided. Supported mgmt server os 
are: `centos6, centos7, ubuntu`. Supported hypervisors are: `kvm-centos6, 
kvm-centos7, kvm-ubuntu, xenserver-65sp1, xenserver-62sp1, vmware-60u2, 
vmware-55u3, vmware-51u1, vmware-50u1`


---
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 #1861: CLOUDSTACK-9698 [VMware] Make hardcorded wait timeou...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1861
  
@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + vmware-60u2) has 
been kicked to run smoke tests


---
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 #1841: CLOUDSTACK-9684 Invalid zone id error while listing ...

2017-02-20 Thread borisstoyanov

Github user borisstoyanov commented on the issue:

https://github.com/apache/cloudstack/pull/1841
  
@blueorangutan test centos7 vmware-60u2


---
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 #1773: CLOUDSTACK-9607: Preventing template deletion when t...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1773
  
@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep 
you posted as I make progress.


---
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 #1872: CLOUDSTACK-3223 Exception observed while creating CP...

2017-02-20 Thread borisstoyanov

Github user borisstoyanov commented on the issue:

https://github.com/apache/cloudstack/pull/1872
  
@blueorangutan test centos6 vmware-60u1


---
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 #1773: CLOUDSTACK-9607: Preventing template deletion when t...

2017-02-20 Thread borisstoyanov

Github user borisstoyanov commented on the issue:

https://github.com/apache/cloudstack/pull/1773
  
@blueorangutan package


---
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: [QUESTION] Upgrade path to JDK8

2017-02-20 Thread Syed Ahmed

The problem is that systemvm.iso is built with java 8 whereas java on the
VR is java 7
On Mon, Feb 20, 2017 at 13:20 Will Stevens  wrote:

> Did it work after resetting a VPC or when blowing away the SSVM or CPVM?  I
> would not expect the SSVM or the CPVM to come up if the management server
> was built with JDK8 and the system vm template is only using JDK7.  Can you
> confirm?
>
> *Will STEVENS*
> Lead Developer
>
> 
>
> On Mon, Feb 20, 2017 at 1:15 PM, Wei ZHOU  wrote:
>
> > We've tested management server 4.7.1 with ubuntu 16.04/openjdk8 and
> > systemvm 4.6 with debian7/openjdk7.
> > The systemvms (ssvm, cpvm) work fine.
> >
> > I agree we need consider the openjdk upgrade in systemvm template.
> >
> > -Wei
> >
> > 2017-02-20 18:15 GMT+01:00 Will Stevens :
> >
> > > Regarding my question. Is it because of the version of Java that the
> > > systemvm.iso is built on?
> > >
> > > On Feb 20, 2017 11:58 AM, "Will Stevens" 
> wrote:
> > >
> > > > A question that is hidden in here is:
> > > > - Why does the JDK version on the management server have to match the
> > JDK
> > > > version of the System VM?
> > > >
> > > > *Will STEVENS*
> > > > Lead Developer
> > > >
> > > > 
> > > >
> > > > On Mon, Feb 20, 2017 at 11:50 AM, Pierre-Luc Dion <
> pd...@cloudops.com>
> > > > wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> In the context of deployment of CloudStack with VPCs,
> > > >> What will happen to a cloud when upgrading to 4.10 that now use
> jdk8?
> > > >>
> > > >> Does upgrading the management-server to 4.10 jdk8 and then keep the
> > old
> > > >> VRs
> > > >> run for a while that run on JDK7 will still work ?
> > > >>
> > > >> Because If we upgrade the management-server to jdk8, we need to keep
> > VR
> > > to
> > > >> work until they get upgraded but we can't force an upgrade of VR
> just
> > > >> because the management-server is now using JDK8.
> > > >>
> > > >> Thanks,
> > > >>
> > > >
> > > >
> > >
> >
>

Re: [QUESTION] Upgrade path to JDK8

2017-02-20 Thread Will Stevens

Did it work after resetting a VPC or when blowing away the SSVM or CPVM?  I
would not expect the SSVM or the CPVM to come up if the management server
was built with JDK8 and the system vm template is only using JDK7.  Can you
confirm?

*Will STEVENS*
Lead Developer



On Mon, Feb 20, 2017 at 1:15 PM, Wei ZHOU  wrote:

> We've tested management server 4.7.1 with ubuntu 16.04/openjdk8 and
> systemvm 4.6 with debian7/openjdk7.
> The systemvms (ssvm, cpvm) work fine.
>
> I agree we need consider the openjdk upgrade in systemvm template.
>
> -Wei
>
> 2017-02-20 18:15 GMT+01:00 Will Stevens :
>
> > Regarding my question. Is it because of the version of Java that the
> > systemvm.iso is built on?
> >
> > On Feb 20, 2017 11:58 AM, "Will Stevens"  wrote:
> >
> > > A question that is hidden in here is:
> > > - Why does the JDK version on the management server have to match the
> JDK
> > > version of the System VM?
> > >
> > > *Will STEVENS*
> > > Lead Developer
> > >
> > > 
> > >
> > > On Mon, Feb 20, 2017 at 11:50 AM, Pierre-Luc Dion 
> > > wrote:
> > >
> > >> Hi,
> > >>
> > >> In the context of deployment of CloudStack with VPCs,
> > >> What will happen to a cloud when upgrading to 4.10 that now use jdk8?
> > >>
> > >> Does upgrading the management-server to 4.10 jdk8 and then keep the
> old
> > >> VRs
> > >> run for a while that run on JDK7 will still work ?
> > >>
> > >> Because If we upgrade the management-server to jdk8, we need to keep
> VR
> > to
> > >> work until they get upgraded but we can't force an upgrade of VR just
> > >> because the management-server is now using JDK8.
> > >>
> > >> Thanks,
> > >>
> > >
> > >
> >
>

Re: [QUESTION] Upgrade path to JDK8

2017-02-20 Thread Wei ZHOU

We've tested management server 4.7.1 with ubuntu 16.04/openjdk8 and
systemvm 4.6 with debian7/openjdk7.
The systemvms (ssvm, cpvm) work fine.

I agree we need consider the openjdk upgrade in systemvm template.

-Wei

2017-02-20 18:15 GMT+01:00 Will Stevens :

> Regarding my question. Is it because of the version of Java that the
> systemvm.iso is built on?
>
> On Feb 20, 2017 11:58 AM, "Will Stevens"  wrote:
>
> > A question that is hidden in here is:
> > - Why does the JDK version on the management server have to match the JDK
> > version of the System VM?
> >
> > *Will STEVENS*
> > Lead Developer
> >
> > 
> >
> > On Mon, Feb 20, 2017 at 11:50 AM, Pierre-Luc Dion 
> > wrote:
> >
> >> Hi,
> >>
> >> In the context of deployment of CloudStack with VPCs,
> >> What will happen to a cloud when upgrading to 4.10 that now use jdk8?
> >>
> >> Does upgrading the management-server to 4.10 jdk8 and then keep the old
> >> VRs
> >> run for a while that run on JDK7 will still work ?
> >>
> >> Because If we upgrade the management-server to jdk8, we need to keep VR
> to
> >> work until they get upgraded but we can't force an upgrade of VR just
> >> because the management-server is now using JDK8.
> >>
> >> Thanks,
> >>
> >
> >
>

[GitHub] cloudstack issue #1915: CLOUDSTACK-9746 system-vm: logrotate config causes c...

2017-02-20 Thread ustcweizhou

Github user ustcweizhou commented on the issue:

https://github.com/apache/cloudstack/pull/1915
  
@serbaut maxsize is fine for me.
Could you please remove delaycompress, and increase rotate in 
systemvm/patches/debian/config/etc/logrotate.d/cloud (eg from 4 to 10) ?
LTGM after that.


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

[GitHub] cloudstack issue #1954: CLOUDSTACK-9795: moved logrotate from cron.daily to ...

2017-02-20 Thread ustcweizhou

Github user ustcweizhou commented on the issue:

https://github.com/apache/cloudstack/pull/1954
  
quite simple and useful change. LGTM


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

Re: [QUESTION] Upgrade path to JDK8

2017-02-20 Thread Will Stevens

Regarding my question. Is it because of the version of Java that the
systemvm.iso is built on?

On Feb 20, 2017 11:58 AM, "Will Stevens"  wrote:

> A question that is hidden in here is:
> - Why does the JDK version on the management server have to match the JDK
> version of the System VM?
>
> *Will STEVENS*
> Lead Developer
>
> 
>
> On Mon, Feb 20, 2017 at 11:50 AM, Pierre-Luc Dion 
> wrote:
>
>> Hi,
>>
>> In the context of deployment of CloudStack with VPCs,
>> What will happen to a cloud when upgrading to 4.10 that now use jdk8?
>>
>> Does upgrading the management-server to 4.10 jdk8 and then keep the old
>> VRs
>> run for a while that run on JDK7 will still work ?
>>
>> Because If we upgrade the management-server to jdk8, we need to keep VR to
>> work until they get upgraded but we can't force an upgrade of VR just
>> because the management-server is now using JDK8.
>>
>> Thanks,
>>
>
>

Re: [QUESTION] Upgrade path to JDK8

2017-02-20 Thread Ron Wheeler

Are any Java enhancements being added to common libraries that would 
force the Client side to have to run Java 8?
Would running Java 7 cause any library to need to be available in 2 
versions?


Ron

On 20/02/2017 11:58 AM, Will Stevens wrote:

A question that is hidden in here is:
- Why does the JDK version on the management server have to match the JDK
version of the System VM?

*Will STEVENS*
Lead Developer



On Mon, Feb 20, 2017 at 11:50 AM, Pierre-Luc Dion 
wrote:


Hi,

In the context of deployment of CloudStack with VPCs,
What will happen to a cloud when upgrading to 4.10 that now use jdk8?

Does upgrading the management-server to 4.10 jdk8 and then keep the old VRs
run for a while that run on JDK7 will still work ?

Because If we upgrade the management-server to jdk8, we need to keep VR to
work until they get upgraded but we can't force an upgrade of VR just
because the management-server is now using JDK8.

Thanks,




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

[GitHub] cloudstack issue #1955: CLOUDSTACK-8239 Add VirtIO SCSI support for KVM host...

2017-02-20 Thread kiwiflyer

Github user kiwiflyer commented on the issue:

https://github.com/apache/cloudstack/pull/1955
  
@remibergsma @ustcweizhou This might be of interest to you guys as well.



---
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: [QUESTION] Upgrade path to JDK8

2017-02-20 Thread Will Stevens

A question that is hidden in here is:
- Why does the JDK version on the management server have to match the JDK
version of the System VM?

*Will STEVENS*
Lead Developer



On Mon, Feb 20, 2017 at 11:50 AM, Pierre-Luc Dion 
wrote:

> Hi,
>
> In the context of deployment of CloudStack with VPCs,
> What will happen to a cloud when upgrading to 4.10 that now use jdk8?
>
> Does upgrading the management-server to 4.10 jdk8 and then keep the old VRs
> run for a while that run on JDK7 will still work ?
>
> Because If we upgrade the management-server to jdk8, we need to keep VR to
> work until they get upgraded but we can't force an upgrade of VR just
> because the management-server is now using JDK8.
>
> Thanks,
>

[QUESTION] Upgrade path to JDK8

2017-02-20 Thread Pierre-Luc Dion

Hi,

In the context of deployment of CloudStack with VPCs,
What will happen to a cloud when upgrading to 4.10 that now use jdk8?

Does upgrading the management-server to 4.10 jdk8 and then keep the old VRs
run for a while that run on JDK7 will still work ?

Because If we upgrade the management-server to jdk8, we need to keep VR to
work until they get upgraded but we can't force an upgrade of VR just
because the management-server is now using JDK8.

Thanks,

[GitHub] cloudstack issue #1915: CLOUDSTACK-9746 system-vm: logrotate config causes c...

2017-02-20 Thread serbaut

Github user serbaut commented on the issue:

https://github.com/apache/cloudstack/pull/1915
  
@dmabry yes we are using redundant VPC routers. 

Using `size` instead of `maxsize` would delay the rotation of logs until 
they reach `size`. 10 logfiles with size 10MB could consume 200MB due to 
deplaycompress. Using `maxsize` would rotate the slowly growing logfiles daily 
and avoid this issue.


---
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 #1847: CLOUDSTACK-9691: Fixed unhandeled excetion in list s...

2017-02-20 Thread serg38

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1847
  
@nvazquez @rhtyd @anshul1886 We might need to tweak the test_data.py to add 
additional nfs mount e.g. nfs1 and use it in this test.  E.g adding 
 "nfs1": {
"url": "nfs://nfs/export/automation/1/testprimary1",
"name": "Primary XEN1"
},
Blueorangutain environment will need to be adjusted as well. Otherwise the 
test fails with 
CloudstackAPIException: Execute cmd: createstoragepool failed, due to: 
errorCode: 530, errorText:Failed to add data store: Storage pool 
NFS://10.2.0.16/acs/primary/pr1847-t854-kvm-centos7/marvin_pri1 already in use 
by another pod (id=1)\n']



---
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 #1955: CLOUDSTACK-8239 Add VirtIO SCSI support for K...

2017-02-20 Thread nathanejohnson

GitHub user nathanejohnson opened a pull request:

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

CLOUDSTACK-8239 Add VirtIO SCSI support for KVM hosts

This is an initial implementation that we have working in the lab.


![devmanagerscreenshot](https://cloud.githubusercontent.com/assets/1360240/23133419/981f89ce-f756-11e6-8d17-9ddae264fca8.png)

![spanned_sceenshot](https://cloud.githubusercontent.com/assets/1360240/23133418/981e55cc-f756-11e6-9fd7-f7757c82438c.png)



[win_virtio_scsi.xml.zip](https://github.com/apache/cloudstack/files/788014/win_virtio_scsi.xml.zip)

@wido @syed Would love to get some feedback on this approach.

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

$ git pull https://github.com/myENA/cloudstack virtio-scsi

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

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


commit d6d1cb20cd6f9984217a09c103610ffb2d4e6cf4
Author: Simon Weller 
Date:   2017-02-07T06:13:12Z

Added support for ViRTIO-SCSI based on template name.

commit 658a5e1b1ade2f936061695dd89ed8828751a3c2
Author: Nathan Johnson 
Date:   2017-02-08T17:02:13Z

CLOUDSTACK-8239 - Adding support for virtio-scsi on KVM hosts

This adds support for virtio-scsi on KVM hosts, but currently
only for guests that are associated with a new os_type of
'Other PV Virtio-SCSI (64-bit)'.  This is to prevent device
name changes on existing templates / VMs.




---
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 #1773: CLOUDSTACK-9607: Preventing template deletion when t...

2017-02-20 Thread serg38

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1773
  
@ustcweizhou @priyankparihar @borisstoyanov The default behavior was always 
equivalent of force=true. We seem to agree that the UI behavior should remain 
forced=true but with extra warning. We can either change default  confirmation 
"Please confirm that you want to delete this template." e.g. to "Please confirm 
that you want to delete this template.  Features that depends on the template 
presence might no longer work". But I think the better option will be to have 
response tag in listTemplate call to indicate if active VMs exists or not. Then 
warning can be given only to such templates.
As for API side we might still change default behavior but we need to 
explicitly document it in Release Notes so users can get prepared and change 
instances of deleteTemplate execution to use forced=true or not as needed.



---
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 #1847: CLOUDSTACK-9691: Fixed unhandeled excetion in list s...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1847
  
Trillian test result (tid-854)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 26568 seconds
Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1847-t854-kvm-centos7.zip
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermitten failure detected: /marvin/tests/smoke/test_snapshots.py
Test completed. 46 look ok, 2 have error(s)


Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_04_rvpc_privategw_static_routes | `Failure` | 315.29 | 
test_privategw_acl.py
test_02_list_snapshots_with_removed_data_store | `Error` | 0.04 | 
test_snapshots.py
test_01_vpc_site2site_vpn | Success | 140.99 | test_vpc_vpn.py
test_01_vpc_remote_access_vpn | Success | 66.12 | test_vpc_vpn.py
test_01_redundant_vpc_site2site_vpn | Success | 220.68 | test_vpc_vpn.py
test_02_VPC_default_routes | Success | 284.23 | test_vpc_router_nics.py
test_01_VPC_nics_after_destroy | Success | 513.11 | test_vpc_router_nics.py
test_05_rvpc_multi_tiers | Success | 503.72 | test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics | Success | 1404.04 | 
test_vpc_redundant.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
Success | 538.71 | test_vpc_redundant.py
test_02_redundant_VPC_default_routes | Success | 741.04 | 
test_vpc_redundant.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1286.74 | 
test_vpc_redundant.py
test_09_delete_detached_volume | Success | 151.44 | test_volumes.py
test_08_resize_volume | Success | 156.61 | test_volumes.py
test_07_resize_fail | Success | 156.51 | test_volumes.py
test_06_download_detached_volume | Success | 157.60 | test_volumes.py
test_05_detach_volume | Success | 151.18 | test_volumes.py
test_04_delete_attached_volume | Success | 151.37 | test_volumes.py
test_03_download_attached_volume | Success | 156.77 | test_volumes.py
test_02_attach_volume | Success | 94.64 | test_volumes.py
test_01_create_volume | Success | 621.09 | test_volumes.py
test_deploy_vm_multiple | Success | 252.67 | test_vm_life_cycle.py
test_deploy_vm | Success | 0.03 | test_vm_life_cycle.py
test_advZoneVirtualRouter | Success | 0.03 | test_vm_life_cycle.py
test_10_attachAndDetach_iso | Success | 26.80 | test_vm_life_cycle.py
test_09_expunge_vm | Success | 125.25 | test_vm_life_cycle.py
test_08_migrate_vm | Success | 40.93 | test_vm_life_cycle.py
test_07_restore_vm | Success | 0.13 | test_vm_life_cycle.py
test_06_destroy_vm | Success | 130.86 | test_vm_life_cycle.py
test_03_reboot_vm | Success | 126.01 | test_vm_life_cycle.py
test_02_start_vm | Success | 10.18 | test_vm_life_cycle.py
test_01_stop_vm | Success | 35.33 | test_vm_life_cycle.py
test_CreateTemplateWithDuplicateName | Success | 75.64 | test_templates.py
test_08_list_system_templates | Success | 0.03 | test_templates.py
test_07_list_public_templates | Success | 0.04 | test_templates.py
test_05_template_permissions | Success | 0.06 | test_templates.py
test_04_extract_template | Success | 5.16 | test_templates.py
test_03_delete_template | Success | 5.13 | test_templates.py
test_02_edit_template | Success | 90.18 | test_templates.py
test_01_create_template | Success | 25.33 | test_templates.py
test_10_destroy_cpvm | Success | 161.44 | test_ssvm.py
test_09_destroy_ssvm | Success | 163.81 | test_ssvm.py
test_08_reboot_cpvm | Success | 101.37 | test_ssvm.py
test_07_reboot_ssvm | Success | 133.56 | test_ssvm.py
test_06_stop_cpvm | Success | 131.60 | test_ssvm.py
test_05_stop_ssvm | Success | 133.67 | test_ssvm.py
test_04_cpvm_internals | Success | 1.02 | test_ssvm.py
test_03_ssvm_internals | Success | 3.29 | test_ssvm.py
test_02_list_cpvm_vm | Success | 0.15 | test_ssvm.py
test_01_list_sec_storage_vm | Success | 0.13 | test_ssvm.py
test_01_snapshot_root_disk | Success | 11.10 | test_snapshots.py
test_04_change_offering_small | Success | 210.81 | test_service_offerings.py
test_03_delete_service_offering | Success | 0.04 | test_service_offerings.py
test_02_edit_service_offering | Success | 0.05 | test_service_offerings.py
test_01_create_service_offering | Success | 0.11 | test_service_offerings.py
test_02_sys_template_ready | Success | 0.13 | test_secondary_storage.py
test_01_sys_vm_start | Success | 0.18 | test_secondary_storage.py
test_09_reboot_router | Success | 40.33 | test_routers.py
test_08_start_router | Success | 30.28 | test_routers.py
test_07_stop_router | Success | 10.16 | test_routers.py
test_06_router_advanced | Success | 0.06 | test_routers.py
test_05_router_basic | Success | 0.04 | test_routers.py

[GitHub] cloudstack issue #1954: CLOUDSTACK-9795: moved logrotate from cron.daily to ...

2017-02-20 Thread kiwiflyer

Github user kiwiflyer commented on the issue:

https://github.com/apache/cloudstack/pull/1954
  
Tested in our QA environment. We cycled 2800 VMs through a VPC VR pair 
successfully over the weekend. 

The logs are rotating correctly as per the following screenshot:


![image](https://cloud.githubusercontent.com/assets/17278194/23131539/fb06a772-f74f-11e6-9e86-afb6d84fe6a9.png)

LGTM based on testing.


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

[GitHub] cloudstack issue #1915: CLOUDSTACK-9746 system-vm: logrotate config causes c...

2017-02-20 Thread dmabry

Github user dmabry commented on the issue:

https://github.com/apache/cloudstack/pull/1915
  
@ustcweizhou Thanks for taking the time to test as well.  I confirm in our 
testing over the weekend that we were able to consistently 
create/destroy/expunge VMs every 2 minutes without issue.  Before the PR 
https://github.com/apache/cloudstack/pull/1954 and this PR, we were having the 
VPC VR fall over ~8 hours into the test.

In summary, this PR with the one I submitted this morning solved our issues.

Thanks again for the help.


---
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 #1915: CLOUDSTACK-9746 system-vm: logrotate config causes c...

2017-02-20 Thread dmabry

Github user dmabry commented on the issue:

https://github.com/apache/cloudstack/pull/1915
  
I have submitted a PR against master that fixes cloud-early-config.
https://github.com/apache/cloudstack/pull/1954



---
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 #1954: CLOUDSTACK-9795: moved logrotate from cron.daily to ...

2017-02-20 Thread swill

Github user swill commented on the issue:

https://github.com/apache/cloudstack/pull/1954
  
LGTM.  This change makes the VPC router behave the same way as the Isolated 
Guest Network router.  eg: 
https://github.com/myENA/cloudstack/blob/450deed8472c06c4fec88e045bef28091502c638/systemvm/patches/debian/config/etc/init.d/cloud-early-config#L959


---
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 #1954: CLOUDSTACK-9795: moved logrotate from cron.da...

2017-02-20 Thread dmabry

GitHub user dmabry opened a pull request:

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

CLOUDSTACK-9795: moved logrotate from cron.daily to cron.hourly for 
vpcrouter

 in cloud-early-config

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

$ git pull https://github.com/myENA/cloudstack bug/vpc-vr-logrotate

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

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


commit 450deed8472c06c4fec88e045bef28091502c638
Author: David Mabry 
Date:   2017-02-20T15:06:46Z

moved logrotate from cron.daily to cron.hourly for vpcrouter in 
cloud-early-config




---
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 #1872: CLOUDSTACK-3223 Exception observed while creating CP...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1872
  
Packaging result: âcentos6 âcentos7 âdebian. JID-514


---
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 #1861: CLOUDSTACK-9698 [VMware] Make hardcorded wait timeou...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1861
  
Packaging result: âcentos6 âcentos7 âdebian. JID-513


---
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 #1841: CLOUDSTACK-9684 Invalid zone id error while listing ...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1841
  
Packaging result: âcentos6 âcentos7 âdebian. JID-512


---
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 #1875: CLOUDSTACK-8608: [VMware] System VMs failed to start...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1875
  
Packaging result: âcentos6 âcentos7 âdebian. JID-511


---
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 #1880: CLOUDSTACK-9720: [VMware] template_spool_ref table i...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1880
  
Packaging result: âcentos6 âcentos7 âdebian. JID-509


---
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 #1891: CLOUDSTACK-9730: [VMware] Unable to add a host with ...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1891
  
Packaging result: âcentos6 âcentos7 âdebian. JID-510


---
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 #1879: CLOUDSTACK-9719: [VMware] VR loses DHCP settings and...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1879
  
Packaging result: âcentos6 âcentos7 âdebian. JID-508


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

[PROPOSAL] add native vm-cluster orchestration service (was: [PROPOSAL] add native container orchestration service)

2017-02-20 Thread Daan Hoogland

So, being very late in the discussion but havingread the whole thread before 
editting the title of this thread,

Can we agree that we want a generic vm-cluster service and leave the container 
bits to containers? Kishan can you share your design? Shapeblue wants to rebase 
their k8 service on top of this and I would like yours and Murali's work to not 
conflict.

daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, Utrecht Utrecht 3531 VENetherlands
@shapeblue
  
 


-Original Message-
From: Paul Angus [mailto:paul.an...@shapeblue.com] 
Sent: dinsdag 7 februari 2017 08:14
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service

Will is 100% correct.  As I mentioned the Title is misleading.  However, Murali 
did clarify in his explanation; this is really about vm cluster orchestration.




From: Will Stevens 
Sent: 6 Feb 2017 22:54
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service

My understanding is that what Paul is talking about is what is already built 
and IS what the thread is talking about.

*Will STEVENS*
Lead Developer



On Mon, Feb 6, 2017 at 2:29 PM, Rajesh Ramchandani < 
rajesh.ramchand...@accelerite.com> wrote:

> Hi Paul - I think this is different from what the thread was about. 
> The conversation was specifically about adding support for container 
> orchestrators. You are talking about provisioning a group of VMs. 
> Although, this is something I think several Cloudstack users have 
> requested before and we should propose a solution to this.
>
> Raj
>
> 
> From: Paul Angus 
> Sent: Monday, February 6, 2017 11:16:41 AM
> To: dev@cloudstack.apache.org
> Subject: RE: [PROPOSAL] add native container orchestration service
>
> #WhatHeSaid
>
> The title is misleading.  The proposal is purely to add the notion of 
> Clusters of VMs to CloudStack.  These may be for databases, containers 
> or anything else that needs 'clusters' of compute. Self-healing and 
> autoscaling are logical next steps to be added.
>
> Those guys at ShapeBlue have open-sourced their whole k8s container 
> service piece.  If/when the 'cluster' part of that work is added into 
> CloudStack, the k8s specific pieces can be used by anyone who wants 
> to, alternatively they could be used for reference in order to create 
> another types of cluster.  (or ignored completely).
>
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
>
>
>
>
> -Original Message-
> From: Will Stevens [mailto:williamstev...@gmail.com]
> Sent: 31 January 2017 13:26
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native container orchestration service
>
> s/cloud-init/cloud-config/
>
> On Jan 31, 2017 7:24 AM, "Will Stevens"  wrote:
>
> > I think that is covered in this proposal. There is nothing k8s
> > specific in this integration (from what I understand), all the k8s
> > details are passed in via the cloud-init configuration after the cluster
> has been provisioned.
> >
> > On Jan 31, 2017 3:06 AM, "Lianghwa Jou" 
> > wrote:
> >
> >
> > There are many container orchestrators. Those container orchestrators
> > are happy to run on any VMs or bare metal machines. K8s is just one of
> > them and there will be more in the future. It may not be a good idea
> > to make CloudStack to be k8s aware. IMO, the relationship between k8s
> > and cloudstack should be similar to application and os. It probably
> > not a good idea to make your OS to be aware of any specific
> > applications so IMHO I don’t think k8s should be native to CloudStack.
> > It makes more sense to provide some generic services that many
> > applications can take advantages of. Some generic resource grouping
> > service makes sense so a group of VMs, baremetal machines or network
> > can be treated as a single entity. Some life cycle management will be
> > necessary for these entities too. We can deploy k8s, swarm, dcos or
> > even non-container specific services on top of CloudStack. The k8s is
> > changing fast. One single tenant installation may need more than one
> > VM group and may actually requires more (k8s federation). It will be a
> > struggle to be in sync if we try to bring k8s specific knowledge into
> cloudstack.
> >
> > Regards,
> >
> >
> > --
> > Lianghwa Jou
> > VP Engineering, Accelerite
> > email: lianghwa@accelerite.com
> >
> >
> >
> >
> >
> > On 1/29/17, 11:54 PM, "Murali Reddy"  wrote:
> >
> >
> > I agree with some good views Will has shared and I also agree to
> > the concerns raised by Wido and Eric. IMO we need balance of staying
> > relevant/add new features vs stability of CloudStack and take
> > corrective

[GitHub] cloudstack issue #1872: CLOUDSTACK-3223 Exception observed while creating CP...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1872
  
@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep 
you posted as I make progress.


---
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 #1872: CLOUDSTACK-3223 Exception observed while creating CP...

2017-02-20 Thread borisstoyanov

Github user borisstoyanov commented on the issue:

https://github.com/apache/cloudstack/pull/1872
  
@blueorangutan package


---
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 #1953: CLOUDSTACK-9794: Unable to attach more than 14 devic...

2017-02-20 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1953
  
@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has 
been kicked to run smoke tests


---
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 #1953: CLOUDSTACK-9794: Unable to attach more than 14 devic...

2017-02-20 Thread borisstoyanov

Github user borisstoyanov commented on the issue:

https://github.com/apache/cloudstack/pull/1953
  
@blueorangutan 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.
---

1 2 >

1 - 100 of 146 matches

Mail list logo