Last updated on: 2018-10-24
Authored by: Rackspace Support
Support is available by email at email@example.com Monday through Friday, 9AM to 5PM CST. Tech support will be happy to answer any questions you have about Cloud Files, except for code related issues. If you do have questions about design or coding please try our forums or documentation.
A container is a “storage compartment” for your data and provides a way for you to organize that data. You can think of a Container as analogous to a folder in Windows® or a directory in UNIX®. The primary difference between a container and these other “file system” constructs is that containers cannot be nested. You can have up to 500,000 Containers in your account, but they only exist at the “top level” of your account and containers cannot reside within other containers.
Containers scale to about one million objects before performance degrades. Containers can only be removed from Cloud Files if they do NOT contain any storage Objects. In other words, make sure the container is empty before attempting to delete it.
The naming requirements for Cloud Files objects and containers (such as illegal characters and name length limits) include:
A key characteristic of Cloud Files is eventual consistency. In computing, the CAP (Consistency, Availability, and Partition Tolerance) theorem states that distributed systems cannot achieve consistency, availability, and network failure tolerance; they can achieve only two. For example, a system can be consistent (that is, all reads get the most current data) and handle network failures, but must sacrifice availability to do so. Or, a system can choose to handle network failures and have perfect availability, but must sacrifice consistency to do so. Distributed systems must always handle network failures, so they must choose to sacrifice either availability or consistency.
Storage systems become distributed as they grow. OpenStack Swift (the basis for the Rackspace Cloud Files service) sacrifices consistency for availability and network failure tolerance. This choice enables the system to scale to enormous levels and to provide massive uptime, but it also means that in certain scenarios some data might not be updated throughout the entire system. For example, a container listing might not be updated immediately after an object is written. OpenStack Swift queues the container listing update and allows the object write to succeed. This sort of consistency model is called eventual consistency.
No. The Cloud Files CDN does not support exposing a custom crossdomain.xml file, as this is a required file by the OpenStack Swift project. OpenStack Swift uses this as a global configuration file for the installation, and can not be modified for multiple tenants, such as our Public Cloud.
When you upload a file in the Cloud Control Panel, an
header is set on the container to support cross-origin resource sharing
(CORS). Browsers prevent AJAX requests between different domains by
default. Because the Cloud Files API and the Cloud Control Panel reside on
different domains, CORS must be enabled to support uploads directly to a
container. When the upload succeeds, the CORS headers are removed.
By allowing the browser to upload directly to the Cloud Files API, maximum upload performance can be achieved.
Read more about CORS at https://en.wikipedia.org/wiki/Cross-origin_resource_sharing .
There are no permissions or access controls around containers or objects other than being split into separate accounts. Users must authenticate with a valid user name and API Access Key, but once authenticated, they can create or delete containers and objects only within that account.
At this time, there is no way to publicly access the objects stored in Cloud Files unless that container is published to CDN. Each request to Cloud Files must include a valid “storage token” in an HTTP header transmitted over a HTTPS connection.
Many Rackspace customers are not flash developers, but still want to use a streaming offer. There are a few players that are dominating the market, and we will plan to support each of them. Custom plugins are required in order for Streaming delivery to work properly over the Akamai network. As Akamai adds support for more players, our customers will have access to them.
RTMP is probably the most popular delivery format today, but the market is quickly moving towards HTTP delivery for Streaming content. Following are just a few reasons the market is moving towards HTTP:
Yes, this is available to both US and UK Cloud customers.
Cloud Files CDN does not support exposing a custom crossdomain.xml file because this file is required by the OpenStack Swift project, on which Cloud Files is based.
OpenStack Swift uses the crossdomain.xml file as a global configuration file for installation. The file cannot be modified for multiple tenants, such as our Rackspace Public Cloud.
For more information, see Cross-domain Policy File.
If your site requires a custom crossdomain.xml file, we suggest you take a look at Rackspace CDN. Rackspace CDN allows you to customize your configuration and define your own origin web server.
When you create a container in Cloud Files and you make that container public, the files within that container have a designated TTL. The TTL is the time interval after which the CDN will reread the contents of the container. For more information on how to mange the TTL attribute, see Manage Time to Live (TTL) in a Cloud Files Container.
Akamai Technologies, Inc. is publicly traded: (NASDAQ: AKAM) company founded in 1998. Akamai has a pervasive, highly-distributed cloud optimization platform with over 73,000 servers in 70 countries within nearly 1,000 networks.
Rackspace expects no customer impact during your transition to Akamai. Once we flip the switch to have a customer’s content served by Akamai, Akamai will begin supporting both new URLs and all other existing CDN provider URLs.
This means that CDN customers who currently have Limelight URLs coded into their websites will continue to serve content using those URLs when they are transitioned to Akamai, but they will be distributed over the Akamai network. At this time, we do not have any plans to discontinue the legacy URLs.
If a customer requests their URL (either in the Cloud Control Panel or through API) for an object, they will be presented with a new Akamai URL. This does not mean that old URLs are invalid. However, as Rackspace releases new features like CNAME and SSL, customers will need to reference their new Akamai URL instead of their legacy URL.
No, as we add new features, we will educate our customers.
No downtime is expected during the implementation of the Akamai platform.
No, all customers facing API calls will remain the same.
Yes, the Rackspace Cloud now supports the transfer and storage of larger files. Following is a list of frequently asked questions about our large file support.
Although support for uploading content to Cloud Files through the Cloud Control Panel is limited to files smaller than 5 GB, we can accommodate the transfer of files larger than 5 GB by allowing you to segment your files into multiple file segments.
Rackspace does not enforce any lower limits on the file size. File segments cannot be larger than 5 GB, and we recommend not storing file segments that are smaller than 100 MB.
At this time, you cannot serve files larger than 10 GB from the CDN.
We have created a tool called Swift to make this process easier. Swift segments your large file for you, creates a manifest file, and uploads the segments accordingly. After it uploads the segments, Swift manages the segments for you, deleting and updating them as needed. You can get information about the Swift Tool and download the Swift tool.
If you are interested in developing against the Rackspace Large File Support code to incorporate into your application, you should work directly with the Cloud Files API. For more information, see Use the API to manage large files.
After files are segmented and uploaded with a manifest file, your large file will be served as a single file, so the experience will mimic the download or service of any other object retrieval.
Yes, you can edit your file segments just like any other object within Cloud Files.
Include your manifest file in your upload. You can change your file name by editing this manifest file as well. We recommend using prefixing in your file segments to easily map your manifest file to the portions of your large file. For example, you could name your segments as follows:
Myfavoritemovie-01 Myfavoritemovie-02 Myfavoritemovie-03 ..etc..
In this case, you would point your manifest file to the prefix:
At this time, Rackspace has not implemented this functionality into the Rackspace Cloud Control Panel.
The Rackspace Cloud system restricts the maximum execution time of any one cron job to 15 minutes. Please make sure that your script is well tested and can complete its intended job within this time frame.
©2020 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License