<div dir="ltr">and by the way, this is what I get in overcloud hosts:<div><div style="box-sizing:border-box;font-family:"Segoe UI",system-ui,"Apple Color Emoji","Segoe UI Emoji",sans-serif;font-size:14px"><strong>cat centos7-rt.repo</strong><br>
[centos7-rt]<br>
name=CentOS 7 - Realtime<br>
baseurl=<a href="http://mirror.centos.org/centos/7/rt/x86_64/" rel="noreferrer noopener" target="_blank" title="http://mirror.centos.org/centos/7/rt/x86_64/" tabindex="-1" style="">http://mirror.centos.org/centos/7/rt/x86_64/</a><br>
enabled=1<br>
gpgcheck=0</div></div><div style="box-sizing:border-box;font-family:"Segoe UI",system-ui,"Apple Color Emoji","Segoe UI Emoji",sans-serif;font-size:14px"><br></div><div style="box-sizing:border-box;font-family:"Segoe UI",system-ui,"Apple Color Emoji","Segoe UI Emoji",sans-serif;font-size:14px">even it has a centos8 running ;)</div><div style="box-sizing:border-box;font-family:"Segoe UI",system-ui,"Apple Color Emoji","Segoe UI Emoji",sans-serif;font-size:14px">looks like, some hardcoded yaml file is still inplace :)</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 14 Jul 2020 at 15:45, Alex Schultz <<a href="mailto:aschultz@redhat.com">aschultz@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, Jul 14, 2020 at 7:37 AM Ruslanas Gžibovskis <<a href="mailto:ruslanas@lpic.lt" target="_blank">ruslanas@lpic.lt</a>> wrote:<br>
><br>
> Thank you Alex.<br>
><br>
> I have read around in this mailinglist, that firstboot will be removed. So I was curious, what way forward to have in case it is depricated.<br>
><br>
<br>
For Ussuri it's still available. In future versions we'll be switching<br>
out how we provision nodes which means the firstboot interface likely<br>
will go away and be replaced with something else during provisioning.<br>
However it's still currently valid.<br>
<br>
> For modifying overcloud-full.qcow2 with virt-customise it do not look nice, would be prety to do it on image generation, not sure where tho... maybe writing own module might do the trick, but I find it as dirty workaround :))<br>
<br>
virt-customize is probably the easiest thing to just inject something<br>
unmanaged into the environment. You can technically use an<br>
AllNodesExtraConfig (example THT/environment/enable-swap.yaml &<br>
THT/extraconfig/all_nodes/swap.yaml) to do some custom script at<br>
installation time as well to manage the files. However this uses a<br>
Heat SoftwareConfig which is also deprecated. Though i'm not certain<br>
we have an official replacement for that yet.<br>
<br>
><br>
> yes, for osp modules, i know how to use puppet to provide needed values. I thought this might be for everything.<br>
><br>
> regarding proxy in certain compute, it needs to do dnf update for centos7-rt repo (yes OS is centos8, but repo it has centos-7)... I am confused why, but it does so.<br>
><br>
> On Tue, 14 Jul 2020, 16:23 Alex Schultz, <<a href="mailto:aschultz@redhat.com" target="_blank">aschultz@redhat.com</a>> wrote:<br>
>><br>
>> On Tue, Jul 14, 2020 at 6:32 AM Ruslanas Gžibovskis <<a href="mailto:ruslanas@lpic.lt" target="_blank">ruslanas@lpic.lt</a>> wrote:<br>
>> ><br>
>> > Hi all,<br>
>> ><br>
>> > Borry to keep spamming you all the time.<br>
>> > But could you help me to find a correct place to "modify" image content (packages installed and not installed) and files and services configured in an "adjusted" way so I would have for example:<br>
>><br>
>> These don't necessarily need to be done in the image itself but you<br>
>> can virt customize the image prior to uploading it to the undercloud<br>
>> to inject some things. We provide ways of configuring these things at<br>
>> deployment time.<br>
>><br>
>> > - tuned ssh<br>
>><br>
>> We have sshd configured via a service. Available options are listed in<br>
>> the service file:<br>
>> <a href="https://opendev.org/openstack/tripleo-heat-templates/src/branch/stable/ussuri/deployment/sshd/sshd-baremetal-puppet.yaml" rel="noreferrer" target="_blank">https://opendev.org/openstack/tripleo-heat-templates/src/branch/stable/ussuri/deployment/sshd/sshd-baremetal-puppet.yaml</a><br>
>><br>
>> > - automatically generated root pass to the one I need<br>
>><br>
>> This can be done via a firstboot script.<br>
>> <a href="https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/features/extra_config.html" rel="noreferrer" target="_blank">https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/features/extra_config.html</a><br>
>><br>
>> > - Also added proxy config to /etc/yum.conf to certain computes, and other would be used without proxy (maybe extraconfig option?)<br>
>><br>
>> You'd probably want to do this via a first boot as well. If you are<br>
>> deploying with overcloud images, technically you shouldn't need a<br>
>> proxy on install but you'd likely need one for subsequent updates.<br>
>><br>
>> > - set up kernel parameters, so I would have console output duplicated to serial connection and to iDRAC serial, so I could see login screen over idrac ssh.<br>
>><br>
>> See KernelArgs.<br>
>> <a href="https://opendev.org/openstack/tripleo-heat-templates/src/branch/stable/ussuri/deployment/kernel/kernel-boot-params-baremetal-ansible.yaml#L35" rel="noreferrer" target="_blank">https://opendev.org/openstack/tripleo-heat-templates/src/branch/stable/ussuri/deployment/kernel/kernel-boot-params-baremetal-ansible.yaml#L35</a><br>
>><br>
>> <a href="https://opendev.org/openstack/tripleo-heat-templates/commit/a3e4a9063612a617105e318e422d90706e4ed43e" rel="noreferrer" target="_blank">https://opendev.org/openstack/tripleo-heat-templates/commit/a3e4a9063612a617105e318e422d90706e4ed43e</a><br>
>><br>
>> > - and so on.<br>
>> ><br>
>><br>
>> Your best reference for what is available is likely going to be by<br>
>> looking in the THT/deployment folder for the service configurations.<br>
>> We don't expose everything but we do allow configurability for a<br>
>> significant amount of options. *ExtraConfig can be used to tweak<br>
>> additional options that we don't necessarily expose directly if you<br>
>> know what options need to be set via the appropriate puppet modules.<br>
>> If there are services we don't actually configure, you can define your<br>
>> own custom tripleo service templates and add them to the roles to do<br>
>> whatever you want.<br>
>><br>
>> > I believe many of those things can be done over extraconfig, I just do not know options to modify. maybe you can point me like a blind hen into a correct bowl? :)))<br>
>> ><br>
>> > Thank you in advance.<br>
>> ><br>
>> > --<br>
>> > Ruslanas Gžibovskis<br>
>> > +370 6030 7030<br>
>><br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Ruslanas Gžibovskis<br>+370 6030 7030<br></div></div></div>