Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-28673

Expose instance ID in system information

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.33.0
    • Fix Version/s: None
    • Component/s: Firewall, Support Tools
    • Labels:
    • Notability:
      4

      Description

      Currently a Nexus Repo's node ID is stored in $keystores/node/private.ks. This is the value that shows up in "support --> system information" in the UI, and it is also the value that initially shows up in Nexus Firewall reports as the "instance ID" in IQ Server.

      However, if you restore from backup:

      https://help.sonatype.com/display/NXRM3/Backup+and+Restore

      That node ID is lost, and a new one is generated.

      This leads to an odd situation... the original node ID is still stored in the configuration database:

         {
                  "@class": "deploymentidentifier",
                  "@rid": "#26:0",
                  "@type": "d",
                  "@version": 1,
                  "alias": null,
                  "id": "12345678-F372C0F9-1621313E-DDF0ABBC-607001EB"
              },
      

      So now, if you're trying to figure out which Nexus Repo instance is associated with a firewall report in IQ Server you can't do it, the listed instance ID in the firewall report view will not match the node ID of any of your running instances.

      Expected: I think the issue here is that we've conflated two different concepts into one. The node ID refers to a specific Nexus Repo installation. The instance ID refers to the installation as a whole. This is an important distinction when you start to consider DR, and HA-C. In HA-C for example, there are 3 node ID's, but just one instance ID.

      We should expose the instance ID in our system information UI, and also make it clear in our Firewall documentation what the difference between node ID and instance ID is.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            rseddon Rich Seddon
            Last Updated By:
            Rich Seddon Rich Seddon
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:

                tigCommentSecurity.panel-title