On Wed, Aug 23, 2017 at 4:28 AM, Oliver Walsh <owa...@redhat.com> wrote: > Hi, > >> sed -i 's/Group=qemu/Group=42427/' >> /usr/lib/systemd/system/ovs-vswitchd.service > > Can't this be overridden via /etc/systemd/system/ovs-vswitchd.service? > Yes. I just provided the changes done on a existing deployment to make it work. I will incorporate it to templates.
>> This change basically runs ovs with group id of kolla's qemu user >> (42427). For the solution, my opinion is that we don't require host's >> qemu (107) user in a containerized deployment. I am planning to ensure >> that kolla's user id (42427) is updated to the host via the host prep >> tasks. Let me know if there is any other aspects to be considered. >> > > Might be worth considering overriding the qemu uid/gid to 107 in the > kolla config file instead. Definitely it will be good for upgrade to keep the same uid/gid so that existing DPDK based VMs continue to work after upgrade. But any other specific reasons for sticking with same qemu uid/gid in kolla containers? Do you foresee any particular cases related to it? Regards, Saravanan KR > > Regards, > Ollie > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
