In the Cloud Manager console, click , then click .
Click .
Fill in the following information:
Name: Provide a name for the zone. This name is displayed in Novell Cloud Manager to both administrators and users.
Description: If desired, add details to further identify the zone. The description is displayed in Novell Cloud Manager to administrators only.
Enabled: Deselect this option to disable the zone. The primary purpose for disabling a zone is to perform maintenance tasks on the PlateSpin Orchestrate Server without receiving error messages and exceptions in Novell Cloud Manager because the server is down.While the zone is disabled, the following occurs:
Any objects (hosts, VM templates, and so forth) provided by the zone’s PlateSpin Orchestrate Server are no longer displayed in Cloud Manager. However, Cloud Manager objects (host groups, service levels, workload templates, and so forth) are still displayed. A user receives a “Zone Disabled” error when adding, editing, or deleting any Cloud Manager object that includes a PlateSpin Orchestrate Server object.
Any workloads deployed in the zone continue in their current state (unless an issue with the zone causes them to be stopped). The workload’s state displays as “Unknown” and the owner cannot cycle the workload.
Server Address: Specify the DNS name or IP address of the PlateSpin Orchestrate Server.
Server Port: Specify the port used by the PlateSpin Orchestrate Server Web Service.
Username: Specify the Administrator username that enables login to the PlateSpin Orchestrate Server.
Password: Specify and confirm the password for the username you supplied.
Secure Connection: Select this option if the PlateSpin Orchestrate Server Web Service uses a secure connection.
IMPORTANT:After you define a PlateSpin Orchestrate Server as a zone, you are not allowed to modify the server address, server port, or connection type (secure or unsecure) for the zone definition. This means that if you change the address or port number of the Orchestrate Server, you must delete the zone, which requires removal of all business services, workload templates, service levels, and so forth associated with the zone, and then define the zone again with the new server address and port. For this reason, we strongly suggest that you not change the Orchestrate Server address and port after defining it as a zone.
Click to add the zone to the list