Closed craig8 closed 9 years ago
If the VOLTTRON platform is hardcoded to a VOLTTRON Central it should attempt to connect to that VC and refuse requests for management from other VCs. If the VOLTTRON platform is not hardcoded to a VC, it will respond to the first management request from a VC. THereafter, it will refuse further management requests from other VCs. A VC may un-register a VOLTTRON platform (non-hardcoded). The VOLTTRON platform is then available for management requests from other VCs.
Future enhancement might be overriding harcoded VCs by adding config information to the mutable luggage of the platforms Management Agent. Another possibility is allowing a platform to be managed by multiple VCs provided the administrators do not send conflicting commands.
Can a VC also issue a command to cause a VOLTTRON platform to register to another VC.
On Thu, May 14, 2015 at 11:24 AM, jhaack notifications@github.com wrote:
If the VOLTTRON platform is hardcoded to a VOLTTRON Central it should attempt to connect to that VC and refuse requests for management from other VCs. If the VOLTTRON platform is not hardcoded to a VC, it will respond to the first management request from a VC. THereafter, it will refuse further management requests from other VCs. A VC may un-register a VOLTTRON platform (non-hardcoded). The VOLTTRON platform is then available for management requests from other VCs.
— Reply to this email directly or view it on GitHub https://github.com/VOLTTRON/volttron/issues/63#issuecomment-102127010.
Sure that's not a problem since they are two different agents on two different vip networks. I should try that and see how it works.
Currently a PlatformAgent calls out to the VolttronCentral agent and establishses a connection. This will allow a PlatformAgent to be dynamically joined to the VolttronCentral agents sphere of influence.