![]() Projects can then integrate these images respecting seccom requirements and hosted in the nexus. We must also build baseline images for java ( ) and python ( ). We shall maintain the java dependencies through the oparent project: Since Frankfurt we try to manage small repositories.so if you want to bring new tests, it has to be discussed with integration, but we may create a new repo if needed Integrators Packaging Other tests can be found in and other repositories Python tests leverage the python_onapsdk are located in the repo: For the moment the 3 main frameworks used are:Īll these tests are hosted in different places as some have been developed upstream, some by security team, some by integration team. If you want to create new tests, you can use any framework you want. The agenda is open, you may add a topic, do not be shy to ask for a quick starting tour and explain what you would liek to do. If you want to be involved, it is recommended to join the weekly meeting (Wednesday 1PM UTC see Integration Project. A basic knowledge of these tools is a good prerequisites. Code contributions are provided through a git/gerrit system. The official documentation is also a good source: Īll the bugs/tasks/Epics are tracked through a JIRA system. but it can be a bit misleading as everything is not maintained (Developing ONAP not updtaed since 2018) More generally the wiki is full of lots of resources: Developing ONAP. The main Integration page is a good first step, it references the documentation, repository, Q&A: Integration Project We develop test, deploy labs, setup CI/CD chains.so we need to get skills from different fields (dev/System/automation/.). ![]() ![]() The mission of the integration projects are very different. ![]() It will depend on what you want to do in ONAP. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |