--- title: "Frontend WG, 28th July 2023" tags: frontend, dashboard, oakestra datetime: 2023-07-20T{{time}}UTC location: Online, Discord, the `#voice-meeting` voice channel teams: - frontendWG participants: - Daniel (DM) - Giovanni (GB) - Nitinder (NM) - Michael (MS) --- ## 📋 Agenda - [x] DM: Update dashboard readme and docs with latest build instructions - [x] GB: test dashboard in oakestra compose file - [x] NM: Send email to HPI for intermittent VMs - [x] DM: description about multi sla deployment in documentation - [x] NM: Add issues to optimize bits about dashboard. - [x] DM: Create SMTP-component issue on oakestra repo. Describe the api that you need from front end to add a new SMTP. - [x] DM: Connect Oakestra SMTP to the dashboard - [x] MS: open API Gateway PR to dev - [x] MS: Take a look at frontend code and workflows. Give comments - [x] NM: Set up frontend review meeting - [x] MS: Cluster FE registration and management components - [x] NM: Finalize private email for sending emails for Oakestra - [x] NM: Template for dashboard - [x] NM: Readme and Wiki for frontend - [x] NM: API description ## 📢 Discussions DM: We have to define some things. We need to define what template to use DM: Template: [2][3] ![2](https://hackmd.io/_uploads/SkIa9eZo3.png) DM: This one cots 17 euros, we need to understand if we can use it for an open soruce project. DM: Licenses: [4] NM: Wanna make sure that this does not restrict us from license perspective. NM: How would the redesign work? DM: Given the template, it would look like that. One dashboard for apps, and one for single app to improve the visualization. User management can go in the sidebar. MS: If we need to rearrange components do we keep the same idea for clusters list page? DM: Up to you, free to re-arrange and take inspiration from templates. NM: Found some other templates: [1][5][6] ![1](https://hackmd.io/_uploads/HJkt9gboh.png) ![5](https://hackmd.io/_uploads/HJO9cx-ih.png) ![6](https://hackmd.io/_uploads/Sycbilbi3.png) GB: Github code has upsides. They are hapy to refer your work in their project GB: Dashboard will be embedded in the new release and will be part of the compose file. MS: we can have minimum and maximum compose file -- lite and full. And you can config. MS: I added nginx config for service discovery, with the dashboard we have another. Do we keep them separate? GB: yup. NM: Dashboard review meeting can be after we have migrated dashbpard tonew template. MS: For next week I'll create an overview and required steps for frontend. MS: Two questions: 1) Marias component merged by Daniel? DM: Yes MS: Question 2) I can't see the cluster component in develop. Not there by default. DM: Yes, there is a clsuter component that is not used. It's commented out. MS: So I need to get the clsuter list running again. DM: Cluster list + cluster dashboard components are there. MS: I'll get this started again and discuss it next week. GB: PR regarding API gateway? MS: Only using API gateway for multi-cloud aspects. For now API gateways is for new components, e.g. multi-cloud broker. Old components are not on API gateway. GB: Lets do things slowly. Lets create a PR with API gateway and slowly add components to it. Outside the Oakestra, we only expose API gateways as entrypoint. We can then start thread on migration of frontend components in `maintainers`. MS: PR for `main`. I have 4 states. 1- cluster API from @Maria -- had to get it up and running but it is stale. 2 -- API gateway. 3 -- integrate JWT service (we cannot have multiple JWT tokens for front facing backend elements). 4 -- multi-cloud support (signing of request to multi-cloud component). DM: Also using JWT in `frontend` so we need to adjust it. MS: The JWT service exposes 3 endpoints, 1) create access token, 2) get pub key and 3) gen refresh token. To create a tokne we just send the attributes that will be part of the token so nothing to change there. GB: Dependency of PR? MS: Added one after another so they must be dependent. Need to check. GB: Please add this and then we can have further discussion. Add @giobart as reviewer. ## References [1] https://github.com/petter-ka/youpez-admin [2] https://www.einfosoft.com/templates/admin/spire/source/dark/#/dashboard/dashboard1 [3] https://themeforest.net/item/spire-angular-15-material-design-admin-dashboard-template/42879617 [4] https://themeforest.net/licenses/standard?license=regular&_ga=2.255225486.742674707.1690529751-325936803.1689751602 [5] https://github.com/akveo/ngx-admin [6] https://github.com/ng-matero/ng-matero ## 🛠️ TODOs - [ ] DM: Update dashboard readme and docs with latest build instructions - [ ] DM & MS: Check template and license for the template. Can we use it in opensource projects? - [ ] NM & DM: Oakestra private email support in dashboard - [ ] DM: description about multi sla deployment in documentation - [ ] DM: Create SMTP-component issue on oakestra repo. Describe the api that you need from front end to add a new SMTP. - [ ] DM: Connect Oakestra SMTP to the dashboard - [ ] GB: Test dashboard in oakestra compose file (will be discussed in `maintainers` as well) - [ ] NM: Send reminder email to HPI for intermittent VMs - [ ] NM: Set up frontend review meeting (after new dashboard) - [ ] MS: Take a look at frontend code and workflows. Give comments - [ ] MS: Cluster FE registration and management components - [ ] MS: open API Gateway PR to dev