2015-06-10 4:11 GMT+02:00 Graeme Gillies <ggillies(a)redhat.com&gt;: > Hi, > > I'm currently responsible for building and maintaining the Operational > Toolchain for RHEL-OSP and RDO (which is Optional at deploy time) which > includes the following areas > > * Centralised Logging > * Performance Monitoring > * Availability Monitoring > > At the moment this consists of around 140 packages for the following tools > > collectd > graphite > grafana > sensu > uchiwa > elasticsearch > fluentd > kibana > > I wanted to open a discussion about what's the best way for me to get > these built and part of the RDO ecosystem (assuming it makes sense to do > so). This list may grow as we and the community look to expand the tools > that form part of that ecosystem (e.g. influxdb for better metrics > storage, or ansible for writing ad-hoc maintenance tasks). > > I know that RDO itself is now being built in cbs.centos.org, and > RDO-Manager is built by delorean. How do people feel it would be best > for me to move these tools into RDO (even if it's a seperate repo, like > RDO-Manager currently is). Should I look to build through a new set of > tags in cbs.centos.org? Or use delorean? Or something else? > Could we have a list? Then we could check their status and see how we could get them all. Basically, they must be reviewed and imported on fedora dist-git (except few cases) and then we will rebuild them in CBS for RDO/EL7 (by apevec or me)

I assume that these tools are not tied to a specific version of openstack so we should leverage the cloud7-openstack-common-xxx tags. doc: https://openstack.redhat.com/packaging/rdo-packaging.html#rdo-pkg-guide Drop by the RDO packaging meeting or if you can't make it, update the agenda and/or contact apevec or me. I suspect that you can't attend as you're in Australia. Reviews should be announced on this list to raise attention, even informal reviews help making the process faster. Thanks for spear-heading this effort :)

H. > Any suggestions or advice would be very much appreciated. > > Regards, > > Graeme > > -- > Graeme Gillies > Principal Systems Administrator > Openstack Infrastructure > Red Hat Australia > > _______________________________________________ > Rdo-list mailing list > Rdo-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe(a)redhat.com

2015-06-11 2:11 GMT+02:00 Graeme Gillies <ggillies(a)redhat.com&gt;: > > Sure the list (with the exception of elasticsearch) is at > > http://paste.fedoraproject.org/230935/98121514/ > Thanks > I've tried to follow the fedora packaging guidelines as much as possible > (there were only draft guidelines for golang packages) so that's why > there are so many of them. > You did it right. > So would the best way forward be for me to get all these packages in > Fedora first? My understanding was with RDO we were moving away from > packaging Openstack itself in fedora (instead keep the fedora packages > in RDO), would we treat these packages the same way? Or just put them > through Fedora, then bring them into RDO for Centos/EL only? > Thanks. Until we have a better alternative for packaging review, we still need to push them in Fedora. Moreover, it actually makes sense for operational tools to have them in Fedora. When they're imported, we'll just rebuild them in CBS.

> > Unfortunately yeah timing wasn't good for me to attend the meeting, but > I'll try and attend the next one. Just to clarify, the first step at > this stage is for me to get all packages above through the fedora > package review process? I am ok to do that, just with ~140 odd packages > it's going to take a while :/ > That's unfortunate, but we'll find more convenient ways to sync up with you :) Since this is a very large list of packages, I suggest that we just do a first round of mass review and fix what needs to be fixed first rather than wasting time ticket per ticket. After that, we'll submit them for review and get them approved rather quickly.

If you could push spec+srpm somewhere, I'll try to free myself some time during the two next weeks and batch review them. I'll also try to sort out packages that requires deeper reviews, and the ones that could be approved in one go after fixing. As we need two people for a review, we could split the list and alternate between the reviewee/reviewer role.

Regards, H. > Regards, > > Graeme > >> >> H. >> >>> Any suggestions or advice would be very much appreciated. >>> >>> Regards, >>> >>> Graeme >>> >>> -- >>> Graeme Gillies >>> Principal Systems Administrator >>> Openstack Infrastructure >>> Red Hat Australia >>> >>> _______________________________________________ >>> Rdo-list mailing list >>> Rdo-list(a)redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list >>> >>> To unsubscribe: rdo-list-unsubscribe(a)redhat.com > > > -- > Graeme Gillies > Principal Systems Administrator > Openstack Infrastructure > Red Hat Australia