Pivotal Cloud Foundry

Announcing the Latest Apigee Edge Installer for PCF

Now available with offline installation capability and more

With proven product-level integrations, Apigee and Pivotal Cloud Foundry (PCF) have helped enterprises boost the consumption of their applications and microservices, modernize legacy systems, and chart a smoother path to cloud migration.

Today we’re excited to strengthen our partnership even more by announcing the general availability of Apigee Edge BOSH Installer for PCF for our Private Cloud 4.18.05 version. This is the latest BOSH installer that Apigee has released and marks another important step in our relationship with Pivotal.  

Operators who deploy PCF use BOSH to install, manage, and maintain it (BOSH is an open-source project that unifies release engineering, deployment, and lifecycle management of cloud software). The latest installer makes it simple for operators to do the same for Apigee Edge Private Cloud 4.18.05. The new release is built to further simplify user experience and provide self-service functionality. 

Offline installation

A key feature of the new release is offline install, which enables operators to install Apigee Edge VMs even without internet connectivity. The new installer enables you to specify a custom repo URL so that it can resolve CentOS and EPEL dependencies required to install Apigee Edge. You can find more details here.

Latest CentOS 7 stem cells support

This release also supports the latest CentOS 7 stem cells (version 3586). Stem cells are customized operating system images containing the filesystem for BOSH-managed VMs.

PCF 2.1 and 2.2 support

The latest release also supports PCF 2.1 and 2.2. Customers running 4.17.09 Edge installer tile on PCF 1.10 or 1.11 should first upgrade to PCF 2.1 or 2.2 and then upgrade the tile to 18.05.01. Details of the upgrade procedure can be found here.

JSON Web Tokens (JWT)

The JWT policies enable Edge API proxies to generate, validate, and decode JWT tokens, which are commonly used to share claims or assertions between connected applications.

Unified Apigee Edge experience (beta)

The unified Apigee Edge experience, now in beta, improves API lifecycle management, from API design and development to publishing.

Postgres upgrades to latest version (9.6)

Postgres 9.6 enables parallel query processing and improves analytics performance.

Give it a try!

The Apigee Edge Installer for Pivotal CF is available as a tile on the Pivotal Network.

This new release can simplify your Apigee Edge deployment, management, and maintenance experience (please note that we've retired the monitoring dashboard and API BaaS in this latest BOSH release). 

All you need is an account on the Pivotal Network (to download the tile) and your Apigee Edge license file (you can get it from your Apigee account team). Please check out  the full documentation and release notes, and visit Apigee Community with any questions or feedback.

 

Apigee for PCF: Modernize Apps Securely and Boost Consumption

There’s immense pressure these days on CIOs to keep up with ever-changing business needs. To move faster and more efficiently, technology teams have had to rethink their application strategies by modernizing legacy applications, embracing microservices-based architectures, and leveraging cloud technologies.

There are two key aspects of app modernization: re-architecting the monolith without affecting business continuity and enabling app consumption. Apigee, in collaboration with Pivotal using Pivotal Cloud Foundry (PCF), has helped many enterprises make this transition successfully and today, we’re proud to announce that Apigee has received the 2018 Pivotal Partner Award for “Consumption.” This award recognizes how Apigee helped several companies increase the usage of their applications built on PCF.

“Apigee Edge can be deployed alongside Pivotal Cloud Foundry as a fully integrated application service. Operating a local API solution has been instrumental in accelerating adoption of applications deployed to PCF,” said Nima Badiey, head of technology ecosystem at Pivotal Software, Inc. “Our partnership with Apigee has been successful due to their leading-edge technology, a relentless focus on customer success, and strategic buy-in from customers fully invested in the journey to modernize their application portfolio.”

Modernizing apps while maintaining business continuity

Application modernization is a phased approach in which one or more components of the monolithic legacy apps are re-architected in sprints. Throughout the process, it’s critical to ensure that the customer experience isn’t degraded. Because Apigee and PCF are integrated at the product level, Apigee Edge can be deployed as a route service, intercepting every request at the edge of PCF. Deploying the Apigee facade ensures that the end requests are routed to the most appropriate target, so developer interface and business continuity are uninterrupted. Using Apigee for PCF, enterprises can:

  • Mitigate modernization risk with automated routing of API requests
  • Monitor performance and usage of both legacy and modern services
  • Secure services from cyber threats and traffic spikes

Increasing consumption of modern applications

Modernized apps are composed of microservices that need to be managed, secured, and made discoverable for external consumption. This makes API management an essential capability that ensures consistent control, security, and visibility of microservices. Enterprises building applications on PCF can leverage the Apigee Edge API management platform to:

  • Manage the entire API lifecycle from design through security
  • Make services discoverable through a developer portal
  • Monitor performance and usage of services
  • Secure APIs from cyber threats and traffic spikes

We’re proud of the work we’ve done with PCF and look forward to engaging with many more enterprises in their digital journey.

Demo: Apigee Integrations for Pivotal Cloud Foundry

We recently announced the release of version 3.0.0 of Apigee Service Broker for Pivotal Cloud Foundry to ensure that the Apigee Service Broker stays up to date and continues to provide a seamless user experience.

Prior to this release, the Apigee Service Broker for Pivotal CF supported two different plans: the org plan and the microgateway plan. In the latest version, we’ve included something new—a microgateway-coresident plan—for deploying the microgateway inside Cloud Foundry apps to provide integrated API management.

In this detailed demo, we help you leverage our integrations with PCF. Check it out!

 

Apigee Edge Service Broker 3.0.0 for Pivotal CF is here!

We’re excited to announce the general availability of Apigee Microgateway for Pivotal Cloud Foundry, a new model for deploying a microgateway inside Cloud Foundry apps to provide integrated API management for microservices.

Over the past couple years, Apigee has delivered native integrations with both Pivotal Cloud Foundry (Pivotal CF) and Open Source Cloud Foundry (CF) that provide app developers with simple, powerful API management services via the Apigee Service Broker.

This service broker has enabled Pivotal CF and CF developers to, in a few simple steps, meet their needs with Apigee Edge, an enterprise-grade, purpose-built API management platform, and Apigee Microgateway, a secure, HTTP-based message processor for APIs that runs in close proximity to a desired application.

We released version 3.0.0 of Apigee Service Broker for Pivotal CF to ensure that the Apigee Service Broker stays up to date and continues to provide a seamless user experience,

Prior to this release, the Apigee Service Broker for Pivotal CF supported two different plans, the org plan and the microgateway plan. In the latest version, we’ve included a new plan for deploying the microgateway inside Cloud Foundry apps to provide integrated API management, adding microgateway-coresident to the list of available plans.

The org plan

The org plan takes advantage of Apigee Edge’s full feature set, including over 30 out-of-the-box policies that provide support for traffic management, caching, OAuth, threat protection, and transformation. Whether Apigee Edge is located on-premises or in the cloud, this plan enables developers to redirect traffic meant for their application to their Apigee Edge proxies.

Besides the complete Apigee Edge feature list, the org plan provides the following benefits and features:

  • An expanded ability to develop and edit proxies
  • Analytics provided across all API exposures
  • Consistent access to APIs by leveraging common infrastructure for API keys, tokens, and API product definitions
  • A single, self-service developer portal for internal and external API consumers

The microgateway plan

The microgateway plan leverages a microgateway through the use of a separate application within CF. This plan enables developers to build their applications around a scalable number of microgateway instances that support custom policies and basic Apigee Edge features without the need for redirecting traffic to the cloud.

Generally the microgateway plan provides the following benefits and features:

  • A single microgateway instance that’s responsible for multiple applications
  • A microgateway that scales as traffic increases
  • Less routing hops in comparison to the org plan
  • Analytics via a lightweight mechanism across all API exposures and use cases.
  • Consistent access to APIs by leveraging common infrastructure for API keys, tokens, and API product definitions
  • A single, self-service developer portal for internal and external API consumers.

The microgateway-coresident plan

The new microgateway-coresident plan leverages the meta buildpack through which the API runtime (the Apigee Microgateway) can be injected into the app container as a sidecar proxy using config/build constructs.

Apigee Microgateway’s light footprint deployment model makes it easy to co-reside within apps/microservices developed in CF.

Generally the coresident model provides the following benefits and features:

  • A lack of routing overhead, as Apigee Microgateway is embedded into the app container, making this option great for apps that have low latency requirements.
  • Automatic scaling, as Apigee Microgateway is part of the app container, so it participates in the app lifecycle process and scales up automatically as the app is scaled.
  • Consistent and pervasive protection to service implementations, as all ingress to the service runs through Apigee Microgateway.
  • Analytics across API exposures, as Apigee Microgateway provides a lightweight mechanism for capturing analytics for all use cases.
  • Consistent access to APIs by leveraging common infrastructure for API keys, tokens, and API product definitions.
  • A single, self-service developer portal for internal and external API consumers.

To make it easy for developers to work with the service broker, we built a series of Cloud Foundry CLI plugins. These make pushing, binding, and unbinding the Apigee service broker simpler and more streamlined.

The new capabilities eliminate friction for app developers and helps them enable API management for their microservices, so they can be secured, managed, and the relevant stakeholders get out-of-the-box, end-to-end visibility.

To try this new release, Pivotal CF app developers can download the service broker tile from the Pivotal Network. Please check out the full documentation and release notes, and visit Apigee Community with any questions or feedback.

API Management for Microservices

Apigee Microgateway for Pivotal Cloud Foundry is now in public beta

We’re excited to announce the public beta of Apigee Microgateway for Pivotal Cloud Foundry, a new model for deploying a microgateway inside Cloud Foundry apps to provide integrated API management for microservices.

Service broker

This new feature is delivered as service broker tile and deployed as a service inside of Cloud Foundry. It ships a new microgateway decorator buildpack, which leverages the meta buildpack through which the microservices API runtime (Apigee Microgateway) can be injected into the app container as a sidecar proxy (Learn more about buildpacks here).

Apigee Microgateway

Apigee Microgateway is a lightweight, secure, HTTP-based message processor designed especially for microservices. It processes requests and responses to and from backend services securely while asynchronously pushing valuable API execution data to Apigee Edge, where it’s consumed by the analytics system. The microgateway provides vital functions, including traffic management (protection from spikes in traffic and usage quota enforcement, for example), security (OAuth and API key validation) and API analytics.

Microgateway decorator buildpack

A meta buildpack is a Cloud Foundry buildpack that enables decomposition and reordering (execution order) of buildpacks. Using this approach, the provided microgateway decorator buildpack gets inserted inside the app container during the app build process and “decorates” or frontends all calls made to the underlying app or API.

Container sidecar 

The light footprint deployment model of the Apigee Microgateway makes it easy for it to be coresident within apps and microservices developed in Cloud Foundry as a container sidecar.

The coresident model provides the following general benefits and features:

  • No routing overhead Apigee Microgateway is embedded into the app container, so this option is great for apps that have low latency requirements.
  • Simplified lifecycle management and automatic scaling As Apigee Microgateway is part of the app container, it participates in the app lifecycle process and scales up automatically as the app is scaled.
  • Consistent and pervasive protection to service implementations All ingress to the service runs through Apigee Microgateway.
  • Analytics across all API exposures Consolidated analytics is valuable across all internal and external consumption patterns. Apigee Microgateway provides a lightweight mechanism for capturing analytics for all use cases.
  • Consistent access to APIs Common infrastructure is leveraged for API keys, tokens, and API product definitions.
  • Self service Internal and external API consumers are served through a single developer portal.

That’s all great, but we wanted to make it even simpler for Cloud Foundry app developers to start using this new feature. So we built a series of Cloud Foundry CLI plugins. These make pushing, binding, and unbinding the Apigee Service Broker more streamlined and easier to use.

The new capabilities eliminate the friction for app developers and makes it easy to enable API management for their microservices, so they can be secured, managed, and the relevant stakeholders get out-of-the-box, end-to-end visibility.

It’s easy to get started:

We’d love to hear from you; please reach out to us at the Apigee Community.

To learn more, read the Apigee eBook, "Maximizing Microservices."  

 

Announcing the Latest Apigee Edge Installer for Pivotal CF

Operators love BOSH, the open-source project that unifies release engineering, deployment, and lifecycle management of cloud software. It enables them to manage Apigee Edge and maintain and perform failure recovery and software updates to the platform the same way they manage Pivotal Cloud Foundry, with zero-to-minimal downtime.

Several customers appreciate this ability so much they have even told us they’re trying to mainstream BOSH for managing platforms and stacks other than Pivotal Cloud Foundry!

So of course we’re excited to announce the general availability of Apigee Edge BOSH Installer for Pivotal CF for our Private Cloud 17.09 version. This is the fourth BOSH installer that Apigee has released and marks another important step in our relationship with Pivotal.  

The new release is built around the theme of simplification and self service. It offers some key features, including:

  • SAML 2.0 support added to Edge, API BaaS, and the Developer Services portal
  • TLS self-service (beta)
  • The Developer Services portal now leverages nginx/Postgres.
  • New UI options and APIs available for configuring TLS

Apigee Edge now supports Security Assertion Markup Language (SAML) 2.0 as the authentication mechanism for Apigee Edge, API BaaS, and the Developer Services portal. SAML supports a single sign-on (SSO) environment. By using SAML, you can support SSO for Edge in addition to any other services that you provide and that also support SAML.

A full list of features is available here.

The Apigee Edge Installer for Pivotal CF is available as a tile on the Pivotal Network.

 


So give it a try! It’ll simplify your Apigee Edge deployment, management, and maintenance experience. All you need is an account on Pivotal Network (to download the tile) and your Apigee Edge license file (you can get that from your Apigee account team). Please check out  the full documentation and release notes, and visit Apigee Community with any questions or feedback.

Which App Modernization Pattern Is Right for You?

Webcast replay

App modernization projects are hard. Enterprises are looking to cloud-native platforms like Pivotal Cloud Foundry to run their applications, but they’re worried about the risks inherent to any replatforming effort.

Fortunately, several repeatable patterns of successful incremental migration have emerged.

In this webcast replay, Google Cloud’s Prithpal Bhogill and Pivotal’s Shaun Anderson discuss best practices for app modernization and securely and seamlessly routing traffic between legacy stacks and Pivotal Cloud Foundry.

This session covers:

  • How to decompose a monolith into logical business domains
  • How to approach modernization using domain driven design
  • How API management can be used to modernize applications while keeping the business running

 

 

Apigee Edge Service Broker 2.1 for PCF Is Here!

Over the past couple years, Apigee has delivered native integrations with Pivotal Cloud Foundry (PCF) that provide app developers access to simple, yet powerful API management services via the Apigee Service Broker.

This service broker has enabled PCF developers to, in a few simple steps, experience how their API needs can be met by Apigee Edge, an enterprise-grade, purpose-built API management platform, and Apigee Microgateway, a secure, HTTP-based message processor for APIs that runs in close proximity to a desired application.

Although the Apigee Service Broker has been available to PCF developers for sometime, we are constantly working to ensure that it stays up to date and continues to provide a good user experience.

As a result, we released version 2.1 of our Apigee Service Broker that includes the following updates:

  • Default protocol: Developers who want to run their proxy’s target endpoint through “https” no longer have go into the Edge UI post proxy creation and manually update the configuration from “http” to “https.” They can now specify their proxy’s target endpoint protocol at the time of proxy creation.
  • Tile metadata: The tile’s metadata version has been updated to provide better support for applications running across multiple availability zones.
  • Elastic runtime and ops manager: The Apigee Service Broker Tile now officially supports PCF Elastic Runtime and Ops Manager 1.7 through 1.11.

PCF app developers can download this service broker tile from the Pivotal Network. We encourage you to try this new tile. It’ll save you some time when providing API management for your apps and provide support for this in multiple PCF availability zones. All you need is an account on Pivotal Network (to download the tile) and an Apigee Edge account (to create the proxies).

Please check out the full documentation and release notes, and visit Apigee Community with any questions or feedback.

It's Here! The Latest Apigee Edge Private Cloud Installer for PCF

The Apigee Edge API platform has been integrated with Pivotal Cloud Foundry for some time now. This has been great because developers and operators alike benefit from pre-integrated API management and get out-of-the-box security, traffic management, and visibility into the APIs.

We haven’t stopped there, though. We’ve been working to streamline how operators install,  manage, and monitor Apigee Edge, so they can do so in the same way they are accustomed to for PCF.

So we’re excited to announce the general availability of Apigee Edge BOSH Installer for PCF for our Private Cloud 17.05 version. BOSH is an open-source project that unifies release engineering, deployment, and lifecycle management of cloud software. This is the third BOSH installer that Apigee has released and marks another important step in our relationship with Pivotal.  

Operators who deploy PCF use BOSH to install, manage, and maintain it. The latest installer makes it simple for operators to do the same for Apigee Edge 17.05.

The new release offers some key features, including:

  • API proxy URL rendering
  • Zero-downtime shared flows deployment
  • Simplified deletion of monetization data for an organization
  • Stricter input validation across all entities in an organization
  • Support for setting the API timeout duration used by Edge UI

 

A full list of features is available here.

The Apigee Edge Installer for PCF is delivered as a tile on the Pivotal Network.This tile provides a BOSH release to deploy Apigee Edge, an enterprise-grade, purpose-built, intelligent API management platform on your IaaS (Infrastructure as a Service). This makes it easy to perform monitoring, failure recovery, and software updates with little to no downtime.

 

 

We encourage you to try this new installer—it’ll simplify your Apigee Edge deployment, management, and maintenance experience. All you need is an account on Pivotal Network (to download the tile) and your Apigee Edge license file (you can get that from your Apigee account team). Please check out  the full documentationrelease notes, and this post for more, and visit Apigee Community with any questions or feedback.

Managing the Complexity of Microservices Deployments

Webcast replay

To rapidly deliver microservices to production, organizations are turning to infrastructure automation provided by a cloud-native platform, like Cloud Foundry. With a platform in place, every microservice team will have what they need to create a CI/CD pipeline that safely delivers applications to a production environment. The final ingredient for success is knowing the right patterns for connecting microservices together over HTTP using REST APIs.

In this webcast replay, Kenny Bastani from Pivotal and Prithpal Bhogill from Apigee dive into a reference architecture that demonstrates the patterns and practices for securely connecting microservices together using Apigee Edge integration for Pivotal Cloud Foundry.

This session covers:

  • basics for building cloud-native applications as microservices on Pivotal Cloud Foundry using Spring Boot and Spring Cloud Services
  • patterns and practices that are enabling small autonomous microservice teams to provision backing services for their applications
  • how to securely expose microservices over HTTP using Apigee Edge for PCF

 
To learn more, read the Apigee eBook, "Maximizing Microservices."