I am planning to run a series about cloud design. Follow me for more 😍
Feedback & suggestions are very welcome. Please comment & share the wealth via RT 👍
When (1)Naming, (2)Filing and (3)Labeling are done right for your resources, we can assume that you have a well defined environment. The problem is to agree upon what "done right" is.
But for (1)naming, that’s up to you to decide about your strategy: cryptic IT naming convention can ruin all the benefits of a careful filling and labeling strategy ❌
At some point in his career, any ops people have named the servers after planets 🪐☄️, greek gods 🔱⚡️or superheroes 🦸♀️ 🦸♂️ names, sometimes a mix of all of the above.
And I am sure there is more than one system administrator that named all the servers after the Game of Thrones characters names. 🩸✍️
Explaining this post mortem to a pointy haired boss have the potential for a great Dilbert strip 😂
Still nobody have a clue at first sight about what these resources are and what they do, unless you already practice these names for some time.
🎁 Bonus: you wasted 10 man-days to produce the initial naming convention proposal, endured a fair number of meetings and email chains to have everybody agreed upon it.
🙅🏻♂️Enough. You probably don't need a naming convention that takes 4 hours to read, 4 weeks to master and generates names that can be used as an RSA private key.
- restriction on allowed character type and number, prevented plain words usage
Your resource name is not your metadata store anymore, you have tags for that.
- «I do some magic filtering on the name & perform operations using `grep, awk, cut & sed`»
- «I need that precise codification to speed my troubleshooting process.»
- «I want to know everything about the resource just by reading its name»
It is ok to have *some* descriptive elements in the name of a resource, but there is no need to over-codify everything in it: you will actually loose in clarity.
1️⃣ Define clearly the lingo related to your technology stack, the acronyms you use for objects, features and concepts,
2️⃣ Simply name the resource after its purpose, in plain word,
4️⃣ When possible, enforce the resource context with a filing structure that represent your organization’s structure.
5️⃣ Put any other information in Tags!