From: cel@kernel.org
To: <kdevops@lists.linux.dev>
Cc: Chandan Babu R <chandanbabu@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>
Subject: [RFC PATCH 31/31] terraform/OCI: Update the OCI section of docs/kdevops-terraform.md
Date: Mon, 31 Mar 2025 21:00:00 -0400 [thread overview]
Message-ID: <20250401010000.764234-32-cel@kernel.org> (raw)
In-Reply-To: <20250401010000.764234-1-cel@kernel.org>
From: Chuck Lever <chuck.lever@oracle.com>
Update documentation URLs, focus on the basics.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
docs/kdevops-terraform.md | 117 ++++++++++++--------------------------
1 file changed, 35 insertions(+), 82 deletions(-)
diff --git a/docs/kdevops-terraform.md b/docs/kdevops-terraform.md
index 5e5107fef73e..34ac1a19eff1 100644
--- a/docs/kdevops-terraform.md
+++ b/docs/kdevops-terraform.md
@@ -298,86 +298,39 @@ https://www.terraform.io/docs/providers/google/index.html
https://cloud.google.com/iam/docs/granting-roles-to-service-accounts#granting_access_to_a_service_account_for_a_resource
### OCI - Oracle Cloud Infrastructure
-OCI documentation is located at
-1. https://docs.oracle.com/en-us/iaas/Content/home.htm
-2. https://docs.oracle.com/en-us/iaas/Content/API/SDKDocs/terraform.htm
-The following is a list of OCI specific configuration variables that the user
-needs to provide values (through `make menuconfig` interface).
- 1. `CONFIG_TERRAFORM_SSH_CONFIG_USER`
- - User name used for the logging into the cloud instance.
- - Please use,
- - `opc` for Oracle Linux.
- - `ubuntu` for Ubuntu Linux
- 2. `CONFIG_TERRAFORM_SSH_CONFIG_PUBKEY_FILE`
- - Path to user's ssh public key (e.g. `~/.ssh/id_rsa.pub`).
- - This key will be copied over to the cloud instance during its
- creation.
- 3. `CONFIG_TERRAFORM_OCI_REGION`
- - String representing the name of the region (e.g. `us-ashburn-1`).
- - https://docs.oracle.com/en-us/iaas/Content/anomaly/using/regions.htm
- - List of the regions can be found at
- https://docs.oracle.com/en-us/iaas/Content/General/Concepts/regions.htm
- 4. `CONFIG_TERRAFORM_OCI_TENANCY_OCID`
- - OCID of the tenancy being used.
- - In order to obtain the OCID, Please refer to
- https://docs.oracle.com/en-us/iaas/Content/GSG/Tasks/contactingsupport_topic-Finding_Your_Tenancy_OCID_Oracle_Cloud_Identifier.htm
- 5. `CONFIG_TERRAFORM_OCI_USER_OCID`
- - OCID of the user.
- - In order to obtain the OCID, Please refer to
- https://docs.oracle.com/en-us/iaas/Content/API/Concepts/apisigningkey.htm#five
- 6. `CONFIG_TERRAFORM_OCI_USER_PRIVATE_KEY_PATH`
- - Path to API private key.
- - Documentation
- - Generating API keys.
- Refer to section `Generating an API Signing Key (Linux and Mac OS X)`
- at
- https://docs.oracle.com/en-us/iaas/Content/API/Concepts/apisigningkey.htm
- - Uploading Public API key.
- Refer to section `How to Upload the Public Key` at
- https://docs.oracle.com/en-us/iaas/Content/API/Concepts/apisigningkey.htm
- - Video: https://www.youtube.com/watch?v=LMvYOSkXF1k
- 7. `CONFIG_TERRAFORM_OCI_USER_FINGERPRINT`
- - Finger print of the API key.
- 8. `CONFIG_TERRAFORM_OCI_AVAILABLITY_DOMAIN` ="VkEH:US-ASHBURN-AD-3"
- - String specifying the availability domain to use in the region
- - Availability domain names can be obtained from the web page used to
- launch an cloud instance.
- 9. `CONFIG_TERRAFORM_OCI_COMPARTMENT_OCID`
- - OCID of the compartment can be obtained by following the instructions
- at
- https://docs.oracle.com/en-us/iaas/Content/GSG/Tasks/contactingsupport_topic-Finding_the_OCID_of_a_Compartment.htm
- 10. `CONFIG_TERRAFORM_OCI_SHAPE`="VM.Standard.E2.8"
- - String representing the name of the compute shape to create.
- - https://docs.oracle.com/en-us/iaas/Content/Compute/References/computeshapes.htm
- 11. `CONFIG_TERRAFORM_OCI_OS_IMAGE_OCID`
- - OCID of the OS image to be installed.
- - Image's OCID can be obtained by following instructions at
- https://docs.oracle.com/en-us/iaas/Content/API/SDKDocs/terraformbestpractices_topic-Referencing_Images.htm
- 12. `CONFIG_TERRAFORM_OCI_SUBNET_OCID`
- - OCID of the subnet to be assigned to the cloud instance.
- - Overview:
- https://docs.oracle.com/en-us/iaas/Content/Network/Tasks/Overview_of_VCNs_and_Subnets.htm
- - Instructions on how to get a list of available subnets can be found at
- https://docs.oracle.com/en-us/iaas/Content/Network/Tasks/get-subnet.htm
- - Click on the hamburger menu provided the right side of a subnet entry
- and select `Copy OCID`.
- 13. `CONFIG_TERRAFORM_OCI_DATA_VOLUME_DISPLAY_NAME`
- - String representing the name for the `data` disk.
- - This is used for storing sources and binaries corresponding to Linux
- kernel, Fstests & Kdevops.
- 14. `CONFIG_TERRAFORM_OCI_DATA_VOLUME_DEVICE_FILE_NAME`
- - Device node to be used for `data` disk.
- - Please specify `/dev/oracleoci/oraclevdb` as the device file.
- 15. `CONFIG_TERRAFORM_OCI_SPARSE_VOLUME_DISPLAY_NAME`
- - String representing the name for the `sparse` disk.
- - This is used for creating regular files to back loop devices.
- 16. `CONFIG_TERRAFORM_OCI_SPARSE_VOLUME_DEVICE_FILE_NAME`
- - Device node to be used for `sparse` disk.
- - Please specify `/dev/oracleoci/oraclevdc` as the device file.
- 17. `CONFIG_TERRAFORM_OCI_INSTANCE_FLEX_OCPUS`
- - Number of OCPUs for a flexiable compute shape.
- - https://docs.oracle.com/en-us/iaas/Content/Compute/References/computeshapes.htm#flexible
- 18. `CONFIG_TERRAFORM_OCI_INSTANCE_FLEX_MEMORY_IN_GBS`
- - Amount of RAM in GB for a flexiable compute shape.
- - https://docs.oracle.com/en-us/iaas/Content/Compute/References/computeshapes.htm#flexible
+kdevops supports using the OCI Public Cloud (OCI).
+
+#### New To OCI?
+
+You can find a generic tutorial guide at the following link. You'll
+need many (but not all) of these steps to bring up kdevops with OCI.
+
+https://docs.oracle.com/en-us/iaas/Content/dev/terraform/tutorials/tf-provider.htm
+
+This explains what an "OCID" is:
+
+https://docs.oracle.com/en-us/iaas/Content/General/Concepts/identifiers.htm
+
+#### Quick Start
+
+To authenticate to the Oracle cloud, kdevops uses the API Key
+authentication method, described here:
+
+ https://docs.oracle.com/en-us/iaas/Content/API/Concepts/apisigningkey.htm
+
+Copy these items into the Kconfig settings under the "Identity &
+Access" submenu. Additional guidance is available in the Kconfig
+help text in this menu.
+
+OCI pre-configures an admin ssh user on each instance. Under the
+CONFIG_TERRAFORM_SSH_CONFIG_USER option, you need to explicitly set
+kconfig's ssh login name depending on which OS image you have
+selected:
+
+ - `opc` for Oracle Linux.
+ - `ubuntu` for Ubuntu Linux
+
+If your Ansible controller (where you run "make bringup") and your
+test instances operate inside the same subnet, you can disable the
+TERRAFORM_OCI_ASSIGN_PUBLIC_IP option for better network security.
--
2.48.1
next prev parent reply other threads:[~2025-04-01 1:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 0:59 [RFC PATCH 00/31] Simplify OCI configuration menu cel
2025-04-01 0:59 ` [RFC PATCH 01/31] terraform/OCI: Remove terraform_oci_instance_display_name cel
2025-04-01 0:59 ` [RFC PATCH 02/31] terraform/OCI: One default value to rule them cel
2025-04-01 0:59 ` [RFC PATCH 03/31] terraform/OCI: Add an "Identity & Access" submenu cel
2025-04-01 0:59 ` [RFC PATCH 04/31] terraform/OCI: Add a "Resource location" submenu cel
2025-04-01 0:59 ` [RFC PATCH 05/31] terraform/OCI: Add a "Compute" Kconfig submenu cel
2025-04-01 0:59 ` [RFC PATCH 06/31] terraform/OCI: Add a "Storage" " cel
2025-04-01 0:59 ` [RFC PATCH 07/31] terraform/OCI: Add a "Networking" " cel
2025-04-01 0:59 ` [RFC PATCH 08/31] terraform/OCI: Use "output yaml" for the tenancy OCID cel
2025-04-01 0:59 ` [RFC PATCH 09/31] terraform/OCI: Use "output yaml" for the user OCID cel
2025-04-01 0:59 ` [RFC PATCH 10/31] terraform/OCI: Use "output yaml" for the signing key cel
2025-04-01 0:59 ` [RFC PATCH 11/31] terraform/OCI: Use "output yaml" for the fingerprint cel
2025-04-01 0:59 ` [RFC PATCH 12/31] terraform/OCI: Add a Region selector cel
2025-04-01 0:59 ` [RFC PATCH 13/31] terraform/OCI: Add an availability domain selector cel
2025-04-01 0:59 ` [RFC PATCH 14/31] terraform/OCI: Select your compartment by name instead of by OCID cel
2025-04-01 0:59 ` [RFC PATCH 15/31] terraform/OCI: Use "output yaml" for the instance shape setting cel
2025-04-01 0:59 ` [RFC PATCH 16/31] terraform/OCI: Add a shape selector for Flex shapes cel
2025-04-01 0:59 ` [RFC PATCH 17/31] terraform/OCI: Use "output yaml" for the OCPUs setting cel
2025-04-01 0:59 ` [RFC PATCH 18/31] terraform/OCI: Use "output yaml" for the memory_in_gbs setting cel
2025-04-01 0:59 ` [RFC PATCH 19/31] terraform/OCI: Add a shape family selector cel
2025-04-01 0:59 ` [RFC PATCH 20/31] terraform/OCI: Add a bare metal shape selector cel
2025-04-01 0:59 ` [RFC PATCH 21/31] terraform/OCI: Use "output yaml" for the source image setting cel
2025-04-01 0:59 ` [RFC PATCH 22/31] terraform/OCI: Simplify image selection cel
2025-04-01 0:59 ` [RFC PATCH 23/31] terraform/OCI: Remove TERRAFORM_OCI_VOLUMES_ENABLE_EXTRA cel
2025-04-01 0:59 ` [RFC PATCH 24/31] terraform/OCI: Use "output yaml" for the assign_public_ip" setting cel
2025-04-01 0:59 ` [RFC PATCH 25/31] terraform/OCI: Use "output yaml" for the subnet_ocid setting cel
2025-04-01 0:59 ` [RFC PATCH 26/31] terraform/OCI: Add a default VCN cel
2025-04-01 0:59 ` [RFC PATCH 27/31] terraform/OCI: Add a Kconfig switch to create a VCN on the fly cel
2025-04-01 0:59 ` [RFC PATCH 28/31] terraform/OCI: Run "terraform fmt" on provider.tf cel
2025-04-01 0:59 ` [RFC PATCH 29/31] terraform/OCI: Run "terraform fmt" on main.tf cel
2025-04-01 0:59 ` [RFC PATCH 30/31] terraform/OCI: Nit: alphabetize vars.tf cel
2025-04-01 1:00 ` cel [this message]
2025-04-02 19:21 ` [RFC PATCH 00/31] Simplify OCI configuration menu Luis Chamberlain
2025-04-02 19:24 ` Luis Chamberlain
2025-04-02 19:38 ` Chuck Lever
2025-04-02 20:08 ` Luis Chamberlain
2025-04-08 12:42 ` Chandan Babu R
2025-04-08 13:20 ` Chuck Lever
2025-04-09 4:04 ` Chandan Babu R
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250401010000.764234-32-cel@kernel.org \
--to=cel@kernel.org \
--cc=chandanbabu@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=kdevops@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox