[ospurge] looking for project owners / considering adoption
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
On 2019-09-30 16:48:38 -0600 (-0600), 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?
The Gerrit ACL for x/ospurge indicates these folks are the current maintainers:
https://review.opendev.org/#/admin/groups/ospurge-core
You could consider attempting to reach out to them directly if you haven't already.
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: https://review.opendev.org/#/c/639010/ https://etherpad.openstack.org/p/community-goal-project-deletion https://etherpad.openstack.org/p/DEN-Deletion-of-resources https://etherpad.openstack.org/p/DEN-Train-PublicCloudWG-brainstorming
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. :)
Cheers, Adrian
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
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.
--Adam
On Tue, Oct 15, 2019, 22:04 Adrian Turjak adriant@catalyst.net.nz wrote:
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: https://review.opendev.org/#/c/639010/ https://etherpad.openstack.org/p/community-goal-project-deletion https://etherpad.openstack.org/p/DEN-Deletion-of-resources https://etherpad.openstack.org/p/DEN-Train-PublicCloudWG-brainstorming
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. :)
Cheers, Adrian
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
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.
--Adam
On Tue, Oct 15, 2019, 22:04 Adrian Turjak <adriant@catalyst.net.nz mailto:adriant@catalyst.net.nz> wrote:
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: https://review.opendev.org/#/c/639010/ https://etherpad.openstack.org/p/community-goal-project-deletion https://etherpad.openstack.org/p/DEN-Deletion-of-resources https://etherpad.openstack.org/p/DEN-Train-PublicCloudWG-brainstorming 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. :) Cheers, Adrian 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
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@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.
--AdamOn Tue, Oct 15, 2019, 22:04 Adrian Turjak adriant@catalyst.net.nz wrote:
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: https://review.opendev.org/#/c/639010/ https://etherpad.openstack.org/p/community-goal-project-deletion https://etherpad.openstack.org/p/DEN-Deletion-of-resources https://etherpad.openstack.org/p/DEN-Train-PublicCloudWG-brainstorming
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. :)
Cheers, Adrian
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
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.
Regards, Artem (gtema).
On 30. Oct 2019, at 14:26, Adam Harwell flux.adam@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@catalyst.net.nz mailto:adriant@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.
--AdamOn Tue, Oct 15, 2019, 22:04 Adrian Turjak <adriant@catalyst.net.nz mailto:adriant@catalyst.net.nz> wrote: 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: https://review.opendev.org/#/c/639010/ https://review.opendev.org/#/c/639010/ https://etherpad.openstack.org/p/community-goal-project-deletion https://etherpad.openstack.org/p/community-goal-project-deletion https://etherpad.openstack.org/p/DEN-Deletion-of-resources https://etherpad.openstack.org/p/DEN-Deletion-of-resources https://etherpad.openstack.org/p/DEN-Train-PublicCloudWG-brainstorming https://etherpad.openstack.org/p/DEN-Train-PublicCloudWG-brainstorming
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. :)
Cheers, Adrian
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
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
--Adam
On Wed, Oct 30, 2019 at 7:43 AM Artem Goncharov artem.goncharov@gmail.com wrote:
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.
Regards, Artem (gtema).
On 30. Oct 2019, at 14:26, Adam Harwell flux.adam@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@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.
--AdamOn Tue, Oct 15, 2019, 22:04 Adrian Turjak adriant@catalyst.net.nz wrote:
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: https://review.opendev.org/#/c/639010/ https://etherpad.openstack.org/p/community-goal-project-deletion https://etherpad.openstack.org/p/DEN-Deletion-of-resources https://etherpad.openstack.org/p/DEN-Train-PublicCloudWG-brainstorming
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. :)
Cheers, Adrian
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
Hi,
A Forum session is planned for this topic, Monday 11:40. Suites perfect to continue the discussions there as well.
https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24407/...
BR, Tobias
Tobias Rydberg Senior Developer Twitter & IRC: tobberydberg
www.citynetwork.eu | www.citycloud.com
INNOVATION THROUGH OPEN IT INFRASTRUCTURE ISO 9001, 14001, 27001, 27015 & 27018 CERTIFIED
On 2019-10-30 15:43, Artem Goncharov wrote:
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.
Regards, Artem (gtema).
On 30. Oct 2019, at 14:26, Adam Harwell <flux.adam@gmail.com mailto:flux.adam@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@catalyst.net.nz mailto:adriant@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. --Adam On Tue, Oct 15, 2019, 22:04 Adrian Turjak <adriant@catalyst.net.nz <mailto:adriant@catalyst.net.nz>> wrote: 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: https://review.opendev.org/#/c/639010/ https://etherpad.openstack.org/p/community-goal-project-deletion https://etherpad.openstack.org/p/DEN-Deletion-of-resources https://etherpad.openstack.org/p/DEN-Train-PublicCloudWG-brainstorming 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. :) Cheers, Adrian 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
Also of potential interest is our own internal variant of project termination: https://gitlab.com/catalyst-cloud/python-opsclient/blob/master/opsclient/ops...
Note, a recent thing we ran into was a lack of support for Swift Bulk deletion... which we are now turning on and fixing, because deleting a project with 2mil + objects one by one is... slow.
On 31/10/19 2:26 am, Adam Harwell 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@catalyst.net.nz mailto:adriant@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. --Adam On Tue, Oct 15, 2019, 22:04 Adrian Turjak <adriant@catalyst.net.nz <mailto:adriant@catalyst.net.nz>> wrote: 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: https://review.opendev.org/#/c/639010/ https://etherpad.openstack.org/p/community-goal-project-deletion https://etherpad.openstack.org/p/DEN-Deletion-of-resources https://etherpad.openstack.org/p/DEN-Train-PublicCloudWG-brainstorming 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. :) Cheers, Adrian 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
Interesting... Well, hopefully I will see some people in about 30 minutes about this. :)
On Mon, Nov 4, 2019, 11:00 AM Adrian Turjak adriant@catalyst.net.nz wrote:
Also of potential interest is our own internal variant of project termination:
https://gitlab.com/catalyst-cloud/python-opsclient/blob/master/opsclient/ops...
Note, a recent thing we ran into was a lack of support for Swift Bulk deletion... which we are now turning on and fixing, because deleting a project with 2mil + objects one by one is... slow. On 31/10/19 2:26 am, Adam Harwell 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@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.
--AdamOn Tue, Oct 15, 2019, 22:04 Adrian Turjak adriant@catalyst.net.nz wrote:
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: https://review.opendev.org/#/c/639010/ https://etherpad.openstack.org/p/community-goal-project-deletion https://etherpad.openstack.org/p/DEN-Deletion-of-resources https://etherpad.openstack.org/p/DEN-Train-PublicCloudWG-brainstorming
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. :)
Cheers, Adrian
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
participants (5)
-
Adam Harwell
-
Adrian Turjak
-
Artem Goncharov
-
Jeremy Stanley
-
Tobias Rydberg