![]() ![]() ![]() NB! By default S3 / Swift service FQDN - ie host to connect to from your S3 / Swift client - is set to " s3.nf.int". Observe nodefabric-dashboard for "Ceph RGW service" statuses - which should gradually turn green across all nodes.ĭirect storage API HTTP endpoints should be available on all network interfaces at port 9000 and load-balanced internal radosgw service endpoint should be available at port 80 on local docker0 interface (ie 172.17.42.1 typically). # this command is re-run safe # it should start nf-ceph-rgw docker containers # across ALL NodeFabric hosts and to enable them at boot time ![]() In order to launch Ceph Object Gateway service please execute the following on one of the NodeFabric cluster nodes: NB! Ceph storage cluster must be running at this point! Nf-ceph-disk activate /dev/sdb1 # or /dev/xvdb1 in AWS # starting from nodefabric-core-0.4.4 its dashboard # also shows the NodeFabric version # NB! Currently there seems to be systemd OSD service related # race condition with ceph-0.94.5 - which causes OSD service to fail on boot! # Current workaround is to manually activate OSD after boot # reboot nodes one-by-one after nodefabric-update # in order to load new configuration files # if previous nodefabric-update produced docker pull failures # due stopped docker daemon - then start docker daemon and run it again! # please run nodefabric-update utility for pulling new containers # and to update the existing ones # NB! Base OS updates may contain docker rpm package update # which is known to stop docker daemon or running containers! # Rebooting the node afterwards will fix that! # for installing RabbitMQ support package # please check afterwards that new config file additions # were properly merged into /etc/nodefabric/conf.d/nf file # and it now also contains the following portionĬEPH_RGW_INSTANCE = "nf-ceph-rgw" CEPH_RGW_IMAGE = "opennode/nf-ceph-rgw" CEPH_RGW_DNS_NAME = "s3.nf.int" CEPH_RGW_BIND_ADDR = "$HOST_PUBLIC_IP" # IF package versions are older than 0.4.4-6 then # install yum-plugin-merge-conf package and # update existing nodefabric-* rpms Yum list installed | grep nodefabric-core # check existing nodefabric package versions If you are running NodeFabric version older than 0.4.4 you need to update nodefabric-core-* rpms and to pull required service containers. Update NodeFabric to latest (DEV) version Their inclusion into pre-built NodeFabric images is planned for upcoming NodeFabric v0.4.4 release - so for now you can pull them through a simple nodefabric-update procedure. NB! At the time of writing this article nf-ceph-rgw and nf-rabbitmq containers were not yet part of latest NodeFabric Host Images release (as of v.0.4.3). However it does not need special bootstrap procedure - it is enough to simply enable nf-rabbitmq docker instances across NodeFabric cluster nodes. It is packaged as nf-rabbitmq service container and currently it does require 3-node NodeFabric cluster to run on - as it is fully clustered service and provides highly-available message queues. RabbitMQ is an open source message broker software that implements the Advanced Message Queuing Protocol (AMQP). Yet its internal load-balanced service endpoint is auto-created and bound to local docker0 interface as usual. It requires that you have Ceph Monitors and OSDs already running - for detailed instructions how to bootstrap Ceph in NodeFabric please refer to this user-guide section.Ĭeph Object Gateway is packaged as nf-ceph-rgw service container and it is basicly "standalone" - so nf-ceph-rgw docker instances do not need any special cluster bootstrap procedure - just enable them on one or more nodes. AboutĪmazon S3 and Swift object storage APIs can enabled by running Ceph Object Gateway (ie radosgw) service on top of existing NodeFabric Ceph storage cluster. In this article we are looking how to implement Amazon S3 and Openstack Swift object storage based on Ceph Object Gateway (radosgw) service and how to run highly-available RabbitMQ messaging cluster - all turn-key with NodeFabric. 21 November 2015 howto, nodefabric Deploying private AWS S3/Swift and RabbitMQ
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |