Okay Matthew we're going to investigate the changes in the networking
configuration. But again thanks for your help.

Talking about kubernetes, we're having also some trobles in the deployment.

When we try to run clearwater over containers with kubernetes as
orchestator we have the next issue:

*When running the command  for the pods, this is the result:*
NAME                             READY     STATUS             RESTARTS   AGE
astaire-778bc84754-k7w5p         2/2       Running            0          33m
bono-5bcc97f696-sv85w            2/2       Running            0          33m
cassandra-757bfd8c68-4prkh       0/1       Running            3          33m
cassandra-757bfd8c68-x6js6       0/1       Running            3          33m
cassandra-757bfd8c68-xqq7l       0/1       Running            3          33m
chronos-94c95964b-b2mw9          2/2       Running            0          33m
ellis-5769fc8bd5-8ks2x           1/1       Running            0          33m
etcd-7954884d7-84jr7             1/1       Running            0          33m
homer-74b7bf5878-k9gr4           1/1       Running            0          33m
homestead-6489ccbf6f-7df66       2/2       Running            0          33m
homestead-prov-89dc6f9c9-9f49p   0/1       CrashLoopBackOff   11         33m
ralf-74dc869579-pcs9f            2/2       Running            0          33m
sprout-564484959d-wkq2v          2/2       Running            0          33m


*The logs for homestead is:*

 15-08-2018 14:32:01.469 UTC [7f53d3eb37c0] Status diameterstack.cpp:571:
Starting Diameter stack
15-08-2018 14:32:01.469 UTC [7f53d3eb37c0] Status freeDiameter: Local
server address(es): Unknown error{---L-}
15-08-2018 14:32:01.469 UTC [7f53d3eb37c0] Status httpstack.cpp:40:
Constructing HTTP stack with 12 threads
15-08-2018 14:32:01.469 UTC [7f53d3eb37c0] Status httpstack.cpp:163:
Binding HTTP TCP socket: address=172.17.0.16, port=8888
15-08-2018 14:32:01.533 UTC [7f53d3eb37c0] Status httpstack.cpp:40:
Constructing HTTP stack with 5 threads
15-08-2018 14:32:01.533 UTC [7f53d3eb37c0] Status httpstack.cpp:215:
Binding HTTP unix socket: path=/tmp/homestead-http-mgmt-socket
15-08-2018 14:32:01.558 UTC [7f53d3eb37c0] Status diameterresolver.cpp:37:
Created Diameter resolver
15-08-2018 14:32:01.558 UTC [7f53d3eb37c0] Status main.cpp:1179: Start-up
complete - wait for termination signal
15-08-2018 14:32:01.896 UTC [7f52697f2700] Error
dnscachedresolver.cpp:1098: Resolution of example.com timed out
15-08-2018 14:32:01.896 UTC [7f52697f2700] Warning
dnscachedresolver.cpp:698: Failed to retrieve record for example.com:
Timeout while contacting DNS servers
15-08-2018 14:32:02.308 UTC [7f52697f2700] Error
dnscachedresolver.cpp:1098: Resolution of _diameter._tcp.example.com timed
out
15-08-2018 14:32:02.308 UTC [7f52697f2700] Warning
dnscachedresolver.cpp:698: Failed to retrieve record for _diameter._
tcp.example.com: Timeout while contacting DNS servers
15-08-2018 14:32:02.346 UTC [7f52697f2700] Error
dnscachedresolver.cpp:1098: Resolution of _diameter._sctp.example.com timed
out
15-08-2018 14:32:02.346 UTC [7f52697f2700] Warning
dnscachedresolver.cpp:698: Failed to retrieve record for _diameter._
sctp.example.com: Timeout while contacting DNS servers
15-08-2018 14:32:02.759 UTC [7f52697f2700] Error
dnscachedresolver.cpp:1098: Resolution of hss.example.com timed out
15-08-2018 14:32:02.759 UTC [7f52697f2700] Warning
dnscachedresolver.cpp:698: Failed to retrieve record for hss.example.com:
Timeout while contacting DNS servers
15-08-2018 14:32:02.759 UTC [7f52697f2700] Error diameterstack.cpp:862: No
Diameter peers have been found
15-08-2018 14:32:31.220 UTC [7f53c546a700] Status alarm.cpp:244: Reraising
all alarms with a known state
15-08-2018 14:32:33.134 UTC [7f52697f2700] Error
dnscachedresolver.cpp:1098: Resolution of _diameter._tcp.example.com timed
out
15-08-2018 14:32:33.134 UTC [7f52697f2700] Warning
dnscachedresolver.cpp:698: Failed to retrieve record for _diameter._
tcp.example.com: Timeout while contacting DNS servers
15-08-2018 14:32:33.209 UTC [7f52697f2700] Error
dnscachedresolver.cpp:1098: Resolution of _diameter._sctp.example.com timed
out
15-08-2018 14:32:33.210 UTC [7f52697f2700] Warning
dnscachedresolver.cpp:698: Failed to retrieve record for _diameter._
sctp.example.com: Timeout while contacting DNS servers
15-08-2018 14:32:33.622 UTC [7f52697f2700] Error
dnscachedresolver.cpp:1098: Resolution of hss.example.com timed out
15-08-2018 14:32:33.622 UTC [7f52697f2700] Warning
dnscachedresolver.cpp:698: Failed to retrieve record for hss.example.com:
Timeout while contacting DNS servers
15-08-2018 14:32:33.622 UTC [7f52697f2700] Error diameterstack.cpp:862: No
Diameter peers have been found
15-08-2018 14:33:01.220 UTC [7f53c546a700] Status alarm.cpp:244: Reraising
all alarms with a known state
15-08-2018 14:33:03.700 UTC [7f52697f2700] Warning
dnscachedresolver.cpp:698: Failed to retrieve record for _diameter._
tcp.example.com: Domain name not found
15-08-2018 14:33:03.789 UTC [7f52697f2700] Warning
dnscachedresolver.cpp:698: Failed to retrieve record for _diameter._
sctp.example.com: Domain name not found
15-08-2018 14:33:03.884 UTC [7f52697f2700] Warning
dnscachedresolver.cpp:698: Failed to retrieve record for hss.example.com:
Domain name not found
15-08-2018 14:33:03.884 UTC [7f52697f2700] Error diameterstack.cpp:862: No
Diameter peers have been found
15-08-2018 14:33:31.220 UTC [7f53c546a700] Status alarm.cpp:244: Reraising
all alarms with a known state
15-08-2018 14:34:01.221 UTC [7f53c546a700] Status alarm.cpp:244: Reraising
all alarms with a known state
15-08-2018 14:34:31.222 UTC [7f53c546a700] Status alarm.cpp:244: Reraising
all alarms with a known state
15-08-2018 14:35:01.222 UTC [7f53c546a700] Status alarm.cpp:244: Reraising
all alarms with a known state
15-08-2018 14:35:31.223 UTC [7f53c546a700] Status alarm.cpp:244: Reraising
all alarms with a known state
15-08-2018 14:36:01.224 UTC [7f53c546a700] Status alarm.cpp:244: Reraising
all alarms with a known state

*The logs for homestead_prov is:*
 2018-08-15 14:36:03,725 CRIT Supervisor running as root (no user in config
file)
2018-08-15 14:36:03,725 WARN Included extra file
"/etc/supervisor/conf.d/socket-factory.supervisord.conf" during parsing
2018-08-15 14:36:03,725 WARN Included extra file
"/etc/supervisor/conf.d/clearwater-group.conf" during parsing
2018-08-15 14:36:03,725 WARN Included extra file
"/etc/supervisor/conf.d/nginx.conf" during parsing
2018-08-15 14:36:03,725 WARN Included extra file
"/etc/supervisor/conf.d/homestead-prov.conf" during parsing
2018-08-15 14:36:03,725 WARN Included extra file
"/etc/supervisor/conf.d/snmpd.conf" during parsing
2018-08-15 14:36:03,725 WARN Included extra file
"/etc/supervisor/conf.d/clearwater-infrastructure.conf" during parsing
2018-08-15 14:36:03,725 WARN Included extra file
"/etc/supervisor/conf.d/supervisord.conf" during parsing
2018-08-15 14:36:03,740 INFO RPC interface 'supervisor' initialized
2018-08-15 14:36:03,741 CRIT Server 'unix_http_server' running without any
HTTP authentication checking
2018-08-15 14:36:03,741 INFO supervisord started with pid 1
2018-08-15 14:36:04,742 INFO spawned: 'snmpd' with pid 7
2018-08-15 14:36:04,743 INFO spawnerr: can't find command
'/usr/share/clearwater/bin/clearwater-socket-factory-sig-wrapper'
2018-08-15 14:36:04,749 INFO spawned: 'clearwater-infrastructure' with pid 9
2018-08-15 14:36:04,751 INFO spawnerr: can't find command
'/usr/share/clearwater/bin/clearwater-socket-factory-mgmt-wrapper'
2018-08-15 14:36:04,752 INFO success: snmpd entered RUNNING state, process
has stayed up for > than 0 seconds (startsecs)
2018-08-15 14:36:04,752 INFO success: clearwater-infrastructure entered
RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-08-15 14:36:05,225 INFO exited: snmpd (exit status 0; expected)
2018-08-15 14:36:05,226 CRIT reaped unknown pid 48)
2018-08-15 14:36:06,226 INFO spawnerr: can't find command
'/usr/share/clearwater/bin/clearwater-socket-factory-sig-wrapper'
2018-08-15 14:36:06,227 INFO spawnerr: can't find command
'/usr/share/clearwater/bin/clearwater-socket-factory-mgmt-wrapper'
2018-08-15 14:36:07,297 CRIT reaped unknown pid 52)
2018-08-15 14:36:07,298 CRIT reaped unknown pid 53)
2018-08-15 14:36:08,300 INFO spawnerr: can't find command
'/usr/share/clearwater/bin/clearwater-socket-factory-sig-wrapper'
2018-08-15 14:36:08,300 INFO spawnerr: can't find command
'/usr/share/clearwater/bin/clearwater-socket-factory-mgmt-wrapper'
2018-08-15 14:36:08,605 CRIT reaped unknown pid 183)
2018-08-15 14:36:08,605 CRIT reaped unknown pid 184)
2018-08-15 14:36:08,630 CRIT reaped unknown pid 209)
2018-08-15 14:36:09,860 INFO spawned: 'homestead-prov' with pid 241
2018-08-15 14:36:09,862 INFO spawned: 'nginx' with pid 242
2018-08-15 14:36:10,302 INFO exited: homestead-prov (exit status 0; not
expected)
2018-08-15 14:36:11,307 INFO spawned: 'homestead-prov' with pid 257
2018-08-15 14:36:11,309 INFO success: nginx entered RUNNING state, process
has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:36:11,310 INFO spawnerr: can't find command
'/usr/share/clearwater/bin/clearwater-socket-factory-sig-wrapper'
2018-08-15 14:36:11,310 INFO gave up: socket-factory-sig entered FATAL
state, too many start retries too quickly
2018-08-15 14:36:11,311 INFO spawnerr: can't find command
'/usr/share/clearwater/bin/clearwater-socket-factory-mgmt-wrapper'
2018-08-15 14:36:11,311 INFO gave up: socket-factory-mgmt entered FATAL
state, too many start retries too quickly
2018-08-15 14:36:11,624 INFO exited: clearwater-infrastructure (exit status
0; expected)
2018-08-15 14:36:11,704 INFO exited: homestead-prov (exit status 0; not
expected)
2018-08-15 14:36:13,707 INFO spawned: 'homestead-prov' with pid 286
2018-08-15 14:36:14,096 INFO exited: homestead-prov (exit status 0; not
expected)
2018-08-15 14:36:17,104 INFO spawned: 'homestead-prov' with pid 297
2018-08-15 14:36:17,498 INFO exited: homestead-prov (exit status 0; not
expected)
2018-08-15 14:36:18,498 INFO gave up: homestead-prov entered FATAL state,
too many start retries too quickly

*The log file for one  Cassandra containers is:*
 2018-08-15 14:31:37,714 CRIT Supervisor running as root (no user in config
file)
2018-08-15 14:31:37,714 WARN Included extra file
"/etc/supervisor/conf.d/clearwater-group.conf" during parsing
2018-08-15 14:31:37,715 WARN Included extra file
"/etc/supervisor/conf.d/cassandra.conf" during parsing
2018-08-15 14:31:37,715 WARN Included extra file
"/etc/supervisor/conf.d/snmpd.conf" during parsing
2018-08-15 14:31:37,715 WARN Included extra file
"/etc/supervisor/conf.d/clearwater-infrastructure.conf" during parsing
2018-08-15 14:31:37,715 WARN Included extra file
"/etc/supervisor/conf.d/supervisord.conf" during parsing
2018-08-15 14:31:37,730 INFO RPC interface 'supervisor' initialized
2018-08-15 14:31:37,730 CRIT Server 'unix_http_server' running without any
HTTP authentication checking
2018-08-15 14:31:37,730 INFO supervisord started with pid 1
2018-08-15 14:31:38,736 INFO spawned: 'snmpd' with pid 10
2018-08-15 14:31:38,739 INFO spawned: 'clearwater-infrastructure' with pid
11
2018-08-15 14:31:38,748 INFO success: snmpd entered RUNNING state, process
has stayed up for > than 0 seconds (startsecs)
2018-08-15 14:31:38,748 INFO success: clearwater-infrastructure entered
RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-08-15 14:31:39,092 INFO exited: snmpd (exit status 0; expected)
2018-08-15 14:31:39,092 CRIT reaped unknown pid 51)
2018-08-15 14:31:41,116 CRIT reaped unknown pid 55)
2018-08-15 14:31:41,117 CRIT reaped unknown pid 56)
2018-08-15 14:31:41,339 CRIT reaped unknown pid 117)
2018-08-15 14:31:41,340 CRIT reaped unknown pid 116)
2018-08-15 14:31:41,363 CRIT reaped unknown pid 141)
2018-08-15 14:31:43,549 CRIT reaped unknown pid 178)
2018-08-15 14:31:43,610 INFO spawned: 'cassandra' with pid 183
2018-08-15 14:31:44,635 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:31:44,641 INFO exited: clearwater-infrastructure (exit status
0; expected)
2018-08-15 14:31:45,637 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:31:46,640 INFO spawned: 'cassandra' with pid 194
2018-08-15 14:31:47,663 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:31:48,666 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:31:49,668 INFO spawned: 'cassandra' with pid 197
2018-08-15 14:31:50,675 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:31:51,677 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:31:52,681 INFO spawned: 'cassandra' with pid 200
2018-08-15 14:31:53,693 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:31:54,699 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:31:55,702 INFO spawned: 'cassandra' with pid 203
2018-08-15 14:31:56,707 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:31:57,708 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:31:58,709 INFO spawned: 'cassandra' with pid 212
2018-08-15 14:31:59,716 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:00,718 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:01,720 INFO spawned: 'cassandra' with pid 215
2018-08-15 14:32:02,726 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:03,726 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:04,730 INFO spawned: 'cassandra' with pid 218
2018-08-15 14:32:05,753 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:06,756 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:07,762 INFO spawned: 'cassandra' with pid 229
2018-08-15 14:32:08,781 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:09,784 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:10,785 INFO spawned: 'cassandra' with pid 232
2018-08-15 14:32:11,791 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:12,791 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:13,793 INFO spawned: 'cassandra' with pid 235
2018-08-15 14:32:14,801 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:15,801 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:16,805 INFO spawned: 'cassandra' with pid 244
2018-08-15 14:32:17,824 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:18,827 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:19,830 INFO spawned: 'cassandra' with pid 247
2018-08-15 14:32:20,841 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:21,841 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:22,843 INFO spawned: 'cassandra' with pid 250
2018-08-15 14:32:23,852 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:24,855 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:25,858 INFO spawned: 'cassandra' with pid 253
2018-08-15 14:32:26,863 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:27,864 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:28,868 INFO spawned: 'cassandra' with pid 263
2018-08-15 14:32:29,888 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:30,891 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:31,897 INFO spawned: 'cassandra' with pid 266
2018-08-15 14:32:32,913 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:33,917 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:34,919 INFO spawned: 'cassandra' with pid 269
2018-08-15 14:32:35,931 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:36,934 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:37,940 INFO spawned: 'cassandra' with pid 278
2018-08-15 14:32:38,964 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:39,967 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:40,969 INFO spawned: 'cassandra' with pid 281
2018-08-15 14:32:41,976 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:42,980 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:43,983 INFO spawned: 'cassandra' with pid 284
2018-08-15 14:32:44,997 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:45,999 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:47,002 INFO spawned: 'cassandra' with pid 294
2018-08-15 14:32:48,021 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:49,023 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:50,026 INFO spawned: 'cassandra' with pid 297
2018-08-15 14:32:51,047 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:52,050 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:53,054 INFO spawned: 'cassandra' with pid 300
2018-08-15 14:32:54,075 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:55,080 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:56,084 INFO spawned: 'cassandra' with pid 303
2018-08-15 14:32:57,097 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:32:58,098 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:32:59,104 INFO spawned: 'cassandra' with pid 314
2018-08-15 14:33:00,123 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:01,123 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:02,129 INFO spawned: 'cassandra' with pid 317
2018-08-15 14:33:03,140 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:04,149 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:05,154 INFO spawned: 'cassandra' with pid 320
2018-08-15 14:33:06,177 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:07,178 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:08,182 INFO spawned: 'cassandra' with pid 329
2018-08-15 14:33:09,206 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:10,205 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:11,209 INFO spawned: 'cassandra' with pid 332
2018-08-15 14:33:12,219 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:13,220 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:14,226 INFO spawned: 'cassandra' with pid 336
2018-08-15 14:33:15,244 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:16,251 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:17,254 INFO spawned: 'cassandra' with pid 348
2018-08-15 14:33:18,259 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:19,259 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:20,263 INFO spawned: 'cassandra' with pid 351
2018-08-15 14:33:21,282 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:22,286 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:23,287 INFO spawned: 'cassandra' with pid 354
2018-08-15 14:33:24,292 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:25,295 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:26,298 INFO spawned: 'cassandra' with pid 362
2018-08-15 14:33:27,318 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:28,319 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:29,321 INFO spawned: 'cassandra' with pid 365
2018-08-15 14:33:30,327 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:31,328 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:32,331 INFO spawned: 'cassandra' with pid 368
2018-08-15 14:33:33,349 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:34,356 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:35,358 INFO spawned: 'cassandra' with pid 371
2018-08-15 14:33:36,364 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:37,364 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:38,367 INFO spawned: 'cassandra' with pid 380
2018-08-15 14:33:39,389 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:40,393 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:41,399 INFO spawned: 'cassandra' with pid 383
2018-08-15 14:33:42,422 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:43,424 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:44,430 INFO spawned: 'cassandra' with pid 386
2018-08-15 14:33:45,441 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:46,443 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:47,445 INFO spawned: 'cassandra' with pid 395
2018-08-15 14:33:48,452 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:49,452 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:50,454 INFO spawned: 'cassandra' with pid 398
2018-08-15 14:33:51,463 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:52,464 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:53,467 INFO spawned: 'cassandra' with pid 401
2018-08-15 14:33:54,477 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:55,478 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:56,483 INFO spawned: 'cassandra' with pid 411
2018-08-15 14:33:57,488 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:33:58,490 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:33:59,492 INFO spawned: 'cassandra' with pid 414
2018-08-15 14:34:00,497 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:34:01,500 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:34:02,505 INFO spawned: 'cassandra' with pid 417
2018-08-15 14:34:03,523 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:34:04,526 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:34:05,530 INFO spawned: 'cassandra' with pid 420
2018-08-15 14:34:06,535 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:34:07,536 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:34:08,541 INFO spawned: 'cassandra' with pid 429
2018-08-15 14:34:09,563 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:34:10,567 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:34:11,572 INFO spawned: 'cassandra' with pid 432
2018-08-15 14:34:12,591 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:34:13,593 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:34:14,597 INFO spawned: 'cassandra' with pid 435
2018-08-15 14:34:15,603 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:34:16,604 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:34:17,608 INFO spawned: 'cassandra' with pid 446
2018-08-15 14:34:18,626 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:34:19,631 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:34:20,634 INFO spawned: 'cassandra' with pid 456
2018-08-15 14:34:21,643 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:34:22,643 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:34:23,646 INFO spawned: 'cassandra' with pid 512
2018-08-15 14:34:23,682 CRIT reaped unknown pid 529)
2018-08-15 14:34:24,050 CRIT reaped unknown pid 530)
2018-08-15 14:34:25,052 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:34:41,929 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:34:42,226 INFO spawned: 'cassandra' with pid 1083
2018-08-15 14:34:42,226 CRIT reaped unknown pid 577)
2018-08-15 14:34:42,256 CRIT reaped unknown pid 1098)
2018-08-15 14:34:42,586 CRIT reaped unknown pid 1100)
2018-08-15 14:34:43,589 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:35:02,573 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:35:02,897 INFO spawned: 'cassandra' with pid 1735
2018-08-15 14:35:02,897 CRIT reaped unknown pid 1145)
2018-08-15 14:35:02,941 CRIT reaped unknown pid 1751)
2018-08-15 14:35:03,340 CRIT reaped unknown pid 1752)
2018-08-15 14:35:04,342 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:35:22,632 CRIT reaped unknown pid 1798)
2018-08-15 14:35:22,674 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:35:23,677 INFO spawned: 'cassandra' with pid 2390
2018-08-15 14:35:23,720 CRIT reaped unknown pid 2405)
2018-08-15 14:35:24,126 CRIT reaped unknown pid 2406)
2018-08-15 14:35:25,128 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:35:43,486 CRIT reaped unknown pid 2453)
2018-08-15 14:35:43,600 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:35:44,603 INFO spawned: 'cassandra' with pid 3044
2018-08-15 14:35:44,650 CRIT reaped unknown pid 3059)
2018-08-15 14:35:45,128 CRIT reaped unknown pid 3060)
2018-08-15 14:35:46,128 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-08-15 14:36:02,745 CRIT reaped unknown pid 3106)
2018-08-15 14:36:02,867 INFO exited: cassandra (exit status 232; not
expected)
2018-08-15 14:36:03,869 INFO spawned: 'cassandra' with pid 3643
2018-08-15 14:36:03,946 CRIT reaped unknown pid 3658)
2018-08-15 14:36:04,497 CRIT reaped unknown pid 3659)
2018-08-15 14:36:05,498 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)

*The logs for etcd is:*

 2018-08-15 14:31:41.683108 I | etcdmain: etcd Version: 2.2.5
2018-08-15 14:31:41.683372 I | etcdmain: Git SHA: bc9ddf2
2018-08-15 14:31:41.683393 I | etcdmain: Go Version: go1.5.3
2018-08-15 14:31:41.683452 I | etcdmain: Go OS/Arch: linux/amd64
2018-08-15 14:31:41.683521 I | etcdmain: setting maximum number of CPUs to
3, total number of available CPUs is 3
2018-08-15 14:31:41.683590 W | etcdmain: no data-dir provided, using
default data-dir ./etcd-7954884d7-84jr7.etcd
2018-08-15 14:31:41.683740 I | etcdmain: listening for peers on
http://0.0.0.0:2380
2018-08-15 14:31:41.683848 I | etcdmain: listening for client requests on
http://0.0.0.0:2379
2018-08-15 14:31:41.683937 I | etcdmain: listening for client requests on
http://0.0.0.0:4001
2018-08-15 14:31:41.684172 I | etcdserver: name = etcd-7954884d7-84jr7
2018-08-15 14:31:41.684204 I | etcdserver: data dir =
etcd-7954884d7-84jr7.etcd
2018-08-15 14:31:41.684268 I | etcdserver: member dir =
etcd-7954884d7-84jr7.etcd/member
2018-08-15 14:31:41.684308 I | etcdserver: heartbeat = 100ms
2018-08-15 14:31:41.684340 I | etcdserver: election = 1000ms
2018-08-15 14:31:41.684371 I | etcdserver: snapshot count = 10000
2018-08-15 14:31:41.684408 I | etcdserver: advertise client URLs =
http://172.17.0.14:2379,http://172.17.0.14:4001
2018-08-15 14:31:41.684447 I | etcdserver: initial advertise peer URLs =
http://172.17.0.14:2380
2018-08-15 14:31:41.684484 I | etcdserver: initial cluster =
etcd-7954884d7-84jr7=http://172.17.0.14:2380
2018-08-15 14:31:41.690385 I | etcdserver: starting member a93655729080770c
in cluster b43922894bcbe68b
2018-08-15 14:31:41.690643 I | raft: a93655729080770c became follower at
term 0
2018-08-15 14:31:41.690729 I | raft: newRaft a93655729080770c [peers: [],
term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
2018-08-15 14:31:41.690809 I | raft: a93655729080770c became follower at
term 1
2018-08-15 14:31:41.692539 I | etcdserver: starting server... [version:
2.2.5, cluster version: to_be_decided]
2018-08-15 14:31:41.695384 N | etcdserver: added local member
a93655729080770c [http://172.17.0.14:2380] to cluster b43922894bcbe68b
2018-08-15 14:31:41.992667 I | raft: a93655729080770c is starting a new
election at term 1
2018-08-15 14:31:41.992758 I | raft: a93655729080770c became candidate at
term 2
2018-08-15 14:31:41.992775 I | raft: a93655729080770c received vote from
a93655729080770c at term 2
2018-08-15 14:31:41.992794 I | raft: a93655729080770c became leader at term
2
2018-08-15 14:31:41.992802 I | raft: raft.node: a93655729080770c elected
leader a93655729080770c at term 2
2018-08-15 14:31:41.993316 I | etcdserver: published
{Name:etcd-7954884d7-84jr7 ClientURLs:[http://172.17.0.14:2379
http://172.17.0.14:4001]} to cluster b43922894bcbe68b
2018-08-15 14:31:41.993514 I | etcdserver: setting up the initial cluster
version to 2.2
2018-08-15 14:31:41.999251 N | etcdserver: set the initial cluster version
to 2.2

*This is the information about the kubernetes version *

Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.0",
GitCommit:"91e7b4fd31fcd3d5f436da26c980becec37ceefe", GitTreeState:"clean",
BuildDate:"2018-06-27T20:17:28Z", GoVersion:"go1.10.2", Compiler:"gc",
Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0",
GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean",
BuildDate:"2018-03-26T16:44:10Z", GoVersion:"go1.9.3", Compiler:"gc",
Platform:"linux/amd64"}

And I'm using minikube 0.28.0

Also, all the steps that we were followed are from the readme in github


Thanks so much for your help.

Att: Gabriel Orozco

El mar., 11 sept. 2018 a las 22:46, Davis, Matthew (<
matthew.davi...@team.telstra.com>) escribió:

> Hi Gabriel,
>
>
>
> Yes there are of course some differences in networking configuration.
>
> I don’t know much about the details of etcd. However I do know that when
> working with Kubernetes (and presumably other container orchestrators) you
> do *not* want to ever hard code IP addresses. Those change. So etcd is
> referenced through DNS, and it points to a service which distributes
> requests across the cluster of etcd notes.
>
> The end result is the same.
>
>
>
> Regards,
>
>
>
> *Matt*
>
> Technical Specialist
>
> Telstra | CTO | Cloud SDN NFV
>
>
>
> *From:* Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org]
> *On Behalf Of *GABRIEL DAVID OROZCO URRUTIA
> *Sent:* Wednesday, 12 September 2018 1:39 PM
> *To:* clearwater@lists.projectclearwater.org
> *Subject:* Re: [Project Clearwater] Difference between source code of
> Clearwater over containers and Virtual Machines
>
>
>
> Thanks so much for your help, Matthew.
>
>
>
> But, It makes me question another thing: what about the local_config file?
>
> Because there are differences between the deploy over VM and containers.
>
>
>
> Local_config file over containers:
>
> # Local IP configuration
>
> local_ip=172.17.0.2
>
> public_ip=172.17.0.2
>
> public_hostname=172.17.0.2
>
>
>
> # Only keep 50MB of logs
>
> max_log_directory_size=52428800
>
> etcd_proxy=etcd0=http://etcd:2380
>
>
>
> Local file over Virtual Machines:
>
> local_ip=<privateIP>
>
> public_ip=<publicIP>
>
> public_hostname=<hostname>
>
> etcd_cluster="<comma separated list of private IPs>"
>
>
>
> The differences are in the usage of etcd_proxy, right? But, where is the
> configuration file for the automatic change when it is deployed over
> containers?
>
>
>
> Again, thanks so much for your help
>
>
>
> Att: Gabriel Orozco (University of Cauca Student)
>
>
>
> El mar., 11 sept. 2018 a las 18:09, Davis, Matthew (<
> matthew.davi...@team.telstra.com>) escribió:
>
> Hi,
>
>
>
> Yes the code is the same for both.
>
> The Dockerfiles just do `apt-get install $MODULE`
> e.g. here’s the one for homestead: 
> https://github.com/Metaswitch/clearwater-docker/blob/83d9519c34bdf52c2e5eb4bd74ceeed1be8f2a15/homestead/Dockerfile#L4
>
>
>
> Yes there’s something funny about homestead-prov. I don’t know the answer
> to that one.
>
>
>
> Regards,
>
>
>
> *Matthew Davis*
>
> Technical Specialist
>
> Telstra | CTO | Cloud SDN NFV
>
>
>
> *From:* Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org]
> *On Behalf Of *GABRIEL DAVID OROZCO URRUTIA
> *Sent:* Wednesday, 12 September 2018 2:30 AM
> *To:* clearwater@lists.projectclearwater.org
> *Subject:* [Project Clearwater] Difference between source code of
> Clearwater over containers and Virtual Machines
>
>
>
> Hello
>
>
>
> We’re working on a performance test of clearwater over containers. We want
> to know if the source code of the components (eg., bono, sprout) over
> containers are the same for the deploy over virtual machines.
>
> Also, we want to know where is the source code of homestead-prov. Because
> we found all the other components codes in the metaswitch github
> repository(eg., ralf, homestead, cassandra) but not the one of
> homestead-prov.
>
>
>
> Thanks for the help
>
>
> ------------------------------
>
> *Hacia una Universidad comprometida con la Paz Territorial*
>
> _______________________________________________
> Clearwater mailing list
> Clearwater@lists.projectclearwater.org
>
> http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
>
>
> ------------------------------
>
> *Hacia una Universidad comprometida con la Paz Territorial*
> _______________________________________________
> Clearwater mailing list
> Clearwater@lists.projectclearwater.org
>
> http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
>

-- 


*Hacia una
Universidad comprometida con la Paz Territorial*
_______________________________________________
Clearwater mailing list
Clearwater@lists.projectclearwater.org
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org

Reply via email to