Kubernetes News, Entwicklungen, Updates, HowTos - Seite 175 von 184

November is packed with plenty of great events including over 75 #Docker Global Mentor Week local events to learn all about Docker! This global event series aims to provide Docker training to both newcomers and intermediate Docker users. More advanced users will have the opportunity to get involved as mentors to further encourage connection and collaboration within the community. Check out the list of confirmed events below to see if there is one happening near you. Make sure to check back as we’ll be updating this list as more events are announced.
Want to help us organize a Mentor Week training in your city? Email us at meetups@docker.com for more information!

From webinars to workshops, meetups to conference talks, check out our list of events that are coming up in November!
Official Docker Training Courses
View the full schedule of instructor led training courses here!
Introduction to Docker:
This is a two-day, on-site or classroom-based training course which introduces you to the Docker platform and takes you through installing, integrating, and running it in your working environment.
Nov 15-16: Introduction to Docker with Amazic – Nieuw-Vennep, The Netherlands
Nov 24-25: Introduction to Docker with Docker Captain Benjamin Wootton &8211; London, United Kingdom

Docker Administration and Operations:
The Docker Administration and Operations course consists of both the Introduction to Docker course, followed by the Advanced Docker Topics course, held over four consecutive days.
Nov 15-18: Docker Administration and Operations with Amazic &8211; Nieuw-Vennep, The Netherlands
Nov 15-18: Docker Administration and Operations with TREEPTIK &8211; Aix en Provence, France
Nov 15-18: Docker Administration and Operations with Vizuri &8211; Washington, D.C.
Nov 21-24: Docker Administration and Operations with Hopla! Software &8211; Lisbon, Portugal
Nov 22-25 11-15: Docker Administration and Operations with TREEPTIK &8211; Paris, France
Nov 29 &8211; Dec 2: Docker Administration and Operations with TEEPTIK &8211; Montreal, Canada

Advanced Docker Operations:
This two day course is designed to help new and experienced systems administrators learn to use Docker to control the Docker daemon, security, Docker Machine, Swarm, and Compose.
Nov 9-10: Advanced Docker Operations with Alter Way &8211; St Cloud, France
Nov 17-18: Advanced Docker Operations with Amazic &8211; Nieuw-Vennep, The Netherlands

Online

Nov 9th: Introduction to InfraKit
While working on Docker for AWS and Azure, we realized the need for a standard way to create and manage infrastructure state that was portable across any type of infrastructure, from different cloud providers to on-prem. One challenge is that each vendor has differentiated IP invested in how they handle certain aspects of their cloud infrastructure. It is not enough to just provision five servers; what IT ops teams need is a simple and consistent way to declare the number of servers, what size they should be, and what sort of base software configuration is required.
Nov 11th: Docker Talk at CheConf16
Che provides a new way to package up a workspace so that it is reproducible and portable. This packaging is possible due to Docker with their descriptive runtimes. This introductory session will introduce you to what Docker is about and how Che uses Docker to represent workspaces, it’s server, it’s launcher, a variety of build utilities. You can even use Docker and Compose to build complex multi machine workspaces.
Nov 16th: Docker Datacenter Demo
In this live presentation you will learn about our Docker Datacenter commercial solution and how it enables enterprise application teams to embrace cloud strategies, application modernization and DevOps. We will then show a live demo of the solution and host a QA session at the end.

Europe

Nov 4th: DOCKER MEETUP AT EYEO GMBH &8211; Koln, Germany
Docker Introduction for Developers.
Nov 7th: DEVOXX BELGIUM &8211; Antwerp, Belgium
Docker is at Devoxx! Join Docker’s Richard Mortier, Justin Cormack & Patrick Chanezon and Docker Captain Phil Estes for the latest Docker updates and deep dives.
Nov 7th: VELOCITY AMSTERDAM &8211; Amsterdam, The Netherlands
Docker&8217;s Amir Chaundhry will discuss unikernels in his Programming IoT talk and Jérôme Petazzoni will deliver a two-day training on Deployment and orchestration at scale with Docker. Docker Captain Adrian Mouat will deliver a tutorial on Docker and Microservices Security.
Nov 9th: DOCKER MEETUP AT DIE ZENTRALE &8211; Frankfurt, Germany
Secrets of Docker Swarm mode.
Nov 14th: GOTO BERLIN &8211; Berlin, Germany
Join Docker Captain Adrian Mouat for Container and Microservices Security.
Nov 15th: CONTAINERCONF 2016 &8211; Mannheim, Germany
Docker Captain Philipp Garbe will cover deploying Docker on AWS and Docker Captain Dieter Reuter will speak about IoT and Docker.
Nov 15th: DEVOPSPRO MOSCOW &8211; Moscow, Russia
Docker Captain Viktor Farcic will be speaking.
Nov 29th: DOCKER MEETUP AT LEINELAB E.V. &8211; Hannover, Germany
Join us for the next Docker Hannover meetup!
Nov 29th &8211; Dec 1st: HPE Discover 2016 London &8211; London, GB
We had a great time at Discover 2016 North America and are returning for a second time to Discover 2016 in London! Check us out for in-depth demos at booth #208.

Asia
Nov 13th: DOCKER ORCHESTRATION SESSION AT BARCAMP SAIGON &8211; Thanh Pho Ho Chi Minh, Vietnam
Come join us for a two hour Docker Orchestration workshop at Barcamp Saigon by Docker Captain and Organizer Vincent De Smet.
Nov 16th: LET’S MEETUP AND VIEW DOCKER IN ACTION! &8211; Colombo, Sri Lanka
A presentation on the Docker basics with a demo by Sanjeewa Alwis from Pearson.

North America
Nov 3rd: CONTAINER DAYS NYC 2016 &8211; New York City, NY
Container Days NYC features Docker Captain Shawn Bower leading an Orchestrating Containers workshop and Docker Captain Francisco Souza delivering Growing Up With Docker: How Docker and Tsuru Have Evolved.
Nov 7th: IMPACT &8211; La Jolla, CA
Mike Coleman from Docker and Docker Captain Kendrick Coleman will be speaking
Nov 9th: DOCKER MEETUP AT LIBERTY MUTUAL &8211; Portland, ME
Docker Container Application Security Deep Dive by Tsvi Korren as well as talks by Ken Cochrane from Docker and Robert Desjarlais.
Nov 10th: DOCKER MEETUP AT RED VENTURES &8211; Charlotte, NC
For this month, we&8217;re hosting AWS Solutions Architect Peter Dalbhanjan to talk about Microservices and ECS!
Nov 28th &8211; Dec 2nd: AWS re:Invent 2016 &8211; Las Vegas, NV
We’re looking forward to another great year at re:Invent in Las Vegas! This time, Docker is outfitted with a larger, custom booth and your chance of scoring even cooler swag. Come see us at #622 inside re:Invent Central.
Nov 29th: NODE.JS INTERACTIVE &8211; AUSTIN, TX
Sophia Parafina from Docker will share how to build and ship apps with Node.js and Docker.
Nov 29th: AMAZON WEB SERVICES &8211; San Mateo, CA
An overview of some of the key concepts inside the service running Docker as the base run time meaning that everything run in EC2 is a Docker image.

South America
GOPHERCON BR &8211; Florianópolis-SC, Brazil
Nov 5th: Docker Captain Marcos Nils will share how to deploy Golang apps with Docker

Oceania
Nov 7th: DOCKER MEETUP AT CATALYST IT &8211; Wellington, New Zealand
We&8217;d like to kick things off again with meetings on the first Monday of every month. Our next scheduled meeting is the 7th of November.
Nov 17th: DOCKER MEETUP AT CCI &8211; Noumea, New Caledonia
Presentation of the Docker Meetup Noumea introduction to Docker by Mathieu Filotto, software architect and trainer and Meetup Organizer of Docker Noumea. Session: Microsoft Windows Server 2016 and Azure &8211; Micro services and Containers by Siddick Elaheebocus, Mauritian origin, consultant and trainer specializing in Microsoft technologies and computer security SPILOG in New Caledonia and French Polynesia.
Nov 24th: DOCKER MEETUP AT CCI &8211; Noumea, New Caledonia
Join our November meetup!

Africa
Nov 2nd: DEVOXX MOROCCO &8211; Casablanca, Morocco
Join Docker Captain Nicolas De loof at Devoxx Morocco to learn about Containers&8217; Jungle. Docker, Rocket, RunC, LXD … WTF? and how to Pimp your CI/CD with Docker-pipeline.
Nov 7th: DEVOPS DAYS CAPE TOWN 2016 &8211; Cape Town, South Africa
Join Docker Captain Tim Haak in Cape Town, South Africa to learnabout Docker 1.12 and The Simplicity of Docker Swarm.

Check out the list of upcoming docker events, meetups and conferences! #learndocker Click To Tweet

The post Your Docker Agenda for November 2016 appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

4. November 20164. November 2016

da Agency

Steve Singh Joins Docker’s Board of Directors

The whole team at Docker would like to welcome Steve Singh, CEO of Concur and Member of SAP’s Executive Board to the Docker family. Steve has accepted a role on Docker’s Board of Directors, bringing his deep experience in building world-class organizations to the Docker board. Steve leads the SAP Business Networks & Applications Group, which brings together teams from Ariba, Fieldglass, Concur, SAP Health, Business Data Network and SMP ERP groups. We had a chance to sit down with Steve to get his thoughts on his appointment to the Docker Board.

How and why did you initially become involved with Docker?
I was certainly aware of Docker. There were also a number of groups across SAP that were using Docker. When a member of the Docker board approached me about joining the company’s Board of Directors, I learned a fair bit more about the market opportunity Docker was pursuing and could easily see the importance of the Docker suite for corporate IT and ISV’s. I was also intrigued by the opportunity to support Ben and Solomon in building an enduring business.

What lead you to Joining the Board?
For me, there are two requirements when considering board roles. The first question I ask – is the company focused on a meaningful problem or opportunity? Docker is focused on giving every developer an opportunity to be independent of the infrastructure that their services are delivered upon. That&8217;s a huge opportunity across corporate IT and every ISV. When you think about how software is becoming the foundation for every industry, you can see the importance of Docker. The second factor is the nature of the founders. It is important to me to work with people with whom I have shared values. I like people that care deeply about their teammates, their community and the legacy that they will leave. Solomon and Ben were down to earth people that had a passion for their company and their team mates. As a founder of a business, I was impressed that Solomon was trying to solve a big problem and wasn’t daunted by obstacles. I was hopeful that as a board member, I could help accelerate the mission that Solomon and Ben were executing against.

As a founder of a high growth start-up yourself and then scaling it; how does that perspective guide how you view your board role?
If I look back at my own experience at Concur, I realized that the early board members were strong financial investors but that they didn’t have a lot of operational experience. I think that the role of the board should be to provide that experience and guidance. Our role is to help the team think through and define their strategy and to help attract, develop and retain incredible leadership talent.

SAP (Ariba), which is part of your business unit, is a Docker customer. Did that play a role in your decision to join the Docker board?
As it turns out, a number of businesses within SAP use Docker and the reviews I received from developers around the company were phenomenal. They loved the Docker product. I couldn’t find one part of the organization that had used Docker and didn’t love it. So while it didn&8217;t factor into my decision to join the board, it was certainly encouraging to see the high regard for Docker.

As a founder that has grown their organization from a startup to a company with several successful business units, are there lessons learned on how to continue and maintain that momentum?
Success is all about people &8211; both the quality of the individuals that are part of the team and perhaps more importantly, the culture that binds those individuals together. As your company gets larger, it is easy to lose your focus. It is easy for the “signal” to degrade from the founder to the newest person joining the team. Certainly part of that signal is the mission of the company, but the most important components of that signal, are the values that define the company and the people that you want at your company. If you can keep that signal strong as you grow, you have every chance to build an incredible company. Not just one that succeeds financially and from a market perspective, but one that is like a second family.

What do you believe is compelling and unique about Docker’s commercial opportunities?
The entire Docker product line has massive opportunity and the open source and the commercial solutions feed into each other. I believe the opportunity is measured in the tens of billions as the demand for Docker among software developers and IT is growing at an unbelievable rate. Docker enables software developers and IT to plug and play into any infrastructure, which gives them control and real economic benefit. In the long term, SAP and other global 2000 companies will have leverage in working with their cloud providers because Docker enables 100 percent portability. This ensures that organizations will be able to seek competitive offerings while avoiding lock-in.

As you look ahead in the next year &8211; what do you see as Docker’s priorities? What are the challenges? What do you see as the board’s challenges?
I see three main priorities for Docker in 2017. Ben and Solomon have to focus on recruiting to develop and bind together a great management team. It is not enough to recruit rock stars – companies need to develop teams that genuinely like working together. The mark of a successful team in one where colleagues form a friendship in a business environment. This reinforces their commitment as they really don’t want to let their peers down. Second, we need to make sure we continue to set the pace for our open source solutions and ensure that our commercial solution, Docker Datacenter (DDC), significantly exceeds customers&8217; expectations. Third, we need to crush our 2017 business metrics, which I believe we can.

Tell us a little bit about yourself – What do you enjoy doing when you are not in your role at Concur or fulfilling your board duties at Concur, CornerStone, OnDemand, etc.
I get a tremendous amount of joy from working with others. Through their own example, my parents taught me that the measure of life is improving the trajectory of humanity &8211; no matter how small or large that improvement is. For me, the best way to accomplish that is to help others. I strive to help my co-workers, friends, community and of course my family. When I am not working – I am with my wife and kids. We have an active family life and my wife and I like to participate in what are children are doing &8211; whether it is with our youngest who is into horseback riding or working with our son, who has started his own company, or visiting our oldest daughter, who is in her final year at college. Family, friends and community &8211; everything else is transient.
The post Steve Singh Joins Docker’s Board of Directors appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

31. Oktober 201631. Oktober 2016

da Agency

Tail Kubernetes with Stern

Editor’s note: today’s post is by Antti Kupila, Software Engineer, at Wercker, about building a tool to tail multiple pods and containers on Kubernetes.We love Kubernetes here at Wercker and build all our infrastructure on top of it. When deploying anything you need to have good visibility to what’s going on and logs are a first view into the inner workings of your application. Good old tail -f has been around for a long time and Kubernetes has this too, built right into kubectl.I should say that tail is by no means the tool to use for debugging issues but instead you should feed the logs into a more persistent place, such as Elasticsearch. However, there’s still a place for tail where you need to quickly debug something or perhaps you don’t have persistent logging set up yet (such as when developing an app in Minikube).Multiple PodsKubernetes has the concept of Replication Controllers which ensure that n pods are running at the same time. This allows rolling updates and redundancy. Considering they’re quite easy to set up there’s really no reason not to do so.However now there are multiple pods running and they all have a unique id. One issue here is that you’ll need to know the exact pod id (kubectl get pods) but that changes every time a pod is created so you’ll need to do this every time. Another consideration is the fact that Kubernetes load balances the traffic so you won’t know at which pod the request ends up at. If you’re tailing pod A but the traffic ends up at pod B you’ll miss what happened.Let’s say we have a pod called service with 3 replicas. Here’s what that would look like:$ kubectl get pods # get pods to find pod ids$ kubectl log -f service-1786497219-2rbt1 # pod 1$ kubectl log -f service-1786497219-8kfbp # pod 2$ kubectl log -f service-1786497219-lttxd # pod 3Multiple containersWe’re heavy users gRPC for internal services and expose the gRPC endpoints over REST using gRPC Gateway. Typically we have server and gateway living as two containers in the same pod (same binary that sets the mode by a cli flag). The gateway talks to the server in the same pod and both ports are exposed to Kubernetes. For internal services we can talk directly to the gRPC endpoint while our website communicates using standard REST to the gateway.This poses a problem though; not only do we now have multiple pods but we also have multiple containers within the pod. When this is the case the built-in logging of kubectl requires you to specify which containers you want logs from.If we have 3 replicas of a pod and 2 containers in the pod you’ll need 6 kubectl log -f <pod id> <container id>. We work with big monitors but this quickly gets out of hand…If our service pod has a server and gateway container we’d be looking at something like this:$ kubectl get pods # get pods to find pod ids$ kubectl describe pod service-1786497219-2rbt1 # get containers in pod$ kubectl log -f service-1786497219-2rbt1 server # pod 1$ kubectl log -f service-1786497219-2rbt1 gateway # pod 1$ kubectl log -f service-1786497219-8kfbp server # pod 2$ kubectl log -f service-1786497219-8kfbp gateway # pod 2$ kubectl log -f service-1786497219-lttxd server # pod 3$ kubectl log -f service-1786497219-lttxd gateway # pod 3SternTo get around this we built Stern. It’s a super simple utility that allows you to specify both the pod id and the container id as regular expressions. Any match will be followed and the output is multiplexed together, prefixed with the pod and container id, and color-coded for human consumption (colors are stripped if piping to a file).Here’s how the service example would look:$ stern serviceThis will match any pod containing the word service and listen to all containers within it. If you only want to see traffic to the server container you could do stern –container server service and it’ll stream the logs of all the server containers from the 3 pods.The output would look something like this:$ stern service+ service-1786497219-2rbt1 › server+ service-1786497219-2rbt1 › gateway+ service-1786497219-8kfbp › server+ service-1786497219-8kfbp › gateway+ service-1786497219-lttxd › server+ service-1786497219-lttxd › gatewayservice-1786497219-8kfbp server Log message from serverservice-1786497219-2rbt1 gateway Log message from gatewayservice-1786497219-8kfbp gateway Log message from gatewayservice-1786497219-lttxd gateway Log message from gatewayservice-1786497219-lttxd server Log message from serverservice-1786497219-2rbt1 server Log message from serverIn addition, if a pod is killed and recreated during a deployment Stern will stop listening to the old pod and automatically hook into the new one. There’s no more need to figure out what the id of that newly created pod is.Configuration optionsStern was deliberately designed to be minimal so there’s not much to it. However, there are still a couple configuration options we can highlight here. They’re very similar to the ones built into kubectl so if you’re familiar with that you should feel right at home.–timestamps adds the timestamp to each line–since shows log entries since a certain time (for instance –since 15min)–kube-config allows you to specify another Kubernetes config. Defaults to ~/.kube/config–namespace allows you to only limit the search to a certain namespaceRun stern –help for all options.ExamplesTail the gateway container running inside of the envvars pod on staging stern –context staging –container gateway envvarsShow auth activity from 15min ago with timestamps stern -t –since 15m authFollow the development of some-new-feature in minikube stern –context minikube some-new-featureView pods from another namespace stern –namespace kube-system kubernetes-dashboardGet SternStern is open source and available on GitHub, we’d love your contributions or ideas. If you don’t want to build from source you can also download a precompiled binary from GitHub releases.
Quelle: kubernetes

31. Oktober 201631. Oktober 2016

da Agency

5 Tales from the Docker Crypt

(Cue the Halloween music)
Welcome to my crypt. This is the #Docker crypt keeper speaking and I’ll be your spirit guide on your journey through the dangerous and frightening world of IT applications. Today you will learn about 5 spooky application stories covering everything from cobweb covered legacy processes to shattered CI/CD pipelines. As these stories unfold, you will hear how Docker helped banish cost, complexity and chaos.
Tale 1 – “Demo Demons”
Splunk was on a mission to enable their employees and partners across the globe to deliver demos of their software regardless of where they’re located in the world, and have each demo function consistently. These business critical demos include everything from Splunk security, to web analytics and IT service intelligence. This vision proved to be quite complex to execute. At times their SEs would be in customer meetings, but their demos would sometimes fail. They needed to ensure that each of their 30 production demos within their Splunk Oxygen demo platform could live forever in eternal greatness.
To ensure their demos were working smoothly with their customers, Splunk uses Docker Datacenter, our on-premises solution that brings container management and deployment services to the enterprise via an integrated platform. Images are stored within the on-premises Docker Trusted Registry and are connected to their Active Directory server so that users have the correct role-based access to the images. These images are publicly accessible to people who are authenticated but are outside of the corporate firewall. Their sales engineers can now pull the images from DTR and give the demo offline ensuring that anyone who goes out and represents the Splunk brand, can demo without demise.
Tale 2 &8211; “Monster Maintenance”
Cornell University’s IT team was spending too many resources taking care of r their installation of Confluence. Their team spent 1,770 hours maintaining applications over a six month period and were in need of utilizing immutable infrastructure that could be easily torn down once processes were complete. Portability across their application lifecycle, which included everything from development, to production, was also a challenge.
With a Docker Datacenter (DDC) commercial subscription from Docker, they now host their Docker images in a central location, allowing multiple organizations to access them securely. Docker Trusted Registry provides high availability via DTR replicas, ensuring that their dockerized apps are continuously available, even if a node fails. With Docker, they experience a 10X reduction in maintenance time. Additionally, he portability of Docker containers helps their workloads move across multiple environments, streamlining their application development, and deployment processes. The team is now able to deploy applications 13X faster than in the past by leveraging reusable architecture patterns and simplified build and deployment processes.
Tale 3 &8211; “Managing Menacing Monoliths and Microservices!”
SA Home Loans, a mortgage firm located in South Africa was experiencing slow application deployment speeds. It took them 2 weeks just to get their newly developed applications over to their testing environment, slowing innovation. These issues extended to production as well. Their main home loan servicing software, a mixture of monolithic Windows services and IIS applications, was complex and difficult to update,placing a strain on the business. Even scarier was that when they deployed new features or fixes, they didn’t have an easy or reliable roll back plan if something went wrong (no blue/green deployment). In addition, their company decided to adopt a microservices architecture. They soon realized that upon completion of this project they’d have over 50 separate services across their Dockerized nodes in production! Orchestration now presented itself as a new challenge.
To solve their issues, SA Home Loans trusts in Docker Datacenter. SA Home Loans can now deploy apps 30 times more often! The solution also provides the production-ready container orchestration solution that they were looking for. Since DDC has embedded swarm within it, it shares the Docker engine APIs, and is one less complex thing to learn. The Docker Datacenter solution provides ease of use and familiar frontend for the ops team.

Tale 4 &8211; “Unearthly Labor”
USDA’s legacy website platform consisted of seven manually managed monolithic application servers that implemented technologies using traditional labor-intensive techniques that required expensive resources. Their systems administrators had to SSH into individual systems deploying updates and configuration one-by-one. USDA discovered that this approach lacked the flexibility and scalability to provide the services necessary for supporting their large number of diverse apps built with PHP, Ruby, and Java – namely Drupal, Jekyll, and Jira. A different approach would be required to fulfill the shared platform goals of USDA.
USDA now uses Docker and has expedited their project and modernized their entire development process. In just 5 weeks. they launched four government websites on their new dockerized platform to production. Later, an additional four websites were launched including one for the first Lady, Michelle Obama, without any additional hardware costs. By using Docker, the USDA saved upwards of $150,000 in technology infrastructure costs alone. Because they could leverage a shared infrastructure model, they were also able to reduce labor costs as well. Using Docker provided the USDA with the agility needed to develop, test, secure, and even deploy modern software in a high-security federal government datacenter environment.
Tale 5 &8211; “An Apparition of CI/CD”
Healthdirect dubbed their original applications development process “anti CI/CD” as it was broken, and difficult to create a secure end-to-end CI/CD pipeline. They had a CI/CD process for the infrastructure team, but were unable to repeat the process across multiple business units. The team wanted repeatability but lacked the ability to deploy their apps and provide 100% hands-off automation. .
Today Healthdirect is using Docker Datacenter. Now their developers are empowered in the release process and the code developed locally ships to production without changes. With Docker, Healthdirect was able to innovate faster and deploy their applications to production, with ease.
So there they are. 5 spooky tales for you on this Halloween day.To learn more about Docker Datacenter check out this demo.
Now, be gone from my crypt. It’s time for me to retire back to my coffin.
Oh and one more thing….Happy Halloween!!
For more resources:

Hear from Docker customers
Learn more about Docker Datacenter
Sign up for your 30 day free evaluation of Docker Datacenter

5 spooky Tales from the Docker Crypt #halloweenClick To Tweet

The post 5 Tales from the Docker Crypt appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

31. Oktober 201631. Oktober 2016

da Agency

Considerations for Running Docker for Windows Server 2016 with Hyper-V VMs

We often get asked at #Docker, “Where should I run my application? On bare metal, virtual or cloud?” The beauty of Docker is that you can run a #container anywhere, so we usually answer this question with “It depends.” Not what you were looking for, right?
To answer this, you first need to consider which infrastructure makes the most sense for your application architecture and business goals. We get this question so often that our technical evangelist, Mike Coleman has written a few blogs to provide some guidance:

To Use Physical Or To Use Virtual: That Is The Container Deployment Question
So, When Do You Use A Container Or VM?

During our recent webinar, titled “Docker for Windows Server 2016”, this question came up a lot, specifically what to consider when deploying a Windows Server 2016 application in a #Hyper-V VM with Docker and how it works. First, you’ll need to understand the differences between Windows Server containers, Hyper-V containers, and Hyper-V VMs before considering how they work together.
A Hyper-V container is a Windows Server container running inside a stripped down Hyper-V VM that is only instantiated for containers.

This provides additional kernel isolation and separation from the host OS that is used by the containerized application. Hyper-V containers automatically create a Hyper-V VM using the application’s base image and the Hyper-V VM includes the required application binaries, libraries inside that Windows container. For more information on Windows Containers read our blog. Whether your application runs as a Windows Server container or as a Hyper-V container is a runtime decision. Additional isolation is a good option for multi tenant environments. No changes are required to the Dockerfile or image, the same image can be run in either mode.
Here we the the top Hyper-V container questions with answers:
Q: I thought that containers do not need a hypervisor?
A: Correct, but since a Hyper-V container packages the same container image with its own dedicated kernel it ensures tighter isolation in multi-tenant environments which may be a business or application requirement for specific Windows Server 2016 applications.
Q: Do you need a hypervisor layer before the OS in both Hyper-V and Docker for Windows Server containers?
A: The hypervisor is optional. With Windows Server containers, isolation is achieved not with hypervisor, but with process isolation, filesystem and registry sandboxing.
Q: Can the Hyper-V containers be managed from the Hyper-V Manager, in the same way that the VM’s are? (ie. turned on/off, check memory usage, etc?)
A: While Hyper-V is the runtime technology powering Hyper-V Isolation, Hyper-V containers are not VMs and neither appear as a Hyper-V resource nor be managed with classic Hyper-V tools, like Hyper-V Manager. Hyper-V containers are only executed at runtime by the Docker Engine.
Q: Can you run Windows Server container and Hyper-V Containers running Linux workloads on the same host?
A: Yes. You can run a Hyper-V VM with a Linux OS on a physical host running Windows Server. Inside the VM, you can run containers built with Linux.

Next week we’ll bring you the next blog in our Windows Server 2016 Q&A Series – Top questions about Docker for SQL Server Express. See you again next week.
For more resources:

Learn more: www.docker.com/microsoft
Read the blog: Webinar Recap: Docker For Windows Server 2016
Learn how to get started with Docker for Windows Server 2016
Read the blog to get started shifting a legacy Windows virtual machine to a Windows Container

Top considerations for running Docker @WindowsServer container in Hyper-VClick To Tweet

The post Considerations for Running Docker for Windows Server 2016 with Hyper-V VMs appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

28. Oktober 201628. Oktober 2016

da Agency

Containerize Windows workloads with Image2Docker

Yesterday, we held a packed webinar on using the Image2Docker tool that prototypes shifting a legacy Windows virtual machine to a Windows Container Dockerfile.
Image2Docker is an open source, community generated powershell module that searches for common components of a Windows Server VM and generates a Dockerfile to match. Originally created by Docker Captain Trevor Sullivan, it is now an open source tool hosted in our GitHub repository. Currently there is discovery of components such IIS, Apache, SQL Server and more. As an input it supports VHD, VHDX, and WIM files. When paired with Microsoft’s Virtual Machine Converter, you can start with pretty much any VM format.
Image2Docker is community supported and designed to show you how easy it is to create Windows Containers from your existing servers. We strongly encourage you to fork it, play with it and contribute pull requests back to the community. Or just install it and use it to generate your own Dockerfiles.
Watch the on-demand webinar to learn more about how to it was built, how to use it and how to contribute.

Here are some of the most popular questions from the sessions with answers.
Is it possible to containerize an application based on an older versions of Windows Server?
Anything you can run on Windows 2016, you can run in Docker, with the exception of anything that requires a GUI. That includes .NET applications, SQL Server, IIS, and all the Windows Server components.
Are there any success stories of people building applications using Docker for Windows Server?
Yes. Tyco has been working with Docker and Windows Server 2016 since Tech Preview and their story is featured here.
Can I run the Windows Server image as a container on a Linux host or any other OS?
For licensing reasons, Windows Server images will currently run on Windows Server 2016 and Windows 10 only.
More Resources:

Check out the Docker and Microsoft partnership
Learn More about Docker for Windows Server
Getting started with Windows Containers Tutorial

The post Containerize Windows workloads with Image2Docker appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

25. Oktober 201625. Oktober 2016

da Agency

How We Architected and Run Kubernetes on OpenStack at Scale at Yahoo! JAPAN

Editor’s note: today’s post is by the Infrastructure Engineering team at Yahoo! JAPAN, talking about how they run OpenStack on Kubernetes. This post has been translated and edited for context with permission — originally published on the Yahoo! JAPAN engineering blog. IntroThis post outlines how Yahoo! JAPAN, with help from Google and Solinea, built an automation tool chain for “one-click” code deployment to Kubernetes running on OpenStack. We’ll also cover the basic security, networking, storage, and performance needs to ensure production readiness. Finally, we will discuss the ecosystem tools used to build the CI/CD pipeline, Kubernetes as a deployment platform on VMs/bare metal, and an overview of Kubernetes architecture to help you architect and deploy your own clusters. PrefaceSince our company started using OpenStack in 2012, our internal environment has changed quickly. Our initial goal of virtualizing hardware was achieved with OpenStack. However, due to the progress of cloud and container technology, we needed the capability to launch services on various platforms. This post will provide our example of taking applications running on OpenStack and porting them to Kubernetes.Coding LifecycleThe goal of this project is to create images for all required platforms from one application code, and deploy those images onto each platform. For example, when code is changed at the code registry, bare metal images, Docker containers and VM images are created by CI (continuous integration) tools, pushed into our image registry, then deployed to each infrastructure platform.We use following products in our CICD pipeline:FunctionProductCode registryGitHub EnterpriseCI toolsJenkinsImage registryArtifactoryBug tracking systemJIRAdeploying Bare metal platformOpenStack Ironicdeploying VM platformOpenStackdeploying container platformKubernetesImage Creation. Each image creation workflow is shown in the next diagram.VM Image Creation:push code to GitHubhook to Jenkins masterLaunch job at Jenkins slave checkout Packer repositoryRun Service JobExecute Packer by build scriptPacker start VM for OpenStack Glance Configure VM and install required applicationscreate snapshot and register to glanceDownload the new created image from GlanceUpload the image to ArtifactoryBare Metal Image Creation:push code to GitHubhook to Jenkins masterLaunch job at Jenkins slave checkout Packer repositoryRun Service JobDownload base bare metal image by build scriptbuild script execute diskimage-builder with Packer to create bare metal imageUpload new created image to GlanceUpload the image to ArtifactoryContainer Image Creation:push code to GitHubhook to Jenkins masterLaunch job at Jenkins slave checkout Dockerfile repositoryRun Service JobDownload base docker image from ArtifactoryIf no docker image found at Artifactory, download from Docker HubExecute docker build and create image Upload the image to ArtifactoryPlatform Architecture.Let’s focus on the container workflow to walk through how we use Kubernetes as a deployment platform. This platform architecture is as below.FunctionProductInfrastructure ServicesOpenStackContainer HostCentOSContainer Cluster ManagerKubernetesContainer NetworkingProject CalicoContainer EngineDockerContainer RegistryArtifactoryService RegistryetcdSource Code ManagementGitHub EnterpriseCI toolJenkinsInfrastructure ProvisioningTerraformLoggingFluentd, Elasticsearch, KibanaMetricsHeapster, Influxdb, GrafanaService MonitoringPrometheusWe use CentOS for Container Host (OpenStack instances) and install Docker, Kubernetes, Calico, etcd and so on. Of course, it is possible to run various container applications on Kubernetes. In fact, we run OpenStack as one of those applications. That’s right, OpenStack on Kubernetes on OpenStack. We currently have more than 30 OpenStack clusters, that quickly become hard to manage and operate. As such, we wanted to create a simple, base OpenStack cluster to provide the basic functionality needed for Kubernetes and make our OpenStack environment easier to manage.Kubernetes ArchitectureLet me explain Kubernetes architecture in some more detail. The architecture diagram is below.ProductDescriptionOpenStack KeystoneKubernetes Authentication and AuthorizationOpenStack CinderExternal volume used from Pod (grouping of multiple containers) kube-apiserverConfigure and validate objects like Pod or Services (definition of access to services in container) through REST API kube-schedulerAllocate Pods to each nodekube-controller-managerExecute Status management, manage replication controllerkubeletRun on each node as agent and manage PodcalicoEnable inter-Pod connection using BGPkube-proxyConfigure iptable NAT tables to configure IP and load balance (ClusterIP)etcdDistribute KVS to store Kubernetes and Calico informationetcd-proxyRun on each node and transfer client request to etcd clustersTenant Isolation To enable multi-tenant usage like OpenStack, we utilize OpenStack Keystone for authentication and authorization.Authentication With a Kubernetes plugin, OpenStack Keystone can be used for Authentication. By Adding authURL of Keystone at startup Kubernetes API server, we can use OpenStack OS_USERNAME and OS_PASSWORD for Authentication. AuthorizationWe currently use the ABAC (Attribute-Based Access Control) mode of Kubernetes Authorization. We worked with a consulting company, Solinea, who helped create a utility to convert OpenStack Keystone user and tenant information to Kubernetes JSON policy file that maps Kubernetes ABAC user and namespace information to OpenStack tenants. We then specify that policy file when launching Kubernetes API Server. This utility also creates namespaces from tenant information. These configurations enable Kubernetes to authenticate with OpenStack Keystone and operate in authorized namespaces. Volumes and Data Persistence Kubernetes provides “Persistent Volumes” subsystem which works as persistent storage for Pods. “Persistent Volumes” is capable to support cloud-provider storage, it is possible to utilize OpenStack cinder-volume by using OpenStack as cloud provider. NetworkingFlannel and various networking exists as networking model for Kubernetes, we used Project Calico for this project. Yahoo! JAPAN recommends to build data center with pure L3 networking like redistribute ARP validation or IP CLOS networking, Project Calico matches this direction. When we apply overlay model like Flannel, we cannot access to Pod IP from outside of Kubernetes clusters. But Project Calico makes it possible. We also use Project Calico for Load Balancing we describe later.In Project Calico, broadcast production IP by BGP working on BIRD containers (OSS routing software) launched on each nodes of Kubernetes. By default, it broadcast in cluster only. By setting peering routers outside of clusters, it makes it possible to access a Pod from outside of the clusters. External Service Load BalancingThere are multiple choices of external service load balancers (access to services from outside of clusters) for Kubernetes such as NodePort, LoadBalancer and Ingress. We could not find solution which exactly matches our requirements. However, we found a solution that almost matches our requirements by broadcasting Cluster IP used for Internal Service Load Balancing (access to services from inside of clusters) with Project Calico BGP which enable External Load Balancing at Layer 4 from outside of clusters.Service Discovery Service Discovery is possible at Kubernetes by using SkyDNS addon. This is provided as cluster internal service, it is accessible in cluster like ClusterIP. By broadcasting ClusterIP by BGP, name resolution works from outside of clusters. By combination of Image creation workflow and Kubernetes, we built the following tool chain which makes it easy from code push to deployment.SummaryIn summary, by combining Image creation workflows and Kubernetes, Yahoo! JAPAN, with help from Google and Solinea, successfully built an automated tool chain which makes it easy to go from code push to deployment, while taking multi-tenancy, authn/authz, storage, networking, service discovery and other necessary factors for production deployment. We hope you found the discussion of ecosystem tools used to build the CI/CD pipeline, Kubernetes as a deployment platform on VMs/bare-metal, and the overview of Kubernetes architecture to help you architect and deploy your own clusters. Thank you to all of the people who helped with this project. –Norifumi Matsuya, Hirotaka Ichikawa, Masaharu Miyamoto and Yuta Kinoshita. This post has been translated and edited for context with permission — originally published on the Yahoo! JAPAN engineer blog where this was one in a series of posts focused on Kubernetes.
Quelle: kubernetes