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