You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Marc Roos <M....@f1-outsourcing.eu> on 2019/04/29 20:44:57 UTC

How to supply cni_args via the environment

I thought you would be able to supply CNI_ARGS via the environment. But 
the command below does not seem to parse the IP to the cni networking. I 
am able to configure the ip directly in the cni network configuration. 
But I like to provide it via the task launch.


[@m03 ~]# cat /test/env-cni.json
{
    "CNI_ARGS": "'IP=192.168.122.178'"
}


[@m03 mesos-cni]# clear; mesos-execute --master=192.168.10.151:5050 
--name=test --command="env > /dev/pts/0; sleep 60" 
--networks=test-macvtap-cniip --env=file:///test/env-cni.json


I0429 22:31:16.062587 25810 scheduler.cpp:189] Version: 1.7.2
I0429 22:31:16.067922 25811 scheduler.cpp:342] Using default 'basic' 
HTTP authenticatee
I0429 22:31:16.068275 25811 scheduler.cpp:525] New master detected at 
master@192.168.10.151:5050
Subscribed with ID c5c2ffdd-8be6-4c88-bf02-5e57d3897c92-0018
Submitted task 'test' to agent 'f469d3c7-4086-448f-96dd-b900b0890a7b-S1'
Received status update TASK_STARTING for task 'test'
  source: SOURCE_EXECUTOR
Received status update TASK_RUNNING for task 'test'
  source: SOURCE_EXECUTOR
CNI_ARGS='IP=192.168.122.178'
LIBPROCESS_IP=0.0.0.0
MESOS_AGENT_ENDPOINT=192.168.10.153:5051
MESOS_DIRECTORY=/var/lib/mesos/slaves/f469d3c7-4086-448f-96dd-b900b0890a
7b-S1/frameworks/c5c2ffdd-8be6-4c88-bf02-5e57d3897c92-0018/executors/tes
t/runs/a552e89d-49ca-4e75-b497-a7a06e9c6957
MESOS_EXECUTOR_ID=test
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/var/lib/mesos/slaves/f469d3c7-4086-448f-96dd-b900b0890a7b-S1/framew
orks/c5c2ffdd-8be6-4c88-bf02-5e57d3897c92-0018/executors/test/runs/a552e
89d-49ca-4e75-b497-a7a06e9c6957
MESOS_EXECUTOR_SHUTDOWN_GRACE_PERIOD=5secs
MESOS_NATIVE_JAVA_LIBRARY=/usr/lib/libmesos-1.7.2.so
MESOS_NATIVE_LIBRARY=/usr/lib/libmesos-1.7.2.so
MESOS_HTTP_COMMAND_EXECUTOR=0
MESOS_SLAVE_PID=slave(1)@192.168.10.153:5051
MESOS_FRAMEWORK_ID=c5c2ffdd-8be6-4c88-bf02-5e57d3897c92-0018
MESOS_CHECKPOINT=0
SHLVL=1
LIBPROCESS_PORT=0
MESOS_SLAVE_ID=f469d3c7-4086-448f-96dd-b900b0890a7b-S1
LIBPROCESS_SSL_SUPPORT_DOWNGRADE=1
MESOS_SANDBOX=/var/lib/mesos/slaves/f469d3c7-4086-448f-96dd-b900b0890a7b
-S1/frameworks/c5c2ffdd-8be6-4c88-bf02-5e57d3897c92-0018/executors/test/
runs/a552e89d-49ca-4e75-b497-a7a06e9c6957
_=/usr/bin/env
Received status update TASK_FINISHED for task 'test'
  message: 'Command exited with status 0'
  source: SOURCE_EXECUTOR