Folks who are managing their own phalanx deployments should take note of our new discovery service called Repertoire.
Repertoire is a data and service discovery layer that enables Phalanx applications to auto-discover servce endpoints available in the same cluster and adjust their functionality on the basis of what services are available. Moreover, Repertoire is data-aware and can be used to discover available datasets. For example, this would allow services that you have running on a development cluster to address a different set of test data that what you have in your production cluster.
Using Repertoire
-
If you have been keeping up to date with Phalanx releases, you already have Repertoire deployed and core services such as Nublado are already using it. You might want to configure it to know about datasets you have available. See our production configuration as an example. More documentation is forthcoming.
-
If you have not updated your Phalanx deployment since before Repertoire was added (December 18th 2025), note that next time you update you will have to sync the
science-platform“app of apps” andrepertoirebefore you sync any other services.
Additionally, you will find other features related to this capability, such as mobu now having the ability to only run notebooks that use applications that Repertoire indicates are available.
To be clear, Repertoire is a Phalanx cluster infrastructure service. Its purpose is to support other Phalanx services. It is not an external capability discovery service (such as a VO registry). A Phalanx VO Registry service is still on our roadmap.
As always, feel free to ask questions in the comments below.