Change Details

Netbox is currently in the 2.4.x versions. 2.5 depends on Python 3.5 is the only real caveat. [x] Write sanitize / dump script for production Netbox -> test Netbox [] Test upgrade in Automation Framework WMCS project [x] Build new netbox instance on Stretch at version 2.4.x [x] Rebuild netbox instance using scapish / puppet [x] Install sanitized dump [x] Test upgrade to 2.5 in place, verify [] Update deploy repository [x] Update our copy of upstream to v2.5.3 after reviewing [] Resubmit deploy repository with our upstream. [] Port existing reports to 2.5 (there are changes to console connections and other things)

Netbox is currently in the 2.4.x versions. 2.5 depends on Python 3.5 is the only real caveat. [x] Write sanitize / dump script for production Netbox -> test Netbox [] Test upgrade in Automation Framework WMCS project [x] Build new netbox instance on Stretch at version 2.4.x [x] Rebuild netbox instance using scapish / puppet [x] Install sanitized dump [x] Test upgrade to 2.5 in place, verify [x] Update deploy repository [x] Update our copy of upstream to v2.5.3 after reviewing [x] Resubmit deploy repository with our upstream. [] Update production Netbox [] Port existing reports to 2.5 (there are changes to console connections and other things)

Netbox is currently in the 2.4.x versions. 2.5 depends on Python 3.5 is the only real caveat. [x] Write sanitize / dump script for production Netbox -> test Netbox [] Test upgrade in Automation Framework WMCS project [x] Build new netbox instance on Stretch at version 2.4.x [x] Rebuild netbox instance using scapish / puppet [x] Install sanitized dump [x] Test upgrade to 2.5 in place, verify [x] Update deploy repository [x] Update our copy of upstream to v2.5.3 after reviewing [x] Resubmit deploy repository with our upstream. [] Update production Netbox [] Port existing reports to 2.5 (there are changes to console connections and other things)