The customer wants to be able to lunch a new GSC while the system is running w/o restarting the GSA.
The GSC configuration should be taken from the existing config/gsa/gsc_xxx.xml configuration.
The GSC should be launched using the REST Manager.
What we currently support?
1. creating a new container using the Rest Manager (http://localhost:8090/v2/index.html#!/Containers/post_containers) but in this case, the user needs to give values for vmArguments, Zones, and Memory, instead of relying on existing gsc_xxx.xml
2. lunch a new container based on Advanced Configuration, as written here: https://docs.gigaspaces.com/latest/admin/the-runtime-environment.html?Highlight=GSA#AdvancedConfiguration
But this is not relevant when the user wants to lunch a new container when the system is running.
3. the user can also extend the Rest Manager as written here:
He can write his own class, pars the gsc_xxx.xml and adds the class as a plugin. This is a good option but we can do it for him. The API should let the user pass the GSC configuration path/name and we will lunch a new GSC based on this configuration.