|
1 | 1 | # Deis Roadmap |
2 | 2 |
|
3 | 3 | The Deis Roadmap is a community document created as part of the open [Planning Process][]. |
4 | | -Each roadmap item describes a high-level capability or grouping of features that are deemed |
5 | | -important to the future of Deis. |
| 4 | +Each roadmap item describes a high-level capability or grouping of features |
| 5 | +that are deemed important to the future of Deis. |
6 | 6 |
|
7 | | -Given the project's rapid [Release Schedule](release-schedule.md), roadmap items are designed to provide a sense of |
8 | | -direction over many releases. |
| 7 | +Given the project's rapid [Release Schedule](release-schedule.md), roadmap |
| 8 | +items are designed to provide a sense of direction over many releases. |
9 | 9 |
|
10 | 10 | ## Deis v2 |
11 | 11 |
|
| 12 | +A complete roadmap for post 2.0 will be provided once we are closer to release. |
| 13 | + |
12 | 14 | Much of the Deis team's efforts are focused on Deis v2, which will see the Deis |
13 | 15 | platform running on Kubernetes. |
14 | 16 |
|
15 | | -For details on Deis v2, see the [Deis v2 Design Document][] |
16 | | -and issues with the [v2][] tag. |
17 | | - |
18 | | -## Etcd Hardening |
19 | | - |
20 | | -We have recently seen various issues with etcd performance, which can cause |
21 | | -issues with Deis. We will focus on re-evaluating our implementation and use |
22 | | -of etcd in Deis, with a focus on performance and reliability. |
23 | | - |
24 | | -This feature is tracked as GitHub issue [#4404][]. |
25 | | - |
26 | | -## Permissions and Teams |
27 | | - |
28 | | -Deis deployments in larger organizations require more fine-grained control |
29 | | -over users and permissions. Implementation of teams and improved user permissions |
30 | | -are tracked in separate issues: |
31 | | - |
32 | | - - [ ] [Permissions][] |
33 | | - - [ ] [Teams][] |
34 | | - |
35 | | -## Monitoring & Telemetry |
36 | | - |
37 | | -Deis installations today use custom solutions for monitoring, alerting and operational visibility. |
38 | | -Deis will standardize the monitoring interfaces and provide open source agent(s) that can be used to ship telemetry to arbitrary endpoints. |
39 | | - |
40 | | - - [ ] Host Telemetry (cpu, memory, network, disk) |
41 | | - - [ ] Container Telemetry (cpu, memory, network, disk) |
42 | | - - [ ] Platform Telemetry (control plane, data plane) |
43 | | - - [ ] Controller Telemetry (app created, build created, containers scaled) |
44 | | - |
45 | | -This feature is tracked as GitHub issue [#3699][]. |
46 | | - |
47 | | -## Internal Service Discovery |
48 | | - |
49 | | -To provide a better container networking experience, Deis must provide |
50 | | -internal service discovery for components to coordinate. |
51 | | - |
52 | | -This feature is tracked as GitHub issue [#3072][]. |
53 | | - |
54 | | -## Update Service |
55 | | - |
56 | | -Deis must support 100% automated, zero-downtime updates of the control plane. |
57 | | -Deis clusters should be attached to an alpha, beta or stable channel and rely on an automatic update mechanism. |
58 | | -To accomplish this, Deis plans to use the `Google Omaha Protocol`_ as implemented by `CoreUpdate`_. |
59 | | - |
60 | | - - [x] [Update client/agent][] |
61 | | - - [ ] Update server |
62 | | - - [ ] CI Integration |
63 | | - |
64 | | -This feature is tracked as GitHub issue [#2106][]. |
65 | | - |
66 | | -## Deis Push |
67 | | - |
68 | | -End-users should be able to push Docker-based applications into Deis from their local machine using `deis push user/app`. |
69 | | -This works around a number of authentication issues with private registries and `deis pull`. |
70 | | - |
71 | | - - [ ] [Docker Registry v2][] |
72 | | - - [ ] [Deis Push][] |
73 | | - |
74 | | -## TTY Broker |
75 | | - |
76 | | -Today Deis cannot provide bi-directional streams needed for log tailing and interactive batch processes. |
77 | | -By having the Controller drive a TTY Broker component, Deis can securely open WebSockets |
78 | | -through the routing mesh. |
79 | | - |
80 | | - - [ ] [TTY Broker component][] |
81 | | - - [ ] [Interactive Deis Run][deis-run] (`deis run bash`) |
82 | | - - [ ] [Log Tailing][] (`deis logs -f`) |
83 | | - |
84 | | -## Service Broker |
85 | | - |
86 | | -In Deis, connections to [Backing Services][] are meant to be explicit and modeled as a series of environment variables. |
87 | | -Deis believes the Cloud Foundry [Service Broker API][] is the best embodiment of this today. |
88 | | - |
89 | | - - [ ] Deis Addons CLI (deis addons) |
90 | | - - [ ] PostgreSQL Service Broker |
91 | | - - [ ] Redis Service Broker |
| 17 | +For details on Deis v2, see the [Deis v2 Design Document][]. |
92 | 18 |
|
93 | | -This feature is tracked as GitHub issue [#231][]. |
| 19 | +* [Alpha Issues](https://github.com/deis/deis/issues/4743) |
| 20 | +* [Beta Issues](https://github.com/deis/deis/issues/4809) |
| 21 | +* [Release Candidate Issues]() |
94 | 22 |
|
95 | | -[#231]: https://github.com/deis/deis/issues/231 |
96 | | -[#2106]: https://github.com/deis/deis/issues/2106 |
97 | | -[#3072]: https://github.com/deis/deis/issues/3072 |
98 | | -[#3699]: https://github.com/deis/deis/issues/3699 |
99 | | -[#4222]: https://github.com/deis/deis/issues/4222 |
100 | | -[#4345]: https://github.com/deis/deis/issues/4345 |
101 | | -[#4404]: https://github.com/deis/deis/issues/4404 |
102 | | -[Automatic CoreOS upgrades]: https://github.com/deis/deis/issues/1043 |
103 | | -[backing services]: ../understanding-deis/concepts.md#backing-services |
104 | | -[CoreUpdate]: https://coreos.com/docs/coreupdate/custom-apps/coreupdate-protocol/ |
105 | | -[deis-run]: https://github.com/deis/deis/issues/117 |
106 | | -[deis push]: https://github.com/deis/deis/issues/2680 |
107 | 23 | [deis v2 design document]: https://github.com/deis/deis/issues/4582 |
108 | | -[docker registry v2]: https://github.com/deis/deis/issues/3814 |
109 | | -[Google Omaha Protocol]: https://code.google.com/p/omaha/wiki/ServerProtocol |
110 | | -[like CoreOS]: https://coreos.com/releases/ |
111 | | -[Log Tailing]: https://github.com/deis/deis/issues/465 |
112 | | -[Permissions]: https://github.com/deis/deis/issues/4150 |
113 | | -[planning process]: planning-process.md |
114 | | -[Rigger]: https://github.com/deis/rigger |
115 | | -[Service Broker API]: http://docs.cloudfoundry.org/services/api.html |
116 | | -[Teams]: https://github.com/deis/deis/issues/4173 |
117 | | -[TTY Broker component]: https://github.com/deis/deis/issues/3808 |
118 | | -[Update client/agent]: https://github.com/deis/deis/issues/3811 |
119 | 24 | [v2]: https://github.com/deis/deis/labels/v2 |
0 commit comments