Bug 1581785 - EC2 custom instance type is not displayed as an option in provisioning
Summary: EC2 custom instance type is not displayed as an option in provisioning
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Documentation
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.8.5
Assignee: Red Hat CloudForms Documentation
QA Contact: Matouš Mojžíš
URL:
Whiteboard: ui:ec2:provisioning
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-23 15:43 UTC by Matouš Mojžíš
Modified: 2019-12-19 15:46 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-19 15:46:50 UTC
Category: Bug
Cloudforms Team: Documentation
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Matouš Mojžíš 2018-05-23 15:43:46 UTC
Description of problem:
Maybe I didn't set some required values for custom instance type, but I couldn't make it appear in Properties -> Instance type list.

Version-Release number of selected component (if applicable):
5.8.4.3

How reproducible:
Always

Steps to Reproduce:
1. Add a custom instance type described here: https://bugzilla.redhat.com/show_bug.cgi?id=1557025
2. Refresh provider and check whether instance type is displayed in Compute -> Cloud -> Flavors list
3. Provision instance
4. Go to Properties and try to find already created custom instance type.

Actual results:
Instance type is not in Properties form.

Expected results:


Additional info:

Comment 2 Greg McCullough 2018-05-24 13:45:32 UTC
Discussed with Bronagh, sending to her to review/assign.

Comment 3 Tomas Coufal 2018-05-25 13:56:47 UTC
The instance type is also missing in MIQ provision dialogue (when provision from template/image). I'll take look into that as well

Comment 4 Tomas Coufal 2018-05-31 12:20:24 UTC
Ok, I think it's much more a setup related stuff, which blocked myself as well. I also struggled to understand your description properly. My bad.

You're basically trying to say that when you have a custom flavor defined and you want to provision an instance you would expect this flavor to be listed as "Instance type" under the "Properties" tab. Is that correct?

So the exact steps to reproduce the "missing flavor" would be:
1. Have a EC2 provider
2. Define custom flavor in "Configuration -> Advanced"
3. Refresh the provider so the flavor gets propagated
4. Go to "EC2 Provider summary -> Instances" OR "Compute -> Cloud -> Instances"
5. Provision via "Lifecycle -> Provision Instances"
6. Select EC2 image and "Continue"
7. Under tab "Properties" in the "Instance type" dropdown should be the flavor available

Is that correct?

I found that Provision dialogue limits which flavors can be displayed based on the template (image) properties. So you need to have selected an image with fits the flavor capabilities. Like HVM images has to be deployed as flavor which supports HVM only etc. The same goes for architecture.

Please try a flavor definition like this:

```
...
    :additional_instance_types:
      :custom_type:
        :virtualization_type:
        - :hvm
        :architecture:
        - :i386
        - :x86_64
        :vcpu: 1
        :ebs_only: false
        :instance_store_size: 0
        :instance_store_volumes: 0
        :memory: 536870912
        :description: Some description
        :name: custom_type
...
 ```

And then try to provision an image. Does it show the flavor to you? It works for me.

I think you were missing the architecture definition or at least I was, when I tried for the first time.

Comment 5 Matouš Mojžíš 2018-06-04 12:07:40 UTC
Tomas,

you are right. After adding architecture types custom instance types were displayed in provisioning.
I think this needs documentation as both of us weren't able to make it work at the first time?

Thanks

Comment 6 Tomas Coufal 2018-06-06 11:55:49 UTC
Sure, that sounds good to me. It's not the most straightforward thing around and it would be nice to have this documented.

To sum it up:
If you want to add an Custom flavor for EC2, follow the workflow mentioned in [Comment 4]. You can't forget to specify the virtualization type and architecture since without these values it won't allow you to provision an instance with this flavor.

Forwarding this bug to Documentation team.


Note You need to log in before you can comment on or make changes to this bug.