public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager] ui: RBDStorage: add field for RBD namespace
Date: Fri, 16 Apr 2021 17:39:27 +0200	[thread overview]
Message-ID: <70e563f9-660f-8e70-f366-a73e3c55837f@proxmox.com> (raw)
In-Reply-To: <90633710-e22f-66dc-2e77-9e8d6979a4ec@proxmox.com>

Thx for the feedback and yep, I forgot to run the linter...

On 4/16/21 4:56 PM, Thomas Lamprecht wrote:
> On 16.04.21 16:10, Aaron Lauterer wrote:
>> Makes it possible to configure the RBD namespace via the GUI.

[....]

>> +		xtype: 'displayfield',
>> +		name: 'namespace-hint',
>> +		userCls: 'pmx-hint',
>> +		value: gettext('RBD namespaces must be created manually!'),
>> +		bind: {
>> +		    hidden: '{!namespacePresent}',
>> +		},
> 
> Alternatively we could probe the rbd storage if the namespace is present on submit?
> 
> I.e., do the RADOS command equivalent to `rbd namespace list -p <pool` in the
> storage add/update hook if the namespace param is present?

Anything against doing it via `rbd -p pool namespace ls`? AFAICT there is no lightweight command to list namespaces via `rados`. Only thing I found was listing all objects in the pool and fetching used namespaces from that output: `rados -p rbd ls --format json` but that is an expensive operation.

One thing though that we should consider: so far adding an external RBD storage worked even if the auth keyring wasn't present. The storage would not get activated until the keyring file was present. But one could still do that after adding the storage config. With this check we would make it a requirement to first place the keyring file and then add the storage config.

> 
>>   	    },
>> -	    checked: true,
>> -	    uncheckedValue: 0,
>> -	    submitValue: false,
>> -	    hidden: !me.isCreate,
>> -	    boxLabel: gettext('Use Proxmox VE managed hyper-converged ceph pool'),
>> -	}];
>> +	];
>>   
>>   	me.callParent();
>>       },
>>
> 




  reply	other threads:[~2021-04-16 15:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 14:10 Aaron Lauterer
2021-04-16 14:56 ` Thomas Lamprecht
2021-04-16 15:39   ` Aaron Lauterer [this message]
2021-04-16 15:48     ` Thomas Lamprecht
2021-04-16 15:56       ` Aaron Lauterer

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=70e563f9-660f-8e70-f366-a73e3c55837f@proxmox.com \
    --to=a.lauterer@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.lamprecht@proxmox.com \
    /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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal