anvil-dev team mailing list archive

[Joshua Harlow <harlowja@xxxxxxxxxxxxx>]

Anvil does have a mailing list.

https://launchpad.net/~anvil-dev

- anvil-dev@xxxxxxxxxxxxxxxxxxx


As for the ubuntu support question can u go into more detail on the
following (as they confuse me).

- fixing unit tests (or to disable them) for unstable builds (is this
openstack tests? or anvil tests?)
 - we have a way to disable openstack tests via the anvil yaml config
(http://bit.ly/1f8UIvu)
- version conventions, this is ok, the version knowledge in anvil is split
into 2 classes, one that does the pip work (http://bit.ly/1dOIBA6) and one
that does the rpm/yum work (http://bit.ly/1byW106), I think there can just
be one that does apt/deb work instead (probably using the same
(http://bit.ly/1dOIBA6) base class module (or slightly adjusted if needed).
- patching DEB but not RPM (no idea here, never done patching with DEB) -
why is this hard?
- APT repo maintenance (can u describe more here?)
- Package signing (whats hard about this?)

As for koji and git-buildpackage and open build system, can u describe
more about those and what mirantis has done and how they work and what
exactly is achieved by those, do those just build DEBs for u, does it
build RPMs? Or is it just a repository for packages (or something else).
As far as jenkins integration I have always wanted
https://blueprints.launchpad.net/anvil/+spec/enable-ci-for-anvil but it
has never gotten the attention that it deserves (sadly). Are u talking
about a different jenkins though?

I'd be more than up for continued ubuntu support, infact along time ago,
anvil had support for both (RHEL and ubuntu), but the support for the
ubuntu side of the family was lacking and I felt that it wasn't getting
the attention it deserved (and removed it). This was before anvil started
building packages (and was more similar to devstack and fuel in that it
used pip directly and such).

-Josh

On 11/17/13 11:50 PM, "Matthew Mosesohn" <mmosesohn@xxxxxxxxxxxx> wrote:

>Hi Josh, Ivan,
>
>I admit we'll have a lot of difficulty having real-time discussion,
>due to the fact that I'm located in Moscow, Russia. Does Anvil have a
>mailing list? Feel free to start a thread by forwarding this message
>to your list.
>
>I feel it would be worthwhile to mention the biggest obstacles to
>Ubuntu support. At a glance they include:
>* fixing unit tests (or to disable them) for unstable builds
>* Version conventions (debs can't have -, rpms can't have _,
>python-setuptools can't have ~)
>* patching DEB but not RPM (and vice versa)
>* APT repo maintenance is far more difficult than Yum
>* Package signing (you may not care so much, but others do) is totally
>different in deb and for the apt repo itself
>
>At Mirantis, we've overcome parts of this challenge by moving away
>from separately building in Koji (from Fedora Project) and
>git-buildpackage to Open Build System (from SUSE). Unfortunately, I
>didn't contribute to the OBS implementation, but I have colleagues who
>could talk more to that effort if it was interesting enough. I can
>share with you some of our DEB scripts to show some approaches to
>packaging for Ubuntu.
>
>The main keys to being successful include continuous integration (via
>Jenkins), rebasing from official Ubuntu and RDO packages as often as
>possible, and testing by hand from Gerrit change requests.
>
>We don't currently have live builds because tiny errors break
>deployments. We only make stable releases, but making the leap to live
>builds from current tip is where we want to go. I believe our projects
>are similar enough that we can try to help kickstart Ubuntu support.
>
>Best Regards,
>Matthew Mosesohn
>Mirantis