- What We Offer
- Your Processing Environment
- Example of tool usage
- Processing EO Data and Serving www services
- Processing and Storing EO
- Embedding OGC WMS Services into Your website
- GPU Use Case
- Using the EO Browser
- EO Data Finder API Manual
- Use of SNAP and QGIS on a CREODIAS Virtual Machine
- Use of WMS Configurator
- DNS as a Service - user documentation
- Use of Sinergise Sentinel Hub on the CREODIAS EO Data Hub
- Load Balancer as a Service
- Jupyter Hub
- Use of CREODIAS Finder for ordering data
- ESRI ArcGIS on CREODIAS
- se of SNAP and QGIS on a CREODIAS Virtual Machine
- Use of CEMS data through CREODIAS
- Legal Matters
- Pricing Plans
- Public Reporting Dashboards
- Sentinel Hub Documentation
- Integration Guides
- OGC API
- Custom Processing Scripts
What is an OpenStack project?
A project is a isolated group of zero or more users who share common access with specific privileges to the software instance in OpenStack. A project is created for each set of instances and networks that are configured as a discrete entity for the project. In Compute, a project owns virtual machines (in Compute) or containers (in Object Storage).
You can imagine that the whole OpenStack cloud is a big cake of resources (vCPU, disks, instances, etc…) and projects are the pieces of this cake served to the customers.
Current project name is visible beside the domain in the Horizon panel.
By default, each domain has two projects:
Projects are created, managed, and edited at the OpenStack Projects screen.
Users can be associated with more than one project, but once signed, they can only see and access the resources available in that project.
Each project and user pairing can have a role associated with it.
Users can create private networks for connectivity within projects. By default, they are fully isolated and are not shared with other projects.