You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RELEASE-NOTES.md
+10Lines changed: 10 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,13 @@
1
+
# May 15, 2024 Release Notes - 0.1.4
2
+
3
+
## New
4
+
1. OKE module added, supporting basic and enhanced clusters, with managed node pools and virtual node pools. See [OKE module](./cis-oke/README.md) for details.
5
+
6
+
## Updates
7
+
1. Compute module can now manage cluster networks and compute clusters. See [Clusters](./cis-compute-storage/README.md#clusters-1) for details.
8
+
2. Compute module now supports cloud-init scripts passed in as a file or as a string in [Terraform heredoc style](https://developer.hashicorp.com/terraform/language/expressions/strings#heredoc-strings). See [Compute](./cis-compute-storage/README.md#compute-1) for details.
9
+
3. Compute module now supports SSH public keys passed in as a file or as a string.
error_message="VALIDATION FAILURE in cluster \"${each.key}\": \"cluster_network_settings\" is required for clusters of type \"${lower(coalesce(each.value.type,"cluster_network"))}\"."
This example shows how to deploy an RDMA cluster network in OCI using the [cis-compute-storage module](../../). It deploys one Compute instance, one cluster instance configuration, and one cluster network with the characteristics described below. Refer to [input.auto.tfvars.template](./input.auto.tfvars.template) for the variables configuration.
5
+
6
+
A [cluster network](https://docs.oracle.com/en-us/iaas/Content/Compute/Tasks/managingclusternetworks.htm) is a pool of high performance computing (HPC) instances that are connected with a high-bandwidth, ultra low-latency network. They're designed for highly demanding parallel computing jobs.
7
+
8
+
### Compute Instance
9
+
- The deployed Compute instance is used as a template for the cluster instance configuration.
10
+
- The Compute instance shape is "BM.Optimized3.36".
11
+
- The Compute instance is created in the compartment and subnet specified by *default_compartment_id* and *default_subnet_id* attributes, respectively, within *instances_configuration* variable.
12
+
13
+
Note that you must provide the image *name* and *publisher_name* for provisioning the Compute instance. Use the [marketplace-images module](../../../marketplace-images/) to obtain Marketplace images information based on a search filter. It will also return the image OCID that can be used instead of the image name/publisher pair.
14
+
15
+
### Cluster Instance Configuration
16
+
- A cluster instance configuration is created based on the Compute instance. This is indicated by *template_instance_id* attribute within *cluster_instances_configuration* variable.
17
+
- The cluster instance configuration is created in the compartment specified by *default_compartment_id* attribute within *cluster_instances_configuration* variable.
18
+
19
+
### Cluster Instance Pool
20
+
- A cluster instance pool is created based on the provided cluster instance configuration.
21
+
22
+
### RDMA Cluster Network
23
+
- An RDMA cluster network with one cluster instance pool of size 1.
24
+
- The cluster instance pool size is specified by *instance_pool size* attribute within *clusters_configuration* variable.
25
+
- The cluster network is created in the compartment specified by *default_compartment_id* attribute within *clusters_configuration* variable.
26
+
27
+
## Using this example
28
+
1. Rename *input.auto.tfvars.template* to *\<project-name\>.auto.tfvars*, where *\<project-name\>* is any name of your choice.
29
+
30
+
2. Within *\<project-name\>.auto.tfvars*, provide tenancy connectivity information and adjust the input variables, by making the appropriate substitutions:
31
+
- Replace \<REPLACE-WITH-\*\> placeholders with appropriate values.
32
+
33
+
Refer to [cis-compute-storage module README.md](../../README.md) for overall attributes usage.
34
+
35
+
3. In this folder, run the typical Terraform workflow:
tenancy_ocid = "<tenancy OCID>" # Get this from OCI Console (after logging in, go to top-right-most menu item and click option "Tenancy: <your tenancy name>").
15
+
user_ocid = "<user OCID>" # Get this from OCI Console (after logging in, go to top-right-most menu item and click option "My profile").
16
+
fingerprint = "<PEM key fingerprint>" # The fingerprint can be gathered from your user account. In the "My profile page, click "API keys" on the menu in left hand side.
17
+
private_key_path = "<path to the private key>" # This is the full path on your local system to the API signing private key.
18
+
private_key_password = "" # This is the password that protects the private key, if any.
19
+
region = "<your tenancy region>" # The region name.
20
+
21
+
#---------------------------------------
22
+
# Input variables
23
+
#---------------------------------------
24
+
25
+
# This variable defines the RDMA clusters configuration.
26
+
# The clusters attribute allows for the definition of an arbitrary number of clusters.
# This variable defines the instances configuration that clusters are built on.
49
+
# The configurations attribute allows for the definition of an arbitrary number of configurations.
50
+
# Each configuration must provide a template_instance_id attribute, which value must be the key of a Compute instance within the instances_configuration variable above.
0 commit comments