Menu
▾
▴
opennode-users
|
From: <ope...@li...> - 2014-11-12 19:12:15
|
Greetings, I've been reading a bit on ploop vs simfs. Does anyone have any experience with this on OpenNode and if so, what are the caveats, pit-falls or reasons for or against using ploop? Thanks, -- -- Steven G. Spencer, Network Administrator KSC Corporate - The Kelly Supply Family of Companies Office 308-382-8764 Ext. 1131 Mobile 402-765-8010 |
|
From: <ope...@li...> - 2014-11-12 20:30:28
|
Hi Steven, Ploop package is included in the OpenNode 6 yum repos for some time now - and also some work was done to support veth devices management in case of ploop VMs. However - TUI has not been fully validated with ploop by us yet - not sure if there are any serious issues or not. You could enable ploop in /etc/vz/vz.conf and give it a try - and give some feedback about it :) > ope...@li... > <mailto:ope...@li...> > 12. november 2014 22:45 > Greetings, > > I've been reading a bit on ploop vs simfs. Does anyone have any > experience with this on OpenNode and if so, what are the caveats, > pit-falls or reasons for or against using ploop? > > Thanks, > Cheers, -- <http://www.getpostbox.com>---------------------------------------------- Andres Toomsalu,an...@op... <mailto:an...@op...> |
|
From: <ope...@li...> - 2014-11-12 20:46:49
|
On 11/12/2014 02:05 PM, ope...@li... wrote: > Hi Steven, > > Ploop package is included in the OpenNode 6 yum repos for some time > now - and also some work was done to support veth devices management > in case of ploop VMs. > However - TUI has not been fully validated with ploop by us yet - not > sure if there are any serious issues or not. You could enable ploop in > /etc/vz/vz.conf and give it a try - and give some feedback about it :) Sure. I've got a test machine on my home network that I can do this with and I'll report back. -- -- Steven G. Spencer, Network Administrator KSC Corporate - The Kelly Supply Family of Companies Office 308-382-8764 Ext. 1131 Mobile 402-765-8010 |
|
From: <ope...@li...> - 2014-11-12 21:18:13
|
On 11/12/2014 02:46 PM, ope...@li... wrote: > On 11/12/2014 02:05 PM, ope...@li... wrote: >> Hi Steven, >> >> Ploop package is included in the OpenNode 6 yum repos for some time >> now - and also some work was done to support veth devices management >> in case of ploop VMs. >> However - TUI has not been fully validated with ploop by us yet - not >> sure if there are any serious issues or not. You could enable ploop in >> /etc/vz/vz.conf and give it a try - and give some feedback about it :) > Sure. I've got a test machine on my home network that I can do this with > and I'll report back. > It would appear, without doing a ton of testing, that it worked as expected. The method was as follows: * prior to creating container with Opennode TUI, vi /etc/vz/vz.conf and change VE_LAYOUT=simfs to VE_LAYOUT=ploop * start the TUI and create a container using the CentOS 6 template * after the container is created and deployed, vzctl enter [Container ID] and did a yum update to ensure full network connectivity, which worked fine * exit out of the running container and check the contents of /storage/local/vz/private/[Container ID] rather than a complete listing of the filesystems directories, I see a root.hdd directory with the following contents: drwx------ 3 root root 4096 Nov 12 14:52 . drwxr-xr-x 3 root root 4096 Nov 12 14:51 .. -rw-r--r-- 1 root root 791 Nov 12 14:51 DiskDescriptor.xml -rw------- 1 root root 0 Nov 12 14:51 DiskDescriptor.xml.lck -rw------- 1 root root 1462763520 Nov 12 14:52 root.hdd drwx------ 2 root root 4096 Nov 12 14:51 root.hdd.mnt I have to fire up another server at home to test migration, but the above would indicate, I think, that the TUI did not balk at the ploop filesystem format. When I can, I'll fire up the other test server at home and do the test migrate and report back on that as well. Anything else that you would like to know about the results, please let me know. Thanks, -- -- Steven G. Spencer, Network Administrator KSC Corporate - The Kelly Supply Family of Companies Office 308-382-8764 Ext. 1131 Mobile 402-765-8010 |
|
From: <ope...@li...> - 2014-11-13 13:48:15
|
On 11/12/2014 10:20 PM, ope...@li... wrote: > Im pretty sure that creating template out of VM with TUI does not work > with ploop - could you please try that also? That is correct. The VM's container does not even show up as an option to create from. -- -- Steven G. Spencer, Network Administrator KSC Corporate - The Kelly Supply Family of Companies Office 308-382-8764 Ext. 1131 Mobile 402-765-8010 |
|
From: <ope...@li...> - 2014-11-13 14:25:49
|
On 11/13/2014 07:48 AM, ope...@li... wrote: > On 11/12/2014 10:20 PM,ope...@li... wrote: >> >Im pretty sure that creating template out of VM with TUI does not work >> >with ploop - could you please try that also? > That is correct. The VM's container does not even show up as an option > to create from. Never mind. I forgot to stop the container first. It /does/ show up as an option to create from, however once you fill out all of the new template data and get down to the OS template field, the cursor exits to the far right of the screen and you cannot input anything in the OS template field. Then the TUI says that it cannot create a template with white space: Ostemplate should not include white spaces. Got: 'Opening delta /storage/lo <-- believe this part of the message is truncated Adding delta dev=/dev/ploop53459 img=/storage/local/vz/private/[Container ID]/root.hdd -- -- Steven G. Spencer, Network Administrator KSC Corporate - The Kelly Supply Family of Companies Office 308-382-8764 Ext. 1131 Mobile 402-765-8010 |
|
From: <ope...@li...> - 2014-11-15 16:02:28
|
I guess that TUI wants to read something from CT filetree - but because of ploop it cant - as CT filesystem is now encapsulated inside disk image. > ope...@li... > <mailto:ope...@li...> > 13. november 2014 18:25 > Never mind. I forgot to stop the container first. It /does/ show up as > an option to create from, however once you fill out all of the new > template data and get down to the OS template field, the cursor exits to > the far right of the screen and you cannot input anything in the OS > template field. Then the TUI says that it cannot create a template with > white space: > > > Ostemplate should not include white spaces. Got: 'Opening delta > /storage/lo <-- believe this part of the message is truncated > Adding delta dev=/dev/ploop53459 > img=/storage/local/vz/private/[Container ID]/root.hdd > > ope...@li... > <mailto:ope...@li...> > 13. november 2014 16:48 > > That is correct. The VM's container does not even show up as an option > to create from. > > Andres Toomsalu <mailto:an...@op...> > 13. november 2014 7:20 > > Im pretty sure that creating template out of VM with TUI does not work > with ploop - could you please try that also? > > ope...@li... > <mailto:ope...@li...> > 13. november 2014 0:18 > It would appear, without doing a ton of testing, that it worked as > expected. The method was as follows: > > * prior to creating container with Opennode TUI, vi /etc/vz/vz.conf and > change VE_LAYOUT=simfs to VE_LAYOUT=ploop > * start the TUI and create a container using the CentOS 6 template > * after the container is created and deployed, vzctl enter [Container > ID] and did a yum update to ensure full network connectivity, which > worked fine > * exit out of the running container and check the contents of > /storage/local/vz/private/[Container ID] rather than a complete listing > of the filesystems directories, I see a root.hdd directory with the > following contents: > > drwx------ 3 root root 4096 Nov 12 14:52 . > drwxr-xr-x 3 root root 4096 Nov 12 14:51 .. > -rw-r--r-- 1 root root 791 Nov 12 14:51 DiskDescriptor.xml > -rw------- 1 root root 0 Nov 12 14:51 DiskDescriptor.xml.lck > -rw------- 1 root root 1462763520 Nov 12 14:52 root.hdd > drwx------ 2 root root 4096 Nov 12 14:51 root.hdd.mnt > > I have to fire up another server at home to test migration, but the > above would indicate, I think, that the TUI did not balk at the ploop > filesystem format. > > When I can, I'll fire up the other test server at home and do the test > migrate and report back on that as well. > > Anything else that you would like to know about the results, please let > me know. > > Thanks, > > ope...@li... > <mailto:ope...@li...> > 12. november 2014 23:46 > > Sure. I've got a test machine on my home network that I can do this with > and I'll report back. > -- <http://www.getpostbox.com>---------------------------------------------- Andres Toomsalu,an...@op... <mailto:an...@op...> |
|
From: <ope...@li...> - 2014-11-13 04:20:55
|
Im pretty sure that creating template out of VM with TUI does not work with ploop - could you please try that also? > ope...@li... > <mailto:ope...@li...> > 13. november 2014 1:18 > It would appear, without doing a ton of testing, that it worked as > expected. The method was as follows: > > * prior to creating container with Opennode TUI, vi /etc/vz/vz.conf and > change VE_LAYOUT=simfs to VE_LAYOUT=ploop > * start the TUI and create a container using the CentOS 6 template > * after the container is created and deployed, vzctl enter [Container > ID] and did a yum update to ensure full network connectivity, which > worked fine > * exit out of the running container and check the contents of > /storage/local/vz/private/[Container ID] rather than a complete listing > of the filesystems directories, I see a root.hdd directory with the > following contents: > > drwx------ 3 root root 4096 Nov 12 14:52 . > drwxr-xr-x 3 root root 4096 Nov 12 14:51 .. > -rw-r--r-- 1 root root 791 Nov 12 14:51 DiskDescriptor.xml > -rw------- 1 root root 0 Nov 12 14:51 DiskDescriptor.xml.lck > -rw------- 1 root root 1462763520 Nov 12 14:52 root.hdd > drwx------ 2 root root 4096 Nov 12 14:51 root.hdd.mnt > > I have to fire up another server at home to test migration, but the > above would indicate, I think, that the TUI did not balk at the ploop > filesystem format. > > When I can, I'll fire up the other test server at home and do the test > migrate and report back on that as well. > > Anything else that you would like to know about the results, please let > me know. > > Thanks, > > ope...@li... > <mailto:ope...@li...> > 12. november 2014 23:46 > > Sure. I've got a test machine on my home network that I can do this with > and I'll report back. > > Andres Toomsalu <mailto:an...@op...> > 12. november 2014 23:05 > Hi Steven, > > Ploop package is included in the OpenNode 6 yum repos for some time > now - and also some work was done to support veth devices management > in case of ploop VMs. > However - TUI has not been fully validated with ploop by us yet - not > sure if there are any serious issues or not. You could enable ploop in > /etc/vz/vz.conf and give it a try - and give some feedback about it :) > > > > Cheers, > ope...@li... > <mailto:ope...@li...> > 12. november 2014 21:45 > Greetings, > > I've been reading a bit on ploop vs simfs. Does anyone have any > experience with this on OpenNode and if so, what are the caveats, > pit-falls or reasons for or against using ploop? > > Thanks, > -- <http://www.getpostbox.com>---------------------------------------------- Andres Toomsalu,an...@op... <mailto:an...@op...> |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X