From mbukatov at redhat.com Mon Oct 2 11:50:54 2017 From: mbukatov at redhat.com (Martin Bukatovic) Date: Mon, 2 Oct 2017 13:50:54 +0200 Subject: [Tendrl-devel] Running Tendrl with a secure etcd cluster In-Reply-To: References: Message-ID: <2b9e0a57-351c-c2d8-a6d0-d3e6534815e4@redhat.com> On 09/29/2017 05:59 AM, Sankarshan Mukhopadhyay wrote: > On Fri, Sep 29, 2017 at 1:09 AM, Rohan Kanade wrote: >> I wrote up a guide and some PRs to enable TLS cert support etcd for Tendrl >> services. Please try it out and provide feedback >> >> https://github.com/Tendrl/documentation/wiki/Tendrl-with-a-secure-etcd-cluster >> > > Thanks Rohan! > > Martin - would these be sufficient for you to work with on > tendrl-ansible? The context for the question is your notes about > tendrl-ansible from a few days back. Yes, this looks good enough for me to start working on this. I will ask for additional details as I go. -- Martin Bukatovic USM QE team Red Hat From mbukatov at redhat.com Mon Oct 2 11:56:14 2017 From: mbukatov at redhat.com (Martin Bukatovic) Date: Mon, 2 Oct 2017 13:56:14 +0200 Subject: [Tendrl-devel] Running Tendrl with a secure etcd cluster In-Reply-To: References: Message-ID: <37c2d2fd-3da8-81c8-ddfe-cd558e0156af@redhat.com> On 09/28/2017 09:39 PM, Rohan Kanade wrote: > I wrote up a guide and some PRs to enable TLS cert support etcd for > Tendrl services. Please try it out and provide feedback > > https://github.com/Tendrl/documentation/wiki/Tendrl-with-a-secure-etcd-cluster Thanks for the write up. I will start working on this today or tomorrow and update my status in this tendrl-ansible issue: https://github.com/Tendrl/tendrl-ansible/issues/42 -- Martin Bukatovic USM QE team Red Hat From mbukatov at redhat.com Mon Oct 2 17:22:40 2017 From: mbukatov at redhat.com (Martin Bukatovic) Date: Mon, 2 Oct 2017 19:22:40 +0200 Subject: [Tendrl-devel] selinux policies for tendrl Message-ID: <6ace36a2-796c-ef1d-4549-b1bd47eb5428@redhat.com> Dear all, I have rechecked current status of SELinux support and noticed organizational issues, which bite us a bit already and will be even more painful in a future if not addressed now. Right now, we have selinux policies stored in 2 different unrelated repositories. Moreover we have policies both for tendrl itself and for 3rd party components, of which some are covered in system selinux-policy packages and some are not. For this reason, I propose this: * create new tendrl repository tendrl-selinux * migrate all selinux code from tendrl-api and tendrl-gluster-integration into this new repository * remove selinux subpackages from tendrl-api and tendrl-gluster-integration spec file * create a single selinux only specfile in tendrl-selinux repo * address filename conflict of a tendrl selinux policy (we have different policy for both server and node, but it's name is the same) This way, it would be much easier to validate, report issues and maintain SELinux support for tendrl. I haven't created any issue for this, as the work here requires a cooperation within multiple repositories and so there is no natural place to create a master/tracking issue for it. We could discuss this on tendrl-dev meeting on Tue and create issues to track work required for this after the discussion. -- Martin Bukatovic USM QE team Red Hat From mkudlej at redhat.com Thu Oct 5 08:31:59 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Thu, 5 Oct 2017 10:31:59 +0200 Subject: [Tendrl-devel] Public ssh keys at Github Message-ID: Hi all, I would like just point out that it will speed up sharing of testing environments if people share their public keys like Rohan does https://github.com/r0h4n.keys Thank you! -- 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 dahorak at redhat.com Mon Oct 9 10:30:48 2017 From: dahorak at redhat.com (=?UTF-8?Q?Daniel_Hor=c3=a1k?=) Date: Mon, 9 Oct 2017 12:30:48 +0200 Subject: [Tendrl-devel] QE infrastructure change, possible delay about 1 day Message-ID: <7105890f-31f2-d649-b017-6620f15bee5e@redhat.com> Hi all, There will be quite big QE HW infrastructure change (out of our control) sometime in the next days, which might affect our testing and delay some QE activities about 1-2 days. Regards, Daniel From rkanade at redhat.com Wed Oct 11 19:10:44 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Thu, 12 Oct 2017 00:40:44 +0530 Subject: [Tendrl-devel] tendrl-release v1.5.3 (bugfixes) is available Message-ID: Hello, The Tendrl team is happy to present tendrl-release v1.5.3 (bugfixes) Install docs: https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.5.3-(install-guide) Metrics: https://github.com/Tendrl/documentation/wiki/Metrics From mbukatov at redhat.com Thu Oct 12 18:16:44 2017 From: mbukatov at redhat.com (Martin Bukatovic) Date: Thu, 12 Oct 2017 20:16:44 +0200 Subject: [Tendrl-devel] tendrl-selinux Message-ID: <7e4c18e1-9295-ffc4-577b-872372333298@redhat.com> Dear tendrl devel list, I have finished work on tendrl-selinux, so that repository https://github.com/mbukatov/tendrl-selinux is ready to be inspected by tendrl team and transferred into Tendrl organization. Besides that, we would need to enable rpm builds on the new repository. Related pull requests (removing selinux code from other repositories): * https://github.com/Tendrl/api/pull/321 * https://github.com/Tendrl/gluster-integration/pull/443 This work fixes the following problems: * https://github.com/Tendrl/api/issues/291 * https://github.com/Tendrl/gluster-integration/issues/424 * https://ci.centos.org/view/tendrl-build-master/job/tendrl-pkgval-2-master-rpmdeplint/lastCompletedBuild/testReport/usmqe_tests.rpm/test_rpm/test_rpmdeplint_tendrl_server_selinux_check_conflicts_/ * having SELinux policies in 2 unrelated repositories makes maintenance and auditing harder * it was hard to find a proper place to report SELinux issues, as the selinux code was hidden Moreover I: * merged tendrl server and tendrl node policies into singe one, based on suggestion from Luk?? Vrabec of SELinux team * rewrote the specfile from scratch based on fedora wikipage https://fedoraproject.org/wiki/SELinux/IndependentPolicy#Creating_the_Spec_File -- Martin Bukatovic USM QE team Red Hat From rkanade at redhat.com Fri Oct 13 07:29:09 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Fri, 13 Oct 2017 12:59:09 +0530 Subject: [Tendrl-devel] tendrl-selinux In-Reply-To: <7e4c18e1-9295-ffc4-577b-872372333298@redhat.com> References: <7e4c18e1-9295-ffc4-577b-872372333298@redhat.com> Message-ID: Thanks for getting this done Martin. I have created the repo after review https://github.com/Tendrl/tendrl-selinux Also, tracking issue for rpm builds on above repo is https://github.com/Tendrl/tendrl-ci/issues/3 On Thu, Oct 12, 2017 at 11:46 PM, Martin Bukatovic wrote: > Dear tendrl devel list, > > I have finished work on tendrl-selinux, so that repository > > https://github.com/mbukatov/tendrl-selinux > > is ready to be inspected by tendrl team and transferred into Tendrl > organization. Besides that, we would need to enable rpm builds on > the new repository. > > Related pull requests (removing selinux code from other repositories): > > * https://github.com/Tendrl/api/pull/321 > * https://github.com/Tendrl/gluster-integration/pull/443 > > This work fixes the following problems: > > * https://github.com/Tendrl/api/issues/291 > * https://github.com/Tendrl/gluster-integration/issues/424 > * > https://ci.centos.org/view/tendrl-build-master/job/tendrl-pkgval-2-master- > rpmdeplint/lastCompletedBuild/testReport/usmqe_tests.rpm/ > test_rpm/test_rpmdeplint_tendrl_server_selinux_check_conflicts_/ > * having SELinux policies in 2 unrelated repositories > makes maintenance and auditing harder > * it was hard to find a proper place to report SELinux issues, as > the selinux code was hidden > > Moreover I: > > * merged tendrl server and tendrl node policies into singe > one, based on suggestion from Luk?? Vrabec of SELinux team > * rewrote the specfile from scratch based on fedora wikipage > > https://fedoraproject.org/wiki/SELinux/IndependentPolicy#Creating_ > the_Spec_File > > -- > Martin Bukatovic > USM QE team > Red Hat > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > From mkudlej at redhat.com Tue Oct 17 07:02:25 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Tue, 17 Oct 2017 09:02:25 +0200 Subject: [Tendrl-devel] ncurses ceph installator Message-ID: Hi, Martin has showed me one of Paul's interesting project, see https://github.com/pcuzner/ceph-ansible-copilot -- 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 at redhat.com Tue Oct 17 07:04:04 2017 From: sankarshan at redhat.com (sankarshan) Date: Tue, 17 Oct 2017 12:34:04 +0530 Subject: [Tendrl-devel] ncurses ceph installator In-Reply-To: References: Message-ID: On 17 October 2017 at 12:32, Martin Kudlej wrote: > Martin has showed me one of Paul's interesting project, see > https://github.com/pcuzner/ceph-ansible-copilot Aside from the ncurses based method, what are your observations which can be useful from an end-user install experience? From ndevos at redhat.com Wed Oct 18 10:42:46 2017 From: ndevos at redhat.com (Niels de Vos) Date: Wed, 18 Oct 2017 12:42:46 +0200 Subject: [Tendrl-devel] Fwd: FOSDEM Call for Participation: Software Defined Storage devroom Message-ID: <20171018104246.GD2476@ndevos-x240.usersys.redhat.com> ----- Forwarded message from Jan Fajerski ----- > Date: Thu, 12 Oct 2017 12:55:28 +0200 > From: Jan Fajerski > To: ceph-devel at vger.kernel.org, ceph-users at ceph.com, gluster-users at gluster.org > Cc: devroom-managers at lists.fosdem.org, fosdem at lists.fosdem.org > Subject: [Gluster-users] FOSDEM Call for Participation: Software Defined Storage devroom > > > CfP for the Software Defined Storage devroom at FOSDEM 2018 > (Brussels, Belgium, February 4th). > > FOSDEM is a free software event that offers open source communities a place to > meet, share ideas and collaborate. It is renown for being highly developer- > oriented and brings together 8000+ participants from all over the world. It > is held in the city of Brussels (Belgium). > > FOSDEM 2018 will take place during the weekend of February 3rd-4th 2018. More > details about the event can be found at http://fosdem.org/ > > ** Call For Participation > > The Software Defined Storage devroom will go into it's second round for > talks around Open Source Software Defined Storage projects, management tools > and real world deployments. > > Presentation topics could include but are not limited too: > > - Your work on a SDS project like Ceph, GlusterFS or LizardFS > > - Your work on or with SDS related projects like SWIFT or Container Storage > Interface > > - Management tools for SDS deployments > > - Monitoring tools for SDS clusters > > ** Important dates: > > - 26 Nov 2017: submission deadline for talk proposals > - 15 Dec 2017: announcement of the final schedule > - 4 Feb 2018: Software Defined Storage dev room > > Talk proposals will be reviewed by a steering committee: > - Leonardo Vaz (Ceph Community Manager - Red Hat Inc.) > - Joao Luis (Core Ceph contributor - SUSE) > - Jan Fajerski (Ceph Developer - SUSE) > > Use the FOSDEM 'pentabarf' tool to submit your proposal: > https://penta.fosdem.org/submission/FOSDEM18 > > - If necessary, create a Pentabarf account and activate it. > Please reuse your account from previous years if you have > already created it. > > - In the "Person" section, provide First name, Last name > (in the "General" tab), Email (in the "Contact" tab) > and Bio ("Abstract" field in the "Description" tab). > > - Submit a proposal by clicking on "Create event". > > - Important! Select the "Software Defined Storage devroom" track > (on the "General" tab). > > - Provide the title of your talk ("Event title" in the "General" tab). > > - Provide a description of the subject of the talk and the > intended audience (in the "Abstract" field of the "Description" tab) > > - Provide a rough outline of the talk or goals of the session (a short > list of bullet points covering topics that will be discussed) in the > "Full description" field in the "Description" tab > > - Provide an expected length of your talk in the "Duration" field. Please > count at least 10 minutes of discussion into your proposal. > > Suggested talk length would be 15, 20+10, 30+15, and 45+15 minutes. > > ** Recording of talks > > The FOSDEM organizers plan to have live streaming and recording fully working, > both for remote/later viewing of talks, and so that people can watch streams > in the hallways when rooms are full. This requires speakers to consent to > being recorded and streamed. If you plan to be a speaker, please understand > that by doing so you implicitly give consent for your talk to be recorded and > streamed. The recordings will be published under the same license as all > FOSDEM content (CC-BY). > > Hope to hear from you soon! And please forward this announcement. > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-users ----- End forwarded message ----- From kdreyer at redhat.com Mon Oct 23 15:11:43 2017 From: kdreyer at redhat.com (Ken Dreyer) Date: Mon, 23 Oct 2017 09:11:43 -0600 Subject: [Tendrl-devel] ncurses ceph installator In-Reply-To: References: Message-ID: Really interesting, thanks for sharing Martin. - Ken On Tue, Oct 17, 2017 at 1:04 AM, sankarshan wrote: > On 17 October 2017 at 12:32, Martin Kudlej wrote: > >> Martin has showed me one of Paul's interesting project, see >> https://github.com/pcuzner/ceph-ansible-copilot > > Aside from the ncurses based method, what are your observations which > can be useful from an end-user install experience? > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel From negupta at redhat.com Tue Oct 24 10:29:00 2017 From: negupta at redhat.com (Neha Gupta) Date: Tue, 24 Oct 2017 15:59:00 +0530 Subject: [Tendrl-devel] Please verify all pending github issues Message-ID: Hi, There are around 18 UI github issues[1] which are in pending verification state. Request all the issue owners to verify and close it, if resolved. [1] https://github.com/Tendrl/ui/labels/pending%20verification Thanks, Neha From sankarshan.mukhopadhyay at gmail.com Wed Oct 25 13:36:57 2017 From: sankarshan.mukhopadhyay at gmail.com (Sankarshan Mukhopadhyay) Date: Wed, 25 Oct 2017 19:06:57 +0530 Subject: [Tendrl-devel] Fwd: [Gluster-devel] Gluster Health Report tool In-Reply-To: <1fe74f0e-64e7-2f26-a323-fb5bc09c37bb@redhat.com> References: <1fe74f0e-64e7-2f26-a323-fb5bc09c37bb@redhat.com> Message-ID: ---------- Forwarded message ---------- From: Aravinda Date: Wed, Oct 25, 2017 at 5:41 PM Subject: [Gluster-devel] Gluster Health Report tool To: Gluster Devel , gluster-users Hi, We started a new project to identify issues/misconfigurations in Gluster nodes. This project is very young and not yet ready for Production use, Feedback on the existing reports and ideas for more Reports are welcome. This tool needs to run in every Gluster node to detect the local issues (Example: Parsing log files, checking disk space etc) in each Nodes. But some of the reports use Gluster CLI to identify the issues Which can be run in any one node.(For example `gluster-health-report --run-only glusterd-peer-disconnect`) # Install sudo pip install gluster-health-report # Usage Run `gluster-health-report --help` for help gluster-health-report Example output is available here https://github.com/aravindavk/gluster-health-report # Project Details - Issue page: https://github.com/gluster/glusterfs/issues/313 - Project page: https://github.com/aravindavk/gluster-health-report - Open new issue if you have new report suggestion or found issue with existing report https://github.com/aravindavk/gluster-health-report/issues -- regards Aravinda VK _______________________________________________ Gluster-devel mailing list Gluster-devel at gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel -- sankarshan mukhopadhyay From mkudlej at redhat.com Thu Oct 26 12:47:40 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Thu, 26 Oct 2017 14:47:40 +0200 Subject: [Tendrl-devel] where are QE on this Friday? Message-ID: <114d2baa-43cc-ef49-b008-c3a48f56812a@redhat.com> Hi all, whole QE team will attend tomorrow and on Saturday Gluster Summit 2017. We will most probably just check emails and we will not be connected to Gitter. Please send us email in case of any need or physically ping us during summit. I'm looking forward to meet our colleagues on summit. -- 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