[jira] [Commented] (CLOUDSTACK-9620) Improvements for Managed Storage

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317934#comment-16317934
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9620:


blueorangutan commented on issue #2298: CLOUDSTACK-9620: Enhancements for 
managed storage
URL: https://github.com/apache/cloudstack/pull/2298#issuecomment-356205510
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1628


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improvements for Managed Storage
> 
>
> Key: CLOUDSTACK-9620
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9620
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Management Server, VMware, XenServer
>Affects Versions: 4.11.0.0
> Environment: KVM, vSphere, and XenServer
>Reporter: Mike Tutkowski
>Assignee: Mike Tutkowski
> Fix For: 4.11.0.0
>
>
> Allowed zone-wide primary storage based on a custom plug-in to be added via 
> the GUI in a KVM-only environment (previously this only worked for XenServer 
> and VMware)
> Added support for root disks on managed storage with KVM
> Added support for volume snapshots with managed storage on KVM
> Enabled creating a template directly from a volume (i.e. without having to go 
> through a volume snapshot) on KVM with managed storage
> Only allowed the resizing of a volume for managed storage on KVM if the 
> volume in question is either not attached to a VM or is attached to a VM in 
> the Stopped state
> Included support for Reinstall VM on KVM with managed storage
> Enabled offline migration on KVM from non-managed storage to managed storage 
> and vice versa
> Included support for online storage migration on KVM with managed storage 
> (NFS and Ceph to managed storage)
> Added support to download (extract) a managed-storage volume to a QCOW2 file
> When uploading a file from outside of CloudStack to CloudStack, set the min 
> and max IOPS, if applicable.
> Included support for the KVM auto-convergence feature
> The compression flag was actually added in version 1.0.3 (103) as opposed 
> to version 1.3.0 (1003000) (changed this to reflect the correct version)
> On KVM when using iSCSI-based managed storage, if the user shuts a VM down 
> from the guest OS (as opposed to doing so from CloudStack), we need to pass 
> to the KVM agent a list of applicable iSCSI volumes that need to be 
> disconnected.
> Added a new Global Setting: kvm.storage.live.migration.wait
> For XenServer, added a check to enforce that only volumes from zone-wide 
> managed storage can be storage motioned from a host in one cluster to a host 
> in another cluster (cannot do so at the time being with volumes from 
> cluster-scoped managed storage)
> Don’t allow Storage XenMotion on a VM that has any managed-storage volume 
> with one or more snapshots.
> Enabled for managed storage with VMware: Template caching, create snapshot, 
> delete snapshot, create volume from snapshot, and create template from 
> snapshot
> Added an SIOC API plug-in to support VMware SIOC
> When starting a VM that uses managed storage in a cluster other than the one 
> it last was running in, we need to remove the reference to the iSCSI volume 
> from the original cluster.
> Added the ability to revert a volume to a snapshot
> Enabled cluster-scoped managed storage
> Added support for VMware dynamic discovery



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317930#comment-16317930
 ] 

ASF GitHub Bot commented on CLOUDSTACK-4757:


rhtyd commented on issue #2146: CLOUDSTACK-4757: Support OVA files with 
multiple disks for templates
URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-356205253
 
 
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Support OVA files with multiple disks for templates
> ---
>
> Key: CLOUDSTACK-4757
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4757
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Storage Controller
>Reporter: Likitha Shetty
>Assignee: Nicolas Vazquez
>Priority: Minor
> Fix For: Future
>
>
> CloudStack volumes and templates are one single virtual disk in case of 
> XenServer/XCP and KVM hypervisors since the files used for templates and 
> volumes are virtual disks (VHD, QCOW2). However, VMware volumes and templates 
> are in OVA format, which are archives that can contain a complete VM 
> including multiple VMDKs and other files such as ISOs. And currently, 
> Cloudstack only supports Template creation based on OVA files containing a 
> single disk. If a user creates a template from a OVA file containing more 
> than 1 disk and launches an instance using this template, only the first disk 
> is attached to the new instance and other disks are ignored.
> Similarly with uploaded volumes, attaching an uploaded volume that contains 
> multiple disks to a VM will result in only one VMDK to being attached to the 
> VM.
> This behavior needs to be improved in VMWare to support OVA files with 
> multiple disks for both uploaded volumes and templates. i.e. If a user 
> creates a template from a OVA file containing more than 1 disk and launches 
> an instance using this template, the first disk should be attached to the new 
> instance as the ROOT disk and volumes should be created based on other VMDK 
> disks in the OVA file and should be attached to the instance.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317931#comment-16317931
 ] 

ASF GitHub Bot commented on CLOUDSTACK-4757:


blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with 
multiple disks for templates
URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-356205310
 
 
   @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted 
as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Support OVA files with multiple disks for templates
> ---
>
> Key: CLOUDSTACK-4757
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4757
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Storage Controller
>Reporter: Likitha Shetty
>Assignee: Nicolas Vazquez
>Priority: Minor
> Fix For: Future
>
>
> CloudStack volumes and templates are one single virtual disk in case of 
> XenServer/XCP and KVM hypervisors since the files used for templates and 
> volumes are virtual disks (VHD, QCOW2). However, VMware volumes and templates 
> are in OVA format, which are archives that can contain a complete VM 
> including multiple VMDKs and other files such as ISOs. And currently, 
> Cloudstack only supports Template creation based on OVA files containing a 
> single disk. If a user creates a template from a OVA file containing more 
> than 1 disk and launches an instance using this template, only the first disk 
> is attached to the new instance and other disks are ignored.
> Similarly with uploaded volumes, attaching an uploaded volume that contains 
> multiple disks to a VM will result in only one VMDK to being attached to the 
> VM.
> This behavior needs to be improved in VMWare to support OVA files with 
> multiple disks for both uploaded volumes and templates. i.e. If a user 
> creates a template from a OVA file containing more than 1 disk and launches 
> an instance using this template, the first disk should be attached to the new 
> instance as the ROOT disk and volumes should be created based on other VMDK 
> disks in the OVA file and should be attached to the instance.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10109) Enable dedication of public IPs to SSVM and CPVM

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317932#comment-16317932
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10109:
-

blueorangutan commented on issue #2394: CLOUDSTACK-10109: Fix regression from 
PR #2295
URL: https://github.com/apache/cloudstack/pull/2394#issuecomment-356205315
 
 
   @rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been 
kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Enable dedication of public IPs to SSVM and CPVM
> 
>
> Key: CLOUDSTACK-10109
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10109
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: public01.png, public02.png, public03.png
>
>
> It is required to dedicate a public IP range for SSVM and CPVM in order to 
> apply firewall rules to control inbound access.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10109) Enable dedication of public IPs to SSVM and CPVM

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317928#comment-16317928
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10109:
-

rhtyd commented on issue #2394: CLOUDSTACK-10109: Fix regression from PR #2295
URL: https://github.com/apache/cloudstack/pull/2394#issuecomment-356205195
 
 
   @blueorangutan test


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Enable dedication of public IPs to SSVM and CPVM
> 
>
> Key: CLOUDSTACK-10109
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10109
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: public01.png, public02.png, public03.png
>
>
> It is required to dedicate a public IP range for SSVM and CPVM in order to 
> apply firewall rules to control inbound access.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9620) Improvements for Managed Storage

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317908#comment-16317908
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9620:


blueorangutan commented on issue #2298: CLOUDSTACK-9620: Enhancements for 
managed storage
URL: https://github.com/apache/cloudstack/pull/2298#issuecomment-356200671
 
 
   @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted 
as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improvements for Managed Storage
> 
>
> Key: CLOUDSTACK-9620
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9620
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Management Server, VMware, XenServer
>Affects Versions: 4.11.0.0
> Environment: KVM, vSphere, and XenServer
>Reporter: Mike Tutkowski
>Assignee: Mike Tutkowski
> Fix For: 4.11.0.0
>
>
> Allowed zone-wide primary storage based on a custom plug-in to be added via 
> the GUI in a KVM-only environment (previously this only worked for XenServer 
> and VMware)
> Added support for root disks on managed storage with KVM
> Added support for volume snapshots with managed storage on KVM
> Enabled creating a template directly from a volume (i.e. without having to go 
> through a volume snapshot) on KVM with managed storage
> Only allowed the resizing of a volume for managed storage on KVM if the 
> volume in question is either not attached to a VM or is attached to a VM in 
> the Stopped state
> Included support for Reinstall VM on KVM with managed storage
> Enabled offline migration on KVM from non-managed storage to managed storage 
> and vice versa
> Included support for online storage migration on KVM with managed storage 
> (NFS and Ceph to managed storage)
> Added support to download (extract) a managed-storage volume to a QCOW2 file
> When uploading a file from outside of CloudStack to CloudStack, set the min 
> and max IOPS, if applicable.
> Included support for the KVM auto-convergence feature
> The compression flag was actually added in version 1.0.3 (103) as opposed 
> to version 1.3.0 (1003000) (changed this to reflect the correct version)
> On KVM when using iSCSI-based managed storage, if the user shuts a VM down 
> from the guest OS (as opposed to doing so from CloudStack), we need to pass 
> to the KVM agent a list of applicable iSCSI volumes that need to be 
> disconnected.
> Added a new Global Setting: kvm.storage.live.migration.wait
> For XenServer, added a check to enforce that only volumes from zone-wide 
> managed storage can be storage motioned from a host in one cluster to a host 
> in another cluster (cannot do so at the time being with volumes from 
> cluster-scoped managed storage)
> Don’t allow Storage XenMotion on a VM that has any managed-storage volume 
> with one or more snapshots.
> Enabled for managed storage with VMware: Template caching, create snapshot, 
> delete snapshot, create volume from snapshot, and create template from 
> snapshot
> Added an SIOC API plug-in to support VMware SIOC
> When starting a VM that uses managed storage in a cluster other than the one 
> it last was running in, we need to remove the reference to the iSCSI volume 
> from the original cluster.
> Added the ability to revert a volume to a snapshot
> Enabled cluster-scoped managed storage
> Added support for VMware dynamic discovery



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10109) Enable dedication of public IPs to SSVM and CPVM

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317903#comment-16317903
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10109:
-

blueorangutan commented on issue #2394: CLOUDSTACK-10109: Fix regression from 
PR #2295
URL: https://github.com/apache/cloudstack/pull/2394#issuecomment-356199870
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1627


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Enable dedication of public IPs to SSVM and CPVM
> 
>
> Key: CLOUDSTACK-10109
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10109
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: public01.png, public02.png, public03.png
>
>
> It is required to dedicate a public IP range for SSVM and CPVM in order to 
> apply firewall rules to control inbound access.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9620) Improvements for Managed Storage

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317877#comment-16317877
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9620:


mike-tutkowski commented on issue #2298: CLOUDSTACK-9620: Enhancements for 
managed storage
URL: https://github.com/apache/cloudstack/pull/2298#issuecomment-356197666
 
 
   @rhtyd I was looking at those tests when I saw the failures came in. It 
seems pretty unlikely that any of this code would be triggering errors in areas 
like VPC, affinity groups, etc. Maybe we should see if we are getting similar 
errors on other PRs?
   
   I can fix the file conflict soon. Thanks!


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improvements for Managed Storage
> 
>
> Key: CLOUDSTACK-9620
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9620
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Management Server, VMware, XenServer
>Affects Versions: 4.11.0.0
> Environment: KVM, vSphere, and XenServer
>Reporter: Mike Tutkowski
>Assignee: Mike Tutkowski
> Fix For: 4.11.0.0
>
>
> Allowed zone-wide primary storage based on a custom plug-in to be added via 
> the GUI in a KVM-only environment (previously this only worked for XenServer 
> and VMware)
> Added support for root disks on managed storage with KVM
> Added support for volume snapshots with managed storage on KVM
> Enabled creating a template directly from a volume (i.e. without having to go 
> through a volume snapshot) on KVM with managed storage
> Only allowed the resizing of a volume for managed storage on KVM if the 
> volume in question is either not attached to a VM or is attached to a VM in 
> the Stopped state
> Included support for Reinstall VM on KVM with managed storage
> Enabled offline migration on KVM from non-managed storage to managed storage 
> and vice versa
> Included support for online storage migration on KVM with managed storage 
> (NFS and Ceph to managed storage)
> Added support to download (extract) a managed-storage volume to a QCOW2 file
> When uploading a file from outside of CloudStack to CloudStack, set the min 
> and max IOPS, if applicable.
> Included support for the KVM auto-convergence feature
> The compression flag was actually added in version 1.0.3 (103) as opposed 
> to version 1.3.0 (1003000) (changed this to reflect the correct version)
> On KVM when using iSCSI-based managed storage, if the user shuts a VM down 
> from the guest OS (as opposed to doing so from CloudStack), we need to pass 
> to the KVM agent a list of applicable iSCSI volumes that need to be 
> disconnected.
> Added a new Global Setting: kvm.storage.live.migration.wait
> For XenServer, added a check to enforce that only volumes from zone-wide 
> managed storage can be storage motioned from a host in one cluster to a host 
> in another cluster (cannot do so at the time being with volumes from 
> cluster-scoped managed storage)
> Don’t allow Storage XenMotion on a VM that has any managed-storage volume 
> with one or more snapshots.
> Enabled for managed storage with VMware: Template caching, create snapshot, 
> delete snapshot, create volume from snapshot, and create template from 
> snapshot
> Added an SIOC API plug-in to support VMware SIOC
> When starting a VM that uses managed storage in a cluster other than the one 
> it last was running in, we need to remove the reference to the iSCSI volume 
> from the original cluster.
> Added the ability to revert a volume to a snapshot
> Enabled cluster-scoped managed storage
> Added support for VMware dynamic discovery



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9620) Improvements for Managed Storage

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317857#comment-16317857
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9620:


rhtyd commented on issue #2298: CLOUDSTACK-9620: Enhancements for managed 
storage
URL: https://github.com/apache/cloudstack/pull/2298#issuecomment-356196162
 
 
   @mike-tutkowski can you look at several of the failures, many could be env 
related. Also fix the conflict?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improvements for Managed Storage
> 
>
> Key: CLOUDSTACK-9620
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9620
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Management Server, VMware, XenServer
>Affects Versions: 4.11.0.0
> Environment: KVM, vSphere, and XenServer
>Reporter: Mike Tutkowski
>Assignee: Mike Tutkowski
> Fix For: 4.11.0.0
>
>
> Allowed zone-wide primary storage based on a custom plug-in to be added via 
> the GUI in a KVM-only environment (previously this only worked for XenServer 
> and VMware)
> Added support for root disks on managed storage with KVM
> Added support for volume snapshots with managed storage on KVM
> Enabled creating a template directly from a volume (i.e. without having to go 
> through a volume snapshot) on KVM with managed storage
> Only allowed the resizing of a volume for managed storage on KVM if the 
> volume in question is either not attached to a VM or is attached to a VM in 
> the Stopped state
> Included support for Reinstall VM on KVM with managed storage
> Enabled offline migration on KVM from non-managed storage to managed storage 
> and vice versa
> Included support for online storage migration on KVM with managed storage 
> (NFS and Ceph to managed storage)
> Added support to download (extract) a managed-storage volume to a QCOW2 file
> When uploading a file from outside of CloudStack to CloudStack, set the min 
> and max IOPS, if applicable.
> Included support for the KVM auto-convergence feature
> The compression flag was actually added in version 1.0.3 (103) as opposed 
> to version 1.3.0 (1003000) (changed this to reflect the correct version)
> On KVM when using iSCSI-based managed storage, if the user shuts a VM down 
> from the guest OS (as opposed to doing so from CloudStack), we need to pass 
> to the KVM agent a list of applicable iSCSI volumes that need to be 
> disconnected.
> Added a new Global Setting: kvm.storage.live.migration.wait
> For XenServer, added a check to enforce that only volumes from zone-wide 
> managed storage can be storage motioned from a host in one cluster to a host 
> in another cluster (cannot do so at the time being with volumes from 
> cluster-scoped managed storage)
> Don’t allow Storage XenMotion on a VM that has any managed-storage volume 
> with one or more snapshots.
> Enabled for managed storage with VMware: Template caching, create snapshot, 
> delete snapshot, create volume from snapshot, and create template from 
> snapshot
> Added an SIOC API plug-in to support VMware SIOC
> When starting a VM that uses managed storage in a cluster other than the one 
> it last was running in, we need to remove the reference to the iSCSI volume 
> from the original cluster.
> Added the ability to revert a volume to a snapshot
> Enabled cluster-scoped managed storage
> Added support for VMware dynamic discovery



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10146) Bypass Secondary Storage for KVM templates

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317855#comment-16317855
 ] 

ASF subversion and git services commented on CLOUDSTACK-10146:
--

Commit e86bb41e0e3facb250cdcb984a8f8f91bf052b2b in cloudstack's branch 
refs/heads/master from [~nicolas.vazquez]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=e86bb41 ]

CLOUDSTACK-10146: Bypass Secondary Storage for KVM templates (#2379)

This feature allows using templates and ISOs avoiding secondary storage as 
intermediate cache on KVM. The virtual machine deployment process is enhanced 
to supported bypassed registered templates and ISOs, delegating the work of 
downloading them to primary storage to the KVM agent instead of the SSVM agent.

Template and ISO registration:
- When hypervisor is KVM, a checkbox is displayed with 'Direct Download' label.
- API methods registerTemplate and registerISO are both extended with this new 
parameter directdownload.
- On template or ISO registration, no download job is sent to SSVM agent, 
CloudStack would only persist an entry on template_store_ref indicating that 
template or ISO has been marked as 'Direct Download' (bypassing Secondary 
Storage). These entries are persisted as:
template_id = Template or ISO id on vm_template table
store_id NULL
download_state = BYPASSED
state = Ready
(Note: these entries allow users to deploy virtual machine from registered 
templates or ISOs)
- An URL validation command is sent to a random KVM host to check if 
template/ISO location can be reached. Metalink are also supported by this 
feature. In case of a metalink, it is fetched and URL check is performed on 
each of its URLs.
- Checksum should be provided as indicated on #2246: {ALGORITHM}CHKSUMHASH
- After template or ISO is registered, it would be displayed in the UI

Virtual machine deployment:
When a 'Direct Download' template is selected for deployment, CloudStack would 
delegate template downloading to destination storage pool via destination host 
by a new pluggable download manager.
Download manager would handle template downloading depending on URL protocol. 
In case of HTTP, request headers can be set by the user via 
vm_template_details. Those details should be persisted as:
Key: HTTP_HEADER
Value: HEADERNAME:HEADERVALUE

In case of HTTPS, a new API method is added 
uploadTemplateDirectDownloadCertificate to allow user importing a client 
certificate into all KVM hosts' keystore before deployment.
After template or ISO is downloaded to primary storage, usual entry would be 
persisted on template_spool_ref indicating the mapping between template/ISO and 
storage pool.

> Bypass Secondary Storage for KVM templates
> --
>
> Key: CLOUDSTACK-10146
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10146
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10146) Bypass Secondary Storage for KVM templates

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317851#comment-16317851
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10146:
-

rhtyd commented on issue #2379: CLOUDSTACK-10146: Bypass Secondary Storage for 
KVM templates
URL: https://github.com/apache/cloudstack/pull/2379#issuecomment-356195834
 
 
   Tests LGTM (template related errors not seen in last run), merging this 
based on code reviews and test results.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bypass Secondary Storage for KVM templates
> --
>
> Key: CLOUDSTACK-10146
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10146
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10109) Enable dedication of public IPs to SSVM and CPVM

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317849#comment-16317849
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10109:
-

blueorangutan commented on issue #2394: CLOUDSTACK-10109: Fix regression from 
PR #2295
URL: https://github.com/apache/cloudstack/pull/2394#issuecomment-356195604
 
 
   @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted 
as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Enable dedication of public IPs to SSVM and CPVM
> 
>
> Key: CLOUDSTACK-10109
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10109
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: public01.png, public02.png, public03.png
>
>
> It is required to dedicate a public IP range for SSVM and CPVM in order to 
> apply firewall rules to control inbound access.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10109) Enable dedication of public IPs to SSVM and CPVM

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317846#comment-16317846
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10109:
-

rhtyd commented on issue #2394: CLOUDSTACK-10109: Fix regression from PR #2295
URL: https://github.com/apache/cloudstack/pull/2394#issuecomment-356195512
 
 
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Enable dedication of public IPs to SSVM and CPVM
> 
>
> Key: CLOUDSTACK-10109
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10109
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: public01.png, public02.png, public03.png
>
>
> It is required to dedicate a public IP range for SSVM and CPVM in order to 
> apply firewall rules to control inbound access.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10109) Enable dedication of public IPs to SSVM and CPVM

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317843#comment-16317843
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10109:
-

rhtyd commented on a change in pull request #2394: CLOUDSTACK-10109: Fix 
regression from PR #2295
URL: https://github.com/apache/cloudstack/pull/2394#discussion_r160328887
 
 

 ##
 File path: server/src/com/cloud/network/IpAddressManagerImpl.java
 ##
 @@ -964,13 +964,7 @@ public PublicIp doInTransaction(TransactionStatus status) 
throws InsufficientAdd
 VpcVO vpc = _vpcDao.findById(vpcId);
 displayIp = vpc.isDisplay();
 }
-PublicIp ip = fetchNewPublicIp(dcId, null, null, owner, 
VlanType.VirtualNetwork, guestNtwkId, isSourceNat, false, null, false, vpcId, 
displayIp, false);
-IPAddressVO publicIp = ip.ip();
-
-markPublicIpAsAllocated(publicIp);
-_ipAddressDao.update(publicIp.getId(), publicIp);
-
-return ip;
+return fetchNewPublicIp(dcId, null, null, owner, 
VlanType.VirtualNetwork, guestNtwkId, isSourceNat, true, null, false, vpcId, 
displayIp, false);
 
 Review comment:
   Yes, that PR incorrectly addressed merge conflict. One of the booleans 
changed from true to false, this fixes that. 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Enable dedication of public IPs to SSVM and CPVM
> 
>
> Key: CLOUDSTACK-10109
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10109
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: public01.png, public02.png, public03.png
>
>
> It is required to dedicate a public IP range for SSVM and CPVM in order to 
> apply firewall rules to control inbound access.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10213) Allow specify SSH key lengh

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317839#comment-16317839
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10213:
-

rhtyd commented on issue #2389: CLOUDSTACK-10213: Allow specify SSH key lengh
URL: https://github.com/apache/cloudstack/pull/2389#issuecomment-356195148
 
 
   Tests ltgm, merging this based on code reviews and tests.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Allow specify SSH key lengh
> ---
>
> Key: CLOUDSTACK-10213
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10213
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Dmytro Shevchenko
>
> SSH keys generated by the ACS are only 1024 bit (RSA). The common standard is 
> now at least 2048 bit.
> decompiled com.jcraft.jsch.KeyPair:
> {code:java}
> public static KeyPair genKeyPair(JSch jsch, int type) throws 
> JSchException {
> return genKeyPair(jsch, type, 1024);
> }
> public static KeyPair genKeyPair(JSch jsch, int type, int key_size) 
> throws JSchException {
> KeyPair kpair = null;
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10213) Allow specify SSH key lengh

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317841#comment-16317841
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10213:
-

rhtyd closed pull request #2389: CLOUDSTACK-10213: Allow specify SSH key lengh
URL: https://github.com/apache/cloudstack/pull/2389
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/server/src/com/cloud/server/ManagementServerImpl.java 
b/server/src/com/cloud/server/ManagementServerImpl.java
index c855c34b60f..855a43e9f7a 100644
--- a/server/src/com/cloud/server/ManagementServerImpl.java
+++ b/server/src/com/cloud/server/ManagementServerImpl.java
@@ -696,6 +696,8 @@
 
 static final ConfigKey vmPasswordLength = new 
ConfigKey("Advanced", Integer.class, "vm.password.length", "6",

   "Specifies the length of a randomly generated password", false);
+static final ConfigKey sshKeyLength = new 
ConfigKey("Advanced", Integer.class, "ssh.key.length",
+"2048", "Specifies custom SSH key length (bit)", true, 
ConfigKey.Scope.Global);
 @Inject
 public AccountManager _accountMgr;
 @Inject
@@ -3045,7 +3047,7 @@ public String getConfigComponentName() {
 
 @Override
 public ConfigKey[] getConfigKeys() {
-return new ConfigKey[] {vmPasswordLength};
+return new ConfigKey[] {vmPasswordLength, sshKeyLength};
 }
 
 protected class EventPurgeTask extends ManagedContextRunnable {
@@ -3577,7 +3579,7 @@ public SSHKeyPair createSSHKeyPair(final 
CreateSSHKeyPairCmd cmd) {
 throw new InvalidParameterValueException("A key pair with name '" 
+ cmd.getName() + "' already exists.");
 }
 
-final SSHKeysHelper keys = new SSHKeysHelper();
+final SSHKeysHelper keys = new SSHKeysHelper(sshKeyLength.value());
 
 final String name = cmd.getName();
 final String publicKey = keys.getPublicKey();
diff --git a/utils/src/main/java/com/cloud/utils/ssh/SSHKeysHelper.java 
b/utils/src/main/java/com/cloud/utils/ssh/SSHKeysHelper.java
index 39db5c46c1b..f80baaf47a1 100644
--- a/utils/src/main/java/com/cloud/utils/ssh/SSHKeysHelper.java
+++ b/utils/src/main/java/com/cloud/utils/ssh/SSHKeysHelper.java
@@ -43,9 +43,9 @@ private static String toHexString(byte[] b) {
 return sb.toString();
 }
 
-public SSHKeysHelper() {
+public SSHKeysHelper(Integer keyLength) {
 try {
-keyPair = KeyPair.genKeyPair(new JSch(), KeyPair.RSA);
+keyPair = KeyPair.genKeyPair(new JSch(), KeyPair.RSA, keyLength);
 } catch (JSchException e) {
 e.printStackTrace();
 }


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Allow specify SSH key lengh
> ---
>
> Key: CLOUDSTACK-10213
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10213
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Dmytro Shevchenko
>
> SSH keys generated by the ACS are only 1024 bit (RSA). The common standard is 
> now at least 2048 bit.
> decompiled com.jcraft.jsch.KeyPair:
> {code:java}
> public static KeyPair genKeyPair(JSch jsch, int type) throws 
> JSchException {
> return genKeyPair(jsch, type, 1024);
> }
> public static KeyPair genKeyPair(JSch jsch, int type, int key_size) 
> throws JSchException {
> KeyPair kpair = null;
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10109) Enable dedication of public IPs to SSVM and CPVM

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317795#comment-16317795
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10109:
-

blueorangutan commented on issue #2394: CLOUDSTACK-10109: Fix regression from 
PR #2295
URL: https://github.com/apache/cloudstack/pull/2394#issuecomment-35614
 
 
   Trillian test result (tid-2083)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 39405 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2394-t2083-kvm-centos7.zip
   Intermitten failure detected: 
/marvin/tests/smoke/test_deploy_virtio_scsi_vm.py
   Intermitten failure detected: /marvin/tests/smoke/test_deploy_vm_iso.py
   Intermitten failure detected: /marvin/tests/smoke/test_iso.py
   Intermitten failure detected: /marvin/tests/smoke/test_ssvm.py
   Smoke tests completed. 63 look OK, 4 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   ContextSuite context=TestDeployVirtioSCSIVM>:teardown | `Error` | 38.63 | 
test_deploy_virtio_scsi_vm.py
   test_deploy_vm_from_iso | `Error` | 1514.47 | test_deploy_vm_iso.py
   test_01_1_create_iso_with_checksum_sha1_negative | `Error` | 70.60 | 
test_iso.py
   test_01_create_iso_with_checksum_sha1 | `Error` | 65.49 | test_iso.py
   test_01_create_iso_with_checksum_sha1 | `Error` | 70.59 | test_iso.py
   test_02_1_create_iso_with_checksum_sha256_negative | `Error` | 70.58 | 
test_iso.py
   test_02_create_iso_with_checksum_sha256 | `Error` | 65.47 | test_iso.py
   test_02_create_iso_with_checksum_sha256 | `Error` | 70.55 | test_iso.py
   test_03_1_create_iso_with_checksum_md5_negative | `Error` | 70.59 | 
test_iso.py
   test_03_create_iso_with_checksum_md5 | `Error` | 65.47 | test_iso.py
   test_03_create_iso_with_checksum_md5 | `Error` | 70.55 | test_iso.py
   test_04_create_iso_with_no_checksum | `Error` | 65.47 | test_iso.py
   test_04_create_iso_with_no_checksum | `Error` | 70.56 | test_iso.py
   test_01_create_iso | `Failure` | 1514.64 | test_iso.py
   ContextSuite context=TestISO>:setup | `Error` | 3034.58 | test_iso.py
   test_03_ssvm_internals | `Failure` | 3.32 | test_ssvm.py
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Enable dedication of public IPs to SSVM and CPVM
> 
>
> Key: CLOUDSTACK-10109
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10109
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: public01.png, public02.png, public03.png
>
>
> It is required to dedicate a public IP range for SSVM and CPVM in order to 
> apply firewall rules to control inbound access.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10188) Resource Accounting for primary storage is Broken

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317735#comment-16317735
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10188:
-

bwsw commented on issue #2362: CLOUDSTACK-10188 - Resource Accounting for 
primary storage is Broken when Domains are in use
URL: https://github.com/apache/cloudstack/pull/2362#issuecomment-356184418
 
 
   Here https://github.com/apache/cloudstack/pull/2379#issuecomment-356183984 
it also fails. I suppose the regression is introduced in 
https://github.com/apache/cloudstack/pull/2088


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Resource Accounting for primary storage is Broken
> -
>
> Key: CLOUDSTACK-10188
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10188
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.9.0, 4.10.0.0, 4.11.0.0
>Reporter: Ivan Kudryavtsev
>
> During storage expunge domain resource statistics for primary storage space 
> resource counter is not updated for domain. This leads to the situation when 
> domain resource statistics for primary storage is overfilled (statistics only 
> increase but not decrease).
> Global scheduled task resourcecount.check.interval > 0 provides a workaround 
> but not fixes the problem truly because when accounts inside domains use 
> primary_storage allocation/deallocation intensively it leads to service block 
> of operation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10146) Bypass Secondary Storage for KVM templates

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317731#comment-16317731
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10146:
-

blueorangutan commented on issue #2379: CLOUDSTACK-10146: Bypass Secondary 
Storage for KVM templates
URL: https://github.com/apache/cloudstack/pull/2379#issuecomment-356183984
 
 
   Trillian test result (tid-2085)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 32518 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2379-t2085-kvm-centos7.zip
   Intermitten failure detected: /marvin/tests/smoke/test_internal_lb.py
   Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
   Intermitten failure detected: /marvin/tests/smoke/test_vpc_vpn.py
   Smoke tests completed. 66 look OK, 1 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   test_05_rvpc_multi_tiers | `Failure` | 345.94 | test_vpc_redundant.py
   test_05_rvpc_multi_tiers | `Error` | 391.55 | test_vpc_redundant.py
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bypass Secondary Storage for KVM templates
> --
>
> Key: CLOUDSTACK-10146
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10146
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10188) Resource Accounting for primary storage is Broken

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317725#comment-16317725
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10188:
-

bwsw commented on issue #2362: CLOUDSTACK-10188 - Resource Accounting for 
primary storage is Broken when Domains are in use
URL: https://github.com/apache/cloudstack/pull/2362#issuecomment-356183214
 
 
   @rhtyd @borisstoyanov 
   Same test [test_volumes.py/test_07_resize_fail] fails in previously merged 
https://github.com/apache/cloudstack/pull/2088 which includes massive volume 
changes. I don't see anything related to my code yet, but suppose that PR 
[2088] could bring a regression. Before that merge I haven't seen that test to 
fail.
 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Resource Accounting for primary storage is Broken
> -
>
> Key: CLOUDSTACK-10188
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10188
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.9.0, 4.10.0.0, 4.11.0.0
>Reporter: Ivan Kudryavtsev
>
> During storage expunge domain resource statistics for primary storage space 
> resource counter is not updated for domain. This leads to the situation when 
> domain resource statistics for primary storage is overfilled (statistics only 
> increase but not decrease).
> Global scheduled task resourcecount.check.interval > 0 provides a workaround 
> but not fixes the problem truly because when accounts inside domains use 
> primary_storage allocation/deallocation intensively it leads to service block 
> of operation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10188) Resource Accounting for primary storage is Broken

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317724#comment-16317724
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10188:
-

bwsw commented on issue #2362: CLOUDSTACK-10188 - Resource Accounting for 
primary storage is Broken when Domains are in use
URL: https://github.com/apache/cloudstack/pull/2362#issuecomment-356183214
 
 
   @rhtyd @borisstoyanov 
   Same test [test_volumes.py/test_07_resize_fail] failed in previously merged 
https://github.com/apache/cloudstack/pull/2088 which includes massive volume 
changes. I don't see anything related to my code yet, but suppose that PR 
[2088] could bring a regression. Before that merge I haven't seen that test to 
fail.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Resource Accounting for primary storage is Broken
> -
>
> Key: CLOUDSTACK-10188
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10188
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.9.0, 4.10.0.0, 4.11.0.0
>Reporter: Ivan Kudryavtsev
>
> During storage expunge domain resource statistics for primary storage space 
> resource counter is not updated for domain. This leads to the situation when 
> domain resource statistics for primary storage is overfilled (statistics only 
> increase but not decrease).
> Global scheduled task resourcecount.check.interval > 0 provides a workaround 
> but not fixes the problem truly because when accounts inside domains use 
> primary_storage allocation/deallocation intensively it leads to service block 
> of operation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9620) Improvements for Managed Storage

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317650#comment-16317650
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9620:


blueorangutan commented on issue #2298: CLOUDSTACK-9620: Enhancements for 
managed storage
URL: https://github.com/apache/cloudstack/pull/2298#issuecomment-356173697
 
 
   Trillian test result (tid-2082)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 32655 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2298-t2082-kvm-centos7.zip
   Intermitten failure detected: /marvin/tests/smoke/test_accounts.py
   Intermitten failure detected: 
/marvin/tests/smoke/test_affinity_groups_projects.py
   Intermitten failure detected: /marvin/tests/smoke/test_affinity_groups.py
   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_vpc_redundant.py
   Smoke tests completed. 61 look OK, 6 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   ContextSuite context=TestAccounts>:setup | `Error` | 0.00 | test_accounts.py
   ContextSuite context=TestAddVmToSubDomain>:setup | `Error` | 0.00 | 
test_accounts.py
   test_DeleteDomain | `Error` | 1.42 | test_accounts.py
   test_forceDeleteDomain | `Error` | 1.48 | test_accounts.py
   ContextSuite context=TestRemoveUserFromAccount>:setup | `Error` | 21.66 | 
test_accounts.py
   ContextSuite context=TestDeployVmWithAffinityGroup>:setup | `Error` | 0.00 | 
test_affinity_groups_projects.py
   ContextSuite context=TestDeployVmWithAffinityGroup>:setup | `Error` | 0.00 | 
test_affinity_groups.py
   test_02_internallb_roundrobin_1RVPC_3VM_HTTP_port80 | `Failure` | 245.25 | 
test_internal_lb.py
   test_02_vpc_privategw_static_routes | `Failure` | 232.61 | 
test_privategw_acl.py
   test_03_vpc_privategw_restart_vpc_cleanup | `Failure` | 207.20 | 
test_privategw_acl.py
   test_02_redundant_VPC_default_routes | `Failure` | 872.33 | 
test_vpc_redundant.py
   test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
`Failure` | 86.21 | test_vpc_redundant.py
   test_04_rvpc_network_garbage_collector_nics | `Failure` | 75.83 | 
test_vpc_redundant.py
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improvements for Managed Storage
> 
>
> Key: CLOUDSTACK-9620
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9620
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Management Server, VMware, XenServer
>Affects Versions: 4.11.0.0
> Environment: KVM, vSphere, and XenServer
>Reporter: Mike Tutkowski
>Assignee: Mike Tutkowski
> Fix For: 4.11.0.0
>
>
> Allowed zone-wide primary storage based on a custom plug-in to be added via 
> the GUI in a KVM-only environment (previously this only worked for XenServer 
> and VMware)
> Added support for root disks on managed storage with KVM
> Added support for volume snapshots with managed storage on KVM
> Enabled creating a template directly from a volume (i.e. without having to go 
> through a volume snapshot) on KVM with managed storage
> Only allowed the resizing of a volume for managed storage on KVM if the 
> volume in question is either not attached to a VM or is attached to a VM in 
> the Stopped state
> Included support for Reinstall VM on KVM with managed storage
> Enabled offline migration on KVM from non-managed storage to managed storage 
> and vice versa
> Included support for online storage migration on KVM with managed storage 
> (NFS and Ceph to managed storage)
> Added support to download (extract) a managed-storage volume to a QCOW2 file
> When uploading a file from outside of CloudStack to CloudStack, set the min 
> and max IOPS, if applicable.
> Included support for the KVM auto-convergence feature
> The compression flag was actually added in version 1.0.3 (103) as opposed 
> to version 1.3.0 (1003000) (changed this to reflect the correct version)
> On KVM when using iSCSI-based managed storage, if the user shuts a VM down 
> from the guest OS (as opposed to doing so from CloudStack), we need to pass 
> to the KVM agent a list of applicable iSCSI volumes that need to be 
> disconnected.
> Added a new Global Setting: kvm.storage.live.migration.wait
> For 

[jira] [Commented] (CLOUDSTACK-10213) Allow specify SSH key lengh

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317511#comment-16317511
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10213:
-

blueorangutan commented on issue #2389: CLOUDSTACK-10213: Allow specify SSH key 
lengh
URL: https://github.com/apache/cloudstack/pull/2389#issuecomment-356152660
 
 
   Trillian test result (tid-2079)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 24727 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2389-t2079-kvm-centos7.zip
   Smoke tests completed. 67 look OK, 0 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Allow specify SSH key lengh
> ---
>
> Key: CLOUDSTACK-10213
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10213
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Dmytro Shevchenko
>
> SSH keys generated by the ACS are only 1024 bit (RSA). The common standard is 
> now at least 2048 bit.
> decompiled com.jcraft.jsch.KeyPair:
> {code:java}
> public static KeyPair genKeyPair(JSch jsch, int type) throws 
> JSchException {
> return genKeyPair(jsch, type, 1024);
> }
> public static KeyPair genKeyPair(JSch jsch, int type, int key_size) 
> throws JSchException {
> KeyPair kpair = null;
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9620) Improvements for Managed Storage

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317416#comment-16317416
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9620:


mike-tutkowski commented on issue #2298: CLOUDSTACK-9620: Enhancements for 
managed storage
URL: https://github.com/apache/cloudstack/pull/2298#issuecomment-356140858
 
 
   @rhtyd Using your system VM templates fixed it - thanks!


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improvements for Managed Storage
> 
>
> Key: CLOUDSTACK-9620
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9620
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Management Server, VMware, XenServer
>Affects Versions: 4.11.0.0
> Environment: KVM, vSphere, and XenServer
>Reporter: Mike Tutkowski
>Assignee: Mike Tutkowski
> Fix For: 4.11.0.0
>
>
> Allowed zone-wide primary storage based on a custom plug-in to be added via 
> the GUI in a KVM-only environment (previously this only worked for XenServer 
> and VMware)
> Added support for root disks on managed storage with KVM
> Added support for volume snapshots with managed storage on KVM
> Enabled creating a template directly from a volume (i.e. without having to go 
> through a volume snapshot) on KVM with managed storage
> Only allowed the resizing of a volume for managed storage on KVM if the 
> volume in question is either not attached to a VM or is attached to a VM in 
> the Stopped state
> Included support for Reinstall VM on KVM with managed storage
> Enabled offline migration on KVM from non-managed storage to managed storage 
> and vice versa
> Included support for online storage migration on KVM with managed storage 
> (NFS and Ceph to managed storage)
> Added support to download (extract) a managed-storage volume to a QCOW2 file
> When uploading a file from outside of CloudStack to CloudStack, set the min 
> and max IOPS, if applicable.
> Included support for the KVM auto-convergence feature
> The compression flag was actually added in version 1.0.3 (103) as opposed 
> to version 1.3.0 (1003000) (changed this to reflect the correct version)
> On KVM when using iSCSI-based managed storage, if the user shuts a VM down 
> from the guest OS (as opposed to doing so from CloudStack), we need to pass 
> to the KVM agent a list of applicable iSCSI volumes that need to be 
> disconnected.
> Added a new Global Setting: kvm.storage.live.migration.wait
> For XenServer, added a check to enforce that only volumes from zone-wide 
> managed storage can be storage motioned from a host in one cluster to a host 
> in another cluster (cannot do so at the time being with volumes from 
> cluster-scoped managed storage)
> Don’t allow Storage XenMotion on a VM that has any managed-storage volume 
> with one or more snapshots.
> Enabled for managed storage with VMware: Template caching, create snapshot, 
> delete snapshot, create volume from snapshot, and create template from 
> snapshot
> Added an SIOC API plug-in to support VMware SIOC
> When starting a VM that uses managed storage in a cluster other than the one 
> it last was running in, we need to remove the reference to the iSCSI volume 
> from the original cluster.
> Added the ability to revert a volume to a snapshot
> Enabled cluster-scoped managed storage
> Added support for VMware dynamic discovery



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10212) Changing IPv4 Address of NIC in Basic Networking does not update the gateway

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317387#comment-16317387
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10212:
-

blueorangutan commented on issue #2388: CLOUDSTACK-10212: Update 
Netmask/Gateway when Changing IPv4 address
URL: https://github.com/apache/cloudstack/pull/2388#issuecomment-356137476
 
 
   Trillian test result (tid-2076)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 31309 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2388-t2076-kvm-centos7.zip
   Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
   Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py
   Smoke tests completed. 66 look OK, 1 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | `Failure` | 394.32 | 
test_vpc_redundant.py
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Changing IPv4 Address of NIC in Basic Networking does not update the gateway
> 
>
> Key: CLOUDSTACK-10212
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10212
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.10.0.0
> Environment: CloudStack 4.10 - KVM - Basic Networking
>Reporter: Wido den Hollander
>Assignee: Wido den Hollander
> Fix For: 4.11.0.0
>
>
> When using updateVMNic to change the IPv4 address of a NIC the IPv4 address 
> is changed, but the Gateway stays the same.
> This can cause problems when multiple IPv4 ranges are used and a wrong 
> gateway is issued to the Instance through DHCP.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10109) Enable dedication of public IPs to SSVM and CPVM

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317180#comment-16317180
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10109:
-

DaanHoogland commented on a change in pull request #2394: CLOUDSTACK-10109: Fix 
regression from PR #2295
URL: https://github.com/apache/cloudstack/pull/2394#discussion_r160267434
 
 

 ##
 File path: server/src/com/cloud/network/IpAddressManagerImpl.java
 ##
 @@ -964,13 +964,7 @@ public PublicIp doInTransaction(TransactionStatus status) 
throws InsufficientAdd
 VpcVO vpc = _vpcDao.findById(vpcId);
 displayIp = vpc.isDisplay();
 }
-PublicIp ip = fetchNewPublicIp(dcId, null, null, owner, 
VlanType.VirtualNetwork, guestNtwkId, isSourceNat, false, null, false, vpcId, 
displayIp, false);
-IPAddressVO publicIp = ip.ip();
-
-markPublicIpAsAllocated(publicIp);
-_ipAddressDao.update(publicIp.getId(), publicIp);
-
-return ip;
+return fetchNewPublicIp(dcId, null, null, owner, 
VlanType.VirtualNetwork, guestNtwkId, isSourceNat, true, null, false, vpcId, 
displayIp, false);
 
 Review comment:
   this is a revert of the code in #2295. Is that functionality now broken?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Enable dedication of public IPs to SSVM and CPVM
> 
>
> Key: CLOUDSTACK-10109
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10109
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: public01.png, public02.png, public03.png
>
>
> It is required to dedicate a public IP range for SSVM and CPVM in order to 
> apply firewall rules to control inbound access.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9620) Improvements for Managed Storage

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317168#comment-16317168
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9620:


rhtyd commented on issue #2298: CLOUDSTACK-9620: Enhancements for managed 
storage
URL: https://github.com/apache/cloudstack/pull/2298#issuecomment-356109368
 
 
   @mike-tutkowski can you try the new debian9 systemvmtemplates, get from 
http://dl.rohityadav.cloud/debian9/ or build yourself using qemu+packer using 
tools/appliance/build.sh


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improvements for Managed Storage
> 
>
> Key: CLOUDSTACK-9620
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9620
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Management Server, VMware, XenServer
>Affects Versions: 4.11.0.0
> Environment: KVM, vSphere, and XenServer
>Reporter: Mike Tutkowski
>Assignee: Mike Tutkowski
> Fix For: 4.11.0.0
>
>
> Allowed zone-wide primary storage based on a custom plug-in to be added via 
> the GUI in a KVM-only environment (previously this only worked for XenServer 
> and VMware)
> Added support for root disks on managed storage with KVM
> Added support for volume snapshots with managed storage on KVM
> Enabled creating a template directly from a volume (i.e. without having to go 
> through a volume snapshot) on KVM with managed storage
> Only allowed the resizing of a volume for managed storage on KVM if the 
> volume in question is either not attached to a VM or is attached to a VM in 
> the Stopped state
> Included support for Reinstall VM on KVM with managed storage
> Enabled offline migration on KVM from non-managed storage to managed storage 
> and vice versa
> Included support for online storage migration on KVM with managed storage 
> (NFS and Ceph to managed storage)
> Added support to download (extract) a managed-storage volume to a QCOW2 file
> When uploading a file from outside of CloudStack to CloudStack, set the min 
> and max IOPS, if applicable.
> Included support for the KVM auto-convergence feature
> The compression flag was actually added in version 1.0.3 (103) as opposed 
> to version 1.3.0 (1003000) (changed this to reflect the correct version)
> On KVM when using iSCSI-based managed storage, if the user shuts a VM down 
> from the guest OS (as opposed to doing so from CloudStack), we need to pass 
> to the KVM agent a list of applicable iSCSI volumes that need to be 
> disconnected.
> Added a new Global Setting: kvm.storage.live.migration.wait
> For XenServer, added a check to enforce that only volumes from zone-wide 
> managed storage can be storage motioned from a host in one cluster to a host 
> in another cluster (cannot do so at the time being with volumes from 
> cluster-scoped managed storage)
> Don’t allow Storage XenMotion on a VM that has any managed-storage volume 
> with one or more snapshots.
> Enabled for managed storage with VMware: Template caching, create snapshot, 
> delete snapshot, create volume from snapshot, and create template from 
> snapshot
> Added an SIOC API plug-in to support VMware SIOC
> When starting a VM that uses managed storage in a cluster other than the one 
> it last was running in, we need to remove the reference to the iSCSI volume 
> from the original cluster.
> Added the ability to revert a volume to a snapshot
> Enabled cluster-scoped managed storage
> Added support for VMware dynamic discovery



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9620) Improvements for Managed Storage

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317162#comment-16317162
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9620:


mike-tutkowski commented on issue #2298: CLOUDSTACK-9620: Enhancements for 
managed storage
URL: https://github.com/apache/cloudstack/pull/2298#issuecomment-356108935
 
 
   @rhtyd I also should note that this is a Basic Zone (I think a lot of our 
automated tests (maybe all) use an Advanced Zone).


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improvements for Managed Storage
> 
>
> Key: CLOUDSTACK-9620
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9620
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Management Server, VMware, XenServer
>Affects Versions: 4.11.0.0
> Environment: KVM, vSphere, and XenServer
>Reporter: Mike Tutkowski
>Assignee: Mike Tutkowski
> Fix For: 4.11.0.0
>
>
> Allowed zone-wide primary storage based on a custom plug-in to be added via 
> the GUI in a KVM-only environment (previously this only worked for XenServer 
> and VMware)
> Added support for root disks on managed storage with KVM
> Added support for volume snapshots with managed storage on KVM
> Enabled creating a template directly from a volume (i.e. without having to go 
> through a volume snapshot) on KVM with managed storage
> Only allowed the resizing of a volume for managed storage on KVM if the 
> volume in question is either not attached to a VM or is attached to a VM in 
> the Stopped state
> Included support for Reinstall VM on KVM with managed storage
> Enabled offline migration on KVM from non-managed storage to managed storage 
> and vice versa
> Included support for online storage migration on KVM with managed storage 
> (NFS and Ceph to managed storage)
> Added support to download (extract) a managed-storage volume to a QCOW2 file
> When uploading a file from outside of CloudStack to CloudStack, set the min 
> and max IOPS, if applicable.
> Included support for the KVM auto-convergence feature
> The compression flag was actually added in version 1.0.3 (103) as opposed 
> to version 1.3.0 (1003000) (changed this to reflect the correct version)
> On KVM when using iSCSI-based managed storage, if the user shuts a VM down 
> from the guest OS (as opposed to doing so from CloudStack), we need to pass 
> to the KVM agent a list of applicable iSCSI volumes that need to be 
> disconnected.
> Added a new Global Setting: kvm.storage.live.migration.wait
> For XenServer, added a check to enforce that only volumes from zone-wide 
> managed storage can be storage motioned from a host in one cluster to a host 
> in another cluster (cannot do so at the time being with volumes from 
> cluster-scoped managed storage)
> Don’t allow Storage XenMotion on a VM that has any managed-storage volume 
> with one or more snapshots.
> Enabled for managed storage with VMware: Template caching, create snapshot, 
> delete snapshot, create volume from snapshot, and create template from 
> snapshot
> Added an SIOC API plug-in to support VMware SIOC
> When starting a VM that uses managed storage in a cluster other than the one 
> it last was running in, we need to remove the reference to the iSCSI volume 
> from the original cluster.
> Added the ability to revert a volume to a snapshot
> Enabled cluster-scoped managed storage
> Added support for VMware dynamic discovery



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9620) Improvements for Managed Storage

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317158#comment-16317158
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9620:


mike-tutkowski commented on issue #2298: CLOUDSTACK-9620: Enhancements for 
managed storage
URL: https://github.com/apache/cloudstack/pull/2298#issuecomment-356107909
 
 
   @rhtyd This is the system VM template that's in use: 
https://builds.cloudstack.org/view/master/job/build-master-systemvm/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-4.11.0.440-xen.vhd.bz2


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improvements for Managed Storage
> 
>
> Key: CLOUDSTACK-9620
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9620
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Management Server, VMware, XenServer
>Affects Versions: 4.11.0.0
> Environment: KVM, vSphere, and XenServer
>Reporter: Mike Tutkowski
>Assignee: Mike Tutkowski
> Fix For: 4.11.0.0
>
>
> Allowed zone-wide primary storage based on a custom plug-in to be added via 
> the GUI in a KVM-only environment (previously this only worked for XenServer 
> and VMware)
> Added support for root disks on managed storage with KVM
> Added support for volume snapshots with managed storage on KVM
> Enabled creating a template directly from a volume (i.e. without having to go 
> through a volume snapshot) on KVM with managed storage
> Only allowed the resizing of a volume for managed storage on KVM if the 
> volume in question is either not attached to a VM or is attached to a VM in 
> the Stopped state
> Included support for Reinstall VM on KVM with managed storage
> Enabled offline migration on KVM from non-managed storage to managed storage 
> and vice versa
> Included support for online storage migration on KVM with managed storage 
> (NFS and Ceph to managed storage)
> Added support to download (extract) a managed-storage volume to a QCOW2 file
> When uploading a file from outside of CloudStack to CloudStack, set the min 
> and max IOPS, if applicable.
> Included support for the KVM auto-convergence feature
> The compression flag was actually added in version 1.0.3 (103) as opposed 
> to version 1.3.0 (1003000) (changed this to reflect the correct version)
> On KVM when using iSCSI-based managed storage, if the user shuts a VM down 
> from the guest OS (as opposed to doing so from CloudStack), we need to pass 
> to the KVM agent a list of applicable iSCSI volumes that need to be 
> disconnected.
> Added a new Global Setting: kvm.storage.live.migration.wait
> For XenServer, added a check to enforce that only volumes from zone-wide 
> managed storage can be storage motioned from a host in one cluster to a host 
> in another cluster (cannot do so at the time being with volumes from 
> cluster-scoped managed storage)
> Don’t allow Storage XenMotion on a VM that has any managed-storage volume 
> with one or more snapshots.
> Enabled for managed storage with VMware: Template caching, create snapshot, 
> delete snapshot, create volume from snapshot, and create template from 
> snapshot
> Added an SIOC API plug-in to support VMware SIOC
> When starting a VM that uses managed storage in a cluster other than the one 
> it last was running in, we need to remove the reference to the iSCSI volume 
> from the original cluster.
> Added the ability to revert a volume to a snapshot
> Enabled cluster-scoped managed storage
> Added support for VMware dynamic discovery



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9620) Improvements for Managed Storage

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317157#comment-16317157
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9620:


mike-tutkowski commented on issue #2298: CLOUDSTACK-9620: Enhancements for 
managed storage
URL: https://github.com/apache/cloudstack/pull/2298#issuecomment-356107638
 
 
   @rhtyd I should point out that these are system VMs running on XenServer 
7.0.0.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improvements for Managed Storage
> 
>
> Key: CLOUDSTACK-9620
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9620
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Management Server, VMware, XenServer
>Affects Versions: 4.11.0.0
> Environment: KVM, vSphere, and XenServer
>Reporter: Mike Tutkowski
>Assignee: Mike Tutkowski
> Fix For: 4.11.0.0
>
>
> Allowed zone-wide primary storage based on a custom plug-in to be added via 
> the GUI in a KVM-only environment (previously this only worked for XenServer 
> and VMware)
> Added support for root disks on managed storage with KVM
> Added support for volume snapshots with managed storage on KVM
> Enabled creating a template directly from a volume (i.e. without having to go 
> through a volume snapshot) on KVM with managed storage
> Only allowed the resizing of a volume for managed storage on KVM if the 
> volume in question is either not attached to a VM or is attached to a VM in 
> the Stopped state
> Included support for Reinstall VM on KVM with managed storage
> Enabled offline migration on KVM from non-managed storage to managed storage 
> and vice versa
> Included support for online storage migration on KVM with managed storage 
> (NFS and Ceph to managed storage)
> Added support to download (extract) a managed-storage volume to a QCOW2 file
> When uploading a file from outside of CloudStack to CloudStack, set the min 
> and max IOPS, if applicable.
> Included support for the KVM auto-convergence feature
> The compression flag was actually added in version 1.0.3 (103) as opposed 
> to version 1.3.0 (1003000) (changed this to reflect the correct version)
> On KVM when using iSCSI-based managed storage, if the user shuts a VM down 
> from the guest OS (as opposed to doing so from CloudStack), we need to pass 
> to the KVM agent a list of applicable iSCSI volumes that need to be 
> disconnected.
> Added a new Global Setting: kvm.storage.live.migration.wait
> For XenServer, added a check to enforce that only volumes from zone-wide 
> managed storage can be storage motioned from a host in one cluster to a host 
> in another cluster (cannot do so at the time being with volumes from 
> cluster-scoped managed storage)
> Don’t allow Storage XenMotion on a VM that has any managed-storage volume 
> with one or more snapshots.
> Enabled for managed storage with VMware: Template caching, create snapshot, 
> delete snapshot, create volume from snapshot, and create template from 
> snapshot
> Added an SIOC API plug-in to support VMware SIOC
> When starting a VM that uses managed storage in a cluster other than the one 
> it last was running in, we need to remove the reference to the iSCSI volume 
> from the original cluster.
> Added the ability to revert a volume to a snapshot
> Enabled cluster-scoped managed storage
> Added support for VMware dynamic discovery



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9620) Improvements for Managed Storage

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317150#comment-16317150
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9620:


mike-tutkowski commented on issue #2298: CLOUDSTACK-9620: Enhancements for 
managed storage
URL: https://github.com/apache/cloudstack/pull/2298#issuecomment-356106901
 
 
   @rhtyd Has something changed with regards to how we need to set up a new 
cloud? Neither my SSVM nor my CPVM was successful at starting up its agent.
   
   From cloud.log in SSVM, I see the following:
   
   Mon Jan  8 20:52:24 UTC 2018 Incompleted parameters STORAGE_IP:, 
STORAGE_NETMASK:, STORAGE_CIDR:. Cannot setup storage network
   Mon Jan  8 20:52:24 UTC 2018 Not setting up route of RFC1918 space to 
10.117.40.126 befause 10.117.40.27 is RFC1918.
   
   Perhaps there is a new Global Setting I need to configure?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improvements for Managed Storage
> 
>
> Key: CLOUDSTACK-9620
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9620
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Management Server, VMware, XenServer
>Affects Versions: 4.11.0.0
> Environment: KVM, vSphere, and XenServer
>Reporter: Mike Tutkowski
>Assignee: Mike Tutkowski
> Fix For: 4.11.0.0
>
>
> Allowed zone-wide primary storage based on a custom plug-in to be added via 
> the GUI in a KVM-only environment (previously this only worked for XenServer 
> and VMware)
> Added support for root disks on managed storage with KVM
> Added support for volume snapshots with managed storage on KVM
> Enabled creating a template directly from a volume (i.e. without having to go 
> through a volume snapshot) on KVM with managed storage
> Only allowed the resizing of a volume for managed storage on KVM if the 
> volume in question is either not attached to a VM or is attached to a VM in 
> the Stopped state
> Included support for Reinstall VM on KVM with managed storage
> Enabled offline migration on KVM from non-managed storage to managed storage 
> and vice versa
> Included support for online storage migration on KVM with managed storage 
> (NFS and Ceph to managed storage)
> Added support to download (extract) a managed-storage volume to a QCOW2 file
> When uploading a file from outside of CloudStack to CloudStack, set the min 
> and max IOPS, if applicable.
> Included support for the KVM auto-convergence feature
> The compression flag was actually added in version 1.0.3 (103) as opposed 
> to version 1.3.0 (1003000) (changed this to reflect the correct version)
> On KVM when using iSCSI-based managed storage, if the user shuts a VM down 
> from the guest OS (as opposed to doing so from CloudStack), we need to pass 
> to the KVM agent a list of applicable iSCSI volumes that need to be 
> disconnected.
> Added a new Global Setting: kvm.storage.live.migration.wait
> For XenServer, added a check to enforce that only volumes from zone-wide 
> managed storage can be storage motioned from a host in one cluster to a host 
> in another cluster (cannot do so at the time being with volumes from 
> cluster-scoped managed storage)
> Don’t allow Storage XenMotion on a VM that has any managed-storage volume 
> with one or more snapshots.
> Enabled for managed storage with VMware: Template caching, create snapshot, 
> delete snapshot, create volume from snapshot, and create template from 
> snapshot
> Added an SIOC API plug-in to support VMware SIOC
> When starting a VM that uses managed storage in a cluster other than the one 
> it last was running in, we need to remove the reference to the iSCSI volume 
> from the original cluster.
> Added the ability to revert a volume to a snapshot
> Enabled cluster-scoped managed storage
> Added support for VMware dynamic discovery



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10109) Enable dedication of public IPs to SSVM and CPVM

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316974#comment-16316974
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10109:
-

rhtyd commented on issue #2394: CLOUDSTACK-10109: Fix regression from PR #2295
URL: https://github.com/apache/cloudstack/pull/2394#issuecomment-356083100
 
 
   Travis has passed finally! /cc @DaanHoogland @mike-tutowski 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Enable dedication of public IPs to SSVM and CPVM
> 
>
> Key: CLOUDSTACK-10109
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10109
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: public01.png, public02.png, public03.png
>
>
> It is required to dedicate a public IP range for SSVM and CPVM in order to 
> apply firewall rules to control inbound access.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10109) Enable dedication of public IPs to SSVM and CPVM

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316794#comment-16316794
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10109:
-

blueorangutan commented on issue #2394: CLOUDSTACK-10109: Fix regression from 
PR #2295
URL: https://github.com/apache/cloudstack/pull/2394#issuecomment-356062180
 
 
   @rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been 
kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Enable dedication of public IPs to SSVM and CPVM
> 
>
> Key: CLOUDSTACK-10109
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10109
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: public01.png, public02.png, public03.png
>
>
> It is required to dedicate a public IP range for SSVM and CPVM in order to 
> apply firewall rules to control inbound access.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10109) Enable dedication of public IPs to SSVM and CPVM

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316793#comment-16316793
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10109:
-

rhtyd commented on issue #2394: CLOUDSTACK-10109: Fix regression from PR #2295
URL: https://github.com/apache/cloudstack/pull/2394#issuecomment-356062020
 
 
   @blueorangutan test


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Enable dedication of public IPs to SSVM and CPVM
> 
>
> Key: CLOUDSTACK-10109
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10109
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: public01.png, public02.png, public03.png
>
>
> It is required to dedicate a public IP range for SSVM and CPVM in order to 
> apply firewall rules to control inbound access.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10109) Enable dedication of public IPs to SSVM and CPVM

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316789#comment-16316789
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10109:
-

blueorangutan commented on issue #2394: CLOUDSTACK-10109: Fix regression from 
PR #2295
URL: https://github.com/apache/cloudstack/pull/2394#issuecomment-356061939
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1626


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Enable dedication of public IPs to SSVM and CPVM
> 
>
> Key: CLOUDSTACK-10109
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10109
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: public01.png, public02.png, public03.png
>
>
> It is required to dedicate a public IP range for SSVM and CPVM in order to 
> apply firewall rules to control inbound access.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10213) Allow specify SSH key lengh

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316770#comment-16316770
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10213:
-

blueorangutan commented on issue #2389: CLOUDSTACK-10213: Allow specify SSH key 
lengh
URL: https://github.com/apache/cloudstack/pull/2389#issuecomment-356056717
 
 
   @rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been 
kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Allow specify SSH key lengh
> ---
>
> Key: CLOUDSTACK-10213
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10213
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Dmytro Shevchenko
>
> SSH keys generated by the ACS are only 1024 bit (RSA). The common standard is 
> now at least 2048 bit.
> decompiled com.jcraft.jsch.KeyPair:
> {code:java}
> public static KeyPair genKeyPair(JSch jsch, int type) throws 
> JSchException {
> return genKeyPair(jsch, type, 1024);
> }
> public static KeyPair genKeyPair(JSch jsch, int type, int key_size) 
> throws JSchException {
> KeyPair kpair = null;
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10213) Allow specify SSH key lengh

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316769#comment-16316769
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10213:
-

rhtyd commented on issue #2389: CLOUDSTACK-10213: Allow specify SSH key lengh
URL: https://github.com/apache/cloudstack/pull/2389#issuecomment-356056463
 
 
   @blueorangutan test


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Allow specify SSH key lengh
> ---
>
> Key: CLOUDSTACK-10213
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10213
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Dmytro Shevchenko
>
> SSH keys generated by the ACS are only 1024 bit (RSA). The common standard is 
> now at least 2048 bit.
> decompiled com.jcraft.jsch.KeyPair:
> {code:java}
> public static KeyPair genKeyPair(JSch jsch, int type) throws 
> JSchException {
> return genKeyPair(jsch, type, 1024);
> }
> public static KeyPair genKeyPair(JSch jsch, int type, int key_size) 
> throws JSchException {
> KeyPair kpair = null;
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9620) Improvements for Managed Storage

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316767#comment-16316767
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9620:


rhtyd commented on issue #2298: CLOUDSTACK-9620: Enhancements for managed 
storage
URL: https://github.com/apache/cloudstack/pull/2298#issuecomment-356056163
 
 
   Thanks @mike-tutkowski I've created a PR #2394 to fix Travis failures. I've 
kicked a test run in the background now. Meanwhile, can you run solidfire tests 
against your PR and ensure that they are all passing, and share results as well?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improvements for Managed Storage
> 
>
> Key: CLOUDSTACK-9620
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9620
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Management Server, VMware, XenServer
>Affects Versions: 4.11.0.0
> Environment: KVM, vSphere, and XenServer
>Reporter: Mike Tutkowski
>Assignee: Mike Tutkowski
> Fix For: 4.11.0.0
>
>
> Allowed zone-wide primary storage based on a custom plug-in to be added via 
> the GUI in a KVM-only environment (previously this only worked for XenServer 
> and VMware)
> Added support for root disks on managed storage with KVM
> Added support for volume snapshots with managed storage on KVM
> Enabled creating a template directly from a volume (i.e. without having to go 
> through a volume snapshot) on KVM with managed storage
> Only allowed the resizing of a volume for managed storage on KVM if the 
> volume in question is either not attached to a VM or is attached to a VM in 
> the Stopped state
> Included support for Reinstall VM on KVM with managed storage
> Enabled offline migration on KVM from non-managed storage to managed storage 
> and vice versa
> Included support for online storage migration on KVM with managed storage 
> (NFS and Ceph to managed storage)
> Added support to download (extract) a managed-storage volume to a QCOW2 file
> When uploading a file from outside of CloudStack to CloudStack, set the min 
> and max IOPS, if applicable.
> Included support for the KVM auto-convergence feature
> The compression flag was actually added in version 1.0.3 (103) as opposed 
> to version 1.3.0 (1003000) (changed this to reflect the correct version)
> On KVM when using iSCSI-based managed storage, if the user shuts a VM down 
> from the guest OS (as opposed to doing so from CloudStack), we need to pass 
> to the KVM agent a list of applicable iSCSI volumes that need to be 
> disconnected.
> Added a new Global Setting: kvm.storage.live.migration.wait
> For XenServer, added a check to enforce that only volumes from zone-wide 
> managed storage can be storage motioned from a host in one cluster to a host 
> in another cluster (cannot do so at the time being with volumes from 
> cluster-scoped managed storage)
> Don’t allow Storage XenMotion on a VM that has any managed-storage volume 
> with one or more snapshots.
> Enabled for managed storage with VMware: Template caching, create snapshot, 
> delete snapshot, create volume from snapshot, and create template from 
> snapshot
> Added an SIOC API plug-in to support VMware SIOC
> When starting a VM that uses managed storage in a cluster other than the one 
> it last was running in, we need to remove the reference to the iSCSI volume 
> from the original cluster.
> Added the ability to revert a volume to a snapshot
> Enabled cluster-scoped managed storage
> Added support for VMware dynamic discovery



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10146) Bypass Secondary Storage for KVM templates

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316755#comment-16316755
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10146:
-

blueorangutan commented on issue #2379: CLOUDSTACK-10146: Bypass Secondary 
Storage for KVM templates
URL: https://github.com/apache/cloudstack/pull/2379#issuecomment-356054223
 
 
   @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has 
been kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bypass Secondary Storage for KVM templates
> --
>
> Key: CLOUDSTACK-10146
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10146
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10146) Bypass Secondary Storage for KVM templates

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316754#comment-16316754
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10146:
-

borisstoyanov commented on issue #2379: CLOUDSTACK-10146: Bypass Secondary 
Storage for KVM templates
URL: https://github.com/apache/cloudstack/pull/2379#issuecomment-356054086
 
 
   @blueorangutan test


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bypass Secondary Storage for KVM templates
> --
>
> Key: CLOUDSTACK-10146
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10146
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10188) Resource Accounting for primary storage is Broken

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316737#comment-16316737
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10188:
-

blueorangutan commented on issue #2362: CLOUDSTACK-10188 - Resource Accounting 
for primary storage is Broken when Domains are in use
URL: https://github.com/apache/cloudstack/pull/2362#issuecomment-356051033
 
 
   Trillian test result (tid-2073)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 31361 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2362-t2073-kvm-centos7.zip
   Intermitten failure detected: /marvin/tests/smoke/test_routers_network_ops.py
   Intermitten failure detected: /marvin/tests/smoke/test_volumes.py
   Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
   Intermitten failure detected: /marvin/tests/smoke/test_host_maintenance.py
   Smoke tests completed. 66 look OK, 1 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   test_07_resize_fail | `Failure` | 15.34 | test_volumes.py
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Resource Accounting for primary storage is Broken
> -
>
> Key: CLOUDSTACK-10188
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10188
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.9.0, 4.10.0.0, 4.11.0.0
>Reporter: Ivan Kudryavtsev
>
> During storage expunge domain resource statistics for primary storage space 
> resource counter is not updated for domain. This leads to the situation when 
> domain resource statistics for primary storage is overfilled (statistics only 
> increase but not decrease).
> Global scheduled task resourcecount.check.interval > 0 provides a workaround 
> but not fixes the problem truly because when accounts inside domains use 
> primary_storage allocation/deallocation intensively it leads to service block 
> of operation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CLOUDSTACK-10197) XenServer 7.1: Cannot mount xentool iso from cloudstack on VMs

[Khosrow Moossavi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Khosrow Moossavi resolved CLOUDSTACK-10197.
---
Resolution: Fixed

> XenServer 7.1: Cannot mount  xentool iso from cloudstack on VMs
> ---
>
> Key: CLOUDSTACK-10197
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10197
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.10.0.0
> Environment: XenServer 7.0+
>Reporter: Khosrow Moossavi
> Fix For: Future, 4.11.0.0
>
>
> In XenServer 7.0+ xentools iso has been renamed from *xs-tools* to 
> *guest-tools* so CloudStack fails to attach it to any VM.
> {code}
> (acs-admin) > attach iso 
> virtualmachineid=d13eeff1-2d99-46a9-8fc5-3510df6e9f5e 
> id=e8a56540-0fc3-44de-9911-635d2d8f25c4
> errorcode = 530
> errortext = Failed to attach iso
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CLOUDSTACK-10197) XenServer 7.1: Cannot mount xentool iso from cloudstack on VMs

[Khosrow Moossavi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Khosrow Moossavi updated CLOUDSTACK-10197:
--
Fix Version/s: 4.11.0.0

> XenServer 7.1: Cannot mount  xentool iso from cloudstack on VMs
> ---
>
> Key: CLOUDSTACK-10197
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10197
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.10.0.0
> Environment: XenServer 7.0+
>Reporter: Khosrow Moossavi
> Fix For: Future, 4.11.0.0
>
>
> In XenServer 7.0+ xentools iso has been renamed from *xs-tools* to 
> *guest-tools* so CloudStack fails to attach it to any VM.
> {code}
> (acs-admin) > attach iso 
> virtualmachineid=d13eeff1-2d99-46a9-8fc5-3510df6e9f5e 
> id=e8a56540-0fc3-44de-9911-635d2d8f25c4
> errorcode = 530
> errortext = Failed to attach iso
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10212) Changing IPv4 Address of NIC in Basic Networking does not update the gateway

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316487#comment-16316487
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10212:
-

wido commented on issue #2388: CLOUDSTACK-10212: Update Netmask/Gateway when 
Changing IPv4 address
URL: https://github.com/apache/cloudstack/pull/2388#issuecomment-355999640
 
 
   Ok, get it @rhtyd :) It was the weekend in between which made me not reply 
to the PR.
   
   I don't have anything else to submit :)


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Changing IPv4 Address of NIC in Basic Networking does not update the gateway
> 
>
> Key: CLOUDSTACK-10212
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10212
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.10.0.0
> Environment: CloudStack 4.10 - KVM - Basic Networking
>Reporter: Wido den Hollander
>Assignee: Wido den Hollander
> Fix For: 4.11.0.0
>
>
> When using updateVMNic to change the IPv4 address of a NIC the IPv4 address 
> is changed, but the Gateway stays the same.
> This can cause problems when multiple IPv4 ranges are used and a wrong 
> gateway is issued to the Instance through DHCP.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10212) Changing IPv4 Address of NIC in Basic Networking does not update the gateway

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316477#comment-16316477
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10212:
-

blueorangutan commented on issue #2388: CLOUDSTACK-10212: Update 
Netmask/Gateway when Changing IPv4 address
URL: https://github.com/apache/cloudstack/pull/2388#issuecomment-355997553
 
 
   @rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been 
kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Changing IPv4 Address of NIC in Basic Networking does not update the gateway
> 
>
> Key: CLOUDSTACK-10212
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10212
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.10.0.0
> Environment: CloudStack 4.10 - KVM - Basic Networking
>Reporter: Wido den Hollander
>Assignee: Wido den Hollander
> Fix For: 4.11.0.0
>
>
> When using updateVMNic to change the IPv4 address of a NIC the IPv4 address 
> is changed, but the Gateway stays the same.
> This can cause problems when multiple IPv4 ranges are used and a wrong 
> gateway is issued to the Instance through DHCP.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10212) Changing IPv4 Address of NIC in Basic Networking does not update the gateway

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316475#comment-16316475
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10212:
-

rhtyd commented on issue #2388: CLOUDSTACK-10212: Update Netmask/Gateway when 
Changing IPv4 address
URL: https://github.com/apache/cloudstack/pull/2388#issuecomment-355997348
 
 
   @wido Yes, due to NPE in tests I could run further tests/reviews. I've 
removed PRs from 4.11 milestone where authors were not replying or were busy 
elsewhere. This was done in past 3 days, as today was the "freeze" date. I'll 
re-include this on your request but now no more PRs please :)
   
   @blueorangutan test


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Changing IPv4 Address of NIC in Basic Networking does not update the gateway
> 
>
> Key: CLOUDSTACK-10212
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10212
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.10.0.0
> Environment: CloudStack 4.10 - KVM - Basic Networking
>Reporter: Wido den Hollander
>Assignee: Wido den Hollander
> Fix For: 4.11.0.0
>
>
> When using updateVMNic to change the IPv4 address of a NIC the IPv4 address 
> is changed, but the Gateway stays the same.
> This can cause problems when multiple IPv4 ranges are used and a wrong 
> gateway is issued to the Instance through DHCP.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9813) Use configdrive for userdata, metadata & password

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316472#comment-16316472
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9813:


fmaximus commented on issue #2097: [4.11] CLOUDSTACK-9813: Extending Config 
Drive support
URL: https://github.com/apache/cloudstack/pull/2097#issuecomment-355996429
 
 
   Test Failure analysis:
   
   Test | Cause
    | -
   test_ssvm.py | Marvin test incorrect: Test checks that system VM gateway is 
equal to the gateway of the public IP ranges. It just takes the first public IP 
range, but doesn't take forsystemvms flag into account. Marvin log shows that 2 
public ip ranges are present, the first one having forsystemvms=False.
   test_templates.py | Extract Template Failed with invalid 
URLhttp://192.168.100.10/userdata/8cec10dd-4dba-459e-a072-e5c34a8c092c.ova
   test_usage.py | Download template: No route to host
   test_vm_life_cycle.py | DetachIsoCmd fails with "Failed to detach iso".
   test_volumes.py | Extract Volume Failed with invalid 
URLhttp://192.168.100.10/userdata/6417246a-f94c-4e9c-a0ac-3a03daf7bb54.ova
   
   Can you provide the management server logs, to be able to find out the cause 
of DetachIsoCmd issue.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Use configdrive for userdata, metadata & password 
> --
>
> Key: CLOUDSTACK-9813
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9813
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Network Controller, Secondary Storage, SystemVM, 
> VMware
>Affects Versions: Future
>Reporter: Eric Waegeman
>Assignee: Kris Sterckx
>
> To avoid the use of an extra VM for the virtual router we implement 
> configdrive for userdata, metadata & password. 
> The configdrive ISO is created on the secondary store and the KVM & VMware 
> plugins are adapted to accept the configdrive ISO as second cdrom.
> Is applicable for isolated, VPC and shared networks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CLOUDSTACK-10121) move user API

[Paul Angus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul Angus updated CLOUDSTACK-10121:

Issue Type: New Feature  (was: Improvement)

> move user API
> -
>
> Key: CLOUDSTACK-10121
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10121
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Daan Hoogland
>
> to be able to move a user from one account to another a move user will be 
> created that does nothing but change the accountId. This is separate from 
> updateUser as only service level calls and maybe admin will be allowed to use 
> it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CLOUDSTACK-10126) Separate Subnet for CPVM and SSVM

[Paul Angus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul Angus updated CLOUDSTACK-10126:

Issue Type: New Feature  (was: Improvement)

> Separate Subnet for CPVM and SSVM
> -
>
> Key: CLOUDSTACK-10126
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10126
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>
> Separate Management Subnet for CPVM and SSVM



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CLOUDSTACK-10109) Enable dedication of public IPs to SSVM and CPVM

[Paul Angus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul Angus updated CLOUDSTACK-10109:

Issue Type: New Feature  (was: Improvement)

> Enable dedication of public IPs to SSVM and CPVM
> 
>
> Key: CLOUDSTACK-10109
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10109
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: public01.png, public02.png, public03.png
>
>
> It is required to dedicate a public IP range for SSVM and CPVM in order to 
> apply firewall rules to control inbound access.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CLOUDSTACK-9861) Expire VM snapshots after configured duration

[Paul Angus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul Angus updated CLOUDSTACK-9861:
---
Issue Type: New Feature  (was: Improvement)

> Expire VM snapshots after configured duration
> -
>
> Key: CLOUDSTACK-9861
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9861
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Abhinandan Prateek
>
> Currently, users can keep VM snapshots for an indefinite time period.  
> Long-lived snapshots can cause stability issues on the hypervisor.
> Requirement: Add a timeout for VM Snapshots, whereby snapshots get 
> automatically deleted after a given time period. This would be available at 
> account level, with a default value determined by a global setting. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CLOUDSTACK-9949) add ability to specify mac address when deployVirtualMachine or addNicToVirtualMachine is called

[Paul Angus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul Angus updated CLOUDSTACK-9949:
---
Issue Type: New Feature  (was: Improvement)

> add ability to specify mac address when deployVirtualMachine or 
> addNicToVirtualMachine is called
> 
>
> Key: CLOUDSTACK-9949
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9949
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, Network Controller
> Environment: All
>Reporter: Nathan Johnson
>Assignee: Nathan Johnson
>Priority: Minor
>
> Please allow specifying a mac address:
> 1) in deployVirtualMachine , as macaddress parameter (as with default 
> networking) or with iptonetworklist mac parameter.
> 2) in addNicToVirtualMachine call, with macaddress parameter.
> This would migrating VMs from another environment into cloudstack.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CLOUDSTACK-9998) CloudStack exporter for Prometheus

[Paul Angus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul Angus updated CLOUDSTACK-9998:
---
Issue Type: New Feature  (was: Bug)

> CloudStack exporter for Prometheus
> --
>
> Key: CLOUDSTACK-9998
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9998
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
> Fix For: Future, 4.11.0.0
>
>
> The aim is to implement a CloudStack exporter plugin for exporting metrics 
> data to Prometheus monitoring system.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CLOUDSTACK-10103) Cloudian Connector for CloudStack

[Paul Angus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul Angus updated CLOUDSTACK-10103:

Issue Type: New Feature  (was: Bug)

> Cloudian Connector for CloudStack
> -
>
> Key: CLOUDSTACK-10103
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10103
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
> Fix For: Future, 4.11.0.0
>
>
> Cloudian Connector for CloudStack that supports following:
> - UI based SSO into Cloudian CMC from CloudStack
> - Auto-provisioning and auto-deprovisioning of CloudStack accounts and 
> domains as Cloudian Users and Groups, when plugin is enabled
> - Easy configuration using CloudStack global settings
> - ASF 2.0 license compatible



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CLOUDSTACK-10077) Allow account to use the same site-2-site VPN gateway with different configs for several VPCs

[Paul Angus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul Angus updated CLOUDSTACK-10077:

Summary: Allow account to use the same site-2-site VPN gateway with 
different configs for several VPCs  (was: Allow account to use the same 
site-2-site VPN gateway with different configs for serveral VPCs)

> Allow account to use the same site-2-site VPN gateway with different configs 
> for several VPCs
> -
>
> Key: CLOUDSTACK-10077
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10077
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VPC
>Affects Versions: 4.5.2, 4.10.0.0, 4.9.3.0
>Reporter: René Moser
>Assignee: René Moser
> Attachments: Selection_044.jpg
>
>
> Related 
> https://github.com/apache/cloudstack/commit/86bbe211f2341d52d1d64b0b6d3abcdcef85d3ee
>  and CLOUDSTACK-494
> Currently we can not have serveral VPCs in one account with different VPN 
> customer gateways configuration per same gateway IP. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CLOUDSTACK-10102) New Network Type (L2)

[Paul Angus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul Angus updated CLOUDSTACK-10102:

Issue Type: New Feature  (was: Improvement)

> New Network Type (L2)
> -
>
> Key: CLOUDSTACK-10102
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10102
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Fix For: 4.11.0.0
>
>
> Feature Specification: 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74680920



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10212) Changing IPv4 Address of NIC in Basic Networking does not update the gateway

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316451#comment-16316451
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10212:
-

wido commented on issue #2388: CLOUDSTACK-10212: Update Netmask/Gateway when 
Changing IPv4 address
URL: https://github.com/apache/cloudstack/pull/2388#issuecomment-355991462
 
 
   @rhtyd I thought I added the milestone 4.11 to this PR, but I see you 
removed it:
   
   
   wido added this to the 4.11 milestone 3 days ago
   rhtyd removed this from the 4.11 milestone 2 days ago
   
   
   Was this due to the NPE during the tests?
   
   As this is a bug, we can include it in 4.11, right?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Changing IPv4 Address of NIC in Basic Networking does not update the gateway
> 
>
> Key: CLOUDSTACK-10212
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10212
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.10.0.0
> Environment: CloudStack 4.10 - KVM - Basic Networking
>Reporter: Wido den Hollander
>Assignee: Wido den Hollander
> Fix For: 4.11.0.0
>
>
> When using updateVMNic to change the IPv4 address of a NIC the IPv4 address 
> is changed, but the Gateway stays the same.
> This can cause problems when multiple IPv4 ranges are used and a wrong 
> gateway is issued to the Instance through DHCP.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10217) When IPv4 address of Instance is updated DHCP data is not cleared on VR

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316445#comment-16316445
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10217:
-

wido commented on issue #2393: CLOUDSTACK-10217: Clean up old MAC addresses 
from DHCP lease file
URL: https://github.com/apache/cloudstack/pull/2393#issuecomment-355991010
 
 
   @DaanHoogland No, it's not. Changing the IP 'works' in 4.10/master, but it 
doesn't change the gateway.
   
   I discovered these duplicate MACs during #2388


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> When IPv4 address of Instance is updated DHCP data is not cleared on VR
> ---
>
> Key: CLOUDSTACK-10217
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10217
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.10.0.0
> Environment: Basic Networking - KVM
>Reporter: Wido den Hollander
>Assignee: Wido den Hollander
>  Labels: basic-networking, dhcp, virtual-router
> Fix For: 4.11.0.0
>
>
> When the IPv4 address of a NIC is changed the new entry is added to the DHCP 
> lease file in the Virtual Router, but the old entry (with the same MAC) is 
> not removed and this causes the Instance to still receive the old address.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10217) When IPv4 address of Instance is updated DHCP data is not cleared on VR

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316390#comment-16316390
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10217:
-

DaanHoogland commented on issue #2393: CLOUDSTACK-10217: Clean up old MAC 
addresses from DHCP lease file
URL: https://github.com/apache/cloudstack/pull/2393#issuecomment-355979212
 
 
   @wido is #2388 a prerequisite for this?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> When IPv4 address of Instance is updated DHCP data is not cleared on VR
> ---
>
> Key: CLOUDSTACK-10217
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10217
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.10.0.0
> Environment: Basic Networking - KVM
>Reporter: Wido den Hollander
>Assignee: Wido den Hollander
>  Labels: basic-networking, dhcp, virtual-router
> Fix For: 4.11.0.0
>
>
> When the IPv4 address of a NIC is changed the new entry is added to the DHCP 
> lease file in the Virtual Router, but the old entry (with the same MAC) is 
> not removed and this causes the Instance to still receive the old address.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10146) Bypass Secondary Storage for KVM templates

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316388#comment-16316388
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10146:
-

blueorangutan commented on issue #2379: CLOUDSTACK-10146: Bypass Secondary 
Storage for KVM templates
URL: https://github.com/apache/cloudstack/pull/2379#issuecomment-355978710
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1623


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bypass Secondary Storage for KVM templates
> --
>
> Key: CLOUDSTACK-10146
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10146
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9620) Improvements for Managed Storage

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316380#comment-16316380
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9620:


mike-tutkowski commented on issue #2298: CLOUDSTACK-9620: Enhancements for 
managed storage
URL: https://github.com/apache/cloudstack/pull/2298#issuecomment-355976720
 
 
   Hi @rhtyd: I notice that the following PRs from our 4.11 milestone list are 
also failing on the same Travis test as mine: 2128, 2146, 2362, 2389, 2393. 
Perhaps we have a problem with that test?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improvements for Managed Storage
> 
>
> Key: CLOUDSTACK-9620
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9620
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Management Server, VMware, XenServer
>Affects Versions: 4.11.0.0
> Environment: KVM, vSphere, and XenServer
>Reporter: Mike Tutkowski
>Assignee: Mike Tutkowski
> Fix For: 4.11.0.0
>
>
> Allowed zone-wide primary storage based on a custom plug-in to be added via 
> the GUI in a KVM-only environment (previously this only worked for XenServer 
> and VMware)
> Added support for root disks on managed storage with KVM
> Added support for volume snapshots with managed storage on KVM
> Enabled creating a template directly from a volume (i.e. without having to go 
> through a volume snapshot) on KVM with managed storage
> Only allowed the resizing of a volume for managed storage on KVM if the 
> volume in question is either not attached to a VM or is attached to a VM in 
> the Stopped state
> Included support for Reinstall VM on KVM with managed storage
> Enabled offline migration on KVM from non-managed storage to managed storage 
> and vice versa
> Included support for online storage migration on KVM with managed storage 
> (NFS and Ceph to managed storage)
> Added support to download (extract) a managed-storage volume to a QCOW2 file
> When uploading a file from outside of CloudStack to CloudStack, set the min 
> and max IOPS, if applicable.
> Included support for the KVM auto-convergence feature
> The compression flag was actually added in version 1.0.3 (103) as opposed 
> to version 1.3.0 (1003000) (changed this to reflect the correct version)
> On KVM when using iSCSI-based managed storage, if the user shuts a VM down 
> from the guest OS (as opposed to doing so from CloudStack), we need to pass 
> to the KVM agent a list of applicable iSCSI volumes that need to be 
> disconnected.
> Added a new Global Setting: kvm.storage.live.migration.wait
> For XenServer, added a check to enforce that only volumes from zone-wide 
> managed storage can be storage motioned from a host in one cluster to a host 
> in another cluster (cannot do so at the time being with volumes from 
> cluster-scoped managed storage)
> Don’t allow Storage XenMotion on a VM that has any managed-storage volume 
> with one or more snapshots.
> Enabled for managed storage with VMware: Template caching, create snapshot, 
> delete snapshot, create volume from snapshot, and create template from 
> snapshot
> Added an SIOC API plug-in to support VMware SIOC
> When starting a VM that uses managed storage in a cluster other than the one 
> it last was running in, we need to remove the reference to the iSCSI volume 
> from the original cluster.
> Added the ability to revert a volume to a snapshot
> Enabled cluster-scoped managed storage
> Added support for VMware dynamic discovery



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10146) Bypass Secondary Storage for KVM templates

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316342#comment-16316342
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10146:
-

blueorangutan commented on issue #2379: CLOUDSTACK-10146: Bypass Secondary 
Storage for KVM templates
URL: https://github.com/apache/cloudstack/pull/2379#issuecomment-355971822
 
 
   @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep 
you posted as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bypass Secondary Storage for KVM templates
> --
>
> Key: CLOUDSTACK-10146
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10146
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10146) Bypass Secondary Storage for KVM templates

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316340#comment-16316340
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10146:
-

borisstoyanov commented on issue #2379: CLOUDSTACK-10146: Bypass Secondary 
Storage for KVM templates
URL: https://github.com/apache/cloudstack/pull/2379#issuecomment-355971751
 
 
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bypass Secondary Storage for KVM templates
> --
>
> Key: CLOUDSTACK-10146
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10146
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10146) Bypass Secondary Storage for KVM templates

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316314#comment-16316314
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10146:
-

blueorangutan commented on issue #2379: CLOUDSTACK-10146: Bypass Secondary 
Storage for KVM templates
URL: https://github.com/apache/cloudstack/pull/2379#issuecomment-355918590
 
 
   @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep 
you posted as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bypass Secondary Storage for KVM templates
> --
>
> Key: CLOUDSTACK-10146
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10146
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10146) Bypass Secondary Storage for KVM templates

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316315#comment-16316315
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10146:
-

blueorangutan commented on issue #2379: CLOUDSTACK-10146: Bypass Secondary 
Storage for KVM templates
URL: https://github.com/apache/cloudstack/pull/2379#issuecomment-355924687
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1620


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bypass Secondary Storage for KVM templates
> --
>
> Key: CLOUDSTACK-10146
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10146
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10146) Bypass Secondary Storage for KVM templates

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316313#comment-16316313
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10146:
-

borisstoyanov commented on issue #2379: CLOUDSTACK-10146: Bypass Secondary 
Storage for KVM templates
URL: https://github.com/apache/cloudstack/pull/2379#issuecomment-355918410
 
 
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bypass Secondary Storage for KVM templates
> --
>
> Key: CLOUDSTACK-10146
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10146
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10217) When IPv4 address of Instance is updated DHCP data is not cleared on VR

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316292#comment-16316292
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10217:
-

wido commented on issue #2393: CLOUDSTACK-10217: Clean up old MAC addresses 
from DHCP lease file
URL: https://github.com/apache/cloudstack/pull/2393#issuecomment-355965666
 
 
   I see I forgot the label on #2388 @rhtyd , my bad!
   
   The cs_dhcp.py file in this case hasn't changed with the Debian 9 template 
so it's still valid.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> When IPv4 address of Instance is updated DHCP data is not cleared on VR
> ---
>
> Key: CLOUDSTACK-10217
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10217
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.10.0.0
> Environment: Basic Networking - KVM
>Reporter: Wido den Hollander
>Assignee: Wido den Hollander
>  Labels: basic-networking, dhcp, virtual-router
> Fix For: 4.11.0.0
>
>
> When the IPv4 address of a NIC is changed the new entry is added to the DHCP 
> lease file in the Virtual Router, but the old entry (with the same MAC) is 
> not removed and this causes the Instance to still receive the old address.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9813) Use configdrive for userdata, metadata & password

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316242#comment-16316242
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9813:


DaanHoogland commented on a change in pull request #2097: [4.11] 
CLOUDSTACK-9813: Extending Config Drive support
URL: https://github.com/apache/cloudstack/pull/2097#discussion_r160032397
 
 

 ##
 File path: core/src/com/cloud/agent/api/HandleConfigDriveIsoCommand.java
 ##
 @@ -0,0 +1,78 @@
+//
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements.  See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership.  The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License.  You may obtain a copy of the License at
+//
+//   http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied.  See the License for the
+// specific language governing permissions and limitations
+// under the License.
+//
+
+package com.cloud.agent.api;
+
+import java.util.List;
+
+import com.cloud.agent.api.to.DataStoreTO;
+
+public class HandleConfigDriveIsoCommand extends Command {
 
 Review comment:
   this is a much more sensible place to add javadoc.
 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Use configdrive for userdata, metadata & password 
> --
>
> Key: CLOUDSTACK-9813
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9813
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Network Controller, Secondary Storage, SystemVM, 
> VMware
>Affects Versions: Future
>Reporter: Eric Waegeman
>Assignee: Kris Sterckx
>
> To avoid the use of an extra VM for the virtual router we implement 
> configdrive for userdata, metadata & password. 
> The configdrive ISO is created on the secondary store and the KVM & VMware 
> plugins are adapted to accept the configdrive ISO as second cdrom.
> Is applicable for isolated, VPC and shared networks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10217) When IPv4 address of Instance is updated DHCP data is not cleared on VR

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316238#comment-16316238
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10217:
-

rhtyd commented on issue #2393: CLOUDSTACK-10217: Clean up old MAC addresses 
from DHCP lease file
URL: https://github.com/apache/cloudstack/pull/2393#issuecomment-355956651
 
 
   @wido PR #2388 is not marked for 4.11, are you able to reproduce the fix for 
this PR with a new 4.11 debian9 systemvmtemplate?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> When IPv4 address of Instance is updated DHCP data is not cleared on VR
> ---
>
> Key: CLOUDSTACK-10217
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10217
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.10.0.0
> Environment: Basic Networking - KVM
>Reporter: Wido den Hollander
>Assignee: Wido den Hollander
>  Labels: basic-networking, dhcp, virtual-router
> Fix For: 4.11.0.0
>
>
> When the IPv4 address of a NIC is changed the new entry is added to the DHCP 
> lease file in the Virtual Router, but the old entry (with the same MAC) is 
> not removed and this causes the Instance to still receive the old address.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10217) When IPv4 address of Instance is updated DHCP data is not cleared on VR

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316191#comment-16316191
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10217:
-

blueorangutan commented on issue #2393: CLOUDSTACK-10217: Clean up old MAC 
addresses from DHCP lease file
URL: https://github.com/apache/cloudstack/pull/2393#issuecomment-355950824
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1621


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> When IPv4 address of Instance is updated DHCP data is not cleared on VR
> ---
>
> Key: CLOUDSTACK-10217
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10217
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.10.0.0
> Environment: Basic Networking - KVM
>Reporter: Wido den Hollander
>Assignee: Wido den Hollander
>  Labels: basic-networking, dhcp, virtual-router
> Fix For: 4.11.0.0
>
>
> When the IPv4 address of a NIC is changed the new entry is added to the DHCP 
> lease file in the Virtual Router, but the old entry (with the same MAC) is 
> not removed and this causes the Instance to still receive the old address.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10213) Allow specify SSH key lengh

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316190#comment-16316190
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10213:
-

blueorangutan commented on issue #2389: CLOUDSTACK-10213: Allow specify SSH key 
lengh
URL: https://github.com/apache/cloudstack/pull/2389#issuecomment-355950826
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1622


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Allow specify SSH key lengh
> ---
>
> Key: CLOUDSTACK-10213
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10213
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Dmytro Shevchenko
>
> SSH keys generated by the ACS are only 1024 bit (RSA). The common standard is 
> now at least 2048 bit.
> decompiled com.jcraft.jsch.KeyPair:
> {code:java}
> public static KeyPair genKeyPair(JSch jsch, int type) throws 
> JSchException {
> return genKeyPair(jsch, type, 1024);
> }
> public static KeyPair genKeyPair(JSch jsch, int type, int key_size) 
> throws JSchException {
> KeyPair kpair = null;
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CLOUDSTACK-10219) move all nuage specific offerings in current global test_data to its specific place

[Kris Sterckx (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kris Sterckx updated CLOUDSTACK-10219:
--
Affects Version/s: (was: 4.10.0.0)
   4.11.0.0

> move all nuage specific offerings in current global test_data to its specific 
> place
> ---
>
> Key: CLOUDSTACK-10219
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10219
> Project: CloudStack
>  Issue Type: Task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Kris Sterckx
>Assignee: Kris Sterckx
>
> For better seperation of concerns, move all nuage specific offerings present 
> in cloudstack/tools/marvin/marvin/config/test_data.py to its specific place 
> in nuagevsp directory (test/integration/plugins/nuagevsp/)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9813) Use configdrive for userdata, metadata & password

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316176#comment-16316176
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9813:


krissterckx commented on a change in pull request #2097: [4.11] 
CLOUDSTACK-9813: Extending Config Drive support
URL: https://github.com/apache/cloudstack/pull/2097#discussion_r160127168
 
 

 ##
 File path: tools/marvin/marvin/config/test_data.py
 ##
 @@ -2186,6 +2371,33 @@
 "Dns": "VpcVirtualRouter"
 }
 },
+"vpc_offering_configdrive_withoutdns": {
 
 Review comment:
   @rhtyd i created CLOUDSTACK-10219 to track this. We will take this forward. 
I expect this not to happen for 4.11 probably though. Hope that's ok.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Use configdrive for userdata, metadata & password 
> --
>
> Key: CLOUDSTACK-9813
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9813
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Network Controller, Secondary Storage, SystemVM, 
> VMware
>Affects Versions: Future
>Reporter: Eric Waegeman
>Assignee: Kris Sterckx
>
> To avoid the use of an extra VM for the virtual router we implement 
> configdrive for userdata, metadata & password. 
> The configdrive ISO is created on the secondary store and the KVM & VMware 
> plugins are adapted to accept the configdrive ISO as second cdrom.
> Is applicable for isolated, VPC and shared networks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CLOUDSTACK-10219) move all nuage specific offerings in current global test_data to its specific place

[Kris Sterckx (JIRA)]

Kris Sterckx created CLOUDSTACK-10219:
-

 Summary: move all nuage specific offerings in current global 
test_data to its specific place
 Key: CLOUDSTACK-10219
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10219
 Project: CloudStack
  Issue Type: Task
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.10.0.0
Reporter: Kris Sterckx
Assignee: Kris Sterckx


For better seperation of concerns, move all nuage specific offerings present in 
cloudstack/tools/marvin/marvin/config/test_data.py to its specific place in 
nuagevsp directory (test/integration/plugins/nuagevsp/)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CLOUDSTACK-10219) move all nuage specific offerings in current global test_data to its specific place

[Kris Sterckx (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kris Sterckx reassigned CLOUDSTACK-10219:
-

Assignee: Kris Sterckx

> move all nuage specific offerings in current global test_data to its specific 
> place
> ---
>
> Key: CLOUDSTACK-10219
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10219
> Project: CloudStack
>  Issue Type: Task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.10.0.0
>Reporter: Kris Sterckx
>Assignee: Kris Sterckx
>
> For better seperation of concerns, move all nuage specific offerings present 
> in cloudstack/tools/marvin/marvin/config/test_data.py to its specific place 
> in nuagevsp directory (test/integration/plugins/nuagevsp/)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CLOUDSTACK-10219) move all nuage specific offerings in current global test_data to its specific place

[Kris Sterckx (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kris Sterckx reassigned CLOUDSTACK-10219:
-

Assignee: (was: Kris Sterckx)

> move all nuage specific offerings in current global test_data to its specific 
> place
> ---
>
> Key: CLOUDSTACK-10219
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10219
> Project: CloudStack
>  Issue Type: Task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.10.0.0
>Reporter: Kris Sterckx
>
> For better seperation of concerns, move all nuage specific offerings present 
> in cloudstack/tools/marvin/marvin/config/test_data.py to its specific place 
> in nuagevsp directory (test/integration/plugins/nuagevsp/)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10128) Template from snapshot not merging vhd files

[Marcelo Lima (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316155#comment-16316155
 ] 

Marcelo Lima commented on CLOUDSTACK-10128:
---

Obrigado Rafael
Feliz ano novo pra ti

Abraço

--
Marcelo Lima

Mobile: +55 51 99630 4055 | Phone: +55 51 3465 6916 | Fax: +55 51 3465 6916

Rua Brasil 1100/24, Canoas, RS - Brazil - CEP 92310-150

ml...@lotic.com.br | www.lotic.com.br | Twitter:@LoticArq



> Template from snapshot not merging vhd files
> 
>
> Key: CLOUDSTACK-10128
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10128
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.10.0.0, 4.9.2.0, 4.5.2.2, 4.9.3.0
> Environment: Production environment running ACS 4.5.2.2, 4.9.2.0, 
> 4.9.3.0
> XenServer 6.5
> Primary Storage NFS and ISCSI
> Fresh install running 4.5.2.2, 4.9.2.0, 4.9.3.0 and 4.10
>Reporter: Marcelo Lima
>Assignee: Rafael Weingärtner
>Priority: Critical
> Fix For: 4.11.0.0
>
>
> If we have two or more snapshots of a ROOT disk and try to create a template 
> from differencial snapshots, CloudStack not merging the vhd files on 
> secondary storage.
> Steps to reproduce
> 1. Create virtual machine - OK
> 2. Create a manual snapshot from ROOT volume - OK
> The vhd of first snapshot (snapshot-base) is stored on secondary storage 
> correctly
> [root@acs01 6]# ls -l 
> /exports/secondary/snapshots/2/6/011a7650-a13f-4332-8c72-2428a002affc.vhd 
> -rw-r--r-- 1 root root 1767191040 Nov  1 12:12 
> /exports/secondary/snapshots/2/6/011a7650-a13f-4332-8c72-2428a002affc.vhd
> [root@acs01 6]# md5sum 
> /exports/secondary/snapshots/2/6/011a7650-a13f-4332-8c72-2428a002affc.vhd 
> 
> 240e5e424552d44b5d297895b064beee  
> /exports/secondary/snapshots/2/6/011a7650-a13f-4332-8c72-2428a002affc.vhd
> 3. Create a template from snapshot-base - OK
> [root@acs01 6]# ls -l 
> /exports/secondary/template/tmpl/2/206/be3311d9-8e59-4240-968d-73d7a6eecfdd.vhd
>  
> -rw-r--r-- 1 root root 1767191040 Nov  1 12:17 
> /exports/secondary/template/tmpl/2/206/be3311d9-8e59-4240-968d-73d7a6eecfdd.vhd
> [root@acs01 6]# md5sum 
> /exports/secondary/template/tmpl/2/206/be3311d9-8e59-4240-968d-73d7a6eecfdd.vhd
>   
> 240e5e424552d44b5d297895b064beee  
> /exports/secondary/template/tmpl/2/206/be3311d9-8e59-4240-968d-73d7a6eecfdd.vhd
> This template from snapshot-base boot normally
> 4. Create new file (1GB) on ROOT volume
> 5. Create new snapshot (snapshot-diff) from ROOT volume - OK
> [root@acs01 6]# ls -l /exports/secondary/snapshots/2/6/ 
> total 2840056
> -rw-r--r-- 1 root root 1767191040 Nov  1 12:12 
> 011a7650-a13f-4332-8c72-2428a002affc.vhd <- snapshot-base
> -rw-r--r-- 1 root root 1141019136 Nov  1 12:21 
> 1503adaa-4f6e-4f9c-8d80-68663baa86b8.vhd <- snapshot-diff
> 6. Create a template from second snapshot - NOK
> [root@acs01 6]# ls -lh 
> /exports/secondary/template/tmpl/2/207/4c5c51a1-fcb4-4cc8-8f97-1664a63af262.vhd
>  
> -rw-r--r-- 1 root root 1141019136 Nov  1 12:30 
> /exports/secondary/template/tmpl/2/207/4c5c51a1-fcb4-4cc8-8f97-1664a63af262.vhd
> CloudStack not merging snapshot-base and snapshot-diff. Template from second 
> snapshot is corrupted because is based just on differential vhd.
> Volume from snapshot work very well
> 1. Create a volume from snapshot-diff - OK
> CloudStack merge two snapshots in one file
> [root@acs01 primary]# ls -l 
> /exports/primary/70f1db23-cc59-4ec7-b8d4-ed036228593b.vhd 
> -rw-r--r-- 1 root root 2843030016 Nov  1 12:34 
> /exports/primary/70f1db23-cc59-4ec7-b8d4-ed036228593b.vhd
> 2. Download the new volume to check vhd on secondary storage
> [root@acs01 9]# ls -l 
> /exports/secondary/volumes/2/9/ec6e0f65-bb71-4c91-bac3-287cde2106b7.vhd 
> -rw-r--r-- 1 root root 2843030016 Nov  1 12:35 
> /exports/secondary/volumes/2/9/ec6e0f65-bb71-4c91-bac3-287cde2106b7.vhd
> We test on 4.5.2.2, 4.9.2.0, 4.9.3.0 and 4.10. XenServer 6.5 with SP1 and 
> XenServer 6.5 with all patches.
> A workaround is create a volume (data-disk) from latest snapshot, create new 
> snapshot from data-disk and convert to template.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10217) When IPv4 address of Instance is updated DHCP data is not cleared on VR

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316153#comment-16316153
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10217:
-

wido commented on issue #2393: CLOUDSTACK-10217: Clean up old MAC addresses 
from DHCP lease file
URL: https://github.com/apache/cloudstack/pull/2393#issuecomment-355944186
 
 
   I understand your comment @DaanHoogland , but I have no idea on how to test 
this :)
   
   We ran into this issue combined with #2388 and then needed to fix this in 
the Python code, this is what it resulted in.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> When IPv4 address of Instance is updated DHCP data is not cleared on VR
> ---
>
> Key: CLOUDSTACK-10217
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10217
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.10.0.0
> Environment: Basic Networking - KVM
>Reporter: Wido den Hollander
>Assignee: Wido den Hollander
>  Labels: basic-networking, dhcp, virtual-router
> Fix For: 4.11.0.0
>
>
> When the IPv4 address of a NIC is changed the new entry is added to the DHCP 
> lease file in the Virtual Router, but the old entry (with the same MAC) is 
> not removed and this causes the Instance to still receive the old address.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10213) Allow specify SSH key lengh

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316152#comment-16316152
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10213:
-

blueorangutan commented on issue #2389: CLOUDSTACK-10213: Allow specify SSH key 
lengh
URL: https://github.com/apache/cloudstack/pull/2389#issuecomment-355944006
 
 
   @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted 
as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Allow specify SSH key lengh
> ---
>
> Key: CLOUDSTACK-10213
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10213
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Dmytro Shevchenko
>
> SSH keys generated by the ACS are only 1024 bit (RSA). The common standard is 
> now at least 2048 bit.
> decompiled com.jcraft.jsch.KeyPair:
> {code:java}
> public static KeyPair genKeyPair(JSch jsch, int type) throws 
> JSchException {
> return genKeyPair(jsch, type, 1024);
> }
> public static KeyPair genKeyPair(JSch jsch, int type, int key_size) 
> throws JSchException {
> KeyPair kpair = null;
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10213) Allow specify SSH key lengh

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316149#comment-16316149
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10213:
-

rhtyd commented on issue #2389: CLOUDSTACK-10213: Allow specify SSH key lengh
URL: https://github.com/apache/cloudstack/pull/2389#issuecomment-355943823
 
 
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Allow specify SSH key lengh
> ---
>
> Key: CLOUDSTACK-10213
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10213
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Dmytro Shevchenko
>
> SSH keys generated by the ACS are only 1024 bit (RSA). The common standard is 
> now at least 2048 bit.
> decompiled com.jcraft.jsch.KeyPair:
> {code:java}
> public static KeyPair genKeyPair(JSch jsch, int type) throws 
> JSchException {
> return genKeyPair(jsch, type, 1024);
> }
> public static KeyPair genKeyPair(JSch jsch, int type, int key_size) 
> throws JSchException {
> KeyPair kpair = null;
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10217) When IPv4 address of Instance is updated DHCP data is not cleared on VR

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316147#comment-16316147
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10217:
-

blueorangutan commented on issue #2393: CLOUDSTACK-10217: Clean up old MAC 
addresses from DHCP lease file
URL: https://github.com/apache/cloudstack/pull/2393#issuecomment-355943805
 
 
   @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted 
as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> When IPv4 address of Instance is updated DHCP data is not cleared on VR
> ---
>
> Key: CLOUDSTACK-10217
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10217
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.10.0.0
> Environment: Basic Networking - KVM
>Reporter: Wido den Hollander
>Assignee: Wido den Hollander
>  Labels: basic-networking, dhcp, virtual-router
> Fix For: 4.11.0.0
>
>
> When the IPv4 address of a NIC is changed the new entry is added to the DHCP 
> lease file in the Virtual Router, but the old entry (with the same MAC) is 
> not removed and this causes the Instance to still receive the old address.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10217) When IPv4 address of Instance is updated DHCP data is not cleared on VR

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316145#comment-16316145
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10217:
-

rhtyd commented on issue #2393: CLOUDSTACK-10217: Clean up old MAC addresses 
from DHCP lease file
URL: https://github.com/apache/cloudstack/pull/2393#issuecomment-355943582
 
 
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> When IPv4 address of Instance is updated DHCP data is not cleared on VR
> ---
>
> Key: CLOUDSTACK-10217
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10217
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.10.0.0
> Environment: Basic Networking - KVM
>Reporter: Wido den Hollander
>Assignee: Wido den Hollander
>  Labels: basic-networking, dhcp, virtual-router
> Fix For: 4.11.0.0
>
>
> When the IPv4 address of a NIC is changed the new entry is added to the DHCP 
> lease file in the Virtual Router, but the old entry (with the same MAC) is 
> not removed and this causes the Instance to still receive the old address.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9885) VPC RVR: On deleting first tier and configuring Private GW both VRs becoming MASTER

[Rohit Yadav (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316142#comment-16316142
 ] 

Rohit Yadav commented on CLOUDSTACK-9885:
-

Lowered to "Critical" as it's not a blocker, blocking the release but a corner 
and specific case.

> VPC RVR: On deleting first tier and configuring Private GW  both VRs becoming 
> MASTER
> 
>
> Key: CLOUDSTACK-9885
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9885
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.10.0.0
>Reporter: Jayapal Reddy
>Assignee: Jayapal Reddy
>Priority: Critical
> Fix For: 4.10.1.0
>
>
> - Configure two tier networks t1 and t2. Delete the t1 network. Both VRs are 
> getting  into MASTER state.
> r-269-QA - was BACKUP VR. On deleting t1 network it became MASTER.
> {noformat}
> root@r-269-QA:~# ip a
> 1: lo:  mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> 2: eth0:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 0e:00:a9:fe:01:dc brd ff:ff:ff:ff:ff:ff
> inet 169.254.1.220/16 brd 169.254.255.255 scope global eth0
> 3: eth1:  mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
> link/ether 06:e4:c8:00:00:0e brd ff:ff:ff:ff:ff:ff
> inet 10.147.46.102/24 brd 10.147.46.255 scope global eth1
> 4: eth2:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:5d:a4:00:03 brd ff:ff:ff:ff:ff:ff
> inet 10.1.1.33/24 brd 10.1.1.255 scope global eth2
> 5: eth3:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 06:de:fc:00:00:29 brd ff:ff:ff:ff:ff:ff
> inet 10.147.52.200/24 brd 10.147.52.255 scope global eth3
> 6: eth4:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:31:e1:00:03 brd ff:ff:ff:ff:ff:ff
> inet 10.1.2.78/24 brd 10.1.2.255 scope global eth4
> root@r-269-QA:~#
> root@r-269-QA:~# ip a
> 1: lo:  mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> 2: eth0:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 0e:00:a9:fe:01:dc brd ff:ff:ff:ff:ff:ff
> inet 169.254.1.220/16 brd 169.254.255.255 scope global eth0
> 3: eth1:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 06:e4:c8:00:00:0e brd ff:ff:ff:ff:ff:ff
> inet 10.147.46.102/24 brd 10.147.46.255 scope global eth1
> 5: eth3:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 06:de:fc:00:00:29 brd ff:ff:ff:ff:ff:ff
> inet 10.147.52.200/24 brd 10.147.52.255 scope global eth3
> inet 10.147.52.100/24 brd 10.147.52.255 scope global secondary eth3
> 6: eth4:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:31:e1:00:03 brd ff:ff:ff:ff:ff:ff
> inet 10.1.2.78/24 brd 10.1.2.255 scope global eth4
> inet 10.1.2.1/24 brd 10.1.2.255 scope global secondary eth4
> root@r-269-QA:~# checkrouter.sh
> Status: MASTER
> root@r-269-QA:~#
> {noformat}
> root@r-268-QA - was MASTER VR. On deleting t1 it deleted its eth2 interface 
> and delete 10.2.1.1 ip on ethic interface.
>After some time it configured 10.2.1.1 ip on eth4 and it became master.
> {noformat}
> root@r-268-QA:~# ip a
> 1: lo:  mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> 2: eth0:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 0e:00:a9:fe:02:ac brd ff:ff:ff:ff:ff:ff
> inet 169.254.2.172/16 brd 169.254.255.255 scope global eth0
> 3: eth1:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 06:e4:c8:00:00:0e brd ff:ff:ff:ff:ff:ff
> inet 10.147.46.102/24 brd 10.147.46.255 scope global eth1
> 4: eth2:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:15:ab:00:02 brd ff:ff:ff:ff:ff:ff
> inet 10.1.1.189/24 brd 10.1.1.255 scope global eth2
> inet 10.1.1.1/24 brd 10.1.1.255 scope global secondary eth2
> 5: eth3:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 06:67:ce:00:00:29 brd ff:ff:ff:ff:ff:ff
> inet 10.147.52.200/24 brd 10.147.52.255 scope global eth3

[jira] [Updated] (CLOUDSTACK-9885) VPC RVR: On deleting first tier and configuring Private GW both VRs becoming MASTER

[Rohit Yadav (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rohit Yadav updated CLOUDSTACK-9885:

Priority: Critical  (was: Blocker)

> VPC RVR: On deleting first tier and configuring Private GW  both VRs becoming 
> MASTER
> 
>
> Key: CLOUDSTACK-9885
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9885
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.10.0.0
>Reporter: Jayapal Reddy
>Assignee: Jayapal Reddy
>Priority: Critical
> Fix For: 4.10.1.0
>
>
> - Configure two tier networks t1 and t2. Delete the t1 network. Both VRs are 
> getting  into MASTER state.
> r-269-QA - was BACKUP VR. On deleting t1 network it became MASTER.
> {noformat}
> root@r-269-QA:~# ip a
> 1: lo:  mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> 2: eth0:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 0e:00:a9:fe:01:dc brd ff:ff:ff:ff:ff:ff
> inet 169.254.1.220/16 brd 169.254.255.255 scope global eth0
> 3: eth1:  mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
> link/ether 06:e4:c8:00:00:0e brd ff:ff:ff:ff:ff:ff
> inet 10.147.46.102/24 brd 10.147.46.255 scope global eth1
> 4: eth2:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:5d:a4:00:03 brd ff:ff:ff:ff:ff:ff
> inet 10.1.1.33/24 brd 10.1.1.255 scope global eth2
> 5: eth3:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 06:de:fc:00:00:29 brd ff:ff:ff:ff:ff:ff
> inet 10.147.52.200/24 brd 10.147.52.255 scope global eth3
> 6: eth4:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:31:e1:00:03 brd ff:ff:ff:ff:ff:ff
> inet 10.1.2.78/24 brd 10.1.2.255 scope global eth4
> root@r-269-QA:~#
> root@r-269-QA:~# ip a
> 1: lo:  mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> 2: eth0:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 0e:00:a9:fe:01:dc brd ff:ff:ff:ff:ff:ff
> inet 169.254.1.220/16 brd 169.254.255.255 scope global eth0
> 3: eth1:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 06:e4:c8:00:00:0e brd ff:ff:ff:ff:ff:ff
> inet 10.147.46.102/24 brd 10.147.46.255 scope global eth1
> 5: eth3:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 06:de:fc:00:00:29 brd ff:ff:ff:ff:ff:ff
> inet 10.147.52.200/24 brd 10.147.52.255 scope global eth3
> inet 10.147.52.100/24 brd 10.147.52.255 scope global secondary eth3
> 6: eth4:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:31:e1:00:03 brd ff:ff:ff:ff:ff:ff
> inet 10.1.2.78/24 brd 10.1.2.255 scope global eth4
> inet 10.1.2.1/24 brd 10.1.2.255 scope global secondary eth4
> root@r-269-QA:~# checkrouter.sh
> Status: MASTER
> root@r-269-QA:~#
> {noformat}
> root@r-268-QA - was MASTER VR. On deleting t1 it deleted its eth2 interface 
> and delete 10.2.1.1 ip on ethic interface.
>After some time it configured 10.2.1.1 ip on eth4 and it became master.
> {noformat}
> root@r-268-QA:~# ip a
> 1: lo:  mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> 2: eth0:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 0e:00:a9:fe:02:ac brd ff:ff:ff:ff:ff:ff
> inet 169.254.2.172/16 brd 169.254.255.255 scope global eth0
> 3: eth1:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 06:e4:c8:00:00:0e brd ff:ff:ff:ff:ff:ff
> inet 10.147.46.102/24 brd 10.147.46.255 scope global eth1
> 4: eth2:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:15:ab:00:02 brd ff:ff:ff:ff:ff:ff
> inet 10.1.1.189/24 brd 10.1.1.255 scope global eth2
> inet 10.1.1.1/24 brd 10.1.1.255 scope global secondary eth2
> 5: eth3:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 06:67:ce:00:00:29 brd ff:ff:ff:ff:ff:ff
> inet 10.147.52.200/24 brd 10.147.52.255 scope global eth3
> inet 10.147.52.100/24 brd 10.147.52.255 scope global secondary eth3
> 6: eth4: 

[jira] [Created] (CLOUDSTACK-10218) forced network update to a nuage network offering with vr fails with IllegalArgumentException

[Raf Smeets (JIRA)]

Raf Smeets created CLOUDSTACK-10218:
---

 Summary: forced network update to a nuage network offering with vr 
fails with IllegalArgumentException
 Key: CLOUDSTACK-10218
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10218
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server, Network Controller
Affects Versions: 4.11.0.0
 Environment: NuageVSP
Reporter: Raf Smeets
 Attachments: configdrivemanagement-server.log

a forced network update from a nuage network offering without vr to a nuage 
network offering with vr fails with  java.lang.IllegalArgumentException
Message: 'null' is not an IP string literal.
It looks like this issue was introduced by recalculate broadcasturi introduced 
by the network migration PR. Cause: VspNetwork.getVirtualRouterIp() == "null" 
NuageVspElement:287

Scenario to reproduce:
update network id  networkofferingid  
forced=true
In failing test , existing network offering is one withoutVR, 
newnetworkoffering is one with VR as DNS requires VR.

The exception reported in cloudstack is : java.lang.IllegalArgumentException
Message: 'null' is not an IP string literal.
Full cloudstack management server logs are attached.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10213) Allow specify SSH key lengh

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316027#comment-16316027
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10213:
-

dmytro-shevchenko commented on issue #2389: CLOUDSTACK-10213: Allow specify SSH 
key lengh
URL: https://github.com/apache/cloudstack/pull/2389#issuecomment-355928022
 
 
   Reasonable, PR updated. Global scope for variable, description a little bit 
updated. This can be only exactly key length, not minimal.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Allow specify SSH key lengh
> ---
>
> Key: CLOUDSTACK-10213
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10213
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Dmytro Shevchenko
>
> SSH keys generated by the ACS are only 1024 bit (RSA). The common standard is 
> now at least 2048 bit.
> decompiled com.jcraft.jsch.KeyPair:
> {code:java}
> public static KeyPair genKeyPair(JSch jsch, int type) throws 
> JSchException {
> return genKeyPair(jsch, type, 1024);
> }
> public static KeyPair genKeyPair(JSch jsch, int type, int key_size) 
> throws JSchException {
> KeyPair kpair = null;
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10213) Allow specify SSH key lengh

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316016#comment-16316016
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10213:
-

bwsw commented on a change in pull request #2389: CLOUDSTACK-10213: Allow 
specify SSH key lengh
URL: https://github.com/apache/cloudstack/pull/2389#discussion_r160106621
 
 

 ##
 File path: utils/src/main/java/com/cloud/utils/ssh/SSHKeysHelper.java
 ##
 @@ -43,9 +43,9 @@ private static String toHexString(byte[] b) {
 return sb.toString();
 }
 
-public SSHKeysHelper() {
+public SSHKeysHelper(Integer keyLenght) {
 
 Review comment:
   It's a typo. ShouldBe keyLength.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Allow specify SSH key lengh
> ---
>
> Key: CLOUDSTACK-10213
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10213
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Dmytro Shevchenko
>
> SSH keys generated by the ACS are only 1024 bit (RSA). The common standard is 
> now at least 2048 bit.
> decompiled com.jcraft.jsch.KeyPair:
> {code:java}
> public static KeyPair genKeyPair(JSch jsch, int type) throws 
> JSchException {
> return genKeyPair(jsch, type, 1024);
> }
> public static KeyPair genKeyPair(JSch jsch, int type, int key_size) 
> throws JSchException {
> KeyPair kpair = null;
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10213) Allow specify SSH key lengh

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316015#comment-16316015
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10213:
-

bwsw commented on a change in pull request #2389: CLOUDSTACK-10213: Allow 
specify SSH key lengh
URL: https://github.com/apache/cloudstack/pull/2389#discussion_r160107085
 
 

 ##
 File path: server/src/com/cloud/server/ManagementServerImpl.java
 ##
 @@ -696,6 +696,8 @@
 
 static final ConfigKey vmPasswordLength = new 
ConfigKey("Advanced", Integer.class, "vm.password.length", "6",

   "Specifies the length of a randomly generated password", false);
+static final ConfigKey sshKeyLength = new 
ConfigKey("Advanced", Integer.class, "ssh.key.length",
+"2048", "User SSH key length (bit)", true, 
ConfigKey.Scope.Account);
 
 Review comment:
   Might the description be more meaningful for average user, like "Specifies 
minimal? amount of SSH key length permitted". Could you please take a look at 
this. May be it can be improved.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Allow specify SSH key lengh
> ---
>
> Key: CLOUDSTACK-10213
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10213
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Dmytro Shevchenko
>
> SSH keys generated by the ACS are only 1024 bit (RSA). The common standard is 
> now at least 2048 bit.
> decompiled com.jcraft.jsch.KeyPair:
> {code:java}
> public static KeyPair genKeyPair(JSch jsch, int type) throws 
> JSchException {
> return genKeyPair(jsch, type, 1024);
> }
> public static KeyPair genKeyPair(JSch jsch, int type, int key_size) 
> throws JSchException {
> KeyPair kpair = null;
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10213) Allow specify SSH key lengh

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316004#comment-16316004
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10213:
-

DaanHoogland commented on issue #2389: CLOUDSTACK-10213: Allow specify SSH key 
lengh
URL: https://github.com/apache/cloudstack/pull/2389#issuecomment-355925007
 
 
   Can you give a rationale as to why account scope, @dmytro-shevchenko ? 
Nowadays you can also use domain scope and for this even global would make 
sense.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Allow specify SSH key lengh
> ---
>
> Key: CLOUDSTACK-10213
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10213
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Dmytro Shevchenko
>
> SSH keys generated by the ACS are only 1024 bit (RSA). The common standard is 
> now at least 2048 bit.
> decompiled com.jcraft.jsch.KeyPair:
> {code:java}
> public static KeyPair genKeyPair(JSch jsch, int type) throws 
> JSchException {
> return genKeyPair(jsch, type, 1024);
> }
> public static KeyPair genKeyPair(JSch jsch, int type, int key_size) 
> throws JSchException {
> KeyPair kpair = null;
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10146) Bypass Secondary Storage for KVM templates

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316000#comment-16316000
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10146:
-

blueorangutan commented on issue #2379: CLOUDSTACK-10146: Bypass Secondary 
Storage for KVM templates
URL: https://github.com/apache/cloudstack/pull/2379#issuecomment-355924687
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1620


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bypass Secondary Storage for KVM templates
> --
>
> Key: CLOUDSTACK-10146
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10146
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CLOUDSTACK-10128) Template from snapshot not merging vhd files

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner updated CLOUDSTACK-10128:

Status: Reviewable  (was: In Progress)

> Template from snapshot not merging vhd files
> 
>
> Key: CLOUDSTACK-10128
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10128
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.10.0.0, 4.9.2.0, 4.5.2.2, 4.9.3.0
> Environment: Production environment running ACS 4.5.2.2, 4.9.2.0, 
> 4.9.3.0
> XenServer 6.5
> Primary Storage NFS and ISCSI
> Fresh install running 4.5.2.2, 4.9.2.0, 4.9.3.0 and 4.10
>Reporter: Marcelo Lima
>Assignee: Rafael Weingärtner
>Priority: Critical
> Fix For: 4.11.0.0
>
>
> If we have two or more snapshots of a ROOT disk and try to create a template 
> from differencial snapshots, CloudStack not merging the vhd files on 
> secondary storage.
> Steps to reproduce
> 1. Create virtual machine - OK
> 2. Create a manual snapshot from ROOT volume - OK
> The vhd of first snapshot (snapshot-base) is stored on secondary storage 
> correctly
> [root@acs01 6]# ls -l 
> /exports/secondary/snapshots/2/6/011a7650-a13f-4332-8c72-2428a002affc.vhd 
> -rw-r--r-- 1 root root 1767191040 Nov  1 12:12 
> /exports/secondary/snapshots/2/6/011a7650-a13f-4332-8c72-2428a002affc.vhd
> [root@acs01 6]# md5sum 
> /exports/secondary/snapshots/2/6/011a7650-a13f-4332-8c72-2428a002affc.vhd 
> 
> 240e5e424552d44b5d297895b064beee  
> /exports/secondary/snapshots/2/6/011a7650-a13f-4332-8c72-2428a002affc.vhd
> 3. Create a template from snapshot-base - OK
> [root@acs01 6]# ls -l 
> /exports/secondary/template/tmpl/2/206/be3311d9-8e59-4240-968d-73d7a6eecfdd.vhd
>  
> -rw-r--r-- 1 root root 1767191040 Nov  1 12:17 
> /exports/secondary/template/tmpl/2/206/be3311d9-8e59-4240-968d-73d7a6eecfdd.vhd
> [root@acs01 6]# md5sum 
> /exports/secondary/template/tmpl/2/206/be3311d9-8e59-4240-968d-73d7a6eecfdd.vhd
>   
> 240e5e424552d44b5d297895b064beee  
> /exports/secondary/template/tmpl/2/206/be3311d9-8e59-4240-968d-73d7a6eecfdd.vhd
> This template from snapshot-base boot normally
> 4. Create new file (1GB) on ROOT volume
> 5. Create new snapshot (snapshot-diff) from ROOT volume - OK
> [root@acs01 6]# ls -l /exports/secondary/snapshots/2/6/ 
> total 2840056
> -rw-r--r-- 1 root root 1767191040 Nov  1 12:12 
> 011a7650-a13f-4332-8c72-2428a002affc.vhd <- snapshot-base
> -rw-r--r-- 1 root root 1141019136 Nov  1 12:21 
> 1503adaa-4f6e-4f9c-8d80-68663baa86b8.vhd <- snapshot-diff
> 6. Create a template from second snapshot - NOK
> [root@acs01 6]# ls -lh 
> /exports/secondary/template/tmpl/2/207/4c5c51a1-fcb4-4cc8-8f97-1664a63af262.vhd
>  
> -rw-r--r-- 1 root root 1141019136 Nov  1 12:30 
> /exports/secondary/template/tmpl/2/207/4c5c51a1-fcb4-4cc8-8f97-1664a63af262.vhd
> CloudStack not merging snapshot-base and snapshot-diff. Template from second 
> snapshot is corrupted because is based just on differential vhd.
> Volume from snapshot work very well
> 1. Create a volume from snapshot-diff - OK
> CloudStack merge two snapshots in one file
> [root@acs01 primary]# ls -l 
> /exports/primary/70f1db23-cc59-4ec7-b8d4-ed036228593b.vhd 
> -rw-r--r-- 1 root root 2843030016 Nov  1 12:34 
> /exports/primary/70f1db23-cc59-4ec7-b8d4-ed036228593b.vhd
> 2. Download the new volume to check vhd on secondary storage
> [root@acs01 9]# ls -l 
> /exports/secondary/volumes/2/9/ec6e0f65-bb71-4c91-bac3-287cde2106b7.vhd 
> -rw-r--r-- 1 root root 2843030016 Nov  1 12:35 
> /exports/secondary/volumes/2/9/ec6e0f65-bb71-4c91-bac3-287cde2106b7.vhd
> We test on 4.5.2.2, 4.9.2.0, 4.9.3.0 and 4.10. XenServer 6.5 with SP1 and 
> XenServer 6.5 with all patches.
> A workaround is create a volume (data-disk) from latest snapshot, create new 
> snapshot from data-disk and convert to template.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CLOUDSTACK-10128) Template from snapshot not merging vhd files

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-10128.
-
   Resolution: Fixed
Fix Version/s: 4.11.0.0

> Template from snapshot not merging vhd files
> 
>
> Key: CLOUDSTACK-10128
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10128
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.10.0.0, 4.9.2.0, 4.5.2.2, 4.9.3.0
> Environment: Production environment running ACS 4.5.2.2, 4.9.2.0, 
> 4.9.3.0
> XenServer 6.5
> Primary Storage NFS and ISCSI
> Fresh install running 4.5.2.2, 4.9.2.0, 4.9.3.0 and 4.10
>Reporter: Marcelo Lima
>Assignee: Rafael Weingärtner
>Priority: Critical
> Fix For: 4.11.0.0
>
>
> If we have two or more snapshots of a ROOT disk and try to create a template 
> from differencial snapshots, CloudStack not merging the vhd files on 
> secondary storage.
> Steps to reproduce
> 1. Create virtual machine - OK
> 2. Create a manual snapshot from ROOT volume - OK
> The vhd of first snapshot (snapshot-base) is stored on secondary storage 
> correctly
> [root@acs01 6]# ls -l 
> /exports/secondary/snapshots/2/6/011a7650-a13f-4332-8c72-2428a002affc.vhd 
> -rw-r--r-- 1 root root 1767191040 Nov  1 12:12 
> /exports/secondary/snapshots/2/6/011a7650-a13f-4332-8c72-2428a002affc.vhd
> [root@acs01 6]# md5sum 
> /exports/secondary/snapshots/2/6/011a7650-a13f-4332-8c72-2428a002affc.vhd 
> 
> 240e5e424552d44b5d297895b064beee  
> /exports/secondary/snapshots/2/6/011a7650-a13f-4332-8c72-2428a002affc.vhd
> 3. Create a template from snapshot-base - OK
> [root@acs01 6]# ls -l 
> /exports/secondary/template/tmpl/2/206/be3311d9-8e59-4240-968d-73d7a6eecfdd.vhd
>  
> -rw-r--r-- 1 root root 1767191040 Nov  1 12:17 
> /exports/secondary/template/tmpl/2/206/be3311d9-8e59-4240-968d-73d7a6eecfdd.vhd
> [root@acs01 6]# md5sum 
> /exports/secondary/template/tmpl/2/206/be3311d9-8e59-4240-968d-73d7a6eecfdd.vhd
>   
> 240e5e424552d44b5d297895b064beee  
> /exports/secondary/template/tmpl/2/206/be3311d9-8e59-4240-968d-73d7a6eecfdd.vhd
> This template from snapshot-base boot normally
> 4. Create new file (1GB) on ROOT volume
> 5. Create new snapshot (snapshot-diff) from ROOT volume - OK
> [root@acs01 6]# ls -l /exports/secondary/snapshots/2/6/ 
> total 2840056
> -rw-r--r-- 1 root root 1767191040 Nov  1 12:12 
> 011a7650-a13f-4332-8c72-2428a002affc.vhd <- snapshot-base
> -rw-r--r-- 1 root root 1141019136 Nov  1 12:21 
> 1503adaa-4f6e-4f9c-8d80-68663baa86b8.vhd <- snapshot-diff
> 6. Create a template from second snapshot - NOK
> [root@acs01 6]# ls -lh 
> /exports/secondary/template/tmpl/2/207/4c5c51a1-fcb4-4cc8-8f97-1664a63af262.vhd
>  
> -rw-r--r-- 1 root root 1141019136 Nov  1 12:30 
> /exports/secondary/template/tmpl/2/207/4c5c51a1-fcb4-4cc8-8f97-1664a63af262.vhd
> CloudStack not merging snapshot-base and snapshot-diff. Template from second 
> snapshot is corrupted because is based just on differential vhd.
> Volume from snapshot work very well
> 1. Create a volume from snapshot-diff - OK
> CloudStack merge two snapshots in one file
> [root@acs01 primary]# ls -l 
> /exports/primary/70f1db23-cc59-4ec7-b8d4-ed036228593b.vhd 
> -rw-r--r-- 1 root root 2843030016 Nov  1 12:34 
> /exports/primary/70f1db23-cc59-4ec7-b8d4-ed036228593b.vhd
> 2. Download the new volume to check vhd on secondary storage
> [root@acs01 9]# ls -l 
> /exports/secondary/volumes/2/9/ec6e0f65-bb71-4c91-bac3-287cde2106b7.vhd 
> -rw-r--r-- 1 root root 2843030016 Nov  1 12:35 
> /exports/secondary/volumes/2/9/ec6e0f65-bb71-4c91-bac3-287cde2106b7.vhd
> We test on 4.5.2.2, 4.9.2.0, 4.9.3.0 and 4.10. XenServer 6.5 with SP1 and 
> XenServer 6.5 with all patches.
> A workaround is create a volume (data-disk) from latest snapshot, create new 
> snapshot from data-disk and convert to template.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10213) Allow specify SSH key lengh

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315981#comment-16315981
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10213:
-

dmytro-shevchenko commented on issue #2389: CLOUDSTACK-10213: Allow specify SSH 
key lengh
URL: https://github.com/apache/cloudstack/pull/2389#issuecomment-355922762
 
 
   PR updated, new style configuration methods used. Variable scope changed to 
"Account".


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Allow specify SSH key lengh
> ---
>
> Key: CLOUDSTACK-10213
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10213
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Dmytro Shevchenko
>
> SSH keys generated by the ACS are only 1024 bit (RSA). The common standard is 
> now at least 2048 bit.
> decompiled com.jcraft.jsch.KeyPair:
> {code:java}
> public static KeyPair genKeyPair(JSch jsch, int type) throws 
> JSchException {
> return genKeyPair(jsch, type, 1024);
> }
> public static KeyPair genKeyPair(JSch jsch, int type, int key_size) 
> throws JSchException {
> KeyPair kpair = null;
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10188) Resource Accounting for primary storage is Broken

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315958#comment-16315958
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10188:
-

blueorangutan commented on issue #2362: CLOUDSTACK-10188 - Resource Accounting 
for primary storage is Broken when Domains are in use
URL: https://github.com/apache/cloudstack/pull/2362#issuecomment-355920275
 
 
   @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has 
been kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Resource Accounting for primary storage is Broken
> -
>
> Key: CLOUDSTACK-10188
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10188
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.9.0, 4.10.0.0, 4.11.0.0
>Reporter: Ivan Kudryavtsev
>
> During storage expunge domain resource statistics for primary storage space 
> resource counter is not updated for domain. This leads to the situation when 
> domain resource statistics for primary storage is overfilled (statistics only 
> increase but not decrease).
> Global scheduled task resourcecount.check.interval > 0 provides a workaround 
> but not fixes the problem truly because when accounts inside domains use 
> primary_storage allocation/deallocation intensively it leads to service block 
> of operation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10188) Resource Accounting for primary storage is Broken

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315957#comment-16315957
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10188:
-

borisstoyanov commented on issue #2362: CLOUDSTACK-10188 - Resource Accounting 
for primary storage is Broken when Domains are in use
URL: https://github.com/apache/cloudstack/pull/2362#issuecomment-355920228
 
 
   @blueorangutan test


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Resource Accounting for primary storage is Broken
> -
>
> Key: CLOUDSTACK-10188
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10188
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.9.0, 4.10.0.0, 4.11.0.0
>Reporter: Ivan Kudryavtsev
>
> During storage expunge domain resource statistics for primary storage space 
> resource counter is not updated for domain. This leads to the situation when 
> domain resource statistics for primary storage is overfilled (statistics only 
> increase but not decrease).
> Global scheduled task resourcecount.check.interval > 0 provides a workaround 
> but not fixes the problem truly because when accounts inside domains use 
> primary_storage allocation/deallocation intensively it leads to service block 
> of operation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10217) When IPv4 address of Instance is updated DHCP data is not cleared on VR

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315959#comment-16315959
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10217:
-

wido opened a new pull request #2393: CLOUDSTACK-10217: Clean up old MAC 
addresses from DHCP lease file
URL: https://github.com/apache/cloudstack/pull/2393
 
 
   When the IPv4 address of a Instance changes we need to make sure the
   old entry is removed from the DHCP lease file on the Virtual Router
   otherwise the Instance will still get the old lease.
   
   Signed-off-by: Wido den Hollander 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> When IPv4 address of Instance is updated DHCP data is not cleared on VR
> ---
>
> Key: CLOUDSTACK-10217
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10217
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.10.0.0
> Environment: Basic Networking - KVM
>Reporter: Wido den Hollander
>Assignee: Wido den Hollander
>  Labels: basic-networking, dhcp, virtual-router
> Fix For: 4.11.0.0
>
>
> When the IPv4 address of a NIC is changed the new entry is added to the DHCP 
> lease file in the Virtual Router, but the old entry (with the same MAC) is 
> not removed and this causes the Instance to still receive the old address.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10188) Resource Accounting for primary storage is Broken

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315956#comment-16315956
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10188:
-

blueorangutan commented on issue #2362: CLOUDSTACK-10188 - Resource Accounting 
for primary storage is Broken when Domains are in use
URL: https://github.com/apache/cloudstack/pull/2362#issuecomment-355920084
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1619


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Resource Accounting for primary storage is Broken
> -
>
> Key: CLOUDSTACK-10188
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10188
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.9.0, 4.10.0.0, 4.11.0.0
>Reporter: Ivan Kudryavtsev
>
> During storage expunge domain resource statistics for primary storage space 
> resource counter is not updated for domain. This leads to the situation when 
> domain resource statistics for primary storage is overfilled (statistics only 
> increase but not decrease).
> Global scheduled task resourcecount.check.interval > 0 provides a workaround 
> but not fixes the problem truly because when accounts inside domains use 
> primary_storage allocation/deallocation intensively it leads to service block 
> of operation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315892#comment-16315892
 ] 

ASF GitHub Bot commented on CLOUDSTACK-4757:


rhtyd commented on a change in pull request #2146: CLOUDSTACK-4757: Support OVA 
files with multiple disks for templates
URL: https://github.com/apache/cloudstack/pull/2146#discussion_r160093366
 
 

 ##
 File path: 
engine/storage/image/src/org/apache/cloudstack/storage/image/TemplateServiceImpl.java
 ##
 @@ -691,6 +723,151 @@ protected Void 
createTemplateCallback(AsyncCallbackDispatcher dataDiskTemplates = new ArrayList();
+ImageStoreEntity tmpltStore = 
(ImageStoreEntity)parentTemplate.getDataStore();
+dataDiskTemplates = tmpltStore.getDataDiskTemplates(parentTemplate);
+s_logger.error("MDOVA createDataDiskTemplates Found " + 
dataDiskTemplates.size() + " Datadisk template(s) for template: " + 
parentTemplate.getId());
+int diskCount = 0;
+VMTemplateVO templateVO = 
_templateDao.findById(parentTemplate.getId());
+DataStore imageStore = parentTemplate.getDataStore();
+Map details = new HashMap();
+for (DatadiskTO diskTemplate : dataDiskTemplates) {
+if (!diskTemplate.isBootable()) {
+createChildDataDiskTemplate(diskTemplate, templateVO, 
parentTemplate, imageStore, diskCount++);
+if (!diskTemplate.isIso() && 
details.get(VmDetailConstants.DATA_DISK_CONTROLLER) == null){
+details.put(VmDetailConstants.DATA_DISK_CONTROLLER, 
getDiskControllerDetails(diskTemplate));
+details.put(VmDetailConstants.DATA_DISK_CONTROLLER + 
diskTemplate.getDiskId(), getDiskControllerDetails(diskTemplate));
+}
+} else {
+finalizeParentTemplate(diskTemplate, templateVO, 
parentTemplate, imageStore, diskCount++);
+details.put(VmDetailConstants.ROOT_DISK_CONTROLLER, 
getDiskControllerDetails(diskTemplate));
+}
+}
+templateVO.setDetails(details);
+_templateDao.saveDetails(templateVO);
+return true;
+}
+
+private boolean createChildDataDiskTemplate(DatadiskTO dataDiskTemplate, 
VMTemplateVO template, TemplateInfo parentTemplate, DataStore imageStore, int 
diskCount) {
+// Make an entry in vm_template table
+Storage.ImageFormat format = dataDiskTemplate.isIso() ? 
Storage.ImageFormat.ISO : template.getFormat();
+String suffix = dataDiskTemplate.isIso() ? "-IsoDiskTemplate-" : 
"-DataDiskTemplate-";
+TemplateType ttype = dataDiskTemplate.isIso() ? TemplateType.ISODISK : 
TemplateType.DATADISK;
+final long templateId = _templateDao.getNextInSequence(Long.class, 
"id");
+long guestOsId = dataDiskTemplate.isIso() ? 1 : 0;
+String templateName = dataDiskTemplate.isIso() ? 
dataDiskTemplate.getPath().substring(dataDiskTemplate.getPath().lastIndexOf(File.separator)
 + 1) : template.getName() + suffix + diskCount;
+VMTemplateVO templateVO = new VMTemplateVO(templateId, templateName, 
format, false, false, false, ttype, template.getUrl(),
+template.requiresHvm(), template.getBits(), 
template.getAccountId(), null, templateName, false, guestOsId, false, 
template.getHypervisorType(), null,
+null, false, false);
+if (dataDiskTemplate.isIso()){
+templateVO.setUniqueName(templateName);
+}
+templateVO.setParentTemplateId(template.getId());
+templateVO.setSize(dataDiskTemplate.getVirtualSize());
+templateVO = _templateDao.persist(templateVO);
+// Make sync call to create Datadisk templates in image store
+TemplateApiResult result = null;
+TemplateInfo dataDiskTemplateInfo = 
imageFactory.getTemplate(templateVO.getId(), imageStore);
+AsyncCallFuture future = 
createDatadiskTemplateAsync(parentTemplate, dataDiskTemplateInfo, 
dataDiskTemplate.getPath(), dataDiskTemplate.getDiskId(),
+dataDiskTemplate.getFileSize(), dataDiskTemplate.isBootable());
+try {
+result = future.get();
+if (result.isSuccess()) {
+// Make an entry in template_zone_ref table
+if (imageStore.getScope().getScopeType() == ScopeType.REGION) {
+associateTemplateToZone(templateId, null);
+} else if (imageStore.getScope().getScopeType() == 
ScopeType.ZONE) {
+Long zoneId = 
((ImageStoreEntity)imageStore).getDataCenterId();
+VMTemplateZoneVO templateZone = new 
VMTemplateZoneVO(zoneId, templateId, new Date());
+_vmTemplateZoneDao.persist(templateZone);
+}
+
_resourceLimitMgr.incrementResourceCount(template.getAccountId(), 

[jira] [Commented] (CLOUDSTACK-10213) Allow specify SSH key lengh

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315944#comment-16315944
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10213:
-

DaanHoogland commented on a change in pull request #2389: CLOUDSTACK-10213: 
Allow specify SSH key lengh
URL: https://github.com/apache/cloudstack/pull/2389#discussion_r159922500
 
 

 ##
 File path: server/src/com/cloud/server/ManagementServerImpl.java
 ##
 @@ -696,6 +696,8 @@
 
 static final ConfigKey vmPasswordLength = new 
ConfigKey("Advanced", Integer.class, "vm.password.length", "6",

   "Specifies the length of a randomly generated password", false);
+static final ConfigKey SSHKeyLength = new 
ConfigKey("Advanced", Integer.class, "ssh.key.length",
 
 Review comment:
   This configkey must be published in a getConfigKeys() implementation
 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Allow specify SSH key lengh
> ---
>
> Key: CLOUDSTACK-10213
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10213
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Dmytro Shevchenko
>
> SSH keys generated by the ACS are only 1024 bit (RSA). The common standard is 
> now at least 2048 bit.
> decompiled com.jcraft.jsch.KeyPair:
> {code:java}
> public static KeyPair genKeyPair(JSch jsch, int type) throws 
> JSchException {
> return genKeyPair(jsch, type, 1024);
> }
> public static KeyPair genKeyPair(JSch jsch, int type, int key_size) 
> throws JSchException {
> KeyPair kpair = null;
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-10146) Bypass Secondary Storage for KVM templates

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315942#comment-16315942
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10146:
-

blueorangutan commented on issue #2379: CLOUDSTACK-10146: Bypass Secondary 
Storage for KVM templates
URL: https://github.com/apache/cloudstack/pull/2379#issuecomment-355918590
 
 
   @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep 
you posted as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bypass Secondary Storage for KVM templates
> --
>
> Key: CLOUDSTACK-10146
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10146
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)