[PKG-Openstack-devel] [MoM] Packaging manila

[Malihe Asemani]

Hi All,

On Tue, May 12, 2015 at 2:16 AM, Thomas Goirand <thomas at goirand.fr> wrote:
> Once I did, pkgos-reqsdiff worked perfectly, and showed numerous issues
in the dependencies, like lack of version numbers in some the dependencies.
It also shows the difference when packaging Oslo libraries, with Canonical
using python-oslo-* instead of python-oslo. (ie: dash instead of dot). This
has to be fixed. Note that this is due to upstream OpenStack project doing
lots of funny things with renaming of libraries, namespace fun and so on,

Renaming of which libraries? I did not get how the last sentence is related
to python-oslo.* ! would you please explain it a little bit more?

> so I do understand how Canonical team may have done a mistake here.

Why renaming python-oslo.* to python-oslo-* can be a mistake?

>
>Another thing which shall be done, is providing a correct default
configuration file for Manila. To generate the file, you should look at how
its done in the tox.ini. In there, you'll see:
>
> oslo-config-generator --config-file etc/oslo-config-generator/manila.conf
>
> This translates into:
>
> mkdir -p $(CURDIR)/debian/manila-common/usr/share/manila-common
> oslo-config-generator \
>         --output-file \
>         $(CURDIR)/debian/manila-common/usr/share/manila-common \
>         --namespace manila \
>         --namespace oslo.messaging \
>         --namespace oslo.db \
>         --namespace oslo.db.concurrency \
>         --namespace keystonemiddleware.auth_token
>
> then in debian/manila-common.postinst.in, you should so something like
this:
>
> pkgos_write_new_conf manila manila.conf
>
> Again, have a look into the cinder package to see how we're using
/usr/share/openstack-pkg-tools/pkgos_insert_include pkgos_func
cinder-common.postinst in the debian/rules file, and how the
cinder-common.postinst is done (ie: having a #PKGOS-INCLUDE# which will be
replaced by a set of shell functions from openstack-pkg-tools). You have to
do this way to make sure /etc/manila/manila.conf has the correct unix
rights (ie: owned by the manila user, not world readable...). I'm not sure
if Ubuntu packages care about this or not... I believe they don't.
>

You mean we should create manila.conf manually(using
oslo-config-generator), set its variables using debconf, and correct its
permissions? Is this all of the process that should be done for config
files?

Another question, from where can I find if I need some other directories
like /var/lib/manila/cache (as an example) or not? what about needed config
files like api-paste.ini for manila?

One more question, I don't know any thing about the mentioned namespaces in
oslo-config-generator. Do I need to know about them for next steps? Where
can I find some explanation about these?  hmm... maybe it is necessary for
me to read Developer's Guide of Openstack (to be able to continue this
work). Is it?

Best regards,
Mali

> Cheers,
>
> Thomas Goirand (zigo)
>
>
> _______________________________________________
> Openstack-devel mailing list
> Openstack-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/openstack-devel




--
------------
you can't start the next chapter if you keep re-reading the last one

mali
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/openstack-devel/attachments/20150527/bd68c8c1/attachment.html>