From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH offline-mirror] pom: add support for ceph squid 19.x release
Date: Thu, 27 Mar 2025 14:12:01 +0100 [thread overview]
Message-ID: <20250327131202.654181-1-c.heiss@proxmox.com> (raw)
Ceph Squid has been available through all of our Ceph repositories since
October 2024 [0], so it should be mirror-able through POM as well.
Reported in the forum [1].
[0] https://forum.proxmox.com/threads/ceph-19-2-squid-stable-release-and-ceph-17-2-quincy-soon-to-be-eol.156433/
[1] https://forum.proxmox.com/threads/ceph-squid-not-availbale-in-proxmox-offline-mirror.164230/
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
src/bin/proxmox-offline-mirror.rs | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/bin/proxmox-offline-mirror.rs b/src/bin/proxmox-offline-mirror.rs
index 2da13f5..78e88c9 100644
--- a/src/bin/proxmox-offline-mirror.rs
+++ b/src/bin/proxmox-offline-mirror.rs
@@ -255,12 +255,14 @@ fn action_add_mirror(config: &SectionConfigData) -> Result<Vec<MirrorConfig>, Er
Pacific,
Quincy,
Reef,
+ Squid,
}
let releases = match release {
Release::Bookworm => vec![
(CephRelease::Quincy, "Quincy (17.x)"),
(CephRelease::Reef, "Reef (18.x)"),
+ (CephRelease::Squid, "Squid (19.x)"),
],
Release::Bullseye => {
vec![
@@ -331,6 +333,7 @@ fn action_add_mirror(config: &SectionConfigData) -> Result<Vec<MirrorConfig>, Er
CephRelease::Pacific => "pacific",
CephRelease::Quincy => "quincy",
CephRelease::Reef => "reef",
+ CephRelease::Squid => "squid",
};
let url = format!("{base_url}-{ceph_release} {release} {components}");
--
2.48.1
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-03-27 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 13:12 Christoph Heiss [this message]
2025-03-27 15:33 ` [pve-devel] applied: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250327131202.654181-1-c.heiss@proxmox.com \
--to=c.heiss@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.