{"id":1808,"date":"2016-11-11T00:00:08","date_gmt":"2016-11-11T06:00:08","guid":{"rendered":"https:\/\/www.supportpro.com\/blog\/?p=1808"},"modified":"2018-10-01T04:24:13","modified_gmt":"2018-10-01T10:24:13","slug":"deploying-openstack-using-packstack","status":"publish","type":"post","link":"https:\/\/www.supportpro.com\/blog\/deploying-openstack-using-packstack\/","title":{"rendered":"Deploying Openstack using Packstack"},"content":{"rendered":"

OpenStack<\/strong> is a set of software tools for building and managing cloud computing platforms for public and private clouds. Mostly deployed as an infrastructure-as-a-service (IaaS). Deploy virtual machines and other instances that handle different tasks for managing a cloud environment on the fly. It makes horizontal scaling easy, which means that tasks that benefit from running concurrently can easily serve more or fewer users on the fly by just spinning up more instances. So we can say OpenStack is the future of cloud computing.<\/p>\n

OpenStack<\/strong> began in 2010 as a joint project of Rackspace Hosting and NASA. As of 2016, it is managed by the OpenStack Foundation, a non-profit corporate entity established in September 2012. Backed by some of the biggest companies in software development and hosting like Intel, Redhat, Cisco, Ubuntu etc, as well as thousands of individual community members.<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Packstack<\/strong> is a utility that uses Puppet modules to deploy various parts of OpenStack on multiple pre-installed servers over SSH automatically. Currently only Fedora, Red Hat Enterprise Linux (RHEL) and Centos are supported.<\/p>\n

Installing package \u201copenstack-packstack\u201d<\/b><\/span><\/p>\n

#yum install openstack-packstack -y<\/i><\/p>\n

Repo files for centos :<\/p>\n

#<\/i>yum install <\/i>https:\/\/rdoproject.org\/repos\/rdo-release.rpm<\/i><\/a><\/p>\n

#yum install centos-release-openstack-mitaka<\/i><\/p>\n

Generating answer file<\/b><\/span><\/p>\n

PackStack is able to generate a generic answer file which you are then able to customize to suit your specific deployment needs. Run the packstack command with the –gen-answer-file=FILE argument to generate an answer file.<\/p>\n

#packstack –gen-answer-file \/root\/answer.txt<\/i><\/p>\n

Editing answer file<\/b><\/span><\/p>\n

#vim \/root\/answer.txt<\/i><\/p>\n

CONFIG_HEAT_INSTALL = Y\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #Enable heat installing
\nCONFIG_ NTP_SERVERS = 172.25.254.254\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #Provide ip for ntp server
\nCONFIG_COMPUTE_HOSTS = 192.168.0.1, 192.168.0.2\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #IP list for compute node
\nCONFIG_STORAGE_HOSTS = 192.168.0.1, 192.168.0.2\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #IP list for storage node
\nCONFIG_KEYSTONE_ADMIN_PW = \u201cpassword\u201d\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #Provide password for admin
\nCONFIG_CINDER_VOLUME_CREATE = N\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #Disable to create cinder
\nCONFIG_LBAAS_INITIAL=Y\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #Enable load balance
\nCONFIG_NEUTRON_AGEN_INITIAL = Y\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #Enable network agents
\nCONFIG_NEUTRON_FWAAS = Y\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #Enable firewall
\nCONFIG_HORIZON_SSL = Y\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #Enable horizon (Dashboard)
\nCONFIG_HEAT_CFN_INITIAL = Y\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #Enable heat (Orchestration)
\nCONFIG_ PROVISION_DEMO = N\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #Disable Demo config<\/p>\n

Deploying openstack<\/b><\/span><\/p>\n

#packstack –answerfile<\/i><\/p>\n

Note: network manager is not supported in openstack. So disable network manager .<\/p>\n

Bridging<\/b><\/span><\/p>\n

Modify the network files with TYPE ‘OVSBridge’ and ‘OVSPort’ as shown below :<\/p>\n

#vim <\/i>\/etc\/sysconfig\/network-scripts\/<\/i>ifcfg-br-ex<\/i><\/p>\n

DEVICE = br-ex
\nBOOTPROTO=static
\nONBOOT=yes
\nTYPE=OVSBridge
\nDEVICETYPE=ovs
\nUSERCTL=yes
\nPEERDNS=yes
\nIPV6INIT=no
\nIPADDR=192.168.0.1
\nNETMASK=255.255.255<\/p>\n

#vim <\/i>\/etc\/sysconfig\/network-scripts\/<\/i>ifcfg-etho<\/i><\/p>\n

DEVICE=etho
\nONBOOT=yes
\nTYPE=OVSPort
\nDEVICETYPE=ovs
\nOVS_BRIDGE=br-EX<\/p>\n

Restart service network<\/b><\/span><\/p>\n

#systemctl restart network<\/i><\/p>\n

Open dashboard<\/b><\/span><\/p>\n

https:\/\/192.168.0.1<\/i>\u00a0\u00a0\u00a0 \u00a0 #IP address of basic node ( Here node 1)<\/p>\n

Username : admin
\nPassword : password<\/p>\n

 <\/p>\n

\"open_stack\"<\/a><\/p>\n

If you require help, contact SupportPRO Server Admin<\/a><\/p>\n

\"Server<\/a><\/span>