1 # Instantiation in VIMs with more than one physnet
5 - Gerardo Garcia (Telefonica)
6 - Alfonso Tierno (Telefonica)
7 - Francisco Javier Ramon (Telefonica)
19 In environments where some physical redundancy is required in terms of
20 networking, it is common the use of schemas with more than one switch upstream,
21 dividing the physical medium in groups of physical interfaces depending of the
22 upstream switch they are attached. In order to facilitate a sensible management
23 of these physical interfaces belonging to different "redundancy groups" by the
24 VIM, there is the possibility to classify them into the so-called 'physnets',
25 so that the VIM can leverage on that physical redundacy if needed.
27 While this feature should not create a fundamental change in OSM operation or
28 the way its modelling works, and it is a fact that OSM can work with these
29 environments, it is also true that it works today with some limitations when
30 SDN Assist is in place. Thus, in a VIM with multiple physnets, only one can be
31 registered today when configuring a VIM target in OSM, leading to potential
32 underuse of resources (usually, by one half). Furthermore, when those physnets
33 obbey to some kind of physical active-active scheme, OSM cannot leverage on
34 this information to make NS/NSI deployments more reliable.
36 This feature intends to solve the limitations described above.
38 ## Demo or definition of done
40 With a VIM with multiple physnets, check that it is possible:
42 - Register the VIM with all its physnets when defining a VIM target in OSM with
44 - Deploy a large NS requiring SDN Assist in such a VIM so that no interfaces
45 are excluded because of the physnet they belong.