Domain Intent

3 views
Skip to first unread message

Michele Santuari

unread,
Apr 18, 2017, 1:02:46 PM4/18/17
to brigade-n...@onosproject.org, Francesco Lucrezia, Thomas Szyrkowiec, Andreas Papazois
Hi all,
we have submitted and tested the patches of the Domain Intent:
Some documentation is available here.

The code submitted is enough to mange the Domain Intent installation process, so that application can request a Domain Intent. Moreover, the aforementioned patches are enough to build your own compiler that allows the compilation of an Intent into Domain Intents and/or FlowRule intents.

We have not yet submitted the extensions to the Link Collection Compiler to identify the path involving different domains and consequently to generate Domain Intents. We are fixing the compiler logic to avoid any performance issues. 

Best.
 

Michele Santuari, Ing
Research Engineer
FuN - Future Networks

---------------------------------------- 
CREATE-NET Research Center
Fondazione Bruno Kessler (FBK)
via alla Cascata 56D
38123 Povo, Trento (Italy)
F: 

e-mail: 
www: 
​http://create-net.fbk.eu

Yuta Higuchi

unread,
Apr 18, 2017, 7:23:51 PM4/18/17
to Michele Santuari, brigade-n...@onosproject.org, Francesco Lucrezia, Thomas Szyrkowiec, Andreas Papazois
Let me first understand how topology looks after introducing this domain.  

Is it like
 a) ONOS can see all the devices (and links) including the devices under the control of Domain controller.
or 
 b) Domain looks like a single Device to regular ONOS world(=DeviceService, etc.)
    and if you query via DomainService, you might be able to see the topology inside the domain?
or something else?





--
You received this message because you are subscribed to the Google Groups "Northbound brigade" group.
To unsubscribe from this group and stop receiving emails from it, send an email to brigade-northbound+unsub...@onosproject.org.
To post to this group, send email to brigade-northbound@onosproject.org.
Visit this group at https://groups.google.com/a/onosproject.org/group/brigade-northbound/.
To view this discussion on the web visit https://groups.google.com/a/onosproject.org/d/msgid/brigade-northbound/CAAHkLFKivGL1R3B1%3Ddim4e%3DNY4Ue0oYqJKA48NViPnRJQThmaQ%40mail.gmail.com.
For more options, visit https://groups.google.com/a/onosproject.org/d/optout.

Michele Santuari

unread,
Apr 19, 2017, 2:58:38 AM4/19/17
to Yuta Higuchi, brigade-n...@onosproject.org, Francesco Lucrezia, Thomas Szyrkowiec, Andreas Papazois
Hi Yuta,
option a. The domain controller exposes a topology (full, parial, big switch...) using the ONOS topology model. 
The Domain Intent does not manage the topology abstraction for the domain and it is used to provision services (intent) through a domain.
Best.

Michele Santuari, Ing
Research Engineer
FuN - Future Networks

---------------------------------------- 
CREATE-NET Research Center
Fondazione Bruno Kessler (FBK)
via alla Cascata 56D
38123 Povo, Trento (Italy)
F: 

e-mail: 
www: 
​http://create-net.fbk.eu

To unsubscribe from this group and stop receiving emails from it, send an email to brigade-northbound+unsubscribe@onosproject.org.

--
You received this message because you are subscribed to the Google Groups "Northbound brigade" group.
To unsubscribe from this group and stop receiving emails from it, send an email to brigade-northbound+unsub...@onosproject.org.
To post to this group, send email to brigade-northbound@onosproject.org.
Visit this group at https://groups.google.com/a/onosproject.org/group/brigade-northbound/.

Yuta Higuchi

unread,
Apr 19, 2017, 6:22:06 PM4/19/17
to Michele Santuari, brigade-n...@onosproject.org, Francesco Lucrezia, Thomas Szyrkowiec, Andreas Papazois
Hi Michele, 

Thanks.  
I'm wondering how path computation process will be executed during service provisioning.
Especially when you expose detailed topology of the Domain to ONOS. 

Off the top of my head, I can think of idea like
various resource availability will be exposed to ONOS so that ONOS can compute appropriate path, 
or ONOS generates abstract view and compute inter-Domain path and let Domain controller to compute intra-Domain path, 
or ...

What were your thoughts?
# That's the part you've mentioned as extension to LinkCollectionIntentCompiler?


Michele Santuari

unread,
Apr 20, 2017, 3:37:20 AM4/20/17
to Yuta Higuchi, brigade-n...@onosproject.org, Francesco Lucrezia, Thomas Szyrkowiec, Andreas Papazois
Hi Yuta,
ONOS should compute the full path including the one within the domain. For example ONOS calculates a path that traverses some devices that do not belong to a domain and some devices that are part of one or more domains. The rule generates are the following:
  1. FlowRule for those devices that do not belong to a domain;
  2. a Domain Intent with an explicit path (a set of links that belong to the domain) for each domain involved in the computed path.
If the domain is abstracted by the domain controller as a big switch or as reduced topology, the aforementioned solution is still valid. The domain controller will manage the abstraction of the domain. For example: the domain controller must translate the Domain Intent into configurations that are compatible with the real topology.

This is the first implementation of the Domain Intent within the LinkCollectionIntentCompiler that should be modified to avoid any performance issue, but can be considered an example of what we want to achieve.
Thank you.


Michele Santuari, Ing
Research Engineer
FuN - Future Networks

---------------------------------------- 
CREATE-NET Research Center
Fondazione Bruno Kessler (FBK)
via alla Cascata 56D
38123 Povo, Trento (Italy)
F: 

e-mail: 
www: 
​http://create-net.fbk.eu

Reply all
Reply to author
Forward
0 new messages