Joining in here. From the artifacts page [1], I see that Apex is released as
an ISO. Only JOID does not produce an ISO.
For the TripleO RPMs, they are built on the OPNFV CentOS slaves, so there is
nothing proprietary there. RPM is the upstream format for the TripleO project
if I understand
Hi Ray,
I just give one of these links, and there are many records about this. I
don't remember the exact record about this for discussed years ago.
In our CI system, we use source code or ISO to deploy the environment from
installer and then perform the tests. I don't think there are changes
Julien,
Based on the minutes, it says Arno will support iso and script based
deployment, but too early to decide on packaging options for future
releases (incl. Brahmaputra).
I'm not sure if I understand your concerns on RPMs from Apex. Could you
elaborate further?
Thanks,
Ray
On Mon, May 8,
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
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
