Same here.
El miércoles, 26 de agosto de 2015, 15:45:07 (UTC+2), Pete Harvey escribió:
On 26 August 2015 at 09:16, Fabrice Bacchella
fabrice@orange.fr javascript: wrote:
My biggest problem: there isn't any working dashboard working with
Puppet 4.
This. Our upgrade to 4 is
Agreed.
Between the AIO packaging, change in configuration file locations, lack of
dashboards, and the many other minor annoyances I do not feel the benefits
of 4 outweigh the hassle of upgrading. 2-3 was much, much less painful.
Jeffrey.
On Thu, Aug 27, 2015 at 1:46 PM, Felix Barbeira
Le 24 août 2015 à 21:59, Christopher Wood christopher_w...@pobox.com a
écrit :
I am not seeing a large amount of blog entries complaining about this
upgrade, how has that gone for you? Is there anything you found particularly
painful? Would you have done anything different in
Le 26 août 2015 à 11:30, Stefan Heijmans heijm...@gmail.com a écrit :
On Wednesday, August 26, 2015 at 10:16:59 AM UTC+2, Fabrice Bacchella wrote:
Le 24 août 2015 à 21:59, Christopher Wood christop...@pobox.com
javascript: a écrit :
My biggest problem: there isn't any working
On Wed, Aug 26, 2015 at 10:16:28AM +0200, Fabrice Bacchella wrote:
Le 24 août 2015 à 21:59, Christopher Wood christopher_w...@pobox.com a
écrit :
I am not seeing a large amount of blog entries complaining about this
upgrade, how has that gone for you? Is there anything you found
(Following up to myself.)
My current set of puppetdb classes do not have an easy upgrade path, especially
given how I macgyvered in the capacity to manage certificate whitelisting.
However I'm still not sure I care about past data in (appliance'y) puppetdb
enough to upgrade anything. I may
On Wednesday, August 26, 2015 at 10:16:59 AM UTC+2, Fabrice Bacchella wrote:
Le 24 août 2015 à 21:59, Christopher Wood christop...@pobox.com
javascript: a écrit :
My biggest problem: there isn't any working dashboard working with Puppet
4. The puppetdb APIv4 in puppet db 3.1 is not
On 26 August 2015 at 09:16, Fabrice Bacchella
fabrice.bacche...@orange.fr wrote:
My biggest problem: there isn't any working dashboard working with Puppet 4.
This. Our upgrade to 4 is essentially blocked until Foreman supports it.
Pete
--
You received this message because you are subscribed
On 8/24/15 12:59 PM, Christopher Wood wrote:
(Although I may dump/restore the data via puppetdb since that's the actual api
to the data, we do not log in via PostgreSQL.)
Others can speak to the rest of the plan, but just to clarify in case
I'm understanding you right: the PuppetDB
I am not seeing a large amount of blog entries complaining about this upgrade,
how has that gone for you? Is there anything you found particularly painful?
Would you have done anything different in retrospect?
I'm staring down a 3.7.2 - 4.2.1 upgrade and after reading a number of docs
the
I will be snapshotting the VM to lower the rollback effort there, but good
point at that. Otherwise that saves me a bunch of preprod fiddling, thank you.
On Mon, Aug 24, 2015 at 01:35:21PM -0700, Wyatt Alt wrote:
On 8/24/15 12:59 PM, Christopher Wood wrote:
(Although I may dump/restore the
11 matches
Mail list logo
