...
Since Openstack is in advanced stages (in Rocky release) of providing FPGA support (via Cyborg project), initial support in ONAP would support Openstack based cloud regions. K8S support will be added later.
FGPAs can be used in following ways:
...
Some points to note are:
- Grouping of various properities properties together is achieved by <N> in resource, trait and function keyword.
- Even though FPGA accelerators typically are PCIe cards, PCIe vendor ID/device ID and VFs are hidden. They don't need to be specified.
- Note that in above examples, only the FPGA accelerators are taken as an example.
...
- In reality, flavors will have other resources too.
ONAP design considerations
- Leverage HPA functionality added in Multi-Cloud, OOF and A&AI.
- Add new HPA feature called "FPGA-AFaaS-Acceleration"
- Have following HPA feature attributes:
- fpga_device. As per above examples, this attributes takes value "FPGA_INTEL_ARRIA10".
- fpga_AF_function: As per above examples, this attributes takes values such as IPSEC_ACCELERATION_AF, TENSORFLOW_ACCELERATION_AF, PUBLIC_CRYPTO_ACCELERATION_AF or COMPRESSION_ACCELERATION_AF
- fpga_AF_count: This holds the number of AFs supported by the site for each workload
Changes in R4:
| Component | Changes |
|---|---|
| OOF |
|
| A&AI |
|
| Multi-Cloud |
|