devopsy.kinsta.cloud

Category: DevOps in the Cloud

Revisiting 2020 Cloud Predictions in Light of COVID-19

Back when the technology industry made its cloud predictions for 2020, no one forecasted the impending impact of COVID-19. Across the board, the pandemic has changed the way consumers have digital experiences, and made businesses realize their legacy IT infrastructure may not be up to keeping pace with new demands.

So how does that change some of the cloud predictions put forward at the end of 2019?

Increased Importance of Hybrid Cloud

Hybrid cloud is a critical focus area as IT organizations prepare to work and operate with clouds but many applications continue to run on-premises. While I predicted that hybrid would be a crucial area, I did not expect the actual pace, which has become much higher.

With cloud technologies becoming part of every IT environment from operations to orchestration and beyond, its adoption, including the move to hybrid, will accelerate due to this new normal. More organizations will adopt a hybrid cloud approach sooner than expected, as they’ll have no other choice to keep up with technology’s aggressive evolution. They must run legacy workloads or local cloud on-premises while also deploying on public clouds and manage workloads there; this is from both a VM and Kubernetes perspective. Red Hat and VMware are going head-to-head here.

As COVID-19 severely impacts IT teams’ time and budget, those that provide solutions that are easier to run and integrate will win this space. Simplicity, known skill sets and familiar products with shorter time to integrate will be critical.

Containers Will Still Become the De Facto Software Packaging Model

Container platforms have become an essential factor in the hybrid cloud landscape, accelerating multi-cloud adoption in enterprises. Gartner predicts that by 2023, 70% of organizations will be using at least three containerized applications in production. Even with the prioritization of other tasks due to COVID-19 disruption, container adoption is continuing at full speed, along with the wider implementation of Kubernetes.

COVID-19 should not impact the adoption of containers for those already on a Kubernetes platform. Anyone who has started with Kubernetes uses containers already, and organizations understand the value of Docker-based DevOps, local PC development and CI/CD pipelines based on containers.

2020 No Longer the Year of Serverless Computing

I expected a move toward maturing best practices, security solutions and tooling around serverless computing as more IT organizations looked to implement the technology. I saw AWS Outposts as the likely chief disruptor here, as it blurs the lines between on-cloud and on-premises workloads and services, with Google Anthos and Microsoft Azure as its main competitors.

However, we can now assume that COVID-19 will have impacted the adoption of new technologies. This is because many organizations are unable to deal with new technology due to the other tasks that have taken precedence for now. I also expect organizations that were experimenting with the likes of AWS Lambda or kNative may take a step back for at least three to six months.

Service Mesh Not Yet Standard for Cloud-Native Apps, Microservices

I expected the industry to start uniting behind a single strategy to service mesh in 2020. But as of now, the list of open source service mesh options continues to grow. This makes it one of the most interesting domains today, full of emotions, fights and changes, unaffected by COVID-19.

As a standard continues to elude the industry, things can become highly problematic. This is because once you adopt service mesh, it becomes a critical path in your deployment and application dependency.

A few weeks ago, I spoke with Dell’s CTO, John Roese, who said he firmly believes the industry will eventually converge. Although IBM, VMware, Red Hat, Pivotal and Google commit to Istio as their service mesh, the industry is still waiting patiently for this convergence to happen.

While all of this infighting is happening, a new body, the Service Mesh Initiative, was set up to ensure none of the hyper-scalers could impose a lock-in on service mesh. This could begin to change things, as IT organizations can define applications that use service mesh without tightly binding to any specific implementation. Watch this space.

While COVID-19’s impact may have thrown a few things off base at the start of 2020, it’s likely a temporary slowdown. As new demands require a more flexible IT environment to keep pace, there is no question that things will speed back up. And when it does, IT organizations must be ready to implement the latest innovations or risk being left behind.

July 20, 2020
Cloud Is Red Hot in the COVID-19 Era
As digital transformation accelerates, cloud services are helping organizations thrive in a COVID-19 world

As the days tick by and the gloomy ramifications of COVID-19 become more apparent, one harsh truth has become crystal clear: Industries that have invested in digital transformation stand a better chance of recovery and survival than others.

The banking industry is a lighthouse example of this principle. Even though the brick-and-mortar branches have had to pull down shutters because of lockdowns and social distancing requirements, many banks have still operated their businesses as usual. They have kept the lights on and handled the pressure of increased online and mobile transactions thanks to cloud-based services.

While the internet has been a key enabler for digital banking, cloud has become the backbone. Cloud is making IT infrastructure vanish. Cloud is where businesses render servers, churn and analyze data, and keep applications humming so they can collaborate with partners and customers.

Many businesses are quickly turning around, moving at speed to adapt and transform their operations. YMCA, Planet Fitness and Nike are offering online fitness classes. Schools and colleges are providing online learning. The demand for Netflix and Amazon Prime has gone up dramatically, and both organizations are now easing telecom network congestion by lowering their bit rates. Online grocery retailers are attempting to keep pace with demand spikes. And working from home has gained momentum, sending the demand for routers, modems and data cards through the roof.

We will see a slew of innovations like these in the coming months, from businesses big and small, that will bring cloud services into sharp focus with their need for scale in a COVID-19 world. Everyone is looking to the cloud to reimagine businesses and make collaboration happen on an unprecedented scale, and the cloud has proven its ability to respond with speed while remaining robust.

While enterprise IT, governments, entrepreneurs and other organizations work on their plans to respond to crises, the focus should be on providing great user experience in the post-COVID-19 era. In regard to the cloud, enterprises should focus on the following key tactics to prepare accordingly:
1. Scaling existing services: Applications currently hosted on-premises will move to the cloud. Extending the data center via software-defined data center solutions into hyperscalers will help achieve scale and business flexibility.
2. Giving businesses ample wiggle room: By adopting a multi-cloud strategy, businesses can de-risk themselves against failure, capacity challenges and operational barriers.
3. Extending and expanding geographical reach: This can be done by deploying applications to geo-specific cloud platforms.
4. Going cloud-native: Design and develop new applications on PaaS using a DevOps approach for rapid rollouts.
5. Strengthening the core strategy: The strategy should be to support rapid and unexpected changes in work and service consumption needs through optimal network bandwidth, VPN connectivity, bandwidth throttling, consumption-based adoption model, remote VDI as a service and SD-WAN based solutions.
6. Investing in a heightened security posture: Cloud solutions should be based on data classification (privacy, availability) without sacrificing application, infrastructure, access or data security.
7. Developing new working models: Address medium and long-term requirements with a hybrid support model and local onsite versus remote versus offshore support.
Having achieved the above, enterprises would be wise to reduce their operations costs and channel the savings into new cloud initiatives. Enterprises should attempt to extend the life cycle of their existing assets before considering a refresh, while simultaneously moving to a subscription-based, pay-as-you-go model rather than footing steep licensing bills.

But the cloud journey doesn’t end there. Goal-oriented and highly motivated businesses will use their cloud credits to support proofs-of-concept and other essential services. One way of doing this is to containerize applications and remediate end-of-life issues around OS, improving computing density and rationalizing OS licenses for cost savings. The other established route to achieve savings is to outsource value streams to trusted partners.

COVID-19 is going to accelerate the cloud journey for scores of enterprises, and investments in the technology will quickly show their upsides—improved business resilience, cost control, and above all, the ability to keep the lights on.
July 8, 2020
AWS Brings Machine Learning to Code Optimization

Amazon Web Services (AWS) has made generally available a tool dubbed Amazon CodeGuru that employs machine learning algorithms to recommend ways to improve code quality and identify which lines of code are the most expensive to run on its cloud service.

Peder Ulander, director of open source for AWS, said Amazon CodeGuru not only helps improve performance and resource utilization but also reduces the time and effort spent optimizing applications before and after they are deployed.

Amazon CodeGuru is based on a set of AWS machine learning algorithms to identify best practices for deploying code. It creates a profile of the code deployed and then surfaces recommendations to improve performance and reduce costs by employing the most appropriate tier of the cloud service.

That latter capability is critical because developers don’t always factor costs into deciding which tier of a cloud service to employ. Amazon CodeGuru enables IT teams to proactively optimize their cloud usage, noted Ulander.

Amazon CodeGuru can pull code from either GitHub or CodeCommit repositories, with support for other repositories planned. It requires developers to insert agent software developed by AWS into their code. Once a pull request is made, Amazon CodeGuru automatically starts evaluating the code using trained artificial intelligence (AI) models developed using data gathered from thousands of different open source software projects by AWS and its parent company.

Once the analysis is completed, Amazon CodeGuru will generate a graph showing such metrics as latency issues and CPU utilization rates, as well as human-readable recommendations to surface specific issues and remediations that include example code and links to relevant documentation for any line of code. Amazon CodeGuru can observe application runtimes and profile application code every five minutes.

Amazon CodeGuru has two core components. Amazon CodeGuru Reviewer automatically flags common issues that deviate from best practices and provides recommendations to fix them, including example code and links to relevant documentation. It then opens a pull request and automatically starts evaluating the code using machine learning models to identify the line of code, specific issue and recommended remediation, and provides access to a pull request dashboard that lists all the information gathered by all code reviews.

IT teams can provide feedback on CodeGuru Reviewer recommendations by clicking on a thumbs up or thumbs down icon, which helps improve recommendations over time using machine learning.

The second component is Amazon CodeGuru Profiler, which identifies the most expensive lines of code by analyzing the runtime behavior of their applications. Armed with those insights, IT teams can identify and remove code inefficiencies, improve performance and decrease compute costs.

IT teams today spend an inordinate amount of time debugging code to address a broad range of issues. The paradox is the more applications they deploy, the more time they spend debugging. Perhaps the time has come to finally let machines discover code issues in the hopes that developers will use their time writing new code, not fixing it.

July 7, 2020
Cloud Foundry Foundation Updates CLI to Extend DevOps Processes

The Cloud Foundry Foundation (CFF) today released an update to its command-line interface (CLI) that will enable DevOps teams to build more granular and complex workflows spanning multiple processes across the open source platform-as-a-service (PaaS) environment.

Announced at the Cloud Foundry North American Summit, version 7 of the Cloud Foundry CLI employs updates to the application programming interfaces (APIs) exposed via the Cloud Foundry PaaS to invoke package, droplet, build and process control resources while adding resources such as sidecars, manifests and deployments.

The updates to the CLI and associated APIs will make it possible to enable rolling application deployments, run multiple processes within the same container and add metadata to objects.

Chip Childers, executive director of the CFF, said most of the organizations that have adopted the Cloud Foundry PaaS are already fairly advanced when it comes to implementing best DevOps practices. The latest version of the CLI will make it possible to tighten DevOps feedback loops within the PaaS environment.

In general, CFF is positioning the Cloud Foundry PaaS environment as a common framework for building and deploying applications on traditional virtual machines and Kubernetes clusters. The CFF has launched an incubation project, dubbed KubeCF, that enables a virtual instance of the Cloud Foundry runtime to be deployed on Kubernetes. At the same time, the CFF has made available Project Eirini, another incubation project that enables the Cloud Foundry scheduler to be replaced by Kubernetes, and Project Quarks, which allows the CF Application Runtime to be packaged using containers.

The CFF has also launched Cloud Foundry for Kubernetes (cf-for-k8s), a more ambitious effort to replace the underpinnings of the PaaS environment with a Kubernetes foundation. That initiative should result in Cloud Foundry requiring much less IT infrastructure to be deployed. The CFF has also committed to embracing other cloud-native technologies such as the Istio service mesh.

As part of that effort, the Bosh framework that the CFF created to automate the deployment of its PaaS will also eventually be replaced by a framework optimized for Kubernetes environments.

Childers said it’s now clear Kubernetes will mature to the level required to support an enterprise-class application development environment. The opportunity now is for IT vendors such as VMware, SUSE and others to deliver an application development environment that makes developers more efficient than any other on cloud-native infrastructure, said Childers.

For example, VMware today is making available a public beta of the VMware Tanzu application service for Kubernetes based on the cf-for-k8s project.

Contributors to the CFF project are clearly trying to make up for lost time. Rival PaaS environments such as Red Hat OpenShift have long been integrated with Kubernetes. The CFF community, however, is betting more enterprise IT organizations will embrace Kubernetes once they discover various distributions of a PaaS environment they already rely on is available on that platform.

Whatever the path chosen, the one thing that is clear is the Cloud Foundry PaaS is about to become a lot more accessible to organizations that, no matter how great the developer experience, previously balked at its overall size.

June 24, 2020
ServiceNow Acquires Sweagle to Advance DevOps Agenda

ServiceNow has acquired Sweagle, a provider of a repository for collecting configuration data that makes it easier to manage IT environments at scale.

RJ Jainendra, vice president and general manager of DevOps and IT business management at ServiceNow, said Sweagle advances the DevOps initiative his company launched last year by providing a way for IT teams to more easily share configurations created by a variety of tools within a single repository. Those configurations can then be vetted to make sure DevOps teams are not reusing configuration that might be propagating a cybersecurity vulnerability, he said.

Sweagle is essentially a modern implementation of a configuration management database (CMDB). It will be revamped to have the same look and feel of a ServiceNow application once the deal formally closes in the early part of the third quarter, Jainendra added.

ServiceNow also plans to integrate Sweagle with its Service Graph, which enables teams to visually track metrics across a service spanning multiple platforms.

Jainendra said as IT teams deploy applications it’s not uncommon for them to track more than 50,000 data configurations. Sweagle provides an opportunity to bring some order to what historically is a set of IT processes that are becoming more complex as organizations embrace microservices based on containers and serverless computing frameworks.

Sweagle complements a DevOps initiative ServiceNow launched late last year through which the company is providing increased visibility into DevOps processes to IT service desk staff. ServiceNow DevOps collects metrics from various DevOps platforms that can be analyzed alongside the metrics ServiceNow surfaces using an ITIL-based framework accessed via a software-as-a-service (SaaS) platform.

Ultimately, ServiceNow doesn’t anticipate DevOps replacing ITIL as much as it sees both approaches creating a need for IT teams to strike a balance across disparate styles of managing IT, each of which places different levels of emphasis on agility and stability, Jainendra noted.

Naturally, each IT organization will need to determine how best to balance those conflicting goals. In many cases, organizations will decide to manage applications very differently from the underlying IT infrastructure on which they are deployed.

Regardless of approach, IT organizations have never been under more pressure. In the wake of the COVID-19 pandemic more applications are moving into the cloud to achieve flexibility and resiliency. At the same time, more application code is being pushed out to the network edge. As IT becomes complicated, many organizations are mixing and matching best ITIL and DevOps practices as they best see fit.

As is the case with any philosophy, there are proponents of DevOps and ITIL frameworks that are not given to compromise. However, most IT organizations tend to gravitate to the middle ground. In the wake of the current economic downturn, it’s probable there will be an even larger inclination toward compromise. After all, the rate at which applications are moving into the cloud is accelerating. However, most of those applications are now being accessed by devices that are more distributed than ever now that more people are working from home.

June 23, 2020
HashiCorp Unfurls Cloud Platform for Managed Services

HashiCorp today at its online HashiConf Digital event launched HashiCorp Cloud Platform (HCP), through which it intends to make all of its software available as a fully managed service.

At the same time, HashiCorp announced a public beta of an update to HashiCorp Terraform, a curated instance of an open source tool for configuring IT infrastructure that adds additional workflow capabilities.

Finally, an update to Nomad, a cluster manager and scheduler for containerized application environments, adds support for multiple clusters as well as the Container Network Interface (CNI) specification defined by the Cloud Native Computing Foundation (CNCF).

Rob Genova, director of product marketing for cloud services at HashiCorp, said although the company previously made some of its offering available as a managed service, HCP will serve as a foundation on which HashiCorp will manage updates to its software on behalf of end customers.

The first managed service on HCP, now available in private beta, is an instance of the Consul service mesh deployed on Amazon Web Services (AWS), which will be followed by an instance of Vault, secrets management software developed HashiCorp, that will also be deployed on AWS.

At the core of HCP is a HashiCorp Virtual Network (HVN), which offers a common abstraction across cloud providers around an isolated single-tenant network. Each HVN can have multiple services deployed within it. In the future, HashiCorp is promising HVN will enable peering across cloud providers and cross-provider clustering of its software. Support for additional cloud services will be added based on customer demand, added Genova.

HCP will be offered on a pay-as-you-go pricing model to minimize upfront costs, which Genova said should make Consul and other HCP services more accessible to smaller teams and organizations. Costs will increase only when workloads scale. Both development and production pricing options will be made available, he said.

HashiCorp already provides access to hosted instances of Consul and Terraform, which it will continue to offer alongside HCP, Genova added.

Genova said it’s become apparent more organizations would prefer to have HashiCorp manage Consul, Vault, Terraform and Nomad on their behalf. At a time when many organizations have limited IT resources, Genova said many organizations want to devote the bulk of their limited internal resources to building and deploying applications rather than the infrastructure required to maintain them.

It’s not clear how many organizations will opt to rely more on managed services in the wake of the economic downturn brought on by the COVID-19 pandemic. At a time when many organizations are either reducing or freezing headcount, all options are being considered. Many internal IT teams may occasionally employ a managed service to extend their own capabilities. In other cases, developers may bypass an IT operations team altogether.

In the wake of the pandemic, Genova noted more organizations simply want to deploy resources in the cloud to ensure availability while gaining increased flexibility.

Regardless of the path chosen, the days when IT teams felt more compelled to do everything themselves are, for better or worse, changing utterly.

June 22, 2020
IT Modernization Yields Business Benefits Even in Early Stages
In recent years, with the emergence of newer technologies ranging from the cloud to machine learning, IT modernization has evolved from a replacement of end-of-life infrastructure to an enabler of innovation and business value. It is a complex process that can take months or even years, but a recent survey shows that the effort begins to deliver measurable results almost as soon as an organization executes the first steps on its roadmap.

In The State of IT Modernization 2020, an IDG Research Services survey of 200 IT executives commissioned last December by Insight Enterprises’ Cloud + Data Center Transformation team, respondents that had completed 25% or less of their initial modernization objectives reported achieving business improvements in each of the eight categories measured. Sixty-five percent had already achieved better quality of service. Significant progress had also been made in improving customer experience/satisfaction (52%), cost savings (50%), uptime (44%) and the ability to create new revenue-generating products and services (42%).

Organizations that had completed their initial modernization objectives reported even better outcomes on all eight measures, notably including the ability to extract business value from data (56%) and faster time to market for new products and services (50%).

The findings clearly demonstrate that a modernized IT ecosystem is a core building block of business transformation. Whether it’s spinning up a new service or application quickly, doing a deep data dive to identify new market opportunities or using artificial intelligence to improve sales forecasts or warehouse operations, it’s essential to have the horsepower, agility and advanced data analysis capabilities to do the job.

The survey of CIOs, CTOs, CSOs and IT directors working at organizations with an average of 29,294 employees also revealed a wide range of details about the status of IT modernization efforts. Let’s look at some examples.

Progress Made

Fifty-six percent of the enterprises surveyed have either achieved initial IT modernization objectives or have made significant progress toward doing so, while 19% have made moderate progress and 26% are in the beginning stages. Interestingly, even those in the earliest stages are pursuing emerging technologies such as AI, machine and/or deep learning (43%), automation to support scale-out and other cloud strategies (37%), cloud native application development (35%) and public cloud container services (35%).

Projects Derailed

Despite this progress, the road to IT modernization can be bumpy. Forty-one percent of survey respondents reported having delayed or abandoned some of their 2019 IT modernization initiatives. The top reasons cited were competing priorities (46%) and lack of a clear roadmap or strategy (45%). Other causes included data security concerns (39%), inadequate in-house expertise (38%), poor preparation (29%) and outdated processes or tools (27%).

Shifting Cloud Strategy

Whether they have just embarked on their IT modernization journey or have made significant progress on their roadmap, organizations continue to grapple with optimizing their cloud strategy. The survey showed that:
- Ninety-two percent of survey respondents increased workloads deployed in the public cloud and 91% in the private cloud in 2019, reflecting the ongoing increase in cloud adoption as well as migration from one platform to another.
- Eighty-nine percent switched or planned to switch from an all-private or all-public cloud strategy to a hybrid cloud approach – and 87% adopted a multicloud approach using more than one public cloud provider – as they attempted to find the right path for their cloud needs.
- Eighty-four percent moved select workloads from a public cloud to an alternative cloud or non-cloud location, suggesting a failure to perform appropriate cost modeling, workload/platform alignment and other due diligence before the initial move.
Poor Public Cloud Cost Controls

More than two-thirds of survey respondents reported that public cloud costs exceeded their expectations, with cost overruns for roughly half that group ranging from 51% to 100%. Most of the causes can be traced to inadequate due diligence, governance or cloud optimization efforts, often due to a lack of in-house expertise in these areas. Examples include: unexpected data egress charges, subscribing to more cloud resources than required, failure to take advantage of vendor volume discounts, lack of knowledge to analyze monthly cloud costs and failure to optimize cloud workloads to extract maximum value from cloud platforms.

Managed Services

Adoption of managed services is widespread at every stage of the IT modernization journey, with an average of 95% of respondents outsourcing one or more IT operating environment functions to a managed services provider and 84% outsourcing cloud management.

Top Challenges Faced

Governance is the number one modernization challenge in 2020, according to survey respondents, with new strategies and processes required to ensure control over areas ranging from cloud deployments to continuous integration and continuous delivery (CI/CD), automation and orchestration, and infrastructure as code. Optimizing and managing the centers of data that are replacing the traditional data center ranks as number two, with workloads located on-premises and in multiple clouds as well as on the edge.

At the same time, most IT organizations have long-standing cultural and technological norms that need to change in order to move modernization initiatives forward. Hurdles cited elsewhere in the survey range from IT silos to outdated processes and tools, understaffed or underskilled DevOps teams and lack of enabling technology for containerization and automation.

These challenges also need to be overcome in order to take full advantage of today’s technology to drive innovation, business transformation and the competitive edge that can help businesses both survive and thrive in today’s economy.
June 22, 2020
The EU’s Plans to Build a Wall Around GDPR-Protected Data

An ambitious German- and French-lead European Union (EU) initiative could wrestle tighter management, and eventually, control of data from commercial cloud providers.

The project, dubbed as “Gaia-X,” is also intended to offer firewall-like protection for data sources from the EU. The initiative could have repercussions on how DevOps teams from outside of the EU manage data from European users, as well as from operations they might have that are physically based in EU member states.

Without specifically citing U.S. cloud giants such as Amazon Web Services (AWS), Google Cloud Platform (GCP) or Microsoft Azure, German and French government officials said the initiative will allow organizations’ cloud data to benefit from EU sovereignty and security. Bruno Le Maire, France’s minister of the economy and finance (Ministre de l’Économie et des Finances), said during a televised Franco-German conference last week, for example, that Gaia-X would offer significantly more data protection for data stored on cloud services from EU organizations and users.

Despite how General Data Protection Regulation (GDPR) mandates rules EU and international firms with user data from EU member state sources must follow—to avoid the risk of heavy fines and other penalties—the EU still lacks sovereignty in the application of GDPR, Le Maire said. Data stored on a U.S. cloud service provider’s server in the U.S. or overseas, for example, is still accessible by U.S. law enforcement officials in some cases under the Clarifying Lawful Overseas Use of Data (CLOUD) Act.

Without disclosing technical details about the kinds of cloud services Gaia-X might offer, the initiative will adhere to four principles: “openness, interoperability, transparency and trust,” Le Maire said.

“We are not China. We are not the United States—we are European countries with our own values,” Le Maire said. “We have our own economic interests that we want to defend.”

Over 20 organizations will form Gaia-X, including AtosBosch, Deutsche Telekom, SAP and Siemens. A prototype of the service should be available by end of year. While specific cloud services the organization will offer remains undisclosed, government officials announcing Gaia-X said it will offer artificial intelligence (AI)-aided meta analysis of data in such sectors as healthcare and smart city management. The use of AI services for data needs would also meet stringent privacy and ethical programming mandates, the officials said.

In a statement, the German Federal Ministry for Economic Affairs and Energy (Bundesministeriums für Wirtschaft und Energie) said:

“Predominant data silos, a lack of standards and the limited transparency of data infrastructure offers are today major obstacles to the application of artificial intelligence. To overcome these obstacles would be very costly and for this reason, the diverse know-how available in Europe is not pooled and used efficiently.”

Build That Wall

While created to ostensibly protect user data from the European member states and to enforce non-compliance with major penalties, accessibility by governmental authorities outside of the EU, for example, can remain outside of EU control. As mentioned above, for example, data storage that is ostensibly GDPR-compliant yet is on a physical AWS or another cloud provider’s server remains subject to access by U.S. law enforcement in certain circumstances.

GDPR compliance is thus often considered a starting point for EU data sovereignty. In many ways, the EU’s initiative, pending the final details about Gaia-X’s infrastructure and the services it will offer, will serve as a firewall built to protect EU.

Clive Longbottom, an analyst for Quocirca, agreed.

“By creating a total data platform that is GDPR compliant, uses have the choice: build directly on that platform and not have to jump through hoops to prove compliance,” Longbottom said. “Those who choose not to, or due to geographical position, cannot use the platform directly can export data into Gaia-X and only have to prove compliance for that part of the platform outside of the environment. So, yes, EU data can be completely airlocked into Gaia-X – or can just make life a lot easier for users.”

Instead of serving as an alternative to AWS, Gaia-X, based on the information the EU officials have communicated so far, is more of a data handling environment that may just have its own cloud components, Longbottom said.

The idea, based on the available information “is to present an environment where data can be handled firmly within the needs of GDPR,” Longbottom said. “Now, there are fundamental difficulties around this, such as with data caching in the network, but we won’t let inconvenient realities get in the way of political perceptions.”

The Gaia-X is thus “really meant to be a platform for data exchange that meets stringent requirements within the EU,” Longbottom said. “I would hazard that it will include those working outside of the EU that want to deal with countries, companies and entities within the EU, accepting data feeds from pretty much any cloud platform. It will probably be that once the data is accepted into the Gaia-X environment, it will then be deemed to be secure under GDPR—and that will not make it necessarily secure under GDPR end-to-end.”

Cloud Alternative

A main selling point of the project is that once data adheres to Gaia-X compliance, DevOps could, in theory, benefit from more seamless data transfers between parties within the environment, as well as transparency about how and where it is stored.

“Gaia-X is a good idea that will make life easier for EU members to share data across a trusted environment and allow externals to feed data into a known, highly standardized environment where they then do not have to prove GDPR compliance across Gaia-X itself,” Longbottom said.

However, whether or not Gaia-X might one day compete against AWS, GCP or Azure remains to be seen. “If the EU can get more cloud platform vendors to join in and show how their platforms are GDPR compliant from the ground up, more EU companies will want to use such platforms where GDPR compliance is a given,” Longbottom said. “Meanwhile, most will stick with the big public platforms and use Gaia-X as a downstream GDPR data handling environment.”

June 19, 2020
Survey Shows Accelerated Shift to Cloud, With Caveats

A survey of 250 IT leaders published by Snow Software, a provider of software asset management software, finds 91% are changing their cloud strategy in the wake of the economic downturn brought on by the COVID-19 pandemic.

The survey also finds twice as many respondents report they are accelerating cloud migration (45%) and digital transformation (41%) projects versus those putting cloud migration (22%) or digital transformation (21%) initiatives on hold.

At the same time, however, nearly a third of respondents (32%) said they are asking their cloud vendors for extended payment terms, while 31% are renegotiating their cloud contracts. Around 10% of respondents indicated that they would not be able to pay their cloud bills last month.

More than three-quarters of respondents (76%) said they have increased their use of cloud platforms such as Amazon Web Services (AWS), Microsoft Azure and even private clouds.

In addition, more than half of respondents (55%) noted an increase in the use of collaboration tools such as Slack, Teams or Google Chat, while 52% said they have seen an increase in the use of cloud-based videoconferencing software such as Zoom, Cisco WebEx or GoToMeeting.

Overall, 60% of IT leaders said they are continuing to increase cloud use.

Jesse Stockall, chief architect for cloud management for Snow Software, said the results show the cloud has played a critical role in enabling employees to work from home. In many cases, the first thing to be shifted to the cloud was application testing environments. With development teams working from home the only way to effectively set up a testing environment is in the cloud.

At the same time, Stockall said entire applications have been lifted and shifted to the cloud using containers. Rather than refactoring these applications, IT teams decided to encapsulate entire applications in a container that could be deployed on any virtual machine. IT teams then will spend the next few months converting those monolithic applications into a series of microservices that can run natively on cloud computing platforms, he noted.

Stockall expects that approach to lifting and shifting applications first and modernizing them second to accelerate as more organizations conclude working remotely is now part of the new normal. Employees may soon head back into the office, but many more of them increasingly will access applications from home. Business and IT leaders are also unsure whether a second wave of the pandemic might make local offices and data center once again inaccessible, he added.

Many IT organizations will also be replacing legacy virtual private networks (VPNs) with software-defined wide area networks (SD-WANs) to make cloud applications more accessible, Stockall, noted.

The COVID-19 pandemic may prove to be a seminal moment in the history of cloud computing; while cloud computing has been around more than a decade, the bulk of applications still run on-premises. However, once many local data centers became inaccessible overnight, strategies that called for either replacing or modernizing those applications are being accelerated.

It’s not clear how many of those on-premises applications might be retired altogether. Whatever the outcome, there’s never been more focus on where application code is being built and deployed.

June 17, 2020
AWS Aligns With Slack to Foster Dev Team Collaboration

Amazon Web Services (AWS) and Slack Technologies have formed an alliance through which they are moving to transform the way development teams collaborate.

Under the terms of the multi-year agreement, Slack will migrate voice and video calls to the Amazon Chime real-time communications service.

In addition, AWS and Slack are integrating Amazon AppFlow integration with Slack, which enables data to be transferred securely between Slack and AWS services such as Amazon Simple Storage Service (Amazon S3) and Amazon Redshift. The two companies are also promising to make it possible to transfer data bi-directionally between multiple Slack channels and AWS services in a single flow.

AWS and Slack have also integrated the AWS Key Management Service with Slack Enterprise Key Management (EKM) to distribute and control cryptographic keys. That capability builds on an instance of EKM for Slack’s Workflow Builder automation tool that was released last month.

Finally, the two companies are committing to make the AWS Chatbot service accessible from directly within Slack.

Slack, which already makes extensive use of the AWS cloud, has emerged as a de facto collaboration tool within many organizations that have embraced best DevOps practices. Eron Kelly, head of product marketing for AWS, said this alliance will make it easier for development teams to employ a wide range of communications tools at scale.

Many DevOps teams already rely on Slack Calls to launch video and voice calls whenever a subject being discussed using text messages requires a deeper level of interaction. As reliance on Slack Calls increases, the software development kit (SDK) for the AWS Chime service that Slack will invoke will ensure the quality of the video and voice calls, said Kelly.

In many ways, DevOps processes revolve around a mix of asynchronous and synchronous communications. The challenge has been to find a way to enable DevOps teams to use those tools in a way that enhances rather than detracts from productivity. Managing multiple Slack communications channels can easily become overwhelming, especially if developers are working on multiple projects at the same time.

Ideally, DevOps teams will eventually become more adept at determining, for example, what messages, such as status updates, are best delivered asynchronously versus urgent requests that need to be made via a communications medium such as Slack.

In the meantime, the COVID-19 pandemic has clearly increased reliance on communications services delivered via the cloud. With most members of DevOps teams working from home, tools such as Slack have become a virtual substitute for walking over to the next cube in an office to resolve an issue. Once development teams return to the office, it will be interesting to see to what degree tools such as Slack have become the default means of communication, even with fellow employees who may be only a few feet away. In fact, such tools may play a critical role in helping organizations adhere to social distancing policies even after employees return to the office.

As philosopher Marshall McLuhan once observed, the medium is the message. Today, however, those messages increasingly are being delivered within a stream of real-time communications that is becoming more challenging to manage.

June 12, 2020