3. Storage Driver
LVM
Ceph
Other
NFS
NetApp
GlusterFS
EMC
Windows
SAN/HP
Nexenta
Xenapi
SAN/Solaris
SolidFire
XIV
Storwize
Coraid
HP LeftHand
HP 3PAR
Zadara
ZFS
Sheepdog
Scality
Huawei
Custom
XenAPI…
EqualLogic
iSCSI
Other
Mellanox
Deployment tool
Puppet
138
Chef
77
71
15
13
12
9
8
8
7
5
5
5
4
4
3
3
3
3
3
3
2
2
1
1
1
35
DevStack
PackStack
SaltStack
Crowbar
Substratum
StackOps
Other
Fuel
Ansible
None
Foreman
FAI
CFEngine
Anvil
OpenVswitch
Linux Bridge
Other
260
37
32
72
Network Driver
86
39
16
8
8
2
2
2
2
2
1
1
1
1
1
155
Cisco
Nicira
Hyper-V
Brocade
Big Switch
Ryu
Other
NEC
PLUMgrid
MidoNet
Juniper
Modular
Mellanox
Custom
Arista
kvm
111
50
Centos
49
Other
125
145
Other
49
esx
38
22
41
RHEL
21
xenserver
23
Windows
QEMU
23
Debian
lxc
15
12
7
6
4
4
3
3
3
2
2
2
2
Ubuntu
312
xen
101
Other
OS
Hypervisor
21
openSUSE
3
SUSE Linux…
3
hyperv
13
Bare Metal
13
OpenVZ
5
Other
4
PowerVM
6
Fedora
3
Scientific Linux
2
Other
1
FreeBSD
1
1
Docker
9
1
Identity Driver
SQL
171
LDAP
103
PAM
20
KVS
Templated
13
2
4. Production Scale
64
# of Instances
# of Cores
# of nodes
63
More than 1,000
11
51-100
27
22
17
501-1,000
15
9
5
34
5
101-500
40
# of Stored Objects
43
11
More than 500 M
11
100-500 TB
100 M to 500 M
21
1 M to 100 M
9
11-100 TB
0-10 TB
39
46
less than
100
10
97
# of IP
Block Storage Size
8
14
1-50
> 500 TB
17
11
101 to
1,000
1,001 to
10,000
More
than
10,000
100,001 to 1 M
10,001-100,000
1-10,000
1
3
4
11
14
34
12. Foundation Priorities
(Feedback from April 2013)
• Simplify installation and configuration process
• Rolling migrations with N-1 compatibility
• Documentation–archive old content, end-user guide, problem guide, …
• Security such as SSL options everywhere
• Horizon lacks latest feature support, admin functionality and more
attractive theme
• High availability out-of-the-box for OpenStack components and VM
restart
• Active Directory integration
13. Operations Feedback Loop
1. User Committee anonymises the feedback
• Ensure data confidentiality is preserved
• Groups comments into different areas
2. Volunteers needed by area
• Operations experience is needed as feedback is often brief and requires
interpretation
• Technical OpenStack knowledge is also needed to work with the developers
• Some time to dedicate to the task
3. Translate the user feedback into user stories
• Several user stories per area to consolidate the needs
• Prioritise based on impact and implementation
14. Operations Feedback Loop (II)
4. Work with development community to produce blueprints
• Incremental, small steps
• Realistic proposals essential
• Provide sounding board for proposals from the developers
5. If further resources needed for implementation, slots to present to
the board and technical committee can be arranged
• TC has already received a summary of the comments before the summit to
assist in the design sessions
15. Can you help ?
• If you are interested, have the time to help and the skills to bridge
from user feedback to development, please get in touch with us
• user-committee@lists.openstack.org
• Follow up discussions on the operations list to refine requirements
and maximise inclusion
• openstack-operators@lists.openstack.org
16. References
• Survey November 2013 at
http://www.openstack.org/assets/Uploads/Deployments-IceHousev1.1.pptx
• Survey April 2013 at http://www.openstack.org/summit/portland2013/session-videos/presentation/openstack-user-committeeupdate-and-survey-results
18. Foundation Priorities
(Feedback from April 2013)
• Ensure compatibility across different implementations
• Stability/Hardening of existing functionality
• Establish certification program
• Encourage training for different skill sets
• Support user groups, especially outside U.S.