How Aeolus Audrey Agent finds the Config Server

How Aeolus Audrey Agent finds the Config Server

Background

The Aeolus Audrey Agent, when built into an image, will attempt to
contact a Config Server at launch time. Once contacted the Config
Server will provide configuration parameters and tooling. For a
more detailed description of what the Aeolus Audrey Agent and Config
Server do and how see:

http://www.aeolusproject.org/page/Audrey

This Document Goal

The goal of this document will be to describe how the Aeolus
Audrey Agent is passed the contact information for the Config
Server.

Config Server contact information format

The Config Server contact information will be delivered to the
Audrey Agent as a base64 encoded string consisting of four
fields separated by the | (vertical bar or pipe) character.

> h3. Format
>
> version | CS URL | oauth key | oauth secret
>
> version
>
> A version number for the protocol between the Audrey
> Agent and the Config Server
>
> CS (Config Server) URL is of the form:
>
> https://

:
> oAuth Key and Secret
>
> address: The IP Address or resolvable host name where the
> Config Server is running
>
> port: The port number where the Config Server is listening.
>
> *oauth key: *
> The OAuth key which the Audrey Agent will use to access the Config Server.
>
> *oauth secret: *
> The OAuth secret which the Audrey Agent will use to access the Config Server.
>
>

Delivering the Config Server contact information to the Agent.

The mechanism for delivering the Config Server contact information to the
Audrey Agent differs depending on which back end the instance containing
the Audrey Agent is launched.

EC2
>
> The Config Server contact information is passed to the Audrey
> Agent running in an EC2 instance using Amazon EC2 instance-specific
> metadata (AKA user data)
>
> see: http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/AESDG-chapter-instancedata.html
>

RHEVm
>
> The Config Server contact information is passed to the Audrey
> Agent running in an RHEVm instance using the RHEVm virtual
> machine instance’s floppy device hooks, as injected by
> deltacloud at launch time.
>
> see: http://deltacloud.apache.org/
>
> > The pseudo code is:
> >

modprobe floppy

mount /dev/fd0 /media

read /media/deltacloud-user-data.txt

>
>

vSphere
>
> The Config Server contact information is passed to the Audrey
> Agent running in an vSphere instance using the vSphere virtual
> machine instance’s cdrom device, as injected by deltacloud at
> launch time.
>
> see: http://deltacloud.apache.org/
>
> > The pseudo code is:
> >

mount /dev/cdrom /media

read /media/deltacloud-user-data.txt