public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Chandan Babu R <chandanbabu@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
	cel@kernel.org, kdevops@lists.linux.dev
Subject: Re: [RFC PATCH 00/31] Simplify OCI configuration menu
Date: Wed, 09 Apr 2025 09:34:01 +0530	[thread overview]
Message-ID: <87friij7yw.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <cdb82282-b95b-4b2e-a772-4b5cbb765263@oracle.com>

On Tue, Apr 08, 2025 at 09:20:30 AM -0400, Chuck Lever wrote:
> On 4/8/25 8:42 AM, Chandan Babu R wrote:
>> On Wed, Apr 02, 2025 at 01:08:34 PM -0700, Luis Chamberlain wrote:
>>> On Wed, Apr 02, 2025 at 03:38:04PM -0400, Chuck Lever wrote:
>>>> On 4/2/25 3:21 PM, Luis Chamberlain wrote:
>>>>> On Mon, Mar 31, 2025 at 08:59:29PM -0400, cel@kernel.org wrote:
>>>>>> From: Chuck Lever <chuck.lever@oracle.com>
>>>>>> I've come up with some simplifications that can apply to all of
>>>>>> the providers, but I'd like to start with OCI because 
>>>>>
>>>>> Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
>>>>
>>>> Thanks for taking a look!
>>>>
>>>> I guess my basic concern here is that I'm changing the name of some
>>>> Kconfig variables, which would break backwards compatibility.
>>>
>>> I've addressed concerns like that befored by adding a respective kconfig
>>> value and mapping the old one to the new shiny one with an XXX to
>>> annotate we should remove the older one later. But if for cloud I
>>> suspect most users might stick to that version of kdevops and have no
>>> need to upgrade too, and so I am not sure if its needed as much as
>>> the guest / virtualization use case.
>>>
>>>> If you and Chandan feel that is not a roadblock, then I will start
>>>> committing these and the similar patches I have for the other three
>>>> major providers.
>>>
>>> My use cases of cloud are all completely ephemeral and stuck to one
>>> version of kdevops in particular because of the cost, and so I am
>>> careful to always 'make destroy' as soon as I'm done otheriwse you
>>> can economically bleed. And so I think economics drives kdevops
>>> cloud instances to be super ephemeral.
>>>
>>> So for *me*, I say go for it.
>>>
>>> But I am not sure if other folks are using kdevops for the cloud
>>> in other ways, but certainly Chandan would have good sensing on that.
>>>
>> 
>> The changes made by the patchset definitely improve the usability of OCI via
>> kdevops. Thanks for working on this.
>> 
>> Reviewed-by: Chandan Babu R <chandanbabu@kernel.org>
>
> Thanks for your review!
>
>
>> Also, Can you please include the VM.Standard.x86.Generic shape in the list of
>> shapes introduced by "[RFC PATCH 16/31] terraform/OCI: Add a shape selector
>> for Flex shapes" patch. This shape is recommended for developers from my
>> department who do not require a specific model of CPU for their work.
>
> Yes, I can do that. An alternative would be to retain the ability to
> enter an arbitrary string here (and maybe for image selection).

Yes, That would be very helpful. Thanks!

-- 
Chandan

      reply	other threads:[~2025-04-09  4:05 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 ` [RFC PATCH 31/31] terraform/OCI: Update the OCI section of docs/kdevops-terraform.md cel
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 [this message]

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=87friij7yw.fsf@debian-BULLSEYE-live-builder-AMD64 \
    --to=chandanbabu@kernel.org \
    --cc=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=kdevops@lists.linux.dev \
    --cc=mcgrof@kernel.org \
    /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