Skip to content

Releases: world-federation-of-advertisers/cross-media-measurement

v0.5.9-rc1

23 Aug 17:29
edd9e3f
Compare
Choose a tag to compare
v0.5.9-rc1 Pre-release
Pre-release

Highlight

TODO

What's Changed

TODO

What's Changed

  • fix[edp-simulator]: Refuse Requisition with invalid EventGroup name by @SanjayVas in #1758
  • refactor[edp-simulator]: Consolidate logging of Requisition refusal by @SanjayVas in #1759
  • feat!: Update cross-media-measurement-api dep for Requisition.State.WITHDRAWN by @SanjayVas in #1746
  • feat: Enable CloudWatch Observability EKS add-on by @SanjayVas in #1763
  • feat: Increase chance of getting Event Groups from Reporting Server ListEventGroups by @tristanvuong2021 in #1762
  • fix: Update Kingdom's duchy id config to select fulfillingDuchyId for HMSS by @renjiezh in #1737
  • refactor: Move dp consistency to cmm. by @ple13 in #1771
  • feat: Fulfill hmss requisition via the share shuffle library. by @ple13 in #1748
  • build!: Update JVM build target to 11 by @tristanvuong2021 in #1766
  • fix: Rollback JVM target upgrade by @tristanvuong2021 in #1776
  • fix: Resolve k8s version mismatch in correctness test by @renjiezh in #1775
  • fix: Fix type_url for EncryptionPublicKey. by @renjiezh in #1774
  • fix: Fix Mill image name on aws. by @renjiezh in #1773

Full Changelog: v0.5.8...v0.5.9-rc1

v0.5.8

14 Aug 20:11
e2fe207
Compare
Choose a tag to compare

This is primarily a bugfix release to update the base Java image.

Highlights

What's Changed

  • test: Update confidence interval for integration tests. by @ple13 in #1742
  • feat: Extract Maven artifacts for CMMS public API by @SanjayVas in #1751
  • build: Update common-jvm dep for Java base image. by @SanjayVas in #1756

Full Changelog: v0.5.7...v0.5.8

v0.5.7

09 Aug 16:54
aabb17a
Compare
Choose a tag to compare

Issues Addressed

  • Existing computations may starve initialization of new computations. See #1637
  • Duchy mill writing output blob error should be transient. See #1644
  • Avoid failing Measurements at Duchy due to stale ComputationParticipant state. See #1663
  • Fix batch get metrics limit in reports service. See #1529
  • CreateEventGroup on v0.5.x fails with v0.4.x EventGroup message containing encrypted metadata. See #1705
  • Multiple Computations are claimed at the same time. See #1722
  • Retryable storage errors may be treated as non-retryable. See #1731

Highlights

  • Mill horizontal autoscaling. See #1697
    • This significantly reduces cost during low traffic periods.
  • More performance improvements for Report creation. See #1641
  • Improved Duchy fault tolerance.
  • The HMSS EDP client library is published as a Maven artifact See README.
  • Kingdom-less panel exchange is supported on Google Cloud. See the deployment guide.

Potentially Requiring Action

  • As part of the Mill horizontal autoscaling feature, the K8s Deployment objects for Mills are replaced with PodTemplate objects.
    • The PodTemplates are used by new MillJobScheduler Deployment to schedule Mill Jobs.
    • The MillJobScheduler Deployment needs some permissions on K8s resources in the same cluster using K8s RBAC. For the dev configuration, this consists of a new Role and RoleBinding.
    • Maximum concurrency for LLv2 and HMSS can be configured using the --llv2-maximum-concurrency and --hmss-maximum-concurrency options to the scheduler, respectively.
      • You will need to ensure that there are enough machine resources available at maximum concurrency. For example, ensuring that the cluster autoscaler has a sufficiently high value for the maximum number of nodes.
    • The value of the --work-lock-duration option for the Mill PodTemplate must match the corresponding option for the scheduler Deployment.
      • --llv2-work-lock-duration or --hmss-work-lock-duration, depending on the Mill type.
  • Kubernetes object configuration changes for HMSS. Some of these are required even if HMSS is not enabled. See the updated deployment guides for GKE and EKS.
    • There is a new HMSS Mill.
    • The Kingdom internal API and public API servers have a new required --hmss-protocol-config-config option. In the dev configuration, this comes from the hmss_protocol_config_config.textproto file in the certs-and-configs Secret.
    • The Herald now needs access to blob storage. This means it needs to run under a K8s ServiceAccount that has access to the appropriate bucket, as well as the appropriate command line options.
    • The Herald and the HMSS Mill have a new --key-encryption-key-file option for worker (non-aggregator) Duchies. In the dev configuration, this comes from the certs-and-configs Secret.
    • The Duchy Requisition fulfillment server may need more heap space to handle HMSS Requisitions.
    • The EDP simulator may need more heap space to fulfill HMSS Requisitions.

What's Changed

Read more

v0.5.7-rc4

08 Aug 19:51
aabb17a
Compare
Choose a tag to compare
v0.5.7-rc4 Pre-release
Pre-release

Issues Addressed

  • Existing computations may starve initialization of new computations. See #1637
  • Duchy mill writing output blob error should be transient. See #1644
  • Avoid failing Measurements at Duchy due to stale ComputationParticipant state. See #1663
  • Fix batch get metrics limit in reports service. See #1529
  • CreateEventGroup on v0.5.x fails with v0.4.x EventGroup message containing encrypted metadata. See #1705
  • Multiple Computations are claimed at the same time. See #1722
  • Retryable storage errors may be treated as non-retryable. See #1731

Highlights

  • Mill horizontal autoscaling. See #1697
    • This significantly reduces cost during low traffic periods.
  • More performance improvements for Report creation. See #1641
  • Improved Duchy fault tolerance.
  • The HMSS EDP client library is published as a Maven artifact See README.
  • Kingdom-less panel exchange is supported on Google Cloud. See the deployment guide.

Potentially Requiring Action

  • As part of the Mill horizontal autoscaling feature, the K8s Deployment objects for Mills are replaced with PodTemplate objects.
    • The PodTemplates are used by new MillJobScheduler Deployment to schedule Mill Jobs.
    • The MillJobScheduler Deployment needs some permissions on K8s resources in the same cluster using K8s RBAC. For the dev configuration, this consists of a new Role and RoleBinding.
    • Maximum concurrency for LLv2 and HMSS can be configured using the --llv2-maximum-concurrency and --hmss-maximum-concurrency options to the scheduler, respectively.
      • You will need to ensure that there are enough machine resources available at maximum concurrency. For example, ensuring that the cluster autoscaler has a sufficiently high value for the maximum number of nodes.
    • The value of the --work-lock-duration option for the Mill PodTemplate must match the corresponding option for the scheduler Deployment.
      • --llv2-work-lock-duration or --hmss-work-lock-duration, depending on the Mill type.
  • Kubernetes object configuration changes for HMSS. Some of these are required even if HMSS is not enabled. See the updated deployment guides for GKE and EKS.
    • There is a new HMSS Mill.
    • The Kingdom internal API and public API servers have a new required --hmss-protocol-config-config option. In the dev configuration, this comes from the hmss_protocol_config_config.textproto file in the certs-and-configs Secret.
    • The Herald now needs access to blob storage. This means it needs to run under a K8s ServiceAccount that has access to the appropriate bucket, as well as the appropriate command line options.
    • The Herald and the HMSS Mill have a new --key-encryption-key-file option for worker (non-aggregator) Duchies. In the dev configuration, this comes from the certs-and-configs Secret.
    • The Duchy Requisition fulfillment server may need more heap space to handle HMSS Requisitions.
    • The EDP simulator may need more heap space to fulfill HMSS Requisitions.

What's Changed

Read more

v0.5.7-rc3

06 Aug 21:09
28bda6a
Compare
Choose a tag to compare
v0.5.7-rc3 Pre-release
Pre-release

Issues Addressed

  • Existing computations may starve initialization of new computations. See #1637
  • Duchy mill writing output blob error should be transient. See #1644
  • Avoid failing Measurements at Duchy due to stale ComputationParticipant state. See #1663
  • Fix batch get metrics limit in reports service. See #1529
  • CreateEventGroup on v0.5.x fails with v0.4.x EventGroup message containing encrypted metadata. See #1705
  • Multiple Computations are claimed at the same time. See #1722
  • Retryable storage errors may be treated as non-retryable. See #1731

Highlights

  • Mill horizontal autoscaling. See #1697
    • This significantly reduces cost during low traffic periods.
  • More performance improvements for Report creation. See #1641
  • Improved Duchy fault tolerance.
  • The HMSS EDP client library is published as a Maven artifact See README.
  • Kingdom-less panel exchange is supported on Google Cloud. See the deployment guide.

Potentially Requiring Action

  • As part of the Mill horizontal autoscaling feature, the K8s Deployment objects for Mills are replaced with PodTemplate objects.
    • The PodTemplates are used by new MillJobScheduler Deployment to schedule Mill Jobs.
    • The MillJobScheduler Deployment needs some permissions on K8s resources in the same cluster using K8s RBAC. For the dev configuration, this consists of a new Role and RoleBinding.
    • Maximum concurrency for LLv2 and HMSS can be configured using the --llv2-maximum-concurrency and --hmss-maximum-concurrency options to the scheduler, respectively.
      • You will need to ensure that there are enough machine resources available at maximum concurrency. For example, ensuring that the cluster autoscaler has a sufficiently high value for the maximum number of nodes.
    • The value of the --work-lock-duration option for the Mill PodTemplate must match the corresponding option for the scheduler Deployment.
      • --llv2-work-lock-duration or --hmss-work-lock-duration, depending on the Mill type.
  • Kubernetes object configuration changes for HMSS. Some of these are required even if HMSS is not enabled. See the updated deployment guides for GKE and EKS.
    • There is a new HMSS Mill.
    • The Kingdom internal API and public API servers have a new required --hmss-protocol-config-config option. In the dev configuration, this comes from the hmss_protocol_config_config.textproto file in the certs-and-configs Secret.
    • The Herald now needs access to blob storage. This means it needs to run under a K8s ServiceAccount that has access to the appropriate bucket, as well as the appropriate command line options.
    • The Herald and the HMSS Mill have a new --key-encryption-key-file option for worker (non-aggregator) Duchies. In the dev configuration, this comes from the certs-and-configs Secret.
    • The Duchy Requisition fulfillment server may need more heap space to handle HMSS Requisitions.
    • The EDP simulator may need more heap space to fulfill HMSS Requisitions.

What's Changed

Read more

v0.5.7-rc2

29 Jul 21:59
644e435
Compare
Choose a tag to compare
v0.5.7-rc2 Pre-release
Pre-release

Issues Addressed

  • Existing computations may starve initialization of new computations. See #1637
  • Duchy mill writing output blob error should be transient. See #1644
  • Avoid failing Measurements at Duchy due to stale ComputationParticipant state. See #1663
  • Fix batch get metrics limit in reports service. See #1529

Highlights

  • Mill horizontal autoscaling. See #1697
    • This significantly reduces cost during low traffic periods.
  • More performance improvements for Report creation. See #1641
  • Improved Duchy fault tolerance.
  • The HMSS EDP client library is published as a Maven artifact See #1710

Potentially Requiring Action

  • As part of the Mill horizontal autoscaling feature, the K8s Deployment objects for Mills are replaced with PodTemplate objects.
    • The PodTemplates are used by new MillJobScheduler Deployment to schedule Mill Jobs.
    • The MillJobScheduler Deployment needs some permissions on K8s resources in the same cluster using K8s RBAC. For the dev configuration, this consists of a new Role and RoleBinding.
  • Kubernetes object configuration changes for HMSS. Some of these are required even if HMSS is not enabled. See the updated deployment guides for GKE and EKS.
    • There is a new HMSS Mill.
    • The Kingdom internal API and public API servers have a new required --hmss-protocol-config-config option. In the dev configuration, this comes from the hmss_protocol_config_config.textproto file in the certs-and-configs Secret.
    • The Herald now needs access to blob storage. This means it needs to run under a K8s ServiceAccount that has access to the appropriate bucket, as well as the appropriate command line options.
    • The Herald and the HMSS Mill have a new --key-encryption-key-file option for worker (non-aggregator) Duchies. In the dev configuration, this comes from the certs-and-configs Secret.
    • The Duchy Requisition fulfillment server may need more heap space to handle HMSS Requisitions.
    • The EDP simulator may need more heap space to fulfill HMSS Requisitions.

What's Changed

New Contributors

Full Changelog: v0.5.6...v0.5.7-rc2

v0.5.7-rc1

16 Jul 23:35
9b9a87b
Compare
Choose a tag to compare
v0.5.7-rc1 Pre-release
Pre-release

This is primarily a bugfix release to improve Duchy fault tolerance and to make the Honest Majority Share Shuffle (HMSS) protocol available for use.

Issues Addressed

Highlights

  • More performance improvements for Report creation. See #1641
  • The Honest Majority Share Shuffle (HMSS) protocol is now available.
  • The HMSS EDP client library is published as a Maven artifact

Potentially Requiring Action

  • Kubernetes object configuration changes for HMSS. These are required even if HMSS is not enabled.

What's Changed

Full Changelog: v0.5.6...v0.5.7-rc1

v0.5.6

07 Jun 22:47
a191453
Compare
Choose a tag to compare

This is primarily a bugfix release to address the following issues:

  • Cannot specify separate privacy parameters for single- vs. multi-EDP Measurements in Reporting v2. See #1610
  • #1626
  • #1636
  • #1612
  • #1648

Potentially Requiring Action

  • MetricSpecConfig for Reporting v2 needs to be updated due to changes in #1610
  • Exported OpenTelemetry metrics have been changed slightly. On GKE, these now are exported directly to Google Cloud Monitoring rather than Managed Prometheus. See #1623

What's Changed

Full Changelog: v0.5.5...v0.5.6

v0.5.5

10 May 21:16
2e98c37
Compare
Choose a tag to compare

This is primarily a bug fix release to address #1616

What's Changed

Full Changelog: v0.5.4...v0.5.5

v0.5.4

02 May 16:59
59fdffa
Compare
Choose a tag to compare

This is primarily a bug fix release to address #1596

Potentially Requiring Action

  • The dev configuration for EKS now manages external IP addresses with Terraform. See #1586
    • Use terraform import to import your existing Elastic IP address resources to avoid unintentional external IP address changes.

What's Changed

  • Skip pushing images in Update CMMS workflow if there's an existing image tag. by @SanjayVas in #1582
  • Manage external IP addresses for EKS in Terraform. by @SanjayVas in #1586
  • Add back dispatch for image push. by @renjiezh in #1598
  • Add INITIALIZED stage for aggregator in HMSS. by @renjiezh in #1587
  • Fail correctness/integration test if Measurement is cancelled. by @SanjayVas in #1599
  • Populate MeasurementSpec.serialized_measurement_public_key field. by @SanjayVas in #1597

Full Changelog: v0.5.3...v0.5.4