base on Gluster Filesystem : Build your distributed storage in minutes <h1 align="center"><img src="https://www.gluster.org/wp-content/uploads/2016/03/gluster-ant.png" width="320" alt="Gluster is a free and open source software scalable network filesystem."></h1> <h4 align="center"> <a href="https://gluster.slack.com/"><img src=https://img.shields.io/badge/CHATON-SLACK-green></a> <a href="https://www.youtube.com/playlist?list=PLUjCssFKEMhXBqPAGtOA1lYtzS1eWaJuN"><img src=https://img.shields.io/badge/DEV%20SESSIONS-YOUTUBE-red></a> <a href="https://twitter.com/gluster"><img src=https://img.shields.io/badge/FOLLOW-ON%20TWITTER-blue></a><br/><br/> <a href="https://docs.gluster.org/en/latest/Quick-Start-Guide/Quickstart/"><img src=https://img.shields.io/badge/%20%20-Quick%20Start%20Guide-yellowgreen?style=for-the-badge></a> <a href="https://docs.gluster.org/en/latest/release-notes/"><img src=https://img.shields.io/badge/%20%20-Release%20Notes-%2341EDF5?style=for-the-badge></a> <a href="https://lists.gluster.org/mailman/listinfo"><img src=https://img.shields.io/badge/%20%20-Mailing%20List-%23F59E41?style=for-the-badge></a> <a href="https://www.gluster.org/community/"><img src=https://img.shields.io/badge/%20-COMMUNITY-%237D41F5?style=for-the-badge></a><br/><br/> <a href="https://docs.gluster.org/en/latest/Contributors-Guide/Index/"><img src=https://readme-typing-svg.herokuapp.com?color=%23000000&size=32&center=true&width=600&lines=Contribute+to+Gluster></a> </h4> --- <p align="left"> <a href="https://github.com/gluster/Gluster-Builds/actions"><img src="https://github.com/gluster/Gluster-Builds/actions/workflows/Nightly_Build_Fedora_Latest.yml/badge.svg" alt="Build Status"></a> <a href="https://github.com/gluster/Gluster-Builds/actions"> <img src="https://github.com/gluster/Gluster-Builds/actions/workflows/Nightly_Build_Centos7.yml/badge.svg" alt="Coverage Status"></a> <a href="https://github.com/gluster/Gluster-Builds/actions"><img src="https://github.com/gluster/Gluster-Builds/actions/workflows/Nightly_Build_Centos8.yml/badge.svg"></a> <a href="https://github.com/gluster/Gluster-Builds/actions"><img src="https://github.com/gluster/Gluster-Builds/actions/workflows/nightly-build-debian.yml/badge.svg"></a> <a href="https://github.com/gluster/Gluster-Builds/actions"><img src="https://github.com/gluster/Gluster-Builds/actions/workflows/nightly-build-ubuntu.yml/badge.svg"></a> <a href="https://ci.centos.org/view/Gluster/job/gluster_build-rpms/"><img src="https://ci.centos.org/buildStatus/icon?job=gluster_build-rpms"></a> <a href="https://scan.coverity.com/projects/gluster-glusterfs"><img src="https://scan.coverity.com/projects/987/badge.svg"></a> </p> # Gluster Gluster is a software defined distributed storage that can scale to several petabytes. It provides interfaces for object, block and file storage. ## Development The development workflow is documented in [Contributors guide](CONTRIBUTING.md) ## Documentation The Gluster documentation can be found at [Gluster Docs](http://docs.gluster.org). ## Deployment Quick instructions to build and install can be found in [INSTALL](INSTALL) file. ## Testing GlusterFS source contains some functional tests under `tests/` directory. All these tests are run against every patch submitted for review. If you want your patch to be tested, please add a `.t` test file as part of your patch submission. You can also submit a patch to only add a `.t` file for the test case you are aware of. To run these tests, on your test-machine, just run `./run-tests.sh`. Don't run this on a machine where you have 'production' glusterfs is running, as it would blindly kill all gluster processes in each runs. If you are sending a patch, and want to validate one or few specific tests, then run a single test by running the below command. ``` bash# /bin/bash ${path_to_gluster}/tests/basic/rpc-coverage.t ``` You can also use `prove` tool if available in your machine, as follows. ``` bash# prove -vmfe '/bin/bash' ${path_to_gluster}/tests/basic/rpc-coverage.t ``` ## Maintainers The list of Gluster maintainers is available in [MAINTAINERS](MAINTAINERS) file. ## License Gluster is dual licensed under [GPLV2](COPYING-GPLV2) and [LGPLV3+](COPYING-LGPLV3). Please visit the [Gluster Home Page](http://www.gluster.org/) to find out more about Gluster. ", Assign "at most 3 tags" to the expected json: {"id":"7629","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"