There’s a new survey out from the Cloud Foundry Foundation, looking at the users of Cloud Foundry. Here’s some highlights and notes:
- Another ClearPath joint, n=735.
- It’s important to keep in mind that this is covers all distress of Cloud Foundry, including open source (no vendor involved).
- “The percentage of user respondents who require over three months
per app drops from 51 percent to 18 percent after deploying Cloud Foundry Application Runtime”
- “…while the percentage of user respondents who require less than a week climbs from 16 percent to 46 percent.”
- “Nearly half (49 percent) of Cloud Foundry Application Runtime users are large enterprises ($1+ billion annual revenue).”
- This chart is hard to read, but it shows a reduction in time to deploy across various time periods:
- Uptake is early, but there are definitely mature users: “A plurality of Cloud Foundry Application Runtime users (61 percent) describe their deployments as somewhere in the early stages—trial, PoC, evaluation, or a partial integration into specific business units. Meanwhile, 39 percent have deployed Cloud Foundry Application Runtime more broadly across their company, from total integration in specific business groups to company-wide deployment.”
- “Comcast, for example has more than 1500 developers using Cloud Foundry Application Runtime daily. Home Depot reports more than 2500 developers.”
- “Comcast has seen between 50 percent and 75 percent improvement in productivity.”
- “Half of Cloud Foundry Application Runtime users are currently using containers, such as Docker or rkt, with another 35 percent evaluating or deploying containers.”
- Container management – there’s a wide variety of tools that people use for container orchestration, including DIY (14%). There’s a lot of interest in having CF do it: “Nearly three-quarters (71 percent) of Cloud Foundry Application Runtime users currently using or evaluating containers are interested in adding container orchestration and management to their Cloud Foundry Application Runtime environment.” Hence, validating the Cloud Foundry Container Runtime.
- Of course, the surveyed are already CF users, so they’re biased/driven by what they know.
- Almost half of respondents say that getting started with CF. But people end up liking it: “An overwhelming majority of users (83 percent) would recommend Cloud Foundry Application Runtime to a colleague, including 60 percent who would do so strongly.”
- “As more companies roll out Cloud Foundry Application Runtime more broadly, the footprint continues to grow. Currently, 46 percent of users have more than 10 apps deployed on Cloud Foundry Application Runtime, including 18 percent with over 100 (and eight percent with over 500).” 4% have over 1,000 apps.
- CF’s uses: “The primary use is for microservices (54 percent), followed by websites (38 percent), internal business applications (31 percent), Software-as-a-Service (SaaS) (27 percent) and legacy software (eight percent).”
- Validating multi-cloud: “60 percent say this is very important, and another 30 percent describe it as somewhat important.” Meanwhile, 53% are using more than one type of IaaS.
I assume this is across distros, and including use of just the ope source stack,
Source: Cloud Foundry adds native Kubernetes support for running containers, TechCrunch
451 Research’s data points suggest that some workloads are likely to remain on private cloud regardless of any disruptor’s attack. And even with hungry cloud providers eyeing private workloads, growth is likely to continue across all cloud models, not just public cloud.
Whole bunch of survey numbers tryin’ figure out how many workloads will stay on private cloud.
Source: Private cloud: avoiding an existential crisis
Lots of growth, it’s all just public cloud, though.
Source: Public Cloud Doesn’t Dominate IT Quite Yet
“We’re seeing a big trend among customers to move cloud stacks inside customer’s data center for security, performance and governance,” Wang told TechCrunch.
There’s not really any qualitative (market share, penetration, or surveys – all pretty easy to lmgtfy) bits here, but I’d take it more as a slightly eyebrow raising thing along the lines of “if even TechCrunch wiffs out private cloud, maybe there’s some fire there.”
Plus, analyst quotes.
Some BOM’ing of Azure Stack:
Azure Stack is made of two basic components, the underlying infrastructure that customers purchase from one of Microsoft’s certified partners (initially Dell EMC, HPE and Lenovo) and software that is licensed from Microsoft.The software includes basic IaaS functions that make up a cloud, such as virtual machines, storage and virtual networking. Azure Stack includes some platform-as-a-service (PaaS) application-development features including the Azure Container Service and Microsoft’s Azure Functions serverless computing software, plus MySQL and SQL Server support. It comes with Azure Active Directory for user authentication.Customers also have access to a wide range of third-party apps from the Azure Marketplace, including OS images from companies like Red Hat and SuSE, and templates that can be installed to run programs like Cloud Foundry, Kubernetes and Mesosphere.On the hardware side, Azure Stack runs on a hyperconverged infrastructure stack that Microsoft and its hardware vendors have certified. The smallest production-level Azure Stack deployment is a four-server rack with three physical switches and a lifecycle management server host. Individual racks can scale up to 12 servers, and eventually, multiple racks can be scaled together. Dell EMC, HPE and Lenovo are initial launch partners. Cisco plans to offer a certified Azure Stack platform based on its UCS hardware line by the end of 2017 and Huawei will roll out Azure Stack support by the end of 2018.IDC Data Center Networking Research Analyst Brad Casemore says he believes customers will need to run at least a 10 Gigabit Ethernet cabling with dual-port mixing. Converged network interface cards, support for BGP and data center bridging are important too. Microsoft estimates that a full-sized, 12-rack server unit of Azure Stack can supply about 400 virtual machines with 2 CPUs and 7 GB of RAM, with resiliency.
And Lydia explains the “people want private cloud ¯_(ツ)_/¯” angle:
“This is definitely a plus in the Microsoft portfolio,” says Gartner VP and Distinguished Analyst Lydia Leong, but she says it’s not right for every customer. “I don’t think this is a fundamental game-changer in the dynamics of the IaaS market,” she notes, but “this is going to be another thing to compel Microsoft-centric organizations to use Azure.”
Leong expects this could be beneficial for customers who want to use Azure but some reason such as regulations, data sensitivity, or location of data prevents them from using the public cloud. If a customer has sensitive data they’re not willing to put in the public cloud, they could deploy Azure Stack behind their firewall to process data, then relatively easily interact with applications and data in the public cloud.
Source: “Azure Stack: Microsoft’s private-cloud platform and what IT pros need to know about it,” Brandon Butler
Good round-up of AWS’s private cloud stuff:
- AWS added on-premises support to its CodeDeploy continuous-delivery service in 2015.
- AWS introduced the Snowball storage server companies could use to copy data and then ship it to the cloud in 2015.
- AWS added on-premises support to its EC2 Run Command tool for running shell scripts on many machines at once in 2016.
- AWS unveiled the Snowmobile truck for copying even larger supplies of data and then hauling it off to Amazon in 2016.
- This past November AWS released a container image of its Amazon Linux server operating system for use on corporate servers.
Source: AWS talking with VMware about building on-premises software: report
“Managed Pivotal Cloud Foundry is Rackspace’s first step into the managed platform space, as we move up the stack to solutions that customers want our help with,” wrote Brannon Lacey, vice president of applications and platforms at Rackspace, in today’s announcement. “It is a solution that helps customers get up and running on Pivotal Cloud Foundry quickly and stay up and running, with operational support and proactive monitoring. This way, in-house teams can focus on innovation and getting out to market quickly while Rackspace handles the backend.”
Source: Rackspace partners with Pivotal to launch managed services for Cloud Foundry, Frederic Lardinois, TechCrunch
Pivotal is at the epicenter of how enormous companies rediscover the art of software development.
Source: Michael Dell Says Public Cloud is Important But It’s Not Everything
While this is sort of a bummer story for Pivotal (we’d like to have this account), it has a good profile of American and their needs in it. All of which are representative of other large organizations, e.g.:
- Application types: “The first result is that the airline will migrate to the IBM Cloud some of its critical applications, including the main website, its customer-facing mobile app and its global network of check-in kiosks. Other workloads and tools, such as the company’s Cargo customer website, also will be moved to the IBM Cloud.”
- Managed data-centers/cloud: “The airline will be able to utilize the global footprint of IBM Cloud, which consists of more than 50 data centers in 17 countries, in addition to a wide range of application development capabilities.”
- Long-term planning: “We wanted to make sure that the cloud provider would be using Cloud Foundry and open-source technologies so we don’t get locked in by proprietary solutions,” Grubbs said. “We also wanted a partner that would offer us the agility to innovate at the organizational and process levels and have deep industry expertise with security at the core.”
- We want to do all the new meat-ware: “As part of this process, American will work with IBM Global Services to use IBM’s Garage Methodology of creating applications through a micro-services architecture, design thinking, agile methodology, DevOps and lean development, the company said.”
- Legacy, it’s how you got here: “IBM Cloud will help enable developers to build and change application functionalities for the airline’s customers. These customer-facing systems will be on the IBM Public Cloud, while American will maintain backend connectivity to other on-premise legacy and third-party systems, for true Hybrid Cloud functionality.”
- There’s a lot going on: “American Airlines and its subsidiary, American Eagle, offer an average of 6,700 flights per day to about 350 destinations in more than 50 countries. American has hubs in Charlotte, Chicago, Dallas/Fort Worth, Los Angeles, Miami, New York, Philadelphia, Phoenix and Washington, D.C.”
Source: American Airlines Heads for a New Cloud with IBM