Skip to content
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

Closed
craig8 opened this issue Apr 23, 2015 · 5 comments · Fixed by #57
Closed

Agent registration and exposure through vip #42

craig8 opened this issue Apr 23, 2015 · 5 comments · Fixed by #57

Comments

@craig8
Copy link
Contributor

craig8 commented Apr 23, 2015

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
Copy link
Contributor

fstshrk commented Apr 23, 2015

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
#42.

@craig8
Copy link
Contributor Author

craig8 commented Apr 23, 2015

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
Copy link
Contributor Author

craig8 commented Apr 30, 2015

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
Copy link
Contributor

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
Copy link
Contributor Author

craig8 commented Apr 30, 2015

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

@craig8 craig8 self-assigned this May 11, 2015
@craig8 craig8 closed this as completed May 11, 2015
craig8 added a commit that referenced this issue Oct 30, 2019
volttrontesting/services/historian/test_multiplatform.py debugging
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants