feat(influxdb3): update install for DEB/RPM and add admin/security

[jdstrand]

This documents the updated Linux packaging that will be in 3.8:

• feat: Linux service management influxdb#27026
• https://github.com/influxdata/influxdb_pro/pull/1811

Closes https://github.com/influxdata/DAR/issues/546
Closes #6396

cc @peterbarnett03

[jdstrand]

@jstirnaman - I'm not sure why the systemd links are failing (see https://github.com/influxdata/docs-v2/actions/runs/20318046271/job/58366824186?pr=6643). They all work fine....

[peterbarnett03]

@jdstrand Thanks! This is great. I was able to successfully install and run on AWS Ubuntu. 😎

Two things that come to mind from an experience perspective:

1. Can we update the docs to highlight the importance of --license-email and --license-type plus confirming email on first run? That's quite hidden unless inspecting the logs and it doesn't error out, so people may think it's working.
2. Something we can probably adjust for a future release (or perhaps not even release related) is elevating those license .conf pieces up if they're running on Enterprise given how critical they are.

Those can be follow-ups, I don't think they preclude merging this info in.

[jdstrand]

@jdstrand Thanks! This is great. I was able to successfully install and run on AWS Ubuntu. 😎

Two things that come to mind from an experience perspective:

1. Can we update the docs to highlight the importance of --license-email and --license-type plus confirming email on first run? That's quite hidden unless inspecting the logs and it doesn't error out, so people may think it's working.

2. Something we can probably adjust for a future release (or perhaps not even release related) is elevating those license .conf pieces up if they're running on Enterprise given how critical they are.

Those can be follow-ups, I don't think they preclude merging this info in.

I can add some language for this.

[jdstrand]

@jdstrand Thanks! This is great. I was able to successfully install and run on AWS Ubuntu. 😎
Two things that come to mind from an experience perspective:

1. Can we update the docs to highlight the importance of --license-email and --license-type plus confirming email on first run? That's quite hidden unless inspecting the logs and it doesn't error out, so people may think it's working.
2. Something we can probably adjust for a future release (or perhaps not even release related) is elevating those license .conf pieces up if they're running on Enterprise given how critical they are.

Those can be follow-ups, I don't think they preclude merging this info in.

I can add some language for this.

#6650