Jump to: navigation, search

Difference between revisions of "SwiftOct1Meeting"

m (Text replace - "__NOTOC__" to "")
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
__NOTOC__
 
= Swift Oct. 1 Meeting Agenda =
 
  
== What is our focus for the next six months? ==
+
= Swift Oct. 1 Meeting =
 +
'''When:''' October 1, 2012 at 20:00 (UTC), 3pm (Central), 1pm (Pacific), 9pm (London)
  
New deployers
+
'''Where:''' #openstack-meeting on freenode (IRC)
* ease of install (shallow learning curve)
 
* automated ops tools
 
  
New contributors
+
== Agenda ==
* better docs about code organization and design
+
# Agenda/Vision/Goal
 +
# Feature catagory overview
 +
# Review features
 +
# Summit talks
 +
# Concerns and Questions
  
New client apps
+
http://etherpad.openstack.org/SwiftOct1Meeting
* improve python-swiftclient
 
* improve other client bindings
 
  
New end users
+
== Features for the next six months, categorized ==
* new features like server-side object splitting
+
=== New Contributors ===
* different auth semantics
+
* improved "getting started as a dev" docs (code organization, design overview)
* other new client-facing features
 
  
Leaves out "baseline" like improving what we already have
+
=== New Deployers ===
* use case: download 1 150MB file with 100 concurrent clients
+
* geo replicas (proxy affinity + tiered zones + separate replication interface)
* better replication
+
* ring server w/ auto device detection
* faster auditing (eg XFS-specific tuning)
+
* remote testing tool (if functests are sufficient, then at least docs)
 +
* concurrent reads to a single object
 +
* on-disk compression
 +
 
 +
=== New Client Apps ===
 +
* improved language bindings
 +
* better docs about ideal client access patters for swift
 +
* better docs about designing datasets to be stored in swift
 +
 
 +
=== New End Users ===
 +
* tiered storage cluster
 +
* better traversal abstractions (how can I get a listing of a large container)
 +
* metadata searching
 +
* server-side object splitting (large single-stream upload)
 +
* multi-range support
 +
* CORS support
 +
* on-disk encryption
 +
* API v2
 +
 
 +
=== Basic "Be More Awesome" Things (Misc) ===
 +
* FS-specific tuning (eg better disk walking)
 +
* replication improvements: eg ring-version-aware communication, "replicate  now" (or general replication priority) support
 +
* remove webob
 +
* replace eventlet?
 +
* container sharding
  
 
== Therefore, what are the summit plans? ==
 
== Therefore, what are the summit plans? ==
 
 
* See Swift topic proposals at http://summit.openstack.org
 
* See Swift topic proposals at http://summit.openstack.org
* CORS
 
* concurrent reads
 
* container sharding
 
* server-side large object splitting
 
* improving replication speed and efficiency
 
* new API
 
* ease of instalation and getting started
 
* geo clusters (affinity, tiered zones)
 
  
 
== Any outstanding concerns or questions ==
 
== Any outstanding concerns or questions ==
* Update on testing concerns (tests not passing on oneric)
+
* ????

Latest revision as of 23:29, 17 February 2013

Swift Oct. 1 Meeting

When: October 1, 2012 at 20:00 (UTC), 3pm (Central), 1pm (Pacific), 9pm (London)

Where: #openstack-meeting on freenode (IRC)

Agenda

  1. Agenda/Vision/Goal
  2. Feature catagory overview
  3. Review features
  4. Summit talks
  5. Concerns and Questions

http://etherpad.openstack.org/SwiftOct1Meeting

Features for the next six months, categorized

New Contributors

  • improved "getting started as a dev" docs (code organization, design overview)

New Deployers

  • geo replicas (proxy affinity + tiered zones + separate replication interface)
  • ring server w/ auto device detection
  • remote testing tool (if functests are sufficient, then at least docs)
  • concurrent reads to a single object
  • on-disk compression

New Client Apps

  • improved language bindings
  • better docs about ideal client access patters for swift
  • better docs about designing datasets to be stored in swift

New End Users

  • tiered storage cluster
  • better traversal abstractions (how can I get a listing of a large container)
  • metadata searching
  • server-side object splitting (large single-stream upload)
  • multi-range support
  • CORS support
  • on-disk encryption
  • API v2

Basic "Be More Awesome" Things (Misc)

  • FS-specific tuning (eg better disk walking)
  • replication improvements: eg ring-version-aware communication, "replicate now" (or general replication priority) support
  • remove webob
  • replace eventlet?
  • container sharding

Therefore, what are the summit plans?

Any outstanding concerns or questions

  •  ????