In Juno, there is an issue with instance rebuild (nova evacuate) when trunk
port is associated with that instance. On the target, it is not provisioning
tbr (bridge) and hence 'ovs-vsctl' command failed when adding trunk port.
To me this seems a design gap; but I couldn't pin point it. Can
I want to collect an *extra_resource* info from compute node(s) and add it in
to the compute_nodes table. I like to understand how nova-compute interacts
with DB currently.
Thanks,
Rao Adnan Khan
AT Integrated Cloud (AIC) Development | SE
Software Development & Engineering (SD)
Emai:
Hi,
I couldn't see neutron neutron trunk-create --.. (as suggested at
https://wiki.openstack.org/wiki/Neutron/TrunkPort#neutron_trunk) supported in
neutron agent 2.4.
Can someone tell as to how to create trunk port in Kilo?
Thanks much!
Rao Adnan Khan
AT Integrated Cloud (AIC) Development |
e's a plenty for you to draw inferences.
Hope this helps!
Cheers,
Sudipto
On Monday 20 June 2016 09:07 AM, Jay Pipes wrote:
> On 06/16/2016 04:16 PM, KHAN, RAO ADNAN wrote:
>> I am writing a nova filter that will check for the compute node (max,
>> avg) bandwidth, before insta
I am writing a nova filter that will check for the compute node (max, avg)
bandwidth, before instantiating an instance. What are some of the recommended
tools that can provide this info in real time? Does any openstack component
hold this info already?
Thanks,
Adnan
