MediaWiki - User contributions [en]

Kopia restore process

2026-06-04T09:43:05Z

Sst-ska:

= Overview =
This page describes the process of restoring instance data from a Kopia backup.
= Connecting a backup repository =
Before data can be restored from a backup, the appropriate Kopia repository needs to be connected to.

The repository connection details are stored locally on the server that is being backed up.
Each server contains the credentials and configuration required to access its own Kopia repository.

First connect to the server:
<syntaxhighlight lang="bash">
# For example: ssh sst-int-001
ssh
</syntaxhighlight>

Then set the path leading to the access information as a variable:
<syntaxhighlight lang="bash">
# For example: file=/home/sst-all/access.yaml
file=
</syntaxhighlight>

Set the required access parameters as variables:
<syntaxhighlight lang="bash">
endpoint=$(awk -F': ' '/^[[:space:]]*endpoint:/ {gsub(/"/,"",$2); print $2}' "$file")
bucket=$(awk -F': ' '/^[[:space:]]*bucket:/ {gsub(/"/,"",$2); print $2}' "$file")
prefix=$(awk -F': ' '/^[[:space:]]*prefix:/ {gsub(/"/,"",$2); print $2}' "$file")
access_key=$(awk -F': ' '/^[[:space:]]*access_key:/ {gsub(/"/,"",$2); print $2}' "$file")
secret_access_key=$(awk -F': ' '/^[[:space:]]*secret_access_key:/ {gsub(/"/,"",$2); print $2}' "$file")
password=$(awk -F': ' '/^[[:space:]]*password:/ {gsub(/"/,"",$2); print $2}' "$file")
</syntaxhighlight>

Check the created variables like so:
<syntaxhighlight lang="bash">
cat <<EOF
S3_ENDPOINT="$endpoint"
S3_BUCKET="$bucket"
S3_PREFIX="$prefix"
S3_ACCESS_KEY="$access_key"
S3_SECRET_ACCESS_KEY="$secret_access_key"
KOPIA_PASSWORD="$password"
EOF
</syntaxhighlight>

If everything looks fine connect to the repository:
<syntaxhighlight lang="bash">
kopia repo connect s3 \
--readonly \
--endpoint="$endpoint" \
--bucket="$bucket" \
--prefix="$prefix" \
--access-key="$access_key" \
--secret-access-key="$secret_access_key" \
--password="$password"
</syntaxhighlight>

{{Note|collapsed=true|title=Output:|content=
<syntaxhighlight lang='text'>
Connected to repository.

NOTICE: Kopia will check for updates on GitHub every 7 days, starting 24 hours after first use.
To disable this behavior, set environment variable KOPIA_CHECK_FOR_UPDATES=false
Alternatively you can remove the file "/root/.config/kopia/repository.config.update-info.json".
</syntaxhighlight>
}}

= Inspecting data =
After connecting to the repository snapshots can be listed like so:
<syntaxhighlight lang="bash">
kopia snapshot list --all --show-identical
</syntaxhighlight>

Usually each mountpoint has it's own snapshots:
{{Note|collapsed=true|title=Output:|content=
<syntaxhighlight lang='text', highlight=1,13,25,37,49 >
root@sst-int-001:/etc
2026-05-26 03:04:27 CEST k2d1601c231eed28510d797778b27091c 27.1 MB drwxr-xr-x files:1430 dirs:444 (daily-10)
2026-05-27 03:04:21 CEST kd8f190358cfdf77b226c69b34b19246c 27.1 MB drwxr-xr-x files:1430 dirs:444 (daily-9)
2026-05-28 03:04:33 CEST ke0aee9e74790d6b1e79d4b2816f05254 27.1 MB drwxr-xr-x files:1430 dirs:444 (daily-8)
2026-05-29 03:04:25 CEST ka20e158f4e52335ae06379a65f14fc9b 27.1 MB drwxr-xr-x files:1430 dirs:444 (daily-7)
2026-05-30 03:04:27 CEST k41338685d0d45becad4bebf977a1b2b0 27.1 MB drwxr-xr-x files:1430 dirs:444 (daily-6)
2026-05-31 03:04:20 CEST k4581635f5244edc6d30640277ff40de1 27.1 MB drwxr-xr-x files:1430 dirs:444 (daily-5)
2026-06-01 03:04:48 CEST k8f65195a4d1cababcfb265f0c190077d 27.1 MB drwxr-xr-x files:1430 dirs:444 (daily-4)
2026-06-02 03:04:21 CEST k73777c3e3acd749f829ab8c43f3e60ac 27.1 MB drwxr-xr-x files:1430 dirs:444 (latest-3,daily-3)
2026-06-03 03:04:29 CEST k8c532d7558940d3dd32cc85c57dd0af5 27.1 MB drwxr-xr-x files:1430 dirs:444 (latest-2,daily-2)
2026-06-04 03:04:25 CEST k60796ced54c59316191b355f58d91d98 27.1 MB drwxr-xr-x files:1430 dirs:444 (latest-1,daily-1)

root@sst-int-001:/home
2026-05-26 03:04:35 CEST k85a74d754790d64a0fa17017d23d3649 1.9 MB drwxr-xr-x files:257 dirs:68 (daily-10)
2026-05-27 03:04:29 CEST kbc9814f2c1a8fb94eef77161da59e748 1.9 MB drwxr-xr-x files:257 dirs:68 (daily-9)
2026-05-28 03:04:41 CEST kbc9814f2c1a8fb94eef77161da59e748 1.9 MB drwxr-xr-x files:257 dirs:68 (daily-8)
2026-05-29 03:04:33 CEST kbc9814f2c1a8fb94eef77161da59e748 1.9 MB drwxr-xr-x files:257 dirs:68 (daily-7)
2026-05-30 03:04:35 CEST kbc9814f2c1a8fb94eef77161da59e748 1.9 MB drwxr-xr-x files:257 dirs:68 (daily-6)
2026-05-31 03:04:27 CEST kbc9814f2c1a8fb94eef77161da59e748 1.9 MB drwxr-xr-x files:257 dirs:68 (daily-5)
2026-06-01 03:05:05 CEST kbc9814f2c1a8fb94eef77161da59e748 1.9 MB drwxr-xr-x files:257 dirs:68 (daily-4)
2026-06-02 03:04:29 CEST kbc9814f2c1a8fb94eef77161da59e748 1.9 MB drwxr-xr-x files:257 dirs:68 (latest-3,daily-3)
2026-06-03 03:04:37 CEST kbc9814f2c1a8fb94eef77161da59e748 1.9 MB drwxr-xr-x files:257 dirs:68 (latest-2,daily-2)
2026-06-04 03:04:34 CEST ke55e94ac077bd393838a2b229551c8a9 1.9 MB drwxr-xr-x files:258 dirs:69 (latest-1,daily-1)

root@sst-int-001:/usr/local
2026-05-26 03:04:36 CEST k75894f3af04c9479f86f6ea31808b302 22 KB drwxr-xr-x files:8 dirs:36 (daily-10)
2026-05-27 03:04:30 CEST k75894f3af04c9479f86f6ea31808b302 22 KB drwxr-xr-x files:8 dirs:36 (daily-9)
2026-05-28 03:04:42 CEST k75894f3af04c9479f86f6ea31808b302 22 KB drwxr-xr-x files:8 dirs:36 (daily-8)
2026-05-29 03:04:35 CEST k75894f3af04c9479f86f6ea31808b302 22 KB drwxr-xr-x files:8 dirs:36 (daily-7)
2026-05-30 03:04:36 CEST k75894f3af04c9479f86f6ea31808b302 22 KB drwxr-xr-x files:8 dirs:36 (daily-6)
2026-05-31 03:04:28 CEST k75894f3af04c9479f86f6ea31808b302 22 KB drwxr-xr-x files:8 dirs:36 (daily-5)
2026-06-01 03:05:06 CEST k75894f3af04c9479f86f6ea31808b302 22 KB drwxr-xr-x files:8 dirs:36 (daily-4)
2026-06-02 03:04:30 CEST k75894f3af04c9479f86f6ea31808b302 22 KB drwxr-xr-x files:8 dirs:36 (latest-3,daily-3)
2026-06-03 03:04:38 CEST k75894f3af04c9479f86f6ea31808b302 22 KB drwxr-xr-x files:8 dirs:36 (latest-2,daily-2)
2026-06-04 03:04:35 CEST k75894f3af04c9479f86f6ea31808b302 22 KB drwxr-xr-x files:8 dirs:36 (latest-1,daily-1)

root@sst-int-001:/var/backup
2026-05-26 03:04:38 CEST k737253d9ce3c4889faba67709bd54c30 3.2 GB drwxr-xr-x files:138 dirs:6 (daily-10)
2026-05-27 03:04:32 CEST k1df55cad1be2d85dd3c8b1086161a321 3.5 GB drwxr-xr-x files:139 dirs:6 (daily-9)
2026-05-28 03:04:43 CEST keb7f9d4a5c1908539d2f818c2863f6e5 3.2 GB drwxr-xr-x files:138 dirs:6 (daily-8)
2026-05-29 03:04:37 CEST k76863a5b41c3d70701a43f3a7f56b7b7 3.2 GB drwxr-xr-x files:138 dirs:6 (daily-7)
2026-05-30 03:04:38 CEST k0f6b31464daafe6e6d98ec4933148723 3.2 GB drwxr-xr-x files:138 dirs:6 (daily-6)
2026-05-31 03:04:30 CEST k9128bd6dae323cb7f82534e96ffe312d 3.5 GB drwxr-xr-x files:139 dirs:6 (daily-5)
2026-06-01 03:05:08 CEST k0789f3fe1645403d65daf45d2dca8b95 3.5 GB drwxr-xr-x files:139 dirs:6 (daily-4)
2026-06-02 03:04:31 CEST k906b99f37cadf4c9d645ec0e3a027805 3.2 GB drwxr-xr-x files:138 dirs:6 (latest-3,daily-3)
2026-06-03 03:04:39 CEST ke6ed15e1dd24e8d4f7c3af45cebb2b35 3.2 GB drwxr-xr-x files:138 dirs:6 (latest-2,daily-2)
2026-06-04 03:04:36 CEST k19beeb2a7ee4d720fcebd7865ec63600 3.2 GB drwxr-xr-x files:138 dirs:6 (latest-1,daily-1)

root@sst-int-001:/var/db
2026-05-26 03:04:26 CEST k8532c690ec118016f2daaf1f072f7b72 0 B drwxr-xr-x files:0 dirs:3 (daily-10)
2026-05-27 03:04:20 CEST k8532c690ec118016f2daaf1f072f7b72 0 B drwxr-xr-x files:0 dirs:3 (daily-9)
2026-05-28 03:04:31 CEST k8532c690ec118016f2daaf1f072f7b72 0 B drwxr-xr-x files:0 dirs:3 (daily-8)
2026-05-29 03:04:23 CEST k8532c690ec118016f2daaf1f072f7b72 0 B drwxr-xr-x files:0 dirs:3 (daily-7)
2026-05-30 03:04:26 CEST k8532c690ec118016f2daaf1f072f7b72 0 B drwxr-xr-x files:0 dirs:3 (daily-6)
2026-05-31 03:04:19 CEST k8532c690ec118016f2daaf1f072f7b72 0 B drwxr-xr-x files:0 dirs:3 (daily-5)
2026-06-01 03:04:47 CEST k8532c690ec118016f2daaf1f072f7b72 0 B drwxr-xr-x files:0 dirs:3 (daily-4)
2026-06-02 03:04:20 CEST k8532c690ec118016f2daaf1f072f7b72 0 B drwxr-xr-x files:0 dirs:3 (latest-3,daily-3)
2026-06-03 03:04:27 CEST k8532c690ec118016f2daaf1f072f7b72 0 B drwxr-xr-x files:0 dirs:3 (latest-2,daily-2)
2026-06-04 03:04:24 CEST k8532c690ec118016f2daaf1f072f7b72 0 B drwxr-xr-x files:0 dirs:3 (latest-1,daily-1)
</syntaxhighlight>
}}

To inspect or restore a snapshot set it's ID as a variable:
<syntaxhighlight lang="bash">
# For example: snapshot='k85a74d754790d64a0fa17017d23d3649'
snapshot=''
</syntaxhighlight>

Taking a look at the snapshot's contents:
<syntaxhighlight lang="bash">
kopia ls ${snapshot}
</syntaxhighlight>

{{Note|collapsed=true|title=Output:|content=
<syntaxhighlight lang='text'>
almalinux
sst-yyy
sst-xxx
certbot
</syntaxhighlight>
}}

We can look into the folders, like so:

<syntaxhighlight lang="bash">
kopia ls ${snapshot}/sst-xxx
</syntaxhighlight>

= Restoring data =

To restore a single file:
<syntaxhighlight lang="bash">
# Restore a file inside a snapshot to a destination
kopia restore ${snapshot}/home/sst-xxx/example.txt /var/tmp/example.txt
</syntaxhighlight>

{{Note|collapsed=true|title=Output:|content=
<syntaxhighlight lang="bash">
Restoring to local filesystem (/var/tmp/example.txt) with parallelism=8...
Processed 1 (2.2 MB) of 0 (0 B).
Restored 1 files, 0 directories and 0 symbolic links (2.2 MB).
</syntaxhighlight>
}}

To restore the entire snapshot:
<syntaxhighlight lang="bash">
# Create a destination directory or use an existing one
mkdir /var/tmp/restore

# Restore the snapshot to the destination
kopia restore ${snapshot} /var/tmp/restore/
</syntaxhighlight>

{{Note|collapsed=true|title=Output:|content=
<syntaxhighlight lang="bash">
Restoring to local filesystem (/var/tmp/restore) with parallelism=8...
Processed 3297 (3 GB) of 3296 (3 GB) 56.5 MB/s (100.0%) remaining 0s.
Restored 2950 files, 347 directories and 0 symbolic links (3 GB).
</syntaxhighlight>
}}

[[Category: Backup]]

Category:Backup

2026-06-04T09:42:29Z

Sst-ska: Created blank page

Kopia restore process

2026-06-04T09:42:20Z

Sst-ska: Created page with "Category: Backup"

[[Category: Backup]]

Main Page

2026-06-04T09:41:57Z

Sst-ska: /* Overview */

<div style="float:left; width:48%;">
== Introduction ==
Welcome to the wiki of our [https://www.openstack.org/ OpenStack] based [https://www.stoney-cloud.com/ stoney cloud] infrastructure.
This collection serves as a comprehensive resource for all aspects of our cloud environment. Here, you will find guides for managing and utilizing our stoney cloud.

== Getting started ==
[[Quickstart]]

</div>

<div style="float:right; width:48%">

== Overview ==

[[:Category:Projects|Projects]]

[[:Category:Instances|Instances]]
* [[VM creation (Linux)]]
* [[VM creation (Windows)]]
* [[VM resize (Linux)]]
* [[VM resize (Windows)]]
* [[Flavor explanation]]
[[:Category:Volumes|Volumes]]
* [[Quota]]

[[:Category:Images|Images]]
* [[Image creation]]
[[:Category:Network|Network]]
* [[Security group rules]]
* [[IP usage]]

[[:Category:Object store|Object store]]
* [[S3 buckets]]

[[:Category:Kubernetes|Kubernetes]]
* [[Kubernetes management]]
* [[Kubernetes usage]]

[[:Category:AI on demand|AI on demand]]
* [[AI on demand: Usage]] (list models, show usage, ...)
* [[AI on demand: BAAI/bge-m3]]
* [[AI on demand: BAAI/bge-reranker-v2-m3]]
* [[AI on demand: MiniMaxAI/MiniMax-M2.5]]
* [[AI on demand: NVIDIA/NVIDIA-Nemotron-3-Super-120B-A12B]]
* [[AI on demand: Qwen/Qwen3-Coder-Next]]
* [[AI on demand: Qwen/Qwen3.5-35B-A3B-FP8]]
* [[AI on demand: allenai/olmOCR-2-7B]]
* [[AI on demand: lightonai/LightOnOCR-2-1B]]
* [[AI on demand: mistralai/Voxtral-Mini-3B-2507]]
* [[AI on demand: openai/whisper-large-v3]]
* [[AI on demand: opendatalab/MinerU2.5-2509-1.2B]]
* <s>[[AI on demand: swiss-ai/Apertus-70B-Instruct-2509]]</s> (discontinued since the 7th of May 2026!)

[[:Category:Backup|Backup]]
* [[Kopia restore process]]
[[:Category:Troubleshooting|Troubleshooting]]
* [[PCI workaround]]
* [[Change user password]]

== Quick links ==
* [https://www.stoney-cloud.com/ stoney cloud Website]
* [https://dashboard.stoney-cloud.com/ stoney cloud Dashboard]
* [https://docs.openstack.org/horizon/latest/user/index.html Official OpenStack Dashboard Documentation]
* [https://docs.openstack.org/python-openstackclient/latest/cli/index.html Official OpenStack CLI Documentation]
</div>

<div style="clear:both; height:0px; line-height:0px;"></div>

__NOTOC__

IP usage

2025-06-25T14:50:56Z

Sst-ska:

= Overview =
This page describes the usage of IP's on VM's either via [https://dashboard.stoney-cloud.com dashboard] or command line interface (CLI).

The following manuals are laid out for Ubuntu.

<tabber>
|-|IP usage CLI=
= Example chapter =
|-|IP usage Dashboard=
= Associate floating IP =
Select the right project by clicking on the '''current project (1)''' and selecting the '''project you want to work with (2)'''.
[[File:IP usage 1.png|none|600px]]
After that navigate to '''Network (1) -> Floating IP's (2)'''.

Click on the '''Button next to Associate (3)''' to associate this IP to a server.
[[File:IP usage 2.png|none|600px]]
In the pop-up select the '''port (1)''' you want to associate the chosen floating IP to.

Usually ports are named after their server. After that '''Associate (2)''' the floating IP.
[[File:IP usage 3.png|none|600px]]
If a floating IP is associated to a server it will appear as such in the Floating IP's menu.

There the Mapped Fixed IP Address Attribute shows the server which uses the floating IP.
[[File:IP usage 7.png|none|600px]]
To disassociate a floating IP you need to change to '''Instances (1)'''.

There it is possible to search for an instance using it's attributes as a filter. In this example I searched for the '''instance name (2)'''.

On the displayed instance overview we can now open the '''submenu (3)''' to perform quick actions.
[[File:IP usage 4.png|none|600px]]
There you can chose '''Disassociate Floating IP (1)'''.
[[File:IP usage 5.png|none|600px]]
This opens a pop-up window with an overview of our planned action.

If a server uses more than one floating IP it's possible to chose the right one here.

If you're positive press '''Dissociate'''. This will remove the floating IP from the server.
[[File:IP usage 6.png|none|600px]]
</tabber>
[[Category: CLI]]
[[Category: Network]]

IP usage

2025-06-25T14:50:14Z

Sst-ska:

= Overview =
This page describes the usage of IP's on VM's either via [https://dashboard.stoney-cloud.com dashboard] or command line interface (CLI).

The following manuals are laid out for Ubuntu.

<tabber>
|-|IP usage CLI=
= Example chapter =
|-|IP usage Dashboard=
= Associate floating IP =
Select the right project by clicking on the '''current project (1)''' and selecting the '''project you want to work with (2)'''.
[[File:IP usage 1.png|none|600px]]
After that navigate to '''Network (1) -> Floating IP's (2)'''.

Click on the '''Button next to Associate (3)''' to associate this IP to a server.
[[File:IP usage 2.png|none|600px]]
In the pop-up select the '''port (1)''' you want to associate the chosen floating IP to.

Usually ports are named after their server. After that '''Associate (2)''' the floating IP.
[[File:IP usage 3.png|none|600px]]
If a floating IP is associated to a server it will appear as such in the Floating IP's menu.
There the Mapped Fixed IP Address Attribute shows the server which uses the floating IP.
[[File:IP usage 7.png|none|600px]]
To disassociate a floating IP you need to change to '''Instances (1)'''.

There it is possible to search for an instance using it's attributes as a filter. In this example I searched for the '''instance name (2)'''.

On the displayed instance overview we can now open the '''submenu (3)''' to perform quick actions.
[[File:IP usage 4.png|none|600px]]
There you can chose '''Disassociate Floating IP (1)'''.
[[File:IP usage 5.png|none|600px]]
This opens a pop-up window with an overview of our planned action.

If a server uses more than one floating IP it's possible to chose the right one here.

If you're positive press '''Dissociate'''. This will remove the floating IP from the server.
[[File:IP usage 6.png|none|600px]]
</tabber>
[[Category: CLI]]
[[Category: Network]]

IP usage

2025-06-25T14:48:48Z

Sst-ska:

= Overview =
This page describes the usage of IP's on VM's either via [https://dashboard.stoney-cloud.com dashboard] or command line interface (CLI).

The following manuals are laid out for Ubuntu.

<tabber>
|-|IP usage CLI=
= Example chapter =
|-|IP usage Dashboard=
= Associate floating IP =
Select the right project by clicking on the '''current project (1)''' and selecting the '''project you want to work with (2)'''.
[[File:IP usage 1.png|none|600px]]
After that navigate to '''Network (1) -> Floating IP's (2)'''. Click on the '''Button next to Associate (3)''' to associate this IP to a server.
[[File:IP usage 2.png|none|600px]]
In the pop-up select the '''port (1)''' you want to associate the chosen floating IP to. Usually ports are named after their server. After that '''Associate (2)''' the floating IP.
[[File:IP usage 3.png|none|600px]]
If a floating IP is associated to a server it will appear as such in the Floating IP's menu. There the Mapped Fixed IP Address Attribute shows the server which uses the floating IP.
[[File:IP usage 7.png|none|600px]]
To disassociate a floating IP you need to change to '''Instances (1)'''. There it is possible to search for an instance using it's attributes as a filter. In this example I searched for the '''instance name (2)'''. On the displayed instance overview we can now open the '''submenu (3)''' to perform quick actions.
[[File:IP usage 4.png|none|600px]]
There you can chose '''Disassociate Floating IP (1)'''.
[[File:IP usage 5.png|none|600px]]
This opens a pop-up window with an overview of our planned action. If a server uses more than one floating IP it's possible to chose the right one here. If you're positive press '''Dissociate'''. This will remove the floating IP from the server.
[[File:IP usage 6.png|none|600px]]
</tabber>
[[Category: CLI]]
[[Category: Network]]

IP usage

2025-06-25T14:46:38Z

Sst-ska:

= Overview =
This page describes the usage of IP's on VM's either via [https://dashboard.stoney-cloud.com dashboard] or command line interface (CLI).

The following manuals are laid out for Ubuntu.

<tabber>
|-|IP usage CLI=
= Example chapter =
|-|IP usage Dashboard=
= Associate floating IP =
Select the right project by clicking on the '''current project (1)''' and selecting the '''project you want to work with (2)'''.
[[File:IP usage 1.png|600px|frame]]
After that navigate to '''Network (1) -> Floating IP's (2)'''. Click on the '''Button next to Associate (3)''' to associate this IP to a server.
[[File:IP usage 2.png|600px|frame]]
In the pop-up select the '''port (1)''' you want to associate the chosen floating IP to. Usually ports are named after their server. After that '''Associate (2)''' the floating IP.
[[File:IP usage 3.png|600px|frame]]
If a floating IP is associated to a server it will appear as such in the Floating IP's menu. There the Mapped Fixed IP Address Attribute shows the server which uses the floating IP.
[[File:IP usage 7.png|600px|frame]]
To disassociate a floating IP you need to change to '''Instances (1)'''. There it is possible to search for an instance using it's attributes as a filter. In this example I searched for the '''instance name (2)'''. On the displayed instance overview we can now open the '''submenu (3)''' to perform quick actions.
[[File:IP usage 4.png|600px|frame]]
There you can chose '''Disassociate Floating IP (1)'''.
[[File:IP usage 5.png|600px|frame]]
This opens a pop-up window with an overview of our planned action. If a server uses more than one floating IP it's possible to chose the right one here. If you're positive press '''Dissociate'''. This will remove the floating IP from the server.
[[File:IP usage 6.png|600px|frame]]
</tabber>
[[Category: CLI]]
[[Category: Network]]

IP usage

2025-06-25T14:45:48Z

Sst-ska:

= Overview =
This page describes the usage of IP's on VM's either via [https://dashboard.stoney-cloud.com dashboard] or command line interface (CLI).

The following manuals are laid out for Ubuntu.

<tabber>
|-|IP usage CLI=
= Example chapter =
|-|IP usage Dashboard=
= Associate floating IP =
Select the right project by clicking on the '''current project (1)''' and selecting the '''project you want to work with (2)'''.
[[File:IP usage 1.png|frame|600px]]
After that navigate to '''Network (1) -> Floating IP's (2)'''. Click on the '''Button next to Associate (3)''' to associate this IP to a server.
[[File:IP usage 2.png|frame|600px]]
In the pop-up select the '''port (1)''' you want to associate the chosen floating IP to. Usually ports are named after their server. After that '''Associate (2)''' the floating IP.
[[File:IP usage 3.png|frame|600px]]
If a floating IP is associated to a server it will appear as such in the Floating IP's menu. There the Mapped Fixed IP Address Attribute shows the server which uses the floating IP.
[[File:IP usage 7.png|frame|600px]]
To disassociate a floating IP you need to change to '''Instances (1)'''. There it is possible to search for an instance using it's attributes as a filter. In this example I searched for the '''instance name (2)'''. On the displayed instance overview we can now open the '''submenu (3)''' to perform quick actions.
[[File:IP usage 4.png|frame|600px]]
There you can chose '''Disassociate Floating IP (1)'''.
[[File:IP usage 5.png|frame|600px]]
This opens a pop-up window with an overview of our planned action. If a server uses more than one floating IP it's possible to chose the right one here. If you're positive press '''Dissociate'''. This will remove the floating IP from the server.
[[File:IP usage 6.png|frame|600px]]
</tabber>
[[Category: CLI]]
[[Category: Network]]

IP usage

2025-06-25T14:44:57Z

Sst-ska:

= Overview =
This page describes the usage of IP's on VM's either via [https://dashboard.stoney-cloud.com dashboard] or command line interface (CLI).

The following manuals are laid out for Ubuntu.

<tabber>
|-|IP usage CLI=
= Example chapter =
|-|IP usage Dashboard=
= Associate floating IP =
Select the right project by clicking on the '''current project (1)''' and selecting the '''project you want to work with (2)'''.
[[File:IP usage 1.png|frameless|600px]]
After that navigate to '''Network (1) -> Floating IP's (2)'''. Click on the '''Button next to Associate (3)''' to associate this IP to a server.
[[File:IP usage 2.png|frameless|600px]]
In the pop-up select the '''port (1)''' you want to associate the chosen floating IP to. Usually ports are named after their server. After that '''Associate (2)''' the floating IP.
[[File:IP usage 3.png|frameless|600px]]
If a floating IP is associated to a server it will appear as such in the Floating IP's menu. There the Mapped Fixed IP Address Attribute shows the server which uses the floating IP.
[[File:IP usage 7.png|frameless|600px]]
To disassociate a floating IP you need to change to '''Instances (1)'''. There it is possible to search for an instance using it's attributes as a filter. In this example I searched for the '''instance name (2)'''. On the displayed instance overview we can now open the '''submenu (3)''' to perform quick actions.
[[File:IP usage 4.png|frameless|600px]]
There you can chose '''Disassociate Floating IP (1)'''.
[[File:IP usage 5.png|frameless|600px]]
This opens a pop-up window with an overview of our planned action. If a server uses more than one floating IP it's possible to chose the right one here. If you're positive press '''Dissociate'''. This will remove the floating IP from the server.
[[File:IP usage 6.png|frameless|600px]]
</tabber>
[[Category: CLI]]
[[Category: Network]]

IP usage

2025-06-25T14:44:01Z

Sst-ska:

= Overview =
This page describes the usage of IP's on VM's either via [https://dashboard.stoney-cloud.com dashboard] or command line interface (CLI).

The following manuals are laid out for Ubuntu.

<tabber>
|-|IP usage CLI=
= Example chapter =
|-|IP usage Dashboard=
= Associate floating IP =
Select the right project by clicking on the '''current project (1)''' and selecting the '''project you want to work with (2)'''.
[[File:IP usage 1.png|600px]]
After that navigate to '''Network (1) -> Floating IP's (2)'''. Click on the '''Button next to Associate (3)''' to associate this IP to a server.
[[File:IP usage 2.png|600px]]
In the pop-up select the '''port (1)''' you want to associate the chosen floating IP to. Usually ports are named after their server. After that '''Associate (2)''' the floating IP.
[[File:IP usage 3.png|600px]]
If a floating IP is associated to a server it will appear as such in the Floating IP's menu. There the Mapped Fixed IP Address Attribute shows the server which uses the floating IP.
[[File:IP usage 7.png|frame|600px]]
To disassociate a floating IP you need to change to '''Instances (1)'''. There it is possible to search for an instance using it's attributes as a filter. In this example I searched for the '''instance name (2)'''. On the displayed instance overview we can now open the '''submenu (3)''' to perform quick actions.
[[File:IP usage 4.png|600px]]
There you can chose '''Disassociate Floating IP (1)'''.
[[File:IP usage 5.png|frame|600px]]
This opens a pop-up window with an overview of our planned action. If a server uses more than one floating IP it's possible to chose the right one here. If you're positive press '''Dissociate'''. This will remove the floating IP from the server.
[[File:IP usage 6.png|frame|600px]]
</tabber>
[[Category: CLI]]
[[Category: Network]]

IP usage

2025-06-25T14:41:47Z

Sst-ska:

= Overview =
This page describes the usage of IP's on VM's either via [https://dashboard.stoney-cloud.com dashboard] or command line interface (CLI).

The following manuals are laid out for Ubuntu.

<tabber>
|-|IP usage CLI=
= Example chapter =
|-|IP usage Dashboard=
= Associate floating IP =
Select the right project by clicking on the '''current project (1)''' and selecting the '''project you want to work with (2)'''.
[[File:IP usage 1.png|600px]]
After that navigate to '''Network (1) -> Floating IP's (2)'''. Click on the '''Button next to Associate (3)''' to associate this IP to a server.
[[File:IP usage 2.png|600px]]
In the pop-up select the '''port (1)''' you want to associate the chosen floating IP to. Usually ports are named after their server. After that '''Associate (2)''' the floating IP.
[[File:IP usage 3.png|600px]]
If a floating IP is associated to a server it will appear as such in the Floating IP's menu. There the Mapped Fixed IP Address Attribute shows the server which uses the floating IP.
[[File:IP usage 7.png|600px]]
To disassociate a floating IP you need to change to '''Instances (1)'''. There it is possible to search for an instance using it's attributes as a filter. In this example I searched for the '''instance name (2)'''. On the displayed instance overview we can now open the '''submenu (3)''' to perform quick actions.
[[File:IP usage 4.png|600px]]
There you can chose '''Disassociate Floating IP (1)'''.
[[File:IP usage 5.png|600px]]
This opens a pop-up window with an overview of our planned action. If a server uses more than one floating IP it's possible to chose the right one here. If you're positive press '''Dissociate'''. This will remove the floating IP from the server.
[[File:IP usage 6.png|600px]]
</tabber>
[[Category: CLI]]
[[Category: Network]]

IP usage

2025-06-25T14:41:07Z

Sst-ska:

= Overview =
This page describes the usage of IP's on VM's either via [https://dashboard.stoney-cloud.com dashboard] or command line interface (CLI).

The following manuals are laid out for Ubuntu.

<tabber>
|-|IP usage CLI=
= Example chapter =
|-|IP usage Dashboard=
= Associate floating IP =
Select the right project by clicking on the '''current project (1)''' and selecting the '''project you want to work with (2)'''.
[[File:IP usage 1.png|thumb|600px]]
After that navigate to '''Network (1) -> Floating IP's (2)'''. Click on the '''Button next to Associate (3)''' to associate this IP to a server.
[[File:IP usage 2.png|thumb|600px]]
In the pop-up select the '''port (1)''' you want to associate the chosen floating IP to. Usually ports are named after their server. After that '''Associate (2)''' the floating IP.
[[File:IP usage 3.png|thumb|600px]]
If a floating IP is associated to a server it will appear as such in the Floating IP's menu. There the Mapped Fixed IP Address Attribute shows the server which uses the floating IP.
[[File:IP usage 7.png|thumb|600px]]
To disassociate a floating IP you need to change to '''Instances (1)'''. There it is possible to search for an instance using it's attributes as a filter. In this example I searched for the '''instance name (2)'''. On the displayed instance overview we can now open the '''submenu (3)''' to perform quick actions.
[[File:IP usage 4.png|thumb|600px]]
There you can chose '''Disassociate Floating IP (1)'''.
[[File:IP usage 5.png|600px]]
This opens a pop-up window with an overview of our planned action. If a server uses more than one floating IP it's possible to chose the right one here. If you're positive press '''Dissociate'''. This will remove the floating IP from the server.
[[File:IP usage 6.png|thumb|600px]]
</tabber>
[[Category: CLI]]
[[Category: Network]]

IP usage

2025-06-25T14:37:50Z

Sst-ska:

= Overview =
This page describes the usage of IP's on VM's either via [https://dashboard.stoney-cloud.com dashboard] or command line interface (CLI).

The following manuals are laid out for Ubuntu.

<tabber>
|-|IP usage CLI=
= Example chapter =
|-|IP usage Dashboard=
= Associate floating IP =
Select the right project by clicking on the '''current project (1)''' and selecting the '''project you want to work with (2)'''.
[[File:IP usage 1.png|600px]]
After that navigate to '''Network (1) -> Floating IP's (2)'''. Click on the '''Button next to Associate (3)''' to associate this IP to a server.
[[File:IP usage 2.png|600px]]
In the pop-up select the '''port (1)''' you want to associate the chosen floating IP to. Usually ports are named after their server. After that '''Associate (2)''' the floating IP.
[[File:IP usage 3.png|600px]]
If a floating IP is associated to a server it will appear as such in the Floating IP's menu. There the Mapped Fixed IP Address Attribute shows the server which uses the floating IP.
[[File:IP usage 7.png|600px]]
To disassociate a floating IP you need to change to '''Instances (1)'''. There it is possible to search for an instance using it's attributes as a filter. In this example I searched for the '''instance name (2)'''. On the displayed instance overview we can now open the '''submenu (3)''' to perform quick actions.
[[File:IP usage 4.png|600px]]
There you can chose '''Disassociate Floating IP (1)'''.
[[File:IP usage 5.png|600px]]
This opens a pop-up window with an overview of our planned action. If a server uses more than one floating IP it's possible to chose the right one here. If you're positive press '''Dissociate'''. This will remove the floating IP from the server.
[[File:IP usage 6.png|600px]]
</tabber>
[[Category: CLI]]
[[Category: Network]]

IP usage

2025-06-25T14:23:35Z

Sst-ska: /* Overview */

File:IP usage 6.png

2025-06-25T14:22:01Z

Sst-ska: Sst-ska uploaded a new version of File:IP usage 6.png

File:IP usage 5.png

2025-06-25T14:21:48Z

Sst-ska: Sst-ska uploaded a new version of File:IP usage 5.png

File:IP usage 4.png

2025-06-25T14:21:39Z

Sst-ska: Sst-ska uploaded a new version of File:IP usage 4.png

File:IP usage 3.png

2025-06-25T14:21:28Z

Sst-ska: Sst-ska uploaded a new version of File:IP usage 3.png

File:IP usage 2.png

2025-06-25T14:21:20Z

Sst-ska: Sst-ska uploaded a new version of File:IP usage 2.png

File:IP usage 1.png

2025-06-25T14:21:10Z

Sst-ska: Sst-ska uploaded a new version of File:IP usage 1.png

IP usage

2025-06-25T14:06:34Z

Sst-ska: /* Overview */

IP usage

2025-06-25T14:05:59Z

Sst-ska: /* Overview */

IP usage

2025-06-25T14:04:47Z

Sst-ska: /* Overview */

File:IP usage 7.png

2025-06-25T14:04:42Z

Sst-ska:

File:IP usage 6.png

2025-06-25T14:04:19Z

Sst-ska:

File:IP usage 4.png

2025-06-25T14:03:55Z

Sst-ska:

File:IP usage 5.png

2025-06-25T14:03:34Z

Sst-ska:

File:IP usage 3.png

2025-06-25T14:03:09Z

Sst-ska:

File:IP usage 2.png

2025-06-25T14:02:48Z

Sst-ska:

File:IP usage 1.png

2025-06-25T14:02:16Z

Sst-ska:

IP usage

2025-06-24T13:13:03Z

Sst-ska:

IP usage

2025-06-24T13:12:07Z

Sst-ska:

IP usage

2025-06-24T13:10:29Z

Sst-ska:

= Overview =
This page describes the usage of IP's on VM's either via [https://dashboard.stoney-cloud.com dashboard] or command line interface (CLI).

The following manuals are laid out for Ubuntu.

<tabber>
|-|IP usage CLI=
= OpenStack CLI Installation =

|-|IP usage Dashboard=

= Login via Dashboard =

</tabber>
[[Category: CLI]]
[[Category: Network]]

IP usage

2025-06-24T13:09:30Z

Sst-ska: Created page with "= Overview = This page describes the process of creating a virtual machine (VM) either via [https://dashboard.stoney-cloud.com dashboard] or command line interface (CLI). The following manuals are laid out for Ubuntu. <tabber> |-|VM creation CLI= = OpenStack CLI Installation = |-|VM creation Dashboard= = Login via Dashboard = </tabber> Category: CLI Category: Network"

Main Page

2025-06-24T13:06:38Z

Sst-ska: /* Overview */

VM creation (Windows)

2024-07-15T13:37:06Z

Sst-ska:

= Overview =
This page describes the process of creating a virtual machine (VM) either via [https://dashboard.stoney-cloud.com dashboard] or command line interface (CLI).

The following manuals are laid out for Windows.

<tabber>
|-|VM creation CLI=
= OpenStack CLI Installation =
To use OpenStack CLI, you need to install the OpenStack CLI Client for your OS:
<syntaxhighlight lang="bash">
# Fedora
dnf install python3-openstackclient
# Debian / Ubuntu
apt install python3-openstackclient
</syntaxhighlight>
The official installaton guide can be found on [https://docs.openstack.org/mitaka/user-guide/common/cli_install_openstack_command_line_clients.html docs.openstack.org].

= OpenStack client environment script (OpenRC file) =
To increase efficiency of client operations, OpenStack supports simple client environment scripts also known as OpenRC files. These scripts typically contain common options for all clients, but also support unique options.

You may download such an OpenRC file from the [https://dashboard.stoney-cloud.com/ dashboard].

After logging into the [https://dashboard.stoney-cloud.com/ dashboard], click on your user name in the upper right corner and choose the menu option «OpenStack RC File v3» and save it the desired location on your local machine. As you can have multiple OpenRC files, we recommend to use a sub directory. For example <code>openrc</code> in your home directory.

[[Image:OpenStack_RC_File_v3.png|600px]]

Source the OpenRC file specific to this project (use single quotation marks to avoid problems with spaces in the file name):
<syntaxhighlight lang='bash'>
source ${HOME}/openrc/'Project Name-openrc.sh'
</syntaxhighlight>

After you sourced the file, you need to enter a password:
<syntaxhighlight lang="text">
Please enter your OpenStack Password for project Project Name as user user:
</syntaxhighlight>

Check if you have access to the OpenStack API by listing the API endpoints:
<syntaxhighlight lang='bash'>
openstack catalog list
</syntaxhighlight>

Expected output:
<syntaxhighlight lang='text'>
+------------+-----------+--------------------------------------------------------------------------------------------------+
| Name | Type | Endpoints |
+------------+-----------+--------------------------------------------------------------------------------------------------+
| glance | image | duedingen-production |
| | | internal: https://glance.ctrl-int.os.stoney-cloud.com:9292 |
| | | duedingen-production |
| | | public: https://api.os.stoney-cloud.com:9292 |
| | | duedingen-production |
| | | admin: https://glance.ctrl-int.os.stoney-cloud.com:9292 |
[...]
| cinderv2 | volumev2 | duedingen-production |
| | | internal: https://cinder.ctrl-int.os.stoney-cloud.com:8776/v2/616812eda14e44de89138f3377841187 |
| | | duedingen-production |
| | | admin: https://cinder.ctrl-int.os.stoney-cloud.com:8776/v2/616812eda14e44de89138f3377841187 |
| | | duedingen-production |
| | | public: https://api.os.stoney-cloud.com:8776/v2/616812eda14e44de89138f3377841187 |
| | | |
+------------+-----------+--------------------------------------------------------------------------------------------------+
</syntaxhighlight>

= VM Creation - One-Disk Setup =
== VM Creation - One-Disk Setup - Variables ==
We define bash variables so that in every command the same value is being used.

Another advantage of variables is, that the documentation is significantly easier, as another person could replicate the server if they know the variables that were set.

Set the following variables that we will use in later commands:
<syntaxhighlight lang='bash'>
# Host name of the server. Example: hostname="sst-int-tmp-041"
hostname=""

# Display name of the server in OpenStack. Example: vmname="sst-int-tmp-041: debian test cli"
vmname=""

# Domain name. Example: domain="os.stoney-cloud.com"
domain=""
</syntaxhighlight>

We need to set the <code>project_id</code> variable to the project our previously sourced openrc file belongs to:
<syntaxhighlight lang='bash'>
# List the projects of your OpenStack domain.
openstack project list

# Project ID of the project in which the VM will be created.
# Example (stepping stone AG - Internal Systems Temporary): project_id="6fd0ccd8b5ae44d292c67f0d3e75ca20"
project_id=""
</syntaxhighlight>

A flavour defines the CPU and RAM resources of the VM.

The flavour is in the following format: <code>cXXmYYYY</code> where <code>XX</code> is the amount of CPUs and <code>YYYY</code> the about of RAM:
<syntaxhighlight lang='bash'>
# List all available flavors
openstack flavor list --column Name --column ID | tail -n+3 | head -n-1 | sort -k3 -t'|' | grep Windows

# Set the flavor ID, default: Standard Düdingen c001m0004 (719c82d4-df94-47fc-a7df-f18d5c6d3727).
# Example: flavor_id="719c82d4-df94-47fc-a7df-f18d5c6d3727"
flavor_id=""
</syntaxhighlight>

We will add our VM to the <code>internal</code> network of our project. This is the default network:
<syntaxhighlight lang='bash'>
# List the networks of the current project
openstack network list --project ${project_id}

# Network ID, usually the ID for the network "internal".
# Example: network_id="919c2dde-6996-494a-86de-fc3b08248418"
network_id=""
</syntaxhighlight>

For this example, we use the "SSH" and "default" security groups (firewall-rules), so that we can access our server via ssh:
<syntaxhighlight lang='bash'>
# List the security groups of the current project and search for ssh and default
openstack security group list --project ${project_id} | egrep -i '(ssh|default)'

# We set the default security group ID "default" ("default" is required for outgoing traffic!):
# Example: default_security_group_id="3f576bd2-11fe-47f3-806e-aaa219cff589" # default
default_security_group_id=""

# We set the "SSH World" security group ID:
# Example: ssh_security_group_id="8083a9f3-e6c0-4061-b4bb-eb0dd24a86ef" # SSH World
ssh_security_group_id=""
</syntaxhighlight>

== VM Creation - One-Disk Setup - Disk creation ==
In OpenStack every Image has an ID.

To create a new VM, we need to create a disk first.

We can list the available images using the openstack-cli - we search for Ubuntu:
<syntaxhighlight lang='bash'>
openstack image list | grep "Windows"
</syntaxhighlight>
Expected output:
<syntaxhighlight lang='text'>
| 053129aa-48b5-40d2-8784-7215fcc62d48 | Windows Server 2012R2 import | active |
| 1004d7c3-da11-404b-bfa7-9f7df18f1966 | Windows Server 2016 Standard | active |
| a68f3f5f-db1f-4610-9931-cb3adf887b8d | Windows Server 2016 Standard (deprecated) | active |
| 9868a8b8-4953-4d16-a078-ba7238fa0a1d | Windows Server 2019 Standard | active |
| 4c56a79b-a2f5-47be-9de0-ce808f5b77cc | Windows Server 2019 Standard - Private | active |
| 3f9bfb18-a263-4e2e-9555-dea8d12bb6ae | Windows Server 2022 Standard (20230928): Primary disk /dev/vda (C:\) | active |
| 93a888a4-abb7-408b-8976-969718a7e5a7 | Windows Server 2022 Standard (deprecated) | active |

</syntaxhighlight>

We set the ID of the image and the size of the disk as variables for later use.
<syntaxhighlight lang='bash'>
# Set the Image ID used for the first volume (Windows Server 2022 Standard (20230928): Primary disk /dev/vda (C:\))
vda_image_id="3f9bfb18-a263-4e2e-9555-dea8d12bb6ae"

# Size for the first volume in GiB
volume_size_vda="10"
</syntaxhighlight>

Now we can create the volume using the variables we just set.

We can set <code>volume_vda_id</code> as the command returns the ID of the newly created disk:
{| style="background-color:rgba(255,0,0,0);border-width:0px;"
|
<syntaxhighlight lang='bash'>
volume_vda_id=$(
openstack volume create \
--property os-vol-tenant-attr:tenant_id=${project_id} \
--bootable \
--size ${volume_size_vda} \
--image ${vda_image_id} \
--description "OS disk (/dev/vda) for ${hostname}." \
--column id \
--format value \
"${hostname}: OS"
)
</syntaxhighlight>
|
<syntaxhighlight lang='bash' line='line' >
Set the variable ${volume_vda_id}.
Creates a new disk.
The disk belongs to the current project.
The disk can be bootable.
The size of the disk is ${volume_size_vda}.
The image of the disk is ${vda_image_id.
We set the description of the disk.
The id column will be printed out as output.
Only the value will be printed out as output.
Name of the disk.
-
</syntaxhighlight>
|}

We ask OpenStack for the status of the current disk.

If the disk has been successfully created, we can move on and create the VM:
<syntaxhighlight lang='bash'>
openstack volume show \
"${volume_vda_id}" \
--column status \
--format value
</syntaxhighlight>

Expected output:
<syntaxhighlight lang='text'>
available
</syntaxhighlight>

== VM Creation - One-Disk Setup - VM creation ==
We can create the server using the <code>openstack server create</code> command:
{|
|
<syntaxhighlight lang='bash'>
server_id=$(
openstack server create \
--property project_id=${project_id} \
--flavor "${flavor_id}" \
--nic "net-id=${network_id}" \
--volume "${volume_vda_id}" \
--security-group "${default_security_group_id}" \
--security-group "${ssh_security_group_id}" \
--column id \
--format value \
"${vmname}"
)
</syntaxhighlight>

|
<syntaxhighlight lang='text' line='line'>
We set the server_id variable to the OpenStack id of the server.
We create a new VM.
We set the project to ${project_id}.
We set the flavor to ${flavor_id}.
We set the nic to ${network_id}.
We set the volume to ${volume_vda_id}.
Use the security-group (firwall rule) ${default_security_group_id}.
Use the security-group (firwall rule) ${ssh_security_group_id}.
We use our previously generated clopud init script as user-data.
The id column will be printed out as output.
Only the value will be printed out as output.
We set the name of the VM.
-
</syntaxhighlight>
|}

Check the status of the newly created instance (should be ACTIVE)
<syntaxhighlight lang='bash'>
openstack server show ${server_id} --column status
</syntaxhighlight>
Expected Output:
<syntaxhighlight lang='text'>
+--------+--------+
| Field | Value |
+--------+--------+
| status | ACTIVE |
+--------+--------+
</syntaxhighlight>

== VM Creation - One-Disk Setup - VM Login ==

Log in to the stoney cloud [https://dashboard.stoney-cloud.com/dashboard dashboard] with the credentials you have received from us.

[[File:Debian VM Creation Dashboard manual 01.png|600px]]

1. Select the appropriate project from the drop down menu at the top left.

2. On the <code>Project</code> tab, open the <code>Compute tab</code> and click <code>Instances</code> category.

[[File:Introduction_to_the_Dashboard_02.png|600px]]

3. Click on the instance name of your VM

[[File:Introduction_to_the_Dashboard_03.png|600px]]

Enter the <code>console</code> tab and set a new administrator password.

Finally, you can connect to your newly created VM by using xfreerdp:

<syntaxhighlight lang='bash'>
password=''
xfreerdp --ignore-certificate --plugin cliprdr -g 1440x900 -u Administrator@PROD-RMA -p $password 127.0.0.1
</syntaxhighlight>

== VM Creation - One-Disk Setup - Checks ==
To verify that the VM got set up correctly start PowerShell as Administrator and run these commands:

Check if the correct image was selected:
<syntaxhighlight lang="powershell">
systeminfo | findstr /B /C:"OS Name" /C:"OS Version"
</syntaxhighlight>
<syntaxhighlight lang="powershell">
OS Name: Microsoft Windows Server 2022 Standard
OS Version: 10.0.20348 N/A Build 20348
</syntaxhighlight>

Check if the disks are mounted correctly:
<syntaxhighlight lang="powershell">
Get-Disk
</syntaxhighlight>
<syntaxhighlight lang="powershell">
Number Friendly Name Serial Number HealthStatus OperationalStatus Total Size Partition Style ------ ------------- ------------- ------------ ----------------- ---------- ---------- 0
Red Hat Vi... 1f4afc6e-be44-4c29-b Healthy Online 20 GB MBR
</syntaxhighlight>

Check if you selected the correct flavour:
<syntaxhighlight lang="powershell">
(Get-CimInstance Win32_PhysicalMemory | Measure-Object -Property capacity -Sum).sum /1gb
(Get-CimInstance Win32_ComputerSystem).NumberOfLogicalProcessors
</syntaxhighlight>
<syntaxhighlight lang="powershell">
4
1
</syntaxhighlight>

|-|VM creation Dashboard=

= Login via Dashboard =
Log in to the stoney cloud [https://dashboard.stoney-cloud.com/dashboard dashboard] with the credentials you have received from us.

[[File:Debian VM Creation Dashboard manual 01.png|600px]]

= Launch Instance - Preperations =
1. Select the appropriate project from the drop down menu at the top left.

3. On the <code>Project</code> tab, open the <code>Compute tab</code> and click <code>Instances</code> category.

4. Click <code>Launch Instance</code>.

[[File:Windows VM Creation Dashboard manual 02.png|600px]]

5. A dialog box opens. Specify the values as follows:
* '''Instance Name''': Assign a name to the virtual machine.
* Click <code>Source</code> tab and chose '''Image''' in '''Select Boot Source'''.
* Type '''Windows''' in the search bar below and allocate the image 'Windows Server 2019 Standard' from the image list by clicking the arrow pointing up.
[[File:Windows Creation Dashboard manual 03.png|600px]]

* Click <code>Flavour</code> tab and allocate the desired Flavour (For example: Standard Düdingen c001m0002) from the list below by clicking the arrow pointing up.
[[File:Windows Creation Dashboard manual 04.png|600px]]

* Click <code>Networks</code> and allocate the network '''internal''' from the list below by clicking the arrow pointing up.
[[File:Windows Creation Dashboard manual 05.png|600px]]

* Click <code>Security Groups</code> and allocate the security group '''RDP World''' from the list below by clicking the arrow pointing up.
[[File:Windows Creation Dashboard manual 06.png|600px]]

Click<code>Launch Instance</code> to create the VM. After no more than a minute the VM is created and listed in the <code>Instances</code> page.
'''Bild einfügen'''

= VM Login =

Log in to the stoney cloud [https://dashboard.stoney-cloud.com/dashboard dashboard] with the credentials you have received from us.

[[File:Debian VM Creation Dashboard manual 01.png|600px]]

1. Select the appropriate project from the drop down menu at the top left.

2. On the <code>Project</code> tab, open the <code>Compute tab</code> and click <code>Instances</code> category.

[[File:Introduction_to_the_Dashboard_02.png|600px]]

3. Click on the instance name of your VM

[[File:Introduction_to_the_Dashboard_03.png|600px]]

Enter the <code>console</code> tab and set a new administrator password.

Finally, you can connect to your newly created VM by using xfreerdp:

<syntaxhighlight lang='bash'>
password=''
xfreerdp --ignore-certificate --plugin cliprdr -g 1440x900 -u Administrator@PROD-RMA -p $password 127.0.0.1
</syntaxhighlight>
</tabber>

[[Category: CLI]]
[[Category: Dashboard]]
[[Category: Instances]]

VM creation (Windows)

2024-07-15T13:36:33Z

Sst-ska:

= Overview =
This page describes the process of creating a virtual machine (VM) either via [https://dashboard.stoney-cloud.com dashboard] or command line interface (CLI).

The following manuals are laid out for Windows.

<tabber>
|-|VM creation CLI=
= OpenStack CLI Installation =
To use OpenStack CLI, you need to install the OpenStack CLI Client for your OS:
<syntaxhighlight lang="bash">
# Fedora
dnf install python3-openstackclient
# Debian / Ubuntu
apt install python3-openstackclient
</syntaxhighlight>
The official installaton guide can be found on [https://docs.openstack.org/mitaka/user-guide/common/cli_install_openstack_command_line_clients.html docs.openstack.org].

= OpenStack client environment script (OpenRC file) =
To increase efficiency of client operations, OpenStack supports simple client environment scripts also known as OpenRC files. These scripts typically contain common options for all clients, but also support unique options.

You may download such an OpenRC file from the [https://dashboard.stoney-cloud.com/ dashboard].

After logging into the [https://dashboard.stoney-cloud.com/ dashboard], click on your user name in the upper right corner and choose the menu option «OpenStack RC File v3» and save it the desired location on your local machine. As you can have multiple OpenRC files, we recommend to use a sub directory. For example <code>openrc</code> in your home directory.

[[Image:OpenStack_RC_File_v3.png|600px]]

Source the OpenRC file specific to this project (use single quotation marks to avoid problems with spaces in the file name):
<syntaxhighlight lang='bash'>
source ${HOME}/openrc/'Project Name-openrc.sh'
</syntaxhighlight>

After you sourced the file, you need to enter a password:
<syntaxhighlight lang="text">
Please enter your OpenStack Password for project Project Name as user user:
</syntaxhighlight>

Check if you have access to the OpenStack API by listing the API endpoints:
<syntaxhighlight lang='bash'>
openstack catalog list
</syntaxhighlight>

Expected output:
<syntaxhighlight lang='text'>
+------------+-----------+--------------------------------------------------------------------------------------------------+
| Name | Type | Endpoints |
+------------+-----------+--------------------------------------------------------------------------------------------------+
| glance | image | duedingen-production |
| | | internal: https://glance.ctrl-int.os.stoney-cloud.com:9292 |
| | | duedingen-production |
| | | public: https://api.os.stoney-cloud.com:9292 |
| | | duedingen-production |
| | | admin: https://glance.ctrl-int.os.stoney-cloud.com:9292 |
[...]
| cinderv2 | volumev2 | duedingen-production |
| | | internal: https://cinder.ctrl-int.os.stoney-cloud.com:8776/v2/616812eda14e44de89138f3377841187 |
| | | duedingen-production |
| | | admin: https://cinder.ctrl-int.os.stoney-cloud.com:8776/v2/616812eda14e44de89138f3377841187 |
| | | duedingen-production |
| | | public: https://api.os.stoney-cloud.com:8776/v2/616812eda14e44de89138f3377841187 |
| | | |
+------------+-----------+--------------------------------------------------------------------------------------------------+
</syntaxhighlight>

= VM Creation - One-Disk Setup =
== VM Creation - One-Disk Setup - Variables ==
We define bash variables so that in every command the same value is being used.

Another advantage of variables is, that the documentation is significantly easier, as another person could replicate the server if they know the variables that were set.

Set the following variables that we will use in later commands:
<syntaxhighlight lang='bash'>
# Host name of the server. Example: hostname="sst-int-tmp-041"
hostname=""

# Display name of the server in OpenStack. Example: vmname="sst-int-tmp-041: debian test cli"
vmname=""

# Domain name. Example: domain="os.stoney-cloud.com"
domain=""
</syntaxhighlight>

We need to set the <code>project_id</code> variable to the project our previously sourced openrc file belongs to:
<syntaxhighlight lang='bash'>
# List the projects of your OpenStack domain.
openstack project list

# Project ID of the project in which the VM will be created.
# Example (stepping stone AG - Internal Systems Temporary): project_id="6fd0ccd8b5ae44d292c67f0d3e75ca20"
project_id=""
</syntaxhighlight>

A flavour defines the CPU and RAM resources of the VM.

The flavour is in the following format: <code>cXXmYYYY</code> where <code>XX</code> is the amount of CPUs and <code>YYYY</code> the about of RAM:
<syntaxhighlight lang='bash'>
# List all available flavors
openstack flavor list --column Name --column ID | tail -n+3 | head -n-1 | sort -k3 -t'|' | grep Windows

# Set the flavor ID, default: Standard Düdingen c001m0004 (719c82d4-df94-47fc-a7df-f18d5c6d3727).
# Example: flavor_id="719c82d4-df94-47fc-a7df-f18d5c6d3727"
flavor_id=""
</syntaxhighlight>

We will add our VM to the <code>internal</code> network of our project. This is the default network:
<syntaxhighlight lang='bash'>
# List the networks of the current project
openstack network list --project ${project_id}

# Network ID, usually the ID for the network "internal".
# Example: network_id="919c2dde-6996-494a-86de-fc3b08248418"
network_id=""
</syntaxhighlight>

For this example, we use the "SSH" and "default" security groups (firewall-rules), so that we can access our server via ssh:
<syntaxhighlight lang='bash'>
# List the security groups of the current project and search for ssh and default
openstack security group list --project ${project_id} | egrep -i '(ssh|default)'

# We set the default security group ID "default" ("default" is required for outgoing traffic!):
# Example: default_security_group_id="3f576bd2-11fe-47f3-806e-aaa219cff589" # default
default_security_group_id=""

# We set the "SSH World" security group ID:
# Example: ssh_security_group_id="8083a9f3-e6c0-4061-b4bb-eb0dd24a86ef" # SSH World
ssh_security_group_id=""
</syntaxhighlight>

== VM Creation - One-Disk Setup - Disk creation ==
In OpenStack every Image has an ID.

To create a new VM, we need to create a disk first.

We can list the available images using the openstack-cli - we search for Ubuntu:
<syntaxhighlight lang='bash'>
openstack image list | grep "Windows"
</syntaxhighlight>
Expected output:
<syntaxhighlight lang='text'>
| 053129aa-48b5-40d2-8784-7215fcc62d48 | Windows Server 2012R2 import | active |
| 1004d7c3-da11-404b-bfa7-9f7df18f1966 | Windows Server 2016 Standard | active |
| a68f3f5f-db1f-4610-9931-cb3adf887b8d | Windows Server 2016 Standard (deprecated) | active |
| 9868a8b8-4953-4d16-a078-ba7238fa0a1d | Windows Server 2019 Standard | active |
| 4c56a79b-a2f5-47be-9de0-ce808f5b77cc | Windows Server 2019 Standard - Private | active |
| 3f9bfb18-a263-4e2e-9555-dea8d12bb6ae | Windows Server 2022 Standard (20230928): Primary disk /dev/vda (C:\) | active |
| 93a888a4-abb7-408b-8976-969718a7e5a7 | Windows Server 2022 Standard (deprecated) | active |

</syntaxhighlight>

We set the ID of the image and the size of the disk as variables for later use.
<syntaxhighlight lang='bash'>
# Set the Image ID used for the first volume (Windows Server 2022 Standard (20230928): Primary disk /dev/vda (C:\))
vda_image_id="3f9bfb18-a263-4e2e-9555-dea8d12bb6ae"

# Size for the first volume in GiB
volume_size_vda="10"
</syntaxhighlight>

Now we can create the volume using the variables we just set.

We can set <code>volume_vda_id</code> as the command returns the ID of the newly created disk:
{| style="background-color:rgba(255,0,0,0);border-width:0px;"
|
<syntaxhighlight lang='bash'>
volume_vda_id=$(
openstack volume create \
--property os-vol-tenant-attr:tenant_id=${project_id} \
--bootable \
--size ${volume_size_vda} \
--image ${vda_image_id} \
--description "OS disk (/dev/vda) for ${hostname}." \
--column id \
--format value \
"${hostname}: OS"
)
</syntaxhighlight>
|
<syntaxhighlight lang='bash' line='line' >
Set the variable ${volume_vda_id}.
Creates a new disk.
The disk belongs to the current project.
The disk can be bootable.
The size of the disk is ${volume_size_vda}.
The image of the disk is ${vda_image_id.
We set the description of the disk.
The id column will be printed out as output.
Only the value will be printed out as output.
Name of the disk.
-
</syntaxhighlight>
|}

We ask OpenStack for the status of the current disk.

If the disk has been successfully created, we can move on and create the VM:
<syntaxhighlight lang='bash'>
openstack volume show \
"${volume_vda_id}" \
--column status \
--format value
</syntaxhighlight>

Expected output:
<syntaxhighlight lang='text'>
available
</syntaxhighlight>

== VM Creation - One-Disk Setup - VM creation ==
We can create the server using the <code>openstack server create</code> command:
{|
|
<syntaxhighlight lang='bash'>
server_id=$(
openstack server create \
--property project_id=${project_id} \
--flavor "${flavor_id}" \
--nic "net-id=${network_id}" \
--volume "${volume_vda_id}" \
--security-group "${default_security_group_id}" \
--security-group "${ssh_security_group_id}" \
--column id \
--format value \
"${vmname}"
)
</syntaxhighlight>

|
<syntaxhighlight lang='text' line='line'>
We set the server_id variable to the OpenStack id of the server.
We create a new VM.
We set the project to ${project_id}.
We set the flavor to ${flavor_id}.
We set the nic to ${network_id}.
We set the volume to ${volume_vda_id}.
Use the security-group (firwall rule) ${default_security_group_id}.
Use the security-group (firwall rule) ${ssh_security_group_id}.
We use our previously generated clopud init script as user-data.
The id column will be printed out as output.
Only the value will be printed out as output.
We set the name of the VM.
-
</syntaxhighlight>
|}

Check the status of the newly created instance (should be ACTIVE)
<syntaxhighlight lang='bash'>
openstack server show ${server_id} --column status
</syntaxhighlight>
Expected Output:
<syntaxhighlight lang='text'>
+--------+--------+
| Field | Value |
+--------+--------+
| status | ACTIVE |
+--------+--------+
</syntaxhighlight>

== VM Creation - One-Disk Setup - VM Login ==

Log in to the stoney cloud [https://dashboard.stoney-cloud.com/dashboard dashboard] with the credentials you have received from us.

[[File:Debian VM Creation Dashboard manual 01.png|600px]]

1. Select the appropriate project from the drop down menu at the top left.

2. On the <code>Project</code> tab, open the <code>Compute tab</code> and click <code>Instances</code> category.

[[File:Introduction_to_the_Dashboard_02.png|600px]]

3. Click on the instance name of your VM

[[File:Introduction_to_the_Dashboard_03.png|600px]]

Enter the <code>console</code> tab and set a new administrator password.

Finally, you can connect to your newly created VM by using xfreerdp:

<syntaxhighlight lang='bash'>
password=''
xfreerdp --ignore-certificate --plugin cliprdr -g 1440x900 -u Administrator@PROD-RMA -p $password 127.0.0.1
</syntaxhighlight>

== VM Creation - One-Disk Setup - Checks ==
To verify that the VM got set up correctly start PowerShell as Administrator and run these commands:

Check if the correct image was selected:
<syntaxhighlight lang="powershell">
systeminfo | findstr /B /C:"OS Name" /C:"OS Version"
</syntaxhighlight>
<syntaxhighlight lang="powershell">
OS Name: Microsoft Windows Server 2022 Standard
OS Version: 10.0.20348 N/A Build 20348
</syntaxhighlight>

Check if the disks are mounted correctly:
<syntaxhighlight lang="powershell">
Get-Disk
</syntaxhighlight>
<syntaxhighlight lang="powershell">
Number Friendly Name Serial Number HealthStatus OperationalStatus Total Size Partition Style ------ ------------- ------------- ------------ ----------------- ---------- ---------- 0
Red Hat Vi... 1f4afc6e-be44-4c29-b Healthy Online 20 GB MBR
</syntaxhighlight>

Check if you selected the correct flavour:
<syntaxhighlight lang="powershell">
(Get-CimInstance Win32_PhysicalMemory | Measure-Object -Property capacity -Sum).sum /1gb
(Get-CimInstance Win32_ComputerSystem).NumberOfLogicalProcessors
</syntaxhighlight>
<syntaxhighlight lang="powershell">
4
1
</syntaxhighlight>

|-|VM creation Dashboard=

= Login via Dashboard =
Log in to the stoney cloud [https://dashboard.stoney-cloud.com/dashboard dashboard] with the credentials you have received from us.

[[File:Debian VM Creation Dashboard manual 01.png|600px]]

= Launch Instance - Preperations =
1. Select the appropriate project from the drop down menu at the top left.

3. On the <code>Project</code> tab, open the <code>Compute tab</code> and click <code>Instances</code> category.

4. Click <code>Launch Instance</code>.

[[File:Windows VM Creation Dashboard manual 02.png|600px]]

5. A dialog box opens. Specify the values as follows:
* '''Instance Name''': Assign a name to the virtual machine.
* Click <code>Source</code> tab and chose '''Image''' in '''Select Boot Source'''.
* Type '''Windows''' in the search bar below and allocate the image 'Windows Server 2019 Standard' from the image list by clicking the arrow pointing up.
[[File:Windows Creation Dashboard manual 03.png|600px]]

* Click <code>Flavour</code> tab and allocate the desired Flavour (For example: Standard Düdingen c001m0002) from the list below by clicking the arrow pointing up.
[[File:Windows Creation Dashboard manual 04.png|600px]]

* Click <code>Networks</code> and allocate the network '''internal''' from the list below by clicking the arrow pointing up.
[[File:Windows Creation Dashboard manual 05.png|600px]]

* Click <code>Security Groups</code> and allocate the security group '''RDP World''' from the list below by clicking the arrow pointing up.
[[File:Windows Creation Dashboard manual 06.png|600px]]

Click<code>Launch Instance</code> to create the VM. After no more than a minute the VM is created and listed in the <code>Instances</code> page.
'''Bild einfügen'''

= VM Login =

Log in to the stoney cloud [https://dashboard.stoney-cloud.com/dashboard dashboard] with the credentials you have received from us.

[[File:Debian VM Creation Dashboard manual 01.png|600px]]

1. Select the appropriate project from the drop down menu at the top left.

2. On the <code>Project</code> tab, open the <code>Compute tab</code> and click <code>Instances</code> category.

[[File:Introduction_to_the_Dashboard_02.png|600px]]

3. Click on the instance name of your VM

[[File:Introduction_to_the_Dashboard_03.png|600px]]

Enter the <code>console</code> tab and set a new administrator password.

Finally, you can connect to your newly created VM by using xfreerdp:

<syntaxhighlight lang='bash'>
password=''
xfreerdp --ignore-certificate --plugin cliprdr -g 1440x900 -u Administrator@PROD-RMA -p $password 127.0.0.1
</syntaxhighlight>
*via RDP (not yet documented)
</tabber>

[[Category: CLI]]
[[Category: Dashboard]]
[[Category: Instances]]

File:Windows VM Creation Dashboard manual 02.png

2024-07-15T12:55:10Z

Sst-ska: Sst-ska uploaded a new version of File:Windows VM Creation Dashboard manual 02.png

File:Introduction to the Dashboard 02.png

2024-07-15T12:53:51Z

Sst-ska: Sst-ska uploaded a new version of File:Introduction to the Dashboard 02.png

File:Ubuntu VM Creation Dashboard manual 02.png

2024-07-15T12:51:20Z

Sst-ska: Sst-ska uploaded a new version of File:Ubuntu VM Creation Dashboard manual 02.png

Ubuntu_VM_Creation_Dashboard_manual_02.png

File:Ubuntu VM Creation Dashboard manual 02.png

2024-07-15T12:50:33Z

Sst-ska: Sst-ska uploaded a new version of File:Ubuntu VM Creation Dashboard manual 02.png

Ubuntu_VM_Creation_Dashboard_manual_02.png

File:Ubuntu VM Creation Dashboard manual 01.png

2024-07-15T12:48:36Z

Sst-ska: Sst-ska uploaded a new version of File:Ubuntu VM Creation Dashboard manual 01.png

Ubuntu_VM_Creation_Dashboard_manual_01.png

File:Debian VM Creation Dashboard manual 02.png

2024-07-15T12:47:41Z

Sst-ska: Sst-ska uploaded a new version of File:Debian VM Creation Dashboard manual 02.png

Debian VM Creation Dashboard manual 02.png

File:OpenStack RC File v3.png

2024-07-15T12:45:47Z

Sst-ska: Sst-ska uploaded a new version of File:OpenStack RC File v3.png

File:Password Change 1.png

2024-07-15T12:44:36Z

Sst-ska: Sst-ska uploaded a new version of File:Password Change 1.png

File:Password Change 1.png

2024-07-15T12:35:37Z

Sst-ska:

File:Password Change 2.png

2024-07-15T12:34:36Z

Sst-ska: Sst-ska uploaded a new version of File:Password Change 2.png

File:Password Change 3.png

2024-07-15T12:29:22Z

Sst-ska:

File:Password Change 2.png

2024-07-15T12:29:14Z

Sst-ska: