cloudXabide | to the Cloud

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-...

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...

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

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.

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). ...

There is quite a bit of nuance in managing accounts in AWS.  One particular issue I see come up is with managing account lifecycles (i.e. if a person wants to have "temp" accounts to provide for people to "play" and learn).  This is simply not easily accomplished.  However, there are procedural ways to deal with this if folks need this type of functionality.  I have given it the following moniker: "account recycling" The idea is that you would have different account types: "core" accounts under the control of your master/payer account - and these do not get recycled. Long lived line of business accounts - hosting production, etc... long lived developer accounts - (still trying to work through how these would be managed) "burner" accounts - preset limits for usage, pre-determined length of time the account is available The idea of the burner account is that you would create a "pool" of accounts that could be provided ...

I put away my pitchforks for protesting Microsoft almost 2 decades ago.  At first I was in the Microsoft is the devil camp... then I started working on Solaris... and then AIX... and then Linux (SuSE) and finally Red Hat Enterprise Linux.  With each iteration along that timeline, I continued to care less and less about what was going on with Microsoft and Windows.  When Microsoft started to show up in the headlines regarding Linux compatibility, Red Hat collaboration, Open Source contributions, I was minimally apprehensive and was actually rather optimistic that times were changing and they saw the light. Today - I am about to install the Linux version of Visual Studio Code (relegating Atom IDE to be the failback). sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc sudo su -c 'echo -e "[code]\nname=Visual Studio Code\nbaseurl=https://packages.microsoft.com/yumrepos/vscode\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsof...