[jira] [Commented] (CLOUDSTACK-5003) [DOC] Documentation tasks for 4.2.1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815729#comment-13815729 ] Jessica Tomechak commented on CLOUDSTACK-5003: -- For the 64-bit template feature: This looks like it belongs in the section "Working with System Virtual Machines" in the Admin Guide. Add a new sub-section called "Changing the Default System VM Template" or "Upgrading to 64-Bit System VM Template" or something similar. Also, the whole existing section ought to be double-checked for side effects. For example, there is a bulleted list "The System VM has the following characteristics: ... 32-bit" which obviously would need to be updated, if 64-bit template versions are now available. It's possible that this 32-bitness is mentioned elsewhere in docs, too. > [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 >Assignee: Radhika Nair >Priority: Blocker > > 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] [Updated] (CLOUDSTACK-4602) [DOC] CLONE - Update the supported ec2 version from 2010-11-15 to a more recent EC2 API version i.e. 2012-08-15.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-4602: - Assignee: (was: Jessica Tomechak) > [DOC] CLONE - Update the supported ec2 version from 2010-11-15 to a more > recent EC2 API version i.e. 2012-08-15. > > > Key: CLOUDSTACK-4602 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4602 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: AWSAPI >Affects Versions: 4.2.0 >Reporter: Likitha Shetty > Labels: documentation > Fix For: 4.2.1 > > > As described the functional spec - > https://cwiki.apache.org/confluence/display/CLOUDSTACK/EC2++-+Functional+Spec+for+Query+API+support, > the AWS EC2 version supported by CS AWSAPI needs to be updated to more > recent version. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-818) Document Dedicate Pod, Cluster or Host to a domain
[ https://issues.apache.org/jira/browse/CLOUDSTACK-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-818: Assignee: (was: Jessica Tomechak) > Document Dedicate Pod, Cluster or Host to a domain > -- > > Key: CLOUDSTACK-818 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-818 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair > Fix For: 4.2.1 > > > Dedicate Pod, Cluster or Host to a domain- Documentation -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-233) Copy edit messages.properties
[ https://issues.apache.org/jira/browse/CLOUDSTACK-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-233: Assignee: (was: Jessica Tomechak) > Copy edit messages.properties > - > > Key: CLOUDSTACK-233 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-233 > Project: CloudStack > Issue Type: Task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: pre-4.0.0 >Reporter: Jessica Tomechak >Priority: Minor > Fix For: 4.1.0 > > > Ensure messages are understandable and use correct English. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-411) Add another step during kvm agent installation on Ubuntu machine
[ https://issues.apache.org/jira/browse/CLOUDSTACK-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-411: Assignee: (was: Jessica Tomechak) > Add another step during kvm agent installation on Ubuntu machine > > > Key: CLOUDSTACK-411 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-411 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: edison su > Fix For: 4.0.1 > > > Ref: https://issues.apache.org/jira/browse/CLOUDSTACK-410. For 4.0 release, > we can document it in the installation guide for kvm agent installation on > ubuntu machine, with the following command: > uncomment out "# vnc_listen = "0.0.0.0"" in /etc/libvirt/qemu.conf -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-900) Document enable storage xenmotion support in XenServer 6.1 feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-900: Assignee: (was: Jessica Tomechak) > Document enable storage xenmotion support in XenServer 6.1 feature > -- > > Key: CLOUDSTACK-900 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-900 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-959) Missing sub-sections in document section System Service Offerings
[ https://issues.apache.org/jira/browse/CLOUDSTACK-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-959: Assignee: (was: Jessica Tomechak) > Missing sub-sections in document section System Service Offerings > - > > Key: CLOUDSTACK-959 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-959 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.0.0 >Reporter: Jessica Tomechak >Priority: Minor > Fix For: 4.1.0 > > > It appears that when the section "System Service Offerings" was added to the > Admin Guide, its sub-heading "Creating a New System Service Offering" was > omitted. The file is in the doc directory, but it was never included in the > main file system-service-offerings.xml. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-861) [DOC] Document Cisco UCS baremetal support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-861: Assignee: (was: Jessica Tomechak) > [DOC] Document Cisco UCS baremetal support > -- > > Key: CLOUDSTACK-861 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-861 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: David Nalley > Fix For: 4.2.1 > > > Document the UCS baremetal functionality -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-1478) [DOC] Document baremetal kickstart
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-1478: - Assignee: (was: Jessica Tomechak) > [DOC] Document baremetal kickstart > -- > > Key: CLOUDSTACK-1478 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1478 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Jessica Tomechak >Priority: Minor > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-17) Merge final documentation into 4.0 branch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-17: --- Assignee: (was: Jessica Tomechak) > Merge final documentation into 4.0 branch > - > > Key: CLOUDSTACK-17 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-17 > Project: CloudStack > Issue Type: Task > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: pre-4.0.0, 4.0.0 >Reporter: Ewan Mellor >Priority: Critical > Fix For: 4.0.0 > > > Merge the latest documentation into the 4.0 branch before we make the final > RC, so that we have a frozen, up-to-date copy in the release branch. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-816) Document health monitoring for load balanced instances
[ https://issues.apache.org/jira/browse/CLOUDSTACK-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-816: Assignee: (was: Jessica Tomechak) > Document health monitoring for load balanced instances > -- > > Key: CLOUDSTACK-816 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-816 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair > Fix For: 4.2.0 > > > Document health monitoring for load balanced instances -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-865) Document API Refactoring
[ https://issues.apache.org/jira/browse/CLOUDSTACK-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-865: Assignee: (was: Jessica Tomechak) > Document API Refactoring > - > > Key: CLOUDSTACK-865 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-865 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair > Fix For: 4.1.0 > > > Document API Refactoring -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-805) Document Isolation based on Security Groups in Advanced Zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-805: Assignee: (was: Jessica Tomechak) > Document Isolation based on Security Groups in Advanced Zone > > > Key: CLOUDSTACK-805 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-805 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair > Fix For: 4.2.0 > > > Documentation on Isolation based on Security Groups in Advanced Zone -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-1932) AutoScale UI documentation doesn't mention the option appears only for NetScaler
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-1932: - Assignee: (was: Jessica Tomechak) > AutoScale UI documentation doesn't mention the option appears only for > NetScaler > > > Key: CLOUDSTACK-1932 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1932 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.1.0, 4.2.0 >Reporter: Jessica Tomechak >Priority: Minor > Fix For: 4.2.1 > > > This affects add-load-balancer-rule.xml and autoscale.xml. > In add-load-balancer-rule.xml, in the step "Fill in the following:", the > bullet item AutoScale should note that this option appears only when > NetScaler is selected as a service provider for the network where you are > defining the LB rule. > And in autoscale.xml, there should be a note right at the top like > "(NetScaler only)" or "(Supported only in networks where the Citrix NetScaler > is used.)" -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-830) Document Reset SSH key feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-830: Assignee: (was: Jessica Tomechak) > Document Reset SSH key feature > -- > > Key: CLOUDSTACK-830 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-830 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers > Fix For: 4.1.0 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-774) Supporting kickstart in CloudStack baremetal
[ https://issues.apache.org/jira/browse/CLOUDSTACK-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-774: Assignee: (was: Jessica Tomechak) > Supporting kickstart in CloudStack baremetal > > > Key: CLOUDSTACK-774 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-774 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Baremetal >Affects Versions: 4.1.0 >Reporter: frank zhang > Fix For: 4.2.0 > > Attachments: CLOUDSTACK-774-baremetal-support.patch, > CLOUDSTACK-774-baremetal-support.patch.md5sum, > CLOUDSTACK-774-baremetal-support.patch.sig > > > Supporting kickstart install for RedHat like Linux in CloudStack Baremetal > provisioning > Release Planning: > Dev List Discussion: http://markmail.org/message/m6tg5nzfgqiwhzre > Functional Spec: https://cwiki.apache.org/CLOUDSTACK/baremetal-kickstart.html > Feature Branch: master > progress: 90% -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-866) Document Limit API Queries
[ https://issues.apache.org/jira/browse/CLOUDSTACK-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-866: Assignee: (was: Jessica Tomechak) > Document Limit API Queries > -- > > Key: CLOUDSTACK-866 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-866 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Reporter: Radhika Nair > Fix For: 4.1.0 > > > Document Limit API Queries -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-405) management server startup missing from install documents
[ https://issues.apache.org/jira/browse/CLOUDSTACK-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-405: Assignee: (was: Jessica Tomechak) > management server startup missing from install documents > > > Key: CLOUDSTACK-405 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-405 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Noa Resare > Fix For: pre-4.0.0 > > > For the simplest possible test case (that I can come up with) the > Installation Guide instructions fail, with status 404 when attempting to > connect to http://MANAGEMENT_SERVER:8080/client > Expected outcome: > The cloudstack web UI in the web browser when accessing > http://MANAGEMENT_SERVER:8080/client > Actual outcome: > The default tomcat 404 page > Steps to reproduce: > - I created a fully updated vmware vm running a 64 bit Ubuntu 12.04.1 > - installed mysql-server, with root password abc123 > - ran mysql_secure_installation, default options > - pulled the latest built ubuntu packages from jenkins: > http://jenkins.cloudstack.org/job/build-4.0-ubuntu1204/535/artifact/CloudStack-oss-4.0.0-535.tar.bz2 > - ran the install script installing the management server (which translates > install 'apt-get install cloud-client') > - ran "cloud-setup-databases cloud:foobar --deploy-as=root:abc123" with the > output "CloudStack has successfully initialized database" > - attempted to connect with my web browser at > http://MANAGEMENT_SERVER:8080/client > Additional notes: > Looking at the output from the installer, it seems the tomcat6 starts on > install, listening on port 8080. If I run > "/etc/init.d/tomcat6 stop" followed by "/etc/init.d/cloud-management start" I > get a cloudstack login prompt at http://MANAGEMENT_SERVER:8080/client/ -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-2018) [DOC] How system.vm passwords can be randomized
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-2018: - Assignee: (was: Jessica Tomechak) > [DOC] How system.vm passwords can be randomized > --- > > Key: CLOUDSTACK-2018 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2018 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.0.0, 4.1.0, 4.2.0 >Reporter: Prasanna Santhanam > > The systemVM password is defaulted and it is possible to change it to a > random password. The process for doing this is through a global setting. > However this doesn't seem to be documented at the moment. > Relevant ML discussion: > http://markmail.org/thread/xdizpx3jumbykcr6#query:+page:1+mid:xdizpx3jumbykcr6+state:results -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4670) [Baremetal] Cloudplatform BareMetal installation guide for CP 4.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-4670: - Assignee: (was: Jessica Tomechak) > [Baremetal] Cloudplatform BareMetal installation guide for CP 4.2 > - > > Key: CLOUDSTACK-4670 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4670 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: angeline shen >Priority: Minor > Fix For: 4.2.1 > > > Jessica: > Cloudplatform BareMetal installation guide for CP 4.2: > Section titled 'Create a Bare Metal Template ' (page 19 - 20 ) should > be moved to after > Section titled 'Add the PXE Server and DHCP Server to Your Deployment' -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-773) Document Object Store-Integration with CS as secondary Storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-773: Assignee: (was: Jessica Tomechak) > Document Object Store-Integration with CS as secondary Storage > -- > > Key: CLOUDSTACK-773 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-773 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair > Fix For: 4.2.1 > > > Document Object Store-Integration with CS as secondary Storage -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-867) Document Scaling up CPU and RAM for running VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-867: Assignee: (was: Jessica Tomechak) > Document Scaling up CPU and RAM for running VMs > > > Key: CLOUDSTACK-867 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-867 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair > Fix For: 4.2.0 > > Attachments: Dynamically_Scalable.jpg, Global_Settings.jpg, > zone_Settings .jpg > > > Document Scaling up CPU and RAM for running VMs -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4229) AWS Style healthcheck creation are not supported on NS 9.3 in Cloudstack 4.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-4229: - Assignee: (was: Jessica Tomechak) > AWS Style healthcheck creation are not supported on NS 9.3 in Cloudstack 4.2 > > > Key: CLOUDSTACK-4229 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4229 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Rajesh Battala > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-745) Reset a VM on reboot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-745: Assignee: (was: Jessica Tomechak) > Reset a VM on reboot > > > Key: CLOUDSTACK-745 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-745 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Harikrishna Patnala > Fix For: 4.2.0 > > > To have a method to reset the vm on its reboot. > So on reboot, the vm's disk is discarded and creates a new root disk using > the template. > The use cases for this are > -> Secure environments that need a fresh start on every boot > -> Desktops that should not retain state -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-833) [DOC] Document increase in VMware 5.1 max cluster size
[ https://issues.apache.org/jira/browse/CLOUDSTACK-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-833: Assignee: (was: Jessica Tomechak) > [DOC] Document increase in VMware 5.1 max cluster size > -- > > Key: CLOUDSTACK-833 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-833 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: David Nalley > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-925) Document XenServer updates notifications
[ https://issues.apache.org/jira/browse/CLOUDSTACK-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-925: Assignee: (was: Jessica Tomechak) > Document XenServer updates notifications > > > Key: CLOUDSTACK-925 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-925 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair > Fix For: 4.1.0 > > > Document XenServer updates notifications -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4550) [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have migration work
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-4550: - Assignee: (was: Jessica Tomechak) > [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have > migration work > -- > > Key: CLOUDSTACK-4550 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4550 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc, KVM, Upgrade >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Priority: Critical > > See CLOUDSTACK-4405 for the original bug. This is the doc to be prepared as > part of upgrade in release notes once the fix for the bug is verified to work > After network bridges being renamed from cloudVirBrVLAN to brem1-VLAN to > support the same VLAN on multiple physical networks the migration of VMs from > hosts prior the upgrade to the ones added after the upgrade will fail. > In order to fix this rename the bridges is required to allow migration to > work. > This can be done by running the cloudstack-agent-upgrade script. The original > bug is still undergoing testing, but these are the initial instructions -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-840) [DOC] Document CLOUDSTACK-670 regarding configuration option for linked clones or lack thereof
[ https://issues.apache.org/jira/browse/CLOUDSTACK-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-840: Assignee: (was: Jessica Tomechak) > [DOC] Document CLOUDSTACK-670 regarding configuration option for linked > clones or lack thereof > -- > > Key: CLOUDSTACK-840 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-840 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: David Nalley > Fix For: 4.2.1 > > > Add documentation for the configuration option about use (or not) of linked > clones. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4568) Need to add this to the release note of 4.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-4568: - Assignee: (was: Jessica Tomechak) > Need to add this to the release note of 4.2 > --- > > Key: CLOUDSTACK-4568 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4568 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Bharat Kumar > Labels: releasenotes > Fix For: 4.2.1 > > > After upgrade to 4.2 the mem.overporvisioning.factor and > cpu.overporvisioning.factor will be set to one that is the default value and > are at cluster level now. > In case if some one prior to the 4.2 was usign mem.overporvisioning.factor > and cpu.overporvisioning.factor after the upgrade these will be reset to one > and can be changed by editing the cluster settings. > All the clusters created after the upgrade will get created with the values > overcomit values specified at the global config by default. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-923) Documentation for Add synchronization for createSnapshot command per host basis
[ https://issues.apache.org/jira/browse/CLOUDSTACK-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-923: Assignee: (was: Jessica Tomechak) > Documentation for Add synchronization for createSnapshot command per host > basis > --- > > Key: CLOUDSTACK-923 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-923 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair > Fix For: 4.1.0 > > > Documentation for Add synchronization for createSnapshot command per host > basis -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-8) Update API Reference man pages for v4.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-8: -- Assignee: (was: Jessica Tomechak) > Update API Reference man pages for v4.0 > --- > > Key: CLOUDSTACK-8 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8 > Project: CloudStack > Issue Type: Task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.0.0 >Reporter: Jessica Tomechak > Fix For: pre-4.0.0 > > > 3.x API Reference needs update for v4.0. Need to run doc gen script and post > the new HTML files. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-406) Amazon Web Service Interface Compatibility Section - Reference to port 8080 needs to be changed to port 7080 in cloudstack-aws-api-register command and when setting E
[ https://issues.apache.org/jira/browse/CLOUDSTACK-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-406: Assignee: (was: Jessica Tomechak) > Amazon Web Service Interface Compatibility Section - Reference to port 8080 > needs to be changed to port 7080 in cloudstack-aws-api-register command and > when setting EC2_URL. > - > > Key: CLOUDSTACK-406 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-406 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: pre-4.0.0 > Environment: Install guide - > http://jenkins.cloudstack.org/view/master/job/build-docs-install-master/lastSuccessfulBuild/artifact/Apache_CloudStack-4.0.0-incubating-Installation_Guide-en-US.pdf >Reporter: Sangeetha Hariharan > Fix For: 4.0.0 > > > Amazon Web Service Interface Compatibility Section - Reference to port 8080 > needs to be changed to port 7080 in cloudstack-aws-api-register command and > when setting EC2_URL. > In 10.4.1. AWS API User Registration section: > $ cloudstack-aws-api-register --apikey=User’s CloudStack API key > --secretkey=User’s > CloudStack Secret key --cert=/path/to/cert.pem > --url=http://CloudStack.server:8080/ > awsapi > --url param should be http://CloudStack.server:7080/awsapi , instead of port > 8080. > 10.4.2. AWS API Command-Line Tools Setup > export EC2_URL=http://CloudStack.server:8080/awsapi > This varibale needs to point to "http://CloudStack.server:7080/awsapi"; -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-134) Document procedure to install vhd-util
[ https://issues.apache.org/jira/browse/CLOUDSTACK-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-134: Assignee: (was: Jessica Tomechak) > Document procedure to install vhd-util > -- > > Key: CLOUDSTACK-134 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-134 > Project: CloudStack > Issue Type: Task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: pre-4.0.0 >Reporter: edison su >Priority: Blocker > Fix For: 4.0.0 > > > Due to license issue reported in CLOUDSTACK-30, vhd-util is removed from > source code and packages. Need to document the procedure to download and > install vhd-util during the mgt server installation. > The current url is http://download.cloud.com.s3.amazonaws.com/tools/vhd-util > If mgt server is rhel/centos, need to download from this url, then copy > vhd-util into /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/ > If mgt server is ubuntu, then put vhd-util into > /usr/lib/cloud/common/scripts/vm/hypervisor/xenserver/vhd-util > (Chandan adds:) > We should also document the requirement of setting the following permissions > to the downloaded vhd-util tool: > Chmod 755 vhd-util -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4300) [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-4300: - Assignee: (was: Jessica Tomechak) > [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade > > > Key: CLOUDSTACK-4300 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4300 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc, KVM, SystemVM, Upgrade >Affects Versions: 4.2.0 > Environment: Host : KVM [CentOS 6.1] > MS : CentOS 6.1 > upgrade from 2.2.14 to 4.2 >Reporter: Abhinav Roy >Priority: Blocker > Fix For: 4.2.1 > > Attachments: CS-4300.zip, re_CS-4300.zip > > > Steps : > > 1. Deploy a CS 2.2.14 advanced zone setup with KVM host. > 2. do some operations like create vm, snapshots, templates, domain, accounts > etc > 3. upgrade to 4.2 > Expected behaviour : > === > Upgrade should go fine and new system vms should come up > Observed behaviour : > == > Upgrade went fine but system vms don't come up, they stay in the starting > state. > Attaching management server logs, catalina logs, agent logs and DB dumps -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-738) Ability to manage Basic and Advanced Zone using a single instance of CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-738: Assignee: (was: Jessica Tomechak) > Ability to manage Basic and Advanced Zone using a single instance of > CloudStack > --- > > Key: CLOUDSTACK-738 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-738 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Manan Shah > Fix For: Future > > > Currently, CloudStack supports Basic Zones as well as Advanced Zones but the > UI supports management of only Basic Zones or Advanced Zones. > This enhancement is to track allowing management of Basic and Advanced Zones > using a single instance of CloudStack. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-1285) UI -Tooltip - Lengthy and inconsistent description among toolips
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-1285: - Assignee: (was: Jessica Tomechak) > UI -Tooltip - Lengthy and inconsistent description among toolips > > > Key: CLOUDSTACK-1285 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1285 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0, 4.2.0 > Environment: RHEL 6.3 Build#15 >Reporter: Parth Jagirdar >Priority: Minor > Attachments: 3.jpg, 4.jpg > > > "A unique name for the template. This will be visible to users, so choose > something descriptive" ; I think 94 Characters are too much for a ToolTip > representing name. (Screen 4) > And is also inconsistent with other tooltips for names which are more concise > and simple such as "A name for the Zone". (Refer to Screen 4 and compare it > to Screen 3) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-1441) Document ApiDiscoverService
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-1441: - Assignee: (was: Jessica Tomechak) > Document ApiDiscoverService > --- > > Key: CLOUDSTACK-1441 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1441 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Jessica Tomechak >Priority: Minor > Labels: api > Fix For: 4.1.1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-1152) Missing tag in host-add.xml
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-1152: - Assignee: (was: Jessica Tomechak) > Missing tag in host-add.xml > --- > > Key: CLOUDSTACK-1152 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1152 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Logan McNaughton >Priority: Minor > Fix For: 4.1.0 > > > docs/en-US/host-add.xml is missing a closing , it is present in master > and prevents docs from building -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-3635) [DOC][Dynamic Scaling][VMware] Guest OS support information
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-3635: - Assignee: (was: Jessica Tomechak) > [DOC][Dynamic Scaling][VMware] Guest OS support information > --- > > Key: CLOUDSTACK-3635 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3635 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Sateesh Chodapuneedi > Labels: adminguide, installguide, release > Fix For: 4.2.1 > > > Dynamic scaling of VM consists of scaling CPU & MEMORY of running VM. > The ability to hotadd cpu or memory depends on Guest operating system version > (like CentOS 5.3) and bits of the OS (like 64 bit). > CloudStack does query Guest OS information available in ESXi information > using vSphere API. But this information is not granular to the level of exact > version of guest operating system and bitness (32 or 64). Hence it is > recommended that user verify if the VM is installed with guest operating > system which supports cpu or memory hotadd features from following link. > http://www.vmware.com/resources/compatibility/search.php?deviceCategory=software&testConfig=16&productid=17364 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-1286) UI - Tooltip - Missing Tooltips for some key features
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-1286: - Assignee: (was: Jessica Tomechak) > UI - Tooltip - Missing Tooltips for some key features > - > > Key: CLOUDSTACK-1286 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1286 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0 > Environment: RHEL 6.3 Build #15 >Reporter: Parth Jagirdar > > A few drop down menus(Select’s) have tooltips and almost no checkbox has any. > (Again this was brief sanity test). > I think ToolTips for "Public" and "Featured" on template registration wizard > would be worth reading for a new user. > Marking this Major as if Tooltips are at all required then these features are > the few places they should go in first. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4729) Document workaround for IPMI protocal type for specific hardware on baremetal
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Tomechak updated CLOUDSTACK-4729:
-
Assignee: (was: Jessica Tomechak)
> Document workaround for IPMI protocal type for specific hardware on baremetal
> -
>
> Key: CLOUDSTACK-4729
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4729
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc
>Affects Versions: 4.2.1
>Reporter: frank zhang
> Fix For: 4.2.1
>
>
> We should mention to users that Baremetal uses ipmitool to control lifecycle
> of baremetal host. ipmitool default uses interface 'lan' to issue ipmi
> commands. Depending on your motherboard, the interface may need to be
> 'lanplus', in this case, user has to modify script
> /usr/lib64/cloud/agent/scripts/util/ipmi.py
> replace all lines calling ipmi tool for example:
> o = ipmitool("-H", hostname, "-U", usrname, "-P", password, "chassis",
> "power", "status")
> to
> o = ipmitool("-H", hostname, ,"-I", "lanplus", "-U", usrname, "-P", password,
> "chassis", "power", "status")
> this issue will be addressed in next release.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4734) Creating snapshot from ROOT volume fails with error message - "Failed to create snapshot due to an internal error creating snapshot for volume 14”
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777223#comment-13777223
]
Jessica Tomechak commented on CLOUDSTACK-4734:
--
Adding Doc component, as it would be useful to mention this as a known issue in
the release notes, and give Sangeetha's workaround from the comment above.
> Creating snapshot from ROOT volume fails with error message - "Failed to
> create snapshot due to an internal error creating snapshot for volume 14”
> --
>
> Key: CLOUDSTACK-4734
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4734
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc, Management Server
>Affects Versions: 4.2.1
> Environment: Build from 4.2-forward
>Reporter: Sangeetha Hariharan
> Fix For: 4.2.1
>
> Attachments: temp.rar
>
>
> Set up:
> 3.0.7 Advanced Zone setup with 2 Zones having Vmware EXSI 5.0 clusters on
> Vcenter 5.0 .
> Upgraded to 4.2.0.
> Tried to take snapshot for ROOT volume of 2 existing Vms from 2 different
> zones.
> Snapshots got created successfully.
> After few hours , when I tried to create snapshot from ROOT volume for a VM,
> I was not able to create snapshots from ROOT volume.
> I get the following error – “Error Code: 530 Error text: Failed to create
> snapshot due to an internal error creating snapshot for volume
> 14”
>
> Following is the error message seen on management server logs:
>
> 2013-09-21 06:56:13,573 DEBUG [agent.transport.Request]
> (Job-Executor-36:job-88 = [ c7cbee54-930d-4020-ae02-4710806
> bdc00 ]) Seq 9-1758069619: Sending { Cmd , MgmtId: 161197867246747, via: 9,
> Ver: v1, Flags: 100111, [{"org.apache.
> cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"path":"9e8a
> 10cf-7cbc-4bef-a57b-563edb6b62ed","volume":{"uuid":"05a6bdfd-e6a5-4ae5-9dab-d06ee40776e9","volumeType":"ROOT","data
> Store":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"61e1621f-a1a8-336d-b18d-050586f19b09","id":2
> 00,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/sangeetha/campofinalga/primary","por
> t":2049}},"name":"ROOT-14","size":2147483648,"path":"ROOT-14-14","volumeId":14,"vmName":"i-3-14-VM","accountId":3,"
> format":"OVA","id":14,"hypervisorType":"VMware"},"dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO"
> :{"uuid":"61e1621f-a1a8-336d-b18d-050586f19b09","id":200,"poolType":"NetworkFilesystem","host":"10.223.110.232","pa
> th":"/export/home/sangeetha/campofinalga/primary","port":2049}},"vmName":"i-3-14-VM","name":"sangee-tier1-4_ROOT-14
> _20130921135613","hypervisorType":"VMware","id":5}},"destTO":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{
> "path":"snapshots/3/14","volume":{"uuid":"05a6bdfd-e6a5-4ae5-9dab-d06ee40776e9","volumeType":"ROOT","dataStore":{"o
> rg.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"61e1621f-a1a8-336d-b18d-050586f19b09","id":200,"poolTy
> pe":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/sangeetha/campofinalga/primary","port":2049}},
> "name":"ROOT-14","size":2147483648,"path":"ROOT-14-14","volumeId":14,"vmName":"i-3-14-VM","accountId":3,"format":"O
> VA","id":14,"hypervisorType":"VMware"},"dataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.223.110.232/ex
> port/home/sangeetha/campofinalga/secondary","_role":"Image"}},"vmName":"i-3-14-VM","name":"sangee-tier1-4_ROOT-14_2
> 0130921135613","hypervisorType":"VMware","id":5}},"executeInSequence":true,"wait":21600}}]
> }
>
> 2013-09-21 06:56:18,263 DEBUG [agent.transport.Request]
> (AgentManager-Handler-14:null) Seq 9-1758069619: Processing
> : { Ans: , MgmtId: 161197867246747, via: 9, Ver: v1, Flags: 110,
> [{"org.apache.cloudstack.storage.command.CopyCmdA
> nswer":{"result":false,"details":"backup snapshot exception: Exception:
> javax.xml.ws.soap.SOAPFaultException\nMessa
> ge: \nRequired property obj is missing from data object of type
> ObjectSpec\n\nwhile parsing serialized DataObject o
> f type vmodl.query.PropertyCollector.ObjectSpec\nat line 1, column
> 305\n\nwhile parsing property \"objectSet\" of s
> tatic type ArrayOfObjectSpec\n\nwhile parsing serialized DataObject of type
> vmodl.query.PropertyCollector.FilterSpe
> c\nat line 1, column 205\n\nwhile parsing call information for method
> RetrieveProperties\nat line 1, column 110\n\n
> while parsing SOAP body\nat line 1, column 102\n\nwhile parsing SOAP
> envelope\nat line 1, column 38\n\nwhile parsin
> g HTTP request for method retrieveContents\non object of type
> vm
[jira] [Updated] (CLOUDSTACK-4734) Creating snapshot from ROOT volume fails with error message - "Failed to create snapshot due to an internal error creating snapshot for volume 14”
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Tomechak updated CLOUDSTACK-4734:
-
Component/s: Doc
> Creating snapshot from ROOT volume fails with error message - "Failed to
> create snapshot due to an internal error creating snapshot for volume 14”
> --
>
> Key: CLOUDSTACK-4734
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4734
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc, Management Server
>Affects Versions: 4.2.1
> Environment: Build from 4.2-forward
>Reporter: Sangeetha Hariharan
> Fix For: 4.2.1
>
> Attachments: temp.rar
>
>
> Set up:
> 3.0.7 Advanced Zone setup with 2 Zones having Vmware EXSI 5.0 clusters on
> Vcenter 5.0 .
> Upgraded to 4.2.0.
> Tried to take snapshot for ROOT volume of 2 existing Vms from 2 different
> zones.
> Snapshots got created successfully.
> After few hours , when I tried to create snapshot from ROOT volume for a VM,
> I was not able to create snapshots from ROOT volume.
> I get the following error – “Error Code: 530 Error text: Failed to create
> snapshot due to an internal error creating snapshot for volume
> 14”
>
> Following is the error message seen on management server logs:
>
> 2013-09-21 06:56:13,573 DEBUG [agent.transport.Request]
> (Job-Executor-36:job-88 = [ c7cbee54-930d-4020-ae02-4710806
> bdc00 ]) Seq 9-1758069619: Sending { Cmd , MgmtId: 161197867246747, via: 9,
> Ver: v1, Flags: 100111, [{"org.apache.
> cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"path":"9e8a
> 10cf-7cbc-4bef-a57b-563edb6b62ed","volume":{"uuid":"05a6bdfd-e6a5-4ae5-9dab-d06ee40776e9","volumeType":"ROOT","data
> Store":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"61e1621f-a1a8-336d-b18d-050586f19b09","id":2
> 00,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/sangeetha/campofinalga/primary","por
> t":2049}},"name":"ROOT-14","size":2147483648,"path":"ROOT-14-14","volumeId":14,"vmName":"i-3-14-VM","accountId":3,"
> format":"OVA","id":14,"hypervisorType":"VMware"},"dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO"
> :{"uuid":"61e1621f-a1a8-336d-b18d-050586f19b09","id":200,"poolType":"NetworkFilesystem","host":"10.223.110.232","pa
> th":"/export/home/sangeetha/campofinalga/primary","port":2049}},"vmName":"i-3-14-VM","name":"sangee-tier1-4_ROOT-14
> _20130921135613","hypervisorType":"VMware","id":5}},"destTO":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{
> "path":"snapshots/3/14","volume":{"uuid":"05a6bdfd-e6a5-4ae5-9dab-d06ee40776e9","volumeType":"ROOT","dataStore":{"o
> rg.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"61e1621f-a1a8-336d-b18d-050586f19b09","id":200,"poolTy
> pe":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/sangeetha/campofinalga/primary","port":2049}},
> "name":"ROOT-14","size":2147483648,"path":"ROOT-14-14","volumeId":14,"vmName":"i-3-14-VM","accountId":3,"format":"O
> VA","id":14,"hypervisorType":"VMware"},"dataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.223.110.232/ex
> port/home/sangeetha/campofinalga/secondary","_role":"Image"}},"vmName":"i-3-14-VM","name":"sangee-tier1-4_ROOT-14_2
> 0130921135613","hypervisorType":"VMware","id":5}},"executeInSequence":true,"wait":21600}}]
> }
>
> 2013-09-21 06:56:18,263 DEBUG [agent.transport.Request]
> (AgentManager-Handler-14:null) Seq 9-1758069619: Processing
> : { Ans: , MgmtId: 161197867246747, via: 9, Ver: v1, Flags: 110,
> [{"org.apache.cloudstack.storage.command.CopyCmdA
> nswer":{"result":false,"details":"backup snapshot exception: Exception:
> javax.xml.ws.soap.SOAPFaultException\nMessa
> ge: \nRequired property obj is missing from data object of type
> ObjectSpec\n\nwhile parsing serialized DataObject o
> f type vmodl.query.PropertyCollector.ObjectSpec\nat line 1, column
> 305\n\nwhile parsing property \"objectSet\" of s
> tatic type ArrayOfObjectSpec\n\nwhile parsing serialized DataObject of type
> vmodl.query.PropertyCollector.FilterSpe
> c\nat line 1, column 205\n\nwhile parsing call information for method
> RetrieveProperties\nat line 1, column 110\n\n
> while parsing SOAP body\nat line 1, column 102\n\nwhile parsing SOAP
> envelope\nat line 1, column 38\n\nwhile parsin
> g HTTP request for method retrieveContents\non object of type
> vmodl.query.PropertyCollector\nat line 1, column 0\n"
> ,"wait":0}}] }
>
> 2013-09-21 06:56:18,264 DEBUG [agent.transport.Request]
> (Job-Executor-36:job-88 = [ c7cbee54-930d-4020-ae02-4710806
> bdc00 ])
[jira] [Commented] (CLOUDSTACK-4729) Document workaround for IPMI protocal type for specific hardware on baremetal
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775698#comment-13775698
]
Jessica Tomechak commented on CLOUDSTACK-4729:
--
At what point in time would they need to modify the script? During
installation? If so, after what existing install step would you insert this
step? Or could this just be added as the final step in bare metal installation?
> Document workaround for IPMI protocal type for specific hardware on baremetal
> -
>
> Key: CLOUDSTACK-4729
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4729
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc
>Affects Versions: 4.2.1
>Reporter: frank zhang
>Assignee: Jessica Tomechak
> Fix For: 4.2.1
>
>
> We should mention to users that Baremetal uses ipmitool to control lifecycle
> of baremetal host. ipmitool default uses interface 'lan' to issue ipmi
> commands. Depending on your motherboard, the interface may need to be
> 'lanplus', in this case, user has to modify script
> /usr/lib64/cloud/agent/scripts/util/ipmi.py
> replace all lines calling ipmi tool for example:
> o = ipmitool("-H", hostname, "-U", usrname, "-P", password, "chassis",
> "power", "status")
> to
> o = ipmitool("-H", hostname, ,"-I", "lanplus", "-U", usrname, "-P", password,
> "chassis", "power", "status")
> this issue will be addressed in next release.
--
This message 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-4497) [doc] Update Installation Guide
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-4497: - Description: • Update the supported operating systems and hypervisor versions. • Where the current documentation directs you to run the script cloud-setup-databases, use the following name instead: cloudstack-setup-databases. • When seeding the system VM template, use the following new path to the script: /usr/share/ cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt. • The location of Management Server configuration and properties files is now /etc/cloudstack/ management/. For example, in database failover setup (an optional part of installation), where the current documentation shows /etc/cloud/management/db.properties, use the following path instead: /etc/cloudstack/management/db.properties. • The names of the Management Server and Usage Server services have changed to cloudstack- management and cloudstack-usage. Use this name in commands to start, stop, or restart these services. • System VM templates have changed. Be sure to download the latest templates from Location: To Be Supplied • The location of the Management Server log file is now /var/log/cloudstack/management/. • (XenServer only) The script cloud-setup-bonding.sh is now located at /usr/share/cloudstack- common/scripts/vm/hypervisor/xenserver/. • (XenServer only) In the procedure for upgrading XenServer versions, you copy some files from the Management Server to the XenServer host. The new location of these files on the Management Server is /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver and /usr/share/cloudstack- common/scripts/vm/hypervisor/xenserver/xenserver60. • (KVM only) During network configuration, where the current documentation shows /etc/cloud/agent/agent.properties, use the following path instead: /etc/cloudstack/agent/agent.properties. • (KVM only) The location of the CloudPlatform KVM agent log file is now /var/log/cloudstack/agent/. • (KVM only) The location of configuration and properties files is now /etc/cloudstack/agent. • (KVM only) The name of the CloudPlatform agent script has changed to cloudstack-agent. Use this name if you need to stop or restart the agent on the KVM host. was: Update the supported operating systems and hypervisor versions. • Where the current documentation directs you to run the script cloud-setup-databases, use the following name instead: cloudstack-setup-databases. • When seeding the system VM template, use the following new path to the script: /usr/share/ cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt. • The location of Management Server configuration and properties files is now /etc/cloudstack/ management/. For example, in database failover setup (an optional part of installation), where the current documentation shows /etc/cloud/management/db.properties, use the following path instead: /etc/cloudstack/management/db.properties. • The names of the Management Server and Usage Server services have changed to cloudstack- management and cloudstack-usage. Use this name in commands to start, stop, or restart these services. • System VM templates have changed. Be sure to download the latest templates from Location: To Be Supplied • The location of the Management Server log file is now /var/log/cloudstack/management/. • (XenServer only) The script cloud-setup-bonding.sh is now located at /usr/share/cloudstack- common/scripts/vm/hypervisor/xenserver/. • (XenServer only) In the procedure for upgrading XenServer versions, you copy some files from the Management Server to the XenServer host. The new location of these files on the Management Server is /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver and /usr/share/cloudstack- common/scripts/vm/hypervisor/xenserver/xenserver60. • (KVM only) During network configuration, where the current documentation shows /etc/cloud/agent/agent.properties, use the following path instead: /etc/cloudstack/agent/agent.properties. • (KVM only) The location of the CloudPlatform KVM agent log file is now /var/log/cloudstack/agent/. • (KVM only) The location of configuration and properties files is now /etc/cloudstack/agent. • (KVM only) The name of the CloudPlatform agent script has changed to cloudstack-agent. Use this name if you need to stop or restart the agent on the KVM host. > [doc] Update Installation Guide > --- > > Key: CLOUDSTACK-4497 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4497 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair > > • Update the supported operating systems and
[jira] [Commented] (CLOUDSTACK-4550) [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have migration work
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754873#comment-13754873 ] Jessica Tomechak commented on CLOUDSTACK-4550: -- Not sure I understand the description given. Can anyone (Edison?) please explain this further. The description seems to say you have to rename the bridges after you rename the bridges. > [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have > migration work > -- > > Key: CLOUDSTACK-4550 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4550 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc, KVM, Upgrade >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Assignee: Jessica Tomechak >Priority: Critical > > See CLOUDSTACK-4405 for the original bug. This is the doc to be prepared as > part of upgrade in release notes once the fix for the bug is verified to work > After network bridges being renamed from cloudVirBrVLAN to brem1-VLAN rename > the bridges to allow migration to work between host added before upgrade to > those added after upgrade > This can be done by running the cloudstack-agent-upgrade script -- 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-774) Supporting kickstart in CloudStack baremetal
[ https://issues.apache.org/jira/browse/CLOUDSTACK-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753084#comment-13753084 ] Jessica Tomechak commented on CLOUDSTACK-774: - Can't have time to convert the attached .doc to XML. Can we stick it in the wiki, or generate a PDF from it and post it as a standalone guide? > Supporting kickstart in CloudStack baremetal > > > Key: CLOUDSTACK-774 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-774 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Baremetal >Affects Versions: 4.1.0 >Reporter: frank zhang >Assignee: Jessica Tomechak > Fix For: 4.2.0 > > Attachments: CLOUDSTACK-774-baremetal-support.patch, > CLOUDSTACK-774-baremetal-support.patch.md5sum, > CLOUDSTACK-774-baremetal-support.patch.sig > > > Supporting kickstart install for RedHat like Linux in CloudStack Baremetal > provisioning > Release Planning: > Dev List Discussion: http://markmail.org/message/m6tg5nzfgqiwhzre > Functional Spec: https://cwiki.apache.org/CLOUDSTACK/baremetal-kickstart.html > Feature Branch: master > progress: 90% -- This message 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-883) Document 3rd party plugin feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-883: Assignee: Sudha Ponnaganti (was: Jessica Tomechak) > Document 3rd party plugin feature > - > > Key: CLOUDSTACK-883 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-883 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers >Assignee: Sudha Ponnaganti > 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] [Updated] (CLOUDSTACK-883) Document 3rd party plugin feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-883: Status: Ready To Review (was: In Progress) > Document 3rd party plugin feature > - > > Key: CLOUDSTACK-883 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-883 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers >Assignee: Jessica Tomechak > 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] [Commented] (CLOUDSTACK-883) Document 3rd party plugin feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752735#comment-13752735 ] Jessica Tomechak commented on CLOUDSTACK-883: - The same doc is also posted on the project wiki. > Document 3rd party plugin feature > - > > Key: CLOUDSTACK-883 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-883 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers >Assignee: Jessica Tomechak > 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] [Commented] (CLOUDSTACK-2407) Document zone wide primary storage support for VMware deployments
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752732#comment-13752732 ] Jessica Tomechak commented on CLOUDSTACK-2407: -- Review comment incorporated. > Document zone wide primary storage support for VMware deployments > - > > Key: CLOUDSTACK-2407 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2407 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Jessica Tomechak > 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] [Updated] (CLOUDSTACK-864) Document Zone-wide primary storage target
[ https://issues.apache.org/jira/browse/CLOUDSTACK-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-864: Assignee: Sudha Ponnaganti (was: Jessica Tomechak) > Document Zone-wide primary storage target > - > > Key: CLOUDSTACK-864 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-864 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Sudha Ponnaganti > Fix For: 4.2.0 > > > Document Zone-wide primary storage target -- 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-2407) Document zone wide primary storage support for VMware deployments
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-2407: - Assignee: Sudha Ponnaganti (was: Jessica Tomechak) > Document zone wide primary storage support for VMware deployments > - > > Key: CLOUDSTACK-2407 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2407 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Sudha Ponnaganti > 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] [Updated] (CLOUDSTACK-2407) Document zone wide primary storage support for VMware deployments
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-2407: - Status: Ready To Review (was: In Progress) > Document zone wide primary storage support for VMware deployments > - > > Key: CLOUDSTACK-2407 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2407 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Jessica Tomechak > 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] [Updated] (CLOUDSTACK-864) Document Zone-wide primary storage target
[ https://issues.apache.org/jira/browse/CLOUDSTACK-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-864: Status: Ready To Review (was: In Progress) > Document Zone-wide primary storage target > - > > Key: CLOUDSTACK-864 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-864 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.2.0 > > > Document Zone-wide primary storage target -- 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-900) Document enable storage xenmotion support in XenServer 6.1 feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-900: Assignee: Sudha Ponnaganti (was: Jessica Tomechak) > Document enable storage xenmotion support in XenServer 6.1 feature > -- > > Key: CLOUDSTACK-900 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-900 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers >Assignee: Sudha Ponnaganti > 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] [Updated] (CLOUDSTACK-900) Document enable storage xenmotion support in XenServer 6.1 feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-900: Status: Ready To Review (was: In Progress) > Document enable storage xenmotion support in XenServer 6.1 feature > -- > > Key: CLOUDSTACK-900 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-900 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers >Assignee: Jessica Tomechak > 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] [Updated] (CLOUDSTACK-2289) Doc- Granular Global Param
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-2289: - Assignee: Sudha Ponnaganti (was: Jessica Tomechak) > Doc- Granular Global Param > -- > > Key: CLOUDSTACK-2289 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2289 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Sudha Ponnaganti > 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] [Updated] (CLOUDSTACK-2289) Doc- Granular Global Param
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-2289: - Status: Ready To Review (was: In Progress) > Doc- Granular Global Param > -- > > Key: CLOUDSTACK-2289 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2289 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.2.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] [Updated] (CLOUDSTACK-2405) Document change account membership
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-2405: - Status: Ready To Review (was: In Progress) > Document change account membership > -- > > Key: CLOUDSTACK-2405 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2405 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Jessica Tomechak > Fix For: 4.2.0 > > > A root administrator can now change the ownership of any virtual machine, > network, data disk, snapshot, template, or ISO from one account to any other > account. A domain or sub-domain administrator can do the same for items > within the domain from one account to any other account in the domain. > Additional documentation to be supplied. -- This message 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-2405) Document change account membership
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-2405: - Assignee: Sudha Ponnaganti (was: Jessica Tomechak) > Document change account membership > -- > > Key: CLOUDSTACK-2405 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2405 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Sudha Ponnaganti > Fix For: 4.2.0 > > > A root administrator can now change the ownership of any virtual machine, > network, data disk, snapshot, template, or ISO from one account to any other > account. A domain or sub-domain administrator can do the same for items > within the domain from one account to any other account in the domain. > Additional documentation to be supplied. -- This message 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-3298) Documentation for Deploy Virtual Machine Userdata Enhancements
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-3298: - Assignee: Sudha Ponnaganti (was: Jessica Tomechak) > Documentation for Deploy Virtual Machine Userdata Enhancements > -- > > Key: CLOUDSTACK-3298 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3298 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Sudha Ponnaganti > 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] [Updated] (CLOUDSTACK-3298) Documentation for Deploy Virtual Machine Userdata Enhancements
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-3298: - Status: Ready To Review (was: In Progress) > Documentation for Deploy Virtual Machine Userdata Enhancements > -- > > Key: CLOUDSTACK-3298 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3298 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.2.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-3298) Documentation for Deploy Virtual Machine Userdata Enhancements
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak reassigned CLOUDSTACK-3298: Assignee: Jessica Tomechak > Documentation for Deploy Virtual Machine Userdata Enhancements > -- > > Key: CLOUDSTACK-3298 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3298 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.2.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] [Comment Edited] (CLOUDSTACK-818) Document Dedicate Pod, Cluster or Host to a domain
[ https://issues.apache.org/jira/browse/CLOUDSTACK-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752210#comment-13752210 ] Jessica Tomechak edited comment on CLOUDSTACK-818 at 8/28/13 4:10 PM: -- For ease of reviewing, here is the full draft: Dedicating Resources to Accounts and Domains The root administrator can dedicate resources to a specific domain or account that needs private infrastructure for additional security or performance guarantees. A zone, pod, cluster, or host can be reserved by the root administrator for a specific domain or account. Only users in that domain or its subdomain may use the infrastructure. For example, only users in a given domain can create guests in a zone dedicated to that domain. There are several types of dedication available: Explicit dedication. A zone, pod, cluster, or host is dedicated to an account or domain by the root administrator during initial deployment and configuration. Strict implicit dedication. A host will not be shared across multiple accounts. For example, strict implicit dedication is useful for deployment of certain types of applications, such as desktops, where no host can be shared between different accounts without violating the desktop software's terms of license. Preferred implicit dedication. The VM will be deployed in dedicated infrastructure if possible. Otherwise, the VM can be deployed in shared infrastructure. How to Dedicate a Zone, Cluster, Pod, or Host to an Account or Domain For explicit dedication: When deploying a new zone, pod, cluster, or host, the root administrator can click the Dedicated checkbox, then choose a domain or account to own the resource. To explicitly dedicate an existing zone, pod, cluster, or host: log in as the root admin, find the resource in the UI, and click the Dedicate button. For implicit dedication: The administrator creates a compute service offering and in the Deployment Planner field, chooses ImplicitDedicationPlanner. Then in Planner Mode, the administrator specifies either Strict or Preferred, depending on whether it is permissible to allow some use of shared resources when dedicated resources are not available. Whenever a user creates a VM based on this service offering, it is allocated on one of the dedicated hosts. How to Use Dedicated Hosts To use an explicitly dedicated host, use the explicit-dedicated type of affinity group (see Affinity Groups). For example, when creating a new VM, an end user can choose to place it on dedicated infrastructure. This operation will succeed only if some infrastructure has already been assigned as dedicated to the user's account or domain. Behavior of Dedicated Hosts, Clusters, Pods, and Zones The administrator can live migrate VMs away from dedicated hosts if desired, whether the destination is a host reserved for a different account/domain or a host that is shared (not dedicated to any particular account or domain). CloudStack will generate an alert, but the operation is allowed. Dedicated hosts can be used in conjunction with host tags. If both a host tag and dedication are requested, the VM will be placed only on a host that meets both requirements. If there is no dedicated resource available to that user that also has the host tag requested by the user, then the VM will not deploy. If you delete an account or domain, any hosts, clusters, pods, and zones that were dedicated to it are freed up. They will now be available to be shared by any account or domain, or the administrator may choose to re-dedicate them to a different account or domain. System VMs and virtual routers affect the behavior of host dedication. System VMs and virtual routers are owned by the CloudStack system account, and they can be deployed on any host. They do not adhere to explicit dedication. The presence of system vms and virtual routers on a host makes it unsuitable for strict implicit dedication. The host can not be used for strict implicit dedication, because the host already has VMs of a specific account (the default system account). However, a host with system VMs or virtual routers can be used for preferred implicit dedication. was (Author: jtomechak): For ease of reviewing, here is the full draft: Dedicating Resources to Accounts and Domains The root administrator can dedicate resources to a specific domain or account that needs private infrastructure for additional security or performance guarantees. A zone, pod, cluster, or host can be reserved by the root administrator for a specific domain or account. Only users in that domain or its subdomain may use the infrastructure. For example, only users in a given domain can create guests in a zone dedicated to that domain. There are several types of dedication available: Explicit dedication. A zone, pod, cluster, or host
[jira] [Commented] (CLOUDSTACK-818) Document Dedicate Pod, Cluster or Host to a domain
[ https://issues.apache.org/jira/browse/CLOUDSTACK-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752210#comment-13752210 ] Jessica Tomechak commented on CLOUDSTACK-818: - For ease of reviewing, here is the full draft: Dedicating Resources to Accounts and Domains The root administrator can dedicate resources to a specific domain or account that needs private infrastructure for additional security or performance guarantees. A zone, pod, cluster, or host can be reserved by the root administrator for a specific domain or account. Only users in that domain or its subdomain may use the infrastructure. For example, only users in a given domain can create guests in a zone dedicated to that domain. There are several types of dedication available: Explicit dedication. A zone, pod, cluster, or host is dedicated to an account or domain by the root administrator during initial deployment and configuration. Strict implicit dedication. A host will not be shared across multiple accounts. For example, strict implicit dedication is useful for deployment of certain types of applications, such as desktops, where no host can be shared between different accounts without violating the desktop software's terms of license. Preferred implicit dedication. The VM will be deployed in dedicated infrastructure if possible. Otherwise, the VM can be deployed in shared infrastructure. How to Dedicate a Zone, Cluster, Pod, or Host to an Account or Domain For explicit dedication: When deploying a new zone, pod, cluster, or host, the root administrator can click the Dedicated checkbox, then choose a domain or account to own the resource. To explicitly dedicate an existing zone, pod, cluster, or host: log in as the root admin, find the resource in the UI, and click the Dedicate button. For implicit dedication: The administrator creates a compute service offering and in the Deployment Planner field, chooses ImplicitDedicationPlanner. Then in Planner Mode, the administrator specifies either Strict or Preferred, depending on whether it is permissible to allow some use of shared resources when dedicated resources are not available. Whenever a user creates a VM based on this service offering, it is allocated on one of the dedicated hosts. How to Use Dedicated Hosts To use an explicitly dedicated host, use the explicit-dedicated type of affinity group (see Affinity Groups). For example, when creating a new VM, an end user can choose to place it on dedicated infrastructure. This operation will succeed only if some infrastructure has already been assigned as dedicated to the user's account or domain. Behavior of Dedicated Hosts, Clusters, Pods, and Zones The administrator can live migrate VMs away from dedicated hosts if desired, whether the destination is a host reserved for a different account/domain or a host that is shared (not dedicated to any particular account or domain). CloudPlatform will generate an alert, but the operation is allowed. Dedicated hosts can be used in conjunction with host tags. If both a host tag and dedication are requested, the VM will be placed only on a host that meets both requirements. If there is no dedicated resource available to that user that also has the host tag requested by the user, then the VM will not deploy. If you delete an account or domain, any hosts, clusters, pods, and zones that were dedicated to it are freed up. They will now be available to be shared by any account or domain, or the administrator may choose to re-dedicate them to a different account or domain. System VMs and virtual routers affect the behavior of host dedication. System VMs and virtual routers are owned by the CloudPlatform system account, and they can be deployed on any host. They do not adhere to explicit dedication. The presence of system vms and virtual routers on a host makes it unsuitable for strict implicit dedication. The host can not be used for strict implicit dedication, because the host already has VMs of a specific account (the default system account). However, a host with system VMs or virtual routers can be used for preferred implicit dedication. > Document Dedicate Pod, Cluster or Host to a domain > -- > > Key: CLOUDSTACK-818 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-818 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.2.0 > > > Dedicate Pod, Cluster or Host to a domain- Documentation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more informa
[jira] [Commented] (CLOUDSTACK-818) Document Dedicate Pod, Cluster or Host to a domain
[ https://issues.apache.org/jira/browse/CLOUDSTACK-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752210#comment-13752210 ] Jessica Tomechak commented on CLOUDSTACK-818: - For ease of reviewing, here is the full draft: Dedicating Resources to Accounts and Domains The root administrator can dedicate resources to a specific domain or account that needs private infrastructure for additional security or performance guarantees. A zone, pod, cluster, or host can be reserved by the root administrator for a specific domain or account. Only users in that domain or its subdomain may use the infrastructure. For example, only users in a given domain can create guests in a zone dedicated to that domain. There are several types of dedication available: Explicit dedication. A zone, pod, cluster, or host is dedicated to an account or domain by the root administrator during initial deployment and configuration. Strict implicit dedication. A host will not be shared across multiple accounts. For example, strict implicit dedication is useful for deployment of certain types of applications, such as desktops, where no host can be shared between different accounts without violating the desktop software's terms of license. Preferred implicit dedication. The VM will be deployed in dedicated infrastructure if possible. Otherwise, the VM can be deployed in shared infrastructure. How to Dedicate a Zone, Cluster, Pod, or Host to an Account or Domain For explicit dedication: When deploying a new zone, pod, cluster, or host, the root administrator can click the Dedicated checkbox, then choose a domain or account to own the resource. To explicitly dedicate an existing zone, pod, cluster, or host: log in as the root admin, find the resource in the UI, and click the Dedicate button. For implicit dedication: The administrator creates a compute service offering and in the Deployment Planner field, chooses ImplicitDedicationPlanner. Then in Planner Mode, the administrator specifies either Strict or Preferred, depending on whether it is permissible to allow some use of shared resources when dedicated resources are not available. Whenever a user creates a VM based on this service offering, it is allocated on one of the dedicated hosts. How to Use Dedicated Hosts To use an explicitly dedicated host, use the explicit-dedicated type of affinity group (see Affinity Groups). For example, when creating a new VM, an end user can choose to place it on dedicated infrastructure. This operation will succeed only if some infrastructure has already been assigned as dedicated to the user's account or domain. Behavior of Dedicated Hosts, Clusters, Pods, and Zones The administrator can live migrate VMs away from dedicated hosts if desired, whether the destination is a host reserved for a different account/domain or a host that is shared (not dedicated to any particular account or domain). CloudPlatform will generate an alert, but the operation is allowed. Dedicated hosts can be used in conjunction with host tags. If both a host tag and dedication are requested, the VM will be placed only on a host that meets both requirements. If there is no dedicated resource available to that user that also has the host tag requested by the user, then the VM will not deploy. If you delete an account or domain, any hosts, clusters, pods, and zones that were dedicated to it are freed up. They will now be available to be shared by any account or domain, or the administrator may choose to re-dedicate them to a different account or domain. System VMs and virtual routers affect the behavior of host dedication. System VMs and virtual routers are owned by the CloudPlatform system account, and they can be deployed on any host. They do not adhere to explicit dedication. The presence of system vms and virtual routers on a host makes it unsuitable for strict implicit dedication. The host can not be used for strict implicit dedication, because the host already has VMs of a specific account (the default system account). However, a host with system VMs or virtual routers can be used for preferred implicit dedication. > Document Dedicate Pod, Cluster or Host to a domain > -- > > Key: CLOUDSTACK-818 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-818 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.2.0 > > > Dedicate Pod, Cluster or Host to a domain- Documentation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more informa
[jira] [Updated] (CLOUDSTACK-815) Document AWS Style Regions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-815: Assignee: Sudha Ponnaganti (was: Jessica Tomechak) > Document AWS Style Regions > -- > > Key: CLOUDSTACK-815 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-815 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Sudha Ponnaganti > Fix For: 4.1.0, 4.2.0 > > > Document AWS Style Regions -- 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-815) Document AWS Style Regions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-815: Status: Ready To Review (was: In Progress) > Document AWS Style Regions > -- > > Key: CLOUDSTACK-815 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-815 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.1.0, 4.2.0 > > > Document AWS Style Regions -- 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] [Reopened] (CLOUDSTACK-815) Document AWS Style Regions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak reopened CLOUDSTACK-815: - Reopening to add more docs for this feature. > Document AWS Style Regions > -- > > Key: CLOUDSTACK-815 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-815 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.1.0 > > > Document AWS Style Regions -- 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-815) Document AWS Style Regions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-815: Fix Version/s: 4.2.0 > Document AWS Style Regions > -- > > Key: CLOUDSTACK-815 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-815 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.1.0, 4.2.0 > > > Document AWS Style Regions -- 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] [Resolved] (CLOUDSTACK-1743) No Section on About Password and Key Encryption Though Multiple References Appear in the Install Guide
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak resolved CLOUDSTACK-1743. -- Resolution: Fixed I see the section in the latest build of the 4.2 Install Guide, so resolving the bug. > No Section on About Password and Key Encryption Though Multiple References > Appear in the Install Guide > -- > > Key: CLOUDSTACK-1743 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1743 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.0.1 >Reporter: Radhika Nair >Priority: Minor > Fix For: 4.2.0 > > > The following section is missing in the Install Guide: > > About Password and Key Encryption > &PRODUCT; stores several sensitive passwords and secret keys that are > used to provide > security. These values are always automatically encrypted: > > > Database secret key > > > Database password > > > SSH keys > > > Compute node root password > > >VPN password > > > User API secret key > > > VNC password > > > &PRODUCT; uses the Java Simplified Encryption (JASYPT) library. The > data values are > encrypted and decrypted using a database secret key, which is stored in > one of &PRODUCT;’s > internal properties files along with the database password. The other > encrypted values listed > above, such as SSH keys, are in the &PRODUCT; internal database. > Of course, the database secret key itself can not be stored in the > open – it must be > encrypted. How then does &PRODUCT; read it? A second secret key must be > provided from an > external source during Management Server startup. This key can be > provided in one of two ways: > loaded from a file or provided by the &PRODUCT; administrator. The > &PRODUCT; database has a new > configuration setting that lets it know which of these methods will be > used. If the encryption > type is set to “file,” the key must be in a file in a known location. If > the encryption type is > set to “web,” the administrator runs the utility > com.cloud.utils.crypt.EncryptionSecretKeySender, which relays the key to > the Management Server > over a known port. > The encryption type, database secret key, and Management Server > secret key are set during > &PRODUCT; installation. They are all parameters to the &PRODUCT; database > setup script > (cloud-setup-databases). The default values are file, password, and > password. It is, of course, > highly recommended that you change these to more secure keys. > -- 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-1932) AutoScale UI documentation doesn't mention the option appears only for NetScaler
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak reassigned CLOUDSTACK-1932: Assignee: Jessica Tomechak > AutoScale UI documentation doesn't mention the option appears only for > NetScaler > > > Key: CLOUDSTACK-1932 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1932 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.1.0, 4.2.0 >Reporter: Jessica Tomechak >Assignee: Jessica Tomechak >Priority: Minor > Fix For: 4.2.0 > > > This affects add-load-balancer-rule.xml and autoscale.xml. > In add-load-balancer-rule.xml, in the step "Fill in the following:", the > bullet item AutoScale should note that this option appears only when > NetScaler is selected as a service provider for the network where you are > defining the LB rule. > And in autoscale.xml, there should be a note right at the top like > "(NetScaler only)" or "(Supported only in networks where the Citrix NetScaler > is used.)" -- This message 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-3635) [DOC][Dynamic Scaling][VMware] Guest OS support information
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak reassigned CLOUDSTACK-3635: Assignee: Jessica Tomechak > [DOC][Dynamic Scaling][VMware] Guest OS support information > --- > > Key: CLOUDSTACK-3635 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3635 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Sateesh Chodapuneedi >Assignee: Jessica Tomechak > Labels: adminguide, installguide, release > Fix For: 4.2.0 > > > Dynamic scaling of VM consists of scaling CPU & MEMORY of running VM. > The ability to hotadd cpu or memory depends on Guest operating system version > (like CentOS 5.3) and bits of the OS (like 64 bit). > CloudStack does query Guest OS information available in ESXi information > using vSphere API. But this information is not granular to the level of exact > version of guest operating system and bitness (32 or 64). Hence it is > recommended that user verify if the VM is installed with guest operating > system which supports cpu or memory hotadd features from following link. > http://www.vmware.com/resources/compatibility/search.php?deviceCategory=software&testConfig=16&productid=17364 -- This message 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-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 ] Jessica Tomechak updated CLOUDSTACK-3466: - Assignee: Radhika Nair > [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: Radhika Nair > Fix For: 4.2.0 > > > 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.ru
[jira] [Commented] (CLOUDSTACK-3635) [DOC][Dynamic Scaling][VMware] Guest OS support information
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751850#comment-13751850 ] Jessica Tomechak commented on CLOUDSTACK-3635: -- I worked on docs for this feature, so assigning this small update to myself. > [DOC][Dynamic Scaling][VMware] Guest OS support information > --- > > Key: CLOUDSTACK-3635 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3635 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Sateesh Chodapuneedi >Assignee: Jessica Tomechak > Labels: adminguide, installguide, release > Fix For: 4.2.0 > > > Dynamic scaling of VM consists of scaling CPU & MEMORY of running VM. > The ability to hotadd cpu or memory depends on Guest operating system version > (like CentOS 5.3) and bits of the OS (like 64 bit). > CloudStack does query Guest OS information available in ESXi information > using vSphere API. But this information is not granular to the level of exact > version of guest operating system and bitness (32 or 64). Hence it is > recommended that user verify if the VM is installed with guest operating > system which supports cpu or memory hotadd features from following link. > http://www.vmware.com/resources/compatibility/search.php?deviceCategory=software&testConfig=16&productid=17364 -- This message 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-2121) Document affinity / anti-affinity rules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-2121: - Assignee: Sudha Ponnaganti (was: Jessica Tomechak) > Document affinity / anti-affinity rules > --- > > Key: CLOUDSTACK-2121 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2121 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Sudha Ponnaganti > 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] [Updated] (CLOUDSTACK-2121) Document affinity / anti-affinity rules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-2121: - Status: Ready To Review (was: In Progress) > Document affinity / anti-affinity rules > --- > > Key: CLOUDSTACK-2121 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2121 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Jessica Tomechak > 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] [Updated] (CLOUDSTACK-818) Document Dedicate Pod, Cluster or Host to a domain
[ https://issues.apache.org/jira/browse/CLOUDSTACK-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-818: Assignee: Jessica Tomechak (was: Prachi Damle) > Document Dedicate Pod, Cluster or Host to a domain > -- > > Key: CLOUDSTACK-818 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-818 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.2.0 > > > Dedicate Pod, Cluster or Host to a domain- Documentation -- 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-818) Document Dedicate Pod, Cluster or Host to a domain
[ https://issues.apache.org/jira/browse/CLOUDSTACK-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751706#comment-13751706 ] Jessica Tomechak commented on CLOUDSTACK-818: - First draft docs on this were submitted to the wrong bug number. Here is the commit: Commit 2d08a322dd976e696783535a0f3d174483adf155 in branch refs/heads/4.2-forward from Jessica Tomechak [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2d08a32 ] CLOUDSTACK-2121. DOC. New docs for affinity groups. > Document Dedicate Pod, Cluster or Host to a domain > -- > > Key: CLOUDSTACK-818 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-818 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.2.0 > > > Dedicate Pod, Cluster or Host to a domain- Documentation -- 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-818) Document Dedicate Pod, Cluster or Host to a domain
[ https://issues.apache.org/jira/browse/CLOUDSTACK-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-818: Status: Ready To Review (was: In Progress) > Document Dedicate Pod, Cluster or Host to a domain > -- > > Key: CLOUDSTACK-818 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-818 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.2.0 > > > Dedicate Pod, Cluster or Host to a domain- Documentation -- 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-818) Document Dedicate Pod, Cluster or Host to a domain
[ https://issues.apache.org/jira/browse/CLOUDSTACK-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-818: Assignee: Prachi Damle (was: Jessica Tomechak) > Document Dedicate Pod, Cluster or Host to a domain > -- > > Key: CLOUDSTACK-818 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-818 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Prachi Damle > Fix For: 4.2.0 > > > Dedicate Pod, Cluster or Host to a domain- Documentation -- 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-2407) Document zone wide primary storage support for VMware deployments
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-2407: - Assignee: Sudha Ponnaganti (was: Jessica Tomechak) > Document zone wide primary storage support for VMware deployments > - > > Key: CLOUDSTACK-2407 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2407 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Sudha Ponnaganti > 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] [Updated] (CLOUDSTACK-2407) Document zone wide primary storage support for VMware deployments
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-2407: - Status: Ready To Review (was: In Progress) > Document zone wide primary storage support for VMware deployments > - > > Key: CLOUDSTACK-2407 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2407 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Jessica Tomechak > 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] [Commented] (CLOUDSTACK-2407) Document zone wide primary storage support for VMware deployments
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751061#comment-13751061 ] Jessica Tomechak commented on CLOUDSTACK-2407: -- Docs for this feature were committed under CLOUDSTACK-864. > Document zone wide primary storage support for VMware deployments > - > > Key: CLOUDSTACK-2407 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2407 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Jessica Tomechak > 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] [Updated] (CLOUDSTACK-3390) Documentation for Mapping CloudStack Zone and VMWare Datacenter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-3390: - Assignee: Sudha Ponnaganti (was: Jessica Tomechak) > Documentation for Mapping CloudStack Zone and VMWare Datacenter > --- > > Key: CLOUDSTACK-3390 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3390 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc, VMware >Reporter: Radhika Nair >Assignee: Sudha Ponnaganti > 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] [Updated] (CLOUDSTACK-864) Document Zone-wide primary storage target
[ https://issues.apache.org/jira/browse/CLOUDSTACK-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-864: Assignee: Sudha Ponnaganti (was: Jessica Tomechak) > Document Zone-wide primary storage target > - > > Key: CLOUDSTACK-864 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-864 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Sudha Ponnaganti > Fix For: 4.2.0 > > > Document Zone-wide primary storage target -- 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-864) Document Zone-wide primary storage target
[ https://issues.apache.org/jira/browse/CLOUDSTACK-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-864: Status: Ready To Review (was: In Progress) > Document Zone-wide primary storage target > - > > Key: CLOUDSTACK-864 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-864 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.2.0 > > > Document Zone-wide primary storage target -- 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-3390) Documentation for Mapping CloudStack Zone and VMWare Datacenter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-3390: - Status: Ready To Review (was: In Progress) > Documentation for Mapping CloudStack Zone and VMWare Datacenter > --- > > Key: CLOUDSTACK-3390 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3390 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc, VMware >Reporter: Radhika Nair >Assignee: Jessica Tomechak > 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] [Commented] (CLOUDSTACK-3390) Documentation for Mapping CloudStack Zone and VMWare Datacenter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750603#comment-13750603 ] Jessica Tomechak commented on CLOUDSTACK-3390: -- The complete doc section, added in "About Zones": In order to support zone-wide functions for VMware, &PRODUCT; is aware of VMware Datacenters and can map each Datacenter to a &PRODUCT; zone. To enable features like storage live migration and zone-wide primary storage for VMware hosts, &PRODUCT; has to make sure that a zone contains only a single VMware Datacenter. Therefore, when you are creating a new &PRODUCT; zone, you can select a VMware Datacenter for the zone. If you are provisioning multiple VMware Datacenters, each one will be set up as a single zone in &PRODUCT;. NOTE: If you are upgrading from a previous &PRODUCT; version, and your existing deployment contains a zone with clusters from multiple VMware Datacenters, that zone will not be forcibly migrated to the new model. It will continue to function as before. However, any new zone-wide operations, such as zone-wide primary storage and live storage migration, will not be available in that zone. > Documentation for Mapping CloudStack Zone and VMWare Datacenter > --- > > Key: CLOUDSTACK-3390 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3390 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc, VMware >Reporter: Radhika Nair >Assignee: Jessica Tomechak > 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] [Updated] (CLOUDSTACK-3390) Documentation for Mapping CloudStack Zone and VMWare Datacenter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-3390: - Assignee: Jessica Tomechak > Documentation for Mapping CloudStack Zone and VMWare Datacenter > --- > > Key: CLOUDSTACK-3390 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3390 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc, VMware >Reporter: Radhika Nair >Assignee: Jessica Tomechak > 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] [Commented] (CLOUDSTACK-864) Document Zone-wide primary storage target
[ https://issues.apache.org/jira/browse/CLOUDSTACK-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750567#comment-13750567 ] Jessica Tomechak commented on CLOUDSTACK-864: - Mike T. also committed some doc changes for this along with his fix to CLOUDSTACK-3291. > Document Zone-wide primary storage target > - > > Key: CLOUDSTACK-864 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-864 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.2.0 > > > Document Zone-wide primary storage target -- 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-864) Document Zone-wide primary storage target
[ https://issues.apache.org/jira/browse/CLOUDSTACK-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750564#comment-13750564 ] Jessica Tomechak commented on CLOUDSTACK-864: - This was committed to master and 4.2-forward along with object store, in the following: Commit: c2cde0b463916f4be3316dd4a8572fa96392b1d5 [c2cde0b] Parents: f814bd Author: Jessica Date: August 26, 2013 12:44:56 PM PDT CLOUDSTACK-4334. Documentation for object store. > Document Zone-wide primary storage target > - > > Key: CLOUDSTACK-864 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-864 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.2.0 > > > Document Zone-wide primary storage target -- 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-1593) Document syslog enhancements
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-1593: - Assignee: Sudha Ponnaganti (was: Jessica Tomechak) > Document syslog enhancements > > > Key: CLOUDSTACK-1593 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1593 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Sudha Ponnaganti >Priority: Minor > Fix For: 4.2.0 > > > The feature can be enabled or disabled. Need to document this configuration > setting, and tell which is the default: disabled. -- 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-1593) Document syslog enhancements
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-1593: - Status: Ready To Review (was: In Progress) > Document syslog enhancements > > > Key: CLOUDSTACK-1593 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1593 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Jessica Tomechak >Priority: Minor > Fix For: 4.2.0 > > > The feature can be enabled or disabled. Need to document this configuration > setting, and tell which is the default: disabled. -- 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-1593) Document syslog enhancements
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750555#comment-13750555 ] Jessica Tomechak commented on CLOUDSTACK-1593: -- Fixed along with CLOUDSTACK-836, which was accepted and closed. > Document syslog enhancements > > > Key: CLOUDSTACK-1593 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1593 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Jessica Tomechak >Priority: Minor > Fix For: 4.2.0 > > > The feature can be enabled or disabled. Need to document this configuration > setting, and tell which is the default: disabled. -- 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-4334) Document storage image store plugin framework
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-4334: - Assignee: Sudha Ponnaganti (was: Jessica Tomechak) > Document storage image store plugin framework > - > > Key: CLOUDSTACK-4334 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4334 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Sudha Ponnaganti > 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] [Updated] (CLOUDSTACK-4334) Document storage image store plugin framework
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-4334: - Status: Ready To Review (was: In Progress) > Document storage image store plugin framework > - > > Key: CLOUDSTACK-4334 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4334 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Jessica Tomechak > 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] [Closed] (CLOUDSTACK-867) Document Scaling up CPU and RAM for running VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak closed CLOUDSTACK-867. --- Assignee: Jessica Tomechak (was: prashant kumar mishra) > Document Scaling up CPU and RAM for running VMs > > > Key: CLOUDSTACK-867 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-867 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.2.0 > > Attachments: Dynamically_Scalable.jpg, Global_Settings.jpg, > zone_Settings .jpg > > > Document Scaling up CPU and RAM for running VMs -- This message 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] [Resolved] (CLOUDSTACK-867) Document Scaling up CPU and RAM for running VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak resolved CLOUDSTACK-867. - Resolution: Fixed Added Prashant's comments and verified against live UI. > Document Scaling up CPU and RAM for running VMs > > > Key: CLOUDSTACK-867 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-867 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: prashant kumar mishra > Fix For: 4.2.0 > > Attachments: Dynamically_Scalable.jpg, Global_Settings.jpg, > zone_Settings .jpg > > > Document Scaling up CPU and RAM for running VMs -- This message 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
