Browse code

Update cirros256 flavor to have some disk

It seems nova has changed defaults on who can create zero-sized disk
instances [1] and now some devstack jobs, like nodepool's, can't
create cirros images using this flavor. It seems the easiest thing to
do is just to bump it up.

[1] https://review.openstack.org/#/c/603910/

Change-Id: I1172d4775d608568ccbeb27e2975d83add892ea9

Ian Wienand authored on 2019/02/19 12:06:18
Showing 1 changed files
... ...
@@ -1167,7 +1167,7 @@ function create_flavors {
1167 1167
     if is_service_enabled n-api; then
1168 1168
         if ! openstack --os-region-name="$REGION_NAME" flavor list | grep -q ds512M; then
1169 1169
             # Note that danms hates these flavors and apologizes for sdague
1170
-            openstack --os-region-name="$REGION_NAME" flavor create --id c1 --ram 256 --disk 0 --vcpus 1 cirros256
1170
+            openstack --os-region-name="$REGION_NAME" flavor create --id c1 --ram 256 --disk 1 --vcpus 1 cirros256
1171 1171
             openstack --os-region-name="$REGION_NAME" flavor create --id d1 --ram 512 --disk 5 --vcpus 1 ds512M
1172 1172
             openstack --os-region-name="$REGION_NAME" flavor create --id d2 --ram 1024 --disk 10 --vcpus 1 ds1G
1173 1173
             openstack --os-region-name="$REGION_NAME" flavor create --id d3 --ram 2048 --disk 10 --vcpus 2 ds2G