Showing headlines posted by dba477

Recent build on CentOS 7.X qemu-kvm-ev-2.1.2-23.el7.1 enables CPU Pinning and NUMA Topology for RDO Kilo on CentOS 7.1. Qemu-kvm upgrade is supposed to be done as post installation procedure.Final target is to perform launching nova instance with CPU pinning on on i7 4790 Haswell CPU box.

Current post describes in details a sequence of steps which allow to work with Nova-Docker driver been built based on top commit of master nova-docker branch, stable/kilo branch is not supposed to be checked out before running `python setup.py install`. This results several additional efforts . . .

Hackery bellow was tested multiple times for AIO installs via packstack, providing completly functional Neutron Services and allows to create neutron routers, tenant's and external networks on single box or virtual machine.

The post follows up http://lxer.com/module/newswire/view/214893/index.html The most recent `yum update` on F22 significantly improved network performance on cloud VMs (L2) . Watching movies running on cloud F22 VM (with "Mate Desktop" been installed and functioning pretty smoothly) without sound refreshes spice memories

Actually, straight forward install RDO Kilo on Fedora 22 crashes due to relatively simple puppet mistake. Workaround for this issue was recently suggested by Javier Pena. Start packstack for multinode deployment as normal to get files require updates. After first packstack crash update /usr/share/ruby/vendor_ruby/puppet/provider/service/systemd.rb to include "F22" (in quite obvious place) on all deployment nodes

It is actually an update for Neutron on Kilo of original blog entry http://techbackground.blogspot.ie/2013/06/metadata-via-quant... considering Quantum implementation on Grizzly. From my standpoint understanding of core architecture of Neutron openstack flow in regards of nova-api metadata service access (and getting proper response from nova-api service) by VMs launching via nova causes a lot of problems due to leak of understanding of core concepts.

Set up RDO Kilo on Fedora 21 per https://www.rdoproject.org/Quickstart Next step is upgrade several python packages via Fedora Rawhide, build Nova-Docker Driver and switch openstack-nova-compute to run Nova-Docker Driver been built via stable/kilo branch of http://github.com/stackforge/nova-docker.git

I largely avoid systemd “debates” these days. They depress me due to all of the flawed reasoning and flinging emerging everywhere, but I felt that perhaps this little write-up could try to explain the background and causes for just why systemd inspires so much vitriol and turf warring.

Following bellow is brief instruction for traditional three node deployment test Controller&&Network&&Compute for oncoming RDO Kilo, which was performed on Fedora 21 host with KVM/Libvirt Hypervisor (16 GB RAM, Intel Core i7-4771 Haswell CPU, ASUS Z97-P ) Three VMs (4 GB RAM,2 VCPUS) have been setup

Following below a (tutorial for a) simple two node Controller&&Network and Compute test for oncoming RDO Kilo, which was performed on Fedora 21 host with KVM/Libvirt Hypervisor (16 GB RAM, i5-4690 Intel CPU,ASUS Z97-P Board). Two VMs (6 GB RAM, 2 VCPUS) have been setup , each one having 2 VNICs (eth0,eth1) for Controller and Compute Nodes emulation.

Posting bellow is targeting testing official version on Nova-Doker Driver for Openstack Kilo with development version RDO Kilo ( supposed GA day is 05/07/2015). RDO Kilo installed via `packstack --allinone` on virtual CentOS 7.1 machine.

Step by step instruction for setting up Nova-Docker driver && Openstack Kilo on Ubuntu 14.04 in devstack environment recoverable between reboots. Also routing across LAN is described for remote access to Devstack (stack.sh) public network.

Following bellow are brief instructions how to achieve extremely high performance of VMs created via devstack ( stack.sh ) inside another virtual machine created with Fedora 22 KVM Hypervisor and having Nested KVM feature enabled, working with sufficiently advanced Intel CPUs (Haswell kernel or above which have newer hardware virt extensions ) and 16 GB or more RAM.

This post is closely related to RDO Juno Multi Node deployment via packstack on Fedora 21 landscape with boxes having different boards and different Ethernet NICs inegrated either plugged into systems. Originally tested on Two Node Controller&&Network and Compute Fedora 21 .

This document describes steps Xing Lin (University of Utah) took to setup a compute node based on Ubuntu 14.04 for OpenStack "juno", using the Xen Project via libvirt approach. As of the fall of 2014, Openstack does not support this approach well as Xen Project is in the Group C of the hypervisor support matrix for Openstack

This article presents a step by step procedure for installing the latest version of nova docker on Fedora 21.

Testing the most recent Nova-Docker driver on Ubuntu 14.04 in devstack environment recoverable between reboots. Recently new patch... However,nova-docker containers have been lost after every reboot due to bridge br-ex came up with no IP and running ./rejoin-stack.sh didn't help much. This post describes workaround for this issue.

It's quite obvious that Nova-Docker driver set up success for real applications is important to get on Compute Nodes . It's nice when everything works on AIO Juno host or Controller, but just as demonstration.

As a final result of performing configuration bellow Juno dashboard will automatically spawn,launch and run Nova-Dockers containers on Controller and usual nova instances supposed to run on KVM Hypervisor (Libvirt driver) on Compute Node

During RDO Juno set up on Fedora 21 Workstation service target is deactivated on boot up, and tgtd is started (versus CentOS 7 installation procedure) , what requires some additional efforts to tune LVMiSCSI cinder back end on newest Fedora release.