On 22.05.2019 02:47, Keong Lim wrote:
> Hi Krzysztof,
>
> Running a kubectl to describe the pod e.g.
>
> $ kubectl -n onap describe pod
> dev-sniro-emulator-sniro-emulator-7fcf786cc4-mj7xj
>
> returns info such as:
>
> Image: nexus3.onap.org:10001/onap/sniroemulator:1.0.0
>
> Then a find for "sniroemulator" across all ONAP projects returns these
> results:
>
> $ find . \( -name "Dockerfile" -o -name "pom.xml" \) -type f -print | xargs
> grep sniroemulator
> ./integration/test/mocks/sniroemulator/pom.xml:
> <artifactId>sniroemulator</artifactId>
> ./integration/test/mocks/sniroemulator/pom.xml: <name>sniroemulator</name>
> ./integration/test/mocks/sniroemulator/pom.xml:
> <start-class>org.onap.integration.test.mocks.sniroemulator.MockApplication</start-class>
> ./integration/test/mocks/sniroemulator/src/main/docker/Dockerfile:COPY
> sniroemulator.jar /var/wiremock/lib/app.jar
>
>
> I imagine that this is a straighforward script to automate or an index that
> can be pre-computed.
>
Yes it is but it requires a whole ONAP source code to be downloaded on
machine which executes this script or uploading of prebuild index. Not
to mention that the version of source code has to exactly match what's
really deployed. I'd be happy if we could save an additional step and be
able to get that answer directly from a deployed environment without
looking for a matching source code.
I know that it may sound silly now but in a future I expect that users
could deploy every ONAP component in different versions (maybe because
of some fixes or required features) and simple grepping may become error
prone.
Best regards,
--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17165): https://lists.onap.org/g/onap-discuss/message/17165
Mute This Topic: https://lists.onap.org/mt/31697270/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
