REST APIs for 24.2.20 and 24.2.10

The VEN Update API (PUT [api-version][ven-href]) allows you to mark a VEN as either suspended or unsuspended in the PCE. It does not, however, actually suspend or unsuspend the VEN.

To suspend a VEN, use the illumio-ven-ctl command-line tool, which isolates a VEN on a workload so that you can troubleshoot issues and determine if the VEN is the cause of any anomalous behavior.

When you suspend a VEN, the VEN informs the PCE that it is in suspended mode.

However, if the PCE does not receive this notification, you must mark the VEN as "Suspended" in the PCE web console (select the VEN and click Edit ), or you can use this API to mark the VEN as suspended.

When you don't mark the VEN as suspended in the PCE, the PCE assumes that the workload is offline and removes it from the policy after one hour. When you mark the VEN as suspended, that VEN’s workload is still included in the policy of other workloads.

When a VEN is suspended:

When a VEN is unsuspended:

VEN upgrade APIs allow you to specify an array of VEN HREFs to upgrade to a specific version instead of a list of agent ID's.

Rules when validating with the VEN upgrade APIs are as follows:

In addition to the page in the PCE web console that lists all VENs and shows the details of a single VEN, there is a Public Experimental API for getting VEN collections and VEN instances. Other new APIs support VEN filtering in the PCE web console and update and unpair VENs.

release_ven_types

{
	"$schema": "hp://json-schema.org/draft-04/schema#",
	"description": "Supported ven types in this release",
	"type": "array",
	"items": {
		"type": "string",
			"enum": ["server", "endpoint"]
		}
}

The new common schema release_ven_types is introduced to show ven_types for each release and to filter releases by ven_type.

Previously, the ven_type was not stored for the release, and database records looked as follows:

With the property ven_type added, the database records are expanded with an additional ven_types column:

Note that in release 22.5.1, the code supports the type "server+endpont". However, Centos (Linux) supports a server-only VEN image, MasOS supports an endpoint-only image, and Windows supports both server and endpoint:

When a user opens the list of release images via UI and looks for the type server + endpoint, only the Windows image will appear as a complete match.

To fix this issue, the ven_type is now based on release and distribution: