{"id":1375,"date":"2012-10-17T02:04:48","date_gmt":"2012-10-17T07:04:48","guid":{"rendered":"http:\/\/www.migrate2cloud.com\/blog\/?p=1375"},"modified":"2016-03-21T02:47:00","modified_gmt":"2016-03-21T07:47:00","slug":"openstack-cloud-software","status":"publish","type":"post","link":"https:\/\/www.migrate2cloud.com\/blog\/openstack-cloud-software\/","title":{"rendered":"Openstack Cloud Software"},"content":{"rendered":"

<\/h2>\n

OpenStack : The Mission<\/strong><\/h2>\n

\u201c To produce the ubiquitous Open Source Cloud Computing platform that will meet the needs of public and private cloud providers regardless of size, by being simple to implement and massively scalable.\u201d<\/p>\n

OpenStack is a collection of open source software projects that enterprises\/service providers can use to setup and run their cloud compute and storage infrastructure.Rackspace and NASA are the key initial contributors to the stack. Rackspace contributed their “Cloud Files” platform (code) to power the Object Storage part of the OpenStack, while NASA contributed their “Nebula” platform (code) to power the Compute part. OpenStack consortium has managed to have more than 150 members including Canonical, Dell, Citrix etc.<\/p>\n

There are 5 main service families under OpenStack<\/strong><\/h2>\n

\u2022 Nova\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 – \u00a0 Compute Service <\/strong><\/p>\n

\u2022 Swift\u00a0\u00a0\u00a0\u00a0 \u00a0 \u00a0 – \u00a0\u00a0 Storage Service <\/strong><\/p>\n

\u2022 Glance\u00a0\u00a0\u00a0 \u00a0 – \u00a0\u00a0 Imaging Service <\/strong><\/p>\n

\u2022 Keystone\u00a0 – \u00a0\u00a0 Identity Service <\/strong><\/p>\n

\u2022 Horizon\u00a0\u00a0\u00a0 – \u00a0\u00a0 UI Service <\/strong><\/p>\n

Open Stack Compute Infrastructure (Nova)<\/strong><\/h2>\n

Nova is the Computing Fabric controller for the OpenStack Cloud. All activities needed to support the life cycle of instances within the OpenStack cloud are handled by Nova. This makes Nova a Management Platform that manages compute resources, networking, authorization, and scalability needs of the OpenStack cloud. But, Nova does not provide any virtualization capabilities by itself; instead, it uses libvirt API to interact with supported hypervisors. Nova exposes all its capabilities through a web services API that is compatible with the EC2 API of Amazon Web Services.<\/p>\n

Functions and Features:<\/strong><\/h2>\n

\u2022 Instance life cycle management<\/p>\n

\u2022 Management of compute resources<\/p>\n

\u2022 Networking and Authorization<\/p>\n

\u2022 REST-based API<\/p>\n

\u2022 Asynchronous eventually consistent communication<\/p>\n

\u2022 Hypervisor agnostic : support for Xen, XenServer\/XCP, KVM, UML, VMware vSphere and Hyper-V<\/p>\n

OpenStack Storage Infrastructure (Swift)<\/strong><\/h2>\n

Swift provides a distributed, eventually consistent virtual object store for OpenStack. It is analogous to Amazon Web Services – Simple Storage Service (S3). Swift is capable of storing billions of objects distributed across nodes. Swift has built-in redundancy and fail-over management and is capable of archiving and media streaming. It is extremely scalable in terms of both size (several petabytes) and capacity (number of objects).<\/p>\n

Functions and Features<\/strong><\/h2>\n

\u2022 Storage of large number of objects<\/p>\n

\u2022 Storage of large sized objects<\/p>\n

\u2022 Data Redundancy<\/p>\n

\u2022 Archival capabilities – Work with large datasets<\/p>\n

\u2022 Data container for virtual machines and cloud apps<\/p>\n

\u2022 Media Streaming capabilities<\/p>\n

\u2022 Secure storage of objects<\/p>\n

\u2022 Backup and archival<\/p>\n

\u2022 Extreme scalability<\/p>\n

OpenStack Imaging Service (Glance) <\/strong><\/h2>\n

OpenStack Imaging Service is a lookup and retrieval system for virtual machine images. It can be configured to use any one of the following storage backends:<\/p>\n

\u2022 Local filesystem (default)<\/p>\n

\u2022 OpenStack Object Store to store images<\/p>\n

\u2022 S3 storage directly<\/p>\n

\u2022 S3 storage with Object Store as the intermediate for S3 access.<\/p>\n

\u2022 HTTP (read-only)<\/p>\n

Functions and Features<\/strong><\/h2>\n

\u2022 Provides imaging service<\/p>\n

OpenStack Identity Service (Keystone)<\/strong><\/h2>\n

Keystone provides identity and access policy services for all components in the OpenStack family. It implements it’s own REST based API (Identity API). It provides authentication and authorization for all components of OpenStack including (but not limited to) Swift, Glance, Nova. Authentication verifies that a request actually comes from who it says it does. Authorization is verifying whether the authenticated user has access to the services he\/she is requesting for.<\/p>\n

Keystone provides two ways of authentication. One is username\/password based and the other is token based. Apart from that, keystone provides the following services:<\/p>\n

\u2022 Token Service (that carries authorization information about an authenticated user)<\/p>\n

\u2022 Catalog Service (that contains a list of available services at the users’ disposal)<\/p>\n

\u2022 Policy Service (that let’s keystone manage access to specific services by specific users or groups).<\/p>\n

Openstack Administrative Web-Interface (Horizon)<\/strong><\/h2>\n

Horizon the web based dashboard can be used to manage \/administer OpenStack services. It can be used to manage instances and images, create keypairs, attach volumes to instances, manipulate Swift containers etc. Apart from this, dashboard even gives the user access to instance console and can connect to an instance through VNC. Overall, Horizon<\/p>\n

Features the following:<\/h2>\n

\u2022 Instance Management – Create or terminate instance, view console logs and connect through VNC, Attaching volumes, etc.<\/p>\n

\u2022 Access and Security Management – Create security groups, manage keypairs, assign floating IPs, etc.<\/p>\n

\u00a0\u2022 Flavor Management – Manage different flavors or instance virtual hardware templates.<\/p>\n

\u00a0\u2022 Image Management – Edit or delete images.<\/p>\n

\u00a0\u2022 View service catalog.<\/p>\n

\u00a0\u2022 Manage users, quotas and usage for projects.<\/p>\n

\u00a0\u2022 User Management – Create user, etc.<\/p>\n

\u00a0\u2022 Volume Management – Creating Volumes and snapshots.<\/p>\n

\u00a0\u2022 Object Store Manipulation – Create, delete containers and objects.<\/p>\n

\u00a0\u2022 Downloading environment variables for a project.<\/p>\n

INSTALLATING OPEN STACK <\/strong><\/h2>\n

We can install open stack ESSEX very easily using StackGeek script. Login to your box and install git<\/code> with apt-get<\/code>. We\u2019ll become root and do an update first.<\/p>\n

sudo\u00a0 su<\/span>
\napt-get update<\/span>
\napt-get install git<\/span><\/p>\n

Now checkout the StackGeek scripts from Github:<\/p>\n

git clone git:\/\/github.com\/StackGeek\/openstackgeek.git <\/span>  \r\ncd openstackgeek<\/span><\/span><\/pre>\n
Install the Base Scripts<\/h3>\n
Be sure to take a look at the scripts before you run them. Keep in mind the scripts will periodically prompt you for input, either for confirming installation of a package, or asking you for information for configuration.<\/p>\n
Start the installation by running the first script:<\/p>\n
.\/openstack_base_1.sh<\/span><\/pre>\n
When the script finishes you\u2019ll see instructions for manually configuring your network. You can edit the interfaces<\/code> file by doing a:<\/p>\n
vim \/etc\/network\/interfaces<\/span><\/pre>\n
Copy and paste the network code provided by the script into the file and then edit:<\/p>\n
auto eth0 <\/span>\r\niface eth0 inet static<\/span>\r\n  address 192.168.1.48<\/span>\t\t\r\n  network 192.168.1.0<\/span>\t\t\r\n  netmask 255.255.255.0<\/span>\r\n broadcast 192.168.1.255<\/span>\r\n  gateway 192.168.1.124<\/span>\t\t\t\r\n  dns-nameservers 8.8.8.8 <\/span> \r\nauto eth1<\/span><\/pre>\n
Change the settings for your network configuration and then restart networking and run the next script:<\/p>\n
\/etc\/init.d\/networking restart<\/span>\r\n\r\nThen run the second script :\r\n\r\n.\/openstack_base_2.sh<\/span><\/pre>\n
After the second script finishes, you\u2019ll need to set up a logical volume for Nova to use for creating snapshots and volumes. Nova is OpenStack\u2019s compute controller process.<\/p>\n
Here\u2019s the output from the format and volume creation process:-<\/p>\n
root@manager-System-Product-Name:\/openstackgeek# fdisk \/dev\/sda<\/span>\r\nDevice contains neither a valid DOS partition table,nor Sun,SGI or OSF disklabel<\/span>\r\nBuilding a new DOS disklabel with disk identifier 0xb39fe7af.<\/span>\r\nChanges will remain in memory only, until you decide to write them.<\/span>\r\nAfter that, of course, the previous content won't be recoverable.<\/span>\r\n\r\nWarning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)<\/span>\r\n\r\nCommand (m for help): n<\/span>\r\nPartition type:<\/span>\r\n   p<\/span>   primary (0 primary, 0 extended, 4 free)<\/span>\r\n   e<\/span>   extended<\/span>\r\nSelect (default p): p Partition number (1-4, default 1): 3 <\/span> \r\nFirst sector (2048-62914559, default 2048):<\/span> \r\n Using default value 2048<\/span> Last sector,(2048-62914559,default 62914559):<\/span> \r\nUsing default value 62914559 <\/span>\r\nCommand (m for help): w The partition table has been altered! <\/span>\r\nCalling ioctl() to re-read partition table. Syncing disks<\/span>.\r\nroot@manager-System-Product-Name:\/openstackgeek# pvcreate -ff \/dev\/sda3<\/span>\r\n Physical volume \"\/dev\/sda3\" successfully created<\/span>\r\nroot@manager-System-Product-Name:\/openstackgeek# vgcreate nova-volumes \/dev\/sda3<\/span>\r\n Volume group \"nova-volumes\" successfully created <\/span><\/pre>\n
Note:<\/code> Your device names may vary.<\/p>\n
Installing MySql<\/h2>\n
The OpenStack components use MySQL for storing state information. Start the install script for MySQL by entering the following:<\/p>\n
.\/openstack_mysql.sh<\/span>\r\n\r\nYou\u2019ll be prompted for a password used for each of the components to talk to MySQL:\r\nEnter a password to be used for the OpenStack services\r\nto talk to MySQL (users nova, glance, keystone): redhat\r\nNote(Here \u201credhat\u201d is the password given to nova,glance,keystone) <\/span><\/pre>\n
During the installation process you will be prompted for a root password for MySQL. In our install example we use the same password, \u2018redhat\u2019. At the end of the MySQL install you\u2019ll be prompted for your root password again.<\/p>\n
mysql start\/running, process 8796<\/span>\r\n################################################################################ \r\nCreating OpenStack databases and users. \r\nUse your database password when prompted. <\/span>\r\n Run '.\/openstack_keystone.sh' when the script exits. \r\n###############################################################################<\/span>#\r\nEnter password:<\/span>\r\nAfter MySQL is running, you should be able to login with any of the OpenStack \r\nusers and\/or the root admin account by doing the following:\r\n\r\nmysql -u root -predhat<\/span>\r\nmysql -u nova -predhat nova<\/span>\r\nmysql -u keystone -predhat keystone<\/span>\r\nmysql -u glance -predhat glance<\/span><\/pre>\n
Installing Keystone<\/h2>\n
Keystone is OpenStack\u2019s identity manager. Start the install of Keystone by doing:<\/p>\n
.\/openstack_keystone.sh<\/span><\/pre>\n
You\u2019ll be prompted for a token, the password you entered for OpenStack\u2019s services, and your email address. The email address is used to populate the user\u2019s information in the database.<\/p>\n
Enter a token for the OpenStack services to auth wth keystone: redhattoken \r\nEnter the password you used for the MySQL users (nova, glance, keystone):redhat<\/span> \r\nEnter the email address for accounts(nova,glance,keystone):user@company.com<\/span><\/a><\/span>\r\nYou should be able to query Keystone at this point. \r\nYou\u2019ll need to source the\u201cstackrc\u201d<\/code> file before you talk to Keystone:\r\n . .\/stackrc \u00a0 \r\n keystone user-list<\/span> \u00a0 \u00a0\r\n Keystone should return a list of users:<\/span>\r\n+----------------------------------+---------+------------------------+--------+\r\n|                id                | enabled |         email          |  name  |\r\n+----------------------------------+---------+------------------------+--------+\r\n| b32b9017fb954eeeacb10bebf14aceb3 | True    | user@company.com       | demo   |\r\n| bfcbaa1425ae4cd2b8ff1ddcf95c907a | True    | user@company.com       | glance |\r\n| c1ca1604c38443f2856e3818c4ceb4d4 | True    | user@company.com       | nova   |\r\n| dd183fe2daac436682e0550d3c339dde | True    | user@company.com       | admin  |\r\n+----------------------------------+---------+------------------------+--------+<\/pre>\n
Installing Glance<\/h2>\n
Glance is OpenStack\u2019s image manager. Start the install of Glance by doing:<\/p>\n
.\/openstack_glance.sh<\/span><\/pre>\n
The script will download an Ubuntu 12.04 LTS cloud image from StackGeek\u2019s S3 bucket.Once it\u2019s done, you should be able to get a list of images:<\/p>\n
glance index<\/span><\/pre>\n
Here\u2019s the expected output:<\/p>\n
ID<\/span>              :-<\/span> 71b8b5d5-a972-48b3-b940-98a74b85ed6a<\/span> \r\nName<\/span>            :-<\/span> Ubuntu<\/span> 12<\/span>.04<\/span> LTS<\/span>\r\nDisk<\/span> Format<\/span>     :-<\/span> qcow2<\/span> \r\nContainer<\/span> Format<\/span>:- ovf<\/span> \r\nSize<\/span>            :-<\/span> 226426880<\/span><\/pre>\n
<\/h3>\n
Installing Nova<\/h2>\n
We\u2019re almost done installing! The last component is the most important one as well. Nova is OpenStack\u2019s compute and network manager. It\u2019s responsible for starting instances, creating snapshots and volumes, and managing the network. Start the Nova install by doing:<\/p>\n
.\/openstack_nova.sh<\/span><\/pre>\n
You\u2019ll immediately be prompted for a few items, including your existing network interface\u2019s IP address, the fixed network address, and the floating pool addresses:<\/p>\n
######################################################<\/span>\r\nThe IP address for eth0 is probably 192.168.1.48.\r\nKeep in mind you need an eth1 for this to work.<\/span>\r\n######################################################<\/span>\r\nEnter the primary ethernet interface IP: 192.168.1.48<\/span>\r\nEnter the fixed network (eg. 10.0.2.32\/27): 192.168.1.0\/24<\/span>\r\nEnter the fixed starting IP (eg. 10.0.2.33): 192.168.1.1<\/span>\r\n############################################################################<\/span>\r\nThe floating range can be a subset of your current network. \r\nConfigure your DHCP server<\/span> to block out the range before you choose it here. \r\nAn example would be 10.0.1.224-255<\/span>\r\n############################################################################<\/span>\r\nEnter the floating network (eg. 10.0.1.224\/27): \u00a0\r\nEnter the floating netowrk size (eg. 32):<\/span><\/pre>\n
The fixed network is a set of IP addresses which will be local to the compute nodes. Think of these addresses as being held and routed internally inside any of the compute node instances.<\/p>\n
The floating network is a pool of addresses which can be assigned to the instances you are running. For example, you could start a web server and map an external IP to it for serving a site on the Internet.<\/p>\n
<\/pre>\n
<\/h4>\n
Finish Installing Nova<\/h2>\n
Nova should finish installing after you enter all the network information. When it\u2019s done, you should be able to get a list of images from Glance via Nova:<\/p>\n
 nova image-list<\/span><\/pre>\n
And get the expected output we saw earlier from Glance:<\/p>\n
root@manager-System-Product-Name:\/openstackgeek# nova image-list<\/span>\r\n+--------------------------------------+------------------+--------+--------+\r\n|                  ID                  |       Name       | Status | Server |\r\n+--------------------------------------+------------------+--------+--------+\r\n| 71b8b5d5-a972-48b3-b940-98a74b85ed6a | Ubuntu 12.04 LTS | ACTIVE |        |\r\n+--------------------------------------+------------------+--------+--------+<\/pre>\n
<\/h3>\n
Installing Horizon<\/h2>\n
Horizon is the UI and dashboard controller for OpenStack. Install it by doing:<\/p>\n
.\/openstack_horizon.sh<\/span>\r\n\r\nWhen it\u2019s done installing, you\u2019ll be given a URL to access the dashboard. \r\nYou\u2019ll be able to login with the user \u2018admin\u2019 \r\nand whatever you entered earlier for your password. \r\nIf you\u2019ve forgotten it, simply grep for it in your environment:\r\n\r\nenv |grep OS_PASSWORD<\/span>\r\n\r\nThe URL will be : http:\/\/192.168.1.48<\/span><\/pre>\n
You can login the Openstack dashboard by the following credentials<\/p>\n
USER : admin<\/span><\/p>\n
PASSWORD : redhat<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"
OpenStack : The Mission \u201c To produce the ubiquitous Open Source Cloud Computing platform that will meet the needs of public and private cloud providers regardless of size, by being simple to implement and massively scalable.\u201d OpenStack is a collection of open source software projects that enterprises\/service providers can use to setup and run their […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[3],"tags":[345,328,222,221,329,315,324,127,316,215,260,353,338,210,333,350,143,334,326,327,351,352,325,238,257,318,339,322,116,330,337,320,348,335,321,336,340,331,312,347,349,311,313,341,323,231,332,346,343,199,300,317,314,136,342,213,344,319,204,233],"class_list":["post-1375","post","type-post","status-publish","format-standard","hentry","category-cloud-computing","tag-access-policy-services","tag-access-to-specific-services","tag-amazon-s3","tag-amazon-web-services","tag-api","tag-carpets-curtains","tag-catalog-service","tag-cloud-computing","tag-cloud-computing-services","tag-cloud-infrastructure","tag-company-technology","tag-company-using-product","tag-company-citrix-systems","tag-company-github","tag-company-hyper-v-openstack-storage-infrastructure-swift-swift","tag-company-interface","tag-company-mysql-ab","tag-company-openstack-identity-service-keystone-keystone","tag-company-rackspace","tag-company-vmware-vsphere","tag-computing-fabric-controller","tag-controller","tag-dashboard-controller","tag-dns","tag-dos","tag-ethernet","tag-fail-over-management","tag-flavors-or-instance-virtual-hardware","tag-http","tag-identity-manager","tag-identity-service","tag-image-manager","tag-imaging-service","tag-life-cycle-management","tag-media-streaming","tag-national-aeronautics-and-space-administration","tag-network-manager","tag-nova-nova","tag-object-storage","tag-object-store","tag-open-source-software-projects","tag-openstack","tag-openstack-appliance","tag-openstack-imaging-service","tag-openstack-object-store","tag-person-career","tag-policy-service","tag-security-groups","tag-security-management","tag-server-database-software","tag-software-nec","tag-stackgeek","tag-synnefo","tag-technologyinternet","tag-token-service","tag-ubuntu","tag-usercompany-com","tag-virtual-machine","tag-web-server","tag-web-services"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t