Re: [Puppet Users] puppet over ansible
On 21/07/2012, at 11:20 AM, Brian Gupta wrote: >> On 18/07/2012, at 8:54 AM, Marc Lucke wrote: >> >>> So I'm seeing a lot of hype around Ansible. It seems to be a compelling >>> story. I've looked around and found a lot of stories about why you would >>> use it over puppet, but not puppet over ansible. Can anyone relate >>> personal experiences or point to some interesting reading? > > On Fri, Jul 20, 2012 at 8:11 PM, Marc Lucke wrote: >> … well there you have it. No advantages. Or nobody cares about this better >> system. Or nobody knows :) >> > > Well, I am guessing most of the people on this list haven't heard of > Ansible (until now). (Other than any Orson Scott Card fans.) > > Taking a quick look the high level differences are: > > 1) Userbase/community - Puppet has a much larger userbase and > community. My belief is this is an advantage for puppet. > > 2) Larger number of modules available for use with puppet. > > 2) Ansible uses SSH to connect to the managed hosts. Pros and cons > here. Will let others argue which is "better". > > 3) DSL - Puppet has a Declarative DSL which largely separates the what > from the how. Ansible seems to mix the two in their playbooks. (Much > like Chef, but with Ansible not being Ruby specific.) I prefer a > Declarative DSL, but others may prefer alternate approaches. > > 4) Python vs Ruby - I feel Ruby is more popular in the Devops > community, and find I like the syntax better, but Python is not > necessarily a bad choice. That said, largely as a puppet user, one > doesn't have to deal with Ruby. (Nor does a Absible user have to deal > with writing Python.) This decision would be more important if you > wanted to contribute to one of the projects in question. > > 5) GPL vs Apache - DIfferent strokes for different folks. I actually > prefer GPL licensed software, but many prefer the Apache 2 license. > > 6) Push vs poll. - Ansible pushes configs to hosts where puppet > clients check in to a central server on regular intervals. (My > understanding is that ansible is somehow serverless.) > > 7) External data - Puppet supports the concept of storing ones data > separately from the code. It appears that ansible does not have a > standard method for doing so. > > 8) Built in remote command execution. Puppet relies on mcollective for > this feature, which is additional administrative overhead to setup and > maintain. However, on the flip side, I am certain that mcollective is > much more scalable than ansible. (IE: I am not using a tool that uses > ssh to manage 1000s of servers.) I can't say as a blanket statement > which is better.. If all you are managing is 10 nodes, I could see > simplicity of setup being an advantage. If you need to scale obviously > the scalable solution wins. That said, I would probably prefer to use > the scalable tool in small scenarios, so I don't have to learn two > toolchains. > > 9) Puppet manifests are historically have non-deterministic order > execution, unless dependencies are specifically declared. I think this > is the correct approach as implicit dependency graphs can be > dangerous, and lead to incomplete understanding of one's > configuration. That said, we are all used to scripts that run in > order, so this is definitely a learning curve when folks are new to > puppet. > > 10) Puppet is available in an Enterprise Edition that you can buy from > a known vendor with a full support contract. This gives many companies > warm and fuzzies. The majority of folks would say this is an advantage > for Puppet, however if one wants to be on the FLOSS bleeding edge, and > you don't have any money for software/support anyway, it might just be > a wash. > > All in all I would say that Ansible feels more like a deployment > system with some basic configuration management idioms supported. > (Basically a step from capistrano or fabric towards a full-fledged > cfg-management framework.) I'm also sure I didn't get this all right, > and missed differences, as I have never used Ansible, and quickly > skimmed the docs. > > Cheers, > Brian > > -- > 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 from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > Thanks for the input Brian. I have to say I definitely prefer procedural scripts with a predictable run order, but you can accomplish this with stages. I've yet to refactor my own code so that I can deploy an ecosystem of servers in one go rather than a few runs per server. I like your analogy that Ansible looks like a step above fabric & capistrano - that's the impression I got too. But I haven't used it either. Marc -- You received this message because you are subscribed to the Google Groups "Puppet Users" grou
Re: [Puppet Users] Facter fact length?
Are you sure that exposing a password hash by a fact is a sane thing to do from a security point of view ? Too simple to mont a dictionary attack, isn't ? 2012/7/22, bg : > This is a bit of a leading question, but is there a limitation as far as > length/size of facts on a node? > > I have a need to perform one way sync of user accounts (non-Puppet managed > users) on many pairs of servers. Thus far, it's been done with scripts > from primary -> backup server, and has been problematic. I'd like to create > > a fact that returns user:password_hash pairs, and then ensure those users > are present on the backup server. > I would guess the largest number of users on a node would be ~100. > > Any other creative solutions are appreciated, but keep in mind ldap/nis > aren't valid options. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/WVxoEY4gic8J. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- Inviato dal mio dispositivo mobile -- 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 from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] How to get puppetmaster's base directory into a variable ?
James Glenn ha escrito:
> On Sat, Jul 21, 2012 at 9:36 PM, eduardo wrote:
>
> > Dears all,
> >
> > I need set variable $puppet_base_dir on my prerequisites class with
> > confdir parameter value of puppetmaster. I need the variable to be
> > used as base directory path of a file named myfile, which it's read it
> > in custom function. I'm trying to avoid absolute path '/etc/pupet/
> > files/myfile' , I want to get it from puppetmaster configuration so i
> > can do something like ${puppet_base_dir}/files/myfile .
> >
> > To do it, I create a custom function which have only one line of
> > code :
> >
> > puppet_dir = %x{puppet master --configprint confdir}.chomp
> >
> > I'm thinking might be a dumb solution.
> >
> > Is there a simple way to do it ?.
> >
> >Thanks in advanced.
> >eduardo.
> >
>
> $settings::confdir
> This will have the variable you are looking for.
>
> See
> http://docs.puppetlabs.com/guides/faq.html#are-there-variables-available-other-than-those-provided-by-facter
> and http://docs.puppetlabs.com/references/stable/configuration.html#confdir
>
> Thanks,
> James Glenn
Thanks you very much James. It's exactly.
Regards,
eduardo
--
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 from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Foreman 1.0 released!
Hello, I'm very excited and pleased to share the release of Foreman 1.0 Since the change log is quite extensive, I would simply refer you to the change log [1] and would highly suggest to read it if you are upgrading. About Foreman: Foreman is an opensource management tool, design to help you to manage your infrastructure. Foreman takes over provisioning(bare metal, virtual or in the cloud)[2], interfacing with puppet to configure your servers, and provides an easy to use UI / API to control and review your server state. I'm also very happy to see that Foreman users, contributes (thanks guys!!) and ecosystem is growing, that includes a mobile app [3] and a CLI that was contributed by our community. I'm assuming packages would be available shortly. have fun, Ohad [1] http://theforeman.org/projects/foreman/wiki/ReleaseNotes#Release-Notes-for-10 [2] http://theforeman.org/projects/foreman/wiki/Screencasts [3] http://www.remoteadmin.co -- 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 from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] How can I list classes available on the puppet master?
On Mon, Jul 16, 2012 at 2:57 PM, Kamil Winczek wrote:
> On 12 Jul 12 08:54 -0700, llow...@oreillyauto.com wrote:
> > Is there a way to get a list of all the classes available from the
> puppet
> > master?
> > I have 2 goals for this - one is documentation in a human readable
> form,
> > and the other is potentially importing that data into dashboard.
>
> Hi,
>
> How about simple:
>
> find . -name '*.pp' -exec awk '/^class [a-zA-Z]/ {print $2}' {} \;
>
You can also use foreman Proxy [1] to get that info for you :)
Ohad
[1] - http://theforeman.org/projects/smart-proxy/wiki
[1]
>
> ?
> --
> Kamil Winczek, Gentoo Linux user, post no: 1443
> GG:888677, M:kamil[at]winczek.com, JID:crs[at]jabster.pl
> For a list of all the ways technology has failed to improve
> the quality of life, please press three. - Alice Kahn
>
> --
> 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 from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
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 from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Any one interested attending a puppetcamp in Israel?
Adding a couple more public mailing lists just in case. On Sun, Jul 22, 2012 at 5:37 PM, Oded Ben-Ozer wrote: > We are trying to see how much people are interested so please let me know > if you want to attend and or I know someone else who wants to attend. > > From puppetlabs.com - "Puppet is IT automation software that helps > system administrators manage infrastructure throughout its lifecycle, from > provisioning and configuration to patch management and compliance. Using > Puppet, you can easily automate repetitive tasks, quickly deploy critical > applications, and proactively manage change, scaling from 10s of servers to > 1000s, on-premise or in the cloud." > > Some info on puppetcamp events in other locations : > http://puppetlabs.com/community/puppet-camp/ > > > > > Oded Ben Ozer > > -- 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 from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Stop aptitude package provider from using '-y'
Hi all, I like to use the aptitude provider to install packages -- all my systems are Debian and it's consistent with what I use manually. However, the aptitude provider seems to pass the '-y' option to aptitude, which causes aptitude to simply assume yes for all prompts. I understand that this might be necessary to avoid puppet hanging due to the subprocess prompting, but in some cases aptitude can prompt because of conflicts. In the case of conflicts, I would want puppet to just return an error and let me handle the situation manually. Because sometimes aptitude's first solution to a conflict is very suboptimal. Does anyone know how I can configure this? Cheers, David -- 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 from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] How to delete users from groups ?
Dears all,
I'm trying update user's membership group deleting users from some
groups.
To do it i took exec way doing :
exec { "deluser ${username} ${group}":
I'm thinking might be there is more elegant solution without using
exec type .
Is there another way to do it ?.
Thanks in advanced.
eduardo.
--
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 from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Stop aptitude package provider from using '-y'
I think a better solution would be using preseed files to answer the questions. Is this not an option? Sent via BlackBerry -Original Message- From: David Banks Sender: puppet-users@googlegroups.com Date: Sun, 22 Jul 2012 23:58:01 To: Reply-To: puppet-users@googlegroups.com Subject: [Puppet Users] Stop aptitude package provider from using '-y' Hi all, I like to use the aptitude provider to install packages -- all my systems are Debian and it's consistent with what I use manually. However, the aptitude provider seems to pass the '-y' option to aptitude, which causes aptitude to simply assume yes for all prompts. I understand that this might be necessary to avoid puppet hanging due to the subprocess prompting, but in some cases aptitude can prompt because of conflicts. In the case of conflicts, I would want puppet to just return an error and let me handle the situation manually. Because sometimes aptitude's first solution to a conflict is very suboptimal. Does anyone know how I can configure this? Cheers, David -- 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 from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- 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 from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Updated version of pupmod-concat released to Github
A long overdue update to pupmod-concat has been released to Github at https://github.com/onyxpoint/pupmod-concat. It contains fixes for all outstanding bug reports as well as some additional optimizations and features. Many thanks to all bug reporters and we're going to try to not wait another year before fixing new issues! Thanks, Trevor -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tvaug...@onyxpoint.com -- This account not approved for unencrypted proprietary information -- -- 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 from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Creating Subgroups in Puppet Dashboard
On Fri, 2012-07-13 at 02:06 -0700, Praveen Shivashankar wrote: > Hi All, > > Is there a feasibility for creating subgroups on the Puppet Dashboard? > Basically the requirement is that we have a huge number of VMs running > designated services. Some of VMs having the same service may yet have > different properties configured on them. We are exploring the feasibility > of having these properties managed through puppet. Currently all these VMs > are put into a single group on the Puppet Dashboard and have global > properties configured on the dashboard. > > Can I create a subgroup among these, and configure separate properties so > that when the Agent contacts the master, based on the subgroup it belongs > the corresponding property values are picked up (or else the default > entries are retained)??? Yes, you can. It's quite simple: Create a new group for your sub-group, then in the "Groups" field, enter the name of the parent group. The new subgroup then inherits all of the properties and classes from the parent group, and you can override properties by entering new values for them in the subgroup. You can also override individual properties by setting them on the node directly, in case you have a one-off situation. -- Calvin Walton Blindside Networks http://www.blindsidenetworks.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 from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: How to delete users from groups ?
Hi eduardo,
> Is there another way to do it ?.
>
user { "$username":
ensure => present,
key_membership => inclusive,
groups => ['all', 'groups', 'except', '$group'], # full listing of all
groups $username belongs to
}
or
group { "$group",
ensure => present,
attribute_membership => inclusive,
members => ['all', 'members', 'except', '$username'], # full listing of
all members of $group
}
Cheers,
Paul
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/vByKYwcuRhoJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: RemoteAdmin 0.6 ( Foreman / Puppet Mobile App ) Now in appstores
I am proud to release the next version of Remote Admin version 0.6. The first mobile app for your puppet environment. What is RemoteAdmin you ask? RemoteAdmin is a mobile (Android / iOS) and desktop (Win / Mac) app written in Flex that controls your puppet infrastructure via foreman. For more information visit: http://www.remoteadmin.co Full Feature List HostGroups (Similar to Roles in puppet) -- Create Host Groups -- Assign and remove hosts to hostgroups -- Assign and remove puppet modules from hostgroups Facts -- Fact viewer for entire environment -- Dynamic graphs based on any fact -- Sort facts by hostgroup(s) -- Email facts Certificate Management (Coming back in 0.7) -- Validate certificate requests -- Revoke certificates -- View revoked certificates -- Search for certificates Reports -- View Latest Puppet Generated Reports -- View report metrics as charts -- Drill down into individual report logs to find issues with puppet runs -- Sort reports by recent, eventful and failed categories Hosts -- View Individual Host puppet reports -- Assign or remove puppet modules from host -- View facts for each host Misc -- Create multiple profiles for different datacenters or foreman hosts -- SSL Support (Recommended) -- User Authentication Support (Recommended) -- Clickable Quickview Dashboard Whats New in 0.6: -- Communication Subsystem (native notifications, alerts) -- Support for Ipad 3 -- iOS inspired Theme -- Clickable Dashboard Graph and Fact Graph -- Swipe to view legend (FactViewer) -- Now Open source! (GPLv3) -- Test Client (if you don't have a foreman host yet) Whats Fixed: -- Too many to list Whats Removed: -- Certificates (Will add back in version 0.7) Future Releases (See http://www.remoteadmin.co) for full roadmap: -- Certificates -- Bookmark integration with entire app (Bookmark and group filters) -- Horizontal (large screen) layouts for tablets and Desktop -- IPMI and Mcollective integration -- More Share Buttons (CSV, Screenshot, ...) -- Badge Integration and Notifications when app is in background Note: Remote Admin Version 0.6 only works with the Foreman 1.0 or latest develop branch. Look in the appstores for RemoteAdmin or click the links below -- iOS Version: http://bit.ly/MojULg Android Version: http://bit.ly/NkRR3M Desktop App: http://www.remoteadmin.co/desktop (Install via Web) OSX and Windows Only For more information please visit http://www.remoteadmin.co Corey Osman co...@logicminds.biz Green IT and Datacenter Automation Specialist -- 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 from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
