(pre-)allocate IP addresses to the VNF

POST 
/api/v1/projects/:projectId/vnfs/:vnfId/actions/allocateipaddresses

Some VNF models require allocating IP addresses before provisioning the VNF because the requester needs to know these addresses to fully configure the VNF

Request

Responses

202

An asynchronous workflowExecution to allocate IP addresses is processing

Response Headers

X-Workflow-Execution-Href

Href of the asynchronous workflow execution that processes the request, in order to track its state.

X-Retry-After

The delay in seconds between requests to check the state of the workflow execution.

400

Bad Request. List of supported codes: 20: Invalid URL parameter value, 21: Missing body, 22: Invalid body, 23: Missing body field, 24: Invalid body field, 25: Missing header, 26: Invalid header value, 27: Missing query-string parameter, 28: Invalid query-string parameter value.

401

Not Authorized. List of supported codes: 40 = Missing credentials, 41 = Invalid credentials, 42 = Expired credentials.

403

Forbidden. List of supported codes: 50 = access denied, 51 = forbidden requester, 53 = too many requests.

404

Resource not found. List of supported codes: 60 = resource not found.

405

Method not allowed. List of supported codes: 61 = method not allowed.

409

Conflict with a workflowExecution that is currently processing on this virtual network function

500

Internal Error. List of supported codes: 1 = internal error.

503

Service unavailable