Skip to content

Conversation

@dhlaluku
Copy link

Description

Currently, CloudStack does not allow additional configuration metadata to guest VMs during deployment. This feature aims to provide operators the functionality to pass arbitrary additional configuration metadata that will be included everytime the guest VM is started.

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)

GitHub Issue/PRs

Screenshots (if appropriate):

How Has This Been Tested?

Checklist:

  • I have read the CONTRIBUTING document.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
    Testing
  • I have added tests to cover my changes.
  • All relevant new and existing integration tests have passed.
  • A full integration testsuite with all test that can run on my environment has passed.

@dhlaluku dhlaluku changed the title [WIP] Allow additional configuration metadata to VM during deployment [WIP] Allow additional configuration metadata to VM during deployment (review) Jul 25, 2018
@rohityadavcloud rohityadavcloud changed the base branch from master to 4.0 July 25, 2018 09:43
@rohityadavcloud rohityadavcloud changed the base branch from 4.0 to master July 25, 2018 09:43
@dhlaluku dhlaluku force-pushed the allow-additional-config-to-vms branch from a107bc3 to 43103ff Compare August 14, 2018 09:07
Copy link
Member

@rohityadavcloud rohityadavcloud left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall good work Dingane, left some comments and TODOs.

@rohityadavcloud
Copy link
Member

@dhlaluku can you also rebase against latest master and fix conflicts.

@dhlaluku dhlaluku force-pushed the allow-additional-config-to-vms branch from badb526 to bec3e28 Compare August 28, 2018 14:32
@dhlaluku dhlaluku force-pushed the allow-additional-config-to-vms branch from 96189b3 to 0fa8aa0 Compare October 11, 2018 08:53
@rohityadavcloud rohityadavcloud changed the base branch from master to 4.11 October 11, 2018 09:20
@rohityadavcloud rohityadavcloud changed the base branch from 4.11 to master October 11, 2018 09:20
@dhlaluku dhlaluku force-pushed the allow-additional-config-to-vms branch from 0fa8aa0 to 3f5c7e9 Compare October 12, 2018 08:25
@dhlaluku dhlaluku force-pushed the allow-additional-config-to-vms branch from 65921a2 to 1fa4375 Compare November 27, 2018 08:51
@dhlaluku dhlaluku changed the base branch from master to 4.11 November 27, 2018 08:53
@borisstoyanov
Copy link
Member

borisstoyanov commented Dec 6, 2018

@dhlaluku
Copy link
Author

@nvazquez @DaanHoogland, please review

@dhlaluku
Copy link
Author

@nvazquez @DaanHoogland @rhtyd may you please have a look at this PR. @rhtyd you requested changes a while back when you reviewed this PR, please have another and advice on any revisions required.

@dhlaluku dhlaluku changed the title [WIP] Allow additional configuration metadata to VM during deployment (review) Allow additional configuration metadata to VM during deployment Mar 1, 2019
@dhlaluku dhlaluku force-pushed the allow-additional-config-to-vms branch from 96dc83d to fcb7d86 Compare March 7, 2019 13:23
@dhlaluku dhlaluku changed the base branch from master to 4.11 March 9, 2019 11:39
@dhlaluku dhlaluku changed the base branch from 4.11 to master March 9, 2019 11:40
host = list_hosts(
self.apiclient,
id=host_id,
hypervisor='kvm')
Copy link
Member

@borisstoyanov borisstoyanov Mar 11, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This shouldn't be 'kvm' hardcoded, but instead use 'testClient.getHypervisorInfo()' to set a class var. In this case hypervisors !=kvm will run

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done, now using self.hypervisor.lower()

@dhlaluku dhlaluku force-pushed the allow-additional-config-to-vms branch from 4d2cc85 to 4d1d4f4 Compare March 12, 2019 14:08
nvazquez and others added 7 commits July 17, 2019 20:13
Fix small UI issue when dedicating public IR range for system VMs:
Unable to execute API command createvlaniprange due to invalid value. Invalid parameter domainid value=undefined due to incorrect long value format, or entity does not exist or due to incorrect parameter annotation for the field in api cmd class.

Fixes: apache#3485
* Add revoke certificates API

* Add background task to sync certificates

* Fix marvin test and revoke certificate

* Fix certificate sent to hypervisor was missing headers

* Fix background task for uploading certificates to hosts
* Allow users to share templates with Accounts or Projects through the
updateTemplate permissions API

* Change behaviour to show only supported projects and accounts with update template permissions

* Allow admins to see accounts dropdown and only hide lists for users

* Don't allow sharing project owned templates as you cannot retrieve them in list api calls
…he#3504)

Set integration.api.port to (0) zero as default. CloudStack provides CloudStack API Unauthenticated Access through port 8096. It should not be open to the Internet in any case.
During volume stats calculation, if a volume has more than one disk in
the chain-info it is not used to sum the physical and virtual size
in the loop, instead any previous entry was overwritten by the last disk.

Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
…ot started before (apache#3494)

When VM is created but not started on any host, attaching a volume on it causes the maximum number of allowed volumes to be 6 (hardcoded).
… vlans when adding ipranges (apache#3430)

Fixes: apache#3114

When adding iprange for VLANs there are 3 cases -

VLAN under consideration has a tag (like 101)
VLAN under consideration has a tag but as a range (like 101-124)
VLAN is untagged (i.e. id is "untagged")
Before adding iprange we have to check for possible overlaps and throw exception. This needs to be done as follows -

If VLAN Tag ID is numeric or a range we need to call UriUtils.checkVlanUriOverlapmethod which internally tries to expand the range as verifies if there are overlaps. If URI overlaps (i.e. there are overlapping VLAN tags) we then need to verify if the iprange being added overlaps with previously added ranges.
If there are no overlapping tags we simply need to test for public networks being present in the VLAN.
A Regression was introduced in 41fdb88#diff-6e2b61984e8fa2823bb47da3caafa4eeR3174 which caused comparing 'untagged' string as a numeric VLAN Tag range and and attempted expanding it to test overlap in UriUtils.checkVlanUriOverlap.

To fix the bug in the issue, we need to handle the untagged case separately as it's non-numeric tag in code. For untagged VLANs and overlapping VLAN URIs we need to check for ipranges and gateways which happens naturally after this change. For tagged VLANs with non-overlapping URIs we need to check if there is a public network.
@borisstoyanov
Copy link
Member

@rhtyd @nvazquez @shwstppr @anuragaw, this is FR04 from the roadmap items, it needs to be rebased and there's merge conflicts.

Dingane Hlaluku and others added 3 commits July 23, 2019 15:06
Update marvin tests to use white list
* Add new marvin negative tests cases
* Remove hard-coded hypervisor types in marvin tests
@anuragaw anuragaw force-pushed the allow-additional-config-to-vms branch from 6e864b7 to d0fcd97 Compare July 23, 2019 10:17
@anuragaw
Copy link

Closing this and opening a public PR as advised.

@anuragaw anuragaw closed this Jul 23, 2019
rohityadavcloud pushed a commit that referenced this pull request Jan 20, 2021
Fixes: #17
Fixes: #18

These dependencies are necessary or eslint will fail with the standard vue.js rule set.
The PR also includes fixes for all lint errors.

Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
shwstppr pushed a commit that referenced this pull request Jul 27, 2021
Co-authored-by: Pearl Dsilva <pearl.dsilva@shapeblue.com>
rohityadavcloud pushed a commit that referenced this pull request Oct 16, 2024
[4.18] server, api: account and api entity access improvements
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants