Start Participant containers after Runtime starts 23/128023/2
authorSirisha_Manchikanti <sirisha.manchikanti@est.tech>
Tue, 22 Mar 2022 16:20:18 +0000 (16:20 +0000)
committerSirisha_Manchikanti <sirisha.manchikanti@est.tech>
Thu, 24 Mar 2022 15:58:24 +0000 (15:58 +0000)
commite8b643b8a9e866cd8bb204dd26b4d3eb3891fa21
tree825a5981bb4baa78c0ef5c753a6616ecd8c6d5e2
parent93d4ee603e563d292845e12b85811bd9e8c42d44
Start Participant containers after Runtime starts

PARTICIPANT_REGISTER message from participants is getting lost, as
RUNTIME_ACM is not started completely. Adjusted CSIT bringup of
containers accordingly. This needs a correction in Participant
Intermediary for next release, Jira raised for the same
https://jira.onap.org/browse/POLICY-4042

Issue-ID: POLICY-4003
Signed-off-by: Sirisha_Manchikanti <sirisha.manchikanti@est.tech>
Change-Id: I146fa5c2ae2090d504b7e665905ff2dba61097ef
csit/clamp/plans/setup.sh
csit/clamp/tests/data/InstantiateAC.json
csit/clamp/tests/data/PMSHMultipleACTosca.yaml
csit/docker-compose-all.yml