VOLTTRON Central

Agent Introduction

The VOLTTRON Central Agent is responsible for controlling multiple VOLTTRON instances through a single interfaces. The VOLTTRON instances can be either local or remote. VOLTTRON Central provides a web based interface to our JSON based web api. Both the web api and the interface are serviced through the VOLTTRON Central agent. There is a VOLTTRON Central Demo that will allow you to quickly setup and see the current offerings of the interface. VOLTTRON Central will allow you to

• See a list of platforms being managed.
• Add and Remove platforms.
• Install, Start and Stop agents to the registered platforms.
• Create graphs from the historians based upon the points.

Configuration

Agent Execution

• Platform status
• Overall status of host machine
• CPU, RAM, HD space
• VOLTTRON Platform status

  • Num of agents installed, running, stopped (error, expected)

• Restricted - # moved onto platform
• Status of service agents
  • Actuator, Weather, etc.
  • Historians
    • Unable to write to remote destination
• Status of user agents
  • AFDD – Unable to take command action (could not get reservation)

Agent Status: val Message

Status Message: {“status”: “red/green/OK”, “message”:”Failed to write to remote host”} When agents start, they register with their expected longevity: forever, periodic.

See points similar to how sMAP does. See values

Status:

• Initial Front End exists
• Developer interface

Use Cases:

• VOLTTRON User: VOLTTRON user wants to see the status of the deployed VOLTTRON platforms. Observe CPU/memory/etc utilization; see the collected points, see the data coming the points and pivot to OpenEIS to run analytics on the data set. VOLTTRON user may want to push a new agent to platform, stop a running agent, or start an agent that is already deployed on the platform.
• VOLTTRON Developer
• VOLTTRON System Administrator: Configure deployed VOLTTRON platforms from VOLTTRON Central. Get a Python shell to execute Python commands. Get a UNIX shell to execute UNIX commands. Synchronize system time. Collect logs from VOLTTRON platforms at VOLTTRON Central. Check system status with respect to success/failure of software updates etc.

Initial VOLTTRON configuration to connect to VOLTTRON Central:

• VOLTTRON Central Domain Name (or IP address)
• VOLTTRON Central Public Key. Requiring the public key of VOLTTRON Central allows the VOLTTRON instance to validate the server's identity. The reverse direction (i.e. client identity is not required) because a VOLTTRON central admin can see the new VOLTTRON platform and authorize the "join" operation.

Next Steps:

• Act as NTP Server
• Initial front end
• Security tab to setup security, maybe through shell