I am getting introduced into GlanceSync and I have a question about:
What information do I need to synchronise the images to a region?
Do I need to know the IP and port of the glance server?
You only need the credential to upload the image, i.e. user, password,
tenant name, region name and keystone URL.
The address and port of the glance server is obtained from keystone with
the credential: each server is registered as an endpoint of the "image"
service. This is the way OpenStack works.
Take a look to the documentation of FIWARE GlanceSync to get more details about it.
Related
I have Postfix/Devocet Email server in a US location, and I would like to create a second email server in the India region but the domain name should be XXYYZZ.COM for both the servers. In the API we are finding the user's location, based on the location I will redirect the Emails.
If the user from US/India tries to create an Email box, India user mails need to redirect to the India server and US user mails need to redirect to the US server using a single domain user1#xxyyzz.com.
Bonjour Nanda,
I understand what you are looking for and it is perfectly possible via proxying which dovecot itself can do.
All you need is extra servers which will act as proxy in front of those you use as backend (US server and India server).
Since I have not much information about your backend, I suggest you read about:
Dovecot proxy (https://doc.dovecot.org/configuration_manual/authentication/proxies/)
IMAP+POP proxying (https://wiki1.dovecot.org/HowTo/ImapProxy)
LMTP proxying (https://doc.dovecot.org/configuration_manual/protocols/lmtp_server/).
If the user from US/India tries to create an Email box
By explicitly setting a "host" attribute for each user in your passdb backend (at account creation), you should be able to redirect all requests to a specific host.
I want to have an IP address which when pinged will load all the data sent from a GPS device. The GPS device is configured to send data to an IP address and port. I need to run a server side script to read the data from that port and display it on the IP address. Does GCP provide a static IP address to be purchased and can I use Google Cloud functions or any other GCP tool to read data from that specific port and display it on that IP address? If yes, how could I go about doing this? And is there any other way to implement this using some other platform?
Does GCP provide a static IP address to be purchased
Yes, you can create a static public IP address in Google Cloud.
Public IP addresses are free when attached to running instances/services.
Reserving a Static External IP Address
can I use Google Cloud functions or any other GCP tool to read data
from that specific port and display it on that IP address?
You have not provided enough information to answer this part of your question.
Do not mix multiple topics into one question. Create separate questions. You will get more/better answers.
I have a UCD server, where the External Agent URL is an IP address 9.x. One of the users has requested to change that IP to a hostname, reason being that his agent can't reach that IP because that segment (9.x) is blocked, but they can reach it using the hostname because the agent can use a different route.
What will be the impact to the agents connected to that server if I change the External Agent URL ? Will they need to be updated too ?
I forgot to update before this question. After a discussion with a developer, I found out there is no impact in changing the IP address for the URL. This is transparent for the agents, and they don't need to be updated in any form.
I wanted to provide this update in case someone find it useful in the future.
Regards
I have created a scalable group container with the latest image, which is created by docker file. I have added a domain name and used an SSL certificate with it. However, I am looking to restrict this domain access to public. I would like to allow access to a specific IP range only.
Is there any approach I can use to achieve this? The client asked to allow this domain URL access within their FW network only.
Many Thanks,
Suresh
Actually there isn't any available service/configuration to restrict access to container/containers group in the IBM Containers service on Bluemix.
The only options coming to my mind could be:
filtering directly on each of your group's nodes, using iptables or the specific service configuration
have a 'filter' container (or also an application on runtime) filtering the connections according to the source IP address, for example using a proxy like varnish or ha_proxy on a container it will be pretty simple
I am a newcomer at the web part of programming and I was given a host. I uploaded a simple index.html file with one header(It is correct). If I then try to connect with the nameserver/ip (gotten with PuTTy) , I get an 404 error. I have tried many different stuff about folders , but I could not fix anything
The nameserver IP address is almost certainly not your hosting IP address. The nameserver is the server (probably owned by your host - but possibly an outsourced service) that converts the human readable domain name (such as www.domain.com) to an IP address the computer can connect to (such as 198.252.206.16 - the IP 4 address I get for www.stackoverflow.com). It acts as a giant lookup list of domain names and IP addresses, much like a telephone book or Yellow Pages.
Moreover, as your host will almost certainly be hosting many domains (tens or possibly hundreds) per server, you will need to use a domain name when attempting to connect to your web page - this will be needed for Apache or IIS to know how to route the request/which content to return to the browser. It will do this using the request header sent by the browser when requesting the page. If you are testing locally then localhost/127.0.0.1 will be good enough if you have a single site registered/single set of content in a wwwroot directory (or equivalent). Similarly a virtual server or dedicated server may well respond to requests by IP address if it is the only site/application registered on the server.
To use another real-world analogy, it is a bit like addressing an item of post to a town or village - without including the recipient name, street or house number - and then expecting it to be received and to get a response.
Some hosts provide temporary domain names for you to use before you purchase your domain name or whilst the domain name details are propagated to DNS servers around the world. This usually looks something like-
http://your-user.your-host.com/ or http://server.your-host.com/your-username/
If your host offers such a service then this should normally be detailed in their self-help pages, or the admin area where you set up the site. Clearly such a domain is not intended for "production" use, and you should purchase a domain name before using the site for anything other than testing - if only to allow you the flexibility to move to a new host in the future.
This is not a question for StackOverflow users though, and I strongly suggest you consult your host's documentation or contact them for further assistance.