Startup Priority Level Settings; Action To Take When An Error Has Occurred - Fujitsu ServerView Resource Orchestrator Cloud Edition V3.1.1 Operation Manual

is completed.
When a deployment finishes, the IP address and host name of the guest OS are the same values as the server from which the cloning image
has been collected. Therefore, if two or more users subscribe servers simultaneously, multiple servers with same settings might be deployed
on the same network. To prevent problems caused by this situation, collect a cloning image from a server that has been configured as
follows:
-
Do not set the IP address to a fixed value.
-
Disable Windows file sharing and other services that cause problems when the host name conflicts with other servers.
After deploying a server with this cloning image, the infrastructure administrator looks up the IP address and host name in the L-Platform
tab, and also looks up the default gateway in the Resource tab, and then connects with the deployed server by using the console connection
function and sets these values manually.
In addition, the administrator includes a description like "The IP address needs to be configured by the administrator after deployment"
in the description field of the L-Platform template, and after the configuration is completed, notifies users that the server has become
accessible.
For a deployment with a cloning image that has not been configured as described earlier, the infrastructure administrator creates an L-
Server by using the Resource tab after receiving a request from a user, and imports the L-Server to the L-Platform management function
by following the description of
Linux OS with SELinux enabled
The administrator must disable SELinux when creating an image, and should include a description like "SELinux needs to be enabled
after the deployment has been completed" in the description field of the L-Platform template.
Because Linux OS is deployed with SELinux disabled, ensure that there are procedures in place to advise the user to enable SELinux after
deployment.

7.2.5 Startup Priority Level Settings

Any server with a startup priority level set to 0 will not startup or shutdown when performing bundled power supply operations.
An information message will be output to vsys_trace_log for any server that did not startup or shutdown.
If any server that either did not startup or shutdown actually needs to be started up or shut down, refer to the information message and use
the StartLServer or StopLServer command to startup or shutdown individually.
Refer to "2.3.5 StartLServer (Starts a Server)" and "2.3.6 StopLServer (Stops a Server)" in the "Reference Guide (API)" for details on this
command.

7.2.6 Action to Take when an Error has Occurred

When an error has occurred during a cancellation application by a tenant user, the cancellation application may become impossible.
In that case, confirm the L-Platform ID, and use the Disable L-Platform Application command to make the cancellation application
possible again for the user.
For information on the Disable L-Platform Application command, refer to "10.10 recoverService (Disable L-Platform Application)" in
the "Reference Guide (Command/XML) CE".
When a Problem Occurs during L-Platform Operation
The flow of when a problem occurs, after the following operations for an L-Platform are implemented by a tenant user, is as below.
-
Creation, modification, or deletion of an L-Platform
"7.2.3.2 Importing L-Servers", and then notifies users that the server has become accessible.
- 17 -