| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
In some cases the vnc server may start before the system has an IP
address. This isn't a fatal problem, it just makes it harder for the
user to know where to connect their vnc client.
This adds a 5 second retry when getting the IP. If that fails it will
still start the vnc server, and will print out instructions for
how to manually discover the IP address.
|
| |
|
|
| |
Regards NM's default autoconnections.
|
| |
|
|
|
|
| |
This cleans up a lot of stuff in this file by making use of the spoke we
have instead of newt. There are also a few whitespace fixes and
removals of unnecessary imports.
|
| |
|
|
|
|
| |
- We can add dhcp activation in networkInitialize in thread later
- Also fixing merge (newui->master) of
https://lists.fedorahosted.org/pipermail/anaconda-patches/2012-June/000023.html
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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 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)
|
| |/
|
|
|
|
|
|
| |
NM is setting hostname and we might be resetting it in kickstart.py.
It is stored in ksdata with unfortunate access (iterating over
network commands).
Hostname handling will need some more work in newui. Here I am just
giving another stab to Network() object.
|
| | |
|
| |
|
|
|
|
|
| |
https://bugzilla.redhat.com/show_bug.cgi?id=814402
Try using the network name of the displayed IP address rather than the
hostname.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
loader was writing the vncpassword out to a file, because:
a) many years ago, VNC got started by loader, and
b) VNC used to need to read its password from a file.
But now it is the Glorious Future and anaconda can just read the
'vncpassword' boot/cmdline arg and hand it to the VncServer object.
This also removes recoverVNCPassword and pw_init_file from the VncServer
class, and the tests associated with them.
|
| |
|
|
|
|
|
| |
New XVNC does not support changing of SecurityTypes when
it is already running with vncconfig. So we have to solve
all the password stuff first, and then run the XVNC with
either None or VncAuth.
|
| |
|
|
|
| |
Mostly replaces 'except Foo, e' with 'except Foo as e', but there
are a few areas where some logic gets reworked.
|
| |
|
|
|
|
|
|
| |
Related to the fullscreen support for the rest of anaconda. Don't force
800x600 here, just let things happen. It works on my screen, which
according to xdpyinfo is 1440x900.
Related: rhbz#663411
|
| |
|
|
|
| |
nm-c-e is not writing it out, and we can stumble over it
in Live CD environment, see bz #648635 for example.
|
| | |
|
| | |
|
|
|
a real Python package.
Also updates the build and autotools stuff to work with the new structure
|
