Skip to content
Snippets Groups Projects
Verified Commit 17d34aa3 authored by Jan Kryštof's avatar Jan Kryštof
Browse files

Merge branch 'master' into 1294-task-revize-hlavne-g2-dokumentace__priklady_pouziti

parents 4e194775 04781fef
Branches
No related tags found
No related merge requests found
topics/compute/sensitive/docs @CESNET/sensitivecloud
topics/compute/openstack/docs @CESNET/cloud
\ No newline at end of file
......@@ -16,20 +16,20 @@ The following guide will take you through the steps necessary to start your firs
Prerequisites:
* Up-to-date web browser
* Active account in [MetaCentrum](https://metavo.metacentrum.cz/en/application/index.html)
* Active account, see [Accessing Brno site](../technical-reference/brno-site/get-access.md) and [Accessing Ostrava site](../technical-reference/ostrava-site/get-access.md)
* Basic knowledge of SSH (for remote connections)
* [API key and CLI client](../how-to-guides/obtaining-api-key.md) (needed only if You want to use CLI)
## Sign In
The dashboard is available at [https://dashboard.cloud.muni.cz](https://dashboard.cloud.muni.cz).
The dashboard is available at [https://dashboard.cloud.muni.cz](https://dashboard.cloud.muni.cz) or [https://horizon.ostrava.openstack.cloud.e-infra.cz](https://horizon.ostrava.openstack.cloud.e-infra.cz).
!!! note
International users may choose <strong>EGI Check-in</strong>, <strong>DEEP AAI</strong> or <strong>LIFESCIENCE AAI</strong>, depending on their membership in these projects.
__1.__ Select `EINFRA CESNET`.
__1.__ Select `EINFRA CESNET` in Brno or `e-INFRA CZ federation` in Ostrava site.
__2.__ Click on **Sign In**.
......
---
title: Managing Network Interface
search:
exclude: false
---
# Managing Network Interface
In OpenStack, you can attach a network interface to an instance to provide additional network connectivity. This allows the instance to communicate with other resources on the network, including other instances, services, and external networks. In this how-to guide, we will walk you through the process of attaching and detaching a network interface using the OpenStack command-line interface (CLI).
## Prerequisites
Before you begin, you should have the following:
- An [instance](../getting-started/creating-first-infrastructure.md) that you want to attach a network interface to
- A pre-existing OpenStack [network](../how-to-guides/create-networking.md) that you want to attach to the instance
## Attaching Interface
!!! info
If you approach a problem with your IPv6 deployment, please refer to [IPv6 troubleshooting](../additional-information/ipv6-troubleshooting.md).
=== "Horizon"
Go to **Project &gt; Compute &gt; Instances**. Click on the menu **Actions** on the instance you wish to change and click on **Attach interface**.
!!! example
![](/compute/openstack/images/networks/attach_interface.png)
In the **Network** dropdown menu select available network.
!!! example
![](/compute/openstack/images/networks/ipv6_attach.png)
=== "Command Line"
To attach a network interface to an OpenStack instance, you will need to create a port that is attached to the desired network and host. You can create a new port using the following:
!!! example
```
openstack port create --network <network_id> --security-group <security_group_name_or_id> --host <virtual_machine_name_or_id> <port_name>
```
!!! info
The `<network_name_or_id>` represents the network you wish to attach the new interface to. By specifying `--security-group` you can select specific security group for the port and by specifying `--host` you can directly attach the interface to the host upon creation.
Additional port configuration is available in [official CLI documentation](https://docs.openstack.org/python-openstackclient/train/cli/command-objects/port.html).
## Detaching Interface
=== "Horizon"
TODO
=== "Command Line"
To detach a network interface from an OpenStack instance, you can use the following command:
!!! example
```
$ openstack server remove port <server_id> <port_id>
```
!!! info
This will detach the OpenStack port specified by `<port_id>` from the instance specified by `<server_id>`.
To delete the port after it has been detached from the instance, use the following command:
!!! example
```
$ openstack port delete <port_id>
```
!!! info
This will delete the specified port `<port_id>` from your OpenStack environment.
## Troubleshooting
If you encounter any issues while attaching or detaching a network interface, you can use the following commands to troubleshoot:
- **Check the status of an OpenStack port**: Make sure that the status is "ACTIVE" and that the port is attached to the correct network. Use the following command:
```
openstack port show <port_id>
```
- **Check the instance and its associated network interfaces**: Make sure that the instance is running and has the appropriate network interfaces attached. Use the following command:
```
$ openstack server show <server_id>
```
- **Check FAQ**: If you approach an issue, make sure to first check FAQ before contacting support.
- **Contact support**: If you're unable to resolve the issue on your own, contact your OpenStack support team for further assistance. Be sure to provide as much information as possible, including error messages and steps you've already taken to troubleshoot the issue.
## Security Considerations
- **Limit the use of network interfaces**: Only attach network interfaces to instances that require them. Avoid attaching network interfaces to instances that do not require them to minimize the attack surface.
- **Review firewall rules**: Review and update firewall rules to ensure that only necessary ports and services are accessible from the network interface.
- **Use security groups**: Use security groups to define the network traffic that is allowed to or from the instance.
......@@ -28,7 +28,6 @@ search:
| hpc.16core-32ram | 16 | 32 | Yes | No | 524.288 | 2000 | 2000.0 | No |
| hpc.16core-64ram-ssd-ephem | 16 | 64 | Yes | Yes | Unlimited | Unlimited | 1250.0 | No |
| hpc.18core-48ram | 18 | 48 | Yes | No | 524.288 | 2000 | 2000.0 | No |
| hpc.19core-176ram-nvidia-1080-glados | 19 | 176 | Yes | Yes | Unlimited | Unlimited | Unlimited | Yes |
| hpc.19core-176ram-nvidia-2080-glados | 19 | 176 | Yes | Yes | Unlimited | Unlimited | Unlimited | Yes |
| hpc.24core-256ram-ssd-ephem | 24 | 256 | Yes | Yes | Unlimited | Unlimited | 1250.0 | No |
| hpc.24core-96ram-ssd-ephem | 24 | 96 | Yes | Yes | Unlimited | Unlimited | 1250.0 | No |
......@@ -36,12 +35,9 @@ search:
| hpc.30core-256ram | 30 | 256 | Yes | No | Unlimited | Unlimited | Unlimited | No |
| hpc.30core-64ram | 30 | 64 | Yes | No | Unlimited | Unlimited | Unlimited | No |
| hpc.32core-256ram-nvidia-t4-single-gpu | 32 | 240 | Yes | No | Unlimited | Unlimited | Unlimited | Yes |
| hpc.38core-372ram-nvidia-1080-glados | 38 | 352 | Yes | Yes | Unlimited | Unlimited | Unlimited | Yes |
| hpc.38core-372ram-nvidia-2080-glados | 38 | 352 | Yes | Yes | Unlimited | Unlimited | Unlimited | Yes |
| hpc.38core-372ram-ssd-ephem | 38 | 372 | Yes | Yes | Unlimited | Unlimited | 1250.0 | No |
| hpc.40core-372ram-nvidia-1080-glados | 40 | 352 | Yes | Yes | Unlimited | Unlimited | Unlimited | Yes |
| hpc.40core-372ram-nvidia-2080-glados | 40 | 352 | Yes | Yes | Unlimited | Unlimited | Unlimited | Yes |
| hpc.40core-372ram-nvidia-titan-glados | 40 | 352 | Yes | Yes | Unlimited | Unlimited | Unlimited | Yes |
| hpc.4core-16ram-ssd-ephem | 4 | 16 | Yes | Yes | Unlimited | Unlimited | 1250.0 | No |
| hpc.4core-16ram-ssd-ephem-500 | 4 | 16 | Yes | Yes | Unlimited | Unlimited | 1250.0 | No |
| hpc.64core-512ram-nvidia-t4 | 64 | 480 | Yes | No | Unlimited | Unlimited | Unlimited | Yes |
......@@ -49,7 +45,6 @@ search:
| hpc.8core-32ram-ssd-ephem | 8 | 32 | Yes | Yes | Unlimited | Unlimited | 1250.0 | No |
| hpc.8core-32ram-ssd-rcx-ephem | 8 | 32 | Yes | Yes | Unlimited | Unlimited | Unlimited | No |
| hpc.8core-64ram | 8 | 64 | Yes | No | 524.288 | 2000 | 2000.0 | No |
| hpc.8core-64ram-nvidia-1080-glados | 8 | 64 | Yes | Yes | Unlimited | Unlimited | Unlimited | Yes |
| hpc.hdh | 32 | 480 | Yes | No | Unlimited | Unlimited | Unlimited | No |
| hpc.hdh-8cpu-120ram | 8 | 120 | Yes | No | Unlimited | Unlimited | Unlimited | No |
| hpc.hdh-ephem | 32 | 480 | Yes | No | Unlimited | Unlimited | Unlimited | No |
......@@ -78,3 +73,11 @@ search:
| standard.xlarge-cpu | 8 | 16 | No | No | 262.144 | 2000 | 250.0 | No |
| standard.xxlarge | 8 | 32 | No | No | 262.144 | 2000 | 250.0 | No |
| standard.xxxlarge | 8 | 64 | No | No | 262.144 | 2000 | 250.0 | No |
| hpc.8core-8ram | 8 | 8 | Yes | No | 524.288 | 2000 | 2000.0 | No |
| hpc.16core-32ram-100disk | 16 | 32 | Yes | No | 524.288 | 2000 | 2000.0 | No |
| meta-hdm.38core-300ram-nvidia-a40-quad | 38 | 300 | Yes | Yes | Unlimited | Unlimited | Unlimited | Yes |
| hpc.4core-4ram | 4 | 4 | Yes | No | 524.288 | 2000 | 2000.0 | No |
| a3.32core-120ram-1t4 | 32 | 120 | Yes | Yes | Unlimited | Unlimited | Unlimited | Yes |
| a3.32core-240ram-1t4 | 32 | 240 | Yes | Yes | Unlimited | Unlimited | Unlimited | Yes |
| a3.64core-240ram-2t4 | 64 | 240 | Yes | Yes | Unlimited | Unlimited | Unlimited | Yes |
| a3.64core-480ram-2t4 | 64 | 480 | Yes | Yes | Unlimited | Unlimited | Unlimited | Yes |
......@@ -13,8 +13,6 @@ On this page, you can find a static list of GPUs offered in Metacentrum Cloud.
|-----------------------------------|---------------|---------------|
| NVIDIA Tesla T4 | 16 | 2 |
| NVIDIA A40 (**) | 2 | 4 |
| NVIDIA TITAN V | 1 | 1 |
| NVIDIA GeForce GTX 1080 Ti (*) | 8 | 2 |
| NVIDIA GeForce GTX 2080 (*) | 9 | 2 |
| NVIDIA GeForce GTX 2080 Ti (*) | 14 | 2 |
......
......@@ -10,3 +10,5 @@ search:
Valid e-INFRA CZ indentity is necessary to log in to Ostrava openstack site.
See [e-INFRA CZ](https://docs.e-infra.cz/account/access/) documentation on access.
Visit [Ostrava site](https://ostrava.openstack.cloud.e-infra.cz/).
......@@ -9,7 +9,7 @@ nav:
- How-to guides:
- how-to-guides/accessing-instances.md
- how-to-guides/managing-floating-ips.md
- how-to-guides/attaching-interface.md
- how-to-guides/managing-interface.md
# - how-to-guides/attaching-remote-storage.md
- how-to-guides/changing-vm-resources.md
- how-to-guides/create-networking.md
......
......@@ -7,11 +7,9 @@ authors:
- matejantol
---
!!! warning "Planned changes to the SensitiveCloud service"
!!! warning "The log-in method to the SensitiveCloud service has been changed"
We would like to inform you that on February 26th, 2023 at 5 p.m. (UTC+1), SensitiveCloud service will be undergoing scheduled maintenance to change the login method from MUNI IDP to e-INFRA CZ IDP.
The expected downtime should not exceed one hour, during which the Rancher portal login will be temporarily unavailable. We apologize for any inconvenience this may cause and assure you that we will work diligently to ensure a swift and seamless transition.
On February 26th, 2023, the SensitiveCloud's login method has been changed from the MUNI Login to e-INFRA CZ Login.
[Read more how it affects users and security][migration]
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment