Technology articles

This article is going to cover how to deploy TripleO Quickstart on baremetal. The undercloud will still be virtualized, but controller and compute will be deployed on baremetal. This post belongs to a serie. In order to get more knowledge about TOAD and tripleo-quickstart, please read http://teknoarticles.blogspot.com/2017/02/automated-osp-deployments-with-tripleo.html and http://teknoarticles.blogspot.com/2017/02/describing-cira-continuous-integration.html Requirements Hardware A baremetal server is needed to act as Jenkins slave + contain virtualized undercloud. A multi-core CPU, 16GB of RAM and 60GB of disk is the recommended setup. One server for each controller/compute that needs to be deployed. They need to have at least 8GB of RAM. Network IPMI access is needed for each controller/compute server  A provisioning network is required, the jenkins slave and the controller/compute nodes need to be on the same network, and the defined CIDR cannot be used for any ot...

In this article I'm going to show a method for automating OSP (RedHat OpenStack platform) deployments. These automated deployments can be very useful for CI, or simply to experiment and test with the system. Components involved TOAD : set of playbooks to deploy Jenkins, jenkins-job-builder and an optional ELK stack. This will install a ready to use system with all the preconfigured jobs (including OSP10 deployments and image building). TOAD jenkins-jobs : A set of job templates and macros, using jenkins-job-builder syntax, that get converted into Jenkins jobs for building the OSP base images and for deploying the system. TOAD job-configs : A set of job configurations to be used along with the jenkins-jobs repo. It provides a set of basic configs to build OpenStack using RDO or OSP. TripleO quickstart : set of ansible playbooks, used for building images and for RDO/OSP deployments. System requirements One VM to run a Jenkins master + nginx provided by TOAD. If you wa...

An overview of the TOAD framework and the advantages What is TOAD? Fully automated deployment using Ansible (single command spin up) Main goal: to automate OSP deployments for continuous integration (CI) and development purposes TOAD is a CI framework using off-the-shelf components that many partners are familiar with: Jenkins Jenkins Job Builder (JJB): http://docs.openstack.org/infra/jenkins-job-builder/   TripleO Quickstart (oooq): https://www.rdoproject.org/tripleo/   Optional ELK Stack (ElasticSearch, Logstash, Kibana)  Its core component is TripleO Quickstart , used for TripleO upstream testing Fully customizable with oooq settings; can be extended Deploy environments with one click; trash after finished  Of course it’s open source! :) https://github.com/redhat-nfvpe/toad https://github.com/redhat-nfvpe/jenkins-jobs   https://github.com/redhat-nfvpe/job-configs What components make up TOAD? Requirements to install TOAD Two...

Continued from http://teknoarticles.blogspot.com.es/2016/12/start-using-whole-disk-images-with.html For security reasons, there may be the need of encrypting several partitions of volumes on your images. And you can have a pre-created image with that encryption on place, instead of having to do manually after boot. This can be done with guestfs and luks . The following script will show how to perform that encryption and mount it automatically: #!/usr/bin/env python import binascii import guestfs import os # remove old generated drive try:     os.unlink("/tmp/overcloud-full-partitioned.qcow2") except:     pass g = guestfs.GuestFS(python_return_dict=True) # import old and new images print("Creating new repartitioned image") g.add_drive_opts("/tmp/overcloud-full.qcow2", format="qcow2", readonly=1) g.disk_create("/tmp/overcloud-full-partitioned.qcow2", "qcow2", 10 * 1024 * 1024 * 1024) #10G g.add_drive_opts("/tmp/o...

What are the differences between flat partition image and whole disk image? In order to understand this article, you first need to know what a flat partition image and a whole disk image are, and the differences between each other. flat partition image: disk image that just contains all the desired content in a filesystem, but does not carry any information about partitions on it, and it does not include a bootloader. In order to boot from a whole disk image, the kernel and ramdisk images need to be passed independently when booting, relying on an external system to mount. whole disk image: image that contains all the information about partitions, bootloaders... as well as all the desired content. It can boot independently, without the need of external kernels or systems to mount it. Right now, OpenStack Ironic   supports both kind of images, but OpenStack TripleO was only supporting flat partition images. TripleO added support for whole disk images Since python-triple...

About Atomic project - http://www.projectatomic.io Atomic is a lightweight operating system, assembled from RPM content. It is mainly designed to run applications in Docker containers. Hosts based on RHEL, Fedora and CentOS are available with Atomic. Project Atomic includes the following components: Docker , Kubernetes , rpm-ostree , systemd What are the advantages of Atomic? Using Atomic distributions limits the patch frequency for administrators. The usage of Docker containers offers a clear path to deliver consistent and fully tested stacks. Containers secured with Linux namespaces, cGroups, and SELinux give isolation close to that of a VM, with much greater flexibility and efficiency. About diskimage-builder - http://docs.openstack.org/developer/diskimage-builder/ Diskimage-builder is a tool for building disk images, file system images and ramdisk images. It is the tool used in OpenStack projects to generate base images for deployments and testing. The problem: ...

Automated OVA deployments using OpenStack infrastructure from Yolanda Robla