I am trying to build a Win 2008 R1 SP2 baked AMI using packer and puppet.
My builder works fine and creates the AMI with puppet installed.
Now in my provisioner I have a very simple puppet script and it is
executing when I do a puppet apply on the instance.
But inside packer it is failing with
Hi,
Sorry for the delayed response.
In our case we are using Passenger.
On 5 March 2015 at 15:24, Henrik Lindberg
wrote:
> On 2015-05-03 12:02, James Green wrote:
>
>> We occasionally have an agent fail because of this. I'm told by others
>> running the agents more frequently that it appears t
The documentation at
https://docs.puppetlabs.com/puppetdb/latest/maintain_and_tune.html talks
about checking the MQ depth.
I'm not seeing such a thing on our dashboard but plenty of others not
documented such as Catalogue Duplication.
Am I looking at outdated documentation?
James
--
You receiv
Hi all.
I am configuring Puppet in our environment for configuration
management. Also I am using Hiera and it's so great so far.
Now managers are asking if we can use it as patch mgmt tool. I said
Puppet it's not but it can help with patch/pkg distribution which I
think it could be very good.
Do yo
I would recommend using the `floor` function from puppetlabs/stdlib
https://forge.puppetlabs.com/puppetlabs/stdlib
Thanks,
Jonathan
On 10/03/15 09:27, MaryG wrote:
Hi,
I get this value from fact:
$shmmax = <<$facts['memorysize_mb']*1024*1024)/2
I want to trunc since I get a float 963211427.
On Tuesday, March 10, 2015 at 9:59:41 PM UTC-5, Bostjan Skufca wrote:
>
>
>
> On Monday, 9 March 2015 14:45:38 UTC+1, Christopher Wood wrote:
>>
>> On Sun, Mar 08, 2015 at 11:55:03AM -0700, Bostjan Skufca wrote:
>> >With hiera:
>> >- How would you go about when certain nodes need data m
I agree with what you wrote.
Puppet is not the best tool to execute one-shot operations like patching or
deploying of applications.
It's good at maintaining the state of the resources of our systems, so you
can use it to configure what you need to manage the patching or the
deployment of a syste
Sure you can,
you have to pass the --hiera_config parameter to the puppet apply command
(pointing to your hiera.yaml) and you will need the private key used to
encrypt keys on every node (this is maybe the only issue with hiera-eyaml
in masterless mode).
al
On Tuesday, March 10, 2015 at 10:37:
On Tuesday, March 10, 2015 at 10:30:48 PM UTC-5, Amos Shapira wrote:
>
> Hi,
>
> I'm running into the common issue of having to force an "apt-get update"
> before installing packages (in my case - because the base EC2 AMI is old
> and I need it to pick newer package versions).
>
> I ended up do
We're using eyaml in our masterless setup as well. We've got our
hiera.yaml in /etc/puppet, so we don't need to specify the
--hiera_config with puppet apply.
True that distributing the private key(s) was an interesting issue to solve.
- Jeff
On 03/11/2015 08:30 AM, Alessandro Franceschi wrote:
(Replying to two people in one email, hum.)
On Wed, Mar 11, 2015 at 06:01:39AM -0700, jcbollinger wrote:
>On Tuesday, March 10, 2015 at 9:59:41 PM UTC-5, Bostjan Skufca wrote:
>
> On Monday, 9 March 2015 14:45:38 UTC+1, Christopher Wood wrote:
>
>On Sun, Mar 08, 2015 at 11:55:03
Looking at developing a type/provider for RHSM.
Python API libraries exist, but not Ruby.
I found the RubyPython gem, but the idea of an imbeded Python interpreter seems
a bit scary.
Anyone been down this road or am I trailblazing again ?
“Sometimes I think the surest sign that intelligent lif
On Wednesday, March 11, 2015 at 1:57:00 PM UTC, Christopher Wood wrote:
>
>
> >Puppet in fact provides three functions functions for lookups: there
> is
> >also hiera_hash().
> >
> >In any case, you are quite right. Which sort of lookup is intended
> is an
> >attribute of th
Hey James,
The MQ depth is labeled "Command Queue depth" in the dashboard. I just
updated the docs to make that connection explicit, so your link should be
updated shortly.
That page isn't intended to document the dashboard specifically, so not all
the fields are described. We don't really docume
On Wednesday, 11 March 2015 14:57:00 UTC+1, Christopher Wood wrote:
>
> (Replying to two people in one email, hum.)
>
> I rather take your point, but isn't the requirement for different data
> handling just another data item? Is any code unaware of the underlying data
> structure? Even if you ha
On Wednesday, 11 March 2015 15:59:12 UTC+1, Luke Bigum wrote:
>
>
> On Wednesday, March 11, 2015 at 1:57:00 PM UTC, Christopher Wood wrote:
>>
>>
>> Could you possibly expound on the "Each user of the data somehow has to
>> know" part? I'm having trouble with the notion that people would use pup
On Wednesday, 11 March 2015 15:59:12 UTC+1, Luke Bigum wrote:
>
>
> The second example of module design may be super awesomely flexible in
> terms of how I can structure my Hiera data, but it doesn't fit the
> direction the community is moving in terms of module design.
>
What do you mean by th
Jeff,
I realize you may not want to share the details, but can you share your
strategy on management of the private keys in a masterless setup?
Thanks for the reply.
Heinz
On Wednesday, March 11, 2015 at 9:43:02 AM UTC-4, jeff Adams wrote:
>
> We're using eyaml in our masterless setup as well.
We're using a couple of techniques:
We bake them into our system images, and for ad-hoc we have a Rundeck
job that can push the keys onto a host.
Haven't had to rotate the keys yet, but I presume that we'd either use
the ad-hoc technique, or re-spin the system image and re-deploy the
hosts. Sinc
We have a Puppet config that stores files outside of modules, along with
appropriate auth.conf entries to support this.For the most part, it has
just worked and I haven't felt any need to muddle with it - so I was
surprised to find a bevy of these errors in the logs:
Mar 11 18:24:51 centra
On Wednesday, March 11, 2015 at 4:35:36 PM UTC, Bostjan Skufca wrote:
>
>
>
>> Something like this seems like I'm telling a module *how* to look up my
>> own data, rather than passing the right data to the module:
>>
>>
>> class resolv (
>> $dns_servers_key_name = 'dns_servers',
>> $dns_serv
Agree.
Thanks
On 12/03/2015 12:26 AM, "Alessandro Franceschi" wrote:
> I agree with what you wrote.
> Puppet is not the best tool to execute one-shot operations like patching
> or deploying of applications.
> It's good at maintaining the state of the resources of our systems, so you
> can use it
Hi there,
I have the same issue here.
Still digging on how to make this work, so far when using package_name =>
'percona-xtradb-cluster-server-5.5' I have an error.
Next step for me is digging into the autogenerated my.cnf ...
Any feedback would be appreciated :)
Anthony
Le mardi 9 décembre 20
Hi,
I'm trying to learn puppet by using it on a test machine I have. Figured
that for single server, it makes sense to use master-less mode.
So, my question is like this. To set it up, I figured that:
1. /etc/puppet would be clone of some repo
2. in /etc/puppet/manifests/site.pp, I would add vcs
- Original Message -
> From: "Christopher Wood"
> >Puppet in fact provides three functions functions for lookups: there is
> >also hiera_hash().
> >
> >In any case, you are quite right. Which sort of lookup is intended is
> >an
> >attribute of the data -- part of the
On Wednesday, 11 March 2015 23:31:38 UTC+1, Luke Bigum wrote:
>
>
>
> On Wednesday, March 11, 2015 at 4:35:36 PM UTC, Bostjan Skufca wrote:
>>
>>
>>
>>> Something like this seems like I'm telling a module *how* to look up my
>>> own data, rather than passing the right data to the module:
>>>
>>>
> On Mar 11, 2015, at 8:32 PM, Hubert Lubaczewski wrote:
>
> Hi,
>
> I'm trying to learn puppet by using it on a test machine I have. Figured that
> for single server, it makes sense to use master-less mode.
>
> So, my question is like this. To set it up, I figured that:
> 1. /etc/puppet would
On Thursday, 12 March 2015 00:39:53 UTC+11, jcbollinger wrote:
>
>
>
> On Tuesday, March 10, 2015 at 10:30:48 PM UTC-5, Amos Shapira wrote:
>>
>> Hi,
>>
>> I'm running into the common issue of having to force an "apt-get update"
>> before installing packages (in my case - because the base EC2 AMI
Hi,
I checked the repo, but I don't understand what you wrote in the README.
What is the purpose of these ssh keys? Why are you, in the run_puppet
script, copying config to some place versioned by git commit, and run
puppet from there, instead of just keeping /etc/puppet as git repo?
Basically
29 matches
Mail list logo
