<commit_before>\section{Features}
\label{features}

\small{
\begin{verbatim}
Also describe it in terms of ``services'', from llp's 10/03 slide

His service taxonomy:
Slice == Experiment Portal
    Create expt/slice
        Resource Discovery [w/ Monitoring Service]
        Resource Allocation
        Boot Slice [w/ Environment Service]

    Maintain expt/slice
        Software Upgrades [w/ Environment Service]
        Monitor Health [w/ Monitoring Service]
        Project membership

    *Control expt/slice
        Node 
        Expt

* = Not in llp's taxonomy; Elab-only

As of 10/03 Plab people were developing these; did not have anything:
   Environment Service
   Monitoring Service
   Resource allocation
\end{verbatim}
}%small



\subsection{Creating slices}

\subsubsection{Resource assignment}

Users of Emulab's PlanetLab interface have three choices for selecting the
nodes that will be used for their slice.

The most basic method is to manually chose nodes, as is done with the
PlanetLab's own current interface. This is accomplished by using Emulab's<commit_msg>Add a detailed outline of features.<commit_after>\section{Features}
\label{features}

\small{
\begin{verbatim}
Also describe it in terms of ``services'', from llp's 10/03 slide

His service taxonomy:
Slice == Experiment Portal
    Create expt/slice
        Resource Discovery [w/ Monitoring Service]
		Uses info from monitoring service
		Monitoring service:
			Node liveness, node resource availability (cpu/mem via loadavg, disk),
			e2e health, pair-wise paths.
        Resource Allocation
		Uses info from monitoring service
		Three ways, can be mixed
			fixed, site/node-centric (w/ types), link-centric [works?  no tunnels?]
		   port space (ssh; extend)
		Can mix with Emulab nodes (works?)

	*Admission control and optional queuing (queuing and retry service)

        Boot Slice [w/ Environment Service]

    Node/slice management (``environment service'')
	Node initialization
		Emulab state, per-user state
		Startup command

    Maintain expt/slice
        Software Upgrades [w/ Environment Service]
        Monitor Health [w/ Monitoring Service]
        Project membership

    *Control expt/slice
        Node 
        Expt

    *Naming service
	Virtual (DNS) or physical

    *Admin management service/interface
	Resource alloc params
	Admission control parameters
	Queue retry params


* = Not in llp's taxonomy; Elab-only

As of 10/03 Plab people were developing these; did not have anything:
   Environment Service
   Monitoring Service
   Resource allocation
\end{verbatim}
}%small



\subsection{Creating slices}

\subsubsection{Resource assignment}

Users of Emulab's PlanetLab interface have three choices for selecting the
nodes that will be used for their slice.

The most basic method is to manually chose nodes, as is done with the
PlanetLab's own current interface. This is accomplished by using Emulab's
{'fraction_non_alphanumeric': 0.06078296703296703, 'fraction_numerical': 0.005837912087912088, 'mean_word_length': 3.516279069767442, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7620180', 'n_tokens_mistral': 842, 'n_tokens_neox': 764, 'n_words': 341}