Bug #5518
Cost calculations take into account only the base template (oneFlow)
| Status: | Pending | Start date: | 10/31/2017 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Abel Coronado | % Done: | 100% | |
| Category: | Sunstone | |||
| Target version: | Release 5.4.4 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | Development |
Description
If you add the vm_template_content attribute in service template, the cost calculation (before instantiating the service) doesn't take it into account.
"vm_template_contents": "APPEND=\"NIC,DISK\"\nDISK=[TYPE=\"FS\",SIZE=\"1024\"]\nDISK=[TYPE=\"FS\",SIZE=\"1024\"]\nNIC=[NETWORK_ID=\"1\"]\nCPU=\"2\"\nMEMORY=\"6144\""
Calculates the cost with the disks, cpu and ram of the base template.
Associated revisions
B #5518: Cost calculations take into account only the base template (oneFlow)
B #5518: Cost calculations take into account only the base template (oneFlow)
(cherry picked from commit e8be19ff53819ab9bca851f22d8a154da88468a1)
History
#1
Updated by Tino Vázquez over 3 years ago
- Target version changed from Release 5.4.4 to Release 5.4.3
#2
Updated by OpenNebula Systems Support Team over 3 years ago
- Target version changed from Release 5.4.3 to Release 5.4.4