Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [volttron-dev] MessageBus WG Summary
Hi Andrew,

What sort of agent backend have you encountered/do you envision that wasn't a message bus and used the pub/sub event based interaction paradigm?

              jak
          

On Sat, Feb 4, 2023 at 8:56 AM Andrew Rodgers <andrew@xxxxxxxxxxxxxxxxxxx> wrote:
My understanding is Pub/Sub is an interface presented to the agent developer, whereas the message bus is a south bound interface to the infrastructure, the goal being that an agent developer doesn't have to have any knowledge of the implementation of the platform and that an agent can be moved from backend to backend without affecting functionality.

—
Andrew Rodgers
Co-Founder
ACE IoT Solutions

On February 3, 2023 at 6:57 PM EST kempf42@xxxxxxxxx wrote:

Hi Craig,

Great summary, thanx.

Here's the question at the end which I didn't have time to ask. With respect to the publish/subscribe mechanisms already in place, from the above and the discussion today I was curious whether the pub/sub abstractions will be used anywhere other than to the VIP bus?  I am wondering why the pub/sub abstraction should be kept separate from the message bus? It seems more complicated and combining them would be simpler, just one interface to keep track of instead of two.

AFICS from the discussion today separating the pub/sub mechanism was primarily to use a common serializing/deserializing mechanism between RabbitMQ and ZeroMQ, right?

       jak

On Fri, Feb 3, 2023 at 1:37 PM Allwardt, Craig H via volttron-dev <volttron-dev@xxxxxxxxxxx> wrote:

All,

 

We had our first MessageBus working group meeting today.  The next one will be in two weeks (opposite Friday’s of the main office hours).

 

We discussed the abstraction of the AuthService

 

  • The AuthService will have an interface in volttron-core that will be available for others to plugin other auth mechanisms
  • The separation of Authentication and Authorization from the auth.json file into potentially two files one that captures the auth mechanisms and one that contains the capabilities of an agent.

 

We discussed the abstraction that the VIP routing gives us

 

  • The MessageBusInterfase does not need a publish/subscribe because the agent’s pubsub service will use Core which has the send/receive vip.  This send/receive vip message does a translation to publish and subscribe mechanisms already in the platform.

 

Some links and topics discussed are as follows which one could implement as authentication services for volttron:

 

If anyone else has some more notes, please send them along.

 

Craig

_______________________________________________
volttron-dev mailing list
volttron-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/volttron-dev

_______________________________________________
volttron-dev mailing list
volttron-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/volttron-dev

Back to the top