Introduction of Satellite Server
Red Hat Satellite is a system management solution that enables you to deploy, configure, and maintain your systems across physical, virtual, and cloud environments. Satellite provides provisioning, remote management and monitoring of multiple Red Hat Enterprise Linux deployments with a single, centralized tool. Red Hat Satellite Server synchronizes the content from Red Hat Customer Portal, and provides functionality including fine-grained lifecycle management, user and group role-based access control, integrated subscription management, as well as advanced GUI, CLI, and API access.
Satellite Server 6.2 installation
--enable=rhel-server-rhscl-7-rpms \
--enable=rhel-7-server-satellite-6.2-rpms
6) Verify your repository & update your system
( if you are using proxy environment )
Download & upload manifest in Satellite Server
Red Hat Satellite 6 imports content from Red Hat’s Content Delivery Network (CDN). To do this, the Satellite Server needs to know what product subscriptions are available so that it can find, access, and download from corresponding repositories. All subscription information is available in your Red Hat Customer Portal account. To import this information into Satellite, you create a subscription manifest.
A subscription manifest is a set of encrypted files that contains your subscription information. You import this manifest into your Satellite Server. The Satellite Server then uses this information to access the CDN and find what repositories are available.
1. Go to the Red Hat Customer Portal and log in.
2. Click SUBSCRIPTIONS.
3. In the Red Hat Subscription Management section, click Satellite.
4. Click Register a Satellite.
5. In the Name field, type Satellite_Server_example.
6. Select Satellite 6.2 as the version and click Register.
7. Click Attach a subscription.
8. Select the check box for each subscription that you want to attach and specify the number
of subscriptions.
9. Click Attach Selected.
It can take several minutes for all the subscriptions to attach.
10. Click Download Manifest and save the manifest file to a known location
11. Import manifest in satellite server
# hammer subscription upload --organization-label Default_Organization --file path_to_manifest
Add repositories
In Satellite, we use the concept of a Product as an organizational unit to group multiple repositories together. Such repository collections are analogous to the concept of real life products. For example, if we view Red Hat Enterprise Linux Server as a Product in Satellite, the repositories for that product might consist of different versions (6.0, 6.1, 7.0), different architectures (i386, x86_64, s390x, arm), and different add-ons (Optional repositories, Supplementary repositories, Virt V2V tools). This unifies all related repositories within the DML. Using Products ensures repositories that depend on each other are synchronized together. For Red Hat repositories, products are created automatically after enabling the repository.
Click on content tab and select Red Hat repositories then select your product and check mark on required repositories.
Sync repositories
Click on content tab and select sync status then check mark on repositories that you want to sync and click on sync now
Creating Life Cycle environment
The application life cycle defines how systems appear at a certain stage. However, the actual application life cycle depends on your organization and how it structures a particular production chain.
For example, an email server might only require a simple application life cycle where you have a production-level server for real world use and a test server for trying out the latest mail server packages. Once the test server passes the initial phase, we can set the production-level server to use the new packages.
Another example might be an development life cycle for a software product. You might aim to develop a new piece of software in a development environment, have it tested in a quality assurance environment, pre-release it as a beta, then release it as a production-level application.
Each application life cycle uses a set of stages called environments. Each environment act as a particular state for our systems. Each environment also follows on from a previous environment, creating a chain of environments that becomes our application life cycle. Each application life cycle starts with an initial Library, which acts as a central source in our Definitive Media Library (DML). The Library environment contains all of the content we previously synchronized in our previous chapters. From this point, we create additional environments that link starting from the Library environment.
1) Click Content tab and select Life Cycle management
2) Click on +Add New Environment.
3) Define your environment Name & Description (Create three Environment stages)
4) Select Content view option from content tab for Environment
Red Hat Satellite 6 uses content views to create customized repositories from the core repositories in your Definitive Media Library (DML). It achieves this through defining which repositories to use and then applying certain filters to the content. These filters include both package filters, package group filters, and errata filters. We use content views as a method to define which software versions a particular environment uses. As mentioned in the previous chapter, a Production environment might use a content view containing older package versions, while a Development environment might use a content view containing newer package versions.
5) Click +Create new view.
6) Define your content ( Name= OS or RHEL-6.6, Left blank composite view ).
7) Add repositories.
8) Publish your new version.
9)Add version Description
10) Content view detail.
11) You need to select where you want to promote this content view
Content moves from one environment to the next in an application life cycle chain. This is a process called promotion. Promotion is an important concept to understand because it is the basis for managing content across an application life cycle.
12) Select Development.
13) Click promote option
14) Confirm your action.
15) Create Activation Key So need to click on content tab and select Activation Key
At this point, we have published some content views, which resulted in the Satellite Server publishing repositories. Systems now can register to the Satellite Server and consume content from these repositories. Systems register in a similar way to how they register to the Red Hat Customer Portal. For example, users can use Red Hat Subscription Manager (subscription-manager) with the --baseurl pointing to the Satellite Server instead of the Red Hat Content Delivery Network.
There are two methods to register a system. The first is to authenticate with a Satellite Server user name and password, which we explored in the previous chapter. An alternative and preferred method is to use an activation key, which acts as an authentication token. Activation keys provide a method for easy system registration and subscription attachment. Users can create multiple keys and associate them with different environments and content views. For example, you might create a basic activation key with a subscription for Red Hat Enterprise Linux workstations and associate it with content views from a particular environment.
16) Click on +New Activation Key
17) Define Activation key with environment and content view.
18) Create Sync plan
Once we choose which repositories form our DML, the Satellite Server synchronizes its own repositories with the repositories on the Red Hat CDN. This ensures that the Satellite Server retains an exact copy of Red Hat’s repositories as a part of its DML. The Satellite Server fetches this repository information and stores it on the Satellite Server’s file system. After an initial synchronization, you can create a synchronization plan that checks to make sure the repositories in the DML is up to date with the CDN’s repositories.
19) Click for new sync plan.
20) Define your sync plan
22) Click + New Product
23) Define the product ( Define Name, Left GPG Key and select created sync plan )
Note:- If already created than don't required to create product again.
24) Verify that all points created for One life cycle with content view, Add repositories, published, promote & used by content host
Registration of Clients
1) Prerequisites for registering client with satellite server
Time match with Satellite Server
Networking and Host-name will set properly
SElinux should be in permissive mode
You are able to reach on following ports with satellite server
port 80/tcp for http protocol (for obtaining Katello information )
port 443/tcp for https protocol ( for subscription management services )
port 5647/tcp for amqp ( for katello agent to communicate with Satellite )
port 8140/tcp for https
port 9090/tcp for https
2) Registering content host along with their activation key
# yum -y --nogpgcheck install http://moonlight.casram.com/pub/katello-ca-consumer-satellite6.example.com-1.0-1.noarch.rpm
# subscription-manager register --activationkey="redhat" –org="Default_Organization"
3) You can also list about your subscriptions
# subscription-manager list
4) Providing subscription to content host
# subscription-manager attach –auto ( if required other wise you can select manually )
5) Set particular release version for content host So that it will get proper errata updates
# subscription-manager release –set '6.7' ( According to your client version release )
6) It will list my repositories
# subscription-manager repos list
7) We need to Enable required repositories
# subscription-manager repos –enable=rhel-server-6-rpms (enable repositories according to your need)
# subscription-manager repos –enable=satellite-6.2-tools-rhel-6-rpms
8) Install Agent in machine
# yum install katello-egent
Backup & Restore of Satellite Configuration and Data
1) You need to ensure that you have valid storage for keeping your satellite backup
# katello-backup backup_directory
Note:- It will stop all service of satellite server to ensure all data and configuration will be backup
So during data backup no process will be running
2) You can restore backup
# katello-restore backup_directory
Managing Errata
As a part of Red Hat’s quality control and release process, we provide customers with updates for each release of official Red Hat RPMs. Red Hat compiles groups of related package into an erratum along with an advisory that provides a description of the update. There are three types of advisories (in order of importance):
Red Hat Satellite 6 imports this errata information when synchronizing repositories with Red Hat’s Content Delivery Network (CDN). Red Hat Satellite 6 also provides tools to inspect and filter errata, allowing for precise update management. This way, you can select relevant updates and propagate them through content views to selected content hosts.
Applicable
Erratum applies to one or more content hosts, which means it updates packages present on the content host. Applicable errata are not yet accessible by the content host.
Installable
Erratum applies to one or more content hosts and it has been made available to the content host. Installable errata are present in the content host’s life cycle environment and content view, but are not yet installed. This way, errata can be installed by users who have permissions to manage content hosts, but are not entitled for errata management at higher levels.
No comments:
Post a Comment