| 19 | This section will guide you through creating and starting a slice, requesting a LAMP services certificate for you slice, uploading your experiment's topology to [http://groups.geni.net/geni/wiki/LAMP/Glossary#UNIS UNIS], and setting up the instrumentation and measurement of your slice. |
| 20 | |
| 21 | === Few words on the LAMP I&M System design === |
| 22 | |
| 23 | It is useful to understand the general principles behind the steps we will take throughout this tutorial. The LAMP I&M System is built on top of three pillars: |
| 24 | |
| 25 | - LAMP Portal: The LAMP Portal is the goto resource for experimenters to manage and visualize their I&M services and data. The portal is deployed with the LAMP image and will usually be enabled through the initial RSpec configuration for the experiment. The portal can run on any node or (nodes) within the slice. The LAMP Portal is derived from the Web Admin component of the pS-Performance Toolkit 3.2 RC1 (although not required, looking at the [http://code.google.com/p/perfsonar-ps/wiki/pSPerformanceToolkit31 comprehensive Quick Start guide] of the pS Toolkit can be very useful to understand the LAMP I&M System setup). |
| 26 | |
| 27 | - UNIS and Topology-based Configuration: xxxxxxx |
| 28 | |
| 29 | - perfSONAR-PS software suite: xxxxx |
| 30 | |
| 31 | |
| 32 | All the services on the LAMP I&M System have Authentication and Authorization (AA) capabilities based on the ProtoGENI AA model. See our [http://groups.geni.net/geni/wiki/LAMP/AA AA page] for more information. |
| 33 | |
| 34 | |
| 35 | |