Skip to main content

How to Install OpenStack Using RDO Packstack

choose-openstack-deployment-model

Prerequisites for Packstack

Packstack is based on OpenStack Puppet modules. It’s a good option when installing OpenStack for a POC or when all OpenStack controller services are installed on a single node. Packstack defines OpenStack resources declaratively and sets reasonable default values for all settings that are essential to installing OpenStack. The settings can be read or modified in a file, called the answer file in Packstack.
Packstack runs on RHEL 7 or later versions and the equivalent version for CentOS. The machine where Packstack will run needs at least 4GB of memory, at least one network adapter and x86 64-bit processors with hardware virtualization extensions.

Install RDO Repository

To install OpenStack, first, download the RDO repository rpm and install it.
On RHEL
$ sudo yum install -y https://rdoproject.org/repos/rdo-release.rpm
On CentOS
$ sudo yum install -y centos-release-openstack-mitaka

Install OpenStack

Install the Packstack installer and then run packstack to install OpenStack on a single node.
$ sudo yum install -y openstack-packstack
$ packstack --allinone
Once the installer completes, verify the installation by login at http://${YourIp}/dashboard.

Things to Consider

During the early days of our product development, Netcompany used Packstack to perform around 400 setups in a day. We found that, for this volume, the performance was not reliable and there were random timeouts. It was difficult to investigate deployment errors. In addition, it was non-trivial to customize the scripts to build and deploy our custom changes.
In general, we think it is best to use Packstack for installing OpenStack on a single node during a PoC when there isn’t a need to customize the install process.
Check out these other resources from platform9 below for more information on OpenStack Deployments.

Comments

Post a Comment

Popular posts from this blog

Zabbix, AWS and Auto Registration

One of the things I love the most with AWS is  auto-scaling . You choose an AMI, set some parameters and AWS will spin instances up and down whenever a threshold is breached. But with all these instances spinning up and down there are some unknowns. For example, what is the IP address of the new instance? Its host name? This can be critical when other components of your infrastructure are dependent on knowing these parameters. I had this problem when I started to use  Zabbix  as the monitoring system. At first it seemed like a complicated one, but Zabbix has a wonderful feature called  Auto Registration  which can be used exactly for this situation. I will try to show how to configure auto registration both on the client (EC2 instance running Ubuntu 14.04) and on the Zabbix server (Zabbix Server 2.4.2). Zabbix-agent Installation and Configuration Let’s start with installing zabbix-agent on the Ubuntu client: 1 2 $ sudo apt-get update $ sud...
8 comments
Read more

Merge AVHDX Hyper-V Checkpoints

When you create a snapshot of a virtual machine in Microsoft Hyper-V, a new file is created with the  .avhdx  file extension. The name of the file begins with the name of its parent VHDX file, but it also has a GUID following that, uniquely representing that checkpoint (sometimes called snapshots). You can see an example of this in the Windows Explorer screenshot below. Creating lots of snapshots will result in many  .avhdx  files, which can quickly become unmanageable. Consequently, you might want to merge these files together. If you want to merge the  .avhdx  file with its parent  .vhdx  file, it’s quite easy to accomplish. PowerShell Method Windows 10 includes support for a  Merge-VHD  PowerShell command, which is incredibly easy to use. In fact, you don’t even need to be running PowerShell “as Administrator” in order to merge VHDX files that you have access to. All you need to do is call  Merge-VHD  with the...
Post a Comment
Read more

SIPp cheatsheet

SIPp  is a free test tool and traffic generator for the SIP protocol. It uses XML format files to define test scenarios. General usage: sipp remote_host[:remote_port] [options] Some important command-line options: -sf filename Load test scenario from specified file. -inf filename Use CSV file to insert data substituted for [field0], [field1], etc into XML scenario. First line of file describes order of inserting field sets (SEQUENTIAL/RANDOM/USE). -sn name Use one of the embedded, predefined scenarios like "uac", "uas". -r rate Scenario execution rate, default value = 10 times per period, default period = 1000 ms. -rp period Scenario execution period [ms], combined with execution rate. Execution rate is combined of rate and period parameters, i.e. if period = 3500 and rate = 7 there will be 7 calls in 3.5 s. -t transport mode Set the transport mode: "u1" - UDP, one socket (default), "un" - UDP, one socket per call, other modes (...
Post a Comment
Read more