cci-moc/moc-ansible-netbox

moc-ansible-netbox

Collection of playbooks to populate MOC's netbox instance.

Requires the netbox collection that can be installed with:

ansible-galaxy collection install netbox.netbox

moc-ansible-netbox's Issues

Register Mellanox Switches

This is in kumo for the Power9 servers

Improve the way we register devices with an IP

moc-ansible-netbox/register-system.yaml

Line 187 in 5ec4ed5

when: interface.type == "ether" and interface.ipv4.address is defined

We have devices that have assigned IP addresses to a bridge and those don't get recorded due to above. Maybe we should just record all IP address or have some blacklist to ignore certain devices (docker, virbr etc).

Register weird IPMI switches in kumo and engage1

They are all different make and models so will modify the hosts file a bit.

Register Virtual Machines in netbox

Only for the sole purpose of tracking IP address usage so should keep the script simple.

add site.yaml

Given that the number of playbooks is increasing and they should be run in a specific order (static data first, then switches, and then everything else).

Register VLANs in netbox

From all our switches

Register systems that we don't have SSH access to

Basically all baremetal nodes in use by researchers.

Track the usage of switchports

We need to record what a switchport is connected to. This will help us plan new connections.

I recorded our current 40G port usage of Kaizen switches in an excel sheet (🙄 ) here: https://docs.google.com/spreadsheets/d/1kKNx2HKtuTL_UZFDsOMfKqk-9KJ3Yd46lvJRn6P-3Zc/edit#gid=1581716051

This is blocked on CCI-MOC/ops-issues#161

Register more systems without SSH access

Now that we have a method of statically adding machines, we should populate it with more machines.

A simple script can query HIL for such systems and produce the yaml with the required information (switchports, NICs etc).

Register IPMi switches in netbox

A playbook that does it statically

register maas VMs into netbox.

and hardware running under maas.

register OCT switches

those should all support dellemcos9 ansible modules so should be straightforward.

Add kumo blades that are a part of a Chassis

The recommended way of doing that in netbox is to create a parent device that supports bays (the chassis) and consumes Rack space. Then the blade servers are of 0U height that are assigned the bay in the parent device.

Create cables between ipmi switches and interfaces

Register IP addresses ranges and usage in netbox

We should only create the ranges first, hopefully as we add all our systems (physical and virtual) the usage will also be updated.