Configurar um balanceador de carga de rede interno avaliações

Микола Д. · Revisado há about 1 year

Erick Osvaldo F. · Revisado há about 1 year

Sheila J. · Revisado há about 1 year

Kumar R. · Revisado há about 1 year

Omar S. · Revisado há about 1 year

Eric P. · Revisado há about 1 year

Gabriel G. · Revisado há about 1 year

Keith H. · Revisado há about 1 year

Vaishali K. · Revisado há about 1 year

Maneesh raj k. · Revisado há about 1 year

Vaishali K. · Revisado há about 1 year

Cristian V. · Revisado há about 1 year

Ming Keat P. · Revisado há about 1 year

Ishtiaq S. · Revisado há about 1 year

Vemu A. · Revisado há about 1 year

Robin A. · Revisado há about 1 year

Lab env is not stable: 1. On the first run of the scripts "sudo google_metadata_script_runner startup" on instance-group-1* and instance-group-2* vm script stuck on startup-script: Processing triggers for man-db (2.9.4-2) ... Ctrl-C and re-run of the script helps, but why do we need man pages installed on those hosts? 2. After creating load balancer, linking backends, frontend, creating ip for LB and health-checks, virtual machines in the pool are reset to their default apache webpages. and curl 10.10.30.5 does not report "<h1>Internal Load Balancing Lab</h1>" but the "<title>Index of /</title>" HTML-page. to make LB correctly report - we have to re-run startup scripts on VM. since this part of the LAB does not have automated checks, I assume most users just click "end lab" and do not see that it not works as described

Yuri G. · Revisado há about 1 year

KHIROD B. · Revisado há about 1 year

Good

Ancymon S. · Revisado há about 1 year

Rahul P. · Revisado há about 1 year

Naveen Krishna B. · Revisado há about 1 year

Shobhit J. · Revisado há about 1 year

Shyni H. · Revisado há about 1 year

Timple Nithiya R. · Revisado há about 1 year

Richa A. · Revisado há about 1 year