NC | NSFS | NSFS NC Systemd example script and docs for RPM installation

[romayalon]

Explain the changes

1. Added systemd example script to the RPM build
2. Added NC NSFS docs for RPM installation and build

Issues: Fixed #xxx / Gap #xxx

Testing Instructions:

• Doc added/updated
• Tests added

[tangledbytes]

I think the command following this line would just install the RPM and not download it.

[romayalon]

@tangledbytes Yes, it's just installation for now because I don't know where will the RPM be published.
@nimrod-becker @guymguym We need to discuss what RPM download instructions will look like,

1. Where these RPMs are published?
2. Will the RPM be based on our regular version branches?
3. Will this RPM build be automated like DS/US builds?

[tangledbytes]

One thing that slightly concerns me (not completely related to this PR) is that I added upgrade manager as part of RPM upgrades, so basically if a user already has NooBaa installed and then the install RPM for version 5.14.1 then our upgrade scripts will kick in and will do its thing. Now that's good but the issue would occur when there would be no postgresql to connect to (NSFS case) and upgrade_script would block (infinite loop) RPM install.

I think we should add a config which disable the upgrade manager. WDYT @romayalon @guymguym?

[PravinRanjan10]

Hi all, Posting the observation for tracking purpose:
Observations on Noobaa-service(nsfs):

1. Systemctl start nsfs (Looks ok)
   Able to start the service, and basic CRUD on buckets done.

2. Systemctl stop nsfs (looks like not smooth stop)
   ● nsfs.service - The NooBaa nsfs service.
   Loaded: loaded (/etc/systemd/system/nsfs.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sun 2023-09-10 21:12:33 PDT; 1s ago
   Process: 1859288 ExecStop=/bin/kill QUIT $MAINPID (code=exited, status=64)
   Process: 1859279 ExecStart=/usr/local/node/bin/node /usr/local/noobaa-core/src/cmd/nsfs.js /tmp/test/ (code=killed, signal=TERM)
   Main PID: 1859279 (code=killed, signal=TERM)

3. Systemctl enable nsfs [seems not working!!]
   [root@pr-ss1-worker-1 ~]# systemctl enable nsfs
   The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
   settings in the [Install] section, and DefaultInstance for template units).
   This means they are not meant to be enabled using systemctl.
   Possible reasons for having this kind of units are:

   1. A unit may be statically enabled by being symlinked from another unit’s
      .wants/ or .requires/ directory.
   2. A unit’s purpose may be to act as a helper for some other unit which has
      a requirement dependency on it.
   3. A unit may be started when needed via activation (socket, path, timer,
      D-Bus, udev, scripted systemctl call, ...).
   4. In case of template units, the unit is meant to be enabled with some
      instance name specified.

4. Systemctl disable nsfs [seems not working]

5. Sometimes nsfs is in auto-start mode (specially, run enable and start)
   ● nsfs.service - The NooBaa nsfs service.
   Loaded: loaded (/etc/systemd/system/nsfs.service; static; vendor preset: disabled)
   Active: activating (auto-restart) (Result: exit-code) since Sun 2023-09-10 21:17:35 PDT; 1s ago
   Process: 1865942 ExecStart=/usr/local/node/bin/node /usr/local/noobaa-core/src/cmd/nsfs.js /tmp/test/ (code=exited, status=1/FAILURE)
   Main PID: 1865942 (code=exited, status=1/FAILURE) (edited)

[romayalon]

@PravinRanjan10
Hey, this is just an example script, the install section is empty, have you tried my answer on slack?

[PravinRanjan10]

@PravinRanjan10 Hey, this is just an example script, the install section is empty, have you tried my answer on slack?

Okay. Edited the nsfs.service file and able to enable/disable the nsfs. But stop still looks failed!!.

[nimrod-becker]

we'll look at stop