Yeah, that would be a problem, so what we are doing is to test for covering
all the cases, so finally could decide which way should be used most
gracefully, e.g for hostname in ocf/upstart or use router migration.
On Wed, Oct 29, 2014 at 9:37 PM, Kaya LIU <email address hidden> wrote:
> that's fine..just wondering if the cluster will be confused with the
> same hostname in some scenarios...for example, stop the pacemaker and
> start it again on the active node.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1379607
>
> Title:
> Neutron Gateway services need HA support
>
> Status in “quantum-gateway” package in Juju Charms Collection:
> In Progress
>
> Bug description:
> Support Active/Passive deployment using pacemaker and corosync.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/charms/+source/quantum-gateway/+bug/1379607/+subscriptions
>
Yeah, that would be a problem, so what we are doing is to test for covering
all the cases, so finally could decide which way should be used most
gracefully, e.g for hostname in ocf/upstart or use router migration.
On Wed, Oct 29, 2014 at 9:37 PM, Kaya LIU <email address hidden> wrote:
> that's fine..just wondering if the cluster will be confused with the /bugs.launchpad .net/bugs/ 1379607 /bugs.launchpad .net/charms/ +source/ quantum- gateway/ +bug/1379607/ +subscriptions
> same hostname in some scenarios...for example, stop the pacemaker and
> start it again on the active node.
>
> --
> You received this bug notification because you are a bug assignee.
> https:/
>
> Title:
> Neutron Gateway services need HA support
>
> Status in “quantum-gateway” package in Juju Charms Collection:
> In Progress
>
> Bug description:
> Support Active/Passive deployment using pacemaker and corosync.
>
> To manage notifications about this bug go to:
>
> https:/
>
--
Best Regards.
Hui.
OpenStack Engineer