summaryrefslogtreecommitdiffstats
path: root/v3po/translate-api/src/main
AgeCommit message (Collapse)AuthorFilesLines
2016-07-29HONEYCOMB-130: Separate v3po plugin from HC infraMaros Marsalek25-1504/+0
Creating folders: - common/ - infra/ - v3po/ - vpp-common/ Change-Id: I2c39e1b17e39e7c0f0628f44aa5fe08563fa06e4 Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
2016-07-25HONEYCOMB-122: Reader registry integration testsMaros Marsalek2-2/+12
Add IT test for read infrastructure + some additional unit tests + Make Read/Write Factory autoCloseable Change-Id: I6eab8e6df2c2132af01cea0a9c4b9bece7dc9b74 Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
2016-07-21HONEYCOMB-122 Update reader registry to share similar APIs as writerMaros Marsalek17-155/+368
+ Extract common registry builder base code (Reader registry is not flat, so there is not full control over ordering as with writers but it is sufficient) + Split CompositeReader into CompositeReader, SubtreeReader and GenericReader + No need to build composite structure in ReaderFactories (registry does that internally) + Keep only ReaderCustomizer + ListReaderCustomizer, no root reader (same for writers) Change-Id: Ic4e5bc96ad47a6cbcada4efcc2209db5c16d2a6c Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
2016-07-13HONEYCOMB-94 Reimplement writer registry with better ordering optionsMaros Marsalek7-91/+362
Now the registry is flat and allows for full control of writer execution order Change-Id: I864e1d676588ffe59b596145e0829e81b1a1ed2f Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
2016-06-27HONEYCOMB-100: introduce default 5s timeoutMarek Gradzki1-2/+14
in TranslateUtils.getReplyFor* calls Change-Id: Iac2bb428ea6adcc8d3da2238db1dec708df550f0 Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
2016-06-10HONEYCOMB-33: Add notification service to HcMaros Marsalek1-0/+5
Implement VPP interface notification translator as part of v3po2vpp plugin Change-Id: I69cfad9668ae9e4d79ed30bb8d54d294faa4c54a Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
2016-05-23HONEYCOMB-61: Add BA broker for context data treeMaros Marsalek5-32/+121
With broker, context data can be accessed in a transactional manner, same as config data + Renamed data-api concepts to not include DataTree + Renamed context related concepts to better distinguish between them + Now passing full ReadContext to read customizers + Naming context is backed by context data broker Change-Id: I0b2876dd74a31a9ced7d9b5145672868e12f8b82 Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
2016-04-12HONEYCOMB-9: Migrate Interface listenerMaros Marsalek5-97/+163
Change-Id: Iffde1ee21b749a8c8efa96c243f7f8bb0811b4c7 Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
2016-04-12HONEYCOMB-9: Add configuration and wiring for readers and writersMaros Marsalek1-0/+37
Remove config module Wrap vpp-japi in a config module Change-Id: Iee1e0c653309bd3c1019323ce689dacf3ed995cd Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
2016-04-12HONEYCOMB-9: Remove references to VPP from translation layerMaros Marsalek14-0/+801
Change-Id: I281db366a112edc08203e8cb392a212708d4552a Signed-off-by: Maros Marsalek <mmarsale@cisco.com>