[Crowbar] [SPAM] RE: Floating IPs

Chris Sanburn csanburn at redwoodit.com
Fri Jan 27 12:20:29 CST 2012


Did a test "nova-manage floating delete x.y.z.128", waited and found chef adds it back in after a while, so that method isn't permanent either. For now I can just delete the 128 and 129 then allocate before chef replaces them.

-----Original Message-----
From: Kevin Bringard [mailto:kbringard at atti.com] 
Sent: Friday, January 27, 2012 11:49 AM
To: Chris Sanburn; crowbar at lists.us.dell.com
Subject: Re: [Crowbar] [SPAM] RE: Floating IPs

I'd need to look at the recipe to be sure, but I'd wager that by removing the Ips (instead of making them deleted = 1) the recipe failed it's not_if check so chef recreated them.

Justin's method is probably the best... you could pretty easily write a script to iterate over all the Ips you don't want allocated and mark them as deleted.

I'm not sure though, just musing out loud to maybe point you in a direction. Hope it helps! :-)

-- Kevin

From: Chris Sanburn <csanburn at redwoodit.com<mailto:csanburn at redwoodit.com>>
Date: Fri, 27 Jan 2012 08:43:58 -0800
To: "crowbar at lists.us.dell.com<mailto:crowbar at lists.us.dell.com>" <crowbar at lists.us.dell.com<mailto:crowbar at lists.us.dell.com>>
Subject: Re: [Crowbar] [SPAM] RE: Floating IPs

Thanks to all of you, I used mysql commands to examine the floating_ip table in my nova database and saw that it was a mess. I'd already played around with the nova-manage create commands and there was a ton of extra entries.
Got them all deleted so that "nova-manage floating list" just returned an error. Then did:
nova-manage floating create x.y.z.210
nova-manage floating create x.y.z.211
nova-manage floating create x.y.z.212

Went to the Nova Dashboard and could then allocate floating IPs!
Strangely enough, after some time had passed, I find that "nova-manage floating list" now shows everything again, from x.y.z.128 to x.y.z.255, not just the 3 I added.

From: Gregory_Althaus at Dell.com<mailto:Gregory_Althaus at Dell.com> [mailto:Gregory_Althaus at Dell.com]
Sent: Friday, January 27, 2012 11:24 AM
To: jshepher at rackspace.com<mailto:jshepher at rackspace.com>
Cc: Chris Sanburn; crowbar at lists.us.dell.com<mailto:crowbar at lists.us.dell.com>
Subject: RE: [Crowbar] [SPAM] RE: Floating IPs

Yeah - CLI.  Thanks, Justin.

Thanks,
Greg

From: Justin Shepherd [mailto:jshepher at rackspace.com]<mailto:[mailto:jshepher at rackspace.com]>
Sent: Friday, January 27, 2012 10:03 AM
To: Althaus, Gregory
Cc: <csanburn at redwoodit.com<mailto:csanburn at redwoodit.com>>; crowbar
Subject: Re: [Crowbar] [SPAM] RE: Floating IPs

Actually there is a nova CLI way to remove these unwanted floating IPs, on the controller node run the following command (substituting the ip you want to delete):

# nova-manage floating delete x.y.z.128

This will mark that ip as deleted in the database. I usually prefer this method rather than mucking around in the db.

--shep
On Jan 27, 2012, at 9:20 AM, <Gregory_Althaus at Dell.com<mailto:Gregory_Althaus at Dell.com>>
 wrote:

Nope.  Welcome to the poor openstack definition of floating ips.

You need to manually reserve the addresses that you don't want to use.

The easiest way is to just reserve them in the database with mysql commands.  You can also assign them to a vm that is a "fake" holder.

On the controller, you can get the mysql credentials to log in with mysql command.

The table is floating_ips.

There is a reserved flag, I believe.  Set that to true for the ips that you don't want to hand out.

I THINK that will work.   You will also want ot reserve the broadcast address, because it hands that one out as well.


Thanks,
Greg

From: crowbar-bounces On Behalf Of Chris Sanburn
Sent: Friday, January 27, 2012 7:57 AM
To: crowbar
Subject: [Crowbar] Floating IPs

I have a block of public IPs, x.y.z.128/25, that I want to use for my test cloud.  I used the following in my floating IP section for the network barclamp:

    "nova_floating": {
      "add_bridge": false,
      "netmask": "255.255.255.128",
      "broadcast": "x.y.z.255",
      "ranges": {
        "host": {
          "end": "x.y.z.240",
          "start": "x.y.z.210"
        }
      },
      "vlan": 300,
      "use_vlan": true,
      "subnet": "x.y.z.128",
      "conduit": "intf1"
    },

But now when I try to assign floating IPs from the dashboard it only lists x.y.z.128 to be assigned, which won't work because my first usable IP is x.y.z.129, the one I've assigned to my router. Do I have my network barclamp misconfigured or possibly have a conflict with my public IP range, which is a part of the same subnet? It's setup as:

    "public": {
      "add_bridge": false,
      "netmask": "255.255.255.128",
      "router": "x.y.z.129",
      "broadcast": "x.y.z.255",
      "router_pref": 5,
      "ranges": {
        "host": {
          "end": "x.y.z.160",
          "start": "x.y.z.130"
        },
        "dhcp": {
          "end": "x.y.z.200",
          "start": "x.y.z.170"
        }
      },
      "vlan": 300,
      "use_vlan": true,
      "subnet": "x.y.z.128",
      "conduit": "intf1"
    },


_______________________________________________
Crowbar mailing list
Crowbar at dell.com<mailto:Crowbar at dell.com>
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: https://github.com/dellcloudedge/crowbar/wiki




More information about the Crowbar mailing list