Fedora WS: (simultaneous) install on multiple pc's
-
Then after it's booted something like Ansible or Salt can be used for Configuration management.
-
Are you trying to do this concurrently if so imaging wouldn't really work unless you have a ton of bandwidth.
-
You could deploy an image using FOG
-
If you were to create an image of fedora you would have remove the
/etc/machine-idand then runsystemd-machine-id-setupto create a new machine id. Almost like doing sysprep for Windows.Does anyone knows how Ubuntu does it with the OEM install?
-
@Dashrender said in Fedora WS: (simultaneous) install on multiple pc's:
You could deploy an image using FOG
While this was my initial thought as well, he has asked about doing this simultaneously. Which fog generally isn't "all at once go".
-
@DustinB3403 said in Fedora WS: (simultaneous) install on multiple pc's:
Are you trying to do this concurrently if so imaging wouldn't really work unless you have a ton of bandwidth.
No, not concurrently.
-
@FATeknollogee said in Fedora WS: (simultaneous) install on multiple pc's:
@DustinB3403 said in Fedora WS: (simultaneous) install on multiple pc's:
Are you trying to do this concurrently if so imaging wouldn't really work unless you have a ton of bandwidth.
No, not concurrently.
So why use (simultaneous) in the subject?
-
If the goal is to just unpack equipment and load it all as quickly as possible using PXE Fog is a hard option to beat.
-
I previously had it setup and could perform 10 devices at a time on the same segmented network.
But if we put this on the main network it would consume and stop all other work.
-
@DustinB3403 said in Fedora WS: (simultaneous) install on multiple pc's:
I previously had it setup and could perform 10 devices at a time on the same segmented network.
But if we put this on the main network it would consume and stop all other work.
Were you using unicast or multicast to deploy images?
-
@DustinB3403 said in Fedora WS: (simultaneous) install on multiple pc's:
@FATeknollogee said in Fedora WS: (simultaneous) install on multiple pc's:
@DustinB3403 said in Fedora WS: (simultaneous) install on multiple pc's:
Are you trying to do this concurrently if so imaging wouldn't really work unless you have a ton of bandwidth.
No, not concurrently.
So why use (simultaneous) in the subject?
Because sometimes I might have 3 or 5 pc's that I'd like to process at once.
-
@black3dynamite said in Fedora WS: (simultaneous) install on multiple pc's:
@DustinB3403 said in Fedora WS: (simultaneous) install on multiple pc's:
I previously had it setup and could perform 10 devices at a time on the same segmented network.
But if we put this on the main network it would consume and stop all other work.
Were you using unicast or multicast to deploy images?
multicast
-
@FATeknollogee said in Fedora WS: (simultaneous) install on multiple pc's:
@DustinB3403 said in Fedora WS: (simultaneous) install on multiple pc's:
@FATeknollogee said in Fedora WS: (simultaneous) install on multiple pc's:
@DustinB3403 said in Fedora WS: (simultaneous) install on multiple pc's:
Are you trying to do this concurrently if so imaging wouldn't really work unless you have a ton of bandwidth.
No, not concurrently.
So why use (simultaneous) in the subject?
Because sometimes I might have 3 or 5 pc's that I'd like to process at once.
Okay. . . but in the post you say "So you want to install Fedora WS on 10, 20 or 100 pc's" so the assumption is upto 100 pc's concurrently.
-
FOG would be my recommendation, but on a segmented network where the imaging process and FOG server are on the same segment.
Configure FOG to automate the process that any machines that netboot on that network segment immediately are imaged without needing input from yourself or team members and be done with it.
-
I specifically managed Fog as a VM, but provided a dedicated network adapter off of the Hypervisor to be used for that purpose only.
Internet access was available on the network so the image could be updated easily enough and it's still in use today.
-
@DustinB3403 said in Fedora WS: (simultaneous) install on multiple pc's:
Are you trying to do this concurrently if so imaging wouldn't really work unless you have a ton of bandwidth.
Uses about the same as Kickstart or PXE boot will. Gotta get those files there somehow.
And if you really want to do it fast, like for a huge organization (we used to do this), you can put some crazy bandwidth in like 40 Gb/s or 100 Gb/s on the server that is handing out the images, and store the image on a RAM disk. Only need 2GB of RAM or so to do it, then you don't even touch the hard drive except at boot time. Once the RAM disk has the image once, you are good until you change it or reboot.
You can push some insane amount of deployments that way.
-
@DustinB3403 said in Fedora WS: (simultaneous) install on multiple pc's:
@Dashrender said in Fedora WS: (simultaneous) install on multiple pc's:
You could deploy an image using FOG
While this was my initial thought as well, he has asked about doing this simultaneously. Which fog generally isn't "all at once go".
It kind of is...I was using FOG to do multicast imaging 7 years ago. We're talking 30-60 machines at a clip.
-
@coliver said in Fedora WS: (simultaneous) install on multiple pc's:
@DustinB3403 said in Fedora WS: (simultaneous) install on multiple pc's:
@Dashrender said in Fedora WS: (simultaneous) install on multiple pc's:
You could deploy an image using FOG
While this was my initial thought as well, he has asked about doing this simultaneously. Which fog generally isn't "all at once go".
It kind of is...I was using FOG to do multicast imaging 7 years ago. We're talking 30-60 machines at a clip.
Sure it can do it but that doesn't mean that you should do it. It's about network performance and if you're not setup for it you'll encounter massive slowdowns
-
@DustinB3403 said in Fedora WS: (simultaneous) install on multiple pc's:
@coliver said in Fedora WS: (simultaneous) install on multiple pc's:
@DustinB3403 said in Fedora WS: (simultaneous) install on multiple pc's:
@Dashrender said in Fedora WS: (simultaneous) install on multiple pc's:
You could deploy an image using FOG
While this was my initial thought as well, he has asked about doing this simultaneously. Which fog generally isn't "all at once go".
It kind of is...I was using FOG to do multicast imaging 7 years ago. We're talking 30-60 machines at a clip.
Sure it can do it but that doesn't mean that you should do it. It's about network performance and if you're not setup for it you'll encounter massive slowdowns
This is somethign I don't undestand on the network side.
If you're doing multicasts - why would the rest of switch be affected? Only the ports subscribed to the multicast, and the one providing the multicast should be affected..
Now of course if you end up going over an uplink connection, the downstream switch will be entirely affected.. but assuming that's not the case, why would everyone else be affected by the multicast? -
@Dashrender said in Fedora WS: (simultaneous) install on multiple pc's:
@DustinB3403 said in Fedora WS: (simultaneous) install on multiple pc's:
@coliver said in Fedora WS: (simultaneous) install on multiple pc's:
@DustinB3403 said in Fedora WS: (simultaneous) install on multiple pc's:
@Dashrender said in Fedora WS: (simultaneous) install on multiple pc's:
You could deploy an image using FOG
While this was my initial thought as well, he has asked about doing this simultaneously. Which fog generally isn't "all at once go".
It kind of is...I was using FOG to do multicast imaging 7 years ago. We're talking 30-60 machines at a clip.
Sure it can do it but that doesn't mean that you should do it. It's about network performance and if you're not setup for it you'll encounter massive slowdowns
This is somethign I don't undestand on the network side.
If you're doing multicasts - why would the rest of switch be affected? Only the ports subscribed to the multicast, and the one providing the multicast should be affected..
Now of course if you end up going over an uplink connection, the downstream switch will be entirely affected.. but assuming that's not the case, why would everyone else be affected by the multicast?Because of poor network design and options in the space, thus using uplink ports across several different switches.
When I changed from using the general network to a segmented one, I was able to run 20 machines at a time (limited by the switch that was available) and no one knew the difference.
