-
Notifications
You must be signed in to change notification settings - Fork 48
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
microcloud/cmd/microcloud: Use quincy client package
The OSD API was changed with reef, but there is a manual patch that makes it compatible with the quincy Go client. https://github.com/canonical/microceph/blob/2bddc9d6280d903dcb52a993833e991873565550/microceph/api/disks.go#L163-L172 So we can use that instead to support both reef and quincy. Signed-off-by: Max Asnaashari <[email protected]>
- Loading branch information
Showing
7 changed files
with
10 additions
and
28 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -46,12 +46,8 @@ update-gomod: | |
# Grab MicroOVN from the corresponding support branch. | ||
go get github.com/canonical/microovn/[email protected] | ||
|
||
# There is a reef branch, but its microcluster dependency has breaking changes. | ||
# Also, the quincy branch has an outdated client for the MicroCeph API offered with reef/stable. | ||
# | ||
# As such, we have to grab the latest commit which uses a compatible microcluster, | ||
# but recent enough to also account for reef's breaking API changes. | ||
go get github.com/canonical/microceph/[email protected] | ||
# There is a reef branch, but its microcluster dependency has breaking changes, so use quincy instead. | ||
go get github.com/canonical/microceph/microceph@quincy | ||
|
||
# Branches named `vN` where N is a number are reserved by go for module versions, | ||
# So we are forced to grab the corresponding commit hash for the `v1` branch instead. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters