search

Teevity / ice

AWS Usage Tool
2.86k stars 435 forks source link

Status of ice - Is it dead? #240

Closed Esya closed 7 years ago

Esya commented 7 years ago

Hey all,

It seems that the netflix team has moved on and does not maintain it anymore. It currently sits with 28 pull requests and 80 open issues. Some pull requests seem to be adding great features, such as SAML Login, or even just some new AWS regions and instance types that are not included yet in ice.

It seems that there is no active fork either.

There is no other open-source project similar to Ice, only commercial solutions, that are quite expensive.

Would you consider giving rights to some active contributors to give a second life to this project? Or do you have another viable approach?

andrewmcgilvray commented 7 years ago

A guy from Teevity said they were going to update their fork a few month ago .. but it never happened. :-(

nfonrose commented 7 years ago

Hi Tristan and Andrew,

A guy from Teevity said they were going to update their fork a few month ago .. but it never happened. :-(

You are right. We've been very busy on other subjects ("RI optimization algorithms" and "Resource Optimization Level Scoring") and have not updated our fork with the latest AWS Regions.

Can I ask what would be the most important things you would like to get fixed first ? I'm speaking to Tristan and Andrew, but also to the larger Ice community. I'm pretty sure all of them are already fixed in our internal (non public) fork so it's not necessarily are lot of work for us to push them to our public fork (even though our internal fork and the public Ice fork are very different now).

We are clearly interested in ensuring that the Ice project doesn't die (even if we realize it's in a pretty bad shape right now) so your answer to my the question above will be seriously taken into account.

Nicolas

PS : I just want to clarify that we are not operating as an OSS company, meaning that we are not and will not publish all our source code as OSS. It's possible that we don't intend to publish as OSS some of the things you would like to see implemented in OSS Ice. But if that's the case :

-- Nicolas Fonrose | Teevity | Founder +33.6.61.35.43.31 https://teevity.com - Cloud Costs Analytics built on NetflixOSS twitter - @nfonrose / @teevity

On Sun, Mar 5, 2017 at 4:02 AM, Andrew McGilvray notifications@github.com wrote:

A guy from Teevity said they were going to update their fork a few month ago .. but it never happened. :-(

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Netflix/ice/issues/240#issuecomment-284201502, or mute the thread https://github.com/notifications/unsubscribe-auth/AACUpcF4QCI43bA-Z9Xq0B0tFXavgZORks5riiXXgaJpZM4MSjlH .

TomGudman commented 7 years ago

Hi Nicolas,

I think fixing the easy stuff first and creating some project activity would be welcome. Like:

amalakar commented 7 years ago

@nfonrose curious has there been any progress or thought around making: https://github.com/Teevity/ice/ active? (like merging current open PRs etc). It would be nice to see ice becoming active again.

JoshRosen commented 7 years ago

ICE is a very useful tool but the project currently suffers from lack of maintenance. Users must maintain their own forks in order to fix basic issues, such as lack of support for new regions, resulting in lots of duplicated effort and frustration.

I'd like to propose the creation of a new GitHub organization to host a community-maintained fork of ICE. In order to prevent the new fork from dying again I would like to include users from multiple companies/organizations as committers / owners (the project could be adopted by a single organization and folks from other companies could be added as external GitHub repo collaborators, but that creates security / IT headaches).

Concretely, I would like to:

One alternative would be to transfer the ownership of the ICE repo itself to the new organization (see https://help.github.com/articles/about-repository-transfers/), so existing forks would then point to our new organization's copy. This would make it easier to review the existing PRs and issues. I don't necessarily want to block on this, however, since getting someone from Netflix to sign off on it could be difficult.

Another alternative would be to get a larger OSS organization, such as Apache, to adopt the project, but that will be a much more complicated process.

If a few folks are willing to join me as initial maintainers and we can come up with a good organization name then I'd be happy to get the ball rolling on setting up the necessary project infrastructure.

(I also cross-posted this message to the iceusers Google Group at https://groups.google.com/forum/#!topic/iceusers/RzbcDCVPwU0)

cpwatson commented 7 years ago

Thanks for the comments @JoshRosen. My team here at Netflix owns ICE and in the past year developed a new solution (which we haven't open sourced) to better support our volume of data and analytic needs. I was in discussions with @nfonrose to perhaps have his fork at Teevity become the more "official" ICE-based project.

Let me discuss internally and see what the best next steps forward might be in terms of the options you proposed above.

zakcrawford commented 7 years ago

Excited to hear that ICE is not dead at netflix, or at least a successor is under active development!

shaneknapp commented 7 years ago

super stoked to hear this as well!

JoshRosen commented 7 years ago

Hi @cpwatson, just checking in to see if you have any updates to share.

It would be great to collaborate with Teevity, but I'm not sure that actually hosting the community fork at Teevity is the best way for this to happen. Instead, I would propose to create a new GitHub organization and invite @nfonrose (and other folks from Teevity) as organization owners / admins. Having the ownership be shared among multiple organizations helps to ensure that the fork won't die due to individual maintainers or organizations moving on from the project.

gyoza commented 7 years ago

Can we call it Teevflix Ice so it sounds like beer?

Additionally, I support this effort in every way possible. (The community fork of the things with the netflix)

ghaber commented 7 years ago

Hi all,

It seems Netflix has passes ownership of this repo to Teevity so I hope this mean the repo comes back to life again. I am ready to help.

Regards

nfonrose commented 7 years ago

It has actually come back to life already. We've pushed a few updates already (to make it compatible with all the latest regions), have setup an automated synchronizing of Ice releases with the Docker image built by jonbrouse.

The next step is to push a CloudFormation so that anybody can easily start Ice on their AWS accounts without having to fight with IAM rights and other issues.

And the next one is to include a basic test suite (focusing on the Processor logic, not the UI) so that people pushing PR can do so with the confidence that nothing has been broken inside the Ice core.

If you want to help, your more than welcome!

ghaber commented 7 years ago

Great news, I think it could be a good idea to create a to-do list so anybody can get a task to be done. A google group or similar with no spam would ne needed for communicating between us and get organized.

Regards

PabloCastellano commented 7 years ago

Since the project has been already transferred to Teevity, I think this issue is solved. ICE has had more commits in the last 3 months than in the last year.

csabaszilveszter commented 6 years ago

How about now? Can't see any updates recently, also there's some spam on the google group. :)

Hoping to be able to use this (or any alternative) in a production env. Suggestions?

Thx in advance.