Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

Any news of 2.0?

Pages: 1 2

twinsen
10 Posts
February 9, 2018, 12:09 am

Should I always have something separate to connect to iSCSI of PetaSAN and then share it among my network (either Windows Server from your example with multipath over IP, or just Linux with CIFS/Samba), or it is possible to rely on built-in soultion, some kind of sharing directly from the nodes? To be honest, I tried Proxmox+CEPH, with LXC container in failover mode. It works surprisingly well. But Proxmox has no automatic deployment of nodes and probably I should use something like Salt to deploy some bigger cluster. You have it already done, and I don't really need any kind of VM in my home environment. Don't get me wrong, but even if majority of your customers/fans are in the commercial domain, those home users are also intereseted in such a solutions.

 

So, let me basically explain what I want to do. I want to but 3-4 post-leasing cheap Dell/HP desktop machines. Each one I wan to equip with:

  • 2 up to 4 HDDs (depends on the SATA ports onboard)
  • 2 ports NIC card low profile

So, it is possible, based on this, to create PetaSAN cluster, having CEPH cluster on the one LAN (separate non-managed switch), iSCSI traffic on another, and the built-in NIC card - for management?

 

Or, for home use - just 1 port NIC is enough - just for CEPH traffic, and the management/iSCSI on another?

But - it would be amazing, to have just 3 stacked machines available as home NAS. Yes, I know there are 1 box solutions. And the RAID and so on. But I just want to have your solution and ability to add some more "old" Dell/HP/Lenovo desktop machines equipped in some another 4TB WD disks for cluster expansion. Just for home.

Would you support me with some clues about it?

Still I need one more machine for Windows Server/Samba to grab CEPH by iSCSI, then share it?

Basically, to be honest - I can't afford Windows Server, or Nano Server. I would use Linux with Samba to share my CEPH.

How to do it the best? Share from PetaSAN machines, or as I said above - I need another one?

Thanks in advance for understanding hobbyist 😉

 

EDIT: Please explain to me - is it possible to provision let's say 20TB disk having only 3x4TB among the nodes, for a good start? Is this be shared with this size, and I just need to monitor if the data is not filling in too much? Is upcoming 2.0 based on Bluestore - behaving like this?

 

And finally: you said that for the journal in bluestore one need 20GB of fast SSD for example. Is this the case for whole OSD? That means, that having two 4TB, I need only 40GB of fast SSD on the machine? It would make sence then to buy older SSDs not to waste space having only 2 20GB partitions on them? - this is not well documented on CEPH - I tried to discover, but I'm stuck.

Last edited on February 9, 2018, 12:21 am by twinsen · #11

admin
2,930 Posts
February 9, 2018, 10:13 am

PetaSAN is a SAN and not NAS. SAN works at the disk/block level and communicate via iSCSI or FC, NAS works at the file system and provide a network share such as NFS/CIFS. So we provide block storage, in some use cases clients directly connect to the SAN to get block storage, other cases clients connect to vms which runs in hypervisors that connects to the SAN and there are cases when clients connect to  a file shares service that connects to the SAN.

For Windows shares, our focus was to insure integration comparability with MS SOFS  ( Scale Out File Server ) to provide scalable shares. You can however use a Linux Samba gateway, but Samba is not compatible with many MS server apps (hyper-v, SQL Server), but if you need it for simple user shares, Samba will do an excellent job, you will also need to setup Samba yourself and make it scalable and highly available else it will be your single point of failure. If you want to setup Samba yourself, then you should be able to install it on existing PetaSAN nodes, so Samba will serve your end clients and be itself a client for the iSCSI target disks.

Regarding NIC configuration, PetaSAN NIC setup is very flexible, so yes you can do the setup with 3 NICs

Regarding storage: example if you have 30 x 4 TB drives for a total of 120 TB raw storage, if your replica count is 2 then your clients will get 60 TB net, if your replica count is 3 your clients will see 40 TB net storage. Bluestore compression will let you get a higher net storage, but if you store videos and pictures then you will not benefit from any compression.

#12

twinsen
10 Posts
February 9, 2018, 10:49 am

Regarding storage: example if you have 30 x 4 TB drives for a total of 120 TB raw storage, if your replica count is 2 then your clients will get 60 TB net, if your replica count is 3 your clients will see 40 TB net storage. Bluestore compression will let you get a higher net storage, but if you store videos and pictures then you will not benefit from any compression.

But the question was, if I can overprovision just a RBD device? Like in your example, can I provision an iSCSI device like it was 500TB? Would it be thin provisioned then? I'm asking, because for just a start, I can use 3x4TB storage on each node. But to avoid further resizing or other filesystem manipulations, can I just provision more, and only monitor if the data is growing?

 

So, accepting this single point of failure, I would probably put another single node machine and let it run just a Samba, mount iSCSI shared from Peta SAN, then I will have NAS+SAN 🙂

 

Thanks for clarification!

#13

admin
2,930 Posts
February 9, 2018, 11:12 am

Yes all storage in PetaSAN is thin provisioned, this is the because Ceph itself is a cloud storage technology which does this by default, you can monitor your real storage from the dashboard, you will also get alarm notifications by email (if you set it) when physical storage starts to fill up. Please refer to the Quick Start guide, it explains all this.

You do not need extra Samba machines if you want you can use the existing PetaSAN nodes to setup a highly available Samba configuration. PetaSAN uses Ubuntu 16.04 as file system, you can use apt-get update (not upgrade ) and apt-get install to install Samba

Last edited on February 9, 2018, 11:14 am by admin · #14

twinsen
10 Posts
February 9, 2018, 11:40 am

You do not need extra Samba machines if you want you can use the existing PetaSAN nodes to setup a highly available Samba configuration. PetaSAN uses Ubuntu 16.04 as file system, you can use apt-get update (not upgrade ) and apt-get install to install Samba

What about to add such an option to the GUI, or already integrate Samba for small home deployments, and have both NAS/SAN solution in one?

But for now - should I install samba on every node right? And then, mounting share on my PC under which ip? What if 1 machine fails? How the CIFS connection would know, that the share is still there, as all connections would drop? Or you mean - use node1 samba ip, if this fails, remount drive in PC to the other node, right?

#15

yudorogov
31 Posts
February 12, 2018, 11:12 am
Quote from admin on February 7, 2018, 12:28 pm

No later than Monday

Monday is today. Why 2.0 not available to download?

#16

davlaw
35 Posts
February 12, 2018, 12:28 pm

Guess that is what happens when you publicly post a date, it will get here.

#17

trexman
60 Posts
February 12, 2018, 2:05 pm
Quote from yudorogov on February 12, 2018, 11:12 am
Quote from admin on February 7, 2018, 12:28 pm

No later than Monday

Monday is today. Why 2.0 not available to download?

Why? It is available.
You just have to play around with the download links 😉

Release 2.0.0

But I guess it isn't official released...

Last edited on February 12, 2018, 2:05 pm by trexman · #18
Pages: 1 2