Odd Workflow Regarding Configuration of Eucalyptus Object Storage Gateway/Object Storage Provider

Follow

Eucalyptus Versions: 4.0

Odd Workflow Regarding Configuration of Eucalyptus Object Storage Gateway/Object Storage Provider

In Eucalyptus 4.0, registration changed with regards to the user facing service for the Eucalyptus S3-compatible Application Programming Interface (API).  Due to this change, the configuration path is now similar to the Eucalyptus Storage Controller, where a backend client configuration needs to be done in the cloud properties.  

However, what this means is that before the Eucalyptus Elastic Load Balancer (ELB) and/or the Eucalyptus Imaging Service (IS - new in Eucalyptus 4.0.0) can be registered and configured, the Eucalyptus Object Storage Gateway (OSG) and Eucalyptus Object Storage Provider (OSP) must be configured.  To configure the Eucalyptus OSG and OSP, and register/configure the Eucalyptus ELB and IS, the cloud administrator credentials must be downloaded and sourced two separate times (a bug [1] has been raised against this behavior in order to be resolved in future releases).  This must be done to make sure the S3_URL is set correctly for the Eucalyptus ELB and IS services, and for image management in general.

The registration/configuration flow is as follows:

  • Register the Eucalyptus OSG
euca-register-object-storage-gateway --partition objectstorage --host 10.104.1.194 OSG1
Registered the first Object Storage Gateway. You must choose a object storage back end client with ``euca-modify-property -p objectstorage.providerclient=$PROVIDER (e.g. walrus or s3)
  • If Eucalyptus Walrus will be used, register Walrus [2].  If another S3-compatible REST API service will be used, please make sure to have the endpoint, access key ID, and secret access key information available.  For more information, please refer to the knowledge base article that discusses the Eucalyptus S3-Compatible API Service in 4.0 [3].
  • Download and source the cloud administrator credentials on the Eucalyptus Database (DB) component (this was known as the Cloud Controller - CLC - in previous versions of Eucalyptus)
euca-get-credentials -a eucalyptus -u admin admin.zip
unzip admin.zip
source eucarc
  • Set the cloud property objectstorage.provider client based upon which OSP will be used.  If Eucalyptus Walrus will be used, set this cloud property to 'walrus'.  If another S3-compatible REST API service will be used, set this cloud property to 's3', and set the cloud properties 'objectstorage.s3provider.s3endpoint', 'objectstorage.s3provider.s3accesskey', and 'objectstorage.s3provider.s3secretkey' are set to their respective values.
  • Re-download and re-source the cloud administrator credentials on the Eucalyptus DB component
rm -rf admin.zip
euca-get-credentials -a eucalyptus -u admin admin.zip
unzip admin.zip
source eucarc
  • The S3_URL is now set correctly so that any service that relies on the Eucalyptus OSG and OSP will work correctly.  This includes the following:
    • Eucalyptus ELB
    • Eucalyptus Imaging Service
    • Image Management (instance store-backed and EBS-backed images)

References

[1] Eucalyptus Jira Bug - EUCA-9107
[2] Eucalyptus 3.4 Installation Guide - Register Walrus
[3] Eucalyptus 4.0 S3-Compatible API Service Registration Change

Have more questions? Submit a request

Comments

Powered by Zendesk