On Fri, Mar 6, 2015 at 8:46 AM, Eric Thompson wrote:
>
>> Currently there are two separate certificate authority implementations,
>> one in Ruby and one in Clojure. Puppet 5 will consolidate onto the new
>> Clojure CA, removing the Ruby CA code and building new command-line tools
>> to interact w
>
>
> Currently there are two separate certificate authority implementations,
> one in Ruby and one in Clojure. Puppet 5 will consolidate onto the new
> Clojure CA, removing the Ruby CA code and building new command-line tools
> to interact with it. (See SERVER-270 for the design/requirements work
On 03/06/2015 05:30 AM, Eric Sorenson wrote:
> There are two main areas of change, both related to continuing to move
> server-side functionality into Puppet Server: the certificate authority and
> the network stack. There may be other semver-major breaks that get rolled
> in, but at this point
On Fri, Mar 6, 2015 at 6:41 AM, Erik Dalén
wrote:
>
> Also a solution to https://tickets.puppetlabs.com/browse/SERVER-115 is
> really needed. It can sort of be solved in the Ruby version by only using a
> single worker instance.
>
This is definitely slated for Puppet 5.0/Puppet Server 3.0.
>
>
+1 to OCSP support!
Trevor
On Fri, Mar 6, 2015 at 9:41 AM, Erik Dalén
wrote:
>
>
> On Fri, 6 Mar 2015 at 05:30 Eric Sorenson
> wrote:
>
>> Hi all, this may seem a bit far-out since we haven't pushed Puppet 4
>> completely out of the nest, but I wanted to talk about some plans for the
>> next c
On Fri, 6 Mar 2015 at 05:30 Eric Sorenson
wrote:
> Hi all, this may seem a bit far-out since we haven't pushed Puppet 4
> completely out of the nest, but I wanted to talk about some plans for the
> next cycle of breaking changes/deprecations that are headed for Puppet 5.
>
> There are two main ar
Hi Eric,
On 06 Mar 2015, at 05:30, Eric Sorenson wrote:
> […]
> Similarly, on the network stack, we want to consolidate on the
> jetty/puppet-server/jruby stack as the single way to run Puppet masters, so
> the built-in webrick support and Rack support layer will ride off into the
> sunset.
Hi all, this may seem a bit far-out since we haven't pushed Puppet 4 completely
out of the nest, but I wanted to talk about some plans for the next cycle of
breaking changes/deprecations that are headed for Puppet 5.
There are two main areas of change, both related to continuing to move
server-
