-
Notifications
You must be signed in to change notification settings - Fork 216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Agent registration and exposure through vip #42
Comments
Hi Craig Just checking that we can still host multiple VOLTTRON instances on one Thanks On Wed, Apr 22, 2015 at 7:13 PM, Craig notifications@github.com wrote:
|
Most definatly. The VOLTTRON_HOME just needs to be set differently for each instance
Seperate vip_addresses, but same vip_identity of 'platform' |
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. |
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? |
then the vip name for that agent could be volttron.central? |
volttrontesting/services/historian/test_multiplatform.py debugging
As a first cut I want to have the following standard approaches for platforms.
'platform'--'platform.manager'-- 'platform.agent'.PlatformManagerAgentVolttronCentralAgent can be available. From the management console an administrator can register a vip_address. Assuming the above two items are established then thePlatformManagementAgentVolttronCentralAgent will have access to all agents that have registered with the individual platforms.The text was updated successfully, but these errors were encountered: