You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I call it service injection, just to have a cool name for it. Basically it'll be a side channel to manually create microservices instances attached to an Allocator. This will enable easier setup for more complex test cases without having to jump through a bunch of hoops.
Current thoughts is that it will be implemented as an HTTP server spun up alongside the allocator P2P node that will respond to commands such as create or possibly in the future kill.
Query the HTTP server with the desired command and the HTTP server will pass this off to the Allocator which will execute the command.
To keep this side channel as consistent as possible so we don't have two sets of similar code to worry about testing, the actual allocation will be done by sending a P2P allocation request from the Allocator back to the Allocator itself.
This can be enhanced for security by adding a PSK to the command to signal that it is a command sent from an "admin" that can be only run by someone who has privileged access to the Allocator.
The text was updated successfully, but these errors were encountered:
It'd be good even for something like our demo covid tracker. I had to manually start the web server since you need something to request it for the allocator to allocate it, but no service sends requests the web server.
I hadn't made the web server able to respond to p2p requests and was running its proxy in client mode, but yeah probably should have made it so that was possible.
I call it service injection, just to have a cool name for it. Basically it'll be a side channel to manually create microservices instances attached to an Allocator. This will enable easier setup for more complex test cases without having to jump through a bunch of hoops.
Current thoughts is that it will be implemented as an HTTP server spun up alongside the allocator P2P node that will respond to commands such as
create
or possibly in the futurekill
.The text was updated successfully, but these errors were encountered: