On 8/4/14, 5:39 PM, mar...@redhat.com mandr...@redhat.com wrote:
On 03/08/14 13:07, Gary Kotton wrote:
Hi,
Happy you asked about this. This is an idea that we have:
Below is a suggestion on how we can improve the metadata service. This
can
be done by leveraging the a Load balancers
On 02/08/14 02:22, Assaf Muller wrote:
Hey Marios, comments inline.
- Original Message -
Hi all,
I have been asked by a colleague about the status of A/A HA for
neutron-* processes. From the 'HA guide' [1], l3-agent and
metadata-agent are the only neutron components that can't be
On 03/08/14 13:07, Gary Kotton wrote:
Hi,
Happy you asked about this. This is an idea that we have:
Below is a suggestion on how we can improve the metadata service. This can
be done by leveraging the a Load balancers supports X-Forwarded-For.The
following link has two diagrams. The first
Hi,
Happy you asked about this. This is an idea that we have:
Below is a suggestion on how we can improve the metadata service. This can
be done by leveraging the a Load balancers supports X-Forwarded-For.The
following link has two diagrams. The first is the existing support (may be
a little
Hi,
The link below is broken. Please see -
https://docs.google.com/drawings/d/19JCirhj2NVVFZ0Vbnsxhyxrm1jjzEAS3ZAMzfBR
C-0E/edit
In short this will give a highly available service without the need for
the metadata proxy.
It will also have one less hop = better performance.
Thanks
Gary
On 8/3/14,
Hi all,
I have been asked by a colleague about the status of A/A HA for
neutron-* processes. From the 'HA guide' [1], l3-agent and
metadata-agent are the only neutron components that can't be deployed in
A/A HA (corosync/pacemaker for a/p is documented as available 'out of
the box' for both).
Hey Marios, comments inline.
- Original Message -
Hi all,
I have been asked by a colleague about the status of A/A HA for
neutron-* processes. From the 'HA guide' [1], l3-agent and
metadata-agent are the only neutron components that can't be deployed in
A/A HA (corosync/pacemaker
