Intent grouping mechanism?

11 views
Skip to first unread message

Yi Tseng

unread,
Mar 14, 2017, 6:20:23 PM3/14/17
to brigade-n...@onosproject.org
Hello,

We already put "ResourceGroup" field in every intent for resource sharing.

Also, as I mentioned in previous emails (doc: https://goo.gl/n3JnXo), I tried to use ResourceGroup as an identifier to share flow objectives between intents.

After I discuss with Sho, I realized that this might cause some problem:

Basically, if we use a resource group for multiple intents, intent framework will sharing same resource (bandwidth...) and same flow objectives to different intents.

However, this means we need to share both resource and flow objectives. We can't not decide which we don't want to share.

For example, it is not possible to share same bandwidth for different groups (NextObjective) if we use resource group only.

My idea is to create another constraint (like... GroupConstraint), which tells intent framework to use same flow objectives for different intents.

Any idea?

Yi

Yi Tseng

unread,
Mar 15, 2017, 2:41:11 PM3/15/17
to Northbound brigade
I want to add an example to describe this problem ​clearly.

 

For example, we have two intent: I1 & I2

For Intent 1, the ingress port is port 1 from s1, and egress ports are port 1 & 2 from s2
For Intent 2, the ingress port is port 2 from s1, and egress ports are port 1 & 3 from s4

They all have bandwidth constraint with bandwidth 10Mbps

Now we have two situations:

1. We share same egress ports for these Intents, but for each Intent they have their bandwidth, which means new bandwidth will be allocated if we add new intents.

2. Intents have their own egress ports, but they shares same bandwidth.

As I mentioned in previous email, we can't handle these two situation if we use resource group only.


Yi


Pier Luigi Ventre

unread,
Mar 20, 2017, 10:12:43 AM3/20/17
to Northbound brigade
Yi, thanks.

I agree on the problem. As regards the design, I was wondering if we can create a generic construct (ReuseConstraint) which we can apply in several cases. For example I would need for the Meters.
Otherwise each time we need to share something of new we have to create a new constraint. What do you think about this ?

Thanks
Pier

Yi Tseng

unread,
Mar 22, 2017, 5:00:39 PM3/22/17
to Pier Luigi Ventre, Northbound brigade
Hi Pier,

Sorry for late reply.

The logic "Use same next objective id to share same VLAN flood group" is from OF-DPA pipeline.

So I think IntentFW should not record anything about VLAN and next objective.

And I try to move this logic to the driver now.

This won't change any thing to my current compiler design.

Yi



--
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/71192a0c-dbf7-4c64-b3dd-9451c7a9871a%40onosproject.org.
For more options, visit https://groups.google.com/a/onosproject.org/d/optout.

Pier Luigi Ventre

unread,
Mar 25, 2017, 8:42:20 AM3/25/17
to Northbound brigade, pl.v...@gmail.com
Yi,
I don't not understand this change. I was thinking we were designing a general mechanism for reusing groups and not something driven by ofdpa design.
I think this is an important feature and there are other scenarios that can benefit. Another use case could be multiple subnets sharing the same next hop.
Please, share other updates about this.

Thanks
Pier
To post to this group, send email to brigade-n...@onosproject.org.

Luca Prete

unread,
Mar 25, 2017, 4:18:06 PM3/25/17
to Pier Luigi Ventre, Northbound brigade
Agreed with Pier that one of our concerns should be making things generic enough, and not tight to a specific technology or protocol.
All the customization should happen from the intent installers and below.

I understand this makes things more challenging, but we need to find a way to achieve also this goal.

-Luca

Pier
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.

Yi Tseng

unread,
Mar 27, 2017, 4:00:34 AM3/27/17
to Pier Luigi Ventre, Luca Prete, Northbound brigade
Hi Pier, Luca,

I think if we want to reuse group, we can't use Intent + Flow Objective system because only pipeline knows correct mapping (one objective can be mapped to many different table, flow rule and group entry)

Because of this, for general use case, I think we should create/use group directly from compiler (like flow rule intent, we assume devices are using single table only).

What do you think?


Yi

--
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+unsubscribe@onosproject.org.

Pier Luigi Ventre

unread,
Mar 28, 2017, 8:45:50 AM3/28/17
to Northbound brigade, pl.v...@gmail.com, lu...@onlab.us
Yi,
I don't know if I get your point, but are you suggesting to use directly flows and groups in the southbound of the Intent framework ?
If I remember well we were designing a solution through which we were able to understand when create a new next objective or reuse an existing one. Does not it work ?

Thanks
Pier

ps: sorry, but for me it is hard to follow everything from here
Pier
To unsubscribe from this group and stop receiving emails from it, send an email to brigade-northbound+unsub...@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.

--
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.

Yi Tseng

unread,
Mar 28, 2017, 5:01:55 PM3/28/17
to Pier Luigi Ventre, Northbound brigade, Luca Prete
Hi Pier,

Science Next Objective is not equal to Group, we have two different situations:

For "Group reuse", yes, use groups directly in IntentFW.
For "Next hop reuse", use Flow objective in IntentFW.

-Yi

Pier
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+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+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.

Yi Tseng

unread,
Mar 28, 2017, 5:03:03 PM3/28/17
to Pier Luigi Ventre, Northbound brigade, Luca Prete
Sorry, "Since", not Science

-Yi

Reply all
Reply to author
Forward
0 new messages