From rdias at suse.com Thu Aug 17 08:46:46 2017 From: rdias at suse.com (Ricardo Dias) Date: Thu, 17 Aug 2017 15:46:46 +0100 Subject: [Deepsea-users] DeepSea execution progress tracking POC Message-ID: <1502981206.32340.16.camel@suse.com> Hi all, During my vacations I played a bit with salt events and I did a small POC of how we could show the progress of DeepSea execution. Currently the POC is just listening the salt event bus for DeepSea events and shows a progress bar when some DeepSea stage is executed. Follow the link to see this POC in action: https://asciinema.org/a/tHrLWgtWJve92d8pyYNxpyUKN In the video, I run stage 0-4 in an external session, and the video shows the progress bar for each stage that is executed. Hope you like it! -- Ricardo Dias Senior Software Engineer - Storage Team SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From holgi at suse.com Thu Aug 17 09:03:28 2017 From: holgi at suse.com (Holger Sickenberg) Date: Thu, 17 Aug 2017 17:03:28 +0200 Subject: [Deepsea-users] DeepSea execution progress tracking POC In-Reply-To: <1502981206.32340.16.camel@suse.com> References: <1502981206.32340.16.camel@suse.com> Message-ID: <91b9cef5-19b5-eed6-f21b-007537301a06@suse.com> Hi Ricardo, On 17.08.2017 16:46, Ricardo Dias wrote: > During my vacations I played a bit with salt events and I did a small > POC of how we could show the progress of DeepSea execution. > > Currently the POC is just listening the salt event bus for DeepSea > events and shows a progress bar when some DeepSea stage is executed. > > Follow the link to see this POC in action: > > https://asciinema.org/a/tHrLWgtWJve92d8pyYNxpyUKN > > In the video, I run stage 0-4 in an external session, and the video > shows the progress bar for each stage that is executed. > > Hope you like it! Yes, I like it very much. Well done! Best wishes Holger -- SUSE Linux GmbH, Maxfeldstra?e 5, D-90409 N?rnberg GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) T: +49 (0) 911 74053-0, F: +49 (0) 911 74053-483 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From lmorris at suse.com Thu Aug 17 09:28:46 2017 From: lmorris at suse.com (Larry Morris) Date: Thu, 17 Aug 2017 15:28:46 +0000 Subject: [Deepsea-users] DeepSea execution progress tracking POC In-Reply-To: <1502981206.32340.16.camel@suse.com> References: <1502981206.32340.16.camel@suse.com> Message-ID: <65144C5C80746A4EB8869FE3F027358D063CEDD9@prvxmb04.microfocus.com> Ricardo: Very nice addition. Best, Larry -----Original Message----- From: deepsea-users-bounces at lists.suse.com [mailto:deepsea-users-bounces at lists.suse.com] On Behalf Of Ricardo Dias Sent: Thursday, August 17, 2017 8:47 AM To: ceph at suse.de; deepsea-users at lists.suse.com Subject: [Deepsea-users] DeepSea execution progress tracking POC Hi all, During my vacations I played a bit with salt events and I did a small POC of how we could show the progress of DeepSea execution. Currently the POC is just listening the salt event bus for DeepSea events and shows a progress bar when some DeepSea stage is executed. Follow the link to see this POC in action: https://asciinema.org/a/tHrLWgtWJve92d8pyYNxpyUKN In the video, I run stage 0-4 in an external session, and the video shows the progress bar for each stage that is executed. Hope you like it! -- Ricardo Dias Senior Software Engineer - Storage Team SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) _______________________________________________ Deepsea-users mailing list Deepsea-users at lists.suse.com http://lists.suse.com/mailman/listinfo/deepsea-users From joao at suse.de Thu Aug 17 09:41:02 2017 From: joao at suse.de (Joao Eduardo Luis) Date: Thu, 17 Aug 2017 16:41:02 +0100 Subject: [Deepsea-users] DeepSea execution progress tracking POC In-Reply-To: <1502981206.32340.16.camel@suse.com> References: <1502981206.32340.16.camel@suse.com> Message-ID: On 08/17/2017 03:46 PM, Ricardo Dias wrote: > Hope you like it! > oooh, fancy ;) -Joao From lgrimmer at suse.com Thu Aug 17 09:42:50 2017 From: lgrimmer at suse.com (Lenz Grimmer) Date: Thu, 17 Aug 2017 17:42:50 +0200 Subject: [Deepsea-users] DeepSea execution progress tracking POC In-Reply-To: <1502981206.32340.16.camel@suse.com> References: <1502981206.32340.16.camel@suse.com> Message-ID: Hi Ricardo, On 08/17/2017 04:46 PM, Ricardo Dias wrote: > During my vacations I played a bit with salt events and I did a small > POC of how we could show the progress of DeepSea execution. > > Currently the POC is just listening the salt event bus for DeepSea > events and shows a progress bar when some DeepSea stage is executed. > > Follow the link to see this POC in action: > > https://asciinema.org/a/tHrLWgtWJve92d8pyYNxpyUKN > > In the video, I run stage 0-4 in an external session, and the video > shows the progress bar for each stage that is executed. > > Hope you like it! I like it very much, this is an excellent usability improvement. When do you submit a PR for this? ;) Lenz -- SUSE Linux GmbH - Maxfeldstr. 5 - 90409 Nuernberg (Germany) GF:Felix Imend?rffer,Jane Smithard,Graham Norton,HRB 21284 (AG N?rnberg) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From abonilla at suse.com Thu Aug 17 13:28:03 2017 From: abonilla at suse.com (Alejandro Bonilla) Date: Thu, 17 Aug 2017 19:28:03 +0000 Subject: [Deepsea-users] DeepSea execution progress tracking POC In-Reply-To: <1502981206.32340.16.camel@suse.com> References: <1502981206.32340.16.camel@suse.com> Message-ID: <60444949-F46F-4C49-B80D-F24B86A05330@suse.com> Very Cool!!! I?d like to see how it spits out errors from a stage and then we?d be gold! > On Aug 17, 2017, at 10:46 AM, Ricardo Dias wrote: > > Hi all, > > During my vacations I played a bit with salt events and I did a small > POC of how we could show the progress of DeepSea execution. > > Currently the POC is just listening the salt event bus for DeepSea > events and shows a progress bar when some DeepSea stage is executed. > > Follow the link to see this POC in action: > > https://asciinema.org/a/tHrLWgtWJve92d8pyYNxpyUKN > > In the video, I run stage 0-4 in an external session, and the video > shows the progress bar for each stage that is executed. > > Hope you like it! > -- > Ricardo Dias > Senior Software Engineer - Storage Team > SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, > HRB 21284 > (AG N?rnberg) > _______________________________________________ > Deepsea-users mailing list > Deepsea-users at lists.suse.com > http://lists.suse.com/mailman/listinfo/deepsea-users From rdias at suse.com Thu Aug 17 14:44:05 2017 From: rdias at suse.com (Ricardo Dias) Date: Thu, 17 Aug 2017 21:44:05 +0100 Subject: [Deepsea-users] DeepSea execution progress tracking POC In-Reply-To: <60444949-F46F-4C49-B80D-F24B86A05330@suse.com> References: <1502981206.32340.16.camel@suse.com> <60444949-F46F-4C49-B80D-F24B86A05330@suse.com> Message-ID: > On 17 Aug 2017, at 20:28, Alejandro Bonilla wrote: > > Very Cool!!! > > I?d like to see how it spits out errors from a stage and then we?d be gold! > I already have a few ideas for that. If I have the time I'll make a new video with that. > >> On Aug 17, 2017, at 10:46 AM, Ricardo Dias wrote: >> >> Hi all, >> >> During my vacations I played a bit with salt events and I did a small >> POC of how we could show the progress of DeepSea execution. >> >> Currently the POC is just listening the salt event bus for DeepSea >> events and shows a progress bar when some DeepSea stage is executed. >> >> Follow the link to see this POC in action: >> >> https://asciinema.org/a/tHrLWgtWJve92d8pyYNxpyUKN >> >> In the video, I run stage 0-4 in an external session, and the video >> shows the progress bar for each stage that is executed. >> >> Hope you like it! >> -- >> Ricardo Dias >> Senior Software Engineer - Storage Team >> SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, >> HRB 21284 >> (AG N?rnberg) >> _______________________________________________ >> Deepsea-users mailing list >> Deepsea-users at lists.suse.com >> http://lists.suse.com/mailman/listinfo/deepsea-users > > _______________________________________________ > Deepsea-users mailing list > Deepsea-users at lists.suse.com > http://lists.suse.com/mailman/listinfo/deepsea-users From sen.lin at suse.com Wed Aug 23 19:46:28 2017 From: sen.lin at suse.com (Sen Lin) Date: Thu, 24 Aug 2017 01:46:28 +0000 Subject: [Deepsea-users] [ses-users] Failed to reconfigure lrdb In-Reply-To: <2211402.8jqTtfIN3J@fury.home> References: <07D131661AF6074BA20564C8482356AA24B8321F@BLRXMB01.microfocus.com> <2211402.8jqTtfIN3J@fury.home> Message-ID: <1503539183.4894.11.camel@suse.com> -----Original Message----- From: Eric Jackson > Reply-to: Discussions about the DeepSea management framework for Ceph To: deepsea-users at lists.suse.com > Subject: Re: [Deepsea-users] [ses-users] Failed to reconfigure lrdb Date: Wed, 23 Aug 2017 14:28:29 +0000 Hi Sen, On Wednesday, August 23, 2017 01:49:24 PM Sen Lin wrote: Hi, Environment: SES5 Milestone10 Failed to transfer iscsi gateway from sesnode04 to sesnode01. My step: 1. Modify policy.cfg ...... # IGW role-igw/stack/default/ceph/minions/sesnode01.suse.com.yml role-igw/cluster/sesnode01.suse.com.sls ...... 2. salt-run state.orch ceph.stage.2 3. salt-run state.orch ceph.stage.4 but with error: ... ---------- ID: iscsi import snip Name: . /etc/sysconfig/lrbd; lrbd -v $LRBD_OPTIONS -f /tmp/lrbd.conf Result: False Comment: Command ". /etc/sysconfig/lrbd; lrbd -v $LRBD_OPTIONS -f /tmp/lrbd.conf" run Started: 21:26:44.948704 default.rgw.buckets.index ERROR: pool 'iscsi-images' does not exist stdout: Summary for sesnode01.suse.com ------------ Succeeded: 2 (changed=1) Failed: 1 Did the iscsi-images pool get created? Verify with rados lspools sen: No. In my mind, it should be created at stage.4, right? Why not create automatically? ... Then I check the file, it still target sesnode04, not sesnode01 sesadmin:/srv/salt/ceph/igw/cache # more lrbd.conf {"pools": [{"gateways": [{"tpg": [{"image": "demo", "lun": "0"}], "target": "iqn.2016-11.org.linux-iscsi.igw.x86:sn.demo"}], "pool": "iscsi-images"}], "portals": [{"name": " portal-sesnode04-1", "addresses": ["192.168.101.14"]}], "targets": [{"hosts": [{"host": "sesnode04", "portal": "portal-sesnode04-1"}], "target": "iqn.2016-11.org.linux-iscsi .igw.x86:sn.demo"}], "auth": [{"authentication": "none", "target": "iqn.2016-11.org.linux-iscsi.igw.x86:sn.demo"}]} My question: 1. Why the lrbd.conf still point to sesnode04? Why not clear it with stage.2 and stage.4? 2. Any special steps needed to clear the info saved before? What does salt-run select.minions cluster=ceph roles=igw host=True return? This command is executed to fill in the template in .../ceph/igw/files/lrbd.conf.j2. If that returns sesnode01, then run salt 'admin.ceph' state.apply ceph.igw.config and verify that the .../ceph/igw/cache/lrbd.conf is correct. That is the first step in the orchestration (see /srv/salt/ceph/stage/iscsi/default.sls). If this is still wrong, then we need to investigate further. sen: I have fixed this issue manually, but I suspect the mechanism is not working well. So I do another test. Can you help me to analyze? I tried to move igw from sesnode01 to sesnode02. (1)sesadmin:/srv/pillar/ceph/proposals # more policy.cfg ... # IGW role-igw/stack/default/ceph/minions/sesnode02.suse.com.yml role-igw/cluster/sesnode02.suse.com.sls ... (2) run stage.2 successfully (3) sesadmin:/srv/pillar/ceph/proposals # salt-run select.minions cluster=ceph roles=igw host=True - sesnode02 (4) sesadmin:/srv/pillar/ceph/proposals # salt 'admin.ceph' state.apply ceph.igw.config No minions matched the target. No command was sent, no jid was assigned. ERROR: No return received sesadmin:/srv/pillar/ceph/proposals # salt 'sesnode02.suse.com' state.apply ceph.igw.config sesnode02.suse.com: Name: igw configured by gui - Function: test.nop - Result: Clean Started: - 09:34:58.706790 Duration: 0.578 ms Summary for sesnode02.suse.com ------------ Succeeded: 1 Failed: 0 ------------ Total states run: 1 Total run time: 0.578 ms (5) But in this file lrbd.conf, it still point to sesnode01 sesadmin:/srv/salt/ceph/igw/cache # more lrbd.conf {"pools": [{"gateways": [{"tpg": [{"image": "demo", "lun": "0"}], "target": "iqn.2016-11.org.linux-iscsi.igw.x86:sn.demo"}], "pool": "iscsi-images"}], "portals": [{"name": " portal-sesnode01.suse.com-1", "addresses": ["192.168.101.11"]}], "targets": [{"hosts": [{"host": "sesnode01.suse.com", "portal": "portal-sesnode01.suse.com-1"}], "target": " iqn.2016-11.org.linux-iscsi.igw.x86:sn.demo"}], "auth": [{"authentication": "none", "target": "iqn.2016-11.org.linux-iscsi.igw.x86:sn.demo"}]} Eric BR/Sen -------------- next part -------------- An HTML attachment was scrubbed... URL: