(bcc'd to onap-tsc)
This is an FYI of a new locked branch which has been created. Issue Raised by the Community: The Integration Team raised the need for a method of ensuring a deployment of ONAP Beijing can be 100% reproducible. Summary: In order to have reproducible deployments, modifications are required for the HEAT and OOM deployments to use the "2.0.0-ONAP" tag instead of the Beijing branch for the gerrit clone operations. Some ONAP images are built using out dated versions of git which do not support passing the tag name as a parameter to the “git clone -b” command. Trying to fix this in the project code will require releasing new artifacts, which is unacceptable at this timeframe. In addition, if/when code does get updated, a reproducible deployment against the Beijing branch itself then becomes a moving target for the end user because the Beijing branch changing. Action Taken: After consulting with some key members of the Community* to remedy this situation in the most expedient and non-disruptive fashion, an actual locked branch labeled “2.0.0-ONAP” has been created. This will allow all any existing deployment scripts to accept “2.0.0-ONAP” as the branch parameter, allowing for the reproducible installation and/or deployment of ONAP Beijing. Impact on the dev Community: Simply the introduction of a locked branch – all dev work is to continue on existing branches (Master or Beijing) as has been the plan. For OOM, & Integration- readthedocs updates are needed – work being coordinated by Gildas. Impact on the end user (installer) Consistent installations over time. * There were numerous messages exchanged with the LF today, along with a meeting I was asked to set up on the matter. It was not until a course of action was already well under way that I realized the entire email thread was backchannel. That oversight was mine. I should have noticed sooner and steered the email thread into one of the public mailing lists where it should have been discussed for visibility. My most sincere apologies for that. Please respond to this thread if you have any questions or concerns, or if you just want to shake your fist at me for failing to ensure that everyone was included. Best Regards, -kenny Kenny Paul, Technical Program Manager, The Linux Foundation [email protected], 510.766.5945 San Francisco Bay Area, Pacific Time Zone
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
