...
-h1. Create standard objects
+Next, we're going to use the Arvados CLI tools on the <strong>shell server</strong> to create a few Arvados objects.
-h3. "All users" group
+First we create a repository object which will be used to set up a hosted clone of the arvados repository on this cluster.
-The convention is to add every active user to this group. We give it a distinctive UUID that looks like an IP broadcast address.
+<notextile>
+<pre><code>~$ <span class="userinput">prefix=`arv --format=uuid user current | cut -d- -f1`</span>
+~$ <span class="userinput">echo "Site prefix is '$prefix'"</span>
+~$ <span class="userinput">all_users_group_uuid="$prefix-j7d0g-fffffffffffffff"</span>
+~$ <span class="userinput">repo_uuid=`arv --format=uuid repository create --repository "{\"owner_uuid\":\"$prefix-tpzed-000000000000000\", \"name\":\"arvados\"}"`</span>
+~$ <span class="userinput">echo "Arvados repository uuid is '$repo_uuid'"</span>
+</code></pre></notextile>
-<pre>
-prefix=`arv user current | cut -d- -f1`
-read -rd $'\000' newgroup <<EOF; arv group create --group "$newgroup"
-{
- "uuid":"$prefix-j7d0g-fffffffffffffff",
- "name":"All users"
-}
-EOF
-</pre>
-
-h3. "arvados" repository
+Secondly, create a link object to make the repository object readable by the "All users" group, and therefore by every active user. This makes it possible for users to run the bundled Crunch scripts by specifying @"script_version":"master","repository":"arvados"@ rather than pulling the Arvados source tree into their own repositories.
-This will be readable by the "All users" group, and therefore by every active user. This makes it possible for users to run the bundled Crunch scripts by specifying a commit like "arvados:HEAD", rather than having to pull the Arvados git tree into their own repositories.
+<notextile>
+<pre><code>~$ <span class="userinput">read -rd $'\000' newlink <<EOF; arv link create --link "$newlink"</span>
+<span class="userinput">{
+ "tail_uuid":"$all_users_group_uuid",
+ "head_uuid":"$repo_uuid",
+ "link_class":"permission",
+ "name":"can_read"
+}
+EOF</span>
+</code></pre></notextile>
-<pre>
-prefix=`arv user current | cut -d- -f1`
-all_users_group_uuid="$prefix-j7d0g-fffffffffffffff"
-repo_uuid=`arv repository create --repository '{"name":"arvados"}'`
-echo "Arvados repository uuid is $repo_uuid"
+Next, create a default project for the standard Arvados Docker images, and give all users read access to it. The project is owned by the system user.
-read -rd $'\000' newlink <<EOF; arv link create --link "$newlink"
-{
- "tail_kind":"arvados#group",
+<notextile>
+<pre><code>~$ <span class="userinput">project_uuid=`arv --format=uuid group create --group "{\"owner_uuid\":\"$prefix-tpzed-000000000000000\", \"name\":\"Arvados Standard Docker Images\"}"`</span>
+~$ <span class="userinput">echo "Arvados project uuid is '$project_uuid'"</span>
+~$ <span class="userinput">read -rd $'\000' newlink <<EOF; arv link create --link "$newlink"</span>
+<span class="userinput">{
"tail_uuid":"$all_users_group_uuid",
- "head_kind":"arvados#repository",
- "head_uuid":"$repo_uuid",
+ "head_uuid":"$project_uuid",
"link_class":"permission",
- "name":"can_read"
-}
-EOF
-</pre>
-
-h3. Keep disks
-
-Currently, you need to tell Arvados about Keep disks manually.
-
-<pre>
-secret=`ruby -e 'print rand(2**512).to_s(36)[0..49]'`
-arv keep_disk create --keep-disk <<EOF
-{
- "service_host":"keep0.xyzzy.arvadosapi.com",
- "service_port":25107,
- "service_ssl_flag":false,
- "ping_secret":"$secret"
+ "name":"can_read"
}
-EOF
-</pre>
+EOF</span>
+</code></pre></notextile>
projects / arvados.git / blobdiff