The system configuration that configures the L-Platform in use can be modified on the [Reconfigure] page.
Note
[Reconfigure] page allows the configuration of the L-Platform to be modified. However, this may only be used when modifications to the configuration of the L-Platform template have been allowed by the infrastructure administrator.
When reconfiguring an already deployed server, the items that can be reconfigured differ depending on the type and power status of the target server.
[Virtual server]
The server is not running
Items other than the following can be changed:
Storage pool
VM pool
Storage pool of the system disk
Storage pool of the deployed data disk
VM host
Virtual storage of the system disk
Virtual storage of the deployed data disk
The server is running
The following items can be changed:
Change the L-Platform name
Change the server name
Change the disk name
Add a server
Add a disk
Change the boot priority
Change the segment name
IP address
Along with these, there are items that can be modified depending on the type of server virtualization software. Details are shown below. However, refer to "NIC Add and Delete" for information on adding and deleting NICs.
Item name | Change type | Server virtualization software | ||||||
|---|---|---|---|---|---|---|---|---|
VMware | Hyper-V | RHEL-KVM | Solaris Zones | Citrix XenServer | OVM for X86 | OVM for SPARC | ||
Number of CPUs | Add | Y | N | N | Y | N | N | Y |
Reduce | N | N | N | Y | N | N | Y | |
CPU Performance | Add | Y | Y | Y | Y | N | Y | - |
Reduce | Y | Y | Y | Y | N | Y | - | |
CPU Reserved | Add | Y | Y | - | - | - | - | - |
Reduce | Y | Y | - | - | - | - | - | |
[VMware] | Add | Y | Y | - | - | N | - | - |
Reduce | Y | Y | - | - | N | - | - | |
Memory Size | Add | Y | N | O | Y | N | N | Y |
Reduce | N | N | O | Y | N | N | Y | |
[VMware] | Add | Y | N | - | - | N | - | - |
Reduce | Y | N | - | - | N | - | - | |
[VMware] | Add | Y | Y | - | - | - | - | - |
Reduce | Y | Y | - | - | - | - | - | |
Server Type | Modify | Y | Y | Y | Y | Y | Y | Y |
Data disk size | Extend | Y | N | - | - | - | - | - |
Host Name | Modify | Y | O | O | O | O | O | O |
Y: Can be changed when the server is running
O: Depending on the system configuration, cannot be changed during server startup.
N: Cannot be changed when the server is running
- : No item or cannot be specified
[Physical server]
Regardless of the power status, only the following items can be changed.
Change the L-Platform name
Change the server name
Change the disk name
Add a server
Add a disk
Change the server type
Change the boot priority
Change the segment name
Change the host name
Regardless of whether or not an L-Platform reconfiguration completion notification email is received, check with the Infrastructure Administrator if an L-Platform is not changed. In this case, the change processing may have failed at the virtual server.
Note the following points for Solaris Zones management servers:
It may not be possible to get server CPU performance, the number of CPUs, and memory size. "-" is displayed if this is the case.
When the OS of the virtual server is Solaris 10, attaching and detaching of disks is not possible.
When the virtual server OS is Solaris 11, disks already deployed cannot be deleted.
The following operations are not possible:
Changes to NIC configuration
Disk size changes
If the resource pool where the server is operating is not being managed by this product, it is not possible to change the number of CPUs, CPU performance, memory size, server name, or boot priority when changing configuration after deployment.
If the resource pool where the server is operating is not being managed by this product, redundancy and automatic server release will not be changed even if the server type is changed.
The number of CPUs and CPU performance may be different to the values allocated when the subscription was made. In this case, the number of CPUs and the CPU performance are adjusted so that the number of CPUs times the CPU performance becomes the same value.
With Solaris 10 not managed by BladeLogic, reconfiguration of servers is not possible.
If Server Type is changed, the following items are changed at the same time.
[Virtual server]
Number of CPUs
CPU Performance
CPU Reserved
CPU Shares/ CPU Weight
Memory Size
Memory Reserved/Memory RAM
Memory Shares/ Memory Weight
Heartbeat
Redundancy
Automatic server release
When changing only Redundancy, Heartbeat, or Automatic server release, set the CPU and memory items back to their previous values after changing Server Type.
[Physical server]
Heartbeat
Redundancy
Automatic server release
Server load balancers (SLB) cannot be added or deleted by changing the L-Platform configuration.
If the number of NICs is increased, IP addresses will not be automatically set on the guest OS. After increasing the number of NICs, log into the guest OS and manually set the IP address displayed in the [L-Platforms] tab.
After setting the IP address, check that the added NIC can communicate properly with other devices.
If two or more NICs are being added, it is recommended to add one by one.
If two or more NICs have been added at the same time, correctly set the IP address of each added NIC by setting the IP address and checking the communication for one NIC at a time.
If a NIC being deleted has been configured on the guest OS, the deletion on the L-Platform tab does not delete the configuration from the guest OS.
Delete the configuration of the NIC from the guest OS beforehand.
When the NIC used to connect to the guest OS is deleted, it will no longer be possible to connect to the guest OS. When deleting the NIC used to connect to the guest OS, first add an NIC to take over the connection to the guest OS and confirm the connection, then delete the NIC.
NICs cannot be added to or deleted from a server that has snapshots. When adding or deleting NICs, delete all snapshots of the server beforehand.
The CPU performance, the CPU reserved, the CPU shares/CPU weight, number of CPUs, the memory size, memory reserved/memory RAM, and the memory shares/memory weight cannot be changed for servers with the VM pool name set to "-".
If the server's VM pool name set is deleted, changed or moved, then CPU performance, number of CPUs and memory size cannot be changed.
The capacity cannot be expanded for disks whose storage pool is deleted, renamed, or moved.
Depending on the guest OS type, disks with expanded capacities may not be recognized or used by the OS. Refer to server virtualization software manuals and technical information to ensure that the expanded disk can be used.
A separate operation is required to make the expanded disk recognizable on the guest OS. Refer to manuals and technical information for each OS for information on the required operations.
When an IP address is changed, it is not automatically configured as the IP address on the guest OS. After changing an IP address, log in to the guest OS and manually configure the changed IP address.
When a host name is changed, it is not automatically configured as the host name on the guest OS. After changing a host name, log in to the guest OS and manually configure the changed host name.
The IP addresses of NICs that are the distribution targets of server load balancers (SLB) cannot be changed.
When addition of a server and changing of a server name or host name are performed at the same time, or multiple server names or host names are changed at the same time, system settings may cause names to overlap making change impossible.
This applies in cases like the following.
When a name used for a server or host before the change is specified for the server name of a server being added
When the server names or host names of multiple servers have been switched
If names overlap, perform the configuration changes in several steps.
When using the host name for the L-Server name, the host names of servers using server virtualization software other than VMware and the host names of virtual servers cannot be changed when they are running.
For servers using server virtualization software other than VMware or Hyper-V, disk capacities cannot be extended.
Follow the steps below to modify the system configuration that configures the L-Platform in use:
Display the [L-Platform Details] page.
Refer to "5.3.2 L-Platform Detailed Information Display" for information on how to display the page.
Click the [Reconfigure] button and display the [Reconfigure] page.
Modify the system configuration as required on the [Reconfigure] page.
Usage fees corresponding to the system reconfiguration will be displayed in the top-right of the window.
Point
Estimated charges for the L-Platform will only be displayed when the usage fees display is set to enabled.
The displayed usage fees will be calculated according to current prices, and not according to prices at the time of deployment.
Note
The pool cannot be changed for system disks and extended disks that have already been deployed. If a cloning image associated with the image information includes a data disk, changes to the number of disks cannot be made until deployment is complete.
When the L-Platform is modified, click the [Next] button.
The [Confirm] page will be displayed.
The difference between the old L-Platform and the new L-Platform is displayed as follows:
Item | Display format |
|---|---|
Item changed | The values of the changed items are displayed in red. The old value is displayed as "Changed from the old value". |
Item added | "*Added" is displayed after items that have been added. |
Item deleted | "*Deleted" is displayed after items that have been deleted. |
Point
[CSV output]
When the [Save as CSV] button located at the bottom left of the window is clicked, the [Select the destination to save] window is displayed where the L-Platform template can be saved as a CSV file.
The default CSV file name format is shown below. This file name can be modified as necessary.
SystemConfiguration (+ <L-Platform name> +)_ <date> + .csv
[Save specification]
Click the [Save Configuration] button to save the L-Platform configuration, and the display returns to the [Management] page.
When the L-Platform template is saved, an icon (
) will be displayed after the L-Platform template name.
Check the displayed contents of the L-Platform configuration, and click the [Next] button.
The [Agreement] page will be displayed.
Check the license agreement displayed. Select the [Agree the license] check box, and then, click the [Reconfigure] button.
Point
When the application process is enabled, clicking of the [Reconfigure] button on the [Agreement] page displays the [Forward screen] window. Refer to "5.5 Select Forward Destination of Application Process" for details.
The [Complete] page will be displayed when an application for modification of an L-Platform is accepted.
When the application process is disabled
The following message will be displayed:
"The request to reconfigure the L-Platform has been completed. The reconfiguration takes some time to complete."
When the application process is enabled
The following message will be displayed:
"The request to reconfigure the L-Platform has been completed. The L-Platform will be reconfigured after approval and/or judgement procedures."
Point
When an L-Platform is changed, an L-Platform reconfiguration completion notification email is sent to the subscriber.
If an L-Platform change fails, an L-Platform reconfiguration failure notification email is sent to the subscriber and the Infrastructure Administrator. In this case, check with the Infrastructure Administrator about the action required.
Refer to "A.2 Emails Sent when Reconfiguring an L-Platform" for information on the flow and content of email messages sent to the subscriber, tenant administrator, and infrastructure administrator when reconfiguring an L-Platform.
If the server virtualization software is RHEL-KVM or the subscribed L-Platform includes a Windows server other than Windows Server 2008 R2, after deployment the L-Platform will be available only after the infrastructure administrator configures the IP address, default gateway, and host name. Request the tenant administrator to configure the server after deployment.
If the server virtualization software is OVM for x86, the L-Platform will be available only after the infrastructure administrator configures the IP address, default gateway, and host name following deployment. Request the tenant administrator to configure the server after deployment.
If the server virtualization software is Citrix XenServer, then depending on the cloning image, the L-Platform will be available only after the infrastructure administrator configures the IP address, default gateway, and host name after deployment. Request the tenant administrator to configure the server after deployment. Check with the tenant administrator whether the cloning image requires configuration (IP address, etc.) after deployment.
When the server virtualization software is OVM for SPARC, IP addresses are set only to the NICs that are connected to admin LAN when you deploy a server whose guest OS is Solaris 11. It is therefore recommended that you connect the NIC to the admin LAN.
If a deployed server is not connected to admin LAN, the tenant administrator needs to set IP addresses and default gateways to the server before use. You also need to set IP addresses on guest OS to the NICs that are connected to business LAN, by confirming deployed IP addresses on the [L-Platforms] tab.
When using Solaris Zones as server virtualization software, an IP address is only configured for the first NIC when deploying a server which uses Solaris 11 for the guest OS. Therefore, when using multiple NICs, use the [L-Platforms] tab to check the IP addresses allocated to the second and later NICs after completing deployment of the relevant server, and directly configure the settings on the guest OS.
If the server virtualization software is OVM for SPARC or Solaris zone, after your deployment the tenant administrator needs to configure deployed servers to enable direct root ssh login.
When specifying an administrator user name other than "root" when deploying a server using Solaris Zones as server virtualization software, it is not necessary to make a request to the infrastructure administrator as connections using ssh are possible in the initial state.
Note the following points if the server virtualization software is OVM for SPARC:
If an increase or decrease of the number of NICs is required after deployment, contact the tenant administrator.
With servers not managed by BladeLogic, it is not possible to change the number of CPUs, the size of the memory, and boot priority when you reconfigure after deployment. It is also not possible to delete servers and disks.
If the server virtualization software is RHEL-KVM, contact the infrastructure administrator for information on how to subscribe to servers other than Windows or Linux servers.
