It has been a week from hell and it is only Thursday afternoon. Allow me to elaborate. On a previous post, I mentioned the events regarding a water leak in my office. That occurred last Monday and Tuesday. At this point I only have to call to return a fan and ask for reimbursement on four books that got damaged by water.
On Wednesday I stopped by the car dealer to get an oil service for my vehicle. It has a lithe over 4,000 miles. I do not drive too much since I work from home. On my way back on 494 E I exited on the ramp to get to 77S (Cedar Avenue). As I merged into Cedar I started accelerating and moving to the center lane (Cedar at that point has three lanes plus a fourth one to enter and exit). As I was reaching the bridge for Old Shakopee Road, my two right tires popped as I hit a set of potholes covered in water. It was raining and quite foggy. After stopping on the bridge over the Minnesota River, I decided drive to a nearby gas station to see if I could put some air in my tires. Lucky I have run flat tires, otherwise I would have had to call a tow. When I tried putting air, I noticed that both tires had openings of about 5 to 6 inches. The only solution was to get them replaced. After talking with my son, he suggested the closest shop which would offer a rental while they replaced the tires. Shortly before 05:00 PM I received a call that the vehicle was ready and headed out to pick it up.
A couple weeks ago, when my wife and I returned from a trip, she started feeling some health issues. On Tuesday we stopped to see a specialist in Ramsey County hospital. Today she underwent three tests. Hope the results become available tomorrow and they find the cause of the issue and are able to specify a treatment.
OK, enough chit chat, let’s get on with the topic of this post. I have signed for a series of six webinars on Docker by Docker. This post has my notes. If you are a user or plan to port your software to microservices and Docker, this series is for you. You can learn more about and register here. What is nice is that in 48 hours after each webinar you receive a MP file with the presentation. I just finished watching the video.
The full name for the webinar: Introduction to Containers, Container Orchestrators and the Docker Enterprise Container Platform
By Oliver Pomeroy, Technical Solutions Engineer
More applications and more components per applications
Deploy applications on multiple platforms.
Standardize on devices.
Deploying a Docker is standard. It does not care what is running in it.
Package, deploy, and manage it the same way in a Docker container.
Docker abstracts the software away from the infrastructure.
@04:37 <== approximate time in the video for the slide with the following notes
VMs vs. Containers
They are different, not mutually exclusive.
Docker does not package the OS.
Light weight package.
Multiple containers on the same hardware are supported.
@07:50 <== approximate time in the video for the slide with the following notes
o Reduce server footprint
o Reduce Operating System License Spend
o Reduce OS patching time
o Drive up server utilization
o Reduce time to patch applications
o Reduce time to deploy applications
o Integrate into CI/CD Pipelines
o Standardization across Applications
@12:25 <== approximate time in the video for the slide with the following notes
Common use cases for Docker
o Modernize Existing or Traditional Applications (“MTA”) (legacy software on modern software)
o Cloud Strategies (avoid lock-in)
o Reduce Data Center Expenses (more applications per host)
o Faster Application Development and Delivery (microservices)
o Modernize Software Supply Chain
o Deploying Software at the Edge
@18:50 <== approximate time in the video for the slide with the following notes
Any app, any OS, any infrastructure
Agility (quick and easy)
The Docker engine is just used to start and stop containers (does not add latency).
The hypervisor is in the path between the OS and the physical server (adds latency).
Defines a container
@25:48 <== approximate time in the video for the slide with the following notes
Linux containers run on a Linux host
Windows containers run on a Windows host
@33:11 <== approximate time in the video for the slide with the following notes
Scheduling (reschedules failed containers)
Resource Management (CPU, memory)
e.g., Swarm Mode, Kubernetes
@36:16 <== approximate time in the video for the slide with the following notes
Container as a Service
Management Layer & Container Registry
@37:51 <== approximate time in the video for the slide with the following notes
Docker Universal Control Plane
Cluster manager that delivers functionalities for production with containers
o Supports / manages Kubernetes and Swarm orchestrators
o Easy installation & setup
o Web console to manage containers operations
o CLI and API support
o Multi tenancy up to physical isolation
o Secure access control with LDAP/AD support and granular custom RBAC
o Content security policy & enforcement
o Integration with Data Center operations
@38:27 <== approximate time in the video for the slide with the following notes
Docker Trusted Registry
Private container images catalogs with advanced architecture and security
o Point and click UI to manage repos, images, and team colaboration
o Image management with labels, tag store and garbage collection
o HA and redundant architecture
o Content security with built in image signing and verification
o Wide variety of storage driver support for image store
o Automated Images Promotions & Immutable Repositories
o Vulnerability Scanning for Docker Images
@39:09 <== approximate time in the video for the slide with the following notes
Universal Control Plane | Docker Trusted Registry
Swarm Mode | Kubernetes
Docker Engine Enterprise
Linux | Windows
Physical or virtual … on premise or or off premises .. x86
@40:05 <== approximate time in the video for the slide with the following notes
3 Core Pillars of Docker Enterprise
o Any application, new apps or legacy apps
o Any infrastructure, on prem, on cloud, on the edge
o Avoiding Lock in
o Industry standard runtime and imahe
o Built into every layer of the container stack
o Integrated into your software supply chain
o Image chain of custody
o Fine-grained access control and governance
o Reducing time taken to release and patch
o Integrate into existing tool chains and pipelines
o Reduce overhead on infrastructure and operations
o Accelerate the migration to containers
@42:17 <== approximate time in the video for the slide with the following notes
:::: :::: ::::
:::: :::: ::::
Kubernetes support not available on Windows yet.
I strongly recommend this series for managers and engineers that are thinking about microservices as a way to drastically improve the time to develop and maintain software and the reduction in time and associated deployment costs. In my humble opinion, going to microservices is the future for all software applications.
If you have comments or questions regarding this or any other post in this blog, or if you need some help on any step of a software development project, please do not hesitate and leave me a message below. Messages do not become available I explicitly do so.
Keep on learning, experimenting and developing great software products and services;
Follow me on Twitter: @john_canessa