On Fri, Sep 8, 2017 at 2:17 PM, John Villalovos
wrote:
> Does this mean we can now get more user friendly names for the log files?
>
> Currently I see names like:
> screen-dstat.txt.gz
> screen-etcd.txt.gz
> screen-g-api.txt.gz
> screen-g-reg.txt.gz
>
Miguel-
Sean was in favor of that, and I started looking into it for plain pdb,
but it barely seemed worth it - it would wind up being like three LOC.
I definitely wouldn't oppose it, though. Please add me to that review
if you go for it.
What seemed more interesting to me was a
I wonder if it makes sense to provide a helper script to do what it's
explained on the document.
So we could ~/devstack/tools/run_locally.sh n-sch.
If yes, I'll send the patch.
On Fri, Sep 8, 2017 at 3:00 PM, Eric Fried wrote:
> Oh, are we talking about the logs produced
Oh, are we talking about the logs produced by CI jobs? I thought we
were talking about on your local devstack itself. Because there, I
don't think you shouldn't be seeing log files like this anymore.
Logging is done via systemd and can be viewed via journalctl [1].
The exceptions are things
I would love to. Those were mostly left because devstack-gate (and
related tooling like elasticsearch) is not branch aware, so things get
ugly on the conditionals for changing expected output files.
That might be a good popup infra topic at PTG.
On 09/08/2017 04:17 PM, John Villalovos wrote:
>
Does this mean we can now get more user friendly names for the log files?
Currently I see names like:
screen-dstat.txt.gz
screen-etcd.txt.gz
screen-g-api.txt.gz
screen-g-reg.txt.gz
screen-ir-api.txt.gz
screen-ir-cond.txt.gz
screen-keystone.txt.gz
screen-n-api-meta.txt.gz
screen-n-api.txt.gz
On Thu, Sep 7, 2017 at 7:07 PM, Sean Dague wrote:
> On 09/07/2017 04:54 PM, Eric Fried wrote:
>
>> All-
>>
>> The plain pdb doc patch [1] is merging.
>>
>> On clarkb's suggestion, I took a look at remote-pdb [2], and it
>> turned
>> out to be easy-peasy to use. I
On 09/07/2017 04:54 PM, Eric Fried wrote:
All-
The plain pdb doc patch [1] is merging.
On clarkb's suggestion, I took a look at remote-pdb [2], and it turned
out to be easy-peasy to use. I submitted a followon doc patch for that [3].
Thanks, John, for speaking up and
All-
The plain pdb doc patch [1] is merging.
On clarkb's suggestion, I took a look at remote-pdb [2], and it turned
out to be easy-peasy to use. I submitted a followon doc patch for that [3].
Thanks, John, for speaking up and getting this rolling.
On Thu, Sep 7, 2017 at 1:28 PM, Sean Dague wrote:
> On 09/07/2017 01:52 PM, Eric Fried wrote:
>
>> John-
>>
>> You're not the only one for whom the transition to systemd has
>> been
>> painful.
>>
>> However...
>>
>> It *is* possible (some would argue just
On Thu, Sep 7, 2017 at 11:52 AM, Eric Fried wrote:
> John-
>
> You're not the only one for whom the transition to systemd has been
> painful.
>
> However...
>
> It *is* possible (some would argue just as easy) to do all things
> with
> systemd that
On 09/07/2017 01:52 PM, Eric Fried wrote:
John-
You're not the only one for whom the transition to systemd has been
painful.
However...
It *is* possible (some would argue just as easy) to do all things with
systemd that were done with screen.
For starters,
I completely agree with you here John. I still prefer to use screen for
my devstack installs, it's just far far easier to use for development.
systemd is a pain to use in comparison.
This is a major step backwards for developers.
:(
On Thu, Sep 7, 2017 at 1:29 PM, John Griffith
John-
You're not the only one for whom the transition to systemd has been
painful.
However...
It *is* possible (some would argue just as easy) to do all things with
systemd that were done with screen.
For starters, have you seen [1] ?
Though looking at
FWIW I realize my opinion doesn't count here particularly since this
already merged, BUT I also realize that it didn't count before it
merged either as the response I was given was "I don't use
debuggers". It's unfortunate, perhaps I'm really the only one that
has counter opinions on
On Thu, Sep 7, 2017 at 11:29 AM, John Griffith
wrote:
> Please don't, some of us have no issues with screen and use it extensively
> for debugging. Unless there's a viable option using systemd I fail to
> understand why this is such a big deal. I've been using
Please don't, some of us have no issues with screen and use it extensively
for debugging. Unless there's a viable option using systemd I fail to
understand why this is such a big deal. I've been using devstack in screen
for a long time without issue, and I still use rejoin that supposedly
didn't
w00t!
On Thu, Sep 7, 2017 at 8:45 AM, Sean Dague wrote:
> On 08/31/2017 06:27 AM, Sean Dague wrote:
>> The work that started last cycle to make devstack only have a single
>> execution mode, that was the same between automated QA and local, is
>> nearing it's completion.
>>
>>
On 08/31/2017 06:27 AM, Sean Dague wrote:
> The work that started last cycle to make devstack only have a single
> execution mode, that was the same between automated QA and local, is
> nearing it's completion.
>
> https://review.openstack.org/#/c/499186/ is the patch that will remove
> screen
19 matches
Mail list logo