Move adsal into its own subdirectory. Moved various adsal components into an opendaylight/adsal subdir, gave it a parent pom, and changed the root parent pom to have the opendaylight/adsal as a module. Change-Id: I1d0e5a7b2a50c65559c2f80dd47cab491b68d561 Signed-off-by: Ed Warnicke <eaw@cisco.com>
Incrementing versions by 0.1.0 for post-Helium master branch * The only version not incrmented is aaa.version, which is left at 0.1.0-SNAPSHOT since they depend on controller and can't update yet. * To break the cyclic dependency, this patch temporarily stops running the netconf-connector and restconf feature tests. * Also fixing a bug causing Errors like "Choice has two nodes case with same qnames". A second patch (to be run after AAA increments their versions to 0.2.0-SNAPSHOT) wiil update aaa.version and re-enable these tests. Change-Id: I70a3987d32504e798c5ed05a67a0a1174338844b Signed-off-by: Colin Dixon <colin@colindixon.com> Signed-off-by: Robert Varga <rovarga@cisco.com>
Configuration service uses an inconsistent hashcode in the clustered data structure - Using Enum in the Key field of a clustered data structure can lead to propagation issues, because the clustering services implementation relay on a consistent hashcode to be calculated. So replaced the Java Enum used in configuration.implementation bundle with String. Change-Id: Id36ac46c9f38859d5325fc4f2e8674c9c3828ec4 Signed-off-by: Giovanni Meo <gmeo@cisco.com>
Unify maven-bundle-plugin version at 2.4.0 This removes superfluous version declarations, fixing about 70 eclipse warnings. At the same time it bumps the version 2.4.0, to unify it -- we were using both 2.3.7 and 2.4.0 at the same time. Change-Id: I0f3f6b68c5c05cb9cc226f75b4eb4dab7d58651d Signed-off-by: Robert Varga <rovarga@cisco.com>
Adding auto-sorting plugin to all Controller via parent/pom.xml leveraging google's sortpom plugin, all controller poms are sorted at build time as per the opendaylight/commons/parent/pom.xml configuration. Sorted lists of properties, dependencies, and plugins will increase pom readability and help prevent duplicate entry errors. This first submission is huge as I changed one pom.xml and all are then sorted. Only if the sortpom plugin is reconfigured will all pom's again be changed. Note that if any pom.xml is pushed without having been through a build ... folks are going to see pom.xml files showup as modified unintentionally. Change-Id: I8553f38b9f0e5f6d27177ad6b9b9c35a4b43d55a Signed-off-by: jameshall03885 <ghall@brocade.com>
ConfigurationService to create default config dir - Have ConfigurationService create a default startup config directory, so that container unaware apps/modules can initiate and individual save. - Semantic fixes in IConfigurationContainerService - Bump configuration api rev since methods were added since last rev Change-Id: Ifec274c258859a402f6dad7394c43c28ed162b95 Signed-off-by: Yevgeny Khodorkovsky <ykhodork@cisco.com>
Fix for container directory creation/deletion in startup without saving config Change-Id: I423e7c3ab186af5ea5bd0ab6d42553b4f988e82f Signed-off-by: Diti Bhatia <dibhatia@cisco.com>
Backward compatibility change for Configuration Service - Now that config save is no longer bound to infinispan cache type contraint of ConcurrentMap, need to assure old configuration still serialized as concurrent maps can be still be read. Change-Id: I6b4404b2280fa923391aeee02cf56ed9a8847552 Signed-off-by: Alessandro Boch <aboch@cisco.com>
Migrate bundles' configuration mgmt to ConfigurationService - Change current logic where read/save config is completely managed by each bundle, with moving it to configuration manager. This decoupling will allow configuration manager to decide how to persist the bundles' configurations to disk, withouth necessarely depend on java serialization as today controlelr does. Also now file names can be static and each bundle does not need to track the container context in the file name (which was lame). This allow controller to erase container startup files on container removal, which was not possible today. - Global and in container configuration services to expose two APIs for the other bundles to retrieve and save their config - Per container startup files organized in directories (directory name = container name) - Container startup directory removed on container removal, and created on container creation if not present Change-Id: I58c283eb796cf2a60466a97162428a8c2ae478ae Signed-off-by: Alessandro Boch <aboch@cisco.com>
Fixed inappropriate uses of log level INFO This is done per the recommendation here: https://wiki.opendaylight.org/view/Draft_Syslog_Level_Settings Change-Id: I69bbe15d81ed49511f643fd4a8c0ad60f58a0c22 Signed-off-by: Ed Warnicke <eaw@cisco.com>
Migrate all artifact versions to dependencyManagement - Migrate all the artifacts to use dependencyManagement to centralize the version changes in controller and make sure the dry-run for release could actually rewrite those. Change-Id: I510e4f15d6d75ec52d49835600338fa069a5a4f6 Signed-off-by: Giovanni Meo <gmeo@cisco.com>
Update to new version of ADSAL components and its dependencies proposed by jenkins-controller-version-changes-8 By splitting the effort into 2 phases, it is more managable and easy to test. After this commit, the ADSAL components and all the NSFs are uptodate with the dependency convergence. Signed-off-by: Madhu Venugopal <mavenugo@gmail.com> Change-Id: Ia8f0a0d2959f8f6ea61babe9c3f826d0950dcaf5
Fix star import and enable checkstyle rule to prevent it. Change-Id: I62a1b8e3e85c2575939c3710524a98c91227648d Signed-off-by: Alissa Bonas <abonas@redhat.com>
Reworked pom files Each pom (artifact) declares it's dependencies (internal and external) No dependencies declared at parent POM level, only dependency Management. Also moved the <modules> from distribution/opendaylight to the root pom.xml distribution/opendaylight now builds entirely from dependencies I have intentionally left some things in here I think are wrong, because the goal of this commit is to reproduce the existing build (which it does, I've checked). Subsequent commits will clean up other things. Change-Id: I358bdac1c0f6a59b37a418a811a30235967fdfdc Signed-off-by: Tony Tkacik <ttkacik@cisco.com>
Per container save configuration is not synced in the cluster ISSUE: When container administrator saves the configuration on GUI, the configurations for the containers on which he has write permission are onlyu saved on the local controller. CHANGE: Have ContainerConfigurationService manage its own event sync cache for this specific case. ContainerConfigurationService.saveConfigurations() gets invoked only when container adminidtrator trigger the save.For the save config triggered by system or network administrator, things work as today, it is handled by ConfigurationService which syncs the config event to the other ConfigurationServices in the cluster. Change-Id: I961558579292fd10b0d8ee601aa64f3a3843b0ed Signed-off-by: Alessandro Boch <aboch@cisco.com>