apt.sources on Ubuntu to Just
Work, i.e. without any special invocations to tell APT to grab from a
Debian release name?)
Thanks for any tips from any Ubuntu+Puppet folks.
--
Kyle Cordes
http://kylecordes.com
--~--~-~--~~~---~--~~
You received this message because you
On Feb 7, 5:19 pm, Jon Stanley wrote:
> Augeas support was introduced in 0.24.7 - but I'm not quite able to
Thanks for the pointer - Augeas appears to be a very good thing (I
encountered it a while back), far superior to manual scripting / sed
hackery to adjust configuration files.
Unless any
ter
> and clients at the same version.
I will follow this advice,
> Author of:
> * Pulling Strings with Puppet
> (http://www.amazon.com/gp/product/1590599780/)
and buy your book.
--
Kyle Cordes
http://kylecordes.com
--~--~-~--~~~---~--~~
You rece
d where I installed once and never upgraded
a distro release, but rather got new versions of everything a bit at
time. This could easily create more trouble than it solves,
obviously.
--
Kyle Cordes
http://kylecordes.com
--~--~-~--~~~---~--~~
You received this messa
understand
why the distros do it the way they do it, and it's the right answer, and
I like it. Most of the time. Puppet is an example of an exception:
the Right Thing is to run the current Puppet across N different
distros/version.)
--
Kyle Cordes
ebian in and
hopefully get it going.
But, I mention it here on the off chance that there is a simpler or
Puppet-specific workaround possible.
--
Kyle Cordes
http://kylecordes.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed t
, so I suspect there is more to do to get it working smoothly.
If it turns out to be too much... I'll upgrade the boxes instead.
--
Kyle Cordes
http://kylecordes.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Grou
versions
... because killing servers by filling /var, is not a good path to
popularity :-)
--
Kyle Cordes
http://kylecordes.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to
Kyle Cordes wrote:
> Apparently, puppetd tries quite vigorously to connect. It generated
> 10GB of syslog and daemon.log overnight, full of this:
> Feb 26 07:45:10 tr11 puppetd[14683]: : Certificate retrieval failed:
> Could not connect to puppet on port 8140
A more enlightene
opment experience, to find that given the existence of
such a capability, that someone would set it as the *default*.
By the way, how do you install puppetd, on Deb systems?
a) use the Debian-provided package, then go back and edit the settings
b) make your own package
c) some oth
wn package
>
> I definitely recommend this route over all the others. We maintain our
This is the path I'm on. My comment above is just a hope to make life
slightly better for the next person who types "apt-get install puppet"
with Debian or Ubuntu out of the box.
--
Ky
find a way to make it harder
to use my tool badly, while also begging any distro doing that to please
stop.
--
Kyle Cordes
http://kylecordes.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users&
ghtforward to
get proper behavior from an init.d script also - such scripts are
supposed to only return success if the daemon really started.)
I'm using the super-fresh Puppet 0.24.8.
I'd be thrilled to find out that I've missed something obvious, of course.
--
Kyle Cord
Kyle Cordes wrote:
> A machine I am looking to run puppetmaster on, is having a reverse DNS
> problem at the moment (reverse DNS of its IP address fails). Of course
The reverse DNS was indeed broken, but fixing it did not fix this:
> # puppetmasterd --no-daemonize
> /usr/
age -rfakeroot
The difference between this, and what a real maintainer does, is that a
real maintainer has a deep understanding of how the package at hand fits
together with the rest of the Debian world, and makes additional changes
(and performs additional testing etc.) to "Debianize"
r interfaces?
Ugh, I can't reproduce the problem now.
But I'll file the general bug anyway: that puppetmaster / its init
script should not return success until it is fully alive.
--
Kyle Cordes
http://kylecordes.com
--~--~-~--~~~---~--~~
You received this mess
go make it so
myself! :-)
--
Kyle Cordes
http://kylecordes.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To uns
Kyle Cordes wrote:
>> Apply the .diff
Ryan Steele wrote:
> I didn't have to download any diffs. Here's what I did:
> 2. Grab the debian directory for 0.24.7 from git (git clone
> git://git.debian.org/git/pkg-puppet/puppet.git) and put it in the 0.24.7
> s
unleash them on others. Yet.
(Most ideally, the build process for the project itself spits out
packages for the most popular N distro and publishes them as part of
nightly builds or whatever, for those who want to list dangerously.)
--
Kyle Cordes
http:
the same, approximately current versions, on all machines. The versions
in various current and past Ubuntu and Debian releases / backports are
not even close.
--
Kyle Cordes
http://kylecordes.com
--~--~-~--~~~---~--~~
You received this message because you are
to be a fan of Puppet!)
--
Kyle Cordes
http://kylecordes.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe
ty.
I don't have any better idea to propose, though. We all need to make a
living.
--
Kyle Cordes
http://kylecordes.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to
cts that use a
commercial-open-source model, regardless of the licensing, generally end
up with very few outside contributors anyway. I wish it weren't so, but
I suspect it is.
--
Kyle Cordes
http://kylecordes.com
--~--~-~--~~~---~--~~
You received this mess
Related to this, I can tell you from personal experience in commercial
software: support costs can be an enormously drain. The most effective
way to keep them down is with relentless quality improvement: kill bugs,
make features more comprehensible, document, make failure modes gentle,
make erro
ion to
create a positive feedback loop in which more success (users / money /
polish) yields more success.
--
Kyle Cordes
http://kylecordes.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users"
ommercial open source firms, about the
typical customer breakdown (and price point tolerance) among those
categories.
--
Kyle Cordes
http://kylecordes.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Pup
on via a file in /etc/cron.whatever is more genuinely Debianish, and
they'll set it up that way.)
--
Kyle Cordes
http://kylecordes.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users"
er as fast and as hard as it can.
... and in the process, becomes a problem for debian/ubuntu users one
after another. :-(
--
Kyle Cordes
http://kylecordes.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
28 matches
Mail list logo
