[
https://issues.apache.org/jira/browse/CLOUDSTACK-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chip Childers updated CLOUDSTACK-399:
-------------------------------------
Description:
Currently the installation guide has a section for patching/upgrading XenServer
hosts (Upgrading XenServer Versions). It would be good to have a documented
procedure for patching/upgrading vSphere as well. The following procedure has
been verified by QA.
1. Unmanage the cluster in CloudStack. This can be done from the CloudStack UI.
2. Do the following 3 steps for each of the ESXi hosts (2.a followed by 2.b,
and 2.c) in the cluster:
2.a. Move each of the ESXi hosts in the cluster to maintanance mode and ensure
all the VMs get migrated to other hosts in that cluster. If there is only 1
host in that cluster, shutdown all VMs and move the host into maintenance mode.
2.b. Apply the patch on the ESXi host. Reboot the host if required.
2.c. Move the host out of maintenance mode.
3. Manage the cluster in CloudStack. This can be done from the CloudStack UI.
4. Verify the host state is properly synchronized and updated in the Cloudstack
database (or via UI... state should be "Up").
Release Planning:
Dev list discussion: N/A
Functional Spec: N/A
Feature Branch: review board submission
QA: review during doc review for release
was:
Currently the installation guide has a section for patching/upgrading XenServer
hosts (Upgrading XenServer Versions). It would be good to have a documented
procedure for patching/upgrading vSphere as well. The following procedure has
been verified by QA.
1. Unmanage the cluster in CloudStack. This can be done from the CloudStack UI.
2. Do the following 3 steps for each of the ESXi hosts (2.a followed by 2.b,
and 2.c) in the cluster:
2.a. Move each of the ESXi hosts in the cluster to maintanance mode and ensure
all the VMs get migrated to other hosts in that cluster. If there is only 1
host in that cluster, shutdown all VMs and move the host into maintenance mode.
2.b. Apply the patch on the ESXi host. Reboot the host if required.
2.c. Move the host out of maintenance mode.
3. Manage the cluster in CloudStack. This can be done from the CloudStack UI.
4. Verify the host state is properly synchronized and updated in the Cloudstack
database (or via UI... state should be "Up").
> Document vSphere / ESXi patch installation procedure
> ----------------------------------------------------
>
> Key: CLOUDSTACK-399
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-399
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc
> Affects Versions: 4.0.0
> Reporter: Kirk Kosinski
> Assignee: Radhika Nair
> Priority: Minor
> Labels: installguide
> Fix For: 4.1.0
>
>
> Currently the installation guide has a section for patching/upgrading
> XenServer hosts (Upgrading XenServer Versions). It would be good to have a
> documented procedure for patching/upgrading vSphere as well. The following
> procedure has been verified by QA.
> 1. Unmanage the cluster in CloudStack. This can be done from the CloudStack
> UI.
> 2. Do the following 3 steps for each of the ESXi hosts (2.a followed by 2.b,
> and 2.c) in the cluster:
> 2.a. Move each of the ESXi hosts in the cluster to maintanance mode and
> ensure all the VMs get migrated to other hosts in that cluster. If there is
> only 1 host in that cluster, shutdown all VMs and move the host into
> maintenance mode.
> 2.b. Apply the patch on the ESXi host. Reboot the host if required.
> 2.c. Move the host out of maintenance mode.
> 3. Manage the cluster in CloudStack. This can be done from the CloudStack UI.
> 4. Verify the host state is properly synchronized and updated in the
> Cloudstack database (or via UI... state should be "Up").
> Release Planning:
> Dev list discussion: N/A
> Functional Spec: N/A
> Feature Branch: review board submission
> QA: review during doc review for 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
