Implementing VNI generation for VBD

Change-Id: Id79cb9442f58761c957914cc8448883d32ebccf3
Signed-off-by: Michal Cmarada <mcmarada@cisco.com>
Signed-off-by: Martin Sunal <msunal@cisco.com>

Merge "Added BridgeMember listener"

Added BridgeMember listener

Problem was that BridgeDomainManagerImpl considered bridge domain as created
when it stores VBD request to CONF DS. BUT bridge domain is created
after VBD stores bridge-member to node in OPER DS.
This commit introduces listener which is registered after VBD request is stored
to CONF DS and it waits for VBD response. When a response is received
the listener is unregistered.

Respons has to be received within 10s otherwise renderer considers that VBD did
not create bridge-domain.

Change-Id: I7a02b87d16c474475b588628ec90c740f939c427
Signed-off-by: Martin Sunal <msunal@cisco.com>

introduced SxpEndpointAugmentor

    - endpoint-augmentor implementation for sgt
    - added domain-specific-registry to config of sxp-mapper

Change-Id: I153368992b59f476f87503bb2c8951a0b5237682
Signed-off-by: Matej Perina <matej.perina@pantheon.sk>
Signed-off-by: Michal Rehak <mirehak@cisco.com>
Signed-off-by: Vladimir Lavor <vlavor@cisco.com>

Adding support for VLAN bridge domains

 - covers one of provider networks use cases
 - VLAN type bridge-domain should be configured
   in vpp-renderer.yang
 - if a bridge domain is not read from renderer's
   config, VXLAN is created by default

Change-Id: I2954bb154718d8cbb73f6a89646fb71df25c1827
Signed-off-by: Tomas Cechvala <tcechval@cisco.com>

Mapping Neutron network for VPP renderer

Neutron networks are mapped to bridge-domains
Works for vxlan, flat and vlan networks.

Any comments on naming are appreciated

Change-Id: Ia96d661ff7c1bcc596e4b50ff189724233e6563f
Signed-off-by: Tomas Cechvala <tcechval@cisco.com>

Fixed test because of v3po.yang change

Change-Id: Ib821d2d747e04262edcd4744919ffb45396ea7e7
Signed-off-by: Martin Sunal <msunal@cisco.com>

Merge "Resolved policy sidepanel"

Merge "Resolved policy contracts"

Merge "Endpoint added"

Merge "resolved-policy view - initial commit"

Merge changes Ic557558f,I59d1ba03

* changes:
  Integrated VBD to VPP renderer for VXLAN
  Added executor for netconf callback processing

Merge "Added check for config change in RendererManager"

ios-xe renderer reporting capabilities

Change-Id: I16ca6bb9ef0a2843624d668136d8dd7ffe015a20
Signed-off-by: Matej Perina <matej.perina@pantheon.sk>

Added check for config change in RendererManager

RendererManager compares current state with last configured state.
Only if these two states are differerent a configuration for renderers
is created.
This check is needed because it happens that a producer rewrites data
in datastare with the same data and it trigger DataTreeChangeEvent
so RendererManager thinks that data was changed but it was not.

Change-Id: Idc145f37351899e1fa9eb70f62a00c8c7d54ebaf
Signed-off-by: Martin Sunal <msunal@cisco.com>

Integrated VBD to VPP renderer for VXLAN

VBD with VXLAN tunnels is created when endpoint location
contains external-node-mount-point but there is no such VPP node
in VBD topology(L2FD from network-containment)

Change-Id: Ic557558f9ff4236f0d801b9a63b44dcadb077b26
Signed-off-by: Martin Sunal <msunal@cisco.com>

Added executor for netconf callback processing

fixed problem when reply from netconf server comes
in netty thread and callback uses this thread for
communication with netconf server again.

Change-Id: I59d1ba03630472fc412e5e230f7b5c5dc546a98f
Signed-off-by: Martin Sunal <msunal@cisco.com>

Merge "Implementing VBD API in Vpp renderer"

Resolved policy sidepanel

- added sidepanel templates
- showing EPGs, contracts in sidepanel

Change-Id: Iedee7f45e6253d9b434b0b08414652568748c007
Signed-off-by: Ľubomír Balogh <lubomir.balogh@pantheon.sk>

Implementing VBD API in Vpp renderer

Change-Id: I424f90ea3984cf01eb9e384c1f3e761e7443f428
Signed-off-by: Michal Cmarada <mcmarada@cisco.com>
Signed-off-by: Martin Sunal <msunal@cisco.com>

Fixed cyclic renderer config update

After renderer processes configuration and reports status
it trigger RendererManager which take this as change
which generates creating of new configuration for renderer.
So this cyclic behavior is fixed in this commit.

Change-Id: I086e6c63d1e8da34943807a940aafe644ad2ae59
Signed-off-by: Martin Sunal <msunal@cisco.com>

Implemented vhostuser port assignation to BD

Change-Id: I236a37797168a5a861a90917efc0f1f18a571776
Signed-off-by: Martin Sunal <msunal@cisco.com>

Tests for NeutronRouterAware

ATTENTION: depends on https://git.opendaylight.org/gerrit/39947

Change-Id: I00d83b39bf385c0cf2f960a171fbcd38dcb0d0da
Signed-off-by: Konstantin Blagov <kblagov@cisco.com>

Unit tests for neutron mapper (parent commit)

- base setup for DataStore testing
- tests for SecurityGroupAware, PortAware

Change-Id: I99ba280c96d60cd1b3e3d1e4923823a8344b5721
Signed-off-by: Konstantin Blagov <kblagov@cisco.com>

Merge "Adding Neutron Physical Provider network model. Allows relating Neutron providers to device physical interfaces"

Resolved policy contracts

resolved-policy data grouped by source and destination epg and contract

Change-Id: I040cfd8e10afbc7b491c063d812d794f69761d33
Signed-off-by: Daniel Malachovsky <dmalacho@cisco.com>

Adding Neutron Physical Provider network model.
Allows relating Neutron providers to device physical interfaces

Change-Id: I2016e0545d1956e2808cc563e04abfe50a1c50c9
Signed-off-by: Wojciech Dec <wdec@cisco.com>

Merge "Change Location Resolver DS to Configuration"

Merge "updated gitignore for log files"

Change Location Resolver DS to Configuration

Change-Id: I06c48db6f50ccb77246296d341905de0f42e39b5
Signed-off-by: Michal Cmarada <mcmarada@cisco.com>

Endpoint added

-work on add endpoint dialog - adding works -is  without value checking
-work on add endpoint dialog

-ctrl, services, tpl added
-sidePannel with EP details works

Change-Id: If63c80cfc185b94a1e478cf004ff26cd74e9116a
Signed-off-by: michal.kovacik <michal.kovacik@pantheon.tech>
Endpoints - ordering fixed
+small code corrections

Change-Id: Ice0cc083053a4a49b03cb5870214c6f81a8333f9
Signed-off-by: michal.kovacik <michal.kovacik@pantheon.tech>
Endpoint's side pannel CSS corrected

Change-Id: Iaf235f94e100c36edd14b9e9452640ecc450ebc8
Signed-off-by: michal.kovacik <michal.kovacik@pantheon.tech>

resolved-policy view - initial commit

- added sidepanel
- opening resolved-policy detail in sidepanel

Change-Id: Ib2ed0da6b0ad5b9a8731e9b099a68639244da57e
Signed-off-by: Ľubomír Balogh <lubomir.balogh@pantheon.sk>

Merge "Next Topology component"

updated gitignore for log files

Change-Id: Iadb863d180f5784b14c0350528e30fed76963e2a
Signed-off-by: Keith Burns (alagalah) <alagalah@gmail.com>

Introduced InterfaceManager in VPP renderer

- creates vhostuser interfaces on VPP (vhostuser interface
  is not assigned to any bridge domain)
- trigger is creating of vpp-endpoint from on vpp-renderer.yang
- does not handle case when a netconf device is connected
  after vpp-endpoint was created

Change-Id: I11ea9e0446d9297129b9a928a8417b95944739e1
Signed-off-by: Martin Sunal <msunal@cisco.com>
Signed-off-by: Michal Cmarada <mcmarada@cisco.com>

Implementing VPP Renderer registration

Change-Id: I516aa14fd96f0931dfd3a1e60a40c0cdec6b041a
Signed-off-by: Michal Cmarada <mcmarada@cisco.com>

Merge "Update of mapping neutron port to vpp endpoint"

Merge "ios-xe-renderer node manager update"

Update of mapping neutron port to vpp endpoint

Ports are mapped to vpp endpoints only if:
  - device owner is a compute or dhcp node
  - vif_type is vhostuser

Socket ID of vpp endpoints consists of:
  - vhostSocketPath + vhostSocketPrefix + portUUID

Incorporated the vpp-node property in vpp endpoints
which provides basic info about location of an endpoint.
Addition of dependency on network topology was needed.

Removing original vpp endpoints as a first step on neutron
port update events in case that updated ports are not
validated as vpp endpoints anymore.

Change-Id: I02ebf69c261a9103a2f62c06520e4bc0ca66f57b
Signed-off-by: Tomas Cechvala <tcechval@cisco.com>

Unit tests for ofoverlay

Change-Id: I1b3773ac70a0ce2d00ed4bf0e97d3eb0462eaa0b
Signed-off-by: Konstantin Blagov <kblagov@cisco.com>

ios-xe-renderer node manager update

    - capability check
    - ability to update/remove node
    - unit test

Signed-off-by: Vladimir Lavor <vlavor@cisco.com>
Signed-off-by: Michal Rehak <mirehak@cisco.com>
Change-Id: Ieae273163e2cdf8e8ae79ef079e9fd53003011d9

Added vpp-node-path to vpp-renderer.yang

- vpp-node-path represents path to the vpp mont-point

Change-Id: If2028b4bd99e27a6223a12aa6ea55cd41c1b2eb5
Signed-off-by: Martin Sunal <msunal@cisco.com>

added translation of augments to AddrEpWithLocation

Change-Id: I8db75b2fa7b0f68160dc9d32d0844a91bd91f3c5
Signed-off-by: Matej Perina <matej.perina@pantheon.sk>

Merge "Add Vhost User implementation for VPP"

Adding necessary VPP mapper attributes and config parameters.
Renaming the VPP Provider to GbpVppProvider to accommodate other VPP Provider.

Change-Id: I10dca53f2ac8321442c9aca6b04f087af9c2c8b3
Signed-off-by: Wojciech Dec <wdec@cisco.com>

Merge "Fixed EIG creation"

additional tests for NeLocationProvider

Change-Id: I3e85f8363253894eb18d7c215997b4d43582bb3e
Signed-off-by: Matej Perina <matej.perina@pantheon.sk>

Next Topology component

Change-Id: I1670cca3f162b5dadfd24f84814a7a38ae4cddc7
Signed-off-by: Daniel Malachovsky <dmalacho@cisco.com>

Add Vhost User implementation for VPP

Change-Id: I3e2245e5152e8129f607fdcd632d84aabfe83c05
Signed-off-by: Michal Cmarada <mcmarada@cisco.com>

Merge "fixes for several logical bugs"

Merge "Moved l2-l3 forwarding to domain-extensions"

Fixed EIG creation

EIG is created only if the isExternal property
in a neutron network says true.

Signed-off-by: Tomas Cechvala <tcechval@cisco.com>

Merge "Code coverage increasing for faas-renderer"

fixes for several logical bugs

Fixes concurent transactions in NeLocationProvider, NullPointerException
in RendererUtils, registration of ForwardingResolver
and logical bugs in RendererManager

Change-Id: I9a09caafcf18fb309a682cd33de9a9fd09b95390
Signed-off-by: Matej Perina <matej.perina@pantheon.sk>

Moved l2-l3 forwarding to domain-extensions

domain-extensions is location for all domain specific
extensions of forwarding and endpoints.
Purpose of puting a domain specific extension
to domain-extensions is that multiple renderers
can depends on it.

The first domain specific extension is l2-l3 (layer 2 and layer 3).
The l2-l3 extension extends forwarding with
L2 and L3 specific contexts and network domains.
It is expected to have L2, L3 augmentations of an endpoint here.

Change-Id: I85e8bc1040acc7ce95a3b5bb9f65ad0e183e12fb
Signed-off-by: Martin Sunal <msunal@cisco.com>

Merge "Fixed IDs of contracts for EIG"

Code coverage increasing for faas-renderer

Change-Id: I7e57e76617976770255287af101ae9054614d5fd
Signed-off-by: Konstantin Blagov <kblagov@cisco.com>

Baseline for neutron-vpp mapping

Initial implementation of neutron-vpp mapper
Initial yang for vpp renderer

Change-Id: Ief0fbc85e68f9c094c9c0ca6687c132cbd8ca6ea
Signed-off-by: Tomas Cechvala <tcechval@cisco.com>

Fixed IDs of contracts for EIG

Signed-off-by: Martin Sunal <msunal@cisco.com>

ios-xe renderer - increase unit test converage

Change-Id: I3e0500813ea761500abf1b859116e92fea2bb338
Signed-off-by: Michal Rehak <mirehak@cisco.com>

ios-xe renderer - features

    - features
    - artifacts
    - config

Change-Id: I1c42cabc69dd0b02268fc5b82fd15a10e12f9ce0
Signed-off-by: Michal Rehak <mirehak@cisco.com>

ios-xe renderer - config compression

    - added PolicyManger's delegate for state compressing
    - unit test

Change-Id: I21435048ef710feeb4631ee15e69daa7992235bc
Signed-off-by: Michal Rehak <mirehak@cisco.com>

ios-xe renderer - policy manager + mapper

- policy manager create case
- class-map mapping
- first hop sff
- added PolicyManager interface
- node listener

Signed-off-by: Vladimir Lavor <vlavor@cisco.com>
Change-Id: Ifd1ef7a312927c442aecf02cc04c0ae9acfb1de7

Introducing new API in neutron-mapper

New forwarding and endpoint model incorporated in
Neutron-Mapper component.

Former forwarding and endpoint API still supported.

Change-Id: Iaa851ec8ab0e7cbf1d04a45d2796b0b87f8e2b3e
Signed-off-by: Tomas Cechvala <tcechval@cisco.com>

ios-xe renderer - listeners+cache

    - added listeners for template and renderer-policy
    - wired listeners
    - added cache for templates
    - tests

Signed-off-by: Michal Rehak <mirehak@cisco.com>
Change-Id: I307091a0d4791b731ea418b926475954dffa09e7

ios-xe renderer - initial push

    - config subsystem binding
    - bootstrap provider
    - ned.yang
    - artifacts involved

Change-Id: Ib8d0afe1d4922404f91081ed80bb20124d76b996
Signed-off-by: Michal Rehak <mirehak@cisco.com>
Signed-off-by: Vladimir Lavor <vlavor@cisco.com>

Merge "Introduced DomainSpecificRegistry service"

Merge "Introduced ForwardingResolver"

Introduced DomainSpecificRegistry service

- the service allows to register augmentors(entity which translates data
  from one augmentation to the other) for domain specific data
- this service starts:
  - BaseEndpointService implementation
  - RendererManger

Domain specific data can be augmented into:
  - address-endpoint-reg, containment-endpoint-reg from RPC register-endpoint (base-endpoint.yang)
    EndpointAugmentor has to be provided in order to propagate augmentations
    to all places
  - forwarding/forwarding-by-tenant/network-domain (forwarding.yang)
    NetworkDomainAugmentor has to be provided in order to propagate augmentations
    to all places

Change-Id: Iaa9a0684651bb53279007de9472341d0e7fe4a4b
Signed-off-by: Martin Sunal <msunal@cisco.com>

Rename common.yang

    - file common.yang contains module gbp-common which
      makes yang processing tools (e.g. pyang) complain
      about missing files
    - according to best practices yang file should have
      the same name as module + '.yang' suffix

Change-Id: I6fc458a9544987bb33e992e98e6dd6cc556717b5
Signed-off-by: Michal Rehak <mirehak@cisco.com>

Introduced ForwardingResolver

- ForwardingResolver listens on forwarding in CONF and stores it to OPER DS
- PolicyResolver changed: listens on tenant without waiting for input from
  renderers

Change-Id: I3119d195452c9a69990c9ab3b574a5204e14b2ef
Signed-off-by: Martin Sunal <msunal@cisco.com>

Merge "Adding name param for forwarding enties:"

Test coverage increasing for iovisor.restclient

Change-Id: I931a58b7386680bf79bdec6860f1550bb5f03bb9
Signed-off-by: Konstantin Blagov <kblagov@cisco.com>

Merge "Tests coverage increasing for iovisor.endpoint"

Merge "Tests for Iovisor root package"

Merge "Tests for iovisor.sf"

Tests coverage increasing for iovisor.endpoint

Change-Id: Ibf87f90000a5e26f2ae5dbe61634b6c0cfac9c0a
Signed-off-by: Konstantin Blagov <kblagov@cisco.com>

Tests for iovisor.sf

Change-Id: I0ed495c712dca33070deda229a318fa1f6722339
Signed-off-by: Konstantin Blagov <kblagov@cisco.com>

Tests for Iovisor root package

Change-Id: Ied5c4af08189bfff2e089c760d9a6a90ba003c1a
Signed-off-by: Konstantin Blagov <kblagov@cisco.com>

Introducing VPP renderer

Initial yang for vpp renderer

Change-Id: I60ab30fa6cc471134271b02282987e05aa1b46c6
Signed-off-by: Michal Cmarada <mcmarada@cisco.com>

Adding name param for forwarding enties:

 - forwarding-context
 - network-domain

Change-Id: I9a079b307449cbce94c7b27d7841fab623ad6718
Signed-off-by: Tomas Cechvala <tcechval@cisco.com>

Merge "Tenant dialogs"

Merge "EPG CRUD"

Merge "Add, Edit, Del contracts"

Merge "contracts, index, rootGBPcontroller"

Introduced Renderer Manager

Renderer manager dispatches policy configuration among endoints
to renderers.
Renderer manager gets data notifications about:
- Endoints (base-endpoint.yang)
- EndpointLocations (base-endpoint.yang)
- ResolvedPolicies (resolved-policy.yang)
- Forwarding (forwarding.yang)

Based on data from notifications it creates a configuration for renderers.
Configuration is stored to CONF DS as Renderers (renderer.yang)

Configuration is sign with version which is incremented by every change.
All rendrers are suposed to be on the same version. Renderer manager waits
for all renderers to respond with version update in OPER DS. After a version
of every renderer in OPER DS is same as version in CONF DS, renderer manager
moves to the next configuration with incremented version.

Change-Id: I475b357d5d60444dc359bc400c567d9d0e36238f
Signed-off-by: Martin Sunal <msunal@cisco.com>

introduced LocationResolver

LocationResolver collects data from all location providers
and union them to EndpointLocations

Change-Id: I60308ba59ab0f17085f3a85ec7d99e2ee2b4307b
Signed-off-by: Matej Perina <matej.perina@pantheon.sk>

Update of BaseEndpointRpcRegistry

- adding Verification of RPC Input
- adding update of Endpoints in op DS
- Unit tests

Change-Id: Ic709f7a47f3aeed7e46201d17ed54d297c8031bc
Signed-off-by: Michal Cmarada <mcmarada@cisco.com>

Add, Edit, Del contracts

It's possible to Add, Edit, Delete Contract via UI now
amend: comments removed

Change-Id: I16265d54a9523ce93e75bc447c17f6e5a29064f4
Signed-off-by: michal.kovacik <michal.kovacik@pantheon.tech>

Added missing order to policy-rule-group

- policy-rule-group should contain order
- fixed fields of containment-endpoint-with-location in renderer.yang

Signed-off-by: Martin Sunal <msunal@cisco.com>

Containment endpoint can only have relative location

Containment endpoint must not contain real location because
containment endpoint represents part of forwarding context
which is out of policy domain(It also means that containment endpoint
can be located only in EIG EPG)

Change-Id: I7b7147c2c23f7bf1bcca116c99970dbb52e9707d
Signed-off-by: Martin Sunal <msunal@cisco.com>

Merge "Editing network containment of endpoints"

EPG CRUD

Signed-off-by: Ľubomír Balogh <lubomir.balogh@pantheon.sk>

Merge "initial contracts work"

Merge "New tests for listeners"

Editing network containment of endpoints

Network containment can refer to
 - forwarding-context, e.g. l2-flood-domain
 - network-domain, e.g. subnet

Signed-off-by: Tomas Cechvala <tcechval@cisco.com>

Tenant dialogs

- edit dialog
- delete dialog

Signed-off-by: Martin Péter Lakatoš <martin.lakatos@pantheon.tech>

contracts, index, rootGBPcontroller

Change-Id: I4fb9494b967bc64d22fb2f39a4c4e2779f7ced09
Signed-off-by: michal.kovacik <michal.kovacik@pantheon.tech>

Simplified renderer API

Pros
- renderer API is more clear
- easy to process config by renderer
- fixes cases which were not possible to have eg.:
  EP1--EPG_BLUE---SUBJECT_1---(P)EPG_PURPLE--EP2
  EP3--EPG_RED----SUBJECT_1---(P)EPG_GREY--EP4
Cons
- repeated data for endpoints with same policy

This commit also depricates domain specific endpoint contstraints
in policy.yang

Signed-off-by: Martin Sunal <msunal@cisco.com>

New tests for listeners

Change-Id: I1fccb761c5e1cfae742d03b18a98c093a3af6aa4
Signed-off-by: Konstantin Blagov <kblagov@cisco.com>