![]() Experiment Precis provides automatic environment capture for documentation and reproducibility.Integration with the Chameleon shared Jupyter environment, to allow orchestrating experiments via Jupyter notebooks.Python-CHI: User-Friendly Python client library with Jupyter IntegrationĬhameleon additionally provides a few useful extra pieces for all users of CHI-in-a-Box associate sites:.Keystone (authentication and authorization).Including custom vendordata service for automatic experiment metrics collection.Nova (instance deployment in conjunction w/ Ironic).Blazar (advanced reservation for resources such as bare metal nodes and public IP addresses or layer-2 circuits).Including support for bare metal snapshots (not yet an OpenStack-provided capability).Currently included with CHI-in-a-Box:įor users: A full-featured cloud deployment optimized for bare metal reservations and provisioning, including the following OpenStack services by default: This scenario will be supported on a best effort basis only. This type of provider will use CHI for the core testbed services only and operate their user services (i.e., manage their own user accounts and/or projects, help desk, mailing lists and other communication channels, etc.), user portal, resource discovery, and appliance catalog (some of those services can in principle be left out at the cost of providing a less friendly interface to users). In this scenario a provider wants to create a testbed that is in every way separate from Chameleon. In this scenario Chameleon support extends only to the time resources are available to the testbed. ![]() This scenario is similar to the Chameleon Associate but while the resources are available to the testbed users most of the time, the provider anticipates that they may want to take them offline for extended periods of time for other uses. All user support will be provided by the Chameleon team. This type of provider will provide system administration of their resources (hardware configuration and operation as well as CHI administration with the support of the Chameleon team) and use the Chameleon user services (user/project management, etc.), user portal, resource discovery, and appliance catalog. In this scenario a provider wants to add resources to the Chameleon testbed such that they are discoverable and available to all Chameleon users while retaining their own project identity (via branding, usage reports, some of the policies, etc.). ![]() We have identified demand for three types of scenarios in which users would like to use a packaging of Chameleon infrastructure: Chameleon Associate
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |