<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">> From: </span>
</b><span style="font-size:12.0pt;color:black">James Page <james.page@ubuntu.com><br>
<br>
</span><o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">> 1) +1 for a consistent approach across projects - /usr/share/<module> sounds like a sensible location - avoiding any complexity with managing changes made by users in /etc/<project> for deploy from source use-cases, and allowing packagers
to know where to expect reference/sample config files to appear during the package build-out/install process.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We have agreement from packagers for Ubuntu [1] and RDO [2] to include the files in the relative path /share. This seems to be the least offensive. OpenStack-Ansible supports the inclusion of the files, regardless of path [3].<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There was acceptance of the /etc relative path from a SuSE packager [4]. Thomas Bechtold – could you comment on whether the relative path of /share is also good for SuSE packaging?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There has been an objection from the OpenStack package maintainer for Debian, but that objection has been to the use of the relative path of /etc. Thomas Goirand, could you please indicate whether you support the use of the relative path
of /share given the currently available functionality in setuptools and pbr?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">> 2) Looking at the Ubuntu packaging for OpenStack projects, we have quite a few places where oslo-config-generator or oslo-policy-generator is used to generate sample configuration files as part of the package build; I might have missed
it in my read through of this thread but it would be awesome if those could be integrated as part of this process as well as the originating project would then be able to provide some level for assurance to the content of generated files in downstream distributions.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As mentioned in [4] these should be auto-generated. Some projects do this and submit samples into the repo from time to time, others have just left a stub with an explanation of how to generate it.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">> I'd also be +1 on a packaging SIG; I don't think it will ever be a high overhead SIG but it sounds like there are common challenges for deployment projects and distributors which would benefit from shared focus.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’m not in a position to set this up or run it, but would be happy to participate if someone is able to take ownership of it.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">[1] <a href="http://lists.openstack.org/pipermail/openstack-dev/2017-October/123235.html">
http://lists.openstack.org/pipermail/openstack-dev/2017-October/123235.html</a><o:p></o:p></p>
<p class="MsoNormal">[2] <a href="http://lists.openstack.org/pipermail/openstack-dev/2017-October/123294.html">
http://lists.openstack.org/pipermail/openstack-dev/2017-October/123294.html</a><o:p></o:p></p>
<p class="MsoNormal">[3] <a href="http://lists.openstack.org/pipermail/openstack-dev/2017-October/123035.html">
http://lists.openstack.org/pipermail/openstack-dev/2017-October/123035.html</a><o:p></o:p></p>
<p class="MsoNormal">[4] <a href="http://lists.openstack.org/pipermail/openstack-dev/2017-September/122843.html">
http://lists.openstack.org/pipermail/openstack-dev/2017-September/122843.html</a><o:p></o:p></p>
<p class="MsoNormal">[5] <a href="http://lists.openstack.org/pipermail/openstack-dev/2017-September/122825.html">
http://lists.openstack.org/pipermail/openstack-dev/2017-September/122825.html</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
<hr>
Rackspace Limited is a company registered in England & Wales (company registered number 03897010) whose registered office is at 5 Millington Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be viewed at www.rackspace.co.uk/legal/privacy-policy
- This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately
by e-mail at abuse@rackspace.com and delete the original message. Your cooperation is appreciated.
</body>
</html>