Versions Compared

Key

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

...

  • Nodes are saved in the same collection. As a consequence: 
    • Import from NMIS option is not available. 
    • IPs are not saved in opConfig database neither. They are part of the inventory collection. They cannot be edited, as modifying an IP has more implications that editing only the IP, there is a bunch of information related.
    • os_info and connection info properties are part of the node configuration attribute. They should be accessed as follows:
      • configuration.os_info.
      • configuration.connection_info.

...

  • Be familiar with opConfig basic concepts
  • The individual performing this installation has a small bit of Linux experience
  • Root access is available
  • Internet access is required for installing any missing but required software packages
  • NMIS 9 must be installed on the same server that opConfig is being installed on. Here you can read the NMIS installation guide. NMIS 9 is not required to be running, but opConfig needs the NMIS dependencies to work. 
  • You will need a license for opConfig ( CONTACT US for an evaluation license )

...

Your next step should be to consult the basics for managing a node and the complete opConfig User Manual, which will tell you how to tell opConfig what commands to perform with which nodes, how to customize opConfig's behaviour to suit your needs and so on.

Please feel free to leave comments and suggestions below!

Upgrade to version 4.2.0 and later.

...

Starting from version 4.2.0,  we have made significant changes on our internal shared code for all our applications to work on Opmantek's latest and fastest platform, however, previously installed product are not compatible with this version. 

To find out more about this upgrade please read: 


What's next? 

...