# 2014-06-17 DefCore Capabilities Scoring¶

The DefCore team has put together a scorecard combining many criteria to evaluate which capabilities of OpenStack should be considered core. They have asked the TC to help fill in the “Aligns with Technical Direction” section, replacing the score in each cell with either 0 (for “not needed”) or 1 (for “required”).

The table below includes the three columns from the “Aligns with Technical Direction” of the original scorecard:

TC Future Direction

Does the Technical Committee plan to continue supporting this feature?

Complete

Is the feature currently implemented and fully working?

Stable

Is the API for the feature stable enough to support over a long period?
Row Candidate Capabilities TC Future Direction Complete Stable
4 compute-servers 1 1 1
5 volume 1 1 1
6 compute-volume 1 1 1
7 compute-quotas 1 1 1
8 compute-flavors 1 1 1
9 images-v1 1 1 1
10 compute-auth 1 1 1
11 images-v2 1 1 1
12 objectstore-object 1 1 1
13 compute-keypairs 1 1 1
15 objectstore-container 1 1 1
16 volume-snapshots 1 1 1
17 compute-images 0 1 1
18 compute-floating-ips 1 1 1
19 compute-instance-actions 1 1 1
20 compute-security-groups 1 1 1
22 objectstore-container-quota 1 1 1
23 compute-virtual-interfaces 1 1 0
24 objectstore-container-acl 0 1 1
25 objectstore-acct-services 0 1 1
26 objectstore-container-staticweb 0 1 1
28 compute-usage 0 1 1
29 compute-limits 1 1 1
30 networks-extensions 1 1 1
31 networks-l2 1 0 0
32 compute-ext-disk-config 0 1 0
33 networks-l3 1 0 0
34 compute-live-migration 1 0 0
35 compute-servers-personality 0 1 1
36 networks-floating-ips 1 0 0
37 networks-security-groups 1 0 0
38 networks-lbaas 1 0 0
39 orch-stacks 0 0 0
40 compute-multiple-create 1 1 1
41 networks-vpn 1 0 0
42 compute-attach-interface 0 0 0
43 networks-quotas 1 0 0
44 compute-auth-v3 1 0 0
45 compute-volume-proxy 0
46 compute-volume-ebs 0
47 compute-console-log 1 0 0
57 volume-multi-backend 1 1 1
61 objectstore-quotas 1 1 1