Hi, you should be able to ignore amsterdam - don't think there is any more development there - DCAEGEN2 for example is refactored in beijing.
Check your images in the csv manifest for heat btw - looks like 2 docker images are missing - we plan on using this csv as an override for the docker prepull and values.yaml
https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv
https://lf-onap.atlassian.net/browse/OOM-952

check your healtcheck as well
https://lf-onap.atlassian.net/browse/OOM-960

Michael,

  All ONAP participants agreed that having a working AAF Beijing in TEST is more important than fixing Amsterdam OOM.

  As of Monday, 04/08/2018, we have AAF in Beijing TEST.  This leaves us time to work on OOM deployments for Beijing without impacting other schedules. 

The AAF Ticket for this is .  

We would appreciate it if you could close down the OOM deployment for AAF Amsterdam, and we can work with what is required for Beijing without impacting Clients.

Thanks,

Jonathan

AAF latsest docker images are now available in Nexus.We do have multiple docker images that needs to deploy,work on modifying existing OOM templates.

ETA to close this by RC0

Planning to validate on new docker image.

Sai to test service in Kubenetes and close this ticket before 03/28