Have just noticed their is packages available for 14.2.4.. I know with the whole 14.2.3 release and the notes not going out to a good day or so later.. but this is not long after the 14.2.3 release..? Was this release even meant to have come out? Makes it difficult for people installing a new node if they can't reply on the current "stable" packages that apt/yum will give them.
On 17.09.2019 06:54, Ashley Merrick wrote:
Have just noticed their is packages available for 14.2.4..
I know with the whole 14.2.3 release and the notes not going out to a good day or so later.. but this is not long after the 14.2.3 release..?
Was this release even meant to have come out? Makes it difficult for people installing a new node if they can't reply on the current "stable" packages that apt/yum will give them.
Never install packages until there is an announcement. IIRC developers have asked if anyone have experience with running repos that could assist in improving the rollout of releases since this have been a recurring issue. If you need to do installs all the time, and can not postpone until the repo settle. Consider rsyncing the repo after a release, and use that for installs. kind regards Ronny
On 9/17/19 8:46 AM, Ronny Aasen wrote:
Never install packages until there is an announcement.
which defeats the purpose of having the repositories in the first place.
IIRC developers have asked if anyone have experience with running repos that could assist in improving the rollout of releases since this have been a recurring issue.
I'm happy to help (daniel@debian.org, dnl on freenode). Regards, Daniel
Hi! Fine! Maybe you know what a new user should do? Which does not yet have a local copy of the repository, and is now trying to install the latest version? ----- Original Message -----
From: "Ronny Aasen" <ronny+ceph-users@aasen.cx> To: ceph-users@ceph.io Sent: Tuesday, 17 September, 2019 09:46:03 Subject: [ceph-users] Re: 14.2.4 Packages Avaliable
On 17.09.2019 06:54, Ashley Merrick wrote:
Have just noticed their is packages available for 14.2.4..
I know with the whole 14.2.3 release and the notes not going out to a good day or so later.. but this is not long after the 14.2.3 release..?
Was this release even meant to have come out? Makes it difficult for people installing a new node if they can't reply on the current "stable" packages that apt/yum will give them.
Never install packages until there is an announcement.
IIRC developers have asked if anyone have experience with running repos that could assist in improving the rollout of releases since this have been a recurring issue.
If you need to do installs all the time, and can not postpone until the repo settle. Consider rsyncing the repo after a release, and use that for installs.
kind regards Ronny
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
Depends on the OS you are using. Version pinning is the search keyword you are looking for Hi! Fine! Maybe you know what a new user should do? Which does not yet have a local copy of the repository, and is now trying to install the latest version? ----- Original Message -----
From: "Ronny Aasen" <ronny+ceph-users@aasen.cx> To: ceph-users@ceph.io Sent: Tuesday, 17 September, 2019 09:46:03 Subject: [ceph-users] Re: 14.2.4 Packages Avaliable
On 17.09.2019 06:54, Ashley Merrick wrote:
Have just noticed their is packages available for 14.2.4..
I know with the whole 14.2.3 release and the notes not going out to a good day or so later.. but this is not long after the 14.2.3 release..?
Was this release even meant to have come out? Makes it difficult for people installing a new node if they can't reply on the current "stable" packages that apt/yum will give them.
Never install packages until there is an announcement.
IIRC developers have asked if anyone have experience with running repos that could assist in improving the rollout of releases since this have been a recurring issue.
If you need to do installs all the time, and can not postpone until the repo settle. Consider rsyncing the repo after a release, and use that for installs.
kind regards Ronny
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
Hi! No. I looking information on https://ceph.io/ why I should not install version 14.2.4, although it is in the repository and how it differs from 14.2.3 ----- Original Message -----
From: "Bastiaan Visser" <bvisser@flexyz.com> To: ceph-users@ceph.io Sent: Tuesday, 17 September, 2019 10:52:54 Subject: [ceph-users] Re: 14.2.4 Packages Avaliable
Depends on the OS you are using. Version pinning is the search keyword you are looking for
Hi!
Fine! Maybe you know what a new user should do? Which does not yet have a local copy of the repository, and is now trying to install the latest version?
----- Original Message -----
From: "Ronny Aasen" <ronny+ceph-users@aasen.cx> To: ceph-users@ceph.io Sent: Tuesday, 17 September, 2019 09:46:03 Subject: [ceph-users] Re: 14.2.4 Packages Avaliable
On 17.09.2019 06:54, Ashley Merrick wrote:
Have just noticed their is packages available for 14.2.4..
I know with the whole 14.2.3 release and the notes not going out to a good day or so later.. but this is not long after the 14.2.3 release..?
Was this release even meant to have come out? Makes it difficult for people installing a new node if they can't reply on the current "stable" packages that apt/yum will give them.
Never install packages until there is an announcement.
IIRC developers have asked if anyone have experience with running repos that could assist in improving the rollout of releases since this have been a recurring issue.
If you need to do installs all the time, and can not postpone until the repo settle. Consider rsyncing the repo after a release, and use that for installs.
kind regards Ronny
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
On 9/17/19 8:46 AM, Ronny Aasen wrote:
On 17.09.2019 06:54, Ashley Merrick wrote:
Have just noticed their is packages available for 14.2.4..
I know with the whole 14.2.3 release and the notes not going out to a good day or so later.. but this is not long after the 14.2.3 release..?
Was this release even meant to have come out? Makes it difficult for people installing a new node if they can't reply on the current "stable" packages that apt/yum will give them.
Never install packages until there is an announcement.
But if a user runs "yum update" or "apt upgrade" one should be able to trust download.ceph.com We can't assume that every user does version pinning.
IIRC developers have asked if anyone have experience with running repos that could assist in improving the rollout of releases since this have been a recurring issue.
That would be great! But it seems right now that packages are pushed, but the Release Notes haven't been generated. This happened a couple of times now. Wido
If you need to do installs all the time, and can not postpone until the repo settle. Consider rsyncing the repo after a release, and use that for installs.
kind regards Ronny
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
Hello,
Have just noticed their is packages available for 14.2.4..
I know with the whole 14.2.3 release and the notes not going out to a good day or so later.. but this is not long after the 14.2.3 release..?
Was this release even meant to have come out? Makes it difficult for people installing a new node if they can't reply on the current "stable" packages that apt/yum will give them.
Never install packages until there is an announcement.
IIRC developers have asked if anyone have experience with running repos that could assist in improving the rollout of releases since this have been a recurring issue.
If you need to do installs all the time, and can not postpone until the repo settle. Consider rsyncing the repo after a release, and use that for installs.
That does not make sense. If a package is available on the repo and can be installed or update directly with apt or yum, it has to be the final release package, any other statement must be flagged as RC or beta. Why don't you add RC flags on this package if it's not ready to publish? I plan to install a new cluster with ceph-ansible, I don't have to take care of the release number as soon as it's the latest package available on the official stable repo. Even on a short period, an « almost ready but not completely full tested » packages can really have an impact on production servers, especially if not announce previously. Best regards, -- Yoann Moulin EPFL IC-IT
14.2.4 is a bug-fix release for https://tracker.ceph.com/issues/41660 There are no other changes beside this fix -- Paul Emmerich Looking for help with your Ceph cluster? Contact us at https://croit.io croit GmbH Freseniusstr. 31h 81247 München www.croit.io Tel: +49 89 1896585 90 On Tue, Sep 17, 2019 at 10:34 AM Yoann Moulin <yoann.moulin@epfl.ch> wrote:
Hello,
Have just noticed their is packages available for 14.2.4..
I know with the whole 14.2.3 release and the notes not going out to a good day or so later.. but this is not long after the 14.2.3 release..?
Was this release even meant to have come out? Makes it difficult for people installing a new node if they can't reply on the current "stable" packages that apt/yum will give them.
Never install packages until there is an announcement.
IIRC developers have asked if anyone have experience with running repos that could assist in improving the rollout of releases since this have been a recurring issue.
If you need to do installs all the time, and can not postpone until the repo settle. Consider rsyncing the repo after a release, and use that for installs.
That does not make sense. If a package is available on the repo and can be installed or update directly with apt or yum, it has to be the final release package, any other statement must be flagged as RC or beta. Why don't you add RC flags on this package if it's not ready to publish?
I plan to install a new cluster with ceph-ansible, I don't have to take care of the release number as soon as it's the latest package available on the official stable repo. Even on a short period, an « almost ready but not completely full tested » packages can really have an impact on production servers, especially if not announce previously.
Best regards,
-- Yoann Moulin EPFL IC-IT _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
Hello,
Have just noticed their is packages available for 14.2.4..
I know with the whole 14.2.3 release and the notes not going out to a good day or so later.. but this is not long after the 14.2.3 release..?
Was this release even meant to have come out? Makes it difficult for people installing a new node if they can't reply on the current "stable" packages that apt/yum will give them.
Never install packages until there is an announcement.
IIRC developers have asked if anyone have experience with running repos that could assist in improving the rollout of releases since this have been a recurring issue.
If you need to do installs all the time, and can not postpone until the repo settle. Consider rsyncing the repo after a release, and use that for installs.
That does not make sense. If a package is available on the repo and can be installed or update directly with apt or yum, it has to be the final release package, any other statement must be flagged as RC or beta. Why don't you add RC flags on this package if it's not ready to publish?
I plan to install a new cluster with ceph-ansible, I don't have to take care of the release number as soon as it's the latest package available on the official stable repo. Even on a short period, an « almost ready but not completely full tested » packages can really have an impact on production servers, especially if not announce previously.
14.2.4 is a bug-fix release for https://tracker.ceph.com/issues/41660
There are no other changes beside this fix
My reaction was not on this specific release but with this sentence : « Never install packages until there is an announcement. » And also with this one : « If you need to do installs all the time, and can not postpone until the repo settle. Consider rsyncing the repo after a release, and use that for installs. » This sound crazy to me. Best regards, -- Yoann Moulin EPFL IC-IT
Den tis 17 sep. 2019 kl 12:52 skrev Yoann Moulin <yoann.moulin@epfl.ch>:
Hello,
Never install packages until there is an announcement.
My reaction was not on this specific release but with this sentence : « Never install packages until there is an announcement. » And also with this one : « If you need to do installs all the time, and can not postpone until the repo settle. Consider rsyncing the repo after a release, and use that for installs. » This sound crazy to me.
I would have to agree with this. If these statements are true: 1) devs say: don't install unless there is an announcement out 2) devs have previously dropped new releases before posting the announcement and told people it was a mistake to "yum upgrade"/"apt upgrade" before announcement then the solution seems very simple, do NOT populate the repos with packages that your users shouldn't install until release notes are out. I am well aware of that 100s of things around packaging and testing a release is hard, times the amount of platforms and arches you support, but to the untrained eye, not pushing packages out seems like quite a binary thing. Either you press whatever button there is that pushes the files out, or you don't press it. If there is a reason for people to not run packages until a certain condition is true, then don't press that hypothetical button until you get convinced that the condition is. Among all other things that are hard about releases, that can't be the worst? -- May the most significant bit of your life be positive.
Hi, Yesterday I completed the 14.2.4 release by jumping a few procedures that should've been followed, mainly communicating with the release manager and the team involved in sending out the release announcement. There was a sense of urgency since the 14.2.3 release introduced issues with the ceph-volume tool which breaks deployment tools that capture stderr/stdout (see https://tracker.ceph.com/issues/41660) The release process started on Friday (!) and finished late yesterday. I'm following up with the release manager to get the proper notes out, like I mentioned he was unaware of the ongoing release (my fault). Let me know if you have any questions (or complaints!) while we try to get this sorted out. -Alfredo On Tue, Sep 17, 2019 at 7:49 AM Janne Johansson <icepic.dz@gmail.com> wrote:
Den tis 17 sep. 2019 kl 12:52 skrev Yoann Moulin <yoann.moulin@epfl.ch>:
Hello,
Never install packages until there is an announcement.
My reaction was not on this specific release but with this sentence : « Never install packages until there is an announcement. » And also with this one : « If you need to do installs all the time, and can not postpone until the repo settle. Consider rsyncing the repo after a release, and use that for installs. » This sound crazy to me.
I would have to agree with this. If these statements are true: 1) devs say: don't install unless there is an announcement out 2) devs have previously dropped new releases before posting the announcement and told people it was a mistake to "yum upgrade"/"apt upgrade" before announcement
then the solution seems very simple, do NOT populate the repos with packages that your users shouldn't install until release notes are out.
I am well aware of that 100s of things around packaging and testing a release is hard, times the amount of platforms and arches you support, but to the untrained eye, not pushing packages out seems like quite a binary thing. Either you press whatever button there is that pushes the files out, or you don't press it.
If there is a reason for people to not run packages until a certain condition is true, then don't press that hypothetical button until you get convinced that the condition is.
Among all other things that are hard about releases, that can't be the worst?
-- May the most significant bit of your life be positive.
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
On 9/17/19 6:54 AM, Ashley Merrick wrote:
Have just noticed their is packages available for 14.2.4..
I know with the whole 14.2.3 release and the notes not going out to a good day or so later.. but this is not long after the 14.2.3 release..?
It seems that the release is intentional. See this commit: https://github.com/ceph/ceph/commit/cf78989688038a55b029e2535ae9fe58479fb369 It's from Friday the 13th (who releases on a Friday the 13th ;-) ?) September. Wido
Was this release even meant to have come out? Makes it difficult for people installing a new node if they can't reply on the current "stable" packages that apt/yum will give them.
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
participants (10)
-
Alfredo Deza
-
Ashley Merrick
-
Bastiaan Visser
-
Daniel Baumann
-
Fyodor Ustinov
-
Janne Johansson
-
Paul Emmerich
-
Ronny Aasen
-
Wido den Hollander
-
Yoann Moulin