RfC: rename metropolis to "Monogon OS"

[leoluk]

The longer we wait, the more painful it becomes :P

Our buzzkill lawyers say we can't call the product "Metropolis", due to approximately a dozen companies owning trademarks in every relevant category. Meanwhile, Monogon + arbitrary generic description is guaranteed to be fine. Monogon OS it is!

[fionera]

Leo and I talked about this already and where thinking about just replacing metropolis with os in our directory tree. In docs we have to just rephrase them

[jscissr]

The name "metropolis" is used in various places in the code base, not just the directory name:

• metroctl is derived from metropolis
• Node IDs, e.g. metropolis-d62d11981c11b4592629b644f57f0ed9
• GCP metadata URL http://169.254.169.254/computeMetadata/v1/instance/attributes/metropolis-node-params
• Bundle file name metropolis-v0.1.zip
• Installer image FAT32 partition label METRO_INST (abbreviated because this is limited to max 11 characters)
• etcd InitialClusterToken METROPOLIS
• OS release ID metropolis-node and name Metropolis Node
• GPT partition labels METROPOLIS-SYSTEM-A, METROPOLIS-NODE-DATA
• PEM owner key type METROPOLIS INITIAL OWNER PRIVATE KEY
• RPC resolver URL metropolis://control
• /metropolis and /EFI/metropolis directories on the ESP
• Soon in the Kubernetes field manager name metropolis-labelmaker

Many of these are stored on disk somewhere. For these, we can either leave them unchanged, simply change them to a new name and break upgrade compatibility, forcing a reinstall, or implement an upgrade path, which adds complexity and takes effort.

It's useful to have a name like Metropolis, which is a single word, not generic, and can be abbreviated to 4-5 letters as in metroctl. "Monogon OS" does not have these properties. How would we rename metroctl? osctl seems too generic, mngnctl is hard to pronounce. We could make it a single word for use in identifiers by removing the space as in monogonos, but that is not ideal.