Thanks a lot Brian.
-Paddu
On 8/13/15, 7:59 AM, Brian Haley brian.ha...@hp.com wrote:
On 08/13/2015 04:04 AM, Padmanabhan Krishnan wrote:
Hello,
Is there a Neutron public API to get the list of router ports?
Something similar
to what the command neutron router-port-list {tenant} gives
Hello,Is there a Neutron public API to get the list of router ports? Something
similar to what the command neutron router-port-list {tenant} gives.I wasn't
able to find one in the Neutron API doc as well as in
neutronclient/v2_0/client.py.
I think with a combination of subnet_show, port_list,
Hello,
I am seeing some weird behavior in my setup and would really appreciate if
someone could clarify a few things below:
Setup: Simple two node. One with control+compute (Node1) and another a compute
(Node2). Since, Node2 is running low in HW, I create a AvlZone putting only
Node2 so that I
.
[1] -
http://specs.openstack.org/openstack/neutron-specs/specs/kilo/neutron-ipam.html
From: Padmanabhan Krishnan kpr...@yahoo.com
Reply-To: Padmanabhan Krishnan kpr...@yahoo.com
Date: Thursday, February 5, 2015 at 1:47 AM
To: John Belamaric jbelama...@infoblox.com, OpenStack Development Mailing
authoritative) IPAM system. This could lead to
duplicate IP issues since each VM is deciding its own IP without any
centralized coordination. I wouldn't recommend this approach to managing your
IP space.
John
From: Padmanabhan Krishnan kpr...@yahoo.com
Reply-To: Padmanabhan Krishnan kpr...@yahoo.com
Date
an
update_port when the IP address becomes available.
I don't see that option. Please correct me if I am wrong.
Thanks,Paddu
On Thursday, December 18, 2014 7:59 AM, Padmanabhan Krishnan
kpr...@yahoo.com wrote:
Hi John,Thanks for the pointers. I shall take a look and get back.
Regards
-ipam[2]
https://etherpad.openstack.org/p/neutron-dhcp-org[3]
https://blueprints.launchpad.net/neutron/+spec/dhcp-relay
John
From: Padmanabhan Krishnan kpr...@yahoo.com
Reply-To: Padmanabhan Krishnan kpr...@yahoo.com, OpenStack Development
Mailing List (not for usage questions) openstack-dev
Hello,I have a question regarding the enable_dhcp option when creating a
network.
When a VM is attached to a network where enable_dhcp is False, I understand
that the DHCP namespace is not created for the network and the VM does not get
any IP address after it boots up and sends a DHCP
/17/14 09:15, Padmanabhan Krishnan wrote:
Hello,I have a question regarding the enable_dhcp option when creating a
network.
When a VM is attached to a network where enable_dhcp is False, I understand
that the DHCP namespace is not created for the network and the VM does not get
any IP address
This means whatever tools the operators are using, it need to make sure the IP
address assigned inside the VM matches with Openstack has assigned to the
port.Bringing the question that i had in another thread on the same topic:
If one wants to use the provider DHCP server and not have
Hello,
I have two Openstack nodes (controller Compute and a Compute). VM's are
getting launched fine on the node that also acts as the controller. But, the
VM's that are scheduled on the compute node seems to go to
error state. I am running Icehouse Master version and my ML2 type driver is GRE
Hello,
I have two Openstack nodes (controller Compute and a Compute). VM's are
getting launched fine on the node that also acts as the controller. But, the
VM's that are scheduled on the compute node seems to go to error state. I am
running Icehouse version and my ML2 type driver is VXLAN. I
will
just
have the br-eth/r-ex and its port connecting to the fabric just like if the
type was VLAN. If we had
to do this, the changes has to be in neutron agent code.
Is this the right way to go or any
suggestions?
Thanks,
Paddu
On Wednesday, March 26, 2014 11:28 AM, Padmanabhan Krishnan kpr
Hello,
I have a topology where my Openstack compute nodes are connected to the
external switches. The fabric comprising of the switches support more than 4K
segments. So, i should be able to create more than 4K networks in Openstack.
But, the VLAN to be used for communication with the switches
14 matches
Mail list logo