Hello,

I am pleased to announce a new version of the Choria Server, the focus
here was, as in the previous release, about the early bootup life cycle
of new instances in environments without traditional CM (IoT, Cloud,
Containers etc).
The Choria Server (and soon most other components) will emit life cycle
events to the middleware on startup, shutdown etc. Tools like the
recently released provisioner can listen for these events and short
circuit the time to provision new nodes based on these events.
I've also added some basic tooling to view events, publish and view
contents of arbitrary topics to assist with debugging etc.
*Enhancements:*
 * Add a plugin to assist with resolving the provisioning mode target
   brokers (#408)
 * Attempt to find the FQDN via DNS lookups before calling Puppet when
   the hostname is incomplete (#412)
 * Expose the version to Prometheus as choria_build_info (#411)
 * Publish a startup lifecycle event on startup (#416)
 * publish a shutdown lifecycle event on clean shutdowns (#422)
 * Add tool event, tool sub and tool pub commands to the CLI (#419)
 * Update provisioning agent dependency, allows restart when not in
   provisioning mode if a token is set (choria-io/provisioning-agent#41)
*Bug Fixes:*
 * Ensure provisioning mode is active only for the server and not client
   invocations (#402)
--
R.I.Pienaar / www.devco.net / @ripienaar

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"mcollective-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mcollective-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to