Hello,
That was indeed my suggestion.
The alternative would be to make sure your ceph can be routed through your
public network. But it’s not my infrastructure, I don’t know what you store as
data, etc…
In either case, you’re making possible for your tenants to access a part of
your infra
Thanks for the answer.
My use case is for a file-hosting software system like « Seafile » which can
use a ceph backend (swift too but we don’t deploy swift on our infra).
Our network configuration of our infra is identical as your OSA documentation.
So, on our compute node we have two bonding
I doubt many people have tried this, because 1) cinder/nova/glance probably do
the job well in a multi-tenant fashion 2) you’re poking holes into your ceph
cluster security.
Anyway, if you still want it, you would need (I guess) have to create a
provider network that will be allowed to access
Hi osa team,
i have a multimode openstack-ansible deployed, ocata 15.1.3, with ceph as
backend for cinder (with our own ceph infra).
After create an instance with root volume, i would like to mount a ceph block
or cephfs directly to the vm (not a cinder volume). So i want to attach a new
