Edison, The old S3 and Swift-backed secondary storage can still be enabled (via global options) and configured along side the new object store feature. Is there a reason why they are still present? I would have expected the code to have been removed.
The second question is how users utilizing those features will be migrated to the new object storage approach. Thanks, -John On Jul 25, 2013, at 5:09 PM, Edison Su <edison...@citrix.com> wrote: > > >> -----Original Message----- >> From: John Burwell [mailto:jburw...@basho.com] >> Sent: Thursday, July 25, 2013 2:06 PM >> To: dev@cloudstack.apache.org >> Cc: Edison Su; Min Chen >> Subject: [ACS42] Duplicate S3 and Swift Object Storage Features >> >> All, >> >> I have noticed during testing that the old S3 and Swift-backed secondary > > > What you mean the old s3/swift secondary? Upgrading the old s3 from 4.1 to > 4.2? > >> storage features are still available in the 4.2.0. It seems to me that they >> should be disabled (given the late date), and removed completely post 4.2.0 >> release. Also, what is the migration/upgrade strategy for customers using >> these features? >> >> Thanks, >> -John
signature.asc
Description: Message signed with OpenPGP using GPGMail
