Open Stack

and by the way, this is what I get in overcloud hosts:
*cat centos7-rt.repo*
[centos7-rt]
name=CentOS 7 - Realtime
baseurl=http://mirror.centos.org/centos/7/rt/x86_64/
enabled=1
gpgcheck=0

even it has a centos8 running ;)
looks like, some hardcoded yaml file is still inplace :)

On Tue, 14 Jul 2020 at 15:45, Alex Schultz <aschultz at redhat.com> wrote:

> On Tue, Jul 14, 2020 at 7:37 AM Ruslanas Gžibovskis <ruslanas at lpic.lt>
> wrote:
> >
> > Thank you Alex.
> >
> > 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.
> >
>
> For Ussuri it's still available. In future versions we'll be switching
> out how we provision nodes which means the firstboot interface likely
> will go away and be replaced with something else during provisioning.
> However it's still currently valid.
>
> > 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 :))
>
> virt-customize is probably the easiest thing to just inject something
> unmanaged into the environment.  You can technically use an
> AllNodesExtraConfig (example THT/environment/enable-swap.yaml &
> THT/extraconfig/all_nodes/swap.yaml) to do some custom script at
> installation time as well to manage the files. However this uses a
> Heat SoftwareConfig which is also deprecated. Though i'm not certain
> we have an official replacement for that yet.
>
> >
> > yes, for osp modules, i know how to use puppet to provide needed values.
> I thought this might be for everything.
> >
> > 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.
> >
> > On Tue, 14 Jul 2020, 16:23 Alex Schultz, <aschultz at redhat.com> wrote:
> >>
> >> On Tue, Jul 14, 2020 at 6:32 AM Ruslanas Gžibovskis <ruslanas at lpic.lt>
> wrote:
> >> >
> >> > Hi all,
> >> >
> >> > Borry to keep spamming you all the time.
> >> > 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:
> >>
> >> These don't necessarily need to be done in the image itself but you
> >> can virt customize the image prior to uploading it to the undercloud
> >> to inject some things. We provide ways of configuring these things at
> >> deployment time.
> >>
> >> >  - tuned ssh
> >>
> >> We have sshd configured via a service. Available options are listed in
> >> the service file:
> >>
> https://opendev.org/openstack/tripleo-heat-templates/src/branch/stable/ussuri/deployment/sshd/sshd-baremetal-puppet.yaml
> >>
> >> >  - automatically generated root pass to the one I need
> >>
> >> This can be done via a firstboot script.
> >>
> https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/features/extra_config.html
> >>
> >> >  - Also added proxy config to /etc/yum.conf to certain computes, and
> other would be used without proxy (maybe extraconfig option?)
> >>
> >> You'd probably want to do this via a first boot as well. If you are
> >> deploying with overcloud images, technically you shouldn't need a
> >> proxy on install but you'd likely need one for subsequent updates.
> >>
> >> >  - 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.
> >>
> >> See KernelArgs.
> >>
> https://opendev.org/openstack/tripleo-heat-templates/src/branch/stable/ussuri/deployment/kernel/kernel-boot-params-baremetal-ansible.yaml#L35
> >>
> >>
> https://opendev.org/openstack/tripleo-heat-templates/commit/a3e4a9063612a617105e318e422d90706e4ed43e
> >>
> >> >  - and so on.
> >> >
> >>
> >> Your best reference for what is available is likely going to be by
> >> looking in the THT/deployment folder for the service configurations.
> >> We don't expose everything but we do allow configurability for a
> >> significant amount of options.  *ExtraConfig can be used to tweak
> >> additional options that we don't necessarily expose directly if you
> >> know what options need to be set via the appropriate puppet modules.
> >> If there are services we don't actually configure, you can define your
> >> own custom tripleo service templates and add them to the roles to do
> >> whatever you want.
> >>
> >> > 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? :)))
> >> >
> >> > Thank you in advance.
> >> >
> >> > --
> >> > Ruslanas Gžibovskis
> >> > +370 6030 7030
> >>
>
>

-- 
Ruslanas Gžibovskis
+370 6030 7030
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200714/d7ade340/attachment.html>