search

deanhiller / databus

time series data in cassandra with visualization(NREL's opensource databus project)
Other
53 stars 21 forks source link

Remove demo data from Production Mode #24

Closed hopcroft closed 10 years ago

hopcroft commented 10 years ago

When a new DataBus installation is created, it is populated with lots of "demo" data, like agg1Db, groupofusersandgroups, etc. This is useful for Demo mode, but not for Production. Note this demo data is created in Production mode for installations that are not using Active Directory. [Priority: high]

hopcroft commented 10 years ago

Related request: an easy way (or any way) to erase an existing DataBus configuration, including users, groups, databases, charts, etc. Basically a "reset" function.

deanhiller commented 10 years ago

This should not be the case. what are your steps for starting databus for the very first time? Was it the documentation on buffalosw.com or??? (I want to walk through the steps myself and see what we have wrong in the documentation and fix that). Resetting is like resetting with any database technology then which is to delete all data in the database and restart the system.

ps. we just added linear interpolation and a special attribute on sumstreamsV2 where you can have nulls returned if 1 of the streams is null(ie. you want to show the graph is out as one of the streams is dead rather than show a dip in the total energy which people might think we saved energy but really it was one stream went down).

hopcroft commented 10 years ago

My basic steps for installation are:

1) git pull the latest code 2) build 3) run units test (fail, but ignore that) 4) run in dev mode (./play run) to verify installation and network settings 5) run in demo mode (./startDemo.sh) to log in, see help file, look at new chart features, etc. 6) modify application.conf for the installation. Set admin users, (no AD), port numbers, cassandra, etc. 7) run in production mode (./startProduction.sh). Create databases, groups, robots, etc.

I have deleted all the files in /var/lib/cassandra/data and /commitlog, and it does not seem to affect the test data present in DataBus. Are the lists of users and groups stored in cassandra, or in some other file? When using the inmemory database, where are the users and groups stored?

On 17Sep2013, at 06:34 , deanhiller wrote:

This should not be the case. what are your steps for starting databus for the very first time? Was it the documentation on buffalosw.com or??? (I want to walk through the steps myself and see what we have wrong in the documentation and fix that). Resetting is like resetting with any database technology then which is to delete all data in the database and restart the system.

ps. we just added linear interpolation and a special attribute on sumstreamsV2 where you can have nulls returned if 1 of the streams is null(ie. you want to show the graph is out as one of the streams is dead rather than show a dip in the total energy which people might think we saved energy but really it was one stream went down).

— Reply to this email directly or view it on GitHub.

deanhiller commented 10 years ago

ok, this should now be fixed in that demo.mode=false and domain=none and application.mode=prod and lastly upgrade.mode=NEW (this setting is really just for performance not for data population)

with those settings, only admin user will be added to an empty database. Please let me know if this does not work. thanks, Dean