drpfeature-dhcp-debug¶
- Intent
- This feature is used to setup and debug drp-provision dhcp.
- Success
- Demonstrate dhcp debugging on an isolated network using drpcli, drp-ux and virtual-box PXE client.
Manual Steps
- Configure drpfeature-test-network (mikrotek 192.168.88.1 router)
- Install drp-provision via drp-quickstart in the drpfeature-test-macosx configuration
- Configure drpfeature-test-vbox (virtual box)
- Start drp-provision
- Browse to RackN-Portal at https://192.168.88.9:8092 and login with rocketskates r0cketsk8ts
- Browse to Subnets add or enable subnet en0 192.168.88.9/24
- Disable all other Subnets
- Browse to Leases
- Clear or validate all current dhcp leases
- Browse to Boot ISOs
- Verify or load the following
- CentOS-7-x86_64-Minimal-1708.iso
- sledgehammer-f5ffd3ed10ba403ffff40c3621f1e31ada0c7e15.tar
- Browse to Info & Preferences
- In System Preferences set the following
- Default Stage -> discover
- Default BootEnv -> sledgehammer-wait
- Unknown BootEnv -> discovery
- Click Save
- Browse to Profiles
- Should have some clusters
- k8s-cluster-Install
- k8s-cluster-ram
- Browse to Bulk Actions
- Browse to Workflow
- Fire up test drpfeature-test-vbox vm’s bm1, bm2, bm3, bm4, bm5 and bm6
- Browse to RackN-Portal Machines
- Verify the bm1-6 machines are Stage: discover BootEnv: sledgehammer
Note
Start drp-provision
sudo ./dr-provision --static-ip=192.168.88.9 --base-root=/Users/msops/Code/drpfeature/drpisolated/drp-data --local-content="" --default-content=""
Note
Generate admin.conf
./drpcli profiles get k8s-cluster-ram param krib/cluster-admin-conf > admin.conf
Note
Get node info via kubectl
kubectl --kubeconfig=admin.conf get nodes
Note
SETUP kubctl PROXY
kubectl --kubeconfig=admin.conf proxy
Video Track
- Begin configuration to start k8s-cluster-install
- tc715 Set KRIBnode[1..4] to Stages -> Mount Local Disk
- tc736 Show LIVE events of above
- tc743 Click on KRIBnode1 to show what that node will go through
- tc722 Set KRIBnode[4..8] to Profiles -> k8s-cluster-install
- tc798 Set KRIBnode[4..8] to Boot Environmens -> centos-7-install
- tc802 Set KRIBnode[4..8] to Plugin Action -> powercycle
- General Exlaining while k8s-cluster builds
- tc860 Look into what k8s-cluster-ram in Profiles does (verbal explain)
- tc918 Navigate to Stages select krib-install which has task krib-install
- tc935 krib-install verbal explain of how tasks, jobs, alerts and workflow are composeable
- tc953 Pull up krib-install.sh.tmpl and explain template that is executed by runner
- tc990 Go look at current status of DRIBnode1 in Machines it is in docker-install stage of Stages
- tc1079 Show Jobs and bring up a job progress of a job log on a node.
- tc1102 Navigate to machine via the link in the Jobs listing to check on machine task which is now krib-install
- tc1104 Navigate to task via the link in the machine view to see the log of the krib-install task
- tc1115 Navigate to Profiles show k8s-cluster-ram see that node 56… has krib/cluster-master parameter so it WON the master election
- tc1160 Go back to SLIDES… finish slide talk esp about dynamic tokens, configuration injection and bootstraping
- tc1238 Go back to Profiles and refresh then pull up k8s-cluster-ram again. You see new parameter for cluster-join-command
- The COOL NEW STUFF
- tc1262 Show cluster-admin-conf and use that to create admin.conf
- tc1284 Generate admin.conf
- tc1318 Now go get node info via kubectl (note this is on the local system going cloud cluster)
- tc1337 SETUP kubectl PROXY via
- tc1375 FOR THE WIN: browse to http://localhost:8001 to get to the remote kubeadmin dashboard