Please note: This schedule is for OpenStack Active Technical Contributors participating in the Icehouse Design Summit sessions in Hong Kong. These are working sessions to determine the roadmap of the Icehouse release and make decisions across the project. To see the full OpenStack Summit schedule, including presentations, panels and workshops, go to http://openstacksummitnovember2013.sched.org.
With the DiskFile abstraction in place for Icehouse development it becomes much easier to create extensions for the Swift Object Server and service requests to alternative storage systems.
To continue and expand on this work I'd like to briefly share my experience building on DiskFile and an alternative object replicator implementation for Swift on ethernet connected key-value drives [1]. Specifically what I discovered about where other storage implementations do not have to overlap with the existing filesystem/rsync implementation.
I'd like to engage the Swift community and seek input on how we can further divide the Swift backend storage system orchestration from implementation and discover emergent generalizations [2] that may be applicable to abstractions in to the Swift consistency engine as a whole.
The goal of the session is set of blueprints that can be refined, accepted, and developed during the Icehouse cycle.
1. Before the session, the kinetic-swift development codebase (which you can run on the Seagate Kinetic-Preview Simulator), will be publicly available as a reference to this work. 2. I'd call out gholt's ssync (https://review.openstack.org/#/c/44115/) specifically as another alternative implementation for the replicators that should inform how we should think about plugging in to backend Swift processes.
