Hamad application layout scheme 05 of hashicopy (visit the web page)

One start-up nomad visit web Interface

Now? , You will quickly explore Nomad web Interface .
If you arrive at this tutorial in a different order , Please complete the previous steps in this collection , Or run

nomad agent -dev -bind 0.0.0.0 -log-level=INFO

Two visit UI

as long as Nomad Running ,Nomad UI It's also running . It is associated with Nomad HTTP API At the same address and port , be located /UI Under the namespace .
function Nomad dev After agency , visit http://localhost:4646 open Nomad UI. You should start with the work page . You should also see the sample job from the previous tutorial .

• Run job

• Job Carry out orders

Look at the individual Jobs details

3、 ... and Troubleshooting

If you are using Vagrant And cannot connect to Nomad web Interface , Here are some possible reasons .

• Nomad dev The agent is not in -bind Value is set to 0.0.0.0 In case of starting
  Stop and restart Nomad dev agent , And set the binding flag to the correct value .
• take 4646 Port conflict while mapping back to host
  Vagrant Select a new port to map to VM Medium 4646. Your vagrant up The output should contain the new port mapping ：

 default: Fixed port collision for 4646 => 4646. Now on port 2200.

If there is this message , You will be connected to http://localhost:2200.

Four View cluster information

Nomad web The interface provides a way to view Nomad The cluster itself ： The server 、 Client and cluster topologies .

4.1 see servers

4.2 see client

4.3 Cluster topology

Nomad web Interface topology viewer (http://localhost:4646/ui/topology) Provides an alternative view of clusters and running workloads . In a more complex environment , This view can help you understand where and how the workload runs 、 The jobs running next to you and the advanced view of the used and open cluster capacity .

5、 ... and monitor

Nomad web The interface also displays at the user selectable log level Nomad Application log . This is similar to the command line interface nomad monitor Command parallelism . You can access it from the details page of a single node . This works for both the server and the client .

6、 ... and stop it Job

Running dev Acting shell In the session , Use Ctrl-C Interrupt the signal to stop the agent .
After interrupting the agent , The log shows that the cluster is shutting down ：

nomad job stop example

• Use vagrant clear

vagrant destroyvagrant box remove bento/ubuntu-18.04