NEW API call to add topology/blueprint to the domains without checking requirements, fast and without side-effects

We need a new API call to add a topology/blueprint to a domain (or domains) without checking if the topology can be reserved in the target domain.

This can be a new API call, or modification of the existing API call, by introducing an optional input parameter to allow this new behavior.

The intent is to have an API call that is FAST and without side effects (described below), make the topology visible in the new domain, and THEN let admins deal with the lack of required resources (if the problem exist at all).

*** Problem description (why current implementation does not match my needs)

Based on my observations, the existing API call (AddTopologiesToDomain) has the following undesirable side effects:

1. Server tries to find if the topology can be reserved in the new domain if the resources can be found to satisfy the topology requirements

2. Call takes a lot of time to complete work described under (1), and frequently fails to complete and then reports a timeout error (time allowed is set by the key "MaxRoutesResolveTime" on the server).

2a. I observed the timeout errors even if the max resolution time is set to 20min. I think this is an unreasonable slow response.

3. If the call does not fail with the timeout error (see 2) then it typically finds resources in the domains where the BP is already visible and adds those resources to the target domain.

3a. As a system admin I do not want the Quali server to make decisions about to which domains my lab resources belong. I do not want resources from Lab1 (in DC1) to be added to Lab2 (in DC2) which is 1000 miles away. This is a show-stopper. It suddenly produces (unusable) sandboxes with resources that should not be there.

3b. Unwanted action of adding resources to the domain happen even if the target domain has all the resources required by the BP (we use abstract resources)

3c. This side effect is not documented

4. Command in the RM Client seems to be using the same API call, produces the same side-effects, and takes a lot of time to complete. Admin is not informed/warned about the side effects, before or after the command is executed

5. While executing this API call (5-20min for a single topology), the system is very slow to make new reservations. API calls to add /remove resources to/from a domain are blocked (do not return any result).

6. My DB has >100k resources and subresources. Getting rid of the misplaced resources (in the wrong domains) is not an easy task to do, and it should not be needed in the first place.

I opened a support case about the behavior of this API call. I got a response that the system works as designed and that I need to request a new feature (IdeaBox).... so here it is...