MatthiasScholz / cos

Basic Cluster Orchestration Setup
GNU Lesser General Public License v3.0
34 stars 11 forks source link

Names of nomad and consul instances are unclear #1

Closed ThomasObenaus closed 6 years ago

ThomasObenaus commented 6 years ago

Current state

nomad-client (dc public-services): COS-public-services-shiner consul: COS-consul-shiner nomad-server: nomad-example-server

Problem

  1. The names can't be long, since they are used inside the official nomad-module as name-prefix, which introduces size limits for names (32 for target-groups, 64 for security-groups)
  2. To avoid collisions the name should contain a random part.

Proposal

  1. Keep random part at the end
  2. Restrict the data-center name (only in this names) to max of 10 items.
  3. Add abbrev. for node-type
    • nomad-client: NMC
    • nomad-server: NMS
    • consul: SDCFG (Service Discovery + Configuration)

Examples

COS-SDCFG-consul-shiner COS-NMC-public-ser-shiner COS-NMC-private-se-shiner COS-NMC-backoffice-shiner COS-NMC-content-se-shiner COS-NMS-leader-shiner

ThomasObenaus commented 6 years ago

Adjusted names with https://github.com/MatthiasScholz/cos/commit/027ab70ef44ccf368d0f83372a0b4f40f4fc0a0f.