da Agency

What’s new in Kubernetes 1.6 — a focus on stability

The post What’s new in Kubernetes 1.6 — a focus on stability appeared first on Mirantis | Pure Play Open Cloud.
Kubernetes 1.6 is forecast to be released this week. Major themes include new capabilities for Daemon Sets, the beta release of Kubernetes federation and new scheduling features, and new networking capabilities. You can get an in-depth look at all of the new features in the Kubernetes 1.6 release notes, but let&8217;s get a quick overview here.
DaemonSet rolling updates
You&8217;re probably used to dealing with Kubernetes in terms of creating a Deployment or a ReplicationController and having it manage your pods, making certain that you always have a particular number of instances spread among the nodes that are available.  DaemonSets, on the other hand, look at things from the opposite perspective.
With DaemonSets, you specify the nodes to run a particular set of containers, and Kubernetes will make certain that any nodes that satisfy those requirements will run those pods. With Kubernetes 1.6, you now have the option to update those DaemonSets with a new image or other information.  (For more information on DaemonSets, you can see this article,which explains how and why to use them.)
Kubernetes Federation
As Kubernetes takes hold, the likelihood of running into situations in which users have multiple large clusters to deal with increases. Federation enables you to create an infrastructure in which users can use, say, the closest cluster to them, or the one that has the most spare capacity.
Now in beta, kubefed “supports hosting federation on on-prem clusters, [and] automatically configures kube-dns in joining clusters and allows passing arguments to federation components.”
Authentication and access control improvements
Role-Based Access Control (RBAC), which makes it possible to define roles for control plane, node, and controller components, is now in the beta phase.  (It also defines default roles for these components.) There are numerous changes from the alpha version (such as a change from using * for all users to using system:authenticated or system:unauthenticated) so make sure to check out the release notes for all the details.
Attribute-Based Access Control (ABAC) also been tweaked, with wild cards defaulting to authenticated users. The kube-apiserver and the authentication API have also seen a number of improvements.
Scheduling changes
Now in beta is the ability to have multiple schedulers, with each controlling a different set of pods. You can also set the scheduler you want for a particular pod on the pod sec, rather than as an annotation, as in the alpha version.
Also in beta are node and pod affinity/anti-affinity. This capability enables you to intelligently schedule pods that should, or shouldn&8217;t be, on the same piece of hardware.  For example, if you have a web application that talks to a database, you might wat them on the same pod.  If, on the other hand, you have a pod that needs to be highly available, you might want to spread different instances over different nodes as a safeguard against failure. You can specify the affinity field on the PodSpec.
Kubernetes 1.6 also includes the beta release of taints and tolerations, and some improvements to that functionality from the alpha version.  Taints enable you to dedicate a node to a particular kind of pod, similar to the way in which you might flavors in OpenStack. Unlike OpenStack, however, you can tell Kubernetes to try to avoid scheduling pods that aren&8217;t explicitly allowed (read: tolerated) to that node, but if it has no choice, it can go ahead. This functionality also enables to you specify a period of time a mod might run on this node before being &8220;evicted.&8221;
And speaking of being evicted, Kubernetes 1.6 now enables you to override the default 5 minute period during which a pod remains bound to a node if there are problems,s o you can specify that a pod either finds another node more quickly, or is more patient and waits even longer.
The Container Runtime Interface is now the default
While it&8217;s natural to assume that containers running on Kubernetes are Docker containers, that&8217;s not always true.  Kubernetes also supports rkt containers, and in fact the goal is to enable Kubernetes to orchestrate any container runtime. Up until now, that&8217;s been difficult, because the container runtimes were coded into the kubelet component that runs the actual containers.
Now, with Kubernetes 1.6, the beta version of the Docker Container Runtime Interface is enabled by default &8212; you can turn it off with –enable-cri=false &8212; it will be easier to add new runtimes.  The old non-runtime architecture is deprecated in 1.6 and is scheduled for remove in Kubernetes 1.7.
Storage improvements
Kubernetes 1.6 includes the general availability release of StorageClasses, which enable you to specify a particular type of storage resource for users without exposing them to the details.  (This is also similar to flavors in OpenStack.)
Also now in GA are the ability to populate environment variables from a configmap or a secret, as well as support for writing and running your own dynamic PersistentVolume provisioners.
Note that StorageClasses will change the behaviors of PersistentVolumeClaim objects on existing clouds, so be sure to read the Release Notes.
Networking improvements
You now have added control over DNS; Kubernetes 1.6 enables you to set stubDomains, which define the nameservers used for specific domains (such as *.mycompany.local), and to specify what upstreamNameservers you want to use, overriding resolve.conf.
Digging deeper, the Container Network Interface (CNI) is now integrated with the Container Runtime Interface (CRI) by default, and the standard bridge plugin has been validated with the combination.
Other changes
Kubernetes 1.6 includes a huge number of changes and improvements, some of which will only be of interest to operators, as opposed to end users, but all of which are important. Some of these changes include:

By default, etcd v3 is enabled, enabling clusters up to 5000 nodes
The ability to know via the API whether a Deployment is blocked
Easier logging access
Improvements to the Horizontal Pod Autoscaler
The ability to add third party resources and extension API servers with the edit command
New commands for creating roles, as well as determining whether you can perform an action
New fields added to describe output
Improvements to kubeadm

Definitely take a look at the full release notes to get the details.
The post What&8217;s new in Kubernetes 1.6 &8212; a focus on stability appeared first on Mirantis | Pure Play Open Cloud.
Quelle: Mirantis

da Agency

Solutions Delivery Executive- UK

The post Solutions Delivery Executive- UK appeared first on Mirantis | Pure Play Open Cloud.
Mirantis, Inc. is looking for an experienced Solutions Delivery Executive to help lead our clients on their journey to the cloud. This highly-visible, senior leadership role within the Mirantis Services organization is a functional peer to the Enterprise Sales executives aligned to our most strategic global accounts.Your top-level responsibilities will include: overall ownership of the end-to-end service delivery experience, building & executing multi-year client account plans, establishing/maintaining corporate governance, driving cross-functional collaboration & communications with client executives and business stakeholders, and ensuring operational excellence & successful business outcomes for the clientCandidates considered for this role must have a good mix of strong operational & business skills combined with strategic thought-leadership and a mind for tactical execution. Acting as a liaison between the client and Mirantis worldwide, you should be a strong advocate for the client, but with the goals of sound business judgments and mutual assured success for both parties.Primary ResponsibilitiesLead the global service delivery experience; single point of ownership and accountability for all client service delivery related activitiesBuilding and maintaining trusted advisor relationships with influential client decision-makers for the successful adoption and deployment of cloud services and technologiesWork in collaboration with the client Sales team to create and execute multi-year business plans to accelerate the adoption of cloud across the client’s business units, exceed revenue goals, and driving client referrals and referencesManage client level P&L – drive revenue recognition, achieve and/or exceed quarterly PS revenue, cost, utilization & profitability objectivesEnsure client-specific operational, change management and compliance practices are implemented and adhered-to; continually seek to improve processes, reduce complexity and drive predictability for clientsAct as escalation lead for all service delivery-related issues that could impact client relationshipParticipate in contract and financial negotiations (MSAs, SOWs, ELAs, T&Cs)Qualifications10+ years experience in infrastructure/cloud solutions Services company,ideally as an executive within a large Enterprise IT organization, consulting firm or global systems integration companyBachelor’s degree (Business, Science, Technology, Engineering, Math) or equivalent experienceAnalytical decision-making and detail-oriented thinking combined with strong management skillsDemonstrated experience managing large, cross-functional teams within matrix organizationsSuperior interpersonal, written, verbal, listening and presentation skills &8211; ability to communicate cross-functionally with most senior-level executivesHighly organized, able to track multiple concurrent tasks and activities simultaneously; first-hand Change Management and Business Process Mapping experienceHistory of leading successful business transformations using cloud & related technologiesIn-depth knowledge of OpenStack or similar cloud technologies (AWS, Azure, CloudStack)Ability to travel freely between client sites and Mirantis HQ as neededWhat We OfferPartner with exceptionally passionate, talented and engaging colleagues.Implement cloud solutions for some of the best known brands in the industry for use in mission critical applications.High-energy atmosphere of a young company, competitive compensation package with strong benefits plan and stock options.Environment that fosters creativity and personal growth.The post Solutions Delivery Executive- UK appeared first on Mirantis | Pure Play Open Cloud.
Quelle: Mirantis

da Agency

How Watson helps H&R Block deliver engaging customer experiences

Just under three-fourths of US citizens get tax refunds every year, according to H&R Block CEO Bill Cobb. For H&R Block customers, the number is higher; it’s closer to 85 percent.
Now that IBM Watson is helping H&R Block tax professionals guide customers through the filing process, the company is aiming to make that number rise even further.
Cobb joined IBM CEO Ginni Rometty on stage at IBM InterConnect Tuesday to explain just how H&R Block teamed up with IBM to get Watson working on taxes and how the whole process works.
“I think this is one of the best examples of two brands coming together where they worked seamlessly,” Cobb said after showing the ad that aired during this year&8217;s big game. Rometty added that H&R Block is &8220;a wonderful exemplar of continuous transformation.&8221;
Cobb shared that, after the 2016 tax season, H&R Block research found that customers were looking for more engaging experiences. So he called IBM on his landline phone and asked how Watson could make that happen while still keeping tax professionals at the center of customer relationships. In June 2016, teams from both companies were working on a solution. Just eight months later, ads for the service were running on TV.
&8220;Anyone who says IBM doesn&8217;t work quickly, I&8217;m here to tell you, IBM works fast,&8221; Cobb said.
The cognitive interview
Here&8217;s how the process works: a customer walks into an H&R Block office and sits down in front of a screen–where previously they usually just watched a tax professional type away. A tax professional begins the usual interview, asking about life events, potential deductions and possible credits.
Throughout that process, Watson is listening in, referencing 600 million data points and the entire US tax code, creating a &8220;knowledge graph,&8221; which outlines all the areas where there might be a savings.
After the interview, Watson displays a massive chart of all the possible deductions and credits, and the tax professional goes through that chart with the customer, explaining all the different ways to increase the refund.
Positive response
Even before H&R Block with Watson was branded, when it was just a pilot program, customer satisfaction was ticking up, Cobb said. Now it&8217;s rising even more.
Tax professionals are responding positively, too, he said.
&8220;This makes them feel like they&8217;re really on the cutting edge,&8221; Cobb said.
Cobb said Watson is &8220;a beautiful fit for the nature of our business&8221; and is likely to expand into other areas of H&R Block&8217;s services, such as digital tax preparation.
Learn more about Watson on IBM Cloud.
The post How Watson helps H&R Block deliver engaging customer experiences appeared first on #Cloud computing news.
Quelle: Thoughts on Cloud

da Agency

Open Technology Summit focuses on contributors

The Open Technology Summit, now in its fifth year, has become an annual state of the union for the established and budding open source projects that IBM supports.
The conclusion drawn at Sunday’s OTS during IBM InterConnect in Las Vegas is that the state of open tech is strong and getting stronger.
The event brought together leaders from some of today’s top open source #cloud projects: #OpenStack, Cloud Foundry, the Linux Foundation, JS Foundation and the Apache Software Foundation, plus the IBM leaders that support these projects.
“The open source community is only as good as the people who are contributing,” Willie Tejada, IBM Chief Developer Advocate, told the capacity crowd.

“We’ve been systematically building an open innovation platform — cloud, #cognitive, etc.” @angelluisdiaz https://t.co/HHMqWmi3v4 #ibmots pic.twitter.com/945FkRbkZg
— IBM Cloud (@#IBMcloud) March 20, 2017

Judging by the success stories shared on stage, contributor quality appears to be quite high. In short, the open source community is thriving.
Finding success in the open
The Linux Foundation has become one of the great success stories in open source, thanks largely to the huge number of contributors it has attracted. In his talk, the organization’s executive director, Jim Zemlin, told the crowd that across its various projects, contributors add a staggering 10,800 lines of code, remove 5,300 lines of code and modify 1,875 lines of code per day.
Zemlin called open source “the new norm” for software and application development.

&8220;Open source is now the new norm for software development.” – @jzemlin IBMOTS #ibminterconnect https://t.co/y3V3IGfcTK pic.twitter.com/83k9yLdJdf
— IBM Cloud (@IBMcloud) March 20, 2017

Cloud Foundry Foundation executive director Abby Kearns stressed her organization’s commitment to bringing forward greater diversity among its community.
“When I think about innovation, I think about diversity,” said Kearns, who took over as executive director four months ago. “We have the potential to change our industry, our countries and the world.”
Like Cloud Foundry, the OpenStack community has seen tremendous growth in its user community thanks to increased integration and cooperation with other open source communities. OpenStack Foundation executive director Jonathan Bryce and Lauren Sell, vice president of marketing and community services, shared their community’s pithy, tongue-in-cheek motto:

&8220;In 2014, there was 323 developers contributing to OpenStack. In 2016, we had 531.&8221; @jbryce IBMOTS ibminterconnect pic.twitter.com/6PxYzrVxsL
— IBM WebSphere (@IBMWebSphere) March 20, 2017

The community, which aims to create a single platform for bare metal servers, virtual machines and containers, has seen 5 million cores deployed on it. Contributors have jumped from 323 in 2014 to 531 in 2016.
Sell echoed several of the other speakers, when she noted that we’re living in a “multi-cloud world,” and that open technologies are enabling it.
IBM: Contributors, collaborators, solution providers
While it’s well known that IBM has helped start and lead many of the open source communities that it supports, the company also offers a robust set of unique capabilities around these technologies. The company is constantly working to expand its offerings around open technologies.
For example, IBM Cloud Platform Vice President and CTO Jason McGee previewed the announcement that Kubernetes is now available on IBM Bluemix Container Service.
“This service lets us bring together the power of that project and all of the amazing technology in the engine with Docker and the orchestration layer with Kubernetes and combine it with the power of cloud-based delivery,” McGee said.
David Kenny, senior vice president, IBM Watson and Cloud Platform, also spoke about “the power of the community to move the technology faster and to consume it and learn from it.”
“We’re very much committed as IBM to be participants,” he said. “Certainly IBM Cloud and IBM Watson are two pretty big initiatives at IBM these days, and both of those have come together around the belief that open source is a key part of our platform.”

“IBMCloud and Watson have come together around the belief that #opensource is a key part of our platform.” &8211; @davidwkenny IBMOTS pic.twitter.com/gU9DCzMsoC
— Kevin J. Allen (@KevJosephAllen) March 20, 2017

Moving forward as a community
Looking toward the future of open tech, it was clear that its success will depend on the next generation of contributors.
Tejada went so far as to call the open source movement a religion. “The most important piece is to understand the core premises of the religion.” He identified those as:

Embrace the new face of development
Acknowledge and adapt to the new methodologies of application development
Seize the opportunity to do more with less at an accelerated rate

For more on IBM work in open technology, visit developerWorks Open.
The post Open Technology Summit focuses on contributors appeared first on #Cloud computing news.
Quelle: Thoughts on Cloud

da Agency

OpenStack Developer Mailing List Digest March 11-17

SuccessBot Says

Dims [1]: Nova now has a python35 based CI job in check queue running Tempest tests (everything running on py35)
jaypipes [2]: Finally got a good functional test created that stresses the Ironic and Nova integration and migration from Newton to Ocata.
Lbragstad [3]: the #OpenStack-Ansible project has a test environment that automates rolling upgrade performance testing
annegentle [4]: Craig Sterrett and the App Dev Enablement WG: New links to more content for the appdev docs [5]
jlvillal [6]: Ironic team completed the multi-node grenade CI job
Tell us yours via OpenStack IRC channels with message “#success <message>”

All: [7]

Pike Release Management Communication

The release liaison is responsible for:

Coordinating with the release management team.
Validating your team release team requests.
Ensure release cycle deadlines are met.
It&#8217;s encouraged to nominate a release liaison. Otherwise this tasks falls back to the PTL.

Ensure the releaase liaison has time and ability to handle the communication necessary.

Failing to follow through on a needed process step may block you from meeting deadlines or releasing as our milestones are date-based, not feature-based.

Three primary communication tools:

Email for announcements and asynchronous communication

“[release]” topic tag on the openstack-dev mailing list.
This includes the weekly release countdown emails with details on focus, tasks, and upcoming dates.

IRC for time sensitive interactions

With more than 50 teams, the release team relies on your presence in the freenode openstack-release channel.

Written documentation for relatively stable information

The release team has published the schedule for the Pike cycle [8]
You can add the schedule to your own calendar [9]

Things to do right now:

Update your release liaisons [10].
Make sure your IRC and email address listed in projects.yaml [11].

Update your mail filters to look for “[release]” in the subject line.
Full thread [12]

OpenStack Summit Boston Schedule Now Live!

Main conference schedule [13]
Register now [14]
Hotel discount rates for attendees [15]
Stackcity party [16]
Take the certified OpenStack Administrator exam [17]
City guide of restaurants and must see sites [18]
Full thread [19]

Some Information About the Forum at the Summit in Boston

“Forum” proper

3 medium sized fishbowl rooms for cross-community discussions.
Selected and scheduled by a committee formed of TC and UC members, facilitated by the Foundation staff members.
Brainstorming for topics [20]

“On-boarding” rooms

Two rooms setup classroom style for projects teams and workgroups who want to on-board new team members.
Examples include providing introduction to your codebase for prospective new contributors.
These should not be tradiitonal “project intro” talks.

Free hacking/meetup spaces

Four to five rooms populated with roundtables for ad-hoc discussions and hacking.

Full thread [21]

 
The Future of the App Catalog

Created early 2015 as a market place of pre-packaged applications [22] that you can deploy using Murano.
This has grown to 45 Glance images, 13 Heat templates and 6 Tosca templates. Otherwise did not pick up a lot of steam.
~30% are just thin wrappers around Docker containers.
Traffic stats show 100 visits per week, 75% of which only read the index page.
In parallel, Docker developed a pretty successful containerized application marketplace (Docker Hub) with hundreds or thousands regularly updated apps.

Keeping the catalog around makes us look like we are unsuccessfully trying to compete with that ecosystem, while OpenStack is in fact complimentary.

In the past, we have retired projects that were dead upstream.

The app catalog is however has an active maintenance team.
If we retire the app catalog, it would not be a reflection on that team performance, but that the beta was arguably not successful in build an active market place and a great fit from a strategy perspective.

Two approaches for users today to deploy docker apps in OpenStack:

Container-native approach using “docker run” after using Nova or K8s cluster using Magnum.
OpenStack Native approach “zun create nginx”.

Full thread [23][24]

ZooKeeper vs etcd for Tooz/DLM

Devstack defaults to ZooKeeper and is opinionated about it.
Lots of container related projects are using etcd [25], so do we need to avoid both ZooKeeper and etcd?
For things like databases and message queues, it&8217;s more than time for us to contract on one solution.

For DLMs ZooKeepers gives us mature/ featureful angle. Etcd covers the Kubernetes cooperation / non-java angle.

OpenStack interacts with DLM&8217;s via the library Tooz. Tooz today only supports etcd v2, but v3 is planned which would support GRPC.
The OpenStack gate will begin to default to etcd with Tooz.
Full thread [26]

Small Steps for Go

An etherpad [27] has been started to begin tackling the new language requirements [28] for Go.
An golang-commons repository exists [29]
Gopher cloud versus having a golang-client project is being discussed in the etherpad. Regardless we need support for os-client-config.
Full thread [30]

POST /api-wg/news

Guidelines under review:

Add API capabilities discovery guideline [31]
Refactor and re-validate API change guidelines [32]
Microversions: add next_min_version field in version body [33]
WIP: microversion architecture archival doc [34]

Full thread [35]

Proposal to Rename Castellan to oslo.keymanager

Castellan is a python abstraction to different keymanager solutions such as Barbican. Implementations like Vault could be supported, but currently is not.
The rename would emphasize the Castellan is an abstraction layer.

Similar to oslo.db supporting MySQL and PostgreSQL.

Instead of oslo.keymanager, it can be rolled into the oslo umbrella without a rename. Tooz sets the precedent of this.
Full thread [36]

Release Countdown for week R-23 and R-22

Focus:

Specification approval and implementation for priority features for this cycle.

Actions:

Teams should research how they can meet the Pike release goals [37][38].
Teams that want to change their release model should do so before end of Pike-1 [39].

Upcoming Deadlines and Dates

Boston Forum topic formal submission period: March 20 &#8211; April 2
Pike-1 milestone: April 13 (R-20 week)
Forum at OpenStack Summit in Boston: May 8-11

Full thread [40]

Deployment Working Group

Mission: To collaborate on best practices for deploying and configuring OpenStack in production environments.
Examples:

OpenStack Ansible and Puppet OpenStack have been collaborating on Continuous Integration scenarios but also on Nova upgrades orchestration
TripleO and Kolla share the same tool for container builds.
TripleO and Fuel share the same Puppet OpenStack modules.
OpenStack and Kubernetes are interested in collaborating on configuration management.
Most of tools want to collect OpenStack parameters for configuration management in a common fashion.

Wiki [41] has been started to document how the group will work together. Also an etherpad [42] for brainstorming.

 
Quelle: openstack.org

da Agency

Learn Docker with our DockerCon 2017 Hands-On Labs

We’re excited to announce that #DockerCon 2017 will feature a comprehensive set of hands-on labs. We first introduced hands-on labs at DockerCon EU in 2015, and they were also part of DockerCon 2016 last year in Seattle. This year we’re offering a broader range of topics that cover the interests of both developers and operations personnel on both Windows and Linux (see below for a full list)
These hands-on labs are designed to be self-paced, and are run on the attendee’s laptop. But, don’t worry, all the infrastructure will be hosted again this year on Microsoft Azure. So, all you will need is a laptop capable of instantiating a remote session over SSH (for Linux) or RDP (for Windows).

We’ll have a nice space set up in between the ecosystem expo and breakout rooms for you to work on the labs. There will be tables and stools along with power and wireless Internet access as well as lab proctors to answer questions. But, because of the way the labs are set up, you could also stop by, sign up, and take your laptop to a quiet spot and work on your own.
As you can tell, we’re pretty stoked on the labs, and we think you will be to.
See you in Austin!
DockerCon 2017 Hands-on Labs

Title

Abstract

#Docker Orchestration

In this lab you can play around with the container orchestration features of Docker. You will deploy a Dockerized application to a single host and test the application. You will then configure Docker Swarm Mode and deploy the same application across multiple hosts. You will then see how to scale the application and move the workload across different hosts easily.

Docker Networking

In this lab you will learn about key Docker Networking concepts. You will get your hands dirty by going through examples of a few basic concepts, learn about Bridge and Overlay networking, and finally learning about the Swarm Routing Mesh.

Modernize .NET Apps &#8211; for Devs.

A developer’s guide to app migration, showing how the Docker platform lets you update a monolithic application without doing a full rebuild. You’ll start with a sample app and see how to break components out into separate units, plumbing the units together with the Docker platform and the tried-and-trusted applications available on Docker Hub.

Modernize .NET Apps &8211; for Ops.

An admin guide to migrating .NET apps to Docker images, showing how the build, ship, run workflow makes application maintenance fast and risk-free. You’ll start by migrating a sample app to Docker, and then learn how to upgrade the application, patch the Windows version the app uses, and patch the Windows version on the host &8211; all with zero downtime.

Getting Started with Docker on Windows Server 2016

Get started with Docker on Windows, and learn why the world is moving to containers. You’ll start by exploring the Windows Docker images from Microsoft, then you’ll run some simple applications, and learn how to scale apps across multiple servers running Docker in swarm mode

Building a CI / CD Pipeline in Docker Cloud

In this lab you will construct a CI / CD pipeline using Docker Cloud. You&#8217;ll connect your GitHub account to Docker Cloud, and set up triggers so that when a change is pushed to GitHub, a new version of your Docker container is built.

Discovering and Deploying Certified Content with Docker Store

In this lab you will learn how to locate certified containers and plugins on docker store. You&8217;ll then deploy both a certified Docker image, as well as a certified Docker plugin.

Deploying Applications with Docker EE (Docker DataCenter)

In this lab you will deploy an application that takes advantage of some of the latest features of Docker EE (Docker Datacenter). The tutorial will lead you through building a compose file that can deploy a full application on UCP in one click. Capabilities that you will use in this application deployment include:

Docker services
Application scaling and failure mitigation
Layer 7 load balancing
Overlay networking
Application secrets
Application health checks
RBAC-based control and visibility with teams

Vulnerability Detection and Remediation with Docker EE (Docker Datacenter)

Application vulnerabilities are a continuous threat and must be continuously managed. In this tutorial we will show you how Docker Trusted Registry (DTR) can detect known vulnerabilities through image security scanning. You will detect a vulnerability in a running app, patch the app, and then apply a rolling update to gradually deploy the update across your cluster without causing any application downtime.

 
Learn More about DockerCon:

What’s new at DockerCon?
5 reasons to attend DockerCon
Convince your manager to send you to DockerCon
DockerCon for Windows containers practitioners 

Check out all the Docker Hands-on labs at DockerCon #learndockerClick To Tweet

The post Learn Docker with our DockerCon 2017 Hands-On Labs appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

da Agency

Learn Docker with our DockerCon 2017 Hands-On Labs

We’re excited to announce that #DockerCon 2017 will feature a comprehensive set of hands-on labs. We first introduced hands-on labs at DockerCon EU in 2015, and they were also part of DockerCon 2016 last year in Seattle. This year we’re offering a broader range of topics that cover the interests of both developers and operations personnel on both Windows and Linux (see below for a full list)
These hands-on labs are designed to be self-paced, and are run on the attendee’s laptop. But, don’t worry, all the infrastructure will be hosted again this year on Microsoft Azure. So, all you will need is a laptop capable of instantiating a remote session over SSH (for Linux) or RDP (for Windows).

We’ll have a nice space set up in between the ecosystem expo and breakout rooms for you to work on the labs. There will be tables and stools along with power and wireless Internet access as well as lab proctors to answer questions. But, because of the way the labs are set up, you could also stop by, sign up, and take your laptop to a quiet spot and work on your own.
As you can tell, we’re pretty stoked on the labs, and we think you will be to.
See you in Austin!
DockerCon 2017 Hands-on Labs

Title

Abstract

#Docker Orchestration

In this lab you can play around with the container orchestration features of Docker. You will deploy a Dockerized application to a single host and test the application. You will then configure Docker Swarm Mode and deploy the same application across multiple hosts. You will then see how to scale the application and move the workload across different hosts easily.

Docker Networking

In this lab you will learn about key Docker Networking concepts. You will get your hands dirty by going through examples of a few basic concepts, learn about Bridge and Overlay networking, and finally learning about the Swarm Routing Mesh.

Modernize .NET Apps &#8211; for Devs.

A developer’s guide to app migration, showing how the Docker platform lets you update a monolithic application without doing a full rebuild. You’ll start with a sample app and see how to break components out into separate units, plumbing the units together with the Docker platform and the tried-and-trusted applications available on Docker Hub.

Modernize .NET Apps &8211; for Ops.

An admin guide to migrating .NET apps to Docker images, showing how the build, ship, run workflow makes application maintenance fast and risk-free. You’ll start by migrating a sample app to Docker, and then learn how to upgrade the application, patch the Windows version the app uses, and patch the Windows version on the host &8211; all with zero downtime.

Getting Started with Docker on Windows Server 2016

Get started with Docker on Windows, and learn why the world is moving to containers. You’ll start by exploring the Windows Docker images from Microsoft, then you’ll run some simple applications, and learn how to scale apps across multiple servers running Docker in swarm mode

Building a CI / CD Pipeline in Docker Cloud

In this lab you will construct a CI / CD pipeline using Docker Cloud. You&#8217;ll connect your GitHub account to Docker Cloud, and set up triggers so that when a change is pushed to GitHub, a new version of your Docker container is built.

Discovering and Deploying Certified Content with Docker Store

In this lab you will learn how to locate certified containers and plugins on docker store. You&8217;ll then deploy both a certified Docker image, as well as a certified Docker plugin.

Deploying Applications with Docker EE (Docker DataCenter)

In this lab you will deploy an application that takes advantage of some of the latest features of Docker EE (Docker Datacenter). The tutorial will lead you through building a compose file that can deploy a full application on UCP in one click. Capabilities that you will use in this application deployment include:
&8211; Docker services
&8211; Application scaling and failure mitigation
&8211; Layer 7 load balancing
&8211; Overlay networking
&8211; Application secrets
&8211; Application health checks
&8211; RBAC-based control and visibility with teams

Vulnerability Detection and Remediation with Docker EE (Docker Datacenter)

Application vulnerabilities are a continuous threat and must be continuously managed. In this tutorial we will show you how DTR can detect known vulnerabilities through image security scanning. You will detect a vulnerability in a running app, patch the app, and then apply a rolling update to gradually deploy the update across your cluster without causing any application downtime.

 
Learn More about DockerCon:

What’s new at DockerCon?
5 reasons to attend DockerCon
Convince your manager to send you to DockerCon
DockerCon for Windows containers practitioners 

Check out all the Docker Hands-on labs at DockerCon #learndockerClick To Tweet

The post Learn Docker with our DockerCon 2017 Hands-On Labs appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

da Agency

Docker Turns 4: Thank you Docker Community!

In case you missed it, this week we’re celebrating #Docker’s 4th Birthday with meetups all over the world (check out #dockerbday on twitter). This feels like the right time to look back at the past 4 years and reflect on what makes the Docker Community so unique and vibrant: people, values, mentorship and learning opportunities. You can read our own Jérôme Petazzoni’s blog post for a more technical retrospective.
Managing an open source project at that scale and preserving a healthy community doesn’t come without challenges. Last year, Arnaud Porterie wrote a very interesting 3-part series blog post on open source at Docker covering the different challenges associated with the People, the Process and the Tooling and Automation. The most important aspect of all being the people.
Respect, fairness and openness are essential values required to create a welcoming environment for professionals and hobbyists alike. In that spirit, we’ve launched a scholarship program and partnerships in an attempt to improve opportunities for underrepresented groups in the tech industry while helping the Docker Community become more diverse. If you’re interested in this topic, we’re fortunate enough to have Austin area high school student Kate Hirschfeld presenting at DockerCon on Diversity in the face of adversity.
But what really makes the Docker community so special is all of the passionate contributors who work tremendously hard to submit pull requests, file GitHub issues, organize meetups, give talks at conferences, write blog posts or record Docker tips videos.
Leadership, mentorship, contribution and collaboration play a massive role in the development of the Docker Community and container ecosystem. Through the organization of the Docker Mentor Week last year or a Docker Mentor Summit at DockerCon 2017, we’re always trying to emulate the community and encourage more advanced users to share their knowledge with newcomers.
A great example of leadership and mentorship in the Docker Community is Docker Captain Alex Ellis. We could not write a blog post on #PiDay without mentioning Alex and the awesome work he does around Docker and Raspberry Pi. In addition to sharing his knowledge through blog posts and videos, Alex is actively inspiring and mentoring younger folks such as Finnian Anderson. Alex’s support and advocacy got Finnian invited to DockerCon 2017 to give a demo of a Raspberry Pi-driven hardware gauge to monitor a Docker Swarm in real time.

If you’re pumped about all the things you learn and all the people you meet at Docker events, you’re going to love what we have planned for you at this year’s DockerCon! We’re giving everyone at DockerCon access to a tool called #MobyMingle to connect with people who share the same Docker use cases, topic of interests or hack ideas, or even your favorite TV shows. So no matter where you’re traveling from or how many people you know before the conference, we will make sure you end up feeling at home!
Register for DockerCon 2017 
   

  

Docker turns 4 &#8211; our take on what makes the docker community so vibrant and unique #dockerbdayClick To Tweet

The post Docker Turns 4: Thank you Docker Community! appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

da Agency

Docker Turns 4: Mentorship, Pi, Moby Mingle and Moar

In case you missed it, this week we’re celebrating #Docker’s 4th Birthday with meetup celebrations all over the world (check out #dockerbday on twitter). This feels like the right time to look back at the past 4 years and reflect on what makes the Docker Community so unique and vibrant: people, values, mentorship and learning opportunities. You can read our own Jérôme Petazzoni’s blog post for a more technical retrospective.
Managing an open source project at that scale and preserving a healthy community doesn’t come without challenges. Last year, Arnaud Porterie wrote a very interesting 3-part series blog post on open source at Docker covering the different challenges associated with the People, the Process and the Tooling and Automation. The most important aspect of all being the people.
Respect, fairness and openness are essential values required to create a welcoming environment for professionals and hobbyists alike. In that spirit, we’ve launched a scholarship program and partnerships in an attempt to improve opportunities for underrepresented groups in the tech industry while helping the Docker Community become more diverse. If you’re interested in this topic, we’re fortunate enough to have Austin area high school student Kate Hirschfeld presenting at DockerCon on Diversity in the face of adversity.
But what really makes the Docker community so special is all of the passionate contributors who work tremendously hard to submit pull requests, file GitHub issues, organize meetups, give talks at conferences, write blog posts or record Docker tips videos.
Leadership, mentorship, contribution and collaboration play a massive role in the development of the Docker Community and container ecosystem. Through the organization of the Docker Mentor Week last year or a Docker Mentor Summit at DockerCon 2017, we’re always trying to emulate the community and encourage more advanced users to share their knowledge with newcomers.
A great example of leadership and mentorship in the Docker Community is Docker Captain Alex Ellis. We could not write a blog post on Pi Day without mentioning Alex and the awesome work he does around Docker and Raspberry Pi. In addition to sharing his knowledge through blog posts and videos, Alex is actively inspiring and mentoring younger folks such as Finnian Anderson. Alex’s support and advocacy got Finnian invited to DockerCon 2017 to give a demo of a Raspberry Pi-driven hardware gauge to monitor a Docker Swarm in real time.

If you’re pumped about all the things you learn and all the people you meet at Docker events, you’re going to love what we have planned for you at this year’s DockerCon! We’re giving everyone at DockerCon access to a tool called #MobyMingle to connect with people who share the same Docker use cases, topic of interests or hack ideas, or even your favorite TV shows. So no matter where you’re traveling from or how many people you know before the conference, we will make sure you end up feeling at home!

Register for DockerCon 2017 
   

  

Docker turns 4 &#8211; our take on what makes the docker community vibrant and unique dockerbday&#8230;Click To Tweet

The post Docker Turns 4: Mentorship, Pi, Moby Mingle and Moar appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

da Agency

10 do-not-miss hands-on labs at IBM InterConnect

Looking for a hands-on experience with technologies and services that can help your organization work smarter?
The InterConnect Hands-on Lab Center provides an opportunity for attendees at this year’s conference to get first-hand, technical experience with the latest IBM products and solutions. Stop by and meet experts. Try hands-on exercises at your own pace.
Choose from more than 200 hands-on labs in areas including Bluemix, hybrid cloud and more, and of three types: Bootcamp, scheduled, and open.
Bootcamp Labs are three- to four-hour sessions providing enrollees the opportunity for a deeper dive through hands-on work with new products and technologies. Attendees will also be eligible to receive an IBM Open Badge upon successful completion of the lab. You can find the details about the Bootcamp Labs at InterConnect here.
Attendees must enroll to secure seats at scheduled labs, so early enrollment is strongly suggested. See the detailed agenda of scheduled labs and enroll by using the IBM Events mobile app or InterConnect Session Expert.
Open labs are open to attendees on a first-come, first-serve basis. No registration is required. Attendees complete labs in a classroom setting, each with a dedicated laptop. Open labs are self-paced, but expert proctors are available to answer questions and guide users through the step-by-step instructions provided for the lab.
Here are five scheduled labs not to miss:
1. Make your processes cognitive by infusing Watson services
In this lab, attendees create and train a Watson Conversation Service in IBM Bluemix, then train it to conduct a conversation. Using IBM BPM, attendees will create a REST Service from a local Watson Conversation Swagger file. They’ll use Human Services to wire the Watson Conversation Service to a Coach, and finally, attendees will test the solution by conducting a machine-to-human conversation with Watson.
2. Build a custom web portal for IBM SoftLayer on Bluemix using Docker
In this lab, attendees will build a Python web application into an Ubuntu-based Docker image, which hosts and runs on IBM Bluemix. The Slick web portal for SoftLayer is built using the SoftLayer API. This lab is accompanied by a developerWorks Recipe.
3. Build, deploy and manage microservices with IBM API Connect and Docker container orchestration
Here, attendees can learn how to effectively deploy IBM API Connect in a Docker environment to create, secure and manage APIs and microservices. Using a Docker container orchestration (Swarm or Kubernetes), attendees orchestrate a complete API Connect setup for different environments.
4. Cognitive IoT transformation using Watson IoT platform, NodeRED, NoSQL and data science experience
This lab offers attendees the chance to implement their own cognitive Internet of Things (IoT) workflow using an open source pipeline backed by Linux and Raspberry Pi, MQTT, Apache CouchDB, NodeRED/Node.js, Apache Spark, Jupyter and Python. Attendees will capture, store, analyze and act based on insights created on-the-fly using different data science methods, including exploratory data analysis, time series analysis and artificial intelligence on IoT sensor data.
5. Agile development using MicroProfile and IBM WebSphere Liberty
In this lab, attendees learn how to use MicroProfile, as well as key application development technologies in Java EE 7 and beyond, to create a microservice that uses CDI, JAX-RS, WebSockets, Concurrency Utilities for Java and a NoSQL database running on WebSphere Liberty.
Check out these five open labs not to miss:
1. Build a travel application on IBM Bluemix using Watson and Cloudant in 15 minutes
This lab showcases the advantage of combining and using multiple services such as Cloudant as storage, Watson as an analytics engine and Node-RED to build/design an application. During this lab, attendees have a choice to build an application using either Watson Visual Recognition service or Watson Tradeoff Analytics service in Bluemix.
2. Working with containers in IBM Bluemix
In this lab, attendees learn to build and deploy a container in IBM Bluemix. They deploy a Cloud Foundry application, then build that same application as a Docker container and deploy it in Bluemix.
3, Learn how to extend API Connect to use IBM MQ
This lab reviews how IBM API Connect out-of-the-box capabilities can be extended by using DataPower extensions and Custom Properties to integrate with IBM MQ.
4. Using related Docker containers for Liberty and MongoDB database
In this exercise, attendees run the Liberty MongoDB sample application in one container with MongoDB database running in another container. Then, they’ll link the two containers and run a multi-container application using Docker Compose.
5. IBM UrbanCode Deploy: Introduction to designing software deployments
Here, attendees will configure IBM UrbanCode Deploy for the deployment of a pet store application to two different environments. They’ll create resources and versioned components, configure the environments, and deploy the application and snapshots. Attendees will also create teams and roles and learn the fundamentals of security.
Open Labs will be held in the Mandalay Bay South Seas ballrooms on the third floor in South Seas room F. Open labs are available at the following times:
Sunday 2:00 PM &#8211; 5:00 PM
Monday 11:15 AM &8211; 5:00 PM
Tuesday 11:30 AM &8211; 6:00 PM
Wednesday 8:00 AM &8211; 5:00 PM
Thursday 8:30 AM &8211; 12:30 PM
Follow @IBMCloudEdu to get the latest on labs and the InterConnect Hands-on Lab Center. Don’t forget to register today and enroll for your Bootcamp and scheduled labs.
The post 10 do-not-miss hands-on labs at IBM InterConnect appeared first on #Cloud computing news.
Quelle: Thoughts on Cloud