--
You received this message because you are subscribed to the Google Groups "Salt-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to salt-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Bruno,Masterless minion can run salt-call without master, it can run highstate just like you have a master/minions setup, see https://docs.saltstack.com/en/latest/topics/tutorials/quickstart.html
I'm not sure why you feel it slow, since it basically the same as running a minion with master, less the network back and forth.
Could you be more specific about what you want to achieve with salt engine?
В Втр, 11/10/2016 в 18:30 +0200, bruno binet пишет:
...
>
> What I would like to achieve is something similar to the salt-api of
> the salt master, but for the salt minion.
>
> So the engine would basically do the initialization stuff once at
> startup, and then it would expose an http api (similar to the
> salt-api) so that executing states through this http api would be much
> faster than running the salt-call command.
>
>
> Also the second advantage of such an engine is that a http api would
> be easy to integrate in a webapp running on the minion, for example if
> you want to create a system web admin interface based on salt
> (masterless).
as a workaround you can run full-featured minion and master with api on
the same system. maybe overkill, but should work out of the box.
To unsubscribe from this group and stop receiving emails from it, send an email to salt-users+unsubscribe@googlegroups.com.
You'd need to set up a parallel config directory and insure the new Masterless minion calls have the correct config directory flags when called. If you compile yourself, you can set the default directory differently at compile time.
~~shane
--
You received this message because you are subscribed to a topic in the Google Groups "Salt-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/salt-users/jPVEAYnD5SA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to salt-users+unsubscribe@googlegroups.com.
It only returns 200 if it posted the message to the queue, if it is a minion with file_client: local, it sends the event to the minion, otherwise it sends the event to the master.
If it is on the master, it sends the event to the master. It is an engine so it can run on both masters and minions, starting in Carbon.It takes the uri, and just passes that as the tag to the event stream, and then takes the payload, and passes it in the data to the event stream, it also passes the headers, so that stuff like the github webhook events can be verified with the hmac signature.
On 14 October 2016 at 16:01, Daniel Wallace <dwal...@saltstack.com> wrote:I can add that.ThanksIt only returns 200 if it posted the message to the queue, if it is a minion with file_client: local, it sends the event to the minion, otherwise it sends the event to the master.It would be great if we could also choose to force send the message to the minion even if file_client is not "local". Can we imagine a configuration option or a runtime parameter (like listening to two different urls, either dedicated to sending events to either the master or dedicated to sending events yo the minion)?