magnum/magnum/objects
Jaycen Grant 06f056f606 Allow keypair to be added during cluster create
Keypair can now be added during Cluster create command. This allows
Clusters to be created from the same ClusterTemplate but have
different keypair values when created. If not specified on create
then the value from the ClusterTemplate will be used. Adds keypair_id
to Cluster object and uses of keypair_id will use the value from Cluster
instead of ClusterTemplate.

Added release note for new features in magnum and magnum CLI.

Change-Id: I177a5aa06f881156944a9f74c9ccc3cd2abac492
Implements: blueprint keypair-override-on-create
2016-10-06 17:25:09 +00:00
..
__init__.py Rename Bay DB, Object, and internal usage to Cluster 2016-09-08 13:01:12 -07:00
base.py Use obj_attr_is_set to check whether an attr is set in oslo_versionedobject 2016-03-01 23:20:19 +08:00
certificate.py Rename bay to cluster in certificate object and references 2016-09-01 08:48:24 -07:00
cluster.py Allow keypair to be added during cluster create 2016-10-06 17:25:09 +00:00
cluster_template.py Rename Bay DB, Object, and internal usage to Cluster 2016-09-08 13:01:12 -07:00
fields.py Restrict server type only to vm/bm 2016-09-16 14:48:44 +05:30
magnum_service.py Cleanup MagnumService Object usage 2016-01-29 15:39:28 +08:00
x509keypair.py X509keypair cleanup 2016-05-30 12:02:26 +05:30