Re: [kura-dev] changing config from outside kura

["Lewis, ScottX" <scottx.lewis@xxxxxxxxx>]

Hi Dave,

I'll take a look at this doc.  It would be best if we could setup the configuration without running Kura at all...or rather before running Kura at all.   We just want to be able to configure things like listening ports, some of our service configurations before starting anything at all....e.g. from a shell script that's run once to configure things before starting.

But if we need to start framework, configure over MQTT and restart we could probably do that...so I will consult the document, thanks.

FWIW...seems like [3] could be represented as a set of OSGi remote services.

Scott

________________________________________
From: kura-dev-bounces@xxxxxxxxxxx [kura-dev-bounces@xxxxxxxxxxx] on behalf of Woodard, David [david.woodard@xxxxxxxxxxxx]
Sent: Tuesday, October 31, 2017 4:09 PM
To: Kura Developers mailing list
Subject: Re: [kura-dev] changing config from outside kura

Hi Scott,

The most common way to do this is over MQTT. We have a Cloudlet [1] implemented in the framework that works directly with the Kura ConfigurationService. If you haven’t, please review this document [2]. It is a pretty dense document, the section related to remote config management is here [3]. If this isn’t what you are looking for, please let me know.

[1] http://download.eclipse.org/kura/docs/api/3.1.0/apidocs/org/eclipse/kura/cloud/Cloudlet.html
[2] http://eclipse.github.io/kura/ref/mqtt-namespace.html
[3] http://eclipse.github.io/kura/ref/mqtt-namespace.html#remote-osgi-configurationadmin-interactions-via-mqtt

Thanks,
--Dave


On 10/30/17, 09:06, "kura-dev-bounces@xxxxxxxxxxx on behalf of Lewis, ScottX" <kura-dev-bounces@xxxxxxxxxxx on behalf of scottx.lewis@xxxxxxxxx> wrote:

    Hi,

    We would like to be able to change the kura config admin information (i.e. some persistent data for some components) from outside of a running kura instance.   For example, from a shell script.  The idea is to automate some of the configuration of our components prior to deployment.

    Is there an API for this...or some other procedure?  I wasn't able to find with casual search, so forgiveness if it's there and I didn't find.

    Thanksinadvance,

    Scott
    _______________________________________________
    kura-dev mailing list
    kura-dev@xxxxxxxxxxx
    To change your delivery options, retrieve your password, or unsubscribe from this list, visit
    https://dev.eclipse.org/mailman/listinfo/kura-dev


_______________________________________________
kura-dev mailing list
kura-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kura-dev