Hi guys, As I mentioned during the last meeting, I am working towards installer support for Gluon in OPNFV. I believe it is highly beneficial for Gluon if we can make use of the CI and testing framework that OPNFV provides - in addition to the community building, of course. In this context, I have been in contact with Feng Pan from the Apex team.
The first step towards an OPNFV integration is to define a new deployment scenario for Gluon. This involves a couple of aspects I'd like to get your input on: * SDN controller: There are currently two major SDN controllers in OPNFV: ODL and ONOS. Based on our experience and competence, I propose to start with ODL. * Network Service: This one is simple as we only have the L3VPN service at the moment. * Layer: The current scenarios distinguish between l2 and l3. For Gluon, I'd like to refrain from prematurely restricting the deployed network service. Hence, I propose to leave out any reference to l2 or l3. * Installer: As I mentioned, the Apex team voiced interest in supporting this activity. * High-availability: We have not looked into high-availability aspects of Gluon yet. Hence, I propose to define a noha scenario first. In summary, given the OPNFV scenario naming conventions, a first Gluon scenario would be called os-odl-gluon-noha. Let know what you think. Best regards Georg _______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
