Hi Michael, >When upgrade my first test installation from 4.0 à 4.2 it changed those >definitions from /vmfs/voluems to >/var/lib/one/datastores
Are you sure about this? Because the migrators from 4.0 to 4.2 doesn't change the datastore templates. > That’s exactly what happened , and on a clean install of 4.0 I was able to > modify oned.conf and change the default datastore to /vmfs/volumes and it > modified the original settings to use that for system(0) and images(1) > > But on a clean install of 4.2 – it made me create new DS’s and assign new > system(102) and images(103) to the cluster so as not to use 0/1/2 which only > expected local datastores. You are absolutely right. The only way in 4.2 to make a datastore using a DATASTORE_LOCATION other than "/var/lib/one/datastores" is to add it to a cluster with a DATASTORE_LOCATION set in its template. I've opened a bug to keep track of the solution: http://dev.opennebula.org/issues/2326 Thanks for the feedback! -Tino > > > > Michael Curran | connectsolutions | Lead Network Architect > > Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com > > > > From: Jaime Melis [mailto:jme...@opennebula.org] > Sent: Thursday, August 15, 2013 7:48 AM > > > To: Michael Curran > Cc: users@lists.opennebula.org > Subject: Re: [one-users] Datastores > > > > Sorry to ask you this basic question, but, what exactly do you mean by > > > > When upgrade my first test installation from 4.0 à 4.2 it changed those > definitions from /vmfs/voluems to /var/lib/one/datastore > > > Do you mean that before the upgrade you did "onedatastore show <id>|grep > BASE_PATH" and it pointed to /vmfs/volumes and after the upgrade the output > was /var/lib/one/datastores ?? > > That shouldn't be happening at all. > > > > On Wed, Aug 14, 2013 at 8:14 AM, Michael Curran > <michael.cur...@connectsolutions.com> wrote: > > The problem is – when I installed ON4.0 – I was able to re-direct the > datastores to the /vmfs/volumes instead of /var/lib/one/datastores > > > > So my system (0) and images (1) datastores did not have to be re-recreated > > > > When upgrade my first test installation from 4.0 à 4.2 it changed those > definitions from /vmfs/voluems to /var/lib/one/datastores and I had to > create my own datastores because they were not customizable by me > > > > Originally thought it was part of the upgrade process – however when I built > a clean installation of 4.2 I ran into the same problem 0/1/2 datastores all > expect ONLY local volumes to the ON node and I had to create my own > datastores for the cluster I built. > > > > I would expect that I should be able to do one of the following > > > > n Delete and recreate the 0/1/2 datastores for use as VMFS volumes instead > of locally mounted datastores > > n Modify or change those datastore definitions from locally mounted > directories to vmfs mounts (which is what I set in the oned.conf file, and > is adopted by the datastores) > > > > Michael Curran | connectsolutions | Lead Network Architect > > Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com > > > > From: Jaime Melis [mailto:jme...@opennebula.org] > Sent: Tuesday, August 13, 2013 5:36 PM > > > To: Michael Curran > Cc: users@lists.opennebula.org > Subject: Re: [one-users] Datastores > > > > Hi Michael, > > > > would you care to explain the problem again? we don't quite understand what > might be the issue. Do you have any further comments on the matter? > > > > regards, > > Jaime > > > > On Thu, Aug 8, 2013 at 12:44 PM, Michael Curran > <michael.cur...@connectsolutions.com> wrote: > > An update to this – > > > > I ran into the same issue with the DS names, before creating them myself – > and they only point locally > > > > I’ve created the system/images DS’s on my ESXi hosts as 102/103 – and > working on getting them to monitor > > > > So far just get errors if I run /var/lib/one/remotes/datastore/vmfs/monitor > > > > Are they any options at the end of monitor? > > > > > > Michael Curran | connectsolutions | Lead Network Architect > > Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com > > > > From: Ruben S. Montero [mailto:rsmont...@opennebula.org] > Sent: Thursday, July 25, 2013 12:55 PM > > > To: Michael Curran > Cc: users@lists.opennebula.org > Subject: Re: [one-users] Datastores > > > > Ok Thanks. We've been looking at the upgrade process and it should not > modify the base path of the datastores.... > > > > > > Cheers > > > > Ruben > > > > On Thu, Jul 25, 2013 at 6:21 PM, Michael Curran > <michael.cur...@connectsolutions.com> wrote: > > Okay – I re-created the images DS from the Sunstone GUI and when I uploaded > an image it now captures the right size – bug report maybe? I’ll find out > tomorrow when I transfer this to our DC lab machines from our office labs on > a clean build > > > > Michael Curran | connectsolutions | Lead Network Architect > > Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com > > > > From: users-boun...@lists.opennebula.org > [mailto:users-boun...@lists.opennebula.org] On Behalf Of Michael Curran > Sent: Thursday, July 25, 2013 11:26 AM > To: rsmont...@opennebula.org > > > Cc: users@lists.opennebula.org > Subject: Re: [one-users] Datastores > > > > The problem exists because when I upgrade from 4.0.1 à 4.1.80 it recreated > the images datastore with a path of /var/lib/one/datastores/1 and since I am > on vmfs – it should be /vmfs/volumes/1 > > > > Is there a way to modify that path? Or will I have to re-create the > datastore in OpenNebula and then rename the datastore? > > > > Michael Curran | connectsolutions | Lead Network Architect > > Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com > > > > From: Michael Curran > Sent: Thursday, July 25, 2013 9:06 AM > To: rsmont...@opennebula.org; Michael Curran > Cc: users@lists.opennebula.org > Subject: RE: [one-users] Datastores > > > > What does the monitor command look like from the CLI ? My logs only show > successful response, not what it ran to check > > But your right, if I do a list on the datastores - my system/images sore > zero or nothing...so that's my issue > > Sent from my Android phone using TouchDown (www.nitrodesk.com) > > -----Original Message----- > From: Michael Curran [michael.cur...@connectsolutions.com] > Received: Wednesday, 24 Jul 2013, 2:23pm > To: Ruben S. Montero [rsmont...@opennebula.org] > CC: users@lists.opennebula.org [users@lists.opennebula.org] > Subject: Re: [one-users] Datastores > > Ive been on the datastores – I will check the monitor data since that makes > the most sense – something must be amiss there > > > > My test env has 2 1tb volumes with one image and 2 running VM’s – neither is > more than 2% used > > > > So monitoring seems the likelier culprit – Ill investigate that piece. > > > > Michael Curran | connectsolutions | Lead Network Architect > > Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com > > > > From: Ruben S. Montero [mailto:rsmont...@opennebula.org] > Sent: Wednesday, July 24, 2013 1:04 PM > To: Michael Curran > Cc: users@lists.opennebula.org > Subject: Re: [one-users] Datastores > > > > This error is because of the space left in the datastore. Can you check that > datastores are being monitor, and capacity data is get without errors? Are > there any error or message relative to monitor datastores in oned.log? What > is the size available/total shown in onedatastore show ? > > > > Cheers > > > > Ruben > > > > On Wed, Jul 24, 2013 at 5:30 PM, Michael Curran > <michael.cur...@connectsolutions.com> wrote: > > Can the images DS and the filestore DS be the same physical volume? Or must > they be 2 separate volumes? > > > > When I try to upload files to the images DS – I get > > > > Req:752 UID:0 ImageAllocate result FAILURE Not enough space in datastore > > > > I also tested images files – and I get the same error > > > > I logged into the ESX host and made my way to the images datastore in > /vmfs/volumes/1 – and as oneadmin (ssh , no passwd) I am able to create and > remove files within the datastore itself > > > > p.s. – commands also fail the same way via CLI and oneimage command > > > > Michael Curran | connectsolutions | Lead Network Architect > > Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com > > > > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > > > > > -- > > -- > > Join us at OpenNebulaConf2013 in Berlin, 24-26 September, 2013 > > -- > > Ruben S. Montero, PhD > Project co-Lead and Chief Architect > OpenNebula - The Open Source Solution for Data Center Virtualization > www.OpenNebula.org | rsmont...@opennebula.org | @OpenNebula > > > > > > -- > > -- > > Join us at OpenNebulaConf2013 in Berlin, 24-26 September, 2013 > > -- > > Ruben S. Montero, PhD > Project co-Lead and Chief Architect > OpenNebula - The Open Source Solution for Data Center Virtualization > www.OpenNebula.org | rsmont...@opennebula.org | @OpenNebula > > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > > > > > -- > > Join us at OpenNebulaConf2013 in Berlin, 24-26 September, 2013 > -- > > Jaime Melis > Project Engineer > OpenNebula - The Open Source Toolkit for Cloud Computing > www.OpenNebula.org | jme...@opennebula.org > > > > > > -- > > Join us at OpenNebulaConf2013 in Berlin, 24-26 September, 2013 > -- > > Jaime Melis > Project Engineer > OpenNebula - The Open Source Toolkit for Cloud Computing > www.OpenNebula.org | jme...@opennebula.org > > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org