Selfhosted

58318 readers

444 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Haven't been as busy as you guys, but still wanted to show off (lemmy.world)

submitted 5 days ago by EpicFailGuy@lemmy.world to c/selfhosted@lemmy.world

42 comments fedilink hide all child comments

What's everyone's server naming scheme?

you are viewing a single comment's thread
view the rest of the comments

[–] atzanteol@sh.itjust.works 2 points 4 days ago (1 children)

In a business with tens of thousands of servers, it makes sense to have long complicated names.

I'm actually not convinced of this approach. It's one of those things that makes perfect logical sense when you say it - but in practice "DBDWWHORCLHHIP01" is just as meaningless as "Hercules". And it's a lot more difficult to say, remember and differentiate from "DBDWWHORCLHHID01". You may as well just use UUIDs at that point.

Humans are really good at associating names with things. It's why people have names. We don't call people "AMCAM601W" for a reason. Even in conversations you don't rattle off the long initialism names of systems - you say "The database".

[–] Tetsuo@jlai.lu 1 points 4 days ago* (last edited 4 days ago) (1 children)

I think you choose a poor example.

When I say long name I wasn't implying meaningless ones.

Most business with a lot of machines uses long names where everything as a logical meaning.

[Site][service][Rack][User selected 8 chars name]

I mean you dont have to use such obtuse names. But if you have a lot of servers you have to have a long name or you will risk exhausting the available names.

I'm just saying long names dont have to be obtuse or confusing. You can use user selected names as a suffix to a more functional initial prefix. So that people who work this area of the infrastructure can have clear names but at the same time some other sys admin that never worked on it can still know where and who is responsible of the server.

My initial point is just that the namespace and length of hostnames mostly depends on what you want to do. For a homelab you dont need wide namespace. But for a large business using short names wouldn't be practical either.

[–] atzanteol@sh.itjust.works 1 points 4 days ago* (last edited 4 days ago) (1 children)

I think you choose a poor example.

When I say long name I wasn’t implying meaningless ones.

Sooo, that example wasn't exactly "contrived" - it's based on a standard I see where I work.

DB - it's a database!
DW - and a data warehouse at that!
ORCL - It's an Oracle database!
HHI - Application or team using / managing this database
P - Production (T for Test - love the 1 char difference between names!)
01 - There may be more than one.

This is more what I'm arguing against - embedding meta-data about the thing into its name. Especially when all of that information is available in AWS metadata.

[Site][service][Rack] makes sense for on-premise stuff - no argument there.

I’m just saying long names dont have to be obtuse or confusing.

Agree

[–] EpicFailGuy@lemmy.world 1 points 2 days ago

Not to butt in into your conversation, just wanted to drop that me and my colleagues use what we call the "clone cars" method to combat our company's naming scheme

So for example we dubbed CAPROD01 "Cappy" NASPROD01 became "Nasir" LTPDEV02 became "Luigi" (because he's always number 2)

Of course in written communication we use the full name (which is much less of an inconvenience) and we always double check in conversation or spell out full names before doing anything critical