Thoughts on how to handle an Intent in perpetual "Installing" State.

45 views
Skip to first unread message

Rusty Eddy

unread,
Apr 30, 2015, 9:09:29 PM4/30/15
to onos...@onosproject.org
For whatever reason (possibly due to my mininet topology), my P2MP intent stays stuck in "INSTALLING" state.  (They were working beautifully this morning :)

While, I will debug this issue, it does have me wondering how I should best handle this condition..

1) First question: once I attempt to install an intent I assume that I should avoid re-installing the same intent, correct?   Or a more general question: other than removing an intent (or changing connectpoints), is there ever a reason that I should attempt to mess with it?

2) Since the Intent is INSTALLING, ONOS continues to receive data packets that match that would match the intent.  Since the INSTALLING state is perpetual, the controller will continue to receive these packets indefinitely. 

I can see a pro and a con to this:

pro: the controller can continue to emit the packet out of it's egress ports, hence not loosing any packets. (unless the controller becomes congested)

con: the controller becomes congested.  If the packets are high data rate, and large (such as video).  I can imagine that quickly overwhelming a controller.

Any suggestions on how to properly handle this situation?  For example 'de-register the matching packets from the TrafficSelector?

Once again TIA!


--

Rusty Eddy

Brian O'Connor

unread,
May 1, 2015, 7:53:06 PM5/1/15
to Rusty Eddy, onos...@onosproject.org
Hi Rusty,

We have just introduced a new component that you might find is relevant/useful: IntentCleanup

The job of IntentCleanup is three-fold:
  - Attempt to fix intents in the newly introduced CORRUPT state (they end up there because of errors in devices or other components)
  - Resubmit requests that have been waiting for too long (stuck in INSTALL_REQ or WITHDRAW_REQ)
  - Reinstall intents stuck in INSTALLING and re-withdraw intents stuck in WITHDRAWING

In general, it's fine to resubmit an intent that is stuck; it will just replace any existing intent that has the same key. However, hopefully that will no longer be necessary as the framework should handle it automatically.

Also, it would be interesting to figure out why the intent gets stuck in INSTALLING in the first place. So if you come up with a reason/solution or have a reproducible test case, perhaps we can fix the root cause of this one.

Thanks,
Brian

--
You received this message because you are subscribed to the Google Groups "ONOS Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to onos-dev+u...@onosproject.org.
To post to this group, send email to onos...@onosproject.org.
Visit this group at http://groups.google.com/a/onosproject.org/group/onos-dev/.
To view this discussion on the web visit https://groups.google.com/a/onosproject.org/d/msgid/onos-dev/CACt_Cc1dgHM7O3htYt10CkvxTnnPWqXqO8NqrqvZj9uHAbu0Kw%40mail.gmail.com.

Rusty Eddy

unread,
May 1, 2015, 8:24:43 PM5/1/15
to Brian O'Connor, onos...@onosproject.org
Hi Brian,

Yes, the IntentCleanup is very interesting and timely indeed.

My intent today (pun intended) was to debug this problem.  I have bigger problems..  I updated ONOS this morning, and I have not been able to get anything to work since then.  Basically my app does not appear to be receiving packets.  Everything was fine yesterday before the update.

Break points in the app are not getting hit.  I even try to set a break point in the activate method, I then deactivate / activate and nothing happens.

I can see the of_packet_in messages being sent to ONOS with tcpdump, however, my TrafficSelector does not appear to invoke my callback.

A couple other weird things are happening: Also I get this:

onos> intents
Service org.onosproject.net.intent.IntentService not found
onos> 

Also I can not connect to the ONOS GUI, I consistently  get "Web-socket to server connection closed".  There are some other weird things, but basically things have gone very wrong and I don't know how to recover ..  (ONOS can see devices, but it does not see any links, etc.)..  The only error I see in karaf log is that Host services can't be found..

I have tried completely wiping out ONOS & karaf totally, re-installing, but no difference.  

I'm stuck in the mud :(  and not sure how to proceed.  Sigh..

- rusty

Thomas Vachuska

unread,
May 1, 2015, 8:48:11 PM5/1/15
to Rusty Eddy, Brian O'Connor, onos...@onosproject.org
Rusty, do you have the drivers app
loaded? You need to. 

Thomas

Rusty Eddy

unread,
May 1, 2015, 9:18:10 PM5/1/15
to Thomas Vachuska, Brian O'Connor, onos...@onosproject.org
No I probably do NOT.  I will check again.

I just pulled an older commit, dated on 4/23 and everything is working fine again.   Even the Intent has been installed and working properly.  

Ok, I will pull the latest, make sure I am loading the driver app and take it from there..

Just curious, Is that something that changed recently?   Or could it be a problem with my karaf config?


t: @rustyeddy


Rusty Eddy

unread,
May 1, 2015, 9:46:30 PM5/1/15
to Thomas Vachuska, Brian O'Connor, onos...@onosproject.org
Thomas, no need to reply, I just read your recent post to onos-dev :)


t: @rustyeddy


Reply all
Reply to author
Forward
0 new messages