Third Party Software Integration for Deployed Containers

[cmyers-mieweb]

We will need a way to automate a step by step installation process to add additional server software that is typically added after an LXC is stood up. If Developers make projects on demand it will be difficult to keep track of what exists and what needs installed to meet server setup requirements.
Some concerns that pop up directly in my head.

• For containers made for enterprise use, we will need to integrate the Netbox API to call a request to create a new container entry. On deletion we can call the API to request to remove the existing entry.
• Will need to find solutions to install virus protection such as ClamAV, and also modify the Wazuh endpoint to reflect an enterprise environment.
• Unsure what/if we want to run and keep backups, or make it an option.
• PMM integration with database specific containers?
• Zabbix monitoring through a landing ran by the manager? Set to immediately add the host to a developer group once the agent is live.

[runleveldev]

1. For the Netbox API, do we need to push containers into Netbox or do we develop a Netbox plugin to pull containers from the Manager API?
2. I think we can just install stock ClamAV in all containers, even opensource ones?
3. We discussed no backups for individual containers, I have a seperate plan for "shared volumes" based on CephFS storage which could be candidates for backups, but this will need further discussion.
4. PMM is a good idea for future DBaaS plans. Related: OpenTelemetry Stack #227
5. We could handle Zabbix via Env Vars like we do Wazuh, but I'm thinking that the person creating a container needs to be responsible for any Zabbix-generated alerts. This relates to OpenTelemetry Stack #227 and Auto monitoring of services #148

[cmyers-mieweb]

1. The API would be called in two seperate functions, on the creation step, and on the delete step, probably something like this.

# Update KEYS in settings.js to include netbox_url and netbox_token
const KEYS = [
  'push_notification_url',
  'push_notification_enabled',
  'push_notification_api_key',
  'smtp_url',
  'smtp_noreply_address',
  'default_container_env_vars',
  'netbox_url',
  'netbox_token',
];

# New functions in netbox.js for the actual calls
async function createVirtualMachine(baseUrl, token, { hostname, clusterName, ipv4Address }) {
  const clusterId = await findClusterId(baseUrl, token, clusterName);

  const vm = await nbFetch(baseUrl, token, '/virtualization/virtual-machines/', {
    method: 'POST',
    body: JSON.stringify({
      name: hostname,
      cluster: clusterId,
      status: 'active',
      comments: NETBOX_COMMENT,
    }),
  });

async function deleteVirtualMachine(baseUrl, token, hostname) {
  try {
    const data = await nbFetch(
      baseUrl,
      token,
      `/virtualization/virtual-machines/?name=${encodeURIComponent(hostname)}&limit=1`,
    );