On Tue, Sep 10, 2019 at 05:14:34PM +0800, vladimir franciz blando wrote:
> I have 2 OpenStack environment that I want to integrate to an
> existing ceph cluster.  I know technically it can be done but has
> anyone tried this?

Yes, it works fine. You need each OpenStack to have a different client
key, so that they can't trample on each other's pools; and you need some
sort of naming convention, so you can tell which pool belongs to which
OpenStack.

For example, our OpenStack deployments are named after Greek letters, so
we have ceph-ansible create the pools eta-images, eta-vms,
eta-volumes... zeta-images, zeta-vms, zeta-volumes for the two
deployments "eta" and "zeta". ceph-ansible also manages the different
client keys, "client.openstack-eta" and "client.openstack-zeta", with
permissions only for the appropriate pools.

We use Red Hat OpenStack (based on TripleO) so for each deployment there
is a yaml file describing where its Ceph is, e.g. for Eta it looks like
this:

parameter_defaults:
  CephClusterFSID: '12341234-1234-1234-1234-123412341234'
  CephClientKey: 'asdfasdfasdfasdfasdfasdfasdfasdfasdfas=='
  CephExternalMonHost: '1.2.3.4, 5.6.7.8, 9.10.11.12'
  NovaRbdPoolName: eta-vms
  CinderRbdPoolName: eta-volumes
  GlanceRbdPoolName: eta-images
  CephClientUserName: openstack-eta

The FSID and mons will be the same for each deployment but the key and
pool names will be different.

Cheers,
Dave
--
** Dave Holland ** Systems Support -- Informatics Systems Group **
** 01223 496923 **    Wellcome Sanger Institute, Hinxton, UK    **


--
 The Wellcome Sanger Institute is operated by Genome Research
 Limited, a charity registered in England with number 1021457 and a
 company registered in England with number 2742969, whose registered
 office is 215 Euston Road, London, NW1 2BE.
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-leave@ceph.io