We'll respond shortly.
The new Greenplum Database 188.8.131.52 sandbox has been released as an Amazon EC2 AMI in addition the VMware and Virtual Box formats. This post explains where to get it, what instances sizes to use, access setup, use of data sets, and related information.
In this post, Pivotal data engineers Amey Banarse and Qi Shao follow the recent announcement of Pivotal Greenplum’s new ability to query both on-premise and AWS S3 data. They cover a high level overview of the key technical scenarios, a deeper technical explanation of how it works, and a hands-on set of steps for getting started.
Today, Pivotal is announcing the release of Pivotal Greenplum 4.3.8. It features the ability to run one analytical query and return results for data that sits across both on-premise data warehouses and clouds, starting with AWS S3. Now business intelligence, data science, or advanced analytical workloads can run in near-real-time across hybrid clouds, breaking down silos, and opening up a new world of possibilities.
One of the biggest announcements coming out of Google Cloud Platform’s Next Conference last week was about Apple moving workloads from AWS, but there is much more to the story than the headline. The world of poly-cloud is making big moves from financial justifications to customer moves to product developments. We cover it in this week’s BUILD Newsletter.
The Build Newsletter is shorter and more focused this week. In it, we cover the latest news in the cloud native platform arena—from innovations and talent to vendor and analyst updates. This newsletter captures the latest, most important happenings in the space from Pivotal’s perspective.
During the Cloud Foundry Summit 2015, Pivotal’s David Sabeti and IBM’s Michael Maximilien reviewed the latest Cloud Foundry Service Broker Updates. These new features offer new opportunities to provision and customize services which were previously difficult to implement. Recently, the Cloud Foundry Service Broker API was updated to version 2.7, and some of the experimental API features went from experimental to GA.
This post describes how to deploy a BIND 9 DNS server to Amazon AWS using bosh-init, a command-line BOSH tool that enables the deployment of VMs without requiring a Director VM. This blog post is the second of a series; it picks up where the previous one, How to Create a BOSH Release of a DNS Server, left off. Previously we described how to create a BOSH release (i.e. a BOSH software package) of the BIND 9 DNS server and deploy the server to VirtualBox via BOSH Lite.
Whilst you have always been able to deploy Cloud Foundry onto Amazon Web Services using BOSH—you needed good BOSH skills to make it happen. With version 1.4 of Pivotal Cloud Foundry, this is now all handled by the Ops Manager.
Pivotal's Cote reviews the big impact the small licensing changes we made last week had for Pivotal Cloud Foundry customers, allowing them to move between private clouds and Pivotal Web Services without incurring extra costs. Equally importantly, Pivotal Cloud Foundry customers now have all types of cloud at their disposal, helping them get the multi-cloud capabilities: they can run in full-on, public cloud multi-tenant mode, single-tenant “public cloud” in an AWS VPC, or “private cloud” on their own hardware. These changes allow customers a greater range of optionality for their infrastructure development and deployment choices, and speeding the time to deliver apps.
In the Cloud Operations team at Pivotal, we value documentation that is easy to discover. One method we use at Pivotal to ensure the availability of documentation is is to make it visible within the normal workflow—or as we view it discoverable in-context. What follows is one example of the value of in-context documentation, and how we used that idea to better manage our Elastic IPs within our Amazon Web Services accounts.