From Fedora Project Wiki
(clarify repo architecture) |
(adjust example somewhat for NFSv4, which is the default in anaconda. I'm not sure NFSv3 can be made to work at present in anaconda...) |
||
| Line 5: | Line 5: | ||
#* Mount the image over loopback: {{command|# mount -o loop Fedora-{{FedoraVersionNumber|next}}-x86_64-DVD.iso /mnt/repo}} | #* Mount the image over loopback: {{command|# mount -o loop Fedora-{{FedoraVersionNumber|next}}-x86_64-DVD.iso /mnt/repo}} | ||
#* Install {{package|nfs-utils}}. | #* Install {{package|nfs-utils}}. | ||
#* Let's say your (virtual) test machine is in the <code>192.168.1.0/24</code> subnet. Put the following line into {{filename|/etc/exports}}: <pre>/mnt/repo 192.168.1.0/24(ro)</pre> | #* Let's say your (virtual) test machine is in the <code>192.168.1.0/24</code> subnet. Put the following line into {{filename|/etc/exports}}: | ||
<pre> | |||
/mnt 192.168.1.0/24(ro,fsid=0) | |||
/mnt/repo 192.168.1.0/24(ro) | |||
</pre> | |||
#* Restart NFS service: {{command|# systemctl restart nfs-server.service}} | #* Restart NFS service: {{command|# systemctl restart nfs-server.service}} | ||
#* The repository is now accessible over NFS via <code><your_IP>: | #* The repository is now accessible over NFS via <code><your_IP>:/repo</code> | ||
|actions= | |actions= | ||
# Boot the installer using any available non-live means (anything except {{filename|Live.iso}}) | # Boot the installer using any available non-live means (anything except {{filename|Live.iso}}) | ||
# Change the installation source to point to a custom NFS repository | # Change the installation source to point to a custom NFS repository | ||
#* The correct syntax is <code>server:/path</code>, e.g. <code><your_IP>: | #* The correct syntax is <code>server:/path</code>, e.g. <code><your_IP>:/repo</code> | ||
#* Make sure the repository architecture matches the architecture of your installer media. | #* Make sure the repository architecture matches the architecture of your installer media. | ||
# Proceed with installation | # Proceed with installation | ||
Revision as of 11:07, 23 May 2013
Description
This is to verify that an installation can be performed from a NFS repository configured in the Anaconda GUI.
Setup
- You need to have a Fedora repository accessible over an NFS protocol. If you do have it, no further setup is needed. If you don't, you can mount a
DVD.isoimage and export it over NFS this way:- Mount the image over loopback:
# mount -o loop Fedora-42-x86_64-DVD.iso /mnt/repo - Install
nfs-utils - Let's say your (virtual) test machine is in the
192.168.1.0/24subnet. Put the following line into/etc/exports:
- Mount the image over loopback:
/mnt 192.168.1.0/24(ro,fsid=0) /mnt/repo 192.168.1.0/24(ro)
- Restart NFS service:
# systemctl restart nfs-server.service - The repository is now accessible over NFS via
<your_IP>:/repo
- Restart NFS service:
How to test
- Boot the installer using any available non-live means (anything except
Live.iso) - Change the installation source to point to a custom NFS repository
- The correct syntax is
server:/path, e.g.<your_IP>:/repo - Make sure the repository architecture matches the architecture of your installer media.
- The correct syntax is
- Proceed with installation
Expected Results
- The installer accepts the NFS repository definition
- The said repository is used for installation. This can be checked by examining the
/tmp/packaging.logfile. Example output:14:44:07,093 INFO packaging: mounting 192.168.1.1:/mnt/repo: on /mnt/install/source ... 14:44:07,545 DEBUG packaging: adding yum repo anaconda with baseurl file:///mnt/install/source and mirrorlist None 14:44:07,568 DEBUG packaging: disabling repo fedora 14:44:07,569 DEBUG packaging: disabling repo updates-testing 14:44:07,569 DEBUG packaging: disabling repo updates
- The installation completes and the new system initiates boot properly