Posts

Apple OSX Catalina and VMware vCenter Server Appliance.. ugh

OSX Catalina came with some rather annoying challenges: dropped support for 32-bit apps.  I don't play Steam games that much on my Mac now that I am stuck at home all the time.  So, not a big deal. implemented a bunch of "gatekeeper" security measures.  Now, typically I would say:  if you need to circumvent security ("Disable SELinux" - for example), you're probably doing it wrong.  But, the case of all the hand-holdy, lockdown stuff, it's pretty annoying.  Several things you cannot simply "accept the risk" and move on, you get constant reminders.  And it is interesting that whenever Microsoft does this sort of thing, it's widely discussed they are vilified.  Somehow, when Apple does this.. meh, just the cost of doing business. The challenges, themselves, are not the point of this post.  The point is you need to do some stuff if you expect to use Mac OSX Catalina to deploy VMware vSphere 6.7 U3 - vCenter Server Appliance. Download the ISO (...

Software RAID via kickstart (not cloud, sorry)

A bunch of the following specifics are out of scope, but I am including them anyhow # System bootloader configuration bootloader --location=mbr --boot-drive=sda --append=" crashkernel=auto hpsa.hpsa_allow_any=1 hpsa.hpsa_simple_mode=1 console=tty0 console=ttyS0,9600n8" # Partition clearing information #ignoredisk --only-use=sda zerombr clearpart --all --initlabel --drives=sda,sdb,sdc # Disk partitioning information part /boot/efi --fstype="efi" --fsoptions="umask=0077,shortname=winnt" --ondisk=sda --size=256 part /boot --fstype="xfs" --ondisk=sda --size=1024 part pv.01 --fstype="lvmpv" --ondisk=sda --size=51200 --grow volgroup vg_rhel7 --pesize=4096 pv.01 logvol /              --fstype="xfs"  --size=10240 --name=root     --vgname=vg_rhel7 logvol /home          --fstype="xfs"  --size=1024  --name=home     --vgname=vg_rhel7 logvol /tmp           --fstyp...

I minishift myself this weekend.

The point of this post (at this time, anyhow) is to remind myself of the stupid issue I ran in to with the install/deploy of minishift on Fedora 31.  Totally my fault, but not exactly intuitive what I happened to have done incorrectly.  Let's roll... I had ran through the standard install docs (which were fairly generic) and the following would occur: $ minishft start ...   ...      ... -- Minishift VM will be configured with ...    Memory:    8 GB    vCPUs :    2    Disk size: 40 GB -- Starting Minishift VM .... FAIL E0118 20:17:12.659441  145997 start.go:494] Error starting the VM: Error creating new host: dial tcp: missing address. Retrying. Error starting the VM: Error creating new host: dial tcp: missing address I had install the driver using $ sudo curl -L https://github.com/docker/machine/releases/download/v0.16.2/docker-machine-Linux-x86_64 -o /usr/local/bin/docker-machine-driver-...

Kind of a Gluster ... Installation woes on 3.11

Update (and TL;DR:) - make sure you are using the right version of Ansible.  For whatever reason I had believed that I should be at 2.6.  Once I updated to 2.8 everything ran correctly. This is probably one of those times when my persistence coupled with OCD behavior was NOT on my side... I have spent literally weeks (elapsed) and probably days (actual) of time trying to deploy my OCP 3.11 Cluster to use Gluster for the Persistent Storage (apps and infra).  And it has failed.. and failed... and failed miserably. Started off with one hypervisor - Xeon and 96GB of memory, 2 x TB of HDD. VMs would (eventually) lock up and require hard restarts.  Hmm.. memory? So, I went and fired up my 3 x HP ML30s (each with 64GB and 1 TB of HDD) Still no love. I'm still fairly novice using Ansible and the scripts/role/playbooks/whatever they're called are actually pretty complex, not idempotent, have to be run in a specific order, etc... Huh? So - there will be a bunc...

Cloud It Out Loud #clouditoutloud

I did a thing... I need a "complete" AWS environment to do some testing... and didn't want to botch my "personal" existing environment which owns my other domains, etc...  Anywho... at some point the following URL will be hosting something https://clouditoutloud.com

HomeLab - Sophos XG SSL VPN and Comcast

Ugh... Comcast.  This sucked particularly much as this was my first attempt to configure a VPN back to my HomeLab and therefore was not sure what options I should have *known* would work.  Anywho... Sophos SSL VPN uses 8443 by default.  I spent a few hours trying to get through the config on the Sophos and my Linux client.  Nothing was working. For giggles I changed the Sophos to use 443, and then updated my client on my Linux workstation.  And suddenly it all works.  Fowk.  Tried 8443 again.  No love. I don't want to utilize port 443 as I intend to actually host some web apps for testing.  So, I have finalized on an "alternate" port which had to be configured on both the Sophos and the Linux client. I'l be doing a better write-up about this later.  I still need to figure out how to configure all this via the Gnome Network-Manager GUI.

Red Hat - KVM Guest connectivity to KVM Host via HTTP

It had been about 10 months since I had done any "hardcore" Linux stuff and I need to get ramped up on a bunch of Red Hat technologies again - namely OCP and Satellite.  So, I decided I would use my laptop to spin-up a bunch of VMs.  I build my own "kickstart" environment using ISOs on my "KVM Host" to build the KVM Guests.  They are NAT'd using 192.168.122.0/24 address space and virbr0. I had everything setup and when I would monitor the console of the VM I was building, I would see "connection refused" when it would go to pull any content (i.e. my kickstart configuration). Initially I thought I simply had to update the "public" firewall zone. Then, I assumed I had to add the "virbr0" or "virbr0-nic0" to the zone's interfaces. Nope... Then I ran "setenforce 0" to see if SELinux was hosing it up.  Nope. chcon -Rvv --type=httpd_sys_content_t /var/www/html.  Nope (still a good measure though). ...