Red Hat Satellite - Revision history

Leo: /* Glossary */

2020-06-14T23:22:36Z

Glossary

← Older revision		Revision as of 23:22, 14 June 2020
Line 330:		Line 330:

	{{Navbox Linux}}[[Category:Linux]]		{{Navbox Linux}}[[Category:Linux]]
			[[Category:LinuxUtilities]]

Leo: /* Bootstrap.py */

2019-10-21T21:41:07Z

Bootstrap.py

← Older revision		Revision as of 21:41, 21 October 2019
Line 292:		Line 292:
	You can use the katello client bootstrap project's {{code\|bootstrap.py}} to manually register and place a host to a particular host group in Satellite. This is typically desired if you are deploying a machine not from kickstart but from something like a virtual machine clone and the host isn't added to Satellite as part of the post-installation process.		You can use the katello client bootstrap project's {{code\|bootstrap.py}} to manually register and place a host to a particular host group in Satellite. This is typically desired if you are deploying a machine not from kickstart but from something like a virtual machine clone and the host isn't added to Satellite as part of the post-installation process.

	Get the {{code\|bootstrap.py}} script from https://github.com/Katello/katello-client-bootstrap. On a host that is to be ~~provisioned~~, ~~copy the script and then~~ run:		Get the {{code\|bootstrap.py}} script from the project at https://github.com/Katello/katello-client-bootstrap. On a host that is to be added to a particular host group in Satellite, run:
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
			# wget https://raw.githubusercontent.com/Katello/katello-client-bootstrap/master/bootstrap.py
			# chmod 755 bootstrap.py
	# ./bootstrap.py -l admin \		# ./bootstrap.py -l admin \
	-s itsosatwebp01.ucalgary.ca \		-s itsosatwebp01.ucalgary.ca \

Leo: /* Bootstrap.py */

2019-10-21T21:38:57Z

Bootstrap.py

← Older revision		Revision as of 21:38, 21 October 2019
Line 295:		Line 295:
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
	# ./bootstrap.py -l admin \		# ./bootstrap.py -l admin \
	-s ~~satellite~~.~~example~~.~~com~~ \		-s itsosatwebp01.ucalgary.ca \
	-o ~~"Red Hat"~~ \		-o UofcServers \
	-L ~~RDU~~ \		-L Calgary \
	-g ~~"RHEL7/Crash"~~ \		-g vRA \
	-a ak-~~Reg_To_Crash~~ \		-a vRA-EL7-Activation \
			--force
	}}		}}

	Where:		Where:
			* {{code\|-l}} - username
	* {{code\|-s}} - satellite server		* {{code\|-s}} - satellite server
	* {{code\|-o}} - Organization		* {{code\|-o}} - Organization
Line 308:		Line 310:
	* {{code\|-g}} - Host group		* {{code\|-g}} - Host group
	* {{code\|-a}} - activation key		* {{code\|-a}} - activation key
			* {{code\|--force}} - removes old host if it exists

	See Also:		See Also:

Leo: /* Terminology */

2019-10-21T21:03:52Z

Terminology

@@ Line 289: / Line 289: @@
-== Terminology ==
+== Bootstrap.py ==
 {| class="wikitable"
 ! Terminology
@@ Line 299: / Line 323: @@
 | Organization
 | Satellite lets the administrator restrict policies/packages based on a machine's group. (Similar to what I already do with labs in CPSC).
-}}
+|}
 {{Navbox Linux}}[[Category:Linux]]

Leo: Text replacement - "Category:Linux{{Navbox Linux}}" to "{{Navbox Linux}}Category:Linux"

2019-09-01T06:22:22Z

Text replacement - "Category:Linux{{Navbox Linux}}" to "{{Navbox Linux}}Category:Linux"

← Older revision		Revision as of 06:22, 1 September 2019
Line 301:		Line 301:
	}}		}}

	[[Category:Linux]]~~{{Navbox Linux}}~~		{{Navbox Linux}}[[Category:Linux]]

Leo: Text replacement - "Category:Linux" to "Category:Linux{{Navbox Linux}}"

2019-09-01T05:09:08Z

Text replacement - "Category:Linux" to "Category:Linux{{Navbox Linux}}"

← Older revision		Revision as of 05:09, 1 September 2019
Line 301:		Line 301:
	}}		}}

	[[Category:Linux]]		[[Category:Linux]]{{Navbox Linux}}

Leo: Text replacement - "{\| " to "{| class="wikitable" "

2019-09-01T01:36:48Z

Text replacement - "{\| " to "{| class="wikitable" "

← Older revision		Revision as of 01:36, 1 September 2019
Line 290:		Line 290:

	== Terminology ==		== Terminology ==
	{\|		{\| class="wikitable"
	! Terminology		! Terminology
	! Definition		! Definition

Leo: /* Installing from ISO */

2018-08-07T19:20:04Z

Installing from ISO

← Older revision		Revision as of 19:20, 7 August 2018
Line 69:		Line 69:
	=== Installing from ISO ===		=== Installing from ISO ===
	You can also install Satellite using the ISO image from the Red Hat Customer Portal.		You can also install Satellite using the ISO image from the Red Hat Customer Portal.

			In the RedHat Satellite training, the ISO can be obtained by running:
			{{highlight\|lang=terminal\|code=
			# cd /tmp
			# wget http://content.example.com/rhsat6.2.1/x86_64/isos/satellite-6.2.1-rhel-7-x86_64-dvd.iso
			}}

	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=

Leo at 17:36, 25 May 2018

2018-05-25T17:36:33Z

← Older revision		Revision as of 17:36, 25 May 2018
Line 1:		Line 1:
	This article will go over content for ~~RedHat~~ Satellite 6.		This article will go over content for Red Hat Satellite 6.

	== Overview ==		== Overview ==
	~~RedHat~~ Satellite is a management tool that helps system administrators to build and maintain Linux (~~RedHat~~ only?) systems.		Red Hat Satellite is a management tool that helps system administrators to build and maintain Linux (Red Hat only?) systems.

	Satellite has the following components:		Satellite has the following components:
	# Foreman - Open Source application used to provision and life cycle manage hosts using kickstart and puppet modules. It also provides historical data on hosts		# Foreman - Open Source application used to provision and life cycle manage hosts using kickstart and puppet modules. It also provides historical data on hosts
	# Katello - Subscription and repository management. It pulls upstream packages from ~~RedHat~~'s CDN		# Katello - Subscription and repository management. It pulls upstream packages from Red Hat's CDN
	# Katello/Pulp - Repository / content management as part of katello		# Katello/Pulp - Repository / content management as part of katello
	# Katello/Candlepin - handles subscription management (to ~~RedHat~~'s CDN)		# Katello/Candlepin - handles subscription management (to Red Hat's CDN)
	# Capsule Server - A capsule module is a proxy for some of Satellite's services (repository, dns, dhcp, puppet master). An integrated capsule server is bundled with a Satellite install, but additional capsule servers can be created to offer HA/Redundancy.		# Capsule Server - A capsule module is a proxy for some of Satellite's services (repository, dns, dhcp, puppet master). An integrated capsule server is bundled with a Satellite install, but additional capsule servers can be created to offer HA/Redundancy.


	== Satellite Installation ==		== Satellite Installation ==
	Satellite should be installed on a clean install of ~~RedHat~~ Enterprise 6 or 7 on a minimum of:		Satellite should be installed on a clean install of Red Hat Enterprise 6 or 7 on a minimum of:
	* x86_64		* x86_64
	* 2 CPU		* 2 CPU
Line 68:		Line 68:

	=== Installing from ISO ===		=== Installing from ISO ===
	You can also install Satellite using the ISO image from the ~~RedHat~~ Customer Portal.		You can also install Satellite using the ISO image from the Red Hat Customer Portal.

	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
Line 90:		Line 90:

	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
	satellite-installer --scenario satellite --foreman-admin-username admin --foreman-admin-password ~~redhat~~		satellite-installer --scenario satellite --foreman-admin-username admin --foreman-admin-password Red Hat
	Installing Done [100%] [...................................]		Installing Done [100%] [...................................]
	Success!		Success!
	* Satellite is running at https://satellite.lab.example.com		* Satellite is running at https://satellite.lab.example.com
	Initial credentials are admin / ~~redhat~~		Initial credentials are admin / Red Hat
	* To install additional capsule on separate machine continue by running:		* To install additional capsule on separate machine continue by running:

Line 194:		Line 194:
	Registering to: satellite.lab.example.com:443/rhsm		Registering to: satellite.lab.example.com:443/rhsm
	Username: admin		Username: admin
	Password: ~~redhat~~		Password: Red Hat
	The system has been registered with ID: f7855ac5-531a-4b09-bc78-13a11e500e5f		The system has been registered with ID: f7855ac5-531a-4b09-bc78-13a11e500e5f

Line 219:		Line 219:

	== Registering Satellite Clients ==		== Registering Satellite Clients ==
	Clients use the {{code\|subscription-manager}} to register with the ~~RedHat~~ Network or to a Satellite server.		Clients use the {{code\|subscription-manager}} to register with the Red Hat Network or to a Satellite server.

	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
Line 225:		Line 225:
	# yum update subscription-manager yum		# yum update subscription-manager yum

	## Install CA Certificate ~~for~~ the Satellite server:		## Install CA Certificate from the Satellite server:
	# yum -y localinstall http://satellite.lab.example.com/pub/katello-ca-consumer-latest.noarch.rpm		# yum -y localinstall http://satellite.lab.example.com/pub/katello-ca-consumer-latest.noarch.rpm

Line 259:		Line 259:


			== Products / Repositories ==
			A repository contains software packages. Multiple repositories can be grouped together to form a 'product'. Products created under an organization context will only be visible in that organization.

			Satellite can:
			* Create custom repositories/products through manual package upload via the web interface
			* Find existing products/packages through the discovery feature
			* Manage GPG keys and host subscriptions automatically.

			3rd party repositories can either have their packages copied to an existing product or cloned as a new product using the Repository Discovery feature.

			Repositories with no GPG public key associated will have the {{code\|gpgcheck}} option set to disabled.

			== Lifecycle Environment ==
			Lifecycle Environment Paths is a feature in Satellite that provides a way for administrators to staging software package/errata releases through clearly defined phases.

			A lifecycle environment is a stage in a lifecycle path. For example, any one of 'Dev', 'QA', 'Production' would be a lifecycle environment.

			An environment path is a sequence of lifecycle environments. All environment paths begin with the 'Library' environment. For example, a path could be: 'Library -> Dev -> QA -> production'.

			You may only delete the last lifecycle environment in an environment path.

			After creating a lifecyce environment, adding additional hosts using {{code\|subscription-manager register}} will require you to provide an environment. Environment names must be given in full


			== Terminology ==
			{\|
			! Terminology
			! Definition
			\|-
			\| Product
			\| A set of repositories makes up a product
			\|-
			\| Organization
			\| Satellite lets the administrator restrict policies/packages based on a machine's group. (Similar to what I already do with labs in CPSC).
			}}

	[[Category:Linux]]		[[Category:Linux]]

Leo: Leo moved page RedHat Satellite to Red Hat Satellite

2018-05-25T16:25:51Z

Leo moved page RedHat Satellite to Red Hat Satellite

← Older revision		Revision as of 16:25, 25 May 2018
(No difference)