On Tue, Mar 05, 2013 at 10:53:47AM -0600, Victor Lowther wrote:
> On Tue, Mar 5, 2013 at 2:48 AM, Ralf Haferkamp <[email protected]> wrote:
> > Hi,
> >
> > On Mon, Mar 04, 2013 at 09:13:42AM -0600, Victor Lowther wrote:
> >> On Mon, Mar 4, 2013 at 7:20 AM, Ralf Haferkamp <[email protected]> wrote:
> >> > Hi,
> >> >
> >> > currenlty the provisioner barclamps sets up a polipo instance on the
> >> > admin node
> >> > to act as a proxy for the client nodes (AFAIK to be able to access
> >> > remote package
> >> > repositories). Is there any specific reason why polipo was choosen for
> >> > this?
> >> > Instead of e.g. choosing apache2?
> >>
> >> Mostly because I knew how to whip up a quick little recipe for polipo,
> >> and I had never tried to use apache2 for that purpose.
> > Using the apache2 cookbook we already have in the chef barclamp this turned
> > out
> > to be pretty easy (at least easier then the effort it would take to spin
> > and
> > maintain working packages for polipo on openSUSE):
> >
> > https://github.com/rhafer/barclamp-provisioner/commit/398de3b6c54fc4ed063574a75e8f9545a810508a
> >
> > This sets up an apache2 instance on the provisioner to take over the tasks
> > of
> > the proxy and the provisioner webserver (nginx on ubuntu AFAIAK). It is
> > currently made SUSE only (but only because I couldn't test on other
> > systems).
> > It should be pretty straightforward to use this also on Ubuntu and Redhat
> > systems.
>
> ok. Set up a pull request, to swap out polipo for using apache as our
> proxy, and I will test it on Ubuntu.
Find it here:
https://github.com/crowbar/barclamp-provisioner/pull/107
thanks,
Ralf
_______________________________________________
Crowbar mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/
