noobaa-core
noobaa-core copied to clipboard
noobaa
when host is only used for gateway it's showing "No Access" label in green color
Environment info
- Version: 1.12
- Deployment: AZURE|ESX|AWS|GCLOUD|DEV|VBOX
- Customer: NAME
Actual behavior
- when host is only used for gateway it's showing "No Access" label in green color
Expected behavior
- When a node has only S3 gate the access should be "No access- Used as S3 gateway only"
Steps to reproduce
- deactivate storage and enable s3
Screenshots or Logs or other output that would be helpful
See screenshot in #3473, when entire host is deactivated we show "used as GW"
@nimrod-becker It should be according to the host statuses doc- "No Access- Used as S3 gate only" (it's currently not implemented as it should have been)
"No Storage Access" sounds like a problem, it's not a problem- it's what the user wanted
@shirimordechay Last week we decided that the accessibility line should be calculated from the aggregated storage mode. This mode does not have any information about the S3 gateway status because it encapsulate only the aggregated mode of the storage drives. So we cannot deduce the extra information (used as s3 gateway) from it.
@nb-ohad The status is according to the storage status - no access. we should be able to add the explanation line as we discussed and as it shows on the aggregation doc.
@nb-ohad I believe you had an issue with the suggested above, can you comment ?
@nb-ohad @nimrod-becker we need to decide which mode is missing. one option is to add a mode to storage nodes mode that reflects also the status of S3 nodes (e.g. DECOMMISSIONED_WITH_S3_ENABLED) I think it's a bad idea.
another option is to add a whole new accessibility_mode which is derived from storage\endpoint modes and returned by the BE.
another option is to allow some logic to happen in the FE. in this case, if the storage is disabled, the accessibility status will be determined by the endpoint mode