Puppet users - Jul 2011 - Best way to create a repo, looking for advice and tips

What is the best way to create a repo?

I like to take baby steps, and test things as I go.

Is this kind of development style possible with puppet?

My hope was to do something like:

Have 1 ec2 vm open that will be my test vm where I will manually install
e.g. mysql or nginx, and then look at what files I will need to work with.

Make modifications to my puppet repo, then commit and apply the changes on a
single VM that will I will just manually apply the repo to.

(I believe this is possible i.e. to apply a repo on a system that isn''t
running a puppet master, please correct me if I am wrong, I swear I read it
somewhere).

Once I have things all setup, I will then test things with a real puppet
master and node(s).

Is this a good approach?  Comments?

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Hi,

Not sure I completely understand what you''re after but i''ll
try to give an answer  (from a red hat perspective).

Yes you can set up a repo that you point puppet clients at. yumrepo allows you
to describe that.

Yes you can use the yum tool createrepo to create a yum repo from a bunch of
rpms.

It is a sound idea to create your own repo for packages when you have change
control obligations or security concerns about package management. 
It''s also really useful when you compile your own packages.

So from that it is pretty easy to achieve. What does get fiddly is dependency
management but if things don''t change often it might be worth the
effort.

If you use EC2 or virtualbox it is neither here nor there really.

Cheers
Den

On 13/07/2011, at 15:19, S Ahmed <sahmed1020@gmail.com> wrote:
> What is the best way to create a repo? 
> 
> I like to take baby steps, and test things as I go.
> 
> Is this kind of development style possible with puppet?
> 
> My hope was to do something like:
> 
> Have 1 ec2 vm open that will be my test vm where I will manually install
e.g. mysql or nginx, and then look at what files I will need to work with.
> 
> Make modifications to my puppet repo, then commit and apply the changes on
a single VM that will I will just manually apply the repo to.
> 
> (I believe this is possible i.e. to apply a repo on a system that
isn''t running a puppet master, please correct me if I am wrong, I swear
I read it somewhere).
> 
> Once I have things all setup, I will then test things with a real puppet
master and node(s).
> 
> Is this a good approach?  Comments?
> -- 
> 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+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.