Should CIB setup instructions mention the service vessel pubkey?

[aaaaalbert]

The custominstallerbuilder config contains the public key which gets embedded in the "service vessel" (i.e. the small reserved space+resources that contains the nodemanager and softwareupdater logs on any install), https://github.com/SeattleTestbed/custominstallerbuilder/blob/2da182b8a52fbc124ec6ce65ee2f148fbcb4408b/settings_base.py#L62-L94. The CIB setup instructions do not currently mention this as an item that should be configured for a new site.

The implications of this are twofold:

• We can track installs that came from CIBs that we didn't set up, because they will advertise "our" service vessel pubkey. (Nice for us to have, but not strictly necessary).
• The admins of those CIB sites have no way to collect NM/SWUP logs from their nodes. (A pain for them, but they might not be aware of this in the first place).

I think that the latter is way more important to fix than the fact that this means we will lose one way of accounting for nodes across testbeds. (See SeattleTestbed/nodemanager#72 for an alternative proposal for tracking nodecounts.)

Opinions?

[aaaaalbert]

Side note: If we make the service vessel key configurable, then we need to change this here too:

https://github.com/SeattleTestbed/nodemanager/blob/master/servicelogger.py#L110