Open Stack

> -----Original Message-----
> From: Saravanan KR [mailto:skramaja at redhat.com]
> Sent: Tuesday, October 3, 2017 1:36 PM
> To: OpenStack Development Mailing List (not for usage questions)
> <openstack-dev at lists.openstack.org>
> Subject: Re: [openstack-dev] [TripleO] Configure SR-IOV VFs in tripleo
> 
> On Tue, Sep 26, 2017 at 3:37 PM, Moshe Levi <moshele at mellanox.com>
> wrote:
> > Hi  all,
> >
> >
> >
> > While working on tripleo-ovs-hw-offload work, I encounter the
> > following issue with SR-IVO.
> >
> >
> >
> > I added -e ~/heat-templates/environments/neutron-sriov.yaml -e
> > ~/heat-templates/environments/host-config-and-reboot.yaml to the
> > overcloud-deploy.sh.
> >
> > The computes nodes are configure with the intel_iommu=on kernel option
> > and the computes are reboot as expected,
> >
> > than the tripleo::host::sriov will create /etc/sysconfig/allocate_vfs
> > to configure the SR-IOV VF. It seem it requires additional reboot for
> > the SR-IOV VFs to be created. Is that expected behavior? Am I doing
> > something wrong?
> 
> The file allocate_vfs is required for the subsequent reboots, but during the
> deployment, the vfs are created by puppet-tripleo [1]. No additional reboot
> required for creating VFs.
Yes, I am not sure what went wrong in my first attempt, but know it is working as expected.
 
> 
> Regards,
> Saravanan KR
> 
> [1]
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit
> hub.com%2Fopenstack%2Fpuppet-
> tripleo%2Fblob%2Fmaster%2Fmanifests%2Fhost%2Fsriov.pp%23L19&data=0
> 2%7C01%7Cmoshele%40mellanox.com%7C92c6146ab3e5460df36808d50a4aa
> 2db%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C63642623803127
> 6659&sdata=zSCKOPHBHyiZXmSs4CLVMxWsZ3KCkp3JGhYZuPZRpY8%3D&res
> erved=0
> 
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > [1]
> >
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit
> > hub.com%2Fopenstack%2Fpuppet-
> tripleo%2Fblob%2F80e646ff779a0f8e201daec0
> >
> c927809224ed5fdb%2Fmanifests%2Fhost%2Fsriov.pp&data=02%7C01%7Cmo
> shele%
> >
> 40mellanox.com%7C92c6146ab3e5460df36808d50a4aa2db%7Ca652971c7d2e
> 4d9ba6
> >
> a4d149256f461b%7C0%7C0%7C636426238031276659&sdata=OBk9S2mnCNoG
> eygYwviv
> > DCDOo4vtG2vAIpHG7yRmpC4%3D&reserved=0
> >
> >
> >
> __________________________________________________________
> ____________
> > ____ OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> >
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flist
> > s.openstack.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fopenstack-
> dev&data=02
> >
> %7C01%7Cmoshele%40mellanox.com%7C92c6146ab3e5460df36808d50a4aa2
> db%7Ca6
> >
> 52971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636426238031276659&sdat
> a=x%2F
> > 0%2F2nDx79tfpFCHyDRFdekO0gCStBbuvviUzVZ9An0%3D&reserved=0
> >
> 
> __________________________________________________________
> ________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-
> request at lists.openstack.org?subject:unsubscribe
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.
> openstack.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fopenstack-
> dev&data=02%7C01%7Cmoshele%40mellanox.com%7C92c6146ab3e5460df3
> 6808d50a4aa2db%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636
> 426238031276659&sdata=x%2F0%2F2nDx79tfpFCHyDRFdekO0gCStBbuvviUz
> VZ9An0%3D&reserved=0