-
Notifications
You must be signed in to change notification settings - Fork 3
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
make index.bob filename unique #130
Comments
There is an issue regarding this but I'm not expecting rapid results |
So this is an issue for:
So at DLS this would only be if we were making developer changes to multiple IOCs at the same time. Is that something we see ourselves doing much? Having said that, the only reason to choose a well known If we do make this change, I slightly prefer |
I've discussed this with @GDYendell. I have come to feel uneasy about it too as its making a change for a corner case that affects our pretty K8S world. I don't particularly like I think I also have a workaround for the issue in podman which is to use bind mounts. So closing |
Would it be reasonable for the generated index.bob filename to instead be $IOC_NAME-index.bob when being generated by ibek's runtime generate function?
Use case:
In the new world of docker compose for beamlines that deploy direct to docker/podman I have an issue with the opis volume mount. docker behaves beautifully like K8S and allows each service to mount a subfolder of the opis volume. But podman does not - it ignores the subpath argument and mounts the root.
Thus for podman our index.bob overwrite each other.
Unique index names seems quite nice because imaging two AD iocs - they will overwrite each other's NDPluginPva.pvi.bob for example, but that will not matter because it is the same for all IOCs and the index supplies the Macros to make the page unique.
@coretl @GDYendell what do you think?
The text was updated successfully, but these errors were encountered: