Difference between revisions of "OWASP Hive Project"

From OWASP
Jump to: navigation, search
(13 intermediate revisions by one user not shown)
Line 1: Line 1:
== '''WE NEED "PI's" FOR TESTING YOU CAN DONATE SOME''' ==
+
== '''WELCOME TO THE GRID'''==
[[File:owaspi.png|px637]]
+
 
 +
                        gggrgM**M#mggg__
 +
                __wgNN@"B*P""mp""@d#"@N#Nw__
 +
              _g#@0F_a*F#  _*F9m_ ,F9*__9NG#g_
 +
            _mN#F  aM"    #p"    !q@    9NL "9#Qu_
 +
          g#MF _pP"L  _g@"9L_  _g""#__  g"9w_ 0N#p
 +
        _0F jL*"  7_wF    #_gF    9gjF  "bJ  9h_
 +
        j#  gAF    _@NL    WELCOME      J@u_    2#_  #_
 +
      ,FF_#" 9_ _#"  "b_  g@  "hg  _#"  !q_ jF "*_09_
 +
      F N"    #p"      Ng@  TO  `#g"      "w@    "# t
 +
      j p#    g"9_    g@"9_      gP"#_    gF"q    Pb L
 +
      0J  k _@  9g_ j#"  "b_  j#"  "b_ _d"  q_ g  ##
 +
      #F  `NF    "#g"  THE  "Md" GRID  5N#      9W"  j#
 +
      #k  jFb_    g@"q_    _*"9m_    _*"R_    _#Np  J#
 +
      tApjF  9g  J"  9M_ _m"    9%_ _*"  "#  gF  9_jNF
 +
      k`N    "q#      9g@        #gF      ##"    #"j
 +
      `_0q_  #"q_    _&"9p_    _g"`L_    _*"#  jAF,'
 +
        9# "b_j  "b_ g"    *g _gF    9_ g#"  "L_*"qNF
 +
        "b_ "#_    "NL      _B#      _I@    j#" _#"
 +
          NM_0"*g_ j""9u_  gP  q_  _w@ ]_ _g*"F_g@
 +
            "NNh_ !w#_  9#g"    "m*"  _#*" _dN@"
 +
              9##g_0@q__ #"4_  j*"k __*NF_g#@P"
 +
                "9NN#gIPNL_ "b@" _2M"Lg#N@F"
 +
                    ""P@*NN#gEZgNN@#@P""
 +
 
 +
=Temp introducer URL=
 +
''' email me and I will give you the details if you would like to try the test grid '''
  
 
=What is it?=
 
=What is it?=
''' You have to [http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy watch the presentation] '''
+
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret! URI looks something like
**  ''' Cost Breakdown '''
+
 
*** '''Raspberry PI Cluster''' - Cost for 10 Environment Hive 500.00 (Approx)
+
<nowiki>URI%3ACHK%3Am6wj5avuhim3flsd2w54lhjcke:j2njlm3cm4sjzqdiwbadmts35lxa656kpvo66kx7wtlfyr6cab6a:3:10:3</nowiki>
*** '''4gb SD Card''' - Cost 8.37 (per Pi) (can be bigger)
+
 
*** '''Development of HIVE cluster wifi and power''' - Cost 300.00 (Approx)
+
Currently I am using a 3 to 10 ratio that means you will need at least 3 storage nodes to retrieve files from in order to download your erasure encoded stuff.  There are two kinds of files: immutable and mutable. When you upload a file to the storage grid you can choose which kind of file it will be in the grid. Immutable files can't be modified once they have been uploaded. A mutable file can be modified by someone with read-write access to it. A user can have read-write access to a mutable file or read-only access to it, or no access to it at all. If you want more details the link will take you to a site interactive illustration by Drew Perttula http://bigasterisk.com/tahoe-playground/
*** '''Single OWASPi HIVE-OFF''' - Cost 50.00 - 75.00 (MetalCase)
+
 
*** '''WiFi Mod''' - Cost 12.00 (per Pi)
+
Some ways I can see this being useful for OWASP is a HIVE cache that is currently what this project is becoming 10-1000 nodes strong but monitoring is controlled and nodes do what they please. The end goal is to provide a global grid for OWASP and any amount of users can use the GRID; a large, diverse ecosystem of people and organizations who want a storage grid with extremely high reliability and availability.
*** '''Starter Kit''' - Cost 20.00 - 69.00 ( the 69$ one has GPIO pinout cables )
+
 
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.
+
Example of project based use. Let’s say BOB has a tomcat server and he wants to share its contents to JOE. BOB has Tahoe up and sets up a dropfolder and this folder he sets up just happens to be his entire tomcat folder. As files change they are sent to the grid and encrypted, stored and shared out to people that JOE selected to give his folder URI to. JOE now has a working copy of BOB’s stuff and can help or just create his own environment. All the while we always use SFTP or SSL with our frontends. If a node gets hacked and stolen because JACK forgot to lock up then big deal there are X number of nodes left and the files on JACKS node are encrypted erasure style.  
** '''QUOTE from [https://www.element14.com/community/groups/raspberry-pi element14 (NEWARK)]
+
 
** '''[http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy OWASPi Overview]'''
+
''The milestones that I anticipate are:''
 +
 
 +
Sweet user interface
 +
Find a LCD for the BeagleBone Black for IP or stats scrolling.
 +
The HIVE setup currently shows the nodes in real time. (expand more on this)  
 +
Make a proposal to OWASP for a more stable introducer and private GRID.
 +
 
  
 +
[https://tahoe-lafs.org Tahoe-lafs homepage]
 +
 
 
{{:Projects/OWASP_Hive_Project}}  
 
{{:Projects/OWASP_Hive_Project}}  
 
[[Category:OWASP Project]]
 
[[Category:OWASP Project]]

Revision as of 14:49, 23 September 2013

WELCOME TO THE GRID

                        gggrgM**M#mggg__
                __wgNN@"B*P""mp""@d#"@N#Nw__
              _g#@0F_a*F#  _*F9m_ ,F9*__9NG#g_
           _mN#F  aM"    #p"    !q@    9NL "9#Qu_
          g#MF _pP"L  _g@"9L_  _g""#__  g"9w_ 0N#p
        _0F jL*"   7_wF     #_gF     9gjF   "bJ  9h_
       j#  gAF    _@NL    WELCOME      J@u_    2#_  #_
      ,FF_#" 9_ _#"  "b_  g@   "hg  _#"  !q_ jF "*_09_
      F N"    #p"      Ng@   TO  `#g"      "w@    "# t
     j p#    g"9_     g@"9_      gP"#_     gF"q    Pb L
     0J  k _@   9g_ j#"   "b_  j#"   "b_ _d"   q_ g  ##
     #F  `NF     "#g"  THE  "Md" GRID  5N#      9W"  j#
     #k  jFb_    g@"q_     _*"9m_     _*"R_    _#Np  J#
     tApjF  9g  J"   9M_ _m"    9%_ _*"   "#  gF  9_jNF
      k`N    "q#       9g@        #gF       ##"    #"j
      `_0q_   #"q_    _&"9p_    _g"`L_    _*"#   jAF,'
       9# "b_j   "b_ g"    *g _gF    9_ g#"  "L_*"qNF
        "b_ "#_    "NL      _B#      _I@     j#" _#"
          NM_0"*g_ j""9u_  gP  q_  _w@ ]_ _g*"F_g@
           "NNh_ !w#_   9#g"    "m*"   _#*" _dN@"
              9##g_0@q__ #"4_  j*"k __*NF_g#@P"
                "9NN#gIPNL_ "b@" _2M"Lg#N@F"
                    ""P@*NN#gEZgNN@#@P""

Temp introducer URL

email me and I will give you the details if you would like to try the test grid

What is it?

The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret! URI looks something like

URI%3ACHK%3Am6wj5avuhim3flsd2w54lhjcke:j2njlm3cm4sjzqdiwbadmts35lxa656kpvo66kx7wtlfyr6cab6a:3:10:3

Currently I am using a 3 to 10 ratio that means you will need at least 3 storage nodes to retrieve files from in order to download your erasure encoded stuff. There are two kinds of files: immutable and mutable. When you upload a file to the storage grid you can choose which kind of file it will be in the grid. Immutable files can't be modified once they have been uploaded. A mutable file can be modified by someone with read-write access to it. A user can have read-write access to a mutable file or read-only access to it, or no access to it at all. If you want more details the link will take you to a site interactive illustration by Drew Perttula http://bigasterisk.com/tahoe-playground/

Some ways I can see this being useful for OWASP is a HIVE cache that is currently what this project is becoming 10-1000 nodes strong but monitoring is controlled and nodes do what they please. The end goal is to provide a global grid for OWASP and any amount of users can use the GRID; a large, diverse ecosystem of people and organizations who want a storage grid with extremely high reliability and availability.

Example of project based use. Let’s say BOB has a tomcat server and he wants to share its contents to JOE. BOB has Tahoe up and sets up a dropfolder and this folder he sets up just happens to be his entire tomcat folder. As files change they are sent to the grid and encrypted, stored and shared out to people that JOE selected to give his folder URI to. JOE now has a working copy of BOB’s stuff and can help or just create his own environment. All the while we always use SFTP or SSL with our frontends. If a node gets hacked and stolen because JACK forgot to lock up then big deal there are X number of nodes left and the files on JACKS node are encrypted erasure style.

The milestones that I anticipate are:

Sweet user interface Find a LCD for the BeagleBone Black for IP or stats scrolling. The HIVE setup currently shows the nodes in real time. (expand more on this) Make a proposal to OWASP for a more stable introducer and private GRID.


Tahoe-lafs homepage


PROJECT INFO
What does this OWASP project offer you?
RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: OWASP_Hive (home page)
Purpose: The HIVE is a bunch of small computers in a cluster or stand alone.

hive (noun)

1. THE HIVE
a. Structure for housing bees aka (WASPS), especially owasps.
b. Colony of bees/owasps living in such a structure.
2. A place swarming with activity.
v. hived, hiv·ing, hives
1. To collect into a hive.
2. To store (data) in a hive.
3. To store up; accumulate.
v.intr.
1. To enter and occupy a hive or network.
2. To live with many others in close association (OWASP).
Phrasal Verb
hive off (term used when gathering)
To set apart from a group: hived off the department into another division.
License: N/A
who is working on this project?
Project Leader(s):
  • Jason Johnson @
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation: View
Mailing list: Mailing List Archives
Project Roadmap: View
Key Contacts
  • Contact Jason Johnson @ to contribute to this project
  • Contact Jason Johnson @ to review or sponsor this project
  • Contact the GPC to report a problem or concern about this project or to update information.
current release
Not Yet Published
last reviewed release
Not Yet Reviewed


other releases