add joe clarke to admins

proxmoz-zfs.md

@@ -87,6 +87,8 @@ Then install ProxMox
 The first thing is set the password to something nasty.  And remember to
 also set the user password.
 
+geshyeeth3
+
 I also have to get the network configured properly.  In my example
 
     cat > /etc/network/interfaces << EOF
@@ -137,8 +139,7 @@ apt install emacs-nox unbound chrony rsync sudo screen debian-goodies bsd-mailx
     
 Fix sudoers
 ```
-cd /etc/sudoers.d
-cat > local << EOF
+cat > /etc/sudoers.d/local << EOF
 %sudo   ALL=(ALL) NOPASSWD: SETENV: ALL
 EOF
 /usr/sbin/usermod -a -G sudo randy
@@ -172,8 +173,9 @@ cat > /etc/ssh/sshd_config.d/99sshd-local.conf << EOF
 # somewhat open-ended attack surface, and tunneled plaintext
 # passwords, which we just don't allow at all.
 
-UsePAM no
+#UsePAM no
 PasswordAuthentication no
+KbdInteractiveAuthentication no
 EOF
 systemctl restart ssh
 ```
@@ -225,7 +227,8 @@ mode, which means this instal may be borked already but almost
 certainly will be if you update grub at this point, so you might want
 to figure that out first.
 
-Update `/etc/network/interfaces` to add two bridged LANs
+I tend to do this later, but Update `/etc/network/interfaces` to add
+two bridged LANs
 ```
 # The loopback network interface
 auto lo
@@ -267,6 +270,7 @@ iface vmbr0 inet static
         bridge_maxwait  0
 ```
 
+
 ## Use Ansible to Install and Configure a Bunch of Things
 
 Now the barrage of ansible, which for me is based on my Mac laptop.
@@ -372,13 +376,21 @@ systemctl restart smartmontools.service
 
 Follow [Install Proxmox VE on Debian 13 Trixie](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie)
 
-If `unbound` does not work, it is probably fighting with apparmor.  i
-just nuke it
+WARNING!!!
+
+Before "Install the Proxmox VE Packages" check that unbound is working,
+i.e. do host addresses resolve.
+
+If `unbound` does not work, after the mid-install `reboot`, it is
+probably fighting with apparmor.  i just nuke it
 
 ```
 aa-teardown
 aa-status 
-systemctl disable apparmor 
+systemctl disable apparmor
+```
+and then
+```
 systemctl restart unbound.service
 ```
 
@@ -432,8 +444,10 @@ root password.  E.g. `https://vm2.dfw.rg.net:8006`
 
 ## Cluster Issues
 
-I found it more reliable to create the cluster before creating the ZFS
-image pools.  I do not know why.
+I found it more reliable to join/create the cluster before creating
+the ZFS image pools.  I do not know why.
+
+WARNING!
 
 But only create cluster if this is the first node in the cluter.
 
@@ -445,6 +459,9 @@ When adding nodes to a cluster.
 
 ## Set Up ZFS Image Pool
 
+I have found it is less pain if the new node joins the cluster before
+creating the ZFS pool.
+
 Remember, partition 4 was saved for ZFS.  So, in the gooey, select the
 server, then ZFS, and then CreateZFS.  I used RAIDz2 as a compromise.
 It should offer you a list of the #4 partition(s).  Accept the offer.
@@ -493,11 +510,12 @@ qm create --net0 virtio,bridge=br-lan,firewall=1 ...
 
 Replication LAN probably needs set-up
 ```
-cat /etc/pve/datacenter.cfg
+cat > /etc/pve/datacenter.cfg << EOF
 crs: ha-rebalance-on-start=1,ha=static
 ha: shutdown_policy=migrate
 keyboard: en-us
 migration: insecure,network=10.0.0.0/24
+EOF
 ```
 
 ## User Management
@@ -517,6 +535,7 @@ Create Usrrs
 pveum user add randy@pam --email "randy@pg.com" --firstname Randy --lastname Bush --groups admins
 pveum user add sra@pam --email "sra@hactrn.net" --firstname Rob -lastname Austein --groups admins
 pveum user add hak@pam --email "hak@flyingpoodle.com" --firstname Hans --lastname Kuhn --groups admins
+pveum user add jclarke@pam --email "jclarke@cisco.com" --firstname Joe --lastname Clarke --groups admins
 ```
 
 You will want mail to the root account to work.  [The long and complex
@@ -536,4 +555,4 @@ At this point, you should be able to CreateVM using an ISO from
 an ISO you just downloaded the library.
 
 ---
-2026.08.23
+2026.09.07