From a2db2afc76f9ce44aaf27a82a7478b7fdbfda7ab Mon Sep 17 00:00:00 2001 From: epauwels Date: Fri, 25 Nov 2022 14:56:59 +0100 Subject: [PATCH 1/6] Rewrite of instance/flavours chapter In line with changes to the request form --- intro-Cloud/ch_Flavors.tex | 49 ++++++++++++++++++-------------------- 1 file changed, 23 insertions(+), 26 deletions(-) diff --git a/intro-Cloud/ch_Flavors.tex b/intro-Cloud/ch_Flavors.tex index 65e334c4c94..1f3eba25a9d 100644 --- a/intro-Cloud/ch_Flavors.tex +++ b/intro-Cloud/ch_Flavors.tex @@ -3,11 +3,11 @@ \chapter{Instance types and flavors} VSC Tier1 Cloud provides several virtual machine instance types and flavors to fit different use cases. Each instance type provides several flavor sizes to give different -combinations of CPU, memory, GPU and network resource. +combinations of CPU, memory, GPU and network resources. \section{Instance Types}\label{sec:instance-types} The following table provides the current main instance types available -from VSC Tier1 Cloud infrastructure: +from the VSC Tier1 Cloud infrastructure: \begin{table}[h!] \centering @@ -30,7 +30,7 @@ \section{Instance Types}\label{sec:instance-types} \begin{itemize} \item AMD Epyc 7542 2.9GHz \item 25Gbit Ethernet - \item NVIDIA Tesla 4 GPU + \item 1 vGPU NVIDIA Tesla 4 \end{itemize} \\ \hline @@ -39,21 +39,23 @@ \section{Instance Types}\label{sec:instance-types} \label{table:instance-type} \end{table} -Each instance type is appropriate for different workloads. From regular -CPU usage (\strong{CPUv}\emph{} instance types), to high performance -GPU computations (\strong{GPUv}\emph{}) or VMs connected to -uninterruptible power supplies (\strong{UPSv}\emph{}). VMs using UPS -flavor types will be keep up and running even if the data centre suffers +Each instance type is appropriate for different workloads: +(\strong{CPUv1}) for regular CPU usage, +(\strong{GPUv1}) for GPU computations, +or (\strong{UPSv1}) for VMs that need to be connected to an uninterruptible power supply. +VMs using UPS will keep up and running even if the datacenter suffers an unexpected power cut. +(\strong{CPUv1}) and (\strong{GPUv1}) virtual machines are not supported by an UPS and will go offline when an unexpected power cut occurs. VSC Tier-1 Cloud instance types also provide different kind of network performance specifications. All the instance types are able to connect to the available networks: public network, VSC network and shared filesystem -network (NFS). VSC and shared file system networks are only available -by project's request. +network (NFS). Note that VSC and shared file system network access is only made available +if explicitly requested in the project application. -VSC network gives an optimal path towards other VSC sites (ideal for high -perfomance connections between different clusters and services within VSC). +VSC network gives an optimal path towards other VSC sites. This is ideal for high +performance connections between different clusters and services within VSC. +E.g. when you intend to do high data volume reshuffling between VMs and other Tier-1 components. \strong{Note:} Cloud projects should request VSC network if they want to connect to VSC Data component (\url{https://www.vscentrum.be/data}) with iRODS @@ -65,24 +67,24 @@ \section{Instance Types}\label{sec:instance-types} \section{Flavor Sizes}\label{sec:flavor-sizes} -A flavor size is a set of virtualized hardware resouces to a virtual -machine (VM) instance like system memory size, virtual CPU (vCPU) +A flavor size is a set of virtualized hardware resources to a virtual +machine (VM) instance like system memory size (RAM), virtual cores (vCPUs) or the root filesystem size. -The flavor's root size is the amount of disk space +The flavor's root disk size is the amount of disk space used by the root (\emph{/}) partition, an ephemeral disk that the base image is copied into (see section \ref{launch-an-instance} for more information about VM persistent/non-persistent instances). The flavor's root ephemeral storage is only used when booting from -a non-persistent VM but not from a persistent storage volume or +a non-persistent VM, but is not used when booting from a persistent storage volume or persistent VM. The flavor's root ephemeral size is not taken into account to calculate the project's local storage quota either. You can also create a persistent volume and choose the desired filesystem size for your persistent VM during the instantiation. VM persistent volumes could be resized later if that is necessary -(see next chapter \ref{cha:launch-manage-inst} for more information). +(see chapter \ref{cha:launch-manage-inst} for more information). VSC Tier-1 Cloud VM flavors are grouped by instance types (see table \ref{table:instance-type}). The current flavor sizes are @@ -118,17 +120,12 @@ \section{Flavor Sizes}\label{sec:flavor-sizes} \label{table:flavor-size} \end{table} -The current VSC Tier-1 Cloud flavors list is available from section \ref{sec:appendix-flavors}. +The current full VSC Tier-1 Cloud flavors list is available from section \ref{sec:appendix-flavors}. -E.g. \strong{GPUv1}.\emph{large} OpenStack flavor will instantiate a -VM with 4 AMD Epyc 7542 2.9GHz CPUs, with a NVIDIA Tesla 4 GPU, 8GB -of ram, 40Gb of root disk and connected to the UPS. +E.g. The \strong{GPUv1}.\emph{large} OpenStack flavor will instantiate a +VM with 4 AMD Epyc 7542 2.9GHz vCPUs, with 1 NVIDIA Tesla 4 vGPUs, 8GB +of RAM, and a 40GB root disk. -\strong{Note:} New Tier-1 VSC Cloud projects should take into account -these flavor sizes in order to request their required resources and quota. -For instance, a new project needs 2 VMs with \emph{xlarge} flavor, -in that case the project should request 32Gb of ram and 16 Cores in total -to deploy their infrastructure. %%% Local Variables: %%% mode: latex From 7f82799bf332ed64baef9cec5d2706a87a210914 Mon Sep 17 00:00:00 2001 From: epauwels Date: Fri, 25 Nov 2022 15:22:57 +0100 Subject: [PATCH 2/6] Included table from section 11.1 in document Don't forget to remove section 11.1 then --- intro-Cloud/ch_Flavors.tex | 45 ++++++++++++++++++++++++++++---------- 1 file changed, 33 insertions(+), 12 deletions(-) diff --git a/intro-Cloud/ch_Flavors.tex b/intro-Cloud/ch_Flavors.tex index 1f3eba25a9d..5957964b891 100644 --- a/intro-Cloud/ch_Flavors.tex +++ b/intro-Cloud/ch_Flavors.tex @@ -93,34 +93,55 @@ \section{Flavor Sizes}\label{sec:flavor-sizes} \begin{table}[h!] \centering -\begin{tabular}{ |p{3cm}|p{3cm}|p{3cm}|p{3cm}| } +\begin{tabular}{ |p{3cm}|p{3cm}|p{3cm}|p{3cm}|p{3cm}| } \hline - \rowcolor{lightgray} \textbf{Flavor Size} & \textbf{RAM} & \textbf{Root Disk} & \textbf{vCPUs} \\ + \rowcolor{lightgray} \textbf{Flavor name} & \textbf{RAM} & \textbf{Root Disk} & \textbf{# vCPUs} & \textbf{# vGPUs} \\ \hline - small & 2Gb & 20Gb & 1 \\ + CPUv1.nano & 64Kb & 1Gb & 1 & 0 \\ \hline - medium & 4Gb & 30Gb & 2 \\ + CPUv1.tiny & 512Kb & 10Gb & 1 & 0 \\ \hline - large & 8Gb & 40Gb & 4 \\ + CPUv1.small & 2Gb & 20Gb & 1 & 0 \\ \hline - xlarge & 16Gb & 40Gb & 8 \\ + CPUv1.medium & 4Gb & 30Gb & 2 & 0 \\ \hline - 1\_2xlarge & 62Gb & 40Gb & 8 \\ + CPUv1.large & 8Gb & 40Gb & 4 & 0 \\ \hline - 2xlarge & 62Gb & 40Gb & 16 \\ + CPUv1.xlarge & 16Gb & 40Gb & 8 & 0 \\ \hline - 1\_3xlarge & 180Gb & 80Gb & 14 \\ + CPUv1.1_2xlarge & 60Gb & 40Gb & 8 & 0 \\ \hline - 3xlarge & 120Gb & 80Gb & 16 \\ + CPUv1.2xlarge & 60Gb & 40Gb & 16 & 0 \\ \hline - 4xlarge & 360Gb & 80Gb & 20 \\ + CPUv1.1_3xlarge & 180Gb & 80Gb & 14 & 0 \\ + \hline + CPUv1.3xlarge & 120Gb & 80Gb & 16 & 0 \\ + \hline + CPUv1.4xlarge & 360Gb & 80Gb & 20 & 0 \\ + \hline + UPSv1.small & 2Gb & 20Gb & 1 & 0 \\ + \hline + UPSv1.medium & 4Gb & 30Gb & 2 & 0 \\ + \hline + UPSv1.large & 8Gb & 40Gb & 4 & 0 \\ + \hline + UPSv1.2xlarge & 60Gb & 40Gb & 16 & 0 \\ + \hline + UPSv1.3xlarge & 120Gb & 80Gb & 16 & 0 \\ + \hline + GPUv1.small & 2Gb & 20Gb & 1 & 1 \\ + \hline + GPUv1.medium & 4Gb & 30Gb & 2 & 1 \\ + \hline + GPUv1.large & 8Gb & 40Gb & 4 & 1 \\ + \hline + GPUv1.2xlarge & 60Gb & 40Gb & 16 & 1 \\ \hline \end{tabular} \caption{Flavor sizes} \label{table:flavor-size} \end{table} -The current full VSC Tier-1 Cloud flavors list is available from section \ref{sec:appendix-flavors}. E.g. The \strong{GPUv1}.\emph{large} OpenStack flavor will instantiate a VM with 4 AMD Epyc 7542 2.9GHz vCPUs, with 1 NVIDIA Tesla 4 vGPUs, 8GB From f914da5056cf45de5aad30263cc2bac62e7f49d0 Mon Sep 17 00:00:00 2001 From: epauwels Date: Fri, 25 Nov 2022 15:39:13 +0100 Subject: [PATCH 3/6] Adjusted hash character in table --- intro-Cloud/ch_Flavors.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/intro-Cloud/ch_Flavors.tex b/intro-Cloud/ch_Flavors.tex index 5957964b891..43433da8e2e 100644 --- a/intro-Cloud/ch_Flavors.tex +++ b/intro-Cloud/ch_Flavors.tex @@ -95,7 +95,7 @@ \section{Flavor Sizes}\label{sec:flavor-sizes} \centering \begin{tabular}{ |p{3cm}|p{3cm}|p{3cm}|p{3cm}|p{3cm}| } \hline - \rowcolor{lightgray} \textbf{Flavor name} & \textbf{RAM} & \textbf{Root Disk} & \textbf{# vCPUs} & \textbf{# vGPUs} \\ + \rowcolor{lightgray} \textbf{Flavor name} & \textbf{RAM} & \textbf{Root Disk} & \textbf{\# vCPUs} & \textbf{\# vGPUs} \\ \hline CPUv1.nano & 64Kb & 1Gb & 1 & 0 \\ \hline From 3b54425d7dca81c73169012d4d7271a146704556 Mon Sep 17 00:00:00 2001 From: epauwels Date: Fri, 25 Nov 2022 15:56:48 +0100 Subject: [PATCH 4/6] Removed hash altogether now + fix example at end --- intro-Cloud/ch_Flavors.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/intro-Cloud/ch_Flavors.tex b/intro-Cloud/ch_Flavors.tex index 43433da8e2e..cc1acdaa3bc 100644 --- a/intro-Cloud/ch_Flavors.tex +++ b/intro-Cloud/ch_Flavors.tex @@ -95,7 +95,7 @@ \section{Flavor Sizes}\label{sec:flavor-sizes} \centering \begin{tabular}{ |p{3cm}|p{3cm}|p{3cm}|p{3cm}|p{3cm}| } \hline - \rowcolor{lightgray} \textbf{Flavor name} & \textbf{RAM} & \textbf{Root Disk} & \textbf{\# vCPUs} & \textbf{\# vGPUs} \\ + \rowcolor{lightgray} \textbf{Flavor name} & \textbf{RAM} & \textbf{Root Disk} & \textbf{vCPUs} & \textbf{vGPUs} \\ \hline CPUv1.nano & 64Kb & 1Gb & 1 & 0 \\ \hline @@ -144,7 +144,7 @@ \section{Flavor Sizes}\label{sec:flavor-sizes} E.g. The \strong{GPUv1}.\emph{large} OpenStack flavor will instantiate a -VM with 4 AMD Epyc 7542 2.9GHz vCPUs, with 1 NVIDIA Tesla 4 vGPUs, 8GB +VM with 4 AMD Epyc 7542 2.9GHz vCPUs, with 1 NVIDIA Tesla4 vGPU, 8GB of RAM, and a 40GB root disk. From 8e3ee6ad4f1abed24897c7bc0e9e76b4560f4c65 Mon Sep 17 00:00:00 2001 From: epauwels Date: Wed, 7 Dec 2022 13:21:28 +0100 Subject: [PATCH 5/6] Escaping underscores --- intro-Cloud/ch_Flavors.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/intro-Cloud/ch_Flavors.tex b/intro-Cloud/ch_Flavors.tex index cc1acdaa3bc..4e9f20be96b 100644 --- a/intro-Cloud/ch_Flavors.tex +++ b/intro-Cloud/ch_Flavors.tex @@ -109,11 +109,11 @@ \section{Flavor Sizes}\label{sec:flavor-sizes} \hline CPUv1.xlarge & 16Gb & 40Gb & 8 & 0 \\ \hline - CPUv1.1_2xlarge & 60Gb & 40Gb & 8 & 0 \\ + CPUv1.1\_2xlarge & 60Gb & 40Gb & 8 & 0 \\ \hline CPUv1.2xlarge & 60Gb & 40Gb & 16 & 0 \\ \hline - CPUv1.1_3xlarge & 180Gb & 80Gb & 14 & 0 \\ + CPUv1.1\_3xlarge & 180Gb & 80Gb & 14 & 0 \\ \hline CPUv1.3xlarge & 120Gb & 80Gb & 16 & 0 \\ \hline From 76f6c69d0d26c164ecf0503b843e8dc2ed76122d Mon Sep 17 00:00:00 2001 From: epauwels Date: Wed, 7 Dec 2022 13:40:31 +0100 Subject: [PATCH 6/6] Adjusted table and reference --- intro-Cloud/ch_Flavors.tex | 50 ++++++++++++++++++++------------------ 1 file changed, 26 insertions(+), 24 deletions(-) diff --git a/intro-Cloud/ch_Flavors.tex b/intro-Cloud/ch_Flavors.tex index 4e9f20be96b..3ce796aa9d6 100644 --- a/intro-Cloud/ch_Flavors.tex +++ b/intro-Cloud/ch_Flavors.tex @@ -87,55 +87,57 @@ \section{Flavor Sizes}\label{sec:flavor-sizes} (see chapter \ref{cha:launch-manage-inst} for more information). VSC Tier-1 Cloud VM flavors are grouped by instance types -(see table \ref{table:instance-type}). The current flavor sizes are -available for each instance type and can be used in different +(see table \ref{table:flavor-size}). Several flavor sizes are +available for each instance type, differing in the number of allocated vCPUs, +RAM and storage size. Every GPU flavor in addition allocates one vGPU. +The various VM flavors can be used in different combinations to fit different workload hardware requirements. \begin{table}[h!] \centering -\begin{tabular}{ |p{3cm}|p{3cm}|p{3cm}|p{3cm}|p{3cm}| } +\begin{tabular}{ |p{3cm}|p{3cm}|p{3cm}|p{3cm}| } \hline - \rowcolor{lightgray} \textbf{Flavor name} & \textbf{RAM} & \textbf{Root Disk} & \textbf{vCPUs} & \textbf{vGPUs} \\ + \rowcolor{lightgray} \textbf{Flavor name} & \textbf{RAM} & \textbf{Root Disk} & \textbf{vCPUs} \\ \hline - CPUv1.nano & 64Kb & 1Gb & 1 & 0 \\ + CPUv1.nano & 64Kb & 1Gb & 1 \\ \hline - CPUv1.tiny & 512Kb & 10Gb & 1 & 0 \\ + CPUv1.tiny & 512Kb & 10Gb & 1 \\ \hline - CPUv1.small & 2Gb & 20Gb & 1 & 0 \\ + CPUv1.small & 2Gb & 20Gb & 1 \\ \hline - CPUv1.medium & 4Gb & 30Gb & 2 & 0 \\ + CPUv1.medium & 4Gb & 30Gb & 2 \\ \hline - CPUv1.large & 8Gb & 40Gb & 4 & 0 \\ + CPUv1.large & 8Gb & 40Gb & 4 \\ \hline - CPUv1.xlarge & 16Gb & 40Gb & 8 & 0 \\ + CPUv1.xlarge & 16Gb & 40Gb & 8 \\ \hline - CPUv1.1\_2xlarge & 60Gb & 40Gb & 8 & 0 \\ + CPUv1.1\_2xlarge & 60Gb & 40Gb & 8 \\ \hline - CPUv1.2xlarge & 60Gb & 40Gb & 16 & 0 \\ + CPUv1.2xlarge & 60Gb & 40Gb & 16 \\ \hline - CPUv1.1\_3xlarge & 180Gb & 80Gb & 14 & 0 \\ + CPUv1.1\_3xlarge & 180Gb & 80Gb & 14 \\ \hline - CPUv1.3xlarge & 120Gb & 80Gb & 16 & 0 \\ + CPUv1.3xlarge & 120Gb & 80Gb & 16 \\ \hline - CPUv1.4xlarge & 360Gb & 80Gb & 20 & 0 \\ + CPUv1.4xlarge & 360Gb & 80Gb & 20 \\ \hline - UPSv1.small & 2Gb & 20Gb & 1 & 0 \\ + UPSv1.small & 2Gb & 20Gb & 1 \\ \hline - UPSv1.medium & 4Gb & 30Gb & 2 & 0 \\ + UPSv1.medium & 4Gb & 30Gb & 2 \\ \hline - UPSv1.large & 8Gb & 40Gb & 4 & 0 \\ + UPSv1.large & 8Gb & 40Gb & 4 \\ \hline - UPSv1.2xlarge & 60Gb & 40Gb & 16 & 0 \\ + UPSv1.2xlarge & 60Gb & 40Gb & 16 \\ \hline - UPSv1.3xlarge & 120Gb & 80Gb & 16 & 0 \\ + UPSv1.3xlarge & 120Gb & 80Gb & 16 \\ \hline - GPUv1.small & 2Gb & 20Gb & 1 & 1 \\ + GPUv1.small & 2Gb & 20Gb & 1 \\ \hline - GPUv1.medium & 4Gb & 30Gb & 2 & 1 \\ + GPUv1.medium & 4Gb & 30Gb & 2 \\ \hline - GPUv1.large & 8Gb & 40Gb & 4 & 1 \\ + GPUv1.large & 8Gb & 40Gb & 4 \\ \hline - GPUv1.2xlarge & 60Gb & 40Gb & 16 & 1 \\ + GPUv1.2xlarge & 60Gb & 40Gb & 16 \\ \hline \end{tabular} \caption{Flavor sizes}