Re: Exposing shares

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Making the AoE feature act like the alternatives makes sense to me.

Would it help you to do something like this if vblade was on github?  You could implement your full-featured vbladed replacement in a fork and see how it goes.

On May 12, 2014, at 1:01 PM, Turbo Fredriksson <turbo@xxxxxxxxxx> wrote:

> On May 11, 2014, at 6:18 PM, Turbo Fredriksson wrote:
> 
>> So I'm wondering about some 'status API' or somewhat to retrieve
>> information about shares and their status. Both the three iSCSI
>> implementations I added support for in ZoL as well as samba have
>> a well defined 'status' information.
> 
> 
> Since I haven't heard anything yet, I thought I put a couple of
> minutes thinking about this. This is what I came up with, without
> spending to much time on it, so it needs work:
> 
> 
> NEEDED INFO                                     IFACE CMD                       EXAMPLE RETURN
> ====================================================================================================
> 1. PID of vblade                                ask pid                         2919
> 2. Shelf number                                 ask shelf                       9
> 3. Slot number                                  ask slot                        0
> 4. Full device path                             ask device name                 /dev/zvol/rpool/test2
> 5. Size of device                               ask device size                 20971520
> 6. Share options (O_DIRECT, O_SYNC, r/o, r/w)   ask option [direct;sync;ro,rw]  
> 7. Ethernet interface for share                 ask netif                       eth0
> 8. Share state (up, ... ?)                      ask state                       up
> 9. MAC Access list                              ask cal 
> 
> 
> The simplest would be to have each individual vblade process
> create a socket to comunicate to.
> Example: /var/run/vblade/<netif>_<shelf>_<slot>.ctrl
> 
> Then 'echo' the command above, and it will respond appropriately.
> 
> 
> The more complicated (but not by much) is to create a 'mother process'
> that will spawon separate processes with ONE socket
> Example: /var/run/vblade/control
> 
>   Additional cmds:
>     create process <shelf> <slot> <options> <device>
>     ask processes
>       returns:
>       <pid> <shelf> <slot> <options> <device>
>       [....]
>     ask <pid> [cmd from top]
> 
>   This would then be 'vbladed' (binary, instead of the
>   shell script that it is today which simply waits for
>   commands and responds appropriately) and a 'vblade_cmd'
>   binary/script that 'simply' talks to the socket and
>   make 'vbladed' start (fork) the child process etc.
> --
> Michael Jackson is not going to buried or cremated
> but recycled into shopping bags so he can remain white,
> plastic and dangerous for kids to play with.
> 
> 
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Aoetools-discuss mailing list
> Aoetools-discuss@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/aoetools-discuss


------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Aoetools-discuss mailing list
Aoetools-discuss@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/aoetools-discuss




[Index of Archives]     [Linux ARM Kernel]     [Linux SCSI]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux