| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Response ID | Time Started | Date Submitted | Status | An OpenStack User - Cloud Operator (operator or infrastructure architect):Before we get started - do you consider yourself (please check all that apply): | An OpenStack User - Cloud Consumer (application developer, account/project owner):Before we get started - do you consider yourself (please check all that apply): | An OpenStack Contributor:Before we get started - do you consider yourself (please check all that apply): | Other (please specify)::Before we get started - do you consider yourself (please check all that apply): | Rather not say:Before we get started - do you consider yourself (please check all that apply): | Other (please specify)::Before we get started - do you consider yourself (please check all that apply): | What about the vision excites you? What do you like? | What needs to be changed? | What is missing? | |||||||||||
2 | 16 | Apr 10, 2017 4:17:31 PM | Apr 10, 2017 4:22:43 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | An OpenStack Contributor | Projections of growth or improvement across multiple demographics and axes, with concrete targets by which to judge success. | We need more meaningful community feedback to make sure this vision accurately aligns with the desires of the TC constituency it's elected to represent. | The vision process seems like a bit of an event horizon, and we need some additional dialogue about what happens once it's officially nailed to the door. | ||||||||||||||
3 | 25 | Apr 13, 2017 9:55:22 AM | Apr 13, 2017 9:58:42 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | An OpenStack Contributor | I get, and like, the idea behind the vision. "Make clear that OpenStack is usable in lots of ways for lots of cool" | It's overly complex and confusing. Right off, it starts talking about constellations and I'm immediately in "wtf is a constellation?" mode Use standard terminology ("reference implementation") or similar, or add an introduction explaining what the constellation concept even is, before the rest of that vision | same comment as what to change | ||||||||||||||
4 | 29 | Apr 13, 2017 9:56:13 AM | Apr 13, 2017 9:59:12 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | Less complication on Networking configuration of Openstack | Simplification; currently highly technical and always need some extensive time to get things to work together | simplified for end users not engineers | ||||||||||||||||
5 | 32 | Apr 13, 2017 9:56:18 AM | Apr 13, 2017 9:56:33 AM | Complete | Rather not say | x | x | x | ||||||||||||||||
6 | 42 | Apr 13, 2017 9:56:37 AM | Apr 13, 2017 10:06:24 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | ? | Too many words and lacking structure. Should start with high-level view of "the vision". Is it outreach? diversity? what about technical vision? what's coming? | Lastly there's a lot of stuff in here about past but I expect to hear future looking things in a vision statement. | ||||||||||||||||
7 | 44 | Apr 13, 2017 9:57:24 AM | Apr 13, 2017 10:42:59 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack Contributor | Orion is a good idea for simplyfing the understanding of openstack. The differentiation of contributions is fundamental and should be encouraged. Since commercial distributions of openstack start spreading, there are operators that limits themself to use openstack instead of also adding what the need. | Nothing, i think is a good vision. | nothing | |||||||||||||||
8 | 48 | Apr 13, 2017 9:57:24 AM | Apr 13, 2017 10:02:20 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | An OpenStack Contributor | OpenStack projects (like Keystone) integrated with outside projects as a natural plugins | nothing :) | nothing :) | ||||||||||||||
9 | 50 | Apr 13, 2017 9:57:42 AM | Apr 13, 2017 10:23:41 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | I see the possibility in it. | we need more experienced contributor. | nothing | ||||||||||||||||
10 | 52 | Apr 13, 2017 9:57:54 AM | Apr 13, 2017 10:15:21 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | An OpenStack Contributor | The simplified structure | nothing | nothing | ||||||||||||||
11 | 53 | Apr 13, 2017 9:57:54 AM | Apr 13, 2017 10:00:49 AM | Complete | An OpenStack Contributor | The concept of constellations helps to give something concrete to talk about and act upon. So often when we're working on this stuff it's all a bit abstract and there are no clear and shared metaphors that we work with. Constellation feels like a good one. | The thing I like the most about this document (the constellation metaphor) is not about the behavior or make up of the TC. The first half of the doc is much more about openstack than the TC. I think OpenStack needs a coherent vision, and I think the TC is a critical factor in creating that vision, but for a document that is supposed to be describing a vision for the TC it feels like it is something else. | There could be more about any changes to the how and why the TC governs, and how it achieves and maintains legitimacy. | ||||||||||||||||
12 | 67 | Apr 13, 2017 9:59:16 AM | Apr 13, 2017 10:21:00 AM | Complete | An OpenStack Contributor | I like the idea of the mentoring program and the constellations. | I'm not sure how they intend to get more companies investing longer term employees in OpenStack | Integration with other Open Source projects was kind of vague, would like to hear more about how OpenStack is being integrated with container tech in real world solutions. | ||||||||||||||||
13 | 68 | Apr 13, 2017 9:59:27 AM | Apr 13, 2017 10:16:28 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | The constellations are awesome, but I haven't heard of any of those (1-3). | nothing | nothing at the moment. | ||||||||||||||||
14 | 82 | Apr 13, 2017 10:01:10 AM | Apr 18, 2017 3:16:22 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | I like the modularity of the OpenStack, and ability to use the projects independently of the OpenStack. | I think everything is going the right direction for now. | Interesting concept about the constellation approach. I tried to open the link you provided but the site is down or unavailable, also google search does not have any reference to openstack constellation or the given web site address (https://orion.openstack.org) | ||||||||||||||||
15 | 83 | Apr 13, 2017 10:00:55 AM | Apr 13, 2017 10:20:50 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | More companies getting involved in the development of OpenStack, instead of a few companies that had a commercial interest. | Easier intstallation and upgrades | openstack managed by K8S | ||||||||||||||||
16 | 87 | Apr 13, 2017 10:01:35 AM | Apr 13, 2017 10:03:24 AM | Complete | Other (please specify): | Tests in lab - for master degree | Innovation, the possibility to virtualize things like IPTV and OTT, besides network | Tacker simply doesnt work if we follow the procedure in the os site. | Nothing. | |||||||||||||||
17 | 96 | Apr 13, 2017 10:02:57 AM | Apr 13, 2017 10:04:30 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | An OpenStack Contributor | ss | s | s | ||||||||||||||
18 | 100 | Apr 13, 2017 10:03:44 AM | Apr 13, 2017 10:05:04 AM | Complete | An OpenStack User - Cloud Consumer (application developer, account/project owner) | the use and growth of the ecosystem | more input validations and operational efficiencies without sacrificing security concerns. the still see to be too much ad odds. | security injected into the early phases | ||||||||||||||||
19 | 107 | Apr 13, 2017 10:05:24 AM | Apr 13, 2017 10:15:41 AM | Complete | An OpenStack Contributor | I like the increased diversity among the leadership and contributors. I also like the idea of a mentoring program to help the leaders of tomorrow. | No large changes needed. | More concrete goals for diversity would be better. | ||||||||||||||||
20 | 111 | Apr 13, 2017 10:07:05 AM | Apr 13, 2017 10:27:58 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | OpenStack is maturing | CLI autocompletion (tab) in openstack-cli would improve the end user experience. | CLI autocompletion for openstack-cli!!!!!!!!!!! | ||||||||||||||||
21 | 126 | Apr 13, 2017 10:10:13 AM | Apr 13, 2017 10:10:41 AM | Complete | Rather not say | too verbose | simplify | cohesion | ||||||||||||||||
22 | 133 | Apr 13, 2017 10:12:16 AM | Apr 13, 2017 10:16:24 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | An OpenStack Contributor | - Clear vision and community contribution - Carrier grade implication | - OpenStack release update and feature avaialbility | - Feature roadmap evolution and follow up par node or controller - openstack Labs | ||||||||||||||
23 | 155 | Apr 13, 2017 10:16:52 AM | Apr 13, 2017 10:21:12 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack Contributor | Nothing | This is just attempting to deal with the chaos that is OpenStack today. Nothing to reign in the chaos and in my belief this chaos will kill OpenStack before 2019. | The TC needs to be a technical oversight committee and control the asylum not stand by and watch the convicts (aka programmers) take over. | |||||||||||||||
24 | 156 | Apr 13, 2017 10:17:02 AM | Apr 13, 2017 10:23:42 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | An OpenStack Contributor | I like the possibility of actually building something that *normal* people can easily and quickly deploy. | Making statements like "pro-actively reaching out to other communities" is great and all, but the problem this is the same TC that likes to use the phrase "one of us", and frankly I think the NIH cancer that plagues OpenStack needs to be called out directly and explicitly. | How do you simplify the architecture? How do we decrease the bloat? How do we get adapt and adopt new technologies and ways of doing things when we have an "old guard" running projects like Nova and frankly sitting on pretty much all of the seats of the TC. I see nothing in this Vision to describe what the TC's actual role in all of this is, how they're going to make any of this happen and most importantly how the TC and it's view of the world is going to change to actually improve things. It sounds great to throw out percentages of contributors etc but what did we do to get there (talking to other communities isn't going to cut it). The TC and the Nova Czars will continue building overly complex, bloated solutions to cater to special interests and OpenStack will continue to be that thing that customers tell me they want nothing to do with because it's WAY too complicated and difficult to deploy let alone maintain. | ||||||||||||||
25 | 166 | Apr 13, 2017 10:19:52 AM | Apr 13, 2017 10:30:16 AM | Complete | An OpenStack User - Cloud Consumer (application developer, account/project owner) | An OpenStack Contributor | It's a mission, not a vision. Vision, according my experience with other FLOSS communities, are much concise. This is a real plan, with numbers (probably even more than a mission). | I think that, as vision, it should be much shorter. | As pointed out, there is already too much at this point for a vision | |||||||||||||||
26 | 167 | Apr 13, 2017 10:19:08 AM | Apr 13, 2017 10:45:20 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | i)User/Contributor oriented view ii)Opening to integration with project developed in other languages | - | - | |||||||||||||||
27 | 175 | Apr 13, 2017 10:20:40 AM | Apr 13, 2017 10:47:35 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | The greater inclusion of input from the operators excites me. What I like is the growth potential in the community. | I don't feel qualified or tuned in enough to know what needs changing. | Again, not sure, but would be nice if the orion.openstack.org site was operational today (13-Apr). | ||||||||||||||||
28 | 178 | Apr 13, 2017 10:21:14 AM | Apr 13, 2017 10:26:25 AM | Complete | An OpenStack Contributor | Other (please specify): | OpenStack pre-sales | The globalisation of the TC, the diversity and inclusive targets | N/A | N/A | ||||||||||||||
29 | 184 | Apr 13, 2017 10:22:20 AM | Apr 13, 2017 10:25:04 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | Non OC usecases | Nothing. LGTM. | LGTM. No changes. | ||||||||||||||||
30 | 185 | Apr 13, 2017 10:22:52 AM | Apr 13, 2017 10:48:23 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | The vision that excites me is "Openstack will concur the computing world with software". I would like to see Openstack grown into the world standard with contributions from around the world as much as we can. | As TC said, we need to get every region to contribute to Openstack both inside openstack and outside openstack communities. | don't know yet. | ||||||||||||||||
31 | 189 | Apr 13, 2017 10:23:29 AM | Apr 13, 2017 10:25:14 AM | Complete | An OpenStack Contributor | More than a vision it seems just a report. Good achievement, but can't get what is exactly the vision. | Clearly express the vision for 2019 | the vision | ||||||||||||||||
32 | 192 | Apr 13, 2017 10:24:16 AM | Apr 13, 2017 10:25:59 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack Contributor | I need put more focus on try to put more security cloud vision | Service of database | Stability over infrastructure | |||||||||||||||
33 | 205 | Apr 13, 2017 10:28:33 AM | Apr 13, 2017 10:29:33 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | one stop shop | easy upgrades | learning. | ||||||||||||||||
34 | 213 | Apr 13, 2017 10:31:10 AM | Apr 13, 2017 10:35:55 AM | Complete | An OpenStack Contributor | nothing - orion.openstack.org doesn't resolve :-/ | everything - see above | everything | ||||||||||||||||
35 | 224 | Apr 13, 2017 10:35:45 AM | Apr 13, 2017 10:37:34 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | Openstack new constellations build | Better documentation. | Déploy tools | |||||||||||||||
36 | 226 | Apr 13, 2017 10:36:09 AM | Apr 13, 2017 10:47:25 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | - focus on open source as a whole and thinking beyond what is OpenStack only - focus on 'constellation' like concepts making on boarding manageable for new and feature specific user/groups | no comments here | - an effort to improve performance and stability of existing components. Adding new features is great, but scaling/maturing core features is essential for maturity and acceptance as a truly production ready platform | |||||||||||||||
37 | 236 | Apr 13, 2017 10:39:59 AM | Apr 13, 2017 10:51:18 AM | Complete | An OpenStack Contributor | I think the OpenStack Ladder program is a very, very interesting idea. I'd like to see a more concrete proposal for how this would work, but I'm glad that the TC is addressing the challenges that new contributors face. I also appreciate the call-outs to diversity both on the TC itself and in the contributor base. | I think the Constellation sections have a bit too much emphasis on what a Constellation is, what the views look like, etc. as opposed to defining the actual problem they're trying to solve. Presumably it's something related to project discoverability and making OpenStack in its many, many combinations easier to consume, but I think its focus and problem domain it's trying to solve for should be scoped more clearly. | Something about how to encourage companies and organizations to invest development time into upstream OpenStack would be useful. Lately, at least in the project(s) I'm active in, it seems as though there has been a decline in contribution, more core developers leaving, and companies pulling developers off of OpenStack. This is very worrisome to me. It'd also be good to encourage the consumption of OpenStack by smaller organizations, startups, etc. For whatever reason, anecdotally, OpenStack has less of a good reputation outside traditional enterprise circles, it seems. Anything I read about OpenStack on Hacker News is mostly doom and gloom or complaints about complexity and reliability issues. | ||||||||||||||||
38 | 253 | Apr 13, 2017 10:48:11 AM | Apr 13, 2017 10:50:16 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | An OpenStack Contributor | |||||||||||||||||
39 | 254 | Apr 13, 2017 10:48:45 AM | Apr 13, 2017 10:54:20 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | sometimes you're talking to questions like put a man on the moon, but you forget simple humans problems!!! | 1) All projects should implement the same feature 2) path to upgrade should be easier!!!! | A Long Term Support release | ||||||||||||||||
40 | 271 | Apr 13, 2017 10:58:33 AM | Apr 13, 2017 10:59:59 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | Absolutely nothing. It's laughable, at best. | Vision does not equal fiction. Document should tossed in its entirety and drafted anew; however, this time with less whimsical cloud fanfic and more centered in the realities and difficulties facing OpenStack. | It's missing a concrete and clear vision. It's missing honesty in the current state of the market and OpenStack. | |||||||||||||||
41 | 291 | Apr 13, 2017 11:11:24 AM | Apr 13, 2017 11:13:08 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | Constellation format | More concise guides with tabled scenarios | Documentation | |||||||||||||||
42 | 297 | Apr 13, 2017 11:14:30 AM | Apr 13, 2017 1:37:49 PM | Complete | An OpenStack Contributor | the idea of having several deeply worked reference architectures for combining different selection of openstack components to server different usecase that are developed but the openstack community instead of by external vendors or communities such as opnfv. | i think there should be a grater emphasis put on encouraging companies to thick upstream first on contributing to community priorities. | definition of terms such as Constellation so that people can get full context of the vision form this document | ||||||||||||||||
43 | 302 | Apr 13, 2017 11:18:05 AM | Apr 13, 2017 11:22:50 AM | Complete | An OpenStack User - Cloud Consumer (application developer, account/project owner) | An OpenStack Contributor | Other (please specify): | Technical Writer and Technical Reviewer | We need openstack to contain Software Development Frameworks from Official Companies Only, Containers, Images, and Stacks Ex. LAMP, Zend, Laravel, JBOSS, Ruby On Rails, etc. and please to make it only by official trusted companies and service providers. To be ready to Launch as Instances from Command Line and | Neutron and Ceilometer needs to be somehow more easy to add to Horizon | Just the Software Development Stacks, this what I think. | |||||||||||||
44 | 303 | Apr 13, 2017 11:18:35 AM | Apr 14, 2017 4:22:16 AM | Complete | An OpenStack Contributor | Openness for innovations: other programming languages (Go), COE (Kubernetes) | Back-pressure to accepting innovations | Vision of vendors leaving OpenStack development becoming a commodity software, like Linux OS. | ||||||||||||||||
45 | 306 | Apr 13, 2017 11:20:47 AM | Apr 13, 2017 11:28:53 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | Partner related complementary Projects Eco System | Speed and Agility 2 years is a lifetime | How do keep interest? finding some integration are easier to do directly and more comprehensive based upon how we use the target integration point i.e VMware how do you keep it from becoming too large keeping everything more like independent microservices and ability to pivot | |||||||||||||||
46 | 308 | Apr 13, 2017 11:22:16 AM | Apr 13, 2017 11:23:02 AM | Complete | An OpenStack Contributor | Looks interesting | Nothing | Nothing | ||||||||||||||||
47 | 314 | Apr 13, 2017 11:28:41 AM | Apr 13, 2017 11:29:10 AM | Complete | An OpenStack User - Cloud Consumer (application developer, account/project owner) | rdvgfedvgfedvgfedvgfedvgfedvgfedvgfedvgfedvgfexcwvcwd dfbvgbvgbvgbvgbvgbvgw | dfbvgvvvvvvvvvw fdwbbbbbb | fsbw< d fdbgrwq ttttttttttttttt | ||||||||||||||||
48 | 326 | Apr 13, 2017 11:39:19 AM | Apr 13, 2017 11:50:24 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack Contributor | The idea to make OpenStack easier to install and understand with Constellations. Having these use cases handy would be a huge help to bootstrap anyone and lower the entry barrier. | I think we probably need a cross project group dedicated to that. | Documentation and scripts to deliver these reference architectures of sorts. | |||||||||||||||
49 | 343 | Apr 13, 2017 11:55:25 AM | Apr 13, 2017 12:06:58 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | The focus on in-the-field challenges is very exciting. | Not much, I think things look good. | Need to continue to expand the Constellation approach. | ||||||||||||||||
50 | 350 | Apr 13, 2017 12:10:08 PM | Apr 13, 2017 12:18:10 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | Great information | You should have short bullet points of where the TC wants to be in 2019, and several short points on how to get there(At the top followed by the rest of the above information explaining in detail). Sometimes getting to the point immediately delivers a better message. The information is good. | Mentioned above | |||||||||||||||
51 | 351 | Apr 13, 2017 12:10:29 PM | Apr 13, 2017 12:27:27 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | The good thing is the contribution and teamwork and voting system for each line of code, | nothing | nothing | ||||||||||||||||
52 | 354 | Apr 13, 2017 12:15:07 PM | Apr 13, 2017 12:16:35 PM | Complete | An OpenStack Contributor | Making more users as open stack developers | Everything is perfect | Nothing | ||||||||||||||||
53 | 358 | Apr 13, 2017 12:22:40 PM | Apr 13, 2017 12:30:48 PM | Complete | An OpenStack Contributor | How is this a vision statement in any way? This just a recap of previous / current events. | I think I cover my feelings well enough in answer 2 and 4 but thanks for making these all required so I have to type something in here. | This doesn't touch on any of the real issues with openstack. The lack of a solid container integration point and the fact that consistently at every summit one of the main complains is usability / debuggability of openstack and it doesn't feel like that is getting any better. | ||||||||||||||||
54 | 365 | Apr 13, 2017 12:38:02 PM | Apr 13, 2017 12:42:37 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | All, because I use Openstack to cover all aspects of services / applications | Documentation structure. Multi-point of views is better. Global vision of constellation, Detailed vision for each distro / product, Aspect or Usage vision, networking, disk, computing, automation, ... Now the documentation structure is the same from the beginning, but now Openstack is more complex than before. | Nothing and All. Need some other details to check what missing in the constellation | |||||||||||||||
55 | 366 | Apr 13, 2017 12:39:45 PM | Apr 13, 2017 12:45:04 PM | Complete | An OpenStack User - Cloud Consumer (application developer, account/project owner) | The mechanism to distribute information include reference architectures will go a long way in bringing increased adoption. | Silos to be eliminated and more synergy should be built in among the developers of different components | cant think of any. | ||||||||||||||||
56 | 368 | Apr 13, 2017 12:42:32 PM | Apr 13, 2017 12:53:22 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | Flexibility to use it as an open source product and getting more and more features day by day unlike other proprietary product like vmware, digitalocean etc.. | More features and integration related to automation and billing modules. | - Slow bug fixes - Documentation need little more modification - More integration documentation for devops | ||||||||||||||||
57 | 374 | Apr 13, 2017 12:51:02 PM | Apr 13, 2017 12:52:40 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | An OpenStack Contributor | I like this new tech. new version. | I need to change its Nova. | Cluster. | ||||||||||||||
58 | 376 | Apr 13, 2017 12:53:59 PM | Apr 13, 2017 1:03:36 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack Contributor | Making projects independent from each other to allow reuse for other use cases. | create liaison with some other important projects (Mesos, Hadoop, ...) to share more technology. | $ wget -S http://orion.openstack.org/ --2017-04-13 18:59:44-- http://orion.openstack.org/ HTTP/1.1 404 Not Found Cache-Control: no-cache Pragma: no-cache Content-Type: text/html; charset=utf-8 Proxy-Connection: close Connection: close Content-Length: 629 2017-04-13 18:59:45 erreur 404 : Not Found. | |||||||||||||||
59 | 388 | Apr 13, 2017 1:12:17 PM | Apr 13, 2017 1:18:09 PM | Complete | An OpenStack User - Cloud Consumer (application developer, account/project owner) | The new architecture of OpenStack. | There's some gap in OpenStack learning for new adopters. | Video tutorials from OpenStack project teams or leads. | ||||||||||||||||
60 | 392 | Apr 13, 2017 1:16:37 PM | Apr 13, 2017 1:25:57 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack Contributor | Constellation part. Pre-built patterns, repeatable usages available for other community members, knowledge repository for contribution. | How individual components can be made compatible or ported with other languages | As far as I have used or level of contribution I did for OpenStack am feeling it's perfect as of today. | |||||||||||||||
61 | 397 | Apr 13, 2017 1:18:40 PM | Apr 13, 2017 4:39:11 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | Inclusion of customer as contributer | Not sure, can't say | User guides for the GUI | |||||||||||||||
62 | 405 | Apr 13, 2017 1:28:43 PM | Apr 13, 2017 1:44:40 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | The constellation idea seems interesting. But orion.openstack.org doesn't resolve, so I can't investigate further. I guess i'll need to try again later. | make orion.openstack.org resolve.. | orion.openstack.org doesn't resolve. | ||||||||||||||||
63 | 409 | Apr 13, 2017 1:41:20 PM | Apr 13, 2017 1:42:15 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | n | n | n | ||||||||||||||||
64 | 413 | Apr 13, 2017 1:48:12 PM | Apr 13, 2017 2:01:38 PM | Complete | Other (please specify): | Consultant | I think the whole idea is a great step in the right direction! | Nothing | Nothing | |||||||||||||||
65 | 414 | Apr 13, 2017 1:54:27 PM | Apr 13, 2017 2:04:37 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | An OpenStack Contributor | It covers a variety of topics, and is very positive. It looks beyond OpenStack itself and sees benefit outside the self-service. I love that operators are getting called out specifically. | I can't think of anything specifically that needs to be changed. | ... nothing? | ||||||||||||||
66 | 418 | Apr 13, 2017 2:11:15 PM | Apr 13, 2017 4:36:58 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | "As we have been going through and building these constellations we found several components that did not fit well. We removed components that either overlapped with work in adjacent communities or were not consistent with the OpenStack mission. Other projects were refactored to clarify their scope as they were placed on the map." "This has helped grow different patterns and culture of contributions, that are more focused on near term needs of the operators in the field" "It has also brought much more sympathy to the needs of part time contributors who can't complete a perfect patch to get it accepted. A small organic team of shepherds have been taking the drive-by contributions and working them into the system, either by taking over the patches or by applying follow-up changes." | IMHO, TC should put/enforce strong focus on APIs; an API ought to be taken at with a structured architecture/design, not "oh, and this, and that" as the code develops. IMHO, an API spec ought to be detached from the code behind it. IE, nova. Was it a structured API with fully automated tests for compliance (and eventually error handling), one could take a leap at refctoring the code currently providing it. Or, even start another project (named neo, perhaps?) providing nova API, doing things right[tm] in the backend, with proper cluster state maintained, without all dem "SELECT 1;" etc, eventually becoming the superior successor for pita, erm, nova. | I keep repeating the "benevolent dictator" thingie. I hope this Constellations-thingie goes much into that direction of more overall-architecture-thinking-before-coding.. | |||||||||||||||
67 | 421 | Apr 13, 2017 2:16:30 PM | Apr 13, 2017 2:17:19 PM | Complete | An OpenStack User - Cloud Consumer (application developer, account/project owner) | future of openstack | faster progress | more co-operation and sharing amongst members | ||||||||||||||||
68 | 422 | Apr 13, 2017 2:18:25 PM | Apr 13, 2017 2:29:43 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | An OpenStack Contributor | The focus on inter-group collaboration and clear lines of responsibility and how to interact between the projects is positive, as is the recognition that user's and consumers of OpenStack need to be considered in the continued project development. | First off, the link in the "vision" doesn't even resolve - https://orion.openstack.org isn't active or responding as I'm filling out this survey. So maybe there's something there that doesn't appear here, but the vision of what feature extensions, collaborations, and growth are considered important by those contributing to OpenStack today are anemic to outright missing here. Most of this vision is looking back, not forward - and as a vision it should set out goals to achieve such that a PTL or contributing wanting to help move in that direction could have a clear roadmap to guide them in terms of development direction and priorities. | The reality is that investment to developers working on OpenStack is falling off heavily - which could seem like a bad thing, but is really an opportunity. A focus on clear interactions between the components, quality and stability on those components, and clear lines of responsibility and integration to enable features and use cases is critical for the future of the project. As is probably apparent from my writing, I think OpenStack suffers greatly from lack of focus, trying to be "everything to everyone" and failing at all it with incredible mediocrity. That said, the core of IaaS is incredibly valuable and is the underpinning for VM/Image based consumption as pools of resources, rather than as single or sets of machines. | ||||||||||||||
69 | 423 | Apr 13, 2017 2:18:35 PM | Apr 13, 2017 2:27:13 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack Contributor | Refine the scope of overlapping OpenStack projects down to one role. About damn time! | Constellation principle seems a good idea but i can it easily seem 'simple' but still complex for new users of OpenStack. We need to ensure it is meant for a total newbie. Representation of APAC, Europe & women. I get this political move but please get the right person for the job and not limit yourself to "We need a woman even though this guy is more qualified for that position". | Involvement with ONAP initiative which is where OpenStack will see growth in 2019. | |||||||||||||||
70 | 431 | Apr 13, 2017 2:43:01 PM | Apr 13, 2017 2:57:48 PM | Complete | Other (please specify): | Cloud Architect | The fact a vision is being discussed and evnagelized | Adding a vision. | This vision as stated is not a vision at all but a self-congratulatory statement for our accomplishments to date. While our accomplishments are indeed worthy of a pat on the back and I appreciate the effort here, I do not see a single forward-thinking goal or vision for the future communicated which is indicative the TC does not truly understand what a vision is or how to communicate it. Therefore it is incredibly disheartening to learn that a "yay us" statement is being put forth as a vision. The lack thereof will be come evident to the extent any lack of collective/governing vision will produce. Please contact me at xxxxxxxx@xxxxx.com for further comment/discussion. If no comment is requested, I'll presume no improvement is desired. All the best. --xxxx | |||||||||||||||
71 | 442 | Apr 13, 2017 3:11:24 PM | Apr 13, 2017 3:15:16 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | It's good that Openstack is growing. However, from the statement above, it's difficult to see what the actual vision is. | Make the vision clearer and possibly shorter. | More focus on Ops. | ||||||||||||||||
72 | 445 | Apr 13, 2017 3:18:34 PM | Apr 13, 2017 3:29:24 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | not sure: it is too long, only read first sentence of each paragraph. | It appears it is all in past tense. Isn't vision supposed to be the future? | I do not see / understand the actual vision. I'd like to see something like: * We want to do X *: < explanation and details> * We want to do less of Y *: < explanation and details> and so on Instead almost every paragraph appears to be: We did this. We did that. It is good. Sorry if I misunderstand the goal of this excercise. | |||||||||||||||
73 | 467 | Apr 13, 2017 5:05:44 PM | Apr 13, 2017 5:06:27 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack Contributor | All of it. Making Openstack a great tool. | More granularity. | Databases | |||||||||||||||
74 | 472 | Apr 13, 2017 6:05:27 PM | Apr 13, 2017 6:28:32 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | An OpenStack Contributor | - communication and interaction among communities. - OpenStack Constellations and how they are interact. | I can see a clear vision and there is nothing to be changed for now. | involve more community members in adding to the contributions | ||||||||||||||
75 | 473 | Apr 13, 2017 6:06:58 PM | Apr 13, 2017 6:07:56 PM | Complete | Rather not say | Good | No | Best | ||||||||||||||||
76 | 477 | Apr 13, 2017 6:50:16 PM | Apr 13, 2017 6:58:54 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | Containerized OpenStack and non x86 architecture Nova Compute Cloud. | Increase contributer. | CMDB, audit log store and upgrade method(include skip upgrade(ex. L to N)) | ||||||||||||||||
77 | 479 | Apr 13, 2017 6:53:02 PM | Apr 13, 2017 7:18:32 PM | Complete | Other (please specify): | At this time I would consider myself a trainer | I think its important not to have tunnel vision, the focus on other open source projects is great as this may bring in better components. Making sure the existing projects can stand alone also helps to keep the community broad and may expose new use cases that could be useful in openstack. | Nothing I can think of, keep doing what you're doing | Again, nothing I can think of | |||||||||||||||
78 | 483 | Apr 13, 2017 7:14:14 PM | Apr 13, 2017 7:21:32 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | Cloud burst, hybrid clouds, easy installation, one front end to manage multiple projects | Installation is too hard and needs to be easier. Also it is hard to manage and understand the underlying technology | Integration with cloud providers. Find a way to easy tune openstack to different architectura and use cases (HPC, container orchestration, etc). Also, it is hard to improve performance | ||||||||||||||||
79 | 490 | Apr 13, 2017 8:08:46 PM | Apr 13, 2017 8:14:29 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | Interoperability and openness of OpenStack. | Support in the production tends to be longer and slower to change compared to the rate of releases of OpenStack. I think we need to make compatibility among new releases better and upgrades seamless. | I think OpenStack needs some help to make installation, upgrades more seamless. Some vendors are providing that but the fear of lock-in is real. | |||||||||||||||
80 | 493 | Apr 13, 2017 8:22:31 PM | Apr 13, 2017 8:35:21 PM | Complete | An OpenStack Contributor | - Incentive for projects to become independent - Cooperation with several other communities (being open and sharing resources with them as well) | I think the last paragraph is too unrealistic according to what is happening now. I see several vendors stepping away from OpenStack, while a few vendors are increasing their dominance in projects. The idea is great, but there is no solid plan to get there. That pictured future requires a lot of resources to work on them. I think the foundation could start hiring more people to work on driving that pictured idea. The other problem is that, with vendors backing away, it is less money for the foundation, and OpenStack development deaccelerates. I think the 2 points I highlighted above (what I like), willl be the main driving force for OpenStack, that will allow it to expand horizontally, pulling many more communities to collaborate into it and being part of the ecossystem, so I think it is a good idea to invest a lot in those 2 items. | I included in item #3. | ||||||||||||||||
81 | 498 | Apr 13, 2017 8:42:19 PM | Apr 13, 2017 8:53:19 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | Other (please specify): | Instructor | Great | No | No | |||||||||||||
82 | 500 | Apr 13, 2017 8:50:29 PM | Apr 13, 2017 8:53:42 PM | Complete | An OpenStack Contributor | I want to know what other done well, and i can learn from them. | More frequently | none | ||||||||||||||||
83 | 502 | Apr 13, 2017 8:58:28 PM | Apr 13, 2017 9:11:13 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | I don't understand what "Constellation for OpenStack" is all about and the link is missing. However, expanding the community or onborading new developers for sustainable growth is crucial for established open source project like OpenStack. | Clear goal of the vision. It seems a little vague on what the TC is trying to accomplish. | More reader friendly documentation. Use bullets, sections. | ||||||||||||||||
84 | 516 | Apr 13, 2017 9:43:27 PM | Apr 13, 2017 9:50:28 PM | Complete | An OpenStack Contributor | Studying and sharing | Till now nothing. | Thanks, keep on-going... | ||||||||||||||||
85 | 528 | Apr 13, 2017 10:52:29 PM | Apr 13, 2017 11:01:58 PM | Complete | Other (please specify): | Quality engineering | The vision is perfect. Implementation patterns and operator plus user views with keystone consideration for multi-tenancy | Add thoughts on scability and really tested large configuration topologies as example. This should focus on some enterprise implementation. | Operations with scale and support patterns Operational data collection with debugging architectures | |||||||||||||||
86 | 537 | Apr 13, 2017 11:44:19 PM | Apr 13, 2017 11:52:23 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | 4th Constellation for OpenStack, available at https://orion.openstack.org | why is this web site down?! https://orion.openstack.org | none | ||||||||||||||||
87 | 538 | Apr 13, 2017 11:53:20 PM | Apr 13, 2017 11:55:39 PM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | All of it | Nothing | Nothing | ||||||||||||||||
88 | 542 | Apr 14, 2017 12:16:46 AM | Apr 14, 2017 12:36:12 AM | Complete | Rather not say | Allowing or giving time for new comers to contribute. Ladder program. | Full or Part time Contributors have to take some sessions regarding their work. What new things have to done in projects. Scope and life cycle have to explained clearly. | Guidance for new comers is recommended. OpenStack is growing rapidly but more proprietary people are playing in the upper hands. One day they may jump over from here. So i don't want that to be happen. | ||||||||||||||||
89 | 544 | Apr 14, 2017 12:31:31 AM | Apr 14, 2017 12:35:45 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | Constellations Security planning Technical Mentoring | way people gets engaged in evolving development of Openstack from Various communities | Benefits and Values adds of new vision | ||||||||||||||||
90 | 549 | Apr 14, 2017 1:14:13 AM | Apr 14, 2017 1:25:15 AM | Complete | An OpenStack Contributor | Most Powerful stability | All Most Done | All Most Done | ||||||||||||||||
91 | 550 | Apr 14, 2017 1:18:41 AM | Apr 14, 2017 1:38:50 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | An OpenStack Contributor | Yes, It is exciting | At present guidelines for various roles installation is there however they seems lacking in contents, these need to revised to fill the gaps and also come up with the fully automated deployment solutions to reduce time to market cycle time. | Include Marketplace information as well. | ||||||||||||||
92 | 551 | Apr 14, 2017 1:24:38 AM | Apr 14, 2017 1:30:50 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack Contributor | vision show the right path of growing tech.that shows openstack become the part of all organizations in different ways. | the changes is required in coming days the licences is open or closed | how contributer meen different organization provide tools that developed related to openstack opensource for community | |||||||||||||||
93 | 553 | Apr 14, 2017 1:43:35 AM | Apr 14, 2017 2:30:26 AM | Complete | An OpenStack Contributor | The vision mentioned not only the OpenStack future but also the other open source projects. I think relationships with the other open source projects is really great. I think the OpenStack community is really big and active. However, I feel it's too focusing on OpenStack. We have really a good ecosystem which is awesome, but I feel like outcast from the other open source projects. | Clear a projects deprecation process. | The goal of diversity? The concrete number of the target ratio, or something like that. | ||||||||||||||||
94 | 557 | Apr 14, 2017 2:13:08 AM | Apr 14, 2017 2:17:06 AM | Complete | An OpenStack User - Cloud Consumer (application developer, account/project owner) | An OpenStack Contributor | Openstack coverage and integration with other products | 1. make study material easy and simple 2. bring more capabilities in horizon dashboard | development focus considering mid range customer | |||||||||||||||
95 | 558 | Apr 14, 2017 2:26:05 AM | Apr 14, 2017 2:42:54 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | I'm probably most excited about the prospects for Keystone being leveraged for projects outside of OpenStack. I'd love to learn more about these minimal component use cases for other projects. | I think a greater emphasis on the user and operator communities is a great start and would like to see this be a greater focus. Operators have a strong responsibility to the users, and finding new ways to engage them through that axis seems key to the evolution of OpenStack. Not sure if that's a change or more of a statement of focus... | It may sound crazy, but borrowing from the lessons learned from the jagged history of support for Hyper-V in Nova, I think the OpenStack interop story with Microsoft Azure should be something to foster. I think OpenStack and Microsoft's AzureStack are going to be the prevailing cloud platforms within the Enterprise, so this should be a consideration. | ||||||||||||||||
96 | 566 | Apr 14, 2017 3:12:41 AM | Apr 14, 2017 3:18:26 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack Contributor | I like the vision of the opstack community, follow the opensource scenario and be an active contributor. Many companies had understood that the way isn't to close their code, their work, but cooperate to achieve some common goals. | Openstack is built on several projects: what needs to be changed is the implementation of some projects; they need, in my opinion, to go to the same path in terms of feature. Today there are yet some pieces that have something divergent in their view. | Again, more standards, more common ways to operate, I mean, more common interfaces among the community people. | |||||||||||||||
97 | 577 | Apr 14, 2017 3:55:49 AM | Apr 14, 2017 4:01:44 AM | Complete | An OpenStack Contributor | It's positive | There is not so much about the value of OpenStack itself. New "constellation" model looks good, but what makes it better than the current one? The similar for integration with other communities: in the current version it feels like OpenStack community needs to learn more from others, but is there anything we can teach other communities as well? | A bit more words about OpenStack users, who are the target group and what benefits do they get from us? | ||||||||||||||||
98 | 578 | Apr 14, 2017 4:10:58 AM | Apr 14, 2017 4:34:55 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | An OpenStack Contributor | The fact that someone is actually thinking ahead 2 years is encouraging. | If I look at where OpenStack was 2 years ago and the where it is now, and the rate of change in the interim I find the timeline of the vision utterly impossible to achieve, which runs the risk of discounting it entirely — and will also cause an immense deal of frustration to anyone taking making a significant contribution implementing this vision. Has anyone looked at the entirety of this document and given thought to whether it's achievable in the given timeframe given the size (and hence, inherent inertia) of the OpenStack community? To me, this looks like a 5-year vision. Which is a good thing to have, no doubt, but failing to break it down into *achievable* goals will just make people look at this and discount it as wishful thinking. | Intermediate headings. This is a style point, but in my opinion in would reflect positively on the professionalism informing the document. Also, an opening paragraph that answers the age-old question of any lengthy document, talk, or presentation: "why should I care?", or "what's in it for me?" | ||||||||||||||
99 | 580 | Apr 14, 2017 4:24:22 AM | Apr 14, 2017 4:30:45 AM | Complete | An OpenStack Contributor | The vision looks really great! | Everything is perfect from my point of view. | I haven't heard about https://orion.openstack.org before. Didn't get for what is this required. | ||||||||||||||||
100 | 585 | Apr 14, 2017 4:38:58 AM | Apr 14, 2017 4:47:13 AM | Complete | An OpenStack User - Cloud Operator (operator or infrastructure architect) | An OpenStack User - Cloud Consumer (application developer, account/project owner) | The idea about using openstack projects outside of openstack ecosystem. | - | - |