Last updated on: 2021-05-24
Authored by: Rackspace Support
Support is available by email at firstname.lastname@example.org Monday through Friday, 9 AM to 5 PM CST. Tech support is happy to answer any questions you have about Cloud Files, except for code-related issues. If you have questions about design or coding, try our documentation.
A container is a storage compartment for your data and enables 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 you can’t nest containers. You can have up to 500,000 Containers in your account. However, 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. You can remove containers from Cloud Files only 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 they must sacrifice availability to do so. Or, a system can choose to handle network failures and have perfect availability, but they 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 provide massive uptime, but it also means that in certain scenarios, some data might not update throughout the entire system. For example, a container listing might not update after the system writes an object. 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 because the OpenStack Swift project considers this a required file. OpenStack Swift uses this as a global configuration file for the installation, and you can’t modify it for multiple tenants, such as our Public Cloud.
When you upload a file in the Cloud Control Panel, an
header supports cross-origin resource sharing (CORS) on the container.
different domains by default. Because the Cloud Files API and the Cloud Control
Panel reside on different domains, CORS must support uploads directly to a
container. When the upload succeeds, the system removes the CORS headers.
By allowing the browser to upload directly to the Cloud Files API, you can achieve maximum upload performance.
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 dividing them into separate accounts. Users must authenticate with a valid user name and API Access Key, but they can create or delete containers and objects within that account after authentication.
At this time, there is no way to publicly access the objects stored in Cloud Files unless that container publishes to CDN. Each request to Cloud Files must include a valid storage token in an HTTP header transmitted over an HTTPS connection.
Rackspace customers are not generally flash developers but still want to use a streaming offer. Some vendors dominate the market, and we plan to support each of them. Streaming delivery requires custom plugins to work properly over the Akamai® network. As Akamai adds support for more players, our customers gain access to them.
Real-Time Messaging Protocol (RTMP) is probably the most popular delivery format today, but the market is 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 the OpenStack Swift project, on which we based Cloud Files, requires this file.
OpenStack Swift uses the crossdomain.xml file as a global configuration file for installation. You cannot modify the file 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 make that container public, the files within that container have a designated time to live (TTL). The TTL is the time interval after which the CDN rereads the contents of the container. For more information on managing the TTL attribute, see Manage Time to Live (TTL) in a Cloud Files Container.
Akamai Technologies, Inc. is a publicly-traded company founded in 1998 (NASDAQ: AKAM). 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. After we flip the switch to have Akamai serve a customer’s content, Akamai supports new URLs and all other existing CDN-provider URLs.
This means that CDN customers who currently have Limelight URLs coded into their websites continue to serve content by using those URLs when they transition to Akamai, but we distribute them 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, we present them 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 should reference their new Akamai URL instead of their legacy URL.
No, as we add new features, we update our customers.
No, you should expect no downtime during the implementation of the Akamai platform.
No, all customers facing API calls 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 support of large files.
Although support for uploading content to Cloud Files through the Cloud Control Panel is for 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 it.
If you want to develop 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, we serve your large file as a single file, so the experience mimics the download or service of any other object retrieval.
Yes, you can edit your file segments 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 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 and so on
In this case, you 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 every cron job to 15 minutes. Ensure that your script is well tested and can complete its intended job within this time frame.
Use the Feedback tab to make any comments or ask questions. You can also start a conversation with us.
©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