And I am trying to do the same thing.
I was wondering if you can share your (sanitized) config files.
I am trying to troubleshoot my setup and it’s very frustrating.
I think it would be helpful to the
openstack community to see a working config example.
There are lots of broken config example
Hi, sorry for the delay.
I am attaching my Neutron and Nova configuration files.
nova.conf on Controller:
[DEFAULT]
neutron_metadata_proxy_shared_secret = pa55
network_api_class=nova.network.neutronv2.api.API
neutron_url=http://Controller:9696
neutron_auth_strategy=keystone
neutron_admin_tenant_n
Good idea! Thank you
Can you please share changes to nova and neutron config. That go with this?
I have a Havana cluster with nova net and am trying to migrate my Dev cloud
to neutron with flat physical network.
Regards
Amit
On Apr 25, 2014 11:54 AM, "Matej" wrote:
> Hello Amit, I am replying
Hello Amit, I am replying also to the group, perhaps someone will find this
useful one day :-)
I have two physical networks, let's say they are: 192.168.22.0/24 and
102.203.103.80/29. I have a HW router that is the gateway for both networks
and there are 2 NICs from every node (compute, network/co
Hello Zuo,
thank you the information. You are right, br-int cannot be used in bridge
and that was one of my mistakes.
I was able to solve my issue entirely with the following set-up:
two physical interfaces on each network and compute node and one physical
interface is used for private (192.168.22
Hi, Matej. About
network_vlan_ranges = physnet1
bridge_mappings = physnet1:br-int
I think br-int can not be used here.
You may need another physical interface (or something can function like
this) on all compute nodes, let's say ethX, and create a new bridge like:
ovs-vsctl add-br flatnet
Hello,
To hopefully move into the right way (first phase with using flat
network with private IPs and then moving further to public IPs), I
have removed all previous routers and networks,
my plan now is to use only hardware router (IP 192.168.22.1) and
having a flat network type.
I have added t
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
cor
> 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:
> 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.
>Wha
Hello Matej,
I *think* that the best solution is to disable NAT at the Neutron L3 router
but, I don't know precisely how to do that... This way, your Neutron L3
Router will not make any NAT, so, the instances will be reachable if you
take care of the routing.
In fact, this is precisely the topolo
Sorry, my original reply went to OP directly... Pasted below..
I am not an expert, but I'll take a stab at it...
Since the openstack environment doesn't have a direct connection to the
"public" network, you would not be able to do anything with that network
inside of Opensta
12 matches
Mail list logo
