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: Documentation/polycubed/polycubed.rst
+28-1Lines changed: 28 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,34 @@ If the same parameter is specified in both, the configuration file and the comma
54
54
daemon: true
55
55
#p: 6000 <-- this is NOT supported, only long options are
56
56
57
+
58
+
59
+
Persistency
60
+
^^^^^^^^^^^
61
+
62
+
Polycubed has persistent capabilities, which means that (1) it can automatically load the configuration that was present when the daemon was shut down, (2) each time a configuration command is issued, it is automatically dumped on disk.
63
+
This enables polycubed also to recover from failures, such as rebooting the machine.
64
+
By default, the daemon keeps in memory an instance of all the topology, including the configuration of each individual service.
65
+
Topology and configuration are automatically updated at each new command; the configuration is also dumped to disk, on file ``/etc/polycube/cubes.yaml``.
66
+
The standard behavior of the daemon at startup is to load the latest topology that was active at the end of the previous execution.
67
+
Users can load a different topology file by using the ``--cubes-dump`` flag followed by the path to the file.
68
+
In case we want to start polycubed with an empty topology, avoiding any possible load at startup, we can launch polycubed with the ``--cubes-init`` flag. Beware that in this case any existing configuration in the default file will be overwritten.
69
+
Finally, persistency can be disabled with the ``--cubes-nodump`` flag; this would also avoid any (very limited) performance penalty introduced by this feature.
70
+
71
+
::
72
+
73
+
# start polycubed with custom cubes configuration
74
+
polycubed --cubes-dump ~/Desktop/myCubes.yaml
75
+
76
+
# start polycubed with an empty topology
77
+
polycubed --cubes-init
78
+
79
+
# start daemon without topology saving functionalities
0 commit comments