Eucalyptus DNS-SD discovery protocol

Eucalyptus components - CLC, Walrus, SC, CC, and NC - use DNS-SD records, broadcast using mDNS, to advertise themselves. This allows the Eucalyptus administrator to install and, later, reconfigure the system with minimal manual effort. Specifically, a utility distributed with Eucalyptus will automatically gather information about Eucalyptus components, perform registration, and distribute cryptographic credentials for components to communicate securely.

Protocol

• Short name: eucalyptus
• Long name: Eucalyptus Discovery
• Contact info: Support Team <support@eucalyptus.com>
• Primary transport: TCP

TXT record keys for DNS-SD records

The TXT records for "eucalyptus" DNS-SD protocol will always contain the following keys:

• txtvers=<integer> (version of the TXT record, starting with "1")
• protovers=<integer> (version of the discovery protocol, starting with "1")
• eucavers=<string> (version of Eucalyptus for the component)
• type=[cloud|walrus|cluster|storage|node] (type of the Eucalyptus component)

Optionally, the TXT records may contain the following keys:

• eucauser=<string> (user that the component is running as)
• eucaroot=<string> (path of the root Eucalyptus directory for the component)

The latter two (eucauser and eucaroot) are useful on a Eucalyptus installation that spans multiple Linux distributions, since the root of the installation and the default user vary across distributions. The version of the Eucalyptus protocol (eucavers) will be provided because the underlying application protocol, based on SOAP messages, does not perform version checking.