Comment 1 for bug 1378993
Revision history for this message
| Julian Edwards (julian-edwards) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Ummm this is a little odd. Let me explain:
The old celery-based startup script connected with the region using a self-generated UUID, which is how the region uniquely IDs each cluster.
Upon each cluster startup connection, the region looked at the cluster status and if it's unknown, it says "go away for now but I may let you in later", and a new cluster is flagged for the admin to accept or not. If it's known, then the cluster connection is either accepted or rejected depending on what the admin previously did. If it's accepted, the secrets are sent back to the cluster so it can complete the (secure) connection.
If this process has gone manual for RPC style, then I consider this a regression that needs to be fixed. The admin should not need to know any secrets, it was designed to be easy to use and automatic.