Uber Fired 20 People In A Harassment Investigation

Adnan Abidi / Reuters

Uber told employees at an all-hands meeting on Tuesday that it has fired 20 people and investigated at least 200 claims of discrimination and harassment in an internal investigation into its workplace culture.

The information was shared by Uber's chief human resources officer Liane Hornsey; CEO Travis Kalanick was not present at the meeting, and is spending time with family following the death of his mother in a boating accident.

Uber launched an internal investigation into its workplace culture after a blog post by former engineer Susan Fowler Rigetti went viral in February, alleging systemic sexism. A source who declined to be named said those terminated were removed due to a variety of reasons including harassment, bullying or discrimination. The company's all-hands meeting was scheduled for an hour and started around 10 a.m. in San Francisco.

Uber on Monday announced that it had hired Frances Frei, a Harvard Business School professor, as senior vice president of leadership and strategy. Uber said in a blog post announcing the hire that she would “act as a partner” to its head of human resources, Lianne Hornsey, and called her “one of the world’s most respected authorities on organizational transformation.” Frei was introduced to Uber staff by Hornsey during Monday's meeting.

The company has also hired a second female executive this week, Bozoma Saint John, who previously served as Apple's head of global consumer marketing for Apple Music and iTunes, according to reports. TechCrunch and Bloomberg reported Tuesday that Saint John had joined Uber. An Uber spokesperson declined to comment but said Saint John would not be filling the role of chief operating officer, for which Uber has been interviewing candidates for several months.

This story is breaking and will continue to be updated…

Quelle: <a href="Uber Fired 20 People In A Harassment Investigation“>BuzzFeed

Multiple Deployment Methods for OpenShift

Deploying an application to OpenShift is easy. The challenge is finding the best way to do it. Because OpenShift is so adaptable and flexible, it offers multiple ways to deploy an application. Learn about 6 different methods to deploy the same application.
Quelle: OpenShift

Containers aren’t a game: industry gets serious about Kubernetes development with Draft and Istio

The post Containers aren’t a game: industry gets serious about Kubernetes development with Draft and Istio appeared first on Mirantis | Pure Play Open Cloud.
As the infrastructure market settles down, more attention is being paid to what happens after you have your cloud up and running. This week we saw the announcement of not one, but two frameworks aimed at developers of Kubernetes-based applications.  Microsoft announced Draft, which provides an easy way for developers to build and deploy Kubernetes and other cloud-based applications, and Istio, announced by Google, IBM, and Lyft, provides a service mesh framework for running, monitoring, and controlling the multiple microservices that make up a cloud-native application.

The industry’s focus is starting to move up the stack; things are getting serious.
Draft: Simplifying development and deployment of cloud-native apps
When you think of Kubernetes, the first name to come to mind probably isn’t “Microsoft”, but Redmond’s been trying to catch up lately. One of the ways they’ve been doing that is with the acquisition in April of Deis, the container platform developed by Engine Yard.

Although there was concern — Microsoft hasn’t exactly been a bastion of open source championship — the Deis team, which is also behind the Helm deployment tool, this week announced Draft, an open source tool for developing and deploying cloud-native applications.

Draft simplifies the job of developers who want to write containerized applications by building the appropriate scaffolding for them so they don’t have to worry about anything but the application itself.  Brendan Burns, Director of Engineering at Microsoft Azure and Kubernetes co-founder, wrote, “When you first run the draft tool, it automatically discovers the code that you are working on and builds out the scaffolding to support containerizing your application. Using heuristics and a variety of pre-defined project templates draft will create an initial Dockerfile to containerize your application, as well as a Helm Chart to enable your application to be deployed and maintained in a Kubernetes cluster. Teams can even bring their own draft project templates to customize the scaffolding that is built by the tool.”

Techcrunch reports that Draft automatically detects whether code is written in Python, Node.js, Java, Ruby, PHP or Go. “It should be pretty easy to integrate this code with existing continuous integration pipelines,” they add.

The software can also code synchronized with Kubernetes, enabling developers to edit code locally but still have it run on the server.
Istio: A service mesh framework enhancing microservices
Istio (Greek for “sailing”, to keep with the Kubernetes theme) provides a way for developers to monitor, secure, and control microservices-based applications.  It works on the Kubernetes Service construct, proxying network transactions with the Lyft-created Envy proxy, so it can even be used with existing applications — no rewriting required.  

The idea is that developers create their application as usual, then run its deployment through Istio, which takes care of setting up all of the pieces. Once that’s done, you can see what’s going on with the application by simply looking at the Grafana dashboard.

Istio currently works with Kubernetes, and can be installed locally or on a public or private cloud.  The eventual goal, however, is to make it work with non-Kubernetes-related clouds, including those running on Mesos, as well as Google’s Cloud Endpoints.

TechCrunch points out that “It’s worth noting that this isn’t all that different from linkerd, a similar project that is now part of the Cloud Native Computing Foundation, the home of the Kubernetes project.” Linkerd supports Kubernetes, Docker, and Mesosphere’s DC/OS.
Reading between the lines
For the past several years, we’ve been focused on getting infrastructure up and running, but industry has now reached the point where that infrastructure is simply assumed; now the attention is on outcomes.

In the case of Draft and Istio, it’s about making development easier, enabling companies to get to those outcomes faster, but it’s about more than that: it’s about disaggregation.

In a move that echoes a greater emphasis on managed open cloud, both of these tools separate the developer from the worry of dealing with the fine points of architecture that aren’t directly related to what they’re doing. In this way, developers can more easily create applications that are not just more cloud-native, but also more cloud-independant, opening the door for hybrid cloud applications and a further emphasis on what needs to be done, rather than how to do it.The post Containers aren’t a game: industry gets serious about Kubernetes development with Draft and Istio appeared first on Mirantis | Pure Play Open Cloud.
Quelle: Mirantis

Managing microservices with Istio

Nowadays, there are more and more developers adopting a microservices approach to build their applications.
One of the main drivers for this is the need to build cloud-native applications, which are continuously available and dynamically scalable. This approach helps the developers break the applications into small, manageable pieces that can be developed and managed independently by different teams.
A microservices approach has  a lot of benefits, but can also be complex. Before a service can be deployed into production, many data and control plane issues relating to the operability of the service must be resolved, including:

how to provide services discovery and request routing between different microservices
how to control and secure access to the application and to individual microservices
how to efficiently scale up (and down) microservices while maintaining connectivity and overall application resiliency
how to collect and send logging and monitoring data for later consumption
how to enable DevOps functions, such as Canary deployments, A/B testing and gradual rollouts or roll-backs

Traditionally, much of that functionality had to be invented or rediscovered by every new application team, with support codified into the different microservices. While this may be an achievable goal within the confines of a single application and source base, as applications grow more complex and microservices are implemented using different languages and runtimes, the work becomes tedious and open to error.

By implementing a common microservices fabric, Istio addresses many of the challenges faced by developers and operators as monolithic applications transition to a distributed microservices architecture.
The initial (0.1) release was just announced at the Glue 2017 Conference. It is a result of collaboration between IBM, Google and Lyft to provide traffic flow management, access policy enforcement and telemetery data aggregation between microservices. All those are achieved without requiring any changes to the application code.  Thus, developers can focus on business logic and quickly integrate new features.
Istio provides an infrastructure-level solution for managing all service-to-service communications. By deploying a special sidecar proxy to intercept and act on traffic between microservices throughout the environment, Istio provides a straightforward way to create a network of deployed services, often referred to as a “service mesh.” Istio automatically collects service metrics, logs and call traces for all traffic within a cluster, including cluster ingress and egress. The use of sidecar proxies enables a gradual and transparent introduction without architectural or application code changes.
The service mesh is configured and managed using Istio’s control plane functionality to deliver the required quality of service attributes, such as load balancing, fine-grain routing, service-to-service authentication, monitoring and more. Istio’s Mixer component provides a pluggable policy layer supporting fine-grain access controls, rate limits and quotas. Since Istio has a control on communication between services, it can enforce authentication and authorization between any pair of communication services,
Istio is not targeted at any specific deployment environment. During the initial stages of development, and as it currently stands, Istio supports Kubernetes-based deployments. However, it is being built to enable rapid and easy adaptation to other environments, such as VMs and Cloud Foundry.
How we got there and what’s next
Our journey to microservices fabric started with developing and open-sourcing Amalgam8. Amalgam8 provided service discovery, smart routing capabilities and controlled resiliency testing.
Istio is the next step in our journey, bringing more powerful functionality and capability around security, policy management, rate limiting, auditing and basic API management.
We are excited to continue to work on building and extending Istio. One of the goals is providing security policy enforcement together with data collection and analytics. It can be extremely helpful to reaching compliance in the cloud native deployments.
What  do you like about Istio. and what are the main challenges when it comes to building and operating microservices applications?
Learn more about Istio.
Related articles:

developerWorks: IBM, Google and Lyft give microservices a ride on the Istio Service Mesh by IBM Fellow Jason McGee
Forbes: Google, IBM And Lyft Want To Simplify Microservices Management With Istio
Research blog: Upping the microservices game with Istio: A microservice mesh by IBM Fellow Tamar Eilam

 
The post Managing microservices with Istio appeared first on Cloud computing news.
Quelle: Thoughts on Cloud

Training helps users get more out of Watson Developer Cloud

Watson has come a long way since first winning against the Jeopardy! champions in 2011.
Watson was initially delivered via supercomputers, but now, with the evolution of cloud platforms, the power of Watson is pervasive and available to all via the Watson Developer Cloud. Delivered through IBM Bluemix, Watson Developer Cloud provides a suite of cognitive services that empower developers to extend and build next-generation user experiences in applications that can interact with humans.
Watson Developer Cloud provides a set of building blocks for developers to build cognitive solutions. Many Watson Developer Cloud services can be consumed by applications as cognitive services with no training effort required.
For example, the Language Translator or Tone Analysis services can, as the names suggest, translate from one language to another or analyze the tone of a body of text by simply invoking the service.
Other services on Watson Developer Cloud require training. Examples include Retrieve and Rank, Discovery, and the Conversation service. When working with a service that requires training, insights delivered by the service can only be as effective as the training provided.
The purpose of AI and cognitive systems developed and applied by IBM is to augment human intelligence. When using Watson’s Discovery service on Bluemix, for example, to augment human ability to glean insights from data, we first need to train Watson to understand information specific to areas of focus, such as an industry or scientific discipline.
Users can do this using Watson Knowledge Studio to create a custom model that the Discovery service will use to enrich document content with cognitive metadata. Similarly, when using the Retrieve and Rank service, training a machine learning ranker helps Watson surface the most relevant information from a collection of documents. Training in each instance requires domain-specific expertise with relevant training data. Without this domain expertise and training, Watson cannot reach its full potential with a user’s data.
Watson’s ability to augment human intelligence is dependent on training, domain expertise and, ultimately, human intelligence. Watson Developer Cloud provides access to Watson capabilities with nothing more required than an IBM Bluemix account.
Why not build cognitive capabilities into your applications with IBM Watson on Bluemix?
Get started with Watson Developer Tools.
The post Training helps users get more out of Watson Developer Cloud appeared first on Cloud computing news.
Quelle: Thoughts on Cloud

Become a disruptor: Announcing new cloud integration capabilities

Digital business transformation is the biggest business disruptor of our age. Consider that the world’s top accommodations provider owns no real estate, and the world’s biggest taxi company owns no vehicles.
Your business can remain vulnerable to “born on digital” disruptors like these. Or you can embrace the seismic shift toward digital business that comes through a fully integrated cloud computing environment.
IBM recognizes that business is about to take the next great leap forward. The future is built on data, enabled by the cloud and driven by cognitive computing to redefine immersive experiences. Create new partnerships, innovate quickly and do it all with one singular goal—providing a truly unique and timely experience for customers, employees and business partners. Create an experience that disrupts their expectations and makes them see your company in a new light.
The ability to connect to everything just became critical to the success of your business. Most of us live in a multicloud environment where you need to be able to access data from the Internet of Things, business partners, third-party clouds and even your own customers. Integration has evolved from a function of IT to business enabler.
This shift is going to require a more unified view of integration, one that support many of the latest integration techniques: API, application, message-based and data. Integration will be based on multiple clouds, new lightweight architectures, event-driven patterns and new connectivity options. You can move beyond connecting systems to connecting entire ecosystems of data so you can gain insight and get to market faster than your competition.
The right cloud integration solution delivers new ways of accessing and combining information. It’s built on an architecture that addresses challenges around security, governance, performance and scale necessary to support business models designed around cloud and cognitive solutions.
Today, IBM is announcing new capabilities to our market-leading cloud integration solution:

New API monetization functionality built right into API Connect allows you to start seeing revenue directly from your APIs.
New open source API microgateway gives your developers with a first-class framework for building their own gateway solution.
New Watson connectors, and App Connect on Bluemix expands functionality to build cognitive solutions and connect cloud and on-premises systems.
New Connector Pack with MQ provides the ability to perform a message-driven query into IBM Blockchain for greater insight.

IBM is dedicated to your success. Our new capabilities are just further evidence of our commitment to driving digital transformation and business results for our customers.
Find out more at IBM Cloud Integration.
 
The post Become a disruptor: Announcing new cloud integration capabilities appeared first on Cloud computing news.
Quelle: Thoughts on Cloud