This is great... I see more options now! Thanks for the advice, really
helpful
On Friday, June 6, 2014 11:17:59 AM UTC+1, Ken Barber wrote:
>
> And another idea that I've seen people use is to install the Brightbox
> PPA packages for Ruby:
>
> http://brightbox.com/docs/ruby/ubuntu/
>
> On Fri,
r the rest of our ruby apps and
that's why I thought on using it , but I see the cons as well.
Thanks for all your help!
On Friday, June 6, 2014 11:05:15 AM UTC+1, JuanBrein wrote:
>
> I've always used distribution packages, but now I need to use
> puppet_decrypt which
flexibility to be installed along puppet as gem on
distributions where there are no packages available.
On Thursday, June 5, 2014 9:56:34 PM UTC+1, jcbollinger wrote:
>
>
>
> On Thursday, June 5, 2014 10:37:46 AM UTC-5, JuanBrein wrote:
>>
>> I see, it is a gap in the
our source tree, that you can build a gem
> from: https://github.com/puppetlabs/puppetdb/blob/master/Gemfile.
>
> ken.
>
> On Thu, Jun 5, 2014 at 1:09 PM, JuanBrein > wrote:
> > HI guys,
> > On Ubuntu 12.04 using ruby 2.0 and puppet 3.3.2 through gem installati
HI guys,
On Ubuntu 12.04 using ruby 2.0 and puppet 3.3.2 through gem installation I
can't find puppetdb-terminus . There is a 1.0 version but is empty
available in rubygems.Does anybody know if there is an easy way to add this
files to my puppet installation rather than just copy them over from
Today looking for a solution to this I came up with a nice solution. I know
this thread is old but I'm posting it just in case is useful for somebody:
on hiera.yaml:
:hierarchy:
- 'host/%{::domain}/%{::hostname}'
- 'domain/%{::domain}'
- 'role/%{system_role}'
- 'common'
on site.pp
node
Today looking for a solution to this I came up with a nice solution. I know
this is old but I'm posting it just in case is useful for somebody:
on hiera.yaml:
:hierarchy:
- 'host/%{::domain}/%{::hostname}'
- 'domain/%{::domain}'
- 'role/%{system_role}'
- 'common'
on site.pp
node defaul
Have you read Continuous Delivery from Jez Humble?
Is a great starting point covering main aspects. Look in youtube as well,
there are plenty of videos from people implementing continuous delivery.
Technology wise it is so wide that is difficult to find a single recipe. If
you detail a bit mor
Interesting... All your comments are very valuable and I definitely see
some differences
I'll test some of your suggestions and see how it goes.
Thanks for taking the time to answer!
Cheers!
Juan
On Monday, February 10, 2014 7:15:28 PM UTC, Ramin K wrote:
>
> On 2/9/2014 11:37 PM
articularly if
it'll never ever conflict with another module. Also a good place to pull
in very simple modules. I'm not a fan of breaking things up into more
specific subclasses within a profile::class.
On Monday, February 10, 2014 6:48:55 AM UTC, Ramin K wrote:
>
> On 2/9/2
service httpd graceful will help. I would highly recommend you to have a
dev / prd environment for your puppetmaster as well. Vagrant is very
helpful for that. Having auto provisioned puppet masters is really helpful
as it allows you to test new puppet master upgrades and configuration
changes.
I've been using puppet on different companies and implementing the roles /
profile pattern on some of them.
In theory the patter works very well but in practice I usually face
challenges that I sort out implementing my own designs / solutions. I would
like to know how you guys deal with that
I would highly suggest you to use VIM+plugins
Powerful as any other graphical IDE plus you can run it in any console plus
run on any OS plus free :-)
On Tuesday, December 24, 2013 11:21:48 PM UTC, Stuart Cracraft wrote:
>
> Hi,
>
> Is there a plain-text visual debugger ide for Linux for Ruby any
Have you seen such a problems or is just an assumption? I've worked on a
few puppet implementations and changing puppet master manifests on the go
has never been an issue.
I might be misunderstanding your question, can you develop more around your
deployment process?
On Tuesday, November 19, 2
You can use inline_template("<%= var = "your ruby code here" %>")
Cheers
On Monday, November 4, 2013 2:23:34 PM UTC, jcbollinger wrote:
>
>
>
> On Saturday, November 2, 2013 5:03:13 PM UTC-5, ytmp123 wrote:
>>
>> Hi guys,
>>
>> I've two questions:
>> 1. How can I execute normal Ruby-Code in a
Hi Community,
As part of a small project I'm working on an automated script to help me
develop puppet modules. The tool is called "puppetize" and is available as
a gem and on github:
https://github.com/BreinsNet/puppetize
The goal is to easy puppet module development process and to help on
st
Just my 2 cents... is better if you use stdlib -> concat function for
/etc/hosts... you can have a default section for all the hosts and a
customized one for specific cases. You avoid conflicts as well.
Cheers
On Monday, October 14, 2013 4:28:39 PM UTC+1, mike wrote:
>
> Hello,
> I fix "the pro
Hi Gonzalo,
First of all you don't need puppetdb to use exported resources. A simple
mysql database will do it, even sqlite works, not recommended though.
Specifically what you need is "stored configs" configured in your puppet
master. The problem with exported resources is that sometimes they
This could be related to a bug in puppet, even though the dependency is
defined between classes, the resources within the classes float and get
executed in a different order. Take a look at the "anchor" pattern in the
puppetlabs documentation.
Juan
On Sunday, September 15, 2013 6:14:17 AM UTC
Not hard at all...
just use "file" resource to deploy the file and then "exec" to execute it:
file{ "/path/to/my/script.sh"
source => "puppet:///modules/${module_name}/script.sh",
mode => 755,
} ~>
exec { "/path/to/my/script.sh"
refreshonly => true,
}
The important bit here is the ~> . T
Hi Neanudorn
Is very difficult... you could try but if you really want to do it properly
is going to take you a lot of time for all the modules. The main problem I
foresee is that adding things is easy, but removing them is hard as you
need to identify each of the objects that were added. Ie w
Hi Faifel,
this is the way I like to organize my modues:
modules/$environment/$type
where $environment usually is one of dev qa stg and prd
and type is one of base common and roles.
So in a typical configuration it would be something like:
modules/dev/common
modules/dev/base
modules/dev/ro
22 matches
Mail list logo
