Saul – Addition of host-fs content is captured in this story:
https://storyboard.openstack.org/#!/story/2006888
Greg and I planned to address a subset of content for this new page (Certificate Management, Local docker reg) in the first pass.
I will be working on this page next week and will welcome any host-fs content!
Cheers,
Kris
From: Waines, Greg <Greg.Waines@windriver.com>
Sent: Monday, November 25, 2019 5:27 AM
To: Saul Wold <sgw@linux.intel.com>; von Hoesslin, Volker <Volker.Hoesslin@swsn.de>; Sun, Austin <austin.sun@intel.com>; starlingx-discuss@lists.starlingx.io; Dale, Kristal <kristal.dale@intel.com>
Subject: Re: [Starlingx-discuss] controller filesystem
Actually a section on managing filesystems on the controllers is planned for STX 3.0 ... based on the proposed TOC for the new Operations Guide.
Greg
From:
Saul Wold <sgw@linux.intel.com>
Date: Thursday, November 21, 2019 at 12:13 PM
To: "von Hoesslin, Volker" <Volker.Hoesslin@swsn.de>, "Sun, Austin" <austin.sun@intel.com>, "starlingx-discuss@lists.starlingx.io"
<starlingx-discuss@lists.starlingx.io>, "Dale, Kristal" <kristal.dale@intel.com>
Subject: Re: [Starlingx-discuss] controller filesystem
Kristal:
We probably need a Story/Task added to the documentation to get the
documentation of host-fs added in the right place. This helps with
filesystem re-sizing.
Maybe it's already there.
Sau!
On 11/21/19 7:12 AM, von Hoesslin, Volker wrote:
incredible !!! thats the point i have search! big thx!
------------------------------------------------------------------------
*Von:* Sun, Austin [austin.sun@intel.com]
*Gesendet:* Donnerstag, 21. November 2019 15:20
*An:* von Hoesslin, Volker; starlingx-discuss@lists.starlingx.io
*Betreff:* Re: [Starlingx-discuss] controller filesystem
Hi Volker:
From the email chain,
You can probably the command line to change the size of docker lv
Thanks.
BR
Austin Sun.
*From:* von Hoesslin, Volker <Volker.Hoesslin@swsn.de>
*Sent:* Thursday, November 21, 2019 9:20 PM
*Subject:* [Starlingx-discuss] controller filesystem
hi,
i trying to import some existing qcow2 images into my new installed STX 2.0.
openstack image create --file /media/foobar.qcow2 --private
--unprotected --disk-format qcow2 "foobar"
all works fine, the image are available.
now, i'm trying to create an new volume based on this images. if the
images are <=6GB all works fine, but some images are very huge
(10-200GB) and then it ends in an error. after some research i can see
on controller the mount point
/dev/mapper/cgts--vg-docker--lv 30G 11G 20G 35% /var/lib/docker
increase the used storage. after fail "volume create" it goes back to
given value 35%. in my oppinion, this mount point should resize to some
value about 300-400GB, but how? in STX horizon backend
there is an "docker-distribution", but no docker-mount-point itself?
btw, if i try to change the "docker-distribution" value to some other
value (eg. 500GB via horizon backend), i got this error:
*Error: *backup size of 60 is insufficient for host controller-1.
Minimum backup size of 100 is required based upon glance size 20 and
database size 20. Rejecting modification request.
- see attachment -
how can i increase the backup size to handle this error?!
greez & thx, volker...
_______________________________________________
Starlingx-discuss mailing list
_______________________________________________
Starlingx-discuss mailing list