I installed openstack using packstack. But I don't know how to configure network.
I want to access my instance using ssh like this.
Is it possible to do this?
By default, Packstack creates an "external" network that is entirely contained inside the host. This is great for creating a cloud without any knowledge of the network environment, but prevents you from accessing instances from outside.
Configure your Packstack so that its external network is your network. This is documented at https://www.rdoproject.org/networking/neutron-with-existing-external-network/.
Actually, without external network its not possible.Your instance should have external(public) ip.I'm using this way but you have other option like proxy.
if your Centos7 machine can connect your instance;
Use HaProxy at Centos machine and proxy instance ssh port to specific centos7 port and connect using this port.I'm using this way on microstack.
Related
I am trying to install openstack on a single node server.
I need to access Instances from internet.
I am new to openstack, so I spent some time trying to get it work correctly but without success. I tried devstack but it is not persistent after reboot.
For microstack, it is not configurable.
I need to assign Public IPs to instances. I have 2 physical networks. I tried with external network, but I don't found an option how to do that.
Did anyone successfully installed openstack on a single machine, and is there a way to expose instances to bring them puclic IPs from a pool.
Thanks in advance.
I have a scenario where I want to establish a communication between the docker container running inside a Virtual machine and console (the VM is present on the same console). This work is to be done on SUSE Linux. How can this be done?
Create a external nat int the host using something `docker network create.
Mention this network while creating the container.
We are currently using Openstack newtown. We can access the API using client on public endpoint from any computer, but the vm don't have access to it, they can ping the IP and dns name but can't curl or access using openstack-client. How can we allow connection from VM to API ?
Assuming your public API endpoint is externally accessible, the network on which your virtual machine resides will need external access. This can be achieved in a few different ways, depending on your current configuration. You can create a Neutron provider network/subnet which will provide access to a physical network and gateway to the outside world. You can then boot your instance directly on the provider network. More information on Neutron provider networks can be found at docs.openstack.org.
The problem is that floating IP don't give the route of my external network.
I add route using neutron and now all is working perfectly. for info the command is:
neutron router-update demo-routeur --routes type=dict list=true destination=192.168.0.27/27,nexthop=10.0.0.1
I am trying to setup a consul server in an openstack cluster. I have the server provisioned and have associated an IP with the server that is accessible from vagrants on developer machines.
I am able to join the server from a local vagrant if I use the -advertise flag on the consul agent -server command and use the floating ip I set. However, I am provisioning the server with salt and need to the machine to be able to determine that IP automatically.
By default, the server is using its bind address which is set to its 10.x.x.x local IP. That local IP is the only one I seem to be able to easily determine.
Is there a way to get an instance's floating ip(s)?
Bonus points: Is there a way to get an instances name?
The information you are looking for is available to an instance using the Openstack metadata service. It is basically a REST API that an instance can hit to get information specific to this instance. See more information here:
http://docs.openstack.org/grizzly/openstack-compute/admin/content/metadata-service.html
You should be able to get both the instance name and its floating ip (look for "public-ipv4")
I have Meteor running on a local virtual machine on Windows which is accessible using the IP address of 192.168.56.111
When I use Robomongo, I use this IP address and point it to port 3001 and I an unable to connect.
Should I expect it to connect? If not, is there anything I need to do to get it to connect?
Setup SSH server on Windows and then simply create SSH tunnel:
ssh -L27018:192.168.56.111:3001 user#host
After that open Robomongo and connect to localhost:27018. That's it!
This technique I'm using successfully to connect to production database.
With meteor the database that runs is bound to 127.0.0.1, so it will not be accessible on other IPs. I think this was done for a security reason, though not sure.
You should use the local IP/127.0.0.1 instead of 192.168.56.11.