Edison, I suggest creating a utils model in engine/storage in package org.apache.cloudstack.engine.storage.utils. When I Swift and S3 were originally implemented, we didn't have such a good place to put these types of classes. Now that we have a more robust module structure, it seems appropriate to move them out.
Thanks, -John On Jul 18, 2013, at 1:53 PM, Edison Su <edison...@citrix.com> wrote: > For s3/swift, both secondary storage code and storage plugin will access > S3/Swift library. > What you suggestion to put these library? > >> -----Original Message----- >> From: Alex Huang [mailto:alex.hu...@citrix.com] >> Sent: Thursday, July 18, 2013 10:02 AM >> To: dev@cloudstack.apache.org >> Subject: Why are these code in utils? >> >> As part of the work to merge vmsync over to master, I've been combing >> through our code. >> >> I'm surprised to find the following code in the utils package. >> >> Cisco n1kv.vsm >> S3 >> Swift >> >> The intent of the utils package is to provide generic java software libraries >> that all other cloudstack libraries to use. These packages do not belong >> here. >> >> --Alex >
