Skip to content
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.

[meta] define a set of fixes necessary for a Deis v1 LTS release #4776

Closed
mboersma opened this issue Dec 3, 2015 · 13 comments
Closed

[meta] define a set of fixes necessary for a Deis v1 LTS release #4776

mboersma opened this issue Dec 3, 2015 · 13 comments

Comments

@mboersma
Copy link
Member

mboersma commented Dec 3, 2015

The next minor release of Deis is intended to be a "long-term support" release that provides a stable, supported platform that will continue to receive fixes for many months.

Please help us ensure that Deis LTS will meet your needs by pointing out which changes are necessary for your use. Add a comment here referencing an existing GitHub issue or describing the problem, and we will roll them up into an "LTS" milestone and update the roadmap document so we can all track progress.

@mboersma mboersma changed the title Define a set of fixes necessary for a Deis v1 LTS release [meta] define a set of fixes necessary for a Deis v1 LTS release Dec 3, 2015
@iancoffey
Copy link
Contributor

I would ❤️ if #4554 could get manual testing and be included. I know its a bear but it feels like its either time to manually test it finally or just close it.

@rvadim
Copy link

rvadim commented Dec 8, 2015

Hello guys. Thank you for your work. Deis is actually great. We use it in production in 1 DC and planning up +2 production clusters in 2 other DC's in February 2016.
At this moment we have one P1(not P0) issue with locking app configuration in controller #4746 and we will be very happy if this issue will be fixed in LTS release. Also i can help with fixing, adding PR, writing tests etc.

@rvadim
Copy link

rvadim commented Dec 14, 2015

#4796

@carmstrong
Copy link
Contributor

Thank you @rvadim!!

@jannispl
Copy link
Contributor

#3969

@rcreasey
Copy link

#4494 would need to be fixed as well.

Running a coreos/deis install entirely behind a corporate proxy makes this a showstopper.

Actually, docker 1.9 supports build-args to be propagated to built images:
moby/moby#15182

This might be an easy way to globally set and propagate to all deis containers. That, and making sure that the docker-in-docker builder also passes it to the herokuish container.

@mboersma mboersma added this to the v1.13 milestone Dec 16, 2015
@lslaslo
Copy link

lslaslo commented Dec 17, 2015

#4787 might be beneficial.

@hakobera
Copy link

Thanks for deis guys, deis is really nice product.
#4746 is neccesary for production usage. Our deis cluster is often lock by multiple config update at same time.

@dpanelli
Copy link

A way to get around this moby/moby#14788

@dmcnaught
Copy link

#4763 : "tags:set isn't restricting my app to certain hosts"

@bacongobbler
Copy link
Member

@dmcnaught yes, that's been merged in master so it will go into the LTS release.

@aespinosa
Copy link

#4732 or getting docker to cleanup its iptables in some way or another.

This was referenced Jan 21, 2016
@nathansamson
Copy link
Contributor

can someone please look at #3479?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests