Description of problem: Via design HDD cannot be used as dedicated journal. However during current create ceph cluster workflow it is possible to choose HDD as the location where dedicated journal should be. Moreover NVMe is missing there. Version-Release number of selected component (if applicable): tendrl-node-agent-3.0-alpha.8.el7scon.noarch tendrl-commons-3.0-alpha.8.el7scon.noarch tendrl-performance-monitoring-3.0-alpha.6.el7scon.noarch tendrl-api-3.0-alpha.4.el7scon.noarch tendrl-api-httpd-3.0-alpha.4.el7scon.noarch tendrl-dashboard-3.0-alpha.4.el7scon.noarch tendrl-alerting-3.0-alpha.3.el7scon.noarch tendrl-api-doc-3.0-alpha.4.el7scon.noarch How reproducible: 100% Steps to Reproduce: 1. Start to create a ceph cluster 2. Check possible targets for dedicated journal 3. Actual results: There are SSD and HDD as possible location for dedicated journal. NVMe is missing. (Moreover SSD is provided as possible location even when there is no SSD.) Expected results: There should be displayed only SSD and NVMe as possible targets. (If there is no such disk on node, dedicated should not be provided at all.) This one depends on our implementation, however it seems logical to not provide what cannot be satisfied. Additional info:
Is there any specific reason why HDD cannot be used as a dedicated journal? Ceph supports it and it is perfectly valid configuration and the recommendation to use HDD as whole to be used as journal, no partitions allowed as we do for SSDs or NVMEs. As of now the journal mapping is done by backend and not manually done as mentioned in the design, so these options(to choose no of partitions per device) will be removed in the upcoming build. NVMe is not supported as of now. Its more of `future` enhancement we are looking at the moment
(In reply to Nishanth Thomas from comment #2) > Is there any specific reason why HDD cannot be used as a dedicated journal? > Ceph supports it and it is perfectly valid configuration and the > recommendation to use HDD as whole to be used as journal, no partitions > allowed as we do for SSDs or NVMEs. > > As of now the journal mapping is done by backend and not manually done as > mentioned in the design, so these options(to choose no of partitions per > device) will be removed in the upcoming build. > > NVMe is not supported as of now. Its more of `future` enhancement we are > looking at the moment You're right HDD could be used as dedicated journal I read design badly. So only the small issue remains that tendrl provides options which are not available. Hence lowering priority.
This product is EOL now