Kepler

Another way of doing site documentation(Figure 1 in https://kepler-project.org/developers/incubation/kepler-engineering-view-for-reap/engineering-view-plans), is to design it until the data logger or a starting point and get all the sensor connected to the data logger (or another URL).

This could potantially be done using SPAN APIs.

This could also be used to validate the site documentation later on based on a kar (bug 4744).

save to metacat instead of dataturbine?

uploading site layouts should be similar to the existing functionality that uploads workflows to the repository.

changing bugs from REAP to Kepler product

Saving a Site Layout to a kar works. Uploading and then downloading this kar from the kepler repository works as expected too.
I think one usecase driving this bug was the need to keep a record of the state of a site at a point in time, and technically this is solved by the above. I made a change to a sensor's sampling rate, then opened the old kar and did a Configure Actor on the sensor and saw the old sampling rate. However I don't think our systems really make this all that clear. We can consider this and open new bugs as appropriate.

Original Bugzilla ID was 4745