Re: SRU Minor Release Exception for Ceph
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Martin On 25/02/13 16:02, Martin Pitt wrote: LTS release updates are made after some time has passed (to allow testing) or if a particularly critical bug needs to get out to users. Updates to LTS releases are numbered with a minor point release Argonaut: 0.48.1, 0.48.2, (0.48.3 released but pending SRU) Bobtail: 0.56, 0.56.1, 0.56.2 So quantal ships the argonaut series, raring the bobtail series. To which Ubuntu releases does this MRE apply to? Ubuntu 12.04 LTS ships 0.41 -- is that also an upstream supported release, or do you propose to update precise to 0.48? (That would then not be a microrelease any more). 0.41 is not a LTS release and I don't intend for the MRE to cover Ceph prior to 12.10 for this reason as we would just backport fixes as required for the version in 12.04. For information the Ubuntu Cloud Archive provides more recent versions of Ceph on 12.04 alongside OpenStack releases. Proposed SRU Approach - - SRU updates for Ceph in Ubuntu will be aligned to the associated LTS release of Ceph: 12.10 - Argonaut 0.48.x 13.04 - Bobtail 0.56.x This seems to indicate that you don't plan on updating 12.04 LTS. That's fine, I'd just like some confirmation as Ubuntu 12.04 seems to be a much more popular server target than quantal or even raring at this moment? Correct - see my note above re backports via Ubuntu Cloud Archive. Assuming that you really only want to update to the new upstream microreleases, +1 from me for a provisional MRE (i. e. doing a test run with an SRU to a new upstream microrelease). Great - thanks! Cheers James - -- James Page Ubuntu Core Developer Debian Maintainer james.p...@ubuntu.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBCAAGBQJRLopXAAoJEL/srsug59jDSqIP/RHQg4PBvTNBh8iv66M1H5Eh v6Vinvb3pEroUzZ3pEILEGXplmHnTmhoC2SLIpJVeD13ZoThcRvImNKMNFqUBBDr 2KYjJOncRFA8wuKSOvO2QwMCLo18MTegJ6GH3ewUiVphWoK34RMLbX+dkMbc+pTg jIfqX+4NAtY8WFhu60RXfgbfsnnV85O/jXTy2A6lYD0x47lisqAJdjnjDu0h4zrM blrTSSYzgdSdoRbnixt7qImGwDTuvW8Ggv9ZDToA88rGjYNLGS8fftIFoTES9pcS sJ5E6BTNkG7s8iv/LyysaNvBm5RXNlLowQTKknZDxUl/YhHFKUnPEZdmY+06l/jk pJhUNpBj0K0RsxIMAy8RP6YAym7DyFgt0EBw/FGb+1JMgcWXE5mvsO2slRZmLDq7 iQMhljy76ITYRgaTs65rTLajzwKsKaqiZBt7xmMjN1jBECYYJKRJ0Pt72MUO5KGy wMuoLz0+beit5EfU1IBy94I5iwFE9TMYDjNHwnzHbe4JqFfS5CAyBEUqV3DZgtgU V52F2aIHUdKAN7uu0gZ/mH1lWUaJsVJh+vghk0nlj4P4V5s81RcZVZfxpO1X+yT+ f64hNfRWZLAX6on1+77KFOOfb8hV2OxpSrHTJHvU5CTgRH4dTDOMvYUxZxkDjJDm u66m3zMmXVTafu410xBv =vUHD -END PGP SIGNATURE- -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
Re: SRU Minor Release Exception for Ceph
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Soren I discussed your questions re what LTS means with Sage (upstream project founder). Exactly how long 'long term' is is still being defined based on user/distro/other project requirements but we did discuss the following... On 19/02/13 13:46, Soren Hansen wrote: Background - -- Ceph was included in Ubuntu main during the 12.04 release cycle; since then upstream Ceph have started maintaining LTS releases of Ceph; Quantal shipped with the 'argonaut' LTS release and Raring will ship the 'bobtail' LTS release. What does LTS mean for Ceph? How long do they expect to support it for? Each LTS release goes through a period of aggressive bug fix backporting; this does tail off BUT if users do encounter a bug then it would still be addressed upstream given sufficient criticality. Are the bobtail and argonaut releases indicative of the frequency of LTS releases? In other words, can we reasoably expect to have a fresh LTS in each Ubuntu release? Ceph are moving to a 3 month release cadence - not every Ceph release will be an LTS release but the LTS releases are expected to line up with distro releases. If not, have you given any thought to how you'll handle the situation where our release cycle doesn't line up well with upstream's LTS releases? If this does happen we would just stick with the most recent LTS release available. Ubuntu Ceph Testing - --- [...] In addition, we are currently setting up regular testing of Ceph 'standalone' in multi-node configurations to support more in-depth testing of ceph itself. This will include basic smoke testing of key components to start with and may expand to include executing upstream regression tests on the packages we publish/propose for inclusion in the Ubuntu archive. I think this is a must-have. If upstream already has a good test suite, we should as far as possible be using that in our testing as well. Agreed - I will work on this. Would basic smoke testing be sufficient for a provisional MRE? Cheers James - -- James Page Ubuntu Core Developer Debian Maintainer james.p...@ubuntu.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBCAAGBQJRLouIAAoJEL/srsug59jDLXoP/iljtENm7Z2uZKx/IJNT5aa3 3KeKOBHnDprkd+N7zKfgQDyVrWwHeMX9etKCJy2yufW+Bb9dD9DPjXjPwZDpOOMK zgtBU9Q/jK1i4RPwYAoOv3YljInSsQE2bsSWfRk7mEW1BOqQaqNwKuN4uqpIxFg0 UHasRxE0jr8tWDCANkAVQU2vzH7LQvcS3HTQhwkjjZGPLl9MpN0RY271Y1eMB7Q1 93hFFqYRDzxRdS1BUIzrTaapMYq0QB08u2Oe0UsGHkocAwbevWQjG86ZjrhEA4Y/ u2DvVtUmBZTPfA22vZdbxOhRdvKwbRq3gRTl5o0BgY5YaacQH0aoCxwA8tfS/rOI eeur21uCXoRc1JD0uHfsSd3b+ADWRFASdp8SK4SpP2hZTvqlP5iow9ex1BKDrZh5 5cAPq0bJWiJqL/8LiPIZiNd6ccrgKR+zFR5JpW37f1sT/k1PS4jUebeUGsA9YhsY nE8y2iDl6E47bHzKIjquQNcdYkP0APNnskUeWr09jZOGriyHOmsezuAK6CVHmTvA 95oWTZVkcZg1HJDQATJuTBsv72aHKiBeL8IRGggiVQ9Do8Zcuj5Uqyzt2En0dTOX Gzx91dAyTPp3VuY3Gk4qHhi1bk5gOpBbXnh0/AhBD2q/vLmheU2SS+cJaAnjGnFC 4/V/b30rtJXK6nNyQm4Q =pRuh -END PGP SIGNATURE- -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
Re: SRU Minor Release Exception for Ceph
2013/2/27 James Page james.p...@ubuntu.com: If not, have you given any thought to how you'll handle the situation where our release cycle doesn't line up well with upstream's LTS releases? If this does happen we would just stick with the most recent LTS release available. Ok, works for me. Ubuntu Ceph Testing - --- In addition, we are currently setting up regular testing of Ceph 'standalone' in multi-node configurations to support more in-depth testing of ceph itself. This will include basic smoke testing of key components to start with and may expand to include executing upstream regression tests on the packages we publish/propose for inclusion in the Ubuntu archive. I think this is a must-have. If upstream already has a good test suite, we should as far as possible be using that in our testing as well. Agreed - I will work on this. Would basic smoke testing be sufficient for a provisional MRE? If doing the whole thing would cause a significant delay, then yes, basic smoke testing is ok, as long as there's a genuine effort afterwards to get the full test suite added. -- Soren Hansen | http://linux2go.dk/ Senior Software Engineer | http://www.cisco.com/ Ubuntu Developer | http://www.ubuntu.com/ OpenStack Developer | http://www.openstack.org/ -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
Re: SRU Minor Release Exception for Ceph
Hello James, James Page [2013-02-08 14:47 +]: I'd like to apply for a Minor Release Exception for the Ceph package. Thanks for the detailled testing plan. This seems quite appropriate to me in general, I just have some further questions: LTS release updates are made after some time has passed (to allow testing) or if a particularly critical bug needs to get out to users. Updates to LTS releases are numbered with a minor point release Argonaut: 0.48.1, 0.48.2, (0.48.3 released but pending SRU) Bobtail: 0.56, 0.56.1, 0.56.2 So quantal ships the argonaut series, raring the bobtail series. To which Ubuntu releases does this MRE apply to? Ubuntu 12.04 LTS ships 0.41 -- is that also an upstream supported release, or do you propose to update precise to 0.48? (That would then not be a microrelease any more). Proposed SRU Approach - - SRU updates for Ceph in Ubuntu will be aligned to the associated LTS release of Ceph: 12.10 - Argonaut 0.48.x 13.04 - Bobtail 0.56.x This seems to indicate that you don't plan on updating 12.04 LTS. That's fine, I'd just like some confirmation as Ubuntu 12.04 seems to be a much more popular server target than quantal or even raring at this moment? Assuming that you really only want to update to the new upstream microreleases, +1 from me for a provisional MRE (i. e. doing a test run with an SRU to a new upstream microrelease). Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
Re: SRU Minor Release Exception for Ceph
2013/2/8 James Page james.p...@ubuntu.com: Background - -- Ceph was included in Ubuntu main during the 12.04 release cycle; since then upstream Ceph have started maintaining LTS releases of Ceph; Quantal shipped with the 'argonaut' LTS release and Raring will ship the 'bobtail' LTS release. What does LTS mean for Ceph? How long do they expect to support it for? Are the bobtail and argonaut releases indicative of the frequency of LTS releases? In other words, can we reasoably expect to have a fresh LTS in each Ubuntu release? If not, have you given any thought to how you'll handle the situation where our release cycle doesn't line up well with upstream's LTS releases? Ubuntu Ceph Testing - --- [...] In addition, we are currently setting up regular testing of Ceph 'standalone' in multi-node configurations to support more in-depth testing of ceph itself. This will include basic smoke testing of key components to start with and may expand to include executing upstream regression tests on the packages we publish/propose for inclusion in the Ubuntu archive. I think this is a must-have. If upstream already has a good test suite, we should as far as possible be using that in our testing as well. -- Soren Hansen | http://linux2go.dk/ Senior Software Engineer | http://www.cisco.com/ Ubuntu Developer | http://www.ubuntu.com/ OpenStack Developer | http://www.openstack.org/ -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
SRU Minor Release Exception for Ceph
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Technical Board I'd like to apply for a Minor Release Exception for the Ceph package. Background - -- Ceph was included in Ubuntu main during the 12.04 release cycle; since then upstream Ceph have started maintaining LTS releases of Ceph; Quantal shipped with the 'argonaut' LTS release and Raring will ship the 'bobtail' LTS release. Ceph provides massively scalable object and block storage on commodity hardware; it integrates closely with OpenStack (Ceph forms part of the regular CI testing we do of OpenStack) and is a key part of the High Availability reference architecture for Ubuntu Openstack deployments. Having a MRE for Ceph will ensure that users of Ceph receive timely critical updates to this software. Upstream Change and Release Policy - -- Upstream have a policy for accepting changes into the LTS release branches which includes: - Back-porting of any critical bug fixes (crashes, data loss, etc) - Minor usability items that are low risk Commits are peer reviewed as part of the normal development process and are signed to signify both the developer and review (see [0] for examples). LTS release updates are made after some time has passed (to allow testing) or if a particularly critical bug needs to get out to users. Updates to LTS releases are numbered with a minor point release Argonaut: 0.48.1, 0.48.2, (0.48.3 released but pending SRU) Bobtail: 0.56, 0.56.1, 0.56.2 Upstream Regression Testing - --- The upstream Ceph regression suite is a mix of comprehensive functional tests (API coverage, etc.), stress workloads (tools like dbench, iozone on fuse, kernel cephfs, kernel rbd, inside qemu; rados bench, rest best, etc.), and stress workloads + cluster thrashing (random restarts of server daemons and data rebalancing). The full set is defined at [1]. The QA suite is run against the Argonaut/Bobtail branches nightly to hunt for low-frequency problems. Everything should be tested regularly, and all but the most recent patches have been tested over and extended period of time. Results are published via email to the ceph-commit mailing list (see [2] for examples). Ubuntu Ceph Testing - --- As previously mentioned, Ceph forms part of the OpenStack testing that we do on a per commit basis of core OpenStack projects during the Ubuntu/OpenStack development cycle; Ceph is also tested alongside OpenStack SRU's for Quantal/Folsom and for updates into the Ubuntu Cloud Archive for Precise/Folsom. In addition, we are currently setting up regular testing of Ceph 'standalone' in multi-node configurations to support more in-depth testing of ceph itself. This will include basic smoke testing of key components to start with and may expand to include executing upstream regression tests on the packages we publish/propose for inclusion in the Ubuntu archive. Proposed SRU Approach - - SRU updates for Ceph in Ubuntu will be aligned to the associated LTS release of Ceph: 12.10 - Argonaut 0.48.x 13.04 - Bobtail 0.56.x Ubuntu will only use the released version of updates and will not pull directly from the upstream VCS. Proposed packages will be prepared, uploaded and tested both standalone and in-conjunction with OpenStack (following the methodology detail above) as part of the standard SRU verification process for packages with MRE's. I hope this information gives the technical board sufficient confidence that Ceph is worthy of a minor release exception for SRU activity. Thanks James [0] http://github.com/ceph/ceph/commits/stable [1] http://github.com/ceph/ceph-qa-suite [2] http://lists.ceph.newdream.net/pipermail/ceph-commit-ceph.newdream.net/2013-February/thread.html - -- James Page Ubuntu Core Developer Debian Maintainer james.p...@ubuntu.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBCAAGBQJRFQ/2AAoJEL/srsug59jDy9wP/3yZyPVCFoHhVsYEtT/wrOcN 3gG3nb8m75oCMdNda1LrHpJ4Wz2eWqRVYuOseEe7RcE0wGwhEl379ez/lqJD9kbL eMB6cDMAp2dbK1g1pBci62NvEiKoFOmHxopseY7PSMfrFLn4RFO+r+2PdXPNorg8 QsjxjvjS2VhU+7paQFYzspTs61Uj1qEC8o+8JQE97C+DLZJ5A3bi2uBJoN/bk9Tl i3Tx+KWRVYxsYVrHFSccffLDi9RxqwGQj1ZwMAhvGfI7de6YLH1lnavyQQUCtqzw F995JGzKkgFxeEjmCzKvqvUAMko71SQzBxNtLMW1HRdOegFHwSBS//dWQzO+EizE BgVTW6HYuK6j483rtTRy0F8r0du+6FJnFzymREkg5Oog/eX1eAdHlrJwRMf8AwyZ Ai0JiyOeHnqpGazV8N14uh5/sYsI6url569GmCBOXpzwc6C2pVGsCjGHzTdh5rtR Mjojnx9eiJjIECVPkiffA0uld+c4UvaaSjvpLdvrXGaVFkHb5gytfpFPK6U9J/71 6Zud4w0U8maT1uNAlNXieL43x9FKBAoedjY5opMDG+Y0LhFvJIRarZdquFbKFqk0 iumZBP6297fycHq4/71IZ0/iqYPeB/X8vL2OsMbONm0fyQ9jtH50GtFgq0kCC0QQ 1sbw/VHRtmSL6AL05uxP =V2VS -END PGP SIGNATURE- -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
