Simple installation instructions

Are there any simple/complete installation instructions for Foreman out
there? This page:
Installation instructions - Foreman and
the "foreman installer" page that it links to both assume a familiarity
with Puppet that someone new to Foreman and Puppet may not have (like, oh,
me, for instance).

A step-by-step setup guide would be greatly appreciated.

Paul

Hey Paul,
I'm working on such a guide right now. Should have it out by the end of the
week. It'll take the approach of using puppet to install foreman and then
show how to configure Foreman to provision bare metal. I'll then move on
to show how to hook up OpenStack nova with Foreman.

Andy
andy.edmonds.be

··· On Wed, May 30, 2012 at 4:40 PM, Paul Archer wrote:

Are there any simple/complete installation instructions for Foreman out
there? This page:
Installation instructions - Foreman and
the “foreman installer” page that it links to both assume a familiarity
with Puppet that someone new to Foreman and Puppet may not have (like, oh,
me, for instance).

A step-by-step setup guide would be greatly appreciated.

Paul


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/4ZB5_RDFn5wJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

Sounds awesome Andy! I've got vague plans to write up setting up
provisioning on an internal KVM virtual network (say, on a beefy laptop
or dev workstation), but I might hold off until you're done to make
sure I don't repeat you :slight_smile:

Looking forward to it.

··· On Wed 30 May 2012 16:29:21 BST, Andy Edmonds wrote: > Hey Paul, > I'm working on such a guide right now. Should have it out by the end > of the week. It'll take the approach of using puppet to install > foreman and then show how to configure Foreman to provision bare > metal. I'll then move on to show how to hook up OpenStack nova with > Foreman. > > Andy

Hey Greg,
I'm currently simulating the environment in VirtualBox (external NAT'ed
adapter & internal host only network) so I'll also be able to share the
foreman VM as an OVF/OVA for those that want to get down and dirty quickly
with Foreman.

Andy
andy.edmonds.be

··· On Wed, May 30, 2012 at 6:10 PM, Greg Sutcliffe wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed 30 May 2012 16:29:21 BST, Andy Edmonds wrote:

Hey Paul,
I’m working on such a guide right now. Should have it out by the end
of the week. It’ll take the approach of using puppet to install
foreman and then show how to configure Foreman to provision bare
metal. I’ll then move on to show how to hook up OpenStack nova with
Foreman.

Andy

Sounds awesome Andy! I’ve got vague plans to write up setting up
provisioning on an internal KVM virtual network (say, on a beefy laptop
or dev workstation), but I might hold off until you’re done to make
sure I don’t repeat you :slight_smile:

Looking forward to it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/GRm4ACgkQ8O7RN8oK65NlUgCgjEaSt2ubSRi0q5m4qOYImU4S
+I8AoMt7+Pvs2fj+ORCaG1VI7oSq1kv2
=OfpT
-----END PGP SIGNATURE-----


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

Andy, that sounds great. I've got to get up to speed on Foreman pretty
quickly, since I have a dozen servers coming in that need to be provisioned
and managed for a project at work. Frankly, I wasted a couple of days with
Dell's crowbar before I decided I couldn't deal with its installation
process (have to start by installing from an ISO) and some other issues.

If you'd like me to take a look at what you've got now, or read it over
before you release it publicly, I'd be glad to. I'm a pretty decent
proofreader.

Paul

··· On Wednesday, May 30, 2012 10:29:21 AM UTC-5, Andy Edmonds wrote: > > Hey Paul, > I'm working on such a guide right now. Should have it out by the end of > the week. It'll take the approach of using puppet to install foreman and > then show how to configure Foreman to provision bare metal. I'll then move > on to show how to hook up OpenStack nova with Foreman. > > Andy > andy.edmonds.be > >

FYI: the first article in a series of using foreman and puppet is now up:

http://www.cloudcomp.ch/2012/06/automating-the-icclab-part-one/

There is a virtual machine with foreman installed also. Comments
gratefully received!

Andy

··· On Thursday, 31 May 2012 17:18:08 UTC+2, Paul Archer wrote: > > > > On Wednesday, May 30, 2012 10:29:21 AM UTC-5, Andy Edmonds wrote: >> >> Hey Paul, >> I'm working on such a guide right now. Should have it out by the end of >> the week. It'll take the approach of using puppet to install foreman and >> then show how to configure Foreman to provision bare metal. I'll then move >> on to show how to hook up OpenStack nova with Foreman. >> >> Andy >> andy.edmonds.be >> >> > Andy, that sounds great. I've got to get up to speed on Foreman pretty > quickly, since I have a dozen servers coming in that need to be provisioned > and managed for a project at work. Frankly, I wasted a couple of days with > Dell's crowbar before I decided I couldn't deal with its installation > process (have to start by installing from an ISO) and some other issues. > > If you'd like me to take a look at what you've got now, or read it over > before you release it publicly, I'd be glad to. I'm a pretty decent > proofreader. > > Paul >

I should also note that in the future, I'll work on the installation using
veewee and vagrant so that setting up a dev/eval environment will be,
hopefully, the execution of one command :slight_smile:

··· On Thursday, 21 June 2012 12:04:28 UTC+2, Andy Edmonds wrote: > > FYI: the first article in a series of using foreman and puppet is now up: > > http://www.cloudcomp.ch/2012/06/automating-the-icclab-part-one/ > > There is a virtual machine with foreman installed also. Comments > gratefully received! > > Andy > > On Thursday, 31 May 2012 17:18:08 UTC+2, Paul Archer wrote: >> >> >> >> On Wednesday, May 30, 2012 10:29:21 AM UTC-5, Andy Edmonds wrote: >>> >>> Hey Paul, >>> I'm working on such a guide right now. Should have it out by the end of >>> the week. It'll take the approach of using puppet to install foreman and >>> then show how to configure Foreman to provision bare metal. I'll then move >>> on to show how to hook up OpenStack nova with Foreman. >>> >>> Andy >>> andy.edmonds.be >>> >>> >> Andy, that sounds great. I've got to get up to speed on Foreman pretty >> quickly, since I have a dozen servers coming in that need to be provisioned >> and managed for a project at work. Frankly, I wasted a couple of days with >> Dell's crowbar before I decided I couldn't deal with its installation >> process (have to start by installing from an ISO) and some other issues. >> >> If you'd like me to take a look at what you've got now, or read it over >> before you release it publicly, I'd be glad to. I'm a pretty decent >> proofreader. >> >> Paul >> >

> FYI: the first article in a series of using foreman and puppet is now up:
>
> http://www.cloudcomp.ch/2012/06/automating-the-icclab-part-one/
>
> There is a virtual machine with foreman installed also. Comments
> gratefully received!

Looks great!

Some comments (Maybe nits, but your instructions are very detailed, so
I figured you'd appreciate them):

  1. I prefer to run apt-get dist-upgrade on new servers, after the
    first update. (I believe this is a fairly common best practice.) "The
    same as upgrade, except adds the "smart upgrade" checkbox. It tells
    APT to use "smart" conflict resolution system, and it will attempt to
    upgrade the most important packages at the expense of less important
    ones if necessary. It also will install the latest bugfix kernel."
  2. I like to make sure the time on new machines is good (We use NTP,
    but perhaps you don't need to because of virtualization?)
  3. You don't set a hostname, perhaps that is an unspoken assumption?
  4. I know it's a little late in the game, but I'd probably focus on
    12.04 (Precise Pangolin), since it is an LTS release?
··· On Thu, Jun 21, 2012 at 6:04 AM, Andy Edmonds wrote:

Andy

On Thursday, 31 May 2012 17:18:08 UTC+2, Paul Archer wrote:

On Wednesday, May 30, 2012 10:29:21 AM UTC-5, Andy Edmonds wrote:

Hey Paul,
I’m working on such a guide right now. Should have it out by the end of
the week. It’ll take the approach of using puppet to install foreman and
then show how to configure Foreman to provision bare metal. I’ll then move
on to show how to hook up OpenStack nova with Foreman.

Andy
andy.edmonds.be

Andy, that sounds great. I’ve got to get up to speed on Foreman pretty
quickly, since I have a dozen servers coming in that need to be provisioned
and managed for a project at work. Frankly, I wasted a couple of days with
Dell’s crowbar before I decided I couldn’t deal with its installation
process (have to start by installing from an ISO) and some other issues.

If you’d like me to take a look at what you’ve got now, or read it over
before you release it publicly, I’d be glad to. I’m a pretty decent
proofreader.

Paul


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/VO17EmKtjjUJ.

To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

great stuff! thanks

a few comments:

  • which db migration schema issues with u12? :slight_smile: - I hope we fixed them all
  • all of the manifests issues you descripe, would you mind adding them to
    the issue tracker / or simply use the edit button on github to submit the
    fix?
  • ovirt /ec2 is already done :slight_smile:

> I should also note that in the future, I'll work on the installation using
> veewee and vagrant so that setting up a dev/eval environment will be,
> hopefully, the execution of one command :slight_smile:

great stuff keep it coming,

thanks,
Ohad

··· On Thu, Jun 21, 2012 at 1:05 PM, Andy Edmonds wrote:

On Thursday, 21 June 2012 12:04:28 UTC+2, Andy Edmonds wrote:

FYI: the first article in a series of using foreman and puppet is now up:

http://www.cloudcomp.ch/2012/**06/automating-the-icclab-part-**one/http://www.cloudcomp.ch/2012/06/automating-the-icclab-part-one/

There is a virtual machine with foreman installed also. Comments
gratefully received!

Andy

On Thursday, 31 May 2012 17:18:08 UTC+2, Paul Archer wrote:

On Wednesday, May 30, 2012 10:29:21 AM UTC-5, Andy Edmonds wrote:

Hey Paul,
I’m working on such a guide right now. Should have it out by the end of
the week. It’ll take the approach of using puppet to install foreman and
then show how to configure Foreman to provision bare metal. I’ll then move
on to show how to hook up OpenStack nova with Foreman.

Andy
andy.edmonds.be

Andy, that sounds great. I’ve got to get up to speed on Foreman pretty
quickly, since I have a dozen servers coming in that need to be provisioned
and managed for a project at work. Frankly, I wasted a couple of days with
Dell’s crowbar before I decided I couldn’t deal with its installation
process (have to start by installing from an ISO) and some other issues.

If you’d like me to take a look at what you’ve got now, or read it over
before you release it publicly, I’d be glad to. I’m a pretty decent
proofreader.

Paul


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/jbLgjTWiqh4J.

To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

Great work, and good comments! I'll add my 0.02 $currency here - the
time must be right for the puppet certificates to function correctly.
My Debian post-install contains:

apt-get -y install ntp
ntpdate -b pool.ntp.org

That way, the time is set right for the certificate at install time,
but no long running daemon is set up. If I do want NTP, puppet will
already have a class for that :slight_smile:

Cheers,
Greg

··· On 22/06/12 02:46, Brian Gupta wrote: > 2) I like to make sure the time on new machines is good (We use > NTP, but perhaps you don't need to because of virtualization?)

Thanks for the pointers Brian and yes, most appreciated! I'll make the
changes to the article to reflect what you've noted here.
Bingo on NTP, in fact I later stumbled onto the time synchronisation issues
with puppet
Ah yes - hostname is an unspoken assumption. I'll add details regarding
that.
Yep - initially I wanted 12.04 LTS but I was bitten by issues related to
bug 1481. I know from playing with foreman 0.5 (now 1.0RC1) that these
issues do not occur so another +1 for Foreman 1.0! w00t! :slight_smile:

Andy
andy.edmonds.be

··· On Fri, Jun 22, 2012 at 3:46 AM, Brian Gupta wrote:

On Thu, Jun 21, 2012 at 6:04 AM, Andy Edmonds andy.edmonds@gmail.com > wrote:

FYI: the first article in a series of using foreman and puppet is now up:

http://www.cloudcomp.ch/2012/06/automating-the-icclab-part-one/

There is a virtual machine with foreman installed also. Comments
gratefully received!

Looks great!

Some comments (Maybe nits, but your instructions are very detailed, so
I figured you’d appreciate them):

  1. I prefer to run apt-get dist-upgrade on new servers, after the
    first update. (I believe this is a fairly common best practice.) “The
    same as upgrade, except adds the “smart upgrade” checkbox. It tells
    APT to use “smart” conflict resolution system, and it will attempt to
    upgrade the most important packages at the expense of less important
    ones if necessary. It also will install the latest bugfix kernel.”
  2. I like to make sure the time on new machines is good (We use NTP,
    but perhaps you don’t need to because of virtualization?)
  3. You don’t set a hostname, perhaps that is an unspoken assumption?
  4. I know it’s a little late in the game, but I’d probably focus on
    12.04 (Precise Pangolin), since it is an LTS release?

Andy

On Thursday, 31 May 2012 17:18:08 UTC+2, Paul Archer wrote:

On Wednesday, May 30, 2012 10:29:21 AM UTC-5, Andy Edmonds wrote:

Hey Paul,
I’m working on such a guide right now. Should have it out by the end of
the week. It’ll take the approach of using puppet to install foreman
and

then show how to configure Foreman to provision bare metal. I’ll then
move

on to show how to hook up OpenStack nova with Foreman.

Andy
andy.edmonds.be

Andy, that sounds great. I’ve got to get up to speed on Foreman pretty
quickly, since I have a dozen servers coming in that need to be
provisioned

and managed for a project at work. Frankly, I wasted a couple of days
with

Dell’s crowbar before I decided I couldn’t deal with its installation
process (have to start by installing from an ISO) and some other issues.

If you’d like me to take a look at what you’ve got now, or read it over
before you release it publicly, I’d be glad to. I’m a pretty decent
proofreader.

Paul


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/VO17EmKtjjUJ.

To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

Thanks for the feedback Ohad, much appreciated!

  • DB migration issues: when installing plain Foreman 0.4.2 on 12.04 I
    ran into the same issues as was listed in bug #1481. I had also installed
  • Fixes: I'll send pull requests to the relevant manifest owners - I
    think most belong to Greg
  • oVirt/EC2: I'll update the article to reflect

Cheers!

Andy
andy.edmonds.be

> great stuff! thanks
>
> a few comments:
> - which db migration schema issues with u12? :slight_smile: - I hope we fixed them all
> - all of the manifests issues you descripe, would you mind adding them to
> the issue tracker / or simply use the edit button on github to submit the
> fix?
> - ovirt /ec2 is already done :slight_smile:
>
>>
>> I should also note that in the future, I'll work on the installation
using
>> veewee and vagrant so that setting up a dev/eval environment will be,
>> hopefully, the execution of one command :slight_smile:
>
>
> great stuff keep it coming,
>
> thanks,
> Ohad
>>
>>
>>
>>>
>>> FYI: the first article in a series of using foreman and puppet is now
up:
>>>
>>> http://www.cloudcomp.ch/2012/06/automating-the-icclab-part-one/
>>>
>>> There is a virtual machine with foreman installed also. Comments
>>> gratefully received!
>>>
>>> Andy
>>>
>>>>
>>>>
>>>>
>>>>>
>>>>> Hey Paul,
>>>>> I'm working on such a guide right now. Should have it out by the end
of
>>>>> the week. It'll take the approach of using puppet to install foreman
and
>>>>> then show how to configure Foreman to provision bare metal. I'll
then move
>>>>> on to show how to hook up OpenStack nova with Foreman.
>>>>>
>>>>> Andy
>>>>> andy.edmonds.be
>>>>>
>>>>
>>>> Andy, that sounds great. I've got to get up to speed on Foreman pretty
>>>> quickly, since I have a dozen servers coming in that need to be
provisioned
>>>> and managed for a project at work. Frankly, I wasted a couple of days
with
>>>> Dell's crowbar before I decided I couldn't deal with its installation
>>>> process (have to start by installing from an ISO) and some other
issues.

··· On Thu, Jun 21, 2012 at 1:36 PM, Ohad Levy wrote: > On Thu, Jun 21, 2012 at 1:05 PM, Andy Edmonds > wrote: >> On Thursday, 21 June 2012 12:04:28 UTC+2, Andy Edmonds wrote: >>> On Thursday, 31 May 2012 17:18:08 UTC+2, Paul Archer wrote: >>>> On Wednesday, May 30, 2012 10:29:21 AM UTC-5, Andy Edmonds wrote: >>>> >>>> If you'd like me to take a look at what you've got now, or read it over >>>> before you release it publicly, I'd be glad to. I'm a pretty decent >>>> proofreader. >>>> >>>> Paul >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/foreman-users/-/jbLgjTWiqh4J. >> >> To post to this group, send email to foreman-users@googlegroups.com. >> To unsubscribe from this group, send email to >> foreman-users+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/foreman-users?hl=en. > > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To post to this group, send email to foreman-users@googlegroups.com. > To unsubscribe from this group, send email to > foreman-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/foreman-users?hl=en.

Super! Thanks Greg! I'll be adding NTP to the whole mix :slight_smile:
By the way: as Ohad suggested I'll fire across the fixes that I have should
you wish to merge them into the various modules you have.

Andy
andy.edmonds.be

··· On Fri, Jun 22, 2012 at 11:55 AM, Greg Sutcliffe wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 22/06/12 02:46, Brian Gupta wrote:

  1. I like to make sure the time on new machines is good (We use
    NTP, but perhaps you don’t need to because of virtualization?)

Great work, and good comments! I’ll add my 0.02 $currency here - the
time must be right for the puppet certificates to function correctly.
My Debian post-install contains:

apt-get -y install ntp
ntpdate -b pool.ntp.org

That way, the time is set right for the certificate at install time,
but no long running daemon is set up. If I do want NTP, puppet will
already have a class for that :slight_smile:

Cheers,
Greg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/kQRYACgkQ8O7RN8oK65NVSwCdEnlAnQPj4iZdZFtPV1cntyzf
YcIAnijIGrjDxx8n8vv0ex05zJfw3Rh2
=cxeg
-----END PGP SIGNATURE-----


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

I've now made the suggested edits and issued pull requests. The only
outstanding issue is the issue related with Augeas. The issue related to
DHCP is now resolved by the updated DHCP module.

Andy
andy.edmonds.be

··· On Fri, Jun 22, 2012 at 12:55 PM, Andy Edmonds wrote:

Super! Thanks Greg! I’ll be adding NTP to the whole mix :slight_smile:
By the way: as Ohad suggested I’ll fire across the fixes that I have
should you wish to merge them into the various modules you have.

Andy
andy.edmonds.be

On Fri, Jun 22, 2012 at 11:55 AM, Greg Sutcliffe gsutcliffe@ibahn.comwrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 22/06/12 02:46, Brian Gupta wrote:

  1. I like to make sure the time on new machines is good (We use
    NTP, but perhaps you don’t need to because of virtualization?)

Great work, and good comments! I’ll add my 0.02 $currency here - the
time must be right for the puppet certificates to function correctly.
My Debian post-install contains:

apt-get -y install ntp
ntpdate -b pool.ntp.org

That way, the time is set right for the certificate at install time,
but no long running daemon is set up. If I do want NTP, puppet will
already have a class for that :slight_smile:

Cheers,
Greg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/kQRYACgkQ8O7RN8oK65NVSwCdEnlAnQPj4iZdZFtPV1cntyzf
YcIAnijIGrjDxx8n8vv0ex05zJfw3Rh2
=cxeg
-----END PGP SIGNATURE-----


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

I have a patch lying around somewhere which I wrote for Archlinux,
where Augeas support is ropey - it swaps the Augeas approach for a file
in sudoers.d. I'll see if I can get it added for you…

Greg

··· On Mon 25 Jun 2012 12:47:21 BST, Andy Edmonds wrote: > I've now made the suggested edits and issued pull requests. The only > outstanding issue is the issue related with Augeas. The issue related > to DHCP is now resolved by the updated DHCP module.

Yep that was the approach I used - but hacked it in. I might have time
this week to codify it.

Andy

··· On 25 Jun 2012, at 14:24, Greg Sutcliffe wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon 25 Jun 2012 12:47:21 BST, Andy Edmonds wrote:

I’ve now made the suggested edits and issued pull requests. The only
outstanding issue is the issue related with Augeas. The issue related
to DHCP is now resolved by the updated DHCP module.

I have a patch lying around somewhere which I wrote for Archlinux,
where Augeas support is ropey - it swaps the Augeas approach for a file
in sudoers.d. I’ll see if I can get it added for you…

Greg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/oWGcACgkQ8O7RN8oK65Nr5wCeJwxATlv+KUXSKcLYtI72kaHc
kakAn2BaVS10yXF9nJLfC8N0Ix6SQCb0
=NH/0
-----END PGP SIGNATURE-----


You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

Sudoers.d support was added somewhere around 7.2 - is that new enough
for us to make a .d style the default with the option to switch to
augeas on older boxen?

Greg

··· On 25/06/12 14:23, Andy Edmonds wrote: > Yep that was the approach I used - but hacked it in. I might have > time this week to codify it. > > Andy

If the fallback of Augeas was available then that would sounds like a good
case of covering all bases.

Andy
andy.edmonds.be

··· On Mon, Jun 25, 2012 at 3:28 PM, Greg Sutcliffe wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 25/06/12 14:23, Andy Edmonds wrote:

Yep that was the approach I used - but hacked it in. I might have
time this week to codify it.

Andy

Sudoers.d support was added somewhere around 7.2 - is that new enough
for us to make a .d style the default with the option to switch to
augeas on older boxen?

Greg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/oZ5kACgkQ8O7RN8oK65MbAACfVZbCSU2Hb7bGgDA84QFnn7QR
g1MAoLK6oHPRRbUKw79FtgjesdIX/jYg
=SYEQ
-----END PGP SIGNATURE-----


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

I've merged all the open pullreqs (thanks, both of you!) and tested on
Debian, Ubuntu and Centos, all seems fine. It's now in master of
foreman-installer. I'll craft up an augeas patch later this week if
you don't beat me to it :slight_smile:

Greg

··· On 26 June 2012 08:57, Andy Edmonds wrote: > If the fallback of Augeas was available then that would sounds like a good > case of covering all bases. > > Andy > andy.edmonds.be

Awesome! Thanks Greg! :slight_smile:

Andy
andy.edmonds.be

··· On Wed, Jun 27, 2012 at 1:38 AM, Greg Sutcliffe wrote:

On 26 June 2012 08:57, Andy Edmonds andy@edmonds.be wrote:

If the fallback of Augeas was available then that would sounds like a
good
case of covering all bases.

Andy
andy.edmonds.be

I’ve merged all the open pullreqs (thanks, both of you!) and tested on
Debian, Ubuntu and Centos, all seems fine. It’s now in master of
foreman-installer. I’ll craft up an augeas patch later this week if
you don’t beat me to it :slight_smile:

Greg


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.