public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Lorenz Stechauner <l.stechauner@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH v2 container] fix #3421: allow custom storage plugins to support rootfs
Date: Mon, 17 May 2021 16:21:07 +0200	[thread overview]
Message-ID: <500231a8-ae07-3d96-9db3-62809ee3bf93@proxmox.com> (raw)
In-Reply-To: <310011e6-083d-e241-80cc-17024a77db31@proxmox.com>

On 5/17/21 3:41 PM, Thomas Lamprecht wrote:

> On 17.05.21 11:03, Lorenz Stechauner wrote:
>> it is now necessary for storages to support the 'rootdir' content
>> in order to create/start containers on them. all native storage
>> plugins already report the rootdir content correctly.
>>
>> Signed-off-by: Lorenz Stechauner <l.stechauner@proxmox.com>
>> ---
> I'm missing the description of changes from v1 -> v2 here...

Sorry, forgot to include. Changes v1 -> v2:

- Added a commit message which explains the need of content type 'rootdir'
- code style
- new behavior should now be the same as old behavior (regarding native 
storage plugins)
- updated error messages

>>   src/PVE/LXC.pm | 30 ++++++++++++------------------
>>   1 file changed, 12 insertions(+), 18 deletions(-)
>>
>> diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm
>> index 7e6f378..75e1c20 100644
>> --- a/src/PVE/LXC.pm
>> +++ b/src/PVE/LXC.pm
>> @@ -1682,15 +1682,16 @@ sub __mountpoint_mount {
>>   		}
>>   	    };
>>   	    my $use_loopdev = 0;
>> -	    if ($scfg->{path}) {
>> -		$mounted_dev = run_with_loopdev($domount, $path, $readonly);
>> -		$use_loopdev = 1;
>> -	    } elsif ($scfg->{type} eq 'drbd' || $scfg->{type} eq 'lvm' ||
>> -		     $scfg->{type} eq 'rbd' || $scfg->{type} eq 'lvmthin') {
>> -		$mounted_dev = $path;
>> -		&$domount($path);
>> +	    if ($scfg->{content}->{rootdir}) {
>> +		if ($scfg->{path}) {
>> +		    $mounted_dev = run_with_loopdev($domount, $path, $readonly);
>> +		    $use_loopdev = 1;
>> +		} else {
>> +		    $mounted_dev = $path;
>> +		    &$domount($path);
>> +		}
>>   	    } else {
>> -		die "unsupported storage type '$scfg->{type}'\n";
>> +		die "storage type '$scfg->{type}' does not support containers\n";
>>   	    }
>>   	    return wantarray ? ($path, $use_loopdev, $mounted_dev) : $path;
>>   	} else {
>> @@ -1871,7 +1872,7 @@ sub alloc_disk {
>>   
>>       eval {
>>   	my $do_format = 0;
>> -	if ($scfg->{type} eq 'dir' || $scfg->{type} eq 'nfs' || $scfg->{type} eq 'cifs' ) {
>> +	if ($scfg->{content}->{rootdir} && $scfg->{path}) {
>>   	    if ($size_kb > 0) {
>>   		$volid = PVE::Storage::vdisk_alloc($storecfg, $storage, $vmid, 'raw',
>>   						   undef, $size_kb);
>> @@ -1882,21 +1883,14 @@ sub alloc_disk {
>>   		$needs_chown = 1;
>>   	    }
>>   	} elsif ($scfg->{type} eq 'zfspool') {
>> -
>>   	    $volid = PVE::Storage::vdisk_alloc($storecfg, $storage, $vmid, 'subvol',
>>   					       undef, $size_kb);
>>   	    $needs_chown = 1;
>> -	} elsif ($scfg->{type} eq 'drbd' || $scfg->{type} eq 'lvm' || $scfg->{type} eq 'lvmthin') {
>> -
>> -	    $volid = PVE::Storage::vdisk_alloc($storecfg, $storage, $vmid, 'raw', undef, $size_kb);
>> -	    $do_format = 1;
>> -
>> -	} elsif ($scfg->{type} eq 'rbd') {
>> -
>> +	} elsif ($scfg->{content}->{rootdir}) {
>>   	    $volid = PVE::Storage::vdisk_alloc($storecfg, $storage, $vmid, 'raw', undef, $size_kb);
>>   	    $do_format = 1;
>>   	} else {
>> -	    die "unable to create containers on storage type '$scfg->{type}'\n";
>> +	    die "storage type '$scfg->{type}' does not supoort containers\n";
>>   	}
>>   	format_disk($storecfg, $volid, $rootuid, $rootgid) if $do_format;
>>       };
>>




  reply	other threads:[~2021-05-17 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17  9:03 Lorenz Stechauner
2021-05-17 13:41 ` Thomas Lamprecht
2021-05-17 14:21   ` Lorenz Stechauner [this message]
2021-05-25  7:57 ` Fabian Ebner

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=500231a8-ae07-3d96-9db3-62809ee3bf93@proxmox.com \
    --to=l.stechauner@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