Add own TCP/IP and TCP/IP of OldRelease to body of /v1/register-yourself

[openBackhaul]

The CONFIGfile contains all data that is necessary to establish the connections, which are required for properly operating the application. TCP/IP addresses, operation names and application release number might depend on the environment (e.g. SDN test laboratory or live network) in which the application gets instantiated in. In case the CONFIGfile has not properly been adapted, the adaption shall automatically been done during embedding. A small subset of addresses is required in that case.

The OAS of the ApplicationPattern to be changed in the following regards:

• [ ] The body of the /v1/register-yourself shall be complemented by the own-ip-address, own-port, old-release-ip-address and old-release-port.
• [ ] Sending these attributes shall not be mandatory.
• [ ] In case not sent within the body, existing values from the CONFIGfile shall be applied.

[PrathibaJee]

The current proposal looks good. For sending the old-release tcp information sharing an alternate proposal ,

Alternate proposal : While sending "embed-yourself" , Registry office shall send the previous version's ipaddress and port information to the new application.

The OAS of the ApplicationPattern to be changed in the following regards:

• [ ] The body of the /v1/embed-yourself shall be complemented with additional two attributes old-release-ip-address and old-release-port.
• [ ] If there is no old release of the same application available in RO then sending the ip-address of the same application shall be allowed
• [ ] Sending these attributes shall be mandatory.

[openBackhaul]

Problem statement:
The CONFIGfile should contain all data that is necessary to establish the connections, which are required for properly operating the application. TCP/IP addresses, operation names and application release number might depend on the environment (e.g. SDN test laboratory or live network) in which the application gets instantiated in. In case the CONFIGfile would not have been properly adapted, the adaption shall automatically been done during embedding. A small set of additional address attributes are required in some requests to support that.

Solution: The OAS of the ApplicationPattern shall be modified in the following regards:

• [x] The body of the /v1/register-yourself shall be complemented by own-address and own-port of the new application.
• [x] Sending these attributes shall not be mandatory.
• [x] Callbacks shall be changed, only if the own-ip-address and own-port attributes shall be actually sent in the respective case.
• [x] Descriptions shall indicate that in case own-ip-address and own-port are not sent within the body, existing values from the CONFIGfile shall be applied.
• [x] The body of the /v1/embed-yourself shall be complemented by old-release-address and old-release-port.
• [x] If there would be no old release of the same application registered at the RegistryOffice application, the own-ip-address and own-port of the new application shall be sent (ip address and port of the new application are required not for passing data, but for initiating a process that establishes the subscriptions required by the new application).
• [x] Sending these attributes shall be mandatory.
• [x] Callbacks shall be changed, too (covered by Issue 108 in the RegistryOffice repository)