Recap: London OpenShift Commons Gathering January 29th 2020 [Videos and Slides]

It’s A Wrap! The first 2020 OpenShift Commons Gathering took place on January 29th in London at Savoy IET.  
This OpenShift Commons Gathering in London featured deep dives into OpenShift 4, DevSecOps, Operators, OKD4, Quarkus, Container Storage and much more!
 
The OpenShift Commons Gathering in London brought together over 350 Kubernetes and Cloud Native experts from all over the world to discuss container technologies, best practices for cloud native application developers and the open source software projects that underpin the OpenShift ecosystem.
Public Health England’s Francesco Giannoccaro discussing the use of open source technologies to support scientific computing at OpenShift Commons Gathering in London
 
Here are the videos and slides from the proceedings:
 

The Search for Connections Across the OpenShift Ecosystem
Diane Mueller (Red Hat)
Slides
Video

State of the Union: Unified Hybrid Cloud Vision
Julio Tapia (Red Hat)
Slides
Video

OpenShift 4 Release and Road Map Update
Duncan Hardie (Red Hat) Jan Kleinert (Red Hat)
Slides
Video

OKD4 Release Update & Road Map
Christian Glombek (Red Hat)
Slides
Video

State of DevSecOps: The Seventh Deadly Disease
John Willis (Red Hat)
Slides
Video

Case Study: OpenShift Hive at Worldpay
Bernd Malmqvist (Worldpay) Matt Simons (Worldpay)
Slides
Video

Future Finance Data Innovations with Open Banking and PSD2 @ Asiakastieto
Eero Arvonen (Suomen Asiakastieto)
Slides
Video

Lightning Talk:DevSecOps Culture with OpenSource Tools
Benjy Portnoy (Aqua Security)
Slides
Video

Lightning Talk: Secure DevOps for OpenShift
Chris Kranz (Sysdig)
Slides
Video

State of the Operator Ecosystem: Framework, SDKs and Best Practices
Guil Barros (Red Hat) Jason Dobies (Red Hat)
Slides
Video

Hybrid Cloud Case Study: OpenShift at Deutsche Bank
Jeremy Crawford (Deutsche Bank) Dipesh Patel (Deutsche Bank)
Slides
Video

Lightning Talk: OpenShift Container Storage
Karena Angell (Red Hat)
Slides
Video

Case Study: OpenShift at Public Health England
Francesco Giannoccaro (Public Health England)
Slides
Video

OpenShift Hosted Services Update
Patrick Strick (Red Hat)
Slides
Video

AMA Panel – Red Hat Upstream Project Leads, Engineers and Product Managers
 Diane Mueller (Red Hat) – moderator
N/A
Video

Closing: Road Ahead & Wrap-Up
Diane Mueller (Red Hat)
Slides
Video

 
To stay abreast of all the latest releases and events, please join the OpenShift Commons and join our mailing lists & slack channel.
What is OpenShift Commons?
Commons builds connections and collaboration across OpenShift communities, projects, and stakeholders. In doing so we’ll enable the success of customers, users, partners, and contributors as we deepen our knowledge and experiences together.
Our goals go beyond code contributions. Commons is a place for companies using OpenShift to accelerate its success and adoption. To do this we’ll act as resources for each other, share best practices and provide a forum for peer-to-peer communication.
Join OpenShift Commons today!
The post Recap: London OpenShift Commons Gathering January 29th 2020 [Videos and Slides] appeared first on Red Hat OpenShift Blog.
Quelle: OpenShift

Bringing a passion for privacy to cloud

Editor’s note:This is the first in our Black History Month series of Cloud Googler profiles. Michee Smith is a product manager within Google Cloud who’s responsible for building products that help protect customer privacy when they store their data within Google Cloud. In her almost five years at Google, she’s led the charge on many key projects, like launching our first Political Ads Transparency Report, redesigning the Transparency Report to be even easier to use, and working on our efforts across Google to comply with the GDPR. We sat down with Michee to talk about her career path, her tech passions, why representation matters, and why staying true to yourself is a winning formula. Michee on why privacy mattersI’m passionate about making our customers super comfortable with holding data inside of Google Cloud. In my opinion, doing privacy right is twofold: Developer tools should make privacy the easiest thing to build into the product. Developers shouldn’t have to jump through hoops to deliver notice and consent flows, and enforce identity and access management policies. It should be natural to the tooling they use and how they work. The second part, and most important, is that customer expectations should be set, then met, around who accesses their data and how it’s used. Users should never be surprised about who saw their data and how it was used; products with transparency and control built-in by default helps make sure they aren’t. At Google, I work on products like Access Transparency and Cloud Audit Logs, which help users easily track who has accessed their data and when. My affection toward privacy and security started at my previous job, when I started to learn how nuanced and technical these important topics are. I became a privacy champion for my products, doing office hours and privacy assessments to help teams understand why it’s important and how to make it easier for users to adopt these products. Then, Google hired me to work on privacy full time, where I’ve worked on a bunch of interesting projects, including Google’s efforts to comply with the GDPR, Europe’s broad privacy regulations. Now, as a part of Google Cloud, I lead a team that builds products to make sure we are a trusted cloud for customers to put their data. At Cloud, I have the opportunity to help not just Google, but many companies across the world, work to ensure the privacy of their data. One project on my team, called Key Access Justifications, lets customers truly be the final arbiters of access to their own data, and gives transparency around Google personnel access to their data. I also get to work on Google’s compliance efforts, and work with product managers and engineers on the best ways we can give our customers data controls.Working at the speed of trust is faster than anything else.On choosing her pathI knew I wanted to study computer science in high school and that meant being around people who were different than those who I grew up with in my predominantly Black neighborhood. So, I applied for a full scholarship to Rochester Institute of Technology to be around people who were different from me. College was the first time I had an email address, and I didn’t even have a computer until I started my first job. I learned technical skills, and also about different cultures and groups of people. Ultimately, that understanding and empathy not only helps me navigate the corporate world, but build products for everyone. I’ve always had a belief in myself, which I credit in part to being raised in the Black church, a supportive and encouraging environment. But even so, it’s sometimes been hard to maintain that confidence. I regretted not taking certain opportunities at RIT, like collaborating with my chemistry professor on a biomedical computing research project, because I didn’t want to fail. I didn’t believe in myself enough. The first time someone asked me to speak at a conference, I had to be pushed. But after it was well-received, I realized I shouldn’t counsel myself out of doing anything. Let other people tell me “no,” but don’t let myself be the one to say it.  I want people to know I’m not a unicorn—I’m not here because I’m necessarily special, but because I haven’t let rejection stop me. My philosophy is that I’m the only one who can tell me I can’t do something. The superpower I rely on is that I won’t let other people tell me I’m not good enough.The superpower I rely on is that I won’t let other people tell me I’m not good enough.On being yourself, no matter whatAt my first job after college in 2003, people would talk over me. I was just the college hire, the junior employee. I had to show up, and I decided to start dressing up for work as a way to show my presence and be taken more seriously. Surprisingly, it worked! Soon I was leading on projects, and my colleagues started looking to me for my counsel. In making that decision to change how I dressed, I became conscious of how I can adapt to situations without changing who I am. It’s a negotiation with myself that I don’t take lightly. I always remember to be true to my values, and I tell my managers that I value camaraderie. I spend more time with my colleagues than my family, so I need to feel good about working with them, and them working with me. Being myself at work lets other people feel comfortable being themselves around me, too. That camaraderie and trust allows us to work quickly and effectively. On the importance of mentors and representationI believe you should always have three relationships: mentor, mentee, peer. I always have those going at all times, whether it’s formal or informal, and I regularly speak at conferences and attend student events, too. Relationships and representation in tech really matter. Often times, people of color don’t see people who look like us in these roles and on stages. There’s a sense of gratitude, belonging, and relief to see someone who looks like you. I want to show up to help others imagine themselves in this role, building products for everyone, and let them know that they, too, can find their superpower.
Quelle: Google Cloud Platform

Introducing the Docker Index: Insight from the World’s Most Popular Container Registry

8 billion pulls! Yes, that’s billion with a B! This number represents a little known level of activity and innovation happening across the community and ecosystem, all in just one average month. How do we know? From the number of pulls and most popular images to top architectures, data from Docker Hub and Docker Desktop provide a window into application development trends in the age of containers. 

Today, we are sharing these findings in something we call the Docker Index – a look at developers’ preferences and trends, as told by using anonymized data from five million Docker Hub and two million Docker Desktop users, as well as countless other developers engaging with content on Hub. 

At Docker, we’re always looking for ways to make life easier for developers. Understanding the what, why and how behind these projects is imperative. As these trends evolve, we will continue to share updates on the findings.

Whether containers will become mainstream is no longer a topic of debate. As the Docker Index data suggests, containers have become a mainstay to how modern, distributed apps are built and shared so they can run anywhere. 

Usage is showing no signs of slowing down. Docker Desktop and Docker Hub are reaching an increasing number of developers and users are engaging with content from Hub at higher rates. Content from community developers and open source projects continues to make Hub a central and valuable source for developers looking to build containerized applications. 

Collaboration is key when building apps so that developers aren’t starting from scratch. Containers have helped to make building blocks the new norm. With container images readily accessible and shareable, everyone can be more productive. 

Modern apps also give rise to increasingly diverse development environments, drawing more attention to the importance of choice. The ability to select your preferred framework, operating system and architecture go a long way in creating a more productive experience for modern app development.

The ecosystem and community are shaping the future of software development and containers are at the heart of this transformation. The level of activity and collaboration is hitting a new gear and with it, continued advancements in how developers build and share apps. We look forward to sharing updates on the Docker Index data over the course of this year. 

To get started with Docker, download Docker Desktop and take a tutorial here https://www.docker.com/get-started.
The post Introducing the Docker Index: Insight from the World’s Most Popular Container Registry appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Sicherheit: "E-Mail ist das Fax von morgen"

Auf dem europäischen Polizeikongress erklärt der CEO von Secusmart, warum Sicherheitstools nur verwendet werden, wenn sie einen Mehrwert bieten und warum Behörden und Firmen aus Sicherheitsgründen auch die private Nutzung von Geräten erlauben sollten. (Security, Instant Messenger)
Quelle: Golem