From Fedora Project Wiki

(Be consistent with our method of appending to files as root)
No edit summary
Line 24: Line 24:
Allocate an address to use for an instance:
Allocate an address to use for an instance:


  $> euca-allocate-address 192.168.122.150
  $> euca-allocate-address
  ADDRESS 192.168.122.150
  ADDRESS 192.168.122.150
{{admon/note|Note|You do not have to specify a specific address with <code>euca-allocate-address</code>.  If you do not specify an address, it will choose one for you out of the pool of available floating IP addresses.}}


Associate the allocated address with a running instance:
Associate the allocated address with a running instance:


  $> euca-associate-address -i i-00000006 192.168.122.150
  $> euca-associate-address -i i-00000001 192.168.122.150
  ADDRESS 192.168.122.150 i-00000006
  ADDRESS 192.168.122.150 i-00000001


|results=
|results=
Line 48: Line 46:


  $> cd ~/novacreds
  $> cd ~/novacreds
  $> ssh -i nova_key.priv root@192.168.122.150
  $> ssh -i nova_key.priv -o UserKnownHostsFile=/dev/null root@192.168.122.150
 
Check for new errors in the logs:
$> grep -i error /var/log/nova/*.log


If you would like, you can now disassociate and release the address assigned for testing.
If you would like, you can now disassociate and release the address assigned for testing.

Revision as of 10:33, 20 October 2011

The content appearing below may require cleanup
Please improve this article if you can, and move or remove this notice if appropriate.


Description

Set up Floating IPs with OpenStack

Setup

Follow QA:Testcase_launch_an_instance_on_OpenStack

Make sure that nova is configured with the correct public network interface. The default is eth0, but you can change it like: 

$> echo '--public_interface=em1' | sudo tee -a /etc/nova/nova.conf
$> sudo service openstack-nova-network restart

Ensure that ICMP (ping) and SSH are allowed to your instances. 

$> euca-authorize -P icmp -t -1:-1 default 
$> euca-authorize -P tcp -p 22 default

How to test

If you've followed all of the test cases, the private network used for OpenStack instances is 10.0.0.0/24. The purpose of this functionality is to be able to assign a pool of floating public IP addresses to instances, as well.

The details of this test case are a bit specific to the environment you are using to test. For this documentation, we're going to assume that the the OpenStack server's public interface is on the 192.168.122.0/24 subnet. We are going to take an unused address from this subnet, 192.168.122.150, and define it as a floating IP address to be used by OpenStack. 

$> sudo nova-manage floating create 192.168.122.150/31

Allocate an address to use for an instance: 

$> euca-allocate-address
ADDRESS	192.168.122.150

Associate the allocated address with a running instance: 

$> euca-associate-address -i i-00000001 192.168.122.150
ADDRESS	192.168.122.150	i-00000001

Expected Results

Verify that the public IP address got assigned to your public network interface on the OpenStack server. 

$> ip addr
...
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
   link/ether 52:54:00:db:c8:51 brd ff:ff:ff:ff:ff:ff
   inet 192.168.122.58/24 brd 192.168.122.255 scope global eth0
   inet 192.168.122.150/32 scope global eth0

Verify that you can now ssh into the instance using the newly assigned address: 

$> cd ~/novacreds
$> ssh -i nova_key.priv -o UserKnownHostsFile=/dev/null root@192.168.122.150

Check for new errors in the logs: 

$> grep -i error /var/log/nova/*.log

If you would like, you can now disassociate and release the address assigned for testing. 

$> euca-disassociate-address 192.168.122.150
ADDRESS	192.168.122.150
$> euca-release-address 192.168.122.150
ADDRESS	192.168.122.150
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_OpenStack_floating_IPs&oldid=257785"