The network in China is not well connected to the rest of the world. We have repository proxy for maven, for pypi, for yarn and so on. Do we have a repository proxy for crates.io?
The Pia S5 is 1:1 compatible with 911 S5 functions and surpasses the 911 S5's Residential Proxy Service.
https://www.piaproxy.com/?utm-source=ggtg&utm-keyword=?1deso2450BR
Related
I have 5 microservices in 5 pods and have deployed each service using specific port using NODE PORT service.
I have a UI app as one service inside another pod which is also exposed using node port service.
Since I can't use pod IP to access urls in UI app as pods live and die so deployed as nodeport service and can I access all 5 services inside UI app seamlessly using respective node port?
Please advise - is this approach going to be reliable?
Yes, you can connect to those Node port services seamlessly.
But remember, you may need higher network bandwidth card and connection (to master nodes) if you get too much traffic to these services.
Also if you have a few master nodes, you can try dedicated master node-ip and nodeport for a service.(If you have 5 master nodes, each service is accessed from one master node's IP etc. This is not mandatory, you can connect to each service using any masterIP:nodeport)
Highly recommend to use load-balancer service for this. If you have baremetal cluster try using MetalLB.
Edit : (after Nagappa LM`s comment)
If its for QA, then no need to worry, but if they perform load test to all the services simultaneously could be a problematic.
Your code change means, only your k8 - deployment is changed, not Kubernetes service. k8 service is where you define nodeport
Our Current Deployment:
1) several back-end devices running an MQTT client connect to an opensource MQTT broker (Mosquitto)
2) Mosquitto is running on a Linux VM and acts as a broker and a communication point between back-end & front-end devices.
3) Several front-end devices (Mobile App / browser based GUI) connect to the broker. some of the front-end devices read & write to the broker (Sub & Pub) while some front-end only read (Sub)
4) Some front-end devices connect for a few minutes & some front ends are always connected.
5) Although the amount of data being transferred is a few kb, it is sometimes fast changing.
6) No TLS is used for the MQTT traffic & it cannot be enabled on the back-end devices.
This setup works for us, but I am looking for a way to scale up and was considering the azure IoT hub, but I am confused if the IoT hub can be used as a broker or I would need additional components to be deployed for acting as a MQTT broker ?
Azure IoT Hub is not a generic MQTT Broker. There is a built-in the device communications for MQTT protocol. More details can be found in the Using the MQTT protocol directly
For exploring the MQTT Devices (virtual devices) with the Azure IoT Hub (without the coding) can be used a small tool Azure IoT Hub Tester
I am developing P2P application in .Net using PNRP
protocol. I have already check tons of materials concerning PRNP and
P2P (SO, Microsoft blog etc). But still cant solve the issues with
clouds. And can`t find exact step -by-step instruction for
proper setting up Clouds and peer name resolving. Everything works
perfectly on local machine (registering and resolving names are ok).
But cloud states for Global and Local always Alone (if i make some
changes sometimes turns to virtual and synchronizing but ended up as Alone). And as result peer names registered on one machine is not
visible on other machine in local network. Ipv6 is supported. Teredo
seems to be working (otherwise global cloud didn't appear):
Scope Id Addr State Name
----- ----- ----- ---------------- -----
3 9 1 Alone LinkLocal_ff00::%9/8
3 5 1 Virtual LinkLocal_ff00::%5/8
1 0 1 Alone Global_
The actions I tried (Win 10 + Win 7):
• disabled firewall for all networks.
• turned on (state: running) and set to Automatic:
○ DNS Client
○ Function Discovery Resource Publication
○ Function Discovery Provider Host
○ SSDP Discovery
○ UPnP Device Host
○ Peer Name Resolution Protocol
○ Peer Networking Grouping
○ Peer Networking Identity Manager
○ PNRP Machine Name Publication Service
• made this actions: https://technet.microsoft.com/en-us/library/dd349394(v=ws.10).aspxLocal
• read and post the same on this blog: https://blogs.msdn.microsoft.com/p2p/2007/07/24/pnrp-debugging-guide-part-1/
• went to Group Policy Editor --> Administrative Templates --> Microsoft Peer-to-Peer Networking Services --> Global Clouds:
○ Turn Off Multicast Bootstrap --> disabled
○ Turn Off PNRP cloud creation --> disabled
○ Set PNRP cloud to resolve only --> disabled
○ Set the Seed Server --> Enabled (leaved empty) and for Linc Local --> Not configured.
But still can`t see registered names of other machines in local
network and resolve peer names. All cloud states are Alone. Any suggestions?
Thank you in advance,
P.S. Ping seed Global_failed, but should not affect the local Cloud?
P.P.S. Ports 3450 and 1900 are opend and added as a rule for Firewall.
Is JIRA supported in GCE? If so, how to make it work?
We have installed 64-bit .bin of JIRA(6.4.1), and opened necessary custom http ports under Networks.
Started JIRA as service, but unable to see it work via browser. No error message than, timed out error!
Any help would be highly appreciated.
Note: We are new to Google Cloud Platform.
Did you enable the http and https services on your instance ? By default the GCE instance does not allow Http and Https traffic, you have to do it manually.
The Jira configuration for Google Compute Engine can be tricky. You need to make sure that:
The firewall rules under Netowrking allows a connection to Jira HTTP port or the HTTP enables in VM properties
The global Networking rules allow TCP traffic on this port
The virtual network have routes configured
If you use Apache as proxy for Jira (recommended) then make sure Apache is configured to point to the Tomcat port
Your Tomcat is configured
You have enabled port allocation using setcap utility
Your local machine firewall enables the connection (in Red Hat ipconfig is enabled by default and blocks the connections)
As you can see it may be tricky to install Jira on Google Cloud. It may be a good idea to use a deployment service like Deploy4Me to do this quickly and automatically.
I have Bonjour (mDNSResponder - Linux version) up and running on a Ubuntu Box (Host A). I have managed to port Avahi to a new platform. As I see, ./mDNSNetMonitor is able to discover the service published by avahi on say different host, Host B (/etc/avahi/services/myservice.service) . This means that Bonjour is able to discover the service published by Avahi.
My question here is, why do I need avahi-compat-libdns_sd library. In the context of experiment, do I need to port avahi-compat-libdns_sd library also to the new platform (Host B)? Note that Avahi running on Host B is 'Dbus enabled'.
Basically it provides a dns_sd.h header file and a backing implementation using avahi to provide compability with the Bonjour SDK interface. So no, you do not need to also port the avahi-compat-libdns_sd part for your experiment.