From rkanade at redhat.com Sat Apr 1 03:04:53 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Sat, 1 Apr 2017 08:34:53 +0530 Subject: [Tendrl-devel] Tendrl release v1.2.2 (beta-1) In-Reply-To: References: Message-ID: Happy to announce the first beta builds for Tendrl components (API, Core) Rpms (install latest): https://copr.fedorainfracloud.org/coprs/tendrl/tendrl/ Create Cluster Tendrl API prerequisites: https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.2.2 Note: tendrl-dashboard, tendrl-performance-monitoring and tendrl-alerting are under integration testing. Will be released soon. From mkudlej at redhat.com Mon Apr 3 06:39:04 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Mon, 3 Apr 2017 08:39:04 +0200 Subject: [Tendrl-devel] Tendrl release v1.2.2 (beta-1) In-Reply-To: References: Message-ID: <497cda0a-ba46-ca23-6f50-33797ca3210f@redhat.com> Hi Rohan, On 04/01/2017 05:04 AM, Rohan Kanade wrote: > Happy to announce the first beta builds for Tendrl components (API, Core) > > Rpms (install latest): > https://copr.fedorainfracloud.org/coprs/tendrl/tendrl/ > > Create Cluster Tendrl API prerequisites: > https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.2.2 Is install documentation update? https://github.com/Tendrl/documentation/wiki/Tendrl-Package-Installation-Reference -- 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 Mon Apr 3 07:02:56 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Mon, 3 Apr 2017 12:32:56 +0530 Subject: [Tendrl-devel] Tendrl release v1.2.2 (beta-1) In-Reply-To: References: <497cda0a-ba46-ca23-6f50-33797ca3210f@redhat.com> Message-ID: Hi Martin, Thanks for trying out the new release. If you've encountered issues in the install document. Please file these issues on the Tendrl/documentation repo On 03-Apr-2017 12:09, "Martin Kudlej" wrote: Hi Rohan, On 04/01/2017 05:04 AM, Rohan Kanade wrote: > Happy to announce the first beta builds for Tendrl components (API, Core) > > Rpms (install latest): > https://copr.fedorainfracloud.org/coprs/tendrl/tendrl/ > > Create Cluster Tendrl API prerequisites: > https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.2.2 > Is install documentation update? https://github.com/Tendrl/docu mentation/wiki/Tendrl-Package-Installation-Reference -- 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 _______________________________________________ Tendrl-devel mailing list Tendrl-devel at redhat.com https://www.redhat.com/mailman/listinfo/tendrl-devel From nthomas at redhat.com Mon Apr 3 08:19:14 2017 From: nthomas at redhat.com (Nishanth Thomas) Date: Mon, 3 Apr 2017 13:49:14 +0530 Subject: [Tendrl-devel] rpmlint errors and warnings (was: Initial package validation process) In-Reply-To: <727f4e47-7a1c-1e0f-f2f5-2f149f75e14d@redhat.com> References: <11f8aec4-457f-4b05-b791-876c7413a27b@redhat.com> <727f4e47-7a1c-1e0f-f2f5-2f149f75e14d@redhat.com> Message-ID: Thanks for raising this and for the efforts. We will address this ASAP On Tue, Mar 28, 2017 at 5:03 PM, Daniel Hor?k wrote: > Hi, > as you might noticed, the dashboard[1] announced in previous email was > changed recently. > Firstly we have nice and clear dashboard. If it is not displayed correctly > on your screen, please tweak it yourself by the "Configure" button (it is > not possible to change this configuration globally, so you have to tweak it > for yourself). > Also I've changed the jobs names to be slightly more clear and I'll add > additional test steps later. > > The main point of this email is the list of failing rpmlint checks[2]. > There are lot's of errors and warnings from rpmlint nearly for each > package in the tendrl repo. > We consider all those issues serious enoght to be looked into. Even when > the warning looks insignificant, it could be caused by serious error and > for this reason, we think it's necessary to look into every error reported > there and find out what caused it and act based on that. The current state > of packaging is not good, definitelly dont matching fedora requirements we > target. > Could you please review those issues and fix what's possible to fix? We > will report github issue for each meaningful warning/error later, but the > list is quite huge and some of the issues might be fixed easily without > unnecessary paperwork. > > [1] https://ci.centos.org/view/Tendrl/ > [2] https://ci.centos.org/view/Tendrl/job/tendrl-0-1-package-val > idation-rpmlint/lastCompletedBuild/testReport/ > > Thanks, > Daniel > > On 03/23/17 21:50, Daniel Hor?k wrote: > >> Hello All, >> >> thanks to Martin B., we have initial version of package validation >> process. >> >> Now it consists from following two jobs in CentOS CI[1]: >> >> Tendrl0 - 2 - package-validation - Test RPMs >> Tendrl0 - 3 - package-validation - Test Installation >> >> (The ambient jobs "Tendrl0 - 1..." and "Tendrl0 - X..." are just >> auxiliary jobs - setup and teardown of the test environment.) >> >> The "Test RPMs"[2] job performs repoclosure for whole tendrl[3] >> repository and rpmlint and rpmdeplint for each tendrl-* package. >> >> As you can see, there are failures in the Test Result - all of them are >> now from rpmlint warnings and errors. >> >> The "Test Installation"[4] job tries to install and uninstall each >> tendrl-* package (nothing else). >> >> Hopefully in the near future, we will be able to add more steps to the >> validation process and also we will have nicer and clearer dashboard. >> >> [1] https://ci.centos.org/view/Tendrl/ >> [2] >> https://ci.centos.org/view/Tendrl/job/tendrl0-2-package-vali >> dation-test-rpm/ >> >> [3] >> https://copr-be.cloud.fedoraproject.org/results/tendrl/ >> tendrl/epel-7-x86_64/ >> >> [4] >> https://ci.centos.org/view/Tendrl/job/tendrl0-3-package-vali >> dation-test-install/ >> >> >> Regards, >> Daniel >> >> _______________________________________________ >> Tendrl-devel mailing list >> Tendrl-devel at redhat.com >> https://www.redhat.com/mailman/listinfo/tendrl-devel >> > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > From rkanade at redhat.com Mon Apr 3 10:48:00 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Mon, 3 Apr 2017 16:18:00 +0530 Subject: [Tendrl-devel] Improved Github workflow/branching for Tendrl components In-Reply-To: References: Message-ID: On Fri, Mar 17, 2017 at 7:08 PM, Martin Bukatovic wrote: > Dear all, > > On 03/14/2017 02:36 PM, Rohan Kanade wrote: > > Over the last release (1.2.1) we ran into issues related to > async/parallel > > development and we broke a few things here and there while trying to sort > > out our branching model. > > > > Here is what we should be doing to enable better categorization of code > > coming in Tendrl > > > > Branch > > 1) Master == production ready code (This code should be tested via all > > functional/regression/integration tests) > > > > 2) Develop == feature ready code (This code should be regularly tested > > functionally) > > > > 3) Feature branches == span across components (eg node-agent, commons > etc) > > and contain code for a that $Feature (these branches should be tested > > functionally and moved to develop once done) > > > > 4) Hotfixes == Any fixes required in the production code (master) branch > > should go to hotfix branches and should be merged back to master and > develop > > > > The Tendrl backend repositories have been updated to reflect above > branches. > > > > Id like to request the tendrl-api and the tendrl-dashboard to incorporate > > these too. > > > > More details on how this works out with examples : > > > > http://nvie.com/posts/a-successful-git-branching-model/ > > I have few questions: > > 1) Do you plan to follow the branching model from nvie.com entirely? > I'm asking because the model is quite specific about what each branch > means and what could be branched from and into. > Yes, only exception is that our "release/$version" branches will be permanent > > 2) The follow up question: if we plan to follow the nvie.com model > entirely, do we have some plan for transition period to get there? > > The Tendrl core, api, monitoring/alerting have already transitioned, you can reach out to those individuals for more help. > 3) The branching model describes feature branches as a private branch > of some developer. Does it fit our model of work? I'm asking because > it's not clear to me how would 2 or more people work on a single > feature. > > There are multiple ways to do this: > > * branching model from nvie.com doesn't allow 2 or more people to > work on a single feature/branch - all branches are on the same > level and for this to work, it's better if the branches are more > or less independent of each other > * "a maintainer/gatekeeper model" when one person maintains some > feature branch and other people, if they need to work on this > feature as well work with this maintainer on his branch. > Tendrl feature branches can have PRs from any contributor, contributors can also maintain these feature branches in their own forks. I dont see a problem here. > > 4) Would we allow branching from and into feature branches or do we > plan to follow linear history there via rebases? This is kind of > related to previous question. > > We do not allow branching from feature branches, feature branches will be made outta develop branch, check my comment on #3, let me know if more discussion required on this. > 5) I see one risk related to parallel development in feature branches. > When there are multiple such branches open, it's possible that all the > branches starts to conflict with each other after some time and so it > would be harder to integrated them together when merging back into > develop. What is our strategy related to this issue? This is related > to question #3. > I agree, we need to focus on ensuring we break down any requirement into these 1) Refactoring: If a new feature requires refactoring (independent of the new feature) of the old code (bug fixes, design fixes, data model fixes etc) before the actual feature can be coded, these changes need to go in directly on the develop branch. 2) Feature: Once above changes are identified and merged in develop, the contributor can then focus on his feature branch by rebasing with develop > > 6) Do we plan to clarify delegation of responsibilities wrt new model, > eg. who is going to be a gatekeeper for merging feature branch into > develop, who would do the merge of develop into master? And so on. > > The team "@Tendrl/tendrl-core" (can be used to mention on github) will be responsible for this. > Thank you all for being patient with me and (maybe) too obvious > questions, I'm guessing you have already figured out at least half > of the details I'm asking about here. I'm just trying to be on the > same page with you. > -- > Martin Bukatovic > USM QE team > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > From mkudlej at redhat.com Mon Apr 3 11:18:39 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Mon, 3 Apr 2017 13:18:39 +0200 Subject: [Tendrl-devel] Tendrl release v1.2.2 (beta-1) In-Reply-To: References: <497cda0a-ba46-ca23-6f50-33797ca3210f@redhat.com> Message-ID: <459017c4-3978-c847-d54b-2e38e92e5ad5@redhat.com> Hi Rohan, On 04/03/2017 09:02 AM, Rohan Kanade wrote: > Thanks for trying out the new release. If you've encountered issues in the > install document. Please file these issues on the Tendrl/documentation repo issue is already there https://github.com/Tendrl/documentation/issues/77 I've just add comment for Tendrl 1.2.2 -- 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 mkudlej at redhat.com Mon Apr 3 12:00:35 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Mon, 3 Apr 2017 14:00:35 +0200 Subject: [Tendrl-devel] Tendrl and ceph-installer in CentOS SIG's Koji In-Reply-To: References: Message-ID: Hi Ken, On 10/21/2016 03:02 AM, Ken Dreyer wrote: > Hi folks, > > I'd like to get Tendrl and ceph-installer packaged in the CentOS Storage SIG. > Is there ceph-installer in CentOS Storage SIG, please? I cannot find it. If no, what is your plan with it? 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 mkudlej at redhat.com Mon Apr 3 13:30:39 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Mon, 3 Apr 2017 15:30:39 +0200 Subject: [Tendrl-devel] Demo environment Message-ID: <09830eee-1ac3-9db4-b635-2fe75fd2f0d4@redhat.com> Hi all, once there is no blocker and there are all 1.2.2 packages ready we can provide environment for demo. Plan is to have cluster with CentOS 7: 1 node for API and Etcd 4 nodes with Gluster repository(for 4 node Gluster cluster) 7 nodes with Ceph repository(for Ceph cluster containing 3 monitors and 4 OSD nodes) Do you plan to do live demo or recorded one? In any case it will be great if there is record with *all* potential environment modifications between prepared environment and environment ready for demo. Then we can change our playbooks and file issues for documentation. Please send me public ssh keys of people who will do demo. -- 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 kdreyer at redhat.com Mon Apr 3 15:39:40 2017 From: kdreyer at redhat.com (Ken Dreyer) Date: Mon, 3 Apr 2017 09:39:40 -0600 Subject: [Tendrl-devel] Tendrl and ceph-installer in CentOS SIG's Koji In-Reply-To: References: Message-ID: On Mon, Apr 3, 2017 at 6:00 AM, Martin Kudlej wrote: > Is there ceph-installer in CentOS Storage SIG, please? I cannot find it. > If no, what is your plan with it? Unfortunately this has fallen so far down on my priority list that I probably won't do it in the next several months. - Ken From dahorak at redhat.com Mon Apr 3 16:38:27 2017 From: dahorak at redhat.com (=?UTF-8?Q?Daniel_Hor=c3=a1k?=) Date: Mon, 3 Apr 2017 18:38:27 +0200 Subject: [Tendrl-devel] Tendrl and ceph-installer in CentOS SIG's Koji In-Reply-To: References: Message-ID: <38323edd-a982-281f-b7f9-73ac9eda3ae2@redhat.com> Hi, I've tried to install ceph-ansible and ceph installer from following repos: https://shaman.ceph.com/api/repos/ceph-installer/master/latest/centos/7/noarch/noarch https://shaman.ceph.com/api/repos/ceph-ansible/master/latest/centos/7/noarch/noarch But there are following unmet requirements: python-pecan-notario python-tambo python-celery python-pecan >= 1 You can check the full output from `yum install ceph-installer` in attachment. Regards, Daniel On 04/03/17 17:39, Ken Dreyer wrote: > On Mon, Apr 3, 2017 at 6:00 AM, Martin Kudlej wrote: >> Is there ceph-installer in CentOS Storage SIG, please? I cannot find it. >> If no, what is your plan with it? > > Unfortunately this has fallen so far down on my priority list that I > probably won't do it in the next several months. > > - Ken > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > -------------- next part -------------- # yum install ceph-installer --enablerepo=epel Loaded plugins: fastestmirror ceph-ansible | 2.9 kB 00:00:00 ceph-installer | 2.9 kB 00:00:00 Loading mirror speeds from cached hostfile * base: ftp.cvut.cz * epel: download.eng.brq.redhat.com * extras: ftp.cvut.cz * updates: ftp.cvut.cz Resolving Dependencies --> Running transaction check ---> Package ceph-installer.noarch 0:1.2.2-23.g19ec4f5.el7 will be installed --> Processing Dependency: python-pecan >= 1 for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-notario >= 0.0.11 for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: ceph-ansible >= 2.0.0 for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-pecan-notario for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-sqlalchemy for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-tambo for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-celery for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: rabbitmq-server for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-gunicorn for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Running transaction check ---> Package ceph-ansible.noarch 0:2.2.0-0.rc1.65.g5ac0726.el7 will be installed ---> Package ceph-installer.noarch 0:1.2.2-23.g19ec4f5.el7 will be installed --> Processing Dependency: python-pecan >= 1 for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-pecan-notario for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-tambo for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-celery for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch ---> Package python-gunicorn.noarch 0:18.0-2.el7 will be installed ---> Package python-sqlalchemy.x86_64 0:0.9.8-2.el7 will be installed ---> Package python2-notario.noarch 0:0.0.11-2.el7 will be installed ---> Package rabbitmq-server.noarch 0:3.3.5-33.el7 will be installed --> Processing Dependency: erlang-xmerl >= R12B-3 for package: rabbitmq-server-3.3.5-33.el7.noarch --> Processing Dependency: erlang-tools >= R12B-3 for package: rabbitmq-server-3.3.5-33.el7.noarch --> Processing Dependency: erlang-stdlib >= R12B-3 for package: rabbitmq-server-3.3.5-33.el7.noarch --> Processing Dependency: erlang-ssl >= R12B-3 for package: rabbitmq-server-3.3.5-33.el7.noarch --> Processing Dependency: erlang-sasl >= R12B-3 for package: rabbitmq-server-3.3.5-33.el7.noarch --> Processing Dependency: erlang-public_key >= R12B-3 for package: rabbitmq-server-3.3.5-33.el7.noarch --> Processing Dependency: erlang-os_mon >= R12B-3 for package: rabbitmq-server-3.3.5-33.el7.noarch --> Processing Dependency: erlang-mnesia >= R12B-3 for package: rabbitmq-server-3.3.5-33.el7.noarch --> Processing Dependency: erlang-kernel >= R12B-3 for package: rabbitmq-server-3.3.5-33.el7.noarch --> Processing Dependency: erlang-erts >= R12B-3 for package: rabbitmq-server-3.3.5-33.el7.noarch --> Processing Dependency: erlang-sd_notify for package: rabbitmq-server-3.3.5-33.el7.noarch --> Running transaction check ---> Package ceph-installer.noarch 0:1.2.2-23.g19ec4f5.el7 will be installed --> Processing Dependency: python-pecan >= 1 for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-pecan-notario for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-tambo for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-celery for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch ---> Package erlang-erts.x86_64 0:R16B-03.18.el7 will be installed --> Processing Dependency: lksctp-tools for package: erlang-erts-R16B-03.18.el7.x86_64 ---> Package erlang-kernel.x86_64 0:R16B-03.18.el7 will be installed ---> Package erlang-mnesia.x86_64 0:R16B-03.18.el7 will be installed ---> Package erlang-os_mon.x86_64 0:R16B-03.18.el7 will be installed --> Processing Dependency: erlang-snmp(x86-64) = R16B-03.18.el7 for package: erlang-os_mon-R16B-03.18.el7.x86_64 --> Processing Dependency: erlang-otp_mibs(x86-64) = R16B-03.18.el7 for package: erlang-os_mon-R16B-03.18.el7.x86_64 ---> Package erlang-public_key.x86_64 0:R16B-03.18.el7 will be installed --> Processing Dependency: erlang-crypto(x86-64) = R16B-03.18.el7 for package: erlang-public_key-R16B-03.18.el7.x86_64 --> Processing Dependency: erlang-asn1(x86-64) = R16B-03.18.el7 for package: erlang-public_key-R16B-03.18.el7.x86_64 ---> Package erlang-sasl.x86_64 0:R16B-03.18.el7 will be installed ---> Package erlang-sd_notify.x86_64 0:0.1-1.el7 will be installed ---> Package erlang-ssl.x86_64 0:R16B-03.18.el7 will be installed ---> Package erlang-stdlib.x86_64 0:R16B-03.18.el7 will be installed --> Processing Dependency: erlang-compiler(x86-64) = R16B-03.18.el7 for package: erlang-stdlib-R16B-03.18.el7.x86_64 ---> Package erlang-tools.x86_64 0:R16B-03.18.el7 will be installed --> Processing Dependency: erlang-runtime_tools(x86-64) = R16B-03.18.el7 for package: erlang-tools-R16B-03.18.el7.x86_64 --> Processing Dependency: erlang-inets(x86-64) = R16B-03.18.el7 for package: erlang-tools-R16B-03.18.el7.x86_64 ---> Package erlang-xmerl.x86_64 0:R16B-03.18.el7 will be installed --> Running transaction check ---> Package ceph-installer.noarch 0:1.2.2-23.g19ec4f5.el7 will be installed --> Processing Dependency: python-pecan >= 1 for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-pecan-notario for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-tambo for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-celery for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch ---> Package erlang-asn1.x86_64 0:R16B-03.18.el7 will be installed ---> Package erlang-compiler.x86_64 0:R16B-03.18.el7 will be installed --> Processing Dependency: erlang-hipe(x86-64) = R16B-03.18.el7 for package: erlang-compiler-R16B-03.18.el7.x86_64 ---> Package erlang-crypto.x86_64 0:R16B-03.18.el7 will be installed ---> Package erlang-inets.x86_64 0:R16B-03.18.el7 will be installed ---> Package erlang-otp_mibs.x86_64 0:R16B-03.18.el7 will be installed ---> Package erlang-runtime_tools.x86_64 0:R16B-03.18.el7 will be installed ---> Package erlang-snmp.x86_64 0:R16B-03.18.el7 will be installed ---> Package lksctp-tools.x86_64 0:1.0.17-2.el7 will be installed --> Running transaction check ---> Package ceph-installer.noarch 0:1.2.2-23.g19ec4f5.el7 will be installed --> Processing Dependency: python-pecan >= 1 for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-pecan-notario for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-tambo for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-celery for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch ---> Package erlang-hipe.x86_64 0:R16B-03.18.el7 will be installed --> Processing Dependency: erlang-syntax_tools(x86-64) = R16B-03.18.el7 for package: erlang-hipe-R16B-03.18.el7.x86_64 --> Running transaction check ---> Package ceph-installer.noarch 0:1.2.2-23.g19ec4f5.el7 will be installed --> Processing Dependency: python-pecan >= 1 for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-pecan-notario for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-tambo for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch --> Processing Dependency: python-celery for package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch ---> Package erlang-syntax_tools.x86_64 0:R16B-03.18.el7 will be installed --> Finished Dependency Resolution Error: Package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch (ceph-installer) Requires: python-pecan-notario Error: Package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch (ceph-installer) Requires: python-tambo Error: Package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch (ceph-installer) Requires: python-celery Error: Package: ceph-installer-1.2.2-23.g19ec4f5.el7.noarch (ceph-installer) Requires: python-pecan >= 1 Available: python-pecan-0.4.5-2.el7.noarch (epel) python-pecan = 0.4.5-2.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest From kdreyer at redhat.com Mon Apr 3 17:45:53 2017 From: kdreyer at redhat.com (Ken Dreyer) Date: Mon, 3 Apr 2017 11:45:53 -0600 Subject: [Tendrl-devel] Tendrl and ceph-installer in CentOS SIG's Koji In-Reply-To: <38323edd-a982-281f-b7f9-73ac9eda3ae2@redhat.com> References: <38323edd-a982-281f-b7f9-73ac9eda3ae2@redhat.com> Message-ID: On Mon, Apr 3, 2017 at 10:38 AM, Daniel Hor?k wrote: > > But there are following unmet requirements: > python-pecan-notario > python-tambo > python-celery > python-pecan >= 1 You can install these from https://copr.fedorainfracloud.org/coprs/ktdreyer/ceph-installer/ as a workaround. - Ken From khartsoe at redhat.com Mon Apr 3 18:56:19 2017 From: khartsoe at redhat.com (Kenneth Hartsoe) Date: Mon, 3 Apr 2017 14:56:19 -0400 (EDT) Subject: [Tendrl-devel] Tendrl release v1.2.2 (beta-1) In-Reply-To: References: Message-ID: <671136336.8451253.1491245779871.JavaMail.zimbra@redhat.com> Hi Rohan, Can you direct me to the file/location where can I view installation error messages? Thanks. Ken Hartsoe Content Strategist Red Hat Storage Documentation khartsoe at redhat.com; IRC: khartsoe Office: 919 754 4770; Internal: 814 4770 ----- Original Message ----- | Happy to announce the first beta builds for Tendrl components (API, Core) | | Rpms (install latest): | https://copr.fedorainfracloud.org/coprs/tendrl/tendrl/ | | Create Cluster Tendrl API prerequisites: | https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.2.2 | | | Note: tendrl-dashboard, tendrl-performance-monitoring and tendrl-alerting | are under integration testing. Will be released soon. | _______________________________________________ | Tendrl-devel mailing list | Tendrl-devel at redhat.com | https://www.redhat.com/mailman/listinfo/tendrl-devel | From dahorak at redhat.com Tue Apr 4 06:59:19 2017 From: dahorak at redhat.com (=?UTF-8?Q?Daniel_Hor=c3=a1k?=) Date: Tue, 4 Apr 2017 08:59:19 +0200 Subject: [Tendrl-devel] Tendrl and ceph-installer in CentOS SIG's Koji In-Reply-To: References: <38323edd-a982-281f-b7f9-73ac9eda3ae2@redhat.com> Message-ID: Thanks Ken, it works well. Thanks, Daniel On 04/03/17 19:45, Ken Dreyer wrote: > On Mon, Apr 3, 2017 at 10:38 AM, Daniel Hor?k wrote: >> >> But there are following unmet requirements: >> python-pecan-notario >> python-tambo >> python-celery >> python-pecan >= 1 > > You can install these from > https://copr.fedorainfracloud.org/coprs/ktdreyer/ceph-installer/ as a > workaround. > > - Ken > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > From sankarshan.mukhopadhyay at gmail.com Tue Apr 4 08:14:23 2017 From: sankarshan.mukhopadhyay at gmail.com (Sankarshan Mukhopadhyay) Date: Tue, 4 Apr 2017 13:44:23 +0530 Subject: [Tendrl-devel] Tendrl release v1.2.2 (beta-1) In-Reply-To: <671136336.8451253.1491245779871.JavaMail.zimbra@redhat.com> References: <671136336.8451253.1491245779871.JavaMail.zimbra@redhat.com> Message-ID: On Tue, Apr 4, 2017 at 12:26 AM, Kenneth Hartsoe wrote: > Can you direct me to the file/location where can I view installation error messages? Thanks. Ken, I am a bit puzzled. What installation error messages would these be? The logs are available at /var/log/tendrl, but I have a feeling that's not what you are asking about. -- sankarshan mukhopadhyay From ltrilety at redhat.com Tue Apr 4 10:40:31 2017 From: ltrilety at redhat.com (Lubos Trilety) Date: Tue, 4 Apr 2017 06:40:31 -0400 (EDT) Subject: [Tendrl-devel] Improved Github workflow/branching for Tendrl components In-Reply-To: References: Message-ID: <990862554.20124747.1491302431625.JavaMail.zimbra@redhat.com> Hi Rohan, Thanks for answering, however I have several doubts: 1. You said that we will follow completely http://nvie.com/posts/a-successful-git-branching-model/ model and Tendrl core, api, monitoring/alerting have already transitioned to this model. So lets see on the definition of feature branches: Feature branches (or sometimes called topic branches) are used to develop new features for the upcoming or a distant future release. When starting development of a feature, the target release in which this feature will be incorporated may well be unknown at that point. The essence of a feature branch is that it exists as long as the feature is in development, but will eventually be merged back into develop (to definitely add the new feature to the upcoming release) or discarded (in case of a disappointing experiment). When I look to e.g. performance-monitoring, I don't see any feature branch there. There were a lot of branches with fixes, which goes to develop branch, but that's not what feature branch should look like. In 'A successful Git branching model' fixes are made for feature branches or if needed they go directly to develop branch e.g. using fast forward merges, no additional branches are shown in graphs. Anyway the most work is done in those feature branches. Please don't take me wrong here, I am not saying that current approach is bad only that's not how it is defined in 'A successful Git branching model'. Hence we cannot say that we are following the model completely. 2. First I'll cite something from your answer, so it will be clear what I am referring to. Citations: """ Tendrl feature branches can have PRs from any contributor, contributors can also maintain these feature branches in their own forks. I dont see a problem here. """ and """ We do not allow branching from feature branches, feature branches will be made outta develop branch, check my comment on #3, let me know if more discussion required on this. """ But if we will be doing pull request for feature branches then we have to create a branch from those branches. In other words if we allow PRs then we will allow branching of feature branches. So I am a little confused here. 3. About 'Refactoring' and 'Feature' points, I have very similar doubt as the previous one. If we want to follow the model, 'Refactoring' part has to be done using fast forward merges only. Sorry for bothering you. It's just I see some discrepancies, however I could be wrong. Lubos ----- Original Message ----- From: "Rohan Kanade" To: "Mailing list for the contributors to the Tendrl project" Sent: Monday, April 3, 2017 12:48:00 PM Subject: Re: [Tendrl-devel] Improved Github workflow/branching for Tendrl components On Fri, Mar 17, 2017 at 7:08 PM, Martin Bukatovic wrote: > Dear all, > > On 03/14/2017 02:36 PM, Rohan Kanade wrote: > > Over the last release (1.2.1) we ran into issues related to > async/parallel > > development and we broke a few things here and there while trying to sort > > out our branching model. > > > > Here is what we should be doing to enable better categorization of code > > coming in Tendrl > > > > Branch > > 1) Master == production ready code (This code should be tested via all > > functional/regression/integration tests) > > > > 2) Develop == feature ready code (This code should be regularly tested > > functionally) > > > > 3) Feature branches == span across components (eg node-agent, commons > etc) > > and contain code for a that $Feature (these branches should be tested > > functionally and moved to develop once done) > > > > 4) Hotfixes == Any fixes required in the production code (master) branch > > should go to hotfix branches and should be merged back to master and > develop > > > > The Tendrl backend repositories have been updated to reflect above > branches. > > > > Id like to request the tendrl-api and the tendrl-dashboard to incorporate > > these too. > > > > More details on how this works out with examples : > > > > http://nvie.com/posts/a-successful-git-branching-model/ > > I have few questions: > > 1) Do you plan to follow the branching model from nvie.com entirely? > I'm asking because the model is quite specific about what each branch > means and what could be branched from and into. > Yes, only exception is that our "release/$version" branches will be permanent > > 2) The follow up question: if we plan to follow the nvie.com model > entirely, do we have some plan for transition period to get there? > > The Tendrl core, api, monitoring/alerting have already transitioned, you can reach out to those individuals for more help. > 3) The branching model describes feature branches as a private branch > of some developer. Does it fit our model of work? I'm asking because > it's not clear to me how would 2 or more people work on a single > feature. > > There are multiple ways to do this: > > * branching model from nvie.com doesn't allow 2 or more people to > work on a single feature/branch - all branches are on the same > level and for this to work, it's better if the branches are more > or less independent of each other > * "a maintainer/gatekeeper model" when one person maintains some > feature branch and other people, if they need to work on this > feature as well work with this maintainer on his branch. > Tendrl feature branches can have PRs from any contributor, contributors can also maintain these feature branches in their own forks. I dont see a problem here. > > 4) Would we allow branching from and into feature branches or do we > plan to follow linear history there via rebases? This is kind of > related to previous question. > > We do not allow branching from feature branches, feature branches will be made outta develop branch, check my comment on #3, let me know if more discussion required on this. > 5) I see one risk related to parallel development in feature branches. > When there are multiple such branches open, it's possible that all the > branches starts to conflict with each other after some time and so it > would be harder to integrated them together when merging back into > develop. What is our strategy related to this issue? This is related > to question #3. > I agree, we need to focus on ensuring we break down any requirement into these 1) Refactoring: If a new feature requires refactoring (independent of the new feature) of the old code (bug fixes, design fixes, data model fixes etc) before the actual feature can be coded, these changes need to go in directly on the develop branch. 2) Feature: Once above changes are identified and merged in develop, the contributor can then focus on his feature branch by rebasing with develop > > 6) Do we plan to clarify delegation of responsibilities wrt new model, > eg. who is going to be a gatekeeper for merging feature branch into > develop, who would do the merge of develop into master? And so on. > > The team "@Tendrl/tendrl-core" (can be used to mention on github) will be responsible for this. > Thank you all for being patient with me and (maybe) too obvious > questions, I'm guessing you have already figured out at least half > of the details I'm asking about here. I'm just trying to be on the > same page with you. > -- > Martin Bukatovic > USM QE team > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > _______________________________________________ Tendrl-devel mailing list Tendrl-devel at redhat.com https://www.redhat.com/mailman/listinfo/tendrl-devel From khartsoe at redhat.com Tue Apr 4 11:36:03 2017 From: khartsoe at redhat.com (Kenneth Hartsoe) Date: Tue, 4 Apr 2017 07:36:03 -0400 (EDT) Subject: [Tendrl-devel] Tendrl release v1.2.2 (beta-1) In-Reply-To: References: <671136336.8451253.1491245779871.JavaMail.zimbra@redhat.com> Message-ID: <218911782.8689573.1491305763434.JavaMail.zimbra@redhat.com> Hi Sankarshan, Sorry for the confusion :-) basically, when a customer goes through install, we would like to see what messages will display should something fail; the idea being that there might be some common scenario(s) that we can provide a brief solution for, as a verification step, etc. Ken Hartsoe Content Strategist Red Hat Storage Documentation khartsoe at redhat.com; IRC: khartsoe Office: 919 754 4770; Internal: 814 4770 ----- Original Message ----- | On Tue, Apr 4, 2017 at 12:26 AM, Kenneth Hartsoe wrote: | > Can you direct me to the file/location where can I view installation error | > messages? Thanks. | | Ken, I am a bit puzzled. What installation error messages would these | be? The logs are available at /var/log/tendrl, but I have a feeling | that's not what you are asking about. | | | -- | sankarshan mukhopadhyay | | | _______________________________________________ | Tendrl-devel mailing list | Tendrl-devel at redhat.com | https://www.redhat.com/mailman/listinfo/tendrl-devel | From rghatvis at redhat.com Tue Apr 4 11:36:06 2017 From: rghatvis at redhat.com (Bobb Gt) Date: Tue, 4 Apr 2017 17:06:06 +0530 Subject: [Tendrl-devel] Tendrl release v1.2.2 (beta-1) In-Reply-To: References: <671136336.8451253.1491245779871.JavaMail.zimbra@redhat.com> Message-ID: Hey Sankarshan, We are trying to gather some error messages resulting out of package installation. The objective is to compile the error messages in the "Troubleshooting section" of the Console 3.0 Admin Guide with the respective resolution/workaround, if available. Bobb [image: photo] Bobb GT Technical Writer, Red Hat Inc Mobile: +91 8411001236 Website: redhat.com Division: Customer Content Services APAC Get a signature like this: Click here! On Tue, Apr 4, 2017 at 1:44 PM, Sankarshan Mukhopadhyay < sankarshan.mukhopadhyay at gmail.com> wrote: > On Tue, Apr 4, 2017 at 12:26 AM, Kenneth Hartsoe > wrote: > > Can you direct me to the file/location where can I view installation > error messages? Thanks. > > Ken, I am a bit puzzled. What installation error messages would these > be? The logs are available at /var/log/tendrl, but I have a feeling > that's not what you are asking about. > > > -- > sankarshan mukhopadhyay > > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > From sankarshan at redhat.com Tue Apr 4 11:39:14 2017 From: sankarshan at redhat.com (sankarshan) Date: Tue, 4 Apr 2017 17:09:14 +0530 Subject: [Tendrl-devel] Tendrl release v1.2.2 (beta-1) In-Reply-To: <218911782.8689573.1491305763434.JavaMail.zimbra@redhat.com> References: <671136336.8451253.1491245779871.JavaMail.zimbra@redhat.com> <218911782.8689573.1491305763434.JavaMail.zimbra@redhat.com> Message-ID: On 4 April 2017 at 17:06, Kenneth Hartsoe wrote: > Sorry for the confusion :-) basically, when a customer goes through install, we would like to see what messages will display should something fail; the idea being that there might be some common scenario(s) that we can provide a brief solution for, as a verification step, etc. > Aha! Alright - so would these be like the information messages/warnings/tips which are also included as part of the UX designs? From khartsoe at redhat.com Tue Apr 4 12:03:02 2017 From: khartsoe at redhat.com (Kenneth Hartsoe) Date: Tue, 4 Apr 2017 08:03:02 -0400 (EDT) Subject: [Tendrl-devel] Tendrl release v1.2.2 (beta-1) In-Reply-To: References: <671136336.8451253.1491245779871.JavaMail.zimbra@redhat.com> <218911782.8689573.1491305763434.JavaMail.zimbra@redhat.com> Message-ID: <423213423.8697385.1491307382991.JavaMail.zimbra@redhat.com> Hi Sankarshan, These are not UX related: the messages/output we are looking for are in regard to installing the packages. For example, after installing the packages (i.e. RHSCON API, Dashboard, etc.), when successful, the user sees this: The packages and dependencies are successfully installed as shown in the following example CLI output. Installed: rhscon-dashboard.noarch 0:1.1-1.el7 Dependency Installed: apr.x86_64 0:1.4.8-3.el7 apr-util.x86_64 0:1.5.2-6.el7 httpd.x86_64 0:2.4.6-45.el7 httpd-tools.x86_64 0:2.4.6-45.el7 mailcap.noarch 0:2.1.41-2.el7 rhscon-api-httpd.noarch 0:0.0.1-1.el7 Complete! We are interested in what messages exist when they are not successful: where are those messages cataloged/located? Ken Hartsoe Content Strategist Red Hat Storage Documentation khartsoe at redhat.com; IRC: khartsoe Office: 919 754 4770; Internal: 814 4770 ----- Original Message ----- | On 4 April 2017 at 17:06, Kenneth Hartsoe wrote: | | > Sorry for the confusion :-) basically, when a customer goes through | > install, we would like to see what messages will display should something | > fail; the idea being that there might be some common scenario(s) that we | > can provide a brief solution for, as a verification step, etc. | > | | Aha! Alright - so would these be like the information | messages/warnings/tips which are also included as part of the UX | designs? | | _______________________________________________ | Tendrl-devel mailing list | Tendrl-devel at redhat.com | https://www.redhat.com/mailman/listinfo/tendrl-devel | From japplewh at redhat.com Tue Apr 4 12:04:12 2017 From: japplewh at redhat.com (Jeff Applewhite) Date: Tue, 4 Apr 2017 08:04:12 -0400 Subject: [Tendrl-devel] Tendrl release v1.2.2 (beta-1) In-Reply-To: References: <671136336.8451253.1491245779871.JavaMail.zimbra@redhat.com> <218911782.8689573.1491305763434.JavaMail.zimbra@redhat.com> Message-ID: In my experience grepping for tendrl in /var/log/messages is a start, followed by journalctl _PID=8088 where the pid = the tendrl-* service pid. It's actually more likely imo that someone might encounter an error in configuration rather than outright failure of tendrl itself. Now when we get into installing ceph and gluster that very well could change. On Tue, Apr 4, 2017 at 7:39 AM, sankarshan wrote: > On 4 April 2017 at 17:06, Kenneth Hartsoe wrote: > > > Sorry for the confusion :-) basically, when a customer goes through > install, we would like to see what messages will display should something > fail; the idea being that there might be some common scenario(s) that we > can provide a brief solution for, as a verification step, etc. > > > > Aha! Alright - so would these be like the information > messages/warnings/tips which are also included as part of the UX > designs? > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > -- Jeff Applewhite Principal Product Manager From mkudlej at redhat.com Tue Apr 4 12:16:49 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Tue, 4 Apr 2017 14:16:49 +0200 Subject: [Tendrl-devel] Tendrl release v1.2.2 (beta-1) In-Reply-To: <423213423.8697385.1491307382991.JavaMail.zimbra@redhat.com> References: <671136336.8451253.1491245779871.JavaMail.zimbra@redhat.com> <218911782.8689573.1491305763434.JavaMail.zimbra@redhat.com> <423213423.8697385.1491307382991.JavaMail.zimbra@redhat.com> Message-ID: <41975146-5f37-4b7e-2c4b-2cec4d96437e@redhat.com> Hi Kenneth, good source of where to look in case of problems is also https://github.com/Tendrl/documentation/wiki/Information-required-for-debugging-issues-on-the-Tendrl-stack On 04/04/2017 02:03 PM, Kenneth Hartsoe wrote: > Hi Sankarshan, > > These are not UX related: the messages/output we are looking for are in regard to installing the packages. > > For example, after installing the packages (i.e. RHSCON API, Dashboard, etc.), when successful, the user sees this: > > The packages and dependencies are successfully installed as shown in the following example CLI output. > Installed: > rhscon-dashboard.noarch 0:1.1-1.el7 > Dependency Installed: > apr.x86_64 0:1.4.8-3.el7 apr-util.x86_64 0:1.5.2-6.el7 httpd.x86_64 0:2.4.6-45.el7 > httpd-tools.x86_64 0:2.4.6-45.el7 mailcap.noarch 0:2.1.41-2.el7 rhscon-api-httpd.noarch 0:0.0.1-1.el7 > > Complete! > > We are interested in what messages exist when they are not successful: where are those messages cataloged/located? > > Ken Hartsoe > Content Strategist > Red Hat Storage Documentation > > khartsoe at redhat.com; IRC: khartsoe > Office: 919 754 4770; Internal: 814 4770 > > ----- Original Message ----- > | On 4 April 2017 at 17:06, Kenneth Hartsoe wrote: > | > | > Sorry for the confusion :-) basically, when a customer goes through > | > install, we would like to see what messages will display should something > | > fail; the idea being that there might be some common scenario(s) that we > | > can provide a brief solution for, as a verification step, etc. > | > > | > | Aha! Alright - so would these be like the information > | messages/warnings/tips which are also included as part of the UX > | designs? > | > | _______________________________________________ > | Tendrl-devel mailing list > | Tendrl-devel at redhat.com > | https://www.redhat.com/mailman/listinfo/tendrl-devel > | > > _______________________________________________ > 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 japplewh at redhat.com Tue Apr 4 20:14:07 2017 From: japplewh at redhat.com (Jeff Applewhite) Date: Tue, 4 Apr 2017 16:14:07 -0400 Subject: [Tendrl-devel] Tendrl Installer Message-ID: Hi All I met with the QE team today and we discussed the plan for installation of Tendrl. The team agreed that their Tendrl server Ansible installation code in the usmqe-setup/tendrl-* playbooks could be merged into the tendrl-ansible repo. I had asked them to consider it because they are on this task regularly and are up to speed on the changes as they land *and they are testing things with this method so it makes for a more complete, tested package. This merge will only happen once the changes settle down (after the beta releases). In the mean time their code will continue to be available in the usmqe-setup/tendrl_[server|node] playbooks (which I have run fine from that location). I have defined some requirements for the installer here: https://tendrl.atlassian.net/browse/TEN-257 Please comment and make any suggestions for improvement, state disagreements with scope, etc. on the Jira page so we can gather that in one location. Just to be clear: The understanding is that QE would take this on for the *Tendrl upstream project only.* Thanks to QE team for agreeing to help out with this! -- Jeff Applewhite Principal Product Manager From mbukatov at redhat.com Wed Apr 5 08:05:54 2017 From: mbukatov at redhat.com (Martin Bukatovic) Date: Wed, 5 Apr 2017 10:05:54 +0200 Subject: [Tendrl-devel] Tendrl release v1.2.2 (beta-1) In-Reply-To: <218911782.8689573.1491305763434.JavaMail.zimbra@redhat.com> References: <671136336.8451253.1491245779871.JavaMail.zimbra@redhat.com> <218911782.8689573.1491305763434.JavaMail.zimbra@redhat.com> Message-ID: <4a3d8745-a70a-1796-4293-0e2ea575201c@redhat.com> Hi Ken, On 04/04/2017 01:36 PM, Kenneth Hartsoe wrote: > Sorry for the confusion :-) basically, when a customer goes through install, we would like to see what messages will display should something fail; the idea being that there might be some common scenario(s) that we can provide a brief solution for, as a verification step, etc. I don't think that the code is in shape good enough for us to have this kind of documentation. -- Martin Bukatovic USM QE team Red Hat From sankarshan.mukhopadhyay at gmail.com Wed Apr 5 08:42:30 2017 From: sankarshan.mukhopadhyay at gmail.com (Sankarshan Mukhopadhyay) Date: Wed, 5 Apr 2017 14:12:30 +0530 Subject: [Tendrl-devel] Tendrl release v1.2.2 (beta-1) In-Reply-To: <4a3d8745-a70a-1796-4293-0e2ea575201c@redhat.com> References: <671136336.8451253.1491245779871.JavaMail.zimbra@redhat.com> <218911782.8689573.1491305763434.JavaMail.zimbra@redhat.com> <4a3d8745-a70a-1796-4293-0e2ea575201c@redhat.com> Message-ID: On Wed, Apr 5, 2017 at 1:35 PM, Martin Bukatovic wrote: > Hi Ken, > > On 04/04/2017 01:36 PM, Kenneth Hartsoe wrote: >> Sorry for the confusion :-) basically, when a customer goes through install, we would like to see what messages will display should something fail; the idea being that there might be some common scenario(s) that we can provide a brief solution for, as a verification step, etc. > > I don't think that the code is in shape good enough for us to have this > kind of documentation. > That is a very sweeping remark - could you take a bit more time to explain why it is not possible to use that kind of "if - else" switch like annotation based on a document such as ? I understand that we might be a couple of steps from achieving what Ken and Rakesh want - but emphatically stating that the code is not in good shape might be a bit too rash. -- sankarshan mukhopadhyay From sankarshan at redhat.com Wed Apr 5 08:49:11 2017 From: sankarshan at redhat.com (sankarshan) Date: Wed, 5 Apr 2017 14:19:11 +0530 Subject: [Tendrl-devel] Tendrl Installer In-Reply-To: References: Message-ID: On 5 April 2017 at 01:44, Jeff Applewhite wrote: > Hi All > > I met with the QE team today and we discussed the plan for installation of > Tendrl. The team agreed that their Tendrl server Ansible installation code > in the usmqe-setup/tendrl-* playbooks could be merged into the > tendrl-ansible repo. I had asked them to consider it because they are on > this task regularly and are up to speed on the changes as they land *and > they are testing things with this method so it makes for a more complete, > tested package. This merge will only happen once the changes settle down > (after the beta releases). In the mean time their code will continue to be > available in the usmqe-setup/tendrl_[server|node] playbooks (which I have > run fine from that location). > > > I have defined some requirements for the installer here: > > https://tendrl.atlassian.net/browse/TEN-257 > > Please comment and make any suggestions for improvement, state > disagreements with scope, etc. on the Jira page so we can gather that in > one location. > > Just to be clear: The understanding is that QE would take this on for > the *Tendrl > upstream project only.* > > Thanks to QE team for agreeing to help out with this! Indeed! This is a strong step forward. Thanks for coordinating all the conversations and moving pieces on this topic. From rkanade at redhat.com Wed Apr 5 09:49:12 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Wed, 5 Apr 2017 15:19:12 +0530 Subject: [Tendrl-devel] Tendrl release v1.2.2 (beta-1) In-Reply-To: References: <671136336.8451253.1491245779871.JavaMail.zimbra@redhat.com> <218911782.8689573.1491305763434.JavaMail.zimbra@redhat.com> <4a3d8745-a70a-1796-4293-0e2ea575201c@redhat.com> Message-ID: tendrl-performance-monitoring and tendrl-alerting, beta-1 are released. RPMS are being built by copr and can be found at : https://copr. fedorainfracloud.org/coprs/tendrl/tendrl/ On Wed, Apr 5, 2017 at 2:12 PM, Sankarshan Mukhopadhyay < sankarshan.mukhopadhyay at gmail.com> wrote: > On Wed, Apr 5, 2017 at 1:35 PM, Martin Bukatovic > wrote: > > Hi Ken, > > > > On 04/04/2017 01:36 PM, Kenneth Hartsoe wrote: > >> Sorry for the confusion :-) basically, when a customer goes through > install, we would like to see what messages will display should something > fail; the idea being that there might be some common scenario(s) that we > can provide a brief solution for, as a verification step, etc. > > > > I don't think that the code is in shape good enough for us to have this > > kind of documentation. > > > > That is a very sweeping remark - could you take a bit more time to > explain why it is not possible to use that kind of "if - else" switch > like annotation based on a document such as > Package-Installation-Reference>? > > I understand that we might be a couple of steps from achieving what > Ken and Rakesh want - but emphatically stating that the code is not in > good shape might be a bit too rash. > > > -- > sankarshan mukhopadhyay > > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > From mbukatov at redhat.com Wed Apr 5 11:15:39 2017 From: mbukatov at redhat.com (Martin Bukatovic) Date: Wed, 5 Apr 2017 13:15:39 +0200 Subject: [Tendrl-devel] Tendrl release v1.2.2 (beta-1) In-Reply-To: References: <671136336.8451253.1491245779871.JavaMail.zimbra@redhat.com> <218911782.8689573.1491305763434.JavaMail.zimbra@redhat.com> <4a3d8745-a70a-1796-4293-0e2ea575201c@redhat.com> Message-ID: <0fab443a-75ec-1d75-4d4b-68b3a94f6aa3@redhat.com> On 04/05/2017 10:42 AM, Sankarshan Mukhopadhyay wrote: > On Wed, Apr 5, 2017 at 1:35 PM, Martin Bukatovic wrote: >> Hi Ken, >> >> On 04/04/2017 01:36 PM, Kenneth Hartsoe wrote: >>> Sorry for the confusion :-) basically, when a customer goes through install, we would like to see what messages will display should something fail; the idea being that there might be some common scenario(s) that we can provide a brief solution for, as a verification step, etc. >> >> I don't think that the code is in shape good enough for us to have this >> kind of documentation. >> > > That is a very sweeping remark - could you take a bit more time to > explain why it is not possible to use that kind of "if - else" switch > like annotation based on a document such as > ? > > I understand that we might be a couple of steps from achieving what > Ken and Rakesh want - but emphatically stating that the code is not in > good shape might be a bit too rash. I'm sorry for sounding harsh and I understand the value of the document Ken proposes. But for this to have any value, the product needs to get into some quality level which I don't see yet. I don't have any formal way to convey this for you, but it probably suggests that the testing should be done before we start working on this. Eg. login/authentication is broken so that it could lead to very strange behaviors and errors[1], but instead of thinking how to document this so that the user installing Tendrl won't be confused, I believe that it would make more sense to fix that, making sure we don't release Tendrl with such issues. [1] https://github.com/Tendrl/api/issues/118 https://github.com/Tendrl/api/issues/119 -- Martin Bukatovic USM QE team Red Hat From khartsoe at redhat.com Wed Apr 5 12:11:08 2017 From: khartsoe at redhat.com (Kenneth Hartsoe) Date: Wed, 5 Apr 2017 08:11:08 -0400 (EDT) Subject: [Tendrl-devel] Tendrl release v1.2.2 (beta-1) In-Reply-To: <0fab443a-75ec-1d75-4d4b-68b3a94f6aa3@redhat.com> References: <671136336.8451253.1491245779871.JavaMail.zimbra@redhat.com> <218911782.8689573.1491305763434.JavaMail.zimbra@redhat.com> <4a3d8745-a70a-1796-4293-0e2ea575201c@redhat.com> <0fab443a-75ec-1d75-4d4b-68b3a94f6aa3@redhat.com> Message-ID: <1904909837.9063277.1491394268664.JavaMail.zimbra@redhat.com> Considering the quality assessment, i.e., unstable login/authentication, I agree stability is needed before trying to resolve via docs. Ken Hartsoe Content Strategist Red Hat Storage Documentation khartsoe at redhat.com; IRC: khartsoe Office: 919 754 4770; Internal: 814 4770 ----- Original Message ----- | On 04/05/2017 10:42 AM, Sankarshan Mukhopadhyay wrote: | > On Wed, Apr 5, 2017 at 1:35 PM, Martin Bukatovic | > wrote: | >> Hi Ken, | >> | >> On 04/04/2017 01:36 PM, Kenneth Hartsoe wrote: | >>> Sorry for the confusion :-) basically, when a customer goes through | >>> install, we would like to see what messages will display should | >>> something fail; the idea being that there might be some common | >>> scenario(s) that we can provide a brief solution for, as a verification | >>> step, etc. | >> | >> I don't think that the code is in shape good enough for us to have this | >> kind of documentation. | >> | > | > That is a very sweeping remark - could you take a bit more time to | > explain why it is not possible to use that kind of "if - else" switch | > like annotation based on a document such as | > ? | > | > I understand that we might be a couple of steps from achieving what | > Ken and Rakesh want - but emphatically stating that the code is not in | > good shape might be a bit too rash. | | I'm sorry for sounding harsh and I understand the value of the document | Ken proposes. But for this to have any value, the product needs to get | into some quality level which I don't see yet. I don't have any formal | way to convey this for you, but it probably suggests that the testing | should be done before we start working on this. | | Eg. login/authentication is broken so that it could lead to very | strange behaviors and errors[1], but instead of thinking how to document | this so that the user installing Tendrl won't be confused, I believe | that it would make more sense to fix that, making sure we don't release | Tendrl with such issues. | | [1] https://github.com/Tendrl/api/issues/118 | https://github.com/Tendrl/api/issues/119 | | -- | 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 shtripat at redhat.com Fri Apr 7 05:02:17 2017 From: shtripat at redhat.com (Shubhendu Tripathi) Date: Fri, 7 Apr 2017 10:32:17 +0530 Subject: [Tendrl-devel] Flow for forming journal mapping In-Reply-To: <447a1c16-e49a-ed1b-2ad7-18b6e31de272@redhat.com> References: <447a1c16-e49a-ed1b-2ad7-18b6e31de272@redhat.com> Message-ID: <1db91392-3a16-f14f-7646-edc7330505a5@redhat.com> Hi Team, Before I go ahead and create a specification for this, I have few clarifications/questions to be answered. It goes as below.... For any flow/work to be executed from API which makes a call to node-agent or {ceph/gluster}-integration is using a job creation in etcd which is picked by backend and output is written back to etcd. Once job is complete, API layer looks for the data in appropriate directory in etcd for the output and moves ahead. Now in the below case where we need to generate journal mapping for OSDs based on disks/devices provided for nodes, should we go with same above way and write the job output in some temporary location say `/_tmp/{integration_id}/journal_mapping` as dictionary? At this moment I cant think any other way to achieve this if the logic for generating the mapping to be maintained within node-agent's ceph provisioner. Kindly provide your thoughts/suggestions in this thread. Thanks and Regards, Shubhendu On 04/06/2017 10:10 PM, Shubhendu Tripathi wrote: > Below looks like input and output structure for journal mapping flow - > > ============================================== > The input structure for the flow is as below - > > { > "node_configuration": { > "node_id_1": { > "storage_disks": [{"device": "/dev/vdb", "size": bytes, > "ssd": true }, {"device": "/dev/vdc", "size": bytes, "ssd": false}, ...] > }, > "node_id_2": { > "storage_disks": [{"device": "/dev/vdb", "size": bytes, > "ssd": true }, {"device": "/dev/vdc", "size": bytes, "ssd": false}, ...] > }, ..... > } > } > > > The output structure from the flow would be as below > > { > "node_id_1": { > "storage_disks": [{"device": "/dev/vdb", "journal": > "/dev/vdc" }, {"device": "/dev/vdd", "journal": "/dev/vde"}, ...], > "unallocated_disks": ["/dev/vdf", "/dev/vdg"] > }, > "node_id_2": { > "storage_disks": [{"device": "/dev/vdb", "journal": > "/dev/vdc" }, {"device": "/dev/vdd", "journal": "/dev/vde"}, ...], > "unallocated_disks": ["/dev/vdf", "/dev/vdg"] > }, ... > } > > =================================================== > > Let me know if something missed out in this. > > Regards, > Shubhendu From shtripat at redhat.com Fri Apr 7 05:14:46 2017 From: shtripat at redhat.com (Shubhendu Tripathi) Date: Fri, 7 Apr 2017 10:44:46 +0530 Subject: [Tendrl-devel] Flow for forming journal mapping In-Reply-To: <1db91392-3a16-f14f-7646-edc7330505a5@redhat.com> References: <447a1c16-e49a-ed1b-2ad7-18b6e31de272@redhat.com> <1db91392-3a16-f14f-7646-edc7330505a5@redhat.com> Message-ID: Another thought, if we dont want go ahead with this flow, the Tendrl API layer need to implement this logic as a GET. Regards, Shubhendu On 04/07/2017 10:32 AM, Shubhendu Tripathi wrote: > Hi Team, > > Before I go ahead and create a specification for this, I have few > clarifications/questions to be answered. > It goes as below.... > > For any flow/work to be executed from API which makes a call to > node-agent or {ceph/gluster}-integration is using a job creation in > etcd which is picked by backend and output is written back to etcd. > Once job is complete, API layer looks for the data in appropriate > directory in etcd for the output and moves ahead. > > Now in the below case where we need to generate journal mapping for > OSDs based on disks/devices provided for nodes, should we go with same > above way and write the job output in some temporary location say > `/_tmp/{integration_id}/journal_mapping` as dictionary? > > At this moment I cant think any other way to achieve this if the logic > for generating the mapping to be maintained within node-agent's ceph > provisioner. > > Kindly provide your thoughts/suggestions in this thread. > > Thanks and Regards, > Shubhendu > > > > On 04/06/2017 10:10 PM, Shubhendu Tripathi wrote: >> Below looks like input and output structure for journal mapping flow - >> >> ============================================== >> The input structure for the flow is as below - >> >> { >> "node_configuration": { >> "node_id_1": { >> "storage_disks": [{"device": "/dev/vdb", "size": bytes, >> "ssd": true }, {"device": "/dev/vdc", "size": bytes, "ssd": false}, ...] >> }, >> "node_id_2": { >> "storage_disks": [{"device": "/dev/vdb", "size": bytes, >> "ssd": true }, {"device": "/dev/vdc", "size": bytes, "ssd": false}, ...] >> }, ..... >> } >> } >> >> >> The output structure from the flow would be as below >> >> { >> "node_id_1": { >> "storage_disks": [{"device": "/dev/vdb", "journal": >> "/dev/vdc" }, {"device": "/dev/vdd", "journal": "/dev/vde"}, ...], >> "unallocated_disks": ["/dev/vdf", "/dev/vdg"] >> }, >> "node_id_2": { >> "storage_disks": [{"device": "/dev/vdb", "journal": >> "/dev/vdc" }, {"device": "/dev/vdd", "journal": "/dev/vde"}, ...], >> "unallocated_disks": ["/dev/vdf", "/dev/vdg"] >> }, ... >> } >> >> =================================================== >> >> Let me know if something missed out in this. >> >> Regards, >> Shubhendu > From tjeyasin at redhat.com Wed Apr 12 09:48:27 2017 From: tjeyasin at redhat.com (Timothy Asir Jeyasingh) Date: Wed, 12 Apr 2017 05:48:27 -0400 (EDT) Subject: [Tendrl-devel] Tendrl dependencies moved to "dependencies" copr repo In-Reply-To: <83258131.13110562.1491990217722.JavaMail.zimbra@redhat.com> Message-ID: <1181180164.13111196.1491990507690.JavaMail.zimbra@redhat.com> Hi All, All the tendrl dependency packages are now moved from "tendrl" copr repo to "dependencies" repo. url: https://copr.fedorainfracloud.org/coprs/tendrl/dependencies/ Please use the following url to enable the repository: https://copr.fedorainfracloud.org/coprs/tendrl/dependencies/repo/epel-7/tendrl-dependencies-epel-7.repo Regards, Tim From mbukatov at redhat.com Wed Apr 12 12:56:00 2017 From: mbukatov at redhat.com (Martin Bukatovic) Date: Wed, 12 Apr 2017 14:56:00 +0200 Subject: [Tendrl-devel] Tendrl dependencies moved to "dependencies" copr repo In-Reply-To: <1181180164.13111196.1491990507690.JavaMail.zimbra@redhat.com> References: <1181180164.13111196.1491990507690.JavaMail.zimbra@redhat.com> Message-ID: <4275e242-00b2-d40e-9642-48a636bbac48@redhat.com> Hi, On 04/12/2017 11:48 AM, Timothy Asir Jeyasingh wrote: > All the tendrl dependency packages are now moved from "tendrl" copr repo > to "dependencies" repo. > url: https://copr.fedorainfracloud.org/coprs/tendrl/dependencies/ > > Please use the following url to enable the repository: > https://copr.fedorainfracloud.org/coprs/tendrl/dependencies/repo/epel-7/tendrl-dependencies-epel-7.repo Understood, we would need to update our tests and setup. /me notes https://github.com/Tendrl/usmqe-tests/issues/68 While I'm ok it, I would still like to know about the reasoning for this change. What would we gain from this? -- Martin Bukatovic USM QE team Red Hat From khartsoe at redhat.com Thu Apr 13 14:57:19 2017 From: khartsoe at redhat.com (Kenneth Hartsoe) Date: Thu, 13 Apr 2017 10:57:19 -0400 (EDT) Subject: [Tendrl-devel] RHS-C 3.0: ansible install method In-Reply-To: <589879576.12158515.1492095151112.JavaMail.zimbra@redhat.com> Message-ID: <1526008124.12160812.1492095439690.JavaMail.zimbra@redhat.com> Hello, Looking for ansible playbooks to glean install method for inclusion in the RHS-C 3 doc. Please forward link, etc. Thank you. Ken Hartsoe Content Strategist Red Hat Storage Documentation khartsoe at redhat.com; IRC: khartsoe Office: 919 754 4770; Internal: 814 4770 From mkudlej at redhat.com Thu Apr 13 15:28:08 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Thu, 13 Apr 2017 17:28:08 +0200 Subject: [Tendrl-devel] RHS-C 3.0: ansible install method In-Reply-To: <1526008124.12160812.1492095439690.JavaMail.zimbra@redhat.com> References: <1526008124.12160812.1492095439690.JavaMail.zimbra@redhat.com> Message-ID: <104ced9e-e1b4-5999-86f8-69cb6eea151d@redhat.com> Hi Ken, On 04/13/2017 04:57 PM, Kenneth Hartsoe wrote: > Looking for ansible playbooks to glean install method for inclusion in the RHS-C 3 doc. Please forward link, etc. Thank you. there is no downstream ansible based installation for now. There are 2 upstream ones: one used by Jeff and other one use and made by QE. There is agreement that installation process will be more clear after end of Beta and there will be some kind of merge from both repositories to tendrl-ansible repository with ansible playbooks for Tendrl installation. -- 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 Thu Apr 13 22:18:54 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Fri, 14 Apr 2017 03:48:54 +0530 Subject: [Tendrl-devel] Tendrl dependencies moved to "dependencies" copr repo In-Reply-To: <4275e242-00b2-d40e-9642-48a636bbac48@redhat.com> References: <1181180164.13111196.1491990507690.JavaMail.zimbra@redhat.com> <4275e242-00b2-d40e-9642-48a636bbac48@redhat.com> Message-ID: Tendrl has a copr repository each for branch "develop" [0], "master" [1], "release/*" [2] All of these require same set of dependencies and we do not want to carry dependencies in each of the above copr repos. Hence the change [0]: https://copr.fedorainfracloud.org/coprs/tendrl/tendrl-develop/ [1]: https://copr.fedorainfracloud.org/coprs/tendrl/tendrl/ [2]: https://copr.fedorainfracloud.org/coprs/tendrl/release/ the only concern I see is if we have a branch above which requires specific versions of dependencies which the common deps repo cannot satisfy On Wed, Apr 12, 2017 at 6:26 PM, Martin Bukatovic wrote: > Hi, > > On 04/12/2017 11:48 AM, Timothy Asir Jeyasingh wrote: > > All the tendrl dependency packages are now moved from "tendrl" copr repo > > to "dependencies" repo. > > url: https://copr.fedorainfracloud.org/coprs/tendrl/dependencies/ > > > > Please use the following url to enable the repository: > > https://copr.fedorainfracloud.org/coprs/tendrl/dependencies/ > repo/epel-7/tendrl-dependencies-epel-7.repo > > Understood, we would need to update our tests and setup. > > /me notes https://github.com/Tendrl/usmqe-tests/issues/68 > > While I'm ok it, I would still like to know about the reasoning for > this change. What would we gain from this? > > -- > 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 rkanade at redhat.com Sat Apr 15 11:42:07 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Sat, 15 Apr 2017 17:12:07 +0530 Subject: [Tendrl-devel] tendrl-node-agent and performance profiling Message-ID: Hi, I tried running a yappi based greenlet profiler [0] which outputs profiling data in the Callgrind format [1], Now I am not a linux profiling expert but I can see some evident sections of code where we can save cpu/memory Please take a look at the callgrind data [2] and the visualizations [3] (done by gprof2dot and dot) so that we can address our perf bottlenecks and generate more meaningful perf visuals [0] https://github.com/ajdavis/GreenletProfiler [0]: https://emptysqua.re/blog/greenletprofiler/ [1]: http://valgrind.org/docs/manual/cl-manual.html [2]: https://paste.fedoraproject.org/paste/No5a2Eznl4Vn11ybYDzfc15M1UNdIGYhyRLivL9gydE= [3]: http://svgshare.com/i/1EE.svg Yappi: https://github.com/sumerc/yappi I would love to have more inputs on what kind of profiling Tendrl should be doing From nthomas at redhat.com Mon Apr 17 13:01:16 2017 From: nthomas at redhat.com (Nishanth Thomas) Date: Mon, 17 Apr 2017 18:31:16 +0530 Subject: [Tendrl-devel] OSD create marked as failed with latest version of ceph-installer Message-ID: Alfredo, Andrew, OSD create task returns a failure with latest version of ceph-installer( http://download-node-02.eng.bos.redhat.com/rcm-guest/ceph-drops/auto/rhscon-2-rhel-7-compose/latest-RHSCON-2-RHEL-7/compose/Installer/x86_64/os/). The OSDs are created and could see that is added to the cluster, but the task is marked as failed. Please have a look at the task status api respose at[1] Note that with a older version( http://download-node-02.eng.bos.redhat.com/rcm-guest/ceph-drops/auto/rhscon-2-rhel-7-compose/RHSCON-2.0-RHEL-7-20170215.t.0/compose/Installer/x86_64/os/), things are working as expected Please have a look at and let us know Thanks, Nishanth [1]https://pastebin.com/Ncdu3sts From aschoen at redhat.com Mon Apr 17 13:10:51 2017 From: aschoen at redhat.com (Andrew Schoen) Date: Mon, 17 Apr 2017 08:10:51 -0500 Subject: [Tendrl-devel] OSD create marked as failed with latest version of ceph-installer In-Reply-To: References: Message-ID: Nishanth, In the output I see the 'ceph.ceph-common : restart ceph osds daemon(s)' tasked failed with: 'Error with PGs, check config'. Have you set any configuration there that does not look correct? Thanks, Andrew On Mon, Apr 17, 2017 at 8:01 AM, Nishanth Thomas wrote: > Alfredo, Andrew, > > > OSD create task returns a failure with latest version of > ceph-installer(http://download-node-02.eng.bos.redhat.com/rcm-guest/ceph-drops/auto/rhscon-2-rhel-7-compose/latest-RHSCON-2-RHEL-7/compose/Installer/x86_64/os/). > The OSDs are created and could see that is added to the cluster, but the > task is marked as failed. Please have a look at the task status api respose > at[1] > > Note that with a older > version(http://download-node-02.eng.bos.redhat.com/rcm-guest/ceph-drops/auto/rhscon-2-rhel-7-compose/RHSCON-2.0-RHEL-7-20170215.t.0/compose/Installer/x86_64/os/), > things are working as expected > > Please have a look at and let us know > > Thanks, > Nishanth > > [1]https://pastebin.com/Ncdu3sts From aschoen at redhat.com Mon Apr 17 13:15:15 2017 From: aschoen at redhat.com (Andrew Schoen) Date: Mon, 17 Apr 2017 08:15:15 -0500 Subject: [Tendrl-devel] OSD create marked as failed with latest version of ceph-installer In-Reply-To: References: Message-ID: On Mon, Apr 17, 2017 at 8:10 AM, Andrew Schoen wrote: > Nishanth, > > In the output I see the 'ceph.ceph-common : restart ceph osds > daemon(s)' tasked failed with: 'Error with PGs, check config'. Actually, it looks like we're seeing the same error in our upstream tests. https://jenkins.ceph.com/job/ceph-installer-tests-ansible2.2-nightly_centos7/109/console From adeza at redhat.com Mon Apr 17 13:50:12 2017 From: adeza at redhat.com (Alfredo Deza) Date: Mon, 17 Apr 2017 09:50:12 -0400 Subject: [Tendrl-devel] OSD create marked as failed with latest version of ceph-installer In-Reply-To: References: Message-ID: On Mon, Apr 17, 2017 at 9:01 AM, Nishanth Thomas wrote: > Alfredo, Andrew, > > > OSD create task returns a failure with latest version of > ceph-installer(http://download-node-02.eng.bos.redhat.com/rcm-guest/ceph-drops/auto/rhscon-2-rhel-7-compose/latest-RHSCON-2-RHEL-7/compose/Installer/x86_64/os/). > The OSDs are created and could see that is added to the cluster, but the > task is marked as failed. Please have a look at the task status api respose > at[1] Hey Guillaume, seems like this is something you added recently with https://github.com/ceph/ceph-ansible/commit/5bec62ba7c8ecbc91ede05297dadb639c530f597 Can you help out sorting it out? Ideally we would want better logging here (had to lookup the bash script to see why we would need to "check config") I also don't think we have 100% clean PGs in our tests anyway. > > Note that with a older > version(http://download-node-02.eng.bos.redhat.com/rcm-guest/ceph-drops/auto/rhscon-2-rhel-7-compose/RHSCON-2.0-RHEL-7-20170215.t.0/compose/Installer/x86_64/os/), > things are working as expected > > Please have a look at and let us know > > Thanks, > Nishanth > > [1]https://pastebin.com/Ncdu3sts From shan at redhat.com Mon Apr 17 22:15:38 2017 From: shan at redhat.com (Sebastien Han) Date: Mon, 17 Apr 2017 17:15:38 -0500 Subject: [Tendrl-devel] OSD create marked as failed with latest version of ceph-installer In-Reply-To: References: Message-ID: Looks like the /tmp/restart_osd_daemon.sh failed, is it possible to run it manually to do further debugging? I added a couple of comments here: https://github.com/ceph/ceph-ansible/commit/5bec62ba7c8ecbc91ede05297dadb639c530f597 On Mon, Apr 17, 2017 at 8:50 AM, Alfredo Deza wrote: > On Mon, Apr 17, 2017 at 9:01 AM, Nishanth Thomas wrote: >> Alfredo, Andrew, >> >> >> OSD create task returns a failure with latest version of >> ceph-installer(http://download-node-02.eng.bos.redhat.com/rcm-guest/ceph-drops/auto/rhscon-2-rhel-7-compose/latest-RHSCON-2-RHEL-7/compose/Installer/x86_64/os/). >> The OSDs are created and could see that is added to the cluster, but the >> task is marked as failed. Please have a look at the task status api respose >> at[1] > > Hey Guillaume, seems like this is something you added recently with > https://github.com/ceph/ceph-ansible/commit/5bec62ba7c8ecbc91ede05297dadb639c530f597 > > Can you help out sorting it out? Ideally we would want better logging > here (had to lookup the bash script to see why we would need to "check > config") > > I also don't think we have 100% clean PGs in our tests anyway. > > >> >> Note that with a older >> version(http://download-node-02.eng.bos.redhat.com/rcm-guest/ceph-drops/auto/rhscon-2-rhel-7-compose/RHSCON-2.0-RHEL-7-20170215.t.0/compose/Installer/x86_64/os/), >> things are working as expected >> >> Please have a look at and let us know >> >> Thanks, >> Nishanth >> >> [1]https://pastebin.com/Ncdu3sts -- Cheers ?????? S?bastien Han Principal Software Engineer, Storage Architect "Always give 100%. Unless you're giving blood." Mail: seb at redhat.com Address: 11 bis, rue Roqu?pine - 75008 Paris From rkanade at redhat.com Tue Apr 18 18:22:43 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Tue, 18 Apr 2017 23:52:43 +0530 Subject: [Tendrl-devel] Tendrl release v1.2.3 Message-ID: Announcing availability of builds for Tendrl v1.2.3 components (API, Alerting, Core, Dashboard) Tendrl release v1.2.3 rpms (install latest): https://copr.fedorainfracloud.org/coprs/tendrl/release/ Extra dependencies: https://copr.fedorainfracloud.org/coprs/tendrl/dependencies/ More details: https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.2.3 Note: tendrl-performance-monitoring and tendrl-node-monitoring are under integration testing. Will be released soon. Until then, Tendrl devel rpm packages can be installed Tendrl hourly repo: https://copr.fedorainfracloud.org/coprs/tendrl/tendrl/ ((under integration testing) From kdreyer at redhat.com Wed Apr 19 00:57:30 2017 From: kdreyer at redhat.com (Ken Dreyer) Date: Tue, 18 Apr 2017 18:57:30 -0600 Subject: [Tendrl-devel] OSD create marked as failed with latest version of ceph-installer In-Reply-To: References: Message-ID: Is this a regression in ceph-ansible v2.2.0 compared with v2.1.9? Do we have a BZ to track this? - Ken On Mon, Apr 17, 2017 at 4:15 PM, Sebastien Han wrote: > Looks like the /tmp/restart_osd_daemon.sh failed, is it possible to > run it manually to do further debugging? > I added a couple of comments here: > https://github.com/ceph/ceph-ansible/commit/5bec62ba7c8ecbc91ede05297dadb639c530f597 > > On Mon, Apr 17, 2017 at 8:50 AM, Alfredo Deza wrote: >> On Mon, Apr 17, 2017 at 9:01 AM, Nishanth Thomas wrote: >>> Alfredo, Andrew, >>> >>> >>> OSD create task returns a failure with latest version of >>> ceph-installer(http://download-node-02.eng.bos.redhat.com/rcm-guest/ceph-drops/auto/rhscon-2-rhel-7-compose/latest-RHSCON-2-RHEL-7/compose/Installer/x86_64/os/). >>> The OSDs are created and could see that is added to the cluster, but the >>> task is marked as failed. Please have a look at the task status api respose >>> at[1] >> >> Hey Guillaume, seems like this is something you added recently with >> https://github.com/ceph/ceph-ansible/commit/5bec62ba7c8ecbc91ede05297dadb639c530f597 >> >> Can you help out sorting it out? Ideally we would want better logging >> here (had to lookup the bash script to see why we would need to "check >> config") >> >> I also don't think we have 100% clean PGs in our tests anyway. >> >> >>> >>> Note that with a older >>> version(http://download-node-02.eng.bos.redhat.com/rcm-guest/ceph-drops/auto/rhscon-2-rhel-7-compose/RHSCON-2.0-RHEL-7-20170215.t.0/compose/Installer/x86_64/os/), >>> things are working as expected >>> >>> Please have a look at and let us know >>> >>> Thanks, >>> Nishanth >>> >>> [1]https://pastebin.com/Ncdu3sts > > > > -- > Cheers > > ?????? > S?bastien Han > Principal Software Engineer, Storage Architect > > "Always give 100%. Unless you're giving blood." > > Mail: seb at redhat.com > Address: 11 bis, rue Roqu?pine - 75008 Paris > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel From aschoen at redhat.com Wed Apr 19 01:12:27 2017 From: aschoen at redhat.com (Andrew Schoen) Date: Tue, 18 Apr 2017 20:12:27 -0500 Subject: [Tendrl-devel] OSD create marked as failed with latest version of ceph-installer In-Reply-To: References: Message-ID: I don't know of any BZ, but his PR seemed to fix the issue for me. https://github.com/ceph/ceph-ansible/pull/1455 Here is a log from our upstream ceph-installer tests using the branch from that PR: https://jenkins.ceph.com/view/ceph-installer/job/ceph-installer-tests-ansible2.2-nightly_centos7/114/consoleFull - Andrew On Tue, Apr 18, 2017 at 7:57 PM, Ken Dreyer wrote: > Is this a regression in ceph-ansible v2.2.0 compared with v2.1.9? > > Do we have a BZ to track this? > > - Ken > > On Mon, Apr 17, 2017 at 4:15 PM, Sebastien Han wrote: >> Looks like the /tmp/restart_osd_daemon.sh failed, is it possible to >> run it manually to do further debugging? >> I added a couple of comments here: >> https://github.com/ceph/ceph-ansible/commit/5bec62ba7c8ecbc91ede05297dadb639c530f597 >> >> On Mon, Apr 17, 2017 at 8:50 AM, Alfredo Deza wrote: >>> On Mon, Apr 17, 2017 at 9:01 AM, Nishanth Thomas wrote: >>>> Alfredo, Andrew, >>>> >>>> >>>> OSD create task returns a failure with latest version of >>>> ceph-installer(http://download-node-02.eng.bos.redhat.com/rcm-guest/ceph-drops/auto/rhscon-2-rhel-7-compose/latest-RHSCON-2-RHEL-7/compose/Installer/x86_64/os/). >>>> The OSDs are created and could see that is added to the cluster, but the >>>> task is marked as failed. Please have a look at the task status api respose >>>> at[1] >>> >>> Hey Guillaume, seems like this is something you added recently with >>> https://github.com/ceph/ceph-ansible/commit/5bec62ba7c8ecbc91ede05297dadb639c530f597 >>> >>> Can you help out sorting it out? Ideally we would want better logging >>> here (had to lookup the bash script to see why we would need to "check >>> config") >>> >>> I also don't think we have 100% clean PGs in our tests anyway. >>> >>> >>>> >>>> Note that with a older >>>> version(http://download-node-02.eng.bos.redhat.com/rcm-guest/ceph-drops/auto/rhscon-2-rhel-7-compose/RHSCON-2.0-RHEL-7-20170215.t.0/compose/Installer/x86_64/os/), >>>> things are working as expected >>>> >>>> Please have a look at and let us know >>>> >>>> Thanks, >>>> Nishanth >>>> >>>> [1]https://pastebin.com/Ncdu3sts >> >> >> >> -- >> Cheers >> >> ?????? >> S?bastien Han >> Principal Software Engineer, Storage Architect >> >> "Always give 100%. Unless you're giving blood." >> >> Mail: seb at redhat.com >> Address: 11 bis, rue Roqu?pine - 75008 Paris >> >> _______________________________________________ >> Tendrl-devel mailing list >> Tendrl-devel at redhat.com >> https://www.redhat.com/mailman/listinfo/tendrl-devel > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel From mkudlej at redhat.com Wed Apr 19 13:03:46 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Wed, 19 Apr 2017 15:03:46 +0200 Subject: [Tendrl-devel] Cluster create documentation Message-ID: <34268847-610e-8121-48b5-1accad4147d1@redhat.com> Hi all, I would like to ask where can I find documentation for create cluster because it is not available in UI so we would like to follow documentation. I cannot find it in: - https://github.com/Tendrl/api/blob/master/docs/clusters.adoc - https://github.com/Tendrl/documentation/tree/master/api I can see output from Flows: { "name": "CreateCluster", "method": "POST", "attributes": [ { "name": "Node[]", "type": "List", "required": true }, { "name": "TendrlContext.cluster_name", "help": "Name of the cluster", "type": "String", "default": null, "required": true }, { "name": "TendrlContext.sds_name", "help": "Name of the Tendrl managed sds, eg: 'gluster'", "type": "String", "default": null, "required": true }, { "name": "TendrlContext.sds_version", "help": "Version of the Tendrl managed sds, eg: '3.2.1'", "type": "String", "default": null, "required": true }, { "name": "Cluster.public_network", "help": "Public Network cidr of the cluster", "type": "String", "default": null, "required": true }, { "name": "Cluster.cluster_network", "help": "Data Nework cidr of the cluster", "type": null, "default": null, "required": true }, { "name": "TendrlContext.integration_id", "help": "Tendrl managed/generated cluster id for the sds being managed by Tendrl", "type": "String", "default": null, "required": true }, { "name": "Cluster.node_configuration", "help": "Node configuration for the cluster nodes", "type": "Dict[]", "default": null, "required": true }, { "name": "Cluster.conf_overrides", "help": "Configuration overrides for the cluster", "type": "Dict", "default": null, "required": true } ] } But I don't know what attributes are applicable for Gluster and what for Ceph and also there is dictionary with unknown content "Cluster.conf_overrides". We know just that there should be gdeploy on every Gluster node and Ceph-installer on "server"(API, Etcd) node. Thank you for your 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 khartsoe at redhat.com Wed Apr 19 14:06:33 2017 From: khartsoe at redhat.com (Kenneth Hartsoe) Date: Wed, 19 Apr 2017 10:06:33 -0400 (EDT) Subject: [Tendrl-devel] Cluster create documentation In-Reply-To: <34268847-610e-8121-48b5-1accad4147d1@redhat.com> References: <34268847-610e-8121-48b5-1accad4147d1@redhat.com> Message-ID: <380155588.14269306.1492610793783.JavaMail.zimbra@redhat.com> Hi Martin....fyi....there are google downstream doc drafts available (which have not been tested yet, etc.) but at least provide a work flow: Create Gluster (DOC RFE BZ#1394696): https://docs.google.com/document/d/11wsw1n2yLtB6x5Vg3PQcjvSKO6CsSw1XyRG2JfCPr_A/edit Create Ceph (Doc RFE BZ#1432037): https://docs.google.com/document/d/1fLzcppLRHQCAG8AP3kERQjYYoQpD6xEBSOuEwzw8UzM/edit Ken Hartsoe Content Strategist Red Hat Storage Documentation khartsoe at redhat.com; IRC: khartsoe Office: 919 754 4770; Internal: 814 4770 ----- Original Message ----- | Hi all, | | I would like to ask where can I find documentation for create cluster because | it is not available in | UI so we would like to follow documentation. I cannot find it in: | - https://github.com/Tendrl/api/blob/master/docs/clusters.adoc | - https://github.com/Tendrl/documentation/tree/master/api | I can see output from Flows: | { | "name": "CreateCluster", | "method": "POST", | "attributes": [ | { | "name": "Node[]", | "type": "List", | "required": true | }, | { | "name": "TendrlContext.cluster_name", | "help": "Name of the cluster", | "type": "String", | "default": null, | "required": true | }, | { | "name": "TendrlContext.sds_name", | "help": "Name of the Tendrl managed sds, eg: 'gluster'", | "type": "String", | "default": null, | "required": true | }, | { | "name": "TendrlContext.sds_version", | "help": "Version of the Tendrl managed sds, eg: '3.2.1'", | "type": "String", | "default": null, | "required": true | }, | { | "name": "Cluster.public_network", | "help": "Public Network cidr of the cluster", | "type": "String", | "default": null, | "required": true | }, | { | "name": "Cluster.cluster_network", | "help": "Data Nework cidr of the cluster", | "type": null, | "default": null, | "required": true | }, | { | "name": "TendrlContext.integration_id", | "help": "Tendrl managed/generated cluster id for the sds being | managed by Tendrl", | "type": "String", | "default": null, | "required": true | }, | { | "name": "Cluster.node_configuration", | "help": "Node configuration for the cluster nodes", | "type": "Dict[]", | "default": null, | "required": true | }, | { | "name": "Cluster.conf_overrides", | "help": "Configuration overrides for the cluster", | "type": "Dict", | "default": null, | "required": true | } | ] | } | | But I don't know what attributes are applicable for Gluster and what for Ceph | and also there is | dictionary with unknown content "Cluster.conf_overrides". | We know just that there should be gdeploy on every Gluster node and | Ceph-installer on "server"(API, | Etcd) node. | | Thank you for your 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 | | _______________________________________________ | Tendrl-devel mailing list | Tendrl-devel at redhat.com | https://www.redhat.com/mailman/listinfo/tendrl-devel | From khartsoe at redhat.com Wed Apr 19 14:08:37 2017 From: khartsoe at redhat.com (Kenneth Hartsoe) Date: Wed, 19 Apr 2017 10:08:37 -0400 (EDT) Subject: [Tendrl-devel] RHS-C 3.0: ansible install method In-Reply-To: <104ced9e-e1b4-5999-86f8-69cb6eea151d@redhat.com> References: <1526008124.12160812.1492095439690.JavaMail.zimbra@redhat.com> <104ced9e-e1b4-5999-86f8-69cb6eea151d@redhat.com> Message-ID: <1411008870.14269912.1492610917161.JavaMail.zimbra@redhat.com> Hi Martin, Please forward the upstream ansible repo links, thanks. Ken Hartsoe Content Strategist Red Hat Storage Documentation khartsoe at redhat.com; IRC: khartsoe Office: 919 754 4770; Internal: 814 4770 ----- Original Message ----- | Hi Ken, | | On 04/13/2017 04:57 PM, Kenneth Hartsoe wrote: | > Looking for ansible playbooks to glean install method for inclusion in the | > RHS-C 3 doc. Please forward link, etc. Thank you. | | there is no downstream ansible based installation for now. There are 2 | upstream ones: one used by | Jeff and other one use and made by QE. There is agreement that installation | process will be more | clear after end of Beta and there will be some kind of merge from both | repositories to | tendrl-ansible repository with ansible playbooks for Tendrl installation. | | | -- | 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 | | _______________________________________________ | Tendrl-devel mailing list | Tendrl-devel at redhat.com | https://www.redhat.com/mailman/listinfo/tendrl-devel | From mkudlej at redhat.com Fri Apr 21 09:51:43 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Fri, 21 Apr 2017 11:51:43 +0200 Subject: [Tendrl-devel] Cluster create documentation In-Reply-To: <380155588.14269306.1492610793783.JavaMail.zimbra@redhat.com> References: <34268847-610e-8121-48b5-1accad4147d1@redhat.com> <380155588.14269306.1492610793783.JavaMail.zimbra@redhat.com> Message-ID: <7891a286-8a2c-aa3a-28ab-c04469744118@redhat.com> Hi Ken, thank you for these drafts but we need updated API functions documentation to be able to create cluster via API because there is no such option to do that via UI right now. And it is already available https://github.com/Tendrl/api/blob/master/docs/clusters.adoc#create-cluster On 04/19/2017 04:06 PM, Kenneth Hartsoe wrote: > Hi Martin....fyi....there are google downstream doc drafts available (which have not been tested yet, etc.) but at least provide a work flow: > > Create Gluster (DOC RFE BZ#1394696): https://docs.google.com/document/d/11wsw1n2yLtB6x5Vg3PQcjvSKO6CsSw1XyRG2JfCPr_A/edit > > Create Ceph (Doc RFE BZ#1432037): https://docs.google.com/document/d/1fLzcppLRHQCAG8AP3kERQjYYoQpD6xEBSOuEwzw8UzM/edit > > Ken Hartsoe > Content Strategist > Red Hat Storage Documentation > > khartsoe at redhat.com; IRC: khartsoe > Office: 919 754 4770; Internal: 814 4770 > > ----- Original Message ----- > | Hi all, > | > | I would like to ask where can I find documentation for create cluster because > | it is not available in > | UI so we would like to follow documentation. I cannot find it in: > | - https://github.com/Tendrl/api/blob/master/docs/clusters.adoc > | - https://github.com/Tendrl/documentation/tree/master/api > | I can see output from Flows: > | { > | "name": "CreateCluster", > | "method": "POST", > | "attributes": [ > | { > | "name": "Node[]", > | "type": "List", > | "required": true > | }, > | { > | "name": "TendrlContext.cluster_name", > | "help": "Name of the cluster", > | "type": "String", > | "default": null, > | "required": true > | }, > | { > | "name": "TendrlContext.sds_name", > | "help": "Name of the Tendrl managed sds, eg: 'gluster'", > | "type": "String", > | "default": null, > | "required": true > | }, > | { > | "name": "TendrlContext.sds_version", > | "help": "Version of the Tendrl managed sds, eg: '3.2.1'", > | "type": "String", > | "default": null, > | "required": true > | }, > | { > | "name": "Cluster.public_network", > | "help": "Public Network cidr of the cluster", > | "type": "String", > | "default": null, > | "required": true > | }, > | { > | "name": "Cluster.cluster_network", > | "help": "Data Nework cidr of the cluster", > | "type": null, > | "default": null, > | "required": true > | }, > | { > | "name": "TendrlContext.integration_id", > | "help": "Tendrl managed/generated cluster id for the sds being > | managed by Tendrl", > | "type": "String", > | "default": null, > | "required": true > | }, > | { > | "name": "Cluster.node_configuration", > | "help": "Node configuration for the cluster nodes", > | "type": "Dict[]", > | "default": null, > | "required": true > | }, > | { > | "name": "Cluster.conf_overrides", > | "help": "Configuration overrides for the cluster", > | "type": "Dict", > | "default": null, > | "required": true > | } > | ] > | } > | > | But I don't know what attributes are applicable for Gluster and what for Ceph > | and also there is > | dictionary with unknown content "Cluster.conf_overrides". > | We know just that there should be gdeploy on every Gluster node and > | Ceph-installer on "server"(API, > | Etcd) node. > | > | Thank you for your 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 > | > | _______________________________________________ > | Tendrl-devel mailing list > | Tendrl-devel at redhat.com > | https://www.redhat.com/mailman/listinfo/tendrl-devel > | > > _______________________________________________ > 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 dahorak at redhat.com Fri Apr 21 10:58:08 2017 From: dahorak at redhat.com (=?UTF-8?Q?Daniel_Hor=c3=a1k?=) Date: Fri, 21 Apr 2017 12:58:08 +0200 Subject: [Tendrl-devel] OSD create marked as failed with latest version of ceph-installer In-Reply-To: References: Message-ID: <1a55c604-3194-f9e0-c171-9a54c1e411e5@redhat.com> I've created the BZ for this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1444444 Regards, Daniel On 04/19/17 03:12, Andrew Schoen wrote: > I don't know of any BZ, but his PR seemed to fix the issue for me. > https://github.com/ceph/ceph-ansible/pull/1455 > > Here is a log from our upstream ceph-installer tests using the branch > from that PR: https://jenkins.ceph.com/view/ceph-installer/job/ceph-installer-tests-ansible2.2-nightly_centos7/114/consoleFull > > - Andrew > > On Tue, Apr 18, 2017 at 7:57 PM, Ken Dreyer wrote: >> Is this a regression in ceph-ansible v2.2.0 compared with v2.1.9? >> >> Do we have a BZ to track this? >> >> - Ken >> >> On Mon, Apr 17, 2017 at 4:15 PM, Sebastien Han wrote: >>> Looks like the /tmp/restart_osd_daemon.sh failed, is it possible to >>> run it manually to do further debugging? >>> I added a couple of comments here: >>> https://github.com/ceph/ceph-ansible/commit/5bec62ba7c8ecbc91ede05297dadb639c530f597 >>> >>> On Mon, Apr 17, 2017 at 8:50 AM, Alfredo Deza wrote: >>>> On Mon, Apr 17, 2017 at 9:01 AM, Nishanth Thomas wrote: >>>>> Alfredo, Andrew, >>>>> >>>>> >>>>> OSD create task returns a failure with latest version of >>>>> ceph-installer(http://download-node-02.eng.bos.redhat.com/rcm-guest/ceph-drops/auto/rhscon-2-rhel-7-compose/latest-RHSCON-2-RHEL-7/compose/Installer/x86_64/os/). >>>>> The OSDs are created and could see that is added to the cluster, but the >>>>> task is marked as failed. Please have a look at the task status api respose >>>>> at[1] >>>> >>>> Hey Guillaume, seems like this is something you added recently with >>>> https://github.com/ceph/ceph-ansible/commit/5bec62ba7c8ecbc91ede05297dadb639c530f597 >>>> >>>> Can you help out sorting it out? Ideally we would want better logging >>>> here (had to lookup the bash script to see why we would need to "check >>>> config") >>>> >>>> I also don't think we have 100% clean PGs in our tests anyway. >>>> >>>> >>>>> >>>>> Note that with a older >>>>> version(http://download-node-02.eng.bos.redhat.com/rcm-guest/ceph-drops/auto/rhscon-2-rhel-7-compose/RHSCON-2.0-RHEL-7-20170215.t.0/compose/Installer/x86_64/os/), >>>>> things are working as expected >>>>> >>>>> Please have a look at and let us know >>>>> >>>>> Thanks, >>>>> Nishanth >>>>> >>>>> [1]https://pastebin.com/Ncdu3sts >>> >>> >>> >>> -- >>> Cheers >>> >>> ?????? >>> S?bastien Han >>> Principal Software Engineer, Storage Architect >>> >>> "Always give 100%. Unless you're giving blood." >>> >>> Mail: seb at redhat.com >>> Address: 11 bis, rue Roqu?pine - 75008 Paris >>> >>> _______________________________________________ >>> Tendrl-devel mailing list >>> Tendrl-devel at redhat.com >>> https://www.redhat.com/mailman/listinfo/tendrl-devel >> >> _______________________________________________ >> Tendrl-devel mailing list >> Tendrl-devel at redhat.com >> https://www.redhat.com/mailman/listinfo/tendrl-devel > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > From dahorak at redhat.com Tue Apr 25 10:54:08 2017 From: dahorak at redhat.com (=?UTF-8?Q?Daniel_Hor=c3=a1k?=) Date: Tue, 25 Apr 2017 12:54:08 +0200 Subject: [Tendrl-devel] Latest tendrl-* packages in copr repo are not signed Message-ID: <5f5d5ced-e949-7ed0-dc09-e746f648cbef@redhat.com> Hi Tim and all, it seems, like there is some issue with the latest builds in tendrl copr repo[1]. The packages are not signed. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ # yumdownloader 'tendrl*' # rpm -qip tendrl-* | grep -e Name -e Signature -e Version Name : tendrl-alerting Version : 1.2.3 Signature : (none) Name : tendrl-api Version : 1.2.3 Signature : (none) Name : tendrl-api-doc Version : 1.2.3 Signature : (none) Name : tendrl-api-httpd Version : 1.2.3 Signature : (none) Name : tendrl-ceph-integration Version : 1.2.3 Signature : (none) Name : tendrl-commons Version : 1.2.3 Signature : (none) Name : tendrl-dashboard Version : 1.2.3 Signature : (none) Name : tendrl-gluster-integration Version : 1.2.3 Signature : (none) Name : tendrl-node-agent Version : 1.2.3 Signature : (none) Name : tendrl-node-monitoring Version : 1.2.3 Signature : (none) Name : tendrl-performance-monitoring Version : 1.2.3 Signature : (none) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [1] https://copr.fedorainfracloud.org/coprs/tendrl/tendrl/ Regards, Daniel From khartsoe at redhat.com Tue Apr 25 14:19:19 2017 From: khartsoe at redhat.com (Kenneth Hartsoe) Date: Tue, 25 Apr 2017 10:19:19 -0400 (EDT) Subject: [Tendrl-devel] RHS-C 3.0: Miration Tasks? In-Reply-To: <206040743.704518.1493129789784.JavaMail.zimbra@redhat.com> Message-ID: <1763172063.705920.1493129959492.JavaMail.zimbra@redhat.com> Hi Jeff, For customers with existing installs of RHGS 3.2/RHCS 2.x: are there any migration tasks, etc., that they need to perform prior to/related to installing RHS-C 3.0? I did not see anything in the MVP doc, etc., but wanted to make sure anything migration-related is not missed in the docs. Thank you. Ken Hartsoe Content Strategist Red Hat Storage Documentation khartsoe at redhat.com; IRC: khartsoe Office: 919 754 4770; Internal: 814 4770 From japplewh at redhat.com Tue Apr 25 15:03:42 2017 From: japplewh at redhat.com (Jeff Applewhite) Date: Tue, 25 Apr 2017 15:03:42 +0000 Subject: [Tendrl-devel] RHS-C 3.0: Miration Tasks? In-Reply-To: <1763172063.705920.1493129959492.JavaMail.zimbra@redhat.com> References: <206040743.704518.1493129789784.JavaMail.zimbra@redhat.com> <1763172063.705920.1493129959492.JavaMail.zimbra@redhat.com> Message-ID: Hi Ken It's a good question. For both Ceph and Gluster there should be a manual process to install and configure the node agent on each storage node, as well as an Ansible driven automated method to install and configure the node agent. This process should ideally not differ from Ceph to Gluster, although the mon vs osd distinction might require it. Jeff On Tue, Apr 25, 2017 at 10:19 AM Kenneth Hartsoe wrote: > Hi Jeff, > > > > For customers with existing installs of RHGS 3.2/RHCS 2.x: are there any > migration tasks, etc., that they need to perform prior to/related to > installing RHS-C 3.0? I did not see anything in the MVP doc, etc., but > wanted to make sure anything migration-related is not missed in the docs. > Thank you. > > > > Ken Hartsoe > > Content Strategist > > Red Hat Storage Documentation > > > > khartsoe at redhat.com; IRC: khartsoe > > Office: 919 754 4770; Internal: 814 4770 > > > > From mkudlej at redhat.com Wed Apr 26 07:58:29 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Wed, 26 Apr 2017 09:58:29 +0200 Subject: [Tendrl-devel] REST API consistency Message-ID: <8e1e89a1-2106-0209-a13b-96186d75fb60@redhat.com> Hi all, I think there is still time to unify Tendrl API functions according some rules. I've filed https://github.com/Tendrl/documentation/issues/70 couple of months ago without response. One example for all. There are these functions for Ceph cluster(Flows on cluster): "name": "CephCreatePool", "method": "POST", "name": "CephCreateECProfile", "method": "POST", "name": "CephDeleteECProfile", "method": "DELETE", "name": "CephCreateRbd", "method": "POST", "name": "CephDeleteRbd", "method": "DELETE", "name": "CephResizeRbd", "method": "PUT", "name": "CephDeletePool", "method": "DELETE", "name": "CephUpdatePool", "method": "PUT", and according documentation there should be also "name": "CephPoolList" "method": "GET" I think that there should be also "GET" "CephPool" because of performance. I think that these functions should be transformed avoiding verb duplicity. Also I believe if API function names are renamed integration with other projects will be much easier. Pool CRUD "name": ":ceph_cluster_id:/pool", "method": "POST", "name": ":ceph_cluster_id:/pool/:ceph_pool_id:", "method": "GET", "name": ":ceph_cluster_id:/pool/:ceph_pool_id:", "method": "PUT", "name": ":ceph_cluster_id:/pool/:ceph_pool_id:", "method": "DELETE", RBD CRUD "name": ":ceph_cluster_id:/rbd", "method": "POST", "name": ":ceph_cluster_id:/rbd/:ceph_pool_id:", "method": "GET", "name": ":ceph_cluster_id:/rbd/:ceph_pool_id:", "method": "PUT", "name": ":ceph_cluster_id:/rbd/:ceph_pool_id:", "method": "DELETE", EC Profile CRUD "name": ":ceph_cluster_id:/ecprofile", "method": "POST", "name": ":ceph_cluster_id:/ecprofile/:ec_profile_id:", "method": "GET", (update if it is possible) "name": ":ceph_cluster_id:/ecprofile/:ec_profile_id:", "method": "PUT", "name": ":ceph_cluster_id:/ecprofile/:ec_profile_id:", "method": "DELETE", Lists "name": ":ceph_cluster_id:/pool" "method": "GET" "name": ":ceph_cluster_id:/rbd" "method": "GET" "name": ":ceph_cluster_id:/ecprofile" "method": "GET" Please consider this rename until is not too late and there are not many projects which are integrated with Tendrl. -- 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 shtripat at redhat.com Wed Apr 26 09:04:47 2017 From: shtripat at redhat.com (Shubhendu Tripathi) Date: Wed, 26 Apr 2017 14:34:47 +0530 Subject: [Tendrl-devel] Fwd: [Gluster-devel] drop-in management/control panel In-Reply-To: <1973780179.1265.1493141153632.JavaMail.zimbra@li.nux.ro> References: <1973780179.1265.1493141153632.JavaMail.zimbra@li.nux.ro> Message-ID: <7c9ce0c3-8a95-5da9-504d-7267b1ea4d75@redhat.com> Adding tendrl-devel list. Regards, Shubhendu -------- Forwarded Message -------- Subject: [Gluster-devel] drop-in management/control panel Date: Tue, 25 Apr 2017 18:25:53 +0100 (BST) From: Nux! To: Gluster Devel Hi, Anyone knows of any solutions I can just drop in my current gluster setup and help me with administrative tasks (create, delete, quota, acl etc) from a web ui? Thanks, Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro _______________________________________________ Gluster-devel mailing list Gluster-devel at gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel From mkudlej at redhat.com Thu Apr 27 04:33:40 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Thu, 27 Apr 2017 06:33:40 +0200 Subject: [Tendrl-devel] Fwd: New ceph-mgr rest API In-Reply-To: <1493222895.4902.19.camel@redhat.com> References: <1493222895.4902.19.camel@redhat.com> Message-ID: <9b305d10-c925-59e3-a6c7-90be934f7ac5@redhat.com> Hi, please read this email about ceph-mgr. -------- Forwarded Message -------- Subject: New ceph-mgr rest API Date: Wed, 26 Apr 2017 09:08:15 -0700 From: Boris Ranto Organization: Red Hat To: Martin Kudlej Hi Martin, I am working on a new ceph-mgr rest API. It is written in pecan so it does not require any new dependencies, simplifies the code a lot (it is ~1/4th of the original django-based rest api), does provide us with a wider developer base (most people that do REST in the team use pecan for it), should be really simple to use from the client side (*), is much more lightweight and much faster (I could do ~150 requests per second on a single notebook while it was running in a VM). The patches are located at https://github.com/ceph/ceph/pull/14457 Please note that there is currently a bug in the latest master in ceph- mgr itself (C++ bits) that breaks python's handle_command interface and hence, it breaks the user creation. I did add a default admin/admin user/password so that the PR could be tested. There is a chacra repo with the packages for testing as well: https://1.chacra.ceph.com/r/ceph/wip-rest-flask/453724112df1bdb0828aafa 9ab9143555cb9d15d/centos/7/flavors/default/ Could you please CC any Storage console developers that might be interested in the API so that they could review and comment as well? Regards, Boris (*) The client just needs to send a request and authenticate with HTTP basic auth, i.e. import requests data = requests.get('https://:8002/osd', auth=('admin', 'admin'), verify=False).json() -- 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 adeza at redhat.com Fri Apr 28 14:10:39 2017 From: adeza at redhat.com (Alfredo Deza) Date: Fri, 28 Apr 2017 10:10:39 -0400 Subject: [Tendrl-devel] REST API consistency In-Reply-To: <8e1e89a1-2106-0209-a13b-96186d75fb60@redhat.com> References: <8e1e89a1-2106-0209-a13b-96186d75fb60@redhat.com> Message-ID: On Wed, Apr 26, 2017 at 3:58 AM, Martin Kudlej wrote: > Hi all, > > I think there is still time to unify Tendrl API functions according some > rules. > I've filed https://github.com/Tendrl/documentation/issues/70 couple of > months ago without response. > > One example for all. > There are these functions for Ceph cluster(Flows on cluster): > "name": "CephCreatePool", > "method": "POST", > > "name": "CephCreateECProfile", > "method": "POST", > > "name": "CephDeleteECProfile", > "method": "DELETE", > > "name": "CephCreateRbd", > "method": "POST", > > "name": "CephDeleteRbd", > "method": "DELETE", > > "name": "CephResizeRbd", > "method": "PUT", > > "name": "CephDeletePool", > "method": "DELETE", > > "name": "CephUpdatePool", > "method": "PUT", > > and according documentation there should be also > "name": "CephPoolList" > "method": "GET" > > I think that there should be also "GET" "CephPool" because of performance. > > I think that these functions should be transformed avoiding verb duplicity. > Also I believe if API function names are renamed integration with other > projects will be much easier. > > Pool CRUD > "name": ":ceph_cluster_id:/pool", > "method": "POST", > > "name": ":ceph_cluster_id:/pool/:ceph_pool_id:", > "method": "GET", > > "name": ":ceph_cluster_id:/pool/:ceph_pool_id:", > "method": "PUT", > > "name": ":ceph_cluster_id:/pool/:ceph_pool_id:", > "method": "DELETE", > > RBD CRUD > > "name": ":ceph_cluster_id:/rbd", > "method": "POST", > > "name": ":ceph_cluster_id:/rbd/:ceph_pool_id:", > "method": "GET", > > "name": ":ceph_cluster_id:/rbd/:ceph_pool_id:", > "method": "PUT", > > "name": ":ceph_cluster_id:/rbd/:ceph_pool_id:", > "method": "DELETE", > > EC Profile CRUD > > "name": ":ceph_cluster_id:/ecprofile", > "method": "POST", > > "name": ":ceph_cluster_id:/ecprofile/:ec_profile_id:", > "method": "GET", > > (update if it is possible) > "name": ":ceph_cluster_id:/ecprofile/:ec_profile_id:", > "method": "PUT", > > "name": ":ceph_cluster_id:/ecprofile/:ec_profile_id:", > "method": "DELETE", > > > Lists > > "name": ":ceph_cluster_id:/pool" > "method": "GET" > > "name": ":ceph_cluster_id:/rbd" > "method": "GET" > > "name": ":ceph_cluster_id:/ecprofile" > "method": "GET" > These are a prime example of a good Restful HTTP API approach. The Pecan project describes this way of presenting an API as "overloading URLs based on request method" [0] and it greatly simplifies the URLs and makes it much easier to consume as a client. [0] https://pecan.readthedocs.io/en/latest/rest.html#writing-restful-web-services-with-generic-controllers > Please consider this rename until is not too late and there are not many > projects which are integrated with Tendrl. This is a great suggestion Martin! > > -- > 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 > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel From rghatvis at redhat.com Sat Apr 29 12:32:52 2017 From: rghatvis at redhat.com (Bobb Gt) Date: Sat, 29 Apr 2017 18:02:52 +0530 Subject: [Tendrl-devel] Bobb PTO Message-ID: I am on PTO from May 02 - May 10 and May 15 - May 24, 2017. For any doc stuff, please content Kenneth Hartsoe(khartsoe at redhat.com) or Anjana Sriram( asriram at redhat.com). Thanks, [image: photo] Bobb GT Technical Writer, Red Hat Inc Mobile: +91 8411001236 Website: redhat.com Division: Customer Content Services APAC Get a signature like this: Click here! From rghatvis at redhat.com Sat Apr 29 13:15:29 2017 From: rghatvis at redhat.com (Bobb Gt) Date: Sat, 29 Apr 2017 18:45:29 +0530 Subject: [Tendrl-devel] Where on Earth is Bobb? Message-ID: Bobb will be navigating the treacherous waters of the Indian Ocean in an exhilarating expedition to discover exotic reefs, limestone sea caves and also keeping an eye on possible sightings of the MH370 wreckage. Bobb will resume his love for fishing and attempt to hook some red snappers using his junky fishing line. The off dates for Bobb: May 02 - May 10 and May 15 - May 24, 2017. For any Storage Console doc stuff, please contact Homestead Alumnus - Kenneth Hartsoe (khartsoe at redhat.com) and/or Anjana Sriram ( asriram at redhat.com). Bobb quote: *You know what they say? A bad day fishing beats a great day at office!* ;) Ahoy mates, cya! [image: photo] Bobb GT Technical Writer, Red Hat Inc Mobile: +91 8411001236 <+91%208411001236> Website: redhat.com Division: Customer Content Services APAC Get a signature like this: Click here!