COOKBOOK - How to add VMWare machines to Satellite 6 - Work in progress
This document will list the method used to add VMWare virtual machine to the Satellite 6 system so that they can be patched/controlled.
First thing is to get Satellite 6 working on your environment. This is documented in "Cookbook - a basic install for patch control - WORK IN PROCESS"
After finishing that then you need the following items to complete this task.
- Running Satellite 6 system (check)
- A virtual machine on the virtual environment you are going to control. (ie. one machine to control all others)
- A login to the virtual machine environment ( ie user id for Satellite 6 to use for data collection).
This login only needs Read-Only access to the VMWare servers that contain the virtual machines to be monitored/controlled.
Ok to start you need to yum install the virt-who package on the machine. The configuration file is located in:
/etc/sysconfig/virt-who
Edit this file and change the following items ( this is for VMWare virtuals otherwise you mileage may vary )
VIRTWHO_BACKGROUND=1
VIRTWHO_DEBUG=1
VIRTWHO_ESX=1
VIRTWHO_ESX_OWNER="ORG NAME" - org name from Satellite 6
VIRTWHO_ESX_ENV=Library - the base patching level
VIRTWHO_ESX_SERVER=255.255.255.255 - the IP address of the VSphere server
VIRTWHO_ESX_USERNAME="username" - this is the login id of the user that can see the ESX servers that your virtual run on
Remember on windows you must supply the windows domain as part of the username "domain\\username"
You have to use a double backslash as the first one excapes the second so that it can actually be used as a backslash
VIRTWHO_ESX_PASSWORD="password" - this is the password for the above user.
You can test the user id and password using the VMWare client to display the systems it can see.
After editing the virt-who file then you need to start the service.
service virt-who start
When you go back to Satellite 6 you need to refresh the "content hosts" screen and you should see systems with long number sequences. These should be the VMWare servers that the system finds.
To put system names on these systems you will need to look at the VMWare environment and record what virtuals are on what real servers.
Then pick one virtual to connect to Satellite 6 the command sequence to be used is:
virtual command line: use the first line supplied from the Satellite 6 "Register Content Host" screen. It looks something like this.
rpm -Uvh http://satellite.example.com/pub/katello-ca-consumer-latest.noarch.rpm
Notice that I replaced the domain name with "example". The screen is not a generic entry but an entry for your specific environment.
The second command line items is:
subscription-manager register --org="Organization" --environment="Library"
I replaced my org with "Organization" on you system it will have the organization you specified on your Satellite 6 system.
This will register your system with the Satellite system. You will have to refresh your screen to see it. Also the screen only displays 20 systems at first. If you want to see more then you need to pull down the screen and it will collect an additional 20 systems to display. If you have several hundred systems this can get to be a real pain point.
When you see your system you need to double click on the system name and it will display system info on the right side of the screen. The "Datails" tab will be displayed. On that screen should be an entry for "Virtual Host" which is the real machine that is hosting this virtual machine. If you double click on the machine name listed it will take you to the screen for that machine. In that screen you can edit the machine name to a "User usable" name.
Then select the virtual machine that you were working on and it will display the info with the "User usable" name for "Virtual Host".
There will be a tab for "Subscriptions" select the tab and the Subscriptions screen will display. The list/remove tab will be active and there should not be any subscriptions listed. Select the "Add" tab and there will be a list of the available subscriptions to be applied to the machines.
Reselect the list/remove tab and the subscription will be displayed for this machine. Also the indicator towards the top of the screen should be "GREEN" and listed as valid. So now you have a system subscribed to get patches.
Back on the command line you now need to issue this command:
subscription-manager repos
This will get the available repos list from the Satellite system. You will not need to figure out what poolid's are need for the subscriptions because the Satellite system knows what they are. You now need to edit the redhat.repo file in /etc/yum.repos.d. You need to enable the common repo as this is where the katello-agent rpm is.
After the subscription-manager command completes the issue this command:
yum repolist
I know that this can be done with any other yum command but by doing it by itself you can isolate/identify any problems at this time.
After yum has gotten the new repos then you can issue this command:
yum install katello-agent
This will install the katello-agent so that the Satellite system can display the "errata" need for this machines repo updates.
At this point you can use the yum update command and patch your machine.
Bob
