[openstack-dev] [monasca][release] missing build artifacts

Doug Hellmann doug at doughellmann.com
Fri Apr 1 20:36:51 UTC 2016

Excerpts from Hochmuth, Roland M's message of 2016-04-01 20:06:28 +0000:
> Hi Doug, Sorry, this is our first release and we want to do the right thing.
> monasca-ceilometer is the code that plugs into the Ceilometer publisher and Ceilometer storage driver to allow Ceilometer to send metrics to the Monasca API and use Monasca as a storage backend. We don't create a pypi for this component.

How do you users receive that code and install it? We at least need
a tarball built. If you don't want to publish to pypi, you can use
the job definitions that the Python server projects use to build

> monasca-log-api is probably not set up completely, but it should be similar to the monasca-api.
> monasca-thresh remains purely Java code. There is a build, but it isn't a Python build so there isn't a tox.ini. Not sure how to deliver this, but the current java build overwrites the jar each time it builds so it sounds like that would need to be fixed.

Are those JAR files going somewhere we could link to?

> I guess, judging by the issues, I don't quite understand what "deliverables" are. I was thinking it was the tagged code, but obviously it includes the build too. It sounds like we have more work ahead of us.

Most of our distributors want a tarball or sdist or other artifact they
can use to build a package from. For the Python-based apps, we have
templates you can use in the zuul/layout.yaml file to introduce those
jobs into the right zuul queues. The release or infra teams can help you
identify the right template to use.

> Let me know how you want to proceed.

We only want to be linking to things we're actually publishing. The
first patch I mentioned removes the links so the Monasca projects
that don't have builds. The second patch removes the projects
entirely, but if we can update the page to link to a downloadable
artifact (rather than just a git repo tag) then we can keep the
projects in the list. We can get downloadable artifacts by having
you add build jobs and then having the release team tag again as a
new release candidate, or if there are already artifacts somewhere
(like the JAR file) we can set up the releases repo to link there.


> Regards --Roland
> On 4/1/16, 1:21 PM, "Doug Hellmann" <doug at doughellmann.com> wrote:
> >Monasca team,
> >
> >We noticed in our audit of the links on
> >http://releases.openstack.org/mitaka/index.html that the links to
> >the build artifacts for monasca-ceilometer, monasca-log-api, and
> >monasca-thresh point to missing files. These repositories either
> >don't seem to have any real build jobs configured in
> >openstack-infra/project-config/zuul/layout.yaml or don't have tox.ini
> >set up correctly (or both), so it's not clear how tagging is producing
> >a release for you.
> >
> >For now, we are disabling links to the artifacts for those repos
> >via https://review.openstack.org/300457 but we're also planning to
> >remove them from the official Mitaka page since there don't
> >appear to be any actual related deliverables
> >(https://review.openstack.org/300619).
> >
> >It would be good to understand what your intent is for builds. Can
> >you follow up here on this thread with some details?
> >
> >Thanks,
> >Doug
> >
> >__________________________________________________________________________
> >OpenStack Development Mailing List (not for usage questions)
> >Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list