mobilize-hdfs 1.0.0
Sign up to get free protection for your applications and to get access to all the features.
- data/.gitignore +19 -0
- data/Gemfile +4 -0
- data/LICENSE.txt +201 -0
- data/README.md +245 -0
- data/Rakefile +18 -0
- data/lib/mobilize-hdfs.rb +9 -0
- data/lib/mobilize-hdfs/handlers/hadoop.rb +67 -0
- data/lib/mobilize-hdfs/handlers/hdfs.rb +187 -0
- data/lib/mobilize-hdfs/tasks.rb +38 -0
- data/lib/mobilize-hdfs/version.rb +5 -0
- data/lib/samples/hadoop.yml +52 -0
- data/mobilize-hdfs.gemspec +20 -0
- data/test/hdfs_job_rows.yml +11 -0
- data/test/mobilize-hdfs_test.rb +46 -0
- data/test/redis-test.conf +540 -0
- data/test/test_helper.rb +10 -0
- metadata +82 -0
data/.gitignore
ADDED
data/Gemfile
ADDED
data/LICENSE.txt
ADDED
@@ -0,0 +1,201 @@
|
|
1
|
+
Apache License
|
2
|
+
Version 2.0, January 2004
|
3
|
+
http://www.apache.org/licenses/
|
4
|
+
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
6
|
+
|
7
|
+
1. Definitions.
|
8
|
+
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
11
|
+
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
13
|
+
the copyright owner that is granting the License.
|
14
|
+
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
16
|
+
other entities that control, are controlled by, or are under common
|
17
|
+
control with that entity. For the purposes of this definition,
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
19
|
+
direction or management of such entity, whether by contract or
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
22
|
+
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
24
|
+
exercising permissions granted by this License.
|
25
|
+
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
27
|
+
including but not limited to software source code, documentation
|
28
|
+
source, and configuration files.
|
29
|
+
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
31
|
+
transformation or translation of a Source form, including but
|
32
|
+
not limited to compiled object code, generated documentation,
|
33
|
+
and conversions to other media types.
|
34
|
+
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
36
|
+
Object form, made available under the License, as indicated by a
|
37
|
+
copyright notice that is included in or attached to the work
|
38
|
+
(an example is provided in the Appendix below).
|
39
|
+
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
46
|
+
the Work and Derivative Works thereof.
|
47
|
+
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
49
|
+
the original version of the Work and any modifications or additions
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
61
|
+
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
64
|
+
subsequently incorporated within the Work.
|
65
|
+
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
72
|
+
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
78
|
+
where such license applies only to those patent claims licensable
|
79
|
+
by such Contributor that are necessarily infringed by their
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
82
|
+
institute patent litigation against any entity (including a
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
85
|
+
or contributory patent infringement, then any patent licenses
|
86
|
+
granted to You under this License for that Work shall terminate
|
87
|
+
as of the date such litigation is filed.
|
88
|
+
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
91
|
+
modifications, and in Source or Object form, provided that You
|
92
|
+
meet the following conditions:
|
93
|
+
|
94
|
+
(a) You must give any other recipients of the Work or
|
95
|
+
Derivative Works a copy of this License; and
|
96
|
+
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
98
|
+
stating that You changed the files; and
|
99
|
+
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
102
|
+
attribution notices from the Source form of the Work,
|
103
|
+
excluding those notices that do not pertain to any part of
|
104
|
+
the Derivative Works; and
|
105
|
+
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
108
|
+
include a readable copy of the attribution notices contained
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
111
|
+
of the following places: within a NOTICE text file distributed
|
112
|
+
as part of the Derivative Works; within the Source form or
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
114
|
+
within a display generated by the Derivative Works, if and
|
115
|
+
wherever such third-party notices normally appear. The contents
|
116
|
+
of the NOTICE file are for informational purposes only and
|
117
|
+
do not modify the License. You may add Your own attribution
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
120
|
+
that such additional attribution notices cannot be construed
|
121
|
+
as modifying the License.
|
122
|
+
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
124
|
+
may provide additional or different license terms and conditions
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
128
|
+
the conditions stated in this License.
|
129
|
+
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
133
|
+
this License, without any additional terms or conditions.
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
135
|
+
the terms of any separate license agreement you may have executed
|
136
|
+
with Licensor regarding such Contributions.
|
137
|
+
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
140
|
+
except as required for reasonable and customary use in describing the
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
142
|
+
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
152
|
+
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
158
|
+
incidental, or consequential damages of any character arising as a
|
159
|
+
result of this License or out of the use or inability to use the
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
162
|
+
other commercial damages or losses), even if such Contributor
|
163
|
+
has been advised of the possibility of such damages.
|
164
|
+
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
168
|
+
or other liability obligations and/or rights consistent with this
|
169
|
+
License. However, in accepting such obligations, You may act only
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
174
|
+
of your accepting any such warranty or additional liability.
|
175
|
+
|
176
|
+
END OF TERMS AND CONDITIONS
|
177
|
+
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
179
|
+
|
180
|
+
To apply the Apache License to your work, attach the following
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
182
|
+
replaced with your own identifying information. (Don't include
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
184
|
+
comment syntax for the file format. We also recommend that a
|
185
|
+
file or class name and description of purpose be included on the
|
186
|
+
same "printed page" as the copyright notice for easier
|
187
|
+
identification within third-party archives.
|
188
|
+
|
189
|
+
Copyright 2012 ngmoco, LLC
|
190
|
+
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
192
|
+
you may not use this file except in compliance with the License.
|
193
|
+
You may obtain a copy of the License at
|
194
|
+
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
196
|
+
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
200
|
+
See the License for the specific language governing permissions and
|
201
|
+
limitations under the License.
|
data/README.md
ADDED
@@ -0,0 +1,245 @@
|
|
1
|
+
Mobilize-Hdfs
|
2
|
+
===============
|
3
|
+
|
4
|
+
Mobilize-Hdfs adds the power of hdfs to [mobilize-ssh][mobilize-ssh].
|
5
|
+
* read, write, and copy hdfs files through Google
|
6
|
+
Spreadsheets.
|
7
|
+
|
8
|
+
Table Of Contents
|
9
|
+
-----------------
|
10
|
+
* [Overview](#section_Overview)
|
11
|
+
* [Install](#section_Install)
|
12
|
+
* [Mobilize-Hdfs](#section_Install_Mobilize-Hdfs)
|
13
|
+
* [Install Dirs and Files](#section_Install_Dirs_and_Files)
|
14
|
+
* [Configure](#section_Configure)
|
15
|
+
* [Hdfs](#section_Configure_Hdfs)
|
16
|
+
* [Start](#section_Start)
|
17
|
+
* [Create Job](#section_Start_Create_Job)
|
18
|
+
* [Run Test](#section_Start_Run_Test)
|
19
|
+
* [Meta](#section_Meta)
|
20
|
+
* [Author](#section_Author)
|
21
|
+
|
22
|
+
<a name='section_Overview'></a>
|
23
|
+
Overview
|
24
|
+
-----------
|
25
|
+
|
26
|
+
* Mobilize-hdfs adds Hdfs methods to mobilize-ssh.
|
27
|
+
|
28
|
+
<a name='section_Install'></a>
|
29
|
+
Install
|
30
|
+
------------
|
31
|
+
|
32
|
+
Make sure you go through all the steps in the
|
33
|
+
[mobilize-base][mobilize-base] and [mobilize-ssh][mobilize-ssh]
|
34
|
+
install sections first.
|
35
|
+
|
36
|
+
<a name='section_Install_Mobilize-Hdfs'></a>
|
37
|
+
### Mobilize-Hdfs
|
38
|
+
|
39
|
+
add this to your Gemfile:
|
40
|
+
|
41
|
+
``` ruby
|
42
|
+
gem "mobilize-hdfs"
|
43
|
+
```
|
44
|
+
|
45
|
+
or do
|
46
|
+
|
47
|
+
$ gem install mobilize-hdfs
|
48
|
+
|
49
|
+
for a ruby-wide install.
|
50
|
+
|
51
|
+
<a name='section_Install_Dirs_and_Files'></a>
|
52
|
+
### Dirs and Files
|
53
|
+
|
54
|
+
### Rakefile
|
55
|
+
|
56
|
+
Inside the Rakefile in your project's root dir, make sure you have:
|
57
|
+
|
58
|
+
``` ruby
|
59
|
+
require 'mobilize-base/tasks'
|
60
|
+
require 'mobilize-ssh/tasks'
|
61
|
+
require 'mobilize-hdfs/tasks'
|
62
|
+
```
|
63
|
+
|
64
|
+
This defines rake tasks essential to run the environment.
|
65
|
+
|
66
|
+
### Config Dir
|
67
|
+
|
68
|
+
run
|
69
|
+
|
70
|
+
$ rake mobilize_hdfs:setup
|
71
|
+
|
72
|
+
This will copy over a sample hadoop.yml to your config dir.
|
73
|
+
|
74
|
+
<a name='section_Configure'></a>
|
75
|
+
Configure
|
76
|
+
------------
|
77
|
+
|
78
|
+
<a name='section_Configure_Hadoop'></a>
|
79
|
+
### Configure Hadoop
|
80
|
+
|
81
|
+
* Hadoop is big data. That means we need to be careful when reading from
|
82
|
+
the cluster as it could easily fill up our mongodb instance, RAM, local disk
|
83
|
+
space, etc.
|
84
|
+
* To achieve this, all hadoop operations, stage outputs, etc. are
|
85
|
+
executed and stored on the cluster only.
|
86
|
+
* The exceptions are:
|
87
|
+
* writing to the cluster from an external source, such as a google
|
88
|
+
sheet. Here there
|
89
|
+
is no risk as the external source has much more strict size limits than
|
90
|
+
hdfs.
|
91
|
+
* reading from the cluster, such as for posting to google sheet. In
|
92
|
+
this case, the read_limit parameter dictates the maximum amount that can
|
93
|
+
be read. If the data is bigger than the read limit, an exception will be
|
94
|
+
raised.
|
95
|
+
|
96
|
+
The Hadoop configuration consists of:
|
97
|
+
* output_cluster, which is the cluster where stage outputs will be
|
98
|
+
stored. Clusters are defined in the clusters parameter as described
|
99
|
+
below.
|
100
|
+
* output_dir, which is the absolute path to the directory in HDFS that will store stage
|
101
|
+
outputs. Directory names should end with a slash (/).
|
102
|
+
* read_limit, which is the maximum size data that can be read from the
|
103
|
+
cluster. This is applied at read time by piping hadoop dfs -cat | head
|
104
|
+
-c <size limit>. Default is 1GB.
|
105
|
+
* clusters - this defines aliases for clusters, which are used as
|
106
|
+
parameters for Hdfs stages. Cluster aliases contain 5 parameters:
|
107
|
+
* namenode - defines the name and port for accessing the namenode
|
108
|
+
* name - namenode full name, as in namenode1.host.com
|
109
|
+
* port - namenode port, by default 50070
|
110
|
+
* gateway_node - defines the node that executes the cluster commands.
|
111
|
+
* exec_path - defines the path to the hadoop
|
112
|
+
This node must be defined in ssh.yml according to the specs in
|
113
|
+
[mobilize-ssh][mobilize-ssh]. The gateway node can be the same for
|
114
|
+
multiple clusters, depending on your cluster setup.
|
115
|
+
* exec_path - defines the path to the hadoop executable on the
|
116
|
+
gateway_node.
|
117
|
+
|
118
|
+
Sample hadoop.yml:
|
119
|
+
|
120
|
+
``` yml
|
121
|
+
---
|
122
|
+
development:
|
123
|
+
output_cluster: dev_cluster
|
124
|
+
output_dir: /user/mobilize/development/
|
125
|
+
read_limit: 1000000000
|
126
|
+
clusters:
|
127
|
+
dev_cluster:
|
128
|
+
namenode:
|
129
|
+
name: dev_namenode.host.com
|
130
|
+
port: 50070
|
131
|
+
gateway_node: dev_hadoop_host
|
132
|
+
exec_path: /path/to/hadoop
|
133
|
+
dev_cluster_2:
|
134
|
+
namenode:
|
135
|
+
name: dev_namenode_2.host.com
|
136
|
+
port: 50070
|
137
|
+
gateway_node: dev_hadoop_host
|
138
|
+
exec_path: /path/to/hadoop
|
139
|
+
test:
|
140
|
+
output_cluster: test_cluster
|
141
|
+
output_dir: /user/mobilize/test/
|
142
|
+
read_limit: 1000000000
|
143
|
+
clusters:
|
144
|
+
test_cluster:
|
145
|
+
namenode:
|
146
|
+
name: test_namenode.host.com
|
147
|
+
port: 50070
|
148
|
+
gateway_node: test_hadoop_host
|
149
|
+
exec_path: /path/to/hadoop
|
150
|
+
test_cluster_2:
|
151
|
+
namenode:
|
152
|
+
name: test_namenode_2.host.com
|
153
|
+
port: 50070
|
154
|
+
gateway_node: test_hadoop_host
|
155
|
+
exec_path: /path/to/hadoop
|
156
|
+
production:
|
157
|
+
output_cluster: prod_cluster
|
158
|
+
output_dir: /user/mobilize/production/
|
159
|
+
read_limit: 1000000000
|
160
|
+
clusters:
|
161
|
+
prod_cluster:
|
162
|
+
namenode:
|
163
|
+
name: prod_namenode.host.com
|
164
|
+
port: 50070
|
165
|
+
gateway_node: prod_hadoop_host
|
166
|
+
exec_path: /path/to/hadoop
|
167
|
+
prod_cluster_2:
|
168
|
+
namenode:
|
169
|
+
name: prod_namenode_2.host.com
|
170
|
+
port: 50070
|
171
|
+
gateway_node: prod_hadoop_host
|
172
|
+
exec_path: /path/to/hadoop
|
173
|
+
```
|
174
|
+
|
175
|
+
<a name='section_Start'></a>
|
176
|
+
Start
|
177
|
+
-----
|
178
|
+
|
179
|
+
<a name='section_Start_Create_Job'></a>
|
180
|
+
### Create Job
|
181
|
+
|
182
|
+
* For mobilize-hdfs, the following stages are available.
|
183
|
+
* cluster and user are optional for all of the below.
|
184
|
+
* cluster defaults to output_cluster;
|
185
|
+
* user is treated the same way as in [mobilize-ssh][mobilize-ssh].
|
186
|
+
* hdfs.read `source:<hdfs_full_path>, user:<user>`, which reads the input path on the specified cluster.
|
187
|
+
* hdfs.write `source:<gsheet_full_path>, target:<hdfs_full_path>, user:<user>`
|
188
|
+
* hdfs.copy `source:<source_hdfs_full_path>,target:<target_hdfs_full_path>,user:<user>`
|
189
|
+
* The gsheet_full_path should be of the form `<gbook_name>/<gsheet_name>`. The test uses "Requestor_mobilize(test)/test_hdfs_1.in".
|
190
|
+
* The hdfs_full_path is the cluster alias followed by full path on the cluster.
|
191
|
+
* if a full path is supplied without a preceding cluster alias (e.g. "/user/mobilize/test/test_hdfs_1.in"),
|
192
|
+
the output cluster will be used.
|
193
|
+
* The test uses "/user/mobilize/test/test_hdfs_1.in" for the initial
|
194
|
+
write, then "test_cluster_2/user/mobilize/test/test_hdfs_copy.out" for
|
195
|
+
the copy and subsequent read.
|
196
|
+
* both cluster arguments and user are optional. If copying from
|
197
|
+
one cluster to another, your source_cluster gateway_node must be able to
|
198
|
+
access both clusters.
|
199
|
+
|
200
|
+
<a name='section_Start_Run_Test'></a>
|
201
|
+
### Run Test
|
202
|
+
|
203
|
+
To run tests, you will need to
|
204
|
+
|
205
|
+
1) go through the [mobilize-base][mobilize-base] and [mobilize-ssh][mobilize-ssh] tests first
|
206
|
+
|
207
|
+
2) clone the mobilize-hdfs repository
|
208
|
+
|
209
|
+
From the project folder, run
|
210
|
+
|
211
|
+
3) $ rake mobilize_hdfs:setup
|
212
|
+
|
213
|
+
Copy over the config files from the mobilize-base and mobilize-ssh
|
214
|
+
projects into the config dir, and populate the values in the hadoop.yml file.
|
215
|
+
|
216
|
+
If you don't have two clusters, you can populate test_cluster_2 with the
|
217
|
+
same cluster as your first.
|
218
|
+
|
219
|
+
3) $ rake test
|
220
|
+
|
221
|
+
* The test runs a 4 stage job:
|
222
|
+
* test_hdfs_1:
|
223
|
+
* `hdfs.write target:"/user/mobilize/test/test_hdfs_1.out", source:"Runner_mobilize(test)/test_hdfs_1.in"`
|
224
|
+
* `hdfs.copy source:"/user/mobilize/test/test_hdfs_1.out",target:"test_cluster_2/user/mobilize/test/test_hdfs_1_copy.out"`
|
225
|
+
* `hdfs.read source:"/user/mobilize/test/test_hdfs_1_copy.out"`
|
226
|
+
* `gsheet.write source:"stage3", target:"Runner_mobilize(test)/test_hdfs_1_copy.out"`
|
227
|
+
* at the end of the test, there should be a sheet named "test_hdfs_1_copy.out" with the same data as test_hdfs_1.in
|
228
|
+
|
229
|
+
<a name='section_Meta'></a>
|
230
|
+
Meta
|
231
|
+
----
|
232
|
+
|
233
|
+
* Code: `git clone git://github.com/ngmoco/mobilize-hdfs.git`
|
234
|
+
* Home: <https://github.com/ngmoco/mobilize-hdfs>
|
235
|
+
* Bugs: <https://github.com/ngmoco/mobilize-hdfs/issues>
|
236
|
+
* Gems: <http://rubygems.org/gems/mobilize-hdfs>
|
237
|
+
|
238
|
+
<a name='section_Author'></a>
|
239
|
+
Author
|
240
|
+
------
|
241
|
+
|
242
|
+
Cassio Paes-Leme :: cpaesleme@ngmoco.com :: @cpaesleme
|
243
|
+
|
244
|
+
[mobilize-base]: https://github.com/ngmoco/mobilize-base
|
245
|
+
[mobilize-ssh]: https://github.com/ngmoco/mobilize-ssh
|