Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

RADOSGW Question


dh0253
15 Posts
August 3, 2020, 6:14 pm

We like to implement PetaSAN. I see application notes for vSphere and Windows for iSCSI. We would also like to add object storage if we move forward. Are there any cheatsheets for adding RADOS gateways? Your support rates are more reasonable than croit.io, but we need to prove to our management team your solution works just as well.

Thank you

#1

admin
2,930 Posts
August 3, 2020, 7:41 pm

I think no one has a solution like us 🙂  We scale out the services layers in active/active fashion (via Consul service mesh platform) besides we put a lot of thought in streamlining the usability of the system.

Yes S3 is planned for 2.7, we typically announce the next release features a week or two after making a release after all the team do their work coordination, so check a week or 2 from now get something solid.

For a test, you can create a simple gateway

# add in etc/ceph/ceph.conf ( replace NODE-NAME with hostname )
[client.rgw.NODE-NAME]
host = NODE-NAME
rgw frontends = "civetweb port=7480"
rgw dns name = 8.8.8.8

mkdir -p /var/lib/ceph/radosgw/ceph-rgw.NODE-NAME
ceph auth get-or-create client.rgw.`hostname -s` osd 'allow rwx' mon 'allow rw' -o /var/lib/ceph/radosgw/ceph-rgw.NODE-NAME/keyring
touch /var/lib/ceph/radosgw/ceph-rgw.NODE-NAME/done
chown -R ceph:ceph /var/lib/ceph/radosgw
systemctl start ceph-radosgw@rgw.NODE-NAME

# add user, make not of access and secret keys
radosgw-admin user create --uid="testuser" --display-name="First User"

That is it. You can test a client via the "TEST S3 ACCESS" method in link 2] at end
Of course this is a simple setup. PetaSAN will support active/active, ha, https, multi-pools, multi-users
1] https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/installation_guide_for_red_hat_enterprise_linux/manually-installing-ceph-object-gateway
2] https://docs.ceph.com/docs/nautilus/install/install-ceph-gateway/

#2

dh0253
15 Posts
August 4, 2020, 12:25 pm

That's great to hear.  I'll check back but in the meantime we'll test using the simple gateway as suggested.  Thank you

#3

admin
2,930 Posts
August 4, 2020, 1:25 pm

To make something production ready:

some client tools like Cyberduck do not work (out of the box without extra config) with http and need https
you can add https by appending 's' to the port name and passing certificate file

[client.rgw.NODE-NAME]
host = NODE-NAME
rgw_frontends = "civetweb port=7480s ssl_certificate=/opt/petasan/config/certificates/radosgw.pem"
rgw dns name = 8.8.8.8

you can use the current PetaSAN certificte used for the PetaSAN Management Web ui if you will run your gateways on the management interface on the first 3 nodes, in such case:

cd /opt/petasan/config/certificates/
cat server.crt server.key > radosgw.pem

On Cyberduck on Windows you would need to install the root.crt in IE or Chrome to be available systemwide for Cyberduck. You can download the certificate from the current PetaSAN Management Web ui.
Again if you want to use https but run the gateways on nodes other than the management nodes, you need to create the certificate yourself.

You can run a load balancer fronting the gateways you will install and have your client access through this balancer.

On first writing, a default data pool will be created with 8 PGs
you can configure the PG count with:

ceph osd pool set default.rgw.buckets.data pg_num 128
ceph osd pool set default.rgw.buckets.data 128

Or if you want full crush control you can create the pool yourself

ceph osd pool create default.rgw.buckets.data 128 128

or
ceph osd pool create default.rgw.buckets.data 128 128 replicated by-host-ssd

#4

dh0253
15 Posts
August 11, 2020, 3:48 pm

I would like to discuss a business opportunity that might expand your product and services further.  Who should I contact?

#5

admin
2,930 Posts
August 11, 2020, 8:51 pm

You can reach us by email:

contact-us @ petasan.org

 

#6