...
Assumptions
# | Issue | Notes | Decisions |
---|---|---|---|
1 | kafka container port issue | The exposed port of kafka container changed to 9092 in docker-compose.yml | As per the technical discussion, there is no hard-coded port given in any java classes. |
2 | KAFKA_ADVERTISED_LISTENERS hostname resolution issue | The port of KAFKA_ADVERTISED_LISTENERS has been changed to 29092. | As per the technical discussion, there is no hard-coded port given in any java classes. |
Issues & Decisions
# | Issue | Notes | Decisions | ||
---|---|---|---|---|---|
1 | kafka container port issue | Open Questions: 1- Can we change the port to 9092 | ?Since docker-compose.yml is being used for local env. setup and CSIT, it is possible to change to 9092. | ||
2 | KAFKA_ADVERTISED_LISTENERS hostname resolution issue | Open Questions: 1- Can we change the port to 29092 | ?As per local tests run by the | teamTeam 2, and ONAP build, the required change has no negative effect. |
Overview
Can Robot Framework test Kafka clusters and events?
...
Whereas, CPS's kafka container expose its port from "19092"
Code Block | ||||
---|---|---|---|---|
| ||||
kafka: image: confluentinc/cp-kafka:6.2.1 container_name: kafka ports: - "19092:19092" depends_on: - zookeeper environment: KAFKA_BROKER_ID: 1 KAFKA_ZOOKEEPER_CONNECT: zookeeper:2181 KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://kafka:9092,CONNECTIONS_FROM_HOST://localhost:19092 KAFKA_LISTENER_SECURITY_PROTOCOL_MAP: PLAINTEXT:PLAINTEXT,CONNECTIONS_FROM_HOST:PLAINTEXT KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR: 1 |
...
However, it gets fail because of hostname to IP address resolution issue. There is a possible solution for this problem.
a- Change A change in the KAFKA_ADVERTISED_LISTENERS port to 29092into
KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://kafka:29092,CONNECTIONS_FROM_HOST://localhost:909
...