Dynamic Resource Allocation and Management Using OpenStack

Dynamic Resource Allocation and Management Using OpenStack Rakesh Kumar 1, Bhanu Bhushan Parashar 2 1 Red Hat Certified Engineer 2 Assistant Professor & JECRC University, Jaipur, India 1 rakeshkumar.it14@jecrc.ac.in, 2 Er.bhanubhushanparashar@gmail.com Abstract OpenStack is a set of software tools for building as well as managing cloud computing platforms for public and private clouds, it has a strong ecosystem and controls large pools of compute, storage, and networking resources throughout a datacenter, managed through a dashboard (Horizon). This paper include the introduction to OpenStack, its background with all release history and components of OpenStack. Further this paper contains OpenStack architecture as well as Conceptual Diagram and at last covering Introduction to Juno which is latest OpenStack release and introduce what new features added in OpenStack Juno. The aim of this paper is to show importance of OpenStack framework that enables efficient as well as dynamic management of virtualization, storage and networking of all resources with great flexibility and ease. Index Terms - Cloud Computing, OpenStack, IaaS, Icehouse, Juno, Kilo, Trove, Ironic, Zaqar and Sahara I. INTRODUCTION Cloud computing revolution continues to change the way organizations view their IT resources. OpenStack provides a common, open source platform that can be used by corporations, researchers, service providers as well as anyone else that wants to deploy a cloud. OpenStack lets users deploy virtual machines (VMs) and it makes horizontal scaling easy. OpenStack is an open source software, which means that anyone who chooses to can access source code, make any changes they need, and freely share these changes back out to the community at large. Important solution for OpenStack brings our proven cluster management software to OpenStack world making it easy to deploy a complete cloud over bare metal and also manage it effectively. II. OPENSTACK OpenStack is mainly a set of software tools for building as well as managing cloud computing platforms for public and private clouds. OpenStack cloud operating system turns all sets of hypervisors within a data centre or across multiple data centres into pools of resources, and these pools of resources can be consumed as well as managed from a single place which is dashboard. Administrators and users can go to its dashboard to perform their tasks in easy and fast manner, and one can create virtual machines (VMs), configure networks and manage volumes all from a single place. OpenStack is a free as well as open-source software cloud computing software platform, and OpenStack.org release it under the terms of Apache License. OpenStack community collaborates around 6 month, time-based release cycle with frequent development milestones. III. HISTORY Rackspace Hosting and NASA jointly launched an open source cloud software initiative known as OpenStack, In July 2010. The community's first official release, Austin, appeared four months later, with plans to release regular updates of software every few months. In, developers of Ubuntu Linux distribution adopted OpenStack with an unsupported technology preview of OpenStack Bexar release for Ubuntu 11.04 Natty Narwhal, and Ubuntu's sponsor Canonical then introduced full support for OpenStack clouds, starting with OpenStack's Cactus release. OpenStack also became available in Debian Sid from OpenStack Cactus release in, as well as first release of Debian including OpenStack was Debian 7.0 (Wheezy), including OpenStack 2012.1 (Essex). In 2012, Red Hat announced a preview of their OpenStack distribution, beginning with the Essex release, and also Red Hat introduced commercial support for OpenStack with Grizzly release, in April 2013. HP announced HP Helion as well as released a preview of HP Helion OpenStack Community, beginning with Icehouse release in April 2014. S. No. 1 2 3 4 Release Date 21 October 2010 3 February 15 April 22 September IV. RELEASE HISTORY Release Name Austin Bexar Cactus Diablo 5 5 April 2012 Essex 6 27 September 2012 Folsom Included Component code names Nova, Swift Horizon, Keystone Quantum, Cinder

7 4 April 2013 Grizzly 8 9 10 17 October 2013 17 April 2014 16 October 2014 Havana Icehous e Juno 11 April 2015 Kilo Quantum, Cinder Ceilometer Ceilometer, Trove Ceilometer, Trove Ceilometer, Trove, Ironic, Zaqar, Sahara powerful functionality for backing up data stored on block storage volumes, and Snapshots can be restored as well as used to create a new block storage volume. The flexible architecture provides creating as well as managing block storage devices very easily. D. OpenStack Networking (Neutron) OpenStack Networking ( Neutron, formerly Quantum) is a scalable, pluggable and API-driven system for managing networks and IP addresses. It provides an extension framework which can deploy as well as manage additional network services like intrusion detection systems (IDS), load balancing, firewalls, and virtual private networks (VPN). OpenStack networking (Neutron) is also useful for VLAN management, IP addresses management to different VMs and firewalls management. E. OpenStack Dashboard (Horizon) Horizon is the dashboard behind OpenStack, and also graphical interface to OpenStack. OpenStack Dashboard (Horizon) provides administrators as well as users a graphical interface to access, provision, and automate cloudbased resources. Table 1 Release History of OpenStack IV. COMPONENTS OF OPENSTACK OpenStack has a modular architecture and various code names for its components. There are many components of OpenStack such as: A. OpenStack Compute (Nova) OpenStack Compute (Nova) is a cloud computing fabric controller, that is main part of an IaaS system, and it allows user to create as well as manage virtual servers using machine images. OpenStack compute is the brain of Cloud and it provisions and manages large networks of virtual machines (VMs). B. OpenStack Object Storage (Swift) OpenStack Object Storage (Swift) is a scalable redundant storage system, and also it is a storage system for objects and files, as well as objects and files are written to multiple disk drives spread throughout servers in the data center, with OpenStack software responsible for ensuring data replication and integrity across cluster. Swift stores as well as retrieves unstructured data objects through HTTP based APIs, and it is also fault tolerant due to its data replication and scale out architecture. C. OpenStack Block Storage (Cinder) Cinder is a mainly block storage component, that is more analogous to traditional notion of a computer being able to access specific locations on a disk drive. This component provides persistent block level storage devices for use with OpenStack compute instances. Block storage system manages creation, attaching as well as detaching of block devices to servers. Snapshot management provides F. OpenStack Identity (Keystone) Keystone mainly provides identity services for OpenStack, and also provides multiple means of access, meaning developers can easily map their existing user access methods against Keystone. OpenStack Identity (Keystone) acts as a common authentication system across the cloud operating system and can integrate with existing backend directory services like LDAP, as well as supports multiple forms of authentication like standard username and password credentials, token-based systems and AWS-style logins. G. OpenStack Image Service (Glance) Glance provides image services to OpenStack, and it provides discovery, registration, and delivery services for disk as well as server images. Glance can used to store and catalog an unlimited number of backups, and it is only module which can add, delete, share, or duplicate images, as well as stores and retrieves the virtual machine disk image. H. OpenStack Telemetry (Ceilometer) OpenStack Telemetry Service (Ceilometer) mainly provides telemetry services that allow cloud to provide billing services to individual users of the cloud, as well as it monitors usage of the Cloud services and decides the billing accordingly. OpenStack Telemetry is used to decide the scalability as well as obtain the statistics regarding the usage. I. Orchestration (Heat) Heat allows developers to store requirements of a cloud application in a file which defines what resources are necessary for that application. Orchestration manages multiple Cloud applications through an OpenStack-native REST API and a CloudFormation-compatible Query API.

J. Database as a Service (Trove) Trove is a database-as-a-service provisioning relational as well as non-relational database engines. Cloud users, database administrators can provision as well as manage multiple database instances as needed. K. Bare Metal Provisioning (Ironic) Ironic is an incubated OpenStack project which aims to provision bare metal machines instead of virtual machines (VMs). Ironic was initially forked from the Nova Bare metal driver as well as has evolved into a separate program. Ironic can be extended with vendor-specific plugins to implement additional functionality. L. Multiple Tenant Cloud Messaging (Zaqar) Zaqar is mainly a multi-tenant cloud messaging service for Web developers. Cloud operators can leverage Zaqar to support same of SQS and SNS to their customers, as well as Zaqar was formerly known as Marconi. M. Elastic Map Reduce (Sahara) Sahara provide users with simple means to provision Hadoop clusters by specifying several parameters such as Hadoop version, cluster topology, nodes hardware details and more. Sahara provides means to scale already provisioned cluster by adding and removing worker nodes on demand, as well as after a user fills all parameters, Sahara easily deploys the cluster in a few minutes. N. Messaging as a Service (Marconi) Marconi is mainly a cloud messaging as well as notification service for developers building applications on top of OpenStack. The service features a web-friendly HTTP API that developers can use to send messages between the different components of their SaaS as well as mobile applications, using a variety of communication patterns. V. OPENSTACK ARCHITECTURE OpenStack project is designed to deliver a massively scalable cloud operating system. OpenStack is architected to provide flexibility as you design your cloud, and no proprietary hardware or software requirements as well as ability to integrate with legacy systems and also third party technologies. OpenStack supports ARM and alternative hardware architectures, as well as KVM and XenServer are popular choices for hypervisor technology. Fig 1 Conceptual Diagram VI. NEW CAPABILITIES IN OPENSTACK JUNO OpenStack is on an approximately 6 month release cycle, and each release given a code name starting with consecutive letters of the alphabet. On 16 October, OpenStack Juno will be released, with many new projects, as well as lots of new features. Here we are discussing few new features that are added in OpenStack Juno release. A. Nova Nova which is Core of OpenStack, needs to be solid, but this does not mean that it is slow to change, but few significant changes coming in OpenStack Juno release. 1) NFV: Network Functions Virtualization (NFV) defines the replacement of usually standalone appliances used for low as well as high level network functions, like firewalls, network address translation, caching, gateways, intrusion detection, accelerators, etc. into virtual instance or set of virtual instances, which are known as Virtual Network Functions (VNF). Main consume rs of NFV are Service providers that are looking to accelerate the deployment of new network services, as well as to do that, need to eliminate the constraint of slow renewal cycle of hardware appliances, that do not auto scale as well as limit their innovation. NFV provide best possible infrastructure for such workloads to be deployed in, while respecting design principles of an Infrastructure as a Service (IaaS) cloud. 2) Scheduler: In the Icehouse release we wanted to split the scheduler out into a new project that code name Gantt. Requires decoupling Nova s scheduler from the rest of Nova, so decoupling effort is the main goal for the Juno release cycle. 3) Upgrades: An Icehouse release of OpenStack was the first release which supported live upgrades in some form. Nova which is core component of OpenStack that is a highly

distributed system, as well as one of the biggest requirements for doing this is versioning everything about the interactions between components, and versioning of the data provided by Nova Objects. OpenStack Juno release cycle supports that how reduce the downtime needed on the control plane by reducing how long it takes for database schema migrations to run. In Icehouse release added some normal testing of the live upgrade scenario to OpenStack CI system. This testing runs OpenStack using the previous release and then upgrades everything except the nova-compute service. At that point, everything should continue to work. Main goal of OpenStack Juno release is to improve this testing to verify that we can run an older instance of the nova network service with an upgraded control plane. 4) Ironic: Nova component introduced bare metal driver in the Grizzly release, and bare metal driver allows you to use Nova s API to do provisioning of bare metal instead of virtual machines (VMs). Start a new project dedicated to bare metal management, and that project name is Ironic. 5) Docker: Docker driver for Nova was moved to Stackforge during OpenStack Icehouse development cycle, and reason was lack of CI running for the driver. In Juno release, Docker supports pause as well as unpause, that is a feature of the Nova API which Docker driver is now able to support and Cinder support. There has been ongoing work to get CI with tempest running, and it s running in OpenStack CI infrastructure. 6) Database Integration: OpenStack projects have begun using Alembic for managing database schema migrations. Michael Bayer, author of SQLAlchemy as well as Alembic, recently joined Red Hat to help with OpenStack, and continue to maintain SQLAlchemy and Alembic. B. Ceilometer Ceilometer is the measurement component of OpenStack. 1) Speed: The Ceilometer team have identified some poorly designed parts of the project, so you can look for Ceilometer to be much more efficient, as well as faster, in Juno release. 2) Community Reboot: Project management is moving from a top down decision making process to a collaborative community decision making process, as well as some controls are being put in place regarding code freeze at end of the cycle, so that people aren't trying to rush new functionality in at the last minute, and resulting in testing gaps. C. Heat Heat is orchestration component of OpenStack that can be used to set up as well as tear down infrastructure automatically in response to environmental events. 1) Rollback: If Heat deploy failed, then you just moved on, as well as maybe went back and cleaned up by hand, in past, but in Juno, it will be easier to roll back a filed deployment, as well as be sure that all of different pieces have been cleaned up. 2) Create Resources without Being Admin: In earlier or Icehouse release, certain types of resources could only be created by admin, but In Juno release, creating users will still require that you be admin, but you can then delegate privileges to that user so that you can create resources without having to be admin power. D. Glance Glance is an important service where users can upload as well as discover data assets that are meant to be used with other services, such as images for Nova and templates for Heat. 1) Artifacts: Scope is expanding in Juno release to be more than just an image registry, and to being a generic catalog of different data assets, that will allow for flexibility in how it can be easily used. E. Marconi Marconi is OpenStack messaging as well as queuing system, so it is important to all of the other components. 1) Redis: In Juno release, Marconi will add a storage driver to support redis, as well as support for storage engines is in the works, and it will be possible to create and tag clusters of storage. 2) Queues migration: The Marconi team will be adding support for queues migration between pools of the same type in OpenStack Juno release. F. Keystone Keystone is basically an identity management piece of OpenStack, as well as has some big improvements coming in Juno release. 1) LDAP Integration: In OpenStack Juno release, you can easily configure Keystone to use multiple identity backends, as well as integration with LDAP will be much easier. 2) Other security projects: Same community works on Keystone that is very interested in security related projects in OpenStack ecosystem, and projects Barbican and Kite to be active in the few months. G. TripleO TripleO is an important project about installing, upgrading, and also operating OpenStack clouds in an automated fashion, and in Juno release making OpenStack easier to deploy and manage. High availability, a big push in

Juno is deploying HA clouds with TripleO, as well as Heat templates TripleO uses Heat as part of the automation of deployment, so in Juno release a lot of work has gone into Heat templates. H. Horizon Horizon is a component that is web admin interface for OpenStack. 1) Sahara (Hadoop) : Sahara is a new and important project that makes it easier to deploy Apache Hadoop on OpenStack and this project is integrated into the dashboard, so you can easily deploy Hadoop clusters with a few mouse clicks. 2) JavaScript Unbundling: Horizon has moved to unbundling the JavaScript libraries which were previously copied into Horizon source tree. It easier to manage upgrades, and complies with no bundling requirements in certain Linux distros like Fedora. 3) RBAC: Horizon-2014.1 aka Icehouse version has support for RBAC for Glance as well as Cinder. Create, delete or access images can be limited on user or role basis, but in Juno release RBAC system was extended to support network, compute and orchestration. Service Cloud Computing Platform IJAETMAS, Vol.1, Issue.2, July- 2014, pg. 111-116; ISSN: 2349-3224. [3] Rakesh Kumar, Neha Gupta, Shilpi Charu, Sunil Kumar Jangir Manage Big Data through NewSQL ; National Conference on Innovation in Wireless Communication and Networking Technology - 2014; Association with THE INSTITUTION OF ENGINEERS(INDIA); Organised by: Regional College for Education Research & Technology. [4] Rakesh Kumar, Neha Gupta, Shilpi Charu, Sunil Kumar Jangir Architectural Paradigms of Big Data ; National Conference on Innovation in Wireless Communication and Networking Technology - 2014; Association with THE INSTITUTION OF ENGINEERS(INDIA); Organised by: Regional College for Education Research & Technology. [5] Rakesh Kumar, Neha Gupta, Hitesh Maharwal, Shilpi Charu, Kusum Yadav Critical Analysis of Database Management Using NewSQL ; IJCSMC, Vol.3 Issue.5, May- 2014, pg. 434-438; ISSN 2320 088X. [6] Rakesh Kumar, Neha Gupta, Shilpi Charu, Somya Bansal, Kusum Yadav Comparison of SQL with HiveQL ; International Journal for Research in Technological Studies, Vol. 1, Issue 9, August 2014; ISSN (online): 2348-1439; pg. 28-30. [7] Rakesh Kumar, Yougeshwary Sharma, Sonu Agarwal, Pragya, Bhanu Bhushan Parashar Extremely effective CRM Solution Using Salesforce ; JETIR, Volume 1, Issue 5, October 2014, pg. 278-282; ISSN: 2349-5162. [8] OpenSource URL: http://opensource.com/ [9] OpenStack URL: http://www.openstack.org/ [10] Get Cloudify URL: http://getcloudify.org/ VII. CONCLUSIONS Cloud computing is an evolving technology that providing IT infrastructure. OpenStack is an open source software that is used for designed to allow researchers as well as administrators to deploy infrastructure as a service (IaaS) and provide tools for managing, creating virtual machines (VMs) on top of existing resources. Further research is going on related to most efficient easy solution of security issues as well as increase the performances in dynamic reconfiguration in an Infrastructure as a Service Cloud Computing. ACKNOWLEDGMENT This paper work was supported by JECRC Foundation, Jaipur, India. We are thankful to Mr. Arpit Agarwal (Director of JECRC Foundation, Jaipur, India) for valuable suggestions, motivation, support and encouragement. Further, we wish to thank to Dr. Prof. K. K. Agrawal (Prof. of JECRC Foundation, Jaipur, India) and all Faculty Member of JECRC Foundation, Jaipur, India for their time to time suggestions, guidelines, relevant data and technical support. REFERENCES [1] Rakesh Kumar, Neha Gupta, Shilpi Charu, Kanishk Jain, Sunil Kumar Jangir Open Source Solution for Cloud Computing Platform Using OpenStack ; IJCSMC, Vol. 3, Issue. 5, May 2014, pg.89 98; ISSN 2320 088X. [2] Rakesh Kumar, Kanishk Jain, Hitesh Maharwal, Neha Jain, Anjali Dadhich Apache CloudStack: Open Source Infrastructure as a