19:31:40 <dbainbri> #startmeeting ONF NBI Session 1
19:31:40 <odl_meetbot> Meeting started Thu Feb 12 19:31:40 2015 UTC.  The chair is dbainbri. Information about MeetBot at http://ci.openstack.org/meetbot.html.
19:31:40 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:31:40 <odl_meetbot> The meeting name has been set to 'onf_nbi_session_1'
19:31:58 <tbachman> dbainbri: I guess we could info in the stuff from above
19:32:19 <tbachman> #info DaveL: intent is meant to be the "most" northbound interface (A true north bound interface? TNBI?)
19:32:27 <tbachman> #info DaveL: now is a unique opportunity to get broad collaboration on a intent and if we don't have an urgent response we may miss the opportunity
19:32:40 <tbachman> #info DaveL: need intent on at least two controllers to start snow ball effect.
19:32:49 <tbachman> #info Pascal (MSFT): there is a thin SDN model and a thick SDN model. The difference is the separation of a "service" component from a low level mediation layer. Vendors are deploying both models today
19:32:59 <tbachman> #info (commentary from david: think it makes sense to have the same intent "syntax" in support of an abstract intent and a precise intent [mediation])
19:33:19 <tbachman> dbainbri: your last one got truncated on my end
19:33:27 <tbachman> saw “both EP to c” and then it got cut off
19:33:38 <dbainbri> #info if an intent implementation will be over multiple domains (where there is a separate controller per domain) the goal would be to send the complete intent to each controller. In order to enable this each controller needs to be able to know what part of the intent they need to provide as well as know which "end points" it needs to use as an interconnect to another domain. Does this mean there is somewhere a registry of both E
19:33:58 <tbachman> lol
19:34:07 <tbachman> now it ended at “both E”
19:34:19 <dbainbri> ok, will break it up
19:34:20 <tbachman> I guess b/c of the xtra #info
19:34:27 <tbachman> you can #undo
19:34:32 <tbachman> to remove the truncated
19:34:43 <dbainbri> #undo
19:34:43 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x19bc310>
19:34:48 <tbachman> :)(
19:34:49 <tbachman> :)
19:35:02 <dbainbri> ok what is in the notes now and what do i need to #info in?
19:35:11 <tbachman> everything except your last entry
19:35:15 <tbachman> which got truncated on my side
19:35:24 <tbachman> I’d break it up at “Does this mean”
19:35:25 <dbainbri> ok, i will add the last bit by bit
19:35:35 <tbachman> dbainbri: thx
19:35:38 <dbainbri> irc://weber.freenode.net:6697/#info if an intent implementation will be over multiple domains (where there is a separate controller per domain) the goal would be to send the complete intent to each controller. In order to enable this each controller needs to be able to know what part of the intent they need to provide as well as know which "end points" it needs to use as an interconnect to another domain.
19:35:54 <dbainbri> #info if an intent implementation will be over multiple domains (where there is a separate controller per domain) the goal would be to send the complete intent to each controller. In order to enable this each controller needs to be able to know what part of the intent they need to provide as well as know which "end points" it needs to use as an interconnect to another domain.
19:36:01 <tbachman> there you go :)
19:36:08 <tbachman> copy paste is a bit weird in these clients
19:36:21 <dbainbri> #question Does this mean there is somewhere a registry of both EP to controller and for each controller some way to lookup to which port the controller should use for the inter-connect?
19:36:52 <dbainbri> #info Does this mean there is somewhere a registry of both EP to controller and for each controller some way to lookup to which port the controller should use for the inter-connect?
19:37:20 <tbachman> dbainbri: you’re getting the hang of it ;)
19:37:42 <dbainbri> i think meetbot is part of the SkyNet take over
19:40:28 <tbachman> lol
20:54:31 <dbainbri> #endmeeting