Hi,

The user shouldn't be allowed to choose an instance flavor that is not
large enough for the image to deploy. Otherwise an error is reported only
when launching (and fails to launch) the Instance.

Steps to reproduce:
1. Click Compute:Instances (left menu)
2. Click Launch new instance button
3. Click Launch on desired Image (tested for: cep-r3.3.3-img, ID:
4dd7a854-14f6-4111-8f28-ee4a9f744acc, in Mexico Region)
4. Insert an Instance name
5. Select m1.tiny flavor
6. Select a security group, select a network zone and click next until
Summary tab
7. Launch click launch instance

Result: an error message is presented:
«Error launching instance test image. Cause: 400 Error
"{"badRequest": {"message": "Flavor's disk is too small for requested
image.", "code": 400}} "», as shown in attached picture.

Now the user has repeat all the steps to launch the instance choosing a
larger instance flavor than the previous one, moreover if only the largest
Instance flavor fits the image, the user could have to repeat the same
steps many time until he chooses a flavor that fits the image.

Browser: Google Chrome

• Responsible: OneSource
• Description: Create Instance - only instance flavors adapted to the
  image to deploy should be listed
• Environment: FIWARE Lab

Best regards,
–
Pedro Alves

pgalves@onesource.pt

http://onesource.pt

_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help