[Spacewalk-list] Cobbler spacewalk proxy issue

[Charlie Derwent]

Sorry to cash in on your misfortune Doug, but I plan on implementing an
architecture similar to what you're describing and would be interested to
see if you manage to get this to work.

Charlie

On Wed, Aug 17, 2011 at 6:20 PM, Doug Bishop <doug at dougbishop.org> wrote:

> Well my concern is running tftp across multiple sites. Each site lives with
> in its own network connected via an MPLS backbone. Maybe I dont fully
> understand how all of this fits together. I need to pxe boot at each of my
> different locations that has a proxy. Does this mean, all tftp requests will
> need to go to our spacewalk server located at our main site? Or can the
> proxy handle the PXE for me, if so how.
>
> -Doug
>
>
>
> On Wed, Aug 17, 2011 at 12:07 PM, Tom Brown <tom at ng23.net> wrote:
>
>> > Ah, I understand, however this will not work for me. I dont want to push
>> > provisioning traffic our my MPLS circuit. Would prefer to have
>> provisioning
>> > in sync across all locations via local cobbler servers. I guess I could
>> > always run a separate cobbler install and use cobbler replication to the
>> > spacewalk master.
>>
>> the only thing being directly served from the spacewalk server is the
>> anaconda kernel and most likely the stage2
>>
>> The install tree comes from the local proxy so not vast amounts of
>> traffic being served non locally
>>
>> _______________________________________________
>> Spacewalk-list mailing list
>> Spacewalk-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>
>
>
> --
> Doug Bishop
> 404-643-1417
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20110823/19d194ed/attachment.htm>