Example Packstack answer file with vxlan

Building on my previous post form James, Packstack is a pretty handy tool. Packstack is designed to easily set up test or proof-of-concept deployments. It uses Puppet modules to enable rapid deployment of OpenStack on existing servers over an SSH connection. PackStack does however make many assumptions in its configuration to simplify the installation process, and is not suitable for production deployments. Also it cannot deploy services in a highly available or load balanced configuration. See the Red Hat docs for more info.

vxlan has become the default plugin for layer2 networking for Neutron via the ML2 plugin, and makes deploying a simple multi-node configuration pretty straight forward. The example Packstack answer file below will produce a working OpenStack environment with three nodes, one controller, one networking node, and one compute node. It assumes two separate network segments, one on eth0 (public)and one on eth1(private). The public network contains the 192.168.1000/24 subnet and how the OpenStack services communicate between nodes and with the outside world. The private network is for our tenant networks and will contain the vxlan tunnels, this can be changed with the CONFIG_NEUTRON_OVS_TUNNEL_IF=eth1 option in the answer file below……

Advertisement

OpenStack Packstack Installation with External Connectivity

Handy info, specifically in regards to network-scripts

all things open

Packstack makes installing OpenStack REALLY easy. By using the –allinone option you could have a working self-contained RDO installation in minutes (and most of those minutes are spent waiting for packages to install). However, the –allinone option really should be renamed to the –onlywithinone today, because while it makes the installation very simple it doesn’t allow for instances spun up on the resulting OpenStack environment to be reachable from external systems. This can be a problem if you are trying to both bring up an OpenStack environment quickly and demonstrate integration with systems outside of OpenStack. With a lot of help and education from Perry Myers and Terry Wilson on Red Hat’s RDO team I was able to make a few modifications to the packstack installation to allow a user to use the packstack installation with –allinone and have external access to the instances launched on the host. While I’m…

View original post 656 more words

guestfish in 3 simple steps

libguestfs is a very handy library for manipulating image files. guestfis is a utility that uses libguestfs that allows you to mount an image file and make changes inside the image. One of the coolest features of libguestfs is that it does not require root prevelages to run or access an image file. The below example shows how to use guest fish to mount an make a change to a machine image.

1) install guestfish

# yum install guestfish

2) connect to the  image

guestfish –rw -a ~/Downloads/rhel-server-x86_64-kvm-6.4_20130130.0-4.qcow2

3) edit image

><fs> run
><fs> list-filesystems
><fs> mount /dev/vda1 /
><fs> vi /etc/fstab

 make any changes you need to

 ><fs> umount /
><fs> exit

 

Additional info:

Download machine images:

http://openstack.redhat.com/Image_resources

Documentation

http://libguestfs.org/guestfish.1.html

Upgrade to Fedora 19; Easy as 1, 2 ,3…

Upgrade form Fedora 18 to 19 with FedUp with 3 easy steps..

1. Install FedUp

$ sudo yum install fedup

2. Run FedUp

$ sudo fedup-cli --network 19

3. Executing the Upgrade

Reboot and select System Upgrade form Grub menu.

* there are some recommended post upgrade  steps but they are optional, I do recommend cleaning up your yum repos with a distro sync see the link below for more info

http://fedoraproject.org/wiki/FedUp

Managing OpenStack with The Foreman

Great post