-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MSAF-Configuration tool: Move m8.json
output code to generic Python modules
#48
Comments
Based on the discussion on 09.08:
|
I've created the data model in the rt_media_configuration python module, now I have to add the output registration and synchronisation logic. If you want a sneak peek then you can look at the development branch in my fork. |
I've updated the model to fix a couple of issues and added most of the synchronisation code. I've split the synchronisation code into 2 parts instead of just one monolithic chuck of code which did these two operations one after another. The first part analyses the changes between the current model and what the AF currently has configured and passes back a list of delta operation objects describing the various changes needed. These delta operations can then be applied to synchronise the AF with the new model. This also gives the option for a UI to present the user with a readable list of changes for approval before the changes are committed. Once this part is complete then the rt_media_configuration python module should be in a suitable state for integration into the WebUI and m1-session tool to begin. I'll then continue to work on the background M8 publication parts that go along with the synchronisation operation. |
@stojkovicv This is now in a state that is ready for checking and starting the integration into the WebUI |
New model now merged by PR #51, this just leaves the updates to the m1-session command line tool and the WebUI. |
Introduction
At present the
msaf-configuration
Python command-line tool is the only part of this repository that can publish the data that will be retrieved by the 5GMS Aware App via the M8 interface to the Application Provider. It is desirable for all tools in this repository to be able to publish data, for retrieval via M8, when the Application Providers' media model changes. This will require other tools such as the WebUI and m1-session tool to be able to publish M8 data files too.This issue tracks the work to separate the M8 data publication from the
msaf-configuration
tool into a set of reusable Python classes. Other issues will cover the integration of these new classes into the other existing tools (i.e. at this time that would be the WebUI andm1-session
tool).This is based on the discussion in discussion thread #43.
Description
After this work
msaf-configuration
will just be a command line interface to the classes in the rt_media_configuration Python module.To be done:
msaf-configuration
.dump_m8_files().msaf-configuration
into the MediaConfiguration class so that they will synchronise the model with the AF configuration by using rt_m1-client.M1Session and make this operation triggered by calling a sychronise() method.streams.json
file and move the logic for this frommsaf-configuration
.msaf-configuration
to use the new importers, formatters and model based on its configuration file.The text was updated successfully, but these errors were encountered: