Skip to content

Being able to change offerings (compute / Network / Disk) #8188

Description

@pcfriek1987
ISSUE TYPE
  • Feature Idea
COMPONENT NAME
Service Offerings
CLOUDSTACK VERSION
4.18.1
CONFIGURATION

N/A

OS / ENVIRONMENT

N/A

SUMMARY
STEPS TO REPRODUCE
Try to edit for example the default egress rules under network offerings or adjust the storage type of the compute offerings from shared to local when using only local storage.
EXPECTED RESULTS
Being able to change those values so I do not need to create a new offering every time something needs to be adjusted.
ACTUAL RESULTS
There is no way to adjust anything besides the name, description.

Activity

  1. boring-cyborg commented on Nov 6, 2023

    @boring-cyborg

    Thanks for opening your first issue here! Be sure to follow the issue template!

  2. changed the title [-]Change offerings (compute / Network / Disk)[/-] [+]Being able to change offerings (compute / Network / Disk)[/+] on Nov 6, 2023
  3. DaanHoogland commented on Nov 6, 2023

    @DaanHoogland
    Contributor

    We already discussed some possible definitions of this enhancement on the users@cloudstack.apache.org list. see https://lists.apache.org/thread/nj3t2xp200fcx254fdxqll66694hclol

    As an operator I want to be able to edit an offering by adjusting the default egress rules from deny to allow or vice versa and being able to adjust the storage from shared to local.

    This can be implemented for instance:

    • extra input parameters to the request that will be ignore in case the offering is in use
    • a force flag on the API request
    • a global setting that will allow it
    • a (global) setting that lists the allowable fields for update; i.e. service.offering.allowed.update.fields = name,description,default_acl,...

    (names are just illustrative)

    full discussion: https://lists.apache.org/thread/gjsz8gvol589jplwgx42yzwjlks1yx1s

  4. added this to the unplanned milestone on Jan 12, 2024
  5. github-actions commented on Jan 3, 2026

    @github-actions

    This issue is stale because it has been open for 120 days with no activity. It may be removed by administrators of this project at any time. Remove the stale label or comment to request for removal of it to prevent this.

  6. github-actions commented on Sep 9, 2026

    @github-actions

    This issue is stale because it has been open for 120 days with no activity. It may be removed by administrators of this project at any time. Remove the stale label or comment to request for removal of it to prevent this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions