search

VOLTTRON / volttron

VOLTTRON Distributed Control System Platform
https://volttron.readthedocs.io/
Other
455 stars 216 forks source link

Agent registration and exposure through vip #42

Closed craig8 closed 9 years ago

craig8 commented 9 years ago

As a first cut I want to have the following standard approaches for platforms.

  1. There will only be one PlatformAgent per instance of volttron.
  2. The single instance of PlatformAgent will have a vip_identity of 'platform' --'platform.manager'-- 'platform.agent'.
  3. A PlatformManagerAgent VolttronCentralAgent can be available. From the management console an administrator can register a vip_address. Assuming the above two items are established then the PlatformManagementAgent VolttronCentralAgent will have access to all agents that have registered with the individual platforms.
fstshrk commented 9 years ago

Hi Craig

Just checking that we can still host multiple VOLTTRON instances on one physical hardware system.

Thanks

On Wed, Apr 22, 2015 at 7:13 PM, Craig notifications@github.com wrote:

As a first cut I want to have the following standard approaches for platforms.

  1. There will only be one PlatformAgent per instance of volttron.
  2. The single instance of PlatformAgent will have a vip_identity of 'platform'
  3. A PlatformManagerAgent can be available. From the management console an administrator can register a vip_address. Assuming the above two items are established then the PlatformManagementAgent will have access to all agents that have registered with the individual platforms.

— Reply to this email directly or view it on GitHub https://github.com/VOLTTRON/volttron/issues/42.

craig8 commented 9 years ago

Most definatly. The VOLTTRON_HOME just needs to be set differently for each instance

VOLTTRON_HOME=/tmp/v1home volttron -vv
VOLTTRON_HOME=/tmp/v2home volttron -vv

Seperate vip_addresses, but same vip_identity of 'platform'

craig8 commented 9 years ago

According to @hashstat the "platform" name is taken for use as the actual platform. So we thought that the name --"platform.manager"-- "platform.agent" would be a good alternative vip name for this.

timothykang commented 9 years ago

If PlatformAgent is going to have the VIP identity "platform.manager", then it seems we'll need a new name for PlatformManagerAgent, to avoid confusion. Perhaps VOLTTRONCentralAgent?

craig8 commented 9 years ago

then the vip name for that agent could be volttron.central?