Hi,
It appears that I missed this thread while I was offline back in March
(I still have a large backlog of puppet-dev to read).
I was surprised when I discovered that the first rc of Statler was about
to be released this week, but now it makes sense :)
And if I'd read this mail before, I'd certainly had found the time to
work on the integration of this patch. So, I'm sorry for this failure on
my side.
Anyway, I'm really happy that you (James in fact) merged the patch set.
This is very cool!
I also have a subsequent patch set that is almost ready (should be
available during the week-end) and that I'd like to see appearing in the
rc2.
It adds a new puppet application: puppet device. It implements the
logical separation between the current host and the switch/routers by
acting like a "proxy" to the switch/router as seen from the puppet
master. It basically fetches the catalog from the master on behalf of
several switches/routers (drived by a configuration file).
The current mode of running is still supported to be able to use puppet
apply on a given switch/router.
The master sees the switch as a regular puppet node (you need to add a
node {} or use an ENC), so it benefits from regular node features, like
certificate security, reports, etc...
This patch also adds a new fact terminus for injecting facts coming from
the network device to the master (with a (minimal) implementation for
cisco).
The patch set looks stable and is quite minimal in terms of puppet core
code modifications, it just needs some minor adaptations for 2.7.x
(especially help embedded in the application).
I understand your concern of moving the cisco implementation out of the
puppet core, and if you want I can craft a patch removing the cisco
bits.
I hope this second part of the patch will be merged. Let me know what I
can do to make that happen.
Thanks!
On Fri, 2011-03-18 at 10:25 -0700, Luke Kanies wrote:
> This is mostly to Brice, but I figure others are interested.
>
> We've been looking at what it will take to get the network device
> support prototype as implemented by Brice into core, along with the
> fact that we'll be producing the RC1 for statler on April 13, and I
> don't think it will make this cut, based on our existing resources.
>
> So, I'd like to work to get it extracted into a module, so it can be
> more easily tested and such between now and the next feature release
> (which, given our announcement of timed releases, will be
> mid-October). One of my goals in this process would be to make sure
> that we got any changes into core that are necessary for this module
> to function.
>
> Does this seem like an acceptable compromise in the short term?
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to puppet-dev@googlegroups.com.
To unsubscribe from this group, send email to
puppet-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
