Re: [openstack-dev] [infra][all] Project Navigator Broken

[Kenny Johnston]

On Thu, Feb 23, 2017 at 8:27 AM, Jeremy Stanley <fu...@yuggoth.org> wrote:

> On 2017-02-23 07:42:19 -0600 (-0600), Kenny Johnston wrote:
> > The project navigator[1] is no longer displaying projects.
>
> I gave the site admins a heads up and it should be fixed as of about
> 5 minutes ago.
>

Awesome, thanks!


> --
> Jeremy Stanley
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Kenny Johnston | irc:kencjohnston | @kencjohnston
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [infra][all] Project Navigator Broken

[Kenny Johnston]

The project navigator[1] is no longer displaying projects.

-- 
Kenny Johnston | irc:kencjohnston | @kencjohnston
[1]https://www.openstack.org/software/project-navigator/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [governance] Where is project:type documented?

[Kenny Johnston]

I saw in the cold upgrades tag page[1] that in order to receive the
designation projects must also be "already tagged as type:service." Where
do we maintain that distinction? I couldn't find it in projects.yaml[2].

-- 
Kenny Johnston | irc:kencjohnston | @kencjohnston
[1]
https://governance.openstack.org/tc/reference/tags/assert_supports-upgrade.html
[2]
https://github.com/openstack/governance/blob/master/reference/projects.yaml
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Project Navigator - Maturity Metrics

[Kenny Johnston]

OpenStackers,

What is the best way to understand the past discussion, and perhaps start a
new conversation about the maturity metrics found in the project
navigator[1]? I don't want to propose anything without knowing more of the
context of why the current metrics and thresholds were chosen.

Thanks!

-- 
Kenny Johnston | irc:kencjohnston | @kencjohnston

[1]https://www.openstack.org/software/project-navigator/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Troubleshooting and ask.openstack.org

[Kenny Johnston]

On Tue, Jun 28, 2016 at 6:49 PM, Steve Martinelli <s.martine...@gmail.com>
wrote:

> I think we want something a bit more organized.
>
> Morgan tossed the idea of a keystone-docs repo, which could have:
>
> - The FAQ Adam is asking about
> - Install guides (moved over from openstack-manuals)
> - A spot for all those neat and unofficial blog posts we do
> - How-to guides
> - etc...
>
> I think it's a neat idea and warrants some discussion. Of course, we don't
> want to be the odd project out.
>

Between the two proposals, I have to imagine that Operators would rather
see a central place for troubleshooting rather than disparate project
specific ones.


> On Tue, Jun 28, 2016 at 6:00 PM, Ian Cordasco <sigmaviru...@gmail.com>
> wrote:
>
>> -Original Message-
>> From: Adam Young <ayo...@redhat.com>
>> Reply: OpenStack Development Mailing List (not for usage questions)
>> <openstack-dev@lists.openstack.org>
>> Date: June 28, 2016 at 16:47:26
>> To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org
>> >
>> Subject:  [openstack-dev] Troubleshooting and ask.openstack.org
>>
>> > Recently, the Keystone team started brainstormin a troubleshooting
>> > document. While we could, eventually put this into the Keystone repo,
>> > it makes sense to also be gathering troubleshooting ideas from the
>> > community at large. How do we do this?
>> >
>> > I think we've had a long enough run with the ask.openstack.org website
>> > to determine if it is really useful, and if it needs an update.
>> >
>> >
>> > I know we getting nuked on the Wiki. What I would like to be able to
>> > generate is Frequently Asked Questions (FAQ) page, but as a living
>> > document.
>> >
>> > I think that ask.openstack.org is the right forum for this, but we need
>> > some more help:
>> >
>> > It seems to me that keystone Core should be able to moderate Keystone
>> > questions on the site. That means that they should be able to remove
>> > old dead ones, remove things tagged as Keystone that do not apply and so
>> > on. I would assume the same is true for Nova, Glance, Trove, Mistral
>> > and all the rest.
>> >
>> > We need some better top level interface than just the tags, though.
>> > Ideally we would have a page where someone lands when troubleshooting
>> > keystone with a series of questions and links to the discussion pages
>> > for that question. Like:
>> >
>> >
>> > I get an error that says "cannot authenticate" what do I do?
>> >
>> > What is the Engine behind "ask.openstack.org?" does it have other tools
>> > we could use?
>>
>> The engine is linked in the footer: https://askbot.com/
>>
>> I'm not sure how much of it is reusable but it claims to be able to do
>> some of the things I think you're asking for except it doesn't
>> explicitly mention deleting comments/questions/etc.
>>
>> --
>> Ian Cordasco
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Kenny Johnston | irc:kencjohnston | @kencjohnston
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

[Kenny Johnston]

On Mon, Apr 4, 2016 at 1:41 PM, Andreas Jaeger <a...@suse.com> wrote:

> On 04/04/2016 12:12 PM, Thierry Carrez wrote:
> > Doug Hellmann wrote:
> >>> [...]
> >>> We would love to add all sufficiently mature projects to the
> >>> installation
> >>> guide because it increases visibility and adoption by operators, but we
> >>> lack resources to develop a source installation mechanism that
> >>> retains as
> >>> much simplicity as possible for our audience.
> >>
> >> I think it would be a big mistake to try to create one guide for
> >> installing all OpenStack projects. As you say, testing what we have
> >> now is already a monumental task and impedes your ability to make
> >> changes.  Adding more projects, with ever more dependencies and
> >> configuration issues to the work the same team is doing would bury
> >> the current documentation team. So I think focusing on the DefCore
> >> list, or even a smaller list of projects with tight installation
> >> integration requirements, makes sense for the team currently producing
> >> the installation guide.
> >
> > Yes, the base install guide should ideally serve as a reference to reach
> > that first step where you have all the underlying services (MySQL,
> > Rabbit) and a base set of functionality (starterkit:compute ?) installed
> > and working. That is where we need high-quality, proactively-checked,
> > easy to understand content.
> >
> > Then additional guides (ideally produced by each project team with
> > tooling and mentoring from the docs team) can pick up from that base
> > first step, assuming their users have completed that first step
> > successfully.
> >
>
> Fully agreed.
>
> I just wrote a first draft spec for all of this and look forward to
> reviews.
>
> I'll enhance some more tomorrow, might copy a bit from above (saw this
> too late).
>
> https://review.openstack.org/301284
>
> Andreas
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
>   SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
>GF: Felix Imendörffer, Jane Smithard, Graham Norton,
>HRB 21284 (AG Nürnberg)
> GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

I commented on the review, but is an alternative solution to appropriately
rename the Install Guide to something like "OpenStack Proof of Concept
Guide" or "OpenStack Starter Kit Guide" and then create the centralized
docs.o.o/install-guides that references both project-specific and
deployment-project install guides?

These guides could then offer more flexibility in install options and
advice.

-- 
Kenny Johnston | freenode:kencjohnston | @kencjohnston
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-infra] Getting Started Guide

[Kenny Johnston]

On Tue, Feb 23, 2016 at 1:49 AM, Andreas Jaeger <a...@suse.com> wrote:

> On 2016-02-23 04:45, Kenny Johnston wrote:
> >   * The Product Work Group (PWG) uses the openstack-user-stories
> > repository and gerrit to review and produce .rst formatted user
> stories
> >   * The PWG is comprised (mostly) of non-developers
> >   * We've found the Getting Started guide a bit inadequate for pointing
> > new PWG contributors to in order to get them up and running with our
> > process, and investigated creating a separate guide of our own to
> > cover getting setup with Windows machines and common issues with
> > corporate firewalls
> >   * I heard at the Ops Summit that the getting started guide should be
> > THE place we point new contributors to learn how to get setup for
> > contributing
> >
> > Would it be palatable to submit patches updating the current guide to
> > cover non-developer getting started instructions?
>
> Yes, please!
>
> Let's try to get this into the Infra Manual, I prefer to have a single
> place for this.
>

OK, great! I'll get our team to put together a patch and submit it.


>
> As usual: It's best to discuss a concrete patch - submit one and then
> let's iterate on that one,
>
> Andreas
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
>   SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
>GF: Felix Imendörffer, Jane Smithard, Graham Norton,
>HRB 21284 (AG Nürnberg)
> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Kenny Johnston
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [openstack-infra] Getting Started Guide

[Kenny Johnston]

   - The Product Work Group (PWG) uses the openstack-user-stories
   repository and gerrit to review and produce .rst formatted user stories
   - The PWG is comprised (mostly) of non-developers
   - We've found the Getting Started guide a bit inadequate for pointing
   new PWG contributors to in order to get them up and running with our
   process, and investigated creating a separate guide of our own to cover
   getting setup with Windows machines and common issues with corporate
   firewalls
   - I heard at the Ops Summit that the getting started guide should be THE
   place we point new contributors to learn how to get setup for contributing

Would it be palatable to submit patches updating the current guide to cover
non-developer getting started instructions?

Thanks!

-- 
Kenny Johnston
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [all][nova][neutron][horizon][keystone][docs] 2016 MAN Ops Meetup - Top 10 Bugs/Features Feedback

[Kenny Johnston]

I had the honor of moderating a session at the MAN Ops Meetup where we
asked operators to identify for the top bugs and feature requests. Whether
it was highlighting command line inconsistencies, improvements needed with
Nova quotas or the need for tenant scrubber tooling (it exists![1]), the
discussion is captured in the sessions etherpad[2].

Please review for additional valuable feedback directly from operators.

Thanks!

-- 
Kenny Johnston
[1]https://github.com/openstack/osops-coda
[2]https://etherpad.openstack.org/p/MAN-ops-Top-10
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] Midcycle summary part 1/6

[Kenny Johnston]

On Feb 16, 2016 11:32 PM, "Jim Rollenhagen"  wrote:
>
> Hi all,
>
> As our midcycle is virtual and split into 6 "sessions" for the sake of
> timezones, we'll be sending a brief summary of each session so that
> folks can catch up before the next one. All of this info should be on
> the etherpad as well.
>
> Session 1/6 was February 16, 1500-2000 UTC.
>
> * We talked about Mitaka priorities and progress, and plans for the
>   remainder of the cycle. Also reminded of timelines.
>   * Feb 29 is the client library deadline; we'll need an ironicclient
> release before then.
>   * Priorities for the remainder of the cycle are laid out in the
> etherpad. Top priorities are network isolation work and manual
> cleaning.
>
> * We discussed the effectiveness of setting cycle priorities.
>   * Consensus was that it was effective overall.
>   * Difficult to keep priorities in mind for reviewers
>   * jroll is going to work on a priorities dashboard, listing progress,
> outstanding patches/topics in gerrit.
>   * Concern there's too many specs for all of us to properly review.
> Deva is going to lead the work on setting up a timebox in our
> meeting to triage a few specs, as far as if it's worth looking at in
> the short term.
>   * Deva and jroll to chat with product working group to see if we can
> mutually help each other, in an attempt to make sure we're working
> on the right things.
+1

We are meeting this week for the PWG mid-cycle. Let us know how we can
help.

>   * We all need to try not to spread ourselves to thin, by assigning
> ourselves to less chunks of work. We also decided that each priority
> should have a group of people invested in it, rather than one, that
> can work together to speed up progress on them.
>
> * We brainstormed on our plans for Newton, and made an exhaustive list
>   of things we'd like to do. We won't be able to do them all, but it's a
>   good start on planning our priorities for Newton and our summit
sessions.
>
> * We made a list of contentious topics that we absolutely want to make
>   sure get discussed during this midcycle. This includes the
>   claims/filter API, boot from volume, and VLAN aware baremetal
>   instances.
>   * jroll to lay out the schedule for these.
>
> * Last, we talked about our gate and how to make it less terrible.
>   * In general, the less voting jobs we have, the less opportunity for
> one to fail at random.
>   * Going to make postgres non-voting.
>   * Going to remove bash ramdisk support and kill that job.
>   * Still working on tinyipa to speed things up.
> * This also allows us to do more tests in parallel.
>   * Discussed writing more tempest deploy tests to test individual
> features, rather than separate jobs.
>   * Also discussed things we want to test better once our gate is
> healthier.
>
> I think that's it from session 1.
>
> As a note, the asterisk setup that Infra provided was *fantastic*, and
> the virtual-ness of this midcycle is going better than I ever expected.
> Thanks again to the infra team for all that you do for us. <3
>
> See you all in the rest of the midcycle! :)
>
> // jim
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [all] PWG - Rolling Upgrades & Updates User Story

[Kenny Johnston]

The Product Working Group[1] is seeking additional reviews on a
"Rolling Updates & Upgrades" User Story[2]. The goal of user stories
is to create a cohesive understanding of the intent and impact of
features which may span projects and releases. If you are working on
or interested in improving upgrades please provide comments.

Thanks!

Kenny Johnston
[1] https://wiki.openstack.org/wiki/ProductTeam
[2] https://review.openstack.org/#/c/274969/

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev