-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathstart.html
More file actions
73 lines (66 loc) · 3.26 KB
/
Copy pathstart.html
File metadata and controls
73 lines (66 loc) · 3.26 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
---
title: Getting started
layout: page
---
<div class="row">
<div class="col-xs-12 col-md-12">
<p class="start-steps text-justify">
<p class="start-steps-content">
<span class="start-steps">Read the basics</span>
</p>
<p class="start-steps-content">
You can check out the <a class="page-link" href="{{ 'architecture.html' | prepend: 'about/' }}">architecture</a> and the <a class="page-link" href="{{ 'features.html' | prepend: 'about/' }}">features</a> provided by the SHIELD platform.
</p>
</p>
<p class="start-steps text-justify">
<p class="start-steps-content">
<span class="start-steps">Identify and download specific components</span>
</p>
<p class="start-steps-content">
Determine which features you need and, based on that, which components you should install and configure.
</p>
</p>
<p class="start-steps text-justify">
<p class="start-steps-content">
<span class="start-steps">Prepare your infrastructure</span>
</p>
<p class="start-steps-content">
<p>
You will need to prepare your environment beforehand (for instance, the <strong>NFVI</strong>, and particularly OSM, will require one or more VIMs as OpenStack, VMware vCloud Director, AWS and OpenVIM). Some guidelines are provided <a class="page-link" href="{{ 'installing.html#infrastructure' | prepend: 'installation/' }}">here</a>.
</p>
<p>
On a lower level you will also need to configure your hardware (whether it is to install the base Operating System, to install a TPM-based firmware in a switch or perform any configuration on a TPM-enabled server); as well as interconnect it properly to conform your infrastructure or testbed.
</p>
</p>
</p>
<p class="start-steps text-justify">
<p class="start-steps-content">
<span class="start-steps">Install each component and apply configurations</span>
</p>
<p class="start-steps-content">
<p>
Go through the README file available in the repository of each component. Look also for information on the <a class="page-link" href="{{ 'installing.html' | prepend: 'installation/' }}">installation guide</a>.
</p>
<p>
The installed components must be configured before these can run. Check out the sample configuration files provided in the repository of each component, copy them into the final configuration file and update the templated values with your own. Again, refer to the installation guide for further details.
</p>
</p>
</p>
<p class="start-steps text-justify">
<p class="start-steps-content">
<span class="start-steps">Run the components and use them</span>
</p>
<p class="start-steps-content">
<p>
Upon a successful configuration and proper set-up of the environment, it is time to run all the components and perform manual tests to verify proper integration between the components in the SHIELD platform.
</p>
<p>
For instance, you may call a REST endpoint in the vNSFO API to start a workflow that involves several components and assess the final outcome against the expected one.
</p>
<p>
In the end, you may check the <a class="page-link" href="{{ 'user-guide.html' | prepend: 'installation/' }}">user guide</a> to see how to access the components and operate with them.
</p>
</p>
</p>
</div>
</div>