canonical / charmed-magma

Charmed Magma is an open source private mobile network operated with Juju.

Magma is an open source 4G and 5G core network. Use it to operate your own private mobile network. Magma enables better connectivity by:

• Allowing operators to offer cellular service without vendor lock-in with a modern, open source core network.
• Enabling operators to manage their networks more efficiently with more automation, less downtime, better predictability, and more agility to add new services and applications.
• Enabling federation between existing MNOs and new infrastructure providers for expanding rural infrastructure.
• Allowing operators who are constrained with licensed spectrum to add capacity and reach by using Wi-Fi and CBRS.

To learn more about Magma, visit the official website.

Charmed Magma

Charmed Magma is a distribution of Magma published by Canonical built to work with Juju. It is the easiest way to operate Magma. It provides the simplest setup, integration and lifecycle management options.

• Works on all clouds: Charmed Magma is not opinionated about your choice of cloud. It can also run on your personnal computer.
• Integrations: Charmed Magma offers seamless integration between each component and with standard monitoring tools.
• Automation: Charmed Magma automates the initial setup and most operations.

Get started here

charmed-magma's Issues

AGW not checking into orchestrator.

Hi,
We have installed charmed magma orchestrator and AGW services on Openstack VMs with Ubuntu 20.04 OS, running behind proxies.

Orchestrator:
microk8s version = 1.23
AGW:
Version = 1.6.1

We are able to access NMS UI and all the AGW services are in active state. There are error logs in AGW services. Attached are the screenshots of same.

Even though orchestrator services come to "Active" and "Idle" state after installation, they tend to go to "maintenance" state after a day or so. They remain in that state. Even though same proxy values are used, not always same services go to "maintenance" state.

End points of orchestrator are accessible from AGW, we used telnet to check the same.

As part of debugging section of documentation, we ran few python scripts to confirm if every prerequisite is satisfied. When we executed "checkin_cli.py" script, we found out that gateway certificate and gateway key are missing. Restarting magma services didn't help in regenerating the certificate and key.

We tried checking AGW to orchestrator with correct hardware details. But it's not checking in and the status in NMS UI is "Bad".

Any help will be appreciated. Thanks in advance.