Skip to content
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

Centralized user and label tree repository #169

Closed
mzur opened this issue Sep 11, 2018 · 3 comments
Closed

Centralized user and label tree repository #169

mzur opened this issue Sep 11, 2018 · 3 comments

Comments

@mzur
Copy link
Member

mzur commented Sep 11, 2018

Goal: Users should be able to use their user account, label trees and projects in every BIIGLE instance.

This goal is in conflict with our current approach of decentralized BIIGLE instances and transfer of data via import/export. One possible idea for implementation is this:

  • Use only a single global BIIGLE instance (ours).
  • Implement BIIGLE "image servers" that are installed on-premise at the various institutions. These image servers can be connected to the global instance and provide image files that are stored on the servers of the institution. Users of the global instance can be authorized to access different image servers so they can create new volumes with images provided by the image server.
  • BIIGLE on the ship stays the same with no connection to the global instance. Users, label trees and volumes have to be im-/exported.

This is based on the assumption that the only motivation of the institutions currently maintaining their own BIIGLE instance is that they don't want to publish their images.

I don't really like this idea as the current decentralized solution has some benefits, too. I doubt that Senckenberg and Geomar want to give up their instances. If they don't, we don't gain anything but additional complexity by the implementation of the idea described above.

@mzur
Copy link
Member Author

mzur commented Oct 5, 2018

After a discussion with the Geomar people, we concluded that the centralized approach described above could indeed be a viable solution. But the most important issue in this case would be user trust. Users would have to be able to trust the entity which maintains BIIGLE with their data (if not their images). This is a similar situation like Pangaea which is maintained by a central authority.

  1. The centralized BIIGLE instance must be maintained by a trusted authority.
  2. BIIGLE might have to be deployed on a server infrastructure that is a little more reliable than the UniBi OpenStack.
  3. Convenient use of images imported from Pangaea would be a huge plus. ( Import volumes from Pangaea #95 )
  4. BIIGLE open source would also improve user trust. ( Software license/open source #154 )
  5. Support for an authentication service like Shibboleth may be a nice solution for new user registration of the centralized instance. ( Automatic registration #173 )

@mzur
Copy link
Member Author

mzur commented Jan 22, 2019

After some discussion with Tim, I tend to prefer a decentralized version that is very similar to what we have today. Every institute maintains its ownl BIIGLE instance but the instances can share data with im-/exports. But the final decision is up to the project partners.

screenshot from 2019-01-22 09-33-34
screenshot from 2019-01-22 09-33-41

@mzur
Copy link
Member Author

mzur commented Dec 11, 2019

Continued in #208.

@mzur mzur closed this as completed Dec 11, 2019
@mzur mzur removed the discuss label Dec 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant