FMP: Integration with service platform (instantiation of NS2)
mpeuster opened this issue · comments
FMP must be able to trigger the SP to instantiate NS2.
It is important to do this instantiation with the correct instantiation parameters, e.g., the IP address of the already running NS1 (normal) and NS1 (quarantine).
I just talked to @mmiiot in a short call.
We can keep this simple, or make it more complex if we have the time.
Implementation options (ordered by complexity) are:
- do not implement (upload a new NS2 package for each instantiation of NS1)
- (semi-) hardcoded instantiation parameter in FMP (code, text file, config)
- fetch all NS1 instance and simply use the addresses of "the latest" one (this is dangerous since we might pick the wrong NS1 instance, or an old one)
- show a text field to enter the infos (not good for story)
- show a dropdown with all NS1 instances to select from (nicer for story, but hard to implement)
I'd say we can close this one and work with the first option "do not implement".