Lots of hosting companies and other service providers settled on combination of the Xen Project Hypervisor and CentOS as a platform for their virtualization needs. Unfortunately, CentOS 6 brings with it the same kernel as RHEL 6 — a kernel which lacks support for the Xen Project Hypervisor.
The Xen Project Developer Summit is approaching: the Call For Participation will be open for two more days until May 16, 2014 11:55pm (EST).
I wanted to also take the opportunity to introduce this year’s Program Management Committee.
With the Xen Project Hypervisor 4.4 released a bit more than a month ago, the project is planning for version 4.5, so it’s a good time to outline how we manage releases.
It’s hard to know what the right thing is. Once you know, it’s hard not to do it.
Harry Fertig (Kingsley). The Confession (1999 film)
Recent upgrade firefox up to 29.0-5 on Fedora 20 causes to fail login to Dashboard Console for Havana F20 Controller been setup per VNC Console in Dashboard on Two Node Neutron GRE+OVS F20 Cluster
This week, we are reblogging this excellent piece from Luis from SUSE.
Last year marked the arrival of the very first Xen Project User Summit. This year, we are aiming to draw over 100 people to the Lighthouse Executive Conference Center in the heart of New York City to discuss the use of the Xen Project hypervisor.
We are actively looking for people who are willing to talk about:
The OpenStack Networking components are deployed on the Controller, Compute, and Network nodes in the following configuration:
In case of Two Node Development Cluster :-
Controller node: hosts the Neutron server service, which provides the networking API and communicates with and tracks the agents.
DHCP agent: spawns and controls dnsmasq processes to provide leases to instances. This agent also spawns neutron-ns-metadata-proxy processes as part of the metadata system.
Per Direct_access _to_Nova_metadata
In an environment running Neutron, a request from your instance must traverse a number of steps:
1. From the instance to a router,
2. Through a NAT rule in the router namespace,
3. To an instance of the neutron-ns-metadata-proxy,
4. To the actual Nova metadata service