16 at 2:05 AM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [Congress] Default devstack deployment config
> Hi All,
>
> I too agree from the development point of view, its easier if we have a single
> process.
> But I wa
Hi All,
I too agree from the development point of view, its easier if we have a
single process.
But I was wondering, tempest jobs we run on gate, isn't it better they run
with 3 processes deployed, to make sure it works across processes too?
Just a thought, how about we keep both the options, so
I completely agree with a single process deployment for DevStack. I
ran into issues last week with the multiple process configuration
while I trying to pinpoint an error. I was using the pdb command line
debugger to step through Congress and Oslo Messaging, making a call
from the CLI. More than on
Hi Congress folks,
I'm in favor of single process for devstack default. It's easy to check
logs and tests its feature.
best regards,
Masahito
On 2016/09/13 11:00, Tim Hinrichs wrote:
I'd agree with a single process version of Congress for devstack. I'd
say we should even do that for Newton.
I'd agree with a single process version of Congress for devstack. I'd say
we should even do that for Newton.
Tim
On Mon, Sep 12, 2016 at 6:34 PM Eric K wrote:
> Hi all,
>
> I want to get people’s thoughts regarding what we should set as default
> devstack deployment config for Ocata.
> At the
Hi all,
I want to get people¹s thoughts regarding what we should set as default
devstack deployment config for Ocata.
At the moment, it is set to deploy three processes: API, policy, and
datasource-drivers.
I see some potential arguments against that:
1. For most users installing via devstack, ru
