|
|
| (3 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| | | | |
| − |
| |
| − |
| |
| − | <source lang="text">
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | https://www.ebay.co.uk/b/yama-buggy-parts/bn_7024825240
| |
| − | https://www.ebay.co.uk/itm/Yama-2-stroke-1-5-scale-Petrol-RC-buggy-front-wheel-1-pair-/163665921047
| |
| − | https://www.youtube.com/watch?v=A1zmhxcUOxw
| |
| − |
| |
| − | [21/06/2018 15:36] Olly Bellamy:
| |
| − | What Ports are Connected to What?
| |
| − |
| |
| − | 172.16.112.232 2306 Te 1/53/1
| |
| − | 172.16.112.233 2306 Te 1/53/2
| |
| − | 172.16.112.234 2306 Te 1/53/1
| |
| − | 172.16.112.235 2306 Te 1/53/2
| |
| − | 172.16.112.236 - -
| |
| − | 172.16.112.237 - -
| |
| − |
| |
| − |
| |
| − | Does SO-4048 serve data AND iscsi?
| |
| − |
| |
| − | No, just iscsi.
| |
| − |
| |
| − |
| |
| − | Does the SAN management network run through the SO-4048?
| |
| − |
| |
| − | Yes.
| |
| − |
| |
| − |
| |
| − |
| |
| − | This may help
| |
| − | https://community.jisc.ac.uk/library/janet-services-documentation/payments-and-charges
| |
| − |
| |
| − |
| |
| − | </source>
| |
| − |
| |
| − | <div style="text-align:center;">'''Red Hat Certification.'''</div>
| |
| − |
| |
| − |
| |
| − | '''Chapters'''
| |
| − |
| |
| − |
| |
| − | [[#chap1installation|1. Installation]]
| |
| − |
| |
| − | [[#chap2essentialtools|2 ]][[#chap2essentialtools|]][[#chap2essentialtools|Using essential tools]]
| |
| − |
| |
| − | [[#chap3essentialtools|3. Essential File Management Tools]]
| |
| − |
| |
| − | [[#chap4textfiles|4. Working with Text Files]]
| |
| − |
| |
| − | [[#chap5connectingto|5. Connecting to Red Hat Linux 7]]
| |
| − |
| |
| − | [[#chap6usergroup|6. User and Group Management]]
| |
| − |
| |
| − | [[#chap7permissionsmanagement|7. Permissions Management]]
| |
| − |
| |
| − | [[#chap8configuringnetworking|8. Configuring Networking]]
| |
| − |
| |
| − | [[#chap9processmanagement|9. Process Management]]
| |
| − |
| |
| − | [[#chap10virtualmachines|10.]][[#chap10virtualmachines| ]][[#chap10virtualmachines|Working with Virtual Machines]]
| |
| − |
| |
| − | [[#chap11installsoftwarepackages|11. Installing Software Packages]]
| |
| − |
| |
| − | [[#chap12schedulingtasks|12. Scheduling Tasks]]
| |
| − |
| |
| − | [[#chap13configuringlogging|13. Configuring Logging]]
| |
| − |
| |
| − | [[#chap14managingpartitions|14. Managing Partitions]]
| |
| − |
| |
| − | [[#chap!5lvm|15. Managing LVM Logical Volumes]]
| |
| − |
| |
| − | [[#chap16kernelmanagement|16. Basic Kernel Management]]
| |
| − |
| |
| − | [[#chap!7basicapache|17. Configuring a Basic Apache Server]]
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | '''1. Red Hat Installation'''
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | '''2. Using Essential Toosl'''
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | '''3. Essentila File Management Tools'''
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | '''4. Working with text files'''
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | '''5. Connecting to Red Hat Linux 7'''
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | '''6. User and Group Management'''
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | '''7. Permissions Management'''
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | '''8. Configuring Networking'''
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | '''9. Process Management'''
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | '''10. Working with Virtual Machines'''
| |
| − |
| |
| − |
| |
| − | QEMU (Quick Emulator) this does the disk format of image files.
| |
| − |
| |
| − |
| |
| − | It offers an infrastructural server that consists of multiple hypervisor nodes
| |
| − |
| |
| − | that are managed from a central RHEV Manager node, on which a web user interface
| |
| − |
| |
| − | makes managing a complex environment easy.
| |
| − |
| |
| − |
| |
| − | To access VMs that are offered through KVM, you use libvirtd. Libvirtd is a process
| |
| − |
| |
| − | that sits between the virtualization layer and the application that an administrator
| |
| − |
| |
| − | is using to access the VMs. Without libvirtd, you cannot manage VMs. Virtual
| |
| − |
| |
| − | machine management options also are configured through the libvirtd configuration
| |
| − |
| |
| − | file /etc/libvirt/libvirtd.conf.
| |
| − |
| |
| − |
| |
| − | Although the method to connect remotely directly to '''libvirtd '''works well and is convenient
| |
| − |
| |
| − | for hypervisors that have a minimal number of software packages installed,
| |
| − |
| |
| − | alternatively you can use Secure Shell (SSH) from virt-manager to connect to
| |
| − |
| |
| − | remote libvirtd processes.
| |
| − |
| |
| − | If you are experiencing problems accessing VMs, libvirtd is the primary suspect,
| |
| − |
| |
| − | and you should at least ensure that it is running, by using the systemctl status -l
| |
| − |
| |
| − | libvirtd command. In Listing 10.1 , you can see how this command shows that libvirtd
| |
| − |
| |
| − | is running; the command also shows information about recent activity on the
| |
| − |
| |
| − | process .
| |
| − |
| |
| − |
| |
| − | systemctl status -l libvirtd
| |
| − |
| |
| − |
| |
| − | '''Making your server a KVM host.'''
| |
| − |
| |
| − |
| |
| − | cat /proc/cpuinfo - '''vmx '''on an intel CPU, and '''svm '''on an AMD CPU.
| |
| − |
| |
| − |
| |
| − | cat /proc/cpuinfo | egrep ‘<span style="background-color:#ffff00;">svm|vmx</span>’
| |
| − |
| |
| − |
| |
| − | yum groupinstall “Virtualization Host â€.
| |
| − |
| |
| − | /var/lib/libvirt/images. - check space
| |
| − |
| |
| − |
| |
| − | '''NOTE''' As an alternative to working with disk image files, you may prefer working
| |
| − |
| |
| − | with LVM logical volumes as the storage backend. This offers some advantages,
| |
| − |
| |
| − | such as the possibility to easily create backups by using the LVM snapshot feature.
| |
| − |
| |
| − | For this reason, LVM is often used as a storage backend in production KVM
| |
| − |
| |
| − | servers.
| |
| − |
| |
| − |
| |
| − | '''KVM Host networking'''
| |
| − |
| |
| − |
| |
| − | brctl show
| |
| − |
| |
| − |
| |
| − | Accessing virtual machines
| |
| − |
| |
| − | â– SSH into the VM
| |
| − |
| |
| − | â– Through Virtual Machine Manager
| |
| − |
| |
| − | â– Through GNOME Boxes
| |
| − |
| |
| − | â– Using virt-viewer
| |
| − |
| |
| − | â– Optionally, through third-party utilities.
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | Accessing virtual Machines from a text only console.
| |
| − |
| |
| − | This is from the KVM host
| |
| − |
| |
| − | grubby --update-kernel=ALL --args=“console=ttyS0â€
| |
| − |
| |
| − | reboot the vm
| |
| − |
| |
| − | virsh console samder-vm1
| |
| − |
| |
| − |
| |
| − | '''Managing virtual machines from the command line'''
| |
| − |
| |
| − | '''virsh commands'''
| |
| − |
| |
| − | list <nowiki>= </nowiki>active vms
| |
| − |
| |
| − | list -all <nowiki>= </nowiki>all, including non active
| |
| − |
| |
| − | help
| |
| − |
| |
| − | shutdown <vmname> shuts down properly
| |
| − |
| |
| − | destroy <vmname> pulls the power plug
| |
| − |
| |
| − | edit <vmname> edit the xml config file.txt
| |
| − |
| |
| − | console <vmname> connects from KVM host console
| |
| − |
| |
| − | start <vmname> Starts a VM
| |
| − |
| |
| − | reboot <vmname> reboots a vm
| |
| − |
| |
| − |
| |
| − | '''Google'''
| |
| − |
| |
| − | virsh list [ --inactive | --all]
| |
| − |
| |
| − |
| |
| − | '''From Red Hat Portal - managing guests '''
| |
| − |
| |
| − | help Prints basic help information.
| |
| − | list Lists all guests.
| |
| − | dumpxml Outputs the XML configuration file for the guest.
| |
| − | create Creates a guest from an XML configuration file and starts the new guest.
| |
| − | start Starts an inactive guest.
| |
| − | destroy Forces a guest to stop.
| |
| − | define Outputs an XML configuration file for a guest.
| |
| − | domid Displays the guest's ID.
| |
| − | domuuid Displays the guest's UUID.
| |
| − | dominfo Displays guest information.
| |
| − | domname Displays the guest's name.
| |
| − | domstate Displays the state of a guest.
| |
| − | quit Quits the interactive terminal.
| |
| − | reboot Reboots a guest.
| |
| − | restore Restores a previously saved guest stored in a file.
| |
| − | resume Resumes a paused guest.
| |
| − | save Save the present state of a guest to a file.
| |
| − | shutdown Gracefully shuts down a guest.
| |
| − | suspend Pauses a guest.
| |
| − | undefine Deletes all files associated with a guest.
| |
| − | migrate Migrates a guest to another host.
| |
| − |
| |
| − | '''Misc :'''
| |
| − | version Displays the version of virsh
| |
| − | nodeinfo Outputs information about the hypervisor
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | '''Reset root password'''
| |
| − |
| |
| − | append the following to the linux16 line at grub - init=bin/sh then control-x
| |
| − |
| |
| − | <div style="color:#000000;">mount -o remount, rw /</div>
| |
| − |
| |
| − | <div style="color:#000000;">( reset the password )</div>
| |
| − |
| |
| − | <div style="color:#000000;"><span style="background-color:transparent;">touch /.autorelabel</span></div>
| |
| − |
| |
| − | <div style="color:#000000;"><span style="background-color:transparent;">/sbin/init</span><span style="background-color:transparent;"> </span><span style="background-color:#ff6600;">this didnt work, couldnt connect to init daemon</span></div>
| |
| − |
| |
| − |
| |
| − | <div style="color:#000000;"><span style="background-color:transparent;">or /sbin/reboot</span></div>
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | '''11. Installing Software Packages'''
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | '''12. Scheduling Tasks'''
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | '''13. Configuring Logging'''
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | '''14. Managing Partitions'''
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | '''15. Managing LVM Logical Volumes'''
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | '''16. Basic Kernel Management'''
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | '''17. Configuring a Basic Apache Server'''
| |
