Skip to main content
Version: 7.2405.x.x LTS

Appendix I - Admin CLI and RPM installation changes introduced with 4.33.0.8

As part of the normal software maintenance and modernization, Nevis is adapting the functionality offered in the administrative command-line interface (CLI) shipped with Nevis components, as well as minor adjustments as part of the RPM installation process.

In the process of streamlining offered functionality, reducing complexity, and providing better support for product features, the CLI functionality will be changed. These adjustments require deprecation and removal of certain features. However, primary CLI commands remain available.

We encourage our customers to use nevisAdmin4 for managing Nevis installations and configurations, for customers who like to still use the native CLI scripts, Nevis provides a ported set of functionality, and tries to make the changes as small as possible.

The changes will be rolled out and take effect with the November 2021 Rolling Release.

RPM installation changes

  • The component RPM installation does not create the runtime users and groups.

    • Change type: behaviour

    • Impact: No impact for Admin3, Admin4, K8s, or Nevis Appliance. Manual setups are affected.

    • Alternative:

      Manual user creation via shell command:

      groupadd -g 30000 nvbgroup
      useradd -g nvbgroup -d /tmp -s /bin/false -u 30003 nvauser

      The example above is related to creating the nevisAuth user and group.

  • The component RPM installation does not automatically generate sudo entries.

    • Change type: behaviour

    • Impact: No impact for Admin3, Admin4, K8s, or Nevis Appliance. Manual setups are affected.

    • Alternative:

      Manual user creation via shell command:

      %nvbgroup  ALL=(nvauser) NOPASSWD:/usr/bin/nevisauth
      %nvbgroup ALL=(nvauser) NOPASSWD:/opt/nevisauth/bin/nevisauth

      The example above is related to creating the nevisAuth user and group.

  • Only one component version can be installed. Installing multiple component versions is no longer possible.

    • Change type: behaviour
    • Impact: The component is directly installed under /opt/<component-name>.
    • Alternative: None, multi-version is deprecated and will be removed.
  • Standalone deployment is the only supported deployment type.

    • Change type: removal
    • Impact: File and directory names no longer contain the word “standalone” to differentiate between containers.
    • Alternative: None, only standalone containers are supported.
  • Scripts directly related to adnpkg are removed from the installation path(s).

    • Change type: removal
    • Impact: The /opt/<component-name> installation path no longer contains adnpkg-related scripts.
    • Alternative: None.

Admin CLI changes

  • <component> inst create <instance> Does not automatically create the user and group.

    • Change type: behaviour

    • Impact: Only Admin3 users are impacted for new machine installations.

    • Alternative:

      Manual user creation via shell command:

      groupadd -g 30000 nvbgroup
      useradd -g nvbgroup -d /tmp -s /bin/false -u 30003 nvauser

      The example above is related to creating the nevisAuth user and group.

  • <component> inst create <instance> Does not automatically add the sudo profiles to /etc/sudoers as the sudo entries have no relation to the instance created.

    • Change type: behaviour

    • Impact: No impact for Admin3, Admin4, K8s, or Nevis Appliance. Manual setups are affected.

    • Alternative:

      Manual editing of the sudoer profile /etc/sudoers via shell command:

      %nvbgroup  ALL=(nvauser) NOPASSWD:/usr/bin/nevisauth
      %nvbgroup ALL=(nvauser) NOPASSWD:/opt/nevisauth/bin/nevisauth

      The example above is related to creating the nevisAuth user and group.

  • <component> inst create <instance> <myProperties.properties> Supplying variables via a .property file is removed.

    • Change type: removal

    • Impact: No impact for Admin3, Admin4, K8s, or Nevis Appliance. Manual setups are affected.

    • Alternative:

      Manually extracting and passing the arguments of the properties file via shell command:

      cat myProperties.properties | xargs -x <component> inst create <instance>

      Additionally, providing key—value pairs as attributes to the inst create command is still supported.

  • <component> inst remove <instance> Does not automatically remove sudo profiles from /etc/sudoers.

    • Change type: behaviour
    • Impact: No impact for Admin3, Admin4, K8s, or Nevis Appliance. Manual setups are affected.
    • Alternative: Manually removing the sudo entries from /etc/sudoers.
  • <component> handover is removed.

    • Change type: removal

    • Impact: -

    • Alternative:

      Manual instance creation and start via shell commands:

      <component> inst create <instance>
      <component> <instance> start
  • <component> pkg only lists the currently installed version.

    • Change type: behaviour
    • Impact: -
    • Alternative: Only one component version is supported.
  • <component> pkg activate <version> is removed.

    • Change type: removal
    • Impact: When upgrading an instance, the old rpm needs to be uninstalled beforehand.
    • Alternative: Only one component version is supported.
  • <component> <instance> start does not display the status after starting the instance.

    • Change type: behaviour
    • Impact: -
    • Alternative: Manually calling the <component> <instance> status shell command.
  • <component> <instance> stop does not display the status after starting the instance.

    • Change type: behaviour
    • Impact: -
    • Alternative: Manually calling the <component> <instance> status shell command.
  • <component> <instance> status does not support the [swdep] argument.

    • Change type: removal
    • Impact: -
    • Alternative: None.
  • <component> <instance> analyse [all] is removed.

    • Change type: removal
    • Impact: -
    • Alternative: Manual gathering of information.
  • <component> <instance> config does not validate the config against the schema definition (xsd) after saving.

    • Change type: behaviour
    • Impact: Configuration errors will only be logged at instance start.
    • Alternative: None.
  • <component> <instance> config vmargs opens the env.conf file for editing.

    • Change type: behaviour
    • Impact: -
    • Alternative: None.
  • <component> <instance> config export <tarfile> is removed.

    • Change type: removal
    • Impact: -
    • Alternative: Manual backup of configuration directory via tar shell command.
  • <component> <instance> config import <tarfile> is removed.

    • Change type: removal
    • Impact: -
    • Alternative: Manual unzipping of backed up configuration directory via tarshell command.
  • <component> <instance> config backup list is removed.

    • Change type: removal
    • Impact: -
    • Alternative: None.
  • <component> <instance> config backup <descr> is removed.

    • Change type: removal
    • Impact: -
    • Alternative: None.
  • <component> <instance> config backup remove <stamp> is removed.

    • Change type: removal
    • Impact: -
    • Alternative: None.
  • <component> <instance> config backup restore <stamp> is removed.

    • Change type: removal
    • Impact: -
    • Alternative: None.
  • <component> <instance> log err [all|server] is removed.

    • Change type: removal
    • Impact: -
    • Alternative: Manual filtering via cat and egrep shell commands.
  • <component> <instance> log show [all|server] is removed.

    • Change type: removal
    • Impact: -
    • Alternative: Manual filtering via cat and egrep shell commands.
  • <component> <instance> log tail [all|server] is removed.

    • Change type: removal
    • Impact: -
    • Alternative: Manual filtering via tail shell commands.
  • <component> <instance> signer [show] is removed.

    • Change type: removal
    • Impact: -
    • Alternative: Using nevisKeyBox, neviskeybox list -slot <slot>
  • <component> <instance> signer create is removed.

    • Change type: removal

    • Impact: -

    • Alternative:

      Using nevisKeyBox:

      neviskeybox selfcert -slot <slot> -label <label> -cn "<label>@`hostname`" -days <valid> -certtype sign
      neviskeybox passwd -keep -slot <slot> -label <label>
      neviskeybox access -user <owner> -slot <slot> -label <label>

      Example values: slot: nevis, label: authSigner, owner: nvauser, valid: 7120

  • <component> <instance> signer export is removed.

    • Change type: removal
    • Impact: -
    • Alternative: Manual command: find /var/opt/keybox/<slot> | egrep 'trust..jks$|trust..pem$|trust.*.der$'
  • <component> <instance> signer delete is removed.

    • Change type: removal

    • Impact: -

    • Alternative:

      Using nevisKeyBox:

      mv /var/opt/keybox/<slot>/<label>_keypass /var/opt/keybox/<slot>/<label>_keypass.bkp
      neviskeybox delete -slot <slot> -label <label>
      neviskeybox delete -slot <slot> -label <label> -trust
  • <component> <instance> encSecret is removed.

  • <component> <instance> text <lang> is removed.

    • Change type: removal
    • Impact: -
    • Alternative: Manual editing of the litdict file.
  • <component> <instance> text init <lang> is removed.

    • Change type: removal
    • Impact: -
    • Alternative: Manual creation of a new litdict file.
  • nevisauth <instance> config krb5 is removed.

    • Change type: removal
    • Impact: -
    • Alternative: Manual editing of the configuration file vi /var/opt/<component>/<instance>/conf/java-krb5.conf
  • nevisauth <instance> config krb-cred is removed.

    • Change type: removal
    • Impact: -
    • Alternative: Manual editing of the configuration file vi /var/opt/<component>/<instance>/conf/kerberos-credentials.properties
  • nevisauth <instance> config events

    • Change type: removal
    • Impact: -
    • Alternative: Manual editing of the configuration file vi /var/opt/<component>/<instance>/conf/nevisevents.xml