Skip to content

Commit ca15513

Browse files
committed
Update nova04delta docs
Signed-off-by: Bohdan Dobrelia <[email protected]>
1 parent 4fa444a commit ca15513

File tree

3 files changed

+60
-10
lines changed

3 files changed

+60
-10
lines changed

dt/nova/nova04delta/README.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
# Deployed Topology - Nova/nova04delta
2+
3+
If you are looking for information on how to deploy the nova04delta based DT, then
4+
please see the
5+
[README](../../../examples/dt/nova/nova04delta/README.md) in the examples
6+
directory.
7+
8+
This directory ,`dt/nova/nova04delta/`, exists so that the
9+
[kustomization.yaml](../../../examples/dt/nova/nova04delta/edpm/nodeset/kustomization.yaml)
10+
in the examples directory of nova04delta topology, reference it by path as a
11+
component. It's contents are likely uninteresting unless you want to understand
12+
how kustomize was implemented in this repository.

examples/dt/nova/nova04delta/README.md

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -29,14 +29,16 @@ The following parameters are crucial for host-level configuration:
2929

3030
## Nova Configuration
3131

32-
# FIXME: this looks only used in PCI groups in placement? The same pci_passthrough:alias should be used in both cases it seems?
33-
Nova control plane is configured for requesting PCI devices from Placement
34-
through `resources:VGPU=X` flavor extra specs.
35-
That is a contrary to the legacy mode where PCI devices used to be requested through
36-
`pci_passthrough:alias` flavor extra specs.
32+
A count of `X` PCI devices may be requested through `"pci_passthrough:alias"="nvidia_a2:X"` flavor extra specs:
33+
```
34+
$ openstack --os-compute-api=2.86 flavor set --property "pci_passthrough:alias"="nvidia_a2:1" device_passthrough
35+
```
3736

3837
### Control Plane (`examples/dt/nova/nova04delta/control-plane/service-values.yaml`)
3938

39+
See [README.md](control-plane/README.md) for deployment instructions.
40+
There are most essential configuration values to define:
41+
4042
* `[pci]alias`: Creates an alias for a specific GPU type. This allows users to request a GPU by a friendly name (e.g., `nvidia_a2`) when creating a VM. This configuration should match the configuration found on the compute nodes.
4143
```yaml
4244
nova:
@@ -53,6 +55,9 @@ That is a contrary to the legacy mode where PCI devices used to be requested thr
5355

5456
### Compute Node (`examples/dt/nova/nova04delta/edpm/nodeset/values.yaml`)
5557

58+
See [dataplane section](data-plane.md) for deployment instructions.
59+
There are most essential configuration values to define:
60+
5661
* `[pci]report_in_placement`: Required for PCI in placement to work.
5762
* `[pci]device_spec`: Whitelists the physical GPUs that are available for passthrough. You must create a `device_spec` entry for each physical GPU you want to make available. For example:
5863
```yaml

examples/dt/nova/nova04delta/data-plane.md

Lines changed: 38 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,27 +2,30 @@
22

33
## Assumptions
44

5-
- The [control plane](control-plane.md) has been created and successfully deployed
5+
- The [control plane](control-plane/README.md) has been created and successfully deployed
66

77
## Initialize
88

99
Switch to the "openstack" namespace
1010
```
1111
oc project openstack
1212
```
13-
Change to the nfv/sriov/edpm directory
13+
Change to the nova/nova04delta directory
1414
```
15-
cd architecture/examples/va/nfv/sriov/edpm
15+
cd architecture/examples/va/nova/nova04delta/edpm
1616
```
17-
Edit the [nodeset/values.yaml](nodeset/values.yaml) and [deployment/values.yaml](deployment/values.yaml) files to suit
17+
Edit the [nodeset/values.yaml](nodeset/values.yaml), [nodeset2/values.yaml](nodeset/values.yaml)
18+
and [deployment/values.yaml](deployment/values.yaml) files to suit
1819
your environment.
1920
```
2021
vi nodeset/values.yaml
22+
vi nodeset2/values.yaml
2123
vi deployment/values.yaml
2224
```
23-
Generate the dataplane nodeset CR.
25+
Generate the dataplane nodeset CRs.
2426
```
2527
kustomize build nodeset > dataplane-nodeset.yaml
28+
kustomize build nodeset2 > dataplane-nodeset2.yaml
2629
```
2730
Generate the dataplane deployment CR.
2831
```
@@ -33,6 +36,7 @@ kustomize build deployment > dataplane-deployment.yaml
3336
Create the nodeset CR
3437
```
3538
oc apply -f dataplane-nodeset.yaml
39+
oc apply -f dataplane-nodeset2.yaml
3640
```
3741
Wait for dataplane nodeset setup to finish
3842
```
@@ -48,3 +52,32 @@ Wait for dataplane deployment to finish
4852
```
4953
oc wait osdpns openstack-edpm --for condition=Ready --timeout=40m
5054
```
55+
56+
## Generate yamls necessary to finialize Nvidia GPU installation
57+
After the Nvidia drivers have been blacklisted on the EDPM nodes, the computes need
58+
to be rebooted. Below explains the necessary steps to apply a reboot on the necessary nodesets.
59+
60+
Change to the nova/nova04delta/edpm-post-driver directory
61+
```
62+
cd architecture/examples/dt/nova/nova04delta/edpm-post-driver/
63+
```
64+
Edit the [deployment/values.yaml](edpm-post-driver/deployment/values.yaml) files to suit
65+
your environment.
66+
```
67+
vi deployment/values.yaml
68+
```
69+
Generate the dataplane deployment CR.
70+
```
71+
kustomize build deployment > dataplane-post-driver-deployment.yaml
72+
```
73+
74+
## Create CRs to finalize GPU installation
75+
Start the deployment
76+
```
77+
oc apply -f dataplane-post-driver-deployment.yaml
78+
```
79+
80+
Wait for dataplane deployment to finish
81+
```
82+
oc wait osdpd edpm-deployment-post-driver --for condition=Ready --timeout=20m
83+
```

0 commit comments

Comments
 (0)