[cloudkitty][tc] Cloudkitty abandoned?

Pierre Riteau pierre at stackhpc.com
Fri Aug 7 09:18:48 UTC 2020

Thanks a lot for starting this discussion, I am also quite concerned about this.

At StackHPC we started looking into CloudKitty a year ago, when the
community was still fairly active. There was an IRC meeting every
month or so throughout 2019. Patches were getting merged.

Unfortunately in 2020 activity stopped abruptly. There hasn't been any
IRC meeting since early December and no patch has been merged since
the end of March. I have submitted straightforward stable backports of
bug fixes which have not received any answer.

I am well aware of the difficulty of keeping up with open-source
project maintenance when work deadlines are always taking priority. If
the existing core team would be willing to grant +2 votes to more
people, I would be happy to participate in the maintenance of the
project. We've now deployed CloudKitty for several of our customers
and have to maintain a stable fork anyway. We would rather maintain
upstream directly!

Pierre Riteau (priteau)

On Tue, 4 Aug 2020 at 23:22, Kendall Nelson <kennelson11 at gmail.com> wrote:
> I think the majority of 'maintenance' activities at the moment for Cloudkitty are the reviewing of open patches in gerrit [1] and triaging bugs that are reported in Launchpad[2] as they come in. When things come up on this mailing list that have the cloudkitty tag in the subject line (like this email), weighing in on them would also be helpful.
> If you need help getting setup with gerrit, I am happy to assist anyway I can :)
> -Kendall Nelson (diablo_rojo)
> [1] https://review.opendev.org/#/q/project:openstack/cloudkitty+OR+project:openstack/python-cloudkittyclient+OR+project:openstack/cloudkitty-dashboard
> [2] https://launchpad.net/cloudkitty
> On Tue, Aug 4, 2020 at 6:21 AM Rafael Weingärtner <rafaelweingartner at gmail.com> wrote:
>> I am not sure how the projects/communities here in OpenStack are maintained and conducted, but I could for sure help.
>> I am a committer and PMC for some Apache projects; therefore, I am a bit familiar with some processes in OpenSource communities.
>> On Tue, Aug 4, 2020 at 5:11 AM Mark Goddard <mark at stackhpc.com> wrote:
>>> On Thu, 30 Jul 2020 at 14:43, Rafael Weingärtner
>>> <rafaelweingartner at gmail.com> wrote:
>>> >
>>> > We are working on it. So far we have 3 open proposals there, but we do not have enough karma to move things along.
>>> > Besides these 3 open proposals, we do have more ongoing extensions that have not yet been proposed to the community.
>>> It's good to hear you want to help improve cloudkitty, however it
>>> sounds like what is required is help with maintaining the project. Is
>>> that something you could be involved with?
>>> Mark
>>> >
>>> > On Thu, Jul 30, 2020 at 10:22 AM Sean McGinnis <sean.mcginnis at gmx.com> wrote:
>>> >>
>>> >> Posting here to raise awareness, and start discussion about next steps.
>>> >>
>>> >> It appears there is no one working on Cloudkitty anymore. No patches
>>> >> have been merged for several months now, including simple bot proposed
>>> >> patches. It would appear no one is maintaining this project anymore.
>>> >>
>>> >> I know there is a need out there for this type of functionality, so
>>> >> maybe this will raise awareness and get some attention to it. But
>>> >> barring that, I am wondering if we should start the process to retire
>>> >> this project.
>>> >>
>>> >>  From a Victoria release perspective, it is milestone-2 week, so we
>>> >> should make a decision if any of the Cloudkitty deliverables should be
>>> >> included in this release or not. We can certainly force releases of
>>> >> whatever is the latest, but I think that is a bit risky since these
>>> >> repos have never merged the job template change for victoria and
>>> >> therefore are not even testing with Python 3.8. That is an official
>>> >> runtime for Victoria, so we run the risk of having issues with the code
>>> >> if someone runs under 3.8 but we have not tested to make sure there are
>>> >> no problems doing so.
>>> >>
>>> >> I am hoping this at least starts the discussion. I will not propose any
>>> >> release patches to remove anything until we have had a chance to discuss
>>> >> the situation.
>>> >>
>>> >> Sean
>>> >>
>>> >>
>>> >
>>> >
>>> > --
>>> > Rafael Weingärtner
>> --
>> Rafael Weingärtner

More information about the openstack-discuss mailing list