[Puppet Users] Re: Is there a way to deploy our configuration to agent.
On Wednesday, July 29, 2015 at 8:52:14 AM UTC-5, Ayyanar wrote:
On Wednesday, 29 July 2015 17:59:02 UTC+5:30, Brendan Murtagh wrote:
Please go into more detail. Are you referring to changing the Puppet
agent config on your nodes or something else?
1. I have two agent ip-10-109-189-241.ec2, ip-10-233-92-172.ec2.internal
node.
2. I want to deploy my configuration to the agents in master itself.
3. I don't want to login to agent and fetch the configuration.
example:
node ['ip-10-109-189-241.ec2.internal' ip-10-233-92-172.ec2.internal] {
include directory-creation
}
I want to deploy directory-creation class file to agents.
Neither Puppet nor any other software running on a given machine can effect
changes to a different machine without some form of cooperation for the
target machine.
The longstanding default approach to this is to configure each machine to
run the agent on a schedule, either via the agent's built-in scheduler
(active when running the agent in daemon mode) or via an external scheduler
such as cron. The traditional run interval is 30 minutes, but there is
nothing special about that particular timing.
If you want to run the agent *on demand* on your target machines, but
without logging in to the individual machines, then you're looking for some
form of remote control software. Puppet is not such software, but
PuppetLabs's MCollective can serve in that role, and it has good
integration with Puppet.
John
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/162ef30d-795e-4c88-9f35-9e56d9070575%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] comments on the Type system and some questions
On 2015-30-07 16:36, R.I.Pienaar wrote:
hello,
I've done a few little things with the type system and really like what it
achieves,
was able to find a few bad data items in my hiera data and it saves on a lot of
the
super annoying validation function calls.
The syntax though is pretty difficult to use, consider:
define foo(
Enum[present, absent] $ensure = present,
Optional[String] $ssh_authorized_file = undef,
Optional[String] $email = undef,
Optional[Integer] $uid = undef,
Optional[Integer] $gid = undef,
Variant[Boolean, String] $sudoer= false,
Boolean $setup_shell= false,
Boolean $setup_rbenv= false
) {
So this has a few issues for me:
Reading it, I just don't see the property names now, its become a real effort
to read this.
$ssh_authorized_file Optional[String] = undef,
seems better for this use case to me and this is probably going to be the most
often used use case.
This gets much worse when we involve more complex type definitions, I can't
imagine
ever using a full on Struct definition here for example it would render it
entirely
unreadable and be impossible to maintain
How would you ever fit this into a param declaration and maintain readability:
Struct[{mode= Enum[read, write, update],
path= Optional[String[1]],
NotUndef[owner] = Optional[String[1]]}]
This leads to my 2nd question, I couldn't find a way to make my own abstract
types.
Consider this hypothetical with made up syntax and all:
site.pp:
typedef MyData Struct[{mode = Enum[read, write, update],
path= Optional[String[1]],
NotUndef[owner] = Optional[String[1]]}]
foo.pp:
define foo(Mydata $data) {
this would improve matters a whole lot. Does a typedef like feature exist? I
couldn't
find anything and tried a few things but failed
The intent is to add typedef like this:
type MyData = Struct[{ }]
Don't think we will change the order of type / param - too late to make
that change, and would be different from most other languages where type
declaration comes first.
- henrik
---
R.I.Pienaar
--
Visit my Blog Puppet on the Edge
http://puppet-on-the-edge.blogspot.se/
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/mpfu0c%24qph%241%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: rpm installation ordering question and yum repos
On Friday, July 24, 2015 at 11:30:34 AM UTC-5, Vince Skahan wrote:
Like many sites, we have internal yum repos that contain our
internally-created rpms, as well as some other repos that are internal
mirrors of upstream sites (centos updates, etc.). We're running into an
ordering issue that I'm looking for what the current suggested best
practice is
We cooked up a 'my-mirrors-release' rpm notionally like 'epel-release' or
'centos-release' etc. that you'd commonly see. Contents are the
/etc/yum.repos.d files for the various internal repos, and some /etc/pki
gpg keys for the repos that have signed rpms. Typical yum repo stuff.
Question is how to ensure that our local mirrors-release rpm installs
before any other rpms that would need to have the repo defined in order to
find the rpms therein. In other words we want this rpm installed first.
Like 'really' first
We're trying to avoid having to specify having the my-mirrors-release rpm
be installed before rpmXYZ every time we specify a rpm to be installed in
all the places we might want to specify a package be installed. Looking
for suggestions for a current best practice (assume puppet 3.8 but if
there's 4.0 magic, that would be good to know)
One solution we came up with is the bottom line in the code snippet
below. Is this today's best practice for this kind of thing ? Again -
we're trying to ensure this 'one' rpm is there before installing later rpms
that would depend on it. Suggestions ?
class myprofiles::my_mirrors { # disable upstream repos yumrepo {
'updates': enabled = 0, } # enable our mirrors yumrepo {
'my-repos': baseurl =
'http://mirrors.example.com/my-mirrors-release/el6', enabled = 1, }
package { 'my-mirrors-release':provider = yum,ensure = latest,
require = Yumrepo['my-repos'], } # Ensure our repositories are installed
before any other package. # (Otherwise the package may not be found.)
Package| title == 'my-mirrors-release' | - Package| title !=
'my-mirrors-release' |
}
Your approach is precisely what I would have recommended for the problem
you present.
Although run stages can sometimes be put to good use, they also can get you
into trouble. I am no fan of them. In this particular case, the approach
you've chosen is no more complex to express in your manifests than one
involving run stages would be, and it is both more localized and lighter
weight.
John
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/03ff01b4-2ae0-4112-a4a1-ba4133b60a10%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Errors for puppet-enterprrise-installer in ubuntu 12.04
My computer is Ubuntu 12.04.5 LTS 1. downloaded puppet-enterprise-3.8.1-ubuntu-12.04-amd64.tar.gz 2. tar -xf 3. sudo ./puppet-enterprrise-installer But it fails with the errors: W: Failed to fetch http://apt.puppetlabs.com/dists/precise/PC1/source/Sources 403 Forbidden W: Failed to fetch http://apt.puppetlabs.com/dists/precise/PC1/binary-amd64/Packages 403 Forbidden W: Failed to fetch http://apt.puppetlabs.com/dists/precise/PC1/binary-i386/Packages 403 Forbidden -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/17feb6aa-8b98-41d0-8b34-47e8b7690968%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. install_log.lastrun.igl0665u.cw01.contiwan.com.log Description: Binary data
[Puppet Users] Nigeria Puppet User Group - Meetup Link
Dear All, Below is the link to the Nigeria Puppet User Group http://www.meetup.com/Nigeria-Puppet-User-Group/ -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6bbe2efd-f131-4f42-949f-5ff992b13c1f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Nigeria Puppet User Group
Dear All, I have started the Nigeria Puppet User Group. The first meeting will be in Lagos, Nigeria and to be set for a date in September 2015. Regards -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/37622cf3-e450-457f-9f74-2745e356ee4e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Lucid leaving apt.puppetlabs.com
We had been talking about this internally for a bit as well. Basically, we have a couple things we'd like to do. 1. In the Puppet Collections Paradigm, we are no longer removing items. 2. In the old production repos, we will still be removing items (to eventually phase those repos out) 3. As far as an archives server go, we all like the idea. We also haven't had time to do the work yet. I'm not sure when we'll get to it. I'm looking into a few options. Mike -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAMto7L%2B9YfSGKoWudAoK%3DiLv6OuecamVMhZ9OzX%3DnTdCvmY4yQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Errors for puppet-enterprrise-installer in ubuntu 12.04
On Fri, Jul 31, 2015 at 12:43 AM, patrick huang patrickh1...@gmail.com wrote: My computer is Ubuntu 12.04.5 LTS 1. downloaded puppet-enterprise-3.8.1-ubuntu-12.04-amd64.tar.gz 2. tar -xf 3. sudo ./puppet-enterprrise-installer But it fails with the errors: W: Failed to fetch http://apt.puppetlabs.com/dists/precise/PC1/source/Sources 403 Forbidden W: Failed to fetch http://apt.puppetlabs.com/dists/precise/PC1/binary-amd64/Packages 403 Forbidden W: Failed to fetch http://apt.puppetlabs.com/dists/precise/PC1/binary-i386/Packages 403 Forbidden Hmm, this is very interesting. My first thought is that you have enabled the PC1 repos, but something went wrong. The installer script runs 'apt-get update -q -y' after it adds the puppet enterprise key. It's with that call that you're seeing the failures. I have no idea why you're getting a 403 though. What happens when you manually run 'apt-get update -q -y'? Do you get the same error? How did you initially enable the PC1 repo? Did you download and install the release package from apt.puppetlabs.com? Also, we don't support the PC1 repos with PE 3.8.1. You will likely run into more problems once you get past these repo issues. I would suggest either installing a 2015.2.0 master, or disabling the PC1 repos and installing PE 3.8.1. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/17feb6aa-8b98-41d0-8b34-47e8b7690968%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Melissa Stone Release Engineer, Puppet Labs -- PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9. Register now to take advantage of the Early Bird discount —save $249! -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAHEe_kp%2BpcMihZ9ewNnptp_dRHN-qZ4JG_QWK%3DRb0NhZbp%2BPsw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
