Comments (5)
A version of the current development AS with the v17.3.0 changes applied is available on the "feature/uplift-to-ts26-512-v17-3-0" branch in my forks of rt-common-shared and rt-5gms-application-server.
I'm currently working on a fix for the configuration of multiple provisioning sessions in NGINX and modifications to fix the uri
vs uri-reference
issue found in the specs.
from rt-5gms-application-server.
Reworked the "feature/uplift-to-ts26-512-v17-3-0" branches in the forked repositories with the suggested "Draft v17.4.0" versions from 5G-MAG/Standards#36. Moved examples out of the rt-common-shared repository and split them between the Application Function and Application Server. The rt-5gms-application-server now contains a tests/examples
directory containing suitable test files for the M3 test client. The rt-5gms-application-function will follow when I've pulled together the relevant updates from @devbbc to create a "feature/uplift-to-ts26-512-v17-3-0" there too.
from rt-5gms-application-server.
The Change Requests for TS 26.512 were approved at SA#98-e last week. Publication of V17.3.0 will follow soon.
(Full details on the seven issues linked from the Context section in the main issue description above.)
from rt-5gms-application-server.
I've now reworked the NGINX configuration writing to group distribution configurations appropriately. I've also tested this with two provisioning sessions at once. Each provisioning session had a Content Hosting Configuration which requested both HTTP and HTTPS distributions. The configuration written out groups the two HTTP distribution configurations under the same "server" configuration so that the port 80 server can serve all configured url prefixes (obtained from distributionConfigurations.baseURL
). Because the SSL configurations have different certificates, they are written out as two separate "server" sections. This does present a problem if two provisioning sessions both only use the canonicalDomainName
as the first one in the configuration will be picked to provide its certificate and URL path prefix. This situation is going to need some more thought as the current solution is not ideal. Using different canonicalDomainName
s for each provisioning session, or insisting that AP's use domainNameAlias
may be a solution here.
I'd like to do a little more testing before posting the PR as I've only done a few basic tests so far, but I think this is feature complete now.
from rt-5gms-application-server.
To address the above problem, we could limit our reference implementation according to one of the following limitations:
- The 5GMS AF rejects distribution configurations referencing a certificate without a domain name alias.
- The 5GMS AF rejects a distribution configuration for a previously seen domain name (canonical or alias) but referencing a different server certificate.
A more elegant solution for distribution configurations not using a host name alias is for the 5GMS AF to allocate a unique canonical 5GMS AS domain name for each such distribution configuration. However, this requires either dynamic DNS updates by the 5GMS AF or else selection of canonical names from a pool of pre-registered DNS names.
from rt-5gms-application-server.
Related Issues (20)
- Use OpenAPI to bindings script from 5G-MAG/rt-common-shared repository. HOT 3
- MVP#1 Application Server installation issues/observations HOT 21
- asyncio.create_task(..., name=...) doesn't work with Python 3.7 HOT 1
- Error, following the build instructions HOT 5
- Application Server crash on certificate upload HOT 3
- Incorrect error response status code for M1_ContentHostingProvisioning_purgeContentHostingCache operation HOT 3
- Documentation updates after review on 23 Jan 2023 HOT 5
- Enhancement: Return number of cache entries purged in M3 response
- MVP#2 Application Server installation/running issues/observations HOT 11
- CI/CD - Automated deployment of 5GMS AS to Linode instance HOT 1
- Implement Server Health Check endpoint
- Uplift to TS 26.512 v17.4.0: Update M3 interface with new ContentHostingConfiguration structure HOT 1
- Feature: Media Streaming Data Reporting at reference point R4 HOT 1
- 5gms-application-server reports `Path parameters cannot have a default value` HOT 3
- Upstream redirects are passed to client HOT 9
- Redirection fails with recent OpenResty version HOT 1
- change in pydantic v2 HOT 3
- Development branch: Missing Nginx mime.types after clean installation HOT 2
- Updating PATH for launching Openresty HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rt-5gms-application-server.