Bug 1534846 - Need a new repository for 'gluster-operator'
Summary: Need a new repository for 'gluster-operator'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-16 04:49 UTC by Amar Tumballi
Modified: 2018-01-16 05:12 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-01-16 05:12:04 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Amar Tumballi 2018-01-16 04:49:14 UTC 
Description of problem:

The goal of this repository is to keep all the operations (deployment, maintenance, and monitoring setups) using just one tool. It would use Ansible and other mechanism to provide these features, and would be a high level tool (not glusterd2) to manage even integrations of Gluster with other projects. For example NFS-ganesha, SMB, gluster-block etc.

Additional Information:

Please keep me (@amarts), @atinmu, @sac in maintainer list for now. Will soon add README and other process related docs to repo.
Comment 1 Nigel Babu 2018-01-16 05:12:04 UTC 
After conversation with Amar, I've created a repo as operator, so it reads github.com/gluster/operator.

Permissions set up.
Note You need to log in before you can comment on or make changes to this bug.