GC Programming

It’s really worth taking a step back now and looking at what you’ve really done, if you’ve been putting the
picture together: you have set up the skeleton of a small startup company, with name, mail, web, and file
servers,
and once you do the AWS lab,
a co
de repository
and two sites linked by VPN, one in a private cloud,
one in a public cloud … without buying a single piece of hardware or going even once to a data center.

CS 470: Unix/Linux Sysadmin
Summer 2021 Lab 9
patching, grading, and the reaper
‼ IMPORTANT NOTE: EXPECT AND WATCH FOR ERRATA HERE ‼
At last, handing in and evaluating all your homework.
It’s really worth taking a step back now and looking at what you’ve really done, if you’ve been putting the
picture together: you have set up the skeleton of a small startup company, with name, mail, web, and file
servers, and once you do the AWS lab, a code repository and two sites linked by VPN, one in a private cloud,
one in a public cloud … without buying a single piece of hardware or going even once to a data center.
Not bad for six weeks, eh? Six weeks ago, lots of you were total noobs. Pat yourself on the back.
It’s also really worth noting that we cut lots of corners due to:
•
•
•
limitations of our hardware and network setup, like not having a publicly routable IP,
our private network, like cutting out encryption certificates for services, which we would never,
ever do in a real company, and
to make sure no more was spent out of pocket, otherwise we’d each have registered a domain
name and set up real inbound/outbound mail servers.
Please keep all this in mind when and if using the materials as a reference.
part zero: grading configuration
Your grading configuration should be your first five VMs, up and running, from labs 1, 2, 3, 4, and 5.
Lab 6 is graded via the lab 2 VM and the artifacts you were asked to store on your NFS server at the end of
that lab.
part one: patching
1. First, let’s bring the base operating system software up to date on each VM. In real life, we often test
patches in test environments before deploying them to production environments.
OpenBSD:
$ sudo syspatch
You set up a cron job to update the ports tree … but you haven’t been looking at the results. Add the
following command as a cron job, and run it immediately to see if any of your ports have gotten out of
date …
# /usr/ports/infrastructure/bin/pkg_outdated
… and if they have, update them!
1
2. FreeBSD:
$ sudo freebsd-update fetch install
We set up an up-to-date ports tree with portsnap … this is the command we use to check if any ports
or packages are outdated …
$ pkg version -l ” cs470.local)
download_frd=1)
errata v5, 8/16/2021:
• Fixed broken SSH config snippet in step #9. (cs470 -> cs470.local)
(https://sdsu.instructure.com/files/3193716/download?
• Clarified grading setup in partJul
zero.
lecture_210707.pdf
7, 2021
Jul 7, 2021
Peter Bartoli (https://sds…
download_frd=1)
• Solaris memory guidance in step #5.
• NEW step #12 for feedback pipeline for lab 6 grading bugs in the reaper.
lab6v3.pdf
lecture_210712.pdf
(https://sdsu.instructure.com/files/3205508/download?
Jul 12, 2021
Jul 12, 2021
download_frd=1)
!! IMPORTANT NOTE: EXPECT AND WATCH FOR ERRATA HERE !!
lecture_210719.pdf
(https://sdsu.instructure.com/files/3226618/download?
Jul 19, 2021
download_frd=1)
3.6 MB
1.1 MB
96 KB
(
129 KB
Peter Bartoli (https://sds… 1.2 MB
At last, handing in and evaluating all your homework.
Jul 19, 2021
Peter Bartoli (https://sds… 37 KB
It’s really worth taking a step back now and looking at what you’ve really done, if you’ve been putting the
picture together: you have set up the skeleton of a small startup company, with name, mail, web, and file
(https://sdsu.instructure.com/files/3277054/download?
servers, and once you do the AWS lab,
a code repository and two
sites linked by VPN, one
in a private cloud,
lecture_210802.pdf
Aug 2, 2021
Aug 2, 2021
Peter Bartoli (https://sds… 35 KB
download_frd=1)
one in a public cloud … without buying a single piece of hardware or going even once to a data center.
Not bad for six weeks, eh? Six weeks ago, lots of you were total noobs. Pat yourself on the back.
lecture_210809.pdf
MoU.pdf
(https://sdsu.instructure.com/files/3316200/download?
Aug 9, 2021
download_frd=1)
Aug 9, 2021
Peter Bartoli (https://sds… 32 KB
Aug 2, 2021
Aug 2, 2021
Peter Bartoli (https://sds… 65 KB
(https://sdsu.instructure.com/files/3211686/download?
Jul 14, 2021
download_frd=1)
Jul 14, 2021
Peter Bartoli (https://sds… 27 KB
(https://sdsu.instructure.com/files/3248920/download?
Jul 26, 2021
download_frd=1)
Jul 26, 2021
Peter Bartoli (https://sds… 58 KB
Jul 7, 2021
Peter Bartoli (https://sds… 136 KB
(https://sdsu.instructure.com/files/3276361/download?
download_frd=1)
notes_lab_210714.pdf
schedule.pdf
(https://sdsu.instructure.com/files/3192604/download?
Jul 7, 2021
download_frd=1)
syllabus.pdf
https://sdsu.instructure.com/courses/59703/files?preview=3372190
Page 1 of 2
Files
8/16/21, 10:28 AM
All My Files
https://sdsu.instructure.com/courses/59703/files?preview=3372190
Page 2 of 2
CS 470: Unix/Linux Sysadmin
Summer 2021 Lab 9
patching, grading, and the reaper
errata v2, 8/12/2021:
• Added in lab 7 to part zero and steps 4 and 7; again, sorry for the late edition, but it had to be done for
completeness.
errata v3, 8/12/2021:
• Added lab 7 to step #8.
• Added clarification in step #9 to make sure EDORAS is in your known_hosts file. If you’re SSHing into
EDORAS for the first time from any lab VM with the reaper, SSH agent forwarding will appear to fail.
errata v4, 8/13/2021:
• Fixed broken SSH config snippet in step #9. (cs470 -> cs470.local)
errata v5, 8/16/2021:
• Fixed broken SSH config snippet in step #9. (cs470 -> cs470.local)
• Clarified grading setup in part zero.
• Solaris memory guidance in step #5.
• NEW step #12 for feedback pipeline for lab 6 grading bugs in the reaper.
‼ IMPORTANT NOTE: EXPECT AND WATCH FOR ERRATA HERE ‼
At last, handing in and evaluating all your homework.
It’s really worth taking a step back now and looking at what you’ve really done, if you’ve been putting the
picture together: you have set up the skeleton of a small startup company, with name, mail, web, and file
servers, and once you do the AWS lab, a code repository and two sites linked by VPN, one in a private cloud,
one in a public cloud … without buying a single piece of hardware or going even once to a data center.
Not bad for six weeks, eh? Six weeks ago, lots of you were total noobs. Pat yourself on the back.
It’s also really worth noting that we cut lots of corners due to:
•
•
•
limitations of our hardware and network setup, like not having a publicly routable IP,
our private network, like cutting out encryption certificates for services, which we would never,
ever do in a real company, and
to make sure no more was spent out of pocket, otherwise we’d each have registered a domain
name and set up real inbound/outbound mail servers.
Please keep all this in mind when and if using the materials as a reference.
part zero: grading configuration
Your grading configuration should be your first five VMs, up and running on your computer, plus lab seven.
You will run the reaper from your VMs from labs 1, 2, 3, 4, 5, and 7.
1
Lab 6 is graded via the lab 2 VM and the artifacts you were asked to store on your NFS server at the end of
that lab.
part one: patching
1. First, let’s bring the base operating system software up to date on each VM. In real life, we often test
patches in test environments before deploying them to production environments.
OpenBSD:
$ sudo syspatch
You set up a cron job to update the ports tree … but you haven’t been looking at the results. Add the
following command as a cron job, and run it immediately to see if any of your ports have gotten out of
date …
# /usr/ports/infrastructure/bin/pkg_outdated
… and if they have, update them!
2. FreeBSD:
$ sudo freebsd-update fetch install
We set up an up-to-date ports tree with portsnap … this is the command we use to check if any ports
or packages are outdated …
$ pkg version -l ”