NSX-T Data Center REST API
ConsolidatedRealizedStatus (type)
{ "additionalProperties": false, "description": "Consolidated Realized Status of an intent object across enforcement points.", "extends": { "$ref": "AggregatePolicyRuntimeInfo }, "id": "ConsolidatedRealizedStatus", "module_id": "PolicyRealizedState", "properties": { "consolidated_status": { "$ref": "ConsolidatedStatus, "description": "Consolidated Realized Status across enforcement points.", "readonly": true, "title": "Consolidated Realized Status" }, "consolidated_status_per_enforcement_point": { "description": "List of Consolidated Realized Status per enforcement point.", "items": { "$ref": "ConsolidatedStatusPerEnforcementPoint }, "readonly": true, "title": "List of Consolidated Realized Status per Enforcement Point", "type": "array" }, "intent_path": { "description": "Intent path of object, forward slashes must be escaped using %2F.", "readonly": true, "required": true, "title": "String Path of the intent object", "type": "string" }, "intent_version": { "description": "Represent highest intent version across all realized objects", "readonly": true, "title": "Intent version for the status", "type": "string" }, "publish_status": { "enum": [ "UNAVAILABLE", "UNREALIZED", "REALIZED", "ERROR" ], "required": true, "title": "Aggregated Realization state of this object", "type": "string" }, "publish_time": { "$ref": "EpochMsTimestamp, "can_sort": true, "description": "This is the time when our system detects that data has been pushed to the transport nodes. This is based on a poll mechanism and hence this is not the accurate time when the intent was published at the data path. The value of -1 indicates that either the publishing is still in progress or the runtime status is UNKNOWN and hence not available. The Runtime status can be UNKNOWN if one or more hosts are down and the rules could not be sent to those hosts. When the host comes up, the runtime status will change to SUCCESS but the publish_time will show the value of the last realization time. Any new configuration change after this will start reflecting the proper value for publish_time", "readonly": true, "title": "Publish time of the intent" }, "site_uuid": { "description": "Site UUID supplied for realized site.", "title": "id of Site", "type": "string" }, "time_taken_for_realization": { "description": "This is an approximate time taken for the realization of the intent to the data path. The actual time taken could be lesser than what is reported here. The value of -1 indicates that either the publishing is still in progress or the runtime status is UNKNOWN and hence not available. The Runtime status can be UNKNOWN if one or more hosts are down and the rules could not be sent to those hosts. When the host comes up, the runtime status will change to SUCCESS but the time taken for realization will show the value of the last realization time. Any new configuration change after this will start reflecting the proper value for time_taken_for_realization.", "title": "Appoximate time taken in milliseconds for end to end realization.", "type": "integer" } }, "title": "Consolidated Realized Status for an Intent Object", "type": "object" }