Don75080's profile - activity

grub2-mkconfig -o /etc/grub2.cfg

You have to rebuild the /boot/grub file which the above command will do.

I installed this on a VM at home and it installs just fine. No idea why this would fail on a 32 core server with 64G of ram. This system is behind a proxy.

Old question but the answer is to use the Management network. That is what it is for.

Found it: "glance-manage db_load_metadefs"

That loads the system defaults.

I saw this youtube video showing this https://www.youtube.com/watch?v=zJpHXdBOoeM (OpenStack Metadata Definitions Concept Demo) I can't tell if this is meant to available and if so how? In RHOSP10 Newton, I go the the tab mentioned for Metadata and I don't see any definitions. I'd like to enable them as we are moving to OVS-DPDK and these are going to be very useful in defining new flavors and launching images.

FYI, I am well on my way to installing RHOSP 10 with DPDK and no, they are not correct. I have a bug opened with RHEL to get it corrected.

RH has midified the current templates and the issue is resolved.

Is the above description still correct with Volume Boot from Ceph?

The drawings and templates don't appear to match. For instance, there is no configuration of NIC1 with the IP of the undercloud. Also, the external network is not assigned in the controller. Both seem odd to me.

Found to be a bug in RHOSP 10 that has been fixed. Apply the latest patch

When launching an instance I am getting the below failure:

2017-06-02 11:10:54.922 170109 ERROR nova.scheduler.utils [req-265e3199-80c1-48d7-8ada-70020
7c70c9e 0c9e99986f574210b9b921db2096c5f3 0beb5494e3924930b35f806c95afbb15 - - -] [instance:
c8245c24-bd98-4e27-8d52-f7e3858fdcb7] Error from last host: overcloud-compute-4.localdomain
(node overcloud-compute-4.localdomain): [u'Traceback (most recent call last):\n', u'  File "
/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1779, in _do_build_and_run_i
nstance\n    filter_properties)\n', u'  File "/usr/lib/python2.7/site-packages/nova/compute/
manager.py", line 1976, in _build_and_run_instance\n    instance_uuid=instance.uuid, reason=
six.text_type(e))\n', u"RescheduledException: Build of instance c8245c24-bd98-4e27-8d52-f7e3
858fdcb7 was re-scheduled: internal error: qemu unexpectedly closed the monitor: warning: ho
st doesn't support requested feature: CPUID.01H:EDX.ds [bit 21]\nwarning: host doesn't suppo
rt requested feature: CPUID.01H:EDX.acpi [bit 22]\nwarning: host doesn't support requested f
eature: CPUID.01H:EDX.ht [bit 28]\nwarning: host doesn't support requested feature: CPUID.01
H:EDX.tm [bit 29]\nwarning: host doesn't support requested feature: CPUID.01H:EDX.pbe [bit 3
1]\nwarning: host doesn't support requested feature: CPUID.01H:ECX.dtes64 [bit 2]\nwarning:
host doesn't support requested feature: CPUID.01H:ECX.monitor [bit 3]\nwarning: host doesn't
support requested feature: CPUID.01H:ECX.ds_cpl [bit 4]\nwarning: host doesn't support requ
ested feature: CPUID.01H:ECX.vmx [bit 5]\nwarning: host doesn't support requested feature: C
PUID.01H:ECX.smx [bit 6]\nwarning: host doesn't support requested feature: CPUID.01H:ECX.est
[bit 7]\nwarning: host doesn't support requested feature: CPUID.01H:ECX.tm2 [bit 8]\nwarnin
g: host doesn't support requested feature: CPUID.01H:ECX.xtpr [bi\n"]

Has anyone had experience with this. This is a DPDK system with multiple kernel command line options used.

So you are saying I only need to call out the additional filters I need?

That sounds like an issue with your profiles. Is this Mitaka or Newton? If Newton, try openstack profile list and make sure they are in the correct order.

Question stated in Title

In Nova.conf on the controller, I am specifically setting the default filters as follows:

scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,CoreFilter,NUMATopologyFilter,AggregateInstanceExtraSpecsFilter

However, on all my other Newton installs, I have not needed "NumaTopology". So, I don't set any config and things like Aggregate and Affinity Filters are there. In the docs, it seems to always say the scheduler default filters config line needs to always be there. What is the correct way to do this?