Laptop Hacking Coffee

User Tools

Site Tools

Trace:
wiki:challenges:linuxsysadmin

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
wiki:challenges:linuxsysadmin [2021/09/30 20:01]
admin 		wiki:challenges:linuxsysadmin [2021/09/30 20:04] (current)
admin
Line 15: Line 15:
  
   Where is [[https://en.wikipedia.org/wiki/Hyper-V|Hyper-V]]?   Where is [[https://en.wikipedia.org/wiki/Hyper-V|Hyper-V]]?
-        Hyper-V requires more overhead and has no real advantages over the other options. As another hit, it is based on + 
-        Microsoft Windows and not any kind of *nix or Linux. If you're on this page, you are probably not interested in learning +''Hyper-V requires more overhead and has no real advantages over the other options. As another hit, it is based on 
-        the Microsoft ecosystem at this point anyways. You can use Hyper-V if you truly wish, but I do not advise it.+Microsoft Windows and not any kind of *nix or Linux. If you're on this page, you are probably not interested in learning 
 +the Microsoft ecosystem at this point anyways. You can use Hyper-V if you truly wish, but I do not advise it.''
  
     2. At this point you have a choice between two things to do, you can either continue to the next step and run everything as per normal, or you can setup routing software to help containerize this project so you don't accidentally break your entire home network at some point and anger those you happen to live with. For this I personally prefer [[https://www.pfsense.org/|PFSense]] to manage this, however there are other options such as [[https://vyos.io/|VyOS]] or [[https://mikrotik.com/software|MicroTik RouterOS]] or this fork of PFSense [[https://opnsense.org/|OPNsense]].     2. At this point you have a choice between two things to do, you can either continue to the next step and run everything as per normal, or you can setup routing software to help containerize this project so you don't accidentally break your entire home network at some point and anger those you happen to live with. For this I personally prefer [[https://www.pfsense.org/|PFSense]] to manage this, however there are other options such as [[https://vyos.io/|VyOS]] or [[https://mikrotik.com/software|MicroTik RouterOS]] or this fork of PFSense [[https://opnsense.org/|OPNsense]].
Line 23: Line 24:
     3. Inside of that KVM hypervisor, install a provisioning management server. Use CentOS 7 as the distro for all work below. (For bonus points, set up errata importation on the CentOS channels, so you can properly see security update advisory information.)     3. Inside of that KVM hypervisor, install a provisioning management server. Use CentOS 7 as the distro for all work below. (For bonus points, set up errata importation on the CentOS channels, so you can properly see security update advisory information.)
  
-    For management servers there are two suggestions that come up [[https://spacewalkproject.github.io/|Spacewalk]] which is what Red Hat's Satellite 5 was based off of, or there is [[https://github.com/Katello/katello|Katello]] which is what Red Hat's current Satellite 6 is based off of. As a note for later, the Katello agent also has inclusion of Puppet which you mind find useful later and is included in a later section of this challenge.+''For management servers there are two suggestions that come up [[https://spacewalkproject.github.io/|Spacewalk]] which is what Red Hat's Satellite 5 was based off of, or there is [[https://github.com/Katello/katello|Katello]] which is what Red Hat's current Satellite 6 is based off of. As a note for later, the Katello agent also has inclusion of Puppet which you mind find useful later and is included in a later section of this challenge.''
  
     4. Create a VM to provide named and dhcp services to your entire environment. Set up the dhcp daemon to use the provisioning management server from step 2 server as the pxeboot machine (thus allowing you to use PXE to do unattended OS installs). Make sure that every forward zone you create has a reverse zone associated with it. Use something like "internal.virtnet" (but not ".local") as your internal DNS zone.     4. Create a VM to provide named and dhcp services to your entire environment. Set up the dhcp daemon to use the provisioning management server from step 2 server as the pxeboot machine (thus allowing you to use PXE to do unattended OS installs). Make sure that every forward zone you create has a reverse zone associated with it. Use something like "internal.virtnet" (but not ".local") as your internal DNS zone.
Line 73: Line 74:
 ---- ----
  
-====== Requirements ======+===== Requirements =====
  
 ==== Hardware ==== ==== Hardware ====
wiki/challenges/linuxsysadmin.1633050086.txt.gz · Last modified: 2021/09/30 20:01 by admin

Page Tools