https://github.com/theforeman/smart_proxy_dhcp_infoblox
foreman smart proxy for dhcp w/ infoblox
https://github.com/theforeman/smart_proxy_dhcp_infoblox
dhcp-provider hacktoberfest smart-proxy
Last synced: 3 months ago
JSON representation
foreman smart proxy for dhcp w/ infoblox
- Host: GitHub
- URL: https://github.com/theforeman/smart_proxy_dhcp_infoblox
- Owner: theforeman
- License: gpl-3.0
- Created: 2016-04-06T20:06:02.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2025-03-06T09:23:02.000Z (7 months ago)
- Last Synced: 2025-06-14T04:25:50.439Z (4 months ago)
- Topics: dhcp-provider, hacktoberfest, smart-proxy
- Language: Ruby
- Homepage:
- Size: 135 KB
- Stars: 10
- Watchers: 4
- Forks: 18
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# SmartProxyDhcpInfoblox
This plugin adds a new DHCP provider for managing records with infoblox servers
## Installation
See [How_to_Install_a_Smart-Proxy_Plugin](http://projects.theforeman.org/projects/foreman/wiki/How_to_Install_a_Smart-Proxy_Plugin)
for how to install Smart Proxy plugins
This plugin is compatible with Smart Proxy 1.11 or higher.
Example installation command via foreman-installer:
```
# foreman-installer --enable-foreman-proxy-plugin-dhcp-infoblox \
--foreman-proxy-dhcp-provider infoblox \
--foreman-proxy-plugin-dhcp-infoblox-record-type host \
--foreman-proxy-dhcp-server 192.168.201.2 \
--foreman-proxy-plugin-dhcp-infoblox-username admin \
--foreman-proxy-plugin-dhcp-infoblox-password infoblox \
--foreman-proxy-plugin-dhcp-infoblox-network-view default \
--foreman-proxy-plugin-dhcp-infoblox-dns-view default
```
When installing using "gem", make sure to install the bundle file:
echo "gem 'smart_proxy_dhcp_infoblox'" > /usr/share/foreman-proxy/bundler.d/dhcp_infoblox.rb
## Configuration
To enable this DHCP provider, edit `/etc/foreman-proxy/settings.d/dhcp.yml` and set:
:use_provider: dhcp_infoblox
:server: IP of infoblox server
:subnets: subnets you want to use (optional unless you set infoblox_subnets to false)
Configuration options for this plugin are in `/etc/foreman-proxy/settings.d/dhcp_infoblox.yml` and include:
* username: API Username
* password: API Password
* record_type: host / fixedaddress (see different record types chapter)
* used_ips_search_type: record_type / used
## Different record types
The main difference between host and fixedaddress is that a host record already includes the dns records. It's an infoblox object that includes dhcp/a record/ptr records. If you use the host objects there is no need to use a dns smart proxy. Everything gets handled inside the dhcp smart proxy. This does however limit functionality. You can't delete conflicting records or you can't change dns names using foreman gui. Beware when editing host objects manually in infoblox, once you delete a host in foreman all associated host objects get deleted.
If you chose to use fixedaddress you'll need to use the infoblox dns smart proxy (https://github.com/theforeman/smart_proxy_dns_infoblox) if you want to manage dns records.
## Used IP search type
When using "record_type" here, used IPs will be looked up among the record type you select on the record_type setting (host or fixedaddress). So everything which is not a host or a fixedaddress (depending on the setting), will be defined as free and can be selected as an IP to provision a host.
If the IP is used by just a DNS A entry for example, this can lead to conflicts. If "used" is set here, any usage of an IP will mark it as used and the IP will not be selected as free ip to provision a host.
Usages without a mac address will get a dummy mac address ("00:00:00:00:00:00"), when Foreman looks for "all_hosts".
## SSL
The plugin enforces HTTPS server certificate verification. Follow a standard CA cert installation procedure for your operating system. It's possible to either download the server certificate from Infoblox web UI or use openssl command to extract it from server response. Here are example steps for Red Hat compatible systems:
```
# update-ca-trust enable
# openssl s_client -showcerts -connect 192.168.201.2:443 /etc/pki/ca-trust/source/anchors/infoblox.crt
# update-ca-trust extract
```
For Debian-compatible systems:
```
# openssl s_client -showcerts -connect 192.168.201.2:443 /usr/local/share/ca-certificates/infoblox.crt
# update-ca-certificates
```
To test the CA certificate, a simple curl query can be used. This is a positive test:
```
# curl -u admin:infoblox https://192.168.201.2/wapi/v2.0/network
[
{
"_ref": "network/ZG5zLm5ldHdvcmskMTkyLjE2OC4yMDIuMC8yNC8w:192.168.202.0/24/default",
"network": "192.168.202.0/24",
"network_view": "default"
}
]
```
And a negative one:
```
# curl -u admin:infoblox https://192.168.201.2/wapi/v2.0/network
curl: (60) SSL certificate problem: self signed certificate
```
## Contributing
Fork and send a Pull Request. Thanks!
## Copyright
Copyright (c) 2016 Klaas Demter
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see .