Hi, thank you all for your answers. Aaron, floating IP delegations from 192.168.22.0/24 and then translating to public IP addresses is my backup plan if this won't work, but I really hope that we can get it working :-)
Martinx, If I would disable NAT at the Neutron L3 then, if I understand it correctly, my currently working set-up (with private subnet) will not function any more which I don't want. I want to use this private IPs and routing as it works right now for *majority* of instances, but on top of that have some instances that I need to bring up publicly. Robert, when trying neutron net-create public --tenant_id a0edd2a531bb41e6b17e0fd644bfd494 --provider:network_type vlan --provider:physical_network default --provider:segmentation_id 1100 --shared True I get: Request Failed: internal server error while processing your request. and in the Neutron's server.log: 2014-04-23 10:25:29.929 5164 ERROR neutron.api.v2.resource [req-7745e39d-7740-4f90-82a2-a0c363617e93 None] create failed 2014-04-23 10:25:29.929 5164 TRACE neutron.api.v2.resource Traceback (most recent call last): 2014-04-23 10:25:29.929 5164 TRACE neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/neutron/api/v2/resource.py", line 87, in resource 2014-04-23 10:25:29.929 5164 TRACE neutron.api.v2.resource result = method(request=request, **args) 2014-04-23 10:25:29.929 5164 TRACE neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/neutron/api/v2/base.py", line 355, in create 2014-04-23 10:25:29.929 5164 TRACE neutron.api.v2.resource allow_bulk=self._allow_bulk) 2014-04-23 10:25:29.929 5164 TRACE neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/neutron/api/v2/base.py", line 605, in prepare_request_body 2014-04-23 10:25:29.929 5164 TRACE neutron.api.v2.resource res_dict[attr] = attr_vals['convert_to'](res_dict[attr]) 2014-04-23 10:25:29.929 5164 TRACE neutron.api.v2.resource TypeError: int() argument must be a string or a number, not 'list' 2014-04-23 10:25:29.929 5164 TRACE neutron.api.v2.resource When I try: neutron net-create public --tenant_id a0edd2a531bb41e6b17e0fd644bfd494 --provider:network_type flat --provider:physical_network default --shared True Invalid input for provider:physical_network. Reason: '[u'default', u'True']' is not a valid string. For being able to use --provider:physical_network I need bridge_mappings in configuration, right? When I add it, my existing GRE network stops working. It seems I am lost here ... Thank you for all the ideas. On Wed, Apr 23, 2014 at 8:44 AM, Robert van Leeuwen < robert.vanleeu...@spilgames.com> wrote: > > I am using GRE tunneling and OVS and have several instances working > perfectly. They get private IP > > addresses (range:10.0.0.0/24) and get routed through my local IP subnet > (192.168.22.0/24) out via > > my HW router's 192.168.22.1. > > This setup works good and I am pretty happy with it. > > >What bothers me is the case where I need to delegate > >some of our instances a direct public IP address, without > >the need for > >any NAT whatsoever. > > You can mix GRE and VLAN based networks. > e.g.: > neutron net-create public --tenant_id $tenant-id --provider:network_type > vlan --provider:physical_network default --provider:segmentation_id > $vlan-id --shared True > > Since this is just a regular VLAN network you can directly patch your > router for the segment also in that VLAN and things should work :) > > Cheers, > Robert van Leeuwen > > > > > > >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
