Open Stack

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 <openstack at fried.cc> wrote:

> 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 that run under apache, like horizon, keystone,
> and placement - their log files can be found wherever apache is set up
> to send 'em.  E.g. [2].
>
> As far as the names go, I *think* we've done away with 'q' as the
> neutron prefixy thing at this point.  On my (pike-ish) setup, the
> devstack neutron API service is quite appropriately called
> devstack at neutron-api.service.
>
> [1] https://docs.openstack.org/devstack/latest/systemd#querying-logs
> [2] http://paste.openstack.org/raw/620754/
>
>
> On 09/08/2017 03:49 PM, Sean Dague wrote:
> > 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
> >> screen-n-cauth.txt.gz
> >> screen-n-cond.txt.gz
> >> screen-n-cpu.txt.gz
> >> screen-n-novnc.txt.gz
> >> screen-n-sch.txt.gz
> >> screen-peakmem_tracker.txt.gz
> >> screen-placement-api.txt.gz
> >> screen-q-agt.txt.gz
> >> screen-q-dhcp.txt.gz
> >> screen-q-l3.txt.gz
> >> screen-q-meta.txt.gz
> >> screen-q-metering.txt.gz
> >> screen-q-svc.txt.gz
> >> screen-s-account.txt.gz
> >> screen-s-container.txt.gz
> >> screen-s-object.txt.gz
> >> screen-s-proxy.txt.gz
> >>
> >> People new to OpenStack don't really know that 'q' means neutron.
> >>
> >>
> >>
> >> On Thu, Sep 7, 2017 at 5:45 AM, Sean Dague <sean at dague.net
> >> <mailto:sean at dague.net>> 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.
> >>     >
> >>     > https://review.openstack.org/#/c/499186/
> >>     <https://review.openstack.org/#/c/499186/> is the patch that will
> remove
> >>     > screen from devstack (which was only left as a fall back for
> things like
> >>     > grenade during Pike). Tests are currently passing on all the
> gating jobs
> >>     > for it. And experimental looks mostly useful.
> >>     >
> >>     > The intent is to merge this in about a week (right before PTG).
> So, if
> >>     > you have a complicated devstack plugin you think might be
> affected by
> >>     > this (and were previously making jobs pretend to be grenade to
> keep
> >>     > screen running), now is the time to run tests against this patch
> and see
> >>     > where things stand.
> >>
> >>     This patch is in the gate and now merging, and with it devstack now
> has
> >>     a single run mode, using systemd units, which is the same between
> test
> >>     and development.
> >>
> >>     Thanks to everyone helping with the transition!
> >>
> >>             -Sean
> >>
> >>     --
> >>     Sean Dague
> >>     http://dague.net
> >>
> >>     ____________________________________________________________
> ______________
> >>     OpenStack Development Mailing List (not for usage questions)
> >>     Unsubscribe:
> >>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> >>     <http://OpenStack-dev-request@lists.openstack.org?subject:
> unsubscribe>
> >>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>     <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> >>
> >>
> >>
> >>
> >> ____________________________________________________________
> ______________
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:
> unsubscribe
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >
> >
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170911/2a2e11c0/attachment.html>