Skip to content

Commit

Permalink
remove references to VMOps Dashboard
Browse files Browse the repository at this point in the history
  • Loading branch information
@sebastian-luna-valero
sebastian-luna-valero committed Mar 18, 2024
1 parent 37fcf71 commit 896d32f
Show file tree
Hide file tree
Showing 4 changed files with 10 additions and 21 deletions.
2 changes: 1 addition & 1 deletion content/en/users/compute/cloud-compute/gpgpu/_index.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ with your Check-In account. More information is available in the

GPUs sites can be accessed in different ways: via site-specific dashboards and
endpoints or via common federated-cloud services like the OpenStack Horizon
dashboards, [VMOps Dashboard](../monitor), or a [cloud orchestrator](../automate).
dashboards or a [cloud orchestrator](../automate).

It is also possible to use the
[FedCloud Client](../../../getting-started/cli) for command-line access. Below is
Expand Down
11 changes: 3 additions & 8 deletions content/en/users/getting-started/_index.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -172,14 +172,9 @@ For pre-configured services (e.g.: [EGI Notebooks](../dev-env/notebooks/)),
the capacity allocated includes up to **4 vCPU cores, 8 GB of RAM and
10 GB of block storage**.

You can manage those resources via [command-line](cli) or any of the dashboards
of the EGI Cloud: the [VMOps dashboard](../compute/cloud-compute/monitor/) and
the [IM dashboard](../compute/orchestration/im/dashboard/).

You can also easily access scientific applications,
[EC3](../compute/orchestration/ec3) has a list of
[applications](../compute/orchestration/ec3/apps/) that you can easily start
from the [EC3 portal](https://servproject.i3m.upv.es/ec3-ltos/index.php).
You can manage those resources via [command-line](cli) or web interface
like the
[Infrastructure Manager dashboard](../compute/orchestration/im/dashboard/).

## Unused resources

Expand Down
16 changes: 5 additions & 11 deletions content/en/users/getting-started/architecture/_index.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -68,17 +68,11 @@ cloud providers at three different layers:
- Directly using the IaaS APIs or [CLIs](../cli) to manage individual resources.
This option is recommended for preexisting use cases with requirements on
specific APIs.
- Using federated access tools that allow managing the complexity of dealing
with different providers in a uniform way. These tools include:
- **Provisioning systems** allow users to define infrastructure as code, then
manage and combine resources from different providers, thus enabling the
portability of application deployments between them (e.g.
[Infrastructure Manager](../../compute/orchestration/im) or
[Terraform](https://www.terraform.io/)), and
- **Cloud brokers** provide matchmaking for workloads to available providers
(e.g. the
[INDIGO-DataCloud Orchestrator](https://indigo-dc.gitbook.io/indigo-paas-orchestrator/)).
- Using the [VMOps dashboard](../../compute/cloud-compute/monitor).
- Using **Provisioning systems** allow users to define infrastructure as code,
then manage and combine resources from different providers, thus enabling
the portability of application deployments between them (e.g.
[Infrastructure Manager](../../compute/orchestration/im) or
[Terraform](https://www.terraform.io/)).

EGI provides ready-to-use software components to enable the federation for
OpenStack. These components rely on public APIs of the IaaS system and use
Expand Down
2 changes: 1 addition & 1 deletion content/en/users/tutorials/adhoc/create-your-first-virtual-machine/_index.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ AppDB is one of the service in the

Once your membership to a VO has been approved you are ready to create your first
Virtual Machine. There are several ways to achieve this. The simplest way is to
use a web dashboard like [VMOps Dashboard](../../../compute/cloud-compute/monitor) or
use the
[Infrastructure Manager Dashboard](../../../compute/orchestration/im/dashboard).
On the other hand, advanced users
may prefer to use the [command-line interface](../../../getting-started/cli).
Expand Down

1 comment on commit 896d32f

@github-actions
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@check-spelling-bot Report

🔴 Please review

See the 📜action log or 📝 job summary for details.

Unrecognized words (7)

datetime
FPGA
GPUs
LCG
OGC
Paa
varchar

To accept these unrecognized words as correct, you could run the following commands

... in a clone of the [email protected]:EGI-Federation/documentation.git repository
on the deprecation branch (ℹ️ how do I use this?):

curl -s -S -L 'https://raw.githubusercontent.com/check-spelling/check-spelling/main/apply.pl' |
perl - 'https://github.com/EGI-Federation/documentation/actions/runs/8324147144/attempts/1'
Available 📚 dictionaries could cover words (expected and unrecognized) not in the 📘 dictionary

This includes both expected items (11) from .github/actions/spelling/expect.txt and unrecognized words (7)

Dictionary Entries Covers Uniquely
cspell:sql/src/tsql.txt 112 2
cspell:java/src/java-terms.txt 920 2
cspell:elixir/dict/elixir.txt 95 1
cspell:python/src/python/python.txt 392 1
cspell:django/dict/django.txt 393 1

Consider adding them (in .github/workflows/spelling.yml) for uses: check-spelling/check-spelling@main in its with:

      with:
        extra_dictionaries:
          cspell:sql/src/tsql.txt
          cspell:java/src/java-terms.txt
          cspell:elixir/dict/elixir.txt
          cspell:python/src/python/python.txt
          cspell:django/dict/django.txt

To stop checking additional dictionaries, add (in .github/workflows/spelling.yml) for uses: check-spelling/check-spelling@main in its with:

check_extra_dictionaries: ''

Please sign in to comment.