catalyst-cloud / catalystcloud-docs Goto Github PK

https://docs.openstack.org/neutron/rocky/admin/vpnaas-scenario.html#using-vpnaas-with-endpoint-group-recommended

https://docs.catalystcloud.io/identity-access-management/roles.html has multiple "click here" links that expose additional data.
These don't work for me at all in Chrome Version 83.0.4103.116 (Official Build) (64-bit) on MacOS.
They do work for me in Firefox.
IMO, they should be removed as "click here" is not useful for accessibility; just show the tables in line.

They aren't necessary, so maybe just use [ instead of [[?

I think we should add the python-octavia to the CLI set up instructions (getting-started/cli.html#command-line-interface-cli) and remove the section that talks about it from the load balancer service.

Despite this being a valuable feature, we don't explain or highlight the volume snapshotting feature.

We should explain how to perform this action on the dashboard, the CLI, and best practices for using snapshots. For example, that they are not a backup, but rather a point in time.

The documentation for setting acls for swift is lacking some crucial details. OS_STORAGE_URL needs to either be set in the openstack rc file or set manually by users.

EXPORT OS_STORAGE_URL=${SWIFT_API}/v1/AUTH_${PROJECT_UUID}/ is the right format for this. It's possible this can be done here or in the openstack-rc file.

The documentation on adding a network is out of date, and should include helpful default suggestions for things like the allocation pools and network address, for those users who know very little about networking.

As per earlier discussion, the docs should have info on at least:

• Creating buckets
• Deleting buckets
• Creating objects
• Downloading objects
• Deleting objects

... with all of the control mechanisms:

• Dashboad
• CLI
• Swift API
• S3 API

It would be nice to list all availability zones on https://docs.catalystcloud.nz/kubernetes/storage.html for ease of use. I have seen several cases that user tried to create a storage class based on 'nz_wlg_2' instead of the correct 'NZ-WLG-2'. Cheers.

It's not clear what the licensing of this repository is. We're interested in a fork, but would in turn be willing to contribute back documentation that we add locally.