#opendaylight-nic: nic_weekly
Meeting started by raphaelamorim at 14:59:58 UTC
(full logs).
Meeting summary
-
- agenda: https://wiki.opendaylight.org/view/Network_Intent_Composition:Main#Oct_23rd.2C_2015
(adetalhouet,
15:03:39)
- Current Status of the User Stories (adetalhouet, 15:04:17)
- status of NEMO Render:
https://trello.com/c/ouzVjVJV/80-9871-nemo-render (adetalhouet,
15:05:28)
- adetalhouet asks about the NEMO renderer,
anipbu says they updated the skeleton, but asks about the model they
should use for the NIC language (colindixon,
15:05:52)
- adetalhouet says there are two models right
now, one which has subjects, actions, etc. and there's there a patch
that allows for dynamically adding new actions (colindixon,
15:06:46)
- https://git.opendaylight.org/gerrit/#/c/25503/
sample of how to add actions (colindixon,
15:07:10)
- Support redirect action (adetalhouet,
15:08:49)
- mailing list thread: https://lists.opendaylight.org/pipermail/nic-dev/2015-October/000957.html
(adetalhouet,
15:09:18)
- Nic Events https://wiki.opendaylight.org/view/Network_Intent_Composition:Nic_Events
(adetalhouet,
15:10:06)
- Maven archetype for actions: no progress
yet (adetalhouet,
15:12:22)
- Hazelcast service for dynamic attributes
resolution (adetalhouet,
15:22:47)
- on going sub tasks: https://trello.com/c/YQ0ywTsR/78-9881-hazelcast-service-for-dynamic-attributes-resolution
(adetalhouet,
15:22:58)
- raphaelamorim creates a separate bundle that
will provide rest interface to interact with this service
(adetalhouet,
15:23:46)
- gzhao asks if there will be a discussion around
this in the coming hackfest? (adetalhouet,
15:24:33)
- raphaelamorim says yes, and also answered that
this service will be agnostic (adetalhouet,
15:24:56)
- you can implement a backend in a separate code,
as needed by the user (adetalhouet,
15:26:07)
- gzhao wants to make sure the mdsal team is
aware of this (adetalhouet,
15:26:48)
- raphaelamorim says he will bring this
discussion once he has left on his plate (adetalhouet,
15:27:11)
- dlenrow says that mdsal has no action to
provide here, just specifying that mdsal is not the only
backend (adetalhouet,
15:27:33)
- Intent State Machine (adetalhouet, 15:27:53)
- https://wiki.opendaylight.org/view/Network_Intent_Composition:Beryllium_Planning#.239883:_Intent_state-machine_.28mandatory.29
initial model for discussion (adetalhouet,
15:28:07)
- mailing thread https://lists.opendaylight.org/pipermail/nic-dev/2015-October/000959.html
(adetalhouet,
15:28:31)
- it needs feedback from the community
(adetalhouet,
15:28:57)
- trello card associated to the Intent state machine: https://trello.com/c/ZJZiMitu/65-9883-intent-state-machine
(adetalhouet,
15:29:18)
- M4 Planning (adetalhouet, 15:32:02)
- User stories and planing are there (adetalhouet,
15:32:16)
- https://wiki.opendaylight.org/view/NIC:Beryllium:Release_Plan
release plan (adetalhouet,
15:32:31)
- raphaelamorim we can start working on the
deliverables (adetalhouet,
15:32:55)
- raphaelamorim says the OFRender is the default
renderer (adetalhouet,
15:35:20)
- Neutron integration (adetalhouet, 15:40:06)
- https://wiki.opendaylight.org/view/Network_Intent_Composition:Beryllium_Planning#User_Stories:_Integration_with_OVSDB.2FNeutron
(adetalhouet,
15:40:09)
- raphaelamorim says we want to listen to the SG
from neutron and store those as intent in MDSAL (adetalhouet,
15:40:51)
- raphaelamorim says then those intents will be
compiled and processed (adetalhouet,
15:41:15)
Meeting ended at 15:55:35 UTC
(full logs).
Action items
- (none)
People present (lines said)
- adetalhouet (40)
- colindixon (8)
- odl_meetbot (6)
- raphaelamorim (4)
Generated by MeetBot 0.1.4.