Creating a basic integration for Chef assets

Oomnitza's Chef Connector allows organizations to pull device information from Chef and populate it in Oomnitza. 

Standard Mappings

The following fields can be mapped from Chef using Oomnitza's User Interface:

• CPU
• CPU Count
• Domain
• FQDN
• Hostname
• IP Address
• Mac Address
• Model
• Node Name
• Platform
• Platform Version
• Serial Number
• Total HDD MB
• Total Memory MB
• Uptime Seconds

Custom Mappings

Additional fields may be available through Chef. For details on how to retrieve them, please reach out to [e-mail] or see our article on Creating Custom Field Mappings.

Setup

Details on setting up the Oomnitza Connector can be found in Oomnitza's Articles on Connector Setup. 

The key information required from Chef includes:

• URL: The URL of your organization's Chef Instance
• Client: The Chef username for authentication
• Key_file: The path to the key file (e.g. /path/to/user.pem) being used for authentication. More information on Chef Key files can be found here: https://docs-archive.chef.io/release/server_12-8/auth.html 

The full config file should also contain the following fields:

• Enable - When True, turns the Chef connector on. When False turns the Chef connector off.

A sample Chef config can be found below, which includes a custom mapping from the "Battery Cycle Count" extension attribute. Details on mapping custom attributes can be found here.

[chef]
enable = True
url = https://example.com/organizations/org
client = user
key_file = /path/to/user.pem