Age | Commit message (Collapse) | Author | Files | Lines |
|
Fixed issues with vnfapi install:
- Resolved issue installing vnftools by converting to blueprint
- Resolved issue not finding RPC implementation of vnfapi by fixing
dependency feature vnftools, and by converting vnfapi to blueprint.
The root cause in both cases was probably something wrong with the
provider configuration, but it was simpler (not to mention more
maintainable) to just convert from config to blueprint.
Change-Id: I7010a845687673c932457774f3103834d328ab84
Issue-ID: SDNC-119
Signed-off-by: Dan Timoney <dtimoney@att.com>
|
|
Replace following deprecated API
1) NotificationProviderService replaced with NotificationPublishService
2) InstanceIdentifier<T> toInstance() replace with build()
3) setProperties replaced with setYangMappingProperties
Change-Id: I89fba42e88363c5e1e5b23fe272d2754361aee25
Issue-Id: SDNC-89
Signed-off-by: Gaurav Agrawal <gaurav.agrawal@huawei.com>
|
|
Split dmaap-listener and ueb-listener to separate artifacts
Change-Id: I7b1d5b15c8ef850ace75d4da451143ba4062b817
Signed-off-by: Dan Timoney <dtimoney@att.com>
|
|
Port to OpenDaylight Boron and sync updates since 16.10
Change-Id: I036c5d0bb600b305300e653023caffc83a262604
Signed-off-by: Dan Timoney <dtimoney@att.com>
|
|
Change-Id: Iffe4d4fbcfd21ecbc1000238354094cc064298ce
Signed-off-by: Dan Timoney <dtimoney@att.com>
|