/[pdpsoft]/trunk/grid-mw-security/ees/thesis/ees.tex
ViewVC logotype

Diff of /trunk/grid-mw-security/ees/thesis/ees.tex

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 945 by aramv, Tue Oct 20 02:01:11 2009 UTC revision 946 by aramv, Tue Oct 20 12:26:31 2009 UTC
# Line 6  The role of the \textit{Execution Enviro Line 6  The role of the \textit{Execution Enviro
6  It provides functionality similar to the SCAS, but delegates the enforcement to the PEP.  It provides functionality similar to the SCAS, but delegates the enforcement to the PEP.
7    
8  % TODO quote "Description of the EES"  % TODO quote "Description of the EES"
9    Here is a description of the EES taken from the document "Description of the EES" \cite{ees_design} for EGEE.
10    \begin{quote}
11    \textit{
12    From the ‘outside’ the EES appears as an ‘obligation transformer’.
13    It takes execution-agnostic assertions and obligations and makes sure that
14    \begin{itemize}
15    \item an execution environment compatible with these assertions and obligations is procured, e.g. by creating or leasing a Unix account;
16    \item new obligations are created that ensure that the policy enforcement points (PEP) can properly move the task into the procured execution environment;
17    \item removes any agnostic obligations that have been fully translated into a site-specific obligation, since the PEP has to be able to enforce all obligations present.
18    \end{itemize}
19    }
20    \end{quote}
21    
22  \section{Requirements}  \section{Requirements}
23  \subsection{Functional requirements}  \subsection{Functional requirements}
# Line 50  Pro's: Line 62  Pro's:
62  \item Fully Object Oriented  \item Fully Object Oriented
63  \item Supposedly very portable  \item Supposedly very portable
64  \end{itemize}  \end{itemize}
65  Con's:  Cons:
66  \begin{itemize}  \begin{itemize}
67  \item Not native, so hard to do low-level OS interaction  \item Not native, so hard to do low-level OS interaction
68  \item Likely to be a memory hog  \item Likely to be a memory hog
# Line 71  Pro's: Line 83  Pro's:
83  \item Can offer good overall performance on most architectures  \item Can offer good overall performance on most architectures
84  \item Has proven to be very portable  \item Has proven to be very portable
85  \end{itemize}  \end{itemize}
86  Con's:  Cons:
87  \begin{itemize}  \begin{itemize}
88  \item Requires careful programming  \item Requires careful programming
89  \item Sometimes a bit too low-level  \item Sometimes a bit too low-level
# Line 88  Pro's: Line 100  Pro's:
100  \item Offers good low-level OS interaction  \item Offers good low-level OS interaction
101  \item Can offer good overall performance on most architectures  \item Can offer good overall performance on most architectures
102  \end{itemize}  \end{itemize}
103  Con's:  Cons:
104  \begin{itemize}  \begin{itemize}
105  \item Not as portable as C  \item Not as portable as C
106  \end{itemize}  \end{itemize}
# Line 149  The rest of the configuration of the ser Line 161  The rest of the configuration of the ser
161  \nomenclature{EES}{Execution Environment Service}  \nomenclature{EES}{Execution Environment Service}
162    
163  \section{Proposed architecture for the EES}  \section{Proposed architecture for the EES}
164  The core component of the \textit{Execution Environment Service} (EES) is a shared library that exposes the core logic, dubbed the \textit{EES Execution Framework} (EEF).  The core component of the \textit{Execution Environment Service} (EES) is a shared library that exposes the core logic, hereby dubbed the \textit{EES Execution Framework} (EEF).
165  \glossary{name={EEF}, description={EES Execution Framework}}  \glossary{name={EEF}, description={EES Execution Framework}}
166  \nomenclature{EEF}{EES Execution Framework}  \nomenclature{EEF}{EES Execution Framework}
167    

Legend:
Removed from v.945  
changed lines
  Added in v.946

grid.support@nikhef.nl
ViewVC Help
Powered by ViewVC 1.1.28