Send Docs Feedback

Differences between Operations Manager and interactive Edge installs

Edge for Private Cloud v. 4.17.05

One of the major differences between an Ops Manager and an interactive Edge install is how you configure Edge components. When using Ops Manager, you typically do not log in to individual servers to make configuration changes. Instead, you configure servers through the Ops Manager. The Ops Manager lets you:

  • Import the Edge Pivotal tile
  • Configure an Edge installation
  • Specify the Edge settings such as the system admin's username/password
  • Specify the Edge license file
  • Select the Edge components to install 

After instaling Edge, use the Ops Manager to manage and modify the installation configurations. For example, the Router and Message Processor have predefined limits for the size of request/response headers. If you want to change those value on a Router in an interactive Edge installation, you log in to the Router server to change the values, then restart the Router. If you have multiple Routers, you have to repeat that process on every Router server.

With Ops Manager, you do not have to log in or access individual servers. Instead, you use the Ops Manager to change the property value in one place, then apply that change to all Routers in the Edge installation. 

Apigee has enabled the Ops Manager to support most configuration tasks that you can perform in an interactive Edge installation. However, you might come across a task that cannot be performed in the Ops Manager. Please let Apigee know if this occurs.

Configuring the Developer Services portal post installation 

At installation time, the Developer Services portal is associated with the VALIDATE organization created by the Edge installer. The VALIDATE org is used by the Apigee Validation Errand and to test that you can log in to the Edge UI. 

Do not use the VALIDATE org to develop your APIs. Provisioning organizations describes how to create an organization for development.

After you provision your own organization, you must log in to the portal and associate it with that organization. You cannot perform that configuration in the Ops Manager but in the portal UI. 

New features for Edge 4.17.05

This release of the Edge Installer for Pivotal Cloud Foundry contains the following new features:

Functional differences

The following table describes additional differences between an interactive install and an Ops Manager install:

Difference

説明

No config files needed.

Use the Ops Manager to specify installation and configuration information. You do not have to create separate config files.  

Enable Monetization only after installing Edge. 

You must install Edge first, and then enable Monetization and apply that change to the Edge installation. You cannot enable Monetization at the same time as you install Edge.

Multiple data centers not supported.

The release supports the installation of a single data center only.

You can only specify the number servers for the Router and Message Processor components.

In this release, Edge is configured to create two Router servers and two Message Processor servers by default. However, you can increase or decrease that number at install time or later.

The number servers for all other Edge components is fixed:

  • Management Server: two

  • Zookeeper: three

  • Cassandra: six

  • Qpid, Postgres:two

  • Influxdb (for Edge monitor): one

  • BaaS Portal: one

  • BaaS Stack (Usergrid): two

  • ElasticSearch (for BaaS): three

Note that there are no dedicated servers for the Edge UI and OpenLDAP components. Each server hosting the Management Server also hosts an instance of the Edge UI and of OpenLDAP.

No need to enable Cassandra authentication.

The Cassandra servers created during the install are not publicly accessible and therefore do not require you to enable authentication.

The two Postgres servers are configured as master/standby servers.

You must use Postgres master/standby configuration in this release.

Do not have to open specific ports on the servers.

In an interactive Edge installation, you have to ensure that the necessary ports are open on each server as described in Edge port requirements.  

With Ops Manager, locking down individual ports is not a requirement and the platform ensures that the VMs are able to communicate over the necessary ports.

Known issues

See the release notes at 4.17.05 - Edge for Private Cloud release notes.

 

Help or comments?