Commit 41ca828a authored by Hammad Zafar's avatar Hammad Zafar
Browse files

Merge branch 'NFVSOL(25)000393_SOL026_Sequence_Diagram_Updates_based_on_DMTF_feedback' into 'main' 

NFVSOL(25)000393_SOL026_Sequence_Diagram_Updates_based_on_DMTF_feedback

See merge request !3
parents 16fc5bda bf134797

GS_NFV-SOL_026.md

+9 −9
Original line number Original line Diff line number Diff line
@@ -428,7 +428,7 @@ The modification of an individual Computer System resource, as illustrated in Fi 
1. The API consumer sends a PATCH request to the Individual Computer System resource, including data structure in the message content body representing the modifiable properties to be modified in the individual computer system resource.

1. The API consumer sends a PATCH request to the Individual Computer System resource, including data structure in the message content body representing the modifiable properties to be modified in the individual computer system resource.

1. If the PIM supports asynchronous operations and modification of the computer system resource requires some time to process, the PIM returns a "202 Accepted" response. The response also contains the URI of the associated Task Monitor in the Location header. The response body can optionally contain representation of the corresponding Task resource created by the PIM for this asynchronous operation.

1. If the PIM supports asynchronous operations and modification of the computer system resource requires some time to process, the PIM returns a "202 Accepted" response. The response also contains the URI of the associated Task Monitor in the Location header. The response body can optionally contain representation of the corresponding Task resource created by the PIM for this asynchronous operation.

1. The PIM modifies the Individual Computer System resource.

1. The PIM modifies the Individual Computer System resource.

1. The PIM returns a "200 OK" response to the API consumer and includes in the message content body a representation of the modified Computer System resource.

1. The PIM returns a "200 OK" response to the API consumer and includes in the message content body a representation of the modified Computer System resource. Alternatively, the PIM can also return a "204 No Content" response to the API consumer indicating successful operation.





**Postcondition:** Upon successful completion of the synchronous operation or of the corresponding task in case of asynchronous operation, the Individual Computer System resource has been modified.

**Postcondition:** Upon successful completion of the synchronous operation or of the corresponding task in case of asynchronous operation, the Individual Computer System resource has been modified.
@@ -449,7 +449,7 @@ The replacement of an individual Computer System resource, as illustrated in Fig 
1. The API consumer sends a PUT request to the Individual Computer System resource including a valid representation of the individual Computer System resource to be replaced in the message content body.

1. The API consumer sends a PUT request to the Individual Computer System resource including a valid representation of the individual Computer System resource to be replaced in the message content body.

1. If the PIM supports asynchronous operations and replacement of the computer system resource requires some time to process, the PIM returns a "202 Accepted" response. The response also contains the URI of the associated Task Monitor in the Location header. The response body can optionally contain representation of the corresponding Task resource created by the PIM for this asynchronous operation.

1. If the PIM supports asynchronous operations and replacement of the computer system resource requires some time to process, the PIM returns a "202 Accepted" response. The response also contains the URI of the associated Task Monitor in the Location header. The response body can optionally contain representation of the corresponding Task resource created by the PIM for this asynchronous operation.

1. The PIM replaces the Individual Computer System resource.

1. The PIM replaces the Individual Computer System resource.

1. The PIM returns a "200 OK" response to the API consumer and includes in the message content body a representation of the replaced Computer System resource.

1. The PIM returns a "200 OK" response to the API consumer and includes in the message content body a representation of the replaced Computer System resource. Alternatively, the PIM can also return a "204 No Content" response to the API consumer indicating successful operation.





**Postcondition:** Upon successful completion of the synchronous operation or of the corresponding task in case of asynchronous operation, the Individual Computer System resource has been replaced.

**Postcondition:** Upon successful completion of the synchronous operation or of the corresponding task in case of asynchronous operation, the Individual Computer System resource has been replaced.
@@ -470,7 +470,7 @@ The deletion of an individual Computer System resource, as illustrated in Figure 
1. The API consumer sends a DELETE request to the Individual Computer System resource.

1. The API consumer sends a DELETE request to the Individual Computer System resource.

1. If the PIM supports asynchronous operations and deletion of the computer system resource requires some time to process, the PIM returns a "202 Accepted" response. The response also contains the URI of the associated Task Monitor in the Location header. The response body can optionally contain representation of the corresponding Task resource created by the PIM for this asynchronous operation.

1. If the PIM supports asynchronous operations and deletion of the computer system resource requires some time to process, the PIM returns a "202 Accepted" response. The response also contains the URI of the associated Task Monitor in the Location header. The response body can optionally contain representation of the corresponding Task resource created by the PIM for this asynchronous operation.

1. The PIM deletes the individual Computer System resource.

1. The PIM deletes the individual Computer System resource.

1. The PIM returns a "204 No Content " response to the API consumer indicating that the resource has been successfully deleted.

1. The PIM returns a "204 No Content " response to the API consumer indicating that the resource has been successfully deleted. Alternatively, the PIM can also return a "200 OK" response to the API consumer including a representation of the deleted Computer System resource in the message content body.





**Postcondition:** Upon successful completion of the synchronous operation or of the corresponding task in case of asynchronous operation, the Individual Computer System resource has been deleted.

**Postcondition:** Upon successful completion of the synchronous operation or of the corresponding task in case of asynchronous operation, the Individual Computer System resource has been deleted.
@@ -857,7 +857,7 @@ The modification of a topology object, as illustrated in Figure 8.4.41, consists 
1. The API consumer sends a PATCH request to the <topology object URI>, including data structure in the message content body representing the modifiable properties to be modified in the individual topology object.

1. The API consumer sends a PATCH request to the <topology object URI>, including data structure in the message content body representing the modifiable properties to be modified in the individual topology object.

1. If the PIM supports asynchronous operations and modification of the topology object requires some time to process, the PIM returns a "202 Accepted" response. The response also contains the URI of the associated Task Monitor in the Location header. The response body can optionally contain representation of the corresponding Task resource created by the PIM for this asynchronous operation.

1. If the PIM supports asynchronous operations and modification of the topology object requires some time to process, the PIM returns a "202 Accepted" response. The response also contains the URI of the associated Task Monitor in the Location header. The response body can optionally contain representation of the corresponding Task resource created by the PIM for this asynchronous operation.

1. The PIM modifies the individual topology object.

1. The PIM modifies the individual topology object.

1. The PIM returns a "200 OK" response to the API consumer and includes in the message content body a representation of the modified topology object.

1. The PIM returns a "200 OK" response to the API consumer and includes in the message content body a representation of the modified topology object. Alternatively, the PIM can also return a "204 No Content" response to the API consumer indicating successful operation.





**Postcondition:** Upon successful completion of the synchronous operation or of the corresponding task in case of asynchronous operation, the individual topology object has been modified.

**Postcondition:** Upon successful completion of the synchronous operation or of the corresponding task in case of asynchronous operation, the individual topology object has been modified.
@@ -878,7 +878,7 @@ The replacement of an individual topology object, as illustrated in Figure 8.4.5 
1. The API consumer sends a PUT request to the <topology object URI> including a valid representation of the individual topology object to be replaced in the message content body.

1. The API consumer sends a PUT request to the <topology object URI> including a valid representation of the individual topology object to be replaced in the message content body.

1. If the PIM supports asynchronous operations and replacement of the topology object requires some time to process, the PIM returns a "202 Accepted" response. The response also contains the URI of the associated Task Monitor in the Location header. The response body can optionally contain representation of the corresponding Task resource created by the PIM for this asynchronous operation.

1. If the PIM supports asynchronous operations and replacement of the topology object requires some time to process, the PIM returns a "202 Accepted" response. The response also contains the URI of the associated Task Monitor in the Location header. The response body can optionally contain representation of the corresponding Task resource created by the PIM for this asynchronous operation.

1. The PIM replaces the individual topology object.

1. The PIM replaces the individual topology object.

1. The PIM returns a "200 OK" response to the API consumer and includes in the message content body a representation of the replaced topology object.

1. The PIM returns a "200 OK" response to the API consumer and includes in the message content body a representation of the replaced topology object. Alternatively, the PIM can also return a "204 No Content" response to the API consumer indicating successful operation.





**Postcondition:** Upon successful completion of the synchronous operation or of the corresponding task in case of asynchronous operation, the individual topology object has been replaced.

**Postcondition:** Upon successful completion of the synchronous operation or of the corresponding task in case of asynchronous operation, the individual topology object has been replaced.
@@ -899,7 +899,7 @@ The deletion of an individual topology object, as illustrated in Figure 8.4.6-1, 
1. The API consumer sends a DELETE request to the <topology object URI>.

1. The API consumer sends a DELETE request to the <topology object URI>.

1. If the PIM supports asynchronous operations and deletion of the topology object requires some time to process, the PIM returns a "202 Accepted" response. The response also contains the URI of the associated Task Monitor in the Location header. The response body can optionally contain representation of the corresponding Task resource created by the PIM for this asynchronous operation.

1. If the PIM supports asynchronous operations and deletion of the topology object requires some time to process, the PIM returns a "202 Accepted" response. The response also contains the URI of the associated Task Monitor in the Location header. The response body can optionally contain representation of the corresponding Task resource created by the PIM for this asynchronous operation.

1. The PIM deletes the individual topology object.

1. The PIM deletes the individual topology object.

1. The PIM returns a "204 No Content " response to the API consumer indicating that the topology object has been successfully deleted.

1. The PIM returns a "204 No Content " response to the API consumer indicating that the topology object has been successfully deleted. Alternatively, the PIM can also return a "200 OK" response to the API consumer including a representation of the deleted topology object in the message content body.





**Postcondition:** Upon successful completion of the synchronous operation or of the corresponding task in case of asynchronous operation, the individual topology object has been deleted.

**Postcondition:** Upon successful completion of the synchronous operation or of the corresponding task in case of asynchronous operation, the individual topology object has been deleted.
@@ -1135,13 +1135,13 @@ The procedure consists of the following steps as illustrated in figure A.2-1: 
1. The PIM returns a "200 OK" response to the API consumer and includes in the message content body a representation of the individual Subscription resource.

1. The PIM returns a "200 OK" response to the API consumer and includes in the message content body a representation of the individual Subscription resource.

1. The API consumer sends a PATCH request to the Individual Subscription resource, including data structure in the message content body representing the modifiable properties to be modified in the Individual Subscription resource.

1. The API consumer sends a PATCH request to the Individual Subscription resource, including data structure in the message content body representing the modifiable properties to be modified in the Individual Subscription resource.

1. The PIM modifies the Individual Subscription resource.

1. The PIM modifies the Individual Subscription resource.

1. The PIM returns a "200 OK" response to the API consumer and includes in the message content body a representation of the modified Subscription resource.

1. The PIM returns a "200 OK" response to the API consumer and includes in the message content body a representation of the modified Subscription resource. Alternatively, the PIM can also return a "204 No Content" response to the API consumer indicating successful operation.

1. The API consumer sends a PUT request to the Individual Subscription resource including a valid representation of the individual Subscription resource to be replaced in the message content body.

1. The API consumer sends a PUT request to the Individual Subscription resource including a valid representation of the individual Subscription resource to be replaced in the message content body.

1. The PIM replaces the Individual Subscription resource.

1. The PIM replaces the Individual Subscription resource.

1. The PIM returns a "200 OK" response to the API consumer and includes in the message content body a representation of the replaced Subscription resource.

1. The PIM returns a "200 OK" response to the API consumer and includes in the message content body a representation of the replaced Subscription resource. Alternatively, the PIM can also return a "204 No Content" response to the API consumer indicating successful operation.

1. The API consumer sends a DELETE request to the Individual Subscription resource.

1. The API consumer sends a DELETE request to the Individual Subscription resource.

1. The PIM deletes the individual Subscription resource.

1. The PIM deletes the individual Subscription resource.

1. The PIM returns a "204 No Content " response to the API consumer indicating that the resource has been successfully deleted.

1. The PIM returns a "204 No Content " response to the API consumer indicating that the resource has been successfully deleted. Alternatively, the PIM can also return a "200 OK" response to the API consumer including a representation of the deleted Subscription resource in the message content body.





**Error handling:** The PIM rejects a subscription management request if the subscription representation in the creation or replacement request is not valid, or properties in the modify request are not modifiable, etc. In case of failure, appropriate error information is provided in the response.

**Error handling:** The PIM rejects a subscription management request if the subscription representation in the creation or replacement request is not valid, or properties in the modify request are not modifiable, etc. In case of failure, appropriate error information is provided in the response.

media/image15.png

−11.5 KiB (13.5 KiB)
Loading image diff...

media/image16.png

−11.1 KiB (13.3 KiB)
Loading image diff...

media/image17.png

−10.5 KiB (13.2 KiB)
Loading image diff...

media/image18.png

−29.7 KiB (30.7 KiB)
Loading image diff...