netbox-stratagram 1.0.2__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- netbox_stratagram-1.0.2/LICENSE +202 -0
- netbox_stratagram-1.0.2/NOTICE +6 -0
- netbox_stratagram-1.0.2/PKG-INFO +142 -0
- netbox_stratagram-1.0.2/README.md +122 -0
- netbox_stratagram-1.0.2/THIRD-PARTY-LICENSES.txt +563 -0
- netbox_stratagram-1.0.2/netbox_stratagram/__init__.py +46 -0
- netbox_stratagram-1.0.2/netbox_stratagram/data.py +251 -0
- netbox_stratagram-1.0.2/netbox_stratagram/editor_build.py +2 -0
- netbox_stratagram-1.0.2/netbox_stratagram/migrations/0001_initial.py +40 -0
- netbox_stratagram-1.0.2/netbox_stratagram/migrations/__init__.py +3 -0
- netbox_stratagram-1.0.2/netbox_stratagram/models.py +34 -0
- netbox_stratagram-1.0.2/netbox_stratagram/static/netbox_stratagram/editor/32e6bb316fa7/app.js +752 -0
- netbox_stratagram-1.0.2/netbox_stratagram/static/netbox_stratagram/editor/32e6bb316fa7/canvas.js +1303 -0
- netbox_stratagram-1.0.2/netbox_stratagram/static/netbox_stratagram/editor/32e6bb316fa7/panel.js +731 -0
- netbox_stratagram-1.0.2/netbox_stratagram/static/netbox_stratagram/editor/32e6bb316fa7/pkg/stratagram_web.js +1128 -0
- netbox_stratagram-1.0.2/netbox_stratagram/static/netbox_stratagram/editor/32e6bb316fa7/pkg/stratagram_web_bg.wasm +0 -0
- netbox_stratagram-1.0.2/netbox_stratagram/static/netbox_stratagram/editor/32e6bb316fa7/stratagram.css +421 -0
- netbox_stratagram-1.0.2/netbox_stratagram/static/netbox_stratagram/netbox.js +121 -0
- netbox_stratagram-1.0.2/netbox_stratagram/templates/netbox_stratagram/diagram.html +40 -0
- netbox_stratagram-1.0.2/netbox_stratagram/urls.py +12 -0
- netbox_stratagram-1.0.2/netbox_stratagram/views.py +198 -0
- netbox_stratagram-1.0.2/netbox_stratagram.egg-info/PKG-INFO +142 -0
- netbox_stratagram-1.0.2/netbox_stratagram.egg-info/SOURCES.txt +25 -0
- netbox_stratagram-1.0.2/netbox_stratagram.egg-info/dependency_links.txt +1 -0
- netbox_stratagram-1.0.2/netbox_stratagram.egg-info/top_level.txt +1 -0
- netbox_stratagram-1.0.2/pyproject.toml +34 -0
- netbox_stratagram-1.0.2/setup.cfg +4 -0
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
|
@@ -0,0 +1,142 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: netbox-stratagram
|
|
3
|
+
Version: 1.0.2
|
|
4
|
+
Summary: NetBox plugin: network diagrams of sites, drawn and edited in NetBox with Stratagram
|
|
5
|
+
Author: Shin Sterneck
|
|
6
|
+
License-Expression: Apache-2.0
|
|
7
|
+
Project-URL: Homepage, https://stratagram.app/
|
|
8
|
+
Project-URL: Source, https://github.com/shinsterneck/stratagram
|
|
9
|
+
Project-URL: Issues, https://github.com/shinsterneck/stratagram/issues
|
|
10
|
+
Keywords: netbox,netbox-plugin,diagram,topology
|
|
11
|
+
Classifier: Framework :: Django
|
|
12
|
+
Classifier: Programming Language :: Python :: 3
|
|
13
|
+
Classifier: Programming Language :: Python :: 3 :: Only
|
|
14
|
+
Requires-Python: >=3.12.0
|
|
15
|
+
Description-Content-Type: text/markdown
|
|
16
|
+
License-File: LICENSE
|
|
17
|
+
License-File: NOTICE
|
|
18
|
+
License-File: THIRD-PARTY-LICENSES.txt
|
|
19
|
+
Dynamic: license-file
|
|
20
|
+
|
|
21
|
+
# NetBox Stratagram
|
|
22
|
+
|
|
23
|
+
Network diagrams of NetBox sites, drawn from their devices and cables and
|
|
24
|
+
edited in the browser on each site's **Diagram** tab, with the Stratagram
|
|
25
|
+
editor (the same as the desktop app, compiled to WebAssembly).
|
|
26
|
+
|
|
27
|
+
- The first time, the tab draws the site as NetBox has it: devices with
|
|
28
|
+
their cabled interfaces as ports, cables as lines, laid out top down
|
|
29
|
+
(internet and firewalls above, servers below). Device types come from the
|
|
30
|
+
device roles, line types from the interfaces (802.1Q trunk, layer 3 when
|
|
31
|
+
routed on both ends, layer 2 for access ports). Provider circuits become
|
|
32
|
+
clouds. Patch panels (by role, or devices with front ports and no other
|
|
33
|
+
role) are drawn with numbered sockets, one per front port, of the front
|
|
34
|
+
ports' type (RJ45, LC or SC), and as wide as they need. Cables to front
|
|
35
|
+
ports plug into their sockets, cables to rear ports come out behind the
|
|
36
|
+
socket of the front port they map to. Switches show their front too: their
|
|
37
|
+
physical interfaces as ports, odd ones on top and even ones below, copper
|
|
38
|
+
ones first and the others as SFP uplinks, each cable in its port.
|
|
39
|
+
- Each of the site's locations gets a sheet of its own after the site's:
|
|
40
|
+
the devices in the location (and in the locations inside it), plus the
|
|
41
|
+
devices elsewhere they are cabled to, on the layer "Other locations"
|
|
42
|
+
(marked with its name). A location's own **Diagram** tab shows the
|
|
43
|
+
site's diagram open on that sheet.
|
|
44
|
+
- Each type of device is on a layer of its own (Internet, Firewalls,
|
|
45
|
+
Routers, Switches, Patch panels, Servers...) and the cables on the layer
|
|
46
|
+
Cables, to show or hide them by type; each device has a sub-layer of its
|
|
47
|
+
own under its type's, named after it (renamed with it), to show or hide
|
|
48
|
+
devices one by one (unfold the type's layer with ▸). The cabling stays end to end: with
|
|
49
|
+
the patch panels hidden, a server's line goes straight to the switch port
|
|
50
|
+
it is patched through to (NetBox's cable path), and hidden cables take
|
|
51
|
+
their end-to-end lines with them. A diagram saved before this gets the
|
|
52
|
+
layers at its next **Refresh from NetBox** (what you drew yourself stays
|
|
53
|
+
where it is; a device you later move to another layer stays there).
|
|
54
|
+
- Arrange it, add notes, a frame, layers..., then **Save**: the diagram is
|
|
55
|
+
kept in NetBox (one per site, in the change log).
|
|
56
|
+
- **Refresh from NetBox** adds new devices and cables, renames what was
|
|
57
|
+
renamed and sets aside what is gone on the layer "Gone from NetBox";
|
|
58
|
+
nothing you placed moves, and Ctrl+Z undoes it. It does so on every
|
|
59
|
+
sheet: renamed locations rename their sheets, and new locations get new
|
|
60
|
+
sheets (a diagram saved before locations had sheets gets them too).
|
|
61
|
+
- Export SVG, PNG or draw.io from the editor's Export menu.
|
|
62
|
+
- Light, Dark and Neon themes (the selector in the editor's toolbar): the
|
|
63
|
+
editor follows NetBox's own light/dark switch until you pick one, which
|
|
64
|
+
is then remembered in your browser. SVG and PNG exports come out in the
|
|
65
|
+
theme; the saved diagram keeps its colors.
|
|
66
|
+
|
|
67
|
+
Requires NetBox 4.5, 4.6 or 4.7.
|
|
68
|
+
|
|
69
|
+
## Install
|
|
70
|
+
|
|
71
|
+
Install it from [PyPI](https://pypi.org/project/netbox-stratagram/) into
|
|
72
|
+
NetBox's virtual environment:
|
|
73
|
+
|
|
74
|
+
```sh
|
|
75
|
+
sudo /opt/netbox/venv/bin/pip install netbox-stratagram
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
With [netbox-docker](https://github.com/netbox-community/netbox-docker), add
|
|
79
|
+
`netbox-stratagram` to `plugin_requirements.txt` and build the image (see
|
|
80
|
+
netbox-docker's guide to plugins; `collectstatic` is part of it).
|
|
81
|
+
|
|
82
|
+
To build the package yourself (needs Rust with the `wasm32-unknown-unknown`
|
|
83
|
+
target and `wasm-bindgen-cli` 0.2.129, see the main README, `pip install
|
|
84
|
+
build`, and `cargo install cargo-about` for the licenses of the libraries
|
|
85
|
+
built into the editor, which go into the package as
|
|
86
|
+
`THIRD-PARTY-LICENSES.txt`):
|
|
87
|
+
|
|
88
|
+
```sh
|
|
89
|
+
netbox-plugin/build.sh # makes netbox-plugin/dist/netbox_stratagram-*.whl
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
and install that wheel instead. Then enable the plugin in `configuration.py`:
|
|
93
|
+
|
|
94
|
+
```python
|
|
95
|
+
PLUGINS = ["netbox_stratagram"]
|
|
96
|
+
PLUGINS_CONFIG = {
|
|
97
|
+
"netbox_stratagram": {
|
|
98
|
+
# Device type by device role (slug or name), before the built-in guesses.
|
|
99
|
+
"kinds": {"patch-panel": "switch", "dmz-host": "server"},
|
|
100
|
+
# Also draw devices without a cable to another device.
|
|
101
|
+
"all_devices": False,
|
|
102
|
+
# Each type of device on a layer of its own, the cables on one.
|
|
103
|
+
"type_layers": True,
|
|
104
|
+
# How the cables run, and new lines drawn by hand: "orthogonal",
|
|
105
|
+
# "straight" or "around" (orthogonal, around devices in between).
|
|
106
|
+
"routing": "orthogonal",
|
|
107
|
+
# Device types drawn with their ports as a front, like a switch's:
|
|
108
|
+
# any of "switch", "router", "firewall", "server".
|
|
109
|
+
"fronts": ["switch"],
|
|
110
|
+
},
|
|
111
|
+
}
|
|
112
|
+
```
|
|
113
|
+
|
|
114
|
+
Then, as for any plugin:
|
|
115
|
+
|
|
116
|
+
```sh
|
|
117
|
+
python3 manage.py migrate
|
|
118
|
+
python3 manage.py collectstatic --no-input
|
|
119
|
+
```
|
|
120
|
+
|
|
121
|
+
Your web server should serve `.wasm` files as `application/wasm` (nginx
|
|
122
|
+
does by default; elsewhere the editor still loads, a little slower).
|
|
123
|
+
|
|
124
|
+
## Permissions
|
|
125
|
+
|
|
126
|
+
The Diagram tab (of sites and locations) shows to those who may view the
|
|
127
|
+
site and *site diagrams* (`netbox_stratagram.view_sitediagram`); grant it
|
|
128
|
+
to everyone who should see the diagrams (superusers have it). A saved
|
|
129
|
+
diagram outside the constraints of their view permission is not shown
|
|
130
|
+
(nor can it be saved over). Drawn afresh or refreshed, the drawing only has
|
|
131
|
+
the devices and cables they may view.
|
|
132
|
+
|
|
133
|
+
Saving needs the permission to add (the first time) or change site
|
|
134
|
+
diagrams (`netbox_stratagram.add_sitediagram`,
|
|
135
|
+
`netbox_stratagram.change_sitediagram`), with their constraints: a diagram
|
|
136
|
+
saved outside them (constraints on `site__region`, say) is undone and the
|
|
137
|
+
save refused, as in NetBox's own edit views.
|
|
138
|
+
|
|
139
|
+
## License
|
|
140
|
+
|
|
141
|
+
Copyright 2026 Shin Sterneck. Licensed under the Apache License, Version
|
|
142
|
+
2.0; the package includes the license and the NOTICE file.
|
|
@@ -0,0 +1,122 @@
|
|
|
1
|
+
# NetBox Stratagram
|
|
2
|
+
|
|
3
|
+
Network diagrams of NetBox sites, drawn from their devices and cables and
|
|
4
|
+
edited in the browser on each site's **Diagram** tab, with the Stratagram
|
|
5
|
+
editor (the same as the desktop app, compiled to WebAssembly).
|
|
6
|
+
|
|
7
|
+
- The first time, the tab draws the site as NetBox has it: devices with
|
|
8
|
+
their cabled interfaces as ports, cables as lines, laid out top down
|
|
9
|
+
(internet and firewalls above, servers below). Device types come from the
|
|
10
|
+
device roles, line types from the interfaces (802.1Q trunk, layer 3 when
|
|
11
|
+
routed on both ends, layer 2 for access ports). Provider circuits become
|
|
12
|
+
clouds. Patch panels (by role, or devices with front ports and no other
|
|
13
|
+
role) are drawn with numbered sockets, one per front port, of the front
|
|
14
|
+
ports' type (RJ45, LC or SC), and as wide as they need. Cables to front
|
|
15
|
+
ports plug into their sockets, cables to rear ports come out behind the
|
|
16
|
+
socket of the front port they map to. Switches show their front too: their
|
|
17
|
+
physical interfaces as ports, odd ones on top and even ones below, copper
|
|
18
|
+
ones first and the others as SFP uplinks, each cable in its port.
|
|
19
|
+
- Each of the site's locations gets a sheet of its own after the site's:
|
|
20
|
+
the devices in the location (and in the locations inside it), plus the
|
|
21
|
+
devices elsewhere they are cabled to, on the layer "Other locations"
|
|
22
|
+
(marked with its name). A location's own **Diagram** tab shows the
|
|
23
|
+
site's diagram open on that sheet.
|
|
24
|
+
- Each type of device is on a layer of its own (Internet, Firewalls,
|
|
25
|
+
Routers, Switches, Patch panels, Servers...) and the cables on the layer
|
|
26
|
+
Cables, to show or hide them by type; each device has a sub-layer of its
|
|
27
|
+
own under its type's, named after it (renamed with it), to show or hide
|
|
28
|
+
devices one by one (unfold the type's layer with ▸). The cabling stays end to end: with
|
|
29
|
+
the patch panels hidden, a server's line goes straight to the switch port
|
|
30
|
+
it is patched through to (NetBox's cable path), and hidden cables take
|
|
31
|
+
their end-to-end lines with them. A diagram saved before this gets the
|
|
32
|
+
layers at its next **Refresh from NetBox** (what you drew yourself stays
|
|
33
|
+
where it is; a device you later move to another layer stays there).
|
|
34
|
+
- Arrange it, add notes, a frame, layers..., then **Save**: the diagram is
|
|
35
|
+
kept in NetBox (one per site, in the change log).
|
|
36
|
+
- **Refresh from NetBox** adds new devices and cables, renames what was
|
|
37
|
+
renamed and sets aside what is gone on the layer "Gone from NetBox";
|
|
38
|
+
nothing you placed moves, and Ctrl+Z undoes it. It does so on every
|
|
39
|
+
sheet: renamed locations rename their sheets, and new locations get new
|
|
40
|
+
sheets (a diagram saved before locations had sheets gets them too).
|
|
41
|
+
- Export SVG, PNG or draw.io from the editor's Export menu.
|
|
42
|
+
- Light, Dark and Neon themes (the selector in the editor's toolbar): the
|
|
43
|
+
editor follows NetBox's own light/dark switch until you pick one, which
|
|
44
|
+
is then remembered in your browser. SVG and PNG exports come out in the
|
|
45
|
+
theme; the saved diagram keeps its colors.
|
|
46
|
+
|
|
47
|
+
Requires NetBox 4.5, 4.6 or 4.7.
|
|
48
|
+
|
|
49
|
+
## Install
|
|
50
|
+
|
|
51
|
+
Install it from [PyPI](https://pypi.org/project/netbox-stratagram/) into
|
|
52
|
+
NetBox's virtual environment:
|
|
53
|
+
|
|
54
|
+
```sh
|
|
55
|
+
sudo /opt/netbox/venv/bin/pip install netbox-stratagram
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
With [netbox-docker](https://github.com/netbox-community/netbox-docker), add
|
|
59
|
+
`netbox-stratagram` to `plugin_requirements.txt` and build the image (see
|
|
60
|
+
netbox-docker's guide to plugins; `collectstatic` is part of it).
|
|
61
|
+
|
|
62
|
+
To build the package yourself (needs Rust with the `wasm32-unknown-unknown`
|
|
63
|
+
target and `wasm-bindgen-cli` 0.2.129, see the main README, `pip install
|
|
64
|
+
build`, and `cargo install cargo-about` for the licenses of the libraries
|
|
65
|
+
built into the editor, which go into the package as
|
|
66
|
+
`THIRD-PARTY-LICENSES.txt`):
|
|
67
|
+
|
|
68
|
+
```sh
|
|
69
|
+
netbox-plugin/build.sh # makes netbox-plugin/dist/netbox_stratagram-*.whl
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
and install that wheel instead. Then enable the plugin in `configuration.py`:
|
|
73
|
+
|
|
74
|
+
```python
|
|
75
|
+
PLUGINS = ["netbox_stratagram"]
|
|
76
|
+
PLUGINS_CONFIG = {
|
|
77
|
+
"netbox_stratagram": {
|
|
78
|
+
# Device type by device role (slug or name), before the built-in guesses.
|
|
79
|
+
"kinds": {"patch-panel": "switch", "dmz-host": "server"},
|
|
80
|
+
# Also draw devices without a cable to another device.
|
|
81
|
+
"all_devices": False,
|
|
82
|
+
# Each type of device on a layer of its own, the cables on one.
|
|
83
|
+
"type_layers": True,
|
|
84
|
+
# How the cables run, and new lines drawn by hand: "orthogonal",
|
|
85
|
+
# "straight" or "around" (orthogonal, around devices in between).
|
|
86
|
+
"routing": "orthogonal",
|
|
87
|
+
# Device types drawn with their ports as a front, like a switch's:
|
|
88
|
+
# any of "switch", "router", "firewall", "server".
|
|
89
|
+
"fronts": ["switch"],
|
|
90
|
+
},
|
|
91
|
+
}
|
|
92
|
+
```
|
|
93
|
+
|
|
94
|
+
Then, as for any plugin:
|
|
95
|
+
|
|
96
|
+
```sh
|
|
97
|
+
python3 manage.py migrate
|
|
98
|
+
python3 manage.py collectstatic --no-input
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
Your web server should serve `.wasm` files as `application/wasm` (nginx
|
|
102
|
+
does by default; elsewhere the editor still loads, a little slower).
|
|
103
|
+
|
|
104
|
+
## Permissions
|
|
105
|
+
|
|
106
|
+
The Diagram tab (of sites and locations) shows to those who may view the
|
|
107
|
+
site and *site diagrams* (`netbox_stratagram.view_sitediagram`); grant it
|
|
108
|
+
to everyone who should see the diagrams (superusers have it). A saved
|
|
109
|
+
diagram outside the constraints of their view permission is not shown
|
|
110
|
+
(nor can it be saved over). Drawn afresh or refreshed, the drawing only has
|
|
111
|
+
the devices and cables they may view.
|
|
112
|
+
|
|
113
|
+
Saving needs the permission to add (the first time) or change site
|
|
114
|
+
diagrams (`netbox_stratagram.add_sitediagram`,
|
|
115
|
+
`netbox_stratagram.change_sitediagram`), with their constraints: a diagram
|
|
116
|
+
saved outside them (constraints on `site__region`, say) is undone and the
|
|
117
|
+
save refused, as in NetBox's own edit views.
|
|
118
|
+
|
|
119
|
+
## License
|
|
120
|
+
|
|
121
|
+
Copyright 2026 Shin Sterneck. Licensed under the Apache License, Version
|
|
122
|
+
2.0; the package includes the license and the NOTICE file.
|