Using Cloud Servers tags
The Cloud Control Panel lets you attach descriptive tags to your Cloud Servers and other assets. Tags help you organize your infrastructure as it grows. You can use them to quickly find specific assets using several different filtering mechanisms.
You can add new tags or edit existing tags for a server by selecting Tag Server from the Actions cog or Actions menu.
After typing a name in the Add or modify tags pop-ever, press the Return or Enter key to add the tags, and then click the Save Tags button to commit your changes.
Check the boxes next to tags in the filter on the left side of the server’s list to find those instances.
A couple of simple tags will help you identify a server’s purpose at a glance. You can also easily filter a huge lists of servers with several tags to distinguish one server type from another. Here are a few ideas for creating tags that can help you organize your cloud infrastructure.
A server environment is a collection of instances that are meant to operate under similar conditions.
A classic example of a set of server environments is the distinction between development, staging, and production environments. Servers in a development environment are used when testing code that is still in flux; the staging environment is a stable testing ground for code deemed to be complete; and the production environment is where the code goes when it’s passed testing and is ready to be used with real data or viewed by customers.
If you have specialized server instances it can be convenient to quickly filter them by function, like web server, proxy, or database.
In a more complex environment you might have primary and backup systems or master and slave database or DNS servers. Having servers labeled according to their role in the environment can help when planning maintenance.
Tags can let you quickly see which servers are running Linux or Windows, or what Linux distributions are being used on each server (like Ubuntu or CentOS).
These are some basic ideas for organizing servers with tags. But since tags are completely flexible, this is definitely not a comprehensive list. For example, you could use tags to divvy up responsibilities among a team, to label servers that only have internal network interfaces active, and to keep track of any other qualities that distinguish your servers from one another.
© 2014 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License
See license specifics and DISCLAIMER