Uploaded image for project: 'Portal'
  1. Portal
  2. PORTAL-1037

Portal is using a custom Cassandra image, while a common ONAP Cassandra image is available

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • Honolulu Release
    • Guilin Release
    • Portal
    • None
    • ONAP/Guilin, OOM/master Nov 6th 2020.

      Portal uses currently a customized, old Cassandra Image (cassandra_music:3.0.0).

      (from oom/kubernetes/portal/components/portal-cassandra/values.yaml )
      image: onap/music/cassandra_music:3.0.0

      We shall be using a common Cassandra image for Portal, similar as for other components.
      This image doesn`t support IPv4/IPv6 dual-stack, and we are not legally permitted to use such a cassandra image. Thus we need to migrate to a publicly available image.
      Initial tests has shown this image:

      docker.io/library/cassandra:3.11.9 ... works properly, although, there might be some additional issues to be solved in a configuration of that image, or pre-configuration needed for Portal.

      This will most probably be done with an init container starting before core portal-fe/be pods.

      Additional hints:

      music-cassandra image has some customization to create user/role like below. Additionally, we need to run portal.cql file when Cassandra loads. CREATE ROLE IF NOT EXISTS <CASSUSER> WITH PASSWORD = '<CASSPASS>' AND SUPERUSER = True AND LOGIN = True; ALTER ROLE cassandra WITH PASSWORD = 'SomeLongRandomStringNoonewillthinkof'; We need to make sure this is happening once we start using the new image.

            grzegorz-lis grzegorz-lis
            deen1985 deen1985
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: