No description, website, or topics provided.
Switch branches/tags
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
group_vars
heat
images
roles
LICENSE
README.md
bootstrap-clients.yml
deboostrap-clients.yml
delete-stack.yml
deploy-satellite.yml
deprovision-client.yml
provision-client.yml
sample.inventory
sample_vars.yml
setup-openstack-client.yml
update-packages.yml

README.md

General

The purpose of this project is to properly setup Satellite on OpenStack. It focuses on three areas: Satellite installation and configuration, bootstrapping existing instances and deploying new instances via Heat with automatic bootstrapping. The aim is to use Heat to do provisioning and then all the systems management: patching, configuration management, insights, etc using Satellite. This allows us to bring traditional workloads that are built and then updated through their lifecycle on a cloud platform like OpenStack. Of course for cloud-native workloads that are always rebuilt from scratch with every change you would take a different approach. Point is both approaches are important and getting the traditional one into OpenStack is something a lot of people struggle with greatly. Satellite is only able to manage Red Hat Enterprise Linux (RHEL) workloads in this way. For other OS's this would not apply.

Contribution

If you want to provide additional features, please feel free to contribute via pull requests or any other means. We are happy to track and discuss ideas, topics and requests via 'Issues'.

Pre-requisites

  • Working OpenStack deployment. Tested is OpenStack Pike (12) using RDO.
  • RHEL 7 image. Tested is RHEL 7.5.
  • An openstack ssh key for accessing instances.
  • A pre-configured provider (public) network with at least three available floating ips.
  • Additional Flavors configured
    • sat6.master (2 vCPU, 12GB RAM, 110GB Disk)
    • m2.tiny (1 vCPU, 1GB RAM, 30 GB Root Disk)
  • A router that has the provider network configured as a gateway (floating ip network).
  • A internal non-routable network and subnet for instances.
  • Properly configured cinder and nova storage.
    • Make sure you aren't using default loop back and have disabled disk zeroing in cinder/nova for LVM.

More information on setting up proper OpenStack environment can be found here.

Blog

I have also created a blog that goes into a bit more detail for those interested here

Install Satellite

Clone github repo

# git clone https://github.com/ktenzer/satellite-on-openstack-123.git

Change directory to repo

# cd satellite-on-openstack-123

Checkout a release branch

[root@localhost]# git checkout release-6.3

Configure OpenStack Client

As mentioned in order to communicate with OpenStack we need a client. The playbook is setup-openstack-client.yml. In order to run it no inventory is needed since it will just configure the client on the localhost or host running playbook.

[root@localhost]# ansible-playbook setup-openstack-client.yml --private-key=/root/admin.pem -e @../vars.yml

PLAY RECAP *****************************************************************************************
localhost : ok=4 changed=1 unreachable=0 failed=0

Configure vars

[root@localhost]# cp sample_vars.yml vars.yml
[root@localhost]# vi vars.yml
---
### General Settings ###
ssh_user: cloud-user
ssh_key_path: /root/admin.pem
admin_user: <Satellite admin user>
admin_passwd: <Satellite admin password>
yum_update: True
yum_update_security_only: False
debug: True

### OpenStack Settings ###
stack_name: myinstance
heat_template_path: /root/satellite-on-openstack-123/heat/satellite_integrated_capsule_only.yaml
openstack_version: 12
openstack_user: admin
openstack_passwd: <passwd>
openstack_ip: <ip>
openstack_project: admin
external_network: public
service_network: internal
service_subnet: internal-subnet

### OpenStack Satellite Settings ###
### Capsule settings only important with satellite.yaml ###
master_hostname: sat6-master
capsule_hostname_prefix: sat6-capsule
satellite_domain_name: novalocal
capsule_count: 1
master_volume_size: 100
capsule_volume_size: 50
satellite_ssh_key_name: admin

### OpenStack Managed Instance Settings (Optional) ###
### This is used for playbooks that deploy managed RHEL instance ###
instance_hostname: rhel123
instance_security_group: base
instance_flavor: m2.tiny
instance_image: rhel75
instance_volume_size: 30
instance_ssh_key_name: admin
instance_domain_name: novalocal

### Satellite Install Settings ###
satellite_server: sat6.novalocal
satellite_version: 6.3
hostgroup: RHEL7_Base
activation_key: rhel7-base
software_collections_enabled: False
puppet_forge_enabled = False
puppet_version: puppet4
puppet_environment: KT_RedHat_unstaged_rhel7_base_5
install_puppet: True
puppet_logdir: /var/log/puppet
puppet_ssldir: /var/lib/puppet/ssl
org: <organization>
location: <location>
manifest_file:

### Red Hat Subscription ###
rhn_username: <user>
rhn_password: <password>
rhn_pool: <pool>

### OpenStack Instance Group Policies ###
### Set to 'affinity' if only one compute node ###
capsule_server_group_policies: "['anti-affinity']"

### OpenStack Instance Flavors ###
master_flavor: sat6.master
capsule_flavor: sat6.capsule
instance_flavor: m1.small

Run Satellite Deployment Playbook

[root@localhost]# ansible-playbook deploy-satellite.yml \
--private-key=/root/admin.pem -e @vars.yml -i inventory

PLAY RECAP *****************************************************************************************
localhost                  : ok=10   changed=5    unreachable=0    failed=0
sat6-master                : ok=45   changed=19   unreachable=0    failed=0

Bootstrap Existing Instances

The bootstrap-clients.yml playbook will simply run the sat6-bootstrap role. The role is responsible for connecting an existing instance to Satellite. A good practice in Ansible is to put tasks into roles and make them reusable, I have followed that.

The Satellite bootstrap steps are as follows:

  • Install Satellite CA Certificate
  • Register to Satellite with activation key
  • Install Katello agent
  • Start and enable goferd
  • Install Red Hat Insights
  • Install Puppet
  • Configure Puppet

Configure Inventory File

[root@localhost]# cp sample.inventory inventory
[root@localhost]# vi inventory
[server]
sat6.novalocal

[capsules]

[clients]
rhel2.novalocal
rhel1.novalocal

Run Bootstrap Playbook

[root@localhost]# ansible-playbook bootstrap-clients.yml --private-key=/root/admin.pem -e @../vars.yml -i ../inventory

PLAY RECAP *****************************************************************************************
rhel1.novalocal : ok=8 changed=2 unreachable=0 failed=0
rhel123.novalocal : ok=8 changed=2 unreachable=0 failed=0

Deploy New Instance via OpenStack and Bootstrap

Authentication credentials are set in the environment. We are using OpenStack CLI through Ansible. Another option is to use OpenStack modules written for Ansible and then authentication is of course built-in. This is a much cleaner approach but also requires various python libraries and versions like shade.

Make sure strict ssh host key checking is off (StrictHostKeyChecking) in /etc/sshd/ssh_config or set option on cli for Ansible. If strict host key checking is on you are of course prompted when connecting to host via ssh for first time and automation requires no manual inputs.

SSH to Satellite Master

[root@localhost(keystone_admin)]# ssh -i /root/admin.pem cloud-user@sat6-master

Change directory

[cloud-user@sat6-master]$ cd satellite-on-openstack-123

Disable host key checking for ansible

[cloud-user@sat6-master]$ export ANSIBLE_HOST_KEY_CHECKING=False

Setup OpenStack Client

[cloud-user@sat6-master]$ ansible-playbook setup-openstack-client.yml --private-key=/home/cloud-user/admin.pem -e @vars.yml

Run the provision-client.yml playbook. This will take a few minutes, as a new instance in OpenStack will be provisioned.

[cloud-user@sat6-master]$ ansible-playbook provision-client.yml --private-key=/home/cloud-user/admin.pem -e @vars.yml
PLAY RECAP *****************************************************************************************
localhost : ok=11 changed=6 unreachable=0 failed=0
rhel3 : ok=15 changed=12 unreachable=0 failed=0

If you are configuring puppet, a certificate needs to be signed in Satellite. You can of course setup auto-signed certificates but default is you need to sign. This means pupet agent run will fail. You need to go into Satellite, under Capsule and Certificates. There you can click sign to sign a certificate.