On 23 August 2017 at 07:18, Saravanan KR wrote:
> On Wed, Aug 23, 2017 at 4:28 AM, Oliver Walsh wrote:
>> Hi,
>>
>>> sed -i 's/Group=qemu/Group=42427/'
>>> /usr/lib/systemd/system/ovs-vswitchd.service
>>
>> Can't this be overridden vi
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?
> 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 ho
nic_python_agent/extensions/image.py#L136
>
>
> On Tue, Dec 13, 2016 at 4:18 PM, Oliver Walsh wrote:
>> Hi Yolanda,
>>
>>> these changes will be created by ironic before the image is deployed
>>
>> The question I'm asking is how are the changed created
ght parameters. The
> alternative of doing with puppet after the image was deployed, needed a
> reboot, because the changes were done post-deploy.
> So ironic build steps are pre-deploy without reboot, puppet changes are
> post-deploy with a reboot.
>
> On Tue, Dec 13, 2016 at 11
Hi,
Saravanan wrote:
> If ironic "deploy steps" can configure this "tuned" setting and run the
> command
How does this avoid the reboot?
Yolanda wrote:
> The idea will be to define custom deployment steps for ironic, like including
> the kernel boot parameters.
Again, is this avoiding the reb
Hi Yolanda,
I've the same requirements for a real-time compute role.
I'm current using #4. Puppet sets the kernel cmdline in
/etc/defaults/grub, then touches a file that triggers a reboot in an
os-refresh-config post-configure script.
How much of an issue is the reboot? In my dev env it doesn't
Hi,
I'd like to post a link to a blueprint/spec that I'm hoping to discuss
at the upcoming summit.
https://blueprints.launchpad.net/tripleo/+spec/tripleo-realtime
https://review.openstack.org/388162
I'm new to both TripleO and OpenStack development. Any
advice/hints/criticism is very much apprec
