On Thu, Jul 09, 2009 at 01:05:43PM -0500, [email protected] wrote: > On Thu, Jul 9, 2009 at 8:51 AM, Diego > Naufel<[email protected]> wrote: > > Use an external dhcp server and add extended dhcp info on > that dhcp servers, > > for sunrays, so no need to multicast searching servers. > > Impractical here. We (the people who run the Sun Ray > deployment) don't operate the network's DHCP, and we've been > told that vendor extensions for DHCP clients can't or won't be > supported.
> > Or use vpn firmware, and configure manually each DTU with
> servers info.
>
> Also impractical; our Sun Ray plant is just too big relative
> to staff for us to be able to hand-adjust each DTU. That's
> part of what brought us to Sun Ray in the first place.
>
> No, we're stuck using DNS for server discovery and feeling
> lucky we were able to get that that much.
We have exactly that "problem". sunray-config-servers.foo.com is the
way to go, without a doubt. You run a TFTP server at that address that
redirects to the servers. In my mind, it's actually much more flexible
than doing it in DHCP would be anyway.
Only problem we have is that putting multiple A records on
sunray-config-servers does not work well, so we had to invest some
effort in making that service as highly available as we can (but
generally only in the morning) which we have done by running it in ESX.
Ceri
--
That must be wonderful! I don't understand it at all.
-- Moliere
pgpiQCoSYbNiE.pgp
Description: PGP signature
_______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
