COMAC-170 Use common patterns in values and manifests in mcord-services
This patchset is a part of mcord-services refactoring.
1. Group values by images, nodeSelectors, resources, configs and networks.
2. Make StatefulSets have common patterns for label, resources, and nodeSelectors
3. Use fixed resource name to reduce complexities
4. Don't set namespace as a value, use the one passed with helm install
5. Use common cniPlugin and ipam for SGI and S1U networks
6. Use camel case for value names
7. Do not support old mme anymore
8. Use official omecproject repo for default images
Change-Id: I9654993c8885f12cebb1a93517119556a90127d6
diff --git a/mcord-release/mcord-services/templates/NOTES.txt b/mcord-release/mcord-services/templates/NOTES.txt
index b7a49b5..a5a7136 100644
--- a/mcord-release/mcord-services/templates/NOTES.txt
+++ b/mcord-release/mcord-services/templates/NOTES.txt
@@ -17,16 +17,12 @@
This is the instruction to configure your eNodeB to work with ONF M-CORD. You can find architecture illustration in assets/mcord-architecture.png.
-1. Check the eNodeB is operating in following information:
- eNodeB Address: {{ .Values.enb.host }}
- eNodeB S1 port: {{ .Values.enb.port }}
-
-2. Configure eNodeB with the correct MME information, get MME IP by following commands:
- export MMEIP=$(kubectl get --namespace {{ .Release.Namespace }} -o jsonpath="{.status.podIP}" pods mme-0
+1. Configure eNodeB with the correct MME information.
+ export MMEIP=[node IP]
export MMEPORT="36412"
- MMEPORT is fixed in templates/mme.yaml.
+ You can change MMEPORT by overriding "Values.config.mme.s1ap.sctp_port_external".
-3. Make sure UE's SIM card information is configured in hss.yaml.
+2. Make sure UE's SIM card information is configured in hss.yaml.
-4. Attach UE to M-CORD.
+3. Attach UE to OMEC.