Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

2018-10-24 Thread Chris Dent 

On Wed, 24 Oct 2018, Jean-Philippe Evrard wrote:


On Mon, 2018-10-22 at 07:50 -0700, Morgan Fainberg wrote:

Also, doesn't bitbucket have a git interface now too (optionally)?


It does :)
But I think it requires a new repo, so it means that could as well move
to somewhere else like github or openstack infra :p


Right, so that combined with bitbucket oozing surveys and assorted
other annoyances over me has meant that I've moved paste to github:

https://github.com/cdent/paste

I merged some of the outstanding patches, forced Zane to fix up a few
more Python 3.7 related things, fixed up some of the docs and
released a new version (3.0.0) to pypi:

https://pypi.org/p/Paste

And I published the docs (linked from the new release and the repo) to
a new URL on RTD, as older versions of the docs were not something I
was able to adopt:

https://pythonpaste.readthedocs.io

And some travis-ci stuff.

I didn't bother to bring Paste into OpenDev infra because that felt
like that was indicating a longer and more engaged commitment than
it feels responses here indicated should happen. We want to
encourage migration away. As Morgan stated elsewhere in the thread [1]
work is in progress to make using something else easier for people.

If you want to help with Paste, make some issues and pull requests
in the repo above. Thanks.

Next step? paste.deploy (which is a separate repo).

[1] http://lists.openstack.org/pipermail/openstack-dev/2018-October/135937.html

--
Chris Dent   ٩◔̯◔۶   https://anticdent.org/
freenode: cdent tw: @anticdent__
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] [tc] [api] Paste Maintenance

2018-10-24 Thread Jean-Philippe Evrard 
On Mon, 2018-10-22 at 07:50 -0700, Morgan Fainberg wrote:
> Also, doesn't bitbucket have a git interface now too (optionally)?
> 
It does :)
But I think it requires a new repo, so it means that could as well move
to somewhere else like github or openstack infra :p 


__
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] [tc] [api] Paste Maintenance

2018-10-23 Thread Chris Dent 

On Mon, 22 Oct 2018, Chris Dent wrote:


Thus far I'm not hearing any volunteers. If that continues to be the
case, I'll just keep it on bitbucket as that's the minimal change.


As there was some noise that suggested "if you make it use git I
might help", I put it on github:

https://github.com/cdent/paste

I'm now in the process of getting it somewhat sane for modern
python, however test coverage isn't that great so additional work is
required. Once it seems mostly okay, I'll push out a new version to
pypi.

I welcome assistance from any and all.

And, rather importantly, we also need to take over pastedeploy
as well, as the functionality there is also important. I've started
that ball rolling.

If having it live in my github proves a problem we can easily move
it along somewhere else, but this was the shortest hop.

--
Chris Dent   ٩◔̯◔۶   https://anticdent.org/
freenode: cdent tw: @anticdent__
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] [tc] [api] Paste Maintenance

2018-10-22 Thread Ben Nemec 



On 10/22/18 10:32 AM, Morgan Fainberg wrote:
I can spin up the code and make it available. There is an example 
(highly-flask specific right now, but would be easy to make it generic) 
from keystone [0] has been implemented. Where should this code live? A 
new library? oslo.?  The aforementioned example would need 
"external middleware via config" loading capabilities, but that isn't 
hard to do, just adding an oslo.cfg opt and referencing it.


This seems pretty closely related to oslo.middleware, so maybe we could 
put it there? Everything in there now appears to be actual middleware, 
but a module to allow the use of that middleware isn't too much of a 
stretch.




[0] 
https://github.com/openstack/keystone/blob/master/keystone/server/flask/core.py#L93

Cheers,
--Morgan

On Mon, Oct 22, 2018 at 8:12 AM Sean McGinnis > wrote:


On Mon, Oct 22, 2018 at 07:49:35AM -0700, Morgan Fainberg wrote:
 > I should be able to do a write up for Keystone's removal of paste
*and*
 > move to flask soon.
 >
 > I can easily extract the bit of code I wrote to load our external
 > middleware (and add an external loader) for the transition away
from paste.
 >
 > I also think paste is terrible, and would be willing to help
folks move off
 > of it rather than maintain it.
 >
 > --Morgan
 >

Do I detect a volunteer to champion a cycle goal? :)


__
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] [all] [tc] [api] Paste Maintenance

2018-10-22 Thread Zane Bitter 

On 22/10/18 10:38 AM, Thomas Goirand wrote:

On 10/22/18 12:55 PM, Chris Dent wrote:

My assumption is that it's "something we plan to minimally maintain
because we depend on it". in which case all options would work: the
exact choice depends on whether there is anybody interested in helping
maintaining it, and where those contributors prefer to do the work.


Thus far I'm not hearing any volunteers. If that continues to be the
case, I'll just keep it on bitbucket as that's the minimal change.


Could you please move it to Github, so that at least, it's easier to
check out? Mercurial is always a pain...


FWIW as one data point I probably would have fixed the py37 pull request 
myself instead of just commenting, had it not involved doing:


* A pull request
* on bitbucket
* with Mercurial

(I used to like the Mercurial UI, but it turns out that after_really_ 
learning Git... my brain is full and I can't remember anything else.)


- ZB

__
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] [tc] [api] Paste Maintenance

2018-10-22 Thread Morgan Fainberg 
I can spin up the code and make it available. There is an example
(highly-flask specific right now, but would be easy to make it generic)
from keystone [0] has been implemented. Where should this code live? A new
library? oslo.?  The aforementioned example would need "external
middleware via config" loading capabilities, but that isn't hard to do,
just adding an oslo.cfg opt and referencing it.

[0]
https://github.com/openstack/keystone/blob/master/keystone/server/flask/core.py#L93
Cheers,
--Morgan

On Mon, Oct 22, 2018 at 8:12 AM Sean McGinnis  wrote:

> On Mon, Oct 22, 2018 at 07:49:35AM -0700, Morgan Fainberg wrote:
> > I should be able to do a write up for Keystone's removal of paste *and*
> > move to flask soon.
> >
> > I can easily extract the bit of code I wrote to load our external
> > middleware (and add an external loader) for the transition away from
> paste.
> >
> > I also think paste is terrible, and would be willing to help folks move
> off
> > of it rather than maintain it.
> >
> > --Morgan
> >
>
> Do I detect a volunteer to champion a cycle goal? :)
>
>
> __
> 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] [all] [tc] [api] Paste Maintenance

2018-10-22 Thread Sean McGinnis 
On Mon, Oct 22, 2018 at 07:49:35AM -0700, Morgan Fainberg wrote:
> I should be able to do a write up for Keystone's removal of paste *and*
> move to flask soon.
> 
> I can easily extract the bit of code I wrote to load our external
> middleware (and add an external loader) for the transition away from paste.
> 
> I also think paste is terrible, and would be willing to help folks move off
> of it rather than maintain it.
> 
> --Morgan
> 

Do I detect a volunteer to champion a cycle goal? :)


__
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] [tc] [api] Paste Maintenance

2018-10-22 Thread Morgan Fainberg 
Also, doesn't bitbucket have a git interface now too (optionally)?

On Mon, Oct 22, 2018, 07:49 Morgan Fainberg 
wrote:

> I should be able to do a write up for Keystone's removal of paste *and*
> move to flask soon.
>
> I can easily extract the bit of code I wrote to load our external
> middleware (and add an external loader) for the transition away from paste.
>
> I also think paste is terrible, and would be willing to help folks move
> off of it rather than maintain it.
>
> --Morgan
>
> On Mon, Oct 22, 2018, 07:38 Thomas Goirand  wrote:
>
>> On 10/22/18 12:55 PM, Chris Dent wrote:
>> >> My assumption is that it's "something we plan to minimally maintain
>> >> because we depend on it". in which case all options would work: the
>> >> exact choice depends on whether there is anybody interested in helping
>> >> maintaining it, and where those contributors prefer to do the work.
>> >
>> > Thus far I'm not hearing any volunteers. If that continues to be the
>> > case, I'll just keep it on bitbucket as that's the minimal change.
>>
>> Could you please move it to Github, so that at least, it's easier to
>> check out? Mercurial is always a pain...
>>
>> Cheers,
>>
>> Thomas Goirand (zigo)
>>
>> __
>> 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] [all] [tc] [api] Paste Maintenance

2018-10-22 Thread Morgan Fainberg 
I should be able to do a write up for Keystone's removal of paste *and*
move to flask soon.

I can easily extract the bit of code I wrote to load our external
middleware (and add an external loader) for the transition away from paste.

I also think paste is terrible, and would be willing to help folks move off
of it rather than maintain it.

--Morgan

On Mon, Oct 22, 2018, 07:38 Thomas Goirand  wrote:

> On 10/22/18 12:55 PM, Chris Dent wrote:
> >> My assumption is that it's "something we plan to minimally maintain
> >> because we depend on it". in which case all options would work: the
> >> exact choice depends on whether there is anybody interested in helping
> >> maintaining it, and where those contributors prefer to do the work.
> >
> > Thus far I'm not hearing any volunteers. If that continues to be the
> > case, I'll just keep it on bitbucket as that's the minimal change.
>
> Could you please move it to Github, so that at least, it's easier to
> check out? Mercurial is always a pain...
>
> Cheers,
>
> Thomas Goirand (zigo)
>
> __
> 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] [all] [tc] [api] Paste Maintenance

2018-10-22 Thread Thomas Goirand 
On 10/22/18 12:55 PM, Chris Dent wrote:
>> My assumption is that it's "something we plan to minimally maintain
>> because we depend on it". in which case all options would work: the
>> exact choice depends on whether there is anybody interested in helping
>> maintaining it, and where those contributors prefer to do the work.
> 
> Thus far I'm not hearing any volunteers. If that continues to be the
> case, I'll just keep it on bitbucket as that's the minimal change.

Could you please move it to Github, so that at least, it's easier to
check out? Mercurial is always a pain...

Cheers,

Thomas Goirand (zigo)

__
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] [tc] [api] Paste Maintenance

2018-10-22 Thread Chris Dent 

On Fri, 19 Oct 2018, Thierry Carrez wrote:


Ed Leafe wrote:

On Oct 15, 2018, at 7:40 AM, Chris Dent  wrote:


I'd like some input from the community on how we'd like this to go.


I would say it depends on the long-term plans for paste. Are we planning on 
weaning ourselves off of paste, and simply need to maintain it until that 
can be completed, or are we planning on encouraging its use?


Agree with Ed... is this something we plan to minimally maintain because we 
depend on it, something that needs feature work and that we want to encourage 
the adoption of, or something that we want to keep on life-support while we 
move away from it?


That is indeed the question. I was rather hoping that some people
who are using paste (besides Keystone) would chime in here with what
they would like to do.

My preference would be that we immediately start moving away from it
and keep paste barely on life-support (a bit like WSME which I also
somehow managed to get involved with despite thinking it is horrible).

However, that's not easy to do because the paste.ini files have to
be considered config because of the way some projects and
deployments use them to drive custom middleware and the ordering of
middleware. So we're in for at least a year or so.

My assumption is that it's "something we plan to minimally maintain because 
we depend on it". in which case all options would work: the exact choice 
depends on whether there is anybody interested in helping maintaining it, and 
where those contributors prefer to do the work.


Thus far I'm not hearing any volunteers. If that continues to be the
case, I'll just keep it on bitbucket as that's the minimal change.

My concern with that is my aforementioned feelings of "it is
horrible". It might be better if someone who actually appreciates
Paste was involved as well.

--
Chris Dent   ٩◔̯◔۶   https://anticdent.org/
freenode: cdent tw: @anticdent__
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] [tc] [api] Paste Maintenance

2018-10-19 Thread Thierry Carrez 

Ed Leafe wrote:

On Oct 15, 2018, at 7:40 AM, Chris Dent  wrote:


I'd like some input from the community on how we'd like this to go.


I would say it depends on the long-term plans for paste. Are we planning on 
weaning ourselves off of paste, and simply need to maintain it until that can 
be completed, or are we planning on encouraging its use?


Agree with Ed... is this something we plan to minimally maintain because 
we depend on it, something that needs feature work and that we want to 
encourage the adoption of, or something that we want to keep on 
life-support while we move away from it?


My assumption is that it's "something we plan to minimally maintain 
because we depend on it". in which case all options would work: the 
exact choice depends on whether there is anybody interested in helping 
maintaining it, and where those contributors prefer to do the work.


--
Thierry Carrez (ttx)

__
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] [tc] [api] Paste Maintenance

2018-10-15 Thread Lance Bragstad 
On Mon, Oct 15, 2018 at 8:52 AM Ed Leafe  wrote:

> On Oct 15, 2018, at 7:40 AM, Chris Dent  wrote:
> >
> > I'd like some input from the community on how we'd like this to go.
>
> I would say it depends on the long-term plans for paste. Are we planning
> on weaning ourselves off of paste, and simply need to maintain it until
> that can be completed, or are we planning on encouraging its use?
>
>
Keystone started doing this last release and we're just finishing it up
now. The removal of keystone's v2.0 API and our hand-rolled API dispatching
ended up being the perfect storm for us to say "let's just remove paste
entirely and migrate to something supported".

It helped that we stacked a couple of long-standing work items behind the
paste removal, but it was a ton of work [0]. I think Morgan was going to
put together a summary of how we approached the removal. If the long-term
goal is to help projects move away from Paste, then we can try and share
some of the knowledge we have.

[0] https://twitter.com/MdrnStm/status/1050519620724056065


>
> -- Ed Leafe
>
>
>
>
>
>
> __
> 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] [all] [tc] [api] Paste Maintenance

2018-10-15 Thread Ed Leafe 
On Oct 15, 2018, at 7:40 AM, Chris Dent  wrote:
> 
> I'd like some input from the community on how we'd like this to go.

I would say it depends on the long-term plans for paste. Are we planning on 
weaning ourselves off of paste, and simply need to maintain it until that can 
be completed, or are we planning on encouraging its use?


-- Ed Leafe






__
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] [tc] [api] Paste Maintenance

2018-10-15 Thread Sean McGinnis 
On Mon, Oct 15, 2018 at 01:40:37PM +0100, Chris Dent wrote:
> 
> Back in August [1] there was an email thread about the Paste package
> being essentially unmaintained and several OpenStack projects still
> using it. At that time we reached the conclusion that we should
> investigate having OpenStack adopt Paste in some form as it would
> take some time or be not worth it to migrate services away from it.
> 
> [snip]
> 
> I'd like some input from the community on how we'd like this to go.
> Some options.
> 
> * Chris becomes the de-facto maintainer of paste and I do whatever I
>   like to get it healthy and released.
> 
> * Several volunteers from the community take over the existing
>   bitbucket setup [2] and keep it going there.
> 
> * Several volunteers from the community import the existing
>   bitbucket setup to OpenStack^wOpenDev infra and manage it.
> 
> What would people like? Who would like to volunteer?
> 

Maybe some combination of bullets one and three?

This seems like it would increase visibility in the community if it were moved
under the OpenDev umbrella. Then we could also leverage our release automation
as/when needed. It might also then attract some of the driveby contributions.


__
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] [tc] [api] Paste Maintenance

2018-10-15 Thread Chris Dent 


Back in August [1] there was an email thread about the Paste package
being essentially unmaintained and several OpenStack projects still
using it. At that time we reached the conclusion that we should
investigate having OpenStack adopt Paste in some form as it would
take some time or be not worth it to migrate services away from it.

I went about trying to locate the last set of maintainers and get
access to picking it up. It took a while, but I've now got owner
bits for both bitbucket and PyPI and enthusiastic support from the
previous maintainer for OpenStack to be the responsible party.

I'd like some input from the community on how we'd like this to go.
Some options.

* Chris becomes the de-facto maintainer of paste and I do whatever I
  like to get it healthy and released.

* Several volunteers from the community take over the existing
  bitbucket setup [2] and keep it going there.

* Several volunteers from the community import the existing
  bitbucket setup to OpenStack^wOpenDev infra and manage it.

What would people like? Who would like to volunteer?

At this stage the main piece of blocking work is a patch [3] (and
subsequent release) to get things working happily in Python 3.7.

[1] http://lists.openstack.org/pipermail/openstack-dev/2018-August/132792.html
[2] https://bitbucket.org/ianb/paste
[3] https://bitbucket.org/ianb/paste/pull-requests/41/python-37-support/diff

--
Chris Dent   ٩◔̯◔۶   https://anticdent.org/
freenode: cdent tw: @anticdent__
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