Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Mastering OpenStack - Episode 04 - Provisioning and Deployment


Published on

A presentation about provisioning and deployment of OpenStack in production that presented in Iran OpenStack users group in 21th July of 2015.

Published in: Technology
  • Be the first to comment

Mastering OpenStack - Episode 04 - Provisioning and Deployment

  1. 1. Presentation By: Roozbeh Shafiee Summer 2015 IRAN OpenStack Users Group MASTERING OPENSTACK (Episode 04) Provisioning and Deployment
  2. 2. IRAN Community| Agenda: ● Automated Deployment ● Automated Configuration ● Disk Partitioning and RAID ● Hardware Requirement For Nodes ● Remote Management ● Iran OpenStack Community OpenStack Provisioning and Deployment
  3. 3. IRAN Community| Automated Deployment OpenStack Provisioning and Deployment
  4. 4. IRAN Community| OpenStack Provisioning and Deployment Automated Deployment: A critical part of a cloud’s scalability is the amount of effort that it takes to run Your cloud. To minimize the operational cost of running your cloud, set up and use an automated deployment and configuration infrastructure with a configuration management system, such as Puppet or Chef. Combined, these systems greatly reduce manual effort and the chance for operator error.
  5. 5. IRAN Community| Manual Tasks Before Automating: ● Physical racking ● MAC-to-IP assignment ● Power configuration OpenStack Provisioning and Deployment
  6. 6. IRAN Community| In Order to Automating: ● PXE boot and TFTP servers for installing OS ● Ubuntu and Red Hat Linux include mechanisms for automating installation ● Preseed and Kickstart automate post install tasks ● Alternatively use own images or image-based approaches ● You can use both approaches with a virtualized infrastructure and physical infrastructure. OpenStack Provisioning and Deployment
  7. 7. IRAN Community| Automated Configuration OpenStack Provisioning and Deployment
  8. 8. IRAN Community| Automated Configuration: ● Automatic configuration management is to establish and maintain the consistency of a system without using human intervention. ● You want to maintain consistency in your deployments so that you can have the same cloud every time, repeatably. ● Proper use of automatic configuration-management tools ensures that components of the cloud systems are in particular states, in addition to simplifying deployment, and configuration change propagation. OpenStack Provisioning and Deployment
  9. 9. IRAN Community| Automation Tools: These tools also make it possible to test and roll back changes, as they are fully repeatable. Conveniently, a large body of work has been done by the OpenStack Community in this space. ● Puppet, a configuration management tool, provides official modules for OpenStack in an OpenStack infrastructure system known as Stackforge. ● PackStack, the command-line utility for Red Hat Enterprise Linux and derivatives that uses Puppet modules to support rapid deployment of OpenStack on existing servers over an SSH connection. ● Chef, Ubuntu Juju, Ansible and Salt OpenStack Provisioning and Deployment
  10. 10. IRAN Community| Disk Partitioning and RAID OpenStack Provisioning and Deployment
  11. 11. IRAN Community| Disk Partitioning and RAID: ● Partitioning, which provides greater flexibility for layout of operating system and swap space ● Adding to a RAID array based on the number of disks you have available ● File system to store files and directories, where all the data lives, including the root partition that starts and runs the system ● Swap space to free up memory for processes, as an independent area of the physical disk used only for swapping and nothing else OpenStack Provisioning and Deployment
  12. 12. IRAN Community| Option 1 for Partitioning and RAID: ● You can assign different partitions to different RAID arrays. ● Allocate partition 1 of disk one and two to the /boot partition mirror. ● Make partition 2 of all disks the root partition mirror. ● Use partition 3 of all disks for a cinder-volumes LVM partition running on a RAID 10 array While you might end up with unused partitions, such as partition 1 in disk three and four of this example, this option allows for maximum utilization of disk space. I/O performance might be an issue as a result of all disks being used for all tasks. OpenStack Provisioning and Deployment
  13. 13. IRAN Community| Option 1 Simple Schema: OpenStack Provisioning and Deployment
  14. 14. IRAN Community| Option 1 Schema: OpenStack Provisioning and Deployment
  15. 15. IRAN Community| Option 2 for Partitioning and RAID: ● Add all raw disks to one large RAID array, either hardware or software based. ● You can partition this large array with the boot, root, swap, and LVM areas. ● This option is simple to implement and uses all partitions. However, disk I/O might suffer. OpenStack Provisioning and Deployment
  16. 16. IRAN Community| Option 2 Schema: OpenStack Provisioning and Deployment
  17. 17. IRAN Community| Option 3 for Partitioning and RAID: ● Dedicate entire disks to certain partitions. You could allocate disk one and two entirely to the boot, root, and swap partitions under a RAID 1 mirror. ● Allocate disk three and four entirely to the LVM partition, also under a RAID 1 mirror for a cinder-volumes ● Disk I/O should be better because I/O is focused on dedicated tasks. However, the LVM partition is much smaller. OpenStack Provisioning and Deployment
  18. 18. IRAN Community| Option 3 Schema: OpenStack Provisioning and Deployment
  19. 19. IRAN Community| Hardware Requirement For Nodes OpenStack Provisioning and Deployment
  20. 20. IRAN Community| Hardware Requirement For Nodes: ● Hardware for controller nodes, used for all stateless OpenStack API services. About 32–64 GB memory, small attached disk, one processor, varied number of cores, such as 6–12. ● Hardware for compute nodes. Typically 256 or 144 GB memory, two processors, 24 cores. 4–6 TB direct attached storage, typically in a RAID 5 configuration. ● Hardware for network nodes. Typically 256 or 144 GB memory, two processors, 12 cores. 2–4 TB direct attached storage, typically in a RAID 5 configuration. ● Hardware for storage nodes. Typically for these, the disk space is optimized for the lowest cost per GB of storage while maintaining rack-space efficiency. OpenStack Provisioning and Deployment
  21. 21. IRAN Community| Remote Management OpenStack Provisioning and Deployment
  22. 22. IRAN Community| Remote Management: ● most operators don’t sit right next to the servers running the cloud, and many don’t necessarily enjoy visiting the data center. ● OpenStack should be entirely remotely configurable, but sometimes not everything goes according to plan. ● having an out-of-band access into nodes running OpenStack components is a boon. ● The IPMI protocol is the de facto standard, and acquiring hardware that supports it is highly recommended to achieve that lights-out data center aim. ● IPMI usually controls the server’s power state, having remote access to the PDU that the server is plugged into can really be useful for situations when everything seems wedged. OpenStack Provisioning and Deployment
  23. 23. IRAN Community| Iran OpenStack Community OpenStack Provisioning and Deployment
  24. 24. IRAN Community| Stay in Touch and Join Us: ● Home Page: ● Meetup Page: ● Mailing List: ● Twitter: @OpenStackIR , #OpenStackIRAN ● IRC Channel on FreeNode#OpenStack-ir OpenStack Provisioning and Deployment
  25. 25. Roozbeh Shafiee Iran OpenStack Community Manager Thank You We need to work together to build a better community