[opendove-dev] External apps packaging
|
Ryan Moats <rmoats@...>
That might be a little difficult as the external apps for OpenDove aren't even intended to be run on the same appliance or physical host as the controller. Yes I agree, we have currently 3 projects with external apps: VTN, OpenDove and Defense4all (cc-ing them as well). It would be good to come up with a common or similar way of packaging these apps. Thanks/Luis -----Original Message-----
From: Ed Warnicke (eaw) [mailto:eaw@...] Sent: Tuesday, November 05, 2013 7:22 AM To: Luis Gomez Cc: Hideyuki Tai; integration-dev@...; vtn-dev@...; <opendove-dev@...> Subject: Re: [integration-dev] Please add VTN Coordinator to the Virtualization Edition Luis, VTN Coordinator is a part of the Virtualization Edition. It, like Defense4All, is an app that runs outside the controller. We should figure out how we want to package them. Here's one suggestion... we could put then in the zip file in opendaylight/externalapps/ as zip files themselves. We also need to figure out how to bring along OpenDove's external bits... Ed On Nov 4, 2013, at 11:21 PM, Luis Gomez <luis.gomez@...> wrote: > Hi Hideyuki, > > My understanding (Ed, correct me if I am wrong) is that, so far and for integration purposes, we are only packaging what is in the controller instance and NOT what is in the overall edition. For this last I heard a similar question very recently in the TSC call on how we are going to package the overall editions (not just the controller node), so your question is very valid and should get an answer very soon. > > Thanks/Luis > > > -----Original Message----- > From: integration-dev-bounces@... [mailto:integration-dev-bounces@...] On Behalf Of Hideyuki Tai > Sent: Monday, November 04, 2013 8:16 PM > To: integration-dev@... > Cc: vtn-dev@... > Subject: [integration-dev] Please add VTN Coordinator to the Virtualization Edition > > Hi all, > > The release deliverable of VTN Project consists of VTN Manager and VTN Coordinator. > Both of them will be included in the Virtualization Edition for Hydrogen. > => See page 21 of OpenDaylight Introduction slide: > http://www.opendaylight.org/resources/collateral > > The current artifacts for the Virtualization Edition, however, have not > included VTN Coordinator yet. > > Could you add VTN Coordinator to a zip file for the Virtualization Edition? > > I could find artifacts for the Virtualization Edition in the Nexus repository. > https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distributions-virtualization/0.1.0-SNAPSHOT/ > -> distributions-virtualization-0.1.0-20131025.213257-10-osgipackage.zip > They, however, do not include VTN Coordinator. > > The groupdId and artifactId of VTN Coordinator are as follows. > > <groupId>org.opendaylight.vtn</groupId> > <artifactId>distribution.vtn-coordinator</artifactId> > > > VTN Coordinator is an application of OpenDaylight Controllers. > It runs outside controllers, and orchestrates multiple Controllers > to provide multi-tenant virtual networks. > > We will prepare an installation procedure and prerequisites for VTN Coordinator. > > Regards, > Hideyuki Tai > > > _______________________________________________ > integration-dev mailing list > integration-dev@... > https://lists.opendaylight.org/mailman/listinfo/integration-dev > _______________________________________________ > integration-dev mailing list > integration-dev@... > https://lists.opendaylight.org/mailman/listinfo/integration-dev _______________________________________________ opendove-dev mailing list opendove-dev@... https://lists.opendaylight.org/mailman/listinfo/opendove-dev |
|
|
|
Luis Gomez <luis.gomez@...>
Hi Ryan, that’s precisely why we call them external apps. The question for you maybe is whether you would like to have OpenDove external apps included in the OpenDaylight release (like VTN people), or you are just fine with the controller based node (oDMC) being part of the OpenDaylight release, because maybe you already have other channels for OpenDove apps distribution. Same question applies to Defense4all.
BR/Luis
From: Ryan Moats [mailto:rmoats@...]
Sent: Tuesday, November 05, 2013 9:40 AM To: Luis Gomez Cc: <defense4all-dev@...>; Ed Warnicke (eaw); integration-dev@...; <opendove-dev@...>; opendove-dev-bounces@...; vtn-dev@... Subject: Re: [opendove-dev] External apps packaging
That might be a little difficult as the external apps for OpenDove aren't even intended to be run on the same appliance or physical host as the controller.
|
|
|
Luis Gomez ---11/05/2013 11:36:19 AM---Yes I agree, we have currently 3 projects with external apps: VTN, OpenDove and Defense4all (cc-ing