Viking Agent

The Viking Agent is the workhorse of the Viking Configuration Management System. An instance of the Agent runs on every managed machine.

The Agent contains the parser and execution engine for interpreting Longships, downloading and caching Hammars, executing Strikes, and reporting back to the Viking Server with the results of the Voyage.

Agent Command Line Options

Voyage Sequence

  1. Call For The Longship - Send a request, including my hostname, to the Viking Server for the Longship. This returns only sections relevant to this machine (i.e. Global and this host)

  2. Pillage - Collection of information (spoils) about the machine that the agent is running on, including, but not limited to

    • Hostname (This is actually determined before calling for the longship, but is also added as a spoil)

    • CPU Type

    • CPU Core Count

    • Memory Quantity

    • Disk space per partition/mount point

  3. Scan the longship for Hammars

    • For each Hammar

      • if that name/version is not already cached

        • Request if from the viking-forge and cache it (The longship can specify a local forge, and whether to try the master forge if the hammar is not found)

      • If that version is not already in the unpacked cache

        • Delete any existing unpacked files

        • Unpack the correct version

  4. Execute the strikes in the Longship, in order, chronicling the Strike against that strike name in the Voyage Chronicle

  5. Return the Voyage Chronicle