From: Alexandre DERUMIER <aderumier@odiso.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] Ceph 15.2.5 update?
Date: Sat, 3 Oct 2020 13:15:22 +0200 (CEST) [thread overview]
Message-ID: <521737835.3272203.1601723722503.JavaMail.zimbra@odiso.com> (raw)
In-Reply-To: <CAMnnoULkHyRbRnRdiqGrojAREfb5O1SO=CCyGGwGL1gDgEc3Pg@mail.gmail.com>
>>
>>Hmm - will that actually work?
>>
>>My understanding was that for Proxmox you had to use the Proxmox-specific
>>Ceph packages - just like there's a Proxmox-specific kernel etc.
Proxmox don't have any extra patch on ceph package, so you can use package from ceph official repo.
(Proxmox have his own repo, to be able to test ceph minor versions before releases, to avoid bug,.....)
----- Mail original -----
De: "Victor Hooi" <victorhooi@yahoo.com>
À: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Envoyé: Vendredi 2 Octobre 2020 14:22:37
Objet: Re: [pve-devel] Ceph 15.2.5 update?
Hi,
Hmm - will that actually work?
My understanding was that for Proxmox you had to use the Proxmox-specific
Ceph packages - just like there's a Proxmox-specific kernel etc.
Regards,
Victor
On Fri, Oct 2, 2020 at 10:08 PM Florent B <florent@coppint.com> wrote:
> Why don't use Ceph official repository ?
>
> https://download.ceph.com/debian-octopus/
>
> On 02/10/2020 05:43, Victor Hooi wrote:
> > Hi,
> >
> > The Ceph 15.2.5 update just came out. Yay! =)
> >
> > Do you know if there's any chance at all that the Octopus testing repos
> > could be updated to this?
> >
> > http://download.proxmox.com/debian/ceph-octopus/dists/buster/test/
> >
> > Thanks,
> > Victor
> > _______________________________________________
> > pve-devel mailing list
> > pve-devel@lists.proxmox.com
> > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> >
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2020-10-03 11:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMnnoUJ41C8L2TyCch0_KXGkKm57Fee8_D2Zy1XqiODKCuuTbg.ref@mail.gmail.com>
2020-10-02 3:43 ` Victor Hooi
[not found] ` <4e732c70-86a1-2d61-3efd-47f5e3a470a6@coppint.com>
2020-10-02 12:22 ` Victor Hooi
2020-10-03 11:15 ` Alexandre DERUMIER [this message]
2020-10-13 12:45 ` 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=521737835.3272203.1601723722503.JavaMail.zimbra@odiso.com \
--to=aderumier@odiso.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox