<div dir="auto"><div>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. <div dir="auto"><br></div><div dir="auto">Yeah, I understand completely about priorities and such internally. Same for me... It just happens that this IS priority work for us right now. :)</div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Oct 29, 2019, 07:48 Adrian Turjak <<a href="mailto:adriant@catalyst.net.nz">adriant@catalyst.net.nz</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p>My apologies I missed this email.<br>
<br>
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.<br>
<br>
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. :(<br>
</p>
<div>On 17/10/19 8:48 am, Adam Harwell
wrote:<br>
</div>
<blockquote type="cite">
<div dir="auto">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.
<div dir="auto"><br>
</div>
<div dir="auto">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.</div>
<div dir="auto"><br>
</div>
<div dir="auto"> --Adam</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Oct 15, 2019, 22:04
Adrian Turjak <<a href="mailto:adriant@catalyst.net.nz" target="_blank" rel="noreferrer">adriant@catalyst.net.nz</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I tried to
get a community goal to do project deletion per project, but<br>
we ended up deciding that a community goal wasn't ideal unless
we did<br>
build a bulk delete API in each service:<br>
<a href="https://review.opendev.org/#/c/639010/" rel="noreferrer noreferrer noreferrer" target="_blank">https://review.opendev.org/#/c/639010/</a><br>
<a href="https://etherpad.openstack.org/p/community-goal-project-deletion" rel="noreferrer noreferrer noreferrer" target="_blank">https://etherpad.openstack.org/p/community-goal-project-deletion</a><br>
<a href="https://etherpad.openstack.org/p/DEN-Deletion-of-resources" rel="noreferrer noreferrer noreferrer" target="_blank">https://etherpad.openstack.org/p/DEN-Deletion-of-resources</a><br>
<a href="https://etherpad.openstack.org/p/DEN-Train-PublicCloudWG-brainstorming" rel="noreferrer noreferrer noreferrer" target="_blank">https://etherpad.openstack.org/p/DEN-Train-PublicCloudWG-brainstorming</a><br>
<br>
What we decided on, but didn't get a chance to work on, was
building<br>
into the OpenstackSDK OS-purge like functionality, as well as
reporting<br>
functionality (of all project resources to be deleted). That
way we<br>
could have per project per resource deletion logic, and all of
that<br>
defined in the SDK.<br>
<br>
I was up for doing some of the work, but ended up swamped with
internal<br>
work and just didn't drive or push for the deletion work
upstream.<br>
<br>
If you want to do something useful, don't pursue OS-Purge,
help us add<br>
that official functionality to the SDK, and then we can push
for bulk<br>
deletion APIs in each project to make resource deletion more
pleasant.<br>
<br>
I'd be happy to help with the work, and Monty on the SDK team
will most<br>
likely be happy to as well. :)<br>
<br>
Cheers,<br>
Adrian<br>
<br>
On 1/10/19 11:48 am, Adam Harwell wrote:<br>
> I haven't seen much activity on this project in a while,
and it's been<br>
> moved to opendev/x since the opendev migration... Who is
the current<br>
> owner of this project? Is there anyone who actually is
maintaining it,<br>
> or would mind if others wanted to adopt the project to
move it forward?<br>
><br>
> Thanks,<br>
> --Adam Harwell<br>
</blockquote>
</div>
</blockquote>
</div>
</blockquote></div></div></div>