├── docs ├── configuration.md ├── modeling │ ├── duplex_circuits.md │ ├── pon_circuits.md │ ├── simplex_circuits.md │ ├── wdm_circuits.md │ ├── key_components.md │ ├── Untitled Diagram.drawio │ └── core_concepts.md ├── installation.md ├── features.md └── index.md ├── README.md ├── mkdocs.yml ├── .gitignore ├── netbox_optical_setup.py └── LICENSE /docs/configuration.md: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /docs/modeling/duplex_circuits.md: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /docs/modeling/pon_circuits.md: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /docs/modeling/simplex_circuits.md: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /docs/modeling/wdm_circuits.md: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /docs/installation.md: -------------------------------------------------------------------------------- 1 | # Installation -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # netbox-optical 2 | A Netbox plugin designed to fully integrate optical network modeling and planning. 3 | -------------------------------------------------------------------------------- /docs/modeling/key_components.md: -------------------------------------------------------------------------------- 1 | 2 | - Attenuators? 3 | - Full power budget specs for transceivers (min/max TX, min/max RX) 4 | - IL field for adapters and transceivers 5 | - Attenuation coefficient field for cables 6 | - First class cables 7 | - Splice loss? 8 | - Splice records? -------------------------------------------------------------------------------- /docs/modeling/Untitled Diagram.drawio: -------------------------------------------------------------------------------- 1 | UzV2zq1wL0osyPDNT0nNUTV2VTV2LsrPL4GwciucU3NyVI0MMlNUjV1UjYwMgFjVyA2HrCFY1qAgsSg1rwSLBiADYTaQg2Y1AA== -------------------------------------------------------------------------------- /mkdocs.yml: -------------------------------------------------------------------------------- 1 | site_name: Netbox Optical Documentation 2 | site_url: https://netbox-optical.telecomcraft.com 3 | repo_name: telecomcraft/netbox-optical 4 | repo_url: https://github.com/telecomcraft/netbox-optical 5 | edit_uri: edit/main/docs/ 6 | theme: 7 | name: material 8 | icon: 9 | repo: fontawesome/brands/github 10 | palette: 11 | - media: "(prefers-color-scheme: light)" 12 | scheme: default 13 | toggle: 14 | icon: material/lightbulb-outline 15 | name: Switch to Dark Mode 16 | - media: "(prefers-color-scheme: dark)" 17 | scheme: slate 18 | toggle: 19 | icon: material/lightbulb 20 | name: Switch to Light Mode 21 | extra: 22 | social: 23 | - icon: fontawesome/brands/github 24 | link: https://github.com/telecomcraft/netbox-optical 25 | - icon: fontawesome/brands/twitter 26 | link: https://www.twitter.com/thetelecomcraft 27 | markdown_extensions: 28 | - admonition 29 | nav: 30 | - Introduction: 'index.md' 31 | - Features: 'features.md' 32 | - Installation: 'installation.md' 33 | - Configuration: 'configuration.md' 34 | - Modeling: 35 | - Core Concepts: 'modeling/core_concepts.md' 36 | - Key Components: 'modeling/key_components.md' 37 | - Simplex Circuits: 'modeling/simplex_circuits.md' 38 | - Duplex Circuits: 'modeling/duplex_circuits.md' 39 | - PON Circuits: 'modeling/pon_circuits.md' 40 | - WDM Circuits: 'modeling/wdm_circuits.md' 41 | - Testing: '' 42 | - Reporting: '' 43 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # Byte-compiled / optimized / DLL files 2 | __pycache__/ 3 | *.py[cod] 4 | *$py.class 5 | 6 | # C extensions 7 | *.so 8 | 9 | # Distribution / packaging 10 | .Python 11 | build/ 12 | develop-eggs/ 13 | dist/ 14 | downloads/ 15 | eggs/ 16 | .eggs/ 17 | lib/ 18 | lib64/ 19 | parts/ 20 | sdist/ 21 | var/ 22 | wheels/ 23 | pip-wheel-metadata/ 24 | share/python-wheels/ 25 | *.egg-info/ 26 | .installed.cfg 27 | *.egg 28 | MANIFEST 29 | 30 | # PyInstaller 31 | # Usually these files are written by a python script from a template 32 | # before PyInstaller builds the exe, so as to inject date/other infos into it. 33 | *.manifest 34 | *.spec 35 | 36 | # Installer logs 37 | pip-log.txt 38 | pip-delete-this-directory.txt 39 | 40 | # Unit test / coverage reports 41 | htmlcov/ 42 | .tox/ 43 | .nox/ 44 | .coverage 45 | .coverage.* 46 | .cache 47 | nosetests.xml 48 | coverage.xml 49 | *.cover 50 | *.py,cover 51 | .hypothesis/ 52 | .pytest_cache/ 53 | 54 | # Translations 55 | *.mo 56 | *.pot 57 | 58 | # Django stuff: 59 | *.log 60 | local_settings.py 61 | db.sqlite3 62 | db.sqlite3-journal 63 | 64 | # Flask stuff: 65 | instance/ 66 | .webassets-cache 67 | 68 | # Scrapy stuff: 69 | .scrapy 70 | 71 | # Sphinx documentation 72 | docs/_build/ 73 | 74 | # PyBuilder 75 | target/ 76 | 77 | # Jupyter Notebook 78 | .ipynb_checkpoints 79 | 80 | # IPython 81 | profile_default/ 82 | ipython_config.py 83 | 84 | # pyenv 85 | .python-version 86 | 87 | # pipenv 88 | # According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control. 89 | # However, in case of collaboration, if having platform-specific dependencies or dependencies 90 | # having no cross-platform support, pipenv may install dependencies that don't work, or not 91 | # install all needed dependencies. 92 | #Pipfile.lock 93 | 94 | # PEP 582; used by e.g. github.com/David-OConnor/pyflow 95 | __pypackages__/ 96 | 97 | # Celery stuff 98 | celerybeat-schedule 99 | celerybeat.pid 100 | 101 | # SageMath parsed files 102 | *.sage.py 103 | 104 | # Environments 105 | .env 106 | .venv 107 | env/ 108 | venv/ 109 | ENV/ 110 | env.bak/ 111 | venv.bak/ 112 | 113 | # Spyder project settings 114 | .spyderproject 115 | .spyproject 116 | 117 | # Rope project settings 118 | .ropeproject 119 | 120 | # mkdocs documentation 121 | /site 122 | 123 | # mypy 124 | .mypy_cache/ 125 | .dmypy.json 126 | dmypy.json 127 | 128 | # Pyre type checker 129 | .pyre/ 130 | -------------------------------------------------------------------------------- /docs/features.md: -------------------------------------------------------------------------------- 1 | # Features 2 | 3 | ## Optical Networking Fields 4 | 5 | ### Cable Fields 6 | 7 | #### Fiber Type 8 | The `fiber_type` custom field with a data type of Selection is added to the `dcim.cable` content type. This field is 9 | used to indicate the specific ITU fiber type (such as G.652D) of the cable using pre-defined choices. 10 | 11 | #### Power Loss 12 | The `power_loss` custom field with a data type of Decimal is added to the `dcim.cable` content type. This field is used 13 | to calculate the optical power loss of the cable using a configurable attenuation coefficient. 14 | 15 | ### Port Fields 16 | 17 | #### Insertion Loss 18 | The `insertion_loss` custom field with a data type of Decimal is added to the `dcim.front_port` and `dcim.rear_port` 19 | content types. This field is used to calculate the optical insertion loss of mating a patch cord to a front or rear port. 20 | 21 | #### Attenuator Loss 22 | The `attenuator_loss` custom field with a data type of Decimal is added to the `dcim.front_port` and `dcim.rear_port` 23 | content types. This field is used to calculate the optical insertion loss of an attenuator placed on a device's front or 24 | rear port. 25 | 26 | #### Return Loss 27 | The `return_loss` custom field with a data type of Decimal is added to the `dcim.front_port` and `dcim.rear_port` 28 | content types. This field is used to calculate the optical return loss of mating a patch cord to a device's front or 29 | rear port. 30 | 31 | ### Interface Fields 32 | 33 | #### Maximum TX Power 34 | The `max_tx_power` custom field with a data type of Decimal is added to the `dcim.interface` content type. This field is 35 | used to calculate the maximum optical power of a device's transceiver. 36 | 37 | #### Minimum TX Power 38 | The `max_tx_power` custom field with a data type of Decimal is added to the `dcim.interface` content type. This field is 39 | used to calculate the minimum optical power of a device's transceiver. 40 | 41 | #### RX Overload Threshold 42 | The `rx_overload` custom field with a data type of Decimal is added to the `dcim.interface` content type. This field 43 | is used to calculate the receiver overload threshold of a device's transceiver. 44 | 45 | #### RX Sensitivity Threshold 46 | The `rx_sensitivity` custom field with a data type of Decimal is added to the `dcim.interface` content type. This field 47 | is used to calculate the receiver sensitivity threshold of a device's transceiver. 48 | 49 | #### TX Wavelength 50 | The `tx_wavelength` custom field with a data type of Decimal is added to the `dcim.interface` content type. This field 51 | is used to calculate the TX wavelength of a device's transceiver. If the transceiver is bi-directional (Bi-Di), simply 52 | set both the TX and RX wavelength fields to the same value. 53 | 54 | #### RX Wavelength 55 | The `rx_wavelength` custom field with a data type of Decimal is added to the `dcim.interface` content type. This field 56 | is used to calculate the RX wavelength of a device's transceiver. If the transceiver is bi-directional (Bi-Di), simply 57 | set both the TX and RX wavelength fields to the same value. 58 | 59 | ## Optical Networking Calculations -------------------------------------------------------------------------------- /docs/index.md: -------------------------------------------------------------------------------- 1 | # Introduction 2 | 3 | In a nutshell, optical networking is focused on the parts of the network where electrical signals are converted to and 4 | transmitted as photonic signals to transport data between devices. This includes whenever data travels through 5 | transceivers connected to fiber optic patch cords between equipment in the same data center, or when that data must 6 | first travel across continents and oceans to reach its destination. 7 | 8 | Maintaining records for optical network elements is just as important as any other aspect of network engineering in a 9 | data center information manager (DCIM). DCIMs help you keep track of sites, racks, equipment, and cabling to exacting 10 | detail, and Netbox remains a leading solution, evolving along with its users' needs year after year. Except for when 11 | it came to certain situations regarding optical networking. 12 | 13 | ## What Made Optical Network Modeling Different? 14 | 15 | Before now, accurately modeling duplex (or higher-count) patch cords and breakout cables (of all media types) in 16 | Netbox wasn’t possible, so documentation beyond the initial equipment cord attached to the transceivers broke down 17 | within patch panels and other optical link components. This also made it difficult to properly model splitters, 18 | mux/demux modules, OADMs, and other passive components that are essential in optical networks. 19 | 20 | Cables couldn’t be edited, either, so any changes to link configurations required deleting and recreating cable 21 | records. This isn’t a blocking issue in and of itself, but because proper selection, installing, and testing of 22 | optical cables is involving, and ideally should include tracking of optical loss and cleaning/inspection data, 23 | having these records destroyed during Move-Add-Change (MAC) activities adds extra time to record keeping and 24 | discourages thorough cable documentation. 25 | 26 | Modeling active optical devices was tricky, too. Historically, devices with modular components such as line cards or 27 | management modules had to be represented as separate, distinct devices in device bays. A GPON optical line terminal 28 | (OLT), for example, often has multiple line cards, which would be represented as separate devices, even though they 29 | weren’t. Also, Netbox lacked some of the interface types unique to optical devices, such as GPON and XGS-PON, so 30 | interface types and their characteristics wouldn’t be correct. 31 | 32 | With the releases of Netbox 3.2 and 3.3, however, all this has been resolved. Thanks to the Netbox development team’s 33 | hard work on [issue #9102, “Extending the cable model to support multiple terminations,”](https://github.com/netbox-community/netbox/issues/9102) 34 | and [issue 7844 “Introduce a model for device modules/line cards”](https://github.com/netbox-community/netbox/issues/7844), 35 | all the above challenges appear to have been addressed, and proper optical modeling should be able to now take place. 36 | 37 | Here are two videos with Netbox’s creator and lead developer, [Jeremy Stretch](https://packetlife.net/), giving a basic 38 | demonstration of these changes: 39 | 40 | [Netbox lead developer Jeremy Stretch presenting the new module functionality of Netbox 3.2.](https://www.youtube.com/watch?v=pIIqc31Mbwc) 41 | 42 | Netbox lead developer Jeremy Stretch presenting the new module functionality of Netbox 3.2. 43 | 44 | [Netbox lead developer Jeremy Stretch presenting the new multi-termination cabling functionality of Netbox 3.3.](https://www.youtube.com/watch?v=5JQlApaS8gM) 45 | 46 | Netbox lead developer Jeremy Stretch presenting the new multi-termination cabling functionality of Netbox 3.3. 47 | 48 | For years we’ve been using some creative workarounds, but I think it’s time to demonstrate the modern way to model 49 | optical networks—in a vendor neural way—that accurately represents the system and can provide better documentation for 50 | ongoing operational support and automation. In this series or articles I will demonstrate those approaches while 51 | highlighting remaining challenges and possible workarounds. -------------------------------------------------------------------------------- /docs/modeling/core_concepts.md: -------------------------------------------------------------------------------- 1 | # Core Optical Modeling Concepts 2 | 3 | ## Common Optical Network Modeling Use Cases 4 | 5 | Optical network modeling can be categorized into **active optical devices** (such as routers, switches, OLTs, 6 | ONUs/ONTs, Mux/Demuxers, ROADMs, amplifiers, etc.) and the **passive optical devices/cable plant** (patch cords, 7 | backbone/distribution cables, adapters, attenuators, filters, splices, etc.) that connect the active devices. 8 | 9 | Using the new Netbox functionality, we’ll model the active optical devices along with the necessary passive optical 10 | cable plant to support that device application, along with the related other models such as sites, locations, racks, 11 | etc. The common use cases for device to cable plant terminations can be categorized into two topologies: 12 | 13 | - **Point-to-point links**, such as simply interconnecting or cross-connecting two switches with simplex or duplex 14 | patch and equipment cords. 15 | - **Point-to-multipoint links**, where a breakout cable, splitter, mux/demux, or OADM would combine fiber strands on 16 | one side, usually to attach to a transceiver, but then create multiple cable paths on the other side to route or 17 | distribute signals in various ways. 18 | 19 | We’ll provide examples of specific configurations for each type of topology in separate pages, but for now let’s 20 | take a closer look at these two topologies before moving on. 21 | 22 | ### Point-to-Point (PTP) Circuit Modeling 23 | 24 | Modeling optical point-to-point (or PTP for short) circuits in Netbox is straightforward. In a simple scenario, you 25 | would define the devices on both sides of a circuit, their interfaces (such as modular SFP+ types), and then model 26 | out the components of the fiber optic link in between. 27 | 28 | In most cases this will start with a simplex or duplex (MMF or SMF) equipment cord, possibly patched into one or more 29 | adapter panels via multiple equivalent patch cords, and then into the equipment cord and terminated at the interface 30 | on the other side of the circuit. A key thing to remember is that there is always a 1:1 ratio of fiber strands across 31 | the link between interfaces. 32 | 33 | For a simplex link, you have one fiber on side A, and one fiber on side B. For a duplex link, you have two fibers on 34 | side A, and two on side B. In both of these cases, the links will be modeled with corresponding simplex or duplex 35 | termination points along the path of the link, such as through adapter panels or splice trays. 36 | 37 | In some cases you’ll be using parallel optics to reach 40Gb/s or higher, via MPO or MPT cable plant. Here you’ll have 38 | 8, 12, 16, or even 24 fibers on side A, but still the same number on side B, keeping the 1:1 ratio between interfaces. 39 | The importance difference here, however, it that if the cables are connectorized, you’ll using single specialized ports 40 | for each termination, versus splicing each fiber if they are not connectorized. 41 | 42 | For all of these cases we’ll still call this a point-to-point link, as there is only one transceiver on each side of 43 | the circuit. 44 | 45 | ### Point to Multi-Point Circuit Modeling 46 | 47 | Modeling optical point-to-multipoint (or PTMP for short) circuits in Netbox is where things get complicated. In these 48 | scenarios, you define one device for the “point” side and multiple devices for the “multi-point” side of the circuit, 49 | and then model out the components of the fiber optic link in between. 50 | 51 | So what makes optical PTMP circuits unique? It’s that the optical transmissions are split up (and possibly 52 | re-combined) within the link. Let’s quickly summarize a few common applications. 53 | 54 | PON 55 | 56 | DWDM Mux/Demux 57 | 58 | ROADM 59 | 60 | 61 | ## Filling in Some Gaps with Custom Fields 62 | 63 | | Field Name | Field Label | Content Types | Data Type | 64 | | -- | --- |------------------|-------| 65 | | `fiber_type` | Fiber Type | `dcim.cable` | Selection | 66 | | `attn_coeff` | Attn Coeff | `dcim.cable` | Decimal | 67 | | `power_loss` | Power Loss | `dcim.cable` | Decimal | 68 | | `attn_loss` | Attn Loss | `dcim.front_port` & `dcim.rear_port` | Decimal | 69 | | `insertion_loss` | Ins Loss | `dcim.front_port` & `dcim.rear_port` | Decimal | 70 | | `return_loss` | Rtn Loss | `dcim.front_port` & `dcim.rear_port` | Decimal | 71 | | `max_tx_power` | Max TX Pwr | `dcim.interface` | Decimal | 72 | | `min_tx_power` | Min TX Pwr | `dcim.interface` | Decimal | 73 | | `rx_overload` | RX Ovld | `dcim.interface` | Decimal | 74 | | `rx_sensitivity` | RX Sen | `dcim.interface` | Decimal | 75 | | `rx_wavelength` | RX Wave | `dcim.interface` | Decimal | 76 | | `tx_wavelength` | TX Wave | `dcim.interface` | Decimal | -------------------------------------------------------------------------------- /netbox_optical_setup.py: -------------------------------------------------------------------------------- 1 | from django.contrib.contenttypes.models import ContentType 2 | 3 | from extras.choices import CustomFieldTypeChoices 4 | from extras.models.customfields import CustomField 5 | from extras.scripts import Script 6 | 7 | 8 | name = 'Netbox Optical Setup (0.8)' 9 | 10 | 11 | # We'll need the IDs of the content types we will attach the custom 12 | # fields to. 13 | cable_id = ContentType.objects.get(model='cable').id 14 | interface_id = ContentType.objects.get(model='interface').id 15 | frontport_id = ContentType.objects.get(model='frontport').id 16 | rearport_id = ContentType.objects.get(model='rearport').id 17 | circuit_id = ContentType.objects.get(model='circuit').id 18 | 19 | # Based on FOA link below and OTT CONA, CONE manuals 20 | # https://www.thefoa.org/tech/smf.htm 21 | 22 | # TODO: Add specialty fibers 23 | FIBER_TYPES = ( 24 | 'G.651.1', 25 | 'G.652', 26 | 'G.652.B', 27 | 'G.652.D', 28 | 'G.653', 29 | 'G.653.A', 30 | 'G.653.B', 31 | 'G.654', 32 | 'G.654.A', 33 | 'G.654.B', 34 | 'G.654.C', 35 | 'G.654.D', 36 | 'G.654.E', 37 | 'G.655', 38 | 'G.655.C', 39 | 'G.655.D', 40 | 'G.655.E', 41 | 'G.656', 42 | 'G.657', 43 | 'G.657.A1', 44 | 'G.657.A2', 45 | 'G.657.B2', 46 | 'G.657.B3' 47 | ) 48 | 49 | 50 | def get_optical_fields(): 51 | fields = CustomField.objects.filter(group_name='Optical Settings') 52 | return fields 53 | 54 | 55 | class CreateCustomFieldsScript(Script): 56 | 57 | class Meta: 58 | name = "Create Optical Networking Custom Fields" 59 | description = "Creates the optical networking custom fields" 60 | commit_default = True 61 | 62 | def run(self, data, commit): 63 | 64 | # TODO: Add exception check to ensure these fields don't already exist 65 | 66 | if CustomField.objects.filter(name='fiber_type').exists(): 67 | self.log_failure('fiber_type custom field already exists') 68 | else: 69 | fiber_type = CustomField.objects.create( 70 | name='fiber_type', 71 | label='Fiber Type', 72 | group_name='Optical Settings', 73 | type=CustomFieldTypeChoices.TYPE_SELECT, 74 | # TODO: Add choices, defaults 75 | description="The ITU fiber type of the cable.", 76 | choices=FIBER_TYPES, 77 | # TODO: Is there a better way to reference this? 78 | # TODO: Any other MM? 79 | default="G.652" 80 | ) 81 | fiber_type.content_types.set([cable_id]) 82 | fiber_type.save() 83 | self.log_info("fiber_type custom field created") 84 | 85 | if CustomField.objects.filter(name='attenuation_coeff').exists(): 86 | self.log_failure('attenuation_coeff custom field already exists') 87 | else: 88 | attenuation_coeff = CustomField.objects.create( 89 | name='attenuation_coeff', 90 | label='Attn Coeff', 91 | group_name='Optical Settings', 92 | type=CustomFieldTypeChoices.TYPE_TEXT, 93 | description="The attenuation coefficient of the cable per km", 94 | choices=FIBER_TYPES, 95 | # TODO: Convert unit as needed, but always based on km 96 | default="0.4", # TODO: Make configurable in config 97 | ) 98 | attenuation_coeff.content_types.set([cable_id]) 99 | attenuation_coeff.save() 100 | self.log_info("attenuation_coeff custom field created") 101 | 102 | if CustomField.objects.filter(name='power_loss').exists(): 103 | self.log_failure('power_loss custom field already exists') 104 | else: 105 | power_loss = CustomField.objects.create( 106 | name='power_loss', 107 | label='Pwr Loss', 108 | group_name='Optical Settings', 109 | # FIXME: Update to Decimal for Netbox 3.4 110 | type=CustomFieldTypeChoices.TYPE_TEXT, 111 | description="The overall power loss on the fiber across the cable's length.", 112 | validation_minimum=-60, # Loss stops at -60 dB (0.000001) 113 | validation_maximum=0 # Loss starts at 0 dB (anything higher 114 | # isn't loss! 115 | ) 116 | power_loss.content_types.set([cable_id]) 117 | power_loss.save() 118 | self.log_info("power_loss custom field created") 119 | 120 | if CustomField.objects.filter(name='attenuator_loss').exists(): 121 | self.log_failure('attenuator_loss custom field already exists') 122 | else: 123 | attenuator_loss = CustomField.objects.create( 124 | name='attenuator_loss', 125 | label='Attn Loss', 126 | group_name='Optical Settings', 127 | # FIXME: Update to Decimal for Netbox 3.4 128 | type=CustomFieldTypeChoices.TYPE_INTEGER, 129 | description="The intentionally-added optical loss on this port from a fixed or variable attenuator.", 130 | validation_minimum=-60, # Loss stops at -60 dB (0.000001) 131 | validation_maximum=0 # Loss starts at 0 dB (anything higher 132 | # isn't loss! 133 | ) 134 | attenuator_loss.content_types.set([frontport_id, rearport_id]) 135 | attenuator_loss.save() 136 | self.log_info("attenuator_loss custom field created") 137 | 138 | if CustomField.objects.filter(name='insertion_loss').exists(): 139 | self.log_failure('insertion_loss custom field already exists') 140 | else: 141 | insertion_loss = CustomField.objects.create( 142 | name='insertion_loss', 143 | label='Ins Loss', 144 | group_name='Optical Settings', 145 | # FIXME: Update to Decimal for Netbox 3.4 146 | type=CustomFieldTypeChoices.TYPE_TEXT, 147 | description="The optical loss caused by passing through the port", 148 | validation_minimum=-60, # Loss stops at -60 dB (0.000001) 149 | validation_maximum=0 # Loss starts at 0 dB (anything higher 150 | # isn't loss! 151 | ) 152 | insertion_loss.content_types.set([frontport_id, rearport_id]) 153 | insertion_loss.save() 154 | self.log_info("insertion_loss custom field created") 155 | 156 | if CustomField.objects.filter(name='return_loss').exists(): 157 | self.log_failure('return_loss custom field already exists') 158 | else: 159 | return_loss = CustomField.objects.create( 160 | name='return_loss', 161 | label='Rtn Loss', 162 | group_name='Optical Settings', 163 | # FIXME: Update to Decimal for Netbox 3.4 164 | type=CustomFieldTypeChoices.TYPE_TEXT, 165 | description="The optical loss from reflection at the port", 166 | validation_minimum=-60, # Loss stops at -60 dB (0.000001) 167 | validation_maximum=0 # Loss starts at 0 dB (anything higher 168 | # isn't loss! 169 | ) 170 | return_loss.content_types.set([frontport_id, rearport_id]) 171 | return_loss.save() 172 | self.log_info("return_loss custom field created") 173 | 174 | if CustomField.objects.filter(name='max_tx_power').exists(): 175 | self.log_failure('max_tx_power custom field already exists') 176 | else: 177 | max_tx_power = CustomField.objects.create( 178 | name='max_tx_power', 179 | label='Max TX Pwr', 180 | group_name='Optical Settings', 181 | # FIXME: Update to Decimal for Netbox 3.4 182 | type=CustomFieldTypeChoices.TYPE_TEXT, 183 | description="The maximum transmission power of the transceiver" 184 | # TODO: Add validation 185 | ) 186 | max_tx_power.content_types.set([interface_id]) 187 | max_tx_power.save() 188 | self.log_info("max_tx_power custom field created") 189 | 190 | if CustomField.objects.filter(name='min_tx_power').exists(): 191 | self.log_failure('min_tx_power custom field already exists') 192 | else: 193 | min_tx_power = CustomField.objects.create( 194 | name='min_tx_power', 195 | label='Min TX Pwr', 196 | group_name='Optical Settings', 197 | # FIXME: Update to Decimal for Netbox 3.4 198 | type=CustomFieldTypeChoices.TYPE_TEXT, 199 | description="The minimum transmission power of the transceiver" 200 | # TODO: Add validation 201 | ) 202 | min_tx_power.content_types.set([interface_id]) 203 | min_tx_power.save() 204 | self.log_info("min_tx_power custom field created") 205 | 206 | if CustomField.objects.filter(name='rx_overload').exists(): 207 | self.log_failure('rx_overload custom field already exists') 208 | else: 209 | rx_overload = CustomField.objects.create( 210 | name='rx_overload', 211 | label='RX Ovld', 212 | group_name='Optical Settings', 213 | # FIXME: Update to Decimal for Netbox 3.4 214 | type=CustomFieldTypeChoices.TYPE_TEXT, 215 | description="The overload power threshold of the transceiver" 216 | # TODO: Add validation 217 | ) 218 | rx_overload.content_types.set([interface_id]) 219 | rx_overload.save() 220 | self.log_info("rx_overload custom field created") 221 | 222 | if CustomField.objects.filter(name='rx_sensitivity').exists(): 223 | self.log_failure('rx_sensitivity custom field already exists') 224 | else: 225 | rx_sensitivity = CustomField.objects.create( 226 | name='rx_sensitivity', 227 | label='RX Sen', 228 | group_name='Optical Settings', 229 | # FIXME: Update to Decimal for Netbox 3.4 230 | type=CustomFieldTypeChoices.TYPE_TEXT, 231 | description="The sensitivity power threshold of the transceiver" 232 | # TODO: Add validation 233 | ) 234 | rx_sensitivity.content_types.set([interface_id]) 235 | rx_sensitivity.save() 236 | self.log_info("rx_sensitivity custom field created") 237 | 238 | if CustomField.objects.filter(name='tx_wavelength').exists(): 239 | self.log_failure('tx_wavelength custom field already exists') 240 | else: 241 | tx_wavelength = CustomField.objects.create( 242 | name='tx_wavelength', 243 | label='TX Wave', 244 | group_name='Optical Settings', 245 | # FIXME: Update to Decimal for Netbox 3.4 246 | type=CustomFieldTypeChoices.TYPE_TEXT, 247 | description="The specific TX wavelength of the transceiver", 248 | # FIXME: Integer fields are a limitation here; need <= option 249 | # and/or Decimal support 250 | validation_minimum=1260, # Use start of the O-band 251 | # End right after the U-band (maybe we can prevent 1676 somehow?) 252 | validation_maximum=1676 253 | ) 254 | tx_wavelength.content_types.set([interface_id]) 255 | tx_wavelength.save() 256 | self.log_info("tx_wavelength custom field created") 257 | 258 | if CustomField.objects.filter(name='rx_wavelength').exists(): 259 | self.log_failure('rx_wavelength custom field already exists') 260 | else: 261 | rx_wavelength = CustomField.objects.create( 262 | name='rx_wavelength', 263 | label='RX Wave', 264 | group_name='Optical Settings', 265 | # FIXME: Update to Decimal for Netbox 3.4 266 | type=CustomFieldTypeChoices.TYPE_TEXT, 267 | description="The specific RX wavelength of the transceiver", 268 | # FIXME: Integer fields are a limitation here; need <= option 269 | # and/or Decimal support 270 | # TODO: Add MM (850) 271 | validation_minimum=1260, # Use start of the O-band 272 | # End right after the U-band (maybe we can prevent 1676 somehow?) 273 | validation_maximum=1676 274 | ) 275 | rx_wavelength.content_types.set([interface_id]) 276 | rx_wavelength.save() 277 | self.log_info("rx_wavelength custom field created") 278 | 279 | # Return the output to the script page 280 | self.log_success('Generation of custom fields complete') 281 | 282 | 283 | class UpdateCustomFieldsScript(Script): 284 | 285 | class Meta: 286 | name = "Update Optical Networking Custom Fields" 287 | description = "Updates the optical networking custom fields" 288 | commit_default = False 289 | 290 | def run(self, data, commit): 291 | 292 | fiber_type = CustomField.objects.get(name='fiber_type') 293 | fiber_type.label = 'Fiber Type' 294 | fiber_type.group_name = 'Optical Settings' 295 | fiber_type.type = CustomFieldTypeChoices.TYPE_SELECT 296 | fiber_type.description = "The ITU fiber type of the cable." 297 | fiber_type.choices = FIBER_TYPES 298 | fiber_type.default = "G.652" 299 | fiber_type.content_types.set([cable_id]) 300 | fiber_type.save() 301 | self.log_info("fiber_type custom field updated") 302 | 303 | attenuation_coeff = CustomField.objects.get(name='attenuation_coeff') 304 | attenuation_coeff.label = 'Attn Coeff' 305 | attenuation_coeff.group_name = 'Optical Settings' 306 | attenuation_coeff.type = CustomFieldTypeChoices.TYPE_TEXT 307 | attenuation_coeff.description = "The attenuation coefficient of the cable per km" 308 | attenuation_coeff.choices = FIBER_TYPES 309 | attenuation_coeff.default = "0.4" 310 | attenuation_coeff.content_types.set([cable_id]) 311 | attenuation_coeff.save() 312 | self.log_info("attenuation_coeff custom field updated") 313 | 314 | power_loss = CustomField.objects.get(name='power_loss') 315 | power_loss.label = 'Pwr Loss' 316 | power_loss.group_name = 'Optical Settings' 317 | power_loss.type = CustomFieldTypeChoices.TYPE_TEXT 318 | power_loss.description = "The overall power loss on the fiber across the cable's length." 319 | power_loss.validation_minimum = -60 320 | power_loss.validation_maximum = 0 321 | power_loss.content_types.set([cable_id]) 322 | power_loss.save() 323 | self.log_info("power_loss custom field updated") 324 | 325 | attenuator_loss = CustomField.objects.get(name='attenuator_loss') 326 | attenuator_loss.label = 'Attn Loss' 327 | attenuator_loss.group_name = 'Optical Settings' 328 | attenuator_loss.type = CustomFieldTypeChoices.TYPE_INTEGER 329 | attenuator_loss.description = "The intentionally-added optical loss on this port from a fixed or variable attenuator." 330 | attenuator_loss.validation_minimum = -60 331 | attenuator_loss.validation_maximum = 0 332 | attenuator_loss.content_types.set([frontport_id, rearport_id]) 333 | attenuator_loss.save() 334 | self.log_info("attenuator_loss custom field updated") 335 | 336 | insertion_loss = CustomField.objects.get(name='insertion_loss') 337 | insertion_loss.label = 'Ins Loss' 338 | insertion_loss.group_name = 'Optical Settings' 339 | insertion_loss.type = CustomFieldTypeChoices.TYPE_TEXT 340 | insertion_loss.description = "The optical loss caused by passing through the port" 341 | insertion_loss.validation_minimum = -60 342 | insertion_loss.validation_maximum = 0 343 | insertion_loss.content_types.set([frontport_id, rearport_id]) 344 | insertion_loss.save() 345 | self.log_info("insertion_loss custom field updated") 346 | 347 | return_loss = CustomField.objects.get(name='return_loss') 348 | return_loss.label = 'Rtn Loss' 349 | return_loss.group_name = 'Optical Settings' 350 | return_loss.type = CustomFieldTypeChoices.TYPE_TEXT 351 | return_loss.description = "The optical loss from reflection at the port" 352 | return_loss.validation_minimum = -60 353 | return_loss.validation_maximum = 0 354 | return_loss.content_types.set([frontport_id, rearport_id]) 355 | return_loss.save() 356 | self.log_info("return_loss custom field updated") 357 | 358 | max_tx_power = CustomField.objects.get(name='max_tx_power') 359 | max_tx_power.label = 'Max TX Pwr' 360 | max_tx_power.group_name = 'Optical Settings' 361 | max_tx_power.type = CustomFieldTypeChoices.TYPE_TEXT 362 | max_tx_power.description = "The maximum transmission power of the transceiver" 363 | max_tx_power.content_types.set([interface_id]) 364 | max_tx_power.save() 365 | self.log_info("max_tx_power custom field updated") 366 | 367 | min_tx_power = CustomField.objects.get(name='min_tx_power') 368 | min_tx_power.label = 'Min TX Pwr' 369 | min_tx_power.group_name = 'Optical Settings' 370 | min_tx_power.type = CustomFieldTypeChoices.TYPE_TEXT 371 | min_tx_power.description = "The minimum transmission power of the transceiver" 372 | min_tx_power.content_types.set([interface_id]) 373 | min_tx_power.save() 374 | self.log_info("min_tx_power custom field updated") 375 | 376 | rx_overload = CustomField.objects.get(name='rx_overload') 377 | rx_overload.label = 'RX Ovld' 378 | rx_overload.group_name = 'Optical Settings' 379 | rx_overload.type = CustomFieldTypeChoices.TYPE_TEXT 380 | rx_overload.description = "The overload power threshold of the transceiver" 381 | rx_overload.content_types.set([interface_id]) 382 | rx_overload.save() 383 | self.log_info("rx_overload custom field updated") 384 | 385 | rx_sensitivity = CustomField.objects.get(name='rx_sensitivity') 386 | rx_sensitivity.label = 'RX Sen' 387 | rx_sensitivity.group_name = 'Optical Settings' 388 | rx_sensitivity.type = CustomFieldTypeChoices.TYPE_TEXT 389 | rx_sensitivity.description = "The sensitivity power threshold of the transceiver" 390 | rx_sensitivity.content_types.set([interface_id]) 391 | rx_sensitivity.save() 392 | self.log_info("rx_sensitivity custom field updated") 393 | 394 | tx_wavelength = CustomField.objects.get(name='tx_wavelength') 395 | tx_wavelength.label = 'TX Wave' 396 | tx_wavelength.group_name = 'Optical Settings' 397 | tx_wavelength.type = CustomFieldTypeChoices.TYPE_TEXT 398 | tx_wavelength.description = "The specific TX wavelength of the transceiver" 399 | tx_wavelength.validation_minimum = 850 400 | tx_wavelength.validation_maximum = 1676 401 | tx_wavelength.content_types.set([interface_id]) 402 | tx_wavelength.save() 403 | self.log_info("tx_wavelength custom field updated") 404 | 405 | rx_wavelength = CustomField.objects.get(name='rx_wavelength') 406 | rx_wavelength.label = 'RX Wave' 407 | rx_wavelength.group_name = 'Optical Settings' 408 | rx_wavelength.type = CustomFieldTypeChoices.TYPE_TEXT 409 | rx_wavelength.description = "The specific RX wavelength of the transceiver" 410 | rx_wavelength.validation_minimum = 850 411 | rx_wavelength.validation_maximum = 1676 412 | rx_wavelength.content_types.set([interface_id]) 413 | rx_wavelength.save() 414 | self.log_info("rx_wavelength custom field updated") 415 | 416 | self.log_success('All optical fields updated') 417 | 418 | 419 | class RemoveCustomFieldsScript(Script): 420 | 421 | class Meta: 422 | name = "Remove Optical Networking Custom Fields" 423 | description = "Removes the optical networking custom fields" 424 | commit_default = False 425 | 426 | def run(self, data, commit): 427 | fields = get_optical_fields() 428 | 429 | for field in fields: 430 | CustomField.objects.filter(id=field.id).delete() 431 | self.log_info(f"{field.name} removed") 432 | 433 | self.log_success('All optical fields removed') 434 | 435 | 436 | script_order = ( 437 | CreateCustomFieldsScript, 438 | UpdateCustomFieldsScript, 439 | RemoveCustomFieldsScript 440 | ) 441 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU AFFERO GENERAL PUBLIC LICENSE 2 | Version 3, 19 November 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU Affero General Public License is a free, copyleft license for 11 | software and other kinds of works, specifically designed to ensure 12 | cooperation with the community in the case of network server software. 13 | 14 | The licenses for most software and other practical works are designed 15 | to take away your freedom to share and change the works. By contrast, 16 | our General Public Licenses are intended to guarantee your freedom to 17 | share and change all versions of a program--to make sure it remains free 18 | software for all its users. 19 | 20 | When we speak of free software, we are referring to freedom, not 21 | price. Our General Public Licenses are designed to make sure that you 22 | have the freedom to distribute copies of free software (and charge for 23 | them if you wish), that you receive source code or can get it if you 24 | want it, that you can change the software or use pieces of it in new 25 | free programs, and that you know you can do these things. 26 | 27 | Developers that use our General Public Licenses protect your rights 28 | with two steps: (1) assert copyright on the software, and (2) offer 29 | you this License which gives you legal permission to copy, distribute 30 | and/or modify the software. 31 | 32 | A secondary benefit of defending all users' freedom is that 33 | improvements made in alternate versions of the program, if they 34 | receive widespread use, become available for other developers to 35 | incorporate. Many developers of free software are heartened and 36 | encouraged by the resulting cooperation. However, in the case of 37 | software used on network servers, this result may fail to come about. 38 | The GNU General Public License permits making a modified version and 39 | letting the public access it on a server without ever releasing its 40 | source code to the public. 41 | 42 | The GNU Affero General Public License is designed specifically to 43 | ensure that, in such cases, the modified source code becomes available 44 | to the community. It requires the operator of a network server to 45 | provide the source code of the modified version running there to the 46 | users of that server. Therefore, public use of a modified version, on 47 | a publicly accessible server, gives the public access to the source 48 | code of the modified version. 49 | 50 | An older license, called the Affero General Public License and 51 | published by Affero, was designed to accomplish similar goals. This is 52 | a different license, not a version of the Affero GPL, but Affero has 53 | released a new version of the Affero GPL which permits relicensing under 54 | this license. 55 | 56 | The precise terms and conditions for copying, distribution and 57 | modification follow. 58 | 59 | TERMS AND CONDITIONS 60 | 61 | 0. Definitions. 62 | 63 | "This License" refers to version 3 of the GNU Affero General Public License. 64 | 65 | "Copyright" also means copyright-like laws that apply to other kinds of 66 | works, such as semiconductor masks. 67 | 68 | "The Program" refers to any copyrightable work licensed under this 69 | License. Each licensee is addressed as "you". "Licensees" and 70 | "recipients" may be individuals or organizations. 71 | 72 | To "modify" a work means to copy from or adapt all or part of the work 73 | in a fashion requiring copyright permission, other than the making of an 74 | exact copy. The resulting work is called a "modified version" of the 75 | earlier work or a work "based on" the earlier work. 76 | 77 | A "covered work" means either the unmodified Program or a work based 78 | on the Program. 79 | 80 | To "propagate" a work means to do anything with it that, without 81 | permission, would make you directly or secondarily liable for 82 | infringement under applicable copyright law, except executing it on a 83 | computer or modifying a private copy. Propagation includes copying, 84 | distribution (with or without modification), making available to the 85 | public, and in some countries other activities as well. 86 | 87 | To "convey" a work means any kind of propagation that enables other 88 | parties to make or receive copies. Mere interaction with a user through 89 | a computer network, with no transfer of a copy, is not conveying. 90 | 91 | An interactive user interface displays "Appropriate Legal Notices" 92 | to the extent that it includes a convenient and prominently visible 93 | feature that (1) displays an appropriate copyright notice, and (2) 94 | tells the user that there is no warranty for the work (except to the 95 | extent that warranties are provided), that licensees may convey the 96 | work under this License, and how to view a copy of this License. If 97 | the interface presents a list of user commands or options, such as a 98 | menu, a prominent item in the list meets this criterion. 99 | 100 | 1. Source Code. 101 | 102 | The "source code" for a work means the preferred form of the work 103 | for making modifications to it. "Object code" means any non-source 104 | form of a work. 105 | 106 | A "Standard Interface" means an interface that either is an official 107 | standard defined by a recognized standards body, or, in the case of 108 | interfaces specified for a particular programming language, one that 109 | is widely used among developers working in that language. 110 | 111 | The "System Libraries" of an executable work include anything, other 112 | than the work as a whole, that (a) is included in the normal form of 113 | packaging a Major Component, but which is not part of that Major 114 | Component, and (b) serves only to enable use of the work with that 115 | Major Component, or to implement a Standard Interface for which an 116 | implementation is available to the public in source code form. A 117 | "Major Component", in this context, means a major essential component 118 | (kernel, window system, and so on) of the specific operating system 119 | (if any) on which the executable work runs, or a compiler used to 120 | produce the work, or an object code interpreter used to run it. 121 | 122 | The "Corresponding Source" for a work in object code form means all 123 | the source code needed to generate, install, and (for an executable 124 | work) run the object code and to modify the work, including scripts to 125 | control those activities. However, it does not include the work's 126 | System Libraries, or general-purpose tools or generally available free 127 | programs which are used unmodified in performing those activities but 128 | which are not part of the work. For example, Corresponding Source 129 | includes interface definition files associated with source files for 130 | the work, and the source code for shared libraries and dynamically 131 | linked subprograms that the work is specifically designed to require, 132 | such as by intimate data communication or control flow between those 133 | subprograms and other parts of the work. 134 | 135 | The Corresponding Source need not include anything that users 136 | can regenerate automatically from other parts of the Corresponding 137 | Source. 138 | 139 | The Corresponding Source for a work in source code form is that 140 | same work. 141 | 142 | 2. Basic Permissions. 143 | 144 | All rights granted under this License are granted for the term of 145 | copyright on the Program, and are irrevocable provided the stated 146 | conditions are met. This License explicitly affirms your unlimited 147 | permission to run the unmodified Program. The output from running a 148 | covered work is covered by this License only if the output, given its 149 | content, constitutes a covered work. This License acknowledges your 150 | rights of fair use or other equivalent, as provided by copyright law. 151 | 152 | You may make, run and propagate covered works that you do not 153 | convey, without conditions so long as your license otherwise remains 154 | in force. You may convey covered works to others for the sole purpose 155 | of having them make modifications exclusively for you, or provide you 156 | with facilities for running those works, provided that you comply with 157 | the terms of this License in conveying all material for which you do 158 | not control copyright. Those thus making or running the covered works 159 | for you must do so exclusively on your behalf, under your direction 160 | and control, on terms that prohibit them from making any copies of 161 | your copyrighted material outside their relationship with you. 162 | 163 | Conveying under any other circumstances is permitted solely under 164 | the conditions stated below. Sublicensing is not allowed; section 10 165 | makes it unnecessary. 166 | 167 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 168 | 169 | No covered work shall be deemed part of an effective technological 170 | measure under any applicable law fulfilling obligations under article 171 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 172 | similar laws prohibiting or restricting circumvention of such 173 | measures. 174 | 175 | When you convey a covered work, you waive any legal power to forbid 176 | circumvention of technological measures to the extent such circumvention 177 | is effected by exercising rights under this License with respect to 178 | the covered work, and you disclaim any intention to limit operation or 179 | modification of the work as a means of enforcing, against the work's 180 | users, your or third parties' legal rights to forbid circumvention of 181 | technological measures. 182 | 183 | 4. Conveying Verbatim Copies. 184 | 185 | You may convey verbatim copies of the Program's source code as you 186 | receive it, in any medium, provided that you conspicuously and 187 | appropriately publish on each copy an appropriate copyright notice; 188 | keep intact all notices stating that this License and any 189 | non-permissive terms added in accord with section 7 apply to the code; 190 | keep intact all notices of the absence of any warranty; and give all 191 | recipients a copy of this License along with the Program. 192 | 193 | You may charge any price or no price for each copy that you convey, 194 | and you may offer support or warranty protection for a fee. 195 | 196 | 5. Conveying Modified Source Versions. 197 | 198 | You may convey a work based on the Program, or the modifications to 199 | produce it from the Program, in the form of source code under the 200 | terms of section 4, provided that you also meet all of these conditions: 201 | 202 | a) The work must carry prominent notices stating that you modified 203 | it, and giving a relevant date. 204 | 205 | b) The work must carry prominent notices stating that it is 206 | released under this License and any conditions added under section 207 | 7. This requirement modifies the requirement in section 4 to 208 | "keep intact all notices". 209 | 210 | c) You must license the entire work, as a whole, under this 211 | License to anyone who comes into possession of a copy. This 212 | License will therefore apply, along with any applicable section 7 213 | additional terms, to the whole of the work, and all its parts, 214 | regardless of how they are packaged. This License gives no 215 | permission to license the work in any other way, but it does not 216 | invalidate such permission if you have separately received it. 217 | 218 | d) If the work has interactive user interfaces, each must display 219 | Appropriate Legal Notices; however, if the Program has interactive 220 | interfaces that do not display Appropriate Legal Notices, your 221 | work need not make them do so. 222 | 223 | A compilation of a covered work with other separate and independent 224 | works, which are not by their nature extensions of the covered work, 225 | and which are not combined with it such as to form a larger program, 226 | in or on a volume of a storage or distribution medium, is called an 227 | "aggregate" if the compilation and its resulting copyright are not 228 | used to limit the access or legal rights of the compilation's users 229 | beyond what the individual works permit. Inclusion of a covered work 230 | in an aggregate does not cause this License to apply to the other 231 | parts of the aggregate. 232 | 233 | 6. Conveying Non-Source Forms. 234 | 235 | You may convey a covered work in object code form under the terms 236 | of sections 4 and 5, provided that you also convey the 237 | machine-readable Corresponding Source under the terms of this License, 238 | in one of these ways: 239 | 240 | a) Convey the object code in, or embodied in, a physical product 241 | (including a physical distribution medium), accompanied by the 242 | Corresponding Source fixed on a durable physical medium 243 | customarily used for software interchange. 244 | 245 | b) Convey the object code in, or embodied in, a physical product 246 | (including a physical distribution medium), accompanied by a 247 | written offer, valid for at least three years and valid for as 248 | long as you offer spare parts or customer support for that product 249 | model, to give anyone who possesses the object code either (1) a 250 | copy of the Corresponding Source for all the software in the 251 | product that is covered by this License, on a durable physical 252 | medium customarily used for software interchange, for a price no 253 | more than your reasonable cost of physically performing this 254 | conveying of source, or (2) access to copy the 255 | Corresponding Source from a network server at no charge. 256 | 257 | c) Convey individual copies of the object code with a copy of the 258 | written offer to provide the Corresponding Source. This 259 | alternative is allowed only occasionally and noncommercially, and 260 | only if you received the object code with such an offer, in accord 261 | with subsection 6b. 262 | 263 | d) Convey the object code by offering access from a designated 264 | place (gratis or for a charge), and offer equivalent access to the 265 | Corresponding Source in the same way through the same place at no 266 | further charge. You need not require recipients to copy the 267 | Corresponding Source along with the object code. If the place to 268 | copy the object code is a network server, the Corresponding Source 269 | may be on a different server (operated by you or a third party) 270 | that supports equivalent copying facilities, provided you maintain 271 | clear directions next to the object code saying where to find the 272 | Corresponding Source. Regardless of what server hosts the 273 | Corresponding Source, you remain obligated to ensure that it is 274 | available for as long as needed to satisfy these requirements. 275 | 276 | e) Convey the object code using peer-to-peer transmission, provided 277 | you inform other peers where the object code and Corresponding 278 | Source of the work are being offered to the general public at no 279 | charge under subsection 6d. 280 | 281 | A separable portion of the object code, whose source code is excluded 282 | from the Corresponding Source as a System Library, need not be 283 | included in conveying the object code work. 284 | 285 | A "User Product" is either (1) a "consumer product", which means any 286 | tangible personal property which is normally used for personal, family, 287 | or household purposes, or (2) anything designed or sold for incorporation 288 | into a dwelling. In determining whether a product is a consumer product, 289 | doubtful cases shall be resolved in favor of coverage. For a particular 290 | product received by a particular user, "normally used" refers to a 291 | typical or common use of that class of product, regardless of the status 292 | of the particular user or of the way in which the particular user 293 | actually uses, or expects or is expected to use, the product. A product 294 | is a consumer product regardless of whether the product has substantial 295 | commercial, industrial or non-consumer uses, unless such uses represent 296 | the only significant mode of use of the product. 297 | 298 | "Installation Information" for a User Product means any methods, 299 | procedures, authorization keys, or other information required to install 300 | and execute modified versions of a covered work in that User Product from 301 | a modified version of its Corresponding Source. The information must 302 | suffice to ensure that the continued functioning of the modified object 303 | code is in no case prevented or interfered with solely because 304 | modification has been made. 305 | 306 | If you convey an object code work under this section in, or with, or 307 | specifically for use in, a User Product, and the conveying occurs as 308 | part of a transaction in which the right of possession and use of the 309 | User Product is transferred to the recipient in perpetuity or for a 310 | fixed term (regardless of how the transaction is characterized), the 311 | Corresponding Source conveyed under this section must be accompanied 312 | by the Installation Information. But this requirement does not apply 313 | if neither you nor any third party retains the ability to install 314 | modified object code on the User Product (for example, the work has 315 | been installed in ROM). 316 | 317 | The requirement to provide Installation Information does not include a 318 | requirement to continue to provide support service, warranty, or updates 319 | for a work that has been modified or installed by the recipient, or for 320 | the User Product in which it has been modified or installed. Access to a 321 | network may be denied when the modification itself materially and 322 | adversely affects the operation of the network or violates the rules and 323 | protocols for communication across the network. 324 | 325 | Corresponding Source conveyed, and Installation Information provided, 326 | in accord with this section must be in a format that is publicly 327 | documented (and with an implementation available to the public in 328 | source code form), and must require no special password or key for 329 | unpacking, reading or copying. 330 | 331 | 7. Additional Terms. 332 | 333 | "Additional permissions" are terms that supplement the terms of this 334 | License by making exceptions from one or more of its conditions. 335 | Additional permissions that are applicable to the entire Program shall 336 | be treated as though they were included in this License, to the extent 337 | that they are valid under applicable law. If additional permissions 338 | apply only to part of the Program, that part may be used separately 339 | under those permissions, but the entire Program remains governed by 340 | this License without regard to the additional permissions. 341 | 342 | When you convey a copy of a covered work, you may at your option 343 | remove any additional permissions from that copy, or from any part of 344 | it. (Additional permissions may be written to require their own 345 | removal in certain cases when you modify the work.) You may place 346 | additional permissions on material, added by you to a covered work, 347 | for which you have or can give appropriate copyright permission. 348 | 349 | Notwithstanding any other provision of this License, for material you 350 | add to a covered work, you may (if authorized by the copyright holders of 351 | that material) supplement the terms of this License with terms: 352 | 353 | a) Disclaiming warranty or limiting liability differently from the 354 | terms of sections 15 and 16 of this License; or 355 | 356 | b) Requiring preservation of specified reasonable legal notices or 357 | author attributions in that material or in the Appropriate Legal 358 | Notices displayed by works containing it; or 359 | 360 | c) Prohibiting misrepresentation of the origin of that material, or 361 | requiring that modified versions of such material be marked in 362 | reasonable ways as different from the original version; or 363 | 364 | d) Limiting the use for publicity purposes of names of licensors or 365 | authors of the material; or 366 | 367 | e) Declining to grant rights under trademark law for use of some 368 | trade names, trademarks, or service marks; or 369 | 370 | f) Requiring indemnification of licensors and authors of that 371 | material by anyone who conveys the material (or modified versions of 372 | it) with contractual assumptions of liability to the recipient, for 373 | any liability that these contractual assumptions directly impose on 374 | those licensors and authors. 375 | 376 | All other non-permissive additional terms are considered "further 377 | restrictions" within the meaning of section 10. If the Program as you 378 | received it, or any part of it, contains a notice stating that it is 379 | governed by this License along with a term that is a further 380 | restriction, you may remove that term. If a license document contains 381 | a further restriction but permits relicensing or conveying under this 382 | License, you may add to a covered work material governed by the terms 383 | of that license document, provided that the further restriction does 384 | not survive such relicensing or conveying. 385 | 386 | If you add terms to a covered work in accord with this section, you 387 | must place, in the relevant source files, a statement of the 388 | additional terms that apply to those files, or a notice indicating 389 | where to find the applicable terms. 390 | 391 | Additional terms, permissive or non-permissive, may be stated in the 392 | form of a separately written license, or stated as exceptions; 393 | the above requirements apply either way. 394 | 395 | 8. Termination. 396 | 397 | You may not propagate or modify a covered work except as expressly 398 | provided under this License. Any attempt otherwise to propagate or 399 | modify it is void, and will automatically terminate your rights under 400 | this License (including any patent licenses granted under the third 401 | paragraph of section 11). 402 | 403 | However, if you cease all violation of this License, then your 404 | license from a particular copyright holder is reinstated (a) 405 | provisionally, unless and until the copyright holder explicitly and 406 | finally terminates your license, and (b) permanently, if the copyright 407 | holder fails to notify you of the violation by some reasonable means 408 | prior to 60 days after the cessation. 409 | 410 | Moreover, your license from a particular copyright holder is 411 | reinstated permanently if the copyright holder notifies you of the 412 | violation by some reasonable means, this is the first time you have 413 | received notice of violation of this License (for any work) from that 414 | copyright holder, and you cure the violation prior to 30 days after 415 | your receipt of the notice. 416 | 417 | Termination of your rights under this section does not terminate the 418 | licenses of parties who have received copies or rights from you under 419 | this License. If your rights have been terminated and not permanently 420 | reinstated, you do not qualify to receive new licenses for the same 421 | material under section 10. 422 | 423 | 9. Acceptance Not Required for Having Copies. 424 | 425 | You are not required to accept this License in order to receive or 426 | run a copy of the Program. Ancillary propagation of a covered work 427 | occurring solely as a consequence of using peer-to-peer transmission 428 | to receive a copy likewise does not require acceptance. However, 429 | nothing other than this License grants you permission to propagate or 430 | modify any covered work. These actions infringe copyright if you do 431 | not accept this License. Therefore, by modifying or propagating a 432 | covered work, you indicate your acceptance of this License to do so. 433 | 434 | 10. Automatic Licensing of Downstream Recipients. 435 | 436 | Each time you convey a covered work, the recipient automatically 437 | receives a license from the original licensors, to run, modify and 438 | propagate that work, subject to this License. You are not responsible 439 | for enforcing compliance by third parties with this License. 440 | 441 | An "entity transaction" is a transaction transferring control of an 442 | organization, or substantially all assets of one, or subdividing an 443 | organization, or merging organizations. If propagation of a covered 444 | work results from an entity transaction, each party to that 445 | transaction who receives a copy of the work also receives whatever 446 | licenses to the work the party's predecessor in interest had or could 447 | give under the previous paragraph, plus a right to possession of the 448 | Corresponding Source of the work from the predecessor in interest, if 449 | the predecessor has it or can get it with reasonable efforts. 450 | 451 | You may not impose any further restrictions on the exercise of the 452 | rights granted or affirmed under this License. For example, you may 453 | not impose a license fee, royalty, or other charge for exercise of 454 | rights granted under this License, and you may not initiate litigation 455 | (including a cross-claim or counterclaim in a lawsuit) alleging that 456 | any patent claim is infringed by making, using, selling, offering for 457 | sale, or importing the Program or any portion of it. 458 | 459 | 11. Patents. 460 | 461 | A "contributor" is a copyright holder who authorizes use under this 462 | License of the Program or a work on which the Program is based. The 463 | work thus licensed is called the contributor's "contributor version". 464 | 465 | A contributor's "essential patent claims" are all patent claims 466 | owned or controlled by the contributor, whether already acquired or 467 | hereafter acquired, that would be infringed by some manner, permitted 468 | by this License, of making, using, or selling its contributor version, 469 | but do not include claims that would be infringed only as a 470 | consequence of further modification of the contributor version. For 471 | purposes of this definition, "control" includes the right to grant 472 | patent sublicenses in a manner consistent with the requirements of 473 | this License. 474 | 475 | Each contributor grants you a non-exclusive, worldwide, royalty-free 476 | patent license under the contributor's essential patent claims, to 477 | make, use, sell, offer for sale, import and otherwise run, modify and 478 | propagate the contents of its contributor version. 479 | 480 | In the following three paragraphs, a "patent license" is any express 481 | agreement or commitment, however denominated, not to enforce a patent 482 | (such as an express permission to practice a patent or covenant not to 483 | sue for patent infringement). To "grant" such a patent license to a 484 | party means to make such an agreement or commitment not to enforce a 485 | patent against the party. 486 | 487 | If you convey a covered work, knowingly relying on a patent license, 488 | and the Corresponding Source of the work is not available for anyone 489 | to copy, free of charge and under the terms of this License, through a 490 | publicly available network server or other readily accessible means, 491 | then you must either (1) cause the Corresponding Source to be so 492 | available, or (2) arrange to deprive yourself of the benefit of the 493 | patent license for this particular work, or (3) arrange, in a manner 494 | consistent with the requirements of this License, to extend the patent 495 | license to downstream recipients. "Knowingly relying" means you have 496 | actual knowledge that, but for the patent license, your conveying the 497 | covered work in a country, or your recipient's use of the covered work 498 | in a country, would infringe one or more identifiable patents in that 499 | country that you have reason to believe are valid. 500 | 501 | If, pursuant to or in connection with a single transaction or 502 | arrangement, you convey, or propagate by procuring conveyance of, a 503 | covered work, and grant a patent license to some of the parties 504 | receiving the covered work authorizing them to use, propagate, modify 505 | or convey a specific copy of the covered work, then the patent license 506 | you grant is automatically extended to all recipients of the covered 507 | work and works based on it. 508 | 509 | A patent license is "discriminatory" if it does not include within 510 | the scope of its coverage, prohibits the exercise of, or is 511 | conditioned on the non-exercise of one or more of the rights that are 512 | specifically granted under this License. You may not convey a covered 513 | work if you are a party to an arrangement with a third party that is 514 | in the business of distributing software, under which you make payment 515 | to the third party based on the extent of your activity of conveying 516 | the work, and under which the third party grants, to any of the 517 | parties who would receive the covered work from you, a discriminatory 518 | patent license (a) in connection with copies of the covered work 519 | conveyed by you (or copies made from those copies), or (b) primarily 520 | for and in connection with specific products or compilations that 521 | contain the covered work, unless you entered into that arrangement, 522 | or that patent license was granted, prior to 28 March 2007. 523 | 524 | Nothing in this License shall be construed as excluding or limiting 525 | any implied license or other defenses to infringement that may 526 | otherwise be available to you under applicable patent law. 527 | 528 | 12. No Surrender of Others' Freedom. 529 | 530 | If conditions are imposed on you (whether by court order, agreement or 531 | otherwise) that contradict the conditions of this License, they do not 532 | excuse you from the conditions of this License. If you cannot convey a 533 | covered work so as to satisfy simultaneously your obligations under this 534 | License and any other pertinent obligations, then as a consequence you may 535 | not convey it at all. For example, if you agree to terms that obligate you 536 | to collect a royalty for further conveying from those to whom you convey 537 | the Program, the only way you could satisfy both those terms and this 538 | License would be to refrain entirely from conveying the Program. 539 | 540 | 13. Remote Network Interaction; Use with the GNU General Public License. 541 | 542 | Notwithstanding any other provision of this License, if you modify the 543 | Program, your modified version must prominently offer all users 544 | interacting with it remotely through a computer network (if your version 545 | supports such interaction) an opportunity to receive the Corresponding 546 | Source of your version by providing access to the Corresponding Source 547 | from a network server at no charge, through some standard or customary 548 | means of facilitating copying of software. This Corresponding Source 549 | shall include the Corresponding Source for any work covered by version 3 550 | of the GNU General Public License that is incorporated pursuant to the 551 | following paragraph. 552 | 553 | Notwithstanding any other provision of this License, you have 554 | permission to link or combine any covered work with a work licensed 555 | under version 3 of the GNU General Public License into a single 556 | combined work, and to convey the resulting work. The terms of this 557 | License will continue to apply to the part which is the covered work, 558 | but the work with which it is combined will remain governed by version 559 | 3 of the GNU General Public License. 560 | 561 | 14. Revised Versions of this License. 562 | 563 | The Free Software Foundation may publish revised and/or new versions of 564 | the GNU Affero General Public License from time to time. Such new versions 565 | will be similar in spirit to the present version, but may differ in detail to 566 | address new problems or concerns. 567 | 568 | Each version is given a distinguishing version number. If the 569 | Program specifies that a certain numbered version of the GNU Affero General 570 | Public License "or any later version" applies to it, you have the 571 | option of following the terms and conditions either of that numbered 572 | version or of any later version published by the Free Software 573 | Foundation. If the Program does not specify a version number of the 574 | GNU Affero General Public License, you may choose any version ever published 575 | by the Free Software Foundation. 576 | 577 | If the Program specifies that a proxy can decide which future 578 | versions of the GNU Affero General Public License can be used, that proxy's 579 | public statement of acceptance of a version permanently authorizes you 580 | to choose that version for the Program. 581 | 582 | Later license versions may give you additional or different 583 | permissions. However, no additional obligations are imposed on any 584 | author or copyright holder as a result of your choosing to follow a 585 | later version. 586 | 587 | 15. Disclaimer of Warranty. 588 | 589 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 590 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 591 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 592 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 593 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 594 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 595 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 596 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 597 | 598 | 16. Limitation of Liability. 599 | 600 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 601 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 602 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 603 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 604 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 605 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 606 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 607 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 608 | SUCH DAMAGES. 609 | 610 | 17. Interpretation of Sections 15 and 16. 611 | 612 | If the disclaimer of warranty and limitation of liability provided 613 | above cannot be given local legal effect according to their terms, 614 | reviewing courts shall apply local law that most closely approximates 615 | an absolute waiver of all civil liability in connection with the 616 | Program, unless a warranty or assumption of liability accompanies a 617 | copy of the Program in return for a fee. 618 | 619 | END OF TERMS AND CONDITIONS 620 | 621 | How to Apply These Terms to Your New Programs 622 | 623 | If you develop a new program, and you want it to be of the greatest 624 | possible use to the public, the best way to achieve this is to make it 625 | free software which everyone can redistribute and change under these terms. 626 | 627 | To do so, attach the following notices to the program. It is safest 628 | to attach them to the start of each source file to most effectively 629 | state the exclusion of warranty; and each file should have at least 630 | the "copyright" line and a pointer to where the full notice is found. 631 | 632 | 633 | Copyright (C) 634 | 635 | This program is free software: you can redistribute it and/or modify 636 | it under the terms of the GNU Affero General Public License as published 637 | by the Free Software Foundation, either version 3 of the License, or 638 | (at your option) any later version. 639 | 640 | This program is distributed in the hope that it will be useful, 641 | but WITHOUT ANY WARRANTY; without even the implied warranty of 642 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 643 | GNU Affero General Public License for more details. 644 | 645 | You should have received a copy of the GNU Affero General Public License 646 | along with this program. If not, see . 647 | 648 | Also add information on how to contact you by electronic and paper mail. 649 | 650 | If your software can interact with users remotely through a computer 651 | network, you should also make sure that it provides a way for users to 652 | get its source. For example, if your program is a web application, its 653 | interface could display a "Source" link that leads users to an archive 654 | of the code. There are many ways you could offer source, and different 655 | solutions will be better for different programs; see section 13 for the 656 | specific requirements. 657 | 658 | You should also get your employer (if you work as a programmer) or school, 659 | if any, to sign a "copyright disclaimer" for the program, if necessary. 660 | For more information on this, and how to apply and follow the GNU AGPL, see 661 | . 662 | --------------------------------------------------------------------------------