How to Directly Connect SUSE Manager to Red Hat Content Delivery Network

Methods to Receive Your Red Hat Updates and Patches
SUSE Manager

Cameron Seader, Sales Engineer, SUSE

Donald Vosburg, Sales Engineer, SUSE

The described solution allows you to directly connect SUSE Manager to the Red Hat Content Delivery Network (CDN) to retrieve your software updates and patches.

This is useful if you plan on continuing your agreement with Red Hat, and/or you do not want to use Expanded Support from SUSE. It is also useful when you have multiple distributions that you want to update and patch from SUSE Manager. Finally, it is helpful if you use an updated code stream of the Satellite 5 series, and continue your use of an enhanced road map to the Spacewalk project.

You must have a current subscription with Red Hat. This in no way requires that you have a subscription to Satellite Server from Red Hat.

1.0 Import Red Hat Entitlement and CA Certificate

During the next few paragraphs, you will learn how to import the Red Hat CA and entitlement certificate.

NOTE: Expiration Dates for Entitlement Certificates

Entitlement certificates have embedded expiration dates tied to the length of the support subscription. You must repeat this process with updated entitlement certificates as needed to avoid disruption in channel mirroring.

1.1 Entitlement Certificate

Red Hat Subscription Manager is a local service which tracks installed products and subscriptions on a local system to help manage subscription assignments. To obtain your certificates, you must register your system using this subscription manager tool supplied by Red Hat.

  1. Register with the subscription manager tool from your Red Hat client. It will prompt you for your user name and password for authentication on the Red Hat Portal:

    subscription-manager register

  2. Navigate to the location of your entitlement certificate and key, and copy these files to where your Web browser connected to SUSE Manager can open them:

    cd /etc/pki/entitlement/

You will see two files with the data file format extension .pem (Program Editor macro). One is the certificate, and the other is the key and it has the word key in the file name.

1.2 Red Hat CA Certificate

The next step is to get the Red Hat CA Certificate file. It is located on this same Red Hat system in the file /etc/rhsm/ca/redhat-uep.pem. Place this file in the same location where, in the previous section, you put the entitlement certificate.

1.3 Obtain Repository URL list

Use the subscription manager tool to obtain the URL’s of the repositories you want to mirror:

subscription-manager repos

1.4 Import

Now you are ready to import the Red Hat CA Certificate and Entitlement Certificate into SUSE Manager for software repository mirroring. You must create three entries here: one each for the entitlement certificate, the entitlement key, and the Red Hat CA certificate.

Start your SUSE Manager. Go to the Systems tab at the top. Click Autoinstallation on the left pane. Then click GPG and SSL Keys also on the left pane, as you can see it from the screenshot below.

Figure 1 SUSE Manager GPG Public Keys and SSL Certificates

Click Create Stored Key/Cert on the right. Another screen opens where you can fill in the required information.

Figure 2 SUSE Manager Create GPG/SSL Keys

Enter the following values, and ensure you enter the date:

  • Description: Entitlement-Cert-date
  • Type: Ensure you select SSL
  • Select file to upload: Browse to where you saved the Entitlement Certificate .pem file and select it.

Click the Create Key button at the bottom.

Figure 3 SUSE Manager Create Key Button

Repeat the above steps for the Entitlement Key and change the values to match the following:

  • Description: Entitlement-key-date
  • Type: SSL
  • Select file to upload: Browse to the location where you saved the Entitlement key .pem file and select it.

Repeat the above steps for the Red Hat CA Certificate (redhat-uep) and change the values to match the following:

  • Description: redhat-uep
  • Type: SSL
  • Select file to upload: Browse to the location where you saved the Red Hat CA Certificate and select it.

You now have imported the Entitlement certificate, the Entitlement key and the Red Hat CA into SUSE Manager for use. Your outcome should look like the screen below:

Figure 4 SUSE Manager Imported Red Hat Certificates

2.0 Create Software Repositories

To mirror the software from the Red Hat CDN, you need to create custom channels and repositories in SUSE Manager that are linked to the CDN with their respective URL. This will only work if you have entitlements to these products in your Red Hat Portal. To create these software repositories you need to perform the following actions.

On your SUSE Manager screen, go to the Software(or in older SUSE Manager versions, to the Channels) tab at top. Click Manage Software Channels on the left pane. Then click Manage Repositories also on the left pane.

Figure 5 SUSE Manager Repositories

Click Create Repository. The following screen opens, where you can enter the required information to create the repository.

Figure 6 SUSE Manager Create Repository

Fill in the fields with values, follwing the example below:

  • Repository Label: rhel-7-server-rpms
  • Repository URL: https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os/
  • Has Signed Metadata?: Uncheck (Uncheck for all Red Hat Enterprise Repositories)
  • SSL CA Certificate: redhat-uep
  • SSL Client Certificate: Entitlement-Cert-date
  • SSL Client Key: Entitlement-Key-date

These steps need to be repeated for the Products / Repository URLs you define for your environment.

Repository Values

Use the output of repository URL’s obtained earlier from the subscription manager tool to create other repositories to which you are entitled. Mirror only the content which you need to manage your systems.

3.0 Create Software Channel Delivery

Next step is to create corresponding channels to which you assign these repositories.

Click Channels, after that click Manage Software Channels .

3.1 Parent Channels Example

Click Create Channel and fill in the fields with at least the following values:

  • Channel Name: RHEL 7 x86_64
  • Channel Label: rhel7-x86_64-server
  • Parent Channel: None
  • Architecture: x86_64
  • Repository Checksum Type: sha1
  • Channel Summary: RHEL 7 x86_64
  • Organization Sharing: Public

After you have filled in the values, click again Create Channel.

On the screen below, click the tab Repositories, and mark the check box next to the appropriate repository.

Figure 7 Create Parent Channels

On the next screen, click the tab Sync and set your preferred recurring schedule for synchronization for this repository. You can also select Sync Now to launch the synchronization immediately.

Figure 8 Synchronize Parent Channels

NOTE: Mirroring Duration

Red Hat Server OS channels can grow to be very large. Thus it can take several hours to complete mirroring.

3.2 Child Channels example

Click Create Channel and fill in the fields with at least the following values:

  • Channel Name: RHEL 7 x86_64
  • Channel Label: rhel7-x86_64-extras
  • Parent Channel: rhel7-x86_64-server (from drop-down box)
  • Architecture: x86_64
  • Repository Checksum Type: sha1
  • Channel Summary: RHEL 7 x86_64 Extras
  • Organization Sharing: Public

After you have filled in the values, click again Create Channel.

On the screen below, click the tab Repositories, and mark the check box next to the appropriate repository.

Figure 9 Create Parent Channels

On the next screen, click the tab Sync and set your preferred recurring schedule for the synchronization of this repository. Ensure you scroll down and click Schedule. You can also select Sync Now to launch the synchronization immediately.

Figure 10 Create Parent Channels

Now you can proceed to create the activation key in the SUSE Manager Web UI, and assign appropriate channels to it.

4.0 Registration

To register your systems, follow the steps described in the sections below.

4.1 Bootstrap Repository Creation

SUSE Manager subscriptions entitle everyone to the tools channels for Red Hat Expanded Support (RES) distributions. Any Red Hat Enterprise Linux or CentOS 6 or 7 system should use these to create the proper bootstrap repository for either traditional or salt-minion connectivity.

  1. Add the corresponding SUSE Manager RES tools channel and allow it to synchronize from SUSE Customer Center. You will need the 0-package parent channel and the tools. Here is an example command to add it for RES6 on AMD64/Intel 64:

    mgr-sync add channels rhel-x86_64-server-6 res6-suse-manager-tools-x86_64
  2. Follow the instructions to synchronize your base media as a child repository for your distribution based on Red Hat Enterprise Linux, as explained in the SUSE Manager Wiki:

    https://wiki.microfocus.com/index.php/SUSE_Manager/Sync_RHEL_media

  3. Create a bootstrap repository for your Red Hat Enterprise Linux clients with

    mgr-create-bootstrap-repo --with-custom-channels

This will use the base media channel to capture needed dependencies. Ensure that it completes without error.

4.2 Minion Registration

On the client machine(s), perform the following steps to register the minion using a bootstrap script (recommended):

  1. If needed, regenerate the bootstrap script with the Salt option enabled:

    mgr-bootstrap --salt --script=bootstrap-salt.sh
  2. Download and run the appropriately edited bootstrap script after adding the correct activation key and other parameters. This will install the necessary Salt packages, set the proper activation key, and start the salt-minion service:

    curl -Sks http://<server>/pub/bootstrap/bootstrap-salt.sh | /bin/bash
  3. In the SUSE Manager Web UI, go to Salt, click Onboarding and accept the minion's key.

After a few minutes, the new minion will appear in your list of systems with the channels assigned in the activation key you specified in the bootstrap process.

5.0 References

For more information, see:

7.0 GNU Free Documentation License

Copyright (C) 2000, 2001, 2002 Free Software Foundation, Inc. 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

0. PREAMBLE

The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or non-commercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

1. APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.

A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.

The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.

A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.

A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.

The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.

2. VERBATIM COPYING

You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly display copies.

3. COPYING IN QUANTITY

If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.

4. MODIFICATIONS

You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

  1. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.

  2. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement.

  3. State on the Title page the name of the publisher of the Modified Version, as the publisher.

  4. Preserve all the copyright notices of the Document.

  5. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.

  6. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.

  7. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.

  8. Include an unaltered copy of this License.

  9. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.

  10. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.

  11. For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.

  12. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.

  13. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version.

  14. Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.

  15. Preserve any Warranty Disclaimers.

If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.

You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.

5. COMBINING DOCUMENTS

You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".

6. COLLECTIONS OF DOCUMENTS

You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.

7. AGGREGATION WITH INDEPENDENT WORKS

A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.

8. TRANSLATION

Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.

If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.

9. TERMINATION

You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

10. FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.

Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.

ADDENDUM: How to use this License for your documents
Copyright (c) YEAR YOUR NAME.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
A copy of the license is included in the section entitled "GNU
 Free Documentation License".

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the "with...Texts". line with this:

with the Invariant Sections being LIST THEIR TITLES, with the
Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.

If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.

If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.