DRAFT [Bug]: NIM Install Test: disconnected mode

[mjang]

Describe the problem you have identified

Note: I'll remove "DRAFT" from the front of this bug after I demo this process at the Wed Dec 17 Writers' Sync

Based on https://docs.nginx.com/nginx-instance-manager/disconnected/offline-install-guide/

This is a DRAFT bug. I'll activate it after I complete my review of the NIM Offline Install Guide

Which product or products does this problem relate to?

NGINX Instance Manager

I'm running the steps as noted in the linked doc on:

• A local Ubuntu 24.04.3 install
• Run on a VM (in this case, VMWare Fusion, on Mac, using a build for the M3 chip (ARM64)

Question, possible doc bug #1

• Should we specify prerequisites

  • Candidate location: "Prepare your system for installation"
  • Based on the Linux installs specified later in the doc page
  • Should we specify that the user should update their Linux systems? (e.g. sudo apt update, sudo dnf update)

• In the section for downloading the CRT and Key files

  • Should we also specify downloading the JWT license

• After "Download the installation script"

  • Should we include an example of how to load these files into a VM (should also apply to Docker containers, etc.)
  • Example: ssh user@VM_IP_address
  • scp *.key user@VM_IP_address:

• (DEFINITE BUG) In the Dependencies Needed section

  • Suggestion: while the user is "online"
  • Include instructions on how to install dependencies (dnf install, apt install)
  • The package names do not work for Ubuntu 24.04
  • Example:

  sudo apt install openssl, rsyslog, systemd, tar, lsb-release, openssl, gawk
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  E: Unable to locate package openssl,
  E: Unable to locate package rsyslog,
  E: Unable to locate package systemd,
  E: Unable to locate package tar,
  E: Unable to locate package lsb-release,
  E: Unable to locate package openssl,
  

Note: the installation script for the "tarball" is missing backslashes, so it does not copy in a useful way

• Since the tarball is specific to the distro (example: nim-oss-ubuntu24.04.tar.gz), the -d switch is not required.

Set the operation mode to disconnected

• Should we include a sudo? sudo vi /etc/nms/nms.conf

Question on Configure SELinux section

• This is typically a RedHat / Rocky / Oracle Linux-only situation

Upgrade section

• I don't see nms-instance-manager packages in MyF5. Possibly a MyF5 bug.

If necessary, explain any additional steps to reproduce the problem.

What is the expected or desired behaviour?

No response

Is this problem specific to a particular platform or software version?

No response

Any additional information

No response