subject:"\[openstack\-dev\] \[all\]\[ptls\]\[tc\] help needed filling out project\-navigator data"

Re: [openstack-dev] [all][ptls][tc] help needed filling out project-navigator data

2017-04-23 Thread Matt Riedemann


On 4/23/2017 10:13 AM, Matt Riedemann wrote:


Yikes, I'm going to need help with Nova and anything that predates the
v2.0 API. I think there was a 1.1 at some point? Which means there was a
1.0? Does anyone know at what point 2.0 was created? I didn't start
working on OpenStack until ~Folsom.

I can dig as well as anybody, but was just wondering if anyone knows off
the top of their head.



Nevermind, I think I got it:

https://review.openstack.org/#/c/459117/

That was a fun trip down memory lane. You know it's bad when you have to 
download a tar ball from launchpad to find the austin release code.


--

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] [all][ptls][tc] help needed filling out project-navigator data

2017-04-23 Thread Matt Riedemann


On 4/19/2017 9:54 AM, Jimmy McArthur wrote:

Ideally, as far back as your project goes. That way we will have a
complete API history, per release, on the project navigator.  This also
helps us determine the project age.

Thanks!
Jimmy



Yikes, I'm going to need help with Nova and anything that predates the 
v2.0 API. I think there was a 1.1 at some point? Which means there was a 
1.0? Does anyone know at what point 2.0 was created? I didn't start 
working on OpenStack until ~Folsom.


I can dig as well as anybody, but was just wondering if anyone knows off 
the top of their head.


--

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] [all][ptls][tc] help needed filling out project-navigator data

2017-04-21 Thread Jimmy McArthur

Just wanted to say thank you to the projects that have already updated. The 
information you provided has already helped make things more accurate on the 
project nav. 

For other projects, please get this info in the repo as soon as you can. When 
we release the new version the Project Navigator, we would like for it to 
contain correct data for all projects. 

Thank you for your assistance!!
Jimmy




> On Apr 21, 2017, at 7:19 AM, Monty Taylor  wrote:
> 
>> On 04/20/2017 05:03 AM, Andrey Kurilin wrote:
>> Hi folks!
>> 
>> Does it possible to store history of the project without alignment to
>> OpenStack releases?
> 
> Not at the moment - the view is based on OpenStack releases.
> 
> That said - it's a git repo, there's no reason we couldn't store some 
> additional info that the navigator doesn't (yet) need. ... Could you describe 
> a little more what you want to additionally store? Maybe we can come up with 
> something for it...
> 
>> 2017-04-19 17:54 GMT+03:00 Jimmy McArthur > >:
>> 
>>Ideally, as far back as your project goes. That way we will have a
>>complete API history, per release, on the project navigator.  This
>>also helps us determine the project age.
>> 
>>Thanks!
>>Jimmy
>> 
>>>Telles Nobrega 
>>>April 19, 2017 at 9:48 AM
>>>Hi Monty,
>>> 
>>>quick question, how far into past releases should we go?
>>> 
>>>Thanks,
>>> 
>>>--
>>> 
>>>TELLES NOBREGA
>>> 
>>>SOFTWARE ENGINEER
>>> 
>>>Red Hat I 
>>> 
>>>tenob...@redhat.com 
>>> 
>>>
>>>TRIED. TESTED. TRUSTED. 
>>> 
>>>
>>> __
>>>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
>>>
>>>Monty Taylor 
>>>April 18, 2017 at 3:03 PM
>>>Hey everybody!
>>> 
>>>The Foundation is rolling out a new version of the Project
>>>Navigator. One of the things it contains is a section that shows
>>>API versions available for each project for each release. They
>>>asked the TC's help in providing that data, so we spun up a new
>>>repository:
>>> 
>>>  http://git.openstack.org/cgit/openstack/project-navigator-data
>>>
>>> 
>>>that the Project Navigator will consume.
>>> 
>>>We need your help!
>>> 
>>>The repo contains a file for each project for each release with
>>>CURRENT/SUPPORTED/DEPRECATED major versions and also microversion
>>>ranges if they exist. The data is pretty much exactly what
>>>everyone already produces in their version discovery documents -
>>>although it's normalized into the format described by the API-WG:
>>> 
>>> 
>>>
>>> https://specs.openstack.org/openstack/api-wg/guidelines/microversion_specification.html#version-discovery
>>>
>>> 
>>> 
>>> 
>>>What would be really helpful is if someone from each project could
>>>go make a patch to the repo adding the historical (and currently)
>>>info for your project. We'll come up with a process for
>>>maintaining it over time - but for now just crowdsourcing the data
>>>seems like the best way.
>>> 
>>>The README file explains the format, and there is data from a few
>>>of the projects for Newton.
>>> 
>>>It would be great to include an entry for every release - which
>>>for many projects will just be the same content copied a bunch of
>>>times back to the first release the project was part of OpenStack.
>>> 
>>>This is only needed for service projects (something that registers
>>>in the keystone catalog) and is only needed for 'main' APIs (like,
>>>it is not needed, for now, to put in things like Placement)
>>> 
>>>If y'all could help - it would be super great!
>>> 
>>>Thanks!
>>>Monty
>>> 
>>>
>>> __
>>> 
>>>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] [all][ptls][tc] help needed filling out project-navigator data

2017-04-21 Thread Monty Taylor

On 04/20/2017 05:03 AM, Andrey Kurilin wrote:

Hi folks!

Does it possible to store history of the project without alignment to
OpenStack releases?

Not at the moment - the view is based on OpenStack releases.

That said - it's a git repo, there's no reason we couldn't store some
additional info that the navigator doesn't (yet) need. ... Could you
describe a little more what you want to additionally store? Maybe we can
come up with something for it...

2017-04-19 17:54 GMT+03:00 Jimmy McArthur >:

Ideally, as far back as your project goes. That way we will have a
complete API history, per release, on the project navigator. This
also helps us determine the project age.

Thanks!
Jimmy

Telles Nobrega
April 19, 2017 at 9:48 AM
Hi Monty,

quick question, how far into past releases should we go?

Thanks,

TELLES NOBREGA

SOFTWARE ENGINEER

Red Hat I

tenob...@redhat.com

TRIED. TESTED. TRUSTED.

__
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

Monty Taylor
April 18, 2017 at 3:03 PM
Hey everybody!

The Foundation is rolling out a new version of the Project
Navigator. One of the things it contains is a section that shows
API versions available for each project for each release. They
asked the TC's help in providing that data, so we spun up a new
repository:

http://git.openstack.org/cgit/openstack/project-navigator-data

that the Project Navigator will consume.

We need your help!

The repo contains a file for each project for each release with
CURRENT/SUPPORTED/DEPRECATED major versions and also microversion
ranges if they exist. The data is pretty much exactly what
everyone already produces in their version discovery documents -
although it's normalized into the format described by the API-WG:

https://specs.openstack.org/openstack/api-wg/guidelines/microversion_specification.html#version-discovery

What would be really helpful is if someone from each project could
go make a patch to the repo adding the historical (and currently)
info for your project. We'll come up with a process for
maintaining it over time - but for now just crowdsourcing the data
seems like the best way.

The README file explains the format, and there is data from a few
of the projects for Newton.

It would be great to include an entry for every release - which
for many projects will just be the same content copied a bunch of
times back to the first release the project was part of OpenStack.

This is only needed for service projects (something that registers
in the keystone catalog) and is only needed for 'main' APIs (like,
it is not needed, for now, to put in things like Placement)

If y'all could help - it would be super great!

Thanks!
Monty

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

--
Best regards,
Andrey Kurilin.

__
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

Re: [openstack-dev] [all][ptls][tc] help needed filling out project-navigator data

2017-04-20 Thread Andrey Kurilin

Hi folks!

Does it possible to store history of the project without alignment to
OpenStack releases?

2017-04-19 17:54 GMT+03:00 Jimmy McArthur :

> Ideally, as far back as your project goes. That way we will have a
> complete API history, per release, on the project navigator.  This also
> helps us determine the project age.
>
> Thanks!
> Jimmy
>
> Telles Nobrega 
> April 19, 2017 at 9:48 AM
> Hi Monty,
>
> quick question, how far into past releases should we go?
>
> Thanks,
>
> --
>
> TELLES NOBREGA
>
> SOFTWARE ENGINEER
>
> Red Hat I 
>
> tenob...@redhat.com
> 
> TRIED. TESTED. TRUSTED. 
> __
> 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
> Monty Taylor 
> April 18, 2017 at 3:03 PM
> Hey everybody!
>
> The Foundation is rolling out a new version of the Project Navigator. One
> of the things it contains is a section that shows API versions available
> for each project for each release. They asked the TC's help in providing
> that data, so we spun up a new repository:
>
>   http://git.openstack.org/cgit/openstack/project-navigator-data
>
> that the Project Navigator will consume.
>
> We need your help!
>
> The repo contains a file for each project for each release with
> CURRENT/SUPPORTED/DEPRECATED major versions and also microversion ranges if
> they exist. The data is pretty much exactly what everyone already produces
> in their version discovery documents - although it's normalized into the
> format described by the API-WG:
>
>
> https://specs.openstack.org/openstack/api-wg/guidelines/
> microversion_specification.html#version-discovery
>
> What would be really helpful is if someone from each project could go make
> a patch to the repo adding the historical (and currently) info for your
> project. We'll come up with a process for maintaining it over time - but
> for now just crowdsourcing the data seems like the best way.
>
> The README file explains the format, and there is data from a few of the
> projects for Newton.
>
> It would be great to include an entry for every release - which for many
> projects will just be the same content copied a bunch of times back to the
> first release the project was part of OpenStack.
>
> This is only needed for service projects (something that registers in the
> keystone catalog) and is only needed for 'main' APIs (like, it is not
> needed, for now, to put in things like Placement)
>
> If y'all could help - it would be super great!
>
> Thanks!
> Monty
>
> __
>
> 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
>
>


-- 
Best regards,
Andrey Kurilin.
__
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] [all][ptls][tc] help needed filling out project-navigator data

2017-04-19 Thread Jimmy McArthur

Ideally, as far back as your project goes. That way we will have a
complete API history, per release, on the project navigator. This also
helps us determine the project age.

Thanks!
Jimmy

Telles Nobrega
April 19, 2017 at 9:48 AM
Hi Monty,

quick question, how far into past releases should we go?

Thanks,

TELLESNOBREGA

SOFTWARE ENGINEER

Red HatI

tenob...@redhat.com

TRIED. TESTED. TRUSTED.

The Foundation is rolling out a new version of the Project Navigator.
One of the things it contains is a section that shows API versions
available for each project for each release. They asked the TC's help
in providing that data, so we spun up a new repository:

http://git.openstack.org/cgit/openstack/project-navigator-data

that the Project Navigator will consume.

We need your help!

The repo contains a file for each project for each release with
CURRENT/SUPPORTED/DEPRECATED major versions and also microversion
ranges if they exist. The data is pretty much exactly what everyone
already produces in their version discovery documents - although it's
normalized into the format described by the API-WG:

https://specs.openstack.org/openstack/api-wg/guidelines/microversion_specification.html#version-discovery

What would be really helpful is if someone from each project could go
make a patch to the repo adding the historical (and currently) info
for your project. We'll come up with a process for maintaining it over
time - but for now just crowdsourcing the data seems like the best way.

The README file explains the format, and there is data from a few of
the projects for Newton.

It would be great to include an entry for every release - which for
many projects will just be the same content copied a bunch of times
back to the first release the project was part of OpenStack.

This is only needed for service projects (something that registers in
the keystone catalog) and is only needed for 'main' APIs (like, it is
not needed, for now, to put in things like Placement)

If y'all could help - it would be super great!

Thanks!
Monty

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] [all][ptls][tc] help needed filling out project-navigator data

2017-04-19 Thread Telles Nobrega

Hi Monty,

quick question, how far into past releases should we go?

Thanks,

On Tue, Apr 18, 2017 at 5:06 PM Monty Taylor  wrote:

> Hey everybody!
>
> The Foundation is rolling out a new version of the Project Navigator.
> One of the things it contains is a section that shows API versions
> available for each project for each release. They asked the TC's help in
> providing that data, so we spun up a new repository:
>
>http://git.openstack.org/cgit/openstack/project-navigator-data
>
> that the Project Navigator will consume.
>
> We need your help!
>
> The repo contains a file for each project for each release with
> CURRENT/SUPPORTED/DEPRECATED major versions and also microversion ranges
> if they exist. The data is pretty much exactly what everyone already
> produces in their version discovery documents - although it's normalized
> into the format described by the API-WG:
>
>
>
> https://specs.openstack.org/openstack/api-wg/guidelines/microversion_specification.html#version-discovery
>
> What would be really helpful is if someone from each project could go
> make a patch to the repo adding the historical (and currently) info for
> your project. We'll come up with a process for maintaining it over time
> - but for now just crowdsourcing the data seems like the best way.
>
> The README file explains the format, and there is data from a few of the
> projects for Newton.
>
> It would be great to include an entry for every release - which for many
> projects will just be the same content copied a bunch of times back to
> the first release the project was part of OpenStack.
>
> This is only needed for service projects (something that registers in
> the keystone catalog) and is only needed for 'main' APIs (like, it is
> not needed, for now, to put in things like Placement)
>
> If y'all could help - it would be super great!
>
> Thanks!
> Monty
>
> __
> 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
>
-- 

TELLES NOBREGA

SOFTWARE ENGINEER

Red Hat I 

tenob...@redhat.com

TRIED. TESTED. TRUSTED. 
__
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][ptls][tc] help needed filling out project-navigator data

2017-04-18 Thread Monty Taylor


Hey everybody!

The Foundation is rolling out a new version of the Project Navigator. 
One of the things it contains is a section that shows API versions 
available for each project for each release. They asked the TC's help in 
providing that data, so we spun up a new repository:


  http://git.openstack.org/cgit/openstack/project-navigator-data

that the Project Navigator will consume.

We need your help!

The repo contains a file for each project for each release with 
CURRENT/SUPPORTED/DEPRECATED major versions and also microversion ranges 
if they exist. The data is pretty much exactly what everyone already 
produces in their version discovery documents - although it's normalized 
into the format described by the API-WG:



https://specs.openstack.org/openstack/api-wg/guidelines/microversion_specification.html#version-discovery

What would be really helpful is if someone from each project could go 
make a patch to the repo adding the historical (and currently) info for 
your project. We'll come up with a process for maintaining it over time 
- but for now just crowdsourcing the data seems like the best way.


The README file explains the format, and there is data from a few of the 
projects for Newton.


It would be great to include an entry for every release - which for many 
projects will just be the same content copied a bunch of times back to 
the first release the project was part of OpenStack.


This is only needed for service projects (something that registers in 
the keystone catalog) and is only needed for 'main' APIs (like, it is 
not needed, for now, to put in things like Placement)


If y'all could help - it would be super great!

Thanks!
Monty

__
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] [all][ptls][tc] help needed filling out project-navigator data

Re: [openstack-dev] [all][ptls][tc] help needed filling out project-navigator data

Re: [openstack-dev] [all][ptls][tc] help needed filling out project-navigator data

Re: [openstack-dev] [all][ptls][tc] help needed filling out project-navigator data

Re: [openstack-dev] [all][ptls][tc] help needed filling out project-navigator data

Re: [openstack-dev] [all][ptls][tc] help needed filling out project-navigator data

Re: [openstack-dev] [all][ptls][tc] help needed filling out project-navigator data

[openstack-dev] [all][ptls][tc] help needed filling out project-navigator data

8 matches

Site Navigation

Mail list logo

Footer information