canonical / canonical/microcloud
Ceph network selection should use a table
- Dominant language
- Go
- Stars
- 532
- Forks
- 83
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 36
Description
The selection of the Ceph public and internal (cluster) networks should also make use of tables when running the interactive deployment to be consistent with the selection of MicroCloud's internal address and the OVN underlay configuration which both are using a table.
The difference is that in case of Ceph instead of just the address an entire network has to be selected. The networks can be derived from the interface and displayed accordingly in the respective table.
Ultimately this allows and admin to select a network based on what is present on the system.
Contributor guide
Research direction
Start in the interactive deployment flow that selects MicroCloud's internal address and the OVN underlay configuration, then trace the corresponding Ceph public and internal network selection. Use the available interfaces to derive and display whole networks in tables rather than only addresses. Done means an administrator can select both Ceph networks from networks present on the system, consistently with the other interactive selections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100