OpenStack Object Storage

  • Service Host

    The service host provider name must be provided in the following format:

    Syntax: <IP Address>:<Port_Number>/auth/v1.0

    Example: 172.12.34.567:8080/auth/v1.0

    However, if you use Keystone Identity Server, the server host provider name must be provided in the following format:

    Syntax: <IP Address>:<Port_Number>/v2.0

    Example: 172.12.34.567:5000/v2.0

    Based on the region, the service host provider name must be provided in the following format:

    Syntax: /auth/v1.0@<regionName>

    Example: 172.12.34.567:8080/auth/v1.0@secondaryRegion

    However, if you use Keystone Identity Server, then based on the region, the server host provider name must be provided in the following format:

    Syntax: <IP Address>:<Port_Number>/v2.0@<regionName>

    Example: 172.12.34.567:5000/v2.0@secondaryRegion

    If SSL is not supported, then use the following format:

    Syntax: http://<hostname/IP>:<Port_Number>

    For Fujitsu Enterprise Cloud Service K5 the host URL is identity server URL.

    Example: https://identity.uk-1.cloud.global.fujitsu.com/v3

    Note

    For V3, version 3.4 (and above) are supported.

  • Username

    The user name must be provided in this format:

    v1 <user name>

    v2 <tenant name>:<user name>

    v3 <domain name>:<project name>:<user name>

    For Fujitsu Enterprise Cloud Service K5 the user name must be provided in the following format:

    <Contractname>:<projectname>:<username>

  • API Key

  • Verify API Key

  • Container

  • Use Internal URLs

  • Region

Best Practices

SwiftStack Object Storage - Performance

The performance of SwiftStack Object Storage reads is better when multiple mount paths are created instead of one single mount path.

Therefore, depending on the estimated Front-End Terabyte (FET) capacity in your environment, create a mount path for every 25 terabyte (TB) of data. For example if the estimation is 100 TB, then create 4 mount paths.

For SwiftStack Object Storage, each mount path should use a different container.

In addition, make sure that the Spill and Fill Mount Paths option is enabled in the Library Properties. This setting will help to distribute the objects across different partitions in the bucket, making the retrieval of the objects faster. For more information on this option, see Parameters for Mount Path Usage.

Loading...