Mudanças entre as edições de "Minicluster:DRBL:exemploFC25"
De WikiLICC
(Criou página com '<pre> root@one /etc/drbl # drblpush -i ****************************************************** Hint! When a yes/no option is available, the default value is uppercase, Ex. (y/N...') |
(Sem diferença)
|
Edição atual tal como às 14h21min de 27 de junho de 2017
root@one /etc/drbl # drblpush -i
******************************************************
Hint! When a yes/no option is available, the default value is uppercase, Ex. (y/N), the default is "N", when you press "Enter", it will use "N". If you are not sure which one to choose, you can just press "Enter" key.
******************************************************
Searching the installed packages for DRBL server...This might take several minutes...
Finished searching the installed packages for DRBL server.
******************************************************
------------------------------------------------------
The interactive mode let you supply the information of your DRBL environment.
------------------------------------------------------
------------------------------------------------------
Please enter DNS domain (such as drbl.sf.net):
[drbl.org]
Set DOMAIN as drbl.org
------------------------------------------------------
Please enter NIS/YP domain name:
[nismatrix]
Set DOMAIN as nismatrix
------------------------------------------------------
Please enter the client hostname prefix:
This prefix is used to automatically create hostname for clients. If you want to overwrite some or all automatically created hostnames, press Ctrl-C to quit this program now, edit /etc/drbl/client-ip-hostname, then run this program again.
[one-] cell
Set the client hostname prefix as cell
------------------------------------------------------
enp0s25: IP address 143.54.226.116, netmask 255.255.254.0
enp7s4: IP address 192.168.0.100, netmask 255.255.255.0
virbr0: IP address 192.168.122.1, netmask 255.255.255.0
Configured ethernet card(s) found in your system: enp0s25 enp7s4 virbr0
------------------------------------------------------
The ethernet port for Internet access is: enp0s25
The ethernet port(s) for DRBL environment: enp7s4 virbr0
******************************************************
******************************************************
Now we can collect the MAC address of clients!
If you want to let the DHCP service in DRBL server offer same IP address to client every time when client boot, and you never did this procedure, you should do it now!
If you already have those MAC addresses of clients, you can put them into different group files (These files number is the same number of networks cards for DRBL service). In this case, you can skip this step.
This step helps you to record the MAC addresses of clients, then divide them into different groups. It will save your time and reduce the typos.
The MAC addresses will be recorded turn by turn according to the boot of clients,
and they will be put into different files according to the network card in server, file name will be like macadr-eth1.txt, macadr-eth2.txt... You can find them in directory /etc/drbl.
Please boot the clients by order, make sure they boot from etherboot or PXE!
Do you want to collect them?
[y/N]
******************************************************
OK! Let's continue...
******************************************************
Hostmin: 192.168.0.1
Do you want to let the DHCP service in DRBL server offer same IP address to the client every time when client boots (If you want this function, you have to collect the MAC addresses of clients, and save them in file(s) (as in the previous procedure)). This is for the clients connected to DRBL server's ethernet network interface enp7s4 ?
[y/N] y
******************************************************
OK! Please tell me the file name which contains the MAC address of clients line by line for enp7s4.
[macadr-enp7s4.txt]
******************************************************
What is the initial number do you want to use in the last set of digits in the IP (i.e. the initial value of d in the IP address a.b.c.d) for DRBL clients connected to this ethernet port enp7s4.
[1] 108
******************************************************
The file name you set is "macadr-enp7s4.txt".
The clients number in this file is 16.
We will set the IP address for the clients connected to DRBL server's ethernet network interface enp7s4 By the MAC address file you set, the IP addresses for the clients connected to DRBL server's ethernet network interface enp7s4 as: 192.168.0.108 - 192.168.0.123
Accept ? [Y/n]
******************************************************
OK! Let's continue...
Hostmin: 192.168.122.1
Do you want to let the DHCP service in DRBL server offer same IP address to the client every time when client boots (If you want this function, you have to collect the MAC addresses of clients, and save them in file(s) (as in the previous procedure)). This is for the clients connected to DRBL server's ethernet network interface virbr0 ?
[y/N] y
******************************************************
OK! Please tell me the file name which contains the MAC address of clients line by line for virbr0.
[macadr-virbr0.txt]
Can't open ./macadr-virbr0.txt*: No such file or directory.
Can't open ./macadr-virbr0.txt*: No such file or directory.
grep: ./macadr-virbr0.txt*: No such file or directory
******************************************************
What is the initial number do you want to use in the last set of digits in the IP (i.e. the initial value of d in the IP address a.b.c.d) for DRBL clients connected to this ethernet port virbr0.
[1] 50
******************************************************
The file name you set is "macadr-virbr0.txt".
The clients number in this file is 0.
We will set the IP address for the clients connected to DRBL server's ethernet network interface virbr0 By the MAC address file you set, the IP addresses for the clients connected to DRBL server's ethernet network interface virbr0 as: 192.168.122.50 -
Accept ? [Y/n]
******************************************************
OK! Let's continue...
******************************************************
The Layout for your DRBL environment:
******************************************************
NIC NIC IP Clients
+-----------------------------+
| DRBL SERVER |
| |
| +-- [enp0s25] 143.54.226.116 +- to WAN
| |
| +-- [enp7s4] 192.168.0.100 +- to clients group enp7s4 [ 16 clients, their IP
| | from 192.168.0.108 - 192.168.0.123]
| +-- [virbr0] 192.168.122.1 +- to clients group virbr0 [ 0 clients, their IP
| | from 192.168.122.50 - ]
+-----------------------------+
******************************************************
Total clients: 16
******************************************************
Press Enter to continue...
******************************************************
------------------------------------------------------
In the system, there are 3 modes for diskless linux services:
[0] Full DRBL mode, every client has its own NFS based /etc and /var.
[1] DRBL SSI (Single system image) mode, every client uses tmpfs based /etc and /var. In this mode, the loading and necessary disk space of server will be lighter. NOTE! (a) The client machine memory is recommended at least 256 MB. (b) The setting and config files of client will not be saved to the DRBL server! They are just used once and will vanish after the machine shutdowns! Besides, if you modify any file in the template client (located in /tftpboot/nodes), you have to run drbl-gen-ssi-files to create the template tarball in /tftpboot/node_root/drbl_ssi/. (c) If you want to provide some file to overwrite the setting in the template tarball when client boots, check /tftpboot/node_root/drbl_ssi/clients/00_README for more details.
[2] I do NOT want to provide diskless Linux service to client.
Which mode do you prefer?
[0] 1
DRBL SSI mode is set, an elegant mode for DRBL is on the way!
******************************************************
------------------------------------------------------
In the system, there are 4 modes available for clonezilla:
[0] Full Clonezilla mode, every client has its own NFS based /etc and /var.
[1] Clonezilla box mode, every client uses tmpfs based /etc and /var. In this mode, the loading and necessary disk space of server will be lighter than that in Full Clonezilla mode. Note! In Clonezilla box mode, the setting and config files of client will not be saved to the DRBL server! They just use once and will vanish after the machine shutdowns!
[2] I do NOT want clonezilla.
[3] Use Clonezilla live as the OS (Operating System) of clients (Testing).
Which mode do you prefer?
[0] 1
Clonezilla box mode is set, an elegant mode for clonezilla is on the way!
******************************************************
******************************************************
The CPU arch for clients when running Clonezilla job: i386
------------------------------------------------------
When using clonezilla, which directory in this server you want to store the saved image (Please use absolute path, and do NOT assign it under /mnt/, /media/ or /tmp/)?
[/home/partimag]
Directory for clonezilla saved images: /home/partimag
------------------------------------------------------
If there is a local harddrive with swap partition or writable file system in your client machine,
do you want to use that swap partition or create a swap file in the writable filesystem so that client has more memory to use? (This step will NOT destroy any data in that harddisk)
[Y/n] n
******************************************************
------------------------------------------------------
Which mode do you want the clients to use after they boot?
"1": Graphic mode (X window system) (default),
"2": Text mode.
[1] 2
The clients will use text mode when they boot.
******************************************************
------------------------------------------------------
Do you want to set the root's password for clients instead of using same root's password copied from server? (For better security)
[y/N]
OK! Let's continue...
------------------------------------------------------
Do you want to set the pxelinux password for clients so that when client boots, a password must be entered to startup (For better security)
[y/N]
OK! Let's continue...
------------------------------------------------------
Do you want to set the boot prompt for clients?
[Y/n]
How many 1/10 sec is the boot prompt timeout for clients?
[70]
OK! Let's continue...
------------------------------------------------------
------------------------------------------------------
Do you want to use graphic background for PXE menu when client boots?
Note! If you use graphical PXELinux menu, however client fails to boot, you can switch to text mode by running "switch-pxe-bg-mode -m text".
[y/N]
Use text PXE Linux menu for the client.
------------------------------------------------------
------------------------------------------------------
By using alias interface, every client can have 2 IPs,
one of them is private IP for clients connected to DRBL server, and the other is public IP for clients directly connected to WAN from switch!
Do you want to setup public IP for clients?
[y/N]
------------------------------------------------------
Do you want to let DRBL clients have an option to run terminal mode? i.e. you want to let that client run remote display (which will mostly use resources of server), say "Y" here.
Note!
0. If you say yes to this option, this will be a very limited environment for client, i.e. NO local access for USB, CD, audio, printer, etc. in client.
1. If your server is not powerful, say "no" here.
2. By saying "yes" here, we will turn on xdmcp,
It is never a safe thing to turn on that. Setting up /etc/hosts.allow and /etc/hosts.deny to only allow local access is another alternative but not the safest.
Firewalling port 177 is the safest if you wish to have xdmcp on.
Read the manual for more notes on the security of XDMCP.
Please set it by yourself!
3. If you say "yes" here, you might have to restart your desktop environment manager (gdm/kdm) later, remember to save your data before you close applications!
Do you want to let client has an option to run terminal mode?
[y/N] y
------------------------------------------------------
Do you want to let DRBL server as a NAT server? If not, your DRBL client will NOT be able to access Internat.
[Y/n]
OK! Let's continue...
------------------------------------------------------
------------------------------------------------------
Do you want to keep the old setting of existing DRBL clients if they exist?
[Y/n]
We will try to keep the setting of the DRBL clients if they already exist.
******************************************************
******************************************************
The running kernel in the server supports NFS over TCP!
Note! If you change the running kernel in the server, and not sure whether the kernel supports NFS over udp or tcp, you'd better to re-run "drblpush -i" again to avoid the client boots in failure!
Press Enter to continue...
------------------------------------------------------
******************************************************
The calculated NETWORK for enp7s4 is 192.168.0.0.
The calculated NETWORK for virbr0 is 192.168.122.0.
cat: macadr-virbr0.txt: No such file or directory
******************************************************
******************************************************
We are now ready to deploy the files to system!
Do you want to continue?
Warning! If you go on, your firewall rules will be overwritten during the setup!
The original rules will be backuped as iptables.drblsave in system config directory (/etc/sysconfig or /etc/default).
[Y/n]
******************************************************
OK! Let's do it!
------------------------------------------------------
Some files are found in /usr/share/drbl//prerun/drbl/. Run them first...
Checking the necessary disk space... done!
Copying the config file to /etc/drbl... done!
Backup the original /etc/hosts as /etc/hosts.drblsave... done!
Generate the /etc/hosts...
done!
DAGO> Cleaning the stale files of the diskless nodes if they exist... done!
*****************************************************.
*****************************************************.
The version number for your GNU/Linux: FC25
Keeping the old common root files if they exist...
Keeping old nodes if they exist...
Creating common root files... This might take several minutes........... done!
Update the kernel for client if necessary...
The DRBL client uses x86_64 kernel with version 4.11.6-201.fc25.x86_64...
Trying to update the /tftpboot/node_root/lib/modules/4.11.6-201.fc25.x86_64 from server's /lib/modules/... This might take several minutes...
"x86_64" 4.11.6-201.fc25.x86_64 kernel in this DRBL server is not found, so skip this.
Copying the directory /etc/ to clients common root /tftpboot/node_root...
Cleaning the ssh key file ssh_host_rsa_key copied from server... done!
Cleaning the ssh key file ssh_host_rsa_key.pub copied from server... done!
Commenting the TCPwrapper related file /tftpboot/node_root/etc/hosts.deny copied from server... done!
Commenting the TCPwrapper related file /tftpboot/node_root/etc/hosts.allow copied from server... done!
Deleting 'README' service in systemd-like environment ...
service README does not support chkconfig
Deleting 'arm-wol' service in systemd-like environment ...
Deleting 'drblthincli' service in systemd-like environment ...
Deleting 'livesys' service in systemd-like environment ...
Deleting 'livesys-late' service in systemd-like environment ...
Deleting 'mkswapfile' service in systemd-like environment ...
Deleting 'netconsole' service in systemd-like environment ...
Deleting 'network' service in systemd-like environment ...
Deleting 'ocs-run' service in systemd-like environment ...
Deleting 'systemd-tmpfiles-clean' service in systemd-like environment ...
Deleting 'vmtoolsd' service in systemd-like environment ...
Deleting 'blk-availability' service in systemd-like environment ...
Deleting 'mkswapfile' service in systemd-like environment ...
Deleting 'sssd-nss' service in systemd-like environment ...
Deleting 'plymouth-kexec' service in systemd-like environment ...
Deleting 'vgauthd' service in systemd-like environment ...
Deleting 'colord' service in systemd-like environment ...
Deleting 'canberra-system-shutdown' service in systemd-like environment ...
Deleting 'munge' service in systemd-like environment ...
Deleting 'hypervvssd' service in systemd-like environment ...
Deleting 'zram' service in systemd-like environment ...
Deleting 'speech-dispatcherd' service in systemd-like environment ...
Deleting 'iscsi-shutdown' service in systemd-like environment ...
Deleting 'fcoe' service in systemd-like environment ...
Deleting 'systemd-halt' service in systemd-like environment ...
Deleting 'dhcpd6' service in systemd-like environment ...
Deleting 'systemd-localed' service in systemd-like environment ...
Deleting 'anaconda-pre' service in systemd-like environment ...
Deleting 'auditd' service in systemd-like environment ...
Deleting 'netcf-transaction' service in systemd-like environment ...
Deleting 'NetworkManager-dispatcher' service in systemd-like environment ...
Deleting 'systemd-journal-catalog-update' service in systemd-like environment ...
Deleting 'systemd-machined' service in systemd-like environment ...
Deleting 'wpa_supplicant' service in systemd-like environment ...
Deleting 'lvm2-lvmpolld' service in systemd-like environment ...
Deleting 'sssd' service in systemd-like environment ...
Deleting 'sssd-secrets' service in systemd-like environment ...
Deleting 'systemd-firstboot' service in systemd-like environment ...
Deleting 'initrd-switch-root' service in systemd-like environment ...
Deleting 'packagekit' service in systemd-like environment ...
Deleting 'usbmuxd' service in systemd-like environment ...
Deleting 'rdisc' service in systemd-like environment ...
Deleting 'systemd-hostnamed' service in systemd-like environment ...
Deleting 'gdm' service in systemd-like environment ...
Deleting 'dmraid-activation' service in systemd-like environment ...
Deleting 'openvpn@' service in systemd-like environment ...
Deleting 'systemd-nspawn@' service in systemd-like environment ...
Deleting 'configure-printer@' service in systemd-like environment ...
Deleting 'teamd@' service in systemd-like environment ...
Deleting 'ldconfig' service in systemd-like environment ...
Deleting 'fwupdate-cleanup' service in systemd-like environment ...
Deleting 'console-getty' service in systemd-like environment ...
Deleting 'systemd-machine-id-commit' service in systemd-like environment ...
Deleting 'fprintd' service in systemd-like environment ...
Deleting 'rescue' service in systemd-like environment ...
Deleting 'systemd-backlight@' service in systemd-like environment ...
Deleting 'corosync-notifyd' service in systemd-like environment ...
Deleting 'systemd-hibernate' service in systemd-like environment ...
Deleting 'corosync' service in systemd-like environment ...
Deleting 'ypserv' service in systemd-like environment ...
Deleting 'abrt-pstoreoops' service in systemd-like environment ...
Deleting 'mdmon@' service in systemd-like environment ...
Deleting 'NetworkManager-wait-online' service in systemd-like environment ...
Deleting 'systemd-tmpfiles-setup' service in systemd-like environment ...
Deleting 'sshd@' service in systemd-like environment ...
Deleting 'systemd-quotacheck' service in systemd-like environment ...
Deleting 'auth-rpcgss-module' service in systemd-like environment ...
Deleting 'systemd-udev-settle' service in systemd-like environment ...
Deleting 'systemd-udevd' service in systemd-like environment ...
Deleting 'debug-shell' service in systemd-like environment ...
Deleting 'sshd' service in systemd-like environment ...
Deleting 'instperf' service in systemd-like environment ...
Deleting 'plymouth-halt' service in systemd-like environment ...
Deleting 'systemd-ask-password-console' service in systemd-like environment ...
Deleting 'mdadm-grow-continue@' service in systemd-like environment ...
Deleting 'rpc-statd-notify' service in systemd-like environment ...
Deleting 'plymouth-poweroff' service in systemd-like environment ...
Deleting 'chronyd' service in systemd-like environment ...
Deleting 'systemd-journal-flush' service in systemd-like environment ...
Deleting 'gssproxy' service in systemd-like environment ...
Deleting 'cups' service in systemd-like environment ...
Deleting 'anaconda-tmux@' service in systemd-like environment ...
Deleting 'plymouth-reboot' service in systemd-like environment ...
Deleting 'ebtables' service in systemd-like environment ...
Deleting 'dhcrelay' service in systemd-like environment ...
Deleting 'initial-setup' service in systemd-like environment ...
Deleting 'systemd-hybrid-sleep' service in systemd-like environment ...
Deleting 'systemd-remount-fs' service in systemd-like environment ...
Deleting 'systemd-update-done' service in systemd-like environment ...
Deleting 'initrd-udevadm-cleanup-db' service in systemd-like environment ...
Deleting 'rpc-gssd' service in systemd-like environment ...
Deleting 'yppasswdd' service in systemd-like environment ...
Deleting 'sssd-pac' service in systemd-like environment ...
Deleting 'iscsiuio' service in systemd-like environment ...
Deleting 'sssd-ssh' service in systemd-like environment ...
Deleting 'fstrim' service in systemd-like environment ...
Deleting 'iptables' service in systemd-like environment ...
Deleting 'chrony-dnssrv@' service in systemd-like environment ...
Deleting 'rngd' service in systemd-like environment ...
Deleting 'brltty' service in systemd-like environment ...
Deleting 'initrd-cleanup' service in systemd-like environment ...
Deleting 'ostree-remount' service in systemd-like environment ...
Deleting 'firewalld' service in systemd-like environment ...
Deleting 'systemd-timedated' service in systemd-like environment ...
Deleting 'systemd-logind' service in systemd-like environment ...
Deleting 'canberra-system-shutdown-reboot' service in systemd-like environment ...
Deleting 'httpd' service in systemd-like environment ...
Deleting 'container-getty@' service in systemd-like environment ...
Deleting 'rpcbind' service in systemd-like environment ...
Deleting 'selinux-autorelabel-mark' service in systemd-like environment ...
Deleting 'initrd-parse-etc' service in systemd-like environment ...
Deleting 'arp-ethers' service in systemd-like environment ...
Deleting 'dm-event' service in systemd-like environment ...
Deleting 'systemd-bootchart' service in systemd-like environment ...
Deleting 'systemd-coredump@' service in systemd-like environment ...
Deleting 'systemd-modules-load' service in systemd-like environment ...
Deleting 'quotaon' service in systemd-like environment ...
Deleting 'fwupd' service in systemd-like environment ...
Deleting 'kdump' service in systemd-like environment ...
Deleting 'console-shell' service in systemd-like environment ...
Deleting 'abrt-ccpp' service in systemd-like environment ...
Deleting 'initial-setup-reconfiguration' service in systemd-like environment ...
Deleting 'systemd-resolved' service in systemd-like environment ...
Deleting 'virtlogd' service in systemd-like environment ...
Deleting 'mdadm-last-resort@' service in systemd-like environment ...
Deleting 'anaconda-sshd' service in systemd-like environment ...
Deleting 'yum-makecache' service in systemd-like environment ...
Deleting 'libvirtd' service in systemd-like environment ...
Deleting 'htcacheclean' service in systemd-like environment ...
Deleting 'upower' service in systemd-like environment ...
Deleting 'hypervfcopyd' service in systemd-like environment ...
Deleting 'ypbind' service in systemd-like environment ...
Deleting 'sssd-autofs' service in systemd-like environment ...
Deleting 'drblthincli' service in systemd-like environment ...
Deleting 'rpc-statd' service in systemd-like environment ...
Deleting 'dnfdaemon' service in systemd-like environment ...
Deleting 'nfs-blkmap' service in systemd-like environment ...
Deleting 'fedora-domainname' service in systemd-like environment ...
Deleting 'systemd-poweroff' service in systemd-like environment ...
Deleting 'iio-sensor-proxy' service in systemd-like environment ...
Deleting 'systemd-hwdb-update' service in systemd-like environment ...
Deleting 'dbus' service in systemd-like environment ...
Deleting 'usb_modeswitch@' service in systemd-like environment ...
Deleting 'systemd-journald' service in systemd-like environment ...
Deleting 'fedora-loadmodules' service in systemd-like environment ...
Deleting 'systemd-timesyncd' service in systemd-like environment ...
Deleting 'systemd-fsck-root' service in systemd-like environment ...
Deleting 'ostree-prepare-root' service in systemd-like environment ...
Deleting 'systemd-udev-trigger' service in systemd-like environment ...
Deleting 'hypervkvpd' service in systemd-like environment ...
Deleting 'tftp' service in systemd-like environment ...
Deleting 'mcelog' service in systemd-like environment ...
Deleting 'systemd-importd' service in systemd-like environment ...
Deleting 'kmod-static-nodes' service in systemd-like environment ...
Deleting 'cups-browsed' service in systemd-like environment ...
Deleting 'systemd-tmpfiles-setup-dev' service in systemd-like environment ...
Deleting 'abrt-journal-core' service in systemd-like environment ...
Deleting 'qemu-guest-agent' service in systemd-like environment ...
Deleting 'virtlockd' service in systemd-like environment ...
Deleting 'mdmonitor' service in systemd-like environment ...
Deleting 'alsa-state' service in systemd-like environment ...
Deleting 'ModemManager' service in systemd-like environment ...
Deleting 'ypxfrd' service in systemd-like environment ...
Deleting 'systemd-ask-password-plymouth' service in systemd-like environment ...
Deleting 'flatpak-system-helper' service in systemd-like environment ...
Deleting 'systemd-update-utmp-runlevel' service in systemd-like environment ...
Deleting 'sheepdog' service in systemd-like environment ...
Deleting 'nfs-utils' service in systemd-like environment ...
Deleting 'fwupd-offline-update' service in systemd-like environment ...
Deleting 'packagekit-offline-update' service in systemd-like environment ...
Deleting 'nfs-config' service in systemd-like environment ...
Deleting 'systemd-binfmt' service in systemd-like environment ...
Deleting 'iscsid' service in systemd-like environment ...
Deleting 'abrtd' service in systemd-like environment ...
Deleting 'bluetooth' service in systemd-like environment ...
Deleting 'arm-wol' service in systemd-like environment ...
Deleting 'multipathd' service in systemd-like environment ...
Deleting 'nfs-server' service in systemd-like environment ...
Deleting 'abrt-oops' service in systemd-like environment ...
Deleting 'systemd-update-utmp' service in systemd-like environment ...
Deleting 'systemd-initctl' service in systemd-like environment ...
Deleting 'switcheroo-control' service in systemd-like environment ...
Deleting 'openvpn-client@' service in systemd-like environment ...
Deleting 'avahi-daemon' service in systemd-like environment ...
Deleting 'lldpad' service in systemd-like environment ...
Deleting 'lvm2-monitor' service in systemd-like environment ...
Deleting 'systemd-reboot' service in systemd-like environment ...
Deleting 'NetworkManager' service in systemd-like environment ...
Deleting 'rtkit-daemon' service in systemd-like environment ...
Deleting 'plymouth-quit' service in systemd-like environment ...
Deleting 'dnsmasq' service in systemd-like environment ...
Deleting 'nfs-mountd' service in systemd-like environment ...
Deleting 'geoclue' service in systemd-like environment ...
Deleting 'systemd-sysctl' service in systemd-like environment ...
Deleting 'pppoe-server' service in systemd-like environment ...
Deleting 'systemd-user-sessions' service in systemd-like environment ...
Deleting 'plymouth-read-write' service in systemd-like environment ...
Deleting 'sssd-pam' service in systemd-like environment ...
Deleting 'openvpn-server@' service in systemd-like environment ...
Deleting 'canberra-system-bootup' service in systemd-like environment ...
Deleting 'numad' service in systemd-like environment ...
Deleting 'abrt-vmcore' service in systemd-like environment ...
Deleting 'polkit' service in systemd-like environment ...
Deleting 'dnf-makecache' service in systemd-like environment ...
Deleting 'plymouth-switch-root' service in systemd-like environment ...
Deleting 'lxdm' service in systemd-like environment ...
Deleting 'selinux-autorelabel' service in systemd-like environment ...
Deleting 'plymouth-start' service in systemd-like environment ...
Deleting 'systemd-networkd' service in systemd-like environment ...
Deleting 'systemd-exit' service in systemd-like environment ...
Deleting 'fedora-readonly' service in systemd-like environment ...
Deleting 'timedatex' service in systemd-like environment ...
Deleting 'radvd' service in systemd-like environment ...
Deleting 'systemd-rfkill' service in systemd-like environment ...
Deleting 'systemd-vconsole-setup' service in systemd-like environment ...
Deleting 'anaconda-nm-config' service in systemd-like environment ...
Deleting 'anaconda-noshell' service in systemd-like environment ...
Deleting 'nfs-idmapd' service in systemd-like environment ...
Deleting 'tcsd' service in systemd-like environment ...
Deleting 'user@' service in systemd-like environment ...
Deleting 'iscsi' service in systemd-like environment ...
Deleting 'udisks2' service in systemd-like environment ...
Deleting 'lvm2-pvscan@' service in systemd-like environment ...
Deleting 'psacct' service in systemd-like environment ...
Deleting 'sshd-keygen@' service in systemd-like environment ...
Deleting 'serial-getty@' service in systemd-like environment ...
Deleting 'fedora-import-state' service in systemd-like environment ...
Deleting 'ip6tables' service in systemd-like environment ...
Deleting 'systemd-networkd-wait-online' service in systemd-like environment ...
Deleting 'lvm2-lvmetad' service in systemd-like environment ...
Deleting 'anaconda-direct' service in systemd-like environment ...
Deleting 'realmd' service in systemd-like environment ...
Deleting 'plymouth-quit-wait' service in systemd-like environment ...
Deleting 'spice-vdagentd' service in systemd-like environment ...
Deleting 'systemd-fsck@' service in systemd-like environment ...
Deleting 'chrony-wait' service in systemd-like environment ...
Deleting 'systemd-kexec' service in systemd-like environment ...
Deleting 'dhcpd' service in systemd-like environment ...
Deleting 'systemd-hibernate-resume@' service in systemd-like environment ...
Deleting 'systemd-ask-password-wall' service in systemd-like environment ...
Deleting 'crond' service in systemd-like environment ...
Deleting 'sssd-sudo' service in systemd-like environment ...
Deleting 'atd' service in systemd-like environment ...
Deleting 'alsa-restore' service in systemd-like environment ...
Deleting 'wacom-inputattach@' service in systemd-like environment ...
Deleting 'abrt-xorg' service in systemd-like environment ...
Deleting 'accounts-daemon' service in systemd-like environment ...
Deleting 'systemd-random-seed' service in systemd-like environment ...
Deleting 'atop' service in systemd-like environment ...
Deleting 'systemd-sysusers' service in systemd-like environment ...
Deleting 'emergency' service in systemd-like environment ...
Deleting 'systemd-suspend' service in systemd-like environment ...
Deleting 'saslauthd' service in systemd-like environment ...
Deleting 'mlocate-updatedb' service in systemd-like environment ...
Deleting 'anaconda-shell@' service in systemd-like environment ...
Deleting 'halt-local' service in systemd-like environment ...
Deleting 'anaconda' service in systemd-like environment ...
Deleting 'rc-local' service in systemd-like environment ...
The startup services for DRBL client are:
firstboot rpcbind crond sshd ypbind messagebus dbus cups abrtd drblthincli arm-wol
Enabling service firstboot...
Enabling service rpcbind...
to target: 'multi-user.target'
'/tftpboot/node_root/etc/systemd/system/multi-user.target.wants/rpcbind.service' -> '/lib/systemd/system/rpcbind.service'
Enabling service crond...
to target: 'multi-user.target'
'/tftpboot/node_root/etc/systemd/system/multi-user.target.wants/crond.service' -> '/lib/systemd/system/crond.service'
Enabling service sshd...
to target: 'multi-user.target'
'/tftpboot/node_root/etc/systemd/system/multi-user.target.wants/sshd.service' -> '/lib/systemd/system/sshd.service'
Enabling service ypbind...
to target: 'multi-user.target'
'/tftpboot/node_root/etc/systemd/system/multi-user.target.wants/ypbind.service' -> '/lib/systemd/system/ypbind.service'
Enabling service messagebus...
Skip ...
Enabling service dbus...
Skip ...
Enabling service cups...
to target: 'printer.target'
'/tftpboot/node_root/etc/systemd/system/printer.target.wants/cups.service' -> '/lib/systemd/system/cups.service'
Enabling service abrtd...
to target: 'multi-user.target'
'/tftpboot/node_root/etc/systemd/system/multi-user.target.wants/abrtd.service' -> '/lib/systemd/system/abrtd.service'
Enabling service drblthincli...
to target: 'multi-user.target'
'/tftpboot/node_root/etc/systemd/system/multi-user.target.wants/drblthincli.service' -> '/lib/systemd/system/drblthincli.service'
Running: chroot /tftpboot/node_root/ /sbin/chkconfig --add drblthincli
Enabling service arm-wol...
to target: 'multi-user.target'
'/tftpboot/node_root/etc/systemd/system/multi-user.target.wants/arm-wol.service' -> '/lib/systemd/system/arm-wol.service'
Running: chroot /tftpboot/node_root/ /sbin/chkconfig --add arm-wol
Warning! The fine-tune files in dir /usr/share/drbl//setup/files/RH/FC25/systemd/system/ were not found. Using ocs-related systemd files in /usr/share/drbl//setup/files/RH/FC23/ for client's systemd service.
This may cause some problems to DRBL clients!
rm: cannot remove '/tftpboot/node_root/etc/udisks2/modules.conf.d': Is a directory
Using udev for clients... '/tftpboot/node_root/etc/systemd/system/default.target' -> '/lib/systemd/system/runlevel3.target'
Can't open /tftpboot/node_root/etc/xinetd.d/tftp: No such file or directory.
Deleting the accounts (except root) in the clients common root template... done!
Enabling the NIS client in the common root template... done!
Creating some necessary files in the clients common root template....ln: failed to create symbolic link '/tftpboot/node_root/var/run/run': File exists
ln: failed to create symbolic link '/tftpboot/node_root/var/lock/lock': File exists
.. done!
Creating DRBL client: cell108 192.168.0.108... Display manager:"gdm"...
Setting node 192.168.0.108 as normal_login... done!
Creating DRBL client: cell109 192.168.0.109... Pseudo client is created for DRBL SSI or clonezilla box mode! done!
Creating DRBL client: cell110 192.168.0.110... Pseudo client is created for DRBL SSI or clonezilla box mode! done!
Creating DRBL client: cell111 192.168.0.111... Pseudo client is created for DRBL SSI or clonezilla box mode! done!
Creating DRBL client: cell112 192.168.0.112... Pseudo client is created for DRBL SSI or clonezilla box mode! done!
Creating DRBL client: cell113 192.168.0.113... Pseudo client is created for DRBL SSI or clonezilla box mode! done!
Creating DRBL client: cell114 192.168.0.114... Pseudo client is created for DRBL SSI or clonezilla box mode! done!
Creating DRBL client: cell115 192.168.0.115... Pseudo client is created for DRBL SSI or clonezilla box mode! done!
Creating DRBL client: cell116 192.168.0.116... Pseudo client is created for DRBL SSI or clonezilla box mode! done!
Creating DRBL client: cell117 192.168.0.117... Pseudo client is created for DRBL SSI or clonezilla box mode! done!
Creating DRBL client: cell118 192.168.0.118... Pseudo client is created for DRBL SSI or clonezilla box mode! done!
Creating DRBL client: cell119 192.168.0.119... Pseudo client is created for DRBL SSI or clonezilla box mode! done!
Creating DRBL client: cell120 192.168.0.120... Pseudo client is created for DRBL SSI or clonezilla box mode! done!
Creating DRBL client: cell121 192.168.0.121... Pseudo client is created for DRBL SSI or clonezilla box mode! done!
Creating DRBL client: cell122 192.168.0.122... Pseudo client is created for DRBL SSI or clonezilla box mode! done!
Creating DRBL client: cell123 192.168.0.123... Pseudo client is created for DRBL SSI or clonezilla box mode! done!
Template client for DRBL SSI, Clonezilla box mode or Clonezilla live client is 192.168.0.108
Using template host /tftpboot/nodes/192.168.0.108
Generating SSH host keys for client 192.168.0.108 if they do not exist... RSA1 key generation failed!
Generating the files for DRBL single system image template... root... etc... var... Root's openssh public key... done!
Modifying option diskless_client_os in drbl-ocs.conf...
Disable the password in pxelinux simple menu for all clients...
Disabling PXE password in config file /tftpboot/nbi_img/pxelinux.cfg/default...
done!
Now add necessary services to this DRBL server: DHCP, TFTP, NFS, NIS...
Generating the NFS exports for DRBL clients...
Backup the original /etc/exports as /etc/exports.drblsave
Exporting to clients by IP address line-by-line...
The /etc/exports setting is ok now!
Now generate the firewall rules for NAT service...
Warning! /etc/sysconfig//iptables is renamed as iptables.drblsave!
Your firewall rules is overwritten!!! We set the NAT for clients to access this DRBL server!
Stop the NAT service first...
Now stop the NAT service...
Stop iptables service ,run :systemctl stop iptables.service
Save iptables service ,run :iptables-save
ip_forward is already on.
Now set the YP securenets...
Backup the original /var/yp/securenets as /var/yp/securenets.drblsave
The /var/yp/securenets setting is done!
Update YP...
Now add the service: dhcpd rpcbind iptables ypserv ypbind yppasswdd ypxfrd nfs rpc-statd nfs-server tftp
Force to add dhcpd service via systemd-like DRBL server...
Force to add rpcbind service via systemd-like DRBL server...
Force to add iptables service via systemd-like DRBL server...
Force to add ypserv service via systemd-like DRBL server...
Force to add ypbind service via systemd-like DRBL server...
Force to add yppasswdd service via systemd-like DRBL server...
Force to add ypxfrd service via systemd-like DRBL server...
Force to add nfs-server service via systemd-like DRBL server...
Force to add rpc-statd service via systemd-like DRBL server...
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
Force to add nfs-server service via systemd-like DRBL server...
Force to add tftp service via systemd-like DRBL server...
Now start the service: dhcpd rpcbind iptables ypserv ypbind yppasswdd ypxfrd nfs rpc-statd nfs-server tftp
Now start 'dhcpd' service in systemd-like environment...
Now start 'rpcbind' service in systemd-like environment...
Now start 'iptables' service in systemd-like environment...
Now stop 'ypserv' service in systemd-like environment...
Now start 'ypserv' service in systemd-like environment...
Now stop 'ypbind' service in systemd-like environment...
Now start 'ypbind' service in systemd-like environment...
Now stop 'yppasswdd' service in systemd-like environment...
Now start 'yppasswdd' service in systemd-like environment...
Now stop 'ypxfrd' service in systemd-like environment...
Now start 'ypxfrd' service in systemd-like environment...
Now start 'nfs-server' service in systemd-like environment...
Now start 'rpc-statd' service in systemd-like environment...
Now stop 'nfs-server' service in systemd-like environment...
Now start 'nfs-server' service in systemd-like environment...
Now start 'tftp' service in systemd-like environment...
ip_forward is already on.
The display manager in this DRBL server is "gdm"
Setting the graphic mode for node IP = 192.168.0.108...
Turn on the GDM remote access...
You have to restart the X-window to make the modified gdm config work! !!Note!! Make sure that gdm is running so that the destination clients can work with gdm on this server!
grep: /etc/X11/gdm/gdm.conf: No such file or directory
Can't find the PID file in the configuration file, going to try:
/var/run/gdm.pid
/var/run/gdm.pid doesn't exist, perhaps GDM isn't running
Setting the terminal mode for DRBL clients...
Set system config DRBL_THIN_CLIENT=on for client 192.168.0.108
done !
Clean all the previous saved config file if they exist...done!
Turn on the boot prompt for PXE client...done!
Turn on the thin client option in PXE menu...done!
Modifying /tftpboot/nbi_img/pxelinux.cfg/default to let DRBL client use text PXE boot menu... done!
DRBL SSI mode. Set clientdir opt for label drbl in pxelinux config...
Setting drbl_mode="drbl_ssi_mode" in /etc/drbl/drbl_deploy.conf and /etc/drbl/drblpush.conf... done!
Clonezilla box mode. Set clientdir opt for label clonezilla in pxelinux config...
Setting clonezilla_mode="clonezilla_box_mode" in /etc/drbl/drbl_deploy.conf and /etc/drbl/drblpush.conf... done!
You have to use "dcs" -> clonezilla-start to start Clonezilla service, so that there will be a Clonezilla menu when client boots
No hidden label Clonezilla-live was found! Skip it.
No hidden menuentry with ID clonezilla-live-client found! Skip it.
Some files are found in /usr/share/drbl//postrun/drbl/. Run them now...
*****************************************************.
Enjoy DRBL!!!
http://drbl.org; http://drbl.nchc.org.tw
NCHC Free Software Labs, Taiwan. http://free.nchc.org.tw
*****************************************************.
If you like, you can reboot the DRBL server now to make sure everything is ready...(This is not necessary, just an option)
*****************************************************.
The DRBL server is ready! Now set the client machines to boot from PXE. (refer to http://drbl.org for more details)
P.S. The config file is saved as /etc/drbl/drblpush.conf. Therefore if you want to run drblpush with the same config again, you may run it as: drblpush -c /etc/drbl/drblpush.conf
root@one /etc/drbl #
