[lte] Add per-APN static IP configuration to subscribers on API

[xjtian]

Signed-off-by: Jacky Tian xjtian@fb.com

Summary

• Add the capability to assign APN-specific static IPs to subscribers
• This introduces a new config field on the subscriber entity which encapsulates the LteSubscription and the static IP config.
• To maintain backwards compatibility with API clients, the lte field is still on the subscriber entity on the read side (GET). On the write side, we add the static IP configuration as a top-level field to the MutableSubscriber.
• Because this changes the network entity in configurator, a data migration is also included.

Test Plan

• New unit tests for API handlers
• Ran locally; API errored out before migration, worked after migration. Also tested migration script on dump of staging DB.
• Tested and verified subscriber streaming on local AGW:

vagrant@magma-dev:~$ subscriber_cli.py get IMSI208950000000012
sid {
  id: "208950000000012"
}
lte {
  state: ACTIVE
  auth_key: "\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000"
  auth_opc: "\000\001\002\003\004\005\006\007\010\t\n\013\014\r\016\017"
}
network_id {
  id: "test"
}
state {
}
sub_profile: "default"
non_3gpp {
  apn_config {
    service_selection: "inet"
    qos_profile {
      class_id: 9
      priority_level: 15
      preemption_capability: true
    }
    ambr {
      max_bandwidth_ul: 10000000
      max_bandwidth_dl: 20000000
    }
    assigned_static_ip: "192.168.100.1"
  }
}

Additional Information

• This change is backwards-breaking

After deploying orc8r, kubectl exec into any controller pod, then:

$ cd /var/opt/magma/bin
$ envdir /var/opt/magma/envdir ./m011_subscriber_config

[hcgatewood]

I think this is a good pattern to include the data migration with the relevant breaking changes

[hcgatewood]

Couple small things

[hcgatewood]

recovered -> Recovered

[hcgatewood]

I like this pattern of having just a single doMigration in main's ExecInTx -- easier to follow the logic