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

Let’s learn how to create an organization and location on Foreman/Satellite server using the hammer command-line-interface. In this example, I’m going to create an organization called: Operation and assign its location to Boston. On the Foreman server, excute the following commands: [root@foreman ~]# hammer organization create --name Operations Organization created. [root@foreman ~]# hammer location create --name Boston Location created. [root@foreman ~]# hammer organization add-location --name Operations \ > --location Boston The location has been associated. Let’s verify it: ...

When I setup Foreman (Satellite) server, I didn’t have Ansible support enabled. Here is how it can be done later on. If we only need Ansible support, it’s sufficient to just run this command: # foreman-installer \ --enable-foreman-plugin-ansible \ --enable-foreman-proxy-plugin-ansible Just a note for myself, I also need Remote Execution enabled if I want to run Ansible playbooks as Job Templates. # foreman-installer \ --enable-foreman-plugin-remote-execution \ --enable-foreman-proxy-plugin-remote-execution-ssh Note that the remote execution feature is enabled by default on Foreman/Satellite server. The Smart Proxy or Capsule server, on the other hand, must be specifically enabled with the above installed command. ...

The steps to build an RPM package: Download the source code Create the spec file (use the rpmdev-newspec command) Build the package (use the rpmbuild command) GPG sign the package (use the rpmsign command) Test the package (use rpm -qip command) In this post, I’m going to learn to create an RPM package of fpaste-4.0.1.1.tar.gz on Red Hat Enterprise Linux 7 (variant). First we need to ensure the necessary packages are installed: ...