nomad

1- Try changing

There are multiple ways you could handle distributing the requests across your servers. Some may be more preferable than the other depending on your deployment environment.

The Fabio load balancer docs have a section on deployment configurations which I'll use as a reference.

In this model, you could configure DNS to point to the IPs of all three servers. Clients would receive all three IPs back in response to a DNS query, and randomly connect to one of the available instances.

If an IP is unhealthy, the client should retry the request to one of the other IPs, but clients may experience slower response times if a server is unavailable for an extended period of time and the client is occasionally routing requests to that unavailable IP.

You can mitigate this issue by configuring your DNS server to perform health checking of backend instances (assuming it supports it). AWS Route 53 provides this functionality (see Configuring DNS failover). If your DNS server does not support health checking, but provides an API to update records, you can use Consul Terraform Sync to automate adding/removing server IPs as the health of the Fabio instances changes in Consul.

As you mentioned the other option would be to place Fabio behind a load balancer. If you're deploying in the cloud, this could be the cloud provider's LB. The LB would give you better control over traffic routing to Fabio, provide TLS/SSL termination, and other functionality.

If you're on-premises, you could front it with any available load balancer like F5, A10, nginx, Apache Traffic Server, etc. You would need to ensure the LB is deployed in a highly available manner. Some suggestions for doing this are covered in the next section.

Whether you're running Fabio directly on the Internet, or behind a load balancer, you need to make sure the IP which clients are connecting to is highly available.

If you're deploying on-premises, one method for achieving this would be to assign a common loopback IP each of the Fabio servers (e.g., 192.0.2.10), and then use an L2 redundancy protocol like Virtual Router Redundancy Protocol (VRRP) or an L3 routing protocol like BGP to ensure the network routes requests to available instances.

Keepalived is a VRRP daemon for Linux. There can find many tutorials online for installing and configure in.

GoCast is a BGP daemon built on GoBGP which conditionally advertises IPs to the upstream network based on the state of health checks. The author of this tool published a blog post titled BGP based Anycast as a Service which walks through deploying GoCast on Nomad, and configuring it to use Consul for health information.

If you're deploying on-premises, a more simple configuration than the two aforementioned solutions might be to configure your router to install/remove static routes based on health checks to your backend instances. Cisco routers support this through their IP SLA feature. This tutorial walks through a basic setup configuration http://www.firewall.cx/cisco-technical-knowledgebase/cisco-routers/813-cisco-router-ipsla-basic.html.

As you can see, there are many ways to configure HA for Fabio or an upstream LB. Its hard to provide a good recommendation without knowing more about your environment. Hopefully one of these suggestions will be useful to you.

I'd suggest to have a look at setting up your local environment using Vagrant (which is also a product for Hashicorp) and Virtual box. There are plenty examples online, for example

• Here is one of the most recent setup with Nomad and Consul, although it is not parametrised much.

• Here is one with the core Hashicorp stack, i.e. Nomad, Vault and Consul. This repo is quite old but it merely means that it uses old versions of binaries, which should be easy to update.

• Here is one with only Vault and Consul, but you can add Nomad in a similar way. In fact, this Vargrant setup and how files are structured seems to me pretty close to the one above

I've run the first two previous week with a simple

Would you call LoginPagePresenter class's constructor method?

Before

You can just simply put the inside the

Ad storage it seems nomad has started to use CSI (Container Storage Interface) plugins, see https://www.nomadproject.io/docs/job-specification/csi_plugin

Ad network, there's support for CNI (Container Network Interface), see https://www.nomadproject.io/docs/job-specification/network#network-examples

Nomad jobs listen on a specific host/port pair.

You might want to ssh into the server and run docker ps to see what host/port pair the job is listening on.

figured it out, I should make separate config files for server and client instead of combining them together.

If pulling data directly from the NOMADS GFS source, it looks like your data should be in yx dimension order (which is also the order assumed by MetPy's lat_lon_grid_deltas function). And so, I would presume that something got messed up in the script with regards to dimension ordering. Resolving this, and making additional use of some of MetPy's xarray integration features to clean up the implementation, we have: