1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
|
.. _ndbdebug:
Debug and logging
=================
Logging
-------
A simple way to set up stderr logging::
# to start logging on the DB init
ndb = NDB(log='on')
# ... or to start it in run time
ndb.log('on')
# ... the same as above, another syntax
ndb.log.on
# ... turn logging off
ndb.log('off')
# ... or
ndb.log.off
It is possible also to set up logging to a file or to a syslog server::
#
ndb.log('file_name.log')
#
ndb.log('syslog://server:port')
Fetching DB data
----------------
By default, NDB starts with an in-memory SQLite3 database. In order to
perform post mortem analysis it may be more useful to start the DB with
a file DB or a PostgreSQL as the backend.
See more: :ref:`ndbschema`
It is possible to dump all the DB data with `schema.export()`::
with NDB() as ndb:
ndb.schema.export('stderr') # dump the DB to stderr
...
ndb.schema.export('pr2_debug') # dump the DB to a file
RTNL events
-----------
All the loaded RTNL events may be stored in the DB. To turn that feature
on, one should start NDB with the `debug` option::
ndb = NDB(rtnl_debug=True)
The events may be exported with the same `schema.export()`.
Unlike ordinary table, limited with the number of network objects in the
system, the events log tables are not limited. Do not enable the events
logging in production, it may exhaust all the memory.
RTNL objects
------------
NDB creates RTNL objects on demand, it doesn't keep them all the time.
References to created objects are linked to the `ndb.<view>.cache` set::
>>> ndb.interfaces.cache.keys()
[(('target', u'localhost'), ('index', 2)),
(('target', u'localhost'), ('index', 39615))]
>>> [x['ifname'] for x in ndb.interfaces.cache.values()]
[u'eth0', u't2']
Object states
-------------
RTNL objects may be in several states:
* invalid: the object does not exist in the system
* system: the object exists both in the system and in NDB
* setns: the existing object should be moved to another network namespace
* remove: the existing object must be deleted from the system
The state transitions are logged in the state log::
>>> from pyroute2 import NDB
>>> ndb = NDB()
>>> c = ndb.interfaces.create(ifname='t0', kind='dummy').commit()
>>> c.state.events
[
(1557752212.6703758, 'invalid'),
(1557752212.6821117, 'system')
]
The timestamps allow to correlate the state transitions with the
NDB log and the RTNL events log, in the case it was enabled.
Object snapshots
----------------
Before running any commit, NDB marks all the related records in the DB
with a random value in the `f_tflags` DB field (`tflags` object field),
and stores all the marked records in the snapshot tables. Shortly, the
`commit()` is a `snapshot() + apply() + revert() if failed`::
>>> nic = ndb.interfaces['t0']
>>> nic['state']
'down'
>>> nic['state'] = 'up'
>>> snapshot = nic.snapshot()
>>> ndb.schema.snapshots
{
'addresses_139736119707256': <weakref at 0x7f16d8391a98; to 'Interface' at 0x7f16d9c708e0>,
'neighbours_139736119707256': <weakref at 0x7f16d8391a98; to 'Interface' at 0x7f16d9c708e0>,
'routes_139736119707256': <weakref at 0x7f16d8391a98; to 'Interface' at 0x7f16d9c708e0>,
'nh_139736119707256': <weakref at 0x7f16d8391a98; to 'Interface' at 0x7f16d9c708e0>,
'p2p_139736119707256': <weakref at 0x7f16d8391a98; to 'Interface' at 0x7f16d9c708e0>,
'ifinfo_bridge_139736119707256': <weakref at 0x7f16d8391a98; to 'Interface' at 0x7f16d9c708e0>,
'ifinfo_bond_139736119707256': <weakref at 0x7f16d8391a98; to 'Interface' at 0x7f16d9c708e0>,
'ifinfo_vlan_139736119707256': <weakref at 0x7f16d8391a98; to 'Interface' at 0x7f16d9c708e0>,
'ifinfo_vxlan_139736119707256': <weakref at 0x7f16d8391a98; to 'Interface' at 0x7f16d9c708e0>,
'ifinfo_gre_139736119707256': <weakref at 0x7f16d8391a98; to 'Interface' at 0x7f16d9c708e0>,
'ifinfo_vrf_139736119707256': <weakref at 0x7f16d8391a98; to 'Interface' at 0x7f16d9c708e0>,
'ifinfo_vti_139736119707256': <weakref at 0x7f16d8391a98; to 'Interface' at 0x7f16d9c708e0>,
'ifinfo_vti6_139736119707256': <weakref at 0x7f16d8391a98; to 'Interface' at 0x7f16d9c708e0>,
'interfaces_139736119707256': <weakref at 0x7f16d8391a98; to 'Interface' at 0x7f16d9c708e0>
}
>>> nic.apply()
...
>>> nic['state']
'up'
>>> snapshot.apply(rollback=True)
...
>>> nic['state']
'down'
Or same::
>>> nic = ndb.interfaces['t0']
>>> nic['state']
'down'
>>> nic['state'] = 'up'
>>> nic.commit()
>>> nic['state']
'up'
>>> nic.rollback()
>>> nic['state']
'down'
These snapshot tables are the objects' state before the changes were applied.
|
