Red Hat Satellite Server 6.2 Pattern

Transcription

1 Red Hat Satellite Server 6.2 Pattern

2 Table of contents Overview What is a Satellite Server? Why did we need a new Satellite Server 6.2 pattern? Architecture High Level Red Hat Satellite 6 System Architecture Content Life Cycle in Red Hat Satellite 6 Usage scenarios How to configure and setup new Red Hat registration files with Satellite 6.2 How to generate the Satellite manifest file. How to deploy a Satellite Server 6.2 using the pattern How to configure the Satellite Server after pattern deployment Troubleshooting / Deep Dive Summary and References Closing remarks 2

3 Overview What is a Satellite Server? Why did we need a new Satellite Server 6.2 pattern?

4 What is a Satellite Server? A Satellite server registers with Red Hat Subscription Management, mirrors all relevant software like security errata and bug fixes, and provides this together with locally added software and configuration to the attached servers. The managed hosts register against the local Satellite server and access the provided resources like software packages, patches, configuration, etc. while they also provide information about the current health state of the server to the Satellite We provide a pattern to automatically stand a satellite 6.2 server with minimum input from our users. The satellite server deployed is within the rack environment, and can be used to manage and patch PureApplication linux VMs. 4

5 Why did we need a new Satellite Server 6.2 pattern? We used to have Satellite Server 5.6 pattern prior to the release. Due to the end of support of existing satellite 5.6 servers on Oct by Red Hat, customers can only deploy satellite 6 servers afterwards, thus demanding a new pattern. Satellite 5.6 pattern will not work after Oct 31, 2017, but existing satellite 5.6 servers can continue to work until Jan 2019 as long as they have underdone the migration from RHN (Red Hat Network) to RHSM (Red Hat Subscription Management) before Oct 31, More info on RHN to RHSM migration at IBM tech note 01.ibm.com/support/docview.wss?uid=swg

6 Architecture High Level Red Hat Satellite 6 System Architecture Content Life Cycle in Red Hat Satellite 6

7 High-level Architecture of Red Hat Satellite 6 External Content Sources The Red Hat Satellite Server can consume diverse types of content from various sources. The required connection is the one with Red Hat Customer Portal, which is the primary source of software packages, errata, Puppet modules, and container images. In addition, you can use other supported content sources (Git repositories, Docker Hub, Puppet Forge, SCAP repositories) as well as your organization s internal data store. Red Hat Satellite Server The Red Hat Satellite Server enables you to plan and manage the content life cycle and the configuration of Capsule Servers and hosts through GUI, CLI, or API. Managed Hosts Hosts are the recipients of content from Capsule Servers. Hosts can be either physical or virtual (deployed on KVM, VMware vsphere, OpenStack, Amazon EC2, Rackspace Cloud Services, Google Compute Engine, or in a Docker container). The Satellite Server can have directly managed hosts. The base system running a Capsule Server is also a managed host of the Satellite Server. 7

8 Content Life Cycle in Red Hat Satellite 6 By default, each organization has a Library of content from external sources. Content Views are subsets of content from the Library created by intelligent filtering. You can publish and promote Content Views into life cycle environments (typically Dev, QA, and Production). When creating a Capsule Server, you can choose which life cycle environments will be copied to that Capsule and made available to managed hosts. Content Views can be combined to create Composite Content Views. It can be beneficial to have a separate Content View for a repository of packages required by an operating system and a separate one for a repository of packages required by an application. One advantage is that any updates to packages in one repository only requires republishing the relevant Content View. You can then use Composite Content Views to combine published Content Views for ease of management. 8

9 Usage scenarios How to configure and setup new Red Hat registration files with Satellite 6.2 How to generate the Satellite manifest file How to deploy a Satellite Server 6.2 using the pattern How to configure the Satellite Server after pattern deployment

10 How to setup new Red Hat registration files with Satellite 6.2 Do you have a Satellite Server and want to add entitlements to existing Red Hat account? If yes skip this step If no - create a Enterprise Red Hat account at Call IBM support or open a PMR to request Satellite Server registration codes Entitlements depend on # of compute nodes in the rack 10

11 How to setup new Red Hat registration files with Satellite 6.2 (cont.) Activate all subscription codes here: 11

12 How to setup new Red Hat registration files with Satellite 6.2 (cont.) Accept Red Hat Terms 12

13 How to setup new Red Hat registration files with Satellite 6.2 (cont.) Confirm NEW subscription activation 13

14 How to setup new Red Hat registration files with Satellite 6.2 (cont.) Congratulations! Subscriptions are successfully added 14

15 How to setup new Red Hat registration files with Satellite 6.2 (cont.) NOTE: Subscription will be activated within 30 minutes. 15

16 How to setup new Red Hat registration files with Satellite 6.2 (cont.) subscriptions -> Active subscriptions (under My Subscriptions section)and confirm subscriptions are added to your account 16

17 How to generate the Satellite manifest file Go to Satellite Organizations section 17

18 How to generate the Satellite manifest file (cont.) Subscription Management Application -> Satellite tab click on Create a satellite 18

19 How to generate the Satellite manifest file (cont.) On the next screen, choose a name for Satellite server set Satellite Server version to 6.2 click Create button 19

20 How to generate the Satellite manifest file (cont.) On the next screen, click on Attach a subscriptions link 20

21 How to generate the Satellite manifest file (cont.) On the next screen, select entitlements. Use table below to set Quantity column Add the following subscriptions: Important: DO NOT add Red Hat Satellite (MCT0370) subscription itself here. Otherwise the pattern will not work. Product: Red Hat Enterprise Linux Server, Premium (8 sockets) (Unlimited guests) (RH ) Number required: The total number of compute nodes in the rack. For example if the rack has 6 compute nodes, meaning it has 6 hypervisors, then user needs to add 6 above subscriptions to the Satellite Organization Note: Mandatory to have. Product: Smart Management for Unlimited Guests (RH ) Number Required: Total number of compute nodes in the rack. Product: Extended Update Support for Red Hat Enterprise Linux Server (8 sockets) (RH ) Number Required: Total number of compute nodes in the rack. Note: Not mandatory to have. Only if customer needs extended support. Screenshot of this step at next page 21

22 How to generate the Satellite manifest file (cont.) Screenshot of adding subscriptions to the satellite organization. Again, do not add Red Hat Satellite product itself to the satellite organization. Otherwise the pattern will fail. (Note: Most Satellite PMRs were because of the failure to do this) 22

23 How to generate the Satellite manifest file (cont.) On the next screen, click Download manifest button and save it somewhere. 23

24 How to deploy the satellite server 6.2 pattern Patterns Virtual System Patterns Red Hat Satellite Server 6.2 Pattern Deploy 24

25 How to deploy the satellite server 6.2 pattern (cont.) Manifest use the one generated in step 4. Organization and Location arbitrary input but mandatory fields. Red Hat Customer Portal Username and Passwords the credentials used to log in your Red Hat Account. Click Quick Deploy and the pattern should complete deploying in 3-4 hours depending on network speed. 25

26 How to configure the Satellite Server after pattern deployment After you have confirmed that the deployment is complete, configure the Satellite Server. Note: All steps below are done on the Satellite Server. a. Click Content > Content Views to create a new content view. b. Click Yum Content > Repositories to add all required repositories to the content. And publish it. (screenshot of this step is shown in the next slide) c. Click Content > Activation Keys to create a new activation key and associate it with the newly created content view. (see screenshot) d. Click the Subscriptions tab and add sufficient subscriptions to the activation key entry. (see screenshot) e. Enable the repositories. Click Product Content and click Override to Yes for the Red Hat Satellite Tools 6.2 (for RHEL 7 Server) (RPMs) and Red Hat Satellite Tools 6.2 (for RHEL 6 Server) (RPMs) repositories. 26

27 How to configure the Satellite Server after pattern deployment (cont.) b. Click Yum Content > Repositories to add all required repositories to the content. And publish it. 27

28 How to configure the Satellite Server after pattern deployment (cont.) c. Click Content > Activation Keys to create a new activation key and associate it with the newly created content view. 28

29 How to configure the Satellite Server after pattern deployment (cont.) d. Click the Subscriptions tab and add sufficient subscriptions to the activation key entry 29

30 How to configure the Satellite Server after pattern deployment virt who configuration After Satellite Server 6.2 is installed using the PureApplication pattern, you must complete the following steps for it to be functional. This step is mandatory. A new subscription system that verifies the number of hypervisors has been introduced by Red Hat. The new system explicitly uses a tool to access VMware vcenter to verify the information. Due to this new subscription system, the Satellite virtual machine must have access to vcenter. PureApplication System version or higher enabled external VMware vcenter access from PureApplication. If your PureApplication System version is or higher, complete Enabling VMware vcenter external access for the Satellite Server virtual machine and Configuring virt-who and host-guests mappings. PureApplication System versions below do not provide VMware vcenter access from PureApplication System so you must open a PMR to request that IBM Support enable VMware vcenter access. 30

31 How to configure the Satellite Server after pattern deployment virt who configuration (cont.) Perform the following steps to complete virt-who configuration For step 2-4, follow the detailed steps in the below tech note link: Step 2: Enabling VMware vcenter external access for the Satellite Server virtual machine Step 3: Configuring virt-who and host-guests mappings Step 4: Attaching host-based subscriptions to the newly created hypervisors 31

32 How to configure Red Hat Satellite Shared Service in PureApp after pattern deployment After a satellite 6.2 server was successfully deployed, one must deploy a satellite 6.2 shared service to make the satellite server reach PureApp VMs. Go to Patterns -> Shared Service -> Deploy 32

33 How to configure Red Hat Satellite Shared Service in PureApp after pattern deployment (cont.) 1. URL to connect to Satellite Server use the IP or FQDN address of the satellite server just deployed 2. Satellite Server activation key use the one created in section How to configure the Satellite Server after pattern deployment (cont.) step d. 3. Organization name use the one whey deploying the satellite pattern. 33

34 End results after successful configuration Now all the PureApp RHEL VMs created in the same cloud group as where the Shared Service deployed in the previous step should be registered and connected to the newly deployed satellite server 6.2. Check to see if these VMs are shown on the satellite server UI console. Deployment and configuration complete. Client VMs can get updates/erratas and install packages from the satellite server now, as shown below: 34

35 Troubleshooting / deep dive Common issues among Red Hat Satellite 6.2 pattern users

36 Troubleshooting Case 1 Error message shows that the VM cannot find pool ID Example log: [Fri 27 Oct :47:18 PM IST] /utils/common_utils.py pid=15821 DEBUG Attaching subscription to the Satellite Server... [Fri 27 Oct :47:27 PM IST] /utils/common_utils.py pid=15821 DEBUG The Satellite Server Subscription ID is [Fri 27 Oct :47:45 PM IST] /utils/common_utils.py pid=15821 DEBUG Pool with id could not be found. Solution: Likely the Red Hat Satellite product has been wrongly attached to the satellite organization Go to the satellite organization and remove any subscriptions named Red Hat Satellite to free it to be used by the pattern. Verification: Log into a VM and log in using #subscription-manager register, with the Red Hat credentials Run #subscription-manager list available, and check if Red Hat Satellite is among the output. 36

37 Troubleshooting Case 2 Network issues. Solution: Check if proxy was set up right by looking at the RHSM config file Run #subscription-manager config Check if the proxy settings and satellite hostname are correct as shown in the screenshot. 37

38 References Red Hat Satellite RHN to RHSM migration guide and Red Hat Satellite Server 6.2 virtwho configuration System Architecture 38

39 Summary Overview What is a Satellite Server? Why did we need a new Satellite Server 6.2 pattern? Architecture High Level Red Hat Satellite 6 System Architecture Content Life Cycle in Red Hat Satellite 6 Usage scenarios How to configure and setup new Red Hat registration files with Satellite 6.2 How to generate the Satellite manifest file. How to deploy a Satellite Server 6.2 using the pattern How to configure the Satellite Server after pattern deployment Troubleshooting / Deep Dive

40 Closing remarks Thanks for listening! Any questions?