Hi,
> At the end of the day, if you need to really be secure, you need to have
> some kind of state on the client machine (Kerberos password, 802.1x
> credentials, etc.)--which generally doesn't exist on a clean image.
>
>
>
'Clean image' runs on a particular machine which, it seems to me, can b
Hi,
The first (and seemingly correct) approach is to use fcopy, without mixing
yet another protocol into the mix. FTP/HTTP/NFS seem to me of 'the same
class' and fcopy was (I admit) the easiest to setup by copying the ready
made skeletons-> I tried it for the first approach, as an ultimate step
f
On Mon, September 24, 2012 12:58, Thomas Lange wrote:
>> On Mon, 3 Sep 2012 22:40:08 +0200, "Andreas B. Mundt"
>> said:
>
> > * Add the MAC addresses of all machines to be installed to
> > dhcpd.conf. You have to make sure that nobody in the network
> > can fake a MA
> On Mon, 3 Sep 2012 22:40:08 +0200, "Andreas B. Mundt"
> said:
> * Add the MAC addresses of all machines to be installed to
> dhcpd.conf. You have to make sure that nobody in the network
> can fake a MAC address if you do that by some automatic means.
> Did I
hi,
Am 24.09.2012 um 17:30 schrieb Michał Dwużnik :
> My config space is indeed in order of 10GB :>
you mean where you have files and directories like
"config/{class,debconf,disk_config ...}" ? over 10GB? It sounds like, that you
transfer images etc. so it would be better, to use ftp to tra
> If your config space is over a meg in total, I'd be surprised. This is
> not the issue.
>
> I have some large tarballs in mine (a few gig) and it moves along smoothly
> with 100 nodes going at once.
>
>
My config space is indeed in order of 10GB :>
Regards
Michal
> If your config space is over a meg in total, I'd be surprised. This is
> not the issue.
Color yourself surprised then. You forgot the base-images which easily
amount to more then 100 MB each. (I've found them quite useful for
installing SuSE-hosts with FAI although you might also use them to '
Sounds to me like you have a network issue, NFS timeouts shouldn't occur
unless there are lost packets -- if the disk is stuck in I/O wait the NFS
process can still respond. Check your interfaces and switches for
dropped/errored packets. You should be able to host hundreds of clients
off a 1G, it
Well,
in my not quite so 10GbE env I experience NFS timeouts when doing 16
machines at a time.
Moving the fai configspace onto ramdisk helps for the rooms equipped with
1Gbps,
yields _lots_ of 'NFS not responding, still trying' for one forgotten room
which has still has 100Mbit
Hence my orig
Le 24/09/2012 14:03, Thomas Lange a écrit :
On Fri, 21 Sep 2012 22:06:27 +0200, Michał Dwużnik
said:
> by the way - what are the default options of mounting the NFS by FAI
when installing?
> (rsize in particular, atime?)
Using a squeeze install server and FAI 3.4.8 I get these NFS
> On Fri, 21 Sep 2012 22:06:27 +0200, Michał Dwużnik
> said:
> by the way - what are the default options of mounting the NFS by FAI when
installing?
> (rsize in particular, atime?)
Using a squeeze install server and FAI 3.4.8 I get these NFS
parameters from cat /proc/mounts
1.2
Thomas Lange writes:
> > On Fri, 21 Sep 2012 20:42:35 +0200, Katarzyna Myrek
> > said:
>
> > Today I was wondering... How many clients can you install
> > simultaneously?
> A lot. Some years ago I could install about 20 machines simultaneously
> when using fast ethernet w
> On Fri, 21 Sep 2012 20:42:35 +0200, Katarzyna Myrek
> said:
> Today I was wondering... How many clients can you install
> simultaneously?
A lot. Some years ago I could install about 20 machines simultaneously
when using fast ethernet without any problems. NFS is not a problem,
13 matches
Mail list logo
