task/TUP-331 -- system monitor client

[jchuahtacc]

Overview:

System monitor

Related:

• TUP-331

Changes:

• System monitor client ported to typescript
• useSystemMonitor hook
• requests hooks (useGet, usePost) now accept a configuration object with alternate baseUrl
• local development baseUrl is now http://localhost (as per https://github.com/TACC/tup-services/pull/13) to not conflict with tup-cms local development

Testing:

1. Start tup-services from https://github.com/TACC/tup-services/pull/13 (localhost serves system monitor files via nginx)
2. npx nx serve tup-cms
3. Browse to http://localhost:8000/dashboard/login and log in.
4. You should see the system monitor. It may take a moment or two to update

UI:

Notes:

• @wesleyboar which core-styles do i need to import for table styles?
• Requires https://github.com/TACC/tup-services/pull/13

[wesleyboar]

I tried to review, but I failed. I do not know how to authenticate to http://localhost/sysmon/.

[wesleyboar]

I get a 403 when I visit http://localhost/sysmon/.

I don't know what username and password to use, nor do I know where to enter that username and password.

What I Have Tried

1. Reviewed https://github.com/TACC/tup-services/pull/5, but the README has since changed.
2. Followed docs/ADMIN.md, and "issued" two admins, my-local-admin and [my TACC username], but I still get 403 at http://localhost/sysmon/.
3. Used my TACC username and TACC password for dev.env and integration.env and restarted the containers, but still get a 403 at http://localhost/sysmon/.
4. Reviewing http://localhost/docs, but mosts POSTs require a JWT.
5. Curled /auth with my TACC username and TACC password, but received Unable to authenticate message.
6. Curled /auth/public_key, but that gives me a public key not a JWT.