Dockerzing Your Infrastructure with Machinery | LinuxCon 2016
Download as ODP, PDF0 likes228 views
The document discusses the process of containerizing infrastructure using Docker, with insights on how to identify workloads and build orchestration templates for applications like MariaDB. It also provides contact information for further inquiries and mentions the proprietary nature of the content, emphasizing that it is confidential and intended for SUSE employees only. Additionally, it includes disclaimers about the document's content and the absence of commitments to deliver or market any product.
Dockerzing Your Infrastructure with Machinery | LinuxCon 2016
- 1. Dockerizing Your Infrastructure with Machinery How I Learned to Stop Worrying and Love the Container Mauro Morales Machinist mamorales@suse.com
- 2. 3 Background Data Center Image by Wikieditor243
- 4. 5 Docker
- 5. 6 But How Do We Get to This? Container Ship Image by Ana Ulin
- 6. 7 Containerize a Rails App
- 7. Demo
- 8. 13 Workload Identification if system.runs_service?("mysql") identify "mariadb", "db" parameter "user", "dbuser" parameter "password", SecureRandom.base64 end
- 9. 14 Orchestration Template mariadb: build: ./mariadb volumes: - ./mariadb/data:/var/lib/mysql environment: DB_USER: :user DB_PASS: :password
- 10. 15 Summary
- 11. 16 Machinery
- 12. 17
- 13. 18 Where to Go From Here? • Workloads • Templates • Orchestration
- 14. Questions?
- 15. 20 Get In Touch! • machinery@lists.suse.com • github.com/SUSE/machinery/issues • @_mauromorales • mamorales@suse.com
- 16. Thank you. 21 Join us at machinery-project.org
- 17. 22
- 18. Corporate Headquarters Maxfeldstrasse 5 90409 Nuremberg Germany +49 911 740 53 0 (Worldwide) www.suse.com Join us on: www.opensuse.org 23
- 19. Unpublished Work of SUSE LLC. All Rights Reserved. This work is an unpublished work and contains confidential, proprietary and trade secret information of SUSE LLC. Access to this work is restricted to SUSE employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of SUSE. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability. General Disclaimer This document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. SUSE makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for SUSE products remains at the sole discretion of SUSE. Further, SUSE reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All SUSE marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.
Editor's Notes
- #4: Sysadmin complicated life - many different kinds of apps - many different ways to deploy - critical decisions early on. Mention DATA CENTER - deeper
- #5: Docker promises application will run the same way everywhere (physical, virtual, cloud, openstack, raspberry pi) Support DevOps approach Reproducibility Single purpose containers Lightweight Start/stop time Lots of containers Build --- run --- deploy!!!! Container tech … what is it????? Processes isolated kernel features Runtime … runc stuff … look for terms More than the runtime
- #6: Build --- run --- deploy!!!! Container tech … what is it????? Processes isolated kernel features Runtime … runc stuff … look for terms More than the runtime Show dockerfile to explain
- #7: Separate applications into more easy to manage services Easy way to get started You don't want to start from scratch, you already have a datacenter
- #8: 3 tier web app More explicit: This is how we imagine 4 steps … 1,23,4 are what is happening and this is what I'll show you Using Portus as an example it is a webfront for the registry it's not required to the containerization but it's part of the example
- #9: Mentions this is step 1, 2, 3, 4
- #16: we are providing templates, which we recommend, best practices as we know them dynamic fill it with data, more powerfull than tutorials
- #17: CLI app for creating descriptions insight into existing systems, to store and track their state create new systems based on existing ones comparisons between systems. export descriptions to other tools for installation, migration, image building, containerization, or cloud deployment defined interfaces to work with system descriptions from your custom tools. Modular SHOW JSON
- #18: 1 click installs Easy get started guides for debian, rhel, centos, fedora Opensouce ruby
- #19: Really running in production Node balancers Kubernetes