You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+41Lines changed: 41 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,46 @@ platform provides services for collecting and storing data from buildings and
8
8
devices and provides an environment for developing applications which interact
9
9
with that data.
10
10
11
+
## Upgrading to VOLTTRON 8.x
12
+
13
+
VOLTTRON 8 introduces three changes that require an explict upgrade step when upgrading from a earlier VOLTTRON version
14
+
15
+
1. Dynamic RPC authorization feature - This requires a modification to the auth file. If you have a pre-existing
16
+
instance of VOLTTRON running on an older version, the auth file will need to be updated.
17
+
2. Historian agents now store the cache database (backup.sqlite file) in
18
+
<volttron home>/agents/<agent uuid>/<agentname-version>/<agentname-version>.agent-data directory instead of
19
+
<volttron home>/agents/<agent uuid>/<agentname-version> directory. In future all core agents will write data only
20
+
to the <agentname-version>.agent-data subdirectory. This is because vctl install --force backs up and restores
21
+
only the contents of this directory.
22
+
3. SQLHistorians (historian version 4.0.0 and above) now use a new database schema where metadata is stored in
23
+
topics table instead of separate metadata table. SQLHistorians with version >= 4.0.0 can work with existing
24
+
database with older schema however the historian agent code should be upgraded to newer version (>=4.0.0) to run
25
+
with VOLTTRON 8 core.
26
+
27
+
To upgrade:
28
+
29
+
1. If upgrading historian, make sure historians are not in auto start mode. To remove any historian from auto start
30
+
mode use the command 'vctl disable <uuid of historian that is currently enabled>. This is necessary so that the old
31
+
sqlhistorian does not automatically start after step 5.
32
+
2. Update volttron source code version to VOLTTRON 8
33
+
3. activate the volttron environment, and run ```python bootstrap.py --force```. If you have
34
+
any additional bootstrap options that you need (rabbitmq, web, drivers, etc.) include these in the above command.
35
+
4. Run ```volttron-upgrade``` to update the auth file and move historian cache files into agent-data directory.
36
+
Note that the upgrade script will only move the backup.sqlite file and will not move sqlite historian's db file
37
+
if they are within the install directory. If using a SQLite historian, please backup the database file of
38
+
sqlite historian before upgrading to the latest historian version.
39
+
5. Start VOLTTRON
40
+
6. Run ```vctl install --force --vip-identity <vip id of existing historian> --agent-config <config>``` to upgrade
41
+
to the latest historian version. vctl install --force will backup the cache in <agent-version>.agent-data
42
+
folder, installs the latest version of the historian and restore the contents of
43
+
<agent-version>.agent-data folder.
44
+
45
+
### Upgrading aggregate historians
46
+
47
+
VOLTTRON 8 also comes with updated SQL aggregate historian schema. However, there is no automated upgrade path for
48
+
aggregate historian. To upgrade an existing aggregate historian please refer to the CHANGELOG.md within
49
+
SQLAggregateHistorian source directory
50
+
11
51
## Features
12
52
13
53
-[Message Bus](https://volttron.readthedocs.io/en/latest/platform-features/message-bus/index.html) allows agents to subscribe to data sources and publish results and messages.
@@ -295,6 +335,7 @@ There are several walkthroughs to explore additional aspects of the platform:
295
335
- [RabbitMQ setup with Federation and Shovel plugins](https://volttron.readthedocs.io/en/latest/deploying-volttron/multi-platform/multi-platform-rabbitmq-deployment.html)
296
336
- [Backward compatibility with the RabbitMQ message bus](https://volttron.readthedocs.io/en/latest/deploying-volttron/multi-platform/multi-platform-multi-bus.html)
297
337
338
+
298
339
## Acquiring Third Party Agent Code
299
340
300
341
Third party agents are available under the volttron-applications repository. In
This section includes individual documents describing important changes to platform components. For information on specific release, please refer to the corresponding document.
0 commit comments