Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [kura-dev] changing config from outside kura

Hi Scott,

maybe a look here [1] helps you. I did create a docker image with Artemis adding as a DP. And pre-configured using the "snapshot_0.xml" file. So the Dockerfile does create a derived Kura image with Artemis and its configuration added during the Docker-build. When Kura starts up everything is pre-configured.

Hope this helps.

Jens

On Wed, Nov 1, 2017 at 7:11 PM, De Alti, Cristiano <Cristiano.DeAlti@xxxxxxxxxxxx> wrote:

Hi,

  Bruno, everything you have said is correct and it’s the preferred way to customize a Kura installation before the very first Kura boot.

 

Regards,

  Cristiano

 

From: <kura-dev-bounces@xxxxxxxxxxx> on behalf of "Bruno.Vetter@xxxxxxxxxxxxxxxx" <Bruno.Vetter@xxxxxxxxxxxxxxxx>
Reply-To: Kura Developers mailing list <kura-dev@xxxxxxxxxxx>
Date: Wednesday, November 1, 2017 at 17:23
To: Kura Developers mailing list <kura-dev@xxxxxxxxxxx>
Subject: Re: [kura-dev] changing config from outside kura

 

Hi Scott,

it is not bound to Chef at all. Kura keeps all components' configurations in a file /opt/eclipse/kura/data/snapshots/snapshot_xxxxxxx.xml. Whenever you edit a configuration via web console, Kura saves a new snapshot file containing all components' configurations. You can modify these configuration files easily. My understanding is that when Kura starts up it reads the most recent snapshot file it can find in the folder /opt/eclipse/kura/data and applies the contents to the deployed components.

When you install Kura from scratch, you will find a basic snapshot_0.xml in the folder. Kura will encrypt this file on first startup, and all further snapshots will be encrypted before they are written to the filesytem. One way to retrieve a non-encrypted snapshot is to download it from the web ui.

I keep unencrypted custom snapshot files on my Chef server. I provide them to the folder mentioned before and restart Kura, so it reads the file and applies the config. I am not 100% sure how Kura deals with unencrypted snapshot files when there are encrypted files in the folder, so I usually delete all snapshot files from the folder before providing a custom snapshot_0.xml.

I think this is not the officially recommended way to configure Kura (as it's not documented), but it works fine. I need to manage a large number of Kura devices and definitely need a way to provide xml based templates as a basis for configuration. The MQTT approach doesn't fit there.

Kind regards
Bruno


nactive hide details for "Lewis, ScottX" ---01.11.2017 17:04:41---Hi Brun"Lewis, ScottX" ---01.11.2017 17:04:41---Hi Bruno, In answer to your question...no we don't mind restarting Kura.  Actually our initial use c

Von: "Lewis, ScottX" <scottx.lewis@xxxxxxxxx>
An: Kura Developers mailing list <kura-dev@xxxxxxxxxxx>
Datum: 01.11.2017 17:04
Betreff: Re: [kura-dev] changing config from outside kura
Gesendet von: kura-dev-bounces@xxxxxxxxxxx





Hi Bruno,

In answer to your question...no we don't mind restarting Kura.  Actually our initial use case for this is deploying for the first time to 'clean' hardware.   But in any event, is your method for accessing config info via snapshot files available?  Is it bound to Chef in particular or can it be used in other ways?

Thanks,

Scott



From: kura-dev-bounces@eclipse.org [kura-dev-bounces@xxxxxxxxxxx] on behalf of Bruno.Vetter@xxxxxxxxxxxxxxxx [Bruno.Vetter@xxxxxxxxxxxxxxxx]
Sent:
 Wednesday, November 01, 2017 12:50 AM
To:
 Kura Developers mailing list
Subject:
 Re: [kura-dev] changing config from outside kura

Hello Scott,

do you mind restarting your Kura instance? We are using Chef to administrate our Kura devices and we access the configuration data via the snapshot files. A configuration change means updating the snapshot xml file on the kura device, and then restarting. Kura will load the new configuration.


Kind regards
Bruno


nactive hide details for "Lewis, ScottX" ---30.10.2017 17:07:03---Hi, We "Lewis, ScottX" ---30.10.2017 17:07:03---Hi, We would like to be able to change the kura config admin information (i.e. some persistent data

Von:
"Lewis, ScottX" <scottx.lewis@xxxxxxxxx>
An:
"kura-dev@xxxxxxxxxxx" <kura-dev@xxxxxxxxxxx>
Datum:
30.10.2017 17:07
Betreff:
[kura-dev] changing config from outside kura
Gesendet von:
kura-dev-bounces@xxxxxxxxxxx





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


_______________________________________________
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



--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
_____________________________________________________________________________

Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill

Back to the top