Ohai Chefs!
As a followup to a sub-conversation on the mailing list a couple weeks
back, a few of us (ranjib, stevendanna, and myself) have been working on a
new systemd cookbook for the last couple of weeks.
Love it or hate it, systemd is going to be pretty pervasive in the coming
years, so we really want this to be a high-quality cookbook. To support
this, we’d love to start getting early-adopter feedback around the APIs in
particular, to make sure we’re on the right track.
For 0.1.1, we focused on providing a set of resources for managing unit
files and their life-cycle events; for the next release we’ll be focusing
on recipes to manage core systemd services (journald, timesyncd, &c), along
with any bug-fixes or enhancements needed.
The code’s still not well-tested in the field, so I’d recommend caution
before using it in production, but any and all feedback is welcome :).
Thanks, and happy testing!
Nathan
This is awesome.
Thanks Nathan!
-s
On Fri, Jul 10, 2015 at 7:38 PM, Nathan Williams nath.e.will@gmail.com wrote:
Ohai Chefs!
As a followup to a sub-conversation on the mailing list a couple weeks back,
a few of us (ranjib, stevendanna, and myself) have been working on a new
systemd cookbook for the last couple of weeks.
Love it or hate it, systemd is going to be pretty pervasive in the coming
years, so we really want this to be a high-quality cookbook. To support
this, we'd love to start getting early-adopter feedback around the APIs in
particular, to make sure we're on the right track.
For 0.1.1, we focused on providing a set of resources for managing unit
files and their life-cycle events; for the next release we'll be focusing on
recipes to manage core systemd services (journald, timesyncd, &c), along
with any bug-fixes or enhancements needed.
The code's still not well-tested in the field, so I'd recommend caution
before using it in production, but any and all feedback is welcome :).
Thanks, and happy testing!
Nathan