From mkudlej at redhat.com Fri Aug 4 10:12:07 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Fri, 4 Aug 2017 12:12:07 +0200 Subject: [Tendrl-devel] Milestone 1 deliverables Message-ID: <3437d314-0877-9901-b73d-49a2b0f3d13b@redhat.com> Hi Tendlr community, I see that first milestone is close to finish https://github.com/Tendrl/specifications/milestone/2 I would like to ask about what deliverables could we expect? I expect install and configuration documentation plus repository where can we find packages for installation. Thank you for answer! -- Best Regards, Martin Kudlej. RHSC/USM Senior Quality Assurance Engineer Red Hat Czech s.r.o. Phone: +420 532 294 155 E-mail:mkudlej at redhat.com IRC: mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph, #usm-meeting @ redhat #tendrl-devel @ freenode From sankarshan.mukhopadhyay at gmail.com Fri Aug 4 10:29:43 2017 From: sankarshan.mukhopadhyay at gmail.com (Sankarshan Mukhopadhyay) Date: Fri, 4 Aug 2017 15:59:43 +0530 Subject: [Tendrl-devel] Milestone 1 deliverables In-Reply-To: <3437d314-0877-9901-b73d-49a2b0f3d13b@redhat.com> References: <3437d314-0877-9901-b73d-49a2b0f3d13b@redhat.com> Message-ID: On Fri, Aug 4, 2017 at 3:42 PM, Martin Kudlej wrote: > I see that first milestone is close to finish > https://github.com/Tendrl/specifications/milestone/2 > I would like to ask about what deliverables could we expect? > I expect install and configuration documentation plus repository where can > we find packages for installation. > In continuation with how we have done any previous builds - the note of announcement will be including link to the documentation which allows installation and configuration of the stack; packages off a repository URL. From dahorak at redhat.com Fri Aug 4 12:49:55 2017 From: dahorak at redhat.com (=?UTF-8?Q?Daniel_Hor=c3=a1k?=) Date: Fri, 4 Aug 2017 14:49:55 +0200 Subject: [Tendrl-devel] CentOS CI status (packages build trigger and validation tests) Message-ID: <1f48081b-02f7-a487-5d22-1d0ca6f72a8b@redhat.com> Hi Timothy, I have few updates (and two questions) related to the CentOS CI jobs, mainly to the jobs for triggering new builds. I've created jobs for building packages from master branch[1] (the job names are quite descriptive what they do). The building process works quite fine, the packages are now stored in my testing copr repository[2]. If you think, everything looks ok, we can switch them to the official tendrl copr repo. For that change, I need two things from you: * Copr configuration file in following location: slave01.ci.centos.org:/home/tendrl/.copr-tendrl.conf If you don't have access to the slave01 machine, send me the content privately and I'll create it there. * Which Copr repo is intended for the tendrl packages from master branch? There are also jobs for building packages from release[3] and feature[4] branches, but those jobs might not be fully ready as I'm not able to properly test them (until there will be new release or some feature branch). The jobs containing "pkgval" are for package validation (rpmlint, rpmdeplint,...). If for example "Tendrl build- (master) - BUILD ALL PACKAGES" job is triggered, the all the packages from master branch are built and then respective validation test jobs are launched. [1] https://ci.centos.org/view/tendrl-build-master/ [2] https://copr.fedorainfracloud.org/coprs/dahorak/tendrl-test-master/packages/ [3] https://ci.centos.org/view/tendrl-build-release/ [4] https://ci.centos.org/view/tendrl-build-feature/ Thanks, Daniel From mkudlej at redhat.com Fri Aug 4 13:06:50 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Fri, 4 Aug 2017 15:06:50 +0200 Subject: [Tendrl-devel] Milestone 1 deliverables In-Reply-To: References: <3437d314-0877-9901-b73d-49a2b0f3d13b@redhat.com> Message-ID: Hi Sankarshan, thank you for response! On 08/04/2017 12:29 PM, Sankarshan Mukhopadhyay wrote: > On Fri, Aug 4, 2017 at 3:42 PM, Martin Kudlej wrote: > >> I see that first milestone is close to finish >> https://github.com/Tendrl/specifications/milestone/2 >> I would like to ask about what deliverables could we expect? >> I expect install and configuration documentation plus repository where can >> we find packages for installation. >> > > In continuation with how we have done any previous builds - the note > of announcement will be including link to the documentation which > allows installation and configuration of the stack; packages off a > repository URL. > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > -- Best Regards, Martin Kudlej. RHSC/USM Senior Quality Assurance Engineer Red Hat Czech s.r.o. Phone: +420 532 294 155 E-mail:mkudlej at redhat.com IRC: mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph, #usm-meeting @ redhat #tendrl-devel @ freenode From rkanade at redhat.com Fri Aug 4 14:18:28 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Fri, 4 Aug 2017 19:48:28 +0530 Subject: [Tendrl-devel] tendrl-release v1.5.0 (Milestone1) is available Message-ID: Hello, The Tendrl team is happy to present tendrl-release v1.5.0 (Milestone1) Summary: https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.5.0-(summary) Install docs: https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.5.0-(install-doc) Cheers! From mbukatov at redhat.com Fri Aug 4 15:50:58 2017 From: mbukatov at redhat.com (Martin Bukatovic) Date: Fri, 4 Aug 2017 17:50:58 +0200 Subject: [Tendrl-devel] improving unit test plumbing Message-ID: Hi Filip, see commits in this node-agent pull request: https://github.com/Tendrl/node-agent/pull/573/commits and create pull requests which will address this kind of problems for the remaining python tendrl repositories (with exception of tendrl-commons, which is being fixed in https://github.com/Tendrl/commons/pull/677). This way, you should be able to run all unit tests from command line via tox like this (assuming you are in the root directory of a repository): $ tox And you should be also able to pass additional arguments to pytest like this: $ tox -- tendrl/commons/tests/test_message.py -v (so that executing particular tests via tox is possible) Thanks a lot. -- Martin Bukatovic USM QE team Red Hat From tjeyasin at redhat.com Tue Aug 8 07:31:34 2017 From: tjeyasin at redhat.com (Timothy Asir Jeyasingh) Date: Tue, 8 Aug 2017 13:01:34 +0530 Subject: [Tendrl-devel] CentOS CI status (packages build trigger and validation tests) In-Reply-To: <1f48081b-02f7-a487-5d22-1d0ca6f72a8b@redhat.com> References: <1f48081b-02f7-a487-5d22-1d0ca6f72a8b@redhat.com> Message-ID: Hi Daniel, Please see my inline messages. Thanks, Timothy On Fri, Aug 4, 2017 at 6:19 PM, Daniel Hor?k wrote: > Hi Timothy, > > I have few updates (and two questions) related to the CentOS CI jobs, > mainly to the jobs for triggering new builds. > > I've created jobs for building packages from master branch[1] (the job > names are quite descriptive what they do). > > The building process works quite fine, the packages are now stored in my > testing copr repository[2]. > If you think, everything looks ok, we can switch them to the official > tendrl copr repo. > For that change, I need two things from you: > > * Copr configuration file in following location: > slave01.ci.centos.org:/home/tendrl/.copr-tendrl.conf > If you don't have access to the slave01 machine, send me the content > privately and I'll create it there. > > Have some access issue, i will send you a mail > * Which Copr repo is intended for the tendrl packages from master branch? > > tendrl/tendrl > There are also jobs for building packages from release[3] and feature[4] > branches, but those jobs might not be fully ready as I'm not able to > properly test them (until there will be new release or some feature branch). > > That's fine > The jobs containing "pkgval" are for package validation (rpmlint, > rpmdeplint,...). > If for example "Tendrl build- (master) - BUILD ALL PACKAGES" job is > triggered, the all the packages from master branch are built and then > respective validation test jobs are launched. > > [1] https://ci.centos.org/view/tendrl-build-master/ > [2] https://copr.fedorainfracloud.org/coprs/dahorak/tendrl-test- > master/packages/ > [3] https://ci.centos.org/view/tendrl-build-release/ > [4] https://ci.centos.org/view/tendrl-build-feature/ > > Thanks, > Daniel > From dahorak at redhat.com Tue Aug 8 08:18:58 2017 From: dahorak at redhat.com (=?UTF-8?Q?Daniel_Hor=c3=a1k?=) Date: Tue, 8 Aug 2017 10:18:58 +0200 Subject: [Tendrl-devel] CentOS CI status (packages build trigger and validation tests) In-Reply-To: References: <1f48081b-02f7-a487-5d22-1d0ca6f72a8b@redhat.com> Message-ID: Hi Timothy, I've switched the master branch builds to tendrl/tendrl repo and it seems to work as expected[1,2]. The build job for each package is configured to trigger once peer 4 hours, if there is any change in the repo/branch (hopefully it will work correctly). Also it is possible to trigger build of all packages manually via "Tendrl build- (master) - BUILD ALL PACKAGES" job. This will also trigger all the package validation tests. Now the jobs are configured to build following packages: - api - commons - gluster-integration - monitoring-integration - node-agent - ui Is the list correct? Or should I add some other (for example ceph-integration)? There are some issues with the package validation tests, I'll work on that. [1] https://ci.centos.org/view/tendrl-build-master/ [2] https://ci.centos.org/view/Tendrl-master/ Regards, Daniel On 08/08/17 09:31, Timothy Asir Jeyasingh wrote: > Hi Daniel, > > Please see my inline messages. > > Thanks, > Timothy > > On Fri, Aug 4, 2017 at 6:19 PM, Daniel Hor?k > wrote: > > Hi Timothy, > > I have few updates (and two questions) related to the CentOS CI > jobs, mainly to the jobs for triggering new builds. > > I've created jobs for building packages from master branch[1] (the > job names are quite descriptive what they do). > > The building process works quite fine, the packages are now stored > in my testing copr repository[2]. > If you think, everything looks ok, we can switch them to the > official tendrl copr repo. > For that change, I need two things from you: > > * Copr configuration file in following location: > slave01.ci.centos.org:/home/tendrl/.copr-tendrl.conf > If you don't have access to the slave01 machine, send me the > content privately and I'll create it there. > > Have some access issue, i will send you a mail > > * Which Copr repo is intended for the tendrl packages from master > branch? > > tendrl/tendrl > > There are also jobs for building packages from release[3] and > feature[4] branches, but those jobs might not be fully ready as I'm > not able to properly test them (until there will be new release or > some feature branch). > > That's fine > > The jobs containing "pkgval" are for package validation (rpmlint, > rpmdeplint,...). > If for example "Tendrl build- (master) - BUILD ALL PACKAGES" job is > triggered, the all the packages from master branch are built and > then respective validation test jobs are launched. > > [1] https://ci.centos.org/view/tendrl-build-master/ > > [2] > https://copr.fedorainfracloud.org/coprs/dahorak/tendrl-test-master/packages/ > > [3] https://ci.centos.org/view/tendrl-build-release/ > > [4] https://ci.centos.org/view/tendrl-build-feature/ > > > Thanks, > Daniel > > From sankarshan at redhat.com Tue Aug 8 08:24:50 2017 From: sankarshan at redhat.com (sankarshan) Date: Tue, 8 Aug 2017 13:54:50 +0530 Subject: [Tendrl-devel] CentOS CI status (packages build trigger and validation tests) In-Reply-To: References: <1f48081b-02f7-a487-5d22-1d0ca6f72a8b@redhat.com> Message-ID: On 8 August 2017 at 13:48, Daniel Hor?k wrote: > Hi Timothy, > > I've switched the master branch builds to tendrl/tendrl repo and it seems to > work as expected[1,2]. > > The build job for each package is configured to trigger once peer 4 hours, > if there is any change in the repo/branch (hopefully it will work > correctly). > > Also it is possible to trigger build of all packages manually via "Tendrl > build- (master) - BUILD ALL PACKAGES" job. This will also trigger all the > package validation tests. > > Now the jobs are configured to build following packages: > - api > - commons > - gluster-integration > - monitoring-integration > - node-agent > - ui > Is the list correct? Or should I add some other (for example > ceph-integration)? > I'd suggest that for the moment we focus on the packages/repositories which result in build of the monitoring solution for Gluster. > There are some issues with the package validation tests, I'll work on that. > > [1] https://ci.centos.org/view/tendrl-build-master/ > [2] https://ci.centos.org/view/Tendrl-master/ > > Regards, > Daniel > > On 08/08/17 09:31, Timothy Asir Jeyasingh wrote: >> >> Hi Daniel, >> >> Please see my inline messages. >> >> Thanks, >> Timothy >> >> On Fri, Aug 4, 2017 at 6:19 PM, Daniel Hor?k > > wrote: >> >> Hi Timothy, >> >> I have few updates (and two questions) related to the CentOS CI >> jobs, mainly to the jobs for triggering new builds. >> >> I've created jobs for building packages from master branch[1] (the >> job names are quite descriptive what they do). >> >> The building process works quite fine, the packages are now stored >> in my testing copr repository[2]. >> If you think, everything looks ok, we can switch them to the >> official tendrl copr repo. >> For that change, I need two things from you: >> >> * Copr configuration file in following location: >> slave01.ci.centos.org:/home/tendrl/.copr-tendrl.conf >> If you don't have access to the slave01 machine, send me the >> content privately and I'll create it there. >> >> Have some access issue, i will send you a mail >> >> * Which Copr repo is intended for the tendrl packages from master >> branch? >> >> tendrl/tendrl >> >> There are also jobs for building packages from release[3] and >> feature[4] branches, but those jobs might not be fully ready as I'm >> not able to properly test them (until there will be new release or >> some feature branch). >> >> That's fine >> >> The jobs containing "pkgval" are for package validation (rpmlint, >> rpmdeplint,...). >> If for example "Tendrl build- (master) - BUILD ALL PACKAGES" job is >> triggered, the all the packages from master branch are built and >> then respective validation test jobs are launched. >> >> [1] https://ci.centos.org/view/tendrl-build-master/ >> >> [2] >> >> https://copr.fedorainfracloud.org/coprs/dahorak/tendrl-test-master/packages/ >> >> >> [3] https://ci.centos.org/view/tendrl-build-release/ >> >> [4] https://ci.centos.org/view/tendrl-build-feature/ >> >> >> Thanks, >> Daniel >> >> > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel From tjeyasin at redhat.com Tue Aug 8 08:33:43 2017 From: tjeyasin at redhat.com (Timothy Asir Jeyasingh) Date: Tue, 8 Aug 2017 14:03:43 +0530 Subject: [Tendrl-devel] CentOS CI status (packages build trigger and validation tests) In-Reply-To: References: <1f48081b-02f7-a487-5d22-1d0ca6f72a8b@redhat.com> Message-ID: Brilliant job!, Perfectly done, Thank you. We need only these packages for now. Please fix those package validation test issues also. Thanks and Regards, Tim On Tue, Aug 8, 2017 at 1:48 PM, Daniel Hor?k wrote: > Hi Timothy, > > I've switched the master branch builds to tendrl/tendrl repo and it seems > to work as expected[1,2]. > > The build job for each package is configured to trigger once peer 4 hours, > if there is any change in the repo/branch (hopefully it will work > correctly). > > Also it is possible to trigger build of all packages manually via "Tendrl > build- (master) - BUILD ALL PACKAGES" job. This will also trigger all the > package validation tests. > > Now the jobs are configured to build following packages: > - api > - commons > - gluster-integration > - monitoring-integration > - node-agent > - ui > Is the list correct? Or should I add some other (for example > ceph-integration)? > > There are some issues with the package validation tests, I'll work on that. > > [1] https://ci.centos.org/view/tendrl-build-master/ > [2] https://ci.centos.org/view/Tendrl-master/ > > Regards, > Daniel > > On 08/08/17 09:31, Timothy Asir Jeyasingh wrote: > >> Hi Daniel, >> >> Please see my inline messages. >> >> Thanks, >> Timothy >> >> On Fri, Aug 4, 2017 at 6:19 PM, Daniel Hor?k > dahorak at redhat.com>> wrote: >> >> Hi Timothy, >> >> I have few updates (and two questions) related to the CentOS CI >> jobs, mainly to the jobs for triggering new builds. >> >> I've created jobs for building packages from master branch[1] (the >> job names are quite descriptive what they do). >> >> The building process works quite fine, the packages are now stored >> in my testing copr repository[2]. >> If you think, everything looks ok, we can switch them to the >> official tendrl copr repo. >> For that change, I need two things from you: >> >> * Copr configuration file in following location: >> slave01.ci.centos.org:/home/tendrl/.copr-tendrl.conf >> If you don't have access to the slave01 machine, send me the >> content privately and I'll create it there. >> >> Have some access issue, i will send you a mail >> >> * Which Copr repo is intended for the tendrl packages from master >> branch? >> >> tendrl/tendrl >> >> There are also jobs for building packages from release[3] and >> feature[4] branches, but those jobs might not be fully ready as I'm >> not able to properly test them (until there will be new release or >> some feature branch). >> >> That's fine >> >> The jobs containing "pkgval" are for package validation (rpmlint, >> rpmdeplint,...). >> If for example "Tendrl build- (master) - BUILD ALL PACKAGES" job is >> triggered, the all the packages from master branch are built and >> then respective validation test jobs are launched. >> >> [1] https://ci.centos.org/view/tendrl-build-master/ >> >> [2] >> https://copr.fedorainfracloud.org/coprs/dahorak/tendrl-test- >> master/packages/ >> > test-master/packages/> >> [3] https://ci.centos.org/view/tendrl-build-release/ >> >> [4] https://ci.centos.org/view/tendrl-build-feature/ >> >> >> Thanks, >> Daniel >> >> >> > From nthomas at redhat.com Tue Aug 8 15:17:38 2017 From: nthomas at redhat.com (Nishanth Thomas) Date: Tue, 8 Aug 2017 20:47:38 +0530 Subject: [Tendrl-devel] CentOS CI status (packages build trigger and validation tests) In-Reply-To: References: <1f48081b-02f7-a487-5d22-1d0ca6f72a8b@redhat.com> Message-ID: On Tue, Aug 8, 2017 at 1:48 PM, Daniel Hor?k wrote: > Hi Timothy, > > I've switched the master branch builds to tendrl/tendrl repo and it seems > to work as expected[1,2]. > > The build job for each package is configured to trigger once peer 4 hours, > if there is any change in the repo/branch (hopefully it will work > correctly). > > Also it is possible to trigger build of all packages manually via "Tendrl > build- (master) - BUILD ALL PACKAGES" job. This will also trigger all the > package validation tests. > > Now the jobs are configured to build following packages: > - api > - commons > - gluster-integration > - monitoring-integration > - node-agent > - ui > Is the list correct? Or should I add some other (for example > ceph-integration)? > This is correct. > > There are some issues with the package validation tests, I'll work on that. > > [1] https://ci.centos.org/view/tendrl-build-master/ > [2] https://ci.centos.org/view/Tendrl-master/ > > Regards, > Daniel > > On 08/08/17 09:31, Timothy Asir Jeyasingh wrote: > >> Hi Daniel, >> >> Please see my inline messages. >> >> Thanks, >> Timothy >> >> On Fri, Aug 4, 2017 at 6:19 PM, Daniel Hor?k > dahorak at redhat.com>> wrote: >> >> Hi Timothy, >> >> I have few updates (and two questions) related to the CentOS CI >> jobs, mainly to the jobs for triggering new builds. >> >> I've created jobs for building packages from master branch[1] (the >> job names are quite descriptive what they do). >> >> The building process works quite fine, the packages are now stored >> in my testing copr repository[2]. >> If you think, everything looks ok, we can switch them to the >> official tendrl copr repo. >> For that change, I need two things from you: >> >> * Copr configuration file in following location: >> slave01.ci.centos.org:/home/tendrl/.copr-tendrl.conf >> If you don't have access to the slave01 machine, send me the >> content privately and I'll create it there. >> >> Have some access issue, i will send you a mail >> >> * Which Copr repo is intended for the tendrl packages from master >> branch? >> >> tendrl/tendrl >> >> There are also jobs for building packages from release[3] and >> feature[4] branches, but those jobs might not be fully ready as I'm >> not able to properly test them (until there will be new release or >> some feature branch). >> >> That's fine >> >> The jobs containing "pkgval" are for package validation (rpmlint, >> rpmdeplint,...). >> If for example "Tendrl build- (master) - BUILD ALL PACKAGES" job is >> triggered, the all the packages from master branch are built and >> then respective validation test jobs are launched. >> >> [1] https://ci.centos.org/view/tendrl-build-master/ >> >> [2] >> https://copr.fedorainfracloud.org/coprs/dahorak/tendrl-test- >> master/packages/ >> > test-master/packages/> >> [3] https://ci.centos.org/view/tendrl-build-release/ >> >> [4] https://ci.centos.org/view/tendrl-build-feature/ >> >> >> Thanks, >> Daniel >> >> >> > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > From surs at redhat.com Wed Aug 9 13:14:22 2017 From: surs at redhat.com (Sachidananda URS) Date: Wed, 9 Aug 2017 18:44:22 +0530 Subject: [Tendrl-devel] Overview of geo-replication support in gdeploy Message-ID: Hi, gdeploy will have support for deploying geo-replication in the upcoming RHGS 3.3.1 release. The following features will be supported: * create (Secure and root user based deployments) * failover * failback * start/stop/pause/delete sessions * config (Configure geo-replication options) * gluster-log-file * gluster-log-level * log-file * log-level * changelog-log-level * ssh-command * rsync-command * use-tarssh * volume-id * timeout * sync-jobs * ignore-deletes * checkpoint * sync-acls * sync-xattrs * log-rsync-performance * rsync-options * use-meta-volume Please find the attached example configuration files. They are self-explanatory. Please let me know if you have any doubts. -sac -------------- next part -------------- # Delete a geo-replication session # Usage: gdeploy -c georep-delete.conf [hosts] 10.70.42.122 [geo-replication] action=delete georepuser=testgeorep mastervol=10.70.42.122:master slavevol=10.70.43.48:slave -------------- next part -------------- # Resume a geo-replication session # Usage: gdeploy -c georep-resume.conf [hosts] 10.70.42.122 [geo-replication] action=resume # georepuser=testgeorep mastervol=10.70.42.122:master slavevol=10.70.43.48:slave # force=no -------------- next part -------------- # Pause a geo-replication session # Usage: gdeploy -c georep-pause.conf [hosts] 10.70.42.122 [geo-replication] action=pause # georepuser=testgeorep mastervol=10.70.42.122:master slavevol=10.70.43.48:slave # force=no -------------- next part -------------- # Stop a geo-replication session # Usage: gdeploy -c georep-stop.conf [hosts] 10.70.42.122 [geo-replication] action=stop #georepuser=testgeorep mastervol=10.70.42.122:master slavevol=10.70.43.48:slave # force=no -------------- next part -------------- # Start a geo-replication session # Usage: gdeploy -c georep-start.conf [hosts] 10.70.42.122 [geo-replication] action=start georepuser=testgeorep mastervol=10.70.42.122:master slavevol=10.70.43.48:slave # force=no -------------- next part -------------- # # Usage: # gdeploy -c georep-secure.conf # # This config sets up secure geo-replication between the volumes # `mastervolume' and `slavevolume' as user testgeorep, by default # georep session is started, to just create a session and not start # it during creation set the variable start=no # # This sets up the session as user root. If a secure-session is # needed see georep-secure.conf # [hosts] 10.70.42.122 [geo-replication] action=create georepuser=testgeorep mastervol=10.70.42.122:master slavevol=10.70.43.48:slave slavenodes=10.70.43.48,10.70.42.217 force=no # start=no -------------- next part -------------- # # Usage: # gdeploy -c geo-replication.conf # # This config sets up geo-replication between the volumes # `mastervolume' and `slavevolume', by default georep session # is started, to just create a session and not start it during # creation set the variable start=no # # This sets up the session as user root. If a secure-session is # needed see georep-secure.conf # [hosts] 10.70.43.219 [geo-replication] action=create mastervol=10.70.43.219:mastervolume slavevol=10.70.43.25:slavesvolume slavenodes=10.70.43.25,10.70.43.86 force=yes # start=no From japplewh at redhat.com Thu Aug 10 00:26:44 2017 From: japplewh at redhat.com (Jeff Applewhite) Date: Thu, 10 Aug 2017 00:26:44 +0000 Subject: [Tendrl-devel] Overview of geo-replication support in gdeploy In-Reply-To: References: Message-ID: Excellent! Thanks Sac On Wed, Aug 9, 2017 at 9:17 AM Sachidananda URS wrote: > Hi, > > gdeploy will have support for deploying geo-replication in the > upcoming RHGS 3.3.1 release. > The following features will be supported: > > * create (Secure and root user based deployments) > * failover > * failback > * start/stop/pause/delete sessions > * config (Configure geo-replication options) > * gluster-log-file > * gluster-log-level > * log-file > * log-level > * changelog-log-level > * ssh-command > * rsync-command > * use-tarssh > * volume-id > * timeout > * sync-jobs > * ignore-deletes > * checkpoint > * sync-acls > * sync-xattrs > * log-rsync-performance > * rsync-options > * use-meta-volume > > > Please find the attached example configuration files. They are > self-explanatory. > Please let me know if you have any doubts. > > -sac > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > -- Jeff Applewhite Principal Product Manager From sankarshan at redhat.com Thu Aug 10 03:52:25 2017 From: sankarshan at redhat.com (sankarshan) Date: Thu, 10 Aug 2017 09:22:25 +0530 Subject: [Tendrl-devel] Overview of geo-replication support in gdeploy In-Reply-To: References: Message-ID: On 9 August 2017 at 18:44, Sachidananda URS wrote: > Hi, > > gdeploy will have support for deploying geo-replication in the > upcoming RHGS 3.3.1 release. > The following features will be supported: > This is an extensive list. Very nice to see gdeploy evolve to enable the fullest extent of geo-replication capability configuration. > * create (Secure and root user based deployments) > * failover > * failback > * start/stop/pause/delete sessions > * config (Configure geo-replication options) > * gluster-log-file > * gluster-log-level > * log-file > * log-level > * changelog-log-level > * ssh-command > * rsync-command > * use-tarssh > * volume-id > * timeout > * sync-jobs > * ignore-deletes > * checkpoint > * sync-acls > * sync-xattrs > * log-rsync-performance > * rsync-options > * use-meta-volume > > > Please find the attached example configuration files. They are self-explanatory. > Please let me know if you have any doubts. > > -sac From mbukatov at redhat.com Thu Aug 17 10:53:24 2017 From: mbukatov at redhat.com (Martin Bukatovic) Date: Thu, 17 Aug 2017 12:53:24 +0200 Subject: [Tendrl-devel] reopening github issues Message-ID: Dear Tednrl team, could you reconfigure Tendrl project on github so that out qe group (mbukatov, mkudlej, fbalak, ltilety and dahorak) can reopen github issues? Thank you. -- Martin Bukatovic USM QE team Red Hat From fbalak at redhat.com Mon Aug 21 13:07:52 2017 From: fbalak at redhat.com (Filip Balak) Date: Mon, 21 Aug 2017 09:07:52 -0400 (EDT) Subject: [Tendrl-devel] New version of API In-Reply-To: <943149658.140884.1503320328438.JavaMail.zimbra@redhat.com> Message-ID: <2083321193.144022.1503320872694.JavaMail.zimbra@redhat.com> Hi all, I am a little confused about the state of API and its change. I thought that with new Tendrl there will be a new API. I see issues https://github.com/Tendrl/api/issues/81 and https://github.com/Tendrl/documentation/issues/70 but I can not find any specifications or links in milestones which are concerned. Does anyone have any information related to this? Best Regards, ~Filip Balak From rkanade at redhat.com Thu Aug 24 19:50:16 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Fri, 25 Aug 2017 01:20:16 +0530 Subject: [Tendrl-devel] tendrl-release v1.5.1 (milestone-2) is available Message-ID: Hello, The Tendrl team is happy to present tendrl-release v1.5.1 (milestone-2) Summary: https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.5.1-(summary) Install docs: https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.5.1-(install-guide) Metrics: https://github.com/Tendrl/documentation/wiki/Metrics Cheers!