Skip to content

Instantly share code, notes, and snippets.

View ajarr's full-sized avatar

Ramana Raja ajarr

16 followers · 0 following
  • Red Hat, Inc.
  • Toronto
View GitHub Profile
@ajarr
ajarr / gist:84e25502a427262b6af234687ed3ea9d
Created November 8, 2019 13:01
my fedora 29 vagrant file
# -*- mode: ruby -*-
# vi: set ft=ruby :
# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
# The most common configuration options are documented and commented below.
# For a complete reference, please see the online documentation at
@ajarr
ajarr / dev_setup_cephfs_nfs_manila.md
Last active February 25, 2019 04:02
All-in-one dev setup for manila's cephfs/nfs-ganesha driver

Dev testing manila's cephfs(NFS) driver

Reference https://docs.openstack.org/developer/manila/devref/cephfs_driver.html

Create all-in-one** CephFS/Ganesha/Manila setup using devstack in a CentOS7 machine similar to the one in the upstream gate, gate-manila-tempest-minimal-dsvm-cephfs-nfs-centos-7-nv

** Ceph server daemons (1 OSD, 1 MON, 1 MDS), NFS-Ganesha server, and manila-services all run in the same machine.

  • Clone devstack
@ajarr
ajarr / single tenant Ganesha driver.md
Last active August 29, 2015 14:01
Single tenant GlusterFS Ganesha driver for Manila

#Single tenant GlusterFS Ganesha driver for Manila

The initial prototype of the Ganesha driver will be tailored to work for the GlusterFS backend, and in the next iteration will be made modular. The following operations will be supported initially:

  • create
  • delete
  • access-allow
  • access-deny

As a part of the initial set up, Manila will check whether the GlusterFS client and Ganesha server programs are installed in the host machine, and will fuse (mount) a GlusterFS volume on the host machine.

@ajarr
ajarr / multi_acc_per_vol_G4S
Created September 20, 2013 14:55
Multiple accounts per volume for Gluster for Swift (revised)
# Multiple accounts per volume for _Gluster for Swift_
[TOC]
##Problem Statement
At present, Gluster for Swift (G4S) allows only one account to reside in a
Gluster volume. An account maps to a single Gluster volume, i.e., the root
directory of the Gluster volume mount point serves as the account.
(*/mnt/gluster-object/$vol\_name*).
@ajarr
ajarr / multi_acc_per_vol_G4S.md
Last active December 23, 2015 12:59
Multiple accounts per volume for Gluster for Swift (revised by Ram)

Multiple accounts per volume for Gluster for Swift

[TOC]

##Problem Statement

At present, Gluster for Swift (G4S) allows only one account to reside in a Gluster volume. An account maps to a single Gluster volume, i.e., the root directory of the Gluster volume mount point serves as the account. (/mnt/gluster-object/$vol_name).

@ajarr
ajarr / Multiples accounts per volume for Gluster for Swift (checked by Ram))
Created September 20, 2013 10:18
Multiple accounts per volume for Gluster for Swift (revised)
# Multiple accounts per volume for _Gluster for Swift_
[TOC]
##Problem Statement
At present, Gluster for Swift (G4S) allows only one account to reside in a
Gluster volume. An account maps to a single Gluster volume, i.e., the root
directory of the Gluster volume mount point serves as the account.
(*/mnt/gluster-object/$vol\_name*).