<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Microsoft YaHei";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"\@Microsoft YaHei";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoPlainText>Hi, Alonso:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I'm not sure that the configuration had been changed. You can check the nova compute's log (you need enable debug mode), search 'cpu_models', you'll see a record similar as below(the record should printed when service start):<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><i>" 2019-11-08 18:21:58.966 6 DEBUG oslo_service.service [req-16a54cb4-1d45-4119-9fd4-6d84f471ebb0 - - - - -] libvirt.cpu_models = <b>[SandyBridge,IvyBridge,Haswell,Broadwell]</b> log_opt_values /var/lib/kolla/venv/lib/python2.7/site-packages/oslo_config/cfg.py:2585"<o:p></o:p></i></p><p class=MsoPlainText><i><o:p> </o:p></i></p><p class=MsoPlainText>Please check the list, if it’s same as you set, then the configuration changed success.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Best Regards<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>On 2019/11/7, 4:19 AM, "Alonso, Juan Carlos" <starlingx-discuss-bounces+wang.ya=99cloud.net@lists.starlingx.io on behalf of juan.carlos.alonso@intel.com> wrote:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText> Hello Ya,<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> I have an standard configuration local storage (2+2) baremetal environment, I can access to nova-compute service for both computes but I did not found a list of 'cpu_models', just found 'cpu_mode' and it is not set as 'custom' as documentation says:<o:p></o:p></p><p class=MsoPlainText> [libvirt]<o:p></o:p></p><p class=MsoPlainText> cpu_mode = host-model<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> So, I executed:<o:p></o:p></p><p class=MsoPlainText> $ system helm-override-update --set livbirt.cpu_mode=custom stx-openstack nova openstack<o:p></o:p></p><p class=MsoPlainText> $ system helm-override-update --set cpu_models=SandyBridge,IvyBridge,Haswell,Broadwell stx-openstack nova openstack<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> I check again /etc/nova/nova.conf inside pod, and still saw just 'cpu_mode = host-model'<o:p></o:p></p><p class=MsoPlainText> Is this configuration be modified? If yes, how can I do it?<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> Also I could create flavors and instances with below configurations:<o:p></o:p></p><p class=MsoPlainText> trait:HW_CPU_X86_AVX='required'<o:p></o:p></p><p class=MsoPlainText> trait:HW_CPU_X86_AVX2='required'<o:p></o:p></p><p class=MsoPlainText> trait:HW_CPU_X86_AVX512F='required'<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> One instance for each configuration and one instance with those three configuration in a same flavor.<o:p></o:p></p><p class=MsoPlainText> But, how can I check the CPU model in the instance?<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> In the test cases I mention at the beginning of this threat it says that the instances with flavor property trait:HW_CPU_X86_AVX512F='required' should get ERROR, but it could be launched as ACTIVE.<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> Regards.<o:p></o:p></p><p class=MsoPlainText> Juan Carlos Alonso<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> -----Original Message-----<o:p></o:p></p><p class=MsoPlainText> From: wang.ya <wang.ya@99cloud.net> <o:p></o:p></p><p class=MsoPlainText> Sent: Monday, November 4, 2019 9:01 PM<o:p></o:p></p><p class=MsoPlainText> To: Hu, Yong <yong.hu@intel.com>; Jones, Bruce E <bruce.e.jones@intel.com>; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Troyer, Dean <dean.troyer@intel.com><o:p></o:p></p><p class=MsoPlainText> Cc: Cabrales, Ada <ada.cabrales@intel.com><o:p></o:p></p><p class=MsoPlainText> Subject: Re: Patch Elimination Train version<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> Hi, yong:<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> *vCPU Models selection* feature has been completed in train release.<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> The feature's workflow is as follow:<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> 1. Configure the *cpu_models* option under [libvirt] module of nova-compute service.<o:p></o:p></p><p class=MsoPlainText> The *cpu_models* option is an ordered list of CPU models. It's sorted by CPU flags, from less to more. For example:<o:p></o:p></p><p class=MsoPlainText> kvm64, IvyBridge, Haswell<o:p></o:p></p><p class=MsoPlainText> In above example, kvm64 only has base flags, IvyBridge has flag *avx*, Haswell have both *avx* and *avx2*.<o:p></o:p></p><p class=MsoPlainText> Please note that the configured CPU models must compatible with compute node's host CPU.<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> 2. Create/Set flavor with required traits. The nova compute will select the CPU model from [libvirt]/cpu_models which first meet the flavor's requested flags. For example:<o:p></o:p></p><p class=MsoPlainText> openstack flavor set 1 --property trait:HW_CPU_X86_AVX=required<o:p></o:p></p><p class=MsoPlainText> In above example, we mark the flavor request flag *avx*, if the CPU of compute node has flag *avx*, then the instance can be scheduled success and created with CPU model IvyBridge, otherwise the API call will get an error: "No valid host". <o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> Spec: http://specs.openstack.org/openstack/nova-specs/specs/train/approved/cpu-model-selection.html<o:p></o:p></p><p class=MsoPlainText> Code: https://review.opendev.org/#/q/status:merged+project:openstack/nova+branch:master+topic:bp/cpu-model-selection<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> Hope the above info can help you. Also, I'll online in today's meeting :)<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> Best Regards<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> On 2019/11/5, 9:13 AM, "Yong Hu" <yong.hu@intel.com> wrote:<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> + Wang Ya.<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> Hi Ya,<o:p></o:p></p><p class=MsoPlainText> I remember your team has been upstreaming the related patches.<o:p></o:p></p><p class=MsoPlainText> Could you share some info with us here or in the meeting tonight?<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> regards,<o:p></o:p></p><p class=MsoPlainText> Yong<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> On 2019/11/5 6:37 AM, Jones, Bruce E wrote:<o:p></o:p></p><p class=MsoPlainText> > + Dean and Yong (the new PL for the OpenStack team)<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > AFAIK the CPU model changes that went into Train are internal only and <o:p></o:p></p><p class=MsoPlainText> > don’t impact OpenStack operation.<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > Suggest you bring all of this to the distro.openstack meeting tomorrow <o:p></o:p></p><p class=MsoPlainText> > where it can be discussed with the right people.<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > brucej<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > *From:* Alonso, Juan Carlos<o:p></o:p></p><p class=MsoPlainText> > *Sent:* Monday, November 4, 2019 2:30 PM<o:p></o:p></p><p class=MsoPlainText> > *To:* Jones, Bruce E <bruce.e.jones@intel.com><o:p></o:p></p><p class=MsoPlainText> > *Cc:* Cabrales, Ada <ada.cabrales@intel.com><o:p></o:p></p><p class=MsoPlainText> > *Subject:* Patch Elimination Train version<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > Hi Bruce,<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > In last test plan for Patch Elimination Stein version, there was some <o:p></o:p></p><p class=MsoPlainText> > *vCPU Model (Nova)* feature test cases that was marked as Unlikely status:<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > 1. Create a flavor without any extra specs. Launch instance using this <o:p></o:p></p><p class=MsoPlainText> > flavor. Check instance cpu_model is 'kvm64'<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > 2. Create a flavor with extra specs: 'trait:HW_CPU_X86_AVX2=required'. <o:p></o:p></p><p class=MsoPlainText> > Launch instance using this flavor. Check instance is Haswell and is in <o:p></o:p></p><p class=MsoPlainText> > compute node 2.<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > 3. Create a flavor with extra specs: <o:p></o:p></p><p class=MsoPlainText> > 'trait:HW_CPU_X86_AVX512F=required'. Launch instance using this flavor. <o:p></o:p></p><p class=MsoPlainText> > Check API call get an error because no compute node has property 'avx512F'.<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > 4. Create a flavor with multiple extra specs: 'trait:xxx'. Launch <o:p></o:p></p><p class=MsoPlainText> > instance using this flavor.<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > 5. Create a flavor and ignoring cpu_model. Launch instance using this <o:p></o:p></p><p class=MsoPlainText> > flavor.<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > For Train version, is such *vCPU Model (Nova)* feature still out?<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > Also, there was some Live Migration Bugs table related to Neutron:<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > Enable delete bound trunk for linux bridge agent<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > 0040-rpc-removing-timeout-backoff-multiplier.patch (2e4ca00)<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > 0062-dvr-force-admin-state-update-before-distri.patch (edf9731)<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > 0065-dvr-do-not-create-agent-gateway-ports-unle.patch (2857911)<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > 0077-api-reject-routes-with-invalid-network-val.patch (6ed8fe6)<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > 0014-add-support-for-querying-quotas-with-usage.patch (71c07d7)<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > Prevent DHCP from processing stale RPC messages<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > 0039-dhcp-handle-concurrent-port-creation-error.patch (a38f89)<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > 0047-wsgi-prevent-accepting-socket-without-a-gr.patch (8e72491)<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > I need to know if such features/tests are going to be testes or not, can <o:p></o:p></p><p class=MsoPlainText> > you help me to verify?<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > Test Plan for Stein: <o:p></o:p></p><p class=MsoPlainText> > https://docs.google.com/spreadsheets/d/1jsTyzy1HT7VR4EUsbBRaTYvs0BlXeGWkhLD0pJmFChc/edit#gid=1511025137<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > Test Plan for Train: <o:p></o:p></p><p class=MsoPlainText> > https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit?pli=1#gid=184151983<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > Regards.<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > Juan Carlos Alonso<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> _______________________________________________<o:p></o:p></p><p class=MsoPlainText> Starlingx-discuss mailing list<o:p></o:p></p><p class=MsoPlainText> Starlingx-discuss@lists.starlingx.io<o:p></o:p></p><p class=MsoPlainText> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p></div></body></html>