I have a need to setup a virtual network on a VM-host server. Usually, I just use the virt-manager gui application to create this task. However, I’d like to do this via command line this time. Why? Well, why not? It’s always fun to learn new thing. :) libvirt keeps network configuration in XML files under /etc/libvirt/qemu/networks/. Here is what I have on one of my machines: # ls -1 /etc/libvirt/qemu/networks/*xml /etc/libvirt/qemu/networks/classroom.xml /etc/libvirt/qemu/networks/default.xml /etc/libvirt/qemu/networks/kubernetes.xml /etc/libvirt/qemu/networks/minikube-net.xml /etc/libvirt/qemu/networks/other.xml /etc/libvirt/qemu/networks/storage.xml /etc/libvirt/qemu/networks/student.xml We can use also list all the available libvirt-related virtual networks using virsh command: ...

Last night I published 4 or 5 of blog posts related to the Foreman/Satellite server. Well, it wasn’t a coincidence, it was me cramming the last minute for the Red Hat Satellite 6 Administration exam today. It’s also known as EX403. Needless to say, I didn’t know what was in the exam, and I can’t share what was in exam I had taken today. What I can share with you is that I passed EX403! ...

In this blog post, I’m going to practice publishing and promoting content views using the hammer CLI. I already know how to do this using the Satellite/Foreman web UI. First, I’m going to create the Base content view for Operations organization and Boston location. [root@foreman ~]# hammer content-view create \ > --name Base --organization Operations \ > --description 'Base Packages' Content view created. [root@foreman ~]# hammer content-view list --organization Operations ----------------|---------------------------|--------------------------|-----------|---------------------|--------------- CONTENT VIEW ID | NAME | LABEL | COMPOSITE | LAST PUBLISHED | REPOSITORY IDS ----------------|---------------------------|--------------------------|-----------|---------------------|--------------- 6 | Base | Base | false | | ----------------|---------------------------|--------------------------|-----------|---------------------|--------------- The next step is adding the repos to the content view. I want to add the CentOS 8 BaseOS repo. ...

In this post, I will create a new life-cycle environment paths for the Operations organization that includes life-cycle environments named Deveopment, QA, and Production. Let’s list the current life-cycle environment for Operations organization. [root@foreman ~]# hammer lifecycle-environment list --organization Operations ---|---------|------ ID | NAME | PRIOR ---|---------|------ 6 | Library | ---|---------|------ When we create our first environment, we’ll need to use the ID of the Library, which is 6 in this case. Alternatively, we can just “Library” as the argument to --prior option. ...

In this blog post, I’m going to show how to add a new product caled EPEL8 and populate it with a repository from EPEL 8. There should be 3 main steps: Create a Content-Credentials which stores the package signing key of the product or repository Create a new Product Create a new Repository Firt thing first, let’s create a new content-credentials named RPM-GPG-KEY-EPEL-8 with the contents from the EPEL 8’s GPG signing key. ...