-
Notifications
You must be signed in to change notification settings - Fork 218
VOLTTRON Central
timothykang edited this page Apr 22, 2015
·
11 revisions
- See a list of platforms being managed (will be there as soon as threading is resolved)
- Platform status
- Overall status of host machine
- CPU, RAM, HD space
- VOLTTRON Platform status
- 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
- Platform Agent
- VOLTTRON Central Agent
- Platform Commands
- Platform Configuration
- [Platform Hardening Security Recommendations] (Linux-Platform-Hardening-Recommendations-for-VOLTTRON-users)
- ...
- [Building VOLTTRON] (Building-VOLTTRON)
- Example Agents
- Agent Development
- [Shortcut Scripts] (Scripts)
- [VOLTTRON Conventions] (Conventions)
- [sMAP Test Server] (sMAP-Test-Instance)
- [Design Discussions] (Design Discussions)
- VIP
- VIP - VOLTTRON Interconnect Protocol
- RPC by example
- VIP - Known Identities
- VIP - Authentication
- VIP - Authorization
- Protecting Pub/Sub Topics
- Setup Eclipse for VOLTTRON
- Deployment Walkthrough
- Forward Historian Walkthrough
- [Create New Historian Agent] (Developing-Historian-Agents)
- [Create New Driver Agent] (Develop-Driver-Agent)
- [Developing With Eclipse] (Eclipse)
- Migrations
- [2.x to 3.x Migration](2.x-to 3.x-Migration)
- 1.2 to 2.0 Migration
- [Deployment Recommendations](Recommendations for Deployments)
VOLTTRON Versions and Features
Transactional Network Platform Overview
- Established Topics
- Working with the Actuator Agent
- Logging
- [Multi-Node Communication] (MultiBuildingMessaging)
Information Exchange Standards