-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
device alias playbook problem #8
Comments
I am getting the same too. Is there a workaround? |
I think this only works on their servers - if somehow we could know what info is needed, we could maybe provide them with a script |
The aim of dmap is to make
These correspond to the named drive slots in an AV15 Storinator. But if you want to make your own vdev_id.conf file on each osd node. Start by running this on all osd nodes first: Then if you want to create your own device aliases, add them the device alias playbook will finish if you have We have udev rules, and a script that runs when the rule fires that will reference dmap, when successful, will also ensure that the required files are present and then run Those files are as follows: So, in summary: eg: Then trigger the udev rules: and as a sanity check, see that the devices show up in That should let the Hope that helps, sorry for taking so long to respond. |
hello,
trying to run this on ubuntu20 - third playbook ( device alias )gives an error
also on server when I run lsdev - I have this error
root@ceph1:~# lsdev
Error opening /etc/vdev_id.conf. Run
dmap
.after running dmap this is the result
this is the content of the /etc/45drives/server_info/server_info.json file
The text was updated successfully, but these errors were encountered: