verizon/5gedgetutorials

Verizon 5G Edge Demos & Tutorials

Tutorials, starter guides, and simple projects to launch your first application at the network edge.

Brought to you by the Verizon 5G Edge Developer Relations Team

What is 5G Edge? Verizon 5G Edge brings the power of the cloud closer to mobile and connected devices at the edge of the Verizon 4G and 5G networks. That means developers can build apps with low latency using familiar cloud services, APIs and tools via seamless extension of your Virtual Private Cloud.

To learn more, check out the Verizon 5G Edge Developer Resources page.

Table of Contents

• Background
• Install
• Usage
• Contribute
• License

Background

We want to make it easier than ever to develop applications for the network edge. To that end, we've created a number of starter projects, tutorials, and infrastructure templates that get your Verizon 5G Edge infrastructure up-and-running in seconds. From there, feel free to experiment with some of the starter applications we've developed, including the following:

Infrastructure Resources

• terraform: Get started using HashiCorp Terraform across HAProxy, MongoDB, and AWS Wavelength (EC2/EKS)
• cdk-tutorials: Use the AWS CDK to create starter modules using AWS Wavelength
• cloudformation-templates: Use AWS CloudFormation to launch your first 5G Edge infrastructure template
• sdk-tutorials: Get started using Boto3 (Python SDK for AWS) across EC2 or EKS
• edge-discovery: Get started with the Verizon edge discovery service, an easy-to-use API to manage multi-Wavelength zone deployments and route mobile clients to the most optimal edge endpoints

Partner Resources

• confluent: Build your first data streaming application using Confluent for Kubernetes on AWS Wavelength
• couchbase: Build your first auction application on AWS Wavelength with Couchbase Server and Sync Gateway
• openshift: Deploying your first OpenShift cluster to AWS Wavelength
• sumologic: Instrument your first EC2-based edge deployment using Sumo Logic custom collectors
• opscruise: Instrument your first EKS environment using OpsCruise

Community Resources

There are a bunch of awesome projects building on Verizon 5G Edge that we wanted to highlight here as well!

• kukicado/vz-immersion-day-demo: Olympics-themed computer vision app on AWS Wavelength with MongoDB
• newrelic-experimental/vz-newrelic-5g-edge: Instrumenting your EKS cluster with Pixie and New Relic
• aws-samples/aws-mqtt-wavelength-latency: Wavelength MQTT latency tester
• VKonanur/MongoDB-Realm-for-Verizon-5G-Edge/: MongoDB Realm on AWS Wavelength
• AWS Lab (Machine Learning): Object detection using AWS Wavelength
• AWS Lab (Video Streaming): WebRTC on AWS Wavelength
• Couchbase Lab (Infrastructure): Couchbase on AWS Wavelength Demo
• HarperDB/hdb-deploy-aws-wavelength-ec2-cloudformation: HarperDB 3.1.3 nodes on AWS Wavelength

5G Edge Resources

• 5G Edge Blog on Medium: Check out the latest tutorials and customer success stories
• 5G Edge Training: Learn more about EC2 on AWS Wavelength or Containers on AWS Wavelength

Contribute

Please refer to the contributing.md file for information about how to get involved. We welcome issues, questions, and pull requests.

Maintainers

• Robbie Belson: [email protected]

License

• This project is licensed under the terms of the Apache 2.0 open source license. Please refer to LICENSE for the full terms.

5gedgetutorials's Issues

Error running createServiceRegistry() example in EDS guide

Following the instructions in https://github.com/Verizon/5GEdgeTutorials/blob/main/edge-discovery/README.md is successful until the createServiceRegistry() call in Step 2, which returns the following error:

TypeError: createServiceRegistry() missing 1 required positional argument: 'fqdns'.

Any guidance would be appreciated. Thank you.

EKS worker nodes not joining the EKS Cluster

Goal:
I am trying to launch EKS cluster on wavelength.

Issue Description
After creating the cloudformation stack using the template, the worker nodes aren't joining to the created eks stack. I also verified on the aws dashboard that eks cluster didn't have any nodes attached to it and it seemed to have all required permissions.

Reproducing the error:
I launched the cloudformation template using the cli command provided in the readme and was able to successfuly create the cloudformation stacks.

aws cloudformation create-stack \
--stack-name myWavelengthStack \
--template-body <selected-cfn-file> \
--parameters ParameterKey=EnvironmentName,ParameterValue=WavelengthCloudFormation \
--capabilities CAPABILITY_NAMED_IAM

The small modifications I made to the template was to change

1. Wavelength zone geo to default to us-west-2-wl1-sfo-wlz-1
2. ParentRegion(1/2)Geo default to us-west-2a/b

I then got the kubeconfig context

aws eks update-kubeconfig --name {my_cluster_name} --kubeconfig <local file>

Then using the aws-auth-cm.yml setup in README, I was able to apply the configmap to the cluster.

At this point, I am able to reach the cluster and the aws-auth config map is applied

$ kubectl get configmaps -n kube-system
NAME                                 DATA   AGE
aws-auth                             1      11h
coredns                              1      12h
cp-vpc-resource-controller           0      12h
eks-certificates-controller          0      12h
extension-apiserver-authentication   6      12h
kube-proxy                           1      12h
kube-proxy-config                    1      12h

Querying the events provides failed scheduling due to no nodes

$ kubectl get events --all-namespaces 
NAMESPACE     LAST SEEN   TYPE      REASON             OBJECT                                            MESSAGE
kube-system   2m40s       Warning   FailedScheduling   pod/coredns-5946c5d67c-p9mf8                      no nodes available to schedule pods
kube-system   2m40s       Warning   FailedScheduling   pod/coredns-5946c5d67c-zlrxw                      no nodes available to schedule pods

With no nodes returning:

$ kubectl get nodes
No resources found in default namespace.

As a side note, I am able to launch regular eks instances using eksctl.

The README does mention attaching carrier ips, but I'm not sure how/why this needs to be done and if this is the issue. If this is the issue, is there a way to do it automatically?

For Public Cluster, ECR/EC2 endpoints are Optional but you must manually attach Carrier IP to public-facing instaces

I was also debugging with https://aws.amazon.com/premiumsupport/knowledge-center/eks-worker-nodes-cluster/ and did notice the eks subnets did not have a wavelength zone. I'm not sure if this could be the issue.