jbadiapa

To install the python-wrapper

$ sudo yum install python2-selenium.noarch

Selenium can also be installed through pip

$ sudo pip install selenium

To install the browser engine

jbadiapa

  +----------------------------------------+
  |                                        |
  |                             Virt-Host  |
  |                                        |
  |                                        |                  +-----------+
  |                                        |                  |           |
  |  +-------+    +----------------------+ |                  |  Laptop   |
  |  |       |    |    Undercloud        | |                  |           |
  |  |Ovr-net|    |     IP-under         | |                  +-----------+

jbadiapa

Telemetry Platform Deployment Over Openstack

Instructions in this gist are for the deployment of the telemetry platform on top of OpenShift Origin v3.9. Deployment of the platform is done in two (2) steps. The first step is bootstrap of the virtual hosts and installation of the virtual machines (VM) as there were overcloud nodes on an Openstack. Following with the installation of the telemetry platform with the telemetry-framework

Prerequisites TBD

jbadiapa

### Check the yaml files on the undercloud
#Puppet
for file in `find /usr/share/openstack-tripleo-heat-templates/puppet  -type f -name '*.yaml'`; do
  ITER=`grep LoggingSource $file | wc -l`
  if [ $ITER -lt 2 ]; then
   echo $file
  fi 
done

### Check the yaml files on the undercloud

jbadiapa

How To Configuring The Logging of the Services on TripleO (fluentd)

To make fluentd aware of the service log files, it needs to set up a couple of variable one for the owner of the file tripleo_fluentd_groups_SERVICE_NAME and the other one to set the log files tripleo_fluentd_sources_SERVICE_NAME.

Syntaxys

Firstly, the SERVICE_NAME should be the name that the service has on the variable

jbadiapa

Service Assusance Framework (SAF) - Telemetry Framework (TF)

TripleO Service Assurance Framework Integration

1. Provisioning with tripleo-quickstart
2. Disable the unused nodes
3. Download the Telemetry patch
4. Deploy Telemetry Framework
5. Overcloud deployment

jbadiapa

TripleO first steps

Deploy

Options

To deploy a full environment there are a couple of projects:

• tripleo-quickstart

jbadiapa

How to create containers

Modified the containers

Editing the files on /usr/share/kolla/docker/XXXXX

Create the kolla file

jbadiapa

NO FEATURE
NODES=3ctlr_2comp_3ceph
# modify the ceph nodes memory to 5GB at config/nodes/3ctlr_2comp_3ceph.yml 
control_memory: 8192
control_disk: 45
compute_memory: 5120
compute_disk: 50
ceph_memory: 5120
ceph_disk: 55
undercloud_memory: 12288

jbadiapa

---
- name: Restore backup
  hosts: controller
  become: yes
  vars:
    tripleo_container_cli: podman
    run_rear: false
    nfs_server: 14.195.11.200
    mysql_db_file: openstack-backup-mysql.sql
    mysql_grants_file: openstack-backup-mysql-grants.sql