Skip to main content

Describing TOAD - TripleO automated deployer

An overview of the TOAD framework and the advantages

What is TOAD?

What components make up TOAD?

Requirements to install TOAD

  • Two different use cases: virtualized and baremetal
  • Only one Jenkins+Nginx VM needed to spin up the platform (8gb at least) 
  • RHEL7 / Centos7 operating system

Virtualized deploys

  • One server for slave and virtualized TripleO deployment:
    • multi-core
    • 16GB mem (better 32GB)
    • 60GB disk
    • external network
  • Needs RHN subscription for OSP jobs.

Baremetal deploys

  • One server for slave and virtualized undercloud:
    • multi-core
    • 16GB mem
    • 60GB disk
    • external network
    • Needs RHN subscription for OSP jobs.
  • One server for controller and one for compute:
    • multi-core
    • 4GB memory
    • 60GB disk
    • IPMI support
    • independent NIC/VLANS for provisioning and administration.
Can be extended with more controller and computes for HA

How users benefit from TOAD?

  • Easy: perform full virtualized and baremetal deployments with one click
  • Automated: avoid manual steps that are prone to human errors
  • Repeatable: job definitions and configs stored in git repos, track changes
  • Battle tested: relies on TripleO quickstart, used for upstream CI
  • Complete: choose between different releases, and RDO/OSP deploys
  • Flexible: extend with customization scripts and templates. Consume local repos with pinned versions and custom packages
  • Visible: logs for all deployment steps are collected and published 

TOAD job deployment workflow 

Labels:

Comments

  1. ICS Cyber SecurityJuly 1, 2017 at 1:23 PM

    Nice blog... This blog is helpful for me to understand OpenStack development. Thanks for sharing information

    ReplyDelete

Post a Comment

Popular posts from this blog

Enable UEFI PXE boot in Supermicro SYS-E200

When provisioning my Supermicro SYS-E200-8D machines (X10 motherboard), i had the need to enable UEFI boot mode, and provision through PXE. This may seem straightforward, but there is a set of BIOS settings that need to be changed in order to enable it. First thing is to enable EFI on LAN , and enable Network Stack. To do that, enter into BIOS > Advanced > PCIe/PCI/PnP configuration and check that your settings match the following: See that PCI-E have EFI firmware loaded. Same for Onboard LAN OPROM and Onboard Video OPROM. And UEFI Network stack is enabled , as well as IPv4 PXE/IPv6 PXE support. Next thing is to modify boot settings. The usual boot order for PXE is to first add hard disk and second PXE network . The PXE tools (for example Ironic) will set a temporary boot order for PXE (one time) to enable the boot from network, but then the reboot will be done from hard disk. So be sure that your boot order matches the following: See that the first order is hard d
1 comment
Read more

Test API endpoint with netcat

Do you need a simple way to validate that an API endpoint is responsive, but you don't want to use curl? There is a simple way to validate the endpoint with nc, producing an output that can be redirected to a logfile and parsed later: URL=$1 PORT=$2 while true; do     RESULT=$(nc -vz $URL $PORT 2>&1)     DATE=$(date)     echo $DATE $RESULT     sleep 1 done You can all this script with the API URL as first parameter, and API port as the second. netcat will be accessing to that endpoint and will report the results, detecting when the API is down. We also can output the date to have a reference when failures are detected. The produced output will be something like: vie jun 26 08:19:28 UTC 2020 Ncat: Version 7.70 ( https://nmap.org/ncat ) Ncat: Connected to 192.168.111.3:6443. Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds. vie jun 26 08:19:29 UTC 2020 Ncat: Version 7.70 ( https://nmap.org/ncat ) Ncat: Connected to 192.168.111.3:6443. Ncat: 0 bytes sent, 0 bytes
1 comment
Read more

Create and restore external backups of virtual machines with libvirt

A common need for deployments in production, is to have the possibility of taking backups of your working virtual machines, and export them to some external storage. Although libvirt offers the possibility of taking snapshots and restore them, those snapshots are intended to be managed locally, and are lost when you destroy your virtual machines. There may be the need to just trash all your environment, and re-create the virtual machines from an external backup, so this article offers a procedure to achieve it. First step, create an external snapshot So the first step will be taking an snapshot from your running vm. The best way to take an isolated backup is using blockcopy virsh command. So, how to proceed? 1. First you need to extract all the disks that your vm has. This can be achieved with domblklist command:   DISK_NAME=$(virsh domblklist {{domain}} --details | grep 'disk' | awk '{print $3}') This will extract the name of the device that the vm is using
4 comments
Read more