Versions Compared

Old Version 9

changes.mady.by.user The Force

Saved on

compared with

New Version 10

changes.mady.by.user The Force

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from this space and version 8.0.0

...

An important first step is determining what items you currently are , (or will be, ) tracking, and what relationship they have with each other.

ProVision ProVision's flexible Resource resource system allows you create and customize detailed entries for any type of item you may want to track: Customerscustomers, Contactscontacts, Data Centersdata centers, Routersrouters, VMs, and more. These types of resources are labeled as "Sections" in ProVision. Once a section Section is made, individual items (resources) may be created as a part of that Section. Each Section may have different Gadgets selected, which then provide additional functionality on a resource entry page. 

...

In ProVision, standard user permissions are set by resource and functional area (IPAM, Resource, Peering, etc), with fine-grained permissions able to be set for specific resources.

Global Admin permissions give access to additional functions such as configuration settings, importing, and Scheduler tasks. Determine which users will require administrative access, and which will have access to only specific resources or functional areas.  You You will need to get more specific later, but having some high level groups to work with is a great start.

See: Users & Permissions


Overview Video: First Steps - Part 2

...

  • Make sure that you use UTF-8 encoding, remove extraneous blank rows, and compare your data to the data fields available in ProVision, shown under "Which Import Tool Should I Use?".
  • Review sample files if desired to see example formats.
  • If you plan to track custom types of Resources resources by creating Sections, you will need to create a Section with custom fields, and verify that your spreadsheet contains the same fields.

...

Before importing DNS zones, it is recommended that a DNS Group be created to hold the zones being imported, and that the DNS server be added into ProVision so that zone updates may be pushed.

For general DNS takstask, see:   DNS Administration, DNS Tab, Working with DNS Groups, Working with DNS Servers

...

The order in which items are added will depend on what ProVision functional area (Resources, IPAM, DNS) you will be using, and what the current / desired data structure is.

In general, the following order is recommended: 

...

Info

Note: If you already have "Resource" data associated with your IP block data (ie, as fields in a spreadsheet with Resource Name and Resource ID), you may choose not to create those resources ahead of time. The IP Import from CSV tool will give you an option to create those Resources resources during the IP import process.

...

Adding resources manually may be done at any time under the Resources Tab tab, by clicking the "Add Entry" button. 

...

C) Add DNS servers and zones

If using the DNS Module module in ProVision, you will need to add your servers prior to importing zones. 

...

Add DNS Severs 

Adding DNS Servers servers requires administrative access.

Servers are added under the DNS Tab tab of ProVision, under "DNS Servers". Click on "Add Server" and fill out the server information. 

...

Information for specific server types and options is available under the following sections:

...


Import DNS Zones 

After creating the applicable servers in ProVision, you may import or manually add DNS zones. 

ProVision offers multiple DNS zone import options, available under the Data Import tab in the Admin section. For more information on importing DNS zones, see Importing your Data and Import DNS Zones. 


BIND Zone Import

      • Imports using the named.conf configuration file tied to the zones you are uploading, a .zip or .tar file of the zones themselves, and an optional .csv file mapping zones to customers.

...

      • Imports DNS zones using a provided Hosthost, Usernameusername, and Passwordpassword.  The The InfoBlox import pulls all zones on the InfoBlox LOCAL grid and adds them to a designated Groupgroup. It is advised to to create a DNS Group prior to the import with default parameters and NS records to be inherited by the imported records.

...

      •  Imports DNS zones using a NS One API Key. It is advised to create a DNS Group prior to the import with default parameters and NS records to be inherited by the imported records. 

...

      • Imports DNS zones using a Dyn DNS Customer Namecustomer name, Usernameusername, and Passwordpassword. It is advised to to create a DNS Group prior to the import with default parameters and NS records to be inherited by the imported records. 

...

      • Imports DNS zones using a DNSMadeEasy API Key and API Secret. It is advised to create a DNS Group prior to the import with default parameters and NS records to be inherited by the imported records. 

...

      • Imports DNS zones using IPPlan MySQL database options. It is advised to create a DNS Group prior to the import with default parameters and NS records to be inherited by the imported records. 

...

Manually adding zones may be done at any time from the  DNS Tab tab. See Working with DNS Zones - Common Tasks and Editing DNS Zones.

...

In ProVision, the permissions structure is handled by assigning users to groups, then setting specific resource-level C/R/U/D permissions for that group. It is designed to give you as much flexibility as you need to accommodate most use cases. When mapping out the permissions structure for your organization, keep in mind who you want to access to application:

  • Internal Users users and Roles roles (Admins, Read-Only, etc.)
  • Partners related to multiple specific Resources/Accountsresources or accounts
  • Customers / Departments departments with limited view to only their respective Resources/Accountsresources or accounts

See: Users & Permissions, Working with Users and Groups

Users and Groups groups may be added at any time. However, assigning permissions to users and groups is best done after the applicable resource hierarchy has been added into ProVision.

...

With the basic data now imported, and users set up, you (and your team) are ready to work in ProVision!

Refer to our User Guide and Admin Guide for details on standard user and admin level areas of ProVision. Or, follow the links below for additional details grouped by specific task areas:

Concepts:

Resources:

IPAM:

DNS:

DHCP:

Peering: