service-discovery

Get All Active Service Instances on Service Start

核能气质少年 提交于 2019-12-21 21:32:28
问题 I'm creating a stateless service inside Azure Service Fabric. However, once service starts (or on start of custom communication listener) I need to get addresses of all other instances/partitions of that service. I'm doing so by creating new FabricClient and calling fabricClient.QueryManager.GetPartitionListAsync(serviceUri) . However I'm getting FabricServiceNotFoundException with message Service does not exist. when a first service instance starts running. I couldn't find that in

Get All Active Service Instances on Service Start

馋奶兔 提交于 2019-12-21 21:26:14
问题 I'm creating a stateless service inside Azure Service Fabric. However, once service starts (or on start of custom communication listener) I need to get addresses of all other instances/partitions of that service. I'm doing so by creating new FabricClient and calling fabricClient.QueryManager.GetPartitionListAsync(serviceUri) . However I'm getting FabricServiceNotFoundException with message Service does not exist. when a first service instance starts running. I couldn't find that in

What is the different between putting a separate service discovery and integrate it into the cluster machine in Docker Swarm

巧了我就是萌 提交于 2019-12-19 11:19:34
问题 I am having problem understanding the need of a separated service discovery server while we could register the slave node to the master node at the slave node start-up through whatever protocol. Hosting another service seem redundant to me. 回答1: Docker Swarm is there to create a cluster of hosts running Docker and schedule containers across the cluster. It does not include service discovery, which is provided by a backend service, such as etcd, consul or zookeeper. The first problem: service

WCF Discovery returns hard-coded URL

懵懂的女人 提交于 2019-12-18 15:28:24
问题 The grand design is the following: There is certain application that gets installed as a Windows Service There may be several of these on the network Each of them exposes some interface to the network (think of it as "remote control" or "configuration" - that kind of thing) Then there is another application that acts as a client for that interface (using same analogies - "remote controller" or "configuration tool") The objective of the latter is to sniff out all instances of the former on the

Wifi P2P service discovery works intermittently

人盡茶涼 提交于 2019-12-17 21:42:15
问题 Wifi P2P service discovery is not behaving as expected. I am seeing intermittent issues where the DNSSD listeners are not called always and hence I have no clue of nearby devices running the same app. I am using the following two APIs - one to register a service to be discovered by other devices and the other to discover the nearby services running on other devices. Any idea if I am doing anything wrong here or is there some specific sequence of other android API calls that need to be made

How to programmatically force bluetooth low energy service discovery on Android without using cache

帅比萌擦擦* 提交于 2019-12-17 04:45:46
问题 I am using Android 4.4.2 on a Nexus 7. I have a bluetooth low energy peripheral whose services change when it is rebooted. The android app calls BluetoothGatt.discoverServices(). However Android only queries the peripheral once to discover services, subsequent calls to discoverServices() result in the cached data from the first call, even between disconnections. If I disable/enable the Android bt adapter then discoverServices() refreshes the cache by querying the peripheral. Is there a

Hyperledger fabric 1.2 service discovery error

ぐ巨炮叔叔 提交于 2019-12-14 03:59:10
问题 I use Hyperledger Fabric 1.2 to build a blockchain cluster, which contains 3 peers and 3 orderers. I can successfully deploy and invoke the chaincode via both CLI and Java SDK. Everything works fine. However, when I notice the service discovery function and try to use it, I met two problems. First, after I build the discover tool and try to use it to get some discovered information, I can't access the peer and get the message as follow "failed connecting to discovery service: failed to create

Docker swarm: How to manually set node names?

自古美人都是妖i 提交于 2019-12-12 15:23:31
问题 For some background on my environment: I have docker swarm running on 3 ubuntu 14.04 vagrant boxes. The swarm master is running on 1 machine (with consul) and the other 2 machines are running swarm workers that are joined to the master. I set up the environment following the documentation page https://docs.docker.com/swarm/install-manual/. It is working correctly so that any docker -H :4000 <some_docker_command> run from my master machine works fine. Service discovery is active as I am

Achieve Fault Tolerance with Consul Cluster

坚强是说给别人听的谎言 提交于 2019-12-12 15:17:15
问题 I have created consul server cluster using different ports in localhost. I used below commands for that. server 1: consul agent -server -bootstrap-expect=3 -data-dir=consul-data -ui -bind=127.0.0.1 -dns-port=8601 -http-port=8501 -serf-lan-port=8303 -serf-wan-port=8304 -server-port=8305 -node=node1 server 2: consul agent -server -bootstrap-expect=3 -data-dir=consul-data2 -ui -bind=127.0.0.1 -dns-port=8602 -http-port=8502 -serf-lan-port=8306 -serf-wan-port=8307 -server-port=8308 -node=node2

Is there a Python library for service discovery using SSDP or UPnP?

橙三吉。 提交于 2019-12-12 01:21:51
问题 Is there a library for implementing Simple Service Discovery Protocol(SSDP) via UPnP in Python? Basically, I want to make protocols for SSDP using python. 回答1: http://brisa.garage.maemo.org/doc/html/upnp/ssdp.html 来源: https://stackoverflow.com/questions/4742001/is-there-a-python-library-for-service-discovery-using-ssdp-or-upnp