Installing the EDA application
After setting up Kubernetes on the VMs, you can now install Nokia EDA using the playground.
Customizing the installation file
Update the settings for the parameters in the prefs.mk file to control the way EDA is installed.
Parameter | Description |
---|---|
NO_KIND
|
Specifies not to deploy the lab KIND node. Must be set to
|
METALLB_VIP |
Specifies the VIP of your EDA deployment. This must be set to the
Virtual IP matching your EXT_DOMAIN_NAME FQDN (or IP).
Make sure to use a CIDR format, preferably a as a /32 (or /128 for an
IPv6 VIP). Example: |
EXT_DOMAIN_NAME
|
The FQDN that resolves to the EDA VIP or the VIP itself. |
EXT_HTTP_PORT
|
The HTTP port that the EDA UI/API should use to redirect to HTTPS.
Set to 80. |
EXT_HTTPS_PORT
|
The HTTPS port on which the EDA UI/API listens. Set to 443. |
EXT_IPV4_ADDR
|
The IPv4 IP address used as the VIP. |
EXT_IPV6_ADDR
|
The IPv6 IP address used as the VIP. |
HTTPS_PROXY
|
Optional: The proxy address for the HTTPS proxy. |
HTTP_PROXY
|
Optional: The proxy address for the HTTP proxy. |
NO_PROXY
|
Optional: The list of IP addresses, IP ranges and hostnames that should not be proxied. |
https_proxy
|
Optional: The proxy address for the HTTPS proxy. |
http_proxy
|
Optional: The proxy address for the HTTP proxy. |
no_proxy
|
Optional: The list of IP addresses, IP ranges and hostnames that should not be proxied. |
LLM_API_KEY
|
Optional: The OpenAI API key for the LLM functionality. |
SINGLESTACK_SVCS
|
Optional: Indicates that internal services should be single stack
instead of dual stack, if Kubernetes is dual stack.
Boolean. |
SIMULATE |
Specifies if the EDA deployment is to manage simulated workloads
(Digital Sandbox) or real hardware. Values: true or
false . By default, this parameter is set to
|
KPT_SETTERS_FILE
|
Advanced configuration file for kpt. |
The prefs.mk file
NO_KIND=1
METALLB_VIP=192.0.2.10/32
EXT_DOMAIN_NAME=eda.domain.tld
EXT_HTTP_PORT=80
EXT_HTTPS_PORT=443
EXT_IPV4_ADDR=192.0.2.10
EXT_IPV6_ADDR=""
HTTPS_PROXY=http://192.0.2.254:8080
HTTP_PROXY=http://192.0.2.254:8080
NO_PROXY=192.0.2.0/24,203.0.113.0/24,.domain.tld,172.22.0.0/16,localhost,127.0.0.1,10.0.1.0/24,0.0.0.0,169.254.116.108
https_proxy=http://192.0.2.254:8080
http_proxy=http://192.0.2.254:8080
no_proxy=192.0.2.0/24,203.0.113.0/24,.domain.tld,172.22.0.0/16,localhost,127.0.0.1,10.0.1.0/24,0.0.0.0,169.254.116.108
LLM_API_KEY=...
Installing Nokia EDA
Follow these steps to install EDA.
-
Download the latest tools.
make download-tools
-
Download the latest packages, including the eda-kpt package.
make download-pkgs
-
Set up the MetalLB environment for VIP management.
make metallb
-
Install the necessary external packages.
make install-external-packages
Note: If this command exits with an error, wait 30 seconds and try again. Sometimes Kubernetes is a bit slower in reconciling the change than the command waits for. -
Change the eda-git Kubernetes service to a ClusterIP service instead of
a LoadBalancer type.
kubectl -n default patch service eda-git -p '{"spec": {"type": "ClusterIP"}}'
-
Generate the EDA core configuration.
make eda-configure-core
-
Install EDA core components.
make eda-install-core
Note: If the command hangs for a long time (>5 minutes) on "reconcile pending" for a workflowdefinition, cancel the command and try again, KPT is designed to handle these cases. This can occasionally happen depending on the Kubernetes cluster -
Verify that the EDA Config Engine is up and running.
make eda-is-core-ready
-
Install all the standard EDA apps.
This step can take approximate 5 to 15 minutes, depending on your connectivity.
make eda-install-apps
-
Bootstrap EDA.
make eda-bootstrap
- Optional:
Deploy an example topology.
make topology-load
Accessing the EDA deployment
You can now access the new EDA deployment using the following methods:
- use https://VIP
- if an FQDN is configured for the
EXT_DOMAIN_NAME
field, use https://FQDN