| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
@ravening could you give me some of the use cases for this change please, I'm not quite following. |
Sorry, something went wrong.
@PaulAngus if template has a tag "windows" then the VM's created using this template should be deployed on hosts with tags "windows". Same thing for templates having tags like "linux", "Unix" it any other tag. So we should not deploy templates having "windows" tag on hosts having "linux" tag Hope it's clear |
Sorry, something went wrong.
|
@ravening Needs conflicts to be resolved. Moving to 4.16.0.0 milestone based on base branch please update if needed |
Sorry, something went wrong.
|
as #4452 has been merged, build will fail. |
Sorry, something went wrong.
|
@ravening any update on this please |
Sorry, something went wrong.
|
good functionality, clear description and sane as far as I can tell. |
Sorry, something went wrong.
|
@DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✖️ el7 ✖️ el8 ✖️ debian ✖️ suse15. SL-JID 946 |
Sorry, something went wrong.
|
ping @ravening, can you fix conflicts |
Sorry, something went wrong.
|
@nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 1290 |
Sorry, something went wrong.
|
running test_host_tags.py, I get Test template/host tag ... === TestName: test_01_template_host_tag | Status : EXCEPTION ===
ERROR
======================================================================
ERROR: Test template/host tag
----------------------------------------------------------------------
Traceback (most recent call last):
File "/marvin/tests/component/test_host_tags.py", line 210, in test_01_template_host_tag
cls.vm_3.start(cls.apiclient, hostid = host.id)
File "/usr/local/lib/python3.6/site-packages/marvin/lib/base.py", line 722, in start
apiclient.startVirtualMachine(cmd)
File "/usr/local/lib/python3.6/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py", line 4014, in startVirtualMachine
response = self.connection.marvinRequest(command, response_type=response, method=method)
File "/usr/local/lib/python3.6/site-packages/marvin/cloudstackConnection.py", line 381, in marvinRequest
raise e
File "/usr/local/lib/python3.6/site-packages/marvin/cloudstackConnection.py", line 376, in marvinRequest
raise self.__lastError
File "/usr/local/lib/python3.6/site-packages/marvin/cloudstackConnection.py", line 105, in __poll
% async_response)
Exception: Job failed: {accountid : 'e423f3e7-16f6-11ec-a2d3-1e00b900043d', userid : 'e4251d92-16f6-11ec-a2d3-1e00b900043d', cmd : 'org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin', jobstatus : 2, jobprocstatus : 0, jobresultcode : 530, jobresulttype : 'object', jobresult : {errorcode : 431, errortext : 'The virtual machine dd283411-86dd-4b94-866c-3d32dd72a89c (Test VM) is already running'}, jobinstancetype : 'VirtualMachine', jobinstanceid : 'dd283411-86dd-4b94-866c-3d32dd72a89c', created : '2021-09-17T10:44:08+0000', completed : '2021-09-17T10:44:08+0000', jobid : '0e11e39a-3329-4cdd-820f-6f904480b5f1'}
running test_template_tags.py executing /usr/local/bin/nosetests --with-xunit --xunit-file=/marvin/MarvinLogs/test_template_tags.py.xml --with-marvin --marvin-config=/marvin/pr4362-t2092-kvm-centos7-advanced-cfg --hypervisor=kvm -s -a tags=advanced tests/component/test_template_tags.py ==== Marvin Init Started ==== === Marvin Parse Config Successful === === Marvin Setting TestData Successful=== ==== Log Folder Path: /marvin/MarvinLogs/Sep_17_2021_11_08_00_IQNIPQ All logs will be available here ==== === Marvin Init Logging Successful=== ==== Marvin Init Successful ==== === TestName: test_01_update_template_tags | Status : SUCCESS === === TestName: test_02_register_template_with_tags | Status : SUCCESS === |
Sorry, something went wrong.
Sorry, something went wrong.
|
follow up: |
Sorry, something went wrong.
@DaanHoogland i will look into it and get back to you |
Sorry, something went wrong.
|
Hi @ravening can you please fix the conflicts? |
Sorry, something went wrong.
|
Hi @${author}, your pull request has merge conflicts. Can you fix the conflicts and sync your branch with the base branch? |
Sorry, something went wrong.
1. Match the template tags with host tags for vm deployment/migration 2. Allow updating templates/isos with template tag by admin 3. Allow adding template tag while registering/creating template/iso 4. Allow searching templats/isos using template tags If a template has template tag then deploy the vm which uses this template on hosts which matches the template tags. If no suitable hosts are found then throw exception Similarly match the template tag with host tags while starting or migrating a vm to a different host
|
@nvazquez done |
Sorry, something went wrong.
|
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description
If a template has a template tag then deploy the VM which uses this
template on hosts that match the template tags. If no suitable
hosts are found then throw an exception
Similarly, match the template tag with host tags while starting or
migrating a VM to a different host
Types of changes
Screenshots (if appropriate):
How Has This Been Tested?
test 1
add different tag to template than hosts
try to deploy. it should fail
try to migrating existing vm. it should fail
test 2
remove all the tags on template
add tags to hosts
try to deploy vm
it can be deployed on any host
try to migrate it.
migration should be possible
stop/start is also possible
test 3
add tag to template
remove tags from host
try to deploy vm
deployment should fail
try to migrate already created vm with template tag
migration should fail
test 4
set same template tag on template and only one host
try to deploy vm
it should deploy vm on host with matching tag
test 5
ow try to migrate above created vm having specific tag
migration should fail as other hosts have either no tags or different tag
test 6
stop the above created vm
try to start of different host
start should fail as the tags dont match
test 7
now remove the tag from the template of the above created vm
try to migrate it
it should work fine
test 8
remove all tags from everyhwere
select any vm and set service offering tag as "ubuntu"
now set host tag as "windows" for all hosts
try to start/deploymigrate vm
it should not start/deploy/migrate as tags dont match
test 9
now set service offering tag as "windows"
try to start/deploy/migrate
it should successfully start/deploy/migrate on/to any host
Same steps for iso as well