Re: [openstack-dev] [goals][upgrade-checkers] Week R-29 Update

2018-09-22 Thread Sean McGinnis
On Fri, Sep 21, 2018 at 04:19:35PM -0500, Ben Nemec wrote:
> 
> 
> On 09/21/2018 03:53 PM, Matt Riedemann wrote:
> > Updates for this week:
> > 
> > * As bnemec noted in the last update [1], he's making some progress with
> > the oslo.upgradecheck library. He's retrofitting the nova-status upgrade
> > check code to use the library and has a patch up for designate to use
> > it.
> > 
> > * The only two projects that I'm aware of with patches up at this point
> > are monasca [2] and designate [3]. The monasca one is tricky because as
> > I've found going through release notes for some projects, they don't
> > really have any major upgrade impacts so writing checks is not obvious.
> > I don't have a great solution here. What monasca has done is add the
> > framework with a noop check. If others are in the same situation, I'd
> > like to hear your thoughts on what you think makes sense here. The
> > alternative is these projects opt out of the goal for Stein and just add
> > the check code later when it makes sense (but people might forget or not
> > care to do that later if it's not a goal).
> 
> My inclination is for the command to exist with a noop check, the main
> reason being that if we create it for everyone this cycle then the
> deployment tools can implement calls to the status commands all at once. If
> we wait until checks are needed then someone has to not only implement it in
> the service but also remember to go update all of the deployment tools.
> Implementing a noop check should be pretty trivial with the library so it
> isn't a huge imposition.
> 

This was brought up at one point, and I think the preference for those involved
at the time was to still have the upgrade check available, even if it is just a
noop. The reason being as you state that it makes things consistent for
deployment tooling to be able to always run the check, regardless which project
is being done.

Sean

__
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 Project Navigator

2018-09-22 Thread Ian Y. Choi

Thanks a lot for sharing presentation slides and more detail explanation,
which are very helpful for me to understand more context.

I thought that the data were in some external database not in the repo, 
and now clearly figure out how it syncs. [1]



With many thanks,

/Ian

[1] 
https://github.com/OpenStackweb/openstack-org/commit/d8d691848a1677c0a96ddd3029bec645dec8e1f7#diff-fbc5b77edab58d4fe24dd4f7644cc62b


Jimmy McArthur wrote on 9/23/2018 2:26 AM:
We ingest the data from yaml files, at least once per day.  We had a 
bug yesterday that was still reading from the old @ttx repo i/o of the 
new openstack-map repo on git.openstack.org.  That might explain some 
of the issues you were seeing with the project details.  I just pushed 
a fix this morning, so let me know if that cleared up the problem.


The code for the software pages on openstack.org can be found here:
https://github.com/OpenStackweb/openstack-org/tree/master/software/code

The yaml that feeds Project Navigator (Project name, project details, 
etc...)

https://git.openstack.org/cgit/openstack/openstack-map

The yaml that feeds the project tags can be found here:
https://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml

The slides from the PTG presentation can be found here:
https://drive.google.com/file/d/10D-h9uJ456fphluc478KZUJZew0XiiO-/view?usp=sharing

Let me know if I  can provide additional details.

Thanks,
Jimmy


Michael Johnson 
September 21, 2018 at 7:41 PM
Jimmy,

Yes, the tags are correct in
https://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml
but are not correct in Project Navigator.

I am asking where is the git repository with the Project Navigator
code that creates the "Project Details" section?
I am looking for the Project Navigator source code.

Michael

__
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
Jimmy McArthur 
September 21, 2018 at 6:21 PM
The TC tags are indeed in a different repo: 
https://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml


Let me know if this makes sense.

Jimmy


__
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
Michael Johnson 
September 21, 2018 at 4:32 PM
Matt,

I'm a bit confused by your response. I'm not looking for a definition
of the tags, that is very clear.

I'm looking for the source code backing the page that is rendering
which tags a project has.
This code appears to be broken and not rendering the tags correctly
and I wanted to see if I could fix it.

Michael

__
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
Matt Riedemann 
September 21, 2018 at 3:04 PM


Those are down in the project details section of the page, look to 
the right and there is a 'tag details' column. The tags are 
descriptive and link to the details on each tag.


Michael Johnson 
September 21, 2018 at 1:11 PM
Thank you Jimmy for making this available for updates.

I was unable to find the code backing the project tags section of the
Project Navigator pages.
Our page is missing some upgrade tags and is showing duplicate "Stable
branch policy" tags.

https://www.openstack.org/software/releases/rocky/components/octavia

Is there a different repository for the tags code?

Thanks,
Michael

__
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 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 Project Navigator

2018-09-22 Thread Jimmy McArthur
We ingest the data from yaml files, at least once per day.  We had a bug 
yesterday that was still reading from the old @ttx repo i/o of the new 
openstack-map repo on git.openstack.org.  That might explain some of the 
issues you were seeing with the project details.  I just pushed a fix 
this morning, so let me know if that cleared up the problem.


The code for the software pages on openstack.org can be found here:
https://github.com/OpenStackweb/openstack-org/tree/master/software/code

The yaml that feeds Project Navigator (Project name, project details, 
etc...)

https://git.openstack.org/cgit/openstack/openstack-map

The yaml that feeds the project tags can be found here:
https://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml

The slides from the PTG presentation can be found here:
https://drive.google.com/file/d/10D-h9uJ456fphluc478KZUJZew0XiiO-/view?usp=sharing

Let me know if I  can provide additional details.

Thanks,
Jimmy


Michael Johnson 
September 21, 2018 at 7:41 PM
Jimmy,

Yes, the tags are correct in
https://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml
but are not correct in Project Navigator.

I am asking where is the git repository with the Project Navigator
code that creates the "Project Details" section?
I am looking for the Project Navigator source code.

Michael

__
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
Jimmy McArthur 
September 21, 2018 at 6:21 PM
The TC tags are indeed in a different repo: 
https://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml


Let me know if this makes sense.

Jimmy


__
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
Michael Johnson 
September 21, 2018 at 4:32 PM
Matt,

I'm a bit confused by your response. I'm not looking for a definition
of the tags, that is very clear.

I'm looking for the source code backing the page that is rendering
which tags a project has.
This code appears to be broken and not rendering the tags correctly
and I wanted to see if I could fix it.

Michael

__
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
Matt Riedemann 
September 21, 2018 at 3:04 PM


Those are down in the project details section of the page, look to the 
right and there is a 'tag details' column. The tags are descriptive 
and link to the details on each tag.


Michael Johnson 
September 21, 2018 at 1:11 PM
Thank you Jimmy for making this available for updates.

I was unable to find the code backing the project tags section of the
Project Navigator pages.
Our page is missing some upgrade tags and is showing duplicate "Stable
branch policy" tags.

https://www.openstack.org/software/releases/rocky/components/octavia

Is there a different repository for the tags code?

Thanks,
Michael

__
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] Nominations for the "T" Release name

2018-09-22 Thread Tony Breeds
Hey everybody,

Once again, it is time for us to pick a name for our "T" release.

Since the associated Summit will be in Denver, the Geographic
Location has been chosen as "Colorado" (State).

Nominations are now open. Please add suitable names to
https://wiki.openstack.org/wiki/Release_Naming/T_Proposals  between now
and 2018-10-15 23:59 UTC.

In case you don't remember the rules:

* Each release name must start with the letter of the ISO basic Latin
alphabet following the initial letter of the previous release, starting
with the initial release of "Austin". After "Z", the next name should
start with "A" again.

* The name must be composed only of the 26 characters of the ISO basic
Latin alphabet. Names which can be transliterated into this character
set are also acceptable.

* The name must refer to the physical or human geography of the region
encompassing the location of the OpenStack design summit for the
corresponding release. The exact boundaries of the geographic region
under consideration must be declared before the opening of nominations,
as part of the initiation of the selection process.

* The name must be a single word with a maximum of 10 characters. Words
that describe the feature should not be included, so "Foo City" or "Foo
Peak" would both be eligible as "Foo".

Names which do not meet these criteria but otherwise sound really cool
should be added to a separate section of the wiki page and the TC may
make an exception for one or more of them to be considered in the
Condorcet poll. The naming official is responsible for presenting the
list of exceptional names for consideration to the TC before the poll opens.

Let the naming begin.

Tony.

Yours Tony.


signature.asc
Description: PGP signature
__
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] [goals][upgrade-checkers] Week R-29 Update

2018-09-22 Thread Matt Riedemann

On 9/21/2018 4:19 PM, Ben Nemec wrote:
* The only two projects that I'm aware of with patches up at this 
point are monasca [2] and designate [3]. The monasca one is tricky 
because as I've found going through release notes for some projects, 
they don't really have any major upgrade impacts so writing checks is 
not obvious. I don't have a great solution here. What monasca has done 
is add the framework with a noop check. If others are in the same 
situation, I'd like to hear your thoughts on what you think makes 
sense here. The alternative is these projects opt out of the goal for 
Stein and just add the check code later when it makes sense (but 
people might forget or not care to do that later if it's not a goal).


My inclination is for the command to exist with a noop check, the main 
reason being that if we create it for everyone this cycle then the 
deployment tools can implement calls to the status commands all at once. 
If we wait until checks are needed then someone has to not only 
implement it in the service but also remember to go update all of the 
deployment tools. Implementing a noop check should be pretty trivial 
with the library so it isn't a huge imposition.


Yeah, I agree, and I've left comments on the patch to give some ideas on 
how to write the noop check with a description that explains it's an 
initial check but doesn't really do anything. The alternative would be 
to dump the table header for the results but then not have any rows, 
which could be more confusing.


--

Thanks,

Matt

__
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 Project Navigator

2018-09-22 Thread Ian Y. Choi
It would be very nice if the slides of Jimmy's presentation on Wednesday 
during PTG + other slides are shared via this + other (e.g., openstack, 
community, ...) mailing lists.


According to what I discussed with Jimmy on Sep 11, a day before on his 
presentation, and what I learned from seeing some stuff,

I can say that:

- The repo is https://github.com/OpenStackweb/openstack-org and the 
target directory

would be https://github.com/OpenStackweb/openstack-org/tree/master/software
but it definitely seems that data is managed via an external database, 
not a yaml file when I skimmed the repository and sources so briefly.


- Foundation shared that Foundation would do best to aggregate
scattered definitions for consistency, and find a nice place for all 
official projects like Docs, i18n, Congress, etc... on the 
Software/Project Navigator. [1].



With many thanks,

/Ian

[1] 
http://lists.openstack.org/pipermail/openstack-dev/2018-September/134883.html



Michael Johnson wrote on 9/22/2018 9:41 AM:

Jimmy,

Yes, the tags are correct in
https://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml
but are not correct in Project Navigator.

I am asking where is the git repository with the Project Navigator
code that creates the "Project Details" section?
I am looking for the Project Navigator source code.

Michael
On Fri, Sep 21, 2018 at 4:22 PM Jimmy McArthur  wrote:

The TC tags are indeed in a different repo: 
https://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml

Let me know if this makes sense.

Jimmy

Michael Johnson September 21, 2018 at 4:32 PM
Matt,

I'm a bit confused by your response. I'm not looking for a definition
of the tags, that is very clear.

I'm looking for the source code backing the page that is rendering
which tags a project has.
This code appears to be broken and not rendering the tags correctly
and I wanted to see if I could fix it.

Michael

__
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
Matt Riedemann September 21, 2018 at 3:04 PM


Those are down in the project details section of the page, look to the right 
and there is a 'tag details' column. The tags are descriptive and link to the 
details on each tag.

Michael Johnson September 21, 2018 at 1:11 PM
Thank you Jimmy for making this available for updates.

I was unable to find the code backing the project tags section of the
Project Navigator pages.
Our page is missing some upgrade tags and is showing duplicate "Stable
branch policy" tags.

https://www.openstack.org/software/releases/rocky/components/octavia

Is there a different repository for the tags code?

Thanks,
Michael

__
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
Jimmy Mcarthur September 21, 2018 at 8:59 AM
Following up on my (very brief) talk from the PTG, you can now propose changes 
to the Project Navigator by going to 
https://git.openstack.org/cgit/openstack/openstack-map repository

Once your patch is merged, the page should reflect the changes straight away.

Cheers,
Jimmy

__
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 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


Re: [openstack-dev] [docs] Nominating Ian Y. Choi for openstack-doc-core

2018-09-22 Thread Ian Y. Choi

Thanks a lot all for such nomination & agreement!

I would like to do my best after I become doc-core as like what I 
current do,
although I still need the help from so many kind, energetic, and 
enthusiastic OpenStack contributors and core members

on OpenStack documentation and so many projects.


With many thanks,

/Ian

Melvin Hillsman wrote on 9/21/2018 5:31 AM:

++

On Thu, Sep 20, 2018 at 3:11 PM Frank Kloeker > wrote:


Am 2018-09-19 20:54, schrieb Andreas Jaeger:
> On 2018-09-19 20:50, Petr Kovar wrote:
>> Hi all,
>>
>> Based on our PTG discussion, I'd like to nominate Ian Y. Choi for
>> membership in the openstack-doc-core team. I think Ian doesn't
need an
>> introduction, he's been around for a while, recently being deeply
>> involved
>> in infra work to get us robust support for project team docs
>> translation and
>> PDF builds.
>>
>> Having Ian on the core team will also strengthen our
integration with
>> the i18n community.
>>
>> Please let the ML know should you have any objections.
>
> The opposite ;), heartly agree with adding him,
>
> Andreas

++

Frank


__
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



--
Kind regards,

Melvin Hillsman
mrhills...@gmail.com 
mobile: (832) 264-2646


__
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