Here are some frequently asked questions about SLATE. If you don’t find your questions answered here, be sure to check Stack Overflow for more Q&A.
When fully developed, SLATE will simplify the deployment and operation of services necessary for your research community. For example, if you have research groups on campus requiring a domain specific task scheduler or science gateway, SLATE will provide the framework to pull containerized service images from trusted repositories and operate them with minimal effort or specific expertise.
SLATE will provide the a “substrate” to host your backend services connecting web portal frameworks to HPC and storage resources. For example, if your gateway requires a Globus endpoint or Open Science Grid “compute element” where there is none, SLATE can be use to quickly deploy the needed service. The benefits of SLATE for developers of distributed systems have more tools available to practice a DevOps programming model over wide area resources.
The SLATE team is actively working with the cybersecurity officers of our participating institutions to ensure best practices in systems management. We are will also be working with the Center for Trustworthy Scientific Cyberinfrastructure to periodically assess and review the trust model and underlying assumptions on balancing risk and science benefit.