[ospurge] looking for project owners / considering adoption
flux.adam at gmail.com
Fri Nov 1 02:29:44 UTC 2019
Yeah, I've halted work for now until the summit when I can talk to other
folks (at the related meeting that is scheduled) -- and I believe I agree
that merging this functionality into the SDK is the best path forward. I
will probably be able to assist somewhat with that as well. I wish I knew
about the discussions that happened last year, I could already have been
working on that... T_T
On Wed, Oct 30, 2019 at 7:43 AM Artem Goncharov <artem.goncharov at gmail.com>
> Hi Adam,
> Since I need this now as well I will start working on implementation how
> it was agreed (in SDK and in OSC) during last summit by mid of November.
> There is no need for discussing this further, it just need to be
> implemented. Sad that we got no progress in half a year.
> Artem (gtema).
> On 30. Oct 2019, at 14:26, Adam Harwell <flux.adam at gmail.com> wrote:
> That's too bad that you won't be at the summit, but I think there may
> still be some discussion planned about this topic.
> Yeah, I understand completely about priorities and such internally. Same
> for me... It just happens that this IS priority work for us right now. :)
> On Tue, Oct 29, 2019, 07:48 Adrian Turjak <adriant at catalyst.net.nz> wrote:
>> My apologies I missed this email.
>> Sadly I won't be at the summit this time around. There may be some public
>> cloud focused discussions, and some of those often have this topic come up.
>> Also if Monty from the SDK team is around, I'd suggest finding him and
>> having a chat.
>> I'll help if I can but we are swamped with internal work and I can't
>> dedicate much time to do upstream work that isn't urgent. :(
>> On 17/10/19 8:48 am, Adam Harwell wrote:
>> That's interesting -- we have already started working to add features and
>> improve ospurge, and it seems like a plenty useful tool for our needs, but
>> I think I agree that it would be nice to have that functionality built into
>> the sdk. I might be able to help with both, since one is immediately useful
>> and we (like everyone) have deadlines to meet, and the other makes sense to
>> me as a possible future direction that could be more widely supported.
>> Will you or someone else be hosting and discussion about this at the
>> Shanghai summit? I'll be there and would be happy to join and discuss.
>> On Tue, Oct 15, 2019, 22:04 Adrian Turjak <adriant at catalyst.net.nz>
>>> I tried to get a community goal to do project deletion per project, but
>>> we ended up deciding that a community goal wasn't ideal unless we did
>>> build a bulk delete API in each service:
>>> What we decided on, but didn't get a chance to work on, was building
>>> into the OpenstackSDK OS-purge like functionality, as well as reporting
>>> functionality (of all project resources to be deleted). That way we
>>> could have per project per resource deletion logic, and all of that
>>> defined in the SDK.
>>> I was up for doing some of the work, but ended up swamped with internal
>>> work and just didn't drive or push for the deletion work upstream.
>>> If you want to do something useful, don't pursue OS-Purge, help us add
>>> that official functionality to the SDK, and then we can push for bulk
>>> deletion APIs in each project to make resource deletion more pleasant.
>>> I'd be happy to help with the work, and Monty on the SDK team will most
>>> likely be happy to as well. :)
>>> On 1/10/19 11:48 am, Adam Harwell wrote:
>>> > I haven't seen much activity on this project in a while, and it's been
>>> > moved to opendev/x since the opendev migration... Who is the current
>>> > owner of this project? Is there anyone who actually is maintaining it,
>>> > or would mind if others wanted to adopt the project to move it forward?
>>> > Thanks,
>>> > --Adam Harwell
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss