OpenStack with-docker-team-17
Download as PPT, PDF0 likes184 views
The document discusses configuring OpenStack with Docker to deploy a three-tier application, detailing the roles of each tier: presentation, business, and data storage. It highlights Docker's advantages, such as lightweight containers and easy interface communication, making it suitable for deploying the application architecture. Additionally, it explains the use of OpenStack Heat for orchestrating Docker deployments through templates and provides implementation examples.
OpenStack with-docker-team-17
- 1. OpenStack with Docker (Configure OpenStack with docker and deploy a threetier application) Team 17: Ruchir Sharma 201405558 Priyanka Bajaj 201405540 Jaspreet Singh 201202078 Shikher Somal 201201091 Mentored By: Vishrut Mehta
- 2. Docker and OpenStack Container based Virtualisation framework. Free of framework, platform dependencies. An open platform to build, ship and run distributed applications. A cloud operating system that controls large pools of compute, storage, and networking resources throughout a data center.
- 3. Why Docker? ➢ Docker Containers are lightweight and fast. ➢ Global image portability and delivery through Registry. ➢ Completeness of vision (Runtime, Configuration, Build, Deployment, Orchestration). ➢ Dockerfiles provide flexible,repeatable image building ➢ Layered images / builds
- 4. Docker suitability for 3-tier application In a three tier application ➢The user interaction is managed by the presentation tier, which provides an easy to operate front end. ➢The business rules are managed by the business tier, which controls and operates the entire application framework. ➢The underlying data is stored and served by the data storage tier, also known as data persistence. Since, the three tiers are loosely coupled to each other, with predetermined and stable interfaces. This decoupling allows for significant changes to occur within the design, implementation and scale of each tier, without impacting the other tiers.
- 5. Docker suitability for 3-tier application (contd..) ➢ Docker suits this functionality really well, as it provides the containers to remain in isolation from one another, while exposing interfaces so containers can talk to each other. ➢ When the containers are created, the P flag is used to automatically map any network port inside it to a random high port within an ephermal port range on the Docker host. ➢ In case of three tier applications, the web tier can expose itself by allowing clients to send requests to this port. ➢ While, the app tier would be responsible for handling all the logic aspect for this, and thus allow the web tier to talk to the app tier, and the app tier can then further talk to the database tier.
- 6. Example: running a container heat_template_version: 20150430 description: Simple template to deploy a single compute instance resources: my_instance: type: OS::Nova::Server properties: image: FedoraCloudBase2014120321.x86_64 flavor: m1.nano
- 7. Nova Docker Architecture ➢ Docker registry is an image proxy. ➢ Users can upload through docker registry or to glance directly. ➢ Docker pulls images through the docker registry proxy.
- 9. Docker on OpenStack Havana Nova supports Docker as a new hypervisor starting with the Havana release ➢ Deploy containers instead of VM with the same API (Nova)
- 10. What is Heat? ➢ The OpenStack Heat service is used to orchestrate the deployment and management composite infrastructure and application stacks. ➢ The stacks are typically described in YAML documents called Heat Orchestration Templates (HOT). ➢ The power of HOT lies in its ability to describe even complex workload deployments in a fully declarative fashion.
- 11. Docker plugin for Heat By using the plugin, Heat can talk directly to Docker
- 12. Heat Workflow
- 13. Why using Heat directly? ➢ Heat as a standalone project for orchestration ➢ It allows to use the whole Docker API from a Heat template
- 14. How to use it? 1. Install Heat with DevStack: https://wiki.openstack. org/wiki/Heat/GettingStartedUsingDevstack 2. Install the Docker plugin
- 15. Creating a HOT file 1. Heat template specifies resources 2. Each resource is part of container 3. Specify the image of the container 4. Specify the environment variables that it may need
- 16. Sample HOT Templates – Nova Server ● This template deploys a sing compute Node on Fedora Image using Nova
- 17. HOT Template – Three Tier Application ● Database tier – MYSQL ● Webapp server – Apache2 ● Frontend Server - PHP
- 18. Database Resource ● Database resource as a mysqldb Docker exposed at port 8888
- 19. Wordpress Resource ● Wordpress Resource as a Docker using Database Resource at same port
- 20. Screenshots – Fedora Console in Openstack
- 22. Thank You !