USER INTERFACES¶
Jetstream2 (JS2) supports a number of different interfaces for creating, deploying, and managing Virtual Machines instances (VMs) and Storage.
-
JS2 has 3 web-based Graphical User Interfaces as well as an OpenStack Command Line Interface (CLI).
When to Use Exosphere¶
If you are new to Jetstream2 and unsure which interface to use, Exosphere is a great place to start. Whether you are exploring new software tools, running compute-intensive jobs, teaching a course/workshop, or building a science gateway, Exosphere can likely help you reach your goals.
- New to cloud computing: The graphical interface reduces the learning curve for launching your first instances by providing a familiar user experience.
- General use: Perfect for a wide variety of use cases.
- Science Gateways: Easily set up your website, app, or portal for your user base.
- Workshops: Allow users to set up their own instances or copy configurations from an existing instance.
Pros:
- User-friendly design: Intuitive interface tailored for researchers.
- Simple actions: Common tasks are streamlined into a few clicks.
- Graphical desktops: Built-in support for web-based remote desktops.
- Usage metrics: Real-time visibility of performance.
- Automated setup: Handles SSH keys, networking, and security groups automatically.
Cons:
- Feature subset: Not all OpenStack actions can be accomplished via Exosphere.
- Limited customization: Less control over low-level infrastructure configurations compared to Horizon or the CLI.
When to Use Horizon¶
Horizon is a web-based GUI for interacting with the OpenStack API. Almost all functionality available from the CLI is available in Horizon. Exosphere and Cacao both provide subsets of Horizon functionality with more focus on ease of use.
- Low-level configuration: Use this when you need to take an action not available through Exosphere’s simplified UI.
- Access Management: The only UI from which users can generate application credentials for certain CLI-based use cases such as Magnum or Barbican workflows.
- Project Oversight: Provides detailed technical information about project settings and specific instance parameters.
Pros:
- Robust suite: Includes advanced actions and official OpenStack management tools.
- Detailed information: High visibility into the specific settings of every resource.
- Official UI: The standard dashboard for all OpenStack-based clouds.
Cons:
- Learning curve: Not as intuitive or informative for beginners as Exosphere.
- Opaque terminology: Some actions use technical jargon that can be confusing.
- Performance: Can suffer from speed issues during high load or complex queries.
When to Use CACAO¶
CACAO is an orchestration service for your ACCESS Jetstream2 allocation. You can organize your Openstack resources—servers, volumes, containers, and more—by project. You can also use CACAO to create other more complex deployments that require the orchestration of multiple servers and storage, such as a JupyterHub for a workshop or a Kubernetes cluster. CACAO already has some templates that are curated by CyVerse, or you can create your own templates.
- Scaling workloads: Ideal for spinning up clusters or more than 25 instances at once.
- Standardized environments: Use curated templates for JupyterHubs, Kubernetes, or custom workshops.
Pros:
- Automation: Built-in orchestration for scaling large environments.
- Unique features: For example, automated shutdown of instances upon completion of work.
- Template-driven: Choose from CyVerse curated templates or create your own.
Cons:
- Template overhead: Requires understanding or creating templates for custom deployments.
When to Use the CLI¶
There are many options and tools for using the OpenStack API from the command line. This provides the most direct and powerful way to manage your infrastructure.
- Programmatic workflows: Best for scripting repetitive tasks or integrating with CI/CD pipelines.
- Unique requirements: Use this for highly specific workflows requiring a high degree of customizability.
- Control: Managing resources at the lowest possible level.
Pros:
- Full access: Provides 100% coverage of all OpenStack API actions.
- Scriptable: Perfect for automation and reproducibility.
- Speed: Faster for experienced users to execute commands across multiple projects.
Cons:
- Complexity: Requires knowledge of terminal commands and the OpenStack API.
- Manual setup: Requires obtaining and managing app credentials from Horizon first, as well as manually setting up features like a network and security policies.