InvariantUUID uniquely identifies the service. It is being generated when the service is first created, and it doesn’t change. UUID identifies the service version, and new UUID is being generated for every new major version of the service.
Example: Service A verison 1.0 InvariantUUID: badde3c7-ce03-4a63-b002-a0e8ad4d29dd UUID: e91aceb0-c609-4483-9cd7-2e92dea88c0a Service A verison 2.0 InvariantUUID: badde3c7-ce03-4a63-b002-a0e8ad4d29dd UUID: 3a2c3bb7-3beb-4617-b0be-614737f726df Service A version 3.0 InvariantUUID: badde3c7-ce03-4a63-b002-a0e8ad4d29dd UUID: 6d4cc346-f5bd-4449-9bfb-18835b4ef12f From: [email protected] [mailto:[email protected]] Sent: Monday, October 16, 2017 10:38 PM To: LANDO, MICHAEL <[email protected]>; SHADMI, DAVID <[email protected]> Cc: [email protected] Subject: Two UUIDs in metadata section of Service template, UUID and invariantUUID. Which one is the only identifier of this service template? Are they able to be modified during the life cycle of the package? Thanks a lot.
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
