Hi Luis,

I really don't mean to throw a wrench in the idea and I believe what I am going to say won't impact the folder structure.. However, while karaf is currently a "distribution" it's more than that and I have sacrificed ODL functionalities to do the current port (such as Shell commands, some specific patches, etc.) a proper "port to karaf" implies changes to code.. and we can leverage it in Pax Exam to test the bundle configurations with the different components. 

What I'm trying to say is karaf is more a way to assemble your distributions than a distribution on its own.. right now I am doing it this way to minimize impact for the rest of the community...

If you have any questions feel free to get in touch.. once I am done with the features I'll help on the pax exam tests..

Cheers

Mathieu 

On Thu, May 1, 2014 at 3:15 PM, Raghurama Bhat (ragbhat) <ragbhat@...> wrote:

+1

‹Raghu

On 5/1/14, 12:07 PM, "Thomas Nadeau" <tnadeau@...> wrote:

>This seems reasonable to me.
>
>On May 1, 2014:3:02 PM, at 3:02 PM, Luis Gomez <ecelgp@...> wrote:
>
>> Hi all,
>>
>> After TSC call today, here is my proposal on how to handle unsupported
>>distributions in the integration repo.
>>
>> This is what we have today for official distributions:
>>
>> /distributions/base
>> /distributions/serviceprovider
>> /distributions/virtualization
>>
>> And I think all will be easier if we can just add an ³extra² folder in
>>distributions to host non-official/non-supported distros:
>>
>> /distributions/base
>> /distributions/serviceprovider
>> /distributions/virtualization
>> /distributions/extra/karaff
>> /distributions/extra/toaster
>>
>> Comments on this proposal:
>>
>> 1) Placing new distros in /distributions folder allows us to use
>>existing verify-distributions and merge-distributions jobs to build the
>>distros upon change in the composition and run full test suite to verify
>>any change here does not impact anything.
>>
>> 2) The new editions will be built at the same time at the official
>>editions, this is when we see changes in project repos. After the build
>>we can trigger or not specific tests for the new editions.
>>
>> 3) Regarding the proposal of using folders to separate main releases

>>like Hydrogen, Helium, etcŠ I do not think this is really needed as we

>>have stable branches, meaning that Hydrogen distros will be under
>>/distributions in stable/hydrogen branch, Helium distros are now under
>>/distributions in master and will be under /distributions in
>>stable/helium after helium release, and so on. Also, one thing we can do
>>when we create stable branches is to remove the extra folder as I do not
>>think extra distros are needed for stable.
>>
>> 4) I really would like to see a folder in Nexus for ³extra" so we do
>>not get confused with official there as well.
>>
>> 5) Finally, we will be addressing to TSC any change in official
>>editions or any proposal to move a distro from extra to official.
>>
>> Please feel free to comment on this proposal.
>>
>> BR/Luis
>>
>> _______________________________________________
>> Discuss mailing list
>> Discuss@...
>> https://lists.opendaylight.org/mailman/listinfo/discuss
>>
>

_______________________________________________
Discuss mailing list
Discuss@...
https://lists.opendaylight.org/mailman/listinfo/discuss

--


Mathieu Lemay

President & CEO

Inocybe Technologies
1-888-445-7505
www.inocybe.ca

_______________________________________________
Discuss mailing list
Discuss@...
https://lists.opendaylight.org/mailman/listinfo/discuss