Installfest Services: Difference between revisions
No edit summary |
(Begn to update this to reflect reality) |
||
Line 5: | Line 5: | ||
== Synopsis == |
== Synopsis == |
||
Installfest "Services" is an working proof-of-concept by [[User:Bseklecki || Brian A. Seklecki]] and [[User:trodgers | Ted Rodgers]] to provide high performance servers for Linux Distro Boot, Install Media, and Updates retrieval via a local FTP/HTTP mirror within the Installfest event. |
Installfest "Services" is an working proof-of-concept by [[User:Bseklecki || Brian A. Seklecki]] and [[User:trodgers | Ted Rodgers]] to provide high performance servers for Linux Distro Boot, Install Media, and Updates retrieval via a local FTP/HTTP/RSYNC/NFS mirror within the Installfest event LAN. |
||
The service runs on local hardware in the LAN. Having local install/update mirrors avoids the need for [[WPLUG]] attendees to consume |
The service runs on local hardware in the LAN. Having local install/update mirrors avoids the need for [[WPLUG]] attendees to consume commodity Internet (commercial upstream Internet Connectivity) at the [[InstallFest]] venue and thus saturating the limited WAN normally available. |
||
NOTICE: [[WPLUG]] doesn't officially endorse or support the distros provided on [[Install Services]]; nor does provide any guarantees about the availability of service itself. |
|||
= Install Services = |
= Network PXE Install Services (PXELINUX) = |
||
[[Image:wplug_installfest_servicesHardare_2009CFIPowerEdgeCisco.jpg|thumb|right|350px|Hardware |
[[Image:wplug_installfest_servicesHardare_2009CFIPowerEdgeCisco.jpg|thumb|right|350px|Original Hardware (provided by Collaborative Fusion, Inc.)]] |
||
The current configuration |
The current configuration of services provides a PXE environment. There PXE magic is a simple 'next-server' and 'boot-file' flags provided to the client via an extended attribute via DHCP offer reply (DHCP options 66/150). |
||
The PXE code in the BIOS of your device will translate extra data into a TFTP client download the 1st/2nd stage boot loader from the server. Currently the system is configured to hand out Redhat/Fedora 'intermediate' boot loader clients from the [http://www.syslinux.org/wiki/index.php/The_Syslinux_Project Syslinux] project. <br> |
|||
⚫ | |||
The Syslinux code then executes a set of additional TFTP request and downloads its configuration files, modules, included config files, graphics, and other data. <br> |
|||
The result is a menu of install'able operating systems; selecting an install target is analagous to booting from the install CD for that OS. <br> |
|||
⚫ | |||
After the boot loader starts the OS install image, select DHCP auto network configuration (DHCP will renew from the BIOS to the OS). <br> |
|||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
= Update Services = |
= Update Services = |
||
After the OS update is complete, you can add new YUM update "repos" via inserting a file into /etc/yum.repos.d (for automatic inclusion). |
After the OS update is complete, you can add new YUM update "repos" via inserting a file into '''/etc/yum.repos.d''' (for automatic inclusion). |
||
<br> |
<br> |
||
Also, during the [[InstallFest]], run all yum(8) commands with the default depos enabled: |
Also, during the [[InstallFest]], run all yum(8) commands with the default depos enabled: |
||
Line 37: | Line 43: | ||
Fetch a Fedora Core 10 i386 YUM Repo Config File at http://digitalfreaks.org/~lavalamp/wplug-updates.repo |
Fetch a Fedora Core 10 i386 YUM Repo Config File at http://digitalfreaks.org/~lavalamp/wplug-updates.repo |
||
Sample: |
|||
⚫ | |||
[updates-wplug] |
|||
name=Fedora Core $releasever - $basearch - Updates from WPLUG InstallFest Services |
|||
baseurl=http://updates.wplug.org/pub/fedora/linux/updates/$releasever/$basearch/ |
|||
#mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-fc$releasever&arch=$basearch |
|||
enabled=1 |
|||
gpgcheck=1 |
|||
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora |
|||
⚫ | |||
NOTE: "updates" here refers to the name of the default Fedora repo -- where as the new Repo is named "wplug-updates" |
NOTE: "updates" here refers to the name of the default Fedora repo -- where as the new Repo is named "wplug-updates" |
||
Line 48: | Line 65: | ||
'''# yum upgrade''' |
'''# yum upgrade''' |
||
4) Test the repo is functional: |
|||
'''# yum install vim''' |
|||
'''# yum update''' |
|||
NOTE: Ensure that the RPMs are downloaded locally and not remotely |
|||
= Install Services = |
= Install Services = |
Revision as of 20:42, 5 March 2012
DEPRECIATED
NOTE: The content on this page is depreciated. The content will be updated on the weekend of 2/17/2012 to reflect current status.
Synopsis
Installfest "Services" is an working proof-of-concept by | Brian A. Seklecki and Ted Rodgers to provide high performance servers for Linux Distro Boot, Install Media, and Updates retrieval via a local FTP/HTTP/RSYNC/NFS mirror within the Installfest event LAN.
The service runs on local hardware in the LAN. Having local install/update mirrors avoids the need for WPLUG attendees to consume commodity Internet (commercial upstream Internet Connectivity) at the InstallFest venue and thus saturating the limited WAN normally available.
NOTICE: WPLUG doesn't officially endorse or support the distros provided on Install Services; nor does provide any guarantees about the availability of service itself.
Network PXE Install Services (PXELINUX)
The current configuration of services provides a PXE environment. There PXE magic is a simple 'next-server' and 'boot-file' flags provided to the client via an extended attribute via DHCP offer reply (DHCP options 66/150).
The PXE code in the BIOS of your device will translate extra data into a TFTP client download the 1st/2nd stage boot loader from the server. Currently the system is configured to hand out Redhat/Fedora 'intermediate' boot loader clients from the Syslinux project.
The Syslinux code then executes a set of additional TFTP request and downloads its configuration files, modules, included config files, graphics, and other data.
The result is a menu of install'able operating systems; selecting an install target is analagous to booting from the install CD for that OS.
After the boot loader starts the OS install image, select DHCP auto network configuration (DHCP will renew from the BIOS to the OS).
Specific client MAC addresses can get specific bootloader code upon request.
At install time, when media selection occurs, select "URL" for media source and enter:
http://updates.wplug.org/pub/fedora/linux/releases/$releasever/Fedora/{i386,x86_64}/os
Update Services
After the OS update is complete, you can add new YUM update "repos" via inserting a file into /etc/yum.repos.d (for automatic inclusion).
Also, during the InstallFest, run all yum(8) commands with the default depos enabled:
Updates for Fedora Core 10 / i386
1) Install the following file into directory /etc/yum.repos.d/"
Fetch a Fedora Core 10 i386 YUM Repo Config File at http://digitalfreaks.org/~lavalamp/wplug-updates.repo
Sample:
[updates-wplug]
name=Fedora Core $releasever - $basearch - Updates from WPLUG InstallFest Services baseurl=http://updates.wplug.org/pub/fedora/linux/updates/$releasever/$basearch/ #mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-fc$releasever&arch=$basearch enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
Note: To ensure that the local WPLUG repositories are utilized instead of the default Redhat / Fedora for all yum(8) functions, always prepend the flag "--disablerepo=updates" to Yum commands until you are no longer connected to the installfest network
NOTE: "updates" here refers to the name of the default Fedora repo -- where as the new Repo is named "wplug-updates"
2) Update the available RPM database YUM maintains
# yum update
3) Update your system:
# yum check-update # yum upgrade
4) Test the repo is functional:
# yum install vim # yum update
NOTE: Ensure that the RPMs are downloaded locally and not remotely
Install Services
The installfest service runs a DHCP+TFTP service which will serve PXE compatible boot loaders and kernels.
The service also provides NAT+PAT routing on an as-needed basis. When it is not functioning as a router, DHCP service should be turned off on the router in use. [[Category:Update]