magnum/api-ref/source
Hongbin Lu 8d53c77c94 Update name of fedora-atomic image
Based on past experience, some failures are caused by using the
stable branch with latest image. That is because the latest image
are supposed to use with master branch.

Let's make this clear by renaming the image from
"fedora-atomic-latest" to "fedora-atomic-newton" in this branch.
In fedorapeople, a soft link was created from
"fedora-atomic-newton.qcow2" to "fedora-23-atomic-20160405.qcow2"

Change-Id: I10e5594b5c5a3ffb9483e7b49bf4325a3c066b1c
2016-09-20 09:23:34 -05:00
..
samples Update name of fedora-atomic image 2016-09-20 09:23:34 -05:00
baymodels.inc Create baymodel/cluster template api reference 2016-09-09 13:08:07 +07:00
bays.inc Create bay/cluster api reference 2016-09-09 14:08:05 +07:00
certificates.inc Create bay/cluster api reference 2016-09-09 14:08:05 +07:00
clusters.inc Create bay/cluster api reference 2016-09-09 14:08:05 +07:00
clustertemplates.inc Create baymodel/cluster template api reference 2016-09-09 13:08:07 +07:00
conf.py Init api-ref structure and requirements 2016-08-29 22:44:08 +07:00
index.rst Create bay/cluster api reference 2016-09-09 14:08:05 +07:00
mservices.inc Create mservices api reference 2016-08-29 23:45:09 +00:00
parameters.yaml Create bay/cluster api reference 2016-09-09 14:08:05 +07:00
status.yaml Init api-ref structure and requirements 2016-08-29 22:44:08 +07:00
urls.inc Init api-ref structure and requirements 2016-08-29 22:44:08 +07:00
versions.inc Create version api reference 2016-08-29 23:44:37 +00:00