Archiv der Kategorie: OpenStack

PowerDNS + PowerAdmin with Master/Slave replication

I think it is self explaining, what we want to do, Bind is a little bit monolitic and has no api for flexible and dynamic
creation of machines (okay there are some aproaches, but anyhow), Designate was not working well for me … so I started with PowerDNS.
Here are my install notes:

sudo su

Install Epel repository:

yum install epel-release.noarch

Update the system (if not already done)

yum -y update

PowerDNS + PowerAdmin with Master/Slave replication weiterlesen

Build a multi Node Openstack Environment with Openvswitch

Since I have some time to write again I would like to share a small HowTo, how to Install a multi Node Openstack install with Openvswitch (ovs) and provider Networks as vlans for mixed Environments. At the end I will also add a subsection how to add a second vlan and a script how to add tenants, users and internal Networks for the tenants.

The whole Setup is made with Devstack, some bash-scripts. What you should look at, is for sure multi homing (iproute2) and a general documentation about
openvswitch and HowTo operate Openstack with provider networks. Over all this Documentation should be doable also without this (hopefully) and hopefully I have no typos 😉

Lets assume we have 3 networks / vlans
1. Network is the Management Network (for the communication between the nodes and for the webinterface -> Horizon)
The network is: 192.168.29.0/24 lets say vlan 29 this must be tagged (access port) on the switch / bladecenter –> as vlan 29 HINT: this is the „Segmentation ID“ the gateway is at the end: 192.168.29.254
Build a multi Node Openstack Environment with Openvswitch weiterlesen

Build with packer qcow2 images (e.g. for OpenStack)

First of all, what is Packer?

Packer is an opensource tool for automated creation of identical machine images
for multiple platforms from a single source configuration. That means OpenStack, Vagrant, VirtualBox, Amazon E2 or even docker container.

Packer handles the different virtualization platforms with the integration of plugins, which are then called by the build scripts for the desired virtualization platform .

So here I use the kvm build environment to build a qcow2 image for my OpenStack environment. Think about it, you can easily build up a Jenkins or Go job for automated builds, integrate a checked out source code and deploy a complete … e.g. Test environment for performance Tests … that’s quite cool … or behind LBaaS … start a new instance in OpenStack from latest stable Release … let’s start …
Build with packer qcow2 images (e.g. for OpenStack) weiterlesen