This repository was archived by the owner on Jan 20, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 20, 2021. It is now read-only.
Deploy VM UX on Allowing Creation of Network #624
Description
Describe the bug
In the old UI when I create/deploy a VM I can create a new isolated network by simply entering a name for it during the deploy dialog.
In primate I have to go into a separate dialog in which the default choice is L2 and no description is entered so a few extra steps need to be taken.
To Reproduce
Steps to reproduce the behavior:
- Log in as a User or an Admin
- Go to 'Compute / Instances'
- Click on '+ Add Instance'
- select a zone
- Scroll down to 'Network'
- Here there is no possibility to add an isolated network by just entering a name anymore
Expected behavior
a option as below
instead i have to go through several extra steps and run into an undesired default.
Screenshots
instead
and then
Desktop (please complete the following information):
- OS: N/A
- Browser N/A
- version 1.0.0 20200825
Additional context
Add any other context about the problem here.
Activity
yadvr commentedon Aug 27, 2020
@davidjumani can we make isolated as the default choice?
yadvr commentedon Aug 27, 2020
@DaanHoogland after consultation with Alex, Sven and others we decided that the VM deployment form shouldn't by default allow users to create networks very easily; but only pre-created networks are shown.
Otherwise some users may end up always creating new networks while deploying the VM, but some users may still want those extra steps and that's why the extra steps were introduced to show explicit form to create a network, and also give more options while creating a network (old UI only allowed isolated networks). I'm happy if you want to discuss that on the dev/users ML.
andrijapanicsb commentedon Aug 27, 2020
I also did find it a bit "more-steps-then-needed", but I agree with Rohit - let the users learn to do it the "proper" way - and Primate actually allows for multiple network types to be ad-hoc created, while the old UI only allowed single Isolated network (not shared, not L2, not VPC Isolated)
DaanHoogland commentedon Aug 28, 2020
@rhtyd, @andrijapanicsb giving a way to just enter a name and create a network does not prohibit a create network button. the two are not mutually exclusive. I consider this a feature missing.
yadvr commentedon Aug 28, 2020
I've change milestone to 1.1, we need to discuss this on dev/users ML to see what is the general preference. During preview and testing we were advised against what old UI did therefore you see the change in UX.
[-][BUG] [/-][+]Deploy VM UX on Allowing Creation of Network[/+]