Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare 0.21.0 #225

Merged
merged 2 commits into from
Jan 20, 2020
Merged

Prepare 0.21.0 #225

merged 2 commits into from
Jan 20, 2020

Conversation

cimnine
Copy link
Collaborator

@cimnine cimnine commented Jan 20, 2020

Preliminary release notes

This PR should be merged as the last PR of the 0.21.0 milestone, just before the PR from develop to release is created.

Version 0.21.0

This release contains the following notable changes:

Compatibility with Netbox 2.7 #209

This project has been updated to work with Netbox 2.7.

Updates to our configuration.py file were necessary. This should not impact you if you upgrade from an earlier version of our project. But you will have the possibility to use separate Redis instances for caching and for the rqworker (i.e. webhooks delivery). The current Redis variables are used for the rqworker (i.e. REDIS_HOST, REDIS_PORT, etc.) and there are new variables for the cache (i.e. REDIS_CACHE_HOST, REDIS_CACHE_PORT, etc.). If the variables REDIS_CACHE_* are not defined the configuration file will fall back to the REDIS_* counterparts.

Please note that it is no longer possible to run Netbox without Redis. The variable WEBHOOKS_ENABLED was removed upstream.

Updates to the default startup scripts were necessary. If you have files in the initializers directory, be aware of the following breaking changes:

  • initializers/custom_fields.yml: (see c001626)
    • the selection type was changed to select
     select_field:
    -   type: selection
    +   type: select
       label: Choose between items
       required: false
       filter_logic: exact
       weight: 30
       on_objects:
       - dcim.models.Device
       choices:
       - value: First Item
         weight: 10
       - value: Second Item
         weight: 20
  • initializers/racks.yml (see 7b914d3)
    • Rack types must match one of the 5 rack types given, e.g. '4-post-cabinet'.
    • Rack width must match one of the 2 rack widths given, i.e. '19' or '23'.
     - site: AMS 2
       name: rack-02
       role: Role 2
    -   type: 4-post cabinet
    +   type: 4-post-cabinet
    -   width: 19 inches
    +   width: 19
       u_height: 47
       custom_fields:
         text_field: Description
  • initializers/devices.yml (see 4a58676)
    • Make sure the rack face is spelled in all-lowercase characters.
     - name: server01
       device_role: server
       device_type: Other
       site: AMS 1
       rack: rack-01
    -   face: Front
    +   face: front
       position: 1
       custom_fields:
         text_field: Description
  • initializers/vlans.yml (see 8d8b9a1)
    • Make sure the status is spelled in all-lowercase characters.
     - name: vlan1
       site: AMS 1
    -   status: Active
    +   status: active
       vid: 5
       role: Main Management
       description: VLAN 5 for MGMT
  • initializers/prefixes.yml (see f3403cd)
    • Make sure the status is spelled in all-lowercase characters.
     - description: prefix1
       prefix: 10.1.1.0/24
       site: AMS 1
    -   status: Active
    +   status: active
       tenant: tenant1
       vlan: vlan1
  • initializers/virtual_machines.yml (see f3403cd)
    • Make sure the status is spelled in all-lowercase characters.
     - cluster: cluster1
       comments: VM1
       disk: 200
       memory: 4096
       name: virtual machine 1
       platform: Platform 2
    -   status: Active
    +   status: active
       tenant: tenant1
       vcpus: 8
     - cluster: cluster1
       comments: VM2
       disk: 100
       memory: 2048
       name: virtual machine 2
       platform: Platform 2
  • initializers/dcim_interfaces.yml
    • Make sure the type is a value out of the possible choices and is spelled in all-lowercase characters.
    • All possible choices are found in Netbox's dcim/choices.py
     - device: server01
       enabled: true
    -   type: Virtual
    +   type: virtual
       name: to-server02
  • initializers/ip_addresses.yml
    • Make sure the status is spelled in all-lowercase characters.
     - address: 10.1.1.1/24
       device: server01
       interface: to-server02
    -   status: Active
    +   status: active
       vrf: vrf1

New Build System #214 #222

We've changed our build system once more. It is based on Github Actions now. This provides us more flexibility and hopefully more reliable feedback on pull requests.

Our users should benefit as well by having more reliable releases when a new version of Netbox is out.

The last benefit is that all build-related configurations are now in this repository. This means we can track changes and retrieve pull-requests on them. Additionally, forks get the same build-configuration as well.

Default branch is release

We have switched to a new branching model in the previous version of this project.
Thereby we changed the default branch to be the develop branch. This has led to some confusion. We are now changing the default branch back to the stable branch, i.e. release.

This is also due to the new build system (see above).

Compatibility

This version is compatible with Netbox 2.7.x (and hopefully later versions as well).

⚠️ This version is not compatible with Netbox 2.6.x or lower!

Known Issues

There are no known issues.

@cimnine cimnine added the maintenance The issue describes a maintenance task, such as upgrading a dependency to a certain version. label Jan 20, 2020
@cimnine cimnine added this to the 0.21.0 milestone Jan 20, 2020
@cimnine cimnine changed the base branch from release to develop January 20, 2020 08:38
@cimnine cimnine marked this pull request as ready for review January 20, 2020 09:38
@cimnine cimnine requested a review from tobiasge January 20, 2020 10:01
@cimnine cimnine merged commit 05b9431 into develop Jan 20, 2020
@cimnine cimnine deleted the prepare-0.21.0 branch January 20, 2020 10:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance The issue describes a maintenance task, such as upgrading a dependency to a certain version.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants