[WIP] Feature/vm wizard

[iceteabottle]

• Add selection for disk offering
• Format Info card for vm config summary
• Add iso selection
• Add tags to the templates (featured, public, etc.)
• Sort templates/isos
• Pin featured templates/isos at the top of each list
• Add search filter input for isos/templates
• Handle form change on switching from template to iso (and vice versa)
• Add translations for all input placeholders
• Implement submit method
• Add affinity group selection
• Add network selection
• Add ssh key pairs selection
• Handle Navigation (e.g. reset the form on navigating away)
• Add filter possibility to selections (compute offering, disk offering, network offering, ...)

[yadvr]

@iceteabottle thanks for resuming this. One request from last time I tested your component/form, can you add the device mixin to hide the infocard on mobile?

[iceteabottle]

Current status:

[iceteabottle]

@iceteabottle thanks for resuming this. One request from last time I tested your component/form, can you add the device mixin to hide the infocard on mobile?

Done.

[iceteabottle]

Iso Selection (WIP):

[iceteabottle]

I updated the tagging of the isos.

I plan to apply this tagging also for the template selection.

[yadvr]

Nice @iceteabottle - do you think instead we could have an explicit tab of featured templates (use the star icon), rest looks great!

[iceteabottle]

Nice @iceteabottle - do you think instead we could have an explicit tab of featured templates (use the star icon), rest looks great!

Thanks. Maybe I could pin the featured above instead of breaking the OS tabs logic. What do you think, @rhtyd ?

[yadvr]

@iceteabottle that's good idea as well, so basically show features templates? However, per the old CloudStack templates have a sort order so I don't know if that would break anything esp. in env with large number of templates. cc @PaulAngus @svenvogel ?

[svenvogel]

@rhtyd Hi Rohit

in the old wizard there are these tabs. do you mean this one?

or

the order in the templates menu?

[yadvr]

Hi @svenvogel in the second screenshot, the order is used to determine the sort order of a resource. CloudStack stores the order in sort_key in the data_center, vm_template and offerings related tables in the cloud db. This sort order is then used to render the sequence of items in the list API response by default, so whatever sort order the admin configures; the templates show up in the UI with that order for each tab (featured, community etc...)

[iceteabottle]

@rhtyd I wrapped each inner wizard components into a collapsable item to improve the UX.
I will prepare my branch for @utchoang these days.

[yadvr]

@utchoang please pick this one next, in consultation with @iceteabottle and @svenvogel. Let me know if you've any questions or need any help.

[iceteabottle]

@rhtyd Today I will add the last major form part "ssh key pairs selection" to finish the main layout stuff. Can you please merge this PR tomorrow? Then @utchoang can continue my work in his own fork.

[iceteabottle]

Add SSH keypair selection.

[svenvogel]

@utchoang can you resume here please?

[iceteabottle]

@utchoang can you resume here please?

@utchoang please see my checklist #7 (comment)

@rhtyd please merge this PR so @utchoang can finish this feature.

Thanks for the cooperation in this project. I'm sorry that I have to discontinue my work here.

[utchoang]

@iceteabottle Thank you so much.
@svenvogel I will start working on it after @rhtyd finishes merging this PR.

[svenvogel]

@rhtyd can you merge that we can proceed?

[yadvr]

@utchoang @svenvogel I'll squash merge this per your request, I've not tested it. Just checked and added license header to some files.

[yadvr]

@utchoang you can continue on it now, raise a new PR. When you do checkout latest master, ensure it's same as origin master by doing:

git fetch origin master
git checkout master
git reset --hard origin/master
git checkout -b 'new-branch-name for your new PR'