From ab36046d912e2282b2c13b1029568c4d5860fcb3 Mon Sep 17 00:00:00 2001
From: lavado <glavado@whitestack.com>
Date: Fri, 29 May 2020 01:09:06 +0200
Subject: [PATCH] Update README.md
---
magma/README.md | 34 ++++++++++++++++++++++------------
1 file changed, 22 insertions(+), 12 deletions(-)
diff --git a/magma/README.md b/magma/README.md
index f5f6d504..a2c1ad6f 100644
--- a/magma/README.md
+++ b/magma/README.md
@@ -34,20 +34,20 @@ This example requires a PNF, emulated with a VyOS router (image [here](http://os
## Verifying the services
1. Visit the Orc8r dashboard at the KNF's nginx-proxy svc IP, with https and credentials admin@magma.test / password1234, then check that your AGW has been registered successfully under the list of Gateways in this path: https://<orc8r-nginx-proxy-ip>/nms/osmnet/gateways) (after proxy charms are finished)
-2. Via this same dashboard, add the test subscriber with the following parameters (this will migrate to Day-2 primitive)
+2. Via this same dashboard, add check that a test subscriber has been added as Day-1 primitive, with these parameters:
- IMSI: 722070000000008
- KEY: c8eba87c1074edd06885cb0486718341
- OPC: 17b6c0157895bcaa1efc1cef55033f5f
-3. The emulator is ready to connect, Day-2 primitives for this is WIP, in the meantime, the following commands can be used to connect the eNB and UE, respectively and in that order (from different terminals)
+3. The emulator is ready to connect, Day-2 primitives are available for this:
-### Configuring eNodeB example
+### eNodeB register Day-2
-`srsenb --enb.name=dummyENB01 --enb.mcc=901 --enb.mnc=70 --enb.mme_addr=192.168.100.254 --enb.gtp_bind_addr=192.168.100.10 --enb.s1c_bind_addr=192.168.100.10 --enb_files.rr_config=/config/rr.conf --enb_files.sib_config=/config/sib.conf --enb_files.drb_config=/config/drb.conf /config/enb.conf.fauxrf`
+`osm ns-action magma_slice.slice_hackfest_nsd_epc --vnf_name 1 --vdu_id srsLTE-vdu --action_name register --params '{mme-addr: "192.168.100.254", gtp-bind-addr: "192.168.100.10", s1c-bind-addr: "192.168.100.10"}'`
-### Attaching UE example
+### UE attach Day-2
-`sudo srsue --usim.imsi=722070000000008 --usim.k=c8eba87c1074edd06885cb0486718341 --usim.algo=milenage --usim.opc=17b6c0157895bcaa1efc1cef55033f5f --nas.apn=oai.ipv4 /config/ue.conf.fauxrf`
+`osm ns-action magma_slice.slice_hackfest_nsd_epc --vnf_name 1 --vdu_id srsLTE-vdu --action_name attach-ue --params '{usim-imsi: "722070000000008", usim-k: "c8eba87c1074edd06885cb0486718341", usim-opc: "17b6c0157895bcaa1efc1cef55033f5f"}'`
## Testing traffic
@@ -63,6 +63,16 @@ With this, the UE machine will have access to Internet through the AGW and then
## Additional tests
+### Web Proxy service
+
+A Web Proxy is available via a KNF with primitives, implemented with Squid through juju-bundles mechanism.
+
+Deploy this NS:
+`osm ns-create --ns_name webcache --nsd_name squid-cnf-ns --vim_account <vim_account> --config '{vld: [ {name: mgmtnet, vim-network-name: osm-ext} ]}'`
+
+The UE's browser can be now configured to navigate with this proxy service.
+TODO: add how to test this service and run primitives to allow URLs.
+
### Network Slicing
- Additional slice instances can be launched (changing agw_id and agw_name), and we should see that just the AGW+emulator NS is launched (Orc8r NS is shared)
@@ -77,16 +87,16 @@ A second slice, reusing the same Orc8r, can be launched at different VIM. The pr
1. Copy the files to the placement folder at PLA:
`docker cp vnf_price_list.yaml $(docker ps -qf name=osm_pla):/placement/.`
`docker cp pil_price_list.yaml $(docker ps -qf name=osm_pla):/placement/.`
-1. Uncomment the placement-engine line and launch as usual! you should see the second slice being instantiated in the second VIM (WIP: Failing due to "NoWimConnectedToDatacenters" error)
+1. Uncomment the placement-engine line and launch as usual! you should see the AGW/srsLTE/PNF subnet being instantiated in the second VIM.
### Metrics collection
VIM-level metrics are being collected by default, they can be observed at the Grafana dashboard (possible bug at the ns_id variable, under review)
+### Auto-scaling
+
+Magma AGW VDU is configured for autoscaling when CPU exceeds a threshold. After scaling, services are not automatically balanced (WIP)
+
## Pending additions
-- Fix placement and test multi-tenancy
-- Navigating from a desktop browser (VNC not working properly)
-- Automatic and manual scaling
-- KNF Primitives (via additional Webhost NS that will be added)
-- SDN Assist in the internal S1 VLD
+- SDN Assist in the internal S1 VLD (Bug 1082)
\ No newline at end of file
--
GitLab