Openstack Mitaka: i deployed Mitaka with the help of Ansible playbooks. My issue is I am able to create network and assign an IP to instance but unable to ping VM from any of my node. I am not able to create network with FLAT or VLAN. I can just create a network with VXLAN. To check VM to VM communication I am unable to launch console.
Related
I have a cluster of VM (vmWare vCloude) with consul server installed on one of them.
communication between VM is done ONLY view internal network IP. using ExternalIP is blocked. so consul agents installed on other VM are getting the internal IP as advertised address.
I created a few Microservices using k8s that is installed on VM outside the cluster. I can communicate with the cluster ONLY with the ExternalIP.
problem:
consul is returning an advertised address from the VM and it can only be either, internal or external IP. if I choose the internalIP then I cannot use it from outside the cluster and if I use the externalIP, then all agents installed within the cluster will not be able to communicate. I did not find a why of configuring the advertised address with FQDN.
Did anyone faced this issue or have a solution for it?
Thank you,
Lior
I are currently running a Kubernetes cluster on GCP. The cluster has several pods. And I created a new VM in the same network. From Kubernetes pod can ping to the VM but can not connect via internal IP of VM. Please help me find solution for this issue. Thanks
I found solution for this issue. Create a firewall on GCP for VM to allow source from pod IP as 10.0.0.0/8
Due to organizational restrictions all EC2 instances must be spun up inside a VPC. I am running Packer from an on prem server (via a Jenkins pipe) and during the image creation, it spins up an EC2 instance inside this VPC which is assigned a private IP.
Back on my on prem server, Packer is waiting for the instance to start up by querying the private IP assigned to it and there is no connectivity between the on prem Jenkins server and the EC2 instance spun up by Packer. Therefore the process hangs is stuck at Waiting for WinRM to become available forever.
Is there a workaround to this?
I am using the builder of type amazon-ebs
A bastion host on public subnet my help you in this case. You can find the Packer configuration for bastion host here: https://www.packer.io/docs/builders/amazon-ebs.html#communicator-configuration
I created an instance on GCP, but I am not able to access it.
This is similar to this one, but the proposed solution isn't working for me:
Unable to telnet to GCP MemoryStore
I have tried to telnet to it, I am in the same project and region, but apparently I need to be in the same network as it's a private ip, but what if you want to connect using the cloud shell? Also, how would an application running on my local machine access it?
I also included a firewall rule to make sure incoming connections are allowed.
To connect a client to a Cloud Memorystore for Redis instance, the client and the instance must be located in the same region, in same project and in the same VPC network. Please check the “Networking” document where you’ll have information on Basic network settings, limited and unsupported networks, network peering, IP address range.
You can connect to Redis from different GCP products like Compute Engine VM, Google Kubernetes Engine Cluster or Google Kubernetes Engine pod, but you can’t connect directly from the Cloud shell or from your local machine since they are not in your VPC network.
It may also have to do with a missing peering connection to your network. Check in your console at https://console.cloud.google.com/networking/peering/ to see if the peering is set up properly.
Using terraform you can use the following docs: https://www.terraform.io/docs/providers/google/r/redis_instance.html
I have set up an AWS EC2 server, and installed cassandra on it. I am successfully able to connect to cassandra and use it through my local machine using the public IP of my ec2 instance.
Now, I need to be connected to a VPN to continue with my work. But, after connecting to the VPN, I am not able to ssh into the ec2 server or access the installed cassandra.
My security group allows all traffic (IPv4 and IPv6).
I'm new to this, so any help would be appreciated. Thanks!