Manage Subscriptions and Content
Create a Subscription Manifest
Chapter 5. Managing Red Hat Subscriptions
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/managing_content/index#Managing_Red_Hat_Subscriptions_content-management
https://access.redhat.com/ -> Subscriptions -> Subscription Allocations -> Create New subscription allocation
Name: mkk-satellite
Type (select a type and version of the subscription management application that you are using): Satellite 6.11
Subscription Allocations -> mkk-satellite -> Subscriptions -> Add Subscriptions
You enable Simple Content Access (SCA) separately for each organization, allowing you to maintain some organizations with the SCA behavior and others without the behavior.
Export a Subscription Manifest from the Customer Portal
Subscription Allocations -> mkk-satellite -> Subscriptions -> Export Manifest
Import a Subscription Manifest to Satellite Server
3.9. Importing a Red Hat Subscription Manifest into Satellite Server
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/installing_satellite_server_in_a_connected_network_environment/index#Importing_a_Red_Hat_Subscription_Manifest_into_Server_satellite
Select Organization to associate the subscription manifest to
https://satellite.mkk.se/ -> <Select Organization> -> Content -> Subscriptions -> Manage Manifest
CDN Configuration
CDN Configuration for Red Hat Content
Red Hat CDN
URL: https://cdn.redhat.com
Manifest
Subscription Manifest
Import New Manifest
Verify Organization, Location and theirs Association
[root@satellite ~]# hammer organization list
---|-------|------|-------------|------
ID | TITLE | NAME | DESCRIPTION | LABEL
---|-------|------|-------------|------
1 | MKK | MKK | | MKK
---|-------|------|-------------|------
[root@satellite ~]# hammer location list
---|-----------|-----------|------------
ID | TITLE | NAME | DESCRIPTION
---|-----------|-----------|------------
2 | Stockholm | Stockholm |
---|-----------|-----------|------------
Verify that Location is associated with Organization
[root@satellite ~]# hammer location list --organization MKK
---|-----------|-----------|------------
ID | TITLE | NAME | DESCRIPTION
---|-----------|-----------|------------
2 | Stockholm | Stockholm |
---|-----------|-----------|------------
Synchronize Red Hat Content
To Enable a Repository in an Organization
6.5. Enabling Red Hat Repositories
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/managing_content/index#Enabling_Red_Hat_Repositories_content-management
https://satellite.mkk.se/ -> <Select Organization> -> Content -> Red Hat Repositories -> <Repository Name>
To Manually Synchronize Red Hat Product Repositories
6.6. Synchronizing Repositories
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/managing_content/index#Synchronizing_Repositories_content-management
https://satellite.mkk.se/ -> <Select Organization> -> Content -> Products -> <Product Name> -> <Repository Name> -> Sync Now
To Schedule Synchronization of Red Hat Product Repositories
Create Sync Plan
https://satellite.mkk.se/ -> <Select Organization> -> Content -> Sync Plans -> Create Sync Plan
Name: rhel8
Interval: hourly
Start Date: Today
Start Time: Now
Products -> Add -> <Select Product Name> -> Add Selected
Define Download Policies
6.7. Download Policies Overview
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/managing_content/index#Download_Policies_Overview_content-management
https://satellite.mkk.se/ -> <Select Organization> -> Administer -> Settings -> Content
Default Custom Repository download policy: immediate
Default Red Hat Repository download policy: on_demand
Verify Content from the CLI
[root@satellite ~]# hammer repository list
---|----------------------------------------------------------|-------------------------------------|--------------|----------------------------------------------------------------
ID | NAME | PRODUCT | CONTENT TYPE | URL
---|----------------------------------------------------------|-------------------------------------|--------------|----------------------------------------------------------------
3 | Red Hat Enterprise Linux 8 for x86_64 - AppStream RPMs 8 | Red Hat Enterprise Linux for x86_64 | yum | https://cdn.redhat.com/content/dist/rhel8/8/x86_64/appstream/os
1 | Red Hat Enterprise Linux 8 for x86_64 - BaseOS RPMs 8 | Red Hat Enterprise Linux for x86_64 | yum | https://cdn.redhat.com/content/dist/rhel8/8/x86_64/baseos/os
---|----------------------------------------------------------|-------------------------------------|--------------|----------------------------------------------------------------
[root@satellite ~]# hammer repository synchronize --id 1
Verify Content from the Web UI
https://satellite.mkk.se/ -> <Select Organization> -> Monitor -> Recurring Logics
https://satellite.mkk.se/ -> <Select Organization> -> -> Content -> Products -> <Product Name> -> <Repository Name>
Create Software Lifecycles
7.3. Creating a Life Cycle Environment Path
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/managing_content/index#Creating_a_Life_Cycle_Environment_Path_content-management
The first environment in every environment path is the Library environment that receives synced content from available sources. The Library environment is continuously syncing with source repositories, which are configured by the sync plans that you assigned to each repository.
Create a lifecycle environment path:
https://satellite.mkk.se/ -> <Select Organization> -> -> Content -> Lifecycle Environments -> Create Environment Path
Name: Development
Label: Development
Descriptiom: Development environment
Add New Environment
Name: Production
Label: Production
Descriptiom: Production environment
Prior Environment: Development
Verify Content from the CLI
[root@satellite ~]# hammer lifecycle-environment list --organization MKK
---|-------------|------------
ID | NAME | PRIOR
---|-------------|------------
2 | Development | Library
1 | Library |
3 | Production | Development
---|-------------|------------
[root@satellite ~]# hammer lifecycle-environment paths --organization MKK
------------------------------------
LIFECYCLE PATH
------------------------------------
Library >> Development >> Production
------------------------------------
Publish and Promote Content Views
Chapter 8. Managing Content Views
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/managing_content/index#Managing_Content_Views_content-management
Content Views
A content view is a customized content repository to define the software that a specific environment uses.
https://satellite.mkk.se/ -> <Select Organization> -> -> Content -> Content Views -> Create New View
Name: Base
Label: Base
Description: Base packages
Manage Repositories in Content Views
Add a repository to a content view:
https://satellite.mkk.se/ -> <Select Organization> -> -> Content -> Content Views -> <Content View Name> -> Repositories -> <Select Checkbox Repository> -> Add Repositories
Content View Filters
Publish a Content View
https://satellite.mkk.se/ -> <Select Organization> -> -> Content -> Content Views -> <Content View Name> -> Publish New Version
Description: Added RHEL 8 BaseOS and AppStream RPM repo
Promote a Content View
After publishing a content view version to the library, you can promote the content view to the first lifecycle environment in the environment path.
To promote a content view:
https://satellite.mkk.se/ -> <Select Organization> -> -> Content -> Content Views -> <Content View Name> -> Versions -> vertical ellipsis menu -> Promote
Description: RHEL 8 BaseOS and AppStream RPM repo
Content View Scenarios
In an all-in-one content view scenario, the content view contains all the needed content for all of your hosts.
In the host-specific content view scenario, dedicated content views exist for each host type.
No comments:
Post a Comment