[jira] [Assigned] (CLOUDSTACK-7283) Allow regular user to execute listUsers API call
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair reassigned CLOUDSTACK-7283: Assignee: (was: Radhika Nair) Allow regular user to execute listUsers API call Key: CLOUDSTACK-7283 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7283 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Doc Affects Versions: 4.5.0 Reporter: Alena Prokharchyk Fix For: 4.5.0 Since normal-user role can have access to listAccounts API that returns user info + he can update users info by calling updateUser, he should have an access to listUsers API. The response should return his user info only. Other users belonging to the same user's account, shouldn't be returned. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-7283) Allow regular user to execute listUsers API call
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair reassigned CLOUDSTACK-7283: Assignee: (was: Radhika Nair) Allow regular user to execute listUsers API call Key: CLOUDSTACK-7283 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7283 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Doc Affects Versions: 4.5.0 Reporter: Alena Prokharchyk Fix For: 4.5.0 Since normal-user role can have access to listAccounts API that returns user info + he can update users info by calling updateUser, he should have an access to listUsers API. The response should return his user info only. Other users belonging to the same user's account, shouldn't be returned. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-6243) [Doc] Document XS-CS Integration
Radhika Nair created CLOUDSTACK-6243: Summary: [Doc] Document XS-CS Integration Key: CLOUDSTACK-6243 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6243 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: Radhika Nair -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6074) [Doc] System Implementation Guide
Radhika Nair created CLOUDSTACK-6074: Summary: [Doc] System Implementation Guide Key: CLOUDSTACK-6074 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6074 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Priority: Minor Requirement from Iliyas Shirol, InMobi. System Implementation Guide which has all the set of activities and tracks everything while deploying a private cloud. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5289) [doc] Document cpu socket count of hosts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-5289. -- Resolution: Fixed [doc] Document cpu socket count of hosts Key: CLOUDSTACK-5289 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5289 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5289) [doc] Document cpu socket count of hosts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-5289: - Attachment: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf 18.2. Reporting CPU Sockets [doc] Document cpu socket count of hosts Key: CLOUDSTACK-5289 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5289 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-5604) [DOC] dynamic compute offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair reassigned CLOUDSTACK-5604: Assignee: Radhika Nair [DOC] dynamic compute offering -- Key: CLOUDSTACK-5604 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5604 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-5590) [Doc] Usage events for dynamic compute offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair reassigned CLOUDSTACK-5590: Assignee: Radhika Nair [Doc] Usage events for dynamic compute offering --- Key: CLOUDSTACK-5590 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5590 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5590) [Doc] Usage events for dynamic compute offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-5590. -- Resolution: Fixed [Doc] Usage events for dynamic compute offering --- Key: CLOUDSTACK-5590 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5590 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5590) [Doc] Usage events for dynamic compute offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-5590: - Attachment: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf 8.1.1. Custom Compute Offering [Doc] Usage events for dynamic compute offering --- Key: CLOUDSTACK-5590 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5590 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5604) [DOC] dynamic compute offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-5604: - Attachment: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf 8.1.1. Custom Compute Offering [DOC] dynamic compute offering -- Key: CLOUDSTACK-5604 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5604 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf, Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5604) [DOC] dynamic compute offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-5604. -- Resolution: Fixed [DOC] dynamic compute offering -- Key: CLOUDSTACK-5604 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5604 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf, Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5943) [doc] Palo Alto Firewall
Radhika Nair created CLOUDSTACK-5943: Summary: [doc] Palo Alto Firewall Key: CLOUDSTACK-5943 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5943 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Radhika Nair Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5940) [doc] Publishing Alerts Via CS Root API
Radhika Nair created CLOUDSTACK-5940: Summary: [doc] Publishing Alerts Via CS Root API Key: CLOUDSTACK-5940 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5940 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5926) [Doc] Create 4.3 Release Notes
Radhika Nair created CLOUDSTACK-5926: Summary: [Doc] Create 4.3 Release Notes Key: CLOUDSTACK-5926 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5926 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5289) [doc] Document cpu socket count of hosts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13878472#comment-13878472 ] Radhika Nair commented on CLOUDSTACK-5289: -- overview added to the RN [doc] Document cpu socket count of hosts Key: CLOUDSTACK-5289 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5289 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-1001) Doc - Hyper V Support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-1001: - Attachment: Apache_CloudStack-4.3.0-Installation_Guide-en-US.pdf See the following : 8.3. Installing Hyper-V for CloudStack 6.7.2. Adding Primary Storage (SMB-related changes) 6.8.2. Adding Secondary Storage (SMB-related changes) Doc - Hyper V Support - Key: CLOUDSTACK-1001 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1001 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc, Management Server, Template, UI Reporter: Sudha Ponnaganti Assignee: Radhika Nair Fix For: 4.3.0 Attachments: Apache_CloudStack-4.3.0-Installation_Guide-en-US.pdf Need to document Hyper V Support -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-1001) Doc - Hyper V Support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13873181#comment-13873181 ] Radhika Nair commented on CLOUDSTACK-1001: -- commit 6b6526b7ad856ff2a4b24578a431bdb956d7fc1a Author: Radhika PC radhika.puthiyet...@citrix.com Date: Thu Jan 16 14:15:24 2014 +0530 CLOUDSTACK-1001 hyper V documentation on SMB commit c6069b1d0bb0b286236aacb70e316747249b4e7e Author: Radhika PC radhika.puthiyet...@citrix.com Date: Thu Jan 16 14:06:06 2014 +0530 CLOUDSTACK-1001 hyper V documentation draft in progress Doc - Hyper V Support - Key: CLOUDSTACK-1001 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1001 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc, Management Server, Template, UI Reporter: Sudha Ponnaganti Assignee: Radhika Nair Fix For: 4.3.0 Need to document Hyper V Support -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5288) [DOC]Document VR Upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-5288: - Attachment: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf Enhanced Upgrade for Virtual Routers ( 232), [DOC]Document VR Upgrade Key: CLOUDSTACK-5288 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5288 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5288) [DOC]Document VR Upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-5288: - Attachment: (was: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf) [DOC]Document VR Upgrade Key: CLOUDSTACK-5288 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5288 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5292) [doc] Document Monitering services in virtual router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-5292: - Attachment: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf 16.5.4. Service Monitoring Tool for Virtual Router [doc] Document Monitering services in virtual router Key: CLOUDSTACK-5292 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5292 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf, Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5847) [Hyper-V] [doc] Document creation of external vswitch for Hyper-V 2012 R2 (unlike Hyper-V running on Windows)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13867725#comment-13867725 ] Radhika Nair commented on CLOUDSTACK-5847: -- Added to the Prerequisite checklist section [Hyper-V] [doc] Document creation of external vswitch for Hyper-V 2012 R2 (unlike Hyper-V running on Windows) - Key: CLOUDSTACK-5847 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5847 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Environment: Hyper-V Reporter: Sowmya Krishnan Assignee: Radhika Nair Fix For: 4.3.0 For Hyper-V 2012 R2, we need to create an external vswitch manually before adding the host to CloudStack. This needs to be documented. This can be done from UI (provided the host is added to any Hyper-V manager) In the manager, click on the host - Virtual Switch Manager - New Virtual Switch - External network (choose the NIC adapter) - Apply This is in contrast to Hyper-V running on Windows 2012 R2, where it gets created automatically. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5218) CLONE - [Doc] Make VMware vCenter session timeout value configurable.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865339#comment-13865339 ] Radhika Nair commented on CLOUDSTACK-5218: -- commit b26878d17961129f2218f442c2fae73b45496bb7 Author: Radhika PC radhika.puthiyet...@citrix.com Date: Wed Jan 8 17:10:44 2014 +0530 CLOUDSTACK-5218 vmware timeout global config CLONE - [Doc] Make VMware vCenter session timeout value configurable. - Key: CLOUDSTACK-5218 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5218 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Likitha Shetty Assignee: Radhika Nair Priority: Critical Labels: documentation Fix For: 4.3.0 We see socket timeout errors in a VMware setup if a VMware task (RelocateVM_Task, CloneVM_Task etc.) takes more than 20 minutes. Add a global config 'vmware.vcenter.session.timeout' to make the vCenter session timeout value configurable. Note that VMware tasks like CloneVM_Task take longer if we use the default full-clone mode and a slow storage. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5218) CLONE - [Doc] Make VMware vCenter session timeout value configurable.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865342#comment-13865342 ] Radhika Nair commented on CLOUDSTACK-5218: -- commit f04070748a784e3b73427975d9c91451eb510787 Author: Radhika PC radhika.puthiyet...@citrix.com Date: Wed Jan 8 17:10:44 2014 +0530 CLOUDSTACK-5218 vmware timeout global config CLONE - [Doc] Make VMware vCenter session timeout value configurable. - Key: CLOUDSTACK-5218 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5218 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Likitha Shetty Assignee: Radhika Nair Priority: Critical Labels: documentation Fix For: 4.3.0 We see socket timeout errors in a VMware setup if a VMware task (RelocateVM_Task, CloneVM_Task etc.) takes more than 20 minutes. Add a global config 'vmware.vcenter.session.timeout' to make the vCenter session timeout value configurable. Note that VMware tasks like CloneVM_Task take longer if we use the default full-clone mode and a slow storage. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5218) CLONE - [Doc] Make VMware vCenter session timeout value configurable.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-5218. -- Resolution: Fixed CLONE - [Doc] Make VMware vCenter session timeout value configurable. - Key: CLOUDSTACK-5218 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5218 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Likitha Shetty Assignee: Radhika Nair Priority: Critical Labels: documentation Fix For: 4.3.0 We see socket timeout errors in a VMware setup if a VMware task (RelocateVM_Task, CloneVM_Task etc.) takes more than 20 minutes. Add a global config 'vmware.vcenter.session.timeout' to make the vCenter session timeout value configurable. Note that VMware tasks like CloneVM_Task take longer if we use the default full-clone mode and a slow storage. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5845) [doc] Document Heterogeneous Secondary Storage Not Supported in Region
Radhika Nair created CLOUDSTACK-5845: Summary: [doc] Document Heterogeneous Secondary Storage Not Supported in Region Key: CLOUDSTACK-5845 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5845 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: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 Current implementation cannot have two zones, one using NFS secondary, the other using S3 secondary. CloudStack does not support heterogeneous secondary storages in a Region. There is a limitation of our support for using S3 as Region-wide secondary storage. In a cloud, if you add S3 as a secondary storage, you cannot have other zone-wide secondary storage existing; For example, if you have an NFS secondary storage, you cannot add a S3 as secondary storage. If you want to use S3 as secondary storage, then you can add your NFS as S3 staging store only. Details are This is documented in the design doc published on ACS https://cwiki.apache.org/confluence/display/CLOUDSTACK/Storage+Backup+Object+Store+Plugin+Framework, maybe release notes didn't state that clearly. In 4.3, we will support migration NFS to S3 by automatically converting existing NFS secondary storage to S3 staging stores. See https://cwiki.apache.org/confluence/display/CLOUDSTACK/Migration+of+NFS+Secondary+Storage+to+Object+Store for details. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5845) [doc] Document Heterogeneous Secondary Storage Not Supported in Region
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866357#comment-13866357 ] Radhika Nair commented on CLOUDSTACK-5845: -- commit b7f65bdcc98516fe0ef7714adbdf3a72c2d0ca63 Author: Radhika PC radhika.puthiyet...@citrix.com Date: Thu Jan 9 11:39:10 2014 +0530 CLOUDSTACK-5845 Document Heterogeneous Secondary Storage Not Supported in Region [doc] Document Heterogeneous Secondary Storage Not Supported in Region -- Key: CLOUDSTACK-5845 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5845 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: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 Current implementation cannot have two zones, one using NFS secondary, the other using S3 secondary. CloudStack does not support heterogeneous secondary storages in a Region. There is a limitation of our support for using S3 as Region-wide secondary storage. In a cloud, if you add S3 as a secondary storage, you cannot have other zone-wide secondary storage existing; For example, if you have an NFS secondary storage, you cannot add a S3 as secondary storage. If you want to use S3 as secondary storage, then you can add your NFS as S3 staging store only. Details are This is documented in the design doc published on ACS https://cwiki.apache.org/confluence/display/CLOUDSTACK/Storage+Backup+Object+Store+Plugin+Framework, maybe release notes didn't state that clearly. In 4.3, we will support migration NFS to S3 by automatically converting existing NFS secondary storage to S3 staging stores. See https://cwiki.apache.org/confluence/display/CLOUDSTACK/Migration+of+NFS+Secondary+Storage+to+Object+Store for details. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5845) [doc] Document Heterogeneous Secondary Storage Not Supported in Region
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866358#comment-13866358 ] Radhika Nair commented on CLOUDSTACK-5845: -- commit 36c7d4e7fe2b47750425a6a10c55ae59901b689c Author: Radhika PC radhika.puthiyet...@citrix.com Date: Thu Jan 9 11:39:10 2014 +0530 CLOUDSTACK-5845 Document Heterogeneous Secondary Storage Not Supported in Region [doc] Document Heterogeneous Secondary Storage Not Supported in Region -- Key: CLOUDSTACK-5845 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5845 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: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 Current implementation cannot have two zones, one using NFS secondary, the other using S3 secondary. CloudStack does not support heterogeneous secondary storages in a Region. There is a limitation of our support for using S3 as Region-wide secondary storage. In a cloud, if you add S3 as a secondary storage, you cannot have other zone-wide secondary storage existing; For example, if you have an NFS secondary storage, you cannot add a S3 as secondary storage. If you want to use S3 as secondary storage, then you can add your NFS as S3 staging store only. Details are This is documented in the design doc published on ACS https://cwiki.apache.org/confluence/display/CLOUDSTACK/Storage+Backup+Object+Store+Plugin+Framework, maybe release notes didn't state that clearly. In 4.3, we will support migration NFS to S3 by automatically converting existing NFS secondary storage to S3 staging stores. See https://cwiki.apache.org/confluence/display/CLOUDSTACK/Migration+of+NFS+Secondary+Storage+to+Object+Store for details. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5845) [doc] Document Heterogeneous Secondary Storage Not Supported in Region
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-5845: - Labels: Documentation (was: ) [doc] Document Heterogeneous Secondary Storage Not Supported in Region -- Key: CLOUDSTACK-5845 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5845 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: Radhika Nair Assignee: Radhika Nair Labels: Documentation Fix For: 4.3.0 Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf Current implementation cannot have two zones, one using NFS secondary, the other using S3 secondary. CloudStack does not support heterogeneous secondary storages in a Region. There is a limitation of our support for using S3 as Region-wide secondary storage. In a cloud, if you add S3 as a secondary storage, you cannot have other zone-wide secondary storage existing; For example, if you have an NFS secondary storage, you cannot add a S3 as secondary storage. If you want to use S3 as secondary storage, then you can add your NFS as S3 staging store only. Details are This is documented in the design doc published on ACS https://cwiki.apache.org/confluence/display/CLOUDSTACK/Storage+Backup+Object+Store+Plugin+Framework, maybe release notes didn't state that clearly. In 4.3, we will support migration NFS to S3 by automatically converting existing NFS secondary storage to S3 staging stores. See https://cwiki.apache.org/confluence/display/CLOUDSTACK/Migration+of+NFS+Secondary+Storage+to+Object+Store for details. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5845) [doc] Document Heterogeneous Secondary Storage Not Supported in Region
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-5845: - Attachment: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf 2.7. About Secondary Storage (12) 7.8.2. Adding Secondary Storage (60) [doc] Document Heterogeneous Secondary Storage Not Supported in Region -- Key: CLOUDSTACK-5845 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5845 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: Radhika Nair Assignee: Radhika Nair Labels: Documentation Fix For: 4.3.0 Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf Current implementation cannot have two zones, one using NFS secondary, the other using S3 secondary. CloudStack does not support heterogeneous secondary storages in a Region. There is a limitation of our support for using S3 as Region-wide secondary storage. In a cloud, if you add S3 as a secondary storage, you cannot have other zone-wide secondary storage existing; For example, if you have an NFS secondary storage, you cannot add a S3 as secondary storage. If you want to use S3 as secondary storage, then you can add your NFS as S3 staging store only. Details are This is documented in the design doc published on ACS https://cwiki.apache.org/confluence/display/CLOUDSTACK/Storage+Backup+Object+Store+Plugin+Framework, maybe release notes didn't state that clearly. In 4.3, we will support migration NFS to S3 by automatically converting existing NFS secondary storage to S3 staging stores. See https://cwiki.apache.org/confluence/display/CLOUDSTACK/Migration+of+NFS+Secondary+Storage+to+Object+Store for details. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5845) [doc] Document Heterogeneous Secondary Storage Not Supported in Region
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-5845: - Status: Ready To Review (was: In Progress) [doc] Document Heterogeneous Secondary Storage Not Supported in Region -- Key: CLOUDSTACK-5845 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5845 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: Radhika Nair Assignee: Radhika Nair Labels: Documentation Fix For: 4.3.0 Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf Current implementation cannot have two zones, one using NFS secondary, the other using S3 secondary. CloudStack does not support heterogeneous secondary storages in a Region. There is a limitation of our support for using S3 as Region-wide secondary storage. In a cloud, if you add S3 as a secondary storage, you cannot have other zone-wide secondary storage existing; For example, if you have an NFS secondary storage, you cannot add a S3 as secondary storage. If you want to use S3 as secondary storage, then you can add your NFS as S3 staging store only. Details are This is documented in the design doc published on ACS https://cwiki.apache.org/confluence/display/CLOUDSTACK/Storage+Backup+Object+Store+Plugin+Framework, maybe release notes didn't state that clearly. In 4.3, we will support migration NFS to S3 by automatically converting existing NFS secondary storage to S3 staging stores. See https://cwiki.apache.org/confluence/display/CLOUDSTACK/Migration+of+NFS+Secondary+Storage+to+Object+Store for details. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-5794) [Hyper-v] Specify username and domain name together in the username field while adding host in Hyper-v cluster
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair reassigned CLOUDSTACK-5794: Assignee: Radhika Nair (was: Devdeep Singh) [Hyper-v] Specify username and domain name together in the username field while adding host in Hyper-v cluster -- Key: CLOUDSTACK-5794 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5794 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc, Hypervisor Controller Affects Versions: 4.3.0 Environment: Hyper-v cluster Reporter: Sanjeev N Assignee: Radhika Nair Labels: hyper-V,, hyper-v, hyperv Fix For: 4.3.0 Attachments: hyprv-host.PNG In Hyper-v all the hosts are domain joined hosts. So while adding a host in hyper-v cluster Admin should pass the domain name and username using username parameter itself. Pass the username parameter as below: username=BLR\sanjeev -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5292) [doc] Document Monitering services in virtual router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-5292: - Attachment: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf [doc] Document Monitering services in virtual router Key: CLOUDSTACK-5292 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5292 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-3466) [DOC] VM Migration across VMWARE clusters which are added with different switches(StandardSwith,DVS,Nexus) is not supported
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-3466: - Labels: Releasenotes (was: ) [DOC] VM Migration across VMWARE clusters which are added with different switches(StandardSwith,DVS,Nexus) is not supported Key: CLOUDSTACK-3466 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3466 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: Sailaja Mada Assignee: Jessica Tomechak Labels: Releasenotes Fix For: 4.2.1 Steps: 1. Tried to migrate VM from VMWARE DVS to Stand Vswitch cluster. It failed as host added with standard switch does not have VDS . DVS has cluster scope. Hence migration of VM is supported across cluster with DVS as the backend vswitch. But if another cluster has vswitch as backend then we don’t support migration between those clusters with different backend vswitches This has to be documented . Details of the error log : 2013-07-05 16:08:11,648 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-100:job-243) release mem from host: 6, old used: 536870912,reserved: 0, total: 34346127360; new used: 0,reserved:0; movedfromreserved: false,moveToReserveredfalse 2013-07-05 16:08:11,685 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-100:job-243) Unexpected exception while executing org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd com.cloud.utils.exception.CloudRuntimeException: Failed to migrated vm VM[User|instance2] along with its volumes. com.cloud.utils.exception.CloudRuntimeException: Error while migrating the vm VM[User|instance2] to host Host[-6-Routing]. Exception: java.lang.RuntimeException Message: Network card 'Network adapter 1' has a DVPort backing, which is not supported. This could be because the host does not support VDS or because the host has not joined a VDS. Stack: java.lang.RuntimeException: Network card 'Network adapter 1' has a DVPort backing, which is not supported. This could be because the host does not support VDS or because the host has not joined a VDS. at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290) at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.migrate(VirtualMachineMO.java:329) at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3638) at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:420) at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266) 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) at com.cloud.storage.VolumeManagerImpl.migrateVolumes(VolumeManagerImpl.java:2177) at com.cloud.vm.VirtualMachineManagerImpl.migrateWithStorage(VirtualMachineManagerImpl.java:1682) at com.cloud.vm.UserVmManagerImpl.migrateVirtualMachineWithVolume(UserVmManagerImpl.java:4035) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd.execute(MigrateVirtualMachineWithVolumeCmd.java:137) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at
[jira] [Commented] (CLOUDSTACK-3466) [DOC] VM Migration across VMWARE clusters which are added with different switches(StandardSwith,DVS,Nexus) is not supported
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863925#comment-13863925 ] Radhika Nair commented on CLOUDSTACK-3466: -- This should be release noted. [DOC] VM Migration across VMWARE clusters which are added with different switches(StandardSwith,DVS,Nexus) is not supported Key: CLOUDSTACK-3466 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3466 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: Sailaja Mada Assignee: Jessica Tomechak Labels: Releasenotes Fix For: 4.2.1 Steps: 1. Tried to migrate VM from VMWARE DVS to Stand Vswitch cluster. It failed as host added with standard switch does not have VDS . DVS has cluster scope. Hence migration of VM is supported across cluster with DVS as the backend vswitch. But if another cluster has vswitch as backend then we don’t support migration between those clusters with different backend vswitches This has to be documented . Details of the error log : 2013-07-05 16:08:11,648 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-100:job-243) release mem from host: 6, old used: 536870912,reserved: 0, total: 34346127360; new used: 0,reserved:0; movedfromreserved: false,moveToReserveredfalse 2013-07-05 16:08:11,685 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-100:job-243) Unexpected exception while executing org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd com.cloud.utils.exception.CloudRuntimeException: Failed to migrated vm VM[User|instance2] along with its volumes. com.cloud.utils.exception.CloudRuntimeException: Error while migrating the vm VM[User|instance2] to host Host[-6-Routing]. Exception: java.lang.RuntimeException Message: Network card 'Network adapter 1' has a DVPort backing, which is not supported. This could be because the host does not support VDS or because the host has not joined a VDS. Stack: java.lang.RuntimeException: Network card 'Network adapter 1' has a DVPort backing, which is not supported. This could be because the host does not support VDS or because the host has not joined a VDS. at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290) at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.migrate(VirtualMachineMO.java:329) at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3638) at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:420) at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266) 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) at com.cloud.storage.VolumeManagerImpl.migrateVolumes(VolumeManagerImpl.java:2177) at com.cloud.vm.VirtualMachineManagerImpl.migrateWithStorage(VirtualMachineManagerImpl.java:1682) at com.cloud.vm.UserVmManagerImpl.migrateVirtualMachineWithVolume(UserVmManagerImpl.java:4035) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd.execute(MigrateVirtualMachineWithVolumeCmd.java:137) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at
[jira] [Updated] (CLOUDSTACK-4945) [Doc] Pluggable VM Snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-4945: - Attachment: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf [Doc] Pluggable VM Snapshot --- Key: CLOUDSTACK-4945 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4945 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.3.0 Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf, Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Comment Edited] (CLOUDSTACK-5604) [DOC] dynamic compute offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13856767#comment-13856767 ] Radhika Nair edited comment on CLOUDSTACK-5604 at 1/3/14 9:33 AM: -- Updated the doc, and is posting was (Author: radhikap): Hi, Greetings and thank you for the message. I am on vacation until 5/01/14 with no access to the Internet; therefore, please expect a delay in my response. Merry X-Mas and Happy New Year ! Thanks -Radhika [DOC] dynamic compute offering -- Key: CLOUDSTACK-5604 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5604 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Radhika Nair Fix For: 4.3.0 Attachments: Apache_CloudStack-4.2.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5604) [DOC] dynamic compute offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-5604: - Attachment: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf [DOC] dynamic compute offering -- Key: CLOUDSTACK-5604 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5604 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Radhika Nair Fix For: 4.3.0 Attachments: Apache_CloudStack-4.2.0-Admin_Guide-en-US.pdf, Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5604) [DOC] dynamic compute offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-5604: - Attachment: (was: Apache_CloudStack-4.2.0-Admin_Guide-en-US.pdf) [DOC] dynamic compute offering -- Key: CLOUDSTACK-5604 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5604 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Radhika Nair Fix For: 4.3.0 Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5604) [DOC] dynamic compute offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13856767#comment-13856767 ] Radhika Nair commented on CLOUDSTACK-5604: -- Hi, Greetings and thank you for the message. I am on vacation until 5/01/14 with no access to the Internet; therefore, please expect a delay in my response. Merry X-Mas and Happy New Year ! Thanks -Radhika [DOC] dynamic compute offering -- Key: CLOUDSTACK-5604 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5604 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Radhika Nair Fix For: 4.3.0 Attachments: Apache_CloudStack-4.2.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5604) [DOC] dynamic compute offering
Radhika Nair created CLOUDSTACK-5604: Summary: [DOC] dynamic compute offering Key: CLOUDSTACK-5604 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5604 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Radhika Nair -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5604) [DOC] dynamic compute offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-5604: - Attachment: Apache_CloudStack-4.2.0-Admin_Guide-en-US.pdf [DOC] dynamic compute offering -- Key: CLOUDSTACK-5604 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5604 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Radhika Nair Fix For: 4.3.0 Attachments: Apache_CloudStack-4.2.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-4945) [Doc] Pluggable VM Snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-4945: - Attachment: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf [Doc] Pluggable VM Snapshot --- Key: CLOUDSTACK-4945 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4945 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.3.0 Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5590) [Doc] Usage events for dynamic compute offering
Radhika Nair created CLOUDSTACK-5590: Summary: [Doc] Usage events for dynamic compute offering Key: CLOUDSTACK-5590 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5590 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5287) [doc] nTier Apps 2.0 : Remote access VPN to VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837607#comment-13837607 ] Radhika Nair commented on CLOUDSTACK-5287: -- commit 351cf1a8c5e5a115ebb0094ce6df1000d6848286 Author: radhikap radhika.puthiyet...@citrix.com Date: Tue Dec 3 17:13:03 2013 +0530 CLOUDSTACK-5287 remote access VPN in VPC [doc] nTier Apps 2.0 : Remote access VPN to VPC --- Key: CLOUDSTACK-5287 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5287 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: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5298) [Doc] Wrong Netscaler Version in Admin Guide
Radhika Nair created CLOUDSTACK-5298: Summary: [Doc] Wrong Netscaler Version in Admin Guide Key: CLOUDSTACK-5298 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5298 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: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.1 At http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Admin_Guide/external-firewalls-and-load-balancers.html AutoScale version mentioned is NetScaler Release 10 Build 73.e and beyond. Change that to the correct version: NS10.0 Build 74.4006.e -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-5298) [Doc] Wrong Netscaler Version in Admin Guide
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-5298. -- Resolution: Fixed Fixed. commit a996072f64d65d16e8d3825c28b8683e392caed4 Author: radhikap radhika.puthiyet...@citrix.com Date: Thu Nov 28 12:17:48 2013 +0530 CLOUDSTACK-5298 [Doc] Wrong Netscaler Version in Admin Guide Key: CLOUDSTACK-5298 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5298 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: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.1 At http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Admin_Guide/external-firewalls-and-load-balancers.html AutoScale version mentioned is NetScaler Release 10 Build 73.e and beyond. Change that to the correct version: NS10.0 Build 74.4006.e -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5288) [DOC]Document VR Upgrade
Radhika Nair created CLOUDSTACK-5288: Summary: [DOC]Document VR Upgrade Key: CLOUDSTACK-5288 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5288 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5289) [doc] Document cpu socket count of hosts
Radhika Nair created CLOUDSTACK-5289: Summary: [doc] Document cpu socket count of hosts Key: CLOUDSTACK-5289 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5289 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5290) [doc] Document LDAP user provisioning improvements
Radhika Nair created CLOUDSTACK-5290: Summary: [doc] Document LDAP user provisioning improvements Key: CLOUDSTACK-5290 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5290 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5291) [doc] Document Site-to-Site VPN VR-to-VR
Radhika Nair created CLOUDSTACK-5291: Summary: [doc] Document Site-to-Site VPN VR-to-VR Key: CLOUDSTACK-5291 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5291 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5292) [doc] Document Monitering services in virtual router
Radhika Nair created CLOUDSTACK-5292: Summary: [doc] Document Monitering services in virtual router Key: CLOUDSTACK-5292 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5292 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5287) [doc] nTier Apps 2.0 : Remote access VPN to VPC
Radhika Nair created CLOUDSTACK-5287: Summary: [doc] nTier Apps 2.0 : Remote access VPN to VPC Key: CLOUDSTACK-5287 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5287 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: Radhika Nair Assignee: Radhika Nair -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-754) nTier Apps 2.0 : Remote access VPN to VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13833525#comment-13833525 ] Radhika Nair commented on CLOUDSTACK-754: - Please close after the doc is done. nTier Apps 2.0 : Remote access VPN to VPC - Key: CLOUDSTACK-754 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-754 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.0 Reporter: Kishan Kavala Assignee: Sheng Yang Priority: Critical Fix For: 4.3.0 This item is a sub task (2.9) of https://issues.apache.org/jira/browse/CLOUDSTACK-621 This would enable remote-users to login to their VPC network -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-5125) [doc] Release Note Known Issues, Fixed Issues, and New features
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1381#comment-1381 ] Radhika Nair commented on CLOUDSTACK-5125: -- commit 9a685a7bb0296bb01a8f3d60b305a593365b338e Author: Radhika PC radhika.puthiyet...@citrix.com Date: Tue Nov 12 16:17:11 2013 +0530 release notes for 4.2.1 CLOUDSTACK-5125 [doc] Release Note Known Issues, Fixed Issues, and New features --- Key: CLOUDSTACK-5125 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5125 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.1 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-5132) [Doc] Support for Acquiring IP Without Enabling SourceNAT Service
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1382#comment-1382 ] Radhika Nair commented on CLOUDSTACK-5132: -- documented in the RN. There is no reference in the Admin Guide about SourceNAT dependency, so nothing to be changed. [Doc] Support for Acquiring IP Without Enabling SourceNAT Service - Key: CLOUDSTACK-5132 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5132 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.1 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4708) Event types and alert types mentioned in doc are not correct
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13820977#comment-13820977 ] Radhika Nair commented on CLOUDSTACK-4708: -- commit 6a61c242e13cdd9440fd86a6c5b282ac8d70123e Author: Radhika PC radhika.puthiyet...@citrix.com Date: Wed Nov 13 11:34:24 2013 +0530 CLOUDSTACK-4708 Event types and alert types mentioned in doc are not correct Key: CLOUDSTACK-4708 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4708 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Anshul Gangwar Assignee: Radhika Nair Attachments: cloudstackalerts.txt, cloudstackevents.txt The event types and alert types mentioned in doc are not correct. They are showing old values and many events are not mentioned -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-4708) Event types and alert types mentioned in doc are not correct
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-4708. -- Resolution: Fixed Event types and alert types mentioned in doc are not correct Key: CLOUDSTACK-4708 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4708 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Anshul Gangwar Assignee: Radhika Nair Attachments: cloudstackalerts.txt, cloudstackevents.txt The event types and alert types mentioned in doc are not correct. They are showing old values and many events are not mentioned -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5126) [Doc] Release Notes 4.2.1 Upgrade
Radhika Nair created CLOUDSTACK-5126: Summary: [Doc] Release Notes 4.2.1 Upgrade Key: CLOUDSTACK-5126 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5126 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 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5125) [doc] Release Note Known Issues, Fixed Issues, and New features
Radhika Nair created CLOUDSTACK-5125: Summary: [doc] Release Note Known Issues, Fixed Issues, and New features Key: CLOUDSTACK-5125 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5125 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: Radhika Nair Assignee: Radhika Nair -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CLOUDSTACK-5003) [DOC] Documentation tasks for 4.2.1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair reassigned CLOUDSTACK-5003: Assignee: (was: Radhika Nair) [DOC] Documentation tasks for 4.2.1 --- Key: CLOUDSTACK-5003 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5003 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: Abhinandan Prateek Priority: Blocker Fix For: 4.2.1 This ticket is for following up progress on following items required · Release notes · Admin guide updates - New Features 1. XS VM Snapshots 2. Update VR to use Xen 64 bit template · Known Issues · Fixed issues -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5127) [Doc] Document XS VM Snapshot
Radhika Nair created CLOUDSTACK-5127: Summary: [Doc] Document XS VM Snapshot Key: CLOUDSTACK-5127 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5127 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 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5129) [Doc] UCS Enhancements
Radhika Nair created CLOUDSTACK-5129: Summary: [Doc] UCS Enhancements Key: CLOUDSTACK-5129 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5129 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 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5132) [Doc] Support for Acquiring IP Without Enabling SourceNAT Service
Radhika Nair created CLOUDSTACK-5132: Summary: [Doc] Support for Acquiring IP Without Enabling SourceNAT Service Key: CLOUDSTACK-5132 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5132 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.1 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5131) [Doc] Device ID Changes for XenServer
Radhika Nair created CLOUDSTACK-5131: Summary: [Doc] Device ID Changes for XenServer Key: CLOUDSTACK-5131 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5131 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.1 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5128) [Doc] Update VR to use Xen 64 bit template
Radhika Nair created CLOUDSTACK-5128: Summary: [Doc] Update VR to use Xen 64 bit template Key: CLOUDSTACK-5128 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5128 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.1 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CLOUDSTACK-5127) [Doc] Document XS VM Snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair reassigned CLOUDSTACK-5127: Assignee: Radhika Nair [Doc] Document XS VM Snapshot - Key: CLOUDSTACK-5127 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5127 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.1 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5130) [Doc] Choose Single-part or Multi-part Upload to Object Storage
Radhika Nair created CLOUDSTACK-5130: Summary: [Doc] Choose Single-part or Multi-part Upload to Object Storage Key: CLOUDSTACK-5130 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5130 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 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-5030) [Doc] Document the Procedure to create custom role in vCenter for CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-5030. -- Resolution: Fixed [Doc] Document the Procedure to create custom role in vCenter for CloudStack Key: CLOUDSTACK-5030 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5030 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: Sailaja Mada Assignee: Radhika Nair Labels: doc Fix For: 4.2.1 Attachments: CustomRolesinvCenter.html Steps: Procedure to create custom role in vCenter for CloudPlatform is described below: Requirement Elaborate minimal permissions required for a user account to be used by CloudPlatform. Back ground To manage VMware deployments, CloudPlatform need permissions for the role to manage infrastructure resources as the minimal i.e, Manage cluster/host Manage datastore/disks/files Manage port groups Manage dvPort groups Manage templates Import appliance Export a template Manage VM Manage snapshot of VM Manage custom field Solution Hence the idea is to create a role with above required minimal permissions and assign this custom role to the user designated to be used by CloudPlatform. For more robust implementation of this, the permissions could be divided into 2 roles where as each role (mapped with a user) is added to relevant object in vCenter infrastructure. Global role This is for custom attribute management - User with this role would be added to vCenter object WITHOUT propagation to child objects. Datacenter role This is for datacenter management - User with this role would be added to each of Datacenter object, WITH propagation to child objects, to be managed by this user. Detailed list of granualar permissions to be added to the global role to be used for CloudPlatform is below. Global.Manage custom attributes Global.set custom attributes Detailed list of granualar permissions to be added to the datacentre role to be used for CloudPlatform is below. Datastore.AllocateSpace Datastore.Browse Datastore.Configure Datastore.Remove file Datastore.FileManagement (Low level file operations and Update virtual machine files) dvPort group.Create dvPort group.Modify dvPort group.Policy dvPort group.Delete Folder.Create folder Folder.Delete folder Network.Assign Network.Configure Network.Remove Resource.HotMigrate (Migrate powered on vm) Resource.ColdMigrate (Migrate powered off vm) Resource.Assign virtualmachine to resource pool Resource.Assign vApp to resource pool Sessions.Validatesession Host.Configuration.Connection Host.Configuration.Security profile and firewall Host.Configuration.Maintenance Host.Configuration.Storage partition configuration Host.Configuration.SystemManagement Host.LocalOperations.Create Virtual Machine Host.LocalOperations.Delete Virtual Machine Host.LocalOperations.Reconfigure Virtual Machine Host.LocalOperations.Relayout Snapshots vApp.Export vApp.Import VirtualMachine.Config.AddExistingDisk VirtualMachine.Config.AddNewDisk VirtualMachine.Config.AdvancedConfig Virtualmachine.Configuration.Add or remove device Virtualmachine.Configuration.Change CPU Count Virtualmachine.Configuration.Change Resource Virtualmachine.Configuration.Extend Disk Virtualmachine.Configuration.Memory Virtualmachine.Configuration.Modify Device Setting Virtualmachine.Configuration.Reload from path Virtualmachine.Configuration.Rename Virtualmachine.Configuration.Remove disk Virtualmachine.Configuration.Set annotation Virtualmachine.Configuration.Settings Virtualmachine.Interaction.Answer question Virtualmachine.Interaction.Power Off Virtualmachine.Interaction.Power On VirtualMachine.Interaction.Reset Virtualmachine.Interaction.VMware Tools install VirtualMachine.Inventory.Create (New and from existing) VirtualMachine.Inventory.Register VirtualMachine.Inventory.Unregister VirtualMachine.Inventory.Remove VirtualMachine.Inventory.Move Virtualmachine.Provisioning.Allow file access Virtualmachine.Provisioning.Allow file upload Virtualmachine.Provisioning.Allow file download Virtualmachine.Provisioning.Mark as template Virtualmachine.Provisioning.Clone template Virtualmachine.Provisioning.Clone virtualmachine
[jira] [Updated] (CLOUDSTACK-5030) [Doc] Document the Procedure to create custom role in vCenter for CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-5030: - Attachment: CustomRolesinvCenter.html [Doc] Document the Procedure to create custom role in vCenter for CloudStack Key: CLOUDSTACK-5030 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5030 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: Sailaja Mada Assignee: Radhika Nair Labels: doc Fix For: 4.2.1 Attachments: CustomRolesinvCenter.html Steps: Procedure to create custom role in vCenter for CloudPlatform is described below: Requirement Elaborate minimal permissions required for a user account to be used by CloudPlatform. Back ground To manage VMware deployments, CloudPlatform need permissions for the role to manage infrastructure resources as the minimal i.e, Manage cluster/host Manage datastore/disks/files Manage port groups Manage dvPort groups Manage templates Import appliance Export a template Manage VM Manage snapshot of VM Manage custom field Solution Hence the idea is to create a role with above required minimal permissions and assign this custom role to the user designated to be used by CloudPlatform. For more robust implementation of this, the permissions could be divided into 2 roles where as each role (mapped with a user) is added to relevant object in vCenter infrastructure. Global role This is for custom attribute management - User with this role would be added to vCenter object WITHOUT propagation to child objects. Datacenter role This is for datacenter management - User with this role would be added to each of Datacenter object, WITH propagation to child objects, to be managed by this user. Detailed list of granualar permissions to be added to the global role to be used for CloudPlatform is below. Global.Manage custom attributes Global.set custom attributes Detailed list of granualar permissions to be added to the datacentre role to be used for CloudPlatform is below. Datastore.AllocateSpace Datastore.Browse Datastore.Configure Datastore.Remove file Datastore.FileManagement (Low level file operations and Update virtual machine files) dvPort group.Create dvPort group.Modify dvPort group.Policy dvPort group.Delete Folder.Create folder Folder.Delete folder Network.Assign Network.Configure Network.Remove Resource.HotMigrate (Migrate powered on vm) Resource.ColdMigrate (Migrate powered off vm) Resource.Assign virtualmachine to resource pool Resource.Assign vApp to resource pool Sessions.Validatesession Host.Configuration.Connection Host.Configuration.Security profile and firewall Host.Configuration.Maintenance Host.Configuration.Storage partition configuration Host.Configuration.SystemManagement Host.LocalOperations.Create Virtual Machine Host.LocalOperations.Delete Virtual Machine Host.LocalOperations.Reconfigure Virtual Machine Host.LocalOperations.Relayout Snapshots vApp.Export vApp.Import VirtualMachine.Config.AddExistingDisk VirtualMachine.Config.AddNewDisk VirtualMachine.Config.AdvancedConfig Virtualmachine.Configuration.Add or remove device Virtualmachine.Configuration.Change CPU Count Virtualmachine.Configuration.Change Resource Virtualmachine.Configuration.Extend Disk Virtualmachine.Configuration.Memory Virtualmachine.Configuration.Modify Device Setting Virtualmachine.Configuration.Reload from path Virtualmachine.Configuration.Rename Virtualmachine.Configuration.Remove disk Virtualmachine.Configuration.Set annotation Virtualmachine.Configuration.Settings Virtualmachine.Interaction.Answer question Virtualmachine.Interaction.Power Off Virtualmachine.Interaction.Power On VirtualMachine.Interaction.Reset Virtualmachine.Interaction.VMware Tools install VirtualMachine.Inventory.Create (New and from existing) VirtualMachine.Inventory.Register VirtualMachine.Inventory.Unregister VirtualMachine.Inventory.Remove VirtualMachine.Inventory.Move Virtualmachine.Provisioning.Allow file access Virtualmachine.Provisioning.Allow file upload Virtualmachine.Provisioning.Allow file download Virtualmachine.Provisioning.Mark as template Virtualmachine.Provisioning.Clone template Virtualmachine.Provisioning.Clone virtualmachine
[jira] [Commented] (CLOUDSTACK-4864) Create VMWare 64 bit system VM template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13812613#comment-13812613 ] Radhika Nair commented on CLOUDSTACK-4864: -- What is the documentation impact of this defect ? Is that a new template is available ? Create VMWare 64 bit system VM template --- Key: CLOUDSTACK-4864 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4864 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.2.0 Reporter: Abhinandan Prateek Assignee: Sateesh Chodapuneedi Priority: Blocker Fix For: 4.2.1 Attachments: systemvmtemplate64.ovf VMWare 64 bit template requires some custom work. Default template that is generated by jenkins has wrong cdrom setup and vmware tools, that needs to be fixed manually. Harddisk type is also incompatible. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4708) Event types and alert types mentioned in doc are not correct
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808782#comment-13808782 ] Radhika Nair commented on CLOUDSTACK-4708: -- commit 1e97c2a1b6a203eb6411cdb92717f9f55522970e Author: radhikap radhika.puthiyet...@citrix.com Date: Wed Oct 30 11:44:09 2013 +0530 CLOUDSTACK-4708 updated with latest alert types in cloudstack Event types and alert types mentioned in doc are not correct Key: CLOUDSTACK-4708 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4708 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Anshul Gangwar Assignee: Radhika Nair Attachments: cloudstackalerts.txt, cloudstackevents.txt The event types and alert types mentioned in doc are not correct. They are showing old values and many events are not mentioned -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-3243) [DOC]Wrong NFS mount point in documentation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807724#comment-13807724 ] Radhika Nair commented on CLOUDSTACK-3243: -- checked in to 4.2 https://git-wip-us.apache.org/repos/asf?p=cloudstack-docs.git;a=shortlog;h=refs/heads/4.2 and Master https://git-wip-us.apache.org/repos/asf?p=cloudstack-docs.git;a=commit;h=b74319385fc1f18faf0a733ba230738dfe81eb1b [DOC]Wrong NFS mount point in documentation --- Key: CLOUDSTACK-3243 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3243 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 Environment: KVM Reporter: Ron Wheeler Assignee: Radhika Nair Priority: Blocker Fix For: 4.2.1 At 4.5.8. Prepare the System VM Template the instructions give the following command. /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h kvm -s optional-management-server-secret-key -F In 4.5.6.2. Using the Management Server as the NFS Server the following commands were give # mkdir /primarymount # mount -t nfs management-server-name:/export/primary /primarymount # umount /primarymount # mkdir /secondarymount # mount -t nfs management-server-name:/export/secondary /secondarymount # umount /secondarymount This results in a mismatch betweenthe location of the NSF storage which causes the error: mount point /mnt/secondary doesn't exist\n Installation failed 4.5.6.1. Using a Separate NFS Server has the storage mounted at /mnt/secondary The documentation needs to be made consistent. Probably 4.5.6.2. Using the Management Server as the NFS Server needs fixing. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-3243) [DOC]Wrong NFS mount point in documentation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-3243: - Status: Ready To Review (was: In Progress) [DOC]Wrong NFS mount point in documentation --- Key: CLOUDSTACK-3243 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3243 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 Environment: KVM Reporter: Ron Wheeler Assignee: Radhika Nair Priority: Blocker Fix For: 4.2.1 At 4.5.8. Prepare the System VM Template the instructions give the following command. /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h kvm -s optional-management-server-secret-key -F In 4.5.6.2. Using the Management Server as the NFS Server the following commands were give # mkdir /primarymount # mount -t nfs management-server-name:/export/primary /primarymount # umount /primarymount # mkdir /secondarymount # mount -t nfs management-server-name:/export/secondary /secondarymount # umount /secondarymount This results in a mismatch betweenthe location of the NSF storage which causes the error: mount point /mnt/secondary doesn't exist\n Installation failed 4.5.6.1. Using a Separate NFS Server has the storage mounted at /mnt/secondary The documentation needs to be made consistent. Probably 4.5.6.2. Using the Management Server as the NFS Server needs fixing. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4708) Event types and alert types mentioned in doc are not correct
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808753#comment-13808753 ] Radhika Nair commented on CLOUDSTACK-4708: -- http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Admin_Guide/event-types.html could you please verify them and let me know what is missing ? Event types and alert types mentioned in doc are not correct Key: CLOUDSTACK-4708 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4708 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Anshul Gangwar Assignee: Radhika Nair The event types and alert types mentioned in doc are not correct. They are showing old values and many events are not mentioned -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Closed] (CLOUDSTACK-4970) [Doc] Installation Guide Error: Typo in the Ubuntu Installation Command
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair closed CLOUDSTACK-4970. [Doc] Installation Guide Error: Typo in the Ubuntu Installation Command --- Key: CLOUDSTACK-4970 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4970 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Radhika Nair Assignee: sebastien goasguen Fix For: 4.2.1 At this link: https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Installation_Guide/management-server-install-flow.html The command for installing the management server for Ubuntu is spelt incorrectly, make sure you spell management correctly if you are copying and pasting from the guide. If someone could spend the 20 seconds updating the guide, even better. (Posted on behalf of Mark van der Meulen m...@fivenynes.com) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CLOUDSTACK-482) Installation Guide Doc Error Section 4.5.7
[ https://issues.apache.org/jira/browse/CLOUDSTACK-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair reassigned CLOUDSTACK-482: --- Assignee: (was: Radhika Nair) Installation Guide Doc Error Section 4.5.7 -- Key: CLOUDSTACK-482 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-482 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.0.0 Environment: Ubuntu 12.04 LTS Reporter: Jim Leary Fix For: Future Section 4.5.7 of the Installation Guide: entries calling out /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt... are incorrect. They should be: /usr/lib/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt... -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-4970) [Doc] Installation Guide Error: Typo in the Ubuntu Installation Command
Radhika Nair created CLOUDSTACK-4970: Summary: [Doc] Installation Guide Error: Typo in the Ubuntu Installation Command Key: CLOUDSTACK-4970 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4970 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Radhika Nair At this link: https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Installation_Guide/management-server-install-flow.html The command for installing the management server for Ubuntu is spelt incorrectly, make sure you spell management correctly if you are copying and pasting from the guide. If someone could spend the 20 seconds updating the guide, even better. (Posted on behalf of Mark van der Meulen m...@fivenynes.com) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4970) [Doc] Installation Guide Error: Typo in the Ubuntu Installation Command
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-4970: - Affects Version/s: 4.2.0 [Doc] Installation Guide Error: Typo in the Ubuntu Installation Command --- Key: CLOUDSTACK-4970 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4970 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Radhika Nair At this link: https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Installation_Guide/management-server-install-flow.html The command for installing the management server for Ubuntu is spelt incorrectly, make sure you spell management correctly if you are copying and pasting from the guide. If someone could spend the 20 seconds updating the guide, even better. (Posted on behalf of Mark van der Meulen m...@fivenynes.com) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CLOUDSTACK-1001) Doc - Hyper V Support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair reassigned CLOUDSTACK-1001: Assignee: Radhika Nair Doc - Hyper V Support - Key: CLOUDSTACK-1001 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1001 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc, Management Server, Template, UI Reporter: Sudha Ponnaganti Assignee: Radhika Nair Fix For: 4.3.0 Need to document Hyper V Support -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-4945) [Doc] Pluggable VM Snapshot
Radhika Nair created CLOUDSTACK-4945: Summary: [Doc] Pluggable VM Snapshot Key: CLOUDSTACK-4945 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4945 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-4919) [Doc] Document LDAP Enhancements
Radhika Nair created CLOUDSTACK-4919: Summary: [Doc] Document LDAP Enhancements Key: CLOUDSTACK-4919 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4919 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: Radhika Nair Assignee: Radhika Nair Fix For: Future -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4879) [doc] XenServer Support Package (CSP) Information for XenServer 6.1 and Beyond Is Missing in the Installation Guide
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-4879: - Summary: [doc] XenServer Support Package (CSP) Information for XenServer 6.1 and Beyond Is Missing in the Installation Guide (was: [doc] XenServer Support Package (CSP) Information for XenServer 6.2 Is Missing in the Installation Guide) [doc] XenServer Support Package (CSP) Information for XenServer 6.1 and Beyond Is Missing in the Installation Guide --- Key: CLOUDSTACK-4879 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4879 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Need to add the following: If you are using XenServer 6.1 or greater, perform the following: a. Run the following commands: echo 1 /proc/sys/net/bridge/bridge-nf-call-iptables echo 1 /proc/sys/net/bridge/bridge-nf-call-arptables b. To persist the above changes across reboots, set the following values in the /etc/sysctl.conf file. Run the following command: sysctl -p /etc/sysctl.conf Set these to 1: net.bridge.bridge-nf-call-iptables = 1 net.bridge.bridge-nf-call-arptables = 1 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-4879) [doc] XenServer Support Package (CSP) Information for XenServer 6.2 Is Missing in the Installation Guide
Radhika Nair created CLOUDSTACK-4879: Summary: [doc] XenServer Support Package (CSP) Information for XenServer 6.2 Is Missing in the Installation Guide Key: CLOUDSTACK-4879 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4879 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Need to add the following: If you are using XenServer 6.1 or greater, perform the following: a. Run the following commands: echo 1 /proc/sys/net/bridge/bridge-nf-call-iptables echo 1 /proc/sys/net/bridge/bridge-nf-call-arptables b. To persist the above changes across reboots, set the following values in the /etc/sysctl.conf file. Run the following command: sysctl -p /etc/sysctl.conf Set these to 1: net.bridge.bridge-nf-call-iptables = 1 net.bridge.bridge-nf-call-arptables = 1 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4879) [doc] XenServer Support Package (CSP) Information for XenServer 6.1 and Beyond Is Missing in the Installation Guide
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-4879: - Fix Version/s: 4.2.1 [doc] XenServer Support Package (CSP) Information for XenServer 6.1 and Beyond Is Missing in the Installation Guide --- Key: CLOUDSTACK-4879 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4879 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Fix For: 4.2.1 Need to add the following: If you are using XenServer 6.1 or greater, perform the following: a. Run the following commands: echo 1 /proc/sys/net/bridge/bridge-nf-call-iptables echo 1 /proc/sys/net/bridge/bridge-nf-call-arptables b. To persist the above changes across reboots, set the following values in the /etc/sysctl.conf file. Run the following command: sysctl -p /etc/sysctl.conf Set these to 1: net.bridge.bridge-nf-call-iptables = 1 net.bridge.bridge-nf-call-arptables = 1 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4072) [DOC][upgrade][2.2.14 to 4.2][CentOS5 RPM builds] mysql-connector-java rpm dependency while upgrading from 2.2.14 to 4.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13791368#comment-13791368 ] Radhika Nair commented on CLOUDSTACK-4072: -- this is already included in the RN. [DOC][upgrade][2.2.14 to 4.2][CentOS5 RPM builds] mysql-connector-java rpm dependency while upgrading from 2.2.14 to 4.2 Key: CLOUDSTACK-4072 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4072 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc, Packaging Affects Versions: 4.2.0 Environment: MS : CentOS 5.6 Host : ESX 4.1 Rhel 5 builds are used to install and upgrade Reporter: Abhinav Roy Assignee: Radhika Nair Priority: Critical Fix For: 4.2.1 Steps : === 1. Install CS advanced zone setup on CentOS 5.6 management server with Rhel 5 build for 2.2.14 2. Do some operations before upgrade. 3. Upgrade to 4.2 , rhel 5 build . Upgrade fails with this dependency : [root@MS-CentOS56 CloudPlatform-4.2-4.2-55-rhel5]# ./install.sh Setting up the temporary repository... Cleaning Yum cache... Loaded plugins: fastestmirror 7 metadata files removed Welcome to the CloudPlatform Installer. What would you like to do? NOTE: For installing KVM agent, please setup EPELhttp://fedoraproject.org/wiki/EPEL yum repo first; For installing CloudPlatform on RHEL6.x, please setup distribution yum repo either from ISO or from your registeration account. 3.We detect you already have MySql server installed, you can bypass mysql install chapter in CloudPlatform installation guide. Or you can use E) to remove current mysql then re-run install.sh selecting D) to reinstall if you think existing MySql server has some trouble. For MySql downloaded from community, the script may not be able to detect it. M) Install the Management Server A) Install the Agent B) Install BareMetal Agent S) Install the Usage Monitor U) Upgrade the CloudPlatform packages installed on this computer R) Stop any running CloudPlatform services and remove the CloudPlatform packages from this computer E) Remove the MySQL server (will not remove the MySQL databases) Q) Quit u Updating the CloudPlatform and its dependencies... Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: centos.mirror.net.in * extras: centos.mirror.net.in * updates: centos.mirror.net.in base cloud-temp cloud-temp/primary cloud-temp extras updates Setting up Update Process Resolving Dependencies -- Running transaction check --- Package cloudstack-common.x86_64 0:4.2.0-SNAPSHOT.el5 set to be updated --- Package cloudstack-management.x86_64 0:4.2.0-SNAPSHOT.el5 set to be updated -- Processing Dependency: cloudstack-awsapi = 4.2.0 for package: cloudstack-management -- Processing Dependency: mysql-connector-java for package: cloudstack-management -- Running transaction check --- Package cloudstack-awsapi.x86_64 0:4.2.0-SNAPSHOT.el5 set to be updated --- Package cloudstack-management.x86_64 0:4.2.0-SNAPSHOT.el5 set to be updated -- Processing Dependency: mysql-connector-java for package: cloudstack-management -- Finished Dependency Resolution cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has depsolving problems -- Missing Dependency: mysql-connector-java is needed by package cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp) Error: Missing Dependency: mysql-connector-java is needed by package cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest The program package-cleanup is found in the yum-utils package. workaround : Download that package from http://dl.fedoraproject.org/pub/epel/5/x86_64/ follow the instructions at http://pkgs.org/centos-5-rhel-5/epel-i386/mysql-connector-java-5.1.12-2.el5.i386.rpm.html . -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-4072) [DOC][upgrade][2.2.14 to 4.2][CentOS5 RPM builds] mysql-connector-java rpm dependency while upgrading from 2.2.14 to 4.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-4072. -- Resolution: Fixed [DOC][upgrade][2.2.14 to 4.2][CentOS5 RPM builds] mysql-connector-java rpm dependency while upgrading from 2.2.14 to 4.2 Key: CLOUDSTACK-4072 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4072 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc, Packaging Affects Versions: 4.2.0 Environment: MS : CentOS 5.6 Host : ESX 4.1 Rhel 5 builds are used to install and upgrade Reporter: Abhinav Roy Assignee: Radhika Nair Priority: Critical Fix For: 4.2.1 Steps : === 1. Install CS advanced zone setup on CentOS 5.6 management server with Rhel 5 build for 2.2.14 2. Do some operations before upgrade. 3. Upgrade to 4.2 , rhel 5 build . Upgrade fails with this dependency : [root@MS-CentOS56 CloudPlatform-4.2-4.2-55-rhel5]# ./install.sh Setting up the temporary repository... Cleaning Yum cache... Loaded plugins: fastestmirror 7 metadata files removed Welcome to the CloudPlatform Installer. What would you like to do? NOTE: For installing KVM agent, please setup EPELhttp://fedoraproject.org/wiki/EPEL yum repo first; For installing CloudPlatform on RHEL6.x, please setup distribution yum repo either from ISO or from your registeration account. 3.We detect you already have MySql server installed, you can bypass mysql install chapter in CloudPlatform installation guide. Or you can use E) to remove current mysql then re-run install.sh selecting D) to reinstall if you think existing MySql server has some trouble. For MySql downloaded from community, the script may not be able to detect it. M) Install the Management Server A) Install the Agent B) Install BareMetal Agent S) Install the Usage Monitor U) Upgrade the CloudPlatform packages installed on this computer R) Stop any running CloudPlatform services and remove the CloudPlatform packages from this computer E) Remove the MySQL server (will not remove the MySQL databases) Q) Quit u Updating the CloudPlatform and its dependencies... Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: centos.mirror.net.in * extras: centos.mirror.net.in * updates: centos.mirror.net.in base cloud-temp cloud-temp/primary cloud-temp extras updates Setting up Update Process Resolving Dependencies -- Running transaction check --- Package cloudstack-common.x86_64 0:4.2.0-SNAPSHOT.el5 set to be updated --- Package cloudstack-management.x86_64 0:4.2.0-SNAPSHOT.el5 set to be updated -- Processing Dependency: cloudstack-awsapi = 4.2.0 for package: cloudstack-management -- Processing Dependency: mysql-connector-java for package: cloudstack-management -- Running transaction check --- Package cloudstack-awsapi.x86_64 0:4.2.0-SNAPSHOT.el5 set to be updated --- Package cloudstack-management.x86_64 0:4.2.0-SNAPSHOT.el5 set to be updated -- Processing Dependency: mysql-connector-java for package: cloudstack-management -- Finished Dependency Resolution cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has depsolving problems -- Missing Dependency: mysql-connector-java is needed by package cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp) Error: Missing Dependency: mysql-connector-java is needed by package cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest The program package-cleanup is found in the yum-utils package. workaround : Download that package from http://dl.fedoraproject.org/pub/epel/5/x86_64/ follow the instructions at http://pkgs.org/centos-5-rhel-5/epel-i386/mysql-connector-java-5.1.12-2.el5.i386.rpm.html . -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-4653) Update What's New Section
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-4653. -- Resolution: Fixed Update What's New Section - Key: CLOUDSTACK-4653 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4653 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.1 -- 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 ] Radhika Nair updated CLOUDSTACK-4300: - Summary: [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade (was: [Doc] [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade) [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 Assignee: Jessica Tomechak Priority: Blocker Fix For: 4.2.0 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-4731) [Doc] [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
Radhika Nair created CLOUDSTACK-4731: Summary: [Doc] [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade Key: CLOUDSTACK-4731 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4731 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Radhika Nair -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13776143#comment-13776143 ] Radhika Nair commented on CLOUDSTACK-4300: -- Created a doc sub task to document this issue. [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 Assignee: Jessica Tomechak Priority: Blocker Fix For: 4.2.0 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-4727) Update Upgrade Instructions
Radhika Nair created CLOUDSTACK-4727: Summary: Update Upgrade Instructions Key: CLOUDSTACK-4727 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4727 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Priority: Blocker 1. Before upgrading from any version to 4.2 we need to register the new 4.2 systemvm templates . This step is there in section 3.3 i.e for upgrade from 2.2.14 to 4.2, but it is missing in section 3.1 and 3.2 . 2. Section 3.1 Step 34 : it should be cloudstack-management and cloudstack-usage as the naming conventions have been changed from 4.1 onwards. Step 6 : The cloudstack 4.2 repo has not been published yet, currently at http://cloudstack.apt-get.eu/ the repo is available only for 4.0.x and 4.1.x What Indira pointed to, needs to be removed, step 6.g) and 6.h) and step 8 also need to be removed In step 6.f) It should be service cloudstack-agent stop Step 9.b) : It should be sudo yum upgrade cloudstack-client Step 9.c) : it should be sudo yum upgrade cloudstack-agent and the following line is not required [[ During the installation of cloudstack-agent, the RPM will copy your agent.properties,log4j-cloud.xml, and environment.properties from /etc/cloud/agent to /etc/cloudstack/agent ]] Step 9.d.ii) : it should be sudo yum upgrade cloudstack-usage 3. Section 3.2 Step 1.e) : The URL of the vmware systemvm template is wrong. It should be http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova . The OSType should be [[Debian GNU/Linux 7.0 (32-bit) (or the highestDebian release number available in the dropdown)]] Similarly, add templates for xenserver and kvm also. Step 7 : Delete this step, it's not needed. Step 16 : It should be cloudstack-sysvmadm 4. Section 3.3 Step 4.d) : For all the newly registered templates, make the OStype as [[Debian GNU/Linux 7.0 (32-bit) (or the highest Debian release number available in the dropdown)]] Step 13.c) : It should be /etc/cloudstack/management/components.xml Step 15.c) : It should be /etc/cloudstack/management/db.properties Step 20 : Remove this step, it's not needed Step 21.e) : It should be /etc/cloudstack/agent/agent.properties Step 23.a) : It should be cloudstack-sysvmadm 5. In addition to all this, If we are using KVM hosts as rhel6.0/6.1 then these extra steps need to be documented for each section, 3.2 and 3.3 (KVM on RHEL 6.0/6.1 only) If your existing CloudStack deployment includes one or more clusters of KVM hosts running RHEL 6.0 or RHEL 6.1, you must first upgrade the operating system version on those hosts before upgrading CloudStack itself. The first order of business will be to change the yum repository for each system with CloudStack packages. This means all management servers, and any hosts that have the KVM agent. (No changes should be necessary for hosts that are running VMware or Xen.) Start by opening /etc/yum.repos.d/cloudstack.repo on any systems that have CloudStack packages installed. [upgrade] name=rhel63 baseurl=url-of-your-rhel6.3-repo enabled=1 gpgcheck=0 [apache CloudStack] name= Apache CloudStack baseurl= http://cloudstack.apt-get.eu/rhel/4.0/ enabled=1 gpgcheck=0 If you are using the community provided package repository, change the baseurl to http:// cloudstack.apt-get.eu/rhel/4.2/ If you're using your own package repository, change this line to read as appropriate for your 4.2.0 repository. b. Now that you have the repository configured c. Upgrade the host operating system from RHEL 6.0 to 6.3: yum upgrade 6. Also, in all the sections 3.2 and 3.3 , add this step for agent upgrades After running this , Edit /etc/cloudstack/agent/agent.properties to change the resource parameter from com.cloud.agent.resource.computing.LibvirtComputingResource to com.cloud.hypervisor.kvm.resource.LibvirtComputingResource We need to run the following too, Upgrade all the existing bridge names to new bridge names by running this script: # cloudstack-agent-upgrade . Install a libvirt hook with the following commands: # mkdir /etc/libvirt/hooks # cp /usr/share/cloudstack-agent/lib/libvirtqemuhook /etc/libvirt/hooks/qemu # chmod +x /etc/libvirt/hooks/qemu . Restart libvirtd. # service libvirtd restart . Start the agent. # service cloudstack-agent start Note : This step will be added after step 13.d in section 3.2 and 21.e in section 3.3 7. We need to add a section for 4.0.x to 4.2 upgrades. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more
[jira] [Updated] (CLOUDSTACK-4245) Create Release Notes for ACS 4.2 Release
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-4245: - Attachment: Apache_CloudStack-4.2.0-Release_Notes-en-US.pdf Upgrade issues fixed Create Release Notes for ACS 4.2 Release Key: CLOUDSTACK-4245 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4245 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Fix For: 4.2.0 Attachments: Apache_CloudStack-4.2.0-Release_Notes-en-US.pdf, Apache_CloudStack-4.2.0-Release_Notes-en-US.pdf -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-4727) Update Upgrade Instructions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair reassigned CLOUDSTACK-4727: Assignee: Radhika Nair Update Upgrade Instructions --- Key: CLOUDSTACK-4727 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4727 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Priority: Blocker Fix For: 4.2.0 1. Before upgrading from any version to 4.2 we need to register the new 4.2 systemvm templates . This step is there in section 3.3 i.e for upgrade from 2.2.14 to 4.2, but it is missing in section 3.1 and 3.2 . 2. Section 3.1 Step 34 : it should be cloudstack-management and cloudstack-usage as the naming conventions have been changed from 4.1 onwards. Step 6 : The cloudstack 4.2 repo has not been published yet, currently at http://cloudstack.apt-get.eu/ the repo is available only for 4.0.x and 4.1.x What Indira pointed to, needs to be removed, step 6.g) and 6.h) and step 8 also need to be removed In step 6.f) It should be service cloudstack-agent stop Step 9.b) : It should be sudo yum upgrade cloudstack-client Step 9.c) : it should be sudo yum upgrade cloudstack-agent and the following line is not required [[ During the installation of cloudstack-agent, the RPM will copy your agent.properties,log4j-cloud.xml, and environment.properties from /etc/cloud/agent to /etc/cloudstack/agent ]] Step 9.d.ii) : it should be sudo yum upgrade cloudstack-usage 3. Section 3.2 Step 1.e) : The URL of the vmware systemvm template is wrong. It should be http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova . The OSType should be [[Debian GNU/Linux 7.0 (32-bit) (or the highestDebian release number available in the dropdown)]] Similarly, add templates for xenserver and kvm also. Step 7 : Delete this step, it's not needed. Step 16 : It should be cloudstack-sysvmadm 4. Section 3.3 Step 4.d) : For all the newly registered templates, make the OStype as [[Debian GNU/Linux 7.0 (32-bit) (or the highest Debian release number available in the dropdown)]] Step 13.c) : It should be /etc/cloudstack/management/components.xml Step 15.c) : It should be /etc/cloudstack/management/db.properties Step 20 : Remove this step, it's not needed Step 21.e) : It should be /etc/cloudstack/agent/agent.properties Step 23.a) : It should be cloudstack-sysvmadm 5. In addition to all this, If we are using KVM hosts as rhel6.0/6.1 then these extra steps need to be documented for each section, 3.2 and 3.3 (KVM on RHEL 6.0/6.1 only) If your existing CloudStack deployment includes one or more clusters of KVM hosts running RHEL 6.0 or RHEL 6.1, you must first upgrade the operating system version on those hosts before upgrading CloudStack itself. The first order of business will be to change the yum repository for each system with CloudStack packages. This means all management servers, and any hosts that have the KVM agent. (No changes should be necessary for hosts that are running VMware or Xen.) Start by opening /etc/yum.repos.d/cloudstack.repo on any systems that have CloudStack packages installed. [upgrade] name=rhel63 baseurl=url-of-your-rhel6.3-repo enabled=1 gpgcheck=0 [apache CloudStack] name= Apache CloudStack baseurl= http://cloudstack.apt-get.eu/rhel/4.0/ enabled=1 gpgcheck=0 If you are using the community provided package repository, change the baseurl to http:// cloudstack.apt-get.eu/rhel/4.2/ If you're using your own package repository, change this line to read as appropriate for your 4.2.0 repository. b. Now that you have the repository configured c. Upgrade the host operating system from RHEL 6.0 to 6.3: yum upgrade 6. Also, in all the sections 3.2 and 3.3 , add this step for agent upgrades After running this , Edit /etc/cloudstack/agent/agent.properties to change the resource parameter from com.cloud.agent.resource.computing.LibvirtComputingResource to com.cloud.hypervisor.kvm.resource.LibvirtComputingResource We need to run the following too, Upgrade all the existing bridge names to new bridge names by running this script: # cloudstack-agent-upgrade . Install a libvirt hook with the following commands: # mkdir /etc/libvirt/hooks # cp /usr/share/cloudstack-agent/lib/libvirtqemuhook /etc/libvirt/hooks/qemu # chmod +x /etc/libvirt/hooks/qemu . Restart libvirtd. # service libvirtd restart . Start the agent. # service
[jira] [Updated] (CLOUDSTACK-4245) Create Release Notes for ACS 4.2 Release
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-4245: - Status: Ready To Review (was: In Progress) Create Release Notes for ACS 4.2 Release Key: CLOUDSTACK-4245 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4245 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 Attachments: Apache_CloudStack-4.2.0-Release_Notes-en-US.pdf -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4727) Update Upgrade Instructions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-4727: - Status: Ready To Review (was: In Progress) Update Upgrade Instructions --- Key: CLOUDSTACK-4727 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4727 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Priority: Blocker Fix For: 4.2.0 1. Before upgrading from any version to 4.2 we need to register the new 4.2 systemvm templates . This step is there in section 3.3 i.e for upgrade from 2.2.14 to 4.2, but it is missing in section 3.1 and 3.2 . 2. Section 3.1 Step 34 : it should be cloudstack-management and cloudstack-usage as the naming conventions have been changed from 4.1 onwards. Step 6 : The cloudstack 4.2 repo has not been published yet, currently at http://cloudstack.apt-get.eu/ the repo is available only for 4.0.x and 4.1.x What Indira pointed to, needs to be removed, step 6.g) and 6.h) and step 8 also need to be removed In step 6.f) It should be service cloudstack-agent stop Step 9.b) : It should be sudo yum upgrade cloudstack-client Step 9.c) : it should be sudo yum upgrade cloudstack-agent and the following line is not required [[ During the installation of cloudstack-agent, the RPM will copy your agent.properties,log4j-cloud.xml, and environment.properties from /etc/cloud/agent to /etc/cloudstack/agent ]] Step 9.d.ii) : it should be sudo yum upgrade cloudstack-usage 3. Section 3.2 Step 1.e) : The URL of the vmware systemvm template is wrong. It should be http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova . The OSType should be [[Debian GNU/Linux 7.0 (32-bit) (or the highestDebian release number available in the dropdown)]] Similarly, add templates for xenserver and kvm also. Step 7 : Delete this step, it's not needed. Step 16 : It should be cloudstack-sysvmadm 4. Section 3.3 Step 4.d) : For all the newly registered templates, make the OStype as [[Debian GNU/Linux 7.0 (32-bit) (or the highest Debian release number available in the dropdown)]] Step 13.c) : It should be /etc/cloudstack/management/components.xml Step 15.c) : It should be /etc/cloudstack/management/db.properties Step 20 : Remove this step, it's not needed Step 21.e) : It should be /etc/cloudstack/agent/agent.properties Step 23.a) : It should be cloudstack-sysvmadm 5. In addition to all this, If we are using KVM hosts as rhel6.0/6.1 then these extra steps need to be documented for each section, 3.2 and 3.3 (KVM on RHEL 6.0/6.1 only) If your existing CloudStack deployment includes one or more clusters of KVM hosts running RHEL 6.0 or RHEL 6.1, you must first upgrade the operating system version on those hosts before upgrading CloudStack itself. The first order of business will be to change the yum repository for each system with CloudStack packages. This means all management servers, and any hosts that have the KVM agent. (No changes should be necessary for hosts that are running VMware or Xen.) Start by opening /etc/yum.repos.d/cloudstack.repo on any systems that have CloudStack packages installed. [upgrade] name=rhel63 baseurl=url-of-your-rhel6.3-repo enabled=1 gpgcheck=0 [apache CloudStack] name= Apache CloudStack baseurl= http://cloudstack.apt-get.eu/rhel/4.0/ enabled=1 gpgcheck=0 If you are using the community provided package repository, change the baseurl to http:// cloudstack.apt-get.eu/rhel/4.2/ If you're using your own package repository, change this line to read as appropriate for your 4.2.0 repository. b. Now that you have the repository configured c. Upgrade the host operating system from RHEL 6.0 to 6.3: yum upgrade 6. Also, in all the sections 3.2 and 3.3 , add this step for agent upgrades After running this , Edit /etc/cloudstack/agent/agent.properties to change the resource parameter from com.cloud.agent.resource.computing.LibvirtComputingResource to com.cloud.hypervisor.kvm.resource.LibvirtComputingResource We need to run the following too, Upgrade all the existing bridge names to new bridge names by running this script: # cloudstack-agent-upgrade . Install a libvirt hook with the following commands: # mkdir /etc/libvirt/hooks # cp /usr/share/cloudstack-agent/lib/libvirtqemuhook /etc/libvirt/hooks/qemu # chmod +x /etc/libvirt/hooks/qemu . Restart libvirtd. # service libvirtd restart . Start the
[jira] [Updated] (CLOUDSTACK-4245) Create Release Notes for ACS 4.2 Release
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-4245: - Attachment: (was: Apache_CloudStack-4.2.0-Release_Notes-en-US.pdf) Create Release Notes for ACS 4.2 Release Key: CLOUDSTACK-4245 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4245 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Fix For: 4.2.0 Attachments: Apache_CloudStack-4.2.0-Release_Notes-en-US.pdf -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4653) Update What's New Section
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-4653: - Status: Ready To Review (was: In Progress) Update What's New Section - Key: CLOUDSTACK-4653 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4653 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-4245) Create Release Notes for ACS 4.2 Release
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair reassigned CLOUDSTACK-4245: Assignee: Radhika Nair Create Release Notes for ACS 4.2 Release Key: CLOUDSTACK-4245 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4245 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 Attachments: Apache_CloudStack-4.2.0-Release_Notes-en-US.pdf -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4245) Create Release Notes for ACS 4.2 Release
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-4245: - Attachment: Apache_CloudStack-4.2.0-Release_Notes-en-US.pdf Create Release Notes for ACS 4.2 Release Key: CLOUDSTACK-4245 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4245 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Fix For: 4.2.0 Attachments: Apache_CloudStack-4.2.0-Release_Notes-en-US.pdf -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
