Hi all ! new to Solus.io with quick question : Direct SAS requirement

Comments

4 comments

  • Official comment
    Avatar
    Artem Volov

    Hi Mathieu Fleet!

    SolusIO > Storage page is used to configure/register only remote storage (NFS in this case), which in turn can be added for specific nodes in their configuration (SolusIO > Compute Resources > necessary CR). It is done so because the addition of remote storage requires extra settings and steps (that are done on a server with NFS share manually) as opposed to LV/file-based storage.

    In your case - using a shared SAS array - it still will be detected as a disk device by all servers that the array is attached to - meaning that you can use this device like any other disk. So you need to operate with it on each CR separately - mount to a directory of a (CR) and use this directory for file-based storage in SolusIO, or you will need to create a volume group and manually configure sharing between all servers (CRs) - then use this volume group for each CR in SolusIO.

    As for plans - after you have added your SAS storage (either as file-based or LV) to each of your CR - you can create a plan for the required type of storage. Unfortunately, it is not possible to select a specific CR storage for a plan (as plans are used globally for all CRs), only its type is selectable.

    Comment actions Permalink
  • Avatar
    Mathieu Fleet

    hi Artmen

    i have successfuly created my cluster in Linux with Highavailibility cluster. both of my blades server see the Disk and we cant mount Virtual VPS on both Ressource computer.

    the problem come at the migration , live or standard migration. it say that the File already exist. ( as both server have access to /data/ ) 

    it seem that Solus.io try to '' copy data '' when its absolutely not desired as the data is already there.

    we need to tell solus.io to not try to replicate data for shared storage.

    thank you for your recommendation as we are waiting for this to deploy :D 

    0
    Comment actions Permalink
  • Avatar
    Mathieu Fleet

    we are getting this error if it can help.

    as you see it try to create a copy of the disk i think for absolutely nothing as its a cluser disk ressource.

     

    Cannot migrate VM: failed to prepare destination for migration: failed to create disks on destination: got unexpected status code 500: cannot initialize disk "/dev/clustvg/2": disk already exists

    0
    Comment actions Permalink
  • Avatar
    Artem Volov

    Thank you for sharing this error with us - it is not possible to migrate SolusIO VPS without actual data transfer - meaning that SolusIO will always try to create a disk for VPS on target CR - and if there is a disk already - SolusIO does not know if it is the same disk (from cluster storage) - it is considered a new object, which prevents migration - exactly what you encountered.

    I have created a ticket 26941 in our system to provide a bit more information - you should have already received a reply there.

    0
    Comment actions Permalink

Please sign in to leave a comment.