Dear All,
I am investigating enabling Mirriored queues in my OpenStack cluster.
I have 3 controllers and a 10G network.
One of the videos in Barcelona summit suggested not to do so :
https://www.youtube.com/watch?v=bpmgxrPOrZw
Because it slows down the cloud significantly.
So my question is,
What do you mean by the instance has an attached volume ?
Have you started the instance from a volume ?
On Fri, Jun 23, 2017 at 8:06 AM, Ignazio Cassano
wrote:
> Hi All,
> using ocata dashboard I am trying to create instance snapshots.
> If the instance has an attached volume, the image created
This is on newton :
cinder-api --version
9.0.0
On Tue, Jan 31, 2017 at 5:00 PM, Ahmed Mostafa
wrote:
> Hello
>
> Anyone else seeing there errors in cinder api?
>
> [ 8092] WARNING: Extension SchedulerHints: Cannot extend resource volumes:
> No such resource
> [ 809
Hello
Anyone else seeing there errors in cinder api?
[ 8092] WARNING: Extension SchedulerHints: Cannot extend resource volumes:
No such resource
[ 8092] WARNING: Extension VolumeTenantAttribute: Cannot extend resource
volumes: No such resource
[ 8092] WARNING: Extension SnapshotActions: Cannot ex
Thank you everyone
The problem was in the image, it does not dhcp
On Sun, 11 Dec 2016 at 16:13, Ahmed Mostafa
wrote:
> So i was able to solve the problem of nova not creating ports, however
> when it creates ports it creates normal ovs ports and they always stays
> down because they a
baremetal,
and binding type of unbound, yet it always stays down and i can not reach
or ping the instance
Any thoughts ?
Thank you
On Sat, 10 Dec 2016 at 23:25, Ahmed Mostafa
wrote:
> Hello all,
>
> I have tried to use ironic in stand alone mode and i tried to integerate
> it with nov
Hello all,
I have tried to use ironic in stand alone mode and i tried to integerate it
with nova
When i use it in stand alone mode, i craate a neutron port of vnic_type
baremetal and i assign it to the ironic node using extra/vif_port_id, i am
able to provision the node, but not able to get conne
Actually it is not authenticating it self against keystone, it is
communicating directly to nova by using a ketstone client
in neutron.conf you have to options which are set to True by default, they
are
notify_nova_on_port_status_changes
notify_nova_on_port_data_changes
If you set both of them
Hello all,
I am a bit confuse by the following parameters :
notify_nova_on_port_status_change
notify_nova_on_port_data_change
The reason i am confused is that i see if there either of these values is
set to true (Which is the default), neutron will create a notiva notifier
and send these events