Coyote's Blog

 I'm still using VCS/Infoscale for parts of my homelab. This allows me to sometimes catch issues ([1], [2] and [3]) that others have not found before. The Legacy GUI One way to administer VCS with a GUI is to use the VCS gui (hagui). Unfortunately, the rpm of VRTScscm which was provided by Veritas is quite dated and on my RHEL systems, it tends to 'freeze' from time to time. I recently noticed that while VRTScscm hadn't been updated since the 6.0.z times, a few updates had been released for Windows platforms only: When I tried the 7.4.1 Windows version on Win10, it worked a lot better than the 6.0.1 Linux version (no freezes, etc..) so I decided to investigate if I could update the Linux version with the bits from the Windows version. Interestingly, it turned out to be quite easy.. Updating the JARs from the Linux version with the GUI JARs from the Windows version delivered a working 7.4.1 on Linux. (and no more GUI freezes!). Java is cross-platform and this is clearly

 Red Hat Satellite provides distribution for rpms and containers for many Red Hat Products. It's an over-simplification but it works well enough for the purpose of this post. As someone who works with RHOSP and RHEL on a daily basis, I find it convenient to have a local Red Hat Satellite VM and all of my permanent or temporary RHEL/RHOSP nodes connect to it. Why use Red Hat Satellite at home? There are a few reasons: - It provides a sort of local Internet Cache of rpms and containers: I might be working on RHOSP 16.2 and perhaps I will need to stand up a temporary RHOSP13 cloud to assist a customer or work on a BZ. This is usually fine but it could impact the Home bandwidth at the worst moment possible, especially when the rest of the Family is taking remote classes. - It's always faster to cache everything locally and in some cases of Network congestion in the middle of the day, it helped me save the virtual deployments I was launching in my Lab. Why did I want a VM for someth