The big takeaway is that small increases in IT budgets are the new normal. Unlike previous recoveries, we have not seen a large jump in IT spending over the past five years. So if a CIO is only seeing a two or three percent increase this year, he or she should understand that is pretty much in line with other companies. See more guidance charts on IT priorities, n=190.

The new version of Pivotal Cloud Foundry (“PCF” as folks like to say) is out. It has awhole slew of updates across the board. My selective highlights: Google Cloud & Azure support, so you’re all multi-cloud ready (still with OpenStack, VMware, and AWS support). Will run 250,000 containers concurrently; in addition to scaling based on CPU usage, you can now auto-scale on HTTP Latency and HTTP Throughput. Updates to Spring Cloud, Zipkin, and Spring Boot Actuators for diagnostic stuff.

The new version of Pivotal Cloud Foundry (“PCF” as folks like to say) is out. It has awhole slew of updates across the board. My selective highlights: Google Cloud & Azure support, so you’re all multi-cloud ready (still with OpenStack, VMware, and AWS support). Will run 250,000 containers concurrently; in addition to scaling based on CPU usage, you can now auto-scale on HTTP Latency and HTTP Throughput. Updates to Spring Cloud, Zipkin, and Spring Boot Actuators for diagnostic stuff.

The new version of Pivotal Cloud Foundry (“PCF” as folks like to say) is out. It has awhole slew of updates across the board. My selective highlights: Google Cloud & Azure support, so you’re all multi-cloud ready (still with OpenStack, VMware, and AWS support). Will run 250,000 containers concurrently; in addition to scaling based on CPU usage, you can now auto-scale on HTTP Latency and HTTP Throughput. Updates to Spring Cloud, Zipkin, and Spring Boot Actuators for diagnostic stuff.

The new version of Pivotal Cloud Foundry (“PCF” as folks like to say) is out. It has awhole slew of updates across the board. My selective highlights: Google Cloud & Azure support, so you’re all multi-cloud ready (still with OpenStack, VMware, and AWS support). Will run 250,000 containers concurrently; in addition to scaling based on CPU usage, you can now auto-scale on HTTP Latency and HTTP Throughput. Updates to Spring Cloud, Zipkin, and Spring Boot Actuators for diagnostic stuff.

The new version of Pivotal Cloud Foundry (“PCF” as folks like to say) is out. It has awhole slew of updates across the board. My selective highlights: Google Cloud & Azure support, so you’re all multi-cloud ready (still with OpenStack, VMware, and AWS support). Will run 250,000 containers concurrently; in addition to scaling based on CPU usage, you can now auto-scale on HTTP Latency and HTTP Throughput. Updates to Spring Cloud, Zipkin, and Spring Boot Actuators for diagnostic stuff.

The new version of Pivotal Cloud Foundry (“PCF” as folks like to say) is out. It has awhole slew of updates across the board. My selective highlights: Google Cloud & Azure support, so you’re all multi-cloud ready (still with OpenStack, VMware, and AWS support). Will run 250,000 containers concurrently; in addition to scaling based on CPU usage, you can now auto-scale on HTTP Latency and HTTP Throughput. Updates to Spring Cloud, Zipkin, and Spring Boot Actuators for diagnostic stuff.

The new version of Pivotal Cloud Foundry (“PCF” as folks like to say) is out. It has awhole slew of updates across the board. My selective highlights: Google Cloud & Azure support, so you’re all multi-cloud ready (still with OpenStack, VMware, and AWS support). Will run 250,000 containers concurrently; in addition to scaling based on CPU usage, you can now auto-scale on HTTP Latency and HTTP Throughput. Updates to Spring Cloud, Zipkin, and Spring Boot Actuators for diagnostic stuff.

When we're talking with customers about the value that Puppet brings to them, invariably we talk about the future, and the future in their mind in some ways includes containers. There's a lot experimentation going on. There's a lot of Docker work being done and container work being done, Kubernetes work being done on their laptops. The conversations we have with them is how does Puppet help you bring it into production, into mission-critical production?

When we're talking with customers about the value that Puppet brings to them, invariably we talk about the future, and the future in their mind in some ways includes containers. There's a lot experimentation going on. There's a lot of Docker work being done and container work being done, Kubernetes work being done on their laptops. The conversations we have with them is how does Puppet help you bring it into production, into mission-critical production?