This document will explain how to activate Satellite and then how to configure the first Channel.
How to Register Satellite & Download & Import Channel Content ISO’s.
Verify Activation in RHN (optional if using spacewalk)
Check for spacewalk-backend-tools package
# rpm –qa | grep backend
To see list of rhn commands run # rhn-
To view channels available run
tmp]# satellite-sync -l | tee channels
# satellite-sync --list-channels | more
Run the following to reregister system and entitle/activate Satellite
[root@satserv rhn]# rhn_register
[root@satserv rhn]# rhn-satellite-activate --rhn-cert=/root/myco.cert
Download Satellite Channel Content ISO’s for each channel you will need.
Red Hat recommends using Channel Content ISO’s locally versus importing directly from RHN website to save time.
Our example, we only user v6.3 RHEL
The process to copy Channel Content ISOs is to mount each one, copy its contents to the temporary repository, and then unmount the ISO.
Mount from your laptop to vmware to satellite server
[root@satserv mnt]# mkdir /var/satellite/sat-import
Mount the iso to local in vCenter and then copy from mount point to sat-import
[root@satserv media]# mount /dev/cdrom /media
[root@satserv media]# cp -ruv * /mnt /var/satellite/sat-import/
Repeat these steps for each Channel Content ISO of every channel to be imported.
The
first step in importing channels into the database is listing the
channels available for import. This is accomplished with the command:
satellite-sync --list-channels --mount-point /var/satellite/sat-import
notes –
run ‘satellite-sync --list-channels’ option to obtain a list of all channels by label.
View local channels available
[root@satserv sat-import]# satellite-sync --list-channels --mount-point /var/satellite/sat-import/
Start the import of a channel
[root@satserv sat-import]# satellite-sync -c rhel-x86_64-server-6 --mount-point /var/satellite/sat-import/
..output.. 13:20:07 Red Hat Network Satellite - file-system synchronization
13:20:07 mp: /var/satellite/sat-import
13:20:07 db: rhnsat/<password>@rhnsat
13:20:08 Retrieving / parsing additional arches data
13:20:08 additional arches data complete
13:20:08 Retrieving / parsing channel data
13:20:09 p = previously imported/synced channel
13:20:09 . = channel not yet imported/synced
13:20:09 . rhel-x86_64-server-6 8203 full import from Mon Jun 25 12:52:55 2012
13:20:10 Channel data complete
13:20:10 Retrieving / parsing blacklists data
13:20:10 blacklists data complete
13:20:10 Retrieving / parsing product names data
13:20:10 Retrieving short package metadata (used for indexing)
13:20:10 Retrieving / parsing short package metadata: rhel-x86_64-server-6 (8203)
13:20:43 Diffing package metadata (what's missing locally?): rhel-x86_64-server-6
________________________________________
Diffing: ######################################## - complete
13:20:57 Downloading package metadata
13:20:57 Retrieving / parsing *relevant* package metadata: rhel-x86_64-server-6 (8203)
13:20:57 * WARNING: this may be a slow process.
________________________________________
Downloading:################################ ---output truncated--- 8203/8203 Fetch successful: freeradius-2.1.12-3.el6.x86_64.rpm (1458248 bytes)
13:38:36 Processing rpm packages complete
13:38:36 Importing package metadata
13:38:36 Importing *relevant* package metadata: rhel-x86_64-server-6 (8203)
13:38:36 * WARNING: this may be a slow process.
________________________________________
Importing: # ---output truncated---
This conducts the following tasks in this order:
Populating the tables describing common features for channels ( channel families). This can also be accomplished individually by passing the --step=channel-families option to satellite-sync.
Creating a particular channel in the database and importing the metadata describing the channel. Individually, use the --step=channels option.
Moving the RPM packages from the temporary repository into their final location. Individually, use the --step=rpms option.
Parsing
the header metadata for each package in the channel, uploading the
package data, and associating it with the channel. Individually, use the
--step=packages option.
Identifying Errata associated with the packages and including them in the repository. Individually, use the --step=errata option.
-
this process worked and resolved my kickstart profile issue
Set up a cron job in /etc/cron.daily to sync from Red Hat Network
Define your Organization
Go to Admin > Organization ( or create new organization)
Fill out appropriate information
Once created, you need to assign system entitlements
for:
- Management (Needed to register with Satellite file management, etc.)
- Monitoring (Needed for Monitoring)
- Provisioning (Needed for bare metal installation, config
- Virtualization (Needed for any machine doing virtualization which is not unlimited)
- Virtualization Platform (Needed for any machine with unlimited virtualization)
Configuration File Management
Go to Configuration > Create New Config Channel
Fill in Name, Label, & Description, then click create
Click Add Files
Click Create File
Create the file
Create ‘Company default’ Config Channel #This is the Myco Config File # It uses variables and will be customized on # per host basis.
MY_SYSTEMID={|rhn.system.sid|} MY_PROFILE_NAME={|rhn.system.profile_name|} MY_SYSTEM_DESCRIPTION={|rhn.system.description|} MY_HOSTNAME={|rhn.system.hostname|} MY_SYSTEM_IP={|rhn.system.ip_address|} MY_ETH0_IP={|rhn.system.net_interface.ip_address(eth0)|} MY_ETH0_NETMASK={|rhn.system.net_interface.netmask(eth0)|} MY_ETH0_BCAST={|rhn.system.net_interface.broadcast(eth0)|} MY_ETH0_MAC={|rhn.system.net_interface.hardware_address(eth0)|} MY_ETH0_DRIVER={| rhn.system.net_interface.driver_module(eth0)|}
Create System Groups
We’ll create 3 System Groups based on Environment (Dev, Stg, Prod)
Create 3 system groups on role (app, db, web)
Go to Systems > System groups > Create New Group
Enter group name and description
Clone a Channel
This is good idea for creating dev, stg, prod channels and keeping track of software at each channel.
Currently only cloned RHEL Server 6 Channel and to Dev-Rhel Server 6
Clone all Child Channels as well
Repeat for other channels as needed.
Create a Custom Channel (for PostgreSQL )
Go to Channels > Manage Software Channels > Create New Channel
Enter the following information
Basic Channel Details
Channel Name
Channel Label
Select Parent Channel
Select Parent Channel Arch [x86_64]
Channel Summary
Channel Maintainer / Contact
Maintainer Name
Maintainer Contact info
Support Policy (if any)
Channel Access Control
Per-User Subs
Organization Sharing
Security GPG Key
If you have GPG enter it here
Then click Create Channel
Create Custom Repository (if available, otherwise push packages in via rhnpush)
Locate the YUM Repo URL
Click on Manage Repositories > Create New Repository
Enter the Repo – label and URL and then click Create Repository
Go to Software Channels > Select your Channel > Repositories
Select the new Repo then click on Update List > Update Repositories
There are 3 methods to Sync
Method 1: Go to Repos > Sync and verify the Repo is there, then click Sync Now
Method 2 = command line, skip to next step 8
Method 3 – To only sync select packages to Repo, Skip to Step 10.
Use spacewalk-repo-sync to sync packages from thirdparty (postgresql ) Repo
]# spacewalk-repo-sync --channel postgresql-9.1
To push single packages Use rhnpush to move to satellite all PostgreSQL server packages.
tmtw1]# rhnpush
postgresql91-9.1.4-3PGDG.rhel6.x86_64.rpm
postgresql91-contrib-9.1.4-3PGDG.rhel6.x86_64.rpm
postgresql91-libs-9.1.4-3PGDG.rhel6.x86_64.rpm
--server=https://satserv.mycoinc.com/APP -u satadm -p satellite -c postgresql-9.1 note: install GPG key [root@satserv /]# rpm -ivh pgdg-redhat91-9.1-5.noarch.rpm Preparing... ########################################### [100%] 1:pgdg-redhat91 ########################################### [100%] [root@satserv /]# cd /etc/pki/rpm-gpg/ [root@satserv rpm-gpg]# ls RPM-GPG-KEY-PGDG-91 RPM-GPG-KEY-redhat-legacy-former RPM-GPG-KEY-redhat-legacy-rhx RPM-GPG-KEY-redhat-beta RPM-GPG-KEY-redhat-legacy-release RPM-GPG-KEY-redhat-release [root@satserv rpm-gpg]# rpm --import RPM-GPG-KEY-PGDG-91 Copy the GPG key into /var/www/html/pub on theSatellite Server so that existing servers can access it using:
How to Create Activation Keys
Go to Systems > Activation Keys > Create New Key
Type a description and Key name
Desc = Master Key
Key = master-key
Select Provisioning
Click ‘Create Activation Key’
Click on Packages and add these packages to all systems
Create MYCO Configuration Channel
Add NTP to Script 2 (standard Script # Configure NTP echo "server ntp.mycoinc.com >> /etc/ntp.conf ntpdate -u ntp.mycoinc.com chkconfig --levels 2345 ntpd on
