[Crowbar] Public Interface Setup

Wed Nov 30 01:18:43 CST 2011

So, Because of the way you define the floating ips in Nova, I think it is easiest to keep it as a separate network that you sub-subnet.  

I think the main change it to use the interface from the nova-floating network and some documentation.
Also, I think the sysctl changes to turn on ipforwarding.

This email is more notes for me than anything.  Sorry for the spam.

Thanks,
Greg

-----Original Message-----
From: Kevin Bringard [mailto:kbringard at atti.com] 
Sent: Tuesday, November 29, 2011 5:39 PM
To: Althaus, Gregory
Cc: crowbar
Subject: Re: Public Interface Setup

Yea, I have my nova_floating setup as a subset of the public space; I've just sharded it out manually.

Perhaps adding new directives to the public data bag would do the trick, like a floating_range or something?

On Nov 29, 2011, at 4:21 PM, "Gregory_Althaus at Dell.com" <Gregory_Althaus at Dell.com> wrote:

> Nova-floating is kinda a bad thing, but it should work.  Ideally, nova_floating should be a subset of the public address space.  This is an area that I still need to play with some.  You are correct in finding the piece of code.  Keep going!
> 
> Thanks,
> Greg
> 
> -----Original Message-----
> From: crowbar-bounces On Behalf Of Kevin Bringard
> Sent: Tuesday, November 29, 2011 5:05 PM
> To: crowbar
> Subject: Re: [Crowbar] Public Interface Setup
> 
> Ah, I see it:
> 
> fixed_interface =
> Chef::Recipe::Barclamp::Inventory.get_network_by_type(network,
> "nova_fixed").interface_list.first
> 
> I *think* using that method to get the public and/or nova_floating interfaces should help in building out a more customized nova.conf like so:
> 
> public_interface =
> Chef::Recipe::Barclamp::Inventory.get_network_by_type(network,
> "public").interface_list.first
> nova_floating_interface =
> Chef::Recipe::Barclamp::Inventory.get_network_by_type(network,
> "nova_floating").interface_list.first
> 
> Then, of course, we need to make sure they're getting written out in the proper places in the config file... But that shouldn't be too hard. I'm going to rebuild my deploy tomorrow, so I'll make notes about what specifically I have to change manually and send it along.
> 
> -- Kevin
> 
> On 11/29/11 3:58 PM, "Gregory_Althaus at Dell.com" 
> <Gregory_Althaus at Dell.com>
> wrote:
> 
>> If that is all it is, then I think it should be quick to fix.  There 
>> is an example in there of looking up the public interface.  From that 
>> you need to get the interface, but ...  I'm not in a handy place to 
>> do it right now.
>> 
>> -----Original Message-----
>> From: crowbar-bounces On Behalf Of Kevin Bringard
>> Sent: Tuesday, November 29, 2011 4:52 PM
>> To: crowbar
>> Subject: Re: [Crowbar] Public Interface Setup
>> 
>> Sure thing! I decided to add a public_interface item in the 
>> bc-template-nova.json where I define what I want my public interface 
>> to be. This is far from the correct way to fix it long term, though 
>> (in my opinion).
>> 
>> It looks like this is getting hardcoded at the config.rb recipe for nova:
>> 
>> node[:nova][:public_interface] = "br#{fixed_net["vlan"]}"
>> 
>> I'd imaging we'd want to change this to use something like 
>> node["network"]["networks"]["public"]["device"]... But in the 2 
>> minutes I looked at it, I wasn't sure how to map the conduit back up 
>> to it's physical device.
>> 
>> We'd probably also want to add something.. Maybe in nework.rb that 
>> does some sed love on /etc/sysctl.conf to remove the # from the
>> #net.ipv4.ip_forward=1 line (per my other email).
>> 
>> Anyway, just a couple of thoughts off the top of my head.
>> 
>> -- Kevin
>> 
>> 
>> On 11/29/11 3:43 PM, "Gregory_Althaus at Dell.com"
>> <Gregory_Althaus at Dell.com>
>> wrote:
>> 
>>> Mostly, this is my not getting to test that yet.  :-(  This and any 
>>> other debugging would be awesome.
>>> 
>>> Thanks,
>>> Greg
>>> 
>>> -----Original Message-----
>>> From: crowbar-bounces On Behalf Of Kevin Bringard
>>> Sent: Tuesday, November 29, 2011 12:12 PM
>>> To: crowbar
>>> Subject: [Crowbar] Public Interface Setup
>>> 
>>> Hey all,
>>> 
>>> I managed to get crowbar to deploy a working openstack, but I am 
>>> running into a few issues. The main one (for now) is that it is 
>>> using the br interface as the IF to attach floating_ips to. The 
>>> problem with this is that the interface it's attaching to is the 
>>> internal interface and not the external interface. I have the 
>>> nova_floating stuff setup and it appears to have created the correct 
>>> Ips in the DB, but it is setting -public_interface to the bridge 
>>> device and not the external interface.
>>> 
>>> Is this expected, or is there something special I should be doping 
>>> to make it use the correct interface?
>>> 
>>> Thanks!
>>> 
>>> -- Kevin
>>> 
>>> _______________________________________________
>>> Crowbar mailing list
>>> Crowbar at dell.com
>>> https://lists.us.dell.com/mailman/listinfo/crowbar
>>> For more information: https://github.com/dellcloudedge/crowbar/wiki
>> 
>> _______________________________________________
>> Crowbar mailing list
>> Crowbar at dell.com
>> https://lists.us.dell.com/mailman/listinfo/crowbar
>> For more information: https://github.com/dellcloudedge/crowbar/wiki
> 
> _______________________________________________
> Crowbar mailing list
> Crowbar at dell.com
> https://lists.us.dell.com/mailman/listinfo/crowbar
> For more information: https://github.com/dellcloudedge/crowbar/wiki