Posts

Showing posts from June, 2016

[Ceilometer] To survey how to improve the performance of OpenStack Ceilometer

Image
Frankly speaking, OpenStack Ceilometer will suffer some kind of performance issues sooner or later if you don't modify or tune the configuration. The issues has two parts that need you to consider. One is the message bus and API loading, and the other is database. However, I find some best practices which are easy and quick for us to adopt. Here you go:
1. Telemetry(Ceilometer) best practiceshttp://docs.openstack.org/admin-guide/telemetry-best-practices.html a. Data collectionBased on your needs, you can edit the pipeline.yaml configuration file to include a selected number of meters while disregarding the rest. By default, Telemetry service polls the service APIs every 10 minutes. You can change the polling interval on a per meter basis by editing the pipeline.yaml configuration file. for example: vim /etc/ceilometer/ceilometer.conf => evaluation_interval=120 vim /etc/ceilometer/pipeline.yaml => interval: 120

you can delay or adjust polling requests by enabling the jitter su…

[Linux] Why does Linux require moving IP from eth interface to bridge interface?

This could be a common problem if you have KVM ( or other hypervisor in Linux ) on your physical server and want to use bridge mode with your VMs. At the same time, you also want to let your physical server has the network that can be accessed from other hosts at the same network subnet. At this moment, when a network interface (e.g., eth0) is added to a Linux bridge (e.g., br0), the IP address must be removed from eth0 and added to br0 for the networking to function properly.

I find some answers as follows:
http://unix.stackexchange.com/questions/86056/why-does-linux-require-moving-ip-from-eth-interface-to-bridge-interface
http://unix.stackexchange.com/questions/52674/why-doesnt-eth0-get-an-ip-address-when-set-up-in-a-bridge

==>
The NIC represents the uplink cable. A cable is layer 1, not layer 3. Now the Bridge works as the device that is being addressed for network traffic (incoming) on the server - either on layer 2 (Ethernet/MAC) and/or layer 3 (IP). So the device that responds to …

[Neutron] Neutron Cheat Cheat Sheet

Image
In recent days, the hand drawing style is becoming more and more pervasive in Taiwan. I don't know how it happens, but at least I can draw the Neutron cheat cheat sheet to echo this kind of style for fun.

P.S: This picture is originally for my colleagues to trouble shooting the Neutron networking problems.

[Neutron and SDN] Warm-up for understaning the integration of Neutron and SDN

Image
I just spend some time to study the integration of Neutron and SDN. Furthermore, I also take a look at how ODL and ONOS are integrated with OpenStack Neutron. The following content and picture ( with URL link) are excerpted from the variety of resource in the internet. Some of sections has my comment with P.S. I think it can give you a clear concept of Neutron and SDN controller.

Neutron and SDN
P.S: This picture gives an overall architecture about Neutron and SDN controller that are integrated together. http://thenewstack.io/sdn-controllers-and-openstack-part1/

When an OpenStack user performs any networking related operation (create/update/delete/read on network, subnet and port resources) the typical flow would be as follows: The user operation on the OpenStack dashboard (Horizon) will be translated into a corresponding networking API and sent to the Neutron server. The Neutron server receives the request and passes the same to the configured plugin (assume ML2 is configured with an ODL m…