Bug #2764
FREECPU/FREE_CPU inconsistencies (core/sunstone/doc)
| Status: | Closed | Start date: | 02/27/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Carlos Martín | % Done: | 0% | |
| Category: | Documentation | |||
| Target version: | Release 4.6 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.4 |
Description
Hi,
We were using FREECPU for VM placement with OpenNebula 4.2.0. Since Feature #2145 and OpenNebula 4.4 it doesn't work anymore. Looking at source code, it looks we have to use FREE_CPU instead. But the documentation and Sunstone wizard booth make use of FREECPU.
This is really confusing !
Just run a grep FREECPU and grep FREE_CPU on the source code tree to figure it out...
Is there any mean to easily replace this parameter inside all running VM instances and templates ?
Best regards,
Laurent
Associated revisions
Bug #2764: Use free_cpu instead of freecpu in sunstone
Bug #2764: onedb will replace deprecated host attributes in existing templates
History
#1
Updated by Ruben S. Montero over 7 years ago
- Category set to Documentation
- Status changed from Pending to New
- Assignee set to Javi Fontan
- Target version set to Release 4.6
Agree, thanks for the heads up.
#2
Updated by Ruben S. Montero over 7 years ago
This should be taken care by the upgrade process, we'll look into it
#3
Updated by Ruben S. Montero over 7 years ago
- Assignee changed from Javi Fontan to Carlos Martín
#4
Updated by Carlos Martín over 7 years ago
- Status changed from New to Closed
- Resolution set to fixed
Hi Laurent,
Thanks a lot for letting us know. When we cleaned the monitoring attributes in #2145, we didn't realize we were using them ourselves in sunstone and the doc.
The documentation for the rank/requirements has been updated, and a note in the known issues added.
http://docs.opennebula.org/stable/release_notes441/known_issues441.html
The "good" values, that you can find in HOST/HOST_SHARE with onehost show -x, are:
=============== =============== 4.2 4.4 =============== =============== TOTALCPU MAX_CPU TOTALMEMORY MAX_MEM FREECPU FREE_CPU FREEMEMORY FREE_MEM USEDCPU USED_CPU USEDMEMORY USED_MEM =============== ===============
The upgrade process to 4.6 will scan existing Templates and replace these strings.
Unfortunately, this is not of much help for your existing 4.4 installation... Maybe I can cook a special onedb fsck tool for this, I'll get back to you.
#5
Updated by Carlos Martín over 7 years ago
Hi again,
Try this fsck file, it has an extra section to change the wrong metric attributes: https://gist.github.com/carlosms/9394393
Copy it into /usr/lib/one/ruby/onedb/fsck.rb, and then follow the fsck procedure described here:
http://docs.opennebula.org/stable/administration/references/onedb.html#onedb-fsck
#6
Updated by Laurent Grawet over 7 years ago
Hi Carlos,
Thanks for the work. We have already modified FREECPU attributes manually so I can't test fsck anymore.