[jira] [Commented] (CLOUDSTACK-4816) provide configurable option to choose single vs multipart upload to S3 object storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786842#comment-13786842 ] ASF subversion and git services commented on CLOUDSTACK-4816: - Commit f1895ea39ae590ed7ff423649420659650b9853f in branch refs/heads/master from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f1895ea ] CLOUDSTACK-4816: Make S3 upload multipart or singlepart configurable. > provide configurable option to choose single vs multipart upload to S3 object > storage > -- > > Key: CLOUDSTACK-4816 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4816 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 >Reporter: Min Chen >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.1 > > > In 4.2, we only supports multipart upload for registering templates and > uploading volumes to object storage in secondary storage. The value of > multi-part is for network failure and throughput when you are going to a > remote storage. But with local storage (local to the DC) customers may prefer > single upload. Also, for templates you know the full size of the object > upfront and don't really need a multipart upload. > Some object storage vendors may prefer that this can be configured. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-3101) [DR] list* APIs are not working based on the display* flags
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786839#comment-13786839 ] ASF subversion and git services commented on CLOUDSTACK-3101: - Commit a6852a340d08845ae41833814d07771ec75cbf36 in branch refs/heads/master from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a6852a3 ] CLOUDSTACK-3101: fix listDiskOffering to not display offerings to the normal users with forDisplay=false. But display them to ROOT Admin irrespective of the flag. Added display flag in the updateVolume/offeirng commands Signed off by : nitin mehta > [DR] list* APIs are not working based on the display* flags > > > Key: CLOUDSTACK-3101 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3101 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 > Environment: commit # 971c40d98e07ab6cddb8e6db5095c1acea935815 >Reporter: venkata swamybabu budumuru >Assignee: Nitin Mehta >Priority: Minor > Fix For: 4.2.1 > > Attachments: logs.tgz > > > Steps to reproduce : > (i) Have CloudStack setup with at least 1 advanced zone > (ii) verify the listAPIs like (listVirtualMachines, listNetworks, listVolumes > etc..,) with the display flag set to true or false (displayvm or display > network) > for ex: > http://10.147.59.194:8096/api?command=listNetworks&displaynetwork=false > Observations: > (i) irrespective what is the value set for display flag, it lists all the > networks (or entities). > (ii) this doesn't do any filtering before listing based on the display flag > set. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-4817) Backup snapshot on Xen should take global setting s3.multipart.enabled.
Min Chen created CLOUDSTACK-4817: Summary: Backup snapshot on Xen should take global setting s3.multipart.enabled. Key: CLOUDSTACK-4817 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4817 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.2.0 Environment: XenServer Reporter: Min Chen Fix For: 4.2.1 Currently backsnapshot to S3 on Xen only used single part upload in s3xen plugin code, which will result in failure in case of snapshot is > 5GB. We need that plugin code to check the configuration setting s3.multipart.enabled to choose multipart or singlepart upload. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CLOUDSTACK-4817) Backup snapshot on Xen should take global setting s3.multipart.enabled.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Min Chen reassigned CLOUDSTACK-4817: Assignee: edison su > Backup snapshot on Xen should take global setting s3.multipart.enabled. > --- > > Key: CLOUDSTACK-4817 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4817 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 > Environment: XenServer >Reporter: Min Chen >Assignee: edison su > Fix For: 4.2.1 > > > Currently backsnapshot to S3 on Xen only used single part upload in s3xen > plugin code, which will result in failure in case of snapshot is > 5GB. We > need that plugin code to check the configuration setting s3.multipart.enabled > to choose multipart or singlepart upload. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-4816) provide configurable option to choose single vs multipart upload to S3 object storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Min Chen resolved CLOUDSTACK-4816. -- Resolution: Fixed > provide configurable option to choose single vs multipart upload to S3 object > storage > -- > > Key: CLOUDSTACK-4816 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4816 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 >Reporter: Min Chen >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.1 > > > In 4.2, we only supports multipart upload for registering templates and > uploading volumes to object storage in secondary storage. The value of > multi-part is for network failure and throughput when you are going to a > remote storage. But with local storage (local to the DC) customers may prefer > single upload. Also, for templates you know the full size of the object > upfront and don't really need a multipart upload. > Some object storage vendors may prefer that this can be configured. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4816) provide configurable option to choose single vs multipart upload to S3 object storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786809#comment-13786809 ] ASF subversion and git services commented on CLOUDSTACK-4816: - Commit 975422a9500f17c5b595e8c4c6075b3b49463337 in branch refs/heads/4.2 from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=975422a ] CLOUDSTACK-4816: Make S3 upload multipart or singlepart configurable. > provide configurable option to choose single vs multipart upload to S3 object > storage > -- > > Key: CLOUDSTACK-4816 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4816 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 >Reporter: Min Chen >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.1 > > > In 4.2, we only supports multipart upload for registering templates and > uploading volumes to object storage in secondary storage. The value of > multi-part is for network failure and throughput when you are going to a > remote storage. But with local storage (local to the DC) customers may prefer > single upload. Also, for templates you know the full size of the object > upfront and don't really need a multipart upload. > Some object storage vendors may prefer that this can be configured. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4816) provide configurable option to choose single vs multipart upload to S3 object storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786810#comment-13786810 ] ASF subversion and git services commented on CLOUDSTACK-4816: - Commit b63270f1d355458e9f5f2543d4320c5c832c41fe in branch refs/heads/4.2 from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b63270f ] CLOUDSTACK-4816: Add global configure s3.multipart.enabled > provide configurable option to choose single vs multipart upload to S3 object > storage > -- > > Key: CLOUDSTACK-4816 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4816 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 >Reporter: Min Chen >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.1 > > > In 4.2, we only supports multipart upload for registering templates and > uploading volumes to object storage in secondary storage. The value of > multi-part is for network failure and throughput when you are going to a > remote storage. But with local storage (local to the DC) customers may prefer > single upload. Also, for templates you know the full size of the object > upfront and don't really need a multipart upload. > Some object storage vendors may prefer that this can be configured. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-4816) provide configurable option to choose single vs multipart upload to S3 object storage
Min Chen created CLOUDSTACK-4816: Summary: provide configurable option to choose single vs multipart upload to S3 object storage Key: CLOUDSTACK-4816 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4816 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.2.0 Reporter: Min Chen Priority: Critical Fix For: 4.2.1 In 4.2, we only supports multipart upload for registering templates and uploading volumes to object storage in secondary storage. The value of multi-part is for network failure and throughput when you are going to a remote storage. But with local storage (local to the DC) customers may prefer single upload. Also, for templates you know the full size of the object upfront and don't really need a multipart upload. Some object storage vendors may prefer that this can be configured. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CLOUDSTACK-4816) provide configurable option to choose single vs multipart upload to S3 object storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Min Chen reassigned CLOUDSTACK-4816: Assignee: Min Chen > provide configurable option to choose single vs multipart upload to S3 object > storage > -- > > Key: CLOUDSTACK-4816 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4816 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 >Reporter: Min Chen >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.1 > > > In 4.2, we only supports multipart upload for registering templates and > uploading volumes to object storage in secondary storage. The value of > multi-part is for network failure and throughput when you are going to a > remote storage. But with local storage (local to the DC) customers may prefer > single upload. Also, for templates you know the full size of the object > upfront and don't really need a multipart upload. > Some object storage vendors may prefer that this can be configured. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-3101) [DR] list* APIs are not working based on the display* flags
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786741#comment-13786741 ] ASF subversion and git services commented on CLOUDSTACK-3101: - Commit f8976a41ce81d289709cd104acac82228536177f in branch refs/heads/master from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f8976a4 ] CLOUDSTACK-3101: fix listVolumes to not display volumes to the normal users with forDisplay=false. But display volumes to ROOT Admin irrespective of the flag. Signed off by : nitin mehta > [DR] list* APIs are not working based on the display* flags > > > Key: CLOUDSTACK-3101 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3101 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 > Environment: commit # 971c40d98e07ab6cddb8e6db5095c1acea935815 >Reporter: venkata swamybabu budumuru >Assignee: Nitin Mehta >Priority: Minor > Fix For: 4.2.1 > > Attachments: logs.tgz > > > Steps to reproduce : > (i) Have CloudStack setup with at least 1 advanced zone > (ii) verify the listAPIs like (listVirtualMachines, listNetworks, listVolumes > etc..,) with the display flag set to true or false (displayvm or display > network) > for ex: > http://10.147.59.194:8096/api?command=listNetworks&displaynetwork=false > Observations: > (i) irrespective what is the value set for display flag, it lists all the > networks (or entities). > (ii) this doesn't do any filtering before listing based on the display flag > set. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4802) [VMware] Unable to start VM if VM has VM snapshot been taken in vSphere version 5.0 Update 2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786738#comment-13786738 ] ASF subversion and git services commented on CLOUDSTACK-4802: - Commit 16b022b1b1e9bf97420ed4110244d8c9a9601a49 in branch refs/heads/master from [~kelveny] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=16b022b ] CLOUDSTACK-4802: Change VM start flow to better support VM snapshot on certian version of vSphere, (vSphere 5.0 Update 2). If we detect that VM has pending VM snapshot, we will fully honor VM disk info from vCenter, since in some version of vSphere (vSphere 5.0 U2) does not allow disk-editting when VM has pending snapshot. > [VMware] Unable to start VM if VM has VM snapshot been taken in vSphere > version 5.0 Update 2 > > > Key: CLOUDSTACK-4802 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4802 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Kelven Yang >Assignee: Kelven Yang >Priority: Critical > > CloudStack VM-start flow is broken by the behave of vSphere 5.0 Update 2. VM > can not be started after VM has VM snapshot been taken. This issue is > currently known to only happen in vSphere 5.0 Update 2 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-4802) [VMware] Unable to start VM if VM has VM snapshot been taken in vSphere version 5.0 Update 2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4802. - Resolution: Fixed > [VMware] Unable to start VM if VM has VM snapshot been taken in vSphere > version 5.0 Update 2 > > > Key: CLOUDSTACK-4802 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4802 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Kelven Yang >Assignee: Kelven Yang >Priority: Critical > > CloudStack VM-start flow is broken by the behave of vSphere 5.0 Update 2. VM > can not be started after VM has VM snapshot been taken. This issue is > currently known to only happen in vSphere 5.0 Update 2 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4802) [VMware] Unable to start VM if VM has VM snapshot been taken in vSphere version 5.0 Update 2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786729#comment-13786729 ] ASF subversion and git services commented on CLOUDSTACK-4802: - Commit 2976d9c7932ed160cf3205c06f4d82efdfa0f10a in branch refs/heads/4.2 from [~kelveny] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2976d9c ] CLOUDSTACK-4802: Change VM start flow to better support VM snapshot on certian version of vSphere, (vSphere 5.0 Update 2). If we detect that VM has pending VM snapshot, we will fully honor VM disk info from vCenter, since in some version of vSphere (vSphere 5.0 U2) does not allow disk-editting when VM has pending snapshot. > [VMware] Unable to start VM if VM has VM snapshot been taken in vSphere > version 5.0 Update 2 > > > Key: CLOUDSTACK-4802 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4802 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Kelven Yang >Assignee: Kelven Yang >Priority: Critical > > CloudStack VM-start flow is broken by the behave of vSphere 5.0 Update 2. VM > can not be started after VM has VM snapshot been taken. This issue is > currently known to only happen in vSphere 5.0 Update 2 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-4815) Correct Management Server Install docs
Travis Graham created CLOUDSTACK-4815: - Summary: Correct Management Server Install docs Key: CLOUDSTACK-4815 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4815 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0 Reporter: Travis Graham Fix For: 4.2.1 Attachments: management-server-install-flow.patch This adds the correct download URLs for XenServer, KVM, and VMware systemvm images and adds no_subtree_check to the NFS exports settings to silence the warning on mount. It defaults to no_subtree_check, so this just removed the warning on mount. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-4701) "Add guest network" button should be disabled for basic zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-4701. -- Resolution: Invalid Even the whole system has only basic zone(s), Add Guest Network Dialog in Network menu should still show. When Add Guest Network Dialog opens up, zone dropdown will have no options (zone dropdown only include Advanced zones) and zone dropdown is required. Then, user will know why Add Guest Network is not available (because there is no zone for it). If we just hide Add Guest Network dialog, user won't know why it doesn't show. > "Add guest network" button should be disabled for basic zone > > > Key: CLOUDSTACK-4701 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4701 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.1 > Environment: UI > Build from 4.2.1 > Basic zone with SG >Reporter: Rayees Namathponnan > Fix For: 4.2.1 > > > Step 1 : Create Basic zone with EIP / ELB > Step 2: Network -> Add Guest Network > If you click Add guest network button, below error gets displayed > Unable to execute API command listnetworkofferings due to invalid value. > Invalid parameter zoneid value=null due to incorrect long value format, or > entity does not exist or due to incorrect parameter annotation for the field > in api cmd class > Expected result > Button ( Add guest network) should be enabled, only if at least one Advanced > zone is configured -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4815) Correct Management Server Install docs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Travis Graham updated CLOUDSTACK-4815: -- Attachment: management-server-install-flow.patch Attaching patch file. > Correct Management Server Install docs > -- > > Key: CLOUDSTACK-4815 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4815 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Travis Graham > Labels: documentation > Fix For: 4.2.1 > > Attachments: management-server-install-flow.patch > > > This adds the correct download URLs for XenServer, KVM, and VMware systemvm > images and adds no_subtree_check to the NFS exports settings to silence the > warning on mount. It defaults to no_subtree_check, so this just removed the > warning on mount. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4811) Adding Incorrect CIDR in public ip range of zone create wizard is allowing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786602#comment-13786602 ] Jessica Wang commented on CLOUDSTACK-4811: -- There is nothing needed to change at UI side. As long as server-side (API) returns an error (e.g. incorrect CIDR error), UI will automatically show it on screen. Therefore, I just removed "UI" from component field. > Adding Incorrect CIDR in public ip range of zone create wizard is allowing > -- > > Key: CLOUDSTACK-4811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Reporter: Jayapal Reddy >Assignee: Jayapal Reddy > Fix For: 4.2.1 > > > 1. Add a new zone from UI add zone wizard. > 2. Add incorrect cidr in in 3rd tab Setup network PUBLIC TRAFFIC > gateway netmask VLANStart IP End > IP > 10.147.52.1 255.255.25.0 52 10.147.52.100 > 10.147.52.120 > 3. UI is allowing the above config > 4. The zone will also get deployed. > 5. The problem is coming in creating the public interface in system vms. If > the interface got created problem in reaching the public network. > 6. This issue is pain to user because after deploying zone user need to > recreate zone again. Also some times user don't realise about the > misconfiguration. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Reopened] (CLOUDSTACK-4811) Adding Incorrect CIDR in public ip range of zone create wizard is allowing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang reopened CLOUDSTACK-4811: -- > Adding Incorrect CIDR in public ip range of zone create wizard is allowing > -- > > Key: CLOUDSTACK-4811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Reporter: Jayapal Reddy >Assignee: Jayapal Reddy > Fix For: 4.2.1 > > > 1. Add a new zone from UI add zone wizard. > 2. Add incorrect cidr in in 3rd tab Setup network PUBLIC TRAFFIC > gateway netmask VLANStart IP End > IP > 10.147.52.1 255.255.25.0 52 10.147.52.100 > 10.147.52.120 > 3. UI is allowing the above config > 4. The zone will also get deployed. > 5. The problem is coming in creating the public interface in system vms. If > the interface got created problem in reaching the public network. > 6. This issue is pain to user because after deploying zone user need to > recreate zone again. Also some times user don't realise about the > misconfiguration. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4811) Adding Incorrect CIDR in public ip range of zone create wizard is allowing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-4811: - Component/s: (was: UI) > Adding Incorrect CIDR in public ip range of zone create wizard is allowing > -- > > Key: CLOUDSTACK-4811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Reporter: Jayapal Reddy >Assignee: Jayapal Reddy > Fix For: 4.2.1 > > > 1. Add a new zone from UI add zone wizard. > 2. Add incorrect cidr in in 3rd tab Setup network PUBLIC TRAFFIC > gateway netmask VLANStart IP End > IP > 10.147.52.1 255.255.25.0 52 10.147.52.100 > 10.147.52.120 > 3. UI is allowing the above config > 4. The zone will also get deployed. > 5. The problem is coming in creating the public interface in system vms. If > the interface got created problem in reaching the public network. > 6. This issue is pain to user because after deploying zone user need to > recreate zone again. Also some times user don't realise about the > misconfiguration. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-4811) Adding Incorrect CIDR in public ip range of zone create wizard is allowing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-4811. -- Resolution: Invalid UI only do simple verification (e.g. required or not, number type or not). Complicated verification like CIDR calculation should be done at server-side. If CIDR is incorrect, server-side (API) should return an error, then UI will show the error returned by API. > Adding Incorrect CIDR in public ip range of zone create wizard is allowing > -- > > Key: CLOUDSTACK-4811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller, UI >Reporter: Jayapal Reddy >Assignee: Jayapal Reddy > Fix For: 4.2.1 > > > 1. Add a new zone from UI add zone wizard. > 2. Add incorrect cidr in in 3rd tab Setup network PUBLIC TRAFFIC > gateway netmask VLANStart IP End > IP > 10.147.52.1 255.255.25.0 52 10.147.52.100 > 10.147.52.120 > 3. UI is allowing the above config > 4. The zone will also get deployed. > 5. The problem is coming in creating the public interface in system vms. If > the interface got created problem in reaching the public network. > 6. This issue is pain to user because after deploying zone user need to > recreate zone again. Also some times user don't realise about the > misconfiguration. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Issue Comment Deleted] (CLOUDSTACK-1994) [SSVM] Unable to start agent: Resource class not found: org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due to: java.lang.ClassNotFo
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dean Kamali updated CLOUDSTACK-1994: Comment: was deleted (was: I'm currently using this version of ssvm http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-master-xen.vhd.bz2 yet, I'm having the same issue still ) > [SSVM] Unable to start agent: Resource class not found: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due to: > java.lang.ClassNotFoundException: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource > --- > > Key: CLOUDSTACK-1994 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1994 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 > Environment: commit 97c2f7d0c4b330f3456e8c1b5236e280b9931197 >Reporter: venkata swamybabu budumuru >Priority: Blocker > Fix For: 4.2.0 > > Attachments: logs.tgz > > > Steps to reproduce : > 1. Have the latest master and deploy an advanced zone with Xen Cluster > 2. use system vm template "systemvmtemplate-2013-03-27-master-xen.vhd.bz2" > from http://jenkins.cloudstack.org > 3. verify whether system vms come up fine or not > Observations : > (i) both v-2-VM and s-1-VM are shown in running state > (ii) cloud.host table doesn't show the SSVM but, shows the console proxy in > host table. > (iii) default centos template download doesn't happen. New template > registration as well fails to download > (iv) Here is the snippet from SSVM:/var/log/cloud/cloud.out > log4j:WARN No appenders could be found for logger > (org.apache.commons.httpclient.params.DefaultHttpParams). > log4j:WARN Please initialize the log4j system properly. > log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more > info. > 08:15:40,493 ERROR AgentShell:610 - Unable to start agent: Resource class not > found: org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due > to: java.lang.ClassNotFoundException: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource > Unable to start agent: Resource class not found: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due to: > java.lang.ClassNotFoundException: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource > (v) Based on the above log, it looks like agent on the ssvm is failing to > start. ps -aef | grep -i java doesn't show up an process. > Attaching all the required logs to bug. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Comment Edited] (CLOUDSTACK-1994) [SSVM] Unable to start agent: Resource class not found: org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due to: java.lang.ClassNotFoundExce
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786547#comment-13786547 ] Dean Kamali edited comment on CLOUDSTACK-1994 at 10/4/13 8:06 PM: -- I'm having the same issue with cloudstack 4.2 and xenserver 6.2 I'm using this version http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-master-xen.vhd.bz2 However issue still persists was (Author: amlife): I'm having the same issue with cloudstack 4.2 and xenserver 6.2 I wonder from where can I get a copy of new ssvm ?, please advise > [SSVM] Unable to start agent: Resource class not found: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due to: > java.lang.ClassNotFoundException: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource > --- > > Key: CLOUDSTACK-1994 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1994 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 > Environment: commit 97c2f7d0c4b330f3456e8c1b5236e280b9931197 >Reporter: venkata swamybabu budumuru >Priority: Blocker > Fix For: 4.2.0 > > Attachments: logs.tgz > > > Steps to reproduce : > 1. Have the latest master and deploy an advanced zone with Xen Cluster > 2. use system vm template "systemvmtemplate-2013-03-27-master-xen.vhd.bz2" > from http://jenkins.cloudstack.org > 3. verify whether system vms come up fine or not > Observations : > (i) both v-2-VM and s-1-VM are shown in running state > (ii) cloud.host table doesn't show the SSVM but, shows the console proxy in > host table. > (iii) default centos template download doesn't happen. New template > registration as well fails to download > (iv) Here is the snippet from SSVM:/var/log/cloud/cloud.out > log4j:WARN No appenders could be found for logger > (org.apache.commons.httpclient.params.DefaultHttpParams). > log4j:WARN Please initialize the log4j system properly. > log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more > info. > 08:15:40,493 ERROR AgentShell:610 - Unable to start agent: Resource class not > found: org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due > to: java.lang.ClassNotFoundException: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource > Unable to start agent: Resource class not found: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due to: > java.lang.ClassNotFoundException: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource > (v) Based on the above log, it looks like agent on the ssvm is failing to > start. ps -aef | grep -i java doesn't show up an process. > Attaching all the required logs to bug. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-1994) [SSVM] Unable to start agent: Resource class not found: org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due to: java.lang.ClassNotFoundException
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786560#comment-13786560 ] Dean Kamali commented on CLOUDSTACK-1994: - I'm currently using this version of ssvm http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-master-xen.vhd.bz2 yet, I'm having the same issue still > [SSVM] Unable to start agent: Resource class not found: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due to: > java.lang.ClassNotFoundException: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource > --- > > Key: CLOUDSTACK-1994 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1994 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 > Environment: commit 97c2f7d0c4b330f3456e8c1b5236e280b9931197 >Reporter: venkata swamybabu budumuru >Priority: Blocker > Fix For: 4.2.0 > > Attachments: logs.tgz > > > Steps to reproduce : > 1. Have the latest master and deploy an advanced zone with Xen Cluster > 2. use system vm template "systemvmtemplate-2013-03-27-master-xen.vhd.bz2" > from http://jenkins.cloudstack.org > 3. verify whether system vms come up fine or not > Observations : > (i) both v-2-VM and s-1-VM are shown in running state > (ii) cloud.host table doesn't show the SSVM but, shows the console proxy in > host table. > (iii) default centos template download doesn't happen. New template > registration as well fails to download > (iv) Here is the snippet from SSVM:/var/log/cloud/cloud.out > log4j:WARN No appenders could be found for logger > (org.apache.commons.httpclient.params.DefaultHttpParams). > log4j:WARN Please initialize the log4j system properly. > log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more > info. > 08:15:40,493 ERROR AgentShell:610 - Unable to start agent: Resource class not > found: org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due > to: java.lang.ClassNotFoundException: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource > Unable to start agent: Resource class not found: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due to: > java.lang.ClassNotFoundException: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource > (v) Based on the above log, it looks like agent on the ssvm is failing to > start. ps -aef | grep -i java doesn't show up an process. > Attaching all the required logs to bug. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-1994) [SSVM] Unable to start agent: Resource class not found: org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due to: java.lang.ClassNotFoundException
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786547#comment-13786547 ] Dean Kamali commented on CLOUDSTACK-1994: - I'm having the same issue with cloudstack 4.2 and xenserver 6.2 I wonder from where can I get a copy of new ssvm ?, please advise > [SSVM] Unable to start agent: Resource class not found: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due to: > java.lang.ClassNotFoundException: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource > --- > > Key: CLOUDSTACK-1994 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1994 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 > Environment: commit 97c2f7d0c4b330f3456e8c1b5236e280b9931197 >Reporter: venkata swamybabu budumuru >Priority: Blocker > Fix For: 4.2.0 > > Attachments: logs.tgz > > > Steps to reproduce : > 1. Have the latest master and deploy an advanced zone with Xen Cluster > 2. use system vm template "systemvmtemplate-2013-03-27-master-xen.vhd.bz2" > from http://jenkins.cloudstack.org > 3. verify whether system vms come up fine or not > Observations : > (i) both v-2-VM and s-1-VM are shown in running state > (ii) cloud.host table doesn't show the SSVM but, shows the console proxy in > host table. > (iii) default centos template download doesn't happen. New template > registration as well fails to download > (iv) Here is the snippet from SSVM:/var/log/cloud/cloud.out > log4j:WARN No appenders could be found for logger > (org.apache.commons.httpclient.params.DefaultHttpParams). > log4j:WARN Please initialize the log4j system properly. > log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more > info. > 08:15:40,493 ERROR AgentShell:610 - Unable to start agent: Resource class not > found: org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due > to: java.lang.ClassNotFoundException: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource > Unable to start agent: Resource class not found: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due to: > java.lang.ClassNotFoundException: > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource > (v) Based on the above log, it looks like agent on the ssvm is failing to > start. ps -aef | grep -i java doesn't show up an process. > Attaching all the required logs to bug. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4793) Improve VR Upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786516#comment-13786516 ] Milamber commented on CLOUDSTACK-4793: -- For the case of Redundant Virtual Router, restart the virtual routers sequentially, with the Backup router first. > Improve VR Upgrade > -- > > Key: CLOUDSTACK-4793 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4793 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Kishan Kavala >Assignee: Kishan Kavala > Fix For: Future > > > Give admin control to sequence the upgrade of the cloud by: > Infrastructure hierarchy: by Cluster, Pod, and Zone etc. > Administrative hierarchy: by Tenant or Domain > Minimize service interruption to users > Improve the speed of the upgrade time by making as many upgrade operations in > parallel as possible -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4793) Improve VR Upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milamber updated CLOUDSTACK-4793: - Summary: Improve VR Upgrade (was: Impore VR Upgrade) > Improve VR Upgrade > -- > > Key: CLOUDSTACK-4793 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4793 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Kishan Kavala >Assignee: Kishan Kavala > Fix For: Future > > > Give admin control to sequence the upgrade of the cloud by: > Infrastructure hierarchy: by Cluster, Pod, and Zone etc. > Administrative hierarchy: by Tenant or Domain > Minimize service interruption to users > Improve the speed of the upgrade time by making as many upgrade operations in > parallel as possible -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4602) [DOC] CLONE - Update the supported ec2 version from 2010-11-15 to a more recent EC2 API version i.e. 2012-08-15.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-4602: - Assignee: (was: Jessica Tomechak) > [DOC] CLONE - Update the supported ec2 version from 2010-11-15 to a more > recent EC2 API version i.e. 2012-08-15. > > > Key: CLOUDSTACK-4602 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4602 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: AWSAPI >Affects Versions: 4.2.0 >Reporter: Likitha Shetty > Labels: documentation > Fix For: 4.2.1 > > > As described the functional spec - > https://cwiki.apache.org/confluence/display/CLOUDSTACK/EC2++-+Functional+Spec+for+Query+API+support, > the AWS EC2 version supported by CS AWSAPI needs to be updated to more > recent version. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-818) Document Dedicate Pod, Cluster or Host to a domain
[ https://issues.apache.org/jira/browse/CLOUDSTACK-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-818: Assignee: (was: Jessica Tomechak) > Document Dedicate Pod, Cluster or Host to a domain > -- > > Key: CLOUDSTACK-818 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-818 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair > Fix For: 4.2.1 > > > Dedicate Pod, Cluster or Host to a domain- Documentation -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-233) Copy edit messages.properties
[ https://issues.apache.org/jira/browse/CLOUDSTACK-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-233: Assignee: (was: Jessica Tomechak) > Copy edit messages.properties > - > > Key: CLOUDSTACK-233 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-233 > Project: CloudStack > Issue Type: Task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: pre-4.0.0 >Reporter: Jessica Tomechak >Priority: Minor > Fix For: 4.1.0 > > > Ensure messages are understandable and use correct English. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-411) Add another step during kvm agent installation on Ubuntu machine
[ https://issues.apache.org/jira/browse/CLOUDSTACK-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-411: Assignee: (was: Jessica Tomechak) > Add another step during kvm agent installation on Ubuntu machine > > > Key: CLOUDSTACK-411 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-411 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: edison su > Fix For: 4.0.1 > > > Ref: https://issues.apache.org/jira/browse/CLOUDSTACK-410. For 4.0 release, > we can document it in the installation guide for kvm agent installation on > ubuntu machine, with the following command: > uncomment out "# vnc_listen = "0.0.0.0"" in /etc/libvirt/qemu.conf -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-900) Document enable storage xenmotion support in XenServer 6.1 feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-900: Assignee: (was: Jessica Tomechak) > Document enable storage xenmotion support in XenServer 6.1 feature > -- > > Key: CLOUDSTACK-900 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-900 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-959) Missing sub-sections in document section System Service Offerings
[ https://issues.apache.org/jira/browse/CLOUDSTACK-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-959: Assignee: (was: Jessica Tomechak) > Missing sub-sections in document section System Service Offerings > - > > Key: CLOUDSTACK-959 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-959 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.0.0 >Reporter: Jessica Tomechak >Priority: Minor > Fix For: 4.1.0 > > > It appears that when the section "System Service Offerings" was added to the > Admin Guide, its sub-heading "Creating a New System Service Offering" was > omitted. The file is in the doc directory, but it was never included in the > main file system-service-offerings.xml. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-861) [DOC] Document Cisco UCS baremetal support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-861: Assignee: (was: Jessica Tomechak) > [DOC] Document Cisco UCS baremetal support > -- > > Key: CLOUDSTACK-861 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-861 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: David Nalley > Fix For: 4.2.1 > > > Document the UCS baremetal functionality -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-1478) [DOC] Document baremetal kickstart
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-1478: - Assignee: (was: Jessica Tomechak) > [DOC] Document baremetal kickstart > -- > > Key: CLOUDSTACK-1478 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1478 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Jessica Tomechak >Priority: Minor > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-17) Merge final documentation into 4.0 branch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-17: --- Assignee: (was: Jessica Tomechak) > Merge final documentation into 4.0 branch > - > > Key: CLOUDSTACK-17 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-17 > Project: CloudStack > Issue Type: Task > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: pre-4.0.0, 4.0.0 >Reporter: Ewan Mellor >Priority: Critical > Fix For: 4.0.0 > > > Merge the latest documentation into the 4.0 branch before we make the final > RC, so that we have a frozen, up-to-date copy in the release branch. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-816) Document health monitoring for load balanced instances
[ https://issues.apache.org/jira/browse/CLOUDSTACK-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-816: Assignee: (was: Jessica Tomechak) > Document health monitoring for load balanced instances > -- > > Key: CLOUDSTACK-816 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-816 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair > Fix For: 4.2.0 > > > Document health monitoring for load balanced instances -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-865) Document API Refactoring
[ https://issues.apache.org/jira/browse/CLOUDSTACK-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-865: Assignee: (was: Jessica Tomechak) > Document API Refactoring > - > > Key: CLOUDSTACK-865 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-865 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair > Fix For: 4.1.0 > > > Document API Refactoring -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-805) Document Isolation based on Security Groups in Advanced Zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-805: Assignee: (was: Jessica Tomechak) > Document Isolation based on Security Groups in Advanced Zone > > > Key: CLOUDSTACK-805 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-805 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair > Fix For: 4.2.0 > > > Documentation on Isolation based on Security Groups in Advanced Zone -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-1932) AutoScale UI documentation doesn't mention the option appears only for NetScaler
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-1932: - Assignee: (was: Jessica Tomechak) > AutoScale UI documentation doesn't mention the option appears only for > NetScaler > > > Key: CLOUDSTACK-1932 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1932 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.1.0, 4.2.0 >Reporter: Jessica Tomechak >Priority: Minor > Fix For: 4.2.1 > > > This affects add-load-balancer-rule.xml and autoscale.xml. > In add-load-balancer-rule.xml, in the step "Fill in the following:", the > bullet item AutoScale should note that this option appears only when > NetScaler is selected as a service provider for the network where you are > defining the LB rule. > And in autoscale.xml, there should be a note right at the top like > "(NetScaler only)" or "(Supported only in networks where the Citrix NetScaler > is used.)" -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-830) Document Reset SSH key feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-830: Assignee: (was: Jessica Tomechak) > Document Reset SSH key feature > -- > > Key: CLOUDSTACK-830 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-830 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers > Fix For: 4.1.0 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-774) Supporting kickstart in CloudStack baremetal
[ https://issues.apache.org/jira/browse/CLOUDSTACK-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-774: Assignee: (was: Jessica Tomechak) > Supporting kickstart in CloudStack baremetal > > > Key: CLOUDSTACK-774 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-774 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Baremetal >Affects Versions: 4.1.0 >Reporter: frank zhang > Fix For: 4.2.0 > > Attachments: CLOUDSTACK-774-baremetal-support.patch, > CLOUDSTACK-774-baremetal-support.patch.md5sum, > CLOUDSTACK-774-baremetal-support.patch.sig > > > Supporting kickstart install for RedHat like Linux in CloudStack Baremetal > provisioning > Release Planning: > Dev List Discussion: http://markmail.org/message/m6tg5nzfgqiwhzre > Functional Spec: https://cwiki.apache.org/CLOUDSTACK/baremetal-kickstart.html > Feature Branch: master > progress: 90% -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-866) Document Limit API Queries
[ https://issues.apache.org/jira/browse/CLOUDSTACK-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-866: Assignee: (was: Jessica Tomechak) > Document Limit API Queries > -- > > Key: CLOUDSTACK-866 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-866 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Reporter: Radhika Nair > Fix For: 4.1.0 > > > Document Limit API Queries -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-405) management server startup missing from install documents
[ https://issues.apache.org/jira/browse/CLOUDSTACK-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-405: Assignee: (was: Jessica Tomechak) > management server startup missing from install documents > > > Key: CLOUDSTACK-405 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-405 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Noa Resare > Fix For: pre-4.0.0 > > > For the simplest possible test case (that I can come up with) the > Installation Guide instructions fail, with status 404 when attempting to > connect to http://MANAGEMENT_SERVER:8080/client > Expected outcome: > The cloudstack web UI in the web browser when accessing > http://MANAGEMENT_SERVER:8080/client > Actual outcome: > The default tomcat 404 page > Steps to reproduce: > - I created a fully updated vmware vm running a 64 bit Ubuntu 12.04.1 > - installed mysql-server, with root password abc123 > - ran mysql_secure_installation, default options > - pulled the latest built ubuntu packages from jenkins: > http://jenkins.cloudstack.org/job/build-4.0-ubuntu1204/535/artifact/CloudStack-oss-4.0.0-535.tar.bz2 > - ran the install script installing the management server (which translates > install 'apt-get install cloud-client') > - ran "cloud-setup-databases cloud:foobar --deploy-as=root:abc123" with the > output "CloudStack has successfully initialized database" > - attempted to connect with my web browser at > http://MANAGEMENT_SERVER:8080/client > Additional notes: > Looking at the output from the installer, it seems the tomcat6 starts on > install, listening on port 8080. If I run > "/etc/init.d/tomcat6 stop" followed by "/etc/init.d/cloud-management start" I > get a cloudstack login prompt at http://MANAGEMENT_SERVER:8080/client/ -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-2018) [DOC] How system.vm passwords can be randomized
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-2018: - Assignee: (was: Jessica Tomechak) > [DOC] How system.vm passwords can be randomized > --- > > Key: CLOUDSTACK-2018 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2018 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.0.0, 4.1.0, 4.2.0 >Reporter: Prasanna Santhanam > > The systemVM password is defaulted and it is possible to change it to a > random password. The process for doing this is through a global setting. > However this doesn't seem to be documented at the moment. > Relevant ML discussion: > http://markmail.org/thread/xdizpx3jumbykcr6#query:+page:1+mid:xdizpx3jumbykcr6+state:results -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4670) [Baremetal] Cloudplatform BareMetal installation guide for CP 4.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-4670: - Assignee: (was: Jessica Tomechak) > [Baremetal] Cloudplatform BareMetal installation guide for CP 4.2 > - > > Key: CLOUDSTACK-4670 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4670 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: angeline shen >Priority: Minor > Fix For: 4.2.1 > > > Jessica: > Cloudplatform BareMetal installation guide for CP 4.2: > Section titled 'Create a Bare Metal Template ' (page 19 - 20 ) should > be moved to after > Section titled 'Add the PXE Server and DHCP Server to Your Deployment' -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-773) Document Object Store-Integration with CS as secondary Storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-773: Assignee: (was: Jessica Tomechak) > Document Object Store-Integration with CS as secondary Storage > -- > > Key: CLOUDSTACK-773 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-773 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair > Fix For: 4.2.1 > > > Document Object Store-Integration with CS as secondary Storage -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-867) Document Scaling up CPU and RAM for running VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-867: Assignee: (was: Jessica Tomechak) > Document Scaling up CPU and RAM for running VMs > > > Key: CLOUDSTACK-867 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-867 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair > Fix For: 4.2.0 > > Attachments: Dynamically_Scalable.jpg, Global_Settings.jpg, > zone_Settings .jpg > > > Document Scaling up CPU and RAM for running VMs -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4229) AWS Style healthcheck creation are not supported on NS 9.3 in Cloudstack 4.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-4229: - Assignee: (was: Jessica Tomechak) > AWS Style healthcheck creation are not supported on NS 9.3 in Cloudstack 4.2 > > > Key: CLOUDSTACK-4229 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4229 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Rajesh Battala > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-745) Reset a VM on reboot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-745: Assignee: (was: Jessica Tomechak) > Reset a VM on reboot > > > Key: CLOUDSTACK-745 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-745 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Harikrishna Patnala > Fix For: 4.2.0 > > > To have a method to reset the vm on its reboot. > So on reboot, the vm's disk is discarded and creates a new root disk using > the template. > The use cases for this are > -> Secure environments that need a fresh start on every boot > -> Desktops that should not retain state -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-833) [DOC] Document increase in VMware 5.1 max cluster size
[ https://issues.apache.org/jira/browse/CLOUDSTACK-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-833: Assignee: (was: Jessica Tomechak) > [DOC] Document increase in VMware 5.1 max cluster size > -- > > Key: CLOUDSTACK-833 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-833 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: David Nalley > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-925) Document XenServer updates notifications
[ https://issues.apache.org/jira/browse/CLOUDSTACK-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-925: Assignee: (was: Jessica Tomechak) > Document XenServer updates notifications > > > Key: CLOUDSTACK-925 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-925 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair > Fix For: 4.1.0 > > > Document XenServer updates notifications -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4550) [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have migration work
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-4550: - Assignee: (was: Jessica Tomechak) > [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have > migration work > -- > > Key: CLOUDSTACK-4550 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4550 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc, KVM, Upgrade >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Priority: Critical > > See CLOUDSTACK-4405 for the original bug. This is the doc to be prepared as > part of upgrade in release notes once the fix for the bug is verified to work > After network bridges being renamed from cloudVirBrVLAN to brem1-VLAN to > support the same VLAN on multiple physical networks the migration of VMs from > hosts prior the upgrade to the ones added after the upgrade will fail. > In order to fix this rename the bridges is required to allow migration to > work. > This can be done by running the cloudstack-agent-upgrade script. The original > bug is still undergoing testing, but these are the initial instructions -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-840) [DOC] Document CLOUDSTACK-670 regarding configuration option for linked clones or lack thereof
[ https://issues.apache.org/jira/browse/CLOUDSTACK-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-840: Assignee: (was: Jessica Tomechak) > [DOC] Document CLOUDSTACK-670 regarding configuration option for linked > clones or lack thereof > -- > > Key: CLOUDSTACK-840 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-840 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: David Nalley > Fix For: 4.2.1 > > > Add documentation for the configuration option about use (or not) of linked > clones. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4568) Need to add this to the release note of 4.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-4568: - Assignee: (was: Jessica Tomechak) > Need to add this to the release note of 4.2 > --- > > Key: CLOUDSTACK-4568 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4568 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Bharat Kumar > Labels: releasenotes > Fix For: 4.2.1 > > > After upgrade to 4.2 the mem.overporvisioning.factor and > cpu.overporvisioning.factor will be set to one that is the default value and > are at cluster level now. > In case if some one prior to the 4.2 was usign mem.overporvisioning.factor > and cpu.overporvisioning.factor after the upgrade these will be reset to one > and can be changed by editing the cluster settings. > All the clusters created after the upgrade will get created with the values > overcomit values specified at the global config by default. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-923) Documentation for Add synchronization for createSnapshot command per host basis
[ https://issues.apache.org/jira/browse/CLOUDSTACK-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-923: Assignee: (was: Jessica Tomechak) > Documentation for Add synchronization for createSnapshot command per host > basis > --- > > Key: CLOUDSTACK-923 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-923 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair > Fix For: 4.1.0 > > > Documentation for Add synchronization for createSnapshot command per host > basis -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-8) Update API Reference man pages for v4.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-8: -- Assignee: (was: Jessica Tomechak) > Update API Reference man pages for v4.0 > --- > > Key: CLOUDSTACK-8 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8 > Project: CloudStack > Issue Type: Task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.0.0 >Reporter: Jessica Tomechak > Fix For: pre-4.0.0 > > > 3.x API Reference needs update for v4.0. Need to run doc gen script and post > the new HTML files. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-406) Amazon Web Service Interface Compatibility Section - Reference to port 8080 needs to be changed to port 7080 in cloudstack-aws-api-register command and when setting E
[ https://issues.apache.org/jira/browse/CLOUDSTACK-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-406: Assignee: (was: Jessica Tomechak) > Amazon Web Service Interface Compatibility Section - Reference to port 8080 > needs to be changed to port 7080 in cloudstack-aws-api-register command and > when setting EC2_URL. > - > > Key: CLOUDSTACK-406 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-406 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: pre-4.0.0 > Environment: Install guide - > http://jenkins.cloudstack.org/view/master/job/build-docs-install-master/lastSuccessfulBuild/artifact/Apache_CloudStack-4.0.0-incubating-Installation_Guide-en-US.pdf >Reporter: Sangeetha Hariharan > Fix For: 4.0.0 > > > Amazon Web Service Interface Compatibility Section - Reference to port 8080 > needs to be changed to port 7080 in cloudstack-aws-api-register command and > when setting EC2_URL. > In 10.4.1. AWS API User Registration section: > $ cloudstack-aws-api-register --apikey=User’s CloudStack API key > --secretkey=User’s > CloudStack Secret key --cert=/path/to/cert.pem > --url=http://CloudStack.server:8080/ > awsapi > --url param should be http://CloudStack.server:7080/awsapi , instead of port > 8080. > 10.4.2. AWS API Command-Line Tools Setup > export EC2_URL=http://CloudStack.server:8080/awsapi > This varibale needs to point to "http://CloudStack.server:7080/awsapi"; -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-134) Document procedure to install vhd-util
[ https://issues.apache.org/jira/browse/CLOUDSTACK-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-134: Assignee: (was: Jessica Tomechak) > Document procedure to install vhd-util > -- > > Key: CLOUDSTACK-134 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-134 > Project: CloudStack > Issue Type: Task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: pre-4.0.0 >Reporter: edison su >Priority: Blocker > Fix For: 4.0.0 > > > Due to license issue reported in CLOUDSTACK-30, vhd-util is removed from > source code and packages. Need to document the procedure to download and > install vhd-util during the mgt server installation. > The current url is http://download.cloud.com.s3.amazonaws.com/tools/vhd-util > If mgt server is rhel/centos, need to download from this url, then copy > vhd-util into /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/ > If mgt server is ubuntu, then put vhd-util into > /usr/lib/cloud/common/scripts/vm/hypervisor/xenserver/vhd-util > (Chandan adds:) > We should also document the requirement of setting the following permissions > to the downloaded vhd-util tool: > Chmod 755 vhd-util -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4300) [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-4300: - Assignee: (was: Jessica Tomechak) > [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade > > > Key: CLOUDSTACK-4300 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4300 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc, KVM, SystemVM, Upgrade >Affects Versions: 4.2.0 > Environment: Host : KVM [CentOS 6.1] > MS : CentOS 6.1 > upgrade from 2.2.14 to 4.2 >Reporter: Abhinav Roy >Priority: Blocker > Fix For: 4.2.1 > > Attachments: CS-4300.zip, re_CS-4300.zip > > > Steps : > > 1. Deploy a CS 2.2.14 advanced zone setup with KVM host. > 2. do some operations like create vm, snapshots, templates, domain, accounts > etc > 3. upgrade to 4.2 > Expected behaviour : > === > Upgrade should go fine and new system vms should come up > Observed behaviour : > == > Upgrade went fine but system vms don't come up, they stay in the starting > state. > Attaching management server logs, catalina logs, agent logs and DB dumps -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-738) Ability to manage Basic and Advanced Zone using a single instance of CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-738: Assignee: (was: Jessica Tomechak) > Ability to manage Basic and Advanced Zone using a single instance of > CloudStack > --- > > Key: CLOUDSTACK-738 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-738 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Manan Shah > Fix For: Future > > > Currently, CloudStack supports Basic Zones as well as Advanced Zones but the > UI supports management of only Basic Zones or Advanced Zones. > This enhancement is to track allowing management of Basic and Advanced Zones > using a single instance of CloudStack. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-1285) UI -Tooltip - Lengthy and inconsistent description among toolips
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-1285: - Assignee: (was: Jessica Tomechak) > UI -Tooltip - Lengthy and inconsistent description among toolips > > > Key: CLOUDSTACK-1285 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1285 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0, 4.2.0 > Environment: RHEL 6.3 Build#15 >Reporter: Parth Jagirdar >Priority: Minor > Attachments: 3.jpg, 4.jpg > > > "A unique name for the template. This will be visible to users, so choose > something descriptive" ; I think 94 Characters are too much for a ToolTip > representing name. (Screen 4) > And is also inconsistent with other tooltips for names which are more concise > and simple such as "A name for the Zone". (Refer to Screen 4 and compare it > to Screen 3) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-1441) Document ApiDiscoverService
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-1441: - Assignee: (was: Jessica Tomechak) > Document ApiDiscoverService > --- > > Key: CLOUDSTACK-1441 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1441 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Jessica Tomechak >Priority: Minor > Labels: api > Fix For: 4.1.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-1152) Missing tag in host-add.xml
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-1152: - Assignee: (was: Jessica Tomechak) > Missing tag in host-add.xml > --- > > Key: CLOUDSTACK-1152 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1152 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Logan McNaughton >Priority: Minor > Fix For: 4.1.0 > > > docs/en-US/host-add.xml is missing a closing , it is present in master > and prevents docs from building -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-3635) [DOC][Dynamic Scaling][VMware] Guest OS support information
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-3635: - Assignee: (was: Jessica Tomechak) > [DOC][Dynamic Scaling][VMware] Guest OS support information > --- > > Key: CLOUDSTACK-3635 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3635 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Sateesh Chodapuneedi > Labels: adminguide, installguide, release > Fix For: 4.2.1 > > > Dynamic scaling of VM consists of scaling CPU & MEMORY of running VM. > The ability to hotadd cpu or memory depends on Guest operating system version > (like CentOS 5.3) and bits of the OS (like 64 bit). > CloudStack does query Guest OS information available in ESXi information > using vSphere API. But this information is not granular to the level of exact > version of guest operating system and bitness (32 or 64). Hence it is > recommended that user verify if the VM is installed with guest operating > system which supports cpu or memory hotadd features from following link. > http://www.vmware.com/resources/compatibility/search.php?deviceCategory=software&testConfig=16&productid=17364 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-1286) UI - Tooltip - Missing Tooltips for some key features
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-1286: - Assignee: (was: Jessica Tomechak) > UI - Tooltip - Missing Tooltips for some key features > - > > Key: CLOUDSTACK-1286 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1286 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0 > Environment: RHEL 6.3 Build #15 >Reporter: Parth Jagirdar > > A few drop down menus(Select’s) have tooltips and almost no checkbox has any. > (Again this was brief sanity test). > I think ToolTips for "Public" and "Featured" on template registration wizard > would be worth reading for a new user. > Marking this Major as if Tooltips are at all required then these features are > the few places they should go in first. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4729) Document workaround for IPMI protocal type for specific hardware on baremetal
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Tomechak updated CLOUDSTACK-4729:
-
Assignee: (was: Jessica Tomechak)
> Document workaround for IPMI protocal type for specific hardware on baremetal
> -
>
> Key: CLOUDSTACK-4729
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4729
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc
>Affects Versions: 4.2.1
>Reporter: frank zhang
> Fix For: 4.2.1
>
>
> We should mention to users that Baremetal uses ipmitool to control lifecycle
> of baremetal host. ipmitool default uses interface 'lan' to issue ipmi
> commands. Depending on your motherboard, the interface may need to be
> 'lanplus', in this case, user has to modify script
> /usr/lib64/cloud/agent/scripts/util/ipmi.py
> replace all lines calling ipmi tool for example:
> o = ipmitool("-H", hostname, "-U", usrname, "-P", password, "chassis",
> "power", "status")
> to
> o = ipmitool("-H", hostname, ,"-I", "lanplus", "-U", usrname, "-P", password,
> "chassis", "power", "status")
> this issue will be addressed in next release.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4799) Update Deployment Architecture Overview section
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786228#comment-13786228 ] Travis Graham commented on CLOUDSTACK-4799: --- I linkend to local pages in the same guide and used ulink urls for pages that were in other guides. If I'm able to use the linkend to still access pages from completely different guides I can start doing that. I was thinking of a way to make doc updating for new version releases easier and used the same interpolation for $PRODUCT that spits out CloudStack with all the things that get updated on a new doc release. That would prevent things like needing to updated the version numbers whenever a new version bump happens for things like the repo info and whatever else gets updated on new releases. That of course will be dependent on whether old docs get rebuilt or not, but if they are, I'm guessing that would happen in their own branch that isn't master. Master would refer to the most current live version and any other feature branch would have their own settings that are particular to the version of CS that's current for the docs. I'm not sure how that's setup in Publican, but I would think making that aspect of the docs more DRY would be a nice time saver for rolling out new versions of the docs. If that's something that's do able I'd be happy to get that rolled into one of the patches I'm rolling out. I also need to get Publican setup locally so I can "test" the changes before sending out patches. I see Daan asked about getting that setup, so I'll work with the link that was provided and see if there's any issues I come across (there was mention of having to tweak the perl scripts). > Update Deployment Architecture Overview section > --- > > Key: CLOUDSTACK-4799 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4799 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Travis Graham > Labels: documentaion > Fix For: 4.2.1 > > Attachments: deployment-architecture-overview.patch > > > Adds in links to other docs it only loosely references by name and adds the > Primary Storage info about being zone wide for 4.2. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4799) Update Deployment Architecture Overview section
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786194#comment-13786194 ] David Nalley commented on CLOUDSTACK-4799: -- Travis: Why are we using linkend on some, and urls on others? I am reticent to put version specific urls in documents as that becomes a maintenance nightmare. --David > Update Deployment Architecture Overview section > --- > > Key: CLOUDSTACK-4799 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4799 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Travis Graham > Labels: documentaion > Fix For: 4.2.1 > > Attachments: deployment-architecture-overview.patch > > > Adds in links to other docs it only loosely references by name and adds the > Primary Storage info about being zone wide for 4.2. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-4800) Updating sections of the Cloud Infrastructure Concepts chapter of the Admin Guide
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley resolved CLOUDSTACK-4800. -- Resolution: Fixed Assignee: David Nalley Looks good - thanks for the patch commit 941c197b51e66ffea70658532c65304d7a80a1d4 Author: Travis Graham Date: Thu Oct 3 17:07:19 2013 -0400 updating sections of the Cloud Infrastructure Concepts chapter of the Admin Guide > Updating sections of the Cloud Infrastructure Concepts chapter of the Admin > Guide > - > > Key: CLOUDSTACK-4800 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4800 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Travis Graham >Assignee: David Nalley > Labels: documentation > Fix For: 4.2.1 > > Attachments: cloud-infrastructure-concepts.patch > > > Adding missing links to referenced sections of the Admin Guide and fixes a > few typos. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4811) Adding Incorrect CIDR in public ip range of zone create wizard is allowing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-4811: --- Assignee: Jayapal Reddy > Adding Incorrect CIDR in public ip range of zone create wizard is allowing > -- > > Key: CLOUDSTACK-4811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller, UI >Reporter: Jayapal Reddy >Assignee: Jayapal Reddy > Fix For: 4.2.1 > > > 1. Add a new zone from UI add zone wizard. > 2. Add incorrect cidr in in 3rd tab Setup network PUBLIC TRAFFIC > gateway netmask VLANStart IP End > IP > 10.147.52.1 255.255.25.0 52 10.147.52.100 > 10.147.52.120 > 3. UI is allowing the above config > 4. The zone will also get deployed. > 5. The problem is coming in creating the public interface in system vms. If > the interface got created problem in reaching the public network. > 6. This issue is pain to user because after deploying zone user need to > recreate zone again. Also some times user don't realise about the > misconfiguration. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-245) VPC ACLs are not stored and programmed consistently
[ https://issues.apache.org/jira/browse/CLOUDSTACK-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-245: -- Fix Version/s: (was: 4.2.0) 4.2.1 > VPC ACLs are not stored and programmed consistently > --- > > Key: CLOUDSTACK-245 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-245 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: pre-4.0.0 >Reporter: David Noland >Priority: Minor > Fix For: 4.2.1 > > > If user specifies 1.2.3.4/24 as the CIDR for an ACL the firewall rule is > being programmed as 1.2.3.0/24. Both CIDRs are correct, but it's inconsistent > to store one thing in the database and program the firewall using another > rule. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-300) Creation of compute offering allow combination of local storage + HA
[ https://issues.apache.org/jira/browse/CLOUDSTACK-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-300: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Creation of compute offering allow combination of local storage + HA > --- > > Key: CLOUDSTACK-300 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-300 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: pre-4.0.0 > Environment: Git Revision: fb88d2e9de795528e8b9f7e16d8a89eacc5a7e12 > Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git >Reporter: prashant kumar mishra >Priority: Minor > Fix For: 4.2.1 > > > HA is not supported for local storage, but crate compute offering allow user > to create a compute offering with a combination of Local storage and HA > together. we should have a check for this combination to make sure that it > should not allowed on UI/API level. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-2405) [DOC]Document change account membership
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-2405: --- Fix Version/s: (was: 4.2.0) 4.2.1 > [DOC]Document change account membership > --- > > Key: CLOUDSTACK-2405 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2405 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Parth Jagirdar > Fix For: 4.2.1 > > > A root administrator can now change the ownership of any virtual machine, > network, data disk, snapshot, template, or ISO from one account to any other > account. A domain or sub-domain administrator can do the same for items > within the domain from one account to any other account in the domain. > Additional documentation to be supplied. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-231) Tag creation using special charecters
[ https://issues.apache.org/jira/browse/CLOUDSTACK-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-231: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Tag creation using special charecters > -- > > Key: CLOUDSTACK-231 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-231 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: pre-4.0.0 > Environment: MS(rhel6.3) > Git Revision: 046e916fcf6d847e2cdf281233d2e68a8e6500f8 > Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git >Reporter: prashant kumar mishra >Priority: Minor > Fix For: 4.2.1 > > > Tag creation > - > - > steps to reproduce > > > 1-create tag on any resource(vm/template/PF/FW) > 2-provide detail key=value=some special character > EXPECTED > -- > -- > Tag creation shouldn't be happening with message "special character's are not > allowed" > ACTUAL > --- > -- > Tag creation is happening properly using special characters -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-270) Ui should not ask for a vlan range if the physical network isolation type is not VLAN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-270: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Ui should not ask for a vlan range if the physical network isolation type is > not VLAN > - > > Key: CLOUDSTACK-270 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-270 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0, 4.2.0 >Reporter: Hugo Trippaers >Assignee: Hugo Trippaers >Priority: Minor > Fix For: 4.2.1 > > > The UI currently asks to enter a VLAN range regardless of the isolation type. > However this question is irrelevant for some isolation types. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-124) NetworkGarbageCollector not cleaning up networks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-124: -- Fix Version/s: (was: 4.2.0) 4.2.1 > NetworkGarbageCollector not cleaning up networks > > > Key: CLOUDSTACK-124 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-124 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: pre-4.0.0 > Environment: KVM >Reporter: Adam Tistler >Priority: Minor > Fix For: 4.2.1 > > > Seeing an issue in version 2.2.14 with the NetworkGarbageCollector. > Basically we have a virtual network (all of whose virtual machines have been > terminated), however the network never gets cleaned up, and the virtual > router never stops. > Config: > - category: Advanced >name: network.gc.interval >value: "600" >description: Seconds to wait before checking for networks to shutdown > - category: Advanced >name: network.gc.wait >value: "600" >description: Time (in seconds) to wait before shutting down a network > that's not in used > Management logs (grepped): > 2012-08-13 13:58:01,598 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) We found network 399 to be free for the first > time. Adding it to the list: 1313360040 > 2012-08-13 14:08:01,758 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) We found network 239 to be free for the first > time. Adding it to the list: 1313360626 > 2012-08-13 14:08:01,759 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) We found network 241 to be free for the first > time. Adding it to the list: 1313360626 > 2012-08-13 14:08:01,759 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) We found network 247 to be free for the first > time. Adding it to the list: 1313360626 > 2012-08-13 14:08:01,759 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) We found network 265 to be free for the first > time. Adding it to the list: 1313360626 > 2012-08-13 14:08:01,759 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) We found network 277 to be free for the first > time. Adding it to the list: 1313360626 > 2012-08-13 14:08:01,759 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) We found network 280 to be free for the first > time. Adding it to the list: 1313360626 > 2012-08-13 14:08:01,759 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) We found network 281 to be free for the first > time. Adding it to the list: 1313360626 > 2012-08-13 14:08:01,759 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) We found network 296 to be free for the first > time. Adding it to the list: 1313360626 > 2012-08-13 14:08:01,759 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) We found network 325 to be free for the first > time. Adding it to the list: 1313360626 > 2012-08-13 14:08:01,759 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) We found network 352 to be free for the first > time. Adding it to the list: 1313360626 > 2012-08-13 14:08:01,759 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) We found network 353 to be free for the first > time. Adding it to the list: 1313360626 > 2012-08-13 14:08:01,759 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) Network 399 is still free but it's not time to > shutdown yet: 1313360040 > 2012-08-13 14:18:01,761 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) Network 239 is still free but it's not time to > shutdown yet: 1313360626 > 2012-08-13 14:18:01,761 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) Network 241 is still free but it's not time to > shutdown yet: 1313360626 > 2012-08-13 14:18:01,761 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) Network 247 is still free but it's not time to > shutdown yet: 1313360626 > 2012-08-13 14:18:01,761 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) Network 265 is still free but it's not time to > shutdown yet: 1313360626 > 2012-08-13 14:18:01,761 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) Network 277 is still free but it's not time to > shutdown yet: 1313360626 > 2012-08-13 14:18:01,761 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) Network 280 is still free but it's not time to > shutdown yet: 1313360626 > 2012-08-13 14:18:01,761 DEBUG [cloud.network.NetworkManagerImpl] > (Network-Scavenger-1:null) Networ
[jira] [Updated] (CLOUDSTACK-315) Infrastructure view does not show capacity values
[ https://issues.apache.org/jira/browse/CLOUDSTACK-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-315: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Infrastructure view does not show capacity values > - > > Key: CLOUDSTACK-315 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-315 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0, 4.2.0 > Environment: master branch >Reporter: Rohit Yadav >Priority: Minor > Fix For: 4.2.1 > > > Goto Infrastructure, it won't post a GET request to get list of capacities, > no. of hosts, zones, routers etc.; and fails to show any capacity values. > This was observed on master branch, > head=16fa74b7293039db75fdc6851c35e194b33f2135. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-310) Failed to add host - Plugin error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-310: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Failed to add host - Plugin error > - > > Key: CLOUDSTACK-310 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-310 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Xen >Affects Versions: 4.1.0, 4.2.0 > Environment: Management server is running centos 6.2 > Host is running Xen 4.1 on ubuntu 12.04 LTS installed with xcp-xapi package > Followed the tutorial - > http://wiki.xen.org/wiki/XCP_toolstack_on_a_Debian-based_distribution_-_proposed >Reporter: Taavi Türnpuu >Priority: Minor > Fix For: 4.2.1 > > Original Estimate: 168h > Remaining Estimate: 168h > > management-server.log > 2012-10-10 12:47:44,767 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] > (consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage > UPintenance mode > 2012-10-10 12:47:45,826 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 routers. > 2012-10-10 12:48:14,767 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] > (consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage > UPintenance mode > 2012-10-10 12:48:15,820 DEBUG [storage.snapshot.SnapshotSchedulerImpl] > (SnapshotPollTask:null) Snapshot scheduler.poll is being called at 2012-10-10 > 09:48:15 GMT > 2012-10-10 12:48:15,822 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (RouterMonitor-1:null) > Found 0 running routers. > 2012-10-10 12:48:15,822 DEBUG [storage.snapshot.SnapshotSchedulerImpl] > (SnapshotPollTask:null) Got 0 snapshots to be executed at 2012-10-10 09:48:15 > GMT > 2012-10-10 12:48:15,826 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 routers. > 2012-10-10 12:48:16,045 DEBUG > [cloud.network.ExternalLoadBalancerUsageManagerImpl] > (ExternalNetworkMonitor-1:null) External load balancer devices stats > collector is running... > 2012-10-10 12:48:32,413 DEBUG [cloud.server.StatsCollector] > (StatsCollector-2:null) VmStatsCollector is running... > 2012-10-10 12:48:32,413 DEBUG [cloud.server.StatsCollector] > (StatsCollector-3:null) HostStatsCollector is running... > 2012-10-10 12:48:32,855 DEBUG [cloud.server.StatsCollector] > (StatsCollector-2:null) StorageCollector is running... > 2012-10-10 12:48:44,767 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] > (consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage > UPintenance mode > 2012-10-10 12:48:45,788 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Running Capacity Checker ... > 2012-10-10 12:48:45,788 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) recalculating system capacity > 2012-10-10 12:48:45,788 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Executing cpu/ram capacity update > 2012-10-10 12:48:45,790 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Done executing cpu/ram capacity update > 2012-10-10 12:48:45,790 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Executing storage capacity update > 2012-10-10 12:48:45,791 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Done executing storage capacity update > 2012-10-10 12:48:45,791 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Executing capacity updates for public ip and Vlans > 2012-10-10 12:48:45,799 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Done capacity updates for public ip and Vlans > 2012-10-10 12:48:45,799 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Executing capacity updates for private ip > 2012-10-10 12:48:45,806 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Done executing capacity updates for private ip > 2012-10-10 12:48:45,806 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Done recalculating system capacity > 2012-10-10 12:48:45,827 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 routers. > 2012-10-10 12:48:45,831 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Done running Capacity Checker ... > 2012-10-10 12:49:14,767 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] > (consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage > UPintenance mode > 2012-10-10 12:49:15,826 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 routers. > 2012-10-10 12:49:32,416 DEBUG [cloud.server.StatsCollector] > (StatsCollector-2:null) V
[jira] [Updated] (CLOUDSTACK-337) Create SELinux policy for KVM agent
[ https://issues.apache.org/jira/browse/CLOUDSTACK-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-337: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Create SELinux policy for KVM agent > --- > > Key: CLOUDSTACK-337 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-337 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Reporter: David Nalley >Assignee: David Nalley > Fix For: 4.2.1 > > > We currently advise folks to disable SELinux, which is BAD. My plan is to > create a policy that we install at runtime. > I'll be using this ticket as a collection point for logs. > Release Planning: > Dev List Discussion: unknown > Functional Spec: N/A > Feature branch: unknown -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-630) Redo storage orchestration for volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-630: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Redo storage orchestration for volume > - > > Key: CLOUDSTACK-630 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-630 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Reporter: Alex Huang > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-338) Unique Names of Disk and Service Offerings in the database are prefixed with "Cloud.com" String
[ https://issues.apache.org/jira/browse/CLOUDSTACK-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-338: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Unique Names of Disk and Service Offerings in the database are prefixed with > "Cloud.com" String > --- > > Key: CLOUDSTACK-338 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-338 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.1.0, 4.2.0 >Reporter: Chandan Purushothama >Priority: Minor > Fix For: 4.2.1 > > > Unique names of disk and service offerings in the database are prefixed with > "Cloud.com" string. > mysql> select id,name,unique_name from disk_offering; > ++--++ > | id | name | unique_name| > ++--++ > | 1 | Small Instance | Cloud.Com-Small Instance | > | 2 | Medium Instance | Cloud.Com-Medium Instance | > | 3 | Small| Cloud.Com-Small| > | 4 | Medium | Cloud.Com-Medium | > | 5 | Large| Cloud.Com-Large| > | 6 | Custom | Cloud.Com-Custom | > | 7 | System Offering For Secondary Storage VM | Cloud.com-SecondaryStorage | > | 8 | System Offering For Console Proxy| Cloud.com-ConsoleProxy | > | 9 | System Offering For Software Router | Cloud.Com-SoftwareRouter | > | 10 | System Offering For Elastic LB VM| Cloud.Com-ElasticLBVm | > ++--++ > 10 rows in set (0.00 sec) > === > JARs version Information: > === > This is the version information for the manifests in the JAR files. > Implementation_Version: 2.2.20121012230921 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-317) get xcp 1.5 into an advanced network zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-317: -- Fix Version/s: (was: 4.2.0) 4.2.1 > get xcp 1.5 into an advanced network zone > - > > Key: CLOUDSTACK-317 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-317 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.0 > Environment: Cloudstack 4.0.0/ubuntu 12.04 LTS for management > server/xcp 1.5 appliance centos from xen.org >Reporter: benoit lair > Fix For: 4.2.1 > > > I'm trying to get my xcp 1.5 onto cloudstack. > After the well known-tricks on NFS python scripts and packages xs:main, i can > get my xcp on a basic network zone. > But when i try to get my xcp 1.5 onto an advanced network zone, i got errors. > Here is the log entries when i try to get it working. > 2012-10-11 15:32:30,347 DEBUG [xen.resource.XenServerConnectionPool] > (catalina-exec-4:null) Logging on as the master to 172.20.0.7 > 2012-10-11 15:32:30,438 INFO [xen.discoverer.XcpServerDiscoverer] > (catalina-exec-4:null) Found host xenserver-xcp-vps-07 ip=172.20.0.7 product > version=1.4.90 > 2012-10-11 15:32:30,610 DEBUG [xen.resource.CitrixResourceBase] > (catalina-exec-4:null) Management network is on > pif=2994f899-f449-178f-7da4-bf1ecdbd8259 > 2012-10-11 15:32:30,621 WARN [xen.resource.CitrixResourceBase] > (catalina-exec-4:null) Unable to get host information for 172.20.0.7 > java.lang.NullPointerException > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.getHostInfo(CitrixResourceBase.java:4331) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.initialize(CitrixResourceBase.java:4460) > at > com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1598) > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:544) > at com.cloud.api.commands.AddHostCmd.execute(AddHostCmd.java:140) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:615) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:744) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2012-10-11 15:32:30,622 WARN [xen.resource.CitrixResourceBase] > (catalina-exec-4:null) Unable to get host information for 172.20.0.7 > 2012-10-11 15:32:30,622 INFO [cloud.resource.ResourceManagerImpl] > (catalina-exec-4:null) Unable to fully initialize the agent because no > StartupCommands are returned > 2012-10-11 15:32:30,622 INFO [cloud.resource.ResourceManagerImpl] > (catalina-exec-4:null) server resources successfully discovered by XCP Agent > 2012-10-11 15:32:30,622 WARN [cloud.api.ApiDispatcher] > (catalina-exec-4:null) class com.cloud.api.ServerApiException : Failed to add > host > 2012-10-11 15:32:52,774 DEBUG [storage.secondary.S
[jira] [Updated] (CLOUDSTACK-633) Redo the orchestration for snapshots
[ https://issues.apache.org/jira/browse/CLOUDSTACK-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-633: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Redo the orchestration for snapshots > > > Key: CLOUDSTACK-633 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-633 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Reporter: Alex Huang > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-469) CloudStack Documentation Landing Page has Alignment Issues
[ https://issues.apache.org/jira/browse/CLOUDSTACK-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-469: -- Fix Version/s: (was: 4.2.0) 4.2.1 > CloudStack Documentation Landing Page has Alignment Issues > -- > > Key: CLOUDSTACK-469 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-469 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Website >Affects Versions: 4.0.0 >Reporter: Radhika Nair >Assignee: Joe Brockmeier >Priority: Minor > Fix For: 4.2.1 > > Attachments: landing-page.png > > > There is a text alignment issue (extra text) in the Apache CloudStack > Documentation landing page. The page at > http://incubator.apache.org/cloudstack/docs/en-US/index.html shows two > "Welcome" texts in the page. One is extra. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-458) xen:snapshots:Storage gc fail to clean the failed snapshot images from secondarystorage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-458: -- Fix Version/s: (was: 4.2.0) 4.2.1 > xen:snapshots:Storage gc fail to clean the failed snapshot images from > secondarystorage > --- > > Key: CLOUDSTACK-458 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-458 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Snapshot >Affects Versions: 4.0.0 >Reporter: deepti dohare >Assignee: deepti dohare >Priority: Minor > Fix For: 4.2.1 > > > After storage cleanup still see the snapshot image oin the secondary storage > snapshot folder for the failure snapshots > In this case : next hourly snapshot was successful but previous snapshot was > stuck in backingupstate > Steps: > *** > 1.Deploy a VM and set concurrent.snapshots.threshold.per host to 2 > 2.Once its successful,schedule the recurring snapshots hourly on the root > volume and also perform snapshot on other instance volumes > 3.configure the storage.cleanup.interval to 150 and restart the > cloud-management service while hourly snapshot on root volume is in progress > 4.check the secondary storage snapshot folder > 5. after few hours,delete all the created snapshots from Cloudstack and check > the storage cleanup thread cleansup all the snapshots form the snapshot > folder or not. > Actual result: > step4:snapshots job failed and secondary storage has copied image file and > database shows snapshot job status as "Backing UP" > next hourly snapshot was successful. > Step5: > It cleans all the successful hourly snapshot images except the failed > snapshot image files > Expected result: > ** > Storage GC should clean all image files exists in the snapshot folder when we > delete the all the snapshots from Cloud stack. > also when previous hourly snapshot stuck in backing up state ,the next hourly > snapshot is successful,Cloudstack should intelligent enough to update the > status of failure jobs properly. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-632) Start a new VM with the new orchestration
[ https://issues.apache.org/jira/browse/CLOUDSTACK-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-632: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Start a new VM with the new orchestration > - > > Key: CLOUDSTACK-632 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-632 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Reporter: Alex Huang > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-631) Create interfaces for Storage Provisioning Plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-631: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Create interfaces for Storage Provisioning Plugin > - > > Key: CLOUDSTACK-631 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-631 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Reporter: Alex Huang > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-634) Introduce plugins for the provisioning of the snapshots
[ https://issues.apache.org/jira/browse/CLOUDSTACK-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-634: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Introduce plugins for the provisioning of the snapshots > --- > > Key: CLOUDSTACK-634 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-634 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Reporter: Alex Huang > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-818) Document Dedicate Pod, Cluster or Host to a domain
[ https://issues.apache.org/jira/browse/CLOUDSTACK-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-818: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Document Dedicate Pod, Cluster or Host to a domain > -- > > Key: CLOUDSTACK-818 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-818 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.2.1 > > > Dedicate Pod, Cluster or Host to a domain- Documentation -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-773) Document Object Store-Integration with CS as secondary Storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-773: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Document Object Store-Integration with CS as secondary Storage > -- > > Key: CLOUDSTACK-773 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-773 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.2.1 > > > Document Object Store-Integration with CS as secondary Storage -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-635) Move the existing provisioning code into plugins
[ https://issues.apache.org/jira/browse/CLOUDSTACK-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-635: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Move the existing provisioning code into plugins > > > Key: CLOUDSTACK-635 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-635 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Reporter: Alex Huang > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-815) Document AWS Style Regions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-815: -- Fix Version/s: (was: 4.2.0) (was: 4.1.0) 4.2.1 > Document AWS Style Regions > -- > > Key: CLOUDSTACK-815 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-815 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Sangeetha Hariharan > Fix For: 4.2.1 > > > Document AWS Style Regions -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-823) Document any changes to the baremetal provisioning feature.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-823: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Document any changes to the baremetal provisioning feature. > --- > > Key: CLOUDSTACK-823 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-823 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-827) Document new advanced searching capabilities.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-827: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Document new advanced searching capabilities. > -- > > Key: CLOUDSTACK-827 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-827 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: David Nalley > Labels: doc > Fix For: 4.2.1 > > > We need to document how the awesome new advanced search capabilities work. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-732) Add back KVM snapshot support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-732: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Add back KVM snapshot support > - > > Key: CLOUDSTACK-732 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-732 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: 4.0.0 > Environment: RHEL 6.3 >Reporter: edison su >Assignee: Fang Wang >Priority: Critical > Fix For: 4.2.1 > > > In the latest KVM(on both RHEL 6.3 and Ubuntu 12.04), it supports external > snapshot. We need to investigate the status of external snapshot, as far as I > know, it still doesn't support disk-only snapshot(taking snapshot will pause > VM for a long time, e.g. few minutes). > 1. testing external snapshot: take an external snapshot instead of default > qcow2 internal snapshot, then back it up into backup storage. Only need to > test with libvirt snapshot API, if it works, then works, no need to hack on > the qemu-kvm. > 2. test how long it will pause a VM during taking snapshot. from link [2] and > [3], only qemu-kvm-rhev supports disk-only snapshot, not sure ubuntu 12.04 > supports it or not. We need to investigate on the issue. > If item 1 and item 2(disk-only snapshot) works, then we can support default > kvm qcow2 snapshot again. > The link: > [1] > http://kashyapc.wordpress.com/2011/10/04/snapshotting-with-libvirt-for-qcow2-images/ > [2] > http://www.linux-kvm.com/content/first-look-virtual-machine-online-disk-snapshots-coming-fedora-18 > [3] http://www.redhat.com/archives/libvir-list/2012-July/msg00782.html -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-663) health monitoring for F5 load balanced instances
[ https://issues.apache.org/jira/browse/CLOUDSTACK-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-663: -- Fix Version/s: (was: 4.2.0) 4.2.1 > health monitoring for F5 load balanced instances > > > Key: CLOUDSTACK-663 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-663 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Reporter: Rajesh Battala > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-666) Health monitoring for Brocade load balanced instances
[ https://issues.apache.org/jira/browse/CLOUDSTACK-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-666: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Health monitoring for Brocade load balanced instances > - > > Key: CLOUDSTACK-666 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-666 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Reporter: Rajesh Battala > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-831) Document remote access VPN on SRX support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-831: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Document remote access VPN on SRX support > - > > Key: CLOUDSTACK-831 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-831 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Reporter: Chip Childers > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-840) [DOC] Document CLOUDSTACK-670 regarding configuration option for linked clones or lack thereof
[ https://issues.apache.org/jira/browse/CLOUDSTACK-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-840: -- Fix Version/s: (was: 4.2.0) 4.2.1 > [DOC] Document CLOUDSTACK-670 regarding configuration option for linked > clones or lack thereof > -- > > Key: CLOUDSTACK-840 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-840 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: David Nalley >Assignee: Jessica Tomechak > Fix For: 4.2.1 > > > Add documentation for the configuration option about use (or not) of linked > clones. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-878) Document S3-backed Secondary Storage Feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-878: -- Fix Version/s: (was: 4.2.0) 4.2.1 > Document S3-backed Secondary Storage Feature > > > Key: CLOUDSTACK-878 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-878 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
