Back to bug 1388245
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla Rules Engine | 2016-10-24 20:28:33 UTC | Keywords | FutureFeature | |
| Michal Skrivanek | 2016-10-25 04:54:42 UTC | CC | michal.skrivanek | |
| Target Milestone | --- | ovirt-4.1.0-alpha | ||
| Flags | ovirt-4.1.0? | |||
| Yaniv Lavi | 2016-12-08 14:40:03 UTC | Link ID | oVirt gerrit 65979 | |
| Status | NEW | POST | ||
| Link ID | oVirt gerrit 66215 | |||
| Link ID | oVirt gerrit 66319 | |||
| Link ID | oVirt gerrit 66323 | |||
| Link ID | oVirt gerrit 67746 | |||
| Link ID | oVirt gerrit 67747 | |||
| Link ID | oVirt gerrit 67748 | |||
| Link ID | oVirt gerrit 67749 | |||
| Status | POST | MODIFIED | ||
| Link ID | oVirt gerrit 67870 | |||
| Status | MODIFIED | POST | ||
| Target Milestone | ovirt-4.1.0-alpha | ovirt-4.1.0-beta | ||
| Michal Skrivanek | 2016-12-15 12:58:54 UTC | Target Milestone | ovirt-4.1.0-beta | ovirt-4.1.0-rc |
| Tomas Jelinek | 2016-12-16 09:31:40 UTC | Status | POST | MODIFIED |
| CC | tjelinek | |||
| meital avital | 2016-12-19 18:00:23 UTC | Flags | testing_plan_complete? | |
| Sandro Bonazzola | 2017-01-09 16:09:25 UTC | Doc Text | Feature: Maximum Memory value can be specified in all vm-like dialogs (VM, Template, Pool and Instance Type). It is accessible in `{vm, template | |
| Doc Text | , instance_type}/memory_policy/max` tag in REST api. The value defines upper limit up to which memory hot plug can be performed. Suggested value is 4x memory size. | |||
| Doc Type | If docs needed, set a value | Enhancement | ||
| Status | MODIFIED | ON_QA | ||
| Moran Goldboim | 2017-01-17 07:00:30 UTC | Target Release | --- | 4.1.0 |
| CC | mgoldboi | |||
| Gil Klein | 2017-01-19 07:26:48 UTC | CC | gklein | |
| Flags | testing_plan_complete? | testing_plan_complete- | ||
| Tahlia Richardson | 2017-01-23 07:44:23 UTC | CC | trichard | |
| Doc Text | Feature: Maximum Memory value can be specified in all vm-like dialogs (VM, Template, Pool and Instance Type). It is accessible in `{vm, template, instance_type}/memory_policy/max` tag in REST api. The value defines upper limit up to which memory hot plug can be performed. Suggested value is 4x memory size. | This release adds the ability to specify a Maximum Memory value in all VM-like dialogs (Virtual Machine, Template, Pool, and Instance Type). It is accessible in the `{vm, template, instance_type}/memory_policy/max` tag in the REST API. The value defines the upper limit to which memory hot plug can be performed. The default value is 4x memory size. | ||
| Tahlia Richardson | 2017-01-23 07:47:17 UTC | Blocks | 1415592 | |
| Israel Pinto | 2017-02-16 07:06:45 UTC | Depends On | 1422546 | |
| Israel Pinto | 2017-02-16 07:07:25 UTC | CC | ipinto | |
| QA Contact | mavital | ipinto | ||
| Israel Pinto | 2017-02-16 08:00:16 UTC | Flags | testing_plan_complete- testing_ack? | testing_plan_complete+ testing_ack+ |
| Julie | 2017-03-07 05:36:50 UTC | CC | jniederm, juwu | |
| Flags | needinfo?(jniederm) | |||
| Hanns-Joachim Uhl | 2017-03-09 08:28:23 UTC | See Also | https://bugzilla.redhat.com/show_bug.cgi?id=1430451 | |
| Flags | needinfo?(jniederm) | |||
| CC | hannsj_uhl | |||
| Hanns-Joachim Uhl | 2017-03-09 08:29:52 UTC | Blocks | 1359843 | |
| Hanns-Joachim Uhl | 2017-03-09 08:35:00 UTC | Link ID | Red Hat Knowledge Base (Solution) 2788261 | |
| Israel Pinto | 2017-03-14 11:52:57 UTC | Status | ON_QA | VERIFIED |
| Sandro Bonazzola | 2017-03-16 14:48:44 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2017-03-16 10:48:44 UTC |
Back to bug 1388245