On Sep 1, 2011, at 1:42 PM, Christopher Brooks wrote: > Hi Tobias, > > We looked at this, but I think I missed something important. Eg on > admin we have something like: > > org.opencastproject.server.url=http://mhadmin.telavivuniv.org > > and on the workers we have: > > org.opencastproject.server.url=http://mhworker.telavivuniv.org > org.opencastproject.admin.ui.url=http://mhadmin.telavivuniv.org > > So I thought our workers should be accessing the admin correctly, and > that the admin url was being used as the default organization. But I > see Josh wrote > >> The value set with "org.opencastproject.server.url" in >> config.properties determines the "default organization" in Matterhorn >> 1.2. So it looks like you've set org.opencastproject.server.url to > > So should we be telling our workers that their server.url is actually > mhadmin? >
No. Each server has at least one URL on which it can be accessed. That includes inter-server access to REST endpoints (e.g. an admin server calling a worker). The public URL for the server is the value you want to set in org.opencastproject.server.url. If you choose to add more DNS pointers to that server, you can associate multiple organizations with the machine. This allows for different branding, authentication, etc based on the URL. There's diagram [1] on the wiki that shows how this works. > Also, I see josh wrote: > >> In the trunk (1.3-SNAPSHOT), you can register any number of >> organizations with specific host names and/or ports, enabling >> multiple customers to run on a single matterhorn instance or cluster, >> each with their own branding, authentication scheme, etc. > > Where do we register new organizations and set information about them? Add a file named org.opencastproject.organization-[id].cfg to $FELIX/load or any other watch directory, where [id] is the tenant's ID. You can register new security configurations for this tenant in $FELIX/conf/security/[id].xml The format is described at [2]. > > What's the use case for workers to be in different organizations? Different security configurations (what roles have access, depending on which org), branding of the rest docs, etc. Josh > > Chris > -- [1] http://opencast.jira.com/wiki/x/H4P0 [2] http://opencast.jira.com/wiki/x/JACHAQ Hope that helps, Josh _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
