motr BE segment size should be configurable about cortx-motr

[kaustubh-d]

Noticed there is a pillar in https://github.com/Seagate/cortx-prvsnr/blob/dev/pillar/components/motr.sls#L47
Wondering if motr team needs to use and apply this in config stage?

Stage - Config Motr:
  cmd.run:
    - name: __slot__:salt:setup_conf.conf_cmd('/opt/seagate/cortx/motr/conf/setup.yaml', 'core:config')

cc @madhavemuri

[madhavemuri]

This is not used, instead motr internal conf update mechanism is present.
But this is not currently configurable.

[kaustubh-d]

Ok, this should be made configurable for open source.

[ypise]

@kaustubh-d , @madhavemuri,
If we agree this is to be addressed in more sources, I'll be closing it from Provisioner issues.
It seems there's no provision to transfer issues in GitHub like we do in JIRA. @mukul-seagate11 any idea if we can transfer issues?

[mukul-seagate11]

@kaustubh-d , @madhavemuri,
If we agree this is to be addressed in more sources, I'll be closing it from Provisioner issues.
It seems there's no provision to transfer issues in GitHub like we do in JIRA. @mukul-seagate11 any idea if we can transfer issues?

@ypise I dont see this feature is available right now, let me still verify from GitHub team

[ypise]

@mukul-seagate11 , @justinzw ,
Consider this issue as candidate for transfer to cortx-motr.

[stale]

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @83bhp @andkononykhin2 for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

[kaustubh-d]

imho, we should still have way from provisioner to configure this as opens source community may have different sized metadata drives. Even storage state needs to be made configurable here https://github.com/Seagate/cortx-prvsnr/blob/dev/srv/components/system/storage/config.sls#L40-L44

[kaustubh-d]

Related to Seagate/cortx-prvsnr#271

[ypise]

@mukul-seagate11
Please transfer this issue to cortx-motr so that @madhavemuri can address and close this one.

[stale]

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @huanghua78 @mukundkanekar for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

[r-wambui]

@madhavemuri Any update on this? has this been implemented?

[stale]

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @nkommuri @mehjoshi @huanghua78 for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

[stale]

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @nkommuri @mehjoshi @huanghua78 for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

[stale]

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @nkommuri @mehjoshi @huanghua78 for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

[nkommuri]

@vidyadhar-pinglikar Is this something being considered as part of Partition STOB implementation?

[stale]

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @nkommuri @mehjoshi @huanghua78 for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

[nkommuri]

Response from Vidyadhar...

[12/13/2021 1:00 PM] Vidyadhar Pinglikar
seg size is provided on cmdline which is typically i guess from sysconfig; partition stob will use that size if provided on cmdline and if not will compute by itself

so to be specific i guess partition stob wont address it; and is out of scope of it.., it just use the size received from cmdline as i/p

in future when hare config will be used may be this will be implemented

[stale]

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @nkommuri @mehjoshi @huanghua78 for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

[chandradharraval]

Added hare component as well

[chandradharraval]

Hi @madhavemuri , @vidyadhar-pinglikar ,
Do we still need this if partition stob will not be implemented?

[stale]

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @nkommuri @mehjoshi @huanghua78 for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

[cortx-admin]

Madhav Vemuri commented in Jira Server:

This is already covered through the size of meta-data device passed in solution.yaml.

[~520479] [~530903]: This ticket can be closed.

[cortx-admin]

Chandradhar Raval commented in Jira Server:

Marking this issue Closed based on above comments