Hi David, This issue has been discussed in the TSC meeting. I don't know this conclusion about *"Packaging is a community decision made by the installer teams and the dependent scenario owners and project teams"* is approved by TSC. I just remember ISO and source code are two alternatives. *"In particular, RPM is standard for Red Hat OSs"* If it is RHEL, it is licensed and not suitable. In OPNFV, we only use community version, ie. CentOS. If we release RPMs in Cent OS, shall we release deb packages for Ubuntu OS?
I'm sorry that I can not go to openstack summit. There are some records in TSC meeting such as July 14th, 2015, and original link is: http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-07-14-14.00.html . Regards, Julien David McBride <dmcbr...@linuxfoundation.org>于2017年5月8日周一 下午11:38写道： > Hi Julien, > > "Apex" is the project name for TripleO in OPNFV. However, "TripleO" is > the name of the installer. Also, "TripleO" is well known outside of OPNFV, > whereas "Apex" is unique to OPNFV. > > Packaging is a community decision made by the installer teams and the > dependent scenario owners and project teams. So far, I've never heard any > complaints from members or end users about packaging. However, this topic > might be worth bringing up at the EUAG in case there are some issues that > I'm unaware of. > > I think that having packaging for each installer that is appropriate and > has community/user consensus is more important than forcing the same > packaging across all installers (i.e. "consistency is the hobgoblin of > little minds"). In particular, RPM is standard for Red Hat OSs, therefore, > it makes sense that TripleO would be released on RPM. > > If you are at OpenStack this week, I'd be happy to discuss this with you > further F2F. > > David > > On Sat, May 6, 2017 at 4:37 AM, Julien <julien...@gmail.com> wrote: > >> Hi David, >> >> In our installer projects, there are Apex, Compass, Fuel, and Juju >> released in Danube. I wonder why use the name TripleO instead of Apex? >> >> I have discussed at Arno and Brahmaputra about how to release OPNFV >> artifacts, and the conclusion is in ISO or source codes. Why release RPMs >> for Apex? It is different from other installers. The release content or >> list are different in OPNV download page. It is really strange. >> >> BR, >> Julien >> >> >> David McBride <dmcbr...@linuxfoundation.org>于2017年5月6日周六 上午5:20写道： >> >>> TSC members, >>> >>> I'm pleased to let you know that OPNFV Danube 2.0 has been released. >>> Software and documentation may be accessed here >>> <https://www.opnfv.org/software/downloads>. >>> >>> Congratulations to everyone in the community that worked hard to make >>> this happen. Please let me know if you have questions or comments. >>> >>> David >>> >>> -- >>> *David McBride* >>> Release Manager, OPNFV >>> Mobile: +1.805.276.8018 >>> Email/Google Talk: dmcbr...@linuxfoundation.org >>> Skype: davidjmcbride1 >>> IRC: dmcbride >>> _______________________________________________ >>> opnfv-tech-discuss mailing list >>> opnfv-tech-discuss@lists.opnfv.org >>> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss >>> >> > > > -- > *David McBride* > Release Manager, OPNFV > Mobile: +1.805.276.8018 > Email/Google Talk: dmcbr...@linuxfoundation.org > Skype: davidjmcbride1 > IRC: dmcbride >
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
