This is a question familiar to those who use shared hosting. There is no limit, since you are in control of everything on your Cloud Server.
Cloud Servers: FAQs
- Getting Started -
Maybe. That mostly depends on your experience as a Systems Administrator for Linux and/or Windows Server. Our Linux Cloud Servers are full Linux distributions with root-level access. Our Windows Cloud Servers give you Administrator access, and are built with nothing but the default applications on install. Cloud Servers are geared towards customers who want to start from scratch and tune a system for their own purposes.
If, after wearing the Systems Administrator hat for a while, you feel that you are out of your league - don't despair! We also offer Cloud Servers with a Managed Operations. Read here for more information on Cloud Servers with Managed Operations.
We have two Service Levels: Managed Infrastructure and Managed Operations. At the Managed Infrastructure level, we support the Cloud Server hardware, datacenter environment, and Internet connectivity - but do not support the software installed on your server, including the operating system and its configuration. When you provision a Cloud Server, you will be given a server with unrestricted access. The Managed Infrastructure support team will not assist in the installation of software or troubleshooting any kind of issue related to the software installed. We have some articles in the Knowledge Center covering basic installation of common applications. We also have community forums where you can share tips and tricks with other customers.
If you would like to have a Managed Operations on your Cloud Servers, we offer that service. This operations level provides additional support on Cloud Servers, which includes monitoring, operating system and application infrastructure layer support, and technical guidance.
Anything you want to (within the law and our Acceptable Use Policy, of course)! The Rackspace Cloud Server solution is a fully unrestricted, root/Administrator level access, Linux or Windows environment. Any application or service that you can run from a traditional, physical, dedicated-unmanaged operations can be run from your Cloud Server.
Of course you can! Simply press the Rebuild button in the Control Panel and you will be able to select a new distribution. Be sure you have a backup of your data because this process will destroy any data that is on the server. The rebuild process does allow you to save you IP address.
You can reboot your server. You can restore from a backup. You can delete your server and start over. You can boot into an emergency rescue mode and attempt fix the problem. There are many options for recovering from mistakes, but the easiest is to keep regular backups and to make a fresh backup before attempting any major configuration changes or before installing new software.
Chances are that the repository for your operating system's package manager has an older approved version. This is fairly common, and you will need to remove that installation and then compile the newer version yourself. Refer to the software vendor for instructions.
It depends on your service level. For Managed Infrastructure Cloud accounts, you are responsible for installing and maintaining all software on your server. However, you can check out our help articles for tutorials and walk-throughs. Rackspace does provide support for specific software and server configurations on Cloud Servers with Managed Operations. For more information on supported systems and third party packages, see Cloud Servers wih Managed Operations - Spheres of Support.
All of our Cloud Servers can be configured as development stacks, database servers and web servers. Apache, Lighttpd and Mongrel, Visual Studio are all options.
You can use the programming language of your choice to interact with Cloud Servers. For help getting started with that, use any of the Software Development Kits (SDKs) documented at https://developer.rackspace.com/sdks/.
dns1.stabletransit.com and dns2.stabletransit.com
- What are security groups?
- Where are the docs?
- What are the benefits?
- What is being launched?
- What features are supported at launch?
- Are security groups on Cloud Networks supported?
- Will security groups be supported via the neutron client?
- Will this be integrated and available from within the Control Panel and Reach?
- Are security groups supported for OnMetal users?
- Is there a default security group that gets applied to my instances?
- Can I apply security groups to ports on an instance at boot time?
- What happens when a security group rule is added to the security group?
- Can traffic be blocked or denied based on a security group rule?
- Is there any traffic that is permitted / allowed by default by security groups?
- What kinds of traffic can be matched by the security group rules?
- Can I have a security group with no rules?
- Are security groups applied to instances?
- What are the limits for security groups and rules?
Security groups are a named collection of network access rules that provide Rackspace Public Cloud users to specify the types of traffic that are allowed to pass through PublicNet and ServiceNet ports on a Cloud Server instance. A security group is a container for security group rules. After you launch an instance, you may assign one or more security groups to ports on that instance. Security groups act as a stateful firewall for your Cloud Server instances.
Prior to this feature being available, customers had to manage traffic to/from their instances individually via iptables rules (as an example) on every instance (or perhaps use 3rd party tools such as CloudPassage). Managing firewall policies involves significant overhead. Security groups makes it possible to use a self-service API to define a common set of rules and apply them to the servers without needing to tweak iptables rules on each server. This simplifies security policy administration for customers across their deployments.
We are launching security groups as limited availability in all Datacenters, so customers may request the security groups feature and receive provisioned endpoints in their service catalog. Security groups are supported for Managed Infrastructure (non-RackConnect) customers at launch.
With the limited availability launch in early 2015, we support only inbound security groups on both PublicNet and ServiceNet interfaces. This means customers can filter incoming traffic to their PublicNet and ServiceNet ports. We will add outbound security group support later this year (2015).
Not at this time. We will add support later this year (2015).
Yes. Users can provision security groups via the neutron client.
Not yet. The product will be available from within the Control Panel 4 to 6 weeks after we deploy to all DCs. In the interim, customers can use either the neutron client or the API.
No. We currently support security groups only for virtual cloud servers.
No. There is no default security group that gets applied. Users must create a security group themselves and apply it to ports on an instance.
No. Security groups can be applied only after the instance is active.
Traffic matching a security group rule is allowed to go through.
No. Traffic that matches a rule is permitted, and any traffic that is not part of the ruleset for that security group is denied or blocked. Due to OpenStack API design requirements, there is no way to specify that traffic matching a rule should be denied. The security groups API is a whitelist. Thus, traffic that doesn't match any of the rules in the whitelist is automatically blacklisted.
DNS responses from Rackspace Provider DNS servers (UDP source port 53) are allowed by default even if a security group does not explicitly allow them. Also the TCP flags “ACK” and “RST” are permitted by default.
The following types of traffic can be matched (for both IPv4 and IPv6 addresses):
- TCP traffic
- UDP traffic
- ICMP traffic
- Traffic from a Source IP address
- Traffic from a CIDR
Yes. Such a Security Group will deny/ block all traffic.
No. Security groups are applied to a Neutron port on a network that is attached to an instance and not to an instance itself.
You can apply up to 5 security groups per port.
You can have up to 20 security group rules per security group
You can have up to 100 security Group rules (aggregate) per user during the limited availability release.
Rackspace cannot determine if a given customer is meeting their obligations under the laws applicable to them, and it remains our customers’ obligation to understand the laws applicable to their use of the services and select appropriate services to meet those obligations. We do understand the needs of many of our customers in the healthcare space to implement appropriate security measures to protect the sensitive information they work with.
To help customers in the healthcare industry meet their compliance requirements with regards to HIPAA, Rackspace offers a Business Associate Agreement in all of our dedicated hosting services segments, and it is included by default in our agreements with customers for those services.
For your security, the Virtual Hard Drive (VHD) on the hypervisor is deleted when you delete a server. Once it is deleted, data cannot be retrieved and customers do not have logical or direct access to the physical drive.
PVHVM refers to the virtualization mode used by the hypervisor to run the virtual machine. PVHVM images are virtual machine images that use the PVHVM virtualization mode. In general, PVHVM offers better performance than PV, especially for disk and network IO, but is not well supported in Linux operating systems with a kernel version earlier than 2.6.36. The availability of PV and PVHVM images in the Rackspace Cloud is determined by the effectiveness of each virtualization mode for that particular operating system.
Work-optimized servers (Compute, I/O, and Memory) require PVHVM images. If you try to create a work-optimized server by using a non-PVHVM image, the following error message is displayed:
Image cannot be built with provided flavor.
For more information about PVHVM, see Choosing a Virtualization Mode (PV versus PVHVM).
The information that you enter in the Server Name field helps you identify this server in the API and Cloud Control Panel.
Initially naming the server
The name that you enter in the Server Name field when you create a server is used as the server’s host name. You can read more about server host names on Wikipedia.
Renaming the server
When you rename a server, the name that is displayed in the API and Cloud Control Panel is updated. However, the host name on the computer is not updated.
Connecting to the server using the server name
To connect to the server from outside of the server’s local network, you need to configure an A record in Cloud DNS. To access Cloud DNS, in the top navigation bar of the Cloud Control Panel, select Networking > Cloud DNS.
For example, if you name your server MyWebServer1.MyExampleDomain.com, you must add an A record for MyWebServer1.MyExampleDomain.com to your DNS zone (MyExampleDomain.com) that points to the public IP address of the server.
Sure, it's right here.
At Rackspace, our goal is to make the Cloud easy for you to use. To meet that goal, we have created many different ways for you to get the support that you need to get the most out of the Cloud.
- Your first stop should be our Knowledge Center, which is the best source for articles, tutorials, and videos to help you get the precise answers that you need.
- The Knowledge Center contains the Getting Started with Cloud Servers Guide, which provides you with the most important information that you need to set up a server.
- Our Open Cloud Forum in the Rackspace Community is always open. Use the forum to get your questions answered by a Racker.
- Do you have a quick question that you can't find an answer for in the Knowledge Center? Open Chat and talk with our Fanatical Support® staff anytime, 24x7x365.
- Do you have a specialized Service Request or are you experiencing a problem with our service? Open a ticket. From the Rackspace Cloud Control Panel, select Support Tickets from the Account menu. Click Create Ticket to open a ticket directly with our support teams to report a problem or make a service request.
- Call us 24x7x365 at 877 934 0407 (toll-free) or +1 210 581 0407 (international).
As a Cloud Servers customer, you have access to create both on-demand images and scheduled images of your cloud server. All Cloud Server images will be stored in your Cloud Files account. This enables you to keep these images even after the Cloud Server they were created on is deleted. It also allows the flexibility to create an unlimited number of on-demand images of your Cloud Server. All Cloud Server images can be used to create new Cloud Servers or restore an existing Cloud Server. For details, see Creating an Image of Your Performance Flavor Server with the Control Panel.
For more information about creating a server from an image, see How to Create a Server from an Image.
You can create an image of any General Purpose Cloud Server, and you can use this image to restore a server or clone a new one. You can create an unlimited number of images on-demand, or you can schedule an automatic daily or weekly image.
If using a virtual cloud server, see Creating an image of your General Purpose Cloud Server with the control panel for more information on the image options associated with virtual cloud servers.
Yes it is! An article on how to install VNC and X-Windows is located here: VNC Install. Keep in mind that this will use up a large amount of bandwidth on your server.
Yes, the Rackspace Cloud Control Panel is a web-based management interface for restarting your cloud server, starting support discussions, viewing stats, and scheduling snapshots. However, we do not offer a control panel like Plesk or cPanel. You’re free to install such packages for your own cloud server.
You may be interested in installing the free monitoring agent on your server and using the Cloud Intelligence dashboard, which offers many of the same functions as a control panel.
Yes, via a Java web terminal accessible through the Details section of each webserver, in the Actions menu under the section labeled Manage, you will see a link to Connect Via Terminal.
Note: Console access is via a secure HTTP connection which is different connection from the traditional way to connect via SSH for Linux or RDP for Windows. Console can be a useful troubleshooting tool if your server is unresponsive or you have locked yourself out.
Yes. All Cloud Servers can perform both soft (reset button) and hard (power cycle) reboots. These are performed instantly and handled via the Cloud Server Control Panel.
Yes. You will be billed for the resources that are used on the host while your server is in the Active status. When your server is created, you are given a dedicated amount of RAM and hard drive space. As long as your server exists, no one else will be able to use those resources that have been allocated to you - this is why you are billed per hour even while powered off. If you would like to stop incurring charges for a given server, you must delete that server in the Control Panel.
If you want to stop paying for a server, but still need to retain the configurations from it, your best option is to create an image of the Cloud Server. Your system configurations on your system disk will be preserved in the image. The image will be saved in Cloud Files and accessible through the Saved Images tab in the Control Panel. There is a fee associated with Cloud Files storage but it is much less than the cost of an active server. You will also need to save the data from your data disk out to Cloud Block Storage or Rackspace Cloud Backup to have available on your next server. Then you will be free to delete the original server, safe in the knowledge that you can always provision a new server using the saved image of your old server and you saved data. After restoring your server from the saved image, the primary difference will be that your new server has a different IP address from the old one. Putting the new server into production may require you to update any associated DNS records to reflect the new IP address.
Please see the following article: Shutting Down and Restarting a Cloud Server
The Features section of our product page has information regarding the Linux distributions and Windows operating systems that we have available.
Yes. With General Purpose Cloud Servers, you can change the size of your data storage space in one of two ways:
- Increase Available Storage with Cloud Block Storage. For more information on Cloud Block Storage, see Create and Attach a Cloud Block Storage Volume.
- Migrate to a larger size server with more RAM, disk space, and vCPUs. For more information on resizing, see Changing the Size of Your First Generation Cloud Server.
The number of customers on a Cloud Server host machine depends on the size of the customers’ Cloud Servers, and the type of operating system.
Note: General Purpose Cloud Servers have specific virtual CPU allocations, as detailed on the Cloud Servers pricing page. The following information on CPU scheduling applies only to next-generation standard (i.e., not General Purpose) Cloud Servers.
For Windows images, each Cloud Server is assigned a number of virtual cores based on the size of the Cloud Server. The Standard 1 GB Cloud Server receives 1 virtual core, the standard 2 GB and 4 GB Cloud Servers receive 2 virtual cores, the standard 8 GB and 15.5 GB Cloud Servers receive 4 virtual cores, and the standard 30GB servers receive 8 virtual cores. Each of these cores is given equal weight when allocating CPU cycles.
For Linux distributions, each Standard Cloud Server is assigned four virtual cores and the CPU cycles allocated to these cores are weighted based on the size of the Cloud Server.
All standard Cloud Servers receive a guaranteed minimum amount of CPU cycles with the ability to burst when excess cycles are available.
The amount of time a resize takes varies by the size of the server and the time of day you are performing the resize. If you have a brand-new server with no additional data or software installed, then you might be looking at 10 minutes. However, if you have data installed on your server and have been installing software then it can take up to 30 minutes or more. Peak times for resize activity tend to be at the start and end of the business day. Expect a short period of downtime while your server is being resized.
Note also that resizing a server down can take longer than resizing up because the system needs to consolidate and copy data to a smaller disk container rather than expand the existing container. Cleaning up unneeded files (like old logs and session files) can improve the speed of a resize operation.
There are different processes of resizes, as follows:
- Online Resizes: Allow for the original sized Cloud Server to be powered on during the "Prep-Resize" step, and only powers down during the second step of the resize process.
This includes: First Generation Server resize up and resize down, and Standard resize up.
- Offline Resizes: Power down as the first "Prep-Resize" step.
This includes: Standard resize down.
NOTE: Resizing is not available for workload-optimized Cloud Servers. For information on your available options, see Changing the size of your workload-optimized Cloud Server.
While the native storage allocation for a Cloud Server is based on the Cloud Server flavor that you select, you can also add extra storage at any time with our Cloud Block Storage service.
Yes. Our Control Panel has a DNS menu for maintaining domain records for your Cloud Servers. Read this article for detailed information on using the Rackspace Cloud DNS Control Panel.
You can setup reverse DNS from your control panel. This article will show you how:DNS - Creating a Reverse DNS Record.
The amount of network throughput varies based on the Cloud Server flavor. For more details, see here.
Yes. Each server comes with an internal IP address that is used to communicate between servers. The traffic that flows over this interface (eth1) on your server is unmetered and is not billed. This network is also referred to as ServiceNet. ServiceNet is an internal only, multi-tenant network connection within each Rackspace datacenter. ServiceNet IPs are not accessible from the public Internet and are local per datacenter.
Yes. For more informaton on the IP request process, see Requesting Additional IPv4 Addresses for First and Next Generation Cloud Servers.
There are several noteworthy differences between Standard and General Purpose Cloud Servers:
- General Purpose Cloud Servers use faster solid state drives (SSD) compared to the standard spinning disk allocation for Standard Cloud Servers.
- Up to 120 GB of RAM is available on General Purpose servers, whereas Standard Servers provide up to 30 GB of RAM.
- You can have up to 32 vCPUs running on General Purpose Cloud Servers, comapred to the maximum of 8 on the Standard Cloud Servers.
- Maximum network bandwidth on Standard Cloud Servers is 300 Mbps public network and 600 Mbps private network. Maximum network bandwidth on General Purpose Cloud Servers is 10,000 Mbps to divide between public and private networks as you choose..
For more information about General Purpose Cloud Servers, see What is new with General Purpose Cloud Servers.
Billing and Account
Yes. We offer different types of discounts based on usage. Please see the Cloud Servers discounts page for details.
Traffic that matches a rule is permitted. Any traffic that is not part of the ruleset for that Security Group is denied / blocked. There is no way to specify that traffic matching a rule should be denied. This is how the OpenStack Security Groups API was designed. Hence the Security Groups API is a white-list. Traffic that doesn't match any of the rules in the white-list is automatically black-listed.
Security Grouos is in Limited Availability in all Data Centers. Please contact Rackspace support to enable this feature.
Prior to this feature being available, customers had to manage traffic to/from their instances individually via (for example) ipTables rules on every instance (or perhaps use 3rd party tools). Managing firewall policies involves in a distributed fashion significant overhead to keep track of and manage. Security Groups makes it possible to use self-service API to define a common set of rules and apply them to the Neutron ports (Public/ServiceNet) on Cloud Servers without needing to tweak iptables rules on each server, thereby simplifying administration of security policies.
Security Groups concepts and introduction : http://docs.rackspace.com/networks/api/v2/cn-devguide/content/api_ext_security_neutron.html
Security groups are a named collection of network access rules that provide Rackspace Public Cloud users the ability to specify the types of traffic that are allowed to pass through, to and from ports (Public/ServiceNet) on a Cloud server instance. A security group is a container for security group rules. After you launch an instance, you can assign one or more security groups to ports on that instance. Security Groups act as a stateful firewall for your cloud server instances.
The Rackspace Cloud environment has not been formally assessed for for compliance with the Payment Card Industry (PCI) Data Security Standard (DSS). For information about PCI-DSS, see Cloud Security Solutions. For information about PCI-DSS when using Rackspace Dedicated Hosting services, see PCI-Compliant Hosting for E-commerce Websites.
Definitely and we encourage it! Each Linux server is capable of running the Linux-standard firewall called iptables- some even have it pre-configured! Other firewall systems have been tested on Cloud Servers as well. To see introductory steps for some of the common options, be sure to check out these articles:
There is an aggregate limit of 100 security Group rules per user during Limited Availability. Please contact Rackspace support if you need this limit raised.
There is a limit of 20 security Group rules per Security Group. Please contact Rackspace support if you need this limit raised.
Up to 5 security Groups are allowed per port. Please contact Rackspace support if you need this limit raised.
Security Groups are applied to Neutron ports (PublicNet and ServiceNet) on Cloud Server instances.
Yes. Such a Security Group will deny/ block all traffic.
TCP, UDP, ICMP traffic can be matched in addition to traffic from a Source IP address or CIDR. Both IPv4 and IPv6 traffic can be matched.
DNS responses from Rackspace Provider DNS servers (UDP source port 53 ) are allowed by default even if they are not explicitly allowed by a Security Group.
Also TCP flags ACK and RST are permitted by default.
Traffic matching a Security Group rule is allowed to go through.
No. Security Groups can only be applied after the instance is active.
No, there is no default security Group that gets applied. Users have to create a Security Group themselves and apply them to ports on an instance.
No, Security Groups are currently only supported for Virtual Cloud servers.
The product will be available via Control panel very soon. In the interim, customers can use either the Neutron client or the API.
Yes. Users can provision security groups via Neutron client.
No. Rackspace will add Security Group support for Cloud Networks in the near future.
No. Rackspace will add Outbound security Group support in the near future.
Inbound Security Groups on PublicNet and ServiceNet interfaces are supported. This means customers can filter incoming traffic to their PublicNet and ServiceNet ports.
Security Groups will only be supported for Managed Infrastructure, non-RackConnect customers at launch.