Git clone Gitlab Gitlab-Serverless 🙂
Crowd Source Best DevOps tools diagram
Redhat remediation solution through Ansible Tower play books … dealing mostly with security risk assessment and mitigations (patches and more) https://www.redhat.com/en/about/press-releases/red-hat-delivers-analytics-driven-automation-latest-version-insights-ansible-integration
Ansible Tower 3.1 brings the new “Workflows” feature allowing you to hook Playbooks, set conditions in executing them and passing data from one Playbook to another.
Additionally Tower can now scale beyond a single instance allowing job processing through any one of the tower nodes in the cluster.
In Tower 3.1 you can easily direct all logs to a central log service such as ELK, Splunk, loggly or others.
More information here: https://www.ansible.com/blog/introducing-asible-tower-3-1
What I liked:
- Versions and aliases (prod as an alias can point to the active function)
- Scheduling of actions
- Support for Python and others
- Dynamic – No need to setup servers
- VPC support – can communicate with other services you have internally
- Integration with CloudWatch (inspect and Analyze incoming log entries)
I remember how I felt years ago, when I had the first couple of Linux and Windows Virtual machines running in the lab. It was a great sense of freedom, from hardware limitations, from lost time and productivity. It was real Magic.
Then about 2 years ago, when Docker started its journey, it almost felt like black magic. The speed, the embedded versioning, the Freedom from the Operating system cage…
Looking at the new opportunities and energy at the recent DockerCon EU (2015), feels like a visit to Harry Potter’s Hogwarts castle. Anyway, enough with the story, let’s dig into some tech bits:
- Impressive focus on security, quality,scalability and stability (See the Keynote as well as this session)
- Docker Trusted Registry – Easy signing of your code using UBkey stick (a bit later AWS launched its own Docker registry service..)
- Remote revocation of signed code in case of compromise
- Nautilus- Automatic vulnerability scan of code that is uploaded into Dockerhub
- Internal Dockerhub on premise option including the secure code signing and Nautilus features
- Swarm cluster scales from 10 to 1000 nodes running 50,000 containers without any hiccups!
- Docker Universal Control plane – the dashboard for managing your docker swarm as well as on-the-fly secret data insertion and rotation, On-The-Fly insertion of specific Docker images across Swarm nodes.
- Docker Remote API that allows remote CLI, remote Compose and Docker Swarm
- Docker compose now
- Includes the network overlay system that automatically allows containers to find each other and applications merely call hostnames without worrying about name resolution
- Allows you to assign volumes to specific containers, which allows mixing of both persistent and non-persistent applications
- Started supporting seccomp for more granular Docker permissions as well as user namespaces which allows a process inside a container to “believe” it is running as root, while in fact it’s not
- Docker monitoring resources
- Docker tools
- Docker Bridge: Interlock, Registrator
- Service Registry: etcd, consul, zookeeper
- Template: Interlock, confd, consul-template
- Reverse Proxy: HAProxy, NGINX, Traefik
- Docker sidekicks – special containers that provide Service Discovery, HealthChecks and orchestration through a REST API. Examples include Amazon ECS Agents, AWS Beanstalk, COREOS, Docker Ambassador
- DCOS – The DataCenter Operating System – The Mesosphere Datacenter Operating System (DCOS) is a new kind of operating system that spans all of the machines in your datacenter or cloud. It provides a highly elastic, and highly scalable way of deploying applications, services and big data infrastructure on shared resources including AWS, GCP, Azure.
- Docker for Windows
- Will not run Linux images
- Same code base as Docker for Linux
- Requires Windows Server 2016
- Includes an abstraction layer between Docker and the Windows Kernel
- The Docker C:\Windows maps to \Global?\C:\Windows
- Contains all Windows device entry points including C: and \Registry, \Device\TCP
- Each container has its own “chrooted” devices
- File system is hybrid of UnionFS and NTFS: Virtual Block Device + NTFS partition per container Symlinks to layers on host FS
- Sundial – Rides on top of AWS ECS (Docker on AWS) and offers aggregation of Docker JOBS / ECS into processes with dependency tree graphical representation and central logging and control
- Great sessions you should NOT miss
If you were wondering how exactly does Native Docker for Windows Server look, you would love this Native Docker containers on Windows walk through done by Microsoft Channel9 Visual Studio podcast.
Here is what I loved about it:
- General yet very good explanation of what docker is all about and why should you care
- What does Native Docker for Windows look like (basically the host for containers is based on Windoes Core edition)
- Clarifying the confusion around the mixing of Linux Windows and Docker
- Live Demo of launching Windows Docker containers right from Visual Studio deploying the .NET application you develop and into Azure host
Got any other great Docker resources you want to share?