Open Source PAAs scenario: Deploying Cloudfoundry on OpenStack (ii) deploying OpenStack

1. Hardware requirements
2. Installing OpenStack
   1. 1 Installing the CentOS 65 system and emptying the Iptables firewall rules
   2. 2 The required toolkit for installing the system includes OpenStack-dependent and cloudfoundry-dependent
   3. 3 Installing Epel Repo
   4. 4 Upgrade Current system
   5. 5 Installing OpenStack Repo currently cloudfoundry can only support Havana version of OpenStack
   6. 6 Installing Packstack
   7. 7 Synchronization Time
   8. 8 Installing single-node OpenStack
3. Configure OpenStack
   1. 0 Installed OpenStack Dashboard There is a small bug using the following command fix
   2. 1 Demo Tenant Default quota quota Not enough to install Cloudfoundry so add demo quota first
   3. 2 Extended disk space

[Python]View Plaincopy

Since both AWS and Vsphere/vcloud are not available for free, this article describes if you are deploying Cloudfoundry to an open source IaaS. The focus of this article is how to deploy Cloudfoundry, so OpenStack's deployment takes the simplest scenario-single-node OpenStack-If the reader wants to know how to deploy a distributed, high-availability OpenStack, refer to the related articles on the network.

So, I chose the CentOS and Redhat tools Packstack to deploy a single-node OpenStack. Currently Cloudfoundry only supports Folsom,grizilly, and Havana three versions of OpenStack.

0. Hardware requirements cpu:x86_64 Architecture of the Intel I5 i7 or Xeon Memory: More than 64GB hard disk: 500G or more of the remaining space 1. Installing OpenStack1.1 Installing the CentOS 6.5 system and emptying the Iptables firewall rules [Python]View Plaincopy

1. # iptables-f

1.2 Install the required toolkit for the system, including OpenStack-dependent and cloudfoundry-dependent [Python]View Plaincopy

1. <pre name="code" class="Python" ># yum install-y gcc python perl vim man wget ntpdate sysstat zlib-d Evel Krb5-devel openssl-devel zlib libyaml-devel readline-devel libyaml-devel readline-devel gcc-c++ glibc-headers Readl ine libxml2 libxml2-devel libxslt libxslt-devel genisoimage sqlite sqlite-devel mysql mysql-devel postgresql postgresql-d Evel git

1.3 Installing Epel Repo [Python]View Plaincopy

1. # RPM-UVH http://ftp.sjtu.edu.cn/fedora/epel/6/i386/epel-release-6-8.noarch.rpm

1.4. Upgrade Current system [Python]View Plaincopy

1. # Yum-y Upgrade

1.5 Installing OpenStack repo, currently cloudfoundry can only support Havana version of OpenStack [Python]View Plaincopy

1. # RPM-UVH https://repos.fedorapeople.org/repos/openstack/EOL/openstack-havana/rdo-release-havana-9.noarch.rpm

Should now Havana has been categorized as an old version of the OpenStack path has changed Epel path error Nano/etc/yum.repo.d/rdo-release.repo change path to baseurl=https:// repos.fedorapeople.org/repos/openstack/eol/openstack-havana/epel-6/

1.6 Installing Packstack [Python]View Plaincopy

1. # yum Install-y openstack-packstack

1.7 Synchronization Time [Python]View Plaincopy

1. # Ntpdate-u Time.asia.apple.com

1.8 Installing single-node OpenStack [Python]View Plaincopy

1. # Packstack-allinone

Because the Havana version of Packstack has terminated the life cycle, so the direct operation will definitely error, after the error, the return to generate a answer-file TXT file, modify the configuration items inside config_use_epel=n for Config_use_ Epel=y run Packstack--answer-file=xxx.txt to install successfully.

2. Configure OpenStack to use Packstack after installation, all services are installed on one node, and a user named Demo tenant and demo is created. This article installs Cloudfoundry using demo user and demo tenant.
2.0 The installed OpenStack Dashboard has a small bug, use the following command to fix [Python]View Plaincopy

1. # sed-i ' s/"Member"/"\_member\_"/'/etc/openstack-dashboard/local_settings
2. # Service httpd Restart

2.1 Demo Tenant's default quota (Quota) is not enough to install Cloudfoundry, so add demo Quota first [Python]View Plaincopy

1. # Nova Quota-update--instances--ram 60000--cores $ (Keystone Tenant-list | awk '/demo/{print $} ')

2.2 Extended disk space

Openstack allocates a space of 20G to cinder by default, and Cloudfoundry needs 500G of space, which needs to be expanded to cinder-volumns size first. If there is unallocated disk space, you can extend cinder-volumes this volume group directly. If there is no disk space, you need to use the Linux loop device. For more information about Loop device, see Http://en.wikipedia.org/wiki/Loop_device

[Python]View Plaincopy

1. # dd If=/dev/zero of=/var/lib/cinder/cinder-volumes1 bs=1k count=500000000
2. # losetup-f (Find a loop device that is not used, the author uses/dev/oop2 here)
3. # losetup/dev/loop2/var/lib/cinder/cinder-volumes1
4. # Vgextend CINDER-VOLUMES/DEV/LOOP2

This way, OpenStack is already set up and ready to install Cloudfoundry.

Open Source PAAs scenario: Deploying Cloudfoundry on OpenStack (ii) deploying OpenStack