On Wed, Sep 25, 2019 at 1:56 PM Sasha Litvak
wrote:
>
> I guess for me the more crucial questions should be answered:
>
> 1. How can a busted release be taken out of repos (some metadata
> update I hope)?
It's hard to define the word "busted" in a way that satisfies everyone.
For example, in
I guess for me the more crucial questions should be answered:
1. How can a busted release be taken out of repos (some metadata update I
hope)?
2. Can some fix(es) be added into a test release so they can be accessed
by community and tested / used before next general release is avaialble.
I was
Den tis 24 sep. 2019 kl 23:35 skrev David Turner :
>
> At work I haven't had a problem with which version of Ceph is being
> installed because we always have local mirrors of the repo that we only
> update with the upstream repos when we're ready to test a new version in
> our QA environments long
IRT a testing/cutting edge repo, the non-LTS versions of Ceph have been
removed because very few people ever used them and tested them. The
majority of people that would be using the testing repo would be people
needing a bug fix ASAP. Very few people would actually use this regularly
and its effec
On Tue, Sep 17, 2019 at 8:03 AM Sasha Litvak
wrote:
>
> * I am bothered with a quality of the releases of a very complex system that
> can bring down a whole house and keep it down for a while. While I wish the
> QA would be perfect, I wonder if it would be practical to release new
> packages to
Hello,
> I still think this is something we should consider as users still
> experience problems:
>
> * Impossible to 'pin' to a version. User installs 14.2.0 and 4 months
> later they add other nodes but version moved to 14.2.2
> * Impossible to use a version that is not what the latest is (e.g.
I have been affected by few issues mentioned by Alfredo.
* Version Pinning: Had to install several debs of specific version to be
able to pull dependencies of the correct version. I believe that other
projects resolving it by creating a virtual package that pulls all of the
proper dependencies i
The worst part about the official repository is that it lacks Debian
packages
Also of course it would be very convenient to be able to install any
version from the repos, not just the latest one. It's certainly possible
with debian repos...
___
ceph
Den tis 17 sep. 2019 kl 15:15 skrev Alfredo Deza :
> Reviving this old thread.
> * When a release is underway, the repository breaks because syncing
> packages takes hours. The operation is not atomic.
>
Couldn't they be almost atomic?
I believe both "yum" and "apt" would only consider rpms/debs
On 17/09/2019 14:14, Alfredo Deza wrote:
> * Impossible to 'pin' to a version. User installs 14.2.0 and 4 months
> later they add other nodes but version moved to 14.2.2
I dynamically generate a pin for the ceph .deb files in ansible using
the tasks below. IIRC the ceph-deploy package doesn't fol
"Alfredo Deza" writes:
> Reviving this old thread.
>
> I still think this is something we should consider as users still
> experience problems:
>
> * Impossible to 'pin' to a version. User installs 14.2.0 and 4 months
> later they add other nodes but version moved to 14.2.2
> * Impossible to use
er 2019 15:15
To: ceph-maintain...@ceph.com; ceph-users; ceph-devel
Subject: [ceph-users] Re: download.ceph.com repository changes
Reviving this old thread.
I still think this is something we should consider as users still
experience problems:
* Impossible to 'pin' to a version. User i
Reviving this old thread.
I still think this is something we should consider as users still
experience problems:
* Impossible to 'pin' to a version. User installs 14.2.0 and 4 months
later they add other nodes but version moved to 14.2.2
* Impossible to use a version that is not what the latest i
13 matches
Mail list logo
