Bug 1152883 - Local replication of Product installation trees
Summary: Local replication of Product installation trees
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora Documentation
Classification: Retired
Component: install-guide
Version: devel
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Bokoc
QA Contact: Fedora Docs QA
URL:
Whiteboard:
Depends On: 1134524
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-15 06:52 UTC by Pete Travis
Modified: 2024-05-21 09:21 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-21 09:21:52 UTC
Embargoed:


Attachments (Terms of Use)

Description Pete Travis 2014-10-15 06:52:49 UTC
It doesn't look like there will be a DVD image, the traditional source in our instructions for site-provided installation repos.  Consider conjuring up a procedure explaining how an administrator could obtain a mirror of the installation tree for each Product (whatever anaconda is pointed at for the netinstalls) without having to pull in the entire repo.

Comment 1 Petr Bokoc 2015-10-19 21:39:50 UTC
So, here's what we should do (based on an IRC convo with randomuser):

* tell people that they don't have to limit themselves to whatever is available on the install media they use; they can use inst.repo=, the Source spoke in the GUI, or repo in Kickstart to point at e.g. http://dl.fedoraproject.org/pub/fedora/linux/releases/22/Workstation/x86_64/os/ and install anything they want

* mention that the Everything variant exists

* make sure to use the download.fedoraproject.org address, instead of e.g. dl.fp.o

* mention somewhere that you can create a local mirror, even a private one, to speed up mass deployments; link to http://fedoraproject.org/wiki/Infrastructure/Mirroring

Comment 2 Petr Bokoc 2024-05-21 09:21:52 UTC
The install guide has been retired, therefore I'm closing this bug. 

If you would like to report Fedora docs bugs in the future, please use the "bug" icon on the top right of the affected page, it will take you directly to the appropriate issue tracker.


Note You need to log in before you can comment on or make changes to this bug.