Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should CIB setup instructions mention the service vessel pubkey? #13

Open
aaaaalbert opened this issue Jul 17, 2015 · 1 comment
Open
Labels

Comments

@aaaaalbert
Copy link
Contributor

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),

RESERVED_PERCENTAGE = 20
RESERVED_PUBLIC_KEY = ('22599311712094481841033180665237806588790054310631' +
'22212640538127192408957390862714329251678153065241' +
'18066213798225790714155936570886371161495933379772' +
'45852950266439908269276789889378874571884748852746' +
'04564336805810746002111791865754241307679148613009' +
'19631126128545917895186908567467573124723623322592' +
'77422867 ' +
'12178066700672820207562107598028055819349361776558' +
'37461088735487045522615055669952637546486391375031' +
'34279683626214107639968565432115029780129789820957' +
'21782038963923296750730921093699612004441897097001' +
'47453137576874628755013536139396199508236250310488' +
'33646534106312288966536664564631008506093439882030' +
'07196015297634940347643303507210312220744678194150' +
'28696628270130764506497467631616708900317832551835' +
'98633442778145515591974745904830447335743299259475' +
'70794508677779986459413166439000241765225023677767' +
'75455528219624191550099684271351183095435347543920' +
'91092498566442787450810470298799990224622309574271' +
'58692886317487753201883260626152112524674984510719' +
'26971542234003862082668443174813132566994006440475' +
'71206017273628813172226993934080975969813558102579' +
'55915922792648825991943804005848347665699744316223' +
'96385126385185348333569932187148396617648083929312' +
'54130576035617245982276177369442602699941116102868' +
'27287926594015501020767105358832476708899657514473' +
'42315337751466064169938344506536919972404338007214' +
'62465370395773906592436407103393295066205750341750' +
'16766639538091937167987100329247642670588246573895' +
'99025121172183951771379041317064617724621636602985' +
'36040314219321231671154448349084245569926629359811' +
'66395451031277981021820123445253')
. 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
Copy link
Contributor Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant