Open Stack

That depends on your definition of system I guess. Modern deployments of
Openstack are using containers to "containerize" the Openstack functions
outside of the OS itself.

Deprecated options are usually removed between Openstack releases (with
some leeway) so that users can adapt their own configuration files. I don't
think they impact the overall system itself, just the Openstack component
behavior.


On Wed, Jan 20, 2021 at 10:56 AM Bessghaier, Narjes <
narjes.bessghaier.1 at ens.etsmtl.ca> wrote:

> Thank you for your reply
>
> Regarding python files that are deprecating some options. Are these files
> considered to impact the configuration of the system?
>
>
> Thank you
>
> Get Outlook for Android <https://aka.ms/ghei36>
>
> ------------------------------
> *From:* Laurent Dumont <laurentfdumont at gmail.com>
> *Sent:* Wednesday, January 20, 2021 10:34:05 AM
> *To:* Bessghaier, Narjes <narjes.bessghaier.1 at ens.etsmtl.ca>
> *Cc:* openstack-discuss at lists.openstack.org <
> openstack-discuss at lists.openstack.org>; Ouni, Ali <Ali.Ouni at etsmtl.ca>
> *Subject:* Re: Requesting help with OpenStack configuration files
>
> Bonjour fellow Montrealer!
>
> As Thomas mentioned, I dont think there is a fixed standard for config
> files vs code.
>
> That said, most configuration file that are used by Openstack services
> (nova, cinder, glance, neutron) are usually ending in .conf and have the
> following contents.
>
> [section_name_blocks]
> key=value
> #comments
>
> If the file looks like that, it's usually a good indication that it's a
> configuration file and not code.
>
> On Tue, Jan 19, 2021 at 4:39 PM Bessghaier, Narjes <
> narjes.bessghaier.1 at ens.etsmtl.ca> wrote:
>
> Dear OpenStack team,
>
>
> I’m a Ph.D. student in software engineering at the ETS Montreal,
> University of Quebec working on the quality and configuration of
> web-based software systems.
> I’m particularly interested in analyzing configuration files from
> different OpenStack files. One of the main challenges I am currently facing
> is the proper identification of configuration files. I’m mostly confused
> between the python files used for production and the python files used for
> configuration. I am kindly requesting your precious help with the following
> questions:
>
>
>
> 1- How to distinguish between python files used for configuration and
> python files used for production? It will be very helpful if there
> are some configuration-based patterns (eg, textual patterns or expressions)
> that we can find in python files to help us distinguish between source code
> and configuration files?
>
>
>
>
> 2- Certain python files use the oslo_config to access and define
> configuration options. Could "all" these python files be considered as
> configuration files? For example, the following python file of the keystone
> project: keystone/keystone/conf/auth.py, is it considered a source code or
> configuration file?
>
>
>
>
> 3- Why are there different source code and configuration repositories for
> OpenStack projects (eg, nova and puppet-nova)? For instance, does the
> OpenStack-nova service have some configuration files in its repository and
> have the puppet-nova as a separate configuration repository as well?
>
>
>
> Thank you very much in advance for your time and your help!
>
> Kind regards,
> Narjes Bessghaier
>
>
>
>
>
> Narjes Bessghaier
>
> Ph.D student in Software Engineering
>
> École de Technologie Supérieure (ETS)| University of Quebec
>
> Montreal, Canada
>
> narjes.bessghaier.1 at ens.etsmtl.ca <yasmine.makroum.1 at ens.etsmtl.ca>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210120/3903dbe1/attachment.html>