Feature #3357

Add option to disable network and capacity selects for all the cloud or per template

Added by Tino Vázquez about 6 years ago. Updated about 6 years ago.

Status:ClosedStart date:11/14/2014
Priority:NormalDue date:
Assignee:Daniel Molina% Done:

100%

Category:Cloud View
Target version:Release 4.10.2
Resolution:fixed Pull request:

Description

At the administrator choice (with a flag porobably in the template, or global setting)

For vOneCloud and hybrid VM Templates


Related issues

Related to Feature #3412: Create a vCenter Cloud View Closed 12/05/2014
Related to Backlog #3478: Add list of authorized/denied instance types/networks per... Pending 12/23/2014

Associated revisions

Revision 34e1a293
Added by Daniel Molina about 6 years ago

feature #3357: Add option to disable capacity and network select

Revision e4904dce
Added by Daniel Molina about 6 years ago

feature #3357: Add option to disable the saved templates functionality

Revision 1c9a2ecc
Added by Daniel Molina about 6 years ago

feature #3357: Add option to disable the saved templates functionality

(cherry picked from commit e4904dce6357d204906f43d69c6ddfb8496c05d6)

Revision d6d6a47d
Added by Daniel Molina about 6 years ago

feature #3357: Add option to disable capacity and network select

(cherry picked from commit 34e1a2931ebb94a175a422dede65771c422e9704)

Revision e42a0e8b
Added by Daniel Molina about 6 years ago

feature #3357: Add option to disable capacity and network selects per template

Revision d1d0e7f5
Added by Daniel Molina about 6 years ago

feature #3357: Add option to disable capacity and network selects per template

Revision 5ec924fa
Added by Daniel Molina about 6 years ago

feature #3357: Check input state

History

#1 Updated by Ruben S. Montero about 6 years ago

  • Target version changed from Release 4.10.1 to Release 4.12

#2 Updated by Ruben S. Montero about 6 years ago

  • Target version changed from Release 4.12 to Release 4.10.2

#3 Updated by Ruben S. Montero about 6 years ago

  • Status changed from Pending to New
This issue is to:
  • add option to enable/disbale the capacity and network sections (create dialog).
  • Enable/disable save_template action on VM view, and list/select saved templates.
  • Configure the actions for Cloud View (e.g. remove delete, or translate poweroff to undeploy)

#4 Updated by Ruben S. Montero about 6 years ago

#5 Updated by Ruben S. Montero about 6 years ago

  • Assignee set to Daniel Molina

#6 Updated by Daniel Dehennin about 6 years ago

Ruben S. Montero wrote:

This issue is to:
  • add option to enable/disbale the capacity and network sections (create dialog).

+1

In our use case, most of the time a user clone a VM template is to increase the capacity or run the VM on its own network, so cloud view is great for us, even if not completely used (#3414).

This could be a true / false or a list of authorized/denied capacities or networks, or two settings, a true / false flag, and when flag is true check a list, for example:

CAPACITY_SELECT = "TRUE",
CAPACITY_ENABLED = [ "small-x1", "small-x2", "medium-x2" ]

In which case, just switching the CAPACITY_SELECT value to FALSE disable all capacities.

For networks, if a user have the USE ACL on a shared network, but a VM has a built-in DHCP server, the admin could opt-in or opt-out the networks usable with this VM, for example:

NETWORKS_SELECT = "TRUE",
NETWORKS_DISABLED = [ "shared_network" ]

The selection should include the _ENABLED list first and then exclude the _DISABLED list.

These parameters should be saved if the user save the VM.

The capacities could be set in the VM template but I see it more useful at user groups, for example:

- every body is authorized to use small-x1, small-x2 and medium-x2
- group need_power can use medium-x4 and large-x4
- group prod_admin can use large-x8

I understand that all of this is useless if the user can update its own VM templates:

  1. user clone a VM
  2. user update the VM template to remove the VM limitations

but the per group limitations stays

Regards.

#7 Updated by EOLE Team about 6 years ago

Tino Vázquez wrote:

For vOneCloud and hybrid VM Templates

I'm not sure if this is a limitation.

If yes, I think cloud.yaml view could use this feature too.

Regards.

#8 Updated by Ruben S. Montero about 6 years ago

  • Category changed from vCenter to Sunstone

Moved this issue to Sunstone category as vcenter driver can now handle vnets. As discussed in the comments this issue does not depends on the hypervisor but on the provisioning model.

#9 Updated by Daniel Molina about 6 years ago

Included options to disable the capacity and network selects for all the cloud in the yaml files and per template in the creation template wizard.

List of authorized or denied is not implemented yet

#10 Updated by Daniel Molina about 6 years ago

  • Subject changed from CloudView should not present the network chosing option when instantiating a Template to Add option to disable network and capacity selects for all the cloud or per template
  • Category changed from Sunstone to Cloud View
  • Status changed from New to Closed
  • % Done changed from 0 to 100
  • Resolution set to fixed

Daniel Dehennin wrote:

Ruben S. Montero wrote:

This issue is to:
  • add option to enable/disbale the capacity and network sections (create dialog).

+1

In our use case, most of the time a user clone a VM template is to increase the capacity or run the VM on its own network, so cloud view is great for us, even if not completely used (#3414).

This could be a true / false or a list of authorized/denied capacities or networks, or two settings, a true / false flag, and when flag is true check a list, for example:

[...]

In which case, just switching the CAPACITY_SELECT value to FALSE disable all capacities.

For networks, if a user have the USE ACL on a shared network, but a VM has a built-in DHCP server, the admin could opt-in or opt-out the networks usable with this VM, for example:

[...]

The selection should include the _ENABLED list first and then exclude the _DISABLED list.

These parameters should be saved if the user save the VM.

The capacities could be set in the VM template but I see it more useful at user groups, for example:

- every body is authorized to use small-x1, small-x2 and medium-x2
- group need_power can use medium-x4 and large-x4
- group prod_admin can use large-x8

I understand that all of this is useless if the user can update its own VM templates:

  1. user clone a VM
  2. user update the VM template to remove the VM limitations

but the per group limitations stays

Regards.

#11 Updated by Daniel Molina about 6 years ago

  • Related to Backlog #3478: Add list of authorized/denied instance types/networks per template added

Also available in: Atom PDF