Migration of service models towards 10.0 reveals an issue with the introduction of a new grouping ('service-endpoint-project') since release 6.0. The fact that setting service-a-end container now requires two different builders from two different packages makes the transfert of service-a-end data from any rpc defining it to service-a-end container of service-list very difficult. As many manually mapping as rpc using it is necessary, what generates important code overhead which is totally useless.
Change 98860 shows an example of solution proposed to OpenROADM MSA community for yand models.
A correction in release 10.1 would be more than appreciated.

Waiting for 10.1 (or later) model version.

OpenROADM models have been available the 11th of January 2022 in the release 10.1, integrating our feedback on models in release 10.0 (removing from org-openroadm-common-service-types the grouping service-endpoint-project). Unfortunately, this new maintenance release also brings strong modifications in the org-openroadm-routing-constraints model, especially in the structure of constraints (removal of choice co-routing-or-general).
All TransportPCE implementation with regards to the management of constraints (service handler, interface with GNPy in PCE modules) nedd to be re-written.