There are various standards for hostnames from complex to simple. This standard tries to achieve the following,
- Easy to use.
- Have consideration of "tying" machines together (for example, web to apps).
- Provide meaningful grouping when sorted in a list.
Samples
We start by providing some example models and see how the naming works as the system evolves.
Web Application Model
Here is a fictional registration system that would be Internet facing. As such, it will require a web server and an application server. The budget is small so the database will also reside with the application.
Phase 1
The system starts small and begins with a registration system.
Hostname | Description | Naming Convention |
---|---|---|
S1 | Host system for Registration System. | Use a 2-3 letter convention to describe the host's main function. As the purpose of the host can easily change we use a generic name, S1 for system 1. |
RGH1V00WEB | Runs Apache Web Server. | RG = Registration |
RGH1V00APP | Runs Tomcat Application Server and HypSQL Database Server. | This has both an application and database. Because the database is portable and more easier to move, we make the judgment call to name the system APP after the more primary, less likely to move, long term function of the server. The convention follows but notice the V00. 00 = First virtual server for the specified function and it visually and via sorting will correspond to the Web Server. |
At this point the hostnames are not too bad. Their real value comes when the system needs to grow.
Phase 2
The system grows and requires a second application server to manage the load. As in many cases, the application is the bottle neck. Here is how it will look in a sorted list,
Hostname | Description | Naming Convention |
---|---|---|
S1 | Host system for Registration System. | Existing. |
RGH1V00WEB | Runs Apache Web Server. | Existing |
RGH1V00APP | Runs Tomcat Application Server and HypSQL Database Server. | Existing |
RGH1V01APP | Runs Tomcat Application Server. | New, noticed the V01. V0 where zero indicates that it belong with the RGH1V00WEB server. The RG and 01 indicates that this the second server under the Registration umbrella. |
The convention naturally sorts well. Now let's add something new to the mix.
Phase 3
There is need for a new system for migrating users to tokens which we'll call MG for migration. Notice that we use a generic name rather than TM as the system could evolved to do other types of migrations. The system is low budget and considered temporary. As such, the customer wants to reuse the web server.
Hostname | Description | Naming Convention |
---|---|---|
S1 | Host system for Registration System. | Existing. |
RGH1V00WEB | Runs Apache Web Server. | Existing |
RGH1V00APP | Runs Tomcat Application Server and HypSQL Database Server. | Existing |
RGH1V01APP | Runs Tomcat Application Server. | Existing |
MGH1V00APP | Runs Tomcat Application Server and HypSQL Database Server. | Again the V0 clearly shows that it is connected to RGH1V00WEB and the MG indicates the systems primary function is for migrations. |
T
..