Virtual machine nomenclature strategies

Virtual machine nomenclature strategies: "

When an IT department is trying to determine a server’s nomenclature, the situation can actually become quite contentious; when you roll virtualization into the fold, things can get even more complicated. I’ve settled on several design elements for naming systems, whether they are physical or virtual, servers or storage, printers or I/O devices.

The single guiding theme to a system nomenclature is to be self-documenting either at a basic level or in painful detail. The absolute basic information that I’d like from a system’s name is to be able to determine the following attributes:

Whether the system is virtual.

Whether the system is in development or production.

What application or operating system is running on the system.

Whether it is the first, second, or third (etc.) of a sequence.

These basic identifiers can create a nomenclature that works for physical and virtual systems. Figure A shows an example that does this for a few types.

Figure A

Click the image to enlarge.

The obvious missing component is location. As I have been around the block a few times, I’ve determined that I am better off not having the location within the name of a server. Virtual machines move around, and I’d prefer that the burden of renaming the virtual machine not be associated with the built-in flexibility of the platform. Windows renames fine enough, but applications can require a bit of manipulation to accommodate name changes. Besides, it is just irritating when the first virtual machine shows up in a location that doesn’t have the site nomenclature.

This framework is also cluster-friendly, hence the triple digit sequencing for instances in positions 8, 9, and 10. Basically, position 8 would indicate a cluster, while leaving positions 9 and 10 for plenty of space to identify each node. As an example using the framework in Figure A, a cluster of five VMware ESXi hosts in a cluster named ESXI101 would be named as follows:

PMPESXI101: Node one of the cluster (physical, production, ESXi)

PMPESXI102: Node two of the cluster

PMPESXI103: Node three of the cluster

PMPESXI104: Node four of the cluster

PMPESXI105: Node five of the cluster

This is just one of the ways that I have gone about this task, and I realize there are many ways to approach this topic. How do you name systems now that virtualization is a significant player in the data center? Share your comments in the discussion.

Comentários

Postagens mais visitadas deste blog

Improve Windows Security By Closing Open Ports

Improve Windows Security By Closing Open Ports : " A standard Windows operating system has a number of ports open after installation. Some of these ports are needed for the system to function properly while others might not. These ports can pose a security risk as every open port on a system might be an entry point for a malicious user. A port basically allows communication to or from the device. Characteristics are a port number, an IP address and a protocol type. This article will give you the tools at hand to identify and evaluate the open ports on your Windows system to make a decision in the end whether they can or should be closed or left open. Software programs and tools that we will use: CurrPorts : Available for 32-bit and 64-bit editions of Windows. It is a port monitor that displays all open ports on a computer system. We will use it to identify the ports and the programs that are using them. Windows Task Manager: Also used to identify the programs and link some p

Diagnosing a Blue Screen of Death Error in Windows

Diagnosing a Blue Screen of Death Error in Windows : For many years now the famous Blue Screen of Death (BSoD) has been the ultimate indication that something disastrous has happened to make your computer die, but how useful is the information in the BSoD and the respective crash dump file that Windows produces? The best article I ever found explaining the BSoD in depth is here on the Microsoft website, however it’s quite technical and doesn’t discuss how to actually troubleshoot a problem. The crash dump file is just technical details of what was being held in the computer’s memory at the time of the crash, and this will include details on every driver and service that was loaded, and every piece of software that was running. The most useful pieces of information are to be found on the BSoD itself and are highlighted on the screenshot below. These are the BSoD error name, the stop error code and the name of the driver or service that has failed (this last one might not always appea

Use BGInfo to Build a Database of System Information of Your Network Computers

Use BGInfo to Build a Database of System Information of Your Network Computers : " One of the more popular tools of the Sysinternals suite among system administrators is BGInfo which tacks real-time system information to your desktop wallpaper when you first login. For obvious reasons, having information such as system memory, available hard drive space and system up time (among others) right in front of you is very convenient when you are managing several systems. A little known feature about this handy utility is the ability to have system information automatically saved to a SQL database or some other data file. With a few minutes of setup work you can easily configure BGInfo to record system information of all your network computers in a centralized storage location. You can then use this data to monitor or report on these systems however you see fit. BGInfo Setup If you are familiar with BGInfo, you can skip this section. However, if you have never used this tool, it takes ju

SysAdmin

Pesquisar este blog