These FAQ aim to answer questions regarding the end of life of Object Storage Unit (OSU).

December 22, 2020

What is the impact on my existing buckets?

When the End of Sale (EOS) is announced, the service continues to function as before, up until the End of Support and Maintenance (EOSM). A feature freeze takes effect for the product and no more feature is added.

When the End of Support and Maintenance (EOSM) is announced, the product is no longer eligible to a maintenance contract and technical support. Product features remain the same and the customer can still access the product. For example, it is still possible to create buckets and to upload objects to a bucket up until the End of Life (EOL).

When the End of Life (EOL) is announced, access to your bucket is removed. You no longer have access to your data.

Regarding the SEC1 Region (cloudgouv-eu-west-1): the data are not impacted. Only the osu.cloudgouv-eu-west-1.outscale.com endpoint will be removed as of the EOL of the OSU service, on December 22, 2021.


Will new accounts have access to OSU?

For existing customers who request a new account, the default answer is no. To synchronize the account to the OSU service, it is necessary to submit a request to the 3DS OUTSCALE support. However, starting from the date of End of Support and Maintenance (EOSM), no newly created account will be synchronized to the OSU service anymore.

For new customers, the product is no longer sold.

For more information, see our End-of-Life Policy where you will find step-by-step dates for example.


Where can I find information on the new OOS service?

You can check:


Are data automatically transferred between OSU and OOS by 3DS OUTSCALE?

No, the data will not be moved. This type of action is under the responsibility of the customer.

Caution: the naming rules for buckets and objects in OOS are stricter than in OSU.
Regarding the SEC1 Region (cloudgouv-eu-west-1): transferring the data is not necessary as they are already available on the oos endpoint. On the SEC1 Region only, the osu and oos endpoints point to the same infrastructure (that is the OOS service, which has been deployed on this Region in advance).


Is OOS more expensive or does it have a different level of service than OSU?

No, OOS offers the same level of SLA as the OSU service.

Historically, there were 2 differentiated offers: Enterprise OSU and Premium OSU. As for OOS, there is only one offer which has the same pricing as the more economical OSU offer, while having the level of service of the premium OSU offer.

As a reminder, object storage services are billed according to 2 accounting units:

  1. The quantity of stored data
  2. The outbound traffic from the object storage platform

The outbound traffic accounting unit for OOS is billed at the same price as OSU.


What are the cost impacts to move customer data to OOS?

From the End of Sales (EOS), OSU outbound traffic is no longer billed.

Therefore, moving customer data from OSU to OOS costs nothing. However, storing your data with OSU and OOS at the same time can lead to extra billing. We therefore encourage you to quickly delete your data from OSU after moving it to OOS.

Regarding the SEC1 Region (cloudgouv-eu-west-1): not applicable, since transferring data is not required for this Region.


What tools are compatible with OOS?

OOS is compatible with the S3 API. You can find a non-exhaustive list in the technical documentation.

As of February 22, 2021

What are the naming rules for OOS buckets?

The name of a bucket must:

  • Be unique for the whole Region
  • Contain between 3 and 63 characters
  • Start with an alphanumerical character
  • Contain only lowercase letters, numbers, and hyphens (-)

With the transfer of TINA features to OOS, it is important to make sure that the names of your OSU buckets comply with the naming rules applicable to OOS. We advise you to create buckets with the same names in OOS before February 22th.


What are the TINA calls impacted by the transfer of the TINA services to OOS?

The TINA calls that used OSU and that are impacted by the transfer of TINA services to OOS are the following:

Service

AWS-compliant API

OUTSCALE API

Recommendations
FCUCreateImageExportTaskCreateImageExportTaskMake sure that the name of the OSU bucket used complies with the naming rules applicable to OOS. We advise you to create a bucket in OOS before the TINA services transfer. Otherwise, a bucket will be created at the execution of the call provided a bucket of the same name does not already exist in OOS.
FCUDescribeImageExportTasksReadImageExportTasks-
FCU

CreateSnapshotExportTask

CreateSnapshotExportTaskMake sure that the name of the OSU bucket used complies with the naming rules applicable to OOS. We advise you to create a bucket in OOS before the TINA services transfer. Otherwise, a bucket will be created at the execution of the call provided a bucket of the same name does not already exist in OOS.
FCUDescribeSnapshotExportTaskReadSnapshotExportTasks-
LBUModifyLoadBalancerAttributesUpdateLoadBalancerCreate an OOS bucket with the same name as the OSU bucket used to store LBU logs.
LBUDescribeLoadBalancerAttributesReadLoadBalancers-


What impact should I expect on these calls?

The following calls now require OOS buckets to be specified:

  • CreateImageExportTask
  • CreateSnapshotExportTask
  • ModifyLoadBalancerAttributes / UpdateLoadBalancer

For instance, for the AccessLog request parameter, the following sub-parameters still include "Osu" in their names, but do require OOS buckets to be specified:

» OsuBucketNamestringfalseThe name of the OOS bucket for the access logs.
» OsuBucketPrefixstringfalseThe path to the folder of the access logs in your OOS bucket (by default, the root level of your bucket).

Generally speaking, in order to minimize user impact, we preferred to keep the same API call and parameter names despite the switch from OSU to OOS services.

Error messages may also contain "Osu" strings while referring to OOS buckets.


What will be the behavior of the CreateSnapshotExportTask call for which an OSU bucket was initially specified?

  • If a bucket of the same name does not already exist in OOS and the bucket to be created complies with OOS naming rules, it will be created and the data will be integrated into it.
  • If a bucket of the same name already exists in OOS, the data will be integrated into it.
  • If a bucket of the same name does not already exist in OOS and the bucket to be created does not comply with OOS naming rules, an error message indicating the creation of the bucket is impossible will be returned.

Regarding the SEC1 Region (cloudgouv-eu-west-1): no impact, because the buckets in question are already available on the oos endpoint.


What will be the behavior of the ModifyLoadBalancerAttributes and UpdateLoadBalancer calls for which an OSU bucket was initially specified?

  • If a bucket of the same name does not exist in OOS, an error message indicating the action is impossible will be returned.

Regarding the SEC1 Region (cloudgouv-eu-west-1): no impact, because the buckets in question are already available on the oos endpoint.


As of May 22, 2021

When is the end of support and maintenance phase of the OSU service effective?

The end of support and maintenance phase of the OSU service is effective May 22, 2021.


Will the OSU service still work after the end of support and maintenance date?

The OSU service will continue to work on all of our Regions until December 22, 2021, OSU's end-of-life date. However, updates and technical support will no longer be available for this service as of May 22, 2021. For more information on the end of life of our products, see our End-of-Life Policy.


What if I encounter a problem with the OSU service after the end of support and maintenance date?

As of May 22, 2021, technical support will no longer be available for the OSU service. Our Sales and Support teams remain at your disposal for any further information at sales@outscale.com and support@outscale.com.


AWS™ and Amazon Web Services™ are trademarks of Amazon Technologies, Inc or its affiliates in the United States and/or other countries.