OpenStack is Network intensive. The setup I had previously, based around a Juniper Router, did not have enough Ports to reflect a real OpenStack deployment. I decided to forgo GigE speeds and get an older Cicso Catalyst 2960-WS Switch. Here is the new setup.
I do this infrequently enough that I want to record a reminder how I do it:
sudo cp ~/Downloads/rhel-server-7.6-x86_64-kvm.qcow2 /var/lib/libvirt/images/tower.qcow2
sudo virt-install --vcpus=2 --name tower --ram 4096 --import --disk /var/lib/libvirt/images/tower.qcow2
Not all of my virtual machines run on OpenStack; I have to run a fair number of virtual machines on my personal workstation via libvirt. However, I like using the cloud versions of RHEL, as they most closely match what I do run in OpenStack. The disconnect is that the Cloud images are designed to accept cloud-init, which pulls the ssh public keys from a metadata web server. Without that, there are no public keys added to the cloud-user account, and the VM is unaccessable. Here is how I add the ssh keys manually.
Ozz did a fantastic job laying out the rules around policy. This article assumes you’ve read that. I’ll wait.
Lets say you are an administrator of an OpenStack cloud. This means you are pretty much all powerful in the deployment. Now, you need to perform some operation, but you don’t want to give it full admin privileges? Why? well, do you work as root on your Linux box? I hope note. Here’s how to set up a self trust for a reduced set of roles on your token.
The Game of Go is still pretty much the ultimate strategy game. No other game distills strategy to its essence, in such simplicity, and thus lets the complexity emerge.
The board is simplicity itself: a 19 X 19 Grid:
Standard Go board
One aspect of Go is that you start from the corners, build a semi-secure formation, and then grow out from there.
For example, here is a recent game of mine in the early stages:
Both my opponent and I have staked out positions in the corners.
What if the board was a little different?
My laptop is my Demo machine. I need to be able to run the Red Hat cloud Suite of software on it. I want to install this software the same way a customer would. However, much of this software is server side software, and my machine was registered as a workstation. This means the Red Hat Content network won’t show me the server yum repositories. Here is how I converted my machine to be a server.
If I want to run software collections code without enabling bash and running interactively, I have to pass the whole command on the command line like this:
scl enable rh-maven35 "mvn package"
I’ll need to use this form to run from Ansible.
My new role has me paying attention to the Network side of cloud a lot more than I had to in the past. One thing I’ve noticed about Networking is that it has a lot of acronyms, and people that work in it tend to throw them out in context and move on. This is my collection of recent acronyms and their meanings.
I will continue to update this one as I come across additional relevant terms and acronyms.