Network as CodeSpecialized Network notification details
On this page, you will find the JSON schema for Specialized-Network notifications.
Its purpose is to monitor changes made to slices, such as creation, modification,
the several outcomes for these changes and the current slice state, e.g.: pending, available, deleted, etc.
Underneath the JSON schema, there is a table with further information on the specific keyword values.
Remember that the string values represented below are just examples that can be used. So, they should contain your real slice values.
JSON schema for Specialized Network notifications
{
"resource": "slice-01",
"action": "add | modify | delete | noChange",
"outcome": "acknowledged | rejected | pending | held | inProgress |
cancelled | completed | failed | partial | assessingCancellation | pendingCancellation",
"current_slice_state": "AVAILABLE | OPERATING | DELETED"
}Learn more about the possible states in a slice life cycle and how to react to them.
| Specialized-Network-keyword values | Description |
|---|---|
resource | A string value with slice name or identifier. |
action | A string value describing the slice operation performed. The possible values are: add, modify, delete, noChange. |
outcome | A string value containing the different outcomes or results of the previous slice action/operation. They can be: acknowledged, rejected, pending, held, inProgress, cancelled, completed, failed, partial, assessingCancellation, pendingCancellation. |
current_slice_state | A string value with the current slice states or statuses, which can be: PENDING, OPERATING, AVAILABLE, DELETED. |
Last updated on July 09, 2024