Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
cta
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Harbor Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
dCache
cta
Commits
32f07d43
Commit
32f07d43
authored
7 years ago
by
Michael Davis
Browse files
Options
Downloads
Patches
Plain Diff
Finishes chapter on installing CTA
parent
801f0982
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/latex/CTA_Admin_Install.tex
+23
-12
23 additions, 12 deletions
doc/latex/CTA_Admin_Install.tex
with
23 additions
and
12 deletions
doc/latex/CTA_Admin_Install.tex
+
23
−
12
View file @
32f07d43
...
...
@@ -550,8 +550,21 @@ Chapters~\ref{admin_commands} and~\ref{user_commands}).
\section
{
Configure EOS Workflows
}
The workflows define how EOS will talk to the CTA Front End. The following EOS workflows should be registered:
Archive workflow
(
executed on CLOSEW
)
:
\begin
{
itemize
}
\item
Archive workflow
(
executed on CLOSEW
)
\item
Retrieve workflow
(
executed on PREPARE
)
\item
Delete Archive workflow
(
executed on DELETE
)
\end
{
itemize
}
Create a workflow namespace directory. This will be used to store the workflow attributes but will not store any files:
\begin
{
lstlisting
}
# eos mkdir
-
p
/
eos
/
dev
/
proc
/
cta
/
workflow
\end
{
lstlisting
}
Link the attributes of the data directory to the attributes of the workflow directory. This causes the workflow
configuration to be inherited by the data directory:
\begin
{
lstlisting
}
# eos attr link
/
eos
/
dev
/
proc
/
cta
/
workflow
/
eos
/
users
/
test
\end
{
lstlisting
}
Configure the three workflows mentioned above. Archive workflow:
\begin
{
lstlisting
}
# eos attr set "sys.workflow.closew.default
=
bash:shell:cta 'cta archive
--
user <eos::wfe::rusername>
...
...
@@ -569,7 +582,7 @@ Archive workflow (executed on CLOSEW):
--
recoveryblob:base
64
<eos::wfe::base
64
:metadata>
--
diskpool default
--
throughput
10000
1
>
&
2
'" .
\end
{
lstlisting
}
Retrieve workflow
(
executed on PREPARE
)
:
Retrieve workflow:
\begin
{
lstlisting
}
# eos attr set "sys.workflow.prepare.default
=
bash:shell:cta 'cta retrieve
--
user <eos::wfe::rusername>
...
...
@@ -582,7 +595,7 @@ Retrieve workflow (executed on PREPARE):
--
recoveryblob:base
64
<eos::wfe::base
64
:metadata>
--
diskpool default
--
throughput
10000
1
>
&
2
'" .
\end
{
lstlisting
}
Delete Archive workflow
(
executed on DELETE
)
:
Delete Archive workflow:
\begin
{
lstlisting
}
# eos attr set "sys.workflow.delete.default
=
bash:shell:cta 'cta deletearchive
--
user <eos::wfe::rusername>
...
...
@@ -594,14 +607,12 @@ Ensure that the EOS workflow engine is switched on:
# eos space config default space.wfe
=
on
# eos space status default
\end
{
lstlisting
}
\subsection
{
Testing EOS with CTA
}
To trigger manually EOS workflows just use the following eos commands:
\begin
{
verbatim
}
file workflow <filename> default closew
file workflow <filename> default prepare
file workflow <filename> default delete
\end
{
verbatim
}
The workflow configuration can be tested by manually triggering the EOS workflows:
\begin
{
lstlisting
}
# eos file workflow <filename> default closew
# eos file workflow <filename> default prepare
# eos file workflow <filename> default delete
\end
{
lstlisting
}
\section
{
Removing CTA
}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment