How to use EVE with a controller (recommended)ĮVE-OS can be used with the opensource Adam controller by following the instructions at Eden. Why pillar? Well, because pillar is the kind of a monolith we need to break out into true, individual microservices under pkg/. All of that functionality is being orchestrated by the Go microservices available under pkg/pillar. To get its job done, EVE leverages a lot of great open source projects: Xen Project, Linuxkit and Alpine Linux just to name a few. While EVE can run on a board as small as a $20 Orange Pi, the sweet spot for its deployment are IoT Gateways and Industrial PCs. Once installed, EVE has direct access to and control of underlying resources and provides standard APIs that allow more efficient use of resources and can effectively partition hardware to increase workload consolidation and application multi-tenancy.ĮVE supports both ARM and Intel architectures and requires hardware-assisted virtualization. It offers users new levels of control through hardware-assisted virtualization of on-prem edge devices. Testing connectivity against public destinations.ĮVE aims to develop an open, agnostic and standardized architecture unifying the approach to developing and orchestrating cloud-native applications across the enterprise on-premises edge. So the idea is to change the default behavior for probing and preferĮndpoints close to the device (inside a private network) before Responds (with anything - we only care about connectivity),Ĥ.3 As a last resort - try to ping 8.8.8.8 and return result. Run query (with one attempt) to get "A" record for the rootĭomain (".").
If any handshake succeeds, consider connectivity asĤ.2 Next try DNS requests. Try TCP handshake with those that are addressed by IPs (DNS not userĭidn't change anything in the probing config.Ĥ.1 First, see if there are proxies configured for the LTE network. This step is run in the default and the most common case - i.e. In that case run the ICMP probe and return the result.Ĥ. Check if user explicitly configured some endpoint for ICMP-based If it is disabled do not continue - assume that connectivity is OKģ. Check if probing is disabled by the user (it is enabled by default).
due to a signal loss, we will very likelyĭetect it already here, without sending/receiving any packets.Ģ. First check connectivity status as reported by the modem. My proposal is to probe connectivity as follows:ġ. That would not require API/controller changes. There is also an incentive for a quicker solution LTE connections are typically priced based on the amount of traffic We should also minimize the amount of traffic used for probing because Note that apart fromĪvoiding incorrect probing results (false positives or negatives), Handle both public and private LTE networks.
Project eve developer Patch#
The goal of this patch is to make the probing a bit more advanced to What's more, proxies may be deployed inside the private network andįirewall configured to allow only proxies to go out into the Internet. Reliable destination inside the private network responding to ICMP However, in customer private LTE networks ICMP towards publicĭestinations is often blocked by a firewall and there might not be any This works well with public LTE networks. This is not recommended - we have seen probing helping to resolveĬonnectivity/modem issues multiple times in the past.īy default, probe uses google public DNS server 8.8.8.8 as theĭestination for ICMP pings.
It is also possible to completely disable probing. This is configurable - the probing target can be set to any IP address Message and the wwan microservice triggers re-connect procedure. If a probe fails, error is reported inside the device info Wwan: more advanced connectivity probing to handle private LTE networks EVE performs periodic connectivity probing for the wwan interface using
0 kommentar(er)
