Bug 1041803

Summary: [RFE][glance]: Driver to store images on an IBM GPFS file system backend
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-glanceAssignee: Flavio Percoco <fpercoco>
Status: CLOSED UPSTREAM QA Contact: nlevinki <nlevinki>
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: eglynn, eharney, fpercoco, markmc, scohen, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/glance/+spec/gpfs-image-store
Whiteboard: upstream_milestone_none upstream_status_needs-code-review upstream_definition_approved
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-16 17:50:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 19:23:55 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/glance/+spec/gpfs-image-store.

Description:

IBM General Parallel File System (GPFS) is a mature cluster file system used by some of the largest enterprises and supercomputers in the world.  It offers a number of specific features and optimizations for hosting master images, instances, and volumes.  In particular, the bock-level format-agnostic copy-on-write mechanism enables quick instance provisioning that avoids data copy.  The File Placement Optimization (FPO) feature allows specifying the set of nodes and their local disks where the physical blocks of a particular image file and its replicas should be allocated. Transparent block-level replication, controllable per file, provides resilience.

This store driver implements an initial set of features using the primitives of the GPFS file system.

Specification URL (additional information):

None
Comment 3 Flavio Percoco 2015-01-14 09:58:04 UTC 
This was never merged and it's stuck upstream
Comment 4 Sean Cohen 2015-03-16 17:50:07 UTC 
(In reply to Flavio Percoco from comment #3)
> This was never merged and it's stuck upstream

Correct, closing upstream accordingly.
Sean