Re: gluster-ansible: status of the project

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Fri, Sep 28, 2018 at 2:33 PM Sachidananda URS <surs@xxxxxxxxxx> wrote:
Hi,

gluster-ansible project is aimed at automating the deployment and maintenance of GlusterFS cluster.

The project can be found at:


We have the python bindings for GlusterD2 API, and can be found at:


The goal is to use the python bindings in gluster_ansible module to make it work with GlusterD2.

Current status of the project:

* We have the initial working roles, packages are available at:

* The initial version supports:
   - End-to-end deployment of Gluster Hyperconverged Infrastructure.
   - GlusterFS volume management
   - GlusterFS brick setup
   - Packages and repository management

* Autogeneration of python bindings for GlusterD2 is being worked by Sidharth (https://github.com/sidharthanup) and available at:

The GD2 API python project will be merged into python-gluster-mgmt-client.

* Ansible modules (WIP):
   - New module: Facts module for self-heal and rebalance. Devyani is working on these modules.
   - Remove brick feature for gluster_ansible module:

Is there any work planned for dynamic inventory (https://docs.ansible.com/ansible/2.5/dev_guide/developing_inventory.html) ?
Peers, bricks and volumes are all good candidates for dynamic inventory.


* Sheersha and Nigel are working on continuous integration, and PR is at:

The CI work is in progress and will be integrated soon. Which will help us to keep the repository
in stable condition.

I recommend running ansible-lint in CI. For example:
[ykaul@ykaul gluster-ansible-infra]$ find . -name "*.yml" |xargs ansible-lint
Syntax Error while loading YAML.
  did not find expected ',' or '}'

The error appears to have been in '/home/ykaul/github/gluster-ansible-infra/examples/backend_with_vdo.yml': line 22, column 8, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

       - {vgname: 'vg_sdb', thinpoolname: 'foo_thinpool', thinpoolsize: '100G', poolmetadatasize: '16G'
       - {vgname: 'vg_sdc', thinpoolname: 'bar_thinpool', thinpoolsize: '500G', poolmetadatasize: '16G'
       ^ here
This one looks easy to fix.  It seems that there is a value started
with a quote, and the YAML parser is expecting to see the line ended
with the same kind of quote.  For instance:

    when: "ok" in result.stdout

Could be written as:

   when: '"ok" in result.stdout'

Or equivalently:

   when: "'ok' in result.stdout"



Questions and feedback are welcome.

-sac
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-devel

[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux