On Thu, Feb 8, 2018 at 9:15 AM, Jamie G. <jamie.goody...@gmail.com> wrote:
> You could always use Blueprint with Config Management; you're able to > set default values in BP, than override via config file. > > ex: > > <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" > xmlns:cm="http://aries.apache.org/blueprint/xmlns/ > blueprint-cm/v1.1.0"> > > <cm:property-placeholder persistent-id="com.foo.bar” > update-strategy="reload"> > <cm:default-properties> > <cm:property name=“fooProp” value="false"/> > <cm:property name=“barProp” value=“127.0.0.1”/> > <cm:property name="bizProp” value=“1500”/> > </cm:default-properties> > </cm:property-placeholder> > yeah we use that in some places. We also have our own BP extension, clustered-app-config, that reads from the DS and listens for updates. The main advantage is that's it's clustered. > > On Thu, Feb 8, 2018 at 10:38 AM, Tom Pantelis <tompante...@gmail.com> > wrote: > > > > > > On Thu, Feb 8, 2018 at 8:56 AM, Sam Hague <sha...@redhat.com> wrote: > >> > >> > >> > >> On Thu, Feb 8, 2018 at 8:54 AM, Sam Hague <sha...@redhat.com> wrote: > >>> > >>> What is the preferred or suggested best practice for service level > >>> configuration? There are two methods we have been using and would like > to > >>> know the pros and cons of each. Genius and NetVirt went with the > blueprint > >>> xmls and openflowplugin and ovsdb went with the cfg's. > >> > >> This seems confusing to end users to have two different methods of > >> configuration. > > > > > > The clustered-app-config has advantages outlined in > > https://wiki.opendaylight.org/view/Using_Blueprint#Applicati > on_configuration. > > However it does require the data store so in some cases may not want that > > dependency or can't, like infrautls. Not sure why OFP and ovsdb opted > for > > cfg files - perhaps that was before clustered-app-config? > > > >>> > >>> > >>> 1. blueprint xml > >>> - more odl/mdsal like since they are yang files > >>> - can be cluster aware - not sure on this > >>> > >>> 2. cfg's > >>> - simple text file rather than xml > >>> - have to explicitly add them to each odl node, could have conflicts > >>> > >>> Thanks, Sam > >> > >> > >> > >> _______________________________________________ > >> Discuss mailing list > >> Discuss@lists.opendaylight.org > >> https://lists.opendaylight.org/mailman/listinfo/discuss > >> > > > > > > _______________________________________________ > > Discuss mailing list > > Discuss@lists.opendaylight.org > > https://lists.opendaylight.org/mailman/listinfo/discuss > > >
_______________________________________________ Discuss mailing list Discuss@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/discuss