Announcement: Red Hat Satellite 6 Provisioning Guide

Latest response

We've seen a lot of discussions and requests for more provisioning content for the Red Hat Satellite 6 documentation. We just want to let you know that we published a Provisioning Guide on November 28th. This guide provides information to help you install and configure Red Hat Satellite, and get it ready to provision physical and virtual hosts. This includes setting up the required network topology, configuring the necessary services, and providing all of the other configuration information needed to provision hosts on your network. (This guide is aimed primarily at Satellite administrators with sound networking knowledge and skills. )

You can find it at https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html/Provisioning_Guide/index.html

We would like to hear from you if you have any feedback or questions about the guide. Feel free to contact us using the details provided in the guide or in this discussion post!

Cheers,
Red Hat Satellite Documentation Team

Responses

Thanks for the update, Megan

Hi folks,
Just bumping this thread to check if anyone had any feedback or comments on this new guide. Please feel free to let us know your experience with it and if you have any suggestions for improvement.
- Dan

Procedure 3.5. To Upload a Puppet Module to the Repository:

Download the motd puppet module from https://forge.puppetlabs.com/jeffmccune/motd. The file that you download will have a .tar.gz extension.
Click Content → Products and then click Custom Products in the Name field.
On the Repositories tab, click Puppet Modules to modify the Puppet Modules repository.
In the Upload Puppet Module section, click Browse, and navigate to the motd module that you downloaded.
Click Upload. Satellite displays Content successfully uploaded after the upload completes successfully.

Results in:

Error during upload: Task f7bf5019-2dbc-4c21-a228-9683727bdd2f: Errno::ENOENT: No such file or directory - /tmp/RackMultipart20150120-8867-qkam0f

At which point I have to dig through a task list, down into some "Dynflow console" (from which there is no way back to the admin interface), skip the install, and then resume it to get the task lock to clear.

I have no idea what this error means or how to fix it.

After wiping out the Satellite instance and starting over following only the steps in this Provisioning document, this step worked. Previously, I had installed from the Satellite 6 ISO.

There's a typo in the table listing the installer options. It reads "--capsule-puppet-ca" when it should read "--capsule-puppetca".

https://db.tt/2acRVxBw

Hi James,

I created https://bugzilla.redhat.com/show_bug.cgi?id=1184671 for this.

Thanks for picking it up.

This has been patched and will be in the next release.
Thanks again.

Between section 2.1.2 and 2.2 there should be a section on firewall configuration.

Hi James,
I created a bug for this - https://bugzilla.redhat.com/show_bug.cgi?id=1194114
Thanks for the feedback,
Megan

After first logging in to the website you are presented with this sentences:

Before you can use Satellite 6 for the first time there are a few tasks that must be performed. You must decide how you wish to use the software, and update the primary settings file config/settings.yaml and the settings to indicate your selections.

The "config/settings.yaml" is not a link, but the word "settings" immediately following it is. Does that link take you to the "config/settings.yaml"? Because the way it's worded makes them sound like separate entities. And there isn't any information on the page nor the Provisioning Guide about where the "config/settings.yaml" is located.

Hi James,
I created this bug (https://bugzilla.redhat.com/show_bug.cgi?id=1194120) for this issue.
Thanks letting us know,
Megan

In section 4.6, "Creating and Editing Activation Keys", is it necessary to select the "Custom Products" subscription that was created in an earlier section? Or, since it is a locally created and managed subscription, will it be available by virtue of being included in the Content View created in section 4.4?

you still need the subscription for Custom Products added to your activation key, even thou it is in the Content View. We may in future releases make this automatic but for now it is still required to add subscriptions for all products in the Content View

In section 1.3.1, I think the instruction for registering should read:

subscription-manager register --type=satellite

I have found that if I do not specify the type at this point, then the system gets registered in such a fashion that I am unable to download the subscription manifest because the system is not registered as a satellite system.

Hi James,
I created another bug for this - https://bugzilla.redhat.com/show_bug.cgi?id=1194118
Thanks again for the feedback,
Megan

We were going to try Satellite 6.0, however, there's no channel dumps in ISO format. All of our satellites (eight of them) are disconnected on secure networks (there is a very compelling reason they are all disconnected). We acquire our base and incremental channels through the Customer Portal.

According to the documentation, there are no plans on having the channels available for download for Satellite 6. For my environment, standing up a public facing CDN synchronization server is out of our hands, and next to impossible to attain. We are going to address this with Red Hat, through a number of means.

R. Hinton,
We hope to have channel dump style ISOs available in the coming months for Satellite 6, yourself and others have voiced your concern that the current routine is not an acceptable mechanism.

Feel free to open a ticket and we can discuss in further detail your needs and the timeline of the availability.

Thanks Mike - That is fantastic news, and we seriously appreciate that greatly. We agree with you that the method (currently in) the documentation would not be acceptable for numerous reasons. We shall certainly submit a case under our various accounts.

Mike, we submitted a case (01350136), we will submit a case in our other affected accounts as well..
Thanks much