Versions Compared

Old Version 50

changes.mady.by.user The Force

Saved on

compared with

New Version Current

changes.mady.by.user The Force

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Future

...

Release Roadmap

 

5.3.0 Release - Q2 2016

  • Minor IPAM updates
  • User Preferences Page
  • Logging Revamp
  • Minor customer feature requests
  • Bug fixes

6.0 Release - Q4 2016


8.1 Release

  • 'Native' 6connect managed DNS and monitoring
  • New IPAM Tree view
  • Per-Netblock IPAM alerts

Seeking Connector Options Feedback - if you want these, let us know!

VMware NSX plugin - a few customers are managing VMware environments and would like to see some tighter integration of network provisioning. Initial discussions have been centered around a similar approach to our Neutron use case. ProVision would be able to natively assign IP blocks (subnet and host) for VMware's use. Additional integration would be DNS zone record updates (forward, reverse) to the DNS server specified in ProVision (the server could be physical, virtual, service, etc.). We also received a request for DHCP support that may also be explored so that all IP data stays centralized. We are assuming automation of SWIP/RIPE functions for IP data to help reduce provisioning times. - CURRENTLY IN CLOSED BETA

VMware ESX - Currently in Beta

  • Resources Chart View enhancements (color/data shown, etc.)
  • APIv2 Framework 
  • UI Redesign/Improvements
  • DNS v3
    • DNS -> Resources
    • DNS Audit v2
    • DNS Gadget - forward/reverse zone auto generator - update and make more intuitive
    • DNS Zone list - multiple updates/Action menu options
    • DNS Zone editor - UI update, additional filtering/search options
  • Licensing Engine
  • Reporting Revamp (incl VLAN, scheduled reports)
    • IPAM - Aggregate utilization report via email (CSV, PDF) with basic format options
  • Admin - Update text to Disable for Users and Groups and "show all”/gray out disabled and allow for re-enabling

  • IPAM - SWIP updates for more intuitive use, improved support for Detailed Reassignment and Reallocation

  • Welcome - improve on-boarding/initial screen for invalid CIDR errors (RIPE data)
  • Customer Feature Requests
    • IP Assignment Rules - IP reservations, SWIP functions

    • Resources - Additional custom field type(s) for Resource Sections

    • IPAM - Add field(s) for assignments - Add meta data field so customers can create multiple custom fields for whatever data they want to attach to block

    • Resources
      • Multi-edit of Resources (similar to IPAM)
      • Bulk Assignment of Resources (similar to IPAM)
    • Peering Improvements - View by Peer (across exchanges)
    • RADIUS - encrypted auth options (CHAP, MS-CHAP, MS-CHAPv2, EAP)
  • Backup v2 
  • Connector(s) - TBD
2016 Big Roadmap Items (in scoping stage) - if you want these, let us know!

VMware vCenter - Currently in Beta


Circuit Manager (includes provisioning support for Supported Connectors) - building on the UI updates in addition to the robustness of the Resource Manager in ProVision, we have received multiple requests to build a dedicated Circuit Management module for ProVision. This would allow physical and virtual circuits to be provisioned across datacenter endpoints. We are scoping this as a full module, so the user will be able to "build" a circuit in the UI and define the various endpoints, then ProVision will actually configure the circuit.

Infoblox Connector - we are scoping this out to allow bi-directional support and state management of IPAM, DNS and DHCP (DDI) functions provided by multiple Infoblox appliances. With the new DNS v3 in our 6.0 Release, we will have the framework in place to slot in this functionality and allow selective management of these elements "in place". We expect to use the SOAP API to tie the integration with ProVision.

SolarWinds Connector - we are scoping this out on two fronts based on some requests - one is for an IPAM connector/importer, the other is integration of their monitoring data into ProVIsion and the Resource Manager. We are still scoping this out, but see this as a great use case for our Reverse API and functionally similar to the Observium integration we built earlier this year.

OpenStack Neutron plugin - we are scoping this out on a few fronts. We are trying to be flexible on the Neutron plugin side, and accommodate various SDN technologies. We are scoping a plugin that would allow users to selectively use ProVision IPAM, DNS or DHCP services along with the Resource Manager for whatever hierarchies are being deployed.VMware NSX plugin - a few customers are managing VMware environments and would like to see some tighter integration of network provisioning. Initial discussions have been centered around a similar approach to our Neutron use case. ProVision would be able to natively assign IP blocks (subnet and host) for VMware's use. Additional integration would be DNS zone record updates (forward, reverse) to the DNS server specified in ProVision (the server could be physical, virtual, service, etc.). We also received a request for DHCP support that may also be explored so that all IP data stays centralized. We are assuming automation of SWIP/RIPE functions for IP data to help reduce provisioning times.

CloudFoundry plugin - Container technology is still maturing, but there are some simple functions that would be a big time savers. One example is DNS, the initial zone setup is manual and could be automated with a simple Connector. With IP data, there is a use case for using the message bus to track and log IP data history for services in a scalable way. Their use of IP data is a bit different, but without a clear use case (especially with IPv6) we would need to some more information.


...