Showing posts from March, 2016

[Ansible] My first step to use Ansible

Before get started to use Ansible, you need to add public ssh key to your remote Server first. If you want to setup SSH keys to allow logging in without a password, you can do so with a single command.
The first thing you’ll need to do is make sure you’ve run the keygen command to generate the keys:

ssh-keygen -t rsa Then use this command to push the key to the remote server, modifying it to match your server name. cat ~/.ssh/ | ssh user@hostname 'cat >> .ssh/authorized_keys'
So, from now on you are able to try Ansible to control your remote server.

# sudo pip install ansible
# sudomkdir /etc/ansible
# cd /etc/ansible/
# vim hosts

[LBaaS] The Load Balance as a Service trace records

A couple of days ago, my colleague imparts Load Balance as a Service (LBaaS) which is the Neutron Plugin to provide the load balancer functionality in OpenStack. Unavoidably, I still like to drill down how it works so that we won't only understand the surface of this function. This article is only focused on the trace record because I have studied the concept of LBaaS. For those who don't know about its concept and implementation, please check out other resources first, ex: 

If created a lb pool ready, you can see something like the following picture. My point is to trace subnet and network port.

From the "subnet" link, we can trace back to the its detail and also can go to its network detail by clicking the link of network id.  

Here we can find the vip port that is for our load balancer as follows.
Click it to see its details.

Now, we will use the first part of port id (70081ac2) to trace what happens in linux netw…