Top
ServerView Resource Orchestrator Cloud Edition V3.3.0 Design Guide
FUJITSU Software

E.1.3 Storage Preparations

This section explains the preparations for setting up storage.

Supported Storage Configurations

The supported storage configurations are as follow:

Preparations for Storage Environments

Check the following:

Point

  • To use VVOL as a disk for virtual L-Servers, ETERNUS SF Storage Cruiser 16.2 (with Patch T010894WP-02, Patch T010908WP-02, and subsequent patches applied) or later and ETERNUS VASA Provider 2.0 or later must be installed.
    For details, refer to the manual of the relevant product.

  • When a virtual machine storage policy is not specified in an L-Server template, the default virtual machine storage policy configured in vSphere Web Client will be used for the virtual machine storage policies of virtual disks at the following timings:

    • Creation of L-Servers

    • Attaching of virtual disks to L-Servers

    The content of the definition of the default virtual machine storage policy can be modified using vSphere Web Client.

    [Windows Manager]

    When configuring a virtual machine storage policy other than the default for virtual disks, perform the following operations:

    • Specify the virtual machine storage policy in L-Server templates.

    • Register the IP addresses of VMware vCenter Server and VMware vSphere on the DNS server, and use the FQDN to enable access from the manager.

Information

By registering the agent of the VM management software and the VM host with Resource Orchestrator, datastores are detected as virtual storage resources in Resource Orchestrator.
Whether the datastore is VMFS, VVOL, or VSAN can be distinguished based on the format of the virtual storage resource name.


Name Format of Virtual Storage Resources for VMFS (Datastores)

The datastore name is used for the virtual storage resource name.
However, when characters other than the following are included in a datastore name, they are replaced with hyphens ("-").
When this product manages two or more vCenters, there may be multiple datastores with the same name. In that case, the form of virtual storage resource names is the datastore name + "_" + serial number (Example: "_1").

  • Numerals (0 to 9)

  • Alphabetical characters: upper case (A to Z), lower case (a to z)

  • Hyphens ("-") and underscores ("_")


Name Format of Virtual Storage Resources for VVOL (Datastores)

Virtual storage resource names are indicated in the following format:

  • "VVOLDS_"+"VVOL_datastore_name"

However, if characters other than those listed below are included in the VVOL datastore name, replace them with hyphens ("-").
When this product manages two or more vCenters, there may be multiple VVOL datastores with the same name. In that case, the form of virtual storage resource names is the VVOL datastore name + "_" + serial number (Example: "_1").

  • Numerals (0 to 9)

  • Alphabetical characters: upper case (A to Z), lower case (a to z)

  • Hyphens ("-") and underscores ("_")


Name Format of Virtual Storage Resources for VSAN (Datastores)

Virtual storage resource names are indicated in the following format:

  • "VSANDS_"+"VSAN_datastore_name"

However, if characters other than those listed below are included in the VSAN datastore name, replace them with hyphens ("-").
When this product manages two or more vCenters, there may be multiple VSA datastores with the same name. In that case, the form of virtual storage resource names is the VSAN datastore name + "_" + serial number (Example: "_1").

  • Numerals (0 to 9)

  • Alphabetical characters: upper case (A to Z), lower case (a to z)

  • Hyphens ("-") and underscores ("_")