| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
Wifi connections have separate ifcfg files, not specified by the
device name.
Signed-off-by: Vratislav Podzimek <vpodzime@redhat.com>
|
|
|
|
|
|
|
| |
ksdata are updated in NetworkSpoke.apply from ifcfg files.
At the end of installation we need to modify ifcfg files
(network configuration) for devices used by storage and to
set ONBOOT defaults. So update also ksdata.
|
| |
|
|
|
|
|
|
|
|
| |
The storage instance contains a platform instance, so there's no need
to pass one in explicitly.
Also, setDefaultPartitioning seems to be a good place to set fstype
for boot requests only once.
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
Makefile.am
anaconda
data/systemd/anaconda.target
pyanaconda/bootloader.py
pyanaconda/constants.py
pyanaconda/iutil.py
pyanaconda/kickstart.py
pyanaconda/network.py
pyanaconda/vnc.py
scripts/makeupdates
|
| |
| |
| |
| | |
This is related to commit 43715e5db831893edcfc2b289a1e575b0ba19403
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is almost the final step, the object is not used anymore,
I am keeping the rest only not to forget to handle what is left:
- I need to look at imageInstall
- creating default ifcfg files (setDefaultConfig) should go to
dracut or some network initialization step
The whole patchset removes anaconda.network object aiming to have all
data/configuration in ksdata.
The object was needed for our GUI using nm-c-e. We used to keep list of device
configuration objects (basically ifcfg dictionaries) in it so that we could
tweak them to be able to use nm-c-e for configuration/activation of devices.
Now it seems we can do without the list although we still need to do some
modifications of ifcfg files at the end of installation (setting onboot policy,
setting values for devices used for storage)
Hopefuly we'll be able to represent all the data stored in network object
in ksdata.
Following to the patchset I want to update ksdata with NetworkData objects
for all devices and use it to replace network.getDevices(). I have to think
where it should happen:
- in kickstart.py
- or somewhere in pre-gui network initialization (so that it happens also
for non-ks cases) where we e.g. activate default device if needed.
- or in initialize of standalone spoke - seems to late, we'll need it
already for eventual bring-up of network
-----
To sum up what the network.py serves for now:
Some of network utility functions (more of them are in isys):
- hostname sanity checking
- ip sanity checking
- hostname resolution
- status of networking
- connected?
- list of active devices
- logging (ifcfg files)
Network configuration:
- hostname setting (getting?)
- note: storage (lvm, raid) is using hostname for default names
- ksdevice resolution (link, MAC address, bootif)
- probably we'll be able to remove it, now it is only used
for unspecified --device in kickstart network command
- write kickstart (currently from ifcfg config)
- used by apply method
- write dracut arguments (from ifcfg config)
- note: depends on storage
- modify configuration of target system (ifcfg files)
- note: depends on storage
- ONBOOT policy (differs on rhel and Fedora)
- FCoE - ONBOOT=yes the devices
- root on iSCSI - NM_CONTROLLED=no for root on iscsi
(there is a NM BZ to fix this)
- write /etc/sysconfig/network configuration
- this should be reviewed
- copy network configuration files to system
- ifcfg-<iface> files and wireless key-<iface> files
- dhclient-<iface>.conf files
(dhcpclass and dhcp timeout which is not supported in noloader)
- /etc/sysconfig/network
- /etc/resolv.conf - genrated by NM
- /etc/udev/rules.d/70-persistent-net.rules (review)
- disable ipv6 on target system (noipv6 boot/ks option)
|
|\|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
Makefile.am
anaconda
anaconda.spec.in
loader/loader.c
loader/net.c
loader/unpack.c
po/POTFILES.in
pyanaconda/__init__.py
pyanaconda/bootloader.py
pyanaconda/cmdline.py
pyanaconda/constants.py
pyanaconda/dispatch.py
pyanaconda/errors.py
pyanaconda/flags.py
pyanaconda/iutil.py
pyanaconda/kickstart.py
pyanaconda/platform.py
pyanaconda/storage/__init__.py
pyanaconda/storage/devicetree.py
pyanaconda/storage/fcoe.py
pyanaconda/storage/formats/swap.py
pyanaconda/storage/iscsi.py
pyanaconda/storage/partitioning.py
pyanaconda/yuminstall.py
scripts/makeupdates
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Instead of us knowing about crashkernel stuff in our code, let the
crashkernel guys own that policy.
rhcrashkernel-param comes from the following url, though I'm told
they're updating it not to end in .sh there:
http://pkgs.fedoraproject.org/gitweb/?p=kexec-tools.git;a=commitdiff;h=ca94c80a91400e9ce95bb56023ca4391d5b41d85
|
| |
| |
| |
| |
| |
| |
| |
| | |
loader used to set ONBOOT=yes for any device it activated, so having an
active netdev implied that at least one of them had ONBOOT=yes.
This logic doesn't necessarily work anymore, so let's just check to see
if any of them have ONBOOT=yes directly.
|
| |
| |
| |
| | |
Also don't use float to compare 2 numbers. Use Decimal instead.
|
| |
| |
| |
| | |
task. (#643786)
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've first removed the definitions of getBackend from our standard install
classes. The base class returns None. For other products with their own
install classes, they can have getBackend return something. For our
products, we will fall back to looking up the payload class based on flags.
Note that payload.setup() still needs to be called, but this should be done
intentionally when it's needed since it must happen after the network is up
and storage is populated.
Note also that this adds more crud to Anaconda, but we're going to be removing
most of this object later so hopefully it won't be so bad. We'll also need
to better document install classes.
|
|
|
|
|
|
| |
If no device was activated during install (e.g. DVD install),
set ONBOOT=yes for first wired device having link found.
(Which means the device will be brought up after system boot).
|
|
|
|
|
|
|
|
|
|
|
| |
This step is not scheduled by default, it is skipped for any text
installation and many kickstart commands (like autopart), it is requested
if the user selects "review partitioning layout" on the parttype screen.
There is a mechanism in autopartitioning that enables manual partitioning
screen (if available) when autopartitioning fails. Instead of checking the
availability this just tries to request the manual partitioning step and
catches DispatcherError for those cases where this is not possible.
|
|
|
|
|
| |
This means that 15-Beta cannot be used to upgrade F12, but it could be used
to upgrade F14.
|
| |
|
|
|
|
|
|
|
|
|
| |
In Fedora, for instance, there's no comps localization file (there's
neither a product.img).
This patch should make the installation tasks look translated
Related: rhbz#681404
|
|
|
|
| |
When checking for the release allow equal versions to be upgraded.
|
| |
|
|
a real Python package.
Also updates the build and autotools stuff to work with the new structure
|