yeah, Daniel and Nikola, you are right.
Before, I find no numa in a host by the numactl --hardware, so I think that
there may be no numa topo.
I made the following test, and find that the libvirt return a numa even if the
value from the numactl is zero.
thanks.
root@tralon-Vostro-1400:~#
Public bug reported:
Currently, the value of scheduler_default_filters is real one, not
default one. so the scheduler_default_filters option is misleading.
** Affects: nova
Importance: Undecided
Assignee: zhangtralon (zhangchunlong1)
Status: New
** Changed in: nova
Public bug reported:
when only using huge page parameter without numa to create vms, the current
code can generate
an instance numatopology with a numa cell.
the solution will filter some hosts which meet the
need of huge page but no numa.
I think that binding the huge page with numa so
Public bug reported:
There is no dealing with the force_host/force_node options in the
ChanceScheduler, which means that the force_host/force_node options
doesn't work.
** Affects: nova
Importance: Undecided
Assignee: zhangtralon (zhangchunlong1)
Status: New
** Changed
not only reduces the possibility of reboot failure but also keep paces
with the other operation
after the nova-compute process reboots.
** Affects: nova
Importance: Undecided
Assignee: zhangtralon (zhangchunlong1)
Status: New
** Changed in: nova
Assignee: (unassigned
** Also affects: cinder
Importance: Undecided
Status: New
** No longer affects: cinder
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1403020
Title:
Kwarg
Public bug reported:
creating ordinary vm may fails with large page vm and ordinary vm on the
same numa node.
the following scene can reproduce the problem:
1. Assumpt that a host with two numa nodes are used to create vm, and the
memory of each numa node consists of 5GB huge page and 5GB
** Also affects: cinder
Importance: Undecided
Status: New
** No longer affects: cinder
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1403020
Title:
Kwarg
: zhangtralon (zhangchunlong1)
Status: New
** Changed in: nova
Assignee: (unassigned) = zhangtralon (zhangchunlong1)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs
Public bug reported:
we should remove the detail method from the LimitsController class
because the detail is not the default method and it doesn't add the
detail operation in the _setup_routes method from the class APIRouter
** Affects: nova
Importance: Undecided
Status: New
--
: zhangtralon (zhangchunlong1)
Status: New
** Changed in: nova
Assignee: (unassigned) = zhangtralon (zhangchunlong1)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs
: zhangtralon (zhangchunlong1)
Status: New
** Changed in: nova
Assignee: (unassigned) = zhangtralon (zhangchunlong1)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs
Public bug reported:
the parameter filter_class_names from funciton get_filtered_hosts is
not assigned values, so we always use the filters from
CONF.scheduler_default_filters.
** Affects: nova
Importance: Undecided
Assignee: zhangtralon (zhangchunlong1)
Status: New
Public bug reported:
we need to to check the value of the configuration item num_retries in
the code in order to ensure the num_retries equal or bigger than 0 ,
done like that the configuration item network_allocate_retries
** Affects: nova
Importance: Undecided
Assignee: zhangtralon
: zhangtralon (zhangchunlong1)
Status: New
** Changed in: nova
Assignee: (unassigned) = zhangtralon (zhangchunlong1)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net
Assignee: zhangtralon (zhangchunlong1)
Status: Confirmed
** Changed in: nova
Assignee: (unassigned) = zhangtralon (zhangchunlong1)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https
Public bug reported:
we need to to check the value of the configuration item
mac_generation_retries in the code in order to ensure the
mac_generation_retries equal or bigger than 0
** Affects: neutron
Importance: Undecided
Assignee: zhangtralon (zhangchunlong1)
Status: New
Public bug reported:
we need to to check the value of the configuration item
metrics_max_retries in the code in order to ensure the
metrics_max_retries equal or bigger than 0
** Affects: neutron
Importance: Undecided
Assignee: zhangtralon (zhangchunlong1)
Status: Invalid
** Changed in: neutron
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1372462
Title:
check the value of the configuration item mac_generation_retries
Public bug reported:
we need to to check the value of the configuration item ESWITCH.retries
in the code in order to ensure the ESWITCH.retries equal or bigger
than 0
** Affects: neutron
Importance: Undecided
Assignee: zhangtralon (zhangchunlong1)
Status: Invalid
** Changed in: neutron
Status: Invalid = New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1372462
Title:
check the value of the configuration item mac_generation_retries
Assignee: zhangtralon (zhangchunlong1)
Status: New
** Changed in: nova
Assignee: (unassigned) = zhangtralon (zhangchunlong1)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https
Assignee: zhangtralon (zhangchunlong1)
Status: New
** Changed in: nova
Assignee: (unassigned) = zhangtralon (zhangchunlong1)
** Summary changed:
- to check the value of the configuration item block_device_allocate_retries
+ check the value of the configuration item
** Changed in: nova
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1355634
Title:
reschedule error after creating an instance from a remote
Public bug reported:
a volume will leave over caused by attaching volume failing when we
create an instance through a boot volume created by an image.
an example to reproduce the problem on latest juno:
(1)root@devstack:/var/log/nova# nova list
** Changed in: nova
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1353874
Title:
a volume will leave over caused by attaching volume
Public bug reported:
here, two scenes may cause that a volume is legacy when we delete
instance whose task_state is block_device_mapping .The first scene is
that using the boot volume created by image creates instance; The other
scene is that using image create instance with a volume
| Name | Size | Volume Type | Bootable | Attached to |
+++--+--+-+--+-+
+++--+--+-+--+-+
** Affects: nova
Importance: Undecided
Assignee: zhangtralon (zhangchunlong1)
Status: New
Public bug reported:
If multiple resources beyond the quotas , the headroom information about the
resources beyond the quotas is incomplete(quota.py).
for example:
If the lens of path and content of the injected files exceed the limits, the
above situation will appear.
2014-06-27
29 matches
Mail list logo
