Open Stack

On Wed, Oct 14, 2015 at 3:14 PM, Haïkel <hguemar at fedoraproject.org> wrote:

> 2015-10-14 21:59 GMT+02:00 Anne Gentle <annegentle at justwriteclick.com>:
> >
> >
> > On Wed, Oct 14, 2015 at 7:53 AM, Haïkel <hguemar at fedoraproject.org>
> wrote:
> >>
> >> Hi,
> >>
> >> I just registered to this list as someone just raised this topic to my
> >> attention. As one of the people maintaining RDO, I will answer some of
> >> the points raised.
> >> I'm not here to rant, but I get the feeling that you got frustrated by
> >> a bad experience with RDO so let's get on a better footing.
> >>
> >> > The Delorean repo is a pretty hilarious combination of old, out of
> date
> >> > config files, and a few Mitaka packages thrown in for good measure
> >>
> >> Delorean is a continuous delivery platform, and there are multiples
> >> topics mixed up here:
> >> * old, out of date config files => RDO strategy is to rely on external
> >> installer (packstack or RDO Manager) to deploy and configure services.
> >> So yes, some out-of-date config files could be undetected, we try to
> >> fix them but AFAIK no tickets were opened.
> >> * packages are automatically built for every commit, so when Liberty
> >> was branched, there was a delay between we fixed delorean
> >> configuration to track the stable/liberty branch rather than master.
> >> Some Mitaka commits were built as packages, but it was fixed rather
> >> quickly.
> >>
> >>
> >> > The Red Hat packages, on the other hand, are missing quite a few
> crucial
> >> > deps, including the PyMySQL deps.
> >>
> >> https://admin.fedoraproject.org/pkgdb/package/python-PyMySQL/
> >> Note this topic was raised in RDO list few weeks ago while we fixed
> >> this with Fedora/RHEL python MySQL package maintainers months ahead of
> >> this discussion.
> >> And RDO repositories should have all the dependencies available, but
> >> yes, if you use Fedora repositories it could be out-of-sync as we're
> >> dependent from the Fedora Reviewing process.
> >>
> >> Yes, our process review can be quite long and I do most of the reviews
> >> here, but it's got better since I added a tracker to track all reviews
> >> blocking RDO (only non-critical reviews are remaining)
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1243533
> >>
> >> > Right now, the Fedora testing situation is slightly better than the
> Red
> >> > Hat/CentOS one, thanks to Delorean being in slightly better shape, and
> >> > thanks to Brian Moss's dogged determination in getting it working.
> >>
> >> Ironically, nope, RDO is better supported on CentOS as we have
> >> slightly more control on our workflow there. And I'm not aware of
> >> Brian Moss efforts, so it's likely not to be fixed in RDO.
> >>
> >>
> >> What bothers me is that some of these issues were never reported to
> >> us, so please open tickets or at least shout an angry mail at me :)
> >> Feel free to ping me in the future for RDO related topics, I'm
> >> number80 on freenode, I hang around #rdo, #openstack-stable and
> >> #openstack-rpm-packaging.
> >
> >
> > Thanks for this info Haïkel. From my view point which is admittedly a bit
> > removed this release, I wonder if it's not so much the packaging itself
> > that's a concern, but people to test and document the packages? Is there
> an
> > RDO community test and writing person who could come in earlier in the
> > release and work with our install guide team?
> >
>
> I'm fine with not publishing untested documentation, which is
> different than "RDO packaging does not work".
> Now, that I know that we have issues with the way documentation team
> install OpenStack with RDO packages,  I'll personally make sure that
> we test and fix all the issues encountered.
> If we could automate somehow all the steps, we could leverage delorean
> so that issues are fixed as soon as upstream projects change.
>
> We do not have a dedicated writer for RDO, but we'll manage somehow.
>
>
Yes, this is pretty obvious by now, but rather than "manage somehow" let's
make an even stronger request. Let's find a way to have a sponsor hire
someone for that position. We've seen this pattern in Debian as well and
it's unfair for the packagers to take on both roles. Mirantis came forward
with a writer, let's find someone in the RDO community. All suggestions
welcome!

Thanks,
Anne


>
> > Sounds like we need earlier coordination, so if you're our contact person
> > that's fine, but might be nice to get you or another liaison integrated
> > sooner.
> >
> > That said, let's find the right wording on the docs site for the people
> who
> > will be asking "what about RDO" starting tomorrow.
> >
> > Anne
> >
>
> Yes, goal is to collaborate more nicely in the futurenot to bicker :)
> As previously stated, I will join the cross-project documentation session.
>
> Regards,
> H.
>
> >>
> >>
> >> Regards,
> >> H.
> >>
> >> _______________________________________________
> >> OpenStack-docs mailing list
> >> OpenStack-docs at lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> >
> >
> >
> >
> > --
> > Anne Gentle
> > Rackspace
> > Principal Engineer
> > www.justwriteclick.com
>
> _______________________________________________
> OpenStack-docs mailing list
> OpenStack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>



-- 
Anne Gentle
Rackspace
Principal Engineer
www.justwriteclick.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20151014/3f65aa65/attachment.html>