I am closing this epic since all the user stories have been closed

We have a GO. 

 After some consultation here, the following is suggested:

• Putting the feature behind a toggle (ofcourse)

• implementing it in a manner the will let in future giving an option to have this feature selectively; i.e. when toggle is on, still default-user will not have the indication, unless it opted in (by some browser-local setting or such).

: What about next steps here?
Assuming, we have all the necessary data to display this additional information in VID already - would it be fine to e.g. modify this "Deploy" button?

:
asked me to give a little bit more on a use-case description, so here it comes.
We would assume, that VID will be used more in the system/service integration phase and service operations phase, rather than for high-load production use (where we expect ExtAPi to be used). (Service integration phase - a human is instantiating the services, to test, if everything works fine; service operations - a user executes actions in VID, after he/she got a support ticket to be solved). In such cases, when a person is using VID - and usually a team of people shares on ONAP/VID instance, like in our case, two features would be useful:

1. Macro/ a`la carte marking of service models (orchestration-type is a property of a service model, selectable in SDC).
   This helps to quickly identify a service orchestrated in a specific way - when we need to test service orchestration steps, or when we need to prepare for a specific orchestration mode.
   E.g. when we do some SO workflow development, and we`d like to confirm, it is working in an E2E environment with VID, then it helps to identify the right service model to be used from orchestration perspective (macro - or a`la carte). If we figure out, that one of the orchestration models is not working properly, it saves our time to look for existing service models, which are orchestrated in a mode, which currently works (or which we`d like to test with VID as GUI front-end) in SO.
   E.g. recently we were spending some time on a`la carte, and marco orchestration of services, which use PNF resources. It was difficult for us to identify a Service model to be orchestrated in an appropriate style, which we wanted to test - as we`re running a shared system with maaany service models loaded. Service Models are similar to each other - it doesn`t matter much which one we select for orchestration, but the orchestration mode matters a lot. If we want to execute a specific service model instantiation, it helps us to prepare further actions (which are different for macro, as a more-less one-click thing; and different for a`la carte, where You have a few things to do - service instance, then VNF, then VF-Module/Modules).

One would say, that we could introduce a naming convention to solve that (say macro_ or alacarte_ prefixes in service models), but in reality no-one seriously thinks about it, when creating service models, and second thing - this will impact the transparency/visibility of service models available.

For me a great thing will be a "Deploy" button, which looks differently for a`la carte, and for macro orchestration it would be easier to select the right service model, when we integrate stuff on our environment. We could ask our human interaction designers to figure something nice out

1. Another thing, which would help in a Service Model browser is a list of filters, based on columns.
   It happens, that we`re looking for a specific service model to be instantiated, and as You can assume - when we`re working with PNFs, most of service models start with pnf..., like pnf_damian, pnf_tomek, pnf_atomek (a`la carte), pnf_mtomek (macro), aso. Difficult to read, and if multiple service models are available, difficult to find "this service, that I really need, and I know a key-word about it".
   It would make a lot of sense to have filtering on columns, so I could filter out e.g. "pnf services", "damian`s services", "macro services", "5g services" (base don sth simple like column.contains($serachString)) - as long as these keywords are stored in the service names. Such a filtering function would be really great for VID, if a person is operating on tons of service models in a shared ONAP/VID system. It happens as well, that I have a Service Model UUID or Invariant UUID - would be great just to copy-paste that in a filter window, and get a service model I am interested in (or a specific service instance in service instance browser - but that`s a different story). Today looking for services in VID without this filtering is difficult, when running with a higher number of services.